text:
model_downloader run failed

Bug report
Required information:

Operating system and version:
Ubuntu 20.04
OpenRMF installation type:
From source
OpenRMF version or commit hash
HEAD -> main
ROS distribution and version:
foxy
ROS installation type:
from binaries
Package or library, if applicable:

Description of the bug

download demo models  use  ros2 run rmf_building_map_tools model_downloader rmf_demos_maps -s airport_terminal
received error :

Could not parse cache file: /home/bing/.gazebo/models/! [Errno 21] Is a directory: '/home/bing/.gazebo/models/'Fetching page: 117
Fetching page: 118
Could not parse cache file: /home/bing/.gazebo/models/! [Errno 21] Is a directory: '/home/bing/.gazebo/models/'Fetching page: 119
Writing to cache: /home/bing/.gazebo/models/
Traceback (most recent call last):
File "/home/bing/rmf_ws/install/rmf_building_map_tools/lib/rmf_building_map_tools/model_downloader", line 11, in
load_entry_point('rmf-building-map-tools==1.5.1', 'console_scripts', 'model_downloader')()
File "/home/bing/rmf_ws/install/rmf_building_map_tools/lib/python3.8/site-packages/model_downloader/model_downloader.py", line 80, in main
download_models(map_dict[name], args.model_path, args.cache)
File "/home/bing/rmf_ws/install/rmf_building_map_tools/lib/python3.8/site-packages/building_map_model_downloader/building_map_model_downloader.py", line 122, in download_models
missing_models = pit_crew.get_missing_models(
File "/home/bing/rmf_ws/install/rmf_building_map_tools/lib/python3.8/site-packages/pit_crew/pit_crew.py", line 153, in get_missing_models
cache = build_and_update_cache(cache_file_path=cache_file_path,
File "/home/bing/rmf_ws/install/rmf_building_map_tools/lib/python3.8/site-packages/pit_crew/pit_crew.py", line 869, in build_and_update_cache
with open(cache_file_path, "w") as f:

Steps to reproduce the bug

build from source colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release
source source ~/rmf_ws/install/setup.bash
Download models using ros2 run rmf_building_map_tools model_downloader rmf_demos_maps -s airport_terminal
See the error displayed

Models: [] are used in crowd_sim
ERROR::pit_crew.load_cache():774: Could not parse cache file: /home/bing/.gazebo/models/! [Errno 21] Is a directory: '/home/bing/.gazebo/models/'
Cache found! Model count: 0

Expected behavior

model_downloader.py  line 80,  method download_models set wrong params,
building_map_model_downloader.py line 91,  method download_models definition incorrect, use wrong params value
Actual behavior

Screenshots

Additional information

Hello @mbb1234567890! Thanks for raising this issue, could you check if https://github.com/open-rmf/rmf_traffic_editor/pull/440 fixes your problem?

Hi aaronchongth ,  model_downloader.py line 24 defined default args "~/.gazebo/models/" for -m
parser.add_argument("-m", "--model-path", type=str,                     default="~/.gazebo/models/",                     help="Path to check models from and download models to")
https://github.com/open-rmf/rmf_traffic_editor/pull/440  will always to be "~/.ignition/fuel/" in building_map_model_downloader.py line 124
Is that right?

hello @mbb1234567890, I am not too sure what your question is. Are you perhaps unsure why these 2 model paths are defined?
building_map_model_downloader uses gz-fuel-tools  for model downloading, therefore we will need to collect the downloaded models from ~/.ignition/fuel after it has been downloaded, and we will then export it to wherever the user defined as --model-path.
The default value of --model-path is ~/.gazebo/models to accommodate the use of these models for gazebo classic, but users can define wherever they would like the models to be exported to.

Thanks , problem solved!

Apologies for closing the issue early, the fix, https://github.com/open-rmf/rmf_traffic_editor/pull/440, has just been merged in


text:
EasyFullControl API

This PR introduces an EasyFullControl API for users to initialize robots and set important API functions as callbacks. This provides an easy way of creating their own adapters and also prevents them from having to update the internals of their modified code manually when new changes are pushed.

@Yadunund Thanks for the comments, addressed them in the latest commit. Also added a Configuration class as suggested to store the parameters needed for initializing an adapter and fleet.

Closed, continuing on #235

source: gharchive/pull-request

license_type: permissive

license_source: github-api


text:
chore: add env var for pinning trace-based test tool version

Changes
Added an env var to make sure the same image version is used for the trace-based test tool. Currently the image version pin in the tracetesting/Dockerfile differs from the image version pin in the docker-compose.yaml.
Updated docs in this PR: https://github.com/open-telemetry/opentelemetry.io/pull/3526
Merge Requirements
For new features contributions please make sure you have completed the following
essential items:

[x] CHANGELOG.md updated to document new feature additions
[x] Appropriate documentation updates in the docs
[ ] Appropriate Helm chart updates in the helm-charts

Maintainers will not merge until the above have been completed. If you're unsure
which docs need to be changed ping the
@open-telemetry/demo-approvers.

I'm actually writing such a blog post right now. That's how I noticed the demo had an issue, and created this PR. 😄
I'll keep you in the loop on progress. 👌

Hi! Since the docs PR https://github.com/open-telemetry/opentelemetry.io/pull/3526 was merged, should we also merge this PR?

repo: open-telemetry/opentelemetry-demo


text:
docs: update README.md

Which problem is this PR solving?

formatting

Short description of the changes

Fixed README.md formatting

Checklist

[x] Ran npm run test-all-versions for the edited package(s) on the latest commit if applicable.

@blumamir, updated 👌

repo: open-telemetry/opentelemetry-js-contrib


text:
Lambda Layer Update - OTel Python 1.9.0 & 0.28b0

This PR updates the OTel Python Core dependencies to 1.9.0 and OTel Python Contrib dependencies to 0.28b0.

Also interested in this update (0.28b0 contrib). @vasireddy99 any chances of un-drafting and merging it soon?

repo: open-telemetry/opentelemetry-lambda


text:
Runs the processors before finishing the span

Hi 👋🏼
This Pull Request simply moves the processors call to the beginning of the finish() method.
Why?
Otherwise, you can't modify the span getting finished. Processors are run AFTER the span @ended variable
gets updated to true. Thus, the span is locked for changes.
Real use case
Suppose you want to add extra attributes to you spans on the way out the door.
Therefore, you can create a custom processor by implementing a child class of
OpenTelemetry::SDK::Trace::SpanProcessor and overriding the method on_finish().
This method receives the span getting finished and you can then add new attributes, right?
Not exactly, cause by calling add_attributes you receive an error: Calling add_attributes on an ended Span.
Whit that, my personal assumption is that you can not do anything useful inside on_finish() method
of a custom Processor cause the span will always be @ended when this method is called.
The changes
This PR makes the span finish() method to iterate calling every Processor BEFORE actually ending
the span. It will allow processors to modify spans before actually finishing it.
Other argument: on_start method
If you look at the way this Span class calls on_start method, you will see it being the last thing in the
initialize() method. That makes sense, we first create the span, then we call each processor for that particular span.
The on_finish() method should do the opposite: run processors FIRST, then finish the span. Does it make sense?
Considerations
Please, let me know in case you folks think I should do something else for this PR.

Heavy 👎
This change does not conform to the specification. Modifying the span in the onEnd/on_finish method is not permitted.
See https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/sdk.md#onendspan
There is a new OnEnding option that SDKs can implement which runs before OnEnd, and which allows spans to be modified. This is what should be implemented in the Ruby SDK to achieve your need.
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/sdk.md#onending

Just quickly chiming in, tldr this is a limitation of the spec. You bring up valid practical considerations (which I agree with the spirit of!) but we are beholden to the specification that states spans have to be ended before being passed into onend
https://opentelemetry.io/docs/specs/otel/trace/sdk/#onendspan
Looks like there's the concept of "onending" that sortve is what you're looking for, but it's in "development" within the spec https://opentelemetry.io/docs/specs/otel/trace/sdk/#onending
, so I'm not sure what the path forward is there for Ruby.
Some of the more knowledgable folks and maintainers here can provide better context with the precise language on why this is working as intended, and suggested workarounds (monkeypatch the sdk itself, some sort of cloning of spans, etc) or path forward.

"in development" means the spec is brand new and may still change, in which case the SDKs would have to change too.
Nothing prevents ruby from adopting this part of the spec right now.

Thank you @dmathieu for all the clarifications. I totally agree with everything you have mentioned.
And thankfully, the new Spec seems to solve the issue I have tried to report.
Do you folks mind if I try to implement the new Spec? Is there anyone working in such thing already?

Hi @pantuza! We'd love to have you work on it! I created https://github.com/open-telemetry/opentelemetry-ruby/issues/1695 to track this work. Please comment on the issue so I can assign it to you.
We've talked about this new feature in the SIG, but no one is working on it AFAIK. Let us know if you need any help 🙂

I am closing this PR since, based on the suggestion made here, I have opened another Pull Request (#1713) addressing the Open Telemetry Spec.

authors: dmathieu ericmustin kaylareopelle pantuza

repo: open-telemetry/opentelemetry-ruby

license_source: bigquery


text:
fix: BatchSpanProcessor should not spawn a thread during app boot for forking webservers

BatchSpanProcessor should not spawn a thread during app boot for forking webservers (passenger puma rainbows unicorn)
I have added code which detects the webserver. You can also set it explicity with OTEL_DISPATCHER env var.
Fixes #462
TODO:

[ ] determine where to put DispatcherDetector (i.e. which namespace)
[ ] add tests to DispatcherDetector after approach is confirmed by code reviewer

@johnnyshields can you please sign the CLA? This is blocking all your PRs at the moment.

@fbogsany please check how I've set it up now. @dazuma @ericmustin your comments are also welcome.
I think we have a philosophical decision to make here. Do we want the OTEL SDK to do auto-detection to "do the right thing" in 95% of cases? Or do we want to take a "configuration-over-convention" approach?
Personally I think there should be an aspect of "user-service" in the SDK, which is the approach other widely-used telemetry vendors have taken in their SDK libs...

My strong preference is to favour configuration. The span processor has to be configured in code at present, so asking the user to decide whether to start the BatchSpanProcessor export thread eagerly seems pretty reasonable.
Our approach to "auto-configuration" at Shopify is to provide a wrapper gem that pulls in "blessed" auto-instrumentation gems and sets up the span processor and exporter with sane defaults according to the environment (dev, prod, CI). Our apps then add just this gem to their Gemfile.

@johnnyshields @fbogsany . First off let me just say that I think this is very thoughtful, well done work, and very much appreciated. And what this PR addresses is, I agree, useful. That being said, I do think this has a little more brittleness than i'd prefer, and I think the maintenance burden here feels like a long tail of edge cases. The configuration-over-convention approach seems to solve a lot of that brittleness (probably not the right word here because I think this is very well written code) while preserving the original intention of your PR, the tradeoff being it requires more thought from a user.
But, i'm ok with that? It's not unreasonable that user should be familiar with their webservers behavior. I agree with you that widely used telemetry vendors for Ruby optimize for "up and running in seconds" far more than OpenTelemetry-Ruby, but, that's sort've the point, vendors optimize for some things that i'm not sure opentelemetry-ruby-sdk should care as strongly about? And given that users are already having to modify application code to set the batch span processor, changing this config doesn't sound unreasonable to me.
Just my two cents, i am certainly not the cosmos here.

We should make it easy for people to adopt this gem. Should be aiming for 5,000 Github stars in 12 months--we're at 80 now.
I'd venture to say that Puma, Unicorn, and Passenger together have at least 80%+ share of Ruby webservers. The gem should know to "do the right thing" for 80% of the users.
I do not consider this code "brittle", because it only "enhances" behavior for the webservers which benefit from it, and otherwise gracefully degrades to spawn-thread-on-boot.

Should be aiming for 5,000 Github stars in 12 months--we're at 80 now.

I don't think this is an explicit goal for us.

Sure--I'd like to encourage the maintainers to think about what gets developers to actually adopt software libraries. One should be able to add the gem and with minimal effort start tracing--that's the selling point of NewRelic, Skylight, etc.

To over simplify the PR (maybe a bit too much), this appears to be whether or not we should embed configuration inside the SDK or not.
So far the SDK tries not assume anything about the application that consumes it and instead it exposes the ability to configure it.
Any library specific instrumentation is carved off into its own gem, and we leave that as something we support but is ultimately optional.
I would like to see us continue that approach going forward, and avoid embedding any config directly inside of the SDK.

SDK tries not assume anything about the application that consumes it and instead it exposes the ability to configure it
While everything should be open to configuration, here I'm propose the SDK should do a modest amount of "auto-configuration" based on what it can easily detect to handle 80%+ use cases. This is what other telemetry libs do.

Any library specific instrumentation is carved off into its own gem
This PR isn't about instrumentation, it's about running the exporter correctly given the runtime we're operating in.

avoid embedding any config directly inside of the SDK.
So we're going "configuration over convention". Great...

Closing in favor of https://github.com/open-telemetry/opentelemetry-ruby/pull/472

authors: ericmustin fbogsany johnnyshields robertlaurin


text:
[wip]: Add config improvements

Summary
WIP, but meant to address:

[x] https://github.com/open-telemetry/opentelemetry-ruby/issues/904
[ ] https://github.com/open-telemetry/opentelemetry-ruby/issues/903
and possibly while i'm in here
[ ] https://github.com/open-telemetry/opentelemetry-ruby/issues/898
[ ] https://github.com/open-telemetry/opentelemetry-ruby/issues/899

Originally some of this work was in https://github.com/open-telemetry/opentelemetry-ruby/pull/946 but i made a new branch based on top of it that includes only the config specific code.
Notes
This PR is an attempt to clean up a bit the way we handle configuration options in instrumentation. It does this by

Establishing a constant on the instrumentation-base and -<subclasses> that is opt-in for storing all configuration option entries (name, default, validator), as well as storing all deprecated configuration options. This will allow us to have a canonical home for the valid configuration options of an instrumentation without needing to instantiate an instance of it. This ought to make it easier to track config options over time, document them, deprecate them, and so on.
Add convenience methods to -instrumentation-base class for both generating a hash of all default options for the subclass and also applying that hash as options. The idea would be to add these helpers and then migrate individual instrmentations to this approach in a followup PR. For now, only http.rb instrumentation is using it as an example.
Add environment variable support for all instrumentation configuration options (excluding callables). This uses the syntax OTEL_RUBY_INSTRUMENTATION_<INSTRUMENTATION_NAME>_<INSTRUMENTATION_OPTION_NAME>. For ex: OTEL_RUBY_INSTRUMENTATION_HTTP_HIDE_QUERY_PARAMS=false. These environment variables take precedence at runtime over local configuration, this PR also include heuristics for coercing them to the appropriate validate types (boolean, integer, array, string).
An easy storage and checking mechanism for determining whether a config option that's being used is deprecated. This is largely just a skeleton still but i'm open to ideas of what we want to expose, in my mental model right now there would be perhaps a list of deprecated options, as well as the ability to either warn (via a log line, this would be default behavior)  or raise (via an exception, in cases where a config option was potentially doing something very bad like causing a memory leak or what have you).

Anyway, PR was getting kinda chunky so wanted to push it up, it's only being used by the http instrumentation but after we get agreement on a form/syntax/etc it would be easy (and can be done in followup prs) to migrate the other instrumentation over, and then once everything is migrated it would be pretty straightforward to add some rake tasks that generate documentation of config options per instrumentation auto-magically.

Here's a convenience diff of only the Environment changes with the changes from #946 excluded.

authors: ericmustin robbkidd


text:
Process semconv: define common attributes and revisit requirement levels

Area(s)
area:process
Is your change request related to a problem? Please describe.
We require any of the following attributes to be present
https://github.com/open-telemetry/semantic-conventions/blob/a04a1f4ba413d0a1f137c223fc243ea14fdcd89b/docs/resource/process.md?plain=1#L39-L45
As a result, users would get inconsistent data from different systems and instrumentations.
Vendors will need to know how to parse and extract specific details (such as process name).
Describe the solution you'd like
The approach we follow in HTTP and other semconv:

Find 1-2 required attributes (e.g. process.executable.name) which are available everywhere
Require instrumentations to do the parsing/extraction of this common information so that users and consumers would get consistent data
Set appropriate requirement levels on other attributes

cc: @open-telemetry/semconv-system-approvers

source: gharchive/issue

authors: ChrsMark lmolkova

repo: open-telemetry/semantic-conventions


text:
Delete create button miUchile

Se oculta el botón de miUchile para la vista de creación de cuenta con le objetivo de evitar el aumento  de tickets en la mesa de ayuda

@catalinaIlabaca por favor hacer squash de los 2 commits en uno para hacer el merge con merge-commit.

authors: catalinaIlabaca fsologureng

repo: open-uchile/open-uchile-theme

license: MIT


text:
XTokens refactor

Unified events so there is only one to deal with
Not allow zero amount because apparently it is not allowed https://github.com/paritytech/polkadot/issues/4996

Codecov Report

Merging #706 (7bb244c) into master (f8f6f82) will increase coverage by 0.28%.
The diff coverage is 84.48%.

@@            Coverage Diff             @@
##           master     #706      +/-   ##
==========================================
+ Coverage   74.70%   74.99%   +0.28%
==========================================
  Files          83       83
  Lines        7282     7266      -16
==========================================
+ Hits         5440     5449       +9
+ Misses       1842     1817      -25

Impacted Files
Coverage Δ

xtokens/src/lib.rs
61.32% <75.00%> (+3.64%)
:arrow_up:

xtokens/src/tests.rs
99.20% <100.00%> (+0.03%)
:arrow_up:

Continue to review full report at Codecov.

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

authors: codecov-commenter xlc


text:
enh: admin password reset env var

#1953

@tjbck I was hoping to take a look at this one. Are you thinking that the environment variable would determine whether the password reset token would force the users to create a new password? If true, forcing reset on next login with token.
ForceNewPWOnAdminReset:True

authors: WaltersAvenger tjbck

repo: open-webui/open-webui


text:
remove root password from images

Currently our KIWI images set a fixed root password. We should not do this.
DISCLAIMER: @cyphar and I weren't sure whether this commit will really fix the issue. There is the possibility that KIWI somehow generates a random password somewhere independent of this configuration file. In that case we might have to patch KIWI if we really do not want any root password at all. Another thing is that KIWI by itself does not create a root user if not instructed to do so. Hopefully removing the password will still leave the creation of a root user intact. If not we must revert.
Signed-off-by: Christian Brauner cbrauner@suse.com

I did a local build with the a modified openSUSE-Tumbleweed config.kiwi file that removes the password section via:
sudo kiwi -build openSUSE-Tumbleweed -d /tmp/img --set-repo http://ftp5.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ --add-repo http://ftp5.gwdg.de/pub/opensuse/tumbleweed/repo/non-oss/
and imported the resulting tar using:
cat openSUSE-tumbleweed-docker-guest-docker.x86_64-1.0.3.tar.xz | sudo docker import - no_root
When running a container from the imported image with the command
docker run -it --rm no_root bash
the root user was present, the home directory set and the password for the root user unset.

I have not tested it but LGTM code-wise.

authors: brauner tboerger

repo: openSUSE/docker-containers

license: mit


text:
Hospitalisation values BE

Hospitalisation values of BE from https://www.besondere-lage.sites.be.ch/de/start/news/fallzahlen.html are atm not harvested.

have they been, and from which source?
values have got asterisks attached, might that be an issue?

Thanks for further analysing the issue, and proposing how to deal with this.

Here is the code:
https://github.com/openZH/covid_19/blob/a2aadd6bb20655aab204c3f677e7b0d627207e91/scrapers/scrape_be.py#L26-L29
i.e. an asterisks indicates and non-current value and is ignored.

Many thanks, so "is ignored" means, that:
a. the asterisk is ignored, and values would be scraped or
b. values with asterisks are ignored, and not scraped?

Many thanks, so "is ignored" means, that:
a. the asterisk is ignored, and values would be scraped or
b. values with asterisks are ignored, and not scraped?

b.

authors: andreasamsler metaodi


text:
Retail Location Data

We work with distributing retail locations. Is this acceptable? How should it be handled?

How are the latitude and longitude of the retail locations captured? If their addresses are run through a geocoder to get the lat/lon, then we can't really use it in our data set.

In most cases, we manually look up the locations and drop pins on the
building (rather than the curb).
On Fri, Jul 31, 2015 at 10:55 AM, Ian Dees notifications@github.com wrote:

How are the latitude and longitude of the retail locations captured? If
their addresses are run through a geocoder to get the lat/lon, then we
can't really use it in our data set.
—
Reply to this email directly or view it on GitHub
https://github.com/openaddresses/openaddresses/issues/1111#issuecomment-126751042
.

If you have rights to the data, I'd certainly be interested in seeing how it could be added to OA. Do you have a sample you can share?

authors: iandees rhaussmann sbma44

repo: openaddresses/openaddresses


text:
Colorado  Commerce City fix url

unsure if this is the actual error but the city_of_commerce_city has had an error since December.
seems to be just httpS://
Not working
http://maps.c3gov.com/arcgis/rest/services/OpenData/Address/MapServer/0
BUT Works
https://maps.c3gov.com/arcgis/rest/services/OpenData/Address/MapServer/0

Commerce City looks to have changed the schema of their data and now list Street Name as having all DEPRECATED as a value and then the actual street name is in Complete Street Name. Not sure on the methodology behind their change but is there a way to pull that Complete Street Name column instead of Street Name


text:
provide device kwarg, and fix f-string incompatibility for py<3.8

[1] I notice that for matmul and softmax we should provide an device kwarg, otherwise it may raise error because device is missing. So I add device="cuda" for the benchmark script.
[2] I also find that, in test_core.py, you use a new feature which is not supported by a low version python. You use f-strings support =, which is available only for python>=3.8. To be compatible with low versions, I remove this new feature, and just use the plain f-strings instead.

Thanks! The bench directory hasn't been touched for a while, and they have been replaced by regression tests in the CI (though blocksparse hasn't been ported yet).

repo: openai/triton


text:
"First Agent" Failed on Ubuntu 16.04

I'm connected to my host via VNC (port 5905)  for a GUI.
'First Agent' failed and I follow the suggest, run container by hand:
$ docker run -p 5900:5900 -p 15900:15900 --cap-add SYS_ADMIN --ipc host --privileged quay.io/openai/universe.flashgames:0.20.4
It also failed with :
Setting VNC and rewarder password: openai
[Thu Dec 22 00:54:46 UTC 2016] Waiting for /tmp/.X11-unix/X0 to be created (try 1/10)
[Thu Dec 22 00:54:46 UTC 2016] [/usr/local/bin/sudoable-env-setup] Disabling outbound network traffic for none
Traceback (most recent call last):
    File "/app/universe-envs/flashgames/init", line 262, in <module>
    sys.exit(main())
    File "/app/universe-envs/flashgames/init", line 243, in main
    setup_logdir(recorder_logdir)
    File "/app/universe-envs/flashgames/init", line 119, in setup_logdir
    os.makedirs(path, exist_ok=True)
    File "/usr/lib/python3.5/os.py", line 226, in makedirs
    head, tail = path.split(name)
    File "/usr/lib/python3.5/posixpath.py", line 103, in split
    i = p.rfind(sep) + 1
    AttributeError: 'NoneType' object has no attribute 'rfind'

It seems something is wrong inside the docker container. How should I fix it?

It's fixed in the latest release of the container. Update the version number in the docker run command to  quay.io/openai/universe.flashgames:0.20.15

the docker is up and vnc connection is ok. I'll try the 'First Agent' again.

repo: openai/universe


text:
[AutoPR azure-iot-deviceupdate] add sample readme.typescript.md

Create to sync https://github.com/openapi-env-test/azure-rest-api-specs/pull/3120
You can install the use using pip install of the artificats.

API change check for azure-iot-deviceupdate
API changes have been detected in azure-iot-deviceupdate. You can review API changes here

repo: openapi-env-test/azure-sdk-for-python


text:
Redfish: LEDs (system, chassis, fan, power supply LEDs)

Dev https://github.com/ibm-openbmc/dev/issues/287

[ ] https://gerrit.openbmc-project.xyz/#/c/openbmc/openbmc-test-automation/+/25900/

repo: openbmc/openbmc-test-automation


text:
[REQUEST] JA3 Spoofing

Hi, I'm wondering if it is possible to add a custom ja3 spoofing feature which would allow the user to use a custom ja3 fingerprint in the request block.

You could try using something like this https://github.com/Carcraftz/TLS-Fingerprint-API and make the request directly to this local "proxy", which will make the request for you and return the valid cookies.
Otherwise, you could try to use Linux/MacOS with the latest openssl library, and then in the request block set 2.0 as HTTP version, SystemNet as library, TLS 1.3 as security protocol, and enable custom cipher suites. Also watch out for the order of headers, you should follow Firefox's order since the default cipher suites I put are from Firefox.

You could try using something like this https://github.com/Carcraftz/TLS-Fingerprint-API and make the request directly to this local "proxy", which will make the request for you and return the valid cookies. You can even pass it a proxy to use.
Otherwise, you could try to use Linux/MacOS with the latest openssl library, and then in the request block set 2.0 as HTTP version, SystemNet as library, TLS 1.3 as security protocol, and enable custom cipher suites. Also watch out for the order of headers, you should follow Firefox's order since the default cipher suites I put are from Firefox.

Is it really only possible to generate a good ja3 fingerprint on linux/macos? TLS-Fingerprint-API is alright but it decreases speed a lot more and sometimes fully stops working until restarted.
Im wondering if there is a way to generate a good ja3 fingerprint or just a random one using windows OB2

It's only possible because Windows uses SChannel as default TLS provider for the TcpClient that I use in the library. I would need to add BouncyCastle as TLS provider or something like this to make it work on Windows. I have plans to do it but it will take time.

Cool, so for now using linux/macOS for proper ja3 fingerprint generation is the only way.
I hope you can add bouncycastle soon because ja3 is being used more and more. Almost every anti bot security uses ja3 to fingerprint devices making it harder to automate tasks without using selenium or puppeteer.

Hey Ruri, any new update to this request? It is really hard to make configs since, almost every site added ja3 to detect from where the requests are comming.

Hi, sorry I don't really have time to code as of late because of my job.

unfortunately Using OB2 is becoming outdated cz it can't bypass the new Securities so adding such libraries
https://github.com/Danny-Dasilva/CycleTLS
to the main functions and BLOCKS of OB2 become necessarily.

so also my voice  -  easy ja3 fingerprint for windows...


text:
[BUG] KeyCheck for errors

So, I have a service im trying to pentest. Now the problem is that the "redirect_url" redirects to an url that can only be used on a phone. (a special url like for example "magnet:")
OpenBullet interprets that as an IP and tries to connect. Which then throws the error
"ERROR: Specified argument was out of the range of valid values.
Parameter name: port"
Is there a way to ignore errors and do the keycheck anyways?
I tried editing the redirect_url but the service doesnt allow it (security reasons)
EDIT: Nevermind. I was using the anomaly version. "Ignore Response" option doesnt work well there.

Sorry, OB1 is not supported anymore, please switch to OB2.

repo: openbullet/openbullet


text:
Multi Content Annotations

This supercedes #387.
TODO before this is ready for merging
Organizational

[ ] This includes #443, which we might not want in master in it's current shape. A proper solution is needed here.

QA

[ ] This needs another round of reviews. A lot of this code was written under time pressure and/or with incomplete information. We won't get it perfect, but I want to at least see if we can't throw out some of the more grievous smells.

[ ] Note that #387 already had a review, and some of the comments remain unaddressed. You should incorporate these here.

[ ] This PR currently fails CI because of test failures. These stem from changes in the API which the tests haven't been adapted to.

Bugs

[ ] The CSV export still works, but doesn't understand MCA, yet, so it outputs mostly garbage.
[ ] The Excel export and the print view don't work at all anymore.

(Missing) Features

[ ] Questionnaires

[ ] Manage questionnaires per Opencast even/series
[ ] Questionnaire creator

Closing again. How all of this is going to make it's way back into master is not clear, yet. I pushed everything to the questionnaire branch for now.

repo: opencast/annotation-tool


text:
No Opencast Series & Episode on Adding a new Video (Opencast) Activity Page

Hi @mtneug and Team.
We are using docker-compose/docker-compose.allinone.mariadb.yml Docker compose file (version 16.4), and it is running on Docker Swarm Cluster.
The series and events (episode) can be successfully added / uploaded via Moodle (version 4.3) site (there are now: Course_Series_99 and Course_Series_100), and those episodes can also be played both on Opencast studio/player and via embedded way.
Moodle Opencast Videos Page

Opencast Events & Series Page

Known Issue

But the are NO series and episodes appear on the menu provided on Adding a new Video (Opencast) Activity page.
Needs help and suggestions.
Thank you in advance.

Is this the course where the Moodle block was added? What publication channel did you configure for the activity plugin?
In general: this seems to be a configuration issue with the Moodle plugins and not related to the Opencast container images.

I just created an example compose setup for Opencast + Moodle in this repository: https://github.com/opencast/community-integrations/tree/main/lms This is not a production example, but it might help you figure out your problem.
I will close this issue for now.

authors: andisugandi mtneug

repo: opencast/opencast-docker


text:
Metadata to ACL Operation

This patch adds a metadata-to-acl workflow operation which can be used
to automatically add access rights for users mentioned in metadata
fields to the access control list.
The operation works like this:

Get values for configured field from the episode Dublin Core catalog
Look up if a user with this username exists
Add read and write permissions for this user

Your pull request should…

[x] have a concise title
[x] close an accompanying issue if one exists
[x] be against the correct branch
[x] include migration scripts and documentation, if appropriate
[x] pass automated tests
[x] have a clean commit history
[x] have proper commit messages (title and body) for all commits

Added another sentence mentioning this. Now it's in both the general description and in the description how this works.
The admin interface's behavior is actually pretty strange, since it presents the username to the user but seems to replace it in the backend so that the metadata value has changed when you next come back to the interface. But, I guess, that's a different issue.

repo: opencast/opencast


text:
I am having problems in installation while setting up the project.

Unable to install package pygrib.
Error contains:
eccodes not found which I installed using conda.
Microsoft Visual C++ 14.0 or greater is required. which also I have installed.
--proof:

Here is the complete error:
Building wheels for collected packages: pygrib
  Building wheel for pygrib (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for pygrib (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [23 lines of output]
      eccodes not found, build may fail...
      running bdist_wheel
      running build
      running build_py
      creating build\lib.win-amd64-cpython-311\pygrib
      copying src\pygrib\__init__.py -> build\lib.win-amd64-cpython-311\pygrib
      running build_ext
      <string>:18: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
      !!

              ********************************************************************************
              Requirements should be satisfied by a PEP 517 installer.
              If you are using pip, you can try `pip install --use-pep517`.
              ********************************************************************************

      !!
      C:\Users\Lenovo\AppData\Local\Temp\pip-build-env-mn706q2z\overlay\Lib\site-packages\Cython\Compiler\Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: C:\Users\Lenovo\AppData\Local\Temp\pip-install-oyr7x6e1\pygrib_df6a9faaa73c4c9989f7dd1248ac782d\src\pygrib\_pygrib.pyx
        tree = Parsing.p_module(s, pxd, full_module_name)
      warning: src\pygrib\_pygrib.pyx:358:12: Unreachable code
      Compiling src/pygrib/_pygrib.pyx because it changed.
      [1/1] Cythonizing src/pygrib/_pygrib.pyx
      building 'pygrib._pygrib' extension
      error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for pygrib
Failed to build pygrib
ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (pygrib)

Try removing geopandas and see if that works?

@peterdudfield Thanks for taking time to propose a solution to my issue but it still gives the same error.

you could run this in docker? Some other solutions here - https://stackoverflow.com/questions/35640117/installing-pygrib-package

Any luck?

@peterdudfield unfortunately no, I am thinking of using a virtual machine now, what do you suggest?

or use docker

authors: Sahil-Chhoker peterdudfield

repo: openclimatefix/analysis-dashboard


text:
feat(Autocomplete tags): Add CollectiveTagStats materialized view and extend tagStats query to use it

API for https://github.com/opencollective/opencollective/issues/5523
Adding a CollectiveTagStats materialized view with Collective tag counts, and extending the current tagStats query to use it when there is no searchTerm provided (which is an existing argument to return tags for collectives that match that search term).
The PR is also adding an tagSearchTerm argument to tagStats, so that it can be used in an autocomplete tag input field to find matches to what you are currently typing in.
Considerations

The CollectiveTagStats view is for all Collective types ('COLLECTIVE', 'USER', 'EVENT', 'ORGANIZATION' etc).

An argument could be made that we could group the view by type, and when querying the tagStats you specify which type to be returned, to avoid having the "user" tag pop up when creating a Collective.
However, this is currently solved by having an ignored tags array (["community", "user"]) in the frontend, and this seems like a good enough and simpler approach. In addition:
The current tagStats query is looking at all types, so it is convenient to have them all in the view as well, to be able to use the materialized view in the initial load of the search page.

We might want another similar materialized view grouping the tag counts by host, to be able to show popular tags specific to that host in the application process.

Maybe there a way to combine those into one view, grouped by host, with the caveat that the records grouped by a null host field includes data from hosts, to easily get the standard view.

We might want another similar materialized view grouping the tag counts by host, to be able to show popular tags specific to that host in the application process.

Maybe there a way to combine those into one view, grouped by host, with the caveat that the records grouped by a null host field includes data from hosts, to easily get the standard view.

Here's a query/view would achieve this. Perhaps something to include from the beginning to avoid another migration? Maybe together with an index on HostCollectiveId.
SELECT tag, count, null AS "HostCollectiveId"
FROM (SELECT DISTINCT unnest(tags) AS tag, COUNT(*) AS count FROM "Collectives" GROUP BY tag) AS AllTags

UNION

SELECT tag, count, "HostCollectiveId"
FROM (SELECT DISTINCT unnest(tags) AS tag, COUNT(*) AS count, "HostCollectiveId" FROM "Collectives" WHERE "HostCollectiveId" IS NOT NULL GROUP BY tag, "HostCollectiveId") AS HostTags

ORDER BY count DESC

On second thought I think it makes sense to wait a bit with adding host tag frequencies to this view until we are 100% sure we will use it. This PR together with an autocomplete tag input in the frontend will be a nice first step.

Backtracking my backtrack and added the tag counts per host to the materialized view in this PR, since I'll be using that in the frontend to show popular tags for the host in the application form.

repo: opencollective/opencollective-api


text:
Track Tiers history

On a few tables, we're tracking the whole history of modifications (Collective, Expense, Order, Subscription).
We need to activate that for Tiers, it will would be really useful for troubleshooting.

A $50 bounty was attached to this issue. Anyone submitting a Pull Request will be rewarded with $50 when the Pull Request is reviewed, accepted and merged. More info
This bounty is currently reserved to participants of the OSCA (Open Source Africa) event. If not completed there, it will be later open to everyone.

I am michael from OSCPH and i want to work on this issue

Hello @znarf Can I please get a hint on how to go about this?

Look at the models https://github.com/opencollective/opencollective-api/tree/master/server/models
And try to understand why have history enabled on Collective and not on Tiers.

I came across this - https://www.npmjs.com/package/sequelize-historical
Please do you think it might help me gain some understanding of the stated above

Yes, this is the package we're currently using.

This bounty is now opened for everyone.

🏆 This issue was completed by @NotJohs
To claim the bounty, you can either:

Submit an invoice to https://opencollective.com/engineering/expenses/new (please mention the issue number in the expense's title)
Or ask for an Open Collective gift card of the same value (to donate to other collectives)

authors: Sokan93 mikkidollar znarf

repo: opencollective/opencollective


text:
Expenses list: add buttons to process expenses

:art: Design: https://www.figma.com/file/ZQBMWhnGGtRWeIZknFW1eP/[OC.com]-Production-Ready-✅?node-id=1120%3A19272
We want to add the buttons to process expenses (Pay, Approve...etc) on the expenses list.

Did design resolve the issue where this is starting to become redundant with the host dashboard?
In order to pay expenses from this screen, you need a way to review expense details (attachments, comments, payment method), otherwise it's not functional for the host admin. But if you add those things, it's super crowded and also basically the host dashboard.
@Memo-Es you and I discussed focusing the design for this view on the other users besides the host admin. So info and actions for the public, the expense submitter, and the Collective admin. I think that design focus could help optimise this view, while we focus everything for host admins on the host dashboard.

@alanna there are two different designs for this component (one for the expenses list and one for the host dashboard). The one presented here is indeed more suited to collective admins.
@Memo-Es let me know if you want to integrate some of the feedback from @alanna before we start the implementation

We designed 2 different versions of this component depending on the context:

Public Collective's budget page
Fiscal host dashboard

- Accesible by normal users and admins
- Accessible only by admins

Try me 👉Behaviour test

This component update is included in the latest design system update #3209
@alanna @Betree

Thank you @Memo-Es This looks great.

authors: Betree Memo-Es alanna piamancini


text:
Rejecting a contribution removes contributor from contributor list

Describe the bug
Contributors with a single rejected contribution are removed from the Contributors list despite having previous (accepted) contributions.
To Reproduce
Steps to reproduce the behavior:

Go to Collective
Contribute twice
Reject a contribution as an admin
... profit

Expected behavior
The contributor should appear int he contributor list if they have valid, accepted contributions to a Collective.
Additional context
This is currently evident on https://opencollective.com/biojulia who have been rejecting all contributions. For example, Sabrina Ward (https://opencollective.com/biojulia/transactions?offset=15) is no longer on the contributor's list despite contributing in the past.
P4 low frequency, low impact

Working as expected I would say.

authors: BenJam znarf


text:
Remove dependency on KNE and update ondatra dep.

kne depends on metallb, and metallb has this issue where it imports something it's not supposed to:
https://github.com/metallb/metallb/blob/v0.13.5/go.mod#L174
This causes consumers of lemming to experience this:
~/gocode/src/github.com/openconfig/gribigo> go mod tidy
go: finding module for package github.com/openconfig/lemming
go: found github.com/openconfig/lemming in github.com/openconfig/lemming
v0.1.0
go: github.com/openconfig/lemming@v0.1.0 requires
        go.universe.tf/metallb@v0.13.5 requires
        k8s.io/kubectl@v0.0.0: reading k8s.io/kubectl/go.mod at revision
v0.0.0: unknown revision v0.0.0
exit 1

This PR removes this file in order to to avoid this issue.

Pull Request Test Coverage Report for Build 4307364647

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

Totals

Change from base Build 4287436212:
0.2%

Covered Lines:
3793

Relevant Lines:
5814

💛  - Coveralls

authors: coveralls wenovus

repo: openconfig/lemming


text:
Helm Chart Volume Configuration "ReadWriteOnce" Doesn't Work with Multiple Pods

My actions before raising this issue

[X] Read/searched the docs
[X] Searched past issues

When using the Helm Chart, the storage.yml ReadWriteOnce option under the backend folder structure doesn't work in my K8s environment. If you have deployments across multiple nodes, ReadWriteOnce will form a race condition causing only one backend pod to start successfully. ReadWriteOnce by definition only allows one node to mount - so how is this supposed to work?
Steps to Reproduce (for bugs)

Attempt to deploy the helm chart to Kubernetes with the default storage

Expected Behaviour

The defaults for the helm chart should be able to launch CVAT in K8s with the minimal amount of modification.

Current Behaviour

Possible Solution

Changing storage.yml to ReadWriteMany
Put all backend deployments into the same node (maybe there's a reason this isn't designed this way though)

Do we actually need these pods to all share storage? Or can they each be granted individual PVCs for each instance of the server/utils/workers pods? Sharing a cache a la volumes seems like a poor design choice so I question if this is just an assumption made in the docker-compose configuration and just found it's way into the helm chart.

I'm unsure why it is needed that all share the same claim. Maybe someone more familiar with the chart knows? It might have some unintended consequences if we remove it.

authors: moghtader westernspion

repo: opencv/cvat


text:
Fixed CVAT annotation view restoring

Motivation and context
Resolved #5133
How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[x] I have added a description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[x] I have linked related issues (read github docs)
[x] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

@klakhov  Could you take a look at this?


text:
Fix ArgoCD sync of OTel collector

Description
Before this change, it would never get to a fully synced state in ArgoCD because it sees a diff between the live state versus the desired state of the manifest.
Before

After

How Has This Been Tested?

See screenshots above: it was tested by verifying that the issue no longer occurs after the change.
Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

/lgtm

/approve

authors: biswassri grdryn

repo: opendatahub-io/ai-edge


text:
WIP UPSTREAM : Rebase code to kfp 2.2.0

Description of your changes:
Resolves #RHOAIENG-6670
Checklist:

[ ] The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

it seems the pr is missing the code changes introduced by the rebased changes, example: https://github.com/rimolive/data-science-pipelines/blob/rebase-2.2.0/VERSION
should read 2.2 from this commit https://github.com/opendatahub-io/data-science-pipelines/pull/68/commits/dd59f48cdd0f6cd7fac40306277ef5f3dad6e263#diff-7b60b8e351cbb80c47459ffe2c79f1a26404871f49294780fe47ad0e58c09350

authors: HumairAK rimolive

repo: opendatahub-io/data-science-pipelines


text:
pip install doesn't function well on jupyterlab extension withing vscode

What steps did you take and what happened:
pip install complains, but when I do the suggestion (using %pip) it doesn't work
What did you expect to happen:
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

OpenDatahub Version: latest
Workbench: VS-Code
Workbench Version: 2023.2
Specific tool: (jupyterlab, rstudio, vscode, elyra-pipelines,etc)
Notebook-Controller Version: (please check the image version in notebook-controller deployment)

Logs/Screenshots

JIRA: https://issues.redhat.com/browse/RHOAIENG-232

So I ran pip install for pandas, matplotlab and scipy. All were installed successfully (as seen in a screenshot below).

Thank you for working this issue.
Seems like there was typo from issue.
!% both are not needed, we should either use ! for using a bash command like cli or %,  not both.
Closing this issue as complete, no changes to be made.

repo: opendatahub-io/notebooks


text:
Setting num-gpus to 0 causes a division by 0 error

This is a very low-priority bug, I'm just taking notes here for the backlog.
If you try to run python -m vllm_tgis_adapter --num-gpus 0 --device cpu it will cause this error:
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/home/mbayser/IBMProjects/FoundationModels/inference/vllm-tgis-adapter/build/__editable__.vllm_tgis_adapter-0.0.0-py3-none-any/vllm_tgis_adapter/__main__.py", line 59, in <module>
    engine = AsyncLLMEngine.from_engine_args(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/mbayser/IBMProjects/FoundationModels/inference/vllm/build/__editable__.vllm-0.5.4+cpu-cp311-cp311-linux_x86_64/vllm/engine/async_llm_engine.py", line 462, in from_engine_args
    engine_config = engine_args.create_engine_config()
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/mbayser/IBMProjects/FoundationModels/inference/vllm/build/__editable__.vllm-0.5.4+cpu-cp311-cp311-linux_x86_64/vllm/engine/arg_utils.py", line 865, in create_engine_config
    return EngineConfig(
           ^^^^^^^^^^^^^
  File "<string>", line 15, in __init__
  File "/home/mbayser/IBMProjects/FoundationModels/inference/vllm/build/__editable__.vllm-0.5.4+cpu-cp311-cp311-linux_x86_64/vllm/config.py", line 1644, in __post_init__
    self.model_config.verify_with_parallel_config(self.parallel_config)
  File "/home/mbayser/IBMProjects/FoundationModels/inference/vllm/build/__editable__.vllm-0.5.4+cpu-cp311-cp311-linux_x86_64/vllm/config.py", line 273, in verify_with_parallel_config
    if total_num_attention_heads % tensor_parallel_size != 0:
       ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
ZeroDivisionError: integer modulo by zero

num-gpus should be ignored completely if device is cpu. But even in the device is gpu there should be a validation error instead of a zero division error.

This looks like an upstream issue tbh

authors: dtrifiro maxdebayser

repo: opendatahub-io/vllm-tgis-adapter


text:
Impossibile visualizzare il template di mkdocs in GitHub Pages

Salve a tutti,
sto provando a creare una pagina usando mkdocs. Ho creato il repo e la pagina con GitHub Pages, ma non so per quale strano motivo non mi carica più il template di mkdocs. Attualmente al link visualizzo la pagina index.md ma senza la possibilità di fare nient'altro.
Qualche consiglio o aiuto?
Grazie in anticipo,
Giuseppe

Ciao Giuseppe
Mostra il link del repo GitHub del tuo progetto.
Hai clonato qualche tepo già esistente?
Il lun 20 set 2021, 00:21 Giuseppe Guarino @.***> ha
scritto:

Salve a tutti,
sto provando a creare una pagina usando mkdocs. Ho creato il repo e la
pagina con GitHub Pages, ma non so per quale strano motivo non mi carica
più il template di mkdocs. Attualmente al link visualizzo la pagina
index.md ma senza la possibilità di fare nient'altro.
Qualche consiglio o aiuto?
Grazie in anticipo,
Giuseppe
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/opendatasicilia/tansignari/issues/188, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA4VLVOL7OEJYEKQXBOKSD3UCZO7DANCNFSM5EKZDOQQ
.

Ciao Giuseppe Mostra il link del repo GitHub del tuo progetto. Hai clonato qualche tepo già esistente? Il lun 20 set 2021, 00:21 Giuseppe Guarino @.***> ha scritto:
…
Salve a tutti, sto provando a creare una pagina usando mkdocs. Ho creato il repo e la pagina con GitHub Pages, ma non so per quale strano motivo non mi carica più il template di mkdocs. Attualmente al link visualizzo la pagina index.md ma senza la possibilità di fare nient'altro. Qualche consiglio o aiuto? Grazie in anticipo, Giuseppe — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#188>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4VLVOL7OEJYEKQXBOKSD3UCZO7DANCNFSM5EKZDOQQ .

Buongiorno, ho utilizzato il classico template chiamato readthedocs. Ecco il repo https://github.com/Heryx/quantumfield.io
Vi do più dettagli. La struttura della cartella root/ è costituita da doc/, site/ mkdocs.myl e Readme.md. In github pages Punto alla cartella doc/ dove all'interno ci sono tutte le pagine da me create compreso un index.md.

Buongiorno, mi sfugge un particolare, se hai usato un template readthedocs perché le pagine html sono dentro la cartella site all'interno del repo?
Vuoi fare il render delle pagine direttamente su github o su readthedocs ?
in entrambi i casi mancano i file di configurazione oltre a mkdocs.yml devi anche inerire .readthedocs.yaml (se vuoi usare RTD come motore di rendering) e requirements-mkdocs.txt
Hai creato un progetto su https://readthedocs.org/...?
Per generare gh-pages in automatico ad ogni modifica devi creare un actions
Se vuoi realizzare una guida puoi clonare un nostro repo  che usiamo come base, devi solo personalizzarlo, l'actions per le gh-pages inclusa :-)
E' sempre mkdocs ma con tema Material for MkDocs

Il perché stiano dentro la cartella site non saprei, ho seguito la guida dal sito di mkdocs e ho lavorato da terminale dando il comando mkdocs build per costruire la cartella site.
Comunque se c'è già il vostro repo bello pronto userò quello :). Per cambiare eventualmente il tema è importante quindi che ci siamo quindi i file di configurazione, ma dovrò farlo manualmente.

Il perché stiano dentro la cartella site non saprei, ho seguito la guida dal sito di mkdocs e ho lavorato da terminale dando il comando mkdocs build per costruire la cartella site.
Comunque se c'è già il vostro repo bello pronto userò quello :). Per cambiare eventualmente il tema è importante quindi che ci siamo quindi i file di configurazione, ma dovrò farlo manualmente.

Nelle impostazioni delle gh-pages hai selezionato il percorso giusto? Punta alla cartella site?

Volevo che puntasse alla cartella site, ma non posso perché come folder disponibili in gh-pages ho solo root e docs.

Salve a tutti,
ho clonato il repo che indicatomi da @gbvitrano. Nonostante tutto, riscontro sempre lo stesso problema, cioè che riesco ad accedere alla Home del sito, ma senza la possibilità di visualizzare il Template. Aggiungo un'immagine in basso come esempio.
In localhost funziona bene, quindi non capisco se è un problema dovuto alla config del file principale del sito, o se di GitHub.
Un saluto,
Giuseppe

Salve a tutti,
ho clonato il repo che indicatomi da @gbvitrano. Nonostante tutto, riscontro sempre lo stesso problema, cioè che riesco ad accedere alla Home del sito, ma senza la possibilità di visualizzare il Template. Aggiungo un'immagine in basso come esempio.
In localhost funziona bene, quindi non capisco se è un problema dovuto alla config del file principale del sito, o se di GitHub.
Un saluto,
Giuseppe

Buongiorno, hai clonato bene il repo? nel tuo manca la la cartella .github al suo interno c'è la cartella workflows che contiene il file gh-deploy.yml con le istruzioni per creare in automatico le gh-pages

dopo devi settare l'indirizzo delle gh-pages

PS. se URL del sito non è quello canonico di github devi seguire questa guida per personalizzarlo.
il file CNAME con la sola riga del tuo URL  deve stare all'interno della cartella doc visto che hai clonato il nostro repo, lo trovi già li, devi solo scrivere il tuo URL.

Ho clonato male il repository, ecco perché non funzionava.
In ogni caso, solo per esser certo di aver fatto bene: ho copiato il link del vostro repo e da repositories ho cliccato su news e successivamente import a repository, dove ho infine aggiunto il link del vostro repo.
Grazie mille per il supporto e la pazienza.

authors: Heryx cirospat gbvitrano

repo: opendatasicilia/tansignari


text:
[EDIFICE] Register sms sending metrics for all SMS providers

Description
Le but de cette PR est d'avoir des métriques sur les temps d'envoi indépendantes du fournisseur de SMS. Auparavant, seule l'implémentation pour le fournisseur OVH exposait ces métriques.
Le code mettant à jour ces métriques ont donc été déplacées de l'implémentation concrète des classes à la classe abstraite dont elle dérive SmsProvider.
De plus, le temps des appels qui terminent en erreur est désormais enregistré.
Fix
WB-2128

Du coup, on en profite pour ventiler les temps d'envoi mesurés en 2 catégories : succès et échec. Cela permettra de voir si les échecs sont plutôt des timeouts classiques (réseau), ou des erreurs liées aux données qui devraient se produire plus rapidement. C'est bien ça ?

Oui c'est ça. Et en plus ça permet de les compter car la métrique de mesure du temps expose aussi le nombre d'événements qui ont généré ladite métrique

repo: opendigitaleducation/mod-sms-sender


text:
style(wyh): add env information in readme

env_lists including env name,gif,github_link,dizoo_link

Codecov Report

Merging #46 (f18aff5) into main (110d406) will decrease coverage by 0.36%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #46      +/-   ##
==========================================
- Coverage   90.06%   89.69%   -0.37%
==========================================
  Files         339      341       +2
  Lines       24846    25212     +366
==========================================
+ Hits        22378    22615     +237
- Misses       2468     2597     +129

Flag
Coverage Δ

unittests
89.69% <ø> (-0.37%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

ding/utils/data/dataset.py
55.35% <0.00%> (-44.65%)
:arrow_down:

ding/worker/learner/comm/flask_fs_learner.py
83.64% <0.00%> (-7.61%)
:arrow_down:

ding/utils/data/structure/cache.py
94.23% <0.00%> (-5.77%)
:arrow_down:

ding/policy/sac.py
75.23% <0.00%> (-3.85%)
:arrow_down:

ding/utils/data/dataloader.py
43.52% <0.00%> (-2.60%)
:arrow_down:

ding/interaction/base/network.py
96.29% <0.00%> (-1.27%)
:arrow_down:

ding/worker/learner/tests/test_base_learner.py
91.01% <0.00%> (-1.13%)
:arrow_down:

ding/envs/env_manager/subprocess_env_manager.py
82.08% <0.00%> (-0.61%)
:arrow_down:

ding/interaction/slave/slave.py
85.08% <0.00%> (-0.51%)
:arrow_down:

ding/interaction/master/master.py
90.16% <0.00%> (-0.45%)
:arrow_down:

... and 32 more

Continue to review full report at Codecov.

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

repo: opendilab/DI-engine


text:
Questions about details of the network

Hi,
Thank you for your great work! I have some questions about details of the network.

For CNN backbone, input images from different cameras are scaled to different size and cropped to different size (e.g. front: 800x600 => scale to 256x256 => crop to 224x224, left/right: 800x600 => scale to 160x160 => crop to 128x128, focus: 800x600 => crop to 128x128), are there any special reasons for different operations and choosing different size?
For backbone, in the paper "We set C = 2048 and (H;W) = (H0/32 ; W0/32 ) in experiments.", any special reason for choosing 2048 and dividing by 32?
After resnet, a convoluation is used to reduce channel from 2048 to 256, any special reason for choosing 256?

Thank you! :)

Hi,

For the front view, we think it's the most important view, so we give it a largest size. For the side views, we take a smaller size to reduce the Flops of the network. For the focus view, we don't scale it and directly center-crop it to capture traffic light status at a distance.
C = 2048 and (H;W) = (H0/32 ; W0/32 ) is just at a Stage 4 of a standard Resnet. H or W/32 is a proper resolution for the following transformer encoder. A higher resolution would  lead to an increase in the O(N^2) calculation of the transformer. A lower resolution would cause a large performance drop.
We have tried other choices and found 256 channels got the best performance with fewer network parameters.

Hi,
Thank you for you replay! :)

For the size (e.g. 256 or 128 or 160), do you try other size?
For higher and lower resolution rather than dividing by 32, do you do any experiments (e.g. using H/16 or H/64)?
I understand now. Thank you.

Thank you very much! :)

Hi, we haven't tried other input size or different resolutions in our experiments. But H/16 will bring 4X tokens and 16X flops, which may make it difficult to train or inference.

Thank you very much! :)

repo: opendilab/InterFuser


text:
Can we upgrade Elasticsearch 7.9 to Opendistro Version of elasticsearch

Hello,
As OD elasticsearch is open source, I'm really interested in it !!
Can I migrate from my present Elastic’s ELK Stack to Open Distro Elasticsearch. Please describe a way to do this.
Is there a way to do this without any downtime? Actually, I'm not sure yet what is the best way to implement it!!
Appreciate your help !!

Hi @Saketha016 we have a similar ticket here with some instructions on snapshots restoration.
Please take a look and let us know if we can be more help.
https://github.com/opendistro/for-elasticsearch-docs/issues/27
https://opendistro.github.io/for-elasticsearch-docs/docs/elasticsearch/snapshot-restore/


text:
problem with self signed cert with oidc

i haven't figured out whether this is the right module that handles the OpenID Connect code - it doesn't seem like so please let me know if I should go to another module instead. Since I can't get SAML to work, I am trying OIDC and I get a self-signed cert error when I use OIDC. I already put the CA cert in
config:
pemtrustedcas_filepath: /path/to/trusted_cas.pem
as well.
Error from the log:
,"tags":["error","openid"],"pid":XXXXX,"level":"error","error":{"message":"Client request error: self signed certificate","name":"Error","stack":"Error: self signed certificate\n    at TLSSocket. (_tls_wrap.js:1116:38)\n    at emitNone (events.js:106:13)\n    at TLSSocket.emit (events.js:208:7)\n    at TLSSocket._finishInit (_tls_wrap.js:643:8)\n    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:473:38)","code":"DEPTH_ZERO_SELF_SIGNED_CERT"},"message":"Client request error: self signed certificate"

@hermanhmlee If possible, can you share your relevant config snipper like openid config, opendistro_security config etc. ?

Hi, I know it is a bit old but I think the case is that there should be a prefix used. See https://github.com/opendistro-for-elasticsearch/security-advanced-modules/issues/63

authors: hermanhmlee miro-grapeup shivdoshi


text:
Add ODFE CLI

Known issues: install section does not include download link.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@VijayanB @vamshin

@aetter Do you think that we don't need a link to download page from this page?

@aetter Do you think that we don't need a link to download page from this page?

@VijayanB it only takes ~15 seconds for the documentation to get updated after we merge, so we typically just do it on release day. I wasn't sure how we were going to present things on the Downloads page, so I listed "no download link yet" as a known gap. I've added a link now and will update it to include a header if we put the CLI into a named section of the page.

@VijayanB it only takes ~15 seconds for the documentation to get updated after we merge, so we typically just do it on release day. I wasn't sure how we were going to present things on the Downloads page, so I listed "no download link yet" as a known gap. I've added a link now and will update it to include a header if we put the CLI into a named section of the page.

authors: VijayanB aetter

repo: opendistro/for-elasticsearch-docs


text:
464 multi tabs

use localStorage to share login state between tabs

@ekraffmiller May be able to reproduce with a clean install and:
(note: only 1 user)
(1) tab 1: log in with dev_admin; click "MyProfile"; click "My Data"
(2) tab 2: login with dev_admin; click "MyProfile"; click "My Data"
(3) tab 1: click "Log out"

@raprasad I was able to reproduce that error - it was happening because the current page is updated after logout, even though the user is redirected to the home page.  I added a condition to check the value of datasets before rendering the v-data-table.

authors: ekraffmiller raprasad

repo: opendp/dpcreator


text:
Sporadic R null pointer errors in tests

R tests failed with the following error, but no error when re-running. Tests should be deterministic.
══ Failed ══════════════════════════════════════════════════════════════════════
── 1. Error ('test-mod.R:8:34'): binary search ─────────────────────────────────
Error: Error in `make_chain_mt(rhs, lhs)`: [FFI] : null pointer: measurement1
Error: Error: Failures detected.
Execution halted
disabled backtrace
Backtrace:
     ▆
  1. ├─opendp::binary_search_chain(...) at test-mod.R:8:5
  2. │ ├─opendp (local) make_chain(...) at opendp/R/mod.R:507:3
  3. │ │ └─opendp::then_laplace(t_sum, s) at test-mod.R:8:34
  4. │ │   ├─opendp:::new_constructor_log(...) at opendp/R/measurements.R:1032:5
  5. │ │   │ └─opendp::new_hashtab(...) at opendp/R/mod.R:431:3
  6. │ │   └─opendp::new_hashtab(list("scale", "QO"), list(scale, .QO)) at opendp/R/mod.R:405:3
  7. │ └─opendp::binary_search_param(...) at opendp/R/mod.R:405:3
  8. │   └─opendp::binary_search(...) at opendp/R/mod.R:525:3
  9. │     └─opendp (local) predicate(mid) at opendp/R/mod.R:584:5
 10. │       └─make_chain(param)(d_in = d_in, d_out = d_out) at opendp/R/mod.R:526:5
 11. │         └─opendp::measurement_check(ptr, d_in, d_out) at opendp/R/mod.R:155:9
 12. │           └─opendp::measurement_input_distance_type(measurement) at opendp/R/core.R:54:5
 13. │             ├─opendp:::new_constructor_log(...) at opendp/R/core.R:133:5
 14. │             │ └─opendp::new_hashtab(...) at opendp/R/mod.R:431:3
 15. │             └─opendp::new_hashtab(list("this"), list(this)) at opendp/R/mod.R:405:3
 16. └─opendp::make_chain_mt(rhs, lhs) at opendp/R/mod.R:405:3

══ DONE ════════════════════════════════════════════════════════════════════════
Error: Process completed with exit code 1.

Another occurrence:
── 1. Error ('test-measurements.R:64:3'): test_gaussian_curve ──────────────────
Error: Error in `make_zCDP_to_approxDP(then_gaussian(input_space, 4))`: [FFI] : null pointer: measurement
disabled backtrace

https://github.com/opendp/opendp/actions/runs/9532168225/job/26274066401

And another: https://github.com/opendp/opendp/pull/1687#issuecomment-2176116502
── 1. Error ('test-measurements.R:64:3'): test_gaussian_curve ──────────────────
Error: Error in `make_zCDP_to_approxDP(then_gaussian(input_space, 4))`: [FFI] : null pointer: measurement
Error: Error: Failures detected.
Execution halted
disabled backtrace
Backtrace:
    ▆
 1. └─opendp::make_zCDP_to_approxDP(then_gaussian(input_space, 4)) at test-measurements.R:64:3

Going back through the past week and collecting all the failures of this type:

https://github.com/opendp/opendp/actions/runs/9588208826/job/26440087474
https://github.com/opendp/opendp/actions/runs/9554951904/job/26346414035
https://github.com/opendp/opendp/actions/runs/9531840741/job/26273331638

Though the initial report is coming from a different place, the last three are all the same. Possible that it's not actually that erratic? Would it help to run the test repeatedly, either locally or on CI to get more examples? Is there any more instrumentation we could add, right before the point of the error?

https://github.com/opendp/opendp/actions/runs/9941992793/job/27463056354?pr=1767
── 1. Error ('test-mod.R:6:32'): binary search ─────────────────────────────────
Error: Error in `measurement_input_distance_type(measurement)`: [FFI] : null pointer: this
Error: Error: Failures detected.
Execution halted
disabled backtrace
Backtrace:
     ▆
  1. └─opendp::binary_search_chain(...) at test-mod.R:6:3
  2.   ├─opendp (local) make_chain(...) at opendp/R/mod.R:510:3
  3.   │ └─opendp::then_laplace(t_sum, s) at test-mod.R:6:32
  4.   │   ├─opendp:::new_constructor_log(...) at opendp/R/measurements.R:442:3
  5.   │   │ └─opendp::new_hashtab(...) at opendp/R/mod.R:434:3
  6.   │   └─opendp::new_hashtab(...) at opendp/R/mod.R:408:3
  7.   └─opendp::binary_search_param(...) at opendp/R/mod.R:408:3
  8.     └─opendp::binary_search(...) at opendp/R/mod.R:528:3
  9.       └─opendp (local) predicate(mid) at opendp/R/mod.R:587:5
 10.         └─make_chain(param)(d_in = d_in, d_out = d_out) at opendp/R/mod.R:529:5
 11.           └─opendp::measurement_check(ptr, d_in, d_out) at opendp/R/mod.R:155:9
 12.             └─opendp::measurement_input_distance_type(measurement) at opendp/R/core.R:53:3

https://github.com/opendp/opendp/actions/runs/9961038699/job/27521828871#step:7:27

repo: opendp/opendp


text:
Binary search in chainers

Occasionally when we write relations, we only write the relation itself-- no constant, no forward map, no backward map. This can cause chaining to fail, because a hinter does not exist. We can, however, still find d_mid via binary search. In the past we've talked about how best to find the binary search bounds: maybe the search bounds are a const associated with a trait on metrics?
However, it would be simpler and better just to use this doubling trick, as the distances are always positive:
let mut lower = 0.;
let mut upper = 1.;
while !predicate(upper) {
    lower = upper;
    upper = 2.0 * upper;
}

The will terminate for some interval (2^(k - 1), 2^k), from which we can begin binary search. The python binary search is a good code snip to adapt for this.

Closed via #463, since maps don't need binary searches when chaining.


text:
fix CallbackFn segfault

Closes #2167

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2168  👈 (View in Graphite)
#2091 : 2 other dependent PRs (#2095 , #2153 )
#2089
main

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


text:
Docs Update -- User Guide Sections by AV

Closes #270.

Added sphinx-prompt for better shell instructions
Wrote Getting Started section
Expanded Programming Framework section
Added forward links to data structures

I think Getting Started is overall pretty good now. I don't love the hello world example, because it requires more type stuff than ideal, but it felt better using make_identity, which is simple and works with strings, instead of something more specific like make_clamp. I'm open to argument on that one though.
Programming Framework is rougher, but at least gives the basics. After writing it, I realize there's going to be some duplication with later sections. It might be better to restructure things to cover each topic in depth, both conceptual stuff and and programming specific stuff, rather than all conceptual topics then all programming topics like it is now. But like all of these docs, something is better than nothing for starters!

Thanks Mike! I've addressed the review comments.


text:
Cas 241 per child io counters

CAS-241. Functionality to store and query a record of the most recent in each nexus child and a means of enabling the feature and setting the buffer size.
The query function returns the number of error IOs more recent than a specified interval and filtered by flags specifying the IO operation and a flag specifying the type of error (currently only one error type "FAILED").
Test added which adds an error bdev layer between the nexus and one of its
replicas and allows unit testing of the feature. This currently tests only failures of reads and writes.
Also included unit testing of the error store independently of the bdev.
Formatting changes in nexus_metadata.rs imposed by the pre-commit hook.
Includes recent code-review changes to store monolithic time instead of absolute time in the records, and to ensure that the storing of error records is handled by the management core.

Closed as not feature-ready for develop yet.

repo: openebs/Mayastor


text:
refact(yaml): Add deprovision task to remove stale daemonset in zv property modification test

What this PR does / why we need it:

This PR add deprovision task to remove stale daemonset.

PLAYBOOK: test.yml *************************************************************
1 plays in ./experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml

PLAY [localhost] ***************************************************************
2020-12-11T10:32:40.071059 (delta: 0.036658)         elapsed: 0.036658 ********
===============================================================================
META: ran handlers

TASK [include_tasks] ***********************************************************
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:13
2020-12-11T10:32:40.080179 (delta: 0.009083)         elapsed: 0.045778 ********
included: /utils/fcm/create_testname.yml for 127.0.0.1

TASK [Record test instance/run ID] *********************************************
task path: /utils/fcm/create_testname.yml:3
2020-12-11T10:32:40.106462 (delta: 0.026269)         elapsed: 0.072061 ********
skipping: [127.0.0.1] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Construct testname appended with runID] **********************************
task path: /utils/fcm/create_testname.yml:7
2020-12-11T10:32:40.156335 (delta: 0.049847)         elapsed: 0.121934 ********
skipping: [127.0.0.1] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [include_tasks] ***********************************************************
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:16
2020-12-11T10:32:40.235984 (delta: 0.079622)         elapsed: 0.201583 ********
included: /utils/fcm/update_litmus_result_resource.yml for 127.0.0.1

TASK [Generate the litmus result CR to reflect SOT (Start of Test)] ************
task path: /utils/fcm/update_litmus_result_resource.yml:3
2020-12-11T10:32:40.276591 (delta: 0.040566)         elapsed: 0.24219 *********
changed: [127.0.0.1] => {"changed": true, "checksum": "840f3b5742ea45e6fb2c6c284dbb1db24249ef3d", "dest": "./litmus-result.yaml", "gid": 0, "group": "root", "md5sum": "1c30751caa6a6f10500548c1364d9861", "mode": "0644", "owner": "root", "size": 429, "src": "/root/.ansible/tmp/ansible-tmp-1607682760.31-183529691079553/source", "state": "file", "uid": 0}

TASK [Analyze the cr yaml] *****************************************************
task path: /utils/fcm/update_litmus_result_resource.yml:14
2020-12-11T10:32:40.782398 (delta: 0.505782)         elapsed: 0.747997 ********
changed: [127.0.0.1] => {"changed": true, "cmd": "cat litmus-result.yaml", "delta": "0:00:00.589754", "end": "2020-12-11 10:32:41.665945", "rc": 0, "start": "2020-12-11 10:32:41.076191", "stderr": "", "stderr_lines": [], "stdout": "---\napiVersion: litmus.io/v1alpha1\nkind: LitmusResult\nmetadata:\n\n  # name of the litmus testcase\n  name: zvol-property-runtime-modify \nspec:\n\n  # holds information on the testcase\n  testMetadata:\n    app:  \n    chaostype:  \n\n  # holds the state of testcase,  manually updated by json merge patch\n  # result is the useful value today, but anticipate phase use in future \n  testStatus: \n    phase: in-progress  \n    result: none ", "stdout_lines": ["---", "apiVersion: litmus.io/v1alpha1", "kind: LitmusResult", "metadata:", "", "  # name of the litmus testcase", "  name: zvol-property-runtime-modify ", "spec:", "", "  # holds information on the testcase", "  testMetadata:", "    app:  ", "    chaostype:  ", "", "  # holds the state of testcase,  manually updated by json merge patch", "  # result is the useful value today, but anticipate phase use in future ", "  testStatus: ", "    phase: in-progress  ", "    result: none "]}

TASK [Apply the litmus result CR] **********************************************
task path: /utils/fcm/update_litmus_result_resource.yml:17
2020-12-11T10:32:41.688989 (delta: 0.906545)         elapsed: 1.654588 ********
changed: [127.0.0.1] => {"changed": true, "failed_when_result": false, "method": "patch", "result": {"apiVersion": "litmus.io/v1alpha1", "kind": "LitmusResult", "metadata": {"creationTimestamp": "2020-12-11T09:47:37Z", "generation": 3, "name": "zvol-property-runtime-modify", "resourceVersion": "4158310", "selfLink": "/apis/litmus.io/v1alpha1/litmusresults/zvol-property-runtime-modify", "uid": "2754c0a3-31ac-4e98-89a9-93337ef889db"}, "spec": {"testMetadata": {}, "testStatus": {"phase": "in-progress", "result": "none"}}}}

TASK [Generate the litmus result CR to reflect EOT (End of Test)] **************
task path: /utils/fcm/update_litmus_result_resource.yml:27
2020-12-11T10:32:42.309250 (delta: 0.620203)         elapsed: 2.274849 ********
skipping: [127.0.0.1] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Analyze the cr yaml] *****************************************************
task path: /utils/fcm/update_litmus_result_resource.yml:38
2020-12-11T10:32:42.332769 (delta: 0.023488)         elapsed: 2.298368 ********
skipping: [127.0.0.1] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Apply the litmus result CR] **********************************************
task path: /utils/fcm/update_litmus_result_resource.yml:41
2020-12-11T10:32:42.360220 (delta: 0.027297)         elapsed: 2.325819 ********
skipping: [127.0.0.1] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Update the daemonset spec template with test specific values] ************
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:21
2020-12-11T10:32:42.383324 (delta: 0.023033)         elapsed: 2.348923 ********
changed: [127.0.0.1] => {"changed": true, "checksum": "328b1a556407d2bb51b4b08154896306375a4e7f", "dest": "./zv_property_ds.yml", "gid": 0, "group": "root", "md5sum": "2edcc626a0a4259e2987beb1ba4a49fa", "mode": "0644", "owner": "root", "size": 899, "src": "/root/.ansible/tmp/ansible-tmp-1607682762.43-69841085064428/source", "state": "file", "uid": 0}

TASK [Create a daemonset with privileged access to verify zvol properties at node level] ***
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:26
2020-12-11T10:32:42.675301 (delta: 0.291932)         elapsed: 2.6409 **********
changed: [127.0.0.1] => {"changed": true, "cmd": "kubectl create -f ./zv_property_ds.yml", "delta": "0:00:01.040917", "end": "2020-12-11 10:32:43.859953", "failed_when_result": false, "rc": 0, "start": "2020-12-11 10:32:42.819036", "stderr": "", "stderr_lines": [], "stdout": "daemonset.apps/zv-property-modify-zfs-428l5 created", "stdout_lines": ["daemonset.apps/zv-property-modify-zfs-428l5 created"]}

TASK [Confirm that the ds pods are running on all nodes] ***********************
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:34
2020-12-11T10:32:43.892282 (delta: 1.216935)         elapsed: 3.857881 ********
FAILED - RETRYING: Confirm that the ds pods are running on all nodes (20 retries left).
changed: [127.0.0.1] => {"attempts": 2, "changed": true, "cmd": "kubectl get pod -l app=zv-property-modify-zfs --no-headers -o custom-columns=:status.phase | sort | uniq", "delta": "0:00:00.668360", "end": "2020-12-11 10:32:50.685373", "rc": 0, "start": "2020-12-11 10:32:50.017013", "stderr": "", "stderr_lines": [], "stdout": "Running", "stdout_lines": ["Running"]}

TASK [Get the node name on which application is scheduled] *********************
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:45
2020-12-11T10:32:50.710816 (delta: 6.81848)         elapsed: 10.676415 ********
changed: [127.0.0.1] => {"changed": true, "cmd": "kubectl get pod -n sam -l name=percona --no-headers -o custom-columns=:.spec.nodeName", "delta": "0:00:00.528805", "end": "2020-12-11 10:32:51.356642", "rc": 0, "start": "2020-12-11 10:32:50.827837", "stderr": "", "stderr_lines": [], "stdout": "e2e1-node3", "stdout_lines": ["e2e1-node3"]}

TASK [Get the daemonset pod name which is scheduled on the same node as of application node] ***
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:53
2020-12-11T10:32:51.381556 (delta: 0.670713)         elapsed: 11.347155 *******
changed: [127.0.0.1] => {"changed": true, "cmd": "kubectl get pod -l app=zv-property-modify-zfs --no-headers -o jsonpath='{.items[?(@.spec.nodeName==\"e2e1-node3\")].metadata.name}'", "delta": "0:00:00.569378", "end": "2020-12-11 10:32:52.126267", "rc": 0, "start": "2020-12-11 10:32:51.556889", "stderr": "", "stderr_lines": [], "stdout": "zv-property-modify-zfs-428l5-s42np", "stdout_lines": ["zv-property-modify-zfs-428l5-s42np"]}

TASK [Record the daemonset pod name scheduled on the same node with application pod] ***
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:61
2020-12-11T10:32:52.148268 (delta: 0.766681)         elapsed: 12.113867 *******
ok: [127.0.0.1] => {"ansible_facts": {"ds_pod": "zv-property-modify-zfs-428l5-s42np"}, "changed": false}

TASK [Get the zvolume name] ****************************************************
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:65
2020-12-11T10:32:52.187532 (delta: 0.039235)         elapsed: 12.153131 *******
changed: [127.0.0.1] => {"changed": true, "cmd": "kubectl get pvc percona-mysql-claim -n sam --no-headers -o custom-columns=:.spec.volumeName", "delta": "0:00:00.611022", "end": "2020-12-11 10:32:52.924875", "rc": 0, "start": "2020-12-11 10:32:52.313853", "stderr": "", "stderr_lines": [], "stdout": "pvc-e801ac87-c9f6-426d-a374-d6a8ac133419", "stdout_lines": ["pvc-e801ac87-c9f6-426d-a374-d6a8ac133419"]}

TASK [Record the zvolume name] *************************************************
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:73
2020-12-11T10:32:52.947063 (delta: 0.759497)         elapsed: 12.912662 *******
ok: [127.0.0.1] => {"ansible_facts": {"zv_name": "pvc-e801ac87-c9f6-426d-a374-d6a8ac133419"}, "changed": false}

TASK [Get the compression parameter value from the zvolume] ********************
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:77
2020-12-11T10:32:52.991448 (delta: 0.044355)         elapsed: 12.957047 *******
changed: [127.0.0.1] => {"changed": true, "cmd": "kubectl get zv pvc-e801ac87-c9f6-426d-a374-d6a8ac133419 -n openebs --no-headers -o custom-columns=:.spec.compression", "delta": "0:00:00.641910", "end": "2020-12-11 10:32:53.766555", "rc": 0, "start": "2020-12-11 10:32:53.124645", "stderr": "", "stderr_lines": [], "stdout": "on", "stdout_lines": ["on"]}

TASK [Get the Dedup parameter value from the zvolume] **************************
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:85
2020-12-11T10:32:53.787586 (delta: 0.796104)         elapsed: 13.753185 *******
changed: [127.0.0.1] => {"changed": true, "cmd": "kubectl get zv pvc-e801ac87-c9f6-426d-a374-d6a8ac133419 -n openebs --no-headers -o custom-columns=:.spec.dedup", "delta": "0:00:00.595167", "end": "2020-12-11 10:32:54.497275", "rc": 0, "start": "2020-12-11 10:32:53.902108", "stderr": "", "stderr_lines": [], "stdout": "on", "stdout_lines": ["on"]}

TASK [Get the yaml file for zvolume] *******************************************
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:93
2020-12-11T10:32:54.536860 (delta: 0.74924)         elapsed: 14.502459 ********
changed: [127.0.0.1] => {"changed": true, "cmd": "kubectl get zv pvc-e801ac87-c9f6-426d-a374-d6a8ac133419 -n openebs -o yaml > zv.yml", "delta": "0:00:00.649860", "end": "2020-12-11 10:32:55.317461", "rc": 0, "start": "2020-12-11 10:32:54.667601", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}

TASK [Modify the compression parameter value] **********************************
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:99
2020-12-11T10:32:55.345130 (delta: 0.808233)         elapsed: 15.310729 *******
changed: [127.0.0.1] => {"changed": true, "msg": "1 replacements made"}

TASK [Modify the dedup parameter value] ****************************************
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:105
2020-12-11T10:32:55.663731 (delta: 0.318573)         elapsed: 15.62933 ********
changed: [127.0.0.1] => {"changed": true, "msg": "1 replacements made"}

TASK [Apply the modified yaml to update the new value of zvolume parameters] ***
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:111
2020-12-11T10:32:55.879450 (delta: 0.215669)         elapsed: 15.845049 *******

changed: [127.0.0.1] => {"changed": true, "cmd": "kubectl apply -f zv.yml", "delta": "0:00:00.993835", "end": "2020-12-11 10:32:57.017876", "failed_when_result": false, "rc": 0, "start": "2020-12-11 10:32:56.024041", "stderr": "", "stderr_lines": [], "stdout": "zfsvolume.zfs.openebs.io/pvc-e801ac87-c9f6-426d-a374-d6a8ac133419 configured", "stdout_lines": ["zfsvolume.zfs.openebs.io/pvc-e801ac87-c9f6-426d-a374-d6a8ac133419 configured"]}

TASK [Verify that compression parameter value is modified in zvolume] **********
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:119
2020-12-11T10:32:57.050005 (delta: 1.170522)         elapsed: 17.015604 *******
 [WARNING]: when statements should not include jinja2 templating delimiters
such as {{ }} or {% %}. Found: modified_compress_val.stdout == "{{
new_compress_val }}"
changed: [127.0.0.1] => {"attempts": 1, "changed": true, "cmd": "kubectl get zv pvc-e801ac87-c9f6-426d-a374-d6a8ac133419 -n openebs --no-headers -o custom-columns=:.spec.compression", "delta": "0:00:00.656957", "end": "2020-12-11 10:32:57.825558", "rc": 0, "start": "2020-12-11 10:32:57.168601", "stderr": "", "stderr_lines": [], "stdout": "off", "stdout_lines": ["off"]}

TASK [Verify that compression parameter value is modified in dataset/zvolume on node] ***
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:130
2020-12-11T10:32:57.863284 (delta: 0.813244)         elapsed: 17.828883 *******
changed: [127.0.0.1] => {"attempts": 1, "changed": true, "cmd": "kubectl exec -ti zv-property-modify-zfs-428l5-s42np -- bash -c 'zfs get all test/pvc-e801ac87-c9f6-426d-a374-d6a8ac133419 | grep compression'", "delta": "0:00:00.807938", "end": "2020-12-11 10:32:58.796664", "rc": 0, "start": "2020-12-11 10:32:57.988726", "stderr": "Unable to use a TTY - input is not a terminal or the right kind of file", "stderr_lines": ["Unable to use a TTY - input is not a terminal or the right kind of file"], "stdout": "test/pvc-e801ac87-c9f6-426d-a374-d6a8ac133419  compression           off                    local", "stdout_lines": ["test/pvc-e801ac87-c9f6-426d-a374-d6a8ac133419  compression           off                    local"]}

TASK [Verify that dedup parameter value is modified in zvolume] ****************
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:140
2020-12-11T10:32:58.836452 (delta: 0.973135)         elapsed: 18.802051 *******
 [WARNING]: when statements should not include jinja2 templating delimiters
such as {{ }} or {% %}. Found: modified_dedup_val.stdout == "{{ new_dedup_val
}}"
changed: [127.0.0.1] => {"attempts": 1, "changed": true, "cmd": "kubectl get zv pvc-e801ac87-c9f6-426d-a374-d6a8ac133419 -n openebs --no-headers -o custom-columns=:.spec.dedup", "delta": "0:00:00.593574", "end": "2020-12-11 10:32:59.548163", "rc": 0, "start": "2020-12-11 10:32:58.954589", "stderr": "", "stderr_lines": [], "stdout": "off", "stdout_lines": ["off"]}

TASK [Verify that compression parameter value is modified in dataset/zvolume on node] ***
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:151
2020-12-11T10:32:59.651271 (delta: 0.814777)         elapsed: 19.61687 ********
changed: [127.0.0.1] => {"attempts": 1, "changed": true, "cmd": "kubectl exec -ti zv-property-modify-zfs-428l5-s42np -- bash -c 'zfs get all test/pvc-e801ac87-c9f6-426d-a374-d6a8ac133419 | grep dedup'", "delta": "0:00:00.871433", "end": "2020-12-11 10:33:00.684193", "rc": 0, "start": "2020-12-11 10:32:59.812760", "stderr": "Unable to use a TTY - input is not a terminal or the right kind of file", "stderr_lines": ["Unable to use a TTY - input is not a terminal or the right kind of file"], "stdout": "test/pvc-e801ac87-c9f6-426d-a374-d6a8ac133419  dedup                 off                    local", "stdout_lines": ["test/pvc-e801ac87-c9f6-426d-a374-d6a8ac133419  dedup                 off                    local"]}

TASK [set_fact] ****************************************************************
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:161
2020-12-11T10:33:00.725423 (delta: 1.073675)         elapsed: 20.691022 *******
ok: [127.0.0.1] => {"ansible_facts": {"flag": "Pass"}, "changed": false}

TASK [Get the name of daemonset] ***********************************************
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:170
2020-12-11T10:33:00.788029 (delta: 0.062565)         elapsed: 20.753628 *******
changed: [127.0.0.1] => {"changed": true, "cmd": "kubectl get ds -n litmus -o jsonpath='{.items[?(@.spec.selector.matchLabels.app==\"zv-property-modify-zfs\")].metadata.name}'", "delta": "0:00:00.608162", "end": "2020-12-11 10:33:01.536690", "rc": 0, "start": "2020-12-11 10:33:00.928528", "stderr": "", "stderr_lines": [], "stdout": "zv-property-modify-zfs-428l5", "stdout_lines": ["zv-property-modify-zfs-428l5"]}

TASK [Delete the daemonset with privileged access to verify zvol properties at node level] ***
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:177
2020-12-11T10:33:01.566898 (delta: 0.778827)         elapsed: 21.532497 *******
changed: [127.0.0.1] => {"changed": true, "cmd": "kubectl delete ds zv-property-modify-zfs-428l5 -n litmus", "delta": "0:00:00.574863", "end": "2020-12-11 10:33:02.283858", "failed_when_result": false, "rc": 0, "start": "2020-12-11 10:33:01.708995", "stderr": "", "stderr_lines": [], "stdout": "daemonset.apps \"zv-property-modify-zfs-428l5\" deleted", "stdout_lines": ["daemonset.apps \"zv-property-modify-zfs-428l5\" deleted"]}

TASK [include_tasks] ***********************************************************
task path: /experiments/zfs-localpv/functional/zv-property-runtime-modify/test.yml:186
2020-12-11T10:33:02.321438 (delta: 0.754458)         elapsed: 22.287037 *******
included: /utils/fcm/update_litmus_result_resource.yml for 127.0.0.1

TASK [Generate the litmus result CR to reflect SOT (Start of Test)] ************
task path: /utils/fcm/update_litmus_result_resource.yml:3
2020-12-11T10:33:02.358591 (delta: 0.037117)         elapsed: 22.32419 ********
skipping: [127.0.0.1] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Analyze the cr yaml] *****************************************************
task path: /utils/fcm/update_litmus_result_resource.yml:14
2020-12-11T10:33:02.385959 (delta: 0.027343)         elapsed: 22.351558 *******
skipping: [127.0.0.1] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Apply the litmus result CR] **********************************************
task path: /utils/fcm/update_litmus_result_resource.yml:17
2020-12-11T10:33:02.423003 (delta: 0.036963)         elapsed: 22.388602 *******
skipping: [127.0.0.1] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Generate the litmus result CR to reflect EOT (End of Test)] **************
task path: /utils/fcm/update_litmus_result_resource.yml:27
2020-12-11T10:33:02.446567 (delta: 0.023531)         elapsed: 22.412166 *******
changed: [127.0.0.1] => {"changed": true, "checksum": "0d5cc8334eefedac4d52dfa16bbebe343f71cd44", "dest": "./litmus-result.yaml", "gid": 0, "group": "root", "md5sum": "3d78df64eca1a39b00169e7cd1d23f15", "mode": "0644", "owner": "root", "size": 427, "src": "/root/.ansible/tmp/ansible-tmp-1607682782.53-155318305479965/source", "state": "file", "uid": 0}

TASK [Analyze the cr yaml] *****************************************************
task path: /utils/fcm/update_litmus_result_resource.yml:38
2020-12-11T10:33:03.855631 (delta: 1.409019)         elapsed: 23.82123 ********
changed: [127.0.0.1] => {"changed": true, "cmd": "cat litmus-result.yaml", "delta": "0:00:00.447742", "end": "2020-12-11 10:33:04.415533", "rc": 0, "start": "2020-12-11 10:33:03.967791", "stderr": "", "stderr_lines": [], "stdout": "---\napiVersion: litmus.io/v1alpha1\nkind: LitmusResult\nmetadata:\n\n  # name of the litmus testcase\n  name: zvol-property-runtime-modify \nspec:\n\n  # holds information on the testcase\n  testMetadata:\n    app:  \n    chaostype:  \n\n  # holds the state of testcase,  manually updated by json merge patch\n  # result is the useful value today, but anticipate phase use in future \n  testStatus: \n    phase: completed  \n    result: Pass ", "stdout_lines": ["---", "apiVersion: litmus.io/v1alpha1", "kind: LitmusResult", "metadata:", "", "  # name of the litmus testcase", "  name: zvol-property-runtime-modify ", "spec:", "", "  # holds information on the testcase", "  testMetadata:", "    app:  ", "    chaostype:  ", "", "  # holds the state of testcase,  manually updated by json merge patch", "  # result is the useful value today, but anticipate phase use in future ", "  testStatus: ", "    phase: completed  ", "    result: Pass "]}

TASK [Apply the litmus result CR] **********************************************
task path: /utils/fcm/update_litmus_result_resource.yml:41
2020-12-11T10:33:04.444427 (delta: 0.588765)         elapsed: 24.410026 *******
changed: [127.0.0.1] => {"changed": true, "failed_when_result": false, "method": "patch", "result": {"apiVersion": "litmus.io/v1alpha1", "kind": "LitmusResult", "metadata": {"creationTimestamp": "2020-12-11T09:47:37Z", "generation": 4, "name": "zvol-property-runtime-modify", "resourceVersion": "4167994", "selfLink": "/apis/litmus.io/v1alpha1/litmusresults/zvol-property-runtime-modify", "uid": "2754c0a3-31ac-4e98-89a9-93337ef889db"}, "spec": {"testMetadata": {}, "testStatus": {"phase": "completed", "result": "Pass"}}}}
META: ran handlers
META: ran handlers

PLAY RECAP *********************************************************************
127.0.0.1                  : ok=30   changed=24   unreachable=0    failed=0