hamming: update version file (v2.0.1 -> v2.1.0)

Please update the version specified in the hamming version file from 2.0.1 to 2.1.0.
This update has been caused by the application of a new input policy.
No tests should be changed as a result.

I'll give this a go!

Closed via #266


Ipa installed app flashed back.

Ios 16.0.2 has escaped from prison. Deb app is running normally.
In addition, ssh can't be used, log in with a mobile user and display zsh:1: command not found: 22.

Ssh works normally. Ipa is still not working.


Update Donation UI for Streaming Swaps

Update Donation Initiation step for Streaming Swaps to be more clear and improve UX. See FIgma files for reference.
Design Reference:
https://www.figma.com/design/ihw1PxBvLxacTHnN2aj4lC/3.-Product?node-id=22410-105909&t=raJHlUYBlTBcdf1E-1

verified on prod


Training on a GTX 1080 does not work, produces random labels

Hi!
I have come across a very very strange issue. Namely, training on an NVIDIA GTX 1080 does not work at all, and judging from the error rate, the predicted labels are completely random.
I have 2 almost identical systems (see below), and while on the System with the GTX 960 the training runs perfectly fine, on the system with the GTX 1080, the training simply doesn't work.
To test this, I ran
the following code:
python -m tensorflow.models.image.mnist.convolutional
On the System 1 (GTX 960), i get to an error rate below 4% within 2-3 batches, and at the end, it's below 1%:
Step 0 (epoch 0.00), 7.6 ms
Minibatch loss: 12.054, learning rate: 0.010000
Minibatch error: 90.6%
Validation error: 84.6%
Step 100 (epoch 0.12), 13.0 ms
Minibatch loss: 3.296, learning rate: 0.010000
Minibatch error: 4.7%
Validation error: 7.3%
Step 200 (epoch 0.23), 13.1 ms
Minibatch loss: 3.459, learning rate: 0.010000
Minibatch error: 12.5%
Validation error: 3.9%
...
Step 8500 (epoch 9.89), 13.0 ms
Minibatch loss: 1.604, learning rate: 0.006302
Minibatch error: 1.6%
Validation error: 0.9%
Test error: 0.8%

On the GTX 1080 system, the performance simply never improves! Error rate is steady at around 90%.
Step 8400 (epoch 9.77), 5.5 ms
Minibatch loss: 3.881, learning rate: 0.006302
Minibatch error: 85.9%
Validation error: 88.7%
Step 8500 (epoch 9.89), 5.5 ms
Minibatch loss: 3.877, learning rate: 0.006302
Minibatch error: 87.5%
Validation error: 88.7%
Test error: 89.7%

I tested this with TensorFlow 0.9, from the release PIP package for Python 3.5 with GPU support.
I also tested this with TensorFlow master from a week ago (fc9162975e52978d3af38549b570cc3cc5f0ab66), compiled to a PIP package on one machine, installed on both machines.
Here are the full system Specs, but the difference between them is only the GPU (1080 vs 960) and the Driver (367.35 vs 361.42)
System 1

OS: Ubuntu 16.04.1 LTS
Kernel: 4.4.0-31-generic
NVIDIA Driver Version: 361.42
CPU: Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz
RAM: 12 GB Ram
GPU: NVIDIA GTX 960, 4GB VRAM (edition: MSI GTX 960 Gaming 4G)

System 2:

OS: Ubuntu 16.04.1 LTS
Kernel: 4.4.0-31-generic
NVIDIA Driver Version: 367.35
CPU: Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz
RAM: 12 GB Ram
GPU: NVIDIA GTX 1080, 8GB VRAM

My LD_LIBRARY_PATH on both machines is:
:/usr/local/cuda/lib64:/usr/local/cuda-7.5/extras/CUPTI/lib64/
My Cuda version is 7.5, cudnn is 4.0.7 on BOTH machines.
Output of ls -l /usr/local/cuda/lib64 on the Machine with the GTX 960 and GTX 1080
https://gist.github.com/akors/30f5fbe3994e3ac40a4adbb6f76eb756#file-cudalibs-gtx960-txt
https://gist.github.com/akors/30f5fbe3994e3ac40a4adbb6f76eb756#file-cudalibs-gtx1080-txt
Does anyone know what could cause this and how to fix this?

Ooops, double-issue. Please disregard.


Workbooks api-version 2023 06 01

ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

[1] public repo review queue, private repo review queue
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue
If you need further help with anything, see Getting help section below.
Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[x] New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.)
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to Step 2, "ARM Review", for this PR.

Breaking changes review (Step 1)

If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

ARM API changes review (Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

Getting help

For general PR approval workflow, see the diagram at the top of this comment.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Hi @vutran01 ,
I compared the "workbooks_API.json" file with previous api-version "2022-04-01", I didn't find any new API/properties are introduced, is it intentional?

correct, the changes are to workbook name which states clearly that it should be an uuid and the bump the api version

/azp run

Azure Pipelines successfully started running 2 pipeline(s).

/pr RequestMerge


Issue when no decimal digits are provided

When I enter 1111.00 in my text box it saves are 1111.00 in database but when I get data back to the text box with Currency mask it shows as $ 11.11 instead of $ 1111.00 ( In this case I don't have anything in my decimal places except zeros). But when I have some thing in decimal places like 1244.44 it saves and shows in the text box as $1244.44. Any idea?

@anirudhsamudrala, what version are you using?

@cesarrew I am using 1.0.1 version.

Ok. Try the latest version, which is 4.1.0. If you use Angular version 2, please use the version 2.1.0.

Hi
This is in continuation to @anirudhsamudrala
When I installed 2.1.0 I get below error in browser. I am using angular 2. Can you let me know how can get through this error message?
Uncaught TypeError: ctorParameters.map is not a function
at ReflectionCapabilities.parameters (vendor.js?v=FIP81wQTCRvVFJHudyg5QnJx_O_wjDqYVkV7ZCQ-SHc:8444)
at Reflector.parameters (vendor.js?v=FIP81wQTCRvVFJHudyg5QnJx_O_wjDqYVkV7ZCQ-SHc:8645)
at CompileMetadataResolver.getDependenciesMetadata (vendor.js?v=FIP81wQTCRvVFJHudyg5QnJx_O_wjDqYVkV7ZCQ-SHc:45863)
at CompileMetadataResolver.getTypeMetadata (vendor.js?v=FIP81wQTCRvVFJHudyg5QnJx_O_wjDqYVkV7ZCQ-SHc:45828)
at CompileMetadataResolver.getDirectiveMetadata (vendor.js?v=FIP81wQTCRvVFJHudyg5QnJx_O_wjDqYVkV7ZCQ-SHc:45601)
at vendor.js?v=FIP81wQTCRvVFJHudyg5QnJx_O_wjDqYVkV7ZCQ-SHc:45670
at Array.forEach ()
at CompileMetadataResolver.getNgModuleMetadata (vendor.js?v=FIP81wQTCRvVFJHudyg5QnJx_O_wjDqYVkV7ZCQ-SHc:45663)
at vendor.js?v=FIP81wQTCRvVFJHudyg5QnJx_O_wjDqYVkV7ZCQ-SHc:45651
at Array.forEach ()


Advanced: Clearing data sources

Within the Advanced modal, clicking the 'x' within the bounding box of the data source filter option deletes all the content from the entire modal.
This result is also occurs when all the data sources are removed individually.
The expected behaviour is to clear the filtering data sources only then allow re-adding.

Fixed in commit 088331dc466356f58af477b39afb66e5e535a018. Fixed datasource bug.


chore(main): release 1.0.0

:robot: I have created a release beep boop
1.0.0 (2024-05-09)
⚠ BREAKING CHANGES

Move event-driver under honestbank domain (#55)
joiner+transformer: Make joiner be able to join the map typed contents as is (#54)
extensions/google-cloud: GCSEventStore keep all storage by default (#53)
golang+handler: Use slog for formatted logging (#47)

Features

EventStore support looking up sources by key (#49) (282ba46)
Extensions use the local version of event-driver as dependency (#51) (9f2cf48)
extensions/google-cloud: GCSEventStore keep all storage by default (#53) (bdf52a6)
golang+handler: Use slog for formatted logging (#47) (a93ad91)
joiner+transformer: Make joiner be able to join the map typed contents as is (#54) (1f00c7d)
Move event-driver under honestbank domain (#55) (187f1de)
Support compressing the data before writing into GCS (#52) (55b8cfc)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/lukecold/event-driver/releases/tag/v1.0.0 :sunflower:


Add biomechanical-analysis-framework  to robotology-superbuild ?

As baf is being used across the lab, could it make sense to add it to biomechanical-analysis-framework ?
What do you think @davidegorbani @claudia-lat @GiulioRomualdi ?
This can be done by following the steps in https://github.com/robotology/robotology-superbuild/blob/master/doc/developers-faqs.md#how-to-add-a-new-package, but if you like I can handle this myself.

Definitely yes!

For what regard conda package generation, I wonder if it could make sense to directly add the package to conda-forge, without passing  via the robotology channel, a bit like we did for gz-sim-yarp-plugins in https://github.com/conda-forge/staged-recipes/pull/25910, https://github.com/robotology/gz-sim-yarp-plugins/issues/132 and https://github.com/robotology/gz-sim-yarp-plugins/issues/131 . The main advantage is that we would have packages available fast after a release, and we will have packages for osx-arm64 (for @DanielePucci to run analysis :) ) and linux-aarch64 (useful if we want eventually to do analysis on jetson or similar.

Fine to me

Ok, @davidegorbani let me know if you like to do this yourself (for learning) or you prefer me handling this. On baf side, we just need an initial release/tag.

I can try to follow the documentation and to it myself.

I created the fork and opened a branch to create the conda package https://github.com/davidegorbani/staged-recipes/tree/add-baf-pkg.

@davidegorbani regarding this, is BAF now available as a conda package?

is BAF now available as a conda package?

Not yet, I opened https://github.com/conda-forge/staged-recipes/pull/26377 but I didn't work on it.

If there is any urgency on that I can help @davidegorbani finalize that.

I wouldn't call it an urgency, but depending on if there is a conda package or not, I will implement the CI for iFeelBAF applications accordingly (installing from conda or compiling from source)


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/opstest2/docs-archive-test-source.git

Docs Build status updates of commit 56095a2:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: RepositoryUnauthorizedWithSourceCommit] Git data access to 'https://github.com/opstest2/docs-archive-test-target' (branch: Release_Archive_main_2022-01-25-03-17-12) is not authorized.. It looks like this might be the first time user: v-alji submitted a pull request to this repo. Before user can run builds in a pull request, he/she can enable 'v-alji' GitHub account in Docs by visiting Docs Portal (https://ops.microsoft.com). After enabling his/her account (v-alji), close and then reopen this pull request to start another build.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Optional Foreign Key EF Check

In pre 3.0.0, if we configure an optional relation, for example:
b.HasOne(p => p.Related)
    .WithMany()
    .HasForeignKey(p => p.RelatedId)
    .IsRequired(false);

and the RelatedId field is of type int then we get an exception:
An exception of type 'System.InvalidOperationException' occurred in Microsoft.EntityFrameworkCore.dll but was not handled in user code: 'The foreign key {'RelatedId'} on entity type 'Related' cannot be marked as optional because it does not contain any property of a nullable type. Any foreign key can be marked as required, but only foreign keys with at least one property of a nullable type and which is not part of primary key can be marked as optional.'

In 3.0.0 Preview 9, there are no exceptions thrown and EF will go ahead and make the relation required, (RelatedId column in database will be not null). I might have missed some release notes if this behavior was changed, but in my opinion, the original behavior with Exceptions seems more correct.

@alaatm This is by design: https://github.com/aspnet/EntityFrameworkCore/issues/14197
For triage: Consider documenting this in https://docs.microsoft.com/en-us/ef/core/what-is-new/ef-core-3.0/breaking-changes

Filed https://github.com/aspnet/EntityFramework.Docs/issues/1697


Can't connect local NVIDIA driver and hadoop-node-manager

OpenPAI Environment:

OpenPAI version: 0.14.0
OS (e.g. from /etc/os-release): Ubuntu 18.04
Kernel (e.g. uname -a): 5.3.0-42-generic
Hardware (e.g. core number, memory size, storage size, GPU type etc.): 12 core, 64 RAM, 1 Tb SSD, NVIDIA 2080 Ti

The main problem:
I'm trying to install PAI without "drivers" service and I added the info about my driver in the hadoop-node-manager service (135 line in hadoop-node-manager.yaml.template). Also, I have added information about my pre-installed-driver in service-configuration.yaml.
However, It doesn't connect anyway.
docker logs k8s_hadoop-node-manager:
./start_service.sh: line 47: nvidia-smi: command not found
And in the end of this log

docker logs k8s_job-exporter shows me these:

In addition, I have installed NVIDIA driver using apt install (apt install nvidia-driver-430.50), and I see my driver only in /usr/src/nvidia-430.50 directory. I don't see anything in /var/drivers/nvidia/current and the same in /usr/local/nvidia. Also, this worker machine has pre-installed nvidia-container-runtime. May you know how to add driver's components in /usr/local/nvidia? Or can you suggest where I am wrong?

https://askubuntu.com/questions/32507/how-do-i-get-a-list-of-installed-files-from-a-package
Can you list the file path with this command.

apt-file nvidia-driver-430 shows me this:
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/LICENSE.gz
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/NVIDIA_Changelog.gz
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/README.txt.gz
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/acknowledgements.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/addressingcapabilities.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/addtlresources.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/appendices.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/audiosupport.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/changelog.Debian.gz
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/commonproblems.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/configlaptop.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/configmultxscreens.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/configtwinview.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/copyright
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/depth30.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/displaydevicenames.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/dma_issues.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/dpi.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/editxconfig.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/egpu.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/faq.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/flippingubb.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/framelock.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/glxsupport.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/gpunames.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/i2c.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/index.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/installationandconfiguration.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/installdriver.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/installedcomponents.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/introduction.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/kms.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/knownissues.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/minimumrequirements.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/newusertips.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/nvidia
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/nvidia-debugdump.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/nvidia-hibernate.service
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/nvidia-ml.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/nvidia-persistenced-init.tar.bz2
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/nvidia-persistenced.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/nvidia-resume.service
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/nvidia-sleep.sh
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/nvidia-smi.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/nvidia-suspend.service
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/nvidiasettings.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/openglenvvariables.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/optimus.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/powermanagement.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/procinterface.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/profiles.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/programmingmodes.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/randr14.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/retpoline.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/sdi.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/selectdriver.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/sli.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/supportedchips.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/vdpausupport.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/xcompositeextension.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/xconfigoptions.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/xineramaglx.html
nvidia-driver-430: /usr/share/doc/nvidia-driver-430/xrandrextension.html

what the output of this
dpkg-query -L ${pkg}

I have this output:
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/nvidia-driver-430
/usr/share/doc/nvidia-driver-430/LICENSE.gz
/usr/share/doc/nvidia-driver-430/NVIDIA_Changelog.gz
/usr/share/doc/nvidia-driver-430/README.txt.gz
/usr/share/doc/nvidia-driver-430/acknowledgements.html
/usr/share/doc/nvidia-driver-430/addressingcapabilities.html
/usr/share/doc/nvidia-driver-430/addtlresources.html
/usr/share/doc/nvidia-driver-430/appendices.html
/usr/share/doc/nvidia-driver-430/audiosupport.html
/usr/share/doc/nvidia-driver-430/changelog.Debian.gz
/usr/share/doc/nvidia-driver-430/commonproblems.html
/usr/share/doc/nvidia-driver-430/configlaptop.html
/usr/share/doc/nvidia-driver-430/configmultxscreens.html
/usr/share/doc/nvidia-driver-430/configtwinview.html
/usr/share/doc/nvidia-driver-430/copyright
/usr/share/doc/nvidia-driver-430/depth30.html
/usr/share/doc/nvidia-driver-430/displaydevicenames.html
/usr/share/doc/nvidia-driver-430/dma_issues.html
/usr/share/doc/nvidia-driver-430/dpi.html
/usr/share/doc/nvidia-driver-430/editxconfig.html
/usr/share/doc/nvidia-driver-430/egpu.html
/usr/share/doc/nvidia-driver-430/faq.html
/usr/share/doc/nvidia-driver-430/flippingubb.html
/usr/share/doc/nvidia-driver-430/framelock.html
/usr/share/doc/nvidia-driver-430/glxsupport.html
/usr/share/doc/nvidia-driver-430/gpunames.html
/usr/share/doc/nvidia-driver-430/i2c.html
/usr/share/doc/nvidia-driver-430/index.html
/usr/share/doc/nvidia-driver-430/installationandconfiguration.html
/usr/share/doc/nvidia-driver-430/installdriver.html
/usr/share/doc/nvidia-driver-430/installedcomponents.html
/usr/share/doc/nvidia-driver-430/introduction.html
/usr/share/doc/nvidia-driver-430/kms.html
/usr/share/doc/nvidia-driver-430/knownissues.html
/usr/share/doc/nvidia-driver-430/minimumrequirements.html
/usr/share/doc/nvidia-driver-430/newusertips.html
/usr/share/doc/nvidia-driver-430/nvidia
/usr/share/doc/nvidia-driver-430/nvidia-debugdump.html
/usr/share/doc/nvidia-driver-430/nvidia-hibernate.service
/usr/share/doc/nvidia-driver-430/nvidia-ml.html
/usr/share/doc/nvidia-driver-430/nvidia-persistenced-init.tar.bz2
/usr/share/doc/nvidia-driver-430/nvidia-persistenced.html
/usr/share/doc/nvidia-driver-430/nvidia-resume.service
/usr/share/doc/nvidia-driver-430/nvidia-sleep.sh
/usr/share/doc/nvidia-driver-430/nvidia-smi.html
/usr/share/doc/nvidia-driver-430/nvidia-suspend.service
/usr/share/doc/nvidia-driver-430/nvidiasettings.html
/usr/share/doc/nvidia-driver-430/openglenvvariables.html
/usr/share/doc/nvidia-driver-430/optimus.html
/usr/share/doc/nvidia-driver-430/powermanagement.html
/usr/share/doc/nvidia-driver-430/procinterface.html
/usr/share/doc/nvidia-driver-430/profiles.html
/usr/share/doc/nvidia-driver-430/programmingmodes.html
/usr/share/doc/nvidia-driver-430/randr14.html
/usr/share/doc/nvidia-driver-430/retpoline.html
/usr/share/doc/nvidia-driver-430/sdi.html
/usr/share/doc/nvidia-driver-430/selectdriver.html
/usr/share/doc/nvidia-driver-430/sli.html
/usr/share/doc/nvidia-driver-430/supportedchips.html
/usr/share/doc/nvidia-driver-430/vdpausupport.html
/usr/share/doc/nvidia-driver-430/xcompositeextension.html
/usr/share/doc/nvidia-driver-430/xconfigoptions.html
/usr/share/doc/nvidia-driver-430/xineramaglx.html
/usr/share/doc/nvidia-driver-430/xrandrextension.html

Not sure where the binary is installed. I guess the gpu drivers in 18.04 different from 16.04, I mean the target path to be installed. Can you ensure this?

I tried whereis nvidia and it showed me nvidia: /usr/lib/nvidia /usr/local/nvidia /usr/share/nvidia /usr/src/nvidia-430.50/nvidia
I've checked anything there and there are no lib directory:

in /usr/lib/nvidia is only pre-install file
in /usr/local/nvidia is nothing (no one file)
in /usr/share/nvidia/ are nvidia-application-profiles-430.50-key-documentation  nvidia-application-profiles-430.50-rc files
in /usr/src/nvidia-430.50/nvidia i have these files common  conftest.sh  dkms.conf  Kbuild  Makefile  nvidia  nvidia-drm  nvidia-modeset  nvidia-uvm  patches

Dear ydye, could you tell me what should be inside the directory of the driver (/usr/local/nvidia or /var/drivers/nvidia/current)?
I see that in drivers.md file of master branch is following information as an example:

But what exactly should be there?

@andrewsen13
Once, in the yarn type openpai, we install nvidia drivers by ourselfs with nvidia's package. The path /var/drivers/nvidia/current is where the drivers should be installed.
The path /usr/local/nvidia is installed by apt-get in ubuntu 16.04 LTS.
See the code in hadoop nm:
https://github.com/microsoft/pai/blob/pai-0.17.y/src/hadoop-node-manager/deploy/hadoop-node-manager-configuration/nodemanager-start-service.sh#L20
https://github.com/microsoft/pai/blob/pai-0.16.y/src/hadoop-node-manager/deploy/hadoop-node-manager.yaml.template#L110
This path should contain the binary nvidia-smi. But in my mind, you'd better mount all path which installed the nvidia-drviers' file.

@ydye
I have this directory /var/drivers/nvidia/current, but there are nothing too.
However, I know where nvidia-smi locates, it's /usr/bin, I've tried to add it in hadoop-node-manager.yaml.template in the line which you noticed, but it hasn't worked too.
I see that nvidia's libraries locates in /usr/lib/x86_64-linux-gnu, but there are no nvidia-smi for sure. I will try to add /usr/bin and /usr/lib/x86_64-linux-gnu in nodemanager-start-service.sh as a hard-code

By the way, it's the first time you install openpai or not?
If yes, I suggest to wait for the pure-k8s version. In this version, we will support local nvidia drivers.

@ydye
Yes, it's the first time when I want to try to use it, but it's not my first installation. I'm trying to deploy it to a working version.
Could you tell me when pure-k8s version will be ready?

@ydye
I have solved this problem.
I created bin and lib directories in /usr/local/nvidia, after this copied nvidia-smi from /usr/bin to /usr/local/nvidia/bin, and copied nvidia-driver libraries from /usr/lib/x86_64-linux-gnu to /usr/local/nvidia/lib.
After this, I changed in hadoop-node-manager.yaml.template following lines from /var/drivers/nvidia/current to /usr/local/nvidia:

https://github.com/microsoft/pai/blob/pai-0.17.y/src/hadoop-node-manager/deploy/hadoop-node-manager.yaml.template#L55
https://github.com/microsoft/pai/blob/pai-0.17.y/src/hadoop-node-manager/deploy/hadoop-node-manager.yaml.template#L111
https://github.com/microsoft/pai/blob/pai-0.17.y/src/hadoop-node-manager/deploy/hadoop-node-manager.yaml.template#L135

The same I did for job-exporter.yaml.template from /var/drivers/nvidia/current to /usr/local/nvidia:

https://github.com/microsoft/pai/blob/v0.14.0/src/job-exporter/deploy/job-exporter.yaml.template#L70
https://github.com/microsoft/pai/blob/v0.14.0/src/job-exporter/deploy/job-exporter.yaml.template#L78
https://github.com/microsoft/pai/blob/v0.14.0/src/job-exporter/deploy/job-exporter.yaml.template#L98

And now it's working fine without any problems.
@ydye Thank you a lot!
By the way, I want to know anyway when pure-k8s version will be ready? (:

@ydye
Yes, it's the first time when I want to try to use it, but it's not my first installation. I'm trying to deploy it to a working version.
Could you tell me when pure-k8s version will be ready?

@hzy46

@hzy46 , could you provide some detail of that?
Just want to up the topic.

@hzy46 , could you provide some detail of that?
Just want to up the topic.

Sorry for the late reply. It will be ready in this week.


feat: add last updated link to gifts page

#524  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @davidlj95 and the rest of your teammates on  Graphite


Added logo

Added the logo to the repo.

I put them in a folder called /docs/assets/img/, it's a bit nested away, but I do this on my projects to accommodate future file/folder structures under /docs. Feel free to change it.

Added logos of both colours, in both 1200px and 512px
Added PSD source
Updated README with Noun Project credit

Awesome work, thanks @leekelleher! 🎉 #h5yr


Exceedingly slow execution?

I'm using regedit to look up the x86 and x64 uninstall lists (writing a software manager that needs to know if certain things are installed already) and so I use the following code:
const regedit = require('regedit')

const keys = [
  'HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Uninstall',
  'HKLM\\Software\\Wow6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall'
];

// the actual list of individual products
const realkeys = [];

// the list of resolved product entries
const entries = [];

// a list of just product names
const names = [];

/**
 * Expand the x86 and x64 "uninstall" keys to a full list of
 * registry keys we'll need to consult.
 */
function findRegKeys() {
  console.log("Resolving x86 and x64 keys...");
  let processed = 0;
  keys.forEach(uninstallKey => {
    regedit.list(uninstallKey, (err,list) => {
      list[uninstallKey].keys.forEach(key => {
        realkeys.push(`${uninstallKey}\\${key}`);
      });

      // are we done here?
      if (++processed === keys.length) {
        process.nextTick(processKeys);
      }
    });
  });
}

This then continues in the processKeys function:
/**
 * Process all keys found by the previous function
 */
function processKeys() {
  console.log(`Processing ${realkeys.length} registry keys...`);

  // We want this as sync as possible, because it seems
  // like the regedit package will return results *before*
  // they are actually done resolving to real data.
  //
  // That means if we don't wait for each entry to be
  // dereferenced by JSON.stringify first, we're going to
  // have an array of entries that might, if we run through
  // them fast enough (say, a subsequent .forEach) we're
  // going to hit shitloads of CRITICIAL ERROR notices
  // because there isn't actually any real data to work with...

  (function next() {
    if (realkeys.length === 0) {
      return processEntries();
    }

    let loc = realkeys.shift();

    regedit.list(loc, (err, data) => {
      if (err) return next();
      if (!data[loc]) return next();

      let entry = data[loc].values;

      if (!entry) return next();
      if (!entry.DisplayName) return next();

      // Force-resolve this object before moving on,
      // so that we have REAL data for each entry.
      let json = JSON.stringify(entry)
      entries.push(json);

      process.nextTick(next);
    });
  }(realkeys.slice()));
}

Which yields the actual data I care about, and hands that off for a final process pass before returning:
/**
 * Process all entries found. We turned them into strings
 * in the previous function, and we want them to be
 * normal objects, instead. So: map that.
 */
function processEntries() {
  console.log(`Processing ${entries.length} registry entries...`);
  let parsedEntries = [];
  entries.forEach(v => parsedEntries.push(JSON.parse(v)));

  // Then, we do a test. There has to be a vc++ redistributable
  // somewhere, because this is a Windows machine, and almost
  // everything comes with an install of one of those things:
  parsedEntries.forEach(entry => {
    let name = entry.DisplayName.value;
    if (name.toLowerCase().indexOf('redistributable')>-1) {
      console.log(entry);
    }
  });
}

// alright let's get this party started
findRegKeys();

On my system, this finds 690 entries, and then the processKeys function takes, literally, a minute. It needs 60 seconds to properly consult and resolve all the data, which seems inordinately long, and this seems caused by the fact that regedit.list doesn't return "real data", it seems to return early with some placeholder object that has getters for what will be real properties, but accessing them too soon will cause a "CRITICAL ERROR" notice. The only way around this I've found so far is to force full access to the object property-by-property (by using JSON.stringify) and not calling regedit.list for a next key until we're done with the current one.
So is there a way to speed this up? Or, is there a faster way to get an entire subtree associated with a key, rather than "just that key"? (and then I'll happily write my own key to run through that tree in JS. It's going to be way faster than waiting that full minute just to get the list of installed applications in the system. I initially tried to use wmic but that can't actually report on anything that wasn't installed from an .msi package, registry is the only way to get this data)

I know that this issue is pretty old but I want to provide some help for the others.
regedit.list is pretty expensive operation and is taking a lot of time to execute. What you could to improve the situation is to request array of keys instead of each key individually.
So instead of doing this:
keys.forEach(key=> {
  regedit.list(key, (err,list) => {
    // Handling result
  })
})

Try doing this:
regedit.list(keys, (err,list) => {
  // Handling result
})

It will take some time still but overall it should be much faster.


added energytracking capabilites for NVIDIA Tegra Devices (Orin)

This commit adds capabilities to track energy for NVIDIA Tegra embedded devices.  It uses tegrastats (a utility commonly found on those system to do the job). It was only tested on an NVIDIA Orin Dev Kit.

Thanks for your contribution!
We know that some tests are currently broken in local setup, due to some permission issues, but could please add some on this topic ? Not sure how we will be able to run them in CI though, it seems that this hardware is a bit unusual ?


cmd/gc: improve "type *X has no field or method M" message when X is an interface type

When using a new, unfamiliar package, programmers occasionally make the error of using a pointer to an interface type instead of the interface type directly:
http://play.golang.org/p/JulyJVaOrG
The compiler reports the error:
/tmp/sandbox956919287/main.go:8: x.Do undefined (type *ImportedFromSomewhere has no field or method Do)
While this is correct, it would be helpful to point out that *ImportedFromSomewhere is a pointer to an interface type, and better yet, that ImportedFromSomewhere has the desired method Do.

Just for the record (because the CL will be implemented this way), I disagree with the 'better yet'. If you're using a pointer to interface, reporting that fact is enough. That's a day 1 Go mistake, better to focus on that issue than cloud things by saying "and you were this close!"


[Feature Request] Enable OTP configuration

Feature Description
I'd like to be able to configure OTP settings such as valid period, digit-length, and which algorithm is used. I've created a commit that does exactly all this and I'd like some comments/review if possible. My private instances and my friends' private group instances will be running this patch, but I'd like someone with more experience with Gitea and Go to possibly provide input on the future-enablements I've dialogued in the commit comments here.
Screenshots
No response

Just make a PR. It has a better chance to be reviewed.


TypeError: Cannot read property 'asyncComputed' of undefined

i get
TypeError: Cannot read property 'asyncComputed' of undefined
    at Object.vueAsyncComputedInjectedDataFn [as data] (app.js:94221)
    at getKeysFromOptions (app.js:85826)
    at Proxy.render (app.js:85864)
    at VueComponent.Vue._render (app.js:105150)
    at VueComponent.updateComponent (app.js:103394)
    at Watcher.get (app.js:103748)
    at new Watcher (app.js:103737)
    at mountComponent (app.js:103401)
    at VueComponent../node_modules/vue/dist/vue.esm.js.Vue.$mount (app.js:109146)
    at VueComponent../node_modules/vue/dist/vue.esm.js.Vue.$mount (app.js:111545)

Every time i render something

Got this problem too, does anyone know a solution?

I don't remember well but as far as i remember you must import vue-async-computed from npm just before vue-runtime-template.

Hmm in my case I had to disable vue-async-computed competely to get it to work.

Had this issue today. It seems that when the parent component has any asyncComputed and the child component has no data, vue messes up.
Quick fix is to always have data() {return {}} in the child components or set them as functional

Had this as well, for me this commit in a fork fixed it:
https://github.com/Duncank/v-runtime-template/commit/567dd1a9b3c04f5d39996cfb766c9ee9412a0471

Fixed on 1.7.1 6289c88c6812df2037f3e138e35fad75c4fd71cc


Implement infer_schema! that actually works for SQLite

I really dropped the ball on this one. I never should have merged in a
PR with such poor test coverage. As it turns out, this feature doesn't
even come close to working.
The load_table_names function did not specify the escape character for
the LIKE clause, meaning it was including Diesel's metadata tables.
Additionally, SQLite has several internal tables that it creates, which
also need to be excluded from schema inference.
Additionally, the types that it mapped to were far too broad, and would
lead to columns being unable to perform certain actions. Even if SQLite
treats Text and VarChar the same under the hood, we treat them
semantically differently and need to respect the users' schema.
I also learned that PRIMARY KEY AUTOINCREMENT doesn't imply NOT NULL
on SQLite. So that's fun.
I have changed our integration tests to make use of this feature, to
ensure it is working in the future. I had hoped to eliminate the
backend_specific_schema module entirely, but was unable to due to
https://github.com/rust-lang/rust/issues/31369

Review? @mfpiccolo @mcasper @samphippen
I'd like to roll a release with this fix ASAP


iohub conversion of MM data to zarr changes image size

While using the iohub cli to convert MicroManager acquired ome-tiff files to zarr format, the x-y size of the images changes. I tested this on the dataset acquired on Hummingbird microscope, of size (T,C,Z,X,Y) [1,4,21,2048,2048]. On conversion of data to zarr using cli command iohub convert -i /path/to/input/ -o /path/to/output/ the size of data was reduced to [1,4,21,666,666].
On inspecting the .zarray file, I see that the chunking is still at [1,4,21,2048,2048], but the napari display of image shows a 666 by 666 image. Is this a real reduction of data or something that happens on loading the data into napari gui?

This is because napari respects the voxel size metadata, and shows image coordinates in spatial units instead of voxels. If you do viewer.layers[0].shape in the console it should be the correct shape. In this case I'm guessing that your XY pixel size is 0.325 microns.


BGDIINF_SB-3058: Fixed transform geometry caching collision - #patch

The cache.memoize() method uses repr for object argument which can creates
cache key collision because the first parameter is an Polygon object.
A Polygon object is represented as follow with repr:
<shapely.geometry.polygon.Polygon object at 0x7f23f6848e80>.
The hex number being the memory address of the object.
It can happen that two different polygon objects reuse the same memory address
which results to the same cache key for two different polygons ! This is what
happen when searching for blauseeli but was a pure hazard and was not easy
to reproduce locally.
The fix is to use cached() with a custom cache key maker which uses str
instead of repr for the polygon object. This represent the polygon as
follow:
POLYGON ((1 1, 1 1, 1 1, 1 1, 1 1))

really nice catch, thank you @ltshb :muscle:


Tag latest version

The latest releases of sisyphus have not been tagged in git. bower installs based off git tags and as a result, only 1.1.103 can be found. Can we please add some git tag's for the latest and past verisons?

Tagged the latest version.
Given that most of the past versions were patch updates, normally you want to use the most recent 1.1.2
bower install "sisyphus#1.1.2" does the trick.

Awesome, thanks =)


Using darker background for error text in dark mode

Currently, error text is displayed as white text on a light red background, which is very difficult to read. This PR just changes the background color to a darker red when the app is in dark mode. I personally found the darker shades of Colors.red too saturated for this use case, so created an arbitrary shade of dark red to use instead. I have no objections if you want to change the shade of red, I just want the text to be legible. You can find before/after screenshots attached below.
Before

After

Good job, thanks!

@all-contributors please add @jmatth for code


Adds Dockerfile

Switch from graphite backend to elasticsearch.
Dockerfile for building on-statsd image.

Assuming the hound comments aren't meaningful here and should be ignored.
How do the applications know where to send the statsd data to this instance? I think in the code & VM based examples, it's locked into udp on localhost - is there additional configuration needed to be passed into the other Docker files to kick that data into this container so that we collect it and route it into ElasticSearch?
Likewise, how does the configuration here for localhost translate into where to send the data from this statsd receiver/forwarding instance?

This is actually a bit magical. Since I'm loading all the RackHD docker containers with net: "host" they all run on the same localhost. That allows this to run a statsd server on port 8125 that is accessible by the other RackHD services. It takes messages from statsd and pumps them back to elasticsearch. Since I'm mapping elasticsearch port to the host in the docker compose it can receive requests from on-statsd.

Added copyright to Dockerfile

:+1:

:+1:


Update fmtlib to version 9.1.0

@mthies I believe this should fix issues #10 an #11

Yes, I can confirm that this PR fixes #10 and #11. I.e. I can build just successfully on ArchLinux against 9.1.0 when I replace my patches for these issues with this PR.

LGMT :)


Convert app to responsive app.

1. What
We should make the following design responsive.
The xd to flutter plugin provided by Adobe xd is difficult to respond to.
We have to go through the process of refactoring your code.
Design prototype : https://xd.adobe.com/view/3b380aca-6f30-43ab-a408-53407a516034-6e6b/
2. Why
Our application runs not only in the tablet PC environment, but also in the desktop environment such as windows, mac, and linux.
The minimum resolution was fixed at 1280 * 768 in the previous meeting, but it should be possible to increase the resolution.
Making our app responsive is inevitable.
3. How(You guess)
Block provider pattern, and just coding it to convert to responsive app.

The xd to flutter plugin provided by Adobe xd uses the adobe_xd package.
In that, we can set Pin to responsive size. And this allows for easy configuration of reactive layouts.


replace referer with request.get_host() to match what django checks against

See https://github.com/ottoyiu/django-cors-headers/issues/309

This is failing a test. I've spent ten mins trying to figure out why, but I'm not sure - for some reason get_host() is ending up with a 400, I think due to the host not matching ALLOWED_HOSTS, but afaict all the settings should be in place to allow this.
I'd also like a test specifically for the behaviour you were trying to fix.

@jacobg do you intend to come back to this?

@adamchainz yes hopefully in the next few days

Opened a new pull request https://github.com/ottoyiu/django-cors-headers/pull/326


Update import/export first step page wording

From Kyle's email to update wording on the first import/export page...
I've also added some styles/margins to the content within the tool as the morpheus reset is currently removing all margins from p, h2, etc.
I removed the Blank Template link from the panel, but left the code in there to generate it.. just in case.

Apparently that morpheus reset has been corrected, I'll merge this in, but just check it's still as you intended. Cheers.


RFC: Mount package.json for Corepack

[ ] Add changeset if we're happy with this change

Our Dockerfiles currently run corepack enable pnpm without any versioning information:
https://github.com/seek-oss/skuba/blob/bc2c69d3b85a6aba738c5d63d01f810a69b1a248/template/greeter/Dockerfile#L5
This may use a different (newer) version than is specified in package.json:
https://github.com/seek-oss/skuba/blob/6c2f984ab3f8681604bda2ecd73b130d0ecf8d52/template/greeter/package.json#L21
This can result in a subsequent pnpm install --offline hanging in CI on the following prompt:
Corepack is about to download https://registry.npmjs.org/pnpm/-/pnpm-8.15.4.tgz.

Do you want to continue? [Y/n]

Couple options:

Stop pinning pnpm version in package.json
Mount package.json on that Dockerfile command

This implements option 2, but I could be convinced the other way.

Mount package.json on that Dockerfile command

This renovate upgrade the packageManager version if we do option 2?

@tadhglewis Yup, Renovate will raise PRs 👍

🤦 forgot a changeset


DateRange in docs not working

rng = DateRange(start, end, offset=BDay())

triggers:
NameError: name 'BDay' is not defined
should be
rng = DateRange(start, end, offset=datetools.BDay())

http://pandas.pydata.org/pandas-docs/stable/timeseries.html#generating-date-ranges-daterange

This is a good point, BDay is not in the global pandas namespace. We should probably change the docs.


Look into using WeakHashMap in MenuManager

See the current TODO comment in the menus variable of MenuManager. Furthermore, this may remove the need for using register and unregister methods at all.

This probably won't work well because with the current implementation of using a WeakReference<Inventory>, a NPE is thrown if the menu or inventory is referenced while the inventory isn't being viewed by anyone


Feat:versioning API

Versioned all API endpoints
pluralized endpoints form singular references to plural

Description

- Versioned all API endpoints from /api/admin/product to /api/v1/admin/product

pluralized endpoints form singular references to plural /api/v1/admin/products and so on

Motivation and Context

Boss @zxenonx  ordered it be done!
How Has This Been Tested?

- all refactored endpoints were tested using postman
Screenshots (if appropriate - Postman, etc):

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

@zxenonx

@zxenonx all changes done


Slurm Commander using slurm 23.02.0-0rc1

Using the latest RC build of Slurm 23.02
scom not working
Thanks!
ERROR: sacct JSON failed to parse, note your slurm version and open an issue with us here: https://github.com/CLIP-HPC/SlurmCommander/issues/new/choose

Hey,
thanks for the feedback.
Haven't got around to testing sc with slurm 23, now i see there is some polishing to be done 😄
Will let you know as soon as i have a fix.

A slight correction from my side on the "some polishing" estimate i gave yesterday is in order.
I've just spun up a 23.02.0 release cluster and the amount of changes SchedMD introduced in their openapi schemas is absolutely staggering.
Right now i'm typing this in a minor state of shock :laughing:
Might be that i'm overestimating and i'll pull myself to a more rational state after the initial "surprise" subsides.
First impression:
I'm having problems seeing how to reconcile the existing code (slurm 21,22 compatible) with the new 23 one and make them play together. It is of course possible, but it makes sense only if it's achievable with a reasonable amount of code refactoring.
In any case, I'll definitely need some time to understand all the changes SchedMD introduced, and see if there is a way to make scom support legacy and 23.x slurm.
Conclusion: support for slurm 23.x might take a while, if it ever happens.
Will keep this issue open and report any progress i might have here.
If anyone reading this issue is interested in helping out, by code or advice, please do not refrain from doing so :smiley:

Right now i'm typing this in a minor state of shock
Might be that i'm overestimating and i'll pull myself to a more rational state after the initial "surprise" subsides.

Took a quick look at the way scom queries the data from Slurm after @shawnhoopes pointed out this issue. Slurm's commands always dumps the latest format (i.e. v0.0.40 in Slurm-23.02) without built-in backward compatibility. Slurm's slurmrestd does not have this limitation and provides versioned queries to avoid changes in the response from breaking existing clients.  slurmrestd maintains prior content plugins for at least 2 releases to give developers of clients such as this more time to port (if needed). I fully understand the code already exists, but I suggest looking into this for future releases. If requiring a standing service is an issue, slurmrestd supports taking queries directly via stdio without running a daemon.
As for porting to the new 23.02 formatting. I noticed that sinfo is called and would have the most drastic changes in content. As part of a project to condense and implement built-in filtering, the sinfo response is now very different and now more closely matches formatted output that can be queried via the non-json output. That prior content was not lost, though, it was moved to scontrol show nodes --json. Due to limitations of several OpenAPI client generators, many numeric outputs were changed to be a dictionary with infinite, number, and set as fields with the number field having the same value as prior formatting. While Slurm can handle overloaded JSON fields internally, it was determined while not being ideal, this was the best way to avoid fatal issues in generated OpenAPI clients. This project's parsers could likely benefit from checking the meta data included in the JSON output to ensure the correct parsers are being used internally to allow a single release of scom to support multiple Slurm releases.
I suggest against grabbing the openapi.json from inside of the Slurm source directly but instead use slurmrestd to generate this with the wanted content plugins via -s v0.0.39,dbv0.0.39. This will avoid having prior versioned paths, the need to correct the URL paths to include the server path, and will work with v0.0.39+ content versions. Slurm uses a new model of generating OpenAPI schemas in v0.0.39+ instead of hand maintaining openapi.json files which has been unnecessarily error-prone.
Hopefully, this helps with your porting efforts as it would be a shame to have this project get abandoned. I also suggest taking a look at the new outputs now provided in Slurm-23.02 as more information tabs may be possible.

I fully understand the code already exists, but I suggest looking into this for future releases. If requiring a standing service is an issue, slurmrestd supports taking queries directly via stdio without running a daemon.

The only rationale behind using commands instead of slurmrestd was the reach of scom. Logic was: "Every slurm user has them, but not everyone has slurmrestd set up on their site." As much as i would love to do the full switch to rest (it would make my life infinitely easier), i'm still a bit hesitant to cut cmds as i feel it might cut quite some users out. Ideally, i'd like to support both, keeping cmd as a fallback for users whose site admins do not provide restd.
Does this make sense from your perspective? I'd love to hear your opinion on this.

Each site has the choice as to which binaries they provide. It is up to each project to decide prerequisites and what levels of compatibility they will provide.

Could you elaborate a bit on the relation between rest endpoints and commands like scontrol example above? Is there a 1:1 mapping between them?

In Slurm-22.05, there was a one-to-one mapping for the commands that got implemented. They actually called the same plugin code. In Slurm-23.02, we did a major redesign and split out the code that did the conversion from Slurm's internal data structures to JSON/YAML. This allows us to add the conversion to JSON all over the place without needing to actually touch any of the openapi/slurmrestd code directly along with several performance improvements. The resultant JSON for each internal structure will be the exactly same but the wrapping around it has changed. Right now, the only changes visible would be in the meta response which now provide info about the CLI command called instead of the OpenAPI plugin information.

I've started work on porting, bellow is a more technical description of some ideas and problems i'm struggling to achieve, probably will hit some roadblocks here and there and in that case i'll take the liberty to ask for more assistance if that is ok with you?
I can provide some input on this but others are design choices for any given project.

"hide" data fetching behind an interface, so both cmd and rest fetching routines exist

users/admins will be able to specify rest endpoint and token in the scom.conf and if that is not found, scom fallbacks to cmd
+automatic regen of token

I think this is a design choice for your project of how much compatibility is important vs the complexity of the implementation.

Problem 2: differences between versions (e.g. 21 vs 23)

Example: clustertab table shows two columns, from fields: State and StateFlags, 23+ there is only one coming in.

Still unclear how to best handle: Checking meta data from JSON gives me the version of struct to use when unmarshalling, but i'm still left with the table code which needs to account for the possibility that some fields are missing or changed the type (i remember seeing in some older version an int field becoming string) (this is in cmd case, for rest case i think i might get by with generated code)
Try?:

slurm/json version detection
Versioning of openapi.json and generated code will be split into packages according to versions (generated by querying slurmrestd)
Table code?... switch version{ case X,Y....}? or manually add methods to each package for fetching certain fields?

It might be easier to use some kind of templated code to handle the conversion of these items but I'm not familiar enough with GO to give suggestions. The provided examples of state flags will not have as easy of conversion because there are actually a set of new flags that are available in 23.02.

1.) SLURM Rest can be also started in so called Inet mode by regular users (https://slurm.schedmd.com/rest.html#inet). So maybe we can start a slurmrestd process (which is simply a HTTP wrapper/webserver) when we start scom. Additionally it can work with local authentication if it's in the same munge perimeter (see slide 9 here: https://slurm.schedmd.com/PEARC20/REST_API.pdf). SLURM Rest (AFAIK) is supported from 20.x on. The only caveat is that SLURM Rest has to be explicitly enabled during build/compile time. So some of the sites might not have it :-(

I would suggest against scom starting a slurmrestd daemon as that could inadvertently cause a security issue without extra steps to ensure the sockets are only visible to scom only. Using inet mode naturally avoids any of those issues:
echo -e 'GET http://localhost/slurm/v0.0.39/jobs HTTP/1.1\r\n'|slurmrestd

2.) One additional benefit of having SLURM Rest is that SchedMD recommends to set up a Caching proxy and I guess most sites will such a setup. We have setup an nginx caching proxy that does TLS + caching of the REST calls (5 minutes cache time and url + SLURM user http header is used as caching key). This will help not to overload the slurmctld/slurmdbd and might be good enough to avoid having to develop a scom caching service/process

Caching proxies are really effective to reduce the load on controllers and adding TLS when clients may be outside of the tightly controlled cluster network. The newly added rate limiting the controllers can also help with this: https://slurm.schedmd.com/slurm.conf.html#OPT_rl_enable


fix #132: build static libs

Codecov Report
Base: 68% // Head: 69% // Increases project coverage by +1% :tada:

Coverage data is based on head (0d2b8e1) compared to base (6e713c3).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##            v1.x    #133     +/-   ##
=======================================
+ Coverage     68%     69%     +1%
=======================================
  Files        195     192      -3
  Lines      17488   15067   -2421
=======================================
- Hits       11946   10431   -1515
+ Misses      5542    4636    -906

Impacted Files
Coverage Δ

test/fixtures/parser.hpp
88% <0%> (-9%)
:arrow_down:

src/libhashkit/string.cc
42% <0%> (-6%)
:arrow_down:

contrib/bin/memaslap/ms_task.c
70% <0%> (-5%)
:arrow_down:

src/bin/memcapable.cc
86% <0%> (-5%)
:arrow_down:

test/tests/memcached/stat.cpp
94% <0%> (-4%)
:arrow_down:

src/libmemcached/dump.cc
65% <0%> (-4%)
:arrow_down:

src/bin/common/checks.hpp
60% <0%> (-3%)
:arrow_down:

test/lib/Shell.cpp
69% <0%> (-2%)
:arrow_down:

contrib/bin/memaslap/ms_conn.c
44% <0%> (-2%)
:arrow_down:

contrib/bin/memaslap/ms_setting.c
75% <0%> (-2%)
:arrow_down:

... and 128 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Downgrade mathigon studio

Changes
Downgrades mathigon studio (upgraded #1966); should fix #1983.

Closing in favour of #1987


ISPN-13773 Upgrade Jackson to 2.13.1

https://issues.redhat.com/browse/ISPN-13773

Merged, thanks


chore: change Config signature

Please rebase on master

Should I still rebase on master? This was related to #11 and it seems like it is not relevant anymore

Renaming dir to path is a good idea, so I'd prefer to land this


Binary

how do to keep ORM_INSERT binary?
Here's what happened (PlayerInfo[playerid][pCA] = LANG_ENGLISH | language)
3133300000000000

Could you explain your problem more precisely? I don't really understand what your issue is.


Question: set the limit of number connections per host

Hi
I wonder is there any way to specify the max number of simultaneous connection for the specific host? number of req/sec?

Ranch has max_connections. Not sure what the point of limiting the number of reqs/s would be.

I have seen this option, but question was about "for the specific host"

You can always have a separate listener per host. Otherwise no, especially since it's requests that have a host, not connections.


Over heating settings - what exactly does it change? + EEV lifetime?

Hi, I am trying to understand the logic behind the AC's internal algorithm that regulates the actual compressor power. It is (should) be closely related with the "over heating setting" but what those numbers even mean? (+4/+6°C). What happens when the tempeature is (presumably) +4°C from setpoint and what happens at +6°C? What are the default (0) values?
I am using LG Standard plus PC12SK
I have it set to +-1°C in hopes it will better regulate indoor temperature and I first thought it will just get to the setpoint +1°C and slow down the compressor and if it gets -1°C from setpoint it will speed up. But the "black box" is more complicated than this. When the temperature started to rise quickly I was still -1°C from setpoint and at this point the AC lowered compressor power.
Does anybody have more observations? Maybe we can get a better picture how it works together.
One observation I can share is from before I started using this wired controller:
I hardwired the actual thermistor input to fixed resistor to simulate 31°C. When set to 30°C and turned ON, the AC started at nominal power (around 900W input) and stayed there forever. When I wanted lower power I set the fan speed to low and the AC lowered power to around 500W within few minutes. When I then set fan speed back to HIGH it kept the 500W again forever.
After defrost it started again at 900W.
Why 30°C? because at JET fan mode the compressor power stayed the same (900 or 500W) and I got high fan speed.
Btw interesting is that the actual power consumption actually drops by 100W after turning on the JET mode - presumably because the internal coil gets colder, pressure drops and the compressor does not have to work so hard even at the same speed (rpm/frequency). The opposite can be observed when lowering the fan speed - consumption immidiately starts to rise until some point when the AC decides to lower the compressor speed.
It is honestly really hard to get relevant data with a repeatability to understand the behaviour because sometimes even after power cycle the AC sets different power level even with the same setpoint + same measured temperature. Maybe outside temperature plays a role aswell? Or pipe temperatures/pressures/ time from the last compressor start?...
I tested the workaround template sensor that fakes the temperature reading but in my conditions it didn't work that great. The AC was constantly modifying the power up and down.*  Maybe it should be "tuned" to specific room and the thermal inertia.

To work around 2), if the temperature drops below setpoint - 0.1 and it has been heating for more  than 10 minutes, it forces the unit to work harder by reporting setpoint - 2.5.

I got a feeling that 2.5°C with just 0.1°C difference was too excessive. The AC started ramping the power too quickly and too much and overshoot the target temperature. It got me thinking that maybe report setpoint -2.5°C but only for a few minutes to get the AC power going up and then lower it to only setpoint +1 or even real temp so it won't ramp up that much? I have to test it further but we currently have quite a warm weather...
* EEV?
And one more thing to consider. As we see the AC is really lazy changing the compressor speeds. It likes to set one speed and let it run for hours even when the temperature is fluctuating. This got me thinking that maybe the manufacturer set the software this poorly on purpose! I am not a HVAC expert but the EEV (Electronics Expansion Valve) needs to change position every time the pressure changes to maintain ideal pressure difference for refrigerant evaporation. So with every compressor speed change the EEV needs to change aswell. And those EEV's have for sure limited cycle lifespan. So in typical conditions, even "shitty" EEV and compressor system can last projected 20 years or so...But once we start to mess with the AC by reporting fluctuating temperature and force it to change the compressor speed every 10minutes, those 20years can quickly shrink to much less.... Maybe I am just overly cautious but be aware of this aspect...

Hi, I am trying to understand the logic behind the AC's internal algorithm that regulates the actual compressor power. It is (should) be closely related with the "over heating setting" but what those numbers even mean? (+4/+6°C). What happens when the tempeature is (presumably) +4°C from setpoint and what happens at +6°C?

+4/+6 means it stops heating at setpoint + 6 and then starts heating again when the room temperature reaches setpoint + 4.

What are the default (0) values? I am using LG Standard plus PC12SK

It's the default behavior for the unit. For my units that's +1/+3 but it could be different for other units.

Maybe outside temperature plays a role aswell?

My units do modulate better (less Watt) when it's cold outside. I agree that the behavior of the unit is hard to predict unfortunately :/

This lower wattage does not come from any active modulation. It is purely physics. Lower temperature = lower pressures and lower heat transfer. This means that at the constant speed the compressor does not work so hard and has lower power input.

I don't think it's that. A few degrees C can be the difference between < 300W or > 450W. This seems to be a multi-split issue though - single split units and units from other brands don't seem to have this.

This lower wattage does not come from any active modulation. It is purely physics. Lower temperature = lower pressures and lower heat transfer. This means that at the constant speed the compressor does not work so hard and has lower power input.

I don't think it's that. A few degrees C can be the difference between < 300W or > 450W. This seems to be a multi-split issue though - single split units and units from other brands don't seem to have this.

Yes it can, depending on the indoor setpoint vs indoor temp. And time cycle delays, (internal PID)
Combined with Outdoor temp and RF-gas properties.
Single split units are better at modulating if correctly sized in power for the room.
Multi splits have a bigger "engine" they need to manage demand and offer more, especially if only 1 unit of 4 is running. (for example.)

I'll just chime in with some of my understanding. I might be wrong of course, so I'm trying to share, not to convince :-)

The efficiency of the HVAC is better when the blower in the indoor unit is at max speed or close to it. That means that real-world experience vs. testing by the manufacturer in a lab with noisy fan setting are different.
for multi units (I've one: one ODU with support for 4 IDU, but I piped only 3), the various manuals show that performance is not as good as single split units, and also the numbers are best when the load of all indoor units does match the outdoor unit's rating & design. Rule of thumb, if the load is < 50% of the ODU Capacity (cooling or heating), efficiency is degraded. And likely at 100% or some pretty high percentage, the efficiency is maximized.
EEV: they are made to be used all the time. Same as modulating the compressor's rpm. But on cheap boards, it's likely some lookup tables for some values based on the inputs. i.e. the MB is pretty dumb, all calculations were pre-made during the R&D time.
In the experiment above, with 30C-31C... if that was for cooling, and you are faking the indoor temperature, "maybe" it is valid.
Basically the HVAC systems we have are still quite basic in design, and you can expect the firmware to only handle specific conditions. All the sensors on the ODU are important and working together. You can also only test cooling mode indoor (besides install & emergency modes) when the outdoor temperature is within some range. Same for testing the heat-pump mode. So it's hard to get reproducible data.
Also note that in heat-pump mode, the ODU has to manage freezing coils, so it's behavior will seem less constant and predictable. And again, you have to take the real outdoor conditions and cannot fake them.


Link of "Business Central docs"

The link text after "Business Central docs" (the very first link in this article) shows "https://docs.microsoft.com/dynamics365/business-central" but points to "https://docs.microsoft.com/en-us/dynamics365/business-central", hence to en-us. Not sure whether this was intended?

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

ID: b9c875d8-3401-cfe3-d7d8-aac436b2b53b
Version Independent ID: 4459ce33-7e99-adf3-591a-a665e3db0067
Content: Resources for Help and Support - Business Central
Content Source: dev-itpro/help-and-support.md
Service: dynamics365-business-central
GitHub Login: @edupont04
Microsoft Alias: edupont

Hi Nathalie,
Thanks for identifying this! The underlying link is actually set up to reflect the browser locale, but because it is (nearly) always being accessed from a page that is rendered in en-US (since we do not translate the developer and IT-pro content), it will always render as en-US....
I'll try to reconfigure it to render as the browser locale.

This is now fixed, I hope.


Update Rollbar to 2.11

See #7266
New Rollbar gem has a default timeout of 3s. Each failed request triggers 2 rollbar failsafes and a CartoDB one, totalling at 6 requests. This PR lowers Rollbar retries from 3 to 1 (value before 2.11, as retries were not implemented), so only 6 request are done (instead of 18).
All of this makes Rollbar take 18s to fail which may still be too much (specially for debug messages). Another solution could be running Rollbar in async mode, which creates a thread to do the error reporting while the main program runs.

Please CR @juanignaciosl. Maybe not the final solution (see PR description) but still an improvement. Although maybe it is worth considering using async reporting.

LGTM, although I'd give async a try. The new thread should be cheaper than the network wait. I guess that this would move the pressure from the network to the CPU.

Tried async, both using threading and resque drivers. Async drivers do not handle retries at all: if they fail to send the report, a new report (failsafe) is queued. This also happens when a failsafe report fails, so it loops infinitely until a report succeeds.
So, until they fix that, it is basically unusable in the event Rollbar goes down again. :disappointed:

✨


fix: fix prog description display

Signed-off-by: feng-tao<EMAIL_ADDRESS>
Summary of Changes
fix: https://github.com/amundsen-io/amundsen/issues/701
Tests
What tests did you add or modify and why? If no tests were added or modified, explain why. Remove this line
Documentation
What documentation did you add or modify and why? Add any relevant links then remove this line
CheckList
Make sure you have checked all steps below to ensure a timely review.

[ ] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[ ] PR includes a summary of changes, including screenshots of any UI changes.
[ ] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public python functions and the classes in the PR contain docstrings that explain what it does

[ ] PR passes all tests documented in the developer guide

@ttannis let me know.

many mypy error if package is setup correctly
mypy --ignore-missing-imports --follow-imports=skip --strict-optional --warn-no-return .
tests/unit/api/search/test_v0.py:84: error: Function is missing a type annotation for one or more arguments
tests/unit/api/search/test_v0.py:108: error: Function is missing a type annotation for one or more arguments
tests/unit/api/search/test_v0.py:140: error: Function is missing a type annotation for one or more arguments
tests/unit/api/search/test_v0.py:166: error: Function is missing a type annotation for one or more arguments
tests/unit/api/search/test_v0.py:323: error: "SearchUser" has no attribute "assertDictContainsSubset"
tests/unit/api/search/test_v0.py:422: error: Function is missing a type annotation for one or more arguments
tests/unit/api/search/test_v0.py:428: error: Need type annotation for 'test_filters'
tests/unit/api/search/test_v0.py:445: error: Function is missing a type annotation for one or more arguments

will create an issue and see if the community has anyone could led a hand


Bed merge upgrade

bedMerge, a cmd that accepts a bed file and merges overlapping entries, previously required presorting. Now the cmd simply sorts the input bed file. Also went ahead and added testing for this cmd.

This branch is more up to date than the bedEnrichments PR, and includes all of that code, so now let's plan on using this PR as a candidate to merge.


Added instructions for clean  up the sidecar container

and expose prometheus-rsync service.
Some minor Markdown lint fixes too.
I guess we can add the service as part of the kubeprod-manifests.jsonnet modifications, but I tried to make it easy to understand by the final user as an explicit step on the procedure.

Let's wait until next Monday to let @dbarranco  verify these changes.

Thanks for the changes! LGTM


Some questions about the convergence

Hi ,
Thanks for your great work，it inspired me a lot. I noticed that in your paper, the model can converge to a good result within 20 epochs. I wonder if you have tried to train the models for more epochs(e.g. 100 epochs or more？) to get better results？To be honest，I really want to know the boundary（or the best results）of the model. For example，by training more epochs or by designing more reasonable training strategies，the model maybe can reach a better mAP？

Hi @fengliqiu,
Thanks for taking an interest in our work.
If I remember this correctly, I conducted cross-validation specifically for the number of epochs and found that the model overfits quite badly beyond 20 epochs. The mAP actually drops as training proceeds further. So 20 epochs is sort of a naÏve early stopping strategy. But feel free to attempt longer training schedules yourself!
Cheers,
Fred.

Thanks for your reply  @fredzzhang . Wonderful work！I understand it.
Thank you.
Cheers!


Avoid discarding input bytes after multi-byte encoded codepoint

Previous when pasting text into the console the pasted text
following a unicode codepoint that encoded to multiple bytes
would be lost.

Please note that the build failure appears to be unrelated to the bugfix.


Replace var with let/const, remove dead code, replace bizarre variable names with self-documenting ones

Test on Node 4.4.0 and 5.8.0 instead of 0.10.0. [enhancement]
All instances of var have been replaced with let and const (which is preferred whenever possible). [style]
Branches that could never, ever be reached were removed from the code entirely. [style]
Replaced confusing branch conditionals with simple switch statements. [style]
Replaced bizarre variable names (like MM or mEc) with sane ones (like moon_mean_anomaly, etc.) [style]
Tried to be more careful with types, hopefully removing all instances of using a Date as a number, and using date.getTime() instead. [style]

With all these single quotes, the code feels like it's speaking in a British accent :)
This PR fixes #13.
This PR includes #14, not sure how Git appreciates that.

Woo!! Shall I publish as 0.3.0?

:+1:

Done!


[FEATURE REQ]support OpenAI assistant api

dose this SDK support OpenAI assistant api？

@mssfang please follow up

@oneanime azure-ai-openai SDK doesn't support assistant API. We are creating a new sibling package, azure-ai-openai-assistant SDK to support assistant API. ETA for the first preview will be soon TBD. Hopefully, will be next month.

@oneanime We just released the first beta of OpenAI SDK for java for Assistant:
First beta is released. https://repo1.maven.org/maven2/com/azure/azure-ai-openai-assistants/


use monospace font for code

yeah... title... this should do the thing
proof:

it may or may not use SF mono (in any case it'll just use discord's default mono font if SF mono is not found)
i also made a repo with all SF fonts it needs to import (this might be more reliable) but let me know if i should change it back to fontapi.ir

yer welcum lol


feat: 5301 - added an erasing tool for proofs

What

Added an "eraser tool" when the user crops the proof image. The typical use case is barring sensitive data in a receipt, e.g. name or account number.

Screenshots

CropImage
getCroppedBitmap

Uploaded image: https://prices.openfoodfacts.net/img/0003/pRFjLvNol8.jpg
Part of

#5301

Files
New files:

eraser_model.dart: Model about the eraser tool: coordinate computations.
eraser_painter.dart:  Painter of the eraser tool: displaying thick lines.

Impacted files:

background_task_add_price.dart: displaying the eraser bars if relevant; new eraserCoordinates field
background_task_image.dart: minor refactoring
crop_helper.dart: new enableEraser field offsets parameters
crop_page.dart: added an erasing tool for proofs; refactored
crop_parameters.dart: new eraserCoordinates parameter
operation_type.dart unrelated minor refactoring
product_crop_helper.dart: minor refactoring
product_price_item.dart: unrelated fix for TEST env
proof_crop_helper.dart: minor refactoring
pubspec.lock: wtf
pubspec.yaml: needed upgrade of crop_image to 1.0.13

Codecov Report
Attention: Patch coverage is 0% with 215 lines in your changes missing coverage. Please review.

Project coverage is 7.58%. Comparing base (4d9c7fc) to head (8402e3e).
Report is 165 commits behind head on develop.

Files
Patch %
Lines

packages/smooth_app/lib/pages/crop_page.dart
0.00%
68 Missing :warning:

...ages/smooth_app/lib/pages/prices/eraser_model.dart
0.00%
61 Missing :warning:

...ages/smooth_app/lib/background/operation_type.dart
0.00%
27 Missing :warning:

..._app/lib/background/background_task_add_price.dart
0.00%
23 Missing :warning:

...es/smooth_app/lib/pages/prices/eraser_painter.dart
0.00%
20 Missing :warning:

...mooth_app/lib/pages/prices/product_price_item.dart
0.00%
7 Missing :warning:

packages/smooth_app/lib/pages/crop_helper.dart
0.00%
4 Missing :warning:

...ooth_app/lib/background/background_task_image.dart
0.00%
3 Missing :warning:

...ages/smooth_app/lib/pages/product_crop_helper.dart
0.00%
1 Missing :warning:

...ckages/smooth_app/lib/pages/proof_crop_helper.dart
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           develop   #5341      +/-   ##
==========================================
- Coverage     9.54%   7.58%   -1.97%
==========================================
  Files          325     373      +48
  Lines        16411   18854    +2443
==========================================
- Hits          1567    1430     -137
- Misses       14844   17424    +2580

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Thank you @teolemon for your review!

I believe we also need #5318 to be on the safe side of things

Working on it.


Reword the Checkpointing article - misleading suggestions regarding checkpointing in distributed environment

📚 Documentation
The Checkpointing article suggests, that using trainer.save_checkpoint is the only distributed-safe solution.
It is not entirely the case - Checkpoint callbacks, with regard to the strategy, are also distributed-safe solutions. For example, running DDP with ModelCheckpoint callback is a viable solution.
The docs in question:
Not using save_checkpoint() can lead to unexpected behavior and potential deadlock. Using other saving functions will result in all devices attempting to save the checkpoint.

An answer from @carmocca on Slack channel:
carmocca
1. Each process is tied to a device in DDP
2. The devices all_reduce the weights as previously said
3. Each process runs the modelcheckpoint logic
4. trainer.save_checkpoint() is called (maybe)
5. The strategy-specific logic saves the checkpoint, in the case of DDP only rank 0 (master) does actually save

Slack conversation in question:
Michał Rembalski
Hi there,
I recently stumbled upon a possible issue in PL. I have created an issue on GitHub to track it - if anyone could give it a “thumbs up” or something to propagate it further (I know it’s easy to forget about an issue with so many being open), it would be much appreciated.
https://github.com/Lightning-AI/lightning/issues/17242
william falcon
last i checked, lightning saves one checkpoint on the root node (that’s been true for years). it does not save checkpoints on the other nodes.  (edited)
Michał Rembalski
Hi, first of all, it’s great to use PL and out of the tools available, I really like it.
The result may indeed be just one file on one node. I just checked that the function _save_checkpoint (which calls trainer.save_checkpoint inside) is actually called multiple times from different processes.
I stumbled upon it by accident (wanted to ensure that metadata of any saved checkpoint would also be saved in another place - that’s why I was looking at internal functions of ModelCheckpoint).
carmocca
The behaviour you are seeing is expected and correct. All processes run the modelcheckpoint logic and call trainer.save_checkpoint
But ultimately, only 1 checkpoint will be saved with the DDP strategy. Other strategies need to consolidate the checkpoint across ranks, hence this design
Michał Rembalski
But, if I were to run it with a “deepspeed” strategy, then the checkpoint that would be saved, could be partial, right? And no warning would be shown?
Adrian
For deepspeed it depends on the configuration, but yeah for zero3 deepspeed will save checkpoints in a folder, each rank saves one file, as this is the most important efficient way.
Michał Rembalski
That makes sense.
Then, If I wanted to use ddp strategy with multiple devices and store/delete checkpoint metadata:
The processes are synced before a checkpoint is created.
Should I do store/delete checkpoint metadata only on rank_zero or just “latest” one (or, if the processes are synced - it doesn’t matter, since the checkpoint is the same for all of them).
Also, how does this look for ddp_spawn? The docs say:
Since .spawn() trains the model in subprocesses, the model on the main process does not get updated.
Which process would save the checkpoint then? Would it be full/partial?
Jirka
[@Adrian] [@carmocca] lets update the issue too :slightly_smiling_face:
carmocca
[@Michał Rembalski] You don't need to worry about any of this! Just implement state_dict for a component and return you metadata
Note that only the state from rank zero will be saved, so if the state differs across ranks, the other rank's state will be lost. (The weights do match of course)
Michał Tyrolski
Hi
[@carmocca] - how it works behind the scene? I mean, if each gpu worker computes gradient, then only master gpu receives all gradients, accumulate it and update weights, then share it to the rest of gpus along with updates weights, is that right? In that case state_dicts will be different among different gpus, right?
carmocca
As you said, the gradient updates are all reduced, meaning all devices will have the same version. https://pytorch.org/tutorials/beginner/ddp_series_theory.html
Then the state dict is saved. So they will match
Michał Tyrolski
ok, so checkpoint is being sent only from master node, right? Btw. thx for sharing
carmocca

Each process is tied to a device in DDP
The devices all_reduce the weights as previously said
Each process runs the modelcheckpoint logic
trainer.save_checkpoint() is called (maybe)
the strategy-specific logic saves the checkpoint, in the case of DDP  only rank 0 (master) does actually save

carmocca
I updated the linked issue. Please continue in it
Michał Rembalski
[@carmocca] thanks so much for explaining it! It all makes sense now.
However, I still think that the docs could be updated, especially:
Not using save_checkpoint() can lead to unexpected behavior and potential deadlock. Using other saving functions will result in all devices attempting to save the checkpoint.
It seems a bit contrary to what you wrote - strategy-specific logic saves the checkpoint, in the case of DDP only rank 0 (master) does actually save.
carmocca
That is still correct
"Not using save_checkpoint" refers to you manually doing torch.save()
carmocca
If you do it through the trainer, the strategies take care of handling what's specific for distributed setup
but if you do torch.save , you are on your own
Michał Rembalski
I’d rather say it refers to trainer.save_checkpoint.
It is the line above it. Latest docs:
https://lightning.ai/docs/pytorch/latest/common/checkpointing_intermediate.html
I understand that Trainer’s Strategies do handle the checkpointing, even for distributed computation, but the docs state that for distributed computation you should only use trainer.save_checkpoint. At least, that’s how I understood it.
New
carmocca
then we clearly need to reword it!
Would you like to open an issue about that?
Michał Rembalski
Sure, I can do that.
cc @borda

@mrembalski How do you suggest that the text is clarified? Feel free to open a PR updating the text

@carmocca i'll open the PR soon (probably today/tomorrow). I was mostly confused that there was no word about strategy of training taking part in saving the checkpoint - and most of the strategies (if not all) do support saving the checkpoints (even if they do call trainer.save_checkpoint underneath).


To handle cases where bash arguments are not made

(Unspecified Target)

This is the wrong way to do it - notice how the other commands show their help if you use them emptily.

Agreed, closing this and adding help to it

Please don't close pull requests when asked to change things. Just leave the pull request open, and push your changes to it.

@architdate - you can actually just reopen this pull request and push your changes to your patch-1 branch to update this

Reopening as suggested

You probably don't have to explain what console access means in the help command

The sole reason I did that TBH is to help people realize that console access is enabled only when both conditionals of being a Global Administrator and having either user.id or the current IP in consoleips are satisfied (For other servers generally not PS! main.)

Server operators should already know what that means though

Also, in the help command, you could probably mention that /bash accepts multi-line arguments as well


Problem "Save picture as" on IE

Configuration:

Internet Explorer : 11.0.9600.18762
Windows 7
PDF.js version: 1.9.640

I can not find "Save picture as" on IE (see attachment)

This is ok for Chrome and Firefox.

Is it possible to correct this anomaly?
Camillio

Closing as incomplete. Not enough details provided. Also, looks like out of scope of this project -- viewer is designed to display pages content and not re-save it as an image.

Okay,
I ask you a question: From the viewer, is it possible to download the images?
Thank you for your reply

From the viewer, is it possible to download the images?

We don't provide the UI to that in the demo viewer. You can add this functionality, if possible, to your customized version.

Thanks :-)


express.post is not a function

Hi there,
Apologies for the lack of detail around this, but I'm struggling somewhat.
I've used the example code for an express integration, but the application fails as soon as I start it with the following error:
TypeError: express.post is not a function
    at express (/home/ubuntu/workspace/node_modules/alexa-app/index.js:491:13)
    at Object.<anonymous> (/home/ubuntu/workspace/server.js:10:10)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Function.Module.runMain (module.js:441:10)
    at startup (node.js:139:18)
    at node.js:974:3

I have removed all dependencies from my package.json and any other files, but I'm still getting the error. However, when I use the code in a fresh project, it is working as expected.

As expected, this was a local environment issue. Sorry!

@tombarton Tom, any chance you can help me out with what was causing this?  Between yesterday and today I have found myself in this same situation and am trying to eliminate variables of what it might be.

@alistairpaul I'd suggest removing your package.json and starting with just alexa-app. Start adding dependencies back in one at a time until you find the troublemaker.

i have the same issue. trying with only sample apps provided. hello-world does not even start. package.json has only alexa-app

uninstall/rm the alexa-app module inside the hello-world app would rid of this problem

Could someone give any details on how they solved this? The comments above didn't help me

For me the issue was that I used an older version on how to pass the express object
    alexaApp.express({ expressApp: app }); //outdated

The above is outdated.
Instead I am now using
    alexaApp.express(app); //works


Deriving from ControllerBase vs Annotation

This article leaves us in more darkness about the pros and cons associated with the use of one or the other method than before we read it. Thanks.
Now, the questions are: Why there are two methods; what are their advantages and disadvantages; which method will be supported longer in the future, etc, etc, etc.

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

ID: b391017f-25e1-d5e1-c4f7-020408ade7b5
Version Independent ID: 263a7b64-2e42-bbfc-c1d3-61680438e1e4
Content: Build web APIs with ASP.NET Core
Content Source: aspnetcore/web-api/index.md
Product: aspnet-core
Technology: aspnetcore-webapi
GitHub Login: @scottaddie
Microsoft Alias: scaddie

32.4K PV, 34 ratings, 62% CSAT.
@williamTri  thanks for bringing this to our attention, I agree with you.
Article needs to be rewritten and replace all the repository stuff with the ValuesController generated by the templates, or better yet, a subset of it.
The imperative Derive class from ControllerBase is unclear - why are you doing that. It should be something like, Historically, web API controllers derived from  ControllerBase -
Actually the templates still do.
Then in the sample they decorate with [ApiController] but keep ControllerBase
It never really tells what that attribute does.
Article needs a scrub.


Slack channel / Discord for discussion

Hi,
Is there / is there a possibility for a slack/discord for discussion about using this lib?

@jq Any idea for this?


Add dev script for summarizing IBU CR

We should be able to do something similar with the "brief" display of the CR, ie. show a summarized highest-condition status in "oc get ibu", but maybe this is useful for folks until then

/lgtm

/override ci/prow/integration


Navigation bar

Description
The navigation bar needs a link added to a separate F.A.Q. page, as referenced in #8 . The entry for the F.A.Q. can be found here on the wiki.
The other links in the navigation bar should scroll to their respective section on the homepage. The product link's behavior may depend on #19 .
The logo on the left of the navigation bar should link to the top of the homepage.
The navigation bar should float as the user scrolls down the page.
The navigation bar should be displayed across all pages of the site. Depending on #19 , there may be a Products page. If so, it should behave as (the navigation bar in the Lamassu products page)[https://lammasu.is/products/] does.
Tasks

[ ] Add F.A.Q. link to the navigation bar
[ ] Remove "Navigation" link from navigation bar
[ ] Ensure each link and the navigation bar logo either scrolls to its respective section or links to the correct page
[ ] Floating navigation bar
[ ] Navigation bar persistent across site, behaves properly on each page

Git Guild Bounty Program

Total
Dev
Sales
Reporter
Tester(s)
Maintainer
Documenter

N/A
assignee(s)
@isysd
@indieinc
@indieinc, @d3brouille
@cindy-zimmerman
@d3brouille

$40
$24
$2
$2
$8
$2
$2


Users can join an event multiple times and be registered more than once

Tapping the same option twice will duplicate the registration for that user  in that option.
Tapping a different option when already registered does not switch registration types.
Tapping Leave will delete all registrations.

This is actually a debugging feature that’s enabled by flag. I’ll switch it off when I start running the prod bot and fork off a dev bot instance.


Autocompletion for already existing identifiers

There is an annoying case for autocompletion: when already have, say singleton imported from Data.Array, when I start typing this identifier it offers autocompletion with another variant first in the list (from Control.Monad...).

Usually still convenient and automatic to use autocompletion: press tab, it inserts the import, has to press Ctrl+Z so it removes the import. This is still annoying and seems bad experience.
So it either should just show only one completion variant (from the existing import). Or show this variant as the first in the list. Any suggestions on how this can be dealt with?

Yes, that is annoying.
The information on the current module imports is available when we do the completion request. In fact there is or was an option to only complete from existing imports so some of the logic may be there already. Whether it requires post-processing or 2 requests should be very possible in the language server.


SyncTeX backward synchronization sometimes off-by-one

Our SyncTeX parser often jumps one line before the right position, but not always.
I don't know why, nor if this behavior also happens with the official parser.

The current approximation seems good enough and the "off-by-one" actually comes from SyncTeX records, not from a bug.
Closing for now ("behaving as expected").


also read cargo.toml

https://doc.rust-lang.org/cargo/faq.html#why-cargotoml
"Sorting files often puts capital letters before lowercase letters"
could you please provide your analysis on how you count "often"?
cause its not with coreutils 8.31, ls:
$> touch foo Foo bar Bar
$> \ls
bar  Bar  foo  Foo

nor sort:
$> \ls | \sort
bar
Bar
foo
Foo

\ is used here to bypass aliases.

"ensuring files like Makefile and Cargo.toml are placed together"
did you know that make also reads makefile?
so please follow makes lead and also read cargo.toml.

An example of where "capital letters before lowercase letters" sorting is done is Github.

i'm sorry, i should not have brought this up (again, it seems. was hard to find old tickets cause github has no case-sensitive search, the irony...).


Added Shift Left principle

Is this pull request a content or a code change? (Please fill in the relevant section and delete the other)
Code change
I can confirm:
Accessibility considerations

[ ] This change will not change layouts, page structures or anything else that might impact accessibility

or

[ ] This change might impact accessibility, automated aXe tests cover the impact

or

[ ] This change might impact accessibility and is not covered by automated aXe tests - manual testing has been performed
(If the change might impact accessibility then please add some further information here)

Content change
I can confirm:

[x] Content does not include any code or configuration changes (excluding frontmatter information)
[x] Content meets the content standards
e.g. Writing a principle and Writing a standard
[x] Content is suitable to open source, i.e.:

Content does not relate to unreleased gov policy
Content does not refer to anti-fraud mechanisms
Content does not include sensitive business logic

[x] Last updated date for content is correct

Abandoning this one in favour of a "Catch problems early" pattern instead


Fcos num pos

Model
4GPU
8GPU

R50-GN-1x
36.6
36.7

R50-GN-mstrain-2x
38.7
38.5

Why is FCOS in mmdet much worse than that of adet (https://github.com/aim-uofa/AdelaiDet/tree/master/configs/FCOS-Detection)?

Why is FCOS in mmdet much worse than that of adet (https://github.com/aim-uofa/AdelaiDet/tree/master/configs/FCOS-Detection)?

We don't use all tricks.

why not?

why not?

We have implemented these tricks, you can refer to https://github.com/open-mmlab/mmdetection/blob/master/configs/fcos/fcos_center-normbbox-centeronreg-giou_r50_caffe_fpn_gn-head_4x4_1x_coco.py.
The baseline config should be consistent with the precision in the original paper. https://arxiv.org/abs/1904.01355
This Pr aims to supports training with 8 GPU without the precision drop. I just picked several models for testing.


query action examples for postgresql are incorrect.

A query action will not run unless you specify which postgres database to run the query against. Going to submit a PR with updates to those examples.

@bkett Thanks for opening up this issue. As it's been a while, I'm not sure if this has been resolved or not, or if the PR that you had mentioned submitting has already been merged or never completed. I also understand this might not be an issue that you care about at this time. I'm going to go ahead and close this issue. If it's still a problem and you want to help us resolve it, please feel free to reopen this with additional information. Thanks!


The join operation in the functional interface only supports equality joins

Suggestions:
(1) Rename this join frontend to equijoin.
(2) Give access to theta-joins from the functional interface

:+1:  will work on it!


organizer page redo

-reorganized profile page with live, upcoming, and past CF
-in each fair, organizer will be able to see number of students, recruiters, companies and maybe interviews conducted
-could also view detailed names of recruiters


start event/phase/pool buttons should say something like "lock" instead to be more meaningful to the TO user

also investigate if the start buttons are even necessary


Please add dependency into vendor directory.

Is it possible to add dependencies into vendor dir? Thanks!

It seems there is a indirect dependence when other project use qingstor-sdk? Our concern is from this merge. Please confirm,tks.

Yeah, we use glide to manage project dependencies.

As an end user I don't care what library the sdk depends on. Could you please add library into vendor dir so that I don't need to manage the version of sdk dependencies? Some projects such as docker/distribution use gonvendor as dependency management tool and one should check the source code of sdk to deduce which version of dependencies to use before he can write their own business logic. I don't think this is a user-friendly experience.

Reasonable, I'll add it.

https://github.com/yunify/qingstor-sdk-go/pull/59