Broken in 2024.11.0

Did you read the instructions?

[X] I have read the README, including the advanced debugging section.

The problem
I know it's deprecated, but it might be good to archive this repo, since it is now completely broken :
`Logger: homeassistant.util.package
Source: util/package.py:152
First occurred: November 7, 2024 at 10:45:50 PM (3 occurrences)
Last logged: November 7, 2024 at 10:45:51 PM
Unable to install package pyoverkiz==1.8.0: × No solution found when resolving dependencies: ╰─▶ Because pyoverkiz==1.8.0 depends on attrs>=21.2,<24.0 and attrs==24.2.0, we can conclude that pyoverkiz==1.8.0 cannot be used. And because you require pyoverkiz==1.8.0, we can conclude that your requirements are unsatisfiable.`
What version of this integration (ha-tahoma) has the issue?
2.15.0
What version of Home Assistant Core has the issue?
2024.11.0
Which gateway / hub do you use?
Somfy Connectivity Kit
Device model
No response
Home Assistant log
Logs
Logger: homeassistant.util.package
Source: util/package.py:152
First occurred: November 7, 2024 at 10:45:50 PM (3 occurrences)
Last logged: November 7, 2024 at 10:45:51 PM
Unable to install package pyoverkiz==1.8.0: × No solution found when resolving dependencies: ╰─▶ Because pyoverkiz==1.8.0 depends on attrs>=21.2,<24.0 and attrs==24.2.0, we can conclude that pyoverkiz==1.8.0 cannot be used. And because you require pyoverkiz==1.8.0, we can conclude that your requirements are unsatisfiable.

Additional information
No response

Hi, Same issue on my side.

any suggestions how to ad somfy tahoma to my Homeasssistant without tahat integration?

It’s natively integrated in HA! Search for overkiz
Verzonden vanuit Outlook voor iOShttps://aka.ms/o0ukef

Van: kaimundo @.>
Verzonden: Friday, November 8, 2024 2:57:00 PM
Aan: iMicknl/ha-tahoma @.>
CC: Dennis Brouwer @.>; Author @.>
Onderwerp: Re: [iMicknl/ha-tahoma] Broken in 2024.11.0 (Issue #858)
any suggestions how to ad somfy tahoma to my Homeasssistant without tahat integration?
—
Reply to this email directly, view it on GitHubhttps://github.com/iMicknl/ha-tahoma/issues/858#issuecomment-2464830277, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEFOO7CEQS2Z3UZ3EKYPRZ3Z7S7KZAVCNFSM6AAAAABRM4DVNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRUHAZTAMRXG4.
You are receiving this because you authored the thread.Message ID: @.***>

@dennisbrouwer91, well yes you are right but TaHoma Somfy integration is required. And we are unable to install because of the error message.

@dennisbrouwer91, well yes you are right but TaHoma Somfy integration is required. And we are unable to install because of the error message.

What do you mean? I switched this morning, turned off the old ha-tahoma integration, enabled the native one, done.

It’s natively integrated in HA! Search for overkiz Verzonden vanuit Outlook voor iOShttps://aka.ms/o0ukef
…
________________________________ Van: kaimundo @.> Verzonden: Friday, November 8, 2024 2:57:00 PM Aan: iMicknl/ha-tahoma @.> CC: Dennis Brouwer @.>; Author @.> Onderwerp: Re: [iMicknl/ha-tahoma] Broken in 2024.11.0 (Issue #858) any suggestions how to ad somfy tahoma to my Homeasssistant without tahat integration? — Reply to this email directly, view it on GitHub<#858 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEFOO7CEQS2Z3UZ3EKYPRZ3Z7S7KZAVCNFSM6AAAAABRM4DVNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRUHAZTAMRXG4. You are receiving this because you authored the thread.Message ID: @.***>

Thanx didnt See it... Stupid. My fault Thank you

hmmmm well the tahoma integration is not showing up in the list "Overkiz" I have different option like Hi-Kumo which is no more working.
I need to have the "Overkiz (by Somfy) - Custom component".  But each time I tried I get to have this integration I got the following error.
I maybe missed something but don't know what ... this is very strange
Erreur
Le flux de configuration n'a pas pu être chargé: 500 Internal Server Error Server got itself in trouble
"
Enregistreur: aiohttp.server
Source: /usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py:448
S'est produit pour la première fois: 18:20:59 (1 occurrences)
Dernier enregistrement: 18:20:59
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 477, in _handle_request
resp = await request_handler(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 559, in _handle
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 117, in impl
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 83, in forwarded_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 86, in ban_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware
response = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle
result = await handler(request, **request.match_info)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 81, in with_admin
return await func(self, request, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 74, in wrapper
return await method(view, request, data, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 172, in post
return await self._post_impl(request, data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 179, in _post_impl
return await super()._post_impl(request, data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 84, in _post_impl
result = await self._flow_mgr.async_init(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1301, in async_init
flow, result = await self._async_init(flow_id, handler, context, data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1326, in _async_init
flow = await self.async_create_flow(handler, context=context, data=data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1518, in async_create_flow
handler = await _async_get_flow_handler(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 3246, in _async_get_flow_handler
await _load_integration(hass, domain, hass_config)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 3223, in _load_integration
await async_process_deps_reqs(hass, hass_config, integration)
File "/usr/src/homeassistant/homeassistant/setup.py", line 575, in async_process_deps_reqs
await requirements.async_get_integration_with_requirements(
File "/usr/src/homeassistant/homeassistant/requirements.py", line 54, in async_get_integration_with_requirements
return await manager.async_get_integration_with_requirements(domain)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/requirements.py", line 170, in async_get_integration_with_requirements
await future
File "/usr/src/homeassistant/homeassistant/requirements.py", line 159, in async_get_integration_with_requirements
await self._async_process_integration(integration, done)
File "/usr/src/homeassistant/homeassistant/requirements.py", line 182, in _async_process_integration
await self.async_process_requirements(
File "/usr/src/homeassistant/homeassistant/requirements.py", line 264, in async_process_requirements
self._raise_for_failed_requirements(name, missing)
File "/usr/src/homeassistant/homeassistant/requirements.py", line 292, in _raise_for_failed_requirements
raise RequirementsNotFound(integration, [req])
homeassistant.requirements.RequirementsNotFound: Requirements for tahoma not found: ['pyoverkiz==1.8.0']."

The core Overkiz integration is broken, it won't let me control the device and it's operating as if it's in Automode.
I can't set any other mode, or enable/disable boost and the device will start heating only when the temperatures reach a threshold regardless of what time of day it is.
Which defeats the purpose of having the device in HA and controlling it smartly based on electricity prices and time of day.

Is there currently no option to add Somfy cover devices to Home Assistant?

Update? Same problem here

I changed the version in manifest.json as suggested by iMicknl in one of the closed issues for this problem and that seems to have solved my problems. I’ll open a new issue if I run into anything.
Fyi the latest version of pyoverkiz included in HA seems to be 1.14.1

If this works, I can see if I can update this custom component when I return from holidays in 2 weeks.
Otherwise I might indeed archive it as suggested, it has taken too much time to merge all features of this integration into Overkiz in core.

By the way, happy to see if I can prioritise porting the elements that are working in the custom integration but not in core.
The only issue is with some Atlantic devices in core, where the new features have not been developed by me and I don’t have a way to test it (and very limited time).

Thanks for the information, which helps to have tahoma installed and working again.
But still have this issue #98939 open
Take care and enjoy your holidays

I changed the version in manifest.json as suggested by iMicknl in one of the closed issues for this problem and that seems to have solved my problems. I’ll open a new issue if I run into anything.
Fyi the latest version of pyoverkiz included in HA seems to be 1.14.1

It's working again with me after changing to 1.14.1

I did the changes for the 1.14.1 version in the jason file and still not working even after a restart. Did I missed something if i tworks for you ? txs in advance

@odauguet, what do you mean exactly still not working ? Was it working before the home assistant upgrade ?

It was working very well before the HA upgrade, then no TaHoma connection
after Even when I changed the version in the json file. I did a rôll Back
on ha, and connection came Back.
So as soon as I upgrade on the novembre version of ha, I can not Connect
anymore to Somfy.
Txs
Le dim. 17 nov. 2024 à 17:30, Wind06 @.***> a écrit :

@odauguet https://github.com/odauguet, what do you mean exactly still
not working ? Was it working before the home assistant upgrade ?
—
Reply to this email directly, view it on GitHub
https://github.com/iMicknl/ha-tahoma/issues/858#issuecomment-2481355278,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BMBEMOZ3XIY77VMPOIZEXA32BDAD7AVCNFSM6AAAAABRM4DVNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBRGM2TKMRXHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Strange, I just updated from 2024.11.1 to 2024.11.2 with modification of the manifest.json. and Tahoma still connected.
Maybe another issue on your side

before the upgrade I was fo somfy on 2.15.0 and it was working

Enregistreur: homeassistant.util.package
Source: util/package.py:152
S'est produit pour la première fois: 18:30:58 (3 occurrences)
Dernier enregistrement: 18:31:00
Unable to install package pyoverkiz==1.8.0: × No solution found when resolving dependencies: ╰─▶ Because pyoverkiz==1.8.0 depends on attrs>=21.2,<24.0 and attrs==24.2.0, we can conclude that pyoverkiz==1.8.0 cannot be used. And because you require pyoverkiz==1.8.0, we can conclude that your requirements are unsatisfiable.

Absolutely I did that. And when I go and check the open version of pioverkiz, it is the 1.14.1…. I did it again and I have the same issue….Envoyé de mon iPhoneLe 18 nov. 2024 à 13:46, Wind06 @.***> a écrit :
Just a stupide question, did you implement the modification on the following file ?
/root/homeassistant/custom_components/tahoma/manifest.json
This is what you need to setup "pyoverkiz==1.14.1"
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Very strange, I am sorry not really sure I can help.

fixed in https://github.com/iMicknl/ha-tahoma/releases/tag/v2.16.0, thanks all!

poor coding etiquette to abandon this, the core component lacks features and plainly doesn't work. I can't control my boiler with the core component. How can you tell people to move to core when it doesn't work?

This wasn't meant to be deconstructive, but you shouldn't retire the old integration when there isn't a working core component with feature parity?
I see how big the list of issues is for the Overkiz core integration, you have worked on the oldest still open issues from dec 2022 & feb 2023 and frankly you seem to be the only one working the Overkiz issues, at least most of them are assigned to you.


Optimise assert, fix webpanel debug, remove legacy givepoints, fix gamegravity default, fix TimeHint

Optimise assert calls
Remove legacy givepoints command, PointsService has been disabled totally
Fix gamegravity command not being able to reset gravity
Fix TimeHint from not working at all
Fix webpanel not understanding error codes properly

No more givepoints command? No.

No more givepoints command? No.

Not needed and now does literally nothing because PointService does not work at all

I use it for the client notification

I use it for the client notification

:rbxnotify player Points awarded. You have been awarded X points

Too bad

Too bad

Bruh

[":giveppoints <player> <points>"] = ":script game:GetService("PointsService"):AwardPoints(game:GetService:("Players"):FindFirstChild("<player>"), <points>)"

What

What

Its an alias

DLGTM

DLGTM

-DLGTM
+LGTM

@Dimenpsyonal you forgot to merge this as well

I will not be merging this.

Get some other noob to merge this

I will not be merging this.

Why?

bro has a grudge against this pr

Removes givepoints command

you will merge it NOW

Removes givepoints command

Ok givepoints removal will be seperated to a different pull

real


Hang on device reduction kernel with 1 work item per group.

Bug summary
A generic reduction kernel hangs on the device when I supply an nd_range with only 1 work item per group.
I only observe the hang when running on the device, and only if using a reduction.
Thread backtrace shows it's stuck in the buffer destructor:
#0  0x000015554ebb370c in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib64/libpthread.so.0
#1  0x000015554fef9420 in __gthread_cond_wait (__mutex=<optimized out>,
    __cond=<optimized out>)
    at /ptmp/peint/build-cray-gcc-20210813.230140.804215673/cray-gcc/BUILD/snos_objdir/x86_64-suse-linux/libstdc++-v3/include/x86_64-suse-linux/bits/gthr-default.h:865
#2  std::__condvar::wait (__m=..., this=<optimized out>)
    at /ptmp/peint/build-cray-gcc-20210813.230140.804215673/cray-gcc/BUILD/snos_objdir/x86_64-suse-linux/libstdc++-v3/include/bits/std_mutex.h:155
#3  std::condition_variable::wait (this=<optimized out>, __lock=...)
    at ../../../../../cpe-gcc-11.2.0-202108140355.9bf1fd589a5c1/libstdc++-v3/src/c++11/condition_variable.cc:41
#4  0x0000155555542b3b in hipsycl::rt::worker_thread::wait() ()
   from /ccs/proj/stf006/rogersdd/crusher/lib/libhipSYCL-rt.so
#5  0x000000000028113b in hipsycl::sycl::detail::buffer_impl::~buffer_impl() ()
#6  0x00000000002808e9 in void __gnu_cxx::new_allocator<hipsycl::sycl::detail::buffer_impl>::destroy<hipsycl::sycl::detail::buffer_impl>(hipsycl::sycl::detail::buffer_impl*) ()
#7  0x000000000028088d in void std::allocator_traits<std::allocator<hipsycl::sycl::detail::buffer_impl> >::destroy<hipsycl::sycl::detail::buffer_impl>(std::allocator<hipsycl::sycl::detail::buffer_impl>&, hipsycl::sycl::detail::buffer_impl*) ()
#8  0x00000000002805c6 in std::_Sp_counted_ptr_inplace<hipsycl::sycl::detail::buffer_impl, std::allocator<hipsycl::sycl::detail::buffer_impl>, (__gnu_cxx::_Lock_policy)2>::_M_dispose() ()
#9  0x00000000002669f3 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() ()
#10 0x00000000002669aa in std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count() ()
#11 0x0000000000287bb9 in std::__shared_ptr<hipsycl::sycl::detail::buffer_impl,
...

To Reproduce
Compile and run the following code:
#include <stdio.h>
#include <stdlib.h>
#include <CL/sycl.hpp>

namespace sycl = cl::sycl;

int main(int argc, char *argv[]) {
    int N = 0;
    int groups = 4;
    int width = 1;
    if(argc > 1) {
        groups = atoi(argv[1]);
    }
    if(argc > 2) {
        width = atoi(argv[2]);
    }

    sycl::queue q;

    if(1) {
      sycl::buffer<int,1> ret(&N, 1);
      q.submit([&](sycl::handler &cgh) {
        sycl::nd_range<1> rng(groups*width, width);
        sycl::accessor<int, 1> d_ret(ret, cgh);//, sycl::read_write);
        const size_t count = 1 << 6;

        cgh.parallel_for(rng,
                sycl::reduction(d_ret, sycl::plus<int>()),
                [count=count](sycl::nd_item<1> it, auto &ans) {
            sycl::group<1> g = it.get_group();
            printf("count %d id %d range %d\n",
                    count, g.get_group_linear_id(),
                    g.get_group_linear_range());
            ans += 1;
        });
      });
    }

    printf("Launched %d workers.\n", N);
    return 0;
}

Passing a value >1 for the width works, but with width=1, it deadlocks.
Expected behavior
The code should run successfully for all device-supported values of groups and width.
Describe your setup

I installed commit 2d937998228826f183a670d927749a4e6cb93a11 from July 13 and am running on AMD gfx90a.

Describe the dependencies that hipSYCL sits on top of in your setup:

host compiler cce/14.0.0
boost 1.79.0
ROCm version 5.1.0
llvm includes /opt/rocm-5.1.0/llvm/lib/clang/14.0.0/include

How you have compiled your application: syclcc --hipsycl-gpu-arch=gfx90a -o err err.cpp

Additional context
Error discovered while running device-accelerated tests on a hash table implementation https://github.com/ORNL/SYCLhash.

Thank you, I think I can reproduce.
It hangs in the buffer destructor because the destructor waits for the kernels to complete, which never happens.
The reason is because there seems to be a bug in the way we determine the number of reduction kernels. The way it works is that the user kernel performs a work group reduction, and then we spawn one (or multiple) pure reduction kernels afterwards that then aggregate the work group results into one global result.
It seems that currently those kernels just reuse the group size of the user kernel. If that group size is one however, no additional group reduction can take place, and the reduction never results in a single value. So it should be easy to fix by defaulting to a group size > 1 for the reduction kernels in case the user group size is 1.
Because of this, it actually works if the number of work groups is one two, but if you have more than one work groups and a local size of 1, it hangs.


experimental(terraform): Initial Conventional Terraform

Reorganizes ops and trigger terraform resources into an individual ops module.
Refactors how services are enabled via terraform by adding a toggle variable
Boiler plate instructions for deploying the ops environment

Thanks for your first PR! This is looking like a great first iteration for experimental terraform refactor. Thanks for putting this together.


Feature/ubuntu18 fix

Fix for ubuntu 18
Updated webservice number for consistency (won't be needed when it's changed to a parameter)

Coverage remained the same at 50.409% when pulling 7d03827cbe107d9c2b68145b49ae4bed7ad882eb on feature/ubuntu18Fix into 9c9518356017b1df182fc007439314f856f09701 on develop.


Add bulkData() method

Adds a method for the bulk data endpoint.
Thanks for your work on this, the interface is very nicely designed. 👍
(Note: my editor automatically trims extra spaces on lines when saving files, so DOCUMENTATION.md has quite a few line changes where a single space was removed.)

Thank you, should have ran tslint first.
Looks good to me.


Release ndk-build-0.4.4, cargo-apk-0.8.3

Despite transitioning over to xbuild I still care about cargo-apk and especially releasing new features and bugfixes that already made it in before we started the process.  This release has many little additions and fixes, though some might be considered API-breaking?

Default target_sdk_version to 30 or lower (instead of the highest supported SDK version by the detected NDK toolchain)
for more consistent interaction with Android backwards compatibility handling and its increasingly strict usage rules:
https://developer.android.com/distribute/best-practices/develop/target-sdk
Remove default insertion of MAIN intent filter through a custom serialization function, this is better filled in by
the default setup in cargo-apk. (#241)

These two changes in ndk-build, and the relevant API/SDK level changes in cargo-apk may warrant a breaking bump?

yes, will be a while before we should recommend people using xbuild by default. hope we can get xbuild there within the next 3 months.

Yeah, so better get this at least the merged features out there, and we can do more releases following that. We'll start recommending PRs to transition to xbuild when they're either large or nearing the "cutoff point" where xbuild successfully supersedes cargo-apk.

@dvc94ch @msiglreith what are your thoughts on making this a breaking minor release?

well, either it breaks existing users or not. did we change any api's in a way that would cause build failures? but I really don't care much either way.

We changed the target_sdk_version which may now be different depending on what SDKs the user had installed, so it does have an impact on compiled binaries. As such ndk-build and cargo-apk should probably be breaking (and I'll add the **Breaking** prefix in the changelog if everyone agrees).

well, bug fixes/behavioral changes are not considered breaking according to semver rules. otherwise you could never have meaningful patch releases (whitespace changes don't count). but don't really care.

That's a fair observation. I think behavioural changes are still part of the API and should as such be guarded by the same semver principles (at least that's what I could find online about the matter) but both functions can just as much be bugfixes...

Given ndk-build is not only used by cargo-apk anymore (https://crates.io/crates/ndk-build/reverse_dependencies) I would vote for a breaking change as upper levels may relay on the default intent filter for example.

@msiglreith Thanks, I've been leaning towards that as well. Breaking version for cargo-apk is probably less of an issue given that cargo install by default picks the latest, but it's more correct nevertheless (and there are probably installers / arguments to stick to a specific version).


NationalIntelligence\Elevation service - appears to be using feet and meters for elevation surfaces

The NationalIntelligence\Elevation service MDS appears to be using a mix of data that includes data with elevation in feet, and meters.

@elinz This is an issue that has been repeatedly fixed.  There seems to be an issue with the mosaic datasets losing raster functions after they are

republished as seen at last years UC both at UC and when we returned
there is a system upgrade 10.4

This issue should be investigated further so that the issue can be addressed without having a ton or fixes after items 1 or 2 are performed.

This service is for the Predicitive Analysis demo data.  Whoever built the
\[severname]\Data\DerivedLayers\PredictiveAnalysis.gdb\Elevation mosaic dataset within the PredictiveAnalysis.gdb needs to add the unit conversion raster function to the lidar data only and then regenerate the overviews.  <-- Assigning to @dfoll
Additionally, I question on why there is a DemoIntelligence elevation service that uses the same elevation data as the Cached Elevation Service or the WGS84 elevation service.  @dfoll If this service is necessary cool but if not and either of the other two elevation services would suffice the please delete this service to reduce confusion to our portal users.  @lfunkhouser What would the process be to delete or remove an already released service?

Currently the NationalIntelligence\Elevation is a single raster created from multiple rasters.  Because of this I am unable to add the unit conversion raster function to the data that is in the wrong measurement units.  This single raster needs to be created.  I have discussed this with @dfoll.
@pshowalter There is debate on this service.  If you need an elevation service right now, please use the Cached World Elevation Service or the World Elevation WGS84 Service.  If either of these two services do not fit your needs please let me know and I will create one that does.

Looks like it would be a good service to use for analysis, rather than global, but have found a few services to test with.
Objective was to test different elevation surface types (Elevation Service, fGDB, MDS, dted) and various PCS’s using  Military Tools for ArcGIS.
·        Cached World Elevation – does not display in my ArcMap 10.3.1 or Pro 1.2 – suggestions?  This service is Web Mercator
·        World Elevation WGS84 does display, and can test with this.
From: Natalie Campos<EMAIL_ADDRESS>Sent: Wednesday, March 16, 2016 1:12 PM
To: Esri/ops-server-config
Cc: Patrick Showalter
Subject: Re: [ops-server-config] NationalIntelligence\Elevation service - appears to be using feet and meters for elevation surfaces (#1410)
Currently the NationalIntelligence\Elevation is a single raster created from multiple rasters. Because of this I am unable to add the unit conversion raster function to the data that is in the wrong measurement units. This single raster needs to be created. I have discussed this with @dfollhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_dfoll&d=CwMCaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=6BG_IlrzjbGAOIlLCA5vdO8l1NJVfhbWnuChxtu_d88&m=hpqdZXMmOsvygJXsEEIurWOdaZF7PrJcEUG7htBNEWY&s=jgdfFt9Xu3GpxS8QWt87r0E-AqklCdFTv8a9bGduF6M&e=.
@pshowalterhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_pshowalter&d=CwMCaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=6BG_IlrzjbGAOIlLCA5vdO8l1NJVfhbWnuChxtu_d88&m=hpqdZXMmOsvygJXsEEIurWOdaZF7PrJcEUG7htBNEWY&s=meagzo-y0TTVKZjk6skBlSWznvKz8hDIm6GditZd5fo&e= There is debate on this service. If you need an elevation service right now, please use the Cached World Elevation Service or the World Elevation WGS84 Service. If either of these two services do not fit your needs please let me know and I will create one that does.
[image]https://urldefense.proofpoint.com/v2/url?u=https-3A__cloud.githubusercontent.com_assets_5116835_13821395_a79cf170-2Deb5e-2D11e5-2D9d8f-2D551ba5f4b7d0.png&d=CwMCaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=6BG_IlrzjbGAOIlLCA5vdO8l1NJVfhbWnuChxtu_d88&m=hpqdZXMmOsvygJXsEEIurWOdaZF7PrJcEUG7htBNEWY&s=faCpqsA9vQvTpxR7b8RDEetZRTC1mixyZgqYKuhyTN0&e=
[image]https://urldefense.proofpoint.com/v2/url?u=https-3A__cloud.githubusercontent.com_assets_5116835_13821574_6f49a52e-2Deb5f-2D11e5-2D9c82-2D2fc74994bef2.png&d=CwMCaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=6BG_IlrzjbGAOIlLCA5vdO8l1NJVfhbWnuChxtu_d88&m=hpqdZXMmOsvygJXsEEIurWOdaZF7PrJcEUG7htBNEWY&s=JzjPYDE9OUGFvoRRJC91pHNOMJxQgp6WccNS5B1Nl_E&e=
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Esri_ops-2Dserver-2Dconfig_issues_1410-23issuecomment-2D197433225&d=CwMCaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=6BG_IlrzjbGAOIlLCA5vdO8l1NJVfhbWnuChxtu_d88&m=hpqdZXMmOsvygJXsEEIurWOdaZF7PrJcEUG7htBNEWY&s=HsDRlT5cYRitEtWis4EbIFeNk9xNdyFGIzbaTnQ6Ki8&e=

cached world elevation is a Lerc service that can not be used in Pro but can still be viewed dynamically in ArcMap.  Though I don't know for how much longer.  To view it in ArcMap r-click in the properties and check the Enable Cache View.

If you need mosaic datasets you can use the MDs for elevation in
\[ServerName]\Data\FoundationOverlays\Elevation\MosaicDatasets
Anything just let me know.

If it’s going away, it may not be worth the effort to run to ground.
Enable Cache mode is checked, but nothing displays.
When I add the Service, I get an RGB Layer in the TOC, and it is just named “Cached World Elevation” not “NationalIntelligence\CachedWorldElevation” like I see in the TOC from your screen capture.
Also, Description should be changed if its not viewable in Pro
Description: A global multi-resolution Digital Terrain Model (DTM) to be used as a cached elevation surface in ArcGIS Pro or ArcGIS Scene Viewer. The World Elevation Cache service can only be viewed dynamically in ArcGIS Pro or ArcMap, and is not viewable in ArcGIS Portal. The World Elevation Cache service was created from: USGS GTOPO30 global coverage, USGS SRTM 90m coverage, USGS GMTED2010, and USGS California Central Coast Lidar.
<EMAIL_ADDRESS><EMAIL_ADDRESS>From: Natalie Campos<EMAIL_ADDRESS>Sent: Wednesday, March 16, 2016 5:15 PM
To: Esri/ops-server-config
Cc: Patrick Showalter
Subject: Re: [ops-server-config] NationalIntelligence\Elevation service - appears to be using feet and meters for elevation surfaces (#1410)

cached world elevation is a Lerc service that can not be used in Pro but can still be viewed dynamically in ArcMap. Though I don't know for how much longer. To view it in ArcMap r-click in the properties and check the Enable Cache View.

[image]https://urldefense.proofpoint.com/v2/url?u=https-3A__cloud.githubusercontent.com_assets_5116835_13828906_54f6aeac-2Deb81-2D11e5-2D91a0-2D3f0f31e2e035.png&d=CwMCaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=6BG_IlrzjbGAOIlLCA5vdO8l1NJVfhbWnuChxtu_d88&m=mOJEovAt1-p71jLl0S3yMTa62q-tVxrHBkvq2kJ_3js&s=UqUvOziScJF7mgSKGFxY-jtBxHyCKj5WAQqeDFpdcm0&e=
If you need mosaic datasets you can use the MDs for elevation in
[ServerName]\Data\FoundationOverlays\Elevation\MosaicDatasets
Anything just let me know.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Esri_ops-2Dserver-2Dconfig_issues_1410-23issuecomment-2D197552187&d=CwMCaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=6BG_IlrzjbGAOIlLCA5vdO8l1NJVfhbWnuChxtu_d88&m=mOJEovAt1-p71jLl0S3yMTa62q-tVxrHBkvq2kJ_3js&s=jlNevkXTWEdnR7SNNyC2mFA7QJmFenZeDcX4UgpeNz0&e=

@dfoll What's the status of this issue? Thanks.

@dfoll - delete this service.

i have taken personal ownership of this item and unshared it (instead of deleting, just in case, we find out we need it back for some reason, then it's still around for a couple days).
@ircampbell @kAilshie in the PA webmap i replaced this layer with the global elevation layer that @NatalieCampos recommends we use


boolean PubSubClient::publish_P returns false

We think there is a bug in the publish_P method which was reporting false, even though the message was sent to the server. The expected length is off by a few bytes.
The original code:
 return rc == tlen + 4 + plength;

Was changed to:
// Header (1 byte) + llen + identifier (2 bytes)  + topic len + payload len
int expectedLength = 1 + llen + 2 + tlen + plength;
return (rc == expectedLength);

}

Any progress on this? Nobody wants to fix this?


Add Aventus Layer-2

Hey @dr-ngubo!
It seems that Aventus is a side-chain and they are using layer2 purely as a marketing term.

According to the source code, the state root of the network can change if the quorum is met: https://etherscan.io/address/0x46eaD2891ecf9c7444cB9197D4FAacC7F54C593C#code#L451
There is no dispute period - withdrawals are not delayed.
There is a slashing mechanism but it's based on quorom - there is no real fraud-proof system.
No tx data are stored on-chain.
In their whitepaper they already hint that consensus relies on 2/3 of validators:

Given all of that, it's hard to claim that Aventus shares the security of L1 - it's fully independent PoS network connected with ethereum via multisig bridge.


Don't enter a newline when pressing return on an auto-completion keyword which has been completed

VSCode Version: 1.12
OS Version: Windows 10

Steps to Reproduce:

Type in a complete keyword which brings up an auto-completion prompt
Press Enter

In my experience, IDE's tend to just close out the auto-completion box in this scenario. It seems quite unusual to have it input a newline in this situation.
Gif of the issue:

This is a dupe of https://github.com/Microsoft/vscode/issues/24420. This isn't an easy topic as it seems, please join the discussion.
In short, to re-store the old enter behaviour add this to your keybindings.json
{
  "key": "enter",
  "command": "acceptSelectedSuggestion",
  "when": "editorTextFocus && suggestWidgetVisible"
}


Save and restore state

Hey,
first of all thanks a lot for this homebridge plugin!
I was looking for an option to save and restore the latest state of an accessory. I didn't find anything yet, but I wanted to make sure this isn't there yet before implementing sth on my own.
More detailed description: Every time I restart home bridge because of whatever reason, all my blinds are virtually opened. In order to get the expected behaviour, I have to move them to 0% or 100% via HomeKit or homebridge.
Saving the current state to a local json file and reading that on boot/initialization should imho do the trick.
As mentioned above, if this functionality does not exist yet, I'd be happy to provide a PR.

I have the same issue with my plugs. Status is lost when restarting homebridge

Same here. Would love to have that 🙏


Resolving #167

corrected confusing addon enablement instruction
added anyuid and admin-user addon as part of profile setup instruction

Can one of the admins verify this patch?


Start/Rescan action it takes a long time and user has none info about background work progress

This behavior is for me as user unpleasant.

Well in case there are updates a popup will show what updates are available. The problem is that the app is sitting in the system tray where I cannot really show a lot of information. So the idea is to have the app running in the background and from time to time you can check the main window to see if there are any updates available. It is not meant to be a desktop app that you execute once. The automatic rescan will take place every 3 hours. So what behavior do you expect?

The give user info about Rescan only in case that is Rescan invoked from GUI (and at start time)... Maybe it be more work...

So you mean if you trigger the rescan manually from the menu you would like to see that it's doing something? Like a spinning indicator or similar? But where should that appear because it is a system tray menu I cannot simply update that, meaning to say only for this purpose I would need to add a window that only shows..."I'm working on a rescan" which does not really make sense right? I mean I could maybe open the main window after the rescan was done in case updates have been found...

Or maybe open the main window directly when rescan was pressed and show an indicator there?

With Version 17.0.5 there will be an indicator in the main window which shows the ongoing update process


Filter selections causes network mismatch

Environment:Testnet
PR:#493
URL:https://explorer-git-feat-microblocks-final-blockstack.vercel.app/transactions?chain=testnet
User selects the filter on Transaction tab
User unselect all of the selection
User notices that the page is asking to switch network
User notices that the behavior isnt user friendly
Is there a flow that we can work here? Making it as a bug but can be changed to enhancement if needed.
https://user-images.githubusercontent.com/38872890/127397945-853a6d25-af90-4b17-a38e-8bf74e62bdc3.mov

@aulneau has a local fix for this

Tested the issue both on testnet and mainnet.
Test passed

@aulneau can we close this issue?

Yep, it's resolved in the microblocks deployment


Example needed

An example would be good.

Examples have been mentioned in the Readme File in commit 6cf56c83fa3ba5e3eb9d00687964ee7f03361640.


Feat/task rnv new args

Description
This allows to pass arguments to rnv new command and --ci to skip asking if provided data is correct - rnv new ${projectName} "${appTitle}" ${appId} ${version} ${workspace} ${template} ${templateVersion} ${supportedPlatforms} --ci
Breaking Changes

PRs should not introduce breaking changes to existing functionality
if breaking change cannot be avoided it has to be introduced in 2 phases (release cycles of 0.x.0)

0.x.0 Add new functionality + add DEPRECATED warning to existing fuctionality
0.[x+1].0 Remove deprecated functionality

I have tested my changes on:
New project:

[x] ios simulator
[ ] ios device
[ ] android simulator
[ ] android device
[ ] web browser
[ ] web -e next browser
[x] tvos simulator
[ ] tvos device
[ ] androidtv simulator
[ ] androidtv device
[ ] androidwear simulator
[ ] androidwear device
[ ] tizen simulator
[ ] tizen device
[ ] tizenmobile simulator
[ ] tizenwatch device
[ ] webos simulator
[ ] webos device
[ ] macos
[ ] windows
[ ] chromecast device

Codecov Report

Merging #732 (fc4492e) into develop (10d8e32) will decrease coverage by 0.06%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           develop     #732      +/-   ##
===========================================
- Coverage    20.04%   19.98%   -0.07%
===========================================
  Files           84       84
  Lines         5766     5784      +18
  Branches      1288     1294       +6
===========================================
  Hits          1156     1156
- Misses        3449     3461      +12
- Partials      1161     1167       +6

Flag
Coverage Δ

rnvunittests
19.98% <0.00%> (-0.07%)
:arrow_down:

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

Impacted Files
Coverage Δ

packages/rnv/src/core/constants.js
98.86% <ø> (ø)

packages/rnv/src/engine-core/tasks/task.rnv.new.js
2.27% <0.00%> (-0.26%)
:arrow_down:

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 10d8e32...fc4492e. Read the comment docs.


failed to load GLFW3 shared lib

this error occured, I'm very new to coding, so I don't know how to solve it.

Make sure you have glfw3 set up on your system.
https://www.glfw.org/

can I just clone the github source glfw and install it?

Most likely yes.

sorry to bother again, but the issue accoured again...

You could try the answers here: https://stackoverflow.com/questions/51918633/importerror-failed-to-load-glfw3-shared-library-without-root-access-on-linux

this appeared when I use the method in your link

You probably have a problem with root permissions in your operating system, which is not my expertise. Seek help from Linux users/forums/websites.


Can't serialize structs that contain ::Type{T} fields

struct MyObject{T}
    field::Type{T}
end
MyObject(Int16)
Arrow.ArrowTypes.registertype!(MyObject, MyObject)
tbl = (; obj = [MyObject(Int16), MyObject(Int16)])
Arrow.write("test.arrow", tbl)

yields
ERROR: ArgumentError: type does not have a definite number of fields
Stacktrace:
 [1] fieldcount at ./reflection.jl:725 [inlined]
 [2] arrowvector(::Arrow.ArrowTypes.StructType, ::Arrow.ToStruct{Type{Int16},1,Array{MyObject{Int16},1}}, ::Int64, ::Int64, ::Int64, ::Dict{Int64,Any}, ::Array{Arrow.DictEncoding,1}, ::Nothing; kw::Base.Iterators.Pairs{Symbol,Union{Nothing, Bool},NTuple{5,Symbol},NamedTuple{(:dictencode, :compression, :largelists, :denseunions, :dictencodenested),Tuple{Bool,Nothing,Bool,Bool,Bool}}}) at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/struct.jl:89
 [3] arrowvector(::Type{Type{Int16}}, ::Arrow.ToStruct{Type{Int16},1,Array{MyObject{Int16},1}}, ::Int64, ::Int64, ::Int64, ::Dict{Int64,Any}, ::Array{Arrow.DictEncoding,1}, ::Nothing; kw::Base.Iterators.Pairs{Symbol,Union{Nothing, Bool},NTuple{5,Symbol},NamedTuple{(:dictencode, :compression, :largelists, :denseunions, :dictencodenested),Tuple{Bool,Nothing,Bool,Bool,Bool}}}) at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:90
 [4] arrowvector(::Arrow.ToStruct{Type{Int16},1,Array{MyObject{Int16},1}}, ::Int64, ::Int64, ::Int64, ::Dict{Int64,Any}, ::Array{Arrow.DictEncoding,1}, ::Nothing; dictencoding::Bool, dictencode::Bool, kw::Base.Iterators.Pairs{Symbol,Union{Nothing, Bool},NTuple{4,Symbol},NamedTuple{(:compression, :largelists, :denseunions, :dictencodenested),Tuple{Nothing,Bool,Bool,Bool}}}) at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:58
 [5] (::Arrow.var"#45#46"{Base.Iterators.Pairs{Symbol,Union{Nothing, Bool},NTuple{5,Symbol},NamedTuple{(:dictencode, :compression, :largelists, :denseunions, :dictencodenested),Tuple{Bool,Nothing,Bool,Bool,Bool}}},Array{MyObject{Int16},1},Int64,Int64,Dict{Int64,Any},Array{Arrow.DictEncoding,1}})(::Int64) at ./none:0
 [6] iterate at ./generator.jl:47 [inlined]
 [7] collect(::Base.Generator{UnitRange{Int64},Arrow.var"#45#46"{Base.Iterators.Pairs{Symbol,Union{Nothing, Bool},NTuple{5,Symbol},NamedTuple{(:dictencode, :compression, :largelists, :denseunions, :dictencodenested),Tuple{Bool,Nothing,Bool,Bool,Bool}}},Array{MyObject{Int16},1},Int64,Int64,Dict{Int64,Any},Array{Arrow.DictEncoding,1}}}) at ./array.jl:686
 [8] _totuple at ./tuple.jl:258 [inlined]
 [9] Tuple at ./tuple.jl:230 [inlined]
 [10] arrowvector(::Arrow.ArrowTypes.StructType, ::Array{MyObject{Int16},1}, ::Int64, ::Int64, ::Int64, ::Dict{Int64,Any}, ::Array{Arrow.DictEncoding,1}, ::Nothing; kw::Base.Iterators.Pairs{Symbol,Union{Nothing, Bool},NTuple{5,Symbol},NamedTuple{(:dictencode, :compression, :largelists, :denseunions, :dictencodenested),Tuple{Bool,Nothing,Bool,Bool,Bool}}}) at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/struct.jl:89
 [11] arrowvector(::Type{MyObject{Int16}}, ::Array{MyObject{Int16},1}, ::Int64, ::Int64, ::Int64, ::Dict{Int64,Any}, ::Array{Arrow.DictEncoding,1}, ::Nothing; kw::Base.Iterators.Pairs{Symbol,Union{Nothing, Bool},NTuple{5,Symbol},NamedTuple{(:dictencode, :compression, :largelists, :denseunions, :dictencodenested),Tuple{Bool,Nothing,Bool,Bool,Bool}}}) at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:90
 [12] arrowvector(::Array{MyObject{Int16},1}, ::Int64, ::Int64, ::Int64, ::Dict{Int64,Any}, ::Array{Arrow.DictEncoding,1}, ::Nothing; dictencoding::Bool, dictencode::Bool, kw::Base.Iterators.Pairs{Symbol,Union{Nothing, Bool},NTuple{4,Symbol},NamedTuple{(:compression, :largelists, :denseunions, :dictencodenested),Tuple{Nothing,Bool,Bool,Bool}}}) at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:58
 [13] toarrowvector(::Array{MyObject{Int16},1}, ::Int64, ::Dict{Int64,Any}, ::Array{Arrow.DictEncoding,1}, ::Nothing; compression::Nothing, kw::Base.Iterators.Pairs{Symbol,Bool,NTuple{4,Symbol},NamedTuple{(:largelists, :denseunions, :dictencode, :dictencodenested),NTuple{4,Bool}}}) at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:36
 [14] (::Arrow.var"#109#110"{Dict{Int64,Any},Bool,Nothing,Bool,Bool,Bool,Array{Any,1},Array{Type,1},Array{Arrow.DictEncoding,1}})(::Array{MyObject{Int16},1}, ::Int64, ::Symbol) at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/write.jl:202
 [15] eachcolumn at /home/ec2-user/.julia/packages/Tables/8FVkV/src/utils.jl:70 [inlined]
 [16] toarrowtable(::NamedTuple{(:obj,),Tuple{Array{MyObject{Int16},1}}}, ::Dict{Int64,Any}, ::Bool, ::Nothing, ::Bool, ::Bool, ::Bool) at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/write.jl:201
 [17] macro expansion at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/write.jl:111 [inlined]
 [18] macro expansion at ./task.jl:332 [inlined]
 [19] write(::IOStream, ::NamedTuple{(:obj,),Tuple{Array{MyObject{Int16},1}}}, ::Bool, ::Bool, ::Nothing, ::Bool, ::Bool, ::Bool, ::Int64) at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/write.jl:108
 [20] #100 at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/write.jl:77 [inlined]
 [21] open(::Arrow.var"#100#101"{Bool,Nothing,Bool,Bool,Bool,Int64,NamedTuple{(:obj,),Tuple{Array{MyObject{Int16},1}}}}, ::String, ::Vararg{String,N} where N; kwargs::Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{(),Tuple{}}}) at ./io.jl:325
 [22] open at ./io.jl:323 [inlined]
 [23] #write#99 at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/write.jl:76 [inlined]
 [24] write(::String, ::NamedTuple{(:obj,),Tuple{Array{MyObject{Int16},1}}}) at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/write.jl:76
 [25] top-level scope at REPL[6]:1

I also tried not annotating with ::Type and got an "unreachable reached" on Julia 1.5.3:
julia> struct MyObject2{TT}
           field::TT
       end

julia> MyObject2(Int16)
MyObject2{DataType}(Int16)

julia> Arrow.ArrowTypes.registertype!(MyObject2, MyObject2)

julia> tbl = (; obj = [MyObject2(Int16), MyObject2(Int16)])
(obj = MyObject2{DataType}[MyObject2{DataType}(Int16), MyObject2{DataType}(Int16)],)

julia> Arrow.write("test.arrow", tbl)
Unreachable reached at 0x7f529255f3f7

signal (4): Illegal instruction
in expression starting at REPL[11]:1
ToStruct at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/struct.jl:67
#45 at ./none:0
iterate at ./generator.jl:47 [inlined]
collect at ./array.jl:686 [inlined]
_totuple at ./tuple.jl:258 [inlined]
Tuple at ./tuple.jl:230 [inlined]
#arrowvector#44 at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/struct.jl:89
arrowvector##kw at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/struct.jl:81 [inlined]
#arrowvector#10 at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:90
arrowvector##kw at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:81
unknown function (ip: 0x7f5292560666)
_jl_invoke at /buildworker/worker/package_linux64/build/src/gf.c:2231 [inlined]
jl_apply_generic at /buildworker/worker/package_linux64/build/src/gf.c:2398
#arrowvector#4 at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:58
unknown function (ip: 0x7f529255f0f3)
arrowvector##kw at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:52
unknown function (ip: 0x7f529255ed96)
_jl_invoke at /buildworker/worker/package_linux64/build/src/gf.c:2231 [inlined]
jl_apply_generic at /buildworker/worker/package_linux64/build/src/gf.c:2398
#45 at ./none:0
iterate at ./generator.jl:47 [inlined]
collect_to! at ./array.jl:732
collect_to_with_first! at ./array.jl:710
unknown function (ip: 0x7f529255e99b)
_jl_invoke at /buildworker/worker/package_linux64/build/src/gf.c:2231 [inlined]
jl_apply_generic at /buildworker/worker/package_linux64/build/src/gf.c:2398
collect at ./array.jl:691
_totuple at ./tuple.jl:258 [inlined]
Tuple at ./tuple.jl:230 [inlined]
#arrowvector#44 at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/struct.jl:89
arrowvector##kw at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/struct.jl:81 [inlined]
#arrowvector#10 at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:90
arrowvector##kw at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:81
unknown function (ip: 0x7f529255a0d6)
_jl_invoke at /buildworker/worker/package_linux64/build/src/gf.c:2231 [inlined]
jl_apply_generic at /buildworker/worker/package_linux64/build/src/gf.c:2398
#arrowvector#4 at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:58
unknown function (ip: 0x7f5292558273)
arrowvector##kw at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:52
unknown function (ip: 0x7f5292557f16)
_jl_invoke at /buildworker/worker/package_linux64/build/src/gf.c:2231 [inlined]
jl_apply_generic at /buildworker/worker/package_linux64/build/src/gf.c:2398
#45 at ./none:0
iterate at ./generator.jl:47 [inlined]
collect at ./array.jl:686
_totuple at ./tuple.jl:258 [inlined]
Tuple at ./tuple.jl:230 [inlined]
#arrowvector#44 at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/struct.jl:89
arrowvector##kw at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/struct.jl:81 [inlined]
#arrowvector#10 at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:90
arrowvector##kw at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:81
unknown function (ip: 0x7f5292557b16)
_jl_invoke at /buildworker/worker/package_linux64/build/src/gf.c:2231 [inlined]
jl_apply_generic at /buildworker/worker/package_linux64/build/src/gf.c:2398
#arrowvector#4 at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:58
unknown function (ip: 0x7f5292555cb3)
arrowvector##kw at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:52
unknown function (ip: 0x7f5292555956)
_jl_invoke at /buildworker/worker/package_linux64/build/src/gf.c:2231 [inlined]
jl_apply_generic at /buildworker/worker/package_linux64/build/src/gf.c:2398
#45 at ./none:0
iterate at ./generator.jl:47 [inlined]
collect at ./array.jl:686
_totuple at ./tuple.jl:258 [inlined]
Tuple at ./tuple.jl:230 [inlined]
#arrowvector#44 at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/struct.jl:89
arrowvector##kw at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/struct.jl:81 [inlined]
#arrowvector#10 at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:90
unknown function (ip: 0x7f529255556d)
arrowvector##kw at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:81
unknown function (ip: 0x7f529255396d)
_jl_invoke at /buildworker/worker/package_linux64/build/src/gf.c:2231 [inlined]
jl_apply_generic at /buildworker/worker/package_linux64/build/src/gf.c:2398
#arrowvector#4 at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:58
unknown function (ip: 0x7f52925536bd)
arrowvector##kw at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:52 [inlined]
#toarrowvector#3 at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:36
toarrowvector##kw at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:34 [inlined]
toarrowvector##kw at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/arraytypes/arraytypes.jl:34 [inlined]
#109 at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/write.jl:202
eachcolumn at /home/ec2-user/.julia/packages/Tables/8FVkV/src/utils.jl:70 [inlined]
toarrowtable at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/write.jl:201
unknown function (ip: 0x7f5292553354)
_jl_invoke at /buildworker/worker/package_linux64/build/src/gf.c:2231 [inlined]
jl_apply_generic at /buildworker/worker/package_linux64/build/src/gf.c:2398
macro expansion at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/write.jl:111 [inlined]
macro expansion at ./task.jl:332 [inlined]
write at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/write.jl:108
#100 at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/write.jl:77 [inlined]
#open#287 at ./io.jl:325
open at ./io.jl:323 [inlined]
#write#99 at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/write.jl:76 [inlined]
write at /home/ec2-user/.julia/packages/Arrow/Re9EM/src/write.jl:76
unknown function (ip: 0x7f529254ffda)
_jl_invoke at /buildworker/worker/package_linux64/build/src/gf.c:2231 [inlined]
jl_apply_generic at /buildworker/worker/package_linux64/build/src/gf.c:2398
jl_apply at /buildworker/worker/package_linux64/build/src/julia.h:1690 [inlined]
do_call at /buildworker/worker/package_linux64/build/src/interpreter.c:117
eval_value at /buildworker/worker/package_linux64/build/src/interpreter.c:206
eval_stmt_value at /buildworker/worker/package_linux64/build/src/interpreter.c:157 [inlined]
eval_body at /buildworker/worker/package_linux64/build/src/interpreter.c:566
jl_interpret_toplevel_thunk at /buildworker/worker/package_linux64/build/src/interpreter.c:660
jl_toplevel_eval_flex at /buildworker/worker/package_linux64/build/src/toplevel.c:840
jl_toplevel_eval_flex at /buildworker/worker/package_linux64/build/src/toplevel.c:790
jl_toplevel_eval_flex at /buildworker/worker/package_linux64/build/src/toplevel.c:790
jl_toplevel_eval_flex at /buildworker/worker/package_linux64/build/src/toplevel.c:790
jl_toplevel_eval_in at /buildworker/worker/package_linux64/build/src/toplevel.c:883
eval at ./boot.jl:331
_jl_invoke at /buildworker/worker/package_linux64/build/src/gf.c:2214 [inlined]
jl_apply_generic at /buildworker/worker/package_linux64/build/src/gf.c:2398
eval_user_input at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.5/REPL/src/REPL.jl:134
repl_backend_loop at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.5/REPL/src/REPL.jl:195
start_repl_backend at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.5/REPL/src/REPL.jl:180
#run_repl#37 at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.5/REPL/src/REPL.jl:292
run_repl at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.5/REPL/src/REPL.jl:288
_jl_invoke at /buildworker/worker/package_linux64/build/src/gf.c:2231 [inlined]
jl_apply_generic at /buildworker/worker/package_linux64/build/src/gf.c:2398
#807 at ./client.jl:399
jfptr_YY.807_45002.clone_1 at /home/ec2-user/.asdf/installs/julia/1.5.3/lib/julia/sys.so (unknown line)
_jl_invoke at /buildworker/worker/package_linux64/build/src/gf.c:2214 [inlined]
jl_apply_generic at /buildworker/worker/package_linux64/build/src/gf.c:2398
jl_apply at /buildworker/worker/package_linux64/build/src/julia.h:1690 [inlined]
do_apply at /buildworker/worker/package_linux64/build/src/builtins.c:655
jl_f__apply_latest at /buildworker/worker/package_linux64/build/src/builtins.c:705
#invokelatest#1 at ./essentials.jl:710 [inlined]
invokelatest at ./essentials.jl:709 [inlined]
run_main_repl at ./client.jl:383
exec_options at ./client.jl:313
_start at ./client.jl:506
jfptr__start_53898.clone_1 at /home/ec2-user/.asdf/installs/julia/1.5.3/lib/julia/sys.so (unknown line)
_jl_invoke at /buildworker/worker/package_linux64/build/src/gf.c:2214 [inlined]
jl_apply_generic at /buildworker/worker/package_linux64/build/src/gf.c:2398
jl_apply at /buildworker/worker/package_linux64/build/ui/../src/julia.h:1690 [inlined]
true_main at /buildworker/worker/package_linux64/build/ui/repl.c:106
main at /buildworker/worker/package_linux64/build/ui/repl.c:227
__libc_start_main at /lib64/libc.so.6 (unknown line)
_start at /home/ec2-user/.asdf/installs/julia/1.5.3/bin/julia (unknown line)
Allocations: 31191622 (Pool: 31182957; Big: 8665); GC: 34
zsh: illegal hardware instruction  julia --project=.

Duplicate of https://github.com/JuliaData/Arrow.jl/issues/74

(but thanks for the report! it's always helpful to hear of what people are running into)


Make a new release (0.7)

Hey folks, I think it's time we made a new release. Anyone feel inclined to take this on? If not, I can do it.
Any objections or blockers that anyone is aware of?

I think a proper resolution to #44 would be good, but that's also a nice to have and not a requirement.
I may be able to find some time to do a formal release this weekend.

If anyone is addressing #44, then pull request #46 could fit in that paradigm (as both are initialization problems).
I'm not sure what pull request #45 is waiting for - it adds a bit of Oracle functionality in production environments, and I'd like to see that in a release.

Just giving this a nudge since the current version in Debian 9 repositories has started to cause us some issues on a production server. Seems that at some point a nasty segfault with PostgreSQL databases was fixed and hasn't yet made it into a release in Debian. Would be nice if this could be resolved soon, thanks. :)

@kawaii I already upload a newer version 0.6 to Debian but it's only available in buster/sid
https://tracker.debian.org/pkg/lua-dbi

Given the bug-fixes we already have ready, I have tagged v0.7 in the repository.
If there are some ready PRs, all the more reason for a 0.8 soon :)

0.7 uploaded to Lua Rocks.
Besides the usual notification email to the Lua-L mailing list, anything else that we need/should do for a release? Or is it time to close this?

@sparked435 great, thanks!! Sorry, I missed the version number. Maybe we can tag 0.7.1 with just this fix. I recently had quite some issues debugging a problem with another Lua library and found I wasn't running the version it reported as :) (at least there is no 0.6.1 here).
Maybe we could add a release checklist in a RELEASE.md or something...


Fix add/removeEventListener for Chrome unstable

This fixes the Chrome unstable navigator.mediaDevices.addEventListener tests even though they only check that the function exists.
@alvestrand, @fippo Not sure about the log text, any ideas?
NOTE: I will update console.log to use whatever is decided in #74.
Fixes #73

The Firefox enumerateDevice test hang is annoying and it also confirms that the test timeout is 10 something minutes ;).


Arm  binary file: Exec format error

Hello,
I installed crowdsec on RPI3 by building. When I try to install cs-firewall-bouncer I get these errors with "make release" :
/bin/sh: 1: go: not found
CURRENT_GOVERSION=""
/bin/sh: 1: go: not found
REQUIRE_GOVERSION="1.13"
RESPECT_VERSION=""
/bin/sh: 1: go: not found
/bin/sh: 1: go: not found
go build -ldflags "-s -w -X github.com/crowdsecurity/cs-firewall-bouncer/pkg/version.Version="v0.0.7" -X github.com/crowdsecurity/cs-firewall-bouncer/pkg/version.BuildDate=2021-01-06_15:23:54 -X github.com/crowdsecurity/cs-firewall-bouncer/pkg/version.Tag="d065585f2b731f59d7be0e734a000df0f3376e6b" -X github.com/crowdsecurity/cs-firewall-bouncer/pkg/version.GoVersion=""" -o cs-firewall-bouncer -v
/bin/sh: 1: go: not found
/bin/sh: 1: go: not found
make: *** [Makefile:37: build] Error 127
thank you

Hello,
Sorry, I post to fast. I ran the command with the wrong user ( profil not configured with golang environement) :-(

Hello,
Sorry, I post to fast. I ran the command with the wrong user ( profil not configured with golang environement) :-(


ES5 legacy support

Fixes #7.

ES5+ rules in base.js.
ES6+ rules in index.js.
React-specific rules in react.js.

Have also added some fixtures that allow us to quickly test rules in an editor and/or using npm run lint.

This should probably be merged :)

:smile:

Looks good to me! I'll merge. :smiley:


Create .gitignore

Ignores files created automatically after installing and running the code.

Hi,
Do you know how the .egg-info folder is created? I remember seeing such a folder in my working directory, but I can't reproduce it for some reason.

According to Stack Overflow:
The .egg-info directories get only created if --single-version-externally-managed was used to install the egg. "Normally", installing an egg would create a single directory (or zip file), containing both the code and the metadata.

Running pip install -e . creates it.

Thanks :+1:


The dist package doesn't work as-is with RequireJS

I'm not sure if this is an issue with RequireJS or Webpack, but I stumbled upon it when trying to use the fuse.js file in dist with a project that was using RequireJS.  For some reason, the factory function defined in the Webpack boilerplate (define("Fuse", [], factory);) is never called by RJS, and therefore the module that's trying to require the Fuse module gets undefined instead.
Changing that line in the boilerplate to just define([], factory), creating an anonymous module, solves the issue.  I think changing umdNamedDefine: true to false in webpack.config.js would fix the issue, though I'm not sure what other ramifications that might have.

@fwextensions thanks a lot for the heads up. I just changed in the minified version. It works.


Register service provider?

Hello Laravel experts!
In our application, we use JWT authorization, and previously on laravel (not RR), we simpy use: https://github.com/tymondesigns/jwt-auth
But when we move to RR, we get some errors, like:
Auth driver [jwt] for guard [api] is not defined.

We fix this error moving \Tymon\JWTAuth\Providers\LaravelServiceProvider::class from app.php ( providers block ) to roadrunner.php ( reset_providers block), but, recently we noticed that this causes a memory leak. Even on Hello world responses, any ideas, how we can register it normally without memory leak?

Hi @koteezy!
Memory leaks on 3rd party packages must be detected and fixed on packages side. Another way - write your own service provider for required package and try to fix it by yourself.
A quick look at AbstractServiceProvider.php and LaravelServiceProvider.php shows that their uses a lot of $this->app->singleton(...) and maybe you should add all of it (or service provider class) into clear_instances section - maybe this can helps you.

@tarampampam clear_instances not works for me, but thanks anyway!
If in future someone will need fix, i simply create a service provider, and remove necessary lines, which caused a memory leak.

CustomJwtServiceProvider
<?php

namespace App\Providers\Auth;

use Tymon\JWTAuth\Providers\AbstractServiceProvider;

class CustomJwtServiceProvider extends AbstractServiceProvider
{
    /**
     * {@inheritdoc}
     */
    public function boot () {
        $this->aliasMiddleware();

        $this->extendAuthGuard();
    }

    public function register () {
        $this->registerAliases();

        $this->registerJWTProvider();
        $this->registerAuthProvider();
        $this->registerStorageProvider();
        $this->registerJWTBlacklist();

        $this->registerManager();
        $this->registerTokenParser();

        $this->registerJWT();
        $this->registerJWTAuth();
        $this->registerPayloadValidator();

        $this->registerClaimFactory();
        $this->registerPayloadFactory();
        $this->registerJWTCommand();
    }

    /**
     * {@inheritdoc}
     */
    protected function registerStorageProvider () {
        $this->app->singleton( 'tymon.jwt.provider.storage', function () {
            $instance = $this->getConfigInstance( 'providers.storage' );

            if ( method_exists( $instance, 'setLaravelVersion' ) ) {
                $instance->setLaravelVersion( $this->app->version() );
            }

            return $instance;
        } );
    }

    /**
     * Alias the middleware.
     *
     * @return void
     */
    protected function aliasMiddleware () {
        $router = $this->app[ 'router' ];

        $method = method_exists( $router, 'aliasMiddleware' ) ? 'aliasMiddleware' : 'middleware';

        foreach ( $this->middlewareAliases as $alias => $middleware ) {
            $router->$method( $alias, $middleware );
        }
    }
}

@ErriourRU Could you please test this solution?
Because of tymon/jwt-auth package looks abandoned and cannot be used with PHP 8 & fresh Laravel - I can't provide a custom listener for his state resetting, sorry for that :(

@tarampampam right now we are working on fork of this repository and trying to fix existing issuer
According to my tests, solution you stated is not sufficient, and some changes to library required. I created an issue on this and we will fix it soon


Prevent Rounding Error in Receipt

When fiat prices are converted to BTC, then converted to a different fiat price, it can result in a rounding error of 0.01 in the displayed total vs. the individual prices of the listing, options, coupons and shipping. This PR fixes that with the following changes:

subtract coupons before adding the shipping price
convert and round all prices to 2 decimal places before doing any calculations
if the quantity is more than 1, show a subtotal with the price for 1 listing after calculations
show the total with quantity for the multiple of the subtotal by the quantity

This PR also refactors the purchases view to move the creation of child views out of the render function, so refreshes are handled correctly.
Closes #660

Closed because I forgot to change the option to be combined with the listing price.


add coverage in readme

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
12805

Relevant Lines:
19265

💛  - Coveralls


less !! use normal function

Pull Request Test Coverage Report for Build 2239
Details

4 of 10 (40.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 90.929%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

result/result.mbt
3
9
33.33%

Totals

Change from base Build 2238:
-0.1%

Covered Lines:
3659

Relevant Lines:
4024

💛  - Coveralls


calculate BN on multi GPUs?

Hi, thanks for your great work. I have a question on BN calculation. In your code, BN is only calculated on a single GPU. What if I want calculate BN on multi GPUs to make the normalization step more accurate? Since it may help network converge better. Thanks.

BN is important. I think it should work better. But I don't have a good implementation of multi-gpu BN in tensorflow.

Thx


Fixed firewall in N-S scenario, Added nfp in place of nsf

RPM Reviewed it on a april 14 branch. Merging this.


Is this tool under active development?

First of all thank you for the awesome tool, it helps me a lot in my day to day.
I'm doubting if this repository is active and under active development.
I know it's difficult to maintain a project like this for the community without any kind of compensation.
I would like to offer help if you need it to maintain the project @wagoodman
It would be sad to see this tool get abandoned.

I haven't been able to get to this repo for a while. I have some ideas about the direction dive could go in, but haven't had the time to execute on it. Happy to chat further on getting some help 🙏👍

I've been doing some cleanup here, mostly dependencies: https://github.com/jauderho/dive . Feel free to pull/fork or I can submit a pull request.
Looks like the transition for gocui v0.6.0 to v1.x.x is going to require some changes documented here: https://github.com/awesome-gocui/gocui/blob/master/migrate-to-v1.md
Mostly, I wanted a build that merged #354

@jauderho is it possible for you to set up builds of your version in the meantime?

@voltagex This is already available here: https://hub.docker.com/r/jauderho/dive/tags

I haven't been able to get to this repo for a while. I have some ideas about the direction dive could go in, but haven't had the time to execute on it. Happy to chat further on getting some help 🙏👍

Just found out about this tool, and wanted to thank you for making it, it's amazing and really useful :)

Happy to chat further on getting some help

Would creating a gitter or a discord server help?
Just to hear out what could we do to help, to organize and divvy up work, since it looks like people are willing to help, based on the number of forks.

@jauderho Appreciate the effort. Are you also maintaining the brew recipe for your fork?

@mprimeaux I do not personally use brew. I just forked homebrew-dive but do not see anything that needs changing at this time.
As mentioned earlier, if you want to take a swing at updating the gocui support to use v1.x.x, that'd help keep dependencies up to date.

Maybe something can be done now to allow the project to survive test of time? I see lots of PRs and people that are able to produce PRs, we only need people that can review and merge those PRs that are valid.

https://github.com/wagoodman/dive/issues/553#issuecomment-2461854191


Add support for plotting points and drawing line segments in graphing mode

Hi,
I want to use windows calculator graphing mode as a replacement for other software such as GeoGebra Classic. However, the lack of features in windows calculator does not  permit me  to do so. Is it possible to add support for plotting points (eg: A = (x, y)), drawing all kinds of lines and line segments (eg: perpendicular lines, line segments, rays, etc), and drawing polygons (again, by choosing the vertices). All these features can be done in Geogebra Classic, which is slightly difficult to use. Would be nice if a native windows app could do this. For reference, this is the link to Geogebra Classic: https://www.geogebra.org/classic

@akhilesh-balaji Sorry, but I think this is a duplicate of #981.

@Rahul-Dixit Yeah, I'm so sorry. However, the line segment and polygon feature isn't there.

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

Thanks for your contribution, @akhilesh-balaji! I've updated #981 with some more details. Can you edit your top post to follow our new feature template? Since #981 is a prerequisite, we should reference it here and scope this issue to adding support for drawing line segments.

@grochocki I've just done that. Please take a look.


Bugfix: Clear default route Id from custom ensembler configs

This MR fixes a few minor bugs on the UI / SDK.
UI

ui/src/services/router/TuringRouter.js - When a router with No Ensembler / Standard Ensembler is edited and updated to use Custom Ensembler (docker / pyfunc), the default_route_id property from the previous configs should be dropped before calling the API. (We could drop this as soon as the type of the Ensembler is changed from the UI but we don't do this for other components too, because with that approach, if the user switched back to the old type in the same edit session, we would have lost the values.)
ui/src/services/ensembler/PyFuncEnsembler.js - Fix missing container config display for Pyfunc ensemblers. Since the detail views now use the parsed data, including the docker_config when parsing.

SDK
Under the hood, the Standard Ensembler's fallback_response_route_id and the No Ensembler's final_response_route_id both map to the default_route_id which will eventually be removed from the SDK. While it is being supported, we were previously not accounting for the idea that the user could directly update the default_route_id when Nop / Standard Ensemblers are in use (i.e., we were copying the ensembler configs to default_route_id on to_open_api() but would have lost the direct changes to the default_route_id). This is now overcome by letting the setter for default_route_id also update the ensembler configs. Then, upon to_open_api(), we only need to look at the ensembler's configs.
To facilitate this fix and to handle potential inconsistencies in the presence of RouterEnsemblerConfig vs one of the child classes, the setter for the ensembler now forces the configs to be of the child class types. This is the first step towards addressing this: https://github.com/gojek/turing/pull/197#discussion_r864489973

@terryyylim I fixed another small UI bug and updated the PR with tests. Could you take another look? Thanks!


COSE input missing for EXPECTEDVERIFY spec in common/2DCode/raw/CBO2.json

@nodh
in Common CBO2 this is the test spec:
"EXPECTEDVERIFY": false
EXPECTEDVERIFY: Data from input in COSE can be cryptographically verified,
with signer's certificate from TESTCTX.CERTIFICATE
But the test spec file does not contain a COSE input.

Thanks for spotting that, I'm gonna fix that

Reference: https://github.com/eu-digital-green-certificates/dgc-testdata/blob/main/README.md
Question 1: Which of the following interpretations are correct?

EXPECTEDDECODE: Data from input in CBOR can be decoded, and the contents match input from JSON
OR
EXPECTEDDECODE: Extract the CBOR content and validate the CBOR content against the RAW CBOR content field.

EXPECTEDVALIDJSON: Data from input (i.e. 2DCODE or PREFIX) can be decoded (whole chain), and the contents match input from JSON
OR
EXPECTEDVALIDJSON: Transform CBOR into JSON and validate against the RAW JSON content.
Question 2:
Should JSON payload inside of CBOR and COSE of test data contain full JSON Payload with Keys -260, 2, 4, 6 etc. See an image for illustration.

OR
Payload inside Key -260? See another image for illustration.

I believe, it should be earlier. However examples under common folder does not follow that. e.g.
https://github.com/eu-digital-green-certificates/dgc-testdata/blob/main/common/2DCode/raw/CO1.json

Question 1: Which of the following interpretations are correct?
EXPECTEDDECODE: Data from input in CBOR can be decoded, and the contents match input from JSON
OR
EXPECTEDDECODE: Extract the CBOR content and validate the CBOR content against the RAW CBOR content field.
EXPECTEDVALIDJSON: Data from input (i.e. 2DCODE or PREFIX) can be decoded (whole chain), and the contents match input from JSON
OR
EXPECTEDVALIDJSON: Transform CBOR into JSON and validate against the RAW JSON content.

In my opinion, in both cases the first interpretation.

Question 2:
Should JSON payload inside of CBOR and COSE of test data contain full JSON Payload with Keys -260, 2, 4, 6 etc. See an image for illustration.
OR
Payload inside Key -260? See another image for illustration

COSE should contain the whole COSE Object, i.e. with protected header, unprotected header, payload and signature. The payload contains a CWT that has the keys you mentioned (i.e. issuedAt, expiration, and -260).
CBOR should contain the DGC only, i.e. what is wrapped in 1 in -260 in the payload of the COSE.
This has been discussed in https://github.com/eu-digital-green-certificates/dgc-testdata/issues/18, too.


GWS.COMMONCONTROLS.11.2v0.3 does not detect setting inheritance

🐛 Summary
GWS.COMMONCONTROLS.11.2v0.3 does not detect setting inheritance (for both OUs and groups)
To reproduce

Follow https://github.com/cisagov/ScubaGoggles/blob/main/baselines/commoncontrols.md#gwscommoncontrols112v03-instructions. Ensure there is an event for the top-level OU
Make a child OU or a group non-compliant.
Click "Inherit" (or "Unset" for a group).
Run ScubaGoggles. The child OU or group will still show as non-compliant.

Expected behavior
The child OU / group to show as compliant if it inherits from its parent.
Any helpful log output or screenshots
N/A

This is moved to 10.5 (confirm) #487
#318

This is moved to 10.5
Related issue and PR: #487
#318
Can this be closed?

Moving to the control to a different policy group wouldn't resolve the underlying bug. Leave open until we test and confirm the issue is resolved. It's good to note the new number though, your comment should help whoever takes this issue.

This setting can be queried using the policy API, so this issue will be fixed in https://github.com/cisagov/ScubaGoggles/pull/499.


Compressed block headers & merkle proofs over low bandwidth communications

This issue by @willcl-ark was closed in the kyuupichan/eletrumx parent fork without explanation by the maintainer just before he declared that he would not support Bitcoin anymore.
Is there any interest in this idea here? For supporting low-bandwidth light clients this would be very useful.

I have written up an Electrum Protocol proposal which seeks to improve both:
(1) Reduce RPC bandwidth requirements (compressed block headers + protobuf/CBOR (de)serialisation)
(2) Reduce requirements of Clients making calls (removing block_height requirement)

I think the blockchain.transaction.get_merkle proposal (2) could be useful and it is a relatively small change anyway.
To make it even less intrusive, and to minimise my performance concern (https://github.com/kyuupichan/electrumx/issues/1007#issuecomment-632219596), the block_height param could be made optional: it would be used if passed (saving bitcoind RPC calls) but queried from bitcoind if absent (incurring higher DOS cost to the session).
If you contributed this change, I think we would definitely be interested in it!

Re (1), for Bitcoin, I am not really convinced that the savings are worth the complexity, and clearly it would be a huge change to the protocol. @JeremyRand, for example, is interested in it for Namecoin, where due to different header construction it might lead to huge savings I suppose. I take it that you yourself would want it for Bitcoin though... Have you done the math for the savings?
I am not saying we are against the change, but how much interest is there in this, and is someone willing to contribute the code?
Perhaps the two changes in (1) (change json encoding and compressed headers) should be considered separately.
I find it nice that the protocol is lightweight and hardly requires any dependency, re encoding change, introducing protobuf or something for CBOR would go against that. It's a tradeoff that should be considered.
OTOH, compressing the headers would be cheap and relatively easy to do but is that worth the savings while keeping the 2x overhead from hex as string?
Though I suppose header-compression could be introduced as an option.

Thanks for the feedback!
I am interested in (1) to support Electrum Bitcoin clients using a low-bandwidth (radio) transport where every byte counts.
I understand the concern about introducing dependencies/complexity and I would lean towards CBOR as a lighter weight binary alternative to JSON rather than protobufs.
Making the changes to remove block height for (2) is also intended to minimize bandwidth because it allows a low-bandwidth client to confirm a tx with a single call (assuming they have block headers sync'd). It would still be useful by itself even without (1) so that's a good suggestion for a place to start.
It looks like any alternative over-the-wire encoding would have to be introduced at the aiorpcX layer and an issue there already captures this idea.

Re (1), for Bitcoin, I am not really convinced that the savings are worth the complexity, and clearly it would be a huge change to the protocol. @JeremyRand, for example, is interested in it for Namecoin, where due to different header construction it might lead to huge savings I suppose. I take it that you yourself would want it for Bitcoin though... Have you done the math for the savings?

@SomberNight So, I think there are two different factors: motivation, and percent savings.
In terms of motivation, Namecoin may be more highly motivated than Bitcoin to save bandwidth, because of the very stringent performance requirements that Tor Browser imposes (i.e. it needs to fully sync from scratch by the time the user finishes typing in a URL after opening Tor Browser) as well as the fact that Namecoin headers are larger than Bitcoin headers.  However, in terms of percent savings in bandwidth, application-layer compressed headers are not going to be as effective in Namecoin as in Bitcoin, because the bulk of Namecoin headers consist of Bitcoin coinbase transactions, which aren't subject to application-layer compression like Bitcoin headers are.  (CBOR encoding and DEFLATE compression will probably have comparable percent savings between Namecoin and Bitcoin, of course.)

I am not saying we are against the change, but how much interest is there in this, and is someone willing to contribute the code?

Namecoin is potentially willing to contribute the code for CBOR and DEFLATE (looks like NLnet may fund us to work on it, probably within the next 6 months).  Note that this is mainly a change in aiorpcx, not ElectrumX.  We do not currently have funding for application-layer compressed headers (which would be an ElectrumX + Electrum patch), so I'm not sure when we would get to that, but if we end up with funding for it, we would be happy to implement it.

(2) Reduce requirements of Clients making calls (removing block_height requirement)

I think the blockchain.transaction.get_merkle proposal (2) could be useful and it is a relatively small change anyway.

Note: I am working on substantial db changes that will give us this change for free. (well, a single LevelDB.get() compared to previously needing a bitcoind RPC + fs reads by bitcoind)
I will include this change in a new protocol version when I am done, which will include other stuff too.


"WAN address" in port forwarding includes VIP addressess.

Hi,
If I use "WAN address" when creating a Port forward, it forwards the port on the "WAN address" AND all VIP's on that interface. If you want to only forward to the WAN IP you need to create an extra VIP alias containing the WAN IP.
Best regards,
Maarten
OPNsense 18.1.9-amd64
FreeBSD 11.1-RELEASE-p10
OpenSSL 1.0.2o 27 Mar 2018

Could probably be fixed like https://github.com/opnsense/core/commit/d823cc71937ff20c1295c8c2dc804cdc7f6419d9 "interface address" converts to "interface" now where it could be "interface:0".

Easy enough to apply via patch, let's keep this away from 18.1.x and make it the default again in 18.7 👍

Decided to revert, need to solve this another way as :0 interferes with IPv6 connectivity.

It would be very nice to have a fix to this: a customer of us just noticed this problem and asked for a solution. In the mean time, we trained them to always put the primary IP address of the WAN interface in the rule, but actually this might not be always feasible: for example, when the WAN is configured as PPPoE or DHCP client.
Thanks for your efforts!

@AdSchellevis keep or close?

@fichtner let's close it, if at some point in time :0 starts working like it should, we can always reopen.

Why would you close an issue which is not fixed yet? Doesn't make sense to me.

There's no easy way out here and the first attempt to correct this was problematic within pf(4) code. Now not enough community feedback to work with. We close it according to our contribution rules.
https://github.com/opnsense/core/blob/master/CONTRIBUTING.md

The revert decision in question is about lax handling of :0 in IPv6. We did add a patch eventually via https://github.com/opnsense/changelog/blob/da9944d43c1fe4466cab2e624727b1ad5f256ca9/community/20.7/20.7.2#L43 but since there are possibilities for primary address to be link-local only on an IPv6 WAN the use of :0 will silently fail.
The best way is likely to add another shortcut that supports single GUA support as an alternative here and leave the existing one as is maybe minus a tweak of the current label.

Having just apparently trodden on this rake, could the incorrect wording of "WAN address" in the NAT rule builder at least be replaced with something clearly indicating "All IPs bound to WAN interface" (which, honestly, I do not think many people will see as the expected/desirable behaviour), or for the rule "WAN address" to actually make a NAT rule for the specific IP address bound to that interface?
If it is possible for me to manually specify the WAN IP as the DST-NAT destination IP, I do not understand why the "WAN address" behaviour is not the same?


Thanks, for your attention of this discussion.

Thanks, for your attention of this discussion.
If you need the quick draw badges, please conform the following link.
https://github.com/orgs/community/discussions/20645
Best regards!
Originally posted by @PurpleMonkey729 in https://github.com/PurpleMonkey729/GitHub-Profile-Achievement-Badge/discussions/1#discussioncomment-6332277

Well, I think you get the constant reply. Thanks.
I will close this issue.

Closed


Not Usable on windows (ext-pcntl is not available on  windows platform)

composer require aaronfrancis/solo --dev
Cannot use aaronfrancis/solo's latest version v0.1.2 as it requires ext-pcntl * which is missing from your platform.
In PackageDiscoveryTrait.php line 325:
Package aaronfrancis/solo has requirements incompatible with your PHP version, PHP extensions and Composer version
:
- aaronfrancis/solo v0.1.2 requires ext-pcntl * but it is not present.
require [--dev] [--dry-run] [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--fixed] [--no-suggest] [--no-progress] [--no-update] [--no-install] [--no-audit] [--audit-format AUDIT-FORMAT] [--update-no-dev] [-w|--update-with-dependencies] [-W|--update-with-all-dependencies] [--with-dependencies] [--with-all-dependencies] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [-m|--minimal-changes] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--apcu-autoloader-prefix APCU-AUTOLOADER-PREFIX] [--] [...]

Yes, laravel pail is also not compatible on UNIX environments, and therefore Windows operating systems, due to the pcntl extension.

Even if we install with ignoring platform dependencies, it returns this error when trying to run

Yes, Windows users we are lag behind.

It's very likely that pcntl will never be supported on Windows. So you'd have to be using it inside of WSL, a Linux Docker container, or some other virtualisation

Hmmm maybe I need to note that this is not usable on Windows. Because yes, it require pctnl. Sorry about that!


Generate Color Palette

We have theme colors for d2p, but only core colors, no shades for hover effects, borders, etc.
https://gka.github.io/palettes
Is a great tool for generating these automatically. Lunar takes in a range from 0-6, where 3 is the core color. This can all be configured in setTheme.

Removed colors.js because it wasn't used, but here they are for this
export const d2tpBlue = '#3A4EA1'
export const d2tpRed = '#EF4927'
export const d2tpBlack = '#231F20'
export const d2tpGreen = '#00B36B'
export const d2tpPink = '#FF99AC'


Please change lowercase to uppercase, it says duplicate wallet

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

I'm getting a new error now :
Not eligible for automerge (click details for more information)
found modified asset file assets/mainnet/CcaKx6adqp8wDeksiR15x8HMgBzjz8QY6pJCmRZQPXAB/Hay.png - only new assets are allowed


Support for Cooler Master Masterkeys Pro L White & Masterkeys Pro M White

FYI: I just tested the SDK provided by Cooler Master,they use the R(red) to determine the brightness of white LEDs

And I don't know if it is a bug or not .Aurora can't detect my Masterkeys Pro L White,it writes Not Initialized at config page.
My keyboard LEDs can respond the Example provided by Cooler Master SDK,but not in Aurora

@snichola Can you help?
Do you have 64 bit sdk installed? Aurora uses 64 bit.

I'm working on it,will done soon

I believe they are working in any of the recent versions


Why not use flet to do？

I'm just curious.

What do you mean?

I mean, why not use flet to build this website?

Because Flet is better suited for web apps, not websites (faster initial load, all text selectable, SEO, etc.).


Rake tasks to import CSV files and sync with Rummager

Currently, recommended links are administered via the recommended-links scripts using CSV files. The first commit adds a rake task to search-admin (which provides a UI for administering recommended links as of https://github.com/alphagov/search-admin/pull/48) to import the existing CSV files and thereby sync the search-admin database with the content in Elasticsearch. The second commit adds a rake task to search-admin to send all recommended links to Rummager.
Trello: https://trello.com/c/WY4JGxKG/39-manage-external-recommended-links-in-search-admin
Follow-up to: https://github.com/alphagov/search-admin/pull/48
Depends on: https://github.com/alphagov/search-admin/pull/50
Paired with @MatMoore

I've rebased this on top of the latest code and addressed previous comments.
I turned RummagerLinkSynchronize into a module and just kept the class methods since there wasn't much benefit to instantiating it.
ElasticSearchRecommendedLink now uses a private reader for recommended_link rather than referring to attributes directly.

:shipit:


What renderer does this use?

Heya! First of all, really nice job, this is the only way I can run studio - grapejuice nor vinegar work for me
However, it's a bit unstable (flickering when resizing windows, when I tried to open a big map, it all crashed and never could open again, had to delete all associated data with it and reinstall)
I'm wondering if this instability could be improved by changing the renderer, perhaps if it's using opengl we could use DX11 with DXVK (i saw that dxvk was marked as an enhancement earlier, so that'd be quite far off)?
Also is there a config file to modify? I'm using the flatpak so the location of it would be much appreciated, thanks!

Oh, I think it's crashing whenever I try and open a cloud project which is interesting

By default, Cork uses whatever Wine provides, in most cases it's WineD3D, but since in the Flatpak version we are using Proton GE, it's using DXVK. Also the settings file for the Flatpak version is in ~/.var/app/io.github.CorkHQ.Corky/config

I see, thank you


[HUDI-8214] Support specify partitions with regex for compaction

support specify partitions with regex for compaction

Change Logs
Describe context and summary for this change. Highlight if any code was copied.

support specify partitions with regex for compaction

Impact
Describe any public API or user-facing feature change or any performance impact.
none
Risk level (write none, low medium or high below)
low
If medium or high, explain what verification was done to mitigate the risks.
Documentation Update
none
Describe any necessary documentation update if there is any new feature, config, or user-facing change. If not, put "none".

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[x] Read through contributor's guide
[x] Change Logs and Impact were stated clearly
[x] Adequate tests were added if applicable
[x] CI passed

@danny0405 Hi, Danny, please have a look~ Thanks!


feat: extend project to run as maven plugin

Reference: #892
This PR extends the project to be used as a maven plugin. I have added two goals to the maven plugin, mine and repair. However, only a few options are available at the moment. The main objective right now is to release a maven plugin that is used in the demo at EclipseCon 2022.
Design Philosophy

We do not want to duplicate the command line spec for both sub-commands. This is to ensure that the CLI and maven plugin behaves exactly the same.

There will be a slight change in how the parameters are passed. The parameter that follows the -D option in maven cannot be in kebab-case. I did not find an article citing this, but the code is not working if I do so. For example, -Dhandled-rules won't be post-processed by the plugin so we need to pass -DhandledRules

We do not want to introduce any breaking changes. The CLI should continue working as before.

Usage of new feature
Before using the plugin, you need to install the plugin locally. Follow these steps to set it up:

Have mavenv3.8.6. The repair command does not work on different versions.
Run mvn install -DskipUnitTests -DskipIntegrationTests.

mine goal
mvn se.kth.castor:sorald:0.6.1-SNAPSHOT:mine [-DhandledRules]

Run this on any maven project and you should get a list of mined violations. -DhandledRules is optional and it works exactly how it is written here.
repair goal
mvn se.kth.castor:sorald:0.6.1-SNAPSHOT:repair -DruleKey=<>

The ruleKey parameter is required here and again, see its input here . This should also run on any maven project and produce repairs or does nothing if there are no violations found.
ToDo

[ ] Make the CI pass on Windows and MacOS. The plugin works locally on Windows though.
[ ] Try that repair goal works with 3.6.3 as well because I assume this version is used by a majority of people since it is shipped by apt package manager.
[ ] Update documentation

@khaes-kth I have updated the details about the new feature in the description. Please check it out.

The tests finally work on Windows and macOS as well. :relieved: Time to update the documentation.

@khaes-kth @monperrus
Please try out sorald maven-plugin and drop your reviews.
Summary of changes

I have managed to extend the Sorald to be used as a maven-plugin. My goal is to make it as analogous as possible to the CLI. Hence, two goals are added - repair and mine. See "Usage of new feature" in the PR description.
We also have integration tests now, thanks @cesarsotovalero for the guidance here. -DskipTests has been split into two parameters now -DskipUnitTests and -DskipIntegrationTests. Keep in mind that the integration tests are triggered in much fewer phases than the unit tests so you may not need to pass -DskipIntegrationTests most of the time. You can see how it used in the updated workflow.

Since we are not meeting this week, I will attach demos of the respective goals.
mine.webm
repair.webm

[ERROR]

Some dependencies of Maven Plugins are expected to be in provided scope.
Please make sure that dependencies listed below declared in POM
have set '<scope>provided</scope>' as well.

The following dependencies are in wrong scope:
 * org.apache.maven:maven-plugin-api:jar:3.8.6:compile
 * org.apache.maven:maven-model:jar:3.8.6:compile
 * org.apache.maven:maven-artifact:jar:3.8.6:compile

Investigate why this "error" is logged while building the maven plugin.


Move DataDog Dashboards to Terraform

Value Statement
When we created dashboards in #159, we decided to use the DataDog UI. This card includes the work to move the dashboard metrics (statsd for now, but maybe more by the time this card is implemented?) to terraform inside our notification-api repo.
Acceptance Criteria
GIVEN
WHEN
THEN
Checklist

[ ] Checklist item here

Assumptions

Additional Info/Resources

Terraform DataDog Provider overview

Out of Scope

Open Questions

Duplicate to #134


Roadmap to v1.0

To-do list
Here's what we want to achieve for version v1.0:

[ ] RateSystem: finalize a convenient struct for easily implementing time-dependent forcing in a given dynamical system, such as parameter ramping
[ ] r-tipping tools: add a few basic tools for analyzing RateSystems in the context of rate-induced tipping
[ ] Output types: Streamline the output of functions (specifically transitions) by creating custom types
[ ] Jacobian: add the option to specify a hard-coded Jacobian in the StochSystem (and RateSystem) structs
[ ] Quasipotential calculation: write a function that performs the ordered line integral method (OLIM) (#34)
[ ] langevin_mcmc: improve performance and enhance symbolic capabilities
[ ] Noise function: Find out how to best design the StochSystem struct in terms of the noise function sys.g, the covariance matrix sys.Σ and allowing for different noise processes
[ ] Lévy noise: add to the list of possible noise processes
[ ] sgMAM: implement simple gMAM
[ ] gMAM performance: solve the bottleneck issue of reinterpolating the path between optimization steps (#23 #33)
[ ] Wrappers: remove superfluous wrapper functions to functions in DynamicalSystems however add them as examples in the documentation.

More general points:

[ ] Performance: identify slow functions and code them more efficiently
[ ] Symbolic features: add symbolic capabilities to the suite of functions
[ ] Tests: Have propper tests (#37)
[ ] Steamline export #43
Please comment and expand on this list!

I added some comment and linked to relevant issue and PRs