Can't print the stars in page

The stars showed in a page cannot be printed with the page. They are not visible.
Is there a way to solve it?
To reproduce it, just open this page e print: http://lunarlogic.github.io/starability/
Thanks!

I have the same issue!!


Fix deleting indices which are currently exported

1. Why is this change necessary?
If the indices for with bin/console dal:refresh:index --use-queue are exported, then with bin/console es:index:cleanup -f also indices are deleted which are currently exported. This behavior is not very useful if the cleanup is done in a cronjob (a constant manual cleanup is not practical here).
2. What does this change do, exactly?
Checks if the indices to be deleted are currently exported. If so, it does not delete them.
3. Describe each step to reproduce the issue or behaviour.

start the command bin/console dal:refresh:index --use-queue
start the command bin/console es:index:cleanup -f

The new indices which are currently exported will be deleted
4. Please link to the relevant issues (if any).
#1528
5. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Currently the pipeline of JS and PHP failed unfortunately. But this seems to be not related to my changes. Can you check this @Shopware

This PR was closed due to inactivity. If this change is still important to you, feel free to create a new pull request.
For more information about our contribution guidelines, see https://docs.shopware.com/en/shopware-platform-dev-en/contribution/contribution-guideline


task "hasm.sh-hasm-hasm" took very long time

Hi the team,
My FALCON_unzip running for human genome has already been running for more than 2 weeks! Actually, it has been hovering the following commands of task "hasm.sh-hasm-hasm" for 12 days:
FALCON-integrate/FALCON-integrate_78e1569/fc_env/bin/python \
FALCON-integrate/FALCON-integrate_78e1569/fc_env/bin/fc_ovlp_filter_with_phase.py \
--fofn ../../2-asm-falcon/las.fofn --max_diff 120 --max_cov 120 --min_cov 1 --n_core 12 \
--min_len 2500 --db ../../1-preads_ovl/preads.db --rid_phase_map ./rid_to_phase.all

The following is my configuration:
[General]
job_type = SGE

[Unzip]
sge_blasr_aln = -pe OpenMP 24 -q long.q -l h_rt=720:00:00,mem_free=64G,h_vmem=64G

smrt_bin = /mnt/projects/liuxl/ctso4_projects/liuxl/Tools/pitchfork_my_python/pitchfork/dist/bin

sge_phasing = -pe OpenMP 12 -q long.q -l h_rt=720:00:00,mem_free=64G,h_vmem=64G

sge_hasm = -pe OpenMP 24 -q long.q -l h_rt=720:00:00,mem_free=64G,h_vmem=64G

sge_track_reads = -pe OpenMP 12 -q long.q -l h_rt=720:00:00,mem_free=64G,h_vmem=64G

unzip_concurrent_jobs = 64

Is that too long to run?

The step is usually fast but it could use too much memory for now (see https://github.com/PacificBiosciences/FALCON_unzip/issues/10). If that is the case for you computation node, you need to check if the process causes swapping. If so, you will need to reduce the amount of parallel process to reduce memory usage.

Hi @pb-jchin,
Hope this issue won't bother you too much.  I closed the threshold yesterday immediately when I found the reason.
Thank you very much for your prompt response.

@lxliangit, glad that you fin the root cause.  Sometimes, it is tricky for such debugging as it not easy to know the exact execution environment.


change to lowercase letter for 'Completion Policy'

Coverage increased (+0.01%) to 51.235% when pulling 808aeb0862decf40c2dcaed547a401d01e1e8237 on binyli/minor-fix into dc59c6351462da524abf897c7e4b54e7e400a6c4 on pai-0.14.y.

Coverage increased (+0.01%) to 51.235% when pulling 808aeb0862decf40c2dcaed547a401d01e1e8237 on binyli/minor-fix into dc59c6351462da524abf897c7e4b54e7e400a6c4 on pai-0.14.y.

Coverage increased (+0.01%) to 51.235% when pulling 808aeb0862decf40c2dcaed547a401d01e1e8237 on binyli/minor-fix into dc59c6351462da524abf897c7e4b54e7e400a6c4 on pai-0.14.y.


Race condition with retries and multiple workers

Symptoms
I'm observing jobs randomly being run sooner than scheduled. As far as I can tell, this occurs with multiple workers and retried jobs.
Investigation
I believe I see a race condition in the code.
Disclaimer: I haven't verified this particular path, as it's extremely difficult to reproduce it. I did, however, verified that scaling down to 1 worker makes the issue go away.
Consider this scenario:

Worker A fetches the job X:

https://github.com/python-arq/arq/blob/3914e48c530f0e5acf02cb340b1f8f3e201ba895/arq/worker.py#L386

Worker B fetches multiple jobs, including the job X. Worker B goes ahead and iterates through them, making its way to the job X:

https://github.com/python-arq/arq/blob/3914e48c530f0e5acf02cb340b1f8f3e201ba895/arq/worker.py#L435

In the meantime, Worker A finishes the job X and catches a Retry. It increments the job score:

https://github.com/python-arq/arq/blob/3914e48c530f0e5acf02cb340b1f8f3e201ba895/arq/worker.py#L701

Now, Worker B gets a chance to run X. It reads the score again:

https://github.com/python-arq/arq/blob/3914e48c530f0e5acf02cb340b1f8f3e201ba895/arq/worker.py#L449
And now, it’s in the future yet worker B continues normally :boom: As far as I can tell, steps 3 and 4 are not protected by the sync primitives. Does this sound plausible?
Possible fix
I haven't studied the code well enough. It looks like an additional check, like score > timestamp_ms() could be added around here to prevent the execution of a future retry:
https://github.com/python-arq/arq/blob/3914e48c530f0e5acf02cb340b1f8f3e201ba895/arq/worker.py#L450

Seems about right. We also experience the same thing
@chrisguidry @samuelcolvin could you please take a look?


Support Domain mode of WildFly and EAP servers

The version for WildFly 10 is 1.1.0.Beta1 on purpose. There was a problem with starting the server with version 1.0.0 and it was fixed in 1.1.0.Beta1.

This change is

Hey @aslakknutsen , fixed ! I think it looks better now.

Thanks! Would it make sense to add a profile for managed containers in domain mode? WDYT?

Hi, it is already there in the PR. The usage is following: WildFly Domain:10.0.0.Final:managed

Must have missed that. So we are all good for merging from your point of view?

Review status: 0 of 2 files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable

Yes, this is ready from my POV. It's been here for a few months.

I think my intention in the previous comment was to add those new containers to all profile for the Maven build.
I've tried to run following
mvn clean install -Darq.container.chameleon.configuration.chameleonTarget="WildFly Domain:10.0.0.Final:managed"

against latest master (you will need to resolve simple merge conflict in containers.yaml if you want to run it smoothly), but this leads to test failures.
@mgencur can you verify if that is also a problem on your side?

I would like to release Chameleon soon. @mgencur can you check on your side if there is an issue  which I encountered?
I would like to release new version soon :)

Hi, the problem could be caused by the version of container adapter - the correct version should be 2.0.0.Final. IIRC there was a rename of class in core for embedded containers. This means that container adapter 1.1.x embedded won't work with EAP 7 and WF10.

Anyway, if the version of the container adapter is fixed, the test is still failing with this exception:
DeploymentException: Could not determine the server-group to deploy the archive to.
This can be solved by specifying @TargetsContainer("main-server-group") for the deployment there in SimpleDeploymentTestCase

Hi, I've rebased my branch on latest master and changed the adapter version to 2.0.0.Final. Thanks for the tips Matous!
I've also added another test that runs for domain mode and added this run to the "all" profile. Let me know if there's anything else I should do. Cheers, Martin

Landed in https://github.com/arquillian/arquillian-container-chameleon/commit/296dc1609fc54eaa4947b2f9dd1c82ced4452b8d :rocket: Thanks a lot for your contribution :+1:


Patch utils: tentative v0.3.

Description
This PR adds several features and minor improvements. Three new modules are created: plot, utils, typing.

plot: Contains functions for plotting curvelet coefficients in different forms, including curveshow which shows all curvelet coefficients in space of frequency domain, and overlay_disks, which visualizes the energy of curvelet coefficients in different pars of the image in a similar way to the Kymatio scattering disk example. These plotting functions require the creation of specializes axes and grids, so convenience functions have been added, see new functions create_colorbar, create_axes_grid and create_inset_axes_grid, for example. Finally, another useful function to overlay a vector field in a similar manner to overlay_disks is included: overlay_arrows. All of the plotting functions are thoroughly documented with self-contained examples.
utils: Contains functions which are helpful when dealing with curvelet structures. apply_along_wedges, for example, maps a lambda function to each curvelet coefficient organized in a curvelet structure. energy is an utility function for computing the energy of a single wedge. Putting these two together can create a structure of curvelet energies. Another useful utility function array_split_nd, splits an N-dimensional array in chunks for each dimension. For example, if you want to split a 2D array into 4 quadrants, you can do array_split_nd(two_d_array, 2, 2). This function also handles uneven splits. It is essentially the N-dimensional version of NumPy's array_split. A similar function that only supports even splits is also included, split_nd.
typing: Contains some useful classes for type annotation: FDCTStructLike, a list of list of nd-arrays and RecursiveListNDArray, a recursive list of nd-arrays.

Suggestion for review
Clone, pip install -e ., run pytest and make doc; make servedoc. From the docs, run the examples in the documentation in an IPython/Jupyter session. Ignore the changes to the cpp files: it is just a reformatting. Run flake8 curvelops/ and mypy curvelops/.

This looks very good. A few comments based on my process going through what you suggested:

There doesn't seem to exist any requirement/environment for developers, so whilst I can easily install myself the required libraries for tests and doc, it would be good to have an easy to install env like in pylops.
The documentation doesn't seem to have working examples right? Just code snippets. For now I think it's ok but it is a bit tedious to copy and paste examples and run them (unless I am missing something). I did it for some of them and didn't find any error. Moving to sphinx-gallery is probably a good idea.
Not sure what you plan to do with the doc (host it on Github pages and build it locally? I do the same in PyMarchenko due to heavy compute on some examples...) or let the user just build it for themselves?

Apart from these comments, feel free to go ahead and merge at any time :)

Thanks @mrava87, I added the requirements and improved the Makefile to go along with it. Regarding your other comments, I think it would be a good idea to host it in github pages, what do you think? And I agree with the sphinx-gallery, as right now the examples are just a collection of notebooks. I will try to figure out the sphinx-gallery in the coming days (new issue #12). Could you investigate how the github pages would work within the PyLops namespace and add any recommentations here: #13?
Feel free to merge this if you are happy with it.


API: random_state argument support

Hi @j-ittner @joerg-schneider!
Here's a small addition to SampleBalancer - random_state argument for reproducible idempotent balancing, ready for comments.

Thanks for the great suggestion 👍


USDT Swaps

Dear Foonsun,
In huobi_usdt_swap, async def place_orders has orders_data for trader.create_orders as
{"price": new_price, "quantity": quantity, "action": action, "order_type": ORDER_TYPE_LIMIT, "lever_rate": 1}._
Question 1:
How can I set USDT Swaps to have cross margin mode instead of isolated margin mode in orders_data or config.json?
Do I add "margin_mode":"cross margin mode"as
{"price": new_price, "quantity": quantity, "action": action, "order_type": ORDER_TYPE_LIMIT, "lever_rate": 1,"margin_mode":"cross margin mode"}
as described in "https://huobiapi.github.io/docs/usdt_swap/v1/en/#query-assets-and-positions-cross-margin-mode".
Question 2:
In  async def on_event_position_update, I want to compute Liquidation Price and margin (position, frozen,..)   based on
cross margin mode.  What is the right way to achieve cross margin mode?
In document, there are POST linear-swap-api/v1/swap_cross_sub_position_info supporting cross margin mode.   I am confused.
Question 3:
Why "huobi_usdt_swap_trade.py" and "huobi_usdt_swap_market.py" in alpha/platforms/ are required instead of using previous swap market and trade?
Are "cross" and "isolated" margin logic to separate out platforms?
Best regards,
Ingyu

Dear Ingyu,
Question 1:
How can I set USDT Swaps to have cross margin mode instead of isolated margin mode in orders_data or config.json?
Cross Margined Mode interfaces will be added in the project later.It's unavailable now.
margin_mode":"cross margin mode" will be passed as parameters of create_orders/create_order interfaces.
Question 2:
Hi, you can use linear-swap-api/v1/swap_cross_account_position_info to get the latest Liquidation price.This interface will be added later.
Question 3:
Hi, "huobi_usdt_swap_market" and "huobi_usdt_swap_trade.py" are similar to the swap market and trade.But indeed there are two systems. The interfaces may not be same.
"cross" and "isolated" margin logic will be integrated into the same usdt swap platform.

Dear Foonsun,
Thanks for detailed answers.  I am looking forward to use "cross" and "isolated" margin logic.
Best regards,
Ingyu

Hi,
There will be “USDTSWAP_CROSS” in the config.json to indicate the cross
margined mode.
New platform will be added for The cross mode for simple use.
Best Regards,
foonsun
On Sat, Dec 12, 2020 at 8:33 PM igkoh<EMAIL_ADDRESS>wrote:

Coin Swaps have config.jon and orders_data as
config.json { ... "symbol" "BTC-USD", "contract_type": "SWAP" } {"price":
new_price, "quantity": quantity, "action": action, "order_type":
ORDER_TYPE_LIMIT, "lever_rate": 1}.
How can I set USDT Swaps to have cross margin mode instead of
isolated margin mode in config.json and orders_data?
Best regards,
Ingyu
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hbdmapi/huobi_futures_Python/issues/45, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABRSHVH73BBFICFP4ZFRGR3SUNPKZANCNFSM4UYDEQOA
.

@igkoh Hi, igkoh. The cross margin mode of usdt swap has been integrated in the alphaquant. feel free to contract with me if any questions.


Not full screen

Hi,
First, thanks for this nice controller port !
I downloaded latest release ('release.zip') and placed both files within my GoG install folder. It runs and I can use my controller, but:

I got a strange "Windows 2000 restricted user" message right after execution (that goes away if I run your exe as admin)
The game is not full screen and displayed in a small 4:3 space at the top-left of my screen

Do you have any hints on what happened?
Thanks in advance.
Felix.

Edit:
I fixed the main problem of not full screened game (but I still got the "Win 2000" warning message)
=> With a GoG install, your files need to be put in C:\Program Files (x86)\GOG Galaxy\Games\Diablo\dx
=> And NOT in the main Diablo folder (i.e. [..]\Games\Diablo)
Maybe you could precise this in the 'README.txt' of your release?
Thanks a lot again!
Felix.

Edit:
I fixed the main problem of not full screened game (but I still got the "Win 2000" warning message)
=> With a GoG install, your files need to be put in C:\Program Files (x86)\GOG Galaxy\Games\Diablo\dx
=> And NOT in the main Diablo folder (i.e. [..]\Games\Diablo)
Maybe you could precise this in the 'README.txt' of your release?
Thanks a lot again!
Felix.


Befit gym website

Befit a gym website

Hello @shashank-2310 , first of all thanks for collaborating with me!! Really, it looks very nice!! But I have 2 queries...1) Why do you wanna change the maximum subarray.cpp file in leetcode folder??? 2) Where is your HTML file for this website.....

I have just improved its readability a bit by adding some spaces and line breaks.
Befit has all the relevant files, kindly check again.


problem building on mac

Hi,
I've been using this wonderful beamer template for some time. Rather recently, I discovered a problem when building on macOS:
(./theme/beamerfontthemeHelmholtzAI.sty

! Package beamerhelmholtzai Error: Patching original frame title failed.

See the beamerhelmholtzai package documentation for explanation.
Type  H <return>  for immediate help.
 ...

l.202 ...tching original frame title failed}\@ehc}

) (./theme/beamercolorthemeHelmholtzAI.sty)

Any ideas?

Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).
$ make
Rc files read:
  NONE
Latexmk: This is Latexmk, John Collins, 7 Jan. 2023. Version 4.79.
No existing .aux file, so I'll make a simple one, and require run of *latex.
Latexmk: applying rule 'xelatex'...
Rule 'xelatex':  Reasons for rerun
Category 'other':
  Rerun of 'xelatex' forced or previously required

------------
Run number 1 of rule 'xelatex'
------------
------------
Running 'xelatex -no-pdf -synctex=1 -interaction=nonstopmode -recorder  "talk.tex"'
------------
This is XeTeX, Version 3.141592653-2.6-0.999995 (TeX Live 2023/Homebrew) (preloaded format=xelatex)
 restricted \write18 enabled.
entering extended mode
(./talk.tex
LaTeX2e <2022-11-01> patch level 1
L3 programming layer <2023-02-22>
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamer.
cls
Document Class: beamer 2023/02/20 v3.69 A class for typesetting presentations

(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
asemodes.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/etoolbox/etool
box.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
asedecode.sty))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/iftex/iftex.
sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
aseoptions.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/graphics/keyva
l.sty))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/geometry/geome
try.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/iftex/ifvtex
.sty))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/pgf/math/pgfma
th.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/pgf/utilities/
pgfrcs.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/utilitie
s/pgfutil-common.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/utilitie
s/pgfutil-latex.def)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/utilitie
s/pgfrcs.code.tex
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/pgf.revi
sion.tex)))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/pgf/utilities/
pgfkeys.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/utilitie
s/pgfkeys.code.tex
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/utilitie
s/pgfkeyslibraryfiltered.code.tex)))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/math/pgf
math.code.tex
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/math/pgf
mathutil.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/math/pgf
mathparser.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/math/pgf
mathfunctions.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/math/pgf
mathfunctions.basic.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/math/pgf
mathfunctions.trigonometric.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/math/pgf
mathfunctions.random.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/math/pgf
mathfunctions.comparison.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/math/pgf
mathfunctions.base.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/math/pgf
mathfunctions.round.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/math/pgf
mathfunctions.misc.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/math/pgf
mathfunctions.integerarithmetics.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/math/pgf
mathcalc.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/math/pgf
mathfloat.code.tex)))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/base/fleqn.clo
)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/base/size11.cl
o)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/pgf/basiclayer
/pgfcore.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/graphics/graph
icx.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/graphics/graph
ics.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/graphics/trig.
sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/graphics-cfg/g
raphics.cfg)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/graphics-def/x
etex.def)))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/pgf/systemlaye
r/pgfsys.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/systemla
yer/pgfsys.code.tex
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/systemla
yer/pgf.cfg)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/systemla
yer/pgfsys-xetex.def
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/systemla
yer/pgfsys-dvipdfmx.def
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/systemla
yer/pgfsys-common-pdf.def))))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/systemla
yer/pgfsyssoftpath.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/systemla
yer/pgfsysprotocol.code.tex))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/xcolor/xcolor.
sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/graphics-cfg/c
olor.cfg)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/graphics/mathc
olor.ltx))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/basiclay
er/pgfcore.code.tex
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/math/pgf
int.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/basiclay
er/pgfcorepoints.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/basiclay
er/pgfcorepathconstruct.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/basiclay
er/pgfcorepathusage.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/basiclay
er/pgfcorescopes.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/basiclay
er/pgfcoregraphicstate.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/basiclay
er/pgfcoretransformations.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/basiclay
er/pgfcorequick.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/basiclay
er/pgfcoreobjects.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/basiclay
er/pgfcorepathprocessing.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/basiclay
er/pgfcorearrows.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/basiclay
er/pgfcoreshade.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/basiclay
er/pgfcoreimage.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/basiclay
er/pgfcoreexternal.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/basiclay
er/pgfcorelayers.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/basiclay
er/pgfcoretransparency.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/basiclay
er/pgfcorepatterns.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/basiclay
er/pgfcorerdf.code.tex)))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/pgf/utilities/
xxcolor.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/base/atbegshi-
ltx.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/hyperref/hyper
ref.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/ltxcmds/ltxc
mds.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pdftexcmds/p
dftexcmds.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/infwarerr/in
fwarerr.sty))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/kvsetkeys/kvse
tkeys.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/kvdefinekeys
/kvdefinekeys.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pdfescape/pd
fescape.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/hycolor/hycolo
r.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/letltxmacro/le
tltxmacro.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/auxhook/auxhoo
k.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/hyperref/namer
ef.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/refcount/refco
unt.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/gettitlestri
ng/gettitlestring.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/kvoptions/kvop
tions.sty)))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/hyperref/pd1en
c.def)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/intcalc/intc
alc.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/etexcmds/ete
xcmds.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/hyperref/puenc
.def)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/url/url.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/bitset/bitse
t.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/bigintcalc/b
igintcalc.sty))

Package hyperref Message: Stopped early.

)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/hyperref/hxete
x.def
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/stringenc/st
ringenc.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/rerunfilecheck
/rerunfilecheck.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/base/atveryend
-ltx.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/uniquecounte
r/uniquecounter.sty)))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
aserequires.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
asecompatibility.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
asefont.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/amsfonts/amssy
mb.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/amsfonts/amsfo
nts.sty))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/sansmathaccent
/sansmathaccent.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/koma-script/sc
rlfile.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/koma-script/sc
rlfile-hook.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/koma-script/sc
rlogo.sty)))))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
asetranslator.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/translator/tra
nslator.sty))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
asemisc.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
asetwoscreens.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
aseoverlay.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
asetitle.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
asesection.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
aseframe.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
aseverbatim.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
aseframesize.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
aseframecomponents.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
asecolor.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
asenotes.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
asetoc.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
asetemplates.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
aseauxtemplates.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
aseboxes.sty)))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
aselocalstructure.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/tools/enumerat
e.sty))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
asenavigation.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
asenavigationsymbols.tex))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
asetheorems.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/amsmath/amsmat
h.sty
For additional information on amsmath, use the `?' option.

(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/amsmath/amstex
t.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/amsmath/amsgen
.sty))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/amsmath/amsbsy
.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/amsmath/amsopn
.sty))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/amscls/amsthm.
sty))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerb
asethemes.sty))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamert
hemedefault.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerf
ontthemedefault.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamerc
olorthemedefault.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beameri
nnerthemedefault.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/beamer/beamero
uterthemedefault.sty))) (./helmholtzai.sty (./theme/beamerthemeHelmholtzAI.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/booktabs/bookt
abs.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/base/fontenc.s
ty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/lm/t1lmss.fd))

(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/fontspec/fonts
pec.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/l3packages/xpa
rse/xparse.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/l3kernel/expl3
.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/l3backend/l3ba
ckend-xetex.def)))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/fontspec/fonts
pec-xetex.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/base/fontenc.s
ty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/fontspec/fonts
pec.cfg)))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/base/inputenc.
sty

Package inputenc Warning: inputenc package ignored with utf8 based engines.

)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/listings/listi
ngs.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/listings/lstmi
sc.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/listings/listi
ngs.cfg))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/pgf/frontendla
yer/tikz.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/pgf/basiclayer
/pgf.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/modules/
pgfmoduleshapes.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/modules/
pgfmoduleplot.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/pgf/compatibil
ity/pgfcomp-version-0-65.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/pgf/compatibil
ity/pgfcomp-version-1-18.sty))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/pgf/utilities/
pgffor.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/utilitie
s/pgffor.code.tex))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/frontend
layer/tikz/tikz.code.tex
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/librarie
s/pgflibraryplothandlers.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/modules/
pgfmodulematrix.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/frontend
layer/tikz/libraries/tikzlibrarytopaths.code.tex)))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/frontend
layer/tikz/libraries/tikzlibrarycalc.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/frontend
layer/tikz/libraries/tikzlibraryturtle.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/frontend
layer/tikz/libraries/tikzlibrarypositioning.code.tex)
(./theme/beamerfontthemeHelmholtzAI.sty

! Package beamerhelmholtzai Error: Patching original frame title failed.

See the beamerhelmholtzai package documentation for explanation.
Type  H <return>  for immediate help.
 ...

l.202 ...tching original frame title failed}\@ehc}

) (./theme/beamercolorthemeHelmholtzAI.sty)
(./theme/beamerinnerthemeHelmholtzAI.sty)
(./theme/beamerouterthemeHelmholtzAI.sty)))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/fontawesome5/f
ontawesome5.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/l3packages/l3k
eys2e/l3keys2e.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/fontawesome5/f
ontawesome5-utex-helper.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/fontawesome5/t
ufontawesomefree.fd)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/fontawesome5/t
ufontawesomebrands.fd)))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/natbib/natbib.
sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/appendixnumber
beamer/appendixnumberbeamer.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/pdfpages/pdfpa
ges.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/base/ifthen.st
y)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/tools/calc.sty
)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/eso-pic/eso-pi
c.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/pdfpages/ppxet
ex.def))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/animate/animat
e.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/oberdiek/ifdra
ft.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/media9/pdfbase
.sty)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/zref/zref-absp
age.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/zref/zref-base
.sty))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/ocgx2/ocgbase.
sty))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/librarie
s/pgflibraryarrows.meta.code.tex)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/frontend
layer/tikz/libraries/tikzlibraryarrows.code.tex
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/librarie
s/pgflibraryarrows.code.tex))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/frontend
layer/tikz/libraries/tikzlibrarydecorations.text.code.tex
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/frontend
layer/tikz/libraries/tikzlibrarydecorations.code.tex
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/modules/
pgfmoduledecorations.code.tex))
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/generic/pgf/librarie
s/decorations/pgflibrarydecorations.text.code.tex))

Package hyperref Warning: Token not allowed in a PDF string (Unicode):
(hyperref)                removing `\noindent' on input line 38.

Package hyperref Warning: Token not allowed in a PDF string (Unicode):
(hyperref)                removing `\inserttitle' on input line 43.

Package hyperref Warning: Token not allowed in a PDF string (Unicode):
(hyperref)                removing `\insertsubtitle' on input line 43.

(./talk.aux)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/base/ts1cmr.fd
)
*geometry* driver: auto-detecting
*geometry* detected driver: xetex

Package hyperref Warning: Rerun to get /PageLabels entry.

(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/translator/tra
nslator-basic-dictionary-English.dict)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/translator/tra
nslator-bibliography-dictionary-English.dict)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/translator/tra
nslator-environment-dictionary-English.dict)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/translator/tra
nslator-months-dictionary-English.dict)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/translator/tra
nslator-numbers-dictionary-English.dict)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/translator/tra
nslator-theorem-dictionary-English.dict)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/pdflscape/pdfl
scape.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/pdflscape/pdfl
scape-nometadata.sty
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/graphics/lscap
e.sty)))
No file talk.nav.
[1]
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/amsfonts/umsa.
fd)
(/usr/local/Cellar/texlive/20230313_2/share/texmf-dist/tex/latex/amsfonts/umsb.
fd)
Overfull \vbox (2.91675pt too high) detected at line 105

Overfull \vbox (10.2738pt too high) has occurred while \output is active
[2]
Overfull \vbox (2.91675pt too high) detected at line 105

Overfull \vbox (10.2738pt too high) has occurred while \output is active
[3]
Overfull \vbox (2.91675pt too high) detected at line 105

Overfull \vbox (10.2738pt too high) has occurred while \output is active
[4]

Package natbib Warning: Citation `olah2020naturally' on page 5 undefined on inp
ut line 120.

Overfull \vbox (10.2738pt too high) has occurred while \output is active
[5]

Package natbib Warning: Citation `olah2020naturally' on page 6 undefined on inp
ut line 120.

Overfull \vbox (10.2738pt too high) has occurred while \output is active
[6]

Package natbib Warning: Citation `bekkers-lecture21' on page 7 undefined on inp
ut line 166.

Package natbib Warning: Citation `pmlr-v48-cohenc16' on page 7 undefined on inp
ut line 166.

Package natbib Warning: Citation `cesa2019' on page 7 undefined on input line 1
66.

Overfull \vbox (3.60536pt too high) detected at line 166

Overfull \vbox (10.2738pt too high) has occurred while \output is active
[7]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[8]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[9]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[10]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[11]
Overfull \hbox (17.07181pt too wide) in paragraph at lines 238--238
[][]

Overfull \vbox (22.37025pt too high) detected at line 238

Overfull \vbox (10.2738pt too high) has occurred while \output is active
[12]
Overfull \hbox (7.2992pt too wide) in paragraph at lines 238--238
[][]

Overfull \vbox (22.37025pt too high) detected at line 238

Overfull \vbox (10.2738pt too high) has occurred while \output is active
[13]
Overfull \hbox (7.2992pt too wide) in paragraph at lines 238--238
[][]

Overfull \vbox (22.37025pt too high) detected at line 238

Overfull \vbox (10.2738pt too high) has occurred while \output is active
[14]
Overfull \hbox (7.2992pt too wide) in paragraph at lines 238--238
[][]

Overfull \vbox (22.37025pt too high) detected at line 238

Overfull \vbox (10.2738pt too high) has occurred while \output is active
[15]
Overfull \hbox (7.2992pt too wide) in paragraph at lines 238--238
[][]

Overfull \vbox (10.2738pt too high) has occurred while \output is active
[16]
Overfull \vbox (21.55809pt too high) detected at line 251

Overfull \vbox (10.2738pt too high) has occurred while \output is active
[17]
Overfull \vbox (21.55809pt too high) detected at line 251

Overfull \vbox (10.2738pt too high) has occurred while \output is active
[18]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[19]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[20]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[21]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[22]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[23]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[24]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[25]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[26]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[27]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[28]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[29]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[30]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[31]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[32]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[33]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[34]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[35]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[36]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[37]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[38]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[39]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[40]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[41]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[42]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[43]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[44]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[45]
Overfull \vbox (10.2738pt too high) has occurred while \output is active
[46]
No file talk.bbl.

Overfull \vbox (10.2738pt too high) has occurred while \output is active
[47]

Package hyperref Warning: Token not allowed in a PDF string (Unicode):
(hyperref)                removing `\translate ' on input line 368.

LaTeX Warning: Hook 'shipout/lastpage' executed on wrong page (1 not 52).
               Rerun to correct this.

(./talk.aux)

LaTeX Warning: Label(s) may have changed. Rerun to get cross-references right.

Package rerunfilecheck Warning: File `talk.out' has changed.
(rerunfilecheck)                Rerun to get outlines right
(rerunfilecheck)                or use package `bookmark'.

 )
(see the transcript file for additional information)
Output written on talk.xdv (52 pages, 418208 bytes).
SyncTeX written on talk.synctex.gz.
Transcript written on talk.log.
Latexmk: Missing input file 'talk.nav' (or dependence on it) from following:
  No file talk.nav.
Latexmk: Missing bbl file 'talk.bbl' in following:
 No file talk.bbl.
Latexmk: Getting log file 'talk.log'
Latexmk: Examining 'talk.fls'
Latexmk: Examining 'talk.log'
Latexmk: References changed.
Latexmk: References changed.
Latexmk: References changed.
Latexmk: Log file says output to 'talk.xdv'
Latexmk: ====List of undefined refs and citations:
  Citation `olah2020naturally' on page 5 undefined on input line 120
  Citation `olah2020naturally' on page 6 undefined on input line 120
  Citation `bekkers-lecture21' on page 7 undefined on input line 166
  Citation `pmlr-v48-cohenc16' on page 7 undefined on input line 166
  Citation `cesa2019' on page 7 undefined on input line 166
Latexmk: If appropriate, the -f option can be used to get latexmk
  to try to force complete processing.
Latexmk: Found bibliography file(s):
  ./references.bib
Latexmk: Summary of warnings from last run of *latex:
  Latex failed to resolve 5 citation(s)
Latexmk: Errors, so I did not complete making targets
Collected error summary (may duplicate other messages):
  xelatex: Command for 'xelatex' gave return code 1
      Refer to 'talk.log' and/or above output for details

make: *** [talk.pdf] Error 12
section_end:1689066286:step_script
section_start:1689066286:cleanup_file_variables
Cleaning up project directory and file based variables
section_end:1689066288:cleanup_file_variables
ERROR: Job failed: Process exited with status 1

I now see this problem on linux as well:
(/usr/local/texlive/2022/texmf-dist/tex/generic/pgf/frontendlayer/tikz/librarie
s/tikzlibrarypositioning.code.tex) (./theme/beamerfontthemeHelmholtzAI.sty
! Package beamerhelmholtzai Error: Patching original frame title failed.
See the beamerhelmholtzai package documentation for explanation.
Type  H <return>  for immediate help.
 ...

l.202 ...tching original frame title failed}\@ehc}

) (./theme/beamercolorthemeHelmholtzAI.sty)

This is with texlive-full on fedora 38.

Digging a bit further, I added the following statement:

    \ifpatchable*{\beamer@@frametitle}%
      {%true
        \PackageInfo{beamerhelmholtzai}{Patching beamer--frametitle is POSSIBLE}\@ehc
      }{%false
        \PackageError{beamerhelmholtzai}{Patching beamer--frametitle is impossible}\@ehc}

Just before \patchcmd{\beamer@@frametitle}% in ./theme/beamerfontthemeHelmholtzAI.sty which produces the error stated above. The false path was triggered which hints to the fact why the entire patchcmd call will fail.
Fun fact:

all CI builds fail for me
locally on fc38, the error is NOT triggered when I remove the ifpatchable call

I am building with:
xelatex -no-pdf -synctex=1 -interaction=nonstopmode --shell-escape -recorder  "example.tex"

at the version:
$ xelatex --version
XeTeX 3.141592653-2.6-0.999994 (TeX Live 2022/CVE-2023-32700 patched)
kpathsea version 6.3.4
Copyright 2022 SIL International, Jonathan Kew and Khaled Hosny.
There is NO warranty.  Redistribution of this software is
covered by the terms of both the XeTeX copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the XeTeX source.
Primary author of XeTeX: Jonathan Kew.
Compiled with ICU version 72.1; using 72.1
Compiled with zlib version 1.2.13; using 1.2.13
Compiled with FreeType2 version 2.13.0; using 2.13.0
Compiled with Graphite2 version 1.3.14; using 1.3.14
Compiled with HarfBuzz version 7.1.0; using 7.1.0
Compiled with libpng version 1.6.37; using 1.6.37
Compiled with pplib version v2.05 less toxic i hope
Compiled with fontconfig version 2.14.2; using 2.14.2

It seems that new TexLive stacks are broken in combination with the template. It seems that only the legacy stacks are working. We do not now yet what the reason is.


Null checks

We used Pie Chart and every time we would navigate to the screen that had the pie chart the whole app would freeze and just crash.
It was because there was a NULL in the mix of values. This was horrible to debug because there wasn't any logging or error check on it. Could you possible add some?

This sounds like a good idea, I would welcome a PR 🙂

This is not just with null values if you have all 0 it will crash and if you have two 0 it will not load the pie chart with 3+ objects in your data set but will display the labels


Create debug docker images for jaeger backends

Signed-off-by: Ashmita Bohara<EMAIL_ADDRESS>
Which problem is this PR solving?
Tackles https://github.com/jaegertracing/jaeger/issues/2493
Short description of the changes
As part of this PR, we are creating separate images for jaeger backend components.

Hi @yurishkuro
Thank you for the review. It definitely makes sense to generate two images out of a single Dockerfile. Let me work on it and update the PR.

I have another question related to this debug image:

Do we need any other debugging tool as part of this image other than delve ?

Do we need any other debugging tool as part of this image other than delve ?

I think the biggest ask was not so much the debug tools, but just any tools, because when we build from scratch we don't even get a shell for minimal troubleshooting.

I think the biggest ask was not so much the debug tools, but just any tools, because when we build from scratch we don't even get a shell for minimal troubleshooting.

True. For the debug images, I would even base it on something else. Note that the CMD instruction should also be custom for the debug image.

Few more questions I have is:

let's say a user face an issue in production. Having separate image for debugging means asking user to deploy that debug image in production separately. In case of systems like k8s, we can't have just one pod of different image, that means we need to deploy this debug image in every pod. Do you think this is the right approach. Somehow I am not convinced with this approach. I would better provide a mechanism to attach a sidecar debug container.

Is there any particular reason why we are using scratch as the base image instead of let's say alpine (which has minimal shell) ?

We talked before about changing the base image (#2116), and to be honest, I forgot to add it to my queue. I guess it's on yours now :-)
That said, for this specific issue here, users would need to deploy a different image anyway, as the process has to be started with dlv as the CMD.
Still about your first point: while I agree that people should be able to enter the container when they face an issue, I don't think it's unreasonable to ask them to deploy a debug image if problems can't be easily detected (#2452 comes to my mind). They can create a second deployment with this special image, and change the fronting service to direct part of the traffic to it: if there are 10 matching pods, one of them being from the debug deployment, then only 10% of the traffic will reach the debug image.

Thank you for answering my questions earlier. This PR is ready for review again. I have updated the PR with:

Merging two dockerfiles into one and using docker build command's --target option (https://docs.docker.com/develop/develop-images/multistage-build/#stop-at-a-specific-build-stage) to build two images.
Using alpine as the base image for docker images.

I have one followup question:
While trying out delve I found that delve suggest to compile with optimisations disabled for golang binaries (https://github.com/go-delve/delve/blob/master/Documentation/usage/dlv_exec.md) Would you suggest for jaeger components binaries used in debug images ?

I noticed @jpkrohling comment in the github issue about disabling optimizations, hence updated the PR accordingly.

Hi @jpkrohling
Thank you for giving detailed feedback earlier. I have updated the branch with the changes for second point in the review.

can we somehow have a base image for our components? Or a script that generates the Dockerfile? Most of it seems to be the same plumbing code, and maintaining is probably becoming harder.

Can I ask for a review again please. I will work on rest three feedbacks once we're convinced with the dockerfiles layout changes since those three will depend on it.

To recap, this PR is still missing:

[ ] apply the same to the all-in-one binary/container image
[ ] documentation

I am still working on the documentation part.

Hello @jpkrohling
I have raised a PR in documentation repo. I wasn't sure about what to document so most likely I am missing something. Thank you.

I'll do a final check next Monday, but looks good to me! If anyone else wants to try this out before that, it would be awesome.

Resolved the merge conflict due to another PR merge in Makefile.

Thanks for your contribution!


It was 40ms with my projects, a have added "~/.local/share/nvim/lazy/*", and it is 20ms more, anyway I don't see any delay visually. I have added a little optimization, now it's around 25ms for me


Handle git branches in the develop rake task

・Addresses the TODOs in lib/tasks/bullet_train_tasks.rake.
I added a TODO of my own → I'd like to hear your thoughts on removing origin/ or not when a developer wants to switch to a remote branch (line 134).

@gazayas Hey, there is a merge conflict here because I changed how we specify the git sources (and now use SSH URLs to do the clone). Do you mind fixing this up to account for that?


Decide about the testing approach for extensions that involve SSF code

Originally posted by @waiting-for-dev in https://github.com/solidusio/solidus_paypal_commerce_platform/pull/166#discussion_r1032533834
We need to decide which one of these options we do prefer:

Create a special, isolated dummy app and copy all the specs over, then run all the specs from that dummy app.
Do the above, but only for code that involves the storefront. All the rest of the specs (models, services, backend, API) will be tested in the extension engine, as we are doing in any other extension, and as we are used to do following the "Rails way".

After discussing this live we concluded that for now we're still spiking the solution and will keep things as they are for now.
We might revise the situation down the road, once we applied the same technique to other extensions, and before building tooling (e.g. in solidus_dev_support).
At that point we'll have more data points, making it a more informed decision, not excluding entirely different approaches that might emerge by then.
cc @waiting-for-dev @chrean @aldesantis for additional details and considerations that I might have missed from the conversation we had


Change Request Timeout

Hi,
Just wondering, how would you change the default request timeout on a per invocation basis?
Thanks

This library should provide setter for
https://github.com/kittinunf/Fuel/blob/master/fuel/src/main/kotlin/com/github/kittinunf/fuel/core/Request.kt#L28

Thanks for pointing that out. Let's do this for next release.

https://github.com/kittinunf/Fuel/commit/104358729adf77770a1da323ea850b281700a0da
Should fix this.

@yoavst do you have any ETA for next release with this fix? Thanks

I will push 0.71 tonight. Hang on tight.

Done! 0.71 is out.

Thank you!

Hi,
Given the current calling semantics, how would you use this in a typical kotlin get call?
Thanks

@jjdestef3
"http://httpbin.org/get".httpGet().timeout(5000).responseString { request, response, result ->
    ...
}

@jjdestef3  https://github.com/kittinunf/Fuel/commit/7a35b6b485a48462bb8db70e2db1e211bed4284e


CI for Node

#1 There is a bug.
CI for Node

use Node.js template to automate the process

>  7 |     expect(data).toMatchSnapshot()


How can i deploy fortune not at root path?

I want installed fortune at http://project.exmaple.com/api. but I find the link in the types are wrong.
try to modify http_html_serializer.js:51
var prefix = this.options.prefix || ''  to var prefix = this.options.prefix || '/api'
The link in the html are right, but the port from postman not working.
Thanks for giving any help!

Good find. This is a bug related to this file: https://github.com/fortunejs/fortune/blob/master/lib/net/http_initialize_context.js
The prefix needs to be removed from the url before trying to parse it internally.

Done https://github.com/fortunejs/fortune/commit/05ddfb90debd89a8a89712024a9ff186e149c2a3.


Refactor Probabilistic Forecast processing in metrics

[x] Partially addresses #426 PR and #425 and #266 (still need full support in reports)
[x] I am familiar with the contributing guidelines.
[x] Tests added.
[x] NOT APPLICABLE.  Updates entries to docs/source/api.rst for API changes.
[ ] Adds descriptions to appropriate "what's new" file in docs/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
[x] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
[ ] Maintainer: Appropriate GitHub Labels and Milestone are assigned to the Pull Request and linked Issue.

@wholmgren @alorenzo175 Should address the issues for ProbabilisticForecast and ProbabilisticForecastConstantValue for metrics preprocessing and metrics calculator. (Btw, I did find one small bug with the preprocessing related to CDF probabilistic forecasts ;) )
Which whatsnew should I update?
If this looks good let me know how you want coordinate on the reports.

Reports for ProbabilisticForecasts render with tables/plots for CRPS if template.render_html(with_timeseries=False). My preference is to expose that option in the relevant places (maybe just cli.report?) and address time series for ProbabilisticForecasts in a separate issue.

I haven't tested the reports at all since I thought we agreed to address that after the this PR on the call. Interesting that it only works if timeseries is ignored, agreed that only seems relevant as a rather odd user test and shouldn't be available normally to a user of the UI.

I did try running the report with the json file I created for probabilistic (1 ProbabilisticForecast, 3 ProbabilisticForecastConstantValue). But the forecasts I put that are in the dashboard don't seem to be available in the API. I can move this to another issue just thought I'd mention it before I forget. JSON attached

But the forecasts I put that are in the dashboard don't seem to be available in the API.

They must be if you're using the same API (dev vs prod) and username/password.

JSON attached nevermind github doesn't allow it

I find it helpful to bury these in <details> my long stuff </details>

Not in details:
{
    "report_parameters": {
        "name": "test",
        "start": "2019-09-25T00:00:00Z",
        "end": "2019-12-03T00:00:00Z",
        "filters": [
            {"quality_flags": [
                "USER FLAGGED",
                "NIGHTTIME",
                "CLEARSKY"
            ]}
        ],
        "metrics": [
            "bs"
        ],
        "categories": [
            "total"
        ],
        "object_pairs": [
            {
                "observation": "9dfe124a-7e49-11e9-98c3-0a580a8003e9",
                "forecast": "a1fc6490-080a-11ea-a9db-0a580a8003a5",
                "forecast_type": "probabilistic_forecast_constant_value"
            }
      ]
    }
  }

in details:

```
{
    "report_parameters": {
        "name": "test",
        "start": "2019-09-25T00:00:00Z",
        "end": "2019-12-03T00:00:00Z",
        "filters": [
            {"quality_flags": [
                "USER FLAGGED",
                "NIGHTTIME",
                "CLEARSKY"
            ]}
        ],
        "metrics": [
            "bs"
        ],
        "categories": [
            "total"
        ],
        "object_pairs": [
            {
                "observation": "9dfe124a-7e49-11e9-98c3-0a580a8003e9",
                "forecast": "a1fc6490-080a-11ea-a9db-0a580a8003a5",
                "forecast_type": "probabilistic_forecast_constant_value"
            }
      ]
    }
  }
```

I find it helpful to bury these in  my long stuff '

Nice use of html
Here is my probabilstic forecast json:

{
  "_comment": "This file is not currently used for tests, but can be used with the CLI tool to generate a real report when using data from the prod. API.",
  "report_parameters": {
    "name": "DOE RTC Albuquerque NM GHI Forecast Analysis",
    "start": "2020-04-01T00:00:00Z",
    "end": "2020-04-08T23:59:00Z",
    "filters": [
      {
        "quality_flags": [
          "USER FLAGGED",
          "NIGHTTIME",
          "LIMITS EXCEEDED",
          "STALE VALUES",
          "INTERPOLATED VALUES",
          "INCONSISTENT IRRADIANCE COMPONENTS"
        ]
      },
      {
        "time_of_day_range": [
          "10:00",
          "14:00"
        ]
      }
    ],
    "metrics": [
      "bs",
      "unc",
      "rel",
      "crps"
    ],
    "categories": [
      "total",
      "date",
      "hour"
    ],
    "report_id": " b63f73cf-865d-4c5a-9bba-bb1436c2802b",
    "object_pairs": [
      {
        "forecast": "26a6684c-080b-11ea-bab3-0a580a8200e0",
        "observation": "059f2be2-99fe-11e9-9161-0a580a8200c9"
      },
      {
        "forecast": "26a82ba8-080b-11ea-a36b-0a580a8200e0",
        "observation": "059f2be2-99fe-11e9-9161-0a580a8200c9"
      },
      {
        "forecast": "26a9e678-080b-11ea-8989-0a580a8200e0",
        "observation": "059f2be2-99fe-11e9-9161-0a580a8200c9"
      }
    ]
  }
}

@awig I think you'll now need to specify a forecast_type in each of your object_pairs (see mine for an example). I'm surprised and confused if it works without it.

@awig I think you'll now need to specify a forecast_type in each of your object_pairs (see mine for an example). I'm surprised and confused if it works without it.

Oh it hasn't worked in its entirety especially after the refactoring. Sorry for the confusion.
I'm a little confused now for this PR.  Please let me know what else should be done before it can be merged and we can start on the reports.

@awig, I think I finally figured it out. The issue is related to the Series name that gets passed into metrics from the API. So it's related to report workflow but it doesn't actually have anything to do with the reporting code. The io.api and io.utils helper functions take the json from the API and construct a DataFrame with a column 'values' in _json_to_dataframe, then slice out the values column into a Series in json_payload_to_forecast_series. When slicing, Pandas automagically sets the column name to be the Series.name.
The name propagates all the way down into _calculator._transform_prob_forecast_value_and_prob. Then, if isinstance(data, pd.Series): data = data.to_frame() ends up creating a DataFrame with the column name "values" instead of the column name equal to the constant value. Finally, the exception occurs when we try to call float(col) since col = "values" instead of something like col = '50.0'
Understandably your test code does not account for this so you didn't see it. But it all needs to work together and I think the right thing to do is to be careful about the to_frame call in calculator.py
I think https://github.com/awig/solarforecastarbiter-core/pull/1 solves it. I merged in master in the process, so the diff to your branch looks huge. I think just look the other way and merge it. Or reimplement my suggestions in your own branch if you'd prefer.
There is one more failing test that I see locally but let's address that once we're on the same page here.

I think the latest commit to https://github.com/awig/solarforecastarbiter-core/pull/1 solves the additional test failure. More implicit API wrapped up in the pandas objects.

Thanks @wholmgren
Glad you were able to fix it. Sorry for not foreseeing that issue.
I've merged in your (awig#1)[https://github.com/awig/solarforecastarbiter-core/pull/1] for the following files ONLY into my branch:

solarforecastarbiter/metrics/tests/test_calculator.py
solarforecastarbiter/metrics/calculator.py
solarforecastarbiter/conftest.py

I made no changes to them. @wholmgren Please confirm if this looks good for you.

@awig yes I think that gets all of my substantive changes. Optimistic that rebasing/merging upstream master will get this PR in mergeable place.

@awig can you rebase/merge master?

@awig can you rebase/merge master?

Done from SolarArbiter/master into awig/prob-refactor and fixed the whatsnew conflict

Fixed flake8 issues and made the other changes as well and remerged with SA/master.

Thanks @awig !


Sync etc and general rules with coreos/prometheus-operator

As per discussion in https://github.com/helm/charts/issues/8749, we need a way to sync rules with coreos/prometheus-operator (or kubernetes-mixin). After that we could have multiply rules files and will be able to disable them in case component scraping is disabled.
Discovering coreos repo I found out that etcd rules file is altered version from etcd repo, I've created https://github.com/etcd-io/etcd/pull/10244 to update bith yaml and libsonnet file with prometheus-operator version.
Etcd rules won't be changed in coreos/prometheus-operator and it's safe to manually update it now from etcd-io version, which I did in this PR along with moving it to separate file. Part of it's rules moved to general.rules section and I've updated it in this PR as well.
Also https://github.com/coreos/prometheus-operator/pull/2096 results merged to fix #9034.
In next PR I'll split all.rules.yaml into multiply files and will add python script to sync them with coreos/prometheus-operator or kubernetes-mixin. This is the first step I'd like to have done separately.

/assign @gianrubio
ping for review @vsliouniaev

Hello there, any ETA for this merge?

Thanks for doing this @paskal . I'm not sure it's a good idea to disable only the etcd rules when etcd is disabled because this creates an inconsistency in the behaviour until this change is applied with respect to all exporters.

I can disable etcd switch for consistency for now. @gianrubio, waiting for your verdict.

@vsliouniaev I've disabled the switch, updated rules from [etcd libsonnet]

/ok-to-test
/lgtm

/ok-to-test
/lgtm

Since this update the following alert is triggered constantly on my cluster:  EtcdHighNumberOfFailedHTTPRequests.
Additionally looking at the upstream etcd rules (https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/etcd3_alert.rules) I do not see references to FailedHTTPRequests anymore so  should shall I open a Issue to remove this from this chart?

I'll prepare PR with fix in the morning, my apologies.

Metrics which alert set up on described there: https://github.com/etcd-io/etcd/blob/master/Documentation/v2/metrics.md
Alerts are in progress of adding in https://github.com/etcd-io/etcd/pull/10244, particular this one is taken from coreos/prometheus-operator originally.
@dojadop, actually, what make you think it's not the real problem?

@paskal after looking at the metrics it looks like there is a constant 404 which causes the alert to trigger:

It might be related to this https://github.com/coreos/prometheus-operator/issues/1631#issuecomment-408087031 but not too sure

@dojadop, I'll exclude 404 from original repo and then will sync it up there.

@dojadop, actually it's hard to debug for me without having etcd. Would you be so kind to prepare expression which will exclude 404 errors from counting, test it and give it to me to be included in https://github.com/etcd-io/etcd/pull/10244?

@paskal you need to add code!="404" to the selector
sum by(method) (rate(etcd_http_failed_total{job=~".*etcd.*", code!="404"}[5m])) / sum by(method) (rate(etcd_http_received_total{job=~".*etcd.*"}[5m])) > 0.05

sum by(method) (rate(etcd_http_failed_total{job=~".*etcd.*", code!="404"}[5m])) / sum by(method) (rate(etcd_http_received_total{job=~".*etcd.*"}[5m])) > 0.01

Or if you want to ignore all 4xx error codes then you would use this:  code!~"4[0-9]{2}"

@dojadop https://github.com/helm/charts/pull/9516 sync this change to this very repo.


Add an AnyViewSequence which is analogous to the AnyView for ViewSequences

This allows for type-erased ViewSequences.
Original Motivation was to check whether this helps with reducing wasm binary size in xilem_html (which wasn't really that successful, static optimization + compression seems to work quite well at this point). But I think this could be helpful otherwise too, e.g. for recursive ViewSequences (see e.g. here) or cross-language bindings that need type erasure in sequences.

Keeping as draft, until there's a real reason for this (maybe recursive ViewSequences, but I'm not sure whether that is more of an artificial use-case)

I mentioned this in Zulip, but I also wanted to comment on the issue so it wouldn't get lost. I have a place where this could be useful. I have a branch where depending on a state variable, I want to return different ViewSequence types. A .boxed combinator would be quite useful:
if foo {
  (
    h1("Foo"),
    span("hello"),
  ).boxed()
} else {
  (
    h1("Bar"),
    div("goodbye"),
  ).boxed()
}

Yeah I see use-cases for this, and I think we should indeed land an updated version of this (also just to reflect a similar API for View <-> AnyView to ViewSequence <-> AnyViewSequence).
For your example you could use boxed for the second element to make it work though.
As a more general workaround for now for a changing number of sequences as mentioned by Daniel on zulip:
You could do either something like this:
let mut seq = Vec::new();
if foo {
    seq.push(h1("Foo").boxed());
    seq.push(span("hello").boxed());
    seq.push(p("baz").boxed());
} else {
    seq.push(h1("Bar").boxed());
    seq.push(div("goodbye").boxed());
}

Or alternatively something like:
if foo {
    (
        h1("Foo"),
        span("hello").boxed(),
        Some(p("baz")),
    )
} else {
    (
        h1("Bar"),
        div("goodbye").boxed(),
        None
    )
}

may work.
(The Option version should also work with the return type impl DomFragment/impl ViewSequence, while the Vec does not).


Server map does not show completely in mixed view page of new UI.

These two images are same data that show between old UI and new UI.As you can see,in old UI,the server map can show "Air Low Fare Search" and "Air Ancillaries Bundle Availability".But in new UI,it only shows the total count but does not show the detail info.
Could you tell me how to solve this problem? Thank you very much !

HI~ @messi-gao
You can see the ungrouped node by right-clicking on the server map and releasing the merge item.

HI~ @messi-gao
You can see the ungrouped node by right-clicking on the server map and releasing the merge item.

@denzelsN  Right-clicking on the server map only works in the home page,but does not work in other page.

home page works.

transactionList page does not work.

transactionView does not work.

@messi-gao
I forgot about transactionList and transactionView.
I'll fix it.
Thank you. :)

@messi-gao
I forgot about transactionList and transactionView.
I'll fix it.
Thank you. :)

@denzelsN If you fix it,please tell me. Thank you very mush.

@messi-gao
Fixed it.

@messi-gao
Fixed it.

My local code from the tag:1.8.3,I am trying to modify the three files you metion.But when complile the code,there are some complile error.Could you modify the code based on code of the tag:1.8.3?

@messi-gao
Change follow code in server-map-for-transaction-list-container.component.ts and server-map-for-transaction-view-container.component.ts:
But the context popup will open in a strange position.
// before
onContextClickBackground(coord: ICoordinate): void {
        this.dynamicPopupService.openPopup({
            data: this.mapData,
            coord,
            component: ServerMapContextPopupContainerComponent
        }, {
            resolver: this.componentFactoryResolver,
            injector: this.injector
        });
}
// after
onContextClickBackground(coord: ICoordinate): void {
        this.dynamicPopupService.openPopup({
            data: this.mapData,
            coord,
            component: ServerMapContextPopupContainerComponent
        });
}

@denzelsN
It is a pity that I can not find the code of onContextClickBackground as you metioned .The link is as below:
server-map-for-transaction-list-container.component.ts in tag:1.8.3
https://github.com/naver/pinpoint/blob/7294fb60a30b6e7a4b587068f7f03d29274f0339/web/src/main/webapp/v2/src/app/core/components/server-map/server-map-for-transaction-list-container.component.ts#L88
server-map-for-transaction-view-container.component.ts in tag:1.8.3
https://github.com/naver/pinpoint/blob/7294fb60a30b6e7a4b587068f7f03d29274f0339/web/src/main/webapp/v2/src/app/core/components/server-map/server-map-for-transaction-view-container.component.ts#L53

@messi-gao
Use updated code.

You may not understand my meannings,I will show the error to you.
After changing the three files,There are compile error in server-map-for-transaction-list-container.component.ts and server-map-for-transaction-view-container.component.ts.The erro code is this.dynamicPopupService.openPopup function,it needs only one parameter,but after you modify it,it needs two parameters.

complie error

dynamic-popup.service.ts openPopup function in tag:1.8.3.

@messi-gao
So, I comment about it.

Remove second parameter ( before --> after )
https://github.com/naver/pinpoint/issues/5565#issuecomment-490344802

@denzelsN You are right.I have saw it.As you say,The context popup will open in a strange position.I hope it could open in a normal position in Pinpoint next release.Thank you!


Wishlist not showing if removed all items from last page.

Issue Reference
#6609

@papnoisanjeev
This is working fine, please find the screenshot Here


Help with gamepad plugin

First of all thks for the library! It is really nice to have all those different human inputs handled by the same framework!
Altouhg, I must be doing something wrong when trying to use the gamepad plugin.
I downloaded the git files and added this to the head of my html:
<script src="extjs/humaninput-1.1.13-full.js"></script>
and them in the end of the body I added this to intialize the gamepad event check:
//initialize Human Input 	var settings = {addEvents: ['gamepad']};  	var HI = new HumanInput(window, settings);
Whenever I run this, the bellow message appears on my console.log every time that the gamepadUpdate() function is called on the loop:
Uncaught TypeError: Cannot read property 'length' of undefined
    at gamepadUpdate (humaninput-1.1.13-full.js:2831)

There is any problem with the gamepad plugin or am I doing something wrong?

More info about the problem.
When initialized the "this" inside the GamepadPlugin.prototype.gamepadUpdate function references to the GamepadPlugin object. However, after each subsequent gamepadUpdate() call, it references to the window object instead.
The problem is definitely on that but I lack the knowledge about your code to make any necessary change to fix it.
I would really like to use this library.
I hope anyone could chime on that.
Anyone has the gamepad HI feature working on last version?

You're right:  It's broken.  I think I've figured out what's going on (recent browser changes in regards to ES6 support).  I'll post a fix soon.

All fixed!  I just pushed a commit and a new version (1.1.15) that should resolve this issue.  Coincidentally I also noticed that when browsers detect axis as buttons HumanInput would think they're "down" and as a result you'd get unnecessary "hold" events.  I fixed that too while I was at it =)


Changelog and automatic GitHub releases

I'd suggest to use a CHANGELOG.md file with the format keep-a-changelog and then setting up:

Automatic check in a PR if the CHANGELOG was changed (unless a label is added);
Automatic GitHub release based on the version from the CHANGELOG file.

These are pretty simple workflows that do the trick: https://github.com/brunodrugowick/timeseries-poc/tree/main/.github/workflows

I've applied the suggested configurations and re ran the failed job. Looks like it worked.
Please let me know anything


Bump electron version to 25.9.6

This PR bumps the electron version to 25.9.6 and updates the ADS-sqlite version to 1.18.0 for our test suite.
*Need to follow up with the new distro hash

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 41.565%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
30790

Relevant Lines:
69376

💛  - Coveralls


doc: mention /var/snap/lxd/common/lxd for snap users

Signed-off-by: Simon Deziel<EMAIL_ADDRESS>

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"


Apply on Mobile

INSERT SHORT DESCRIPTION EXPLAINING THE HIGH-LEVEL REASON FOR THE NEW ISSUE HERE.
Current behavior
Apply Now button doesn't seem to work on mobile. Rather than just clicking the apply button you have to hold it down until it highlights and then double tap - a candidate wouldn't just guess that they'd have to do that. I'm concerned we're losing applications because of the process. Is there a way to make the button work better?
Expected behavior

Tap on Apply Now and have the application screen immediately pop up.

Steps to replicate behavior

Screenshots
Current
Expected

Hello,
This issue was fixed via one of the recent versions of the career portal via #133.
I suggest heading over to the releases page and downloading the most recent version of the career portal.

Hi,
We just downloaded the most recent version, but still have the same problem. Do you have any other suggestions on how to fix this? Thanks.

Can you shoot me a link to your portal so I can take a look?


How to add favicon?

Hi,
Please show me how to add a favicon to the pages.
Thanks so much.

https://github.com/barryclark/jekyll-now/pull/642
This still needs to be pulled/closed


Support launching an application from a CF manifest file

On kf push, search current directory for manifest.yml. Parse and forward args to the push cobra command.

support the flags: source/path, env
print out warnings for fields which are not yet supported

name will be included in this: as its a required field for the app manifest.
Also, app manifests can contain multiple apps. There's the push command might need to call kf.Push for each app in the manifest

Closed via #89


Update ApiClient.mustache

Jersey doesn't allow entities in DELETE method

PR checklist

[ ] Read the contribution guidelines.
[ ] Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
[ ] Run the following to build the project and update samples:./mvnw clean package
./bin/generate-samples.sh ./bin/configs/*.yaml
./bin/utils/export_docs_generators.sh

(For Windows users, please run the script in Git BASH)
Commit all changed files.
This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
These must match the expectations made by your contribution.
You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
[ ] File the PR against the correct branch: master (upcoming 7.6.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
[ ] If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

Jersey doesn't allow entities in method DELETE


ability to remove headers from the request

Hi, i think it is more feature-request.
I would like to remove some of the custom headers added by my load balancer to not expose their values to the registered services. In my configuration it would be enough to set value of this headers globally. I saw few tickets about "adding headers", so decided to add my usecase. If you think that it is something you would like to add - i can try to do a PR.

There has been quite a bit of discussion around header manipulation.
Most notably #110 and #168 which mention adding and removing headers.  I'm going to close this as a duplicate of #168 as I think that issue covers your use case.
Please feel free to on #168 with this use case.