link for icon table component

I would like to have the capability of an icon with a clickable link in table component line.

Hi @f8dca !
It's currently not supported directly by SQLPage's icon system,
but you can get the result you want using a markdown column for the icon and the link :
select 'table' as component,
    'My icon' AS markdown;

select '[
    ![](https://tabler-icons.io/static/tabler-icons/icons-png/accessible-off-filled.png)
](https://google.com)' as "My icon",
    'John' as "First Name",
    'Doe' as "Last Name",
    1994 as "Birth Date";

Does that do what you need ?

Yes, i can do this but you should aim for consistency. Other components already have the link attribute so it would make sense to add it to the table too.


Job Factory provides Job tasks with an ambient scope

Description
Job Factory provides Job tasks with an ambient scope.
Problem
ASP.NET provides an ambient scope for Controllers and other components based on the lifetime of an http request. Our background jobs currently don't provide this and resolve all dependencies from the root container.
When an object implements IDisposable, the root container will track this dependency until the app exits, this reference can cause objects to build in memory and prevent proper garbage collection.
This PR
When a jobInfo is dequeued and the corresponding IJob implementation is created, a new scope is provided for that job to run in. At the end of the run the scope is disposed, without being tracked by the root container, allowing for .NET to collect the objects that are no longer in use.
Testing
Describe how this change was tested.
FHIR Team Checklist

Update the title of the PR to be succinct and less than 65 characters
Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
[ ] CI is green before merge
Review squash-merge requirements

Semver Change (docs)
Patch|Skip|Feature|Breaking (reason)

Not sure why this check says failing, the build looks fine:

I agree. This may be the same issue Isao ran into. Do you want to just merge it?


Add targets to create a release package for caffeine

This PR uses rules_pkg to allow bazel to build a release tarball that installs all the required components to use caffeine from a cmake project. This includes:

All visible headers from caffeine or any of its dependencies
The caffeine binary itself
Caffeine as a shared library which bundles all of its dependencies
The existing opt plugin
Bitcode files for caffeine-builtins, libc, and libcxx
caffeine-config.cmake
and any scripts that are meant to be used with vcpkg

In addition, I've also added an install target that allows for installing caffeine to a destination of your choice. Run bazel run //:install -- --help to see the flags that can be used here. Beyond that, I've also added an export step to CI so we can get a release tarball from any commit that passed CI if we so choose.
This should be enough to be able to use caffeine from cmake without needing to go through the cmake build system for caffeine at all.

I'd be down with stripping out the majority of the cmake build system once I'm sure people aren't using it day-to-day.


Handle missing attachment types. Facebook

Proposed changes:
If a user sends a voice message to the bot using Facebook, users messages were set to the attachments URL. The same is now done for the rest of attachment types(image, video, and file).
Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[x] updated the changelog (please check changelog for instructions)
[x] reformat files using black (please check Readme for instructions)

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

Thanks for submitting a pull request 🚀 @rgstephens will take a look at it as soon as possible ✨

An alternative way would be to check only once if there is an attachment(message can include only one attachment).
But this way you could easily add more code if you want to handle attachment types differently.


sjcl, paranoia and entropy

https://github.com/aws/amazon-cognito-identity-js/#random-numbers
The amazon-cognito-identity-js mentions using a paranoia of greater than 0 and calling startCollectors() on the sjcl library to provide entropy for older browser and mobile os'.
Any reason why it was not done within this quick start?

SJCL was removed as a dependency, a recent pull request had refactored the sdk to make use of web cryptography apis instead of utilizing the sjcl library... I think.

That PR was rejected and not pulled in.
It looks like this PR resolved the issue.
https://github.com/aws/amazon-cognito-identity-js/pull/281
Which makes my question moot.
Next question. Do you have plans to update the quickstart to use the new aws js lib (1.13.0)?

@adamclerk ,
There's no plan to upgrade the aws js lib as of now. You can use the following link to customize your sdk with the latest code: https://sdk.amazonaws.com/builder/js/


dependencies ignored when --root is used

Hey,
This definitely seems like a bug, as I can find no reference to it (nor does it make sense) as a feature.
Issue:
When "--root" is used with setup.py (required for system package installs, e.g. RPM), dependencies listed in setup.py are ignored.
Steps to reproduce:

Create a virtualenv
Download a package with dependencies, like cryptography
Run python setup.py install --root=anywhere

Observe that no dependencies are installed, even though listed.
Null Test:

Create a virtualenv
Download a package with dependencies, like cryptography
Run setup.py install

Observe that dependencies ARE installed in this case.
What I would expect:
Either setup.py errors out that dependencies are missing (preferred), or it attempts to install the dependency packages into the same root.
Why this matters:
When creating RPMs or pacman pkgs of python packages (very common for production environments), you must install relative to the package root.
For example:
python setup.py install --root=$RPM_BUILD_ROOT --record=INSTALLED_FILES
However, without dependency enforcement, the requirements of a package may change, and it will build without error, but portions of the installed module that reference the new requirements will fail.
If yall don't agree that the default behaviour should change, at least maybe we should add an argument like --ensure-deps which will error out if those dependencies are missing.

a --root install is outside of what setuptools properly manages, so it doesn't mess with things
my personal opinion is - if you want manual control, take all of it
as for the dependency check - a --check-deps flag sounds helpful,
the easy case is something like requiring the install_requires into the workingset,
however packages also use extras, which are harder to account for
are you up for implementation?

@RonnyPfannschmidt How is your implementation going?
I prepared https://github.com/cielavenir/setuptools/commit/77413a754638eacdca32b24c0bebf90313ecd577. The basic functionality is working. How do you think? Do we need extra_requires handling?

Im absolutely unaware, i never contemplated or tried implementing as its simply not a use case i have
Afflicted users are probably the most likely to have a sensible answer

@kata198 Does my patch work for you? (it should be cherry-pickable on 44.1.1 as well if you are Py2 user).
In my case, --root is used in https://github.com/GNOME/jhbuild/blob/3.38.0/jhbuild/modtypes/distutils.py#L78 .


Creating a 3D 360 degree volumetric capture video

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

closing this issue, but if you have more questions, please let us know.

Hello @wes-b,
I tried the green_screen example with the following parameters for both configurations (one camera and two synched cameras) and the result seems to be exactly the same one. See the following screenshots:
Result when running it for two cameras >green_screen.exe 2 9 6 22

Result when running for it one camera >green_screen.exe 1 9 6 22

Which are the differences I should see? I was expecting to get better resolution for the 2 cameras configuration but it doesn't seem to be any. Any help would be appreciated.

The demo works best when the camera's are only a few inches apart and the color (master) is between the two depth camera's.
See this: https://github.com/microsoft/Azure-Kinect-Sensor-SDK/tree/develop/examples/green_screen


Restrict environment variables in env local store

Exposing all env variables from daprd into the app might expose unwanted secrets for some scenarios. To reduce attack surface, I propose the env requires the list of env variables allowed to be defined in the Component metadata.

What secrets are you referring to? Can we have an example of this that may matter?
It would be good to have a list of all the Dapr env variable so that we are clear which ones we are referring to.

What secrets are you referring to? Can we have an example of this that may matter?
It would be good to have a list of all the Dapr env variable so that we are clear which ones we are referring to.

I am not referring to any Dapr environment variable specifically. I am referring that users might have environment variables in the container that runs Dapr but do not want to have all of them exposed to apps.

I am not referring to any Dapr environment variable specifically. I am referring that users might have environment variables in the container that runs Dapr but do not want to have all of them exposed to apps.

Apps running in standalone mode already has access to all env variables, so this restriction is not adding any protection.


Createconfig

Creating ConfigMap in DeployCluster.sh

hey @aaron-schnieder will you review this when you get a chance? I don't want to block anyone when they try to deploy the cluster this week


getAnimeInfo not pushing episode array

While reviewing past commits, reviewed latest major change and after some review noticed how getAnimeInfo() in Scrapper.js doesnt seem to be pushing anime info as expected. Currently on a train as I am reviewing so no fix will be implemented until later on into the week

Commit c97b0d5 shows todo list. Cannot open gogoanime on the train so I will push this issue to a later date

Seems error was caused due to poor network connection, or issue directly related to network connection, closing issue


run npm i

apparently after bumping the version i never ran npm i... oops...

closes #39
sorry about the double PR guys... my bad.

Coverage remained the same at 100.0% when pulling ee810f394cad14d69d38fa113342d0ff90fcff0b on run-npm into 8ead998d98b0918238153ebeee1b18368741abc2 on master.


[AutoPR] commerce/resource-manager

Created to accumulate context: commerce/resource-manager

(message created by the CI based on PR content)

Swagger seems dead, not updating


Provide API to toggle a section

I am using the following to toggle the display of the current tag:
" Toggle display of current tag in airline.
nnoremap <silent> g<f1> :call MyToggleDisplayCurrentTag()<cr>
fun! MyToggleDisplayCurrentTag()
  if g:airline_section_x =~ 'tagbar'
    let g:airline_section_x = airline#section#create_right(['filetype'])
  else
    if !has_key(airline#parts#get('tagbar'), 'function')
      call airline#parts#define_function('tagbar', 'airline#extensions#tagbar#currenttag')
    endif
    let g:airline_section_x = airline#section#create_right(['tagbar', 'filetype'])
  endif
  AirlineRefresh
endfun

It would be nice if there would be a single function to do this.

I think this is currently out of the question. You might want to document this in the wiki however. thanks!


How to get IBus from ConsumerContext?

I want to get IBus from ConsumerContext, so that I can create MessageRequestClient to do RPC in consumer.
I use callback to archieve this goal. But I think it's not a good solution.
Hope to get an answer. Thanks.

You can't get IBus from ConsumeContext.
In the next version of MT, there will be a way to create a Request Client Factory, which can be used within a ConsumeContext to get the request client, and maintain the proper ConversationId and other headers. Until then, you need to somehow get the IBus into the consumer so that the request client can be connected to the consume pipeline of the bus endpoint.

Thanks for your answer!


Error while excecuting 'ruby newrelic_logwatcher_agent.rb' on Linux

Hello,
I have been trying to install logwatcher agent on a Linux machine and couldn't locate the rubygems and can see the below error while running  ' newrelic_logwatcher_agent.rb, executed 'yum install ruby' command successfully though.
newrelic_logwatcher_agent.rb:11:in `require': no such file to load -- rubygems (LoadError)
from newrelic_logwatcher_agent.rb:11
could someone suggest?

Hello Team,
Basically, we are working on a POC where we are installing the Logwatcher on both Linux and Windows server to monitor log file on those files.
We got some luck on Linux server and have been able to install the agent on the box. Can you confirm:

Do we have a different binaries for Windows?
2, Where we can get the installation steps and minimum rubygem package as pre-requisites on the windows server?

Thanks and Regards,
Monika


can not git clone videogpt

when pip install requirement.txt, there is error
remote: Support for password authentication was removed on August 13, 2021.
  remote: Please see https://docs.github.com/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
  fatal: Authentication failed for 'https://github.com/z-x-yang/videogpt.git/

and when i clone using the url directly, the url of "https://github.com/z-x-yang/videogpt.git" is nor useable.

Thank you for your message. To resolve the authentication issue you encountered when running pip install requirement.txt, please change the URL from https://github.com/z-x-yang/videogpt.git to https://github.com/z-x-yang/DoraemonGPT.git.
I appreciate you bringing this to my attention, and I have made the necessary updates. If you have any further questions, feel free to ask!

Thanks. I think your framework is good,  but for Egoschema evaluation, your result is not good enough compared to VideoAgent and other Agent methods. what caused this do you think?

The works you mentioned are all recent and very good. The possible reasons for their better performance might be: First, they are more specifically designed for the VQA rather than focusing on solving a broader range of tasks. Second, these recent works use GPT-4 as the base LLM, while our performance was primarily tested on last year’s GPT-3.5. The base LLM’s performance is significantly lower.


Add infrastructure to analyze the middleware pipeline.

#318 @avanderhoorn @davidfowl @lodejard
Also:
https://github.com/aspnet/Entropy/commit/0a003940338a641f1a93659d4b79de661da7a3d7
https://github.com/aspnet/HttpAbstractions/commit/162005aa761874a130855bbbc2ef8344a1f95dbe
Initial PR to verify design. Still needs docs and tests.
 This is just a design or right?

It's not enabled by default, you have to enable it with services.AddMiddlewareAnalysis();. https://github.com/aspnet/Entropy/commit/0a003940338a641f1a93659d4b79de661da7a3d7#diff-9f226b9022c280befddc97d32f23dd8fR17
Or were you saying it should be in a separate package?

Separate package in the diagnostics repo

Sure, this hosting stuff can all move to diagnostics with two provisions: 1. It still needs a hosting dependency for IStartupFilter, and 2. I want to leave the http.abstractions stuff where it is so that everyone can get to it without the extra dependency.

It really doesn't belong in HttpAbstractions though.

Moving to diagnostics.


sumo: 1.9.2 -> 1.15.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/sumo/versions.
meta.description for sumo is: "The SUMO traffic simulator"
meta.homepage for sumo is: "https://github.com/eclipse/sumo"
meta.changelog for sumo is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.15.0 with grep in /nix/store/1y1r3jgqa10jvm9329hp0p35l8afz8pj-sumo-1.15.0
found 1.15.0 in filename of file in /nix/store/1y1r3jgqa10jvm9329hp0p35l8afz8pj-sumo-1.15.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
sumo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1y1r3jgqa10jvm9329hp0p35l8afz8pj-sumo-1.15.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A sumo https://github.com/r-ryantm/nixpkgs/archive/efc80cecf649c04c06e912a08b12fb4f5ffaafc0.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1y1r3jgqa10jvm9329hp0p35l8afz8pj-sumo-1.15.0
ls -la /nix/store/1y1r3jgqa10jvm9329hp0p35l8afz8pj-sumo-1.15.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

sumo

Maintainer pings
cc @mtreca for testing.

@ofborg eval

Result of nixpkgs-review pr 205310 run on aarch64-linux 1


test frameworK: dump yaml and include deployment state

YAML should be more readable, deployments are useful when troubleshooting why no pods are ready

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
744177f0c576c044aa00d24c7e99219770663494
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
744177f0c576c044aa00d24c7e99219770663494
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
3cceda6cba76ad5a14961cb8acdfb9562df4d99a
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

nice!


try to publish without error 403 You cannot publish over the previously published versions

coverage: 100.0%. remained the same
when pulling 97045996e5395331268434861a85a933f224d4d7 on joaoneto:build/remove-package-version-and-publish-tasks
into f7001c8848594f8a1b74b2348342cfa6b0259574 on guarapi:main.


Fix #145: add posargs in tox.ini (single test cases)

This PR fixes #145
Without the posargs argument tox has to run the complete test suite. With this patch, you can
pass a test file and a test function. That allows tox to only run this specific test function. For example:
$ tox -e py36 test_semver.py::test_should_bump_major

Keep in mind, it doesn't change the default behavior. It's just an additional feature if someone wants to run a single test function alone.
This may help to speed up the development a little bit. :wink:

Most of builds was broken. CI triggered again.

Builds still failing

I believe it's caused by invoking tests by python setup.py test in Travis CI. Running them just by running tox works fine. Furthermore, it seems that using tox in setup.py is discouraged: https://tox.readthedocs.io/en/latest/example/basic.html#integration-with-setup-py-test-command

Hmn, this is strange. Seems there is a difference between the run with python setup.py test and tox.
I've try a different attempt now

@ppkt Ha, we almost posted at the same time with the same idea. :laughing:
I've replaced the call of python setup.py test with tox -v. Seems to work. :wink:

I've also added a second line with caching pip dependencies. I think this is useful and described in https://docs.travis-ci.com/user/caching
The cache is stored on Travis in $HOME/.cache/pip.

 I think it deviated a bit from the original idea.
I would suggest to use something like this (adjust it to your needs):
Fix #146: improve tox.ini/.travis.yml

* Changes in tox.ini:
  * add posargs for pytest. This allows to run only a single test function.
  * Rename py.test -> pytest as the old spelling py.test will be deprecated in the future.

* Changes in .travis.yml:
  * Add cache for pip to speed up things a little bit
  * Add tox as a installation requirement
  * Replace setup.py with tox as it discouraged in https://tox.readthedocs.io/en/latest/example/basic.html#integration-with-setup-py-test-command

Thanks again @tomschr for your contribution


ipptool: Add predicate to do an HTTP GET of a URI

It would be useful if tools such as ipptool could do an HTTP GET on a resource at a URL provided by IPP attributes that supply URLs, such as "printer-icons" or "printer-icc-profiles" or "printer-strings-uri". This would allow ipptool to implement tests where the content pointed to by the URL could be validated for reachability and other aspects. While it could be that ipptool supports this using libcurl or something, it could also be supported by libcups.

Proposed change:
EXPECT some-attribute OF-TYPE uri WITH-CONTENT "spec"
EXPECT some-attribute OF-TYPE uri WITH-MIME-TYPE "foo/bar[,...,fooN/barN]"

where "spec" is one of the following keywords:

available to confirm accessibility (a GET succeeds for http/https URIs and a HEAD succeeds for ipp/ipps URIs)
valid to confirm accessibility and perform simple format validation/encoding checks
transparent to confirm accessibility, proper format, and the presence of an alpha channel or transparent pixel in PNG images

The tests will apply to all URI values (effectively WITH-ALL-CONTENT/WITH-ALL-MIME-TYPES) since there seems little point in just checking one value in this case.

Maybe also a SAVE-CONTENT "filename" predicate to save the content to a file?

Proposed change:
EXPECT some-attribute OF-TYPE uri WITH-CONTENT "spec"
EXPECT some-attribute OF-TYPE uri WITH-MIME-TYPE "foo/bar[,...,fooN/barN]"

where "spec" is one of the following keywords:

available to confirm accessibility (a GET succeeds for http/https URIs and a HEAD succeeds for ipp/ipps URIs)
valid to confirm accessibility and perform simple format validation/encoding checks
valid-icon to confirm accessibility, proper format, proper dimensions, and the presence of an alpha channel or transparent pixel in PNG icon images

The tests will apply to all URI values (effectively WITH-ALL-CONTENT/WITH-ALL-MIME-TYPES) since there seems little point in just checking one value in this case.

That all sounds good. If the semantics of 'WITH-CONTENT' is 'WITH-ALL-CONTENT' then why not be explicit and use 'WITH-ALL-CONTENT' and 'WITH-ALL-MIME-TYPES'?

Maybe also a SAVE-CONTENT "filename" predicate to save the content to a file?

That looks good - if the "filename" bit is optional then use the filename of the resource pointed to by the URL?

@wifiprintguy WRT the filename for SAVE-CONTENT, it can't be optional but we could define it as "directory or filename" where the directory gets the base name from the URL added for the full filename, and/or some substitution sequences to insert the full filename, the filename without the extension, and the extension, something like:
SAVE-ALL-CONTENT "/path/to/test-%basename%-%index%.%ext%"

to save files named as "test-basename-N.ext".


Add Mark Harwood's Fraud Demo

I am going to add one of @markharwood Fraud Demos into the Examples repo.
Demo Video: https://www.youtube.com/watch?v=liMhiiyQ9co

@michaelkeevildown do you have a PR for this?

it is in the works, something that is on my long list, but there will be a PR coming shortly.

@michaelkeevildown do we still want to include this?

For now I am going to close this, there were a couple of days of hype around getting this implemented from the SA team that has now died down. I am going to close this and if someone wants this demo I will get them to open a new issue and also implement it.

there were a couple of days of hype around getting this implemented from the SA team that has now died down

FYI - I have a blog post pending on tackling hate speech that references this demo video.
If website owners rely on site users to report undesirable content that is another potential source of review-fraud. In the blog I reference the same collusion-detection approaches used in this demo.


[Driver] BN verification fixes/improvements

Fixed --forw 2 for bnormfp16
Changed the order of computations of reference output (resolves issue #1974).
Print error values when verification passed.

[Attribution] @junliume @johnny-keker https://github.com/ROCmSoftwarePlatform/MIOpen/labels/urgency_normal https://github.com/ROCmSoftwarePlatform/MIOpen/labels/testing https://github.com/ROCmSoftwarePlatform/MIOpen/labels/debugging https://github.com/ROCmSoftwarePlatform/MIOpen/labels/enhancement

Testing:
# MIOPEN_LOG_LEVEL=4 ./bin/MIOpenDriver bnorm -n 1 -c 64 -D 128 -H 128 -W 128 -m 1 --forw 1 -b 0 -r 1 ;\
> MIOPEN_LOG_LEVEL=4 ./bin/MIOpenDriver bnorm -n 1 -c 128 -D 64 -H 64 -W 64 -m 1 --forw 1 -b 0 -r 1 ;\
> MIOPEN_LOG_LEVEL=4 ./bin/MIOpenDriver bnorm -n 1 -c 256 -D 32 -H 32 -W 32 -m 1 --forw 1 -b 0 -r 1 ;\
> MIOPEN_LOG_LEVEL=4 ./bin/MIOpenDriver bnorm -n 1 -c 512 -D 16 -H 16 -W 16 -m 1 --forw 1 -b 0 -r 1 ;\
> MIOPEN_LOG_LEVEL=4 ./bin/MIOpenDriver bnorm -n 1 -c 640 -D 8 -H 8 -W 8 -m 1 --forw 1 -b 0 -r 1 ;\
> MIOPEN_LOG_LEVEL=4 ./bin/MIOpenDriver bnorm -n 1 -c 640 -D 4 -H 4 -W 4 -m 1 --forw 1 -b 0 -r 1
MIOpenDriver bnorm -n 1 -c 64 -D 128 -H 128 -W 128 -m 1 --forw 1 -b 0 -r 1
Forward train batch norm verification passed on running mean (4.10829e-08)
Forward train batch norm verification passed on running variance (3.70848e-07)
Forward batch norm verification passed on output (5.26499e-08)
Forward Batch Norm Verifies on CPU and GPU.
MIOpenDriver bnorm -n 1 -c 128 -D 64 -H 64 -W 64 -m 1 --forw 1 -b 0 -r 1
Forward train batch norm verification passed on running mean (4.52692e-08)
Forward train batch norm verification passed on running variance (3.34151e-07)
Forward batch norm verification passed on output (4.07745e-08)
Forward Batch Norm Verifies on CPU and GPU.
MIOpenDriver bnorm -n 1 -c 256 -D 32 -H 32 -W 32 -m 1 --forw 1 -b 0 -r 1
Forward train batch norm verification passed on running mean (4.49798e-08)
Forward train batch norm verification passed on running variance (3.27171e-07)
Forward batch norm verification passed on output (4.10385e-08)
Forward Batch Norm Verifies on CPU and GPU.
MIOpenDriver bnorm -n 1 -c 512 -D 16 -H 16 -W 16 -m 1 --forw 1 -b 0 -r 1
Forward train batch norm verification passed on running mean (4.09102e-08)
Forward train batch norm verification passed on running variance (2.92176e-07)
Forward batch norm verification passed on output (3.72606e-08)
Forward Batch Norm Verifies on CPU and GPU.
MIOpenDriver bnorm -n 1 -c 640 -D 8 -H 8 -W 8 -m 1 --forw 1 -b 0 -r 1
Forward train batch norm verification passed on running mean (4.09668e-08)
Forward train batch norm verification passed on running variance (2.84293e-07)
Forward batch norm verification passed on output (3.88711e-08)
Forward Batch Norm Verifies on CPU and GPU.
MIOpenDriver bnorm -n 1 -c 640 -D 4 -H 4 -W 4 -m 1 --forw 1 -b 0 -r 1
Forward train batch norm verification passed on running mean (3.44939e-08)
Forward train batch norm verification passed on running variance (2.16954e-07)
Forward batch norm verification passed on output (3.63261e-08)
Forward Batch Norm Verifies on CPU and GPU.

@junliume This can be merged to develop, I guess.


SharePoint add-in for USGCC High

The article describes where to register SharePoint Add-ins depends on location
https://docs.microsoft.com/en-us/office/dev/store/create-or-update-client-ids-and-secrets
But what about US Government customers? According to this article https://docs.microsoft.com/en-us/azure/azure-government/documentation-government-plan-identity#selecting-identity-for-an-azure-government-application
there are two kind of US Gov customers:

US GCC who is hosted in Public Azure AD. This kind of customers can use regular SharePoint ACS endpoints and client id and client secrets which is registered in Seller Dashboard

GCC High or DoD who is hosted in Azure Government AD - what end points should they use? How to register client id, client secret if ISV has multitenant add-in?

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

ID: 2be8c8d6-7ed2-1907-3038-49d8e1c92e8a
Version Independent ID: a2adbe13-e625-3995-fded-fce6c4a701ac
Content: Register SharePoint Add-ins
Content Source: docs/sp-add-ins/register-sharepoint-add-ins.md
Product: sharepoint
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

@andrewconnell any chance to get some insights on this question?

Sure, but not by me 😀 ...  I don't know anything about GCC. I just triaged the type of question.
In my opinion, you'll likely get a better chance at a response by posting to TechCommunity which is where non-developer topics go.


[backport] Backport upcoming PRs to apache/flink back to streamnative/flink

Cool! Which PR are you working on now?

I haven't started the backport process yet. @syhily  Just created this issue.

https://github.com/apache/flink/pull/20582

https://github.com/apache/flink/pull/20567

https://github.com/apache/flink/pull/19972

https://github.com/apache/flink/pull/19972

First backport for FLINK-27399 https://github.com/streamnative/flink/pull/203

Second backport for FLINK-27917 https://github.com/streamnative/flink/pull/204


Unable to edit calculated column definitions - icon to expand/collapse the definition is not loading properly

I have noticed I can't edit existing calculated columns in the edit dataset view. It looks to me, when I inspect the elements, that the expand/collapse toggle is actually there, but the icon doesn't load, so it's not clickable.
How to reproduce the bug

Open a datasource
Click on 'edit dataset'
GO to the 'calculated columns' tab
add a new calculated col (can be anything, select 1)
go back into the 'calculated columns` tab - there is no icon on the left to open the column definition.

I see the following rwo console errors that I suspect are related:

Loading failed for the <script> with source “<host>/explore/theme-[object%20Object].js”.
404 not found: GET | <host>/static/appbuilder/css/font-awesome.min.css

I also see the following, but I'm unsure if it's relevant:
Unable to infer path to ace from script src, use ace.config.set('basePath', 'path') to enable dynamic loading of modes and themes or with webpack use ace/webpack-resolver
Expected results
TO be able to edit the calculated columns using the expand/collapse toggles.
Actual results
They are not visible, and not clickable.
Screenshots

Environment

browser type and version: Firefox 116 / Chrome 116
superset version: apache-superset[cors,postgres] 2.1.0
python version: 3.10
~node.js version: ``~ n/a
any feature flags active:

FEATURE_FLAGS = {
    "EMBEDDABLE_CHARTS": True,
    "GENERIC_CHART_AXES": True,
    "SQL_VALIDATORS_BY_ENGINE": {
        'postgresql': 'PostgreSQLValidator',
    },
    "DRILL_TO_DETAIL": True,
    "HORIZONTAL_FILTER_BAR": True,
}

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
I have tried pinning flask-appbuilder to 4.1.6, since the changelog says they upgraded fontawesome in 4.2.1, but: apache-superset[cors,postgres] 2.1.0 depends on flask-appbuilder<5.0.0 and >=4.3.0

I believe this is either a 2.0 issue (no longer supported) or a config/permissions issue. This is effectively a duplicate of https://github.com/apache/superset/issues/27059. I'll close this in favor of that, even though both are closed because we no longer support 2.x versions. If this is still occurring in Superset 3.x or newer, we can reopen it and try to get to the bottom of things. Thanks for understanding :)


Add missing TaskCreationOptions.RunContinuationsAsynchronously (tests)

See #1672, which covered only the PuppeteerSharp package.
This PR covers the PuppeteerSharp.Tests and PuppeteerSharp.TestServer packages.

Do we need this?
These are just tests...

I don't want the tests to be flaky

I don't have any strong feelings about the tests tho


How hide disable fullscreen button

There is a function to hide the full screen button ?

@matamune94 Add bottom actions and remove full screen button from there, Here is the code.
YoutubePlayer(
controller: _controller,
bottomActions: [
  const SizedBox(width: 14.0),
  CurrentPosition(),
  const SizedBox(width: 8.0),
  ProgressBar(),
  RemainingDuration(),
  const PlaybackSpeedButton(),
  FullScreenButton(),
]
),

Thanks so much, I have one more problem, when I use _controller.load (id) to load another video, the thumbnail of the previous video will appear again, then the next video will load. how can fix?

@matamune94 I have no idea about that, I only load one video at a time. you can open a new issue for that.

@matamune94 I have no idea about that, I only load one video at a time. you can open a new issue for that.
thanks, i will.

@matamune94 Add bottom actions and remove full screen button from there, Here is the code.
YoutubePlayer(
controller: _controller,
bottomActions: [
  const SizedBox(width: 14.0),
  CurrentPosition(),
  const SizedBox(width: 8.0),
  ProgressBar(),
  RemainingDuration(),
  const PlaybackSpeedButton(),
]
),

I think you need add isExpanded: true inside ProgressBar widget.

I just need to disable the full screen button. nothing else

I just need to disable the full screen button. nothing else. please help. how I disable the only that button

I got it.  don't use the button action before the controller. just put the button action code after set controller
controller: _controller,
bottomActions: [
const SizedBox(width: 14.0),
CurrentPosition(),
const SizedBox(width: 8.0),
ProgressBar(),
RemainingDuration(),
const PlaybackSpeedButton(),
]

Hide  full screen button Please Help

Hide full-screen button Please Help
FullScreenButton() Not Working.


zoom-us: add qtgraphicaleffects dependency

Motivation for this change
I noticed this dep was missing looking at the application logs
Things done

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

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

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

Backport needed?


Update podspec to support tvOS

A lot of pods are being updated to support tvOS and the latest RxSwift development branch has been updated as well. Unfortunately I investigated and found that you can't use specific branches in the podspec dependencies due to versioning issues so we might have to wait for the dependencies to work these changes into a tag. This library is a really great idea and I'd love to use it in a tvOS app I'm coding instead of manually wrapping Alamofire with RxSwift observables.

I think you can specify the specific branch of RxSwift on your Podfile with tvOS support and CocoaPods should be able to use the branch specified in the Podfile (as long as that doesn't break current implementation of Moya)

When I did that it said there was conflicts with Moya's dependencies. Also the Moya podspec only defines target of iOS.

¯_(ツ)_/¯  sorry; i thought you were trying to use a «custom made» .podspec.
It shouldn't take too much to support tvOS. I'll try to get to it today.

Well I did try that too and such resulted in the dependency conflict with my own pods. Here was the pods I was using.
pod 'Alamofire', :git => 'https://github.com/Alamofire/Alamofire.git', :branch => 'tvOS'
pod 'RxSwift', :git => 'https://github.com/ReactiveX/RxSwift.git', :branch => 'develop'
pod 'RxCocoa', :git => 'https://github.com/ReactiveX/RxSwift.git', :branch => 'develop'

Strange, our dependency on RxSwift is ~> 2.0.0-aplha-1.
Esteban, it'd be great if you could do this – I'm travelling and don't have good access to internet. If you need push rights for CocoaPods trunk, let me know.

@ashfurrow I just updated the .podspec to use 2.0.0-alpha.4 which is the one with tvOS support.
Also added all supported «devices» like so:
s.ios.deployment_target = '8.0'
s.osx.deployment_target = '10.9'
s.watchos.deployment_target = '2.0'
s.tvos.deployment_target = '9.0'

I can upload the .podspec but I can't push to trunk (I don't have push rights and the pod spec lint fails due to the dependency issue with Alamofire.
Resolving dependencies of
 -> Moya (3.0.0)
    - ERROR | [tvOS] unknown: Encountered an unknown error (The platform of the target `Pods` (tvOS 9.0) is not compatible with `Alamofire (2.0.2)`, which does not support `tvos`.) during validation.

Analyzed 1 podspec.

[!] The spec did not pass validation, due to 1 error.

We could have it living on a tvOS branch (the .podspec) while Alamofire merges that branch to master or makes an official release supporting it and people could use Moya for tvOS from our support branch.

Sure – it surprises me a library as popular as Alamofire doesn't have tvOS support on trunk yet. Putting the podspec on a branch for now sounds like a good plan.

A branch would be great. Keeping it out of the main branch until all dependencies are updated solves the issue for me at least. Then I can just use Moya and get rid of all the other libraries! Thanks for looking into this everyone!

Branch tvOS should address this.
Please @gregpardo test it and let me know if something is not working.
PS. I also modified the Podfile to use this branch

In my Podfile
pod 'Moya/RxSwift', :git => 'https://github.com/Moya/Moya.git', :branch => 'tvOS'

I get this error on pod install
[!] The platform of the target `Snapshots TV` (tvOS 9.0) is not compatible with `Alamofire (3.0.0-beta.3)`, which does not support `tvos`.

Yeah; try to specify the Podfile like the Demo project in that branch => https://github.com/Moya/Moya/blob/tvOS/Demo/Podfile
Chances are you are missing this from the Podfile:
# Fix for `Alamofire` with `tvOS` support
  pod 'Alamofire', :git => "https://github.com/Alamofire/Alamofire", :branch => "tvOS"

Bear in mind this is temporarily until Alamofire moves tvOS support to the master/official branch/release

Okay I was anxious to try it and I guess I didn't notice the Alamofire part. It's working now. Not sure if you guys want to close this out or leave open until these libraries catch up and this can be merged into master...

Added 2 labels to it.
I think leaving it open would be better so we can keep it in mind.
I'll :lock: the issue though since it doesn't make sense to keep it open.
If any @Moya/contributors has other idea as to how to handle this I'm open to ideas.
Thanks for confirming the fix @gregpardo :bow:

Just noticed that when we merge tvOS with master we'll be able to close #192 as well since the .podspec on that branch already handles OSX, watchOS and tvOS :tada:

http://search.cocoapods.org/api/v1/pods.flat.ids.json?query=platform:tvos
tvOS support requires someone with the latest CP rc pushing, so it's got a pretty slow adoption ( plus my plugin undermines it somewhat )

Ok this will be a little more difficult than anticipated. Its seems like some pods have been pushed to trunk with a new version but without the tvos information. One example is Result. Repo version vs trunk version. The same goes for ReactiveCocoa as well.

What an odd discrepancy. @Thomvis is there any reason the CocoaPods trunk version doesn't have TV support?

We should see an updated version tomorrow :)

Result has been updated on Trunk: https://github.com/CocoaPods/Specs/blob/master/Specs/Result/0.6.0-beta.6/Result.podspec.json @petester42 are there any other that need updating?

Thanks to @Thomvis for his quick turnaround on that!

Yes. The ReactiveCocoa one needs updating too. There are two things wrong with it.

Doesn't specify tvOS when it should
OS X target version is 10.10 instead of the project's 10.9

OK, I've updated the ReactiveCocoa podspec on my fork (see: changes.)
Unfortunately, I don't have 7.1 installed at the moment so I can't validate + push to trunk. Will do when I get to NYC.

Oh, wait. Need to replicate prepare_command stuff.

Cool, did that: https://github.com/ashfurrow/ReactiveCocoa/commit/7dc4d95df1dd3166fb4acef6498662f695e55721 Just need to lint + push.

looks good :+1:

Opened https://github.com/ashfurrow/ReactiveCocoa/issues/4 to remind me

Should be good to go – validated with Xcode 7.1 just in case, and it worked :+1:
https://raw.githubusercontent.com/CocoaPods/Specs/a6b9eb7156e4809e43056cd54b6f754d98be6150/Specs/ReactiveCocoa/4.0.1-alpha-3/ReactiveCocoa.podspec.json

Make that 4.0.2-alpha-3 – had a mistake in the podspec :grimacing:
https://raw.githubusercontent.com/CocoaPods/Specs/112a7c37ff9e86ccb41c4e56a94ef55d7367658a/Specs/ReactiveCocoa/4.0.2-alpha-3/ReactiveCocoa.podspec.json


Progress during pulling image

Hello, when I am pulling image onto one docker host I have progress where I see which layer is downloading/extracting etc.
When I am connected to the swarm I see just
node: Pulling <image>...
Is it possible to have more verbose progress? because when I am downloading big images I am not sure if it is working or not (many times it wasnt working).

@AtomicBit thanks for creating the issue. This is possible to do, and we chose to have simpler behavior as of now. I'm not sure how having a full progress report will affect network traffic, but IIRC we already have access to the reader that reports progress, so perhaps it's just a matter of showing that. I'll look it up.


API with Social Auth

I'm working on using AdonisJS as an API-only in a small project. My problem right now is that while I have Social Auth via Ally working for Adonis Views, I haven't found a way to get it to work when using Adonis as an API service, because I don't know how to wire stuff together for this purpose.

Hey @sebasgarcep! 👋
Are you using 3.2 or 4.0?

Thanks @RomainLanz for answering! I'm using 3.2 by now. Does it matter?

Yes, 4.0 are way different.
Could you paste your package.json to see if you aren't merging 3.2 and 4.0 package?

{
  "name": "adonis-app",
  "version": "3.2.1",
  "main": "server.js",
  "scripts": {
    "start": "echo \"\\033[31mWARN: 'start' will be depreciated soon. Instead use 'npm run serve'\" && npm run serve",
    "dev": "echo \"\\033[31mWARN: 'dev' will be depreciated soon. Instead use 'npm run serve:dev'\" && npm run serve:dev",
    "serve:dev": "nodemon --watch app --watch bootstrap --watch config --watch .env -x node server.js",
    "serve": "node server.js",
    "lint": "standard"
  },
  "author": "",
  "license": "MIT",
  "description": "",
  "private": true,
  "dependencies": {
    "adonis-ace": "^3.0.7",
    "adonis-ally": "^1.1.2",
    "adonis-auth": "^1.0.5",
    "adonis-commands": "^2.1.5",
    "adonis-fold": "^3.0.3",
    "adonis-framework": "^3.0.10",
    "adonis-lucid": "^3.0.14",
    "adonis-middleware": "^1.0.11",
    "adonis-validation-provider": "^3.0.5",
    "adonis-websocket": "^1.0.3",
    "pg": "^7.3.0",
    "youch": "^2.0.4"
  },
  "standard": {
    "global": [
      "use",
      "make"
    ]
  },
  "autoload": {
    "App": "./app"
  },
  "devDependencies": {
    "nodemon": "^1.11.0",
    "standard": "^10.0.1"
  }
}

Or maybe you can't use Adonis Ally as an API-only?

@sebasgarcep Why do you think that Ally cannot be used when building Rest API?

I think the issue https://github.com/adonisjs/adonis-ally/issues/29 can help.
In case build api-only service I have  access_token from client and do not need using the code from redirect url

@thetutlage I haven't found anything in the Adonis Ally docs that would allow me to generate and validate google+ access tokens.

I believe it's here http://dev.adonisjs.com/docs/4.0/social-auth#_basic_example

I'm closing as this issue is similar to adonisjs/adonis-ally#29.

how we can use the ally as an api only ?


How to get payment gateway methods list of merchant account using sumUp apis

Which scope is used to get payment methods ?

payments, payment_instruments


Similar type of events not getting generated when configmap is changed

Describe the bug
Create and apply configmap with wrong values which will show event in cso and then apply the right configmap which won't give any ValidationWarning event as everything is correct but when wrong configmap is applied again it won't give any ValidationWarning event in configmap which is not expected
How to Reproduce?
For this issue, I have used Images in PR1000  ( #1000 ).

Install CSI 2.10.0 with the following Images

[root@saurabh6-master pr1000]# oc get pods
NAME                                                  READY   STATUS    RESTARTS       AGE
ibm-spectrum-scale-csi-79pp5                          3/3     Running   0              2m59s
ibm-spectrum-scale-csi-attacher-b6b6d4948-l8kmw       1/1     Running   2 (3m2s ago)   3m42s
ibm-spectrum-scale-csi-attacher-b6b6d4948-prgwj       1/1     Running   2 (3m2s ago)   3m42s
ibm-spectrum-scale-csi-operator-6877d5465c-szr95      1/1     Running   0              3m46s
ibm-spectrum-scale-csi-provisioner-b456fbb49-xxxkt    1/1     Running   2 (3m1s ago)   3m42s
ibm-spectrum-scale-csi-resizer-84d84bfdf6-8zlm2       1/1     Running   2 (3m1s ago)   3m42s
ibm-spectrum-scale-csi-snapshotter-656d4bd64f-s9zzq   1/1     Running   2 (3m1s ago)   3m42s
ibm-spectrum-scale-csi-vhdmf                          3/3     Running   0              2m59s
[root@saurabh6-master pr1000]# oc get cso
NAME                     VERSION   SUCCESS
ibm-spectrum-scale-csi   2.10.0    True
[root@saurabh6-master pr1000]# oc describe pod | grep quay
    Image:         quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:ee9bd3e431cf0d3fb1e407a6e2ed51d6be957dd1445c2cd88f329cbb5b1ea494
    Image ID:      quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:31172dc13f5cc514cf2474cb440697c1da20d035f3fd12ec761f12b06cc2e0a7
  Normal   Pulled     3m9s  kubelet            Container image "quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:ee9bd3e431cf0d3fb1e407a6e2ed51d6be957dd1445c2cd88f329cbb5b1ea494" already present on machine
    Image:         quay.io/badri_pathak/ibm-spectrum-scale-csi-operator:events_gen_v11
    Image ID:      quay.io/badri_pathak/ibm-spectrum-scale-csi-operator@sha256:cb12d4adec4321bc9f4f6091e698d91b70df3d043e31592b39c3686084a1a836
      CSI_DRIVER_IMAGE:      quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:ee9bd3e431cf0d3fb1e407a6e2ed51d6be957dd1445c2cd88f329cbb5b1ea494
  Normal  Pulled     3m55s  kubelet            Container image "quay.io/badri_pathak/ibm-spectrum-scale-csi-operator:events_gen_v11" already present on machine
    Image:         quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:ee9bd3e431cf0d3fb1e407a6e2ed51d6be957dd1445c2cd88f329cbb5b1ea494
    Image ID:      quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:31172dc13f5cc514cf2474cb440697c1da20d035f3fd12ec761f12b06cc2e0a7
  Normal   Pulled     3m9s  kubelet            Container image "quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:ee9bd3e431cf0d3fb1e407a6e2ed51d6be957dd1445c2cd88f329cbb5b1ea494" already present on machine
[root@saurabh6-master pr1000]#

Apply wrong configmap as shown below

[root@saurabh6-master pr1000]# cat wrong_cm.yaml
kind: ConfigMap
apiVersion: v1
metadata:
  name: ibm-spectrum-scale-csi-config
  namespace: ibm-spectrum-scale-csi-driver
data:
  VAR_DRIVER_LOGLEVEL: debug0s
  VAR_DRIVER_PERSISTENT_LO_G: ENABLED
  VAR_DRIVER_VOLUME_STATS_C_APABILITY: DISABLED
  VAR_DRIVER_NODEPUBLISH_METHOD: symlink
  DRIVER_UPGRADE_MAXUNAVAILABLE: 90%
[root@saurabh6-master pr1000]# oc apply -f wrong_cm.yaml
configmap/ibm-spectrum-scale-csi-config created

Check the cso event

Events:
  Type     Reason             Age                  From              Message
  ----     ------             ----                 ----              -------
  Warning  CreateDirFailed    5m13s (x11 over 8m)  CSIScaleOperator  Failed to create a symlink directory with relative path spectrum-scale-csi-volume-store/.volumes on filesystem fs1
  Warning  ValidationWarning  20s                  CSIScaleOperator  There are few entries [VAR_DRIVER_PERSISTENT_LO_G VAR_DRIVER_VOLUME_STATS_C_APABILITY] with wrong key which will not be processed and few entries having wrong values map[VAR_DRIVER_LOGLEVEL:debug0s] in the configmap ibm-spectrum-scale-csi-config, default values will be used
  Warning  UpdateFailed       16s (x2 over 17s)    CSIScaleOperator  Failed to set defaults on the instance ibm-spectrum-scale-csi. Please check Operator logs
  Normal   CSIConfigured      14s (x12 over 4m3s)  CSIScaleOperator  The CSI driver resources have been created/updated successfully

Above ValidationWarning event is getting generated which is expected

Apply correct configmap

[root@saurabh6-master pr1000]# cat correct_cm.yaml
kind: ConfigMap
apiVersion: v1
metadata:
  name: ibm-spectrum-scale-csi-config
  namespace: ibm-spectrum-scale-csi-driver
data:
  VAR_DRIVER_LOGLEVEL: DEBUG
  VAR_DRIVER_PERSISTENT_LOG: ENABLED
  VAR_DRIVER_VOLUME_STATS_CAPABILITY: DISABLED
  VAR_DRIVER_NODEPUBLISH_METHOD: SYMLINK
  DRIVER_UPGRADE_MAXUNAVAILABLE: 90%
[root@saurabh6-master pr1000]# oc apply -f correct_cm.yaml
configmap/ibm-spectrum-scale-csi-config configured

Check the CSO event (It won't show any new event as everything is right)

Events:
  Type     Reason             Age                     From              Message
  ----     ------             ----                    ----              -------
  Warning  CreateDirFailed    6m41s (x11 over 9m28s)  CSIScaleOperator  Failed to create a symlink directory with relative path spectrum-scale-csi-volume-store/.volumes on filesystem fs1
  Warning  ValidationWarning  108s                    CSIScaleOperator  There are few entries [VAR_DRIVER_PERSISTENT_LO_G VAR_DRIVER_VOLUME_STATS_C_APABILITY] with wrong key which will not be processed and few entries having wrong values map[VAR_DRIVER_LOGLEVEL:debug0s] in the configmap ibm-spectrum-scale-csi-config, default values will be used
  Warning  UpdateFailed       21s                     CSIScaleOperator  Synchronization of node/driver ibm-spectrum-scale-csi DaemonSet failed for the CSISCaleOperator instance ibm-spectrum-scale-csi
  Warning  UpdateFailed       19s (x4 over 105s)      CSIScaleOperator  Failed to set defaults on the instance ibm-spectrum-scale-csi. Please check Operator logs
  Normal   CSIConfigured      15s (x20 over 5m31s)    CSIScaleOperator  The CSI driver resources have been created/updated successfully

As cm was correct no ValidationWarning  event is generated after applying correct cm which is expected

Reapply the wrong configmap and check if cso event is shown or not.

[root@saurabh6-master pr1000]# cat wrong_cm.yaml
kind: ConfigMap
apiVersion: v1
metadata:
  name: ibm-spectrum-scale-csi-config
  namespace: ibm-spectrum-scale-csi-driver
data:
  VAR_DRIVER_LOGLEVEL: debug0s
  VAR_DRIVER_PERSISTENT_LO_G: ENABLED
  VAR_DRIVER_VOLUME_STATS_C_APABILITY: DISABLED
  VAR_DRIVER_NODEPUBLISH_METHOD: symlink
  DRIVER_UPGRADE_MAXUNAVAILABLE: 90%
[root@saurabh6-master pr1000]# oc apply -f wrong_cm.yaml
configmap/ibm-spectrum-scale-csi-config configured

Check the CSO status:

Events:
  Type     Reason             Age                   From              Message
  ----     ------             ----                  ----              -------
  Warning  CreateDirFailed    8m18s (x11 over 11m)  CSIScaleOperator  Failed to create a symlink directory with relative path spectrum-scale-csi-volume-store/.volumes on filesystem fs1
  Warning  ValidationWarning  3m25s                 CSIScaleOperator  There are few entries [VAR_DRIVER_PERSISTENT_LO_G VAR_DRIVER_VOLUME_STATS_C_APABILITY] with wrong key which will not be processed and few entries having wrong values map[VAR_DRIVER_LOGLEVEL:debug0s] in the configmap ibm-spectrum-scale-csi-config, default values will be used
  Warning  UpdateFailed       118s                  CSIScaleOperator  Synchronization of node/driver ibm-spectrum-scale-csi DaemonSet failed for the CSISCaleOperator instance ibm-spectrum-scale-csi
  Warning  UpdateFailed       116s (x4 over 3m22s)  CSIScaleOperator  Failed to set defaults on the instance ibm-spectrum-scale-csi. Please check Operator logs
  Normal   CSIConfigured      112s (x20 over 7m8s)  CSIScaleOperator  The CSI driver resources have been created/updated successfully

No ValidationWarning event is shown for wrong cm. If we check the event last ValidationWarning event was 3m25s old and after applying wrong cm recently it is not showing anything.
Note: This issue is seen when wrong cm is deleted and applied again.
Expected behavior
ValidationWarning Event should be generated if wrong cm is applied and same for other failure cases if that is not working

Another scenario is seen as follows:

Apply cm having wrong key , it will generate cso event
Apply cm having wrong value , it will generate cso event
Now apply cm having wrong key in one parameter and wrong value which has correct key , it won't generate cso event which is not expected

@saurabhwani5 I have validated the events with various scenario along with the above mentioned ones. My observation is that Kubernetes suppress similar events whenever cso tries to adding events too frequently. The events details are visible for certain time-period but can be shown after sometime when new events gets generate. The failure values will gets increase with the hidden counts also.
e.g.   Warning  ValidationWarning  9s (x12 over 4h55m)  CSIScaleOperator  There are few entries having wrong key which will not be processed or few entries having wrong values in the configmap ibm-spectrum-scale-csi-config, check operator logs for details
In the above example, after 7-8 counts the events were not visible but tried after some time, its gets new failure events with totalm failed with x12 which is total failed from initial time.

@amdabhad The same behaviour can be noticed with generic message along with unique message when keep on generating events too frequently. I think there won't be any changes required as of now.

@badri-pathak , please check on 2 things:

This is the event generated repeatedly, see if this can be reduced if it is the last event:

Normal   CSIConfigured      112s (x20 over 7m8s)  CSIScaleOperator  The CSI driver resources have been created/updated successfully

See if there is any official k8s doc mentioning about surpassing frequent events, we may have to document that


Add special case for semver@7

The semver package changed in version 7 to use a dynamic/lazy loading index file.
I first first spotted this breaking change in Package Phobia.
This PR adds a special case to statically analyze the preload.js entry point which is effectively what the index.js entry point used to be prior to version 7.
See the changelog:

Add require('semver/preload') to load the entire module without using lazy getter methods.

Codecov Report

Merging #87 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master     #87      +/-   ##
=========================================
+ Coverage   90.78%   90.8%   +0.01%
=========================================
  Files          12      12
  Lines        1042    1044       +2
=========================================
+ Hits          946     948       +2
  Misses         96      96

Impacted Files
Coverage Δ

src/utils/special-cases.js
95.65% <100%> (+0.12%)
:arrow_up:

Continue to review full report at Codecov.

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


Fix line number widths

Fixes regression https://github.com/go-gitea/gitea/pull/31307#issuecomment-2162554913
Table CSS is weird. A auto value does not work and causes the regression while any pixel value causes another regression in diff where the code lines do not stretch. Partially revert this PR and clean up some related too-deep CSS selectors.

Made min-widths match GH in https://github.com/go-gitea/gitea/pull/31341/commits/a95f5ecc3bd7ee437b7aa7524da1e2663e86cb8f.


cbsodata does not work with python 3.8 and later

cbsodata does not seem to work with python 3.8 or later

Thanks for reporting. I think it is an issue with Python 3.9. I made a new release (1.3.3). Hopefully, this resolves your issues. Please let me know.

Thanks for the update. I am still getting the same error however. When i run it with Python 3.7.9 it works fine, but when i run it with 3.83 or 3.9 it stops without finishing properly.

Strange, because tests don't fail.
Can you paste the output here and provide your OS?
Are you using Pycharm? So many issues with Pycharm (see other issue)

This issue has probably nothing to do with the API itself but numpy.py. I was trying to pull out data over with python3.9 and I got the same error. A sanity check there implying a call to fmod() fails due a slightly recent Windows update release.  I've just temporarily commented the call that involves fmod() to be called and the sanity check succeeds (after all is just a sanity check). This module is working fine on Python3.9.(last version) at least for me!
This issue mustn't foil you when using Python 32-bit.
https://tinyurl.com/y3dm3h86

Thanks @SNR20db, this sounds reasonable. The numpy/Windows issues affect thousands of developers at the moment. Numpy is not a dependency of cbsodata, however it is a dependency of pandas.
The issues with numpy and Windows will be resolved by the end of January I think. For now, there is nothing we can do I think. I'm closing the issue. Feel free to reopen or drop a message here.


Add Ali Spittel book

https://twitter.com/aspittel/status/1173973375259152384?s=21

Moved to Nova


Release 0.4.2 or 0.5.0

This was asked on https://gitter.im/dask/dask by @djhoese mainly to have #192 in an official release.
There has been some other improvements over the past few months, but also the start of some tries to write a ClusterManager concept, which is far from being done by now (sorry for not advancing as much as I'd like on this). Fortunately, this should not impact this module stability, this mainly implies some duplication and potential non synchronization of code between dask-jobqueue and distributed.deploy package.
So, should we make a release? Which tag? I'm inclined to go toward 0.5.0 as there is some major changes on going.

I'd be happy to see a 0.5 release. Are there any issues (bugs or major features) that we want to get in before such a release?

I would have liked to get in a lot of things, but I've pretty much not started anything :grin:. So I would say that we may wait for #223 to be finished, but other features will have to wait.
I don't think we've got major bugs waiting to be fixed.

I hope you were not in a hurry @djhoese, hopefully #223 will be completed soon enough.

No problem. This was mostly needed for some jupyter lab on a slurm cluster testing I was doing. I installed from github master and haven't touched it sense. Thanks.

Hi @djhoese , as #223 is merged, just wondering whether you can help to prepare a release? Thanks.

@lokiyang what can I do?

@LokiYang what can I do?

Sorry I should ask @guillaumeeb for release...
Hi @guillaumeeb , as #223 is merged, do you mind to make a release on current master? Thanks.

Oh yes, I'd forgotten about this, quite busy at the moment. I will try to do it by the end of the week.
I suspect there could be another release not so much time after, as there are some evolution to take into accout in distributed.

version 0.5.0 should be up in pypi, waiting for conda bot to ping me.

Thanks for tagging, @guillaumeeb.  It's great to have all the recent progress in a proper release!

Release done!


extra_metadata takes user input for 2D diags of 3D vars

Title says it all! The only current problem is when 2D and 3D versions of the same variable exist in different files which are read in at the same time.
See #142 for a list of new tests which need to be made. I would need some guidance in doing that, but I'd be happy to implement them.

Codecov Report

Merging #143 into master will decrease coverage by 0.56%.
The diff coverage is 14.28%.

@@            Coverage Diff             @@
##           master     #143      +/-   ##
==========================================
- Coverage   94.01%   93.44%   -0.57%
==========================================
  Files           4        4
  Lines         986      992       +6
  Branches      223      227       +4
==========================================
  Hits          927      927
- Misses         31       35       +4
- Partials       28       30       +2

Impacted Files
Coverage Δ

xmitgcm/mds_store.py
90.76% <14.28%> (-1.28%)
:arrow_down:

Continue to review full report at Codecov.

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

Ok latest commit fixes the issue I mentioned. Now, if 2D diagnostics are recognized then the variable name gets appended with '_2D' within the dataset.

I actually think we could do this without the user input, but it requires an assumption. These lines are the main change
https://github.com/xgcm/xmitgcm/blob/6dd33bdfe9efdb28a9915c09afc97a97833b9402/xmitgcm/mds_store.py#L686-L697
I noticed that now only lines 690 on are needed. They assume that 3 dims are expected, but only find two (or in the case of LLC which has face dim, it's 4 and 3), then collapse. I'm curious what you think - maybe this assumes too much and so should we still force the user to tell xmitgcm that they expect 2D slices since this is missing from the meta information?
Thanks guys!

I think this is great! Should we get started with the new tests?

Thanks @raphaeldussin. I'm curious if you think we still need the user to provide the flag '2d_diag_of_3d_var' even though I've found all the tests pass with just the two if statements (without the two involving extra_metadata):
         #Expect 3 dims, vertical and 2 horizontal
         ndims_expected = 3
         if self.llc:
             # llc geometry adds face dim
             ndims_expected += 1

         if len(dims) == 3 and data.ndim == ndims_expected-1:
             dims = dims[1:]
             vname = '%s_2D' % vname

But like I said I'm worried this would be assuming too much - maybe I'm overthinking things! :P
As for the tests, I have a rookie question... For reference here is what @rabernat originally suggested:

Copy one of the 2D files (like Eta) to a 3D file name (like Theta) and create the appropriate meta file. we should test both built-in state variables and those generated from available_diagnostics.log
Open those files with open_mdsdataset and ensure no errors are raised
Check that the files have the right dimensions.

For step 1, do you want to do this all within a test function? So that each time the tests run, it does the steps of copying Eta, making the meta file, writes it out to be loaded in. Or manually copy Eta etc and load it to wherever you guys keep your test data, so that it gets loaded like the other variables each time? If the latter, I'm curious where to load these meta/data files.  Thanks!

I think it would be useful to discuss the optimal design here in general terms, before working more on the implementation. What do we want to happen?
Here is the scenario. We have a file, let's say Theta.data/meta which, instead of having the expected 3 dimensions, has only 2 dimensions. This can happen if MITgcm diagnostics are configure to output only one k level.
To preserve backwards compatibility, I would like an error to continue to be raised, as it is now.
However, I would like to add an optional flag like allow_2d_diags=True to open_mdsdataset which turns on the extra logic @timothyas provided above. After thinking about it more, I agree that extra_metadata doesn't have to be involved.
I can try to tackle the tests. I'll push some proposed tests to your branch later today.

I just added this test:
https://github.com/xgcm/xmitgcm/blob/2fd7ad7a8f8c1077e314aa7a0ee54f1d9dbe6e37/xmitgcm/test/test_mds_store.py#L199-L234
This is not totally complete, but I think it should help @timothyas move forward.
The strange thing is that it passes just fine already with standard grids but doesn't work with LLC grids. I would prefer consistent behavior either way: either we error when 3D fields are expected or not, regardless of grid type. I guess the presence of the extra LLC face dimension throws a wrench into the logic somewhere.

Thanks @rabernat for getting me started on the tests!

I just added this test:
https://github.com/xgcm/xmitgcm/blob/2fd7ad7a8f8c1077e314aa7a0ee54f1d9dbe6e37/xmitgcm/test/test_mds_store.py#L199-L234
This is not totally complete, but I think it should help @timothyas move forward.
The strange thing is that it passes just fine already with standard grids but doesn't work with LLC grids. I would prefer consistent behavior either way: either we error when 3D fields are expected or not, regardless of grid type. I guess the presence of the extra LLC face dimension throws a wrench into the logic somewhere.

I think I found why it fails for llc but not others. This snippet lived just a few lines above our little hack in load_from_prefix:
https://github.com/xgcm/xmitgcm/blob/2fd7ad7a8f8c1077e314aa7a0ee54f1d9dbe6e37/xmitgcm/mds_store.py#L670-L679
I think this was to catch output from e.g. barotropic simulations, where we actually have 2 dims, even for grid variables like hFac. I have made a number of changes, I went ahead and implemented what I mentioned earlier: added a keyword allow_2d_diags. I then removed the above lines, but then had to add the allow_2d_diags to the expected dictionaries in the test suite. This should allow us to say "yes we expect 2D diags for the barotropic experiment, but no others".
However I'm also getting a KeyError: with variable 'T' in get_virtual_variable that I don't quite understand. My hunch is that this has to do with the new test, something to do with the renaming and copying of Eta, but I'm at a loss for that one.

PS perhaps that was assuming of me to just go ahead and implement what I suggested, but I got addicted to solving this. Happy to revert changes if everyone disagrees.

@timothyas - thanks a lot for working on this!
It's not an option to suddenly require a new keyword argument allow_2d_diags=True for barotropic simulations that previously worked fine. This would be considered a "breaking change," because it would cause xmitgcm code that previously worked to suddenly stop working if a user upgrades xmitgcm. Imagine the frustration that would cause for you as a user! These sorts of changes must be avoided at all costs. Instead, we should make whatever changes we make here backwards compatible. If we really need to introduce breaking changes, we need to do so very slowly, over many release cycles, starting first with deprecation warnings. I don't think that is necessary here.
I would back up a little bit and rethink the implementation here.
The default behavior (allow_2d_diags=False) should just leave things as they were before. allow_2d_diags=True should turn on a new code path that overcomes the specific problem raised in #140.

My hunch is that this has to do with the new test, something to do with the renaming and copying of Eta, but I'm at a loss for that one.

Hmm, there could be a problem with my test then. Unfortunately I will not have time to work on this today.
@ifenty - where do we stand on the ECCO summer school. Is there a specific date by which you need this fixed? Have we already missed it? What happens if we fail to implement this new feature by the target date? What work-arounds might exist?

Hey @rabernat, thanks for this thorough explanation. This totally makes sense - of course we don't want to break old code! And it makes sense that you would want these tests to break in order to catch breaking changes like this. I'm learning ... slowly... :)
So I'm now thinking about what was already in the function
https://github.com/xgcm/xmitgcm/blob/2fd7ad7a8f8c1077e314aa7a0ee54f1d9dbe6e37/xmitgcm/mds_store.py#L670-L679
and it seems like the default behavior is the equivalent of allow_2d_diags=True, but now we're just also trying to catch the LLC case.
I also don't have a ton of time to work on this right now since I have to prepare some other materials for the school. I'm curious what @ifenty thinks, but I would like to propose the following temporary solution. The students will be using a central distribution of xmitgcm, which is in a community directory on the super computer cloned from git. We could just clone a branch (e.g. from my fork) which has this fix for LLC geometries and roll with that.

@timothyas
if that's the best we can do before Monday then we'll give the students your xmitgcm branch.

We can easily release a new xmitgcm version over the week.
But I still don't understand...what is the actual fix? Do we know what it is, or it still has to be solved.
I have a hunch it is just a few lines of code.

@timothyas - I made an alternate fix for this in #145.
I really appreciate the effort you put into this. It was definitely not for nothing, as you have learned probably more than you ever wanted to know about the guts of xmitgcm. I think you were on track to reaching the same solution. But you mentioned being pressed for time, so I went ahead with my own solution.

Thanks @rabernat! Yeah I was thinking the same thing, but you wrote it much cleaner, and fixed the rest which I wasn’t sure on. I’m happy enough with the knowledge gained.


emoji picker works

reafactor data caching
add the desktop bookmark bar for jumping to different sections
make custom emojis work with filtering
other fixes and tweaks

This just throws a JS error for me, I'll fix.

Problem is that if a custom emoji is in the frequent list

this will work eventually right

Going to merge this since it allows me to use the picker again for customs (master is broken for me). But @songgao, there needs to be code in here to make it so the frequent section can pick up customs.


Front end bugs

Given an example query there are a few small pagination-related bugs.

Greyed out buttons are still clickable
Clicking Prev can produce a server error
Setting a limit > 100 only displays 100 records per page

The pagination at the bottom is calculated based on the actual limit, not 100.  If we decide 100 should be the cap for html, we need to update pagination accordingly.

I'll do this.

Thanks!


Release on jcenter

Hi, did you request jcenter sync for the bintray repository?
Or did you forget to update the README and it's already there?
Having the library on jcenter ensures consumer projects that the artifact can't be removed.

I now tried to merge the two packages and I'll request to add it to jcenter. Thanks for the reminder!

@jonasbark I had an issue with jcenter some time in the past, and despite me not being a paying customer of bintray, they fixed the issue. It took a few days, but they got a solution after clarification.

@jonasbark You mean they both have the same group now but are only different artifacts of the same group?

I contacted them via https://jfrog.com/contact-us/ and all I got was Can you kindly share which product of JFrog do you use and the level of subscription that you own? and they never replied again after stating that I'm not a paying customer.
But anyways, the request to add the correct (merged) package was just approved and it's now available on jcenter. I'll adjust the Readme!

The maven coordinates didn't change, but all the artifacts are correctly on jcenter?

Yes


Fix error logging from convert

Currently, nothing is reported when using the convert function directly from python, only when using the cli.
This fixes it

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 43.708%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4738

Relevant Lines:
10840

💛  - Coveralls

This works to produce the logging output, however, if you run the conversion for the nth time, all outputs are repeated n times now:
1st run:
Using mpes reader to convert the given files:
• ../specsscan/config/NXmpes_arpes_config.json
The data entry corresponding to /ENTRY[entry]/geometries/arpes_geometry/TRANSFORMATIONS[transformations] is required and hasn't been supplied by the reader.
The data entry corresponding to /ENTRY[entry]/SAMPLE[sample]/transformations/sample_polar is required and hasn't been supplied by the reader.
The data entry corresponding to /ENTRY[entry]/SAMPLE[sample]/transformations/sample_polar/@transformation_type is required and hasn't been supplied by the reader.
The data entry corresponding to /ENTRY[entry]/SAMPLE[sample]/transformations/sample_polar/@vector is required and hasn't been supplied by the reader.
The data entry corresponding to /ENTRY[entry]/SAMPLE[sample]/transformations/sample_polar/@depends_on is required and hasn't been supplied by the reader.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@depends_on, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@units, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@transformation_type, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@vector, is being written but has no documentation.
The output file generated: FS_map_CsV3Sb5.nxs.

2nd run:
Using mpes reader to convert the given files:
• ../specsscan/config/NXmpes_arpes_config.json
Using mpes reader to convert the given files:
• ../specsscan/config/NXmpes_arpes_config.json
The data entry corresponding to /ENTRY[entry]/geometries/arpes_geometry/TRANSFORMATIONS[transformations] is required and hasn't been supplied by the reader.
The data entry corresponding to /ENTRY[entry]/SAMPLE[sample]/transformations/sample_polar is required and hasn't been supplied by the reader.
The data entry corresponding to /ENTRY[entry]/SAMPLE[sample]/transformations/sample_polar/@transformation_type is required and hasn't been supplied by the reader.
The data entry corresponding to /ENTRY[entry]/SAMPLE[sample]/transformations/sample_polar/@vector is required and hasn't been supplied by the reader.
The data entry corresponding to /ENTRY[entry]/SAMPLE[sample]/transformations/sample_polar/@depends_on is required and hasn't been supplied by the reader.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@depends_on, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@depends_on, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@units, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@units, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@transformation_type, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@transformation_type, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@vector, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@vector, is being written but has no documentation.
The output file generated: FS_map_CsV3Sb5.nxs.
The output file generated: FS_map_CsV3Sb5.nxs.

etc.

This works to produce the logging output, however, if you run the conversion for the nth time, all outputs are repeated n times now: 1st run:
Using mpes reader to convert the given files:
• ../specsscan/config/NXmpes_arpes_config.json
The data entry corresponding to /ENTRY[entry]/geometries/arpes_geometry/TRANSFORMATIONS[transformations] is required and hasn't been supplied by the reader.
The data entry corresponding to /ENTRY[entry]/SAMPLE[sample]/transformations/sample_polar is required and hasn't been supplied by the reader.
The data entry corresponding to /ENTRY[entry]/SAMPLE[sample]/transformations/sample_polar/@transformation_type is required and hasn't been supplied by the reader.
The data entry corresponding to /ENTRY[entry]/SAMPLE[sample]/transformations/sample_polar/@vector is required and hasn't been supplied by the reader.
The data entry corresponding to /ENTRY[entry]/SAMPLE[sample]/transformations/sample_polar/@depends_on is required and hasn't been supplied by the reader.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@depends_on, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@units, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@transformation_type, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@vector, is being written but has no documentation.
The output file generated: FS_map_CsV3Sb5.nxs.

2nd run:
Using mpes reader to convert the given files:
• ../specsscan/config/NXmpes_arpes_config.json
Using mpes reader to convert the given files:
• ../specsscan/config/NXmpes_arpes_config.json
The data entry corresponding to /ENTRY[entry]/geometries/arpes_geometry/TRANSFORMATIONS[transformations] is required and hasn't been supplied by the reader.
The data entry corresponding to /ENTRY[entry]/SAMPLE[sample]/transformations/sample_polar is required and hasn't been supplied by the reader.
The data entry corresponding to /ENTRY[entry]/SAMPLE[sample]/transformations/sample_polar/@transformation_type is required and hasn't been supplied by the reader.
The data entry corresponding to /ENTRY[entry]/SAMPLE[sample]/transformations/sample_polar/@vector is required and hasn't been supplied by the reader.
The data entry corresponding to /ENTRY[entry]/SAMPLE[sample]/transformations/sample_polar/@depends_on is required and hasn't been supplied by the reader.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@depends_on, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@depends_on, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@units, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@units, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@transformation_type, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@transformation_type, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@vector, is being written but has no documentation.
NO DOCUMENTATION: The path, /ENTRY[entry]/SAMPLE[sample]/transformations/sample_pola/@vector, is being written but has no documentation.
The output file generated: FS_map_CsV3Sb5.nxs.
The output file generated: FS_map_CsV3Sb5.nxs.

etc.

Can you share the code you're using to run this? It will be easier to debug. Somehow there is a chance we are creating a new logger on every call. I can easily reproduce with your call to convert code. Then I'll debug it.

Yes, the problem is that I copied it into the convert function, so it sets the stream handler for every function call 🙈. I think we just need to do it at the top of the file

This works to produce the logging output, however, if you run the conversion for the nth time, all outputs are repeated n times now: 1st run:

Can you share the code you're using to run this? It will be easier to debug. Somehow there is a chance we are creating a new logger on every call. I can easily reproduce with your call to convert code. Then I'll debug it.

That is unfortunaltey a bit difficult, because the code is wrapped in some class in a private repository. Essentially, at the end it calls:
    convert(
        input_file=input_files,
        objects=(data),
        reader=reader,
        nxdl=definition,
        output=faddr,
        **kwds,
    )

I moved it to the top-level in the file. It should now work and only emit it once even for multiple runs. Can you check @rettigl?

This seems to work now.


Design updates for landing page

Updates the landing page CSS and footer to match with https://docs.ripple.com.

The link checker fails due to some broken links in the AMM docs I think, so can probably ignore those (guess they will be fixed in a separate PR at some point).

Looks great - thanks for taking care of this, @maria-robobug!


added about us page info

Pull Request Checklist

[x] I have added screenshots and videos to show before and after the working of my code.
[x] I have ensured that the screen size is set to 100% while making the video.
[x] I have synced the latest fork with my local repository and resolved any conflicts.
[x] I have mentioned the issue number which I created before making this PR .(format to mention issue number is : fixes #(issue number) )
[x] I understand that if any the above conditions are not met , my PR will not be MERGED .

Kindly follow pr checklist

 before

after
fixed issue #839

Hi I have added screenshots in the comments, kindly check if correct

From: Hiteash Mahajan @.>
Sent: Saturday, October 12, 2024 11:09 AM
To: ANSHIKA-26/WordWise @.>
Cc: Aditi Prabakaran @.>; Author @.>
Subject: Re: [ANSHIKA-26/WordWise] added about us page info (PR #839)
Kindly follow pr checklist
—
Reply to this email directly, view it on GitHubhttps://github.com/ANSHIKA-26/WordWise/pull/839#issuecomment-2408524935, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BC5W2473MP75Z3SZHON7EMLZ3D7PLAVCNFSM6AAAAABP2JTHWWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBYGUZDIOJTGU.
You are receiving this because you authored the thread.Message ID: @.***>

Mention issue number

Issue #674

From: Hiteash Mahajan @.>
Sent: Saturday, October 12, 2024 3:51 PM
To: ANSHIKA-26/WordWise @.>
Cc: Aditi Prabakaran @.>; State change @.>
Subject: Re: [ANSHIKA-26/WordWise] added about us page info (PR #839)
Mention issue number
—
Reply to this email directly, view it on GitHubhttps://github.com/ANSHIKA-26/WordWise/pull/839#issuecomment-2408607670, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BC5W242XTHG3UFDR4JFAACTZ3FAPTAVCNFSM6AAAAABP2JTHWWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBYGYYDONRXGA.
You are receiving this because you modified the open/close state.Message ID: @.***>


Vagrant check always fails on windows

Recently, the check to see if vagrant and virtualbox exist has been changed to the built-in LookPath function: https://github.com/nanobox-io/nanobox/blob/master/util/vagrant/vagrant.go#L28
This doesn't work on windows. Looking through the source code of the LookPath implementation for windows, I can't see why this would fail: https://golang.org/src/os/exec/lp_windows.go

LookPath works fine on windows to find vagrant, so it's somewhere else in the code. I'm not proficient in Go, but a quick check using
package main

import (
	"fmt"
	"os/exec"

)

func main() {
	var err error
	var path string
	if path, err = exec.LookPath("vagrant"); err == nil {
		fmt.Printf("Vagrant found at %s\n", path)
	}else{
		fmt.Printf("Vagrant not found")
	}

}

Output:
Vagrant found at C:\HashiCorp\Vagrant\bin\vagrant.exe
> Elapsed: 1.707s
> Result: Success

So I would assume it's a clause somewhere else that is making this fail.

@Flat Thanks for looking into this!
A new windows installer the the most up-to-date version of nanobox will be up shortly. I'll give that a try and see if perhaps this isn't an issue anymore.
Thanks again!

Confirmed. This issue is resolved in the latest release of nanobox.


Use of unsafe yaml load. Allows instantiation of arbitrary objects. Consider yaml.safe_load().

with open(config_file, "r") as config_file:
cfg = yaml.load(config_file, Loader=yaml.FullLoader)
Why is this an issue?
B506: Test for use of yaml load¶
This plugin test checks for the unsafe usage of the yaml.load function from the PyYAML package. The yaml.load function provides the ability to construct an arbitrary Python object, which may be dangerous if you receive a YAML document from an untrusted source. The function yaml.safe_load limits this ability to simple Python objects like integers or lists.
Please see http://pyyaml.org/wiki/PyYAMLDocumentation#LoadingYAML for more information on yaml.load and yaml.safe_load

Duplicate


Investigate why finding 12267 on our system is marked as changed...

7608 too...

Not relevant anymore.


Timepicker css is having issue in bootstrap modal

Hi, i have used you plugin in my application. it really appreciate your efforts. But i am not getting an issue. the issue is its z-index, it displays below the modal as i am using it in bootstrap modal.
Can you tell me how i can update its z-index please.??

after i increases the z-index, it starts displaying.

You can refer to #1 to fix this problem. Just add another style to make timepicker z-index on top of the page. But I think its important to add z-index option.


[ADDED]: Added Binary String Weight Calculator.

Issue Id you have worked upon -
#480
Briefly explain your program logic -
The program logic is simple i.e we just have to return the number of ones in it .
Screenshots(Attach 2 screenshots of your own input and output) -

By raising this PR I affirm that -

[x] My code follows the guidelines of this project.

[x] I have performed a self-review of my own code.

[x] I have commented my code.

[x] My code gives the correct output.

[x] I affirm that I strictly follow contributing guidelines and code of conduct.

Congratulations 🎉 @Ayush-Vish on your contribution.
Thanks for adding value to this repository. 😊
Let's celebrate this fest 😃 by providing more developers 👨💻👩💻 an opportunity to contribute. Help us make this repository reach far and more by sharing this to your friends and colleagues.
Your efforts can make difference.

Hey 👋, may you also encourage us by clicking the star icon on the repository main page. ⭐


Pre-requisite clarification and Message addition

Based on some research,  it is important to use the correct user when it comes to the Active Directory User who is a member of the "Domain Admins" group for a domain and a member "Enterprise Admins" group for a forest.
A message prompt with appropriate description of the credential being prompted enhances the success rate by eliminating ambiguity.

@rmuralidhar : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

#sign-off

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.


The NPM script 'start' exited without indicating that the Angular CLI

https://stackoverflow.com/questions/52724294/how-to-solve-the-npm-script-start-exited-without-indicating-that-the-angular-c
i posted here today .. but no one reply my error.. please check
https://stackoverflow.com/questions/52714606/an-unhandled-exception-occurred-while-processing-the-request-in-netcore
i am facing these error on my different machine.... i spend 9 hours in this issue but still pending both of these

I would recommend checking our docs on trouble shooting IIS: https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/troubleshoot?view=aspnetcore-2.1.
From one of the stack overflow posts, it seems like there may have been a permission issue with a folder. Seems like you resolved it.
Closing the issue for now, if you have additional concerns, feel free to re-open.


[Enhancement] Support iceberg metadata two level cache

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[x] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[ ] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

run starrocks_fe_unittest

Please add some description in the problem summary

run starrocks_admit_test

run starrocks_fe_unittest

run starrocks_admit_test

run starrocks_fe_unittest

[FE PR Coverage Check]
:disappointed: fail : 43 / 165 (26.06%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/connector/iceberg/io/IOUtil.java
0
22
00.00%
[86, 90, 91, 99, 100, 104, 105, 106, 107, 110, 111, 112, 114, 115, 120, 121, 122, 123, 127, 128, 129, 130]

:large_blue_circle:
com/starrocks/connector/iceberg/io/IcebergCachingFileIO.java
38
138
27.54%
[109, 146, 180, 184, 203, 214, 215, 229, 230, 240, 247, 249, 250, 251, 252, 253, 254, 258, 260, 262, 264, 265, 266, 267, 268, 269, 270, 271, 272, 273, 275, 277, 278, 280, 281, 282, 283, 284, 285, 286, 287, 289, 290, 292, 293, 295, 296, 298, 299, 300, 301, 302, 303, 305, 309, 310, 311, 314, 315, 316, 317, 318, 320, 321, 322, 323, 324, 325, 326, 328, 329, 330, 331, 336, 341, 342, 343, 345, 346, 347, 349, 355, 356, 361, 362, 363, 367, 368, 373, 374, 376, 420, 429, 430, 431, 432, 434, 435, 437, 453]

:large_blue_circle:
com/starrocks/common/Config.java
5
5
100.00%
[]

run starrocks_admit_test


add OWNERS for new area labels

goes along with https://github.com/openshift/release/pull/38274

/area hypershift-operator

/lgtm


efivar: fix Could not parse device path: Invalid Argument

Motivation for this change
Running efibootmgr -v is broken on unstable as efibootmgr returns Could not parse device path: Invalid Argument.
Upstream issue: https://github.com/rhboot/efibootmgr/issues/133
Fixed by 2 additional patches to efivar.
Things done

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

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

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

@GrahamcOfBorg build efibootmgr


Updated instructions for gettext on Windows.

@ramiro, any input on this? The current linked page doesn't have the latest versions of gettext and the new page is what https://www.gnu.org/software/gettext/ points to. It seems to work for me, thought I still run into https://code.djangoproject.com/ticket/25677#comment:10 when running the Django tests on master.

merged in 1d86d4c72b322498819fb8a17a577300152dc6d4.


How to hold a response? And are there something called "maxHeldResponseCount"?

I want to implement a long-polling model in my server (express.app).
I use a map to stored incoming response, waiting (about 60 seconds later) another request to finally send stored response back.
I find the store action will block other incoming request. I mean, the callback of app.post("xxx"...) is not called until I close some of stored responses in step 2.

So, I wonder:

Is it a right method for me to store response from app.post to implement long-polling?
Does express.js itself set max concurrent count of held responses?

Hi @HaloWang there should not be any issue holding on to the objects like thay. As for why your other requests are being blocked, I'm not sure. Express itself does not have any limitation on the number of max concurrent requests. We may need you to provide code and instructions to reproduce the issue so we can help debug.


What happened to .visual-bell ?

I was using .visual-bell and its various states in the previous version of this design system and now it doesn't seem to be present? Is it called something else? Removed?

Hey Craig, I can look at reinstating it. The main reason why I included
this was there was no way to push a message via a native notification when
I first created this. When Figma added it, it seemed beneficial to most to
be able to just use the figma.notify() function.
Does your use case prevent you from being able to use that function?
Cheers!
On Fri, Aug 28, 2020 at 7:52 AM Craig Dennis<EMAIL_ADDRESS>wrote:

I was using .visual-bell and its various states in the previous version
of this design system and now it doesn't seem to be present? Is it called
something else? Removed?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/thomas-lowry/figma-plugin-ds/issues/35, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AJFS3VOQ6OMIPCA2BN7JZHDSC6K7JANCNFSM4QOBPJTA
.

--
Tom Lowry
416 795 2082
<EMAIL_ADDRESS>

I was using the spinner in combination while inserting image data.
I was using the 'error' style to display errors while fetching from an API or inserting images.
I can only find docs for a simple String notification and nothing about persisting, clearing, or setting a type like 'error' on the native notice UI.
These are all things I can recreate but it was nice to have a style that mimicked the native notice UI to make the plugin feel more integrated.

I've just found https://www.figma.com/plugin-docs/api/properties/figma-notify/ which allows me to cancel a notice and specify the duration before timeout. Which is handy.


installation instructions in README.md are out of date

What happened?

The posted installation instructions don't work.
I used https://marketplace.upbound.io/providers/crossplane-contrib/provider-kubernetes/v0.13.0 instead.
How can we reproduce it?

What environment did it happen in?
Crossplane version: 1.15.2
Kubernetes: 1.24
Distribution: RKE2

Ah good point @charlesmelby, thanks for taking the time to call that out! This looks very similar to a recent update we made to provider-helm to fix a very similarly outdated README.md 😊
https://github.com/crossplane-contrib/provider-helm/pull/220
Do you have any interest in taking that out for this repo too? Always happy for community contributions. The local development steps are more tricky, so a phased approach could be to just start by updating the basic install step(s) in the README.

@jbw976 Sure why not, I'll do that in a bit when I'm free

The most critical part of these README installatino instructions has been updated by @scubbo in #239. There is still some more work to update the rest of the readme, e.g. the local development instructions and streamlined set up of in-cluster config (similar to https://github.com/crossplane-contrib/provider-helm/pull/220), but the main problem has been addressed now! 🙇