Timer immediately starts

I just set up the board and installed the reed sensor as described in the README.
After starting the Mara X machine and the board, the timer immediately starts counting, although the pump has not started yet. When starting or stopping the pump, the timer keeps counting and doesn't stop.
Any ideas on what causes the problem and how to fix it?

Hi,
Make sure the switch is connected properly to the board.
If MaraX is off, does the time start counting?

Hi,
Make sure the switch is connected properly to the board.
If MaraX is off, does the time start counting?

If MaraX is off, does the time start counting?

Yes, the timer starts even if the Mara X is off.

If MaraX is off, does the time start counting?

Yes, the timer starts even if the Mara X is off.

Maybe the wrong kind of reed switch?  Did you buy a normally open or normally closed switch?

I think inverting the value should be fine ... give it a try

Yep, inverting the value solved the problem for me!
I will create a pull request with different versions for different reed switches.


Fast Configurable 2 Sided shader only supports Texture when it's set at the start

If you use the Fast Configurable 2 Sided shader , don't set an initial Texture and try to set it runtime it will not display the texture
Workaround - set a dummy texture at startup . Any texture. Just make sure there is a startup texture.

@LocalJoost, I think you may have wanted to open this issue on the Unity specific repo.

I didn't? Whoops
Joost van Schaik
Windows Development MVP
"The world as I envision it in my head is such a more interesting place"

From: Stephen Hodgson<EMAIL_ADDRESS>Sent: Nov 2, 2017 18:08
To: Microsoft/MixedRealityToolkit
Cc: Joost van Schaik; Mention
Subject: Re: [Microsoft/MixedRealityToolkit] Fast Configurable 2 Sided shader only supports Texture when it's set at the start (#123)
@LocalJoosthttps://github.com/localjoost, I think you may have wanted to open this issue on the Unity specific repo.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/MixedRealityToolkit/issues/123#issuecomment-341491237, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8BnwyR0Bo7FUNvhmj9e7I72XW_Ua9Xks5syfbtgaJpZM4QP0CY.

Sorry. Wrong place to place this


Add a Codacy badge to README.md

Coverage remained the same at 83.257% when pulling 153e78d2af9ceefb8a4ffd9fe5eb8274a9c062d6 on codacy-badger:codacy-badge into 40c18dd5977598296a49222e01b3347cd0769d92 on uhawaii-system-its-ti-iam:master.

This has already been taken care of


Artfiact Download option is not displaying in Agent Job task

We have two accounts under one organization in Azure Devops and we have noticed, that Artifact Download option is only displaying in our Dev environment.
Please refer to the screenshots below.
Dev environment

Prod environment

Is there an option somewhere where we can turn this feature on? Or is it just a bug?
Thanks in advance

Hi @qlee94, Thanks for reaching out. I'm following up on this and will be in touch. Thanks again.

Hi @qlee94,
Please accept my sincerest apology for letting this issue slide. Since this was months ago, I imagine it's worked itself out, so I'll be closing this issue. If it does remain an issue, please let me know. Thanks!


After installation when i typed "simplecv" this issue occured...please help

first i used this method
mkdir ~/Code
cd ~/Code
git clone git://github.com/sightmachine/SimpleCV.git
cd SimpleCV
sudo pip install -r requirements.txt
sudo python setup.py develop

when i input sudo pip install -r requirements.txt
i got a problem

i just skip over it and i got this

however, when i input simplecv  this problem happed

edit issue

first you should open the requirements.txt then delete line 3 and line 6 ,because RBP already installed PIL And pygame inside.
But  after i done this i still get the same trouble like you and don't know why.

was facing the same issue, tried many things, solved by forcefully downgrading to IPython4:
pip install 'IPython==4' --force-reinstall


[BUG] ttx -z extfile -o outfile.ttx writes the bitmap folder in the wrong location

Let's say I do
mkdir out
ttx -t CBDT -t CBLC -z extfile -o out/myfont.ttx myfont.ttf

or
mkdir out
ttx -t CBDT -t CBLC -z extfile -d out myfont.ttf

then I expect that ttx will create the bitmap subfolder in the out subfolder, i.e. in the location specified by -o <outfile> or -d <outdir>. But ttx always creates the bitmap subfolder in the current working directory. However, the out/myfont.ttx file will make references to <extfileimagedata value="bitmaps/strike0/glyph2784.png"/> so it expects the location out/bitmaps/strike0/glyph2784.png.
So at this point, I have to manually move bitmap to out, or otherwise, merging won't work.

The problem seems to be in function _writeExtFileImageData of module E_B_D_T:
https://github.com/behdad/fonttools/blob/master/Lib/fontTools/ttLib/tables/E_B_D_T_.py#L341
The location of the bitmaps/ folder is always set to the current working directory, whereas it should be possible to set a different one based on the location of the output ttx file.
One solution could be to get the path to the output TTX file from the writer object which is passed along as an argument; writer has a file attribute, which in turn should have a name attribute for the filename. I'll try that and see if this solves it.

@twardoch could you try and see if #297 fixes the issue?
thank you.


Use new Docks feature

As of Atom 1.17, there's a new Docks feature especially designed for panels like what this package opens. It would simplify usage from a user's point of view, and be more consistent with other Atom packages.

@Scimonster ,
You are totally right. The new docks feature is awesome and I will use them in this package. A new version with docks integrated will be released soon.


Fix "similar-code" issue in pysendyit/errors.py

Similar blocks of code found in 7 locations. Consider refactoring.
https://codeclimate.com/github/0x6f736f646f/sendyit-python/pysendyit/errors.py#issue_5ecb01f11af5890001000025

#23 👍


WIP: OpenMM harness (addresses #147)

Initial structure in place; working on input structure and laying out execution bits. Used the basic example from the OpenMM docs as the starting point, and existing rdkit and psi4 harnesses for guidance.
Using @jchodera's comment as our target use case: https://github.com/MolSSI/QCEngine/issues/147#issuecomment-527691867
Any additional requirements for this harness should be listed in a comment on #147.

Wow, this is a great start!
It looks like you're targeting a really different use case, way beyond a single molecule in vacuum.
In the short-term, we're really in need of something that simply focuses on evaluating the energies and gradients for a single molecule in vacuum---the equivalent of what is done with QM---for comparison/benchmarking of the new openforcefield force field against the QM reference data.
I highly recommend using the RDKit molecule processing from here to form an RDKit Mol:
https://github.com/MolSSI/QCEngine/blob/master/qcengine/programs/rdkit.py#L47-L80
After that, you can then shove it through the Open Force Field toolkit to get an OpenMM System directly from one of our force fields:
# Create an OFF Molecule from the RDKit Molecule
from openforcefield.topology import Molecule
off_molecule = Molecule(rdkit_molecule)
# Load an OFF Force Field
from openforcefield.typing.engines.smirnoff import ForceField
off_forcefield = ForceField(offxml_filename)
# Assign parameters to the molecule in vacuum
openmm_system = off_forcefield.create_openmm_system(off_molecule.to_topology())

You can then perform an energy/gradient evaluation with OpenMM.
For computations with GAFF/GAFF2, it will be a bit more complicated, since we need to use Antechamber to generate charges and parameters, and then either convert those into an OpenMM XML force field residue template or convert them via leap into a prmtop/inpcrd to load into OpenMM. We have lots of code to wrap this already, and I'm happy to help there!
I'm working with Junmei Wang to get access to a historical repository of all GAFF versions so we can specify which version we want in particular.
(Feel free to move this comment to #147 if desired!)

This looks like a great start! I echo what John is pointing out here that keeping something pretty simple and quantum-like is likely the simplest and most useful choice to work through here. compute is specifically for energy/gradient/Hessian computations.
Running short dynamics will be super useful as well, but we would like want to pack this into a procedure.

Changes made addressing comments from @jchodera, @dgasmith, and
@jaimergp:

procesing molecule with rdkit -> openforcefield -> openmm
limiting scope to drivers ('energy', 'gradient')
model specifies forcefield as method; also has offxml and url fields

Next:

need structure positions generated
need gradient calculation (state.getForces())
need rdkit checking in found method
need url handling for forcefield somewhere (either in openforcefield or here)

Hi! Just wanted to check in to see what the plans and timeline for moving forward with this might be.

Implemented recommendations from @jchodera.
Also:

added an attempt at properly specifying the number of threads we want OpenMM to use
added rdkit checking in OpenMMHarness.found using RDKitHarness.found
cut out unncessary postprocessing bits lifted from psi4 harness
used Provenance object to fall in line with current RDKitHarness usage
Result now includes both input data and ouput data, in line with RDKitHarness usage

Remaining items include:

conversion of energies to units of hartree
conversion of gradients to units of hartree/bohr
url handling for forcefield somewhere

Sorry for the delay @jchodera; I'm currently traveling, but definitely don't want to be the bottleneck for a much-needed component. I'll be able to iterate quickly to finish out the remaining items and hammer out any newly-noticed issues over the evenings to come.
There are three items remaining from my view; I'm going to try and address travis next.

Currently, tests fail because these changes are dependent on openmm/openmm#2421 and MolSSI/QCElemental#144 making it into releases for each. I could put in some deliberate hacks to be removed once we have those releases, just to see if this functionality works as expected. Thoughts?

No, lets push out a new QCElemental release now so that this works.

QCElemental v0.10.0 is out. Tests still fail, but you should have the ability to run this through CI now without the previous bottleneck.

I know we're hoping to put an OpenMM bugfix release out soon, but it may be a good idea to work around the Hartree issue for now. It might be easy to do that by simply adding
from simtk import unit
if not hasattr(unit, 'hartree'):
    unit.hartree_base_unit = unit.ScaledUnit(4.3597447222071e-18, unit.joule, "hartree", "Ha")
    unit.hartree = unit.hartrees = unit.Unit({unit.hartree_base_unit: 1.0})

Tests passing on every build but the OpenMM-specific one thanks to MolSSI/QCElemental#150. Addressing comments here over the next few nights so we can move this one closer to the finish line.

@dotsdl Great looking forward to having this in!

A working openmm should be available from the omnia-dev channel right now.
What about adding a devtools/conda-envs/openmm.yaml file based on rdkit.yaml that contains:
name: test
channels:
  - omnia-dev
  - conda-forge
  - rdkit
dependencies:
  - openmm
  - rdkit

    # Core
  - python
  - pyyaml
  - py-cpuinfo
  - psutil
  - qcelemental >=0.9.0
  - pydantic >=0.30.1

    # Testing
  - pytest
  - pytest-cov
  - codecov

Also, shouldn't this be testing the conda-forge RDKit, rather than the rdkit channel RDKit?

You'd of course also have to add a PROG=OPENMM branch to the .travis.yml that would make use of this environment.

We may be hitting some fresh dependency hell with using rdkit from conda-forge. I'm not sure quite yet how to interpret the conda errors I'm seeing on Travis for the OPENMM build.

@jchodera troubleshooting this now. Is omnia-dev a private conda channel?

The dev is a Conda label build from a different github repo, you should be able to access the OpenMM dev builds from conda install -c conda-forge -c omnia/label/dev openmm

Ah, thanks @Lnaden! Unfortunately I'm still getting what looks like the same result as when specifying -c omnia-dev:
> conda create -n molssi3 -c omnia/label/dev  openmm
Collecting package metadata (current_repodata.json): done
Solving environment: failed with current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed

UnsatisfiableError: The following specifications were found to be incompatible with each other:

Package numpy conflicts for:
openmm -> numpy
Package python conflicts for:
openmm -> python[version='2.7.*|3.5.*|3.6.*|3.7.*']
Package fftw3f conflicts for:
openmm -> fftw3f

Does the openmm package on omnia-dev have dependency spec issues? I'll admit I have very little experience troubleshooting conda issues.

@dotsdl: You'll need to include both the omnia and omnia-dev channels to satisfy the dependencies for now.
Don't use the omnia/label/dev label---we've deprecated that.
We're nearing the home stretch with conda-forge! We just need to resolve an outstanding issue with OpenCL:
https://github.com/conda-forge/conda-forge-enhancement-proposals/issues/17

@jchodera awesome, that seems to be the trick! Thank you! I'm also working on the caching components above. I believe I also have enough info to finish out implementing the spec you and @dgasmith decided for inputs. I know we're all looking forward to shipping this.

Everything on the omnia channel and its labels requires conda-forge as a higher order dependency. So I think the fix to the create line there is
conda create -n molssi3 -c conda-forge -c omnia/label/dev  openmm
However, the other thing you can do is save a YAML similar to the one John posted above and then run the command
conda env create -n molssi3 -f openmm.yaml (openmm.yaml is the file you saved)
The problem you were seeing with dependencies is from being slightly incomplete. This YAML should work (at least it does on my laptop)
name: test
channels:
  - conda-forge
  - omnia-dev
  - omnia
dependencies:
  - openmm
  - rdkit

    # Core
  - python
  - pyyaml
  - py-cpuinfo
  - psutil
  - qcelemental >=0.9.0
  - pydantic >=0.30.1

    # Testing
  - pytest
  - pytest-cov
  - codecov

Also, apparently disregard what I said about the dev label (i've struck that in my previous comment)

@dotsdl I think this is ready to go if you can update the test env!

Awesome! Can't wait to get this into a new release.

@dgasmith, @jchodera, thanks! There are a few outstanding items that I want to sprint on this week. I am aiming to have them ready for review by EOD 11/17:

geometry optimization test for OpenMM
tests for each of the options available for specifying which forcefield to use
caching of OpenForceField Forcefield (key: hashlib.sha1(<xml>).hexdigest())
caching of OpenMM System (key: {mol_hash}-{input_model.method}-{hashlib.sha1(forcefield_schema).hexdigest()})
Getting thread specification to work properly (see TODO). We may need to resort to an environment variable; guidance on how best to require env variables in QCEngine appreciated.

geometry optimization test for OpenMM

Is the OpenMM engine supposed to do geometry optimization, or is that driven by GeomeTRIC?

@jchodera In this case we would need to add OpenMM to the optimization procedures as well. This becomes a bit complex and we would need each step of the geometry optimization and energy from OpenMM. We have yet to do this and do not have an example of using a native geometry optimizer.

In this case we would need to add OpenMM to the optimization procedures as well. This becomes a bit complex and we would need each step of the geometry optimization and energy from OpenMM. We have yet to do this and do not have an example of using a native geometry optimizer.

Would this be better to handle as a separate PR? It's not clear to me how big a lift this addition will turn out to be.

I agree this is for another PR.

Considering merging this with test skipped and breaking remaining questions out into issues. What do you think?

@dgasmith agreed, see my updated checklist.
The last item is CPU thread number control. Are harnesses able to rely on environment variables for some of their execution input? Currently these lines throw an exception, and I get the impression this is because OpenMM's only way to alter the number of threads it uses is via the OPENMM_CPU_THREADS environment variable.
If using env variables are fine, these lines should be able to be deleted and OpenMM should respect the env variable.

This is ready for review, from my perspective, even with this outstanding issue.

Tagging @peastman regarding setting the number of threads via a Platform property (see directly above). Are we misunderstanding how we should set the number of CPU threads for the CPU platform?

Comments resolved. Merging and resolving conflicts with current master now.

master merged. Waiting for tests to complete. This work should be good to merge if there are no further concerns. Some follow-up items should be made into separate issues:

Caching of openmm_system upon creation. This should follow a model similar to our caching of off_forcefield, but we need to carefully consider how we generate the key/hash for the openmm_system. Whatever we choose to hash should be invariant to rotations or translations of the system, but should capture connectivity, charge states, etc.
Generation of basis if not specified. Ideally basis is generated from forcefield_name and forcefield_version from the OFFXML file, but these do not appear to be included in current OFFXML forcefields at this time.

Tests pass, please let me know if anything further is needed!

we need to carefully consider how we generate the key/hash for the openmm_system.

One option for this is to serialize the System to XML with XmlSerializer.serialize(system) then compute a hash from the string.  This will detect any change to the System or the Forces it contains, but will be unaffected by changes to particle positions.


throwing different error for spam

I am looking here:
https://github.com/xini/silverstripe-mailchimp-signup/blob/fb1fa073d8a85f0e10ab1db209a50cbe10d08026/src/Extensions/SignupControllerExtension.php#L642-L644
I am getting lots of errors...

User Warning: Last Response: Array
(
    [headers] => Array
        (
            [url] => foo
            [content_type] => application/problem+json; charset=utf-8
            [http_code] => 400
            [header_size] => 355
            [request_size] => 337
            [filetime] => -1
            [ssl_verify_result] => 0
            [redirect_count] => 0
            [total_time] => 0.458694
            [namelookup_time] => 0.004227
            [connect_time] => 0.00545
            [pretransfer_time] => 0.014019
            [size_upload] => 197
            [size_download] => 229
            [speed_download] => 500
            [speed_upload] => 430
            [download_content_length] => 229
            [upload_content_length] => 197
            [starttransfer_time] => 0.014029
            [redirect_time] => 0
            [redirect_url] =>
            [primary_ip] => bar
            [certinfo] => Array
                (
                )

            [primary_port] => 443
            [local_ip] => foo
            [local_port] => foo bar
            [http_version] => 3
            [protocol] => 2
            [ssl_verifyresult] => 0
            [scheme] => HTTPS
            [appconnect_time_us] => 13880
            [connect_time_us] => 5450
            [namelookup_time_us] => 4227
            [pretransfer_time_us] => 14019
            [redirect_time_us] => 0
            [starttransfer_time_us] => 14029
            [total_time_us] => 458694
            [request_header] => foo
user-agent: DrewM/MailChimp-API/3.0 (github.com/drewm/mailchimp-api)
accept-encoding: deflate, gzip, br
accept: application/vnd.api+json
content-type: application/vnd.api+json
authorization: bar
content-length: 197

        )

    [httpHeaders] => Array
        (
            [server] => openresty
            [content-type] => application/problem+json; charset=utf-8
            [content-length] => 229
            [x-request-id] => foo
            [link] => <https://foo.api.mailchimp.com/schema/3.0/Definitions/ProblemDetailDocument.json>; rel="describedBy"
            [content-encoding] => gzip
            [vary] => Accept-Encoding
            [date] => Thu, 16 Mar 2023 20:48:54 GMT
        )

    [body] => {"type":"https://mailchimp.com/developer/marketing/docs/errors/","title":"Invalid<EMAIL_ADDRESS>has signed up to a lot of lists very recently; we're not allowing more signups for now","instance":"foo"}
)

It would be great to ignore these errors, because they are not errors, they are "success" in filtering spam.

Here is what I did for a temporary fix:
if (strpos($mailChimp->getLastError(), 'has signed up to a lot of lists very recently') === false) {

Hey Nicolaas,
Well, that's debatable. The signup failed. Therefore it should show an error.
Also, when you look at https://mailchimp.com/developer/marketing/docs/errors/#error-glossary, there is no way of telling what error is a filtering success and what is some other error.
What do you think?
Cheers

Here is what I did for a temporary fix:
if (strpos($mailChimp->getLastError(), 'has signed up to a lot of lists very recently') === false) {

And then? Do we tell them that signup suceeded? That's not true.
Also, what other "errors" like this exist?
Also, how reliable is that the text in that error message stays the same?

Well, that's debatable. The signup failed. Therefore it should show an error.

Yes debatable.  Here is what I would say in the debate:  I am getting 200+ errors from a  site about people trying to sign-up.  The code - mailchimp - is written in such a way that it blocks spammers. Blocking spammers is not an error, it is a success.
And then? Do we tell them that signup succeeded? That's not true.

Right now, the user also does not know as a E_USER_WARNING does throw an error on production? (not sure).

Also, what other "errors" like this exist?
Also, how reliable is that the text in that error message stays the same?

Yes - obviously this is a hack. I can see it is a bit risky (but not that risky).
Right now, I am getting lots of errors each day, which makes me miss real errors.

sorry, I think I now understand: you want to not throw an error in these cases, but still show the signup error to the user?

ok. and I'll replace the user_error with Injector::inst()->get(LoggerInterface::class)->warning('...');?

That sounds great.

This is now tagged as 4.8.0 and 5.1.0.
Thanks, Nicolaas!

THANK YOU!!!!


Hide Types Behind ABI3 Features

When building with a PyO3 abi3-py38 feature, I've received the following error:
error[E0432]: unresolved imports `pyo3::types::PyDate`, `pyo3::types::PyDateTime`, `pyo3::types::PyDelta`, `pyo3::types::PyTime`, `pyo3::types::PyTzInfo`
  --> ~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rigetti-pyo3-0.3.1/src/to_python.rs:27:13
   |
27 |     types::{PyDate, PyDateTime, PyDelta, PyTime, PyTzInfo},
   |             ^^^^^^  ^^^^^^^^^^  ^^^^^^^  ^^^^^^  ^^^^^^^^ no `PyTzInfo` in `types`
   |             |       |           |        |
   |             |       |           |        no `PyTime` in `types`
   |             |       |           |        help: a similar name exists in the module: `PyType`
   |             |       |           no `PyDelta` in `types`
   |             |       no `PyDateTime` in `types`
   |             no `PyDate` in `types`

This means no crate building with abi3-py38 can build if it depends on rigetti-pyo3. As such, these imports and functionality that depends on them should be hidden behind an appropriate abi3-py* feature (or lack thereof).
To test this in CI, try building a simple module extension with and without the appropriate abi3-py* features that do not use the PyDate, et al. objects; the build should not fail with an error similar to that above.

PRs #45 and #46 fix this, but I think it would be great to get some sort of test for this – I somehow had to do two PRs because I missed one set of files along the way.

#46 closes this and includes better testing on builds.


merge from arlac77/template-github,arlac77/template-kronos-module

package.json

chore(package): add ^3.8.0 remove ^3.7.1 (devDependencies.ava)

:tada: This PR is included in version 8.3.25 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Improve future interoperability with responses-module

Adds more test cases with older versions of responses
Removes a method that will no longer exist in the next responses-release
Removes a parameter that throws warnings in the latest responses-release

Codecov Report

Merging #4753 (05a4ed0) into master (2407e96) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #4753   +/-   ##
=======================================
  Coverage   95.34%   95.34%
=======================================
  Files         570      570
  Lines       61124    61133    +9
=======================================
+ Hits        58276    58285    +9
  Misses       2848     2848

Flag
Coverage Δ

servertests
46.47% <16.66%> (-0.97%)
:arrow_down:

test_responses
33.02% <100.00%> (+0.90%)
:arrow_up:

unittests
95.22% <83.33%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

moto/apigateway/models.py
93.64% <ø> (ø)

moto/core/custom_responses_mock.py
93.54% <100.00%> (+0.69%)
:arrow_up:

moto/core/models.py
97.60% <100.00%> (ø)

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 2407e96...05a4ed0. Read the comment docs.


Update disk-encryption-portal-quickstart.md

Incorrect reference: running Ubuntu 18.04 LTS

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

Excellent suggestion, thanks! #sign-off


Update GitLab CI

Fixes #634.

How can we tell that it fixed the build?  Would you share a link?

Sure. https://code.ornl.gov/ecpcitest/alexa/-/pipelines/192716 is showing that it's passing.


failing tests: editor

seems like some tests are breaking the others, when run solely one suite, no errors are shown


CookieJar

Hi,
I'm trying to pass cookies to my html conversion, but have no idea how. HtmlToPdf contains cookieJar method, but passing string like this ->"COOKIE_LABEL="COOKIE_VALUE"; expires=Thu, 03-Sep-2020 12:53:09 GMT; domain=mail.intalio.pl; path=/;") doesn't actually make any difference. I try to pass authentication cookie with session id, which will resolve my image href into actual image object.

I'm also adding my code snippet which using for converting
`
HtmlToPdf pdf_obj = HtmlToPdf.create()
.object(HtmlToPdfObject.forHtml(<HTML_STRING>).useExternalLinks(true).enableJavascript(true).convertInternalLinksToPdfReferences(true).loadImages(true))
.cookieJar("ZM_AUTH_TOKEN="<AUTH_TOKEN_STRING>"; expires=Thu, 03-Sep-2020 12:53:09 GMT; domain=some-domain.pl; path=/;");
boolean success = pdf_obj.convert("./test.pdf");
`

I also have the problem,but i do not know how to solve


chore: release 2.0.1

:robot: I have created a release *beep* *boop*
2.0.1 (2023-04-08)
Bug Fixes

ensure nestd allOfs are correctly resolved (#95) (d6605c6)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/contiamo/openapi-generator-go/releases/tag/v2.0.1 :sunflower:


Make localStorage harder to read

During Ops 101 classes, people with web dev experience very quickly find the password, because they read out the values in localStorage in the JS console.
I'd propose either encoding the values with Base64, or storing it in a different place (like cookies, session store, or indexedDB).


com.kickstarter.extensions.showSnackBar

When i was trying to debugging the code to understand it  i got a error. looking to the classes i found that you have a un resolve reference that is com.kickstarter.extensions.showSnackBar

Hey @sbenitez10, I'm not getting this error. Have you been successfully able to build the app previously?

nope i wasnt.  i am checking it know

HI, i was trying to build the app but i  get this error and i dont know how to solve it

I think that error is a red herring. When you open the project, Android Studio makes suggestions about updating your version of kotlin and gradle but that actually breaks the app. Try reverting your changes in build.gradle and gradle-wrapper properties and then rebuild. Tell me how it goes.

i revert my changes but nothings happens i still getting the same error

sorry for the problems.

No problem! Looks like the build "completed successfully" and that error shouldn't affect you so have you tried actually running it on a device or emulator?
Here's my output when I build the app:

yeap i run it but when i scroll too much the first view it generates a ANR. so i thought that maybe was because the build had that error.

Alright, I just pulled down the OSS version and debugged 🕵🏾♀. I will open a PR to fix this!

The PR has been merged. Please pull the latest and you shouldn't see the crash anymore!


XLSX.utils.sheet_to_json returning empty array

Hey,
I am trying to give our users the possibility to upload an XLSX file (through ng-file-uploader), and to convert this XLSX file to JSON data afterwards.
The uploading of the file works fine, this is the result when I print $scope.file in the console:

When I try to use the sheet to json function, I get an empty array back, while there is a lot of data in the uploaded XLSX file.
In my code I use the following:
XLSX.utils.sheet_to_json($scope.file);
This returns an empty array as said before.
Is there something I'm forgetting or should execute differently?
Kind regards,
Thomas

Update: I got the file into the XLSX tool now. I was able to create the workbook, but now I'm trying to use the XLSX.utils.sheet_to_json on one of the sheets inside the workbook in the following way, and I'm getting an error:
var roa = XLSX.utils.json_to_sheet(workbook)
The error:

This is my workbook object:

any solution on this?

@Xsmael I solved this setting a the name of the sheet you want to use and also the header, which might help you to identify each column.
var workbook = XLSX.read(bstr, {type:'binary'});
var form = XLSX.utils.sheet_to_json(workbook.Sheets[workbook.SheetNames[3]], {header:["headerName1","headerName2","headerName3"]});

I hope this helps you

@jvicensfarrus proving headers just outputs an array with provided headers, no other sheet data is prasent ? anything else we need to do ?
const wb = XLSX.read( bufferArray, { type: 'buffer' } );
      const wsname = wb.SheetNames[7];
      const ws = wb.Sheets[wsname];
      const data = XLSX.utils.sheet_to_json(ws, {
        raw : true,
        header : ['Date','Currency','Income','Expense','Fee','Balance','Reason','Remarks']
      });

@jvicensfarrus proving headers just outputs an array with provided headers, no other sheet data is prasent ? anything else we need to do ?
const wb = XLSX.read( bufferArray, { type: 'buffer' } );
      const wsname = wb.SheetNames[7];
      const ws = wb.Sheets[wsname];
      const data = XLSX.utils.sheet_to_json(ws, {
        raw : true,
        header : ['Date','Currency','Income','Expense','Fee','Balance','Reason','Remarks']
      });

@shamseerahammedm
you could try to not use constants and creating the 'ws' directly within the wb.SheetName[7]
      var ws = wb.SheetNames[7];
      var data = XLSX.utils.sheet_to_json(ws, {
        raw : true,
        header : ['Date','Currency','Income','Expense','Fee','Balance','Reason','Remarks']
      });```


Kaldi Active Grammer Implementation

Have been working on this my osx recently works great.. they have support for win/mac/linux
and see the accuracy is amazing also the impletementation is pretty straightforward as deepspeech and works out of the box without the hasle of installing kaldi
is anyone aware of this yet.. ? should we think of add this ?
https://github.com/daanzu/kaldi-active-grammar/

This would be perfect for toggling intents on and off. Rhasspy does this in the NLU system, but the ASR can still listen for invalid intents. With active grammars, we could simply have a grammar per intent.
@mathquis has also been looking into using Kaldi's grammars for named entities/slots. I wonder if these two approaches can be merged?


Nest an Anchor Element within a Paragraph not working correctly

Challenge Nest an Anchor Element within a Paragraph has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.

Please provide more information on the exact issue that you are facing. I can pass the challenge with the above code.

Your a element should be nested within your new p element.
Your p element should have the text "View more " (with a space after it).
these are the challenges that are incomplete

I am facing the issue only in chrome and not on firefox. In chrome, when i click run test nothing happens even if the code is correct.
Thanks,
Vinesh

@vinesh178
Can you check the dev tools console for errors?
On Windows: Press F12, Go to the Console Tab, and retry the challenge.
Should see any errors post the screenshots here.
Also, try the challenge in a incognito window with all add-ons disabled.

Please report back as requested, to re-open


Getting more done in GitHub with ZenHub

Hola! @blackwhites has created a ZenHub account for the blackwhites organization. ZenHub is the leading team collaboration and project management solution built for GitHub.

How do I use ZenHub?
To get set up with ZenHub, all you have to do is download the browser extension and log in with your GitHub account. Once you do, you’ll get access to ZenHub’s complete feature-set immediately.
What can ZenHub do?
ZenHub adds a series of enhancements directly inside the GitHub UI:

Real-time, customizable task boards for GitHub issues;
Burndown charts, estimates, and velocity tracking based on GitHub Milestones;
Personal to-do lists and task prioritization;
“+1” button for GitHub issues and comments;
Drag-and-drop file sharing;
Time-saving shortcuts like a quick repo switcher.

Add ZenHub to GitHub
Still curious? See more ZenHub features or read user reviews. This issue was written by your friendly ZenHub bot, posted by request from @blackwhites.

fix it


Add fluree.svg, update refs in landscape.yml

Signed-off-by: Tr3yb0<EMAIL_ADDRESS>Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[x] Have you signed-off your commits

Other than the build server not finding the Twitter_Keys, I am not sure what is breaking here. Can someone let me know what needs to be done to get this to work?

It looks like the build process is trying to hit Twitter for each of the applications in the landscape, but there is a , appended to each of the urls, which is also causing problems.

Thanks for updating the SVG file, it looks like the build is failing one of the tests unrelated to this pull request. The twitter error is expected here. We're looking into it and will retry this branch build once it's fixed.


Proposal to create FAQ and about us

Hello farmerbb, I am mayowa, a github promoter, I would love to create FAQ and ABOUT US for this beautiful project.
Gracias!

Thanks for your offer.  I think the current README.md is fine for now as it's just me developing this project and I don't get a lot of frequently asked questions.


decodeAddress (and its variations) should be public

Doing so will make many operations way easier, for example in order to get all the information for an address, one needs to run isValidAddress first (or wrap all operations in try-catch), and then call all detectAddress methods individually (which are already using decodeAddress as source);
Also, there may be cases where one wants to check the output of cashaddr decode directly (for example, accessing prefix property which do includes bchreg and detectNetwork treats it as testnet)

the lower level library cashaddrj is better suited for that use case

the lower level library cashaddrj is better suited for that use case


caddy.Restart() - listen tcp :443: bind: address already in use

1. What version of Caddy are you running (caddy -version)?
9e386fc (latest commit on master at the moment)
2. What are you trying to do?
I'm using Caddy as a library to embed it so I can easily pull data from my database system, rebuild the Caddyfile and call caddy.Restart(Caddyfile) to restart gracefully. I love Caddy, but I have to say this ability to use Caddy as a library is by far my favourite feature :) It makes things that are a pain to do otherwise easy and straight forward.
3. What is your entire Caddyfile?
My entire Caddyfile is huge. It has thousands of virtual hosts in it. In any case the file itself doesn't seem to have a problem because Caddy starts and runs fine when using it. The problem arises when a caddy.Restart(Caddyfile) is issued.
4.
I'm running Caddy as an embedded library. Here is my entire main function:-
package main

import (
        "github.com/mholt/caddy/caddy"
        "log"
)

func init() {
        caddy.AppName = "name"
        caddy.AppVersion = "version"
}

func main() {
        // Start services
        cfg := new(Config)
        cfg.compile()
        err := caddy.Start(cfg)
        if err != nil {
                log.Fatal(err)
        }
        // Stop services on exit
        defer func() {
                err = caddy.Stop()
                if err != nil {
                        log.Fatal(err)
                }
        }()
        go cfg.watchUpdates()
        // Wait for services as they run
        caddy.Wait()
}

watchUpdates() waits for updates in the database and then compiles the Caddyfile and restarts the server:-
c.compile()
caddy.Restart(c)

c is an instance of Config, an alias type of caddyfile.Caddyfile
5. What did you expect to see?
I expected the server to gracefully restart and the new Caddyfile to be applied after that.
6. What did you see instead (give full error messages and/or log)?
I see either:-
listen tcp :443: bind: address already in use
or
listen tcp :80: bind: address already in use
in the logs. Also the old Caddyfile is still in use at this point which confirms that the restart is failing.
caddy.Start() carries the following note:-
// Note (POSIX): If Start is called in the child process of a
// restart more than once within the duration of the graceful
// cutoff (i.e. the child process called Start a first time,
// then called Stop, then Start again within the first 5 seconds
// or however long GracefulTimeout is) and the Caddyfiles have
// at least one listener address in common, the second Start
// may fail with "address already in use" as there's no
// guarantee that the parent process has relinquished the
// address before the grace period ends.

Inside the function, a couple of lines after that note I also see the following comment:-
signalSuccessToParent() // TODO: Is doing this more than once per process a bad idea? Start could get called more than once in other apps.

In my logs after [INFO] Restarting I see messages printed to screen twice, not once so I suspect that the above is what's affecting me. That is caddy.Start() is somehow being called more than once during caddy.Restart().

First, this is an awesome issue. Thanks for using the new template!
One thing to be aware of when calling Restart() is that your Go process will spawn a new one, and the parent process will die, either immediately or in a few seconds.
That TODO next to signalSuccessToParent() might be outdated (oops), since the signalSuccessToParent() function uses a sync.Once to ensure that it only happens once, even if the function is called multiple times.
The reason your restart might be using the old Caddyfile is because you need to call LoadCaddyfile() in order for it to use the new one that you passed into Restart().
The caddy package actually uses caddy.Input as the type to represent a Caddyfile. caddyfile.Caddyfile is for the upcoming API which will be able to transmit the Caddyfile as parsed tokens in JSON format.
Try using LoadCaddyfile() and let me see your updated code if you still have the problem.

I don't know how I overlooked LoadCaddyfile(). I was aware of caddy.Input. My Config was simply implementing it. I have since discovered caddy.CaddyfileInput so I'm now using that instead. My Config is still an alias type of caddyfile.Caddyfile though since I'm currently marshaling the struct to JSON and then using caddyfile.FromJSON() to convert it. I have been reading the wiki and studying the code. I can already see how I can improve my code. Thanks!

I've made a new wiki page in an effort to make it more obvious: https://github.com/mholt/caddy/wiki/Embedding-Caddy-in-your-Go-program
Cheers!

Awesome, thanks!


fix error in createHeightMap function of system.js

THREE.ParametricGeometry has been moved to /examples/jsm/geometries/ParametricGeometry.js

Thank you!


how to remove arrow and add drawer icon?

how to remove arrow and add drawer icon?
Please someone explain me

try this setting
app:viewpager_disableToolbar="true"


Don't proxy to local bookshelf if it's disabled.

Issue described in https://github.com/chef/chef-server/issues/694.
It's not clear whether nginx_bookshelf_caching works for remote bookshelfs; if so, this would need an update to factor that in.

Thanks for following up on this!
I don't think nginx_bookshelf_caching works for remote cookbook storage. I suppose it is possible if someone had customized their nginx configuration via the .d configuration directory.  But I think that is an unlikely case and that this is fine.

Great; thanks for clarifying.  If there's anything outstanding for this PR, let me know and I'll work on it when I can scrape up some time.

@ameir The only thing we were thinking of adding was potentially doing both this change and tightening up the regular expression.

@stevendanna, I updated the regex to what I believe is a safe value.  You may have insights that I don't have, though.  On a default Chef Server install, the location block now resolves to:
location ~ "^/bookshelf/organization-.+/" {
  proxy_pass http://bookshelf;
}

In my tests, things look good.  Let me know what you think.


send file: change cache control behaviour

if files are restricted the cache-control header will now be set to "no-cache" so that resources are always checked to be fresh before being served.
some context on this PR can be found here: https://codimd.web.cern.ch/DpHiJGHSRlGGyPg1KNTcmw#
partly closes https://github.com/inveniosoftware/invenio-communities/issues/718

LGTM! Tests failing because of FAILED invenio_files_rest/helpers.py::PYCODESTYLE.

LGTM, but can you fix the tests?


[BUG] Furnaces are inconsistent

Please post multiple screenshots on a site like Imgur and post config files on a site like Pastebin or some other alternative.
N/A
Please describe the bug
What is the bug? What do you think the appropriate behavior would be for this feature? (Paste screenshots here)
Furnaces sometimes return as null and/or sometimes items are not properly saved to the furnaces configuration file.
If there is a stack trace in console, please post that here.
When an error occurs and you receive the "An internal error has occurred..." message there is some sort of error in console, please copy and past that here.
*Unknown if there are errors in console when attempting to save a furnace.
How to reproduce the error?
What can I do to reproduce the error you have experienced? Please be detailed.
It's inconsistent though I have experienced it in dev testing.
What is your Spigot Version and your plugin list?
What version of Spigot are you using? /ver What plugins are you using? /plugins
Plugin's shouldn't matter, assuming latest build of 1.17 and/or 1.16
What is the plugins version?
Please run '/pci version' in your console or in game and paste it here.
1.6.4 - Could have existed since furnace release.
Anything else I should know?
Is there something else that I should know before attempting to fix this bug?
This is created in idea of an issue on the resource page for easier tracking.

https://pastebin.com/i03qCCXv may be applicable to this issue as well.


Change name of public API header?

The 1.0 release is approaching, but before it happens, we might reconsider the name of the public API header of the JerryScript library. Now, it is called jerry-api.h, which is somewhat unusual. For an ordinary library user, writing #include <jerry.h> might be more intuitive.
The time of the release is close and the change might need adaptation at various places of the project, but we should think about it since whatever we choose will most probably stay with us for good (or, for a long time, at least), as the name of the header is also part of the fixed API.
(Note: I'm not proposing to change the name of jerry-port.h. That's OK, IMHO, as it is important for and used by port developers only.)

I don't mind to rename the header. I think the question is how risky this change is.

I think it is not the right time to change the header name. Such change implies an RC3. It will delay the release if we rename it.

In terms of release I think it's too late for an invasive change like that, we should only cherry-pick bug fixes for critical bugs which would block the release for one reason or another :)
In terms of header naming I think "jerryscript.h" would be even more appropriate since after all the project is called JerryScript not Jerry :)

OK, let's wait with renamings then. (BTW: calling the resulting library libjerry-core.a is also a bit unnatural, libjerry.a or libjerryscript.a would seem more clean.)
Removing the issue from the 1.0 release milestone but leaving it open as a reminder that we might still consider something like this in the future. (Feel free to close it if you disagree, though.)

Yes, I'd very much in favor of changing the header name to "jerryscript.h" and the library name to "libjerryscript.a" in the future :)
I think we should consider this for the next stable release after 1.0.


undefined reference to `_binary_x509_crt_bundle_start'

I'm trying to make use of the bundled certificates as per #37. This works fine as far as I can tell but the problem is that we don't have the magic asm() from esp-idf exposed anywhere in esp-idf-svc and so linking to these inline asm binary positions fails. I don't currently see a good way to fix this.
@kcking did you get this working perchance?

So this fails because they are using target_add_binary_data which embeds the data like so. I'm not sure there's a good way to imitate this.

 That have the same names as ${varname}*? Would that not work?

I did this:
extern "C" {
    static _binary_x509_crt_bundle_start: *const u8;
    static _binary_x509_crt_bundle_end: *const u8;
}

fn main() -> Result<()> {
}

and no dice:
  = note: Running ldproxy
          Error: Linker .embuild/espressif/tools/xtensa-esp32-elf/esp-2021r2-patch3-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc failed: exit status: 1
          STDERR OUTPUT:
         .embuild/espressif/tools/xtensa-esp32-elf/esp-2021r2-patch3-8.4.0/xtensa-esp32-elf/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: esp-idf/mbedtls/libmbedtls.a(esp_crt_bundle.c.obj):(.literal.esp_crt_bundle_attach+0x0): undefined reference to `_binary_x509_crt_bundle_start'
          collect2: error: ld returned 1 exit status

Hey @sergiogasquez sorry for the random ping but I couldn't help but notice that you did essentially the same thing just a few days ago. Would you be able to weigh in how you solved this particular issue when calling
    let mut client = EspHttpClient::new(&EspHttpClientConfiguration {
        use_global_ca_store: true,
        crt_bundle_attach: Some(esp_crt_bundle_attach),
        ..Default::default()
    })?;

?
Any hints would be super greatly appreciated!

Whoops that's weird! GitHub search only showed yours and not the original one.


Demonstrate broken cognito user pool client

Description of your changes
This is not intended to be merged, but just to demonstrate the current broken behavior which is fixed in #1021

Fixes #
I have:

[ ] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

/test-examples="examples/cognitoidp/userpooluicustomization.yaml"

/test-examples="examples/cognitoidp/userpoolclient.yaml"

/test-examples="examples/cognitoidp/userpoolclient-with-dashes.yaml, examples/cognitoidp/userpoolclient-observe.yaml"


Applying same fix to ForwardRequested as we did in BackRequested to h…

…andle users subscribing to ForwardRequeted but not setting Handled = true

See #206


Set up<EMAIL_ADDRESS>

Actually any of the following:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>This will allow verification of SSL certificates without having to disable WhoIs protection.

For future Marri: https://letsencrypt.org


clang-tidy-12 installation failes on ubuntu-20.04

Description
Dear Developers!
I can not install clang-tidy-12 package on ubuntu-20.04.
Please fix the APT issue so the proper packages will be available.
Thank you in advance!
My job failures:

with apt update
without apt update

Virtual environments affected

[ ] Ubuntu 16.04
[ ] Ubuntu 18.04
[X] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11
[ ] Windows Server 2016
[ ] Windows Server 2019

Image version and build link
Version: 20210726.1
Is it regression?
unknown
Expected behavior
Installation of clang-tidy-12 does not fail.
Actual behavior
It failes.
Repro steps
Run sudo apt-get install -f cmake libc-ares-dev libcurl4-openssl-dev libev-dev build-essential clang-tidy-12 clang-12 on ubuntu-20.04.

Hello @baranyaib90 . Thank you for your report. We will take a look.

Hey, @baranyaib90
We currently try to avoid using additional repos on Ubuntu images, you can install this one with:
- run: sudo bash -c "$(wget -O - https://apt.llvm.org/llvm.sh)"
- run: sudo apt update
- run: sudo apt-get install -f cmake libc-ares-dev libcurl4-openssl-dev libev-dev build-essential clang-tidy-12 clang-12

I'll close this issue but feel free to reopen it/tag me if you have any concerns.
Thanks!

Hi @LeonidLapshin,
as you can see in the "sudo apt-get update" output (when checking my linked "with apt update" logs) the "focal-updates/universe" repository is default Ubuntu repo. So it's not additional. Please check the output I provided.
It's simple Ubuntu 20.04 package I want: https://packages.ubuntu.com/focal-updates/clang-tidy-12
So please continue the investigation.

Hey, @baranyaib90
Clang 12 packages installed from PPA, the installation script don't use default Ubuntu repo, because these packages were absent when we added it to the image. After the installation PPA is removed and additional dependencies can not be installed :(
So for now if you want to install some additional packages you can delete current installation from PPA and install them from default repo or add a custom PPA using script and install dependencies from PPA.
There is no actual reason for this behavior and we'll change it to installation from default repo. I'll create PR soon and will share all details in this ticket :)
Thanks!

Hi @LeonidLapshin,
thank you very much for the investigation!
Now everything is clear for me.

LLVM 12.0.1 seems to be using GLIBC_2.33, which is not available on Ubuntu 20.04. You should use LLVM 12.0.0 instead.

@aminya , we don't install llvm on Ubuntu during image generation process, I guess setup action is the best option to use the correct version.

@aminya  I'll close the issue, but feel free to tag me here to reopen it if you have any concerns
Thanks!

Thank you!


Added support for internal CIDR

Right now the ec2 instances created by molecule allow an ingress rule to <IP_ADDRESS>/0 on the ssh port.
As we have a restrictive security policy, we only allow ssh traffic from within the subnet, therefore we need to be able to specify the CIDR that is allowed to ssh into the molecule ec2 instance.
As there can be multiple platforms I've decided to set up the configuration in the molecule.yml under the driver section. Although I don't know if it's the best place.
driver:
  name: ec2
  internal_cidr: <IP_ADDRESS>/24

Changes are backward compatible and shouldn't affect current users.
PR Type

Feature Pull Request

Hi @decentral1se, I've checked both cases, either specifying the internal_cidr and not specifying it and it worked as expected

@ssbarnea I've just changed the names of the variables, I don't see how it has broken the tests, could we rerun them?

Restarted the failed build. It was unrelated.


Lychee trys to parse math equation leading to erroneous error message.

For example:
$$
[\psi](\mathbf{L})
$$

Is interpreted as a link and checked, giving an erroneous error message.
Is there anyway to workaround this?  -- Thank you!

I'm assuming that's inside a Markdown file?

Is there anyway to workaround this? -- Thank you!

Well, you can exclude it with --exclude mathbf until we fixed the bug.

Ah thank you @mre ! I didn't realize the exclude would be that easy so I hadn't even looked yet. Thanks!

The solution to this bug is to support the maths syntax. We wouldn't really want to work out a spec and add custom parsers atop pulldown-cmark, so we are blocked on this being supported upstream.
It looks like there is some interest: https://github.com/raphlinus/pulldown-cmark/pull/622 https://github.com/rust-lang/mdBook/issues/2222
As this bug has a workaround, I think it would be ok to close this issue with the stance that we will support maths syntax when pulldown-cmark does. Of course, discussion can still take place on the closed issue and it can be re-opened by anyone who wishes.
@mre I will leave closing this to you if you agree.

Good call. Seems like upstream process on this feature is slow, so might not make much sense to hold our breath before it lands. Closing. In case this gets merged in the future, I'd be thankful if someone could reopen the issue.

Thanks for the notification.

👋 It got fixed by Hugo.

Thank you both for getting this done! 🙏


Feature test with Capybara:  Error connecting to Sphinx via the MySQL protocol.

Hi @pat
We are running into MySQL connection issue when running feature test relying on sphinx. It seems to happen if there is more than one test requiring sphinx, ie if we run each test one by one manually we don't get the error.
My dev environment is setup with docker but we have the same issue in our CI environment.
In the example below, the first test will pass and the second will fail with an Error connecting to Sphinx.
describe 'test something', sphinx: true do
  it 'does something' do
    # test loading a page requiring sphinx
  end

  it 'does something 2' do
    # test loading a page requiring sphinx
  end
end

It looks like ThinkingSphinx isn't ready yet for the second test, I tried adding a sleep after sleep ThinkingSphinx::Test.start but no luck.
I also added ThinkingSphinx::Test.running? but it tells me that ThinkingSphinx is still running at the start of the test, even when it's failing.
def self.running?
  config.controller.running?
end

Any pointers? I am not sure what else I can check.
Gems version
gem 'flying-sphinx',   '~> 1.3'
gem 'mysql2',          '~> 0.5.3'
gem 'thinking-sphinx', '~> 3.4'

sphinx config
development: &common
  morphology: stem_en
test:
  <<: *common
  mysql41: 9307
production:
  <<: *common
  version: 2.2.11

spec/support/sphinx.rb
RSpec.configure do |config|
  config.before(:each) do |example|
    if example.metadata[:sphinx]
      ThinkingSphinx::Test.init
      ThinkingSphinx::Test.start index: false
    end

    ThinkingSphinx::Configuration.instance.settings['real_time_callbacks'] =
      !!example.metadata[:sphinx]
  end

  config.after(:each) do |example|
    if example.metadata[:sphinx]
      ThinkingSphinx::Test.stop
      ThinkingSphinx::Test.clear
    end
  end
end

stacktrace
ActionView::Template::Error:
       Error connecting to Sphinx via the MySQL protocol. Can't connect to MySQL server on '<IP_ADDRESS>' (115)
     # /bundle/gems/mysql2-0.5.3/lib/mysql2/client.rb:90:in `connect'
     # /bundle/gems/mysql2-0.5.3/lib/mysql2/client.rb:90:in `initialize'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/connection/mri.rb:15:in `new'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/connection/mri.rb:15:in `client'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/connection/client.rb:7:in `close!'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/connection.rb:29:in `block in pool'
     # /bundle/gems/innertube-1.1.0/lib/innertube.rb:88:in `delete_element'
     # /bundle/gems/innertube-1.1.0/lib/innertube.rb:140:in `rescue in take'
     # /bundle/gems/innertube-1.1.0/lib/innertube.rb:139:in `take'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/connection.rb:37:in `take'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/search/batch_inquirer.rb:16:in `results'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/middlewares/inquirer.rb:9:in `block in call'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:164:in `block in instrument'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:164:in `instrument'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/logger.rb:3:in `log'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/middlewares/inquirer.rb:8:in `call'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/middlewares/geographer.rb:11:in `call'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/middlewares/sphinxql.rb:14:in `call'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/middlewares/attribute_typer.rb:12:in `call'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/middlewares/valid_options.rb:7:in `call'
     # /bundle/gems/middleware-0.1.0/lib/middleware/runner.rb:31:in `call'
     # /bundle/gems/middleware-0.1.0/lib/middleware/builder.rb:102:in `call'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/search.rb:92:in `populate'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/search.rb:71:in `meta'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/masks/pagination_mask.rb:43:in `total_entries'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/search.rb:139:in `block in method_missing'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/search.rb:138:in `each'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/search.rb:138:in `method_missing'
     # /bundle/gems/thinking-sphinx-3.4.2/lib/thinking_sphinx/active_record/base.rb:24:in `search_count'
     # ./lib/spree/sphinx/search.rb:36:in `retrieve_count'
     # /bundle/gems/scout_apm-2.6.10/lib/scout_apm/tracer.rb:77:in `block in retrieve_count_with_scout_instrument'
     # /bundle/gems/scout_apm-2.6.10/lib/scout_apm/tracer.rb:34:in `instrument'
     # /bundle/gems/scout_apm-2.6.10/lib/scout_apm/tracer.rb:73:in `retrieve_count_with_scout_instrument'
     # ./app/factories/search_factory.rb:86:in `searcher_call'
     # ./app/factories/search_factory.rb:36:in `total_products'
     # ./app/presenters/api/search_presenter.rb:10:in `total_products'
     # ./app/presenters/api/search_presenter.rb:17:in `total_pages'
     # ./app/views/api/shared/_products.json.jbuilder:5:in `_60832711be3f6dfe1def535d1fb47a1c'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/template.rb:159:in `block in render'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:166:in `instrument'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/template.rb:354:in `instrument'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/template.rb:157:in `render'
     # /bundle/gems/deface-1.3.2/lib/deface/action_view_extensions.rb:41:in `render'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/partial_renderer.rb:343:in `render_partial'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/partial_renderer.rb:311:in `block in render'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/abstract_renderer.rb:42:in `block in instrument'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:164:in `block in instrument'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:164:in `instrument'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/abstract_renderer.rb:41:in `instrument'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/partial_renderer.rb:310:in `render'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/renderer.rb:47:in `render_partial'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/renderer.rb:21:in `render'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/rendering_helper.rb:32:in `render'
     # /bundle/gems/haml-5.1.2/lib/haml/helpers/action_view_mods.rb:15:in `render'
     # /bundle/gems/jbuilder-2.11.2/lib/jbuilder/jbuilder_template.rb:128:in `_render_partial'
     # /bundle/gems/jbuilder-2.11.2/lib/jbuilder/jbuilder_template.rb:122:in `_render_partial_with_options'
     # /bundle/gems/jbuilder-2.11.2/lib/jbuilder/jbuilder_template.rb:215:in `_render_explicit_partial'
     # /bundle/gems/jbuilder-2.11.2/lib/jbuilder/jbuilder_template.rb:22:in `partial!'
     # ./app/views/api/searches/show.json.jbuilder:4:in `block in _4f8feb8faf510bb7a26268538015000c'
     # /bundle/gems/jbuilder-2.11.2/lib/jbuilder/jbuilder_template.rb:42:in `cache!'
     # ./app/views/api/searches/show.json.jbuilder:3:in `_4f8feb8faf510bb7a26268538015000c'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/template.rb:159:in `block in render'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:166:in `instrument'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/template.rb:354:in `instrument'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/template.rb:157:in `render'
     # /bundle/gems/deface-1.3.2/lib/deface/action_view_extensions.rb:41:in `render'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:54:in `block (2 levels) in render_template'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/abstract_renderer.rb:42:in `block in instrument'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:164:in `block in instrument'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:164:in `instrument'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/abstract_renderer.rb:41:in `instrument'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:53:in `block in render_template'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:61:in `render_with_layout'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:52:in `render_template'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:14:in `render'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/renderer.rb:42:in `render_template'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/renderer.rb:23:in `render'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/rendering.rb:104:in `_render_template'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/streaming.rb:217:in `_render_template'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/rendering.rb:83:in `render_to_body'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rendering.rb:52:in `render_to_body'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/renderers.rb:142:in `render_to_body'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/rendering.rb:26:in `render'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rendering.rb:36:in `render'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:44:in `block (2 levels) in render'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext/benchmark.rb:12:in `block in ms'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext/benchmark.rb:12:in `ms'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:44:in `block in render'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:87:in `cleanup_view_runtime'
     # /bundle/gems/activerecord-<IP_ADDRESS>/lib/active_record/railties/controller_runtime.rb:25:in `cleanup_view_runtime'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:43:in `render'
     # /bundle/gems/meta-tags-2.14.0/lib/meta_tags/controller_helper.rb:22:in `render'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/implicit_render.rb:36:in `default_render'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/basic_implicit_render.rb:4:in `block in send_action'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/basic_implicit_render.rb:4:in `tap'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/basic_implicit_render.rb:4:in `send_action'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/base.rb:188:in `process_action'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rendering.rb:30:in `process_action'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:126:in `call'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:506:in `block (2 levels) in compile'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:455:in `call'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:448:in `block (2 levels) in around'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:286:in `block (2 levels) in halting'
     # /bundle/gems/audited-4.10.0/lib/audited/sweeper.rb:14:in `around'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:405:in `public_send'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:405:in `block in make_lambda'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:285:in `block in halting'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:447:in `block in around'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:455:in `call'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:448:in `block (2 levels) in around'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:286:in `block (2 levels) in halting'
     # /bundle/gems/audited-4.10.0/lib/audited/sweeper.rb:14:in `around'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:405:in `public_send'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:405:in `block in make_lambda'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:285:in `block in halting'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:447:in `block in around'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:455:in `call'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:101:in `__run_callbacks__'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:750:in `_run_process_action_callbacks'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:90:in `run_callbacks'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/callbacks.rb:19:in `process_action'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rescue.rb:20:in `process_action'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:164:in `block in instrument'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:164:in `instrument'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/params_wrapper.rb:248:in `process_action'
     # /bundle/gems/activerecord-<IP_ADDRESS>/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/base.rb:126:in `process'
     # /bundle/gems/actionview-<IP_ADDRESS>/lib/action_view/rendering.rb:30:in `process'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal.rb:190:in `dispatch'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal.rb:262:in `dispatch'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:50:in `dispatch'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:32:in `serve'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/journey/router.rb:39:in `block in serve'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/journey/router.rb:26:in `each'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/journey/router.rb:26:in `serve'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:727:in `call'
     # /bundle/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:202:in `call!'
     # /bundle/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:169:in `call'
     # /bundle/gems/omniauth-2.0.4/lib/omniauth/builder.rb:45:in `call'
     # /bundle/gems/scout_apm-2.6.10/lib/scout_apm/middleware.rb:17:in `call'
     # /bundle/gems/warden-1.2.9/lib/warden/manager.rb:36:in `block in call'
     # /bundle/gems/warden-1.2.9/lib/warden/manager.rb:34:in `catch'
     # /bundle/gems/warden-1.2.9/lib/warden/manager.rb:34:in `call'
     # /bundle/gems/rack-<IP_ADDRESS>/lib/rack/etag.rb:27:in `call'
     # /bundle/gems/rack-<IP_ADDRESS>/lib/rack/conditional_get.rb:27:in `call'
     # /bundle/gems/rack-<IP_ADDRESS>/lib/rack/head.rb:12:in `call'
     # /bundle/gems/rack-<IP_ADDRESS>/lib/rack/session/abstract/id.rb:266:in `context'
     # /bundle/gems/rack-<IP_ADDRESS>/lib/rack/session/abstract/id.rb:260:in `call'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/cookies.rb:613:in `call'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/callbacks.rb:38:in `block in call'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:97:in `__run_callbacks__'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:750:in `_run_call_callbacks'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:90:in `run_callbacks'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/callbacks.rb:36:in `call'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/remote_ip.rb:79:in `call'
     # /bundle/gems/bugsnag-5.5.0/lib/bugsnag/rack.rb:42:in `call'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/debug_exceptions.rb:49:in `call'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
     # /bundle/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:36:in `call_app'
     # /bundle/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:24:in `block in call'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:69:in `block in tagged'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:26:in `tagged'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:69:in `tagged'
     # /bundle/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:24:in `call'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/request_id.rb:24:in `call'
     # /bundle/gems/rack-<IP_ADDRESS>/lib/rack/method_override.rb:24:in `call'
     # /bundle/gems/rack-<IP_ADDRESS>/lib/rack/runtime.rb:22:in `call'
     # /bundle/gems/rails_autoscale_agent-0.10.2/lib/rails_autoscale_agent/middleware.rb:27:in `call'
     # /bundle/gems/activesupport-<IP_ADDRESS>/lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/executor.rb:12:in `call'
     # /bundle/gems/rack-<IP_ADDRESS>/lib/rack/lock.rb:18:in `call'
     # /bundle/gems/rack-<IP_ADDRESS>/lib/rack/deflater.rb:44:in `call'
     # /bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/static.rb:136:in `call'
     # /bundle/gems/rack-<IP_ADDRESS>/lib/rack/sendfile.rb:110:in `call'
     # /bundle/gems/rack-cors-1.1.1/lib/rack/cors.rb:100:in `call'
     # /bundle/gems/railties-<IP_ADDRESS>/lib/rails/engine.rb:522:in `call'
     # /bundle/gems/rack-<IP_ADDRESS>/lib/rack/urlmap.rb:74:in `block in call'
     # /bundle/gems/rack-<IP_ADDRESS>/lib/rack/urlmap.rb:58:in `each'
     # /bundle/gems/rack-<IP_ADDRESS>/lib/rack/urlmap.rb:58:in `call'
     # /bundle/gems/capybara-3.35.3/lib/capybara/server/middleware.rb:60:in `call'
     # /bundle/gems/puma-5.6.4/lib/puma/configuration.rb:252:in `call'
     # /bundle/gems/puma-5.6.4/lib/puma/request.rb:77:in `block in handle_request'
     # /bundle/gems/puma-5.6.4/lib/puma/thread_pool.rb:340:in `with_force_shutdown'
     # /bundle/gems/puma-5.6.4/lib/puma/request.rb:76:in `handle_request'
     # /bundle/gems/puma-5.6.4/lib/puma/server.rb:441:in `process_client'
     # /bundle/gems/puma-5.6.4/lib/puma/thread_pool.rb:147:in `block in spawn_thread'
     # ------------------
     # --- Caused by: ---
     # Mysql2::Error::ConnectionError:
     #   Lost connection to MySQL server at 'handshake: reading initial communication packet', system error: 104
     #   /bundle/gems/mysql2-0.5.3/lib/mysql2/client.rb:90:in `connect'

I'm afraid I don't have any inspiration on what might be causing this - your setup is very similar to a project of my own, and the tests for that run reliably on GitHub Actions. 🤔
I do see that you're running old versions of TS and FS - upgrading is certainly recommended, but I would be surprised if that resolves this specific problem.
I guess it might be worth diving into your local copies of the TS and Riddle gems to try and catch the shell output from the stop/start calls to see if they hold any clues?

Thanks Pat, I'll have dig further when I get a chance.

Hi @gaetan-yg - I'm going to close this issue as it's been a few months without any change here. That said: if you find it's still a problem and have any further questions/fixes, please do comment, I'll be happy to re-open the issue.


unityhub: 3.8.0 -> 3.9.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for unityhub is: Official Unity3D app to download and manage Unity Projects and installations
meta.homepage for unityhub is: https://unity.com/
meta.changelog for unityhub is: https://unity.com/unity-hub/release-notes
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.9.1 with grep in /nix/store/hhqa8g6fqzvhn85igv3x0b23b8jdsvc8-unityhub-3.9.1
found 3.9.1 in filename of file in /nix/store/hhqa8g6fqzvhn85igv3x0b23b8jdsvc8-unityhub-3.9.1

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

unityhub

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/410554efd51567b54167e7c368f9a348cc70a7ea#unityhub

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

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

1 package built:

unityhub

Maintainer pings
cc @tesq0 @huantianad for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge

oh yeah i forgot about that


Use team.slug for GitHub auth teams matching

Currently Concourse is using team.name returned by GitHub's API for matching teams, this is causing issues when team name contain special characters, as these are encoded.
For example if you want to auth against team named Monkeys & Bananas under organization myorg, team has to be passed to Concourse as myorg/Monkeys \u0026 Bananas, else it's not matched.
GitHub teams API returns also team.slug, which is machine friendly version (also used in GitHub's urls) and would look like monkeys-bananas (see https://developer.github.com/v3/orgs/teams/#list-user-teams). I would suggest using this preferably to the name.
Please note that this is potentially breaking change for current configuration.

Yeah let's not break existing configurations. Could it support both?

Sure can do that...

@vito This should now add team in both forms, so we stay backward compatible (I would still eventually get rid of the name form potentially containing special characters, but that's just personal preferencs :))

Mind rebasing this to kick CI again? I fixed the error it's reporting (it was unrelated). There were also no tests updated for this, so I suspect one is broken or at least needs to be updated/added.

np, I'll rebase and try to add some test for this

@vito I did rebase on master, but the PR tests seems to fail still with:
package code.cloudfoundry.org/garden/client/connection/fakes: cannot find package "code.cloudfoundry.org/garden/client/connection/fakes" in any of:
	/usr/local/go/src/code.cloudfoundry.org/garden/client/connection/fakes (from $GOROOT)
	/tmp/build/0df9eea0/gopath/src/code.cloudfoundry.org/garden/client/connection/fakes (from $GOPATH)

am I missing something?
Updated the tests for this as well.

@stepanstipl Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@stepanstipl Thank you for signing the Contributor License Agreement!

Rebased on latest master, the tests are green now.

thanks!


Host downloadable binaries with HTTPS enabled

Now valid links from readme use HTTP protocol for downloading binaries.
http://sdkbinaries-ws.tonlabs.io/tonclient_1_darwin.gz
It's not secure - pls add HTTPS

Thanks we will add this soon


"Auto" event

This event might be specialized to send/receive different data than the original client. This would allow us to send a special signal that would only be understood by our modified client. (Still needs testing to prove it though.) The original auto event can easily be replaced by 1 or 2 PlayerTeamChanged events.

Modifying the "auto" event required admin privileges and also caused desynchronization issues. Instead, "chat indicator" event was modified to be sent just once with some custom data just after joining a room, to indicate that we are using a special client. If the host is using the same client mechanism, it would understand this message and register the sender client as a custom client that can receive custom events.
There is also a CustomEvent that can be sent by Room.sendCustomEvent, and received by Plugin.onCustomEvent. Room.sendCustomEvent sends this custom event message to only modified clients, because sending any unregistered signal/event causes an error on original Haxball clients.


⚠ Jenkins Plugins Artifactory has degraded performance

In 5316737, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1752 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 1971e8c after 1 hour, 4 minutes.


Documentation conversion from .md -> .adoc

[kind/Documentation]
A few todo's for .md to .adoc conversion:

[ ] Synchronization script must be updated
[ ] CLI reference script must also be updated to use .adoc instead of markdown.

@Preeticp Could you please add some more todo's / checklist of what needs to be done before the documentation goes live?

Convert all docs to asciidoc:

[ ] Installation
[ ] Getting Started
[ ] Development
[ ] Readme
[ ] CI reference
[ ] CLI reference
[ ] Completion Architecture
[ ] Examples
[ ] logging
[ ] tdd-workflow
[ ] validation architecture

@cdrage all docs have been converted to asciidoc, You can go ahead with changes in the script.

@cdrage we need to change the scripts. We can't mantain docs in both formats

/priority high

@kadel I'll push the changes today to use .adoc instead.

This shouldn't be closed.
https://github.com/openshift/odo/blob/master/cmd/cli-doc/cli-doc.go is still generating markdown and needs to be updated
/cc @girishramnani @cdrage

I have this already in the sprint planning and will be working on this soon. Fixing the generating markdown file as well as auto synchronization.

please close this issue @cdrage if its resolved

@girishramnani It's not yet, still need to add the auto sync working :+1:

Closing this issue in favour of: #1679


Add a GPU install build script

Helping a new user get everything installed and it was brought up that having an example GPU build script would be useful.
Also, it appears that our fork of MFEM that we use needs to be updated again. I ran into some cmake issues while helping this user out.

Our mfem fork has been updated so the cmake issue should now be fixed for users using CUDA and cmake version < 3.12

BLT needs to be updated to v0.3.6 in order to handle the CUDA and cmake version < 3.12 issue.

Fixed as of 5d9ae95956b2fa2f5b6366641ed9ec0bd37f544c


Remove semicolons in switch snippet

Not sure why those were present at all. Agree, they should go


engine: upgrade wasmer to ~4.0.0

L1 requires >=1.78 rust. It may be time to upgrade wasmer to avoid this issue:
Error: unsafe precondition(s) violated: ptr::copy_nonoverlapping requires that both pointer arguments are aligned and non-null and the specified memory ranges do not overlap

Completed in https://github.com/tari-project/tari-dan/pull/1184


[Bug]: "Unsupported Model File" error for HTDemucs_6s

Describe the bug
audio-separator --list
returns:
        "Demucs v4: htdemucs_6s": {             "5c90dfd2-34c22ccb.th": "https://dl.fbaipublicfiles.com/demucs/hybrid_transformer/5c90dfd2-34c22ccb.th",             "htdemucs_6s.yaml": "https://github.com/TRvlvr/model_repo/releases/download/all_public_uvr_models/htdemucs_6s.yaml"         }
but loading 5c90dfd2-34c22ccb.th does not work.
Have you searched for existing issues?  🔎

[X] I have searched and found no existing issues.

Screenshots or Videos
No response
Logs
No response
System Info
Operating System: Windows
Python version: 3.10
Other...

Additional Information
No response

That's just a little inconsistency in the model list output because there are multiple sub-files for the demucs models (which could probably be tidied up in the -l output)
to use that demucs model use the model filename "htdemucs_6s.yaml" instead 😄

like this:
separator = Separator()
separator.load_model(model_filename='htdemucs_6s.yaml')


1.18?

Will there be a version for 1.18/21w44a?

i'll definitely update this for the 1.18 release but i don't know if i'll update it for the snapshots (if i do there will be no config screen). although it shouldn't be hard to update it to 21w44a.

i've updated it to the 21w44a snapshot. :]


Python: update context variable with config while kernel run_async pipeline

current version of semantic_function call only updates main key in ContextVariables
# semantic_kernel.orchestration.sk_function
def from_semantic_config(
    ...
) -> "SKFunction":
    async def _local_func(client, request_settings, context):
        ...
        prompt = await function_config.prompt_template.render_async(context)
        completion = await client.complete_async(prompt, request_settings)
        context.variables.update(completion) # <- updates ContextVariables here

This makes it difficult to invoke skills in a pipeline form within the kernel.
It would be more easier if this code can be changed like "TO-BE"
kernel, skills = init_kernel()
vars = semantic_kernel.ContextVariables(
    variables={"genre": genre, "characters": characters, "text": text}
)

# AS-IS
result = await kernel.run_async(skills["ExtractTopic"], input_vars=vars)
var["topic"] = result.result

result = await kernel.run_async(skills["CreatePlot"], input_vars=var)
var["plot"] = result.result

# TO-BE
await kernel.run_async(
    skills["ExtractTopic"],
    skills["CreatePlot"],
    input_vars=var
)

To do that, semantic_function's config.json can have one more key namedoutput_key
and then updates vars in sk_function
# semantic_kernel.orchestration.sk_function
def from_semantic_config(
    ...
) -> "SKFunction":
    async def _local_func(client, request_settings, context):
        ...
        prompt = await function_config.prompt_template.render_async(context)
        completion = await client.complete_async(prompt, request_settings)
        context.variables.update(completion)

        output_key = function_config.prompt_template_config.output_key
        if (output_key):
            context.variables[output_key] = completion

find out similar concept in langchain

Hmm this is an interesting point. Right now we only reserve the {{$input}} keyword for prompts and I believe the input in the context gets overridden with the output of the previous step.
@dluc what do you think? What's the best way to capture output of skills in a pipeline?

Not something we are pursuing at this time. We're changing our inputs/outputs to help avoid these issue all together.


Keyword scope docs are misleading

Under https://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#keyword-scopes, the docs state that the following rule is used when determining keyword priority:
1. Created as a user keyword in the same file where it is used. These keywords have the highest priority and they are always used, even if there are other keywords with the same name elsewhere.
Robot Framework does not actually behave likes this when it comes to resource files. Consider the following three files:
Resource1.robot:
*** Keywords ***
A
    Log  Resource1

Resource2.robot:
*** Keywords ***
A
    Log  Resource2

B
    A

TestSuite1.robot:
*** Settings ***
Resource  Resource1.robot
Resource  Resource2.robot

*** Test Cases ***
Test Case 1
    B

Attempting to run TestSuite1.robot will fail with the following message:
FAIL : Multiple keywords with name 'A' found. Give the full name of the keyword you want to use:
    Resource1.A
    Resource2.A

So keyword B uses keyword A, which is "[c]reated as a user keyword in the same file where it is used". According to the documentation, this should just work. Yet it doesn't.
Considering the way namespacing is actually implemented, I'd suggest updating this line of documentation by adding "test case":
1. Created as a user keyword in the same test case file where it is used. These keywords have the highest priority and they are always used, even if there are other keywords with the same name elsewhere.
You may also want to add something like:

Note
When a test case file defines a keyword, all uses of keywords with the same name in resource files will be overridden, unless they use the full name of the keyword as explained in the next section.

Also, I'd like to use this opportunity to thank you for creating such an awesome piece of software, maintaining and improving it through the years and letting us use it for free. Much, much, much appreciated 🙂!

I've been thinking some more on this, and maybe this would be a better replacement for the first keyword scope rule:
1. Created as a user keyword in the test case file that is currently being executed. These keywords have the highest priority and they are always used, even if there are other keywords with the same name elsewhere.
This better covers how Robot Framework seems to work. My knowledge is still limited, though, so correct me if I'm wrong 🙂
Also, even with this version of the scope rule, I'd still like to see the aforementioned Note added. Not knowing that test-case-file-defined keywords override uses in imported resource files can cause some very, very unexpected behavior 😇

True, the docs should mention that keywords in the same file as the test case have highest priority.


Add Tiktaalik's Airlock Collection from SpaceDock

This pull request was automatically generated by SpaceDock on behalf of TiktaalikDreaming, to add Tiktaalik's Airlock Collection to CKAN.
Mod details:
name = /mod/865/Tiktaalik%27s%20Airlock%20Collection
author = TiktaalikDreaming
abstract = Have parts with no hatches?  Dislike hatches not being airlocks?  I have a solution for you.
license = MIT
Homepage = http://forum.kerbalspaceprogram.com/index.php?/topic/144599-wip-add-on-airlocks/
description =  This mod will be a few add on airlocks, mostly as surface attachable parts.
Over on the G+ community for KSP someone mentioned it would be nice to be able to add hatches to parts.  That's a task I leave to someone who wants lots of coding headaches.  However, and Airlock is quite fine.  Basically a small part, with a crew capacity of one, with a hatch.  I'll be adding in the MM config for Connected Living Space, so if you're using that, they'll be usable.  For us non-realism type users, they are available to add hatch functions to any part.
Now, they're not hatches.  You first need to transfer your kerbal to the airlock.  Then EVA them.  Repeating the process on the way back.  This is both because KSP requires the hatch to be on the part that holds the EVAing kerbal.  And because airlocks just work that way.
Now, initially, I'm making just one part, a mostly-replica of the ISS's Japanese Lab's Airlock, as it's about the smallest genuine airlock I could find.
Future plans;
Totally cheaty airlock/hatch.  A REALLY small hatch that is impossibly small, for anyone who just wants to add a hatch, and is OK transferring Kerbals to wafer thin strange dimensions in limbo until they're EVAed.
A hatch and docking node set for any sizes that aren't completely ludicrous (I'm not sure if the small docking node is big enough for a sane looking hatch, haven't checked yet).  So basically a part that's both a docking node and an airlock.  I'll base at least one of those on the Common Berthing Mechanism.  The part will be a bit longer than the existing docking nodes, but use the same widths for sizes 1, 2, and 3.

Please direct questions about this pull request to TiktaalikDreaming.

#rebuild

Maybe throw in git branch and git remote -v commands in the build.sh before the diff to see what the problem is with the git environment?

#rebuild


[Bug]: --filter argument inconsistent with documentation

Version
v29.0.2
Steps to reproduce

Install the latest version of Jest in a repository with existing test files
Confirm Jest runs all your test files properly by running jest without arguments
Create a file called filter.js in the current folder and paste the below contents

module.exports = testPaths => {
  return {
    filtered: testPaths,
  };
};

Run jest --filter=<absolute-path>/filter.js

Expected behavior
I would expect Jest to run all the tests, considering I am not filtering any tests from the given input
Actual behavior
Jest outputs Pattern: - 0 matches
Additional context
This is not consistent with what the documentation (that can be found here) suggests.
From the docs:
Path to a module exporting a filtering function. This asynchronous function receives a list of test paths which can be manipulated to exclude tests from running by returning an object with the "filtered" property.  Especially useful when used in conjunction with a testing infrastructure to filter known broken, e.g.
However, in the SearchSource.getTestPaths, we can see that it looks for a property called test in every item returned from the filter.
A workaround I did in my environment was to have it return the expected property, like below:
module.exports = (testPaths) => {
  ... code omitted ...
  return {
    filtered: testsToExecute.map((test) => ({ test })),
  };
}

We should probably either update the code so it only expects an array of string as the documentation suggests, or update the documentation to specify it requires the filtered property to have an array of shape { test: string}
Environment
System:
	OS: Windows 11 Home
	CPU: (8) x86-64
Binaries:
	Node: 16.14.0
	Yarn: 1.22.15
	npm: 8.3.1
npmPackages:
	jest: 29.0.2 (also tested on 26.6.3)

As mentioned in #12260, I believe the fix is fairly simple. Either update the documentation to specify that the return type is
type T = {
    filtered: { test: string }[];
};

or change this line SearchSource.js to
const filteredSet = new Set(filterResult.filtered);

I will say that the latter seems more clear as the current implementation seems redundant.

Thanks @jfw225, I think it makes more sense to just return an array of strings in the shape of { filtered: Array<string> }, considering the method accepts an array of strings too. I just created a PR for it.

https://github.com/jestjs/jest/releases/tag/v30.0.0-alpha.3


Attach Child Work and Attach Image do not work

Summary
The "Attach Work" and "Attach Image" links appear when you click on the "Attach Child" button on while logged in on the work show page, but do not do anything when pressed. It should take the admin user to that work type's create new form.
In addition, it is missing all of the options, which should be 'Attach Work', 'Attach Image', 'Attach OER', 'Attach ETD', 'Attach CDL'
https://github.com/scientist-softserv/palni_palci_knapsack/assets/84697174/f68e294e-e0fb-44ba-aaa4-6eae58c784a7
Goal
https://github.com/scientist-softserv/palni_palci_knapsack/assets/84697174/b0364788-4f7b-4bb4-a441-b2efcf5a4106
Acceptance Criteria

[ ] 'Attach Child' on a work show page has the following options:

[ ] Attach Work
[ ] Attach Image
[ ] Attach OER
[ ] Attach ETD
[ ] Attach CDL

[ ] Clicking the above options takes the admin user to the work type's create new form

=> [GenericWork, Image, Etd, Oer]
CDL is missing
(byebug) Hyrax::ChildTypes.method(:for).source_location
["/app/samvera/hyrax-webapp/gems/hyrax/app/services/hyrax/child_types.rb", 27]

The link part of this ticket has been fixed but the drop down of all the work options is still a TODO (correct me if I'm wrong). So I'm going to move this ticket back to ready for dev.

SoftServ QA: Pass ✅
https://github.com/user-attachments/assets/0a37a92c-798c-48e9-b0e5-2eb77c343d86


stuck on the installation window

after getting done with the preferences, the installation process for BloxStrap seems to go on forever.

On the "Installing Roblox" stage?

On the "Installing Roblox" stage?

on the "Select cancel to return to preferences" stage.

You clicked the "Preview" button, which previews the look of the bootstrapper.

ohh, yeah that explains it. thank you alot!


why ros2 topic list no data?

why ros2 topic list no data?

I can not find arduino_chatter topic by ros2 topic list command,my ros version is foxy.how could i do