Draft Requirements & Mockups

From the brief create draft requirements and mock ups in wiki

Balsamiq framework is being used for creating mock-ups.

The base for mock-up preparations has been shared. Multiple user login has been provided for group work.

Mock up study started for recommendation, space and profile/space management

I am closing this one since we submitted our requirements to moodle.


watch timeout

This isn't really an issue, but I was hoping to see thoughts on the best way of addressing this.  Eventually k8s will timout the watch and close it.  Currently it seems this will cause the program to exit.  What's the right way to have it so once the timeout happens, this can detect the close, and just re-establish a watch, so that way there is really a continual watch that could run for weeks?

I have a similar issue where in im watching a object forever, but the cluster times out the oldest connection when required which eventually is my stream watcher.
I'm tackling this by running the for loop inside another loop continuously.
however the problem with this is, it just replays all the stream (since the start of cluster) back in to the watcher object

@genericgithubuser @kartik-tavisca  which version of the code (Go, Java, etc) are you asking about. I did think the Go client timed out a watcher since the watcher periodically asks for watched resources.  But I may be wrong.  Let me know exactly in the location of the code this is about.


unable to install pyenv on windows 10 (pip install pyenv )

Collecting pyenv
Using cached pyenv-20150113.1.tar.gz
Building wheels for collected packages: pyenv
Running setup.py bdist_wheel for pyenv ... error
Complete output from command d:\python\python.exe -u -c "import setuptools, tokenize;file='c:\users\user\appdata\local\temp\pip-build-6ldgff\pyenv\setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" bdist_wheel -d c:\users\user\appdata\local\temp\tmprauu_6pip-wheel- --python-tag cp27:
running bdist_wheel
running build
installing to build\bdist.win32\wheel
running install
error: [Error 2] The system cannot find the file specified

Failed building wheel for pyenv
Running setup.py clean for pyenv
Failed to build pyenv
Installing collected packages: pyenv
Running setup.py install for pyenv ... error
Complete output from command d:\python\python.exe -u -c "import setuptools, tokenize;file='c:\users\user\appdata\local\temp\pip-build-6ldgff\pyenv\setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record c:\users\user\appdata\local\temp\pip-wg9dun-record\install-record.txt --single-version-externally-managed --compile:
usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: -c --help [cmd1 cmd2 ...]
or: -c --help-commands
or: -c cmd --help
error: option --single-version-externally-managed not recognized

----------------------------------------

Command "d:\python\python.exe -u -c "import setuptools, tokenize;file='c:\users\user\appdata\local\temp\pip-build-6ldgff\pyenv\setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record c:\users\user\appdata\local\temp\pip-wg9dun-record\install-record.txt --single-version-externally-managed --compile" failed with error code 1 in c:\users\user\appdata\local\temp\pip-build-6ldgff\pyenv\

Hi, sorry but pyenv ist not supported on Windows and likely isn't if nobody takes that in their own hands. See: https://github.com/yyuu/pyenv/issues/62.

I guess pyenv could be able to work on bash on Windows. I've never tried, though.
Anyway it seems the error is occurring inside setuptools or pip, not in pyenv's code.

Anyway it seems the error is occurring inside setuptools or pip, not in pyenv's code.

That's the other thing ... I will definitely have to carve out some time to make it work consistently with the pip installer (see: https://github.com/yyuu/pyenv-installer/issues/25) or admit defeat and propse complete removal of the installer (but then we have a project on pypi that is not pip installable - bad).

pyenv works excellent under windows subsystem for linux, but You need windows10anniversary edition or newer.

If you use a python in one of these environments, such as CygWin and especially WSL, you will have limited integration with other tools that require python.  The recommendation out there, is to use conda tool to manage versions.  I'm still testing this out, for compatibility with tools like node-gyp that many Node NPM packages use.

@nikesh363 See pyenv-win by kirankotari for a Windows port.


Rename symbol problem with TypeScript

There are problems renaming of symbols in base/derived objects.
In the example below:

Renaming foo in "basevar" does not rename foo in "derivedvar".
Renaming foo in "base" does not rename foo in "derivedvar"
Renaming foo in "derivedvar" does not rename foo in "base" and "basevar". (webstorm offers an option to rename base symbols here)

const basevar : base = {
    foo:42
};

const derivedvar : derived = {
    foo:42
}

interface base {
    foo:number;
}

interface derived extends base {
    foo:number;
}

This issue was moved to Microsoft/TypeScript#18866


Upgrade dependencies to match quality checklist

Resolves #46

Nice work Angie! I see a lot of improvements over the old code. I left some minor comments about grammar and code cleanup. I do have a concern though:
Rails 6 brought some big changes over its predecessor, one of them is the inclusion of webpack to serve front-end assets which is now the default JavaScript compiler. In order to get the new Rails 6 structure we need to add a NodeJS engine to provide the webpack feature which will be consumed through Webpacker. The easiest way to add this is to create a new project from scratch (or use the sample template) then copy all the content to the new project and move the contents from the public directory to the new assets path.
Other minor stuff:

This image should be removed.

Hey @mrcrow85 , about your comment of the NodeJS engine, thanks for pointing this out. I'm going to talk about this with Dominik and check if it is possible to do this in this phase.


--extensions-dir option to code cli ignored in 1.74.0

Type: Bug
Steps to reproduce

Make sure you have an extension installed in VSCode (any extension)
Run mkdir foo to make an empty directory
Run mkdir bar to make an empty directory
Run code --extensions-dir foo bar to open directory bar in VSCode using the empty directory foo as the extensions dir
Run "Extensions: Show Enabled Extensions" command from the command palette in the newly opened workspace

Expected behaviour
There should be no extensions in the list, because code was called with an empty extensions dir
Actual behaviour
It shows the full list of extensions from the default extension dir.   May I know if you have enabled profiles in stable?

Strange.  I do not have profiles enabled; here are my settings in case helpful https://github.com/pokey/dotfiles/blob/d9103190ac6bc32fcb1a5b875c242b3a0feeebf6/vscode/settings.json

By any chance, you have extensions.json file in the same directory as settings.json ?

Hey, I'm having the same issue here. On 1.73.1 it worked, on 1.74.1 it feels like --extensions-dir is ignored.
This command returns an empty list for 1.74.1, and on 1.73.1 it lists the extensions:
$ code --extensions-dir /usr/share/vscode-extensions --list-extensions

Before, vscode was used to install the extensions to this directory, via:
$ code --extensions-dir /usr/share/vscode-extensions --install-extension <ext>

By any chance, you have extensions.json file in the same directory as settings.json ?

Nope

Having same issue (1.74.1). Discovered on both

Linux debian 5.10.0
Linux ubuntu 22.10 (Kinetic Kudu)

I've created a minimal repo to demonstrate the issue in my case of extension development.
This repo consists of the default boilerplate for a vscode extension generated using these instructions with the following changes to specify the extensions dir.
I would expect that when I startup the extension development host using the shortcut fn+f5; that the host would not contain any extensions due to the fact that I have set the --extensions-dir to the empty directory at ./vscode-test/extensions in the launch.json config. Instead all of my personal extensions appear in the development environment. Furthermore; if I manually install additional extensions to ./vscode-test/extensions/ they do not appear in the extensions development host.

@pokey @rtpt-alexanderneumann Can you please try following steps and see if it fixes for you?

Open the extensions installation folder
Delete the files extensions.json and .init-default-profile-extensions
Restart VS Code

@jeswr I think you are having a different issue related to debug launches. Please file a separate issue.

Didn't seem to help: I deleted both files and am still seeing the same issue

@pokey Can you please re-describe the problem you are seeing and what steps you are following?

I'm sorry but I'm not sure how to make the description from the top of the issue clearer.  Is one of those 5 steps in particular not clear?

It does for me. I tried following:
code --extensions-dir ~/work/testing/setup/extensions-dir --verbose
And I can see code launched with different extensions dir as shown in the main log

Can you please try the same and share the log?

I'm here sorry I got tied up with a few other things I am NEW to this and it is a learning process trying to catch all the fine line details in between!  I am currently branching into my own part of merchandising so this part is new to me!

@sandy081 Removing both files (.init-default-profile-extensions and extensions.json) fixes it. VSCode creates both files anew.
I've diffed the content of extensions.json and I can see that the paths contained for each extension are different. Before (non-working), the paths were incorrect (pointing to a temporary directory that I used to install the extensions). After, the paths are correct.
In previous versions of VSCode, there was no extensions.json in that directory. In newer versions, VSCode insists on writing one, and fails if it cannot do that (as it is for our directory):
$ code --extensions-dir /usr/share/vscode-extensions --list-extensions
Unable to write file '/usr/share/vscode-extensions/extensions.json' (NoPermissions (FileSystemError): Error: EACCES: permission denied, open '/usr/share/vscode-extensions/extensions.json')

Our solution (for now) is to make sure that the paths in extensions.json are correct.
Reproducible example:
$ mkdir /tmp/extdir

$ code --extensions-dir /tmp/extdir --install-extension golang.go
[...]
Extension 'golang.go' v0.37.0 was successfully installed.

$ code --extensions-dir /tmp/extdir --list-extensions
golang.go

$ mv /tmp/extdir /tmp/other-extdir

$ code --extensions-dir /tmp/other-extdir --list-extensions
[empty]

$ jq . /tmp/other-extdir/extensions.json
[
  {
    "identifier": {
      "id": "golang.go",
      "uuid": "d6f6cfea-4b6f-41f4-b571-6ad2ab7918da"
    },
    "version": "0.37.0",
    "location": {
      "$mid": 1,
      "fsPath": "/tmp/extdir/golang.go-0.37.0",
      "path": "/tmp/extdir/golang.go-0.37.0",
      "scheme": "file"
    },
    "metadata": {
      "id": "d6f6cfea-4b6f-41f4-b571-6ad2ab7918da",
      "publisherId": "dbf6ae0a-da75-4167-ac8b-75b4512f2153",
      "publisherDisplayName": "Go Team at Google",
      "targetPlatform": "undefined",
      "isApplicationScoped": false,
      "updated": false,
      "isPreReleaseVersion": false,
      "installedTimestamp":<PHONE_NUMBER>536,
      "preRelease": false
    }
  }
]

# fix paths
$ sed -i 's,/tmp/extdir,/tmp/other-extdir,g' /tmp/other-extdir/extensions.json

# works again:
$ code --extensions-dir /tmp/other-extdir --list-extensions
golang.go

# remove the files and make the dir r/o
$ rm /tmp/other-extdir/extensions.json /tmp/other-extdir/.init-default-profile-extensions
$ chmod u-w /tmp/other-extdir

$ code --extensions-dir /tmp/other-extdir --list-extensions
Unable to write file '/tmp/other-extdir/extensions.json' (NoPermissions (FileSystemError): Error: EACCES: permission denied, open '/tmp/other-extdir/extensions.json')

Can you please try the same and share the log?

➜ code --extensions-dir .vscode-sandbox/extensions --verbose ~/vscode-test
[main 2022-12-21T12:32:44.838Z] [File Watcher (node.js)] Request to start watching: /Users/pokey/Library/Application Support/Code/User (excludes: <none>, includes: <all>),/Users/pokey/Library/Application Support/Code/User/settings.json (excludes: <none>, includes: <all>)
[main 2022-12-21T12:32:44.855Z] Sending env to running instance...
[main 2022-12-21T12:32:44.858Z] [File Watcher (node.js)] correcting a path to watch that seems to be a symbolic link or wrong casing (original: /Users/pokey/Library/Application Support/Code/User/settings.json, real: /Users/pokey/pokey-home-files/vscode/settings.json)
[main 2022-12-21T12:32:44.861Z] [File Watcher (node.js)] Started watching: '/Users/pokey/pokey-home-files/vscode/settings.json'
[main 2022-12-21T12:32:44.863Z] [File Watcher (node.js)] Started watching: '/Users/pokey/Library/Application Support/Code/User'
[main 2022-12-21T12:32:44.907Z] Sent env to running instance. Terminating...
[main 2022-12-21T12:32:44.907Z] Lifecycle#kill()
[main 2022-12-21T12:32:44.907Z] Lifecycle#onWillShutdown.fire()

Note that this was after removing extensions.json and .init-default-profile-extensions from .vscode-sandbox/extensions (the extensions dir)

@pokey Do you have vscode running while you execute this command?
code --extensions-dir .vscode-sandbox/extensions --verbose ~/vscode-test

Yes I run it from the integrated terminal.  The same issue also occurs when I run VSCode from a launch config (the issue described in https://github.com/microsoft/vscode/issues/169734)

OK. As mentioned in the issue #169734, this was working by chance before. Extensions UI and Running Extensions are completely disconnected because both of them are using two different extensions directories. For this use case, I would recommend to start using our new Profiles feature so that it works flawlessly unlike before  -https://code.visualstudio.com/updates/v1_71#_settings-profiles

I can confirm that settings profiles solve the issue for me.  Thanks!


signInWithCustomToken: type 'Null' is not a subtype of type 'String' in type cast

[ERROR:flutter/lib/ui/ui_dart_state.cc(209)] Unhandled Exception: type 'Null' is not a subtype of type 'String' in type cast
#0      _$_$CustomTokenSignInResponseFromJson (package:firebase_auth_rest/src/models/signin_response.g.dart:106:30)
#1      new _$CustomTokenSignInResponse.fromJson (package:firebase_auth_rest/src/models/signin_response.freezed.dart:1703:7)
#2      RestApi.signInWithCustomToken (package:firebase_auth_rest/src/rest_api.dart:99:33)
<asynchronous suspension>
#3      FirebaseAuth.signInWithCustomToken (package:firebase_auth_rest/src/firebase_auth.dart:209:9)
<asynchronous suspension>

Which is here:
_$CustomTokenSignInResponse _$_$CustomTokenSignInResponseFromJson(
    Map<String, dynamic> json) {
  return _$CustomTokenSignInResponse(
    idToken: json['idToken'] as String,
    refreshToken: json['refreshToken'] as String,
    expiresIn: json['expiresIn'] as String,
    localId: json['localId'] as String, // <<<< NPE
  );
}

In the code CustomTokenSignInResponse declares localId, however looking at the doc it should not be there:
https://firebase.google.com/docs/reference/rest/auth#section-verify-custom-token

I think this is because I falsely assumed it exists on any auth response. I will have to adjust the models. I will try to do so without breaking compability

Should be fixed with version 2.0.2. Once the pipelines have run successfully, it should be available within a few hours


Update expressroute-troubleshooting-network-performance.md

typo .. Rotue .. Route

Thanks, @annadeaz!


Horizontal scrollbars appear when viewing presentations

Tested in Firefox/Iceweasel 38.0.1

Neither horizontal nor vertical scrollbars should be appearing. I'll look into it.

The example was running an old version of the code.Recompiled and repushed; the issue should be gone :)


Switch off KenBurns Effect

My Raspberry is lagging due to the KenBurns Effect. I am really bad in Java - is there an easy solution to get a simple image after image slideshow with no effect?

I managed to do so, thanks a lot for the support!


No Typescript type locations listed for the NodeJS version. Not included in the JavaScript client/server

While it lists type information broadly, there isn't any documentation on where to find TypeScript types for the V3 or V4 types (e.g., WebPubSubContext, WebPubSubConnection, etc.). Given that this is an official Microsoft product and given that there's been no statement that these types aren't coming, it's unlikely that we'll see the community provide type information either.

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

ID: 0c4c897d-50cd-34e9-c2e7-7ca235090b8c
Version Independent ID: 65d9edff-959a-e5d7-1164-947261bb592a
Content: Reference - Azure Web PubSub trigger and bindings for Azure Functions
Content Source: articles/azure-web-pubsub/reference-functions-bindings.md
Service: azure-web-pubsub
GitHub Login: @JialinXin
Microsoft Alias: jixin

@oadrian2
Thanks for your feedback! We will investigate and update as appropriate.

@oadrian2 We're still planning for this support. The V4 model is defined in Azure Functions and it's open source that welcome community contribute. https://github.com/Azure/azure-functions-nodejs-library/tree/v4.x

It looks like this has been resolved. Closing! #please-close


Sample Manifests for pattern Crossplane Argocd GitOps

Issue #, if available:
These manifests files are for a blog myself and @elamaran11  are working on it. It is about using Crossplane and ArgoCD in a Managment cluster to deploy/manage EKS Addons, K8s Manifests or Helm charts in Workload clusters.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@ajpaws Please add description to the PR about the purpose of the PR, what we are achieving with it.
Do we need a change in this repo specifically, for example, will it be useful to people who use EKS Blueprint terraform or other tooling ? If yes, please add to the PR description.
The PR has 18 files, do we need all of these samples in the repo?
I would also exercise caution about adding stuff into existing environments as those are used for demos by many and an unexpected deployment of additional manifest may cause a problem. We can discuss if needed.

@shapirov103 It is for a blog myself and @elamaran11 are working on it. We will make some changes to align with current structure and examples in this repo

@ajpaws Did you fix all the feedback?

@ajpaws Did you fix all the feedback?

yes

@ajpaws Did you fix all the feedback?

yes

Overall looks good. I had one question, plus I see some unresolved questions from Ela.
Let's add a section to the README file to describe team-spock and templates - link it back to the pattern.
I will merge then and we can move on to the functional validation of the pattern. Great work!

Not addressed, please add a section to the readme otherwise this repo gets workloads that won't be clear to anyone as far as how they are used.

Overall looks good. I had one question, plus I see some unresolved questions from Ela.
Let's add a section to the README file to describe team-spock and templates - link it back to the pattern.
I will merge then and we can move on to the functional validation of the pattern. Great work!

Not addressed, please add a section to the readme otherwise this repo gets workloads that won't be clear to anyone as far as how they are used.

added a commit to update the README with team description


Subscriptions and blocking next()

Currently subscriptions are blocking in the sync case. See here:
https://github.com/scs/substrate-api-client/blob/4d4f19810f607371cf84e5885f398ab483f5aec9/src/rpc/jsonrpsee_client/subscription.rs#L30-L31
Check whether it is possible to "break" this blocking by calling unsubscribe() and if yes also allow the user to use this to cancel calls to next() that are stuck.
See this previous discussion: https://github.com/scs/substrate-api-client/pull/635#discussion_r1277185031

With #692 this issue is now obsolete and can be closed


runguard/runguard: cannot start ` sh': Resource temporarily unavailable

Hello, when I try to run ' python3 testsubmit.py', I obtain 28 error messages like :
```/var/www/html/jobe/application/libraries/../../runguard/runguard: cannot start `                                                                                sh': Resource temporarily unavailable
I run it in a Lxc container in proxmox , et the container is 'ubuntu 18.04' type.

Thank's a lot,

I haven't installed jobe in an LXC container myself. But another user reports (see here) " was 100% unsuccessful when trying to install the Jobe Docker image within or parallel to the LXC-container that my Moodle instance is running in. It simply did not work either way I tried. Creating a separate LXC-machine for Jobe was done in less than 30 minutes and is working well."
Have you got a separate LXC container for Jobe?

I just successfully fired up Jobe in a privileged LXC container on a Linux host (Ubuntu 20.04; guest was Ubuntu 18.04). I'm guessing your problems relate to privileges within the container, but I've no idea how proxmox manages those. You're on your own there, I'm afraid.

Thank you for your answer!
Yes, I used a different container from container with moodle inside.
Thinking too that the problem related to privileges within the container, I tried to modify /etc/security/limits.conf, or /etc/security/limits.d/90-nproc.conf with "*               hard    nproc           unlimited" for example.
Nothing changed.
Finally, I installed a VM with ubuntu 18.04 server from iso image, et I followed your installation 's steps, and now  it works perfectly.
So, Proxmox+VM guest ubuntu 18.04 works for me.
Thank's a lot!
Best regards,


Fix grab-site and python3Packages.lmdb

Motivation for this change
This fixes:

python3Packages.lmdb

upgraded lmdb to fix a failing test with lmdb 0.9.28: https://github.com/jnwatson/py-lmdb/issues/278
removed the strange dependency on ludios_wpull, which was breaking the python38Packages.lmdb build

grab-site, which depends on python37Packages.lmdb

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

cc maintainers @copumpkin @jb55 @vcunat
I confirmed that grab-site now builds and runs on NixOS master.

The C part looks good to me; I'm not really familiar with the python package.

@ofborg build python3.pkgs.lmdb

Result of nixpkgs-review pr 120785 at 68756398 run on aarch64-linux 1

61 packages marked as broken and skipped:

gnome3.gnome-books
gnome3.gnome-documents
libsForQt512.baloo
libsForQt512.baloo-widgets
libsForQt512.discover
libsForQt512.dolphin
libsForQt512.dolphin-plugins
libsForQt512.dragon
libsForQt512.elisa
libsForQt512.gwenview
...

1 package failed to build:

pantheon.appcenter

48 packages skipped due to time constraints:

caffe
denemo
dero
gerbil
gerbil-unstable
glom
kdev-php
kdev-python
kdevelop-unwrapped
libmodsecurity
...

44 packages built successfully:

appstream
bookworm
evince (gnome3.evince)
gawkextlib.lmdb
gnome-feeds
gnome3.sushi
grab-site
haskellPackages.lmdb
haskellPackages.lmdb-high-level
haskellPackages.lmdb-simple
knot-dns
knot-resolver
libsForQt5.appstream-qt (libsForQt515.appstream-qt ,plasma5Packages.appstream-qt)
libsForQt5.baloo (libsForQt515.baloo ,plasma5Packages.baloo)
libsForQt5.baloo-widgets (libsForQt515.baloo-widgets ,plasma5Packages.baloo-widgets)
libsForQt5.dragon (libsForQt515.dragon ,plasma5Packages.dragon)
libsForQt5.kde-cli-tools (libsForQt515.kde-cli-tools ,plasma5Packages.kde-cli-tools)
libsForQt5.khotkeys (libsForQt515.khotkeys ,plasma5Packages.khotkeys)
libsForQt5.kmenuedit (libsForQt515.kmenuedit ,plasma5Packages.kmenuedit)
libsForQt5.krohnkite (libsForQt515.krohnkite ,plasma5Packages.krohnkite)
libsForQt5.kwin-dynamic-workspaces (libsForQt515.kwin-dynamic-workspaces ,plasma5Packages.kwin-dynamic-workspaces)
libsForQt5.kwin-tiling (libsForQt515.kwin-tiling ,plasma5Packages.kwin-tiling)
libsForQt5.parachute (libsForQt515.parachute ,plasma5Packages.parachute)
libsForQt5.plasma-browser-integration (libsForQt515.plasma-browser-integration ,plasma5Packages.plasma-browser-integration)
libsForQt5.plasma-disks (libsForQt515.plasma-disks ,plasma5Packages.plasma-disks)
libsForQt5.plasma-workspace (libsForQt515.plasma-workspace ,plasma5Packages.plasma-workspace)
libsForQt5.systemsettings (libsForQt515.systemsettings ,plasma5Packages.systemsettings)
libsForQt514.appstream-qt
libsForQt514.baloo
libsForQt514.baloo-widgets
lmdb
metadata-cleaner
meteo
pantheon.elementary-calculator
pantheon.elementary-camera
pantheon.elementary-code
pantheon.elementary-greeter
pantheon.elementary-terminal
pantheon.wingpanel-applications-menu
pantheon.wingpanel-with-indicators
python38Packages.lmdb
python39Packages.lmdb
setzer
snippetpixie

2 suggestions:

warning: missing-phase-hooks
checkPhase should probably contain runHook preCheck and runHook postCheck.
Near pkgs/development/libraries/lmdb/default.nix:28:3:
   |
28 |   checkPhase = "make test";
   |   ^

warning: missing-patch-comment
Please add a comment on the line above, explaining the purpose of this patch.
Near pkgs/development/libraries/lmdb/default.nix:15:15:
   |
15 |   patches = [ ./hardcoded-compiler.patch ];
   |               ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement.

On Mon, Apr 26, 2021 at 07:57:58PM +0000, Ivan Kozik wrote:

This makes no sense and yet was added in 65eccfad5d32328d12cf8b42d02560905a8c9bae
This was breaking the build of python3Packages.lmdb because ludios_wpull does not
build on 3.8, only 3.7

propogatedBuildInputs = [ ludios_wpull ];

weird, good catch. ACK.


New Info endpoint

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes #316
Type of change

New feature (non-breaking change which adds functionality)
Unit tests (no changes in the code)

Testing steps
$ curl localhost:8080/api/v1/info | jq .

{
  "info": {
    "BuildBranch": "info-endpoint",
    "BuildCommit": "a985007e982f6c82152e14c5436154525d176735",
    "BuildTime": "Fri 29 Oct 2021 04:27:26 PM CEST",
    "BuildVersion": "0.5",
    "UtilsVersion": "v1.21.2"
  },
  "status": "ok"
}

Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report

Merging #317 (da46251) into master (a0616c2) will decrease coverage by 0.80%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##           master     #317      +/-   ##
==========================================
- Coverage   73.39%   72.58%   -0.81%
==========================================
  Files          11       11
  Lines         560      580      +20
==========================================
+ Hits          411      421      +10
- Misses        126      134       +8
- Partials       23       25       +2

Impacted Files
Coverage Δ

server/handlers.go
41.37% <18.18%> (-5.43%)
:arrow_down:

content-service.go
42.42% <85.71%> (+2.42%)
:arrow_up:

server/endpoints.go
100.00% <100.00%> (ø)

server/server.go
100.00% <100.00%> (ø)

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 a0616c2...da46251. Read the comment docs.


Mrs/ci

This branche adds two files corresponding to a pipeline in YAML format into the hidden repository ".github/workflows/" :

ci_mac.yml (run CI on macOS 10.15.1: build node.gl)
ci_linux.yml (run CI on Ubuntu 18.04 with a Docker on Ubuntu 19.10: build node.gl and run tests without graphic context)

Every workflow is triggered at each Pull Request and for each Push on Master.
You also have to add the statut badge at the beggining on your README but the repo path is hardcoded inside it so I can't do it in this PR:
Please, follow this example :
[![Actions Status](https://github.com/mrobertseidowsky-gpsw/node.gl.ci/workflows/Continuous%20Integration%20Pipeline/badge.svg)](https://github.com/mrobertseidowsky-gpsw/node.gl.ci/actions?query=workflow%3AContinuous%20Integration%20Pipeline)
To block the merge of PR is ci_mac.yml and ci_linux.yml are failing, please follow: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks
I can show you my configuration if needed.
Example of workflow in fail statut on a PR (since I'm admin I can merge it even in fail case) :

Example of workflow in success statut on a PR :

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

Would you mind using "ci: add ..." as prefix? ".github/workflows" is a bit too much

@cboesch-gpsw  done, more concise indeed

@cboesch-gpsw  you can see on my draft repo the results on the two scripts I suggest in this PR:
Linux:

https://github.com/mrobertseidowsky-gpsw/node.gl.ci/runs/423524548?check_suite_focus=true  => 2min37

Mac:

https://github.com/mrobertseidowsky-gpsw/node.gl.ci/runs/423524546?check_suite_focus=true => 7min47

rebase WIP


React visio 191

Q
A

Bug fix?
no

New feature?
no

New sample?
no

Related issues?

What's in this Pull Request?
Update react-visio sample to SPFx 1.9.1.
Removed fix for IE as no longer seems to be an issue.

Hi Joel,
Thanks for the updates to this sample! Keep up the good work. :)
Laura

Hi @joelfmrodrigues ,
I don't think this web part has yet been showcased in one of our community calls. Would you be up for doing a 10-15 min demo about this in one of our upcoming community calls?
We still have room in the call on the 24th (Thursday next week) for example. Would you be up for that?
Cheers,
Laura

Hi @LauraKokkarinen
Thanks for the invite, but I have already showcased that web part about a year ago after it was added to the repository.
Cheers,
Joel


Bug in match related to variable binding

See factorial definition in nat.rkt test.

Think this is the same bug as #64. Should just throw out match and do it properly.

wontfix until #55


Setup brew determine-test-runners for macOS 15 x86_64

Verification

[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

Provide a detailed description of the proposed feature
We're ready to enable macOS 15 x86_64 for PRs but the setup is a little more complex.
We need brew determine-test-runners to add macOS 15 x86_64 to the matrix if any of the following are true:

The package is pkg-config or pkgconf
formula.class.pour_bottle_only_if == :clt_installed
Any recursive dependent of the tested formula satisfies dependent_formula.class.pour_bottle_only_if == :clt_installed
--all-supported is passed

The last condition may require making --eval-all mandatory.
What is the motivation for the feature?
In order to have proper testing of macOS 15 x86_64 and not require manual post-merge building.
It is also blocking https://github.com/Homebrew/homebrew-core/pull/190981.
How will the feature be relevant to at least 90% of Homebrew users?
They will get upgraded to compatible bottles rather than temporarily get incompatible bottles that break their workflow.
What alternatives to the feature have been considered?
None

Any recursive dependent of the tested formula satisfies dependent_formula.class.pour_bottle_only_if == :clt_installed

This currently includes all Python dependents, no? Though I suppose we want to and should fix that.

Any recursive dependent of the tested formula satisfies dependent_formula.class.pour_bottle_only_if == :clt_installed

This currently includes all Python dependents, no? Though I suppose we want to and should fix that.

All Python dependencies.
<EMAIL_ADDRESS>ended up being a dependency of LLVM anyway so we have already built that depedency tree.

Any recursive dependent of the tested formula satisfies dependent_formula.class.pour_bottle_only_if == :clt_installed

This currently includes all Python dependents, no? Though I suppose we want to and should fix that.

All Python dependencies.

So, should the original post instead say

Any recursive dependency of the tested formula satisfies dependent_formula.class.pour_bottle_only_if == :clt_installed

? (Or am I confused?)

If you are building mpdecimal, a Python dependency, you need to check dependents to find Python.
(btw I've also added a note about --all-supported to the original issue as I forgot about that case)

Alternatively I guess if it's simpler: you could find all formula matching pour_bottle_only_if, calculate their dependency trees and union into one and then check for intersections between that list and the tested formulae.

If you are building e.g. mpdecimal, a Python dependency, you need to check dependents to find Python.

Ah, gotcha, thanks for the explanation.

What is this for/to do?

Cache workflow + brew doctor workflow here.

Could this be non-recursive?

No, we build full dependency trees. For the affected formulae this isn't that big.

Feels like adding a new DSL for this might be nicer and a bit less involved?

The DSL is effectively there for most cases except the pkg-config exception. We just need it to cover the full dep tree.

Any recursive dependent of the tested formula satisfies dependent_formula.class.pour_bottle_only_if == :clt_installed

This is pretty straightforward to do now with TestRunnerFormula#dependents.
Though the implementation of that is really inefficient -- it walks Formula.all for each runner and tested formula. This is part of why it's really slow, but the slowness didn't matter as much previously (since it could run concurrently with formula builds).
Ideally it would construct the dependency once for each runner and then query that for each tested formula instead.

What is this for/to do?

Cache workflow + brew doctor workflow here.

Ok, gotcha.

For the affected formulae this isn't that big if we maybe flip it and check the dependency trees rather than constructing dependent trees.

This seems nicer.

The DSL is effectively there for most cases except the pkg-config exception. We just need it to cover the full dep tree.

I think it's kind of there but very unintuitive to folks without a deep understanding of Homebrew and/or macOS SDKs.
I think a new DSL with audits or cops to enforce them based on the cases we already know would be nice rather than an implied DSL like we have today.


Remove GNUC and XTENSA preprocessor switches

Supporting XTENSA (ESP32) has used __GNUC__ and __XTENSA__ preprocessor switches. These obscure the clarity of the code in main() because xtensa needs a task called main_loop(void*) instead.
The point of this issue is to try to remove the use of these compiler switches. Consider optional inclusion/exclusion of file(s) in the build systems.

Nobody is disturbed by this and I have grown to disregard the compiler switches. Close this issue with no activity performed.


Add FsfFree designation

Please add a field on the JSON representing if an FSF license is considered Free / Libre.
The licenses listed on the Free Software Foundation License List have the following designations:

Free licenses compatible with the GNU GPL
Free licenses compatible with the FDL
Free licenses incompatible with the GNU GPL and FDL
Nonfree licenses
Licenses for work stating a viewpoint

The Free / Libre designation would be a license identified as 1, 2, or 3 in the above list.

On Fri, Oct 20, 2017 at 08:19:27PM +0000, goneall wrote:

Please add a field on the JSON representing if an FSF license is
considered Free / Libre.

Already there 1, for example:
$ curl -s https://wking.github.io/fsf-api/Expat.json | jq .tags
[
"glp-compatible",
"libre"
]
That information isn't in licenses.json, since that's trimmed down to
only provide an index 2.  That keeps the size manageable as the
per-license metadata grows (e.g. to include the full license text,
if/when we start providing that).

Please re-open if there's still something missing, or if you just want to kick around how/where to store this information.

Got it - I was just looking at the index.  Would you be OK adding the tags to the index?  It would save me quite a few file opens and a bit of code complexity.

Now, if only I could figure out how to re-open ;)

From the Stack Overflow post it looks like I can't re-open the issue if I didn't close it.

On Fri, Oct 20, 2017 at 02:42:03PM -0700, goneall wrote:

Got it - I was just looking at the index.  Would you be OK adding
the tags to the index?  It would save me quite a few file opens and
a bit of code complexity.

This is for a pull into spdx/license-list-data, right?  Can you point
me at your WIP code so I can take a stab at the “fetch tags from the
per-license JSON” approach?  Then if you don't like what I come up
with, I'll add them to the index here.

I'm planning on updating the License Generator to read the JSON file from the repository.
The files is in the middle of some major refactoring (it has gotten a bit out of hand with the addition of several new output formats).
I'll add a comment once I check in the refactored code.
I'll also add a hook for updating the FSF Libre flag.

Just updated the code repository for the tools.  I added a class specifically to parse any FSF data FsfDataParser.  Not much in the class yet - just a hook.  I also added hooks to pull external data for both licenses and exceptions during the license processing, which should make it easier to add OSI checking later.

BTW - I don't mind doing a file by file parsing if you're opposed to adding the tags in the index.  It would just be easier for me to process one file (and it may be easier for other users of the metadata as well).

I added a class specifically to parse any FSF data FsfDataParser.   Not much in the class yet - just a hook.

I've filed spdx/tools#112 filling that in.

It would just be easier for me to process one file…

I agree, and as you point out in #5, the size increase by including tags is only around 55%.  I'm less concerned about that specific bump, and more concerned about starting down a slippery slope.  Scoping the index as “only what you need to find FSF ID(s) (for a given name or SPDX ID)” is more objective than trying to decide on a per-property basis which properties will be needed by aggregators.  Of course, I may have already started down that slippery slope by including name and identifiers.  I've filed #6 pulling those out.  How does that look to you?

Note: Moving conversation from https://github.com/spdx/tools/pull/112#issuecomment-339783347
I understand the desire to have a "clean" implementation of an API, but the same argument could even be made for storing the SPDX ID. That being said, my opinion is that we should include the flag in the index for practical reasons.
Can you describe any practical issues with including the flag in the index (e.g. performance or maintenance issues)? And do you believe these issues outweigh the practical issues with not including the information in the index?
There are several examples of indexes and file system directory structures where metadata is stored in the index itself.
One other consideration, the fsfLibre is a core piece of FSF information and, in my opinion, the main reason for the FSF list. Therefore it should be included in the index.

On Thu, Oct 26, 2017 at 01:06:49PM -0700, goneall wrote:

Can you describe any practical issues with including the flag in the
index (e.g. performance or maintenance issues)?

I don't see a practical issue with including tags in the index, but I
do see size/efficiency issues if we grow the fat index used by the OSI
[1,2,3,4,5].  license-list-XML (with all our data) currently has
around 4.5MB in src/.  The FSF is unlikely to have opinions on as many
licenses as we carry, but still, a fat index will be much bigger than
#6's 2.2kB.
My issue with including tags (or as in #6, even names and SPDX IDs),
is that it's very hard to draw a clear line about what information is
important enough to go into the index, and what information is
peripheral enough to be kept out.  If we let tags in now, we have to
repeat this discussion for each property when someone else comes along
asking to have it added to the index.

And do you believe these issues outweigh the practical issues with
not including the information in the index?

With #6, figuring out the FSF metadata for any license is a single
request (e.g. to 6).  I expect the main index consumers will be:

Pages like 7, if the FSF decides to render that from the API
(currently we render the API from their list, but with a canonical
API it would be DRYer to go the other way).

Tools constructing FSF ↔ whatever ID mappings.

That latter case will need access to the full text of the license, and
that's what I'm concerned about stuffing into the index.  Folks who
are interested in a fat index can still reconstruct it on their side
with:
FIRST=1;
echo '{' >fat-index.json
for LICENSE in $(curl -s https://wking.github.io/fsf-api/licenses.json | jq -r '.[]')
do
if test -z "${FIRST}"
then
echo ',' >>fat-index.json
fi
FIRST=
echo -n ""${LICENSE}": " >>fat-index.json
curl -s "https://wking.github.io/fsf-api/${LICENSE}.json" >>fat-index.json
done
echo '}' >>fat-index.json
or similar, which allows them to trim out anything they aren't
interested in.
A more modern approach to this would be to serve the metadata with
GraphQL 8 or similar, so consumers could ask for what they want
explicitly.  But that seems over-engineered for data the size of this
license list.

My issue with including tags (or as in #6, even names and SPDX IDs),
is that it's very hard to draw a clear line about what information is
important enough to go into the index, and what information is
peripheral enough to be kept out.  If we let tags in now, we have to
repeat this discussion for each property when someone else comes along
asking to have it added to the index.

I don't think drawing the line is that difficult.  If the information is small and is high use, it should be included in the index (and also in the details).  If the information is large, it should only be present in the details.  I concede that small and large are judgement calls, but I don't see that being a big issue.  License text is clearly a large amount of data and should not be in an index.
This is the approach we took on the license list JSON format and I have not heard any of the users of that format raising concerns on the information stored at the index or detail level once the detail level was added for capturing the license text and template data.
We could take another approach and have 2 indexes - one small and one large containing the extra data.  I still would not include the license text in the larger file, but all other metadata could be added.

We could take another approach and have 2 indexes...

Done via #6.


Support /dev/crypto on FreeBSD 12.x and older

This is a cherry-pick of the first change from #13468 and the followup fix in #13807.  Note that the commit to use CIOCGSESSION2 to select between hardware and software drivers from #13468 is not included as the related code changes to support the same functionality on Linux are not present in the 1.1.1 branch.

@mattcaswell you had reviewed the master analogue, if you have a moment.

@mattcaswell you had reviewed the master analogue, if you have a moment.

This pull request is ready to merge

Merged to 1.1.1.  Thanks for the submission, and sorry to have let it sit for so long!

Somehow this change breaks Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028) on FreeNAS 11.3-RELEASE (FreeBSD 11.x based, both in OS and in iocage). On 1.1.1j and 1.1.1k without this fix works fine. Might it be possible to handle CRIOGET error with just message + cfd =fd?

@lonewasp it's probably best to file a new github issue for your problem.
That said, do you think it is related to the issue described at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254643 ?

@kaduk Yes, looks to be same origin of issue. Compile time check for CRIOGET seems to be in conflict with runtime reaction on ioctl.

Sorry, I've been meaning to submit a change to just revert this change both in master and 1.1.1.  Given FreeBSD's ports have effectively done that I hadn't gotten around to filing the PRs upstream (I hadn't really counted on other folks building OpenSSL directly from source outside of ports).  As discussed in the bug @kaduk linked to, the issue is that FreeBSD's kernel kills the CRIOGET fds during fork().  This doesn't break simple tests (like openssl speed), but does break applications like apache and nginx that initialize OpenSSL in a master process that forks off worker processes.  The pre-1.1.1 engine handled this by doing the CRIOGET at the time of creating a session (so post-fork).  While this could be fixed to do that, the /dev/crypto engine in FreeBSD 12 and earlier is of limited utility (the only useful thing you could offload would be AES-CBC, but you'd still do the associated HMAC for MTE/ETM modes in userland defeating much of the point).


1.0 Roadmap

There are two issues and a number of tiny improvements that should land for the 1.0 release.

#3
#6
[ ] outdated menu handler should have navigation control access, and the default handler should leverage that awful types and worse performance
[x] DynamicString should only be a function, and the current version should be called MaybeDynamicString
[x] Make addRange public
[x] Make add public and let it accept many buttons
[x] Fix Range class not appearing in API reference (expose directly and rename to MenuRange, not on Menu instance)
[x] Document default values of config options
[ ] Write plugin docs on https://grammy.dev
[x] Drop the byte count because fingerprints and payloads add to much uncertainty for the check to be meaningful

If user testing reveals further flaws in the design of this plugin, the above list will be extended.
If you want to work on any of the things, please leave a comment here so no work is done twice.

Please test this plugin, and give feedback! It should be ready to use. No further changes are planned, unless you bring up something.

1.0 released in a0cd64a02681ef33d2a2a5517f85818dfe83f1d7


Some LightGBM predictions are not coming in quantile regression range

Environment info
Operating System: Ubuntu 16.04.3 LTS
CPU/GPU model: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
C++/Python/R version: Python
LightGBM version or commit hash: 2.2.3
Issue
Some predictions of LightGBM regression are not coming in the quantile regression range. In the below code, y_pred outputs are not in between y_lower and y_upper after taking prediction interval (PI) range 98%.
Also, shouldn't the mean of y_lower and y_upper  always be same irrespective of the PI range? I'm getting different mean value of y_lower and y_upper for different PI.
clfl = lgb.LGBMRegressor(objective = 'quantile', alpha = 0.01, metric = 'l2')
clf = lgb.LGBMRegressor(objective = 'regression', metric = 'l2')
clfh = lgb.LGBMRegressor(objective = 'quantile', alpha = 0.99, metric = 'l2')

xx = [...]

y_pred = clf.predict(xx)
y_lower = clfl.predict(xx)
y_upper = clfh.predict(xx)

@pratyush19 the quantile regression cannot ensure 100% predictions are in the ranges.
The goal of quantile is too reduce the quantile loss.


Complete onboarding plan for PAE

[x] Complete starter projects doc
[x] Complete welcome to ODI checklist
[x] Complete onboarding form for Aeri
[x] Verify start date
[x] Schedule meetings using aeri's ODI email ahead
[x] Create AWS user
[x] Create Snowflake user

Closing as complete


Added #[Inject] attribute support

Codecov Report

Merging #34 (25a08da) into master (0083004) will increase coverage by 5.96%.
The diff coverage is 93.97%.

@@             Coverage Diff              @@
##             master      #34      +/-   ##
============================================
+ Coverage     88.53%   94.49%   +5.96%
- Complexity      458      677     +219
============================================
  Files            19       23       +4
  Lines           916     1309     +393
============================================
+ Hits            811     1237     +426
+ Misses          105       72      -33

Impacted Files
Coverage Δ

src/Traits/ResolveTrait.php
80.23% <87.50%> (+26.16%)
:arrow_up:

src/Loader/YamlFileLoader.php
89.55% <89.55%> (ø)

src/Definition.php
97.47% <92.50%> (-0.86%)
:arrow_down:

src/ContainerBuilder.php
96.57% <93.47%> (+7.44%)
:arrow_up:

src/Loader/FileLoader.php
95.94% <95.94%> (ø)

src/AbstractContainer.php
100.00% <100.00%> (ø)

src/Builder/CodePrinter.php
100.00% <100.00%> (ø)

src/Container.php
100.00% <100.00%> (ø)

src/Facade/FacadeProxy.php
100.00% <100.00%> (ø)

src/FallbackContainer.php
100.00% <100.00%> (ø)

... and 17 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 2991f1e...25a08da. Read the comment docs.


Added support for relative file paths

The recent changes to the copy_artifacts fastlane action broke relative paths. This PR fixes those.

:+1:

This is great! Thanks @lmirosevic !! 🚀


Units reads ratio when it should read percent

When the unit percent is selected for the display the widget displays the value as percent correctly, however it shows the units as ratio.

Added new percent unit :) Will be in next release


LTS Haskell

If we use LTS Haskell, what is the advantage of keeping version ranges for modules in the haskoin.cabal file? Souldn't we also align those versions to the LTS versions? That way, people that don't use LTS Haskell would still be guaranteed a correct build and a predictable and tested build.

I don’t think so. Policy should not be in our cabal file.  The Cabal file in the application merely states what is compatible at the API level with our repository, while the config.cabal from Stackage is a policy.  It states exact versions.  We may update the config.cabal at any time, and it does not necessarily mean that we will update our cabal file.  A user that needs to compile haskoin on a non-Stackage system may decide to remove config.cabal for that.

OK, sounds good then. ACK


Changed Github to GitHub

i did not change any property names or stuff because i didnt want to break anything, just strings that the user can actually see

thanks


Remove redundant code from lexer

Just removes a couple of lines of redundant code from the lexer.
A note on the 2nd one:
let mut builder = AutoCow::new(lexer);
let c = lexer.consume_char();
builder.push_matching(c);

push_matching() is a no-op unless force_allocation_without_current_ascii_char() has already been called. Here the AutoCow has just been freshly created, so we know it hasn't.

Compiler would have probably been smart enough to chop them out anyway, but was just aiming for tidier code.


Update to latest version of glslang

See https://github.com/KhronosGroup/glslang/issues/1976 for context. It would be good to update and remove ENABLE_HLSL define to avoid future layout issue.

draft PR https://github.com/BabylonJS/BabylonNative/pull/129


Fix CircleCI Contexts

This pull request was programmatically opened by the multi-repo-updater program. It should be adding the 'Gruntwork Admin' context to any Workflows -> Jobs nodes and should also be leaving the rest of the .circleci/config.yml file alone.
This PR was opened so that all our repositories' .circleci/config.yml files can be converted to use the same CircleCI context, which will make rotating secrets much easier in the future.

No files changed in the PR?

No files changed in the PR?

Yes, at the end of the night I updated this status at the bottom of the PR description here: https://github.com/gruntwork-io/prototypes/pull/85 but realized I should have dropped a comment here.
TLDR; I will look into and fix why this is happening. I suspect the logic for detecting that the correct contexts are already in place worked here, yet execution incorrectly proceeded to creating a branch and PR anyway. I wanted to leave it open until I could confirm, then patch the code, close this PR and re-run.

No files changed in the PR?

Fixed in https://github.com/gruntwork-io/prototypes/pull/85/commits/cfcfffdcd8120b7d471238d406eb8b256cbeea97

Preparing to re-run the batch that includes this repo now that the bugs have been fixed.


#109 and #110 about page updates

This closes #109 and closes #110.
I also added target="_blank" to all of the external links in index.html
@nathanmwilliams I slightly changed the language on the "We do not currently include" section from                   "Events where it would be inappropriate to ask policy questions of your representative (i.e. a funeral)" to "Inappropriate events to ask policy questions at (e.g. funerals)".  Lemme know if that's a problem copy wise, but I wanted to try and fit it on a single line as that section is already larger than everything else.
@meganrm I switched the 3col layout to a 2col.  Could keep 4 at lg/xl but it still looked kinda smushed.  And this way it matches the row under the banner.  We could also put the Our Supporters down under the banner (and make both 3col) but it doesn't really seem to match the content.

@pdvorchik Gotcha. Could you lose the "at"? So "Inappropriate events to ask policy questions (e.g. funerals)"

Sure.  Done.


Detailed SHR results

Hello,
I am trying SHR evaluation and would like to compare the results, could you please share the following:

average generation length (i.e., words_per_image, sents_per_image) of the reported numbers, e.g., in Table 3;
Or it would be even better if you could share the full metrics.json file for the corresponding models. As you understand, getting a lower SHR is easy if the generated length is very small.
also, I guess the SHR reported in Table 3 is the same as mean_hal_ratio*100 in the metrics.json file?

Thanks!

Thanks for your interest in our work! Here are the full metrics:
MiniGPT4

HA-DPO
metric file

n
metrics.json

y
metrics.json

InstructBLIP

HA-DPO
metric file

n
metrics.json

y
metrics.json

LLaVA-1.5

HA-DPO
metric file

n
metrics.json

y
metrics.json

As far as our concern:

It is indeed that SHR is lower when the model is very cautious (output few words or sentences), so we use average generation length to indicate whether this phenomenon happens. And HA-DPO won't lead to a decrease in generation length.
Yes, the SHR in Table3 is the same as mean_hal_ratio*100 in the metrics.json file, which is the average number of hallucinated sentences.

awesome! appreciate it.


Update swift-wisdom to Swift 3

This PR encompasses all changes to make Swift Wisdom compatible with Swift 3. Thanks everyone who helped out! The goal of this PR is to get a workable swift wisdom so that people can start using it in their projects. Therefore, there remains some TODOs and some inconsistencies. This PR includes changes from nyc/standard-library, whose commits have been reviewed. This PR also includes two unreviewed commits:

a bit more bookkeeping
attempt to rename some more classes

This commits can be reviewed individually.
Other than that, all tests are passing, and I have tested this against a swift-3 project. :tada: To try it out, add this to your Podfile:
pod 'Intrepid', :git => 'https://github.com/IntrepidPursuits/swift-wisdom.git', :tag => '0.6.0'

Once I get 2 approvals, I will merge this into master. Like the real master. Really.

actually, 4 unreviewed commits, the last 2 to update pods and add attributions are also technically unreviewed.

Looks like we didn't get dropping CompositeDisposable's key into this PR


Ontology term 'mixed' CHEBI:60004 missing from a number of compounds

Hi Adnan,
Jerven from our development team identified a range of compounds which in their definitions were described as mixtures without being linked to 'mixture ' in the ontology.
He has generated a list which is currently available at this URL:
https://tinyurl.com/ypxjhtl2
If it expires you can generate the list at sparql.rhea-db.org using this query:
SELECT ?chebi ?label ?comment
WHERE {
GRAPH <
http://sparql.rhea-db.org/chebi>
{
?chebi <
http://purl.obolibrary.org/obo/IAO_0000115>
?comment .
FILTER(CONTAINS(?comment, "mixture"))
OPTIONAL {
?chebi rdfs:subClassOf CHEBI:60004 .
BIND(true AS ?isMixture)
}
FILTER(!BOUND(?isMixture))
FILTER(?chebi != CHEBI:60004)
?chebi rdfs:label ?label .
}
}
Best,
Kristian

Formatted query written in a way that can be run at ontobee or rhea-db
PREFIX CHEBI: <http://purl.obolibrary.org/obo/CHEBI_>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX owl: <http://www.w3.org/2002/07/owl#>
SELECT ?chebi ?label ?comment
FROM <http://sparql.rhea-db.org/chebi>
FROM <http://purl.obolibrary.org/obo/merged/CHEBI>
WHERE {
  ?chebi <http://purl.obolibrary.org/obo/IAO_0000115> ?comment .
  FILTER(CONTAINS(?comment, "mixture"))
  OPTIONAL {
    ?chebi rdfs:subClassOf* CHEBI:60004 .
    BIND(true AS ?isMixture)
  }
  FILTER(!BOUND(?isMixture))
  FILTER(?chebi != CHEBI:60004)
  ?chebi rdfs:label ?label .
}


Fix dependencies

Strong versioning of dependencies can mess up existing envs and cross deps
cc @vikashplus

Just had the same issue when installing the repo into an existing conda env which had a higher pytorch version, it was downgraded as a result of installing r3m.

@suraj-nair-1 -- Can we relax these dependencies? We might have to validate that the published checkpoints load, and the numbers can be reproduced.

Yeah this should be fine, let me just verify that numbers still reproduce as expected then I'll merge this.

Ok just tested and with the most up to date torch, torchvision, and cuda the models load and the "Verifying Correct Installation" numbers are similar, so going to merge.


2.1.6 Nuget package build issue

Hi,
I am getting below error in xamarin iOS project. Can you please help me to solve it
Error MT2002: Failed to resolve "System.Void ObjCRuntime.DelegateProxyAttribute::.ctor(System.Type)" reference from "Xamarin.iOS, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=84e04ff9cfb79065" (MT2002)
I have added 2.1.6 branch io nuget package.
When i add below piece of code in appdelegate class. i get the above error
BranchIOS.Init("key_test_ebkY2JyMRCUqeEdJ5KfaSbcoAzdcxfMn", options, this);
Regards,
Sudarshan Shetty

Hello @Sudarshanshetty,
does "this" implement IBranchSessionInterface or IBranchBUOSessionInterface?

ya we have implemented . Please find below snippet
public partial class AppDelegate : UIApplicationDelegate,IBranchSessionInterface
#region IBranchSessionInterface implementation
    public void InitSessionComplete(Dictionary<string, object> data)
    {
        // Do something with the referring link data...
    }

    public void SessionRequestError(BranchError error)
    {
        // Handle the error case here
    }

    #endregion

@Sudarshanshetty try to set "linker behaviour" to "don't link"

@antonargunov : But it will effect my other library . Can you please tell why we need to set "linker behaviour" to "don't link"

http://xamarin21.rssing.com/browser.php?indx=23562832&item=23109
We can update the package, but I can't guarantee that new package will help you.
Can you try to put our SDK source code into your project?

So latest nuget package you have updated is built with Xamarin beta SDK ?
We tried with updating nuget packages in some other project  , we are getting same issue in all projects .

@Sudarshanshetty all our package versions were built with stable Xamarin versions, we don't use Xamarin beta versions.

We tried with updating nuget packages in some other project , we are getting same issue in all projects.

Can you explain that?
What packages did you try?
What is your version of Xamarin?
Also, can you download our Xamarin SDK and try to run our iOS testbed?

Can you explain that?
1We have already implemented branch.io in of old project. it was working very good. we just took update by clicking on update in xamarin studio, it got updated to 2.1.6 version. Also we tried in the new project in which we are trying to integrate branch.io for the first time . that also got failed.
What packages did you try?
https://www.nuget.org/packages/Branch-Xamarin-Linking-SDK/     version number 2.1.6
What is your version of Xamarin?
5.10.1 (build 6) , iOS SDK 9.1

@antonargunov , any updates on this issue?
We face the same issue mentioned here in our apps.
When linker behaviour is set as not to link, the integration works and branch links opens the app.
But we do have other libraries in the project, which needs to be linked. So any estimated time for this fix?

Hi @venky284 , sorry but I can't reproduce that.
Can you provide me with info:

what library(s) do you have in your project?
if you use PCL, what PCL profile do you use?
if you don't use PCL - write "no" please

And then I will create new project and will try to reproduce that issue.

Hi @venky284 , did you try other linker behaviours? If yes, what is result?

@Sudarshanshetty you wrote "We have already implemented branch.io in of old project", what version does work nice for you?

@antonargunov
We have other libraries for barcode scanners and loading the images.
PCL, we use targeting .Net 4.5
We are facing the issue in iOS (Xamarin)

@antonargunov , at the moment we use 2.1.3, which used to work before the 2.1.6 release.
Now the apps are doesn't open up with the bnc.lt links, where in it redirects to appstore and tapping open from there, opens the app. This is expected as we are using a legacy version.
But to update the sdk to 2.1.6, we face the above mentioned issue. Hoping for an early resolution.

@venky284 update will be soon
Note: in new version of SDK we will remove non-BranchUniversalObject functional

@antonargunov , could we get any ETA on the updated SDK?

@antonargunov  , could we get any ETA on the updated SDK?

@venky284 Hi, sorry, for delay.
We are going to publish new version this week.

We have uploaded new version of Xamarin SDK.
Read please documentation, because there are several changes in new SDK.
You can find samples for iOS and Android (form, non-form) in our repo.
Feel free to create new issue after integration of new version.


Added Strikethrough

This PR adds strikethrough text as one of the /-commands.

Okay I'm a dummy and realized that it doesn't really makes sense to have this as a slash command option – it's already been added as a Bubble Menu option (#13) and I believe that's the more natural place for this to live.
Gonna close this for now – sorry for the trouble here Dries! 😅


Add support for windows MSVC builds.

Signed-off-by: Teemu Rytkonen<EMAIL_ADDRESS>

@schoolpost Could you check this pull request?


Use a single data field in roaring.container instead of 3 slices.

Description
Continuing the theme from #824 and #825 - it may be possible to save significant memory without affecting performance in the roaring.container struct. It currently has 3 slices of different types - each of which consumes 24 bytes of memory. Only one of these is in use at a time while the other two are nil (except during conversions). The proposal is to use a single field data interface{}, and use type switches or type assertion like so:
func (c *container) array() []uint16 {
    if r, ok := c.data.([]uint16); ok {
        return r
    }
    return nil // or panic?
}

Basic benchmarking seems to indicate that this will be similar to, or even better than the previous solution in terms of performance, and it will save (I think) 32 bytes of memory per container. Reasoning here is we're getting rid of two slices which saves 24*2=48 bytes, but we're adding an interface{} value which points to a slice, and the interface costs 16 bytes, so 48-16=32.
Success criteria (What criteria will consider this ticket closeable?)
Refactor roaring to use a single field for container data - confirm memory savings and minimal performance impact.

and before i forget: this might conceivably imply that a bitmap struct would be [8192]uint64 instead of []uint64, saving us a valuable allocation.

wouldn't it be [1024]uint64?

Well, sure, if you wanted to be correct.
I remembered that it was "8K", and there was too much blood in my caffeine stream.

we went a different direction on this, but the container shrinking work is in


Asyncify

https://github.com/GoogleChromeLabs/asyncify

Please use performant true coroutines with a relooper, no stack allocation management and registers. See https://github.com/mys-lang/mys/discussions/17
asyncify is way too generic to get wasm or softrealtime decent performance.

@pmp-p Thank you for your advice.
I'll look into it.


Include latest operator sdk version released

Include latest version of the operator sdk.
This is done to test if this latest operator
version helps on fixing deployment issues
detected on some deployments.
Resolves: #33

After several runs, it seems operator-sdk v1.28.0 fixes the stability issues. Merging


ARTEMIS-4127 refactor multiprotocol JMS tests in AMQP package

Over time org.apache.activemq.artemis.tests.integration.amqp has become home to many multi-protocol JMS tests even though the package is really for AMQP-specific tests. This commit splits those tests out into their own package.
This is a preliminary step to clarify these tests before I add another one for a different issue.

This change looks good, there is test failure, but don't believe its related to this change. But if in another cycle anyone has a chance to look at would be good, bit of a worry.......
Build / Test (17) (pull_request) Failing after 25m

[INFO]
Error:  Failures:
Error:    AcknowledgementTest.testDupsOKAcknowledgeQueue:555->ActiveMQServerTestCase.assertRemainingMessages:364 expected:<20> but was:<21>


Make use of nitro server API routes

Idea:
Introduce server API that proxies requests through the Drupal backend
/api/drupal/* ---> drupal/  (no cache by default)
/api/drupal-ce/   ---> drupal/ce-api/  (no cache by default)
/api/menu/{name} ---> drupal/api/rest_menu_items/{name}   (cached 5min by default, if possible disabled in dev)

Advantages:

Make use of route caching settings to cache API responses in Nuxt - https://nitro.unjs.io/guide/routing#route-rules
Possibility  to simplify authentication by being able to simply set a cookie on the frontend domain + forward to the backend

Requirements:

Keep SSG working, hopefully nuxt handles that out-of-the-box
Be able to customize cache settings in projects by API endpoint

Implementation plan:

Have default route rules via module, support override config. If route-rule, pre-exists, just take that.
change default code to use the server-route instead of Drupal-API directly

Ah this is a great idea. I was going to ask about this.

this is shipped in https://github.com/drunomics/nuxtjs-drupal-ce/releases/tag/v2.0.0-beta4


Fix int overflow on 32bit OSs

Original error was:
failed to get torrents: json: cannot unmarshal number<PHONE_NUMBER>7 into Go struct field Torrent.arguments.torrents.leftUntilDone of type int

Tested on armv7l.

cool! Thanks


Disparity of right image

Hi, the output is the disparity map of the left image. Can I get the disparity of the right image? Many thanks!

Hi, the output is the disparity map of the left image. Can I get the disparity of the right image? Many thanks!

Hi, I'm looking forward to get the right disparity map.Have you figured it out?
Best wishes.

You can rotate the input image pair by 180 degree. Then the right image becomes left one.

This will make learned biases apparent, i.e. hallucinating road surface like depths in the bottom sky.

You can rotate the input image pair by 180 degree. Then the right image becomes left one.

Thank U very much for your replying, I tried to rotate the input image pair by 180° as you said, but the results seems not right like this:

don't know why. It seems ok in my application.

don't know why. It seems ok in my application.

When I exchange the input like this:
left_fold  = 'image_3(180)/'   right_fold = 'image_2(180)/'
It works very well.

Thanks for your kind help again.

This will make learned biases apparent, i.e. hallucinating road surface like depths in the bottom sky.

It shouldn't if the network do not estimate the disparity relying on over-fitting.

This will make learned biases apparent, i.e. hallucinating road surface like depths in the bottom sky.
It shouldn't if the network do not estimate the disparity relying on over-fitting.

It did for me kind of.
Color KITTI VO 00 00000


[security] setting X-Frame-Options=SAMEORIGIN to prevent clickjacking

@williaster does that break your integration?


Connection Pool

Create and reuse existing connections to the database. Similar as HirakiCP or Postgres PooledConnection

I think we don't need a custom implementation of the connection pool.
An end-user can provide a pooled data source if needed using, for example, Hikari data source. https://www.baeldung.com/hikaricp


Add alias for dotnet workload install command

dotnet workload install - Installs optional workloads. Introduced with .NET 6 SDK.
The dotnet workload install command installs one or more optional workloads. Optional workloads can be installed on top of the .NET SDK to provide support for various application types, such as .NET MAUI and Blazor WebAssembly AOT.
Docs: https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-workload-install

Please assign it to me

Hi @pascalberger @augustoproiete
could you please create a separate issue to add integration tests for all workload aliases to https://github.com/cake-build/cake/blob/develop/tests/integration/Cake.Common/Tools/DotNetCore/DotNetCoreAliases.cake?
It'd be better to add tests when all aliases will be merged because for instance  dotnet workload uninstall  - there is nothing to uninstall on the build servers. First, we need dotnet workload install, to assert the installation we need  dotnet workload list and so on


Additional Resources on open Access from various sources

We can get a few Low-cost Journals here: https://github.com/JoachimGoedhart/LOA
We can obtain some data on the cost of APC in various journals here. Last updated two years ago, but it is a good start
Cost of open access publishing in Germany: https://github.com/njahn82/paper_openapc
FourishAI is already doing part of what we could be interested in but hasn't been updated in years. https://github.com/FlourishOA/Data. The data is useful; what can we borrow from what they have done. The information they have is essential; we need to find a way of ensuring continuity and sustainability.
OpenAPC: Would have additional information we may require.

having looked at the above resources, what problem needs solving? What can we address during the Sprint, especially with potential contributors?

[ ] A Website to host the data?
[ ] Web scrapper to automatically extract the information from various publishers?
[ ] List of funding opportunities for OA publishing?

In light of the above resources, we may:

Extend the LowCostOpenAccess resource to include information on the range of APCs. This may be useful in combination with waivers or subsidies being offered by the journals.
Create web scrapper would be useful to obtain the data on the APCs while also building on the already existing data.
As authors may choose to have their APCs covered by OA funding agencies, we can also include this in the resource. Even some publishers offer assistance on APC funding. For example, PLoS has a publication fee assistance program.
We may create a short survey to get feedback from prospective users on what information authors look for as they look forward to publishing.

I think having a form like structure on the GitHub-hosted site would be helpful. Anyone who knows of a OA journal that is free/costs less for APC/has subsidies for low and mid-income countries should be able to submit from a simple form on the  LowCostOpenAccess site which then can be accepted/discarded by the moderator.

That is very useful @psubhashish, this can be linked in the site, and would allow us to collect additional information from the users of Affordabee.

Thank you @psubhashish. We could also use the same strategy to collect feedback on the Affordabee site.

Great, let's create an issue with this as an independent task.

Great, let's create an issue with this as an independent task.

Done #21


Device tracker

Thanks for the integration,  I propose some enhancement
I use device trackers to monitor the different equipments connected to my livebox.
Other integrations also provide device trackers.
In order to filter the equipment linked to the livebox I propose to add an attribute
"Scanner =LiveboxDeviceScanner".
I also modified the device_tracker.py file in order to make other informations available to improve devices monitoring.
My device_tracker.py is joined as .zip
An exemple of the displayed data

_
device_tracker.zip

I propose the PR  "Update device_tracker.py #84"

I just suggested some improvements. Thanks for looking at the PR.

Look at 2.1.2-beta version


Backup codes aren't written to the database so can't be used

Everything else so far is working, and broadly I followed the approach described here - https://www.jamesridgway.co.uk/implementing-a-two-step-otp-u2f-login-workflow-with-rails-and-devise/
I've added :two_factor_backupable on my user model, and this to the devise initializer:
config.warden do |manager|
  manager.default_strategies(:scope => :user).unshift :two_factor_backupable
end

One comment here, it wasn't clear whether I also needed to add :two_factor_authenticatable to the warden config? It seems to work without so assume not?
My user model has:
  devise :two_factor_authenticatable, :two_factor_backupable,
          otp_backup_code_length: 10, otp_number_of_backup_codes: 10

I am able to generate and view the codes, using the following in the controller:
    @backup_codes = current_user.generate_otp_backup_codes!
    current_user.save!

However the codes don't get saved to the database, which means when I try to use them it just says invalid code. Opening the console and running `user.two_factor_backup_codes_generated?' on that user always returns nil, and looking at the database there is nothing saved to the otp_back_codes column. Using Postgres so should work?
Anyone got any thoughts?
Thanks

Urgh ignore me. The guide must be a little outdated because it says to serialise as JSON:
  # Ensure that backup codes can be serialized
  serialize :otp_backup_codes, JSON

Don't do that.


Authority::Locale raised as error by xsd validation

I'm getting the following XSD validation error for the file below, which at first sight seems correct to me and to my understanding of the XSD:

Element 'Locale': This element is not expected. Expected is one of ( PrivateContactDetails, OrganisationType, typesOfOrganisation, Status, ValidityPeriod, parts, ownResponsibilitySets, delegatedResponsibilitySets, delegatedFrom, relatedOrganisations ).

The faulty part is (extract of the relevant section):
                <ResourceFrame version="any" id="FOO:ResourceFrame:0">
                    <organisations>
                        <Authority version="any" id="FOO:Authority:1">
                            <Name lang="fr">FOO</Name>
                            <ContactDetails>
                               <Phone>0102030405</Phone>
                               <Url>https://www.foo.com</Url>
                            </ContactDetails>
                            <Locale>
                                <TimeZone>Europe/Paris</TimeZone>
                                <DefaultLanguage>fr</DefaultLanguage>
                            </Locale>
                        </Authority>
                    </organisations>
                </ResourceFrame>

Reading the Netex 1.2.2 generated Java binding classes, the "rest" field of the "Organisation_VersionStructure" can refer to "Locale" in it's list. The XML above is generated using the binding classes + JAXB.
Is it a faulty interpretation of the specs? Or a bug in the validator?
Note 1: I'm using a 1.2.2 version to generate the XML, however the XSD part of the relevant section from my validator is exactly the same as the one I'm using to generate the file.
Note 2: The validation error is raised by both the latest docker image and the online validator.

From what I have gathered reading https://github.com/ITxPT/DATA4PTTools/blob/develop/xsd/netex/1.2/netex_framework/netex_genericFramework/netex_organisation_version.xsd#L254, the order is important, the element must appear in the same order as in the definition i.e. swapping the place of <ContactDetails> and <Locale> should fix the issue.
Working example
<ResourceFrame version="any" id="FOO:ResourceFrame:0">
  <organisations>
    <Authority version="any" id="FOO:Authority:1">
      <Name lang="fr">FOO</Name>
        <Locale>
          <TimeZone>Europe/Paris</TimeZone>
          <DefaultLanguage>fr</DefaultLanguage>
        </Locale>
        <ContactDetails>
          <Phone>0102030405</Phone>
          <Url>https://www.foo.com</Url>
        </ContactDetails>
    </Authority>
  </organisations>
</ResourceFrame>

Indeed, that solved the issue. The generated java binding classes does not enforce the fact that the order matters.


[fix] Fixed mobile scaling and desktop issues with FileInfoDialog

Earlier:
Hello, sorry for the earlier mess that was a pull request, I'm still getting the hang of things :)
Mobile changes:
I found the FileInformationDialog to be unusable on mobile, as the texts and buttons were all not scaling with the window size, and there was also the thumbnail or "preview" message on the side pushing everything even more off-screen. From now on the preview message should not show up when in mobile mode or any other kind of preview. The UI stuff like buttons and textboxes are now also correctly scaled and usable.
Desktop changes:
I also noticed that when in desktop mode, when listing a file's information, elements from the album section and under would go off screen and you could not navigate to them by scrolling. I've now made it so that the text and elements stay within the InformationDialog box and are able to be scrolled.
Video:
https://files.nocx420.xyz/dRCvTdlxtEV0.mp4

Thank you for working on this, I'll check it out this week and get back to you!

@NOCx420 sorry it took me so long to check this, I was on vacation.
For the portion of the changes that modify how it looks on mobile I see no issues, but I'm not sure about the second part. You mention that it's not possible to scroll down to the off-screen settings at the bottom of the dialog yet in the current version I'm able to do so as shown on the following video https://chibisafe.moe/GAH5oCll.mp4
Would you mind checking it out and if you experience the same, getting rid of those changes so that I can merge the mobile fix only?
Thanks!

@Pitu I have removed the changes you asked for, however on my side, scrolling doesn't work without them (https://files.nocx420.xyz/axQzcEDtjK6t.mp4). Might be a platform issue. I'm using linux and firefox, I'll try to look into what the problem might be.

Yep, it's definitely something with firefox. Scrolling works and elements don't overlap on chromium, but not on firefox. I'm still looking for what the issue could be, but honestly, I'm stuck for now.


Scala 2.9.1 and Salat 1.9.2

For your consideration:
I've managed to get tests passing using Salat 1.9.2 (I plan on making a 2.10 branch as well).
I've also added some methods for working with Avro datafiles, and some test to go along with them.
Apologies for the messy history; still getting the hang of things!
No sweat if you're over this project, thanks for making this OSS!
-Julian

We no longer use salat-avro for anything. I'm going to close this as it's been sitting around for a year. Sorry.


Removed stale-bot integration

Proposed Changes
Remove stalebot integration.
Similar to https://github.com/datapane/datapane-hosted/pull/1034
In general, I feel it is pretty annoying to Open Source contributors when an issue is closed just because we didn't do anything about it yet, and the label wontfix is unhelpful when it has been decided by a bot.
At the moment, we have very few issues/PRs in this repo, so staying on top of them is not hard. In the future, if we do have problems, I'd suggest something like:

if we (datapane.com employees) are intending to work on a bug/feature request, never close it automatically just because we haven't done so yet.
if we are not intending to work on it, but would accept a patch from the community, we should:

clearly indicate this on the PR/issue with a comment and with a label
close the issue if there is no activity after 1 year, on the assumption that everyone involved has lost interest.

LGTM - merged


Update zk_login.md to include instructions for downloading devnet proving key

Description
See above.
Test Plan
> wget -O - https://raw.githubusercontent.com/sui-foundation/zklogin-ceremony-contributions/main/download-test-zkey.sh | bash
--2023-11-06 12:32:39--  https://raw.githubusercontent.com/sui-foundation/zklogin-ceremony-contributions/main/download-test-zkey.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 2606:50c0:8001::154, 2606:50c0:8003::154, 2606:50c0:8000::154, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|2606:50c0:8001::154|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 180 [text/plain]
Saving to: ‘STDOUT’

-                                               100%[=====================================================================================================>]     180  --.-KB/s    in 0s

2023-11-06 12:32:39 (11.4 MB/s) - written to stdout [180/180]

Cloning into 'zklogin-ceremony-contributions'...
remote: Enumerating objects: 195, done.
remote: Counting objects: 100% (195/195), done.
remote: Compressing objects: 100% (181/181), done.
remote: Total 195 (delta 33), reused 155 (delta 12), pack-reused 0
Receiving objects: 100% (195/195), 59.85 KiB | 2.30 MiB/s, done.
Resolving deltas: 100% (33/33), done.
> cd zklogin-ceremony-contributions
> ls
README.md             download-main-zkey.sh phase1                zkLogin-main.vkey     zkLogin-test.vkey
contributor_list.tsv  download-test-zkey.sh phase2                zkLogin-main.zkey     zkLogin-test.zkey
git❨ main ❩
> b2sum zkLogin-test.zkey
686e2f5fd969897b1c034d7654799ee2c3952489814e4eaaf3d7e1bb539841047ae8ee5fdcdaca5f4ddd76abb5a8e8eb77b44b693a2ba9d4be57e94292b26ce2  zkLogin-test.zkey
git❨ main ❩

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

Transferred changes to the new page.

Ah thanks! Should we be editing the new one from now on? The checks failure suggested so - but I wasn't sure.


calendar: introducing row span limit and default builder

Merging this PR as it's a shell of actual logic which can be found at snehmehta/table_calendar