NixOS unstable not updating / hydra is down

Issue description
Looks like hydra is down:
DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI connect('dbname=hydra;user=hydra;','',...) failed: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5432"? at /nix/store/d38294yk1n439fppd1rbpihnxih9mg94-hydra-perl-deps/lib/perl5/site_perl/5.22.2/DBIx/Class/Storage/DBI.pm line 1517. at /nix/store/pkc8nj14mkmd3z2x82ik993p7kfvr1z2-hydra-0.1.1234.abcdef/libexec/hydra/lib/Hydra/Helper/CatalystUtils.pm line 357

Cc: @grahamc @rbvermaa

Yes, nixos-unstable is over two weeks old now.

Yes, I'm trying to get a channel bump through, one test remaining.

That gnome test seems unfixable, at least without admin access.

Seems to be continuing now.

Success! I think the channel will get bumped updated soon.

Channel updated


Update walkthrough-set-up-integration-services-scale-out.md

Fixed the parentheses:

SQL Server Integration Services Scale Out Master 14.0 (SSISScaleOutMaster140s
to
SQL Server Integration Services Scale Out Master 14.0 (SSISScaleOutMaster140)

@cloudgiant99 : Thanks for your contribution! The author(s) have been notified to review your proposed change. @haoqian

@HaoQian-MS - you're the author of this article, correct?  If so, can you review this change?  Also please update the author metadata to be the same as your GitHub name (and not your microsoft alias). Thanks.

#sign-off


Add gradle wrapper validation

There is a gradle wrapper validation action available. This PR enables it for this repo.
Reason: PRs https://github.com/openjfx/javafx-gradle-plugin/pull/79 and https://github.com/openjfx/javafx-gradle-plugin/pull/74 are touching the gradle binaries. Who knows whether non-good code was introduced there.

Note that Gradle wrapper validation could also be added to the existing Github workflow YAML file...

Please point me to the existing GitHub workflow YAML file.
Currently, this repository seems to rely on TravisCI. Therefore, I followed the second proposal from the action's repository:
https://github.com/gradle/wrapper-validation-action#add-a-new-dedicated-workflow

Please point me to the existing GitHub workflow YAML file.

Haha. Sorry! I didn't realize that there wasn't one already.


Provide easier interaction for getting from list to detail view (e.g. Shift-Click?)

With the implementation of summary trays in all our list views, the interaction to go from list to detail view takes more steps.
Without trays (1 step):

Click row (goes to detail)

With trays (2 steps):

Click three-dot "More" icon (opens "Actions" dropdown menu)
Click "View details" (goes to detail)

or

Click row (opens tray)
Click tray title (goes to detail)

Options
1: Click to tray; Shift+Click to detail
Clicking opens the tray and Shift-clicking goes to the detail view.

Draft implementation: https://github.com/kumahq/kuma-gui/pull/1679
Bad: Hard to discover. How would we teach people that this shortcut exists?

2: Click to tray; "View details" icon link next to three-dot "More" dropdown menu to detail

Clicking opens the tray.
A new "View details" link in the form of an icon (an eye?) next to the three-dot "More" dropdown menu provides access to the detail view (replacing "View details" in the "More" dropdown menu).

Good: Relatively easy to discover.

3: Click to detail; "View summary" icon link next to three-dot "More" dropdown menu to tray
Clicking opens the detail.
A new "View summary" link in the form of an icon next to the three-dot "More" dropdown menu provides access to the detail view.

We decided to implement option 1 and 2. To summarize:

The main (i.e. Click) interaction on rows is to open a summary tray
Each name cell is linked to the detail view and has an "Eye" icon (to make it more obvious that it can be clicked)
The secondary (i.e. Shift-Click) interaction on rows is to navigate to a detail view (the "Eye" icon from the name cell should have a tooltip explaining this shortcut)
The "View details" item will be removed from all three-dot "More" dropdown menus (as it’ll be redundant)
We’ll likely add the "More" dropdown menus to summary trays (this should be follow up work)


Create contributing.md

Successfully added contribution instructions.
closes #33

@PradnyaGaitonde Sorry, but someone else was working with the contribution.md and has opened a PR before you. So, I have to merge his PR.

Hey. @PradnyaGaitonde I am Merging Your PR. As, @sethshivam11 Mentioned, Someone else was Working but You Raised the Issue Earlier. It was Our Fault that we were confused.
So, I am Merging Your PR. Thanks !! Happy Coding !! 😊

@PradnyaGaitonde yes sorry for the confusion


Unable to see UDFs

SQL Operations Studio Version: sqlops 0.23.6 (8a3011756318a2ded1e6e84332230a2b2bf9c544, 2017-11-06T21:51:43.232Z)
OS Version: Windows_NT x64 10.0.16299

When searching for functions  using the search box of browsing using the Servers pallet  I can't find any!
My database is a P2 Azure SQL DB compatibility level 110 and I am an server admin. No security issues.
The functions do show up when browsing using SSMS.
Steps to Reproduce:

Open SQL Operations Studio
Search or browse for UDFs

This may be related to #595 where inline functions do not show up in Object Explorer but other kinds of user defined functions do.

Closing since we don't have an active repro for this.  Please reactive if this is still an issue.  Thanks!


Add basic example of login with Firebase in Kotlin branch #dev-firebase-login-kotlin

Along with example of firebase login, do it using both custom UI as well as Firebase UI. And make sure to add examples of login using email id and phone numbers also.


Package restore requirement on opening project and many builds is unsustainable.

Thanks for your interest in .NET Core.
Please note that this repo (dotnet/core) is not for filing product issues. Here are some repos where you can file an issue:

dotnet/cli - for CLI tools and questions
dotnet/corefx - for API issues and questions
dotnet/coreclr - for runtime issues
nuget/home - for NuGet questions and issues

Hi @CampsiteHelper , can you help clarify what you are seeing and what you would expect instead?
/cc @rrelyea @livarcocc

Please file a new issue with more info. It is fine to file it here.


[18.09] X-Server fails to start since latest update

Issue description
I cannot start my X server since the latest stable channel update.
The channel was forwarded: 235487585ed to 4c0be408155.
All relevant updates I see are kernel updates (I'm running 4.14 LTS kernel). But maybe I'm missing something.
The journal tells me:
[...]
Mär 04 07:32:46 terry display-manager[1281]: (II) No input driver specified, ignoring this device.
Mär 04 07:32:46 terry display-manager[1281]: (II) This device may have been added with another device file.
Mär 04 07:32:46 terry display-manager[1281]: (II) config/udev: Adding input device (unnamed) (/dev/tty8)
Mär 04 07:32:46 terry display-manager[1281]: (II) No input driver specified, ignoring this device.
Mär 04 07:32:46 terry display-manager[1281]: (II) This device may have been added with another device file.
Mär 04 07:32:46 terry display-manager[1281]: (II) config/udev: Adding input device (unnamed) (/dev/tty9)
Mär 04 07:32:46 terry display-manager[1281]: (II) No input driver specified, ignoring this device.
Mär 04 07:32:46 terry display-manager[1281]: (II) This device may have been added with another device file.
[...]

Steps to reproduce
Not sure.
(Edit: Running a ThinkPad X220 here, maybe someone can reproduce with this information alone)
Technical details

system: "x86_64-linux"
host os: Linux 4.14.104, NixOS, 18.09.2292.4c0be408155 (Jellyfish)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.1.3
channels(root): "nixos-18.09.2292.4c0be408155"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

More information can be provided, of course.
Pinging
Pinging stable channel maintainers and kernel guys here.
@NeQuissimus updated the 4.14 kernel in this cycle.
Other kernel people: @dezgeg @FRidh (just taking randomly two instead of pinging all of you).

If this becomes important: The kernel was updated from 4.14.102 to 4.14.104. The kernel log can be shown with this:
# in the kernel repository
$ git remote add stable git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
$ git fetch stable linux-4.14.y
$ git log --oneline 5461ace2e2f7..30921fc1e5fc

Any chance your services.xserver.videoDriver is incorrect?
I have not seen any issues with the updated kernels yet.

I did not change (nor touch) this setting on this device:
$  git log --grep videoDrivers --format="%ai"
2016-05-24 11:42:52 +0200
2016-05-24 11:41:38 +0200
2016-05-22 18:46:19 +0200

(II) lines from X log tend to have low importance.  Are there no (EE) or at least (WW) lines?  I have logs (also) in /var/log/X.0.log{,.old}.

$ journalctl -b -1 | grep -E "(EE|WW)"
Mär 04 07:31:18 terry kernel: DMI: LENOVO 4290A11/4290A11, BIOS 8DET66WW (1.36 ) 10/22/2012
Mär 04 07:31:19 terry kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Mär 04 07:31:19 terry kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Mär 04 07:31:19 terry kernel: thinkpad_acpi: ThinkPad BIOS 8DET66WW (1.36 ), EC unknown
Mär 04 07:31:21 terry smartd[785]: Device: /dev/sda [SAT], Samsung SSD 850 PRO 256GB, S/N:S251NX0HC00131F, WWN:5-002538-8402a77a3, FW:EXM02B6Q, 256 GB
Mär 04 07:31:21 terry display-manager[844]:         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Mär 04 07:31:21 terry display-manager[844]: (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
Mär 04 07:31:21 terry display-manager[844]: (WW) Falling back to old probe method for cirrus
Mär 04 07:31:21 terry display-manager[844]: (WW) Falling back to old probe method for modesetting
Mär 04 07:31:21 terry display-manager[844]: > Internal error:   Could not resolve keysym XF86WWAN
Mär 04 07:31:22 terry display-manager[844]: > Internal error:   Could not resolve keysym XF86WWAN
Mär 04 07:31:26 terry display-manager[974]:         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Mär 04 07:31:26 terry display-manager[974]: (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
Mär 04 07:31:26 terry display-manager[974]: (WW) Falling back to old probe method for cirrus
Mär 04 07:31:26 terry display-manager[974]: (WW) Falling back to old probe method for modesetting
Mär 04 07:31:26 terry display-manager[974]: > Internal error:   Could not resolve keysym XF86WWAN
Mär 04 07:31:26 terry display-manager[974]: > Internal error:   Could not resolve keysym XF86WWAN
Mär 04 07:31:32 terry display-manager[1071]:         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Mär 04 07:31:32 terry display-manager[1071]: (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
Mär 04 07:31:32 terry display-manager[1071]: (WW) Falling back to old probe method for cirrus
Mär 04 07:31:32 terry display-manager[1071]: (WW) Falling back to old probe method for modesetting
Mär 04 07:31:32 terry display-manager[1071]: > Internal error:   Could not resolve keysym XF86WWAN
Mär 04 07:31:32 terry display-manager[1071]: > Internal error:   Could not resolve keysym XF86WWAN
Mär 04 07:31:40 terry kernel: Hardware name: LENOVO 4290A11/4290A11, BIOS 8DET66WW (1.36 ) 10/22/2012
Mär 04 07:31:40 terry kernel: Hardware name: LENOVO 4290A11/4290A11, BIOS 8DET66WW (1.36 ) 10/22/2012
Mär 04 07:31:40 terry kernel: Hardware name: LENOVO 4290A11/4290A11, BIOS 8DET66WW (1.36 ) 10/22/2012
Mär 04 07:32:26 terry display-manager[1208]:         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Mär 04 07:32:26 terry display-manager[1208]: (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
Mär 04 07:32:26 terry display-manager[1208]: (WW) Falling back to old probe method for cirrus
Mär 04 07:32:26 terry display-manager[1208]: (WW) Falling back to old probe method for modesetting
Mär 04 07:32:26 terry display-manager[1208]: > Internal error:   Could not resolve keysym XF86WWAN
Mär 04 07:32:26 terry display-manager[1208]: > Internal error:   Could not resolve keysym XF86WWAN
Mär 04 07:32:46 terry display-manager[1281]:         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Mär 04 07:32:46 terry display-manager[1281]: (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
Mär 04 07:32:46 terry display-manager[1281]: (WW) Falling back to old probe method for cirrus
Mär 04 07:32:46 terry display-manager[1281]: (WW) Falling back to old probe method for modesetting
Mär 04 07:32:46 terry display-manager[1281]: > Internal error:   Could not resolve keysym XF86WWAN
Mär 04 07:32:46 terry display-manager[1281]: > Internal error:   Could not resolve keysym XF86WWAN

$ ls /var/log | grep X | wc -l
0

Hmm, I can't see anything fishy in there either :-/

It sounds more and more like a kernel bug, at least to me (hint: I have no experience with kernel bugs, so maybe this is stupid).
How to proceed?

Looking at diff between the two commits, kernel seems the most likely.  Without some concrete info like logs, it seems hard to report anywhere, so I would most likely try to find the particular commit causing this.  Bisection should work in the worst case.  One may be able to tip-off the candidate by looking at commit log, but I probably can't do that confidently, and log2 grows so slowly...

I have just opened somehow similar issue: https://github.com/NixOS/nixpkgs/issues/57014
(though my X server is starting but freezes right afterwards)
Mine problem was in "removing obsolete xorg.conf" during switching to a new generation:
removing obsolete symlink ‘/etc/X11/xkb’...
removing obsolete symlink ‘/etc/X11/xorg.conf’...

Can it be that you have the same problem?
Hotfix is to copy the old xorg.conf to the new generation.

There should be another kernel bump incoming.

Can it be that you have the same problem?

I don't know ... I guess journalctl does not give me the nixos-rebuild logs, right?

There should be another kernel bump incoming.

I'll wait for that.

Does the same happen with 4.19?

I'll test after the 4.14 bump if it doesn't work.

According to http://howoldis.herokuapp.com/ you should be getting 4.14.105 already

(The following might be completely false. Take a big grain of salt NOW):
So what I see in the diff (git diff --name-only) is that there are changes in drivers/gpu. All other stuff (like security or arch) seem to be not relevant here from my understanding.
If we take that as a starting point, we're down to 2 (two) patches that changed the kernel in drivers/gpu between 4.14.102 and 4.14.104:
6964c1d5062d drm/i915/fbdev: Actually configure untiled displays
170c71065fec drm/meson: add missing of_node_put

But the commit messages and the code do not help (at least me).

I don't know ... I guess journalctl does not give me the nixos-rebuild logs, right?

I'm not sure, but you can try copying xorg.conf from the working generation (or rebuild generation) to verify if it is the problem.

Unfortunately, I get the same error with kernel 4.14.105

I will now test with kernel commit 6964c1d5062de1fb26864f59b41a5ad00f641db9 reverted. Maybe it's a lucky shot.

 I compiled for two hours... And when I tried to boot it tells me that it cannot find the fuckin /dev/sda
Yeah thanks, I'm going to the club now

So after a night of thinking, I wonder why my custom kernel does not boot. Because all that is (should be) different is the kernel, build with one damn patch reverted... why doesn't it find the root filesystem? Of course you guys cannot tell me why, but it feels somewhat strange, I think you understand...

Okay, now the fun beginns:
I tried the following:

Updating the channel (to 37694c8cc0)
git checkout the configuration from the last update that worked
build the system
reboot
works

Damn.
Now here's my config diff from "works" to "doesn't work" (excluding some private stuff):
$ git diff HEAD..master  --name-only
nixos/lucy.nix
nixos/pkgs/desktopPackages.nix
nixos/programs/utils.nix
nixos/services/x-noautostart.nix
nixos/services/x.nix
nixos/terry.nix
vdirsyncer/config

$ git diff HEAD..master -- nixos/
[ excluded because different machine: /nixos/lucy.nix ]
diff --git a/nixos/pkgs/desktopPackages.nix b/nixos/pkgs/desktopPackages.nix
index c3af2c8..39e02b8 100644
--- a/nixos/pkgs/desktopPackages.nix
+++ b/nixos/pkgs/desktopPackages.nix
@@ -15,9 +15,6 @@ let
     ((utils pkgs).optimizeForThisHost (muttWithoutThings pkgs)
     );

-  xfce4term = pkgs:
-    (utils pkgs).optimizeForThisHost pkgs.xfce4-12.xfce4terminal;
-
 in
 pkgs: [
   pkgs.acpi
@@ -59,35 +56,6 @@ pkgs: [
   pkgs.youtube-dl
   pkgs.zathura

-  # Packages for desktop env
-  #pkgs.xfce4-12.xinitrc
-  pkgs.arc-icon-theme
-  pkgs.arc-theme
-  pkgs.adapta-gtk-theme
-  pkgs.papirus-icon-theme
-  pkgs.xfce.xfce4_xkb_plugin
-  pkgs.xfce4-12.gtk-xfce-engine
-  pkgs.xfce4-12.xfce4-sensors-plugin
-  pkgs.xfce4-12.xfce4_appfinder
-  pkgs.xfce4-12.xfce4_genmon_plugin
-  pkgs.xfce4-12.xfce4_battery_plugin
-  pkgs.xfce4-12.xfce4_datetime_plugin
-  pkgs.xfce4-12.xfce4_mpc_plugin
-  pkgs.xfce4-12.xfce4_mailwatch_plugin
-  pkgs.xfce4-12.xfce4_timer_plugin
-  pkgs.xfce4-12.xfce4_power_manager
-  pkgs.xfce4-12.xfce4icontheme
-  pkgs.xfce4-12.xfce4mixer
-  pkgs.xfce4-12.xfce4notifyd
-  pkgs.xfce4-12.xfce4panel
-  pkgs.xfce4-12.xfce4session
-  pkgs.xfce4-12.xfce4settings
-  (xfce4term pkgs)
-  pkgs.xfce4-12.xfce4volumed
-  pkgs.xfce4-12.xfconf
-  pkgs.xfce4-12.xfdesktop
-  pkgs.xfce4-12.xfwm4
-
   pkgs.plymouth

   # Finance packages
diff --git a/nixos/programs/utils.nix b/nixos/programs/utils.nix
deleted file mode 100644
index e76fb7a..0000000
--- a/nixos/programs/utils.nix
+++ /dev/null
@@ -1,16 +0,0 @@
-{
-  makei3config = { alacrittyConfigFilePath, i3Config }:
-    (builtins.toFile "i3.conf" ''
-      ${i3Config}
-
-      # start a terminal
-      bindsym Mod4+Return exec xterm -bg grey10 -fg grey90
-
-      # start a terminal in floating mode
-      bindsym Mod4+Shift+Return exec xterm -bg grey10 -fg grey90 -geometry 80x24 -class "floating_term" -name "floating_term"
-      for_window [class="floating_term"] floating toggle
-
-      exec xterm -bg grey10 -fg grey90
-    '');
-
-}
[ excluded because not in configuration: /nixos/services/x-noautostart.nix ]
diff --git a/nixos/services/x.nix b/nixos/services/x.nix
index 1b5cd32..b335e14 100644
--- a/nixos/services/x.nix
+++ b/nixos/services/x.nix
@@ -1,7 +1,4 @@
-{ pkgs
-, i3Config
-, ...
-}:
+{ pkgs, configDir, ...  }:

 {
   autorun    = true;
@@ -21,6 +18,6 @@

   windowManager.i3 = {
     enable = true;
-    configFile = i3Config;
+    configFile = "${configDir}/i3/config";
   };
 }
diff --git a/nixos/terry.nix b/nixos/terry.nix
index 888d83e..3102c6b 100644
--- a/nixos/terry.nix
+++ b/nixos/terry.nix
@@ -23,16 +23,6 @@ let
     sidebar
   ];

-  # Funny shit here: We generate a custom alacritty config per hostName
-  #
-  # That config is then used in the i3Config for the bindings for starting
-  # terminals
-  #
-  # And that config is then used in the x-server service configuration for i3
-  alacrittyConfig = import ./programs/alacritty.nix { textsize = "7.0"; };
-
-  defaulti3Config = (builtins.readFile ../i3/config);
-
   utils = import "${configDir}/programs/utils.nix";
 in

@@ -71,12 +61,9 @@ in
   boot.initrd.luks.cryptoModules = [ "aes" "sha256" "sha1" "cbc" ];

   services.xserver = (import "${configDir}/services/x.nix" {
-      pkgs = pkgs;
-      i3Config = (utils.makei3config {
-        i3Config = defaulti3Config;
-        alacrittyConfigFilePath = alacrittyConfig;
-      });
-    });
+    pkgs = pkgs;
+    configDir = configDir;
+  });

   networking = {

@@ -98,7 +85,6 @@ in
     CONFIG_DIR  = "/home/m/config";
     HOST_COLOR  = ''\e[1;30m'';
     EDITOR      = "vim";
-    TERMINAL    = "xfce4-terminal";
   };

   # Program configuration

So from what I see (and maybe I'm missing something, but I looked really hard several times) I do not see anything that could cause the xserver to crash on startup. I removed some xfce packages from my configuration, removed some utility functions, removed alacritty-config-building and removed an environment variable. Nothing that could cause an xserver to crash, right?

Either way, this seems not to be a kernel bug (thank god!), so please @NeQuissimus remove the kernel label.

I don't know why, but this fixes my problem (tested with nixos-rebuild build-vm && ./result/bin/run-terry-vm):
diff --git a/nixos/services/x.nix b/nixos/services/x.nix
index b335e14..8af015c 100644
--- a/nixos/services/x.nix
+++ b/nixos/services/x.nix
@@ -1,4 +1,4 @@
-{ pkgs, configDir, ...  }:
+{ pkgs, ...  }:

 {
   autorun    = true;
@@ -16,8 +16,5 @@
     };
   };

-  windowManager.i3 = {
-    enable = true;
-    configFile = "${configDir}/i3/config";
-  };
+  windowManager.i3.enable = true;
 }

With references like this I'm often unsure whether I get reference to the source path or to a copy inside the nix store :-)  but perhaps that wouldn't make a difference in your case?

Yeah, maybe that was the issue. configDir is set to /home/m/config, but if that is joined onto a nix path it might end up being /nix/store/somehash-foo/home/m/config, ... Maybe putting the config into the store in this step would be the right thing to do here.


Adds prototype implementation of an Incentive System

This is now superseded by https://github.com/cryptimeleon/uacs-incentive-system using the new APIs


Only the first action runs when multiple actions are selected

For example, with the following sequence of actions, only 1 and 2 run (3 does not run):

Select All
Mark as Complete
Lock

On hold due to #265

Replaced by #265


Fix: Remove sort when matching metric is removed

Description
When removing a metric in the new column config, any matching sorts are not removed, causing Fili API errors
Proposed Changes

Add corresponding consumer for REMOVE_METRIC_FRAGMENT in sort consumer.

License
I confirm that this contribution is made under an MIT license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

I'll just go ahead and fix that now in this PR.


Remove deprecated set_validator from Parameter

@jenshnielsen  i will rebase+push after https://github.com/QCoDeS/Qcodes/pull/1859 is merged


Bump metal go to v0.9.2

v0.9.1 breaks prior clients because firewall find request now has a POST body.

obsoleted by #97


I keep getting this "Realm accessed from incorrect thread"

Hello,
I've just started using this library. I am running into
libc++abi.dylib: terminating with uncaught exception of type realm::IncorrectThreadException: Realm accessed from incorrect thread.
I tried calling my realm operations only from a main thread, but to no avail.
func removeGotOffer(row: Int) {
        Async.main {
            let offerCode = self.offers[row].code
            try! self.db.operation({ (context, save) -> Void in
                guard let offer = try! context.request(Offer.self).filteredWith("code", equalTo: offerCode).fetch().first else {
                    debugPrint("Couldn't find the required offer to delete")
                    return
                }
                _ = try? context.remove(offer)
                save()
            })
        }
    }

Hi @sasikiran . I've detected a bug with the current implementation. Because it uses an already existing context that was created on a different thread. I'll fix it and push the fix as soon as possible.

Thanks!
On Tue, Aug 23, 2016 at 1:59 PM Pedro Piñera Buendía <
<EMAIL_ADDRESS>wrote:

Hi @sasikiran https://github.com/sasikiran . I've detected a bug with
the current implementation. Because it uses an already existing context
that was created on a different thread. I'll fix it and push the fix as
soon as possible.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pepibumur/SugarRecord/issues/271#issuecomment-241662644,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABRWXDOuXfnJ4QxSxi2witkg78uFzFrNks5qiq9sgaJpZM4JpxGu
.

@sasikiran could you try with the last version of SugarRecord?

Closing the issue, couldn't reproduce it and got no input from the user.

is there some one has solved this problem ??

@pepibumur
@sasikiran


Concurrency safety parallelisation

Hi all,
I have a problem where in order to evaluate an individual I need to write a file to disk, execute a program, and read the file. In order to safely parallelise, I need to be able to write the files with distinct name for each pop individual, i.e. something like this
file_path = f"/tmp/{point_id}"
with(f"{file_path}.in", "w") as f:
   f.write(x)
_ = subprocess.run([mysofware, f"/tmp/{point_id}.in", "f/tmp/{point_id}.out", capture_output=True)
with(f"{file_path}.out","w") as f:
    output = f.read()

however, looking at all possible ways of running pymoo (minimize, ask and tell, etc) I don't seem to have any way of having a (at least per generation) unique identifier of a candidate solution so that file_path is unique and I don't have concurrency issues, and therefore can't parallelise my evaluate.
Am I missing something?
Cheers

Sorry, just realised that Problem, instead of ElementWiseProblem accepts a whole pop, so I can in principle parallelise inside the _evaluate method. Is this currect?

yes exactly this is how pymoo is designed!
Please reopen if this does not resolve your issue.


Open Classifieds

Could we add Open-classifieds.com to the showcase?  https://github.com/open-classifieds/openclassifieds2 you can read a bit more about FOSS for profit here too http://open-classifieds.com/2014/02/03/how-we-make-money-open-source-for-profit/
We earn from consultancy, themes and since 1 year ago SaaS https://yclas.com/
thanks

hi! Apologies for the slow response. Which funding category would this best fit into? (Ideally, whichever method is covered most comprehensively in your blog post, so others can learn)

Right now SaaS, but many times we earn from consultancy ;)

ok- this one feels a bit fuzzy to me (ex. in your post you have a section that says "why not SaaS", but you currently earn from SaaS), so I don't think it'll be the most clear-cut example to showcase, especially given that the SaaS category already has a bunch of clearer examples. I appreciate the suggestion though! Apologies this has taken me awhile to resolve. I'm going to close this issue.


"Timeout reading from socket" error in network stability health check stacktrace

scenario

create environment with two nodes
remove node_2 (not from the api)
get node_1 healthcheck

result
Error TimeoutError: Timeout reading from socket

software version
master : 4768508

Fixed by making sure the healthcheck only runs when we can ping the nodes

Software Version
7c9ffb9d081915770442d3955223406bfaf73f03


Ability to add Helper Text to Import Column

Description

This PR introduces an optional method for adding helperText() to ImportColumn. This functionality is particularly useful for providing instructions prior to validation.
ImportColumn::make('associated_skus')
                ->label('Associated SKUs')
                ->requiredMapping()
                ->helperText('Comma separated list of SKUs')

[X] Visual changes (if any) are shown using screenshots/recordings of before and after.

Code style

[X] composer cs command has been run.

Testing

[X] Changes have been tested.

Documentation

[X] Documentation is up-to-date.

Thanks


checkpoint is failing on Fedora 23

Currently the test suite of runc is based on a ubuntu docker image (runc/script/test_Dockerfile). I am trying to write a Dockerfile, runc/script/test_Dockerfile_1, for testing runc on fedora 23.
You can find test_Dockerfile_1 here: https://github.com/hmeng-19/logs/blob/master/test_Dockerfile_1
test_Dockerfile_1 tries to mimic the summary of the following two ubuntu-oriented Dockerfiles:

https://github.com/docker-library/golang/blob/d7e2a8d90a9b8f5dfd5bcd428e0c33b68c40cc19/1.5/alpine/Dockerfile
https://github.com/opencontainers/runc/blob/master/script/test_Dockerfile

The docker image is created successfully after docker build:
docker build -t runc_test:fedora -f script/test_Dockerfile_1 .

However, TestCheckpoint for checkpoint_test.go failed for both the test commands:
docker run -e TESTFLAGS -ti --privileged --rm -v /home/hmeng/go/src/github.com/hmeng-19/runc:/go/src/github.com/opencontainers/runc runc_test:fedora make localunittest
docker run -e TESTFLAGS -t --privileged --rm -v /home/hmeng/go/src/github.com/hmeng-19/runc:/go/src/github.com/opencontainers/runc runc_test:fedora make localintegration

The output of docker run .... make localunittest is here: https://github.com/hmeng-19/logs/blob/master/localunittest.log . The failure happened at TestCheckpoint, starting from line 267.
The output of docker run .... make localintegration is here: https://github.com/hmeng-19/logs/blob/master/localintegration.log . The 3rd test failed.
Clearly, both of these two failures are related to checkpoint and restore function of runc. As for as I see, there may have two reasons for the failure:

The test_Dockerfile_1 file does not completely mimic the original ubuntu-oriented test_Dockerfile. This may happen because some packages mentioned in ubuntu-version Dockerfile, such as build-essential and python-minimal are difficult to mapped to fedora packages.

The setting of fedora:23 docker image relavant to the checkpointing and restoring function does not match the setting on ubuntu.

Some other reasons I did not realize?

@mrunalp, @rhatdan , I moved this issue to my own fork.
Hope it does not create too much confusion on the upstream.

@rhatdan , the test using the default Ubuntu Dockerfile can finish successfully on my Fedora system.
docker run -e TESTFLAGS -ti --privileged --rm -v /home/hmeng/go/src/github.com/hmeng-19/runc:/go/src/github.com/opencontainers/runc runc_test make localunittest
docker run -e TESTFLAGS -t --privileged --rm -v /home/hmeng/go/src/github.com/hmeng-19/runc:/go/src/github.com/opencontainers/runc runc_test make localintegration

Ok lets look at this on Monday.

@rhatdan , the problem was solved.
I double-checked all the dependencies listed on the criu's installation page (https://criu.org/Installation), and added the following deps into test_Dockerfile_fedora. However, I think the real deps we were missing yesterday is libnl3 and libnl3-devel.
libnl3
libnl3-devel
glibc-devel.i686
iproute
protobuf-c
protobuf-python
python-ipaddr

Nice!
Sent from my iPhone

On Jun 7, 2016, at 7:25 AM, hmeng-19<EMAIL_ADDRESS>wrote:
@rhatdan , the problem was solved.
I double-checked all the dependencies listed on the criu's installation page (https://criu.org/Installation), and added the following deps into test_Dockerfile_fedora. However, I think the real deps we were missing yesterday is libnl3 and libnl3-devel.
libnl3
libnl3-devel
glibc-devel.i686
iproute
protobuf-c
protobuf-python
python-ipaddr
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Awesome job.  Now show me it working on RHEL and Centos.  :^)
Then we have to talk about whether we want to have this happen by default like we do with docker.

As for RHEL docker images, do we have some internal package repository I can use?
Running yum install <package_name> inside a docker RHEL container fails without registering the RHEL correctly:
+ yum -y install bash ca-certificates gcc glibc-devel glibc-devel.i686 make openssl tar wget
Loaded plugins: fastestmirror
Determining fastest mirrors
There are no enabled repos.
 Run "yum repolist all" to see the repos you have.
  You can enable repos with yum-config-manager --enable <repo>

Currently I am pulling the base RHEL7 docker image from  docker.io/thezxm/redhat7:latest.
Do we have some image registry where I should pull the base RHEL docker image from?

On 06/07/2016 05:22 PM, hmeng-19 wrote:

Currently I am pulling the base RHEL7 docker image from
|docker.io/thezxm/redhat7:latest|.
Do we have some image registry where I should pull the base RHEL
docker image from?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hmeng-19/runc/issues/1#issuecomment-224418659, or
mute the thread
https://github.com/notifications/unsubscribe/AB6Hw7LvSY-0I44m6fHbAYNlAMoBKjZlks5qJeEUgaJpZM4ItvHZ.

You need to setup credentials via rhn to test this.

@rhatdan , I am not sure I caught your point.
According to https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/version-7/getting-started-with-containers/#get_started_with_docker_formatted_container_images, it
seems that the host should be RHEL 7 and register properly to support Docker RHEL images.
Using the RHEL 7 subscription model, if you want to create Docker images or
containers, you must properly register and entitle the host computer on which
you build them. When you use yum install within a container to add packages,
the container automatically has access to entitlements available from the RHEL
7 host, so it can get RPM packages from any repository enabled on that host.

@rhatdan , @mrunalp , considering I do not have a RHEL 7 server to work on,  I plan to give RHEL 7 atomic host a try following the instruction here https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/7/installation-and-configuration-guide .
Let me know if this is the right thing to do.

You can try to use this http://developers.redhat.com/blog/2016/03/31/no-cost-rhel-developer-subscription-now-available/
Sent from my iPhone

On Jun 8, 2016, at 8:35 AM, hmeng-19<EMAIL_ADDRESS>wrote:
@rhatdan , @mrunalp , considering I do not have a RHEL 7 server to work on, I plan to give RHEL 7 atomic host a try following the instruction here https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/7/installation-and-configuration-guide .
Let me know if this is the right thing to do.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

It seems that runc starts using golang 1.6.
My next step will be update the test_Dockerfile_fedora to use golang 1.6.

@mrunalp , I tried running the tests of runc the RHEL 7 provided by http://developers.redhat.com/products/rhel/get-started/#tab-kvm .
Even the test_Dockerfile for ubuntu failed with some errors about nsenter on RHEL 7 virtual machine.  However, these tests work fine on my own machine.
For now, I plan to focus on test_Dockerfile_fedora and test_Docker_centos. Sounds good?

@hmeng-19 I have created PRs to runc for both the test failures that you reported in #2 Thanks!

@hmeng-19 Can you create an issue for what errors you are seeing on RHEL 7? I can take a look. Also, meanwhile making progress on test_Dockerfile_fedora and test_Docker_centos sounds good.

@mrunalp , sounds good. Thanks for the quick fixing.
The runc test inside my RHEL 7 VM today broke the VM heavily, I plan to reinstall the RHEL 7 VM and test the new runc master after your PRs are merged into the master tomorrow.

@mrunalp , I filed the problem I met during the execution of make test on a RHEL 7 VM at #4 .


Unit test failed and crashed under Swift Package + iOS Simulator

Hi there,
In my framework https://github.com/liuxuan30/TelloSwift, I created swift package file and tried to run UT on macOS and iOS Simulator.
the macOS passed, however every time I ran on iOS Sim, it always crashes inside nio. Running same tests in original xcode project on both iOS and macOS passed without problem, which makes me very confused
the crash:

Can someone help, if this is a nio bug, or Xcode UT bug?

@liuxuan30 thanks for reporting. This sounds very much like https://bugs.swift.org/browse/SR-11564 . Can you confirm the following:

you're on Xcode 11.2.x or 11.3 beta
this only happens on device or in simulator, not on macOS
if you set DEAD_CODE_STRIPPING=NO in your Xcode project then this doesn't happen either

Hi @weissi yes I'm on 11.2.1 from AppStore build;
This only happens on iOS simulator, and under Swift Package xcode project, not regular (the regular is perfectly running tests)
where to set DEAD_CODE_STRIPPING?
I set it in Swift package "Run scheme", still crashes

@liuxuan30 you need to

Select your project on the left side in Xcode
Click on 'build settings'
Select the project up top
under "Linking", go to "Dead Code Stripping"
set it to "No"

like here, make sure that in both cases the project itself is selected

@weissi
Some context:
In my original Xcode project, they are YES, and the tests runs perfectly on iOS simulator;
I have set them all to NO, including the PROJECT and TARGETS, and then bring up the swift package Xcode project, it still crashes;
I think the problem is I cannot see build setting for a swift package project, there is no place to click like a regular xcodeproj:

@liuxuan30 oh yes, with a Swift package I don't know how to change that. You could temporarily use the old school swift package generate-xcodeproj and set it there

@liuxuan30 another thing that may help would be this: Once it has crashed, type in the (lldb)  console in the bottom right:
command script import lldb.macosx.crashlog
save_crashlog /tmp/crash.txt

and then attach /tmp/crash.txt here.

crash.txt
crash text here you go

@liuxuan30 thanks! this is 99.9% the bug I mentioned:
Thread 5:
0   TelloSwiftTests                  0x000000010f622032 method descriptor for TelloSwift.TelloCommandHandler.write(context: NIO.ChannelHandlerContext, data: NIO.NIOAny, promise: Swift.Optional<NIO.EventLoopPromise<()>>) -> ()
1   None                             0x000070000b7a4560 None

we're trying to execute the method descriptor which is data. The same happened for example in

https://github.com/apple/swift-nio/issues/1227
https://github.com/grpc/grpc-swift/issues/623
https://github.com/grpc/grpc-swift/issues/605

sure, much appreciated your help. So we just sit tight and wait for https://bugs.swift.org/browse/SR-11564 to be fixed?

but one weird thing is the normal Xcode tests passed all the time, even with Dead Code Stripping is YES

@liuxuan30 what do you mean with 'the normal Xcode tests'? I think the bug is a bit random, it doesn't always cause an issue and it doesn't always hit the same piece of code :(

@liuxuan30 could you try with Xcode 11.1?

@liuxuan30 what do you mean with 'the normal Xcode tests'? I think the bug is a bit random, it doesn't always cause an issue and it doesn't always hit the same piece of code :(

The normal tests means, running the exact same tests in original .xcodeproj, it passes all the time in my memory, as well as travis CI, you can check it in my project repo. But the swift package project will fail 100%
I'm not able to try 11.1 :( sorry

Sorry, I wasn't quite precise enough: I meant random as in it depends on the binary. With the same binary, the crash will always be the same.
Can you try this from the command line:
cd TelloSwift # go to your checkout (where your Package.swift lives)
xcodebuild -scheme swift-nio-Package test -destination "id=$(xcrun simctl list -j devices iPhone\ 11\ Pro\ Max available | grep udid | cut -d '"' -f4)" DEAD_CODE_STRIPPING=NO

what happens if you do that?

Hi @weissi sorry for the late reply.
running

xcodebuild -scheme TelloSwift test -destination "id=$(xcrun simctl list -j devices iPhone\ 11\ Pro\ Max available | grep udid | cut -d '"' -f4)" DEAD_CODE_STRIPPING=NO

seems passed without problem.

@liuxuan30 what happens if you re-run the above command but remove the DEAD_CODE_STRIPPING=NO argument?

@weissi the tests passed as well without DEAD_CODE_STRIPPING=NO

I'm seeing a new Xcode 13.3, when it's installed I will try again.

thank you!

it seems Xcode 11.3 indeed fixed this issue :) good day


[BUG] Ensure energy buffer is retained when changing/upgrading capacitor.

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Currently removal of capacitor voids energy.
Expected Behavior
It might be nice for the energy to be conserved.
Steps To Reproduce
No response
Environment
No response
Anything else?
No response

Should energy be stored in the machine in a locked state or should it be attached to the cap ?

I thought about attaching to the cap, but i dont know if that kinda ruins upgrades, and i dont really wanna write a machines energy to an itemstack. Maybe just storing the buffer internally is better

How should it be handled if the cap is a downgrade?
How about the capacitor is getting "charged" and all machines have the same capacity with the same type of capacitor. In this case the capacitor is acting like the internal power storage of the machine.

Fixed in dev, but requires LTS backport.

Backported.


flex-nowrap safari 9

Found a problem with displaying flex-nowrap in Mobile Safari 9 IPad A iOS 9.3.5 operating system. You can see in the screenshot below as content flex-item is abnormally compressed in columns.

URL documentation https://getbootstrap.com/docs/4.1/utilities/flex/#wrap

@MartijnCuppens can you reproduce on BrowserStack?

Closing due to lack of response. You can comment here and we can re-open the issue.
This is an automated reply


build: incdir.sh shouldn't check whether the path exist

since compiler never complain that the path(by -I) doesn't exist
Signed-off-by: Xiang Xiao<EMAIL_ADDRESS>Summary
Impact
Testing

This patch make the conversoin from:
ARCHXXINCLUDES = -isystem "${shell cygpath -w $(TOPDIR)$(DELIM)include$(DELIM)cxx}"

to:
ARCHXXINCLUDES += ${shell $(INCDIR) -s "$(CC)" $(TOPDIR)$(DELIM)include$(DELIM)cxx}

don't complain that include\cxx doesn't exist.


Merge nRF and nRF Connect Dockerfiles

Problem
As @rwalker-apple pointed out in #1529 Dockerfiles for nrf and nrfconnect platforms share some dependencies, so the scripts might be merged to avoid maintenance burden related to the need to update them both in the future.
Summary of Changes

nrf and nrfconnect Dockerfiles merged into a single multi-stage Dockerfile
change in integrations/docker/build.sh to support selection of a target from a multi-stage Dockerfile.

fixes #1549

Are the images sufficiently different to warrant separate  docker images?
I originally understood the merge request as 'build single dockerfile for all nRF development'. This PRs generates the same output except that it uses a single dockerfile ... for me updating docker seems to have become more complex as a result instead of easier.

Are the images sufficiently different to warrant separate docker images?
I originally understood the merge request as 'build single dockerfile for all nRF development'. This PRs generates the same output except that it uses a single dockerfile ... for me updating docker seems to have become more complex as a result instead of easier.

Hmm... The reason I thought it would be better to have separate images is that nRF Connect SDK adds over 1GB of files which are irrelevant for someone who wants to use nRF5 SDK. And similarly the other way around (although nRF5 SDK adds a bit less). I understood that the merge was requested to avoid the need to update two Dockerfiles instead of one when it's necessary to update toolchain etc. and I couldn't find an easier way to meet those two requirements other than using a multi-stage dockerfile (since Docker doesn't support any "include other Dockerfile" functionality).
If it's still controversial I can create a single nRF docker image and if we decide we can make developers' lives easier by publishing a minimal nRF Connect SDK image we can probably maintain it on Nordic side. Let me know if that's ok.

This isn't the way I was expecting this to come out.  I would have been happier with an image that has both SDKs and exports all the env vars (they don't conflict).
@Damian-Nordic if you feel strongly that these environments should be separate, I'd prefer that you refactored according to the pattern already in place here:

construct a base image directory (with a run.sh, build.sh, and Dockerfile) that contains the common deb packages
construct an image directory for each of the environments that FROM the base image directory

This isn't the way I was expecting this to come out. I would have been happier with an image that has both SDKs and exports all the env vars (they don't conflict).

As I mentioned before I just wanted the images to be smaller so that they would be faster to setup by users, but maybe that's not important, so I'll do what you propose.

This isn't the way I was expecting this to come out. I would have been happier with an image that has both SDKs and exports all the env vars (they don't conflict).

As I mentioned before I just wanted the images to be smaller so that they would be faster to setup by users, but maybe that's not important, so I'll do what you propose.

the proposal above of a "base" image with the common bits achieve the smaller images goal

the proposal above of a "base" image with the common bits achieve the smaller images goal

yes, I understand and thank you for that, but after second thought we should be fine with merging both nRF images and if the size becomes an issue we'll return to the proposal.


Fixes glfw/src/cocoa_platform.h:34:9: warning: 'GL_SILENCE_DEPRECATION' macro redefined [-Wmacro-redefined]

I build glfw from source, directly in my Xcode project, where I already have the GL_SILENCE_DEPRECATION macro defined.
Wrapping glfw's GL_SILENCE_DEPRECATION macro definition in an #ifndef removes the macro redefined warning.
Feel free to close if this is irrelevant for standard glfw usage (linking against built library), but it is useful for me.

Closing due to inactivity


Barometer Cal Seems to Get Stuck

So, it seems to me that if the barometer fails on the first try, it can never succeed.  Not sure why, but it seems to be a problem.

Also having this problem both with the flip32+ (with integrated baro) and with the flip32 (external baro).  It seems to happen on both, but more frequently with the external baro.  Below are some screen grabs of it happening on the flip32+ with onboard baro.  I didn't tell it to calibrate here, it just suddenly dove to a huge negative altitude.

Here I ran a rosservice call to calibrate the baro and it finally completed the calibration a minute later.  The whole time, the board was motionless so the "too much movement" thing wasn't due to the board actually moving or the pressure changing.

Yeah, we need to find a way to replicate this on the ground.  I'll dig into the i2c driver and see if there's still some issues there.

Great. The problem seems to be fairly easily replicated in my experience. The plots above were both from a plain flip32 at my desk with nothing else connected to it.

I just slowed down the barometer update a little bit, and am not leveraging the i2c queue as heavily.  Perhaps this will fix it.  @wynn4, can you confirm this fix on your hardware?  (fix_259 branch)

As an unrelated, but potentially useful fix, I just recently added support for the BMP280 barometer from the rev6 naze32.  This chip uses far less overhead on the i2c lines.  It might be be a little better about avoiding this issue.

This was merged into master (illegally)


getCurrentSelectionCfi() error when selection contains images.

Hello,
I'm trying to create annotations on selected content but when i want to get the CFI of a selection containing images, i get the following Uncaught SyntaxError.
Uncaught SyntaxError: Expected "!/", "/", "[" or [0-9] but "," found. in /lib/epub_cfi.js (1483)

Moved:
https://github.com/readium/readium-cfi-js/issues/31

Annotations_module needs to be tested with the newest CFI library.

Closing as per message above from Feb 6, 2015. For any problems related to "annotations_module", please open a new issue.


fix(deps): update icr.io/ext/logdna-agent docker tag to v3.8.9-20231106.f2f1aff739bf8115

This PR contains the following updates:

Package
Update
Change

icr.io/ext/logdna-agent
patch
3.8.9-20231030.1d91357d61b35ff6 -> 3.8.9-20231106.f2f1aff739bf8115

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

:tada: This PR is included in version 1.12.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Tightening of pydantic dependancy following release of v0.11.1

Describe the bug
The recent release changed the dependency of  pydantic  from "1.10.12" to  ">=1.10.12".
This is causing pipelines using data-diff to break, because of breaking changes with pydantic in version 2.
Would this version be more appropriate:
pydantic = ">=1.10.12, <2.0.0"

Appreciate the stance outlined here.
We don't use pydantic in our service and it feels peculiar for us to restrict a transitive dependency, but that may be my misunderstanding.

We don't use pydantic in our service

https://github.com/datafold/data-diff/blob/master/data_diff/dbt_config_validators.py#L3
Traceback (most recent call last):
  File "/tmp/myvenv/bin/data-diff", line 5, in <module>
    from data_diff.__main__ import main
  File "/tmp/myvenv/lib/python3.10/site-packages/data_diff/__main__.py", line 18, in <module>
    from data_diff.dbt import dbt_diff
  File "/tmp/myvenv/lib/python3.10/site-packages/data_diff/dbt.py", line 22, in <module>
    from data_diff.cloud import DatafoldAPI, TCloudApiDataDiff, TCloudApiOrgMeta
  File "/tmp/myvenv/lib/python3.10/site-packages/data_diff/cloud/__init__.py", line 2, in <module>
    from data_diff.cloud.data_source import get_or_create_data_source
  File "/tmp/myvenv/lib/python3.10/site-packages/data_diff/cloud/data_source.py", line 18, in <module>
    from data_diff.dbt_parser import DbtParser
  File "/tmp/myvenv/lib/python3.10/site-packages/data_diff/dbt_parser.py", line 13, in <module>
    from data_diff.dbt_config_validators import ManifestJsonConfig, RunResultsJsonConfig
  File "/tmp/myvenv/lib/python3.10/site-packages/data_diff/dbt_config_validators.py", line 6, in <module>
    class ManifestJsonConfig(BaseModel):
  File "/tmp/myvenv/lib/python3.10/site-packages/data_diff/dbt_config_validators.py", line 7, in ManifestJsonConfig
    class Metadata(BaseModel):
  File "/tmp/myvenv/lib/python3.10/site-packages/data_diff/dbt_config_validators.py", line 8, in Metadata
    dbt_version: str = Field(..., regex=r"^\d+\.\d+\.\d+([a-zA-Z0-9]+)?$")
  File "/tmp/myvenv/lib/python3.10/site-packages/pydantic/fields.py", line 751, in Field
    raise PydanticUserError('`regex` is removed. use `pattern` instead', code='removed-kwargs')
pydantic.errors.PydanticUserError: `regex` is removed. use `pattern` instead

For further information visit https://errors.pydantic.dev/2.6/u/removed-kwargs

Experiencing the exact same issue.

Same issue here (now with data-diff 0.11.1 and the snowflake extra). Adding pydantic = ">=1.10.12, <2.0.0" explicitly indeed seems to resolve the issue.

Yeah I would argue its annoying for me to have to restrict a transitive dependancy, so hoping we can restrict within this package.


Update all Google.Apis.* assemblies to version 1.10.0.

LGTM, feel tree to merge it whenever you are ready!


[WIP] Start adding a connection model

We are going to synchronize (possibly only one direction at first) the connections between nodes.

when doing console.log before creating the manager, the connection can show up. While putting it after newConnection._connection = connection; , it will raise an error Uncaught (in promise) Syncing error: no comm channel defined


Set up

Description
initial backup set-up
Fixes #1
Fixes #12
Checklist:

[x ] My code follows the style guidelines of this project
[x ] I have performed a self-review of my own code
[] I have commented my code, particularly in hard-to-understand areas
[ ] I have added necessary inline code documentation
[ ] I have added tests that prove my fix is effective and that this feature works
[ ] New and existing unit tests pass locally with my changes

I think we should use es modules imports going forward. That's why babel is among the dependencies. Also why are we doing API versioning? The backend is for a single app. I feel it creates unnecessary complexity.

@vector-ok

I think we should use es modules imports going forward. That's why babel is among the dependencies. Also why are we doing API versioning? The backend is for a single app. I feel it creates unnecessary complexity.

Actually we'll need the versioning. The versioning factor allows companies to walk back on unwanted changes.

I think we should use es modules imports going forward. That's why babel is among the dependencies. Also why are we doing API versioning? The backend is for a single app. I feel it creates unnecessary complexity.

Yes. We'll be making use of the ES module on this project. I'm sure it was an oversight as the commonJS syntax came with the template.

The changes regarding using ES module should be made.
We'll be keeping versioning..


Fix casting warnings in Projection::new

There is a commented-out assertion with a TODO in Projection::new: the assertion fails on some regression tests; but also on some standard library issues that would be useful to have an actual check for. Once we fix the regressions we should enable it.
        // TODO: these assertions fail on a few regressions. Figure out why.
        // I think it may have to do with boxed fat pointers.
        // assert!(
        //     Self::check_expr_typ(&goto_expr, &mir_typ_or_variant, ctx),
        //     "\n{:?}\n{:?}",
        //     &goto_expr,
        //     &mir_typ_or_variant
        // );

Example: boxed closures, like this:
   // Create a boxed once-callable closure
    let f: Box<dyn FnOnce()> = Box::new(|| {});
    f();

Not that I have a solution here as to why "Pointer" and "FlexibleArray" seem to be confused here, but I just wanted to note that CBMC now takes a #flexible_array_member annotation on flexible array members.

From what I gather so far, it looks like we are incorrectly using Struct { Pointer } when adding the symbol to the symbol table. Trying to pin down where this is happening.

Oh, I think I found it. :)
https://github.com/model-checking/kani/blob/e6fb98834a72a30c80875da9d42de0e790fcdcd7/src/kani-compiler/src/codegen_cprover_gotoc/codegen/typ.rs#L770
It looks like we are assuming in a lot of places in this file that a slice is encoded as:
struct<T> Slice{
   data: const* T,
   len: usize,
}

But in the following line we expect a FlexibleArray:
https://github.com/model-checking/kani/blob/e6fb98834a72a30c80875da9d42de0e790fcdcd7/src/kani-compiler/src/codegen_cprover_gotoc/codegen/typ.rs#L542


implement snapshotting of certain configuration during transaction lifetime

this should avoid issues when the configuration changes while a
transaction is active, e.g. through central config

:broken_heart: Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2021-12-08T14:55:55.870+0000

Duration: 31 min 37 sec

Commit: e8bfc362969fe9d7193a4f1112a72f45cd74d4c0

Test stats :test_tube:

Test
Results

Failed
8

Passed
9644

Skipped
8073

Total
17725

Test errors
Expand to view the tests failures
Initializing / Test / Python-python-3.6-1 / test_config_all_upper_case – tests.config.tests

Expand to view the error details
 AssertionError: assert 'ELASTIC_APM_..._min_duration' == 'ELASTIC_APM_..._MIN_DURATION'
  - ELASTIC_APM_EXIT_SPAN_MIN_DURATION
  + ELASTIC_APM_exit_span_min_duration

Expand to view the stacktrace
 def test_config_all_upper_case():
        c = Config.__class__.__dict__.items()
        for field, config_value in Config.__dict__.items():
            if not isinstance(config_value, _ConfigValue):
                continue
>           assert config_value.env_key == config_value.env_key.upper()
E           AssertionError: assert 'ELASTIC_APM_..._min_duration' == 'ELASTIC_APM_..._MIN_DURATION'
E             - ELASTIC_APM_EXIT_SPAN_MIN_DURATION
E             + ELASTIC_APM_exit_span_min_duration

tests/config/tests.py:450: AssertionError

Initializing / Test / Python-python-3.10-1 / test_config_all_upper_case – tests.config.tests

Expand to view the error details
 AssertionError: assert 'ELASTIC_APM_..._min_duration' == 'ELASTIC_APM_..._MIN_DURATION'
  - ELASTIC_APM_EXIT_SPAN_MIN_DURATION
  + ELASTIC_APM_exit_span_min_duration

Expand to view the stacktrace
 def test_config_all_upper_case():
        c = Config.__class__.__dict__.items()
        for field, config_value in Config.__dict__.items():
            if not isinstance(config_value, _ConfigValue):
                continue
>           assert config_value.env_key == config_value.env_key.upper()
E           AssertionError: assert 'ELASTIC_APM_..._min_duration' == 'ELASTIC_APM_..._MIN_DURATION'
E             - ELASTIC_APM_EXIT_SPAN_MIN_DURATION
E             + ELASTIC_APM_exit_span_min_duration

tests/config/tests.py:450: AssertionError

Initializing / Test / Python-python-3.7-1 / test_config_all_upper_case – tests.config.tests

Expand to view the error details
 AssertionError: assert 'ELASTIC_APM_..._min_duration' == 'ELASTIC_APM_..._MIN_DURATION'
  - ELASTIC_APM_EXIT_SPAN_MIN_DURATION
  + ELASTIC_APM_exit_span_min_duration

Expand to view the stacktrace
 def test_config_all_upper_case():
        c = Config.__class__.__dict__.items()
        for field, config_value in Config.__dict__.items():
            if not isinstance(config_value, _ConfigValue):
                continue
>           assert config_value.env_key == config_value.env_key.upper()
E           AssertionError: assert 'ELASTIC_APM_..._min_duration' == 'ELASTIC_APM_..._MIN_DURATION'
E             - ELASTIC_APM_EXIT_SPAN_MIN_DURATION
E             + ELASTIC_APM_exit_span_min_duration

tests/config/tests.py:450: AssertionError

Initializing / Test / windows-3.8-none / test_config_all_upper_case – tests.config.tests

Expand to view the error details
 AssertionError: assert 'ELASTIC_APM_..._min_duration' == 'ELASTIC_APM_..._MIN_DURATION'
  - ELASTIC_APM_EXIT_SPAN_MIN_DURATION
  + ELASTIC_APM_exit_span_min_duration

Expand to view the stacktrace
 def test_config_all_upper_case():
        c = Config.__class__.__dict__.items()
        for field, config_value in Config.__dict__.items():
            if not isinstance(config_value, _ConfigValue):
                continue
>           assert config_value.env_key == config_value.env_key.upper()
E           AssertionError: assert 'ELASTIC_APM_..._min_duration' == 'ELASTIC_APM_..._MIN_DURATION'
E             - ELASTIC_APM_EXIT_SPAN_MIN_DURATION
E             + ELASTIC_APM_exit_span_min_duration

tests\config\tests.py:450: AssertionError

Initializing / Test / windows-3.7-none / test_config_all_upper_case – tests.config.tests

Expand to view the error details
 AssertionError: assert 'ELASTIC_APM_..._min_duration' == 'ELASTIC_APM_..._MIN_DURATION'
  - ELASTIC_APM_EXIT_SPAN_MIN_DURATION
  + ELASTIC_APM_exit_span_min_duration

Expand to view the stacktrace
 def test_config_all_upper_case():
        c = Config.__class__.__dict__.items()
        for field, config_value in Config.__dict__.items():
            if not isinstance(config_value, _ConfigValue):
                continue
>           assert config_value.env_key == config_value.env_key.upper()
E           AssertionError: assert 'ELASTIC_APM_..._min_duration' == 'ELASTIC_APM_..._MIN_DURATION'
E             - ELASTIC_APM_EXIT_SPAN_MIN_DURATION
E             + ELASTIC_APM_exit_span_min_duration

tests\config\tests.py:450: AssertionError

Initializing / Test / Python-python-3.9-1 / test_config_all_upper_case – tests.config.tests

Expand to view the error details
 AssertionError: assert 'ELASTIC_APM_..._min_duration' == 'ELASTIC_APM_..._MIN_DURATION'
  - ELASTIC_APM_EXIT_SPAN_MIN_DURATION
  + ELASTIC_APM_exit_span_min_duration

Expand to view the stacktrace
 def test_config_all_upper_case():
        c = Config.__class__.__dict__.items()
        for field, config_value in Config.__dict__.items():
            if not isinstance(config_value, _ConfigValue):
                continue
>           assert config_value.env_key == config_value.env_key.upper()
E           AssertionError: assert 'ELASTIC_APM_..._min_duration' == 'ELASTIC_APM_..._MIN_DURATION'
E             - ELASTIC_APM_EXIT_SPAN_MIN_DURATION
E             + ELASTIC_APM_exit_span_min_duration

tests/config/tests.py:450: AssertionError

Initializing / Test / Python-python-3.8-1 / test_config_all_upper_case – tests.config.tests

Expand to view the error details
 AssertionError: assert 'ELASTIC_APM_..._min_duration' == 'ELASTIC_APM_..._MIN_DURATION'
  - ELASTIC_APM_EXIT_SPAN_MIN_DURATION
  + ELASTIC_APM_exit_span_min_duration

Expand to view the stacktrace
 def test_config_all_upper_case():
        c = Config.__class__.__dict__.items()
        for field, config_value in Config.__dict__.items():
            if not isinstance(config_value, _ConfigValue):
                continue
>           assert config_value.env_key == config_value.env_key.upper()
E           AssertionError: assert 'ELASTIC_APM_..._min_duration' == 'ELASTIC_APM_..._MIN_DURATION'
E             - ELASTIC_APM_EXIT_SPAN_MIN_DURATION
E             + ELASTIC_APM_exit_span_min_duration

tests/config/tests.py:450: AssertionError

Initializing / Test / windows-3.9-none / test_config_all_upper_case – tests.config.tests

Expand to view the error details
 AssertionError: assert 'ELASTIC_APM_..._min_duration' == 'ELASTIC_APM_..._MIN_DURATION'
  - ELASTIC_APM_EXIT_SPAN_MIN_DURATION
  + ELASTIC_APM_exit_span_min_duration

Expand to view the stacktrace
 def test_config_all_upper_case():
        c = Config.__class__.__dict__.items()
        for field, config_value in Config.__dict__.items():
            if not isinstance(config_value, _ConfigValue):
                continue
>           assert config_value.env_key == config_value.env_key.upper()
E           AssertionError: assert 'ELASTIC_APM_..._min_duration' == 'ELASTIC_APM_..._MIN_DURATION'
E             - ELASTIC_APM_EXIT_SPAN_MIN_DURATION
E             + ELASTIC_APM_exit_span_min_duration

tests\config\tests.py:450: AssertionError

Steps errors
Expand to view the steps failures

Show only the first 10 steps failures

Restore files previously stashed

Took 0 min 0 sec . View more details here
Description: coverage-python-3.9-httplib2-newest

Restore files previously stashed

Took 0 min 0 sec . View more details here
Description: coverage-python-3.10-flask-1.1

Restore files previously stashed

Took 0 min 0 sec . View more details here
Description: coverage-python-3.10-requests-newest

Restore files previously stashed

Took 0 min 0 sec . View more details here
Description: coverage-python-3.10-pyodbc-newest

Restore files previously stashed

Took 0 min 0 sec . View more details here
Description: coverage-python-3.10-elasticsearch-7

Restore files previously stashed

Took 0 min 0 sec . View more details here
Description: coverage-python-3.10-pymysql-newest

Restore files previously stashed

Took 0 min 0 sec . View more details here
Description: coverage-python-3.10-tornado-newest

Restore files previously stashed

Took 0 min 0 sec . View more details here
Description: coverage-python-3.10-sanic-newest

Archive the artifacts

Took 0 min 0 sec . View more details here
Description: [2021-12-08T15:26:29.698Z] Archiving artifacts
Python-python-3.6-none tests failed : hudson.AbortEx

Error signal

Took 0 min 0 sec . View more details here
Description: Python-python-3.6-none tests failed : hudson.AbortException: script returned exit code 2

:bug: Flaky test report
:grey_exclamation: There are test failures but not known flaky tests.
Expand to view the summary

Genuine test errors
:broken_heart: There are test failures but not known flaky tests, most likely a genuine test failure.

Name: Initializing / Test / Python-python-3.6-1 / test_config_all_upper_case – tests.config.tests
Name: Initializing / Test / Python-python-3.10-1 / test_config_all_upper_case – tests.config.tests
Name: Initializing / Test / Python-python-3.7-1 / test_config_all_upper_case – tests.config.tests
Name: Initializing / Test / windows-3.8-none / test_config_all_upper_case – tests.config.tests
Name: Initializing / Test / windows-3.7-none / test_config_all_upper_case – tests.config.tests
Name: Initializing / Test / Python-python-3.9-1 / test_config_all_upper_case – tests.config.tests
Name: Initializing / Test / Python-python-3.8-1 / test_config_all_upper_case – tests.config.tests
Name: Initializing / Test / windows-3.9-none / test_config_all_upper_case – tests.config.tests

:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

/test linters : Run the Python linters only.

/test full : Run the full matrix of tests.

/test benchmark : Run the APM Agent Python benchmarks tests.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)


HTTP POST Configuration Issues

I need monitor my Azure OCR API  status, But I can't complete the configuration.
Here is the curl type reuqst:
curl --location --request POST 'https://ocrapi.my.site/computervision/imageanalysis:analyze?features=read&model-version=latest&language=en&api-version=2024-02-01' \
--header 'User-Agent: Apifox/1.0.0 (https://apifox.com)' \
--header 'Content-Type: application/json' \
--header 'Ocp-Apim-Subscription-Key: my-key-value' \
--header 'Accept: */*' \
--header 'Host: ocrapi.my.site' \
--header 'Connection: keep-alive' \
--data-raw '{
    "url": "my-img-url"
}'

You can see that it can accept a application/json type as the body request, but it seems that the current configuration does not support this operation.
In addition, I noticed that other Issues asked for adding custom check interval, this is a scenario, because requesting this API is charged, so maybe that would be a good idea.

Hi, I think it's possible in the current version. The JSON data in the HTTP POST is just serialized into the string, with a Content-Type header indicating it's a JSON.
so this config should work:
{
  id: 'foo_monitor',
  name: 'My API Monitor',
  method: 'POST',
  target: 'https://example.com',
  headers: {
    'Content-Type': 'application/json'
  },
  body: '{"key1": "value1"}'
}

As for the monitoring interval issue you mentioned, I plan to add a separate cron setting for each request in a subsequent release, which should solve your problem.
However I've been busy with my internship lately and there's no guarantee when a new version will be released. (；′⌒`)


openc2-yuuki does not conform to the latest version of the OpenC2 specification

The OpenC2 specification has undergone several changes since this project was developed. openc2-yuuki should be updated to conform to the new spec.

@dlemire60 - if my understanding is correct, this issue could now be closed based on PR #5 #6 #7 #8


Checkbox Doesn't Shift Left When Initial Theme is Dark, but Theme Switches Successfully

If the initial theme is dark, the checkbox does not shift to the left when the theme is toggled, even though the theme changes as expected. This issue does not occur if the initial theme is light. Changing defaultChecked to checked in the ThemeSwitcher component resolves the issue.

I noticed this bug too


Logger without handlers

When a log level is passed to the client (e.g. logging.DEBUG) the handler is not found raising:
  No handlers could be found for logger "GoDaddyPy.Client"
Fixing it in Client.py module
   # Logging setup
        logging.basicConfig()
        self.logger = logging.getLogger('GoDaddyPy.Client')

This is expected behavior and is notifying consumers of the library that they attempting to use logging without first configuring handlers.
See https://docs.python.org/2/howto/logging.html#configuring-logging-for-a-library for reasoning behind this decision.  Simple use, logging.basicConfig() outside the library if you don't want to see this message, OR simply use logging in production mode and set logging.raiseExceptions = False if you really don't want to see this error.  HOWEVER, this means that logging won't occur in the library because for some reason the logging module was imported but never configured.  This falls outside of the wheelhouse of what I believe this library should do.

To summarize, this is simply my opinion on the matter and I may very well be objectively wrong.  I simply believe it is important to not do "magic" behind the scenes in a library and I don't want to contribute to peoples misunderstandings of how the logging system in python works.


Respect regional settings for number group and decimal separators

If formatting numbers according to system settings and nothing else was all we wanted, this would have been relatively simple. However, we want control over the number of decimal places. Getting system formatting for a variable number of decimal places turned out to be even harder to get right than dates and times thanks to the associated archaic and clumsy Windows APIs...
But we got there in the end. Thanks, users, for your patience! If anyone spots an area in the app that does not appear to be using the correct formatting, please let us know by opening a new issue.


Use core and alloc crates for no_std compatibility (Take 2)

Part of informalsystems/ibc-rs#1158
This follows similar work in informalsystems/ibc-rs#1156 to move closer to supporting no_std in tendermint-rs.
This is a succession of #980 with the changes to replace the use of std::time::SystemTime being moved to another PR.

[ ] Referenced an issue explaining the need for the change
[ ] Updated all relevant documentation in docs
[ ] Updated all code comments where relevant
[ ] Wrote tests
[ ] Added entry in .changelog/

Codecov Report

Merging #993 (56acfec) into master (34c5d2a) will increase coverage by 0.0%.
The diff coverage is 87.5%.

:exclamation: Current head 56acfec differs from pull request most recent head 86ff845. Consider uploading reports for the commit 86ff845 to get more accurate results

@@          Coverage Diff           @@
##           master    #993   +/-   ##
======================================
  Coverage    72.5%   72.6%
======================================
  Files         204     204
  Lines       16655   16645   -10
======================================
+ Hits        12078   12086    +8
+ Misses       4577    4559   -18

Impacted Files
Coverage Δ

light-client/src/components/verifier.rs
87.9% <ø> (ø)

light-client/tests/model_based.rs
90.1% <ø> (ø)

proto/src/lib.rs
100.0% <ø> (ø)

proto/src/serializers/bytes.rs
80.0% <ø> (ø)

proto/src/serializers/optional_from_str.rs
0.0% <ø> (ø)

proto/src/serializers/part_set_header_total.rs
100.0% <ø> (ø)

proto/src/serializers/time_duration.rs
87.5% <ø> (ø)

proto/src/serializers/timestamp.rs
96.3% <ø> (ø)

proto/src/serializers/txs.rs
64.5% <ø> (ø)

rpc/src/client.rs
16.9% <ø> (ø)

... and 123 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 34c5d2a...86ff845. Read the comment docs.

Would it be possible to consolidate the multiple preludes into a shared crate to ease with maintenance down the line?

I am a bit reluctant to expose the internal prelude as public interface. It will make it more difficult for us to remove it in the future.
It is also not clear that if we do want to expose it, which crate should it be in. The lowest common denominator of all tendermint-rs and ibc-rs crates is probably tendermint-proto. But it also doesn't feel right to put it there. I also don't think it is worth a hassle to publish it as a separate crate.
In any case, I think this is just a temporary measure with minimal content that we can manage with. Once the alloc::prelude crate is graduated from nightly at https://github.com/rust-lang/rust/issues/58935, or in case the Rust team decide to go with different approaches, it is much easier for us to remove/alter the prelude.rs in the individual crates than having to do a major version release with deprecation and other hassles.


To_do_list

To_do_list using html , css and js

@TechHack3 Please assign me this issue #19

I am interested in taking on the task at hand and want to assure you that I will complete it to the best of my ability. I kindly request that you assign this task to me. #19 .

@TechHack3 Can I contribute to #19 issue

hey @TechHack3 can I contribute to this :)


odo link: fix command description

What type of PR is this?
/kind cleanup
What does this PR do / why we need it:
odo link had an outdated description
commands supports linking two devfile components

https://github.com/openshift/odo/pull/4930/files#diff-65ce0831cfcea5d7cd8cd8c5fc59b342b13cf367f4c7ff976aba7b1ac3f83eaaR69

We can now link the two applications (works only with s2i components):
odo link backend --component frontend

Can you fix this line as well?

:+1: done

I am also approving this PR since it's a really small change.
/approve

odo link and unlink command tests
/go/src/github.com/openshift/odo/tests/integration/cmd_link_unlink_test.go:10
when running help for link and unlink command
/go/src/github.com/openshift/odo/tests/integration/cmd_link_unlink_test.go:32
should display the help [It]
/go/src/github.com/openshift/odo/tests/integration/cmd_link_unlink_test.go:33
to contain substring
   <string>: works only with s2i components

Missed out on this one.

    to contain substring
        <string>: works only with s2i components

https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_odo/4930/pull-ci-openshift-odo-main-v4.7-integration-e2e/1418565524144525312
/hold

@kadel can you please address the changes requested by @valaparthvi & @mik-dass? Also, please update the Changelog.md file.

Also, please update the Changelog.md file.

Should something as small as this be in the changelog?

/hold cancel

Also, please update the Changelog.md file.

Should something as small as this be in the changelog?

IMO yes because it's still a user facing change nonetheless. We tend to (or, maybe, we should) put even the things that don't directly impact users in the Changelog. I'm trying to use it as the source of truth for Sprint Review document, making announcements of new release at the end of each Sprint, and maybe even blog on docusaurus site announcing new release every Sprint.

Also, please update the Changelog.md file.

Should something as small as this be in the changelog?

IMO yes because it's still a user facing change nonetheless. We tend to (or, maybe, we should) put even the things that don't directly impact users in the Changelog. I'm trying to use it as the source of truth for Sprint Review document, making announcements of new release at the end of each Sprint, and maybe even blog on docusaurus site announcing new release every Sprint.

udpated


fixing issue #259 and unit test cleanup

resolves https://github.com/RackHD/RackHD/issues/259
The actual fix for the bug was the line I added to the swagger_render.  @zyoung51 helped me find that fix.
@RackHD/corecommitters @dalebremner @srinia6 @brianparry

*** BUILD #1603 ***

test this please

+1

@yyscamper not sure if you want to take a look at this fix since it addresses github issue RackHD/RackHD#259 that you worked on

@BillyAbildgaard thanks for your fix. Could you please clarify my above questions? and also the following question:
Do you have run the unit-test files in random order with enough times?

@yyscamper I ran the tests in general and ran the specific case you saw where running workflows before profiles caused the failure.  The fix eliminated this case.
This story was just to fix the bug.  Stryker team has an additional story in our backlog to look into running the unit tests randomly

@BillyAbildgaard : The whole solution of random unit-test will need relative much consideration, but if you want to try, so can simplify use sort -R, the full command is:
./node_modules/.bin/mocha $(find spec -name '*-spec.js' | sort -R ) -R spec --require spec/helper.js

Could you please try above random testing with enough times? Because I think that issue should not be considered as fully resolved if the random testing fails.

@yyscamper I can confirm the fix does resolve the bug that was reported.  I tested it multiple times.
We have a story for randomized testing, but that was outside the scope of what I was trying to do for this, which was just to resolve the bug reported in RackHD/RackHD#259.

@yyscamper As @BillyAbildgaard has mentioned, this PR is a general cleanup of unit test mocking and a fix for RackHD/RackHD#259.  Full random-order testing support is planned as part of a future story and is outside the scope of this PR.

@BillyAbildgaard @brianparry : I agree on the scope for this PR. So if there is any more unit-test error if run in random order, we can fix it then.


Create Appveyor NuGet feed for releases

Use the Appveyor NuGet feed to push releases in addition to GitHub so someone can add it to Octopus instead of downloading and then uploading packages.

Awesome idea.  I didn’t know you could hit the AppVeyor feed externally.
From: Dan Piessens<EMAIL_ADDRESS>Sent: Tuesday, February 9, 2016 1:15 PM
To: Zywave/OctopusDeploy-Kraken<EMAIL_ADDRESS>Subject: [OctopusDeploy-Kraken] Create Appveyor NuGet feed for releases (#23)
Use the Appveyor NuGet feed to push releases in addition to GitHub so someone can add it to Octopus instead of downloading and then uploading packages.
—
Reply to this email directly or view it on GitHubhttps://github.com/Zywave/OctopusDeploy-Kraken/issues/23.
John Cruikshank
Principal Software Architect
T<PHONE_NUMBER>
Zywave
TF<PHONE_NUMBER>
F<PHONE_NUMBER>
www.zywave.com
Join us on Twitterhttp://twitter.com/zywave, Facebookhttp://www.facebook.com/Zywave, Google+https://plus.google.com/u/0/b/117181742152023791165/#117181742152023791165/posts and LinkedInhttp://www.linkedin.com/groups?mostPopular=&gid=146696 to continue the conversation.
CONFIDENTIALITY NOTICE: This e-mail, including attachments, is intended solely for the person or entity to which it is addressed and may contain confidential, privileged and/or proprietary information. Any review, dissemination, distribution, copying, printing, or other use of this e-mail by persons or entities other than the addressee or his/her authorized agent is prohibited. If you have received this e-mail in error, please contact the sender immediately and delete the material from your computer. You may notify this individual that you no longer wish to receive any commercial e-mails from this sender by replying to this e-mail or by sending a written request to 10700 W. Research Drive, Suite 400, Attn: Marketing, Milwaukee, WI  53226.

To be honest I'm not completely confident you can but I wanted to give it a try and see :)

This already works! I have updated the Installation Guide to reflect this workflow.
Thanks for the idea.

Closed with AppVeyor already being magical.


Param source timezone (review)

Looks good to me apart from a clash with #366.  I managed to replicate to UTC with this PR.

Thanks @IlyaTsoi for your contribution.


Method App\Application::getName does not exist when running non-existent command

Cannot reproduce from source, only in the compiled app.
$ hyde foo

In Macroable.php line 112:

  Method App\Application::getName does not exist.

https://github.com/hydephp/cli/commit/8c1af254a192bedbc34f5551fa7dd01039637f8b brings a new error!
 hyde foo

   ERROR  Command "HydePHP" is not defined.

So I assume the method is supposed to return the default command name

Confirmed to be fixed by https://github.com/hydephp/cli/commit/1e8beab058a87e8679e01316a67bc573a4b48969


gradle androidInstall fails on simple application

org.javafxports:jfxmobile-plugin:2.0.16
Description
Running gradle androidInstall results in the following error on a simple app (works fine on desktop and iOS).  The latest Android Studio is installed and the line from the README.md has been executed successfully.
WARNING: platform-tools package is not installed.
:cleanAndroid
:validateManifest
:collectMultiDexComponents
:compileJava UP-TO-DATE
:processResources UP-TO-DATE
:classes UP-TO-DATE
:compileAndroidJava NO-SOURCE
:processAndroidResources NO-SOURCE
:androidClasses UP-TO-DATE
:copyClassesForDesugar
Mar 19, 2018 01:01:01 PM org.javafxports.retrobuffer.Main main
SEVERE: Failed to run Retrobuffer
java.lang.IllegalArgumentException
	at org.objectweb.asm.ClassReader.<init>(Unknown Source)
	at org.objectweb.asm.ClassReader.<init>(Unknown Source)
	at org.javafxports.retrobuffer.ClassAnalyzer.analyze(ClassAnalyzer.java:48)
	at org.javafxports.retrobuffer.Retrobuffer$1.visitClass(Retrobuffer.java:59)
	at org.javafxports.retrobuffer.ClasspathVisitor.visitFile(ClasspathVisitor.java:59)
	at org.javafxports.retrobuffer.ClasspathVisitor.visitFile(ClasspathVisitor.java:41)
	at java.base/java.nio.file.Files.walkFileTree(Files.java:2713)
	at java.base/java.nio.file.Files.walkFileTree(Files.java:2785)
	at org.javafxports.retrobuffer.Retrobuffer.run(Retrobuffer.java:56)
	at org.javafxports.retrobuffer.Main.main(Main.java:45)

:applyRetrobuffer FAILED

This exception means there's still at least one class on the classpath that has been compiled with java 9 or higher as the target. There's already an issue for improving the error message by printing the affected class: https://github.com/javafxports/javafxmobile-plugin/issues/32

Yes, that was the case.  Thanks.


The startFrame param of Actions.PlayAnimation() is not compatible with ignoreIfPlaying param of AnimationState.play()

Version

Phaser Version: 3.52.0

Description
startFrame is an optional number, but ignoreIfPlaying is an optional boolean:
https://github.com/photonstorm/phaser/blob/master/src/actions/PlayAnimation.js#L21
/**
 * @function Phaser.Actions.PlayAnimation
 * @param {(string|number)} [startFrame] - The starting frame of the animation with the given key.
 */
var PlayAnimation = function (items, key, startFrame)
{
    for (var i = 0; i < items.length; i++)
    {
        items[i].anims.play(key, startFrame); // will eventually call AnimationState.play()
    }

    return items;
};

https://github.com/photonstorm/phaser/blob/master/src/animations/AnimationState.js#L826
/**
 * @method Phaser.Animations.AnimationState#play
 * @param {boolean} [ignoreIfPlaying=false] - If this animation is already playing then ignore this call.
 */
play: function (key, ignoreIfPlaying)
{
  // ...
}

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.


fix: navigation to sections

Fixes Issue
Closes #239

Can you share screenshot or a screen recording to see what changes you made?


MacOS Electron app closes application instead of window

On MacOS, it's expected that when the user closes a window by either clicking the red "x" on the top left of a window or by using Command + W, the window will close, but the application will still be running, as represented by the icon remaining in the dock. However, when closing the app by clicking the "x", the application itself also closes. Furthermore, when closing with Command + W, the application appears to close, but a few seconds later a crash report appears indicating an unexpected termination of the process. This crash report does not appear when using Command + Q.
Keeping the application running after a window is closed is a good idea since it allows background processes, such as a voice call or notifications, to keep running. It also allows the user to jump back in the app quicker and where they left off.
Regarding the crash, I am on a MacBook Pro 16,1 running MacOS Catalina 10.15.7, if this information is necessary.

The first part of you issue is intentional. We will soon add support for the app to run in background (probably after the next version is released) but as of right now there is no support.
However i would like to know mode about the crash you mentioned. Can you please attach the crash report below and also tell which build are you using?

I am using the latest release build at the time (1.0.29). I'll paste the first bit of the crash report and upload the entire report as a text file here:
Process:               DogeHouse [17212]
Path:                  /Applications/DogeHouse.app/Contents/MacOS/DogeHouse
Identifier:            com.electron.dogehouse
Version:               1.0.29 (1.0.29)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           DogeHouse [17212]
User ID:               501

Date/Time:             2021-03-30 15:54:56.732 -0700
OS Version:            Mac OS X 10.15.7 (19H524)
Report Version:        12
Bridge OS Version:     5.2 (18P4346)
Anonymous UUID:        20E3346B-08C2-359B-21B7-7DB53E2C1559

Time Awake Since Boot: 110000 seconds

System Integrity Protection: disabled

Crashed Thread:        32  async-std/runtime

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called

@ben9583 can you try the latest build 1.0.30 and check if this still occurs?

Looks like I'm not getting the crash anymore; thanks!


fy2021q1 refresh

updated demos to SPFx v1.11
update pictures, resources, and steps to account for dependency updates

Excellent, thanks AC and Rob for the updates for 1.11.


Typo - apps spelled aps

https://docs.microsoft.com/en-us/azure/virtual-desktop/app-attach#install-certificates
You must install certificates on all session hosts in the host pool that will host the aps from your MSIX app attach packages.

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

ID: 62521d12-9efc-d132-176b-ca6a4ea83f16
Version Independent ID: 21322b77-a2e0-41a2-b128-7681d2d62577
Content: Configure Windows Virtual Desktop MSIX app attach PowerShell scripts - Azure
Content Source: articles/virtual-desktop/app-attach.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

@melzayet Thanks for pointing this out. The document is updated and changes will go live soon.


Backup hangs on [GetRegistryInfo] value from imagestream

Hi, Using oadp-0.5.3 and a DPA configured with 2 backupLocations:
apiVersion: oadp.openshift.io/v1alpha1
kind: DataProtectionApplication
metadata:
  name: sf-dpa
  namespace: openshift-adp
spec:
  configuration:
    velero:
      defaultPlugins:
      - openshift
      - aws
      - csi
      featureFlags:
      - EnableCSI
    restic:
      enable: true
  backupImages: true
  backupLocations:
    - name: sf-dpa-1
      velero:
        provider: aws
        default: true
        credential:
          key: sf-ocp
          name: cloud-credentials
        objectStorage:
          bucket: oadp-backups-nimbus-ec-u12-dr01
          prefix: nimbus
        config:
          insecureSkipTLSVerify: "true"
          profile: default
          region: us-east-1
          s3ForcePathStyle: "true"
          s3Url: https://s3-netapp-storagegrid-fqdn
          signatureVersion: "4"
    - name: sf-dpa-2
      velero:
        provider: aws
        default: false
        credential:
          key: demo-customer
          name: cloud-credentials
        objectStorage:
          bucket: nimbus-demo-customer-ec-u12-dr01
          prefix: nimbus
        config:
          insecureSkipTLSVerify: "true"
          profile: default
          region: us-east-1
          s3ForcePathStyle: "true"
          s3Url: https://s3-netapp-storagegrid-fqdn
          signatureVersion: "4"

Created a backup:
apiVersion: velero.io/v1
kind: Backup
metadata:
  namespace: openshift-adp
  generateName: demo-customer-backup-
spec:
  defaultVolumesToRestic: true
  storageLocation: sf-dpa-2
  includedNamespaces:
    - demo-customer

Also enabled --log-level debug with velero pod I found that the backup appears to hang in openshift-velero-plugin:
time="2021-12-30T07:52:52Z" level=info msg="[common-backup] Entering common backup plugin" backup=openshift-adp/demo-customer-backup-z9gcj cmd=/plugins/velero-plugins logSource="/opt/app-root/src/github.com/konveyor/openshift-velero-plugin/velero-plugins/common/backup.go:39" pluginName=velero-plugins
time="2021-12-30T07:52:52Z" level=info msg="[GetRegistryInfo] value from imagestream" backup=openshift-adp/demo-customer-backup-z9gcj cmd=/plugins/velero-plugins logSource="/opt/app-root/src/github.com/konveyor/openshift-velero-plugin/velero-plugins/common/shared.go:36" pluginName=velero-plugins
time="2021-12-30T07:52:52Z" level=debug msg="Skipping action because it does not apply to this resource" backup=openshift-adp/demo-customer-backup-z9gcj logSource="pkg/backup/item_backupper.go:308" name=demo-customer-backend-86b7cfbb9f-psbxm namespace=demo-customer resource=pods
time="2021-12-30T07:52:52Z" level=debug msg="Skipping action because it does not apply to this resource" backup=openshift-adp/demo-customer-backup-z9gcj logSource="pkg/backup/item_backupper.go:308" name=demo-customer-backend-86b7cfbb9f-psbxm namespace=demo-customer resource=pods
time="2021-12-30T07:52:52Z" level=debug msg="Skipping action because it does not apply to this resource" backup=openshift-adp/demo-customer-backup-z9gcj logSource="pkg/backup/item_backupper.go:308" name=demo-customer-backend-86b7cfbb9f-psbxm namespace=demo-customer resource=pods
time="2021-12-30T07:52:52Z" level=debug msg="Skipping action because it does not apply to this resource" backup=openshift-adp/demo-customer-backup-z9gcj logSource="pkg/backup/item_backupper.go:308" name=demo-customer-backend-86b7cfbb9f-psbxm namespace=demo-customer resource=pods
time="2021-12-30T07:52:52Z" level=debug msg="Skipping action because it does not apply to this resource" backup=openshift-adp/demo-customer-backup-z9gcj logSource="pkg/backup/item_backupper.go:308" name=demo-customer-backend-86b7cfbb9f-psbxm namespace=demo-customer resource=pods
time="2021-12-30T07:52:52Z" level=debug msg="Skipping action because it does not apply to this resource" backup=openshift-adp/demo-customer-backup-z9gcj logSource="pkg/backup/item_backupper.go:308" name=demo-customer-backend-86b7cfbb9f-psbxm namespace=demo-customer resource=pods
time="2021-12-30T07:52:52Z" level=debug msg="Acquiring lock" backupLocation=sf-dpa-2 logSource="pkg/restic/repository_ensurer.go:122" volumeNamespace=demo-customer
time="2021-12-30T07:52:52Z" level=debug msg="Acquired lock" backupLocation=sf-dpa-2 logSource="pkg/restic/repository_ensurer.go:131" volumeNamespace=demo-customer
time="2021-12-30T07:52:52Z" level=debug msg="Ready repository found" backupLocation=sf-dpa-2 logSource="pkg/restic/repository_ensurer.go:147" volumeNamespace=demo-customer
time="2021-12-30T07:52:52Z" level=debug msg="Released lock" backupLocation=sf-dpa-2 logSource="pkg/restic/repository_ensurer.go:128" volumeNamespace=demo-customer

Hanging ...

Can also see that the PodVolumeBackup is stuck and doesnt progress:
$ oc describe PodVolumeBackup demo-customer-backup-z9gcj-n6bj8
Name:         demo-customer-backup-z9gcj-n6bj8
Namespace:    openshift-adp
Labels:       velero.io/backup-name=demo-customer-backup-z9gcj
              velero.io/backup-uid=57465526-2181-4e7d-8fcc-5b61af769c58
              velero.io/pvc-uid=875b84a8-84c6-4dec-94a8-6a1f2e286e18
Annotations:  velero.io/pvc-name: demo-customer-backend-pvc
API Version:  velero.io/v1
Kind:         PodVolumeBackup
Metadata:
  Creation Timestamp:  2021-12-30T07:52:52Z
  Generate Name:       demo-customer-backup-z9gcj-
  Generation:          1
    Manager:    velero-server
    Operation:  Update
    Time:       2021-12-30T07:52:52Z
  Owner References:
    API Version:     velero.io/v1
    Controller:      true
    Kind:            Backup
    Name:            demo-customer-backup-z9gcj
    UID:             57465526-2181-4e7d-8fcc-5b61af769c58
  Resource Version:  261201462
  UID:               fba2cc44-9e71-4709-b522-d44fa301b43d
Spec:
  Backup Storage Location:  sf-dpa-2
  Node:                     mycluster-x4rx9-worker-5hj47
  Pod:
    Kind:           Pod
    Name:           demo-customer-backend-86b7cfbb9f-psbxm
    Namespace:      demo-customer
    UID:            1917842f-5308-4180-b016-4e9ae0437daf
  Repo Identifier:  s3:https://s3-netapp-storagegrid-fqdn/nimbus-demo-customer-ec-u12-dr01/nimbus/restic/demo-customer
  Tags:
    Backup:        demo-customer-backup-z9gcj
    Backup - UID:  57465526-2181-4e7d-8fcc-5b61af769c58
    Ns:            demo-customer
    Pod:           demo-customer-backend-86b7cfbb9f-psbxm
    Pod - UID:     1917842f-5308-4180-b016-4e9ae0437daf
    Pvc - UID:     875b84a8-84c6-4dec-94a8-6a1f2e286e18
    Volume:        demo-customer-backend-storage
  Volume:          demo-customer-backend-storage
Status:
  Progress:
Events:  <none>

(The pod demo-customer-backend-86b7cfbb9f-psbxm has annotations "backup.velero.io/backup-volumes: demo-customer-backend-storage" set)
When checking the logs for oadp-sf-dpa-2-aws-registry I cant see anything relevant ...
According to Docs I should see that the "is-backup" starts but it doesnt...
Any suggestions how to troubleshoot?

Sorry, there was a nodeSelector on the oadp-operator namespace causing the restic pods to not be scheduled on the worker nodes, doh!


feat(core): add environments block to datasource configuration

This will add datasource config for each environments (development, test, and production).
Fixes grails/grails-core#13103

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: puneetbehl:x: Weiqi GaoWeiqi Gao seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: puneetbehl:x: Weiqi GaoWeiqi Gao seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Filtering a list where the items contain spaces when using select

Describe the problem
I'm trying to find a way to not use the space character as selection when filtering a list using select. I'm using select for a list of names that have spaces in them (e.g  ["Some Team", "Some Team: Subteam"]).
When the user types "Some " the prompt selects the first instance and I want it to continue filtering using the space.
I tried using prompt.select('Select a team name:', team_names, filter: true, keys: [:return]) but that didn't work.
Steps to reproduce the problem
prompt = TTY::Prompt.new(active_color: :green)
team_names = ['Some Team', 'Some Team: Subteam']
prompt.select('Select a team name:', team_names, filter: true)

Actual behaviour
When the user types "Some " the prompt selects the first instance (i.e. Some Team)
Expected behaviour
When the user types "Some " the prompt continues filtering using the space.
Describe your environment

OS version: macOS 11.2.3
Ruby version: ruby 2.6.3
TTY::Prompt version: 0.23.0

Hi Francisco 👋
Thanks for submitting the issue.
I had a quick look at implementing this for the select prompt and I can make it work fine. However, the space character in the multi_select prompt is used for selecting choices and I'm not sure how to solve this conundrum. These two prompts work in tandem so I would need to find a solution that works for both of them. Do you have any suggestions?

Interesting! I was thinking that we'd keep the default as is (i.e. space is selection) unless explicitly stated otherwise -- something similar to what I tried above:
prompt.select('Select a team name:', team_names, filter: true, keys: [:return])
Then if the user explicitly does this for multi_select we can require it to also pass another key for multiple selection?
Does that make sense?

Yup, makes sense. I wanted to avoid the need to specify a different key for selection in the multi_select prompt but this may be the most straightforward way. Having said that, there is inherent complexity in going down this route. Choosing keys has an impact on displayed hints as well as the regex used for filtering. Not to mention a need then to dynamically register key events for a new selection key. Ultimately this will lead to greater flexibility. Do you have time to submit PR?

I can. I'm not super familiar with the structure of the codebase so if you can guide me a little bit where I could add a failing test + where I'd go to work to fix it that'd be a great start!

Sure thing. The logic responsible for the select is in list.rb and for the multi_select in mulit_list.rb. The test files match the prompt names.

@piotrmurach Any chance you could help me out get a start here? I've downloaded the project but I'm not entirely sure how I'd start tackling this since I'm fairly unfamiliar with the implementation.
Even if you can put a branch up with what you had would probably be super helpful!

Hey all! I stumbled upon the same problem, needing my filters to include spaces.
I believe I have implemented what @piotrmurach described in the PR above, including the check for clashing keys in mutli-select.

As I just encountered the same issue, I work around it with a specific new class and a little monkey patch:
class SpaceList < TTY::Prompt::List
  def keyspace(event)
    @filter << event.value
    @active = 1
  end
end

module TTY
  class Prompt
    def select_with_space(question, *args, &block)
      invoke_select(SpaceList, question, *args, &block)
    end
  end
end

prompt = TTY::Prompt.new(interrupt: :exit)
answer = prompt.select_with_space('Select a sentence: ', sentences, filter: true)

Hey @piotrmurach, is there an estimation when this will be added? This issue exists for years now...