Create a v1 otlp only distro

As part of https://github.com/open-telemetry/opentelemetry-collector/issues/9375, we'll need a distro for this

As a formality, here is how such a distribution meets our criteria:

Serve a specific purpose that has minimal overlap with the purpose of any other distribution: This distribution's specific purpose would be to be used as a "side-car" - an absolutely bare minimum collector capable of receiving application OTLP telemetry, queuing, and exporting that OTLP telemetry.
Should meet general needs and be desired by many users.: A side car collector has been brought up before and I believe implemented elsewhere (@jpkrohling can you confirm?). It could be usable as the default side-car collector for the OpenTelemetry Operator.
Should not be specific to any vendor.: ✅
May be focused on development or proof of concept use cases.  The distribution should clearly indicate whether the Collector SIG recommends the distribution be used in production environments.: This will be a production-ready distribution.
Must only include components from the opentelemetry-collector and opentelemetry-collector-contrib repositories: ✅
Have a clearly defined list of criteria for which components are included.: The criteria will be only only the otlpreceiver, otlpexporter, and otlphttpexporter are allowed.
Must include the following assets except where the specific purpose of the distribution is naturally associated with a subset of these assets.: We'll release our typical assets, including windows.

A side car collector has been brought up before and I believe implemented elsewhere (@jpkrohling can you confirm?).

Yes, here: https://github.com/jpkrohling/otelcol-distributions/tree/main/distributions/otelcol-otlp
That one includes a few more things that I thought were essential after putting this in the real world. Here's the full manifest:
https://github.com/jpkrohling/otelcol-distributions/blob/5566bf802a2177effb98894f47aab6ab6a1b9696/distributions/otelcol-otlp/manifest.yaml#L9-L21

@jade-guiton-dd would you like to take this one?

Sure.

Fixed by #663


IOA Support

IOA Support

Enhancement

Bandit analysis
BANDIT ANALYSIS RESULTS SHOULD BE POSTED
HERE. PLEASE REVIEW CONTRIBUTING.md FOR
MORE DETAILS ON GENERATING BANDIT RESULTS

Added features and functionality

New API module CustomIoaApiModule
New wrappers IoaRuleGroup, CustomIoaRule
More stuff still being worked on

Feature Checklist

Custom IOA Rule Groups

[x] Create rule group(s)

[x] implemented
[x] documented
[x] tested

[x] Query rule groups

[x] implemented
[x] documented
[x] tested

[x] Delete rule group(s)

[x] implemented
[x] documented
[x] tested

[x] Update existing rule group details

[x] implemented
[x] documented
[x] tested

[ ] Assign a rule group to a prevention policy

[ ] implemented
[ ] documented
[ ] tested

Custom IOA Rules

[x] Create new rules (implemented via rule group create/update)
[x] Updating existing rules (implemented via rule group update)
[x] Delete rules (implemented via rule group update)

Current issues

Design issue of overlapping filters across API modules

e.g. Hosts has platform_name:'Windows' whereas equivalent in IOA is platform:'windows'
Decided that this issue should be deferred as it's a big architectural change, this PR will not ship with any IOA filters (more info here: https://github.com/CrowdStrike/caracara/issues/42)

Slightly smaller design issue of global sort

caracara/common/sorting.py has SORT_ASC and SORT_DSC, which sorts by precedence, but not all modules have a precedence (e.g. this one!)
Decided that this issue can just be ignored for now, since it's non-blocking

I have not forgotten about this PR! Once I get some time I am going to clean this up and get it merged. I want this functionality in Caracara ASAP


[stable/redmine] Option to customize security context

What this PR does / why we need it:
PR allows custom securityContext for stable/redmine.
Special notes for your reviewer:
This PR does not change current behavior.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] DCO signed
[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] Title of the PR starts with chart name (e.g. [stable/mychartname])

/ok-to-test
/lgtm


Fix unit tests

relates to - https://github.com/Arduino-CI/arduino_ci/issues/258

fixed as it runs now...

fixed as it runs now...


WASAPI Audio not working in BackGround Task

We are developing a VoIP Application and have a need to process the incoming call in the background beyond 30 seconds but we notice that background task gets suspended after 30 seconds on Windows 10 Mobile when we run this from Visual Studio debugger and it doesn't play any Audio in Background when we launch the app and put it in background, but the same code is working fine on the desktop. We are using WASAPI to record & play the audio.
I have uploaded the modified Sample project in
https://drive.google.com/file/d/0B21RgZ6oQIFWckVLWGZvOFAxVjg/view?usp=sharing

WASAPI is not supported from a background task in UWP.  It works in most cases on desktop only because we have different background policies there that allow your task to run longer than on mobile.
The supported approach to background audio is shown here:
https://github.com/Microsoft/Windows-universal-samples/tree/master/Samples/BackgroundAudio
You need to use BackgroundMediaPlayer. As you are developing a VoIP app you most likely will need to combine that with MediaStreamSource if you have a custom protocol and media container.  If there is a specific reason you must use WASAPI it can work inside the background audio task above provided you periodically play audio with the media player.

Hi Aaron,
Thank you for your quick reply.
We have  tried BackgroundMediaPlayer but this worked when the API is called from foreground and then moved to background, but this didn’t work when I called this from background task.
Regards,
Jeethan

I need more details.
Did you try running the sample I linked? Did that work?
Background audio is only supported using a background audio task as demonstrated by the sample. If you are trying to do background audio from within any other task type it will not work because we go out of our way to prevent it.

Other things to check-- that you added the correct audio task extension entry to your package.appxmanifest and that you are setting up your media source from the task and not the foreground. You may also need to bind to the SMTC.
Please refer to our documentation here:
https://msdn.microsoft.com/en-us/library/windows/apps/mt282140.aspx

Hi  Aaron,
If we acquire the audio channel in the foreground and keep it active in the background,then if we receive a GSM incoming call and after user has end the GSM call, would the background tasks still be able to play the audio.
if not, how can we play the audio again without moving the app into foreground.

All setup of the background audio source must be performed from inside the background task as the sample shows. You have to pass messages from the foreground to the background to setup the playback source. The documentation I linked explains this architecture. We do not support setting up audio sources in the foreground and then continuing to play in the background today. You must host the audio source from the background to begin with.
The only alternative is to use a "background capable media" audio category from a MediaElement or video tag.
https://msdn.microsoft.com/en-us/library/windows/apps/hh452730.aspx
This approach requires more resources and may only work well on desktop devices. We do not currently intend to support this approach in the future.

There is a walkthrough of the background audio sample here:
https://blogs.windows.com/buildingapps/2016/01/13/the-basics-of-background-audio/


[BUG]

Describe the bug
zenml installation error.
To Reproduce
Steps to reproduce the behavior:
pip install zenml
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Stack Trace
ERROR: Cannot install zenml==0.1.0 and zenml==0.1.1 because these package versions have conflicting dependencies.

The conflict is caused by:
    zenml 0.1.1 depends on tfx==0.25.0
    zenml 0.1.0 depends on tfx==0.25.0

** Context (please complete the following information):**

OS: [e.g. windows 10]
Python Version: [3.9.5]
ZenML Version: latest

Additional information
Add any other context about the problem here.

Hi @huiwenhan , this issue is caused currently because we support Python >=3.6 < 3.9 therefore, please try to use a supported Python version between that ramge. 3.9.5 support will hopefully arrive soon

I found that I'm unable to install zenml on any version of Python, even within the range of >=3.6 < 3.9. I get the same error message / stack trace as the OP.

Ok we're investigating. Thanks @strickvl  ;-)

Hey @huiwenhan and @strickvl , we have an issue regarding our dependencies on Python <3.9. We are investigating it at the moment and we will update this thread as it develops.
As a temporary solution, I have tested the installation with two clean versions of Python, 3.6.9 and 3.8.2 respectively, which seems to solve the dependency problem in the installation. Let us know if it works for you as well or if there are any other issues.

@bcdurak I got it installing and init working with 3.6.9, but only when using raw pip install.
When I did a pipenv install zenml, I got the following error message:
Adding zenml to Pipfile's [packages]...
✔ Installation Succeeded
Pipfile.lock not found, creating...
Locking [dev-packages] dependencies...
Locking [packages] dependencies...
Building requirements...
Resolving dependencies...
✘ Locking Failed!
[ResolutionFailure]:   File "/usr/local/Cellar/pipenv/2021.5.29/libexec/lib/python3.9/site-packages/pipenv/resolver.py", line 741, in _main
[ResolutionFailure]:       resolve_packages(pre, clear, verbose, system, write, requirements_dir, packages, dev)
[ResolutionFailure]:   File "/usr/local/Cellar/pipenv/2021.5.29/libexec/lib/python3.9/site-packages/pipenv/resolver.py", line 709, in resolve_packages
[ResolutionFailure]:       requirements_dir=requirements_dir,
[ResolutionFailure]:   File "/usr/local/Cellar/pipenv/2021.5.29/libexec/lib/python3.9/site-packages/pipenv/resolver.py", line 692, in resolve
[ResolutionFailure]:       req_dir=requirements_dir
[ResolutionFailure]:   File "/usr/local/Cellar/pipenv/2021.5.29/libexec/lib/python3.9/site-packages/pipenv/utils.py", line 1405, in resolve_deps
[ResolutionFailure]:       req_dir=req_dir,
[ResolutionFailure]:   File "/usr/local/Cellar/pipenv/2021.5.29/libexec/lib/python3.9/site-packages/pipenv/utils.py", line 1110, in actually_resolve_deps
[ResolutionFailure]:       resolver.resolve()
[ResolutionFailure]:   File "/usr/local/Cellar/pipenv/2021.5.29/libexec/lib/python3.9/site-packages/pipenv/utils.py", line 835, in resolve
[ResolutionFailure]:       raise ResolutionFailure(message=str(e))
[pipenv.exceptions.ResolutionFailure]: Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  First try clearing your dependency cache with $ pipenv lock --clear, then try the original command again.
 Alternatively, you can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
  Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: Could not find a version that matches tensorflow!=2.0.*,!=2.1.*,!=2.2.*,!=2.2.*!=2.3.*,!=2.3.*,!=2.5.*,<2.5,<3,==2.4.1,>=1.15.2,>=2.6.0 (from zenml==0.3.8->-r /var/folders/49/7x17fsrn4knfk852z31cs_vm0000gn/T/pipenv21um7kftrequirements/pipenv-4_56wm4q-constraints.txt (line 2))
Tried: 0.12.1, 1.0.0, 1.1.0, 1.2.0, 1.2.1, 1.3.0, 1.4.0, 1.4.1, 1.5.0, 1.5.1, 1.6.0, 1.7.0, 1.7.1, 1.8.0, 1.9.0, 1.10.0, 1.10.1, 1.11.0, 1.12.0, 1.12.2, 1.12.3, 1.13.1, 1.13.2, 1.14.0, 1.15.0, 1.15.2, 1.15.3, 1.15.4, 1.15.5, 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.3.4, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.5.0, 2.5.1, 2.6.0
Skipped pre-versions: 1.1.0rc0, 1.1.0rc1, 1.1.0rc2, 1.2.0rc0, 1.2.0rc1, 1.2.0rc2, 1.3.0rc0, 1.3.0rc1, 1.3.0rc2, 1.4.0rc0, 1.4.0rc1, 1.5.0rc0, 1.5.0rc1, 1.6.0rc0, 1.6.0rc1, 1.7.0rc0, 1.7.0rc1, 1.8.0rc0, 1.8.0rc1, 1.9.0rc0, 1.9.0rc1, 1.9.0rc2, 1.10.0rc0, 1.10.0rc1, 1.11.0rc0, 1.12.0rc0, 1.12.0rc1, 1.12.0rc2, 1.13.0rc0, 1.13.0rc1, 1.13.0rc2, 1.14.0rc0, 1.14.0rc1, 1.15.0rc0, 1.15.0rc1, 1.15.0rc2, 1.15.0rc3, 2.0.0a0, 2.0.0b0, 2.0.0b1, 2.0.0rc0, 2.0.0rc1, 2.0.0rc2, 2.1.0rc0, 2.1.0rc1, 2.1.0rc2, 2.2.0rc0, 2.2.0rc1, 2.2.0rc2, 2.2.0rc3, 2.2.0rc4, 2.3.0rc0, 2.3.0rc1, 2.3.0rc2, 2.4.0rc0, 2.4.0rc1, 2.4.0rc2, 2.4.0rc3, 2.4.0rc4, 2.5.0rc0, 2.5.0rc1, 2.5.0rc2, 2.5.0rc3, 2.6.0rc0, 2.6.0rc1, 2.6.0rc2
There are incompatible versions in the resolved dependencies:
  tensorflow!=2.0.*,!=2.1.*,!=2.2.*!=2.3.*,<3,>=1.15.2 (from tensorflow-model-analysis==0.30.0->tfx==0.30.0->zenml==0.3.8->-r /var/folders/49/7x17fsrn4knfk852z31cs_vm0000gn/T/pipenv21um7kftrequirements/pipenv-4_56wm4q-constraints.txt (line 2))
  tensorflow!=2.0.*,!=2.1.*,!=2.2.*,!=2.3.*,!=2.5.*,<3,>=1.15.2 (from tfx==0.30.0->zenml==0.3.8->-r /var/folders/49/7x17fsrn4knfk852z31cs_vm0000gn/T/pipenv21um7kftrequirements/pipenv-4_56wm4q-constraints.txt (line 2))
  tensorflow!=2.0.*,!=2.1.*,!=2.2.*,!=2.3.*,<2.5,>=1.15.2 (from tensorflow-transform==0.30.0->tfx==0.30.0->zenml==0.3.8->-r /var/folders/49/7x17fsrn4knfk852z31cs_vm0000gn/T/pipenv21um7kftrequirements/pipenv-4_56wm4q-constraints.txt (line 2))
  tensorflow!=2.0.*,!=2.1.*,!=2.2.*,!=2.3.*,<3,>=1.15.2 (from tensorflow-data-validation==0.30.0->tfx==0.30.0->zenml==0.3.8->-r /var/folders/49/7x17fsrn4knfk852z31cs_vm0000gn/T/pipenv21um7kftrequirements/pipenv-4_56wm4q-constraints.txt (line 2))
  tensorflow!=2.0.*,!=2.1.*,!=2.2.*,!=2.3.*,<3,>=1.15.2 (from tfx-bsl==0.30.0->tfx==0.30.0->zenml==0.3.8->-r /var/folders/49/7x17fsrn4knfk852z31cs_vm0000gn/T/pipenv21um7kftrequirements/pipenv-4_56wm4q-constraints.txt (line 2))
  tensorflow<3,>=2.6.0 (from tensorflow-serving-api==2.6.0->tfx==0.30.0->zenml==0.3.8->-r /var/folders/49/7x17fsrn4knfk852z31cs_vm0000gn/T/pipenv21um7kftrequirements/pipenv-4_56wm4q-constraints.txt (line 2))
  tensorflow==2.4.1 (from zenml==0.3.8->-r /var/folders/49/7x17fsrn4knfk852z31cs_vm0000gn/T/pipenv21um7kftrequirements/pipenv-4_56wm4q-constraints.txt (line 2))

I get the same message when using pipenv install zenml using Python 3.8.2.
As the error message suggests, I can run it with the --skip-lock flag, but that isn't really solving the problem. I guess pipenv is stricter or runs some dependency checks earlier than pip?
In any case, at least a straightforward pip install zenml works on those two versions that you specified. I can at least confirm that.

Hey @strickvl, I am happy to hear that the straightforward installation is working.
As for the pipenv installation on 3.8.2, we need to investigate the issue a bit further. I will update the thread when we have more insight.

I reproduced the issue of the quickstart not working.
Steps taken:

pip install zenml
git init
zenml init
created a .py file into which I put (verbatim copy) the code listed in step 2 of the quickstart
ran the file

I didn't get the dataset download issue that @bcdurak you said you had. Instead, I got the following error:
2021-09-13 16:45:44,361 — zenml.pipelines.base_pipeline — INFO — Pipeline Quickstart created.
2021-09-13 16:45:44,361 — zenml.datasources.base_datasource — INFO — Datasource Pima Indians Diabetes Dataset created.
2021-09-13 16:45:44,378 — zenml.pipelines.training_pipeline — INFO — Datasource Pima Indians Diabetes Dataset has no commits. Creating the first one..
2021-09-13 16:45:44,378 — zenml.pipelines.base_pipeline — INFO — Pipeline<PHONE_NUMBER>378 created.
2021-09-13 16:45:44,995 — zenml.datasources.csv_datasource — INFO — Matched 1: ['gs://zenml_quickstart/diabetes.csv']
2021-09-13 16:45:44,995 — zenml.datasources.csv_datasource — INFO — Using header from file: gs://zenml_quickstart/diabetes.csv.
2021-09-13 16:45:45,641 — zenml.datasources.csv_datasource — INFO — Header: ['times_pregnant', 'pgc', 'dbp', 'tst', 'insulin', 'bmi', 'pedigree', 'age', 'has_diabetes'].
2021-09-13 16:45:48,659 — apache_beam.internal.gcp.auth — WARNING — Unable to find default credentials to use: The Application Default Credentials are not available. They are available if running in Google Compute Engine. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
Connecting anonymously.
2021-09-13 16:45:49,408 — root — WARNING — Make sure that locally built Python SDK docker image has Python 3.8 interpreter.
Traceback (most recent call last):
  File "pima-test.py", line 45, in <module>
    training_pipeline.run()
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/zenml/utils/analytics_utils.py", line 177, in inner_func
    result = func(*args, **kwargs)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/zenml/pipelines/base_pipeline.py", line 457, in run
    self.run_config(config)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/zenml/pipelines/base_pipeline.py", line 378, in run_config
    self.backend.run(config)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/zenml/backends/orchestrator/base/orchestrator_base_backend.py", line 108, in run
    tfx_pipeline = self.get_tfx_pipeline(config)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/zenml/backends/orchestrator/base/orchestrator_base_backend.py", line 60, in get_tfx_pipeline
    component_list = zen_pipeline.get_tfx_component_list(config)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/zenml/pipelines/training_pipeline.py", line 88, in get_tfx_component_list
    self.datasource_commit_id = self.datasource.commit()
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/zenml/datasources/base_datasource.py", line 153, in commit
    data_pipeline.run()
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/zenml/utils/analytics_utils.py", line 177, in inner_func
    result = func(*args, **kwargs)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/zenml/pipelines/base_pipeline.py", line 457, in run
    self.run_config(config)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/zenml/pipelines/base_pipeline.py", line 378, in run_config
    self.backend.run(config)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/zenml/backends/orchestrator/base/orchestrator_base_backend.py", line 109, in run
    ZenMLLocalDagRunner().run(tfx_pipeline)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/zenml/backends/orchestrator/base/zenml_local_orchestrator.py", line 97, in run
    component_launcher.launch()
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/tfx/orchestration/portable/launcher.py", line 431, in launch
    executor_output = self._run_executor(execution_info)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/tfx/orchestration/portable/launcher.py", line 325, in _run_executor
    executor_output = self._executor_operator.run_executor(execution_info)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/tfx/orchestration/portable/python_executor_operator.py", line 141, in run_executor
    return run_with_executor(execution_info, executor)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/tfx/orchestration/portable/python_executor_operator.py", line 65, in run_with_executor
    result = executor.Do(execution_info.input_dict, output_dict,
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/zenml/components/data_gen/executor.py", line 56, in Do
    datasource.process(
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/zenml/datasources/csv_datasource.py", line 90, in process
    p | 'ReadFromText' >> beam.io.ReadFromText(
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/pipeline.py", line 585, in __exit__
    self.result = self.run()
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/pipeline.py", line 564, in run
    return self.runner.run_pipeline(self, self._options)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/runners/direct/direct_runner.py", line 131, in run_pipeline
    return runner.run_pipeline(pipeline, options)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 195, in run_pipeline
    self._latest_run_result = self.run_via_runner_api(
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 206, in run_via_runner_api
    return self.run_stages(stage_context, stages)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 384, in run_stages
    stage_results = self._run_stage(
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 646, in _run_stage
    self._run_bundle(
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 769, in _run_bundle
    result, splits = bundle_manager.process_bundle(
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 1080, in process_bundle
    result_future = self._worker_handler.control_conn.push(process_bundle_req)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/runners/portability/fn_api_runner/worker_handlers.py", line 378, in push
    response = self.worker.do_instruction(request)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/runners/worker/sdk_worker.py", line 601, in do_instruction
    return getattr(self, request_type)(
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/runners/worker/sdk_worker.py", line 639, in process_bundle
    bundle_processor.process_bundle(instruction_id))
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/runners/worker/bundle_processor.py", line 996, in process_bundle
    input_op_by_transform_id[element.transform_id].process_encoded(
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/runners/worker/bundle_processor.py", line 222, in process_encoded
    self.output(decoded_value)
  File "apache_beam/runners/worker/operations.py", line 351, in apache_beam.runners.worker.operations.Operation.output
  File "apache_beam/runners/worker/operations.py", line 353, in apache_beam.runners.worker.operations.Operation.output
  File "apache_beam/runners/worker/operations.py", line 215, in apache_beam.runners.worker.operations.SingletonConsumerSet.receive
  File "apache_beam/runners/worker/operations.py", line 823, in apache_beam.runners.worker.operations.SdfProcessSizedElements.process
  File "apache_beam/runners/worker/operations.py", line 832, in apache_beam.runners.worker.operations.SdfProcessSizedElements.process
  File "apache_beam/runners/common.py", line 1240, in apache_beam.runners.common.DoFnRunner.process_with_sized_restriction
  File "apache_beam/runners/common.py", line 732, in apache_beam.runners.common.PerWindowInvoker.invoke_process
  File "apache_beam/runners/common.py", line 870, in apache_beam.runners.common.PerWindowInvoker._invoke_process_per_window
  File "apache_beam/runners/common.py", line 1368, in apache_beam.runners.common._OutputProcessor.process_outputs
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/io/textio.py", line 163, in read_records
    with self.open_file(file_name) as file_to_read:
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/io/filebasedsource.py", line 172, in open_file
    return FileSystems.open(
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/io/filesystems.py", line 244, in open
    return filesystem.open(path, mime_type, compression_type)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/io/gcp/gcsfilesystem.py", line 177, in open
    return self._path_open(path, 'rb', mime_type, compression_type)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/io/gcp/gcsfilesystem.py", line 138, in _path_open
    raw_file = gcsio.GcsIO().open(path, mode, mime_type=mime_type)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/io/gcp/gcsio.py", line 223, in open
    downloader = GcsDownloader(
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/io/gcp/gcsio.py", line 585, in __init__
    project_number = self._get_project_number(self._bucket)
  File "/Users/strickvl/.local/share/virtualenvs/pima-EMmKrcqa/lib/python3.8/site-packages/apache_beam/io/gcp/gcsio.py", line 166, in get_project_number
    self.bucket_to_project_number[bucket] = bucket_metadata.projectNumber
AttributeError: 'NoneType' object has no attribute 'projectNumber'

I don't fully understand what's going on here, but I can dig into it tomorrow.

So after some research, we figured out that the apache-beam==2.32.0 version caused the above error @alex-zenml. To fix, please downgrade apache-beam for now like so:
pip install apache-beam==2.28.0

Hope that fixes the issue! We'll make sure to fix it in the next release for sure.


请问如何不通过web页面修改配置

Description
想通过命令行修改配置，直接修改文件.ddns_go_config.yaml不生效，请问有什么办法不通过web页面也能修改配置吗
Problem
No response
Other Description
No response
Checklist

[X] I am using the latest version and have confirmed that the feature is not yet implemented in the latest version
[X] I have searched for similar feature requests before submitting this one

直接修改后需要重启ddns-go


How to get response in object using SQL ElasticSearch, I am close but still not getting  exact syntax

I have uploaded users in elastic search, now I want to get particular user by username.
I want to use elastic using SQL to retrieve data.
I have written following function, please let me know how can I get response in [User] c# object.
Any way to get it auto mapped to my required object?
Please help me with syntax.
  public static User GetUserByUserName()
    {
        var client = new ElasticConnectionManager().GetClient("users");
        var query = "SELECT * FROM users where username = 'DummyStudent_6610'";

        var sqlRequest = new QuerySqlRequest();
        sqlRequest.Query = query;
        sqlRequest.Format = "json";

        var response = client.QuerySql(sqlRequest);
        //How to convert to User object?

        return;
    }

Stackoverflow Link for same question:
https://stackoverflow.com/questions/53746080/elastic-search-getting-response-in-object

Hi @nileshpore ,
We reserve GitHub Issues for bug reports and feature requests.
In order for your question to get the attention it deserves, the best place to ask it would be the Elastic Discourse forums at https://discuss.elastic.co/c/elasticsearch. Not only do more folks view the forums than the GitHub Issues list, and hence it is more likely to receive attention, but the forums are also geared towards being able to search previous questions and answers, making it a much more valuable archive for future question askers.
Thanks!


Fix KVM import and list unmanaged VMs

Description
This PR fixes part (issues 2 and3) of #8439 and depends on #8433
1 - Fix of VM insert for VMs with StorPool volumes
2 - Fix of the list/insert unmanaged VMs with RBD volumes
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[X] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[X] Minor
[ ] Trivial

How Has This Been Tested?
manually tested

@blueorangutan package

@shwstppr a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 8202

@blueorangutan test

@shwstppr a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

[SF] Trillian test result (tid-8725)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 46357 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr8445-t8725-kvm-centos7.zip
Smoke tests completed. 119 look OK, 2 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_02_trigger_shutdown
Failure
336.70
test_safe_shutdown.py

test_07_deploy_kubernetes_ha_cluster
Failure
3611.63
test_kubernetes_clusters.py

test_08_upgrade_kubernetes_ha_cluster
Failure
0.04
test_kubernetes_clusters.py

test_09_delete_kubernetes_ha_cluster
Failure
0.04
test_kubernetes_clusters.py

test_10_vpc_tier_kubernetes_cluster
Failure
42.62
test_kubernetes_clusters.py

ContextSuite context=TestKubernetesCluster>:teardown
Error
90.87
test_kubernetes_clusters.py

@blueorangutan package

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 8251

@blueorangutan package

@nvazquez a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 8256


Potential issue with discovery

I'm using Mosquitto and the auto-discovery for home assistant. It looks like the entities are picked up, but on the integrations page, when selecting "MQTT", I see a page that says "Entities without devices" that lists all my ring sensors. Is that correct or is there an extra step I need to take to associate them to a device?

There's nothing to do, and everything is working as expected.  I don't currently send any device info as part of the auto discovery, although it is something on my to-do list so I would consider it more of an enhancement request than an actual issue.
Basically, device info is a way to identify the physical device and associate it with it's available entities, so, for example, if a single physical device has two sensors, like the freeze/flood sensor, I could send device info and Home Assistant would recognize it as a single device with two sensors vs right now where it just recognizes it as two separate entities.  From a functional perspective, it doesn't change a whole lot, although it might make the GUI categorize devices/entities a little more clearly without as much manual effort.
In your case each of our physical devices only have a single entity anyway, so it really would make no practical difference.  I guess I could potentially expose the battery and tamper sensors as separate entities on the same device instead of including them as json attributes, but I think that would mostly just clutter up the interface.

@tsightler - thanks for the explanation about devices! I'm still new to HA and really appreciate it 😄


Launch Minecraft suspended

The project long-term needs to be able to hook functions which are called really early. This would be a significant thing for the project, and would solve one of the problems with the api running before it's possible to attach a debugger

Why not do what MCLauncher or Jiayi does, and download a seperate instance of the game somewhere else? Then you can create some kind of proxy launcher dll like I did on my NKHook project which allows me to run code right before the game starts running, but after its loaded into memory. This way you can apply your patches, scan all of the sigs, and much more before the game even does anything.

Why not do what MCLauncher or Jiayi does, and download a seperate instance of the game somewhere else? Then you can create some kind of proxy launcher dll like I did on my NKHook project which allows me to run code right before the game starts running, but after its loaded into memory. This way you can apply your patches, scan all of the sigs, and much more before the game even does anything.

For doing that. Wouldnt we need to find a dll the game calls to and doesnt import like 600 functions? Or would it make more sense to just auto generate most the the function from an import table and just add our own data onto it

Yea we would, but I'm sure we could pick a decent candidate.

I have implemented this via a proxy dll which spoofs being a required dll by the game. Only thing i havent done is make the launcher copy the proxy into the games install dir, and or download the required mc version which i plan to do


Update sv.js

formatatet is spelled wrong should be formatet
🔎 Overview
The translation is wrong the spelling should be formatet not formatatet
✔ Issues affected
Version:
vee-validate: 2.2.0
There is a spelling mistake in the Swedish translation of one of the validation error texts.
The file sv.js contains the following:
date_format: (field, [target]) => Fältet ${field} måste ha formatatet ${target}.
But the word "formatatet" does not exist in Swedish. It should in fact be "formatet" instead.
Use google translate to verify this is the case.

closes #2024

Looks good to me.

Thanks for the update, much appreciated!


Calibration superfluous edges

Addresses https://github.com/MetOffice/improver_suite/issues/1750
Description
Updates gridded calibration CLI to align itself with spot calibration, e.g. The CLI now takes a directory and it is responsible for identifying which files are required.
This is additionally driven by a desire to remove >day long offsets in the suite configurations, as these require handling before producing a Cylc graph
Related

https://github.com/MetOffice/improver_suite/pull/2376
https://github.com/metoppv/improver_test_data/pull/57

Testing:

[x] Rewrite acceptance tests (?)
[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

ping @gavinevans - you might be interested in this.

Thanks @SamGriffithsMO, this looks very promising 👍

Still wip

I am still looking for a performant method to extract the validity time from a netcdf, instead of from the filename
I need to write tests

I am still looking for a performant method to extract the validity time from a netcdf, instead of from the filename

100% agree in using metadata rather information encoded in the filepath if possible.
However.  Better metadata within the output of NetCDF to increase traceability is something I have been wanting to address the entire time I have been here (on the 'todo' so-to-speak).  If the metadata available right now isn't sufficient or deriving the validity time becomes performance inhibitive with the number of files involved, it might still be worth considering the filepath as a short term solution.  An excuse for us to look at enforcing traceability through metadata within improver.

@SamGriffithsMO, have you given thought as to how to incorporate this change? (implications for BoM, USAF etc.)
An option to consider might be to create two new CLI's and making no functional change to the existing two CLI's.  What you think?

Putting in to draft to address what Carwyn and I discussed offline. Move the loading to clize (more inline with other plugins), and therefore allow the plugin to run whether given specific cubes or the directories as planed here

Closing this due to the complexity of conditional loads with clize. Aiming to fix this with specialised dagrunner load plugins


Correction for arrays of more than 2 dimensions with $type

When using the type interpretation for arrays of more than 2 dimensions, on deserialization, an error is encountered.
There is a problem in the switch case that does not allow adding more than one comma between the brackets of System.xxxx [].
View issue #2591

Hi! Thanks for the fix.
I've made some small changes and added some tests. This PR is replaced by https://github.com/JamesNK/Newtonsoft.Json/pull/2610 which builds on your changes.


set wave height to 60px

I have this configuration inside a vue method:
      const el = document.getElementById("waveform");
      this.wave = WaweSurfer.create({
        container: el,
        waveColor: "black",
        progressColor: "crimson",
        height: 60
      });
      this.wave.load(this.trackURL);
      this.wave.on('ready', () => {
        this.showPreloader = false;
        this.isLoading = false;
        //this.trackDuration = this.wawe.getDuration();
        this.wave.play();
        this.isPlaying = true;
      });

I've set the height of the wave to 60px but it will not be loaded. The audio play works well. Is there a fix or it's a  bug of the library?

Setting the height works fine for me and I'm using vue too. Maybe try setting responsive: true or passing container as a string like '#waveform' to see if those make a difference.

I've found the issue, the problem is with the server where I fetch the
data. I've tried setting the backend to MediaElementWebAudio and then to
MediaElement, with the second option all works fine, I think that the
hearthis.at API use MediaElement
Il giorno mar 21 lug 2020 alle ore 19:01 sundays<EMAIL_ADDRESS>ha scritto:

Setting the height works fine for me and I'm using vue too. Maybe try
setting responsive: true or passing container as a string like '#waveform'
to see if those make a difference.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/katspaugh/wavesurfer.js/issues/2016#issuecomment-661984031,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMKZMUWA76PI5S37E2CXKQDR4XCXDANCNFSM4PDX5RNQ
.

I've found the issue,


[apimanagement][test] reduce polling 202 responses in recordings

as they still cost a lot of time even the polling interval is set to 0 in playback.  This PR removes most of the 202 responses while still keep some in order to test the polling.
when recording, it is probably better to set the polling interval to a large
number instead of using the default.

There's a bug in core-lro that results in more polling than we actually expect. #19479


Uncaught TypeError: Cannot read property 'offsetWidth' of null

When importing GLightbox as an ES6 module (e.g. import GLightbox from 'glightbox';) it spits out this error when clicking a link that matches the selector:

(No special config is used, only the selector option is passed into the GLightbox function)
Problem has to do with body not being available inside the GlightboxInit class.

Nopes, no solution yet. I eventually moved away from glightbox to https://github.com/sachinchoolur/lightgallery.js

Nopes, no solution yet. I eventually moved away from glightbox to https://github.com/sachinchoolur/lightgallery.js

Be careful with license for this plugin.

If you initiate the javascript script inside your body tag it'll work

I get the same error in Chrome v72
I just include the js file and call it like this.
document.addEventListener("DOMContentLoaded", function() {
	GLightbox({
		selector: 'lightbox'
	});
});

redefining the body variable in the method open() is a quick workaround.
if(body === null){
        body = document.body;
}

hi @d3pendent thank's for taking a look at this, i'll update the code asap to remove the body variable as it's only used twice so there's no point. i'll let you know when the update is published.

This issue has been fixed in the latest version v2.0.0, i'm closing this for now, feel free to open any new issues if you find a bug.


Fix widths

Make badges narrower by changing padding character count from 3 to 2, and also setting default number of padding chars to 0 due to the interest in producing more compact badges.

Using the code from @ahogen's gist here, here's a comparison of outputs against shields.io.
Anybadge:

Shields.io:

I would like feedback on this before I accept this PR - specifically the updated spacing and also the change of default num padding chars (was 0.5, now 0).

Tried out the fixed-widths branch this evening. I like it! Looks good!


Updating Programs

Updating New Programs

Thank-you! Could you please list your twitter here so I can send you a one month pentesterlab voucher for your contribution.

@bcdavidchou could you resolve the conflicts here?


Strange errors with EventEmmiter and Promise combination

My application is throwing a strange flow error that I cannot debug, or find a reason of.
The code of is as follows
import {EventEmitter} from 'events'; // given using browserify

class Foo extends EventEmitter {
}

function experiment(): Promise<Foo> {
    var foo: Foo = new Foo();
    var res: Promise<Foo> = Promise.resolve(foo);
    return res;
}

This produces the following error

(...): Foo
This type is incompatible with
/tmp/flow/flowlib_10182f91/lib/core.js:337:1,364:1: Promise

What is going on?

Interestingly, this code seems to work
function experiment(): Promise<Array<Foo>> {
    var foo: Foo = new Foo();
    var arrfoo: Array<Foo> = [foo];
    var res: Promise<Array<Foo>> = Promise.resolve(arrfoo);
    return res;
}

I can reproduce this and if seems like a bug. It's particularly curious that this bug seems to depend on the type parameter to Promise being imported. If I inline the class declaration into Foo, there is no error:
/* @flow */

declare class Foo {
  static listenerCount(emitter: events$EventEmitter, event: string): number;

  addListener(event: string, listener: Function): Foo;
  emit(event: string, ...args:Array<any>): boolean;
  listeners(event: string): Array<Function>;
  on(event: string, listener: Function): Foo;
  once(event: string, listener: Function): Foo;
  removeAllListeners(event?: string): Foo;
  removeListener(event: string, listener: Function): Foo;
  setMaxListeners(n: number): void;
}

function experiment(): Promise<Foo> {
  var foo: Foo = new Foo();
  var res: Promise<Foo> = Promise.resolve(foo);
  return res;
}

The above is OK.

Interesting, thanks @runn1ng for the repro and @samwgoldman for the additional analysis!

Here's another mostly similar reproduction case I ran into:
/* @flow */
// jshint ignore:start

import {EventEmitter} from 'events';

class Bar extends EventEmitter {
    constructor() {
        super();
    }
}

var pr = new Promise((resolve, reject) => {
    resolve(new Bar());
});

I cannot reproduce this bug anymore.

Nope, still can reproduce, reopening. It did not produce error first due to this bug
https://github.com/facebook/flow/issues/1410
but once I set up flow so it loaded EventEmitter definitions properly (instead of ignoring it because of the module events), it starting doing this again.

When I investigated more, it seems it has nothing to do with EventEmitters. Any time a class extends a class, that's declared in an external module, it does that.
It just happens that EventEmitter is probably the most extended class like that.
But when I tried that with any similar class, it did the same thing. It has to be from an external module from a definition file, and the returned class have to extend that class. Try, for example, net$Socket that is in node.js, etc.

It does not need to be from the lib/* flow definition file; it can be anything defined in [libs] in .flowconfig.

HA! I solved it in the most weird and roundabout way possible.
I created a file eventEmitter.js, in which I have a simple few line script that doesn't do anything in particular
import {EventEmitter} from 'events';
export class EventEmitterMine extends EventEmitter {
     constructor() {
          super();
     }
}

and in the files, describing classes extending EventEmitter, I just do this
import {EventEmitterMine} from './eventEmitter';
class MyClass extends EventEmitterMine {
     constructor(...) {
         super();
         ....
     }
}

and it starts working. Interestingly, this alone doesn't help, without creating the extra file. The EventEmitterMine has to be in another file than the extending class.
import {EventEmitter} from 'events';
export class EventEmitterMine extends EventEmitter {
     constructor() {
          super();
     }
}

class MyClass extends EventEmitterMine {
     constructor(...) {
         super();
         ....
     }
}

Hey, thanks for digging into the analysis. Are you able to come up with a repro that doesn't use eventemitter? A small isolated repro would really help nail this down.

Well the repro is easy... as I said, just replace EventEmitter with net$socket...
import {Socket} from 'net';

class Foo extends Socket {
}

function experiment(): Promise<Foo> {
    var foo: Foo = new Foo();
    var res: Promise<Foo> = Promise.resolve(foo);
    return res;
}

Exactly the same error (at least on my version... I haven't updated flow in a while)

And what really fixes it is having a small "helper" class, that sits in a separate file, and looks like this (this is the entire file)
/* @flow */
import {EventEmitter as EventEmitterOut} from 'events';
export class EventEmitter extends EventEmitterOut {
    constructor() {
        super();
    }
}

...and use that one instead of EventEmitter from node. Everything is then typechecked correctly and works correctly.

This is fixed a while ago.


feat(react): combobox

Purpose
Implement Combobox component
Approach
Extract OptionList out of Select for reusability, then create Combobox that reuses the former.
Mostly composable, small amount of repetition, the biggest difference is event bindings and what each does, not worth a propscalypse on CustomSelect for that.
Testing
Storybook.
Still in progress, please help, it's a huge component.
Risks

Arguable breaking change in Select.
I'd say it's not breaking because it's internals.

Non-React component is extremely complex and convoluted, not sure if even worth an HTML + CSS story.
Web component would be nice but we still don't do that

I did some more testing, I've found the following issues, and tried to detail more of the accessibility approach.

When the combobox is focussed to via keyboard, the options list shouldn’t display until the up or down cursor keys are pressed, or the user has started typing a word.  This is in-keeping with expected accessible patterns as described in the aria docs, as well as other implementations I've seen.  I know you were pushing back on this a bit Andre, but I think we need it for it to be properly usable and accessible.
On the vercel instance I’m testing on, Select appears to be broken (placeholder text or selected option not displaying).  Need to investigate if this is a breaking change due to combobox changes, or something unrelated.

Accessibility:
(Tested on Safari with Voiceover on Mac.)
Combobox needs aria attributes specified as explained here: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/combobox_role#specifications
It's hard for me to add roles and aria stuff to see how different things affect what's read out, so I'd suggest we start with the above recommendations, and iterate/improve from there.


ImportError: cannot import name 'generate_X_grid'

I successfuly installed the pygam package, but when I do
from pygam.utils import generate_X_grid
It gives this error:
Traceback (most recent call last):

 File "<ipython-input-23-58b7fe4be83a>", line 1, in <module>
   from pygam.utils import generate_X_grid

ImportError: cannot import name 'generate_X_grid'

What am doing wrong, or is it a bug? How to solve it?
Thanks
Tiago

@tiago-monge
generate_X_grid was moved.
it is now a method of any GAM object, so you can do
gam = GAM().fit(X, y)
gam.generate_X_grid(term=...)

it looks like you are referencing some out-of-date usage.
where did you read that?
sorry for the confusion,
Dani

ahh is that from the CodeBurst tutorial?

Thanks for the prompt answer. Yes, I was following the CodeBurst tutorial. I'll try with the new approach.

cool,
ok we will have to update/change that tutorial.


adding test case for #899

[ ] Closes #899 (Replace xxxx with the Github issue number)
[ ] Tests added: test_multiindex_loc_str_tuple

I currently only added the tests.
Currently I don't know any solution to fix the issue.
See #899

Currently I don't know any solution to fix the issue.

See what I wrote here and try that out.
https://github.com/pandas-dev/pandas-stubs/issues/899#issuecomment-2032055407

Currently I don't know any solution to fix the issue.

See what I wrote here and try that out. #899 (comment)

I did and put the result in: https://github.com/pandas-dev/pandas-stubs/issues/899#issuecomment-2034348040

Ready to be merged


Add runtimeWarn() as public function

Unfortunately without XCTest support

Moving #if DEBUG to the file scope seems better in our case, maybe we can create a todo not to forget that when we update the package.


[modules/go] re-write go vet target

what
use go too vet $dir to vet code
why
go vet command require:

named files must all be in one directory; have ...

Should fix https://github.com/cloudposse/github-authorized-keys/issues/29

But we need to exclude the vendor folder since we have to control over the formatting of 3rd party code. Will this automatically exclude that?

@osterman hm, you're right.
i'll bring old solution with find, but using go tool vet


How to change the colour of the mask

Here is my outcome.

I want to get a white and black jpg, what can i do? Thanks!!!!

The mask doesn't have a color. You're using something like matplotlib which is providing the default yellow (1) and purple (0) cmap. The mask is only a single binary channel, with 1 being where something is. If you want black and white, just do this:
mask[mask == 1] =255
plt.imsave(arr=mask, fname="mask.jpg")

Excuse me, where should i put the code in? I put them  after function save_mask_data(output_dir, masks, boxes_filt, pred_phrases) in grounded_sam_demo.py, but it does not work...

The mask doesn't have a color. You're using something like matplotlib which is providing the default yellow (1) and purple (0) cmap. The mask is only a single binary channel, with 1 being where something is. If you want black and white, just do this:
mask[mask == 1] =255
plt.imsave(arr=mask, fname="mask.jpg")

Excuse me, where should i put the code in? I put them after function save_mask_data(output_dir, masks, boxes_filt, pred_phrases) in grounded_sam_demo.py, but it does not work...

The mask doesn't have a color. You're using something like matplotlib which is providing the default yellow (1) and purple (0) cmap. The mask is only a single binary channel, with 1 being where something is. If you want black and white, just do this:
mask[mask == 1] =255
plt.imsave(arr=mask, fname="mask.jpg")

Excuse me, where should i put the code in? I put them after function save_mask_data(output_dir, masks, boxes_filt, pred_phrases) in grounded_sam_demo.py, but it does not work...

You can use this repo: https://github.com/Nomination-NRB/SAM-webui


Make mono repo

It's probably a good idea to make SamOS a single repo containing:

https://github.com/thewoodfish/samaritan-2nd-wave
https://github.com/thewoodfish/s-chain-2nd-wave

Then add simple set-up instructions to launch samOS with the s-chain block-end locally.

this should work https://github.com/thewoodfish/SamaritanOS


#806 part 1: tear out import/export

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "remove_import_export" git@github.com:endophage/notary.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "remove_import_export" git@github.com:endophage/notary.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "remove_import_export" git@github.com:endophage/notary.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "remove_import_export" git@github.com:endophage/notary.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "remove_import_export" git@github.com:endophage/notary.git somewhere
$ cd somewhere
$ git rebase -i HEAD~2
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

\o/ so much red!  This is great, though I want to wait on reviewing the other parts before merging this.

No worries. Don't get too excited about it. Some amount of code will get added back in for part 3 to re-implement import/export

LGTM!


Not entirely clear how and where to use this

The plugin takes an object which is a configuration for a single micro frontend (module) with a set of activeWhen condition only for that micro frontend?
It includes references to an import map with multiple entries (which could include multiple other micro frontends?)
How would we use this plugin for an entire single-spa with 5-10 micro frontends published to our IMD?
Is there a sample application leveraging this plugin with a webpack configuration?
Thanks

The plugin takes an object which is a configuration for a single micro frontend (module) with a set of activeWhen condition only for that micro frontend?

Correct, as noted in the README.

It includes references to an import map with multiple entries (which could include multiple other micro frontends?)

This doesn't make sense to me. The importMapUrl option accepts only one URL, which is useful for enabling cross-microfrontend imports. The importMap option can be thought of as local overrides and isn't required. By their nature, yes import maps are going to point to multiple modules.

How would we use this plugin for an entire single-spa with 5-10 micro frontends published to our IMD?

You wouldn't. This is intended to enable a standalone environment for local development of individual applications, not the entirety of your org's microfrontends.
If you're asking how you would implement this across all of your microfrontends, I'd recommend creating a shared webpack config that they would all use so that they can get configuration changes as needed.

Is there a sample application leveraging this plugin with a webpack configuration?

Yep! Our react-microfrontends example has it as a separate npm script. Also, our shared webpack-config-single-spa might be a good reference too.
I'm going to close this as I think your question has been answered and there isn't an issue in the plugin, but feel free to ask any other questions.

Cool :) Thank you so much @filoxo
"This is intended to enable a standalone environment for local development of individual applications" wasn't entirely clear from the readme. Also sometimes a bit confusing what app vs micro frontend means.
"Parcels are an advanced feature of single-spa. We recommend that you use applications as the primary type of micro frontend in your architecture." So app is just an alias for micro frontend, not for the entire app of multiple micro frontends.
PS: Would be great if you could add an entry/section to the single-spa documentation site about this plugin. Didn't see it there when I searched for it. Cheers :)

Agreed - we could add it to the Local Development section of the recommended setup. I'll add it there. https://single-spa.js.org/docs/recommended-setup#local-development

Added a bit of documentation at https://github.com/single-spa/single-spa.js.org/pull/384

Thank you so much :)


🐛 Disable Table support

this was never meant to be enabled!
we don't ever want to support tables via markdown, instead we want to offer a different solution in future

Documentation on how to manage rules: https://github.com/markdown-it/markdown-it#manage-rules
List of rules: https://github.com/markdown-it/markdown-it/issues/289
Ghost has always deliberately not supported markdown tables because it's a compatibility nightmare, and we intend to offer something better in future.

Coverage increased (+0.04%) to 73.249% when pulling fc8b8097db6c57c747c9350c69fea534fabb3b48 on ErisDS:disable-tables into 2a73c798c53c6d589d3b5c5f2a1bc3dd815165d2 on TryGhost:master.

Leaving this in for now


Synthetic lockup

Closes: #XXX
Description

For contributor use:

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer

Closing because its all in #587, with several updates there


deal with wikipedia bug

When trying to use the wikipedia dataset I get the BUG:
Traceback (most recent call last):
  File "C:\repos\pmi_masking\create_pmi_masking_vocab.py", line 188, in <module>
    main()
  File "C:\repos\pmi_masking\create_pmi_masking_vocab.py", line 184, in main
    run_pipeline(**args.__dict__)
  File "C:\repos\pmi_masking\src\db_implementation\run_pipeline.py", line 66, in run_pipeline
    dataset = load_and_tokenize_dataset(dataset_name=dataset_name, tokenizer_name=tokenizer_name,
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\repos\pmi_masking\src\load_dataset.py", line 81, in load_and_tokenize_dataset
    dataset = dataset_name_to_load_function[dataset_name]()
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\repos\pmi_masking\src\load_dataset.py", line 29, in load_bookcorpus_and_wikipedia_dataset
    wiki = load_wikipedia_dataset()
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\repos\pmi_masking\src\load_dataset.py", line 23, in load_wikipedia_dataset
    return load_dataset(dataset_path, configuration_name, split=split)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\repos\pmi_masking\venv\Lib\site-packages\datasets\load.py", line 1791, in load_dataset
    builder_instance.download_and_prepare(
  File "C:\repos\pmi_masking\venv\Lib\site-packages\datasets\builder.py", line 902, in download_and_prepare
    self._save_info()
  File "C:\repos\pmi_masking\venv\Lib\site-packages\datasets\builder.py", line 2039, in _save_info
    import apache_beam as beam
ModuleNotFoundError: No module named 'apache_beam'

BUT, installing apache_beam could be problematic. maybe I can use this dataset without it? or use a different version? or not use it at all? try to figure this out

Before that, when I run .map with multiple processes, I would get an error since apache_beam and multiprocess have conflicting versions of dill

https://github.com/huggingface/datasets/issues/5232
https://github.com/huggingface/datasets/issues/5613
https://github.com/apache/beam/issues/24458

***Solution to try -- try to use python 3.9 instead of python 3.10 / 3.11
UPDATE: OK, so downgrading to python 3.9 seems to work, but I still got a memory allocation error when tokenizing the dataset, so I reduced the tokenizer batch size to 10_000 instead to see if it works better that way.
I also changed the datasets line in the requirement.txt to datasets[apache-beam].

Reopend 02.07.2023
I get this error:
Traceback (most recent call last):
File "", line 1, in
ModuleNotFoundError: No module named 'multiprocess'
And i think it is related to this issue:
https://github.com/uqfoundation/multiprocess/issues/61
so I'm kinda giving up on wikipedia , and I think that this could be a Windows bug. So I hope runing this on linux will work Alright.

I see two possible solutions for that:

maybe this bug only happens on windows, so using linux should be OK
simply use a dataset of a similar size to test this out, without having to deal with apache-beam


Graceful Master Takeover Split Brain

I'm having an issue with a minor split-brain when I do a graceful master takeover.
I've done two production master takeovers, and both times the old master cannot rejoin replication because it receives 2-7 transactions that the new master, and all replicas, do not.
Configuration: I have three nodes, one master and two replica master candidates.
MySQL Version: 5.7
Replication: Row Format, GTID enabled
VIP Management: ProxySQL + Keepalived
My VIP is mostly managed by ProxySQL. I have a three node cluster of ProxySQL servers that are managed by keepalived to elect a master that receives all updates (setup this way for HA).
Proxy SQL monitors the READ_ONLY setting on the cluster and uses the replication host groups feature to set the cluster master into the writer hostgroup, directing write queries to the master.
I also have a second, fallback VIP for a handful of services that don't like ProxySQL (most of them poorly written legacy code that is being replaced). This VIP is managed by keepalived, which uses the orchestrator-api to query for the cluster master every half second and adjust the VIP based on this.
My prefailover scripts are a notification script and a shutdown script that is used to STONITH the master in the event of a hard failure. The STONITH script does a system check to verify the server is fully online and takes about 6s to run. I could speed this up if it's the problem as it always checks the full system instead of aborting at the first success (look for server in proxysql, connect to server's direct mysql interface, run a hostname check through ssh, verify status of power outlets on rack PDU). We figure this is safe and accept the 6s delay.
When the switch succeeds and the old master immediately fails to rejoin replication. Orchestrator indicates that it has errant GTIDs. It always possesses between 1 and 7 transactions under it's own UUID that do not appear on the rest of the cluster, and by some luck there's almost always a table which receives an insertion on both old and new master such that distinct data receives the same ID, causing a collision.
I'm not sure what's wrong here. I'm coming from MHA which was always very careful about setting the master read only and letting it close out transactions, or STONITHing it, before setting the new master writable and triggering the IP Switchover scripts.
My parsing of the Orchestrator log seems to indicate that orchestrator brings the new master writable before the old master is set read only. This seems... iffy. Am I supposed to deal with quiescing the old master prior to failover manually? I could certainly have proxySQL offline the master, devise a mechanism to make my keepalived script detect and drop the VIP, manually read_only, wait for transactions to clear and then return to let Orchestrator finish the failover.
I guess I just assumed it was safe to let my VIPs switch when orchestrator flipped the read-only flags. Is this not the case?

Here is the output of the recovery audit for the takeover:
2019-03-27 18:23:46 | will handle DeadMaster event on mysql1:3306
-- | --
2019-03-27 18:23:46 | Running 3 PreFailoverProcesses hooks
2019-03-27 18:23:46 | Running PreFailoverProcesses hook 1 of 3: python3 /usr/local/bin/mysqlha-notify.py -c /etc/dbaha.conf --emergency -w info -s "Failover mysql-prod Start" -m "Failing mysql-prod away from failed master mysql1. 1 avaiable replicas." -o >> /var/log/orchestrator-recovery.log
2019-03-27 18:23:47 | Completed PreFailoverProcesses hook 1 of 3 in 433.767742ms
2019-03-27 18:23:47 | Running PreFailoverProcesses hook 2 of 3: python3 /usr/local/bin/mysqlha-shutdown.py --conf=/etc/dbaha.conf --command=shutdown --master=mysql1 -v --failure=graceful-master-takeover >> /var/log/orchestrator-recovery.log
2019-03-27 18:23:53 | Completed PreFailoverProcesses hook 2 of 3 in 6.024836989s
2019-03-27 18:23:53 | Running PreFailoverProcesses hook 3 of 3: python3 /usr/local/bin/mysqlha-notify.py -c /etc/dbaha.conf -w info -s "mysql1 Shutdown" -m "Shutdown of mysql1 complete as part of graceful-master-takeover from DeadMaster on mysql-prod" -o >> /var/log/orchestrator-recovery.log
2019-03-27 18:23:53 | Completed PreFailoverProcesses hook 3 of 3 in 389.010598ms
2019-03-27 18:23:53 | done running PreFailoverProcesses hooks
2019-03-27 18:23:53 | RecoverDeadMaster: will recover mysql1:3306
2019-03-27 18:23:53 | RecoverDeadMaster: masterRecoveryType=MasterRecoveryGTID
2019-03-27 18:23:53 | RecoverDeadMaster: regrouping replicas via GTID
2019-03-27 18:23:53 | RecoverDeadMaster: promotedReplicaIsIdeal(mysql3:3306)
2019-03-27 18:23:53 | RecoverDeadMaster: 1 postponed functions
2019-03-27 18:23:53 | checking if should replace promoted replica with a better candidate
2019-03-27 18:23:53 | + sanity check: found our very own server to promote; doing nothing
2019-03-27 18:23:53 | replace-promoted-replica-with-candidate: promoted instance mysql3:3306 requires no further action
2019-03-27 18:23:53 | promoted replica: mysql3:3306
2019-03-27 18:23:53 | RecoverDeadMaster: successfully promoted mysql3:3306
2019-03-27 18:23:53 | - RecoverDeadMaster: promoted server coordinates: mysql-bin.000057:131829962
2019-03-27 18:23:53 | - RecoverDeadMaster: will apply MySQL changes to promoted master
2019-03-27 18:23:53 | - RecoverDeadMaster: applying RESET SLAVE ALL on promoted master: success=true
2019-03-27 18:23:53 | - RecoverDeadMaster: applying read-only=0 on promoted master: success=true
2019-03-27 18:23:53 | Writing KV [mysql/master/mysql-prod:mysql3:3306 mysql/master/mysql-prod/hostname:mysql3 mysql/master/mysql-prod/port:3306 mysql/master/mysql-prod/ipv4:<IP_ADDRESS> mysql/master/mysql-prod/ipv6:]
2019-03-27 18:23:53 | - RecoverDeadMaster: applying read-only=1 on demoted master: success=true

The current orchestrator documentation says this about Graceful Takeover:
In a graceful takeover:

You indicate a server to promote.

- orchestrator turns your master to be read-only.
- orchestrator makes sure your designated server is caught up with replication.
- orchestrator promotes your designated server as the new master.
- orchestrator turns promoted server to be writable.

The operation can take a few seconds, during which time your app is expected to complain, seeing that the master is read-only.

This makes me believe that the old master goes read-only first.

Writes to the unfailed VIP begin failing against read_only status.
The new master is given time to catch up in replication.
The new master is made writable.

However, my log output leads me to believe the order is wrong:
2019-03-27 18:23:53 | - RecoverDeadMaster: applying read-only=0 on promoted master: success=true
2019-03-27 18:23:53 | Writing KV [mysql/master/mysql-prod:mysql3:3306 mysql/master/mysql-prod/hostname:mysql3 mysql/master/mysql-prod/port:3306 mysql/master/mysql-prod/ipv4:<IP_ADDRESS> mysql/master/mysql-prod/ipv6:]
2019-03-27 18:23:53 | - RecoverDeadMaster: applying read-only=1 on demoted master: success=true

Unless the log is not necessarily written in order, it seems like this is not what the documentation indicates should happen.
Attaching the output of the orchestrator.log file for the same event.
032719.182346.m3tm1takeover.log

Hi,
The graceful failover has logic that wraps the "standard" failovr. The line:
2019-03-27 18:23:53 | - RecoverDeadMaster: applying read-only=1 on demoted master: success=true

which you observe to be running after the failover, is part of the "standard" failover. However, the graceful failover sets the read_only flag way before that. So this is a 2nd, redundant time we apply read_only=1.
My immediate guess is that you have users with the SUPER privilege which continuously write to the old master. A user with SUPER is allowed to write even in face of read_only=1.
Consider setting "UseSuperReadOnly": true in your orchestrator config file: https://github.com/github/orchestrator/blob/master/docs/configuration-topology-control.md#usesuperreadonly

Hi,
Ah, I see that now listed way up by the pre-failure hooks. I didn't think to look up there, but you're obviously correct.
Your guess is also accurate. The specific user account which was creating the errant transactions did indeed have SUPER when it should not have. I missed this in my most recent user audit, so not only does this explain the issue, but it also highlights a potentially dangerous misconfiguration in our environment!
I will examine the SuperReadOnly setting as well. This seems useful as many of the service accounts used for backups and application monitoring require SUPER and this will help keep them in check.
As always, thank you for your exceptional support. You always provide timely, detailed feedback and I greatly appreciate it!


Implement FX

See https://github.com/Kava-Labs/crypto-rate-utils

Also see https://currencylayer.com/


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/55671

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/55956

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/56893

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58878

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/63334

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/67521

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/74698

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.


NPM Package

I think it would be very useful if the package is available in NPM.

Besides this, you'd need to submit it as well @pavei :P


Added Edge to a note in how-to-connect-sso-quick-start.md

I think it should also work with Edge.

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

#sign-off

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

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


chore: use line+html in default config

Turns out with only the html reporter no errors get displayed on the CI inside the logs. So we can either add line, dot or list as an additional reporter, I thought list might work the best.
Relates https://github.com/debs-obrien/debbie.codes/pull/253

Folding into https://github.com/microsoft/playwright/issues/13761


setup the provided template for this project

see step 2 at https://github.com/IHE/supplement-template/wiki/Getting-Started#step-by-step

once this is specialized according to step 2, I will set it up for CI build.


P UI: Added frontend publishing for bare-metal (git)

This PR adds the required tasks and CI for deploying the frontend to bare-metal git installs. Code by @wolflu05

Replaced by #5277


The VisVolume() function is not working

This is an issue related to the volume examples. Is it possible to generate a solid volume using a NURBS volume object and Visvolume()? All the volume examples in this repo have defined the bounding surfaces and then created a volume. I tried to create a cuboid using the NURBS volume object however, the render function is plotting the evaluation points instead of the solid.  How to get a proper 3D visualization of the solid?
This is the pdf form of my notebook.
NURBS_Solid.pdf

VisVolume is intended to render the points as it is the fastest way to render it. There is also a VisVoxel class which renders the voxels. There are some glitches in rendering the voxels, it is not perfect but representative. There is also possibility to extract the isosurface and render it, if you mean this by saying proper 3D visualization of the solid.
Please take a look at this example for more details on the methods available other than VisVolume:
https://github.com/orbingol/geomdl-examples/blob/master/volume/ex_planar_bspline.py

Thanks for your response. I wanted to have a visualization similar to the CAD packages, with shaded edges and surfaces. I will try out the alternatives that you suggested. Just a follow up question, is it possible to export the NURBS volume object to a CAD readable format such as ".IGES" or ".stp" for better visualization?

I am not sure whether IGES supports NURBS volumes or not. I guess it is only curves and surfaces. I haven't found precise references but I am guessing STEP also supports curves and surfaces only. Rhino supports an object named "Cage" which looks like NURBS volumes, but somehow it didn't work with OpenNURBS -- I don't remember why.
I've published another tool, rw3dm which can convert most geomdl objects into OpenNURBS/Rhino format.


Running CRA throw error of missing "extras" from pixi.js v5

Description
<EMAIL_ADDRESS>Attempted import error: 'extras' is not exported from 'pixi.js'.

Works in Storybook
Works with pixi.js 4
Doesn't work with CRA (create-react-app)

Steps to reproduce

git clone https://github.com/kresli/cra-react-pixi
yarn or npm install
yarn start

Additional info (please refer to provided repository)

<EMAIL_ADDRESS>"^4.8.6"
"@inlet/react-pixi": "^0.5.7",
"@types/react": "16.8.8",
"@types/react-dom": "16.8.3",
"pixi.js": "^5.0.0-rc.2",
"react": "^16.8.5"

Ah yes, Pixi v5 is not fully supported yet. (nothing to do with create-react-app though)
Feel free to create a PR, should be easy to fix. Some namespaces and implementations have slightly changed.

I've got the same issue with PIXI v5, I assume this hasn't be tackled yet ?

Hi @chrisella, I haven't got the time to make this lib PIXI v5 compliant. On the other hand it should be fairly simple. Feel free to create a PR and we'll work on it together :)

I did actually clone the repo and start taking a look last night, but quickly encountered issues just trying to install the npm dependencies with yarn :(
It seems you're using node-canvas-prebuilt which is 404'ing and from what I've read has been superseded, but unfortunately that means it's fairly hard for me to begin taking look without some significant time poking at the internals I suspect.
That said, if you know a reason I'd be getting this and any work-around etc then please do let me know and I can keep pressing forward.

Ah I see, canvas-prebuilt is only needed to support canvas in jsdom. It seems that replacing this with canvas package should fix the issue, see https://github.com/jsdom/jsdom#canvas-support. Haven't tested it though.
I'm currently busy working on another project, but I'll give it a proper look when I have time. In meantime feel free to fiddle around and see if you get it working ☺

Btw, you can use PIXI v5 stuff by using custom components. Here's an example https://codepen.io/inlet/pen/feddc8fa71e3b5afc6c3e4eda9cc83df

should be fixed by this PR https://github.com/inlet/react-pixi/pull/109
I've tested with pixijs 5.0.4 & 4.8.5 and both seem to work correctly

@rluncasu just check out the docs, you can find tuts and demos there.

This worked for me:
import * as PIXI from "pixi.js";
window.PIXI = PIXI;
import 'pixi-projection'; // or require("pixi-projection");

The only exception is if you wanna call PIXI.projection you have to call it like window.PIXI.projection
I hope this gets fixed soon, I guess the Pixi plugins should also support ES6 modules.

Hi @human-a,
This seems not related to react-pixi, see:
https://github.com/pixijs/pixi-projection#angularjs

Oops, sorry I commented on the wrong repo :D

No worries 😉


tests: Move random data generation methods from CometCastSuite to new DataGenerator class

Which issue does this PR close?

N/A
Rationale for this change

Start moving random data generation out of CometCastSuite and into a class that can be used from other test suites.
What changes are included in this PR?

How are these changes tested?

Existing tests

However, the CI is failing, you may need to take a look at that.

Yes, this change effectivey changed the seed and it has exposed new compatibility issues in existing tests. I am investigating.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 34.18%. Comparing base (14494d3) to head (cf779df).
Report is 9 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #426      +/-   ##
============================================
+ Coverage     34.02%   34.18%   +0.16%
+ Complexity      857      850       -7
============================================
  Files           116      116
  Lines         38565    38552      -13
  Branches       8517     8523       +6
============================================
+ Hits          13120    13178      +58
+ Misses        22691    22609      -82
- Partials       2754     2765      +11

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

Merged. Thanks @andygrove


Edit DOC: consistent imports (GH9886) part V

Updated - but no idea why this is such a messed up branch.

needs a rebase

@springcoil I don't really understand how you manage to such a mess of your commits :-) (we had better looked at it together yesterday)
Some things:

if you start to work on something new (eg updating the imports in merging.rst), no rebase or something is needed. Just be sure to start your branch from the latest upstream master. Rebasing is only needed once there are conflicts because other people have changed the same file. Which is not the case here at all.

To start a new branch from upstream master, just do:

git checkout master
git fetch upstream
git merge --ff-only upstream/master
git checkout -b new_branch

When you need to rebase (which will probably not be the case here if you did like above), simply do the following:

git fetch upstream
git checkout new_branch
git rebase upstream/master

and this should almost always work.

Don't close this PR, just try to clean up this branch and force push. To clean this up, do exactly the following:

git fetch upstream
git checkout merging
git rebase -i upstream/master
then in overview of commits, remove all commits apart from the last one 'updating the docs' (the only commit with the actual changes I think), and leave that one as 'pick'
git push -f origin merging

If you do exactly as above, this should be fine

Ok will do that thanks.
ᐧ
On Mon, Aug 31, 2015 at 12:45 PM, Joris Van den Bossche <
<EMAIL_ADDRESS>wrote:

@springcoil https://github.com/springcoil I don't really understand how
you manage to such a mess of your commits :-) (we had better looked at it
together yesterday)
Some things:

if you start to work on something new (eg updating the imports in
merging.rst), no rebase or something is needed. Just be sure to start your
branch from the latest upstream master. Rebasing is only needed once there
are conflicts because other people have changed the same file. Which is not
the case here at all.
To start a new branch from upstream master, just do:
git checkout master
git fetch upstream
git merge --ff-only upstream/master
git checkout -b new_branch

When you need to rebase (which will probably not be the case here if
you did like above), simply do the following:
git fetch upstream
git checkout new_branch
git rebase upstream/master
and this should almost always work.
Don't close this PR, just try to clean up this branch and force push. To
clean this up, do exactly the following:
git fetch upstream
git checkout merging
git rebase -i upstream/master
then in overview of commits, remove all commits apart from the last one 'updating the docs' (the only commit with the actual changes I think), and leave that one as 'pick'
git push -f origin merging
If you do exactly as above, this should be fine
—
Reply to this email directly or view it on GitHub
https://github.com/pydata/pandas/pull/10941#issuecomment-136330541.

--
Peadar Coyle
Skype: springcoilarch
www.twitter.com/springcoil
peadarcoyle.wordpress.com

Thanks for the help - @jreback and @jorisvandenbossche Ok @jorisvandenbossche all the checks passed. Is this ready to be merged?

Yep, thanks!


[Doc Migration] - Temporarily available at: https://tlb-lab.github.io/

Docs are being migrated from current hosting. Changes can take a day or two to propagate. In the meantime, there are available at:
https://tlb-lab.github.io/

The docs have returned home: https://graphein.ai/


chore: Add Semantic Conventions to the merge script

This is the Merge master PR that this change will cause https://github.com/open-telemetry/opentelemetry-sandbox-web-js/pull/42 for the inclusion of the semantic conventions package


Device unauthorized

What to do with this man ? :(
Multiple time replug, usb debugging enabled. Is there any way around it?

https://github.com/Genymobile/scrcpy/blob/master/FAQ.md#device-unauthorized

You need to enable usb debugging mode in developer options. After it run adb devices command. There you find Is your device is authorized or not. If there is device status then run scrcpy command and it will run.

I have two questions: 1) I want to connect two mobile devices simultaneously to the PC, could this be done? Would you explain to me how I could do it? 2) If I can connect a cell phone with a type C output to another cell phone with a type C output, I have the cable, and through this I can control the other mobile device that has a broken screen. Thanks in advance, those are my two questions.

In my case
"Settings" > "Developer options" > "Revoke USB debugging authorizations"
then I disable USB debugging Mode
and then enabled again in this case it will ask allow for this pc or machine then after that unauthorized error remove for me
and it is working fine :)
good luck for you

If someone stumbles upon this one day, just turn off usb debugging , turn it back on and allow connection from this pc when it asks on your phone.


DockerHub Image

Reason/Context
Please try answering few of those questions

Why we need this improvement?
It would be beneficial to developers to be able to run this locally and internally within organisations.

How will this change help?
Pushing the docker image for every new release to docker hub

What is the motivation?
Swagger Editor also provides this https://hub.docker.com/r/swaggerapi/swagger-editor/

Description
Please try answering few of those questions

What changes have to be introduced?

On release builds the versioned docker image would be built and pushed to docker hub

Will this be a breaking change?
no

How could it be implemented/designed?
as part of the GibHub build

moved issue to studio as it will be our new playground and the only official docker image we will provide for the studio, not playground

I mark this as a long-term issue.


Credit card not showing details

I have a form for entering credit card details. First time when i enter card shows all the details which I enter. When I submit the form if any error occurred during process I am showing the same form with same data. This time even though form contains data credit card not showing any data. I need to re enter the details again. How can I solve this ?

@rig1 How did you solve this?


IBM zSystems DFLTCC: Inline DLFTCC states into zlib states

Currently DFLTCC states are allocated using hook macros, complicating memory management. Inline them into zlib states and remove the hooks.

I didn't know about the empty struct restriction, thanks! I guess even if it were allowed, the compiler would still have to implicitly make it at least 1 byte in size in order to give it a distinct address. So I've added an #ifdef to omit the arch field.


Loss of frames with pjsip

Hello and TIA for good work!
I try to use pjsua (SIP application) from pjsip library with latest version of bluez-alsa (SCO profile).
The sound always interrupt, the conversation example here. I have some suspicions with incorrect buffer length of the buffer or drop the buffer before it finish.
The CPU load for pjsua is about 10% and 5% for bluez-alsa. So the problem is not performance.
aplay works fine on the same system with bluez-alsa, pjsua also works fine on the same system with PulseAudio.
How to debug and fix this error?
If to set pcm->frame_size to 15 bytes (calculated as 16) in bluealsa_hw_params function, the sound is almost continuous, but cracks appear.

The buffer size for aplay (works) fine:

../../../git/src/asound/bluealsa-pcm.c:366: Initializing HW
../../../git/src/asound/bluealsa-pcm.c:140: Requesting PCM open for 1C:48:F9:40:03:FB
../../../git/src/asound/bluealsa-pcm.c:157: Opening PCM FIFO (mode: WR): /var/run/bluealsa/hci0-1C:48:F9:40:03:FB-2-0
../../../git/src/asound/bluealsa-pcm.c:389: FIFO buffer size: 4096
../../../git/src/asound/bluealsa-pcm.c:394: Selected HW buffer: 8000 ?= 4 periods x 2000 bytes

And for pjsua:
../../../git/src/asound/bluealsa-pcm.c:140: Requesting PCM open for 1C:48:F9:40:03:FB
../../../git/src/asound/bluealsa-pcm.c:157: Opening PCM FIFO (mode: RO): /var/run/bluealsa/hci0-1C:48:F9:40:03:FB-2-1
../../../git/src/asound/bluealsa-pcm.c:394: Selected HW buffer: 1600 ?= 5 periods x 320 bytes
../../../git/src/asound/bluealsa-pcm.c:425: Prepared
../../../git/src/asound/bluealsa-pcm.c:366: Initializing HW
../../../git/src/asound/bluealsa-pcm.c:140: Requesting PCM open for 1C:48:F9:40:03:FB
../../../git/src/asound/bluealsa-pcm.c:157: Opening PCM FIFO (mode: WR): /var/run/bluealsa/hci0-1C:48:F9:40:03:FB-2-0
../../../git/src/asound/bluealsa-pcm.c:389: FIFO buffer size: 4096
../../../git/src/asound/bluealsa-pcm.c:394: Selected HW buffer: 2240 ?= 7 periods x 320 bytes

If to set pcm->frame_size to 15 bytes (calculated as 16)

Are you sure, that the frame_size is calculated as 16 bytes? Because it seems ridiculously wrong. It should be 2 bytes for mono and 4 bytes for stereo. If however it is calculated as 16 bytes, then it might a cause of trouble.

The CPU load for pjsua is about 10% and 5% for bluez-alsa. So the problem is not performance.

Actually this issue might be performance related. But the bottleneck in not a CPU, but an overall bluealsa performance/timing. The problem might be too small period. I've tried to set the minimum requirement for period size to 1024 bytes, but it is not respected... I remember that I've seen such an interruption in the audio by myself, but I can't remember with which application.
I'd like to reproduce this issue with the pjsua, however I don't know how to set it up :D - I've got no (zero, null, zilch) experience with VoIP. Could you give me a hint how to setup pjsua. Some "howto" article, or simple configuration. I was able to compile pjproject and that's all :).

Are you sure, that the frame_size is calculated as 16 bytes?

Sorry, forgot divided into 8 (snd_pcm_format_physical_width(io->format) = 16, io->channels = 1). So it 2 bytes. But changing this variable affects the sound interruption.
Ok, to reproduce this issue need to install VoIP server and compile pjproject.
I use AsteriskNOW Linux distro with Asterisk 11. It is free and based on Cent OS. Install on the any virtual machine (use free Oracle VM VirtualBox).
When it's done, FreePBX web interface will available by address (change to own IP address). It is need to add 2 users (Applications -> Extensions -> Add an Extension -> Generic CHAN SIP Device, set any value for User Extension field (for example 600), Display Name (for example User 600) and password in the Secret field (for example ab1234), press Submit and then Apply Config at the top of the page). When configure the network in Settings -> Asterisk SIP Settings tab (in Local Networks field, press Submit and Apply Settings).
The VoIP SIP server is ready. :-)
Then compile the PJSIP (I try 2.4.5 and 2.5.5 versions).
wget http://www.pjsip.org/release/2.6/pjproject-2.6.tar.bz2
tar xvjf pjproject-2.6.tar.bz2
cd ./pjproject-2.6/
./configure
make dep
make

To run PJSUA just run the command ./pjsip-apps/bin/pjsua-x86_64-unknown-linux-gnu after successful compilation.
When select _ (+a)    Add new accnt_:
>>> +a
Your SIP URL: (empty to cancel<EMAIL_ADDRESS>URL of the registrar: (empty to cancel): sip:<IP_ADDRESS>
Auth Realm: (empty to cancel): *
Auth Username: (empty to cancel): 600
Auth Password: (empty to cancel): ab1234

Just change credentials to own.
Repeat that on the second PC (add the second account):
>>> +a
Your SIP URL: (empty to cancel<EMAIL_ADDRESS>URL of the registrar: (empty to cancel): sip:<IP_ADDRESS>
Auth Realm: (empty to cancel): *
Auth Username: (empty to cancel): 601
Auth Password: (empty to cancel): ab1234

And make the call from first PC to the second:
m
(You currently have 0 calls)
Buddy list:
 -none-

Choices:
   0         For current dialog.
  -1         All 0 buddies in buddy list
  [1 - 0]    Select from buddy list
  URL        An URL
  <Enter>    Empty input (or 'q') to cancel
Make call<EMAIL_ADDRESS>
To answer the call, press a hot button and send 200 reply code on the second PC.
With bluez-alsa this issue reproduced, with pulseaudio no any problems. :-)

Did you manage to find out anything? Be may need my help?

Unfortunately not yet. When something pops out, or I will need some
assistance, I will write immediately :)

Hello! Are there any news?

Hi! I'm constantly working on it, and it seems, that it is a little bit harder than I thought. There is no much info on the net about the ALSA PCM I/O plugin architecture.... I'm making some progress, though :] However, it might take another week or two.

Hi.
If you're still using bluez-alsa try fresh master snapshot. I think, that finally I've made things right (commit ca72c1e). I wasn't able to test it with the PJSIP (I have failed to set it up right....), though.

Of course, I like bluez-alsa and still using it. Thank you very much for the fix! I will check it within a week.

Thanks in advance! No any problems with PJSIP with the latest master snapshot.

That's great! :tada:

How were you able to get PJSIP detect bluealsa devices?
It never detects for me and gives me an error of no default device exists. PJMEDIA_EAUD_NODEFDEV


Enable users to set names of schemas for storing temporary and/or metadata tables

VerdictContext now has a VerdictOption object, which stores user-configurable
options. For now, it only contains two options, setting names for
temporary and metadata schema
VerdictOption can parse 'verdictdbmetaschema' and
'verdictdbtempschema' keys in jdbc connection string or any
Properties object provided
Corresponding unit tests have been added
Updated version of maven-surefire-plugin to 2.22.0 in pom.xml

Codecov Report

Merging #203 into master will decrease coverage by 2.44%.
The diff coverage is 79.02%.

@@            Coverage Diff             @@
##           master     #203      +/-   ##
==========================================
- Coverage   73.77%   71.34%   -2.43%
==========================================
  Files         143      144       +1
  Lines        8536     8597      +61
  Branches     1357     1364       +7
==========================================
- Hits         6297     6133     -164
- Misses       1889     2117     +228
+ Partials      350      347       -3

Impacted Files
Coverage Δ

.../verdictdb/coordinator/SelectQueryCoordinator.java
93.03% <100%> (-0.87%)
:arrow_down:

...ava/org/verdictdb/metastore/ScrambleMetaStore.java
90.63% <100%> (-7.76%)
:arrow_down:

...va/org/verdictdb/coordinator/ExecutionContext.java
38.47% <47.06%> (-51.4%)
:arrow_down:

...main/java/org/verdictdb/commons/VerdictOption.java
83.88% <83.88%> (ø)

src/main/java/org/verdictdb/VerdictContext.java
75% <84.22%> (-2.41%)
:arrow_down:

.../verdictdb/core/sqlobject/CreateScrambleQuery.java
0% <0%> (-53.57%)
:arrow_down:

...ordinator/VerdictResultStreamFromSingleResult.java
0% <0%> (-46.66%)
:arrow_down:

...b/coordinator/VerdictSingleResultFromListData.java
0% <0%> (-32.85%)
:arrow_down:

...g/verdictdb/coordinator/ScramblingCoordinator.java
44.25% <0%> (-31.85%)
:arrow_down:

... and 23 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 01f38a9...6ed9d3d. Read the comment docs.


Fixed proxy merge conflicts

Also could you add a note to the README to indicate how to set this up?


Exports initSSR

Exports initSSR to help when occurs document is not defined with renderSSR
I'm using Vite to build my SSR application and initSSR is missing in exports, causing incorrectly bundle build

I don't recommend using initSSR() manually, but instead wrap your component inside a anonymous function.
See https://github.com/nanojsx/nano/issues/106


added new file, newfile.jsgit

What is Semantic HTML? - it shows you what you’re doing or working on. Ex Div
2. What is HTML used for? - used to “write” up the code, and the textual information.
3. What is an attribute and where do we put it?
4. What is the h1 tag used for? How many times should I use it on a page?- Title, just then.
5. Name two tags that have required attributes- Body, Header
6. What do we put in the head of our HTML document? -Title
7. What is an id? Attributes to the html
8. What elements can I add an id to? Within a section.
9. How many times can I use the same id on a page? 1
10. What is a class? stylesheet
11. What elements can I add a class to? Specific sections.
12. How many times can I use the same class on a page? As many as times as you want
13. How do I get my link to open in a new tab?
14. What is the alt attribute used for?
15. How do I reference an id?
16. What is the difference between a section and a div
17. What is CSS used for? To visually see the page.
18. How do we select an element? Example - every h2 on the page command + find
19. What is the difference between a class and an id? - Give me an example of when I might use each one…. Not sure
20. How do we select classes in CSS?.... No sure
21. How do we select a p element with a single class of “human””?.... Not sure
22. What is a parent child selector? When would this be useful? The indented section that portraits to a certain section… ex Body… and next line with the indentation would be the child.
23. How do you select all links within a div with the class of sidebar? Not sure
24. What is a pseudo selector? What we hover over and see what it’s details are… inspection
25. What do we use the change the spacing between lines? Line Height
26. What do we use to change the spacing between letters? Leigh Width
27. What do we use to to change everything to CAPITALS? lowercase? Capitalize? Not sure
28. How do I add a 1px border around my div that is dotted and black? Change the px border: 1px;
29. How do I select everything on the page? Git all? This one i'm confused on
30. How do I write a comment in CSS? Git m-?
31. How do I find out what file I am in, when I am using the command line? Git ls
32. Using the command line - how do I see a list of files/folders in my current folder? Not sure
33. How do I remove a file via the command line? Why do I have to be careful with this? You can’t. Because you can’t.
34. Why should I use version control? It saves and you can go back if need be.
35. How often should I commit to github? If it’s making changes… 15… if it’s developing it should be used regularly as it’s used by everyone.
36. What is the command we would use to push our repo up to github? Git push
37. Walk me through Lambda's git flow. Command, space brings up the terminal and from there you can add a source that you use to make certain commands to, that as a developer you can update a certain development.


Add automation to archive issues/PRs, close current milestone and create new miles

It would be nice to automate the release workflow to cleanup issues/milestones after things have been released.

We've stepped away from using milestones, instead releasing more frequently with GitHub automated release notes. I don't think we'll need anything in this space, but can be swayed to reopen if needed.