Document response without specifying schema

I have an endpoint that allows the end user to specify which fields they want returned, which I pass through to the Marshmallow serializer. This is pretty easy to do:
blp = Blueprint('people', 'people', url_prefix='/people',
                description='Operations on people')

class PersonGetArgsSchema(Schema):
    """Query arg schema for people get endpoint"""
    id = fields.String(required=True)
    return_fields = fields.List(fields.String(), required=True)

@api.definition('Person')
class PersonSchema(Schema):
    """Marshmallow schema for serializing a person instance"""
    id = fields.String(required=True, example='3065ac69-6aad-4832-9889-c81ab773424e')
    # other fields

@blp.route('/get')
class PersonResource(MethodView):
    @blp.arguments(PersonGetArgsSchema, location='json')
    @blp.response(None)
    def post(self, body):
        """Get a single person by ID (actually using POST, since REPORT isn't supported)"""

        # get the person from Elasticsearch
        person = PersonDoc.get(id=body['id'], _source=body['return_fields'])

        # serialize and return
        person_schema = PersonSchema(only=body['return_fields'])
        return person_schema.dump(person.to_dict())

This works fine, but because I specified @blp.response(None), my API docs don't automatically have an example response like I would if I had schema=PersonSchema.
My current solutions is to subclass Schema:
class SchemaWithEx(Schema):
    def example_dict(self):
        return {
            k: v.metadata['example'] for k, v in self.fields.items() if 'example' in v.metadata
        }

@api.definition('Person')
class PersonSchema(SchemaWithEx):
    # ...

@blp.response(schema=None, example=PersonSchema(only=['id', 'name']).example_dict())

Is my situation really obscure or would it be worth adding a feature like this?

Hi.
I do think this is pretty specific. But I could be proven wrong.
I don't really see what feature flask-rest-api could propose to make this easier. Do you have a more precise idea?
Also, since the example_dict method is not specific to this schema but generic to your use case, I'd put it in a BaseSchema and let all schemas inherit from it. This sounds like a reasonable compromise. What do you think?

Closing this for now.
Doing it in a BaseSchema sounds reasonable to me. If you think there's anything this lib can do to help, please comment.


Missing description how to set up Type Instance with AWS credentials

Description
We have one for GCP https://github.com/capactio/website/blob/main/docs/example/mattermost-installation.md#instructions-1
We have manifests for AWS, like for RDS and Elasticsearch, we should have description how to use them.
Maybe we could rework Mattermost example so it have 3 paths. For local deployment, for AWS and for GCP.
Consider creating a new document where it's described how to create a Type Instances for AWS and GCP.

AC:

Add AWS RDS scenario for Mattermost
In separate document, describe how to create common TypeInstances (AWS nad GCP credentials) - how to generate credentials in AWS/GCP and how to create the TypeInstances

It would be also good to include description of the scenario with reusing existing DB for Mattermost, as AFAIK we don't have anywhere such description.

I would leave it for a different example. Mattermost is already big with 3 different scenarios.
Maybe an example where we deploy Database and the reuse it with two different projects would be better.

closed in https://github.com/capactio/website/pull/56


language idea

I hope that Chinese can be added to the language in future versions

Hi @Ferdavis9,
You can help translating if you can: https://hassagent.readthedocs.io/en/latest/translating/
The translations are community driven (as they're very expensive to have done professionally).


Meson complains about an absolute include path

This is a fairly annoying issue, and I've seen it before but somehow am only now running into it again - probably because I'm working in a Docker container.
Trying to run pip install . --no-build-isolation inside a Docker container on current main results in:
      ../../scipy/meson.build:48:0: ERROR: Tried to form an absolute path to a source dir.
      You should not do that but use relative paths instead.

Outside of a Docker container there's never a complaint - and yes, we are feeding include_directories an absolute path.
find_libraries, which we also use, does require an absolute path. So it looks like we need both; this diff gets us past errors in scipy/meson.build:
diff --git a/scipy/meson.build b/scipy/meson.build
index a1e97b2dd..26f0af439 100644
--- a/scipy/meson.build
+++ b/scipy/meson.build
@@ -37,7 +37,7 @@ if is_windows
 endif

 # NumPy include directory - needed in all submodules
-incdir_numpy = run_command(py3,
+incdir_numpy_abs = run_command(py3,
   [
     '-c',
     'import os; os.chdir(".."); import numpy; print(numpy.get_include())'
@@ -45,29 +45,37 @@ incdir_numpy = run_command(py3,
   check: true
 ).stdout().strip()

-inc_np = include_directories(incdir_numpy)
+incdir_numpy_rel = run_command(py3,
+  [
+    '-c',
+    'import os; os.chdir(".."); import numpy; print(os.path.join("..", os.path.relpath(numpy.get_include())))'
+  ],
+  check: true
+).stdout().strip()
+
+inc_np = include_directories(incdir_numpy_rel)

-incdir_f2py = incdir_numpy / '..' / '..' / 'f2py' / 'src'
+incdir_f2py = incdir_numpy_rel / '..' / '..' / 'f2py' / 'src'
 inc_f2py = include_directories(incdir_f2py)
 fortranobject_c = incdir_f2py / 'fortranobject.c'

 cc = meson.get_compiler('c')
-npymath_path = incdir_numpy / '..' / 'lib'
+npymath_path = incdir_numpy_abs / '..' / 'lib'
 npymath_lib = cc.find_library('npymath', dirs: npymath_path)
-npyrandom_path = incdir_numpy / '..' / '..' / 'random' / 'lib'
+npyrandom_path = incdir_numpy_abs / '..' / '..' / 'random' / 'lib'
 # Note: `required: false` can be removed once numpy 1.19 is the minimum version
 npyrandom_lib = cc.find_library('npyrandom', dirs: npyrandom_path, required: false)

 # pybind11 include directory - needed in several submodules
-incdir_pybind11 = run_command(py3,
+incdir_pybind11_rel = run_command(py3,
   [
     '-c',
-    'import pybind11; print(pybind11.get_include())'
+    'import os; import pybind11; print(os.path.relpath(pybind11.get_include()))'
   ],
   check: true
 ).stdout().strip()

-inc_pybind11 = include_directories(incdir_pybind11)
+inc_pybind11 = include_directories(incdir_pybind11_rel)

 # Pythran include directory and build flags
 use_pythran = run_command(py3,
@@ -82,7 +90,7 @@ if use_pythran
   incdir_pythran = run_command(py3,
     [
       '-c',
-      'import os; os.chdir(".."); import pythran; print(os.path.dirname(pythran.__file__));'
+      'import os; os.chdir(".."); import pythran; print(os.path.join("..", os.path.relpath(os.path.dirname(pythran.__file__))));'
     ],
     check: true
   ).stdout().strip()

However, now inc_np is a relative path so it cannot be reused as easily in subdirectories. The next error that pops up is:
      ../../scipy/special/meson.build:320:4: ERROR: File ../env/lib/python3.10/site-packages/numpy/core/include/../../f2py/src/fortranobject.c does not exist.

We'd have to go through every subdir where we use inc_np (and there's 67 usages). An absolute path should be fine (and is nicer to use), and it's not clear to me why it doesn't work inside Docker.
@eli-schwartz any thoughts?

Similar bug report (but no follow-up, does say it's happening on Ubuntu, and I was using an Ubuntu Docker container with system Python): https://github.com/mesonbuild/meson/issues/8640

Ah, the code looks like this:
src_root = self.environment.get_source_dir()

for a in incdir_strings:
    if a.startswith(src_root):
        raise InvalidArguments(textwrap.dedent('''\
            Tried to form an absolute path to a source dir.

So what's happening is that the check goes off only if your include dir is inside your source tree. In this case I was creating a Python virtual environment within the scipy source tree. So the error message is highly misleading.
I think it's actually not good practice to create venv's within the source tree, but it's also common (I don't use venv's or Docker much, so I just copy-pasted a tutorial which is why I ran into it now).

I have a vague memory of bringing this up before and the initial answer being "don't do that". We need to fix this somehow though, because it's common practice. Here's a few tools that do create venv's inside the local tree:

PDM (based on PEP 582)
Tox
ASV
The first search result for a virtualenv tutorial: https://realpython.com/python-virtual-environments-a-primer/

https://github.com/rgommers/scipy/issues/82#issuecomment-974225733

Argh yes, thanks. That increases the importance of making dependency('numpy') work natively in Meson. And until we do that, I guess the answer remains "don't do that".
I'll submit a PR to Meson to clarify the error message though.

And until we do that, I guess the answer remains "don't do that".

And it will remain the same after that, too.
One thing that an old-fashioned virtualenv package is better than venv, is you create a  ~/.virtualenvs directory, set a $WORKON_HOME env var in  .bashrc, once. and that's it.

Not considering this a blocker for 1.9.0, so bumping the milestone. If someone runs into this when building from source in a venv that's installed inside the source tree: see the four last comments above.

I think I had this issue in #17151. I've been trying to use meson to build in an ubuntu and a quay.io/pypa/manylinux2014_x86_64 docker image.  I get the error reported in #17151, which is a lengthier version of the first comment in this issue. I have trying to build within a venv, and see this error regardless of whether I make the venv inside or outside of the scipy source tree.
I do not see the error if I try to build without a venv.

We do have a CI job specifically testing a venv on Debian: https://github.com/scipy/scipy/blob/main/.github/workflows/linux_meson.yml#L125. So it's a little odd that that works, except when you're in Docker.

So what's happening is that the check goes off only if your include dir is inside your source tree.

I am fairly sure that that is the only thing that triggers this check. It would be helpful to to confirm that by debugging in the Docker container if you can @andyfaff, and checking the paths. The exact line of code is https://github.com/mesonbuild/meson/blob/b8e53ed5ea9c2a3eec19396233e646d4c1f667ae/mesonbuild/interpreter/interpreter.py#L2657.

We are observing this issue during the PyData NYC mini sprints outside a Docker container. System is a Macbook Pro with macOS Big Sur from @kejsitake. Creating the virtual environment outside the SciPy source directory didn't help.

After switching to a conda/mamba environment @kejsitake managed to successfully build SciPy. In parallel she made some global software changes with Homebrew so it's unclear whether we will be able to reproduce the issue again or recover the logs, but at least knowing that it was a venv thing might help.

This is important, but not as high prio as working on the BLAS/LAPACK support in Meson. We won't get around to this for 1.10.0, so I have bumped the milestone.


[WIP] On-board insights.

Hi @haocs, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;

As no one is actively working on this and I have this branch in my repo, I'm going to close this for now.


What does AT-23, AT-20, AT-04,... mean?

See e.g. https://github.com/smhg/sepa-qr-data-php#setbicbic
I figure you've copied this from the EPC PDF. Do you know what it stands for?

Not sure, but it seems to be the identifier of each part of the money transfer? Maybe it predates SEPA? Feel free to add it to this issue if you figure it out. It would be nice to know.

From the "SCT Rulebook" at https://www.europeanpaymentscouncil.eu/document-library/rulebooks/2019-sepa-credit-transfer-rulebook-version-12 :

This numbering is only for cross referencing purposes within the Rulebook.

So I would suggest: Remove it from README; since "AT-23" is just a shortcut for "The BIC code of the Beneficiary Bank" and doesn't add any value.

Thank you for looking this up!


Formatting doesn't work

Every time I try to format a QML-FIle, it shows:
Formatting of 'main.qml' failed (ENOENT): 'spawn qmlformat ENOENT'.

Hi.
By default, the extension tries to call qmlformat command. If it's not available in your PATH by default, you can specify the path toward the qmlformat in the settings:
{
    "qmlFormat.command": "/usr/lib/qt6/bin/qmlformat",
}

See requirements and example in the README.

Thanks a lot!

I'm closing the ticket as it seems resolved. :+1:


Component names in production...

When installing this as a dev dependency, I would have expected the component names to just appear when running in dev environment. But they are also appearing in our production environment - how is this possible?

@joetidee (and others who are here from search), here is how I solved this issue in my next.js app
.babelrc
{
  "presets": ["next/babel", "@zeit/next-typescript/babel"],
  "plugins": [
    [
      "babel-plugin-styled-components",
      { "ssr": true, "displayName": true, "preprocess": false }
    ]
  ],
  "env": {
    "production": {
      "plugins": [
        [
          "babel-plugin-styled-components",
          { "ssr": true, "displayName": false, "preprocess": false }
        ]
      ]
    }
  }
}

Correct me if I'm wrong folks 😉


Typesafe Links

Description
I've a design in mind to make this work:
// Note the typo (it should be `product` instead of `produt`).
// TypeScript complains that '/produt/42' isn't matching '/product/${string}' | '/' | '/some-other-route'
<Link href="/produt/42" />

React with 👍 if you want this.

Could a global type declaration for anchor tags <a> achieve typesafety instead of a custom link component?

I stand to be corrected, but I believe that isn't possible.
The idea is to have VPS code-gen type Routes = '/product/${string}' | '/' | '/some-other-route' while:

Routes is completely UI framework agnostic and can be used by the user/framework's <Link> implementation.
The code-gen will be completely seamless (although Yarn users will have to add a line to their tsconfig.json). (But I've to check whether TypeScript doens't do something unexpected with the trick I've in mind.)

Routes is completely UI framework agnostic and can be used by the user/framework's  implementation.

That makes sense. Users are required to provide their own  component.

From Discord:

It would be very nice if it were possible to auto-generate types for routes out of the box, to be able to do something like <Link href={routes.Product} parameters={[paramA, paramB]}, with type-safety for all parameters and the route itself.

Yea I thought about this but, so far, I'm against this. Because it would require the user to give each and every route a name, which is pesky. And the ability to change the route of a page without having to update every <Link> is clearly useful, but not that useful (instead you can let TypeScript tell you what links you have to update which is an acceptable DX, I think).

From Discord:

It would be very nice if it were possible to auto-generate types for routes out of the box, to be able to do something like <Link href={routes.Product} parameters={[paramA, paramB]}, with type-safety for all parameters and the route itself.

Yea I thought about this but, so far, I'm against this. Because it would require the user to give each and every route a name, which is pesky. And the ability to change the route of a page without having to update every <Link> is clearly useful, but not that useful (instead you can let TypeScript tell you what links you have to update which is an acceptable DX, I think).

Yes TS template strings are clearly less cluttered. This is better, didn't even think about that feature.
Now I'm curious how file-based routing works with i18n. Is this also a part of the idea? Haven't used i18n with VPS so far a at all.

Currenlty, i18n is being implemented programmatically, which provides a lot of flexibility, see https://vite-plugin-ssr.com/i18n.
And, yes, for typesafe links a declarative i18n interface will be needed. (Not only for providing typesafe i18n links, but also for a simpler interface that works for the vast majority of users.)

Makes senses, thank you for your reply.
Programmatic i18n leaves most flexibility for routes (e.g. subdomain vs pathname prefix) and people can still share functions, components or e.g. React hooks to work with the API.

Would this also apply to navigate?
remix-routes does this as $path so you'd just by default kill two birds with one stone, as you just call it with that function.

Would this also apply to navigate?

Yes.

Very much looking forward to using this!
It’d be awesome if in addition to type-safe pathnames, there was support (or at least a recommendation) for how to set and consume type-safe query parameters / hashes in the URL, similar to TanStack Router.

type-safe query parameters / hashes in the URL, similar to TanStack Router.

I agree.


Remove: Unity.Unity.6000.WindowsIL2CPP version 6000.0.5f1

Microsoft Reviewers: Open in CodeFlow

URL: https://download.unity3d.com/download_unity/17028576122a/TargetSupportInstaller/UnitySetup-Windows-IL2CPP-Support-for-Editor-6000.0.5f1.exe
OK
(Automated message - build 923)

https://github.com/microsoft/winget-pkgs/pull/186121#issuecomment-2445759087

[Policy] Needs-Manual-Merge


Allow setup inside nvim-treesitter

Description
Hello!
I would be nice to setup up this plugin from inside treesitter similar to several other plugins (autotag, endwise, playground, textobjects, etc):
Example from playground:

Thanks!
Neovim version
0.10
Expected behavior
No response
Actual behavior
See description
Minimal config
See description

Steps to reproduce

nvim --clean -u minimal.lua
...

nvim-treesitter modules are planned to be removed.

nvim-treesitter modules are planned to be removed.

Do you have a link to relevant discussion / issue?

All discussion is on matrix. It's well agreed in the team that nvim-treesitter modules are a big mistake.

Also see https://github.com/nvim-treesitter/nvim-treesitter/issues/4767


cli tests

We keep breaking the cli in various ways. Time for automated tests!

[ ] test the entire "menu" state machine
[ ] key generation properly making things with the right permissions
[ ] your ideas here

From #898, by @johnwu93:
Extend from this: #897

We want to test user inputs on coda client. Particularly, we want to test the logic of Daemon_cli. Namely, we want to test whether the daemon startup menu will show up or not or if we automatically connect to a daemon.


Update kseq++ version

This includes the speed improvements suggested for seqtk at https://github.com/lh3/seqtk/pull/123
Also:

Add kseq++ files to a separate folder and add the LICENSE file (as required)
Update the README for the list of 3rd-party software

Approved.


[Bug]: Insecure URL is automatically upgraded to Secure when using headless: new

Minimal, reproducible example
const puppeteer = require("puppeteer");

(async () => {

    const launchOptions = {
        headless: 'old',
        args: ['--no-sandbox', '--disable-setuid-sandbox', '--single-process', '--disable-gpu'],
    };

    const browser = await puppeteer.launch(launchOptions);
    const page = await browser.newPage();

    const url = 'http://www.httpvshttps.com';
    console.log("goto URL: ", url);
    await page.goto(url);
    let currentURL = page.url()
    console.log("current URL: ", currentURL);

    await browser.close();
})();

Error string
no error
Bug behavior

[ ] Flaky
[ ] PDF

Background
I have a test which loads an insecure page on http://domain.com, with insecure assets over http://assets.domain.com - when I set headless to new the request is upgraded to https://domain.com which then breaks the page entirely, as the assets continue to load from their insecure domain.
Using my example above the output for headless: 'new' is
goto URL:  http://www.httpvshttps.com
current URL:  https://www.httpvshttps.com/

when I set headless: 'old' (or headless: true)
goto URL:  http://www.httpvshttps.com
current URL:  http://www.httpvshttps.com/

Expectation
Not automatically upgrade the insecure request
Reality
It switches the request from http://domain.com to https://domain.com
Puppeteer configuration file (if used)
No response
Puppeteer version
21.4.1
Node version
18.18.0
Package manager
npm
Package manager version
9.8.1
Operating system
Linux

Indeed, new headless is upgrading the URL. Could you clarify what you mean by

I set headless to new the request is upgraded to https://domain.com/ which then breaks the page entirely, as the assets continue to load from their insecure domain.

Is this for a custom domain? Or for http://www.httpvshttps.com? The latter works fine with the upgrade.

@jrandolf thanks for the reply. You can ignore domain.com really, that was just a placehold/example.
So with http://www.httpvshttps.com/ you can see that setting headless: 'new' causes the loading of https://www.httpvshttps.com/ though, and the other headless options don't.
Is this a bug or a feature? if it's a feature, then how can it be disabled?

@jrandolf in case it's unclear, there's no redirection on the web server for http://www.httpvshttps.com/ which is why I chose that site. Going to that URL in Puppeteer, I'd expect the URL to be unchanged, but instead it's changed to https://www.httpvshttps.com/

This is working as expected as it matches the behaviour for the headful browser. See https://blog.chromium.org/2023/08/towards-https-by-default.html


Added flag  --non-interactive to fly set-team and destroy-team #1326

… issue #1326

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

@aleksey-hariton Thank you for signing the Contributor License Agreement!

It would be great if you could run go fmt on the two files you modified, as this will unify the spacing and alignment in the structs and is considered best practice in the Go community.

@SHyx0rmZ I'll, first experience with Go :)
Also need to fix tests.

@SHyx0rmZ done

Thanks for the PR @aleksey-hariton-epam . I've scheduled it under our UX project as Ready to Work, someone from our team should be reviewing it soon!


Fixed reference to nil value causing errors when players disconnect.

Fixed the following:
[ERROR] entities/gmod_wire_expression2/core/debug.lua:34: table index is nil
  1. v - entities/gmod_wire_expression2/core/debug.lua:34
   2. unknown - lua/includes/modules/hook.lua:84

Caused by k being nil. Error happens when leaving a server while E2 is printing.

Thank you :)


Update AeroGear Android dependency version

We may need to tag this version as well

@wtrocki https://github.com/aerogear/aerogear-android-example-apps/releases/tag/2.1.0-alpha.1


How to do custom class with Field and Radio Buttons

<Field model={'.purpose'} validators={{required}}>
            <CustRadio label="In Order to"
            options={[
              {value: 'option1', name: 'option1'},
              {value: 'option2', name: 'option2'},
              {value: 'option3', name: 'option3'}
            ]}/>

class CustRadio extends React.Component {
  render() {
    return (
      <div className={`form-group ${(props.valid === false && props.touched === true) ? 'has-error' : ''}`}>
        {props.label}
        {
          props.options.map(function(option, index){
            return (

                  <input type="radio" name="test" value={option.value}/>
                  {option.name}

            )
          })
        }

    )
  }
}

Trying to get props from Fields to map on to CustRadio so that a custom class can be used.  Don't know how to map all of the props onto the custom component.

Try this pattern:
<Field model="...">
{(fieldValue) => <CustRadio {...} />}
</Field>

Is the {...} literal?  This throws an error for me

Oh, sorry - that is just a placeholder for you to do whatever you want with the fieldValue, such as...
<Field model="...">
{(fieldValue) => <CustRadio valid={fieldValue.valid} />}
</Field>

etc.

Somehow the binding of the data is lost when using the custom component.  The radio buttons aren't mapped back to the model.

Can you post what you currently have in www.esnextb.in ?

Actually I ended up moving the whole Field into the custom component and that ended up working.

Awesome! Would love if you could share your solution here for others to see.


Add translators, translation strategy and tests (major design changes)

This pr adds translators, translation strategies and tests to the package. This includes major design changes. How the features are used is explained as follows. Furthermore an upgrade guide describes the breaking changes.
Translators
Translators have the purpose to bind a translatable attribute to a model. A build in example is the AstrotomicTranslator that updates models that are translated by the astrotomic/laravel-translatable package.
Creating A Translator
A translator must extend the AwStudio\Deeplable\Translators\BaseTranslator class which has 2 abstract methods:
class AstrotomicTranslator
{
    protected function translateAttribute(Model $model, $attribute, $locale, $translation)
    {
        $model->translateOrNew($locale)->setAttribute($attribute, $translation);
    }

    public function getTranslatedAttributes(Model $model, $locale)
    {
        return array_keys($model->getTranslationsArray()[$locale] ?? []);
    }
}

Registering The Translator
A translator may be registered in a Service Provider like this:
use AwStudio\Deeplable\Translators\Resolver;
use Astrotomic\Translatable\Contracts\Translatable;

public function register()
{
    Translator::register(Translatable::class, function () {
            return new AstrotomicTranslator($this->app['deeplable.api']);
    });
}

Using The Translator
The translator can then be used like this:
use AwStudio\Deeplable\Facades\Translator;
use Astrotomic\Translatable\Contracts\Translatable;

Translator::get(Translatable::class)->translate($post, 'de', 'en'); // Translates the whole model from en to de
Translator::get(Translatable::class)->translateAttributes($post, ['title', 'text'], 'de', 'en'); // Translates attributes title and text from en to de

Translation Strategy
Given the case that different models need different translators, a translation strategy can be specified in a service provider like this:
use AwStudio\Deeplable\Facades\Translator;
use AwStudio\Deeplable\Translators\Resolver;
use Astrotomic\Translatable\Contracts\Translatable;

public function register()
{
    Translator::strategy(function(Model $model) {
        if($model instanceof Translatable) {
            return Translatable::class;
        }
        // something else...
    });
}

The correct translator can now be received like this:
Translator::for($post)->translate(...);

Upgrade Guide
The config key deeplable.api_url changed:
-https://api-free.deepl.com/v2/translate
+https://api-free.deepl.com/v2

cc @shad0w-rep, @larshanskrause this might be interesting for you, please notice the breaking changes:
The config key deeplable.api_url changed:
-https://api-free.deepl.com/v2/translate
+https://api-free.deepl.com/v2


Update for R 3.5.1

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

Using toolchain directly in this manner is deprecated.  Consider using the compilers outlined here.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@bgruening I'm not sure what to do here. The linter recommended using the new compilers, but when I reverted to the previous version of the recipe, it broke the AppVeyor build.
https://github.com/conda-forge/r-markdown-feedstock/commit/d13014d2231402d023e6a6a8151da62a980c24e0


Ghost will fail to start if theme name can be interpreted as a number

Suppose Ghost theme is named 1.4 (which actually happened when I uploaded older Casper theme release downloaded from Github as 1.4.zip).
When you select the theme in the settings, everything will work fine. Until you restart the Ghost.
It will fail to start again. The reason is that in the database, theme name is saved as 1.4. Somehow, this string gets converted to number, causing some major confusion. In order to fix this, you'll have to edit the database manually, changing theme name to "1.4" (with quotes).
Here is traceback extracted from a log file:
The server has encountered an error.","stack":"InternalServerError: The server has encountered an error.
    at new GhostError (/var/www/ghost/versions/1.14.1/core/server/errors.js:9:26)
    at /var/www/ghost/versions/1.14.1/index.js:38:15
    at tryCatcher (/var/www/ghost/versions/1.14.1/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/var/www/ghost/versions/1.14.1/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/var/www/ghost/versions/1.14.1/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/var/www/ghost/versions/1.14.1/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/var/www/ghost/versions/1.14.1/node_modules/bluebird/js/release/promise.js:689:18)
    at Async._drainQueue (/var/www/ghost/versions/1.14.1/node_modules/bluebird/js/release/async.js:133:16)
    at Async._drainQueues (/var/www/ghost/versions/1.14.1/node_modules/bluebird/js/release/async.js:143:10)
    at Immediate.Async.drainQueues (/var/www/ghost/versions/1.14.1/node_modules/bluebird/js/release/async.js:17:14)
    at runCallback (timers.js:672:20)
    at tryOnImmediate (timers.js:645:5)
    at processImmediate [as _immediateCallback] (timers.js:617:5)

TypeError: Path must be a string. Received 1.4
    at assertPath (path.js:7:11)
    at join (path.js:1218:7)
    at Object.readPackage [as one] (/var/www/ghost/versions/1.14.1/core/server/utils/packages/read-packages.js:46:24)
    at Object.loadOneTheme (/var/www/ghost/versions/1.14.1/core/server/themes/loader.js:20:10)
    at Object.initThemes [as init] (/var/www/ghost/versions/1.14.1/core/server/themes/index.js:31:14)
    at /var/www/ghost/versions/1.14.1/core/server/index.js:58:20
    at tryCatcher (/var/www/ghost/versions/1.14.1/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/var/www/ghost/versions/1.14.1/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/var/www/ghost/versions/1.14.1/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/var/www/ghost/versions/1.14.1/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/var/www/ghost/versions/1.14.1/node_modules/bluebird/js/release/promise.js:693:18)
    at Promise._fulfill (/var/www/ghost/versions/1.14.1/node_modules/bluebird/js/release/promise.js:638:18)
    at Promise._resolveCallback (/var/www/ghost/versions/1.14.1/node_modules/bluebird/js/release/promise.js:432:57)
    at Promise._settlePromiseFromHandler (/var/www/ghost/versions/1.14.1/node_modules/bluebird/js/release/promise.js:524:17)
    at Promise._settlePromise (/var/www/ghost/versions/1.14.1/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/var/www/ghost/versions/1.14.1/node_modules/bluebird/js/release/promise.js:614:10)

It seems that #8505 was not fixed properly, after all.

I can confirm this behaviour. Just renamed the .zip file to 1.4 and after restarting getting the same error message.


Handling headers in HTTP requests

So when we have headers in the HTTP request, the code at http://curl.trillworks.com/#node is unable to handle it. Is it a feature that is yet to be implemented or have I just caught a bug? Want a helping hand?

The original use cases were pretty narrow, but it would be great to make it work for more.
Go ahead and send a pull request that includes a test case in test/test.js.

Actually, it seems like the headers do work, but for some reason you must have at least two of them.
That is, this:
curl http://example.com/ -H 'foo: bar'

fails with an "Error parsing curl command." message, but this:
curl http://example.com/ -H 'foo: bar'  -H 'foo2: bar2'

works properly.
@aravindkk this may be a work around for you at least.  Also I imagine this isn't too hard to track down in the code, seems like a silly little bug that's easily fixed.

Actually, here's a fix for this issue.
In util.js the code assumes that parsedArguments.H is an array, which is true when there is more than one -H value passed on the curl command line, but not when there is exactly one.
One easy way to address that is just to wrap the value of parsedArguments.H in an array if it isn't already an array, adding these three lines:
--- a/util.js
+++ b/util.js
@@ -22,6 +22,9 @@ var parseCurlCommand = function(curlCommand) {
     var headers;
     if (parsedArguments.H) {
         headers = {};
+        if (!Array.isArray(parsedArguments.H)) {
+          parsedArguments.H = [parsedArguments.H];
+        }
         parsedArguments.H.forEach(function (header) {
             if (header.indexOf('Cookie') !== -1) {
                 cookieString = header;

If you are uncomfortable modifying the content of parsedArguments (since it comes from minimist originally) you could obviously introduce a new variable to iterate over.
If I get around to it I can probably create a proper pull request for this, but it's pretty much a one line fix.

@rodw, thanks for digging into that. I've implemented your fix in 0.0.19. I'll publish to the website shortly.


Add built trigger line separator back in.

Replace inline styles with metadata class.
Move code block for "There are currently no pods for this service." that wasn't within tile.
Include container block for more consistent control of spaceing/margin/padding.

@liggitt updates


Add Format Converter

Add feature to convert from ONNX and DNNP to rlv, nnet, or vnnlib files without verification.

Codecov Report

Merging #36 (a5d7679) into develop (c34d599) will decrease coverage by 0.55%.
The diff coverage is 33.61%.

@@             Coverage Diff             @@
##           develop      #36      +/-   ##
===========================================
- Coverage    66.36%   65.81%   -0.56%
===========================================
  Files           82       85       +3
  Lines         6119     6222     +103
  Branches      1175     1194      +19
===========================================
+ Hits          4061     4095      +34
- Misses        1699     1769      +70
+ Partials       359      358       -1

Impacted Files
Coverage Δ

dnnv/__main__.py
0.00% <0.00%> (ø)

dnnv/cli/__init__.py
20.54% <0.00%> (-0.79%)
:arrow_down:

dnnv/verifiers/common/reductions/iopolytope.py
64.42% <ø> (-0.08%)
:arrow_down:

dnnv/properties/transformers.py
73.35% <20.00%> (-0.47%)
:arrow_down:

dnnv/properties/vnnlib.py
23.25% <25.00%> (-1.34%)
:arrow_down:

dnnv/verifiers/convert/utils.py
26.92% <26.92%> (ø)

dnnv/verifiers/convert/__init__.py
45.45% <45.45%> (ø)

dnnv/properties/base.py
75.25% <100.00%> (+0.03%)
:arrow_up:

dnnv/verifiers/convert/errors.py
100.00% <100.00%> (ø)

dnnv/nn/transformers/simplifiers/__init__.py
85.71% <0.00%> (-3.58%)
:arrow_down:

... and 3 more

Continue to review full report at Codecov.

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


Preload turf.js on the site for programmatic manipulation of features

It could be handy to have turf already preloaded on the site. I tried to include it by dynamically injecting a <script> tag, but it refuses because of the Content Security Policy.
This would enable more complex manipulation of the geojson features.
One of my use-cases is to be able to export many polygons as a single multi-polygon, which I can input in another system.

@walling To avoid feature creep here, have you considered piping features into dropchop.io? It accepts gist IDs the same way that geojson.io does. e.g.:
http://dropchop.io/?gist=e1028889229343fa8ed8a6e74d21f5d0

Thanks, it looks interesting from the first quick look. I'll check it out further!
Btw. I solved my original issue by creating a small user script for Tampermonkey, which does the processing for me. What I like about geojson.io is that I can copy-paste my GeoJSON back and forth between systems.
I understand that including more libraries is feature creep, so you can just close this issue.

This is already possible, albeit not built-in, but via the console. I've added a tip for how: https://github.com/mapbox/geojson.io/blob/gh-pages/API.md#protips


progress bar appears on the login screen - which should not happen

If you go to http://www.droneshare.com/login you see the progress bar loading at the top of the window - though there really shouldn't be anything loading at that time...

I can't seem to recreate it -- what browser and platform are you using?


It shows how the garbage collection will be done. However, the piece missing is actually figuring out which hashes to keep. I didn't do that yet because I am having trouble populating the database - not able to read the nwb file now (ndx_franklab_novela may have changed?)
Also:
my conda was having trouble loading ghostipy -- so I removed it as a conda dependency, and kept it as a pip dependency

First, thank you.
As far as the ndx-franklab-noveal, it has indeed changed; I had to remove it from the repo and use the conda version. Have you tried that?
And pip is fine for ghostipy.
Loren
Loren M. Frank
Professor
Howard Hughes Medical Institute
Kavli Institute for Fundamental Neuroscience
Department of Physiology
University of California, San Francisco
Office Phone:<PHONE_NUMBER>

On Jul 13, 2020, at 12:33 PM, Jeremy Magland<EMAIL_ADDRESS>wrote:
Added devel/garbage_collection.py which is a WIP.
It shows how the garbage collection will be done. However, the piece missing is actually figuring out which hashes to keep. I didn't do that yet because I am having trouble populating the database - not able to read the nwb file now (ndx_franklab_novela may have changed?)
Also:
my conda was having trouble loading ghostipy -- so I removed it as a conda dependency, and kept it as a pip dependency
You can view, comment on, or merge this pull request online at:
https://github.com/LorenFrankLab/nwb_datajoint/pull/4 https://github.com/LorenFrankLab/nwb_datajoint/pull/4
Commit Summary
garbage collection and couple minor edits
File Changes
A devel/garbage_collection.py https://github.com/LorenFrankLab/nwb_datajoint/pull/4/files#diff-6925f0c75d344f03c73931049f496d44 (59)
M environment.yml https://github.com/LorenFrankLab/nwb_datajoint/pull/4/files#diff-b7cb75ca59993a879e29bed8cd8469b8 (3)
M setup.py https://github.com/LorenFrankLab/nwb_datajoint/pull/4/files#diff-2eeaed663bd0d25b7e608891384b7298 (2)
Patch Links:
https://github.com/LorenFrankLab/nwb_datajoint/pull/4.patch https://github.com/LorenFrankLab/nwb_datajoint/pull/4.patch
https://github.com/LorenFrankLab/nwb_datajoint/pull/4.diff https://github.com/LorenFrankLab/nwb_datajoint/pull/4.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/LorenFrankLab/nwb_datajoint/pull/4, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABV4PSOWFZBAWUEOTAPA5ADR3NORDANCNFSM4OYZMOBQ.


reformat HTTP API guide

This is in preparation for #113.

Updated PR based on typo feedback.

These typos make me wonder if we could hook up aspell checking with an accepted dictionary list...

Updated PR with different headings.


Where to Pass trino.s3.credentials-provider Parameter in Helm Chart?

I'm working with a Helm chart for deploying Trino and need to configure the trino.s3.credentials-provider parameter to use com.amazonaws.auth.InstanceProfileCredentialsProvider for S3 access.
Could someone please guide where to specify the trino.s3.credentials-provider parameter in the Helm chart configuration?
Any assistance would be appreciated!

Hi
To access s3, I'm using IAM role with serviceAccount
Create an IAM role + IAM policy to access s3
Define the role arn in annotation eks.amazonaws.com/role-arn

    serviceAccount:
      create: true
      annotations:
        eks.amazonaws.com/role-arn: arn:aws:iam::YOUR_AWS_ACCOUNT_ID:role/ROLE_NAME

trino.s3.credentials-provider goes into the catalog properties, so additionalCatalogs


[Untested] Utilities library

It would be useful to have a utilities library of miscellaneous common operations. We could add more functionality later, but it currently has:

A function for printing an array of uint8_t bytes in hex format
Defines the F_CPU macro for <util/delay.h> once so it doesn't need to be redefined in every file we use delays

Since this always requires UART to be active, I think we should just add it to the UART library as it's own function.

For the time being, I think we can do without a utilities library; the print hex function is useful, and although it is slightly annoying to write out the value of F_CPU each time, the compiler reminds you, so nothing breaks if you forget.

I think it would be a problem if someone defines F_CPU as the wrong value when rewriting it, might be good to have a standard constant value
How would you test that UART actually printed the right string and that the delay is for the right amount of time?

@brunofalmeida As an external program, the test harness can test both delays and UART output, so testing is not an issue. See the time parameter in the test_t struct in test.h and the associated commit message for timing-based test info, as well as the arithmetic test, which includes a delay test. Testing UART output would be easier with a new ASSERT_STR macro, but that isn't too difficult to add; I'll make a note of it.
I agree that it would be problematic if someone defined F_CPU incorrectly, but I think that the cost of hauling around another library isn't worth it.

Ok that makes sense. I'd still like to add print_hex_bytes() to the UART library though.

@brunofalmeida @dhanyaa97 See #54


[Doc] toc entry for json_length

What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

run starrocks_admit_test

@mergify backport branch-2.4


feat: remove transformed collections

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

performance/code quality

What is the current behavior? (You can also link to an open issue here)

Some collection documents are transformed into classes instead of interfaces when being loaded from the db.
This results in an iteration over every propery on the documents, and some copying, and so will be a small performance penalty.

What is the new behavior (if this is a feature change)?

Instead of this, we should move the methods off the classes and feed them the interface form as a parameter.
The classes can then be removed, as they serve no purpose.

Other information:

This has been split into many many commits, to aid in reviewing. It might be best to not squash when merging to keep this readability instead of a large touching everything commit
Status

[ ] Code documentation for the relevant parts in the code have been added/updated by the PR author
[ ] The functionality has been tested by the PR author
[ ] The functionality has been tested by NRK

Codecov Report

Merging #633 (08b5710) into release38 (102085a) will increase coverage by 15.20%.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           release38     #633       +/-   ##
==============================================
+ Coverage      67.25%   82.46%   +15.20%
==============================================
  Files            269       12      -257
  Lines          18704     1015    -17689
  Branches        4167      215     -3952
==============================================
- Hits           12580      837    -11743
+ Misses          6082      177     -5905
+ Partials          42        1       -41

Impacted Files
Coverage Δ

meteor/client/lib/rundown.ts

meteor/lib/Rundown.ts

meteor/lib/collections/AdLibActions.ts

meteor/lib/collections/AdLibPieces.ts

meteor/lib/collections/Blueprints.ts

meteor/lib/collections/BucketAdlibActions.ts

meteor/lib/collections/BucketAdlibs.ts

meteor/lib/collections/Buckets.ts

meteor/lib/collections/CoreSystem.ts

meteor/lib/collections/Evaluations.ts

... and 247 more

Continue to review full report at Codecov.

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

@nytamin To see how bad it will be for TV2, I have done a crude simulation of the merge conflict they will end up with.
I took a branch that looked to be most up to date on nrk changes, and updated it to release38. (ignoring all merge conflicts)
Then I merged this branch into that, and looked at what new conflicts arose.
Quite a few files had new conflicts:

# Conflicts:
#	meteor/client/ui/RundownView.tsx - method renaming
#	meteor/client/ui/RundownView/RundownTiming/RundownTimingProvider.tsx - method renaming
#	meteor/client/ui/Shelf/AdLibPanel.tsx - import
#	meteor/client/ui/Shelf/AdLibRegionPanel.tsx - method renaming & import
#	meteor/client/ui/Shelf/BucketPanel.tsx - import
#	meteor/client/ui/Shelf/TimelineDashboardPanel.tsx - import
#	meteor/lib/api/triggers/actionFilterChainCompilers.ts - import
#	meteor/lib/collections/PartInstances.ts - code change
#	meteor/lib/collections/RundownPlaylists.ts - code change
#	meteor/lib/collections/Segments.ts - code change
#	meteor/lib/rundown/__tests__/rundownTiming.test.ts - import
#	meteor/server/api/ingest/__tests__/ingest.test.ts - code change
#	meteor/server/api/ingest/generation.ts - code change
#	meteor/server/api/ingest/rundownInput.ts - import
#	meteor/server/api/playout/adlib.ts - code change
#	meteor/server/api/playout/lib.ts - import
#	meteor/server/api/rundownPlaylist.ts - code change
#	meteor/server/api/userActions.ts - code change
#	meteor/server/cache/CacheCollection.ts - code change

a majority of those are due to the changed imports, or the methods having moved. Only a few are related to the interface renaming. There are a few new uses of the old names that will need to be updated, but typescript will make that easy, to track down (up to 48 cases of the wrong naming being used, merge conflicts add some uncertainty to that number)
From this, I don't think that removing the bulk renames from this PR will make merging much easier. But I am open to removing those commits anyway

@nytamin I have removed the commits which did the bulk renames. They didnt do anything for performance, solely code readability and tidiness.
It looks like some of those lines remain, as they got pulled back in by rebase conflicts


Documentation update

Can the readme, and package descriptions, please be updated to explain what these packages are? When do you need what package?!? If they are the same why are there 2 packages?
AWSSDK.CloudSearch

    Amazon CloudSearch is a managed service in the AWS Cloud that makes it simple and cost-effective to set up, manage, and scale a search solution for your website or application.

AWSSDK.CloudSearchDomain

    Amazon CloudSearch is a managed service in the AWS Cloud that makes it simple and cost-effective to set up, manage, and scale a search solution for your website or application.

@phillip-haydon, thanks for the feedback on this.  We'll get it updated.  AWSSDK.CloudSearch is the configuration API for setting up CloudSearch domains.  AWSSDK.CloudSearchDomain is the API for both document management (adding, deleting, replacing) within your domain and searching your domain.  You can see more details by looking at the code or referencing the service's documentation here:  https://docs.aws.amazon.com/cloudsearch/latest/developerguide/api-ref.html

Fixed https://www.nuget.org/packages/AWSSDK.CloudSearchDomain/


Char instance

I'd like to be able to format Char:

Integral formatting will display the integral value of the char
String formatting will display the char (and is the default)
Floating formatting will display purple unicorns.

That's trivial to define a PyFToString instance for String formatting, but for now Integral and Floating formatting uses python default RealFrac and Integral type classes and nobody sane wants to derive Integral for Char.
I propose to integrate PyFIntegral and PyFFloating instead of Integral and Floating default type class, with a default instance for Integral and Floating classes (similar to the default instance for PyfString).
Pros: we will be able to display / format stuffs which are not Integral, but which have a meaning to be displayed as Integral.
Cons: PyF was able to format anything Integral or RealFrac for free, now users will have to derive instances. PyF will have to derive the basic instances for common types. This may generate a bunch of orphan instances.

#71 introduced PyFToRealFrac for "float"-like numbers with an "all-types" instances for Real. The same can be done for PyFToIntegral in order to support Char.

Closed by #71


Please support or (<|>) Deriver?

In the project's business scenario, three derivations are used, namely =>,<=>,<|>, the first two LoginNGs are supported, XOR <|> It seems that I don't support it now. What should I do?

Hi! There are several reasons why we decided not to support XOR (one of which is that its meaning with more than two operands is not intuitive for many people).
If you create the formulas directly, you can formulate a XOR b as f.and(f.or(f.variable("a"), f.variable("b")), f.or(f.literal("a", false), f.literal("b", false))). If you need a parser, you will probably need to copy and adjust one of our parsers or write your own.

Got it, thank you.😊


Cable Creation Failed

cable = nb.dcim.cables.create(termination_a_type='dcim.interface',termination_a_id=interface_a.id, termination_b_type='dcim.interface',termination_b_id=interface_b.id, status="connected")
print(cable.id)

output  =
switch-01
Interface_a: Ethernet1/18
Interface_a id: 2354
Interface_b: TenGigabitEthernet1/49
Interface_b id: 2283
pynetbox.core.query.RequestError: The request failed with code 400 Bad Request: {'__all__': ['Must define A and B terminations when creating a new cable.']}

Seeking advice on how to write the script to create a cable.

Works fine with this method
   cable = nb.dcim.cables.create(
            # a_terminations=[remote_interface],
            # b_terminations=[local_interface],
            a_terminations=[
                {
                    "object_type": "dcim.interface",
                    "object_id": local_interface.id,
                }
            ],
            b_terminations=[
                {
                    "object_type": "dcim.interface",
                    "object_id": remote_interface.id,
                }
            ],
        )


error when deploy to azure from visual studio code"Azure IoT Device Workbench: Deploy to Azure".

Does this occur consistently?
Repro steps:

Action: azureFunctions.deploy
Error type: Error
Error Message: Failed to deploy path that does not exist: c:\Users\tmala\Documents\IoTWorkbenchProjects\examples\devkit_translator\Functions\bin\Release\netcoreapp2.1\publish
Version: 0.22.0
OS: win32
OS Release: 10.0.18363
Product: Visual Studio Code
Product Version: 1.44.2
Language: en

Call Stack
Object.<anonymous> extension.bundle.js:281:26571
fulfilled extension.bundle.js:281:26075

@tmalahlela did the publish task succeed? That path won't exist if it failed. Please check your task output and if that doesn't help, add more detailed repro steps here


matter-labs

zweite stufe Sicherheit einfügen

Hi there, thanks so much for your suggestion. I'm linking to our Audits and Bug Bounty pages for more information on how we are proactively dealing with security issues. I have passed your suggestion on to our security team. Thanks again.


Back butten press wont stop the service, But would the service stops when the app closes ?

Hi @contactsamie , yes you can stop the service when the app closes by calling StopBackgroundService method inside OnSleep method of your App.cs
// Called each time the application goes to the background.
protected override void OnSleep()
{
    BackgroundAggregatorService.StopBackgroundService();
}


feat: add a nonce key override to support parallel nonces (#462)

Pull Request Checklist

[ ] Did you add new tests and confirm existing tests pass? (yarn test)
[ ] Did you update relevant docs? (docs are found in the site folder, and guidelines for updating/adding docs can be found in the contribution guide)
[ ] Do your commits follow the Conventional Commits standard?
[ ] Does your PR title also follow the Conventional Commits standard?
[ ] If you have a breaking change, is it correctly reflected in your commit message? (e.g. feat!: breaking change)
[ ] Did you run lint (yarn lint:check) and fix any issues? (yarn lint:write)
[ ] Did you follow the contribution guidelines?

PR-Codex overview
The focus of this PR is to enhance the buildUserOperation functionality and update links in the documentation.
Detailed summary

Updated buildUserOperation to support overriding nonce key
Updated links in the documentation for Light Account deployment addresses
Added nonceKey field to UserOperationStruct type
Modified getNonce function to accept a nonceKey parameter

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

wait what's happened here? I thought we merged this in already?


How to install?

First off, very excited that this project exists!
I'm looking for a solution to manage our Cloudflare configuration alongside other K8s resources.
Unfortunately, I'm not able to try this project as as the installation docs seem to be outdated.

Kubeflare requires Kubernetes 1.16 or later to install.
To install the current version of Kubeflare:
kubectl apply -f https://git.io/kubeflare

https://git.io/kubeflare leads nowhere:
❯ curl -i https://git.io/kubeflare
HTTP/1.1 404 Not Found

ping @diamonwiggins

@lmakarov sorry for the late reply. I will get the README updated this week as well. there is much to be done here, and we're just as excited about this project as you 😄

@lmakarov A quick and dirty to get you started should be:
clone repo
kubectl apply -f config/crds/v1

Apply the following
apiVersion: apps/v1
kind: Deployment
metadata:
  name: kubeflare
spec:
  replicas: 1
  selector:
    matchLabels:
      app: kubeflare
  template:
    metadata:
      labels:
        app: kubeflare
    spec:
      containers:
      - env:
        - name: CF_API_EMAIL
          value<EMAIL_ADDRESS>        - name: CF_ZONE_ID
          value: your-zone-id
        - name: CF_ZONE_NAME
          value: your-zone-name
        - name: CF_API_KEY
          valueFrom:
            secretKeyRef:
              key: api-key
              name: cf-api-key
        image: replicated/kubeflare-manager:0.1.0
        imagePullPolicy: IfNotPresent
        name: kubeflare

@diamonwiggins thanks, that gave me a starting point.
The final working solution ended up being way more complicated and took some time to figure out.

Apply the crds from the repo:

clone repo
kubectl apply -f config/crds/v1

Deploy kubeflare using the manifest below (namespace, RBAC, deployment)

---
apiVersion: v1
kind: Namespace
metadata:
  name: kubeflare-system

---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: kubeflare
rules:
- apiGroups: ['']
  resources:
  - namespaces
  - secrets
  verbs: [get, list, watch]
- apiGroups: [crds.kubeflare.io]
  resources: ['*']
  verbs: [get, list, watch, update, patch, create, delete]

---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: kubeflare
  namespace: kubeflare-system

---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: kubeflare
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: kubeflare
subjects:
- name: kubeflare
  namespace: kubeflare-system
  kind: ServiceAccount

---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: kubeflare
  namespace: kubeflare-system
spec:
  replicas: 1
  selector:
    matchLabels:
      app: kubeflare
  template:
    metadata:
      labels:
        app: kubeflare
    spec:
      serviceAccountName: kubeflare
      containers:
      -
        name: kubeflare
        image: replicated/kubeflare-manager:0.1.0
        imagePullPolicy: IfNotPresent
        env:
          - name: CF_API_EMAIL
            value: <CF_API_EMAIL>
          - name: CF_ZONE_ID
            value: <CF_ZONE_ID>
          - name: CF_ZONE_NAME
            value: <CF_ZONE_NAME>
          - name: CF_API_KEY
            #value: <CF_API_KEY>
            valueFrom:
              secretKeyRef:
                key: api-key
                name: cf-api-secret
        resources:
          limits:
            cpu: 50m
            memory: 64Mi
          requests:
            cpu: 10m
            memory: 32Mi

Create the secret with the Cloudflare Global API Key in the kubeflare-system namespace:

kubectl -n kubeflare-system create secret generic cf-api-secret --from-literal api-key=<CF_API_KEY>

Create a kubeflare APIToken using the manifest below

apiVersion: crds.kubeflare.io/v1alpha1
kind: APIToken
metadata:
  name: cf-api-token
  namespace: kubeflare-system
spec:
  email: <CF_API_EMAIL>
  name: "Global API Key"
  #value: <CF_API_KEY>
  valueFrom:
    secretKeyRef:
      key: api-key
      name: cf-api-secret

The use case for these APITokens is unclear to me.
Cloudflare API creds are already set in the Deployment. Why would you need to set it again at the zone level via an APIToken?
Also, the name APIToken leads to a confusion with Cloudflare API Tokens, which is an alternative (newer) authentication mechanism and which you DO NOT use here. Instead, it's again that Cloudflare Global API Key that goes here.

Next, load your zone definition with the manifest below:

---
apiVersion: crds.kubeflare.io/v1alpha1
kind: Zone
metadata:
  name: example.com
  namespace: kubeflare-system
spec:
  apiToken: cf-api-token
  settings:
    alwaysOnline: true
    # Zone setting mapping can be found here:
    # https://kubeflare.com/api/zone/#settings

Finally, you can manage some DNS entries

apiVersion: crds.kubeflare.io/v1alpha1
kind: DNSRecord
metadata:
  name: www.example.com
  namespace: kubeflare-system
spec:
  record:
    content: <IP_ADDRESS>
    name: www.example.com
    priority: 0
    proxied: false
    ttl: 1
    type: A
  zone: example.com

@lmakarov thanks for working through this and awesome to see you were able to get it running despite the lack of documentation at the moment :).

The use case for these APITokens is unclear to me. Cloudflare API creds are already set in the Deployment. Why would you need to set it again at the zone level via an APIToken?

Your confusion is warranted. First, you don't need any of the environment variables in the deployment example I gave you, so you can remove those and rely solely on the APIToken/Zone CRDs  for auth. Second, the Manager should just be relying on an APIToken everywhere. Looks like I corrected that in master, but its not released yet. https://github.com/replicatedhq/kubeflare/commit/93ec3d9364b6e287be9d05ae85a3237c85f4a613#diff-efa17ace5b45857940b854055d06a11b52ddc018acd36ab0a04e9e3072c27e87R40
I got sidetracked with a few things this week, but still planning on working on this late tomorrow/this weekend. Please feel free to create additional issues for any other problems you run into/suggest any improvements!

Will document helm in the future when a chart is created, but for now the instructions for kubectl have been updated https://github.com/replicatedhq/kubeflare/pull/16


factor Mesh.load for files or constructed meshio.Meshes

I started looking at the skfem.Mesh.boundaries attribute used in test_mesh.Loading.  Very nice!  This will make the top-level scripts much more readable.
I wanted to improve examples/ex14.py in this way but its skfem.MeshTri lacked this attribute; an skfem.Mesh only gets boundaries if constructed by classmethod Mesh.load and that takes the name of a file whereas there's no accessible file containing the mesh in the example.  It uses pygmsh.generate_mesh which writes the mesh in a tempfile.NamedTemporaryFile.
So I could eschew generate_mesh in favour of writing geom.get_code() to a GEO file and then running Gmsh myself in a subprocess to generate the MSH file, but that's verbose and duplicates a lot of what's in generate_mesh.
Instead, what about factorizing Mesh.load so that everything after the definition of
        meshdata = meshio.read(filename)

is delegated to another classmethod, say from_meshio_mesh and then either load calls that or the user if they have a meshio.Mesh (say by passing the values returned from pygmsh.generate_mesh) can call it directly.
I'll attempt an implementation.

Yes, I don't object. There is still the one TODO in the edge loading that I haven't had time to fix but it doesn't matter.


Get cloud status for all locations in watchlist for given user

Once we retrieved cloud status for one location id, get cloud status for all location id's for given user.

This should no longer be needed once #42 has been implemented because that will add cloud data as soon as a location is added.

#42 is now closed. all added locations will now have cloud data.


Suggestion, file sharing modules in prosody.

Maybe we could modify the prosody guide to enable http_file(for downloading files) and http_upload(for uploading files) modules. I think it would make it a bit more normie friendly because most IM's allow you to share files.

Sounds like a good idea.

I am going to try and write it up later this week or maybe this weekend. But if anyone else wants to write it up, here is a good guide that shows how to do this. It is litterally just adding a Component "uploads.example.com" "http_upload" and a few options like max upload size. Here is the documentation for the module. Please note that they say specifically to NOT ADD IT under modules_enabled. Just add the component!

Also here is a guide from the same website that shows how to setup prosody for audio/video calling. It is just setting up a turn server(for which we already have a guide) and configuring the options in the prosody config.


[Triton-MLIR][FRONTEND] Fix the implicit broadcasting rule

This PR solves the cast issue that appears in some tutorial code.
Problem
The frontend cannot compile the following code because tensor<f32> returned by tl.max(row, axis=0) was not cast properly to tensor<256xf32>, which is the type of row.
import triton
import triton.language as tl

@triton.jit
def softmax_kernel(
    output_ptr, input_ptr,
    BLOCK_SIZE: tl.constexpr
):
    col_offsets = tl.arange(0, BLOCK_SIZE)
    row = tl.load(input_ptr + col_offsets)
    row_minus_max = row - tl.max(row, axis=0) # <=================== This line
    tl.store(output_ptr + col_offsets, row_minus_max)

if __name__ == "__main__":
    output = triton.compile(softmax_kernel, "*fp32,*fp32", device=0, constants={'BLOCK_SIZE': 256}, output="ttir")
    print(output)

Solution
This PR fixes this issue by fixing/extending the implicit broadcast semantics. As a result, the code above will be translated into the following (specifically,  tt.expand_dims is issued for the reduced value %4)
module {
  func @softmax_kernel__Pfp32_Pfp32__2c256(%arg0: !tt.ptr<f32>, %arg1: !tt.ptr<f32>) {
    %0 = tt.make_range {end = 256 : i32, start = 0 : i32} : tensor<256xi32>
    %1 = tt.splat %arg1 : (!tt.ptr<f32>) -> tensor<256x!tt.ptr<f32>>
    %2 = tt.addptr %1, %0 : tensor<256x!tt.ptr<f32>>
    %3 = tt.load %2 {cache = 1 : i32, evict = 1 : i32, isVolatile = false} : tensor<256xf32>
    %4 = tt.reduce %3 {axis = 0 : i32, redOp = 5 : i32} : tensor<256xf32> -> tensor<f32>
    %5 = tt.expand_dims %4 {axis = 0 : i32} : (tensor<f32>) -> tensor<1xf32>
    %6 = tt.broadcast %5 : (tensor<1xf32>) -> tensor<256xf32>
    %7 = arith.subf %3, %6 : tensor<256xf32>
    %8 = tt.splat %arg0 : (!tt.ptr<f32>) -> tensor<256x!tt.ptr<f32>>
    %9 = tt.addptr %8, %0 : tensor<256x!tt.ptr<f32>>
    tt.store %9, %7 : tensor<256xf32>
    return
  }
}

Technical details
Previously, the following 3 cases are handled.
scalar [binop] tensor -> splat(scalar) + tensor   # note: scalar != 0D-tensor
tensor [binop] scalar -> tensor + splat(scalar).  # note: scalar != 0D-tensor
nD-tensor [binop] mD-tensor -> broadcast(...)     # only if n == m

This patch newly allows the following.

0D-tensor (e.g., tensor<f32>)
nD-tensor [binop] mD-tensor where n != m, by adding axes to the smaller tensor, which will be broadcast before (for example) [binop].

For example:

tensor<f32> -> tensor<1x1x1xf32>
tensor<128xf32> -> tensor<128x1xf32>

It seems that I am still a first-time contributor... Maybe I need to contribute to the master branch of Triton. @ptillet I would appreciate it if you could approve running workflows.

Yeah, actually I think you should push this patch to master, since it is an issue that also affects the triton main branch I presume? You could re-use test_core.py and just add a test_implicit_broadcast rule

Wait, actually I guess softmax works on master so the issue isn't there? This is odd, because as far as I remember they use the same semantic analysis.

Thanks for your review, @ptillet !

tl.max returns a scalar on master and a 0D tensor in the MLIR branch

Yes, it seems so. First, the following is the result of the above kernel with the current Triton.
def void softmax_kernel__Pfp32_Pfp32__2c256(f32* output_ptr .aligned(16), f32* input_ptr .aligned(16)){
entry:
  %0 = make_range[0 : 256] i32<256>;
  %1 = splat f32*<256> input_ptr;
  %2 = getelementptr f32*<256> %1, %0;
  %3 = unmasked_load f32<256> %2;
  %4 = reduce f32 %3;    # <======================== This line (though type is not explicit in IR)
  %5 = splat f32<256> %4;
  %6 = fsub f32<256> %3, %5;
  %7 = splat f32*<256> output_ptr;
  %8 = getelementptr f32*<256> %7, %0;
  unmasked_store void %8, %6;
  ret void;
}

Both of Triton and the current Triton-MLIR allow reduce to generate a scalar value.

The corresponding Triton-MLIR code and the change made by this PR:
https://github.com/openai/triton/pull/663/files#diff-a28ba3a22fe48841e9eeede9c8ad5585e8f80b93e72397991d56a0ff2a4bb376R978

This PR changes the output type of reduce from scalar to 0d-tensor for Triton-MLIR; this is because the MLIR infrastructure handles types more strictly and thus does not accept scalar value as a result of reduce.
I can change the behavior of the current Triton to this new Triton-MLIR behavior proposed by this PR, but I am not sure if it makes much sense since master is working well.
What would be your suggestions?

I actually wouldn't expect the master branch of the public repo to work for all the cases tested in test_cast.py. I guess my main worry with this PR is that the test doesn't actually test much. Here's what we can do:

For now, I can merge this PR to unblock the softmax situation
When phil/new-runtime lands into master, we should also merge this PR against master, and add a proper  test_implicit_broadcast to test_core.py that can test the new code completely.
When we merge triton-mlir into master, we don't merge test_cast.py as it will duplicate test_core.py.

Does that look ok?

Yes it sounds great. In any case test_cast.py should be removed in the near future.


Usage example is confusing and doesn't follow best practises

NSError *anError = nil;
NBPhoneNumber *myNumber = [phoneUtil parse:@"6766077303"
                             defaultRegion:@"AT" error:&anError];
if (anError == nil) {
    // Should check error
    NSLog(@"isValidPhoneNumber ? [%@]", [phoneUtil isValidNumber:myNumber] ? @"YES":@"NO");
    …
} else {
    NSLog(@"Error : %@", [anError localizedDescription]);
}

Line 5 above says "Should check error", but after it already checked that anError was nil, so isValid should always return YES at this point? However, the order of these should be reversed according to the following:

If an error occurs, the writeToURL:... method will return NO, and update your anyError pointer to point to an error object describing the problem.
When dealing with errors passed by reference, it’s important to test the return value of the method to see whether an error occurred, as shown above. Don’t just test to see whether the error pointer was set to point to an error.

Source: Apple's "Dealing with Errors" page

It was port from google's libphonenumber javascript, so that is not good with obj-c.
Thanks, I will consider to change method logic for handling errors.


Importing a smaller subset of core-js modules instead of the whole co…

…re-js/shim
Fixes #23

:+1: for this to be merged in :)

:+1:


Restrictions on nested variables

Hi, I was just wondering if there was a reason why nested variables are restricted to only having alphanum plus underscores? This has caused issues in our dev environment because we can't do things like namespacing properties with dots, or doing array syntax properties, which would be very useful for our team. Is there any reason why this cannot be done with this package?
Also we're required to use v1.1 because we're on Laravel 5.1 LTS, so if we could get the enhancement made on that branch I'd appreciate it. If it's good to go into the package, I'd be willing to make the modification and submit a PR.
For clarification, what I'm looking for is the ability to do nested variables such as:
APP[0].URL=whatever

and then be able to nest those with:
API[0].URL={$APP[0].URL}

For the record, that's not really a use case we're looking for, it was just something easy I came up with off the top of my head. Thanks!

You can do this with https://github.com/josegonzalez/php-dotenv -- maybe vlucas/phpdotenv should think about using the env parser by m1:https://github.com/m1/Env like the josegonzalez/php-dotenv package?

The 1.1 branch is there for bug fixes. New stuff goes into 2.x.


Specify behavior of @CacheResult when a method returns a null value

Currently in the spec it states:

When a method annotated with @CacheResult is invoked the following must occur.

Generate a key based on InvocationContext using the specified CacheKeyGenerator
Use this key to look up the entry in the cache.
If an entry is found return it as the result and do not call the annotated method.
If no entry is found invoke the method.
Use the result to populate the cache with this key/result pair.

If the result returned by the method of step 4 is null, it is not specified what action should be taken. Null values cannot be placed directly into a CacheEntry since null is not allowed as a key or value in a JSr107 cache.
Step 5 might imply to some that a NullPlaceholder should be used in order to properly memoise the result of the method call - but this isn't stated explicitly so it could lead to differences in implementation.
Nothing needs to be added to the API to handle this, but the RI and any other implementation could implement this by creating something like a simple NullMethodResultPlaceholder object that was stored if the method result was null - and in step 3 if the entry found in looking up the key is the NullMethodResultPlaceholder then a simple null would be returned.
Because the of the intent of @CacheResult is to memoise the result of a method call, it seems that the most reasonable approach is to have it return a null value from the cache when the method returned null previously. Another option - which would be to have it silently ignore the null value and just return it without attempting to cache the null result would also be preferrable to throwing a NullPointerException - but whatever behavior is considered correct should be specified.
I have created a branch of the RI that supports caching null methods - https://github.com/ryangardner/RI/tree/cache-null-objects-in-cacheresult I can update that branch to match the latest and pull the changes into the RI
(I think I have commit access on the RI - but I'd rather not push something like this in directly without some input first)

I had advocated for a boolean flag in @CacheResult which allowed developers to specify if null values should be cached or not. With your input here I think I'll revisit that and add that feature using the placeholder object approach.

Added support for caching null values in @CacheResult and @CachePut


[feature-582] Update release version 1.5.1

Description
Change the versions from 1.5.0 to 1.5.1
GitHub Issues
List the GitHub issues impacted by this PR:

GitHub Issue #

https://github.com/dell/csm/issues/582

Checklist:

[x] I have performed a self-review of my own code to ensure there are no formatting, vetting, linting, or security issues
[x] I have verified that new and existing unit tests pass locally with my changes
[x] I have not allowed coverage numbers to degenerate
[ ] I have maintained at least 90% code coverage
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Backward compatibility is not broken

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration.
Manually tested with karavi-testing PR (https://eos2git.cec.lab.emc.com/CSM/karavi-testing/pull/194) and generated RPM version: karavi-authorization-1.5-1.x86_64.rpm

[x] e2e test for RPM and helm installation

Please update manual test details in the PR description for rpm file changes.

Updated in the description.

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

I somehow forgot to sign some of the commits. I've rebased all commits into one and signed. Requesting new approvals..

run e2e test


bumping react-plotly.js version

Should resolve some EventEmitter noise in the console :)

nice thanks!


publish<EMAIL_ADDRESS>

Requested by: @kamilogorek
Merge target: (default)
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Leave the #retract comment under this issue to retract the release (original issuer only).
Targets

[ ] crates
[ ] pypi
[ ] github

Targets marked with a checkbox have already been executed.  Administrators can manually tick a checkbox to force craft to skip it.

#retract

#retract


Add links to @willirath tutorial

I added them on the docs and in the README. Any comments, let me know!
This is how it looks on the documentation generated locally:
.

I wanted to say it is slightly weird to have the Tutorial non-section before the "Getting started" but I figure it is better to make the tutorial prominent rather than hidden in a sub-page.

Thanks for adding these!
There's a DOI now: https://doi.org/10.5281/zenodo.3337784
But the look and feel is much nicer in the Github repo.  So I'm not sure which to better include.  The DOI is much more stable, though.

I wanted to say it is slightly weird to have the Tutorial non-section before the "Getting started" but I figure it is better to make the tutorial prominent rather than hidden in a sub-page.

What about putting it in a Tutorials page under "Detailed Use"? There, we could also link the video from the front page and the slides / video of @andersy005's SciPy2019 talk.

I haven't had time to catch up with SciPy I have to admit (just watching Matt's talk now). My not super strong opinions:

I'd be in favour to make the tutorial(s) prominent. So maybe a reasonable compromise is to have a link with tutorials on the main documentation page that goes to a "Tutorials" sub-section.
I'd go for the github repo rather than the DOI. user-friendly trumps stability in this particular case.

Sounds great!

Pushed an update. I put this in the "Getting started" section, because I feel this is where I would expect a tutorial to show up rather than "detailed use". Let me know what you think.

Looks great!

If there's no objections within the next hour or so, I'd merge.


tests: Remove superfluous method for StackOverflowException test in the parser

Also remove public from all test classes and methods, since we've switched to junit5 and the pattern is to use package private. (Intellij also shows them as warnings by default).

Also remove public from all test classes and methods, since we've switched to junit5 and the pattern is to use package private. (Intellij also shows them as warnings by default).

Can we disable the warning? It's just needles busywork similar to the unused exception warning. There's no clear advantage of this style (?)  (and it breaks the snippet I use to create the test boilerplate)

Also remove public from all test classes and methods, since we've switched to junit5 and the pattern is to use package private. (Intellij also shows them as warnings by default).

Can we disable the warning? It's just needles busywork similar to the unused exception warning. There's no clear advantage of this style (?) (and it breaks the snippet I use to create the test boilerplate)

totally fine, I will drop the commit.


Popovers with redux

Hey, I just wanted to check if there was any kind of support for redux integration?
So far the popover content is rendered outside the "App" so the provider does not wrap the popover, making redux integration more difficult.
Has anyone found a good way of combining the two so far?

I have the same issue but with ThemeContext.Consumer

Just ran into the same issue today and we got around with by wrapping the content in a new Provider. Since we use a popover in more than place I made a wrapper component.
import React from 'react';
import Popover from 'react-tiny-popover';
import { Provider } from 'react-redux';
import store from '../redux/store';

type ConnectedPopoverProps = React.ComponentPropsWithoutRef<typeof Popover>;

const ConnectedPopover: React.FC<ConnectedPopoverProps> = props => (
  <Popover
    {...props}
    content={contentProps => (
      <Provider store={store}>
        {typeof props.content === 'function'
          ? props.content(contentProps)
          : props.content
        }
      </Provider>
    )}
  />
);

export default ConnectedPopover;

This can be solved by simply wrapping the parent of the PopOver container in the provider, sorry for the confusion.


Fix invalid free

memory error while dlclose

sorry, I used uv_replace_allocator, and the custom memory manager was closed before the process exit, so it accessed invalid memory (some config vars)
and UV_DESTRUCTOR is used in many places, I think I have to filter the NULL ptr by myself in the registered function, Thanks

if the memory manager closed before process exit, all of the memory will be freed, UV_DESTRUCTOR always read invalid memory... __attribute__((destructor)) depends on the compiler, and I cannot change the behavior of the memory manager.

@twose Do you want to send a PR that adds a note to the documentation? It currently says this in docs/src/misc.rst:
This function must be called before any other libuv function is called or
after all resources have been freed and thus libuv doesn't reference
any allocated memory chunk.

A casual reader might be misled to believe that "after all resources have been freed" means "after the event loop has been closed." It'd be better to be explicit and say "after libuv has been unloaded."

@bnoordhuis Thanks!
I agree with what you said, but my problem may not be misunderstanding this API
For example, If I try to write an extension for PHP, and I may use Zend Memory Manager, and the memory manager always exit before UV_DESTRUCTORS, unless Zend Memory Manager also use the __attribute__((destructor))

so I think that if it is possible to destruct these things through an API instead of compiler ways?


Advanced Mode

With a check box, an advanced mode will be started. This mode hides of shows complicated fields like hyperbolicity and so on.

done


Julia processes are not automatically shut down on Jupyter server shutdown

When closing an IJulia notebook, unless you do an explicit "shutdown kernel" command from within the notebook, its associated Julia process continues to run after the Jupyter server has terminated. Verified with Julia 1.5.3 and 1.6.0-beta1, on MacOS Catalina and Ubuntu 20.04.

As @rgobbel reported, I too have this issue on Fedora 32. I am running Julia 1.5.0 and IJulia version 1.23.1. Thanks for the help!

As @rgobbel reported, I too have this issue on Fedora 32. I am running Julia 1.5.0 and IJulia version 1.23.1. Thanks for the help!

Seems like this issue is related as well to bug #921. Any updates on this @stevengj or @fredrikekre?

Seems like this issue is related as well to bug #921. Any updates on this @stevengj or @fredrikekre?

Seems like this should be reported to the Jupyter repo, not IJulia?

Seems like this should be reported to the Jupyter repo, not IJulia?

I thought this was specifically an IJulia problem, but as far as I can tell everything works fine with Jupyter Lab--clean shutdown and no dangling processes whether I use the "Quit" command or just type a ctrl-C.

I encountered similar problems on a linux cluster. A lot of julia process still exist even after complete shut down of Julia and Jupyter-lab. Any updates on this?

same behavior even more "openly visible" if you use jupyter console --kernel=julia
in that case exit() will not even close the typical IJulia input zou can only help yourself via CTRL-Z but a ps will cintinue to show you the jupyter-console process which not even a kill command will be able to get rid off


Update embed_code.html

Lazy-loading YouTube video embeds (saves ~500KB on initial page load)

Hey @iamsushanth! This seems like a good approach. Would it be possible to update the tests to work with the new attribute so we can get this upstreamed?


[Image Request]:

Does this apply to existing image
Yes
What's the image for (e.g. NodeJS, Dotnet, Shenandoah, etc)
GraalVM
Image Request
Add support for GraalVM Java 20

Added GraalVM 21, which is an LTS release.


fix(dev site): remove insert key

Description
From docs team jira: removing references to insert key and the 'x-insert-key' header and replacing with license key and 'Api-Key' header.

@zuluecho9  I also wanted confirm if you still wanted this merged, as it's an older PR


Dev/ybronshteyn/issue85

Migrating to Jena 3.1.1

Thanks Yev,
Reviewed all changes.
Only one very minor formatting - line 305 in src/org/spdx/rdfparser/license/ListedLicenses.java should be indented.
All looks good - I also noticed you fixed some pre-existing bugs in the process :)

Suggest we branch the existing code to "SPDX 2.2-Java6Supported" then merge in the pull request.  That way, we could merge any critical fixes back for those few cases where Java6 or Java7 is still used.
We should do this after Monday so that we don't need to mess with the git.spdx.org synchronization.


sq.im.ImageContainer loads data incorrectly

Description

The sq.im.ImageContainer loads high-res Visium images (.tif) incorrectly - images show an unexpected checkerboard pattern. This issue persists across different Visium datsets. Other image libraries (like imageio) show that the image file is not corrupted. The same image could be successfully loaded in previous versions of squidpy.
Minimal reproducible example

import imageio
import os
from os.path import join
import matplotlib.pyplot as plt
import scanpy as sc
import squidpy as sq

# Adjust paths according to your system
storage = '/storage/groups/ml01/datasets/raw/20200909_PublicVisium_giovanni.palla'
folder = "2020_10XFluoVisium_HumanBrain1_giovanni.palla"
dataset_name = 'V1_Human_Brain_Section_1'

image_path = join(join(storage, folder), dataset_name+'_image.tif')
print(f"Valid image path: {os.path.exists(image_path)}")

image = sq.im.ImageContainer(image_path, lazy=True, chunks=200)

display(image)

plt.imshow(image['image'][5800:6000, 5800:6000, 0, 0])

img = imageio.volread(image_path)
plt.imshow(img[0, 5800:6000, 5800:6000])

Output from ImageContainer:

Expected output:

Traceback

no error thrown

Version

1.1.0

@MxMstrmn should be fixed in #390 (tried with your data, looks correct, still need to write tests though).

closed via #390


Major environment update: Python 3.8, Django 3

DO NOT MERGE YET
Not all conda dependencies have been rebuilt for 3.8 yet, so we may have to retry installing this environment in the future.
https://conda-forge.org/status/

That's a lot of updates. You may want to try the new environment on a test server before merging.

Tested https://github.com/greenelab/connectivity-search-backend/pull/70/commits/b75de1809c44843280836b8f0d22a4f8cb03dc8a locally using:
conda env update --file environment.yml
conda activate hetmech-backend
python manage.py runserver

Since on a different machine, I SSH port forwarded like:
ssh -L 9000:localhost:8000<EMAIL_ADDRESS>
Then clicked through every API endpoint at http://localhost:9000/v1/ and looked for errors.
Here are the runserver logs:
python manage.py runserver

Watching for file changes with StatReloader
Performing system checks...

System check identified no issues (0 silenced).
June 22, 2020 - 21:41:25
Django version 3.0.7, using settings 'dj_hetmech.settings'
Starting development server at http://<IP_ADDRESS>:8000/
Quit the server with CONTROL-C.
 Pretty amazing not even any deprecation warnings after such major upgrades. I think this should have assessed much of this codebase. Possible something breaks in the code not covered here, like the management command to populate database.

Notes:

https://docs.djangoproject.com/en/3.0/releases/3.0/


Update to FREE TOken

https://github.com/solana-labs/token-list/pull/28190

original PR https://github.com/solana-labs/token-list/pull/28177


[wip] Add support for using DataStax Enterprise with CCMBridge.

Adds support for running integration tests with DataStax Enterprise.
To run tests with DSE, set the system property 'dse.version' to the version of DSE you want to test with.  Note that you will still need to pass in a 'cassandra.version' property to indicate which major version of cassandra is associated with this DSE version (as this affects behavior of some tests).
Rather than adding system properties for DSE credentials, this relies on a recent change in CCM to support providing credentials via $HOME/.ccm/.dse.ini.  The contents of this file needs to be formed in this way:
[dse_credentials]
dse_username = myusername
dse_password = mypassword

Moving this to work in progress as I think it would also be useful to have a means decorate tests as DSE specific so they are only ran if a DSE version is provided.

Is it possible to launch a DSE instance from a git branch or an install directory? If so, I would suggest:

Re-use the cassandra.* properties for DSE version/branch/dir
Add a boolean system property dse that triggers the inclusion of --dse in the CCM command line if its value is true

Is it possible to launch a DSE instance from a git branch or an install directory?

It does indeed work from install directory using 'cassandra.directory' system property granted it was previously built (same behavior as oss cassandra).   Git branch would not work as of yet as CCM does not support this, but if it did, it would work via cassandra.branch.

If so, I would suggest:

Re-use the cassandra.* properties for DSE version/branch/dir
Add a boolean system property dse that triggers the inclusion of --dse in the CCM command line if its value is true.

It should work this way for both cases, the code sets an isDSE boolean which is used for determining whether or not '--dse' needs to be appended to args when adding/creating a node (only 2 CCM commands that seem to be depend on this that i've seen so far).

After speaking with @adutra about this, I understand and agree with his points.   I will overload -Dcassandra.version to support handling the DSE version and add a -Ddse parameter such that if true will interpret that as a DSE release.  In addition, will add a mapping of DSE <-> C* versions to determine test compatibility.   I've also added a @DseVersion annotation that will only run tests if the version criteria is met and DSE is in use (otherwise the tests are skipped).

Updated to use '-Dcassandra.version' for both C* and DSE versions.  If '-Ddse' is provided, it is assumed a DSE version is passed.  A mapping for determining C* version from DSE version is described in CCMBridge.
Example usages:
DSE 4.8.3:
-Ddse -Dcassandra.version=4.8.3
-Ddse=true -Dcassandra.version=4.8.3
Emits:
[CCMBridge] Using DSE version: 4.8.3 (C* 2.1.11, install arguments: -v4.8.3 --dse)
Cassandra 1.2.19:
-Dcassandra.version=1.2.19
Emits:
[CCMBridge] Using Cassandra version: 1.2.19 (install arguments: -v1.2.19)
Custom local install of DSE 5.0
-Dcassandra.version=5.0 -Ddse -Dcassandra.directory=/Users/atolbert/Documents/Projects/dse
Emits:
[CCMBridge] Using DSE version: 5.0 (C* 3.0, install arguments: --install-dir=/Users/atolbert/Documents/Projects/dse --dse)
Also added @DseVersion annotation which validates against DSE version.  If DSE not in use, skips test.   Also updated version checks to allow partial versions (i.e. C* 3.0) which is treated ad Major.MAX_VALUE for cases where we can't determine the exact C* version from the DSE version.

Since switching to the docker-based infra for travis we often have should_stop_if_cancelled_during_failed_reconnect(com.datastax.driver.core.AbstractReconnectionHandlerTest fail.  This test is pretty sensitive/timing based, I'll investigate in a separate PR.

I think this is ready to go, removing WIP tag.  If it looks ok I'll rebase before merging.

Squashed again on top of current 2.1 (no changes).

Looks very very good so far; I have a few more general remarks:

We should document somewhere in the code (CCMBridge class?) that when using DSE one needs to create the file $HOME/.ccm/.dse.ini with proper credentials.
I was wondering if cassandra.version shouldn't be renamed to ccm.version or stg similar to denote that it can be either a C* version or a DSE version.

This is awesome.
I'm fine leaving the name as cassandra.version.
As for documentation, I think we should do that in the CONTRIBUTING.md of the module that will run DSE tests.


Map view

As an OpenCDMS App user, I want to be able to select a "Map" view from the navigation menu and see an interactive map centered on my country with each station shown on the map.

Optionally host location may be polygon instead point


The streams Json is missing content

In the Json that returns https://iptv-org.github.io/api/streams.json you should put the url of the image of the transmitted channel and the name of the channel that is transmitted, it would be more comfortable for everyone to have that information in that API, thanks!

You can already get all this information from https://iptv-org.github.io/api/channels.json by channel ID.
More details: https://github.com/iptv-org/api#channels

The API https://iptv-org.github.io/api/channels.json does not have the streaming url, the ideal would be to have a single Json with all the information

How often is the streams.json updated? I can see a bunch of japanese streams being removed 5 days ago, but that are still on the streams.json


Version sorting performance improvements

Context
As documented on issue #1600, version comparison and sorting have performance issues:

CPU and object allocation head due to use of plain String.matches to determine if version parts are numeric
Object allocation overhead during version sorting, due to versions being parsed for each call to compare

This pull requests removes the String version comparator, to ensure that a callee either parses the Version outside of the comparator, or for classes involved in sorting, parse instances on construction and hold them for their lifetime.
Contributor Checklist

[x] Review Contribution Guidelines
[x] Sign Gradle CLA
[ ] Link to Design Spec for changes that affect more than 1 public API (that is, not in an internal package) or updates to > 20 files
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[x] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[x] Ensure that tests pass locally: ./gradlew quickCheck <impacted-subproject>:check

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation including proper use of @since and @Incubating annotations for all public APIs
[ ] Recognize contributor in release notes

@melix @oehme as discussed!

Thanks @melix. I'm about to go on paternity leave, so I won't get time for that improvement, though I had thought about it myself :)


Project contributor/maintainer needed.

Leave comments here if you are interested.

Sorry for the delay. That's great to hear @gsylvie. I'll email you to work through the details.

I'm interested too

interested if still needed

This repo is being archived. Thanks for your support along the way!


⚠ Fetchers has degraded performance

In e5f6695, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 244 ms

Resolved: Fetchers performance has improved in f9235e2.


Won't publish onPostTokenRevocationBySystem event when re-using auth code

Is your suggestion related to an experience ? Please describe.
When the authorization code is reused, the identity server revokes all relevant access tokens. Still the tokens are present in the gateway cache. In order to remove the tokens from cache, the APIM requires the access token value, hence need to publish an event with access token IDs.
Describe the improvement
publish onPostTokenRevocationBySystem event with token ID when re-using auth code
Additional context
https://support-internal.wso2.com/jira/browse/OBINTERNAL-881

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Markers on datasets getting multiple colors

A dataset has no dimension on which marker color should change (unlike place collections), but they do:

Those in blue are features identified as water bodies.

Never differentiated them before, but if we must for some reason, a legend would be in order, no?

Merged into #396


Information on extending / buying search quota

On two tenants (Targeted Release) we are no longer able to configure connections:
Error message:
" Your organization have no allocated quota. You will need to purchase quota so that you can add new connections. "
We cannot find documentation on how to purchase quota for search service.

Hi @marcoschmucker, sorry you are running into this issue. Please send an email to<EMAIL_ADDRESS>including the 2 tenant IDs and screenshots of this behavior. Also make sure to mention that you had raised an issue in the docs as well. Someone from our team will get back to you and help resolve this issue. In the meantime, let me know if you have any questions.


Can't define variables in inline event handler: "Property does not exist on type"

When defining a variable like this:
@click="() => {
  const x = 1
  if (x === 1) {
  }
}"

it yields two errors:

'x' is declared but its value is never read. ts(6133)
Property 'x' does not exist on type 'MyComponent'. ts(2339)

The code using such variable works correctly, and I've been using this syntax since Vue 2 with Vetur. After migrating to Vue 3 with Volar, this type safety and inference in VS Code fails.

Notes:
When using script setup only, everything is good
When using script lang="ts", only 'x' is declared but its value is never read. ts(6133)
When using script setup lang="ts", 'x' is declared but its value is never read. ts(6133) and Property 'x' does not exist on type '...'. ts(2339)