Slack crashes at start

Steps To Reproduce
Steps to reproduce the behavior:

slack
crashes

Additional context
I'm on 21.11 Wayland but unstable channel slack.
Only recently did slack begin to crash. I have 3 different 4.23 slacks and the one that doesn't crash is /nix/store/y7m50zjsnl7kdqp219vxg9hdw4saiknz-slack-4.23.0/bin/slack, which I built on Feb 13 via home-manager. I don't know how to get back the nixpkgs commit from that build :-/
NIXOS_OZONE makes no difference, it crashes before that.
Output:
$ /nix/store/8jpil83x4wnpgliqfi4bvs0ldyyjazsx-slack-4.23.0/bin/slack
Initializing local storage instance
(electron) Sending uncompressed crash reports is deprecated and will be removed in a future version of Electron. Set { compress: true } to opt-in to the new behavior. Crash reports will be uploaded gzipped, which most crash reporting servers support.
[782641:0222/182359.537485:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is egl, ANGLE is
[782641:0222/182359.540799:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[02/22/22, 18:23:59:601] info:
╔══════════════════════════════════════════════╗
║      Slack 4.23.0, linux 5.10.99 on x64      ║
╚══════════════════════════════════════════════╝
[02/22/22, 18:23:59:601] info: Configured logger via
{
  "enableConsoleTransport": true,
  "identifierOverride": "webapp-service-worker-console",
  "shouldUseNewBackend": false,
  "loggerInstanceCount": 2
}
[02/22/22, 18:23:59:601] info: Predefined values for process
{
  "NODE_ENV": "production",
  "platform": "linux",
  "type": "browser",
  "timeZone": "Europe/Brussels",
  "PACKAGE_MANIFEST.productName": "Slack",
  "PACKAGE_MANIFEST.version": "4.23.0",
  "PACKAGE_MANIFEST.commit": "8c4b013",
  "PACKAGE_MANIFEST.branch": "HEAD"
}
[782594:0222/182359.623586:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[782594:0222/182359.623643:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[782594:0222/182359.630989:ERROR:cursor_loader.cc(114)] Failed to load a platform cursor of type kNull
Segmentation fault (core dumped)

The working slack outputs this:
$ /nix/store/y7m50zjsnl7kdqp219vxg9hdw4saiknz-slack-4.23.0/bin/slack
Initializing local storage instance
(electron) Sending uncompressed crash reports is deprecated and will be removed in a future version of Electron. Set { compress: true } to opt-in to the new behavior. Crash reports will be uploaded gzipped, which most crash reporting servers support.
[782882:0222/182413.066023:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is egl, ANGLE is
[782882:0222/182413.069877:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[02/22/22, 18:24:13:116] info:
╔══════════════════════════════════════════════╗
║      Slack 4.23.0, linux 5.10.99 on x64      ║
╚══════════════════════════════════════════════╝
[02/22/22, 18:24:13:116] info: Configured logger via
{
  "enableConsoleTransport": true,
  "identifierOverride": "webapp-service-worker-console",
  "shouldUseNewBackend": false,
  "loggerInstanceCount": 2
}
[02/22/22, 18:24:13:116] info: Predefined values for process
{
  "NODE_ENV": "production",
  "platform": "linux",
  "type": "browser",
  "timeZone": "Europe/Brussels",
  "PACKAGE_MANIFEST.productName": "Slack",
  "PACKAGE_MANIFEST.version": "4.23.0",
  "PACKAGE_MANIFEST.commit": "8c4b013",
  "PACKAGE_MANIFEST.branch": "HEAD"
}
[782835:0222/182413.144294:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[782835:0222/182413.144397:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[782835:0222/182413.153040:ERROR:cursor_loader.cc(114)] Failed to load a platform cursor of type kNull
[02/22/22, 18:24:13:201] info: Boots up new service worker version
{
  "scriptUrl": "https://app.slack.com/service-worker.js",
  "scope": "https://app.slack.com/",
  "renderProcessId": 4,
  "versionId": 1
}
[02/22/22, 18:24:13:202] info: Feb-22 18:24:13.200 [SERVICE-WORKER] normalizing request URL for cache https://app.slack.com/client/T5U1HAHFD
{
  "versionId": 1
}
[02/22/22, 18:24:13:243] info: Feb-22 18:24:13.241 [SERVICE-WORKER] responding from cache (normalized) /boot/client.html
{
  "versionId": 1
}
[782835:0222/182413.305509:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
[782835:0222/182413.305755:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
[02/22/22, 18:24:13:341] info: Feb-22 18:24:13.340 [SERVICE-WORKER] responding from cache https://a.slack-edge.com/bv1-9/lato-regular-d9ce515.woff2
{
  "versionId": 1
}
[...]

Notify maintainers
@mmahut

Hi,
There is an issue in old Electron versions when running under Wayland.
See:

https://github.com/NixOS/nixpkgs/pull/154003

cc @primeos @Synthetica9

Hmm odd, v4.23 only is packaged with the one electron, but presumably with differing dependent libs.
And indeed when I run it with NIXOS_OZONE_WL=  slack, it doesn't crash (but is mega fuzzy).
So the only logical conclusion is that one of the dependency libraries had a breaking change? Somewhere between Feb 12 and now?

oops I'm wrong - all 3 versions crash and sometimes they don't. So it's indeed an Electron issue. Too bad we can't rebundle Slack ourselves

Yes, if this only happens with Ozone/Wayland it's a known upstream issue: https://github.com/NixOS/nixpkgs/issues/158175 / https://github.com/electron/electron/issues/32436.

Ok, nothing we can do besides not running slack with NIXOS_OZONE_WL=1. Closing.


nixos/redmine: replace extraConfig option with settings option

Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[x] 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
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg test redmine

@GrahamcOfBorg test redmine.mysql
@GrahamcOfBorg test redmine.pgsql


Swarm nodes details should show also engine labels

Description
Node details section shows node labels but not node engine labels.
A read-only section for this kind of labels would be useful.
Steps to reproduce the issue:
information is available via
docker inspect <nodeid>
under
"Description" ->  "Engine"-> "Labels"

I've submitted a PR (https://github.com/portainer/portainer/pull/1451) which adds engine labels that had been set to the docker daemon.


Create a terraform module for kfp-operators charms

Context
According to the terraform modules organization spec, this is the first step to provide a terraform solution module. We need to create a terraform module for each charm.
What needs to get done
Create a terraform module for this charm that complies with the spec.
Definition of Done
All charms in this repository have individual terraform modules.

Closed by #572 and #573


deep equals back to shallow equals because Firebase

OfficerID to params.id comparison must be a shallow equals == instead of deep equals === because Firebase doesn't accept the deep equals condition.
Description
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

Change Status

[ ] Complete, tested, ready to review and merge
[x] Complete, but not tested (may need new tests)
[ ] Incomplete/work-in-progress, PR is for discussion/feedback

How Has This Been Tested?

[ ] Test A
[ ] Test B

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] There are no merge conflicts

KP made the adjustment in her most recent PR, so this will be closed.


Chapter 11, page 227 - typo

Then, we configure the connection to the hub. Then, we specify the URL to the hub; this should be the same as we specified in step 7.

Actually, it was step 6.

Agreed :)


Update state on message received

we receive messages here: https://github.com/olincollege/p2p-networking/blob/main/src/loop.c#L130 but we don't do anything with them. Write an implementation that appropriately updates the state to reflect the changes.

I can work on this in the next bit.


React 17 support

This module does not currently allow React 17 in it's peerDependency range. Requesting that this would be allowed.

@mihkeleidast Super simple, will take care of it now

Published under 8.1.1


Snippet Generation doesn't use CreateAsync

In the sample here: https://docs.microsoft.com/en-us/graph/api/team-put-schedule?view=graph-rest-beta&tabs=csharp, we should be using CreateAsync instead of PutAsync:
Actual:
GraphServiceClient graphClient = new GraphServiceClient( authProvider );

var schedule = new Schedule
{
	Enabled = true,
	TimeZone = "America/Chicago"
};

await graphClient.Teams["{teamId}"].Schedule
	.Request()
	.PutAsync(schedule);

Expected:
GraphServiceClient graphClient = new GraphServiceClient( authProvider );

var schedule = new Schedule
{
	Enabled = true,
	TimeZone = "America/Chicago"
};

await graphClient.Teams["{teamId}"].Schedule
	.Request()
	.CreateAsync(schedule);

AB#6992

The analysis on this one is not correct. It needs to be a PutAsync.

Reopening because there is another sample where the solution is CreateAsync. So the issue still holds, but not on the sample given in the original issue description.
Actual:
GraphServiceClient graphClient = new GraphServiceClient( authProvider );

var schema = new Schema
{
	BaseType = "microsoft.graph.externalItem",
	Properties = new List<Property>()
	{
		new Property
		{
			Name = "ticketTitle",
			Type = PropertyType.String,
			IsSearchable = true,
			IsRetrievable = true,
			Labels = new List<Label>()
			{
				Label.Title
			}
		},
		new Property
		{
			Name = "priority",
			Type = PropertyType.String,
			IsQueryable = true,
			IsRetrievable = true,
			IsSearchable = false
		},
		new Property
		{
			Name = "assignee",
			Type = PropertyType.String,
			IsRetrievable = true
		}
	}
};

await graphClient.External.Connections["contosohr"].Schema
	.Request()
	.Header("Prefer","respond-async")
	.AddAsync(schema);

Expected:
GraphServiceClient graphClient = new GraphServiceClient( authProvider );

var schema = new Schema
{
	BaseType = "microsoft.graph.externalItem",
	Properties = new List<Property>()
	{
		new Property
		{
			Name = "ticketTitle",
			Type = PropertyType.String,
			IsSearchable = true,
			IsRetrievable = true,
			Labels = new List<Label>()
			{
				Label.Title
			}
		},
		new Property
		{
			Name = "priority",
			Type = PropertyType.String,
			IsQueryable = true,
			IsRetrievable = true,
			IsSearchable = false
		},
		new Property
		{
			Name = "assignee",
			Type = PropertyType.String,
			IsRetrievable = true
		}
	}
};

await graphClient.External.Connections["contosohr"].Schema
	.Request()
	.Header("Prefer","respond-async")
	.CreateAsync(schema);

https://docs.microsoft.com/en-us/graph/api/externalconnection-post-schema?view=graph-rest-beta&tabs=csharp#request

This is no longer applicable after SDK v5.


Remove the validation of header grant_type in token auth password validation

grant_type as a header variable is not needed because it is being passed in the body of the post request.

Done


fix!: correct AppendSerializtionError typo

BREAKING CHANGE: customers need to update their code to fix build errors.
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> ☕
If you write sample code, please follow the samples format.

This breaking change will be included in the 2023 major version update.

Merge https://github.com/googleapis/java-bigquerystorage/pull/2037/ instead


Vogue - Metamorph part II completely breaks the player

http://www.a1k0n.net/code/jsxm/#morph2.xm
We have a propagation of NaN samples through the IIR filter, apparently.
Intuition is a bug in parsing >1 sample per instrument, but I haven't looked into this at all yet.

was a buggy sample; set the loop flag, but loop length is 0. naughty.


sourcekitd: using gyb to generate UIDs instead of a def file. NFC

Inspired by the infrastructure of SwiftSyntax, a gyb file can facilitate
cross-language sharing.

@swift-ci please test

@swift-ci please test source compatibility

Build failed
Swift Test OS X Platform
Git Sha - 8dd681b0a10267cb8275376ff98af7c137138fc2

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci Please clean test Linux platform

@swift-ci please test source compatibility

@swift-ci please test source compatibility

This broke unified builds. Why was generated_sourcekit_uids added to tools/CMakeLists.txt? That seems wrong when it doesn't work and overkill when it does work.

Thanks @nkcsgexi. That seems to fix unified builds.


Update instructions on how to run behave tests

This change to the README mitigates issue #1202 by instructing the user to kill the unit tests peer that makes behave fail.

Signed-off-by: Arnaud Le Hors<EMAIL_ADDRESS>

Waiting to merge until we finish discussion on PR #1164. If we merge #1164 this PR will need to be rebased.

this should be automated with a bash script that detects a running peer(s) and tears down an environment before launching the behave tests. No?

I agreed with @christo4ferris -- we need to look at the script to see if we can detect a local running peer; issue #1223

@binhn I did look at it and have a fix but in doing so I uncovered another problem with the CLI: It can't run from outside its source directory, because the paths to the config files are relative. I will open a separate issue for that and submit a fix, and then submit the fix to stop any running peer when behave is launched.
I'll close this PR as it will become irrelevant.


Added login successful popup in patient portal

Description
When user enters details , in patient portal , login successful comes
Related Issues

Closes #938

Type of PR

[X] Feature enhancement

Screenshots / videos (if applicable)
https://github.com/user-attachments/assets/ea88478b-12ab-4eb1-bac2-712ceb7cb8ed
Checklist

[X] I have gone through the contributing guide
[X] I have updated my branch and synced it with project main branch before making this PR
[X] I have performed a self-review of my code
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[X] I have commented my code, particularly in hard-to-understand areas.

@varshith257 Please assign it to me


Updating jQuery 1.7 to jQuery 3.4.1 getting error

Updating jquery version from 1.7 to  3.4.1.
While running the application  in chrome browser getting below error.
TypeError: 'undefined' is not a function (evaluating 'e.getAttribute("type")')
/js/jquery.js:2 in Pe
/jquery.js:2
/jquery.js:2 in Ie
CURRENT VERSION :Jquery-3.4.1.js

This issue tracker is for Closure Library, but your bug report indicates only JQuery and Chrome, neither of which we manage.  You'll need to provide some more information (a) about how this relates to Closure Library, and (b) with more thorough reproduction instructions - as it is, there's nothing I can do with this.  If you can reduce your problem to a minimal example (smallest possible self-contained HTML/JS that still demonstrates the error) then we'll have something to work with.  Until then, I'm closing this issue, but feel free to reopen if you can provide more information.


Currently Pull request CI test is failing

Kind (Required)

Improvement

Overview (Required)

We should fix it. And when the test failed. we should use fail status 😭

https://github.com/DroidKaigi/conference-app-2020/blob/master/.circleci/config.yml

> Task :feature:system:compileDebugUnitTestJavaWithJavac NO-SOURCE
> Task :feature:system:testDebugUnitTest NO-SOURCE

FAILURE: Build completed with 5 failures.

1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':android-base:lintDebug'.
> Could not resolve all files for configuration ':android-base:androidTestUtil'.
   > Could not resolve androidx.test:orchestrator:1.3.0-alpha02.
     Required by:
         project :android-base
      > No cached version of androidx.test:orchestrator:1.3.0-alpha02 available for offline mode.
      > No cached version of androidx.test:orchestrator:1.3.0-alpha02 available for offline mode.
      > No cached version of androidx.test:orchestrator:1.3.0-alpha02 available for offline mode.
      > No cached version of androidx.test:orchestrator:1.3.0-alpha02 available for offline mode.
      > No cached version of androidx.test:orchestrator:1.3.0-alpha02 available for offline mode.
      > No cached version of androidx.test:orchestrator:1.3.0-alpha02 available for offline mode.
      > No cached version of androidx.test:orchestrator:1.3.0-alpha02 available for offline mode.
      > No cached version of androidx.test:orchestrator:1.3.0-alpha02 available for offline mode.
      > No cached version of androidx.test:orchestrator:1.3.0-alpha02 available for offline mode.
      > No cached version of androidx.test:orchestrator:1.3.0-alpha02 available for offline mode.

Links

For now, I think it is better to disable --offline.

I'd like to fix this issue, and #706 which is also ignored in pull request CI 🙋♂

@nashcft
Thanks 👍
For now, I'll assign both issues(this PR and #706 ).
Please let me know if you have any problems🙏


URIBuilder seems not to be thread safe

We test this in case of a multi cluster setup and sometimes went the java.net.URL.factory to null instead of the original factory.
Scenario:
Thread 1
replaceURLFactory
currentFactory is original value
start create URL
Thread 2
replaceURLFactory
currentFactory == newFactory -> currentFactory = null
start create URL
Thread 1 and 2
restoreURLFactory
set URL.factory to null
Next “new URL(…)” from different call cause to load new handlers.
Best,
ebersb

Fixed in https://github.com/redisson/redisson/issues/798

Sorry, I forgot to add the used version: 3.3.2
#789 does not fix this issue. In #789 are the methods replaceURLFactory and restoreURLFactory set to synchronized. This fixed the issues with the exceptions thrown from URL.setURLStreamHandlerFactory.
This issue describes the scenario where the URL.factory is null when two concurrent threads like to create an new URL with the URLBuilder.
I try to create a pull request later.
Thanks,
ebersb

I try to create a pull request later.

OK, I'm looking forward to it


Max version for dependencies restricts freedom for consuming projects

Is your feature request related to a problem? Please describe.
Recently httpx had a security vulnerability posted that required an update to httpx==0.23.0.
openapi-python-client does not have a lot of dependencies, but httpx was one of them, and httpx was pinned to <0.23.0
The solution at the time was to bump the limit to 0.24.0
Some concerns with the 0.24.0 approach:

That only kicks the problem down the road. What if 0.23.0 also has a security vulnerability?
Projects were unable to update for ~10 days after the vulnerabilities were reported

I believe a better solution is to remove the max version for all dependencies. This allows clients the freedom to utilize the latest version, and puts less stress on the maintainers of this project to quickly respond to urgent PRs. The concern about untested versions is valid, but a test matrix can help with that.
While not a perfectly relevant example, the recommendation in the python.org documentation reflects my sentiment, notably the gaining the benefit of dependency upgrades part:

It is not considered best practice to use install_requires to pin dependencies to specific versions, or to specify sub-dependencies (i.e. dependencies of your dependencies). This is overly-restrictive, and prevents the user from gaining the benefit of dependency upgrades.

Describe the solution you'd like

Remove the max version for dependencies in setup.py and pyproject.toml jinja files
Consider: Updating the test pipelines to test known good versions, and the latest version (to ensure a dependabot PR for a new version fails if it has regressions)
Consider: Adding verbiage to the readme / license specifying known good versions

Describe alternatives you've considered

Make the max version a full major version bump ahead. For example, with httpx: <1.0.0

This has the same problem as the proposed solution:

Future versions (e.g. 0.25.0) are permitted but  are "untested" for compatibility

It also has the same problem as the current solution:

A future update is blocked by the library (e.g. 1.0.0)

Rely on consuming projects to fork the setup.py/pyproject.toml templates (using --custom-template-path) to remove the max version restriction.

This is what my project did.
I strongly prefer to NOT fork templates from openapi-python-client unless I have to. Forking puts the onus on my project team to analyze and merge any upstream changes to those templates in the future, just because I needed to change one line.

Additional context
Add any other context or screenshots about the feature request here.

Related to #629

I'm more concerned with the day-to-day usability of this project (not getting random errors at runtime from incompatible dependencies) than a small delay in updates while a Renovate PR comes in.
Ideally, security vulnerabilities are fixed in the current semver-compatible version so that there is no delay in upgrading. Hopefully, httpx will be stable (1.x) soon, so there will be less churn.


Kubeflow on Kubernetes guide: add instructions for connecting with LDAP/AD

Kubeflow on Kubernetes guide: add instructions in the arrikto section for connecting with LDAP/AD:
https://www.kubeflow.org/docs/started/getting-started-k8s/

/assign @yanniszark

/close


Queues: use case statements in FIFO control

This PR attempts to reap the rewards of #2168 by using case statements in the FIFO. Sadly something seems to be wrong... I am getting an empty par in my control instead of the equality checks I would expect. Paging @nathanielnrn to take a look. And of course please let me know if I've made a silly mistake.
In the first commit I massaged my logic to strictly check a cell, cmd, for four cases of equality. This passed all queue tests.
Then I tried to move to the case idiom in the most obvious way. Sadly I got errors about unused groups. Upon inspection of the futil code, which I am also checking in temporarily, it seems the errors are warranted: control is just an empty par!
https://github.com/calyxir/calyx/blob/a5a8616d56bb417abb88cef636cf2dca7cbadd63/calyx-py/test/correctness/queues/fifo.futil#L100-L104

The fix in 94e19ec saved the day! Thanks @nathanielnrn!

Ah yes thanks, I checked it in to show Nathaniel the issue but then forgot to get rid of it. I'll do that and then enable auto-merge


Add resolution, FOV and number of timepoints to metadata

What should be exactly reported for FoV? Is it in the sidecar json?

It's a fancy name for the number of voxels along each axis. Can be read
from the nifti header.
On Wed, Jan 18, 2017 at 2:40 PM, Oscar Esteban<EMAIL_ADDRESS>wrote:

What should be exactly reported for FoV? Is it in the sidecar json?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/mriqc/issues/335#issuecomment-273625271,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOkp_u_MYhh6BmcXXWQ0AIiIOi0Mqrfks5rTpT0gaJpZM4LnSh4
.

For the anatomical, we have the following fields as IQMs: size_[x,y,z] and spacing_[x,y,z]
For the functional, we have size_[x,y,z,t] and spacing_[x,y,z,t]

Should we move them from the regular IQMs section to the metadata dictionary? If so, please reopen this issue. Otherwise we can say this is already implemented.


Recipes not updated after tab refresh

The list of recipes is not updated after a tab refresh.

I'll take a look into this.

This should be fixed now

Is there any estimate for when a new release with this fix will be available?

Looks like 1.20 will have your fix. Please let us know if this is not working as intended.


Create MD version of "Git for Open Source Cheat Sheet" PDF

@verythorough has a PDF "Git for Open Source Cheat Sheet". We'd like to have a Markdown version that could be referenced in the Contributor Guide.
Related Issues
Issue 1038

Claiming. :) But I'm not able to find the resources directory that you referenced.

Oops, we were talking about two repos at the same time. When @cory-wc and I chatted about this, I actually had the GDISF teaching materials repo in mind, which is where she ended up PR'ing the file. You can find it here: https://github.com/gdisf/teaching-materials/blob/master/resources/git-for-open-source-cheat-sheet.md

Closing as stale and/or outdated.


Support parallel for operations, like data parallel training, model parallel training etc

What changes were proposed in this pull request?
Support ParallelFor pipeline features for each operation. Set parallel_count > 2 to start parallel operations like distributed training, distributed data processing etc. Below are features/limitations:

Suport kfp + Argo currently.
Automatically set TF_CONFIG for Tensorflow and MASTER_ADDR, MASTER_PORT for Pytorch. Yet in some cases, workers rank >=1 should wait for rank0 to start. This can be achieved by waiting rank0's TCP server port by user.
No Parameter Server style distritubed training support, since it's less popular now.
Components/Operations before and after parallelfor operation is supported

How was this pull request tested?
Unit tests are included in test_bootstrapper.py to ensure argument parallel_count is working.
TODO:

support airflow, kfp tekton
support parallel operation output file (fetch output only from rank0)
add examples to do tensorflow/pytorch/accelerate distributed training

@akchinSTC Can you please checkout this feature

@akchinSTC Can you please checkout this feature

What is the current status of this PR? I still see the work in progress tag..

@akchinSTC Can you please checkout this feature

What is the current status of this PR? I still see the work in progress tag..

This PR is ready for review now.
I removed "WIP" from the title, yet the tag seems still there.
Work under the TODO list will move on after this feature is merged.


Publish to Maven Central

### Tasks
- [ ] Publish to Maven Central during the release process
- [ ] Update readme to include updated install instructions

@toddbaert do you think you could assist us with this a bit?
I would assume that we want more steps in the release-please.yaml similar to what the java sdk does? But with ./gradlew publish instead?

I would assume that we want more steps in the release-please.yaml similar to what the java sdk does? But with ./gradlew publish instead?

Yes - but honestly the bulk of the work is handled by maven, not the workflows. Specifically, we use the nexus-staging-maven-plugin... This is because (as described here) artifacts generally are not pushed to maven central directly. Instead, they are pushed to some other repository, and then periodically exposed through Maven Central. We use OSSRH (a Nexus instance) for this. Maven central and OSSRH have quite a few requirements about artifacts, and validate conformance as part of the staging; the nexus-staging-maven-plugin handles this automatically. We already have credentials for OSSRH, and we can publish any artifact under the group id dev.openfeature.
I think you'll have to use https://github.com/Codearte/gradle-nexus-staging-plugin or maybe https://github.com/gradle-nexus/publish-plugin/ to do something similar to what we do in the java-sdk pom.xml.

👍


Problems that can be modified by smart contracts

the smart contract  , I think adding an option that can't be modified,Like f3d, if  can modify it, there will be less  to trust

Yeah, the fact that any token can spontaneously add a destroy() or freeze() method is worrying. It'd be nice if there was a way to opt-out of mutability and deploy an immutable contract.

Yes, this problem is very serious for contractual fairness. It is recommended that EOS should be resolved with the highest priority.

It is better if we have 2 mode for the contract. And the user should be know which contract can be modified which cannot.

The permissions of a contract can be adjusted to make it harder or impossible to modify.


dev.py test fails because of hypothesis "profile"

Describe your issue.
Starting from a fresh env environment, I do not seem to be able to run tests at all:
$ git clean -xdf
$ mamba env create -f environment.yml
$ mamba activate scipy-dev
$ python dev.py build     # builds OK
$ python dev.py test
💻  ninja -C /home/ev-br/repos/scipy/build -j32
ninja: Entering directory `/home/ev-br/repos/scipy/build'
[1/1] Generating scipy/generate-version with a custom command
Build OK
💻  meson install -C build --only-changed --tags runtime,python-runtime,tests,devel
Installing, see meson-install.log...
Installation OK
SciPy from development installed path at: /home/ev-br/repos/scipy/build-install/lib/python3.12/site-packages
Running tests for scipy version:1.15.0.dev0+git20240829.a7c2c54, installed at:/home/ev-br/repos/scipy/build-install/lib/python3.12/site-packages/scipy
ImportError while loading conftest '/home/ev-br/repos/scipy/build-install/lib/python3.12/site-packages/scipy/conftest.py'.
scipy/conftest.py:293: in <module>
    hypothesis.settings.register_profile(
/home/ev-br/.conda/envs/scipy-dev/lib/python3.12/site-packages/hypothesis/_settings.py:329: in register_profile
    settings._profiles[name] = settings(parent=parent, **kwargs)
/home/ev-br/.conda/envs/scipy-dev/lib/python3.12/site-packages/hypothesis/_settings.py:186: in __init__
    self, setting.name, getattr(defaults, setting.name)
/home/ev-br/.conda/envs/scipy-dev/lib/python3.12/site-packages/hypothesis/_settings.py:74: in __get__
    result = ExampleDatabase(not_set)
/home/ev-br/.conda/envs/scipy-dev/lib/python3.12/site-packages/hypothesis/database.py:84: in __call__
    return _db_for_path(*args, **kwargs)
/home/ev-br/.conda/envs/scipy-dev/lib/python3.12/site-packages/hypothesis/database.py:68: in _db_for_path
    warnings.warn(
E   hypothesis.errors.HypothesisWarning: The database setting is not configured, and the default location is unusable - falling back to an in-memory database for this session.  path=PosixPath('/tmp/.hypothesis/examples')

Reproducing Code Example
.

Error message
.

SciPy/NumPy/Python version and system information
main

And what is the default place it wants to use,  do you happen to know?

Okay, the problem was that

this was on a shared machine
/tmp/.hypothesis was not empty
and it was owned by some other user.

Clearing it fixed the issue, hence closing.
One possible UX improvement could be to change the hypothesis folder into tmpfile.mkdtemp() / ".hypothesis". Currently the failure mode is a bit mysterious and I would not have known where to look were it not for @mdhaber 's pointer (thanks!).
OTOH, the issue is probably rare enough to warrant just keeping the status quo.


Initial checkin to create nutanix image for eks-a

Issue #, if available:
Description of changes:
This PR adds necessary changes required to build eks-a image for nutanix ahv/capx using nutanix packer plugin
This PR depends on merging of https://github.com/kubernetes-sigs/image-builder/pull/982
Testing done on ubuntu vm

curl -OL https://go.dev/dl/go1.19.1.linux-amd64.tar.gz
sudo tar -C /usr/local -xvf go1.19.1.linux-amd64.tar.gz
export PATH=$PATH:/usr/local/go/bin
export GOPATH=/home/ubuntu/go

cd go/src/github.com/nutanix-cloud-native
git clone https://github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling.git
cd aws-eks-anywhere-build-tooling/
git checkout deepakm-aws-eks-anywhere-build-tooling

sudo apt update -y
sudo apt install jq unzip make ansible -y
sudo snap install yq

cd projects/aws/image-builder/

rm /home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/aws/image-builder/_output/bin/image-builder/linux-amd64/image-builder
make binaries

/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/aws/image-builder/_output/bin/image-builder/linux-amd64/image-builder build --help
This command is used to build EKS Anywhere node images

Usage:
  image-builder build --os  --hypervisor  [flags]

Flags:
      --force                    Force flag to clean up leftover files from previous execution
  -h, --help                     help for build
      --hypervisor string        Target hypervisor EKS-A node image
      --nutanix-config string    Path to Nutanix AHV Config file
      --os string                Operating system to use for EKS-A node image
      --release-channel string   EKS-D Release channel for node image. Can be 1-20, 1-21, 1-22 or 1-23 (default "1-23")
      --vsphere-config string    Path to vSphere Config file

Global Flags:
  -v, --verbosity int   Set the log level verbosity

Create following file with details

cat nutanix-connection.json
{
    "nutanix_cluster_name": "",
    "image_name": "eksa-dm-image-ubuntu-2004-kube-v1.22",
    "source_image_name": "ubuntu-20.04-server-cloudimg-amd64",
    "nutanix_endpoint": "",
    "nutanix_insecure": "true",
    "nutanix_port": "9440",
    "nutanix_username": "",
    "nutanix_password": "",
    "nutanix_subnet_name": ""
}

Download local copy of upstream image-builder repo

cd ~/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder
git clone https://github.com/kubernetes-sigs/image-builder.git

/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/aws/image-builder/_output/bin/image-builder/linux-amd64/image-builder build --os ubuntu --hypervisor nutanixahv --nutanix-config ./nutanix-connection.json --release-channel 1-22

/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/aws/image-builder/_output/bin/image-builder/linux-amd64/image-builder build --os ubuntu --hypervisor nutanixahv --nutanix-config ./nutanix-connection.json --release-channel 1-22
Creating builder config
2022/09/27 18:18:33 Using repo checked out from code commit
2022/09/27 18:18:33 Executing command: /usr/bin/git -C /home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling rev-parse --show-toplevel
2022/09/27 18:18:33 Initiating Image Build
 Image OS: ubuntu
 Hypervisor: nutanixahv
2022/09/27 18:18:33 Executing command: /usr/bin/bash -c make -C /home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder local-build-nutanix-ubuntu-2004
make: Entering directory '/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder'
(cd image-builder && /home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/build/lib/wait_for_tag.sh ef9fed11d164c58dcb9e56699c56b0fe953f40d9)
Checking for tag ef9fed11d164c58dcb9e56699c56b0fe953f40d9...
ef9fed11d164c58dcb9e56699c56b0fe953f40d9
Tag ef9fed11d164c58dcb9e56699c56b0fe953f40d9 exists!
git -C image-builder checkout -f ef9fed11d164c58dcb9e56699c56b0fe953f40d9
Note: switching to 'ef9fed11d164c58dcb9e56699c56b0fe953f40d9'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at ef9fed11d Merge pull request #982 from nutanix-cloud-native/nutanix_imagebuilder
touch image-builder/eks-anywhere-checkout-ef9fed11d164c58dcb9e56699c56b0fe953f40d9
git -C image-builder config user.email<EMAIL_ADDRESS>git -C image-builder config user.name "Prow Bot"
git -C image-builder am --committer-date-is-author-date /home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/patches/*
Applying: Add goss validations for EKS-D artifacts
Applying: Install containerd from apt for Ubuntu
Applying: Output vsphere builds to content library instead of exports
Applying: Create /etc/pki/tls/certs dir as part of image-builds
Applying: Add etcdadm and etcd.tar.gz to image for unstacked etcd support
Applying: Additional EKS-A specific goss validations
Applying: Tweak Product info in OVF
Applying: Add support for RHEL 8 RAW image builds
Applying: Support crictl validation from input checksum
make -C image-builder/images/capi deps-nutanix
make[1]: Entering directory '/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/image-builder/images/capi'
hack/ensure-ansible.sh
Starting galaxy collection install process
Nothing to do. All requested collections are already installed. If you want to reinstall them, consider using `--force`.
hack/ensure-packer.sh
packer_1.8.3_linux_amd64.zip: OK
Archive:  packer_1.8.3_linux_amd64.zip
  inflating: packer
'packer' has been installed to /home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/image-builder/images/capi/.local/bin, make sure this directory is in your $PATH
hack/ensure-goss.sh
Right version of binary present
make[1]: Leaving directory '/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/image-builder/images/capi'
build/setup_packer_configs.sh 1-22 nutanix-ubuntu ubuntu s3://my-s3-bucket /home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/-/artifacts/1-22/nutanix-ubuntu/ubuntu 1-21 latest image-builder/images/capi
+ set -o errexit
+ set -o nounset
+ set -o pipefail
+ RELEASE_BRANCH=1-22
+ IMAGE_FORMAT=nutanix-ubuntu
+ IMAGE_OS=ubuntu
+ ARTIFACTS_BUCKET=s3://my-s3-bucket
+ OVA_PATH=/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/-/artifacts/1-22/nutanix-ubuntu/ubuntu
+ ADDITIONAL_PAUSE_IMAGE_FROM=1-21
+ LATEST_TAG=latest
+ IMAGE_BUILDER_DIR=image-builder/images/capi
+ CI=false
+ CODEBUILD_CI=true
+ DEV_RELEASE=false
+ [[ false == true ]]
+ [[ true == true ]]
+ DEV_RELEASE=true
+++ dirname build/setup_packer_configs.sh
++ cd build/..
++ pwd -P
+ MAKE_ROOT=/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder
+ source /home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/../../../build/lib/common.sh
++++ dirname /home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/../../../build/lib/common.sh
+++ cd /home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/../../../build/lib/
+++ pwd -P
++ BUILD_ROOT=/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/build/lib
++ source /home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/build/lib/eksd_releases.sh
+++++ dirname /home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/build/lib/eksd_releases.sh
++++ cd /home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/build/lib/../../
++++ pwd -P
+++ REPO_ROOT=/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling
+++ LATEST_RELEASE_BRANCH=
+++ PROD_DOMAIN=distro.eks.amazonaws.com
+++ DEV_DOMAIN=eks-d-postsubmit-artifacts.s3.us-west-2.amazonaws.com
+++ RELEASE_YAML=()
+++ declare -A RELEASE_YAML
+ source /home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/../../../build/lib/eksa_releases.sh
++ BUNDLE_MANIFEST=()
++ declare -A BUNDLE_MANIFEST
+ build::eksd_releases::load_release_yaml 1-22
+ local -r release_branch=1-22
+ local -r echo=true
+ oldopt=ehuxB
+ set +o nounset
+ set +x
apiVersion: distro.eks.amazonaws.com/v1alpha1
kind: Release
...
..
.
++ echo https://distro.eks.amazonaws.com/kubernetes-1-22/kubernetes-1-22-eks-10.yaml
+ export EKSD_MANIFEST_URL=https://distro.eks.amazonaws.com/kubernetes-1-22/kubernetes-1-22-eks-10.yaml
+ EKSD_MANIFEST_URL=https://distro.eks.amazonaws.com/kubernetes-1-22/kubernetes-1-22-eks-10.yaml
+ echo https://distro.eks.amazonaws.com/kubernetes-1-22/kubernetes-1-22-eks-10.yaml
+ envsubst '$CNI_VERSION:$ETCD_VERSION:$ETCD_SHA256:$ETCDADM_VERSION:$PAUSE_IMAGE:$CNI_HOST_DEVICE_SHA256'
+ envsubst '$EKSD_NAME'
+ '[' nutanix-ubuntu = ova ']'
PACKER_FLAGS="-force" PACKER_LOG=1 PACKER_LOG_PATH=/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/-/artifacts/1-22/raw/ubuntu/packer.log PACKER_VAR_FILES="/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/_output/1-22/nutanix/ubuntu/config/kubernetes.json /home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/_output/1-22/nutanix/ubuntu/config/common.json /home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/_output/1-22/nutanix/ubuntu/config/cni.json /home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/_output/1-22/nutanix/ubuntu/config/additional_components.json " \
	make -C image-builder/images/capi build-nutanix-ubuntu-2004
make[1]: Entering directory '/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/image-builder/images/capi'
Makefile:168: warning: undefined variable 'FOREGROUND'
Makefile:175: warning: undefined variable 'ON_ERROR_ASK'
Makefile:184: warning: undefined variable 'SSH_PRIVATE_KEY_FILE'
Makefile:188: warning: undefined variable 'SSH_PUBLIC_KEY_FILE'
Makefile:194: warning: undefined variable 'DEBUG'
hack/ensure-ansible.sh
Starting galaxy collection install process
Nothing to do. All requested collections are already installed. If you want to reinstall them, consider using `--force`.
hack/ensure-packer.sh
hack/ensure-goss.sh
Right version of binary present
packer init packer/nutanix/config.pkr.hcl
packer build -var-file="/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/image-builder/images/capi/packer/config/kubernetes.json"  -var-file="/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/image-builder/images/capi/packer/config/cni.json"  -var-file="/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/image-builder/images/capi/packer/config/containerd.json"  -var-file="/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/image-builder/images/capi/packer/config/ansible-args.json"  -var-file="/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/image-builder/images/capi/packer/config/goss-args.json"  -var-file="/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/image-builder/images/capi/packer/config/common.json"  -var-file="/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/image-builder/images/capi/packer/config/additional_components.json"  -force -color=true -var-file="packer/nutanix/nutanix.json" -var-file="/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/image-builder/images/capi/packer/nutanix/ubuntu-2004.json" -var-file="/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/_output/1-22/nutanix-ubuntu/ubuntu/config/kubernetes.json"  -var-file="/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/_output/1-22/nutanix-ubuntu/ubuntu/config/common.json"  -var-file="/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/_output/1-22/nutanix-ubuntu/ubuntu/config/cni.json"  -var-file="/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/_output/1-22/nutanix-ubuntu/ubuntu/config/additional_components.json"  packer/nutanix/packer.json
nutanix: output will be in this color.

==> nutanix: Creating Packer Builder VM on Nutanix Cluster.
...
..
.
==> Builds finished. The artifacts of successful builds are:
--> nutanix: ubuntu-2004-kube-v1.22.12
--> nutanix: ubuntu-2004-kube-v1.22.12
make[1]: Leaving directory '/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder/image-builder/images/capi'
make: Leaving directory '/home/ubuntu/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere-build-tooling/projects/kubernetes-sigs/image-builder'
2022/09/27 20:40:08 Image Build Successful
 Please find the image uploaded under Nutanix Image Service with name eksa-dm-image-ubuntu-2004-kube-v1.22
2022/09/27 20:40:08 Build Successful. Output artifacts located at current working directory

/ok-to-test
/hold for upstream PR to be merged

waiting for https://github.com/aws/eks-anywhere-build-tooling/pull/1313 to get merged before current one

/assign @abhinavmpandey08

/assign @vignesh-goutham

/retest-required


Add installation instructions for Homebrew

Pending merge of Homebrew/homebrew#37854

The formula was merged in, so this should be good to go.

:+1:


Rebasing Focus Areas

The WG meeting today recentered on working from the Focus Areas down (notes available here). With that in mind, there are a few takeaways:

The current proposals for Focus Areas of Reputation and Economics (#84 & #87) aren't quite capturing the intention of audience's perception of value since interpretations of value often include elements of both.
@sgoggins proposed areas aligned to audience that seem to be a good start for us:

Community Value
Social Value
Organizational Value
Individual Value

@germonprez will facilitate the next WG meeting focused on exploring the goals, questions, and metrics associated with the list above.

Have feedback? Add comments or thoughts to the meeting notes for next time.
This issue can be closed by the PR that adds Focus Areas to the repository.

We've completed this effort with #93.


Prepare 2.7.0 release

@iwysiu can you also downgrade the grafana-plugin-sdk-go to the previous version used to avoid any issue like https://github.com/grafana/athena-datasource/issues/233 ?
https://raintank-corp.slack.com/archives/C01LVB0CYTW/p1683130735011179

Athena data source had no issue with the freshly-released grafana-plugin-sdk-go v0.161.0 -- sorry it's a pain, but would you use that instead?


Refactor NWM storage structure

Moved from email exchanges
Drew:
We are reviewing and rethinking the way how we store the National Water Model (NWM) data, and we would like to have your comments/suggestions from computer science perspective.
There is a folder mounted on our apps server at /projects/water/nwm/data/analysis_assim/ for permanently storing a specific type of NWM daily output files. The archiving procedure started in 2016 June, and currently it contains 115,746 files with 288 new files being added per day.
We established this workflow about 2 years ago as this would allow our Tethys app to easily access multiple local files over a random date range (say 2017-01-01 to 2017-05-31) from within the same folder. Also, this folder and its contained files are registered into NWM Zone as IRODs resources for users to access from outside of Tethys app.
Since more files are being piled up every day, this started to make us concerned:

We didn’t notice any obvious performance deterioration in our app yet. However, we found Linux command "ls" takes about 10s, and iCommand "ils" may take around 30s for the first run.

Is there any limit on how many files can be stored in one folder on Linux or on IRODs?

What is a better way to store these files as a long term solution?

Any comments/thoughts/suggestions would be appreciated.

Hong:
I’ll defer this to Michael and Ray, but agreed putting thousands of files in the same folder will have performance impact even though theoretically the number of files in a folder in ext4 file system on linux is limitless. Check out:
https://serverfault.com/questions/98235/how-many-files-in-a-directory-is-too-many-downloading-data-from-net
and
https://groups.google.com/forum/#!topic/irod-chat/iIGe9hs0QnE
I think over the long term it will be better to put files in different folders, e.g., based on date range, and as long as folder names are named in an agreed-upon scheme, it should not be too difficult to go into different sub-folders to retrieve files that fall into a specific date range…

Tony:
I think it’s a better idea to restructure this directory sooner rather than later.  The bigger the directory becomes, the more difficult it will become to use.  I suggest we follow a similar pattern to the medium range directory, but add year and month aggregations.  For example:
2018
— 01
— 20180101
(f003 - f240)
— nwm.t00z.medium_range.channel_rt.f003.conus.nc
— nwm.t00z.medium_range.land.f003.conus.nc
— nwm.t00z.medium_range.reservoir.f003.conus.nc
— nwm.t00z.medium_range.terrain_rt.f003.conus.nc
(f003 - f240)
— nwm.t06z.medium_range.channel_rt.f003.conus.nc
— nwm.t06z.medium_range.land.f003.conus.nc
— nwm.t06z.medium_range.reservoir.f003.conus.nc
— nwm.t06z.medium_range.terrain_rt.f003.conus.nc
     — …
     — …
 — 20180102
 — 20180103
 — …

— 02
— …
— 11
— 12

Dan:
I agree with Hong. I'm concerned about the length of time for an ls command in that folder. Drew can you propose a new folder structure that would potentially make ore sense? - Dan
(cc'ing Dave since he likes to keep his finger on the pulse...)

Mark:
Hong's suggestion of datetime based folders seems to make sense, I concur. Just consider the highest number of files in each folder:
4 digit year: /2008/ - 2000 possible values, probably under 100 in practice
2 digit month: /2008/12/ - 12 possible values
2 digit day: /2008/12/31 - 31 possible values
Then you can put each model output in there by day. If there's still too many you can move to hours (24 possible) and minutes (60 possible)

Michael:
From a machine perspective you’re realistically not going to encounter issues with the number of files at any particular directory level until you get into the billions.
From a human readable perspective and UI tooling, you’ve probably already surpassed what is “comfortable” to interact with.
The analysis_assim, fe_analysis_assim and forcing_analysis_assim directories should likely be reformatted to resemble the rest of their friends in the nwm archive. Except that the date directories will be going back to 20160609, and up until present day.
Example: short_range data
— —
ls /projects/water/nwm/data/short_range/ -1
20180114
20180115
...
20180222
20180223
— —
This formatting already applies to: other nwm friends
— —
forcing_medium_range
forcing_short_range
long_range
medium_range
short_range
usgs_timeslices
— —
And the nomads directory which is a full 40 day rolling copy of the source nwm files looks like:
— —
$ ls /projects/water/nwm/data/nomads/ -1
nwm.20180114
nwm.20180115
...
nwm.20180222
nwm.20180223
— —
Where each subdirectory of the dated nomads data is:
— —
$ ls /projects/water/nwm/data/nomads/nwm.20180222 -1
analysis_assim
forcing_analysis_assim
forcing_medium_range
forcing_short_range
long_range_mem1
long_range_mem2
long_range_mem3
long_range_mem4
medium_range
short_range
usgs_timeslices
— —
At present the outer representation of the nwm data directories (what Tethys interacts with) are full copies of what is in the nomads directory, with the exception of the analysis and assimilation related data as that extends back to the beginning of the project. There are opportunities here for symbolic links that would reduce the number of copies on disk, or optionally simply keep everything in source nomads format and drop off the non-analysis and assimilation data as the rolling window exceeds the drop off date.
The more immediate question in my mind is what are the limits of data structure that the Tethys apps can interact with in an efficient way?

Drew:
Thanks for all your inputs. I will be moving these conversations to a github issue on HydroShare repo. Although we haven't finally decided what the new folder structure would be, a few things are worthy taking into considerations.

Any change to the current storage structure will immediately break existing app functionalities (partially or entirely).

As NWM archive is too big, it seems hard or impossible to make a full clone of current data to keep existing app in service while we work on re-structuring the storage and changing app accordingly.

Symbolic links allows us to have different patterns of folder structure co-exist by pointing to only one copy of data, but I am not sure the symbolic links are still valid once getting mounted into containers.

looking at the recent discussions regarding the NWM Viewer this seems to be not relevant anymore, please re-open if I'm mistaken.


path/filepath: Glob malfunction under Windows when pattern matching is used

Here's a sample code to illustrate the problem which stems from a case sensitive string matching somewhere in the code:
package main

import (
	"fmt"
	"path/filepath"
)

func main() {
	a,_ := filepath.Glob("c:\\users\\*\\appdata")
	fmt.Println(a)  //this prints []
	b,_ := filepath.Glob("c:\\users\\*\\AppData")
	fmt.Println(b)  //this prints [c:\users\Default\Appdata ...]
}

Because file and directory names in Windows are case insensitive therefore this is a bug.
Please note that before the asterisk(*) the path name does not have to match case but after the asterisk it doesn't provide any results if the case doesn't match.

Dup of #5441?
Alex

Possibly. But that one is an old issue (over 2 years old) which should have been fixed a long time ago. I think we should keep this open to have more chance that this issue gets fixed.

@laszlothewiz that's not how our process works. If you want to help get the problem fixed, you'd best update the existing issue #5441 add some more information and propose a fix (or track down @alexbrainman's old proposed fix). Keeping duplicate issues open doesn't help anyone, and FWIW all else being equal we're more likely to fix an old issue than a new one.


common/LinkButton.tsx: Manage tabIndex property correctly

Closes #1327 #1328
Motivation and context
Closing the above mentioned issues, thus improving the accessibility.
Testing
Steps to test
Navigate with the TAB key to the campaign card buttons.
Check if there is a invisible tabbable element.
Check if disabled button can receive focus-visible property.

@sashko9807 You commited without formatting, likely something pre-commit hooks went wrong and prettier is erroring out.


Error when i get data for index

Hi !!
I have this error when i get info to index Benefits
"message": "json_decode(): Argument #1 ($json) must be of type string, bool given",
"exception": "TypeError",
"file": "/var/www/html/vendor/zing/laravel-scout-opensearch/src/Engines/OpenSearchEngine.php",
"line": 170,
The instance to open search is in docker and this is running

And the API Laravel comunicated with this container

i configure the scout.php

and

Thanks

In fact, this project is for Alibaba Cloud OpenSearch Service, and the version for OpenSearch Project is still in test. See https://github.com/zingimmick/laravel-scout-opensearch/pull/57
I'm very sorry for the confusion caused by the project name, I'll consider renaming this project later to avoid ambiguity.


[Review content] - Update About page to include information on guilds and previous usage of term 'SEGAS'

Which content do you think should be reviewed?
About page
Why do you think we should review this?
Could give more information to people viewing site for the first time
Do you have a suggestion for how this could be improved?
Brief explanations of SEGAS (as acronym) and guilds
Please confirm the below

[x] I have checked through the issues on the repository and don't think this has already been suggested

We can probably use some of the information from the CONTRIBUTING doc for this


Default volume levels for Windows 10

Hi,
The table in the page does not provide default volume levels for Windows 10. Please update.
Thanks.

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

ID: b8a38021-98c1-f7a4-50d1-231230d460d0
Version Independent ID: 1d277dd0-454f-7069-2763-2bf4797417ad
Content: Default Audio Volume Settings - Windows drivers
Content Source: windows-driver-docs-pr/audio/default-audio-volume-settings.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @DOMARS
Microsoft Alias: domars

@guliteb - Thanks for pointing out this gap in our docs. The db and level volume settings remain the same from Windows 8. I added a new row to document these settings for Windows 10 in this topic. Thanks for your interest in improving the Windows driver documentation!


Add left_join, right_join, inner_join and outer_join functionalities

Not ready for merging. Need to understand how to write unit tests.

Chatted in person. Will have different way to implement.


Improvements

This PR includes

scrolling flag removing
items requesting never ends (https://github.com/Hill30/NGScroller/issues/64) fix
some minor refactoring
a new adapter introducing

The last one is a complex issue, it includes a detailed demo:
http://rawgit.com/dhilt/NGScroller/improvements/src/examples/adapter.html

It would be better to change minor version of the product after that I suppose.
To v1.1.0.


Packaging

This generates npm packages when a build runs. It'll first attach it as an artifact to the build job (so you could download and install it from the file) but it also pushes to GitHub Packages, so you can install it from there.
The package is versioned using the current semver of the package.json but then adds a prerelease of -ci-<BuildId> so it sits outside of the standard semver process being used.

@manekinekko this helps speed up the dev cycle. I've found that it can be really painful to run from source, but now it can be easily installed


Support configure() without a component=...

Current Situation
All reactpy.backend.*.configure(...) calls currently require a component. However, our main method telling users how to use ReactPy should involve using our template tag.
Proposed Actions
Either remove component as a parameter, or make it an optional parameter.
Frankly, the current method of artificially setting up an index route is useless or gimmicky at best.

Frankly, the current method of artificially setting up an index route is useless or gimmicky at best.

Can you explain the problems with the current implementation bit more?

Right now there is a lot of necessary browser features that can't be done with ReactPy.
The configure() assumes you're making a completely new project, and we are deciding for the user that it's a SPA. But, our SPA support isn't really that useable given that we don't have Python support for

File Uploads
Browser cookies
Sessions
IndexDB
WebSQL
Push Messaging
Background Sync
Forward Cache
Local Storage
Service Workers
Web manifests

Practically everything under Chrome Devtools -> Application is going to need native integration if we want to advertise SPAs as a realistic dev scenario. Getting there is going to require a lot of dev hours, so we won't reach it quickly.
Right now, the only realistic scenarios we can easily support is embedding within existing projects. And unfortunately, mounting a configure(... , componet = ...) at the index route severely clashes with that concept. The template tag is needed so we don't awkwardly force users to write their own JS clients with unpinned ReactPy versions.

Closing this in favor of #1110


Duplicate paragraph

First 2 paragraphs are duplicates. One of them needs cleaning up.

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

ID: be8aa07f-6145-c3a7-b527-aa3d4931d87a
Version Independent ID: 442e92d2-93bb-addc-de9b-4817d428f355
Content: Grant users access - Power Platform
Content Source: power-platform/admin/grant-users-access.md
Service: power-platform
GitHub Login: @jimholtz
Microsoft Alias: jimholtz

@cesar-younes
Thanks for bringing this to our attention. This will be corrected.


In util tests, custom asserters are not curried with context.

So I've got a custom assertion. In an integration test I use it like this:
assert.foo('bar', 'baz');

But in a util test, I have to invoke my custom assertion like this:
assert.foo(null, 'bar', 'baz');

I assume that in util tests the custom assertion function is not being curried with context.

@lolmaus I wasn't sure how best to handle this case or how to work around it within unit tests. Ideally we could support both use cases without having the null placeholder argument. I'm open to all ideas on how to get around this.

Only some custom assertions need access to the context. Have user explicitly pass the context when necessary.

Even for stuff like assert.false(bool)?

For example, I've just implemented an assert.almostEqual() assertion for floats. Why would I want to pass a context into it?

Okay, I figured it out.
The official unit test example demonstrates this usage:
module('Unit | model | foo', {
  beforeEach: function() {
    assertionInjector();
  },
});

It makes sense because unit tests have no application instance to pass.
But it results in an unwanted argument in ALL custom assertions that use arguments:
test("bar", function(assert) {
  const model = this.subject();
  assert.baz(null, model.bar()); // <- unwanted first argument
});

I dared to look into the subj's source and found that the context argument is actually never used:
      if (context) {
        args.unshift(context);
      }

https://github.com/dockyard/ember-cli-custom-assertions/blob/v0.0.4/test-support/assertions.js#L41-L43
So my issue can be resolved with:
module('Unit | model | foo', {
  beforeEach: function() {
    assertionInjector("just pass whatever arg here, it's not used anyway");
  },
});

test("bar", function(assert) {
  const model = this.subject();
  assert.baz(model.bar()); // <-- yay, no unnecessary arguments!
});

I'll keep this open as a reminder to properly document the matter.
I'm not providing my own README edit as my previous edit was neither accepted nor given specific directions to make it acceptable.

Ah, sorry, I read unshift as shift`.
I believe this nuisance can be resolved by reverting this commit: https://github.com/dockyard/ember-cli-custom-assertions/commit/5a5b3ebc88ad02131218faf4ffee7e1ce29be786#diff-2c881d7ac1eb00900cc9af8de52152aeL41
I. e. unshift unconditionally.
Why was the condition introduced in the first place?

What about integration tests? How would I use, for example, the contains assertion from the README in an integration test?

I figured it out: just pass this to assertionInjector:
import { assertionInjector } from 'dummy/tests/assertions';

moduleForComponent('my-component', 'Integration | Component | my component', {
  integration: true,
  beforeEach() {
    assertionInjector(this);
  }
});

I assume the best practice would be to pass this in ordinary unit tests as well.

@lastobelus thanks!


Adding Fallback Value to CSS var results in no change to CSS Image

Describe your problem and - if possible - how to reproduce it
Basic CSS: Attach a Fallback value to a CSS Variable, when you add black as a Fallback Value to var(--penguin-skin) there is no change in the CSS Penguin image.  The last note in the exercise states "This style will be applied because of a typo in the variable name." however there is no typo in the variable name.  if I add a typo to the variable name the penguin top and bottom background change to black.
I am not sure if the intent is for the penguin background to change black or to have the user add a typo to the css var name to have the penguin background change black.  Maybe a clarification on the instructions would be helpful.  Thank you.
Add a Link to the page with the problem
https://learn.freecodecamp.org/responsive-web-design/basic-css/attach-a-fallback-value-to-a-css-variable
Tell us about your browser and operating system

Browser Name: Safari
Browser Version:
Operating System: macOS High Sierra ver 10.13.4

If possible, add a screenshot here

@emh1010 Thanks for reporting the issue. If I recall correctly, the variable was --pengiun-skin. It had a typo on purpose, as stated in the description, but probably someone overlooked and corrected it.
@moT01 I believe you are the author of this section. Can you confirm the typo thing?

@huyenltnguyen yes, there is supposed to be a typo in the variable name for those two classes - the way it is on the live site now is correct, I believe - but it looks like one of the tests isn't passing unless the typo is corrected


Create a tag when releasing is performed

It would be nice if a tag could be created when a release is performed

THis should be included in https://github.com/fabric8-launcher/ngx-launcher/issues/324


When Storymode song ends the game softlocks

Describe your problem here.
Basically, I broke something in PlayState.hx and I have no idea what the hell I did to break it
TableBroken.zip
How can I fix this
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
Yes, I edited almost every .hx file

I found the problem, something in the lua script is stopping the song from ending


Fixed the issue in JSP for "<>"  operator since internal Tomcat does not allow to set the JDK version for 1.7

Changes added to identity-framewor with https://github.com/wso2/identity-framework/pull/12/files


biblatex support

author:

book class template uses the natbib package by default.

We want to use the biblatex package (with biber instead of bibtex)
instead because it is much more flexible and modern,
and it supports separate bibliographies in each chapter.

(anyway, it's not a problem for me, because my solution is to just ignore the references.tex file and insert bibtex instead. I'm just mentioning it because the way the references.tex file is set up is probably misleading/frustrating for beginners).
@katyhuff : Could you tell me what files do I need to change so that I can use bibtex too ?

It's been a few years now, but....
option 1: Edit References.tex
Instead of the content currently in references.tex, include the following:
\chapter*{References}
\end{frontmatter}

  \bibliographystyle{dinat}
  \bibliography{2018-hybrid-book}

option 2: Ignore References.tex
Alternatively, in the book.tex file, replace:
\Backmatter
  \include{references}
\end{document}

with:
\Backmatter
  \bibliographystyle{plain}
  \bibliography{2018-hybrid-book}
\end{document}

Either way
In the new scenario in both cases, you reference a .bib file from whence to source the bibliography. You'll want to create such a .bib file. Name it whatever you put as the name (where I have 2018-hybrid-book, put the name of your file.). I create my .bib files automatically with a reference manager. I use Zotero, but you can use anything (mendeley, endnote, refworks, whatever...)
Additionally, you'll need to compile the document with bibtex included, like so (or similar):
latex book
bibtex book
latex book
latex book
dvipdf book

or, alternatively
pdflatex book
bibtex book
pdflatex book
pdflatex book

@katyhuff  Agreed. I have updated the template slightly. Basically I commented out the reference section. Now author can choose what to use:  bibtex, biblatex or plain latex.
Thanks for reminding me about the issue.

Excellent, nice work! This issue can probably be closed then! (I don't have permission to do that, so it'll be up to you @dgalcius )

The natbib package is moved from the class to the .tex template file. This way author can replace natbib with biblatex if needed.


Verify RS256 JWT signature without private key

Many tools online only require the public key to verify the JWT signature
example: https://developer.pingidentity.com/en/tools/jwt-decoder.html
In the documentation section of this addon to Verify RS256 JWT:
var private_key: CryptoKey = CryptoKey.new()
var public_key: CryptoKey = CryptoKey.new()
private_key.load_from_string("<your private key PEM string>", false)
public_key.load_from_string("<your public key PEM string>", true)

var jwt: String = "<a jwt>"
var jwt_algorithm: JWTAlgorithm = JWTAlgorithmBuilder.RS256(public_key)
var jwt_verifier: JWTVerifier = JWT.require(jwt_algorithm) \
    .with_claim("id","someid") \
    .build() # Reusable Verifier
if jwt_verifier.verify(jwt) == JWTVerifier.JWTExceptions.OK :
	print("Verified!")
else:
	print(jwt_verifier.exception)

How can I skip verifying the algorithm here JWT.require(jwt_algorithm) ? I only need to verify the signature and claims.

If you just want to verify, you can skip the private_key initialization as well. Then, you can use the verify_signature() method to verify only the signature, and verify_claim_values() to verify all or some of the claims.
# verify signature
if jwt_verifier.verify_signature(JWTDecoder.new(jwt)):
	print("Valid!")
else:
	print(jwt_verifier.exception)

# verify specific claims
if jwt_verifier.verify_claim_values(JWTDecoder.new(jwt), { my_claim = "my_value" }):
	print("Valid!")
else:
	print(jwt_verifier.exception)

# verify claims previously provided to the verifier with `with_claim()` method
if jwt_verifier.verify_claim_values(JWTDecoder.new(jwt), jwt_verifier.claims):
	print("Valid!")
else:
	print(jwt_verifier.exception)

You can't skip the algorithm verification, since you need to provide the algorithm that was used to generate your JWT. If some tools online don't ask you the algorithm, it's because they are taking it from the JWT header, but it's always best to provide the algorithm to the verifier.

By the way jwt_verifier.verify() does all of that for you plus some other verification, so I suggest you to just use that instead :)
Take a look here

Thank you for your help,

JWT.require() doesn't "verify" the algorithm, but asks what algorithm should be used to verify the signature

jwt_verifier.verify() does all of that for you plus some other verification, so I suggest you to just use that instead

Yes, what I meant to say is that I need to provide public and private keys to even get that jwt_verifier variable
var jwt_algorithm: JWTAlgorithm = JWTAlgorithmBuilder.RS256(public_key, private_key)
var jwt_verifier: JWTVerifier = JWT.require(jwt_algorithm) \
    .with_claim("id","someid") \
    .build() # Reusable Verifier

jwt_algorithm variable requires public and private keys... and JWT.require() requires jwt_algorithm
In other words, cannot skip the private_key initialization if I where to simply call jwt_verifier.verify() since jwt_verifier needs a private key.. I hope my issue made sense.

Oh yes, that makes sense now, but you can just set the private_key = null or just not loading any key, and verification will work anyway :)

Okay, thanks for the clarification. It is working now :)


A bunch of fixes

Instagram link below the About section was broken along with LinkedIn.

Removed the LinkedIn link and replaced the instagram one working link from the contact section.

Made all links open in new tab.

removed the empty projects

made the background of contacts form white to make it more readable and made the corners rounded.

increased the speed of typing animation on the home section

@ahsankhan26 Kindly resolve the conflicts and provide screenshots pointing the changes


Solve Largest Square Problem in java

Is your feature request related to a problem? Please describe.
Given an m x n binary matrix filled with 0's and 1's, find the largest square containing only 1's and return its area.
Describe the solution you'd like
dynamic programming array
Describe alternatives you've considered
dynamic programming array and then Traverse through the matrix
Additional context
Assign my contribution under SSOC'23

Don't raise issues for leetcode problems


Remove ArchGDAL.Table

For reasons unknown to me, we can no more access the field inside the row by the symbol.
To go around this, I first find out the index of the field which contains the key and then get the field using getfield method.
@yeesian ArchGDAL.getfield(Feature, i) seems to be missing in the documentation.
I tried to run the code and it seems to work fine, please have another look @juliohm.

Thanks for the ping! Yeah the implementation in this PR is correct for ArchGDAL v0.7, and the following test is failing:
https://github.com/JuliaGeo/GADM.jl/blob/f04d7c2d4c63ac9ffa14927b5f1404ae8f2a98c3/test/GADM.jl#L50
The tests will be more robust when they're testing for behavior rather than implementation (i.e. knowledge of the return type), so I think it's better to remove that line/test altogether, since it might be subject to yet another change in pending the resolution of https://github.com/yeesian/ArchGDAL.jl/issues/223.

@zerefwayne could you please remove that test as pointed out by @yeesian ?

ping @zerefwayne

Thank you @zerefwayne !


Grasplan base module

I think we should create a base module that handles some common initialization for the place, pick and insert actions. For example each actions needs the interfaces to MoveIt!:
https://github.com/DFKI-NI/grasplan/blob/f6280970b1134fef316e675a7e3bec09999ea3c9/src/grasplan/place.py#L113-L125
https://github.com/DFKI-NI/grasplan/blob/f6280970b1134fef316e675a7e3bec09999ea3c9/src/grasplan/pick.py#L88-L104
a tf client etc, ....

very good idea! we could do that with inheritance, having a (singleton?) base class that initializes the necessary modules.


Profile wrapup

Closes #172

Here is what I ended up doing with Weirs.

@aerispaha I force pushed the reduced lines... didn't know you were working on it :)

pushed the reduced lines... didn't know you were working on it

awesome, thanks! love that commit message btw :)

@aerispaha Do you want to drop appveyor soon?

@bemcdonnell re: appveyor, yes I would like to drop appveyor soon. Just need to port over the deploy logic such that we can automatically post new versions to PyPI on tagged versions

let's raise that in a separate issue.

@aerispaha happy to help!

let's raise that in a separate issue.

Here it is! #175


Alternative approach

This is a complete re-thinking of the library, by taking advantage of the new large-records infrastructure for routing GHC generics to LR generics.
This is an experiment: first signs are good, but we'll need to construct a full example before I can really be sure that this will work out.
Depends on https://github.com/well-typed/large-records/pull/9 as well as a patch to beam-core to export some classes (GZipTables, GTableSkeleton, and others).

If this works, this obsoletes PR #2 and #3.

Depends on well-typed/large-records#9 as well as a patch to beam-core to export some classes (GZipTables, GTableSkeleton, and others).


PropTypes via the main React package is deprecated

warning.js:36 Warning: Accessing PropTypes via the main React package is deprecated. Use the prop-types package from npm instead.
https://facebook.github.io/react/blog/2017/04/07/react-v15.5.0.html
New release version of React (15.5.0) add new Warning that React.PropTypes will be deprecated soon. You must use the prop-types package from npm.

Notice that the next branch has been migrated to the prop-types package.
The master branch isn't actively maintained, any help is welcomed.

@oliviertassinari I have the same issue. What branch should we use ? 'next' branch doesn't seem to work perfectly (missing svg Icon, for instance), and you say that master branch is not maintained anymore.

missing svg Icon, for instance

@Colmea The svg icons are published under their own package, for more details: https://material-ui-1dab0.firebaseapp.com/style/icons#svg-icons.

master branch is not maintained anymore

I'm not saying that the master is no longer maintained. I'm saying that we don't plan any features/core improvements based on that branch. We focus on bug fixes and stability.

Ok perfect, thanks for the clarification.


Add a Testnet property

A testnet property should be added to each chain so that clients can correctly distinguish between two categories: Non-testnets and testnets.
Proposed API
Add isTestnet flag to Chain model

@safe-global/safe-web, please confirm whether the proposed API is sufficient. I suggest the same for the gateway.

Yes, looks good. 👍


rados restructure singleton for downstream - adding msgr

Signed-off-by: Rachanaben Patel<EMAIL_ADDRESS>

http://pulpito.ceph.redhat.com/racpatel-2020-05-18_04:32:36-rados:downstream:singleton-nautilus-distro-basic-argo/


Fix p300 flash behaviour

P300 behavior was broken in recent versions of Bessy Unity due to the Generate RNRA (RandomNonRepeatingArray) not generating appropriate arrays. This fix reverts to the old RNRA solution that was used with Dion and Joanna's projects. This solves the issues seen in B4K-273 and B4K-98 where not every item flashes and causes Bessy Python to crash.
This PR also handles some basic quality of life updates, including that the training target now grows in size by default, and the setup required toggle is on by default for P300, MI, and SSVEP is checked by default.
I commented out the Fischer Yates RNRA because I don't think it was used, and it was throwing an error that Random() was ambiguous to System.Random() or UnityEngine.Random().
I remember some complaints about row column and checkerboard not working, they are working now. But don't want to take credit if that was already fixed (I didn't test until after).
To test this code open up the controller hotswap example in the Samples folder and request the P300 behavior. Then hit s and confirm that all objects are flashing.

@brianjohannes - I've tested out the differences between your changes and the existing main branch and am not sure about committing the ones outlined here. See below:

Problems with row/column & checkerboard.  The existing problems outlined with row/column & checkerboard flashing are the same in both the current main solution, and your changes. Specifically, the only broken issue is when running row/column for anything that is a non-square set of objects. Everything works fine with 3x3 matrices, but breaks for 2 x 3 or 3 x 2 (or any other permutation). However, you prompted me to double check the checkerboard implementation on main and it works as expected, as long as the correct row/column values are input.

Training doesn't include all objects - Running on main and verifying with different combinations of numbers, I can train with no errors all cases - train on a subset of available SPOs, train exactly the same number of SPOs, and train on a greater set of SPOs. Furthermore, each set is verified to do a random repeat so that each SPO is trained on exactly one time before its repeated. This has been verified both by manual counting and the output from the console log.

Single flashing doesn't include all objects in the RNRA - Again, this has been verified in the current solution to be working. All of the flashing occurs correctly, each object flashes without missing objects the right number of times, and there is no object that flashes 2 times in a row.

QoL - We can move these to another PR, as I'm not sure that some of those aspects are what we want to include in the defaults. We can update and make a new sample where there is growing by default for training and each controller behavior is set to "set-up required" by default, but think for the actual prefab we should leave this empty. Additional QoL improvements in the editor should be considered as well (e.g. better grouping of variables, breaks in the editor spacing, etc.).

Fisher-Yates - I'll double check where that ended up, but again it might be a separate PR to see whether its worth keeping or not.

Ultimately, I think then that there isn't a reason to revert to the older implementation of the RNRA - the current one works well and is performant, plus easier to digest what is happening.


[ASK] Question about license of the fridge dataset for object detection

Hi team,
I am Francesco, a contributor to the open-source IceVision library for object detection.
The framework was originally developed, and is being currently maintained, by Farid and Lucas.
In a nutshell, the purpose of IceVision is to democratize access to the notoriously complex domain of object detection, providing a set of tools to streamline the end-to-end ML pipeline, from data parsing, to model training and deployment.
I am writing on behalf of the three of us for a request around the Fridge Dataset (FD), which you kindly put together and made available to the public.
Given its size and simplicity, FD is the ideal toy candidate for entry-level examples, reason why we are currently using it for several IceVision tutorials (here and here).
In the last couple of weeks, we noticed that the URL we fetch FD from, is often unavailable, creating frustration and friction among our users.
Therefore, we were wondering if we were allowed to make a copy of it and store it on our open-source repo.
Given we couldn't find the dataset's license, we obviously wanted to check if that wouldn't violate any restrictions, first.
Is this request reasonable?
Are we allowed to create a copy of FD and make it publicly accessible from within IceVision?
In thanking you for your great contributions to open-source, we wish you a pleasant week ahead.
Looking forward to your response!

Hi Francesco, apologies for this. We had to move the data to a new location, but should be stable again.

Thanks a lot for the prompt reply and for clarifying!

@PatrickBue just to make sure, is this the correct link?
https://cvbp.blob.core.windows.net/public/datasets/object_detection/odFridgeObjects.zip
I am trying and it doesn't seem to work.

Also, would you see as reasonable the possibility of hosting the dataset ourselves on our repo?
I didn't find the license, which is why I was not sure we were allowed to do that.


Remove WindowProperties, implement WindowRef

This is built on top of PR #441. Here's the relevant commit for this PR: https://github.com/AngryLawyer/rust-sdl2/commit/5d8e866739bfc33e10cbe7d2b896669a4d5e6d46
So, WindowProperties is overkill for most use cases. I realized that it can be eliminated and still meet the safety criteria for get_surface() (i.e. the event loop can't run and the window can't mutate because it would reallocate the surface).
// Old
window.properties(&event_pump).set_title("Hello!");
let s = window.properties(&event_pump).get_surface();

// New
window.set_title("Hello!");
let s = window.get_surface(&event_pump);

Renderer needed a method to access the underlying window, so I implemented WindowRef in a similar fashion to SurfaceRef in #435. It's not an option to expose &mut Window because all mutable references can be exchanged with another value (with std::mem::swap or similar).

Much cleaner. Cheers!


Tasks/gha testing

Soundtrack of this PR: Integration Song
Motivation
We need the ability to run configurable integration tests (i.e. configure environment, branch to test, etc).
In this PR

This is an initial GHA to run integration tests for any env using any branch.

Pivotal Tracker: Add a GitHub Action to run iOS SDK tests
Future Work

Ability to support dynamic environments, where the env config is passed via a pre-build command line step leveraging CocoaPodsKeys (i.e. bundle exec pod key set <name> <value>)
(ticket for above to be created)

stale PR, closing


Idle page send heartbeat (close #146)

/cc @inikulin @AlexanderMoskovkin

\r-

FPR

In general, looks good. Just single minor stylistic issue left.

FPR

\r-

@helen-dikareva It requires rebase now

FPR

lgtm

lgtm


Adding nested Object each loop

Adding nested Object each loop.
Trying to be consistent with: https://github.com/MicrosoftDocs/azure-devops-docs/pull/12997

@juliakm
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@juliakm just bumping this PR

@JFolberth  Thanks! This worked well for me.

#sign-off


Canvaskit and Skwasm need to support blur tile modes for backdrop filters

The issue was fixed in https://github.com/flutter/engine/pull/55640 for the native engine, but the same changes need to be made for the other backends that use Skia (CK and Skwasm?) as saveLayer does not honor the tile mode of a backdrop filter and instead you must copy that tile mode to the appropriate member of the SaveLayerRec in order to get it honored.

My CL to expose this API in CanvasKit just landed: https://skia-review.googlesource.com/c/skia/+/912262
It should roll into the Flutter engine shortly and we can use it to set the backdrop filter tile mode.

@flar fixed this

Fixed by https://github.com/flutter/engine/pull/55552


Can't delete the sleepimage on high sierra

sudo rm /private/var/vm/sleepimage
override rw------T  root/wheel for /private/var/vm/sleepimage? yes
rm: /private/var/vm/sleepimage: Operation not permitted
The same command works for macOS Sierra

I have the same problem here. Anyone knows how to fix it?

Hi, I am also having this problem, for example:
sudo rm:
Justin:vm justinbagley$ sudo rm -rf /var/vm/sleepimage
rm: /var/vm/sleepimage: Operation not permitted
OR
rm:
Justin:~ justinbagley$ cd /var/vm/
Justin:vm justinbagley$ ls
sleepimage	swapfile0
Justin:vm justinbagley$ rm ./sleepimage
override rw------T  root/wheel for ./sleepimage? y
rm: ./sleepimage: Operation not permitted
Permissions on sleepimage are read and write:
Justin:~ justinbagley$ ls -lod sleepimage
-rw------T  1 root<PHONE_NUMBER> Nov 21 08:02 sleepimage
Could someone please explain how to fix this issue and allow sudo access to not just read and write in var, but also remove files? I worry this may affect other files that I will need to sudo rm. ~ J

Anyone get a solution on this one? I'm getting the same in Sierra 10.12.6 also.

I'm guessing that probably in High Sierra the sleepimage was put under SIP control.  If that's the case, there's nothing you can do unless you disable SIP.

Excuse my ignorance, but what is SIP?

System Integrity Protection.

reboot into Recovery mode
open terminal
type: csrutil disable
reboot
try to remove the image again with SIP disabled

Read: https://www.imore.com/el-capitan-system-integrity-protection-helps-keep-malware-away

@chdiza is right. In High Sierra the sleepimage was put under SIP control. Just follow @markstachowski instructions.

I was able to select "EJECT" it (just as dmg or drive). Hope this helps someone!

Thanks worked like a champ 😊

You must first disable hibernation by executing:
sudo pmset -a hibernatemode 0

The problem I ran into on a MacBook Pro is every time you reboot with 10.13 the system resets the Hibernation mode to 3.

on a MacBook Pro is every time you reboot with 10.13 the system resets the Hibernation mode to 3.

It doesn't do that on mine.  It does recreate a sleepimage upon startup despite being in hibernate mode 0.  I reported this to Apple and they haven't done anything about it.

I'm late to the party... It's probably the SIP. Almost each time the shell returns ${command}: ${path}: Operation not permitted, the SIP prevents writing. See more here, there, here and there, and here also.

I think it worked for me. I did sudo pmset -a hibernatemode 0 and now it says the file doesn’t exist.


[FLINK-34268] Removing exclusions for FLINK-33676 33805

What is the purpose of the change
When FLINK-34268 was initially implemented, FLINK-33676 and FLINK-33805 had not landed.
Brief change log
Given that, there were exclusions hard-coded.  This PR removes those.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)

The description in the PR talks about FLINK-3367, but the code explains it's about https://issues.apache.org/jira/browse/FLINK-33676

The description in the PR talks about FLINK-3367, but the code explains it's about https://issues.apache.org/jira/browse/FLINK-33676

Updated!  Sorry for the typos!


[Image] Update URI GIF specific error

https://github.com/facebook/react-native/issues/2233#issuecomment-128173721

How does https://facebook.github.io/react-native/docs/image.html#network-resources address this?


ACCESS MED setup failing

Hi @dsroberts,
I am trying to set up a conda environment for MED using your singularity setup.
see here:
https://github.com/ACCESS-NRI/MED-condaenv/pulls
The initialisation is failing when calling singularity:
/opt/singularity/bin/singularity -s exec --bind /etc,/half-root,/local,/ram,/run,/system,/usr,/var/lib/sss,/var/run/munge,/var/lib/rpm,/jobfs/84698570.gadi-pbs/overlay/:/g /g/data/xp65/admin/MED-condaenv/container/base.sif /g/data/xp65/admin/MED-condaenv/scripts/initialise.sh --inner
for some reason, singularity cannot see the initialise.sh script.
FATAL:   stat /g/data/xp65/admin/MED-condaenv/scripts/initialise.sh: no such file or directory

Any idea?
Romain

This issue is actually intended behaviour. This part of the --bind flags: /jobfs/84698570.gadi-pbs/overlay/:/g replaces the default bind mount at /g (which is just Gadi's /g), with an empty directory in $PBS_JOBFS. This guarantees that the in-progress installation or update is completely isolated from the existing installation, and can therefore be deployed (or, crucially, not deployed in case of failure) without any effect on the existing installation. Solution is to run install.sh from a filesystem that is not /g/data. I run it out of /home, as the repository is pretty small.

Thanks @dsroberts. That makes sense.
I move the repo to my home.
I got the build to work.
Now the testing fails for probably the same reason.
diff: /g/data/xp65/admin/conda_concept/admin/staging/deployed.yml: No such file or directory
diff: /g/data/xp65/admin/conda_concept/admin/staging/deployed.old.yml: No such file or directory
tar: /g/data/xp65/admin/conda_concept/admin/staging/conda_base.tar: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
FATAL:   while loading overlay images: failed to open overlay image /g/data/xp65/admin/conda_concept/admin/staging/med-conda-0.1.sqsh.tmp: failed to retrieve path for /g/data/xp65/admin/conda_concept/admin/staging/med-conda-0.1.sqsh.tmp: lstat /g/data/xp65/admin/conda_concept/admin/staging/med-conda-0.1.sqsh.tmp: no such file or directory

The thing is you also define your admin folder to be on gdata.
What am I missing?

@rbeucher that part of the test script is run outside of the container, so those paths should exist at that point. You may want to double-check that those files are where you expect. The build scripts ends with || true to handle missing deployed.old.yml files in the case of a brand new installation. If the actual container build passed, but the copying at the end fails, the build will still report passed because of that.

Thanks @dsroberts.
I got it to work.
Question: This is the structure I get in the module after deployment:
modules
`-- conda
    |-- .access-med-0.1
    |-- .modulerc
    |-- access-med-0.1 -> .common_v3
    `-- conda
        `-- .common_v3

It expects .common_v3 to be in the first level conda folder. Although, there is another sub-folder called conda/conda
Is it intended behaviour?
Here is a link to my config:
https://github.com/ACCESS-NRI/MED-condaenv/blob/main/scripts/install_config.sh
R

Nope, not intended. I see what I did there. This line: https://github.com/coecms/cms-conda-singularity/blob/3a2540ceffb4b946f8c1326ffa019c6e6511762c/scripts/initialise.sh#LL30C22-L30C22
has an extra ${MODULE_NAME}, this is already included in ${CONDA_MODULE_PATH}

You want me to submit a PR for a fix?

I'm just about to do it along with another error I found

Also, I have added some conditions here.
https://github.com/coecms/cms-conda-singularity/compare/main...ACCESS-NRI:MED-condaenv:main#diff-3d64996115d0ac3b74e36f57ce6b00d6b4982614c41b1ed39eab8ef43b2e9a2b
It was breaking for the minimal example I was trying to set up.

Thanks. I got it to work on the CLI. Now I am trying with ARE.
I had commented out jupyter build. I turned it back on and it is failing... of course :-/
Hre is the extract of the job error output:
Please update conda by running

    $ conda update -n base -c defaults conda

[LabBuildApp] JupyterLab 4.0.0
[LabBuildApp] Building in /jobfs/85145911.gadi-pbs/squashfs-root/opt/conda/access-med-0.1/share/jupyter/lab
[LabBuildApp] ERROR | Build failed.
Troubleshooting: If the build failed due to an out-of-memory error, you
may be able to fix it by disabling the `dev_build` and/or `minimize` options.

If you are building via the `jupyter lab build` command, you can disable
these options like so:

jupyter lab build --dev-build=False --minimize=False

You can also disable these options for all JupyterLab builds by adding these
lines to a Jupyter config file named `jupyter_config.py`:

c.LabBuildApp.minimize = False
c.LabBuildApp.dev_build = False

If you don't already have a `jupyter_config.py` file, you can create one by
adding a blank file of that name to any of the Jupyter config directories.
The config directories can be listed by running:

jupyter --paths

Explanation:

- `dev-build`: This option controls whether a `dev` or a more streamlined
`production` build is used. This option will default to `False` (i.e., the
`production` build) for most users. However, if you have any labextensions
installed from local files, this option will instead default to `True`.
Explicitly setting `dev-build` to `False` will ensure that the `production`
build is used in all circumstances.

- `minimize`: This option controls whether your JS bundle is minified
during the Webpack build, which helps to improve JupyterLab's overall
performance. However, the minifier plugin used by Webpack is very memory
intensive, so turning it off may help the build finish successfully in
low-memory environments.

/g/data/xp65/public/apps/med_conda/envs/access-med-0.1/lib/python3.10/site-packages/jupyterlab/debuglog.py:56: UserWarning: An error occurred.
  warnings.warn("An error occurred.")
/g/data/xp65/public/apps/med_conda/envs/access-med-0.1/lib/python3.10/site-packages/jupyterlab/debuglog.py:57: UserWarning: ValueError: Please install Node.js and npm before continuing installation. You may be able to install Node.js from your package manager, from conda, or directly from the Node.js website (https://nodejs.org).
  warnings.warn(msg[-1].strip())
/g/data/xp65/public/apps/med_conda/envs/access-med-0.1/lib/python3.10/site-packages/jupyterlab/debuglog.py:58: UserWarning: See the log file for details: /jobfs/85145911.gadi-pbs/jupyterlab-debug-7ju_dqfv.log
  warnings.warn(f"See the log file for details: {log_path!s}")

My understanding of jupyter build is that it relates specifically to optional notebook assets like dask-labextension. So with your minimal environment, it probably isn't necessary. You know you'll need it when you start getting popups like:
JupyterLab build is suggested:

dask-labextension needs to be included in build

on connecting to a jupyterlab session. And the error tells you how to fix it anyway.
Please install Node.js and npm before continuing installation. You may be able to install Node.js from your package manager, from conda...

For what its worth, npm doesn't appear necessary. The jupyter build command completes in the hh5 envs just fine without it.