[vcpkg][gdal] Switch build method to vcpkg_nmake(win)/vcpkg_make(unix)

This PR will:

[x] Update to 3.1.2
[x] Add new option BUILD_TARGET to vcpkg_*_nmake to select target.
[x] Add new option MAKEFILE to vcpkg_build_make to select the makefile.
[x] Add new vcpkg function vcpkg_use_system_ports to use configure's option to handle vcpkg installed ports.
[x] Switch gdal build method to vcpkg_*_nmake (Windows) / vcpkg_*_make (UNIX).
[x] Fix linux build.

Related: #9068.

@Neumann-A This PR should fix your issue. Can you review it?
Thanks.

@Neumann-A You are right, I found that almost all features were broken. Mostly because the dependent libraries were not added to the test case.

@JackBoosY You should probably ask @lakinwecker to check this PR.
I'm not using gdal. I was just trying to solve a problem which was discussed in the slack channel and then discovered that gdal on linux is totally broken and made an issue out of it.

@Neumann-A In the end, I found that the order of ports in gdal configure/configure.ac is incorrect. We can only solve these configuration problems by adding -l$ {lib}.

Current status:
  Installation directory:    /home/usr/work/9100/vcpkg/packages/gdal_x64-linux/debug
  C compiler:                gcc -DHAVE_AVX_AT_COMPILE_TIME -DHAVE_SSSE3_AT_COMPILE_TIME -DHAVE_SSE_AT_COMPILE_TIME  -g -DDEBUG -ftrapv
  C++ compiler:              g++ -DHAVE_AVX_AT_COMPILE_TIME -DHAVE_SSSE3_AT_COMPILE_TIME -DHAVE_SSE_AT_COMPILE_TIME  -g -DDEBUG -ftrapv
  C++14 support:             no

  LIBTOOL support:           yes

  LIBZ support:              external
  LIBLZMA support:           yes
  ZSTD support:              yes
  cryptopp support:          no
  crypto/openssl support:    yes
  GRASS support:             no
  CFITSIO support:           no
  PCRaster support:          internal
  LIBPNG support:            external
  DDS support:               no
  GTA support:               no
  LIBTIFF support:           external (BigTIFF=no)
  LIBGEOTIFF support:        internal
  LIBJPEG support:           internal
  12 bit JPEG:               no
  12 bit JPEG-in-TIFF:       no
  LIBGIF support:            external
  JPEG-Lossless/CharLS:      no
  OGDI support:              no
  HDF4 support:              no
  HDF5 support:              yes
  Kea support:               no
  NetCDF support:            yes
  NetCDF has netcdf_mem.h:   yes
  Kakadu support:            no
  JasPer support:            no
  OpenJPEG support:          yes
  ECW support:               no
  MrSID support:             no
  MrSID/MG4 Lidar support:   no
  JP2Lura support:           no
  MSG support:               no
  GRIB support:              yes
  EPSILON support:           no
  WebP support:              yes
  cURL support (wms/wcs/...):yes
  PostgreSQL support:        no
  MRF support:               yes
  LERC support:              yes
  MySQL support:             yes
  Ingres support:            no
  Xerces-C support:          yes
  NAS support:               yes
  Expat support:             yes
  libxml2 support:           yes
  Google libkml support:     no
  ODBC support:              yes
  PGeo support:              yes
  FGDB support:              no
  MDB support:               no
  PCIDSK support:            internal
  OCI support:               no
  GEORASTER support:         no
  SDE support:               no
  Rasdaman support:          no
  DODS support:              no
  SQLite support:            yes
  PCRE support:              yes
  SpatiaLite support:        yes
  RasterLite2 support:       no
  Teigha (DWG and DGNv8):    no
  INFORMIX DataBlade support:no
  GEOS support:              yes
  SFCGAL support:            no
  QHull support:             internal
  Poppler support:           no
  Podofo support:            no
  PDFium support:            no
  OpenCL support:            no
  Armadillo support:         no
  FreeXL support:            no
  SOSI support:              no
  MongoDB support:           no
  HDFS support:              no
  userfaultfd support:       yes

  SWIG Bindings:             no

  Statically link PROJ:      yes
  enable GNM building:       yes
  enable pthread support:    yes
  enable POSIX iconv support:yes
  hide internal symbols:     no

The CI system did not really test gdal, we need to fix it before merging this PR.

  LIBGEOTIFF support:        internal
  LIBJPEG support:           internal
  QHull support:             internal

shouldn't those be external? (If I understand external correctly)
It also looks like some of those dependencies could potentially screw up CI results (if there is a port depending on gdal)
like
  Armadillo support:         no
  MongoDB support:           no
  PostgreSQL support:        no

@Neumann-A Because these 6 ports are not added as functions. This PR only fixes existing features.

liblzma and libjpeg-turbo are failing for Linux, that causes tiff and gdal to be skipped by CI.

Hey @JackBoosY. We like vcpkg_use_system_port, but @vicroms and I are thinking about whether it can be merged into vcpkg_check_features with a flag. We'll take this on and ping you when we've got something for you to see!

Explanation of common autoconf-style arguments: https://autotools.io/autoconf/arguments.html
It looks like "enable" is typically paired with "disable" and "with" is paired with "without".

@ras0219-msft According to the documentation, with should be paired with without, but in general, the judgment in configure.ac is:
elif test "$with_libgrass" = "no" ; then

or
if test "$with_pcidsk" != "no" ; then

@JackBoosY gdal[core] (commit cb7d59e Add feature options) works for me on x64-windows and x64-linux with small changes:
diff --git a/ports/gdal/portfile.cmake b/ports/gdal/portfile.cmake
index 34af0075b..1b938ffd7 100644
--- a/ports/gdal/portfile.cmake
+++ b/ports/gdal/portfile.cmake
@@ -119,6 +119,7 @@ if (VCPKG_TARGET_IS_WINDOWS)
         HTMLDIR=${NATIVE_HTML_DIR}
         GEOS_DIR=${COMMON_INCLUDE_DIR}
         "GEOS_CFLAGS=-I${COMMON_INCLUDE_DIR} -DHAVE_GEOS"
+        "PROJ_FLAGS=-DPROJ_STATIC -DPROJ_VERSION=5"
         PROJ_INCLUDE=-I${COMMON_INCLUDE_DIR}
         EXPAT_DIR=${COMMON_INCLUDE_DIR}
         EXPAT_INCLUDE=-I${COMMON_INCLUDE_DIR}
@@ -188,7 +189,7 @@ if (VCPKG_TARGET_IS_WINDOWS)
         OPTIONS_RELEASE ${NMAKE_OPTIONS_REL}
     )

-    if (CMAKE_BUILD_TYPE STREQUAL debug)
+    if (VCPKG_BUILD_TYPE STREQUAL debug)
         set(GDAL_OBJ_DIR ${CURRENT_BUILDTREES_DIR}/${TARGET_TRIPLET}-dbg)
     else()
         set(GDAL_OBJ_DIR ${CURRENT_BUILDTREES_DIR}/${TARGET_TRIPLET}-rel)
@@ -281,7 +282,12 @@ else()
         SOURCE_PATH ${SOURCE_PATH}
         AUTOCONFIG
         OPTIONS ${EXTRA_OPTIONS}
+            --with-jpeg=${CURRENT_INSTALLED_DIR}
+            --with-qhull=no
             --with-proj5-api=yes
+            --with-hide-internal-symbols=yes
+            --with-rename-internal-libgeotiff-symbols=yes
+            --with-rename-internal-shapelib-symbols=yes
             --enable-shared=${BUILD_DYNAMIC}
             --enable-static=${BUILD_STATIC}
         OPTIONS_DEBUG
@@ -303,11 +309,14 @@ else()

     file(GLOB GDAL_TOOLS ${CURRENT_PACKAGES_DIR}/bin/*)
     foreach (GDAL_TOOL ${GDAL_TOOLS})
-        file(INSTALL ${GDAL_TOOL} DESTINATION ${CURRENT_PACKAGES_DIR}/tools/gdal)
+        file(INSTALL ${GDAL_TOOL} DESTINATION ${CURRENT_PACKAGES_DIR}/tools/gdal
+                PERMISSIONS OWNER_READ OWNER_WRITE OWNER_EXECUTE GROUP_READ GROUP_WRITE GROUP_EXECUTE WORLD_READ)
         file(REMOVE ${GDAL_TOOL})
     endforeach()
     file(REMOVE_RECURSE ${CURRENT_PACKAGES_DIR}/bin)
 endif()

+configure_file(${CMAKE_CURRENT_LIST_DIR}/vcpkg-cmake-wrapper.cmake ${CURRENT_PACKAGES_DIR}/share/${PORT}/vcpkg-cmake-wrapper.cmake @ONLY)
+
 # Handle copyright

and help in vcpkg-cmake-wrapper.cmake for static linking:
_find_package(${ARGS})

if(TARGET GDAL::GDAL AND "@VCPKG_LIBRARY_LINKAGE@" STREQUAL "static")
	find_package(PROJ4 REQUIRED)
	find_package(PNG REQUIRED)
	find_library(GDAL_GEOS_LIB NAMES geos)
	find_library(GDAL_GEOSC_LIB NAMES geos_c)
	message(STATUS "GDAL_GEOS: ${GDAL_GEOS_LIB} ${GDAL_GEOSC_LIB}")
	find_package(WebP REQUIRED)
	find_package(sqlite3 CONFIG REQUIRED)
	find_package(EXPAT REQUIRED)
	find_package(OpenJPEG CONFIG REQUIRED)
	find_package(netCDF REQUIRED)
	find_package(HDF5 CONFIG REQUIRED)
	find_package(SZIP REQUIRED)
	find_package(JPEG REQUIRED)
	find_package(TIFF REQUIRED)
	find_package(Threads)
	find_package(CURL CONFIG REQUIRED)
	find_package(OpenSSL REQUIRED)
	find_package(LibXml2 REQUIRED)
	find_package(ZLIB REQUIRED)
	find_package(LibLZMA CONFIG REQUIRED)

	set_property(TARGET GDAL::GDAL APPEND PROPERTY INTERFACE_LINK_LIBRARIES
		PROJ4::proj
		PNG::PNG
		${GDAL_GEOS_LIB} ${GDAL_GEOSC_LIB}
		WebP::webp
		sqlite3
		EXPAT::EXPAT
		openjp2
		netcdf
		hdf5::hdf5_hl-static hdf5::hdf5-static
		szip-static
		JPEG::JPEG
		TIFF::TIFF
		Threads::Threads
		${CMAKE_DL_LIBS}
		CURL::libcurl
		OpenSSL::SSL OpenSSL::Crypto
		LibXml2::LibXml2
		ZLIB::ZLIB
		LibLZMA::LibLZMA
	)
endif()

Here additional features omitted, libgeotiff - internal renamed, jpeg - external, qhull - disabled (all just for quick test).
Also I have a pretty clean Linux, with minimum -dev packages. I think it is a problem that configure can pick up "system" libraries, so maybe it is preferable to have exhaustive options list for configure that mimics configure --help (all would be explicit and easy to check that nothing is missing). For example gdal has -with-kea=ARG      Include kealib (ARG=path to kea-config) [default=yes], so now you can easily end up with misterious kea.

@JackBoosY small typo fix
diff --git a/ports/gdal/portfile.cmake b/ports/gdal/portfile.cmake
index 1b938ffd7..c101cd235 100644
--- a/ports/gdal/portfile.cmake
+++ b/ports/gdal/portfile.cmake
@@ -27,8 +27,8 @@ vcpkg_extract_source_archive_ex(
 )

 if (VCPKG_TARGET_IS_WINDOWS)
-    set(NATIVE_PACKAGES_DIR_DBG "${CURRENT_PACKAGES_DIR}")
-    set(NATIVE_PACKAGES_DIR_REL "${CURRENT_PACKAGES_DIR}/debug")
+    set(NATIVE_PACKAGES_DIR_REL "${CURRENT_PACKAGES_DIR}")
+    set(NATIVE_PACKAGES_DIR_DBG "${CURRENT_PACKAGES_DIR}/debug")
     # We can't pass in the normal absolute path because the "xcopy" command needs to use the windows path.
     # We also can't pass in the windows path because it is used as an argument after the "\" will be used as an escape character and cannot be resolved using double quotes.
     # Use relative path here to install manually below

/azp run

/azp run

/azp run

This is too hard for me, close it temporary.


⚠ Fortnite has degraded performance

In 299ebd9, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1338 ms

Resolved: Fortnite performance has improved in 4b2d124.


Catch and log fetching errors

What it solves
Resolves #2327.
Some network errors weren't caught.
How this PR fixes it
Adds a try-catch for possible exceptions when fetching the safe info, balances, history, collectibles etc
These errors are just logged to the console to not flood Sentry.
I've also added Code in front of the error messages so that it's easier to search for them.
@fernandomg I've deleted allSettled, sorry 😅
How to test it

Disable network and wait
It will attempt to fetch the safe info but fail
Observe the new error messages in the console (see the screenshot below)
None of the functionality should be affected

Any extra information

Looks good to me,
checked in the rinkeby and mainnet build. Had the errors 601 to 605 as described

Regarding the removed block, #2420 (comment), I think that leads to the infinite loading icon in the history tab.

Good catch, thanks @fernandomg!
I missed one place where it wasn't caught.


[Support] How can I deploy to Heroku?

Hello all,
I've followed most guides available to deploy a Backpack app to heroku, but so far I've not being able to load the CSS/JS files from the public/vendor folder. My procfile is the following:
web: vendor/bin/heroku-php-apache2 public/
I already have both nodejs and php buildpacks in Heroku, but I don't know what else should I be doing to get this done. I checked manually using heroku bash and in the public folder I don't have any vendor directory.
I would really appreciate if you can help me with this!

Hi @NicolasBonet ,
Sorry, don't have enough experience in using Heroku - only used it once 2-3 years ago. Maybe someone else in the community does.
Cheers!
P.S. I am, however, very interested in having a "deploy to heroku" button for Backpack\Demo, so maybe if you figure it out you might want to help with that?

The procfile should work. From what I can gather, it's the missing vendor folder.
What's the package that is using it? elfinder is under the packages folder.
@NicolasBonet, are there any routes under public being defined in Backpack? I don't remember any.

You guys can close this now, the problem was simply that the vendor folder wasn't generated with Heroku directly, so I simply had to generate it in my local environment and then push the changes to Heroku with a little modification to the .gitignore I had.
About the button, I never used one before, but I do can share how I did it (which was quite simple actually!) if it helps 👍


Implement suggestions after crate usage in rust-elements

Recently @apoelstra attempted to use this crate in rust-elemements, a few things came out in the wash (https://github.com/rust-bitcoin/hex-conservative/pull/15#issuecomment-1613578223)

Patch 1: Rename FromHex associated error type to Err.
Patch 2: Attempt to improve docs around formatting hex using the DisplayHex trait.
Patch 3: Add debug derive to the hexy example struct

Deriving Debug in an example doesn't change anything about the API. The problem is that DisplayByteSlice and DisplayArray don't implement Debug or Display.
In general DisplayHex::Display should have Debug and Display bounds, and have documentation indicating that both of these should be equivalent to LowerHex.

Deriving Debug in an example doesn't change anything about the API. The problem is that DisplayByteSlice and DisplayArray don't implement Debug or Display.

Excuse the changes I made yesterday, I was confused.

In general DisplayHex::Display should have Debug and Display bounds, and have documentation indicating that both of these should be equivalent to LowerHex.

I think that is counter to the objective of the DisplayHex trait
/// Types that have a single, obvious text representation being hex should **not** implement this
/// trait and simply implement `Display` instead.

I think that is counter to the objective of the DisplayHex trait

Surely DisplayBytesSlice and DisplayArray have a "single, obvious text representation"?

Ok, I spent literally hours on this crate today. FTR this code is way too complicated for such a trivial task as converting bytes to/from hex. Anyway, whinge over. I'll push a few PRs with what I came up with.

I think this can be closed now, nothing here needs action still.


Deprecate prepareBeaconProposer, consolidate on registerValidator.

I truly believe prepareBeaconProposer is strictly more cumbersome than registerValidator.

It's vulnerable to attack
Validator Clients have inherent knowledge of the private keys of their attached Validators, but not the indices, so the first thing many of them do is request, by public key, the index of each associated validator. This can lead to problems at worst, but even with the kinks get ironed out, it represents unnecessary overhead during validator client startup.

Now that builder_boost_factor is present, control over whether to use a builder block or a paired node block is satisfied at the time produceBlockV3 is called, and consolidating prepareBeaconProposer and registerValidator will not leave the BN wondering which block to return to each attached validator client.

As the author of that blog post about the attack, it's not something I would be worried about and if anything I'd consider it a feature. A validator should not be using a public beacon node to perform its duties as that means it isn't actually validating the chain (it's just trusting the public node provider).
Otherwise I haven't thought enough about the proposed change to say if it's a good idea or not - just wanted to clarify that this isn't required to fix an actual security issue.

Registering validators registers all validators known by the validator client and is a pass-through to relays, whereas prepare proposer is meant to be limited to just those validators that are scheduled to propose within the next epoch and more focused on local block production.
There is an argument for using public key rather than index in the registration, although index is used in a number of other places in the API so it isn't a unique requirement for this endpoint.  But I think some sort of fast-path notification to the beacon node that the validator client has a validator that is expecting to request a block in the near future is still useful, as it avoids the beacon node having to wade through potentially tens of thousands of registrations to see if one of them is scheduled to propose (although client teams can weigh in here if they think that the overhead isn't relevant).

Now that https://github.com/ethereum/beacon-APIs/pull/386 is present, control over whether to use a builder block or a paired node block is satisfied at the time produceBlockV3 is called, and consolidating prepareBeaconProposer and registerValidator will not leave the BN wondering which block to return to each attached validator client.

Note that local payload generation is usually started ahead of the proposing slot, to allow the execution node a chance to build a good payload and provide same when requested with minimal delay.  And the underlying code will usually (outside of specific values of the boost factor) talk to both relays and execution node for payloads simultaneously, so I don't think that this point is relevant for what is being discussed.

As the author of that blog post about the attack, it's not something I would be worried about and if anything I'd consider it a feature. A validator should not be using a public beacon node to perform its duties as that means it isn't actually validating the chain (it's just trusting the public node provider).

Hi Adrian, I have been wondering when we'd run into each other. I reference your blog post often.
Evaluating it as a feature, it also fails the sniff test in my opinion. The trust assumption with a public beacon node with prepareBeaconProposer is that not only are the maintainers benevolent but that so is every single other participant- but this can easily be reduced by the maintainers to eliminate the need to trust all the other participants. I helped build such a public beacon node.. Further, most "public beacon nodes" are public by accident- node operators spin up a VPS or baremetal and use docker to manage their clients and ufw to secure the node, but the iptables entries for each bypass one another. A quick search on shodan shows thousands of nodes with unsecured API ports.
So, it doesn't accomplish the prevention of public beacon nodes, and it also hurts less-than-professional node operators. Requiring a signature from the validator would at least protect the latter group.
Proof of custody, if well implemented, will resolve the public beacon node problem. prepareBeaconProposer is largely irrelevant at this point.

Registering validators registers all validators known by the validator client and is a pass-through to relays, whereas prepare proposer is meant to be limited to just those validators that are scheduled to propose within the next epoch and more focused on local block production.

Interesting, if this is the original intent. I have observed every single client send prepareBeaconProposer and registerValidator with the same vector sizes at the same cadence. I have graphs, if needed, to back this up.
Since both are called with every attached validator, every epoch (generally), it doesn't make sense to me that they can't serve the same purpose.

I don't think that this point is relevant for what is being discussed.

It is perhaps unrelated. I only mean that in the past, eligibility to request a blinded block was predicated on a validator's presence in registerValidators, and eligibility to request a block built by the paired execution client was predicated on a validator's presence in prepareBeaconProposer, but that need not be true. Both can be prepared by the beacon node based on registerValidator alone, called unconditionally by the validator client, and the validator client can control which one is signed and published.

Ultimately this suggestion serves two purposes:

Improve the security of node operators who fail to secure their beacon node API port
Simplify the clients

I'd like to hear from the client teams as to whether they think it accomplishes 2.
I can tell you that 1 is a given, though.

send prepareBeaconProposer and registerValidator with the same vector sizes at the same cadence. I have graphs, if needed, to back this up.

This is correct, the validator client doesn't know the proposers beforehand so it has to send them all and the beacon node will prepare a payload if there is an scheduled proposal.

I'd like to hear from the client teams

Although we still need to get the validator status at startup for various other reasons, I think consolidating those two APIs is a strict improvement in terms of security and also avoids overhead of calling two different APIs. The only overhead is that we would have to verify signatures but since this API is not that time sensitive I don't think it's an issue.
Just a note that we can't just deprecate prepareBeaconProposers and use the current registerValidator API. This requires to implement a registerValidatorV2 API which consolidates the two APIs (similar to block v3), otherwise pairing two different clients might result in proposers not being prepared at all.
Maybe something to enable at Electra fork epoch?

I spoke out-of-band with @tersec on the nimbus discord to get his perspective, and hopefully this summary is representative:

He is unconcerned with the security implications of prepareBeaconProposer being unauthed, and indifferent to changes to add signatures provided they do not create excess complexity.
Nimbus and at least LH send prepareBeaconProposer every slot, and registerValidator every epoch.

They do this to prevent, say, proxy changes which switch BNs in a way opaque to the validator client from creating up-to-one-epoch delays in signaling the EC to build blocks for pending duties.
If we were to merge endpoints, they would either have to revert to accepting delays in prepareBeaconProposer updates, or send registerValidator once per slot and rate limit the pass-through to the relays (who do not want registerValidator calls to cause undue load).

He is somewhat compelled by the notion of using pubkeys in place of indices to simplify the VC lifecycle.
He is wary of merging what he sees as loosely related codepaths (ie, they are similar, but not so similar that they should be combined, lest we need to revert them to separate in the future)

I'm of a mind to day that proxied beacon nodes bear the responsibility to broadcast prepareBeaconProposer requests to all upstreams, and that the VCs should not be sending prepareBeaconProposer once per slot. On the other hand, I can see why they do- a node operator who is not savvy enough to secure their beacon api port certainly is not savvy enough to handle a complicated proxying setup.

Thank you for summarizing our discussion here; yes, that's accurate from my perspective.

Speaking as a Lighthouse dev, I am in favour of combining them. I think it's a good simplification. I suspect that the current per-slot schedule for prepareBeaconProposer is excessive. It serves to inform the BN of the fee recipient, which would only be unknown if the BN had just restarted and lost all its state.
We could start experimenting prior to a coordinated release (e.g. Electra) by updating BNs to always draw fee recipients from registerValidator calls, and adding a flag to VCs to stop sending prepareBeaconProposer. Then the fork would just be a matter of 1) Knowing that the BN is consuming the fee recipient data and 2) Enabling the flag to turn off prepareBeaconProposer. We could also bump the version number on registerValidator for good measure, but we would not need to.

It serves to inform the BN of the fee recipient, which would only be unknown if the BN had just restarted and lost all its state.

This can also be mitigated by holding a tcp connection open (or similar), and sending an adhoc request each time it's reestablished. Nimbus does something along these lines, from what I can tell through observation.

There is ongoing discussion to pass the target gas limit configured on the vc side as part of prepareBeaconProposer which would be required for https://github.com/ethereum/execution-apis/pull/608. It would be a good opportunity now to consolidate these apis as we would have to update prepareBeaconProposer either way.
The new consolidated api could be called each slot as currently to address https://github.com/ethereum/beacon-APIs/issues/435#issuecomment-2042107011 or depending on validator client use different approaches but either way on the beacon node side could limit this to only forward registrations to builder once an epoch (to still follow builder spec).
Ideally, we wanna roll this out to out now and migrate to consolidated api post-electra

If we forget prepare_beacon_proposer and focus on register_validator then we could say that the validator client would send the validator registrations:

on startup
once per epoch
when it detects a beacon node restart

which should cover all of the eventualities.  However, the last situation here isn't something that can be recognized with the existing API.  It's possible that the clients will pick up the dropped connection if using long-lived connections, but it's not guaranteed.
An alternative would be to require on-disk caching of the validator registrations on the beacon node so that they are not lost on restart, but that seems like dumping a lot of work on the client teams.
We could add an endpoint in /eth/v1/node/ to provide the startup time of the node, but then this would need to be polled regularly and that's not a great solution either.
Or we can send the data more frequently, e.g. every slot, as you say.  But that's a significant amount of additional work for a corner case.
Perhaps a hybrid approach: if a validator client knows that it has a proposal coming up in the next epoch it sends the registrations each slot, otherwise once per epoch?  That may fit best in terms of retaining the statelessness of the API (and the underlying beacon node), but cover the corner case.  Thoughts?

We could add an endpoint in /eth/v1/node/ to provide the startup time of the node, but then this would need to be polled regularly and that's not a great solution either.

The Lodestar vc already polls /eth/v1/node/syncing each slot to refetch duties if node goes from syncing to synced. If this api returns a http error we can infer that the node is offline and resubmit proposer data if it comes online again. The edge case would be if the node restarts within the same slot so it appears online all the time from the vc point of view but the proposer cache would be cleared. This could be resolve by adding a start_time (or similar) as you proposed to the response.

That may fit best in terms of retaining the statelessness of the API (and the underlying beacon node), but cover the corner case. Thoughts?

I also think it would be best to not make any assumptions on how the beacon node manages the cache (eg. like persisting it to disk between restarts) and leave it up to the validator client to make sure it's updated before a proposal with whatever strategy fits well with the current design, this is pretty implementation specific, especially when it comes to how the interacts with multiple connected bns.


Getting the slice diagonals

Adding read access to the diagonal elements of a slice. For non-square slice, the returned vector containing the diagonal elements will have the length of the smaller dimension of the slice.
This is helpful for extracting contiguous diagonal elements of a bigger matrix.

Coverage remained the same at 100.0% when pulling 2b6783b48424622d79cd26342d78636ef57b1b8e on kamilritz:slice_diagonals into de6a2d31ffcd1ce1adcc3e273dc6f6459b318f79 on PX4:master.


response_type bug

.well-known/openid-configuration API said response_type support id_token

but actually not support.

occured when set casdoor as huawei iam ids provider. ref: https://support.huaweicloud.com/usermanual-iam/iam_08_0010.html

huawei ima only support id_token option

Yes, currently id_token can only be obtained at the access_token endpoint, and I will support this method as soon as possible with response_type=id_token.

Fixed in: https://github.com/casdoor/casdoor/pull/534


python312Packages.pygithub: 2.4.0 -> 2.5.0

Diff: https://github.com/PyGithub/PyGithub/compare/refs/tags/v2.4.0...v2.5.0
Changelog: https://github.com/PyGithub/PyGithub/raw/v2.5.0/doc/changes.rst

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.


Ellipse - ReadDWG - EndPoint (MajorAxis) is always 0,0,0

ellipse.zip

Hi @mattbrownfaro
I've open a new branch with a fix, please check this PR https://github.com/DomCR/ACadSharp/pull/43 and confirm it works for your case.

Sorry I missed this comment. I will take a look at 43. Thank you!

This morning I publish a release in nuget https://github.com/DomCR/ACadSharp/releases/tag/v1.3.4-alpha

Thank you Albert. I’ll get back to you later today.
From: Albert Domenech @.>
Sent: Monday, July 25, 2022 10:09 AM
To: DomCR/ACadSharp @.>
Cc: Matt Brown @.>; Mention @.>
Subject: Re: [DomCR/ACadSharp] Ellipse - ReadDWG - EndPoint (MajorAxis) is always 0,0,0 (Issue #42)
You don't often get email from<EMAIL_ADDRESS>Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
If you have clicked a link in this message with unexpected results, call IT immediately
This morning I publish a release in nuget https://github.com/DomCR/ACadSharp/releases/tag/v1.3.4-alpha
—
Reply to this email directly, view it on GitHubhttps://github.com/DomCR/ACadSharp/issues/42#issuecomment-1194364700, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACJHMIRVO2YTJR6HJACFWCLVV3CZHANCNFSM54M6Y7TA.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Hi DomCR,
I have a ByLayer question. Is this how you are supposed to use it?
                ACadSharp.Color color = dxfEnt.Color;
                int idx = color.Index;
                if (color.IsByLayer)
                {
                      idx = dxfEnt.Layer.Color.Index;
                }

The Sample_2018.dwg has a group of bylayer lines that are red in ACAD, but the Layer.Color.Index is 0.
@.***
Thanks,
Matt Brown | Sr Programmer
FARO Technologies, Inc.| Spokane, WA 99223
Mobile<PHONE_NUMBER>
Nasdaq: FARO |<EMAIL_ADDRESS>| www.faro.comhttps://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.faro.com%2F&data=04|01|mziegler%40inspired-tech.net|396be9692454496e050208d9cfc26c23|46c7c48fc6de455595c87a1742070915|0|0|637769256222737178|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=AMW80jNF2BOgUG2GKRGcvUDqOYJqvu%2FkbityWYl7u00%3D&reserved=0
To receive FARO marketing material including but not limited to, Tech Sheets and Whitepapers, for new and existing FARO Products, please  Subscribe herehttps://subscription.faro.com/ (you may select an alternative language).
To learn more about how FARO processes your personal data, please read our privacy policy which is available at:  Privacy Noticehttps://www.faro.com/en-gb/privacy-policy
Click herehttps://subscription.faro.com/?rec=1&lang=en to quickly and easily unsubscribe from receiving additional marketing material from FARO.
Unsubscribehttps://subscription.faro.com/?rec=1&lang=nl       Se d?sabonnerhttps://subscription.faro.com/?rec=1&lang=fr      Abmeldenhttps://subscription.faro.com/?rec=1&lang=de      Disiscrizionehttps://subscription.faro.com/?rec=1&lang=it      Odmowa Subskrybcjihttps://subscription.faro.com/?rec=1&lang=pl      Cancelar la suscripci?nhttps://subscription.faro.com/?rec=1&lang=es      Cancelar a subscri??ohttps://subscription.faro.com/?rec=1&lang=pt      Oturumu kapathttps://subscription.faro.com/?rec=1&lang=tr
**** This electronic mail message is transmitted exclusively for the intended recipient. It is not intended for transmission to, or receipt or use by, any unintended or unauthorized persons. Any review, use, printing, copying, retention, disclosure or distribution not expressly authorized is strictly prohibited and may violate applicable laws. If you have received this message in error, please (i) do not read it or any attachment, ii) immediately reply to the sender that you received the message in error, and (iii) erase or destroy the message and any copies that may exist. Thank you. ****


Feature/wa 320 swagger setup

Introduced SWAGGER_SCHEME_PROTOCOL to force to use swagger using a specific scheme protocol.

Pull Request Test Coverage Report for Build 67

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

Totals

Change from base Build 60:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls


feat: kyvejs runtime containerization and enhancements

Revamp the KYVE protocol node architecture, which currently consists of two main components: the core and the runtime. The primary focus of this overhaul is the enhancement of the runtime component, which, as of now, is exclusively developed by the KYVE team and implemented in TypeScript.
The primary goal is to introduce a standardized Docker interface, opening the door for the broader community to create their own runtimes in their preferred programming languages, as long as they adhere to the specified Docker interface standards. Consequently, the core component will communicate with the runtime via this Docker interface, simplifying the transfer of data between these two vital parts.
This pull request includes the following key updates:

Definition of gRPC protobuf file.
Porting of the Tendermint runtime into a standalone Docker container.
Development of a command-line tool enabling users to interact with core functions through the command line interface.

These changes collectively aim to make the KYVE protocol node more versatile, allowing a wider community of developers to contribute to and extend its functionality.
Resolves  https://linear.app/kyve/issue/TECH-1077
Resolves https://linear.app/kyve/issue/TECH-1076
Resolves https://linear.app/kyve/issue/TECH-1034

Here my thoughts:

move runtime.proto from common/types to common/protocol since it is the "source of truth" of the runtime <> core communication and is definitely a core feature. Currently the source of truth for the runtime interface is the runtime.interface.ts: question here: what will be the truth of source in the future, do we compile the TS interface out of the proto file?
validateDataItem changed, instead of a boolean it returns a number now (indicating either valid, invalid or abstain), this has to be adjusted so @kyvejs/docker successfully builds again


Migrating from NPM to YARN

I have migrated the codebase from npm to yarn
In terms of speed and performance Yarn is better than NPM because it performs the parallel installation. Yarn is still more secure than NPM
This is simple task

Hey!
We just migrated into Qwik framework 💯
Do you mind update the PR?

Ok
Actually I was waiting for it

Don't forget to update the README.md


How to change the OpenAI interface address

Prompt openai can't connect, how to change openai interface address, please help me

Try transcribe - https://github.com/vivekuppal/transcribe
It allows for changing the base URL. See this as an example - https://github.com/vivekuppal/transcribe/issues/198


Review how we create the name of the host_vars file as it contains invalid chars

Problem
Ansible reports this WARNING message
ansible-playbook ansible/playbook/post_installation.yml --tags k8s_cluster -e k8s_version=1.16.7 --limit n01-k116 -b
[DEPRECATION WARNING]: The TRANSFORM_INVALID_GROUP_CHARS settings is set to allow bad characters in group names by default, this will change, but still be user configurable on deprecation. This feature will be removed in version 2.10. Deprecation warnings can be
disabled by setting deprecation_warnings=False in ansible.cfg.
[WARNING]: Invalid characters were found in group names but not replaced, use -vvvv to see details

[WARNING]: Found both group and host with same name: n01-k116

[WARNING]: Found both group and host with same name: n01-k116

Action items:

[ ]  Should we then rename the file n01-k116 created under ansible/inventory/host_vars ?
[ ] Should we also document what do to to avoid the warning Found both group and host with same name: n01-k116 ?

@jacobdotcosta

I think the problem is with group names, as groups shouldn't contain the minus character. That's why Ansible is complaining about  Invalid characters were found in group names (for instance, this issue ).
I suggest group names relate to some kind of functionality, because they provide resources for playbooks and roles as well as allow to filter to which hosts a playbook applies. For instance, we could have different hosts for k8s hosts, and a lower level indicating which version of k8s to be installed. This would be implemented with a hosts file and several group_vars files such as:
.../inventory/k8s_hosts
[masters:children]
k8s_115
k8s_116

[k8s_115]
host_01
host_02

[k8s_116]
host_03
host_04

Then in the each of the group_vars files, located at .../inventory/groups_vars
masters
firewall_ports: ... firewall_services: ...
k8s_115
k8s_version: 1.15.10
k8s_116
k8s_version: 1.16.19

Would the information be better organized if we use YAML syntax ? As this file will mainly be used by you and stored under gitlab, then we can adopt whatever solution you propose ;-)

The hosts are now in the dynamic inventory. The groups var files are being documented in #148 .


Fix #119

Tested in Windows, and found an issue with when you call a folder. @gordonwritescode is fixing.


fix: secret-lookup tests changed to use organization where github app is not installed

Description
secret-lookup tests changed to use organization where github app is not installed
Credits: https://github.com/konflux-ci/e2e-tests/pull/1200
Issue ticket number and link
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:

[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/lgtm

/approve

/approve


Adds travis support, with README badge

Go to https://travis-ci.org/profile/kgabis in order to enable the travis testing on this repository. Once this is done, every PR (and direct pushes too) will be tested automatically when it is open. You will also have to authorize travis as an oauth app for your profile.
Note: If you merge this PR after #76, you will need to append make tests in the .travis.yml file. If you merge it before, you will need to append that line in #76.

I don't see a good reason to add this change. It's a small project and I test every PR myself, having a green badge in readme doesn't really add much value. And  seeing if parson builds is probably the least time consuming part of accepting a PR. I might be missing something though, so feel free to explain your view.

Pretty simple. What can be automated shall be automated. No matter how, you can never be on average faster than travis, because that would require you to instantly start testing the PR when it is submitted. The results of the tests are not only for you, but for the people sending the PRs too. If they didn't bother to run the tests, and send the PR, they will see that their patch is broken before you tell them.
Also testing with the default make rule is semantically incorrect; as it will break many distribution tools, expecting to have tests in a separate rule (but that's in another PR).

I disagree, sometimes the cost of automating something is higher than the value it provides (see home IoT). And the only thing it automates is a one line command. I don't know what travis-ci is, if it will exist in few years, and what it will do with all the permissions it requires. And a PR not building has never been an issue so far. I'll close this PR because I really don't see a reason to merge it. Also, sorry for not addressing you other PR so far, I'll take a look at it when I've got a spare moment.


Logo Proposal

Hi @davidmerfield  Good day Sir! I am a graphic designer and i would like to contribute to your great project by designing a logo for it as my gift for free. I first need your permission before i begin working on ideas..Thanks and best regards! - Tobaloidee

Hello @Tobaloidee, that's kind of you but I must decline. Closing this for now


Logging operator reports CrashLoopBackOff when I try the steps from README to install the operator

Describe the bug
$ kubectl get pods
NAME                                READY   STATUS             RESTARTS   AGE
logging-operator-795f4f66d4-pr4tb   0/1     CrashLoopBackOff   5          5m33s
kubectl logs logging-operator-795f4f66d4-pr4tb
/usr/local/go/src/runtime/asm_amd64.s:1333
panic: assignment to entry in nil map [recovered]
panic: assignment to entry in nil map
{"level":"info","ts":1551810833.3330257,"logger":"controller_plugin","msg":"Reconciling Plugin","Request.Namespace":"default","Request.Name":"nginx-logging"}
time="2019-03-05T18:33:53Z" level=info msg="Applying filter"
E0305 18:33:53.434889       1 runtime.go:69] Observed a panic: "assignment to entry in nil map" (assignment to entry in nil map)
To Reproduce
Steps to reproduce the behavior:
Follow the exact steps of readme for logging operator.
Expected behavior
Operator pod
Fluentbit and Fluentd daemon sets should have been created
kubectl get pods should have returned all the created resources.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

@mradha25 thanks for reporting this issue, sorry we just updated the README.

Hi, is the issue just with the readme file? I had tried by correcting those glithces.


GCC 13.2 issue

Hi,
pllua 2.0.12 fails to build against GCC 13.2 on Fedora 38. Output is below. Can you please take a look?
Thanks!
Regards, Devrim

gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Werror=vla -Wendif-labels -Wmissing-format-attribute -Wimplicit-fallthrough=3 -Wcast-function-type -Wshadow=compatible-local -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -Wno-format-truncation -Wno-stringop-truncation -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fPIC -fvisibility=hidden -I%{includedir}  -I. -I./ -I/usr/pgsql-16/include/server -I/usr/pgsql-16/include/internal  -D_GNU_SOURCE -I/usr/include/libxml2  -I/usr/include  -c -o src/paths.o src/paths.c
src/objects.c: In function 'pllua_resetactivation':
src/objects.c:419:22: error: too few arguments to function 'lua_resetthread'
419 |                 rc = lua_resetthread(thread);
|                      ^~~~~~~~~~~~~~~
In file included from src/pllua.h:19,
from src/objects.c:7:
/usr/include/lua.h:156:21: note: declared here
156 | LUA_API int        (lua_resetthread) (lua_State *L, lua_State *from);
|                     ^~~~~~~~~~~~~~~
make[1]: *** [: src/objects.o] Error 1

Confirmed this is a bug in Fedora 38 packaging of Lua, which claims to be 5.4.4 but incorporates changes from upstream 5.4.5, including the change that broke the ABI and API.
Closing wontfix, because this is the fault of the FC Lua package maintainer, for creating a package that is incompatible with every other Lua version in existence.

Incidentally, you probably need to be aware that pllua binaries built against any Fedora Lua 5.4.x package from before lua-5.4.4-9 will likely crash if run against the libraries from lua-5.4.4-9 if given a query that involves early termination of a SETOF function (since in such cases lua_resetthread will be called with a single arg).
(This is why I put in code to try and detect 5.4.5 at runtime, but that doesn't help since the Fedora package still claims to be 5.4.4.)


.click() element of control_type=Pane

I have an element:
{'class_name': 'WindowsForms10.Window.8.app.0.3b93019_r36_ad1',  'friendly_class_name': 'Pane',  'texts': [' On '],  'control_id': 328786,  'rectangle': <RECT L121, T476, R141, B496>,  'is_visible': True,  'is_enabled': True,  'control_count': 0,  'is_keyboard_focusable': True,  'has_keyboard_focus': False,  'automation_id': 'm_7b4cbcbae7174e47929ddd7339f80b0d'}
Control Identifiers: Pane - ' On '    (L751, T747, R771, B767) [' On ', 'Pane', ' On Pane'] child_window(title=" On ", auto_id="m_7b4cbcbae7174e47929ddd7339f80b0d", control_type="Pane")
Output from Inspect.exe:

hwnd=0x00050452 32bit class="WindowsForms10.Window.8.app.0.3b93019_r36_ad1"
ControlType:	UIA_PaneControlTypeId (0xC371)
LocalizedControlType:	"pane"
Name:	" On "
ClassName:	"WindowsForms10.Window.8.app.0.3b93019_r36_ad1"
NativeWindowHandle:	0x50452
IsOffscreen:	false
FrameworkId:	"WinForm"
ProviderDescription:	"[pid:6960,hwnd:0x50452 Main:Nested [pid:1908,hwnd:0x50452 Main(parent link):Microsoft: MSAA Proxy (unmanaged:uiautomationcore.dll)]; Hwnd(parent link):Microsoft: HWND Proxy (unmanaged:uiautomationcore.dll)]"

The element looks like a CheckBox, but raises AttributeError: Neither GUI element (wrapper) nor wrapper method 'click' were found (typo?) upon .click(), and raises NoPatternInterfaceError upon .invoke() and .select().  I believe this error is because it's a Pane control_type.
.click_input() works fine, but I would prefer to not have the window and button visible.
I should also note that all of the above is identical with both 'uia' or 'win32' backends.
My question: is it possible to get .click() to work on this element?
Thanks in advance.

The simplest way might be just get the control coordinates and use the mouse module to perform the click.
import pywinauto.mouse as mouse

coords = app.child_window(title=" On ", auto_id="m_7b4cbcbae7174e47929ddd7339f80b0d", control_type="Pane").rectangle().mid_point()
mouse.click(coords=(coords.x, coords.y))  # left button is the default

It's worth trying methods .toggle() and .select(). Method .click() is an alias for .invoke() for pure buttons only. Otherwise use .click_input() method as a usual click by mouse.

Hi airelil and Vasily. Thanks for your responses.
Getting mid_point() coords and mouse clicking performs the same as .click_input(). It works when the item is visible in the window, but doesn't work when scrolled out of view.
But never mind that, I got .click() to work. Using backend='win32' makes it respond to .click(). I thought I tested this, but I obviously did not.
Now my next issue is getting the button to click while the window is minimized.
If I set Application(visible_only=False) or  .window(visible_only=False) then I should expect that dlg.button.click() will work when the window is minimized, is that right?

First, make sure you are able to get the access to the control. If it's resolved you can get the "wrapper_object" for the control with dlg.button.wrapper_object(). After this, you may want to call set_focus() before calling the click(), so the window will be restored back.
If you don't want to change the active window, I think, there is not much you can do about it because, win32 backend's HwndWrapper.click() method is already sending WM_BUTTON messages to the control and that's up to the application and the control itself to process the messages.

That's good to know. I'll mark as closed because I have a good solution. I plan to use .set_focus() and then .move_window() to ensure robust button clicking. Thanks for all the help.

Hi
If I use wo = getattr(app, app_name_for_pb).child_window(title=ev['element_name'], control_type=ev['control_type'], found_index=0).wrapper_object()
where element_name and control_type are derived from the elements properties.
Will it be possible to use this wrapper_object to click on an element whose control_type is pane.
ev is the events which is stored in a json format after a bunch of action has been performed on an application


[WIP] initializing new sphinx docs based on submodule_template

initializing new sphinx docs based on submodule_template

Pull Request Test Coverage Report for Build 675

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage remained the same at 88.308%

Files with Coverage Reduction
New Missed Lines
%

spaghetti/network.py
2
89.39%

Totals

Change from base Build 673:
0.0%

Covered Lines:
1148

Relevant Lines:
1300

💛  - Coveralls


pip install cocotb-vivado problem

I tried to installed cocotb-vivado with pip install cocotb-vivado, which seemingly worked, but running any test files throws an error:
.... ~/projects/cocotb-vivado/tests (main)$ python3 test_axil.py
Traceback (most recent call last):
  File "/home/kolos/projects/cocotb-vivado/tests/test_axil.py", line 1, in <module>
    from cocotb_vivado import run
ModuleNotFoundError: No module named 'cocotb_vivado'

While trying to fix it I unintentionally installed a python environment "thing" with
sudo apt install pipenv
so now when I try uninstall or reinstall any python package I get this error:
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
   python3-xyz, where xyz is the package you are trying to
   install.

   If you wish to install a non-Debian-packaged Python package,
   create a virtual environment using python3 -m venv path/to/venv.
   Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
   sure you have python3-full installed.

   If you wish to install a non-Debian packaged Python application,
   it may be easiest to use pipx install xyz, which will manage a
   virtual environment for you. Make sure you have pipx installed.

   See /usr/share/doc/python3.12/README.venv for more information.

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.

If I try to us pipx for installing stuff to handled virtual environments it gives menacing warnings and simulations still fail with the same error:
pipx install cocotb-vivado --include-deps
⚠  File exists at /home/kolos/.local/bin/cocotb-config and points to /home/kolos/.local/bin/cocotb-config, not
    /home/kolos/.local/share/pipx/venvs/cocotb-vivado/bin/cocotb-config. Not modifying.
⚠  File exists at /home/kolos/.local/bin/find_libpython and points to /home/kolos/.local/bin/find_libpython, not
    /home/kolos/.local/share/pipx/venvs/cocotb-vivado/bin/find_libpython. Not modifying.
  installed package cocotb-vivado 0.0.4, installed using Python 3.12.3
  These apps are now globally available
    - cocotb-config (symlink missing or pointing to unexpected location)
    - find_libpython (symlink missing or pointing to unexpected location)
done! ✨ 🌟 ✨

I know it is messed up and feel ashamed of it.
Do you have any suggestion how to get cocotb-vivado running?
I haven't installed python modules from source yet.

You can try something like this (it will decompress/install conda to $HOME/miniconda you can delete it afterwards).
curl -L https://repo.anaconda.com/miniconda/Miniconda3-py310_24.9.2-0-Linux-x86_64.sh -o miniconda.sh
bash miniconda.sh -b -p $HOME/miniconda
export PATH=$HOME/miniconda/bin:$PATH
pip install cocotb-vivado pytest


feat(gitlab): collect child pipelines

⚠ Pre Checklist

Please complete ALL items in this checklist, and remove before submitting

[x] I have read through the Contributing Documentation.
[ ] I have added relevant tests.
[ ] I have added relevant documentation.
[x] I will add labels to the PR, such as pr-type/bug-fix, pr-type/feature-development, etc.

Summary
What does this PR do?
Collect child pipelines in gitlab plugin
Does this close any open issues?
Closes #8005
Screenshots
Include any relevant screenshots here.
child pipelines in raw layer

child pipelines in tool layer

child pipelines in domain layer

Other Information
Any other information that is important to this PR.

Hi,
I tested this fix but unfortunately it doesn't resolve the issue.  I can provide more information if you tell me what you need to have.
Thanks.

Hi, I tested this fix but unfortunately it doesn't resolve the issue. I can provide more information if you tell me what you need to have. Thanks.

@MarcViola Please submit a new issue and describe it in detail.


correcting spelling mistakes

What is the purpose of the change?
I have corrected some spelling mistakes I found.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 29.18%. Comparing base (a9e4910) to head (75458e4).

:exclamation:  There is a different number of reports uploaded between BASE (a9e4910) and HEAD (75458e4). Click for more details.
HEAD has 2 uploads less than BASE

Flag
BASE (a9e4910)
HEAD (75458e4)

integration-tests
1
0

unit-tests
1
0

Additional details and impacted files
@@              Coverage Diff              @@
##                3.3   #15015       +/-   ##
=============================================
- Coverage     60.76%   29.18%   -31.58%
+ Complexity    10866     8860     -2006
=============================================
  Files          1882     1882
  Lines         85983    85983
  Branches      12876    12876
=============================================
- Hits          52246    25098    -27148
- Misses        28289    56908    +28619
+ Partials       5448     3977     -1471

Flag
Coverage Δ

integration-tests
?

samples-tests
29.18% <ø> (-0.04%)
:arrow_down:

unit-tests
?

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Role Assignment

User story

As a Team Member
I want  the roles to be assigned week by week
So that a plan and history of role assignments so that everyone knows their job

Acceptance criteria

The project should be planned at the start of the
More roles can be assigned beyond the four required ones
...

Definition of done

Added only after week 5
The same for all features

Please comment Okay, if you agree with the role assignment.

Okey

that's ok for me

Okay..

OKAY

Okay

okay for me

Okay for me.

ok


Attesteer API for requesting remote attestation

So far we have only implemented the PoC for the Attesteer such that it can fetch the Marbles of Marblerun and fetch the enclave quote to send a remote attestation on chain. However, for non-security setups, we need to expose an endpoint to request forwarding of a remote attestation. This should be fairly simple:

[ ] Add RPC method to the trusted TLS server to request forwarding
[ ] We also need to check f the requester has subscribed to using the service. We will probably have a pro-rata billig, so we need a local DB that stores per subscriber: 1. Remaining quota, 2. How many requests have been sent. Not sure about the second though, all the remote attestations are already on the public blockchain.

Should we consider that this could also be a pull service?

So summarizing about what we talked about: The Attesteer shall be used by clients who do not use our SDK; hence we should not use the TrustedOperation in the RPC, which will also remove the double encryption issue for this specific RPC. Steps to do:

Add new commands here: https://github.com/integritee-network/worker/tree/master/cli/src/trusted_base_cli/commands. Todo: in what format is it the easiest to supply the attestation to the CLI (hex, json)? in a first step, we could also read it from the file system if we have one available. -> Go for the quickest solution here, and refine later.

send_ias_attestation,
send_dcap_quote

Let yourself insire from send_request: https://github.com/integritee-network/worker/blob/d71d2c572259605ee1c9f92b8d3e0a1de150098c/cli/src/trusted_operation.rs#L105

but don't send an encrypted trusted operation, send and hex-encoded, unencrypted quote/attestation report
the result is not a trusted operation status, but simply an ok/error.

Skip decryption the rpc-params here, as you receive the quote directly: https://github.com/integritee-network/worker/blob/b900e2da99c3d766a2adddd7b2bfb5f46c105f29/enclave-runtime/src/rpc/worker_api_direct.rs#L252


ISPN-13342 HotRodSslFunctionalTest.testLifespan2x random failure

https://issues.redhat.com/browse/ISPN-13342
Compute the lifespan/max-idle values just like the server would

Merged, thanks


Updating documentation for Lindenmayer

converting to using SwiftUI's Angle type instead of Double in renderers and rendering commands for consistency and usability clarity
adding docs to a variety of methods
renamed PWrapper to ParameterWrapper
normalized rendering commands and removed unimplemented ones

resolves #7

coverage update with this PR:
   --- Experimental coverage output enabled. ---
                | Abstract        | Curated         | Code Listing
Types           | 99% (114/115)   | 100% (115/115)  | 0.87% (1/115)
Members         | 4.4% (431/9733) | 98% (9548/9733) | 0.010% (1/9733)
Globals         | 27% (4/15)      | 100% (15/15)    | 0.0% (0/15)

from command:
xcrun docc convert \
--fallback-display-name Lindenmayer \
--fallback-bundle-identifier Lindenmayer-swift \
--fallback-bundle-version 0.1.0 \
--additional-symbol-graph-dir .build/symbol-graphs \
--experimental-documentation-coverage \
--level brief


Clear command in the tile38-cli

Is your feature request related to a problem? Please describe.
Although not strictly necessary, it would be nice if the tile38-cli had a "clear" command to clean up the console.

This could improve user's experience of using the cli specially when the database is already populated.
Describe the solution you'd like
Something like the "clear" command in the redis-cli.

Hi @CaioDallaqua, you can use CTRL+L to clear your terminal output on unix systems. Not sure about the windows alternative.


ps doesn't work reliably when executed inside pods by the e2e test suite

What happened:
Functional tests that run ps inside of virt-handler (and virt-launcher?) tend to get flaky, with ps usually finding the right information but then failing with error 1.
Some past investigation seemed to identify SIGURG as causing issues, but trapping it didn't seem to make a difference:
https://github.com/kubevirt/kubevirt/commit/13a7e4c82ea0fa600a17512fa4addda3ccbf1205
https://github.com/kubevirt/kubevirt/pull/8600/files
As a result, we usually end up replacing ps calls to other tools like pidof or pgrep that do not seem to suffer the same problem. Examples:
https://github.com/kubevirt/kubevirt/pull/6734
https://github.com/kubevirt/kubevirt/pull/10235
It would be a good idea to create a draft PR with tons of debug around some flaky ps call to find the root cause of this, as it could be an important issue with KubeVirt containers...

Maybe the ps bug was fixed and we need to drop the trap of SIGURG
something like that was suggested here
https://www.suse.com/support/update/announcement/2022/suse-ru-20220808-1/

Maybe the ps bug was fixed and we need to drop the trap of SIGURG
something like that was suggested here iiuc https://www.suse.com/support/update/announcement/2022/suse-ru-20220808-1/

Thanks for the pointer! However, we see the issue with and without the URG trap.
The reason I mentioned it is to avoid someone else going down this rabbit hole. Your link further supports the fact that that signal is not the problem.
In fact, right now I don't think any ps call in kubevirt tests runs with SIGURG trapped anymore.

@jean-edouard would you be able to check if we use ps anymore?


Upgrade deprecated node.js from 12 to 16

upgrade the docker image in action.yaml
upgrade the node typings in package.json

@microsoft-github-policy-service agree [company="{your company}"]

@microsoft-github-policy-service agree

@microsoft-github-policy-service agree company="Atanasov-IT"


Compatible with Chrome OS

Kind (Required)

Proposal / Discussion

Overview (Required)

Chrome OSに対応。

Links

Chromebookで始めるラップトップ向けAndroidアプリ - DroidKaigi 2019 https://droidkaigi.jp/2019/timetable/70230

Preview virtual Chrome OS devices on the Android Emulator  _  Android Developers
https://developer.android.com/topic/arc/emulator

This is current situation I launched the app on emulator.
Good.

It's my fault. There is no Play Services on this emulator.
Is there anyone who has physical Chrome OS device?


Update app store for release

New Cover thing
Better screenshots (with overlayed words)
Actually write things about it


Query: What is the difference between detector_backend and model_name in many of the functions in Deepface

For example,
find, stream etc. functions in Deepface have both detector_backend and model_name as arguments.
I also tried to understand a little more by reading the codebase and some articles too https://viso.ai/computer-vision/deepface/
I didn't really get the difference. Also Dlib is both a detector_backend and model. Its confusing.
Tried to search existing issues too, if its already been asked.
Sorry, if its a silly question. Good library, thanks for creating it.
Thanks

Firstly, these are explained in read me
Model name refers to face recognition models whereas detector backend refers to face detector models.
Dlib has its own face recognition model and face detector. That is why, it appears in both.


Style and other errors were fixed

Changes Unknown when pulling 4b178c9010e5c734a7c158813b3f78b584fb8279 on Senex626:homework1 into ** on rybalkinsd:homework1**.

Changes Unknown when pulling cc5a4759a041d10c669755a4d1285f2cfd54ecd2 on Senex626:homework1 into ** on rybalkinsd:homework1**.

Фамилия?

Филатов
2017-03-14 1:18 GMT+03:00 Alexander<EMAIL_ADDRESS>
Фамилия?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rybalkinsd/atom/pull/71#issuecomment-286261514, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AYwPRo19yT1U42pptvZWm1e48-ZqDsp1ks5rlcC7gaJpZM4MMSnq
.


Fix issue #11

I guess we should. But I feel that you would prefer not to. How would you solve this?

I very much appreciate your input. I am a bit busy currently so I can‘t review the code and the consequences of this change. It does seem to make total sense but I was wondering why I enumerated all files (w/o a filter), and whether there was possibly a reason. If you have verified the functionality, and all works fine, then I am more than happy to accept your request and add the code change :-)

When using the fast method, with -Filter it now works beautifully. I will updated my fork's branch to filter to slow method and send you a new PR.

Many thanks that‘s awesome mate. Just added the merge.


Bad naming on Path.GetDirectoryName and Path.GetFileName

These are well known problems:
Path.GetDirectoryName is NOT returns the directory name but the parent path of the string provided.
Path.GetFileName is NOT returns the file name but the last path node of the string provided.
Problem is when dealing with a folder path, it is very easy to be confused to choose GetDirectoryName incorrectly over GetFileName.
Why not consider to change those name?
Thanks for hearing my murmur...

This repo is no longer actively monitored. Closing up old issues that have not had activity in while. If this is still an issue, please open a new issue in an appropriate repo listed in microsoft/dotnet#1275

This repo is no longer actively monitored. Closing up old issues that have not had activity in while. If this is still an issue, please open a new issue in an appropriate repo listed in microsoft/dotnet#1275


pods Item list is empty

Lens: 2024.11.261604-latest
This horrible app updated itself and stopped working at the most crucial moment! It just doesn't display the list of pods.

I was able to access my cluster by defining it's name in the namespace settings.

I was able to access my cluster by defining it's name in the namespace settings.
Unfortunately this didn't help (arm version)

+1

+1

I was able to access my cluster by defining it's name in the namespace settings.

It works for me

I was able to access my cluster by defining it's name in the namespace settings.

It work.
thank you

Unfortunately, @ericdesa solution didn't help.

Note: you need to define the correct name of the Namespaces (or add multiple Namespaces). It's probably the same that is defined in the kubeconfig.

I was able to access my cluster by defining it's name in the namespace settings.

works for me, thanks

Was able to make it work as @ericdesa suggested. By adding the namespace. But this is annoying, previously it used to work.
Following this thread +1
Waiting for fix to be rolled out

I was able to access my cluster by defining it's name in the namespace settings.

Thanks, it works

@dawsayan the fix should be in the beta release that we rolled out, and then in the next version coming soon.


chore: add new sponsors

also @rebeccawang06, let's put the squarish logos at the bottom so it doesn't make the spacing weird.
the mostly-typographic logos are usually rectangular so they take up less space. we can put these above.


Save & Share your work feature

Consider developing an easy way for users to bookmark and share search parameters from DB.
Before implementing we should user test this feature.

Reference: https://www.consumerfinance.gov/data-research/hmda/explore

This could be a candidate for an FAQ vs new feature. We can check to see if this is still a friction point with users during the next round of user testing


Maintain existing file structure - update from 0.2.4 to 0.9.9

Our current es cluster is being managed by version 0.2.4 of the plugin. In order to migrate from ES 1.7.1 to 2.1.0 we are updating to the latest version of the plugin.
Our current data structure looks like this:
/var
  /lib
    /elasticsearch
      /sa-****
        /nodes
          /0

Previously we did not name this instance but with the new version of the module I guess we have to. So, I played around with the instance naming a bit. I tried naming the instance to elasticsearch but that creates /var/lib/elasticsearch-elasticsearch
I thought the following would work:
  elasticsearch::instance { 'sa-****':
    config        => $config,
    init_defaults => $init_defaults,
    datadir       => '/var/lib/elasticsearch/sa-****',
  }

That creates /var/lib/elasticsearch-sa-**** This would be fine if it is looking at the existing data dir but the process indicates it is looking at /var/lib/elasticsearch-sa-sand-logyard:
elastic+ 20129 61.2  4.2 4573796 343928 ?      Sl   11:36   0:07 /usr/lib/jvm/java-7-openjdk-amd64//bin/java -Xms2g -Xmx2g -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFr
action=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -XX:+DisableExplicitGC -Dfile.encoding=UTF-8 -Djna.nosys=true -Des.path.home=/usr/share/elasticsearch -cp /usr/share/elasticsearch/lib/elast
icsearch-2.1.0.jar:/usr/share/elasticsearch/lib/* org.elasticsearch.bootstrap.Elasticsearch start -d -p /var/run/elasticsearch-sa-****.pid -Des.default.path.home=/usr/share/elasticsearch -Des.default.path.logs
=/var/log/elasticsearch/sa-**** -Des.default.path.data=/var/lib/elasticsearch-sa-**** -Des.default.path.work=/tmp/elasticsearch-sa-**** -Des.default.path.conf=/etc/elasticsearch/sa-****

Any ideas on how I can maintain my existing file structure with the new plugin?

Hmm, when setting the data dir in the instance config it should honour that.
Let me double check tomorrow in my tests and see if there is a bug.

Thank you, I am also taking a look at the module itself to see if that can be improved

It doesn't look like the data directory set on an instance is making it into the init.d script. The CONF_DIR is another example of a variable in the init.d script that will not honor what is set on the instance.

the init scripts are not changed but the defaults file is at /etc/sysconfig/elasticsearch-$instancename
Also the data dir is being set in the elasticsearch.yml file in the instance config dir.

Hi,
The test at https://github.com/elastic/puppet-elasticsearch/blob/master/spec/acceptance/005_datapath_spec.rb#L129-L177 tests your specific situation and should work fine.
Can you check the settings in your elasticsearch.yml file?
Also could you check the content of $init_defaults ?  that you set in your instance config ?
Cheers.

I did find out where the -Des.default.path.data comes from but it should be overridden by the values that are in the elasticsearch.yml file.

I work with @erikanderson here at mx.com and the issue we were having was that we were making the wrong assumptions about how the data path for an instance in puppet translated to the data path that elasticsearch uses. We did not account for elasticsearch using the cluster.name as a sub-directory, so we were ending up with data in /es/data/instance-name/cluster-name, but what we wanted is /es/data/cluster-name.
Figured out how to get that with your module, so this is a non-issue. Thanks for you help!

Ahh okay. Yeah, the cluster name is what ES inserts by default, that's something i can't control using the puppet module :-(
Glad its solved.
Let me know if we can close this.
Cheers.

Yes, its good to close, thanks for the help


[DRAFT] Create a setting to represent a FHIR validation profile

User Story:
TBC
Description/Use Case
Organizations now have the ability to add {org}.*.report scope keys and will need to have the ability to remove them as well
Risks/Impacts/Considerations
Dev Notes:

Coming soon

Acceptance Criteria

[ ] Profile should include type (parser, instance, XML)
[ ] Profile should include type-specific config

Closing as it is a duplicate of #8977


Version tracking

When we modify a note, its ResourceId changes as well. This is expected since we use content-addressing. In order to provide proper UX, we need to track versions of the same note and present them to user as a single note. We also need UI elements to present older versions to user ("timeback machine"). User should be able to view or remove unwanted versions. Forking older versions into another note is separate feature.
Version storage must be stored in .ark/versions file and should look approximately like this:
3155416 -> 7705444
5839051 -> 8921986
9279849 -> 1558729
3155416 -> 9763586
2128401 -> 19145158

Each entry of the file is a pair of ResourceIds, left id is parent and right id is child.
This feature needs a button to invoke list of versions, or "timeback machine", for any note. Each version must have a button to see its content (read-only mode), to remove it and to fork it (separate issue).
When we remove a version, we must keep the history unbroken.
Suppose, we have entries like this in storage:
3155416 -> 7705444
7705444 -> 8921986

If we want to remove 7705444 version, then we must replace these 2 entries with new entry:
3155416 -> 8921986

Here is similar issue in Navigator: https://github.com/ARK-Builders/ARK-Navigator/issues/40

Attached bounty: https://gitcoin.co/issue/29633

Payout for prototype of this feature: https://etherscan.io/tx/0xa9df96496280e01b5221aed96e2ff858b8ecb0f1861ccd6e1c75de055e4fda3a


DialogDismiss not compatible with forms

Current behavior
Using an HTML form in a Dialog, you use DialogDismiss to submit the form and close the dialog, but a couple different things are happening for me:

on codesandbox, it doesn't submit the form at all and just closes the dialog.
on my project, it does submit the form somehow but it also closes the dialog no matter what, even if the form fails validations so refocusing the failed input fails with the error "An invalid form control with name='field' is not focusable."

Steps to reproduce the bug

Open sandbox: https://codesandbox.io/s/lucid-dream-kvyjcj?file=/index.js
Try submitting with native submit to see the validation that should happen
Then submit with dialogdismiss and see it just dismisses even though it is type submit

Expected behavior
It should work with forms. It should submit a form when it is type="submit", which buttons are by default, and if a validation error occurs, it should not dismiss the dialog.
Workaround
No response
Possible solutions
No response

Marking this as a feature request because DialogDismiss is working as expected. It just doesn't support forms.
You can use the onSubmit event to close the dialog:
<form onSubmit={() => dialog.hide()}>


Binance perpetual - Delay on available balance causing inconsistent orders

Describe the bug
Reviewing binance perpetual for couple of hours and observed that the available balance is delayed on updating causing inconsistent order creation. On the screen recording below observed that the strategy is returning of insufficient balance when it should able post both buy and sell order.
https://github.com/hummingbot/hummingbot/assets/73840223/38d2d901-7d00-46a8-a3fb-d5a337baef2a

Observed that the available balance is causing inconsistent orders and delay which is also recorded on time 2:13 onwards
While this is true that there was a a change on the values, still it is not correct since the value of XRP upon testing was around 12 USDT and both buy and sell order are posted so expected available balance would be around 22 USDT

This issue has been also observed on previous v1.17 which we assume happen on other versions. We are still looking how to reproduce this using sample directional strategies (in progress)
Steps to reproduce

Setup Perpetual market making with binance_perpetual
Set order amount enough to create buy and sell order
Set long refresh time and observe connector behavior

Release version
previous versions and dev-1.19.0
Type of installation
Source
Attach required files
logs_perp-binance.log
perp-binance.yml.log must remove the .log to be used

Issue reproduced on dev-1.19.0

hi, would this bug be fixed soon?
it seems that the connector does not update the available balance with the ORDER_TRADE_UPDATE stream data.

it is only updated via the balance stream which only get updates when there is a change in position and the rest api only.

@leastchaos how is it going!
just to follow up this issue, if the docs says that account update only sends the update when we have a change on balance, positions or margin type, this means that the real balance will be okey but the available balance not since create and cancel orders are not included in this stream?
would you like to propose a solution for this?
there is a parameter of the connector that uses the information of the inflight orders to do the calculation.
It's defined in the connector base and is called real_time_balance_update

yes, available balance is only updated in the rest and not the websocket stream.
adding a single line self.real_time_balance_update = False to the init of BinancePerpetualDerivative can solve the available balance issue if we are only creating and canceling orders in a single market. e.g. creating orders and canceling orders in BTC/USDT if the strategy is market making on BTC/USDT but if i run on BTC/USDT but create and cancel orders in ETH/USDT, it will not do the update as the connector is not looking for the orders update for other markets.
so I'm stuck here and did not try to attempt further to  solve this as  I ended up polling more often by changing LONG_POLL_INTERVAL to just 2sec which suited my needs at the time.


Add support for enum basic type in VALUE clause

Description

Currently we cannot use enums in the VALUES clause:
.fromValues(MyEnum.class, "myEnum", MyEnum.values())

A workaround is to use the underlying type the enum is mapped to.
Expected behavior

That it simply works
Actual behavior

Produces an exception
Steps to reproduce

See code above
Environment

Version:            1.2.0
JPA-Provider:       Hibernate 5.2
DBMS:               -
Application Server: -

Another option is to make use of the fromValuesLike function introduced in 1.3.0.


Feature-Request

Is it possible to automatically include an item template for the MetroWindow?
It takes some time to always create a new WpfWindow, then include the namespace, rename the window, and finally deleting the baseclass from the code behind..
If it's not clear what I'm meaning then look here:
https://msdn.microsoft.com/en-us/library/tsyyf0yh.aspx
I don't know anything about the whole nugget thingy, so I don't know if its even possible to automatically include it, but I think it would be a good enhancement, even if we have to manually copy files :)

@MWFIAE This is already available https://github.com/MahApps/MahApps.Metro#visual-studio-templates

Ok, this should really be on the quick start guide or in the MetroWindow control page, because it should make working with metro much easier :)
But thx for helping me out. And shame on me for not rtfm good enough^^


no-mergeable-selectors can't handle media-queries with functions

When using a media-query with a function, like @media(min-width: break('large')) the no-mergeable-selectors rule has a false positive, because it's evaluating the rule to @media(min-width: null) for all break function calls and thus throws a warning for media-queries using different values in the break function.
This seems to be related to #703 which probably included a fix for variables but not for functions.

Thanks for the issue @thasmo I'll look into it soon


@kanaabe => Article overflow width bug

Another bug related to accessible text -- will be sure to take a close look at the previous changes and find more instances with width problems. This bug was raised here: https://artsy.slack.com/archives/C04GGGDCM/p1505920868000296
Adding a position and overflow declaration to the parent of a block including .screen-reader-text prevents it from overflowing the page width.  This PR adds this to social buttons in both sticky and footer placements.

Does this mean that any time a new page is created with the main nav the team has to remember to do this? If so, fixing these bugs one-off doesn't seem like a good long-term solution. Maybe there's a better way to get the text on the page without moving it far off the page?

Main nav has already been fixed page wide -- this was an edge case, but as noted above, I'm going to follow up on all the changes from the hackathon to see if anything else was missed.

Ok, sounds good. Maybe it's worth adding in a doc with best practices for accessibility so others can implement it on their pages with prior knowledge of the problems/caveats you've run into already.

Yeah smart thinking -- I will look into making a doc


Dropdown List in MonitorList

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
UI Feature
🔖 Feature description
I'm using Kuma to monitor my servers, and I noticed that as I add items to monitor the MonitorList starts to get polluted.
It wouldn't be interesting to put a drop-down list in the MonitorList, for example, separated by the first tag.
✔ Solution
I believe that performing a separation by tag, considering the first tag and making it clear in the settings that the first tag would be used for the drop-down list.
❓ Alternatives
No response
📝 Additional Context
No response

@Chronos093
I think this got resolved in 1.23.0

If this is not resolved, could you add screenshots what you are refering to?


Dead link

The link for the Microsoft Trust Center gives a 404.

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

ID: 7badd9db-8ff0-87b5-dea3-69b111a5752c
Version Independent ID: 449e2a7a-bbd4-7387-c9f8-2f3e06b38e74
Content: Azure security overview
Content Source: articles/security/security-get-started-overview.md
Service: security
GitHub Login: @TomShinder
Microsoft Alias: terrylan

@lordstyx  Thank you for pointing this out. I just went ahead and fixed this. Sorry for the slow response.

#please-close

@lordstyx We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


I found a broken link and wrong info in doc

in https://success.docker.com/article/how-do-i-set-the-docker-daemon-options has broken link: https://docs.docker.com/engine/reference/commandline/daemon/
and at this page wrong info: https://success.docker.com/article/how-do-i-set-the-docker-daemon-options
CentOS 7, in real possible use variable:
Environment="DOCKER_OPTS=-H=<IP_ADDRESS>:1111 -H unix:///var/run/docker.sock --tlsverify --tlscacert=/home/docker/ca.pem --tlscert=/home/docker/server-cert.pem --tlskey=/home/docker/server-key.pem"

ExecStart=/usr/bin/dockerd $DOCKER_OPTS

Hi @mmmcorpsvit - sorry for the delayed response. These are actually support articles, so we have opened up an issue in the applicable repository. Thank you so much for bringing this to our attention!

@mmmcorpsvit fix should be published within the next two to three business days.  Thanks again!


Bare line feed characters

Describe the bug
Your message contains invalid characters (bare line feed characters) which the email servers at yahoo.com don't support.
To Reproduce
When sending emails to @yahoo.com with html, and content property set to 'auto'
Expected behavior
No errors.

Will look into it. I think there is a quick fix...

Coud you provide a html example. I can't reproduce the error...

Close this as no reproduction was provided. Feel free to repopen or create a new issue

Maybe fixed by 8e0de37964518e18aa50edb06b99547638ddc3a6


Having categories for components beside general in left sidebar

Description
The component section  in the left sidebar has just two categories, we need more.
Steps to reproduce
At the moment there are only two categories, modal and general.
It would be great to have more categories, maybe one for each existing component type in your project.
Being able to resize that one would also be great.
ILLA Builder Version
2.9.1
Browser
No response
Operating System

[ ] macOS
[ ] Windows
[ ] Linux

Additional Information
No response

Thank you for your feedback. However, we may use different methods to allow you to customize the grouping of components instead of grouping by component type. Maybe your ideas and ours can be combined to group components by category after custom grouping. I will convey your suggestion to the relevant colleagues, and I will reply to you if there is a subsequent conclusion.


stats master_replica_placement_mismatch

What problem are we solving?
Alerting if the number of replicas does not match the given ones
How are we solving the problem?
Add a metric about the discrepancy between the number of replicas given
Checks

[ok] I have added unit tests if possible.
[ok] I will add related wiki document changes and link to this PR after merging.

Need to also update the grafana dashboard.


instantiate status bar contribs with services scoped to the window

fix https://github.com/microsoft/vscode/issues/210383
current issues:

line ending status bar contrib leaks over into the notebook editor now
sometimes duplicate status items are added to the notebook editor in the main window when a text editor is open in the aux window
status bar items are not re-added on reload, I'm not sure how this works for text editors

There is a IEditorGroupService.onDidCreateAuxiliaryEditorPart event that editor status listens to to create status:
https://github.com/microsoft/vscode/blob/0d7778d5441fa5bf751cb6f380724fa968797a96/src/vs/workbench/browser/parts/editor/editorStatus.ts#L901-L904
That should be called on startup when aux windows are restored.


Added Catalan language dictionary

I needed a Catalan spell checker, so I added one based on the LibreOffice dictionary files.

Thank you.  I'll merge.


Project picker says requirements not met even though it's all green

I tried opening https://github.com/land-of-apps/spring-petclinic — this is the welcome project picker screen:

It does appear to be working as intended with Python

It does appear to be working as intended with Python

Is it? I think it should say to proceed with caution. Seems like the logic could be inverted here.

It doesn't always work correctly with python, though:

flaskbb uses pytest as its test runner.

This issue is fixed by https://github.com/applandinc/appmap-intellij-plugin/pull/81/commits/e3bc36b17e8265f00ac8a7ab3dd401b59304009d

@apotterri Thanks! That's a new issue, tracking at https://github.com/applandinc/appmap-intellij-plugin/issues/120

Should be fixed with 0.11.0-2, please reopen if it's still a bug on your machine.
https://github.com/applandinc/appmap-intellij-plugin/releases/tag/install-guide-preview

:tada: This issue has been resolved in version 0.12.1 :tada:
The release is available on:

v0.12.1
GitHub release

Your semantic-release bot :package::rocket:


chore: rename *.yaml to *.json

cc @ShyunnY

cc @ShyunnY

YAML is compatible with JSON. Do we need to modify it to JSON?

cc @ShyunnY

YAML is compatible with JSON. Do we need to modify it to JSON?

this will case yamllint tool panic
on the otherside, content should match with ext

block

replaced by https://github.com/envoyproxy/gateway/pull/3077


chore: upgrade amaribot.js to v2

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#119  👈
#118
#117
#116
#115
#114
#113
#112
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @lynnntropy and the rest of your teammates on  Graphite

Merge activity

Mar 2, 10:51 AM EST: @lynnntropy started a stack merge that includes this pull request via Graphite.


youtube-dl no longer works on Chaturbate

They seem to have changed the way they stream, now I get...
$ youtube-dl https://chaturbate.com/[room-id]
[Chaturbate] [room-id]: Downloading webpage
ERROR: Room is currently offline

Room is not offline.
Same behaviour in both Windows and Linux.

Carefully read new issue template and provide all requested information.


Font-awesome glyphs not displayed

No fontawesome.css in assets folder, may be linked to the timeout error during post-install ? (#1)

Solved in 2b58401. It was indeed due to the timeout error during install : some files were not created.


Add Support for Laravel 6

Please provide compatibility for Laravel's latest release, version 6.

Done, I just tagged v1.4

With this new update, i get a 500 code when using the feedback system.
{message: "Call to undefined function Mydnic\Kustomer\Http\Controllers\str_random()",…}
exception: "Symfony\Component\Debug\Exception\FatalThrowableError"
file: "/var/www/html/vendor/mydnic/laravel-kustomer/src/Http/Controllers/FeedbackController.php"
line: 72
message: "Call to undefined function Mydnic\Kustomer\Http\Controllers\str_random()"

@PatricNox just fixed it, completely forgot I was using this function use  v1.4.1

Very nice!


Implement deserializeEnum for test deserializer

Closed in https://github.com/getty-zig/getty/commit/35194f717083b1e14cc9ee84631af98f637eb509.


Add file path option

Could you please add file path option to make the search more powerful ?
(path:.xml OR path:.json OR path:.properties OR path:.sql OR path:.txt OR path:.log OR path:.tmp OR path:.backup OR path:.bak OR path:.enc OR path:.yml OR path:.yaml OR path:.toml OR path:.ini OR path:.config OR path:.conf OR path:.cfg OR path:.env OR path:.envrc OR path:.prod OR path:.secret OR path:.private OR path:*.key)

This is a good suggestion, I will implement this. Thanks!


changes to enable building as a submodule

Since hipBLAS is a very frequently used library,  it makes much more sense to be able to build it in a single step.
This replaces the previous version which was a fork of Sabojit's branch.

Maybe retarget this to the develop branch where changes should be staged before we merge in master for new releases.

@rothpc  please review


Register and launch single task execution

TL;DR
This change implements register_and_launch for single task executions featuring containerless tasks.
Type

[ ] Bug Fix
[x] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[x] Smoke tested
[x] Unit tests added
[x] Code documentation added
[x] Any pending items have an associated Issue

Complete description
The use case for this feature is in-notebook task execution. Because only containerless tasks do not need to update an image during task iteration, only those are supported for register_and_launch.
Tracking Issue
https://github.com/lyft/flyte/issues/256
Follow-up issue
https://github.com/lyft/flyte/issues/221

Codecov Report

Merging #126 into master will decrease coverage by 0.11%.
The diff coverage is 52.83%.

@@            Coverage Diff             @@
##           master     #126      +/-   ##
==========================================
- Coverage   81.51%   81.39%   -0.12%
==========================================
  Files         213      215       +2
  Lines       13907    14012     +105
  Branches     1142     1146       +4
==========================================
+ Hits        11336    11405      +69
- Misses       2302     2337      +35
- Partials      269      270       +1

Impacted Files
Coverage Δ

flytekit/common/mixins/launchable.py
72.22% <0.00%> (ø)

flytekit/common/tasks/task.py
66.14% <37.50%> (-9.90%)
:arrow_down:

flytekit/common/tasks/presto_task.py
73.80% <42.85%> (ø)

flytekit/__init__.py
100.00% <100.00%> (ø)

flytekit/models/common.py
94.15% <100.00%> (ø)

...ests/flytekit/unit/common_tests/tasks/test_task.py
97.95% <100.00%> (+0.59%)
:arrow_up:

flytekit/models/presto.py
76.19% <0.00%> (ø)

Continue to review full report at Codecov.

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

Is there an example execution of single task from command line / jupyter?

Is there an example execution of single task from command line / jupyter?

@kumare3 adding docs separately :) https://github.com/lyft/flyte/pull/354

@katrogan do we want to add the example notebook that you had to this? Or maybe I will just update my raw container task example to use your single task execution :)

@kumare3 do we have a designated place in the docs or flytekit for adding example notebooks?

@kumare3 do we have a designated place in the docs or flytekit for adding example notebooks?

I am actually creating one in my Raw Container PR. For now I think you can continue merge it, I will use it in my PR


Support deploying AYS Portal in remote/seperate container

Add parameters to the AYS Portal config.yaml for IP address and port number of the AYS Server RESTful API in order to support the below setup, allowing the portal to run in a separate container:

software version
9.2


Upgrade to Cassandra 3.11.13/4.0.4

We shouldn't be holding these releases this long. We need 4.0.4 / 3.11.13 images.

@burmanm Sorry about that, I should have merged this already.


fix(conf) cassandra consistency changes that were reported after #4772 was merged

Summary
Fixes cassandra consistency changes that were reported after #4772 was merged.

Moving this out of the 1.3.0 milestone, replacing by #4811 instead.

These changes should go in when the original PR this builds on gets reworked.


[6249] Wire up progress to track placements flow

Context
https://trello.com/c/K1yETwNB/6249-add-a-trainee-page-placements-task-list
Changes proposed in this pull request
https://github.com/DFE-Digital/register-trainee-teachers/assets/616080/ddd87e6d-5825-4931-ae28-75dafe54a188

Wires up the progress service to track the placements section

Guidance to review

Choose a placements enabled route
Go through placements (select no) and go back to review draft page
Go through again and confirm details then go back and check it says completed

This still needs to be wired up properly for https://github.com/DFE-Digital/register-trainee-teachers/pull/3698 likely through a composite validator object to check for the different parts (as we do for other multi step sections) but will be handled once it's merged in.

 Add a trainee page - placements Task list


Use methods in all controller in the same order (Let's make controller development a joy)

Hi,
Working on an extension of JTC (#140), it's very disturbing (or at least disconcerting) not having unified members/methods order between the different controllers and the controller_interface. The issue I have is jumping between different states of the controller and having to check all the time at which lifecycle state controller is, i.e., which members are filled and which not...
I propose to restructure controller_interface methods to the execution order and keep that throughout this repository.
P.S. I know this is a very unproductive request. Still, IMHO it's important to increase understanding and finally acceptance of the library...
Any thoughts?

I propose the following order:

constructor
init
configure()
command_interface_configuration()
state_interface_configuration()
activate
update
deactivate
cleanup
shutdown

I've just read this issue for the first time, and agree with you ;)
on_error() is new since 2021, but this can go to the end


Uninstall Snaptool

Your Idea
i used better alternative tool like shareX
SophiApp Version
No response
Windows Version
Windows 11 22H2
Comments
No response

Enhancement in what? :)


Upgrading to latest Cinder API

Hi James!
I'm using Cinder-glTF in my project and recently I've upgraded to latest Cinder v0.9.1. There were couple of compilation errors in Cinder-glTF that I've already fixed and put in a separate branch.
If you could give me access to this repository then I can create PR on you. Or you can fix errors on your own or I can send you a patch :)
Looking forward for your feedback.
Thanks,
Andrey.

Hi Andrey, thanks for fixing errors on the repo. Could you fork it and then do a pull request? I think that's the typical way to do it. Thanks and let me know if you have any problems!

Hi James! Sorry I didn't mention that I could fork. PR is open, cannot assign you to review though. Could you please review it? Thanks!

It's updated now. thanks


Cannot Download files from thor link, fail2ban problem

Downloading stops halfway, and cannot resume. I guess fail2ban blocks ip address.
are the files hosted someplace else?

Fail2Ban will allow the re-connecting in 15 min (I think) -- please try again.
Also, it only blocks if your cancel / somehow the download fails.
The files are not hosted anywhere else.

Using a tor browser helped me download the files.
You are very prompt to support, Thanks a lot


Logging

Swap the warnings package out with the logging package, which will also replace any print statements with better logging methods for INFO, DEBUG, WARNING, and ERROR logging.

Hello @stadmill @ltorres6 Can i work on this?

Take a crack at it if you'd like!