"cf cs" ERRORS

I have mongodb running at localhost:27017 and able to connect to it using robomongo.
Also, I deploy cloudfoundry-service-broker to CF and register this app as a mongo service broker.
"cf apps" returns

mongodb-cf-service-broker   started           1/1         1G       1G     mongodb-cf-service-broker.myhost.com

After register with CF, "cf marketplace" returns

Mongo DB   Default Mongo Plan*   A simple MongoDB service broker implementation

However, "cf cs "Mongo DB" "Default Mongo Plan" testMongodbInstance" returns follow ERROR
I've tried to look at this error for a while; but could not find out why. Command using curl to query for the broker's catalog is successful and return the catalog.
Any tips?
Thanks
Beth
--------ERROR--------
Server error, status code: 502, error code: 10001, message: Service broker error: Timed out after 10000 ms while waiting to connect. Client view of cluster state is {type=Unknown, servers=[{address=localhost:27017, type=Unknown, state=Connecting, exception={com.mongodb.MongoException$Network: Exception opening the socket}, caused by {java.net.ConnectException: Connection refused}}]; nested exception is com.mongodb.MongoTimeoutException: Timed out after 10000 ms while waiting to connect. Client view of cluster state is {type=Unknown, servers=[{address=localhost:27017, type=Unknown, state=Connecting, exception={com.mongodb.MongoException$Network: Exception opening the socket}, caused by {java.net.ConnectException: Connection refused}}]

The service broker running on CF must be able to talk to a MongoDB server. It won't be able to talk to the server on localhost:27017 because the MongoDB server isn't running on the same localhost as the container the app is running in. You'll need to run the MongoDB server with a real hostname that the broker app can access.

Scott - I have CF running on guest VM, and MongoDB runs on the host.  Will this setting work? If not, I can put MongoDB on a guest VM

A localhost hostname isn't likely to work unless the service broker app and the MongoDb server are running on the same VM and in the same container. If you are pushing the broker app to CF, you can't make that happen since CF controls the container the broker app runs in. You need to configure the broker to look for the mongo server on a hostname other than localhost.


Error in the display of yields: APY instead of APR

What happened:
In the new wallet the display of the returns is still wrong. The returns are APR and not APY.
What you expected to happen:
You only have to change APY in APR... thats all.
How to reproduce it (as minimally and precisely as possible):
Open the wallet.
What are your environment parameters?

DeFi Wallet Version: All versions
Operating System (OS): All OS

Anything else we need to know?:

Hi @Kolibri1990 , thanks for your feedback, the team is aware and are currently investigating.

I noticed the web site (https://defichain.com/dex/) shows the rate as APR but the App and the screenshots show APY.
I don't know which is correct. Could someone explain why one or the other?
I have looked around but I can't find which is the number of periods for the calculation. Is it monthly? Daily? Each 12 hours? (https://app.cakedefi.com/ says Rewards every 12 hours)

Hey @diegorodriguezv
As with cake, the return on LM on the DeFi Wallet is an APR and not an APY.
It is wrong on the DEX page (https://dex.defichain.com/mainnet/pool) and also the DeFi Wallet.
The values are right but the naming is wrong.

Hi @diegorodriguezv you can ask the community DeFiChain Telegram (EN) on such enquiries.
Thanks @Kolibri1990 !

Hi @Kolibri1990 @diegorodriguezv @wmbst @adrian-schnell v2.4.0 is out, this is a mandatory update. Please read through the release notes before updating. This comment is to notify you about the update.

When is this going to happen? APY is wrong and misleading.

so to be clear, app should be also showing APR, as the website already shows correctly that is APR

Hi @sandrich , the team is working on it, kindly refer to DeFiChain Announcements (EN) for the latest updates. Thank you.

Hi, we have updated this on the latest app release v2.4.2, please have a look. thank you - https://defichain.com/downloads/


Fix symbol checking test when compiled with debug symbols

🦟 Bug fix
Summary
The test that checks for prefixed binary symbols was broken when compiled with DebWithRelInfo since it was checking debugging symbols that broke the heuristics used.
The commit fixes it doing a couple of actions:

Include the length of the namespace sdf according to the mangling rules: 3sdf
Check only dynamic symbols being exported

Checklist

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

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

Tested (pending):

Tested (pending):

trying again with different branch parameters

 https://build.osrfoundation.org/job/sdformat15-debbuilder/530/

I was also working on this and found that adding the --extern-only flag to nm fixes the issue. From what I can understand, the issue is that debbuilders enable LTO which causes some debug symbols to be added to the shared library. These symbols contain the file names, one of which is :
0000000000f9c8ce N sdformat15_get_install_prefix_impl.cc.b80149f8

This causes a false negative on the versioned symbol test.
I tested by adding set(CMAKE_INTERPROCEDURAL_OPTIMIZATION TRUE) in the root CMakeLists.txt file and was able to reproduce the test failure locally.
In general, it would be good to enable LTO on our libraries so these types of issues are caught at the PR stage. I think this is the third time this LTO stuff has bit us.

In general, it would be good to enable LTO on our libraries so these types of issues are caught at the PR stage. I think this is the third time this LTO stuff has bit us.

should we do this in the action-gz-ci workflow?

In general, it would be good to enable LTO on our libraries so these types of issues are caught at the PR stage. I think this is the third time this LTO stuff has bit us.

should we do this in the action-gz-ci workflow?

I was thinking of enabling it via CMake, maybe in gz-cmake or on a per-project basis. That way local development will also use the same flags.

@Mergifyio backport sdf15 sdf14


Feature/add new deep link sample

Adds a new Teams sample app demonstrating the use of deep links to pass values to tab apps.
Description
This sample tab app shows how to retrieve data that was passed through a deep link. It also demonstrates the creation of two types of deep links: one for opening the app in Teams, and another for opening the app directly in the browser using its public URL. This dual-support enables information to be passed to the app both inside and outside of Teams.
Background
Deep links facilitate passing data to an app when it loads, enabling operations like internal page navigation and database searches. Using deep links, you can quickly lead users to specific content in your application or perform other app logic.
However, Teams requires a unique format for deep links. If an app needs to support both Teams and standalone access, then two different URL formats are needed. This sample app is designed to help other developers understand and implement deep linking as a way to pass values to their Teams tab apps.
Related Issue: https://github.com/OfficeDev/Microsoft-Teams-Samples/issues/1143

Hello @Prithvi-MSFT , @Pawank-MSFT , thank you very much for approving and merging my submission!


Dropdown module updates.

Hello.
I added loading props to the dropdown module with the example in the doc.
Also, there was an error with the dropdown module.
I made an adjustment to fix it.
This error happens if use key up/down arrow when the options list is empty.
Here is the full stacktrace of the error from my browser console:
Dropdown.jsx?3fbe:417 Uncaught TypeError: Cannot read property 'value' of undefined
    at VueComponent.handleKeyDown (Dropdown.jsx?3fbe:417)
    at eval (index.js?9ef6:48)
    at invoker (vue.esm.js?efeb:2027)
    at HTMLDivElement.fn._withTask.fn._withTask (vue.esm.js?efeb:1826)
handleKeyDown @ Dropdown.jsx?3fbe:417
(anonymous) @ index.js?9ef6:48
invoker @ vue.esm.js?efeb:2027
fn._withTask.fn._withTask @ vue.esm.js?efeb:1826

Thanks!


added value argument in set_{option,properties}_string fallbacks

The option and property setter fallbacks to respective _string functions was missing the value argument. Presumably caused by copying the fallback code from the respective getters.

Thanks for this! Out of interest, are you actually using aesop, or are you just interested in the mpv wrapper?
I ask because I've considered breaking the mpv wrapper out into a separate library (and putting it on pypi), and I'd appreciate someone else's thoughts on the matter.

I and @lars-tiede (I am hoping github CCs him) at a UiT (a university in Norway) are working on a synchronized video player for this project. As a part of this project we are trying to utilize a scriptable video player (e.g. mpv) to implement synchronized video clients, and as such we are only using the python mpv wrapper.
This turned out to be a better starting point than the python-mpv project. It included a working example of how to use the wrapper, so it made it simpler to create a proof of concept application that actually played something. Since we are only using the mpv wrappers it would be nice to have them available in a standalone library.


Reduce docker images from 1GB to 251MB

Django-eth-events dependency was updated too

Coverage remained the same at 87.098% when pulling d3c6b62e914c711c2b9b9bbda2e1aacdc635afba on develop into 20beb036c5051b7258181cf72b92c3d66cd55ddc on master.


Add license blob to the top of all source files

This PR adds the Apache 2 license blob to the top of all source code files. This PR closes #33.

Codecov Report

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

@@            Coverage Diff             @@
##           master      #35      +/-   ##
==========================================
- Coverage   30.73%   30.54%   -0.20%
==========================================
  Files           4        4
  Lines         231      203      -28
==========================================
- Hits           71       62       -9
+ Misses        151      132      -19
  Partials        9        9

Impacted Files
Coverage Δ

internal/server/about.go
100.00% <ø> (ø)

internal/server/api.go
35.29% <ø> (-0.24%)
:arrow_down:

internal/server/cache.go
47.05% <ø> (-1.22%)
:arrow_down:

pkg/mms/events.go
10.25% <ø> (+0.25%)
:arrow_up:

Continue to review full report at Codecov.

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


add: gbfs and astar search algorithms

Describe the algorithm/code
python code for gbfs and astar search algorithms
Do you want to work on this feature?

[X] I am willing to implement this feature.

You can work on this issue!


how can i set the  focus  follow mouse off

thanks a lot

You can disable this by removing the line
chunkc core::load ffm.so from your .chunkwmrc file.

oh i see it  thank you
can i ask one more question

how can  i  hide the   close minimize maximize buttons


[SPARK-5640] Synchronize ScalaReflection where necessary

Can one of the admins verify this patch?

Review by @marmbrus

ok to test

Test build #26923 has started for   PR 4431 at commit c5da21e.

This patch merges cleanly.

Test build #26923 has finished for   PR 4431 at commit c5da21e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26923/
Test PASSed.

Thanks! Merged to master and 1.3


$AlterTable->dropConstraint() on MySQL,There is no support for "DROP CONSTRAINT"

I'm dropping a constraint on mysql5.6, code:
$AlterTable = new Ddl\AlterTable($test_table_name);
$AlterTable->dropConstraint('text_UniqueKey');

echo $sql->buildSqlString($AlterTable,$adapter);

$adapter->query(
    $sql->buildSqlString($AlterTable,$adapter),
    $adapter::QUERY_MODE_EXECUTE
);

And this code output :
ALTER TABLE `test` DROP CONSTRAINT `text_UniqueKey`

Here is the problem, Mysql nerver support the Syntax "DROP CONSTRAINT", so it throw an error :
SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'CONSTRAINT `text_UniqueKey`' at line 2

Note: $adapter config array is
'db' => array(
    'driver' => 'Pdo_Mysql',
    'hostname' => 'localhost',
    'username' => 'root',
    'password' => 'abc123',
    'database' => 'easypay',
)

Help ! What to do now ???

please anyone help @_@

open bug report on https://github.com/zendframework/zend-db/issues

I had done this on  https://github.com/zendframework/zend-db/issues/36
hope someone repair it.@_@


Reference acorns

We need to agree on the first 5 that we should do.
MySQL seems to be a lock.
Acorns should showcase key features of acron, like ability to perform operations such as backup and restore.

This is getting tracked and completed out-of-band. no point in keeping this issue open


utf converter seems to be slow

According to http://stackoverflow.com/questions/28359949/how-to-convert-binary-data-to-utf8-string-after-dart2js utf8 encoding/decoding is slow in dart2js.
Load:

import 'dart:convert';
import 'package:archive/archive.dart';
import 'package:crypto/crypto.dart';
var base64 = CryptoUtils.base64StringToBytes(window.localStorage[storageName]);
var decompress = new GZipDecoder().decodeBytes(base64);
storage = JSON.decode(new Utf8Decoder().convert(decompress));

Save:

var g = JSON.encode(storage);
List<int> bz2 = new GZipEncoder().encode(new Utf8Encoder().convert(g));
window.localStorage[storageName] = CryptoUtils.bytesToBase64(bz2);

Consider using TextEncoder / TextDecoder on browsers that support this operation.
It might still be necessary to fall back on the current implementation if there is a mismatch in error handling.


feat: improve libpod API support

What does this PR do?
This PR improves use cases where LibPod is used by Podman desktop by:

adding support for some additinal configuration options that were not previously translated from the input options
forcing the use of LibPod if an nvidia gpu is requested on linux.  Requesting the device "nvidia.com/gpu=all" only works through the LibPod API, not the docker compatibility API. Therefore, force the use of LibPod over the compatiliby API if this device is requested.

These changes were needed for me to get GPU acceleration working on linux for podman-desktop-extension-ai-lab, however, I think they are just general improvements that are useful on their own in cases where containers are started and LibPod would have already been used as the API.
Screenshot / video of UI
N/A
What issues does this PR fix or reference?

How to test this PR?
The tests were updated to cover the additions in terms of the addional options translated into the podman options.
For live test, I tested this PR along with this PR to podman-desktop-extension-ai-lab  - https://github.com/containers/podman-desktop-extension-ai-lab/pull/2180, by creating a model service and validating that the service reported GPU acceleration, and used the GPU when submitted requests to the service.  I also tested with the chatbot Node.js recipe I was working on that it got GPU acceleration as well.

[X] Tests are covering the bug fix or the new feature

I should have also mentioned that the change to the entrypoint was need to match the spec in https://docs.podman.io/en/latest/_static/api.html#tag/containers/operation/ContainerCreateLibpod and it did not work as a single string. My assumption is that nothing within podman desktop had used the entrypoint passing in a string in the  options (the compat options allow either a string or array of strings)).

Pushed change to address the typecheck failures.
Will now work on splitting out the different changes into 4 PRs

@benoitf first PR - https://github.com/podman-desktop/podman-desktop/pull/10178

@benoitf second PR  - https://github.com/podman-desktop/podman-desktop/pull/10179

third PR - https://github.com/podman-desktop/podman-desktop/pull/10180

@benoitf I think that the fourth PR needs the third one which adds the initial device support (https://github.com/podman-desktop/podman-desktop/pull/10180) so I'll wait to create that one until the third PR hopefully lands

@benoitf here is the last PR of the four - https://github.com/podman-desktop/podman-desktop/pull/10251

Ok, all four PRs covering what this had have landed. @benoitf many thanks in your helps and suggestions, closing.

@mhdawson thanks for the split across multiple chunks and rebasing each of them 👍


Make name prop accept variables

Instead of having to hard code the name like this:
<download-excel :data=output type="xlsx" worksheet="E-Mails" name="data.xlsx">
            <button>Download Excel </button>
</download-excel>

I would like to dynamically specify the name of the created xlsx like this:
<download-excel :data=output type="xlsx" worksheet="E-Mails" :name=myNameVar>
            <button>Download Excel </button>
</download-excel>

This does not seem to work at the moment.

Closing these issue


VMR servicing - Incremental package servicing

Runtime has an incremental servicing model which only publishes packages that changed in a given servicing cycle. For the VMR, we are always live building and therefore downstream repos need all runtime packages produced, not just the ones that changed.
We need to come up with a solution to support incremental package servicing. I see a few options:

Mark the packages that don't ship in a given servicing non-shipping
Let runtime generate a file that lists the packages to ship

There are probably more and I'm not sure if 1) will work.
cc @ericstj @carlossanlop @mmitche

Let repo build produce the shipping packages, everything from VMR is just ignored.  That's effectively what source-build does today.
Keep incremental servicing in place and allow downstream repos to restore packages that aren't shipping.

Closing as not planned for the initial release of the VMR as runtime doesn't do incremental servicing anymore and we aren't aware of any other repository that needs such a functionality.


feat: Modal GM-179

Overview

New

Modal component for abstract Modal dialogs that are not binary flows.
Moves Modal / Dialog / Overlay / ModalDeprecated to a new Molecule section Modals.
Creates shared components and types for Modal and Dialog for shared layout configuration and spacing.
Creates a new Modal documentation page with sizing examples.
Adds a fluid size for standard Modals that responds to content but is capped at the viewport.
Updates Overlays to accept a shroud boolean prop to add an opaque background.

Modal Usage
<Modal title="My Modal Title" onRequestClose={() => {}}>
  Arbitrary content for arbitrary features!
</Modal>

Overlay shroud
<Overlay shroud>
// Content
</Overlay>

Sizes

PR Checklist

[x] Related to designs: figma
[x] Related to JIRA ticket: https://codecademy.atlassian.net/browse/GM-179
[x] I have run this code to verify it works
[x] This PR includes unit tests for the code change

📬Published Alpha Packages:@codecademy/gamut-kit@0.5.22-alpha.cea900.0@codecademy/gamut-labs@19.19.8-alpha.cea900.0@codecademy/gamut@35.14.1-alpha.cea900.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6111affa1612e155a76f2832--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.5.22-alpha.6b6d23.0@codecademy/gamut-labs@19.19.8-alpha.6b6d23.0@codecademy/gamut@35.14.1-alpha.6b6d23.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6111b1a11bf4865273e6def9--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.5.22-alpha.7dcd16.0@codecademy/gamut-labs@19.19.8-alpha.7dcd16.0@codecademy/gamut@35.14.1-alpha.7dcd16.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6112905c801cb98e6e5cee78--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.5.22-alpha.ce9852.0@codecademy/gamut-labs@19.19.8-alpha.ce9852.0@codecademy/gamut@35.14.1-alpha.ce9852.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6112c91a148ef57f1e4196bb--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.5.22-alpha.bb4bd8.0@codecademy/gamut-labs@19.19.8-alpha.bb4bd8.0@codecademy/gamut@35.14.1-alpha.bb4bd8.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6112d74b044c78d7fdff5f0c--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.5.22-alpha.da7b6f.0@codecademy/gamut-labs@19.19.8-alpha.da7b6f.0@codecademy/gamut@35.14.1-alpha.da7b6f.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6112e622044c78eac0ff5e2e--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.5.23-alpha.3dc772.0@codecademy/gamut-labs@19.19.9-alpha.3dc772.0@codecademy/gamut@36.0.1-alpha.3dc772.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6112eca25b77c6878e0009f8--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.5.23-alpha.9f4b80.0@codecademy/gamut-labs@19.19.9-alpha.9f4b80.0@codecademy/gamut@36.0.1-alpha.9f4b80.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://61140fcda7bc070091568629--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.5.24-alpha.b8d1ec.0@codecademy/gamut-labs@19.19.10-alpha.b8d1ec.0@codecademy/gamut@36.0.2-alpha.b8d1ec.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://61141bf28036cb00992f0e51--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.5.24-alpha.fe746f.0@codecademy/gamut-labs@19.19.10-alpha.fe746f.0@codecademy/gamut@36.0.2-alpha.fe746f.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://611437cc6c4fa51621f0bd6d--gamut-preview.netlify.appDeploy Logs

Looks great so far -- I tested in the monolith!
I'm having trouble viewing the code for some of the stories -- example for the modal size variants; and when I try to switch to "canvas" view the page breaks
https://611437cc6c4fa51621f0bd6d--gamut-preview.netlify.app/storybook/?path=/docs/molecules-modals-modal--medium

📬Published Alpha Packages:@codecademy/gamut-kit@0.5.29-alpha.00b952.0@codecademy/gamut-labs@19.20.4-alpha.00b952.0@codecademy/gamut@36.2.1-alpha.00b952.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6116b77ff3ac540096a96cdf--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.5.29-alpha.3de45d.0@codecademy/gamut-labs@19.20.4-alpha.3de45d.0@codecademy/gamut@36.2.1-alpha.3de45d.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6116c0e543bd000a3a58e4aa--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.5.30-alpha.86930f.0@codecademy/gamut-labs@19.20.5-alpha.86930f.0@codecademy/gamut@36.3.1-alpha.86930f.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6116cd0ed7f79400915cb2e5--gamut-preview.netlify.appDeploy Logs


APT whitelist request for jq  in trusty

To process JSON output from GitHub API.

jq should be pre-installed in all the images.


Empty wireguard installation $VER-linux-amd64.tar.gz with 1kb size is downloaded

############
Hello everyone, since 2.05.22 I have a problem when installing the flat on Linux Debian 11/Ubuntu.
The download of the installation file for Wireguard configuration is downloaded "empty" with only 1 kb to the VPS with Linux:
wireguard-ui--linux-amd64.tar.gz
wireguard-ui-v0.3.7-linux-amd64.tar.gz
The problem is when executing the update.sh "Creating the wireguard ui download and update script".
An empty wireguard installation $VER-linux-amd64.tar.gz with 1kb size is probably downloaded.
This can no longer be extracted logically:
cd /etc/wireguard; ./update.sh
downloading wireguard-ui
extracting tar: This does not look like a tar archive
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
restarting wgui-web.service
#####################################
#My Script: WireGuard UI
#First we create the Systemd Service Unit.
cat < /etc/systemd/system/wgui-web.service
[Unit]
Description=WireGuard UI
[Service]
Type=simple
ExecStart=/etc/wireguard/start-wgui.sh
[Install]
WantedBy=multi-user.target
EOF
#WireGuard UI Download and Update Script:
cat < /etc/wireguard/update.sh
#!/bin/bash
VER=$(curl -s https://github.com/ngoduykhanh/wireguard-ui/releases/latest | cut -d "/" -f8 | cut -d """ -f1)
echo "downloading wireguard-ui $VER"
curl -sL "https://github.com/ngoduykhanh/wireguard-ui/releases/download/$VER/wireguard-ui-$VER-linux-amd64.tar.gz" -o wireguard-ui-$VER-linux-amd64.tar.gz
echo -n "extracting "; tar xvf wireguard-ui-$VER-linux-amd64.tar.gz
echo "restarting wgui-web.service"
systemctl restart wgui-web.service
EOF
#Now we can run the Wireguard UI Update Script for the first time. The download starts automatically and Wireguard's web interface is started.
chmod +x /etc/wireguard/update.sh
cd /etc/wireguard; ./update.sh
#####################################
Error:
cd /etc/wireguard; ./update.sh
downloading wireguard-ui
extracting tar: This does not look like a tar archive
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
restarting wgui-web.service

This should work:
VER=$(curl -ILs -o /dev/null -w %{url_effective} https://github.com/ngoduykhanh/wireguard-ui/releases/latest | cut -d "/" -f8)

TOP, Thank you ;)


what if the page elements don't have ids??

Is there any other way to identify elements that don't have ids??

yes, plenty of other ways
http://selendroid.io/native.html

When I use uiautomatorviewer, am not even able to highlight/hover over the element. But the button exists on the page. any thoughts ?


fw-ectool: unstable-2022-12-03 -> 0-unstable-2023-12-15, switch upstream

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Tested most functionalities, e.g. changing fan curves, checking battery.

This was a breaking change for me (Framework 13th gen Intel).
$ sudo nix run nixpkgs/nixos-23.11#fw-ectool led power red
$ sudo nix run nixpkgs#fw-ectool led power red
Missing Chromium EC memory map.
Cannot find I2C adapter
Unable to establish host communication
Couldn't find EC
$

This was a breaking change for me (Framework 13th gen Intel).

May you try different interfaces? e.g. ectool --interface lpc led power red

This was a breaking change for me (Framework 13th gen Intel).

May you try different interfaces? e.g. ectool --interface lpc led power red

Same issue (the older version with lpc works, but not the newer one)
$ sudo nix run nixpkgs#fw-ectool -- --interface dev led power off
Unable to establish host communication
Couldn't find EC
$ sudo nix run nixpkgs#fw-ectool -- --interface i2c led power off
Cannot find I2C adapter
Unable to establish host communication
Couldn't find EC
$ sudo nix run nixpkgs#fw-ectool -- --interface lpc led power off
Missing Chromium EC memory map.
Unable to establish host communication
Couldn't find EC
$ sudo nix run nixpkgs/nixos-23.11#fw-ectool -- --interface dev led power off
Unable to establish host communication
Couldn't find EC
$ sudo nix run nixpkgs/nixos-23.11#fw-ectool -- --interface i2c led power off
Cannot find I2C adapter
Unable to establish host communication
Couldn't find EC
$ sudo nix run nixpkgs/nixos-23.11#fw-ectool -- --interface lpc led power off
$

Let's revert this for now.

This was a breaking change for me (Framework 13th gen Intel).
$ sudo nix run nixpkgs/nixos-23.11#fw-ectool led power red
$ sudo nix run nixpkgs#fw-ectool led power red
Missing Chromium EC memory map.
Cannot find I2C adapter
Unable to establish host communication
Couldn't find EC
$

I tried asking upstream and this was the response:
> Can someone test this command on a 13th gen intel cpu?
> sudo ectool led power red .
> ...

Unfortunately, the modern devices don’t expose support for red on the power LED.
That having been said, you still shouldn’t get that error.
Can you check whether the module cros_ec_lpcs is loaded?
If not, no EC communication will work. :slight_smile:

Source: official framework forum

The cros_ec_lpcs module shows up in lsmod. I'm not sure what changed, but I tried again with the same package and same commit hash, and also by building the upstream code from source, and both times it worked. Maybe some driver update somewhere fixed it? Anyway, now I don't need to worry about upstream breaking https://github.com/io12/nixos-framework-led.

@NickCao
Can we bring back this package and update it to the latest version?

@NickCao Can we bring back this package and update it to the latest version?

Revived in https://github.com/NixOS/nixpkgs/pull/312063, please test.

@NickCao Can we bring back this package and update it to the latest version?

Revived in #312063, please test.

I tested and it works for everything I use it for.


Update ReadMe

Signed-off-by: Jens<EMAIL_ADDRESS>
PR checklist

[ ] Ensure you have added or ran the appropriate tests for your PR.
[ ] DCO signed

What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Can we merge now? @jonycfu so I can continue with some marketing campaigns


AddReference between containers

Hey
I'm trying to connect to container together with WithReference. But I'm not able to get the AllocatedEndpointAnnotation.
Here is a very simple example. (I'm aware that this would not make a lot of sense ;) )
var redis = builder.AddRedisContainer("redis");
var rabbitMq = builder.AddRabbitMQContainer("rabbitmq");

rabbitMq.WithReference(redis);

When I start the application locally on my mac. I get the error:  Aspire.Hosting.DistributedApplicationException: Redis resource does not have endpoint annotation.
This is the same behavior when I try to reference my custom containers.

When I start the application locally on my mac. I get the error: Aspire.Hosting.DistributedApplicationException: Redis resource does not have endpoint annotation.

I'm not sure how you got this exception. Can you share all of your code and the stack trace?

This is the full code:
using Test.cloud.AppHost;
using System.Net;

var builder = DistributedApplication.CreateBuilder(args);

var redis = builder.AddRedisContainer("redis");
var rabbitMq = builder.AddRabbitMQContainer("rabbitmq");

rabbitMq.WithReference(redis);

builder.Build().Run();

Full stack trace:
      Aspire.Hosting.DistributedApplicationException: Redis resource does not have endpoint annotation.
         at Aspire.Hosting.ApplicationModel.RedisContainerResource.GetConnectionString() in /_/src/Aspire.Hosting/Redis/RedisContainerResource.cs:line 20
         at Aspire.Hosting.ResourceBuilderExtensions.<>c__DisplayClass8_0`1.<WithReference>b__0(EnvironmentCallbackContext context) in /_/src/Aspire.Hosting/Extensions/ResourceBuilderExtensions.cs:line 149
         at Aspire.Hosting.Dcp.ApplicationExecutor.CreateContainersAsync(IEnumerable`1 containerResources, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/ApplicationExecutor.cs:line 564
         at Aspire.Hosting.Dcp.ApplicationExecutor.CreateContainerSingletonsAsync(CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/ApplicationExecutor.cs:line 108
         at Aspire.Hosting.Dcp.ApplicationExecutor.RunApplicationAsync(CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/ApplicationExecutor.cs:line 74
         at Aspire.Hosting.Dcp.DcpHostService.StartAsync(CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/DcpHostService.cs:line 83
         at Microsoft.Extensions.Hosting.Internal.Host.<StartAsync>b__15_1(IHostedService service, CancellationToken token)
         at Microsoft.Extensions.Hosting.Internal.Host.ForeachService[T](IEnumerable`1 services, CancellationToken token, Boolean concurrent, Boolean abortOnFirstException, List`1 exceptions, Func`3 operation)
Could not stop container 'rabbitmq': k8s.Autorest.HttpOperationException: Operation returned an invalid status code 'NotFound', response body {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"containers.usvc-dev.developer.microsoft.com \"rabbitmq\" not found","reason":"NotFound","details":{"name":"rabbitmq","group":"usvc-dev.developer.microsoft.com","kind":"containers"},"code":404}

   at k8s.Kubernetes.SendRequestRaw(String requestContent, HttpRequestMessage httpRequest, CancellationToken cancellationToken)
   at k8s.AbstractKubernetes.ICustomObjectsOperations_DeleteClusterCustomObjectWithHttpMessagesAsync[T](String group, String version, String plural, String name, V1DeleteOptions body, Nullable`1 gracePeriodSeconds, Nullable`1 orphanDependents, String propagationPolicy, String dryRun, IReadOnlyDictionary`2 customHeaders, CancellationToken cancellationToken)
   at k8s.AbstractKubernetes.k8s.ICustomObjectsOperations.DeleteClusterCustomObjectWithHttpMessagesAsync(String group, String version, String plural, String name, V1DeleteOptions body, Nullable`1 gracePeriodSeconds, Nullable`1 orphanDependents, String propagationPolicy, String dryRun, IReadOnlyDictionary`2 customHeaders, CancellationToken cancellationToken)
   at Aspire.Hosting.Dcp.KubernetesService.<>c__DisplayClass12_0`1.<<DeleteAsync>b__0>d.MoveNext() in /_/src/Aspire.Hosting/Dcp/KubernetesService.cs:line 109
--- End of stack trace from previous location ---
   at Aspire.Hosting.Dcp.KubernetesService.ExecuteWithRetry[TResult](DcpApiOperationType operationType, String resourceType, Func`2 operation, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/KubernetesService.cs:line 198
   at Aspire.Hosting.Dcp.ApplicationExecutor.DeleteResourcesAsync[RT](String resourceName, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/ApplicationExecutor.cs:line 686
Could not stop service 'redis': k8s.Autorest.HttpOperationException: Operation returned an invalid status code 'NotFound', response body {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"services.usvc-dev.developer.microsoft.com \"redis\" not found","reason":"NotFound","details":{"name":"redis","group":"usvc-dev.developer.microsoft.com","kind":"services"},"code":404}

   at k8s.Kubernetes.SendRequestRaw(String requestContent, HttpRequestMessage httpRequest, CancellationToken cancellationToken)
   at k8s.AbstractKubernetes.ICustomObjectsOperations_DeleteClusterCustomObjectWithHttpMessagesAsync[T](String group, String version, String plural, String name, V1DeleteOptions body, Nullable`1 gracePeriodSeconds, Nullable`1 orphanDependents, String propagationPolicy, String dryRun, IReadOnlyDictionary`2 customHeaders, CancellationToken cancellationToken)
   at k8s.AbstractKubernetes.k8s.ICustomObjectsOperations.DeleteClusterCustomObjectWithHttpMessagesAsync(String group, String version, String plural, String name, V1DeleteOptions body, Nullable`1 gracePeriodSeconds, Nullable`1 orphanDependents, String propagationPolicy, String dryRun, IReadOnlyDictionary`2 customHeaders, CancellationToken cancellationToken)
   at Aspire.Hosting.Dcp.KubernetesService.<>c__DisplayClass12_0`1.<<DeleteAsync>b__0>d.MoveNext() in /_/src/Aspire.Hosting/Dcp/KubernetesService.cs:line 109
--- End of stack trace from previous location ---
   at Aspire.Hosting.Dcp.KubernetesService.ExecuteWithRetry[TResult](DcpApiOperationType operationType, String resourceType, Func`2 operation, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/KubernetesService.cs:line 198
   at Aspire.Hosting.Dcp.ApplicationExecutor.DeleteResourcesAsync[RT](String resourceName, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/ApplicationExecutor.cs:line 686
Could not stop service 'rabbitmq_tcp': k8s.Autorest.HttpOperationException: Operation returned an invalid status code 'NotFound', response body {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"services.usvc-dev.developer.microsoft.com \"rabbitmq_tcp\" not found","reason":"NotFound","details":{"name":"rabbitmq_tcp","group":"usvc-dev.developer.microsoft.com","kind":"services"},"code":404}

   at k8s.Kubernetes.SendRequestRaw(String requestContent, HttpRequestMessage httpRequest, CancellationToken cancellationToken)
   at k8s.AbstractKubernetes.ICustomObjectsOperations_DeleteClusterCustomObjectWithHttpMessagesAsync[T](String group, String version, String plural, String name, V1DeleteOptions body, Nullable`1 gracePeriodSeconds, Nullable`1 orphanDependents, String propagationPolicy, String dryRun, IReadOnlyDictionary`2 customHeaders, CancellationToken cancellationToken)
   at k8s.AbstractKubernetes.k8s.ICustomObjectsOperations.DeleteClusterCustomObjectWithHttpMessagesAsync(String group, String version, String plural, String name, V1DeleteOptions body, Nullable`1 gracePeriodSeconds, Nullable`1 orphanDependents, String propagationPolicy, String dryRun, IReadOnlyDictionary`2 customHeaders, CancellationToken cancellationToken)
   at Aspire.Hosting.Dcp.KubernetesService.<>c__DisplayClass12_0`1.<<DeleteAsync>b__0>d.MoveNext() in /_/src/Aspire.Hosting/Dcp/KubernetesService.cs:line 109
--- End of stack trace from previous location ---
   at Aspire.Hosting.Dcp.KubernetesService.ExecuteWithRetry[TResult](DcpApiOperationType operationType, String resourceType, Func`2 operation, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/KubernetesService.cs:line 198
   at Aspire.Hosting.Dcp.ApplicationExecutor.DeleteResourcesAsync[RT](String resourceName, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/ApplicationExecutor.cs:line 686
Could not stop service 'rabbitmq_management': k8s.Autorest.HttpOperationException: Operation returned an invalid status code 'NotFound', response body {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"services.usvc-dev.developer.microsoft.com \"rabbitmq_management\" not found","reason":"NotFound","details":{"name":"rabbitmq_management","group":"usvc-dev.developer.microsoft.com","kind":"services"},"code":404}

   at k8s.Kubernetes.SendRequestRaw(String requestContent, HttpRequestMessage httpRequest, CancellationToken cancellationToken)
   at k8s.AbstractKubernetes.ICustomObjectsOperations_DeleteClusterCustomObjectWithHttpMessagesAsync[T](String group, String version, String plural, String name, V1DeleteOptions body, Nullable`1 gracePeriodSeconds, Nullable`1 orphanDependents, String propagationPolicy, String dryRun, IReadOnlyDictionary`2 customHeaders, CancellationToken cancellationToken)
   at k8s.AbstractKubernetes.k8s.ICustomObjectsOperations.DeleteClusterCustomObjectWithHttpMessagesAsync(String group, String version, String plural, String name, V1DeleteOptions body, Nullable`1 gracePeriodSeconds, Nullable`1 orphanDependents, String propagationPolicy, String dryRun, IReadOnlyDictionary`2 customHeaders, CancellationToken cancellationToken)
   at Aspire.Hosting.Dcp.KubernetesService.<>c__DisplayClass12_0`1.<<DeleteAsync>b__0>d.MoveNext() in /_/src/Aspire.Hosting/Dcp/KubernetesService.cs:line 109
--- End of stack trace from previous location ---
   at Aspire.Hosting.Dcp.KubernetesService.ExecuteWithRetry[TResult](DcpApiOperationType operationType, String resourceType, Func`2 operation, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/KubernetesService.cs:line 198
   at Aspire.Hosting.Dcp.ApplicationExecutor.DeleteResourcesAsync[RT](String resourceName, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/ApplicationExecutor.cs:line 686
Unhandled exception. System.AggregateException: One or more errors occurred. (Redis resource does not have endpoint annotation.)
 ---> Aspire.Hosting.DistributedApplicationException: Redis resource does not have endpoint annotation.
   at Aspire.Hosting.ApplicationModel.RedisContainerResource.GetConnectionString() in /_/src/Aspire.Hosting/Redis/RedisContainerResource.cs:line 20
   at Aspire.Hosting.ResourceBuilderExtensions.<>c__DisplayClass8_0`1.<WithReference>b__0(EnvironmentCallbackContext context) in /_/src/Aspire.Hosting/Extensions/ResourceBuilderExtensions.cs:line 149
   at Aspire.Hosting.Dcp.ApplicationExecutor.CreateContainersAsync(IEnumerable`1 containerResources, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/ApplicationExecutor.cs:line 564
   at Aspire.Hosting.Dcp.ApplicationExecutor.CreateContainerSingletonsAsync(CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/ApplicationExecutor.cs:line 108
   at Aspire.Hosting.Dcp.ApplicationExecutor.RunApplicationAsync(CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/ApplicationExecutor.cs:line 74
   at Aspire.Hosting.Dcp.DcpHostService.StartAsync(CancellationToken cancellationToken) in /_/src/Aspire.Hosting/Dcp/DcpHostService.cs:line 83
   at Microsoft.Extensions.Hosting.Internal.Host.<StartAsync>b__15_1(IHostedService service, CancellationToken token)
   at Microsoft.Extensions.Hosting.Internal.Host.ForeachService[T](IEnumerable`1 services, CancellationToken token, Boolean concurrent, Boolean abortOnFirstException, List`1 exceptions, Func`3 operation)
   at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken)
   at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)
   at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)
   at Aspire.Hosting.DistributedApplication.RunAsync(CancellationToken cancellationToken) in /_/src/Aspire.Hosting/DistributedApplication.cs:line 147
   --- End of inner exception stack trace ---
   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait()
   at Aspire.Hosting.DistributedApplication.Run() in /_/src/Aspire.Hosting/DistributedApplication.cs:line 155
   at Program.<Main>$(String[] args) in /Users/simonhoss/Documents/entwicklung/Octopus/iot/cloud/cloud.AppHost/Program.cs:line 11

The code where the exception is thrown is here:
        if (!this.TryGetAnnotationsOfType<AllocatedEndpointAnnotation>(out var allocatedEndpoints))
        {
            throw new DistributedApplicationException("Redis resource does not have endpoint annotation.");
        }

On my system I saw that the AllocatedEndpointAnnotation are added to late. When I debug I'm able to reach this point in ApplicactionExecutor, but far to late.
                var a = new AllocatedEndpointAnnotation(
                    sp.ServiceBindingAnnotation.Name,
                    PortProtocol.ToProtocolType(svc.Spec.Protocol),
                    svc.AllocatedAddress!,
                    (int)(sp.ServiceBindingAnnotation.Port ?? svc.AllocatedPort!), // Checked by HasCompleteAddress above.
                    sp.ServiceBindingAnnotation.UriScheme
                    );

                appResource.ModelResource.Annotations.Add(a);

I see you’re using the latest builds. This was a regression introduced that we’re looking at


Selecting custom caching strategy

Hello,
Following #4058 discussion (about statement caches), I want to propose a possible solution.
Since rebuilding statement cache on error is not an option (at least for PostgreSQL). The only convenient option that I see, is to give control to end user, to decide how he wants to use statement cache (of course user can implement it's own connection type, but that is not convenient option, as most likely user also needs to implement r2d2 traits as well).
There's the core idea:

decision (whether to cache or not) is maid by StatementCacheStrategy trait. To implementations are already provided: WithCacheStrategy (default), WithoutCacheStrategy.
user can choose what strategy to use by setting set_cache_strategy globally per connection type (because traits are generic over DB and Statement).
there's no breaking changes for end users (maybe there are breaking changes if users already use i-implement-a-third-party-backend-and-opt-into-breaking-changes feature flags).

Notable changes:

introduced ConnectionStatementCache that is implemented by all connections which will use statement cache. This trait has two purposes: 1) exposes functionality for end user to set custom caching strategy, 2) StatementCache use this, to actually get current caching strategy. Another option was to implement this directly on Connection, but that would require adding new type Statement associated type parameter, and I didn't wanted to deal with MultiConnection macro.
removed len from StatementCache. It was used by PostgreSQL implementation to generate statement cache names, but this might easily break if user provides it's own implementation for statement cache. Instead, StatementCache implementation provide a cache_counter: Option<u64> that is incremented every time if statement will be cached, or None otherwise.
introduced IntrospectCachingStrategy for tests only (behind cfg(test)), that wraps actual StatementCacheStrategy and records outcome. This is used in tests to check if tests related to statement caching behave correctly. (previously len field from StatementCache was utilized, but this is more precise).
module statement_cache is public (instead of being behind i-implement-a-third-party-backend-and-opt-into-breaking-changes).

Thanks for opening this PR and working on this issue.
That written: I'm not fond of the chosen approach. I personally do not see why rebuilding the statement isn't an option. Yes it might fail for PostgreSQL in a transaction, but on the other hand there is so many other things that might file and render a transaction unusable that I don't feel that this really matters. If you care about such cases you must implement a transaction retry logic anyway.
There are several things to consider with the proposed solution, that I personally not a fan of:

It introduces global state, which is something that we want to avoid as best as possible
It exposes types that were previously considered implementation details. By doing that they become part of the stable API, which in turn would make it really hard to change them later. They were private on propose.
I'm not sure of the performance implications of this kind of change. Especially for the SQLite backend the additional dyn dispatch could come with a significant cost.

I'm sorry if that sounds like I want to dismiss your work, but I just have different ideas in mind on how to approach that problem. I personally would have preferred to discuss the design of this feature first before posting a PR, as that would likely result in much less frustration on both sides.

Since this is not a huge feature, I like to start discussion from some point. Real implementations usually have some subtle nuances and you also see full scope, these things are hard to discuss up-front.
And please, don't feel frustrated, - it's ok that you don't like it :)
One important thing, regarding transactions. YMMV, but for us transactions fail only for network issues or breaking-scheme-change issues. Breaking-scheme-change we solve by properly managing migrations in non-breaking change manner, the rest (network issues) we simply propagate to upstream, as technical problems (which might be retried later or not).
Implementing transaction retry, just for this one type of error, would be very painful for us, because that would mean, that we need to update all functions that is written in 4+ years from FnOnce to Fn, while disabling cache would make some breaking-scheme-change into non-breaking-scheme-change and make life significantly simpler :)
Before discussing further points, I think that we need to agree on one fundamental point first:

do you consider an option, where user can choose custom caching strategy?

I'm open to allow configuring the cache, but I would like to make that option connection specific rather than global. So just PgConnection::set_cache_size(CacheSize) with cache size having 3 variants (Unbound (default), Size(NonZeroUsize) and Disabled). This likely needs some adjustments on the cache hashmap to drop values for the Size variant, otherwise I expect this to be a rather simple change.
That written: I would prefer to have the automatic retry for statements nevertheless as at least I do want to use the statement cache whenever possible as it gives a quite large performance boost.

Let me think out lout :).
Ideally, we would like to satisfy all of these constrains for a service:

service must be running while we run migrations.
service should run efficiently, e.g. utilize statement cache.
service uses connection pools to handle many concurrent requests

To achieve that, migration process could be implemented like this:

disable caching at runtime (we'll probably send some sort of trigger to a service, we need to somehow disable caching for all subsequent queries)
run migrations
enable caching at runtime again.

In order to implement caching behavior at runtime, we would wrap r2d2 connection pool into our own and every time we get connection from the pool, we would set_cache_size. If underlying implementation is efficient, it should be no-op if we set the same value as it was before.
I probably it's a bit more work on end user side (to wrap connection), but actually that would solve our problem :)
So I guess we'll come back to you with updated revision ;)

That sounds like a good summary, thanks for writing it up. I think it would be also fine to have an additional function that just empties the current query cache.

Some comments:

regarding cache clearing, I think it's not necessary, as you can disable & enable and achieve cache clearing this way.
you raised concern about dynamic dispatch performance. I did some testing locally (on my laptop 13th Gen Intel® Core™ i7-1355U × 12). Overhead is around 2.1ms (+/- 0.1ms) per 1M calls, (or ~2ns per call)). So I think we can ignore it.
I had to expose some fields pub(crate) statement_cache in order to proper testing using IntrospectCachingStrategy.
I did not implemented Size(NonZeroUsize) caching strategy, to be honest I'm not sure what would be the use case...

Happy reviewing and waiting for your comments :)

I think I have addressed all your comments.
I have removed IntrospectCachingStrategy because using Instrumentation is enough to test caching.

Thanks for the update. I really like the solution to test this via the instrumentation tooling.
It looks nearly ready now. I added a number of minor comments about stylistic things and changes that are not required anymore. The only larger point that still remains is adding at least one test that checks the disabled cache behaviour.

Hi, @weiznich
Thanks for merging this!
I was on vacation for a while and didn't managed to address your comments on time...
Should I create a new pull request to address your comments, or it's not worth it?

@fraillt No worries, holiday is important and you shouldn't response to anything there. I already fixed the last few comments in https://github.com/diesel-rs/diesel/pull/4161/commits/bda514b4f88110a64d31f76bada2e81c599477a9, so there is nothing that needs to be done here.


Updated "forthcoming" item

Updated last item so it's balanced with a link

Thanks Andrew! Closing in favour of https://github.com/pol-is/polisClientAdmin/pull/31


delete states if it exists on run

can you rebase this on main so the diff doesn't look weird

fixed!


Feature/superpower

Solves #99
Migrates from Sprache to SuperPower

Quite some stuff to do, many red tests, but a first buildable draft which allows to work at making tests green...

No clue about the current failure in ParseDotEnvFile.
It says that Many() cannot be applied to zero-width parsers and I can't find any solution right now.

fixed the mentioned issue:
Empty should not parse EOF, otherwise AtLeastOnce() [exactly, the Many() within] fails.
Explanation:

Many() (and AtLeastOnce(), which uses Many internally) cannot be used together with a Parser which is not consuming any character
EOF without any preceding character means consuming no character at all
excluding EOF in Empty requires to change AtLeastOnce() to Many(), because with an EOF only, we do not have any Element now
since AtEnd() in ParseDotenvFile() requires the Parser to reach EOF, there is no chance of missing something, because any not consumed character leads to fail

🟢 All tests green
Switched to Ready-state


Add Blast Sepolia Testnet

Addded blast-sepolia-testnet. We recently deployed the Testnet Random Numbers QRNG Provider there.
Blast Sepolia Testnet
AirnodeRrpV0.sol

@vanshwassan do you need this released asap?

@vanshwassan do you need this released asap?

We need to add it to the vitepress-docs so it would be good if we could get a release unless you have more plans for the next release.

Released as v4.4.0: https://github.com/api3dao/chains/releases


[8pt] Possible problem re-running fim_post_processing.sh a second time

While not confirmed, there might be a problem running post processing a second time. We need to be able to re-run post processing on a huc run as many times as we like.  This has not yet been confirmed that there even is a problem, but will be very urgent if it does exist. This can affect both fails on processing (AWS or OWP), but also testing/debugging for code related to post processing.
Might be extra columns added to hydrotables?   It is possible that some parts of post processing are updating files in the huc folders.
Research required and possible urgent fix.

Duplicate of #1141


ARROW-2835: [C++] Make file position undefined after ReadAt()

Seeking is required when calling an implicitly-positioned operation such as Read() after ReadAt().

Another possibility would be to use a R/W lock to serialize Read() calls while allowing parallel ReadAt() calls. That's slightly more involved, though (and would rely on boost::thread for a R/W lock aka. shared_mutex or shared_timed_mutex).

So are they poisoning someone with some kind toxic can I just have  a normal English version instead of encoding

I just reported this spam comment to GitHub

Rebased.

CI failures are unrelated, will merge.


Kubernetes support externalname service

Fixes #1142
Docs will need to be updated but before doing that I wanted to make sure I was at least going about this the right way.
Along with actually supporting the ExternalName service type I added support for the passHostHeader annotation. This is a requirement for actually using ExternalName.
This is basically the first Go code I have written, so very much open to any and all feedback.

Thanks for the feedback @timoreimann. I have made the requested changes. :)

As this seems to be reasonably acceptable  I will go ahead and update some docs when I have a few minutes to spare.

@emilevauge @SantoDE @errm @dtomcej @vdemeester


Deploy static website without deleting all files

Is there any chance to deploy static website without deleting all files in the storage?
In my application, we use an internal update website feature that detects new files and forces reload of the website, but we need the old version still there.

We can accomplish this by supporting a setting that allows users to have an "overwrite" deployment instead of deleting everything.

A setting that accomplishes this called deleteBeforeDeploy was just shipped in version 0.11.0.


feat(ui): add toggle button group component [LW-9269]

Checklist

[x] JIRA
[x] Proper tests implemented
[x] Screenshots added.

Proposed solution
Add a new ToggleButtonGroup component. Supporting keyboard navigation and other a11y-related features.
Testing
Open storybook, test different options for user navigation and selection e.g. mouse clicks and keyboard focus.
Screenshots

coverage: 53.17%. remained the same
when pulling 8ee2e7fbd154424f4fbe8a62cead0c6657a612ad on feat/LW-9269-new-toggle-button-group-component
into 9da512ddebe22885994af1af5abaa3fde02b8f01 on main.

Nice work @przemyslaw-wlodek 💪


do not hotplug network device when stopping sandbox

#1957 is problematic that it causes vfio nic passthrough to fail, because we need to bind the device back to host and that is not possible when qemu is still running. So we should revert it.
And to fix the original issue #1956, we can just skip hotunplug all together as it is not really necessary when stopping a vm.

/test


remove foreach to test generator results

Codecov Report

Merging #38 into master will not change coverage by %.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #38   +/-   ##
=========================================
  Coverage     92.73%   92.73%
  Complexity       96       96
=========================================
  Files            16       16
  Lines           234      234
=========================================
  Hits            217      217
  Misses           17       17

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 60c7483...49edc47. Read the comment docs.


remove un-needed -ti

Er, don't the instructions say to type exit to finish that step? Without -it that won't work

@johndmulhausen

don't the instructions say to type exit to finish that step?

no.

Agh, sorry, I was thinking of the Ubuntu workflow. That's the one where you type exit. Thanks, @friism :)


[#6762] Add Process Fork Plugin

Added ServiceTypes, Annotations, and Configurations
ServiceTypes:
PROCESS - 6005
Annotations:
process.command - 180
Configurations:
profiler.process.tracing.enabled=true or false

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

process.command annotation is added as in the screenshot attached.

process.pid annotation added

Codecov Report

Merging #6763 into master will decrease coverage by 0.04%.
The diff coverage is 9.61%.

@@            Coverage Diff             @@
##           master    #6763      +/-   ##
==========================================
- Coverage   39.14%   39.09%   -0.05%
==========================================
  Files        3136     3140       +4
  Lines       93896    93948      +52
  Branches    11793    11800       +7
==========================================
- Hits        36756    36730      -26
- Misses      54176    54250      +74
- Partials     2964     2968       +4

Impacted Files
Coverage Δ

...vercorp/pinpoint/plugin/process/ProcessPlugin.java
0.00% <0.00%> (ø)

...p/pinpoint/plugin/process/ProcessPluginConfig.java
0.00% <0.00%> (ø)

...process/interceptor/ProcessExecuteInterceptor.java
0.00% <0.00%> (ø)

...orp/pinpoint/profiler/UnmodifiableClassFilter.java
45.00% <33.33%> (-5.00%)
:arrow_down:

...oint/plugin/process/ProcessPluginTypeProvider.java
100.00% <100.00%> (ø)

...p/pinpoint/rpc/client/WriteFailFutureListener.java
56.25% <0.00%> (-18.75%)
:arrow_down:

...rp/pinpoint/rpc/control/ControlMessageDecoder.java
64.28% <0.00%> (-14.29%)
:arrow_down:

...vercorp/pinpoint/rpc/packet/ClientClosePacket.java
55.55% <0.00%> (-11.12%)
:arrow_down:

.../pinpoint/rpc/client/PinpointClientHandshaker.java
60.00% <0.00%> (-5.00%)
:arrow_down:

...tor/metric/datasource/DefaultDataSourceMetric.java
75.00% <0.00%> (-3.13%)
:arrow_down:

... and 10 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #6763 into master will increase coverage by 0.01%.
The diff coverage is 20.93%.

@@            Coverage Diff             @@
##           master    #6763      +/-   ##
==========================================
+ Coverage   39.14%   39.16%   +0.01%
==========================================
  Files        3136     3159      +23
  Lines       93896    94184     +288
  Branches    11793    11813      +20
==========================================
+ Hits        36756    36884     +128
- Misses      54176    54335     +159
- Partials     2964     2965       +1

Impacted Files
Coverage Δ

...vercorp/pinpoint/plugin/process/ProcessPlugin.java
0.00% <0.00%> (ø)

...p/pinpoint/plugin/process/ProcessPluginConfig.java
0.00% <0.00%> (ø)

...t/plugin/process/interceptor/Java9PidProvider.java
0.00% <0.00%> (ø)

...process/interceptor/ProcessExecuteInterceptor.java
0.00% <0.00%> (ø)

...lugin/process/interceptor/ProcessImplProvider.java
0.00% <0.00%> (ø)

...ugin/process/interceptor/UnsupportPidProvider.java
0.00% <0.00%> (ø)

...plugin/process/interceptor/PidProviderFactory.java
30.76% <30.76%> (ø)

...orp/pinpoint/profiler/UnmodifiableClassFilter.java
45.00% <33.33%> (-5.00%)
:arrow_down:

...in/process/interceptor/UNIXProcessPidProvider.java
52.00% <52.00%> (ø)

...oint/plugin/process/ProcessPluginTypeProvider.java
100.00% <100.00%> (ø)

... and 51 more

Continue to review full report at Codecov.

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

command and pid annotation works in mac environment


Update website to spec 1.21.0

The spec 1.21.0 was released yesterday, but https://opentelemetry.io/docs/specs/ show 1.20.0
What steps are needed to update it?

@tigrannajaryan it's still a manual process that needs to be triggered by us. Some folks (including myself) have been out of office for some days last week so that's why we have a delay. We will take care of this as soon as possible.

Thanks a lot for updating!


revision based auto-compaction-retention

Hi,
Currently we are using the auto-compaction-retention parameter to compact etcd data every 24h. But given our spiky usage pattern(we are using etcd as distributed lock), this time based compaction policy doesn't work too well for us. Is there a revision-based auto-compaction policy that we can configure? Also, is there a metric for # of revision that we can watch on(I didn't find in the current exposed metrics)?
Thanks

It makes sense. We will probably add it.

Thanks. Is there a workaround that we can do now to alleviate us from manually compacting every now and then? We are using etcd-operator, is this something that operator can help?

@clusc Not really. It is all manual at the moment.

@clusc

is there a metric for # of revision

revision is attached in every response header.

It doesn't for /metrics endpoint though right?

@clusc No. You can add a debugging metrics for it if you wish. Open a pr, thanks.

I had the same idea and just crated a PR for it.
Still, compaction happens every 5 minutes, but I believe it should cover almost all environments.

fixed by #8123


Test the update_cost function

Is your feature request related to a problem? Please describe.
The update cost function take the air quality predictions (hexgrid), does an spatial intersection with the road network then applies a cost function to each edge.
It needs to be tested properly.
Describe the solution you'd like

[ ] Test setting fill_edge_geometry to True does something sensible.
[ ] Test that the cost function is calculated properly. Generalise to allow different cost functions to be applied.
[ ] Create a fake road network and fake grid for testing geospatial queries.

Describe alternatives you've considered
We run the tests on the osmnx graph itself, but its difficult to verify correct results on a real graph
Additional context

This function is superceded by the new RoadQuery object created in #34


Possibly fix PinephonePro low batery startup problem

Is it possible to wait for a minimum battery level before continuing the boot process?
This will fix the boot loop problem the PPP has currently.

Yes, it is possible. Though it requires adding a driver for the PMIC to query the battery state.
I believe it was being worked on for upstreaming in U-Boot by other Pine64 community members.

Does anyone know of any resources on this issue (links where people might be working on it, etc)?

This sounds like a basic feature that should be added to Tow-Boot.

#168 may help with part of the problem.

The "drained battery issue" is fixed in megi's u-boot. See this commit -- https://xff.cz/git/u-boot/commit/?h=ppp&id=7f8238fd608290152b143322178a5be21a447dc1

The "drained battery issue" is fixed in megi's u-boot. See this commit -- https://xff.cz/git/u-boot/commit/?h=ppp&id=7f8238fd608290152b143322178a5be21a447dc1

and that is exactly what is done in #168 pretty much. Just set the PMIC to take a higher current at start up, the other part of the fix is keeping the current limit set by the bootloader until the kernel knows more about the situation, so the kernel doesn't shut off the device from taking in any more charge and therefore creating this bootloop issue. Wthout the kernel patch, the PPP's PMIC Linux driver sets the input current to 0 at boot and keeps doing so until it has figured out more about the situation which is too late and the device has already shut off because the battery is dead :). Said fix was created by megi and is in most distros kernels now.

According to megi that fix isn't sufficient, unfortunately I don't have a PPP to test against, but I figured it was worth documenting.
From the #pinephone channel on irc.pine64.org

<megi> it is not really fixed in Tow-Boot
<megi> tow-boot uses this patch https://github.com/Tow-Boot/U-Boot/commit/465e5a1776d84f5e85836c61466b732c740ed8e5#diff-96512640d535c88213089e33fa98fc4a77b4f2bad8916e2cccc310cc24a43211 which raises current limit too high, raises it too late, and doesn't wait for battery charge to rise before booting
<megi> here's a better approach https://megous.com/git/u-boot/commit/?h=ppp-2023.07&id=ced7bf1bc5f5539da35eeae0b7b70f0954871862


Bring the README in line with other projects

Mostly shifting thing around. This also adds a support guide which resolves #31.

@JakeChampion if you get a sec this week could you take a look?

LGTM 👍

I like the saucelabs compat page!
It also looks like we need to add a few more tests as we are covering only 95% so far.


fix: use right example link

Small fix, about the URL of the chat example in README.md.

How about also removing this dropdown icon
(This doesn’t expand)

How about also removing this dropdown icon  (This doesn’t expand)

Yes!

Looks perfect!

It looks like this now, maybe @tausifcreates has ideas to make it more beautiful.

Let's just hope Totodore will fix it 😁

@caojen removing the <summary> did it for me :) can you check on your end?

@caojen removing the <summary> did it for me :) can you check on your end?

yes, it works.

I don't have a better solution than that but thanks for the fix :)


Use custom httpServer with uWebSockets

Hey
we have implemented our own httpServer and wanted to know if it's possible to use is instead of the one created by the library?

I don't know. Maybe? How can I know?

If you can expose two different ports it should work


[Torch][AArch64] Skip test_load_model___wrong_language__to_pytorch

This patch makes test_load_model___wrong_language__to_pytorch to be
skipped in AArch64 due to a bug that can be reproduced when enabling
Integration Tests in machines with Torch installed in TVM.
The error message seen is:
OSError: /usr/local/lib/python3.7/dist-packages/torch/lib/
libgomp-d22c30c5.so.1: cannot allocate memory in static TLS block

While the test needs further investigation, it is being set as
skipped so other tests can be enabled and not to regress and allow
time for the investigation to be made.
This relates to the issue described in #10673.
cc @Mousius @driazati @NicolaLancellotti @ashutosh-arm @areusch @gromero

Once this is merged, we can then proceed and:

Merge https://github.com/apache/tvm/pull/12131
generate/update Docker images
Merge https://github.com/apache/tvm/pull/11519

Just curious why does CI not show this failure if it's running pytest tests/python/driver on aarch64 after #10677?

This is actually something I've reported in https://github.com/apache/tvm/issues/12529 and exactly what is blocking us to update the AArch64 images with updates for ONNX/Torch and TF for better coverage.
#10677 is merged, but the production images are not reflecting that yet.

It seems CI is happy now fyi @driazati @areusch @Mousius


device not loaded from profile

I got the following default profile:
lxc profile show default

config:
  environment.http_proxy: ""
  user.network_mode: ""
description: Default LXD profile
devices:
  eth0:
    name: eth0
    nictype: bridged
    parent: lxdbr0
    type: nic
  root:
    path: /
    type: disk
  sdb:
    path: /home
    source: /home
    type: disk
  sdc:
    path: /var/nfs
    source: /var/nfs
    type: disk
name: default
used_by:
- /1.0/containers/server101
- /1.0/containers/server102
- /1.0/containers/server103
- /1.0/containers/server104
- /1.0/containers/server105

and my configs looks like these:
lxc config show server101

architecture: x86_64
config:
  boot.autostart: "true"
  volatile.base_image: 0c85c33e8528b21910364dfa12328ba91416edf4bc3c2d606b2224075e9b79ba
  volatile.eth0.hwaddr: 00:16:3e:49:0e:02
  volatile.idmap.base: "0"
  volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
  volatile.last_state.idmap: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
devices: {}
ephemeral: false
profiles:
- default
stateful: false
description: ""

yesterday I did a dist-upgrade (running Ubuntu 18.04 server) which also updated lxc/lxd and now none of my instances will start,..
I just get:
lxc start server101

Error: Common start logic: Set volatile.last_state.idmap config key on container "server101" (id 1): Containers must have a root disk device (directly or inherited)

runing 'lxc info --show-log server101', I get:
Name: server101
Remote: unix://
Architektur: x86_64
Erstellt: 2018/06/11 10:41 UTC
Status : Stopped
Type: persistent
Profile: default

Protokoll:

seems to me like the root disk device isn't taken from the profile like it was before the update.
'lxc storage list'
gives me:
+---------+--------------+--------+------------------------------------+-------------+
|  NAME   | BESCHREIBUNG | DRIVER |               SOURCE               | BENUTZT VON |
+---------+--------------+--------+------------------------------------+-------------+
| default |              | btrfs  | /var/lib/lxd/storage-pools/default | 5           |
+---------+--------------+--------+------------------------------------+-------------+

Since I'm fairly inexperienced with lxc&co I hope someone can tell me how to fix this.
(Like I wrote, this setup did run fine till the update, so the configs shouldn't be that messed up. :))
Thanks!

Your root device in the default profile above is missing the pool property which in your case should be set to default

Calling 'lxc profile edit default' and changing
  root:
    path: /
    type: disk

to
  root:
    path: /
    type: disk
    pool: default

gives me
Config parsing error: At least one container relies on this profile's root disk device

saving the file before closing (not while) gives me:
Config parsing error: The following containers failed to update (profile change still saved):
 - server101: Containers must have a root disk device (directly or inherited)
 - server102: Containers must have a root disk device (directly or inherited)
 - server103: Containers must have a root disk device (directly or inherited)
 - server104: Containers must have a root disk device (directly or inherited)
 - server105: Containers must have a root disk device (directly or inherited)

-> Any idea on how to fix this?

What's lxc config show --expanded server101 showing you now?

As per the error above, the profile change should have been saved regardless, so assuming there's nothing wrong, the container configuration should be correct now.

it didn't change the profile
I tried saving using 'CTRL+O' and then exiting, which gave the above error but it still wants to go back to nano and edit the file. :(
which is why 'lxc config show --expanded server101' still looks like this:
architecture: x86_64
config:
  boot.autostart: "true"
  environment.http_proxy: ""
  user.network_mode: ""
  volatile.base_image: 0c85c33e8528b21910364dfa12328ba91416edf4bc3c2d606b2224075e9b79ba
  volatile.eth0.hwaddr: 00:16:3e:49:0e:02
  volatile.idmap.base: "0"
  volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
  volatile.last_state.idmap: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
devices:
  eth0:
    name: eth0
    nictype: bridged
    parent: lxdbr0
    type: nic
  root:
    path: /
    type: disk
  sdb:
    path: /home
    source: /home
    type: disk
  sdc:
    path: /var/nfs
    source: /var/nfs
    type: disk
ephemeral: false
profiles:
- default
stateful: false
description: ""

That's odd, okay, then, this should unstick things:

lxc config device add server101 root disk path=/ pool=default
lxc config device add server102 root disk path=/ pool=default
lxc config device add server103 root disk path=/ pool=default
lxc config device add server104 root disk path=/ pool=default
lxc config device add server105 root disk path=/ pool=default
lxc profile device set default root pool default

So effectively first manually fixing all the containers individually and then applying the profile change which should then be happy to comply.

lxc config device add server101 root disk path=/ pool=default
gives me:
Error: The storage pool of the root disk can only be changed through move

lxd sql global "INSERT INTO profiles_devices_config (profile_device_id, key, value) VALUES (23, 'pool', 'default');"
Rows affected: 1

added the pool to the default profile :+1:
and to the container :+1:
lxc config show --expanded server101
architecture: x86_64
config:
  boot.autostart: "true"
  environment.http_proxy: ""
  user.network_mode: ""
  volatile.base_image: 0c85c33e8528b21910364dfa12328ba91416edf4bc3c2d606b2224075e9b79ba
  volatile.eth0.hwaddr: 00:16:3e:49:0e:02
  volatile.idmap.base: "0"
  volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
  volatile.last_state.idmap: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
devices:
  eth0:
    name: eth0
    nictype: bridged
    parent: lxdbr0
    type: nic
  root:
    path: /
    pool: default
    type: disk
  sdb:
    path: /home
    source: /home
    type: disk
  sdc:
    path: /var/nfs
    source: /var/nfs
    type: disk
ephemeral: false
profiles:
- default
stateful: false
description: ""

Thanks a lot, you really saved my day here!

Perfect, glad that fixed that issue :)


Modified to just have LICENSE file.


Adds labelOverlapSeparator option to customize default ' - '

When the range labels overlap the separator string is ' - '.
The problem is that this character can be interpreted as 'minus'.
Steps to reproduce

slider range with high value just above 0
http://jsfiddle.net/04sr3ty0/1/

Expected behaviour
Should be able to tell if the high value is positive of negative
Actual behaviour
Looks like the range is -2 to -1 when in fact it is -2 to +1
I am happy to create a pull request to fix this minor issue

Hi @ben-henoida ,
I've never thought about this, but this makes sense! ^^
What character should we use in your opinion?

' .. ' is common enough to represent range :  -2 .. 1
How about a making it an option ?

Yes let's make it an option and keep the default to be - so we don't make a breaking change. 👍 If you can make a PR for this, it would be awesome! ;)

PR created : https://github.com/angular-slider/angularjs-slider/pull/616

Released in https://github.com/angular-slider/angularjs-slider/releases/tag/6.5.0


Fix convention on border-zero rule

Not 'zero' but '0' is used for convention option in border-zero rule.
https://github.com/sasstools/sass-lint/blob/develop/docs/rules/border-zero.md

Coverage remained the same at 100.0% when pulling<PHONE_NUMBER>f416d905bac68cac03f148c942a542 on ueokande:fix_border_zero into 3aebbb2d6bbf49a10dde1769e2e453540a00263b on sasstools:master.

LGTM, thanks!


why Amazon Linux 2 is ignoring /etc/syscconfig/docker and using very low ulimit for nofile

Environment:

AWS Region: us-east-1

Instance Type(s): c5.2xlarge

Kubernetes version (use aws eks describe-cluster --name <name> --query cluster.version): 1.11.x

This is a general questions
I noticed that the Amazon Linux 2 in general is using pretty low ulimit and ignoring configuration in /etc/sysconfig/docker and /etc/sysconfig/docker-storage, is this by design or a bug?
this is also same on ECS optimized and vanilla Amazon Linux 2

What AMI version are you using?

latest

@benishak Try using the previous version. A ulimits regression was introduced to the latest AMI. It has since been fixed, but a new AMI has not yet been released.

This is the commit that fixes the issue:
https://github.com/awslabs/amazon-eks-ami/commit/9f2000223d4f081d24419c5af7dd058c4117c945


[Feature] User confirmation UI to make sure task is completed succesfully

if it isn't, we let the LLM know to keep trying

relates to #9

no longer an issue with new input UI


Add function and cli tool for DRISE sal gen with detector instantiated from config file

An initial general comment here is that the current take is focused specifically on DRISE the implementation. We should probably write to the interface, not the implementation, e.g. write the utility to use generic GenerateDetectorProposalSaliency implementation, the instance of which we would take in a configuration for in a similar way the DetectImageObjects is being used to hydrate the blackbox detector.

This first tool iteration LGTM and am happy to merge if there aren't other objections.

Modulo autosquash rebase to resolve fixup commits.


Responsive bug in some screen sizes

Hi team, looks like the website doesn't look good from 600px to 1440px. There are some common devices with these screen widths (tablets' are around 600 to 800 in portrait, 800 to 1200 in landscape, many laptops are around 1200 -> 1400)

Are you open for a PR to fix this?

Hey!
That would be amazing!

Wow thanks @arjunan-k @jfranciscosousa !


Generic type that conditionally returns never can result in a never acting like any when used

Bug Report
🔎 Search Terms
generics, as keyword, type assertion, never
🕗 Version & Regression Information
I see the same behavior in versions 3.3 through 4.8.0 beta in the TS Playground

This is the behavior in every version I tried, and I reviewed the FAQ for entries about the never type being used after being returned_____

⏯ Playground Link
Playground link
💻 Code

type SometimesNever<T> =
  T extends string ? string
    : T extends number ? never
    : never;

function sometimesNeverFn<T>(something: T): SometimesNever<T> {
  return something as SometimesNever<T>;
}

const ok = sometimesNeverFn('something');
doSomething(ok); // expected/actual error: Argument of type 'string' is not assignable to parameter of type 'Date'.(2345)

const wtf = sometimesNeverFn(10);
doSomething(wtf);  // expected: This should error, but doesn't.  `wtf` is type `never` (visible in playground) but we can pass it to a function that expects a Date.

function doSomething(s: Date) {
  s.getDate();
}

🙁 Actual behavior
When a generic type that might be never is returned from a function by using a type assertion in the return, and the type resolves as never, the type is still usable to be passed as an argument to functions, almost as if it was an any.
🙂 Expected behavior
If the compiler is able to resolve a type as never, then the variable with that type should cause an error when passed as a function argument.
I had this occur on a vastly more complex set of generic types and functions that could sometimes be never (and correctly so, as the function did runtime checks and would throw if passed certain types), and it was very unintuitive that the type could be resolved as never but still returned and subsequently passed to another function without an error.

That's working as intended. Nothing is assignable to never, but never is assignable to anything.

Yeah, can see that even this works.
function alwaysNever(something: string | number): never {
  throw Error('err');
}

const ok = alwaysNever('something');
doSomething(ok);

const wtf = alwaysNever(10);
doSomething(wtf);

function doSomething(s: Date) {
  s.getDate();
}

Thanks for the explanation @MartinJohns.  I'll close the ticket.  It is very unintuitive, but I think I understand why it's happening.

I think what I'm really wishing for here is something like what is proposed in #23689, a type that is neither assignable to anything nor assignable from anything.

Yep, #23689 (invalid type) is most likely what you're really looking for.

It is very unintuitive, but I think I understand why it's happening.

Yeah, so never is the bottom type which represents the "result" of infinite loops or exceptions, so you (and the compiler) are free to pretend it's whatever type you want.  This is the type-theoretically correct behavior, see https://github.com/microsoft/TypeScript/issues/49862#issuecomment-1180954393
tl;dr: If doSomething(neverVal) is reachable, your program is already ill-typed by definition.


How to convert custom op into tensorrt

Thank you for your great job!
When I try to convert pytorch model to tensorrt, there are some custom operations just like AvgVoxelization, furthest_point_sample hard to convert into tensorrt. Is there any suggestion or reference code for me? Thanks a lot.

It's not very easy to convert PVCNN to TensorRT. You probably need to register them as custom plugins in TensorRT.


Do we commit to BigInt, or not?

Assuming that the coin supply of Dash stays forever capped at 21.3 million...
Number.MAX_SAFE_INTEGER
// 9_007_199_254_740_991 (uint52)

Dash.SATOSHIS // 100_000_000

Dash.MAX_COIN_SUPPLY // 21_300_000

Dash.MAX_COIN_SUPPLY * Dash.SATOSHIS
// 2_130_000_000_000_000

In theory that gives a safety factor of over 3.8, so it's good enough for government work.
However, there are certain math operations that can only work on uint32 or uint64, but not uint52, IIRC.
let MAX_UINT32 = Math.pow(2, 32) -1; // 4_294_967_295
MAX_UINT32 / Dash.SATOSHIS; // ~= 42.949 DASH

For any issues related to uint32, we max out at 42.949 DASH. So I'm probably mistaken about issues that would affect uint32s, otherwise they would have surfaced many times over.
Due to some "good reason" I had, which unfortunately I can't remember, I wrote most of DashTx for BigInt.
However, BigInts cannot be serialized with JSON.
JSON.stringify({ big: 2n });

Uncaught TypeError: Do not know how to serialize a BigInt
    at JSON.stringify (<anonymous>)

Thoughts?
cc/ @riongull

I'm thinking we commit to NOT using BigInt.
If we need to support > Uint53 in the future, we can reference these commits to see what will go back where:

https://github.com/dashhive/DashTx.js/pull/36/files


[iOS] Bug when focusing TextField and pulling down iOS Control Center or notifications

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

Run the sample
Click on the text field and drag down the messages or the control center directly after that while the keyboard appears.
Observe that no keyboard appears, but a red box is visible.

Reproduced on an iPhone 14 Pro with iOS 16.3.1
Expected results
The keyboard should be visible or the MediaQuery.viewInsets should be correctly updated.
Actual results

Observe that no keyboard appears, but a red box is visible.

Code sample
Code sample
runApp(
    MaterialApp(
      home: Scaffold(
        resizeToAvoidBottomInset: false,
        body: SafeArea(
          child: Stack(
            children: [
              Center(child: TextField()),
              Positioned(
                bottom: 0,
                left: 0,
                right: 0,
                child: Builder(builder: (context) {
                  return Container(
                    height: MediaQuery.viewInsetsOf(context).bottom,
                    color: Colors.red,
                  );
                }),
              )
            ],
          ),
        ),
      ),
    ),
  );

Screenshots or Video

Screenshots / Video demonstration
https://github.com/flutter/flutter/assets/18357332/4d0e2dcd-3afc-4141-a57c-2283fb0af043

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
Flutter (Channel master, 3.13.0-3.0.pre.69, on macOS 12.6 21G115 darwin-arm64, locale en-US)

Thanks for the report @b3nni97

Reproduced on an iPhone 14 Pro with iOS 16.3.1

Although I don't have the said device, but I tried on a lesser iOS simulator version on which the reported behavior didn't occur. After clearing the control center or notifications screen, the keyboard was intact in the app.
Can you also try on same iOS version's simulator to see if the behavior still persists or is it only specific to physical device ?

This bug also happens in native apps, so this is not a direct problem with Flutter.
Closed.


[FR] Ability to edit macros

The ability to edit existing (default) macros and define new macros can be quite handy for advanced users. Furthermore, there are many default macros in MathLive that don't work well in KaTex. For instance, typing \phase{30} gets converted into \enclose{phasorangle}[shadow="none", solid currentColor]{30} which doesn't display in KaTex. Another example is \mathbf{\dot{x}} which gets converted into \bm{\dot{x}}. I don't know if MathLive even recognizes \phasor{} as a command. But it shouldn't expand it into an unsupported macro.
A possible solution is to provide a way to define aliases for certain commands to improve compatibility between MathLive and KaTex. Allowing us, for instance, to use \phasor{} and MathLive would display it internally using \enclose{phasorangle}[shadow="none", solid currentColor]{30}. I do acknowledge, however, that such a solution would be quite hacky.

I've added the settings to configure MathLive macros.
If MathLive does not have this bug, we can have everything work properly by setting expand: false for each macro supported by KaTeX. In your case, it is
    "phase": {
      "def": "\\enclose{phasorangle}{#1}",
      "args": 1,
      "captureSelection": false,
      "expand": false
    }

And the final result is just $\phase{30}. However, because of that bug, you can not edit number 30 inside that angle in MathLive afterward. But at least it is better than before.


Minor typo: becuase -> because

As per title, small type, in 3 places
SwiftNIO version/commit hash
current master: 12cae95c641bbd213080bdb3cf31cb5dec048c2f

https://github.com/apple/swift-nio/pull/394


Link to  bashtage.github.io/linearmodels/doc not working

On the main GitHub page, the link to the docs under About is not working:
bashtage.github.io/linearmodels/doc

@blucap Thanks for the report.  Where are you seeing this broken link?  I can't seem to find it easily in the source.

Sorry, should have read your issue more carefully. Fixed.


motion_representation.ipynb to check if it's alight with the given reference

Hello,
I was running the motion_representation.ipynb notebook, but I encountered an issue where the difference between an existing reference and a newly made reference is not zero.
Specifically, they are 0.00322 and 0.0185, respectively, as shown in the attached photo.
Is it okay to proceed to the next step for preprocessing the data, or should I restart the download process?
If I shouldn't proceed, what could be the reason for this issue?
Thank you.

It’s okay. It’s quite small.
On Thu, Jul 11, 2024 at 4:13 AM Daye-Lee18 @.***> wrote:

Hello,
I was running the motion_representation.ipynb notebook, but I encountered
an issue where the difference between an existing reference and a newly
made reference is not zero.
Specifically, they are 0.00322 and 0.0185, respectively, as shown in the
attached photo.
Is it okay to proceed to the next step for preprocessing the data, or
should I restart the download process?
If I shouldn't proceed, what could be the reason for this issue?
Thank you.
Screenshot.2024-07-11.at.5.09.20.PM.png (view on web)
https://github.com/EricGuo5513/HumanML3D/assets/102942350/7f302303-8b39-4717-8ab0-4321f51ff004
—
Reply to this email directly, view it on GitHub
https://github.com/EricGuo5513/HumanML3D/issues/138, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKRYNB5LHKCEITC5LJNWZVLZLY5DPAVCNFSM6AAAAABKWOGM3WVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQYDENJVGMZTGMI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Sort and enumeration labels

Update the labels for methods using options in the collections to match Darwin. Additionally rename SortOptions to NSSortOptions to match Darwin names

@swift-ci Please test and merge


Fix NPE when calling ActionBarImpl.getNavigationItemCount() when tab navigation is enabled and no tab is actually selected. Return -1 in this case, which is what the Honeycomb implementation does.

Returning -1 is undocumented behavior, but empirical observation reveals this to be a part of Google's implementation.

Merged to dev @ 5fd238aa31b21370cd979f7e7def4a20031aac70.


Particle/sound effect when a mob spawns naturally in the world

When a living entity naturally spawns in the world (a monster spawns at night, or an animal spawns), some particle effect - like smoke - accompanies the entity.
Some sound effect could also be played, such as a "pop" (egg) sound.

i vaguely remember the "flame" particles being associated with mobs spawns in older versions, though i could very well be misremembering. this was most noticeable in peaceful mode

i vaguely remember the "flame" particles being associated with mobs spawns in older versions, though i could very well be misremembering. this was most noticeable in peaceful mode

Flame particles are (were?) used for spawners, at least.

Flame particles are (were?) used for spawners, at least.

i'm aware of spawner particles, as well as the smoke clouds they make when spawning mobs, but i recall the torch particles appearing at the center of a mob when it naturally spawned.

i'm aware of spawner particles, as well as the smoke clouds they make when spawning mobs, but i recall the torch particles appearing at the center of a mob when it naturally spawned.

If so, it's not present in Beta 1.2_01 which is the current legacy version of Minecraft I have around and decompiled.

If so, it's not present in Beta 1.2_01 which is the current legacy version of Minecraft I have around and decompiled.

I was not playing the game in the beta stage, i'll check some versions later today and update this if I can find if it exists

I was not playing the game in the beta stage, i'll check some versions later today and update this if I can find if it exists

I've received an overwhelming number of feature requests over the week and they are filling up the issue tracker and making it difficult to keep track of what is even going on. I've enabled Discussions on the repo as a new location for feature requests. Unfortunately, GitHub has "temporarily" disabled the ability to convert issues to discussions, so I'm closing all feature request issues. However, I'm tracking all the closed issues in a Project board; despite being closed, they're still on my radar on the board. All new feature requests must go to Discussions. Feature requests opened as issues going forward will be closed.

I've received an overwhelming number of feature requests over the week and they are filling up the issue tracker and making it difficult to keep track of what is even going on. I've enabled Discussions on the repo as a new location for feature requests. Unfortunately, GitHub has "temporarily" disabled the ability to convert issues to discussions, so I'm closing all feature request issues. However, I'm tracking all the closed issues in a Project board; despite being closed, they're still on my radar on the board. All new feature requests must go to Discussions. Feature requests opened as issues going forward will be closed.


Why use drop_last=True in test (and val) dataloader?

Hi,
First, thanks for the excellent paper and for sharing this repo. Great work!
I want to ask why do you set the test dataloader drop_last=True? By doing that performance is not reported for all samples in the test dataset (some samples will be dropped, which is not what we want). In addition to this, changes in the batch size would lead to reporting performance on a different number of samples.
I've tested the difference by setting drop_last=False with the ILI dataset and the result is worse than the published one, although it still is the best-published result I've seen so far.
I saw the same issue in the Autoformer repo and logged an issue (https://github.com/thuml/Autoformer/issues/104). As a result they've now updated the code.
BTW, this is likely to also occur with other papers that seem to use a similar code base to Autoformer's.

Hi @oguiza, that is a great catch. Thank you very much! Our thought was to use the same setting in the dataloader they had for a fair comparison. But you are correct that setting drop_last=True will lead to the number of test samples not to be consistent with different choices of the batch size, although this difference may not cause a significant performance drop. We will change that setting in the code.
For self-supervised learning, we accidentally use the default drop_last=False which turns out to be the right choice, and the reported self-supervised results in the paper is for this setting.

Thanks for your quick response @namctin.
I just run the script on the ILI dataset and the difference was significant in my opinion. If the performance with self-supervised is measured with all test samples as you say, this might indicate that the difference between supervised and self-supervised would be bigger than what's reflected in your paper. I'm sharing this just in case you want to investigate it further.

Do you mean ILI results is much worse than results in paper(supervised)? @oguiza

Thank you for confirming the result @oguiza! Since ILI is a fairly small dataset, so the setting of drop_last can affect the result. I would think this will be diminished for larger datasets. But in any case, we should set the drop_last=False and we will fix that in the code.

I discovered that a number of the performance gain in the supervised patchTST comes from using 'drop_last=True' for the test dataset.
With 'drop_last=False', for the ETTh1, Traffic, and Illness datasets, there was a drop in performance, while there was no drop for the Weather dataset.
I have not yet tested on the other datasets.
I think this can be a significant problem, as it would require the most of the tables in the paper to be rewritten and this could be considered as a cheating.


[MINOR] Add markdown escaping to find missing parts

What is this PR for?
Currently {{note.id}}>{{noteName(note)}} is not shown in notebookashomepage.md. So I added markdown escaping for this.
What type of PR is it?
Documentation
What is the Jira issue?
no Jira issue for this
How should this be tested?
Please see the below screenshot imgs :)
Screenshots (if appropriate)

Before

After

Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

LGTM! 👍

@tae-jun Thanks!
Merge if there are no more discussions.


merge transaction expiration time stamp update

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

BingAds/hotel-ads/release-notes.md
:white_check_mark:Succeeded

BingAds/hotel-service/reference.md
:white_check_mark:Succeeded

BingAds/transaction-message/create-transaction-message.md
:white_check_mark:Succeeded

BingAds/transaction-message/google-bing-transaction-message-differences.md
:white_check_mark:Succeeded

BingAds/transaction-message/reference.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.