[HierarchyList] re-render on prop change and fix styling

Closes #927
Summary

Fixed prop re-render comparison bug
Fixed spacing issue

Change List (commits, features, bugs, etc)

Added useDeepCompareEffect with the items dependency to properly re-render
Changed listItem style to use padding-right vs margin-right as the node was being moved when the text was too wide

Acceptance Test (how to verify the PR)

Open HierarchyList story in local dev environment
Change one of the item prop values
See that the element re-renders
Proper testing needs a full implementation such as in Monitor

:tada: This PR is included in version 2.43.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Use script name by default rather than package name

:tada: This PR is included in version 1.3.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


helm create with custom chart.yaml

Helm version: 3.0.3
This might be a feature request rather than a bug as I'm not sure if this was intended behavior.
For our use case we have a various helm templates available for different application types and want to provide preconfigured Chart.yaml files to help enforce naming conventions for different application types.
The issue is that the command helm create charts -p my-template seems to write out its own Chart.yaml ignoring any existing Chart.yaml in my-template.

@laurencee It is intended that the generator overwrites the Chart.yaml. See docs: https://helm.sh/docs/topics/charts/#chart-starter-packs
It is an interesting use case that you raise. To get a better understanding, could you show by example why you would need to keep the Chart.yaml file intact.

@hickeyma Thank you for the prompt reply and I apologies for missing that in the docs. I've updated the title appropriately.
A simple example for our case is that we do not currently use the appVersion field from the Chart.yaml. We also have a convention to use the chart name to determine the names of various other resources such as the docker image name and have documentation to indicate this to users.
We also had planned to display some additional comments above the name field to describe where to see our chart naming conventions.
So given the following chart.yaml
apiVersion: v2
name: replace-me-cron
description: A cron job Helm chart for Kubernetes
type: application

# This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates.
version: 0.1.0

In the _helpers.tpl we have entry defined as such
{{/*
Provide a default image repository value using the name of the chart.
*/}}
{{- define "charts.imageRepository" -}}
{{- if .Values.image.repositoryOverride -}}
{{- .Values.image.repositoryOverride | trunc 63 | trimSuffix "-" -}}
{{- else -}}
{{- $name := (include "charts.name" .) -}}
{{- printf "our.repository.io/%s" $name | trunc 63 | trimSuffix "-" -}}
{{- end -}}
{{- end -}}

From within cronjob.yaml
...
containers:
  - name: {{ .Chart.Name }}
    image: "{{ include "charts.imageRepository" . }}:{{ .Values.image.tag }}"
...

Thanks for describing the use case @laurencee. I have set this as a feature.  Would you be interested in pushing a PR for this?

I'll see if I can figure it out this weekend, haven't written any go before but this seems like as good an opportunity as any.

I ran into the same issue, though I have a separate use case, in my case, I'm looking to create a helm starter with some default chart dependencies.  Since in Helm 3, dependencies are now declared in Chart.yaml, the behavior of rewriting the Chart.yaml eliminates the ability to specify starter dependencies.

As a workaround, I can still declare a requirements.yaml file; though if I have the apiVersion of the starter's Chart.yaml set to v2, then the requirements.yaml file will be omitted from the output chart.
The apiVersion of the output chart will always be set to v2 regardless of whether or not a requirements.yaml exists and disregarding what apiVersion is set to.

Didn't get it sorted out this weekend, I'll give it ago again next weekend but that'll be my last chance for a while as I have lots of weekend things coming after up after that so hopefully no issues.

Leaving this open as a feature request. Let me know if you want to be un-assigned from it.

unassigning due to inactivity.

any update on this?  running into this same issue now

I also have starter charts with dependencies which are lost when creating a chart. Please don't close this issue. This is a needed feature.

I also have starter charts with dependencies which are lost when creating a chart. Please don't close this issue. This is a needed feature.

Same here.  Bump

/assign

Could benefit from this too.


1x1conv Block

Thanks for your great work.
I'm confused about the site of the 1x1conv Block. Could you explain why the 1x1conv block before the avgpool during training and behind the avgpool during testing?

Hi,
Moving the 1x1 conv behind the avgpool during testing is for saving computational cost.


Fix kind.sh development scripts on MacOS

Our Makefiles and scripts largely assume GNU sed, and kind.sh uses sed -z which requires GNU sed. MacOS ships with BSD sed, so to make the existing kind.sh script work, make the sed binary configurable, and pass through the Makefile SED to the script.
Fix kind.sh development scripts on MacOS

Integration tests failed on a panic. Seems to be same as https://github.com/cilium/cilium/issues/24696.

/test

Thanks for this @chancez. This works for me on my Mac M1.

Hit the same error as https://github.com/cilium/cilium/issues/22749 in k8s-1.16-kernel-4.19. This change shouldn't impact any existing e2e style tests from what I can tell, but I'll try re-running it so things are green.

/test-1.16-4.19


IE11 - Stale reference to variable "measureText" can cause permission denied errors from deleted iframes

This can be a pretty obscure case, but because of IE11's security setup (or bug depending on your preference), the variable measureText is holding a stale reference that can make IE11 throw a permission denied error.
Platform: IE11.0.9600
Version 5.8.1
To replicate, do the following:

Create an iframe with a text box inside it.
Initialize CodeMirror on the text box
Programmatically delete the iframe
Try to re-initialize CodeMirror on another item (text box somewhere on the page, does not matter where)

Error will be "Permission denied" on CodeMirror/lib/codemirror.js: Line 2937.
Issue is the following code... (starting at line 2933)
  var measureText;
  // Compute the default text height.
  function textHeight(display) {
    if (display.cachedTextHeight != null) return display.cachedTextHeight;
    if (measureText == null) {
     //.....

var measureText can be holding a stale reference to a child of a deleted element, which FF and Chrome can handle, but IE sees that as a DOM element that no longer be referenced and is a security risk(?).
The change to fix this is simple.  Simply scope var measureText into the function textHeight(display) and remove the conditional check if (measureText == null) { as it is no longer needed.  Code is below:
  function textHeight(display) {
    if (display.cachedTextHeight != null) return display.cachedTextHeight;

    var measureText = elt("pre");
    // Measure a bunch of lines, for browsers that compute
    // fractional heights.
    for (var i = 0; i < 49; ++i) {
      measureText.appendChild(document.createTextNode("x"));
      measureText.appendChild(elt("br"));
    }
    measureText.appendChild(document.createTextNode("x"));

    removeChildrenAndAdd(display.measure, measureText);
    var height = measureText.offsetHeight / 50;
    if (height > 3) display.cachedTextHeight = height;
    removeChildren(display.measure);
    return height || 1;
  }

Using CodeMirror in a window other than the one in which it was loaded isn't supported -- I'm highly surprised it worked at all (it'll fail completely on older versions of Firefox). Until I get around to having a different window per editor (stored as option, used everywhere instead of the global window), that's just the way things are. I don't think your patch is a full solution, and it definitely is a performance liability.

Ah, you are most correct.  Nope, it is not a full solution and was only tested against IE11. :(  I will withdraw the patch as it was not fully test given the breadth of use cases.


⚠ Tada Wallet API has degraded performance

In 408bfe2, Tada Wallet API ($BRIDGE_API_TADA_WALLET_URL) experienced degraded performance:

HTTP code: 504
Response time: 29813 ms

Resolved: Tada Wallet API performance has improved in e851275.


add support for creating vector redisearch indices

Vector RediSearch indices require more information when being created, such as whether to use FLAT or HNSW and the dimensionality of the vector; I have extended the types to allow this
In <FtSearchResult as Deserialize<'_>>::visit_seq I was getting panics due to overflow when seq_size was zero, so I rearranged the code to avoid this. I'm not really sure why seq_size would be zero, but it seems to work fine this way

Hi @laptou ,
Thank you for your contribution!
Could you please add:

tests for your changes
documentation for public structs, enum etc ?

Thank you,
Michaël


Error handling

Currently, bits-to-dead-trees doesn't care about the page's response code, it just takes a screenshot of the page. This can result in PDFs that contain only an error message.
It would be nice if there was an option to only generate a PDF for 200 responses, and return potential errors back to the caller so that our app can decide how to handle them.

I can't assign anyone to this issue, so I'll use the comment: I'm working on this currently.


saltern senior and atmos removal

About the PR
what will atmos do now that they dont have 5 mins of roundstart welding to do!!! :trollface:

youll need to change ur proto next

Oh, thank you! I hate this pump from tritium camera to distro. And fucjing volumetric pumps.

i already removed volumetric pump

Yes, I'm see. I thanking you for this.

first time atmos player's nightmare

second time atmos players dream
maps having atmos removed is good because everyone just removes it roundstart anyway


rpc|test:  Introduce "mnauth" RPC command to fake masternode authentications

Allows to fake verified MN P2P connections. Something i need for an other test. If someone has a better idea how to archive this, let me know :)
Based on #3929

Code looks good but... why?

Something i need for another test.

Can you expand on this a bit pls?

Code looks good but... why?

Something i need for another test.

Can you expand on this a bit pls?

Code looks good but... why?

Something i need for another test.

Can you expand on this a bit pls?

Im working on the QGETDATA/QDATA stuff which should be restricted to be used by masternodes only. At least that was the initial proposed idea from the document and normal nodes should anyway not care about it. And while i was writing tests i realised its not possible to write direct P2P tests if there is such a restriction. Soo, i see/saw the following options:

Not restrict it to masternodes only at all
Not restrict it to masternodes only for -regtest
Not restrict it to masternodes only if some command line parameter is set
Just fake MNAUTH for the testing P2P connection

I mean, actually i like having such a restriction but we could go with 1. if thats not a real concern? I guess the data should be cached then but it would make testing easier. Anyway, i don't like 2. and 3. because it wouldn't be a "full" test thats why i then took 4.

Code looks good but... why?

Something i need for another test.

Can you expand on this a bit pls?

Im working on the QGETDATA/QDATA stuff which should be restricted to be used by masternodes only. At least that was the initial proposed idea from the document and normal nodes should anyway not care about it. And while i was writing tests i realised its not possible to write direct P2P tests if there is such a restriction. Soo, i see/saw the following options:

Not restrict it to masternodes only at all
Not restrict it to masternodes only for -regtest
Not restrict it to masternodes only if some command line parameter is set
Just fake MNAUTH for the testing P2P connection

I mean, actually i like having such a restriction but we could go with 1. if thats not a real concern? I guess the data should be cached then but it would make testing easier. Anyway, i don't like 2. and 3. because it wouldn't be a "full" test thats why i then took 4.

Ok, so you want to use mininode to send/receive these new messages but to do this you want dashd you are connected to to think that this mininode is a masternode, right? Can't you just reuse qwatch for this?

Ok, so you want to use mininode to send/receive these new messages but to do this you want dashd you are connected to to think that this mininode is a masternode, right? Can't you just reuse qwatch for this?

Can't you just reuse qwatch instead?

Hm, not really. Maybe i just don't get how you think that would help but what i basically need is that the connected node has a verified protx hash assigned. This branch is still WIP but See https://github.com/xdustinface/dash/commit/aea5dd77b97c8e151b19497ccef9e60299975afe, https://github.com/xdustinface/dash/commit/03e9edb604bcc549017a9ea66249b06c4942817c. Its already implemented with the fake mnauth in https://github.com/xdustinface/dash/commit/c287a462b7ea60ee809bb2129da17943c3b3186d but im totally open to drop the implementation and this PR if you come up with something else which makes more sense, let me know your thoughts :)

Can't you just reuse qwatch instead?

Hm, not really. Maybe i just don't get how you think that would help but what i basically need is that the connected node has a verified protx hash assigned. This branch is still WIP but See https://github.com/xdustinface/dash/commit/aea5dd77b97c8e151b19497ccef9e60299975afe, https://github.com/xdustinface/dash/commit/03e9edb604bcc549017a9ea66249b06c4942817c. Its already implemented with the fake mnauth in https://github.com/xdustinface/dash/commit/c287a462b7ea60ee809bb2129da17943c3b3186d but im totally open to drop the implementation and this PR if you come up with something else which makes more sense, let me know your thoughts :)

How about https://github.com/xdustinface/dash/commit/aea5dd77b97c8e151b19497ccef9e60299975afe#r45968519 ?

How about https://github.com/xdustinface/dash/commit/aea5dd77b97c8e151b19497ccef9e60299975afe#r45968519 ?

@UdjinM6 Got it now with qwatch! I like the idea, see a55ac9a where i implemented it :) Buut, what do you think about adding both? I mean, the mnauth RPC command is basically useful for tests in general (depending on what we might do in the future with the MNAUTH for sure 🙈), no? And it at least helps in #3953 to somewhat test independent connections like here https://github.com/dashpay/dash/pull/3953/files#diff-2829e166b218f8d2acb7af7fd4e966be5cd8a21c9cc97f13fc29a8fa4a940dc6R274-R303. It's obviously not super important thing to test but it's one more 😄

@UdjinM6 Got it now with qwatch! I like the idea, see a55ac9a where i implemented it :) Buut, what do you think about adding both? I mean, the mnauth RPC command is basically useful for tests in general (depending on what we might do in the future with the MNAUTH for sure 🙈), no? And it at least helps in #3953 to somewhat test independent connections like here https://github.com/dashpay/dash/pull/3953/files#diff-2829e166b218f8d2acb7af7fd4e966be5cd8a21c9cc97f13fc29a8fa4a940dc6R274-R303. It's obviously not super important thing to test but it's one more 😄


Codacy Badge URL Invalid in README.adoc

Describe the bug
I have found that the Codacy badge in the README.adoc is invalid. This image link and related link currently inaccessible, resulting in the badge not displaying.
Outcome
In the Home page, it looks like this:

Expect
Please check the status on Codacy whether is valid, or generate a new badge. Looking forward to your reply.

We actually dont even use Coday anymore so I removed that badge
https://github.com/spring-cloud/spring-cloud-config/commit/78c693b77c81125f7c549413dd312685f2aa4917

We actually dont even use Coday anymore so I removed that badge
https://github.com/spring-cloud/spring-cloud-config/commit/78c693b77c81125f7c549413dd312685f2aa4917

Thanks for your reply also your PR to fix this issue😊.


Fix native file dialogs being shown on set_visible(false)

I was pretty confused when get_tree().root.propagate_notification(Node.NOTIFICATION_WM_CLOSE_REQUEST) popped up all my file dialogs.
Here's a MRP: native-file-dialog-wm-close.zip
Fixes #92946.

Please open a bug report to track this

Thanks!Thanks!


RC2 Notes

This issue tracks release notes, migration guides, and other things of interest to mention in the RC2 release.

Calling out that we should highlight https://github.com/Microsoft/MixedRealityToolkit-Unity/pull/4103 which makes it easier to do an HTK -> MRTK upgrade

https://github.com/microsoft/MixedRealityToolkit-Unity/pull/4211
Hand input recording functionality. Note that because this is actually renaming a class this is technically a breaking change.

#4532 includes two interesting changes for RC2
Introduce the Experimental Attribute
This change includes a new [Experimental] attribute you can attach to a class to denote that the component is experimental. Experimental means a promising idea that we have not yet graduated to a full feature. The component subject to change and not subject to same testing and validations.
Experimental Hand-Attached menu
First experimental feature: a hand-attached menu. Please see #4532 for a description.

Recommendation to add the following into the RC2 Release
Experimental UI UX Features
Some features the MRTK team works on appear to have a lot of initial value even if we haven’t fully fleshed out the details. For these types of features, we want the community to get a chance to see them early. Because they are early in the cycle, we label them as experimental to indicate that they are still evolving, and subject to change over time.
Please read the following page for more details: https://github.com/microsoft/MixedRealityToolkit-Unity/wiki/Experimental-UI-UX-Features

For UX controls, Slider is newly added after RC1 release.
https://github.com/microsoft/MixedRealityToolkit-Unity/blob/prerelease/2.0.0.rc2_stabilization/Documentation/README_Sliders.md


Google Assistant: make it possible to set a custom domain/type

Makes it possible to map for example switch to light in Google Assistant.
Some wall switches which controls ceiling lights etc are reported as a switch in hass.
This makes it cumbersome to use Google Assistant as you need to issue to voice commands.
hey google, turn off the lights in bedroom or hey google, turn off bedroom. The latter would also turn off outlets etc.
Example customize:
switch.bedroom_switch:
  friendly_name: "Bedroom, ceiling"
  google_assistant: true
  google_assistant_type: 'light'

Flush installed fibaro dimmer 2 are reported as "light" (as it has a dimmer).
How is the flush Fibaro Switch reported? (the one without dimmer).
My wall switch is reported as switch.

So far, seems to work great for me! Groups seem to be the only method that didn't work, but I wouldn't hold this back for that.
For troubleshooting (also posted this at #10111), I tried setting a group as type light and switch and got the following error: WARNING (MainThread) [homeassistant.core] Unable to find service group/turn_on

Right, group doesn't have a turn_on service.
I guess they need homeassistant.turn_on

Awesome 🌮


Update documentation generation

In the documentation the section "direct childs" should be "direct children". This commit updates the genericSpecFunctions.xsl and generateGuidelines.xsl to correct this, as well as renaming 'childs' to 'children' throughout the code.

3 more childs in the code basis: https://github.com/music-encoding/music-encoding/search?q=childs

thanks everyone


XCDYouTubeVideoPlayerViewController "Implementing deprecated class" Warning

I've just this evening updated to version 2.8.1 (from 2.6.0) and am now getting the following warning:
XCDYouTubeVideoPlayerViewController.m
@implementation XCDYouTubeVideoPlayerViewController
Implementing deprecated class
Short of turning off or ignoring warnings in XCode can you please advise as to what I need to do to clear this warning? Thank you.

I do now see the issue -- XCDYouTubeVideoPlayerViewController inherits from the deprecated iOS MPMoviePlayerViewController class, i.e.:
@interface XCDYouTubeVideoPlayerViewController : MPMoviePlayerViewController
Should I just ignore the warning? (Or is there a way to clear the warning that I've missed?)
Thank you.

I meet the same warning,

It's a crashing app in iOS 13+
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'MPMoviePlayerViewController is no longer available. Use AVPlayerViewController in AVKit.'

I silenced the warning in https://github.com/0xced/XCDYouTubeKit/commit/b12328732456196020e22f9f79e46ef692a7bf94
if you're targeting iOS 13.0+ do not use XCDYouTubeVideoPlayerViewController instead use XCDYouTubeClient or XCDYouTubeVideoOperation


TypeError in /clan/bharat-2-pq290u82

Error in ClashLeaders
TypeError in /clan/bharat-2-pq290u82
Cannot read property 'forEach' of undefined
View on Bugsnag
Stacktrace
webpack:///node_modules/chartist/dist/chartist.js:3408 - null.<anonymous>

View full stacktrace
Created automatically via Bugsnag

An error linked to this issue has been marked as fixed in Bugsnag
TypeError in /clan/american-bacon-9jgcvypl

An error linked to this issue has been reopened in Bugsnag
TypeError in /clan/mustafa-hack-vvj9qyrr

An error linked to this issue has been marked as fixed in Bugsnag
TypeError in /clan/rising-legends-ygrqjjqr

An error linked to this issue has been reopened in Bugsnag
TypeError in /clan/pamsus-1-y0prcgqg

An error linked to this issue has been marked as fixed in Bugsnag
TypeError in /clan/awsomeness-pyq8pqyl

An error linked to this issue has been reopened in Bugsnag
TypeError in /clan/indian-friends2-88uq8j0

An error linked to this issue has been marked as fixed in Bugsnag
TypeError in /clan/russiberiano-br-qjv8ql20

An error linked to this issue has been reopened in Bugsnag
TypeError in /clan/tegal-bersatu-9lp0vc0p

An error linked to this issue has been marked as fixed in Bugsnag
TypeError in /clan/jngjwyn-mgrwr-vquuu9uj


fix: do not create a git repo when already in a git repo

closes https://github.com/graphprotocol/graph-tooling/issues/1450

Checking in on this @saihaj, did my comment make sense or did I read it wrong?


Support for older browsers eg. chrome 45

Hi there,  this is not an issue but a question -
There seems to be es6 dept for this lib which could cause issue for older browsers -  any suggestion on alternative or what can be done to address this?  Fairly new to google oauth here.
Thanks in advance and this has worked well so far,  except the compatibility requirement :(

@jeremycy I'm sorry but Chrome 45 version is very old, and I wouldn't update the build to bundle to very old bundle
you can copy and paste the implementation from the source code and take it in your project directly


default-import doesn't include source map file

At the end of dist/default-import.js, there is //# sourceMappingURL=default-import.js.map. However, default-import.js.map is not included in the NPM package. Some bundlers would complain about this because they cannot find the source map.
WARNING in ./node_modules/default-import/dist/default-import.js
Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from '/Users/ocavue/code/github/remirror-examples/with-create-react-app/node_modules/default-import/dist/default-import.js.map' file: Error: ENOENT: no such file or directory, open '/Users/ocavue/code/github/remirror-examples/with-create-react-app/node_modules/default-import/dist/default-import.js.map'

webpack compiled with 16 warnings

It would be great if we can remove this comment from default-import.js or just include the generated source map in the NPM package.

Can you give an example of a bundler that would expect source map files to exist for dependencies?
That source map is written/maintained by typescript when generating that file, so it only exists locally for test/debug. I do not include that map + source file in the final output because those files are not executable, nor provide any extra context that the d.ts file does not, and would therefore only add possible confusion of what files are actually being executed.
While I am surprised there are errors on "misleading" //# sourceMappingURL=default-import.js.map, I can agree that the comment on published files is useless at best.
I'm open to removing this comment from all .js files before publishing to npm. Do you know of any good existing packages to do that? Otherwise probably would not be too hard to implement this manually... Just scan /dist for files with //# sourceMappingURL=... at end of file and strip out that line.
BTW thanks for the first issue!

Can you give an example of a bundler that would expect source map files to exist for dependencies?

$ git clone https://github.com/remirror/remirror-examples
$ cd remirror-examples/with-create-react-app
$ yarn install
$ yarn build

Failed to parse source map from '/Users/ocavue/code/github/remirror-examples/with-create-react-app/node_modules/default-import/dist/default-import.js.map' file: Error: ENOENT: no such file or directory, open '/Users/ocavue/code/github/remirror-examples/with-create-react-app/node_modules/default-import/dist/default-import.js.map'

Do you know of any good existing packages to do that?

The simplest way would be not to generate the source map by setting sourceMap:false in tsconfig.json.

not to generate the source map
🤦
I could not see the forest for the trees...

Should be fixed via https://github.com/JacobLey/jacobley/commit/8db8dff86fd759f3d5d030243aa6d261ffd885d5 and released with 1.1.3


Client Login- Mobile App

Client ko invite karna hai
us client k jo bhi email address ho us se woh login kar sakta hai
agar ek email multiple client me use hua hai toh invite karne pe error message dikhao email is linked with another contact kindly provide unique email
client invite ka ek unique url ho accountant company ka. client us url ko kholega and apna email id dalega toh woh connect ho jayega us accountant company k sath agar usko invite bheja hai toh

@Harsheasy I Required Video of current Process here

GO WITH EXISTING SOLUTION JUST PROVIDE EMAIL INVITE AS WELLBESIDES SMS


stop at win

Game should stop at winning position

This has been solved. I added a win screen that tells who won at the end of the game.


Unable to build or start fresh hugo server

Below you'll find every command I've run to reach the error, as well as the hugo version. I'm using the hugo package available from the apt on Debian 11.
root@nasko:/data/Shared/hugo# hugo new site test
Congratulations! Your new Hugo site is created in /data/Shared/hugo/test.

Just a few more steps and you're ready to go:

1. Download a theme into the same-named folder.
   Choose a theme from https://themes.gohugo.io/ or
   create your own with the "hugo new theme <THEMENAME>" command.
2. Perhaps you want to add some content. You can add single files
   with "hugo new <SECTIONNAME>/<FILENAME>.<FORMAT>".
3. Start the built-in live server via "hugo server".

Visit https://gohugo.io/ for quickstart guide and full documentation.

root@nasko:/data/Shared/hugo# cd test

root@nasko:/data/Shared/hugo/test# git init
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint:   git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint:   git branch -m <name>
Initialized empty Git repository in /srv/dev-disk-by-uuid-bc1f180e-8a5d-461f-871b-58c9f1e9b0d6/Shared/hugo/test/.git/

root@nasko:/data/Shared/hugo/test# git submodule add https://github.com/LordMathis/hugo-theme-nightfall themes/nightfall
Cloning into '/srv/dev-disk-by-uuid-bc1f180e-8a5d-461f-871b-58c9f1e9b0d6/Shared/hugo/test/themes/nightfall'...
remote: Enumerating objects: 290, done.
remote: Counting objects: 100% (78/78), done.
remote: Compressing objects: 100% (32/32), done.
remote: Total 290 (delta 56), reused 50 (delta 46), pack-reused 212
Receiving objects: 100% (290/290), 985.58 KiB | 3.71 MiB/s, done.
Resolving deltas: 100% (129/129), done.
root@nasko:/data/Shared/hugo/test# echo "theme = 'nightfall'" >> config.toml

root@nasko:/data/Shared/hugo/test# cat config.toml
baseURL = "http://example.org/"
languageCode = "en-us"
title = "My New Hugo Site"
theme = 'nightfall'

root@nasko:/data/Shared/hugo/test# hugo
Start building sites …
Total in 44 ms
Error: Error building site: failed to render pages: render of "home" failed: execute of template failed: template: index.html:24:23: executing "index.html" at <partial "social.html" .>: error calling partial: "/data/Shared/hugo/test/themes/nightfall/layouts/partials/social.html:3:17": execute of template failed: template: partials/social.html:3:17: executing "partials/social.html" at <sort .Site.Params.social "key">: error calling sort: sequence must be provided

root@nasko:/data/Shared/hugo/test# hugo version
Hugo Static Site Generator v0.80.0/extended linux/amd64 BuildDate: 2021-07-18T09:31:51Z (debian 0.80.0-6+b5)

root@nasko:/data/Shared/hugo/test# hugo server
Start building sites …
Built in 18 ms
Error: Error building site: failed to render pages: render of "home" failed: execute of template failed: template: index.html:24:23: executing "index.html" at <partial "social.html" .>: error calling partial: "/data/Shared/hugo/test/themes/nightfall/layouts/partials/social.html:3:17": execute of template failed: template: partials/social.html:3:17: executing "partials/social.html" at <sort .Site.Params.social "key">: error calling sort: sequence must be provided

root@nasko:/data/Shared/hugo/test# hugo version
Hugo Static Site Generator v0.80.0/extended linux/amd64 BuildDate: 2021-07-18T09:31:51Z (debian 0.80.0-6+b5)

Really like the look of the theme, would appreciate some help getting it running, or a fix to the issue if indeed it is one :)

I have added the configurations from the readme to my config.toml and the issue has gone away. It appears this may be an issue where the theme assumes these configurations may be available, and if they aren't, it will throw an error.
I understand this is at its core a user issue, but it might be nice to provide a user-friendly message when and if one attempts to use the theme without these configurations in place.

You are right that this is an issue with some expected configuration missing. Specifically the theme expects at least one item in [[params.social]].
I can't do anything about the error message since that is coming from hugo and not the theme.
The theme should definitely render even without any social links


Add repr_html for CubeLists

As a (long-delayed) follow-on to a previous PR to add cube html repr (see #2918), this adds html repr functionality to CubeList objects. The html repr is designed to be reasonably simple, retaining the content of the original CubeList repr while adding an accordion effect that, when a cube in the list is clicked, expands to reveal the html repr of that cube.

For want of a properly interactive notebook that demonstrates this in operation, here's a static screengrab of what the repr looks like (with one cube in the list expanded to show the embedded cube repr):

@DPeterK Fancy doing a re-base?
We just fixed the travis-ci tests on master, and I'm hoping this will tidy up your CI failures.
Reference https://github.com/SciTools/iris/issues/3349

Ping @DPeterK :wink:

@bjlittle ping noted; unfortunately I'm busy now! I'll see what I can do.

@DPeterK No worries :wink:

@bjlittle I did it 😁

... shame the tests still didn't pass :(

I've updated the CSS for the cubelist repr, including making use of jupyter variables to define elements of the style. This means the cubelist repr will correctly follow jupyter lab themes. When combined with #3380 the cubelist repr now looks like the following:
Light theme:

Dark theme:

@DPeterK Awesome, LGTM :+1:


Add more compression types for to_json

This PR adds bz2, xz, and zip (WIP) for to_json. I also plan to add infer like how pandas does it

I looked into how to compress with zipfile for which few methods exists, let me know which one looks good:

create the file in normal wb mode and then zip it separately
use ZipFile.write_str to write file into the archive. For this we'll need to change how we're writing files from _write method

How pandas handles it is that they have created a wrapper for standard library class ZipFile and allow the returned file-like handle to accept byte strings via write method instead of write_str (purpose was to change the name of function by creating that wrapper)

sounds not ideal since it creates an intermediary file.
I like pandas' approach. Is it possible to implement 2. using the pandas class ? Or maybe we can have something similar ?

Definitely, @lhoestq! I've adapted that from original code and turns out it is faster than gz compression. Apart from that I've also added infer option to automatically infer compression type from path_or_buf given

One small thing, currently I'm assuming that user will provide compression extension in path_or_buf. Is it this also possible?
dataset.to_json("from_dataset.json", compression="zip")?
Should I put an assert to ensure the file name provided always has a compression extension?

Thanks !

One small thing, currently I'm assuming that user will provide compression extension in path_or_buf. Is it this also possible?
dataset.to_json("from_dataset.json", compression="zip")?
Should I put an assert to ensure the file name provided always has a compression extension?

I think it's fine as it is right now :) No need to check the extension of the filename passed to path_or_buf.

turns out it is faster than gz compression

I think the default compression level of gzip is 9 in python, which is very slow. Maybe we can switch to compression level 6 instead which is faster, like the gzip command on unix

I found that fsspec has something that may interest you: fsspec.open(..., compression=...)
It also has zip if I understand correctly ! see https://github.com/fsspec/filesystem_spec/blob/master/fsspec/compression.py#L70
Since fsspec is a dependency of datasets we can use all this :)
Let me know if you prefer using fsspec instead (I haven't tested this yet to write compressed files). IMO it sounds pretty easy to use and it would make the code base simpler

Just tried fsspec but I'm not able to write compressed zip files :/
gzip, xz, bz2 are all working fine and it's really simple (no need for FileWriteHandler now!)


[Bug]: Using latest SWC rule, swc crash while not finding 'base_dir'

What happened?
While running the latest version of SWC rules, it crashes with this error:
ERROR: /Users/romain/git/oidc/packages/i18n/express/BUILD:25:11: Compiling //packages/i18n/express:ts_transpile [swc packages/i18n/express/src/i18n.ts] failed: (Exit 101): swc-darwin-arm64 failed: error executing command (from target //packages/i18n/express:ts_transpile)
  (cd /private/var/tmp/_bazel_romain/aab898f10bfeb90def8d69f3c9616e24/sandbox/darwin-sandbox/1652/execroot/com_shadow_cbp && \
  exec env - \
  external/swc_darwin-arm64/swc-darwin-arm64 compile --source-maps true --source-file-name ../src/i18n.ts --source-root packages/i18n/express --config-file bazel-out/darwin_arm64-fastbuild/bin/packages/i18n/express/.swcrc --out-file bazel-out/darwin_arm64-fastbuild/bin/packages/i18n/express/src/i18n.js packages/i18n/express/src/i18n.ts)
# Configuration: 7f308466bd98cfb2b391af4037586009214979163f843b0f91a1705af46bb64c
# Execution platform: @local_config_platform//:host

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
thread 'main' panicked at 'base_dir(``) must be absolute. Please ensure that `jsc.baseUrl` is specified correctly. This cannot be deduced by SWC itself because SWC is a transpiler and it does not try to resolve project details. In other works, SWC does not know which directory should be used as a base directory. It can be deduced if `.swcrc` is used, but if not, there are many candidates. e.g. the directory containing `package.json`, or the current working directory. Because of that, the caller (typically the developer of the JavaScript package) should specify it. If you see this error, please report an issue to the package author.', /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/swc_ecma_transforms_module-0.173.38/src/path.rs:104:13

Version
Development (host) and target OS/architectures:
Output of bazel --version:
bazel 7.1.1
Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file:
rules_swc-1.2.2
rules_ts-2.2.0
rules_js-1.40.0
Language(s) and/or frameworks involved:
TS
How to reproduce
No response
Any other information?
While upgrading from rules_swc-1.1.0 to rules_swc-1.2.2

Some more info:
Version 1.2.2 works with SWC SWC_VERSION = "v1.3.75" but doesn't with LATEST_SWC_VERSION (v1.3.78)

Error lies between version SWC v1.3.75 and v1.3.76

Probably due to this fix:
https://github.com/swc-project/swc/pull/7775

Ok, I've found the solution:
With new versions of SWC, if you specify path rewrite, you need to specify a baseUrl.
For exemple if you have this in you .swcrc:
"jsc": {
...
  "paths": {
      "i18next": [
        "./node_modules/i18next"
      ]
    },
...
}

You have to specify:
"jsc": {
...
    "baseUrl": "."
  }
...
}

Thanks for following up and recording your findings 👍


[Feature Fix] Fixed search nodes not updating

Purpose
Closes #2565.  Previously, the users information would not update in elastic search when they changed it.  This PR addresses and fixes this issue.
Changes
All relevant code was already created, but the "update_search" method in framework/auth/core.py was missing a method call.  Adding this line fixed the issue.
Side effects
Currently this is being called every time a user changes any information on their profile.  Since not all changes will show up in elastic search (i.e. if they change their employment), this may have some performance issues.  This could be later addressed by making it asynchronous or making the method call only if the user changed information that would show up in elastic search.

This issue has been previously reported in #1237 -- there's some discussion about performance concerns that you should take a look at! :sunglasses:

Closing in light of duplicate PR (#2956), which addresses the performance concerns mentioned above.


Move transport test-suite out of tree

Resolves #286

Pull Request Test Coverage Report for Build 1363

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.004%) to 28.479%

Totals

Change from base Build 1344:
0.004%

Covered Lines:
2192

Relevant Lines:
7697

💛  - Coveralls


Failed at the<EMAIL_ADDRESS>prebuild script

Hi
I get an error on npm run build with latest node and npm release
assert.js:89
throw new assert.AssertionError({
^
AssertionError: Current node version is not supported for development, expected "5.7.0" to satisfy "4.x".

npm ERR! Darwin 15.3.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
npm ERR! node v5.7.0
npm ERR! npm  v3.7.3

In a similar vein I get an assertion exception using NPM 3.7.5 and Node 4.3.0
AssertionError: Current npm version is not supported for development, expected "3.7.5" to satisfy "2.x".
at /$HOME/draft-js/node_modules/fbjs-scripts/node/check-dev-engines.js:57:5

In my case, just running gulp seems to build it successfully.

@taggon thank you. gulpbuild successfully

Is there a hard dependency on a particular version of Node?  I notice it failed with<EMAIL_ADDRESS>as well.  If things work fine then perhaps the version check should be relaxed?

@taggon, you're completely correct. Running gulp builds the package just fine. Seems peculiar that there's such a strict Node/NPM version check. Works fine on 4.3.0-4.3.1(LTS) and 5.7.0(Stable) using NPM 3.7.5

Also wondering why does the check for 4.x exists ? What are the current incompatibilities ? Are they listed anywhere that we could submit PR's ?

The dependency on node 4 is not a hard dep. But npm 2 is so that we can run our tests. See #37 where we're going to make it so it's possible to build with npm3 but if you try to contribute and run tests you'll get stopped.

I assume we're ok here?


LEO Staff logs

Describe the feature
Currently AFAIK there is no way to know for commanding officers who has e.g. revoked the license, who accessed what files and when.
It would be great to have some frontend where Police/EMS/FD supervisors would see logs of their officers.
Additional Context
No response

duplicate of #914. At this time, this is a bit to large for me to handle. I'll see what I can do

Closing this for now and moving to backlog. I currently don't have the resources to work on this. I'll create a draft issue soon with a long-term solution to this and #914


[Antipattern]

% Rendering into JavaScript
severity: 4
type: antipattern
tags: []
layers: [templates, views]
related_packages: []
Often one wants to pass some data to JavaScript and to do that one renders into JavaScript using Django. for example:
<body>
Body Content
<script>
    let a = {{ var_1 }};
    let b = "{{ var_2|safe }}";
</script>
<script>
    let c = {{ var_3|safe }};
</script>
</body>

Why is it a problem?
This is very unsafe and it makes one vulnerable to XSS attacks. Let us consider that the values of the variables rendered above are provided from the user. For demonstration purposes below is some view code with these variables set to such values that each of them will cause an alert:
import json

def test_xss(request):
    context = {
        'var_1': 'alert(1)',
        'var_2': '";\nalert(2);\n"',
        'var_3': json.dumps('</script><script>alert(3);</script><script>')
    }
    return render(request, 'test.html', context)

This snippet might not cause much damage, but it can be much more dangerous. It can also be seen that even using json.dumps is not very safe here.
What can be done to resolve the problem?
Don't render from Django into JavaScript, instead use the json_script template filter [Django-doc] and parse it's results using JSON.parse:
<body>
Body Content
{{ var_1|json_script:"var-1-json" }}
{{ var_2|json_script:"var-2-json" }}
{{ var_3|json_script:"var-3-json" }}
<script>
    let a = JSON.parse(document.getElementById('var-1-json').textContent);;
    let b = JSON.parse(document.getElementById('var-2-json').textContent);;
</script>
<script>
    let c = JSON.parse(document.getElementById('var-3-json').textContent);;
</script>
</body>

Thanks! Now published here: https://www.django-antipatterns.com/antipattern/rendering-into-javascript.html


Remove version: WHONET.2023 version 23.13.17

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Sequence contains no elements

#133371

Sequence contains no elements

https://github.com/microsoft/winget-pkgs/issues/133371

(Automated response - build 642.)

Automatic Validation ended with:

2024-01-20T04:01:37.6853367Z Processing manifest: manifests\w\WHONET\2023\23.13.17
2024-01-20T04:01:37.6864101Z -----------------------------------------------------
2024-01-20T04:01:37.6869115Z Status: Started
2024-01-20T04:01:37.6877514Z Manifest file is Deleted
2024-01-20T04:01:37.9198054Z Status: Completed
2024-01-20T04:01:37.9206184Z ##[error] Result: Failed
2024-01-20T04:01:37.9215341Z ##[error] Sequence contains no elements
2024-01-20T04:01:37.9823363Z ##[error]Manifest Validation Failed

(Automated response - build 642.)

URL: https://whonet.org/WHONET2023-Setup-x86.exe
Status Code: 200
(Automated message - build 642)


Dialogset constructor gives error

dialogs = new DialogSet(); gives error that it takes the IstatePropertyAccessor as  a parameter.
How shall I continue?
Thanks,
Vivek

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

ID: 95db9168-d434-3461-ab0d-c623c27800a6
Version Independent ID: f3463efe-3ba7-385a-f2b4-9398fb5028de
Content: Ask the user questions - Bot Service
Content Source: articles/v4sdk/bot-builder-tutorial-waterfall.md
Service: bot-service
Product: bot-framework
GitHub Login: @v-ducvo
Microsoft Alias: v-ducvo

The content that you are looking at is not in the TOC and is outdated. The correct link is: https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-prompts?view=azure-bot-service-4.0&tabs=csharp.
I've removed the old content and the site will be updated soon.


Caused by: java.lang.IllegalArgumentException: Supported locales are 'English' and 'Arabic'

App crashed in case of multi-language supported app. In my use case using Bengali-BD "bn" language this error has been found.
Error-     Caused by: java.lang.IllegalArgumentException: Supported locales are 'English' and 'Arabic'

App crashed in case of multi-language supported app. In my use case using Bengali-BD "bn" language this error has been found.
Error- Caused by: java.lang.IllegalArgumentException: Supported locales are 'English' and 'Arabic'

Update this dependency to version 1.2.0:
implementation group: 'com.github.msarhan', name: 'ummalqura-calendar', version:'1.2.0'

@dzemalibric Please share more details so that I can help you fix the issue.

App crashed in case of multi-language supported app. In my use case using Bengali-BD "bn" language this error has been found.
Error- Caused by: java.lang.IllegalArgumentException: Supported locales are 'English' and 'Arabic'

Update this dependency to version 1.2.0:
implementation group: 'com.github.msarhan', name: 'ummalqura-calendar', version:'1.2.0'

Thank you! Worked me 👍


Cbr module waits

Need to add wait function after creation, current in state of module impossible to update cbr after creation

done in #278


Add CVA for simplifying variant management

To clean up how we deal with Tailwind classes and component variants, might want something a little more robust than what I'm currently doing (classnames/clsx and toggling class chunks based on states + variants combinations).
Looks like CVA is a popular choice for something like this: https://cva.style/docs/getting-started

Obsolete in beta.1


Shared states

All instances of {{ember-scrollable}} appear to share state.
If I hover over one container, not only the scrollbar of this container fades in, but all other containers do the same. Also, when using scrollTo, all containers scroll to that position.

Correction: the synced scrolling was my bad. However, I still have both scrollbars fading in and out synchronously. Is this intended behavior?

I still have both scrollbars fading in and out synchronously. Is this intended behavior?

@buschtoens I believe so. When you hover over a scrollable div, the scrollbars should fade in to show the user that they can scroll either horizontally, vertically, or both.

I think I wasn't wording it clearly enough. I mean in two separate scroll
containers.
On Thu, Feb 2, 2017, 21:16 Offir Golan<EMAIL_ADDRESS>wrote:

I still have both scrollbars fading in and out synchronously. Is this
intended behavior?
@buschtoens https://github.com/buschtoens I believe so. When you hover
over a scrollable div, the scrollbars should fade in to show the user that
they can scroll either horizontally, vertically, or both.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/alphasights/ember-scrollable/issues/46#issuecomment-277070489,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAy8THwCx5vgP8WDBb-P440PYKZyQV_Gks5rYjmGgaJpZM4L1ZD_
.

@buschtoens oh... I dont think that is intended....


'naturalWidth' of undefined

Component not loaded, switch page appears "'naturalWidth' of undefined".

which version are you using?

Im getting a similar error a few minutes after it runs.
" Cannot read property 'width' of undefined "
please help

Hello, that use to happen when the image is not found, maybe wrong name or path.
check the dev tools network tab to identify which one.
regards

I also get the error "Cannot read property 'width' of undefined"
Error encountered when changing the browser size that the slider is running.
Or when viewing the full screen image and exit that slider is running.
https://uphinh.org/image/MkE4xT

I investigated the error as a result of FluxTransition.
At funtion style in the computed section.
this.size undefined

Thanks, I will review it and make a new release in the next days.
Regards!

New release ready :)
Now on resizing, if there is a transition running will cancel it.


Hello, may I ask if you have any pre-training parameters that have not been released? Why is r1 only 0.2 when I use the model to run msrvtt data, is the cross_pytorch_model.bin file not released?

04/10/2023 19:25:53 - INFO -   Weights from pretrained model not used in CLIP4Clip:

did you download weights from CLIP4Clip? Our model is initialized with a zero gate. So, the worst case is identical to CLIP4Clip

I'd like to run the MSRVTT dataset using the ECLIPSE model, and I found that when evaluating the test set directly with the model, the R@1 value is normal at 26. However, when fine-tuning on the MSRVTT dataset, the R@1 value becomes very low, like 0.1 or 0.2, which is quite strange. Do you know the reason for this, or have you ever worked with the MSRVTT dataset? Could you please tell me the values you obtained when running the MSRVTT dataset?

I am primarily interested in referencing and comparing your method with mine in a research paper, and I hope to receive your assistance in this matter

Based on my experience, the batchsize cannot be too small, and the learning rate cannot be too large.
You can also check the learning rate at CLIP4Clip

Yes, but after fine-tuning, the R@1 value is around 0.1, which is basically equivalent to random guessing. When not fine-tuned, the R@1 value is quite normal. It doesn't seem to be an issue with the parameter settings.

Thank you, let me try your suggestion first.

learning rate is 1e-4

Thank you, you are correct.


Source S3 bucket dropdown in Create Event page does not list any buckets

Hello!
When attempting to create Events through the MRE UI, the dropdown menu labeled "Source S3 Bucket" is an empty drop-down menu. I am however, able to create an event by going to API Gateway in the AWS console and manually sending the POST request with the required information (including the S3 bucket), and MRE has no issues accessing that bucket (i.e. it can place a trigger on it, read objects from it, etc.). However, it would be more convenient to use the UI. I have S3 buckets that are in the same region as MRE. Why might nothing show up in the dropdown? Thank you!

Hi @marcos-acosta, thanks for bringing this issue to our attention! After initial analysis, we've identified the root cause of the issue and will be pushing a fix in the upcoming MRE version that's tentatively scheduled to be released by the end of this month. Thanks!


Fixed signatures

Fixes #1890

Codecov Report

Merging #1891 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1891   +/-   ##
=========================================
  Coverage     98.07%   98.07%
  Complexity     5051     5051
=========================================
  Files            88       88
  Lines         11401    11401
  Branches       1503     1503
=========================================
  Hits          11182    11182
  Misses          113      113
  Partials        106      106

Impacted Files
Coverage Δ
Complexity Δ

javaslang/src/main/java/javaslang/Predicates.java
80% <ø> (ø)
15 <0> (ø)
:x:

Continue to review full report at Codecov.

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


Adds Output Channel to "Other web audio lists"

Hello, nice list of resources!
Would you be interested in adding outputchannel.com?
Cheers,
Ed

Cool! Thanks :)


Add sharing text support to the Telegram button

The Telegram button implemented in #23 can currently only share a specific URL. Telegram also allows to specify the message that will appear next to the URL, and @ilyabirman suggested that we implement it. Let’s do this.
I suggest to add the data-text attribute to the Telegram button which can be used to specify the message. The button code will look like following:

Send

The attribute should translate to the text parameter of the sharing URL. The URL will then look like following: https://telegram.me/share/url?url=http://ilyabirman.net&text=Ilya%20Birman.
PRs are welcome. PR should also describe the sharing options in the according section of Readme.

Share → Send

@ilyabirman, yep, you’re right, updated the issue.
BTW, I missed this in #40, made #47 to address this.


Update License and Help sections

There's an official License file now, so no need to specify this in the
README. And now this project has other maintainers, it's better for the
few support queries to go somewhere public.

Thanks, Alex.


Actuator Lockup

After basic testing with a Xbox One controller using ROS + interface board to control brake_ecu there appears to be an issue where rapidly bringing the brake from max position to min position can lead to to actuator getting stuck at full or near full brake and ceasing to respond to additional commands and needing to be restarted.

After testing on the other actuator this seems to only be prevalent on the actuator with wireless capabilities as the issue doesn't seem to arise on the non-wireless actuator. Considering the problematic actuator was less performant overall in the first place that could be what is causing the issue. Ill be leaving this issue open until more through testing can be done as well as testing with the actual wheel and pedal setup.

This was confermed to just be the other actuator


updated mkdoc plugin order; fixed style bug

@ifokkema Yes, it works locally for me, and  did not work before yesterday's fix.
The facts on the table make me wonder whether the plugin order error depends on a version of mkdocs or one of the plugins.
@ifokkema, let's collect some data about what works/doesn't work.
snafu (linux, Python 3.12)
Installation exactly as described in the README with new venv.
❯ uv pip freeze | rg 'mkdocs|mark|pymdown'
Using Python 3.12.3 environment at venv
markdown==3.7
markdown-captions==2.1.2
markdown-exec==1.9.3
markupsafe==3.0.1
mkdocs==1.6.1
mkdocs-autolinks-plugin==0.7.1
mkdocs-awesome-pages-plugin==2.9.3
mkdocs-exclude==1.0.2
mkdocs-get-deps==0.2.0
mkdocs-glightbox==0.4.0
mkdocs-macros-plugin==1.3.4
mkdocs-material==9.5.39
mkdocs-material-extensions==1.3.1
mkdocs-mermaid2-plugin==1.1.1
mkdocs-multirepo-plugin==0.8.3
mkdocs-simple-hooks==0.1.5
mkdocs-table-reader-plugin==3.1.0
pymdown-extensions==10.11.2

@ifokkema, let's collect some data about what works/doesn't work.

Good idea;
$ uv pip freeze | grep -E 'mkdocs|mark|pymdown'
Using Python 3.10.12 environment at /www/git/hgvs-nomenclature/venv
markdown==3.4.4
markdown-captions==2.1.2
markdown-exec==1.7.0
markupsafe==2.1.3
mkdocs==1.5.3
mkdocs-autolinks-plugin==0.7.1
mkdocs-awesome-pages-plugin==2.9.2
mkdocs-exclude==1.0.2
mkdocs-glightbox==0.3.4
mkdocs-macros-plugin==1.0.4
mkdocs-material==9.4.3
mkdocs-material-extensions==1.2
mkdocs-mermaid2-plugin==1.1.1
mkdocs-multirepo-plugin==0.6.3
mkdocs-simple-hooks==0.1.5
mkdocs-table-reader-plugin==2.0.1
pymdown-extensions==10.3
(venv)

There are quite a few differences. I'll try upgrading packages one by one and see if I can pinpoint it.

Updating mkdocs-table-reader-plugin to version 3.1.0 solved the problem. I'll build a new venv and see what my versions are then; if I can't run mkdocs with the defaults, I'll set a version for the table reader plugin in requirements.txt.

@reece When rebuilding my venv, all my package versions are the same as yours. Only my Python version differs. Since rebuilding the venv solves the problem, new users won't have this issue. Only users who built their venv some time ago and now pull in main will have issues. Do you think we should still update the requirements.txt?

I recommend leaving requirements.txt as is.
We could consider pinning, but I don't think it's worth the effort, and
often creates more problems than it's worth.
On Wed, Oct 9, 2024, 12:08 Ivo Fokkema @.***> wrote:

@reece https://github.com/reece When rebuilding my venv, all my package
versions are the same as yours. Only my Python version differs. Since
rebuilding the venv solves the problem, new users won't have this issue.
Only users who built their venv some time ago and now pull in main will
have issues. Do you think we should still update the requirements.txt?
—
Reply to this email directly, view it on GitHub
https://github.com/HGVSnomenclature/hgvs-nomenclature/pull/187#issuecomment-2403195786,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA2XDNAFRG26QO2WQIVUTDZ2V5KDAVCNFSM6AAAAABPTFNFZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBTGE4TKNZYGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

I recommend leaving requirements.txt as is. We could consider pinning, but I don't think it's worth the effort, and often creates more problems than it's worth.

Purely for my own understanding, since I'm not very familiar with this, I understand how mkdocs-table-reader-plugin==3.1.0 would cause issues, but what about mkdocs-table-reader-plugin>=3.1.0? I can't think of potential issues, but maybe I'm overlooking something?

Nope that's a good solution.
If we're going to pin versions, I would use the tilde syntax like this:
mkdocs-table-reader-plugin~=3.1
For packages that support semantic versioning, I find that this is a good
trade-off between staying up-to-date and not getting surprised by changes.
On Thu, Oct 10, 2024, 07:47 Ivo Fokkema @.***> wrote:

I recommend leaving requirements.txt as is. We could consider pinning, but
I don't think it's worth the effort, and often creates more problems than
it's worth.
Purely for my own understanding, since I'm not very familiar with this, I
understand how mkdocs-table-reader-plugin==3.1.0 would cause issues, but
what about mkdocs-table-reader-plugin>=3.1.0? I can't think of potential
issues, but maybe I'm overlooking something?
—
Reply to this email directly, view it on GitHub
https://github.com/HGVSnomenclature/hgvs-nomenclature/pull/187#issuecomment-2405320755,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA2XDJM2Y6RXFMRHUYOYCLZ22HO3AVCNFSM6AAAAABPTFNFZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBVGMZDANZVGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Just FYI; ran into this exact same issue today and was grateful for the discussion here. I didn't rebuild venv, just updated this package to 3.1.0.


fix(sec): upgrade github.com/containerd/containerd to 1.6.18

What happened？
There are 1 security vulnerabilities found in github.com/containerd/containerd v1.5.17

CVE-2023-25173

What did I do？
Upgrade github.com/containerd/containerd from v1.5.17 to 1.6.18 for vulnerability fix
What did you expect to happen？
Ideally, no insecure libs should be used.
How can we automate the detection of these types of issues?
By using the GitHub Actions configurations provided by murphysec, we can conduct automatic code security checks in our CI pipeline.
The specification of the pull request
PR Specification from OSCS

Hello @dack-su ,
Thanks for reaching out.
We are not affected by those CVEs because they affect pieces of code that we don't use.
The Docker CVEs are about the daemon and the API server, we are only using the client API.
For this reason, I have to decline your Pull Request.


Fix this please

Could you update this please?

Just updated Quizlet scripts, Gimkit may not be coming back for awhile. In the meantime, I will be taking a deeper look at Quizizz and some other games to see what I can do.


Duration type is a builtin type

Pull Request Description

Important Notes

Checklist
Please include the following checklist in your PR:

[x] The documentation has been updated if necessary.
[x] All code conforms to the
Scala,
Java,
and
Rust
style guides.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed: Enso GUI was tested when built using BOTH
./run ide build and ./run ide watch.

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

According to the associated issue description, we want to split the current functionality of Duration into Duration and Period, so I removed all the date-related functionality from Duration, and left only time-related functionality. All the removed date-related functionality should be moved to a new Period (maybe existing Time_Period?) builtin type in the future.

Thanks for making the TruffleObject implementations final, Pavel.

As discussed with @radeusgd, I reverted the incompatible changes that I introduced in this PR. So the only breaking changes are:

removing all Integer extension methods, as we want to explicitly differentiate between Duration and Period.
Ignore all tests that are related to Period, i.e., that will be failing untill Period is implemented.


Fix: Correct abnormal breakpoint in Filepond style

Found this strange break-point to be inconsistent with Tailwind's breakpoints. And upon Dan's suggestion, I fixed it to the nearest Tailwind's breakpoint (md). 🙂

Sorry, just got back. And I noticed that their docs is missing the grid layout altogether!
https://pqina.nl/filepond/docs/api/instance/properties/#styles

That's because its a custom layout, just for Filament :)

Thank you!

No u! Thank you! 🙃


fix: Cargo test args being parsed breaks test

Summary
Passing args to cargo test such as cargo test -- --test-threads=1 causes tests to fail since the cargo arguments are being parsed by the test. This fixes that by explicity using the get_matches_from_safe function even when there are no arguments used in the test.
Preflight checklist

[x] Code formatted with rustfmt
[x] Relevant tests added
[x] Any new documentation added

Thanks @wkral!


While deploying new version of same API existing version is overwritten

Current API version 4.x. While deploying a new version or evision, the existing version is overwritten

Hi @charlievpaul ,
You have to use same apiversionsetid for both apis as same, but the name value of the api version 1 and version 2 should be different. You can have display name as same for both apis and description. Just try this.
Basically the api name should be unique.
@RupengLiu please correct me if am wrong.

It worked with different API name! Thanks Sanjeev


gcloud-sqlproxy: add tolerations and affinity to the Deployment

What this PR does / why we need it:
This minor change just provides the ability to configure tolerations and affinity on the Deployment.
@rimusz

/assign @unguiculus

/assign @unguiculus

/ok-to-test

/lgtm


Add Abseil dep to the README

The readme say to run git-sync-deps. The following lines are redudant
because those repos will already be checked out.
I did not update the README after adding Abseil as a dep. This updates to README.

That section is prefaced by noting this would be an non-standard workflow. I'm ok not listing the commands, but maybe it would be good to have a list of the dependent repos in the readme somewhere.

That section is prefaced by noting this would be an non-standard workflow. I'm ok not listing the commands, but maybe it would be good to have a list of the dependent repos in the readme somewhere.

Okay, I left it in and just added Abseil to the README.


Resolution for #103: Support for HTTP PATCH operation

Added HTTP Patch operation.

Hi @sukidesuaoi, you've added to the input test fixture but not the resulting output fixture (fixtures/cats.proto), which contain the expected protobuf specs. Please add the missing Protobuf specs so the tests pass. You can run this test this locally by running go test ./... in the base of the repo.
For details on which tests are failing, check out the Travis build: https://travis-ci.org/NYTimes/openapi2proto/builds/490369413

Thanks for adding the test fixture changes, @sukidesuaoi.
Is there some reason you've created a new openai2proto directory inside the project, though? It's broken pretty much everything. Please revert that change.

Thanks for adding the test fixture changes, @sukidesuaoi.
Is there some reason you've created a new openai2proto directory inside the project, though? It's broken pretty much everything. Please revert that change.

I was doing the testing. hehe. I will revert the directory change.


Release-4

Summary by Sourcery
Update the deploy_docs task to simplify the command execution and add a RELEASE.md file to document the release details.
Build:

Remove the user working directory specification from the deploy_docs task in the taskfile.yml.

Documentation:

Add a RELEASE.md file to document the release type and reference the related issue.

Release Notes

Just wanted to say

Release type: patch
Release for #586


Git Clone failing

./yesiscan --no-backend-scancode https://github.com/aws/amazon-cloudwatch-agent
Results:
main: failed: repository not found

So I've been tracking this down. Here's why it's broken:
https://github.com/aws/amazon-cloudwatch-agent/commit/1c07e074c34707a4470707dbcc7a2fa743398efb
Look at their commit. They did something weird on purpose. I'm trying now to decide whether it's valid git (I guess so) but seeing as it's non-standard, that's why it's broken. Fun issue!

This is now fixed in f0856bc1c10935ad9589d2fce59e7133749bd410


Publish into a publication

Hello @kylehg, @mikkot,
Please review the following commits I made in branch 'jamie-publish-into-pub'.
e97d46c59cbc3c946f7430701ebe1820158136d3 (2015-11-20 10:22:18 -0800)
Publish into a publication
R=@kylehg
R=@mikkot

YOLOMerging, will add vars shortly.


Add installation instructions to readme

someone that wants to do this may have no idea to, we should facilitate this process as much as possible

Thank you for the feedback, I'd be happy to do so.

I added installation instructions @SavagePastaMan. Took a year or so.


fix flag parse issue

separate flag name and flag value with equal sign instand of space.
Signed-off-by: Jizhong Jiang<EMAIL_ADDRESS>Description of the changes
Type of fix: Bug Fix
Fixes
Please describe:

Separate flag name and flag value with equal sign instand of space in install/v2plugin/startcontiv.sh

The flag name and value was separated by space, if the value is empty, go flag set the value with the next flag name.
for example:
/netplugin $dbg_flag -plugin-mode=$plugin_mode $vxlan_port_cfg -vlan-if=$iflist -cluster-store=$cluster_store $ctrl_ip_cfg $vtep_ip_cfg

if iflist is empty, the value of -vlan-if is "-cluster-store"

@rchirakk: It's not needed. The CI is running now.


Move the username and password to Application Credentials

Could the U/P be moved to Application Credentials? It would be nice to be able to change the U/P without remove/reinstall.

I believe this is done already.


XPost Update

small refactor; added condition to decide if a message should be included in cross post checking

only actual changes are:
https://github.com/iosdevelopershq/Camille/pull/20/files#diff-4bfb64213411709e338e3e422e34a922R41
and
https://github.com/iosdevelopershq/Camille/pull/20/files#diff-591b38ade686d8d8d2c6ba4c4fec802aR17

Looks good to me!


Suddenly Hazard Zone

Hi,
I am not sure on how I am doing it. But I can replicate it.
When I was in the LightZone and then got into the Hazard Zone, then I get out of the Hazard Zone and suddenly I get the visual hint that I am in the Hazard Zone and my HP gets drained, but I am not in the Zone.
Please see the video attachment if you don't know what I mean.
https://github.com/Phazorknight/Cogito/assets/87974401/6d391449-436f-471e-a028-401d7e3ae124
https://www.veed.io/view/31afa1c4-a564-4a8d-922b-7f9016d32112?panel= (githubs 10 MB border is a little pain for me)

Oh, thanks for flagging this. Will take a look.

I think this is just damage from Sanity right? Once you walk into the lightzone it sets brightness level to 1 and then when you walk out it sets it to 0, after a limited amount of time you start taking damage.

I am not sure on how I am doing it. But I can replicate it.

Bezoika is right, when I get into the lightzone and just wait I get the same result. So it was just my stupidity, sorry to bother you.
I got confused because I was in the HazardZone just in the right time.

Re-opening this so I'll look into this more:
Need to make it clear that this is happening due to the SanityComponent, as it's otherwise very confusing. Will update once I fix that.

I would suggest to make it visibily more clear that something other then the hazardzone is happening, like with a black overlay instead of the same (?) red of the hazardzone. Some more debug prints like "insanity now active" could also help to reduce the confusion, at least for me :)

Should be improved with https://github.com/Phazorknight/Cogito/commit/a117370610f000ae11005e84e01ad0c0ad12237c:
I've added a bool flag to the player.gd to easily turn sanity off.
Also added a print that tells you if the player is losing health due to low sanity.
All of this will be improved in the future when tackling #49, but for now I consider this closed.


Address mamba v2 incompatibilities

Closes https://github.com/conda-incubator/setup-miniconda/issues/366

Ok, this seems to work mostly in Unix, but mamba v2 gets "stuck" for Windows in this part:
...
  Linking requests-2.32.3-pyhd8ed1ab_0
  Linking jsonschema-4.23.0-pyhd8ed1ab_0
  Linking requests-toolbelt-1.0.0-pyhd8ed1ab_0
  Linking nbformat-5.10.4-pyhd8ed1ab_0
  Linking anaconda-client-1.12.3-pyhd8ed1ab_1
  Warning: warning  libmamba draining failed An existing connection was forcibly closed by the remote host.

  warning  libmamba draining failed An existing connection was forcibly closed by the remote host.

Disabling PYC compilation unlocks the hang, but then it hangs again during the pip installs. Seems that in both cases a hung subprocess on Windows is involved. I guess these code blocks:

https://github.com/mamba-org/mamba/blob/31b23473e059b47c03b065e5592ea5a7cf77fc9b/libmamba/src/api/pip_utils.cpp#L173
https://github.com/mamba-org/mamba/blob/31b23473e059b47c03b065e5592ea5a7cf77fc9b/libmamba/src/core/transaction_context.cpp#L319

@conda-incubator/setup-miniconda, ready for review!


Bump electron-overlay-window to latest version

Started in https://github.com/grusigast/doa-gravure-studio-overlay/tree/7-bump-electron-overlay-window-to-latest-version but there is a weird bug where overlay is not interactive before toggling off and on


few small PS fixes:

fail to process dsa when session is already ready
fail to process dsvin if session is not ready yet
fail to process any message on the wrong side (mn/client)
fail in PrepareDenominate if pool already has entries
fail if can't sign anything in final tx, also reset local pool in such case
fix "number of entries" pushed on DSSTATUSUPDATE

(part of #1120)

rebased after #1121


AdminCreateOrg API ignores FullName property

Gogs version (or commit ref):
<IP_ADDRESS>5
7049cb9d975505a6f1fa3fad809dd92c1078360f
Database:

[x] PostgreSQL

Can you reproduce the bug at http://try.gogs.io:

[ ] Yes (provide example URL)
[x] No... because I don't known how to create a new organization in my account with client.AdminCreateOrg...
[ ] Not relevant

Description
The FullName property from bellow seems to be ignored by the gogs API endpoint. It seem to end up with the same value as the UserName  property.
	org, err := client.AdminCreateOrg(
		"gogs",
		gogs.CreateOrgOption{
			UserName:    "acmeOrganization",
			FullName:    "acmeOrganization Full Name", // XXX this is ignored.
			Description: "Description",
			Website:     "http://acme.example.com",
			Location:    "Lisbon, Portugal",
		})

@Unknwon this requires fiddling with go-gogs-client right?

@bkcsoft Yes, I think so

Patch has pushed to fix this issue, please test on develop branch or https://try.gogs.io.


Remove ZMQ and WS JSON-RPC transports

These transports have had a history of causing hang-ups during testing. Better to remove them. It's easy to re-add them later if there is a strong wish for them to be present.

Removed zmq, but left ws for now. Disabled ws tests


Fix #539

r? @vinipsmaker
(maidsafe_highfive has picked a reviewer for you, use r? to override)

This has been rebased off of the newly-rebased service-test-changes branch.

It needs to be rebased. It contains commits that were merged in master already.

Continuing in https://github.com/maidsafe/crust/pull/553


different css style between npm run dev and npm run build

Describe the issue / bug.
I have a input element with the following css style:
  .host-input {
    margin-left: 10px;
    display: inline-table;
    width: 300px;
  }

If I run npm run dev, the width is correct.
However, if I run npm run build and open the generated app, the width of the input element is to the border of the right, which I think is auto.
How could this difference happen?  Is it related to the difference of two webpack.renderer.config.js files under the root dir and the ./electron-vue?
I have the same issue with anchor element.
  a {
    color: inherit;
  }

In dev environment, it is with black color, however, after I open the build app, the color is blue.
If visual, provide a screenshot.
Under dev:

After build:

Tell me about your development environment.

Node version: v7.7.4
NPM version: 4.1.2
vue-cli version: (if necessary)
Operating System: MacOS

@fluency03
CSS is not handled differently in development vs. production. I'm not entirely sure what may be causing this issue. Do you have a project repo I could take a look at?

@SimulatedGREG sorry, this project I am working on is not open source, I am not allowed to do so.
I will try to figure it out.  Thanks.

@fluency03 Hi, was wondering if you were able to solve this as I am experiencing similar issues?


Record all parameter values (including defaults) in output MMIF

New Feature Summary
Desired functionality:
When the SWT app is run, the values of all parameters, including those implicitly assigned default values, are recorded in
views > n > metadata > parameters
In v4.1 (and previous versions), parameters are recorded in the MMIF only if they were set explicitly at runtime.
Since different versions of the same app can have different default values for the parameters, having all the parameter values explicitly recorded in the MMIF makes it easier to investigate how a particular MMIF file was generated.
Related
No response
Alternatives
No response
Additional context
This seems to me like desirable functionality to have in all CLAMS apps, not only SWT.

This was actually discussed in https://github.com/clamsproject/mmif/issues/208, then reverted via https://github.com/clamsproject/mmif/pull/217. We can always revisit our previous decision, but a couple things to note;

we can't (re-)use view::metadata::parameters for this, as we want to keep that field for pure user inputs (for reproducibility and accountability)
which leads to an addition of a new field, that will lead to a "breaking" change in MMIF json scheme and will end up with MMIF 1.1.x.

Closing as duplicate to https://github.com/clamsproject/mmif/issues/208 , as that issue is now re-opened for further discussion.


Add List Clients Command

Closes https://github.com/AY2223S1-CS2103-W14-1/tp/pull/63. I've added a new panel to display the existing clients in our app. Ideally there should be a feature to toggle the view between clients and properties, but currently I just split the window into 2, as shown below.
I also added the list -c command
Screenshots:

Good work! WIth your implementation, is it that list -p and list -c would just refresh their respective panel?

Good work! WIth your implementation, is it that list -p and list -c would just refresh their respective panel?

Yup! I think the existing code has a Predicate Class that is used to filter the list. So the list -p command will just change the Predicate to show all the properties. So only the respective directory is updated.


Add suggestion to use DOCKER_TAGS to error message when trying to docker-push the dev tag

Since we used to use DOCKER_TAG, devs are confused when it no longer works. This message:
The 'dev' tag can not be pushed to the registry!

Could easily include a suggestion about how to "fix" the issue.

Fixed in https://github.com/make-files/pkg-docker/commit/6c5ad80ef25b61da42cd07fb5de342c922f7ed89


Consider renaming the project

As described in the documentation we prefer that 3rd party starters do no start with spring-boot.
Could you please rename the starter so that we can include it in our list?
Thanks!

Sure! will do that!

Any updates ?

Sorry, I'll do it in the following 3 weeks

Any update?

Hi @snicoll, sorry for the delay, the project is renamed now.

@domix it looks like the build.gradle needs to be updated to reflect the new name. It is important that the artifact you publish is compliant with our naming recommendation.

@snicoll just applied the changes to build.gradle

Thanks but we're not there yet. If I checkout this project and I build it, It generates the following artifacts:
-rw-r--r--  1 snicoll  staff    32K Jul 12 08:28 spring-boot-starter-jade4j-0.3.3-javadoc.jar
-rw-r--r--  1 snicoll  staff   5.3K Jul 12 08:28 spring-boot-starter-jade4j-0.3.3-sources.jar
-rw-r--r--  1 snicoll  staff   8.6K Jul 12 08:28 spring-boot-starter-jade4j-0.3.3.jar

Ultimately, a release of this project will still violate the naming convention.

Now seems to be fixed, thanks @snicoll!


Update Composer dependencies (2021-03-16-00-09)

Visual regression test passed!
View the visual regression test report


[BUG] Megatron-LM with DeepSpeed training, get stuck in the _exec_schedule function

Describe the bug
When training the Megatron-LM model with DeepSpeed, if I set the global batch size to 16, it will get stuck in the _exec_schedule function in deepspeed/runtime/pipeline/engine.py. However, if I set the global batch size to 8, the training will start normally.
To Reproduce
Steps to reproduce the behavior:
envirment:
python==3.9.7
pip ==21.2.4
torch==1.10.1
torchvision==0.11.2
deepspeed==0.5.10
apex==0.1
ds_report output
Please run ds_report to give us details about your setup.
--------------------------------------------------
DeepSpeed C++/CUDA extension op report
--------------------------------------------------
NOTE: Ops not installed will be just-in-time (JIT) compiled at
      runtime if needed. Op compatibility means that your system
      meet the required dependencies to JIT install the op.
--------------------------------------------------
JIT compiled ops requires ninja
ninja .................. [OKAY]
--------------------------------------------------
op name ................ installed .. compatible
--------------------------------------------------
cpu_adam ............... [NO] ....... [OKAY]
cpu_adagrad ............ [NO] ....... [OKAY]
fused_adam ............. [NO] ....... [OKAY]
fused_lamb ............. [NO] ....... [OKAY]
sparse_attn ............ [NO] ....... [OKAY]
transformer ............ [NO] ....... [OKAY]
stochastic_transformer . [NO] ....... [OKAY]
 [WARNING]  async_io requires the dev libaio .so object and headers but these were not found.
 [WARNING]  async_io: please install the libaio-dev package with apt
 [WARNING]  If libaio is already installed (perhaps from source), try setting the CFLAGS and LDFLAGS environment variables to where it can be found.
async_io ............... [NO] ....... [NO]
transformer_inference .. [NO] ....... [OKAY]
utils .................. [NO] ....... [OKAY]
quantizer .............. [NO] .......
Additional context
Add any other context about the problem here.

Here is a suggested solution:

Verify resource availability: Ensure that there are enough resources (such as GPU memory) to handle a global batch size of 16. Since training is working with a batch size of 8, it could be an indication of insufficient resources.

Check for bottlenecks: It's possible that certain pipeline stages are causing a bottleneck when the global batch size is increased to 16. You can try profiling the execution of the pipeline stages to identify any potential bottlenecks.

Adjust the pipeline model parallelism: The current configuration has a pipeline-model-parallel-size of 2. You can experiment with different values for this parameter to see if it helps with the training when using a global batch size of 16.

Update DeepSpeed: Make sure you're using the latest version of DeepSpeed. Update the package if necessary, as newer versions may have bug fixes or performance improvements.

Monitor GPU utilization: You can use tools like NVIDIA's nvidia-smi or nvtop to monitor GPU utilization during training. This can help you identify any potential issues with GPU utilization when using a global batch size of 16.

Check for deadlocks: DeepSpeed uses various synchronization primitives like barriers and events. It's possible that a deadlock is occurring with a global batch size of 16. To debug this, you can add print statements or use a debugger to monitor the execution flow of the _exec_schedule function and identify where it is getting stuck.

After trying these steps, if the issue persists, it would be helpful to provide more information in this GitHub issue, such as detailed logs, profiling results, and any additional observations made during debugging. This will help the DeepSpeed maintainers in identifying the root cause and providing a more specific solution.

@hemangjoshi37a Thank you very much. I will try your suggestions, and if there are any further questions, I will provide more information in the issue

Thank you for your efforts @Zhang-kg and @hemangjoshi37a, may I ask how to solve this problem? I meet the same issue with CUDA 12.2, NCCL 2.20.5, GCC 10.2, PyTorch 2.3.1, Deepspeed 0.12.4+02e2ebf, Python 3.8.19, GPU 4xA100-SXM4-40GB, CPU AMD EPYC 7543 32-Core  Processor, Memory 195607748 kB(free).
Thanks again for your time and patience. Looking forward to your reply.


Implement physics engine

The physics engine should fundamentally support the following:

Particles and emitters
Forces (gravity, wind, drag, etc.)
Rigid body simulation and interactions between such bodies

The Editor interface should suppport adding parameters to change relevant properties.

This issue is way too large.


Adds Poseidon CRH w/ constraints

You have a similar draft implementation currently experimental in sponge.
https://github.com/arkworks-rs/sponge/blob/experimental/src/poseidon/mod.rs
It may be able if the work can be merged together. @Will-Lin4 is working on that part.
One thing:

One observation from Fractal is that the cost of Poseidon is a little bit mysterious. For example, we may consider 3, 5, inverse:

PoseidonSboxGadget {
    Exponentiation3,
    Exponentiation5,
    Inverse,
}

It appears that sometimes, exp by 17 would be better for efficiency, for two reasons:

17 = 16 + 1, so not too hard to compute using fast powering.
using exp by 17 allows us to spend fewer rounds.

And therefore, there is a slightly interesting cost model here.

Also, one of the big challenges currently for arkworks is the lack of Poseidon parameters for the common curves (no need for all). If you are interested in that part, it would be really appericated.
We have an extended discussion on that in
https://github.com/arkworks-rs/sponge/issues/8

It appears that sometimes, exp by 17 would be better for efficiency, for two reasons:

17 = 16 + 1, so not too hard to compute using fast powering.
using exp by 17 allows us to spend fewer rounds.

And therefore, there is a slightly interesting cost model here.

Sure thing, this can all be added to make it support different options. I can try to generalise it as well.
As far as merging goes, I'm definitely looking to have an implementation that is consistent with our existing one over at @webb-tools. This is a migration of sorts of the work we have there. I'm not sure if the sponge variant will yield the same hash but this is due to my lack of knowledge of truly what sponges are.

Also, one of the big challenges currently for arkworks is the lack of Poseidon parameters for the common curves (no need for all). If you are interested in that part, it would be really appreciated.
We have an extended discussion on that in
arkworks-rs/sponge#8

Are you thinking we have a repo of hardcoded parameters exportable for different curves or an implementation of the parameter generation for generic curves? I'd guess the latter is more robust and sustainable.

@weikengchen I would suggest that if the two versions yield different hashes that we still have separate implementations. Otherwise, this will cause me to need to implement sponge variants as well in other applications (against bulletproofs, circom, etc.)
Having both is definitely useful also from visibility and example perspective.


Add daemon mode for Windows

On Windows, the admin-helper service can be installed automatically with
the command 'admin-helper install-daemon' and uninstalled with
'admin-helper uninstall-daemon'.
It will launch the admin-helper in daemon mode and provide an HTTP API
available on the named pipe crc-admin-helper.
Only members of the Hyper-V administrators group can use it.

Will we still do this?

Yes I need to add more APIs and use it in crc.

I was thinking maybe we should use the crc daemon, it can execute the admin-helper command needed, but this won't work on windows, as there we need a service (with admin privileges).
Not sure if we should run it as a service only in windows and use this API. For linux and macOS add similar API in the crc daemon which runs the admin-helper on demand. Apart from not running another background process we don't gain much by doing this though.

The major win is the removal of all UAC prompt after crc setup.

@guillaumerose Not sure if the install-daemon command will be used in the preflight of crc, but for me on macOS its not working as expected, but the issue is with the path of the unix socket, check the stdErr o/p of the service:
$ sudo ./admin-helper install-daemon
$ sudo cat /usr/local/var/log/CodeReadyContainersAdminHelper.err.log
2021/02/19 15:19:56 listen unix daemon.sock: bind: read-only file system
2021/02/19 15:20:06 listen unix daemon.sock: bind: read-only file system
2021/02/19 15:20:16 listen unix daemon.sock: bind: read-only file system

Oh yes don't use it on macOS ^^ It is only for Windows. I should add a build flag.

I added a if for Windows. There is no more daemon for mac/linux :)

@guillaumerose This is still needed for the routes controller to work on windows, right?

No it is not strictly required.
Current crc will use the regular admin-helper and display UAC prompts.
When this PR will land and will be used in crc, it will remove these prompts.
TBH, UAC prompts are fairly limited now. It should only appear once or twice at crc start and only if the user adds a custom route.
This daemon mode is an UX improvement.

Let's start with this!


Sum of Digits in Julia | Math | GSSoC'21 |

💥 Proposal
Sum of Digits in Julia
Have you read the Contributing Guidelines on Pull Requests?
YES

\assign


Featurette widget does not change from example

I am using hugo version 0.55.4 and Academic theme version 4.2.5. and trying to get the featurette widget on a separate widget page that is not homepage. I have followed the instruction in Managing Content documentation and managed to get my separate widget page with experience and skill widget, but I could not change the icon and the description on the featurette widget.
This is the featurette section, as you can see it does not look different from the example site...

...while I actually have changed the front matter for that widget as follows.
+++
# A Skills section created with the Featurette widget.
widget = "featurette"  # See https://sourcethemes.com/academic/docs/page-builder/
headless = true  # This file represents a page section.
active = true  # Activate this widget? true/false
weight = 1  # Order that this section will appear.

title = "Skills"
subtitle = ""

# Showcase personal skills or business features.
#
# Add/remove as many `[[feature]]` blocks below as you like.
#
# For available icons, see: https://sourcethemes.com/academic/docs/widgets/#icons

[[feature]]
  icon = "r-project"
  icon_pack = "fab"
  name = "R user"
  description = "..."

[[feature]]
  icon = "seedling"
  icon_pack = "fas"
  name = "Biodiversity Scientist"
  description = "..."

[[feature]]
  icon = "chart-line"
  icon_pack = "fas"
  name = "Data Analyst"
  description = "..."

[[feature]]
  icon = "handshake"
  icon_pack = "far"
  name = "Community Builder"
  description = "..."

+++

No matter how I see it, I could not spot any difference from the example on skill other that the choice of icon and the description. Could you please tell me where I got wrong or is this a bug?
UPDATE: I even change the active status in the skills.md file in my widget page (active = false) and it just did not respond to it (featurette still showing in the next render within localhost after active=false). Is this something to do with the newest version of hugo? I should add that whenever I run blogdown::serve_site() in R to render the website in localhost. I keep getting this message:
Building sites â€¦ WARN 2019/04/26 19:39:25 found no layout file for "CSS" for "home": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.

Thanks in advance for anyone's assistance!

You have updated to the unreleased version. You'll need to remove the "CSS" output entry from config.Toml

Thanks, removing the CSS output in config.toml remove the warning message, but my widgets are still not updating when I render it in localhost. Now I say "widgets" as my "experience" widget was also not updating. I don't know if this is a hugo issue, hugo-academic issue, or blogdown issue 😂

If there are no errors/warnings then it would appear that Blogdown is not calling Hugo to update your site. The Blogdown community should be able to help.

But when I edited the about.md file and other blog posts in .Rmd, also my project files, blogdown::serve_site() still render my website updated with all those changes I had made within those files; only this new widget page that I made does not update, and there were no warning or error messages even when I built it with hugo.
Within this content/bio/ directory, there were only experience.md, skills.md, and index.md, and the front matter of index.md was just this:
+++
# Bio page
type = "widget_page"  # Page type is a Widget Page
headless = true
+++

So I don't think the problem is from blogdown or hugo.

I have a similar issue after updating, is there a fix for this? I rolled back my upgrade but can't find a mention to a home.css anywhere


Fixed bug wherein SitesCommand#addSiteToCache checks for an $org_id which DNE

Found while probing #732

Nice fix :+1:


500 Error when I click on Google+ link in stakeholder or contact form

When I'm in a stakeholder or contact form and i click on the Google+ icon on the bottom left I receive the Jordan 500 error message. Consider deleting/removing this icon as I have no idea what it's supposed to do.
https://tola-activity.mercycorps.org/complete/google-oauth2/?state=V2Ks3Fg8KgwViVeMY8fyKdSzOcU18dc7&code=4/4v7B2ub9afvP-5yFzc447mhylCZ2j6Zi9KZ1TGPHtf4&authuser=0&hd=mercycorps.org&session_state=2ea29e0d1ff0465c9f3ab6eb43b0e7800c97117c..93e2&prompt=none#

This link should not be there since we have not yet migrated to Google authentication. I will remove it.


⚠ SSH 🇱🇺 Luxembourg LUF 1 has degraded performance

In 4613637, SSH 🇱🇺 Luxembourg LUF 1 (http://lus-1.optnl.com:8080/) experienced degraded performance:

HTTP code: 400
Response time: 7372 ms

Resolved: SSH 🇱🇺 Luxembourg LUF 1 performance has improved in 5a47733.


[BUG] unable to upgrade k3s

Rancher Server Setup

Rancher version: 2.8.2 - stable docker image
Installation option (Docker install/Helm Chart): docker

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):

Proxy/Cert Details: nginx

Information about the Cluster

Kubernetes version: 128.9
Cluster Type (Local/Downstream): Downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): imported

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions: Admin

Describe the bug

No option in cluster config view to update from 128.9 to 128.11
To Reproduce

Result
Expected Result

Would’ve expected k3s version upgrade to be available in Rancher UI via system upgrade controller. If 128.9 is the highest supported version, the docs are out of date.
Screenshots

Additional context

@mike12806 , Rancher leverages KDM (https://github.com/rancher/kontainer-driver-metadata) for list of supported RKE2/K3s/RKE1 versions, so:

Just-released https://github.com/k3s-io/k3s/releases/tag/v1.28.11%2Bk3s1 is not added to KDM data for 2.8 yet (release-v2.8 branch is used - https://github.com/rancher/kontainer-driver-metadata/blob/release-v2.8/channels.yaml#L590-L595 (permalink). So the latest available 1.28.x version for 2.8.x at the moment is v1.28.10+k3s1.

Also, Rancher 2.8.2 doesn't actually support K8s 1.28 (the support was added in https://github.com/rancher/rancher/releases/tag/v2.8.3). So running v2.8.2 + downstream K8s 1.28 clusters is not a supported configuration. Please upgrade to v2.8.3+ to run 1.28.x downstream clusters and be able to upgrade them as new patches become released via KDM.

Closing as "working as expected".

This is helpful, thank you. Any idea why all the docker images for rancher seem to include 2.8.2? I checked both the latest and stable tagged images. If I get on 2.8.3, sounds like I can at least get to 1.28.10.

@mike12806 , I'm seeing both latest and stable tags pointing to the latest v2.8.5 release (digest sha256:4c2eae327f2e41effdddd0d71a4840094ecd9bcbe1c74876e59d184be85779c9 is the same on:

https://hub.docker.com/layers/rancher/rancher/v2.8.5/images/sha256-20cd423bc7e01026bb35a08e464c26c13857ded0a6164d6518043db89711d052
https://hub.docker.com/layers/rancher/rancher/stable/images/sha256-20cd423bc7e01026bb35a08e464c26c13857ded0a6164d6518043db89711d052
https://hub.docker.com/layers/rancher/rancher/latest/images/sha256-20cd423bc7e01026bb35a08e464c26c13857ded0a6164d6518043db89711d052

Interesting - I’m seeing
[rancher/rancher:stable@sha256:91a26da6b860b5b3a4507db6b30879d74f7d95edf252dce0a4cf86dd52449d74]
I’ll have to dig in why I’m getting a stale image somehow. Thanks!


How to insert spacing?

My config is this:
modules-left = i3
modules-center = date weather
modules-right = wireless-network cpu memory temperature pavolume backlight battery powermenu

I have icons at the first of every module. Because of that, the modules "date" and "wireless-network" appear with their icon cut in half, because the icon is the first thing in the modules-center and in the modules-right.
How i can create a bigger separation there or add blank spacing before that icons?
Here is a picture showing the error:
http://i.imgur.com/EzJ3dei.png

format-NAME-padding = N
format-NAME-margin  = N
format-NAME-spacing = N

You can also do:
[bar/mybar]
# Spaces before and after each module
module-margin = N

@jaagr module-margin is what i had at first. But the result was the image above


follow redirects?

www.simvascular.org redirects to simvascular.github.io/  and turned up something about "Redirecting" in the suggested citation. Today it just doesn't return.

fixed!  http://citeas.org/cite/www.simvascular.org
The webpage was using a less common kind of redirect, but now we support it.