Pagekit self-update command fails

Problem
I wanted to update Pagekit from 1.0.5 to latest version. I first tried this via command line by running:
./pagekit self-update. The output I received is the content of a webpage, which inside the body has
Whoops, looks like something went wrong.
.
I checked at the recommended way to update Pagekit, and went with the update in the admin panel. Update was successful. After update, I wanted to run ./pagekit self-update to see what I get. Same result.
I checked the app/console/src/Commands/SelfupdateCommand.php and it seems the problem comes from line 42 ($this->client = new Client; - >GuzzleHttp\Client). However, I can't find a reference to GuzzleHttp anywhere in the dependencies (by looking at Composer).
After a quick grep -r 'Guzzle' ./* in the project folder, I see Guzzle being referenced in the following places:

./app/console/src/Commands/SelfupdateCommand.php:use GuzzleHttp\Client;
./app/console/src/Commands/SelfupdateCommand.php:use GuzzleHttp\Exception\BadResponseException;
./app/console/src/Commands/SelfupdateCommand.php:use GuzzleHttp\Exception\TransferException;
./app/console/src/Translate/TransifexApi.php:use GuzzleHttp\Client;
./app/vendor/monolog/monolog/tests/Monolog/Formatter/NormalizerFormatterTest.php:
./CHANGELOG.md:- Removed Guzzle dependency

So, according to Changelog, Guzzle dependency was removed in version 0.11.3 (April 7, 2016). Not sure what the plan is for self-update, so I'm making this issue here to reference the problem I found (couldn't find another issue which talks about self-update).
Technical Details

Pagekit version: 1.0.5 and 1.0.8
Webserver:    nginx/1.9.14
Database: SQLite 3.8.2
PHP Version: 7.0.5-2+deb.sury.org~trusty+1

Thanks for reporting!

I'm having the same problem, right now, with 1.0.8.

The fix for this is not delivered yet. So 1.0.8 still contains this bug and only the next version should not have it any more.


Implement language server protocol client

https://docs.microsoft.com/en-us/visualstudio/extensibility/adding-an-lsp-extension?view=vs-2017
If this works out it could greatly reduce the amount of IntelliSense and other editor code we have to maintain.
Some of our special needs are not necessarily well tested / supported, so there are risks:

Designed to work for open folder, not projects, so we need to do custom initialization for projects
Colorization supported by TextMate, should be able to use our own colorizer
Interactive window completions require fetching from both language server and live running session

This will require porting our custom functionality that isn't supplied by language client. We'll need to move our own Analysis protocol as language server protocol extension and access it via the LSP client connection.

Closing in favor of https://github.com/microsoft/PTVS/issues/5210


Loading NBT files is wasteful

In the current implementation, loading an NBT file implies creating a TAG_ object for every element in the file.  This can be very wasteful whenever we're only interested in the Blocks and Data arrays, since there can be a very large number of [Tile]Entities in any chunk, possibly with inventory substructures.
One place to work on this would be in the InfdevChunk class.  Instead of loading the entire NBT tree via nbt.loadFile, only pull out the Blocks, Data, Light, SkyLight and HeightMap arrays, and have a mechanism for loading everything else as needed.
Another approach is with a custom TAG class that's designed specifically for the root element of a chunk file. Like above, it would only break out the block arrays on load, and wait to create TAG_ elements for the rest of the file until they're needed.

Fixed with recent addition of _nbt.pyx


CD for jupysql

Changes

release job added to ci.yaml
flake8 and black added to the setup

How it works

release job is triggered only on the master branch with the following commit message: tag and release this version
This means we can trigger the release in 2 ways:

Commit PR merge to master with tag and release this version
Add an empty commit on master

release job uses pkgmt and runs 4 steps:

Installs all the needed packages to tag and release (pkgmt, wheel, and twine)
Sets git configuration (username : github-actions, email<EMAIL_ADDRESS>Bumps up version with pkgmt version
Releases to PyPI production with the new tag pkgmt release $TAG --production

Documentation
Where should this be documented?
A successfull release should look like this

A regular PR/commit should skip release

Closes: #23

:books: Documentation preview :books:: https://jupysql--104.org.readthedocs.build/en/104/

awesome, moving this to https://github.com/ploomber/dummy/issues/2 so we can test it there and iron out the details!


Detecting when a Saga started

Is there any way to detect when a saga has started?  I'm looking for a way to add a loading dialog for all async requests such that when a saga starts, the loading dialog displays and when it is finished the loading dialog stops.
Right now I'm placing yield put(actions.setLoading(true)) at the top of every saga which seems less than ideal.

Each saga effect actually emit events. For more details look in sagaMonitor implementation.

You can also simply create a saga to encapsulate the full logic
function* wrapSaga(saga, ...args) {
   yield put(setLoading(true))
   try {
    return yield call(saga, ...args)
   } finally {
      yield put(setLoading(false))
   }
}

// used with fork
yield fork(wrapSaga, myAsyncTask, somearg)

I ended up going with @yelouafi suggestion, thanks!


feat(client): add flags for automating auth:cancel

this fixes up those random /dev/ptmx errors we're finding in ci.deis.io every so often when piping manual I/O to auth:cancel.

I'm not sure what the issue is with the gexpect code, but this is simpler WRT the tests anyway. Code LGTM.

Code LGTM.

job 79 indicates that the error occurred while expecting "Account cancelled": https://github.com/deis/deis/blob/c9eb523c4899af094f1e3fb844c9b87e196526e2/tests/utils/itutils.go#L170-L173
Not sure what would cause this issue but it does seem to be something to do with gexpect... Maybe it's a race condition?
In either case this should solve it for auth:cancel ;)

@bacongobbler
PR issue:
Warning, treated as error:
/var/lib/jenkins/jobs/test-ec2/workspace@3/src/github.com/deis/deis/client/deis.py:docstring of client.deis.DeisClient.auth_cancel:10: WARNING: Option list ends without a blank line; unexpected unindent.

for some reason it didn't like -y --yes=false at the end so for the sake of getting this in I just removed the -y shortflag.

Still LGTM.

Code LGTM++.

Jenkins has blessed this PR!

:angel: thank you Jenkins :angel:


pull request for e2e test at 11/24/2016 17:56:08

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Propose a LICENSE file

@dims -- I've been using the tool recently and would like to contribute, but shouldn't without a LICENSE file.
Can I suggest Apache 2.0, given the current module name?
ref: https://github.com/dims/maintainers/issues/1

Done.


closure can't use property

namespace Example;

class Closure
{
  protected test;

  public function callback()
  {

      return function ()  {

          return this->test;

      };
  }
}

@dreamsxin Could you please take a look

@sergeyklay We need check that, it in the return expression and call Closure::bindTo to bound object.


[Birdnet-Go] Added Home Assistant Integration info

I documented how users can integrate the addon with Home Assistant.

Thanks very much for the great additions!


Some viewers can't display search results or new data notifications

Currently, viewers can be switched out (via the work done on the switchview branch), but not all viewers (or are guaranteed to) support the display of search results and new data notifications.

This is resolved by only using viewers that support these things


AdminSDHolder members Windows Server 2019 and Windows Server 2022

What about AdminSDHolder members for Windows Server 2019 and Windows Server 2022?
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d03c8028-a0b9-f28a-c795-85f03563b549
Version Independent ID: c1c8c10b-12e1-74fb-d824-10eeb924e73e
Content: Appendix C - Protected Accounts and Groups in Active Directory
Content Source: WindowsServerDocs/identity/ad-ds/plan/security-best-practices/Appendix-C--Protected-Accounts-and-Groups-in-Active-Directory.md
Product: windows-server
Technology: ad-ds
GitHub Login: @iainfoulds
Microsoft Alias: daveba

AdminSDHolder content exists in document and applies to line has been updated.


Check that enable_xcom_pickling is set to True

Check if AIRFLOW__CORE__ENABLE_XCOM_PICKLING is set to True else raise exception in __init__().

Codecov Report

Merging #446 (37757ce) into main (f0eae9a) will decrease coverage by 0.26%.
The diff coverage is 42.85%.

@@            Coverage Diff             @@
##             main     #446      +/-   ##
==========================================
- Coverage   93.16%   92.90%   -0.27%
==========================================
  Files          42       42
  Lines        1317     1324       +7
  Branches      169      170       +1
==========================================
+ Hits         1227     1230       +3
- Misses         69       72       +3
- Partials       21       22       +1

Impacted Files
Coverage Δ

src/astro/__init__.py
63.63% <42.85%> (-36.37%)
:arrow_down:

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 f0eae9a...37757ce. Read the comment docs.


Create an intro

Add an intro about yourself: who are you, what is your strength, why are you here.

Fully merged


chore: try add small optimizations to divide_polynomialcoeff

This adds three optimizations:

Replace .insert(0,x) with .append(x) and then a .reverse. Inserting at the first index on each loop causes every item in the list to be shifted down by one at each loop iteration.

return [x % BLS_MODULUS for x in o] to return o . The values of o should already be reduced since they are coming from the div function.

(a - b + modulus) becomes (a + (modulus - b)) - This mainly a nit, as the order of operations is not entirely clear.

This shaves off around 2 minutes from the 7594 tests (looked at other PRs to see how long they took compared to this)

Good points -- I'm happy to leave this open until there's consensus

This doesn't appear to be faster (compare the 1st and 3rd images). I think GitHub CI runs aren't always run on the same hardware and/or have less priority. The same run can vary by a few mins.

Click to see some CI runs

So I think we should close this PR, as the original code is easier to read.

Most of the changes have been superceded by changing to bls.Scalar it seems, so happy to close!


Setup : When on device with touch input, if user focus an input field, hide "Return to homepage" button

On phones, if the phone is in landscape and he tries to input something in one of the fiedls, the "Return to homepage" button gets in the field way.
Note that simply hiding on md bootstrap size won't work, as landscape on phone can also be md.
Some javascript will be required here.

Another possibility would simply to stick the button in the top left of the page, without it floating above the whole page even when scrolling down...
I'll test what feels better


Redhat 6.6

Missing redhat 6.6

Fauxhai is a community-based project and relies on community-supplied data. If you would like to submit this data to Fauxhai, please consult the README for instructions.


fetch value from db.json

how can i get values from multiple resource stored in db.json ?

very simple example to give you an idea
giving the following in db.json
{
  "posts": [
    { "title": "post title1", "comment": "post comment1" },
    { "title": "post title2", "comment": "post comment2" },
    { "title": "post title3", "comment": "post comment3" },
    { "title": "post title4", "comment": "post comment4" },
    { "title": "post title5", "comment": "post comment5" }
  ],
  "users": [
    { "name": "user1", "age": 21 },
    { "name": "user2", "age": 22 },
    { "name": "user3", "age": 23 },
    { "name": "user4", "age": 24 },
    { "name": "user5", "age": 25 }
  ],
  "comments": [
    { "id": 1, "content": "content 1" },
    { "id": 2, "content": "content 2" },
    { "id": 3, "content": "content 3" },
    { "id": 4, "content": "content 4" },
    { "id": 5, "content": "content 5" }
  ]

}

// server.js
var jsonServer = require('json-server')
var server = jsonServer.create()
var router = jsonServer.router('db.json')
var middlewares = jsonServer.defaults()

// create a custom middleware that looks for
// any request that has querystring `getall`
server.use(function(req, res, next) {
  if (req.query['getall']) {
    var resourcesArr = req.query['getall'].split(","),
      db = router.db, //lowdb instance
      allResources; //to store the aggregated resources

    allResources = resourcesArr.reduce(function(accumulator, resource) {
      accumulator[resource] = db.get(resource).value()
      return accumulator;
    }, {});
    res.json(allResources);
  } else {
  //proceed normally if no `getall` querystring
    next()
  }
})
server.use(middlewares)
server.use(router)

server.listen(3000, function() {
  console.log('JSON Server is running')
})

make a request like /?getall=posts,users
you will get
{
  "comments": [
    {
      "id": 1,
      "content": "content 1"
    },
    {
      "id": 2,
      "content": "content 2"
    },
    {
      "id": 3,
      "content": "content 3"
    },
    {
      "id": 4,
      "content": "content 4"
    },
    {
      "id": 5,
      "content": "content 5"
    }
  ],
  "users": [
    {
      "name": "user1",
      "age": 21
    },
    {
      "name": "user2",
      "age": 22
    },
    {
      "name": "user3",
      "age": 23
    },
    {
      "name": "user4",
      "age": 24
    },
    {
      "name": "user5",
      "age": 25
    }
  ]
}

router.db is an instance of lowdb
Please note that this is a very basic example to demonstrate the idea

Thanks @Nilegfx this example was a life saver. My js foo is weak and I tried to access router.db directly and it didn't work e.g. router.db.get

do you mean it still not working? if so, please post your code here.

Can we add router.db api to documentation?
For example I would like to know how to pass search params to db, if it allows.

Oh sorry my bad, I think it is using https://github.com/typicode/lowdb
Awesome package!


Add API.

Hello everyone,
I apologize for any inconvenience. This Pull Request was created by MISTAKE and has been closed. Please IGNORE it.


#1057 - Expanded plotting options of plot_posterior_predictive (clean version)

Description

The `plot_posterior_predictive' function has gotten new plotting options. Depending on the parameters, it can also show:
HDI (Highest Density Intervals) at 94% and 50% levels (as before)
Mean prediction line (new)
Gradient representation of the full posterior distribution (new)

The new function argument related to this are:
add_hdi : bool, optional - If True, add highest density intervals to the plot. Default is True.
add_mean : bool, optional - If True, add the mean prediction to the plot. Default is True.
add_gradient : bool, optional - If True, add a gradient representation of the full posterior distribution. Default is False.

A new example notebook is added to demonstrate: mmm_plotting_options.ipynb
Related Issue

[x] Closes #1057
[ ] Related to #

Checklist

[x] Checked that the pre-commit linting/style checks pass
[x] Included tests that prove the fix is effective or that the new feature works
[x] Added necessary documentation (docstrings and/or example notebooks)
[ ] If you are a pro: each commit corresponds to a relevant logical change

Modules affected

[x] MMM
[ ] CLV

Type of change

[x] New feature / enhancement
[ ] Bug fix
[ ] Documentation
[ ] Maintenance
[ ] Other (please specify):

📚 Documentation preview 📚: https://pymc-marketing--1066.org.readthedocs.build/en/1066/

Hi @jsnyde0 please let us know whenever this PR is ready for review :)

@juanitorduz oh sorry, yeah as far as I'm concerned it's ready!
The one thing I'm not sure about is that the mean is plotted in red by default. But the logic of the code should be ready.

@jsnyde0 What if we show these plotting options in the existing example notebook instead of this new addition which seems just explaining a very specific plotting function?

Sure, I'll get to that next Monday!
On Fri, 27 Sept 2024 at 17:06, Juan Orduz @.***> wrote:

@jsnyde0 https://github.com/jsnyde0 What if we show these plotting
options in the existing example notebook instead of this new addition which
seems just explaining a very specific plotting function?
—
Reply to this email directly, view it on GitHub
https://github.com/pymc-labs/pymc-marketing/pull/1066#issuecomment-2379490333,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACRXIYBT7QDBU62MHFSQPYTZYVX5RAVCNFSM6AAAAABOX3OFXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZZGQ4TAMZTGM
.


WebsocketClient syntax error prevents client from working

A syntax error was introduced here https://github.com/danpaquin/coinbasepro-python/pull/381/files#diff-57a4208fce375ee0b398b308ead6930aR33
This results in the test suite failing as well as prevents the client from working
============================================================================================================ test session starts =============================================================================================================
platform linux2 -- Python 2.7.17, pytest-4.6.9, py-1.8.1, pluggy-0.13.1
rootdir: /home/peterzal/coinbasepro-python
collected 0 items / 2 errors

=================================================================================================================== ERRORS ===================================================================================================================
____________________________________________________________________________________________ ERROR collecting tests/test_authenticated_client.py _____________________________________________________________________________________________
../.local/lib/python2.7/site-packages/_pytest/python.py:507: in _importtestmodule
    mod = self.fspath.pyimport(ensuresyspath=importmode)
../.local/lib/python2.7/site-packages/py/_path/local.py:701: in pyimport
    __import__(modname)
../.local/lib/python2.7/site-packages/_pytest/assertion/rewrite.py:304: in load_module
    exec(co, mod.__dict__)
tests/test_authenticated_client.py:5: in <module>
    from cbpro.authenticated_client import AuthenticatedClient
cbpro/__init__.py:3: in <module>
    from cbpro.websocket_client import WebsocketClient
E     File "cbpro/websocket_client.py", line 33
E       *,
E        ^
E   SyntaxError: invalid syntax
________________________________________________________________________________________________ ERROR collecting tests/test_public_client.py ________________________________________________________________________________________________
../.local/lib/python2.7/site-packages/_pytest/python.py:507: in _importtestmodule
    mod = self.fspath.pyimport(ensuresyspath=importmode)
../.local/lib/python2.7/site-packages/py/_path/local.py:701: in pyimport
    __import__(modname)
../.local/lib/python2.7/site-packages/_pytest/assertion/rewrite.py:304: in load_module
    exec(co, mod.__dict__)
tests/test_public_client.py:6: in <module>
    from cbpro.public_client import PublicClient
cbpro/__init__.py:3: in <module>
    from cbpro.websocket_client import WebsocketClient
E     File "cbpro/websocket_client.py", line 33
E       *,
E        ^
E   SyntaxError: invalid syntax
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 2 errors during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
========================================================================================================== 2 error in 0.31 seconds ===========================================================================================================

So from the comments of this commit, it looks like this idea was based on PEP3102, which requires Python 3. Python 2 has been officially unsupported by the PSF for a while now. Are we still attempting to maintain Python 2 compatibility?

Issue confirmed:  This code does not run on Python 2.7, but does run on Python 3.6.

Issue confirmed:  This code does not run on Python 2.7, but does run on Python 3.6.

There are a TON of people locked to Python2.7 still. Argh


fix detection of whether -LiteralPath was used to suppress wildcardexpansion for navigation cmdlets

Fix https://github.com/PowerShell/PowerShell/issues/5031

@SteveL-MSFT The test 'Remove-Item -LiteralPath should succeed for file with asterisk in name' is failing. Please fix.

@adityapatwardhan I only ran it on my Mac, I need to skip it on Windows since asterisk isn't allowed in filename

@SteveL-MSFT  Please add the test as described in the issue #5031. That should work on Windows as well.

@adityapatwardhan added more test variations for the wildcard not finding files scenario


code

where is the code？

where is the code？

Hi smile-yc. Thanks for your question and interest in our code. Sorry for the inconvenience. We are working on the code release process right now. Hopefully, we can have everything ready ASAP.
Please leave your contact information, we will send you an email once the code is ready.

where is the code？

Hi smile-yc,
Our code is ready now. Please let me know if you have more questions.
Kaiqiang


Foyer installation details. Docker file is up to date?

Hello!
Is the Docker file in the repo up to date or is this one that shall be used?
Do I understand it correct that the installation of foyer is done via the following two commands :
mamba env create --file environment-dev.yml &&
conda activate foyer-dev &&

and not via git clone of this github repository and the following pip command? So, the installation works simply because foyer is in the dependencies list of mbuild and gmso that are in turn in the dependencies list of foyer and all the three packages are installed from conda-forge channel, correct?
P.S. Check the dependencies file environment-dev.yml of foyer. There is gmso written twice.

I'll have to take a closer look at the Docker file to answer that question.
But, there are multiple ways to install foyer.

Install from anaconda

mamba create -n foyer -c conda-forge foyer

This will make a new conda environment and install the latest release of foyer along with all the dependencies needed to use it. For most use cases, this will be all you need to do. But also, as you mention, if you install gmso from anaconda you'll get foyer as well.
Or you can install foyer into an existing conda environment you're already using
mamba activate your-environment
mamba install -c conda-forge foyer

Install from source

Installing from source is helpful if you need to use some functionality that has been merged in, but not yet released, or if you want to modify foyer's code yourself and run it. In this case you'll use the .yml file in this repo, then use pip to install from either this cloned repo, or your fork.
mamba env create -f environment-dev.yml
mamba activate foyer-dev
pip install -e .

Technically, creating the environment from the .yml will also install foyer, since gmso is listed as a dependency, but typically, the idea of using these .yml files is to then install from source. Otherwise, you might as well just install directly from anaconda.

Dear @chrisjonesBSU ,
thanks for your reply and for the installation instructions recall.
The Dockerfile that I got from here ( otherwise, look for the latest tag here ), looks approximately like the following :
ADD file:f278386b0cef68136129f5f58c52445590a417b624d62bca158d4dc926c340df in /

CMD ["/bin/sh"]

LABEL maintainer=Vlad Frolov

LABEL src=https://github.com/frol/docker-alpine-glibc

ENV LANG=C.UTF-8 LC_ALL=C.UTF-8

SHELL [/bin/ash -eo pipefail -c]

RUN /bin/ash -eo pipefail -c ALPINE_GLIBC_BASE_URL="https://github.com/sgerrand/alpine-pkg-glibc/releases/download" &&
  ALPINE_GLIBC_PACKAGE_VERSION="2.33-r0" &&
  ALPINE_GLIBC_BASE_PACKAGE_FILENAME="glibc-$ALPINE_GLIBC_PACKAGE_VERSION.apk" &&
  ALPINE_GLIBC_BIN_PACKAGE_FILENAME="glibc-bin-$ALPINE_GLIBC_PACKAGE_VERSION.apk" &&
  ALPINE_GLIBC_I18N_PACKAGE_FILENAME="glibc-i18n-$ALPINE_GLIBC_PACKAGE_VERSION.apk" &&
  apk add -q --no-cache --virtual=.build-dependencies wget ca-certificates &&
  echo "-----BEGIN PUBLIC KEY-----        MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApZ2u1KJKUu/fW4A25y9m        y70AGEa/J3Wi5ibNVGNn1gT1r0VfgeWd0pUybS4UmcHdiNzxJPgoWQhV2SSW1JYu        tOqKZF5QSN6X937PTUpNBjUvLtTQ1ve1fp39uf/lEXPpFpOPL88LKnDBgbh7wkCp        m2KzLVGChf83MS0ShL6G9EQIAUxLm99VpgRjwqTQ/KfzGtpke1wqws4au0Ab4qPY        KXvMLSPLUp7cfulWvhmZSegr5AdhNw5KNizPqCJT8ZrGvgHypXyiFvvAH5YRtSsc        Zvo9GI2e2MaZyo9/lvb+LbLEJZKEQckqRj4P26gmASrZEPStwc+yqy1ShHLA0j6m        1QIDAQAB        -----END PUBLIC KEY-----" | sed 's/   */\n/g' > "/etc/apk/keys/sgerrand.rsa.pub" &&
  wget -q "$ALPINE_GLIBC_BASE_URL/$ALPINE_GLIBC_PACKAGE_VERSION/$ALPINE_GLIBC_BASE_PACKAGE_FILENAME" "$ALPINE_GLIBC_BASE_URL/$ALPINE_GLIBC_PACKAGE_VERSION/$ALPINE_GLIBC_BIN_PACKAGE_FILENAME" "$ALPINE_GLIBC_BASE_URL/$ALPINE_GLIBC_PACKAGE_VERSION/$ALPINE_GLIBC_I18N_PACKAGE_FILENAME" &&
  apk add -q --no-cache "$ALPINE_GLIBC_BASE_PACKAGE_FILENAME" "$ALPINE_GLIBC_BIN_PACKAGE_FILENAME" "$ALPINE_GLIBC_I18N_PACKAGE_FILENAME" &&
  rm "/etc/apk/keys/sgerrand.rsa.pub" &&
  /usr/glibc-compat/bin/localedef --force --inputfile POSIX --charmap UTF-8 "$LANG" || true &&
  echo "export LANG=$LANG" > /etc/profile.d/locale.sh &&
  apk del -q glibc-i18n &&
  rm "/root/.wget-hsts" &&
  apk del -q .build-dependencies &&
  rm "$ALPINE_GLIBC_BASE_PACKAGE_FILENAME" "$ALPINE_GLIBC_BIN_PACKAGE_FILENAME" "$ALPINE_GLIBC_I18N_PACKAGE_FILENAME" # buildkit

LABEL maintainer=Anaconda, Inc

ENV PATH=/opt/conda/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

ARG CONDA_VERSION=py39_4.10.3

ARG SHA256SUM=1ea2f885b4dbc3098662845560bc64271eb17085387a70c2ba3f29fff6f8d52f

RUN |2 CONDA_VERSION=py39_4.10.3 SHA256SUM=1ea2f885b4dbc3098662845560bc64271eb17085387a70c2ba3f29fff6f8d52f /bin/ash -eo pipefail -c apk add -q --no-cache bash procps &&
  wget --quiet https://repo.anaconda.com/miniconda/Miniconda3-${CONDA_VERSION}-Linux-x86_64.sh -O miniconda.sh &&
  echo "${SHA256SUM}  miniconda.sh" > miniconda.sha256 &&
  if ! sha256sum -cs miniconda.sha256; then exit 1; fi &&
  mkdir -p /opt &&
  sh miniconda.sh -b -p /opt/conda &&
  rm miniconda.sh miniconda.sha256 &&
  ln -s /opt/conda/etc/profile.d/conda.sh /etc/profile.d/conda.sh &&
  echo ". /opt/conda/etc/profile.d/conda.sh" >> ~/.bashrc &&
  echo "conda activate base" >> ~/.bashrc &&
  find /opt/conda/ -follow -type f -name '*.a' -delete &&
  find /opt/conda/ -follow -type f -name '*.js.map' -delete &&
  /opt/conda/bin/conda clean -afy # buildkit

CMD ["/bin/bash"]

EXPOSE map[8888/tcp:{}]

LABEL maintainer.name=mosdef-hub maintainer.url=https://mosdef.org

ENV PATH=/opt/micromamba/bin:/opt/conda/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

USER root

ADD . /foyer # buildkit

WORKDIR /foyer

RUN /bin/ash -eo pipefail -c addgroup -S anaconda && adduser -S anaconda -G anaconda # buildkit

RUN /bin/ash -eo pipefail -c apk update && apk add libarchive &&
  conda update conda -yq &&
  conda config --set always_yes yes --set changeps1 no &&
  . /opt/conda/etc/profile.d/conda.sh &&
  sed -i -E "s/python.*$/python="$(PY_VERSION)"/" environment.yml &&
  conda install -c conda-forge mamba &&
  mamba env create --file environment-dev.yml &&
  conda activate foyer-dev &&
  mamba install -c conda-forge jupyter python="$PY_VERSION" &&
  python setup.py install &&
  echo "source activate foyer-dev" >> /home/anaconda/.profile &&
  conda clean -afy &&
  mkdir -p /home/anaconda/data &&
  chown -R anaconda:anaconda /foyer &&
  chown -R anaconda:anaconda /opt &&
  chown -R anaconda:anaconda /home/anaconda # buildkit

WORKDIR /home/anaconda

COPY devtools/docker-entrypoint.sh /entrypoint.sh # buildkit

RUN /bin/ash -eo pipefail -c chmod a+x /entrypoint.sh # buildkit

USER anaconda

ENTRYPOINT ["/entrypoint.sh"]

CMD ["jupyter"]

It's clearly different from the one in this repo and I think it's confusing whether this installation follows p. 1 or 2 of your installation instructions above. For me, it looks like a mixture of both with some necessary commands missing, e.g. I see no git clone that copies foyer repo.
Perhaps, you may want to clarify the connection between foyer, mbuild and gmso, i.e. what depends on what and what requires what? Do I understand it correct that foyer requires mbuild, whereas foyer itself is required by gmso?

@chrisjonesBSU , forgot to add the following last time.
I'm creating Singularity container with the whole MoSDeF infrastructure [ based on my own base conda image ] and thus I'm following your installation variant 2. Consequently, in my Singularity definition file [ these files are equivalent to the Docker files ] , I have the following instructions :
export APP="mosdef"
git clone https://github.com/mosdef-hub/foyer.git
. /opt/conda/etc/profile.d/conda.sh
conda env create -f ./environment_${APP}.yml
conda activate ${APP}
pip install -e foyer

where the environment_${APP}.yml file is basically the compilation of the development versions of the environmetal files of foyer, mbuild, gmso :
name: mosdef
channels:
  - conda-forge
  - omnia
dependencies:
  - boltons
  - bump2version
  - codecov
  - ele >= 0.2.0
  - forcefield-utilities >= 0.2.1
  - gmso
  - importlib_resources
  - lark
  - lxml
  - mbuild >= 0.17
  - networkx >= 2.5
  - numpy = 1.26.4
  - openff-toolkit >= 0.11
  - openmm
  - parmed >= 3.4.3
  - pip
  - pre-commit
  - pydantic >= 2
  - pytest
  - pytest-azurepipelines
  - pytest-cov
  - python-symengine
  - pytest-timeout
  - pytest-xdist
  - python >= 3.9, <= 3.12
  - requests
  - requests-mock
  - scipy
  - symengine
  - sympy
  - treelib
#  - unyt >= 3.0.3

unyt is commented out, since it leads to the following error upon the call of import foyer :
Traceback (most recent call last):
  File "/femshare/azure/md/apps/mosdef/test_new.py", line 4, in <module>
    import foyer, mbuild, parmed, gmso
  File "/foyer/foyer/__init__.py", line 3, in <module>
    from foyer.forcefield import Forcefield
  File "/foyer/foyer/forcefield.py", line 38, in <module>
    from foyer.atomtyper import find_atomtypes
  File "/foyer/foyer/atomtyper.py", line 7, in <module>
    from gmso import Topology
  File "/opt/conda/envs/mosdef/lib/python3.12/site-packages/gmso/__init__.py", line 2, in <module>
    from .core.angle import Angle
  File "/opt/conda/envs/mosdef/lib/python3.12/site-packages/gmso/core/angle.py", line 6, in <module>
    from gmso.abc.abstract_connection import Connection
  File "/opt/conda/envs/mosdef/lib/python3.12/site-packages/gmso/abc/abstract_connection.py", line 5, in <module>
    from gmso.abc.abstract_site import Site
  File "/opt/conda/envs/mosdef/lib/python3.12/site-packages/gmso/abc/abstract_site.py", line 10, in <module>
    from gmso.abc.gmso_base import GMSOBase
  File "/opt/conda/envs/mosdef/lib/python3.12/site-packages/gmso/abc/gmso_base.py", line 8, in <module>
    from pydantic.validators import dict_validator
ImportError: cannot import name 'dict_validator' from 'pydantic.validators' (/opt/conda/envs/mosdef/lib/python3.12/site-packages/pydantic/validators.py)

The reason for this I need all three mbuild, foyer, gmso to be able to, respectively, create a file with coordinates from SMILES sequence, apply a force field to a created molecule, and convert GROMACS top and gro files into those ones compatible with LAMMPS, NAMD, etc., and to be able to install foyer from the source. However, since I'm not that strong with technical details of conda / mamba, especially environment creature, etc., and since I'm not aware about the exact dependencies list of mbuild, foyer, gmso each [ there are regular and development versions of the yml dependencies files in their guthub repositories, and this is confusing ] , I simply merged the development versions of their dependencies lists into a single one.
I'm pretty sure I'm doing some excessive things in my installation routine, but I'm not sure which ones to exclude. And the reason why I was looking into your Dockerfile was to understand how exactly you install mbuild, foyer, gmso and why your Docker container was working, whereas mine wasn't.

If you just need the mosdef software stack and are working with your own base image, it seems like the route to go would be to install all 3 packages from anaconda rather than using the environment.yml files in each of the 3 repos, and installing from source.
conda create -n mosdef -c conda-forge mbuild gmso foyer

This should handle all of the dependencies for you.

@chrisjonesBSU , thanks for the short and yet clear explanation to my insanely long stream of words and I'm retrospectively sorry for the latter :)

@chrisjonesBSU , thanks for the short and yet clear explanation to my insanely long stream of words and I'm retrospectively sorry for the latter :)

No worries! I'm happy to help.
I can understand the confusion, so just to clarify, all 3 of the foyer, mbuild and GMSO repos have their own environment-dev.yml files, but the point of these files is to create a development and testing environment for that specific package, not for the mosdef software stack as a whole. Also, with anaconda, you can install a package from source after the fact, even if that package is already in your conda environment (e.g. it was installed as a dependency from another package).

Thanks! Now, it has become even clearer!
Still, I have a few Qs remained :

the Dockerfile in the foyer is outdated, is it not?
what is the most up-to-date version of, let's say, foyer? is it the one in conda repo or the one in github repo, or are those both synchronised between each other? namely, installation via conda install and via git clone <foyer repo> + pip install give the same version?

Best, @iGulitch

The versions of foyer available on conda coincide with the release which you can find here, so we did a foyer release 2 days ago, which is essentially a snapshot of the repo as it existed then. The last release before that was in January, so the January release on conda did not have anything that was merged between January and now. So, the GitHub repo is always the most up-to-date, but only by whatever has been committed since the last release. Pretty much all the commits since January have been maintenance and CI related, so there really isn't a big difference between foyer version 0.12.1 and the current GitHub repo.  Foyer isn't currently undergoing active changes.
From looking at the Docker file, it seems up-to-date and fine from what I can tell. I haven't tried testing it out yet though.


Add options for skani sketching/searching, in particular for marker k-mer compression factor.

Still not super flexible - but have added an option in zol to use skani's new --small-genomes preset. If there is desire for this option, please open a new issue or re-open this one.


Rename "trackingConfig" intro "trackingGroups"

This parameter is used to configure group of files being tracked. In that sense "trackingGroups" feels like a better name.

This is a breaking change so it will certainly wait


Add description to the call and extract it from the canvas (#5514)

Pull request opened by the merge tool on behalf of #5514

Merged in dfc04efa88f007e1f789ad1c950684975e8839c8


[Automation] Generate SDK based on TypeSpec

[Automation] Generate SDK based on TypeSpec

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-openai

@jpalvarezl @srnagar
Java may need to change the scope of @include from openai client.tsp
https://github.com/Azure/azure-rest-api-specs/blob/db23874c147db173933476b3b352cbf12abe84a9/specification/cognitiveservices/OpenAI.Inference/client.tsp#L12-L14
Appears we don't want to have at least some of these model generated. ImageGenerations even contains a Union.


Export all npm files, and source for react-native

This allows all files to come with the npm package, and points Metro to the source code so that it can provide source maps for consumption in react-native apps.

@ericvicenti - do you want to update this like you did for the other navigator repos?


some further README.md polish

Summary of changes

added some anim.gifs for j26 jumper and DAPLink mode.
added inline notes for some of the troubleshooting issues.

@maclobdell mind to review.

[X] I confirm this contribution is my own and I agree to license it with Apache 2.0.
[X] I confirm the moderators may change the PR before merging it in.
For new board enablements only:
[] I confirm the board is Mbed Enabled and passes the Mbed Enabled test set.
[] I confirm the contribution has been tested properly and the tests results for TESTS are attached.
[] I confirm mbed-os.lib and mbed-cloud-client.lib hashes or the content in folders mbed-os and mbed-cloud-client were not modified in order to pass the tests.

Maintainers of this repository update the Mbed OS and Client hashes.
Please report any issues through issues in relevant repositories.

looks good to me!


Validate Metaschema

This PR adds metaschema file validation to the OCSF validation tool.

I reused InvalidMetaSchemaError for when the JSON schema file flags an issue with OCSF schemas.
I created a new InvalidMetaSchemaFileError, used when a metaschema file itself has errors.

I tried matching the patterns I saw in the repository as best I could, let me know how I can improve it.
Part of https://github.com/ocsf/ocsf-schema/issues/735

My timings are 0.29s without and 5.83s with. That may matter later on public GitHub runners, but I say we add it for now and see if it causes problems :)

I noticed this as well.  It's possible there are other options, like https://github.com/horejsek/python-fastjsonschema that might perform better.


jinja2 <4 support

3.0.x is out

Hi @fgaz. I'm not sure what you are looking for here. I think staticjinja should be compatible with both jinja 2.x and 3.x. If you want to use jinja 3.x in your project, go ahead and do that, I don't think you should have any problem. Have you encountered a problem when using jinja 3.x?

I may be mistaken, but doesn't this line mean that only jinja2 < 3 is supported?
https://github.com/staticjinja/staticjinja/blob/dcfcaf88f02e2e9494fcc64bfa25e36ea53a46f2/pyproject.toml#L38

Oops I didn't understand the caret modifier. Indeed, you're right. I think the solution is to change the caret to a >. I'll double check that this doesn't have any unintended consequences.

>= 2.10.1, < 4 is also ok and signals that jinja 4 is not yet supported (since it does not exist yet and it isn't kn own if it'll break staticjinja). not sure if upper version bounds are common in the python ecosystem.

This gives a good reason why you should specify an upper bound. https://python-poetry.org/docs/faq/#why-are-unbound-version-constraints-a-bad-idea
Your suggestion above is I think what we want. That PR contains that


[azservicebus] Adding in support for embedded SharedAccessSignatures in connection strings

Adding support for parity with other Service Bus libraries allow you pass a connection string with a SharedAccessSignature, rather than an embedded SharedKey.
Fixes #16641

/azp run go - azservicebus


why the gwp-asan stack frame only address pointer

How can I get the code backtrace?
This is some test result.
[  DEATH   ] tcmalloc/guarded_page_allocator.cc:488] *** GWP-ASan (https://google.github.io/tcmalloc/gwp-asan.html)  ha
s detected a memory error ***
[  DEATH   ] tcmalloc/guarded_page_allocator.cc:492] >>> Access at offset 0 into buffer of length 3
[  DEATH   ] tcmalloc/guarded_page_allocator.cc:494] Error originates from memory allocated in thread 27 at:
[  DEATH   ] tcmalloc/guarded_page_allocator.cc:460]   @   0x55b7c96f7c3f
[  DEATH   ] tcmalloc/guarded_page_allocator.cc:460]   @   0x55b7c96e4008
[  DEATH   ] tcmalloc/guarded_page_allocator.cc:460]   @   0x55b7c97a507e
[  DEATH   ] tcmalloc/guarded_page_allocator.cc:460]   @   0x55b7c96cb9d6
[  DEATH   ] tcmalloc/guarded_page_allocator.cc:460]   @   0x7fbdea933ea4
[  DEATH   ] tcmalloc/guarded_page_allocator.cc:460]   @   0x7fbdea92e059
[  DEATH   ] tcmalloc/guarded_page_allocator.cc:460]   @   0x7fbdea90ef20
[  DEATH   ] tcmalloc/guarded_page_allocator.cc:460]   @   0x7fbdea90f9ae
[  DEATH   ] tcmalloc/guarded_page_allocator.cc:460]   @   0x7fbdea91035f
[  DEATH   ] tcmalloc/guarded_page_allocator.cc:460]   @   0x7fbdea92019d
[  DEATH   ] tcmalloc/guarded_page_allocator.cc:460]   @   0x7fbdea934e82
[  DEATH   ] tcmalloc/guarded_page_allocator.cc:460]   @   0x7fbdea92f2bb
[  DEATH   ] tcmalloc/guarded_page_allocator.cc:460]   @   0x7fbdea91e835
[  DEATH   ] tcmalloc/guarded_page_allocator.cc:460]   @   0x7fbdea986af8
[  DEATH   ] tcmalloc/guarded_page_allocator.cc:460]   @   0x7fbdea986a7a
[  DEATH   ] tcmalloc/guarded_page_allocator.cc:460]   @   0x7fbde9f73083

Is the program built with debug symbols?

Is the program built with debug symbols?

hi, I have the same question. My compilation instrution is

bazel build --compilation_mode=dbg  --config=asan-libfuzzer tcmalloc/testing:memory_errors_test

Thanks for your help :)


[Bug]: Android splash screen header/footer

Describe the bug
The top and bottom colors for the splash screen (and the home screen after) are inconsistent. It should be all orange and then all black.
Reproduce

Launch app
The top of the screen is black (should be orange)
Sometimes after the splash screen the bottom stays orange

Screenshots / Recording
I don't have screenshots right now.
Operating system
Android (on device)
Bitkit version
master
Log output
No response

Verified in v118


Update Port 25 to address Azure Firewall

Update Port 25 to address Azure Firewall

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

@anavinahar @davegoddard FYI

@ryanborMSFT  Thanks for the suggestion.
#sign-off

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


Add news filter

We need a tag filter so that it's easier to find articles in the future

Can we elaborate more about this?
Is this feature work just like a blog that you click on tag and list items with same tag?

@opdev1004 these are the chips on top of the news articles

#79


Fix JSON formatting

Problem:

The JSON content of some of the config files and the README is not formatted correctly.

Solution:

Make sure that the JSON content is properly formatted.

Fixed in the following PR:

https://github.com/geniusyield/smart-order-router/issues/10


Remove unused variable _maxScanLineSize from B44Compressor

This is a follow up to a closed PR.
It was recommended to add a comment that this should be cleaned up, once its safe to break the ABI
WARNING: Breaks the ABI!

Since our last release was 3.1.7 and the next is 3.2.0, I think now would be a good time to do this? ie, remove _maxScanLineSize. If there's no objections, let's move ahead with the removal.


About char ✓ 's question

Saying directly, l find you can't input '✓' and save in atom
You can input this code to try about it.
#include <stdio.h> int main(void) {         printf("✓");         return 0; }
if you input this in atom, you can find that you can't save.
if you click "save as", when you turn into the file again, you can find that the '✓' and below's content isn't load.

Thank you for reaching out!
Because this doesn't reproduce in Safe Mode, it would seem that what you're reporting isn't being caused by Atom itself but by a community package you have installed. It may be that there is still a bug in Atom. If so, we'll need the maintainer of the package that is causing the problem to help track that down.
What we need you to do is to figure out what community package is causing the problem. Some people have reported that using the package-cop package has been helpful, you may want to try it. Once you've determined what package is causing the problem, The Atom FAQ has information on how to contact the maintainers of any Atom community package or theme so you can file this issue there.


Feature: Alternative config file type

We should consider switching to, or at least providing the option to use a standardized file format for biome and object configuration  files. This would allow us to reduce the size of configuration files, provide easier parsing with an external API such as SnakeYAML, and allow for easy integration with programs such as visual studio code and online parsers.
YAML or TOML would be good options for this.
SnakeYAML: https://bitbucket.org/asomov/snakeyaml/src/master/

I vote for YAML.

Most important ofc would be to ask the people actually using the configs on a regular basis.
Here's what the current configs can do btw, that a new implementation should also support:

Default/Min/Max values for settings.
Allow settings missing from file, use configured default values if missing. Missing int settings should not default to 0 (zero), etc.
Comments
Allow all value types and syntaxes, without the need for manual escaping of characters.

For YAML:

Here's what the current configs can do btw, that a new implementation should also support:
* Default/Min/Max values for settings.

This is currently done in the code anyway.

* Allow settings missing from file, use per-setting default values if missing. Missing int settings should not default to 0 (zero), etc.

This is currently done in the code anyway.

* Backwards compatibility for older versions/formats (read old format, write new format).

Shouldn't be an issue, and I haven't seen any breaking changes in YAML for a long time

* Comments.

Modern SnakeYML supports comments

* Allow all value types and syntaxes, without the need for manual escaping of characters.

Should be possible? " and ' may need escaping.

For my part, I'd highly recommend that whatever language you/we use, you use an OTG-specific file extension.  Not sure what the best value would be to use for this -- we've got BO3, BO4, and BC currently. Google says OTG is already taken by a different standard, so probably not free real estate there.

@Coll1234567 If yaml just deserializes classes like xml, json etc, just reading files direclty into classes, then you won't be able to do:

Default/Min/Max values for settings.
Allow settings missing from file, use per-setting default values if missing. Missing int settings should not default to 0 (zero), etc.

Things like ints will be automatically coerced to zero when missing, but that should also be an allowed value, and not assumed to be the default. We need to be able to recognise settings that are missing from the file entirely.

Backwards compatibility for older versions/formats (read old format, write new format).

If you're using deserialisation, you can't do this, unless you maintain classes that represent every previous version of the format as well, or are prepared to include in one class every setting and format we've ever supported (which will then also be written back ofc).

Allow all value types and syntaxes, without the need for manual escaping of characters.

Any string has to be encased in "" (not needed currently), any quotes or reserved characters inside will need to be escaped, though I suppose we rarely use those for any settings.

To me this seems a little unnecessary, especially as everyone is just going to be using the old types of files.
Plus it'll be a cold day in heck before community tools like bo3_bulkedit will support it.
Just seems like a waste of effort. We've had our own special way of doing things since Buycruss and it works so why fix it?


Use of uninitialized memory of trailer list

Description
The use of uninitialized memory of the trailer array is found in function cups_fill of cups/file.c. Detailed code can be found below:
unsigned char	trailer[8];	// Trailer bytes
uLong		tcrc;		// Trailer CRC
ssize_t		tbytes = 0;	// Number of bytes

if (fp->stream.avail_in > 0)
{
  if (fp->stream.avail_in > sizeof(trailer))
    tbytes = (ssize_t)sizeof(trailer);
  else
    tbytes = (ssize_t)fp->stream.avail_in;

  memcpy(trailer, fp->stream.next_in, (size_t)tbytes);
  fp->stream.next_in  += tbytes;
  fp->stream.avail_in -= (size_t)tbytes;
}

      if (tbytes < (ssize_t)sizeof(trailer))
{
  if (read(fp->fd, trailer + tbytes, sizeof(trailer) - (size_t)tbytes) < ((ssize_t)sizeof(trailer) - tbytes))
  {
...
  }
}

tcrc = ((((((uLong)trailer[3] << 8) | (uLong)trailer[2]) << 8) | (uLong)trailer[1]) << 8) | (uLong)trailer[0];

if (tcrc != fp->crc)
{
...

when vail_in is less than sizeof(trailer), the operation memcpy(trailer, fp->stream.next_in, (size_t)tbytes); will end up with uninitialized value in trailer array. The subsequent function if (read(fp->fd, trailer + tbytes, sizeof(trailer) - (size_t)tbytes) < ((ssize_t)sizeof(trailer) - tbytes)) may also inroduce unitialized value issue when read() function returns EOF or error.
Suggested Fix

Initialize trailer with zero e.g., unsigned char trailer[8] = {0};
Handle read() error

Postscript
The issue is identified by OSS-Fuzz harness fuzzipp with MSAN. Here is the linked issue.

OK, the code handles read errors - if we get less than "sizeof(trailer) - tbytes" bytes, that is an error and we abort.
I think the issue is that this and the CRC failure don't call inflateEnd.
Test this change:
[master 83562f7c7] Make sure we call inflateEnd when there is an error reading or comparing the stream CRC (Issue #91)


[FeatureRequest] Confirm dialog after press Enter

Keyboard button "Esc" closes dialog just like the "false" button does.
Keyboard button "Enter" does nothing, but it must act (optionally) like the "true" button.

Use it in version 2.0.1


az ml workspace create throws InvalidRequestContent error

Extension name (the extension in question)
azure-cli-ml

Using Azure CLI version 2.4.0...
Using Azure CLI ML extension version 1.3.0...

Description of issue (in as much detail as possible)
When running az ml workspace create --workspace-name anyname -g anyresourcegroup I get the following error message:
Unable to create the workspace.
 Azure Error: InvalidRequestContent
Message: The request content was invalid and could not be deserialized: 'Could not find member 'template' on object of type 'DeploymentDefinition'. Path 'template', line 1, position 12.'.
WorkspaceException:
	Message: Unable to create the workspace. The request content was invalid and could not be deserialized: 'Could not find member 'template' on object of type 'DeploymentDefinition'. Path 'template', line 1, position 12.'.
	InnerException Azure Error: InvalidRequestContent
Message: The request content was invalid and could not be deserialized: 'Could not find member 'template' on object of type 'DeploymentDefinition'. Path 'template', line 1, position 12.'.
	ErrorResponse
{
    "error": {
        "message": "Unable to create the workspace. The request content was invalid and could not be deserialized: 'Could not find member 'template' on object of type 'DeploymentDefinition'. Path 'template', line 1, position 12.'."
    }
}

The same command works fine with an older Azure CLI version, just tested and working fine in 2.1.0.

ml

I saw precisely the same error using the same Az CLI and azure-cli-ml extension. Updating azure-cl-ml from 1.3.0 to 1.4.0 fixed the problem and the workspace deployed correctly.


[Feature Request] Dataclasses as commands

Given some existing config dataclass, I would like to parse arguments to create the config.
Example:

import sys

from cyclopts import App

@dataclass
class MyConfig:
    a: int = 1
    b: int = 2

config = object.__new__(MyConfig)

app = App()
app.default(config.__init__)

sys.argv = [__file__,  "--a", "3", "--b", "4"]
app()
print(config)

MyConfig(a=3, b=4)
This already works as is, but I was wondering if a prettier solution already exists, either currently working or planned for version 3?
Generally, I would prefer defining a CLI around dataclasses rather than function implementations (one reason being that it's easier to extend something based on classes using inheritance).
I assume someone else has already thought about this, so before I start reinventing the wheel, I thought I should ask here.
Thanks for the great work, really like it so far  👍

ok, the positional arguments should now work on dev-3.0.0. The example provided above now fully works as expected.

v3.0.0 has been released! Please let me know if you run into any issues, thanks!


Use ColumnarBatch instead of BatchColumn & enable returnBatch#789

What changes were proposed in this pull request?
Delete SingleGroupOapRecordReader
Modify function 'def cache' which loads one column data of one group into cache.
Modify function 'private def buildColumnarBatchFromCache' which constructs a ColumnarBatch from cache data.
How was this patch tested?
All exists test cases passed.
Add a new test case in FilterSuite.
filtering parquet in FiberCache with partition.

Let's holding this PR for one more day to see if anyone else has interest.

Thanks @songzhan01 , this generally LGTM except a few comments

@gczsjdy , could you help merge this PR after the PR is good to you?
seems there still is some work to do.
It'll be great if we can merge this by today.

Thanks @linhong-intel @songzhan01 @LuciferYang !

thx @songzhan01 @gczsjdy @linhong-intel ~


migrations: Remove disallowed characters from topics.

Following b3c58f454f0dce8a88c696305945bac41f9786bc, we want to clean up
old topics that may contain the disallowed characters. The Message table
is large, so we go in batches, making sure we limit topic fetches and
UPDATE query to no more than BATCH_SIZE Message rows per query.

It seemed tempting to try to limit the number of topics processed per batch, rather than going by Message id ranges, but it complicates reasoning about the logic (huge UPDATE if the topic is super large for example, the fact that the ordering of topics can change as a result of removing some characters from a topic etc.)

Thanks! See my question about using "(no topic)" for topics that would otherwise be "", at https://chat.zulip.org/#narrow/stream/141-kandra-ops/topic/Special.20characters.20in.20topics/near/1294838.

Renamed the migration and added the extra if:
                if fixed_topic == topic:
                    continue

                if fixed_topic == "":
                    fixed_topic = "(no topic)"

This is great; I added a bit more of our standard progress logging, test-deployed it on chat.zulip.org (fixing 63 messages, apparently) and merged this. Thanks @mateuszmandera!


Move PHPStan to it's own action & bump the scanning level

This PR moves PHPStan to it's own action, with the latest version of PHP.
It also increases the scanning level from 0 to 1 which adds scanning for the following:
possibly undefined variables, unknown magic methods and properties on classes with __call and __get
Also fixes a handful of the potential issues it caught with the new level

fyi, the only failing test is because of a 'TODO' comment I added to the code


Vaccination Endpoint returning error

since today the following error is returned:
{"error":{"message":"An error occurred.","details":"Cannot read properties of undefined (reading 'state')","stack":"TypeError: Cannot read properties of undefined (reading 'state')\n    at /workspace/src/data-requests/vaccination.ts:323:15\n    at Generator.next (<anonymous>)\n    at fulfilled (/workspace/dist/data-requests/vaccination.js:5:58)\n    at runMicrotasks (<anonymous>)\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)"}}

The RKI change the stucture of the data source, the parser must be rewritten .....

To keep the existing data structure of the API we have to switch to the csv data on github (witch is not changed!) and do the extract ourselfs ......... but this needs some time, hopefully finish the work this weekend ...


Enable an existing WebTracingConfiguration to be used to initialise a…

… new builder, used to update/replace the previous values
The BeanPostProcessor approach discussed in #28 works, but there is currently no way to update the skip pattern in the WebTracingConfiguration. This PR provides a using method on the builder to enable an existing configuration to be used to initialise the config before the other builder methods are used to change the values.
Its not an issue currently, as the WebTracingConfiguration only has one property - but in the future it might cause issues if (for example) the metrics lib just returns a new config with the pattern but any other properties on the config are not copied.
If you have other thoughts on how to do this then happy to change.

Updated to use the toBuilder approach.


Update Konnectivity to v0.0.32

New tag of Konnectivity has been released fo and contains improvements to memory leaks which makes sense for us to
update.
Signed-off-by: Imran Pochi<EMAIL_ADDRESS>

/cc @jveski


Some observations - some proposed fixes

Hi Georg,
I cloned 123b622 and tried to follow the instructions here. I'd like to share some of my observations, some problems I ran into, and propose some improvements with respect to test automation.

Tools installation

As all the required tools were already present on my Ubuntu 16.04 x64 machine (SDCC 3.6.0, stm8flash, default Python 2.7...), and I decided to skip the SPL installation for now.
There is, however no indication, that the project requires Python 3 (a subset of the scripts have a #!/usr/bin/python3 header).
It worked for me but some more clarity (and consistency) wouldn't hurt :-)

Getting started

In the fist bullet point, it's not really clear where to copy a suitable example, nor what such a suitable example is, and thus I tried Basic_Project in the repo root folder with the following result:
thomas@w500:~/source/stm8s/STM8_templates/Basic_Project$ ./build_upload.py
Traceback (most recent call last):
  File "./build_upload.py", line 42, in <module>
    import misc
ImportError: No module named misc

I tried a different example (ADC_Measure) with the same result.
Browsing the docs once more didn't help, so I stopped here.

Through the back door

I instead turned to the script ./Projects/build_all_projects.py and ran it. It was a nice surprise that the first examples compiled normally - until the notorious SPL made itself noticed:
compile ./STM8_StdPeriphLib_Examples/Basic_Project ... In file included from ./SPL.c:13:
./stm8s_conf.h:22:19: fatal error: stm8s.h: No such file or directory
compilation terminated.

I then got the SPL from https://github.com/bschwand/STM8-SPL-SDCC (thanks for providing it!), and tried to figure out what to copy to ./Library/ .
I guess that in tool-installation the instruction should be "copy the content of SPL folder Libraries/STM8S_StdPeriph_Driver/" instead of "Library" .
A patched SPL library is now available on GitHub, and maybe it would be easier to integrate into the STM8_templates directly? As the saying goes: In for a penny, in for a pound :-)

Why ask the user to "press return" if the build exits anyway?

Indeed why do I need to press return twice...
press return ...

Which is surprising since build_all_projects.py uses the parameter skippause when calling build_upload.py. Also build_all_projects.py doesn't provide a  skippause option (the conditional pause block is if True:.
Even if it did, the input request comes from Tools/misc.py and appears to be unconditional. I usually try to run my stuff in a Continuous Integration system, and keyboard pixies, e.g. inside Travis-CI, require an awful lot of training on the job ;-) .

Runs on my machine...

After copying in the SPL files, compilation stopped when compiling Basic_Project:
compile ./STM8_StdPeriphLib_Examples/Basic_Project ... SPL.c:46: warning 85: in function assert_failed unreferenced function argument : 'file'
SPL.c:46: warning 85: in function assert_failed unreferenced function argument : 'line'

?ASlink-Warning-Undefined Global '_GPIO_Init' referenced by module 'SPL'

?ASlink-Warning-Undefined Global '_GPIO_WriteReverse' referenced by module 'SPL'

?ASlink-Warning-Undefined Global '_GPIO_WriteHigh' referenced by module 'SPL'
make: *** [output/main.ihx] Error 1

I decided to hide the folder and look into the problem later.
Next was a similar problem in Minimal-C. It got the same treatment.
compile ./STM8_StdPeriphLib_Examples/Minimal-C ... SPL.c:52: warning 85: in function assert_failed unreferenced function argument : 'file'
SPL.c:52: warning 85: in function assert_failed unreferenced function argument : 'line'

?ASlink-Warning-Undefined Global '_GPIO_Init' referenced by module 'SPL'

?ASlink-Warning-Undefined Global '_GPIO_WriteLow' referenced by module 'SPL'

?ASlink-Warning-Undefined Global '_CLK_HSIPrescalerConfig' referenced by module 'SPL'

?ASlink-Warning-Undefined Global '_GPIO_WriteHigh' referenced by module 'SPL'
make: *** [output/main.ihx] Error 1

Everything else compiled (great!), and I made the folders visible again, and ran build_all_projects.py again.
To my surprise I got no error this time! The error returned after running clean_all_projects.py first, and the observed effect is reproducible.
One shouldn't jump to conclusions, and always be careful not to infer the rule from an observation, but it might be the case that both projects depend on an obscure something that's produced by some project later in the compile sequence.

Finally...

I know that building frameworks is hard (people find the most absurd ways to use them), and that's why basic smoke tests should be automated with a reference tool installation.
If you're interested I can contribute a Docker based Travis-CI setup that does basic QA chores. @larsbrinkhoff once did that for my project, and it was the best thing that ever happened to it.
This said, I hope it won't be long until your Christmas vacation :-)
Kind regards,
Thomas

hi Thomas,
thanks a lot for this very thorough comment - though it points out a lot of shortcomings from my side. Unfortunately it's been quite some time that I've been working on this project, so I don't really know where to start...
Anyway, I somewhat lost interest in STM8_templates because I am now involved (a bit) in the sduino project, which aims at integrating the STM8 via SDCC into the Arduino toolchain. It is still work in progress, but Michael Mayer has done a great job of making STM8 programming easy. E.g. no hassle with cryptic Python build-scripts or missing library paths... ;-)   Maybe you want to take a look at sduino instead...?
Some more remarks on your comments:

I decided to publish patches only because SPL is not 100% OSS (see this discussion). Maybe I'm just paranoid but I don't need legal issues... So patchfile it is, sorry!

the basis of STM8_templates is a custom peripheral header stm8s.h. Creating and debugging it was very painstaking! Now I realized that I would need individual headers for the other variants like STM8L. On the other hand the SPLs already provide them for all STM8 variants (+ corresponding functions). Kind of a motivation killer...

IMHO the main issue with SPL is that code using it becomes huge. Now both sduino and this project found a way to split the SPL into individual functions prior to compiling. With this the SPL overhead becomes quite small. With that my main motivation to create a lean framework for STM8 is void.

All in all I have the feeling that STM8_templates is a dead horse. The effort to make it as flexible as the various SPLs, and as easy to use as sduino, is just too big.
Maybe I should point this out clearly on the repo homepage to warn people off...!? In any case sorry for the time you wasted due to my limited Python skills and poor testing! And thanks again for your thorough comments!!
Regards, Georg

PS: what's that "Travis-CI" you mentioned...?

Hi Georg,
There is nothing wrong with losing interest in a project that's not fun anymore. Putting a "sorry, we're closed" sign there would make things clear, though :-)
I had been looking for an STM8 framework for testing an idea that recently received some interest from a team member. Of course, sduino also fits the bill!
I'm aware of the sad state of ST's SPL, but hey, that's a company with at least 100 departments and, likely, no less than 8 levels of hierarchy. It's maybe unavoidable that common sense gets bored and walks away somewhere between the 2nd and the 7th level. On the other hand, the marketing department guys spend millions to look cool nonetheless, and they won't do anything that might discourage the hobby crowd. They even managed to come up with the hyperbole freedom terms ;-)
Travis-CI is a continuous integration system with very good GitHub integration that's free to use for Open Source projects. They supports Docker containers, and the runs are reasonably fast. For sduino, I'm almost sure, it would be a good choice.
Kind regards,
Thomas

hi Thomas,
ad 1) Done. Sorry again for the inconvenience! It had simply slipped my mind  :-(
ad 3) I know exactly what you mean - Dilbert in action...  ;-)    But especially because of that I don't assume common sense but rather play safe and publish patches only.
ad 4) That looks very promising indeed. Maybe I will come back to you on that if I may...?
Good luck with point 2 and have a Merry Christmas! Ho ho ho...
Georg

Hi Georg,
ad 4) I'd happy to get you started. Just open a ticket in the sduino repo and post it here.
Merry Christmas, too!
/Thomas
PS: please check your Connect invites!


ENH: make stage and unstage return status objects

Let stage and unstage return Status objects, so multiple objects can be staged at once.
Description
I have made changes to  _stage and _unstage to allow Stageables to return status objects from their stage and unstage methods. The changes mimic _trigger.
I have changed the type hints on the Stageable protocol.
I have created a test for staging 2 Stageables at once.
I have also changed the plan stubs accordingly.
Motivation and Context
resolves #1559
This change will allow the run engine to stage multiple devices without blocking. And these can then be awaited but a wait message.
How Has This Been Tested?
These changes have been tested by a new test test_stage_and_unstage_status_objects().
Which stages/unstages 2 dummy Stageables then awaits their completion.
The new _stage and _unstage methods use isinstance() to check to see if the output of an objects stage/unstage method is a status object. If it is not they will return the result preserving previous behaviour for Stageables that returns lists of staged objects.

@awalter-bnl was interested in the progress on that topic.

@mrakitin will review and merge tomorrow if he's happy


EFO3: new endpoint required for front-end React application

The new React application requires a new endpoint that serves the EFO3 ontology data. Previously, the Angular app used paths to construct the ontology but this will not be suitable for EFO3 - hence the need for a new endpoint.
Details TBC

An initial ETL pipeline version of the EFO ontology and TAs is available on Google Cloud in JSON format:
https://console.cloud.google.com/storage/browser/open-targets-data-releases/20.04/output/?forceOnBucketsSortingFiltering=false&authuser=0&organizationId=817248562955&project=open-targets-prod&supportedpurview=project
As noted by @cmalangone in Slack, this is an initial version for the MVP and there are two key points to remember:

It is missing the ROOT because we do not have a real entry for the root

{
"id": "EFO_ROOT",
"name": "root",
"parentIds": []
}

No ROOT because the single therapeticArea do not have parentIds

{"id":"EFO_0001444","name":"measurement","parentIds":[]}

Subsequent improvements to the EFO and TA JSON and integration into the GraphQL API will be done after the initial MVP alpha release and will be captured with another ticket.


Is there a "force" mode?

Thus, skips collecting, and "force" overwrite all to the server.
Thanks!

Unfortunately No. Please reference the ftpsync https://www.npmjs.com/package/ftpsync#ftpsyncsettings


Fix a couple bugs in file service

Changes:

Handle the case of Files.probeContentType returning null. This prevented some files from working.
Handle the case of larger files by increasing the limit to 100 MB as specified by pass-ui.

Ok. There is also a bug if there is no file extension. It makes the S3 code unhappy.

@markpatton the issue should now be resolved.


Incorrect listener's onStart(ISuite suite) execution order in case of inner suites

TestNG Version

Note: only the latest version is supported
6.11

Expected behavior
The listener is called for each suite, if the parent suite contains child suites then the parent suites should run first before running the child suite.
Actual behavior
The child suites are first run before running the parent suite.
Is the issue reproducible on runner?

[x] Shell
[x] Maven
[x] Gradle
[x] Ant
[x] Eclipse
[x] IntelliJ
[x] NetBeans

Test case sample
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="ParentSuite" parallel="classes" thread-count="10">

    <suite-files>
        <suite-file path="child_suite.xml"/>
    </suite-files>

    <test verbose="1" name="SomeTest">
        <classes>
            <class name="com.example.SomeTest"/>
        </classes>
    </test>

</suite>

Currently, suite-files is like an import, include <test> from specified suites and the result is only one suite.
Thats why onStart` is only called once.

@juherr actually it's called twice (for each suite file). Has the behaviour changed since 6.11?

Ok, two calls is an issue.
@krmahadevan What is the expected behavior of onStart in case of suite-files?

@juherr - I think that's the correct behavior.
As part of #1285 I think we changed this behavior

I am able to reproduce the issue but, in fact, TestNG was always running child suites before parent suite (https://github.com/cbeust/testng/blame/master/src/main/java/org/testng/TestNG.java#L1191-L1199) and listeners were not correctly added before #1285.

6.13 should have fixed the duplicate issue with #1533

@avarabyeu
I can change the order behavior and run the master suite before the child suites but the master suite will finish before its children.
Will it be ok for you? A better child management implies big changes we will probably don't do.
Could you confirm that 6.13 is fixing the event duplication issue?

Closing this issue for now. @avarabyeu Please comment back if you have an update on the query that I raised so that we can further triage this issue if necessary.

@krmahadevan @avarabyeu
I tried to execute suite of suite-files, without any <test> tags in the master suite file and the problem still happened.
(tested on TestNG v6.14.3)

There were some changes made to the latest codebase in TestNG with respect
to ordering of suites etc.,
So can you please try once again using TestNG  7.0.0-SNAPSHOT and post back
your results ?
If its still a problem, request you to please help share a sample that can
be used to reproduce the problem.

The same problem happened on version 7.0.0-SNAPSHOT
attaching example maven project
testng-reportportal-example.zip

@ulmanA - The sample you shared doesn't say a lot of things (at-least it wasn't explicit for me).
You basically have a suite file called all-suites.xml which looks like below
<suite name="All Suites" verbose="2">
    <suite-files>
        <suite-file path="suite1.xml"/>
        <suite-file path="suite2.xml"/>
    </suite-files>
</suite>

And when I run this, I notice that suite1 gets executed first, then suite2, leading to all_suites completing itself.
...
... TestNG 7.0.0-SNAPSHOT by Cédric Beust<EMAIL_ADDRESS>...
Suite 1 -> TEST 1
Suite 1 -> TEST 2

===============================================
All Suites (0)
Total tests run: 2, Passes: 2, Failures: 0, Skips: 0
===============================================
Suite 2 -> TEST 2
Suite 2 -> TEST 1

===============================================
All Suites (1)
Total tests run: 2, Passes: 2, Failures: 0, Skips: 0
===============================================

===============================================
All Suites
Total tests run: 4, Passes: 4, Failures: 0, Skips: 0
===============================================

So what is your expectation here ? Its not clear.
all_suites is visualized as a container of suites so its going to be finishing at the last.

@avarabyeu
Please answer.

@krmahadevan I am not the bug reporter but I would expect the following order of execution:

ISuiteListener#onStart - all_suites
ISuiteListener#onStart - suite1
ISuiteListener#onFinish - suite1
ISuiteListener#onStart - suite2
ISuiteListener#onFinish - suite2
ISuiteListener#onFinish - all_suites

So yes, all_suites should finish last but it should start first, because it contains all other suites! However, currently all_suites behaves not as a root container but as a container of any  items not included in the nested suites.


Alphabetize packages

Alphabetize packages in DESCRIPTION.

The workflow fails  The deploy step encountered an error: The process '/usr/bin/git' failed with exit code 128 ❌
Can be a problem with a token?


Lab 07 - Missing Instructions

Module: 07
Lab/Demo: 07
Task: 2.2
Step: 07
Description of issue:
There should be an additional step Save & Close after Changing the Status Reason to New Request. This step is necessary for the user to be able to see all four inspections.
Attached Screenshot:

Step is added

Thank You!


Release of action labels

Thanks for releasing such a big dataset.
In your paper, you mentioned 123 #Action in this dataset. Will you release the action labels?

Sorry for late reply. The action annotation file has been released on this link. Please check it out.
Currently, we only release short action category labels, and we are planing to give some dense caption in recent future.

Thanks for your kind sharing.


⚠ Bofrost.at has degraded performance

In ecb34cc, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1643 ms

Resolved: Bofrost.at performance has improved in 93bedfe after 6 minutes.


Domains and emails with non-ASCII characters are not hyperlinked

Email Address Internationalization (EAI) is not hyperlinked correctly.
Here is the link to the tweet: https://twitter.com/datamail_in/status/1055140179089022976?s=19
The email address with non-ASCII character in the above tweet is valid and expected to have a hyperlink when typed in twitter application.
A quick guide that explains the expected behavior of a correct linkification is here:
https://uasg.tech/wp-content/uploads/2017/06/UASG010-Quick-Guide-to-Linkification.pdf
It only linkifies until it comes across "á" letter. There is no link below "á" character.
Internationalized Domain Names (IDNs) permit the global community to use a domain name in their native language or script. This is enabled by allowing domain names to have characters from different scripts, beyond the letters (a to z), digits (0 to 9) and hyphen (-), as encoded by the Unicode standard and as allowed by relevant IDN protocols.
Email Address Internationalization (EAI) is the protocol that allows email addresses with IDNs in the domain part and/or Unicode (non-ASCII) characters in the Local part of the Mailbox name.  Please see the quick guide for EAI from here:
https://uasg.tech/wp-content/uploads/2017/02/UASG014_20170206.pdf
Kindly please look into this issue.
Thank you in advance.

Hi,
Are there any updates on this issue?
I was wondering how long it can take to assign the case to someone?
Thank you

We shouldn't have identified that portion of the text as a link at all. It is not a goal of twitter-text to identify email addresses. This is a bug, but the fix will be to prevent detecting a url incorrectly at all.

Dear leeaustinadams,
Thank you for your reply. I am happy to hear an update.
Let me provide you with more clarification. Universal Acceptance is a concept of treating all domain names equally. If twitter recognizes email addresses or domain names on a tweet, and linkifies, we expect this to happen for all email addresses and domain names, including the ones that have non-ASCII characters. Non-ASCII email holders, domain holders, as Twitter users, will experience dissatisfaction if no action is taken.
To excel in the long run, organizations need to ensure their systems work with the naming infrastructure of the Internet –the domain name system. When businesses are UA-ready, their systems and services will work with the continuously expanding domain name space. It also helps businesses set themselves
up for future opportunities and success by supporting their customers using their customers’ chosen identities.
UA-ready websites, applications and services lead to better user experiences. When a company is UA-ready, email addresses in any script from any domain name can be used. When a site is UA-ready, it will allow customers with domain names in new top-level domains to successfully use the site and its forms.
For this reason, we would appreciate if you can look into this issue. I am including some reference materials for you and your team to review:
Linkification : https://uasg.tech/wp-content/uploads/2017/06/UASG010-Quick-Guide-to-Linkification.pdf
Fact Sheet : https://uasg.tech/wp-content/uploads/2016/08/UASG003-160823-en-onesheet-digital.pdf
All Resources : https://uasg.tech/documents/
Please let me know if you have any questions. Looking forward to hearing positive updates from you.
Have a great day!

Noted, thank you for your thoroughness. We shouldn't have recognized that as a domain because it was an email address and we do not want to hyperlink email addresses.

Assigned to me, have internal review underway. Thanks for your patience!

Hi Leeautinadams,
Thank you for the update.
May I also ask you to reopen our case based on the additional information we add on https://github.com/twitter/twitter-text/issues/281
Thanks in advance.

I will try and see if there is a relationship between this code and #281 or if that represents some kind of policy decision (which I can make no promises about).


[Documentation Error] Chart Events -> click repeated

Bug report
Minor issue in documentation page:
https://apexcharts.com/docs/options/chart/events/
The click event entry is duplicated.
 Only one entry in this page for mouse click event
What is happening instead? Two entries describing the function
What error message are you getting? N/A

Thanks for the heads up! Fixed it


fix: update for latest framework and pieces

[!WARNING]
src/register.ts(15,24): error TS2345: Argument of type 'UtilitiesStore' is not assignable to parameter of type 'Store<Piece<PieceOptions, keyof StoreRegistryEntries>, keyof StoreRegistryEntries>'.
  Type 'UtilitiesStore' is missing the following properties from type 'Store<Piece<PieceOptions, keyof StoreRegistryEntries>, keyof StoreRegistryEntries>': #private, walk, [ManuallyRegisteredPiecesSymbol]

Error: error occured in dts build
    at Worker.<anonymous> (/Users/favna/workspace/sapphire/plugins/node_modules/tsup/dist/index.js:2690:26)
    at Worker.emit (node:events:514:28)
    at MessagePort.<anonymous> (node:internal/worker:263:53)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:807:20)
    at exports.emitMessage (node:internal/per_context/messageport:23:28)
DTS Build error
RollupError: Failed to compile. Check the logs above.
    at Object.error (/Users/favna/workspace/sapphire/plugins/node_modules/rollup/dist/shared/parseAst.js:279:30)
    at Object.error (/Users/favna/workspace/sapphire/plugins/node_modules/rollup/dist/shared/rollup.js:820:32)
    at Object.error (/Users/favna/workspace/sapphire/plugins/node_modules/rollup/dist/shared/rollup.js:18602:42)
    at generateDtsFromTs (/Users/favna/workspace/sapphire/plugins/node_modules/tsup/dist/rollup.js:7776:22)
    at /Users/favna/workspace/sapphire/plugins/node_modules/tsup/dist/rollup.js:7783:59
    at _nullishCoalesce (/Users/favna/workspace/sapphire/plugins/node_modules/tsup/dist/rollup.js:1:198)
    at Object.transform (/Users/favna/workspace/sapphire/plugins/node_modules/tsup/dist/rollup.js:7783:18)
    at /Users/favna/workspace/sapphire/plugins/node_modules/rollup/dist/shared/rollup.js:1005:40

[!WARNING]
src/listeners/_load.ts(6,65): error TS2419: Types of construct signatures are incompatible.
  Type 'new (context: LoaderContext) => PluginListener' is not assignable to type 'new (...args: any[]) => Piece<PieceOptions, never>'.
    Construct signature return types 'PluginListener' and 'Piece<PieceOptions, never>' are incompatible.
      The types of 'store' are incompatible between these types.
        Type 'ListenerStore' is missing the following properties from type 'Store<Piece<PieceOptions, never>, never>': #private, [ManuallyRegisteredPiecesSymbol]
src/listeners/_load.ts(6,93): error TS2322: Type 'string' is not assignable to type 'never'.

Error: error occured in dts build
    at Worker.<anonymous> (/Users/favna/workspace/sapphire/plugins/node_modules/tsup/dist/index.js:2690:26)
    at Worker.emit (node:events:514:28)
    at MessagePort.<anonymous> (node:internal/worker:263:53)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:807:20)
    at exports.emitMessage (node:internal/per_context/messageport:23:28)
DTS Build error
RollupError: Failed to compile. Check the logs above.
    at Object.error (/Users/favna/workspace/sapphire/plugins/node_modules/rollup/dist/shared/parseAst.js:279:30)
    at Object.error (/Users/favna/workspace/sapphire/plugins/node_modules/rollup/dist/shared/rollup.js:820:32)
    at Object.error (/Users/favna/workspace/sapphire/plugins/node_modules/rollup/dist/shared/rollup.js:18602:42)
    at generateDtsFromTs (/Users/favna/workspace/sapphire/plugins/node_modules/tsup/dist/rollup.js:7776:22)
    at /Users/favna/workspace/sapphire/plugins/node_modules/tsup/dist/rollup.js:7783:59
    at _nullishCoalesce (/Users/favna/workspace/sapphire/plugins/node_modules/tsup/dist/rollup.js:1:198)
    at Object.transform (/Users/favna/workspace/sapphire/plugins/node_modules/tsup/dist/rollup.js:7783:18)
    at /Users/favna/workspace/sapphire/plugins/node_modules/rollup/dist/shared/rollup.js:1005:40

Basically we need to be able to remove all the ts-expect-error comments without getting build errors.
The cause appears to be that module augmentations arent being loaded
Purely experimental but I've already tried setting type to module in each package.json but to no avail

@sapphiredev pack

@sapphiredev pack

@sapphiredev pack


UWP app launches very slow with many assets

Describe the bug
UWP app launch length is proportional to the number of assets included in the project (e.g. images with Build Action set to Content). Even for a simple blank page, which does not do anything, just having many assets present in the application package causes the app to load extremely slow - while the code is not touching them at all.
Steps to reproduce the bug
Steps to reproduce the behavior:

Create a blank app
Launch it - observe it starts up almost immediately
Add 1000 small images in the Assets folder (even icons are enough)
Launch app - it may now take even 20 seconds to launch

For better convenience, I have created a simple repro here on GitHub. It contains two apps - one is simple blank UWP app without any assets, second is a blank UWP app with many image content assets (which are however not used at all.
Expected behavior
When app does not use the content files in any way, they should not affect the launch time of the app (as the files are already deployed with the package, so the app should not manipulate them on start).
Screenshots
Profiler output
Notice the profiler shows all the launch time spent in Window Resized.

During debugging, you can see there is almost no CPU nor RAM activity during this wait time.
Version Info

NuGet package version: none required, classic UWP is sufficient

Windows 10 version
Saw the problem?

Insider Build (xxxxx)
Yes

November 2019 Update (18363)
Yes

May 2019 Update (18362)
Yes

October 2018 Update (17763)
Yes

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Mobile
Yes

Xbox

Surface Hub

IoT

Additional context
Noticed this long ago with my app which has a lot of content icon images, but now I finally found out what is the root cause of it launching this slow.

@Austin-Lamb @bartekk8 The repro is with just the platform bits (no winUI).

@ranjeshj That is true, it would not matter if I added Microsoft.UI. Unfortunately there is no better place to report UWP issues (that would be seen by the developers), that's why I posted the problem here. I will repost it on Windows Feedback too, but I am not sure it will reach the developer team from there.

@MartinZikmund We have the correct repo :). With WinUI3 the platform bits are being moved out of the OS. So we can track this issue here. Thanks for reporting.

Hi guys, I'm having the exact same issue. Just wondering if anyone has found a solution and/or source of the problem yet, thanks!

I'm also running into this issue and discovered that it's irrelevant if there's many Assets included in the .csproj (as is the case in the original posters' repo). As long as there are a lot of assets in the AppX output directory, the slowdown occurs. The hang is occurs on rootPage.Navigate in the App.xaml.cs.

Apparently it also has to do with the image size on my end, I've compressed a few images in the app assets and the startup time went to just 3 seconds on debug from around 11 seconds.

@bartjroos My workaround here was to add the assets into a single .zip file, which I extract to ApplicationData folder on first launch. Then, I reference the files via ms-appdata:///Local/ instead of ms-appx. It means the app takes up twice the storage space though, so it is not a "proper" solution. On the other hand, this way the app launches very fast.


Support stale-while-revalidate

Fixes and missing checks to caching logic to improve performance by enabling on disk caching for certain tilesets (Google 3D Tiles).

Fix cases where response headers with both max-age=0 and an intentionally out of date Expires header would cause responses to never get cached on disk. Ex. Google 3D Tiles root response.
Fix cases where response headers with max-age=0 and stale-while-revalidate would not get cached to disk, even though they are eligible with revalidation. Ex. Google 3D Tiles response.
Fix handling of no-cache directive to let response go to cache shouldCacheRequest and always cause a revalidate in shouldRevalidateCache. Previous logic did not let it go to cache at all.
Modify ResponseCacheControl class to store stale-while-revalidate directive. Also let it contain new methods to individually check for existence / value of certain params.
Add 2 new unit tests

Closes #659

@kring All ready for re-review, when you're ready.

Here are some numbers that anticipate the real-world improvements that users could see...
@shehzan10
Plugin: Cesium for Unreal
Repro: Open map in editor, let it sit until network access stops
Test Map: cesium-unreal-samples -> \Content\CesiumSamples\Maps\12\12_CesiumGoogleMapsTiles.umap
First run: Disk cache empty, tile content loading from network only
Network bytes downloaded: 14,320,916
Second run: Disk cache populated, content is revalidated, and previous content reused
Network bytes downloaded: 308,364
In this example, our network usage reduced by ~97.8% when our visible tiles were already in our disk cache. In addition, tiles should appear to load faster, as there is less to download, but times will vary based on your processor and network connection.
This is a substantial win for network bandwidth in the best cases. That being said, network lag is still present in all cases, as we do have to ask the server if the content has changed.

This is a substantial win for network bandwidth in the best cases.

14MB -> 300KB is indeed a great improvement! That's enough of a difference that, even if you have a decent network that can download multiple megabytes per second, it may still save a few seconds. Out of curiosity, were you able to measure any reduction in total load time?

This is a substantial win for network bandwidth in the best cases.

14MB -> 300KB is indeed a great improvement! That's enough of a difference that, even if you have a decent network that can download multiple megabytes per second, it may still save a few seconds. Out of curiosity, were you able to measure any reduction in total load time?

I didn't, but I can. Timing will vary a lot with your particular CPU and network provider, even from run to run, but I can measure something so we can have at least one data point.

One more small thing I forgot to mention before: please update CHANGES.md to mention this change.

Thanks @csciguy8! I tweaked the shouldCacheRequest function just a liiiitle more, and wrote some tests to demonstrate the difference. Please check my commit to make sure I didn't miss anything, but I'm going to go ahead and merge this.

Looks sensible to me. Like the addition of even more tests. Funny how this started as supporting the stale-while-revalidate directive, but has very little to do with it in the end. Lots of great changes for our caching engine.


Hello dynamic configuration has not been effective, I want to use redis or db

Hello dynamic configuration has not been effective, I want to use redis or db

Hi @whd120130 can you elaborate? I'm not completely sure if I understand what you are asking.

Closing due inactivity.


SyntaxError in the example code in readme

It appears the exception syntax in the following line is incorrect: https://github.com/irods/irods_rule_engine_plugin_python/blob/main/README.md?plain=1#L156
When I modified it to except Exception as e:, the check_err function didn’t work as expected.

Good find. To be more specific, here's the Python stacktrace I got when running this against <IP_ADDRESS> / 4.3.3 on Ubuntu 22.04 (python 3.10.12):
Traceback (most recent call last):
  File \"/etc/irods/core.py\", line 8, in testRule
    if check_err(e, USER_FILE_DOES_NOT_EXIST):
  File \"/etc/irods/core.py\", line 3, in <lambda>
    check_err = lambda e,errcode: e.message.startswith('[iRods__Error__Code:{}]'.format(errcode))
AttributeError: 'RuntimeError' object has no attribute 'message'

A RuntimeError is being raised and RuntimeError does not have a message attribute.
In addition to fixing the SyntaxError, I made the following adjustment to the example rule and got the expected output:
3c3
<   check_err = lambda e,errcode: e.message.startswith('[iRods__Error__Code:{}]'.format(errcode))
---
>   check_err = lambda e,errcode: str(e).startswith('[iRods__Error__Code:{}]'.format(errcode))

Here's the output with the adjustment:
$ irule -r irods_rule_engine_plugin-python-instance -F call_testRule.r '*dataPath="/tempZone/home/rods/goo"'

Level 0: DEBUG: msiObjStat: rsObjStat failed for /tempZone/home/rods/goo, status = -310000

We'll get that fixed up


[Bug] Datasource secret reference not working

Describe the bug
I've been following this document: https://grafana-operator.github.io/grafana-operator/docs/examples/datasource_variables/readme/ to create datasource and refer the token created in a kubernetes secret (deployed in same namespace).
Version
Full semver version of the operator being used- v5.0.0-rc2
To Reproduce
Steps to reproduce the behavior:

Install Grafana operator and Grafana external instance
Create a Grafana datasource as below:

apiVersion: grafana.integreatly.org/v1beta1
kind: GrafanaDatasource
metadata:
  name: sentry-ds1
  namespace: monitoring
spec:
  valuesFrom:
    - targetPath: "secureJsonData.authToken"
      valueFrom:
        secretKeyRef:
          name: "my-secrets"
          key: "sentry_org_token"
  instanceSelector:
    matchLabels:
      dashboards: dashboarding
  datasource:
    name: sentry-ds1
    access: proxy
    editable: false
    jsonData:
      url: https://sentry.io
      orgSlug: 'my-org'
    secureJsonData:
      "authToken": ${sentry_org_token}
    type: grafana-sentry-datasource

Define K8s secret:

apiVersion: v1
stringData:
  sentry_org_token: MY--RANDOM--TOKEN==
kind: Secret
metadata:
  name: my-secrets
  namespace: monitoring
type: Opaque

See error

message: |
      GrafanaDatasource/monitoring/sentry-ds1 dry-run failed, error: failed to create typed patch object (monitoring/sentry-ds1; grafana.integreatly.org/v1beta1, Kind=GrafanaDatasource): .spec.valuesFrom: field not declared in schema
    reason: ReconciliationFailed

Expected behavior
The datasource should be created with secret defined in my-secrets and it should not complain about schema as I've taken the example from docs.
Suspect component/Location where the bug might be occurring
While creating the datasource - while referring the k8s secrets.
Screenshots
If applicable, add screenshots to help explain your problem.
Runtime (please complete the following information):

OS: [e.g. Linux,Fedora,Mac] - Linux
Grafana Operator Version [e.g. v5.0.0]  v5.0.0-rc2
Environment: [e.g Openshift,Kubernetes,minikube etc. please specify versions] Kubernetes
Deployment type: [e.g running the operator locally, or deployed] Running operator locally
Other: [Other variables/things that might be relevant to this bug, versions of other services e.g. operator-sdk]

Additional context
I'm using kustomize to sync the Grafana objects. These object (dashboards or datasources) can be created in any given namespace hence I should not set the reference in Grafana object. I've been testing this use case from last one month and observed following:

Datasource are not easy on reading K8s secrets - even deployed in same NS
It should not complaints about schema (already example is given)
Update in datasource or secret will break the datasource
I've tried following but even this does not work with secret grafana-os-credentials deployed and ready.

# deploy on bakery grafana
apiVersion: grafana.integreatly.org/v1beta1
kind: GrafanaDatasource
metadata:
  name: sentry-datasource1
  namespace: monitoring
spec:
  secrets:
    - grafana-os-credentials
  instanceSelector:
    matchLabels:
      dashboards: dashboarding
  datasource:
    name: sentry-datasource1
    access: proxy
    editable: false
    jsonData:
      url: https://sentry.io
      orgSlug: 'my-org'
    secureJsonData:
      authToken: ${SENTRY_ORG_TOKEN}
    type: grafana-sentry-datasource

Any hint would be great.

It seems the feature was added here but still not working for me. Am I missing anything?

@rajeevsh990 You're simply trying to use syntax that was introduced in a newer version of the operator. The PR you're referring to is part of v5.0.0-RC3). Though, I'd recommend to install something newer like v5.1.0 to avoid hitting some bugs.

Thankfully I found it and it worked.


populations + getindex/iteration support

Population allows creating arbitrary numbers of neurons from a prototype/template using the Base.Iterators interface.
This PR will also implement iteration and indexing on MultiCompartmentSystems (to index subcompartments versus calling by name with getproperty) and the same for NetworkTopology and NeuronalNetworkSystem.

Enables convenient syntax like:
for neuron in network, compartment in neuron
    # process each compartment of each neuron in a NeuronalNetworkSystem
end

# make a synapse between two neurons
topology[pre, post] = Glut(30nS)
# alternatively...
topology[pre => post] = Glut(30nS)

# mixed syntax...
network[2].soma # soma of the 2nd neuron in the network


Add Resemble.js

Adds types for Resemble.js
This is the first library I've added, hope I've done it right :-).
The Resemble.js API is fairly minimal, so reasonably easy to come up with a clear outline. It's not a particularly well documented library though sadly, which makes it hard to be definitive. I've pulled in the examples from their page plus a few extra bits for detail as tests, and this does successfully compile everything I'm using it for in my project.
(Sorry, I've been doing lots of moving things to TypeScript today, so lots of PRs for libraries en route. Hope that's ok!)

And indeed I had done it wrong; turns out while it compiled, it didn't actually pass the NPM tests. Now fixed.

resemble/resemble.d.ts
check list

[ ] is collect naming convention?

https://www.npmjs.com/package/resemble
http://bower.io/search/?q=resemble
others?

[X] has a test file? (resemble/resemble-tests.ts or others)
[ ] pass the Travic-CI test?

@pimterry thank you for your contributions!
please rename resemble/resemble.d.ts to resemblejs/resemblejs.d.ts

Done :smile:

@pimterry thanks mate!


[#264, #266] fix issue.

see #264, #266.

Coverage increased (+0.0%) to 72.91% when pulling 2298db63ba20a904a45bcef84aa93ccb9a46a63d on sunny4381:shirasagi-264 into 07386a099e0be8c52d7b490e1773a329c645dba0 on shirasagi:master.