PartialMatchFilter is a real performance killer

Affected Version
SS 3 & 4
Description
The default search options should have safe behaviour on large tables
On large table, the default behaviour makes like query starting with %
This prevent using any indexes on the table, leading to slow queries
I'm aware that "like" is not great and that fulltext should be the proper alternative, nevertheless, it's not great
Maybe this is acceptable on small tables, but for large table, a safer default should be used (query% instead + reverse query ?)
Steps to Reproduce

Make a search on a very large member list on surname
This make a query %myquery% on Surname
Index doesn't work well due to starting % leading to slow queries

Extra info
The opposite case is also possible: a LIKE expression that starts with a wild card. Such a LIKE expression cannot serve as an access predicate. The database has to scan the entire table if there are no other conditions that provide access predicates.
Tip
Avoid LIKE expressions with leading wildcards (e.g., '%TERM').
from: https://use-the-index-luke.com/sql/where-clause/searching-for-ranges/like-performance-tuning

why could mysql not use like on the index? in other words, why not have mysql fix this? Is that an option? One thing to try is to use LIKE "foo%"
see: https://stackoverflow.com/questions/9928929/mysql-like-query-takes-too-long


Final TS tidyup

Just some last TSLint passes. Also I did the "manual remove-and-sort" process on the imports (i.e.: remove them all and Ctrl-. until the errors stop ;))

Yeah, that's an upcoming dev PR. There are some places that aren't running the linter (unit tests mostly)


AutoStart=false and initialDuration issue

When I set AutoStart=false,  it causes the timer to not start from its initialDuration when I start the timer. Instead, It starts from 0.
I would be so grateful if you fix this issue.

Can you please share the code that is causing this issue?


Consider using launchWhenStarted instead of launch

I recently came across an issue that was due to the fact that the flow collection started with observe operator is actually performed right before the lifecycle reaches the STARTED state.
Checking the source code, we can indeed see that:
/**
  * Started state for a LifecycleOwner. For an {@link android.app.Activity}, this state
  * is reached in two cases:
  *

  *
after {@link android.app.Activity#onStart() onStart} call;
  *
right before {@link android.app.Activity#onPause() onPause} call.
  *

  */
  STARTED,

Well, I can at least tell that onStart() on a lifecycle observer is indeed invoked right before an androidx.Fragment reaches the STARTED state.
It may all sound not really important, but it turned out to matter today for some particular case. I could easy fix that with using launchWhenStarted instead of launch, inside the operator implementation.
This what I'm using in my project (it also has different naming, which I find more explicit. It also has a collectWhileResumed variant):
@file:Suppress("unused")

package com.peterlaurence.trekme.util

import androidx.lifecycle.DefaultLifecycleObserver
import androidx.lifecycle.LifecycleOwner
import androidx.lifecycle.lifecycleScope
import kotlinx.coroutines.Job
import kotlinx.coroutines.flow.Flow
import kotlinx.coroutines.flow.collect

/**
 * Utility extension function to start collecting a flow when the lifecycle is started,
 * and *cancel* the collection on stop, with a custom collector.
 * This is different from `lifecycleScope.launchWhenStarted{ flow.collect{..} }`, in which case the
 * coroutine is just suspended on stop.
 */
inline fun <reified T> Flow<T>.collectWhileStarted(
        lifecycleOwner: LifecycleOwner,
        noinline collector: suspend (T) -> Unit
) {
    ObserverWhileStartedImpl(lifecycleOwner, this, collector)
}

/**
 * Utility extension function on [Flow] to start collecting a flow when the lifecycle is started,
 * and *cancel* the collection on stop.
 */
inline fun <reified T> Flow<T>.collectWhileStartedIn(
        lifecycleOwner: LifecycleOwner
) {
    ObserverWhileStartedImpl(lifecycleOwner, this, {})
}

class ObserverWhileStartedImpl<T>(
        lifecycleOwner: LifecycleOwner,
        private val flow: Flow<T>,
        private val collector: suspend (T) -> Unit
) : DefaultLifecycleObserver {

    private var job: Job? = null

    override fun onStart(owner: LifecycleOwner) {
        job = owner.lifecycleScope.launchWhenStarted {
            flow.collect {
                collector(it)
            }
        }
    }

    override fun onStop(owner: LifecycleOwner) {
        job?.cancel()
        job = null
    }

    init {
        lifecycleOwner.lifecycle.addObserver(this)
    }
}

inline fun <reified T> Flow<T>.collectWhileResumed(
        lifecycleOwner: LifecycleOwner,
        noinline collector: suspend (T) -> Unit
) {
    ObserverWhileResumedImpl(lifecycleOwner, this, collector)
}

class ObserverWhileResumedImpl<T>(
        lifecycleOwner: LifecycleOwner,
        private val flow: Flow<T>,
        private val collector: suspend (T) -> Unit
) : DefaultLifecycleObserver {

    private var job: Job? = null

    override fun onResume(owner: LifecycleOwner) {
        job = owner.lifecycleScope.launchWhenResumed {
            flow.collect {
                collector(it)
            }
        }
    }

    override fun onPause(owner: LifecycleOwner) {
        job?.cancel()
        job = null
    }

    init {
        lifecycleOwner.lifecycle.addObserver(this)
    }
}

Hi @peterLaurence,
Your change looks good. Could you please tell more about the use case where launchWhenStarted mattered?
Please consider opening a pull request for your changes - both the naming of the functions and the launchWhenStarted change. I'll be happy to review them and integrate.
Thanks!

Hi @peterLaurence,
Your change looks good. Could you please tell more about the use case where launchWhenStarted mattered?
Please consider opening a pull request for your changes - both the naming of the functions and the launchWhenStarted change. I'll be happy to review them and integrate.
Thanks!

Hi @psteiger,
When the flow collection is done inside a fragment, and when we want trigger a view change based on a particular event, we can use collectWhileStarted operator. The issue I had is was due to the fact that I had to remove a child view and add it back to the view hierarchy, assigning the same id. If this is done when the state is STARTED, the newly added view has its state automatically restored (using the state of the previous view). While if this is done when the state isn't yet STARTED, the view state isn't automatically restored.
On the other hand, for other use cases, I don't think using  launchWhenStarted instead of launch will make a difference. Anyway, I think that this is a good thing that the name of the operator explicitly tells when actions are triggered.
If that sounds ok to you, I can do a PR.

Hi @psteiger,
When the flow collection is done inside a fragment, and when we want trigger a view change based on a particular event, we can use collectWhileStarted operator. The issue I had is was due to the fact that I had to remove a child view and add it back to the view hierarchy, assigning the same id. If this is done when the state is STARTED, the newly added view has its state automatically restored (using the state of the previous view). While if this is done when the state isn't yet STARTED, the view state isn't automatically restored.
On the other hand, for other use cases, I don't think using  launchWhenStarted instead of launch will make a difference. Anyway, I think that this is a good thing that the name of the operator explicitly tells when actions are triggered.
If that sounds ok to you, I can do a PR.

Ok @peterLaurence , I understand the failing use case and I don't think using a lifecycle-specific launch would break other use cases.
A PR would be welcome! Thanks.

Ok @peterLaurence , I understand the failing use case and I don't think using a lifecycle-specific launch would break other use cases.
A PR would be welcome! Thanks.

Ok great, I'll do that.

Ok great, I'll do that.

Solved by PR #3

Solved by PR #3

onStart() on a lifecycle observer is indeed invoked right before an androidx.Fragment reaches the STARTED state

@peterLaurence Are you sure? I see that lifecycle.currentState is indeed CREATED during Activity/Fragment onStart() (in accordance to the docs), but it is already STARTED during LifecycleObserver.onStart(), where flow collection is launched.
You can also check the code: mState is currentState, and sync() is where observers are notified.

@gmk57 I'll double check. Anyway, there was a difference between using launchWhenStarted and launch. Even though, if you're right, there shouldn't have been a difference.


Missing vocabulary schema option

Hi !
In the "CDMOnboarding" package, there are two functions that don't allow to specify a vocabulary schema :

For https://github.com/darwin-eu/CdmOnboarding/blob/main/R/CdmOnboarding.R : the function dataTablesResults the parameter vocabDatabaseSchema is missing (see : PR #5 )
For https://github.com/darwin-eu/CdmOnboarding/blob/main/R/DedChecks.R (lines 40-41) : the function cdm_from_conn from the CDMConnector package does not allow to specify a vocabulary schema, when it is not the same as the CDM one.

Thanks for your help !

Thanks for raising this issue and making a PR.
We are going to remove support for a separate vocabulary schema. Most DARWIN analytics (and e.g. OHDSI Atlas) does not support this.
Please consider moving your vocabulary tables to the cdm schema. A workaround is to create views in the cdm schema referring to the tables in the vocabulary schema.


Add support for retainBackups when deleting clusters

The cluster deletion API endpoints have a retainBackups query parameter, could you also support it in this package ?
See: https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Multi-Cloud-Clusters/operation/deleteCluster and https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Clusters/operation/deleteLegacyCluster
Thanks 🙂

Thanks for submittig this! I will check into this later in September.


fix: Remove unreadable CNS state file upon CNS service start

This change removes unreadable state file ( azure-cns.json ) while starting the CNS service

Reason for Change:

Issue Fixed:

Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests

Notes:

/azp run


An overall document update and new release

Why:
What:
Scope of work:

[x] Create a mock release to get a comprehensive list of changes (then stop it)
[x] Share here to discuss what information is needed to update what docs

@jmcook1186 here are PRs which will be included in next release
What's Changed

Sync release with main by @narekhovhannisyan in https://github.com/Green-Software-Foundation/if/pull/958
Emit warning about node-level config by @manushak in https://github.com/Green-Software-Foundation/if/pull/962
Fix copy-param to support string and number for from by @manushak in https://github.com/Green-Software-Foundation/if/pull/967
Rename global-config to config by @manushak in https://github.com/Green-Software-Foundation/if/pull/963
Add mapping feature by @manushak in https://github.com/Green-Software-Foundation/if/pull/923
Fix --debug mode logs by @manushak in https://github.com/Green-Software-Foundation/if/pull/969
Improve debug logs by @manushak in https://github.com/Green-Software-Foundation/if/pull/974
Update mapping feature to map output parameters by @manushak in https://github.com/Green-Software-Foundation/if/pull/973
Move mapping functions by @manushak in https://github.com/Green-Software-Foundation/if/pull/978
Sci-embodied redesign by @narekhovhannisyan in https://github.com/Green-Software-Foundation/if/pull/995
Fix broken manifests by @manushak in https://github.com/Green-Software-Foundation/if/pull/998
Update explain feature by @manushak in https://github.com/Green-Software-Foundation/if/pull/996
Time sync fix by @narekhovhannisyan in https://github.com/Green-Software-Foundation/if/pull/1003
Granular aggregation by @narekhovhannisyan in https://github.com/Green-Software-Foundation/if/pull/1008
feat(src): add support for appending to existing outputs by @jamescrowley in https://github.com/Green-Software-Foundation/if/pull/932
Enhance plugins with an inline arithmetic feature by @manushak in https://github.com/Green-Software-Foundation/if/pull/1004
Fix manifests by @manushak in https://github.com/Green-Software-Foundation/if/pull/1012
Fix and add missing manifests by @manushak in https://github.com/Green-Software-Foundation/if/pull/1014
user-defined upsampling resolution by @mouhamadalmounayar in https://github.com/Green-Software-Foundation/if/pull/990

Documentation needed for at least

[ ] --append
[ ] Inline arithmetic
[ ] Community PR for time Sync
[ ] Plugin Factory
[ ] Plugin builders guide

cc @jmcook1186 @narekhovhannisyan @manushak can you please review and indicate any other functionality that might have been skipped


Ruby - provide an option in extconf.rb to use system grpc

Should this be an issue in the gRPC issue tracker?
yes
What version of gRPC and what language are you using?
1.3.2 with ruby (though it is not specific to any particular version)
What operating system (Linux, Windows, …) and version?
Debian GNU/Linux (in all versions, using sid/unstable)
What runtime / compiler are you using (e.g. python version or version of gcc)
gcc version 6.4.0 20170704 (Debian 6.4.0-1)
What did you do?
I'm packaging ruby binding of grpc and it is trying to build libgrpc.a
What did you expect to see?
Similar to how OpenSSL or zlib can be used from the system, I should be able to use libgrpc.a from system since grpc is already packaged in debian.
What did you see instead?
It is trying to build libgrpc.a but failing to find openssl (may be because bugs in how the build system is setup, but there should be an option to use already built libgrpc.a).
Anything else we should know about your project / environment?
You can see more info about the steps I tried https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867541

Is there something in particular that is preventing full source compilation, or use of a grpc gem with the core library and ruby-c-extension pre-compiled?
Also by version 1.3.2, I assume this is the version for libgrpc.a? Note that newer versions of the ruby wrapper aren't tested with older versions of the c-core library.

@apolcyn , there are two reasons for not doing full source compilation

When tried, it could not find openssl because debian already use openssl 1.1 whereas grpc still supports only openssl 1.0.

The already built libgrpc.a or libgrpc.so (since both are available, .so is preferred) is patched to support openssl 1.1. So we really don't need to build it twice (debian already provides libgrpc C and C++ libraries, using them makes it easier to maintain, as we don't have to apply patches twice for example like adding support for openssl 1.1).

In debian, we should build every binary from source code as per debian policy, so pre-built binary cannot be used.

The ruby version is also 1.3.2 since I want to use libgrpc.so built from 1.3.2.
I managed to make it work with this patch https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-grpc.git/tree/debian/patches/no-make-in-extconf.patch but it would be nice if it was supported with a conditional like ENV['EMBED_GRPC'] = 'false'. It also requires a change in LDFLAGS when building libgrpc.so (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867541#89).

adding @nicolasnoble

Chatted offline - question on the maintenance of this package: I guess the libgrpc debian package is  a little out of date, and we are also seeking maintainers for it. Does maintenance of a grpc-ruby debian package entail maintenance of the libgrpc package as well?
As for the option of including an EMBED_GRPC option in the extconf.rb, this seems doable but I'm not sure if it would be more beneficial than a custom patch if this is a one-time use case.

@apolcyn I offered to be a co-maintainer, but I was asked to sent patches instead https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867541#27
I'm fine with custom patch, but having it included officially may help people trying to package it for other distros as it took quite a lot of effort for me to figure this out by myself. If it was just setting yes or no, I'd have found this easily like for openssl or zlib.

I'd be better if the package was maintained in a git repo for other people to contribute easily as I suggested in the bug above.

Just note that we don't currently have anything in place for testing this support - ok with putting such options in the main extconf.rb file here, but just note their maintenance would likely be best effort.

@apolcyn is this issue still relevant?

Rethinking this, perhaps we can let the user pass in a pre-built core library when building the ruby gem.

Closing since I won't get to this any time soon.  If this is important, please ping this issue, file a new one, or file a patch.


feat:remote_voices

dont depend on piper from pypi
improve voice caching/download
dynamic voice list from huggingface https://huggingface.co/rhasspy/piper-voices

Summary by CodeRabbit
Release Notes

New Features

Introduced a new text-to-speech synthesis module with enhanced voice management.
Added support for loading and synthesizing audio from ONNX models.
New configuration options for model paths and remote URLs.
Improved voice retrieval and error handling mechanisms.

Bug Fixes

Resolved issues with speaker ID handling in single-speaker scenarios.

Documentation

Updated installation and configuration instructions in the README for clarity and new features.

Chores

Enhanced package metadata to include additional files during distribution.
Updated dependency management in requirements.

This plugin cannot be build on Debian Trixie which runs Python 3.12.

This plugin cannot be build on Debian Trixie which runs Python 3.12.

why?

This plugin cannot be build on Debian Trixie which runs Python 3.12.

why?

There is no piper_phonemize for Python 3.12 on PyPi.

maybe we could build a wheel until upstream solves it properly https://github.com/rhasspy/piper-phonemize/issues/33

Tested with Python 3.11, seems fine so far.


Added custom configuration to slave connections

This commit allows for custom configurations to be passed when
establishing connection to slaves.
While we can assume that with traditional rails apps, a straightforward
host substitution will be suffice, this assumption cannot be made for
projects of a certain scale, where slave boxes may have custom
configurations (maybe different password/username/etc).
This commit's approach relies on the consumer of this package to specify
a lambda that takes in the slave hostname and returns a configuration
object to pass to Mysql2Adapter. Alternatively, we could make the
consumer pass in a hash, but I think this approach is slightly cleaner
and more flexible.
@camilo @arthurnn @jasonhl
Also note: I don't quite know how to properly test this. It seems like the MysqlAdapter does not expose its config object in something that I can access..

MysqlAdapter does not expose its config object in something that I can access..

It's mostly for tests,  as I want to assert that the mysql connection is created with the correct config.

It's mostly for tests, as I want to assert that the mysql connection is created with the correct config.

Is kinda OK in this context to reach into the object via .instance_eval{ } or something like that, the other thing you can do is to make it exec sql and ask for the hostname and user name

ping @arthurnn not sure if you are in context, do ask if any of this makes no sense.

I've updated according to feedback and added unittests. However, I'm unsure what how this code triggered failed test? Also I can't get test to run locally according to the (outdated) instructions under spec/README. Any feedback?


Can't set fan preset modes: failed to call service fan/set_present_mode. required key not provided @ data ['preset_mode']

Trying to set the preset mode on a Levoit Core 400S.
Getting:
failed to call service fan/set_present_mode. required key not provided @ data ['preset_mode']
The documented service call which works is:
service: fan.set_preset_mode
data:
  preset_mode: sleep
target:
  device_id: f4230bc48a2d48b2e8e87cefc43950bf

The YAML for the card:
shortcuts:
  - name: Sleep
    icon: 'mdi:weather-night'
    service: fan.set_preset_mode
    data:
      - preset_mode: sleep

Does the card support this service call?

I'll closed this. Figured out that the existing code already handles the preset_mode service call data.  Just had to set them to the correct modes, 'auto' and 'sleep'.


Fix invalid collection version

'latest' is not a valid version key for galaxy collections and causes dependency resolutions to fail during checks.
Version syntax reference: https://docs.ansible.com/ansible/latest/user_guide/collections_using.html#collections-older-version
Added a valid minimum version. This minimum is required for the ha_cluster role.

lgtm


FINERACT-910: Serving apiDocs as part of the fineract-provider

Description
Configured Spring Boot to serve /static and /public directories from the classpath, and moved apiDocs to /static directory so that it will be served. Removed existing serving of '/apps/**' from cwd as a) that did not seem to be used and b) could be a potential security risk.
Updated pull request checklist template to reflect new location.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[X] Commit message starts with the issue number from https://issues.apache.org/jira/projects/FINERACT/. Ex: FINERACT-646 Pockets API.

[X] Coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions have been followed.

[X] API documentation at https://github.com/apache/fineract/blob/develop/api-docs/apiLive.htm has been updated with details of any API changes.

[X] Integration tests have been created/updated for verifying the changes made.

[X] All Integrations tests are passing with the new commits.

[X] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the list.)

Our guidelines for code reviews is at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide

@ptuomola Great, thanks! Small thing: Would you perhaps like to add a trivial new integration test here, doing GET /apiDocs/ asset 200 instead of 400, just to ensure future non-regression for this? Just a thought.

Sounds good - will do this tomorrow!

Ping.. Whats left here maybe just the integration test otherwise everything looks great.

@awasum @vorburger I've added an integration test - so hopefully this is now good to go? Let me know if any other comments...


Give the item durability

Maybe some durability as a slight nerf to the item. Maybe enough for 20 uses or something not sure :) or maybe less than 20 and ender pearls as a repair item in anvil. no enchanting though

Thank you for your idea! I’ve actually been considering this feature myself and I will do my best to implement it in a future update.

I just came here to suggest this :)  Making durability configurable would be awesome! For our mod pack I'd probably set it to 3 uses.

I just came here to suggest this :) Making durability configurable would be awesome! For our mod pack I'd probably set it to 3 uses.

Yes, I have a plan to make the mod as configurable as possible so players can customize it for themselves.


Can we get update for this plugin which is supporting vite: ^4.0.0

Hi, currently this plugin has peer dependency with "vite": "^2.5.0 || ^3.0.0-0".
But now a day most of the other plugins are supporting vite: '^4.0.0'. due to this we are getting dependency conflicts.
Could you please provide update version of "vite-plugin-vue-layout" which peer dependency with "vite":"^4.0.0"
Thank you.

UP


Logo.svg optimizations?

This is probably silly, and probably out of scope for this repo, but I was copying the logo.svg file from the startup repo to create a test case for importing images in an online fiddle.  I was surprised it's such a big file in order to display essentially a circle and three identical ellipses.
It probably doesn't matter, and it's probably just consuming the official logo and modifying any branding / marketing stuff is a heavy lift for a couple extra bits, but it could be vastly simplified.
Here's the current version (1.6 KB)
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 841.9 595.3">
    <g fill="#61DAFB">
        <path d="M666.3 296.5c0-32.5-40.7-63.3-103.1-82.4 14.4-63.6 8-114.2-20.2-130.4-6.5-3.8-14.1-5.6-22.4-5.6v22.3c4.6 0 8.3.9 11.4 2.6 13.6 7.8 19.5 37.5 14.9 75.7-1.1 9.4-2.9 19.3-5.1 29.4-19.6-4.8-41-8.5-63.5-10.9-13.5-18.5-27.5-35.3-41.6-50 32.6-30.3 63.2-46.9 84-46.9V78c-27.5 0-63.5 19.6-99.9 53.6-36.4-33.8-72.4-53.2-99.9-53.2v22.3c20.7 0 51.4 16.5 84 46.6-14 14.7-28 31.4-41.3 49.9-22.6 2.4-44 6.1-63.6 11-2.3-10-4-19.7-5.2-29-4.7-38.2 1.1-67.9 14.6-75.8 3-1.8 6.9-2.6 11.5-2.6V78.5c-8.4 0-16 1.8-22.6 5.6-28.1 16.2-34.4 66.7-19.9 130.1-62.2 19.2-102.7 49.9-102.7 82.3 0 32.5 40.7 63.3 103.1 82.4-14.4 63.6-8 114.2 20.2 130.4 6.5 3.8 14.1 5.6 22.5 5.6 27.5 0 63.5-19.6 99.9-53.6 36.4 33.8 72.4 53.2 99.9 53.2 8.4 0 16-1.8 22.6-5.6 28.1-16.2 34.4-66.7 19.9-130.1 62-19.1 102.5-49.9 102.5-82.3zm-130.2-66.7c-3.7 12.9-8.3 26.2-13.5 39.5-4.1-8-8.4-16-13.1-24-4.6-8-9.5-15.8-14.4-23.4 14.2 2.1 27.9 4.7 41 7.9zm-45.8 106.5c-7.8 13.5-15.8 26.3-24.1 38.2-14.9 1.3-30 2-45.2 2-15.1 0-30.2-.7-45-1.9-8.3-11.9-16.4-24.6-24.2-38-7.6-13.1-14.5-26.4-20.8-39.8 6.2-13.4 13.2-26.8 20.7-39.9 7.8-13.5 15.8-26.3 24.1-38.2 14.9-1.3 30-2 45.2-2 15.1 0 30.2.7 45 1.9 8.3 11.9 16.4 24.6 24.2 38 7.6 13.1 14.5 26.4 20.8 39.8-6.3 13.4-13.2 26.8-20.7 39.9zm32.3-13c5.4 13.4 10 26.8 13.8 39.8-13.1 3.2-26.9 5.9-41.2 8 4.9-7.7 9.8-15.6 14.4-23.7 4.6-8 8.9-16.1 13-24.1zM421.2 430c-9.3-9.6-18.6-20.3-27.8-32 9 .4 18.2.7 27.5.7 9.4 0 18.7-.2 27.8-.7-9 11.7-18.3 22.4-27.5 32zm-74.4-58.9c-14.2-2.1-27.9-4.7-41-7.9 3.7-12.9 8.3-26.2 13.5-39.5 4.1 8 8.4 16 13.1 24 4.7 8 9.5 15.8 14.4 23.4zM420.7 163c9.3 9.6 18.6 20.3 27.8 32-9-.4-18.2-.7-27.5-.7-9.4 0-18.7.2-27.8.7 9-11.7 18.3-22.4 27.5-32zm-74 58.9c-4.9 7.7-9.8 15.6-14.4 23.7-4.6 8-8.9 16-13 24-5.4-13.4-10-26.8-13.8-39.8 13.1-3.1 26.9-5.8 41.2-7.9zm-90.5 125.2c-35.4-15.1-58.3-34.9-58.3-50.6 0-15.7 22.9-35.6 58.3-50.6 8.6-3.7 18-7 27.7-10.1 5.7 19.6 13.2 40 22.5 60.9-9.2 20.8-16.6 41.1-22.2 60.6-9.9-3.1-19.3-6.5-28-10.2zM310 490c-13.6-7.8-19.5-37.5-14.9-75.7 1.1-9.4 2.9-19.3 5.1-29.4 19.6 4.8 41 8.5 63.5 10.9 13.5 18.5 27.5 35.3 41.6 50-32.6 30.3-63.2 46.9-84 46.9-4.5-.1-8.3-1-11.3-2.7zm237.2-76.2c4.7 38.2-1.1 67.9-14.6 75.8-3 1.8-6.9 2.6-11.5 2.6-20.7 0-51.4-16.5-84-46.6 14-14.7 28-31.4 41.3-49.9 22.6-2.4 44-6.1 63.6-11 2.3 10.1 4.1 19.8 5.2 29.1zm38.5-66.7c-8.6 3.7-18 7-27.7 10.1-5.7-19.6-13.2-40-22.5-60.9 9.2-20.8 16.6-41.1 22.2-60.6 9.9 3.1 19.3 6.5 28.1 10.2 35.4 15.1 58.3 34.9 58.3 50.6-.1 15.7-23 35.6-58.4 50.6zM320.8 78.4z"/>
        <circle cx="420.9" cy="296.5" r="45.7"/>
        <path d="M520.5 78.1z"/>
    </g>
</svg>

And here's a cleaner, more readable, more composable, smaller version (0.6 KB):
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 841.9 595.3">
  <g fill="none" stroke="#61DAFB" stroke-width="23" >
    <ellipse cx="420.9" cy="296.5" rx="235" ry="91" />
    <ellipse cx="420.9" cy="296.5" rx="235" ry="91" transform="rotate(120 420.9 296.5)"/>
    <ellipse cx="420.9" cy="296.5" rx="235" ry="91" transform="rotate(240 420.9 296.5)"/>
  </g>
  <circle cx="420.9" cy="296.5" r="45.7" fill="#61DAFB"/>
</svg>

And here are both images side-by-side:

Even if the goal was to retain pixel perfection by drawing the perimeter of each ellipse, the first one could at least be re-used twice and rotated 120° and 240°

For extra optimization xmlns can be removed too :)

This is certainly interesting @KyleMit. We're just using the official React logo though. They might be interested in these optimizations and then we would update our version as well. I'm going to close this for now as I don't think it's out place to mess with this.


dbs-virtio-devices: fix Balloon::write_config() bugs

Fix two bugs in Balloon::write_config():

offset + data_len might overflow. This causes a panic in debug builds, and wraps around in release builds.
https://github.com/openanolis/dragonball-sandbox/blob/8ed5e3fea96bf16747945d65c2b386542b28e1b7/crates/dbs-virtio-devices/src/balloon.rs#L634
Source (data) and destination (right) slices' sizes might be mismatched in right.copy_from_slice(data), which causes a panic (this is documented). This can happen if data is shorter than the right side of config_slice.split_at_mut(offset):
https://github.com/openanolis/dragonball-sandbox/blob/8ed5e3fea96bf16747945d65c2b386542b28e1b7/crates/dbs-virtio-devices/src/balloon.rs#L638-L640

See also firecracker-microvm/firecracker#3869

Please fix ut/clippy

@00xc Hi, could you please help fix the UT before this week since we are going to migrate all dbs crates to kata containers next week.

Should be good now

@00xc There seems several clippy warnings please help fix it.
Tip: we are using Rust 1.70.

Those warnings popped up on code completely unrelated to this PR. I have fixed them, but that seems like a very unusual request.

@00xc , sorry, after dig into the reason for CI complaining for the code not in your PR, we found out that there is one PR merged without clippy pass. Do you mind fix that in this PR or I could raise a new PR to fix this ?

@00xc Hi, the PR itself looks good to me. I'll handle the clippy warnings.

@00xc Hi, the PR itself looks good to me. I'll handle the clippy warnings.

Thanks!


[Experimental] Flip startTransition and isPending

facebook/react#20976

Is this released anywhere yet? I know it's an unstable API, so things can change whenever they want. But just so folks using this don't run into trouble.

It's already released as latest experimental version. The last version that works with react-router-dom@experimental is<EMAIL_ADDRESS>

There are even more changes unstable_ prefixes got removed

@RichardLindhout  What I know transition is still unstable_  other one gets stable with lastest React but transition not.. Only if this changed in last days...

In the experimental release I'm importing straight from   React.useTransition but I'm using ^0.0.0-experimental-46491dce9 maybe they've changed it back to unstable

Are you using typescript and last Types? I remember i was updating types month ago for this... But maybe I should check correctly again :P  But good to know the import is directly available...

Updated React again. react-test-rendered is not the latest because it fails.

Are you using typescript and last Types? I remember i was updating types month ago for this... But maybe I should check correctly again :P But good to know the import is directly available...

Types were not up to date yet I think. Btw React 18 is now released so hope react-router will update soon :)

Can we bump this to the @alpha releases, now that they are out? That should be a more stable target. Thanks!

Updated and now it warns about not using ReactDOM.createRoot, but when I change it then it fails. react-test-renderer still fails with alpha version so I left it at last experimental version that works.

Did you use React.createRoot().render()? That's the new API (you create a root and then render or hydrate it)

Did you use React.createRoot().render()? That's the new API (you create a root and then render or hydrate it)

Yes, like that:
 act(() => {
-  ReactDOM.render(
+  ReactDOM.createRoot(node).render(
     <Router initialEntries={['/home']}>
       <Routes>
         <Route path="home" element={<Home />} />
         <Route path="about" element={<About />} />
       </Routes>
     </Router>,
-    node,
   );
 };

And I get error:
/home/lis/code/react-router/node_modules/react-dom/cjs/react-dom.development.js:1543
    return doc.body;
               ^

TypeError: Cannot read property 'body' of null
    at getActiveElement (/home/lis/code/react-router/node_modules/react-dom/cjs/react-dom.development.js:1543:16)
    at getActiveElementDeep (/home/lis/code/react-router/node_modules/react-dom/cjs/react-dom.development.js:8017:17)
    at getSelectionInformation (/home/lis/code/react-router/node_modules/react-dom/cjs/react-dom.development.js:8050:21)
    at prepareForCommit (/home/lis/code/react-router/node_modules/react-dom/cjs/react-dom.development.js:10500:26)
    at commitBeforeMutationEffects (/home/lis/code/react-router/node_modules/react-dom/cjs/react-dom.development.js:21737:27)
    at commitRootImpl (/home/lis/code/react-router/node_modules/react-dom/cjs/react-dom.development.js:25273:45)
    at commitRoot (/home/lis/code/react-router/node_modules/react-dom/cjs/react-dom.development.js:25168:5)
    at finishConcurrentRender (/home/lis/code/react-router/node_modules/react-dom/cjs/react-dom.development.js:24511:9)
    at performConcurrentWorkOnRoot (/home/lis/code/react-router/node_modules/react-dom/cjs/react-dom.development.js:24389:5)
    at workLoop (/home/lis/code/react-router/node_modules/react-dom/node_modules/scheduler/cjs/scheduler.development.js:253:34)
    at flushWork (/home/lis/code/react-router/node_modules/react-dom/node_modules/scheduler/cjs/scheduler.development.js:226:14)
    at Immediate.performWorkUntilDeadline (/home/lis/code/react-router/node_modules/react-dom/node_modules/scheduler/cjs/scheduler.development.js:516:21)
    at processImmediate (internal/timers.js:461:21)


[Qt6 pyside6 6.5] TypeError on start

🐛 Bug
Trying to launch napari from command line with pyside6==6.5.0 fails with an error:
Traceback (most recent call last):
  File "/Users/piotrsobolewski/Dev/miniforge3/envs/nap-test/bin/napari", line 8, in <module>
    sys.exit(main())
  File "/Users/piotrsobolewski/Dev/napari/napari/__main__.py", line 566, in main
    _run()
  File "/Users/piotrsobolewski/Dev/napari/napari/__main__.py", line 326, in _run
    viewer = Viewer()
  File "/Users/piotrsobolewski/Dev/napari/napari/viewer.py", line 67, in __init__
    self._window = Window(self, show=show)
  File "/Users/piotrsobolewski/Dev/napari/napari/_qt/qt_main_window.py", line 589, in __init__
    self._qt_viewer.dockLayerList, tabify=False, menu=self.window_menu
  File "/Users/piotrsobolewski/Dev/napari/napari/_qt/qt_viewer.py", line 357, in dockLayerList
    layerListLayout.addWidget(self.layers)
  File "/Users/piotrsobolewski/Dev/napari/napari/_qt/qt_viewer.py", line 335, in layers
    self._layers = QtLayerList(self.viewer.layers)
  File "/Users/piotrsobolewski/Dev/napari/napari/_qt/containers/qt_layer_list.py", line 46, in __init__
    super().__init__(root, parent)
  File "/Users/piotrsobolewski/Dev/napari/napari/_qt/containers/qt_list_view.py", line 43, in __init__
    self.setRoot(root)
  File "/Users/piotrsobolewski/Dev/napari/napari/_qt/containers/_base_item_view.py", line 87, in setRoot
    self.setModel(create_model(root, self))
  File "/Users/piotrsobolewski/Dev/napari/napari/_qt/containers/_factory.py", line 72, in create_model
    return QtLayerListModel(obj, parent=parent)
  File "/Users/piotrsobolewski/Dev/napari/napari/_qt/containers/_base_item_model.py", line 80, in __init__
    super().__init__(parent=parent)
TypeError: object.__init__() takes exactly one argument (the instance to initialize)

To Reproduce
Steps to reproduce the behavior:

make fresh conda env (python 3.10)
pip install pyside6 (will yield 6.5.0
pip install -e . (napari from main)
try to launch using napari

Expected behavior
Should work
Environment
macOS 13.2.1, arm64, python 3.10, napari from main, pyside6 6.5.0 from pip
Edit: update: also occurs with 13.3.1, python 3.11.3, pyside 6.5.1
Additional context
This is also reflected in failing tests, see: https://github.com/napari/napari/pull/5702
Some discussion here:
https://github.com/pyapp-kit/app-model/issues/93
and https://napari.zulipchat.com/#narrow/stream/212875-general/topic/Qt.206.2E5

It looks like it is working with PyQt6, so the problem is only touching PySide6.

It looks like this is a pyside6 6.5 bug
https://bugreports.qt.io/browse/PYSIDE-2294
and it looks like a fix has been merged:
https://codereview.qt-project.org/c/pyside/pyside-setup/+/471544

pyside6 6.5.1 is live on pypi, but alas this issue is still not fixed. I guess need to wait for 6.6.0?

@hmaarrfk as you switch to pyside6 in deepcutlab you may be interested in tracing this Issue.

(not officially involved with deeplabcut but thanks for the ping)
Lets see if we can backport the patch: https://github.com/conda-forge/pyside2-feedstock/pull/191

The patch has already been applied in 6.5.1
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/sources/shiboken6/libshiboken/bindingmanager.cpp?h=v6.5.1#n429
but it seems like the issue is not resolved :(

To recreate the PySide6 issue
from PySide6.QtWidgets import QApplication, QMainWindow, QLabel
from typing import Generic, TypeVar

ItemType = TypeVar("ItemType")

class MainWindow(QMainWindow, Generic[ItemType]):
    def __init__(self):
        QMainWindow.__init__(self, parent=None)
        self.resize(400, 300)
        self.lbl = QLabel(self)
        self.lbl.setText("XXX")

app = QApplication([])
window = MainWindow()
window.show()
app.exec()

now i need to figure out their issue reporting system.

I think this pyside issue seems relevant here:
https://bugreports.qt.io/browse/PYSIDE-2304

Maybe, Issue 2354 has been getting good attention. The developers translated my example and adapted it for their internal validation and reuploaded it. so i'm pretty confident that there will be some improvement.

Small update:
Newly released: PySide6 Version: <IP_ADDRESS>
doesn't address this.

I happen to notice that in this superqt pr:
pyapp-kit/superqt@a8e7d0f (#154)
@dalthviz swapped the class inheritance order to fix pyside6 6.5.0 behavior.
Daniel, perhaps you can chime in here regarding the possible fix above?

Thanks @dalthviz
I think maybe we should take the same approach in napari, so we can test on pyside >6.5

Hi all 👋 - thanks for your efforts here. It's currently a big blocker for us at deeplabcut, so if our dev team can allocate time/efforts please let us know and cc @jeylau ❤

class _BaseEventedItemModel(Generic[ItemType], QAbstractItemModel):

Would swapping the order of the subclasses be acceptable for napari? The presumption is that it would be accompanied with a comment as to why this is important for PySide6.

@hmaarrfk Did you test that this works? The multiple inheritance with QObject is not trivial.

It seems really promising, but if the approach is a non-starter, then I don't think it makes sense for myself, or @MMathisLab or @jeylau to spend the time to validate futher than this screenshot

Dependencies installed using conda-forge and screenshot taken on Ubuntu 22.04 on X11.
Napari started with the command
QT_API=PySide6 napari

Right now, I don't see any problem with this approach. Maybe @brisvag knows something more about any problem.
(I will be less available in the following week so any review PR may be delayed)

I have a branch with the swap of position and it seems to work fine.
However, we hit a different issue: https://github.com/napari/napari/issues/5657
I will make a PR, but I expect that tests will fail.

Here's the branch: https://github.com/napari/napari/pull/6062
Tests pass prior to bumping CI to pyside6 <IP_ADDRESS>, so I don't think it broke anything.
napari runs normally for me locally, but even locally the viewer tests crash as noted in
https://github.com/napari/napari/issues/5657

Ok building <IP_ADDRESS> https://github.com/conda-forge/pyside2-feedstock/pull/195 to help with testing.

Just as an update, pyside6 6.5.2 was released and this issue remains.
The fix in https://github.com/napari/napari/pull/6062 still works, but alas so do the test failures from https://github.com/napari/napari/issues/5657

Hi there, just in case, checked this with latest pyside6 (6.7.0) and now I'm able to launch napari from latest main ( f9773dbdb) without doing any changes :tada: !

napari info:

napari: 0.5.0a2.dev626+ge0c5c220
Platform: Windows-10-10.0.19045-SP0
Python: 3.10.9 | packaged by conda-forge | (main, Jan 11 2023, 15:15:40) [MSC v.1916 64 bit (AMD64)]
Qt: 6.7.0
PySide6:
NumPy: 1.25.2
SciPy: 1.9.3
Dask: 2023.10.1
VisPy: 0.14.1
magicgui: 0.7.3
superqt: 0.5.0
in-n-out: 0.2.0
app-model: 0.2.2
npe2: 0.7.3

OpenGL:
- GL version: 4.5.0 - Build <IP_ADDRESS>44
- MAX_TEXTURE_SIZE: 16384
- GL_MAX_3D_TEXTURE_SIZE: 2048

Screens:
- screen 1: resolution 1366x768, scale 1.0
- screen 2: resolution 1920x1080, scale 1.0

Optional:
- numba: 0.58.1
- triangle not installed

Settings path:
- C:\Users\dalth\AppData\Local\napari\napari-dev_4454fdbf170edefe23827a4bf512389a6806af69\settings.yaml

However, I'm still able to reproduce #5657 Also, I tried adding layers and removing them continuosly and at some point that causes the application to crash :/

Hmmm, progress? 🤣
They mention some known issues and soon-to-come 6.7.1
https://wiki.qt.io/Qt_for_Python_Development_Notes

Odd that there isn't anything printed? segfault?

Yep, a segfault is my guess :+1:

I think there's some odd behaviors with removing layers where they are partially maintained -- like if you watch RAM.
And you're going pretty fast, so maybe this is a corner case that's not horrible in reality? 🤔

Yep, I don't think a user will trigger a crash in that way so easly. It just ocurred to me, while thinking about the operations a test does on teardown, to check what would happen if you try to do a quick layer removal and indeed napari crashed 😅

I think we can consider this specific issue fixed with pyside6 6.7
The seg fault issue has it's own issue, so I will close this.


Doesn't work on distros with Python3 as default python version

Some distros (Archlinux for example) have Python 3 as default python version. So when install calls pip command, it will install dependencies in python 3 global environment. Also /usr/bin/python points to Python 3 binary.
Best fix would be to create virtualenv for srclib-python and install dependencies there. This would also benefit people with older python 2 as it would not litter global environment with extra packages and it would remove the need for sudo.
Example error:
Running: [/home/maiku/.srclib/sourcegraph.com/sourcegraph/srclib-python/.bin/srclib-python scan --repo github.com/MaikuMori/sourcegraph-atom --subdir .]
  --> with input {}
  File "/usr/bin/pydep-run.py", line 54
    print json.dumps(setup_infos)
             ^
SyntaxError: invalid syntax
EOF

Yeah, this is a good idea. Currently, we've only tested with Python 2.7. We're currently bottlenecked on dev resources, though, so it might take us awhile to get to this, unfortunately.


Add support for Spring Boot applications with classifier

Add support for Spring Boot applications with a classifier and Spring Boot WAR.

@anjumfatima90 Can this issue be closed since the PR was merged?


compute_ring_position - invalid literal error

replicates https://github.com/graphite-project/carbon/pull/679

Codecov Report

Merging #2014 into master will decrease coverage by 0.01%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master    #2014      +/-   ##
==========================================
- Coverage   69.41%   69.39%   -0.02%
==========================================
  Files          71       71
  Lines        6971     6973       +2
  Branches     1361     1362       +1
==========================================
  Hits         4839     4839
- Misses       1888     1889       +1
- Partials      244      245       +1

Impacted Files
Coverage Δ

webapp/graphite/render/hashing.py
94.31% <33.33%> (-2.2%)
:arrow_down:

Continue to review full report at Codecov.

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


Borrow Rates: Extra Rewards APY

Not sure if this is done already. cc @kcole16 to add context on this.


Improved routing info on regex constraints, plus more

Also fixed some broken/inaccurate links, typos, etc.
cc @Rick-Anderson @rynowak @danroth27

Hi @Eilon, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

@Eilon  thanks for the fantastic updates


yubico-piv-tool: 2.6.0 -> 2.6.1

https://github.com/Yubico/yubico-piv-tool/compare/yubico-piv-tool-2.6.0...yubico-piv-tool-2.6.1
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 341631 run on x86_64-linux 1

3 packages built:

yubico-piv-tool
yubico-piv-tool.dev
yubico-piv-tool.man

Does it work for you in practice? I get:
$ ./results/yubico-piv-tool/bin/yubico-piv-tool -a list-readers
Failed to connect to yubikey: Invalid object.

(same for any other action)


Add South Korea and Australia

See parent/forked repo: https://github.com/se-panfilov/jsvat/issues/127

Australia will be added soon based on https://abr.business.gov.au/Help/AbnFormat


Best way to validate email, more safe & compliant with RFC 822

Best way to validate email, more safe & compliant with RFC 822 (http://php.net/manual/en/filter.filters.validate.php)

Unfortunately, filter_var isn't perfect and fails for many valid emails.


system monitor process no longer exists

Home Assistant release (hass --version):
0.36.1
Python release (python3 --version):
3.4.3
Component/platform:
sensor:
  - platform: systemmonitor

Description of problem:
When tracking the state of some processes, psutil reads in all processes and then filters them.
This results in processes sometimes being stopped before their process files have been read, resulting in an error (see traceback below).
Expected:
It's ok that some processes have been stopped while updating, handling the error would be nicer though.
Problem-relevant configuration.yaml entries and steps to reproduce:
sensor:
  - platform: systemmonitor
     resources:
       - type: process
          arg: deluged
       - type: process
          arg: deluge-web

Traceback (if applicable):
17-01-27 01:34:54 homeassistant.core: Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/PlexMediaServer/hass/lib/python3.4/site-packages/psutil/_pslinux.py", line 1084, in wrapper
    return fun(self, *args, **kwargs)
  File "/PlexMediaServer/hass/lib/python3.4/site-packages/psutil/_pslinux.py", line 1157, in name
    name = self._parse_stat_file()[0]
  File "/PlexMediaServer/hass/lib/python3.4/site-packages/psutil/_common.py", line 293, in wrapper
    return fun(self)
  File "/PlexMediaServer/hass/lib/python3.4/site-packages/psutil/_pslinux.py", line 1119, in _parse_stat_file
    with open_binary("%s/%s/stat" % (self._procfs_path, self.pid)) as f:
  File "/PlexMediaServer/hass/lib/python3.4/site-packages/psutil/_pslinux.py", line 181, in open_binary
    return open(fname, "rb", **kwargs)
FileNotFoundError: [Errno 2] No such file or directory: '/proc/14214/stat'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.4/asyncio/tasks.py", line 234, in _step
    result = coro.throw(exc)
  File "/PlexMediaServer/hass/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 387, in _update_entity_states
    yield from update_coro
  File "/PlexMediaServer/hass/lib/python3.4/site-packages/homeassistant/helpers/entity.py", line 216, in async_update_ha_state
    yield from self.hass.loop.run_in_executor(None, self.update)
  File "/usr/lib/python3.4/asyncio/futures.py", line 386, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 287, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 275, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/PlexMediaServer/hass/lib/python3.4/site-packages/homeassistant/components/sensor/systemmonitor.py", line 137, in update
    if any(self.argument in l.name() for l in psutil.process_iter()):
  File "/PlexMediaServer/hass/lib/python3.4/site-packages/homeassistant/components/sensor/systemmonitor.py", line 137, in <genexpr>
    if any(self.argument in l.name() for l in psutil.process_iter()):
  File "/PlexMediaServer/hass/lib/python3.4/site-packages/psutil/__init__.py", line 634, in name
    name = self._proc.name()
  File "/PlexMediaServer/hass/lib/python3.4/site-packages/psutil/_pslinux.py", line 1090, in wrapper
    raise NoSuchProcess(self.pid, self._name)
psutil.NoSuchProcess: psutil.NoSuchProcess process no longer exists (pid=14214)

Additional info:
I'm not sure if it's helpful, but I use it to track 4 different processes, perhaps this causes the filtering to be slow.

Well, I was about to mention it didn't happen anymore, but it still this, just gotten one these morning:
17-04-02 11:49:49 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.system_monitor_process_plexpy fails
Traceback (most recent call last):
  File "/home/hass/.homeassistant/deps/psutil/_pslinux.py", line 1314, in wrapper
    return fun(self, *args, **kwargs)
  File "/home/hass/.homeassistant/deps/psutil/_pslinux.py", line 1387, in name
    name = self._parse_stat_file()[0]
  File "/home/hass/.homeassistant/deps/psutil/_common.py", line 313, in wrapper
    return fun(self)
  File "/home/hass/.homeassistant/deps/psutil/_pslinux.py", line 1349, in _parse_stat_file
    with open_binary("%s/%s/stat" % (self._procfs_path, self.pid)) as f:
  File "/home/hass/.homeassistant/deps/psutil/_pslinux.py", line 190, in open_binary
    return open(fname, "rb", **kwargs)
FileNotFoundError: [Errno 2] No such file or directory: '/proc/16942/stat'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/PlexMediaServer/hass/lib/python3.4/site-packages/homeassistant/helpers/entity.py", line 225, in async_update_ha_state
    None, self.update)
  File "/usr/lib/python3.4/asyncio/futures.py", line 386, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 287, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 275, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/PlexMediaServer/hass/lib/python3.4/site-packages/homeassistant/components/sensor/systemmonitor.py", line 141, in update
    if any(self.argument in l.name() for l in psutil.process_iter()):
  File "/PlexMediaServer/hass/lib/python3.4/site-packages/homeassistant/components/sensor/systemmonitor.py", line 141, in <genexpr>
    if any(self.argument in l.name() for l in psutil.process_iter()):
  File "/home/hass/.homeassistant/deps/psutil/__init__.py", line 641, in name
    name = self._proc.name()
  File "/home/hass/.homeassistant/deps/psutil/_pslinux.py", line 1320, in wrapper
    raise NoSuchProcess(self.pid, self._name)
psutil.NoSuchProcess: psutil.NoSuchProcess process no longer exists (pid=16942, name='sshd')


Change the way we reference folders and messages

Right now we reference folders by name and messages by UID. Those are both identifiers that should be private to the RemoteStore and sync implementations. Everywhere else I want us to eventually use the local (database) ID to reference a folder or message.
Places that need to be changed (feel free to edit):

[ ] UI code (ideally, the relevant code would be strictly separated from the UI; but that's not how it is right now)
[ ] MessageReference
[x] LocalSearch
[ ] MessagingController
[ ] Notification code
[x] Home screen widget configuration
[x] Special folders configuration (Account.get*Folder())

Using the folder name as the ID is also bad internally in the store because it makes implementing namespaces and subfolders and EWS impossible

Folders should now only be referenced by the database ID. Messages are sometimes still referenced by server ID (UID).


Enable the rules I want

Is there any way to only enable the rules I want?
For example, I only want my custom rules + bold, link and nothing else.

Yes! The only rules simple-markdown will use are the rules you pass to parserFor and outputFor, so if you only wanted your custom rules + bold, you could copy the bold (strong) rule to your custom rules object and pass that.
You'll probably also want the text rule, as it's the base rule for text that doesn't match any other rules. If you don't use the provided text rule, you'll need to create your own rule that has the highest order and matches if no others do.
You also may want the paragraph rule if you want the paragraph rule if you want to parse input with newlines.
    const SimpleMarkdown = require('simple-markdown');

    let order = 0;  // order the below rules as declared below rather than by the original defaultRules order:

    let rules = {
        // OPTIONAL: copy the paragraph rule with a new `order`
        paragraph: Object.assign({}, SimpleMarkdown.defaultRules.paragraph, {
            order: order++,
        }),

        myCustomRule1: {
            order: order++,
            match: ... ,
            html: ... ,  // or react: for react output.
        },

        // copy the bold/strong rule with a new `order`
        strong: Object.assign({}, SimpleMarkdown.defaultRules.strong, {
            order: order++,
        }),

        // copy the text rule with a new `order`
        text: Object.assign({}, SimpleMarkdown.defaultRules.text, {
            order: order++,
        }),
    };

    let parse = SimpleMarkdown.parserFor(rules);
    let output = SimpleMarkdown.outputFor(rules, 'html');
    // alternatively, if using react:
    // let output = SimpleMarkdown.outputFor(rules, 'react');

    let markdownToHtml = function(source, state) {
        // if you don't have a paragraph rule, you probably want to default `state.inline` to true, to
        // indicate to the bold rule that it is parsing inline text:
        if (rules.paragraph == null) state.inline = true;

        let parsedContentTree = parse(source, state);
        return output(parsedContentTree, state);
    };

ah, I see, thank you!


[CKAN] Use scheming plugin

What
Now that https://github.com/Marvell-Consulting/ckanext-extrafields/pull/1 has landed,
extrafields is essentially a shell we can use to commit schema information
ready for use by the scheming plugin.
Here we're adding the scheming plugin and then pointing the
ckan config-tool to set the dataset reference to
ckanext-extrafields/ckanext/extrafields/ckan_dataset.yaml
Why?
The ckan scheming plugin provides an
easily configurable way of mofifying CKAN schemas, and making
representations of those schemas available in CKAN forms. Unless we come
up against some very custom fields, this is a good way to get going with
most of the basic needs for the registry form fields and data structure.

Schema file and its corresponding output in CKAN's dataset editing UI

🥳


Improve go report rating

So far it's B - Not Bad!
https://goreportcard.com/report/github.com/oracle/speedle
We need some effort to get better rating.

it's A now.


Design Events Implementation

Design the Azure equivalent to the AWS Lambda support
http://capitalone.github.io/cloud-custodian/docs/policy/lambda.html
It has been proposed that this could be done with
Activity Logs -> Event Hub -> Azure Function
or potentially
Azure Monitor Alerts -> Azure Function (However it is unclear if Azure Monitor Action groups have a reliable and secure way to call a function yet)
This issue should track the proposed design and agreement, and then we'll file issues to track implementation tasks.

We'll also need a variant of mu for cloud functions. I think we'll need to move policy execution modes to using a registry as well, and update schema for that.
On the overall subscription, the ideal scenario minimizes both the invocations of functions to just the events of interest, and secondarily that we not even process events not of interest.
Given that, the issue i think with activity logs -> event hubs -> functions is that we have to replay the entire volume of activity logs to event hubs, it was unclear if we could filter the activity log stream till we got to the hub -> function subscription. If there is then that would be ideal.
Azure monitor alerts seem to handle that filtering within their definition but as you note its unclear if there is a direct invocation mechanism there for function invocation.
Outside of feature dev by the underlying product teams, ie. based on what we have now, the path forward is still activity log -> hub - function.
I'd suggest we start with just provisioning the cloud function as a minimal work stream thats common to all approaches, and can then re-evaluate as there is product evolution.

Azure Functions support of Python appears to be moving in the direction of using containers with a python virtualenv. I am capturing some notes on items that will need to be investigated.

[ ] Python Runtime Dependencies: Python virtual env needs to be compatible with the custodian application dependencies and the azure functions runtime dependencies. In particular, the large Azure python SDK.

[ ] Identity + Auth: We need to provide environment variables to the Azure function with the credentials of the service principal. It would be even better if we could use MSI for the identity of the function app. (may need to add explicit support for this in custodian)

[ ] Packaging and Uploading: Wrap or leverage existing mu.py to create packages. Either the custom policy needs to be built into a new container image or it needs to be uploaded via Kudu to the function app.

[ ] Caching Azure Dependencies between multiple lambdas because of large Azure function dependencies. (This may not be an issue if we are leveraging containers and we have a base image with all of the dependencies)

Closing this abstract level work item - we have more tactical work items in place or coming for remaining work.


Lots of additions :-)

This PR adds lots of stuff :star_struck: :sunglasses:
I have basically added all functionally previously supplied by my Kotlin library, now as Python:

access the device's log
read/change the device's name
enable/disable cloud remote
configure NTP server
configure custom IP setup (disabling DHCP)
set IP setup back to DHCP
set night mode settings, i.e. LED brightness
set LED theme (individually for each side)
identify air-Q device (by blinking its LEDs)
manually restart air-Q device
gracefully shutdown air-Q device

I also added tests for all the above (where applicable, e.g. doesn't make sense to shut the air-Q down while testing :wink:).
Furthermore, I

extended the README to describe the steps for a Python noob to get everything running.
added a fix, so it works with Python 3.9

Note, I am no Python expert. While researching how to write an async setter, I got the answer: Don't! That's why I put explicit setters and getters into play, rather than following the property schema.
See https://stackoverflow.com/a/36666220/2992323 and https://stackoverflow.com/a/54987177/2992323.

This PR just adds stuff, so it should not break anything.
Please have a look, if you like the direction this is going.
My plan is, so time permits, to have a look into Home Assistant and improve the integration as well. But I need to see how I can setup a non-productive HA first.
I would very much see an option to change the LED intensity by Home Assistant automation. air-Q's concept of "NightMode" is a little interfering in this use-case, but I will see, what I can do. I assume the solution is to keep the night mode disabled and just change the BrightnessDay value. That's how I configure my devices at the moment.
This PR should prepare everything needed to improve the HA integration. (The blink() function also can be used to provide the usual "Identify" functionality most integrations offer, air-Q's one still is missing)

Thanks for the contributions @theHacker, I'll go through them in the upcoming days.

I updated the PR. That should address all your feedback :)

Thanks again @theHacker, and sorry for my late reply. I see a few requested changes still pending, or am I missing smth?

I see a few requested changes still pending, or am I missing smth?

The remaining points were waiting on your reply about the IP adresses. They have been resolved now.
All done.

When merging, please remember to use "Rebase" (not "Squash"!).
I put a lot of effort into keeping a clean VCS history :-)


Improvements to README for newcomers.

Describe the bug
I think some items could be improved in the README.md, to make it clearer for folks new to StepZen:

define what the StepZen endpoint will be given the environment variables
some more information on configuration sets. Unclear what I would need to do if needed to have my own database password etc.

Took a look-- one thing that could be added is a link to docs to explain configurationsets here: STEPZEN_CONFIGURATION_SETS is a list of StepZen configurationsets to apply to your schema definitions. This is specified as a comma separated string, and defaults to...
https://my.stepzen.com/docs/build-a-graphql-endpoint/general#exploring-the-configuration

Assigning to @remotesynth for advice.
After that please assign back to @sridhraj for action. Thanks!

@sridhraj @remotesynth The README in question is this right?
https://github.com/steprz/netlify-plugin-stepzen#readme

@sridhraj @remotesynth The README in question is this right?
https://github.com/steprz/netlify-plugin-stepzen#readme

Yes.

Can you bundle this fix @sridhraj and @remotesynth
I just spotted that we have the wrong email alias on the plugin page
https://app.netlify.com/teams/stepr-hw/plugins?search=stepzen
<EMAIL_ADDRESS>is the internal alias
should be<EMAIL_ADDRESS>

I made some tweaks. Hopefully this version is clearer. Leaving this open for feedback.

@sridhraj next step here??

The documentation is updated and correct.

This issue is now closed.


RSwift Not working on custom strings added in Localizable Strings file

I have a login and Keyboard Toolbar with done button.
The strings that are associated directly with storyboard works fine on change language. But not the programmatically.
I have added in Localizable String file (Dutch)
/* Keyboard Done Title */
"DONE.text" = "Klaar";
/* CANCEL */
"CANCEL.text" = "Annuleer";
/* OK */
"OK.text" = "Oke";
/* Class = "UIButton"; normalTitle = "Inloggen"; ObjectID = "zcB-rQ-yoP"; */
"zcB-rQ-yoP.normalTitle" = "Inloggen";
/* INVALID EMAIL ALERT MESSAGE */
"EAM.text" = "Ongeldig e-mailadres";
But on launch i got below.
DONE BUTTON

##Alert

// PROJECT SETTINGS

Code
R.string.login.okText()
R.string.login.eamText()
R.string.login.doneText()
R.string.login.zcBRQYoPNormalTitle()
Let me know what's wrong in above ??
@mac-cain13 @tomlokhorst  : Need you help :|

Does this work if you don't use R.swift, but instead use NSLocalizedString natively?

@tomlokhorst : I tried like this

let ss = NSLocalizedString("DONE.text", comment: "XXXXX")
print(ss)

Output: DONE.text
Anything i am missing ??

If your strings are in a different file, you need to specify that file name in the call to NSLocalizedString.
For example, if your strings are in login.strings, use: NSLocalizedString("MyString", tableName: "login", comment: "XXX")
However in general; if it also doesn't work without R.swift, it's not an issue with R.swift itself, but something unrelated.

I have almost the same problems. But for works when I use NSLocalizedString, but when I build  project, after I don't see new strings, colors and images. It's like generated old version of rswift..What I'm missing?


fixes bug 1275907 - uploaded videos should be processing on publish

Coverage remained the same at 84.836% when pulling 62811b415aa6443292c78a6bfa52fc7f4609b8cc on peterbe:bug-1275907-uploaded-videos-should-be-processing-on-publish into 54be83522e56ac680424435ad2131b7dfd4791fb on mozilla:master.


Create CardTable component for home page

Currently <q-table> are being repeated on home page
I can create CardTable component for home page and pass only require props to make the code more DRY.
This is a self reminder and doesn't need to be resolved before #1 is merged

No longer required since the home page is using list


fix creating items with the big padding, add tests

Signed-off-by: Viacheslav Yartsev<EMAIL_ADDRESS>

Approved


Metrics server doesn't seem to be installing in AKS 1.12.6

Hey guys, I recreated my AKS cluster, that as far as I can say was working fine with HPA.
Now HPA does not work as the metrics-server doesn't seem to be running.
Some outputs:
$az aks show --resource-group RG-XXX --name AKS-XXX --query kubernetesVersion
"1.12.6"

$ kubectl get pods -n kube-system
NAME                                                              READY   STATUS    RESTARTS   AGE
addon-http-application-routing-default-http-backend-8cdc9d22zp8   1/1     Running   0          18h
addon-http-application-routing-external-dns-7669cc8557-ptmqd      1/1     Running   0          18h
addon-http-application-routing-nginx-ingress-controller-8fpm2q2   1/1     Running   0          18h
coredns-754f947b4-7bplw                                           1/1     Running   0          18h
coredns-754f947b4-m8c52                                           1/1     Running   0          18h
coredns-autoscaler-6fcdb7d64-twqnz                                1/1     Running   0          18h
heapster-5fb7488d97-p7qtg                                         2/2     Running   0          18h
kube-proxy-dn669                                                  1/1     Running   0          18h
kube-svc-redirect-xb4l4                                           2/2     Running   0          18h
kubernetes-dashboard-847bb4ddc6-mwmmt                             1/1     Running   0          18h
omsagent-8qrsd                                                    1/1     Running   0          18h
omsagent-rs-7769dc79f4-rpm4b                                      1/1     Running   0          18h
tiller-deploy-8f884fd6f-jhh6n                                     1/1     Running   0          18h
tunnelfront-5b44f75b58-m2bb9                                      1/1     Running   0          18h

$ kubectl get hpa
NAME                           REFERENCE                                 TARGETS         MINPODS   MAXPODS   REPLICAS   AGE
a                              Deployment/a                              <unknown>/50%   1         4         1          18h
b                              Deployment/b                              <unknown>/35%   5         10        5          18h
c                              Deployment/c                              <unknown>/50%   1         4         1          18h

$kubectl describe hpa a
Name:                                                  a
Namespace:                                             default
Labels:                                                <none>
Annotations:                                           <none>
CreationTimestamp:                                     Wed, 27 Mar 2019 04:24:58 +0000
Reference:                                             Deployment/a
Metrics:                                               ( current / target )
  resource cpu on pods  (as a percentage of request):  <unknown> / 50%
Min replicas:                                          1
Max replicas:                                          4
Deployment pods:                                       1 current / 0 desired
Conditions:
  Type           Status  Reason                   Message
  ----           ------  ------                   -------
  AbleToScale    True    SucceededGetScale        the HPA controller was able to get the target's current scale
  ScalingActive  False   FailedGetResourceMetric  the HPA was unable to compute the replica count: unable to get metrics for resource cpu: unable to fetch metrics from resource metrics API: the server could not find the requested resource (get pods.metrics.k8s.io)
Events:
  Type     Reason                   Age                     From                       Message
  ----     ------                   ----                    ----                       -------
  Warning  FailedGetResourceMetric  2m18s (x4496 over 18h)  horizontal-pod-autoscaler  unable to get metrics for resource cpu: unable to fetch metrics from resource metrics API: the server could not find the requested resource (get pods.metrics.k8s.io)

Shouldn't the metrics server come with any deployments of AKS on version above 1.10?
Can this be related to me deploying in a different location? I had it deployed on Southeast Asia before and now I have it in Australia Southeast
Is it possible for me to change my scripts to also deploy metrics-server in case I need to do it manually? Would it affect AKS whenever it goes back to deploying metrics-server by itself (if I run an ARM script updating AKS or just destroy and recreate it again)?

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

ID: 6ab10c96-1f2f-e48f-a084-b1715156e33f
Version Independent ID: a113b8e9-259a-2a65-2e54-a2661c78ddb5
Content: Kubernetes on Azure tutorial  - Scale Application
Content Source: articles/aks/tutorial-kubernetes-scale.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

Thanks for the feedback! We are currently investigating and will update you shortly.

@Merurino I ran through some tests but I am unable to repro the issue you are having. Which leads me to believe there is something specific in your environment that is causing the error.
Do you have the ability to open a technical support ticket to have this looked into further? If not, you can email me at<EMAIL_ADDRESS>and provide me with your SubscriptionID and link to this issue. I can enable your subscription for a free support request.
I will close this for now as I found no issues with the documentation but will be on the lookout for that email from you if needed.

Thanks @MicahMcKittrick-MSFT , I will open a support ticket.


Add Support for Rich Text Formatting

Users will want some way to include formatted text-links, bolded text, italicized text, etc. We should extend the application with some standard formatting system like markdown or HTML.

just flagging this as something we'll want consider a generic solution that can be reused / incorporated by other apps with chat.
gut says a json schema is going to be flexible for validating on multiple clients, parsing, extending. also with node level schema validation, you can enforce other apps tapping into a chat thread use the same rules and so can be viewed by other clients.
been going iteratively deeper on slate's schema for note based content, https://docs.slatejs.org/slate-core/schema


Can you add a counter?

Can you add a counter on the key which has been double clicked? We want to know how serious it is, so that we can repair it in the genius bar.
Thank you.

you are talking about counting for individual keys right? Currently we have a counter but it is aggregating counts of all keys.

Yes. That was exactly what I mean.

Thanks again for creating this code, I can't tell you how much I appreciate it. Is it possible to view the aggregate counter for which keys are double clicking and how often?

I think that having a counter for the individual keys would be great as well.

Will work on it :-)

+1

I also think it'd be great to have individual key double press logs available! Would help fine tune the delays for different keys.

It will be in the next release :D


soco.discover() returning nothing at all

Hello. I am getting this issue on my Raspberry Pi 4. The function works on my Windows PC, but not on my Raspberry Pi unfortunately.
It's running Raspbian. I suspect it might have something to do with ports, because I closed most? Maybe not at all.
I'm just really lost and need this function. Not sure which extra info to provide, so just ask me questions.
Thanks and have a great day.

First, make sure you're using SoCo v0.21.
If that's already the case, try: soco.discovery.scan_network()

First, make sure you're using SoCo v0.21.
If that's already the case, try: soco.discovery.scan_network()

First, make sure you're using SoCo v0.21.
If that's already the case, try: soco.discovery.scan_network()
Edit: note that the 'normal' discover() function requires incoming UDP/1900 to be open, to receive multicast discovery responses.

Thank you soco.discovery.scan_network() works. For some reason it didn't work in the python interpreter (python, import soco, soco.discovery.scan_network() - AttributeError: module 'soco.discovery' has no attribute 'scan_network' )

First, make sure you're using SoCo v0.21.
If that's already the case, try: soco.discovery.scan_network()
Edit: note that the 'normal' discover() function requires incoming UDP/1900 to be open, to receive multicast discovery responses.

Thank you soco.discovery.scan_network() works. For some reason it didn't work in the python interpreter (python, import soco, soco.discovery.scan_network() - AttributeError: module 'soco.discovery' has no attribute 'scan_network' )

from soco.discovery import scan_network.

from soco.discovery import scan_network.

Thanks. It does seem to be very inconsistent though. I often get None and then in periods I actually receive the set...

Thanks. It does seem to be very inconsistent though. I often get None and then in periods I actually receive the set...

Generally, it's better if you can use discover(), but some networks have problems with multicast forwarding, and some systems have the required incoming port blocked. Both of these will prevent 'normal' discovery from working.
scan_network probes the network for Sonos devices. You can improve its chances of success by increasing the timeout for each IP probe. There's full documentation at: http://docs.python-soco.com/en/v0.21.1/api/soco.discovery.html#soco.discovery.scan_network.

Generally, it's better if you can use discover(), but some networks have problems with multicast forwarding, and some systems have the required incoming port blocked. Both of these will prevent 'normal' discovery from working.
scan_network probes the network for Sonos devices. You can improve its chances of success by increasing the timeout for each IP probe. There's full documentation at: http://docs.python-soco.com/en/v0.21.1/api/soco.discovery.html#soco.discovery.scan_network.


zerotierone: 1.8.2 -> 1.8.3

Motivation for this change
https://github.com/zerotier/ZeroTierOne/releases/tag/1.8.3
https://github.com/zerotier/ZeroTierOne/blob/1.8.3/RELEASE-NOTES.md
Things done

Built on platform(s)

[X] x86_64-linux
[X] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 146293 run on x86_64-linux 1

1 package built:

zerotierone


more platform dependent conditional flags

fixes #11

Thanks!
@alexcrichton am I doing anything dumb with my iOS travis setup? I would have thought that it should have found this link error.

@sfackler I'm actually not sure, the iOS stuff I did in liblibc was the first thing that worked, and I never bothered to figure out if it was actually testing what I wanted it to test.


Randomizing Bridge (Many-to-many relationship) Tables while retaining Integrity to Parent

Hi!,
I use AliceBundle to generate random data. My database is moderately complex with many-to-many relationships where the entities themselves are a child of a common parent (one-to-many) entity.
Example:
Teams can have many Students
Students can be apart of many Teams
This is managed by a separate TeamStudent Entity that includes other information about the relationship

In this environment, both Team and Student entities are many-to-one child of a Campaign entity.
Example:
Campaigns can have many Students
Campaigns can have many Teams
This is managed by a traditional one-to-many entity relationship

Current Fixtures:
AppBundle\Entity\Student:
    student{1..1000}:
        name: <firstName()> <lastName()>
        campaign: '@campaign*'

AppBundle\Entity\Team:
    team{1..10}:
        name: 'Team <current()>'
        url: 'team<current()>'
        campaign: '@campaign*'
        user: '@user<current()>'
        teamType: '@teamType2'
        fundingGoal: <randomFloat(2, 50, 200)>

AppBundle\Entity\TeamStudent:
    br_team_student{1..100}:
        student: '@student*'
        team: '@team*'
        name: <firstName()> <lastName()>

This will randomize the elements without ensuring that the student and team are apart of the same campaign. Is there a way to maintain referencial integrity with the parent Campaign entity?
Thanks!

I don't think there's an easy out-of-the-box way to do it. Indeed your assignment of campaign depends of rules requiring all the other relationships to be completed. So the way to go IMO would be to decorate the loader to set the campaign after all the entities are loaded. Note that you can still assign them randomly by calling faker directly

I apologize for my ignorance of Alice, Faker, and your AliceBundle, but how do I create a custom loader (which is what I assume is what you mean by decorate the loader)?

which is what I assume is what you mean by decorate the loader

Right assumption :) In symfony it can easily bone by declaring your own service with the same service ID.

I have so many questions on declaring my own service, but thats on me research. I'll be happy to share if I am able to come to a good resolution on this.
Meanwhile, another possible way to solve the problem would be to design the fixtures to load one campaign at a time with its Teams, Students, and TeamStudents. I know I can use the "--append" option to repeat the process from a CI/CD perspective, but is there a hautelook:fixtures:load option and to only run a specific set of fixtures? the "--fixtures" option doesn't exist.

I have so many questions on declaring my own service

Feel free to ask for help on symfony-dev: Slack invite

is there a hautelook:fixtures:load option and to only run a specific set of fixtures? the "--fixtures" option doesn't exist.

That could be a new feature indeed :)

Closing as the question has been answered. Feel free to ping me on slack for those kind of questions :)


question about the network architecture for set transformer

Hi, @yoonholee ,
Thanks a lot for adding the code for the point cloud part.  After looking into the network part, it shows that SAB modules are not included in decoder part? Is that the reason of increased time complexity when appending SAB modules to enhance the expressiveness of representations ? It seems that the classification accuracy will be increased by doing so. Had you performed the related experiments?
THX!

I tried architectures made of various combinations of [SAB, ISAB, PMA, fc, dropout], including using SAB in the decoder, for this task when we were writing the paper. Using no SAB in the decoder worked best in my experiments.
My best guess for why this simple decoder worked best here is that classification is such a simple task that we don't need to model many high-order interactions to achieve good accuracy. Set Transformers seem to be most useful in complex (in terms of interactions among items) tasks such as clustering.

@yoonholee ,
Thanks for your reply. One further question, had you also tried increasing the numbers of ISAB layers (e.g. more than two), as the original Transformer model uses 6 layers of MAB in its encoder part? Any different performances or memory limitations?
THX!

Yes, we shared building blocks but tuned the architectures to suit each specific task. Using two worked best in point cloud classification, but we used 3 ISABs in clustering and 4 SABs in the anomaly detection experiment (see appendix).
Memory was never an issue when using ISABs (see fig 1 of the appendix); the problem was mainly that larger architectures take longer to optimize and/or overfitted. I personally think that if this is somehow solved, stacking more attention-based blocks should yield better results across the board.


fix cmake errors on Check on fresh build

from F54280 on r/C_programming - the default build scripts on my OSX machine gives:
-- Found PkgConfig: /usr/local/bin/pkg-config (found version "0.29.2")
CMake Error at cmake/FindCheck.cmake:43 (MESSAGE):
Could NOT find CHECK
Call Stack (most recent call first):
CMakeLists.txt:33 (find_package)

Only do check find when the code is tested, not during build.


Allow users to be given access to manage just a specific election

To enable people to remotely manage specific elections - e.g. by-elections.
Election Managers

[ ] Can be appointed to manage individual elections (e.g. local government elections, by-elections)
[ ] For elections they have access to they will have rights to:

[ ] Add/upload polling booths
[ ] Approve pending booths
[ ] Edit polling booths

[ ] They will receive emails notices that there are pending stalls
[ ] Investigate whether electoral commissions release polling booth data for these smaller elections.

[ ] It may be necessary to develop a simple GUI to let them map polling places by-hand where there no authoritative list of polling booths.

[ ] Individuals to be managers can be recruited from social media
[ ] Consider what tools/materials they would need to perform this role and promote DS in their local communities.

Manage Users

[ ] Create User
[ ] Edit User
[ ] Delete User
[ ] Set user access level: Super User, Election Manager

AB#131

Closing and merging into https://github.com/keithamoss/demsausage/issues/97


Available spell slots on the UI

With the removal of weapon spells, there are some empty spaces on the UI to fill with other spells, preferably the default spells added (Shove, Dodge or Disengage)

Patch 6 removed the DefaultWeaponAction from the UI, so this is no longer possible to use


Move unwanted print statement to input

Checklist

[ ] Added tests for changed code.
[ ] Updated documentation for changed code.
[ ] I've added a news fragment of my changes with the name,
"{ISSUE_NUM}.{feature|bugfix|doc|removal|misc}""

Related Issue

Description

Moved the "Input mfa code:" within input statement

Reason:
There is no reason for the print statement to be stand-alone, as it will eventually be printed in the console for standard input in python
I'd also prefer pyrh using logger instead of print statements all over, but I'm not sure how you feel changing it. If it is a 👍🏻 , I can create a follow up PR for that as well. It doesn't need to be a static logger, pyrh can use a default logger and still give an option to users to bring their own formatted logger.

Sure, happy to accept contributions to this project. But, fair warning--it's in maintenance mode these days. If you intend to land logic changes, would appreciate it if you could take a look at CI as well so we can merge with confidence.


⚠ Bofrost.de has degraded performance

In 150c437, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 4670 ms

Resolved: Bofrost.de performance has improved in fb96dfe after 8 minutes.


No clear information on how to create shipnotices with items.

Creating Shipnotice requires creating Shipnotice Items, which in turn, requires creating a shipnotice first. This should be made more clear in the API docs.

This is a problem with the documentation:

You can currently create an empty shipnotice. We'll discuss internally and either update the doc, or add the requirement to the API.
When shipnotice_items within a shipnotice, you shouldn't specify a shipnotice_id. It works fine if you don't (same as with order_items). I'll update the doc to reflect this.

Yeah, sorry, I was passing items as a hash, while I should have been passing them as an array. Seems like an oversight on my part. Sorry about that.
I have updated the tests, and the code to reflect this.
However, please note that, if the passed array is not valid (i.e. associated shipnotice_items, and order_items are not valid - e.g. if they are missing quantity field), the shipnotice/order is saved without spitting a validation error. IMO, if the associated child records could not be saved, it should throw an error. But, since, you said you will be working on validations later, I will close this for now.


[Question] Can it show more metric fields, such as SSL's start_time and end_time, it is helpful to quickly understand the status of resources

Question

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

Question

hi This can't be done yet, the monitor list is a common frontend page, there is no special ui page for each monitoring type.


Type Fix for "a existing" to "an existing"

What is the purpose of this change?

Was the change discussed in an issue or in the forum before?

Checklist

[x] I have read the contribution guidelines.
[x] I have added tests for all changes in this PR if appropriate.
[x] I have added documentation for the changes if appropriate.

[x] I'm done, this Pull Request is ready for review :-)

Thanks for that :-)  I took the auto generated files out of the commit - these will be regenerated at the next release.


Unable to save specific block in array of blocks

Update
It's actually the API not being aware of newly created blocks until the server restarts.
Just restarted the development server. Seems that blocks in the API don't get restarted the same way the API UI does. After closing down the server and starting up again entirely it now works as expected.
Don't know if you still want to consider this a bug but it was confusing from a developer experience perspective because everything else restarts smoothly. 😎

Bug Report
Certain blocks are failing to update their content via the admin. Initially, I thought it was down to a definition I created but after copying the QuoteBlock example from here I find they are also not updating.
I will try to experiment later and find some more information but I'm hoping you might have some insight in the mean time.
Expected Behavior
My blocks should save the content I added to them.
Current Behavior
Data returned from the API does not include new values added via the block. Also attached is the request/response that's made to the API.
const ClientListBlock: Block = {
  slug: 'clientList',
  labels: {
    singular: 'Client Listing',
    plural: 'Client Listings'
  },
  fields: [
    {
      type: 'text',
      name: 'test',
      label: 'Test'
    }
  ]
}

export default ClientListBlock

const QuoteBlock: Block = {
  slug: 'Quote', // required
  imageURL: 'https://google.com/path/to/image.jpg',
  imageAltText: 'A nice thumbnail image to show what this block looks like',
  labels: {
    singular: 'Test',
    plural: 'Tests'
  },
  fields: [ // required
    {
      name: 'text',
      label: 'Quote Text',
      type: 'text',
      localized: true,
      required: true,
    },
    {
      name: 'text',
      label: 'Quotee',
      type: 'text',
      localized: true,
    },
  ]
};

Steps to Reproduce

Create page builder schema with the definition bellow
(possibly related but maybe not) add localisation as defined below
Add either of the attached block schemas
Try to create a new block

Detailed Description
Request Screenshots:

Request stack trace:
put @ http://localhost:3000/admin/main.js:25097
(anonymous) @ http://localhost:3000/adminvendors-node_modules_payload_dist_admin_components_forms_Error_index_js-node_modules_payload_-6c3d35.js:834
(anonymous) @ http://localhost:3000/adminvendors-node_modules_payload_dist_admin_components_forms_Error_index_js-node_modules_payload_-6c3d35.js:819
callCallback @ http://localhost:3000/admin/main.js:43269
invokeGuardedCallbackDev @ http://localhost:3000/admin/main.js:43318
invokeGuardedCallback @ http://localhost:3000/admin/main.js:43380
invokeGuardedCallbackAndCatchFirstError @ http://localhost:3000/admin/main.js:43394
executeDispatch @ http://localhost:3000/admin/main.js:47567
processDispatchQueueItemsInOrder @ http://localhost:3000/admin/main.js:47599
processDispatchQueue @ http://localhost:3000/admin/main.js:47612
dispatchEventsForPlugins @ http://localhost:3000/admin/main.js:47623
(anonymous) @ http://localhost:3000/admin/main.js:47832
batchedEventUpdates$1 @ http://localhost:3000/admin/main.js:61715
batchedEventUpdates @ http://localhost:3000/admin/main.js:43069
dispatchEventForPluginEventSystem @ http://localhost:3000/admin/main.js:47831
attemptToDispatchEvent @ http://localhost:3000/admin/main.js:45329
dispatchEvent @ http://localhost:3000/admin/main.js:45248
unstable_runWithPriority @ http://localhost:3000/admin/main.js:80927
runWithPriority$1 @ http://localhost:3000/admin/main.js:50600
discreteUpdates$1 @ http://localhost:3000/admin/main.js:61732
discreteUpdates @ http://localhost:3000/admin/main.js:43080
dispatchDiscreteEvent @ http://localhost:3000/admin/main.js:45213

I'm not sure why you would not have an updated API running.
From create-payload-app, the package.json has a script for PAYLOAD_CONFIG_PATH=src/payload.config.ts nodemon
If you're using yarn dev or npm run dev to run the project, nodemon should see file changes and restart node automatically. Payload should start up and alwayrs have your latest changes.
Do you see in your console, after saving a file that it says [nodemon] restarting due to changes...? That should indicate the API is good to go with those updates.
Are you having to stop and start node each time you make changes? How are you running your project?

That's probably it. I'm not seeing any messages from nodemon on file change only messages from webpack.
I don't think I've changed anything from the defaults.  This might be related to a couple of other frustrations I'm having.
❯ yarn dev
yarn run v1.22.4
$ cross-env PAYLOAD_CONFIG_PATH=src/payload.config.ts nodemon
[nodemon] 2.0.7
[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): *.*
[nodemon] watching extensions: ts
[nodemon] starting `ts-node src/server.ts`
[03:26:44] INFO (payload): Starting Payload...
[03:26:45] INFO (payload): Payload Admin URL: http://localhost:3000/admin
[03:26:45] INFO (payload): Connected to Mongo server successfully!
[03:26:47] INFO (payload): E-mail configured with mock configuration
[03:26:47] INFO (payload): Log into mock email provider at https://ethereal.email
[03:26:47] INFO (payload): Mock email account username<EMAIL_ADDRESS>[03:26:47] INFO (payload): Mock email account password: k26t4NzzNTXCw4ureZ
webpack built f146d48c3cec33fdb48f in 9971ms
webpack building...
webpack built 47e2c8af6d843195c44f in 1206ms

Yeah, that definitly is the issue. Each save you should see:
webpack building...
[nodemon] restarting due to changes...
[nodemon] starting `ts-node src/server.ts`
[14:51:03] INFO (payload): Starting Payload...
[14:51:04] INFO (payload): Payload Admin URL: http://localhost:3000/admin
[14:51:05] INFO (payload): Connected to Mongo server successfully!
[14:51:05] INFO (payload): E-mail configured with mock configuration
[14:51:05] INFO (payload): Log into mock email provider at https://ethereal.email
[14:51:05] INFO (payload): Mock email account username<EMAIL_ADDRESS>[14:51:05] INFO (payload): Mock email account password: RCgFydxecDnfTbcRFw
webpack built 80cff2faf5e3bdd7bfd4 in 9546ms

You're only getting webpack updates and not nodemon and Payload.
I landed on this thread with a few suggestions about nodemon. Might be worth checking out?
https://github.com/remy/nodemon/issues/1630#issuecomment-661858846

If you're running on windows, make sure system32 folder is in the path variables.

Do you have another project that you can test nodemon on your system, seperate from Payload to isolate the issue?

@richardvanbergen what is the filename of your config and / or block config filename? Are you using a .js extension, or a .ts extension?
We can update this within create-payload-app, and you can also update your local config to support it as well by changing your nodemon.json file to watch extensions ts AND js.
Let us know!

Hey guys really sorry but I've looked into it and it's down to the fact that some of the files in a yarn workspace and nodemon wasn't aware of them.
Changing the dev command to cross-env PAYLOAD_CONFIG_PATH=src/payload.config.ts nodemon --watch ../components fixed the issue.

No problem, @richardvanbergen! Thanks so much for sharing the solution!


Albl example

[Current coverage][cc-pull] is 85.13%

Merging [#58][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master        #58   diff @@
==========================================
  Files            19         19
  Lines           565        565
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            481        481
  Misses           84         84
  Partials          0          0

Powered by Codecov. Last updated by [44ef927...22f08fc][cc-compare]
[cc-base-branch]: https://codecov.io/gh/ntucllab/libact/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/ntucllab/libact/compare/44ef92723a5acc67f3219825147ea59e6387a749...22f08fc82c0efe843f15090895b0f21e7bdbb1c6
[cc-pull]: https://codecov.io/gh/ntucllab/libact/pull/58?src=pr


[RESOLVED] Unavailable by ICMP ping

Problem started at 14:55:14 on 2023.01.05
Problem name: Unavailable by ICMP ping
Host: ZO-FG
Severity: High
Operational data: Down (0)
Original problem ID: 4680
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23123&eventid=4680

Problem has been resolved in 1m 0s at 14:56:14 on 2023.01.05
Problem name: Unavailable by ICMP ping
Host: ZO-FG
Severity: High
Original problem ID: 4680


Added the touches functionality

You can toggle it in the Settings app on apple device

Tested with iOS Build 1416

@singhgag Tested with Build 1457 - comments in original Issue

@singhgag Just a couple of comments

@maryharvey @singhgag has addressed all my comments.  Are you ready for this to merge?

Done.


CharSeq maintenance

The tests seem too big ... the changes there are mainly static imports from the SUT and added missing tests to maximize coverage.

Current coverage is 95.67%

Merging #1283 into master will increase coverage by +0.02% as of 85b2f95

@@            master   #1283   diff @@
======================================
  Files           83      83
  Stmts         9592    9579    -13
  Branches      1761    1757     -4
  Methods          0       0
======================================
- Hit           9175    9165    -10
- Partial         99     100     +1
+ Missed         318     314     -4

Review entire Coverage Diff as of 85b2f95

Powered by Codecov. Updated on successful CI builds.

Awesome, thanks. Now you have a new nickname - The Wolf aka The Cleaner

Hope I'll prove that I can create also, not just clean :p

You will!

https://40.media.tumblr.com/25d9b64f997e657fe1ba7995329c4d4e/tumblr_ncnhyxBvcA1qbizb0o1_500.jpg

:laughing:


Don't require RegistrationActions if the feature is disabled

Describe the desired behavior
Users shouldn't need to supply the RegistrationUIActions if they have disabled the registration capabilities
Describe the current behavior
This prop is required even if the registration capabilities are disabled.
Is this request related to a current issue?
This was requested by the Red/Green seed UI team.
Additional Context

This could be more involved than it seems...it would require adding a bunch of conditional logic throughout since functions are no longer guaranteed to exist, plus probably some sort of type unions to only make it required when the other props are true.

Will transfer to JIRA

PXBLUE-2159