Uptane docs

First, this will need a rebase. Update master on your branch so that it's up to date with uptane/uptane.github.io:master first, then do a rebase and force push.
Second, I have some git hygiene issues with this PR, that should be fairly easy to fix:

7a28d95  and 498fa59 should be squashed into one commit. This is just to keep the history clean; there's no need for the files you deleted to be added to the repo in the first place.
8236c3b should be split into two commits: first a commit to rename/move the files, and then a second commit with the various formatting changes you've applied. This helps reviewers actually see the changes you've made. With the rename and edits in the same commit, difftool isn't able to tell that you made edits to the moved files, so it shows up as though you added a bunch of brand new files.

Once that's done, this branch can serve as a basis for adding the build pipeline.

However, I'll note that the build is currently failing because of a bunch of broken links:
λ yarn build
yarn run v1.22.10
$ docusaurus build
[INFO] [en] Creating an optimized production build...

✔ Client

✔ Server
  Compiled successfully in 2.17s

● Client █████████████████████████ cache (99%) shutdown IdleFileCachePlugin
 stored

● Server █████████████████████████ cache (99%) shutdown IdleFileCachePlugin
 serialize pack

[ERROR] Unable to build website for locale en.
[ERROR] Error: Docusaurus found broken links!

Please check the pages of your site in the list below, and make sure you don't reference any path that does not exist.
Note: it's possible to ignore broken links with the 'onBrokenLinks' Docusaurus configuration, and let the build pass.

It looks like some of the broken links we found appear in many pages of your site.
Maybe those broken links appear on all pages through your site layout?
We recommend that you check your theme configuration for such links (particularly, theme navbar and footer).
Frequent broken links are linking to:
- /docs/intro

Exhaustive list of all broken links found:

- On source page path = /404.html:
   -> linking to /docs/intro

- On source page path = /blog:
   -> linking to /docs/intro

- On source page path = /blog/archive:
   -> linking to /docs/intro

- On source page path = /blog/blog Index 0:
   -> linking to /docs/intro

- On source page path = /markdown-page:
   -> linking to /docs/intro

- On source page path = /docs/:
   -> linking to /papers/Uptane_meeting_agenda_62323.pdf
   -> linking to /papers/uptane-standard.1.1.0.html
   -> linking to /papers/uptane-standard.1.2.0.html
   -> linking to /papers/uptane-standard.2.0.0.html
   -> linking to /uptane-standard/2.1.0/uptane-standard.html
   -> linking to /deployment-considerations/index.html
   -> linking to /docs/intro

- On source page path = /docs/adoptions:
   -> linking to /docs/intro

- On source page path = /docs/alliance:
   -> linking to /docs/intro

- On source page path = /docs/attacks:
   -> linking to /docs/intro

- On source page path = /docs/audio:
   -> linking to /papers/23uptane_331_mackay.pdf
   -> linking to /papers/23uptane_331_ms.pdf
   -> linking to /papers/22uptane_yokohama_december_7.pdf
   -> linking to /papers/22uptane_october_22_presentationmain.pdf
   -> linking to /papers/Lightman_ISO_24089.pdf
   -> linking to /papers/22uptane_russell_UNECEWP.29.pdf
   -> linking to /papers/Over-the-Air-Updates-PACCAR.pdf
   -> linking to /papers/IIW21_session1.pdf
   -> linking to /papers/IIW21_session2.pdf
   -> linking to /papers/IW20_lightning_update.pdf
   -> linking to /papers/IW20_aftermarket.pdf
   -> linking to /papers/IW20_emergency_updates.pdf
   -> linking to /papers/IW20_poufs.pdf
   -> linking to /docs/intro

- On source page path = /docs/audits:
   -> linking to /docs/intro

- On source page path = /docs/contact:
   -> linking to<EMAIL_ADDRESS>(resolved as<EMAIL_ADDRESS>   -> linking to /docs/intro

- On source page path = /docs/deployment/introduction:
   -> linking to /docs/intro

- On source page path = /docs/design:
   -> linking to /docs/intro

- On source page path = /docs/faq:
   -> linking to /docs/intro

- On source page path = /docs/governance:
   -> linking to /docs/intro

- On source page path = /docs/overview:
   -> linking to /docs/intro

- On source page path = /docs/participate:
   -> linking to /docs/intro

- On source page path = /docs/people:
   -> linking to /docs/intro

- On source page path = /docs/pouf:
   -> linking to /docs/intro

- On source page path = /docs/press:
   -> linking to /docs/intro

- On source page path = /docs/publications:
   -> linking to /docs/intro

- On source page path = /docs/reference_pouf:
   -> linking to /docs/intro

- On source page path = /docs/standardref:
   -> linking to papers/uptane-standard.2.1.0.html (resolved as: /docs/papers/uptane-standard.2.1.0.html)
   -> linking to /uptane-standard/2.1.0/uptane-standard.pdf
   -> linking to /deployment-considerations/changelog.html#210---2023-06-6 (resolved as: /deployment-considerations/changelog.html)
   -> linking to papers/uptane-standard.2.0.0.html (resolved as: /docs/papers/uptane-standard.2.0.0.html)
   -> linking to /deployment-considerations/changelog.html#200---2022-01-18 (resolved as: /deployment-considerations/changelog.html)
   -> linking to papers/uptane-standard.1.2.0.html (resolved as: /docs/papers/uptane-standard.1.2.0.html)
   -> linking to papers/uptane-standard.1.1.0.html (resolved as: /docs/papers/uptane-standard.1.1.0.html)
   -> linking to papers/uptane-standard.1.0.1.html (resolved as: /docs/papers/uptane-standard.1.0.1.html)
   -> linking to papers/uptane-standard.1.0.1.pdf (resolved as: /docs/papers/uptane-standard.1.0.1.pdf)
   -> linking to papers/ieee-isto-6<IP_ADDRESS>.uptane-standard.html (resolved as: /docs/papers/ieee-isto-6<IP_ADDRESS>.uptane-standard.html)
   -> linking to papers/V2.0.0_uptane_deploy.html (resolved as: /docs/papers/V2.0.0_uptane_deploy.html)
   -> linking to /docs/intro

- On source page path = /docs/timeline:
   -> linking to /docs/intro

- On source page path = /:
   -> linking to /docs/intro

    at throwError (/Users/jon/tdx/scratchpad/tkfu.github.io/node_modules/@docusaurus/logger/lib/index.js:76:11)
    at handleBrokenLinks (/Users/jon/tdx/scratchpad/tkfu.github.io/node_modules/@docusaurus/core/lib/server/brokenLinks.js:153:47)
    at async buildLocale (/Users/jon/tdx/scratchpad/tkfu.github.io/node_modules/@docusaurus/core/lib/commands/build.js:186:5)
    at async tryToBuildLocale (/Users/jon/tdx/scratchpad/tkfu.github.io/node_modules/@docusaurus/core/lib/commands/build.js:41:20)
    at async mapAsyncSequential (/Users/jon/tdx/scratchpad/tkfu.github.io/node_modules/@docusaurus/utils/lib/jsUtils.js:34:24)
    at async Command.build (/Users/jon/tdx/scratchpad/tkfu.github.io/node_modules/@docusaurus/core/lib/commands/build.js:76:21)
[INFO] Docusaurus version: 2.4.1
Node version: v18.12.0
error Command failed with exit code 1.

Once you've got the other issues with this branch sorted out, here's a workflow that can get you started. It only builds the site (no deployment), which is a good starting point. Once you've got passing builds, you can iterate and add a deployment step.
name: Build

on:
  push:
    branches: [ "master" ]
  pull_request:
    branches: [ "master" ]
  workflow_dispatch:

jobs:
  build:
    name: Build uptane website
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: 18
          cache: yarn

      - name: Install dependencies
        run: yarn install --frozen-lockfile
      - name: Build website
        run: yarn build

Oh, and get rid of package-lock.json, and create yarn.lock. yarn is the recommended build tool for docusaurus.

Thanks for the review, @tkfu! I will look into your suggestions and resolve them as soon as possible.

First, this will need a rebase. Update the master on your branch so that it's up to date with uptane/uptane.github.io:master first, then do a rebase and force push.

Hi @tkfu, I followed these steps for your first suggestion. I want you to cross-check it once in case I made any mistakes while updating the master on my branch and making sure it's up to date with uptane/uptane.github.io:master. Here's what I did:
First, I updated my local branch with uptane/uptane.github.io:master by fetching the latest changes from the upstream remote using this command:
git fetch upstream

Then, I checked out to my branch:
git checkout uptaneDocs

Next, I merged the changes from uptane/uptane.github.io:master into my local "uptaneDocs" branch:
git merge upstream/master

Now, my branch is up to date with uptane/uptane.github.io:master.
To perform the rebase, I used the following command:
git rebase uptaneDocs master

I received a message saying Successfully rebased and updated refs/heads/master, but I'm not entirely sure if I needed to use git rebase master instead of the command I used. When I tried that command, it resulted in many conflicts and errors. Could you please guide me on this? is git rebase uptaneDocs master the right command to use?
Also now I moved to step two which is squashing and splitting the commits

However, I'll note that the build is currently failing because of a bunch of broken links:
λ yarn build
yarn run v1.22.10
$ docusaurus build
[INFO] [en] Creating an optimized production build...

✔ Client

✔ Server
  Compiled successfully in 2.17s

● Client █████████████████████████ cache (99%) shutdown IdleFileCachePlugin
 stored

● Server █████████████████████████ cache (99%) shutdown IdleFileCachePlugin
 serialize pack

[ERROR] Unable to build website for locale en.
[ERROR] Error: Docusaurus found broken links!

Please check the pages of your site in the list below, and make sure you don't reference any path that does not exist.
Note: it's possible to ignore broken links with the 'onBrokenLinks' Docusaurus configuration, and let the build pass.

It looks like some of the broken links we found appear in many pages of your site.
Maybe those broken links appear on all pages through your site layout?
We recommend that you check your theme configuration for such links (particularly, theme navbar and footer).
Frequent broken links are linking to:
- /docs/intro

Exhaustive list of all broken links found:

- On source page path = /404.html:
   -> linking to /docs/intro

- On source page path = /blog:
   -> linking to /docs/intro

- On source page path = /blog/archive:
   -> linking to /docs/intro

- On source page path = /blog/blog Index 0:
   -> linking to /docs/intro

- On source page path = /markdown-page:
   -> linking to /docs/intro

- On source page path = /docs/:
   -> linking to /papers/Uptane_meeting_agenda_62323.pdf
   -> linking to /papers/uptane-standard.1.1.0.html
   -> linking to /papers/uptane-standard.1.2.0.html
   -> linking to /papers/uptane-standard.2.0.0.html
   -> linking to /uptane-standard/2.1.0/uptane-standard.html
   -> linking to /deployment-considerations/index.html
   -> linking to /docs/intro

- On source page path = /docs/adoptions:
   -> linking to /docs/intro

- On source page path = /docs/alliance:
   -> linking to /docs/intro

- On source page path = /docs/attacks:
   -> linking to /docs/intro

- On source page path = /docs/audio:
   -> linking to /papers/23uptane_331_mackay.pdf
   -> linking to /papers/23uptane_331_ms.pdf
   -> linking to /papers/22uptane_yokohama_december_7.pdf
   -> linking to /papers/22uptane_october_22_presentationmain.pdf
   -> linking to /papers/Lightman_ISO_24089.pdf
   -> linking to /papers/22uptane_russell_UNECEWP.29.pdf
   -> linking to /papers/Over-the-Air-Updates-PACCAR.pdf
   -> linking to /papers/IIW21_session1.pdf
   -> linking to /papers/IIW21_session2.pdf
   -> linking to /papers/IW20_lightning_update.pdf
   -> linking to /papers/IW20_aftermarket.pdf
   -> linking to /papers/IW20_emergency_updates.pdf
   -> linking to /papers/IW20_poufs.pdf
   -> linking to /docs/intro

- On source page path = /docs/audits:
   -> linking to /docs/intro

- On source page path = /docs/contact:
   -> linking to<EMAIL_ADDRESS>(resolved as<EMAIL_ADDRESS>   -> linking to /docs/intro

- On source page path = /docs/deployment/introduction:
   -> linking to /docs/intro

- On source page path = /docs/design:
   -> linking to /docs/intro

- On source page path = /docs/faq:
   -> linking to /docs/intro

- On source page path = /docs/governance:
   -> linking to /docs/intro

- On source page path = /docs/overview:
   -> linking to /docs/intro

- On source page path = /docs/participate:
   -> linking to /docs/intro

- On source page path = /docs/people:
   -> linking to /docs/intro

- On source page path = /docs/pouf:
   -> linking to /docs/intro

- On source page path = /docs/press:
   -> linking to /docs/intro

- On source page path = /docs/publications:
   -> linking to /docs/intro

- On source page path = /docs/reference_pouf:
   -> linking to /docs/intro

- On source page path = /docs/standardref:
   -> linking to papers/uptane-standard.2.1.0.html (resolved as: /docs/papers/uptane-standard.2.1.0.html)
   -> linking to /uptane-standard/2.1.0/uptane-standard.pdf
   -> linking to /deployment-considerations/changelog.html#210---2023-06-6 (resolved as: /deployment-considerations/changelog.html)
   -> linking to papers/uptane-standard.2.0.0.html (resolved as: /docs/papers/uptane-standard.2.0.0.html)
   -> linking to /deployment-considerations/changelog.html#200---2022-01-18 (resolved as: /deployment-considerations/changelog.html)
   -> linking to papers/uptane-standard.1.2.0.html (resolved as: /docs/papers/uptane-standard.1.2.0.html)
   -> linking to papers/uptane-standard.1.1.0.html (resolved as: /docs/papers/uptane-standard.1.1.0.html)
   -> linking to papers/uptane-standard.1.0.1.html (resolved as: /docs/papers/uptane-standard.1.0.1.html)
   -> linking to papers/uptane-standard.1.0.1.pdf (resolved as: /docs/papers/uptane-standard.1.0.1.pdf)
   -> linking to papers/ieee-isto-6<IP_ADDRESS>.uptane-standard.html (resolved as: /docs/papers/ieee-isto-6<IP_ADDRESS>.uptane-standard.html)
   -> linking to papers/V2.0.0_uptane_deploy.html (resolved as: /docs/papers/V2.0.0_uptane_deploy.html)
   -> linking to /docs/intro

- On source page path = /docs/timeline:
   -> linking to /docs/intro

- On source page path = /:
   -> linking to /docs/intro

    at throwError (/Users/jon/tdx/scratchpad/tkfu.github.io/node_modules/@docusaurus/logger/lib/index.js:76:11)
    at handleBrokenLinks (/Users/jon/tdx/scratchpad/tkfu.github.io/node_modules/@docusaurus/core/lib/server/brokenLinks.js:153:47)
    at async buildLocale (/Users/jon/tdx/scratchpad/tkfu.github.io/node_modules/@docusaurus/core/lib/commands/build.js:186:5)
    at async tryToBuildLocale (/Users/jon/tdx/scratchpad/tkfu.github.io/node_modules/@docusaurus/core/lib/commands/build.js:41:20)
    at async mapAsyncSequential (/Users/jon/tdx/scratchpad/tkfu.github.io/node_modules/@docusaurus/utils/lib/jsUtils.js:34:24)
    at async Command.build (/Users/jon/tdx/scratchpad/tkfu.github.io/node_modules/@docusaurus/core/lib/commands/build.js:76:21)
[INFO] Docusaurus version: 2.4.1
Node version: v18.12.0
error Command failed with exit code 1.

Hi @tkfu , I've managed to resolve some of the links, but I'm encountering an issue. It appears that most of the links mentioned in the broken build are not actually broken; they are pointing to the correct files, still while running yarn build it is showing that these links are broken. Can you suggest what I should do in this case?
[ERROR] Unable to build website for locale en.
[ERROR] Error: Docusaurus found broken links!

Please check the pages of your site in the list below, and make sure you don't reference any path that does not exist.
Note: it's possible to ignore broken links with the 'onBrokenLinks' Docusaurus configuration, and let the build pass.

Exhaustive list of all broken links found:

- On source page path = /docs/:
   -> linking to papers/uptane-standard.1.1.0.html (resolved as: /docs/papers/uptane-standard.1.1.0.html)
   -> linking to papers/uptane-standard.1.2.0.html (resolved as: /docs/papers/uptane-standard.1.2.0.html)
   -> linking to papers/uptane-standard.2.0.0.html (resolved as: /docs/papers/uptane-standard.2.0.0.html)
   -> linking to /uptane-standard/2.1.0/uptane-standard.html

- On source page path = /docs/contact:
   -> linking to<EMAIL_ADDRESS>(resolved as<EMAIL_ADDRESS>
- On source page path = /docs/standardref:
   -> linking to papers/uptane-standard.2.1.0.html (resolved as: /docs/papers/uptane-standard.2.1.0.html)
   -> linking to /uptane-standard/2.1.0/uptane-standard.pdf
   -> linking to /deployment-considerations/changelog.html#210---2023-06-6 (resolved as: /deployment-considerations/changelog.html)
   -> linking to papers/uptane-standard.2.0.0.html (resolved as: /docs/papers/uptane-standard.2.0.0.html)
   -> linking to /deployment-considerations/changelog.html#200---2022-01-18 (resolved as: /deployment-considerations/changelog.html)
   -> linking to papers/uptane-standard.1.2.0.html (resolved as: /docs/papers/uptane-standard.1.2.0.html)
   -> linking to papers/uptane-standard.1.1.0.html (resolved as: /docs/papers/uptane-standard.1.1.0.html)
   -> linking to papers/uptane-standard.1.0.1.html (resolved as: /docs/papers/uptane-standard.1.0.1.html)
   -> linking to papers/uptane-standard.1.0.1.pdf (resolved as: /docs/papers/uptane-standard.1.0.1.pdf)
   -> linking to /docs/papers/ieee-isto-6<IP_ADDRESS>.uptane-standard.html
   -> linking to papers/V2.0.0_uptane_deploy.html (resolved as: /docs/papers/V2.0.0_uptane_deploy.html)
   -> linking to /docs/papers/V2.0.0_uptane_deploy.html

Abhijay,  suggest cancelling this pull request and make a new one with the latest content. You have made many changes and updates since this pull request.

Abhijay, suggest cancelling this pull request and make a new one with the latest content. You have made many changes and updates since this pull request.

sure I added new branch here : https://github.com/Abhijay007/Abhijay007.github.io/tree/uptaneDemo


New release checklist BG standard: python -m build and twine check dist/*

Please use the latest release_checklist.md containing python -m build and twine check dist/* https://github.com/Billingegroup/cookiecutter/blob/main/{{ cookiecutter.repo_name }}/.github/ISSUE_TEMPLATE/release_checklist.md

@bobleesj Also can close this


Performance hit with Honer's algorithm

Consider this code to evaluate polynomials (and make pretty fractals):
import sys

import numpy as np
import matplotlib.pyplot as plt

import tqdm

accelerate = '--aot' in sys.argv

if accelerate:
    from extern import newton_step

else:
    def eval_poly(coeffs, x):
        # Taken from numpy.polynomial.polynomial._val
        c0 = coeffs[-1] + x*0
        for i in range(2, len(coeffs) + 1):
            c0 = coeffs[-i] + c0*x
        return c0

    def newton_step(z, poly_coeffs, der_coeffs):
        return z - eval_poly(poly_coeffs, z) / eval_poly(der_coeffs, z)

N = 1024
iter = 4

extent = 1.5
real = np.linspace(-extent, extent, N)
imag = np.linspace(-extent, extent, N)

xv, yv = np.meshgrid(real, imag)
z = xv + 1j * yv

roots = [1, np.exp(2j * np.pi / 3), np.exp(-2j * np.pi / 3)]

polynomial = np.polynomial.Polynomial.fromroots(roots)
deriv = polynomial.deriv()

poly_coeffs = polynomial.coef
der_coeffs = deriv.coef

for it in tqdm.trange(iter):
    z = newton_step(z, poly_coeffs, der_coeffs)

# -- This is just to make it pretty
frame = np.zeros((N, N, 3), dtype=np.float64)

for i, root in enumerate(roots):
    dist = np.abs(z - root)
    frame[:, :, i] = 1/(dist ** 2 + 1)

frame_norm = frame / np.linalg.norm(frame, axis=-1)[:, :, None]
plt.imshow(frame_norm)
plt.show()

with extern.py:
    c0 = coeffs[-1] + x*0
    for i in range(2, len(coeffs) + 1):
        c0 = coeffs[-i] + c0*x
    return c0

#pythran export newton_step(complex128[:, :], complex128[:], complex128[:])
def newton_step(z, poly_coeffs, der_coeffs):
    return z - eval_poly(poly_coeffs, z) / eval_poly(der_coeffs, z)

Running in pure Python mode, I get over 7 it/s, but with Pythran I get over 4 s/it. This is with both release and master, Python 3.11, on Fedora 40 (GCC 14.1.1).
I don't know what is going on, but this should be the kind of problems Pythran shines at.
Restricting ourselves to reals we get an even larger slow down, from 17 it/s in pure Python, down to 3.8 s/it with Pythran:
z = xv + yv

roots = [1, np.exp(2j * np.pi / 3), np.exp(-2j * np.pi / 3)]

polynomial = np.polynomial.Polynomial.fromroots(roots)
deriv = polynomial.deriv()

poly_coeffs = np.real(polynomial.coef).copy()
der_coeffs = np.real(deriv.coef).copy()

for it in tqdm.trange(iter):
    z = newton_step(z, poly_coeffs, der_coeffs)

and #pythran export newton_step(float64[:, :], float64[:], float64[:])

I can reproduce the issue. Investigating...

Can you confirm that passing -O2 to pythran fixes the issue? It looks like the python-config --cflags no longer includes any optimization flag o_O

https://github.com/serge-sans-paille/pythran/pull/2222 may do the trick. @Dapid I'll wait for your confirmation to merge.

It does work, now I have a 4.5x over pure Python, and a 6.5x on the real case.
Thanks!


Register Kima Chain

Can we skip all the extra images for now, and try to add them as they are registered as assets? (I see a lot of issues with then that will take a while to get through). I think it's best to only registered the kima asset for now.

Can we skip all the extra images for now, and try to add them as they are registered as assets? (I see a lot of issues with then that will take a while to get through). I think it's best to only registered the kima asset for now.

removed

Hey @JeremyParish69 please could you take a look at our updated PR where we fixed our fees: https://github.com/cosmos/chain-registry/pull/5293/files


Updating .travis.yml to use<EMAIL_ADDRESS>

phantomjs is still not happy

@edewit yeah, have a feeling a dev-dep changed, will keep digging

@wei-lee

:+1:

There was a devDependency sub-dep that had been unpublished in the browserify module. Bumping it fixed things - have also made a few small changes to the .travis.yml config


How to use inside Rails engine?

It is possible to use this gem inside another rails engine gem as a dependency? Simply adding it as a dependency inside the gemspec file does not work. But adding it to the main rails gemfile works.
Thanks.

This issue is not relevant to this lib and should be closed.
With Rails engines I recommend to put all dependencies in the root Gemfile. I18n is NOT scoped to engines, it is loaded globally.

I don't know much about engines, so I don't have an opinion, but nothing here seems actionable.


Release

TODO:

[x] Merge https://github.com/nitrictech/cli/pull/265

Codecov Report

Merging #266 (25cd91c) into main (639836b) will decrease coverage by 2.78%.
The diff coverage is 15.24%.

@@            Coverage Diff             @@
##             main     #266      +/-   ##
==========================================
- Coverage   35.94%   33.15%   -2.79%
==========================================
  Files          48       49       +1
  Lines        4215     4636     +421
==========================================
+ Hits         1515     1537      +22
- Misses       2557     2947     +390
- Partials      143      152       +9

Flag
Coverage Δ

unittests
33.15% <15.24%> (-2.79%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/codeconfig/function.go
0.00% <0.00%> (ø)

pkg/codeconfig/server.go
0.00% <0.00%> (ø)

pkg/project/config.go
0.00% <0.00%> (ø)

pkg/provider/pulumi/aws/aws.go
60.99% <0.00%> (-1.03%)
:arrow_down:

pkg/provider/pulumi/aws/gateway.go
0.00% <0.00%> (ø)

pkg/provider/pulumi/azure/apimanagement.go
0.00% <0.00%> (ø)

pkg/provider/pulumi/azure/azure.go
6.46% <0.00%> (-0.72%)
:arrow_down:

pkg/provider/pulumi/azure/containerapp.go
0.00% <0.00%> (ø)

pkg/provider/pulumi/azure/serviceprinciple.go
0.00% <0.00%> (ø)

pkg/provider/pulumi/azure/subscriptions.go
0.00% <0.00%> (ø)

... and 21 more

Continue to review full report at Codecov.

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


chore: pr auto label

Summary by CodeRabbit

New Features

Introduced an automated labeling system for pull requests, enhancing organization and project management.
Added a workflow to streamline the application of labels based on predefined rules.

Bug Fixes

Improved accuracy of labeling by defining specific categories for changes and breaking modifications.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 34.24%. Comparing base (fbbc1c7) to head (a29339f).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #243   +/-   ##
=======================================
  Coverage   34.24%   34.24%
=======================================
  Files          81       81
  Lines        7164     7164
=======================================
  Hits         2453     2453
  Misses       4711     4711

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


Configured pydocstyle for the trainer, callbacks, loggers, optimizers, and utils.

This PR enables the pydocstyle pre-commit hook for most of the codebase. Docstrings were brought up to compliance so they would pass the pydocstyle check.

The main changes involved ensuring summary docstring lines were indeed just one line, that they ended with periods, and that there were no blank lines between the end of the docstring and the start of the function.
Added docstrings for missing arguments that were identified.
(Coming along for the ride): Remove calls to trainer.engine.close, as now close() is invoked automatically in __del__ as part of #948

Model, dataset, and algorithm docstrings will be addressed in future PRs.

This PR is obv very large and mostly contains routine docstring edits. I won't look at each one; I will trust that pydoctest does what it claims to do. Any diffs that do other things that we should take special look at in this PR? Like the pre-commit config or anything else?

This PR is obv very large and mostly contains routine docstring edits. I won't look at each one; I will trust that pydoctest does what it claims to do. Any diffs that do other things that we should take special look at in this PR? Like the pre-commit config or anything else?

I know it's a bunch of files, but it would be super helpful if you could double check that there aren't any unintentional changes from a sloppy merge that I might have done (e.g. remove new functionality). Let me update it against the latest dev.


Friendly reminder to update main Docs page

This is  a reminder.

Prerequisites

[x ] Are you running the latest version?
[x ] Are you reporting to the correct repository?
(enso is made of many specialized packages: https://github.com/laravel-enso)
[ x] Did you check the documentation?
[x ] Did you perform a cursory search?

Description
The "try it up" description is outdated. The steps are incomplete and do not lead to an up-and-running app in 5 minutes
Steps to Reproduce

First Step
Second Step
and so on...

Expected behavior
A working app. Possibly in 5 minutes.
Actual behavior
running "yarn" leads to "package.json" not found.
running "php artisan migrate" leads to access error because no database present.
database is not seeded, so no user present.

Hi @wbovela
Thanks for the reminder, the page was updated


Use bfloat16 for eval

I'm running paxml on an Intel Xeon CPU server using the paxml/main.py program. I'm trying to create a model that creates weights in bfloat16, and uses that datatype during eval. I modified the LmCloudSpmd2B configuration with the following lines:
MODEL_DTYPE = jnp.bfloat16
ICI_MESH_SHAPE = [1, 1, 1]

The training status output includes the following output.
model.dtype : type/jax.numpy/float32
model.fprop_dtype : dtype[bfloat16]

All of the other operator datatypes are float32. When I run that model with the --eval switch all of the computation is in float32. How can I direct paxml to use bfloat16?
Tom

Any comments on this?


fix(security-insights): set filtered table data on initial load

This PR updated this component to filter to open on initial load. However, on initial load only tableData was being set previously.
Fixes: https://github.com/RoadieHQ/roadie-backstage-plugins/issues/1492
There is a check in the JSX to render filteredTableData if insightsStatusFilter is set. Since insightsStatusFilter is set with the default state value now (const [insightsStatusFilter, setInsightsStatusFilter] = useState<SecurityInsightFilterState>('open');), this was rendering filteredTableData on the first render which was null. Clicking on Open would display data but may give uses a false sense of security that they have no security insights with a quick glance at the tab.
:heavy_check_mark: Checklist

[ ] Added tests for new functionality and regression tests for bug fixes

there are no existing tests for this component

[x] Added changeset (run yarn changeset in the root)
[ ] Screenshots of before and after attached (for UI changes)

Tested this on one of our components that has security insights but don't really want to post screenshots because security

[ ] Added or updated documentation (if applicable)

N/A - bug fix

This PR is not stale. @punkle could I get some assistance on a review for this one?

Still looking for some review on this one.


remove my deadname

Today I saw one of the tutorials on the netcup Twitter and I saw that the tutorials I wrote still include my deadname, because of this it would be nice if that gets changed

Certainly, I have just approved your request and looked through all remaining tutorials, ensuring that the name has been changed. Thank you very much for participating in the community and do not hesitate to contact us for any changes.

Thanks! But, will the name on https://community.netcup.com/en/tutorials be automatically updated?

I have informed the responsible department to trigger a rebuild of the website as soon as possible. Once that has been done, the name change will be applied side wide.


[SPARK-42532][K8S][DOCS] Update YuniKorn documentation with v1.2

What changes were proposed in this pull request?
This PR aims to update YuniKorn documentation with the latest v1.2.0 and fix codify issues in doc.
Why are the changes needed?

https://yunikorn.apache.org/release-announce/1.2.0

Does this PR introduce any user-facing change?
This is a documentation-only change.
BEFORE

https://dist.apache.org/repos/dist/dev/spark/v3.4.0-rc1-docs/_site/running-on-kubernetes.html#using-apache-yunikorn-as-customized-scheduler-for-spark-on-kubernetes

AFTER

How was this patch tested?
Manually test.
$ build/sbt -Psparkr -Pkubernetes -Pkubernetes-integration-tests -Dspark.kubernetes.test.deployMode=docker-desktop "kubernetes-integration-tests/test" -Dtest.exclude.tags=minikube,local,decom -Dtest.default.exclude.tags=''
[info] KubernetesSuite:
[info] - SPARK-42190: Run SparkPi with local[*] (10 seconds, 832 milliseconds)
[info] - Run SparkPi with no resources (12 seconds, 421 milliseconds)
[info] - Run SparkPi with no resources & statefulset allocation (17 seconds, 861 milliseconds)
[info] - Run SparkPi with a very long application name. (12 seconds, 531 milliseconds)
[info] - Use SparkLauncher.NO_RESOURCE (17 seconds, 697 milliseconds)
[info] - Run SparkPi with a master URL without a scheme. (12 seconds, 499 milliseconds)
[info] - Run SparkPi with an argument. (18 seconds, 734 milliseconds)
[info] - Run SparkPi with custom labels, annotations, and environment variables. (12 seconds, 520 milliseconds)
[info] - All pods have the same service account by default (17 seconds, 504 milliseconds)
[info] - Run extraJVMOptions check on driver (9 seconds, 402 milliseconds)
[info] - SPARK-42474: Run extraJVMOptions JVM GC option check - G1GC (9 seconds, 389 milliseconds)
[info] - SPARK-42474: Run extraJVMOptions JVM GC option check - Other GC (9 seconds, 330 milliseconds)
[info] - Verify logging configuration is picked from the provided SPARK_CONF_DIR/log4j2.properties (17 seconds, 710 milliseconds)
[info] - Run SparkPi with env and mount secrets. (19 seconds, 797 milliseconds)
[info] - Run PySpark on simple pi.py example (18 seconds, 568 milliseconds)
[info] - Run PySpark to test a pyfiles example (15 seconds, 622 milliseconds)
[info] - Run PySpark with memory customization (18 seconds, 507 milliseconds)
[info] - Run in client mode. (6 seconds, 185 milliseconds)
[info] - Start pod creation from template (17 seconds, 696 milliseconds)
[info] - SPARK-38398: Schedule pod creation from template (12 seconds, 585 milliseconds)
[info] - Run SparkR on simple dataframe.R example (19 seconds, 639 milliseconds)
[info] YuniKornSuite:
[info] - SPARK-42190: Run SparkPi with local[*] (12 seconds, 421 milliseconds)
[info] - Run SparkPi with no resources (20 seconds, 465 milliseconds)
[info] - Run SparkPi with no resources & statefulset allocation (15 seconds, 516 milliseconds)
[info] - Run SparkPi with a very long application name. (20 seconds, 532 milliseconds)
[info] - Use SparkLauncher.NO_RESOURCE (15 seconds, 545 milliseconds)
[info] - Run SparkPi with a master URL without a scheme. (20 seconds, 575 milliseconds)
[info] - Run SparkPi with an argument. (16 seconds, 462 milliseconds)
[info] - Run SparkPi with custom labels, annotations, and environment variables. (20 seconds, 568 milliseconds)
[info] - All pods have the same service account by default (15 seconds, 630 milliseconds)
[info] - Run extraJVMOptions check on driver (12 seconds, 483 milliseconds)
[info] - SPARK-42474: Run extraJVMOptions JVM GC option check - G1GC (12 seconds, 665 milliseconds)
[info] - SPARK-42474: Run extraJVMOptions JVM GC option check - Other GC (11 seconds, 615 milliseconds)
[info] - Verify logging configuration is picked from the provided SPARK_CONF_DIR/log4j2.properties (20 seconds, 810 milliseconds)
[info] - Run SparkPi with env and mount secrets. (24 seconds, 622 milliseconds)
[info] - Run PySpark on simple pi.py example (16 seconds, 650 milliseconds)
[info] - Run PySpark to test a pyfiles example (23 seconds, 662 milliseconds)
[info] - Run PySpark with memory customization (15 seconds, 450 milliseconds)
[info] - Run in client mode. (5 seconds, 121 milliseconds)
[info] - Start pod creation from template (20 seconds, 552 milliseconds)
[info] - SPARK-38398: Schedule pod creation from template (15 seconds, 847 milliseconds)
[info] - Run SparkR on simple dataframe.R example (22 seconds, 739 milliseconds)
[info] Run completed in 15 minutes, 41 seconds.
[info] Total number of tests run: 42
[info] Suites: completed 2, aborted 0
[info] Tests: succeeded 42, failed 0, canceled 0, ignored 0, pending 0
[info] All tests passed.
[success] Total time: 1306 s (21:46), completed Feb 22, 2023, 2:28:18 PM

Could you review this too, @viirya ? I fixed some K8s documentation issues while reviewing and testing 3.4.0 RC1 and updated YuniKorn documentation with the latest information.

Looks good to me.

Thank you so much, @viirya . Merged to master/3.4.


Tweak rules for traps in CLIF translation

This commit updates how the signals_based_traps setting is read for
various instruction generation during the wasm-to-CLIF translation
phase. Specifically this splits the signals_based_traps configuration
into one for "general CLIF instructions can trap" and another for
"memory traps are allowed". These settings are based on
signals_based_traps but then differ for Pulley. For example Pulley
allows general instructions to trap since that just halts the
interpreter, but memory-related instructions can't trap since segfaults
aren't caught during the execution of Pulley. These settings then take
Pulley into account to assist in translating Pulley compatibly by
default.

I'll note that this is temporarily based on https://github.com/bytecodealliance/wasmtime/pull/9736, so only the second commit is part of this PR


continuous update rejects could flood envoy with discovery requests

If for a particular reason, an update is rejected, Envoy sends back a response immediately indicating the failure to management server. However if management server, responds again with incorrect data with possibility of update being rejected, Envoy would send the update rejected response immediately.
This continuous flow of rejections can be quite chatty and could flood envoy with discovery requests.
It is better to implement back-off for update rejected cases with back-off starting immediately after the first failure.

Arguably the management server should implement back-off here @ramaraochavali.

@htuch I was also thinking that management server should implement the back-off here. However following (especially the first one) was the motivation for the issue and the PR.

Should Envoy protect itself from a management server misbehaviour possibly because of a bug in it's implementation or some other conditions?
Would it be useful for all management servers if Envoy implements this instead of every one doing it?
I am Ok if we say it is a conscious design choice that management server should take care of this.

Another point to consider here request back-off vs. response back-off which one is better as a design choice? I tried both with this PR in envoy and implementing it in our management server on the response side - request side looked more natural to me, but it's just me.
LMK what you think?

@htuch jumping in from the left field here. ~I vaguely remember someone bringing up a similar line of conversation a few months ago. I think we discussed "ratelimiting" discovery interactions back then.~ Found the discussion in #2169 (if you are interested, @ramaraochavali).

Yeah, I think we can do back-off in Envoy, we just need to make sure it doesn't affect normal rapid successful updates. I still think Envoy doesn't need to protect itself as the management server is essentially trusted (a broken management server can do a lot more bad things than cause Envoy to spin..). But, if you want to add this, seems legit.


Some changes to the x11 backend

The first commit is a refactoring with (I think) obviously no change in behaviour.
The second commit has a harmless, internal-only behaviour change that should not make any difference.
The last two commits in this deal with resizing. They can be tested by starting rootston with the X11 backend, (making it floating if on a tiling WM,) and resizing it with the mouse a lot.

Thanks!


added iterative example

Adds an Iterative example in the enums section.

Can you just add some context above the example and say that we demonstrate two different ways, using a) recursive functions and b) loops?
Thank you for this contribution!

Makes sense.
Thanks for mentioning, updated accordingly


Kth largest Element in array.

This can be done in klog(n) using Heap sort.
where K is the kth largest element in array .
Create a Max Heap and iterate till k largest Element.

Thank you!
Will add another algorithm to perform Kth largest number search using a Max Heap.
And you are always welcome to contribute and just follow the guidelines.

Added new function in kthLargest.go named KthLargestUsingHeap(). See this a3479f7 for more info.


Fix coverage

Workspace coverage with cargo-make doesn't seem to build the full coverage for all workspace members and include it for Codecov. It should, so we should fix this!

Coverage is fixed using kcov, with reports being sent to CodeCov.


[Doc]: Add hacktoberfest logo in the documentation

Describe the bug

[ ] Information addition regarding the newest change through a PR.
[ ] Typo error.
[ ] New category addition.
[ ] Refractoring sentences that make more sense.
[ ] Fixing broken links.
[ ] Refractors / reformating of the document.

Please assign. I've done frontend contributions before.


integration-cli: fix test name typo

ocd, couldn't wait more..
Signed-off-by: Antonio Murdaca<EMAIL_ADDRESS>

+kind/ocd :angel: :sweat_smile:
LGTM 🐷

:-)
LGTM

+kind/ocd :angel: :sweat_smile:

:joy: haha


Automated cherry pick of #9958: fix(cloudid): add en-US html templte

Cherry pick of #9958 on release/3.7.
#9958: fix(cloudid): add en-US html templte

Codecov Report

Merging #9959 (49c90a3) into release/3.7 (0ff3997) will increase coverage by 5.98%.
The diff coverage is 9.16%.

@@               Coverage Diff                @@
##           release/3.7    #9959       +/-   ##
================================================
+ Coverage         5.98%   11.96%    +5.98%
================================================
  Files              848      231      -617
  Lines           131795    25831   -105964
================================================
- Hits              7887     3091     -4796
+ Misses          123206    22429   -100777
+ Partials           702      311      -391

Flag
Coverage Δ

aFlag
11.96% <9.16%> (+5.98%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/apigateway/handler/auth.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/auth_totp.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/idp.go
1.84% <0.00%> (ø)

pkg/apigateway/handler/misc.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/resource.go
0.00% <0.00%> (ø)

pkg/compute/guestdrivers/managedvirtual.go
0.00% <0.00%> (ø)

pkg/hostman/diskutils/nbd/driver.go
0.74% <0.00%> (-0.01%)
:arrow_down:

pkg/hostman/diskutils/nbd/lvmutils.go
4.70% <0.00%> (-0.24%)
:arrow_down:

pkg/monitor/alerting/conditions/mathreducer.go
0.00% <0.00%> (ø)

pkg/monitor/alerting/conditions/nodataquery.go
0.64% <0.00%> (-0.10%)
:arrow_down:

... and 585 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #9959 (49c90a3) into release/3.7 (0ff3997) will increase coverage by 5.98%.
The diff coverage is 9.16%.

@@               Coverage Diff                @@
##           release/3.7    #9959       +/-   ##
================================================
+ Coverage         5.98%   11.96%    +5.98%
================================================
  Files              848      231      -617
  Lines           131795    25831   -105964
================================================
- Hits              7887     3091     -4796
+ Misses          123206    22429   -100777
+ Partials           702      311      -391

Flag
Coverage Δ

aFlag
11.96% <9.16%> (+5.98%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/apigateway/handler/auth.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/auth_totp.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/idp.go
1.84% <0.00%> (ø)

pkg/apigateway/handler/misc.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/resource.go
0.00% <0.00%> (ø)

pkg/compute/guestdrivers/managedvirtual.go
0.00% <0.00%> (ø)

pkg/hostman/diskutils/nbd/driver.go
0.74% <0.00%> (-0.01%)
:arrow_down:

pkg/hostman/diskutils/nbd/lvmutils.go
4.70% <0.00%> (-0.24%)
:arrow_down:

pkg/monitor/alerting/conditions/mathreducer.go
0.00% <0.00%> (ø)

pkg/monitor/alerting/conditions/nodataquery.go
0.64% <0.00%> (-0.10%)
:arrow_down:

... and 585 more

Continue to review full report at Codecov.

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


Support of Conan

Many people are using Gitlab to build and deploy their code. Gitlab Ultimate will support dependency scanning of C and C++ files that use Conan  to analyse dependencies and to create SBOMs, an important topic in the industry nowadays.
See https://docs.gitlab.com/ee/user/application_security/dependency_scanning/index.html#supported-languages-and-package-managers for the explanation.
Is there any plan to support Conan in the future?
Thanks

@jankap could you please confirm that you are referring to the scanning of the source code the tools are build from and not the scanning of the source code that the tools are processing?

I'm afraid I don't get the point, could you elaborate please?

@jankap what is your use-case of Conen in context of the CMSIS-Toolbox?
Do you want to use Conen as Artifactor or the CMSIS-Toolbox binaries so that they can be installed or is it something different?

We would like to use the security scanning mechanism of Gitlab. It seems like only Conan is currently supported. Conan creates lockfiles, similar to Pythons pip requirements.txt. Basically, it contains the name, link/path and version of dependent packages, required by the project to be build. CMSIS-toolbox does similar things, it creates a list of dependencies based on CMSIS-Packs. Maybe there's a way to export that list to a conan compatible format to get it scanned for vulnerabilities. I don't think that the code is scanned, but a list of known vulnerabilities is used for comparison.

Would it be possible to used the information in the Cbuild.yml files as starting point?  These describe all the files that are used in the build process.

closing as no further activities.  @jankap let us know if you need additional information.


Update targeted-content.md

Remove bold from introduction

Raised this to demo the editing workflow in a working group session.


How to avoid delegating member functions for guards

Hi,
I read https://github.com/boost-experimental/sml/issues/93 and want add a guard to this example.
#include <iostream>
#include <boost/sml.hpp>

namespace sml = boost::sml;

struct ev1 {};
struct with_prop;

struct table {
    auto operator()() const noexcept {
        using namespace sml;
        return make_transition_table(
            *"s1"_s  + event<ev1>
            [([](with_prop& p) {
            [](auto& p) -> bool {
                std::cout << "on_entry:guard" << std::endl;
                return p.guard();
            }(p);
            })]
            /
            [](with_prop& p) {
                [](auto& p) -> void {
                    std::cout << "on_entry:action" << std::endl;
                    p.method1();
                }(p);
            }
        );
    }
};
struct with_prop {
    with_prop() : sm(*this) {}

    template <typename Event>
    void process_event(Event&& ev) {
        sm.process_event(std::forward<Event>(ev));
    }

    void method1() {
        std::cout << "method1" << std::endl;
    }
    void method2() {
        std::cout << "method2" << std::endl;
    }

    bool guard() {
       std::cout << "guard" << std::endl;
       return true;
    }

private:
    sml::sm<table> sm;
};

int main() {
    with_prop wp;
    std::cout << "> Send Event1" << std::endl;
    wp.process_event(ev1());
    wp.method2();
}

Error:
use of 'static auto boost::sml::v1_1_0::front::call<TEvent, boost::sml::v1_1_0::aux::type_list<TArgs ...>, boost::sml::v1_1_0::back::no_policy>::execute(T, const TEvent&, TSM&, TDeps&, TSubs&) [with T = boost::sml::v1_1_0::aux::zero_wrapper<table::operator()() const::<lambda(with_prop&)>, void>; TSM = boost::sml::v1_1_0::back::sm_impl<boost::sml::v1_1_0::back::sm_policy<table> >; TDeps = boost::sml::v1_1_0::aux::pool<with_prop&>; TSubs = boost::sml::v1_1_0::aux::pool<boost::sml::v1_1_0::back::sm_impl<boost::sml::v1_1_0::back::sm_policy<table> > >; TEvent = ev1; Ts = {with_prop&}]' before deduction of 'auto'
Is there any good way to use the guards with delegating member functions? How can I avoid this error?
Thanks for the help!

@Zlatan1988 , this is not a solution of your question but it might be useful.
Why do you want to use with_prop? In my case #93, I want to call process_event in action handlers.
If your reason is the same, you don't need to use dependency mechanism such as with_prop.
See https://github.com/boost-experimental/sml/issues/94#issuecomment-310989485.
https://wandbox.org/permlink/5JiWphg7w78VizbK
Be careful about #96 and #113. sml still have some unexpected action order.

@Zlatan1988 , I found the solution for you question.
See https://wandbox.org/permlink/eZ813UwG0YQsgK4Q
It's function object approach.
See https://github.com/boost-experimental/sml/issues/93#issuecomment-283629397
I'm not sure the instantiation timing of nested lambda expression.
My #93 nested lambda code works on g++ 7.2.0
https://wandbox.org/permlink/LFjJfz2W4ayWs690
but got compile error on clang++
https://wandbox.org/permlink/LFjJfz2W4ayWs690
Perhaps the instantiation is implementation defined.

but got compile error on clang++
https://wandbox.org/permlink/omCLBzjZuLeWcuQl
Perhaps the instantiation is implementation defined.

When I set -std=c++14, it successfully compiled.
https://wandbox.org/permlink/labBCx2XZXD22fhY
And back to your original question, you just need to insert return statement to the inner lambda expression:
Before
            [](auto& p) -> bool {

After
            return [](auto& p) -> bool {

        return make_transition_table(
            *"s1"_s  + event<ev1>
            [([](with_prop& p) {
            return [](auto& p) -> bool {
                std::cout << "on_entry:guard" << std::endl;
                return p.guard();
            }(p);
            })]
            /
            [](with_prop& p) {
                [](auto& p) -> void {
                    std::cout << "on_entry:action" << std::endl;
                    p.method1();
                }(p);
            }
        );

gcc 7.2.0
https://wandbox.org/permlink/ZjJ60m0g3IFCuuhk
and clang 5.0.0
https://wandbox.org/permlink/hc6mtlAIgpnncqaJ
both successfully compiled.

@redboltz Thank you very much!
I'm new to lambda expression and your solution helped me a lot :-)


Enable multi-signature on sendTransaction

When sendTransaction, the connector infers the transaction owner by looking up resource inputs and returns the first one it finds. It could be an issue when the TX has inputs form different owners, making it differ from a wrong owner to the tx.
This is a use case more complex and not-so-common use case but should be handled in the future.

This was updated to use an address informed by on the TX payload.


Default warehouse ignored

Describe the bug
Seems that the passed default Warehouse parameter gets ignored.
snowflake.connector.errors.ProgrammingError: 000606 (57P03): No active warehouse selected in the current session.  Select an active warehouse with the 'use warehouse' command.
The DEPLOY_WH exists in the account.
To Reproduce
Using default role DEPLOY_ROLE
Using default warehouse DEPLOY_WH
Using default database DEMO_DBschema None
Traceback (most recent call last):
File "/opt/hostedtoolcache/Python/3.8.18/x64/bin/schemachange", line 8, in
sys.exit(main())
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/schemachange/cli.py", line 896, in main
deploy_command(config)
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/schemachange/cli.py", line 506, in deploy_command
change_history_metadata = session.fetch_change_history_metadata(change_history_table)
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/schemachange/cli.py", line 372, in fetch_change_history_metadata
results = self.execute_snowflake_query(query)
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/schemachange/cli.py", line 367, in execute_snowflake_query
raise e
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/schemachange/cli.py", line 360, in execute_snowflake_query
res = self.con.execute_string(query)
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/snowflake/connector/connection.py", line 833, in execute_string
ret = list(stream_generator)
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/snowflake/connector/connection.py", line 851, in execute_stream
cur.execute(sql, _is_put_get=is_put_or_get, **kwargs)
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/snowflake/connector/cursor.py", line 1136, in execute
Error.errorhandler_wrapper(self.connection, self, error_class, errvalue)
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/snowflake/connector/errors.py", line 290, in errorhandler_wrapper
handed_over = Error.hand_to_other_handler(
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/snowflake/connector/errors.py", line 345, in hand_to_other_handler
cursor.errorhandler(connection, cursor, error_class, error_value)
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/snowflake/connector/errors.py", line 221, in default_errorhandler
raise error_class(
snowflake.connector.errors.ProgrammingError: 000606 (57P03): No active warehouse selected in the current session.  Select an active warehouse with the 'use warehouse' command.
Expected behavior
I should not need to specify Warehouse inside the script

This is the same behavior for the ticket I entered: https://github.com/Snowflake-Labs/schemachange/issues/224


divop directory should be renamed divergence, and also include the compute_diveu functionality

Keep in mind that PeleLM reimplements calc_divu, for example, as it does a bunch of other functions.  This is one of the fundamental flaws of C++...

Yes, but calc_divu and many of the other functions in IAMR do not have the same format and names in this code, so if PeleLM is going to use incflo at any point the work will probably need to happen on that end.


Suggestions from a specific namespace aren't shown unless prefixed with {NAMESPACE}:

Is there some way I can influence this behaviour?
I tried changing the Filtering Mode but that doesn't seem to affect this

What is the issue here exactly? What you've pictured is intended behavior. In the first image nothing shows up because you're searching for aquamirae in all namespaces, which means only the path part of the resource location is compared. In the second image you're searching for everything inside the aquamirae namespace.

well if i search for aquamirae i would've kinda expected it to list structures from aquamirae
otherwise i always have to write out the namespace for it to actually search the structures related to said namespace

You have a reasonable expectation but this doesn't work for all cases. I made it this way to prevent the suggestions from getting cluttered because of some mod's namespace, e.g. when you try to search for some item or w/e containing aqua but then you have to skip through all of aquamirae's suggestions. I think it's a reasonable trade-off but if more people have something to say against it I might change it.

not sure if this is possible but can you filter the namespace when you write it as :aqua?
meaning aqua shows the structures incl. namespace but :aqua only shows things where the word is in the path

It's possible but idk how generally preferable that is to the current implementation.

Hey!  I was also looking to search via namespace initially and would greatly appreciate this functionality.  Could it be introduced as a config?
Maybe if you could have a more strict or separate strictness for namespaces?


Improve Sia sample

Description

Plan to use wgpu as the backend, and currently priority is given to winit as the gui load by dotnet console.
winit: cross-platform window handle
wgpu: cross-platform graphic api

[ ] #16

What is the purpose of this pull request?

[ ] Bug fix
[x] New Feature
[ ] Documentation update
[ ] Other

This part will be move to another repository. A simple sample would be better.


How to prepare the data?

Thanks for your inspired work, and I would like to know how to prepare the data, such as BraST datasets.
When I download the BraST dataset, it includes 3 folds: ImageTr, Label, ImageTs. All files are stored as .nii.gz file, and how to use these data?
Thanks for your reply!

Hi @YurongChen1998
Thanks for your interest in using our code.
You need to store the files as numpy files (format ".npy"). And then you should be able to load these files. Check out the loader scripts here: https://github.com/HealthML/self-supervised-3d-tasks/blob/master/self_supervised_3d_tasks/data/segmentation_task_loader.py or here: https://github.com/HealthML/self-supervised-3d-tasks/blob/master/self_supervised_3d_tasks/data/numpy_3d_loader.py

Btw, there is a helper script here to convert nifti files to npy: https://github.com/HealthML/self-supervised-3d-tasks/blob/master/self_supervised_3d_tasks/data_util/ukb_convert_brain_mri_to_npy.py


Document observability with OSM (howto; tools; configuration)

In our demos we show observability with Jaeger.
This Github Issue is to write a document on:

how we enable observability (how are Envoys configured)
how we install Jaeger and what can be done with it
what other software can be used to extend OSM (Zipkin, OpenTelemetry etc.)

As an aside, can you write some documentation somewhere for the zipkin stuff when you get a chance?

@draychev - Were you planning for some docs at some point? I can certainly help if needed.
Originally posted by @nojnhuh in https://github.com/open-service-mesh/osm/pull/907#issuecomment-649857479

There's some documentation here on Jaeger
@nojnhuh what's the status on documentation for Zipkin and OpenTracking?

I think that's all we were looking to add for now. I don't think we need anything for Zipkin or OpenTracing if we've settled on Jaeger. @draychev Is there any more you were looking to add for this issue?

I'd definitely like to see a move thorough documentation on "Observability with OSM"
I am going to rename this Issue to reflect this.

This was completed.

ref https://github.com/openservicemesh/osm/issues/1919

ref https://github.com/openservicemesh/osm/issues/1921
ref https://github.com/openservicemesh/osm/issues/1511


Can we work on why there's the pop or hiss in some generate voice samples

The title says a lot but the issue is sometimes there's the random noise at the end of a generated sample or sometimes there's a metallic sound in the middle of a voice sample.
I have noticed that if a deep breathe is made there will be a metallic hiss, to me it seems as if there's no valid voice sample for the sound the algorithm falls back to a  metallic sound similar to the first stage training to generate the mel spectrum.
Is there a way to have some debugging where we can see where in the data was sampled to generate the audio, this could help us debug if these metallic sounds even on well trained voice models be an issue of insufficient data to generate quality output.

@akaihaoshuai can you share the hiss you're talking about? I'll get some of the hiss that I have and try to upload it some where to share it here as well.

Hello!
They already solved this issue here:
https://github.com/yl4579/StyleTTS2/discussions/81
TL;DR >> Add a little bit of silence at the beginning and end of each training sample in your dataset.

@akaihaoshuai can you share the hiss you're talking about? I'll get some of the hiss that I have and try to upload it some where to share it here as well.

I solved it by modifying the configuration file as follows
config = yaml.safe_load(open("models/LJSpeech/config.yml"))


refactor(storage): build rowset while appending data in ColumnMemTable

Signed-off-by: asuka<EMAIL_ADDRESS>

Please format your codes with “cargo fly”


Paginate dataset list

Quickly figured this out, no UI changes but allows showing more datasets with ?page=2.

Looks good but I'm not sure those who initially raised the issue will be happy to edit URL parameters to get pagination working.

No worries, it's just meant to be a quick hack before the UI is
implemented. At least it provides access to data which is currently not
accessible at all.
On Fri, 12 Jun 2020 at 12:55, Vitaly Kovalev<EMAIL_ADDRESS>wrote:

Looks good but I'm not sure those who initially raised the issue will be
happy to edit URL parameters to get pagination working.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/metaspace2020/metaspace/pull/603#issuecomment-643209504,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAK5BWM6TYCDWEFGZWGQGM3RWICSXANCNFSM4NSPQGZA
.


Question: Missing instructions for react-native-screens installation in iOS?

Current behavior
Hi! Looking at the react-native-screens installation guide for iOS, I see there is one extra step to properly set it up, which includes adding some handlers to the AppDeletegate.mm to start listening for orientation notifications. However, this step is not documented in the react-navigation docs.
Considering react-navigation depends on react-native-screens, I was wondering whether this is something we should add to our app as well.
Link to the installation guide: https://github.com/software-mansion/react-native-screens#ios
Expected behavior
Either clarifying in the react-navigation docs that this step is not necessary, or adding it as part of the installation process in the docs.
Reproduction
https://github.com/software-mansion/react-native-screens#ios
Platform

[ ] Android
[X] iOS
[ ] Web
[ ] Windows
[ ] MacOS

Packages

[ ] @react-navigation/bottom-tabs
[ ] @react-navigation/drawer
[ ] @react-navigation/material-bottom-tabs
[ ] @react-navigation/material-top-tabs
[X] @react-navigation/stack
[ ] @react-navigation/native-stack

Environment

[x] I've removed the packages that I don't use

package
version

@react-navigation/native
6.0.11

@react-navigation/native-stack
6.7.0

react-native-safe-area-context
4.3.1

react-native-screens
3.17.0

react-native-gesture-handler
2.5.0

react-native-reanimated
2.9.1

react-native
0.69

node
16.10.0

npm or yarn
7.24.0

Fixed in https://github.com/software-mansion/react-native-screens/pull/1596


Feature/dds psm api xtypes test

adding test

Build status:

Linux
Mac
Windows
Performance

Build status:

Linux
Mac
Windows
Performance

Build status:

Linux
Mac
Windows
Performance

Build status:

Linux
Mac
Windows
Performance

Build status:

Linux
Mac
Windows
Performance

Rebase to main xtypes branch

Build status:

Linux
Mac
Windows
Performance

Build status:

Linux
Mac
Windows
Performance

Build status:

Linux
Mac
Windows
Performance

Build status:

Linux
Mac
Windows
Performance

Build status:

Linux
Mac
Windows
Performance


Feature: Delete image files along with the presentation

Add a button next to "Destroy" labelled something like "Destroy and delete" that deletes all image files on the server associated with this presentation, so unused slides do not pile up.

Implemented in 01ba7f7d6b2f50a0655fea0b1b2421fc493641e0


Add test coverage for rest-data-with-panache repositories

This work is part of https://github.com/quarkus-qe/quarkus-test-plans/blob/main/QUARKUS-976.md effort

There are just a few minor (cosmetic) changes, apart from that LGTM

@pjgg @Sgitario comments were resolved. May you take another look pls.


Allow theme switcher override with slots

Closes https://github.com/mui/toolpad/issues/4151 and https://github.com/mui/toolpad/issues/4291

Include ThemeSwitcher component in toolbarActions slot so it can be hidden
Export existing ThemeSwitcher and ToolbarActions (default slot) components
Add example of popover menu & custom theme switcher in DashboardLayout demo page in docs

https://deploy-preview-4340--mui-toolpad-docs.netlify.app/toolpad/core/react-dashboard-layout/#customization

@bharatkashyap I just noticed this if you sign out in the "Account in sidebar" example:

Probably no need to fix it in this release, just ran into it! Also not sure how to best handle it in the mini variant of the sidebar...

Probably no need to fix it in this release, just ran into it! Also not sure how to best handle it in the mini variant of the sidebar...

Thanks for that catch! I'll open an issue to track this


Question: Disallow toString / cast to String

Hi,
I like to disallow (=compiler error) the toString / cast to string for a object. Is this possible?
TypeScript Version:
1.8
Code
I have the following class:
class Person
{
   private toString(): string {
            return "not allowed";
    }
}
var person1 = new Person();

This is now disallowed
person1.toString();

But can I also disallow this?
var text = person1 + "";

Is this possible

Just quick info : Not at the moment :rose:

You could throw in the toString() method if you are really that desperate to keep people from using implicit coercion on your instances.

You could throw in the toString() method if you are really that desperate to keep people from using implicit coercion on your instances.

Yes, we're doing it now, but I was hoping for a better solution.
Thanks for the replies!


Has anyone encountered such a problem where the webpage can be successfully opened, but there is no response when clicking ‘interact’?

I deployed this project on Windows. After the deployment, I opened the webpage and clicked the ‘interact’ button, but there was no response. Does anyone know how to fix this?

it seems tobe something wrong with the backend

I had the same issue, but I solved it. There are my steps:

STOP all the code for ai-town
cd ai-town folder
run just convex run init
restart ai-town

I had the same issue, but I solved it. There are my steps:

STOP all the code for ai-town
cd ai-town folder
run just convex run init
restart ai-town

Thank you very much for your solution. I’ve managed to get it running successfully as well. Thank you！But there seems to be a bit of an issue with my page still; I can’t see the conversation between Agents. When I click ‘interact’ to interact with one of the Agents, there’s no response. I think there must still be some problems. Anyway, thank you very much.

me too ,why

Have you solved this problem yet? If not, you can try using this method from leotireger; I’ve already got it running successfully.

Thanks you two a lot, I 'll have a try

I had the same issue, but I solved it. There are my steps:

STOP all the code for ai-town
cd ai-town folder
run just convex run init
restart ai-town

Thank you very much for your solution. I’ve managed to get it running successfully as well. Thank you！But there seems to be a bit of an issue with my page still; I can’t see the conversation between Agents. When I click ‘interact’ to interact with one of the Agents, there’s no response. I think there must still be some problems. Anyway, thank you very much.

I finally run the total project just now. After making sure ollama's serve is working properly locally, and and then follow the steps linked below :
https://github.com/a16z-infra/ai-town/issues/249#issuecomment-2439830066
There are my steps:

STOP all the code for ai-town
delete ".env.local" file
run just convex run init
in a terminal, run npm run dev:backend
in a new terminal, run npm run dev:frontend
Maybe there are some other steps not mentioned, but key points are mentioned above, you can try it and good luck.

me too ,why

Have you solved this problem yet? If not, you can try using this method from leotireger; I’ve already got it running successfully.

Now I have known how to successfully run the backend and restart the code. But my frontend still can't work as your pic. BTW, how can I record the messages locally. When I run the code locally, I have no dashboard.

5. but key points are mentioned above,

Thank you for your solution, but I'm still encountering issues. My program's request for Ollama's service was denied. I'm wondering if you have experienced this problem as well. May I ask what type of machine you ran your program on? I am using a Windows system and followed the WSL deployment method mentioned in the README. I also saw in the issues section that others have encountered the same problem as me, but I haven't found a good solution yet.The issue I'm encountering is as follows. My frontend displays normally, but there is no dialogue between Agents.

Thank you very much for your reply regardless. I wish you all the best.

but key points are mentioned above,

Thank you for your solution, but I'm still encountering issues. My program's request for Ollama's service was denied. And I have already tested that I can communicate with Ollama using the api/embed method in the WSL environment. However, the problem arises only when I try to integrate it into my program.I'm wondering if you have experienced this problem as well. May I ask what type of machine you ran your program on? I am using a Windows system and followed the WSL deployment method mentioned in the README. I also saw in the issues section that others have encountered the same problem as me, but I haven't found a good solution yet.The issue I'm encountering is as follows. My frontend displays normally, but there is no dialogue between Agents.   Thank you very much for your reply regardless. I wish you all the best.

For me, if the frontend is running normally, it must be on the cloud version convex, so you can't get local ollama embed.


Added --batchable option to artisan make:job command

With the --batchable option you can quickly create a batchable job.

Hmm, I'm not sure I want to maintain another stub just for this one trait. 😅


No way to provide Pact token for Dius Pact broker

The Dius hosted pact solution now requires a token rather then username / password.  Is there a way to provide this?
Similar to this previous issue, but with a token auth.
<configuration>
  <contractsRepositoryUrl>pact://https://pocJKHSAJ.pact.dius.com.au:443</contractsRepositoryUrl>
  ...
</configuration>

Thanks

I think we've added that in the latest release 3.0.0-m2 https://github.com/spring-cloud/spring-cloud-contract/blob/master/spring-cloud-contract-tools/spring-cloud-contract-pact/src/main/groovy/org/springframework/cloud/contract/stubrunner/PactStubDownloaderBuilder.java#L312 you can try adding the property

I tried on 3.0.0-M2 using both of the approaches below, neither seemed to work.
Maven plugin:
<contractsRepositoryToken>myToken</contractsRepositoryToken>
Env variable property:
-Dpactbroker.auth.token=myToken

Can you please try the system property in such a form -Dstubrunner.pactbroker.auth.token=myToken ? Or like described in https://docs.spring.io/spring-cloud-contract/docs/3.0.0-SNAPSHOT/reference/html/maven-project.html#maven-configuration-options <contractsProperties><pactbroker.auth.token>myToken</pactbroker.auth.token></contractsProperties> ?

I tried system property and via plugin configuration in the POM and neither resolve the issue for me unfortunately.
For example the following failed:
<plugin>
	<groupId>org.springframework.cloud</groupId>
	<artifactId>spring-cloud-contract-maven-plugin</artifactId>
	<version>3.0.0-M2</version>
	<extensions>true</extensions>
	<configuration>
		<contractsRepositoryUrl>${pact.url}</contractsRepositoryUrl>
		<contractsProperties>
			<pactbroker.auth.token>${pact.auth}</pactbroker.auth.token>
		</contractsProperties>
		<contractsMode>REMOTE</contractsMode>
		<contractsPath>my-path</contractsPath>
		<contractDependency>...</contractDependency>
		<baseClassForTests>MyBaseClass</baseClassForTests>
	</configuration>
	<dependencies>
		<dependency>
			<groupId>org.springframework.cloud</groupId>
			<artifactId>spring-cloud-contract-pact</artifactId>
			<version>3.0.0-M2</version>
		</dependency>
	</dependencies>
</plugin>

Do you have a sample POM plugin configuration that uses auth that I can attempt to follow please?

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


make DBController tolerant to wrong framework request

Currently, database controller assumes all framework requests it receives are valid. Thus it will try to sync every framework request to api server.
However, it is hard to validate the request in the rest-server. There is chance that rest-server generates wrong framework requests. Then database controller will keep trying to sync the wrong request forever.
We could make DBcontroller tolerant to wrong framework request.

In previous design #4651,
We assume apiserver submission error as our platform issues, such as we generated invalid json object, so we always retry and expose the errors as job events to user.

Is that good enough?

In previous design #4651,
We assume apiserver submission error as our platform issues, such as we generated invalid json object, so we always retry and expose the errors as job events to user.

Is that good enough? As you cannot totally distingush between transient and permenant apiserver submission error.
BTW, any real example for the apiserver submission error?
Curious how can we generate invalid framework object

If such error happens, I think the user may not able to stop the job. e.g. rest-server generates a wrong request object  -> the request object is stored in db ->  db controller tries to sync it to api server, but failed -> user stop the job, which will patch the spec.executionType field of the framework request object in db -> db controller tries to sync it to api server, but failed -> user will see his job is always in Stopping status.
I haven't found a real example.

@hzy46  Valid point for the stop request cannot be satisfied, but we have to send stop to apiserver, because you do not know if the job really stopped (or not exist) in k8s. Considering this issue is most caused by our platform issues, under platform issues, everything may not work properly, so hang in stopping is acceptable, and we need to fix the platform issue ASAP/

@yqwang-ms
If ApiServer non-404 error, can we mock a Failed Framework event to watcher? I think it is a clean solution for this problem.

It should be:

If ApiServer reports non-404 error, and it is caused by a invalid protocol, mock a Failed Framework event to watcher.
If ApiServer reports other non-404 error, add the event to db.

That's ok now. Be sure that we are sure that the error MUST BE "caused by a invalid protocol", and then have 100% confidence to mock Fail job

If ApiServer reports non-404 error, and it is caused by a invalid protocol, mock a Failed Framework event to watcher.

Is there a specific error code from FC to indicate failed validation?

It is the error code from ApiServer instead of FC. We can just use Status code 422 in the first stage.
BTW, would better give one example of this issue, so we know the exact Status code of it

It is the error code from ApiServer instead of FC. We can just use Status code 422 in the first stage.
BTW, would better give one example of this issue, so we know the exact Status code of it

An example found and recorded in #5093

Work items for this issue:

[ ] If non-404 error in poller, store it as a framework event.
[ ] If any unrecoverable error happens, mock a Failed Framework event to watcher.

[ ] Add 413 / 422 in the unrecoverable errors.


Submission 729 (Northern Greenland) is missing Connectivity Level attribute

It's not too important since they are all level 0 or 1, but it would be nice to have.

Trello: https://trello.com/c/GFI39nz3

Frank says its not important


Fixed #25390 -- Alowed specifying a start migration in squashmigrations.

Ticket: https://code.djangoproject.com/ticket/25390

Will this handle dependencies correctly?
$ python manage.py squashmigrations auth 0002 0005
Will squash the following migrations:
 - 0002_alter_permission_name_max_length
 - 0003_alter_user_email_max_length
 - 0004_alter_user_username_opts
 - 0005_alter_user_last_login_null
Do you wish to proceed? [yN] y
Optimizing...
  No optimizations possible.
Created new squashed migration /home/tim/code/django/django/contrib/auth/migrations/0002_alter_permission_name_max_length_squashed_0005_alter_user_last_login_null.py
  You should commit this migration but leave the old ones in place;
  the new migration will be used for new installs. Once you are sure
  all instances of the codebase have applied the migrations you squashed,
  you can delete them.
(django34)[~/code/mysite] (master)
tim$ python manage.py migrate auth
CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0007_alter_validators_add_error_messages, 0001_initial in auth).
To fix them run 'python manage.py makemigrations --merge'

Ouch, good point. I missed an edge case. Thanks!

The squashed migration is always marked initial = True. This doesn't seem correct.


Templated-docs crashes server with exit codes 139, 77

Templated-docs version: 0.2.9
Python version: 2.7.12
Operating System: Ubuntu 16.04

Description
I faced a critical bug which kills Django server with exit codes 139, 77.
I have an API which handles .docx render. I will show one of views, as an example, they are pretty similar:
@permission_classes((permissions.IsAdminUser,))
class BookDocxViewSet(mixins.RetrieveModelMixin, viewsets.GenericViewSet):
    def retrieve(self, request, *args, **kwargs):
        queryset = Pupils.objects.get(id=kwargs['pk'])
        serializer = StudentSerializer(queryset)
        context = dict(serializer.data)
        doc = fill_template('crm/docs/book.ott', context, output_format='docx')
        p = u'docs/books/%s/%s_%s_%s.doc' % (datetime.now().date(), context[u'surname'], context[u'name'], datetime.now().date())
        with open(doc, 'rb') as f:
            content = f.read()
            path = default_storage.save(p, ContentFile(content))
            f.close()
        return response.Response(u'/media/' + path)

When I call it the first time, it creates a .docx file, saves it to my default_storage and then returns me a download link. But when I try to do it again, or do it with another method (which works with another template and context), my server just crashes without any logs. The last thing I see is either
Process finished with exit code 77 if I call it with a little delay (more then one second)
Process finished with exit code 139 (interrupted by signal 11: SIGSEGV) if call my method for the second time right away (in less than one second)
I tried to use debuger -- it said that my server crashes on this line:
doc = fill_template('crm/docs/book.ott', context, output_format='docx')
I bet what happens is:

When I call my method the first time templated_docs starts LibreOffice backend, and then does not stop it
When I call my method the second time templated_docs tries to start LibreOffice backend again, but it is already busy.

According to this documentation, the process that used pylockt should be killed after. But we cannot kill Django server.
What I Did
I made some changes to __init__.py to add multiprocessing. Pull request is attached.
Paste the command(s) you ran and the output.
If there was a crash, please include the traceback here.

I have the same code base running either on nginx and apache. With @dukeimg  commit it works perfectly on nginx. No more crashes (I was also struggling with this bug)
However, on the apache2 codebase, it doesn't work at all. Probably some config issue.
@dukeimg , were you using nginx on deployment too? Thanks for the commit!!

@dudanogueira Yes. We do use nginx.

Hey Viktor, thanks for a patch! I've just proposed the pylokit's author to incorporate your change in his/her library, let's see if that works out. Here's the ref: https://github.com/xrmx/pylokit/issues/7

@dukeimg @dudanogueira which version of libreoffice do you have? Do you have any backtrace or log?

hi @xrmx I am actually using libreoffice 1:5.2.0~rc4-0ubuntu1~trusty1 and it's working fine with @dukeimg patch with nginx. The strange thing is that it doesn't give much a clue about the problem on the logs. On nginx I got:
2016/08/10 08:09:42 [error] 1623#0: *7 upstream prematurely closed connection while reading response header from upstream, Client. XXXXXXXXX
that's why @dukeimg was bright on his assertion about the origin of the bug. It was like a head shot in the dark :)

@dudanogueira ngnix logs won't tell you much, you'd better check out uwsgi/gunicorn/runner-you-use logs.

@dudanogueira unfoutunately, logs won't tell you anything. That's why I spend 2 hours with debugger, looking how those libraries were executed line by line :P

Hope that's fixed in b0a6669. Feel free to reopen if you see it's not.


[WIP] Swift 5.1/Xcode 11 support

[x] Swift 5.1
[x] Swift Package Manager integration
[ ] Fix bugs on iOS 13

If there's any specific Xcode 11/Swift 5.1 feature that would be nice to support please let me know.

Having trouble with AppStoreAnimator on iOS 13. Animates wrong, broken constraints. Any help would be appreciated.

@tomislav yes I saw that issue as well. It will be fixed on the upcoming weeks. I'll post the updates here.

@marcosgriselli any updates?

@pchelnikov I haven't been able to work on this library for a while. It's still in my plans to do it but I don't have a delivery date estimate unfortunately


Fixed withIndexHTML example when leading / is stripped

When leading / is stripped, withIndexHTML receives "" as URL path and doesn't handle it as "/".
Fix for #16 (2nd issue)

Thanks!


Deprecation warning from pandas

anndata/_core/anndata.py:21: FutureWarning: pandas.core.index is deprecated and will be removed in a future version.  The public classes are available in the top-level namespace.
from pandas.core.index import RangeIndex
RangeIndex is now accessible directly as pandas.RangeIndex.

Please use the search function: https://github.com/theislab/anndata/search?q=RangeIndex+is%3Aissue&type=Issues
This has been fixed as #319


DoubleSlabs 1.12.2 not compatible with Conquest Forged (same version)

Hi, as mentioned on the CurseForge mod page (and in the title), would love it if both mods (both 1.12.2) were compatible (the Conquest Reforged mod does come with vertical slabs btw).
Thanks!

Added in the latest version!


fixed upper_tab_bar file carshing and added const

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Fixed Upper_tab_bar Crashing

Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Manual testing
[x] Widget testing
[ ] Unit testing

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

I have fixed this issue

Congrats @Ayushpanditmoto 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐

SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .

Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.

https://www.clueless.tech/profile/admin/31253617
@Roshaen


Tiling performance regression

I think the recent grid refactoring (5e734f20) has introduced a regression in the tiling performance.
I'm observing this on the mobile example. With a cold browser cache when I click on the + button to zoom in it takes approximately 1 second to load all the tiles for the new zoom level. If I checkout 40806db (the grid refactoring commit's parent) the same operation takes approximately 250ms. It looks like the refactoring decreases the level of tile loading parallelization.
I hope I can provide more information later, but this initial experience demonstrates the regression I think.

This raises the question: how do you measure overall performance of a slippy map, and how do you determine if it is a regression or not?
If you measure performance by using pan and zoom heavily to navigate to a place on the map, I'm sure we perform way better now than before 5e734f2. The old behavior put an incredible burden on servers when navigating the map, and used more network bandwidth than we use now. Server administrators, and people who run free services like tile.openstreetmap.org and have to pay for bandwidth will thank us for 5e734f2. Also when loading layers from a plain WMS server (without a tile cache), there is a good chance we perform better now, depending on how many tiles per second the WMS can serve.

Also note that there were other changes that have an impact on tile loading, e.g.

Previously, the OSM layer only used tile.openstreetmap.org. Now we use {a,b,c}.tile.openstreetmap.org.
Previously, we did not set the crossorigin attribute for images. This means there will be an extra OPTIONS request now for every tile.

@ahocevar Excellent remarks. I'll do more experiments.

More information: if I revert the grid refactoring commit only (git revert --no-commit -m1 5e734f2) then the tiles loading time difference is even bigger: 1s with the grid refactoring commit, and 130ms without.

@elemoine OpenLayers.Animation performs one operation per 16ms if native requestAnimationFrame is not available. For a screen size that shows 46 = 24 tiles, this would mean that 2416 = 384ms are spent waiting.

Also note that using tile.openstreetmap.org as test server for your benchmarks is pointless. To get comparable results, you would need a tile server that is only hit by you.

Some answers and comments:

The abortable nature of the tile queue is definitely a win.
I'm doing tests in FireFox 10, where requestAnimationFrame is available.
I'll look at using a private tile server.

Ah, Firefox. I am somewhat able to reproduce the issue. It seems Firebug has a negative impact on performance, but even without Firebug enabled I notice a difference.

Hm. Now I compared master with 2.11, and it seems tile.openstreetmap.org is slow today (2.11 is just as slow as master). With the Bing layer in the mobile-jq example, both 2.11 and master feel like they perform equally well.

Ok, here are some test results:
Server: local GeoWebCache with the world layer from the OpenGeo Suite
Example: mobile.html, modified to use OpenLayers.Layer.WMS from Server, with transitionEffect: resize
Map size: 1675x648 pixels
Environment: Firefox 10, Firebug enabled
Test setup:

load page

clear cache

reload page

add the following listeners through the Firebug console:
map.baseLayer.events.register("loadstart", this, function() {console.time("load");});
map.baseLayer.events.register("loadend", this, function() {console.timeEnd("load");});

zoom in 4 times.

Results master:
load: 977ms
load: 954ms
load: 968ms
load: 899ms
(average: 950ms)

Results 2.11:
load: 747ms
load: 690ms
load: 735ms
load: 795ms
(average: 742ms)

No big surprises I'd say.

@ahocevar Thanks for the numbers. I'll try to do more testing tonight or tomorrow, using @twpayne's excellent tileclould. And btw, don't get me wrong, I don't think the grid refactoring is a win. I'm just wondering if the tile queue could be better managed, to maximize the level of parallelism.


Build for Apple Silicon (darwin-arm64) devices in CI, and sign and notarize all macOS binaries

[!IMPORTANT]
Add Apple Silicon build and signing support to CI workflow for macOS in build_and_release.yml.

CI Workflow:

Add aarch64-apple-darwin target to build matrix in build_and_release.yml for Apple Silicon support.
Introduce darwin-arm64 as binary name for ARM64 macOS builds.
Add steps to sign and notarize macOS binaries using indygreg/apple-code-sign-action@v1 when os is macos-latest.

This description was created by  for 9ea45f59c0d82e50c4c24f42f81b595ed3f3d1ac. It will automatically update as commits are pushed.

Summary by CodeRabbit

New Features

Added support for building binaries for the new aarch64-apple-darwin architecture on macOS.

Improvements

Enhanced job matrix configuration for better readability and structure.
Introduced signing and notarization steps for macOS binaries to ensure security and compliance.

Fixes #82.


Signin Button looks like link but there should be different background color and text decoration of button have to be removed for better UX

Here is the issue , what it looks like when visiting auth/signin route of 100xdev webpage.

Here is the issue , what it looks like when visiting auth/signin route of 100xdev webpage.

If you think it is valid issue then let me fix this by assigning this to me . This same color and hover would be great in auth/signin.


PNP error can't create site - Need help with deploy.ps1 script

`### TEAMS REQUESTS SITE CREATION ###
Creating Teams Requests SharePoint site...
Error occured while creating of the SharePoint site: Cannot bind argument to parameter 'Title' because it is null.
Connect-PnPOnline : The remote server returned an error: (401) Unauthorized.
At C:\Scripts\Deploy\Teams\Auto-Provisioning\Deployment\Scripts\deploy.ps1:699 char:15

$pnpConnect = Connect-PnPOnline $requestsSiteUrl

          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Connect-PnPOnline], WebException
FullyQualifiedErrorId : System.Net.WebException,SharePointPnP.PowerShell.Commands.Base.ConnectOnline

REQUESTS SPO SITE CONFIGURATION
Configuring SharePoint site...
Applying provisioning template...
WARNING: The source site from which the template was generated had a base template ID value of GROUP#0, while the current target site has a base template ID value of TENANTADMIN#0. This could cause potential issues while applying the t
emplate.
WARNING: ListInstance Style Library is a Style Library of a site with NoScript enabled and will be skipped
Apply-PnPProvisioningTemplate : Access denied. You do not have permission to perform this action or access this resource.
At C:\Scripts\Deploy\Teams\Auto-Provisioning\Deployment\Scripts\deploy.ps1:286 char:9

    Apply-PnPProvisioningTemplate -Path (Join-Path $packageRootPa ...

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : WriteError: (:) [Apply-PnPProvisioningTemplate], ServerUnauthorizedAccessException
FullyQualifiedErrorId : EXCEPTION,SharePointPnP.PowerShell.Commands.Provisioning.Site.ApplyProvisioningTemplate
Applied template`

@Lolipopzs It appears that it's trying to apply the PnP template to your SPO admin center. Can you check the parameters that you provided please.


Move LLM callbacks to base class

Description
This PR adds a decorator to the LLM endpoints to hook in API calls. Now, every LLM call is observable, including during agent usage. (This also adds token counting to agents!).
Type of Change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

[x] Tested existing notebooks
[x] I stared at the code and made sure it makes sense

One caveat is that I removed pydantic from the OpenAI and Azure LLM classes. It was conflicting with how I wanted the callback manager to work

nit: Instead of llm_callback with is_chat arg. perhaps just two separate decorators?

@Disiok split the callbacks into two, also ensured that counting tokens works for streaming 👍🏻


Any plan for new release? Need redis v9

Redis v9 codes has merged into master months ago, but the latest v0.7.1 release does not contain that.

@zyfdegh please used with tag v0.7.2


feat(#26): release to pypi

[ ] I have considered whether this PR needs review, and requested a review if necessary.

Fixes issue #
Notes for reviewers
Reviewers can skip X, but should pay attention to Y.

Merge activity

Feb 5, 1:50 PM GMT+1: @MartinBernstorff merged this pull request with Graphite.


Qwant Maps, Vespucci, & Discord

Qwant Maps - Only real  web based Google Maps alternative using OSM data I've seen.
Vespucci - Android only OSM editor. A bit more advanced but more powerful too.
There's also a Discord server
I know of a few others too and I'll add them to this list/issue soon

Thanks!
I've gone ahead and added them, feel free to open another issue with more suggestions! 🙂


Add composeK, dissoc and pipeK

Tell me more, tell me more

Another PR to add some more helpers. With the addition of composeK and pipeK, that should close out this issue. Figured I should add dissoc as assoc has been added.

Coverage remained the same at 100.0% when pulling b0b4fd704649addc0b85842bb29511d00fd3baea on add-more-funcs into 195dfeddb2d65fe6a99a7c98be3d75ace436b081 on master.


Partition is not resized at VM creation

Disk size is allocated according to flavor, but the partition inside it is not resized.

On a running linux system, it is possible to resize (upsize only) the partition, of course you must have root privileges.

Get the partition start with fdisk -l /dev/vda.

Disk /dev/vda: 21.5 GB,<PHONE_NUMBER>0 bytes
255 heads, 63 sectors/track, 2610 cylinders, total 41943040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00030fe9
Device Boot      Start         End      Blocks   Id  System
/dev/vda1   *        2048    16775167     8386560   83  Linux

Now delete + recreate a partition with the same start and the end at the end of the disk

fdisk /dev/vda

Command (m for help): d[ENTER]
Selected partition 1
Command (m for help): n[ENTER]
Partition type:
p   primary (0 primary, 0 extended, 4 free)
e   extended
Select (default p): p[ENTER]
Partition number (1-4, default 1): 1[ENTER]
First sector (2048-41943039, default 2048): [ENTER]
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-41943039, default 41943039):
Using default value 41943039
Command (m for help): w[ENTER]
The partition table has been altered!
Calling ioctl() to re-read partition table.
WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table. The new table will be used at
the next reboot or after you run partprobe(8) or kpartx(8)
Syncing disks.

Force the kernel to re-load the partition table

partprobe

And now resize the filesystem to match the partition size

resize2fs /dev/vda1

resize2fs 1.42.9 (4-Feb-2014)
Filesystem at /dev/vda1 is mounted on /; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 2
The filesystem on /dev/vda1 is now 5242624 blocks long.

New base images ('xubuntu 15.04 1.01' and 'ubuntu server 1.01') with automatic resize have been uploaded.
Old image can be resized by running this script (as root):
#!/bin/bash
echo "d
n
p
1

w
"|fdisk /dev/vda
partprobe
resize2fs /dev/vda1


Muchocine - Spanish movie reviews dataset

Hi @mapmeld !
have you had a chance to take a look at my suggestions ?
Feel free to ping me if you have questions or when you're ready for a review

@lhoestq unfortunately I don't have any more information about where the dataset comes from

It's fine, you can just add the sections titles back and leave the content with [More Information Needed]

added missing sections, updated the Python code ✅


Update project-for-the-web-limits-and-boundaries.md

We had the wrong date range listed for task dates. It does not start at 1/1/1984. It starts at 1/1/2000.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@JohanFreelancer9 do I need to do anything else to get this change published? I'm not familiar with the process. Thanks!

@hocull - Thank you. nothing more is required from your side. @scanum - This PR is ready for final review.

@efrene PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Storage sample docs #6

fixes #6

@Suresh-Nakkeran Can you help rebase from main branch to fix the netlify CI build issue?

/lgtm
/approve


build: use fixed Go version

TODO

This is a test build. I expect it to fail the same way as https://cloudnative-k8sci.southcentralus.cloudapp.azure.com/blue/organizations/jenkins/pmem-csi-periodic/detail/pmem-csi-periodic/152/pipeline with:
go test -run none ./pkg/... ./test/e2e

?   	github.com/intel/pmem-csi/pkg/coverage	[no test files]

?   	github.com/intel/pmem-csi/pkg/ndctl	[no test files]

?   	github.com/intel/pmem-csi/pkg/pmem-common	[no test files]

?   	github.com/intel/pmem-csi/pkg/pmem-csi-driver	[no test files]

?   	github.com/intel/pmem-csi/pkg/pmem-device-manager	[no test files]

?   	github.com/intel/pmem-csi/pkg/pmem-exec	[no test files]

?   	github.com/intel/pmem-csi/pkg/pmem-grpc	[no test files]

ok  	github.com/intel/pmem-csi/pkg/pmem-ns-init	0.033s [no tests to run]

?   	github.com/intel/pmem-csi/pkg/pmem-registry	[no test files]

ok  	github.com/intel/pmem-csi/pkg/pmem-state	0.048s [no tests to run]

?   	github.com/intel/pmem-csi/pkg/pmem-vgm	[no test files]

ok  	github.com/intel/pmem-csi/pkg/registryserver	0.081s [no tests to run]

flag provided but not defined: -test.testlogfile

Usage of /tmp/go-build240487305/b265/e2e.test:
[no -test flags here]

Clear Linux updated to go 1.13 and that broke invoking the e2e.test binary.

When avoiding the build image reuse it also fails for PRs:
https://cloudnative-k8sci.southcentralus.cloudapp.azure.com/blue/organizations/jenkins/pmem-csi/detail/PR-397/2/pipeline