New : component extension demo

This PR will not be merged into integration, instead we will just keep it aside as a reference for demo purpose.

I don't think that this code should ever be merged. The point of the extension documentation is to teach someone how to extend the app. If the extension is already built, it kinda defeats the purpose. Maybe it can live on as a separate branch (linked to in the documentation). Even that seems slightly weird.


POST create data should not send index

When I want to create a data like "user", I'd like to make a request like this:
fetch('rooturl/users', {
    method: 'POST',
    body: { username: 'xxxx', passwd: '*****' }
})

instead of:
fetch('rooturl/users/1', {
    method: 'POST',
    body: { username: 'xxxx', passwd: '*****' }
})

then you assign an id to this data.
Now the data structure should look like this:
{
     users: [
         { id: 0, username: 'xxxx', passwd: '*****' }
     ]
}

then I can get all users:
fetch('rooturl/users', {
    method: 'GET'
})

and get one of them:
// id = 0
fetch('rooturl/users/${id}', {
    method: 'GET'
})

update it:
// id = 0
fetch('rooturl/users/${id}', {
    method: 'PUT',
    body: { username: 'xxx', passwd: '******' }
})

or
// id = 0
fetch('rooturl/users', {
    method: 'PUT',
    body: { id: id, username: 'xxx', passwd: '******' }
})

and delete it:
// id = 0
fetch('rooturl/users/${id}', {
    method: 'DELETE'
})

Do you think so?
In addition, why don't you open the dashboard?

I don't think that is really what this project is about. It does not have any logic in it's backend. To make something like this work the server would need to be aware of data structure. It is not aware of that. Use something like firebase instead or implement this in a custom backend.


Robot goes around in circles.

I cloned this repo and ran the training, however, there has been no noticable improvement in the reward and the robot just goes around rotating, and does not move at all. Am I missing setting some parameters or getting overly stressed way too early in the training process ?

It is moving a bit, but mainly just in circles, Also, I'm running this on an Titan RTX and it trained around 52 epochs in around 15 hours, I think its taking longer than it should, but I don't know how to change that.

Hi,
It could just e that you need to change the seed for the initialization of the network.
See explanation here: https://github.com/reiniscimurs/DRL-robot-navigation/issues/19
Let me know if that does not work, then we can look into it deeper.

Thank you, will try that. Also thank you for being so responsive

This worked perfectly.

This worked perfectly.

Hi, can you please tell me what your seed value is set at? I have set many values without good results and end up in the situation described in your question.

This worked perfectly.

Please may I know which value of seed has worked good I have tried many values but no improvement.


gflags master + Windows 10 + VS2015 = setlocal error during building project

Good afternoon all,
This is my first post on GitHub, so apologies if I've not formatted my comment/problem correct (any feedback would be appreciated).
I downloaded Gflags today because I need it as a dependency for the Ceres non-linear solver library. However, after running CMAKE, I tried to use Visual Studio 2015 (VS2015) to build the generated gflags.sln, and got the following error:
5>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: The command "setlocal
5>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: E:\cmake-3.5.1-win32-x86\cmake-3.5.1-win32-x86\bin\cmake.exe -DBUILD_TYPE=Release -P cmake_install.cmake
5>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: if %errorlevel% neq 0 goto :cmEnd
5>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: :cmEnd
5>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone
5>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: :cmErrorLevel
5>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: exit /b %1
5>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: :cmDone
5>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: if %errorlevel% neq 0 goto :VCEnd
5>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: :VCEnd" exited with code 1.
I've got the exact same error for the current Master branch, and the Release branch.
Any help would be greatly appreciated.
Best regards,
Frazer

Okay, so just in case there's anyone else who experiences the same issue, it turns out that CMAKE configured the solution to install to C:/Program Files/..., which needs administrative privileges. To work around this problem, just change the CMAKE_INSTALL_PREFIX to something else, e.g. E:/gflags.


Auto Commenting when an issue is closed by repo maintainer

This feature aims to solve the problem of poor communication and lack of acknowledgment when issues are closed. By automatically commenting on closed issues, it ensures that contributors are informed about the closure and are thanked for their efforts. This helps maintain a positive and engaging community atmosphere, encouraging continued contributions and fostering good relationships between maintainers and contributors.

@Akshat111111 please assign me this issue under gssoc'24

This feature aims to solve the problem of poor communication and lack of acknowledgment when issues are closed. By automatically commenting on closed issues, it ensures that contributors are informed about the closure and are thanked for their efforts. This helps maintain a positive and engaging community atmosphere, encouraging continued contributions and fostering good relationships between maintainers and contributors.

nice idea, you can start working on it.

@Akshat111111 Please don't revert it, the error is occuring because GITHUB_TOKEN does not have necessary conditions to carry out the actions specified in the workflow file. The solution for this is:

Create a Personal Access Token (PAT)

Go to your GitHub settings.
Navigate to Developer settings -> Personal access tokens -> Tokens (classic).
Generate a new token with the required scopes ( permission to be granted: repo).

Navigate to Settings -> Secrets and variables -> Actions.
Click New repository secret.
Name it something like PAT_GITHUB and paste your PAT.

Update Your Workflow File

Replace the instances of GITHUB_TOKEN with PAT_GITHUB

@Akshat111111 Please don't revert it, the error is occuring because GITHUB_TOKEN does not have necessary conditions to carry out the actions specified in the workflow file. The solution for this is:

Create a Personal Access Token (PAT)

Go to your GitHub settings.
Navigate to Developer settings -> Personal access tokens -> Tokens (classic).
Generate a new token with the required scopes ( permission to be granted: repo).

Navigate to Settings -> Secrets and variables -> Actions.
Click New repository secret.
Name it something like PAT_GITHUB and paste your PAT.

Update Your Workflow File

Replace the instances of GITHUB_TOKEN with PAT_GITHUB

But it can cause future problems and its not necessary to do so

@Akshat111111 ok no problem


Fix conda-forge build

Subj

This is porting the changes made in hdk-feedstock back to our repo?

Yes, plus I've added some heuristics to guess a config name


Client crashed when clicked on inventory

So put this code in that doesn't have the perandus coin but when I click on inventory, it crashes. Not sure what's going on :(
<List name="MyTabs">
      <!--If you only want Procurement to download specific tabs list them here, eg :-->
      	<Item value="Tab1" />
	<Item value="Tab2" />
	<Item value="Tab3" />
	<Item value="Tab4" />
	<Item value="Tab5" />
	<Item value="Tab6" />
</List>

Looks like you're using none premium tabs, for those you need to use just the number of the tab, so "1" and not "Tab1".
Try that, if you still have issues, paste what's in your debug file.

I'm still having issues :(  SOrry for the trouble.  Below is my debug file
[10-03-2016 21:05] System.InvalidOperationException: Sequence contains no matching element
at System.Linq.Enumerable.First[TSource](IEnumerable1 source, Func2 predicate)
at POEApi.Model.ProxyMapper.GetOrbType(String name)
[10-03-2016 21:05] ProxyMapper.GetOrbType Failed! ItemType = Perandus Coin
[10-03-2016 21:05] System.Exception: ProxyMapper.GetOrbType Failed! ItemType = Perandus Coin
at POEApi.Model.ProxyMapper.GetOrbType(String name)
at POEApi.Model.Currency..ctor(Item item)
at POEApi.Model.ItemFactory.Get(Item item)
[10-03-2016 21:05] ItemFactory unable to instanciate type : Perandus Coin
[10-03-2016 21:05] Error downloading stash for Hardcore Perandus, exception details: System.Exception: ItemFactory unable to instanciate type : Perandus Coin
at POEApi.Model.ItemFactory.Get(Item item)
at System.Linq.Enumerable.WhereSelectListIterator2.MoveNext()    at System.Collections.Generic.List1..ctor(IEnumerable1 collection)    at System.Linq.Enumerable.ToList[TSource](IEnumerable1 source)
at POEApi.Model.Stash..ctor(Stash proxy)
at POEApi.Model.POEModel.GetStash(Int32 index, String league, String accountName, Boolean forceRefresh)
at POEApi.Model.POEModel.getAllTabs(String league, String accountName, Stash stash)
at POEApi.Model.POEModel.GetStash(String league, String accountName)
[10-03-2016 21:05] System.Exception: Downloading stash for Hardcore Perandus, details logged to DebugInfo.log, please open a ticket at https://github.com/Stickymaddness/Procurement/issues and include your DebugInfo.log
at POEApi.Model.POEModel.GetStash(String league, String accountName)
at Procurement.ViewModel.LoginWindowViewModel.LoadStashItems(Character character)
at Procurement.ViewModel.LoginWindowViewModel.d__6.MoveNext()
at System.Collections.Generic.List1..ctor(IEnumerable1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable1 source)    at Procurement.ViewModel.LoginWindowViewModel.<>c__DisplayClass2.<Login>b__1()    at System.Threading.Tasks.Task.Execute() [10-03-2016 21:06] System.InvalidOperationException: Sequence contains no matching element    at System.Linq.Enumerable.First[TSource](IEnumerable1 source, Func2 predicate)    at POEApi.Model.ProxyMapper.GetOrbType(String name) [10-03-2016 21:06] ProxyMapper.GetOrbType Failed! ItemType = Perandus Coin [10-03-2016 21:06] System.Exception: ProxyMapper.GetOrbType Failed! ItemType = Perandus Coin    at POEApi.Model.ProxyMapper.GetOrbType(String name)    at POEApi.Model.Currency..ctor(Item item)    at POEApi.Model.ItemFactory.Get(Item item) [10-03-2016 21:06] ItemFactory unable to instanciate type : Perandus Coin [10-03-2016 21:06] Error downloading stash for Hardcore Perandus, exception details: System.Exception: ItemFactory unable to instanciate type : Perandus Coin    at POEApi.Model.ItemFactory.Get(Item item)    at System.Linq.Enumerable.WhereSelectListIterator2.MoveNext()
at System.Collections.Generic.List1..ctor(IEnumerable1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable1 source)    at POEApi.Model.Stash..ctor(Stash proxy)    at POEApi.Model.POEModel.GetStash(Int32 index, String league, String accountName, Boolean forceRefresh)    at POEApi.Model.POEModel.getAllTabs(String league, String accountName, Stash stash)    at POEApi.Model.POEModel.GetStash(String league, String accountName) [10-03-2016 21:06] System.Exception: Downloading stash for Hardcore Perandus, details logged to DebugInfo.log, please open a ticket at https://github.com/Stickymaddness/Procurement/issues and include your DebugInfo.log    at POEApi.Model.POEModel.GetStash(String league, String accountName)    at Procurement.ViewModel.LoginWindowViewModel.LoadStashItems(Character character)    at Procurement.ViewModel.LoginWindowViewModel.<LoadItems>d__6.MoveNext()    at System.Collections.Generic.List1..ctor(IEnumerable1 collection)    at System.Linq.Enumerable.ToList[TSource](IEnumerable1 source)
at Procurement.ViewModel.LoginWindowViewModel.<>c__DisplayClass2.b__1()
at System.Threading.Tasks.Task.Execute()

I've released a new version of Procurement which fixes the coin issue, so you do not need to change your settings file or anything!
https://github.com/Stickymaddness/Procurement/releases/tag/1.9.8-RC2

Procurement 1.9.8 has been released, please retest and open a new issue if you still have problems
https://github.com/Stickymaddness/Procurement/releases/tag/1.9.8


Implements a mapper option

Summary
This PR allows jest-haste-map to generate additional files that aren't actually baked by the filesystem. The implementation is partial and experimental, since it doesn't remove the virtual files when their source file is being removed (they would have to be linked together in some way).
Test plan
Added a test.

Will fix the tests tomorrow 👍

I'm missing the bigger picture (use case) here

I'm figuring out ways to access the content of zip archives as if they were raw files (without unpacking them). In the case of Jest Haste Map, it requires to fake the existence of those "virtual files" (since Watchman isn't aware about them), so the idea is that the configured mapper will detect such archives and replace them by their content in the haste map.

@SimenB the travis failure doesn't seem related to my diff, right?


#uicontrol not working

Using the demo website and my own dev server, I've found the #uicontrol directive mentioned on the Image Layer Rendering page doesn't seem to be supported when updating the shader.

Hmm, it's possible that the demo version is not the latest build? UI
control commit seems pretty recent.
On Fri, 18 Oct. 2019, 05:14 Chris Roat<EMAIL_ADDRESS>wrote:

Using the demo
https://neuroglancer-demo.appspot.com/#!{"layers":[{"source":"precomputed://gs://neuroglancer-public-data/kasthuri2011/image"%2C"crossSectionRenderScale":0.835863629425607%2C"type":"image"%2C"opacity":0.64%2C"shader":"%23uicontrol float brightness slider(min=-1%2C max=1)\nvoid main() {\n  emitGrayscale(toNormalized(getDataValue()) + brightness)%3B\n}\n"%2C"name":"original-image"}]%2C"navigation":{"pose":{"position":{"voxelSize":[6%2C6%2C30]%2C"voxelCoordinates":[5590.55419921875%2C8720.7275390625%2C1097.0750732421875]}}%2C"zoomFactor":45.146224259999094}%2C"perspectiveOrientation":[-0.00007811884279362857%2C-0.8536661863327026%2C-0.393139511346817%2C-0.341607004404068]%2C"perspectiveZoom":340.35867907175077%2C"selectedLayer":{"layer":"original-image"%2C"visible":true%2C"size":599}%2C"layout":"4panel"}
website and my own dev server, I've found the #uicontrol directive
mentioned on the Image Layer Rendering
https://github.com/google/neuroglancer/blob/ebb893928bc00ee61508f2c6ce23e01fe0e650c9/src/neuroglancer/sliceview/image_layer_rendering.md
page doesn't seem to be supported when updating the shader.
[image: Screen Shot 2019-10-17 at 8 12 55 PM]
https://user-images.githubusercontent.com/1053153/67063162-94d5e400-f11a-11e9-9a2e-3ed427e39796.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/neuroglancer/issues/168?email_source=notifications&email_token=AET34F2MJLU6OADOPIPDJODQPES2LA5CNFSM4JCB72V2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HSUDZRQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AET34F55ND2P3YYIG7ATLVLQPES2LANCNFSM4JCB72VQ
.

Ah, you are likely correct.  When I tested on my dev server, I just type "#uicontrol" and got the same error.
The error goes away when the full #uicontrol line is entered.  A better error might be "syntax error" if the directive is correct, but the usage is incomplete/wrong.


schutzbot: run openstack/* jobs on a dedicated runner

We have limited resources in openstack. We can only run about 40 concurrent VMs.
Previously, the rate limiting was kinda stupid:
All (aws and openstack) jobs were run using the same runner. This runner was
globally limited to 60 concurrent jobs. For openstack, the individual
images were also limited to a certain number of concurrent jobs in
the gitlab-ci-terraform repository so we don't hit the quota. This limit
was applied at runtime - the first thing that an openstack job did was to
wait for a slot. This job counted towards the global limit of jobs (60)
and thus was blocking one slot without doing any useful work.
 We have much
more demand for rhel-8.5 runner than for e.g. Fedora. It would be much
better to just use global limit that would map much nicely to global
quota.
Today, I've introduced a new runner with tag terraform/openstack. It's
currently limited to 20 concurrent jobs. All jobs running on openstack should
run on the new runner. This runner has the local rate limiting for openstack
disabled. This means that we can run 20 concurrent openstack jobs and it
doesn't matter which distribution they run.
To sum it up, this has two benefits:

no local limits, we can just use the full quota
no idling jobs waiting for an openstack slot

Note that the openstack global limit is currently set to 20, I will raise
it once all PRs are rebased on top of this change.
Side effect: I moved all libvirt test to openstack. I think this is overall
better because testing guest images on KVM makes more sense than testing them
on TCG.
Signed-off-by: Ondřej Budai<EMAIL_ADDRESS>This pull request includes:

[ ] adequate testing for the new functionality or fixed issue
[ ] adequate documentation informing people about the change such as

[ ] create a file in news/unreleased directory if this change should be mentioned in the release news
[ ] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/

Force-pushed to fix a conflict.

Yeah, I will rebase it as soon as I come home.

Rebased.


allow derived types of DataFrame

This PR updates DataFrame type checkings to allow derived types of DataFrame as input type.

@microsoft-github-policy-service agree [company="Amazon"]

@microsoft-github-policy-service agree company="Amazon"

@microsoft-github-policy-service agree

@microsoft-github-policy-service agree company="Amazon"

Codecov Report

Merging #637 (f95dcb9) into main (a090681) will decrease coverage by 0.01%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##             main     #637      +/-   ##
==========================================
- Coverage   90.20%   90.18%   -0.02%
==========================================
  Files          78       77       -1
  Lines        4563     4556       -7
  Branches      945      846      -99
==========================================
- Hits         4116     4109       -7
  Misses        252      252
  Partials      195      195

Flag
Coverage Δ

unittests
90.18% <66.66%> (-0.02%)
:arrow_down:

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

Impacted Files
Coverage Δ

hummingbird/ml/_executor.py
82.19% <0.00%> (ø)

...ngbird/ml/containers/sklearn/pytorch_containers.py
83.33% <0.00%> (ø)

hummingbird/ml/_utils.py
88.13% <100.00%> (ø)

...mmingbird/ml/containers/_sklearn_api_containers.py
89.39% <100.00%> (ø)

hummingbird/ml/containers/batch_container.py
85.00% <100.00%> (ø)

hummingbird/__init__.py

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


node_modules animation-mixer not working

Do you want to request a feature or report a bug?
Report a bug

What is the current behavior?
When I use nextjs / webpack /node_modules the animation-mixer does not work, but it works with pure html / js
If the current behavior is a bug, please provide the steps to reproduce.
create a nextjs project (or any project that uses node_modules)
npm install @ar-js-org/ar.js aframe aframe-extras`

{
 ...
<EMAIL_ADDRESS>"^3.4.5",
     "aframe": "^1.3.0",
    "aframe-extras": "^7.2.0",
}

render a client component like
import "aframe";
import<EMAIL_ADDRESS>import "aframe-extras";

<a-scene>
<a-marker preset="hiro">
<a-entity
  position="0 0 0"
  rotation="-90 0 0"
  scale="3 3 3"
  gltf-model="/t3.glb"
  animation-mixer
    ></a-entity>
  </a-marker>
</a-scene>

The 3d model shows up but does not animate, where as w/o node_modules it works and animates
<!DOCTYPE html>
<html>
<script src="https://aframe.io/releases/1.3.0/aframe.min.js"></script>
<script src="https://raw.githack.com/AR-js-org/AR.js/dev/aframe/build/aframe-ar.js"></script>
<script<EMAIL_ADDRESS><body style="margin : 0px; overflow: hidden;">
  <a-scene>
    <a-marker preset="hiro">
      <a-entity position="0 0 0" rotation="-90 0 0" scale="3 3 3" gltf-model="./3d3/t3.glb" animation-mixer></a-entity>
      <a-entity scale="5 5 5" text="value: Transmute;"></a-entity>
    </a-marker>
    <a-entity camera></a-entity>
  </a-scene>
</body>
</html>

Please mention other relevant information such as the browser version, Operating System and Device Name
Brave Version 1.66.110 Chromium: 125.0.6422.60 (Official Build) (64-bit) Ubuntu 24.04 LTS Desktop computer
What is the expected behavior?
Should animate the glb 3d asset
If this is a feature request, what is motivation or use case for changing the behavior?

I know nothing about nextjs so I can't help you with this specific setup. But I have a project using just webpack and a static index.html, that works fine using aframe cdn or npm dependencies.
Your above configuration doesn't make any sense, are you using npm dependencies or the cdn? Please use one or the other, not both. Do you have any errors in the console?

Thanks for the quick response, everything works, like the 3d model displays in the camera above the marker, except for the animation when node_modules and import syntax basically.

I know nothing about nextjs so I can't help you with this specific setup. But I have a project using just webpack and a static index.html, that works fine using aframe cdn or npm dependencies.
I think this would be the same with webpack, if you could share your code where the animation works with glb and animation-mixer that would be helpful for me if it works to see if I am doing some setup incorrectly.
Your above configuration doesn't make any sense, are you using npm dependencies or the cdn? Please use one or the other, not both. Do you have any errors in the console?
I am saying if I use import and node_modules animate doesn't work, this is what I am using and would like to get working, I am just saying that my glb 3d asset and animation normally works when using a cdn , I don't see any console errors.  But these are the logs I see around aframe / ar.js when the page loads

A-Frame Version: 1.5.0 (Date 2023-11-14, Commit #7856a058)
page.js:5023 THREE Version (https://github.com/supermedium/three.js): 0.158.0
page.js:5023 WebVR Polyfill Version: ^0.10.12
page.js:7471 WARNING: Multiple instances of Three.js being imported.
eval @ three.cjs:50433
...
page.js:8238 WARNING: Multiple instances of Three.js being imported.

If you see the "WARNING: Multiple instances of Three.js being imported." message that's not normal with latest aframe-extras. Double check you don't include the scripts twice.
I have an example of webpack config and static index.html in https://github.com/networked-aframe/naf-valid-avatars/ using a components bundle and defer ui bundle. That example uses aframe and aframe-extras with cdn in index.html. But you can put aframe and aframe-extras imports in src/components.js instead, that will work the same.

@acarnagey I just released a new AR.js version (3.4.6) can you test with it? I also provided a module version, though i don't know if it can help you in some way...


Account registration request fails

With the latest version of nginx-proxy the following error message is shown when registering a new account:
 ACME server returned an error: urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Account creation on ACMEv1 is disabled. Please upgrade your ACME client to a version that supports ACMEv2 / RFC 8555. See https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for details.

Indeed, Letsencrypt has stopped supporting ACMEv1 registration requests. Is there a chance to get an ACMEv2 capable client into the nginx-proxy image?
Thank you for your support!
Sascha

Sorry, wrong issue tracker - it's an issue for the nginx-proxy letsencrypt-companion.


Add multiple local agents support

As a user I'd like to use the same xds-server to build multiple projects from multiple xds-agents.
I'm currently setting a docker with xds-server in our internal infrastructure and it will be really good if we can share the same build server (xds-server) within multiple projects/users.
This might also be implemented by moving the Global Configuration to each projects' configuration.

Hello,
The "Global Configuration" is already agent/client specific. So there is no need (and that doesn't make sens) to move "Global Configuration" settings to each projects.
I have no yet tested multiple xds-agent connected to one xds-server but I don't see any restriction to do that.
Would you please tell me more about what problem you are facing ?

You are right. I could check it. I though that the project were available for everyone on the server side. Now with your comment I tested and it's actually agent-wise.


getRedisNodes().pingAll() returning false after Redis sentinel restart in Kubernetes setup

We have a 3 node sentinel cluster deployed in Kubernetes and use pingAll() to check for connection issues.
Now after a restart of Redis pingAll() returns false. I assume the following, please correct me if I am wrong:

The Redis connections are based on IP addresses, not hostnames
Redisson keeps track of the Redis nodes by their IP address

Now in Kubernetes a Redis node will get a new IP address upon restart. Is there a recommended configuration to prevent issues with this? I believe this may impact not only the pingAll() method but also other functions?
The redisson configuration is the following:
redis:
  redisson:
    config: |-
      sentinelServersConfig:
          password: ${REDIS_AUTHENTICATION_PASSWORD}
          masterName: "mymaster"
          sentinelsDiscovery: false
          sentinelAddresses:
          - "redis://redis-headless.myapp:26379"

Note that this issue also occurs, when I explicitly set all 3 nodes in the sentinel addresses list like this:
sentinelAddresses:
- "redis://redis-node-0.redis-headless.myapp:26379"
- "redis://redis-node-1.redis-headless.myapp:26379"
- "redis://redis-node-2.redis-headless.myapp:26379"

@mrniko Any chance you could reply to this?

Now after a restart of Redis pingAll() returns false

It might be a temporary issue, until dns resolver get new ip addresses.
Can you share logs with trace logging level for org.redisson package?

It might be a temporary issue, until dns resolver get new ip addresses.

To be honest I don't think so. We had Redisson report a pingAll() result of false while being connected to the restarted nodes for 3 days. After we restart our application Redisson has no issues at all. As far as we observed it does not "recover" automatically.

Can you share logs with trace logging level for org.redisson package?

I'd be happy to. Could you tell me what kind of logs we're looking for? In our setup Redisson logs a lot of messages on trace so there's a lot of noise.

logs during pingAll method invocation. Can you also report which Redisson version do you use?

We're using Redisson 3.17.4. These should be all logs exactly between the ping. They're JSON formatted. If that should be an issue I can try to extract the messages to a different format.
What I can already see is that in the "Connection created" lines the IPs <IP_ADDRESS> and (further to the bottom) <IP_ADDRESS> are wrong and refer to old Redis nodes. In this log only the following IPs are valid Redis IPs <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS> while the IP <IP_ADDRESS> is the application using Redisson.
Thank you for looking into it. If I can help you somehow please let me know!
{"@timestamp":"2022-07-18T18:44:22.886Z","@version":"1","message":"pinging redis","logger_name":"com.mycompany.myproduct.myapp.dataaccess.redis.RedisConnectionMetrics","thread_name":"scheduling-1","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.887Z","@version":"1","message":"Connection created [addr=redis://<IP_ADDRESS>:6379]","logger_name":"org.redisson.client.RedisConnection","thread_name":"redisson-netty-2-13","level":"DEBUG","level_value":10000}
{"@timestamp":"2022-07-18T18:44:22.887Z","@version":"1","message":"Connection created [addr=redis://<IP_ADDRESS>:6379]","logger_name":"org.redisson.client.RedisConnection","thread_name":"redisson-netty-2-29","level":"DEBUG","level_value":10000}
{"@timestamp":"2022-07-18T18:44:22.887Z","@version":"1","message":"Connection created [addr=redis://<IP_ADDRESS>:6379]","logger_name":"org.redisson.client.RedisConnection","thread_name":"redisson-netty-2-14","level":"DEBUG","level_value":10000}
{"@timestamp":"2022-07-18T18:44:22.887Z","@version":"1","message":"Connection created [addr=redis://<IP_ADDRESS>:6379]","logger_name":"org.redisson.client.RedisConnection","thread_name":"redisson-netty-2-15","level":"DEBUG","level_value":10000}
{"@timestamp":"2022-07-18T18:44:22.887Z","@version":"1","message":"channel: [id: 0x4a83dd31, L:/<IP_ADDRESS>:43970 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379] message: *2\r\n$4\r\nAUTH(password masked)","logger_name":"org.redisson.client.handler.CommandEncoder","thread_name":"redisson-netty-2-13","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.887Z","@version":"1","message":"reply: +OK\r\n, channel: [id: 0xf7b9e0c8, L:/<IP_ADDRESS>:40280 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379], command: CommandData [promise=java.util.concurrent.CompletableFuture@d285081[Not completed, 2 dependents], command=(QUIT), params=[], codec=null]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-31","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.887Z","@version":"1","message":"reply: +OK\r\n, channel: [id: 0xca9c8b3a, L:/<IP_ADDRESS>:43910 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379], command: CommandData [promise=java.util.concurrent.CompletableFuture@58dabbea[Not completed, 2 dependents], command=(QUIT), params=[], codec=null]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-17","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.888Z","@version":"1","message":"channel: [id: 0x4a83dd31, L:/<IP_ADDRESS>:43970 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379] message: *1\r\n$4\r\nPING\r\n","logger_name":"org.redisson.client.handler.CommandEncoder","thread_name":"redisson-netty-2-13","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.888Z","@version":"1","message":"reply: +OK\r\n, channel: [id: 0xea573406, L:/<IP_ADDRESS>:52152 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379], command: CommandData [promise=java.util.concurrent.CompletableFuture@41654763[Not completed, 2 dependents], command=(QUIT), params=[], codec=null]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-18","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.888Z","@version":"1","message":"channel: [id: 0xad98aa09, L:/<IP_ADDRESS>:40348 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379] message: *2\r\n$4\r\nAUTH(password masked)","logger_name":"org.redisson.client.handler.CommandEncoder","thread_name":"redisson-netty-2-15","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.888Z","@version":"1","message":"channel: [id: 0x7a601e5d, L:/<IP_ADDRESS>:52218 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379] message: *2\r\n$4\r\nAUTH(password masked)","logger_name":"org.redisson.client.handler.CommandEncoder","thread_name":"redisson-netty-2-14","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.888Z","@version":"1","message":"reply: +OK\r\n+PONG\r\n, channel: [id: 0x4a83dd31, L:/<IP_ADDRESS>:43970 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379], command: CommandData [promise=java.util.concurrent.CompletableFuture@3c245f7[Not completed, 2 dependents], command=(AUTH), params=[a23kf1qqylpg3de1vgg50ysfa], codec=null]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-13","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.888Z","@version":"1","message":"channel: [id: 0xad98aa09, L:/<IP_ADDRESS>:40348 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379] message: *1\r\n$4\r\nPING\r\n","logger_name":"org.redisson.client.handler.CommandEncoder","thread_name":"redisson-netty-2-15","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.888Z","@version":"1","message":"reply: +OK\r\n+PONG\r\n, channel: [id: 0x4a83dd31, L:/<IP_ADDRESS>:43970 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379], command: CommandData [promise=java.util.concurrent.CompletableFuture@2c9a740e[Not completed, 2 dependents], command=(PING), params=[], codec=null]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-13","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.888Z","@version":"1","message":"channel: [id: 0x7a601e5d, L:/<IP_ADDRESS>:52218 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379] message: *1\r\n$4\r\nPING\r\n","logger_name":"org.redisson.client.handler.CommandEncoder","thread_name":"redisson-netty-2-14","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.888Z","@version":"1","message":"channel: [id: 0x4a83dd31, L:/<IP_ADDRESS>:43970 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379] message: *1\r\n$4\r\nPING\r\n","logger_name":"org.redisson.client.handler.CommandEncoder","thread_name":"redisson-netty-2-13","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.888Z","@version":"1","message":"reply: +OK\r\n, channel: [id: 0xad98aa09, L:/<IP_ADDRESS>:40348 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379], command: CommandData [promise=java.util.concurrent.CompletableFuture@37fd661f[Not completed, 2 dependents], command=(AUTH), params=[a23kf1qqylpg3de1vgg50ysfa], codec=null]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-15","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.888Z","@version":"1","message":"channel: [id: 0x4a83dd31, L:/<IP_ADDRESS>:43970 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379] message: *1\r\n$4\r\nPING\r\n","logger_name":"org.redisson.client.handler.CommandEncoder","thread_name":"redisson-netty-2-13","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.888Z","@version":"1","message":"reply: +OK\r\n, channel: [id: 0x7a601e5d, L:/<IP_ADDRESS>:52218 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379], command: CommandData [promise=java.util.concurrent.CompletableFuture@c47a5a0[Not completed, 2 dependents], command=(AUTH), params=[a23kf1qqylpg3de1vgg50ysfa], codec=null]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-14","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.888Z","@version":"1","message":"reply: +PONG\r\n, channel: [id: 0xad98aa09, L:/<IP_ADDRESS>:40348 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379], command: CommandData [promise=java.util.concurrent.CompletableFuture@73076843[Not completed, 2 dependents], command=(PING), params=[], codec=null]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-15","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.888Z","@version":"1","message":"reply: +PONG\r\n, channel: [id: 0x4a83dd31, L:/<IP_ADDRESS>:43970 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379], command: CommandData [promise=java.util.concurrent.CompletableFuture@9101f0e[Not completed, 1 dependents], command=(PING), params=[], codec=org.redisson.client.codec.StringCodec]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-13","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.888Z","@version":"1","message":"reply: +PONG\r\n, channel: [id: 0x7a601e5d, L:/<IP_ADDRESS>:52218 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379], command: CommandData [promise=java.util.concurrent.CompletableFuture@1767645a[Not completed, 2 dependents], command=(PING), params=[], codec=null]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-14","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.888Z","@version":"1","message":"channel: [id: 0xad98aa09, L:/<IP_ADDRESS>:40348 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379] message: *1\r\n$4\r\nPING\r\n","logger_name":"org.redisson.client.handler.CommandEncoder","thread_name":"redisson-netty-2-15","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.888Z","@version":"1","message":"channel: [id: 0x7a601e5d, L:/<IP_ADDRESS>:52218 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379] message: *1\r\n$4\r\nPING\r\n","logger_name":"org.redisson.client.handler.CommandEncoder","thread_name":"redisson-netty-2-14","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.889Z","@version":"1","message":"reply: +PONG\r\n, channel: [id: 0x4a83dd31, L:/<IP_ADDRESS>:43970 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379], command: CommandData [promise=java.util.concurrent.CompletableFuture@12262de4[Not completed, 1 dependents], command=(PING), params=[], codec=null]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-13","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.889Z","@version":"1","message":"channel: [id: 0x7a601e5d, L:/<IP_ADDRESS>:52218 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379] message: *1\r\n$4\r\nPING\r\n","logger_name":"org.redisson.client.handler.CommandEncoder","thread_name":"redisson-netty-2-14","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.889Z","@version":"1","message":"channel: [id: 0xad98aa09, L:/<IP_ADDRESS>:40348 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379] message: *1\r\n$4\r\nPING\r\n","logger_name":"org.redisson.client.handler.CommandEncoder","thread_name":"redisson-netty-2-15","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.889Z","@version":"1","message":"reply: +PONG\r\n, channel: [id: 0x7a601e5d, L:/<IP_ADDRESS>:52218 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379], command: CommandData [promise=java.util.concurrent.CompletableFuture@70be0bb[Not completed, 1 dependents], command=(PING), params=[], codec=org.redisson.client.codec.StringCodec]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-14","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.889Z","@version":"1","message":"reply: +PONG\r\n, channel: [id: 0xad98aa09, L:/<IP_ADDRESS>:40348 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379], command: CommandData [promise=java.util.concurrent.CompletableFuture@793533d8[Not completed, 1 dependents], command=(PING), params=[], codec=org.redisson.client.codec.StringCodec]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-15","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.889Z","@version":"1","message":"reply: +PONG\r\n, channel: [id: 0x7a601e5d, L:/<IP_ADDRESS>:52218 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379], command: CommandData [promise=java.util.concurrent.CompletableFuture@7d6eb3a9[Not completed, 1 dependents], command=(PING), params=[], codec=null]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-14","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:22.889Z","@version":"1","message":"reply: +PONG\r\n, channel: [id: 0xad98aa09, L:/<IP_ADDRESS>:40348 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379], command: CommandData [promise=java.util.concurrent.CompletableFuture@19a93bf7[Not completed, 1 dependents], command=(PING), params=[], codec=null]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-15","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:24.169Z","@version":"1","message":"reconnecting RedisConnection@155631377 [redisClient=[addr=redis://<IP_ADDRESS>:26379], channel=[id: 0x4654e868, L:/<IP_ADDRESS>:54374 ! R:<IP_ADDRESS>/<IP_ADDRESS>:26379], currentCommand=null, usage=0] to <IP_ADDRESS>/<IP_ADDRESS>:26379 ","logger_name":"org.redisson.client.handler.ConnectionWatchdog","thread_name":"redisson-timer-4-1","level":"DEBUG","level_value":10000}
{"@timestamp":"2022-07-18T18:44:24.170Z","@version":"1","message":"Connection created [addr=redis://<IP_ADDRESS>:26379]","logger_name":"org.redisson.client.RedisConnection","thread_name":"redisson-netty-2-18","level":"DEBUG","level_value":10000}
{"@timestamp":"2022-07-18T18:44:26.569Z","@version":"1","message":"reconnecting RedisConnection@353700576 [redisClient=[addr=redis://<IP_ADDRESS>:26379], channel=[id: 0xed35274c, L:/<IP_ADDRESS>:54814 ! R:<IP_ADDRESS>/<IP_ADDRESS>:26379], currentCommand=null, usage=0] to <IP_ADDRESS>/<IP_ADDRESS>:26379 ","logger_name":"org.redisson.client.handler.ConnectionWatchdog","thread_name":"redisson-timer-4-1","level":"DEBUG","level_value":10000}
{"@timestamp":"2022-07-18T18:44:26.569Z","@version":"1","message":"Connection created [addr=redis://<IP_ADDRESS>:26379]","logger_name":"org.redisson.client.RedisConnection","thread_name":"redisson-netty-2-31","level":"DEBUG","level_value":10000}
{"@timestamp":"2022-07-18T18:44:28.268Z","@version":"1","message":"channel: [id: 0xcc6b36a7, L:/<IP_ADDRESS>:43204 - R:<IP_ADDRESS>/<IP_ADDRESS>:26379] message: *3\r\n$8\r\nSENTINEL\r\n$23\r\nGET-MASTER-ADDR-BY-NAME\r\n$8\r\nmymaster\r\n","logger_name":"org.redisson.client.handler.CommandEncoder","thread_name":"redisson-netty-2-32","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:28.268Z","@version":"1","message":"channel: [id: 0xcc6b36a7, L:/<IP_ADDRESS>:43204 - R:<IP_ADDRESS>/<IP_ADDRESS>:26379] message: *3\r\n$8\r\nSENTINEL\r\n$6\r\nSLAVES\r\n$8\r\nmymaster\r\n","logger_name":"org.redisson.client.handler.CommandEncoder","thread_name":"redisson-netty-2-32","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:28.269Z","@version":"1","message":"reply: *2\r\n$53\r\nredis-node-1.redis-headless.myproduct.svc.cluster.local\r\n$4\r\n6379\r\n*2\r\n*42\r\n$4\r\nname\r\n$58\r\nredis-node-2.redis-headless.myproduct.svc.cluster.local:6379\r\n$2\r\nip\r\n$53\r\nredis-node-2.redis-headless.myproduct.svc.cluster.local\r\n$4\r\nport\r\n$4\r\n6379\r\n$5\r\nrunid\r\n$40\r\n92fbb556f16348cbe612dadd44c9ce5d1642d4ac\r\n$5\r\nflags\r\n$5\r\nslave\r\n$21\r\nlink-pending-commands\r\n$1\r\n0\r\n$13\r\nlink-refcount\r\n$1\r\n1\r\n$14\r\nlast-ping-sent\r\n$1\r\n0\r\n$18\r\nlast-ok-ping-reply\r\n$3\r\n585\r\n$15\r\nlast-ping-reply\r\n$3\r\n585\r\n$23\r\ndown-after-milliseconds\r\n$5\r\n60000\r\n$12\r\ninfo-refresh\r\n$4\r\n6953\r\n$13\r\nrole-reported\r\n$5\r\nslave\r\n$18\r\nrole-reported-time\r\n$6\r\n438437\r\n$21\r\nmaster-link-down-time\r\n$1\r\n0\r\n$18\r\nmaster-link-status\r\n$2\r\nok\r\n$11\r\nmaster-host\r\n$53\r\nredis-node-1.redis-headless.myproduct.svc.cluster.local\r\n$11\r\nmaster-port\r\n$4\r\n6379\r\n$14\r\nslave-priority\r\n$3\r\n100\r\n$17\r\nslave-repl-offset\r\n$10\r\n3803134056\r\n$17\r\nreplica-announced\r\n$1\r\n1\r\n*42\r\n$4\r\nname\r\n$58\r\nredis-node-0.redis-headless.myproduct.svc.cluster.local:6379\r\n$2\r\nip\r\n$53\r\nredis-node-0.redis-headless.myproduct.svc.cluster.local\r\n$4\r\nport\r\n$4\r\n6379\r\n$5\r\nrunid\r\n$40\r\n385de72864434b99c78c8b0b4a34056393b3795b\r\n$5\r\nflags\r\n$5\r\nslave\r\n$21\r\nlink-pending-commands\r\n$1\r\n0\r\n$13\r\nlink-refcount\r\n$1\r\n1\r\n$14\r\nlast-ping-sent\r\n$1\r\n0\r\n$18\r\nlast-ok-ping-reply\r\n$3\r\n585\r\n$15\r\nlast-ping-reply\r\n$3\r\n585\r\n$23\r\ndown-after-milliseconds\r\n$5\r\n60000\r\n$12\r\ninfo-refresh\r\n$4\r\n6898\r\n$13\r\nrole-reported\r\n$5\r\nslave\r\n$18\r\nrole-reported-time\r\n$6\r\n398241\r\n$21\r\nmaster-link-down-time\r\n$1\r\n0\r\n$18\r\nmaster-link-status\r\n$2\r\nok\r\n$11\r\nmaster-host\r\n$53\r\nredis-node-1.redis-headless.myproduct.svc.cluster.local\r\n$11\r\nmaster-port\r\n$4\r\n6379\r\n$14\r\nslave-priority\r\n$3\r\n100\r\n$17\r\nslave-repl-offset\r\n$10\r\n3803134056\r\n$17\r\nreplica-announced\r\n$1\r\n1\r\n, channel: [id: 0xcc6b36a7, L:/<IP_ADDRESS>:43204 - R:<IP_ADDRESS>/<IP_ADDRESS>:26379], command: CommandData [promise=java.util.concurrent.CompletableFuture@32f725b2[Not completed, 2 dependents], command=(SENTINEL GET-MASTER-ADDR-BY-NAME), params=[mymaster], codec=org.redisson.client.codec.StringCodec]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-32","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:28.270Z","@version":"1","message":"reply: *2\r\n$53\r\nredis-node-1.redis-headless.myproduct.svc.cluster.local\r\n$4\r\n6379\r\n*2\r\n*42\r\n$4\r\nname\r\n$58\r\nredis-node-2.redis-headless.myproduct.svc.cluster.local:6379\r\n$2\r\nip\r\n$53\r\nredis-node-2.redis-headless.myproduct.svc.cluster.local\r\n$4\r\nport\r\n$4\r\n6379\r\n$5\r\nrunid\r\n$40\r\n92fbb556f16348cbe612dadd44c9ce5d1642d4ac\r\n$5\r\nflags\r\n$5\r\nslave\r\n$21\r\nlink-pending-commands\r\n$1\r\n0\r\n$13\r\nlink-refcount\r\n$1\r\n1\r\n$14\r\nlast-ping-sent\r\n$1\r\n0\r\n$18\r\nlast-ok-ping-reply\r\n$3\r\n585\r\n$15\r\nlast-ping-reply\r\n$3\r\n585\r\n$23\r\ndown-after-milliseconds\r\n$5\r\n60000\r\n$12\r\ninfo-refresh\r\n$4\r\n6953\r\n$13\r\nrole-reported\r\n$5\r\nslave\r\n$18\r\nrole-reported-time\r\n$6\r\n438437\r\n$21\r\nmaster-link-down-time\r\n$1\r\n0\r\n$18\r\nmaster-link-status\r\n$2\r\nok\r\n$11\r\nmaster-host\r\n$53\r\nredis-node-1.redis-headless.myproduct.svc.cluster.local\r\n$11\r\nmaster-port\r\n$4\r\n6379\r\n$14\r\nslave-priority\r\n$3\r\n100\r\n$17\r\nslave-repl-offset\r\n$10\r\n3803134056\r\n$17\r\nreplica-announced\r\n$1\r\n1\r\n*42\r\n$4\r\nname\r\n$58\r\nredis-node-0.redis-headless.myproduct.svc.cluster.local:6379\r\n$2\r\nip\r\n$53\r\nredis-node-0.redis-headless.myproduct.svc.cluster.local\r\n$4\r\nport\r\n$4\r\n6379\r\n$5\r\nrunid\r\n$40\r\n385de72864434b99c78c8b0b4a34056393b3795b\r\n$5\r\nflags\r\n$5\r\nslave\r\n$21\r\nlink-pending-commands\r\n$1\r\n0\r\n$13\r\nlink-refcount\r\n$1\r\n1\r\n$14\r\nlast-ping-sent\r\n$1\r\n0\r\n$18\r\nlast-ok-ping-reply\r\n$3\r\n585\r\n$15\r\nlast-ping-reply\r\n$3\r\n585\r\n$23\r\ndown-after-milliseconds\r\n$5\r\n60000\r\n$12\r\ninfo-refresh\r\n$4\r\n6898\r\n$13\r\nrole-reported\r\n$5\r\nslave\r\n$18\r\nrole-reported-time\r\n$6\r\n398241\r\n$21\r\nmaster-link-down-time\r\n$1\r\n0\r\n$18\r\nmaster-link-status\r\n$2\r\nok\r\n$11\r\nmaster-host\r\n$53\r\nredis-node-1.redis-headless.myproduct.svc.cluster.local\r\n$11\r\nmaster-port\r\n$4\r\n6379\r\n$14\r\nslave-priority\r\n$3\r\n100\r\n$17\r\nslave-repl-offset\r\n$10\r\n3803134056\r\n$17\r\nreplica-announced\r\n$1\r\n1\r\n, channel: [id: 0xcc6b36a7, L:/<IP_ADDRESS>:43204 - R:<IP_ADDRESS>/<IP_ADDRESS>:26379], command: CommandData [promise=java.util.concurrent.CompletableFuture@1793ebda[Not completed, 2 dependents], command=(SENTINEL SLAVES), params=[mymaster], codec=org.redisson.client.codec.StringCodec]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-32","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:29.273Z","@version":"1","message":"Connection created [addr=redis://<IP_ADDRESS>:26379]","logger_name":"org.redisson.client.RedisConnection","thread_name":"redisson-netty-2-2","level":"DEBUG","level_value":10000}
{"@timestamp":"2022-07-18T18:44:31.769Z","@version":"1","message":"channel: [id: 0xab18e3af, L:/<IP_ADDRESS>:38792 - R:<IP_ADDRESS>/<IP_ADDRESS>:26379] message: *1\r\n$4\r\nPING\r\n","logger_name":"org.redisson.client.handler.CommandEncoder","thread_name":"redisson-netty-2-9","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:31.771Z","@version":"1","message":"reply: +PONG\r\n, channel: [id: 0xab18e3af, L:/<IP_ADDRESS>:38792 - R:<IP_ADDRESS>/<IP_ADDRESS>:26379], command: CommandData [promise=java.util.concurrent.CompletableFuture@2c0eafda[Not completed, 1 dependents], command=(PING), params=[], codec=org.redisson.client.codec.StringCodec]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-9","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:31.869Z","@version":"1","message":"channel: [id: 0xaef45073, L:/<IP_ADDRESS>:58860 - R:<IP_ADDRESS>/<IP_ADDRESS>:26379] message: *1\r\n$4\r\nPING\r\n","logger_name":"org.redisson.client.handler.CommandEncoder","thread_name":"redisson-netty-2-11","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:31.871Z","@version":"1","message":"reply: +PONG\r\n, channel: [id: 0xaef45073, L:/<IP_ADDRESS>:58860 - R:<IP_ADDRESS>/<IP_ADDRESS>:26379], command: CommandData [promise=java.util.concurrent.CompletableFuture@39f1760d[Not completed, 1 dependents], command=(PING), params=[], codec=org.redisson.client.codec.StringCodec]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-11","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:31.970Z","@version":"1","message":"channel: [id: 0x52af28e2, L:/<IP_ADDRESS>:42288 - R:<IP_ADDRESS>/<IP_ADDRESS>:26379] message: *1\r\n$4\r\nPING\r\n","logger_name":"org.redisson.client.handler.CommandEncoder","thread_name":"redisson-netty-2-26","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:31.970Z","@version":"1","message":"reply: +PONG\r\n, channel: [id: 0x52af28e2, L:/<IP_ADDRESS>:42288 - R:<IP_ADDRESS>/<IP_ADDRESS>:26379], command: CommandData [promise=java.util.concurrent.CompletableFuture@17ab8da1[Not completed, 1 dependents], command=(PING), params=[], codec=org.redisson.client.codec.StringCodec]","logger_name":"org.redisson.client.handler.CommandDecoder","thread_name":"redisson-netty-2-26","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:32.897Z","@version":"1","message":"channel: [id: 0xad98aa09, L:/<IP_ADDRESS>:40348 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379] message: *1\r\n$4\r\nQUIT\r\n","logger_name":"org.redisson.client.handler.CommandEncoder","thread_name":"redisson-netty-2-15","level":"TRACE","level_value":5000}
{"@timestamp":"2022-07-18T18:44:32.897Z","@version":"1","message":"done pinging redis (ping_result=false)","logger_name":"com.mycompany.myproduct.myapp.dataaccess.redis.RedisConnectionMetrics","thread_name":"scheduling-1","level":"TRACE","level_value":5000,"ping_result":false}

I spent a little time remote debugging this problem. My guess is that this issue occurs in the SentinelConnectionManager in performSentinelDNSCheck(..):
future.getNow().stream()
        .map(addr -> toURI(addr))
        .filter(uri -> !sentinels.containsKey(uri) && !disconnectedSentinels.contains(uri))
        .forEach(uri -> registerSentinel(uri, getConfig(), host.getHost()));

Apparently the check whether the RedisURI is already contained in one of the Sets is wrong and does not recognize the restarted Redis nodes. During my debugging what I saw was that the URIs contain the IP addresses and not the hostnames:
Before Redis restart:

After Redis restart:

After/During the Redis restart performSentinelDNSCheck(..) will call registerSentinel(..) for the Redis nodes with the changed IP address. What I also saw was that the sslHostname parameter in registerSentinel(..) points to the correct hostname, which means that the hostname exists at least at the point of registration.
Does this information help you, @mrniko? Can I provide you more information? I'm happy to help to get this fixed quickly!

I'm still debugging. In the above examples we set the sentinelsDiscovery property to false because we had the same issue we found in #3681.
Now for the sake of testing I changed that property to true and now I'm really lost because the SentinelConnectionManager now correctly updates the sentinels set after a restart of Redis. I'm not sure how it's intended but the disconnectedSentinels do not contain any entries. What I do not understand though is that despite the list being correct I see various errors in the application logs. In the following exception message it lists all current and previous IPs as disconnected:
org.redisson.client.RedisConnectionException: SlaveConnectionPool no available Redis entries. Master entry host: <IP_ADDRESS>/<IP_ADDRESS>:6379 Disconnected hosts: [<IP_ADDRESS>/<IP_ADDRESS>:6379, <IP_ADDRESS>/<IP_ADDRESS>:6379, <IP_ADDRESS>/<IP_ADDRESS>:6379, <IP_ADDRESS>/<IP_ADDRESS>:6379, <IP_ADDRESS>/<IP_ADDRESS>:6379]
	at org.redisson.connection.pool.ConnectionPool.get(ConnectionPool.java:207)
	at org.redisson.connection.pool.SlaveConnectionPool.get(SlaveConnectionPool.java:30)
	at org.redisson.connection.balancer.LoadBalancerManager.nextConnection(LoadBalancerManager.java:315)
	at org.redisson.connection.MasterSlaveEntry.connectionReadOp(MasterSlaveEntry.java:555)
	at org.redisson.connection.MasterSlaveConnectionManager.connectionReadOp(MasterSlaveConnectionManager.java:556)
	at org.redisson.command.RedisExecutor.getConnection(RedisExecutor.java:641)
	at org.redisson.command.RedisExecutor.execute(RedisExecutor.java:124)
	at org.redisson.command.RedisExecutor$1.run(RedisExecutor.java:298)
	at io.netty.util.HashedWheelTimer$HashedWheelTimeout.run(HashedWheelTimer.java:715)
	at io.netty.util.concurrent.ImmediateExecutor.execute(ImmediateExecutor.java:34)
	at io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:703)
	at io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:790)
	at io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:503)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.base/java.lang.Thread.run(Thread.java:829)

I also see the following exceptions (maybe it helps):
2022-08-02 15:40:31.091 ERROR 39515 --- [isson-netty-2-2] o.r.c.SentinelConnectionManager          : Unable to resolve redis-node-1.redis-headless.sophora-5.svc.cluster.local

io.netty.resolver.dns.DnsResolveContext$SearchDomainUnknownHostException: Failed to resolve 'redis-node-1.redis-headless.sophora-5.svc.cluster.local' and search domain query for configured domains failed as well: [mycompany.com]
	at io.netty.resolver.dns.DnsResolveContext.finishResolve(DnsResolveContext.java:1047)
	at io.netty.resolver.dns.DnsResolveContext.tryToFinishResolve(DnsResolveContext.java:1000)
	at io.netty.resolver.dns.DnsResolveContext.query(DnsResolveContext.java:418)
	at io.netty.resolver.dns.DnsResolveContext.access$600(DnsResolveContext.java:66)
	at io.netty.resolver.dns.DnsResolveContext$2.operationComplete(DnsResolveContext.java:467)
	at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:578)
	at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:571)
	at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:550)
	at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:491)
	at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:616)
	at io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:609)
	at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:117)
	at io.netty.resolver.dns.DnsQueryContext.tryFailure(DnsQueryContext.java:240)
	at io.netty.resolver.dns.DnsQueryContext$4.run(DnsQueryContext.java:192)
	at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
	at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)
	at io.netty.util.concurrent.AbstractEventExecutor.runTask$$$capture(AbstractEventExecutor.java:174)
	at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java)
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute$$$capture(AbstractEventExecutor.java:167)
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java)
	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:503)
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:995)
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: io.netty.resolver.dns.DnsNameResolverTimeoutException: [/<IP_ADDRESS>:54022] query via UDP timed out after 5000 milliseconds (no stack trace available)

(I saw the above exception for more than this Redis node)
2022-08-02 15:40:35.797 ERROR 39515 --- [sson-netty-2-24] o.r.c.balancer.LoadBalancerManager       : Unable to unfreeze entry: [freeSubscribeConnectionsAmount=1, freeSubscribeConnectionsCounter=value:50:queue:0, freeConnectionsAmount=12, freeConnectionsCounter=value:64:queue:0, freezeReason=MANAGER, client=[addr=redis://<IP_ADDRESS>:6379], nodeType=SLAVE, firstFail=1659447635796]

java.util.concurrent.CompletionException: org.redisson.client.RedisConnectionException: Unable to init enough connections amount! Only 12 of 24 were initialized. Redis server: <IP_ADDRESS>/<IP_ADDRESS>:6379
	at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331)
	at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:346)
	at java.base/java.util.concurrent.CompletableFuture$BiRelay.tryFire(CompletableFuture.java:1423)
	at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
	at java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
	at org.redisson.connection.pool.ConnectionPool.lambda$createConnection$1(ConnectionPool.java:151)
	at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
	at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
	at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
	at java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
	at org.redisson.connection.pool.ConnectionPool.promiseFailure(ConnectionPool.java:307)
	at org.redisson.connection.pool.ConnectionPool.lambda$createConnection$6(ConnectionPool.java:273)
	at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
	at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
	at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
	at java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
	at org.redisson.client.RedisClient$1$1.run(RedisClient.java:226)
	at io.netty.util.concurrent.AbstractEventExecutor.runTask$$$capture(AbstractEventExecutor.java:174)
	at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java)
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute$$$capture(AbstractEventExecutor.java:167)
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java)
	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:503)
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:995)
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: org.redisson.client.RedisConnectionException: Unable to init enough connections amount! Only 12 of 24 were initialized. Redis server: <IP_ADDRESS>/<IP_ADDRESS>:6379
	at org.redisson.connection.pool.ConnectionPool.lambda$createConnection$1(ConnectionPool.java:150)
	... 21 common frames omitted
Caused by: java.util.concurrent.CompletionException: org.redisson.client.RedisTimeoutException: Command execution timeout for command: (AUTH), params: (password masked), Redis client: [addr=redis://<IP_ADDRESS>:6379]
	at java.base/java.util.concurrent.CompletableFuture.encodeRelay(CompletableFuture.java:367)
	at java.base/java.util.concurrent.CompletableFuture.completeRelay(CompletableFuture.java:376)
	at java.base/java.util.concurrent.CompletableFuture$UniRelay.tryFire(CompletableFuture.java:1019)
	... 13 common frames omitted
Caused by: org.redisson.client.RedisTimeoutException: Command execution timeout for command: (AUTH), params: (password masked), Redis client: [addr=redis://<IP_ADDRESS>:6379]
	at org.redisson.client.RedisConnection.lambda$async$0(RedisConnection.java:244)
	at io.netty.util.HashedWheelTimer$HashedWheelTimeout.run(HashedWheelTimer.java:715)
	at io.netty.util.concurrent.ImmediateExecutor.execute(ImmediateExecutor.java:34)
	at io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:703)
	at io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:790)
	at io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:503)
	... 2 common frames omitted

(I saw the above exception for more than this Redis node and also for the master node)

Facing the same issue @mrniko. We have 2 node setup with 1 master, 1 slave and 3 sentinels. When the master node is down, the slave became the new master, but the app shows the below logs. After the app restart, its working fine.
Caused by: org.redisson.client.RedisConnectionException: SlaveConnectionPool no available Redis entries. Master entry host: /<IP_ADDRESS>:6379 Disconnected hosts: [redis-service-0.test.svc.cluster.local/<IP_ADDRESS>:6379, redis-service-1.test.svc.cluster.local/<IP_ADDRESS>:6379]
at org.redisson.connection.pool.ConnectionPool.get(ConnectionPool.java:217) ~[redisson-3.15.5.jar:3.15.5]
at org.redisson.connection.pool.SlaveConnectionPool.get(SlaveConnectionPool.java:30) ~[redisson-3.15.5.jar:3.15.5]
at org.redisson.connection.balancer.LoadBalancerManager.nextConnection(LoadBalancerManager.java:277) ~[redisson-3.15.5.jar:3.15.5]
at org.redisson.connection.MasterSlaveEntry.connectionReadOp(MasterSlaveEntry.java:499) ~[redisson-3.15.5.jar:3.15.5]
at org.redisson.connection.MasterSlaveConnectionManager.connectionReadOp(MasterSlaveConnectionManager.java:553) ~[redisson-3.15.5.jar:3.15.5]
at org.redisson.command.RedisExecutor.getConnection(RedisExecutor.java:532) ~[redisson-3.15.5.jar:3.15.5]
at org.redisson.command.RedisExecutor.execute(RedisExecutor.java:121) ~[redisson-3.15.5.jar:3.15.5]
at org.redisson.command.RedisExecutor$2.run(RedisExecutor.java:251) ~[redisson-3.15.5.jar:3.15.5]
at io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:672) ~[netty-common-4.1.63.Final.jar:4.1.63.Final]
at io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:747) ~[netty-common-4.1.63.Final.jar:4.1.63.Final]
at io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:472) ~[netty-common-4.1.63.Final.jar:4.1.63.Final]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.63.Final.jar:4.1.63.Final]
... 1 more

@ramprasad1996 please provide Redisson logs in trace logging level

@philmtd "SlaveConnectionPool no available Redis entries" error resolved in 3.17.6. Unable to init enough connections amount! Only 12 of 24 were initialized. Try to set 12 maxIdleConnections setting

@mrniko Provided a workaround by setting the Read mode as MASTER from MASTER_SLAVE


opentelemetry tracer: Not crash envoy when environment resource detector can't detect attributes

Commit Message: Not crash envoy when env resource detector can't detect attributes
Additional Description:
Risk Level: Low
Testing: Unit/Integration/Manual
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: N/A
[Optional Runtime guard:]
[Optional Fixes #32225]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

CC @wbpcode

/retest

/wait add warning log


The main trio: C#, F# and Visual Basic

Issue tracking new topic at http://dotnet.github.io/docs/languages/main-trio.html

This is supposed to be an short, very short overview of languages on .NET, the main languages.


Windows setup

enabling deployment on windows

Thanks for the PR! I hope you don't mind if I squash it and reword the commit message slighly.


Add new liquid-c headline benchmark

This is a suggestion from Jimmy Miller. According to him, YJIT makes Liquid-C quite a bit faster, giving an extra boost above vanilla Liquid. That makes it worthwhile to track the performance of liquid-c, which will likely behave differently from vanilla liquid.

This can be closed, it was added in https://github.com/Shopify/yjit-bench/pull/170


How can we set timeout for a HTTP request?

Is it possible to set timeout for the request or for all requests in uWebSockets.js?

Got it, thanks. I knew about this solution but wanted to know if something else was possible. Because in this case, the asyncTask will keep running even if close the request.


Sprig with Smart Map

Question
Craft <IP_ADDRESS>
Sprig 1.3.0
Smartmap 3.3.5
I'm attempting to sprigify a page with entry pagination and a google map powered by smart maps.
Pagination and form filtering are working fine with the entries listed on the page. However when clicking through pagination or filtering the map goes blank.

I've place the sprig attribute in the div wrapping wher ehte smartmap code goes but that doesn't seem to be helping.
see code:
{# Map #}
<div class="relative flex-100 md:mt-header mapped" sprig>

  {# more code here #}

  {# {% set locations = craft.entries.section('projects').all() %} #}
  {% set locations = entryQuery.all() %}
  {{ craft.smartMap.map(locations, options) }}

  {% include 'maps/_map-styles' %}

</div>
{# end map #}

Do I need to add the sprig attribute to the smartmap.map tag? There doesn't appear to be an option to add attributes https://plugins.doublesecretagency.com/smart-map/customizing-the-map-in-twig/#map-options
Additional context
Add any other context or screenshots about the support request here.

My guess is that Smart Map outputs some JavaScript files when craft.smartMap.map is called. Given that this template is re-rendered and the result loaded over AJAX, you need to account for the fact that browsers will block scripts that exist in the returned value as a security precaution.
Instead, you'd need to find a way to re-instantiate Smart Map after re-rendering, for example:
<script>
   htmx.on('htmx:afterSwap', function(event) {
       // Re-instantiate Smart Map
   });
</script>

Perhaps @lindseydiloreto can be of assistance?

My guess is that Smart Map outputs some JavaScript files when craft.smartMap.map is called. Given that this template is re-rendered and the result loaded over AJAX, you need to account for the fact that browsers will block scripts that exist in the returned value as a security precaution.
Instead, you'd need to find a way to re-instantiate Smart Map after re-rendering, for example:
<script>
   htmx.on('htmx:afterSwap', function(event) {
       // Re-instantiate Smart Map
   });
</script>

Perhaps @lindseydiloreto can be of assistance?

I tried this:
<script>
   htmx.on('htmx:afterSwap', function(event) {
       smartMap.refreshMap('main-map1');
   });
</script>

but it didn't work. Will hit up Lindsey and when I get a solution update this thread for future reference.

I tried this:
<script>
   htmx.on('htmx:afterSwap', function(event) {
       smartMap.refreshMap('main-map1');
   });
</script>

but it didn't work. Will hit up Lindsey and when I get a solution update this thread for future reference.

Did a little experimenting with an upcoming beta, and it looks like everything is working smoothly! I chatted with @CreateSean  via DM, I think we've got everything working as intended.
Thanks @bencroker, feel free to close this thread! 🍺

Did a little experimenting with an upcoming beta, and it looks like everything is working smoothly! I chatted with @CreateSean  via DM, I think we've got everything working as intended.
Thanks @bencroker, feel free to close this thread! 🍺

Thank you @lindseydiloreto!

Thank you @lindseydiloreto!

Did a little experimenting with an upcoming beta, and it looks like everything is working smoothly! I chatted with @CreateSean via DM, I think we've got everything working as intended.
Thanks @bencroker, feel free to close this thread! 🍺

What was the solution? I'm having the same issue.

@ConversioniaDev The solution relies on an upcoming beta version of Smart Map. If you'd like a copy of the beta, feel free to DM me on Discord (or email support@doublesecretagency.com).
Alternatively, you could just wait about 2 weeks for me to release it publicly. 😉


Remove version: FengHe.FocusNote version 2.15.2-671

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://download.kirakuapp.com/FN_PC/Focus Note Setup 2.15.2-671.exe
Response Error: The remote server returned an error: (403) Forbidden.
(Automated message - build 912)


Added recursive call to getRecord for paged results

When there are > 30 records on a domain, the results of the /domains/DOMAIN/records call will be paged. I added a recursive call to the getRecord function which passes in a page number. In the event that the record wasn't found and there is found.
I'm unsure if results for API v1 are paged, I only made this change to the v2 version.

@nickwest Good catch, thanks for the update! I'm not going to bother updating V1 for now as I suspect most people will be using V2...


Implement missing encodings

This is a master list for important missing encodings. What is considered "important" is a delicate question, but for now I have the following list:

WHATWG multibyte encodings

[x] gbk
[x] gb18030
[x] hz-gb-2312
[x] big5
[x] iso-2022-jp
[x] utf-16be
[x] utf-16le

Non-WHATWG multibyte encodings of the special interest

[ ] JIS X 0213 encodings: euc-jis-2004, iso-2022-jp-2004, shift-jis-2004
[ ] Other encodings based on Shift_JIS (WHATWG's shift_jis is actually windows-31j)
[ ] cesu-8, required for compatibility

Required for completeness

[x] iso-8859-1 (compare with windows-1252)
[ ] euc-kr (compare with windows-949)
[ ] euc-jp with and without JIS X 0212 compatibility (WHATWG's euc-jp is asymmetric: it encodes without 0212 and decodes with 0212)
[ ] utf-32 and friends
[ ] utf-7?

Do you have any interest in supporting EBCDIC encodings, maybe behind a feature since they are not the most commonly used? I know that Java provides a built-in support for a limited set, iconv and icu offer more extended support.
If so, I could provide help, for example by providing tables with similar syntax as https://encoding.spec.whatwg.org/index-iso-8859-15.txt

Would you be willing to consider supporting IBM code page 437? (The original DOS/IBM PC codepage)
So far, the only Rust support I've been able to find is a read-only crate named cp437 which doesn't inspire confidence. (The heading correctly says "cp437", but then it's typo'd as "cp537" in the very first non-heading line of the README and there's no unit test badge.)
I ask because I have a Python script for generating batch file menus for DOSBox and my retro PC (which means I need to encode box-drawing characters to cp437) and it'd be nice if I could port them to Rust to get more compile-time correctness enforcement and easier distribution to others.


Wrong encoding?

Hi,
When I have a "content: '\e003';" in scss the file gets converted to "content: "î€ƒ";" instead of keeping the "\e003" ascii value.
This is using the CompileFile function.
KR
MK

have a scss file of...
@import 'mixin';
a {
@include pseudoFontIcon('\e003');
}
with a mixin defined as ...
@mixin pseudoFontIcon($content) {
content: $content;
}
outputs a css of...
@charset "UTF-8";
a {
content: "î€ƒ";
}

@geniuscodemonkey Thanks for the report, will look into it as it might be libsass bug and not libsass-net related.
Will let you know as soon as possible

Hi I suffer for same problem. Some testing:
.myClass {
content: "\f000";
}
-> "\f000" //Right
$my-variable: "\f000";
.myClass {
content: $my-variable;
}
-> "ï€ƒ"
And on both way if using actual utf-8 character its also leads to "ï€ƒ". In my case its fine to get eather ascii representation \f000 or actual utf character .

The sassc command-line tool from native C/C++ libsass is having the same encoding issue.
https://github.com/sass/libsass/issues/1235 looks into this...

I think it's the same issue with the CompileFile function, but I can repro it with this:
content: "✔";

which generates this:
content: "âœ”";

I don't think it's a libsass issue since this issue doesn't seem to repro in the node module. Perhaps the CompileFile function should take a System.Text.Encoding parameter?

I found that libsass-net can't handle Unicode characters well.  Is it a issue from libsass?

Is there a work around for this issue? Right now font-awesome or bootstrap are not even usable, it's all a encoding mess.

Sorry, I couldn't find a work around for this;  but I didn't look to closely at the GitHub code.
I ended up using another library (I can't remember what it was though and I don't have the code handy anymore)
Sent from my Samsung Galaxy smartphone.
-------- Original message --------
From: Roger Versluis<EMAIL_ADDRESS>Date:26/11/2015  18:10  (GMT+00:00)
To: darrenkopp/libsass-net<EMAIL_ADDRESS>Cc: geniuscodemonkey<EMAIL_ADDRESS>Subject: Re: [libsass-net] Wrong encoding? (#24)
Is there a work around for this issue? Right now font-awesome or bootstrap are not even usable, it's all a encoding mess.
—
Reply to this email directly or view it on GitHub.

The spec test https://github.com/sass/sass-spec/tree/master/spec/libsass-closed-issues/issue_1231 (for sass/libsass#1231) is passing with LibSass.NET master, so this should be fixed with the upcoming release.
test.scss
@mixin pseudoFontIcon($content) {
    content: $content;
}
a:before {
  @include pseudoFontIcon('\e003');
}

C# code:
var options = new SassOptions
{
    InputPath = "path\\to\\my-test.scss"
   // Note: here if we add another option:
   //
   // OutputStyle = OutputStyle.Compressed
   //
   // compiler will not produce @charset "UTF-8"; statement in
   // the output but instead use the byte-order-mark (BOM). This
   // is totally fine, because either way browser will show the
   // right thing.
};

var sass = new SassCompiler(options);
var result = sass.Compile();

File.WriteAllText("path/to/styles.css", result.Output); // IO writes are now handled by consumer
                      // (probably later in a separate extension package: LibSass.NET.Extensions)
                       // either way no encoding is necessary to be passed to WriteAllText method

Do  - verify the styles.css in browser.
Don't - rely on the visibility in text editor.
.. because the rendered Unicode chars are different than \e escaped ones. If (for some unrelated reason) we do want that the compiler must produce the visible \e003, it is possible by using quoted interpolation (like happening in aforementioned spec fixture):
@mixin pseudoFontIcon($content) {
    content: #{"\""+$content+"\""};
}
a:before {
  @include pseudoFontIcon(\e003); // without single/double quotes here
}

The important thing is, while both outputs looks different in text editor, they produce same effect when rendered by the browser.

Since it's fixed, i'm closing the issue.


APT whitelist request for libsdl-mixer1.2-dev

on ubuntu-precise.

Closing in favor of travis-ci/apt-package-whitelist#715


Overflow bug when running tf.keras.layers.ZeroPadding2D

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
No
Source
binary
TensorFlow version
2.13.0
Custom code
Yes
OS platform and distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
Due to large list element
Standalone code to reproduce the issue
import tensorflow as tf
import os
import numpy as np
try:
  padding_0_0 =<PHONE_NUMBER>51
  padding_0_1 = False
  padding_0 = [padding_0_0,padding_0_1,]
  padding_1_0 =<PHONE_NUMBER>51
  padding_1_1 =<PHONE_NUMBER>51
  padding_1 = [padding_1_0,padding_1_1,]
  padding = [padding_0,padding_1,]
  arg_class = tf.keras.layers.ZeroPadding2D(padding=padding,)
  arg_input_0_tensor = tf.random.uniform([3, 300, 300, 192], dtype=tf.float32)
  arg_input_0 = tf.identity(arg_input_0_tensor)
  arg_input = [arg_input_0,]
  out = arg_class(*arg_input)
except Exception as e:
  print("Error:"+str(e))

### Relevant log output

```shell
['{{function_node __wrapped__Pad_device_/job:localhost/replica:0/task:0/device:GPU:0}} Encountered overflow when multiplying<PHONE_NUMBER>529 with<PHONE_NUMBER>530, result: -1\n', '\t [[{{node Pad}}]] [Op:Pad]\n', '\n', "Call arguments received by layer 'zero_padding2d' (type ZeroPadding2D):\n", ' • inputs=tf.Tensor(shape=(1, 1, 2, 2), dtype=float32)\n']

Not an issue, that's an error that is being returned to the user instead of performing bad computations.
Please consult again the SECURITY.md guide, please don't spam with low quality issues.


Can't find pv_wslink.py in paraview.web in Paraview 5.4  macOS version

node_modules/pvw-visualizer/server/pvw-visualizer.py", line 85, in <module>
    from paraview.web import pv_wslink
ImportError: cannot import name pv_wslink

So where should I get those files? Install an old version?

ws_link was introduced in Visualizer 2.3 which would only work with ParaView/master.
You can refer to the compatibility table here or on the main README.


Cannot run with an ia64 CPU

I try to run an OS with an ia64 dual-core CPU, but UTM crashed.
When I start the VM, UTM quits and back to Home Page of iPadOS.
But it's normal when I use an x86_64 dual_core CPU.
Configuration (required)

UTM Version: UTM-TCI
OS Version: iPadOS 14.5
Device Model: iPad mini 5 white with WLAN, 256GB
no any jailbrokens
How did you install UTM?
AltStore on iPad

IA64 is not a supported architecture. You can try x86 or x86_64 (amd64)

IA64 is not a supported architecture. You can try x86 or x86_64 (amd64)

So how about making ia64 CPU supported?


data is possibly null

after handling the error and we are sure that the data is not null anymore, typescript cannot detect this and considers the data nullable. ts is still thinking about [null, error]
I was curious if it could be fixed though it is a typescript limit
const fetchData = () => Promise.resolve({id: 1})
const [data, error] = await trytm(fetchData())
if (error) {
  return
}

data.id // data is possibly null

maybe by changing this line with adding a bang
return [null!, error] as const

maybe by changing this line with adding a bang
return [null!, error] as const

Tried it but the behavior is still the same.
I'll focus on other projects for now but might revisit this at some point. Feel free to open a PR if you find a solution.

Since anything can be thrown, it's probably a good idea to check whether error is actually an instance of Error.
Frameworks like Remix allows for throwing of responses and this could avoid break such functionality.


dts: xtensa: intel_adsp_ace15/ace20/tgph: correct SSP definition

Fix the SSP definitions for multiple adsp platforms.

@kv2019i  What about the cavs25.dtsi file? Shouldn't it also be changed?

@dnikodem the cavs25/tgp definition is actually correct, it has 6 SSP instances. the tgph variant has 3.


Pierogii.eateof 6932a 948598d3 7d04 418e bf82 d6b477fc9af5

Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Manual Validation ended with:

##[error] Manifest Error: Schema Error. [Schema validation failed.
Error context: [Installers][0][NestedInstallerFiles][1] Description: Missing required property 'RelativeFilePath'.
Error context: [Installers][0][NestedInstallerFiles] Description: Failed to validate item #1 in array. Error context: [Installers][0] Description: Failed to validate against schema associated with property name 'NestedInstallerFiles'.
Error context: [Installers] Description: Failed to validate item #0 in array.
Error context:  Description: Failed to validate against schema associated with property name 'Installers'. ] File: pierogii.EATEOF.installer.yaml
Manifest Error: Required field missing. [RelativeFilePath]

Hi @@upintheairsheep,,
It seems the NestedInstallerFiles key is missing.


xiwi cannot start

Firstly I installed the arch using command "sudo sh -e installer/main.sh -r arch -t xiwi"
then I installed crouton integration extension on my chromebook, when I finished installation I tried to start xiwi but no starting script in /usr/local/bin/, so I ran 'sudo /usr/local/bin/enter-chroot' then I ran 'xinit'.  crouton integration extension tried to connect to arch but Chrome extension shows this error message.
ERROR: Connection failed (code: -2).
Disconnected, please close the window.
Please help me, Thanks!

Looks like the most recent Chrome update did this to a some folks.  I WAS running very nicely w lxqt, yaourt (to fetch and build it) et al, and had this stable, reliable setup for nigh a year, then SPLAT, the DOWNgrade to v 44.0.2403 fuktover my lovely chroagh bigtime.    First, lxqt wouldn't connect to Xephyr, so I twiddled and tweaked in /etc/crouton to no avail, saw the stuff on this new extension which X clients now are supposed to connect to, wiped my trusty old chroot, got the latest chroagh, noted that yes, it runs boring old XFCE as advertized, but for OTHER window managers or desktops.?.... NADA!!    Will maybe post some details if I find any cause for hope in this wiki....

yup my chrome got updated and now my arch awesome wm just went splat.

No hope yet either.  I got boring old XFCE going after deleting my lovely lxqt env, and updating chroagh/crouton, but this new xiwi extension SHIT doesn't begin to make up for the loss.  I have updated my Slackware sdcard, and it runs OK, though slow, being constrained by the card.  Will likely go ahead and just burn all ChromeOS off the eMMC next week.  Google has shown its hand very clearly now.

here is a possible fix, I am currently trying this right now. I will update as soon as I see some progress.
https://github.com/dnschneid/crouton/pull/1973

here is the fix:
(the only option as of now is to downgrade your chromeos version)
instructions:
Downgrading chromeos and then re-installing worked.
Here's a link:
http://www.chromestory.com/2014/11/chromebooks-get-options-downgrade-operating-system/
Also, you can prevent chromeos auto updates as described here:
https://productforums.google.com/forum/#!topic/chromebook-central/KZoIpuuYHeo
(see last comment)

Hmm, yeah, I DID consider downgrading ChromeOS.  Its a workaround.  Thanks bro.  Happy hacking!  Think I'll go for ArnoldtheBat's ARM build if I flash on any more Chrome(ium) OSes.  More likely, will Slack it.  XFCE works OK w xiwi for this week anyway...


Request: Enable intel-xe-kmd for mesa

Enable intel-xe-kmd for mesa
Hey it would be great if the intel xe kernel module support could be enabled for mesa.
Normally I would just override the derivation but sadly my computer is not powerful enough
to rebuild all of the dependent packages (nameley webkit and chromium) in a reasonable amount
of time (my RAM and SWAP completely fills up).
I haven't investigated it any further but I believe adding "-Dintel-xe-kmd=enabled" to meson flags should do the trick.
Metadata

source URL: https://gitlab.freedesktop.org/mesa/mesa
platforms: linux

Add a :+1: reaction to issues you find important.

Shouldn't be necessary one this commit hits the next release. I don't see it in 24.0.3 so I assume it'll be in 24.0.4

Looks like that won't be in 24.0, it's only in main so it'll be in 24.1

Changing the flag doesn't change any ABI so a rebuild isn't forced.
Try overriding hardware.opengl.package with mesa with this option and rebooting.

Ah I overlayed mesa before didnt have in mind that it has a .package option. Thanks will try that

24.0.4 is now released, I'm just about to open a ticket to request it be updated

Oh, nvm, it's already been updated, just hasn't landed in unstable yet

Hi, it didn't get merged in time for mesa 24.0.4, but it is in 24.0.5 which released two days ago.

Mesa 24.05 is now in unstable, and you can enable the xe driver using modprobe like I have.

For context, mesa was updated  by a direct commit, without a pr, to 24.0.5. (why Idk??)

Given this is fixed in 24.0.5, I don't see a reason why this issue should remain open

For context, mesa was updated by a direct commit, without a pr, to 24.0.5. (why Idk??)

FWIW it came via GH-301941 to staging-next, then via GH-303527 (including that commit you referenced) to master.


NPE in FileSystemInfo

Bug report

What is the current behavior?
Null pointer error in FileSystemInfo.getContextTimestamp
If the current behavior is a bug, please provide the steps to reproduce.
Call FileSystemInfo.getContextTimestamp with an immutable path (immutable path prefixes are provided in FileSystemInfo constructor).

What is the expected behavior?
_readContextTimestamp (processor for contextTimestampQueue) returns null for immutable paths:
https://github.com/webpack/webpack/blob/bd7cb37f1c0d872cfff9fc27c7db52a25e1ba6a3/lib/FileSystemInfo.js#L3016-L3020
so the queue callback in getContextTimestamp should handle entry possibly being null: https://github.com/webpack/webpack/blob/bd7cb37f1c0d872cfff9fc27c7db52a25e1ba6a3/lib/FileSystemInfo.js#L1164-L1168

Other relevant information:
webpack version:  5.51.0
Node.js version: all
Operating System: all
Additional tools: N/A

Related: https://github.com/webpack/webpack/pull/14019

What is Null pointer? It is not Java

What is Null pointer? It is not Java

True, JavaScript has "nullable types" instead of "null pointers", and typeof null === "object", so technically I should say "null object error" or "error due to null object". But perhaps enough nitpicking, let's focus on the fact that callback receives null and doesn't handle it.

I have also this problem
FileSystemInfo.js:816
if (entry.resolved !== undefined) return entry.resolved;
^
TypeError: Cannot read property 'resolved' of null
This looks like a recent webpack update. (use webpack as a transitive dependency in my Node project).

This looks like a recent webpack update. (use webpack as a transitive dependency in my Node project).

It appeared in 5.51.0, so just downgrade to 5.50.0

Yep that is a bug. Could one of you give me a stack trace of that?

Yep that is a bug. Could one of you give me a stack trace of that?

TypeError: Cannot read property 'resolved' of null
    at getResolvedTimestamp (node_modules/webpack/lib/FileSystemInfo.js:816:12)
    at node_modules/webpack/lib/FileSystemInfo.js:1165:21
    at node_modules/webpack/lib/util/AsyncQueue.js:352:5
    at Hook.eval [as callAsync] (eval at create (node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (node_modules/tapable/lib/Hook.js:18:14)
    at AsyncQueue._handleResult (node_modules/webpack/lib/util/AsyncQueue.js:322:21)
    at node_modules/webpack/lib/util/AsyncQueue.js:305:11
    at node_modules/webpack/lib/FileSystemInfo.js:3100:5
    at Array.<anonymous> (node_modules/webpack/lib/FileSystemInfo.js:2960:13)
    at runCallbacks (node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:27:15)


[Website update] Make our RSS feed more obvious

Is your feature request related to a problem? Please describe.
While the community can pick up an RSS feed from https://opensearch.org/feed.xml - we need to make this easier to find
Describe the solution you'd like
Add icon/link for the blog RSS feed for our community

Hello! Would love to help out with this issue if nobody has tackled this yet.


Remove first_round from rules files

After #1132, consent will always be shown via the consent field tied to the Experiment parent.
Calling the endpoint block/{id} will do the following:

check the participant
start a session with the current / new participant and the current block, and return its id to the frontend

After that, the block will be handled through the session/{id}/next_round endpoint
Steps:
Backend

[ ] remove Consent actions from all first_round methods
[ ] move Playlist views to next_round (only for those rules where it's conceivable we may have multiple playlists tied to them)
[ ] move every Explainer to next_round
[ ] remove first_round methods
[ ] migrate existing Consent forms to Experiment level if applicable

Frontend

[ ] remove Consent as an option from Block

After #1132, consent will always be shown via the consent field tied to the Experiment parent.

I mean... technically the field is there, but do we have functionality that also checks if the participant has accepted the consent form before starting the experiment / block and shows the consent form if that's not the case? If not, perhaps we should make that before doing this refactor. 🤔


How to get the pre-trained model？

While executing the run_train.sh the parameter --pretrained_model_name=vqr_pretrained_model.bin --model_name=vqr_fine_tuned_model.bin, which means the pretrained model name.  However, I can not find the model or any description of the model in your repository. Could you please tell me how to download this model please

While executing the run_train.sh the parameter --pretrained_model_name=vqr_pretrained_model.bin --model_name=vqr_fine_tuned_model.bin, which means the pretrained model name. However, I can not find the model or any description of the model in your repository. Could you please tell me how to download this model please

Do you succeed finally, I can't reproduce the experiment results if I train from codebert and codet5 without the pretrained model

After executing download_model.sh, it seems to download a pre-trained model, but with a different name than the one given, you can try it. I ran it about 6 months ago but I don't remember now, I can go back and try it then share it if needed.

After executing download_model.sh, it seems to download a pre-trained model, but with a different name than the one given, you can try it. I ran it about 6 months ago but I don't remember now, I can go back and try it then share it if needed.

I used the 'loc_fine_tuned_model', and train the 'vqr_model' by myself, but I can't get the correct rate of 33.21% in the paper ,I tried to change parameters but I can not get any result better than 29%. Can you provide some detailed parameters like weight_decay, random seed. Appreciate for any help you can provide!

I was also unable to achieve the results mentioned in the paper, I achieved even worse results, barely less than 20%, I'm not quite sure what the reason for this is, but in my paper I used my reproduced results with some explanations.


scrutiny: 0.8.0 -> 0.8.1

Also driveby to add the changelog attribute to meta
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

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

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

Result of nixpkgs-review pr 303293 run on x86_64-linux 1

1 package built:

scrutiny

@katexochen FYI, would've been good to have borgo run the nixos tests just as a best practice

Didn't know you also tested, since it wasn't mentioned in your comment. But either way works I think.

Ya, should have mentioned that in the comment, too (but nix run .#nixosTests.* doesn't provide such a nice report.md you can copy afterwards :see_no_evil: )


Create sub-commands using a commander for cli interactions

Display usage:
opwire-agent help

Display version:
opwire-agent version

Run service:
opwire-agent serve

Finish in b2fed0e7b8f42d471097d554b770b42368fd9c4a

Finish @ b2fed0e7b8f42d471097d554b770b42368fd9c4a


Blank page on new publish instance

Hi, I installed v1.6.12 on an author instance a couple of months ago, got it up and working, got it working on a publish instance at the time. Then had other priorities get in the way of moving the project along. Now in order to get all the setup steps documented, I'm trying to get it working on a completely fresh, brand new publish instance (AEM v6.4). I'm using the same author instance it was originally installed on. What I'm doing is just publishing all pages in the site to the publish instance and all I get is a blank white page. Any idea what I'm doing wrong or setup I'm missing and have long since forgotten?

Hi @jorgenson112358, you will also need the code base (ui.apps, core) installed on the publish instance. An easy way is to replicate the packages from your author instance (or re-upload them on the publish side)

You will also need the templates/policies published as well, but that might happen automatically via the Sites UI when you publish the pages...

My brain was not thinking of straightforward simple solutions. It jumped right into which config, which rule, which toggle did I not set. Thanks for the quick reply!


Updates to allow running the tests on a very large number of profiles…

… without running out of memory. Also a couple of changes to make the EN_spike_and_step_check more robust and to improve the output from the benchmarking code.
Results from the 150 profile test dataset available in the repository are the same as before. Results when running on the full test dataset are:
155794 profiles will be read
7 quality control checks will be applied:
Argo_global_range_check
Argo_gradient_test
Argo_pressure_increasing_test
Argo_spike_test
EN_range_check
EN_spike_and_step_check
WOD_gradient_check
Number of profiles tested was 155787
Number of profiles that failed Argo_global_range_check was 2560
Number of profiles that failed Argo_gradient_test was 4331
Number of profiles that failed Argo_pressure_increasing_test was 7514
Number of profiles that failed Argo_spike_test was 1031
Number of profiles that failed EN_range_check was 2351
Number of profiles that failed EN_spike_and_step_check was 7198
Number of profiles that failed WOD_gradient_check was 8201
Number of profiles that should have been failed was 18174
Previously the code would not run on this number of profiles without running out of memory.

I'd like to find a way to make the full dataset available for reproduction of these results; there are a number of technical options, but are there any copyright or privacy protections preventing distribution of the dataset?


Bad value for type int :<PHONE_NUMBER>

Is this a bug report?
yes
Environment
java -version
openjdk version "1.8.0_222"
OpenJDK Runtime Environment (build 1.8.0_222-8u222-b10-1ubuntu1~16.04.1-b10)
OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode)
Then, specify:

Operating system: Ubuntu 16/18
Browser and version (if relevant): not relevant
Saiku plugin to Pentaho or Saiku Standalone: Saiku Standalone
Saiku CE or Saiku EE: Saiku CE
Saiku version: 3.15 same on saiku-latest

Steps to Reproduce
generate over 2 149 310 316  row counts in facts table
Expected Behavior
initial select  count(*) from a fact table  return the result for cardinality
Actual Behavior
cubes are not initialized

and in logs
2019-10-21 04:30:20,914 ERROR [org.saiku.web.core.SecurityAwareConnectionManager] Error connecting: prod
mondrian.olap.MondrianException: Mondrian Error:Internal error: Reading row count from table [null, olap, facts]; sql=[select count(*) from "olap"."facts"]
....
Caused by: org.postgresql.util.PSQLException: Bad value for type int :<PHONE_NUMBER>
fact tables are partition by int field if it's mater

hi is there any updates?
for now, as i understand it's a limitation of Mondrian engine and it also presents in EE edition
upgrade to EE will not resolve my issue
the only way to fix is cut my data as I did it  earlier