error: value is null while a set was expected, at linux/nvidia-x11/generic.nix

Issue description
Trying to upgrade throws an error:
nixos-rebuild switch --upgrade

unpacking channels...
building Nix...
building the system configuration...
error: value is null while a set was expected, at /nix/store/1ka8pv78p0p9c3h8qb892f8xb23zv9a0-nixos-17.09/nixos/pkgs/os-specific/linux/nvidia-x11/generic.nix:65:52
(use '--show-trace' to show detailed location information)

With '--show-trace':
nixos-rebuild switch --upgrade --show-trace                                                                                (1)
unpacking channels...
building Nix...
building the system configuration...
error: while evaluating the attribute 'activationScript' of the derivation 'nixos-system-rogue-17.09.2498.a9ffb7b0b5a' at /nix/store/1ka8pv78p0p9c3h8qb892f8xb23zv9a0-nixos-17.09/nixos/pkgs/stdenv/generic/make-derivation.nix:98:11:
while evaluating the attribute 'system.activationScripts.script' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/nixos/modules/system/activation/activation-script.nix:62:9:
while evaluating 'textClosureMap' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/strings-with-deps.nix:70:35, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/nixos/modules/system/activation/activation-script.nix:83:18:
while evaluating 'textClosureList' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/strings-with-deps.nix:54:33, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/strings-with-deps.nix:71:35:
while evaluating 'f' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/strings-with-deps.nix:56:17, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/strings-with-deps.nix:68:9:
while evaluating 'mapAttrs' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/attrsets.nix:198:17, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/nixos/modules/system/activation/activation-script.nix:82:33:
while evaluating 'mapAttrs' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/attrsets.nix:198:17, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/nixos/modules/system/activation/activation-script.nix:81:24:
while evaluating the attribute 'mergedValue' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:339:5:
while evaluating anonymous function at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:339:32, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:339:19:
while evaluating 'merge' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/types.nix:203:20, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:342:8:
while evaluating 'mapAttrs' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/attrsets.nix:198:17, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/types.nix:204:9:
while evaluating 'filterAttrs' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/attrsets.nix:115:23, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/types.nix:204:35:
while evaluating 'concatMap' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/lists.nix:102:18, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/attrsets.nix:116:18:
while evaluating anonymous function at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/attrsets.nix:116:29, called from undefined position:
while evaluating anonymous function at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/types.nix:204:51, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/attrsets.nix:116:62:
while evaluating the attribute 'setup-opengl' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/attrsets.nix:334:7:
while evaluating anonymous function at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/types.nix:204:86, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/attrsets.nix:334:15:
while evaluating the attribute 'optionalValue' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:346:5:
while evaluating 'filterOverrides' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:419:21, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:328:18:
while evaluating 'concatMap' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/lists.nix:102:18, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:425:8:
while evaluating 'concatMap' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/lists.nix:102:18, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:323:17:
while evaluating anonymous function at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:323:28, called from undefined position:
while evaluating 'dischargeProperties' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:386:25, called from /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/modules.nix:324:62:
while evaluating the attribute 'value' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/lib/types.nix:209:55:
while evaluating the attribute 'setup-opengl' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs/nixos/modules/hardware/opengl.nix:123:5:
while evaluating the attribute 'passAsFile' of the derivation 'opengl-drivers-32bit' at /nix/store/1ka8pv78p0p9c3h8qb892f8xb23zv9a0-nixos-17.09/nixos/pkgs/stdenv/generic/make-derivation.nix:98:11:
while evaluating the attribute 'passAsFile' of the derivation 'nvidia-libs' at /nix/store/1ka8pv78p0p9c3h8qb892f8xb23zv9a0-nixos-17.09/nixos/pkgs/stdenv/generic/make-derivation.nix:98:11:
while evaluating the attribute 'nativeBuildInputs' of the derivation 'nvidia-x11-384.98' at /nix/store/1ka8pv78p0p9c3h8qb892f8xb23zv9a0-nixos-17.09/nixos/pkgs/stdenv/generic/make-derivation.nix:98:11:
while evaluating 'chooseDevOutputs' at /nix/store/1ka8pv78p0p9c3h8qb892f8xb23zv9a0-nixos-17.09/nixos/lib/attrsets.nix:460:22, called from undefined position:
value is null while a set was expected, at /nix/store/1ka8pv78p0p9c3h8qb892f8xb23zv9a0-nixos-17.09/nixos/pkgs/os-specific/linux/nvidia-x11/generic.nix:65:52

cat /nix/store/1ka8pv78p0p9c3h8qb892f8xb23zv9a0-nixos-17.09/nixos/pkgs/os-specific/linux/nvidia-x11/generic.nix | nl -ba           (1)
     1	{ version
     2	, sha256_32bit
     3	, sha256_64bit
     4	, settingsSha256
     5	, persistencedSha256
     6	, useGLVND ? true
     7	, useProfiles ? true
     8	, preferGtk2 ? false
     9
    10	, prePatch ? ""
    11	, patches ? []
    12	}:
    13
    14	{ stdenv, callPackage, callPackage_i686, fetchurl, fetchpatch
    15	, kernel ? null, xorg, zlib, perl, nukeReferences
    16	, # Whether to build the libraries only (i.e. not the kernel module or
    17	  # nvidia-settings).  Used to support 32-bit binaries on 64-bit
    18	  # Linux.
    19	  libsOnly ? false
    20	}:
    21
    22	with stdenv.lib;
    23
    24	assert (!libsOnly) -> kernel != null;
    25
    26	let
    27	  nameSuffix = optionalString (!libsOnly) "-${kernel.version}";
    28	  pkgSuffix = optionalString (versionOlder version "304") "-pkg0";
    29
    30	  self = stdenv.mkDerivation {
    31	    name = "nvidia-x11-${version}${nameSuffix}";
    32
    33	    builder = ./builder.sh;
    34
    35	    src =
    36	      if stdenv.system == "i686-linux" then
    37	        fetchurl {
    38	          url = "https://download.nvidia.com/XFree86/Linux-x86/${version}/NVIDIA-Linux-x86-${version}${pkgSuffix}.run";
    39	          sha256 = sha256_32bit;
    40	        }
    41	      else if stdenv.system == "x86_64-linux" then
    42	        fetchurl {
    43	          url = "https://download.nvidia.com/XFree86/Linux-x86_64/${version}/NVIDIA-Linux-x86_64-${version}${pkgSuffix}.run";
    44	          sha256 = sha256_64bit;
    45	        }
    46	      else throw "nvidia-x11 does not support platform ${stdenv.system}";
    47
    48	    patches = if libsOnly then null else patches;
    49	    inherit prePatch;
    50	    inherit version useGLVND useProfiles;
    51	    inherit (stdenv) system;
    52
    53	    outputs = [ "out" ] ++ optional (!libsOnly) "bin";
    54	    outputDev = if libsOnly then null else "bin";
    55
    56	    kernel = if libsOnly then null else kernel.dev;
    57
    58	    hardeningDisable = [ "pic" "format" ];
    59
    60	    dontStrip = true;
    61	    dontPatchELF = true;
    62
    63	    libPath = makeLibraryPath [ xorg.libXext xorg.libX11 xorg.libXv xorg.libXrandr zlib stdenv.cc.cc ];
    64
->  65	    nativeBuildInputs = [ perl nukeReferences ] ++ kernel.moduleBuildDependencies;
    66
    67	    disallowedReferences = optional (!libsOnly) [ kernel.dev ];
    68
    69	    passthru = {
    70	      settings = callPackage (import ./settings.nix self settingsSha256) {
    71	        withGtk2 = preferGtk2;
    72	        withGtk3 = !preferGtk2;
    73	      };
    74	      persistenced = mapNullable (hash: callPackage (import ./persistenced.nix self hash) { }) persistencedSha256;
    75	    };
    76
    77	    meta = with stdenv.lib; {
    78	      homepage = http://www.nvidia.com/object/unix.html;
    79	      description = "X.org driver and kernel module for NVIDIA graphics cards";
    80	      license = licenses.unfreeRedistributable;
    81	      platforms = platforms.linux;
    82	      maintainers = [ maintainers.vcunat ];
    83	      priority = 4; # resolves collision with xorg-server's "lib/xorg/modules/extensions/libglx.so"
    84	    };
    85	  };
    86
    87	in self

Steps to reproduce
  services.xserver = {                       # Enable the X11 windowing system.
      videoDrivers = [ "nvidia" ];    # Proprietary nVidia driver
  };

  hardware = {
    cpu.intel.updateMicrocode = true;
    enableAllFirmware = true;
    # Enable 32bit acceleration
    opengl.driSupport32Bit = true;
  };

Technical details

system: "x86_64-linux"
host os: Linux 4.9.68, NixOS, 17.09.2498.a9ffb7b0b5a (Hummingbird)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 1.12pre5788_e3013543
channels(root): "nixos-17.09, unstable-18.03pre123130.1bc288591ea"
channels(pyro): ""
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

I'm also getting this issue with both "nvidia" and "nvidiaBeta".

I can not reproduce it, and since your nix-info reports that you already are on a9ffb7b0b5a, but the latest nixos-17.09 release is the same, it does not look like anything in Nixpkgs has changed to cause this failure.

I'm encountering the same issue.
The first broken commit is 708b151c9d5ebd6572457cb182b1a33551e579a2, cc @fpletz

Parts of nvidia driver are built without kernel, in which case kernel.moduleBuildDependencies should not be added.
The following fixes the issue:
@@ -62,7 +62,7 @@ let

     libPath = makeLibraryPath [ xorg.libXext xorg.libX11 xorg.libXv xorg.libXrandr zlib stdenv.cc.cc ];

-    nativeBuildInputs = [ perl nukeReferences ] ++ kernel.moduleBuildDependencies;
+    nativeBuildInputs = [ perl nukeReferences ] ++ optionals (!libsOnly) kernel.moduleBuildDependencies;

     disallowedReferences = optional (!libsOnly) [ kernel.dev ];

Is fixed on master with 9fe81b5ac2bca0577042e43483096f50c46e4dbb and release-17.09 with 9fe81b5ac2bca0577042e43483096f50c46e4dbb.

Thank you 8)
Happy New Year everyone!


Error starting packager: TypeError: Cannot read property 'version' of undefined

Description
When I try to use yarn start , I got this error.
Error starting packager: TypeError: Cannot read property 'version' of undefined
Expected Behavior
All commands I  used:
create-react-native-app rn-awe
yarn start
Observed Behavior
Error details
E:\Web\Joe.Wu\rn-awe>yarn start
yarn run v1.3.2
$ react-native-scripts start
17:16:47: Starting packager...
17:17:43: Error starting packager: TypeError: Cannot read property 'version' of undef
    at E:\xdl\src\project\Doctor.js:641:44
    at E:\Web\Joe.Wu\rn-awe\node_modules\lodash\lodash.js:4944:15
    at baseForOwn (E:\Web\Joe.Wu\rn-awe\node_modules\lodash\lodash.js:3001:24)
    at E:\Web\Joe.Wu\rn-awe\node_modules\lodash\lodash.js:4913:18
    at Function.forEach (E:\Web\Joe.Wu\rn-awe\node_modules\lodash\lodash.js:9359:14)
    at E:\xdl\src\project\Doctor.js:631:9
    at Generator.next (<anonymous>)
    at step (E:\Web\Joe.Wu\rn-awe\node_modules\react-native-scripts\node_modules\xdl\
    at E:\Web\Joe.Wu\rn-awe\node_modules\react-native-scripts\node_modules\xdl\build\
    at <anonymous>
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Environment

npm ls react-native-scripts: --<EMAIL_ADDRESS>npm ls react-native: -- (empty)  (Actually react-native is installed inside node_modules. I don't know why there is empty.)
npm ls expo: -- (empty)
node -v: v8.7.0
npm -v: 5.4.2
yarn --version: 1.3.2
watchman version: Not installed

Also specify:

Operating system: Windows 7
Phone/emulator/simulator & version: Nubia NX549J

It might be the case that not everything installed correctly.
Try being in rn-awe, rm -rf node_modules and then type yarn to install the dependencies again.

I try to reinstall several times, but it still does not work.

I installed react-native yesterday without problem. I run react-native-scripts version 1.7. Have you tried that version ?
Also i run the app with npm instead of yarn and I have read numerous problems regarding npm version 5 won't work with react-native.

The react-native-scripts version 1.7.0 is not in versions list.
E:\Web\Joe.Wu\rn-awe>yarn add<EMAIL_ADDRESS>yarn add v1.3.2
[1/4] Resolving packages...
Couldn't find any versions for "react-native-scripts" that matches "1.7.0"
? Please choose a version of "react-native-scripts" from this list: (Use arrow keys)
> 0.0.26
  0.0.1
  0.0.2
  0.0.3
  0.0.4
  0.0.5
  0.0.6
  0.0.7
  0.0.8
  0.0.9
  0.0.10
  0.0.11
  0.0.12
  0.0.13
  0.0.14
  0.0.15
  0.0.16
  0.0.17
  0.0.18
  0.0.19
  0.0.20
  0.0.21
  0.0.22
  0.0.23
  0.0.24
  0.0.25
  0.0.27
  0.0.28
  0.0.29
  0.0.30
  0.0.31
  0.0.40
  0.0.50
  1.0.0-rc.0
  1.0.0
  1.1.0
  1.2.0
  1.2.1
  1.3.0
  1.3.1
  1.5.0
  1.6.0

Is my yarn config registry problem?
E:\Web\Joe.Wu\rn-awe>yarn config list
yarn config v1.3.2
info yarn config
{ 'version-tag-prefix': 'v',
  'version-git-tag': true,
  'version-git-sign': false,
  'version-git-message': 'v%s',
  'init-version': '1.0.0',
  'init-license': 'MIT',
  'save-prefix': '^',
  'ignore-scripts': false,
  'ignore-optional': false,
  registry: 'https://registry.yarnpkg.com',
  'strict-ssl': true,
  'user-agent': 'yarn/1.3.2 npm/? node/v8.7.0 win32 x64',
  lastUpdateCheck:<PHONE_NUMBER>558 }
info npm config
{ config: 'registry=https://registry.npm.taobao.org',
  registry: 'http://r.cnpmjs.org/',
  dev: true,
  arg: '123', }

@travellerwjoe have the same problem with you when using create-react-native-app. You might want to try  Building Projects with Native Code instead.


Getting a "could not parse error" info. Not displaying refresh token

I have used this library for about 6 months and then suddenly I'm constantly getting a could not parse error and connection failed. When I try to get my new refresh token, it is not prompting it and again i get could not parse error on my serial monitor. Please help :((

Ok. Found it and fixed It!
The problem was an invalid spotify fingerprint. It must have changed with the last update.


Warden headdresses In-hand Sprites

About the PR
Adds in-hand sprites to the warden beret and cap. based #33386
Why / Balance
Currently it has no in-hands, so this is adding one.
Media

Requirements

[x] I have read and am following the Pull Request and Changelog Guidelines.
[x] I have added media to this PR or it does not require an ingame showcase.

Changelog

:cl: onesch

add: Adds in-hand sprites to the warden beret.
add: Adds in-hand sprites to the warden cap.

Also a small visual change like this does not need a changelog entry, could you remove that from your PR description?
You will of course still be mentioned in the game's credits for contributing.

Since emisse approved the sprite I went ahead and removed the changelog entry.
Thank you for your first contribution!

Since emisse approved the sprite I went ahead and removed the changelog entry.
Thank you for your first contribution!

I'm so glad I contributed to my favorite game!!


Don't call RewriteDriver::SetUserAgent on the UA in the request-headers.

RewriteDriver::SetRequestHeaders already pulls the UA from the request-headers.

LGTM


Bug: Login Page: Mobile view

Description
In mobile view, the login page is not responsive. User is unable to scroll horizontally past the screen height hence hindering the login procedure.
Screenshots
No response
Additional information
No response
What browser are you seeing this bug on?
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I have read the Code Of Conduct
[X] The changes don't break the code

Go ahead!


Unexpected EOF while reading bytes

Reproducible in:
The slack_bolt version
slack-bolt==1.18.0
slack_sdk==3.26.2
Python runtime version
Python 2.7.5
OS info
Ubuntu 20.04
Steps to reproduce:
Running a normal slack app which sends message in the form of blocks and receives input on submit button click.
Everything runs normally but in logs there is this below warning, what does this signify and can it cause issues ?
2024-02-20 13:18:42:WARNING: Error on <machine-ip>:9000 ping: Unexpected EOF while reading bytes
2024-02-20 13:18:42:WARNING: Connection was closed, reconnecting.
2024-02-20 13:18:42:WARNING: Error on socket shutdown: [Errno 107] Transport endpoint is not connected

@ashutosh-ag-2024 - When does this error occur? Does it occur consistently? Does it impact your app functioning?

This warning might be raised by the underlying modules such as Python standard libraries and WebSocket client libraries. If you see the warnings frequently, that may be caused by the network stability and/or some issues with proxy servers.
Enabling debug-level logging might be helpful to know more details, but if there is no issue affecting your end-users and you're observing the warnings in app logs, you can ignore it so far.


adding Universidad Virtual Internacional

Adding "Universidad Virtual Internacional" located in Colombia.

@SeittiffeDeveloper Please provide us with an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course. Also please specify whether the university gives the email addresses in this domain to the students for a lifetime or they expire when a student graduates.
Thank you.

Hello,
I’m studying Digital Graphic Design (https://www.uvirtual.edu.co/programas/diseno-grafico-digital/), the career it self is not directly related to IT specifics, however I’m looking forward into learn how to develop an e-commerce website using spring, java, SQL and Angular (I pretend to use the knowledge obtained from the career in order to design a fully functional and mesmerizing website)
The career im currently studying last 2 years with the option of study two more year in order to achieve a professional degree in graphic design.
Regards,

On Nov 22, 2021, at 07:30, Philip Torchinsky @.***> wrote:
@SeittiffeDeveloper https://github.com/SeittiffeDeveloper Please provide us with an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course. Also please specify whether the university gives the email addresses in this domain to the students for a lifetime or they expire when a student graduates.
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/JetBrains/swot/pull/13002#issuecomment-975378844, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASWTXXUIVTD3ZFDNQXTAXMLUNILS3ANCNFSM5IPUWUFA.

@SeittiffeDeveloper Thank you for the clarification. Pull request merged.


Bug from page text blocks

Description:
"There seems to be a bug in the header blocks. On edit mode, content written in those blocks are invisible but appear in test mode. I added a new block and it seems to be messing with a separate block under it."

Steps to Recreate:

Create a new form
Enter title name
Add the description
Add a short answer block - type in the question
Click on Add (default page text block) and click on select block
Move the page text block above the short answer block
Enter text into the page text block and the same text appears under short block

https://images.zenhubusercontent.com/315708034/084439d1-aadc-475a-9168-ad70fcd65eb5/screen_recording_2023_05_24_at_3_49_25_pm.mov

Hi @bryan-robitaille - I tested it out the fix on staging, but it seems like it still persists?
https://images.zenhubusercontent.com/315708034/a6aff9dc-07a1-4406-8b6e-55d63dadbf6b/screen_recording_2023_05_25_at_1_50_06_pm.mov

Re-opening this card to review the scenario where this issue persists when: the page text immediately follows the question and is then moved

@timarney I'm wondering if this is because the RichText elements are not using refs?  I think the bug is because of a mismatch between form store element index and the ref index.


feat: number of unpushed commits in dtn info cmd

feat: number of unpushed commits in dtn info cmd
Description
This PR enhances the daytona info command by adding a feature similar to git status, which checks the project's difference from the origin branch. It displays the number of unpushed commits, with changes made to info.go, service.go, tests, and documentation.

[ ] This change requires a documentation update
[ ] I have made corresponding changes to the documentation

Related Issue(s)
Closes #532
/claim #532
Screenshots

https://github.com/user-attachments/assets/51cd37a9-53aa-454f-8e1f-1caafa5a57c1
Notes
Please add any relevant notes if necessary.

@Tpuljak can you help me with formatting of information

@Tpuljak can you help me with formatting of information

@rajivkuma45 the output in the screenshot seems fine to me at first glance. I'll do a full review and we can follow up then. Thanks for the effort!

@Tpuljak @idagelic  any update

@divgro9 since we noticed that you made 2 new accounts and are keeping up with the constant tagging, we will be closing all 3 of your PRs.
As we mentioned too many times at this point, we are working as hard as we can to review every PR as soon as we can. Tagging us repeatedly greatly influences our productivity and we are forced to take measures to protect ourselves from such actions.

@Tpuljak I dont know who is the man divgro . why do you have closed my pr and blocked me from daytona .   MY CODE IS WORKING , TESTED , PASSED ALL THE CHECKS , I HAVE ALSO SENT SCREENCHOT.  JUST BECAUSE A UNKNOWN HAVE COMMENTED ON MY PR .


Incrimination of kickCount in ReactControllerHost

Fixes #1815
The _kickCount property is not linked to the react component, meaning the _kick function, does not change the value of _kickCount. I would consider: using a proxy or If there is no reason to keep the _kickCount updated: removing the property from ReactControllerHost, and instead setting it to a random hash or timestamp in the component.
Linted, formatted, and tested.

Thanks for the fix! We'll definitely need tests though. I'm happy to do that soon, or you can if you want to.

I'm not very familiar with testing in the way you are doing it. So if you wouldn't mind taking care of that, I would appreciate it.

Fixed with a test in https://github.com/lit/lit/pull/1820
Thanks for this PR though @Vac1911 !


Update to k8s.io/api/admissionregistration/v1

k8s.io/api/admissionregistration/v1beta1 is deprecated since Kubernetes 1.16+ and will be removed in 1.22+. Code should be updated to use new API types.

1.22 has been out for quite a while and this is still broken.

please try to use k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.1.1 instead.

I'll lose this issue as k8s.gcr.io/ingress-nginx/kube-webhook-certgen is now likely considered upstream.

I'll lose this issue as k8s.gcr.io/ingress-nginx/kube-webhook-certgen is now likely considered upstream.

I think this issue should be left open for exactly this reason.


DM-3568: Define code ownership of examples repo

This PR is intended to correctly assign everything the examples repo to their owners. I have assigned owners based on recent/prior contributions and topics.

No objections on the ownership, would be nice if we could use the team alias rather than an individual where possible.

@sagscmi I have committed your suggestion, but to make it work that team must be entered as contributor with write access in this repo by a repo admin.

No objections on the ownership, would be nice if we could use the team alias rather than an individual where possible.

@sagscmi I have committed your suggestion, but to make it work that team must be entered as contributor with write access in this repo by a repo admin.

@l2p- do you happen to know who the admins are for this repo?   All I can tell you is that I'm not one of them.
I do not, but I have asked org admins to assign me as repo admin so that I can resolve this myself.

@sagscmi I have added your team as contributor.


Gather requirements and user stories from stakeholders or product owners.

Related to #12

Required user-stories have been acquired and are the following: #10 #11 #12 #14


Fixing an IsDeleted issue on import/history.

Description
The PR addresses two issues.

IsDeleted() for Bundle.EntryComponent returns false on a deleted resource imported.
A _history response doesn't have the request and response section for a deleted resource imported.

Related issues
Addresses [issue #120287].
Bug 120287: Bundle.EntryComponent IsDeleted() method does not return TRUE for records deleted via $import
Testing
Tested $import/_history scenarios by locally running the service.
FHIR Team Checklist

Update the title of the PR to be succinct and less than 65 characters
Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
[ ] CI is green before merge
Review squash-merge requirements

Semver Change (docs)
Patch|Skip|Feature|Breaking (reason)

Should the verb for not deleted resource from $import be PUT?

Fixed as suggested.


Fedora 40/41 - Installing Multimedia Codecs

Describe the bug
The installation shows fail but also says it's already installed. It is confusing about its results. It used to install just fine without errors a few weeks ago. I don't know if it's related to them getting ready to release 41 out of beta or something in the code made recently.
Expected behavior
Clean results as either successful or completed if there is nothing to update, fail is misleading.
Screenshots

Additional context
There are other issues similar to this, I will report separately for records.
Checklist

[x] I checked for duplicate issues.
[x] I checked already existing discussions.
[ ] This issue is not included in the roadmap.
[ ] This issue is present on both stable and development branches.

/label 'script'


Editorial: Reword normative uses of "can"

In appendix B there is normative text reading:

An HTTP request to fetch a service worker's script resource can include the following header:

An HTTP response to a service worker's script resource request can include the following header:

Those should follow RFC2119 and be phrased as MUST or SHOULD or MAY,

Thanks!

Hmm, shouldn't that be described in the algorithm responsible for the fetch?

It was already described in the algorithm for those fetches. And the original "can include" text was just confusing in that it didn't make it clear at all that the Service-Worker header is always included for those requests.

It seems "can include" should then say "will include". You shouldn't make normative requirements twice.


How to cancel an async RPC call after calling Finish()?

Is there any method to cancel an async RPC call?

You can use ClientContext::TryCancel() to cancel the rpc, sync or async.


Store the menu item level as a param, custom Read More labels from  tag, support for shortcodes when get_preview uses content

This is for ease of access and can help with creating hierarchical structures

This is great @newkind -- the next thing we need before I can merge is a test to verify the behavior. Are you familiar with (or interested in getting acquainted with) PHPUnit + unit tests?

@jarednova sure! i'm always happy to learn something new! i just set up the VVV but I'm having issues with getting PHPUnit to run properly with Timber. I followed the wiki instructions but they seem incomplete. Right now I'm struggling with PHP Fatal error:  require_once(): Failed opening required '/tmp/wordpress-tests-lib/includes/functions.php' Do I need to install wordpress tests separately ? I tried also going with ./install-wp-tests.sh wordpress_unit_tests wp wp but looks like the http://wordpress.org/wordpress-master.tar.gz returns 404 - I might need to do some script edits ;)

Hmmmm, it's been a loooooong time since I've set stuff up. Let me run through the instructions and get those in better shape so you can have at it.

@newkind @jarednova to setup testing on your local, I suggest grabbing http://wp-cli.org/
After correct install on a proper environment, check out my quick summary guide via:
https://github.com/KLVTZ/WordPressHackersGuide/blob/master/08-unit-testing-in-wordpress/17.wordpress-testing.md

@newkind @jarednova keep in mind that the above guide uses the param argument found in scaffold:
https://github.com/KLVTZ/WordPressGalaxy/blob/master/public/content/plugins/justin/bin/install-wp-tests.sh#L4

Hmm I have added a new piece of code to detect custom read more labels in the  tag, but I'm not sure why it got added by this pull request ... Anyways, another pull request is here ;)

Thanks @newkind! I've merged the menu parts in and moved the stuff about shortcodes, etc. into #602 for further review and testing

No problem @jarednova :) I'm planning to do some more pull requests as I'm going through some Timber stuff and think that allowing a little bit more of user customization here and there would be a good thing.


wishlist (rust web application)

I'm working on a serverless web app, which leverages github oauth2 for accounts. I'm using cors.sh to request access tokens on user login. https://github.com/temportalflux/wishlist

Hi. Can you email me so that I can send you an API Key?
Here is my email address<EMAIL_ADDRESS>Thank you for applying. I Apologies for the late reply.


Open and read content of boxes from my computer ( my_box.hive )

Question
I want to know if there is a way to read the content of a Hive Box with my computer ( I'm able to do it with SQLLite db files with DB Browser for SQLLite )
I'm able to access hive files ( for example my_box.hive ), but I didn't find the right way to read its content.
Here is my screenshot :

I've tried to open it with DB Browser for SQLLite, but it's asking me for a password ... :
Here is my screenshot :

I need to access this data for debugging my app.
Version

Platform: Android ( Flutter )
Flutter version: Flutter 2.5.3
Hive version: 2.0.5

Thanks you in advance,

Does anyone find how can we read the hive content on the desktop for debugging purposes?
I was able to provide my customer cipher to the hive, but still, the password used to read and decrypt is used by the application, not SQLite.


Remove rounding from end users' public logs

This rounding sometimes makes debugging too hard and it's not important
with regards to privacy.
Note that currently used log-warper version doesn't support more granular
timestamps (1 second is maximal precision).

Since it's already approved by @dcoutts and gromak rebased, I'll merge this PR.


Using the library as "daemon" without stdin

I'm trying to integrate this library in an application that already uses stdin. It would be great to add a daemon option to the library so that there is no conflict about stdin.
Accessory, I would be interested to know how I should patch btlib.c to prevent stdin usage. Should I return 0 in setkeymode and readkey?

STDIN is only used for three things:

Input PIN code. This can be avoided by putting the PIN code in devices.txt, and the code around line 6176 that prompts for the code can be deleted.
Input passkey. This can be avoided by using security that does not require passkey input from the btferret keyboard, and the code around line 6207 that prompts for input can be deleted.
Exit from servers by pressing x key. As you say, this can be disabled by returning 0 from setkeymode and readkey. But you will have to rely on SERVER_EXIT returns to stop a server, or find some other way of stopping a server that is stuck waiting for input.

This is very useful. Thank you. A second argument to init_blue_ex noinput to init would be the best.
init_blue_ex(char *filename,int hcin, int noinput);


Badge Count inaccurate

Expected Behaviour
Show a "1" for badge count, or any number depending on how many push notifications have been received since last time app ran.
Actual Behaviour
Always says "7" as badge number, no matter how many push has been received
Reproduce Scenario (including but not limited to)
Send push notification to app when app is not inuse, badge goes from nothing to "7" instead of "1"
Steps to Reproduce
Install, set badge:true; send push notification when app is not in use
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
Sample Push Data Payload Data
payload is empty except for title and body
Sample Code that illustrates the problem
Logs taken while reproducing problem

How are u setting up the badge? Can u show the code?

Sure thing, its pretty much exactly as the example says. Here it is below:
     ```

var push = PushNotification.init({
android: {
senderID: "12345679"
},
ios: {
alert: "true",
badge: false,
clearBadge: true,
sound: 'false'
}
});
push.on('registration', function(data) {
console.log("=========registration event PUSH=========");
window.localStorage.setItem('appleTokenID',data.registrationId);
registerApp($http); //my unction to send info to my servers
});
            push.on('notification', function(data) { //have tried with and without this being commented. incorrect badge number occurs both cases

//                        alert(data.message);
//                        push.setApplicationIconBadgeNumber(function() {
//                                                           console.log('success');
//                                                           }, function() {
//                                                           console.log('error');
//                                                           }, 1);
//window.localStorage.setItem('push_waiting', true);
//                        console.log(data.message);
//                        console.log(data.title);
//                        console.log(data.count);
//                        console.log(data.sound);
//                        console.log(data.image);
//                        console.log(data.additionalData);
});

@slowsword it's up to you to send the data in order for iOS to setup the badge number. In the payload data send:
{
        "aps": {
            "alert": {
                  "title": "Hello",
                  "body": "from the push service"
                },
            "badge": 1
        }
}

whatever you send as the badge property will be what the OS shows. You can over ride this behaviour by calling the setApplicationBadgeNumber method.


StixCyberObservable and StixDomainObject should only have a single subclass assertion that they are subclasses of StixObject.

This has been resolved (fixed in incident-update-2021-12-09 branch).


big number 15 significant digits error

yarn cli-rinkeby deposit 1.61744723307346186 WETH
yarn run v1.13.0
$ NETWORK=rinkeby node src/cli/cli.js deposit 1.61744723307346186 WETH
Keccak bindings are not compiled. Pure JS implementation will be used.
  INFO-dx-service:repositories:EthereumClient Checking Node connectivity... +0ms

  INFO-dx-service:repositories:EthereumClient Using Node Geth/v1.8.20-omnibus-c5febb98/linux-amd64/go1.11.1 +1s
  INFO-cli Deposit 1.617447233073462 WETH into the DX for 0x5899c1651653e1e4a110cd45c7f4e9f576de0670 +0ms
  INFO-dx-service:services:DxTradeService Fund the account 0x5899c1651653e1e4a110cd45c7f4e9f576de0670 with 1.617447233073462 WETH +0ms
cli.js deposit <amount> <token> [--account account]

Deposit funds in order to be used on the DX

Positionals:
  amount   Amount to buy, i.e. 0.8                                                        [required]
  token    Name of the token, i.e. WETH                                          [string] [required]
  account  Address where you send the tokens                                                [string]

Options:
  --version  Show version number                                                           [boolean]
  -h         Show help                                                                     [boolean]

{ BigNumber Error: lt() number type has more than 15 significant digits:<PHONE_NUMBER>073462000
    at raise (/Users/billy/gnosis/dx-services/node_modules/bignumber.js/bignumber.js:1177:25)
    at new BigNumber (/Users/billy/gnosis/dx-services/node_modules/bignumber.js/bignumber.js:261:50)
    at BigNumber.P.lessThan.P.lt (/Users/billy/gnosis/dx-services/node_modules/bignumber.js/bignumber.js:1551:35)
    at DxTradeService._depositEtherIfRequired (/Users/billy/gnosis/dx-services/src/services/DxTradeService/DxTradeService.js:307:27)
    at processTicksAndRejections (internal/process/next_tick.js:81:5) name: 'BigNumber Error' }
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Hi,
I think this bug occurs because BigNumber(etherTokenBalance variable) is compared to normal number(amount variable)
https://github.com/gnosis/dx-services/blob/68e0ddae27ae567381c19cd1c0386f9f425ce789/src/services/DxTradeService/DxTradeService.js#L305-L307
Maybe line 307 should look like:
if (etherTokenBalance.lessThan(amountInWei)) {
But I am not sure, the same error occurs with other cli commands like 'buy', that is why you cannot use  your whole balance if it has more than 15digits. There can be more places in the code that behave the same, maybe the author can confirm this.

Thank you for reporting.
BigNumber library is able to automatically convert Javascript Number into BigNumber to do operations, but this conversion has a 15 digit limitation. In order to avoid that is recommended to convert Javascript Number to String first.
In this PR we will change CLI commands to convert the amount passed to Wei using an internal util that checks this limitations and will pass an usable BigNumber even with an over 15 digit amount:
https://github.com/gnosis/dx-services/pull/49
This is planned to be fixed in v2.0.3

I think it might be necessary to bump yargs version too acording to comments below:
https://github.com/yargs/yargs/issues/550#issuecomment-460006293

@TomFrost the specific issue you were running into should have been addressed by the fact that we now treat options that look like numbers as strings, if they're larger than JavaScript's Number.MAX_SAFE_INTEGER.

https://github.com/yargs/yargs/issues/1099
Otherwise more than 15 digits numbers could by rounded anyway while passing as CLI arguments.
By the way I am not sure about my observation here.


[MRG] Upgrade to support newest scikit-learn version

Reference Issues/PRs
No.
What does this implement/fix? Explain your changes.
When upgrading to sklearn==0.24.2, it occurs five FAILs during python setup.py test.

Check why test FAILs occurs.
Update the test case to pass it.

Any other comments?

It's worth thinking about the efficient ways to upgrade when dependencies upgrade.
Please see the comments below.

Hi @ariapoy,
Thank you so much for submitting this PR.
There is one thing I would like to make sure, the change of test_hs_active_selecting, test_hs_active_selecting, and test_hs_random_selecting is because of Fixed a bug in datasets.load_iris which had two wrong data points, right?
Thanks.
Yao-Yuan

Hi @yangarbiter,
Yes! Change of sklearn.dataset.load_iris affect test_hs_active_selecting, test_hs_active_selecting, and test_hs_random_selecting in sklearn==0.20.

Codecov Report

Merging #188 (35e82ae) into master (2432b51) will increase coverage by 0.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #188      +/-   ##
==========================================
+ Coverage   89.47%   89.53%   +0.05%
==========================================
  Files          37       37
  Lines        1568     1596      +28
==========================================
+ Hits         1403     1429      +26
- Misses        165      167       +2

Impacted Files
Coverage Δ

libact/query_strategies/multiclass/mdsp.py
78.76% <100.00%> (ø)

libact/utils/__init__.py
77.27% <0.00%> (-4.55%)
:arrow_down:

...ery_strategies/multiclass/hierarchical_sampling.py
95.32% <0.00%> (-0.54%)
:arrow_down:

libact/labelers/ideal_labeler.py
100.00% <0.00%> (ø)

libact/query_strategies/random_sampling.py
100.00% <0.00%> (ø)

...query_strategies/multilabel/binary_minimization.py
100.00% <0.00%> (ø)

..._strategies/multilabel/adaptive_active_learning.py
100.00% <0.00%> (ø)

.../multiclass/active_learning_with_cost_embedding.py
100.00% <0.00%> (ø)

...trategies/density_weighted_uncertainty_sampling.py
98.71% <0.00%> (+0.01%)
:arrow_up:

..._strategies/multilabel/maximum_margin_reduction.py
97.82% <0.00%> (+0.04%)
:arrow_up:

... and 10 more

Continue to review full report at Codecov.

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

https://github.com/ntucllab/libact/pull/188/checks?check_run_id=3258702214
It appears that sklearn > 0.24 is not installable on python 2.7, maybe we should also consider dropping support for python 2.7.

https://github.com/ntucllab/libact/pull/188/checks?check_run_id=3258702214
It appears that sklearn > 0.24 is not installable on python 2.7, maybe we should also consider dropping support for python 2.7.

@yangarbiter
Agree! Follow Warning Scikit-learn 0.20 was the last version to support Python 2.7.
We could drop support for Python 2.7.
Sorry for forgetting to notify you that I just test Ubuntu:20.04 with default Python 3.8.
I notice the FAIL in ubuntu-latest, 3.9 during CI checking.
I'll check it later.
Thanks!

https://github.com/ntucllab/libact/pull/188/checks?check_run_id=3258702214
It appears that sklearn > 0.24 is not installable on python 2.7, maybe we should also consider dropping support for python 2.7.

@yangarbiter
Agree! Follow Warning Scikit-learn 0.20 was the last version to support Python 2.7.
We could drop support for Python 2.7.
Sorry for forgetting to notify you that I just test Ubuntu:20.04 with default Python 3.8.
Does it work?

I notice the FAIL in ubuntu-latest, 3.9 during CI checking.
I'll check it later.
Thanks!

Libact linting / build (ubuntu-latest, 3.9) (pull_request) this one should fail, which is fine since this is coding style check.
I'll try to fix them (you could also help if you want) after this PR is merged.


Fill cache configuration before creating new cache filesystem

if local disk cache enabled
What type of PR is this：

[ ] bug
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

run starrocks_admit_test


#147 issue fix

#147 issue fix

Sorry, but I am closing this PR. Please refer to https://github.com/react-native-community/react-native-linear-gradient/pull/150#issuecomment-290373936 for explanation.


Integrate GToolkit Magritte project

Integrate feenkcom/gt4magritte.

Example of GToolkit Magritte Integration
You can see on the right side a GToolkit Magritte widgets with following properties:

changed (and not accepted) fields are indicated using yellow bars,
field validations are displayed in red whenever they are not satisfied,
users can add and remove items from the collections.


feat: Add support for windows

Also look for _netrc file in USERPROFILE.
fixes #1 and fixes #2

This fix should use conditional compilation with target_family.

This fix should use conditional compilation with target_family.

You are right, I've updated the pull request. Please review again.

Could you please push a release with this change to crates.io. Thanks in advance!


[Icon Request] html and scss icons for Angular (+2)

Checklist:

[x] I'm sure this issue is not a duplicate?
[x] I want to create an icon request(if not, remove these lines below):
- Type: extension
- Icon Name: angular-template
- Sample original Icon (32x32/svg/transparent whenever possible): [url]
- Extensions: [ *.component.html, *.component.scss ]

I think this could be just the *.component.ts, with the Angular red logo but with the HTML5, and SCSS as subindex.

We have already talked about those icons and we have decided not to go forward with it.
@robertohuertasm Are you thinking it?

My first reaction has been to say "create your own custom icons for this" but... I'm actually thinking about this and, to be frank, I don´t have a clear idea in my mind.
One should argue that this would be following the same pattern we started with .component.ts... but then I think that if we start down this road we´ll end up with lots of angular icons everywhere (i.e. .component.spec.ts probably should be also considered) and we'll lose the point of spotting the angular files.
Let's play with this idea a little more time before deciding what to do. @jens1o, @JimiC what is your point of view, if any?

I think at some time, it is unmaintainable and too complicated for the user, I don't think we need the icons.

vs

I somehow don't get the point... I don't know why we should introduce this, because this is true, but on the other side, it will look the same. I can't decide, but I think we don't need them.

Here I posted another one with more files, just to see the contrast and how easy is to spot them in a real project loaded with lots of icons.
The current one is clear. The proposed one is not as clear but it's very uniform and makes the component folders to look nicely structured.

For the history, I was the one that proposed to add Angular specific icons for html and css.
But @robertohuertasm convinced me that there is no point in doing it because:

It will confuse users as it will not be clear which file is which.
Angular html file is still an html file and so is a css one. There isn't any fundamental syntax chance in them (yes I know that you have Angular directives as attributes in them but the file is still an html one in most parts).

The js, ts (and we should have added the dart too) have a syntactic structure that is specific to Angular and that's the main reason they got a specific icon.
So my vote is to leave things as they are.

I agree with @JimiC

I didn't remember that but that was indeed my first thought. For the record, here is the link to the comments .
Anyway, if it's ok with you and given that we have second sets of icons, I'd propose to upload them in case anyone wants to use them and customize the experience. This will leave things as they are and allow angular fanboys to set their angular icons everywhere. Is this fair enough?

angular fanboys
sigh

Okay, but I'll stick to it: I don't need it.

You guys rock! Thank you!


How to update

just asking, how do I update the browser?

Just download and install the new version over the old one.

cmn! see #719

#719


Update faq.md

Added 2 FAQ for cached logon

@RavennMSFT : Thanks for your contribution! The author, @MarkusVi, has been notified to review your proposed change.

#sign-off

Hi @RavennMSFT:
For future PRs, you should join MSFT / GitHub accounts and make PRs in the private repo, so the content can be staged and validated by the current validation rules.
Follow the instructions in Set up Git repository locally for documentation to link your GitHub alias with your Microsoft account.
Then, make content contributions through the private repository so the content can be staged and validated by the current validation rules.
Read about working in the public repo for more information.
Thank you.
Trisha
Merging now


No difference for users joining themselves or being added

I receive messageChatAddMembers in both cases, when I join a group or also when I am being added by someone else. Official clients can make a difference it seems, also our old Telegram app could calculate this from the update message (with a lot of mistakes though, since determining the join action was not easy). Is there a way to distinguish this in tdlib?

The messages will have different users as a sender.

Thanks that solved it! For reference, it will be the same for messageChatDeleteMembers.


Implement Different Types of Linked Lists and Operations

I would like to contribute by implementing different types of linked lists along with basic and advanced operations in C/C++. The linked lists and operations are as follows:
Linked List Types:
Singly Linked List (SLL)
Singly Circular Linked List (SCLL)
Doubly Linked List (DLL)
Doubly Circular Linked List (DCLL)
Operations:
Basic: Insert, Delete, Display.
Advanced: Search, Sort, Reverse, Count nodes, Detect loops.
Proposed Approach:
Implement each linked list in separate files.
Add basic operations first, followed by advanced operations.
Language: C/C++
This contribution will enhance the repo's data structure implementations, making it more comprehensive for developers.

Kindly assign this issue to me. I’m eager to contribute and implement these features.

Hi, I have already added a code in C folder, a randomized quick sort. will there be any issues or that will be accepted for Hactoberfest 2024? If there is any issue, please let me know, I will make the necessary changes.


Play ads in  pre-roll, mid-roll and end-roll range

Play ads in  pre-roll, mid-roll and end-roll range

Have you tried using the tagUrl option? We're using the Google IMA SDK so they should be supported.

Okay, @sampotts Thanks.


File to import not found or unreadable: minimal-mistakes/skins/air

[X] This is a question about using the theme.
[ ] This is a feature request.
[ ] I believe this to be a bug with the theme.

[X] I have updated all gems with bundle update.
[X] I have tested locally with bundle exec jekyll build.

Environment informations

Minimal Mistakes version: 4.5.2
Jekyll version: 3.5.2
GitHub Pages hosted: no
Operating system: Travis

Updated to use the new version of MM locally and everything worked as expected, however, when committed to use the latest update 4.5.2, Travis CI complained:
 Theme Config file: /home/travis/build/justinrummel/jr.com-mm/vendor/bundle/ruby/2.4.0/bundler/gems/minimal-mistakes-1a2a953dfb21/_config.yml
            Source: /home/travis/build/justinrummel/jr.com-mm
       Destination: /home/travis/build/justinrummel/jr.com-mm/_site
 Incremental build: disabled. Enable with --incremental
      Generating...
              Lunr: Creating search index...
              Lunr: Index ready (lunr.js v0.4.5)
  Conversion error: Jekyll::Converters::Scss encountered an error while converting 'assets/css/main.scss':
                    File to import not found or unreadable: minimal-mistakes/skins/air. Load paths: /home/travis/build/justinrummel/jr.com-mm/vendor/bundle/ruby/2.4.0/bundler/gems/minimal-mistakes-1a2a953dfb21/_sass /home/travis/build/justinrummel/jr.com-mm/vendor/bundle/ruby/2.4.0/bundler/gems/minimal-mistakes-1a2a953dfb21/_sass on line 3
jekyll 3.5.2 | Error:  File to import not found or unreadable: minimal-mistakes/skins/air.
Load paths:
  /home/travis/build/justinrummel/jr.com-mm/vendor/bundle/ruby/2.4.0/bundler/gems/minimal-mistakes-1a2a953dfb21/_sass
  /home/travis/build/justinrummel/jr.com-mm/vendor/bundle/ruby/2.4.0/bundler/gems/minimal-mistakes-1a2a953dfb21/_sass on line 3
The command "./script/cibuild" exited with 1.

What is interesting is I set to use ruby 2.4.1, which is later confirmed to be available, yet the error path is referencing /ruby/2.4.0/.
$ rvm use 2.4.1 --install --binary --fuzzy
$ export BUNDLE_GEMFILE=$PWD/Gemfile
$ ruby --version
ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-linux]
$ rvm --version
rvm 1.29.2 (latest) by Michal Papis, Piotr Kuczynski, Wayne E. Seguin [https://rvm.io/]
$ bundle --version
Bundler version 1.15.4

Not sure if you can see Travis CI outputs, but here is the link
Repo: https://github.com/justinrummel/jr.com-mm

I've seen that weird version of Ruby too when testing. What I think the issue is, is the missing Sass partials for the new skins. I haven't released it yet so maybe you have some sort of conflict using the 4.5.2 gem and what's currently only on master in the MM repo.
When I do a 4.6 release all the new skin stuff will be in the gem, but it's not there yet.

Think the issue is here in your Gemfile
gem "minimal-mistakes-jekyll", :github => "mmistakes/minimal-mistakes"
# gem "minimal-mistakes-jekyll", :github => "mmistakes/minimal-mistakes", :branch => 'color-skins'

You're using the latest on master, which doesn't have the color skin stuff. You need to uncomment that second line if you want that.
Or remove this line from your /assets/css/main.scss file.
@import "minimal-mistakes/skins/{{ site.minimal_mistakes_skin | default: 'default' }}"; // skin

ah!  my fault... thought it was released.  Thanks for the help!

No worries. Should be released soon...


backend-storage: add RWO FS support

What this PR does
See https://github.com/kubevirt/community/pull/314
Before this PR:
After this PR:

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

backend-storage now supports RWO FS

/test all

/test all

/test all

/test all

/test all

/cc @acardace

/retest

/retest

Left another review, still some things to adjust but I think we're almost there!

@dhiller is there a way to mark tests as incompatible with the flake-checker? I duplicated 4 test into sig-compute to test behavior when NFS is absent.
They fail on the flake checker since it has NFS... Thanks!

/approve
Thank you @jean-edouard !

@jean-edouard kudos for the great idea to add a separate label for flake-check compatibility.
I figure we need to add the label here: https://github.com/kubevirt/kubevirt/blob/main/automation/repeated_test.sh#L199
Would you be up to creating a follow up PR marking all the other tests that have been filtered out in other ways? (Since I just came back I might have that in my emails - apologies for pinging you in that case)

@jean-edouard kudos for the great idea to add a separate label for flake-check compatibility.
I figure we need to add the label here: https://github.com/kubevirt/kubevirt/blob/main/automation/repeated_test.sh#L199

Isn't that what I already do? :)

Would you be up to creating a follow up PR marking all the other tests that have been filtered out in other ways? (Since I just came back I might have that in my emails - apologies for pinging you in that case)

Sure, do you have any pointers?

/test pull-kubevirt-check-tests-for-flakes

@jean-edouard kudos for the great idea to add a separate label for flake-check compatibility.
I figure we need to add the label here: https://github.com/kubevirt/kubevirt/blob/main/automation/repeated_test.sh#L199

Isn't that what I already do? :)

Yeah - glancing at this PR I just missed it, you are right :blush:

Would you be up to creating a follow up PR marking all the other tests that have been filtered out in other ways? (Since I just came back I might have that in my emails - apologies for pinging you in that case)

Sure, do you have any pointers?

I was thinking about what is currently achieved with the exclude-native-ssh label but maybe @0xFelix has a better POV here about whether this makes sense. It wouldn't hurt to broadcast about this new label anyway, so that everyone knows, by i.e. adding a paragraph here : https://github.com/kubevirt/kubevirt/blob/91e5d7899442f97b2635c82bd0d446c92969dc99/tests/README.md?plain=1#L3

/retest-required

/test pull-kubevirt-e2e-k8s-1.31-sig-network
/test pull-kubevirt-e2e-k8s-1.31-sig-compute-migrations

@jean-edouard The cache fixes are required in previous versions

@jean-edouard could you please open an upstream issue for https://issues.redhat.com/browse/CNV-50720

@jean-edouard could you please open an upstream issue for https://issues.redhat.com/browse/CNV-50720

Wouldn't it be basically the same as https://github.com/kubevirt/kubevirt/issues/13112 ?

@jean-edouard could you please open an upstream issue for https://issues.redhat.com/browse/CNV-50720

Wouldn't it be basically the same as #13112 ?

It's similar, even if we fix #13112 we will still have a problem when the source and the target crash.
In #13112, the controller can observe that the target pod is happily running on the target already, so it can finalize the migration. (one possible solution)
in the case when the source and the target are gone, we don't know how to finalize the migration.
We don't know which volume was updated last.
As it is today if the source pod is gone without communicating the results to the handler we cannot tell which volume to choose when the VM starts again.

just a reminder - we should update the user-guide regarding this.


Unravel bufrw Series workaround

This removes the work-around and retains the regression test, which still passes, having updated bufrw with the proper bufix for SeriesRW.
r @jcorbin @Raynos @abhinav

lgtm

:+1:


MVP Content Sharing - Link Generator using Sharing ID

[ ] Bug fix?
[x] New sample?
[ ] Related issues: fixes #X, partially #Y, mentioned in #Z
[ ] Needs API permissions?
[ ] Has other prerequisites? (E.g. requires a list, document library, etc.)

What's in this Pull Request?
Are you a Microsoft Learn Student Ambassador or a Microsoft's Most Valuable Professional? Our app lets you generate links with your unique ID in seconds. Share resources seamlessly and make an impact

Checklist

[x] My pull request affects only ONE sample.
[x] I have updated the README file.
[x] My README has at least one static high-resolution screenshot (i.e. not a GIF)
[x] My README contains complete setup instructions, including pre-requisites and permissions required

Any Update @Katerina-Chernevskaya

Hi @shaheerahmadch,
The maintainers are managing this during their spare time. Your patience is greatly appreciated, and we will attend to your PR as soon as we are able to.


Switch from node12 to node16 to avoid top-level await issues

Today, --moduleResolution node12 is a pit-of-failure experience because Node.js 12 is already oldish and doesn't support top-level await. This was brought up in https://github.com/microsoft/TypeScript/issues/46452 (and in this comment https://github.com/microsoft/TypeScript/issues/46452#issuecomment-952987242)
Before TypeScript 4.7 RC, we should remove node12 as an option and provide a node16 option instead.`

I get wanting a newer numbered node version (and am all for it); but is there a reason to remove the node12 support? It's the first node version with native esm support, and it has some important caveats in its resolution that are fixed or changed by later versions.

It's the first node version with native esm support, and it has some important caveats in its resolution (in addition to the whole no-TLA thing) that are fixed or changed by later versions.

The way I see it, every time a user has to decide between these, and every time we have to list every possible option, is a place where dropping node12 and starting at node14/node16 could improve those experiences. So let's not provide awkward middle grounds leading up to the experience that most users will want, and let's not obligate ourselves to supporting the caveats either of Node 12 either.

You don't see users wanting to support every node version that supports esm format source code?

Like, I'm all for nodenext being the preferred mode - you really don't have a good reason to not track latest node unless you're building for maximal compatibility.

Well people need a stable target. I just think we have a decent amount of agreement on https://github.com/microsoft/TypeScript/issues/46452#issuecomment-952987242 around dropping node12 in favor of a later version which would both allow us to shed some extra corner-cases and remove a step of friction for users.

node16 will be the first node version to support https imports in it's release line, as an FYI.

FYI @DanielRosenwasser TLA in node is still documented as experimental even in 18 (though there's an open PR to stabilize it in the 18 timeframe since it's officially stabilized in v8). If we respect the docs, we shouldn't even allow TLA in a hypothetical node18 just yet.

@DanielRosenwasser @weswigham
node v12 has reached end-of-life April 30th 2022 https://nodejs.org/en/about/releases/   it's probably a good idea to drop node12 and move to node16 directly for TypeScript v4.7.

After this change, a nightly, RC, or stable version of TypeScript will issue the following error message:
error TS6046: Argument for '--module' option must be: 'none', 'commonjs', 'amd', 'system', 'umd', 'es6', 'es2015', 'es2020', 'es2022', 'esnext', 'node16', 'nodenext'.
error TS6046: Argument for '--moduleResolution' option must be: 'node', 'classic', 'node16', 'nodenext'.

Instead of node12, you should switch to node16.


Integrate with Connexion and API Gateway

Credit goes to @larsbutler for doing the initial integration.
Also updated the README, so it can be converted to reStructuredText easily for new releases as the long description on PyPI.

Looks good to me. Thanks for porting this over to Fleece! I've been meaning to do that for a while. :)


binary data?

what is the best way to make this work effectively on binary data?
i'm assuming the network won't learn to output binary on its own, even if all the inputs are binary. trivially you can just threshold each output value at 0.5, but is there a better way to do this? i'm hoping to take advantage of having only two states to get away with using a larger input vector.

I think shareholding input at 0.5 to either 0.0 or 1.0 is sufficient and generally done. I'd expect output to quickly favor binary as anything else would tip of the discriminator. Main speed up would be making sure the architecture has 1 channel and not 3.

Have you tried using sigmoid generator output instead? When you train a DCGAN on mnist with sigmoid outputs it's pretty much always railed binary like you expect.

thanks for the tips!
relatedly -- is my intuition about using larger inputs incorrect? i.e. in the image examples, each element is an 8-bit int (0-255). if i use binary instead, is it fair to expect comparable performance for input vectors 8x the same size?


az image create -- Limited command options as compared to Azure Portal

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug

Perhaps a maturity issue as opposed to bug. The documentation for az image create does not list a clear way to specify storage-sku for each data disk attached to an image.
Also encryption options visible in Image create UI, is not listed in configuration options in Azure CLI.
Sample command: -- this is a long multi-line command in windows cmd. It works, but does not allow specifying encryption at rest, or per data disk storage type, as seen in the GUI.
az image create --name image1 -g resource_group01 --os-type Linux --location eastus --hyper-v-generation V1 ^
--zone-resilient true --storage-sku Premium_LRS ^
--source https://storage1.blob.core.windows.net/container1/root-disk.vhd ^
--data-disk-sources https://storage1.blob.core.windows.net/container1/second-disk.vhd https://storagestratozen.blob.core.windows.net/container1/third-disk.vhd ^
--os-disk-caching ReadWrite ^
--data-disk-caching ReadWrite ^
//Relevant documentation
https://docs.microsoft.com/en-us/cli/azure/image?view=azure-cli-latest#az-image-create
In Summary:

How do I specify encryption for the image, as seen in the UI?
How do I specify storage type (premium etc) per data disk if multiple?
How do I specify disk read/write caching per data disk added? -- I mean usually I'll do read/write for everything, but why does the option not exist?

Is there a simple way to do this via azure cli, or do I have to use some way to input json (no example documentation).
Is the only option an ARM template?

Hi @qwordy , could you please help with this issue ? Thanks

Reasonable ask. Added to S178. It is a known issue. Azure CLI doesn't guarantee that it supports all features defined in specification. Neither does Portal. Azure CLI and Portal are designed separately by different people. Sometimes they have differences.

Thanks! I look forward to seeing it in upcoming release.

hi @qwordy could you pls update status of the issue? thanks.

This feature request is in the queue and does not have a definite timeline now.

How do I specify encryption for the image, as seen in the UI?
How do I specify storage type (premium etc) per data disk if multiple?
How do I specify disk read/write caching per data disk added? -- I mean usually I'll do read/write for everything, but why does the option not exist?

The REST documentation images/create-or-update doesn't seem to show support for these features, which requires service team to confirm whether support is required

@SimSama user images do not support encryption and there are no plans to support it. We encourage our customers to move over to the Shared Image Gallery. You can import your user image into the Shared Image Gallery by following these instructions.

@SimSama user images do not support encryption and there are no plans to support it. We encourage our customers to move over to the Shared Image Gallery. You can import your user image into the Shared Image Gallery by following these instructions.

I think you are getting caught up in word semantics. Disk encryption for custom linux images seems to be supported in the console. If you are trying  to say disk encryption is not supported for any non microsoft supplied image, then we'd move our customers off Azure.
I only ask for features supported in the console as of today, and 6+ months ago be replicated in REST / cmd. These things are already implemented features as of this moment, just not in all configuration methods.
These are all options I had available to me in the GUI, but no equivalent option in the command line, so to say they don't work or not supported outright just seems wrong.
If you don't want to fix it, the discussion is over it seems. More revenue for AWS.

I misspoke. The API for user images does support encryption for data disks.
@zhoxing-ms examples may be missing but the Images API supports Disk Encryption Set.
@qwordy is your team still working on supporting this?

How do I specify encryption for the image, as seen in the UI?
How do I specify storage type (premium etc) per data disk if multiple?
How do I specify disk read/write caching per data disk added? -- I mean usually I'll do read/write for everything, but why does the option not exist?

@olayemio Hi, our team is working on CLI. May I ask does REST API support these features now?
I have not found the relevant documentation at this time. If service supports them, how should CLI pass in parameters to REST? It would be better if you could give us some examples~

@zhoxing-ms Yes, all these features are supported in the REST API. Customers are only able to specify all three settings if they use disks, snapshots or blobs to create the image. For customers that use VMs to create their image, the settings have to be applied to the disks on the VM before the image capture process.
Here is a sample that has uses encryption, specifies storage type, and the caching.
{
  "location": "East US",
  "properties": {
    "storageProfile": {
      "osDisk": {
        "osType": "Linux",
        "snapshot": {
          "id": "/subscriptions/[subid}/resourceGroups/{rg}/providers/Microsoft.Compute/disks/{osDiskName}"
        },
        "diskEncryptionSet": {
          "id": "/subscriptions/[subid}/resourceGroups/{rg}/providers/Microsoft.Compute/diskEncryptionSets/{desName}"
        },
        "caching": "None",
        "osState": "Generalized"
      },
      "dataDisks": [
        {
          "lun": 0,
          "managedDisk": {
            "id": "/subscriptions/[subid}/resourceGroups/{rg}/providers/Microsoft.Compute/disks/{diskName0}"
          },
          "diskEncryptionSet": {
            "id": "/subscriptions/[subid}/resourceGroups/{rg}/providers/Microsoft.Compute/diskEncryptionSets/{desName}"
          },
          "storageAccountType": "Premium_LRS",
          "caching": "ReadOnly"
        },
        {
          "lun": 1,
          "managedDisk": {
            "id": "/subscriptions/[subid}/resourceGroups/{rg}/providers/Microsoft.Compute/disks/{diskName1}"
          },
          "diskEncryptionSet": {
            "id": "/subscriptions/[subid}/resourceGroups/{rg}/providers/Microsoft.Compute/diskEncryptionSets/{desName}"
          },
          "storageAccountType": "Standard_LRS",
          "caching": "ReadWrite"
        }
      ],
      "zoneResilient": false
    }
  }
}

@olayemio  OK, I see. Thank you for the example. We will arrange development for this requirement~


Hospitality pawns don't have enough silver

extra multiplier on the hospitality multiplier so they can buy stuff

Resolved by recent hospitality update


possible races (may be worth while checking)

Hi,
While trying to understand #1009 I noticed a couple of places which may be data races. I've not seen any problems caused by these; but I thought I'd mention them so you can consider if they're something worth changing.
(i) increment of h.fileCounter and subsequent read (during filepath.Join()), in a couple of places. Maybe these should be within a write lock, not only a read lock.
(ii) data race in managedRPCRevise() during call obligation.fileSize(). Race was with ProcessConsensusChange(), on write of ob.OriginTransaction. [This one was flagged by the golang race detector]
Thanks.

The host code is being change significantly on the renter-host-upgrades branch, so it's unlikely that these races will recur there. But we'll be on the lookout! Thanks.


Add support for more Buttons

Hi,
thank you for your effort in putting together this project! I managed to extend and compile the code and use it to revive an old and no longer driver supported Thrustmaster FFB Wheel. Yet I am struggling to extend the number off buttons/axis supported by the code. I couldn't find the spot where i could rise/change the Number of buttons/axis. As fas as t know there are special axes e.g  for accelerator in the HID... could you help out?
Thank you and my best wishes!
S.

I made another Step and found where to change the number of buttons from 8 to 16. The HID Description yet is cryptic...
I've tried to change the USAGE_MAX in the descriptor to 16 (0x10) and the REPORT_COUNT as well and changed the variable type from uint8 to uint16 for all the handling functions and HID Struct... I can see the Buttons now but the whole communication seems to have stopped, no input is being outout... Broken HID communication!?
  //================================Input Report======================================//
  0x09, 0x01, // USAGE (Pointer)
  // WheelReport
  0x85, HID_REPORTID_WHEEL, // REPORT_ID (1)
  0xA1, 0x00, // COLLECTION (Physical)
  // Button for Shifter
  0x05, 0x09, // USAGE_PAGE  (Button)
  0x19, 0x01, // USAGE_MINIMUM (Button 1)
  0x29, 0x10, // USAGE_MAXIMUM (Button 16)
  0x15, 0x00, // LOGICAL_MINIMUM (0)
  0x25, 0x01, // LOGICAL_MAXIMUM (1)
  0x75, 0x01, // REPORT_SIZE (1)
  0x95, 0x10, // REPORT_COUNT (1)
  0x81, 0x02, //INPUT (Data,Var,Abs)

You have to change in joystick report. I havent time to maintain this repo :)


Create dependabot.yml

Checklist

[ ] I have read the CONTRIBUTING guide
[ ] Good naming (as clear and simple as possible)
[ ] Correct behavior if external API endpoints are down, return 404, 504 (or no answer), 401 errors (ddos simulation)
[ ] I tested desktop/mobile resolution
[ ] I tested light/dark theme
[ ] I tested different languages
[ ] I checked the functionality once again (AFFECT MONEY)
[ ] I checked the work on the Testnet
[ ] I checked the work on the Mainnet
[ ] I checked the work in the plugin
[ ] I checked the PR once again

Tests
Please start auto tests as follows:

add a label swap test to start swap tests
add a label withdraw test to start withdraw tests

You can skip these tests if you completely sure that your changes aren't related to this functional
Original issue

Video / screenshot proof

Депендабот пропал, чтоб вернуть надо файл сделать https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates

builded https://testnet4728.swaponline.site ;

Депендабот пропал, чтоб вернуть надо файл сделать https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates

вроде все поля нужные сделаны, можно мержить


Need category name in check-in report

How do we reproduce the problem?
In my check-in report, I need to see the titles of the category (F. A. S. T. E. or R.) in addition to the subcategory/action that characterizes the category for the check in. This will help me more easily share with my group which letter I'm referring to during my check in.
What's expected?
What do you get instead?
Additional info

Q
A

PHP version

Operating System and Browser

I assume you're talking about the email report? The category titles are above the "Selected Behaviors" section. Do you mean the "Question Responses" section?
Looks like it's a similar story with the website (the /checkin/view page). The Behaviors list has the categories and Questions don't.

Hi Corey,
Yes, exactly – in the “question responses” section, I would like to see the category titles listed (Forgetting priorities, anxiety, etc). A few of the guys in my group are using the Faster Scale app/site now, and I’ve noticed that we’re always trying to remember which category corresponds with our question responses at the top of the report. Hard to remember in the moment and requires scrolling down. I’ve found this to be true on both the email and web reports.
For example (from your attachment), I can see that you wrote “secrets,” but I can’t remember if that’s associated with forgetting priorities or anxiety until I scroll down and look in the selected behaviors section. If the category was also listed at the top with the question responses (ex: forgetting priorities: secrets), it would be easier to share with my group more fluidly. “For me this week, forgetting priorities looked like keeping secrets from my wife.”
Thanks for writing me – and thank you for developing this excellent tool.
Brandon
From: Corey Watts @.>
Reply-To: CorWatts/fasterscale @.>
Date: Tuesday, April 6, 2021 at 08:12
To: CorWatts/fasterscale @.>
Cc: Brandon Pearce @.>, Author @.***>
Subject: Re: [CorWatts/fasterscale] Need category name in check-in report (#194)
I assume you're talking about the email report? The category titles are above the "Selected Behaviors" section. Do you mean the "Question Responses" section?
Looks like it's a similar story with the website (the /checkin/view page). The Behaviors list has the categories and Questions don't.
[Screen Shot 2021-04-05 at 8 09 15 PM]https://user-images.githubusercontent.com/220260/113653503-cdd58180-964a-11eb-859f-575be9ca16e5.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/CorWatts/fasterscale/issues/194#issuecomment-813790299, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATRGN2ESGGEU7OI2GHCARD3THJ32PANCNFSM42MFKGTA.

Thanks Brandon, that makes sense. That's a very reasonable request!
I'll look into adding this additional text to both the site and the email report. I'll leave this issue open as I do that.

Hey Brandon, I've added the category name to both the website and the email report and deployed the update. I hope that helps. Please let me know what you think!

Hey Corey,
The last two times that I’ve tried to use the FASTER scale check in, the results have been mixed up. Can you check that for me?
From the attached screenshot: I chose “roving eyes / lustful thoughts” for Forgetting Priorities (which shows correctly here), but then what I’ve typed below it is my description from Ticked Off’s “overreacting.” The long paragraphs (answers to the questions) are in the wrong places.
Thanks,
Brandon
From: Corey Watts @.>
Reply-To: CorWatts/fasterscale @.>
Date: Thursday, April 15, 2021 at 09:12
To: CorWatts/fasterscale @.>
Cc: Brandon Pearce @.>, Author @.***>
Subject: Re: [CorWatts/fasterscale] Need category name in check-in report (#194)
Hey Brandon, I've added the category name to both the website and the email report and deployed the update. I hope that helps. Please let me know what you think!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/CorWatts/fasterscale/issues/194#issuecomment-820080873, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATRGN2CM42ABJW7FG3J7TNLTIZRR7ANCNFSM42MFKGTA.

Hey Brandon, I've tried but have been unable to reproduce this. Also I don't think your screenshots came through. If you could re-send those I'd appreciate it.
To clarify -- you see this issue in the /checkin/view page in your browser, right? Not the emailed report.

Yep, that’s the check in/view page, I haven’t checked the emailed report. If they are not mixed up, I can just use them instead for the time being. You sure my screenshot didn’t send? Looks like they sent through on my end.
Brandon
Brandon P

From: Corey Watts @.>
Sent: Tuesday, September 7, 2021 1:36:38 AM
To: CorWatts/fasterscale @.>
Cc: brandogamus @.>; Author @.>
Subject: Re: [CorWatts/fasterscale] Need category name in check-in report (#194)
Reopened #194https://github.com/CorWatts/fasterscale/issues/194.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/CorWatts/fasterscale/issues/194#event-5262514217, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATRGN2A5NHBWZ6V4WP6LQOTUAUQ5NANCNFSM42MFKGTA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Just a quick -- and very belated -- update. This is indeed a bug though we already knew that :)
I've dug into this bug several times but have been unable to identify and fix the primary cause. Unfortunately it's difficult for me to arrange significant blocks of time to devote to programming/debugging. I'll continue to spend time looking into this. I know it's an inconvenient and noticeable issue.

Hey @brandogamus I wanted to let you know I've finally fixed this issue. Past check-ins won't be affected (and will still have an incorrect question answer <-> behavior association) but new check-ins will be correct now.

Thanks Corey! Keep up the great work.
Brandon

On Sep 10, 2023, at 3:52 PM, Corey Watts @.***> wrote:
Hey @brandogamus https://github.com/brandogamus I wanted to let you know I've finally fixed this issue. Past check-ins won't be affected (and will still have an incorrect question answer <-> behavior association) but new check-ins will be correct now.
—
Reply to this email directly, view it on GitHub https://github.com/CorWatts/fasterscale/issues/194#issuecomment-1712933976, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATRGN2FEYX5Q4IGINCRAMRDXZYSABANCNFSM42MFKGTA.
You are receiving this because you were mentioned.


DevTools: Minor fixes, expression playground feature: 'vis alle steg i evalueringen'

Description
In preparation for todays Altinn Kaffe:

Fixing component highlighter z-index so that is stays underneath the devtools, and making sure the Select component stays above it
Making sure errors in expression playground are not JSON encoded
Adding a feature to the expression playground to show all steps/function calls when evaluating expressions (very useful when you have deep expressions)

Sneaking in a new feature right after this was reviewed.. (Sorry!) Adding expression result history (with up to 10 items in the history/log). This allows you to compare expression evaluations with earlier runs to easily spot the difference.

https://github.com/Altinn/app-frontend-react/assets/700139/70f19502-74d6-48d3-b353-7f0e5252a7cc
Related Issue(s)

closes #{issue number}

Verification/QA

Manual functionality testing

[x] I have tested these changes manually
[ ] Creator of the original issue (or service owner) has been contacted for manual testing (or will be contacted when released in alpha)
[ ] No testing done/necessary

Automated tests

[ ] Unit test(s) have been added/updated
[ ] Cypress E2E test(s) have been added/updated
[x] No automatic tests are needed here (no functional changes/additions)
[ ] I want someone to help me make some tests

UU/WCAG (follow these guidelines until we have our own)

[ ] I have tested with a screen reader/keyboard navigation/automated wcag validator
[x] No testing done/necessary (no DOM/visual changes)
[ ] I want someone to help me perform accessibility testing

User documentation @ altinn-studio-docs

[ ] Has been added/updated

[x] No functionality has been changed/added, so no documentation is needed
[ ] I will do that later/have created an issue

Changes/additions to component properties

[ ] Changes are reflected in both src/layout/layout.d.ts and layout.schema.v1.json, and these are all backwards-compatible
[x] No changes made

Support in Altinn Studio

[ ] Issue(s) created for support in Studio

[x] This change/feature does not require any changes to Altinn Studio

Sprint board

[ ] The original issue (or this PR itself) has been added to the Team Apps project and to the current sprint board
[ ] I don't have permissions to do that, please help me out

Labels

[x] I have added a kind/* label to this PR for proper release notes grouping
[ ] I don't have permissions to add labels, please help me out

Whoops, sorry @bjosttveit! I added another feature (history/log over the last 10 evaluations). See the video above.

Whoops, sorry @bjosttveit! I added another feature (history/log over the last 10 evaluations). See the video above.

Dayum very nice


Mpt2test memory state support

This PR adds support for replicating the memory state of an original benchmark in a microbenchmark. To do so, it uses a new, slightly different, assembly wrapper which organizes data and code into sections. These are referenced by an automatically generated linker script, indicating the actual addresses into which this data/code is to be located.
@rbertran I tried to apply the feedback you've given me over time, but I might've forgot some. If that is the case, just let me know and I'll try implementing it next week ;)

@ArnauBigas I did some minor updates to merged the branch with the latest master branch and fix the CI setup.
Then, I realized that the functionality implemented in mp_mpt2test are very similar to the one implemented in the mp_mpt2elf . The first has been tested on your side on a RISCV platform, whereas the second has been tested on POWER and Z platforms.
The solution to avoid replicating similar code would be to cleanup/refactor/merge the functionality so that the same tool is valid across the three platforms but before doing further changes, I wanted to check with you to avoid "breaking" your current RISCV setup.
Ideally, I'd want to proceed as following: 1st, I'll integrate the your contributions to the mp_mpt2elf, 2nd: we validate that it works for all the tests (i.e. not new regressions on your tests or my tests) and finally, I'd remove the mp_mpt2test one.
Let me know, and I'll work accordingly.

Sorry, I had completely missed your last message. I see what you mean by the two tools being similar, please go ahead with the merge, I will do whatever testing is necessary on my side.
Speaking of which, I have finally ported all the tools necessary on our side to begin testing this code on Power. Since you open sourced the power backend for microprobe (much appreciated!), I can proceed with the validation. I don't expect to need to change the code in this PR. If I do have to change something, I will try to keep the changes in a separate branch (and tell you beforehand) so that I don't interfere with your work.

@ArnauBigas , I've integrated the RISCV functionality of mp_mpt2test into mp_mpt2elf tool. The following command:
mp_mpt2elf.py -T riscv_v22-riscv_generic-riscv64_linux_gcc -t <input_mpt_file>  -O <output.s> --raw-bin --reset --compiler <your_compiler>
should create ELF binaries that can be run in linux out of the mpt files. One change to take into account is that I've added the Program Counter (PC) register (which is user-visible) to the RISCV target definition. As a result, the PC register value should be also part of the Microprobe state file accompanying the mpt file. For consistency, this will require that other tools (e.g. Chopstix) to also dump that register in the mpt/mps files generated (not a big deal I think, since that value is already provided in the default_code_address).
Please give a try at this branch whenever you have some time to make sure your still maintain the functionality you have before with the mpt2test tool. Once you confirm, I'll remove that tool, and remove some other unused classes.

That looks great! Right now I'm a bit busy, but hopefully I'll be able to test this by next week.
Thanks!


Test restricted workspace settings

Ref #120860

[ ] windows @joaomoreno
[ ] mac @lramos15
[x] linux @deepak1556

Complexity: 5
Create Issue

Note: Use security.workspace.trust.enabled setting to enable workspace trust feature.
Test defining restricted workspace settings

Write a simple extension that defines a configuration in its package.json and reads its value when a command is executed
Eg:

"capabilities": {
		"untrustedWorkspaces": {
			"supported": "limited",
			"restrictedConfigurations": [
				"testExtension.restricted"
			]
		}
	},
	"contributes": {
		"configuration": {
			"title": "test",
			"properties": {
				"testExtension.restricted": {
					"type": "string",
					"scope": "resource",
					"default": "defaultValue"
				}
			}
		}
        }

export function activate(context: vscode.ExtensionContext) {
	vscode.commands.registerCommand('testExtension.helloWorld', (arg) => {
		vscode.window.showInformationMessage(vscode.workspace.getConfiguration().get('testExtension.restricted') || '');
	});
}

Validate the documentation for restrictedConfigurations

Run this extension in a trusted workspace.

Open workspace settings and update the value of the setting testExtension.restricted
Make sure testExtension.helloWorld command prompts the workspace value
Make sure vscode.workspace.getConfiguration().inspect('testExtension.restricted') has workspace & workspace folder value

Run this extension in an untrusted workspace (Use same workspace and change it to untrusted - by opening the workspace trust editor and removing the folder from trusted paths)

Make sure testExtension.helloWorld command does not prompts the workspace value (prompts either default value or user value if defined in user settings)
Make sure vscode.workspace.getConfiguration().inspect('testExtension.restricted') does not has workspace & workspace folder value
Run this extension in a multi-root workspace that includes this folder and validate all above 2 points are applied. In addition

Test restricted workspace settings UI in Untrusted workpsace

Test workspace trust editor shows a link with number of workspace settings which are not applied
Clicking on this link opens settings UI filtered with restricted settings in workspace settings
Make sure you cannot edit them
Validate the information shown makes sense and helpful
Clear the filter in settings search box. Make sure those restricted settings which are modified in workspace settings are shown on top under Workspace Trust category
Make sure applying the filter @tag:requireTrustedWorkspace  shows all list of restricted settings requiring workspace trust.
Open workspace settings.json file and make sure a warning is shown for the restricted setting if modified in the file. You can also find a light bulb (quick fix) that provides an action to open workspace trust editor
Make sure in workspace settings.json file you do not get IntelliSense for restricted settings
Validate all above points are applied in a multi-root workspace that includes this untrusted folder

vscode.workspace.getConfiguration().inspect('testExtension.restricted') provided undefined as workspaceFolderValue. Had to inspect the value per folder to verify, is that the intended way to do it ?
let folders = vscode.workspace.workspaceFolders;
folders.forEach(folder => {
   vscode.workspace.getConfiguration('testExtension', folder.uri).inspect('restricted'); // workspaceFolderValue is defined here
});

Yes, restricted setting value shall be undefined for each workspace folder if workspace is not trusted even if value is defined in the workspace folder.


CPU and GPU producing different results in some cases

CPU and GPU builds are sometimes producing meaningfully different results. This has so far been observed for

Immersed boundary method, Karman vortex street (via @anshgupta1234)
Cases with body forces (via @wilfonba), including

Falling droplet
Rayleigh--Taylor instability

Of these three cases, two involve physical instability, so of the three, it seems that the falling droplet cases are the easiest to analyze.
Some previous results noted that -O2 (instead of -O3) builds on GPU matched CPU results, but this does not seem to be universally true, as noted for the IBM case via @anshgupta1234.
It is not clear to me where the difference arises, though the reconstruction procedure and Riemann solve are the first most obvious places to look.

@wilfonba, is there a example
case that can be used to test this on your fork ?

@anandrdbz I just made a push with new two example cases, 2D_rayleigh_taylor and 2D_rising_bubble

@wilfonba, is there a example case that can be used to test this on your fork ?

FYI if you look at @wilfonba's most recent slides you'll see that GCC and NVHPC give different results even on CPU, and NVHPC gives different results for different optimization levels (none matching the GCC result).

@sbryngelson , but I presume this difference is only present in the body-force problems and not the regular cases like shock droplet or bubble screen ?

@anandrdbz Unsure at this point. The problems that made this issue apparent were body-force and immersed boundary problems, but I haven't looked into if other features have similar issues.

@anandrdbz I just made a push with new two example cases, 2D_rayleigh_taylor and 2D_rising_bubble

Okay, I guess this is the STRevert branch right ? Also if other cases had this issue, most likely it would fail the test suite

Yeah, it's the STRevert branch. It might fail the test suite if other cases were a problem, but the test suite only runs 50 time-steps which may not be enough for differences that are significant enough to fail tests to happen. I'll look into running the test suite for more time-steps and see what I find.

Okay sounds good, I'll take a look at the rising bubble problem tonight

Update: Different optimization levels give different results for GCC compilers on CPUs, NVHPC compilers on GPUs, and NVHPC compilers on CPUs. NVHPC compilers on GPUs with the same optimization level yield the same results when using different compiler versions on the same hardware and when using the same compilers on different hardware when using GPUs.

The immersed boundary problem at least could potentially be related to the bug I observed with Cray compilers (round-off being significant)

Changing this from bug to "invalid". I think the real reason is just floating point problems. This happens across the board (different CPUs and compilers have this as well). The real issue is identifying how to avoid this when designing cases and writing code. Leaving this open for further discussion of the particular cases that 'trigger' this so we can find the root causes so we can avoid them later.

No activity on this. Closing.


Use golang 1.12 to build in dockerfile

as title

Codecov Report

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

@@            Coverage Diff             @@
##           master    #6285      +/-   ##
==========================================
- Coverage   38.89%   38.88%   -0.02%
==========================================
  Files         359      359
  Lines       50993    50993
==========================================
- Hits        19835    19829       -6
- Misses      28288    28295       +7
+ Partials     2870     2869       -1

Impacted Files
Coverage Δ

models/unit.go
0% <0%> (-14.29%)
:arrow_down:

routers/repo/view.go
41.08% <0%> (-1%)
:arrow_down:

Continue to review full report at Codecov.

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


Redefined signatures are not checked

Example:
class Foo
	fun foo(bar: Int, baz: Bool): String is abstract
end

class Bar
	super Foo

	redef fun foo(bar: Int, baz: Bool) do # forgotten return type?
            return ""
        end
end

I think that the redef should be raising an error or at least a warning about the return type.

It is not a bug, it is a feature! Types of the parameter and return types are inherited independently.
Try to redefine with a different return type, or remove the return to see it.
The idea was to allow the redefinition of the return type (that is allowed in a covariant way) while inhering the parameter type (because they are invariant so superfluous to repeat).
I need a seconder or something if you want a change in the feature. :)

Ok, I understand and it makes sense. I close the issue.


Getting past cloudflare?

Having some trouble getting past cloudflare. Doing some research on how to bypass it (although it looks complicated). Anyone had some luck?
So far I tried using regular chrome instead of chromium, but that didn't work out (using channel='chrome'). I'm logged in successfully on my regular chrome.

Update: Current workaround is switching to Firefox instead of chromium. I am leaving this open unless (@danielgross wants to close it) in case people have found other workarounds.
Example:
# In server.py
BROWSER = PLAY.firefox.launch_persistent_context(
    user_data_dir=PROFILE_DIR,
    headless=False,
    java_script_enabled=True,
)

Update: Current workaround is switching to Firefox instead of chromium. I am leaving this open unless (@danielgross wants to close it) in case people have found other workarounds.
Example:
# In server.py
BROWSER = PLAY.firefox.launch_persistent_context(
    user_data_dir=PROFILE_DIR,
    headless=False,
    java_script_enabled=True,
)

Can you pr it?

I was able to get it working with firefox, but only thing is im having an issue geting it sent to my whatsapp chat .  Something about send button timing out


Supervisor Meeting, Scheduled, Wednesday, Jan 24th, 5:00, Teams

Topics

[x] discuss about future progress direction
[x] update progress: 1. working on UI enhancement 2. unit testing 3. Connection with the summer Tai Chi project.

Attendance

[x] @qstommyshu
[x] @yex33
[x] @marischan888
[x] @jiaoa3
[x] @KehaoHuang

Todo
-[ ] 2d HPE
-[ ] 3d HPE
-[ ] Semantic Segmentation, try to draw something over the person to show the effect
-[ ] ways to add titles
-[ ] different rooms with different annotations


PROD ISSUE - Parser is incorrectly categorizing value as geolocation unit

[ ] Feature
[x] Bug

Description
Parsing a soql query that contains 'MI' or 'KM' as a value is incorrectly being categorized as a geolocation unit instead of a string literal.
Steps -

Parse this query SELECT State_Abbr_c FROM Contact WHERE State_Abbr_c = 'MI'
The MI token is being categorized as a geolocation unit instead of a string literal which is throwing an error.

@divijklenty - Thank you for reporting this issue ❤  and I am VERY surprised this was not identified sooner as this library has been used millions of times in a production application to parse user generated queries and this never creeped up as far as I know.
Version 4.4.1 has been released to resolved this issue.


removed require "pg_search/migration/associated_against_generator"

removed require "pg_search/migration/associated_against_generator" as its deleted from v2.0.0

Duplicate of #342.
Please try v2.0.1 to pick up the fix. Thanks!