Status Bar No Longer Clickable

Type: Bug
This morning when I opened VSCode, it installed the most recent version update and since then, the status bar at the bottom of the window is o longer clickable. The icons seem to have no actions associated with them.

Expected Results:

Open VSCode using code <directory>/ call
Using git control features on the lefthand side of the status bar, view branches within the current repository

Actual Results:

Open VSCode using code <directory>/ call
Click on git control features on the lefthand side of the status bar, and nothing happens.
Hover over git control features on the lefthand side of the status bar, and nothing happens.
Try to click on other icons usually available to click previously, and nothing happens.

VS Code version: Code 1.82.3 (fdb98833154679dbaa7af67a5a29fe19e55c2b73, 2023-10-02T10:51:22.294Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Remote OS version: Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2
Extensions (23)

Extension
Author (truncated)
Version

better-comments
aar
3.0.2

jupyter-keymap
ms-
1.1.2

remote-containers
ms-
0.309.0

remote-ssh
ms-
0.106.4

remote-ssh-edit
ms-
0.86.0

remote-wsl
ms-
0.81.7

remote-explorer
ms-
0.4.1

EditorConfig
Edi
0.16.4

rainbow-csv
mec
3.7.1

vscode-docker
ms-
1.26.1

black-formatter
ms-
2023.4.1

flake8
ms-
2023.6.0

isort
ms-
2023.10.1

pylint
ms-
2023.6.0

python
ms-
2023.16.0

vscode-pylance
ms-
2023.9.30

jupyter
ms-
2023.8.1002501831

jupyter-keymap
ms-
1.1.2

jupyter-renderers
ms-
1.0.17

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

live-server
ms-
0.4.9

git-prefix
srm
1.3.2

Wanted to leave an update:
As of today, 10/04/2023, the status bar seems to be working again. Not sure the issue that caused it yesterday.

My biggest apologies, after working a little I realized that the status bar only seems to be working if that section of the VSCode window is above the bottom 1/10th of my screen.
When window above certain spot, status bar is clickable and hover tool tips appear:

When window below certain spot, no window resizing happen, window was simply moved down. Status bar becomes unclickable and no hover happens.

Note: I did a delayed screenshot and so in both pictures, my mouse was hovering over the far left side of the status bar. Unfortunately the screenshot did not capture the mouse.
It is possible that this is an issue with my machine but not sure as it has been happening for 2 days now.
I did attempt to close all my VSCode windows, and restart my WSL instance. VSCode installed an update but the result was the same.

I wasn't able to reproduce this in any windows version (tested 10 and 11). This may be an issue with your OS or your machine?
Does this issue happen when in full screen or only when windowed and at the bottom left?

Hmm definitely could be an issue with my machine.
It was happening in:

windowed mode (with window at bottom of screen)
Maximized window

I just tested Full Screen/Zen Mode and the issue is NOT happening in that mode.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

I've had the same problem a couple of times both on Windows 10 and Windows 11 on two different laptops, it seems to be a problem in windows explorer that misunderstands how big its taskbar is and it is stealing clicks from whatever is actually there. Killing and restarting explorer.exe solved the problem for me.
My assumption is that this probably has something to do with different UI scaling on my main monitor and laptop screen and waking from sleep.

My assumption is that this probably has something to do with different UI scaling on my main monitor and laptop screen and waking from sleep.

This sounds most likely as to what was happening. I do not believe the issue I experienced had anything to do with VSCode in the end


[Feature Request] Main dashboard  with all pages and their status

Hello,
Is it possible to create main dashboard  with all configured pages and their current status? If any of the monitor checks configured on a particular page is different than green it should be visible on that dashboard as well.
Thanks to that it would be quite easy to monitor all pages all at once and react instead of clicking on each page separately and checking if everything is OK.
I used current pages overview just to show my idea

i am not sure i understand your mind. did you wanna display a overview status in page list?

Yes, i've got ~ 20 applications that i need to monitor. For each application i want to create separate page with 4-5 monitoring checks. I would like to use page list as a main monitoring page where i can easily check if all my apps are working fine or not. If not then i can click on particular page with yellow/red status to check what's wrong.


Is is possible to return a function from bridge class method??

So, I have bridge class inside I have method called load that returns a load object which is a wrapper class inside of it I have a field called loadMoreData which is of type void function(String) this returns Future object.
Now, can i return this class and invoke the function.
I tried it and it didn't work so thought I might be doing something wrong.

It should be possible. Depending on how it is invoked you will either have to use $Function or $Closure so I would try them both. I'd need to see an example of the code to give more specific advice.

Closing this because it is possible.
static const __$static$method$lazy = $Function(_$static$method$lazy);
  static $Value? _$static$method$lazy(
      Runtime runtime, $Value? target, List<$Value?> args) {
    final builder = args[0] as EvalCallable;
    final $result = Movie.lazy(
      () => (builder.call(runtime, null, [])?.$value as Future)
          .then((value) => value as Movie),
    );
    return $LazyContent.wrap($result);
  }


Clean up brand colors in colors.xml

Description
MA-2576
Every color now comes from the color palette (edx_*) except:

greys
"offline bar" (deprecated)
error bar (deprecated, will use snackbars eventually)

Things to test

The download progress in the action bar is now a standard green
The download progress bar in the download list is now a standard green
The error text / error progress bar in the download list is now standard reds
Text links now just use brand base color (which is what happens on edx.org)
Edit/Cancel/Delete buttons now use a ripple instead of brand highlight

Reviewers
If you've been tagged for review, please check your corresponding box once you've given the :+1:.

[ ] Code review: @BenjiLee
[ ] Code review: @mdinino

IIRC we didn't want to go through and fix all the grays just yet (lot of work to make sure the color palette colors work).
But, I did check the colors I swapped here and I think they look good.

@@             master       #781   diff @@
==========================================
  Files           486        486
  Lines         19989      19989
  Methods           0          0
  Messages          0          0
  Branches       2821       2821
==========================================
  Hits           3688       3688
  Misses        15887      15887
  Partials        414        414

Review #781 on Codecov

Powered by Codecov. Last update e80e6b2...6fce090

Checking link failing CI here https://github.com/edx/edx-app-android/pull/783

I don't see the ripple on the edit/cancel/delete.

Why do we have 50 greys -.-

I don't see the ripple on the edit/cancel/delete.

It's there. What API level are you testing on?

👍

:+1


Oil extractors stop working when mod installed

When this mod is installed oil extractors don't extract to belts and just sit on "product overflow". I've confirmed this by only using this mod and required dependent mods. Is it possible I've got one of your mod's settings that's causing this, or is it a bug?

There are many mods in this repo. You should specify which mod you install and what options you enable.

I apologize, I thought I was in the CheatEnabler repository. I had a lot of things adjusted in the mod, so I deleted the config file and tried it again. After I did this the issue disappeared. I re-enabled several settings but it did not re-create the problem. So you can close this, but please be aware that you have a conflict somewhere. Sorry I couldn't help track it down, but if I encounter it again I'll let you know. Thanks for the quick response and for all the great mods!

I'd think you have enabled the option: Protect veins from exhaustion.
Check README.md for its use.


[SR-2469] New uuid-dev requirement missing from swift.org

Previous ID
SR-2469

Radar
None

Original Reporter
@hpux735

Type
Bug

Additional Detail from JIRA

Votes
0

Component/s

Labels
Bug

Assignee
None

Priority
Medium

md5: 9d792302c321af8c39a381fb50ff9f42

Issue Description:
On Linux uuid-dev is new required for installing from binaries. This requirement is missing from swift.org.

I think this issue can be closed


Cannot install via Pip neither Miniconda.

i have Windows 11, Python 3.11, cuda 12.4, so at the moment of installing :
pip install nnabla_ext_cuda120 nnabla-converter
it gives :
"ERROR: Could not find a version that satisfies the requirement nnabla_ext_cuda120 (from versions: none)
ERROR: No matching distribution found for nnabla_ext_cuda120"
installing via miniconda :
conda install nnabla_ext_cuda120 nnabla-converter
yields :
Retrieving notices: ...working... done
Channels:

defaults
Platform: win-64
Collecting package metadata (repodata.json): done
Solving environment: failed

PackagesNotFoundError: The following packages are not available from current channels:

nnabla_ext_cuda120
nnabla-converter

Current channels:

defaults

To search for alternate channels that may provide the conda package you're
looking for, navigate to
https://anaconda.org

and use the search bar at the top of the page.
please help

Thank you for creating this issue.
We're very sorry but currently we are supporting python3.8, 3.9 and 3.10 only.
So, we don't provide packages for python3.11.

https://pypi.org/project/nnabla/#files
https://pypi.org/project/nnabla-ext-cuda120/#files

Sorry for inconvenience.

Ok don't worry, My Bad..... So....
Please add support for Python 3.11

Thank you for your request.
EOL for python3.8 is the end of October, so we will change supported versions.
But, it will take some time, and I think the next release (1.39.0) will have the same supported versions as before.


Remote Config Dynamic Property Wrapper

Added the new API that enables developers to define a property wrapper that listens to a remote config key value. When remote config is activated, the UI component will automatically reflect the activated value.

In addition to fixing CI, Changelog should be updated for the release notes

It is strange that I already ran swift-format  on those files but they still produce errors, I wonder our CI is using a different build.

Ignore the test failure since it's something we need to fix in the infra.

Hi @chliangGoogle, I re-ran 40804aa's CI and PTAL at the results here:
https://github.com/firebase/firebase-ios-sdk/actions/runs/3084312372/jobs/5019355333
The 429 errors are gone, but there are 4 failures. Are these the failures you've been seeing?


Added interface for GDNative Videodecoder.

Interface and callback api added for Videodecoder support.
Should be able to construct any format videodecoder using
only the given interface.
GSoC 2018 project.

All changes made.

@TMM @karroffel: could you review again?

@tmm @karroffel: could you review again?

Bump :)

GDNative side is still looking good :+1:

@hpvb Can you check this one again? @karroffel says it's good from the GDNative end, is it also good on the feature/video decoding end?

Includes have been changed, so the pull request doesn't compile on master.

diff --git a/modules/gdnative/videodecoder/register_types.cpp b/modules/gdnative/videodecoder/register_types.cpp
index 64599365e..dfb1966a7 100644
--- a/modules/gdnative/videodecoder/register_types.cpp
+++ b/modules/gdnative/videodecoder/register_types.cpp
@@ -28,7 +28,7 @@
/* SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.                /
/************************************************************************/
-#include "class_db.h"
+#include "core/class_db.h"
#include "resource_importer_av_gdnative.h"
#include "video_stream_gdnative.h"
diff --git a/modules/gdnative/videodecoder/resource_importer_av_gdnative.cpp b/modules/gdnative/videodecoder/resource_importer_av_gdnative.cpp
index ff9f6118f..7fe8cc89d 100644
--- a/modules/gdnative/videodecoder/resource_importer_av_gdnative.cpp
+++ b/modules/gdnative/videodecoder/resource_importer_av_gdnative.cpp
@@ -30,8 +30,8 @@
#include "resource_importer_av_gdnative.h"
-#include "io/resource_saver.h"
-#include "os/file_access.h"
+#include "core/io/resource_saver.h"
+#include "core/os/file_access.h"
#include "scene/resources/texture.h"
String ResourceImporterAVGDNative::get_importer_name() const {
diff --git a/modules/gdnative/videodecoder/video_stream_gdnative.cpp b/modules/gdnative/videodecoder/video_stream_gdnative.cpp
index a959a4c8a..2e2c400d5 100644
--- a/modules/gdnative/videodecoder/video_stream_gdnative.cpp
+++ b/modules/gdnative/videodecoder/video_stream_gdnative.cpp
@@ -29,7 +29,7 @@
/*************************************************************************/
#include "video_stream_gdnative.h"
-#include <project_settings.h>
+#include <core/project_settings.h>
#include <servers/audio_server.h>
VideoDecoderServer *VideoDecoderServer::instance = NULL;
diff --git a/modules/gdnative/videodecoder/video_stream_gdnative.h b/modules/gdnative/videodecoder/video_stream_gdnative.h
index d203a5d04..ee9410e3c 100644
--- a/modules/gdnative/videodecoder/video_stream_gdnative.h
+++ b/modules/gdnative/videodecoder/video_stream_gdnative.h
@@ -32,7 +32,7 @@
#define VIDEO_STREAM_GDNATIVE_H
#include <modules/gdnative/gdnative.h>
-#include <os/file_access.h>
+#include <core/os/file_access.h>
#include <scene/resources/texture.h>
#include <scene/resources/video_stream.h>

I rebased and pushed a new commit to this PR to fix includes, some style issues and a compile warning.
There's one thing left to do before merging though, as VideoStreamGDNative was based off VideoStream{Theora,Webm} as some point in the past and lacks bug fixes done recently: #19937 and #21084.

There's one thing left to do before merging though, as VideoStreamGDNative was based off VideoStream{Theora,Webm} as some point in the past and lacks bug fixes done recently: #19937 and #21084.

I've done the relevant work in akien-mga@dbb5cb6
I'm not adding it to this PR yet as I think the crash reported above should be investigated first.

Now that the crash is fixed, I've added this to this PR too: 72feccf20.
Still untested with the actual GDNative plugin as I'm not sure how to use it :)

Now that the crash is fixed, I've added this to this PR too: 72feccf.
Still untested with the actual GDNative plugin as I'm not sure how to use it :)

Well, got a crash(*) with this commit and the https://github.com/KidRigger/godot-videodecoder test project, so I'll remove it for now until we get things working with the original state. (PR back to 012dac9.)
I can't get the test project to load though with 012dac9, I get this error:
ERROR: _load: No loader found for resource: res://samples/big_buck_bunny.mp4
   At: core/io/resource_loader.cpp:192.
ERROR: _load: No loader found for resource: res://samples/big_buck_bunny.mp4
   At: core/io/resource_loader.cpp:192.
WARNING: _parse_ext_resource: Couldn't load external resource: res://samples/big_buck_bunny.mp4
   At: scene/resources/scene_format_text.cpp:174.
ERROR: remove_scene: Index p_idx=1 out of size (edited_scene.size()=1)
   At: editor/editor_data.cpp:564.

I did build the Linux .so with scons platform=linux.

 Are you missing the Samples module in the test folder?
If not then this issue is new and unknown. I'll catch up to all the changes and get back to this issue.

I can't get the test project to load though with 012dac9

Test project needs the samples downloaded. Are you missing the Samples module in the test folder?

I did forget to pull the submodule, I'll try again. Might be worth mentioning it in the repo's README.md, Git is not very explicit about the existence of submodules when you clone a repo.

Tested again with 012dac9 and the properly checked out samples, I now get a crash when opening the editor:
ctor()
set_audio_track()
open_file()
QuickTime / MOV

Thread 1 "godot-git" received signal SIGSEGV, Segmentation fault.
godot_videodecoder_open_file (p_data=0xc6d5d30, file=0xfa239a0) at src/gdnative_videodecoder.c:414
414                     if (data->format_ctx->streams[i]->codecpar->codec_type == AVMEDIA_TYPE_VIDEO) {

(gdb) bt
#0  godot_videodecoder_open_file (p_data=0xc6d5d30, file=0xfa239a0) at src/gdnative_videodecoder.c:414
#1  0x000000000123cfb4 in VideoStreamPlaybackGDNative::open_file (this=0x63d9920, p_file=...) at modules/gdnative/videodecoder/video_stream_gdnative.cpp:118
#2  0x000000000123de52 in VideoStreamGDNative::instance_playback (this=0xcf8f670) at modules/gdnative/videodecoder/video_stream_gdnative.cpp:322
#3  0x00000000026a9b9c in VideoPlayer::set_stream (this=0xfa1cda0, p_stream=...) at scene/gui/video_player.cpp:209
#4  0x00000000026af957 in MethodBind1<Ref<VideoStream> const&>::call (this=0x593a330, p_object=0xfa1cda0, p_args=0x7fffffffbcb8, p_arg_count=1, r_error=...)
    at ./core/method_bind.gen.inc:729
#5  0x00000000030817c5 in ClassDB::set_property (p_object=0xfa1cda0, p_property=..., p_value=..., r_valid=0x7fffffffbecf) at core/class_db.cpp:1020
#6  0x00000000030f99d8 in Object::set (this=0xfa1cda0, p_name=..., p_value=..., r_valid=0x7fffffffbecf) at core/object.cpp:422
#7  0x0000000002ba4577 in SceneState::instance (this=0x61c3060, p_edit_state=SceneState::GEN_EDIT_STATE_MAIN) at scene/resources/packed_scene.cpp:252
#8  0x0000000002baeaf6 in PackedScene::instance (this=0xfa177d0, p_edit_state=PackedScene::GEN_EDIT_STATE_MAIN) at scene/resources/packed_scene.cpp:1697
#9  0x0000000001c5a27e in EditorNode::load_scene (this=0x65c89b0, p_scene=..., p_ignore_broken_deps=false, p_set_inherited=false, p_clear_errors=true, p_force_open_imported=false)
    at editor/editor_node.cpp:2919
#10 0x0000000001c43fb6 in EditorNode::_sources_changed (this=0x65c89b0, p_exist=false) at editor/editor_node.cpp:534
#11 0x0000000001336524 in MethodBind1<bool>::call (this=0xb29cde0, p_object=0x65c89b0, p_args=0x7fffffffc8c0, p_arg_count=1, r_error=...) at ./core/method_bind.gen.inc:729
#12 0x00000000030fc60d in Object::call (this=0x65c89b0, p_method=..., p_args=0x7fffffffc8c0, p_argcount=1, r_error=...) at core/object.cpp:945
#13 0x00000000030fde96 in Object::emit_signal (this=0x6d17380, p_name=..., p_args=0x7fffffffc8c0, p_argcount=1) at core/object.cpp:1231
#14 0x00000000030fe505 in Object::emit_signal (this=0x6d17380, p_name=..., p_arg1=..., p_arg2=..., p_arg3=..., p_arg4=..., p_arg5=...) at core/object.cpp:1287
#15 0x0000000001beb135 in EditorFileSystem::_notification (this=0x6d17380, p_what=17) at editor/editor_file_system.cpp:1102
#16 0x0000000001bf3488 in EditorFileSystem::_notificationv (this=0x6d17380, p_notification=17, p_reversed=false) at editor/editor_file_system.h:107
#17 0x00000000030fc78a in Object::notification (this=0x6d17380, p_notification=17, p_reversed=false) at core/object.cpp:955
#18 0x000000000247b96e in SceneTree::_notify_group_pause (this=0x5d92be0, p_group=..., p_notification=17) at scene/main/scene_tree.cpp:967
#19 0x00000000024796ec in SceneTree::idle (this=0x5d92be0, p_time=0.150000095) at scene/main/scene_tree.cpp:510
#20 0x00000000011d38ff in Main::iteration () at main/main.cpp:1862
#21 0x00000000011a8a29 in OS_X11::run (this=0x7fffffffd230) at platform/x11/os_x11.cpp:2821
#22 0x000000000119b38d in main (argc=2, argv=0x7fffffffd968) at platform/x11/godot_x11.cpp:55

Note that I'm compiling against system-installed ffmpeg 4.1.


Strata change possible?

would it be possible to change the strata so that the widget is not overlaying the top of regular game windows?

So right now, the widgets are attached to the ScreenText addon, since that's basically the only addon that is guaranteed to be enabled by any given user.  The problem is, as you see, that addon is always visible, and always on top haha.  I was planning to look into adding an option to attach the widgets to target bar, focus target bar, etc. addons at some point.  So the short answer to your question is probably, but don't expect anything immediately, as most of my free time is going to be going toward raid-related things for the next few weeks.

@cosmo-somebody I added options for this in version <IP_ADDRESS>.  It should be automatic when the plugin is updated, but you'll need to reset the positions of any widgets that you have, as binding to different UI elements means that the relative coordinates won't be the same anymore.  Sorry for the inconvenience.
Also, this plugin was accepted into Dalamud testing, so it's no longer on my third party repo.  Enable plugin testing in /xlsettings to get the current version once the PR gets merged.


Add tooltip to series title inline edit

When hovering over the series title, the cursor changes which is good, but there is no tooltip to give indication that you can edit. We should add a tooltip with the following copy:
"Click to edit the title of this series

"

Fixed in https://github.com/CUL-DigitalServices/grasshopper-ui/pull/306


Remove unused fields from KubernetesConfig/LinuxProfile

This PR removes all the fields that have never been referenced outside types.go for the struct KubernetesConfig and LinuxProfile

I may not have the full context about this task so I have a few questions about this:

How/what sets the default values for these removed fields from KubernetesConfig (before this PR)? I see that the fields are not referenced in the agentbaker code but are they used/set as defaults in rp?
Are we confident that these removed fields will not be used in the future? Or should we add them back in later when needed?
For KubernetesConfig, did you manually check each field to see if it was referenced elsewhere or needed to be removed? Or was there a faster way to do it?

Thanks in advance for answering the questions!


24 removed map

@Graur please review
I removed deprecated map  according to #24

@levBagryansky Please, restart github actions checks

@levBagryansky Please, restart github actions checks

@Graur done

@rultor merge

@rultor merge

@graur OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@graur Done! FYI, the full log is here (took me 6min)

@levBagryansky Thanks!


Unable to run wp-cypress on Circle CI

Describe the bug
When running wp-cypress on a circle CI build I get the following error:
`#!/bin/bash -eo pipefail
yarn run wp-cypress start
yarn run v1.22.5
warning package.json: No license field
$ /home/circleci/project/node_modules/.bin/wp-cypress start

Installing dependencies
wp-cypress ✔ Dependencies installed

Creating test container
wp-cypress ✔ Test container created

Waiting for database connection
wp-cypress ✔ Database connected

Creating wp-config.php
wp-cypress ✔ wp-config.php created

Creating database
wp-cypress ✔ Database created

Installing WordPress
wp-cypress ✔ WordPress installed

Activating plugins
wp-cypress ⚠ Warning: The 'wp-cypress' plugin could not be found.
Error: No plugins activated.

Creating default users
wp-cypress ✖ Error: 'seed' is not a registered wp command. See 'wp help' for available commands.

See logs for more info<EMAIL_ADDRESS>error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.`
To Reproduce
https://github.com/danrhjones/wp-cypress-circleci
https://app.circleci.com/pipelines/github/danrhjones/wp-cypress-circleci/2/workflows/bbd9da79-0bc5-49c3-9010-ac7898178325/jobs/2
Expected behavior
I expect that wp-cypress should build the docker container and the tests should be able to be run

I have also tried using a machine executor and get a different error
https://app.circleci.com/pipelines/github/danrhjones/wp-cypress-circleci/24/workflows/c130d12e-041b-4b16-9d41-7549c00cab84/jobs/25
` Installing dependencies
wp-cypress ✔ Dependencies installed

Creating test container
wp-cypress ✔ Test container created
Waiting for database connection
wp-cypress ✔ Database connected
Creating wp-config.php
wp-cypress ✔ wp-config.php created
Creating database
wp-cypress ✔ Database created
Installing WordPress
wp-cypress ✔ WordPress installed
Activating plugins
wp-cypress ✔ Activated plugins
Creating default users
wp-cypress ✖ Error: "DefaultUsers" is not a seeder.

`

Hi @danrhjones
We are working on the issue and hope to have a fix today.
Thanks
Jason

Hi @danrhjones
Apologies for the delay on this. CircleCI poses a few issues if not using the machine option. We've made some changes which are yet to be released but you can use them by:
npm uninstall @bigbite/wp-cypress
npm install --save https://github.com/bigbite/wp-cypress.git\#feature/no-volumes

OR
yarn remove @bigbite/wp-cypress
yarn add https://github.com/bigbite/wp-cypress.git\#feature/no-volumes

I took your repo and made the change and confirm it runs: https://github.com/bigbite/wp-cypress-issue-42
As for the docker option on CircleCI it has two limitations, doesn't support volumes and it doesn't allow ports to be open between current docker image and remote docker (wp-cypress). In those changes mention above we added a --no-volumes flag to the start command yarn run wp-cypress start --no-volumes which allows wp-cypress to pass the point mentioned in your issue but there is no way to run the tests as cypress cannot access localhost. However it is not yet clear how to overcome the port issue yet but we will continue looking into it.
Thanks
Jason


Add some safeguards for appserver dependency

Our Appserver has a dependency on the JS/React SDKs as well, and is getting errors while trying to start because of the undefined window/navigator object. This PR fixes that issue.

[x] Add null check around window object
[x] Add null check around navigator object

Was able to come back and edit appserver dependencies before needing this. No longer necessary.


More accurate random

Original issue 379
"Hello,
Is it possible to make random/probability more accurate? 1% step would be perfect, 5% also, but 12.5% is pretty big step
Cheers"

min value is 1.6%


Revert "Set the TLS connection ServerName when the transport is created."

This commit is causing issues in Swarm. We don't need this change yet, so I rather revert it for the upcoming release.
This reverts commit 9eec4dc67b13ace4c3c34496089122b9f1f7c28e.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "revert_server_name_set" git@github.com:calavera/engine-api.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "revert_server_name_set" git@github.com:calavera/engine-api.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Arf :sweat:
LGTM 🐡

LGTM


Support for project references

Is your proposal related to a problem?
I'm using create-react-app for my React workshops. Each project has an exercise file (the unfinished code) and a final file (the finished code). I'm rewriting them all to TypeScript. I don't want to enable strict mode for the exercise files because it can be difficult for people new to TypeScript. However I do want the final version of the exercise to be type checked with strict mode (for my own sake).
Having different configs for different files in a project can be accomplished using project references configuration. Here's what I've done to make this "work": https://github.com/kentcdodds/react-fundamentals/commit/84eb9ed2f10a060898d115e768df77c8dc603d46
tsconfig.json
{
  "files": [],
  "references": [
    {"path": "config/tsconfig.exercise.json"},
    {"path": "config/tsconfig.final.json"}
  ]
}

config/tsconfig.exercise.json
{
  "extends": "./tsconfig.shared.json",
  "include": ["../src/exercise/"],
  "compilerOptions": {
    "strict": false
  }
}

config/tsconfig.final.json
{
  "extends": "./tsconfig.shared.json",
  "exclude": ["../src/exercise/"],
  "include": ["../src"],
  "compilerOptions": {
    "strict": true,
    "noUncheckedIndexedAccess": true
  }
}

config/tsconfig.shared.json
{
  "compilerOptions": {
    "target": "es5",
    "lib": ["dom", "dom.iterable", "esnext"],
    "allowJs": true,
    "skipLibCheck": true,
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "strict": false,
    "forceConsistentCasingInFileNames": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "noEmit": true,
    "jsx": "react-jsx",
    "noFallthroughCasesInSwitch": true
  }
}

Running tsc -b will typecheck all the files with the expected configuration.
However, as soon as I run react-scripts start, my tsconfig.json gets changed:
{
  "files": [],
  "references": [
    {
      "path": "config/tsconfig.exercise.json"
    },
    {
      "path": "config/tsconfig.final.json"
    }
  ],
  "compilerOptions": {
    "target": "es5",
    "lib": [
      "dom",
      "dom.iterable",
      "esnext"
    ],
    "allowJs": true,
    "skipLibCheck": true,
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "noFallthroughCasesInSwitch": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "noEmit": true,
    "jsx": "react-jsx"
  },
  "include": [
    "src"
  ]
}

With those changes, when I try to run tsc (or tsc -b), I get several errors, for example:
tsconfig.json:4:5 - error TS6306: Referenced project '/Users/kentcdodds/code/epic-react/react-fundamentals/config/tsconfig.exercise.json' must have setting "composite": true.

4     {
      ~
5       "path": "config/tsconfig.exercise.json"
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
6     },
  ~~~~~

tsconfig.json:7:5 - error TS6310: Referenced project '/Users/kentcdodds/code/epic-react/react-fundamentals/config/tsconfig.final.json' may not disable emit.

By setting "noEmit": false and "composite": true to the config/tsconfig.shared.json, I get a little further, but can't get rid of this error:
error TS6305: Output file '/Users/kentcdodds/code/epic-react/react-fundamentals/src/final/07.extra-3.d.ts' has not been built from source file '/Users/kentcdodds/code/epic-react/react-fundamentals/src/final/07.extra-3.tsx'.
  The file is in the program because:
    Matched by include pattern 'src' in '/Users/kentcdodds/code/epic-react/react-fundamentals/tsconfig.json'

  tsconfig.json:33:5
    33     "src"
           ~~~~~
    File is matched by include pattern specified here.

I've tried all combinations of options I can think of and nothing I can think of will make TypeScript happy + accomplish my goal of having a different config for different files in my create-react-app project.
Describe the solution you'd like
I would like support for references directly. I did notice ts-loader's page on references.
Short of that, I would be happy with an environment variable (similar to SKIP_PREFLIGHT_CHECK) which opts-out of updating the tsconfig.json and just trusts that the config works as-is.
Describe alternatives you've considered
I've thought about switching off of create-react-app or using one of the off-shoot projects that are flexible, but I'd really prefer to not do that.
Additional context
I think I've said everything that needs to be said 😅

Did a little investigation and noticed that create-react-app actually uses https://github.com/TypeStrong/fork-ts-checker-webpack-plugin for TypeScript checking. That actually does support references, but CRA has an older version which I don't think supports references.
Unfortunately when I tried to upgrade to the latest version I got an error (without any stack trace): Cannot read property 'tap' of undefined. I'm guessing this is because fork-ts-checker-webpack-plugin uses APIs in the v5 of webpack, but CRA is using webpack v4.
Upgrading to v5 would probably be pretty involved, so I stopped investigating there.
For the time being, I've just decided to use patch-package. My patch simply does an early exit in verifyTypeScriptSetup:
diff --git a/node_modules/react-scripts/scripts/utils/verifyTypeScriptSetup.js b/node_modules/react-scripts/scripts/utils/verifyTypeScriptSetup.js
index 949f34a..0b3b54e 100644
--- a/node_modules/react-scripts/scripts/utils/verifyTypeScriptSetup.js
+++ b/node_modules/react-scripts/scripts/utils/verifyTypeScriptSetup.js
@@ -58,6 +58,7 @@ function verifyNoTypeScript() {
 }

 function verifyTypeScriptSetup() {
+  return
   let firstTimeSetup = false;

   if (!fs.existsSync(paths.appTsConfig)) {

It "works" in that CRA doesn't update my tsconfig anymore, but I don't get any output in the terminal or in the error overlay when there's a TS error. This actually works out better for my use case, so this workaround works for me.

Yes, it seems pretty awkward that at this point in time CRA still hasn't solved this issue.
Development
├── Common Framework
│   └── tsconfig.json
└── MyApp
    ├── NodeProject
    │   └── tsconfig.json -> references: [ { path: "../../Common Framework/tsconfig.json" } ]
    ├── CRA Project
    │   └── tsconfig.json -> references: [ { path: "../../Common Framework/tsconfig.json" } ]
    └── Electron Project
        └── tsconfig.json -> references: [ { path: "../../Common Framework/tsconfig.json" } ]

In the CRA Project, everything works well in the editor (VS Code) but the project won't start.

+1 mono repos with Typescript would really benefit here

+1, been hoping for that feature for years now 🙏


CA retries three times when requesting secret creation.

Also includes the unit test to inject the failure.
fix #3844

@incfly: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
79e3a8b60848628b61cb509003f894441a20f8c2
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-presubmit

@incfly: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
79966d783991a25b9fc1481b8d2c3c2c2ef96608
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/reset

/retest

@incfly: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
79966d783991a25b9fc1481b8d2c3c2c2ef96608
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-presubmit

@incfly: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
79966d783991a25b9fc1481b8d2c3c2c2ef96608
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
79966d783991a25b9fc1481b8d2c3c2c2ef96608
link
/test istio-presubmit

prow/istio-unit-tests.sh
9b5c50ad5c988118c47a270bea4be50942ed9e4d
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
79966d783991a25b9fc1481b8d2c3c2c2ef96608
link
/test istio-presubmit

prow/istio-unit-tests.sh
ed0a7c083dfc96e0d410413919b1119afa5cb5ca
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
ed0a7c083dfc96e0d410413919b1119afa5cb5ca
link
/test istio-unit-tests

prow/istio-presubmit.sh
ed0a7c083dfc96e0d410413919b1119afa5cb5ca
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

Can you rebase to trigger the tests again?

@incfly: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ed0a7c083dfc96e0d410413919b1119afa5cb5ca
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@incfly: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
bc6ee18cb31ee110dfed08c3231ffed047602235
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


The scheduler doesn't work on IIS server

I have configured quartz scheduler in my code to run an overnight job, which runs perfectly fine in my local code if I leave my code running through the night. However, it never fires up on the IIS server.

Can't help you with IIS server here. This is a Java Quartz project.


Start to migrate away from Cert::Status, this is being done incrementally

Cert::Status is being deprecated in favour of util::Status and util::StatusOr. This converts 3 methods to StatusOr and adds some helpers to support the change.

Ok, FULLY reviewed this now, instead of the stop-and-restart I had been doing! So once all this is addressed, we should be good.

BTW, useful bit of info, this here is where the error codes really matter, as they get sent to the user:
https://github.com/google/certificate-transparency/blob/master/cpp/server/handler.cc#L122

Is this PR good now? It's really hard to tell with this review system.

LGTM

Thanks. I even rebased it onto master without breaking the universe.

Oh, you've never broken the universe that badly... I once rebased the master branch itself by mistake, pushed it, and Al started working in an "alternate universe". :smiley:
Thanks!


[BUG] Error points towards non-existent directory.

Describe the bug
Installed Ducker, and tried to run it, but can't debug why it's throwing an error because it's throwing multiple and doesn't point towards a valid file
To Reproduce
Steps to reproduce the behavior:

Install Ducker
Try to run it
Location where the error points to while being thrown doesn't exist

Expected behavior
Ideally it should just work, but at least it should throw an error that points to a valid directory
Screenshots

Desktop (please complete the following information):

OS: WSL2 - Arch Linux (Base; Windows 11)
Version <IP_ADDRESS>-microsoft-standard-WSL2

@danyshs this seems to be a config issue
The error is essentially a prettified stack trace, and it should be read as
"Error - 0: ... because 1:... because ...", with the location referencing the location of line in the source code that's raised the error
Ducker is unable to find the docker socket file (usually unix:///var/run/docker.sock)
Does that file exist? If it does, what happens if you execute docker image ls?

[I have Docker-cli on wsl, I don't have Docker Desktop!]
I..............think I realized what the issue was.
At the time of making the post, I think the docker daemon was off.
All is well now.

Either that, or when I had no containers or images loaded up, it had a breaking error rather than launching to an empty screen.
That is a possibility too.


Fix OkLCh parsing

Accidentally had part of our regex duplicated. Only failed when hue was a single digit value.
Fixes #257

Ugh, something changed with lint and now it doesn't like Typing imports that are used in comments as it things we are not using the import....

Also, mypy seems broken on Windows for some reason.

Turns out it was a permission issue in the environment. We can no longer directly call the mypy executable due to permission issues. We need to call python -m mypy instead.

@gir-bot lgtm


Succeed to paste blobs which support access tier to a BlockBlobStorage blob container with the setting 'Preserve blob access tier' is enabled

Storage Explorer Version: 1.16.0
Build Number: 20201119.2
Branch: main
Platform/OS: Windows 10/ Linux Ubuntu 16.04/ MacOS Catalina
Architecture: i32/x64
Regression From:  Not a regression
Steps to Reproduce

Launch Storage Explorer -> Go to 'Settings -> Transfers' -> Enable the setting 'Preserve blob access tier'.
Expand one GPV2 storage account -> Blob Containers -> Create a blob container.
Upload a block blob -> Copy the blob.
Expand one BlockBlobstorage account -> Blob Containers -> Open one blob container -> Paste the blob.
Check the result.

Expected Experience
Fail to paste the blob.
Actual Experience
Succeed to paste the blob.

Confirmed with AzCopy that it should proceed without setting the access tier. I will change the text of the setting's description.

@JasonYeMSFT
Failed to paste blobs which support access tier to one Classic blob container with the 'Preserve blob access tier' is enabled.
Could you help to take a look?

Could you use the latest version to try "pasting to a classic storage account" to see if it is working now?

@JasonYeMSFT
Verified on the latest build main/20210416.2.
Fail to paste one block blob to one classic blob container with 'Preserve blob access tier' enabled.

Error in Azcopy:
RESPONSE Status: 400 Blob access tier is not supported on this storage account type.

Verified this issue on the build main/20220518.1. Fixed.


sql: add support for intervals, DATE_SUB and DATE_ADD

Fixes #663
This PR introduces a few new features:

Correctly parsing interval expressions.
Allow using the + and - operators to subtract from and add to
dates. e.g. '2019-04-10' - INTERVAL 1 DAY.
New DATE_ADD function, which is essentially the same as
DATE + INTERVAL.
New DATE_SUB function, which is essentially the same as
DATE - INTERVAL.
Validation rule to ensure intervals are only used in certain
specific places, such as DATE_SUB, DATE_ADD, + and -. Using it
anywhere else is not valid SQL, but vitess does not catch those
errors. Plus, even if it's an expression for convenience, its
Eval method is a stub and panics, so it should not be used
unless it's in an expression that knows how to deal with intervals.

I confirm that works properly with superset

Rebased

Rebased again

Shall we merge this?

@erizocosmico I think changes on SUPPORTED.md file are missed.

@ajnavarro the one for DAYOFMONTH? That's not from this PR. DATE_ADD and DATE_SUB are already on SUPPORTED.md


Google Sign In Log in integration

I have google sign in in my app already. When I add the chat sdk I want to skip the log in screen and let users chat with their google accounts, is this possible and how can I do this?

Hi @zkharris,
You will need to link your Google Sign in flow with that of the Chat SDK.
You can see how the code should go here - looking at google sign in on Android for Firebase. I would also recommend looking at how we currently login with the Chat SDK and then linking that in with your current login flow.
Simon

Hi @simonsmiley64,
I am looking for a similar approach where I can use the usernames to chat with different people?To implement push notification can I use my own server instead of backendless.?

Has anyone done a module to Sign in with Google?
It'll be interesting to make module similar to Facebook one but using Google Auth code.

Added in v4.0.


When return back online multiple mutations sent to AppSync

Describe the bug
When doing multiple mutations on the same record, after the app getting back online, the Amplify sends all the mutations not the last mutation record.
For example: if we have a Post entity and this entity has rates parameter, editing this parameter while offline for example 5 times on the same record (Same Post ID), after the app getting back online, the Amplify sends these 5 different mutations, instead of sending the latest changes only.
Steps To Reproduce
1. Make multiple actions on the same record
2. Turn on wifi
3. the Amplify will send all record mutations, not the latest change only.

Expected behavior
To send only the latest mutation on the same record, instead  of sending all the mutations happened on the same record.
Amplify Framework Version
1.28.0
Amplify Categories
DataStore
Dependency manager
Cocoapods
Swift version
5.0
CLI version
Not Installed
Xcode version
13.3.1
Relevant log output
Is this a regression?
Yes
Regression additional context
No response
Device
iPad 5th generation
iOS Version
15.5
Specific to simulators
No response
Additional context
No response

I can confirm that this is related to query predicates params, as the code below
// Only applies the update if the data in the remote backend satisfies the criteria
Amplify.DataStore.save(post, where: Post.keys.title.beginsWith("[Amplify]")) {
// handle result
}
if your backend implementation doesn't satisfies the criteria, you have to use the save method only without query predicates, this will send all the latest mutation happened on the record and will not send the all the mutations happened on the same record
Amplify.DataStore.save(post) {
// handle result
}
as you can find in the documentation: (https://docs.amplify.aws/lib/datastore/sync/q/platform/ios/#distributed-data)
I wanted to comment this info in case anyone may need it in the future.
Thanks.

Hi @medhatIbsais-Harri, I believe there is some logic in DataStore that will dedup in some scenario such as "create then delete" and remove both of them from being sent, or when the "create then update" will replace the create with the update and remove the update. In this case, it sounds like all "updates" should be replaced with the initial "create". However, it the "create" is already in flight and retrying its attempt to sync to AppSync then remaining "updates" as they get added to the queue will missing the dedup logic.

We can explore this with your repro steps, and debug around this code in https://github.com/aws-amplify/amplify-swift/blob/main/AmplifyPlugins/DataStore/Sources/AWSDataStorePlugin/Sync/MutationSync/AWSMutationDatabaseAdapter/AWSMutationDatabaseAdapter%2BMutationEventIngester.swift and determine whether this is the expected behavior or if there's a bug. You also mentioned that this is a regression, is this true? is there a version of DataStore that is deduping the 5 mutations down to 1?

Please re-open if this is still an issue impacting your app. Dedupping mutation events logic hasn't changed and should be sending all 5 mutations if they were not dedupped according to the dedup logic. If you can provide us with more details such as the schema and operations performed, we can cross check against the dedup logic on a high level to see if they should be dedupped or not.


Add container monitor plugin type for restart

Adds a plugin type for container monitor. This avoids making the internal plugin type require service plugins since internal plugins should be loaded earlier.
Rename the task monitor type to avoid confusion.
Add config migration for new plugin types to pass existing migration tests.

Updated to use config version from the version package


Error log when dataType is "file" in @ApiImplicitParam (swagger-jaxrs)

Hi all,
Working with version 1.5.1, I get an error trace[1] when I set "file" as the dataType in an ApiImplicitParam annotation.
Seems like the problem is in the method "typeFromString" in https://github.com/swagger-api/swagger-core/blob/master/modules/swagger-jaxrs/src/main/java/io/swagger/jaxrs/utils/ReflectionUtils.java
Maybe "file" should be in PrimitiveType ?
Changing dataType to java.io.File the error dissapeared but the file input also dissapeared from the UI and I cannot perform multipart post.
[1] ERROR [io.swagger.jaxrs.utils.ReflectionUtils] Failed to resolve 'file' into class: java.lang.ClassNotFoundException: file from ...

Hi @webron, thank you for classify it. Do you have any idea what version it will be solved?

No idea.

@webron ok, thanks for the reply.
Do you think that adding "file" to PrimitiveType could be a good solution?
I just made the change in the develop_2.0 branch and adding file to io.swagger.converter.PrimitiveType.java solves the error log and all test are OK so if all of you agree I can send a PR

I'm reading right now the announcement in the google group [1] so I suppose that it's better wait that the changes are done in the repo to be sure in what branch I have to test the changes.
Anyway, I'm available to send the PR if my proposal is correct.
[1] https://groups.google.com/forum/#!topic/swagger-swaggersocket/dEwm8J5p7Ag

Hi everybody,
I know that this is not a critical bug but the fake error in the log is generating some "controversy" in our solution and it would be great if can be solved in the next release.
I suppose that the PR #1363 is yet not accepted because more test are needed or there are another issues related so if we can help doing more changes or tests, we are glad to help you.
Regards,
Agus

The dataType field is expecting either a primitive or a fully-qualified type.  So you can certainly use java.io.File and it'll follow the regular processing patterns.

Hi @fehguy,
Changing the dataType to java.io.File solves the log issue, but then in the swagger UI (I'm working with the 2.1.1 version) the file input dissapeared and it becomes a normal text input.
This is the JSON fragment with the definition for this input:
{
"name" : "file",
"in" : "formData",
"description" : "File to upload",
"required" : true,
"type" : "java.io.File"
}
Should I open an issue in the swagger-ui project?
Thanks!!

hmm.  Can you please change the input type to java.io.InputStream and let me know what you get?

Hi again @fehguy,
With java.io.InputStream as dataType I get the same situation. There are no error in the log but the file input in the IU is  a normal text input.
This is the generated JSON:
{
"name" : "file",
"in" : "formData",
"description" : "File to upload",
"required" : true,
"type" : "java.io.InputStream"
}
Let me know if you need some more testing and if I should open an issue in the UI project.
Thanks!

OK I've dug into this more.  We do indeed need to make a change in the processing chain :(

You can pull this from master

Hi @fehguy !
I've  tested and works fine! (setting java.io.File as the dataType).  Do you have a date (or an aproximate idea) for the 1.5.5 release?
Thanks!

Hi, I have pushed a snapshot to sonatype-snapshots repo.  For the next release, I don't have a date but I do hope to do it within a few weeks.  I apologize that we didn't get this into 1.5.4, there was just too much to do :)

I can confirm that this is resolved in 1.5.6.

great, thank you

@fehguy I'm still seeing this error log with dataType="file" in 1.5.9. dataType="java.io.InputStream" generates no error on the server-side, but also no file chooser on the client side (also having "java.io.InputStream" in the generated swagger.json/yaml wouldn't really be helping our non-java clients). "java.io.File" on the annotation works (and results in the correct "type": "file" in the JSON), but the spec says to use "file", so maybe this should be supported on the annotation?

@dklotz please share your whole annotation declaration

This works:
@ApiImplicitParams({
            @ApiImplicitParam(name = UploadRequestParts.FILE, value = "The binary file to upload.", required = true, dataType = "java.io.File", paramType = "form")
})

This generates the error log mentioned above:
@ApiImplicitParams({
            @ApiImplicitParam(name = UploadRequestParts.FILE, value = "The binary file to upload.", required = true, dataType = "file", paramType = "form")
})

So the workaround works, I just thought the annotations should maybe accept the type "file" as its described in the spec.

I don't know if this was ever pulled in or what happened but the fix for this thing is definitely not in. Was this rejected on purpose or can we still add file as primitive type?

I've created pull request here:
https://github.com/swagger-api/swagger-core/pull/1981


Missing Autoupdate in call list

Current behaviour:
If the call list is changed in motions > multi-select then the call list is not automatically updated in the call-list
Reproduction:
To be able to test you need to wait for or checkout #2861

create two motions
open a second tab with the call-list
change the order of the call-list via multi-select in the motion-list-view
look at the tab with the call-list
the call list is not updated automatically
if the page is reloaded then the call-list is up-to-date

Wanted behaviour:
the call-list should be automatically up-to-date

the call-list should be automatically up-to-date

this is NOT desired. Don't need a fix.


Data validation

This PR adds data validation routines that compare data values against valid ranges in src/descriptors/validation_config.yml

Some unit tests error out because of an invalid range on bus and line angles. Cannot create a system with data_14bus_pu.jl data.
Working on adding table of valid range data to docs.

@kdheepak @daniel-thom @claytonpbarrows @jd-lara

Looks like you need to run again generate_structs.jl since the structs don't match the files in the PR.

The validation code is too verbose and it is impossible to tell what is wrong. Also, from a quick glance on the values, it seems that they are causing all the datasets to fail.

Overall, nice work!  My comments are mostly minor and can easily be fixed.

validation functions are now organized using multiple dispatch, which will allow users to add functions later on without having to change any logic
error logs are now more descriptive, so it is now easier to what data errors are coming from

I get this error when running the tests:
┌ Error: Invalid range
│   valid_info.struct_name = "Bus"
│   field_name = "angle"
│   field_value = -7.74152
│   valid_range =
│    Dict{Any,Any} with 2 entries:
│      "max" => 1.571
│      "min" => -1.571
│   valid_info.ps_struct =
│    Bus:
│       number: 101
│       name: Abel
│       bustype: PV
│       angle: -7.74152
│       voltage: 1.04777
│       voltagelimits: (min = 0.95, max = 1.05)
│       basevoltage: 138.0
│       internal: PowerSystems.PowerSystemInternal(UUID("f5906819-ff64-4605-aa3e-7ce3bbb4891d"))

This data is from RTS_GMLC/bus.csv

@jd-lara @claytonpbarrows
The parse_matpower tests are also failing because of some valid_range violations. Some of the lines have b values above 2.0, as high as 6.8. Also, some Transformer2Ws have r and x values of about 2.14.
Are these valid data values and should I just adjust the valid ranges accordingly?

@KiraDF which files are these? in transformers isn't too crazy to see these values because of the voltage p.u. transformations.

@jd-lara

@KiraDF which files are these? in transformers isn't too crazy to see these values because of the voltage p.u. transformations.

@jd-lara I believe it's case_ACTIVSg10k.m

case_ACTIVSg10k.m contains 765 kV lines with really large shunt capacitance values. The recommendation is to open up the valid range to make tests pass and address the parameter checks for lines in a different way. Related to #290

Disabled validation in pm to ps parsing for now so that unit tests pass. When validation for pm to ps parsing is enabled, the only test that still fails is network_matrices.

The test is failing at
LoadError: SystemError: opening file "/home/travis/build/NREL/PowerSystems.jl/src/descriptors/validation_config.yml": No such file or directory
246  Stacktrace:

What's left:

Travis build failing because of pyaml package
To add on:
SIL calculations
Enabling data validation for pm to ps parsing

Codecov Report

Merging #294 into dev will increase coverage by 0.54%.
The diff coverage is 89.18%.

@@            Coverage Diff            @@
##              dev    #294      +/-   ##
=========================================
+ Coverage   62.15%   62.7%   +0.54%
=========================================
  Files          78      73       -5
  Lines        4410    4475      +65
=========================================
+ Hits         2741    2806      +65
  Misses       1669    1669

Impacted Files
Coverage Δ

src/parsers/pm_io/common.jl
75% <ø> (-0.68%)
:arrow_down:

src/models/generated/Transformer2W.jl
75% <ø> (ø)
:arrow_up:

src/models/generated/Line.jl
69.23% <ø> (ø)
:arrow_up:

src/models/generated/TapTransformer.jl
76.92% <ø> (ø)
:arrow_up:

src/models/generated/ThermalStandard.jl
50% <ø> (ø)
:arrow_up:

src/models/generated/PhaseShiftingTransformer.jl
78.57% <ø> (ø)
:arrow_up:

src/models/generated/MonitoredLine.jl
28.57% <ø> (ø)
:arrow_up:

src/parsers/pm_io/data.jl
43.1% <ø> (-3.12%)
:arrow_down:

src/PowerSystems.jl
100% <ø> (ø)
:arrow_up:

src/common.jl
100% <100%> (ø)
:arrow_up:

... and 9 more

Continue to review full report at Codecov.

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

If the validation is being switched to JSON instead of YAML we don't need the python script anymore I think.


iOS: Able to login to eSignet health portal using old binded credentials

Describe the bug
Able to login using old binded credentials.
To Reproduce
Prerequisite: Download VC on iphone 11 & iphone 8

bind the VC using VID in iPhone 11
now bind VC  for same VID in iPhone 8
login to eSignet health portal using iPhone 8 -> Login is successful.
again to eSignet health portal using iPhone 11

Expected behavior
Login on iPhone 11 should fail by displayed error message as on iPhone 11 binding of VC was done before iPhone 8.
Actual behavior
Able to login to eSignet portal using old binded VC i.e on iPhone 11
Screenshots

Add the screenshot of the profile page with commit id

iOS app version :0.4.1 (32)

Smartphone (please complete the following information):
Device 1 : iphone 11 | iPhone 15 BLE 5.0
Device 2 : iphone 8 | iphone 16 BLE 5.0

Mimoto version: <IP_ADDRESS>
MOSIP Version: qa-1201-b2.mosip.net

Where does the issue occur: Wallet/Verifier?
N/A
Logs of wallet and verifier:
N/A

Tried to reproduce the issue with iPhone 8 and iPhone 11. However, I couldn't able to reproduce it.
It works as expected - Old binded vc not logging in esignet health portal

cc @krishnakumar4a4 @ravikp

@Anushree09-N @santhoshsunder
I have tested in iPhone 11, XR and 14 Promax 5 times and couldn't able to reproduce the issue.
Test details:
Test flight build: 0.4.1(32)
QA env: 1201 qa / Purple theme

This issue has been verified and closed in jira https://mosip.atlassian.net/browse/INJI-49 , hence closing the same on git.


Some question

Thank you for sharing. What GPU are you using and how long does it take to run on ShapeNet and KITTI?

Hello, thanks for your question!
With batch size 32, it takes 5 days for training on the ShapeNet dataset with 4 Tesla V100 GPUs.
For inference, it takes 46 ms to generate 16,384 points on a single Nvidia V100 GPU.
We do not train the model on KITTI dataset since there is no Gound Truth in KITTI. We do inference on KITTI.


Service Camera Snapshot not working Home Assistant

Recalling service: Camera.Snapshot not work.
The image file is created but the size is always 0B

Does it work if you call it from the web gui?
I tested it now with ha and it works.
Have you tested it with a correct external dir?
Do you have the permissions to write to this folder?

in attachment the screenshot of service recal from HA dev tool

What do you mean with "Does it work if you call it from the web gui?"

Maybe a "/" is missing before tmp?
Open this url:
http://IP-CAM/?page=snapshot
using the IP of your cam.

Hi,
I verified in the web UI and the snapshot feature was disabled.
I enabled it and now it works.
I only noticed that the snapshot in hi res take so much time (about 3 seconds) and to avoid timeout in HA automation I must keep active the "Force low res snapshot feature".
We can close the issue
Best regards
Cristian

Yes, I know. The snapshot is very expensive in terms of cpu and memory.
So, it requires time.


Add remaining KDD routing config

Description
Add remaining KDD routing options to the docs.  This remains a Beta feature.
After a scour of the docs, I think the changes need to be relatively minimal - basically pointing to the existing BGP doc to illustrate how to configure BGP.

@robbrockbank looks fine to me, but we should port to the v2.4 docs as well.

Fixes #942


[Efficient Metadata Operations] Create methods in ClusterMapUtils to assist in reserving metadata id for regular uploads as well as stitched uploads.

There are 4 cases to handle in order to reserve metadata chunks:

Reserve metadata chunk id for regular Post requests to upload a regular simple or composite blob.
Reserve metadata chunk id for POST signed-url requests with the "chunked-upload" header set to true. This reserved metadata id will be used for chunked uploads and the subsequent stitch blob operation.
For chunked uploads use the reserved metadata id encoded in the signed-URL.
For stitch requests use the reserved metadata id in the signed-ids of the chunks.

This PR makes preparation for reserving metadata id for cases 1 & 2 above.

Codecov Report
Patch coverage: 84.61% and project coverage change: -4.96 :warning:

Comparison is base (11b42f5) 73.19% compared to head (fb4128b) 68.23%.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #2447      +/-   ##
============================================
- Coverage     73.19%   68.23%   -4.96%
+ Complexity    10993    10293     -700
============================================
  Files           777      777
  Lines         61649    61656       +7
  Branches       7571     7574       +3
============================================
- Hits          45126    42074    -3052
- Misses        14049    17151    +3102
+ Partials       2474     2431      -43

Impacted Files
Coverage Δ

...ain/java/com/github/ambry/router/PutOperation.java
89.80% <80.00%> (-0.40%)
:arrow_down:

...a/com/github/ambry/clustermap/ClusterMapUtils.java
91.77% <87.50%> (-0.17%)
:arrow_down:

... and 158 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


version 4.1.0

Codecov Report

Merging #2 (1447caf) into master (4831034) will decrease coverage by 13.72%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master       #2       +/-   ##
===========================================
- Coverage   94.29%   80.57%   -13.73%
===========================================
  Files          75       75
  Lines       15783    15147      -636
===========================================
- Hits        14883    12205     -2678
- Misses        900     2942     +2042

Impacted Files
Coverage Δ

setup.py
0.00% <ø> (ø)

tests/test_cluster.py
14.82% <0.00%> (-83.72%)
:arrow_down:

redis/cluster.py
21.79% <0.00%> (-68.51%)
:arrow_down:

redis/commands/cluster.py
34.48% <0.00%> (-60.35%)
:arrow_down:

redis/crc.py
40.00% <0.00%> (-60.00%)
:arrow_down:

redis/utils.py
70.00% <0.00%> (-20.33%)
:arrow_down:

redis/__init__.py
76.19% <0.00%> (-14.29%)
:arrow_down:

tests/conftest.py
77.60% <0.00%> (-13.53%)
:arrow_down:

redis/exceptions.py
86.15% <0.00%> (-12.31%)
:arrow_down:

redis/connection.py
79.27% <0.00%> (-9.43%)
:arrow_down:

... and 37 more

Continue to review full report at Codecov.

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

out of date, closing.


using special enter/leave stderr escape sequence on DomTerm

Stderrred doesn't work right if stderr contains escape sequences (one example is gcc). In that case only the initial part of the error message is red.  This can be fixed by parsing the output looking for escape sequences (specifically "end style" sequences), but that is complex.  Better would be for the terminal to understand a special escape sequence pair to delimit error messages.  DomTerm defines such a pair of sequences.
Another advantage of a distinct escape sequence is that you can style it - even retroactively. DomTerm (being web-based) uses CSS, so you can use whatever style you want.
Note setting STDERRED_ESC_CODE is insufficient as it doesn't override the end_color_code.  Plus it is nicer if it is automatic.  An alternative way to deal with this would be to allow STDERRED_ESC_CODE to optionally contain both the start_color_code and the end_color_code, perhaps separated by a newline.

How is that complex?

Parsing terminal escape sequences is quite tricky if you want to do it correctly. To start with, you have to use a state machine - you can't use regular expressions. You should emit end_color_code before an escape, but recognizing when you should switch back (with start_color_code) is trickier.  You can handle probably 99% of cases if you switch back after a letter.
I notice issue #87 is related.


[wopi] Check file info return 500 when COLLABORATION_APP_PROOF_DISABLE set false

Describe the bug
try to get file info inside projects using wopi, which returns 500 when COLLABORATION_APP_PROOF_DISABLE set to true
Steps to reproduce

create file test.txt inside project space new-space
get access token and URL  using endpoint /app/open?app_name=$app&file_id=$fileId&view_mode=$viewMode returns

"app_url":"https://host.docker.internal:9980/browser/d5ebff5/cool.html?WOPISrc=https%3A%2F%2Fhost.docker.internal%3A9300%2Fwopi%2Ffiles%2F667803bae99efa72b803fd01131514d95dc2f1ef880be032da20f5ff6ccdbaed",
"method":"POST",
"form_parameters":{"access_token":"eyJhbGciOiJIUzI1NiIjl0BboY4ktwyLYivcSK08",
"access_token_ttl":"1727850048000"
}

using WOPISrc and access_token from the above response send get request return 500 status code

collaboration-1     | {"level":"error","service":"collaboration","request-id":"","proto":"HTTP/1.1","method":"GET","path":"/wopi/files/667803bae99efa72b803fd01131514d95dc2f1ef880be032da20f5ff6ccdbaed","WopiSessionId":"","WopiOverride":"","WopiProof":"","WopiProofOld":"","WopiStamp":"","FileReference":"resource_id:{storage_id:\"48e4a2bf-9500-42d5-9294-147c544343cf\" opaque_id:\"9ee81667-30f8-4939-ab6d-51b81c3cf0e9\" space_id:\"4068e0a9-e76e-43fb-883d-0b47146f8fd8\"} path:\".\"","ViewMode":"VIEW_MODE_VIEW_ONLY","Requester":"idp:\"https://host.docker.internal:9200\" opaque_id:\"64fd0d40-ef6a-428a-b372-d805d9e42b9c\" type:USER_TYPE_PRIMARY","error":"Invalid timestamp","time":"2024-10-01T06:27:10Z","line":"github.com/owncloud/ocis/v2/services/collaboration/pkg/middleware/proofkeys.go:55","message":"ProofKeys verification failed"}
collaboration-1     | {"level":"info","service":"collaboration","proto":"HTTP/1.1","request-id":"e7a2b2c5f26f/uOXBipWHg9-000023","traceid":"00000000000000000000000000000000","remote-addr":"<IP_ADDRESS>:33384","method":"GET","wopi-action":"","status":500,"path":"/wopi/files/667803bae99efa72b803fd01131514d95dc2f1ef880be032da20f5ff6ccdbaed","duration":0.219521,"bytes":22,"time":"2024-10-01T06:27:10Z","line":"github.com/owncloud/ocis/v2/services/collaboration/pkg/middleware/accesslog.go:35","message":"access-log"}

Expected behavior
HTTP status code should not be 500
Actual behavior
Returns 500 status code
Setup
Please describe how you started the server and provide a list of relevant environment variables or configuration files.

ownCloud	Infinite Scale
Edition	Community
Version	6.4.0+ee8a3d48b
Web client version	10.3.0

@amrita-shrestha
There is a security mechanism called „proof keys“ which prevents that api call.
It should not give a 500 error though (@jvillafanez  please check which could be an appropriate response code)
You can disable proof key validation for testing purposes.

From https://learn.microsoft.com/en-us/microsoft-365/cloud-storage-partner-program/online/scenarios/proofkeys :

When validating proof keys, if a request isn't signed properly, the host must return a 500 Internal Server Error

According to the logs, no proof key has been sent, so I think it can fall under that case. I don't see any other information about the proper error code we should send.

its look expected behavior so closing this issue

From https://learn.microsoft.com/en-us/microsoft-365/cloud-storage-partner-program/online/scenarios/proofkeys :

When validating proof keys, if a request isn't signed properly, the host must return a 500 Internal Server Error

According to the logs, no proof key has been sent, so I think it can fall under that case. I don't see any other information about the proper error code we should send.

We could also return status 400.

There are some headers that should be filled for a proper validation (https://github.com/owncloud/ocis/blob/master/services/collaboration/pkg/middleware/proofkeys.go#L42-L52), so we could return a 400 if any of them is missing or with an empty value. However, I think we should still return a 500 if the "official" validation fails, as it's documented.
I think this is a good compromise.


Fix issue where yarn was required when it shouldn't be

The new command was assuming yarn is installed. This PR fixes that and adds another method to the packager module, packager.is("yarn" | "npm").
Fixes #1597.

:tada: This PR is included in version 6.5.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix: sync: true BehaviorSubject

Making the BehaviorSubject sync allows the LiveList to emit the new items right after the change is made (eg with upserItem or any other dependent stream event)
This solves the case of the "placeholder screen is shown after contract is accepted" issue for clara clients.

"i trust you bro"'d by @attilapolgar


Documentation and code refresh

Made some minor changes to project structure. Made courses.csv and entitlements.csv single file titled: courses.csv. User filtering is optional and can be done with the inclusion of a user_id column. Courses.csv must then be joined with data in Tableau. Updated README.

Hey @alisonmyers. I've blended entitlements.csv and courses.csv into a single courses.csv file. user_id column is optional.
Tableau has since changed how relationships work between Tables and now I'm a bit less familiar with it. See the README under "Connecting to Tableau", I've tagged you and asked for tips. How do we get that same "join" type filtering in Tableau's new "relationship" feature?
This is how we used to do it:

can we call it course_entitlements (?)

sure!

Would close #8
Would close #10

your pull request is still a draft - let me know if you are ready for review

Made change above. Merge ready?


Calling close() on a popout group will also close the group from which it originated

Describe the bug
When addPopoutGroup is called with an IDockViewPanel as its parameter, it creates a new group that is inexplicably "bound" to the group from which that panel originated. When the new group is closed, the old group will be closed as well.
To Reproduce
This issue can be demonstrated with just the Dockview Demo codesandbox.
Steps to reproduce the behavior:

Go to https://codesandbox.io/p/sandbox/frosty-shtern-ldx2jk
Click "Open in New Window" on panel_3
Click "Close" on panel_3 OR call close() on the new group created for the popout window
Panels 1 and 2 will inexplicably close

Expected behavior
Panels 1 and 2 should remain, only panel 3 should close.
Videos
https://github.com/user-attachments/assets/cadaa47a-0816-4f03-acc3-f245a11a93b0
https://github.com/user-attachments/assets/dff2d581-e0bc-4568-a6e7-c88a978a210a
Desktop (please complete the following information):

Chrome
Version 131.0.6778.86
Dockview version 2.0.0

Additional context
I'm working on an app with controls that let the user pop out individual panels, in addition to whole groups, so this issue pops up extremely often.

To clarify I suppose, because I'm not sure I was descriptive enough: a prescient problem with the new Group that is generated after calling api.addPopoutGroup() with an IDockviewPanel as the parameter. Closing the new Group by any means will also close the old Group, even though these two groups should no longer be related in any way.

Currently- as a workaround- I call moveTo on the panel being moved before I pop it out. This puts it in its own group, so the original group doesn't get destroyed when the new group is Close()d.
https://github.com/user-attachments/assets/04d998f1-c183-4580-bbc6-a007a7ecb592

Currently- as a workaround- I call moveTo on the panel being moved before I pop it out. This puts it in its own group, so the original group doesn't get destroyed when the new group is Close()d. This is fine for now, if a little janky in appearance.👍
https://github.com/user-attachments/assets/5a655450-ac27-489e-8d92-4017c55e0097

This should be fixed as of version 2.1.1. Please do let me know if you agree

Yes, tested & fixed as of 2.1.1 - nice one! :)


bugfix: add node failure

close #2389
cluster status might be overwriten by inappropriate usage

test:
1 master, 1 node before test.
add nodes failure and  then delete nodes that failed to join cluster.
root@lmaster:~/cf# sealos add --nodes <IP_ADDRESS>
2023-01-13T09:56:38 info start to scale this cluster
2023-01-13T09:56:38 info Executing pipeline JoinCheck in ScaleProcessor.
2023-01-13T09:56:38 info checker:hostname [<IP_ADDRESS>:22 <IP_ADDRESS>:22]
2023-01-13T09:56:38 info checker:timeSync [<IP_ADDRESS>:22 <IP_ADDRESS>:22]
2023-01-13T09:56:38 info Executing pipeline PreProcess in ScaleProcessor.
2023-01-13T09:56:45 error Applied to cluster error: failed to init runtime: cluster image kubernetes version cannot be empty
Error: failed to init runtime: cluster image kubernetes version cannot be empty
failed to init runtime: cluster image kubernetes version cannot be empty
root@lmaster:~/cf# sealos delete --nodes <IP_ADDRESS>
are you sure to delete these nodes? Yes [y/yes], No [n/no] : y
2023-01-13T09:57:19 info start to scale this cluster
2023-01-13T09:57:19 info Executing pipeline DeleteCheck in ScaleProcessor.
2023-01-13T09:57:19 info checker:hostname [<IP_ADDRESS>:22 <IP_ADDRESS>:22]
2023-01-13T09:57:20 info checker:timeSync [<IP_ADDRESS>:22 <IP_ADDRESS>:22]
2023-01-13T09:57:20 info Executing pipeline PreProcess in ScaleProcessor.
2023-01-13T09:57:27 error Applied to cluster error: failed to init runtime: cluster image kubernetes version cannot be empty
Error: failed to init runtime: cluster image kubernetes version cannot be empty
failed to init runtime: cluster image kubernetes version cannot be empty

bugfix:
root@lmaster:~/cf# sealos add --nodes <IP_ADDRESS>
2023-01-13T09:57:30 info start to scale this cluster
2023-01-13T09:57:30 info Executing pipeline JoinCheck in ScaleProcessor.
2023-01-13T09:57:30 info checker:hostname [<IP_ADDRESS>:22 <IP_ADDRESS>:22]
2023-01-13T09:57:31 info checker:timeSync [<IP_ADDRESS>:22 <IP_ADDRESS>:22]
2023-01-13T09:57:31 info Executing pipeline PreProcess in ScaleProcessor.
2023-01-13T09:57:38 info Executing pipeline PreProcessImage in ScaleProcessor.
2023-01-13T09:57:38 info Executing pipeline RunConfig in ScaleProcessor.
2023-01-13T09:57:38 info Executing pipeline MountRootfs in ScaleProcessor.
2023-01-13T09:58:05 info Executing pipeline Bootstrap in ScaleProcessort/s)
<IP_ADDRESS>:22:  INFO [2023-01-13 09:58:06] >> check root,port,cri success
<IP_ADDRESS>:22: Created symlink /etc/systemd/system/multi-user.target.wants/containerd.service → /etc/systemd/system/containerd.service.
<IP_ADDRESS>:22:  INFO [2023-01-13 09:58:07] >> Health check containerd!
<IP_ADDRESS>:22:  INFO [2023-01-13 09:58:07] >> containerd is running
<IP_ADDRESS>:22:  INFO [2023-01-13 09:58:07] >> init containerd success
<IP_ADDRESS>:22: Created symlink /etc/systemd/system/multi-user.target.wants/image-cri-shim.service → /etc/systemd/system/image-cri-shim.service.
<IP_ADDRESS>:22:  INFO [2023-01-13 09:58:08] >> Health check image-cri-shim!
<IP_ADDRESS>:22:  INFO [2023-01-13 09:58:08] >> image-cri-shim is running
<IP_ADDRESS>:22:  INFO [2023-01-13 09:58:08] >> init shim success
<IP_ADDRESS>:22: <IP_ADDRESS> localhost
<IP_ADDRESS>:22: ::1 localhost ip6-localhost ip6-loopback
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-console-messages.conf ...
<IP_ADDRESS>:22: kernel.printk = 4 4 1 7
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-ipv6-privacy.conf ...
<IP_ADDRESS>:22: net.ipv6.conf.all.use_tempaddr = 2
<IP_ADDRESS>:22: net.ipv6.conf.default.use_tempaddr = 2
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-kernel-hardening.conf ...
<IP_ADDRESS>:22: kernel.kptr_restrict = 1
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-magic-sysrq.conf ...
<IP_ADDRESS>:22: kernel.sysrq = 176
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-network-security.conf ...
<IP_ADDRESS>:22: net.ipv4.conf.default.rp_filter = 2
<IP_ADDRESS>:22: net.ipv4.conf.all.rp_filter = 2
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-ptrace.conf ...
<IP_ADDRESS>:22: kernel.yama.ptrace_scope = 1
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/10-zeropage.conf ...
<IP_ADDRESS>:22: vm.mmap_min_addr = 32768
<IP_ADDRESS>:22: * Applying /usr/lib/sysctl.d/50-default.conf ...
<IP_ADDRESS>:22: kernel.core_uses_pid = 1
<IP_ADDRESS>:22: net.ipv4.conf.default.rp_filter = 2
<IP_ADDRESS>:22: net.ipv4.conf.default.accept_source_route = 0
<IP_ADDRESS>:22: sysctl: setting key "net.ipv4.conf.all.accept_source_route": Invalid argument
<IP_ADDRESS>:22: net.ipv4.conf.default.promote_secondaries = 1
<IP_ADDRESS>:22: sysctl: setting key "net.ipv4.conf.all.promote_secondaries": Invalid argument
<IP_ADDRESS>:22: net.ipv4.ping_group_range = 0<PHONE_NUMBER>
<IP_ADDRESS>:22: net.core.default_qdisc = fq_codel
<IP_ADDRESS>:22: fs.protected_hardlinks = 1
<IP_ADDRESS>:22: fs.protected_symlinks = 1
<IP_ADDRESS>:22: fs.protected_regular = 1
<IP_ADDRESS>:22: fs.protected_fifos = 1
<IP_ADDRESS>:22: * Applying /usr/lib/sysctl.d/50-pid-max.conf ...
<IP_ADDRESS>:22: kernel.pid_max = 4194304
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/99-cloudimg-ipv6.conf ...
<IP_ADDRESS>:22: net.ipv6.conf.all.use_tempaddr = 0
<IP_ADDRESS>:22: net.ipv6.conf.default.use_tempaddr = 0
<IP_ADDRESS>:22: * Applying /usr/lib/sysctl.d/99-protect-links.conf ...
<IP_ADDRESS>:22: fs.protected_fifos = 1
<IP_ADDRESS>:22: fs.protected_hardlinks = 1
<IP_ADDRESS>:22: fs.protected_regular = 2
<IP_ADDRESS>:22: fs.protected_symlinks = 1
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/99-sysctl.conf ...
<IP_ADDRESS>:22: * Applying /etc/sysctl.d/k8s.conf ...
<IP_ADDRESS>:22: net.bridge.bridge-nf-call-ip6tables = 1
<IP_ADDRESS>:22: net.bridge.bridge-nf-call-iptables = 1
<IP_ADDRESS>:22: net.ipv4.conf.all.rp_filter = 0
<IP_ADDRESS>:22: * Applying /etc/sysctl.conf ...
<IP_ADDRESS>:22: net.ipv4.ip_forward = 1
<IP_ADDRESS>:22: Firewall stopped and disabled on system startup
<IP_ADDRESS>:22:  INFO [2023-01-13 09:58:09] >> init kube success
<IP_ADDRESS>:22:  INFO [2023-01-13 09:58:09] >> init rootfs success
2023-01-13T09:58:09 info Executing pipeline Join in ScaleProcessor.
2023-01-13T09:58:09 info [<IP_ADDRESS>:22] will be added as worker
2023-01-13T09:58:09 info start to get kubernetes token...
2023-01-13T09:58:09 info start to join <IP_ADDRESS>:22 as worker
2023-01-13T09:58:09 info start to copy kubeadm join config to node: <IP_ADDRESS>:22
<IP_ADDRESS>:22: 2023-01-13T09:58:10 info domain apiserver.cluster.local:<IP_ADDRESS> append success
<IP_ADDRESS>:22: 2023-01-13T09:58:11 info domain lvscare.node.ip:<IP_ADDRESS> append success
2023-01-13T09:58:11 info registry auth in node <IP_ADDRESS>:22
<IP_ADDRESS>:22: 2023-01-13T09:58:11 info domain sealos.hub:<IP_ADDRESS> append success
2023-01-13T09:58:11 info run ipvs once module: <IP_ADDRESS>:22
<IP_ADDRESS>:22: 2023-01-13T09:58:12 info Trying to add route
<IP_ADDRESS>:22: 2023-01-13T09:58:12 info success to set route.(host:<IP_ADDRESS>, gateway:<IP_ADDRESS>)
2023-01-13T09:58:12 info start join node: <IP_ADDRESS>:22
<IP_ADDRESS>:22: W0113 09:58:12.519218  139821 initconfiguration.go:120] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme "unix" to the "criSocket" with value "/run/containerd/containerd.sock". Please update your configuration!
<IP_ADDRESS>:22: [preflight] Running pre-flight checks
<IP_ADDRESS>:22:       [WARNING FileExisting-socat]: socat not found in system path
<IP_ADDRESS>:22:       [WARNING SystemVerification]: missing optional cgroups: blkio
<IP_ADDRESS>:22: [preflight] Reading configuration from the cluster...
<IP_ADDRESS>:22: [preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
<IP_ADDRESS>:22: W0113 09:58:12.637308  139821 utils.go:69] The recommended value for "healthzBindAddress" in "KubeletConfiguration" is: <IP_ADDRESS>; the provided value is: <IP_ADDRESS>
<IP_ADDRESS>:22: [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
<IP_ADDRESS>:22: [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
<IP_ADDRESS>:22: [kubelet-start] Starting the kubelet
<IP_ADDRESS>:22: [kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
<IP_ADDRESS>:22:
<IP_ADDRESS>:22: This node has joined the cluster:
<IP_ADDRESS>:22: * Certificate signing request was sent to apiserver and a response was received.
<IP_ADDRESS>:22: * The Kubelet was informed of the new secure connection details.
<IP_ADDRESS>:22:
<IP_ADDRESS>:22: Run 'kubectl get nodes' on the control-plane to see this node join the cluster.
<IP_ADDRESS>:22:
2023-01-13T09:58:26 info succeeded in joining <IP_ADDRESS>:22 as worker
2023-01-13T09:58:27 info start to sync lvscare static pod to node: <IP_ADDRESS>:22 master: [<IP_ADDRESS>:6443]
<IP_ADDRESS>:22: 2023-01-13T09:58:27 info generator lvscare static pod is success
2023-01-13T09:58:27 info succeeded in scaling this cluster
2023-01-13T09:58:27 info
      ___           ___           ___           ___       ___           ___
     /\  \         /\  \         /\  \         /\__\     /\  \         /\  \
    /::\  \       /::\  \       /::\  \       /:/  /    /::\  \       /::\  \
   /:/\ \  \     /:/\:\  \     /:/\:\  \     /:/  /    /:/\:\  \     /:/\ \  \
  _\:\~\ \  \   /::\~\:\  \   /::\~\:\  \   /:/  /    /:/  \:\  \   _\:\~\ \  \
 /\ \:\ \ \__\ /:/\:\ \:\__\ /:/\:\ \:\__\ /:/__/    /:/__/ \:\__\ /\ \:\ \ \__\
 \:\ \:\ \/__/ \:\~\:\ \/__/ \/__\:\/:/  / \:\  \    \:\  \ /:/  / \:\ \:\ \/__/
  \:\ \:\__\    \:\ \:\__\        \::/  /   \:\  \    \:\  /:/  /   \:\ \:\__\
   \:\/:/  /     \:\ \/__/        /:/  /     \:\  \    \:\/:/  /     \:\/:/  /
    \::/  /       \:\__\         /:/  /       \:\__\    \::/  /       \::/  /
     \/__/         \/__/         \/__/         \/__/     \/__/         \/__/

                  Website :https://www.sealos.io/
                  Address :github.com/labring/sealos
                BuildVersion: latest-

root@lmaster:~/cf# kubectl get nodes
NAME      STATUS   ROLES           AGE   VERSION
lmaster   Ready    control-plane   96m   v1.24.0
node1     Ready    <none>          95m   v1.24.0
node2     Ready    <none>          24s   v1.24.0

+1


Timer functionality

Issue Details
Type of Issue  (check one with "X")
[ X ] Bug Report => Please search GitHub for a similar issue or PR before submitting
[ ] Feature Request => Please ensure feature is not already in progress
[ ] Support Request => Please do not submit support requests here, instead see: https://discourse.oss.antheminc.com/

Current Behavior
No implementation
Expected Behavior
Need timer to be shown on UI and persist the time on exit of case
How to Reproduce the Issue
Steps to Reproduce

Code Snippet

Environment Details

Nimbus Version:
1.3.1.M6

Browser:
Chrome

The changes are available in 1.3.1.M15 version


started going through chapin hall list

started adding a bunch of datasets

There aren't any repeated entries, correct?

No, I didn't find any repeats.
Later I'll write a quick script to attempt to identify repeats.

so is this good to go outside of conflicts?

^asking because I have another few that I've added locally on my branch


incorrect link- should redirect to the power platform

in:
Prepare the environment
First, select a non-production environment and enable Use Unified Interface only mode, which will use the Unified Interface for all model-driven apps in the environment. This also includes any Dynamics 365 application modules originally configured for the legacy web client.
Sign in to Power Apps, select Environment, and then select a sandbox environment.
Select Settings > Behavior and then turn on Use Unified Interface only.
the link to powerapps should be the link to the Power Platform, https://admin.powerplatform.microsoft.com/
thank you

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

ID: 1dba9985-89f9-5c4d-84e4-f5825683a6c5
Version Independent ID: 2de67ad8-df27-064e-28fc-7536e6326390
Content: Quick start for transitioning your legacy web client application to Unified Interface - Power Apps
Content Source: powerapps-docs/maker/model-driven-apps/transition-web-app.md
Service: powerapps
GitHub Login: @Mattp123
Microsoft Alias: matp

@anapereiCRMSE - thank you for your feedback. The link and text has been updated to point to the Power Platform admin center.
Closing issue.

@anapereiCRMSE - thank you for your feedback. The link and text has been updated to point to the Power Platform admin center.
Closing issue.


Callbacks should be returned so that api methods can be chained

It would be helpful for the defaultFuncs call in some api methods to be returned, so that api calls can be chained.
For example, currently the following code would get errors:
api.getUserInfo(id, (err, arr) => {
    return arr;
}).then(function(data) {
    console.log(data);
});

If instead line 43 of getUserInfo.js is return defaultFuncs, the then in the above code would successfully run.
I can make a quick PR for this. 👍

Hey @enhdless, how often do you chain more than 2-3 api calls like this?
We don't really see promises as simple, and we're a bit scared of exposing them to the user. Errors/exceptions get hairy with promises (arguably promises are a problem in the codebase right now because we don't handle errors correctly).
Callbacks are simpler to understand :)

@enhdless If you need promises, you can use bluebird's Promise.promisify(api.someFunc). I'm using it in my project and it works fine, except for api.listen(cb) which isn't suitable for promises because it invokes cb(err, msg) everytime it receives a message.
E.g.:
Promise.promisify(api.getUserInfo)(id)
   .then(info => { ... })
   .catch(err => { ... })

Thanks @ivkos, I was thinking there much be something like this.
@enhdless would this work for you?

Ah I wasn't aware of promisify, seems like it'll suit my needs perfectly. Thanks @ivkos!


Setting rgb_preferred to SXGA_30Hz results in an "scrolling image"

Setting the rgb_preferred parameter in the Astra.cfg file to 1 results in an image with the correct size, but the image scrolls. I think this has something to do with the maximum height resolution of the camera being 960. but the image is pretty much unusable. I (understand)[https://github.com/orbbec/ros_astra_camera/issues/32] that the intended behaviour would be that a fixed part of the image would have invalid data.
Further more I did some experimenting with the different colour modes and I cannot say I understand which modes are compatible. Is there some documentation on that?

you should contact the seller to upgrade the firmware. pls visit orbbec3d.com for support.

刘华
座机：0755-86329228 转 8173
<EMAIL_ADDRESS>手机：13603061506
深圳奥比中光科技有限公司 www.orbbec.com.cn
地址：深圳市南山区学府路63号高新区联合总部大厦12楼
From: Mart Moerdijk
Date: 2018-04-10 23:18
To: orbbec/ros_astra_camera
CC: Subscribed
Subject: [orbbec/ros_astra_camera] Setting rgb_preferred to SXGA_30Hz results in an "scrolling image" (#49)
Setting the rgb_preferred parameter in the Astra.cfg file to 1 results in an image with the correct size, but the image scrolls. I think this has something to do with the maximum height resolution of the camera being 960. but the image is pretty much unusable. I (understand)[https://github.com/orbbec/ros_astra_camera/issues/32] that the intended behaviour would be that a fixed part of the image would have invalid data.
Further more I did some experimenting with the different colour modes and I cannot say I understand which modes are compatible. Is there some documentation on that?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi,
I tryied to find the update tool but I cannot find it. The topics I could find are all outdated. Could you provide me with the correct tool?
Best Regards,
Mart
These links don’t work
[1] https://3dclub.orbbec3d.com/t/astra-s-firmware-verification-and-update/
[2] https://3dclub.orbbec3d.com/t/rgb-d-sync-project/265
From: ob-tim-liu<EMAIL_ADDRESS>Sent: Wednesday, April 11, 2018 03:07
To: orbbec/ros_astra_camera<EMAIL_ADDRESS>Cc: Moerdijk, Marinus Matthias<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [orbbec/ros_astra_camera] Setting rgb_preferred to SXGA_30Hz results in an "scrolling image" (#49)
you should contact the seller to upgrade the firmware. pls visit orbbec3d.com for support.

刘华
座机：0755-86329228 转 8173
邮箱：liuhua<EMAIL_ADDRESS>手机：13603061506
深圳奥比中光科技有限公司 www.orbbec.com.cnhttp://atpscan.global.hornetsecurity.com/index.php?atp_str=3g3x7GE_17R7EkudUS7qm9vcG1K355zYMXMRGpZVC88KRrXlRvZVtmaj8oANQqVeI6HI-xXIWH2odM-EZkaGiNf6Y4BRhAcfI5k2THUBxJQFmUr2AHaunpa6yh3KLbddZz2mvdK-COLGtIVseQ6rZ7RzCYPtgW9os5q6iI3KvYj97WR1bWY91A0_WIXyYPS4DkXMjziVt8ldLvJWkaZ9s1103wbjWQqoBHPjQrMfyTz1aXhWMRalfNQrlNYBOKFuErVsWYvmwbrqJyL9xVPZxeM-e0JS9vJttqN9_7NpjvcdT2ppkce_MWu9Z-7WHDfsToPyYiAjsMEPSbiAAs8YW_ojOjojZjk5MWM1YjNkYjYzIzo6Izm9D46kSlEyW3u10qXFOXc
地址：深圳市南山区学府路63号高新区联合总部大厦12楼
From: Mart Moerdijk
Date: 2018-04-10 23:18
To: orbbec/ros_astra_camera
CC: Subscribed
Subject: [orbbec/ros_astra_camera] Setting rgb_preferred to SXGA_30Hz results in an "scrolling image" (#49)
Setting the rgb_preferred parameter in the Astra.cfg file to 1 results in an image with the correct size, but the image scrolls. I think this has something to do with the maximum height resolution of the camera being 960. but the image is pretty much unusable. I (understand)[https://github.com/orbbec/ros_astra_camera/issues/32] that the intended behaviour would be that a fixed part of the image would have invalid data.
Further more I did some experimenting with the different colour modes and I cannot say I understand which modes are compatible. Is there some documentation on that?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/orbbec/ros_astra_camera/issues/49#issuecomment-380294011, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIlKGd6p4Q3yoI_00SCoGdalVys0HFVvks5tnVcogaJpZM4TOeHt.


⚠ Bofrost.lu has degraded performance

In 4d0c2fa, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1763 ms

Resolved: Bofrost.lu performance has improved in 40334be after 10 minutes.


Hello, regarding the issue of random seeds,

may I ask why random seeds are set but the results are still different each time they are run?

Hi @Nieleilei,
Thank you for showing interest in our work!
Regarding your query, please note the following:
MaPLe uses multiple image-recognition benchmarks which all lies under the few-shot setting (i-e only few samples like 16-shots for each class are available for training).
Due to the few-shot training scenario, the model final performance heavily depend on the choice/quality of the few-shots samples used for each class and results fluctuate when the samples are changed. Therefore, it is a standard practice to train model using different seeds and report the performance averaged over 3 seeds. In this case, each seed uses different few-shot samples during training.
In our work, we train the models on 3 seeds where each seed uses different samples for each class, thus producing different results per seed.
I hope your query is resolved. Kindly let us know if there is any further question. Thank you!


build(package & releaserc): semantic release bump to 22.0.5 and node to latest & gulp release plugin

semantic release bump to 22.05 & node to latest and gulp plugin to publish releases on teams channel

Let me still merge this one - commit your review directly to master later.

:tada: This PR is included in version 4.0.1 :tada:
The release is available on:

v4.0.1
GitHub release

Your semantic-release bot :package::rocket:


add version fix

This fixes a typo in the version code.  Also the config file has
a space which causes the minor version to fail.  Rather than
modify that file, this makes the minor version check more robust.

Oh.
the problem is that the minor version is
#define foo 1(space)
Which means it didn't match the regex
Rather than remove the trailing space, I changed the regex to be more
robust.
On Mon, Aug 3, 2020 at 4:04 PM Mariana Meireles<EMAIL_ADDRESS>wrote:

@marimeireles commented on this pull request.
Hey @joequant https://github.com/joequant thank you very much for
catching this! :)
I just marked one question here.
In CMakeLists.txt
https://github.com/jupyter-xeus/xeus-sqlite/pull/57#discussion_r464255257
:

@@ -29,12 +29,12 @@ set(CMAKE_PROGRAM_PATH ${CMAKE_PREFIX_PATH})
file(STRINGS "${XEUS_SQLITE_INCLUDE_DIR}/xeus-sqlite/xeus_sqlite_config.hpp" xsqlite_version_defines
REGEX "#define XSQLITE_VERSION_(MAJOR|MINOR|PATCH)")
foreach(ver ${xsqlite_version_defines})

if(ver MATCHES "#define XSQLITE_VERSION_(MAJOR|MINOR|PATCH) +([^ ]+)$")

Why did you remove the $?
We're interested in that one, no?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jupyter-xeus/xeus-sqlite/pull/57#pullrequestreview-459824758,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWGAGKUSCVRYXLAEZRVOHDR6ZVQ5ANCNFSM4PSEAZWA
.

Alright, I see your point.
The problem now is that... It catches all other words if there are any. e.g is matching #define XSQLITE_VERSION_MAJOR 1.2.3 banana and we don't want that.
What do you think of adding: #define XSQLITE_VERSION_(MAJOR|MINOR|PATCH) +([^ ]+) *$? It's a bit more error proof, imo.
Thanks again!

That seems reasonable to me.
On Tue, Aug 4, 2020 at 5:09 PM Mariana Meireles<EMAIL_ADDRESS>wrote:

Alright, I see your point.
The problem now is that... It catches all other words if there are any.
e.g is matching #define XSQLITE_VERSION_MAJOR 1.2.3 banana and we don't
want that.
What do you think of adding: #define XSQLITE_VERSION_(MAJOR|MINOR|PATCH)
+([^ ]+) *$? It's a bit more error proof, imo.
Thanks again!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jupyter-xeus/xeus-sqlite/pull/57#issuecomment-668480688,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWGAGJEHCQXSF55Q6V5MDLR67F6FANCNFSM4PSEAZWA
.

Thanks again @joequant ! 🌸


Add Flavio to the author list.

Thanks for your contribution, Flavio!
Signed-off-by: Hui Kang<EMAIL_ADDRESS>

Thanks for doing this, Hui!
I noticed that the email is formatted with < > and the others in that file are not. Not sure
which one is the proper one.

@flavio-fernandes my bad. I will modify this. Thanks.

@mestery @hzhou8 , @l8huang could any of you commit this PR? Thanks.


[Bug] Effects do not align with token.

Default settings were used, effects don't appear to properly position themselves onto the token.
https://streamable.com/bk9nvw

You need to set it as a static image, the settings you have are for rotation


Review PromptModal logic

Detailed Description
Review data and logic related to the PromptModal.
Context
For the use of modals we have a generic action extended to several components. The data is too much generic and there's not defined common actions as separated key/value.
This generates confusion, bloated data and also issues like in this case

For the list of receivers for AlertmanagerConfigs in project monitoring, I ran into this problem too. For me the issue was not just that it was a generic action, but that it was tightly coupled to the Resource class, so it was hard to make it work on a list view of something that isn't a Kubernetes resource.
I modified the component to take props, so that its show/hide state could be controlled with props instead of the generic piece of state in Vuex, which was also tightly coupled with data from the Resource class. See the comments I left on the new props: https://github.com/rancher/dashboard/blob/master/shell/components/ActionMenu.vue#L31
If we refactored the list views to control the state with props and use a single ActionMenu component on each list view, instead of just using a single ActionMenu throughout the entire application, I think that it would make the code a lot more readable and maintainable.

For historical purposes, this looks to have shipped in 2.7.2 since the .x milestone typically means unscheduled.