text:
Script defaults

In async-profiler I've found that you use ${{GIT_REPO:/tmp/async-profiler}} multiple times. You also declare used variables in a comment - that leads me to a suggestion that the script could be written as:
name: async-profiler
defaults:
  GIT_REPO: /tmp/async-profiler
required:
- ROOT_PASSWORD
- ...
scripts: ...

and qDup would make sure that the required variables are set and non-empty and optionally set defaults on the non-mandatory ones.

I think it is a good idea to stop repetition in scripts.
State variables can currently be defined with a default value and overridden at runtime.
e.g.
states:
  BUILD_PROJECT: false

I think the important change here is to be able to define if the variable is required or not and thrown an exception if the state variable has not been defined either in the script or at runtime.
Perhaps we could have an extra field available when defining a state variable that determines if the variable is required and deprecate the default state values that can currently be defined at the point in the script that a state variable is resolved?
e.g.
states:
  BUILD_PROJECT:
    - value: false
    - required: true
  BUILD_PROJECT_EMPTY:
    - value:
    - required: true

The second definition would cause an exception if BUILD_PROJECT_EMPTY was not passed a value at runtime
@willr3 wdyt?

You don't need to put value/`required into a list.
I agree that while it might be more verbose (repetition of value and required) it's probably better to have single mapping for variables than two mappings (defaults and required as I suggested above). Note that setting value for required state does not make much sense, so you can contract that to
states:
  VAR_WITH_DEFAULT: some-default
  ANOTHER_VAR:
    default: foobar # Just an alternative way to set default
  REQUIRED_VAR:
    required: true # or maybe optional: false?

@johnaohara Btw. yesterday we've discussed with Will that in order to have the states configurable either from bash script (e.g. in CLI) or from qDup script it would be nice to ignore -S FOO=${FOO} when ${FOO} is empty, instead of overriding value in script with an empty value. We could intentionally unset FOO using -S !FOO (though I doubt that will be required much in practice).

states:
  VAR_WITH_DEFAULT: some-default
  ANOTHER_VAR:
    default: foobar # Just an alternative way to set default
  REQUIRED_VAR:
    required: true # or maybe optional: false?

This example is similar to how steps can have multiple key/value mappings with some keys having default values and I think makes the most sense.
If we default optional to false, this would retain the current behaviour

@johnaohara Btw. yesterday we've discussed with Will that in order to have the states configurable either from bash script (e.g. in CLI) or from qDup script it would be nice to ignore -S FOO=${FOO} when ${FOO} is empty, instead of overriding value in script with an empty value. We could intentionally unset FOO using -S !FOO (though I doubt that will be required much in practice).

+1

I created #61 for the change to -S so that we don't override values with an empty string.
We could replace all the ${{GIT_REPO:/tmp/async-profiler}} with a set-state at the start of the script
scripts:
  foo:
  - set-state: repo ${{GIT_REPO:/tmp/async-profiler}}
  - sh: echo ${{repo}} #do stuff with repo instead of GIT_REPO

I probably put too much weight on the copy paste crutch when creating the initial scripts :)
After eb1054e59f3c05effecac38eddb085a863bd14be the run should abort if ${{FOO}} fails to resolve to a state value so we have to use ${{FOO:}} if the script supports an empty value. Please let me know if that isn't happening somewhere :)
- set-state: script_foo ${{FOO:}} #optional value
- set-state: script_bar ${{BAR}} #required value, aborts run if missing

I think runs aborting due to missing state should already provide the desired check on required state so we don't need to add reserved words to the state json. Aborting has the added benefit of catching runtime issues that cannot be detected at compile time. For example set-state: ${{FOO}} ${{BAR}} where FOO or BAR come from a regex could not be detected at compile time.
Is there something we don't get from the current master implementation that we would get from adding default with required or optional?

One note: right now states are declared on a file level, and I am not sure if these are set for the non-main files. I did not properly realize that above.
set-state does the job, though the imperative approach does not stick out in the script structure as declarative one. There's also duplication of the variable name when you write
scripts:
  foo:
  - set-state: FOO ${{FOO:my-default}}
  - sh: ...

and some curly braces that your eyes need to parse. IMO despite a bit more verbosity it's easier to read
scripts:
  foo:
    states:
      FOO:
        default: my-default
    commands:
    - sh: ...

It's true that simple FOO: my-default looks more like overriding that variable than just supplying the default if not set.
About the required vars: I agree with the abort; the thing is to abort as soon as possible. With declarative required variable it would fail before the first command from the script gets executed. Yes, you could have the same check doing just
- sh: echo ${{FOO}} > /dev/null

but again, it's about readability.

I think the benefit of adding required / optional allows for a fail fast path for validating state variables required for a run at startup.

We could replace all the ${{GIT_REPO:/tmp/async-profiler}} with a set-state at the start of the script

If we have multiple scripts running on multiple hosts, there is no guarantee of script ordering. We would need to add a set-state command to the start of every script that used that state variable to check if it was empty if we want to fail fast. Or add the the setup script, but not all qDup files will contain setup scripts.

I think runs aborting due to missing state should already provide the desired check on required state so we don't need to add reserved words to the state json.

I think this is a side effect of set-state and is not explicit behaviour of qDup, I think it would be more difficult for users to find/remember this behaviour compared to a declarative property on a state variable that could be easily documented.

Aborting has the added benefit of catching runtime issues that cannot be detected at compile time. For example set-state: ${{FOO}} ${{BAR}} where FOO or BAR come from a regex could not be detected at compile time.

I agree that in the case of assigning dynamic state based on the result of a cmd, the onus should be on the user to verify that the  state variable contains valid data or abort.

Is there something we don't get from the current master implementation that we would get from adding default with required or optional?

I think we would get a succinct, more robust, fail fast error checking for variables that need to be set for a script

Sorry if I am being dense but what are the goals for this feature change? I'm reluctant to add reserved words but if that proves to be the best way to achieve the goals then we can certainly add them.
If our goal is to mark variables as optional or required then I think we already have that in the syntax.
foo:
- sh: echo ${{OPTIONAL:defaultValue}} #will not fail because a default is provided
- sh: echo ${{REQUIRED}} #will fail because a default is not provided

There is a complaint we have about ${{OPTIONAL:defaultValue}} and having to write the defaultValue each time. I don't think that is necessary, it was just how I wrote the scripts originally. We can either set-state: OPTIONAL ${{OPTIONAL:defaultValue}} or the script can add OPTIONAL: defaultValue to states and rely on the failure if it gets removed from states. A utility yaml can also have a states section which are overridden by the first yaml file in the list of yaml files to qDup.jar. I used the ${{OPTIONAL:defaultValue}}
If our goal is to fail at build time rather than runtime when a required variable is not defined then I would like to take a try at adding that to the static analysis that runs during build time. Right now qDup does the following static analysis:

Calculate expected signal counts for all signals
Ensure there are no remote shell commands in an observable context. (make sure sh isn't called in watch or on-signal or timeout)
Check for script loops
We could check for ${{FOO}} where FOO is not in states and not in set-state: FOO .... This would not deal with set-state: ${{BIZ}} ...' where BIZ=FOObut I suspect that will be uncommon and we either add a flag to disable the static check when we know it fails incorrectly (e.g.--disable statescan) or a flag to ignore specific variable names (e.g. --state-ignore FOO`)

Let me know what you guys think and I might start hacking at the static analysis because that part of the code could use a few minutes of review.

The goal is improved readability and structure, opinionated places to declare input variables for each script. As you've said, the goal can be achieved with set-state/echo.
Static analysis is definitely something extra, out of scope of this issue, and would work even with the imperative syntax.
If you prefer minimal complexity over readability, so be it.

I re-read the thread and I think I missed the initial issue. Did you proposed adding defaults and required as a way to declare the variables for a script? The scripts section right now only uses the key to define the script and then the value is expected to be a sequence of commands in the script. I don't think the current yaml structure would make it possible to provide per-script information about variables. We could use the states section to declare the default values for all variables in the file. The states get loaded based on the yaml file order so the first file would define the current value of states and subsequent files could define the default values.
Another option is to introduce a more verbose way to write the yaml for the scripts section.
scripts:
  - name: async-profiler
  - variables:
    - GIT_REPO: /tmp/async-profiler #provides a default
    - PASSWORD: #no default so user must provide a value

I think I like the idea both of slim and verbose way to write the scripts. Adding variables moves the existing comments into the yaml syntax which makes it easier to read and lets us include the default in the syntax but I doubt it will be more accurate. We will need to scan the script to make sure variables is correct.

Yes, I was thinking about scripts (conceptually thinking about these as functions with parameters), though some symmetry between scripts and the global vars would be welcome.
Your example mixes lists and mappings, what you wanted is
scripts:
- name: async-profiler
  variables:
    GIT_REPO: /tmp/async-profiler #provides a default
    PASSWORD: #no default so user must provide a value
  commands:
  - sh: ...

Name, variable and commands belong to single item, so these all are single mapping in the list of scripts. Also, variable mapping uses unique keys (variable names) so there's no need to put them in as a list.
One downside of the verbose way is that while the name (async-profiler) is unique it is not used as unique key for the scripts; if you did so you'd have to add one more level of indentation:
scripts:
  async-profiler:
    variables:
      GIT_REPO: /tmp/async-profiler #provides a default
      PASSWORD: #no default so user must provide a value
    commands:
    - sh: ...

About the order of loading: to me it seems a bit confusing that you can have multiple files with host definitions etc. but actually only the first is used. I'd prefer the other files to be library-only (so these could contain only scripts - ok, maybe some global vars as well).

Any updates?

The static analysis part is added to qDup.
scripts:
  test:
  - sh: echo "${{does_not_exist}}"

Will not start a run if does_not_exist is not defined
Error: does_not_exist is used before it appears to be set
  role: doit stage: setup script: test
  command: sh: echo "${{does_not_exist}}"

We don't yet have an updated yaml parser that accepts variables and associates a default value. We also need to ensure the default value gets replaced with any other value in state be it in a with, set-state, states, or -S in the command line.

I guess that you're not going to introduce any new syntax for this; superseded by https://github.com/Hyperfoil/qDup/issues/160

authors: johnaohara rvansa willr3

repo: Hyperfoil/qDup


text:
Dev - added reward address getter and signData() method.

Added a getter to return the current array of reward addresses as an array of StackAddress objects.  Also, added a signData() method so the user can sign messages with their wallet.  The signData() method accepts the message as a string and internally converts it to the hex string required by the wallet's signData() method before calling that method.

@christianschmitz Sure.  Would you mind telling which branch (and tag if any) so I don't make the same mistake?  Also, any other changes necessary beyond just pulling from the latest code version?

The latest tag is v0.16.15

@christianschmitz Thanks, main or dev branch?

always main branch please

Creating new PR based on main instead of dev, so closing this one.

source: gharchive/pull-request

authors: christianschmitz roschler

repo: Hyperion-BT/helios

license_type: permissive

license_source: github-api


text:
JupyterHub frequently goes down due to NSF server issues

The hub pod for JupyterHub seems to die when it is unable to mount the hub-db-dir volume from the NFS server.
The NFS server VM seems to frequently go down without warning and takes a long time to restart.
Hub is functional again when the NFS server is back up and the NFS service is restarted.
Debug the cause of the node going down and whether we need to migrate to a larger/new VM on Jetstream2

Ticket submitted to Jetstream2 team. They are taking a look at the VM logs now.

Issue was due to one of the network interfaces going down on the server behind this VM. Jetstream has routed all traffic to the working interface and will look into fixing the other one.

source: gharchive/issue


text:
能否在readme中补充一下评估结果的复现指令？

没太看懂到底哪个是测试文件入口。好多文件里的json文件也没有附带在仓库里，麻烦作者能补充一下吗？

好的，非常感谢您对本工作的关注，了解到您遇到的困难了。本工作涉及到多个benchmark和数据集，由于文件较大没有上传，我们本周更新一版readme文档，将说明如何下载数据、配置程序以便进行分块和评估。另外，我们将提供一个各类方法针对不同数据集的分块结果的网盘链接，便于您的使用。

感谢作者的回复，使我的issue旋转。
期待后续更新。

repo: IAAR-Shanghai/Meta-Chunking


text:
[CLOSED] Weather Insights

 Issue by Wilson-Ding1
Thursday Sep 28, 2017 at 04:13 GMT
Originally opened as https://github.ibm.com/IBM-Swift/swift-watson-sdk/issues/4

 Issue by rfdickerson
Friday May 06, 2016 at 12:35 GMT
Originally opened as https://github.com/IBM-Swift/swift-watson-sdk/issues/4

 Comment by Wilson-Ding1
Thursday Sep 28, 2017 at 04:13 GMT

 Comment by vherrin
Friday Jul 15, 2016 at 13:25 GMT

done

repo: IBM-Swift-Sunset/swift-watson-sdk


text:
Add new Swift Server Generator section to Getting Started guide

On request of Helen Masters - a new section of documentation added.
All formatted to appear the same as the existing documentation.
One new addition to the menu structure.

@tunniclm
Hi, thanks for reviewing.
When Helen gave me the documentation, I should have checked through all of the links as well as applied the formatting - didn't clock that, of course, her .md links should be .html.
This morning I will fix those links, and the parts that I understand, but there are some errors here that I think are best fixed either by the original author (Helen), or by someone else who understands the technical aspects.

@Joe-Brady I think @tunniclm  has provided all the replacement text with the exception of the 15.10 support one, for which I've requested he confirms. So I think you have everything you need. Is there some information you are ambiguous about still?
Thanks

"There is no -n or --name option. The name can be passed as an optional argument." - what should the final text read instead?

Replace -n or --name with
Name
Set the application name

@lroseblade @tunniclm Hi Lloyd, Mike said to remove that little section entirely? I have done that already, so let me know if you've both decided that needs changing

Sorry, didn't get around to checking the modifications today and I have a bunch of other things I need to get done tonight. I should get a look tomorrow then hopefully we'll be in shape to merge.

Ping me on Slack when its merged and I'll tweet about it (with reference to the demo at Playgrounds).

lgtm

Note: these docs are consistent with the master branch of generator-swiftserver. They will need an update when we merge in all the new work we have been doing for the next release.

Merged.
@seabaylea http://www.kitura.io/en/starter/generator.html :)

authors: Joe-Brady ianpartridge lroseblade seabaylea tunniclm

license_source: bigquery


text:
Some manual e2e tests never run because testng.xml is out-of-date in fhir-server-test

There are a handful of manual e2e tests that never run because testng.xml is out-of-date. Testng.xml should be updated to include all server integration tests and we can work out specific issues from there.

Or better yet, maybe we change / remove testng.xml altogether so that new tests are picked up automatically (by default).

I think we originally decided to go the testng.xml route so that we could easily remove or disable tests until they are fixed or removed.

authors: JohnTimm lmsurpre

repo: IBM/FHIR


text:
add_any_resource stored procedure, p_source_key not used

Is your feature request related to a problem? Please describe.
p_source_key is passed a UUID which previously was used to guarantee idempotence in replication scenarios.
Describe the solution you'd like
This is no longer used in the procedure, and can be removed as a parameter.
Describe alternatives you've considered
Leave it unchanged.
Additional context
Because this changes the signature of the procedure, some care is required to ensure the old procedure is removed.

Turned out I did this anyway in the current code, I've moved this to in progress

I think this got split out into https://github.com/IBM/FHIR/pull/1567 ...not yet closed

PR waiting review

authors: lmsurpre prb112 punktilious


text:
Unable to display the output.

Hi I am trying to run the code on google colab, but at the end I am unable to get the final output.
2023-02-27 08:39:09.639300: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 AVX512F AVX512_VNNI FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-02-27 08:39:09.769144: I tensorflow/core/util/port.cc:104] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable TF_ENABLE_ONEDNN_OPTS=0.
2023-02-27 08:39:10.469656: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer.so.7'; dlerror: libnvinfer.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /usr/lib64-nvidia
2023-02-27 08:39:10.469742: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer_plugin.so.7'; dlerror: libnvinfer_plugin.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /usr/lib64-nvidia
2023-02-27 08:39:10.469758: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
Serving TensorBoard on localhost; to expose to the network, use a proxy or pass --bind_all
TensorBoard 2.11.2 at http://localhost:6006/ (Press CTRL+C to quit)

It looks like it fails to load some dynamic libraries. Not sure what causes this error, but it is unrelated to the code itself. Please check your colab settings.

Grapher]$ tensorboard --logdir output
/cm/shared/public/apps/miniconda/3.7/lib/python3.7/site-packages/tensorflow/python/framework/dtypes.py:516: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint8 = np.dtype([("qint8", np.int8, 1)])
/cm/shared/public/apps/miniconda/3.7/lib/python3.7/site-packages/tensorflow/python/framework/dtypes.py:517: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint8 = np.dtype([("quint8", np.uint8, 1)])
/cm/shared/public/apps/miniconda/3.7/lib/python3.7/site-packages/tensorflow/python/framework/dtypes.py:518: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint16 = np.dtype([("qint16", np.int16, 1)])
/cm/shared/public/apps/miniconda/3.7/lib/python3.7/site-packages/tensorflow/python/framework/dtypes.py:519: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint16 = np.dtype([("quint16", np.uint16, 1)])
/cm/shared/public/apps/miniconda/3.7/lib/python3.7/site-packages/tensorflow/python/framework/dtypes.py:520: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint32 = np.dtype([("qint32", np.int32, 1)])
/cm/shared/public/apps/miniconda/3.7/lib/python3.7/site-packages/tensorflow/python/framework/dtypes.py:525: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_resource = np.dtype([("resource", np.ubyte, 1)])
/home/sgudati/.local/lib/python3.7/site-packages/tensorboard_data_server/bin/server: /lib64/libc.so.6: version `GLIBC_2.18' not found (required by /home/sgudati/.local/lib/python3.7/site-packages/tensorboard_data_server/bin/server)
Serving TensorBoard on localhost; to expose to the network, use a proxy or pass --bind_all
TensorBoard 2.11.2 at http://localhost:6006/ (Press CTRL+C to quit)
Unable to visualize the final output. Is it the version that I need to update?

i found this type of error :-
NOTE: Using experimental fast data loading logic. To disable, pass
"--load_fast=false" and report issues on GitHub. More details:
https://github.com/tensorflow/tensorboard/issues/4784
Traceback (most recent call last):
File "/DATA/chatterjee2/anaconda3/envs/rajnishgrapher1/bin/tensorboard", line 8, in
sys.exit(run_main())
File "/DATA/chatterjee2/anaconda3/envs/rajnishgrapher1/lib/python3.7/site-packages/tensorboard/main.py", line 46, in run_main
app.run(tensorboard.main, flags_parser=tensorboard.configure)
File "/DATA/chatterjee2/anaconda3/envs/rajnishgrapher1/lib/python3.7/site-packages/absl/app.py", line 308, in run
_run_main(main, args)
File "/DATA/chatterjee2/anaconda3/envs/rajnishgrapher1/lib/python3.7/site-packages/absl/app.py", line 254, in _run_main
sys.exit(main(argv))
File "/DATA/chatterjee2/anaconda3/envs/rajnishgrapher1/lib/python3.7/site-packages/tensorboard/program.py", line 276, in main
return runner(self.flags) or 0
File "/DATA/chatterjee2/anaconda3/envs/rajnishgrapher1/lib/python3.7/site-packages/tensorboard/program.py", line 292, in _run_serve_subcommand
server = self._make_server()
File "/DATA/chatterjee2/anaconda3/envs/rajnishgrapher1/lib/python3.7/site-packages/tensorboard/program.py", line 472, in _make_server
deprecated_multiplexer,
File "/DATA/chatterjee2/anaconda3/envs/rajnishgrapher1/lib/python3.7/site-packages/tensorboard/backend/application.py", line 146, in TensorBoardWSGIApp
experimental_middlewares,
File "/DATA/chatterjee2/anaconda3/envs/rajnishgrapher1/lib/python3.7/site-packages/tensorboard/backend/application.py", line 254, in init
"Duplicate plugins for name %s" % plugin.plugin_name
ValueError: Duplicate plugins for name projector
please help me.

another error :-
2024-04-13 14:42:19.440814: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-04-13 14:42:19.736572: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcudart.so.11.0'; dlerror: libcudart.so.11.0: cannot open shared object file: No such file or directory
2024-04-13 14:42:19.736635: I tensorflow/compiler/xla/stream_executor/cuda/cudart_stub.cc:29] Ignore above cudart dlerror if you do not have a GPU set up on your machine.
2024-04-13 14:42:20.742295: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer.so.7'; dlerror: libnvinfer.so.7: cannot open shared object file: No such file or directory
2024-04-13 14:42:20.742429: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer_plugin.so.7'; dlerror: libnvinfer_plugin.so.7: cannot open shared object file: No such file or directory
2024-04-13 14:42:20.742448: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
2024-04-13 14:42:21.987385: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcudart.so.11.0'; dlerror: libcudart.so.11.0: cannot open shared object file: No such file or directory
2024-04-13 14:42:21.987526: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcublas.so.11'; dlerror: libcublas.so.11: cannot open shared object file: No such file or directory
2024-04-13 14:42:21.987597: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcublasLt.so.11'; dlerror: libcublasLt.so.11: cannot open shared object file: No such file or directory
2024-04-13 14:42:21.991509: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcusolver.so.11'; dlerror: libcusolver.so.11: cannot open shared object file: No such file or directory
2024-04-13 14:42:21.991631: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcusparse.so.11'; dlerror: libcusparse.so.11: cannot open shared object file: No such file or directory
2024-04-13 14:42:21.991703: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcudnn.so.8'; dlerror: libcudnn.so.8: cannot open shared object file: No such file or directory
2024-04-13 14:42:21.991732: W tensorflow/core/common_runtime/gpu/gpu_device.cc:1934] Cannot dlopen some GPU libraries. Please make sure the missing libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
Skipping registering GPU devices...
NOTE: Using experimental fast data loading logic. To disable, pass
"--load_fast=false" and report issues on GitHub. More details:
https://github.com/tensorflow/tensorboard/issues/4784
Serving TensorBoard on localhost; to expose to the network, use a proxy or pass --bind_all
TensorBoard 2.11.2 at http://localhost:6006/ (Press CTRL+C to quit)
but it doesn't give any output in this localhost.    , please help me

repo: IBM/Grapher


text:
Accessibility for TooltipDefinition

Accessibility for TooltipDefinition

Describe in detail the issue you're having.
My react component has code like:

              <TooltipDefinition onMouseOver={this.onMouseOver} tooltipText={name || 'undefined'} aria-label='tooltip for parameter'>
              </TooltipDefinition>

...

The generated html is like:

    <button class="bx--tooltip__trigger" aria-describedby="definition-tooltip-13"></button>

classes

The DAP accessibility tool complains:

Each form control must have associated label.
on the<button>tag line.

Please see if a label can be generated for it.

Is this issue related to a specific component?
TooltipDefinition

What did you expect to happen? What happened instead? What would you like to see changed?
no DAP error for the component

What browser are you working in?
Chrome

What version of the Carbon Design System are you using?
"carbon-components": "~9.1.13",
"carbon-components-react": "^6.12.1",

What offering/product do you work on? Any pressing ship or release dates we should be aware of?
console

Hi @gracelo! 👋 Thanks so much for taking the time to make this issue 😄
With this DAP error specifically, you need to have content in the Tooltip for the violation to pass. You can see in our Storybook how this component is intended to be used, namely:
<TooltipDefinition tooltipText="Brief description of the dotted, underlined word above.">
  Definition Tooltip
</TooltipDefinition>

This text is then placed inside the button which should get rid of this violation.

However, in my UI design, the tooltip only shows the tooltipText on hovering.  We don't want to show any default text inside the TooltipDefinition.

Sounds good! Could you share an image or gif that shows the behavior you're looking for in your UI?

So the "vertical line" has the tooltip when hovering on, shows type name.

Ah, unfortunately that's not an intended use-case for TooltipDefinition. Here's some information on the component:

Ok.  I will circle back to the team and may be that part cannot be accessible at the moment.

http://carbondesignsystem.com/components/tooltip/usage

Going to close this for now, feel free to comment if there is still an issue!

authors: gracelo joshblack tw15egan

repo: IBM/carbon-components-react


text:
♿Checkbox AVT1 - August 2018♿

Environment
Chrome Version 70.0.3538.67 (Official Build) (64-bit)
macOS Mojave 10/Windows 10
Violations:
Minimum contrast of 3.36 with its background is not sufficient to meet WCAG AA requirements for text of size 14px and weight of 400 on the disabled checkbox element.
How to reproduce

Download the Dynamic Accessibility Plugin tool here
Run the extension using the August 2018 ruleset

Do we need the contrast requirement for a disabled state? I always thought that we didn't.

The rule states The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, with a 3:1 ratio for large-scale text. with an incidental exception for inactive interface components. So it the design follows the letter of the law.
There is an issue where if the user is in High Contrast mode the only indication that the text is disabled is a cursor change on hover, but we might be fine with that as well.
If we are cool with it this ticket can just be used to document a false positive for help with future audits.

Jeoff: Consider solutions to accessibility that's not contrast. Maybe on hover there can be a tooltip/message saying "this is disabled" etc

@aagonzales This violation is specifically for checkbox.

Although the recommended fix will remove the violation it turns out that there is a DAP GitHub issue 1184 that is causing the violation in error and it should be fixed in the next DAP release expected later this month.  This should be re-tested with the new ruleset.

I'll close this for now and we'll test it on the next DAP release. Thanks all!

authors: dakahn joshblack shixiedesign snidersd

repo: IBM/carbon-components


text:
Immutability check in service controller failing

Create a translator
Change serviceClass to messagehub
Result is 3 services (2 messagehubs and 1 translator)

Fixed in v0.1.7

repo: IBM/cloud-operators


text:
fake implementation for unit tests

Is your feature request related to a problem? Please describe.
When I use this sdk, it makes it difficult to unit test this without passing functions like postDocument in as a function argument and having to declare types in order to mock them in an easy way or I have to create a http test server and understand the underlying api calls that this cloudant SDK makes. I imagine other consumers of this library also hit the same problems.
Describe the solution you'd like
A fake implementation that allows a user to configure what a function call to cloudant returns. This allows users to maintain less code and have a single source of mocking calls to cloudant for unit testing.
Describe alternatives you've considered
As above in the first part.
Additional context
Add any other context or screenshots about the feature request here.

Right now we don't have plans to introduce lightweight test doubles for our sdk functions. We might look into it in the future, but it's not on a priority list.
What I can suggest is to define a service interface that'd specify a subset of cloudant-go-sdk functions your application's using, something like:
type Service interface {
  PostDocument(opts *cloudantv1.PostDocumentOptions) (result *cloudantv1.DocumentResult, response *core.DetailedResponse, err error)
}

Then you can use it in your application instead of a direct instance of CloudantV1 and mock it in your tests, so you wouldn't need to pass functions into them. This is pretty common approach in golang for testing a database layer in isolation and there are generic mocking libraries that simplify this, e.g. https://github.com/golang/mock, though they are adding a bit of a learning curve.
Another approach would be more in an integration tests venue to run CouchDB or Cloudant docker container, a Cloudant service instance or a mock HTTP server and execute tests against them. We are using all three of those in our separate sdk's test suite and it proved to be reasonably reliable method.

authors: eiri jack-evans

repo: IBM/cloudant-go-sdk


text:
Encoding issue with new OR concatenation

Test framework failing due to an encoding issue of the develop branch .
450: Unexpected character: ' ' @ line 450, column 35.
   		} else if (isDLI(logicalFile) || isIMS(logicalFile)) {
                                     ^

1 error

https://github.com/IBM/dbb-zappbuild/blob/f9257a10d765f1ac8ced1adb0a3d55e025327483/utilities/BuildUtilities.groovy#L450

Resolved

repo: IBM/dbb-zappbuild


text:
Deploy decentralized energy network app in local host?

Hi,
How can I deploy decentralized energy network app in local host instead of IBM Blockchain Platform?
Thx in advance.

You can run this locally by using the https://github.com/hyperledger/fabric-samples repository. Or you can make your own repository with customized scripts.
For using fabric-samples you need to

Clone this repo and fabric-samples repo separately

Hi,
I follow your instruction but when I run ./startFabric.sh, there is error:
...
Creating cli ... done
Error: open 1.0: no such file or directory
I think the error happened when exciting command in startFabric.sh
docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp" cli peer chaincode install -n decentralized-energy-v 1.0 -p "$CC_SRC_PATH" -l "$LANGUAGE"
Any idea how to fix this?

Is there a space between decentralized-energy and -v 1.0. I guess the space got missed when I typed out the command. Try and let me know.

Hi,
Thanks a lot. There is progress now. The command "docker exec -e  .." works after I add a space between decentralized-energy and -v 1.0 as per you recommended.
However, there is error:
Error: error getting chaincode code decentralized-energy: path to chaincode does not exist: github.com/decentralized-energy/node
I noted that in startFabric.sh, there is a line:
CC_SRC_PATH=github.com/decentralized-energy/node
In my PC, the structure is below. I cannot find the path .../github.com/decentralized-energy/node anywhere
~/fabric-samples
-- decentralized-energy
-- startFabric.sh
-- application
~/fabric-samples
-- chaincode
-- decentralized-energy
-- node
-- lib
-- index.js

Does that mean its fabric-samples/chaincode/decentralized-energy/node in which all the files are present?
The pathing is a minor issue, means you are almost there. When running the containers the pathing becomes a bit weird cause you are now interacting with docker.

Hi Varun,
Yes, the folder ~/fabric-samples/chaincode/decentralized-energy/node exists because I followed your step 2 to create/rename it as below. Not sure all the files are present there.

Copy paste the contract folder to fabric-samples/chaincode/decentralized-energy and rename the folder to node.

@gnurtcouq omg I am so sorry, just realized my command has a typo in it :)
CC_SRC_PATH=/opt/gopath/src/github.com/chaincode/decentralized-energy/node should fix the problem. Using node chaincode requires absolute path unlike golang, so I missed the edit.

Hi Varun,
Thanks. I have changed CC_SRC_PATH in startFabric.sh as your recommended:
CC_SRC_PATH=/opt/gopath/src/github.com/chaincode/decentralized-energy/node
I also remember that in the file ~/fabric-samples/basic-network/docker-compose.yml should have the mapping for cli as:
_cli:
container_name: cli
image: hyperledger/fabric-tools
tty: true
environment:
- GOPATH=/opt/gopath
- CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
- FABRIC_LOGGING_SPEC=info
- CORE_PEER_ID=cli
- CORE_PEER_ADDRESS=peer0.org1.example.com:7051
- CORE_PEER_LOCALMSPID=Org1MSP
- CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
- CORE_CHAINCODE_KEEPALIVE=10
working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
command: /bin/bash
volumes:
- /var/run/:/host/var/run/
- ./../chaincode/:/opt/gopath/src/github.com/
- ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
- ./../chaincode/decentralized-energy/node/:/opt/gopath/src/github.com/chaincode/decentralized-energy/node/
Then I run ./startFabric.sh
This time, there is progress. But there is another error:
Creating cli ... done
2019-06-27 08:54:23.535 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2019-06-27 08:54:23.536 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
2019-06-27 08:54:23.584 UTC [chaincodeCmd] install -> INFO 003 Installed remotely response:<status:200 payload:"OK" >
2019-06-27 08:54:24.141 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2019-06-27 08:54:24.141 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
Error: could not assemble transaction, err proposal response was not successful, error code 500, msg transaction returned with failure: Error: You've asked to invoke a function that does not exist:
Any idea how to fix this?

Hi Varun,
Finally I found another typo in the startFabric.sh & I correct it by :
docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp" cli peer chaincode instantiate -o orderer.example.com:7050 -C mychannel -n decentralized-energy -l "$LANGUAGE" -v 1.0 -c '{"Args":[]}' -P "AND('Org1MSP.member','Org2MSP.member')"
Then it worked!. It shows a message:
Creating cli ... done
2019-06-27 09:10:17.524 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2019-06-27 09:10:17.524 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
2019-06-27 09:10:17.567 UTC [chaincodeCmd] install -> INFO 003 Installed remotely response:<status:200 payload:"OK" >
2019-06-27 09:10:18.085 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2019-06-27 09:10:18.086 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
Total setup execution time : 43 secs ...
Start by installing required packages run 'npm install'
Then run 'node enrollAdmin.js', then 'node registerUser'
The 'node invoke.js' will fail until it has been updated with valid arguments
The 'node query.js' may be run at anytime once the user has been registered
What the next steps I should continue?

what was the typo in startFabric.sh, I am unable to see what the difference was eactly.
So now the chainode is installed and running. You can confirm by typing docker ps. You should see a new container dev.*.*.decentralized-energy.*, a very long name. Next steps are the same as the ones in the current ReadMe. Start with npm install from the application folder, node enrollAdmin.js will enroll the default user registered with the CA while brining up the network. Just run the commands one after another.
Looks like everything is working fine for you :)

Hi Varun,
The typo is:

OK, if everything is working, lets close the issue?

Hi Varun,
When I run command:
docker ps|grep decentralized-energy
It shows:
c4f63829ad6e        dev-peer0.org1.example.com-decentralized-energy-1.0-8708ae281243dcb8f47086ca1f47209a7c84d2a13a8774a7a3cb4145d9f9604f
But when going to application folder and run "npm install", then run "node enrollAdmin.js" , there is error:
error: [FabricCAClientService.js]: Failed to enroll app-admin, error:%o message=Calling enrollment endpoint failed with error [Error: connect ETIMEDOUT 184.172.242.127:31286], stack=Error: Calling enrollment endpoint failed with error [Error: connect ETIMEDOUT 184.172.242.127:31286]
When I tried to ping:
ping 184.172.242.127
It's OK. Any ideal how to fix this?

Right, so the client is using the connection profile provided by IBM. That is to be used when deploying on a cloud service provider. For your self, look at other samples in the code such as this. Essentially the connections.json and config.json need to be modified. You can simply copy code used in fabcar/javascript

Hi Varun,
After customizing the connections.json and config.json, I managed to run "node enrollAdmin.js" with the respond from system as:
node enrollAdmin.js
Wallet path: ~/fabric-samples/decentralized-energy/application/_idwallet
msg: Successfully enrolled admin user admin and imported it into the wallet
Next step as per ReadMe is to run "node registerUser.js" but I got error:
Error: Cannot find module '~/fabric-samples/decentralized-energy/application/registerUser.js'
I check & found no file registerUse.js in above folder. Any idea how to fix?

@gnurtcouq - are you reading from this pattern URL: https://github.com/IBM/decentralized-energy-fabric-on-IBP20?  It appears you are reading from an old readme.  The next step after enrolling the Admin is to start the application server.  fyi @varunagarwal315

Ohh I assumed he wanted to run through command line, forgot about the UI. Was referring to using these files followed by the invoke functions interact with the smart contracts. I guess I have caused some confusion.

Hi Varun/ ljbennett
Thanks for the reminder. I followed the instruction in  URL: https://github.com/IBM/decentralized-energy-fabric-on-IBP20 and execute command "npm start" under application folder but there is error:

gfapplication@0.0.7 start ~/fabric-samples/decentralized-energy/application
fabric-chaincode-node start

sh: 1: fabric-chaincode-node: not found
npm ERR! Linux 4.15.0-54-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "start"
npm ERR! node v8.10.0
npm ERR! npm  v3.5.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! gfapplication@0.0.7 start: fabric-chaincode-node start
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the gfapplication@0.0.7 start script 'fabric-chaincode-node start'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the gfapplication package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     fabric-chaincode-node start
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs gfapplication
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls gfapplication
npm ERR! There is likely additional logging output above.
How can I fix this?

I believe you need to run npm start under /web-app/server and then either go to the port if mentioned separately or the default one 8081.

Hi Varun/ ljbennett,
I copied/pasted the web-app folder to ~/fabric-samples/decentralized-energy. From there I customized the connections.json and config.json, then run "node enrollAdmin.js" under /web-app/server without any error.
Next step as per instructions in https://github.com/IBM/decentralized-energy-fabric-on-IBP20, I run:
npm start

server@1.0.0 start ~/fabric-samples/decentralized-energy/web-app/server
./node_modules/nodemon/bin/nodemon.js src/app.js

[nodemon] 1.19.1
[nodemon] to restart at any time, enter rs
[nodemon] watching: .
[nodemon] starting node src/app.js
Then I use Firefox to connect to http://localhost:4200/. It shows the Welcome page of "Decentralized Energy with Hyperledger Fabric". When click Participants/Residents, there is error in my browser "Error: 401 - Unauthorized ".
In the Console log, it shows:
::ffff:127.0.0.1 - - [06/Jul/2019:02:10:32 +0000] "OPTIONS /api/Resident HTTP/1.1" 204 0 "http://localhost:4200/Resident" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0"
::ffff:127.0.0.1 - - [06/Jul/2019:02:10:32 +0000] "GET /api/Resident HTTP/1.1" 401 1467 "http://localhost:4200/Resident" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0"
UnauthorizedError: jwt expired
at ~/fabric-samples/decentralized-energy/web-app/server/node_modules/express-jwt/lib/index.js:102:22
at ~/fabric-samples/decentralized-energy/web-app/server/node_modules/jsonwebtoken/verify.js:152:16
at getSecret (~/fabric-samples/decentralized-energy/web-app/server/node_modules/jsonwebtoken/verify.js:90:14)
at Object.module.exports [as verify] (~/fabric-samples/decentralized-energy/web-app/server/node_modules/jsonwebtoken/verify.js:94:10)
at verifyToken (~/fabric-samples/decentralized-energy/web-app/server/node_modules/express-jwt/lib/index.js:100:13)
at fn (~/fabric-samples/decentralized-energy/web-app/server/node_modules/async/lib/async.js:746:34)
at ~/fabric-samples/decentralized-energy/web-app/server/node_modules/async/lib/async.js:1213:16
at ~/fabric-samples/decentralized-energy/web-app/server/node_modules/async/lib/async.js:166:37
at ~/fabric-samples/decentralized-energy/web-app/server/node_modules/async/lib/async.js:706:43
at ~/fabric-samples/decentralized-energy/web-app/server/node_modules/async/lib/async.js:167:37
How can I fix this error?

@gnurtcouq You need to first authorize access by clicking the Green "Authorize action" button. You can refer the gif in the https://github.com/IBM/decentralized-energy-fabric-on-IBP20#7-run-the-application section.


text:
fix: support JSSE system properties

This commit makes a small change to the
HttpClientSingleton.setupTLSProtocol() method
to allow for the use of mutual TLS (i.e. client
authentication).
Specifically, the code changes will allow the JSSE-related
system properties to be used to specify a client truststore
and/or keystore:

javax.net.ssl.trustStore
javax.net.ssl.trustStorePassword
javax.net.ssl.keyStore
javax.net.ssl.keyStorePassword

Isn't this a breaking change?
Consider a case where the default SSLContext for whatever reason doesn't enable the TLS protocol. The existing code using getInstance("TLS") will go through the list of configured providers looking for one that does support TLS, but this new code will not and will fail instead; ulimately forcing a user configuration change to add TLS support in their default context (which is presumably not desirable if it hasn't been configured as such) or to otherwise customize the SSLSocketFactory.
I'm not sure just how significant that risk is, but nonetheless I feel it is a breaking behaviour change and it probably disproportionately impacts server environments with different frontend/backend contexts.
I also have concerns about  disableSslVerification (beyond my usual ones about how I dislike that option 😄) - it won't delegate to the default SSLContext instead creating one in the current style, so there will be mismatch in behaviour depending if that toggle is on (beyond the existing one I've just noticed where SSL and TLS may not be necessarily be provided by the same provider anyway) .
Looking at this are of code in general I think we should probably consider the balance of the most common use case vs where customization is required by the user before making a breaking change. For example using cacerts by default is more likely to succeed when connecting to the IBM Cloud services with public certs than using any other configured trust store. Further when running the SDKs in e.g. an app in a WAS Liberty runtime then there are some specific caveats around what is honoured and what isn't and expectations for third-party (i.e. non-WAS) code to call SSLSocketFactory.getDefault() rather than SSLContext.getDefault().
In the meantime #174 provides an option for customizing right? via something like:
getHttpClient().newBuilder().sslSocketFactory(...).build()

@ricellis and I discussed this via slack and decided not to go with these changes due to the potential change in default behavior for users.   It's not clear how popular mTLS is among our users, so we need to be careful not to potentially break existing (non-mTLS) users in order to solve a problem that has unknown scope/prevalence. I'll be looking at alternatives and will submit a new PR if/when appropriate.

authors: padamstx ricellis

repo: IBM/java-sdk-core


text:
File Lock Tests: flock  and fcntl positive lock and negative lock pods scheduled on same node

flock across nodes is not supported.
Use podAffinity for create-lock , create-lock2 pods to be scheduled on the same node

Test results:
spectrum storage:
 ansible-playbook main.yml --extra-vars "@./params.yml" | tee output.log
[WARNING]: No inventory was parsed, only implicit localhost is available
[WARNING]: provided hosts list is empty, only localhost is available. Note that
the implicit localhost does not match 'all'

PLAY [localhost] ***************************************************************

TASK [ocp login using creds] ***************************************************
changed: [localhost]

TASK [ocp login using token] ***************************************************
skipping: [localhost]

TASK [debug] *******************************************************************
ok: [localhost] => {
    "login_creds.stdout_lines": [
        "WARNING: Using insecure TLS client config. Setting this option is not supported!",
        "",
        "Login successful.",
        "",
        "You have access to 82 projects, the list has been suppressed. You can list all projects with 'oc projects'",
        "",
        "Using project \"zen\"."
    ]
}

TASK [debug] *******************************************************************
skipping: [localhost]

TASK [Storage Readiness] *******************************************************
[WARNING]: Collection kubernetes.core does not support Ansible version 2.10.17

TASK [storage-readiness : Create namespace stgtest if not present] *************
ok: [localhost]

TASK [storage-readiness : Run simple mount test for ReadWriteOnce] *************
included: /root/storage_test/k8s-storage-tests/roles/storage-readiness/tasks/mount-test.yaml for localhost

TASK [storage-readiness : Test mount ReadWriteOnce volumes for readiness] ******
changed: [localhost] => (item={'name': 'create-volume.yaml.j2'})
ok: [localhost] => (item={'name': 'mount-job.yaml.j2'})

TASK [storage-readiness : Verify mount completed for ReadWriteOnce] ************
FAILED - RETRYING: Verify mount completed for ReadWriteOnce (20 retries left).
FAILED - RETRYING: Verify mount completed for ReadWriteOnce (19 retries left).
ok: [localhost]

TASK [storage-readiness : debug] ***********************************************
ok: [localhost] => {
    "msg": "######################## MOUNT TESTS PASSED FOR ReadWriteOnce Volume  #################################"
}

TASK [storage-readiness : Run simple mount test for ReadWriteMany] *************
included: /root/storage_test/k8s-storage-tests/roles/storage-readiness/tasks/mount-test.yaml for localhost

TASK [storage-readiness : Test mount ReadWriteMany volumes for readiness] ******
changed: [localhost] => (item={'name': 'create-volume.yaml.j2'})
changed: [localhost] => (item={'name': 'mount-job.yaml.j2'})

TASK [storage-readiness : Verify mount completed for ReadWriteMany] ************
FAILED - RETRYING: Verify mount completed for ReadWriteMany (20 retries left).
FAILED - RETRYING: Verify mount completed for ReadWriteMany (19 retries left).
ok: [localhost]

TASK [storage-readiness : debug] ***********************************************
ok: [localhost] => {
    "msg": "######################## MOUNT TESTS PASSED FOR ReadWriteMany Volume  #################################"
}

TASK [storage-readiness : Run sequential RW tests for ReadWriteOnce] ***********
included: /root/storage_test/k8s-storage-tests/roles/storage-readiness/tasks/sequential-rw.yaml for localhost

TASK [storage-readiness : Test mount ReadWriteOnce volumes for readiness] ******
ok: [localhost] => (item={'name': 'create-volume.yaml.j2'})

TASK [storage-readiness : Set config maps] *************************************
changed: [localhost] => (item={'name': 'producer-cm.yaml.j2'})
changed: [localhost] => (item={'name': 'consumer-cm.yaml.j2'})

TASK [storage-readiness : Sequential read/write ReadWriteOnce volumes for readiness] ***
changed: [localhost] => (item={'name': 'producer.yaml.j2'})
changed: [localhost] => (item={'name': 'consumer.yaml.j2'})

TASK [storage-readiness : debug] ***********************************************
ok: [localhost] => {
    "msg": "######################## SEQUENTIAL READ WRITE TEST PASSED FOR ReadWriteOnce Volume #################################"
}

TASK [storage-readiness : Run sequential RW tests for ReadWriteMany] ***********
included: /root/storage_test/k8s-storage-tests/roles/storage-readiness/tasks/sequential-rw.yaml for localhost

TASK [storage-readiness : Test mount ReadWriteMany volumes for readiness] ******
ok: [localhost] => (item={'name': 'create-volume.yaml.j2'})

TASK [storage-readiness : Set config maps] *************************************
ok: [localhost] => (item={'name': 'producer-cm.yaml.j2'})
ok: [localhost] => (item={'name': 'consumer-cm.yaml.j2'})

TASK [storage-readiness : Sequential read/write ReadWriteMany volumes for readiness] ***
changed: [localhost] => (item={'name': 'producer.yaml.j2'})
changed: [localhost] => (item={'name': 'consumer.yaml.j2'})

TASK [storage-readiness : debug] ***********************************************
ok: [localhost] => {
    "msg": "######################## SEQUENTIAL READ WRITE TEST PASSED FOR ReadWriteMany Volume #################################"
}

TASK [storage-readiness : Run parallel rw single thread tests  ReadWriteOnce] ***
included: /root/storage_test/k8s-storage-tests/roles/storage-readiness/tasks/parallel-rw-single-thread.yaml for localhost

TASK [storage-readiness : Test mount ReadWriteOnce volumes for readiness] ******
ok: [localhost] => (item={'name': 'create-volume.yaml.j2'})

TASK [storage-readiness : Set config maps] *************************************
ok: [localhost] => (item={'name': 'producer-cm.yaml.j2'})
changed: [localhost] => (item={'name': 'consumer-nocheck-cm.yaml.j2'})

TASK [storage-readiness : Parallel read/write  ReadWriteOnce volumes for readiness] ***
changed: [localhost] => (item={'name': 'producer.yaml.j2'})

TASK [storage-readiness : Parallel concurrency read while producer is running] ***
changed: [localhost] => (item={'name': 'consumer-nocheck.yaml.j2'})

TASK [storage-readiness : Assert that producer is still running] ***************
ok: [localhost]

TASK [storage-readiness : Warn if producer job is already completed] ***********
skipping: [localhost]

TASK [storage-readiness : Wait until producer job is done] *********************
FAILED - RETRYING: Wait until producer job is done (20 retries left).
ok: [localhost]

TASK [storage-readiness : Parallel read  ReadWriteOnce volumes for readiness] ***
changed: [localhost] => (item={'name': 'consumer.yaml.j2'})

TASK [storage-readiness : debug] ***********************************************
ok: [localhost] => {
    "msg": "######################## SINGLE THREAD PARALLEL READ WRITE TEST PASSED for ReadWriteOnce #################################"
}

TASK [storage-readiness : Run parallel rw single thread tests for ReadWriteMany] ***
included: /root/storage_test/k8s-storage-tests/roles/storage-readiness/tasks/parallel-rw-single-thread.yaml for localhost

TASK [storage-readiness : Test mount ReadWriteMany volumes for readiness] ******
ok: [localhost] => (item={'name': 'create-volume.yaml.j2'})

TASK [storage-readiness : Set config maps] *************************************
ok: [localhost] => (item={'name': 'producer-cm.yaml.j2'})
ok: [localhost] => (item={'name': 'consumer-nocheck-cm.yaml.j2'})

TASK [storage-readiness : Parallel read/write  ReadWriteMany volumes for readiness] ***
changed: [localhost] => (item={'name': 'producer.yaml.j2'})

TASK [storage-readiness : Parallel concurrency read while producer is running] ***
changed: [localhost] => (item={'name': 'consumer-nocheck.yaml.j2'})

TASK [storage-readiness : Assert that producer is still running] ***************
ok: [localhost]

TASK [storage-readiness : Warn if producer job is already completed] ***********
skipping: [localhost]

TASK [storage-readiness : Wait until producer job is done] *********************
FAILED - RETRYING: Wait until producer job is done (20 retries left).
ok: [localhost]

TASK [storage-readiness : Parallel read  ReadWriteMany volumes for readiness] ***
changed: [localhost] => (item={'name': 'consumer.yaml.j2'})

TASK [storage-readiness : debug] ***********************************************
ok: [localhost] => {
    "msg": "######################## SINGLE THREAD PARALLEL READ WRITE TEST PASSED for ReadWriteMany #################################"
}

TASK [storage-readiness : Run parallel rw multi thread tests for ReadWriteOnce] ***
included: /root/storage_test/k8s-storage-tests/roles/storage-readiness/tasks/parallel-rw-multi-thread.yaml for localhost

TASK [storage-readiness : Test mount ReadWriteOnce volumes for readiness] ******
ok: [localhost] => (item={'name': 'create-volume.yaml.j2'})

TASK [storage-readiness : Set config maps] *************************************
ok: [localhost] => (item={'name': 'producer-cm.yaml.j2'})
ok: [localhost] => (item={'name': 'consumer-nocheck-cm.yaml.j2'})

TASK [storage-readiness : Get node count] **************************************
ok: [localhost]

TASK [storage-readiness : set_fact] ********************************************
ok: [localhost]

TASK [storage-readiness : Parallel write from same/separate nodes] *************
changed: [localhost] => (item={'name': 'parallel-producer.yaml.j2'})

TASK [storage-readiness : Parallel write no wait from same/separate nodes] *****
changed: [localhost] => (item={'name': 'parallel-producer.yaml.j2'})

TASK [storage-readiness : Parallel read no wait from same/separate nodes] ******
changed: [localhost] => (item={'name': 'parallel-consumer.yaml.j2'})

TASK [storage-readiness : Wait Until parallel producer job is done] ************
FAILED - RETRYING: Wait Until parallel producer job is done (10 retries left).
ok: [localhost]

TASK [storage-readiness : Wait Until parallel consumer job is done] ************
ok: [localhost]

TASK [storage-readiness : debug] ***********************************************
ok: [localhost] => {
    "msg": "######################## MULTI NODE PARALLEL READ WRTIE TEST PASSED FOR ReadWriteOnce #################################"
}

TASK [storage-readiness : Run parallel rw multi thread tests  for ReadWriteMany] ***
included: /root/storage_test/k8s-storage-tests/roles/storage-readiness/tasks/parallel-rw-multi-thread.yaml for localhost

TASK [storage-readiness : Test mount ReadWriteMany volumes for readiness] ******
ok: [localhost] => (item={'name': 'create-volume.yaml.j2'})

TASK [storage-readiness : Set config maps] *************************************
ok: [localhost] => (item={'name': 'producer-cm.yaml.j2'})
ok: [localhost] => (item={'name': 'consumer-nocheck-cm.yaml.j2'})

TASK [storage-readiness : Get node count] **************************************
ok: [localhost]

TASK [storage-readiness : set_fact] ********************************************
ok: [localhost]

TASK [storage-readiness : Parallel write from same/separate nodes] *************
changed: [localhost] => (item={'name': 'parallel-producer.yaml.j2'})

TASK [storage-readiness : Parallel write no wait from same/separate nodes] *****
changed: [localhost] => (item={'name': 'parallel-producer.yaml.j2'})

TASK [storage-readiness : Parallel read no wait from same/separate nodes] ******
changed: [localhost] => (item={'name': 'parallel-consumer.yaml.j2'})

TASK [storage-readiness : Wait Until parallel producer job is done] ************
FAILED - RETRYING: Wait Until parallel producer job is done (10 retries left).
ok: [localhost]

TASK [storage-readiness : Wait Until parallel consumer job is done] ************
ok: [localhost]

TASK [storage-readiness : debug] ***********************************************
ok: [localhost] => {
    "msg": "######################## MULTI NODE PARALLEL READ WRTIE TEST PASSED FOR ReadWriteMany #################################"
}

TASK [storage-readiness : File UID permission tests for ReadWriteMany] *********
included: /root/storage_test/k8s-storage-tests/roles/storage-readiness/tasks/file-uid-test.yaml for localhost

TASK [storage-readiness : Test mount ReadWriteMany volumes for readiness] ******
ok: [localhost] => (item={'name': 'create-volume.yaml.j2'})

TASK [storage-readiness : Set config maps] *************************************
ok: [localhost] => (item={'name': 'producer-cm.yaml.j2'})
ok: [localhost] => (item={'name': 'consumer-cm.yaml.j2'})

TASK [storage-readiness : create custom scc] ***********************************
changed: [localhost]

TASK [storage-readiness : create custom sa] ************************************
changed: [localhost]

TASK [storage-readiness : add scc to custom sa] ********************************
changed: [localhost]

TASK [storage-readiness : File uid create ReadWriteMany volumes for readiness] ***
changed: [localhost] => (item={'name': 'file-owner-uid-test.yaml.j2'})
changed: [localhost] => (item={'name': 'file-create-uid.yaml.j2'})
changed: [localhost] => (item={'name': 'file-edit-uid.yaml.j2'})

TASK [storage-readiness : debug] ***********************************************
ok: [localhost] => {
    "msg": "######################## FILE UID TEST PASSED FOR ReadWriteMany Volume #################################"
}

TASK [storage-readiness : SupplementalGroup GID permission tests for ReadWriteMany] ***
included: /root/storage_test/k8s-storage-tests/roles/storage-readiness/tasks/file-permissions-test.yaml for localhost

TASK [storage-readiness : Test mount ReadWriteMany volumes for readiness] ******
ok: [localhost] => (item={'name': 'create-volume.yaml.j2'})

TASK [storage-readiness : Set config maps] *************************************
ok: [localhost] => (item={'name': 'producer-cm.yaml.j2'})
ok: [localhost] => (item={'name': 'consumer-cm.yaml.j2'})

TASK [storage-readiness : Get first uid from project range] ********************
changed: [localhost]

TASK [storage-readiness : Set target uid to set for the reader job to be different than the writer] ***
ok: [localhost]

TASK [storage-readiness : debug] ***********************************************
ok: [localhost] => {
    "msg": "The target_uid_reader is 1000810100"
}

TASK [storage-readiness : create custom scc] ***********************************
skipping: [localhost]

TASK [storage-readiness : create custom sa] ************************************
skipping: [localhost]

TASK [storage-readiness : add scc to custom sa] ********************************
skipping: [localhost]

TASK [storage-readiness : File Permissions GID test for ReadWriteMany volumes for readiness] ***
changed: [localhost] => (item={'name': 'create-file-gid.yaml.j2'})
changed: [localhost] => (item={'name': 'read-file-gid.yaml.j2'})
changed: [localhost] => (item={'name': 'edit-file-gid.yaml.j2'})

TASK [storage-readiness : File Permissions Supplemental Group test for ReadWriteMany volumes for readiness] ***
changed: [localhost] => (item={'name': 'create-file-gid.yaml.j2'})
changed: [localhost] => (item={'name': 'read-file-gid.yaml.j2'})
changed: [localhost] => (item={'name': 'edit-file-gid.yaml.j2'})

TASK [storage-readiness : debug] ***********************************************
ok: [localhost] => {
    "msg": "######################## FILE PERMISSIONS TEST PASSED FOR ReadWriteMany Volume #################################"
}

TASK [storage-readiness : FSGroup GID permission tests for ReadWriteOnce] ******
included: /root/storage_test/k8s-storage-tests/roles/storage-readiness/tasks/file-permissions-test.yaml for localhost

TASK [storage-readiness : Test mount ReadWriteOnce volumes for readiness] ******
ok: [localhost] => (item={'name': 'create-volume.yaml.j2'})

TASK [storage-readiness : Set config maps] *************************************
ok: [localhost] => (item={'name': 'producer-cm.yaml.j2'})
ok: [localhost] => (item={'name': 'consumer-cm.yaml.j2'})

TASK [storage-readiness : Get first uid from project range] ********************
changed: [localhost]

TASK [storage-readiness : Set target uid to set for the reader job to be different than the writer] ***
ok: [localhost]

TASK [storage-readiness : debug] ***********************************************
ok: [localhost] => {
    "msg": "The target_uid_reader is 1000810100"
}

TASK [storage-readiness : create custom scc] ***********************************
changed: [localhost]

TASK [storage-readiness : create custom sa] ************************************
changed: [localhost]

TASK [storage-readiness : add scc to custom sa] ********************************
changed: [localhost]

TASK [storage-readiness : File Permissions GID test for ReadWriteOnce volumes for readiness] ***
changed: [localhost] => (item={'name': 'create-file-gid.yaml.j2'})
changed: [localhost] => (item={'name': 'read-file-gid.yaml.j2'})
changed: [localhost] => (item={'name': 'edit-file-gid.yaml.j2'})

TASK [storage-readiness : File Permissions Supplemental Group test for ReadWriteOnce volumes for readiness] ***
changed: [localhost] => (item={'name': 'create-file-gid.yaml.j2'})
changed: [localhost] => (item={'name': 'read-file-gid.yaml.j2'})
changed: [localhost] => (item={'name': 'edit-file-gid.yaml.j2'})

TASK [storage-readiness : debug] ***********************************************
ok: [localhost] => {
    "msg": "######################## FILE PERMISSIONS TEST PASSED FOR ReadWriteOnce Volume #################################"
}

TASK [storage-readiness : Subpath tests ReadWriteMany] *************************
included: /root/storage_test/k8s-storage-tests/roles/storage-readiness/tasks/volume-subpath-test.yaml for localhost

TASK [storage-readiness : Test mount ReadWriteMany volumes for readiness] ******
ok: [localhost] => (item={'name': 'create-volume.yaml.j2'})

TASK [storage-readiness : Set config maps] *************************************
ok: [localhost] => (item={'name': 'producer-cm.yaml.j2'})
ok: [localhost] => (item={'name': 'consumer-cm.yaml.j2'})

TASK [storage-readiness : Subpath tests for ReadWriteMany volumes for readiness] ***
changed: [localhost] => (item={'name': 'producer-subpath.yaml.j2'})
changed: [localhost] => (item={'name': 'consumer-subpath.yaml.j2'})

TASK [storage-readiness : debug] ***********************************************
ok: [localhost] => {
    "msg": "######################## SUB PATH TEST PASSED FOR ReadWriteMany Volume #################################"
}

TASK [storage-readiness : File locks tests] ************************************
included: /root/storage_test/k8s-storage-tests/roles/storage-readiness/tasks/file-lock-test.yaml for localhost

TASK [storage-readiness : Test mount ReadWriteMany volumes for readiness] ******
ok: [localhost] => (item={'name': 'create-volume.yaml.j2'})

TASK [storage-readiness : Set config maps] *************************************
ok: [localhost] => (item={'name': 'producer-cm.yaml.j2'})

TASK [storage-readiness : File lock test for readiness] ************************
changed: [localhost] => (item={'name': 'file-lock.yaml.j2'})

TASK [storage-readiness : Wait few seconds] ************************************
Pausing for 20 seconds
(ctrl+C then 'C' = continue early, ctrl+C then 'A' = abort)
ok: [localhost]

TASK [storage-readiness : Negative file lock test for readiness] ***************
changed: [localhost] => (item={'name': 'file-lock2.yaml.j2'})

TASK [storage-readiness : Wait for lock to be released] ************************
changed: [localhost] => (item={'name': 'file-lock.yaml.j2'})

TASK [storage-readiness : Positive lock test for readiness] ********************

changed: [localhost] => (item={'name': 'file-lock.yaml.j2'})

TASK [storage-readiness : Fcntl test for readiness] ****************************
changed: [localhost] => (item={'name': 'file-lock-fcntl.yaml.j2'})

TASK [storage-readiness : Wait few seconds] ************************************
Pausing for 20 seconds
(ctrl+C then 'C' = continue early, ctrl+C then 'A' = abort)
ok: [localhost]

TASK [storage-readiness : Negative Fcntl test for readiness] *******************
changed: [localhost] => (item={'name': 'file-lock-fcntl2.yaml.j2'})

TASK [storage-readiness : Wait for Fcntl lock to be released] ******************
changed: [localhost] => (item={'name': 'file-lock-fcntl.yaml.j2'})

TASK [storage-readiness : Positive Fcntl test for readiness] *******************
changed: [localhost] => (item={'name': 'file-lock-fcntl.yaml.j2'})

TASK [storage-readiness : debug] ***********************************************
ok: [localhost] => {
    "msg": "######################## FILE LOCK TESTS PASSED FOR ReadWriteMany Volume #################################"
}

PLAY RECAP *********************************************************************
localhost                  : ok=109  changed=41   unreachable=0    failed=0    skipped=7    rescued=0    ignored=0
flock,fcntl pods :

oc get po -o wide  | grep readiness-file-lock
readiness-file-lock-fcntl-job-create-lock-r22jb                   0/1     Completed   0          5m17s   10.254.41.137   worker5.sre-chs-3m15w-ss-c627.cp.fyre.ibm.com    <none>           <none>
readiness-file-lock-fcntl-job-create-lock2-rktnn                  0/1     Error       0          4m45s   10.254.41.140   worker5.sre-chs-3m15w-ss-c627.cp.fyre.ibm.com    <none>           <none>
readiness-file-lock-fcntl-job-create-lock2-x9d28                  0/1     Error       0          4m56s   10.254.41.139   worker5.sre-chs-3m15w-ss-c627.cp.fyre.ibm.com    <none>           <none>
readiness-file-lock-fcntl-job-create-lock3-ll2fz                  0/1     Completed   0          3m59s   10.254.41.143   worker5.sre-chs-3m15w-ss-c627.cp.fyre.ibm.com    <none>           <none>
readiness-file-lock-job-create-lock-pj5gr                         0/1     Completed   0          7m45s   10.254.41.121   worker5.sre-chs-3m15w-ss-c627.cp.fyre.ibm.com    <none>           <none>
readiness-file-lock-job-create-lock2-6wmnq                        0/1     Error       0          7m14s   10.254.41.125   worker5.sre-chs-3m15w-ss-c627.cp.fyre.ibm.com    <none>           <none>
readiness-file-lock-job-create-lock2-kldhw                        0/1     Error       0          7m24s   10.254.41.124   worker5.sre-chs-3m15w-ss-c627.cp.fyre.ibm.com    <none>           <none>
readiness-file-lock-job-create-lock3-hdx2k                        0/1     Completed   0          6m28s   10.254.41.130   worker5.sre-chs-3m15w-ss-c627.cp.fyre.ibm.com    <none>           <none>
``

Tested on NFS, ODF and pods create-lock,create-lock2 are getting scheduled on same node as expected.

Merging Changes


text:
feat: kubectl exec support

Description of what you did:
Redirect kubectl exec commands to ! and make ! for internal plugin-to-plugin use only
Fixes #2117

My PR is a:

[ ] 💥 Breaking change
[ ] 🐛 Bug fix
[ ] 💅 Enhancement
[x] 🚀 New feature

Please confirm that your PR fulfills these requirements

[x] Multiple commits are squashed into one commit.
[x] The commit message follows Conventional Commits, which allows us to autogenerate release notes; e.g. fix(plugins/plugin-k8s): fixed annoying bugs
[x] All npm dependencies are pinned.

tests for kubectl exec?

covered by #2250

authors: ruanxianzhi starpit

repo: IBM/kui


text:
feat(IAM Identity): adding effective account settings

PR summary
new endpoint to get Effective account settings,
also has action control added to existing template calls.
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

Current vs new behavior

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

added screenshots of passing test cases :)

@pooraniss-ibm Could you please sign off on your commit?  That is the "DCO" failure in the list of checks for the PR.  To sign off on your commit, you could use the "-s" option on git commit.  More details here: https://github.com/IBM/platform-services-go-sdk/blob/main/update_service.md#7-open-pr-with-your-changes

:tada: This PR is included in version 0.66.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

authors: ibm-devx-sdk padamstx pooraniss-ibm

repo: IBM/platform-services-go-sdk


text:
Update nimbix trial instructions in Korean L10N

I can't read this but I updated the nimbix trial instructions to match the powerai-notebook version.
Should be the same here, but please review.

@changwoojung can you review this patch?

@changwoojung @stevemart  i've reviewed this PR and proposed new one with c8764074c428d4066d0d81c5eb77f18e375ce905
https://github.com/IBM/powerai-transfer-learning/compare/new_nimbix_ko...hongjsk:patch-1

@hongjsk thank you, i will use https://github.com/IBM/powerai-transfer-learning/pull/22 instead.

authors: hongjsk markstur stevemart

repo: IBM/powerai-transfer-learning


text:
obtain processing geography from cluster selector

Signed-off-by: SHLOMITK@il.ibm.com
This PR is related to https://github.com/IBM/the-mesh-for-data/issues/226

Extended the existing LabelSelector of m4dapplication by ClusterSelector which contains both the label selector and the cluster name of the running workload.
Removed processingGeography from the spec. It is received from ClusterSelector, using cluster metadata. If no cluster is specified in the selector, a local cluster is assumed and is read from the cluster-metadata config.
Removed a cloned selector from the blueprint. Not sure it is required at the blueprint level running in a remote cluster.
Minor changes to silence a lint checker.

@shlomitk1 you are making changes to the API.
Do we have a policy about backward compatibility? if not, can we define one? i.e., from which version whould we start being backward compatible? how do we manager versions?
@roee88 do we have these guidelines?

@shlomitk1 you are making changes to the API.
Do we have a policy about backward compatibility? if not, can we define one? i.e., from which version whould we start being backward compatible? how do we manager versions?
@roee88 do we have these guidelines?

We are not yet maintaining any backward compatibility, this is why the API is marked v1alpha1 (we're not special, that's what everyone else does).

repo: IBM/the-mesh-for-data


text:
how to use IDEA-CCNL/Erlangshen-TCBert-110M-Sentence-Embedding-Chinese

hi, I am wondering the usage of this model: IDEA-CCNL/Erlangshen-TCBert-110M-Sentence-Embedding-Chinese,
could you provide some example code and explanmantion?

hi, I am wondering the usage of this model: IDEA-CCNL/Erlangshen-TCBert-110M-Sentence-Embedding-Chinese, could you provide some example code and explanmantion?

hi, we are writing a paper and will release our codes and examples soon.

hi, I am wondering the usage of this model: IDEA-CCNL/Erlangshen-TCBert-110M-Sentence-Embedding-Chinese, could you provide some example code and explanmantion?

Hi, yyts, sorry to have kept you waiting.
We have released our paper and example codes for finetuning.
As for how to construct sentence embedding, you can refer to our paper.

authors: pskun yyht

repo: IDEA-CCNL/Fengshenbang-LM


text:
🛑 CN Org Home is down

In f12c612, CN Org Home (https://snapmaker.cn/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CN Org Home is back up in 3913f7e after 1 hour, 16 minutes.

repo: IDKHTS/upptime-demo

license: MIT


text:
Basics of DSA with Python

You can add some basic codes in Python like factorial, prime and perfect number , largest of three number, etc.
https://github.com/IEEE-WIE-VIT/WIE-WoC/tree/main/DSA Coding/Basics

hi i will do it

Go ahead

repo: IEEE-WIE-VIT/WIE-WoC


text:
Outdated three version causing problems with larger projects

Description 📝
Hello!
We're quite enthusiastic about using this library in our product, but we are encountering some issues while trying to set it up. We already use three separately from this library for a more generic 3D view, so there is a version conflict already when installing this library:

This can of course be solved by us downgrading our three version to the one this library uses, but we are not very happy with the idea of being locked out of bug fixes and updates because of it, and it also is a regressive change in terms of features and development time.
My question is - what is the maintenance strategy regarding this from your side? When can we expect three to be updated to a newer version? We understand it is not going to be immediately updated whenever a new version is there, we are also a bit behind, but aligning update cycles more closely would help us move forward with our integration.
Suggested solution 💡
Provide clarity and/or timeline in supporting new three versions
Alternative ⛕
No response
Additional context ☝
No response
Validations ✅

[X] Read the docs.
[X] Check that there isn't already an issue that requests the same feature to avoid creating a duplicate.

@tb-viktor our plan is to update the three.js version with each release (the next one is in the start of January). Keep in mind though that our release calendar is not necessarily the same as the three.js release calendar, so there might always be an offset in the versions. That said, we have defined three.js as a peer dependency, so if there are no breaking changes, everything should work even with that offset

@tb-viktor our plan is to update the three.js version with each release (the next one is in the start of January). Keep in mind though that our release calendar is not necessarily the same as the three.js release calendar, so there might always be an offset in the versions. That said, we have defined three.js as a peer dependency, so if there are no breaking changes, everything should work even with that offset

@agviegas have you managed to make any progress with this? January is almost over and so far the version has not went up 🙂

Hey @tb-viktor sorry for the late reply. We are a super small team, so we had to leave the issues on stand by for some time. After a huge update, now we are addressing them all. Three is now a flexible peer dependency, so this shouldn't be a problem in the future. Let us know if you face this issue again. Thanks!

authors: agviegas tb-viktor

repo: IFCjs/components


text:
imGuru crash on Big Sur

The app launch OK on Big Sur.  However, when you login and authenticated by Imgur, it will crash.  And then when you reopen again, it will crash again.

I didn't have this problem (imGuru v1.0.4 from the MAS on macOS 11.2.2).

Crash has not been found.
Closed outdated issue.

authors: JayBrown iKorich sdugoten

repo: IGRSoft/imGuru

license: mit


text:
🛑 Pilsudski Katalog Biblioteki is down

In 2608bf0, Pilsudski Katalog Biblioteki (http://www.pilsudskilibrary.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Pilsudski Katalog Biblioteki is back up in e6853d0.

repo: IJPNY/upptime


text:
Add confirmation before deleting a password

Before removing a password, prompt the user to confirm the deletion.

hi im interested to solve this issue , please assign me this issue

repo: IMGIITRoorkee/PwManager


text:
pinkhof maintenance

Resolved: pinkhof.ivdnt.org is back up in 4039e55 after 1 hour, 10 minutes.

repo: INL/ivdnt-statusoverzicht


text:
🛑 lexiconfrisicum.ivdnt.org is down

In b407105, lexiconfrisicum.ivdnt.org (https://lexiconfrisicum.ivdnt.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: lexiconfrisicum.ivdnt.org is back up in faa4d0e after 35 minutes.


text:
ネットワークモードの変更

外部からアクセスできるようにnetwork_mode: hostに変更する

こんな感じで、${ENVIRONMENT_VARIABLE:-'default_value'}
環境変数で引数を渡すことができます。
 network_mode: ${NETWORK_MODE:-'bridge'} のようにしてみてください。
https://github.com/IRSL-tut/irsl_docker_irsl_system/blob/main/files/docker-compose-win.yaml#L14
bridgeにすると挙動が変わらないと思います。

変更しました．
試したところシングルクオーテーションは不要でした．

authors: Hiroaki-Masuzawa YoheiKakiuchi


text:
BABCN-32 OpendataControllerTest

Algunos ensayos no pueden ser testeados hasta que los endpoints con paginación estén hechos. Bastaría con "descomentar" el comando adecuado en las líneas 218 a 220 e importar la clase DTO apropiada.
Ayer comentó al grupo que no podemos utilizar polimorfismo con los DTOs sin perjudicar el rendimiento. Y el lenguaje JAVA no tiene macros. La única solución se me ocurre para automatizar los ensayos sobre los DTOs cuando las clases ya no están relacionadas es usando métodos reflexivos.

Hum.... no recuerdo haber comentado lo que indicas al grupo. La utilización de polimorfismo nunca perjudica el rendimiento, ni en los DTO's ni en ningún otro objeto. Si no recuerdo mal, indiqué que emplear el polimorfismo puede traer problemas a la hora de aislar bugs en entornos productivos, y puede hacer complicado el seguimiento de errores, pero en ningún caso penaliza el rendimiento.

Hum.... no encuentro motivo por el cual BigMallsDto deba contener sus métodos public.

authors: R-Torrent jonatanvicente


text:
Авторизация через facebook

Пройти полную регистрацию приложения на facebook, чтобы добавить возможность авторизации.

Добавлен логин через fb.

authors: Jugastrov kovalevsky


text:
country borders are a little rough

I'm sending you data that's already too simplified, and then you're simplifying it even more. I need to fix this on my side first, then you. But maybe that would be too big a performance hit?
My simplification

Your simplification

I removed the my simplification, and it looks good now

authors: dtreich-itdp kauebraga

repo: ITDP/atlas


text:
[BlockSparseArrays] Use new SparseArrayDOK type in BlockSparseArrays

TODO:

[x] Get BlockSparseArray working with new SparseArrayDOK type. Seems to require an overload of getindex_notstored to construct a zero block matrix when accessing structurally zero blocks.

Other TODO items moved to #1250.

[test ITensors mps]


text:
🛑 Website is down

In f8c67f9, Website (https://pt.ivao.aero/portal) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Website is back up in 50ca382.

repo: IVAO-Portugal/status-page


text:
Commands and plugin not working on my server.

It doesn't do anything, I don't see an error. I'll check and reply back but I do not see one.
/door - "Command not found"
Plugin is inside of the Plugins folder in Rocket

Maybe, just maybe include your Rocket.log so anyone can actually help you?

authors: Trojaner VRPCaden

repo: IcePlugins/BreakAndEnter

license: WTFPL


text:
Add ApiUser object

Hi, this PR add new ApiUser object https://www.icinga.com/docs/icinga2/latest/doc/09-object-types/#apiuser

@scopenco 👍

authors: scopenco vkhatri


text:
Back button takes back to tutorial

Description
The app takes back to the last intro page after completing it.
What are the steps to reproduce this issue?

Install for the first time
After the introduction, press back

What happens?
Takes back to the intro.
What were you expecting to happen?
App should exit
What versions of software are you using?
App version: 0.1

Hi @manparvesh , I would like to work on this issue

@ikakus sure

authors: ikakus manparvesh

repo: IdeaTrackerPlus/IdeaTrackerPlus


text:
Authentication fails when app is run in a sub-path

Issue / Steps to reproduce the problem
I have created an IdentityServer derived app but removed the default MVC based UI and created a pure HTML/JavaScript UI that calls a WebApi for Login/Logout.
It works fine when run in VisualStudio and also under IIS in the root path, say http://localhost:5001.
Now I would like to run it in IIS in a sub-path, say http://localhost:5001/Test
but this fails after committing the login form.
Relevant parts of the log file
Here are two excerpts from the log files, one for the root path and one for the sub-path. I marked the lines where they start to differ.
This one is from a test in the root path that works
2017-05-19 02:18:10.459 +02:00 [Debug] Augmenting SignInContext
2017-05-19 02:18:10.498 +02:00 [Information] AuthenticationScheme: "Identity.Application" signed in.
2017-05-19 02:18:10.498 +02:00 [Information] User 'root' logged in.
2017-05-19 02:18:10.500 +02:00 [Verbose] returnUrl is valid
2017-05-19 02:18:10.500 +02:00 [Verbose] IsValidReturnUrl true
2017-05-19 02:18:10.518 +02:00 [Information] Executing ObjectResult, writing value "Microsoft.AspNetCore.Mvc.ControllerContext".
2017-05-19 02:18:10.544 +02:00 [Information] Executed action "RiaIdentityServer.Controllers.AccountController.Login (RiaIdentityServer)" in 1028.3367ms
2017-05-19 02:18:10.546 +02:00 [Information] Request finished in 1042.045ms 200 application/json; charset=utf-8
2017-05-19 02:18:13.550 +02:00 [Information] Request starting HTTP/1.1 GET http://localhost:5001/connect/authorize/login?client_id=RiaIdentityServer&redirect_uri=http%3A%2F%2Flocalhost%3A5001%2Fcallback.html&response_type=id_token%20token&scope=openid%20profile%20RiaIdentityServerApi&state=4f3a4a1935a04c0496e731cd7e2a8cb0&nonce=38e89e380da84418916f4c85acd57e6e
####### 2017-05-19 02:18:13.682 +02:00 [Information] HttpContext.User merged via AutomaticAuthentication from authenticationScheme: "Identity.Application".
2017-05-19 02:18:13.683 +02:00 [Information] AuthenticationScheme: "Identity.Application" was successfully authenticated.
2017-05-19 02:18:13.683 +02:00 [Debug] Request path "/connect/authorize/login" matched to endpoint type Authorize
2017-05-19 02:18:13.683 +02:00 [Debug] Mapping found for endpoint: Authorize, creating handler: "IdentityServer4.Endpoints.AuthorizeEndpoint"
2017-05-19 02:18:13.683 +02:00 [Information] Invoking IdentityServer endpoint: "IdentityServer4.Endpoints.AuthorizeEndpoint" for "/connect/authorize/login"
2017-05-19 02:18:13.690 +02:00 [Debug] Start authorize request (after login)
2017-05-19 02:18:13.690 +02:00 [Information] AuthenticationScheme: "Identity.Application" was successfully authenticated.
2017-05-19 02:18:13.691 +02:00 [Debug] User in authorize request: "83504cd2-0473-4b05-b57e-72f94dba6be2"
2017-05-19 02:18:13.692 +02:00 [Debug] Start authorize request protocol validation
2017-05-19 02:18:13.692 +02:00 [Information] AuthenticationScheme: "Identity.Application" was successfully authenticated.
2017-05-19 02:18:13.692 +02:00 [Debug] Calling into custom validator: "IdentityServer4.Validation.DefaultCustomAuthorizeRequestValidator"
2017-05-19 02:18:13.692 +02:00 [Verbose] Authorize request protocol validation successful
2017-05-19 02:18:13.692 +02:00 [Information] ValidatedAuthorizeRequest

This one is from the failed test with the app running in the sub-path:
2017-05-19 02:07:33.190 +02:00 [Debug] Augmenting SignInContext
2017-05-19 02:07:33.228 +02:00 [Information] AuthenticationScheme: "Identity.Application" signed in.
2017-05-19 02:07:33.228 +02:00 [Information] User 'root' logged in.
2017-05-19 02:07:33.228 +02:00 [Verbose] returnUrl is valid
2017-05-19 02:07:33.228 +02:00 [Verbose] IsValidReturnUrl true
2017-05-19 02:07:33.246 +02:00 [Information] Executing ObjectResult, writing value "Microsoft.AspNetCore.Mvc.ControllerContext".
2017-05-19 02:07:33.264 +02:00 [Information] Executed action "RiaIdentityServer.Controllers.AccountController.Login (RiaIdentityServer)" in 1197.9142ms
2017-05-19 02:07:33.267 +02:00 [Information] Request finished in 1212.6975ms 200 application/json; charset=utf-8
2017-05-19 02:07:33.275 +02:00 [Information] Request starting HTTP/1.1 GET http://localhost:5001/Test/connect/authorize/login?client_id=RiaIdentityServer&redirect_uri=http%3A%2F%2Flocalhost%3A5001%2FTest%2Fcallback.html&response_type=id_token%20token&scope=openid%20profile%20RiaIdentityServerApi&state=c940d0f5598b4087ad28e291f6d0388e&nonce=e8d14e6fe710456080df6af8f6018bb8
####### 2017-05-19 02:07:33.276 +02:00 [Information] "Identity.Application" was not authenticated. Failure message: "Unprotect ticket failed"
2017-05-19 02:07:33.276 +02:00 [Debug] Request path "/connect/authorize/login" matched to endpoint type Authorize
2017-05-19 02:07:33.276 +02:00 [Debug] Mapping found for endpoint: Authorize, creating handler: "IdentityServer4.Endpoints.AuthorizeEndpoint"
2017-05-19 02:07:33.277 +02:00 [Information] Invoking IdentityServer endpoint: "IdentityServer4.Endpoints.AuthorizeEndpoint" for "/connect/authorize/login"
2017-05-19 02:07:33.284 +02:00 [Debug] Start authorize request (after login)
2017-05-19 02:07:33.288 +02:00 [Error] User is not authenticated
2017-05-19 02:07:33.295 +02:00 [Verbose] Invoking result: "IdentityServer4.Endpoints.Results.AuthorizeResult"
2017-05-19 02:07:33.347 +02:00 [Verbose] Protecting message: "{\"Id\":\"541e482e7e6ffbecdae22cdd43636db0\",\"Created\":636307492533100205,\"Data\":{\"Error\":\"server_error\",\"RequestId\":\"0HL4U9C0Q8DLK\"}}"
2017-05-19 02:07:33.354 +02:00 [Information] Request finished in 78.9716ms 302
2017-05-19 02:07:33.359 +02:00 [Information] Request starting HTTP/1.1 GET http://localhost:5001/Test/error.html?errorId=541e482e7e6ffbecdae22cdd43636db0
2017-05-19 02:07:33.359 +02:00 [Information] Sending file. Request path: '"/error.html"'. Physical path: '"C:\inetpub\wwwroot\RiaIdentityServer\Test\wwwroot\error.html"'
2017-05-19 02:07:33.360 +02:00 [Information] Request finished in 1.1124ms 200 text/html

Here is the code from ConfigureServices:
    //Custom class that reads the clients/resources from a file
IIdentityServerConfig idsc = new IdentityServerConfig(Configuration);

services.AddIdentityServer(options =>
{
	options.UserInteraction.LoginUrl = "/api/Account/Login";
	options.UserInteraction.LogoutUrl = "/api/Account/Logout";
	options.UserInteraction.ErrorUrl = "/error.html";

})
	.AddTemporarySigningCredential()
	.AddInMemoryIdentityResources(idsc.GetIdentityResources())
	.AddInMemoryApiResources(idsc.GetApiResources())
	.AddInMemoryClients(idsc.GetClients())
	.AddAspNetIdentity<ApplicationUser>();

I currently have no idea how to further diagnose this issue. I can not debug it in Visual Studio because I don't have it running in a sub-path there.
I would appreciate any idea. Please let me know if more information or code is necessary.

After a couple more tests I found out that this is simply a cookie problem. First running the app in VS produces a cookie with the root path in it. Then running the same app in a sub-path under IIS leads to the mentioned problem. Deleting cookies fixes it. Sorry for reporting another seemingly bug that again turns out to be simply incompetence on my side ;-)

It also might be a casing issue -- keep in mind that URLs are case sensitive and that if the client has the wrong case, the browser might not send the auth cookie if the redirect URL is incorrect.


text:
Consider making client claims prefix value configurable

instead of boolean and default to "client_"

Done.

authors: brockallen leastprivilege


text:
🛑 Swila is down

In 5b4d8b1, Swila (https://swila.waithakasam.com) was down:

HTTP code: 502
Response time: 9360 ms

Resolved: Swila is back up in 98f47a5 after 27 minutes.

repo: IdrisFallout/upptime


text:
[WIP] Imrove metrics collection

Collect metrics to csv

Добавил графики с lowess аппроксимацией и доверительными интервалами. Иногда это работает нормально а иногда нет. Математику доразберу чуть позже.

repo: IgorErin/tokiobench


text:
[CLEANUP] Standardize names #1

This is a first pass of standardizing names.
The first commit renames the fields in the st_key_buffer_t struct to match our current vocabulary:
typedef struct
{
    st_key_action_t * const data;        // array of keycodes
    const int               capacity;        // buffer size (TODO: rename to capacity)
    int                     size; // number of current keys in buffer (TODO: rename to size)
    int                     current_head;     // current head for circular access
} st_key_buffer_t;```

Each commit will contain all the renames that fall out from fixing the names in everything defined in that header.

The second commit is a big one, because I renamed everything in the python generator, which really touched everything.
@kamih  I'm going to stop here to let you take a look. I honestly don't think any more changes should be made in this PR, except possibly re-renaming things, if you disagree with anything.
The one last bit of unfinished business is that we have a couple different names for the "right" side of a rule used internally in the generator. Sometimes it is referred to as a "transform", "transformation", or "output". I'm the one who used the "output" naming originally, and I will get rid of it, but I want to refactor most of that code, so I don't want to rename it yet, so that it sticks out. "Transformations" is your code. And "transformations", being the noun form of "transforms" is probably the most correct name, but we have frequently been taking advantage of the ability to "noun a verb" and using "transform" as a noun, and that is shorter.


text:
Overlapping parameters are passed to memcpy

I was playing around with libsais and Silesia corpus when I encountered a possibility for overlapping parameters passed to memcpy. This can happen precisely at libsais_reconstruct_compacted_lms_suffixes_32s_2k_omp libsais/src/libsais.c:3912.
Whether this causes problems or not, seems to depend on environment. In an environment where calls to memcpy are redirected to memmove this does not seem to cause problems and is only detected with AddressSanitizer. However in an environment where memcpy is actually utilized, this causes either a corrupted SA and/or segmentation fault, and is detected also with Valgrind.
I was able to isolate the part of the payload causing this error and wrote a minimal reproducer for it. Payload is a 32kiB block extracted from concatenation of Silesia corpus contents in alphabetical order.
How to use reproducer:
Compile with gcc -o reproducer -g -fsanitize=address reproducer.c libsais.c
Run with ./reproducer payload
If there is some information that I could provide additionally, please feel free to ask.

Hi @akiutoslahti, thank you for reporting this issue! I committed fix for it by switch from memcpy to memmove as you recommended. I did some some extensive fuzzing with clang libFuzzer and surprisingly were never able to hit this issue :(

@IlyaGrebnov No problem, happy to be of help! :)

authors: IlyaGrebnov akiutoslahti

repo: IlyaGrebnov/libsais