Forward+ incompatibility issues with new AMD GPU driver(s)

Tested versions

Reproducible in: 4.2.1

System information
Windows 10 - Godot 4.2.1.stable - Forward+ - Vulkan - AMD RX 7800XT
Issue description

Full driver versions:
GPU - AMD Radeon RX 7800 XT - Primary/Discrete
VRAM - 16368 MB - GDDR6 2438 MHz
Driver Version - 23.40.02-240111a-399551C-AMD-Software-Adrenalin-Edition
AMD Windows Driver Version - 31.0.24002.92
Direct3D API Version - 12.1
Vulkan™ API Version - 1.3.270
OpenCL™ API Version - 2.0
OpenGL® API Version - 4.6
Direct3D® Driver Version - <IP_ADDRESS>0
Vulkan™ Driver Version - 2.0.294
OpenCL® Driver Version - 31.0.24002.92
OpenGL® Driver Version - 24.01.231107_282afec
2D Driver Version - <IP_ADDRESS>4
2D Driver File Path - /REGISTRY/MACHINE/SYSTEM/CurrentControlSet/Control/Class/{4d36e968-e325-11ce-bfc1-08002be10318}/0000
UI Version - 2024.0111.1250.2016
AMD Audio Driver Version - <IP_ADDRESS>
Driver Provider - Advanced Micro Devices, Inc.
Windows Edition - Windows 10 Professional (64 bit)
Windows Version - 22H2

Steps to reproduce
Just open any project with Forward+ rendering.
Minimal reproduction project (MRP)
N/A

I also cannot launch godot after the latest amd adrenalin update (24.1.1)

The error code is VK_ERROR_UNKNOWN by the way, which sounds like a pretty uninformative message.
Will run a quick check to see if it can be reproduced on master.

I installed 24.1.1 on an AMD iGPU (Ryzen 7950x) and don't seem to be able to run into the error in master. Seems like someone else will need to confirm with a discrete AMD GPU.

I can't reproduce this on 4.2.1.stable (Windows 10 22H2, AMD Radeon RX 6900XT with 23.4.3 previously and 24.1.1 now) with an empty project. The editor's 3D viewport and project render correctly in all cases.
Before driver update (23.4.3)
In both cases, OpenGL appears first as I go through the project manager.
Forward+
Godot Engine v4.2.1.stable.official.b09f793f5 - https://godotengine.org
OpenGL API 3.3.0 Core Profile Context <IP_ADDRESS>420 - Compatibility - Using Device: ATI Technologies Inc. - AMD Radeon RX 6900 XT

Editing project: C:/Users/user/Documents/Godot/test_forward_plus
Godot Engine v4.2.1.stable.official.b09f793f5 - https://godotengine.org
Vulkan API 1.3.246 - Forward+ - Using Vulkan Device #0: AMD - AMD Radeon RX 6900 XT

Mobile
Godot Engine v4.2.1.stable.official.b09f793f5 - https://godotengine.org
OpenGL API 3.3.0 Core Profile Context <IP_ADDRESS>420 - Compatibility - Using Device: ATI Technologies Inc. - AMD Radeon RX 6900 XT

Editing project: C:/Users/user/Documents/Godot/test_mobile
Godot Engine v4.2.1.stable.official.b09f793f5 - https://godotengine.org
Vulkan API 1.3.246 - Forward Mobile - Using Vulkan Device #0: AMD - AMD Radeon RX 6900 XT
WARNING: 1 RID of type "StorageBuffer" was leaked.
     at: _free_rids (drivers/vulkan/rendering_device_vulkan.cpp:9286)
WARNING: 1 RID of type "Framebuffer" was leaked.
     at: _free_rids (drivers/vulkan/rendering_device_vulkan.cpp:9286)
WARNING: 4 RIDs of type "Texture" were leaked.
     at: finalize (drivers/vulkan/rendering_device_vulkan.cpp:9626)

After driver update (24.1.1)
Forward+
Godot Engine v4.2.1.stable.official.b09f793f5 - https://godotengine.org
OpenGL API 3.3.0 Core Profile Context <IP_ADDRESS>110 - Compatibility - Using Device: ATI Technologies Inc. - AMD Radeon RX 6900 XT

Editing project: C:/Users/user/Documents/Godot/test_forward_plus
Godot Engine v4.2.1.stable.official.b09f793f5 - https://godotengine.org
Vulkan API 1.3.270 - Forward+ - Using Vulkan Device #0: AMD - AMD Radeon RX 6900 XT

WARNING: Invalid pipelines cache header.
     at: _load_pipeline_cache (drivers/vulkan/rendering_device_vulkan.cpp:9200)

Mobile
Godot Engine v4.2.1.stable.official.b09f793f5 - https://godotengine.org
OpenGL API 3.3.0 Core Profile Context <IP_ADDRESS>110 - Compatibility - Using Device: ATI Technologies Inc. - AMD Radeon RX 6900 XT

Editing project: C:/Users/user/Documents/Godot/test_mobile
Godot Engine v4.2.1.stable.official.b09f793f5 - https://godotengine.org
Vulkan API 1.3.270 - Forward Mobile - Using Vulkan Device #0: AMD - AMD Radeon RX 6900 XT

WARNING: Invalid pipelines cache header.
     at: _load_pipeline_cache (drivers/vulkan/rendering_device_vulkan.cpp:9200)

WARNING: 1 RID of type "StorageBuffer" was leaked.
     at: _free_rids (drivers/vulkan/rendering_device_vulkan.cpp:9286)
WARNING: 1 RID of type "Framebuffer" was leaked.
     at: _free_rids (drivers/vulkan/rendering_device_vulkan.cpp:9286)
WARNING: 4 RIDs of type "Texture" were leaked.
     at: finalize (drivers/vulkan/rendering_device_vulkan.cpp:9626)

Are there any additional logs that I can provide in order to help with investigating this issue?
Also, I would like to specify that for me Godot crashes even when creating a new Godot project using Forward+.

Are there any additional logs that I can provide in order to help with investigating this issue? Also, I would like to specify that for me Godot crashes even when creating a new Godot project using Forward+.

I also redownloaded Godot and deleted %appdata%/Godot

Apparently a (second) restart fixed the issue.
To note: I did restart when the drivers first finished installing, and a shut down/startup has also been performed since, but AMD wanted an additional restart for some reason to make stuff work.
Sorry for wasting your time.


Numberbox format property

Issue Type
Bug report
Description
I use dx-number-box in my project and initialize format property as a string (from devexpress documentation):
data: function () {
		return {
			numberbox: {
				value: 100.123,
				format: "$ #0.##",
			}
		}
}

The format is applying well but in the browser console I've got the red message::

Invalid prop: type check failed for prop "format". Expected Object, got String.
found in --->   at test\components\numberbox.vue

is it normal? or I do smth wrong?

Hi!
Yes, this is a bug in our prop types. We will fix it in future releases.


fonts

https://github.com/rsms/inter/
https://black-foundry.com/blog/inria-serif-and-inria/
b/c Alegreya Sans looks so small 😭
Also:
https://github.com/belluzj/fantasque-sans
https://twitter.com/grrrck/status/1334852384418361345?s=20

make font fallbacks work again :(

make font fallbacks work again :(

Decision: replace Alegreya Sans with https://brailleinstitute.org/freefont


Add juliacon talk script to docs

Add the images to the PR comments itself and link them.

It looks to be working fine by placing it in assets folder as well https://gsa.sciml.ai/previews/PR42/tutorials/juliacon21/?

Are you concerned about the repo size due to saving images there?

Yeah, images pile up really quickly, so I like to make sure each PR is clean to not have them.

(just make sure to squash merge).


CORS Issue

How can we resolve a CORS issue?

What exactly do you mean?

Hi @akhilgupta1093, for now we don't have a dedicated middleware for this purpose yet. But the framework is compatible with native gin middlewares, so you can use e.g. github.com/gin-contrib/cors library:
router := gnext.Router()

corsConfig := cors.DefaultConfig()
corsConfig.AllowCredentials = true
corsConfig.AllowAllOrigins = true
corsConfig.AddAllowHeaders("Authorization")

router.Engine().Use(cors.New(corsConfig))

@akhilgupta1093 Does the problem still exist?

Hi, not for this reason, but I decided not to use this library. Seems like the standard gin middleware should fix the issue, thanks.


redis.Lock.acquire should take a timeout kwarg just like threading.Lock

https://github.com/andymccurdy/redis-py/blob/master/redis/lock.py#L135 as the title says redis.Lock.acquire should take a timeout kwarg to match the behavior of threading.Lock.

Lock.acquire accepts blocking_timeout, which I believe is what you're looking for.


Make mobs not suffocate in livestock crates.

About the PR

One line change. Makes livestock crates not airtight.
Why / Balance

Livestock currently breathes (the audacity!) and exhales chemicals that kill themselves pretty fast inside of crates.
The current sprite has what looks (to me) like an oxygen tank on the side, so I would support the idea if someone wants to figure out how to make that work. I only experimented enough to find out it was the exhaled gases.
Technical details

Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

tweak: Livestock crates are no longer airtight.

Ubuntu is high, the test fail makes no sense.

this will make animals in crates vulnerable to space


Some question about FID evaluation

I see that you use the ADM assessment approach:
In ADM (https://github.com/openai/guided-diffusion/blob/main/evaluations/README.md)

They say pre-computed statistics over the whole dataset, but when i load ImageNet 256x256: [reference batch](https://openaipublic.blob.core.windows.net/diffusion/jul-2021/ref_batches/imagenet/256/VIRTUAL_imagenet256_labeled.npz)

but get 10000 image, not  whole dataset, Is rcg also calculated in this way? I don't understand the 10000 here, could you please help me? Thank you very much!

This also confused me for a while. In the ADM-precomputed reference batch, the pre-computed statistics for FID evaluation are just 'mu' and 'sigma'. The 10000 images in the batch are only for precision and recall computation, and not used for FID.

yes, 'mu', 'sigma', is easy to understand, but 'mu_s', 'sigma_s', don't know what it is? And how to calculate, they do not provide the relevant code.

I remember it is for sFID.

I see. I am also confused here for a long time, really thank you very much :pray: :pray: :pray:


Calling async_task from an async function

I use Django Channels to manage websockets. I have configured Django-Q to use Django ORM as a broker.
In the WS message handler I store some data in DB, then I want to perform some async tasks, here is some sample code
async def receive(self, text_data):
  logging.debug(f"Received WS message: {text_data}")

  new_answer = Answer(
      answer=answer,
      ...
  )
  await new_answer.asave()
  async_task(add_answer_to_vectorstore, new_answer.id)

On the async_task call I get You cannot call this from an async context - use a thread or sync_to_async.. I could not find any instance of such error for Django-Q but I suspect it's because of using Django ORM as a broker (model.save() cannot be call within an async context, we should use .asave as in my code).
Has anyone else stumbled upon this? Any solution?

Additional info:

No code inside add_answer_to_vectorstore is executed
sync_to_async(async_task)(add_answer_to_vectorstore, new_answer) works but I don't see any logs in cluster, so I suppose the task is executed synchronously

Hi @Alain1405 - you might be more likely getting a response from https://github.com/django-q2/django-q2 which is an active fork of this project


feat: Fix offsets type check

I tried running some jobs with a packaged JAR from this branch but kept getting the following error, which may or may not be related:
pyspark.sql.utils.StreamingQueryException: u'Method com/google/cloud/pubsublite/spark/PslContinuousReader.createDataReaderFactories()Ljava/util/List; is abstract\n=== Streaming Query ===\nIdentifier: [id = d069e69e-69f8-443f-93c6-ccf8f5b6472e, runId = 1c618d95-d20d-44c6-8f7d-6be74543659f]\nCurrent Committed Offsets: {}\nCurrent Available Offsets: {}\n\nCurrent State: ACTIVE\nThread State: RUNNABLE\n\nLogical Plan:\ncom.google.cloud.pubsublite.spark.PslDataSource@7f8b0070' 21/01/15 23:53:21 INFO org.spark_project.jetty.server.AbstractConnector: Stopped Spark@68058ecf{HTTP/1.1,[http/1.1]}{<IP_ADDRESS>:4040}

I tried running some jobs with a packaged JAR from this branch but kept getting the following error, which may or may not be related:
pyspark.sql.utils.StreamingQueryException: u'Method com/google/cloud/pubsublite/spark/PslContinuousReader.createDataReaderFactories()Ljava/util/List; is abstract\n=== Streaming Query ===\nIdentifier: [id = d069e69e-69f8-443f-93c6-ccf8f5b6472e, runId = 1c618d95-d20d-44c6-8f7d-6be74543659f]\nCurrent Committed Offsets: {}\nCurrent Available Offsets: {}\n\nCurrent State: ACTIVE\nThread State: RUNNABLE\n\nLogical Plan:\ncom.google.cloud.pubsublite.spark.PslDataSource@7f8b0070' 21/01/15 23:53:21 INFO org.spark_project.jetty.server.AbstractConnector: Stopped Spark@68058ecf{HTTP/1.1,[http/1.1]}{<IP_ADDRESS>:4040}

the error tianzi@ saw was due to a wrong spark 2.3 api, we are using spark 2.4.

the error tianzi@ saw was due to a wrong spark 2.3 api, we are using spark 2.4.


Add @harry671003 to triagers

I've been invited to be a triager on Thanos. I thankfully accept.

Need to take a closer look at CI failures. I think they are failing everywhere


Remove frameborder attribute on YouTube block and use CSS border for W3C validation

We recently came across this error in the W3C validation of the YouTube block, so what about replacing the frameborder attribute with a border: none; ?
The error :

I like the idea, but it can be an unwelcome change for users who use providesAsset in their page_theme file, don't you think? I guess in that case the iframe will have borders after upgrading to a newer concrete5 version?

I didn't think about that, and inline style would always override any other value...
So i guess we'll stay with frameborder ! 😄

Although using inline styles is generally not good practice, maybe in this case adding style="border:none;" solves the issue.

Well, I still think it's a good idea to change it... but it should maybe not be released in a minor version.

I reopen and let the core team decide what to do 👍


What does this code mean?

Hello,
The following code confuses me, anyone can explain its grammar？
  []() -> LocalizationBase* { return new RTKLocalization(); });
 []()->  means what?
It is in Localization.cc of apollo1.0 and line 38.
thanks.

Its a lambda function with no input parameter and the return object having the type LocalizationBase*. Look up on lambda expressions here

I see, thank you！


Reconsider the "aborting" status

It would be simpler if we had a dedicated field for an abortion request instead of an aborting status.

The aborting state masks the doing state. State transitions from aborting are the same as from doing.
Also, since the user does not necessarily have to follow this request with a dedicated field, it would still be preserved in a subsequent possible retry.
Race conditions may occur that could solved with a dedicated field.

I already started working on a PR.
I added a boolean abort column to the jobs table. The migration will change all aborting states to doing states and set the abort to true.
One principle question: Should we keep the abort as true when the job is finished, or should we reset it to false? Does it matter somehow?

I came pretty far with everything (all but one test succeeded), but I think I need some help with the migration 😞. The migration is quite long as PostgreSQL does not allow the removal of one value from the enum type, so I have to create a new enum type and switch to it (and recreate all dependent indices, triggers, and functions). Also not a problem, but the problem is when changing the status column to the new type. Here is a reduced example:
-- Delete the triggers that depends on the old status type (to recreate them later)
DROP TRIGGER IF EXISTS procrastinate_jobs_notify_queue ON procrastinate_jobs;
DROP TRIGGER IF EXISTS procrastinate_trigger_status_events_update ON procrastinate_jobs;
DROP TRIGGER IF EXISTS procrastinate_trigger_status_events_insert ON procrastinate_jobs;
DROP TRIGGER IF EXISTS procrastinate_trigger_scheduled_events ON procrastinate_jobs;

-- Create a new enum type without 'aborting'
CREATE TYPE procrastinate_job_status_new AS ENUM (
    'todo',
    'doing',
    'succeeded',
    'failed',
    'cancelled',
    'aborted'
);

-- We need to drop the default temporarily as otherwise a DatatypeMismatch would occur
ALTER TABLE procrastinate_jobs ALTER COLUMN status DROP DEFAULT;

-- Alter the table to use the new type
ALTER TABLE procrastinate_jobs
ALTER COLUMN status TYPE procrastinate_job_status_new
USING (CASE
    WHEN status::text = 'aborting' THEN 'aborted'::procrastinate_job_status_new
    ELSE status::text::procrastinate_job_status_new
END);

And here the error I get because of the last statement:
2024-07-31 14:52:28.849 UTC [2525] ERROR:  operator does not exist: procrastinate_job_status_new = procrastinate_job_status at character 129
2024-07-31 14:52:28.849 UTC [2525] HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
2024-07-31 14:52:28.849 UTC [2525] STATEMENT:  -- Delete the triggers that depends on the old status type (to recreate them later)

I don't know how I could be even more explicit about the casting?!

Should we keep the abort as true when the job is finished, or should we reset it to false? Does it matter somehow?

(As long as the job is not retried, I don't have a strong opinion)

Fixed by #1139


Pin traces to bottom for autoscrolling

automatically scroll down to the last trace
when scrolled somewhere not at the end of the traces, prevent autoscrolling

fixes #20

Hmm, seems like this sometimes cuts the last trace element(s) off:

ready to review!


Uncaught TypeError: Cannot read property 'tokens' of undefined

[Enter steps to reproduce below:]

...
...

Atom Version: 0.168.0
System: Unknown Windows Version
Thrown From: minimap package, v3.5.4
Stack Trace
Uncaught TypeError: Cannot read property 'tokens' of undefined
At c:\Users\eerieN\AppData\Local\atom\app-0.168.0\resources\app\src\display-buffer.js:958

TypeError: Cannot read property 'tokens' of undefined
  at DisplayBuffer.module.exports.DisplayBuffer.screenPositionForPixelPosition (c:\Users\eerieN\AppData\Local\atom\app-0.168.0\resources\app\src\display-buffer.js:958:50)
  at MinimapView.module.exports.MinimapView.onMouseDown (c:\Users\eerieN\.atom\packages\minimap\lib\minimap-view.coffee:500:27)
  at space-pen-div.<anonymous> (c:\Users\eerieN\.atom\packages\minimap\lib\minimap-view.coffee:1:1)

Commands
  2x -1:08.4 core:backspace (atom-text-editor.editor.is-focused)
  2x -1:07.9 core:move-up (atom-text-editor.editor.is-focused)
     -1:07.3 editor:newline (atom-text-editor.editor.is-focused)
     -1:06.7 core:backspace (atom-text-editor.editor.is-focused)
     -1:04.4 core:paste (atom-text-editor.editor.is-focused)
     -0:59.1 core:copy (atom-text-editor.editor.is-focused)
     -0:58.1 core:paste (atom-text-editor.editor.is-focused)
     -0:13.3 editor:select-to-end-of-line (atom-text-editor.editor.is-focused)
     -0:13.2 core:cut (atom-text-editor.editor.is-focused)
     -0:01.9 editor:select-to-first-character-of-line (atom-text-editor.editor.is-focused)
     -0:01.4 core:cut (atom-text-editor.editor.is-focused)
  2x -0:01.0 core:backspace (atom-text-editor.editor.is-focused)
  2x -0:00.6 core:move-down (atom-text-editor.editor.is-focused)
     -0:00.2 editor:move-to-end-of-screen-line (atom-text-editor.editor.is-focused)
     -0:00.1 editor:newline (atom-text-editor.editor.is-focused)
     -0:00.0 core:paste (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "disabledPackages": [
      "tree-view"
    ]
  },
  "minimap": {
    "plugins": {
      "selection": true,
      "git-diff": true,
      "find-and-replace": true
    }
  }
}

Installed Packages
# User
line-ending-converter, v0.4.0
minimap, v3.5.4
minimap-color-highlight, v3.1.0
minimap-find-and-replace, v3.1.0
minimap-git-diff, v3.1.0
minimap-highlight-selected, v3.1.0
minimap-selection, v3.1.0
open-recent, v2.0.0
save-session, v0.11.3
Sublime-Style-Column-Selection, v1.1.3

# Dev
No dev packages

/cc @atom/core

Duplicate of #204. Closing it.


Add measures on the Stiefel manifold

Add the following measures from Chikuse, Statistics on Special Manifolds. 2003:

[x] Hausdorff
[ ] Matrix Langevin
[ ] Matrix Bingham
[x] Matrix angular central Gaussian
[ ] Matrix generalized Langevin
[ ] Matrix generalized Scheiddegger-Watson
[ ] "general Family" (Chikuse, 2003)

Matrix Langevin and Bingham are partially implemented; to compute their log densities, we need an implementation of hypergeometric functions with matrix arguments, which should perhaps be its own Julia package. @stla wrote this gist, which might be exactly what we need.

Hello @sethaxen
I have a package: https://github.com/stla/HypergeoMat.jl
I didn't register it to JuliaHub.

Thanks, @stla, that looks really useful. It would be nice to have the package registered. Would you accept several PRs to get it ready for registration? Or alternatively, would you like to keep it at is, and I would develop a new package derived from it for registration?

Also note that I'm not a star in Julia. The package maybe imperfect.

Neither am I, and, is there such a thing as a perfect package?

Yes, I would accept PRs.
I think the package is good globally, I'm just not sure of my myriad of macros @inbounds, that I put everywhere.


Feature/vocabulary term freq estimator

Basically the only new thing is src/feature_extractors/term_frequency_feature_extractor.py

Forgive me for I have sinned and uploaded a dataset to github. It's only 5 mb, and the moment we add dataset loading procedure to ci-cd, we can remove it from the repository.

@implausibleDeniability good feature generator based of frequency of words!


Switch Order table to provide more annotated information

Right now, we have a status field on Order which has a few options: IN_PROGRESS, PENDING, COMPLETED, and REFUNDED.
This is okay, but we can / should do better. For example, we now fully support multiple transactions on an Order. So an order can be "completed" and still have a cart. Or it can be "refunded", in that it has a refunded transaction, but "completed" in that it has another transaction that is still valid.
I think the solution is that we should instead annotate the queryset with the payment / refund information and use that to determine what state the order is in. Ideally in a way that lets us still filter by "state", but remove the status field.

(this is waiting on the merge of #409 changes.)


JOINDIN-649 Add in CRUD for talk links

Delete, Post, Put, Get added
Changed the structure of the test to make smaller tests
Had to adjust the autoloader because of this
All lines changes are covered by tests

Can one of the admins verify this patch?

Ok to test
On Tue 24 Jan 2017 at 21:27, joindin-jenkins<EMAIL_ADDRESS>wrote:

Can one of the admins verify this patch?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/joindin/joindin-api/pull/392#issuecomment-274944026,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF1wJZKuWfiPO6LGsOAXkwDy9tkZqC2nks5rVmysgaJpZM4Lszk4
.

Sorry its a little bigger than I thought. This PR contains both

ok to test

@exussum12 can you have a look at the conflicts when you get a chance please

Note, the db patch number will need to be increased to 70

@exussum12 - just to confirm, as far as I can tell, I can close #390 as the commits are contained within this? Have you got a little time to go through and sort the conflicts? Would be great to get this merged :)

Thats right, all is in here, Sorry was going to look after I added to the front end. Will fix them now!

Was a bit of a messy merge. Can someone please double check I didnt break anything

Sorry found a small issue with this, I have committed the fix on 651


Typo in LaunchLunarModule script

The LaunchLunarModule script has a "StartThruster" and a "StopThruster" function. Unfortonately, both functions have typos in them, and they are instead "StartThurster" and "StopThurster"

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

ID: 3d715666-5a8f-a497-db0e-152491d52813
Version Independent ID: be21949e-301f-78cb-ccc2-0fe6eb87c009
Content: MR Learning Base Module - Lunar Module Assembly Sample Experience - Mixed Reality
Content Source: mixed-reality-docs/mrlearning-base-ch6.md
Product: mixed-reality
Technology: mr-dev
GitHub Login: @jessemcculloch
Microsoft Alias: jemccull

Wow, good catch! Yes, we'll fix the typo and provide an update here once the fix is live. Thank you

@mr0ng, do you know if this was corrected yet?

@jessemcculloch This issue was addressed with PR #1868, commit https://github.com/MicrosoftDocs/mixed-reality/commit/f807e57597b92d6189f40695e8d388e28bd44403.


feat: populate the http server

Stack:

#806
#804
#810
#799
#798
#797 ⬅
#758

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is

✓ Commit merged in pull request #799


A way to have a swipe distance threshold

Hey!
Is there a current way how I could add a swipe distance threshold? Meaning a minimum amount of distance needs to be swiped for interaction to take effect?

hmm.. the moment you start swiping, the Interactable view gets dragged with your finger. Currently, it's always immediate. If you let go, it will snap back to its place (assuming you didn't move it too far).
What is the use-case you want this behavior for? so it will be a little easier to imagine

I have created a sliding navigation

But I need to have a margin of error so that when users interact with the content the slides don't move.
Does that make sense?

wow this is so cool! do you mind sharing the code so I can play with this?
what sort of content will have horizontal dragging? will there be horizontal scrollviews inside?
or are you worried that the user is just accidently moving their finger on the content?

I'm doing this experiment for work, so I can't just share it. I will isolate it later today and give you a link.
I will have a list view inside, but I'm mainly worried that this will be triggered accidentally and I would like for the movement to start after the user has dragged finger horizontally, let's say, after 15 points.
Does that make sense?

It makes sense, I'm trying to think how to do that..


media_player volume buttons if statement alignment

This fixes an issue I have with a silicon frontier internet radio (and probably others). This player supports both VOLUME_SET and VOLUME_STEP. However, the if statement for VOLUME_SET also checks the current level, which this items cannot provide. This means that no volume controls at all are shown. By adding this second condition also to the VOLUME_STEP block ensures that at leasst the plus/minus controls are available.

This is rather strange. Does HA's UI handle it correctly?

I've solved it slightly differently. Could you please check if it works now?


VSCode is not saving any file nor exiting IDE after updated to v1.28.1

After accepting suggested update to version 1.28.1, VSCode is no longer saving any files. However, changes are shown on filles untill  IDE is restarted.
VSCode is no longer closing down / Exiting either using the close icon, or by exit option from the menu. The only way to exit VSCode is killing it's process through Windows Task manager.
Uninstalling, Reinstalling or Downgrading to the previous version didn't solve the problem.

Can you illustrate the problem you are having with screen shots or provide more details.

However, changes are shown on filles untill IDE is restarted.

Can you please elaborate where changes are shown?


Adds nwc requester

#127  👈
develop

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

Join @shreyav and the rest of your teammates on  Graphite


Callback called twice on findGroups error

When calling findGroups(opts, callback) I receive a ECONNREFUSED error twice.
The first at onClientError ln 493.
The second in Search.call() ln 1588.
<EMAIL_ADDRESS>

I too just stumbled upon this error. Is there any progress on resolving this error?

Confirmed this exact issue as described.
<EMAIL_ADDRESS>

Similar Issue. Callback called twice on findUser error (when incorrect password used for ad authentication)


tmux colors wrong in WT preview version

Environment
Windows build number: 10.0.19041.388
Windows Terminal version: 1.2.2022.0

Any other software?
wsl 2
zsh 5.4.2
tmux 3.2

Steps to reproduce
Open tmux with custom colors theme in Windows Terminal official and preview version
Expected behavior
Expect the colors to be the same in official and preview version
Actual behavior
The colors are correct when using just zsh, but wrong in the preview version when using tmux.
It looks like the zsh prompt colors are still correct, but anything set in .tmux.conf is wrong.
Official windows terminal:

Preview windows terminal:

I had this in my tmux config to enable truecolor:
set-option -ga terminal-overrides ",rxvt-256color:Tc"
After removing that it looks good in both official and preview version.


feat: Standardize Inference

Introduces new build image pipeline and standardized inference

Covered in https://github.com/Azure/kaito/pull/216 https://github.com/Azure/kaito/pull/217 https://github.com/Azure/kaito/pull/218 https://github.com/Azure/kaito/pull/219

Covered in https://github.com/Azure/kaito/pull/216 https://github.com/Azure/kaito/pull/217 https://github.com/Azure/kaito/pull/218 https://github.com/Azure/kaito/pull/219


Scalar installs Git without LFS

I attempted to assess Scalar but failed - the repo that I work in uses GitLFS and the private version of Git that Scalar installs doesn't include GitLFS. It's not clear if GitLFS is supported with Scalar - is there guidance for using GitLFS with Scalar?

We do not package Git LFS with our Git installer, but you can install it directly: https://git-lfs.github.com/
Git LFS should work without issue when using Scalar with a regular Git clone. Git LFS will probably not work with the GVFS protocol.


"Icon font not found for set: pencil"

Hi there
I've been working on getting the scalar crypto spec to use the right styles as was pointed out in riscv/riscv-crypto#89. It seems to work, but I get a build error:
work@ben-TF:~/riscv/riscv-crypto/doc/adoc-scalar$ make all
asciidoctor-pdf \
        -a pdf-style=resources/themes/risc-v_spec-pdf.yml \
        -a pdf-fontsdir=resources/fonts \
        -o riscv-crypto-spec-scalar.pdf riscv-crypto-spec-scalar.adoc
Icon font not found for set: pencil
  Use --trace for backtrace

If I comment out lines 165-167 of "resources/themes/risc-v_spec-pdf.yml", then everything works fine, I just get a different icon for the NOTE admonition.
The exact file set and makefile I'm using can be found here. The branch of the riscv-crypto repo I'm using is this one. Everything is under doc/adoc-scalar.
Tool versions:
work@ben-TF:~/riscv/riscv-crypto/doc/adoc-scalar$ asciidoctor-pdf --version
Asciidoctor PDF 1.5.0.alpha.17.dev using Asciidoctor 2.0.10 [https://asciidoctor.org]
Runtime Environment (ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-linux-gnu]) (lc:UTF-8 fs:UTF-8 in:UTF-8 ex:UTF-8)

I'm using Ubuntu 20.04, with asciidoctor-pdf installed via the ruby-asciidoctor-pdf apt package.
Please let me know if you need any more information? This feels like it is a problem more with my system than the template, but I figured I'd ask to be sure.
Many thanks,
Ben

Managed to fix this by using rvm and using gem to install the dependencies rather than relying on the ubuntu packages.


Converting the tests from Enzyme to Testing Library.

Hi :wave:
I recognized your library when looking for a solution that allows me to check the previous pathname. :grin:
I saw that you guys are currently using Enzyme, which itself seems to be blocking the support of React 17+.
I and many friends are a part of the Open Source Raid Guild, a group that supports OSS projects. :blue_heart:
Many of us work together on one large PR. :nerd_face:
We would fork your project to our Github Team and work on our fork, and communicate with some of the maintainers closely over at Discord.
Read more about us: https://github.com/OpenSourceRaidGuild/tutorial-quest#hi-wave-welcome-to-the-open-source-raid-guild-crossed_swords
Our discord server: https://discord.gg/JczjG8su
Let us know if you've any questions, and feel free to join the Discord already, even if it is just a question. :partying_face:

@hinok FYI this would unblock #46.

@joealden  @tigerabrodi Feel free to create a PR here that will use react-testing-library instead of enzyme.

We will create a PR soon.
Any objections to adding more tests as well?

@hinok Nearly done.

Should have something by this weekend.


GDXray not available anymore

GDXray: X-ray images for X-ray testing and Computer Vision is not available anymore. The link of its zip get "Page not found":
https://domingomery.ing.puc.cl/images/GDXray/Baggages.zip
https://domingomery.ing.puc.cl/images/GDXray/Castings.zip
https://domingomery.ing.puc.cl/images/GDXray/Welds.zip
https://domingomery.ing.puc.cl/images/GDXray/Nature.zip
https://domingomery.ing.puc.cl/images/GDXray/Settings.zip

You don't say where you got those links, but the current links on the main page (https://domingomery.ing.puc.cl/material/gdxray/) appear to be valid e.g. http://dmery.sitios.ing.uc.cl/images/GDXray/Nature.zip


Implement "IsNumeric": false

{"foo":"abc"}

{"Variable": "$.foo", "IsNumeric": false}

If foo is not numeric, this will return true
Support for all type checks

Code-wise looks good to me - I'm trying to think of a better variable name for the tests, but I don't think we should hold up the merge for it.


repeatscout: Error: Directory not empty

$ brew install repeatscout
==> Reinstalling homebrew/science/repeatscout
==> Downloading http://repeatscout.bioprojects.org/RepeatScout-1.0.5.tar.gz
Already downloaded: /home/ngs/.cache/Homebrew/repeatscout-1.0.5.tar.gz
==> make
Error: Directory not empty - /home/ngs/.linuxbrew/Cellar/repeatscout/1.0.5

The error seems to be in this line of the install prefix.rmdir.  If you change this to rm_r prefix it installs correctly on linux.  Not sure why the prefix.rmdir removes all files from directory on mac but not on linux.

There's a hack on Linux for a bug in ld.so of glibc 2.19 that creates an empty directory $prefix/lib, so $prefix is not empty on Linux. That's causing a few occasional build errors like this, so I think we may have to find a different solution to that bug.

Fixed!


Upgrade Go version to 1.21 & go-yaml to 3.0.1

This PR upgrades the version of Go to 1.21 in order to remediate CVE-2022-29526. Similarly, it updates the go-yaml version to 3.0.1 in order to remediate CVE-2022-28948.
Fixes #353

Done!


Added timestamp for the console tree builder.

Added timestamp option to be able to log with the current time.
Need to pass a time format in which time has to be formatted.

Hi, thanks for checking it. Going to fix it ASAP

@insearching Did you notice the last comment please? Not sure if you got notification for only in file comment so I write again.

Yes, I did, sorry, I'm on vacation now, will be able to close it in a week.

@jraska I have fixed formatting issues. Please have a look when you have time.

thanks for reviewing :)


Fix for filled chest bug

This should fix the bug for the filled chest bug, please test when you find out how to recreate it.

@waafleston try this and see if it fixes for your problem.

@waffleston ^

It did not appear to solve the problem.  It still allows the trade to happen.
Recreation:
Fill chest all the way with stacks of 64 stone.
[Trade]
1 stone
1 dirt

Right clicking results in one stone being deducted from chest but no dirt - should prevent trade.

@waffleston should work now

@SparklingComet This pull fixes both issues were having and cleans up a bit(also fixes some wierd indenting that existed)
Uses @waffleston code for the data value fixes

Now its ready

Assuming that your tests went well, I will now merge this.
Thanks for the hard work :)


Open ssl 1 1 1m+quic

Rebase onto 1.1.1m (bug fix release)

Checklist

[X] documentation is added or updated
[X] tests are added or updated

Pushed a fixup commit... won't bother to fixup until the next rebase to 3.0.2.


.myuw .rounded bugged for buttons

If you add .rounded to a .btn, the button radius of 4px trumps .rounded.  Add !important to .rounded?

Yea, I think !important is the best way to do this. Changing.

Should be fixed now.

@jhanstra which PR was this fixed in?

nm, found the commit df84fd4


Feature fill-left

Now the initial state can be taken into account at the left side of the time bar. It is necessary if you want to display the correct fractions of states over, for example one week.
It is a bit against the conventions of grafana. After getting the data for the chosen time range into the panel it starts a second query to fetch the last values before the original from time point for all measurements. This point will be added as first DistinctPoints with the timestamp set to from.
The time for the secound query to look in the past can be configured in the options:

I removed the old function applyPanelTimeOverrides(). It never gets called because it's no method of the panel any more.
This should solve Issue #69
I tested only with Influxdb as data source and it seems to work quite good. But it should also work with other data sources.

when do we see this in the addon? version?

@ryantxu What is your opinion? I tested the feature also with postgres datasource and it worked nicely. What do you think? Is it to hacky? Is there a better solution for the problem?

For me, it didn't solve #69 with InfluxDB

For me as well didn't solve 69 i'm using MS SQL, but yes some sort of fill-left option would be nice.


chore: zeebe-operator to 0.0.23

chore: Promote zeebe-operator to version 0.0.23

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Defang SDK

It would be neat if you could import an SDK to control your Defang provisioned infrastructure from within your application.
For example something very loosely along these lines:
import defang from '@defang/sdk';

function myMonitoringService(){
  const workerService = defang.getService('worker');
  const instanceCount = workerService.getInstanceCount();
  const customMetric = myPrivateFunctionThatGivesMeARelevantMetric();
  if(customMetric > 0.8 && instanceCount < 10) {
    workerService.setInstanceCount(instanceCount + 1);
  }
  if(customMetric < 0.4 && instanceCount > 2){
    workerService.setInstanceCount(instanceCount - 1);
  }
}

Relates to #451


AttributeError: module 'torch' has no attribute 'cov'

hi,which torch version should i install, i try 1.12.0 and 1.8.0,but still casuse the problem

Pytorch version should >=1.10.0 for torch.cov according to the official pytorch documentation.
https://pytorch.org/docs/1.12/generated/torch.cov.html?highlight=torch cov#torch.cov
Please double-check if your pytorch is well installed and if you run the correct pytorch version.

you can use this code  instead
tmp = np.cov(embedding_vectors[:, :, i].T.cpu().numpy())
cov[:, :, i] = torch.from_numpy(tmp).to(cov.device) + 0.01 * I


Question about config of networks for users.xml

Hi, i am using 0.9.3 , and when i set a new user, it auto generates network config like this:
<networks>
    <host_regexp>(chi-[^.]+\d+-\d+|clickhouse\)\.default\.svc\.cluster\.local$</host_regexp>
    <ip>::1</ip>
    <ip><IP_ADDRESS></ip>
</networks>

i have two questions

according to the official website, For use in production, only specify ip elements (IP addresses and their masks), since using host and hoost_regexp might cause extra latency. Is it a must to use this host_regexp in production?
i am using in Intranet, and i do not want any ip filters. the default setting is a whitelist so it blocks connection from other pods (e.g. User default is not allowed to connect from address <IP_ADDRESS>), and the network segment is dynamic so admin/networks/ip: "<IP_ADDRESS>/8" does not work for me. Is there any method to avoid the network filtering?

Thank you!

update:
For the second question, it seems work if i change this, is that right? i am not familiar with ip rules
chConfigUserDefaultNetworksIP:
      - "::/0"

@xiaozzz,

there is no or very little performance penalty when hostRegexp is used, since ClickHouse cashes DNS resolution.
You can enable connections from everywhere by adding a line to your ClickHouseInstallation CRD:
{code}
spec:
configuration:
users:
default/networks/ip: "::/0"
{code}


New permissions

Purpose
Sets permissions for models:

WorkflowLevel1
WorkflowLevel2
WorkflowTeam
Portfolio
Indicators
Objective

Specs
https://docs.google.com/spreadsheets/d/1mWGhO-Acin5SQnfOrHm58UCY3Y965x98fk9i6-ozpq0/edit?ts=59de11f0#gid=0

Coverage increased (+1.6%) to 50.748% when pulling 77fce7afc9b56d7cb2343f70fb15701d922d8f83 on jefmoura:new-permissions into cfd7ba89647116497a9a8dde5040a9276ea8f610 on toladata:dev-v2.

Coverage increased (+1.1%) to 50.289% when pulling 99165fb147860bcfec90c0baaadc15f23a8ab764 on jefmoura:new-permissions into cfd7ba89647116497a9a8dde5040a9276ea8f610 on toladata:dev-v2.


[BUG] Migrations not executing correctly

Is there an existing issue for this?

[X] I have searched for any related issues and avoided creating a duplicate issue.

Have you read our code of conduct?

[X] I have read and agree to the code of conduct

Current Behavior
Getting an error trying to setup the tasks app.
Created a MySQL database called "vztaskmaster" from MySQL
Attempted to run the database migration step according to the setup instructions...
Got an error that needed to install mysql2, so then ran the command "npm install mysql2"
Attempted the database migration command again, got the following error:
PS C:\Users\removed\Downloads\Slack Workflows\Applications\VZ Taskmaster> npx sequelize-cli db:migrate --url 'mysql://root:removed@localhost:3306/vztaskmaster'

Sequelize CLI [Node: 16.4.1, CLI: 6.2.0, ORM: 6.6.2]

Parsed url mysql://root:*****@localhost:3306/vztaskmaster
==<PHONE_NUMBER>4545-create-task: migrating =======
==<PHONE_NUMBER>4545-create-task: migrated (0.070s)

==<PHONE_NUMBER>5427-create-user: migrating =======
==<PHONE_NUMBER>5427-create-user: migrated (0.070s)

==<PHONE_NUMBER>0421-user-to-task-key: migrating =======

ERROR: Referencing column 'UserId' and referenced column 'id' in foreign key constraint 'Tasks_UserId_foreign_idx' are incompatible.

Expected Behavior
I was hoping that the app would start and run.
Steps To Reproduce
Just running through the setup.md documentation...
Environment
- OS: Win 10
- Language version: Node v16.4.1

Anything else?
Environment file:
SLACK_BOT_TOKEN=xoxb-removed
SLACK_APP_TOKEN=xapp-removed
DB_URI=mysql:root:removed@localhost:3306/vztaskmaster
SAMPLE_DB_URI=sqlite:./database.sqlite3

Weird. We develop the sample using SQLite, but use Sequelize to abstract any concerns about different underlying datastores. Let me do some testing with MySQL to try figure this out.

@mcsescott - This is resolved now, thanks for your report!


Deleting not existing key in cluster mode fails with MOVED error

Environment:

Node.js Version: v14.16.1
Redis Server Version: AWS ElastiCache Redis in cluster mode. Engine Version Compatibility: 6.2.5
Node Redis Version: 4.0.4
Platform:  Amazon Linux 2 (Linux 4.14.177-139.254.amzn2.x86_64) and on Windows 10 as well

minimal code to reproduce:
const cluster = createCluster({
  rootNodes: [{ url: "redis://*******.cache.amazonaws.com:7000"}]
})

await cluster.connect()
await cluster.del(['not-existing-key])

Received error: ReplyError: MOVED 12723 ***:7000
It happens sometimes for existing keys as well.
------------ EDIT ----------
With an existing key in cluster mode it also fails sometimes:
const key = "somekey"
await cluster.sAdd(key, "value2")
console.log('exists:', await cluster.exists([key]))  // prints 1
await cluster.del([key])  // fails with `MOVED` error

The cluster has 30 nodes with 1 replica each (total 60)

Found a solution that worked for me, needed to set the maxCommandRedirections value to be higher than the default 16. I set it to be 100 and it worked.
The reason I think is because we have 30 shards with 1 replica each (60 nodes). We rebalanced the cluster multiple times in a single day due to some bug that we had. This probably resulted in a lot of movement of keys. Also our Redis was chocked with 100% memory, so perhaps it also tried moving things around to rebalance itself.


Login page revamped to match the retro theme

Pull Request Format
PR Naming
Issue #13 : Login page can look way better solved
Type of PR

Improvement in style, fonts, colours and themes .
[ ] Bug fix
[cool retro login button; background and a hazy login box ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): ___________

Description
This pull request aims to [enhance the look of the login page making it more attractive to the eye.].
Screenshots / Videos (if applicable)
Before

[Describe the state before the changes - Missmatch in the fonts; the theme did not match the overall type of website; did not feel attractive; boring login ]

After:

[Describe the state after the changes - Beter visuals; matches the theme of website; fun to look at; minute changes that go well together cohesively]

Checklist

Add X in the box to specify.
[X ] I have performed a self-review of my code.
[X ] I have tested the changes thoroughly before submitting this pull request.
[ X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[X ] I have commented my code, particularly in hard-to-understand areas.

Additional Context
[Provide any additional context about the changes, such as specific challenges you faced or decisions you made. This can help reviewers understand the rationale behind your changes.]-Aesthetics are the only thoughts I had
Thank you for reviewing my pull request!

@harbakshsinghbaath After reviewing the login page, I noticed that the background doesn't look very good as a gaming E-Com site, and the color and size of the login button are too large. Please fix it.

sure will change the size of login button and if you have any ideas as to what you want as the background I'm open to ideas

this image will match the colour gradients of the buttons we have in home page what do you think of it?

fixed the size of login button just needed input on the background

@harbakshsinghbaath
I recommend making the background slightly blurred to enhance the focus on the login form. Additionally, the button currently appears a bit large; reducing its size would improve the overall aesthetics.
Please sync your fork with the repo and make these changes. Once you’re done, you can also consider adding similar adjustments to the sign-up page.

These are the final changes as you asked, the login button according to me now looks suitable in size and the background is a bit more understated so it doesn't take away the focus from login form
as for the signup page id be delighted to revamp it too as I'll be able to maintain the theme but could you assign a new issue to me for it?

(please do add hactober fest tag to me too) And I've synced the fork to my repository too.

Ok I check if there is not hactoberfest tag...I will add it.

Thank you so much. Issue #69 is also opened by me and I would be glad if you'd assign it to me

Thank you so much. Issue #69 is also opened by me and I would be glad if you'd assign it to me

assigned already


Add CpuTimes and CpuPercent

Adding some cpu features from psutil.

Any update on this issue ? Can I do something to help this PR to get merged ?

I'll try and find some time to review this soon - there are a lot of changes here!
(In the future, it's probably best to make formatting changes to existing code in a separate PR, so that it's easy for reviewers to see what has been added.)

Looks good - I merged #31 first and it's left some conflicts that need resolving but happy to merge after that.

Thanks! I just resolved the conflicts.


Slow Response time on long running tab sessions (likely a websocket reconnection problem)

Version
Forked from 1.45.0
Describe the bug
We are finding that occasionally the bot takes a very long time to respond (somewhere around a minute.
We did some investigative work and we have a running theory.
The most reliable way for us to reproduce it is to open a chrome tab with the webchat, have your computer go to sleep for a few minutes (about 5) re-open it and resume the chat.
Our investigations points to the problem having to do with websocket connections. We feel like when the websocket is lost, it takes about a minute before it reconnects. The gotcha is that we have reports of users experiencing this while using the bot. But this report also had a very long running tab.
Perhaps there is some logic around destroying the websocket after some time. I have a Chrome performance recording but for now i will include some of the screenshots from that recording.

The first screenshot is to show that a function call is made to destroy the websocket and later it reconnects.
The second is to show the timeline it took before making that call.
I am curious if I can get a description of the websocket logic. Is there a timeframe that it will close?
To Reproduce
Steps to reproduce the behavior:
(Only tried on MacOS Chrome both up to date)

Go to webchat.mazda.carlabs.com
send a few random messages
have your computer go to sleep while the tab is still open for about 5 minutes
message the bot again and it might take a minute or so to respond.

Expected behavior
Webchat should reconnect to the websocket as quickly as possible.
[Bug]

Love your technical deepness and curiosity, and excellent explanation. So I am wearing my technical hat to give you as much details as I could.

Web Socket doesn't work across sleeps I believe, including switching apps on iPhone, they will get killed

Today, Web Socket doesn't have a good connection detection algorithm

DirectLineJS is responsible for the connectivity, but currently, the resume/end conversation is quite broken in Web Socket story, we are planning to work on it during this sprint (4.6, releasing mid-to-late October)
Server-Sent Event is a better protocol for dealing with intermittent connectivity and better power consumption as well, despite it is half-duplex (we use Web Socket in half-duplex fashion today)

We don't support SSE on our servers yet, no plan either 😥
We tried something experimental in a hackathon project, building a WS -> SSE bridge, and it looks quite promising to me

After DirectLineJS rework is done, you don't need to bump Web Chat. You can use newer version of DirectLineJS in older version of Web Chat, including Web Chat v3 (0.*.*)

Will talk to the team. This bug will serve as a vote to our Direct Line rework. 👍

@compulim Thank you for the response!

Adding blocked tag since this would propagate from a DLJS change first.

Adding blocked tag since this would propagate from a DLJS change first.

This work hasn't been approved. Please keep an eyes out for update from @Kaiqb.

I am not able to repro the behavior using the website (webchat.mazda.carlabs.com) that was mentioned in the issue. I am not sure whether the site works or not. For now, I am going to close this issue but if this is still causing problems, feel free to re-open.


no such table: main.catalogue_product__old when creating a new product

Hi,
I've ran into a really strange error which I'm not able to debug.
On a fresh django-oscar installation (tested with 1.6.4 and 2.0-dev) I'm getting this when I add new product via the dashboard:
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 85, in _execute
    return self.cursor.execute(sql, params)
  File "/usr/local/lib/python3.7/site-packages/django/db/backends/sqlite3/base.py", line 296, in execute
    return Database.Cursor.execute(self, query, params)
sqlite3.OperationalError: no such table: main.catalogue_product__old

I guess there is some bug in the migrations? I looked into this quite some time and couldn't find the problem.
I prepared a minimal example:
minimalexample.zip
In the extracted folder, run the following commands to init the project and get the same error:
# I tried both the system's pip and virtual envs
pip install django-oscar
python manage.py migrate
# sets up superuser "admin"<EMAIL_ADDRESS>with password "admin"
python manage.py loaddata data/auth.json
# this triggers the error
python manage.py loaddata data/catalogue.json

This bug also appears when creating a new product via the dashboard in both oscar 2.0 and 1.6.4...
Any ideas?

I'm not able to reproduce this with the example code you have provided - I get an error loading the catalogue fixture but it's because there is an invalid foreign key relationship.
Oscar does not have a main app, which is what the table main.catalogue_product__old appears to be coming from. Nor does it have any models which would result in that table name.
I think the issue here is that you have a main app in your project, which is perhaps a fork of Oscar's catalogue app, and where there is inconsistent database state.

Thank you for your answer. I think I found the problem. It's a problem with Django and the new alter table command in SQLite 3.26: https://groups.google.com/forum/#!topic/django-updates/htVqH24DImg
Django already has an open pull request for this:
https://github.com/django/django/pull/10733

I did this in pycharm and it did work:
pip install Django --upgrade
Then
python manage.py migrate
python manage.py makemigrations 'app_name'
python manage.py migrate

I did this in pycharm and it did work:
pip install Django --upgrade
Then
python manage.py migrate
python manage.py makemigrations 'app_name'
python manage.py migrate

A really great trick, it worked for me!!1
Thanx a ton

I did this in pycharm and it did work:
pip install Django --upgrade
Then
python manage.py migrate
python manage.py makemigrations 'app_name'
python manage.py migrate

I m facing the same issue in pycham but its not getting done by thjs.

I did this in pycharm and it did work:
pip install Django --upgrade
Then
python manage.py migrate
python manage.py makemigrations 'app_name'
python manage.py migrate

Man I could KISS you! I have spent 14 hours trying to debug this problem with another Django app because after 3 days of writing the web server crashes when trying to write to the database. This crash caused over one hundred exceptions to be thrown and I didn't even know where on earth to start.
 This fixed my problem one hundred percent and I don't have a single error now. Oh my days! There is a god!


Add static build support

This PR adds the static library compilation and fixes #220.
I have marked it as a draft because as of now I have not been able to test if the shared library compilation still works (I need the static libraries because I do not have all the shared dependencies installed)

Thanks @rapgenic for tackling this!
I think it makes a lot of sense to provide a static build of xwidgets, for many reasons. I just looked it up and found your xeus-octave project, which I think is a great addition. Kudos on this!

Thanks @rapgenic for tackling this!
I think it makes a lot of sense to provide a static build of xwidgets, for many reasons. I just looked it up and found your xeus-octave project, which I think is a great addition. Kudos on this!

I can see that all the tests have passed, can this be considered enough to prove that there is no breaking change? (I am asking that because I'm having a few difficulties to build all the dependencies on my system)
Than you for your nice words on my project! I must say however that is still very much a proof of concept and I'm experimenting with many things at the moment, integration the xwidgets library is one of the next things I'll be checking out

I can see that all the tests have passed, can this be considered enough to prove that there is no breaking change? (I am asking that because I'm having a few difficulties to build all the dependencies on my system)
Than you for your nice words on my project! I must say however that is still very much a proof of concept and I'm experimenting with many things at the moment, integration the xwidgets library is one of the next things I'll be checking out

I can see that all the tests have passed, can this be considered enough to prove that there is no breaking change? (I am asking that because I'm having a few difficulties to build all the dependencies on my system)

I think that it looks good. For your own development workflow, I recommend using conda even for octave etc in your development workflow. Octave is already packaged on conda-forge as well as the xeus stack.

Than you for your nice words on my project! I must say however that is still very much a proof of concept and I'm experimenting with many things at the moment, integration with the xwidgets library is one of the next things I'll be checking out!

Making a xeus-octave is really something that was on our radar for some time. (I did some nights-and-weekend work towards scilab, but Scilab resisted a bit).

I can see that all the tests have passed, can this be considered enough to prove that there is no breaking change? (I am asking that because I'm having a few difficulties to build all the dependencies on my system)

I think that it looks good. For your own development workflow, I recommend using conda even for octave etc in your development workflow. Octave is already packaged on conda-forge as well as the xeus stack.

Than you for your nice words on my project! I must say however that is still very much a proof of concept and I'm experimenting with many things at the moment, integration with the xwidgets library is one of the next things I'll be checking out!

Making a xeus-octave is really something that was on our radar for some time. (I did some nights-and-weekend work towards scilab, but Scilab resisted a bit).

cc @JohanMabille if you want to have a look at the changes.

cc @JohanMabille if you want to have a look at the changes.

I recommend using conda even for octave etc in your development workflow. Octave is already packaged on conda-forge as well as the xeus stack.

Thank you for the suggestion, I have no experience with conda, but I'll give it a look. At the moment however I have no problem building with static linkage (the only problem was installing all the dependencies to test the non-static build) and I think it is enough for the development purposes, as I don't have to manage any dependency at the expense of having a bigger binary. Once the project is more mature I'll surely look at integrating it, as it seems to me that conda has become the main way of distributing software in this ecosystem.

I think that it looks good

I'll remove the draft marker, then.

Making a xeus-octave is really something that was on our radar for some time. (I did some nights-and-weekend work towards scilab, but Scilab resisted a bit).

Octave, too, is quite convoluted.. I remember however that there's a patch done a few years ago by some GSOC student that tried to implement a basic kernel if you're interested

I recommend using conda even for octave etc in your development workflow. Octave is already packaged on conda-forge as well as the xeus stack.

Thank you for the suggestion, I have no experience with conda, but I'll give it a look. At the moment however I have no problem building with static linkage (the only problem was installing all the dependencies to test the non-static build) and I think it is enough for the development purposes, as I don't have to manage any dependency at the expense of having a bigger binary. Once the project is more mature I'll surely look at integrating it, as it seems to me that conda has become the main way of distributing software in this ecosystem.

I think that it looks good

I'll remove the draft marker, then.

Making a xeus-octave is really something that was on our radar for some time. (I did some nights-and-weekend work towards scilab, but Scilab resisted a bit).

Octave, too, is quite convoluted.. I remember however that there's a patch done a few years ago by some GSOC student that tried to implement a basic kernel if you're interested

I will merge today. Leaving it open for a bit to give the occasion to @JohanMabille to comment!

I will merge today. Leaving it open for a bit to give the occasion to @JohanMabille to comment!

Thanks!

Thanks!


Padding to Each side test has an issue !

Challenge Add Different Padding to Each Side of an Element has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.84 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

margin

padding

padding

My codes are right but it doesn't seem accept it. Is it something worng from my side or this is a bug?

my bad . my code is wrong .


Remove unused methods in Archive.java which use Files stream in an unsafe way. [phab:D2111]

Created by danielmoy-google at 2018-01-04 23:28:36:

schroederc accepted this revision at 2018-01-04 23:30:37

danielmoy-google closed via commit 6e4afb0239a1720e8185f8b5df1fec981ad019d3 at 2018-01-04 23:31:33


Improve offside system

Got to find a way to make offside distance work without it gets called while that particular player had nothing to do with the play. Going to be hard but not impossible.

Passive offside turns into active offside if:

the player is inside the opponent penalty box
the player is closer than x units to the ball and the ball is moving slower than x units per second
the player collides with or shoots the ball


improvements on read me

Signed-off-by: Thalles Freitas<EMAIL_ADDRESS>

Codecov Report

Merging #3 (697b578) into main (28e5b1f) will decrease coverage by 7.56%.
The diff coverage is 40.74%.

@@            Coverage Diff             @@
##             main       #3      +/-   ##
==========================================
- Coverage   79.66%   72.09%   -7.57%
==========================================
  Files           1        1
  Lines          59       86      +27
==========================================
+ Hits           47       62      +15
- Misses          8       15       +7
- Partials        4        9       +5

Impacted Files
Coverage Δ

helm/helm.go
72.09% <40.74%> (-7.57%)
:arrow_down:

Continue to review full report at Codecov.

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


mat-table-filter bugfix and enhancement

Primitive array support as well as handling 'false'

Many thanks for your help.
I'm really sorry to be late about this. I've actually implemented a solution with loadash providing some more features, I just couldn't find the time to publish and commit it. That's why I have to close this pull request this time. I'd be appriciated if you keep up the good work :)

Thanks again for your effort. Appearantly I have to override it all since Ive gone for some more changes along with other enhancements. Thats the reason Im closing this PR. Ive committed the new features in ng6-7 branch they will be available for master soon.


Bump to PHPStan 0.12

Fixes #91

[x] Need to test schema of extension.neon to resolve Unexpected option 'parameters › drupalServiceMap', 'parameters › entityTypeStorageMapping'.
[x] Configurations for testing PHPStan analysis rules are not running 😬
[ ] Document breaking config changes (no more root drupal:, under parameters
[x] ServiceDynamicReturnTypeExtension is broken

Okay. So this works when I run the test with Xdebug. Otherwise it fails. 🤷♂

I've sent you a PR with a couple of minor things :) https://github.com/mglaman/phpstan-drupal/pull/99
The first commit really makes the extension work - without it, user wouldn't be able to use the extension without defining drupal_root parameter.


about cifar10 download

hi, thanks for your works. I cannot download the tar.gz files about cifar10, could you please send me the cifar10 datasets for training and test?
Thank you. My email is<EMAIL_ADDRESS>

@ZJiaQi thanks. The file is too big to be sent over email. Could you try to download it again? What is the problem you're having with download?

Thanks for your answer, this problem was solving. But I have a new question. As for  the imagespace task, how could it output multi labels(such as multi words)?

Yeah, more information about imagespace! Looks very interesting!

@ZJiaQi Hi, thanks for asking. Could you clarify on "multi labels (multi words)"? Do you mean that your label contains multiple words, or that an image can be of multi labels? Could you give me an example? Thanks.


chore: runtime upgrade 1.25.4

The Pr changes the following

[x] bump spec_version
[ ] Bench marking
[x] Tested with chopsticks
[ ] Tested on testnet
[ ] Tag version

/run_benchmark interlay

/run_benchmarks interlay

/run_benchmark kintsugi

/run_benchmarks

Closing as benchmarking bot not working, as weights have already been updated and push.


Ways to identify schema changes

While using stand-alone exporter, keeping target database's credential in the config files may be restricted for some clusters. Are there any ways to identify schema changes other than connecting to the database using native transport protocol?

JMXHarvester doing refresh of MBean for every 30 minutes  which will take care of reloading the MBeans of new tables and removal of MBeans of deleted tables.


Paper trading in sandbox

There seems to be a sandbox env for api, how can we make use of it to paper trade? or at least test out the API before live trading?
https://developer.schwab.com/user-guides/apis-and-apps/test-in-sandbox

The sandbox does not appear to support paper trading. It's just to verify that all API calls are placed correctly.


runtime: Cancel tests after timeout

This change causes stalling unit tests to fail after 3/30 minutes (banshee/RTL).

Why would some tests suddenly stop with Error: The operation was canceled.?

That is a good question. Maybe because GitHub sees that there is already a CI test failing and therefore killing the other one to free the resources?

That is a good question. Maybe because GitHub sees that there is already a CI test failing and therefore killing the other one to free the resources?

Time to fix the failing tests then ;)


strings-ansi gem version conflict with other latest tty gems

Are you in the right place?

For issues or feature requests file a GitHub issue in this repository
For general questions or discussion post in Gitter

Describe the problem
A brief description of the issue/feature.
Hi, I tried using tty-progressbar in a project of mine and mix it with another project using the latest versions of tty-markdown and tty-prompt, and a gem conflict occurred that forced me to downgrade them to accommodate strings-ansi '~> 0.1.0' (from 0.2)
I just saw you have changed the dependency to `~> 0.2', which would resolve my issue.
My only question is when will you be making the next release? And, if not soon, would you be able to make a quick patch release in the meantime with only that dependency change?
Describe your environment

OS version: Mac Catalina
Ruby version: Ruby 2.7.1 and JRuby <IP_ADDRESS>
TTY::ProgressBar version: 0.17.0

Thanks for posting this issue. I'm aware of this and it's on my list. The two remaining tty gems that need upgrading is this one and tty-command. I'm waiting for a feature review of the indeterminate progress and plan to release a new version this coming weekend.

I just hit this again, can't use tty-table and this at the same time :(

@dkowis There will be a release soon. The tty-progressbar is the last remaining gem from tty to update but I need to get the API right. The indeterminate progress feature is in, I just added :bar_format for choosing preconfigured bar displays. The last thing that remains to do is to get pausing/resuming behaviour for multi bars working https://github.com/piotrmurach/tty-progressbar/issues/37. All the tty gems took few months to update but going forward the process will be much smoother.

Released v0.18.0. Definitely the biggest release so far. This version is feature-packed, see changelog. Enjoy!

Released v0.18.0. Definitely the biggest release so far. This version is feature-packed, see changelog. Enjoy!


Improve CAPA upgrade suite reliability

What this PR does
Alertnative to https://github.com/giantswarm/cluster-test-suites/pull/339, just with less changes.
Added

[!NOTE]
Currently before we upgrade the cluster, we just check if the nodes are ready. Just checking the nodes is IMO far from enough, and below additions are the bare minimum we should add now (meaning more checks should be added in addition to these two below).

Test workload cluster's Deployments, DaemonSets, StatefulSets and Pods before upgrading the cluster because we test these after the upgrade, so we should make sure that they worked before the upgrade, as the upgrade can impact them.
Test if cluster is ready before upgrading the cluster, i.e. check if Cluster resource has Ready condition with status True. When it comes to Cluster API, this is sort of a quick catch-all test, as Ready condition is a summary of all other conditions in CAPI and CAPA resources, so it is a quick check to verify if something is not ready in the cluster. In case Ready condition has a status False, that means that some fundamental part of the cluster is not ready, and therefore we should know that and wait for it to get ready before upgrading the cluster.

Changed

Increase node pool min size from 2 to 3 for CAPA upgrade test.

Removed

Remove node checks from upgrade because we already check nodes in common tests after the upgrade.

Checklist

[x] Update changelog in CHANGELOG.md.

Trigger e2e tests

/run cluster-test-suites

This was not enough, when running tests locally, the upgrade site fails because kyverno was either still not fully installed, or it got messed up somehow during the upgrade.
This is from the upgrade suite logs:
  {"level":"info","ts":"2024-06-17T01:00:46+02:00","msg":"App status for 't-l4obbvm821ejht90ry-kyverno' is not yet as expected: expectedStatus='deployed' actualStatus='pending-install' (reason: 'Initial install underway')"}

Will add also App CRs tests.

After just re-running the tests again locally, without any changes to this PR here:
All Wc workload passed tests before the upgrade, Deployments, StatefulSets, DaemonmSets and Pods, all ready/running/completed.
New cluster version is applied and the upgrade starts.
At that moment, this is the state of the App CRs in the MC:
kubectl get app -n org-t-jkxy3x249u50kcdutq
NAME                                                INSTALLED VERSION                                 CREATED AT   LAST DEPLOYED   STATUS
t-6a4p97in38waqz7q3a                                0.78.2                                            23m          15m             deployed
t-6a4p97in38waqz7q3a-app-operator                   6.11.0-0cb0cbfa7a70d2dcc4e372d23c8a23f05fd12bda   15m          15m             deployed
t-6a4p97in38waqz7q3a-aws-ebs-csi-driver-smons                                                         15m
t-6a4p97in38waqz7q3a-aws-pod-identity-webhook                                                         15m
t-6a4p97in38waqz7q3a-capi-node-labeler              0.5.0                                             15m          8m23s           deployed
t-6a4p97in38waqz7q3a-cert-exporter                                                                    15m
t-6a4p97in38waqz7q3a-cert-manager                   3.7.6                                             15m          2m19s           deployed
t-6a4p97in38waqz7q3a-chart-operator                 3.2.1                                             15m          8m12s           deployed
t-6a4p97in38waqz7q3a-chart-operator-extensions      1.1.2                                             15m          2m1s            deployed
t-6a4p97in38waqz7q3a-cilium-servicemonitors         0.1.2                                             15m          103s            deployed
t-6a4p97in38waqz7q3a-cluster-autoscaler             1.27.3-gs9                                        15m          103s            deployed
t-6a4p97in38waqz7q3a-etcd-k8s-res-count-exporter                                                      15m
t-6a4p97in38waqz7q3a-external-dns                   3.1.0                                             15m          2m51s           deployed
t-6a4p97in38waqz7q3a-grafana-agent                  0.4.3                                             5m53s        5m46s           deployed
t-6a4p97in38waqz7q3a-irsa-servicemonitors                                                             15m
t-6a4p97in38waqz7q3a-k8s-audit-metrics              0.9.0                                             15m          83s             deployed
t-6a4p97in38waqz7q3a-k8s-dns-node-cache                                                               15m
t-6a4p97in38waqz7q3a-kube-prometheus-stack          9.1.2                                             5m53s        2m              deployed
t-6a4p97in38waqz7q3a-kyverno                        0.17.13                                           3m52s        3m20s           deployed
t-6a4p97in38waqz7q3a-kyverno-policies                                                                 3m52s
t-6a4p97in38waqz7q3a-kyverno-policy-operator                                                          3m52s
t-6a4p97in38waqz7q3a-metrics-server                                                                   15m
t-6a4p97in38waqz7q3a-net-exporter                   1.19.0                                            15m          2m42s           deployed
t-6a4p97in38waqz7q3a-node-exporter                                                                    15m
t-6a4p97in38waqz7q3a-observability-bundle           1.3.4                                             15m          5m53s           deployed
t-6a4p97in38waqz7q3a-prometheus-agent               0.6.9                                             5m53s        2m44s           deployed
t-6a4p97in38waqz7q3a-prometheus-blackbox-exporter   0.4.1                                             15m          2m42s           deployed
t-6a4p97in38waqz7q3a-prometheus-operator-crd        9.0.0                                             5m53s        5m48s           deployed
t-6a4p97in38waqz7q3a-promtail                       1.5.3                                             5m53s        2m44s           deployed
t-6a4p97in38waqz7q3a-security-bundle                1.7.0                                             15m          3m52s           deployed
t-6a4p97in38waqz7q3a-teleport-kube-agent            0.9.0                                             15m          8m23s           deployed
t-6a4p97in38waqz7q3a-vertical-pod-autoscaler        5.2.2                                             15m          2m42s           deployed

So either app-operator is slow to update the App CRs here, or all Deployments, StatefulSets, DaemonmSets and Pods being ready/running/completed is not enough and something else is not yet done for the apps. So we probably need to add also default apps check here.
And some 3-4 minutes after the upgrade has already started, all App CRs look fine:
kubectl get app -n org-t-jkxy3x249u50kcdutq
NAME                                                INSTALLED VERSION                                 CREATED AT   LAST DEPLOYED   STATUS
t-6a4p97in38waqz7q3a                                0.78.2-db7ea9b54f773193700df6dcc648d4a99bb19600   27m          3m51s           deployed
t-6a4p97in38waqz7q3a-app-operator                   6.11.0-0cb0cbfa7a70d2dcc4e372d23c8a23f05fd12bda   20m          19m             deployed
t-6a4p97in38waqz7q3a-aws-ebs-csi-driver-smons       0.1.0                                             20m          3m29s           deployed
t-6a4p97in38waqz7q3a-aws-pod-identity-webhook       1.16.0                                            20m          3m44s           deployed
t-6a4p97in38waqz7q3a-capi-node-labeler              0.5.0                                             20m          12m             deployed
t-6a4p97in38waqz7q3a-cert-exporter                  2.9.0                                             20m          3m46s           deployed
t-6a4p97in38waqz7q3a-cert-manager                   3.7.6                                             20m          6m26s           deployed
t-6a4p97in38waqz7q3a-chart-operator                 3.2.1                                             20m          12m             deployed
t-6a4p97in38waqz7q3a-chart-operator-extensions      1.1.2                                             20m          6m8s            deployed
t-6a4p97in38waqz7q3a-cilium-servicemonitors         0.1.2                                             20m          5m50s           deployed
t-6a4p97in38waqz7q3a-cluster-autoscaler             1.27.3-gs9                                        20m          5m50s           deployed
t-6a4p97in38waqz7q3a-etcd-k8s-res-count-exporter    1.10.0                                            20m          3m50s           deployed
t-6a4p97in38waqz7q3a-external-dns                   3.1.0                                             20m          6m58s           deployed
t-6a4p97in38waqz7q3a-grafana-agent                  0.4.3                                             10m          9m53s           deployed
t-6a4p97in38waqz7q3a-irsa-servicemonitors           0.0.1                                             20m          3m27s           deployed
t-6a4p97in38waqz7q3a-k8s-audit-metrics              0.9.0                                             20m          5m30s           deployed
t-6a4p97in38waqz7q3a-k8s-dns-node-cache             2.6.2                                             20m          3m36s           deployed
t-6a4p97in38waqz7q3a-kube-prometheus-stack          9.1.2                                             10m          6m7s            deployed
t-6a4p97in38waqz7q3a-kyverno                        0.17.13                                           7m59s        7m27s           deployed
t-6a4p97in38waqz7q3a-kyverno-policies               0.20.2                                            7m59s        2m30s           deployed
t-6a4p97in38waqz7q3a-kyverno-policy-operator        0.0.7                                             7m59s        2m5s            deployed
t-6a4p97in38waqz7q3a-metrics-server                 2.4.2                                             20m          3m47s           deployed
t-6a4p97in38waqz7q3a-net-exporter                   1.19.0                                            20m          6m49s           deployed
t-6a4p97in38waqz7q3a-node-exporter                  1.19.0                                            20m          3m35s           deployed
t-6a4p97in38waqz7q3a-observability-bundle           1.3.4                                             20m          10m             deployed
t-6a4p97in38waqz7q3a-prometheus-agent               0.6.9                                             10m          6m51s           deployed
t-6a4p97in38waqz7q3a-prometheus-blackbox-exporter   0.4.1                                             20m          6m49s           deployed
t-6a4p97in38waqz7q3a-prometheus-operator-crd        9.0.0                                             10m          9m55s           deployed
t-6a4p97in38waqz7q3a-promtail                       1.5.3                                             10m          6m51s           deployed
t-6a4p97in38waqz7q3a-security-bundle                1.7.0                                             20m          7m59s           deployed
t-6a4p97in38waqz7q3a-teleport-kube-agent            0.9.0                                             20m          12m             deployed
t-6a4p97in38waqz7q3a-vertical-pod-autoscaler        5.2.2                                             20m          6m49s           deployed

And it CAPA upgrade suite failed again when re-ran, but with a different error.
This time the worker nodes did not come up.
The cluster had 2 nodes after the upgrade, and as the test was running it went down to just 1 node.
Basic upgrade test basic has all the worker nodes running
/Users/nikola/workspaces/giantswarm/e2e-tests/cluster-test-suites/internal/common/basic.go:62
  {"level":"info","ts":"2024-06-17T02:10:19+02:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2024-06-17T02:10:19+02:00","msg":"2 nodes ready, expecting between 3 and 5"}
  ...
  {"level":"info","ts":"2024-06-17T02:15:50+02:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2024-06-17T02:15:51+02:00","msg":"2 nodes ready, expecting between 3 and 5"}
  {"level":"info","ts":"2024-06-17T02:16:06+02:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2024-06-17T02:16:06+02:00","msg":"1 nodes ready, expecting between 3 and 5"}
  {"level":"info","ts":"2024-06-17T02:16:21+02:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2024-06-17T02:16:21+02:00","msg":"1 nodes ready, expecting between 3 and 5"}
  ...
  {"level":"info","ts":"2024-06-17T02:24:52+02:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2024-06-17T02:24:53+02:00","msg":"1 nodes ready, expecting between 3 and 5"}
  {"level":"info","ts":"2024-06-17T02:25:08+02:00","msg":"Checking for ready nodes"}
  {"level":"info","ts":"2024-06-17T02:25:08+02:00","msg":"1 nodes ready, expecting between 3 and 5"}
  [FAILED] in [It] - /Users/nikola/workspaces/giantswarm/e2e-tests/cluster-test-suites/internal/common/basic.go:73 @ 06/17/24 02:25:14.778
• [FAILED] [900.477 seconds]
Basic upgrade test basic [It] has all the worker nodes running
/Users/nikola/workspaces/giantswarm/e2e-tests/cluster-test-suites/internal/common/basic.go:62

  [FAILED] Timed out after 900.001s.
  Expected success, but got an error:
      <*errors.errorString | 0x14000f2d190>:
      unexpected number of nodes
      {
          s: "unexpected number of nodes",
      }
  In [It] at: /Users/nikola/workspaces/giantswarm/e2e-tests/cluster-test-suites/internal/common/basic.go:73 @ 06/17/24 02:25:14.778

Test passed on the 3rd test run, but not sure if I should trust it 🙈

Will update this PR by removing changes from other merged smaller PRs.

Rebased PR after merging other smaller PRs. Will re-test this now.

/run cluster-test-suites

/run cluster-test-suites

/run cluster-test-suites

Local test run of upgrade suite failed as apps were not deployed before doing the upgrade:
  {"level":"info","ts":"2024-06-19T16:05:17+02:00","msg":"App status for 't-9c04xu14g2485ge7ep-kyverno' is not yet as expected: expectedStatus='deployed' actualStatus='pending-upgrade' (reason: 'Preparing upgrade')"}

So I would say the changes here are working like a charm 😄


Compile to wasm and deploy to GitHub Pages

Done in https://github.com/ringsaturn/tzf-web/releases/tag/v0.1.0


NPE from createCompletionAvailableSuggestionsNotification (SDK version 2.2.0-edge. ...)

Analyzer Feedback from IntelliJ
Version information

IDEA IC-191.6707.61
2.2.0-edge.0a7dcf17eb5f2450480527d6ad1e201fb47f1e36
IC-191.6707.61, JRE 1.8.0_202-release-1483-b44x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.14.4, screens 1440x900, 2560x1080  Retina

Exception
Dart analysis server, SDK version 2.2.0-edge.0a7dcf17eb5f2450480527d6ad1e201fb47f1e36, server version 1.23.0, error: Failed to handle completion domain request: {id: 2, method: completion.setSubscriptions, params: {subscriptions: [AVAILABLE_SUGGESTION_SETS]}, clientRequestTime:<PHONE_NUMBER>494}
NoSuchMethodError: The method 'map' was called on null.
Receiver: null
Tried calling: map<AvailableSuggestion>(Closure: (Declaration) => AvailableSuggestion)
#0      Object.noSuchMethod (dart:core/runtime/libobject_patch.dart:50:5)
#1      createCompletionAvailableSuggestionsNotification.<anonymous closure> (package:analysis_server/src/domains/completion/available_suggestions.dart:85:30)
#2      MappedListIterable.elementAt (dart:_internal/iterable.dart:414:29)
#3      ListIterable.toList (dart:_internal/iterable.dart:219:19)
#4      createCompletionAvailableSuggestionsNotification (package:analysis_server/src/domains/completion/available_suggestions.dart:89:8)
#5      CompletionDomainHandler.setSubscriptions.<anonymous closure> (package:analysis_server/src/domain_completion.dart:383:11)
#6      _rootRunUnary (dart:async/zone.dart:1136:13)
#7      _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#8      _CustomZone.runUnaryGuarded (dart:async/zone.dart:931:7)
#9      _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336:11)
#10     _DelayedData.perform (dart:async/stream_impl.dart:591:14)
#11     _StreamImplEvents.handleNext (dart:async/stream_impl.dart:707:11)
#12     _PendingEvents.schedule.<anonymous closure> (dart:async/stream_impl.dart:667:7)
#13     _rootRun (dart:async/zone.dart:1120:38)
#14     _CustomZone.run (dart:async/zone.dart:1021:19)
#15     _CustomZone.runGuarded (dart:async/zone.dart:923:7)
#16     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:963:23)
#17     _rootRun (dart:async/zone.dart:1124:13)
#18     _CustomZone.run (dart:async/zone.dart:1021:19)
#19     _CustomZone.runGuarded (dart:async/zone.dart:923:7)
#20     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:963:23)
#21     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#22     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#23     _Timer._runTimers (dart:isolate/runtime/libtimer_impl.dart:391:30)
#24     _Timer._handleMessage (dart:isolate/runtime/libtimer_impl.dart:416:5)
#25     _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:171:12)

For additional log information, please append the contents of
file:///private/var/folders/my/lqgvw_xj0dd8p6lzxcj_jy7w0000gn/T/report.txt.

Thanks for reporting this issue! This was previously reported at https://github.com/dart-lang/sdk/issues/36623; please follow along there.

Duplicate of https://github.com/dart-lang/sdk/issues/36623