How to find current tenant instance?

I am not able to get the tenant instance to limit choices or return limited query of other models.
e.g: Tenant has MTM relation with City model. The tenant has stores in some of those cities.
A different X model has MTM city field.
And question is, how can i limit the city list called by x object to those of tenant's?
Thank you
P.S: Docs didn't help me for the issue

In your views just do request.tenant.

First explain better your app layout, as you explained it in rather chaotic way. Write what models are in what app, and what app are in SHARED and TENANT APPS. Then, were is M2M field.
In general if you have M2M  between 2 models in SHARED and  TENANT_APPS, then you have to declare it on TENANT_APPS side, this way it will be automatically restricted to what relation were created on this TENANT, opposite won't work and even may break db integrity, as you may have m2m relation to not existing objects.
Example of breaking integrity:
You create M2M relation between Tenant and Model with id 10 that exists in Tenant A.
You create new Tenant B and switch to it, you list Models by M2M relation and have problem as M2M is pointing to Model id 10 witch doesn't exists yet at Tenant B.
If M2M would be on Tenant schema side, then this M2M relation table would be clear same way as this Model table, and thats how it should be done properly. Declare your cross schema relations on TENANT side.

In your views just do request.tenant.

Thank you. It works as expected.
P.S: is it possible to get it in models.py or admin.py ?

I already told you about the solution:
from django.db import connection

def some_function():
     schema_name = connection.get_schema()
     tenant = connection.get_tenant()
     ...

Do not use connection in places like:
from django.db import connection
# do not use here
class Model(models.Model):
    # not here
   def method(self):
        # here is ok

def aaa():
    # here ok

I see that subject and description are 2 separate questions, so first was answered, but you can also use method on connection wrapper to just know current tenant: https://github.com/tomturner/django-tenants/blob/master/django_tenants/postgresql_backend/base.py
Second one:
First explain better your app layout, as you explained it in rather chaotic way. Write what models are in what app, and what app are in SHARED and TENANT APPS. Then, were is M2M field.
In general if you have M2M between 2 models in SHARED and TENANT_APPS, then you have to declare it on TENANT_APPS side, this way it will be automatically restricted to what relation were created on this TENANT, opposite won't work and even may break db integrity, as you may have m2m relation to not existing objects.
Example of breaking integrity:
You create M2M relation between Tenant and Model with id 10 that exists in Tenant A.
You create new Tenant B and switch to it, you list Models by M2M relation and have problem as M2M is pointing to Model id 10 witch doesn't exists yet at Tenant B.
If M2M would be on Tenant schema side, then this M2M relation table would be clear same way as this Model table, and thats how it should be done properly. Declare your cross schema relations on TENANT side.
Other way is to create M2M through model with additional tenant id indicator, but that just sucks :P

The question within the explanation was the real problem and the subject was the reason of it. Also the one in the description should be expected to explain the issue.
On the other hand, you are right that the two seems to be unrelated. Especially, if you have a clear understanding of django-tenants.. But I don't have that yet.
Thank you for your explanation. Sorry for the chaotic way of explanation, but it seems that it worked due to detailed explanation of the concept by you. Shared Apps and Tenant Apps are always be a problem for django-tenants.(at least for me) Which app to where? Are there any strict rules for it. How should be the relation btw them and so on.
Your second explanation is really valuable and I will be studying your first solution which is also great.. Thanks again.
P.S: my apps and models are:
tenants (shared app)
    Company (model)
        .... (field)
        city
        ...

location (shared app)
    City
        ...

another_app (tenant app)
    X
        city (choices to this field should be limited to current tenant's cities)

I already told you about the solution:
from django.db import connection

def some_function():
     schema_name = connection.get_schema()
     tenant = connection.get_tenant()
     ...

Do not use connection in places like:
from django.db import connection
# do not use here
class Model(models.Model):
    # not here
   def method(self):
        # here is ok

def aaa():
    # here ok

As in such places it's run only at start, and you know that it would be public schema.

This is the head shot. Thank you again.

If you do not need to have locations shared, then you can move them to tenant. But probably it's not this case, as it's wise to share locations. So in fact you need to dynamically filter cities. And then it depends how you solve it at frontend. If you load it by json query, just filter with request.tenant, if by form use dynamic choice fields: https://stackoverflow.com/questions/3419997/creating-a-dynamic-choice-field


Refactor and Add Features to UI Components

This pull request includes several commits that refactor and update various aspects of the UI components. The changes include updating dependencies, adding new components such as a contact form, LinkedIn and GitHub buttons, and a project carousel. The code has been refactored to use trpc for data fetching and to use hooks for client logic. Additionally, there are updates to the code style and formatting, as well as improvements to build configurations and directory structure. Unused files and directories have been removed. Overall, these changes enhance the UI components and improve the codebase.

:tada: This PR is included in version 1.13.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.14.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.14.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.15.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Remove unused variable

I think the correct behavior here is to check if the error is END_REACHED after the loop. If not, we should probably propagate the error to the caller.

The error variable comes from lai_resource_iterate, which only returns LAI_ERROR_END_REACHED or LAI_ERROR_UNEXPECTED_RESULT. LAI_ERROR_UNEXPECTED_RESULT already gets returned on error, so I don't think propagating it would change anything.

Oh, that's true. This LGTM in that case. Thank you very much for the PR!


Support for Level Up Advanced 5E system

Describe the solution you'd like
Would it be possible to include a setup of defaults for A5E? the overall features of 5e would work for most of it, with only a few additional items, but they're labeled diff as it's a diff system from 5e similar to how pf1/pf2 have similar items to 3e/3.5e but most likely have different names in foundry for ea stat, save, check, skill, etc
What system(s) do you want this feature to work with?
Level Up: Advanced 5th Edition (A5E)
What other modules do you use that you want to ensure work well with this feature?
I'm sure there's plenty of them out there that'd go nicely w/ this but off the top of my head I can't think of any...just getting this to work in the system proper would be nice enough for starters.
Additional context
Here's the token debug txt file for the a5e tokens if that helps any. I just dragged & copied the debug popup for all the stats on it.

I don't use the A5E system, so it's possible I missed some things - if you notice anything missing that you think should be supported, or if any values are showing incorrectly, feel free to open another issue with details on what's missing/wrong.


Docker Image Not Found

I execute this cmd: docker pull gcr.io/spark-operator/spark-py:v3.1.0

Error response from daemon: manifest for gcr.io/spark-operator/spark-py:v3.1.0 not found: manifest unknown: Failed to fetch "v3.1.0" from request "/v2/spark-operator/spark-py/manifests/v3.1.0".

Use the official spark docker repo instead, confirmed it works.  https://hub.docker.com/_/spark/tags


[zh]: Rsyc content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md

part of #33475  setup-1

I'd suggest combining commits to all three files under 'setup-1' into this PR.

I'd suggest combining commits to all three files under 'setup-1' into this PR.

Got it, I will merge this commit later

/approve

/approve

/lgtm


Error on macOS Mojave: cannot load such file -- trollop

I'm running macOS mojave, tried installing vagrant with brew and also downloaded from vagrantup directly.
Steps to reproduce

brew cask install vagrant (or download and install Vagrant)
vagrant plugin install google
vagrant up --provider=google

Actual result
Vagrant failed to initialize at a very early stage:
The plugins failed to load properly. The error message given is
shown below.
cannot load such file -- trollop
Expected result
Instance should be created on GCE.
Additional info
Because vagrant is using its own ruby, I can't even install trollop manually. How to resolve this issue? I would like to use GCE for my VMs, since running VMs on my own computer with something like virtualbox is so last century.
Is this plugin even maintained anymore? I mean, when running vagrant plugin install, it installs something like version 0.0.2. Any way to get a more recent version of this plugin, or is this already the latest version?

@LRH539
I've upgraded my machine to Mojave to test this but I cannot reproduce the behaviour you're specifying:
 2.4.3 ~ [13:41:41]∞
temikus λ vagrant --version
Vagrant 2.1.5
 2.4.3 ~ [13:41:45]∞
temikus λ vagrant plugin install vagrant-google
Installing the 'vagrant-google' plugin. This can take a few minutes...
Fetching: excon-0.62.0.gem (100%)
Fetching: formatador-0.2.5.gem (100%)
Fetching: fog-core-2.1.0.gem (100%)
Fetching: fog-json-1.2.0.gem (100%)
Fetching: mini_portile2-2.3.0.gem (100%)
Fetching: nokogiri-1.8.5.gem (100%)
Building native extensions.  This could take a while...
Fetching: fog-xml-0.1.3.gem (100%)
Fetching: uber-0.1.0.gem (100%)
Fetching: declarative-0.0.10.gem (100%)
Fetching: declarative-option-0.1.0.gem (100%)
Fetching: representable-3.0.4.gem (100%)
Fetching: retriable-3.1.2.gem (100%)
Fetching: public_suffix-3.0.3.gem (100%)
Fetching: addressable-2.5.2.gem (100%)
Fetching: multipart-post-2.0.0.gem (100%)
Fetching: faraday-0.15.4.gem (100%)
Fetching: jwt-2.1.0.gem (100%)
Fetching: signet-0.11.0.gem (100%)
Fetching: memoist-0.16.0.gem (100%)
Fetching: os-1.0.0.gem (100%)
Fetching: googleauth-0.6.7.gem (100%)
Fetching: google-api-client-0.23.9.gem (100%)
Fetching: fog-google-1.8.1.gem (100%)
Fetching: vagrant-google-2.2.1.gem (100%)
Installed the plugin 'vagrant-google (2.2.1)'!

VM starts up normally as well:
λ vagrant up --provider google
Bringing machine 'default' up with 'google' provider...
==> default: Checking if box 'google/gce' is up to date...
==> default: Launching an instance with the following settings...
...
==> default: Machine is booted and ready for use!

Considering you're mentioning version 0.0.2 and the latest version is 2.2.1 I think you may have issues with your environment.

Have you tried installing vagrant from https://www.vagrantup.com/downloads.html?
How did you install the plugin?

@LRH539 Great to hear it worked out!
I'm not sure why, to be honest. vagrant-google is just a rubygem essentially. I checked and there's no such version on rubygems:
λ gem list vagrant-google --remote --all

*** REMOTE GEMS ***

tcr-vagrant-google (0.1.4)
vagrant-google (2.2.1, 2.2.0, 2.1.0, 2.0.0, 1.0.0, 0.2.5, 0.2.4, 0.2.3, 0.2.2, 0.2.1, 0.2.0, 0.1.5, 0.1.4, 0.1.3)

However, if it was 0.2.X, then it uses a slightly different set of dependencies. Maybe something got messed up in the vagrant built-in ruby and it resolved to the old version. But that's only a theory, can't say much more without debugging data.
I'll close this out but feel free to reopen if you experience any additional issues.


Fdroid Repo not up to date

I just noticed that the Fdroid Repo is out of date. The last version on there is v1.1.0.

https://gitlab.com/fdroid/fdroiddata/-/merge_requests/12489

Version 1.2.0 is now available on F-Droid.


Verified logging

Add verified logging support.

Yet to test the changes on Rpi with FSS enabled. Do not merge until then.

@ygoyal18 If keys are already generated on the gateway  (through command line), we will get an error if we are trying to generate the keys again using pep tool.
Should we use --force option (When --setup-keys is passed and Forward Secure Sealing (FSS) has already been configured, recreate FSS keys.Read more at: https://www.commandlinux.com/man-page/man1/journalctl.1.html) ?
That is include --force option here https://github.com/armPelionEdge/pelion-edge-provisioner/blob/dbc7de862ba13daf0e9a2d7a926638d31f0b22c3/cli/bash/commands/get-one-identity.sh#L60

@ygoyal18 Should we merge this PR to dev for SQA?


Automatically set issue to / label with "stale" and "rotten" after some time

Description
Issues not touched for a long time (proposal 180 days) should go to / labeled as "lifecycle/stale". After another period (proposal additional 180 days) in that status they should be set to "lifecycle/rotten". There should be an action similar to https://github.com/actions/stale which handles that.

Reopen because we have some more repos to go through 😢


Support SpEL expression resolution for @Document "collection" field

It would be nice to be able to dynamically load a collection name using SpEL expressions.
Examples:

from property source:
e.g.

@Document(collection = "${dynamic.collection.name}")
public class MyCollection

@Document(collection = "#{@environment.getProperty('dynamic.collection.name')}")
public class MyCollection

from bean field/method invocation:

@Document(collection = "#{@someBean.getCollectionName()}")
public class MyCollection

Pull Requests
https://github.com/microsoft/spring-data-cosmosdb/pull/390

Hi, this feature would be really helpful. 👍
Right now I'm looking for away to make the collection name configurable by a property file like in the fist option.
I noticed that the pull request has merge conflicts. Are there any plans to add this feature in the near future? :)
Can anyone tell me the best practice for making the collection name configurable without this change?

I noticed that the pull request has merge conflicts.

Thanks for noticing, I pulled the changes and solved the conflicts. The Travis CI pipeline for integration tests seems to be broken though :(

Can anyone tell me the best practice for making the collection name configurable without this change?

Without this feature, I think you'd have to work with changing the collection name reflectively at runtime (e.g. https://www.baeldung.com/java-reflection-change-annotation-params)

@kushagraThapar - can you take a look at this?

@dsibilio I have moved the travis CI to Azure DevOps CI, which supports running the CI on PRs from forked repository.
I have tried running that on your PR, but there are still some hiccups. I will fix that asap.

@kushagraThapar Thank you, let me know if I can help you with anything.

@dsibilio CI is running successfully on external PRs now. I will take a look at the PR tomorrow.


Sync between Zotero and Word document after extraction

Hi,
Thanks for this tools. Really nice.
I extracted Zotero references from a Word document in CSL JSON format. All went well.
But there is no synchronization between Zotero and the document.
When I modify a reference in Zotero, the modification does not synchronize in the Word document after a refresh.
Is it a normal situation or do I have to do something else?
Do I have to "reactivate" (enter again with Add/Edit Citation) in the Word document each citation so that Zotero will recognize them?
Thanks,
François

@Lycurgue, there is currently no automated workflow for linking the items extracted with ref-extractor with the original items in the extracted Word document. And yes, manually re-inserting the items is the way to go for now.


⚠ ClamAV has degraded performance

In 48449ac, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 240 ms

Resolved: ClamAV performance has improved in 9f4c040 after 5 minutes.


⚠ PrivateHD has degraded performance

In 580b5f0, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2222 ms

Resolved: PrivateHD performance has improved in 392b80b.


More build information available on Github comments.

Hello, I would like to be able to post of the build information from Jenkins to the comment made on the Github pull request. Currently the list of environment variables that can be used is somewhat limited.
I would like to be able to post information such as the build duration, test results, build health and so on.
I have found a way to implement this functionality but it is pretty basic. I would be happy to contribute to the plugin as a whole and was wondering what the best way to add this functionality in would be. I looked at the possibility of making some of these things environment variables but those are set when the build starts and thus would not work for things like duration or test results.
How should I implement this to be consistent with the current way of doing things and how should it be offered as an option to users?

This can be accomplished using the downstream job pattern that was introduced in v 1.28. I'm closing this for now.


R:  user-defined functions (UDFs)

Ideally, add this for the initial release to main

Duplicate of #833


RequestUserInformation get '[unknown]'

The data I obtained is' unknown '. Is there any rule for this? Or is there a problem with the code I wrote? Can you give me a demo? Only obtain the user's profile picture and nickname, using the user's teamUserId

Can I only access user information that exists in my friend list?
If I want to obtain user information from someone who is not my friend? What should I do?


#5 Converting JSON DM Plan into a document

Rebased to be in sync with developed

Rebased to be in sync with develop (after change of Dockerfile)


sveltekit compatibility?

Looks like we cannot use it directly in Sveltekit. It would be great if it is compatible.

It has been working with sveltekit. I'll try it with the latest version. Perhaps there are some breaking changes in new beta version. I'll be back soon with response / fix.

I have just installed latest version od svelte kit and installed svelte gestures into it, it worked flawlessly. Looks like the issue is on your side. If there is some specific error, please create a repl with it and I can fix it then

I have just installed latest version od svelte kit and installed svelte gestures into it, it worked flawlessly. Looks like the issue is on your side. If there is some specific error, please create a repl with it and I can fix it then

It does work on a new project!
Could be something wrong on my setup. Thanks for testing.


[Feature] Smooth bar animation

Describe the feature
It would be great if there was an option for smooth bar animation, like the cell built-in unit frames
Describe the implementation
When editing the specific unit (Player, Target etc), there could be dropdown with the same options as base cell for Bar Animation with the same options (Flash, Smooth, None). Alternatively it could be an option for all Cell_UnitFrames frames, or maybe inherit from the base cell configuration?

The smoothing part was actually a bug, will be fixed in next version - flash will be a future project.


ValueError: API token not defined

Olá, podem me ajudar com esse erro?

Hi @MuriloIuryBarbosa,
Are you working in Leap's IDE or did you clone the repo to run locally on your computer?

If you're running the example locally, see the configuring access documentation
If you're running the example in the Leap IDE, take a look at Finding a Workspace’s API Token and the following sections in that document


Android callback for  matter commissioning without using chipcontroller.jar ?

AOS Currently I done matter commission using connecthomeip sample code and I tried using google sample app as well but in the both app way there are using chipcontroller.jar internally for commissioning, unlink IOS is there any way in android to do commissioning without  chipcontroller.jar with internal android callback method.

currently this code is not in part of android AOSP, so you have to link chipcontroller.jar for matter commissioning and IM control...


When the file extension is changed, read silently fails.

Describe the bug
When reading from a parquet file, if the file extension doesn't happen to match the default configuration, an empty DataFrame is produced. I believe this is easily encountered as a beginner (reading a Parquet file using the default read options is one of the first things I tried), and the lack of feedback makes this a challenge to debug.
To Reproduce
//! ```cargo
//! [dependencies]
//! anyhow = "1.0"
//! datafusion = "32.0"
//! tokio = { version = "1.33", features = ["macros", "rt-multi-thread"] }
//! ```
use std::sync::Arc;

use datafusion::arrow::array::{Float32Array, Int32Array};
use datafusion::arrow::datatypes::{DataType, Field, Schema};
use datafusion::arrow::record_batch::RecordBatch;
use datafusion::dataframe::DataFrameWriteOptions;
use datafusion::parquet::basic::Compression;
use datafusion::parquet::file::properties::WriterProperties;
use datafusion::prelude::*;

#[tokio::main]
async fn main() -> anyhow::Result<()> {
    let ctx = SessionContext::new();

    // Make up a new dataframe.
    let write_df = ctx.read_batch(RecordBatch::try_new(
        Arc::new(Schema::new(vec![
            Field::new("purchase_id", DataType::Int32, false),
            Field::new("price", DataType::Float32, false),
            Field::new("quantity", DataType::Int32, false),
        ])),
        vec![
            Arc::new(Int32Array::from(vec![1, 2, 3, 4, 5])),
            Arc::new(Float32Array::from(vec![1.12, 3.40, 2.33, 9.10, 6.66])),
            Arc::new(Int32Array::from(vec![1, 3, 2, 4, 3])),
        ],
    )?)?;

    write_df
        .write_parquet(
            "output.parquet.snappy",
            DataFrameWriteOptions::new().with_single_file_output(true),
            Some(
                WriterProperties::builder()
                    .set_compression(Compression::SNAPPY)
                    .build(),
            ),
        )
        .await?;

    let read_df = ctx
        .read_parquet(
            "output.parquet.snappy",
            ParquetReadOptions {
                // If this line is uncommented, the read will be successful.
                // file_extension: "parquet.snappy",
                ..Default::default()
            },
        )
        .await?;

    read_df.show().await?;

    Ok(())
}

Gives output:
$ cargo run
   Compiling bug_repro_open_no_error v0.1.0 (/home/jacob/src/gro-sandbox/user/jsimpson/app/bug_repro_open_no_error)
    Finished dev [unoptimized + debuginfo] target(s) in 7.56s
     Running `target/debug/bug_repro_open_no_error`
++
++

Expected behavior
I would like to get an error if the read fails, rather than an empty DataFrame.
Additional context
No response

Thank you @jsimpson-gro  -- I agree this is confusing behavior and would be nice to fix.
I am marking it as a good first issue as I think the reproducer is very nice and he description clear.


Kazakh Translation

Create Kazakh Translation
References
Add references/links to any related issues or PRs. These may include:

Fixes #[issue-number]
Requires DSpace/DSpace#[pr-number] (if a REST API PR is required to test this)

Description
Our libraryan staff has translates at Science Library of KATU
Instructions for Reviewers
Please add a more detailed description of the changes made by your PR. At a minimum, providing a bulleted list of changes in your PR is helpful to reviewers.
List of changes in this PR:

First, ...
Second, ...

Include guidance for how to test or review your PR. This may include: steps to reproduce a bug, screenshots or description of a new feature, or reasons behind specific changes.
Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

[ ] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
[ ] My PR passes TSLint validation using yarn run lint
[ ] My PR doesn't introduce circular dependencies
[ ] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
[ ] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
[ ] If my PR includes new, third-party dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.

Is admin section should be Kazakh if admin guy undersand English or not? we would like to miss admin section

@myrza1 : I just wanted to ping you one last time to let you know we are finishing up the 7.4 release in the next 2 weeks.  If you have a chance to update this PR based on my last review (https://github.com/DSpace/dspace-angular/pull/1297#pullrequestreview-1059057947), then we may be able to include it in 7.4.  Otherwise, we'll have to reschedule it for 7.5 (due in Feb)

@myrza1 : I just wanted to ping you one last time to let you know we are finishing up the 7.4 release in the next 2 weeks. If you have a chance to update this PR based on my last review (#1297 (review)), then we may be able to include it in 7.4. Otherwise, we'll have to reschedule it for 7.5 (due in Feb)

Hello,
#1297

We will rename to kk.json
Better label "Қазақ"

for next 2 week it maybe possible
Thanks!

@myrza1 : Thank you for making the updates!  I'll add this to my list of PRs to re-review and try to get this merged into the upcoming 7.4 release


Waiting for daemons to come online ...

Hello,
I just installed miningcore and downloaded the blockchain. But when I run miningcore I receive the message: Waiting for daemons to come online ...
This is how I launched the litecoin daemon: litecoind -server -datadir= -rpcuser= -rpcpassword= -port=9333 -rpcport=9332 -rpcbind=<IP_ADDRESS>
What wrong with that? How many litecoin daemons should I run, and how?
Thank you.

@1n4ho05
Stop opening up new issues for this. This is the second time in 24 hours for the same Question.
I converted the issue into a Discussion here: https://github.com/oliverw/miningcore/discussions/1361, so please follow it for an answer to your Question.
Everyone, please only open a new issue for problems that are directly code related
If you do not know how to configure Miningcore, the coin daemons, or don't understand basic Linux & server configurations, that is not a bug and it belongs in a Discussion. Don't open an Issue for this.
PS - You can also find a wealth of information by searching Closed Issues ;-)

https://github.com/oliverw/miningcore/discussions/1361 - no page!


Try fix ui tests

polkadot companion: https://github.com/paritytech/polkadot/pull/3208

bot merge


Multi echo: tCompCor - numpy.linalg.linalg.LinAlgError: SVD did not converge

Hello all,
An older error I saw in a previous solved issue seems to have reappeared when I tried to run fmriprep on a multi echo dataset. Version 1.2.3 previously ran on the same data without any errors, but when I updated to 1.2.4 today, I got an error saying that SVD did not converge. Previous work directories were removed, and outputs were moved elsewhere before running fmriprep 1.2.4.
The full output is as follows:
[Node] Error on "fmriprep_wf.single_subject_4154_wf.func_preproc_task_co_run_2_echo_1_wf.bold_confounds_wf.tcompcor" (/data/work/fmriprep_wf/single_subject_4154_wf/func_preproc_task_co_run_2_echo_1_wf/bold_confounds_wf/tcompcor)
181204-15:14:53,737 nipype.workflow ERROR:
	 Node tcompcor failed to run on host pavlov.amc.nl.
181204-15:14:53,743 nipype.workflow ERROR:
	 Saving crash info to /data/fmriprep/sub-4154/log/20181204-143741_072fe7eb-6c6e-4559-aafd-94fe1bdf66a4/crash-20181204-151453-gbrunner-tcompcor-7402206b-78a1-4ed0-b54e-53fe7c787030.txt
Traceback (most recent call last):
  File "/usr/local/miniconda/lib/python3.6/site-packages/nipype/pipeline/plugins/multiproc.py", line 69, in run_node
    result['result'] = node.run(updatehash=updatehash)
  File "/usr/local/miniconda/lib/python3.6/site-packages/nipype/pipeline/engine/nodes.py", line 473, in run
    result = self._run_interface(execute=True)
  File "/usr/local/miniconda/lib/python3.6/site-packages/nipype/pipeline/engine/nodes.py", line 557, in _run_interface
    return self._run_command(execute)
  File "/usr/local/miniconda/lib/python3.6/site-packages/nipype/pipeline/engine/nodes.py", line 637, in _run_command
    result = self._interface.run(cwd=outdir)
  File "/usr/local/miniconda/lib/python3.6/site-packages/nipype/interfaces/base/core.py", line 511, in run
    runtime = self._run_interface(runtime)
  File "/usr/local/miniconda/lib/python3.6/site-packages/fmriprep/interfaces/patches.py", line 51, in _run_interface
    runtime = super(RobustTCompCor, self)._run_interface(runtime)
  File "/usr/local/miniconda/lib/python3.6/site-packages/nipype/algorithms/confounds.py", line 539, in _run_interface
    self.inputs.pre_filter, degree, self.inputs.high_pass_cutoff, TR)
  File "/usr/local/miniconda/lib/python3.6/site-packages/nipype/algorithms/confounds.py", line 1189, in compute_noise_components
    u, _, _ = linalg.svd(M, full_matrices=False)
  File "/usr/local/miniconda/lib/python3.6/site-packages/scipy/linalg/decomp_svd.py", line 132, in svd
    raise LinAlgError("SVD did not converge")
numpy.linalg.linalg.LinAlgError: SVD did not converge

Preprocessing did not finish successfully. Errors occurred while processing data from participants: 4154 (1). Check the HTML reports for details.
Traceback (most recent call last):
  File "/usr/local/miniconda/bin/fmriprep", line 11, in <module>
    sys.exit(main())
  File "/usr/local/miniconda/lib/python3.6/site-packages/fmriprep/cli/run.py", line 431, in main
    fmriprep_wf.run(**plugin_settings)
  File "/usr/local/miniconda/lib/python3.6/site-packages/nipype/pipeline/engine/workflows.py", line 597, in run
    runner.run(execgraph, updatehash=updatehash, config=self.config)
  File "/usr/local/miniconda/lib/python3.6/site-packages/nipype/pipeline/plugins/base.py", line 162, in run
    self._clean_queue(jobid, graph, result=result))
  File "/usr/local/miniconda/lib/python3.6/site-packages/nipype/pipeline/plugins/base.py", line 225, in _clean_queue
    raise RuntimeError("".join(result['traceback']))
RuntimeError: Traceback (most recent call last):
  File "/usr/local/miniconda/lib/python3.6/site-packages/nipype/pipeline/plugins/multiproc.py", line 69, in run_node
    result['result'] = node.run(updatehash=updatehash)
  File "/usr/local/miniconda/lib/python3.6/site-packages/nipype/pipeline/engine/nodes.py", line 473, in run
    result = self._run_interface(execute=True)
  File "/usr/local/miniconda/lib/python3.6/site-packages/nipype/pipeline/engine/nodes.py", line 557, in _run_interface
    return self._run_command(execute)
  File "/usr/local/miniconda/lib/python3.6/site-packages/nipype/pipeline/engine/nodes.py", line 637, in _run_command
    result = self._interface.run(cwd=outdir)
  File "/usr/local/miniconda/lib/python3.6/site-packages/nipype/interfaces/base/core.py", line 511, in run
    runtime = self._run_interface(runtime)
  File "/usr/local/miniconda/lib/python3.6/site-packages/fmriprep/interfaces/patches.py", line 51, in _run_interface
    runtime = super(RobustTCompCor, self)._run_interface(runtime)
  File "/usr/local/miniconda/lib/python3.6/site-packages/nipype/algorithms/confounds.py", line 539, in _run_interface
    self.inputs.pre_filter, degree, self.inputs.high_pass_cutoff, TR)
  File "/usr/local/miniconda/lib/python3.6/site-packages/nipype/algorithms/confounds.py", line 1189, in compute_noise_components
    u, _, _ = linalg.svd(M, full_matrices=False)
  File "/usr/local/miniconda/lib/python3.6/site-packages/scipy/linalg/decomp_svd.py", line 132, in svd
    raise LinAlgError("SVD did not converge")
numpy.linalg.linalg.LinAlgError: SVD did not converge

Sentry is attempting to send 3 pending error messages
Waiting up to 2.0 seconds
Press Ctrl-C to quit

Facing the same issue (multi-band dataset).
Any planning information would be valuable.
Many thanks!

@shirareznik Is your dataset also multiecho? Multiecho handling changed between 1.2.3 and 1.2.4.
@emdupre Do you know if this is expected if we run tCompCor on the optimal combination of echoes? Are *CompCor even valid measures on combined BOLD runs?

@effigies ,
Yes, it is.
Thanks!

Looking at #1010, it may be that we should skip CompCor for multiecho datasets.
@shirareznik @gb4944 Just as a couple data points, were either of you intend to use the CompCor regressors?

@shirareznik @gb4944 Just as a couple data points, were either of you intend to use the CompCor regressors?

Thanks for the response! ME-ICA would be preferable for noise correction, but I couldn't find any options regarding it in the latest version of the fmriprep documentation.

No, it is not currently implemented. The question is whether CompCor is useful for multiecho data, in its absence.
We're also happy to get contributions from people with more multiecho experience in implementing MEICA, of course.

Hi,
Thanks for reporting these issues ! Just to confirm, is this affecting all multi-echo runs, or only specific ones ? I've run several datasets myself locally and not encountered this error, so just trying to understand why !
That being said, I would discourage interpreting tCompCor measures from the optimal combination. This was the update in 1.2.4, that we switched from individual echos returned by default to the optimal combination. I'm not sure if this made it into the release notes, but hopefully the documentation is clear !
I would actually discourage implementing MEICA denoising here, since there is some confusion across the field about which specific component selection criteria to adopt. That being said, we're having those discussions in the tedana repo and would love your input !!

@effigies I see, that explains that! I was not intending on using tCompCorr in place of it.
@emdupre That's good to know, thank you! I've only tested a subset of subjects the dataset, but the error appeared for all of them when processing the first functional run.

@gb4944 Thanks for the response. Just to be sure, your derivatives otherwise look sensible? You should be getting reports and derivatives that don't depend on the confounds, and the reports should show the masks of voxels passed to CompCor. With SVD failures, the main thing we can control is whether we're giving sensible data to the process; if the data is good and it's still just failing, all we can try to do is handle that case more gracefully. @shirareznik Same questions for you.
I would propose that we catch LinAlgErrors in CompCor interfaces, and return columns of NaNs, producing a warning that SVD did not converge.
It sounds like we don't want to disable CompCor altogether with ME, at present, as we don't have MEICA to replace it, and there's no guarantee that users aren't using it. I also found this Power, et al. paper from February that seems to indicate from a cursory reading that there's value to CompCor in ME datasets.
cc @oesteban @chrisfilo

+1 for graceful handling non converging SVD (since there is no known solution). There were 12 such errors reported in the past couple of weeks (https://sentry.io/poldracklab/fmriprep/issues/774850143/?query=is%3Aunresolved)

@effigies Thank you for the suggestion! I re-ran fmriprep for one subject to look at the rest of the derivatives, and it appears that the input to CompCorr doesn't look entirely correct, especially in the top right corner of this image. No errors occurred using the same files with 1.2.3.

Just to clarify: the reason this is new with 1.2.4 is that effectively you are processing a different file, since you are deriving CompCor measures from the optimal combination rather than any individual echo. If you would like to process individual echos instead, I've added the --echo-idx flag.
But what you're seeing is actually an older issue, see: https://neurostars.org/t/weird-brain-mask-in-fmriprep-report/1812
It'd be great if you could confirm this looks right in your own data by looking at the brainmask.nii.gz and ensuring its shape is sensible.

@emdupre Good point, the grid pattern is not present in the brain mask. Other parts that are missing or outside of the brain seem consistent with the image from the report that I posted.

@gb4944 Your aCompCor (magenta) and tCompCor (blue) masks look reasonable. I note that your BOLD mask seems to be cropping rather more than it should... This image is from the 1.2.4 run?

@effigies Yes, it's from 1.2.4.

Could you go ahead and open a new issue for that? Also, are you using single-band references, or just the BOLD series?

@gb4944 Just the BOLD series.
I'll open a new issue. Thanks for the help!

@gb4944 @shirareznik If either of you is running with fmriprep-docker, could you do the following, to run in developer mode?
git clone https://github.com/effigies/fmriprep.git
git clone https://github.com/effigies/nipype.git
pushd fmriprep; git checkout fix/compcor_nans; popd
pushd nipype; git checkout enh/compcor_svd_failure; popd

pip install --upgrade fmriprep-docker
fmriprep-docker -p nipype -f fmriprep [YOUR NORMAL FMRIPREP OPTIONS]

Of course- I'll run it soon and update you.
On Thu, Dec 13, 2018 at 2:30 PM Chris Markiewicz<EMAIL_ADDRESS>wrote:

@gb4944 https://github.com/gb4944 @shirareznik
https://github.com/shirareznik If either of you is running with
fmriprep-docker, could you do the following, to run in developer mode?
git clone https://github.com/effigies/fmriprep.git
git clone https://github.com/effigies/nipype.gitpushd fmriprep; git checkout fix/compcor_nans; popdpushd nipype; git checkout enh/compcor_svd_failure; popd
pip install --upgrade fmriprep-docker
fmriprep-docker -p nipype -f fmriprep [YOUR NORMAL FMRIPREP OPTIONS]
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/fmriprep/issues/1433#issuecomment-446951901,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABMYijlHACh4huiNpr0k4QQ6hftj1kJ5ks5u4khqgaJpZM4ZBCxe
.

@gb4944 @shirareznik Hi, any updates? I can't off the top of my head think of a way of generating a synthetic dataset that will consistently fail to converge with SVD, so if you could verify that this produces NaN confounds and doesn't crash, that would be a good test.

@effigies Apologies for the delay, unfortunately I don't think I have the permissions required to run this on the server where the data is stored. I will ask about it and update you if I can get it to run.

@gb4944 No worries. If you're running it on a cluster, it'll be difficult. We can always just try it and see if the next release fixes your issue.

Hi @gb4944, @shirareznik have you experienced this again with latest versions of fMRIPrep? Could I ask you to try on the same failing data, but with version 1.4.0 (the latest)?
Thanks

Hi,
Sorry for being "slow"- I'll test this during this week and update (in case
I'll be overloaded, it might take another day or two).
I've read the change log yesterday and was very curious to try it already!
Many thanks
On Tue, May 21, 2019, 21:57 Oscar Esteban<EMAIL_ADDRESS>wrote:

Hi @gb4944 https://github.com/gb4944, @shirareznik
https://github.com/shirareznik have you experienced this again with
latest versions of fMRIPrep? Could I ask you to try on the same failing
data, but with version 1.4.0 (the latest)?
Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/fmriprep/issues/1433?email_source=notifications&email_token=AAJRRCRPATPL7WOLEAV7KM3PWRAZ7A5CNFSM4GIEFRPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV43J2Y#issuecomment-494515435,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJRRCQ7UMDWU5TZG3PWF33PWRAZ7ANCNFSM4GIEFRPA
.


filter action type causing the whole list empty

It should only filter the current view.

Also, it does not need to list all actions in the list. only the list inside the current view is enough.

plum* types are all deprecated

It's already implemented.
Currently, if I click one from the filter, it navigates to actions page.
"Also, it does not need to list all actions in the list. only the list inside the current view is enough."
Does it mean I should show the filtered actions on the address page(current page)?

It's already implemented.
Currently, if I click one from the filter, it navigates to actions page.
"Also, it does not need to list all actions in the list. only the list inside the current view is enough."
Does it mean I should show the filtered actions on the address page(current page)?

@guo has the answer

https://www.iotexscan.io/action?actionType=transfer
The “sender” and “to” fields are not properly displayed. Should be the same as https://www.iotexscan.io/action

This issue was fixed before, I think.
I checked the code related to that and tested.
When addressMeta doesn't exist, it shows the raw address.
Pls check

https://www.iotexscan.io/action?actionType=transfer
The “sender” and “to” fields are not properly displayed. Should be the same as https://www.iotexscan.io/action

@liaojikunwork can u fix this before we close this issue?

Currently, it shows the raw address if addressMeta doesn't exist.
What should I show if addressMeta doesn't exist?

first 18 chars + '....'

Exactly 18 chars + '...' or make it similar to other fields(hash)?

other fields are (18 chars + '...' ), no?

No, just styling


Adjusted values should be used in convergence update in FirstOrderMinimizer

As per https://groups.google.com/forum/#!topic/scala-breeze/YapqCs6222w adjValue and adjGrad should be used in convergence check in FirstOrderMinimizer::infiniteIterations

The way I see it updateHistory should also use the adjusted values, do you agree?


Enable @react-native/babel-plugin-codegen for RNTester

Summary:
This diff adds react-native/babel-plugin-codegen as an extra Babel plugin for Metro in RNTester to enable static view configs support.
This diff does not provide full static view configs support for every React Native project. It only enables them for RNTester to unblock further bridgeless mode OSS rollout work.
Changelog: [Internal] - Static view configs support for RNTester.
Differential Revision: D46523066

Closing as abandoned internally


Using with Angular CLI - types

I'm trying to use your lib with my angular-cli project:
Your readme instructions don't quite explain how to import your lib for my needs so I am following other instructions here: https://stackoverflow.com/a/40527978/413127
Question is:
Do you offer @types so that I can import straight into my component? (or do you plan to?)

this is an angular 1.x lib , and i am using angular 4.x


Fixing the information request page

There are presently a couple of bugs in the Information Request page of the template.

The "info_request_create.html" template requires an array of cruises to be passed in, to populate the dropdown box, but none are. This PR fetches the cruises and passes them in.
When submitting an info request, there is a 500 error. This is due to some incorrect typing, of parameters. Additionally, int returns a raw object. I noticed that the template has a message prop, so I made it re-render the template with a message assigned to that prop.

This maybe still isn't ideal, as there's no way to actually see the info requests from the database, so as a tutorial it can be hard to be certain that your database is writing correctly, but it's an improvement.

@microsoft-github-policy-service agree

Thanks @jackreichelt for the contribution!
This repo is actually a generated repo, could you make the same PR on this file instead? https://github.com/Azure-Samples/Azure-Python-Standardization-Template-Generator/blob/main/{{cookiecutter.__src_folder_name}}/src/fastapi/fastapi_app/app.py

Thanks @pamelafox. I've raised that PR here: https://github.com/Azure-Samples/Azure-Python-Standardization-Template-Generator/pull/87


Great article!

This should be the first introduction to Xamarin.Forms, xaml and getting started imho.  Unless the previous articles were to raise suspicion and gather a list of further questions.  Now i see the connection between the markup and code behind.

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

ID: 02a2221e-ff55-cfe0-9f24-382101584c80
Version Independent ID: 260000a6-cee8-487a-2fbd-2dfdd0864735
Content: Part 1. Getting Started with XAML - Xamarin
Content Source: docs/xamarin-forms/xaml/xaml-basics/get-started-with-xaml.md
Service: unspecified
GitHub Login: @charlespetzold
Microsoft Alias: chape

Thanks for the feedback @brokenjavagit.


composer install errors - avoid packages

Version information

Laravel: v5.7
Voyager: v1.1 (lastest from that repo)
PHP: 7.2.11
Database: Mysql 5.7.23

Description
while
composer install

[package errors]
Package **satooshi/php-coveralls is abandoned**, you should avoid using it. Use php-coveralls/php-coveralls instead.
Package **guzzle/guzzle is abandoned**, you should avoid using it. Use guzzlehttp/guzzle instead.

Screenshots

Running composer why guzzle/guzzle gives
satooshi/php-coveralls  v1.1.0  requires  guzzle/guzzle (^2.8 || ^3.0)
Then running composer why satooshi/php-coveralls gives:
codeclimate/php-test-reporter  dev-master  requires  satooshi/php-coveralls (^1.0)
Looks like codeclimate/php-test-reporter is the root of both problems.
Nothing we can really do about it.

Looks like that package is deprecated: https://github.com/codeclimate/php-test-reporter
We should consider removing it (since I don't believe we're really using it anyway) or changing to a different package.


fix jshint errors and warnings

Just fixed annoying jshint errors. The code is a bit cleaner now.

This PR is outdated, and if @mbektimirov u may still do updates, please syn with latest master, and I will review PR again. But if in week no reply, I will close this PR, and recreate new one with suggestions. I also wanted to do similar fixes.
cc/ @YetiCGN


Enable sodiums entity culling option

Is your request related to a problem? Please describe.
Sodium's entity culling is a fairly effective method in terms of optimizations, it helps even when other mods such as entity culling is present(entity culling can often hurt performance in cases and sodium can help reduce said cases)
Describe the solution you'd like
Assuming there are no issues, rein-able the entity culling option in sodium.
Describe alternatives you've considered
There are no alternatives I can think of as of this moment.
Additional context
I have done some minor testing to see if this setting broke anything and have not found any such cases, however, I was not the most thorough when testing.

Yeah, it should be enabled, I think sodium entity culling was disabled because there is already a mod called entity culling included in the modpack that may seem to do the same thing, but according to the mod developer, it doesn't do the same thing and sodium entity culling should be enabled.
https://github.com/tr7zw/EntityCulling/issues/132#issuecomment-1869783948

Will be done next time I update as I don't see any issues with it - thanks!

Will this also be applied to additive by chance?

Yes. Changes from Adrenaline get applied to Additive as well

Quite honestly, is the sodium config needed at all? Seems the changes it has might just be in default sodium already. Haven’t double checked.

The cpu_render_ahead_limit option is different from default Sodium. However, in modern versions of Sodium, always_defer_chunk_updates is already set to true (iirc). I'll remove the always_defer_chunk_updates line where applicable


Bounty Submission # 1

Canister URL(s): https://5zugh-4yaaa-aaaag-qjqra-cai.raw.icp0.io
Repo URL: https://github.com/fxgst/azle-react
Oisy wallet principal: yrgau-u5kqp-4qtan-kgkt2-rfwta-422so-l3c5x-pc55l-v5dcf-5id7e-yae

Canister URL(s) : https://4wksd-7yaaa-aaaap-qkmxa-cai.icp0.io/
Repo URL : https://github.com/phukrit7171/Hello_Name_ICP.git
Oisy wallet principal :  lvcvh-yva5w-t4w5z-liyru-idf7b-f6tti-bcie6-i23xk-ait27-jgfsu-tqe


ERROR: "rental" videos not supported; please report this issue

Hi guys, is there someone working on this? Any plans?
It seems to be complicated to download a purchased youtoube video (like in my case), why is it?
Thank you!

I think no. If someone is interested in it, pull requests are welcomed.
I'm closing this ticket as it's a duplicated feature request as #359


Multidimensional Arrays as POST Fields

What is the expected behavior?
$curl->post($endpoint, [
        'OuterArrayKey' => [
            'title' => 'Testing API'
            ,'opened_at' =>  '10 Feb 2011, 15:37'
            ,'occured_at' => '10 Feb 2011, 15:37'
        ]
    ]));

This code should go through. *

What is the actual behavior?

What happens is a "Error: 400: HTTP/1.1 400 Bad Request"*

Could I suggest having an option in Curl::post to have:
$data = json_encode($data);

instead of
$data = http_build_query($data);

Hi. Here's an example showing how to POST json.
https://github.com/php-curl-class/php-curl-class/blob/master/examples/post_json.php
You need
$curl->setHeader('Content-Type', 'application/json');


make impl IntoFuture for Insertion generic over Database

This enables writing code like this:
async fn hi<D: Model<Postgres> + Send>(data: D, conn: &ormlite::Pool<Postgres>) {
    let _ = data.insert(conn).await.unwrap();
}

Previously, this would have required an ugly where clause:
async fn hi<D: Model<Postgres> + Send>(data: D, conn: &ormlite::Pool<Postgres>)
where
    for<'a> ormlite_core::insert::Insertion<'a, &'a ormlite::Pool<Database>, D, Database>: IntoFuture,
{
    let _ = data.insert(conn).await;
}

Very nice. Thank you for adding this.


piraeus-server: start dmeventd on start-up

dmeventd will be started by lvm commands (i.e. lvcreate, lvremove, ..) if it does not already run. This is an issue if started in a context with a high soft file limit: dmeventd will try to close all FDs after forking. The limit on Almalinux9 is higher than 1_000_000_000, which caused the initial command to wait for over 100 seconds, mostly leading to linstor commands timing out.
The workaround here is to start "dmeventd" before starting the satellite with a known reasonable file limit.
See also 0c6c6ec0d1d1d38320f66295d9f992ea8ee50815 in the linstor-server project.

I'm fine with "backporting" that in general, but where does this come from? piraeus is not rhel/alma based, we used bullseye without issues, or did that pop up in bullseye now as well or where does this actually come from?

The issue pops up when running the container on an almalinux9 host. The file limit is not configured by the container OS but the host OS


Allow users to publish comments for developers only

Users should be able to create comments that are only visible to developer (or a group of developers)

This depends on the ability of radiks to get the public key of a group.


Add the mod on Modrinth

I think it would be great to see this mod on https://modrinth.com
Thank you for this cool project !

Maybe

https://modrinth.com/mod/auto-clicker


[BUG] Zephyr counter driver test feils

Describe the bug
Since tiacsys/zephyr@51f452b the RTC (counter) test runs into timeout. Thus the qa-integration workflow fails since a couple of days.
To Reproduce
Steps to reproduce the behavior:

following https://bridle.tiac-systems.net/doc/latest/bridle/gs_installing.html
west twister --device-testing --hardware-map bridle/.github/qa-integration/map-tiac_magpie.yml --board-root bridle/boards --testsuite-root zephyr/tests/drivers/counter

Expected behavior
The original Zephyr test for RTC (counter) on STM32 should be successfully run without hacks. But sadly, it seems Zephyr have never used this test for RTC, only counter and only on selected boards.
Impact
It is an showstopper. Our QA workflow is broken.
Logs and console output
INFO    - Using Ninja..
INFO    - Zephyr version: zephyr-v3.3.0-1683-g7e5349a33581
INFO    - Using 'zephyr' toolchain.
INFO    - Building initial testsuite list...
INFO    - Writing JSON report twister-out/testplan.json

Device testing on:

| Platform    | ID       | Serial device   |
|-------------|----------|-----------------|
| tiac_magpie | DT04ATV0 | /dev/ttyUSB0    |

INFO    - JOBS: 4
INFO    - Adding tasks to the queue...
INFO    - Added initial list of jobs to queue
INFO    - 26/47 tiac_magpie               tests/drivers/spi/dt_spec/drivers.spi.dt_spec      PASSED (device 14.033s)
INFO    - 27/47 tiac_magpie               tests/drivers/can/shell/drivers.can.shell          PASSED (device 13.979s)
INFO    - 28/47 tiac_magpie               tests/drivers/spi/spi_loopback/drivers.spi.loopback.internal SKIPPED (runtime filter)
INFO    - 29/47 tiac_magpie               tests/drivers/spi/spi_loopback/drivers.spi.loopback PASSED (device 8.452s)
INFO    - 30/47 tiac_magpie               tests/drivers/gpio/gpio_get_direction/peripheral.gpio.get_direction PASSED (device 6.206s)
INFO    - 31/47 tiac_magpie               tests/drivers/can/timing/drivers.can.timing        PASSED (device 5.942s)
INFO    - 32/47 tiac_magpie               tests/drivers/can/api/drivers.can.api              PASSED (device 7.069s)
INFO    - 33/47 tiac_magpie               tests/drivers/gpio/gpio_basic_api/drivers.gpio.2pin PASSED (device 27.412s)
INFO    - 34/47 tiac_magpie               tests/drivers/hwinfo/api/drivers.hwinfo.api        PASSED (device 6.589s)
INFO    - 35/47 tiac_magpie               tests/drivers/gpio/gpio_api_1pin/peripheral.gpio.1pin PASSED (device 11.960s)
INFO    - 36/47 tiac_magpie               tests/drivers/watchdog/wdt_basic_api/drivers.watchdog SKIPPED (runtime filter)
INFO    - 37/47 tiac_magpie               tests/drivers/entropy/api/drivers.entropy.psa_crypto SKIPPED (runtime filter)
INFO    - 38/47 tiac_magpie               wdt_basic_api/drivers.watchdog.stm32iwdg.tiac_magpie PASSED (device 9.774s)
INFO    - 39/47 tiac_magpie               tests/crypto/rand32/drivers.rand32.random_psa_crypto SKIPPED (runtime filter)
INFO    - 40/47 tiac_magpie               tests/drivers/counter/counter_basic_api/drivers.counter.basic_api  FAILED Timeout (device 605.294s)
ERROR   - *** Booting Zephyr OS build zephyr-v3.3.0-1683-g7e5349a33581 ***
Running TESTSUITE counter_basic
===================================================================
START - test_all_channels
Testing rtc@40002800
PASS - test_all_channels in 3.103 seconds
===================================================================
START - test_cancelled_alarm_does_not_expire
Skipped for rtc@40002800
PASS - test_cancelled_alarm_does_not_expire in 0.103 seconds
===================================================================
START - test_late_alarm
Skipped for rtc@40002800
PASS - test_late_alarm in 0.103 seconds
===================================================================
START - test_late_alarm_error
Skipped for rtc@40002800
PASS - test_late_alarm_error in 0.103 seconds
===================================================================
START - test_multiple_alarms
Skipped for rtc@40002800
PASS - test_multiple_alarms in 0.103 seconds
===================================================================
START - test_set_top_value_with_alarm
Skipped for rtc@40002800
PASS - test_set_top_value_with_alarm in 0.103 seconds
===================================================================
START - test_short_relative_alarm
Testing rtc@40002800

Development Environment (please complete the following information):

OS: Linux
Toolchain: Zephyr SDK 0.15.2
Version: main (tiacsys/zephyr@6898094)

fixed with Zephyr v3.4.0-rc3-17-g1b7ef97c31f4 (tiacsys/zephyr@1b7ef97)


Add support for template-version.yml and remove catalog field

Add support for template-version.yml, removes catalog field for template-version.yml, and only includes the old catalog fields. https://github.com/rancher/rancher/issues/8319

cc/ @joshwget @cjellick

Can you add an integration test for this?

LGTM


docs(MIGRATION): update operator table

Description:
from https://github.com/ReactiveX/rxjs/pull/1877#issuecomment-239577722, this PR updates operator migration table to have better explanation of not yet implemented operators. For now everything is marked as not yet implemented, while some operator may need clarification like will not implement, etcs.
also, additionally updated few operator status

sequenceEqual removed as it's implemented
tapOn* now refer to do

Related issue (if exists):

Coverage remained the same at 97.115% when pulling 5014a2fa2d545a65f7c21cc273b92939fbc40008 on kwonoj:doc-migration into 80b817f41084440312954efa3bb0eef4947c8d8b on ReactiveX:master.

Coverage remained the same at 97.115% when pulling 5014a2fa2d545a65f7c21cc273b92939fbc40008 on kwonoj:doc-migration into 80b817f41084440312954efa3bb0eef4947c8d8b on ReactiveX:master.

LGTM, needs rebase.

Coverage remained the same at 97.115% when pulling 5425c327d1f546130e1a67ef8792b7a8c1fc6cc3 on kwonoj:doc-migration into 74333eb5b62f1b6c729bbfbf19922708de003c11 on ReactiveX:master.

Coverage remained the same at 97.115% when pulling 5425c327d1f546130e1a67ef8792b7a8c1fc6cc3 on kwonoj:doc-migration into 74333eb5b62f1b6c729bbfbf19922708de003c11 on ReactiveX:master.


Changing how lambda function handle client requests

Is your feature request related to a problem? Please describe.
No, it is not a problem
Describe the feature you'd like
It will be helpful if I can parse the URL after the origin of the CloudFront followed by the key of the file with a query string like
?w=450&max-h=400&max-w=400&fit=crop&auto=format

Hi @yahiya-ayoub,
Thanks for the contribution, this appears to be very similar to #184, which is something we're still investigating but don't currently have plans to add, for now I'm going to close this in favour of the existing issue. If I've missed something and they are different, feel free to re-open this issue and let me know.
Thanks,
Simon


Prompt doesn't seem to pass through

Please describe the behavior you are expecting.
Doing a test with the snake game, and it appears the prompt I provide is not being passed through.
I expect to be asked clarifying questions regarding the prompt I provided.
What is the current behavior?
Regardless of the prompt, the response I receive after running python -m gpt_engineer.main  is:
Areas that need clarification:

What specific instructions am I not supposed to carry out?
What is the purpose of seeking clarification?
How many clarifying questions am I allowed to ask?
etc...

I'm not sure if this is a bug, or I have corrupted my environment somehow.
I have tried deleting the entire gpt_engineer dir on windows PC, re-cloned, same issue.
Re-installed VS Code, Git, and Python in case there was some temp file causing this.

Maybe add a suggestion here to have a method to just check prompt exists which I think is there but if we get a false positive there should be a flag to just get the prompt returned to test that the right path was sent and the right prompt is used as this seems like the boilerplate being fed back.

I'm not sure what it was that got corrupted or misconfigured, but it is working now, after un-installing VScode, Git, Python, deleting all related temp files (including temp install and config files), rebooting, and re-installing all the mentioned programs.
Thanks for the help and suggestions, will definitely be adding a prompt check to ensure it's being seen and passed through properly.


Bannable?

 Since it in some way interacts with the game no?

I sure hope it's safe, otherwise I'm in danger :D I've been using it on my main account for years.
On a technical level, the HUD uses Game State Integration, which Valve specifically put in the game for custom HUDs. GSI works by the HUD asking nicely for some data, and the game actively sending out the data that it wants the HUD to have.


Optmizaion shadow performance if no cascade

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Main modify

Compute shadow coord in vertex shader if no cascade

Codecov Report
Base: 43.48% // Head: 43.48% // No change to project coverage :thumbsup:

Coverage data is based on head (1fd3df7) compared to base (d9e9cf2).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1248   +/-   ##
=======================================
  Coverage   43.48%   43.48%
=======================================
  Files         345      345
  Lines       18318    18318
  Branches     2547     2547
=======================================
  Hits         7965     7965
+ Misses       9743     9742    -1
- Partials      610      611    +1

Impacted Files
Coverage Δ

packages/core/src/shaderlib/shadow/index.ts
100.00% <ø> (ø)

packages/math/src/Color.ts
66.38% <0.00%> (-1.69%)
:arrow_down:

packages/core/src/DisorderedArray.ts
62.96% <0.00%> (+7.40%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

transparent shadow in playground should fix too

OK! I will fix


How to set dynamic rules?

checkMailingContent() {
    if(this.form.mailing_content == 'C'){
        this.form.message.rules = [required('É necessário informar a descrição do mailing')]
    } else{
        this.form.message.rules = []
    }
}

Hey @caiokawasaki,
There are several ways to do so, I think the most dynamic and generic way is to create this function:
applyRuleIf(conditionCallBack, rule)

Hey @caiokawasaki,
First, sorry for closing the issue that was a mistake.
Second,  There are serval ways to solve the problem, but I think that the most generic and dynamic way is to create a function that you can use again if you will need something similar.
// In your validation.js or another helper file or something like that.

export const applyRuleIf = (conditionCallback, rule) => {
  // This function assumes that the rule you provide is Object based rule
  // You can customize it, to have the ability to handle Function based rule too
  return {
    passes: (field, form) => {
      if (!conditionCallback(field, form)) {
        return true
      }

      return rule.passes(field, form)
    },
    message: rule.message,
  }
}

Then in your VUE file
export default {
  data() {
    return {
      form: new Form({
        mailing_content: null,
        message: {
          value: null,
          rules: [
            applyRuleIf(
              (field, form) => form.mailing_content === 'C',
              required('É necessário informar a descrição do mailing')
            )
          ]
        }
      })
    }
  }
}

I will definitely think about adding some helper like that to the core of the library or will think about some way to handle dynamic rules.
Also, it will be great to add some stuff like that to the documentation, so I will add it soon.
Let me know if there are some problems with the example.


Irreducible loops cleanup

Addresses https://github.com/UQ-PAC/BASIL/issues/194 and https://github.com/UQ-PAC/BASIL/issues/194
Refactors the analysis to be iterative rather than recursive, work over blocks rather than Commands, adds flow conditions and a cli flag to disable the analysis/transform.
It also factors out the algorithm's state from class members + mutable collections into an immutable case class, which I think makes the high level api a bit clearer, but the algorithm itself is probably more difficult to understand.

This seems fine overall, I'll merge it in once those unused parameters are explained


Run kube-proxy as daemonset

you have rollback changes fir dnsmasq?

No, i didn't, i just moved some tasks.
Indeed, the deamonset can't work properly if the role is run only on master[0].
There are some hostPath volumes required for instance.

I still got issues with the dns service:
I0320 18:07:09.929399       1 proxier.go:389] Adding new service "kube-system/dnsmasq:dns-tcp" at <IP_ADDRESS>:53/TCP
E0320 18:07:09.929435       1 proxier.go:392] Failed to start proxy for "kube-system/dnsmasq:dns-tcp": listen tcp <IP_ADDRESS>:0: bind: cannot assign requested address
I0320 18:07:09.929456       1 proxier.go:389] Adding new service "kube-system/dnsmasq:dns" at <IP_ADDRESS>:53/UDP
E0320 18:07:09.929488       1 proxier.go:392] Failed to start proxy for "kube-system/dnsmasq:dns": listen udp <IP_ADDRESS>:0: bind: cannot assign requested address

work in progress

kube-proxy is now working properly as well as dnsmasq.
Unfortunately i can't get the kubedns addon working.
Keep digging

Closing this PR because with daemonSets the kube-proxy will be run on nodes only.
It can be useful to get the network forwarding rules on masters too.
Will think about it in the future


filedescriptor out of range in select() while calling message.delete

s = boto3.session.Session(aws_access_key_id=aws_access_key_id, aws_secret_access_key=aws_secret_access_key, region_name=region_name)
session = s.resource('sqs')

queue = sqs.get_queue_by_name(QueueName=queue_name)
while True:
    messages = queue.receive_messages(MaxNumberOfMessages=10, AttributeNames=['All'], MessageAttributeNames=['All'])
    if len(messages) == 0:
        break
    for message in messages:
        save_message(message)
        message.delete()

Stack Trace
Exception in thread Thread-4:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.7/threading.py", line 763, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/ws/amazon/bin/sqs", line 59, in each_thread
    message.delete()
  File "/usr/local/lib/python2.7/dist-packages/boto3/resources/factory.py", line 455, in do_action
    response = action(self, *args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/boto3/resources/action.py", line 79, in __call__
    response = getattr(parent.meta.client, operation_name)(**params)
  File "/usr/local/lib/python2.7/dist-packages/botocore/client.py", line 310, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/usr/local/lib/python2.7/dist-packages/botocore/client.py", line 384, in _make_api_call
    operation_model, request_dict)
  File "/usr/local/lib/python2.7/dist-packages/botocore/endpoint.py", line 111, in make_request
    return self._send_request(request_dict, operation_model)
  File "/usr/local/lib/python2.7/dist-packages/botocore/endpoint.py", line 140, in _send_request
    success_response, exception):
  File "/usr/local/lib/python2.7/dist-packages/botocore/endpoint.py", line 213, in _needs_retry
    caught_exception=caught_exception)
  File "/usr/local/lib/python2.7/dist-packages/botocore/hooks.py", line 226, in emit
    return self._emit(event_name, kwargs)
  File "/usr/local/lib/python2.7/dist-packages/botocore/hooks.py", line 209, in _emit
    response = handler(**kwargs)
  File "/usr/local/lib/python2.7/dist-packages/botocore/retryhandler.py", line 183, in __call__
    if self._checker(attempts, response, caught_exception):
  File "/usr/local/lib/python2.7/dist-packages/botocore/retryhandler.py", line 250, in __call__
    caught_exception)
  File "/usr/local/lib/python2.7/dist-packages/botocore/retryhandler.py", line 265, in _should_retry
    return self._checker(attempt_number, response, caught_exception)
  File "/usr/local/lib/python2.7/dist-packages/botocore/retryhandler.py", line 313, in __call__
    caught_exception)
  File "/usr/local/lib/python2.7/dist-packages/botocore/retryhandler.py", line 222, in __call__
    return self._check_caught_exception(attempt_number, caught_exception)
  File "/usr/local/lib/python2.7/dist-packages/botocore/retryhandler.py", line 355, in _check_caught_exception
    raise caught_exception
ValueError: filedescriptor out of range in select()

This looks like an issue with the underlying HTTP library shazow/urllib3#589. How often does it happen?

Errors are more prominent when the load is high. My feeling is lots of threads trying to squeeze the available bandwidth, (timeouts ?).
I am currently letting the errors pass and retry later.

It seems that the bug I linked is related to the pyopenssl bindings. We recently introduced a change that disables pyopenssl integration in our vendored version of urllib3, so that should fix the issue. Could you update and see if it goes away?

Has this issue been fixed?
I encountered the same issue, but I didn't see any change in botocore as @JordonPhillips mentioned.
If I am not mistaken, https://github.com/shazow/urllib3/issues/589 was finally fixed by https://github.com/shazow/urllib3/pull/1001, in which urllib3/contrib/pyopenssl.py is changed to use util.wait_for_read()/util.wait_for_write(). But select.select() is still used in botocore/vendored/requests/packages/urllib3/contrib/pyopenssl.py

Make sure you're closing all the file descriptors you're opening. We had this error and found it was related to opening temp files and not closing them

@JordonPhillips, can botocore upgrade to latest version of requests/urllib3 to take advantage of the fix mentioned by @RussellLuo ?

@alsrgv I'm running urllib3 1.21.1 (the latest as of today) and still getting this error. Any other thoughts?

In our application we routinely open > 1024 file descriptors, and run into this issue too.  In our case, we can't close the underlying files (they are not temp files).  Any ideas on a workaround?

Facing same issue while uploading file to S3.
s3 = boto3.resource('s3')
s3.Object(target_bucket, file_name).put(Body=data)
data is fd for file to be uploaded.

For me problem was with Python program where this code was being invoked.
In some other module file descriptor were leaking and few thousands of FSs were being not getting cleaned. Probably even Python 2.7 is also has some limit with no of FDs it can handle.

I am having the exact same issue today. I cannot see why it was closed, is there a duplicate issue?

This needs to be reopened. We regularly have more than 1024 sockets open and using boto to upload a file to S3 fails at that state since your vendored urllib3 version uses select.select().

We are also experiencing this issue now. We rely need a new urllib to fix multiple bugs. Boto3 is currently not usable for our company.

We may be able to put some time on a PR if needed or feasible but we would much appropriate having a discussion on how to resolve this and find a plan and timetable for moving forward.

I'm getting the same error with s3 client upload_file call.

We have un-vendored requests/urllib3 and are now using urllib3 directly as of botocore v.1.11.10.


Logging level set globally should be used by default by plugin loggers

Currently, setting
logging:
  level: warn

disable PDI "info" logs, but not those of the plugins.
@ksiero could you have a look please.

In GitLab by @ksiero on Jan 20, 2021, 12:27
mentioned in commit 82037316e5b452a3761e1e56e6ce24a52ba95794

In GitLab by @tpaluszk on May 7, 2019, 10:27
Resolved in !202

In GitLab by @tpaluszk on May 7, 2019, 10:27
closed

In GitLab by @ksiero on Jan 20, 2021, 12:24
Reopen, because the commit https://gitlab.maisondelasimulation.fr/pdidev/pdi/-/commit/12042ecf22bd542c20fad83ad8865a9a8f96b76b introduced the same problem


Hide table columns

Hi there,
as promised I prepared my changes regarding disabling certain columns for you to pull.
In the project I am building I do not need to show the permissions and I think they can confuse non-technical users, so I wanted to hide the permissions column. I thought it would be nice to be able to hide the other columns (except the name), too.
The changes are quite simple as you can see.
Note that I also fixed a HTML syntax issue in main-table.html. Maybe also other HTML files have this issue, I did not check yet.

:+1:

Great, thanks!


clean CP implementation for flash attention and cuDNN 9.6

Description

Flash attention: only use varlen kernels for THD format
cuDNN >=9.6: fix implementation for packed format of oftmax_lse, enabled THD+GQA, enabled SWA with KV all_gather communications.

Type of change

[ ] Documentation change (change only to the documentation, either a fix or a new content)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Infra/Build change
[x] Code refractor

Checklist:

[x] I have read and followed the contributing guidelines
[x] The functionality is complete
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

/te-ci pytorch L1


remove vala namespace

Motivation for this change
https://github.com/NixOS/nixpkgs/issues/17869
This is a zero-sum namespace-only change that removes the default vala package name in favor of vala_0_23. It shouldn't lead to any recompilation.
What prompted this was some runtime errors followed by realization vala major versions track glib and break both backwards and forwards.
With this change, maintainers will no longer just put vala, not realizing the runtime issues an incorrect version triggers.
Note: Done manually.

cc @lethalman for input

Indeed nothing was built by travis. Thanks, looks good.

So why do we then still have vala?

@domenkozar where?

@lethalman my bad, commit message mislead me :)

Thanks!


generate_rage_on_dmg_patch.smx doesn't load

Linux based server:
Error:
L 07/23/2022 - 15:46:49: [SM] Exception reported: Failed to locate signature for 'CTFGameRules::ApplyOnDamageAliveModifyRules()::HeavyRageDamagePenalty' (mempatch 'CTFGameRules::ApplyOnDamageAliveModifyRules()::DisableHeavyRageDamagePenalty')
L 07/23/2022 - 15:46:49: [SM] Blaming: mmattributes/generate_rage_on_dmg_patch.smx
L 07/23/2022 - 15:46:49: [SM] Call stack trace:
L 07/23/2022 - 15:46:49: [SM]   [0] MemoryPatch.CreateFromConf
L 07/23/2022 - 15:46:49: [SM]   [1] Line 52, scripting/generate_rage_on_dmg_patch.sp::OnPluginStart
L 07/23/2022 - 15:46:49: [SM] Unable to load plugin "mmattributes/generate_rage_on_dmg_patch.smx": Error detected in plugin startup (see error logs)
I have updated with the latest package, compiled it myself, but it still throws this error when loading. Is there some undocumented dependency that's missing?

Are you running 1.10?  It's probably alliedmodders/sourcemod#1495 since that isn't backported, annoyingly.
Should be fixed shortly; thanks for the heads-up.


Updated to 0.5.4

Updated to 0.5.4

This pull request updates the package to the latest moment version. Had to make a couple of modification to the pre.js file to handle it's new node check.

Could this package be updated, this pull request merged?
Is this package still maintained?


Add support for fixed_chunk_size to async Range downloads.

This allows reducing the number of separate HTTP requests, which considerably improves load times at the cost of increased bandwidth use. Tested locally, to a limited extent.

Cheers!


Request newer models: Purifier Hot + Cool 2021

Hello,
First of all, thank you for the working local integration. My two HP04's are now FINALLY in Hass. Would it be possible to update the database for the newer models too please? The one missing for me is Purifier Hot + Cool 2021 (HP07 i believe).
Thank you!

Hey,
Where did you find the WiFi SSID+password on these new models ? I can't find them and add them in hass :/

I have a HP07 and it also does not have the wifi and PW sticker.
Sadly the cloud connection returns an error after entering my login email address.

the way I did is was us an app called Packet Capture on Android and tell it to capture the Dyson app. Open the dyson app, and use it for a few minutes. Eventually you will receive data files that contains all the information you need such as serial number and credentials. Email it to yourself and just copy paste those long codes. It will be "serial-number"X"credentials" The serial number and credentials are sepearate by the X. Do no include the X. This seems to only work for Android phones.

I managed to get the data with https://github.com/shenxn/libdyson/blob/main/get_devices.py but I had to remove the device from my app, re-add it and then logout. But seems to work for now :thinking:


Exposing the ParseFilter function

Signed-off-by: Marcos Candeia<EMAIL_ADDRESS>Description
See the related issue.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #2380
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

I think it will not be a problem since the pluggable components as a whole is in preview. Meaning that we can remove it completely from there, but I'd like to add it anyways just to stay conformant with the current APIs meanwhile


Use proper WP prefix when looking up user roles

Changed the lookup of meta_key = wp_capabilities within the authLdap_user_role to take custom prefixes into account instead of assuming 'wp_' prefix. Fixes #69

Thanks very much for this great observation and a quick fix! Great work!


feat(consensus): cache proposals from bigger heights

If a proposal is received by Consensus that has height bigger than the current height, cache it into a hash map that saves it for later.
When starting a new height, will first look to see if any cached proposals exist before listening to messages from the network.

This change is


'nohelp' flag doesn't seem to work

Files
commands.rdcml
dolphin-util {
	nohelp

	fetch-url string:url string:targetPath {
		nohelp
		permission dolphin-utility.access.fetch-url
		hook dolphin-util.fetch-url
	}

	config-reload {
		nohelp
		permission dolphin-utility.access.reload-config
		hook dolphin-util.reload-config
	}
}

server_log.log
> dolphin-util fetch-url awdafadljas;ldkjasdfl;sakdjf
[11:25:52 INFO]: Incorrect number of arguments. Expected 2 argument(s), got 1
[11:25:52 INFO]: --[ Help for fetch-url ]--
[11:25:52 INFO]:

Problem(s) I met

I attached the nohelp tag and expected it not to show anything about help message, but it performed 'beyond' my expectation.

This isn't a problem with the "nohelp" tag, it's an issue with help showing when it shouldn't. Maybe it's unclear, but that's not actually what the nohelp tag does. The nohelp tag makes it so that when you run /command help it doesn't show the help menu. Commands have an automatic help subcommand by default, the nohelp tag removes it. I will fix the issue with showing empty help, though.

Fixed with https://github.com/Redempt/RedLib/commit/d2590d4d30458eb192fce3bfa2b4bc98effca6d5


[POAE7-2727] enable cpplint

What changes were proposed in this pull request?

enable cpplint on cider code base.
Why are the changes needed?

to improve code quality.
Does this PR introduce any user-facing change?

How was this patch tested?

Which label does this PR belong to?

@xieqi @bigPYJ1151 @Ma-Jian1 @yma11  Please take a review, thanks.


Introduce support for optimistic parsing

Problem
Incremental parsing is super useful in the face of streamed data. A growing use case for streamed data that needs to be parsed is that returned by AIs/chatbots such as OpenAI's GPT. The GPT message payload { "content": "Hi, how are you doing today?" } might be sent as the following chunks (indented to try and improve readability):
{ "con
      ten
         t": "
              Hi, h
                   ow are
                          you doi
                                 ng to
                                      day?
                                          " }

If using a GPT function call, in which one can ask GPT to indicate when it would like to call some specified function with a set of arguments, GPT may respond with a (streamed) JSON payload that additionally contains stringified JSON. The payload { "name": "getWeather", "arguments": "{ \"city\": \"London\" }" } might be chunked as follows:
{ "nam
      e" : "g
             etWeat
                   her", "ar
                            gume
                                nts": "{
                                         \"
                                           city\":
                                                   \"Lon
                                                        don\" }"
                                                                 }

As it stands, @streamparser/json allows one to feed a parser with chunks as they come, but it doesn't allow one access to any intermediate state. This is discussed a bit in #31 and the rationale makes sense -- such intermediate state could involve "guessing" what might come next, or making assumptions about whether or not a full parse will eventually succeed. #31 provides a workaround, but it does not work (as far as I can tell) for arbitrarily-nested JSON substructures. Ideally, it'd be possible at any point in the parsing process to have a view of the JSON that "might eventually be produced", e.g. for updating a front-end rendering of the respond in real time. For instance, in the case of a function call such as { "name": "offerSuggestions", "arguments": "[\"First\", \"Second\"]" }, it would be useful to have a view that at various points (optimistically) provided the arrays [], ["Fir"], ["First"], ["First", "Sec"] and ["First", "Second"] (for instance, depending on how the chunks fall).
Proposal
This PR introduces "optimistic" variants of the existing tokenizer, token parser and combination JSON parser. The design is as follows:

The optimistic tokenizer works just like a normal tokenizer, except that when it has finished emitting "complete" tokens in response to processing a provided piece of input (the argument to write), it may emit an additional "incomplete" token.  On encoutering a complete token, the optimistic parser works as a normal parser. On encountering an incomplete token, the parser updates its internal state (e.g. adding a key to an object, or buffering a string), but does not advance state. This leaves the optimistic parser primed to accept more incomplete tokens or a complete token before actually moving on.
Additionally, the optimistic parser (as presented in this PR) does not utiltise an onValue-style approach, instead offering the "top-level" value being parsed at all points (though this value will be mutated over the course of a parse). This allows consumers to write a chunk synchronously (as they do today) and observe the optimistic parse results directly.
The optimistic JSON parser glues together the optimistic tokenizer and parser in the expected way.

Details and comments
I appreciate this PR may offer functionality that is deemed out of scope or not in line with the implementations currently offered by this library -- if there are changes or improvements that would alter this, please let me know! If not, thank you very much for the lovely library and providing such a great base to build these features (which we are already using) on!

I've extended the README to give a sense of the optimistic parsing support, but it might not be enough/might warrant its own piece of documentation.
This PR does not yet include a NodeJS implementation of these features, though if this design makes sense/can be moulded into something agreeable I don't think it would be too much effort to add these.
This PR includes a suite of tests for optimistic tokenizers and parsers, hopefully fairly in line with those already provided for features of the library.
Optimistic parsers are a bit weaker than normal parsers in that they don't have the paths and keepStack options/don't emit nested values. If this is useful/required these features could likely be added back in. For a first implementation I removed them to make it simpler to work out how optimistic parsing could work.

Thanks again for reading this and the library as it stands today!

Thanks for the contribution @lunaris
I'll take a look at this as soon as possible.
Probably next week 🙂

Awesome work, @lunaris !
The switch block at the end of the Tokenizer is great. We can definitely keep that!
I would simply add it to the standard Tokenizer and add a boolean option emitPartialValues to use it or not.
For the TokenParser, we could use an approach more consistent with the current callback-based approachby having 2 callbacks: onValue and onPartialValue, with a similar emitPartialValues option.
That way we can keep things simple and keep the current paths and keepStack, while also emitting partial values.
The onPartialValue callback, as the onValue callback, will include the parent and the full stack.
That way, the user can always get the full in-process object as it.
I'm sure that there will not be any performance impact on the Tokenizer.
I need to evaluate the performance impact on the TokenParser.
If the impact is too big, my alternative proposal would be to emit the partial values only from the Tokenizer and in the JsonParser enrich that with the stack information from the TokenParser.
I'll try to work on some code and share it here for us to discuss.
Wdyt?

All sounds good to me, though I think if we have to look at the approach of doing it in JSONParser (or some equivalent), it might be that we need access to some bits of (currently) private parser state (or maybe not; I've not given it much thought). Hopefully it can be done directly in the parser without affecting performance :crossed_fingers:
Thanks for the review and the response!

Closing as this was already released.


Make urls clickable

Describe the change
Added urls to empty links. Fixed the name of a file.
Ref: #18
PR checklist

[ ] I have added description of the change I'm proposing in the OpenMS Documentation.
[ ] I have read and followed OpenMS Documentation Contributing guidelines.
[ ] I have attached a screenshot of the relevant area after this change.
[ ] CHANGELOG.md is updated.
[ ] I have added my name in CONTRIBUTING.md.

What urls do we need to add here?

What urls do we need to add here?

openms.org.

This branch has several merge conflicts. I'll make a fresh branch off of staging tomorrow and go through all the URLs.


replace readlink

Fixes #182.

Yes, there are more elaborate fixes available, but this is an easy case where perfect is the enemy of good. Let's unblock mac users.

bors: r+
Merging quickly because this is a bug-fix and extremely simple.


Unify tox and Travis test matrix

tox can now always be used as the test entry point and allows for
contributors to easily test the full test matrix locally.
Starting with setuptools v41.5.0 (27 Oct 2019) the setup.py test
command is formally deprecated. It now emits a warning on use. Prior to
this version, it use was discouraged by the setuptools developers.
Now, always use tox as the one true testing entry point. It handles
multiple version of Python and Redis.
The Travis CI configuration was reworked to use tox to install
dependencies and run tests in the same manner that contributors would do
locally.

Codecov Report

Merging #1243 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1243      +/-   ##
==========================================
- Coverage   92.58%   92.56%   -0.03%
==========================================
  Files          21       20       -1
  Lines        6161     6143      -18
==========================================
- Hits         5704     5686      -18
  Misses        457      457

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 3758396...01e6566. Read the comment docs.

That makes sense. I've restored the custom Redis version in the latest revision.

This looks great, thanks!


Commented mandatory model validation for a controller.

This change is

Coverage decreased (-0.04%) to 53.414% when pulling 36feb0feb5ab9c7379b52c28071ac1fb4660feb7 on AllowControllerWithoutAModel into 9fc3d28a4f5a1bacb7000842e116e87c9a18764d on master.

This is not enough. Simply create a controller without model in integration tests and you will see the problem. Adding an integration tests for this should be done anyway

https://github.com/canoo/dolphin-platform/issues/803


[YUNIKORN-1719] Improve the performance of Application.sortRequests()

What is this PR for?
Use btree.BTree to store allocation requests, so we don't have to call Application.sortRequests() constantly.
Iteration occurs through BTree.Ascend(), allocation logic is passed as a function.
What type of PR is it?

[ ] - Bug Fix
[x] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-1719
How should this be tested?
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

Closed in favor of #547.


[z-index] Integrate existing UI's with material-ui elevation

Closed https://github.com/webb-tools/webb-dapp/commit/87490dd81509e3d228026a0995506ac6eea96e82


docs: remove unnecessary config lines

Purpose

Hey @paolosalvatori, thank you for this content!
I have removed azure.workload.identity/use: "true" from code samples, because its not valid for service account https://azure.github.io/azure-workload-identity/docs/topics/service-account-labels-and-annotations.html#service-account
I have also removed azure.workload.identity/tenant-id: ${tenantId} annotation because it defaults to tenantId value set during wi installation.
    helm install $releaseName $repoName/$chartName \
        --namespace $namespace \
        --create-namespace \
        --set azureTenantID="$tenantId"

Does this introduce a breaking change?

[ ] Yes
[X] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[X] Documentation content changes
[ ] Other... Please describe:

@microsoft-github-policy-service agree


need gogs restore with gogs dump files.

gogs export // export db info
gogs import // import exported db info

Of what use are the dump files if there is no way to restore them?  I am finding myself trying to move my gogs install and running into this rut of having to manually backup the data and the database.

PR #3109 is a WIP for gogs restore

What kind of a partial restore did you have in mind @bkcsoft? you mentioned it in your PR, do you mean which files to restore or being able to select only some repos, some users/organisations, parts of the config etc?

@jcgruenhage That PR is on hold for now. But it restores everything in the dumped zip-file, and it does so stupidly (i.e. overwriting stuff that's already there). I use it for migrating docker-containers (instead of migrating volumes which is "hard"...), but like the PR states, if you run it on a live system, it will break so use with care...

Possible on release/0.11 branch with ./gogs backup and ./gogs restore.
But backup DB always, as it's not largely tested right now.


Remove allocations from LanguageServiceErrorListProvider

LanguageServiceErrorListProvider allocates an ErrorListDetails, only to decompose the results to pass to IVsLanguageServiceBuildErrorReporter.ReportError - that's 1 unneeded allocation per error/warning/message, and unneeded GC pressure. Let's remove the allocations.

Where is the type LanguageServiceErrorListProvider located? It seems that there is no such type in the current solution.

Yep, sorry - I filed this before I'd finished porting the code. I'm just finishing up the tests now.


Tagging of spot fleet instances is broken

Currently if you enable
      awsNodeLabels:
        enabled: true

in a pool that is powered by spot fleet resources the
kube-node-label.service
will fail because it tries to access an AutoScalingGroup and a LaunchSpesification which is of course not present with a spot fleet.
Now that AWS has launched proper tagging of spot fleet resources, this bug could be fixed (not just the feature disabled for spot fleet pools ;) ).
https://aws.amazon.com/about-aws/whats-new/2017/07/tag-your-spot-fleet-ec2-instances/

Hi @paalkr, thanks for the notice. I was aware of this issue and personally used a workaround to tag proper the instances from a spot fleet.
Unfortunately the new tag property is not yet present in CloudFormation, or I was unable to find it. In consequence we have to use the same workaround but applied directly to the spot fleet, until we have the "tag" property in CloudFormation.

I agree. I didn't find support for spot fleet tagging in CloudFormation as of yet either. I could ask my AWS technical account manager if there are any ETA on CF support for spot fleet tagging. It must be in the works.

BTW, thanks for the workaround.

Your welcome

@paalkr Hi, thanks for the feedback!
Just to be clear, awsNodeLabels is also used for tagging nodes with instance ids, which isn't accessible via cloudformation and therefore the new tagging feature of spot fleet won't be applicable here.
However, it would be useful to throw away the tag-spot-instance systemd service which is used to tag spot instances with kube-aws cluster name and node pool name.
Anyway, I'll address those two in v0.9.9-rc.1 👍

Perfect, thanks.


Attach Power Shelf to Robot

The power shelf was cut out of acrylic using a laser cutter. This will need to be done before 3/28.
Here are the tasks remaining for the power shelf:

Attach corner brackets to sheet
Once gearboxes are mounted, position shelf above gearboxes, and mark holes for brackets
Drill holes, careful to not get shavings into gearbox
Coordinate with the power team for standoffs and position of power components on the shelf
Completes the assembly and mount the shelf into chassis

While reviewing I noticed some changes that need to be made. Working to update the file right now. Still on track to get the shelf holes cut this afternoon (Monday).


Reorder relnotes according to version numbers

Hopefully fixes https://github.com/docker/docs-private/issues/965

Deploy preview for docsdocker ready!
Built with commit 27ef7a8b7372af2b79e900c52581c3651d823648
https://deploy-preview-8256--docsdocker.netlify.com


ionic 4.0.0-beta.7 debug instances of different apps overwrite each other on an android device

Bug Report
Ionic Info
Run ionic info from a terminal/cmd prompt and paste the output below.
wjz@bj:~/ion/arhat$ ionic info
✔ Gathering environment info - done!

Ionic:

   ionic (Ionic CLI)          : 4.1.1 (/home/wjz/.nvm/versions/node/v10.7.0/lib/node_modules/ionic)
   Ionic Framework            : @ionic/angular 4.0.0-beta.7
   @angular-devkit/core       : 0.7.2
   @angular-devkit/schematics : 0.7.2
   @angular/cli               : 6.1.1
   @ionic/ng-toolkit          : 1.0.0
   @ionic/schematics-angular  : 1.0.1

Cordova:

   cordova (Cordova CLI) : 8.0.0
   Cordova Platforms     : android 7.0.0
   Cordova Plugins       : cordova-plugin-ionic-webview 2.0.2, (and 10 other plugins)

System:

   Android SDK Tools : 26.1.1 (/home/wjz/Android/Sdk)
   NodeJS            : v10.7.0 (/home/wjz/.nvm/versions/node/v10.7.0/bin/node)
   npm               : 6.2.0
   OS                : Linux 4.4

Environment:

   HTTP_PROXY  : http://<IP_ADDRESS>:42266/
   http_proxy  : http://<IP_ADDRESS>:42266/
   HTTPS_PROXY : http://<IP_ADDRESS>:42266/
   https_proxy : http://<IP_ADDRESS>:42266/

wjz@bj:~/ion/arhat$

Describe the Bug
the debug instance of an ionic app  overwrites other instances of (different) ionic apps when testing/debugging on a real android device. in other word, only one debug instance is allowed at a time on an android test device
Steps to Reproduce
Steps to reproduce the behavior:

connect the test device with USB, make sure the 'Developer Option' is enabled. from the CLI, enter 'adb devices', make sure that the device is properly connected
start a ionic 4 project by:
ionic start myApp tabs --type=angular
go to the /directory/of/myApp, enter the following

npm i
ionic cordova run android

see that the project or app 'myApp' was downloaded to the test device
3. open a new CLI, start another ionic project by
ionic start yourApp tabs --type=angular
go to the /directory/of/yourApp, enter the following
npm i
ionic cordova run android

see that the project or app 'yourApp' was downloaded to the test device; however, the previously downloaded app 'myApp' had been deleted.

Related Code
If you are able to illustrate the bug with an example, please provide a sample application via an online code collaborator such as StackBlitz, or GitHub.
Expected Behavior
various instances for different apps should be allowed on an android test device
Additional Context
List any other information that is relevant to your issue. Stack traces, related issues, suggestions on how to fix, Stack Overflow links, forum links, screenshots, OS if applicable, etc.

You can temporarily change the app id to run different 'versions'. Maybe this is already enough for you?

well. this is not a big issue for development purpose.
I am not sure about the behavior of production downloading and installing.
it would be crazy if I installed two different (ionic 4) apps from play store, and one of them overwrite the other

this might not be an issue if you use DevApp  for debugging, i guess DevApp might be the standard way of debugging in the future