Added the component in Navbar

Title and Issue number

Title :
Issue No. :#117
Code Stack :
Close #117

Video/Screenshots (mandatory)

Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have gone through the  contributing.md file before contributing

Additional context (Mandatory )
Are you contributing under any Open-source programme?

Yes JWOC 2024

& also the about us section is not visible in the dark theme . make the changes in CSS

@shreya9x1 There is merge conflicts & the PR template is not properly filled .

Respected Sir, I'm facing a problem in this as the updates made by regarding dark screen mode is not visible in my forked repository. Kindly help me out with this So that I can make the changes of dark mode in "About Us" block.

& also the about us section is not visible in the dark theme . make the changes in CSS

Respected Sir, I'm facing a problem in this as the updates made by regarding dark screen mode is not visible in my forked repository. Kindly help me out with this So that I can make the changes of dark mode in "About Us" block.

& also the about us section is not visible in the dark theme . make the changes in CSS

Respected Sir, I'm facing a problem in this as the updates made by regarding dark screen mode is not visible in my forked repository. Kindly help me out with this So that I can make the changes of dark mode in "About Us" block.

@shreya9x1 I want to suggest you to update your branch to your Forked repo by clicking on the "SYNC FORK" option. So that In  that branch you can make your changes & make a PR .

@shreya9x1 I want to suggest you to make a new PR making a new updated branch in your forked repo & make changes there. I am closing this PR . Please submit your new PR . If you need any more help you can reach out to me in Discord


Improve handling of unicode characters

Close #3574
Related to #6

LGTM.
A problem is that utils::unicode_str_width takes O(n) whereas String::len takes O(1). If we were to replace every s.len() with utils::unicode_str_width(s), then we may hit a performance issue.
One solution is to create our own string type which holds the width of the Grapheme Cluster and replace it with String, though this would require a significant amount of rewriting.


Add qwen2-1.5b-instruct into igpu performance

updated qwen2-1.5b-instruct to all 7 transformers==4.37 yaml files in igpu-perf

Please make sure this model is put into xx01 first. Then we can merge this PR.


Can benchmark updated with every big version?

benchmark result in readme doc seems not updated for a long time. is it possible to updated with the big version?
@antfu

🎉 awesome.


Excluded 0044 from for Adoptium on java 19

Excluded this test to not fail pipelines like this - https://github.com/rh-openjdk/WindowsTPS/actions/runs/4365175766
It'll be fixed in #24 or #35.
Closes #35

By looking at test code bellow your changes, I got impression that ${JAVA_INSTALL_DIR}\\lib\\server was changed to ${JAVA_INSTALL_DIR}\\bin\\server in JDK17. But exact version is tested.
I think better fix would probably be changing [[ $OTOOL_JDK_VERSION -eq 17 ]] to [[ $OTOOL_JDK_VERSION -gt 17 ]].


Unions

Adding support for union types.
It works with present tests (samples files in tests directory).
However, some cases must be checked like anonymous types in variable declarations and union initialization subscripts.

This change is

I've seen checking error (codeclimate, ...), so i'll post another pull request that will pass these checks.

@corebreaker in case you don't know, you can still push commits after a PR has been opened and the commits will appear on the end.


docs: add known limitations for app.config.ts

🔗 Linked issue
#19858
#19854

Very nicely explained ❤


OCPVE-404: chore: decoupling the e2e tests from operator deployment

/override ci/prow/lvm-operator-bundle-e2e-aws

e2e tests are still broken
/override ci/prow/lvm-operator-bundle-e2e-aws


feat(behavior_path_planner): add curvature consideration in shift start

Description
Add an error handling when the module output is null.
Without this code, some modules may die due to invalid memory access.
Tests performed
Run psim
Effects on system behavior
Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

the PR title is wrong?


Add gauge and counter for suggest stats

I have added the missing metrics for suggestions relevant for ES version >=  <IP_ADDRESS>

Thanks :)


Production Builds

In order to ship the app, there may be a few things to do before we can ship to app stores.

[ ] ios screenshots/design assets
[ ] ios descripton/marketing content
[ ] ios cert signing/provisioning
[ ] android screenshots/design assets
[ ] android description/marketing content
[ ] android cert signing/provisioning
[ ] anything else?

@johnthepink @samclaridge where are we on this?

@jbaxleyiii i think we still need to create them all? the certs and provisioning are good to go.

@jbaxleyiii my thought was to use the on-boarding images as the screenshots. Is marketing writing the copy for the description, I feel like that's more up their alley?

we are in production!


Feature Request: Enhance derive_param_computed()

Feature Idea
derive_param_computed() should be enhanced such that the following parameter can be derived.

PARAMCD = "CHSF13"
AVAL: If QS.QSORRES in("Not applicable") then AVAL=0. If QS.QSORRES="Yes" then AVAL=38. If QS.QSORRES="No" and QS.QSSTRESN when PARAMCD="CHSF12" is greater than QS.QSSTRESN when PARAMCD="CHSF14" then AVAL=25. If QS.QSORRES="No" and QS.QSSTRESN when PARAMCD="CHSF12" equals QS.QSSTRESN when PARAMCD="CHSF14" then AVAL=0.

For example:
adchsf <- derive_param_computed(
  adchsf,
  dataset_add = qs,
  parameters = exprs(CHSF12, CHSF13 = QSTESTCD %in% c("CHSF113", "CHSF213"), CHSF14),
  analysis_value = case_when(
    QSORRES.CHSF13 == "Not applicable" ~ 0,
    QSORRES.CHSF13 == "Yes" ~ 38,
    QSORRES.CHSF13 == "No" ~ if_else(
      QSSTRESN.CHSF12 > QSSTRESN.CHSF14,
      25,
      0
    )
  ),
  set_values_to = exprs(PARAMCD = "CHSF13")
)

The dataset_add argument is added to use observations from a different dataset than the input dataset.
The parameters argument is enhanced such that "new" parameters can be defined via conditions.
The analysis_value argument is enhanced such that other source variables than AVAL can be used, e.g., QSORRES or QSSTRESN.

Relevant Input
No response
Relevant Output
No response
Reproducible Example/Pseudo Code
No response

What do you think of this update @pharmaverse/admiral ?

I like this enhancement, but I can imagine it starts to become difficult to "visualize" what's happening here (also true for many of our advanced general functions) wondering if in the documentation for the function, we can include some sort of simple diagram the origin of the expressions/columns involved, what is retained/created/removed along the way to the end return object

Good idea! I never tried it but it seems that you can create diagrams directly in R markdown: https://bookdown.org/yihui/rmarkdown-cookbook/diagrams.html

Yeah it seems very complicated to me, what would be the alternative solution with the current functions we have? 2 steps I guess?
I would be concerned about the need for diagrams to explain a function.

@PavloChaika if you are still interested, we have been given the go-ahead to implement this change.  We need to have it completed before no later than May 31st as we are doing a release on June 5th.  Let us know your thoughts!!  We will support you! :)

@PavloChaika if you are still interested, we have been given the go-ahead to implement this change. We need to have it completed before no later than May 31st as we are doing a release on June 5th. Let us know your thoughts!! We will support you! :)

Thank you for letting me know about the go-ahead to implement the change. I apologize for not responding earlier. I think it is better if Stefan finishes it since he has already started working on it. However, since I still want to gain some practice, I'll work on it locally. I will let you know if I have any questions.


Added AWS resources; New Relic fix; HCL version update

Added support for AWS Lambda, KMS, Beanstalk and EMR resources. Had to do some hacks to format some of the properties. I tried a nice way to make Terraform format properly but gave up (HCL support in V2 for JSON->HCL parsing is still non-existent ref https://github.com/kubernetes/kops/issues/7052#issuecomment-554581139).
What we can think to do in the future is to abandon HCL syntax in favour for saving data as JSON - https://www.terraform.io/docs/configuration/syntax-json.html. It will result in less hacks to maintain.
Added an ability to make Terraform send lower number of requests in order to respond to request throttling. Right now it's a manual process for AWS KMS resources and New Relic dashboards.
fixes #126
fixes #283
fixes #203

🥇


Added grammar for case outcome and EDD

Added grammar for case outcome and EDD and tweaked the README

Added grammar for EDD, outcome, actions, batches and birth & death date for cases and mothers


Allow comparison between Cell and numpy array or list of len = 1.

Fixes #2914.
A simple fix to allow numpy arrays (or lists) with only one element to be compared to a Cell.

Thanks for the update @gcaria!

it is arguably a bit of a misuse to not feed a sequence to np.array

I don't know how the original issue came up and unfortunately the developers involved have both since moved on.  However I've found a couple of ways the 0-dimensional array could be created:
cube  = iris.cube.Cube(1)
print(repr(cube.data))

array = np.squeeze([[[4]]])
print(repr(array))

gives
array(1)
array(4)

so possibly there was a use-case where the 0-dimensional array came out of some other calculation.
Using float seems OK to me too given the operators.

Thanks for the clarification @rcomer, I was mostly surprised to see np.array can be used in that way, but this is surely not an issue with iris.
I have added a minimal set of lines for the testing.

Thanks @gcaria, these tests look good to me.  Could you add similar tests for the size 1 array/list case you originally added?  Just to make sure the various paths through the if loop are covered.  Then this just needs an entry under "bugs fixed" in the whatsnew and I think we're done.
Really appreciate your work on this - it's great to get some of these old issues tidied up!


weave-npc blocks everything if kubelet --hostname_override flag used

As reported on Slack
we see in the weave-npc logs:
INFO: 2017/05/31 12:50:19.956363 Starting Weaveworks NPC 1.9.6; node name "kube01"
...
DEBU: 2017/05/31 12:50:20.318135 AddPod ignored for pod kube-system/weave-net-qbvhp on node <IP_ADDRESS>
DEBU: 2017/05/31 12:50:20.318257 AddPod ignored for pod default/nginx-701339712-v3dkt on node <IP_ADDRESS>

but these pods are actually local - kubelet's args include --hostname_override=<IP_ADDRESS>
If we take the node name via the Kubernetes downward API it should match.

Fixed by #2996


[SP-5264] Backport of PDI-18254 - Exported Kafka Consumer Step cannot…

… be imported (8.3 Suite)
Cherry-pick of #6825 into 8.3 branch.
@ssamora

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -f 'pom.xml' -pl 'engine,core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'engine,core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  core/src/main/java/org/pentaho/di/core/xml/XMLHandler.java
  engine/src/main/java/org/pentaho/di/repository/RepositoryExportSaxParser.java
  engine/src/test/java/org/pentaho/di/repository/RepositoryExportSaxParserTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.core.xml.XMLHandler

Branch Change: -1.3% :small_red_triangle_down:
Complexity Change: -1.4% :small_red_triangle_down:
Instruction Change: -2.1% :small_red_triangle_down:
Line Change: -2.2% :small_red_triangle_down:
Method Change: -1.9% :small_red_triangle_down:

org.pentaho.di.trans.steps.csvinput.CsvInputMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -4.1% :small_red_triangle_down:
Complexity Change: -4.2% :small_red_triangle_down:
Instruction Change: -0.3% :small_red_triangle_down:
Line Change: -0.7% :small_red_triangle_down:

org.pentaho.di.trans.steps.ifnull.IfNullMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -1.9% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.ldapoutput.LDAPOutputMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.uniquerows.UniqueRowsMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceinsert.SalesforceInsertMeta

Instruction Change: -0.1% :small_red_triangle_down:


Changing files inside node_modules requires restarting packager

When I change files under node_modules, I need to restart the packager for it to pick up changes. The regression was introduced somewhere around v0.40. It becomes very difficult to debug/develop and debug libraries because of the issue.

cc @cpojer

Since 0.39 we have some troubles with node_modules. See #11301

@cpojer claims this should work in a version of RN where jest-haste-map is updated to 19.x+

Seems it's in latest RC https://github.com/facebook/react-native/commit/570c564e77d00bbbc090acd047f04779914a5d9c#diff-b9cfc7f2cdf78a7f4b91a753d10865a2
Maybe we could cherry-pick to stable? cc @grabbou

I think it's a must as it's rather important feature. Let's discuss it tomorrow as I'll be wrapping up changelog.


Add Authoritative Selectable Property

Hey Michael, I branched out an tentative to add the Auth property to the plugin and have it behave accordingly.
Tested briefly via remote emulation on a NMX-DEC-N2312 and seems to work properly

I'm sorry for the mess on commits, I am a bit rusty in using proper SCM


I/O error, no data when trying to read file in pachctl mount

I'm new to pachyderm and just trying it out. Deployed pachyderm in minikube with the KVM driver and I'm able to interact with pachctl just fine, but the FUSE mount isn't working for me. I can create files in a commit, but once i finish the commit, I can't read the file I've added to it:
c@zeugmatic:~$ pachctl start-commit data
f8901e20e72442f09a577eee28d76e69
c@zeugmatic:~$ cd ~/pfs/data/f8901e20e72442f09a577eee28d76e69/
@zeugmatic:~/pfs/data/f8901e20e72442f09a577eee28d76e69$ cat ~/src/pachyderm/examples/fruit_stand/set1.txt >~/pfs/data/f8901e20e72442f09a577eee28d76e69/sales
c@zeugmatic:~/pfs/data/f8901e20e72442f09a577eee28d76e69$ cat sales
cat: sales: Input/output error
c@zeugmatic:~/pfs/data/f8901e20e72442f09a577eee28d76e69$ pachctl finish-commit data f8901e20e72442f09a577eee28d76e69
c@zeugmatic:~/pfs/data/f8901e20e72442f09a577eee28d76e69$ cat sales
cat: sales: Input/output error

When I try to get the file with pachctl, I get nothing:
c@zeugmatic:~/pfs/data/f8901e20e72442f09a577eee28d76e69$ pachctl get-file data f8901e20e72442f09a577eee28d76e69 sales
c@zeugmatic:~/pfs/data/f8901e20e72442f09a577eee28d76e69$

Even though the file is 874 bytes:
c@zeugmatic:~/pfs/data/f8901e20e72442f09a577eee28d76e69$ pachctl inspect-file data f8901e20e72442f09a577eee28d76e69 sales
Path: data/f8901e20e72442f09a577eee28d76e69/sales
Type: file
Modifed: About a minute ago
Size: 874 B
Commit Modified: data/f8901e20e72442f09a577eee28d76e69

Remounting doesn't help.
Some info on my setup:
c@zeugmatic:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.1 LTS
Release:        16.04
Codename:       xenial
c@zeugmatic:~$ pachctl version
COMPONENT           VERSION
pachctl             1.1.0-c13bec58aabf564490c6b1895198d1e69f56457c
pachd               1.1.0
c@zeugmatic:~$ kubectl get all
NAME            DESIRED      CURRENT       AGE
etcd            1            1             45m
pachd           2            2             45m
rethink         1            1             45m
NAME            CLUSTER-IP   EXTERNAL-IP   PORT(S)                        AGE
etcd            <IP_ADDRESS>    <none>        2379/TCP,2380/TCP              45m
kubernetes      <IP_ADDRESS>     <none>        443/TCP                        11h
pachd           <IP_ADDRESS>    <nodes>       650/TCP                        45m
rethink         <IP_ADDRESS>   <nodes>       8080/TCP,28015/TCP,29015/TCP   45m
NAME            READY        STATUS        RESTARTS                       AGE
etcd-ldl1e      1/1          Running       0                              45m
pachd-6pght     1/1          Running       2                              45m
pachd-np5rh     1/1          Running       2                              45m
rethink-9lce8   1/1          Running       0                              45m

Not sure what else might be helpful. Didn't see anything obvious in the pachd or rethink logs.

Hmm, my guess would be that a version mismatch between pachctl and pachd is to blame. The mounting process pachctl mount ... should have some logs about the input/output error that would reveal more. To fix try:
git checkout v1.1.0
make install

Then try doing the get-file again, hopefully that'll work.
Sorry you hit this, we're going to be adding some measures to maintain backward compatibility so people don't hit this soon.

@jdoliner That fixed my issue, thanks!

I also had to specify v1.1.0 in etc/kube/pachyderm.json. I was getting pachd 1.0.1 otherwise, which didn't support the fruit-stand example when I tried working with pipelines, with a 1.1.0 client.
However, everything's working now!

Awesome, btw instead of modifying etc/kube/pachyderm.json you can just use etc/kube/pachyderm-versioned.json


Subscription destination URL with path is considered invalid

Bug report
System info: InfluxDB v1.3.6 (git: 1.3 a7c3d3c0f7b74f71919047adbc4933460967a576)
I am running Kapacitor behind a reverse proxy and when Kapacitor attempts to create a subscription it fails when there is a path present in the destination URL.
Looking into the InfluxDB logs and pulling Kapacitor from the equation I am able to reproduce the issue below.
Steps to reproduce:
Run the following command on the InfluxDB machine:
curl -v -X POST "localhost:8086/query?db=&q=CREATE+SUBSCRIPTION+%22test%22+ON+system.autogen+DESTINATIONS+ANY+%27http%3A%2F%2Flocalhost.localdomain%2Freverseproxy%3A80%27"

Expected behavior:
{"results":[{"statement_id":0}]}

Actual behavior:
{"results":[{"statement_id":0,"error":"invalid subscription URL: http://localhost.localdomain/reverseproxy:80"}]}

My apologies -- long day of troubleshooting. Transposed path and port in the URL.


Live demo link is broken in README

The link gives a Page Not Found error:

Oh dear, that's a new one. Possibly part of the facebook -> graphql foundation transition. I'll ask around.

Can you report that here @RussianCow ? https://github.com/graphql/swapi-graphql
Might have to do with updated deps


dataset.sample_type field values are inconsistent in case-sensitivity "cell" vs "Cell"

Describe the bug
"cell" in non-jensen data vs "Cell" in jensen data
To Reproduce
from cryoet_data_portal import Client, Dataset
api query
c=Client()
d1=Dataset.find(c, query_filters=[Dataset.sample_type=="Cell"])
d2 = Dataset.find(c, query_filters=[Dataset.sample_type=="cell"])
print(len(d1))
print(len(d2))
Both returns non-zero result.

https://github.com/czimaginginstitute/czii-data-portal-processing/commit/8e38d9c61ea9834973e96d8b4c854d33c39348ad fixes this in jensen data ingestion json files. Will need these new metadata ingested to fix the bug.
This is a low-priority bug. might be useful to tag on other re-ingestion tasks. @manasaV3 @jgadling

Relates to:
https://github.com/chanzuckerberg/cryoet-data-portal/issues/693
https://github.com/chanzuckerberg/cryoet-data-portal/issues/692


[BUG]: Sanity checks during schema creation

What version of drizzle-orm are you using?
0.21.1
Describe the Bug
Common mistakes like two columns with the same names, should be caught early, during schema creation:
const users = pgTable('users', {
  id: serial('id').primaryKey(),
  fullName: text('id'), // id field created twice
});

This can happen pretty easily while copy-pasting lines of code.

Related: https://github.com/drizzle-team/drizzle-orm/issues/1695


Bazel 0.13

Motivation for this change
Upgrade to latest upstream.
There is already #40424 and #40205 that propose much the same thing. But the latter is currently just a change to the version number and sha256 sum, which doesn't build on NixOS. And the former propose far more changes in this PR that are certainly worth considering, but not on the critical path to upgrading to Bazel 0.13.
As per #39585, this change furthermore contains a change in package maintainer.
As noted in #40205, with this PR Tensorflow doesn't build due to Bazel 0.13 removing features that were previously deprecated. This needs to be addressed still.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Thank you. May I suggest you and the authors of the other 2 related PRs, @uri-canva and @rdnetto4  discuss this and try to reach consensus on how to move forward.

I will close my PR and create a new PR for darwin support after Bazel has been upgraded to 0.13.0. As @mboes notes my PR has bigger changes than strictly required for the upgrade because of that.

@GrahamcOfBorg build bazel

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: bazel
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: bazel
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-linux (full log)
Attempted: bazel
Partial log (click to expand)
[2,076 / 2,210] no action
INFO: Elapsed time: 217.383s, Critical Path: 53.88s
[2,076 / 2,210] no action
INFO: 1706 processes: 1488 local, 218 worker.
[2,076 / 2,210] no action
FAILED: Build did NOT complete successfully

ERROR: Could not build Bazel
builder for '/nix/store/ahjv8qhsacyd6difl940v9bxdgyd7h6v-bazel-0.13.0.drv' failed with exit code 1
error: build of '/nix/store/ahjv8qhsacyd6difl940v9bxdgyd7h6v-bazel-0.13.0.drv' failed

@mboes the /usr/bin/env replacement is still necessary. The build is currently failing with:

Executing genrule //src:embedded_tools; 0s local
/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/bash: bazel-out/host/bin/src/create_embedded_tools: /usr/bin/env: bad interpreter: No such file or directory

Note that is might not be the case on your local host if build sandboxing is turned off.

@GrahamcOfBorg  build bazel

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: bazel
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: bazel
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: bazel
Partial log (click to expand)
//examples/cpp:hello-success_test                                        PASSED in 0.1s
//examples/java-native/src/test/java/com/example/myproject:hello         PASSED in 0.2s

Executed 2 out of 2 tests: 2 tests pass.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line option to see which ones these are.
installing
post-installation fixup
patching script interpreter paths in /nix/store/k9i0ana4jn3nd8sp50qjav42k4v4h7rr-bazel-0.13.0
checking for references to /tmp in /nix/store/k9i0ana4jn3nd8sp50qjav42k4v4h7rr-bazel-0.13.0...
/nix/store/k9i0ana4jn3nd8sp50qjav42k4v4h7rr-bazel-0.13.0

things failing with nox-review:
error: build of '/nix/store/3p39fs8ffx0ypb71nvxmvlz4bb08ihka-python2.7-tflearn-0.2.1.drv', '/nix/store/d16mya1nc0inxijjmxypkpx4p633vjpz-python3.6-tensorflow-1.5.0.drv', '/nix/store/d4qdhaaj9n6lfl67s52kvi8ng8s8mn40-python3.6-edward-1.3.5.drv', '/nix/store/k5r4bbbsn00kqjhnv1bxghfxhacpihw7-python3.6-tflearn-0.2.1.drv', '/nix/store/racll38b0qkg79yd0x06yvz75h04mp2j-python2.7-edward-1.3.5.drv', '/nix/store/xk47wvbmyzjalbdfadr70v841bax4nfa-python2.7-tensorflow-1.5.0.drv' failed

they all seem to be tensorflow-related

Yes, this breaks the build of tensorflow and would require us to bump it to 1.8  according to discussion in #40205 . I'd rather wait for someone familiar with tensorflow to test if 1.8 really works before we merge this.

it would also be acceptable to keep version 0.12 around until tensorflow gets upgraded

So I tried giving building tensorflow 1.8 a go. But I either ran out of memory or hit what looks like a internal race condition within Bazel. The error goes something like this:
java.lang.RuntimeException: Unrecoverable error while evaluating node 'PACKAGE:tensorflow/core/kernels' (requested by nodes '//tensorflow:libtensorflow_framework.so com.google.devtools.build.lib.skyframe.BuildConfigurationValue$Key@edd564fa true<PHONE_NUMBER>)', '//tensorflow:libtensorflow_framework.so com.google.devtools.build.lib.skyframe.BuildConfigurationValue$Key@71af1344 false (265845462)', '//tensorflow/core/grappler/costs:measuring_cost_estimator com.google.devtools.build.lib.skyframe.BuildConfigurationValue$Key@71af1344 false<PHONE_NUMBER>)', '//tensorflow/core:core_cpu_internal com.google.devtools.build.lib.skyframe.BuildConfigurationValue$Key@71af1344 false (308542468)', '//tensorflow/core:framework_internal_headers_lib_gather com.google.devtools.build.lib.skyframe.BuildConfigurationValue$Key@71af1344 false<PHONE_NUMBER>)', '//tensorflow/core:framework_internal_headers_lib_gather com.google.devtools.build.lib.skyframe.BuildConfigurationValue$Key@edd564fa true (824725492)')
        at com.google.devtools.build.skyframe.AbstractParallelEvaluator$Evaluate.run(AbstractParallelEvaluator.java:424)
        at com.google.devtools.build.lib.concurrent.AbstractQueueVisitor$WrappedRunnable.run(AbstractQueueVisitor.java:355)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException: Invalid EvalException:
java.lang.InterruptedException
        at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:503)
        at com.google.common.util.concurrent.AbstractFuture$TrustedFuture.get(AbstractFuture.java:85)
        at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:62)
        ...

Only related upstream issue I could find is https://github.com/bazelbuild/bazel/issues/2423.
Upshot: let's try keeping 0.12 for Tensorflow then, until we can get to the bottom of this.

Or more likely, this issue: https://github.com/bazelbuild/bazel/issues/5177.

@mboes thanks for investigating. Let's keep the old version as bazel_0_12 and pin tensorflow to it for the time being.

@mboes this cannot be merged yet because the tensorflow update (#40689) doesn't build.
We can merge this if we keep the old version as bazel_0_12 and pin tensorflow to it.
Or we can let this wait until #40689 is fixed. What do you prefer?

cc @abbradar

@xeji looks like tensorflow is no longer a problem, because since #41259 Tensorflow is now built from a binary distribution. So I believe that blocker is now gone.

I have rebased the commits that were on this branch originally to current master, which has #41259 merged in.

@GrahamcOfBorg build bazel

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: bazel
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-darwin (full log)
Attempted: bazel
Partial log (click to expand)
./tools/test/collect_coverage.sh: interpreter directive changed from "/bin/bash -x" to "/nix/store/46y32j94pm0cz6ygywb3wxxj0fdbqj13-bash/bin/bash -x"
./tools/test/test-setup.sh: interpreter directive changed from "/bin/bash" to "/nix/store/46y32j94pm0cz6ygywb3wxxj0fdbqj13-bash/bin/bash"
configuring
no configure script, doing nothing
building
Building Bazel from scratch....../usr/bin/xcrun clang -fobjc-arc -framework CoreServices -framework Foundation -o /tmp/bazel_jHWExtEd/archive/_embedded_binaries/xcode-locator tools/osx/xcode_locator.m
xcode-select: error: no developer tools were found at '/Applications/Xcode.app', and no install could be requested (perhaps no UI is present), please install manually from 'developer.apple.com'.
/nix/store/7amnc2662p390bgzj6c0snylj19vxmj2-stdenv-darwin/setup: line 1291: ./output/bazel: No such file or directory
builder for '/nix/store/skpwcblpi077b7zw26mm0jqmlznsw8d9-bazel-0.13.0.drv' failed with exit code 127
error: build of '/nix/store/skpwcblpi077b7zw26mm0jqmlznsw8d9-bazel-0.13.0.drv' failed

Success on x86_64-linux (full log)
Attempted: bazel
Partial log (click to expand)
//examples/cpp:hello-success_test                                        PASSED in 0.0s
//examples/java-native/src/test/java/com/example/myproject:hello         PASSED in 0.2s

Executed 2 out of 2 tests: 2 tests pass.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line option to see which ones these are.
installing
post-installation fixup
patching script interpreter paths in /nix/store/jh7xc1qbf4by5cqnqxgiafvwfwqbyish-bazel-0.13.0
checking for references to /tmp in /nix/store/jh7xc1qbf4by5cqnqxgiafvwfwqbyish-bazel-0.13.0...
/nix/store/jh7xc1qbf4by5cqnqxgiafvwfwqbyish-bazel-0.13.0

Darwin build was broken before this PR despite #41911, which (according to its title) should have fixed it. cc @uri-canva

xcode-select: error: no developer tools were found at '/Applications/Xcode.app', and no install could be requested (perhaps no UI is present), please install manually from 'developer.apple.com'.

It seems Bazel cannot be built on CI without Xcode, and I'm not sure we can install Xcode from nix because of the license. A shim can be created, but that's a lot of work.
In the meantime I'll double check it's working on darwin on master, thanks for the heads up @xeji.


FetchPush tqc or her?

Hi! I'm new to rl-baselines3-zoo.
I want to try out FetchPush-v1 with TQC or HER, but I couldn't download trained agents of TQC with 'git clone --recursive'.
And I found out HER is deprecated now(I guess?), so I couldn't 'enjoy' FetchPush-v1 with trained agents of HER.
(I got an error message that HER is not in possible algo choices.)
So I tried to train TQC myself
python train.py --algo tqc --env FetchPush-v1
, but error occurs with the message below.
Traceback (most recent call last):   File "train.py", line 174, in <module>     model = exp_manager.setup_experiment()   File "/home/name/projects/rl-baselines3-zoo/utils/exp_manager.py", line 171, in setup_experiment     **self._hyperparams, TypeError: __init__() got an unexpected keyword argument 'replay_buffer_class'
Am I doing something wrong? How can I fix it?
System Info
I forgot how I installed Stable Baselines3, but either pip or source.
Python version is 3.7.9
pytorch version is 1.7.1

Hello,

I want to try out FetchPush-v1 with TQC or HER, but I couldn't download trained agents of TQC with 'git clone --recursive'

yes, I need to retrain the models, will try to do that soon (before the v1.1.0 release).

, but error occurs with the message below.
I forgot how I installed Stable Baselines3, but either pip or source.

This is your error, please follow the instructions of the README and do pip install -e requirements.txt, it should fix your issue ;)

Thanks! It worked with the command
pip install -r requirements.txt


feat: add grafana dashboard to helm chart

Signed-off-by: Engin Diri<EMAIL_ADDRESS>Hi,
This PR adds the Grafana dashboard into the helm chart. So now we can you, if we want, use the Grafana dashboard sidecar to import the dashboards via configmap.
Looking for your feedback.
FYI: @Kaktor

Thanks! Testing this out some...


CASSANDRA-19223: Column type mapping error for timestamp type during …

…bulk writes

Closed via https://github.com/apache/cassandra-analytics/commit/e82fceaecfe5ea04ac3ddff92be5a6a41456333c


Wrong types in Typescript UBO management

MangoPay.UboDeclarations.updateUbo() expects an UpdateUbo object, but the ID field is not available (the underlying API call is /users/:UserId/kyc/ubodeclarations/:UboDeclarationId/ubos/:UboId and the UboId parameter is mandatory).
Interface UboDeclarationData has every property with a null type.

Hello @belinde,
Thanks for the feedback. Let us look into it.
Regards and happy new year,

Hello @belinde, I am closing this issue because it has been fixed in 1.25.1


New version: Feather v0.5.7

Registering package: Feather
Repository: https://github.com/JuliaData/Feather.jl
Created by: @bkamins
Version: v0.5.7
Commit: a46b4e2c756dd586bf216fb7f54937571c17f8ad
Reviewed by: @bkamins
Reference: https://github.com/JuliaData/Feather.jl/commit/a46b4e2c756dd586bf216fb7f54937571c17f8ad#commitcomment-38981362

Please close this PR. I made the version number incorrectly


notification improvements

There are various actions in data.all that happen asynchronously such as a share being processed, dataset and environment stacks being updates, health of shares being verified etc. All of these actions can fail for whatever reason. Currently when things fail users are not able to find out until they check the logs or inspect data.all UI.
I'd like to propose that all asynchronous actions in data.all that can fail would send notifications and also be integrated with the recent reminder service that was implemented for shares to remind users that approvals for shares are pending.
A list of actions that should send notifications and to whom they should be sent:
a) An approved share fails (or revoked) to become successfully processed - both dataset owner and requester team should be notified and reminded. Optionally DA admins should also be able to subscribe to these notifications.
b) Dataset or Environment stack fails to update environment admin team should be notified as well as the dataset owner team. Reminders should be sent. DA admins should be able to optionally subscribe as well.
c) Any background task such as catalog reindexing, share health verified - if it fails (throws an exception) then DA admins should be notified ONCE.
d) If a share becomes unhealthy both the requester and dataset owner should be notified and reminded. DA admins should be able to optionally subscribe also.
e) If attempting to re-apply a share fails both the requester and dataset owner should be notified ONCE. DA admins should be able to optionally subscribe also.
There are already a few tickets filed for this effort that we should combine into this major story:
https://github.com/data-dot-all/dataall/issues/1251
https://github.com/data-dot-all/dataall/issues/1299
There might be more that I was not able to find.

Hi @zsaltys - also want to link these comments from an earlier discussion on persistent reminders feature that begin to start thinking through the above issue described
https://github.com/data-dot-all/dataall/issues/1248#issuecomment-2108546716
https://github.com/data-dot-all/dataall/issues/1248#issuecomment-2112705676
Ultimately I envision we would have a list of different "NotificationEvents" (i.e. StackFailedNotification, ShareUnHealthyNotification, CatalogIndexerFailedNotification, etc.) and so on that each have their own generic notification groups and reminder schedules depending on the event specified
Also this list of events should be easily extendable if tomorrow we wanted to add a notification for NewTableMetricsNotification OR NewTeamInvitedNotification for example.
I think it may be best to take some time and iron our a good generic and flexible design on how this notification system would look like in data.all. I think once we define it once it will be seamless to extend to more and more type of events or more and more type of delivery channels to send outbound notifications (on top of already in the UI and (optionally) via email)
Please let me know if you are thinking the same and let's use this issue here to discuss further on what that design could entail

Another small issue - Currently  if the share is with a consumption role then the email notification body text contains something like - share request for dataset <DATASET_NAME> for principal ggief66q.
The principal name is not readable and it is the internal id used by data.all for that principal. Instead of id this should be replaced with a user friendly readable consumption role name

Proposal
Summarizing the notifications improvements which need to be made

Send notifications ( both UI and email ) when a share fails
Send notification ( both UI and email ) when a share verifier find the share in unhealthy state. Also send notification when the reapply for the share fails.

As a sub part of this, send email notification when a share which was previously in unhealthy state gets to a healthy state.

Send weekly reminder notifications ( similar to the persistent email ) with a share info digest. This digest will contain

First Section can be about the shares which are in submitted state and need some action to be taken from the dataowner / stewards
Second section can be about share which belong to the owner and which are in unhealthy state.
Third section can be about the environment and datasets which are in unhealthy state.

Dataset notifications

When a dataset is created in an environment ? Send it to the env admin team ? Dataset owner and steward team
When dataset gets into an unhealthy state ( CREATE_FAILED, UPDATE_ROLLBACK_COMPLETE, UPDATE_FAILED, etc ) then send email notifications to dataset owner and stewards  ( also environment admin ? )
When tables are removed from dataset ( i.e. after synchronizing ) , send email to the dataset owner ?
Notify dataset owner and stewards when the S3 bucket / KMS registered with data.all for the bucket / Glue database change / get deleted , etc

Environment notifications

When an environment is in unhealthy state ( CREATE_FAILED, UPDATE_ROLLBACK_COMPLETE, etc ) to env admin and org admins ?

Notifications when any task fails

When any ECS task fails - scheduled ECS task only - then send a notification to the DAAdmins

Notification Module Improvement - As highlighted by @noah-paige  in this message ( https://github.com/data-dot-all/dataall/issues/1420#issuecomment-2253121297 ) , there is a need to refactor and design notifications such that there is  base template which other modules can leverage and create notifications seemlessly.

Stage 1
There are instances in which someone approves a share, thinking it will succeed, only later to find out that the share failed. Also, since the bucket / kms and IAM policies can be modified in an environment account apart from data.all, there are instance in which the verifier detects unhealthy share but the share requestor and dataset owner are not aware. Apart from this, all ECS tasks which are scheduled fail sometime and this failure is not notified to data.all DAAdmins. Thus adding these notifications is very important.
Since these notifications are share related notifications and there already exist share notifications code base, in the first stage, additional notification support can be added. Following will be covered as a part of Stage 1,

Sending ( UI and Email ) notifications when a share fails.

Both approver and requestor will be notified

Sending ( UI and Email ) notifications when share verifier finds a share in unhealthy state. Same for share re-apply

Requestor of the share will get notified ( ? Should the owner also get notified ? )

Sending ( Email ) notifications when an ECS task fails due to some reason

Share Verifier ECS Task
Share Reapplier ECS Task
Catalog Service ECS Task
Stack Update ECS Task
Persistent Email Reminder ECS Task
Table Syncer ECS Task

Weekly ( configurable ) reminder digest email which will combine all the share which are unhealthy, in submitted state and needs actions by the team, and environment, dataset which are in unhealthy state. This could leverage the existing code in persistent email reminders and then structure it to contain all this. Since persistent email reminders send emails about a particular share to all the team members, it so happens that a single user gets multiple emails about different shares. This can be annoying at times. With the digest, number of emails a user from a team gets for unsubmitted shares / unhealthy shares, etc will reduce and also all the actionable items will be in one single email.

Stage 2  ( WIP )
In this stage the notifications system will be refactored so that each module can hook up their own notification and which will conform with some standards set by the notification module.

How should the configs look like ?
How should the notification template look like ?
What is most common and important in the template for notification event ?
Can transport and notification separated in a meaningfulway

Part of refactoring,

Move share_notifications from dataset_base to shares_base.


What kind of model and feature is suitable for this scenery? (deal with synonym)

Train data: Who is Michael Jordan?  and Who is Air Jordan?  are one right match.
The test data is Who is Jumpman Jordan?   and Who is Air Jordan?
What feature should I add for training? Which model can capture the match info for this case?
Thank you！！！
@pl8787 @faneshion @yangliuy @HouJP @JiafengGuo

@guotong1988 Can you clarify your question?

@guotong1988 I think your question is on training/testing of paraphrase identification. You test data should also contain a question pair, correct ? You can refer to the QuoraQP data in the readme file. PI is supported by MatchZoo.

Thank you. I have edit the question~

@guotong1988 @yangliuy 's answer make sense for you?

Thanks for your question, I'll close it for now. If you have further questions, please feel free to re-open it or create a new issue. Best.


Turn server config

Hi, I installed Coturn server and username and password are incorrect, i get 401 in server logs,
While testing with Spreed-webrtc works fine..
How do I set up coturn or peercalls to work together?
Does peercall needs to hash the username, se this is what i got.
57: session<PHONE_NUMBER>00000003: realm domain.com> user : incoming packet message processed, error 401: Unauthorised

Hi @utan, can you share the value of iceServers in your config? (please mask actual username/password)

I am away from my pc, but i am overwriting default peercall settings editing the default config..
My coturn server has the same realm and username set, but it wont accept it..
The username is sent in as set meanwhile spreed-webrtc sent like a hash as username...and same realm

57: session<PHONE_NUMBER>00000003: closed (2nd stage), user <1502742494:CeTSMai82npnusi4ortyuxJbDqZhXPcB4JszAISysi> realm <mydomain.com> origin <>, local ip#here, remote someip:29443, reason: TCP connection closed by client (callback
Thats the payload of spreed-webrtc to the coturn server, which spreed has the same plain realm and usrername as set in peercall..

Are you trying to use coturn's [--use-auth-secret][1] flaf?

This option uses timestamp as part of combined username:
usercombo -> "timestamp:username",
turn user -> usercombo,
turn password -> base64(hmac(input_buffer = usercombo, key = shared-secret)).

If so, can you make sure that you have auth: 'secret' property set in your iceServer config?
1: https://github.com/coturn/coturn/blob/master/README.turnserver

Settings for my coturn Server, it is online but my testbed for peercall is at home in my computer.
Run as TURN server only, all STUN requests will be ignored.
no-stun
Specify listening port. Change to 80 or 443 to go around some strict NATs.
listening-port=8443
tls-listening-port=5349
Specify listening IP, if not set then Coturn listens on all system IPs.
#listening-ip=<IP_ADDRESS>
#relay-ip=<IP_ADDRESS>
These lines enable support for WebRTC
fingerprint
lt-cred-mech
realm=domain.com
Authentication method
use-auth-secret
static-auth-secret=somewords.
total-quota=100
Total bytes-per-second bandwidth the TURN server is allowed to allocate
for the sessions, combined (input and output network streams are treated separately).
bps-capacity=0
This line provides extra security.
stale-nonce
log-file=/var/log/turnserver/turn.log
no-loopback-peers
no-multicast-peers

Elaborate please, I am not using the setting u are asking me..
Should be set as u you suggested?
I will check for those options.. and enable them.

Do u want me to use the console to see its content?
I will be able to to see its content later late tonight pacific time..

I don't same lines but this ones in my Coturn server
usercombo -> "timestamp:myuser"
turn user -> usercombo
turn password -> base64(hmac('mypassword', usercombo))
And set my usercombo content and mypassword in PeerCall default settings?
Does it look correct?

Try updating your config file to contain the following:
{
  iceServers: [{
    urls: "yourdomain.com",
    username: "<your_coturn_username>",
    secret: "<your_coturn_secret>",
    auth: "secret"
  }]
}

On Aug 14, 2017 10:00 PM, "Neumann Valle"<EMAIL_ADDRESS>wrote:
I don't same lines but this ones in my Coturn server
usercombo -> "timestamp:myuser"
turn user -> usercombo
turn password -> base64(hmac('mypassword', usercombo))
And set my usercombo content and mypassword in PeerCall default settings?
Does it look correct?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jeremija/peer-calls/issues/40#issuecomment-322356719,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABa6Ve7nY-Q8l4XfDxkEToZQZbhsc42lks5sYPvJgaJpZM4O29jd
.

I am sorry, I am more confused, should I set the coturn server the way I discribed above and then setup  PeerCalls as ur previous reply?
I am new to this, and not as proficient as I thought I was..

Hi it's working now..
#for PeerCalls settings
fingerprint
lt-cred-mech
#single static user details for long-term authentication:
user=user-you-want-to-user:12352453256482331
#your domain here:
realm=domain.com
Found the answer at
https://stackoverflow.com/questions/26110412/is-long-term-credentials-authentication-mechanism-required-for-webrtc-to-wor


ctrl + alt - p using right alt key and caps lock key (mapped to ctrl) does not work

I'm using a 2015 Macbook Air's built-in keyboard, the physical layout is Italian but I set the ABC layout in the macOS settings,  even though I'm not sure this matters.
It's confusing to explain so I'm just gonna give instructions on how to recreate the bug and, hopefully, you'll be able to reproduce and the issue'll be clear.

Open System Preferences, go to Modifier Keys and set the Caps Lock Key to Control

. Now both the ordinary ctrl key and the Caps Lock key on the keyboard work as ctrl.
In your .skhdrc, remove your ctrl + alt - p mapping if you have one, and add

ctrl + alt - p : osascript -e 'display notification "Hello world!" with title "Hi!"'

.
Now the ctrl + alt - p shortcut is supposed to send a very simple notification.

There are 4 ways to call this combination since we have 2 alt keys and 2 ctrl keys now. One of these ways does not work.

Left alt key
Right alt key

"Caps Lock" key
Works
⚠Does not work⚠

Ordinary ctrl key
Works
Works

The not working combination is Caps Lock ctrl key + Right alt key - p
Are you able to reproduce the issue?

I can reproduce this on a macbook pro (15-inch, 2018) with an american qwerty keyboard.


Base64 attachments

This is a rebase of #12 on top of the current master. I plan to follow up this PR with another one to also expose the locations in the hard drive where the attachments are actually downloaded.

Hi @filipre , it's been a while but I got again some time to work on this. Let me know if there is anything else that I should do to get this and #70 merged.


validate() presentOnly parameter can be used to specify attributes to validate.

The static validate() method on the model provides the presentOnly parameter to indicate that only the provided subset of values should be validated. When desiring to validate only a single modified value this can become problematic if that value depends on other attributes in the model, since the values of those attributes wouldn't be present at the time. Adding those values in is not ideal since it will cause them to be validated as well and requires extra code.
While this might not be a big issue on a server I am investigating the use of Waterline on the client in an isomorphic app. When some attributes require async validation to the server it becomes a big problem if I can't validate one property at a time, but then the issue in the first paragraph may come into play with the current implementation.
My solution is to allow passing the name of a single attribute to validate, or an array of attribute names, on the same presentOnly parameter. This is backwards compatible, and also allows for a wide range of use cases since the entire set of values can be provided with just the specified value(s) validated.
I have added a complete suite of unit tests for my changes.

If you choose to merge this PR, perhaps you would consider another proposal towards client-side use of Waterline: Selectively validating async validation rules or not.
In waterline\core\validations.js lines 165-169 synchronous vs. asynchronous functions (rules) are already handled separately. The only thing left to do is allow passing a flag to actually run the async methods or not.
Where this becomes handy client side is when you might check, for example, that a username is less than 10 characters (done locally) and that it is unique (with a call to the server). The former rule could be checked on every keystroke for immediate feedback, whereas the latter will only be processed once the user stops typing.
I'd love to hear you comments/suggestions, or if you want me to take a bash at it I can do that as well.

The code change and tests look good.
@devinivy, @tjwebb, what do you think?

Looks good :heavy_check_mark:

@dmarcelino Is this waiting for the next minor release? Is there a date scheduled for such a release?
(Since this doesn't introduce breaking changes perhaps it can go in a patch update?)

Thanks @marnusw!

Thanks for merging. :smile:

Changes Unknown when pulling 3ea72cfec24341bb7cf4906d8de096e283e5817f on marnusw:specifyValidatedValues into ** on balderdashy:master**.


GTA IV - Rendering issues on AMD and Intel

Software information
GTA IV at max settings
System information

GPU: RX 580 4GB and UHD 620
Driver: AMDVLK 2019.Q2.2,  RADV Git and ANV 19.0.3
Wine version: Proton 4.2-3
D9VK version: da39227

GTA IV has artifacting issues on AMD and Intel as well. On RADV and ANV the car textures aren't rendered correctly, AMDVLK doesn't have this problem. On Intel, there are even more issues.
AMDVLK:

https://www.youtube.com/watch?v=2EukzCABdhA
RADV:

https://www.youtube.com/watch?v=P1d1mlIO8Z8
Intel:

https://www.youtube.com/watch?v=EIQZd-_AFks
Apitrace file(s)

https://mega.nz/#!DEFnDQLI!G0fkUFzyZSvxbImQbB8xsSFNTX4bt_IWPoOXfbUalG8
For some reason, most of the artifacting visible in the screenshots and the videos above, are not visible when replaying the trace.

Log files

d3d9.log (AMDVLK): GTAIV_d3d9_amdvlk.log
d3d9.log (RADV): GTAIV_d3d9_radv.log
d3d9.log (Intel): GTAIV_d3d9_intel.log

Game seems to render fine on NVidia.
I ran a spirv-val on the shaders and everything seems to be OK -- I checked the shaders and didn't see anything too crazy it was doing.
Need to compile a new version of regular vk val layers to check those (current SDK is completely broken.)

This should be fixed (well, worked around) by the d3d9-hazards branch.

The d3d9-hazards workaround fixed the issue for me, though at the expense of a framerate drop.
I tested the same scene several times, casually observing a drop from 85-110 fps (0.12 release; similar performance to native D3D9) down to 70-85 (d3d9-hazards)
Machine:

Windows 10 1809
Radeon RX 580
Ryzen 2600X

Unfortunately that has to be expected which is why it's a separate branch for now.
We're still looking for a better way to fix it but it's a very tricky problem.

AMDVLK doesn't have this problem

I can actually see this problem with AMDVLK 2019.Q2.5 . Not sure about earlier versions.
I found that when I retrace https://github.com/Joshua-Ashton/d9vk/issues/164 I see the very same corruption as with trace from here, but OP in second issue seemingly does not see any colorful corruption (it's not visible in screenshots). The difference is that OP in seconds thread is on Vega 11, and I am on POLARIS10. hasHazards=true helps in both cases. Is this expected?

This should be fixed in master? Can you try it?

Tested with 0fd76277. Looks just like native D3D9 as far as I can tell. Performance is comparable, too. There's moments where it'll drop from ~110 down to ~65 but I think that's just an underlying limitation of the game engine.
Cheers!


GaMD has adaptive biasing potential

Thanks to All for your "living" review of enhanced sampling methods!
I wanted to point out that GaMD does have adaptive biasing potential during the simulations, and should not be put in section 6.
As shown in the GaMD publications (Refs. 81 and 82) and GaMD website (https://miaolab.ku.edu/GaMD/theory.html), the GaMD boost potential is a harmonic function of the system potential energy at any given time t. Thus it will "adaptively" adjust its value at different simulation frames with updated system potential energy values.
Moreover, we generally run initial short conventional MD to collect potential statistics and GaMD equilibration to optimize the threshold energy E for applying boost potential and the harmonic force constant. Then that will give us optimal acceleration parameters to run the GaMD production simulations. You can find an illustration of the algorithm at: https://miaolab.ku.edu/GaMD/manual.html.
I hope this makes sense and you can put GaMD in the right category of enhanced sampling methods. Thank you!

Hello Yinglong!
Thanks for your comment. I agree with Jérôme that it would make sense to mention GaMD (and also accelerated MD) in the "Adaptive Biasing Potential Methods Using the Potential Energy as a Collective Variable" in Section 7.
However, I am not sure that the bias potential in GaMD is an adaptive biasing potential according to the definition that we use in the review, and how I like to think about it.
If I understand equation 1.1 in https://miaolab.ku.edu/GaMD/theory.html, during a simulation (e.g., the production one), the E and k parameters are kept fixed. Is my understanding correct? Generally, I would consider an adaptive biasing potential where the parameters of the bias potential are changed during the simulation, e.g., the parameters of the bias potential are time-dependent. Thus, if E and k are fixed during a simulation, the bias potential within that single simulation would not be an adaptive biasing potential.
However, I can agree that the whole procedure of running multiple simulations to adjust the boost parameters E and k makes the whole GaMD procedure an adaptive method. Therefore, it makes sense to discuss it in Section 7.
Please let me know if you think I am misunderstanding something or if you do not agree with me.
Omar

Thanks for your insightful thoughts, Omar!
I guess we call "Adaptive Biasing Potential", not "Adaptive Biasing/Boosting/Acceleration Parameters". Broadly speaking, once the biasing potential is time-dependent, it may be adaptive (to the present system state or potential energy). That's my intuitive thought, but yes, it's up to how you define it in the review.
On the same note, the E and k parameters are constantly updated during GaMD equilibration. I actually had an earlier version of GaMD that simply runs "equilibration" until the end of the simulation (so truly adaptive in terms of both the biasing potential and acceleration parameters). However, it didn't show significantly improved sampling power, while at the same time the simulation efficiency/speed was slightly reduced and the biasing potential appeared more noisy for reweighting. That eventually led to the current version of GaMD that runs equilibration to optimize the E and k parameters and then production simulation.
Hope this helps and I'm open to discuss more!
All the best,
Yinglong

Thank you Yinglong, we have updated the text with insight from this conversation.


Add community creation page

This adds the community creation form and a very basic, temporary community header to show off the title and images.
Another major change is an update to the user context. Where I added an explicit property to the context data to tell us whether a user is logged in or not.

PR has been open for over a week. No current frontend members have time to review it.
It's being merged by overriding the requirement for one approval. Adding to https://github.com/sublinks/sublinks-frontend/issues/124 to make sure someone gives this an extra close look in the future.


Exclude specific builtins as an external

I wonder if I can exclude specific builtins as an external to support shimming.
For example:
plugins: [
  autoExternal({
    builtins: {
      include: '*'
      exclude: ['readline']
    }
  }),
  shim({
    readline: "export default {createInterface(){}}"
  })
]

For more granular control:
plugins: [
  autoExternal({
    builtins: {
      include: '*'
+     exclude: {
+	     '@npm/module1': ['readline']
+     }
    }
  }),
  shim({
    readline: "export default {createInterface(){}}"
  })
]

I'll see if I can make this work. Thanks for the suggestion 😄

Untill then, this should work:
import autoExternal from 'rollup-plugin-auto-external';
import shim from 'rollup-plugin-shim';
import builtins from 'builtins';

export default {
  input: 'index.js',
  external: builtins().filter(id => id !== 'readline'),
  plugins: [
    autoExternal({
      builtins: false
    }),
    shim({
      readline: "export default {createInterface(){}}"
    })
  ]
};

I'm thinking about moving the external option to the root of the options object. I don't think this has to be limited to builtins. What do you think @DrSensor?
plugins: [
  autoExternal({
    exclude: ['readline']
  }),
  shim({
    readline: "export default {createInterface(){}}"
  })
]

For more granular control:

Care to elaborate about this @DrSensor? Do you have a specific use case in mind?


Errant layout marker appears before the last character of some files

Shared Program: https://code.world/#PmqhHS7qOj_hBr76jEIJjFA
Description
This program (correctly) fails to compile, but that's not the bug.
Note the layout marker that's to the left of the final x, overlapping the underscore character.  This happens because layout markers are placed by adding a :before rule to the syntax highlighter.  But CodeMirror in this case splits the final token in half, creating a new span for just the last character of the document.  This is fine for fonts and colors, where splitting up the span doesn't change the appearance.  But splitting a token with a layout marker adds a new layout marker.  Oops!

@nixorn FYI, this is cleanup from the layout feature.  It looks like this might require a CodeMirror change to fix, though, and it's not critical.
Though, it may be fixable using CSS... something like span.cm-layout:not(span.cm-layout + *)  Haven't tried it.

I did try :not combined with +, and it doesn't seem to work.

OH!  Actually, the problem comes from the fact that there's a CodeMirror-lint-mark-error style on the last element, and that forces it to be split up.  One fix might be to just ensure that error marks are always applied to complete tokens.

There was a CSS fix after all.


deps: tools: up esbuilt to v0.14.48

Details are here https://github.com/evanw/esbuild/releases/tag/v0.14.48.

https://github.com/kamilsk/dotfiles/commit/6a9194d1583b462bfab8a40d2b2384ca42488cd6


Support for input fields of search type

For input text fields used for the filters, only type="text" seems to be supported.
Please consider also supporting type="search", as filter fields are sort of like search fields too, and we can benefit from the built-in "clear" button implemented by popular browsers.

Yes that's a fair point. I'll look at adding that.

I have made some changes locally while awaiting the next release, hopefully this helps anyone in the same boat:

added input[type="search"] to the selector type to include search inputs as well.
changed the event type from keyup to input. This ensures that any change to the input value, including clicking the built-in "clear" button, and clearing the field with JavaScript, will always trigger the filter to run.

// Line 10, sv-filtable.js
// control types with events
const controlTypes = {
  text: {
    selector: 'input[type="text"], input[type="search"]',
    event: "input",
  },
  ...
};

Thanks! I've added that to the latest release.


Sync master with live

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/Consume-Packages/Package-References-in-Project-Files.md
:white_check_mark:Succeeded

docs/Consume-Packages/Packages-and-Source-Control.md
:white_check_mark:Succeeded

docs/Create-Packages/Dependency-Versions.md
:white_check_mark:Succeeded

docs/Create-Packages/Source-and-Config-File-Transformations.md
:white_check_mark:Succeeded

docs/Schema/Target-Frameworks.md
:white_check_mark:Succeeded

docs/Schema/nuspec.md
:white_check_mark:Succeeded

docs/Tools/Package-Manager-UI.md
:white_check_mark:Succeeded

docs/Tools/PowerShell-Reference.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


skip over any Null values in mappings

This is an extension to the fix for the env mapping and skips over any Null values in RenderedMapppings.
That means, keys are ignored if the value is Null. I do think that's the desired behavior and means we can write stuff like
build:
  number: ${{ 10 if false }}

without error.

Note: even when the value is Null, duplicate keys should not be allowed (see #570)


chore(deps): upgrade runtime dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-runtime-dependencies-k8s-27-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3180

Questions ?
Please refer to the Backport tool documentation


add ElastiCache for rendering results

the user can choose which cache to use

The CLA bot is also failing. Can you either sign the CLA with the same email address as you authored the commits or amend the commits to use the correct email address?

Closing due to inactivity since we are unable to merge this.


support version 0.8.26 now?

Is this a solidity version? If that's the case then can you share any issue that is causing the plugin not work with this solidity version?


[Question] What about the thread safety

Generally, I am interested in your implementation, because I was trying to implement concurrent open-addressed map in the past (and failed).
As I understood, it is not thread-safe variants?
Btw, how it compares to the DictionarySlim?

These hashmaps were not made with concurrency in mind, hence they work fine (wont throw collection modified exceptions)
none the less they should'nt be used in situations were concurrency is key. I might add one in the near future, need to do some research on cas and kcas first.
DictionarySlim still uses chaining which results in alot of cpu cache misses. I wont expect much from this, but ill add some benchmarks this week

Thanks for clarifying. Immediately want to re-try out  my old experiments. Interesting that I did not use Robinhood probing Unsafe stuff and instead was trying approaches from here https://probablydance.com/2017/02/26/i-wrote-the-fastest-hashtable

This hashmap originated from probablydance and is using all tips and tricks :) , mind a few tweaks of my own

DictionarySlim added to benchmarks


error when running Go tests

Not sure quite what's going on - this is a smaller example than my actual test, which doesn't compile, but is sufficient to reproduce the issue. in this test file:
func TestSwap(t *testing.T) {
	a := &Member{
		Track: []tracks.Element{
			{Segment: tracks.TS_MAP[tracks.ELEM_FLAT]},
			{Segment: tracks.TS_MAP[tracks.ELEM_25_DEG_UP]},
		},
	}
	if a.Track[0] != "" || a.Track[1] != "" {
		t.Errorf("expected d to be %v, was %v", dexpected, d.Track)
	}
}

If I call :TestNearest from the a := line, the test runs fine. If I call it from the if statement, I get the following error:
Error detected while processing function WriteAndRunTest..test#run..test#base#build_position..test#go#gotest#build_position..<SNR>94_nearest_test..test#base#nearest_test:
line   18:
E684: list index out of range: 0
E116: Invalid arguments for function add

Not sure what's going on, I haven't dug into the guts of the plugin. Let me know if you need more data about my system. I'm running vim-test commit 5ca90c0.

Thanks, that's all I need to start digging. The error happens when parsing the file for running the nearest test, I just need to correct that function.


client lr_scheduler does not need to be one of DeepSpeed's VALID_LR_SCHEDULES

I think this checking is not necessary and wrong. DeepSpeed supports any of torch.optim.lr_scheduler. Indeed, when specific in the DeepSpeed config, it will first look up the DeepSpeed lr_schedulers (VALID_LR_SCHEDULES), and if not found, used those inside torch.optim.lr_scheduler.    This checking will prevent us from using pytorch's lr_scheduler with DeepSpeed.
https://github.com/huggingface/accelerate/blob/ea36b7dcebd5292afba328291a2ec6361dbcfb9a/src/accelerate/accelerator.py#L1285-L1286
Also, I think the loop here is incorrect. You shouldn't need to do 8 steps when 8 GPUs.  Unless you define a step as 'micro-step' instead of global step.
https://github.com/huggingface/accelerate/blob/ea36b7dcebd5292afba328291a2ec6361dbcfb9a/src/accelerate/scheduler.py#L74-L80

Re; the second, that is correct. Given how accelerate splits the batches of data it's considered a "micro step" https://huggingface.co/docs/accelerate/concept_guides/performance#learning-rates
cc @pacman100 for the DeepSpeed part

@muellerzr  Thanks for replying. I never use without DeepSpeed.  How does it interact with grad_accum_steps? Said, if I increase from 2 GPUs to 4GPUs, from grad_accum_step=2 to 1, same per_gpu_batch_size.  What will happen?
With DeepSpeed, it is definitely wrong (that's what current case, as the lr_scheduler will not be passed to deepspeed.initialize, and fall back to use Accelerator scheduler, which step 8 times for 8GPUs). In DeepSpeed, only one optimizer step will be taken in grad_accum boundary.

Hello @linxihui, it is not wrong or unnecessary. If the user has specified a PyTorch Scheduler, it won't be given to the deepspeed.initialize and it will be wrapped separately by Accelerate to create AcceleratedScheduler object which the user can control separately in their training loop. See, https://github.com/huggingface/accelerate/blob/ea36b7dcebd5292afba328291a2ec6361dbcfb9a/src/accelerate/accelerator.py#L1292-L1298. DeepSpeed docs specify below guidelines for lr scheduler

if the schedule is supposed to execute at every training step, then the user can pass the scheduler to deepspeed.initialize when initializing the DeepSpeed engine and let DeepSpeed manage it for update or save/restore.
if the schedule is supposed to execute at any other interval (e.g., training epochs), then the user should NOT pass the scheduler to DeepSpeed during initialization and must manage it explicitly.

When user specifies custom scheduler in training loop, it would be incorrect to assume that it will be executed every training step, as such we wrap it in AcceleratedScheduler and let user control it in their training loop.
If the scheduler is one of DeepSpeed's VALID_LR_SCHEDULES  or a DummyScheduler with its config specified in the DeepSpeed Config file, then only DeepSpeedEngine object will have the Scheduler whose update it will control. Please refer to the documentation section Important code changes when using DeepSpeed Config File when specifying optimizer or scheduler in deepspeed config file: https://huggingface.co/docs/accelerate/usage_guides/deepspeed#deepspeed-config-file

@linxihui, with respect to scehduler step updates, let us walk through an example to make sure we are on same page and to confirm that things are working as expected:

I specified below optimizer and scheduler config in my ds config file:

"optimizer": {
        "type": "AdamW",
        "params": {
            "lr": "auto",
            "weight_decay": "auto"
        }
    },
    "scheduler": {
        "type": "WarmupDecayLR",
        "params": {
            "warmup_min_lr": "auto",
            "warmup_max_lr": "auto",
            "warmup_num_steps": "auto",
            "total_num_steps": "auto"
        }
    }

Because of this, in my training loop, I will specify DummyOptim and DummyScheduler as shown below:

# Creates Dummy Optimizer if `optimizer` was spcified in the config file else creates Adam Optimizer
 optimizer_cls = (
     torch.optim.AdamW
     if accelerator.state.deepspeed_plugin is None
     or "optimizer" not in accelerator.state.deepspeed_plugin.deepspeed_config
     else DummyOptim
 )
 optimizer = optimizer_cls(optimizer_grouped_parameters, lr=args.learning_rate)

 # Creates Dummy Scheduler if `scheduler` was spcified in the config file else creates `args.lr_scheduler_type` Scheduler
 if (
     accelerator.state.deepspeed_plugin is None
     or "scheduler" not in accelerator.state.deepspeed_plugin.deepspeed_config
 ):
     lr_scheduler = get_scheduler(
         name=args.lr_scheduler_type,
         optimizer=optimizer,
         num_warmup_steps=args.num_warmup_steps,
         num_training_steps=args.max_train_steps,
     )
 else:
     lr_scheduler = DummyScheduler(
         optimizer, total_num_steps=args.max_train_steps, warmup_num_steps=args.num_warmup_steps
     )

Let:
gradient_accumulation_steps=1
num_processes or num_gpus=8,
len(train_dataloader) = 100
num_epochs = 10
lr = 5e-5
num_warmup_steps=0

max_train_steps =  (num_epochs*dataloader_len)/(Gradient_accumulation_steps) = (100*10)/(1) = 1000.
But it needs to be divided by num_processes to account for data parallel. This is done while replacing the auto value of ds config file as shown below:
https://github.com/huggingface/accelerate/blob/ea36b7dcebd5292afba328291a2ec6361dbcfb9a/src/accelerate/accelerator.py#L1270-L1275
So, scheduler.params.total_num_steps=125 (1000/8). Now, DeepSpeed model.step() with call scheduler.step() once for first step to reduce lr to 4.96e-5 (i.e., 5e-5 * (1-1/125)) after step 1.
However, for AcceleratedScheduler doesn't reduce the max_train_steps to 125 and keeps it as 1000. So, after first call to accelerated_scheduler.step() it will result into lr being 4.96e-5 (i.e., 5e-5 * (1-8/1000)) .
So, both result in same lr post first step and so on.

@pacman100  thanks so much for the examples! super detail. I agree with your point.
As a user, who use the high-level interface of  model, opt, lr_scheduler = accelerator.prepare(model, opt, lr_shceduler) with DeepSpeed backend, I'd expect the lr_scheduler  be called by DeepSpeed Engine, i.e., once every global batch, just like passing lr_scheduler to deepspeed.initialize, regardless if it is from torch.optim.lr_scheduler or DeepSpeed's VALID_LR_SCHEDULES.
But now instead, my lr_scheduler is wrapped by AcceleratedScheduler with different executing scheduler.  I think there should be at lease some warning so users know they need to account for #GPUs used, or adding some flag to force it.

Came to this same problem. gradient accumulation and learning rate warm up was not working when using huggingface's get_scheduler function.
To fix it I had to inject Deepspeed so the scheduler is passed to deepspeed.initialize and you get the same behavior you get when using deepspeed under accelerate.
def patch_target_module(
    to_patch: str,
    replace_with: Any,
):
    to_patch = to_patch.split(".")
    assert len(to_patch) > 1, "must have an object to patch"

    to_patch, obj_name_to_patch = to_patch[:-1], to_patch[-1]
    to_patch = ".".join(to_patch)
    source = importlib.import_module(to_patch)
    setattr(source, obj_name_to_patch, replace_with)

from deepspeed.runtime.lr_schedules import VALID_LR_SCHEDULES

new_lr_schedules = deepcopy(VALID_LR_SCHEDULES)
new_lr_schedules.append("LambdaLR")

patch_target_module(
    "deepspeed.runtime.lr_schedules.VALID_LR_SCHEDULES",
    new_lr_schedules,
)

accelerator = Accelerator(
    deepspeed_plugging=...,
)

lr_scheduler = get_scheduler(
    name=args.lr_scheduler,
    optimizer=optimizer,
    num_warmup_steps=args.num_warmup_steps,
    num_training_steps=args.num_epochs * len(train_loader) // grad_accum,
)
model, optimizer, _, lr_scheduler = accelerator.prepare(
    model,
    optimizer,
    train_loader,
    lr_scheduler,
)


ServiceTemplate Lifecycle Management (goals, desired UX specification, etc.)

Goals
In #203  we have implemented state management inside a cluster Template, while this solves some of the use cases of a platform engineering teams and is quite simple to use, it has one big downside: there is no centrals place to define a helmchart/artifact which should be deployed across all clusters, no matter which template they use. Instead you need to define the helmchart/artifact in each template, and if you have many templates updating a single helm chart across all these templates becomes a pain very fast.
The goal of this epic is to allow the platform leads to define, control, and manage the lifecycle of (beachhead) service-specific templates, such as Ingress controllers or other application-level components, while allowing platform engineers to implement and manage those templates across environments.
Goals:

Separation of Concerns: Decouple the management of service/beachhead templates (e.g., Ingress, monitoring solutions) from cluster templates.
ServiceTemplate Lifecycle Management: Allow templates for services to be version-controlled, updated, and managed similarly to ClusterTemplates.
Access Control: Provide granular control for platform leads over who can use which templates, ensuring service templates are only available to approved environments.
Upgrade Path: Allow platform engineers to selectively upgrade service templates, providing a clear upgrade path from one template version to the next.

Major deliverables

ServiceTemplate and ServiceTemplateChain Objects:

Define Helm chart-based templates for services (e.g., beachhead services) using ServiceTemplate objects.
Define ServiceTemplateChain objects to manage the supported versions of service templates and their upgrade paths.

Versioning and Immutability:

ServiceTemplates must be immutable. Each new version of a service must create a new ServiceTemplate object, similar to the ClusterTemplate system.
Platform leads must define which versions are available and manage the upgrade path.

Namespace-Based Access Control:

Implement a system for controlling which namespaces (environments like dev, test, or prod) can access specific versions of ServiceTemplates.
Granular access control should ensure that services are only deployed in approved environments.

Upgrade Mechanism:

Platform engineers must have the ability to choose when to apply a service template upgrade, ensuring there is no unintended impact on running clusters.

TemplateAccess Management:

Define and implement the TemplateManagement object that governs access to both ClusterTemplateChains and ServiceTemplateChains across namespaces.

Who it benefits

Platform Leads: Can control the availability and lifecycle of (beachhead) service templates, ensuring that engineers use only approved and tested service versions.
Platform Engineers: Gain the ability to manage services like Ingress, logging, or monitoring templates independently of cluster upgrades, allowing for more flexible management of the overall stack.

Acceptance criteria
New ServiceTemplate:

Platform leads can create new ServiceTemplate objects and associate them with ServiceTemplateChains.
New service templates must be created when an updated Helm chart version is available (e.g., mirantis-ha-ingress-nginx v1.11.2).

ServiceTemplateChain:

Platform leads can define and update ServiceTemplateChains that specify which versions are supported and what upgrades are available for each template.
Available upgrades for a ServiceTemplate must be clearly defined, allowing platform engineers to see what options they have for upgrading.

ServiceTemplate Updates:

Platform engineers must be able to see when a new service template version is available and apply upgrades to the services independently of the cluster.
TBD:  Updates must be non-disruptive, with the option for engineers to approve upgrades before applying them.

Template Access:

Platform leads can assign ServiceTemplates and ServiceTemplateChains to specific namespaces, ensuring that only approved environments (e.g., dev, test, prod) have access to the correct templates.
New ServiceTemplates created by platform leads or Mirantis are inaccessible to platform engineers until explicitly approved and made available by the platform lead.

Assumptions

ServiceTemplates (Helm charts and CRDs) are immutable, and a new template must be created for every new version.
TBD multiple template repositories (e.g., Mirantis and customer-specific) will be supported.

Note:  The actual deployment and updates of services will be managed by the hmc.mirantis.com system.
Limitations
The epic focuses solely on managing the lifecycle of service templates and the associated access control. It does not cover the validation of the deployed services in the cluster or the monitoring of their health post-deployment.
Out of Scope

Validation of the deployed services.
The actual  BHS Helm charts to be implementation or development of service applications.
Cluster-level lifecycle management (covered in #296 )

User stories

Platform Lead: Define ServiceTemplateChain

As a platform lead, I want to be able to create and manage ServiceTemplateChains for different services (e.g., Ingress controllers) so that I can define supported versions and available upgrades.

Platform Lead: Manage Service Template Access

As a platform lead, I need to control which ServiceTemplates are accessible to specific namespaces (e.g., dev, test, prod) to ensure only approved templates are used.

Platform Engineer: Upgrade ServiceTemplates

As a platform engineer, I want to upgrade the services (e.g., BHS) in my cluster using the latest approved templates so that I can keep my services up to date.

Platform Engineer: View ServiceTemplate Upgrades

As a platform engineer, I need to see which service template upgrades are available so that I can plan and apply updates when needed.

Platform Engineer: Non-disruptive Upgrades

As a platform engineer, I want to apply service template upgrades in a non-disruptive way, ensuring that my running clusters and services are not affected unless approved.

Related implementation GH issues:

#268
#316  (depends on #266)

all actual implementation tasks (for first level of development) completed -> closing this epic where we tracked the original goals / concepts / etc.


Fix repr to work with partially bound expressions

Previously, if you had an expression composed of both symbolics and InteractiveSymbol instances, the repr would call compute, which would error. This fixes that so that compute is only called for fully bound expressions (all leaves have data).
I left the repr alone for now (not touching #1356). As such, bound symbols will display only their name in an expression.
Fixes #1355.

My intent was to merge this before solving the repr issue, but if we can come to a consensus on #1356 before then, I can also fix that here. Ping @llllllllll, @cpcloud, @kwmsmith.

lgtm, I think we can merge this fix before resolving the long term repr because currently this is just broken.

Sounds good. Merging.

@jcrist please add a short summary to the release notes for this bugfix, thanks!


Suggestion: Togglable "Collapse Rich Content By Default"

I think it'd be a nice addition to the web client to be able to choose to see all rich content collapsed by default, or even more granular control to collapse certain types by default.
For instance, sometimes people post gist links, and if you have rich content enabled, the content of that gist is embedded in the chat. You can manually collapse it, but it'd be nice to be able to let it START collapsed, because those things can get quite long sometimes.

You can already disable rich content on a per-room basis. Via the room settings.

I saw that, but then it seems to he completely disabled. My idea is that it
just starts out collapsed and you can expand it manually.
On Sun, Mar 1, 2015, 23:05 Ben Dornis<EMAIL_ADDRESS>wrote:

You can already disable rich content on a per-room basis. Via the room
settings.
—
Reply to this email directly or view it on GitHub
https://github.com/JabbR/JabbR/issues/1218#issuecomment-76659137.


Instructions for running tests on Linux do not work

How do I run the MIEngine test cases on Linux?

I started with README.md which says I need to read the developer guide:
https://github.com/microsoft/MIEngine/blob/a109b93b5855e3895ccb92e0440d92eea1f1d961/README.md?plain=1#L36

The linked developer guide does not exist, however I found a "Testing OpenDebugAD7" page in the Wiki which has instructions for running OpenDebugAD7 tests on Linux.

The instructions have five steps.

(0) "Make sure you have built the solution. See Building MIEngine for VSCode."
MIEngine$ dotnet build src/MIDebugEngine-Unix.sln
Microsoft (R) Build Engine version 17.0.0+c9eb9dd64 for .NET
...
Build succeeded.
MIEngine$ ./PublishOpenDebugAD7.sh -c Debug
##[command] dotnet build /home/grees/github.com/MIEngine/src/MIDebugEngine-Unix.sln -c Debug
...
Build succeeded.
...
##[command] dotnet publish /home/grees/github.com/MIEngine/src/OpenDebugAD7/OpenDebugAD7.csproj -c Debug -r linux-x64 --self-contained
...
##[command] cp /home/grees/github.com/MIEngine/bin/Debug/Microsoft.MIDebugEngine.dll /home/grees/github.com/MIEngine/bin/Debug/vscode/linux-x64/publish/.
##[command] cp /home/grees/github.com/MIEngine/bin/Debug/Microsoft.MICore.dll /home/grees/github.com/MIEngine/bin/Debug/vscode/linux-x64/publish/.

(1) "Make sure you have g++ and gdb installed."
MIEngine$ g++ --version | head -1
g++ (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
MIEngine$ gdb --version | head -1
GNU gdb (Ubuntu 8.1.1-0ubuntu1) 8.1.1

(2) "You will want to use config_gdb.xml as a template for your config_gdb.xml." The link mistakenly goes to config_lldb.xml, and I assume this should be "for your config.xml"

(3) "You will want to create config.xml at <MIEngine_Root>/bin/DebugAdapterProtocolTests/Debug/CppTests"
MIEngine$ cp test/CppTests/TestConfigurations/config_gdb.xml bin/DebugAdapterProtocolTests/Debug/CppTests/config.xml

(4) "Then you should be able to run dotnet test <MIEngine_Root>/bin/DebugAdapterProtocolTests/Debug/CppTests/CppTests.dll"
MIEngine$ dotnet test bin/DebugAdapterProtocolTests/Debug/CppTests/CppTests.dll
Microsoft (R) Test Execution Command Line Tool Version 17.0.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
[xUnit.net 00:00:00.99]     CppTests.Tests.AutoCompleteTests.TestAutoComplete(settings: Gpp/x64/Gdb) [FAIL]
  Failed CppTests.Tests.AutoCompleteTests.TestAutoComplete(settings: Gpp/x64/Gdb) [5 ms]
  Error Message:
   Debug Adapter Path /home/grees/github.com/MIEngine/bin/DebugAdapterProtocolTests/Debug/extension/debugAdapters/OpenDebugAD7 does not exist.
...
Failed!  - Failed:    50, Passed:    14, Skipped:     1, Total:    65, Duration: 24 s - /home/grees/github.com/MIEngine/bin/DebugAdapterProtocolTests/Debug/CppTests/CppTests.dll (net5.0)

(I've trimmed many lines of output from these commands, but I can provide the full details if it will help.)
I suggest that the instructions for running tests on Linux should be brought up to date.

@gareth-rees Thanks for letting us know!
One mistake is that when you build you will need to publish in an area that the test suite knows.
E.g. <MIEngine_Root>/bin/DebugAdapterProtocolTests/Debug/extension/debugAdapter
instead of /home/grees/github.com/MIEngine/bin/Debug/vscode/linux-x64/publish/

One mistake is that when you build you will need to publish in an area that the test suite knows.

Thank you for updating the wiki, I can now run the tests. But note that the publish destination needs to end with .../debugAdapters (with a s), not .../debugAdapter.
MIEngine$ ./PublishOpenDebugAD7.sh -c Debug -o bin/DebugAdapterProtocolTests/Debug/extension/debugAdapters
...
Build succeeded.
...
MIEngine$ dotnet test bin/DebugAdapterProtocolTests/Debug/CppTests/CppTests.dll
...
Failed!  - Failed:     2, Passed:    62, Skipped:     1, Total:    65, Duration: 4 m 59 s - /home/grees/github.com/MIEngine/bin/DebugAdapterProtocolTests/Debug/CppTests/CppTests.dll (net5.0)

Updated.
@gareth-rees Thank for pointing out the issues in our documentation.

Updated Wiki looks good to me and I can follow the instructions and run the test cases. Thanks for fixing the docs!


Hello, I am a Korean developer

Your portfolio is so nice and pretty!
Could you please show me the code to smoothly navigate to that item when I click on something?
Even a simple example...

Hi DoYoung!
Thank you so much!
The code is actually really simple. Add "scroll-behavior: smooth;" in the universal or HTML selector in CSS.
Example from my CSS/main.css code:
html {
color: #222;
font-size: 1rem;
line-height: 1.4;
scroll-behavior: smooth;
}
Hope that answers your question - if not, let me know. :smile:

Can you add code to "scroll-behavior: smooth;" in CSS and JS? The question is the code that goes to the corresponding item when the nav bar is clicked! As a novice developer, I'm sorry for the many questions.

The above example was in CSS. It will do the trick. If have a specific issue you're dealing with, feel free to send a link to your code.

After testing it works fine thank you👍

That's great! 😀


Consider switching from travis to jenkins

We have paid jenkins services. Suggestion to look at this rather than enterprise travis

Close this for inactivity.


Enables per-bundle configuration of auto build

See #389

@miracle2k, looks like build failed because of unavailability of file http://michael.elsdoerfer.name/rjsmin/rjsmin-1.0.1-webassets.tar.gz.

Oh, I got it.
I'll close related issue as resolved.


update triton_ops.py from triton/python/tutorials/06-fused-attention.py

Update deepspeed/ops/transformer/inference/triton_ops.py with latest triton/python/tutorials/06-fused-attention.py,
num_stages = 1 in deepspeed/ops/transformer/inference/triton_ops.py , num_stages=2 in triton/python/tutorials/06-fused-attention.py, because when running stable diffusion inference with deepspeed inference engine with num_stages=2 gives out of memory error (either BLOCK = 64 or num_stages=1)
stable diffusion ineference with deepspeed inference works with latest triton with this update on A100. But the output image is not as good as using triton older version with which now it works
with num_stages=1

with BLOCK=64

@microsoft-github-policy-service agree company="AMD"


Token renewal operation failed due to timeout

Instead of: _renewStates = _renewStates.split(';');
use: _renewStates = _renewStates.split(',');
This can cause the error: Token renewal failed due to timeout

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

ID: 2fc6b567-0762-fb88-e9f6-11482e81a5b2
Version Independent ID: c64e977e-5adf-e31d-955b-1bafae3e9006
Content: Call the Microsoft Graph API using OAuth from your web part
Content Source: docs/spfx/web-parts/guidance/call-microsoft-graph-from-your-web-part.md
Service: unspecified
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

This does seem to be an issue and the suggested fix worked for me.


Create the Organization documentation

We should use a tool like Cacoo to draw the AWS environment and connect the services, it will change in the future, but we need to map what we think until now

The documentation for the organization has already been started with the design, and I am contemplating how we will implement this process.
Options: Terraform, Ansible, CloudFormation, CDK
Im thinking of using Terraform, but it has some warnings, so i dont now if the best option, maybe CDK from the start in this block.

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/organizations_organization

Using cloudformation: https://aws.amazon.com/blogs/security/deploy-aws-organizations-resources-by-using-cloudformation/

Doc to read, may give some insight of better implementation: https://aws.amazon.com/blogs/containers/scaling-iac-and-ci-cd-pipelines-with-terraform-github-actions-and-aws-proton/

Im going to use https://terragrunt.gruntwork.io/ from the start and use terraform to create the organization, i have to validate the aws warning and see what i should not implement using terraform.

For reference the issue for the implementation is #4

Im changing the step of organization a lot after read some documentation, will restart this item after finish the implementation


SCP: The frontend now renders forms and submits them to the server.

The UX could be a lot better, but we'll deal with that next. The point
is the functionality's there.

Here's an example of the endpoints being rendered. Again, this isn't pretty - the point is it works so I can now move on to making it pretty. :-}


WIP : Added ability to deploy K8s environment and fixed DO test cases to use add_host instead of add_machine

LGTM


Workaround about Filters Members for KPIs

This is a first step for working filters: get correct list values for filters.
The problem is that some tMembers contain simple number like an index or amount of child members.
We just do replace them by the key.

@eduard93 check it now


bitmap.Find no longer finds images

bitmap version (or commit ref): v0.10.0-beta3.1
Go version: go version go1.17.6 windows/amd64
Gcc version: gcc.exe (x86_64-win32-seh-rev0, Built by MinGW-W64 project) 8.1.0 (recommended by robotgo's README)
Operating system and bit: Windows 10 64bit
Provide example code:

package main

import (
	"fmt"
	"github.com/go-vgo/robotgo"
	"github.com/vcaesar/bitmap"
)

func main() {
	haystack := robotgo.CaptureScreen(100, 0, 1000, 500)
	needle := robotgo.CaptureScreen(400, 200, 500, 300) // smaller than the one above
	x, y := bitmap.Find(needle, haystack, 0.1)
	fmt.Println(x, y)

	err := bitmap.Save(haystack, "haystack.bmp")
	if err != nil {
		log.Fatalf("saving haystack failed: %s", err)
	}
	err = bitmap.Save(needle, "needle.bmp")
	if err != nil {
		log.Fatalf("saving needle failed: %s", err)
	}

	haystackImg := bitmap.Open("haystack.bmp")
	needleImg := bitmap.Open("needle.bmp")
	x, y = bitmap.Find(needleImg, haystackImg, 0.1)
	fmt.Println(x, y)
}

Description
In another issue I noticed that bitmap.Find has problems finding images in newer versions than<EMAIL_ADDRESS>My initial tests were opening an image to search for from file system (png image) and search it on current screen. To narrow the problem down, I used robotgo.CaptureScreen to get both the "needle" (image to search for) and "haystack" (source image to search in). The results are consistent, and increasing tolerance/precision of the Find function does not help.
go get<EMAIL_ADDRESS><EMAIL_ADDRESS>| go run .
300 200
300 200

go get<EMAIL_ADDRESS><EMAIL_ADDRESS>| go run .
0 0
0 0

go get<EMAIL_ADDRESS><EMAIL_ADDRESS>| go run .
0 0
0 0

Ps. Issue template asks for gcv version - I think bitmap was meant to be there.

Fixed by new robotgo.


Implement affected-by reverse cache

This supercedes #1470 by extending the work there and simplifying the mapping represented in the affected-by cache to be a simple reverse-map of the group-to-constituent map contained in the Group definition. This will simplify updates to the cache and should make it perform a bit better, while also avoiding potential unforseen bugs when using multiple levels of group constituent nesting (groups within groups while also containing repos). If something in the middle of such a chain gets updated, recalculating a fully flattened affected-by mapping could become error prone and would definitely be expensive.
The new code simply stores a reverse map of the constituent mapping, aggregated for all groups. When the affectedBy() method is called, this reverse map is iterated using processed / toProcess sets to avoid recursion. This should be relatively light-weight because we don't need to iterate the cache itself; we're still loading entries by their keys. Memory usage could be a bit higher I suppose, since we might end up storing reverse-mappings for more intermediary groups...but that's not clear, since a fully flattened structure would still contain nearly all of the same references.
Additionally, I added logic to the InfinispanStoreDataManager.init() method that will check whether the affected-by cache is empty. If it is, and while iterating all store definitions for purposes of booting up the by-package-type cache, this method will also create the affected-by reverse mapping for all groups that it knows about. After that point, the refreshAffectedBy method should enable us to maintain the data. Of course, leaving the affected-by cache as an in-memory cache will also work well, and similarly to the by-pacakge-type cache.
Longer term, we need a proper data-driven (not cache-based) store data manager, where we can handle these reverse-mapping optimizations. Until then, I think this will help improve performance a bit.

The failed test is ContentIndexNestedGroupAndStoreDeletionTest. There is an NPE. When a group is deleted it fires postDelete event and ContentIndexManager gets it and fire CacheEntryRemovedEvent. This causes NFCContentListener addMissing throw NPE because it failed to get the store by key. I got a fix at https://github.com/Commonjava/indy/pull/1481, though I am not quite sure what triggers this case.


Question about min-k%

How to explain this pic?

What does Qwen 7b, 14b & 72b mean? Is the result of three size qwen model?
What is the meaning of x-axis?

Yes.
The x-axis is the Min-K% score.


BUG - Fix reaction button position

TO: @bradystroud
CC: @christianmorfordwaitessw
The position of the reaction buttons was changed making them too close to the header and the counters.


Specklecore dotnetstandard build unable to use reflection in a dotnetcore application

Expected Behaviour
lieber specklers,
admittedly this isn't in master yet so fair enough it doesnt work, but.... i'd like to use the dotnetstandard build of SpeckleCore from within a .NET core application in order to run speckle in a linux env
Actual Behaviour
im getting the following exception when using speckle core in another .net core 2 application
System.PlatformNotSupportedException exception when calling Assembly.ReflectionOnlyLoadFrom
Reproduction Steps & System Config (win, osx, web, etc.)
i sucessfully merged master into https://github.com/speckleworks/SpeckleCore/tree/dotnetstandard locally built it then referenced the project in another
windows .NET core 2.1 console application
using System;
using SpeckleCore;

namespace ConsoleApp2
{
    class Program
    {
        static void Main(string[] args)
        {
            SpeckleCore.SpeckleInitializer.Initialize();
            Console.WriteLine("Hello World!");
        }
    }
}

Proposed Solution (if any)
apparently this is to do with the kit initalisation parts, it needs to be changed to not use reflection only load

for the sake of reference, https://www.nuget.org/packages/SpeckleCore/1.7.0-wip should be .net standard 2.0.
I've also started scaffolding some basic tests in this branch, i might continue on those a wee bit.