Alert on sum of values (avg/sum aggregation)

Hi,
I browsed and read all rule types, but didn't find any that can use a "sum/avg" aggregation result as threshold for alert (like this aggregation: https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-metrics-sum-aggregation.html ).
Are there any similar rules that use this type of aggregation that I can learn from? I guess I'll need to write my own rule.
Is it possible to specify the 'avg/sum/other' in "filter" of the rule? (I suppose not, because it gets passed as '{'filter': {'bool': {'must': [config.filter]}}}' to elasticsearch)
thanks in advance :)

http://elastalert.readthedocs.io/en/latest/ruletypes.html?highlight=avg#metric-aggregation
"This must be one of ‘min’, ‘max’, ‘avg’, ‘sum’, ‘cardinality’, ‘value_count’."

Oh, ok :) . This might help. I actually need the spike and percentage rules, to work on 'numbers' (sum) of a field instead on matched document count. Like if I had a sum of 500 'something' in last hour, followed by 2500 in next hour, the spike rule will alert. And same with percentage.. to compare sum between one field, and sum of other field, of the same hour, and calculate percentage.
Do you think it's possible?

I've been meaning to release this as official code but I had forgotten about it:
# -*- coding: utf-8 -*-
"""
Rule types that count one document multiple times according to a field in the
document. This rule may only be used when the contents of the document may be
discarded (i.e. use_count_query would have sufficed), as it does not
preserve them.
"""
import copy

from elastalert.ruletypes import FrequencyRule
from elastalert.ruletypes import SpikeRule
from elastalert.ruletypes import FlatlineRule
from elastalert.ruletypes import EventWindow
from elastalert.util import lookup_es_key
from elastalert.util import elastalert_logger

def verify_integer_field(document, rule, count_field, allow_zero=False):
    count = lookup_es_key(document, count_field)
    # Attempt to convert strings to ints
    if isinstance(count, basestring):
        try:
            count = int(count)
        except ValueError:
            elastalert_logger.warning(
                'Field %s is a string which could not be converted'
                'into an integer for rule %s' % (count_field, rule['name']))
            return None
    if count is None:
        elastalert_logger.warning(
            'Did not find field %s representing document count in '
            'document for rule %s' % (count_field, rule['name']))
        return None
    if isinstance(count, float):
        count = int(count)
    if not isinstance(count, (int, long)):
        elastalert_logger.warning(
            'Non-integer value of field %s representing document '
            'count in document for rule %s: %s'
            % (count_field, rule['name'], count))
        return None
    if count < 0 or (count == 0 and not allow_zero):
        return None
    return count

class SumOfFieldRuleFactory(type):
    """
    Metaclass that creates a subclass of the class's backing_rule_type.
    backing_rule_type must implement add_count_data.
    """
    # This allows the add_data to use super(...).add_count_data(...) to call
    # the add_count_data method of the appropriate backing RuleType, without
    # having to reimplement all the common logic for each backing_rule_type.

    def __new__(mcs, name, _, dct):

        def add_data(self, data):
            for document in data:
                count = verify_integer_field(
                    document, self.rules, self.rules['count_field'])
                ts = lookup_es_key(document, self.ts_field)
                if count and ts:
                    super(self.__class__, self).add_count_data({ts: count})

        backing_rule_type_cls = dct['backing_rule_type']
        dct['required_options'] = (
            dct['backing_rule_type'].required_options | frozenset(['count_field']))
        dct['add_data'] = add_data
        return type.__new__(mcs, name, (backing_rule_type_cls,), dct)

class SumOfFieldFrequencyRule(object):
    __metaclass__ = SumOfFieldRuleFactory
    backing_rule_type = FrequencyRule

class SumOfFieldSpikeRule(object):
    __metaclass__ = SumOfFieldRuleFactory
    backing_rule_type = SpikeRule

I think this is what I'm looking for. Thank you!
On Aug 16, 2017 9:17 PM, "Quentin Long"<EMAIL_ADDRESS>wrote:
Reopened #1288 https://github.com/Yelp/elastalert/issues/1288.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Yelp/elastalert/issues/1288#event-1208808166, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AI71-OHE9ofgS9X1oEYG3AJ3gsUUvF65ks5sYzJUgaJpZM4O5O9U
.

Hi @Qmando ,
I tried to use it as new rule (http://elastalert.readthedocs.io/en/latest/recipes/adding_rules.html) but it didn't work saying:
Could not import module elastalert_modules.custom_rules.SumOfFieldSpikeRule: No module named ruletypes

So I moved it from separate file into default "ruletypes.py", and added a section to "schema.py" too.
But I'm getting error:
Error loading file /opt/rules/count.yaml: Could not import module SumOfFieldSpikeRule: need more than 1 value to unpack
My rule tries to call the new type directly (it's a regular spike rule but with "count_field"):
import: shared_settings.conf
timestamp_field: orig_timestamp
index: metric_aggs-graylog*
name: Sum spike test
type: SumOfFieldSpikeRule
count_field: count
spike_height: 2
spike_type: "up"
threshold_ref: 1000
query_key: environment
timeframe:
  hours: 2
filter:
- term:
    message: "access_http_200"

I think my mistake is that I don't use the "SumOfFieldFrequencyRule" and "SumOfFieldSpikeRule" the correct way.
Do I need to extend them somehow to make work?  I see they add the "count" functionality to "SpikeRule" and "FrequencyRule", but how  "my-rule.yaml" needs to specify them?
or do I need to use "type:SpikeRule" as usual, but inside SpikeRule code I have to make use of those new classes somehow?

sorry I forgot to mention where exactly the error happens:   elastalert/config.py", line 454, in load_rules
Traceback (most recent call last):
  File "elastalert/elastalert.py", line 1732, in <module>
    sys.exit(main(sys.argv[1:]))
  File "elastalert/elastalert.py", line 1726, in main
    client = ElastAlerter(args)
  File "elastalert/elastalert.py", line 111, in __init__
    self.conf = load_rules(self.args)
  File "/opt/elastalert/elastalert/config.py", line 454, in load_rules
    raise EAException('Error loading file %s: %s' % (rule_file, e))
util.EAException: Error loading file /opt/rules/count.yaml: Could not import module SumOfFieldSpikeRule: need more than 1 value to unpack

I followed it to "def load_configuration(filename, conf, args=None):"  function. Probably it fails somewhere in
    rule = load_rule_yaml(filename)
    load_options(rule, conf, filename, args)
    load_modules(rule, args)

but I can't understand what exactly it is... :(
My execution command is:
python elastalert/elastalert.py --start "2017-08-17 02:00"  --es_debug_trace debug.log --verbose --config elastalert-config/elas
talert_config.yaml  --rule /opt/rules/count.yaml
appreciate any advice :)

Assuming you have
type: "elastalert_modules.custom_rules.SumOfFieldSpikeRule"

This means you need to have a folder in the current directory named "elastalert_modules" containing "custom_rules.py" containing that code. There also needs to be an init.py file in this folder. You might be able to fix this import error by running $ export $PYTHONPATH=`pwd`
If you move the code into ruletypes.yaml, you'll need to add this line to make it work:
--- a/elastalert/config.py
+++ b/elastalert/config.py
@@ -51,6 +51,7 @@ rules_mapping = {
     'cardinality': ruletypes.CardinalityRule,
     'metric_aggregation': ruletypes.MetricAggregationRule,
     'percentage_match': ruletypes.PercentageMatchRule,
+    'SumOfFieldSpikeRule': ruletypes.SumOfFieldSpikeRule
 }

Hi,
I was able to make it all work, including duplicating and modifying the 'metric_aggregation' rule for our needs.
My issues were all in config.py / schema.yaml files :) .
Thanks a lot buddy!

@Dmitry1987
How did you do a metric_aggregation modification?? Did you a merge from Spike and Aggregation rules?
tks for help

@Qmando @Dmitry1987 : is there any code/branch/PR which you can share here? It's this already doable in master? If you can link here your current WIP, perhaps other people might test and/or pick it up.
TIA.

More issue gardening: cross-linking to related #401.


Invert angle function not reasonable.

The invert angle function seems to be trying to pull variables out of a magic hat... :P

Oh, dafuk.

Tomorrow I will make a pull request with the shift distance changed, the wall angles adjusted and maybe make the bot pass jshint.


Update description

Update description to increase topic relevance.

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

@JoeDavies-MSFT - PR has been copy edited and is ready for final review.
Thank you.
cc: @kenwith

Please change "In this article, you'll learn about" to "Learn about". Thanks.


Docs: Port 1.5 components that don't require redesign

Goal: Port 1.5 components that don't require redesign
Further discussion is needed as we have a dependency on bootstrap on most of the 1.5 components.

A simple place to start may be to scaffold the pages on the site so we can establish the full nav, etc. even if the pages have no content. That will help us know what we are working towards at least.

Closing this as we would need a separate for each component.


Notifications sound not coming : Swift 3 , iOS 10

May I know where to place this code in AppDelegate so that push notification sound will played.
     let content = UNMutableNotificationContent()
     content.sound = UNNotificationSound(named: "tone.aiff")

tone.aiff is available in my app bundle.
I placed where there is possibility to hear sound. But It's not playing.
So tell me where to place in Appdelegate to play custom sound / default sound while receiving push notifications.

Please move this question to StackOverflow, since it seems to be Firebase-agnostic assuming you're receiving notifications correctly.
If you're having issues receiving notifications, please open a separate issue.


Tag releases

There are a couple of release that were made silently. These releases need to be tagged on git so people can easily reference to it when installing the package.
You can tag on a previous commit, e.g.:
git tag -a 0.7.0 1901a47 -m "0.7.0"
git tag -a 0.8.0 3c68b57 -m "0.8.0"
git push --tags

That way people can just:
pip install https://github.com/corpetty/py-etherscan-api/archive/0.8.0.zip

yeah my  release process is garbage.. thanks, i'll get to this.


python3Packages.py-partiql-parser: init at 0.3.3

Description of changes
Homepage: https://github.com/getmoto/py-partiql-parser
moto 4.1.8 introduces this package as a dependency. Once this is merged I can submit a PR for moto 4.1.3 -> 4.1.8.
Things done

Built on platform(s)

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

[x] 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/)
23.05 Release Notes (or backporting 22.11 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 229956 run on x86_64-linux 1

4 packages built:

python310Packages.py-partiql-parser
python310Packages.py-partiql-parser.dist
python311Packages.py-partiql-parser
python311Packages.py-partiql-parser.dist

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2235

Result of nixpkgs-review pr 229956 run on x86_64-darwin 1

4 packages built:

python310Packages.py-partiql-parser
python310Packages.py-partiql-parser.dist
python311Packages.py-partiql-parser
python311Packages.py-partiql-parser.dist


fix: React-Hot-Loader compatibility

Source issue: #500.
Just changing createSymbol to behave like pure function and return the same result for the same arguments.
As a result - after hot class update .state and .props refers the same underlaying objects.
Before - RHL did not work due to runtime error, as long .state was undefined for a while.

Thanks!

That PR was a bit incomplete :)


Can't open playground with Xcode 7.2

When you open the project none of the SDK's are set in any of the targets. When you set them correctly and try to build the project it says PRODUCT_NAME undefined. I set that to Swinject then it spits out:
Umbrella header 'Swinject.h' not found,
Could not build Objective-C module 'Swinject'
What now?

Would you attach a screenshot of the error messages?
Here is an instruction to run the playground:
https://github.com/Swinject/Swinject#play-in-playground
You need to build Swinject-iOS target like this image before running the playground:

Hmmm. I tried it again and it compiled (after the fixes below):
Opening the project file right after git clone shows my Mac as the iOS target:
Changing the base SDK to Latest iOS and trying to compile
Setting the Product Name and compiling then worked

On Jan 4, 2016, at 7:00 PM, Yoichi Tagaya<EMAIL_ADDRESS>wrote:
Would you attach a screenshot of the error messages?
Here is an instruction to run the playground:
https://github.com/Swinject/Swinject#play-in-playground https://github.com/Swinject/Swinject#play-in-playground
You need to build Swinject-iOS target like this image before running the playground:
https://cloud.githubusercontent.com/assets/965994/12106497/b08847be-b3a3-11e5-92b8-fb245f235bd5.png
—
Reply to this email directly or view it on GitHub https://github.com/Swinject/Swinject/issues/47#issuecomment-168878767.

That's good to hear you succeeded building the project.
It looks Xcode has the problem. Sometimes I have another (similar) problem on another project, and restarting Xcode or removing DerivedData solves the problem.


Textfield select component inside Popper has wrong anchor in non-native mode

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example:
Steps:

https://github.com/codedthemes/berry-free-react-admin-template

Click on Notification Icon on the top right corner, and status select works OK in native-mode

Now apply the patch below

diff --git a/rmk/berry-free-react-admin-template/src/layout/MainLayout/Header/NotificationSection/index.js b/rmk/berry-free-react-admin-template/src/layout/MainLayout/Header/NotificationSection/index.js
index fcae30e429..d6a60d67ff 100644
--- a/berry-free-react-admin-template/src/layout/MainLayout/Header/NotificationSection/index.js
+++ b/berry-free-react-admin-template/src/layout/MainLayout/Header/NotificationSection/index.js
@@ -17,6 +17,7 @@ import {
     Popper,
     Stack,
     TextField,
+    MenuItem,
     Typography,
     useMediaQuery
 } from '@mui/material';
@@ -182,14 +183,11 @@ const NotificationSection = () => {
                                                                 fullWidth
                                                                 value={value}
                                                                 onChange={handleChange}
-                                                                SelectProps={{
-                                                                    native: true
-                                                                }}
                                                             >
                                                                 {status.map((option) => (
-                                                                    <option key={option.value} value={option.value}>
+                                                                    <MenuItem key={option.value} value={option.value}>
                                                                         {option.label}
-                                                                    </option>
+                                                                    </MenuItem>
                                                                 ))}
                                                             </TextField>
                                                         </Box>

Now click on the status select component. The overlay flys away.

Current behavior 😯
If SelectProps is not using native: true, the overlay flys away.
Expected behavior 🤔
No response
Context 🔦
No response
Your environment 🌎

npx @mui/envinfo
  System:
    OS: macOS 10.15.7
  Binaries:
    Node: 16.15.1 - /usr/local/opt/node@16/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 8.13.2 - /usr/local/bin/npm
  Browsers:
    Chrome: 110.0.5481.100
    Edge: Not Found
    Firefox: Not Found
    Safari: 13.1.3
  npmPackages:
    @emotion/react: ^11.8.1 => 11.10.0
    @emotion/styled: ^11.8.1 => 11.8.1
    @mui/base:  5.0.0-alpha.91
    @mui/icons-material: ^5.8.4 => 5.8.4
    @mui/lab: ^5.0.0-alpha.92 => 5.0.0-alpha.92
    @mui/material: ^5.9.2 => 5.9.2
    @mui/private-theming:  5.9.1
    @mui/styled-engine:  5.8.7
    @mui/system:  5.9.2
    @mui/types:  7.1.5
    @mui/utils:  5.9.1
    @mui/x-date-pickers: ^5.0.0-beta.3 => 5.0.0-beta.3
    @types/react: ^17.0.47 => 17.0.47
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    typescript: ^4.9.3 => 4.9.3 ```
</details>

Chrome 110.0.5481.100

Thanks for reporting this ~ would you mind providing a minimal example that can reproduce the issue? @wenq1
Here are some tips for providing a minimal example https://stackoverflow.com/help/mcve, and here's a CodeSandbox template you can quickly use https://mui.com/r/issue-template

Sure. Here you go below. Just click on "open the popper". The first native select works ok. The second one (mui-decorated) has its overlay flying away.
https://codesandbox.io/s/silly-pasteur-pvgliv?file=/src/App.tsx

please triage

will you triage?

Any update? The issue is still happening with MUI 6.1.3


[CUDA8] use NVVM IR ver 1.3

This patch makes CUDA 8 a strict requirement for CUDA support. (update: as discussed privately, we will make CUDA 8 optional by falling back to old IR version if necessary)

NVVM now use the same LLVM IR format (ver 3.8)
NVVM is now stricter in symbol names.  No dot (".") in symbols.
Update atomic helpers.

Current coverage is 87.03% (diff: 100%)

Merging #2161 into master will not change coverage

@@             master      #2161   diff @@
==========================================
  Files           308        308
  Lines         56735      56735
  Methods           0          0
  Messages          0          0
  Branches       5889       5889
==========================================
  Hits          49377      49377
  Misses         6408       6408
  Partials        950        950

Powered by Codecov. Last update 516b657...1e7837c

With the move to llvm3.9, we can't use the 3.8 bitcode path here.  Better to stay using the 3.4 IR path.  A new patch should be made with some of the useful changes here.


Fix a bug in case of ordering on an unselected metric that is of datetime type

Coverage increased (+0.02%) to 91.053% when pulling 4878d862e6290b6f9618f13ad75fa3abcd241b44 on gl3nn:sort-edge-case into 70ee976c897027b0711b967e5c658feda06b4ca7 on kayak:master.


Radar 'width' and 'overflow' are not in effect

Version
4.5.0
Reproduction link
https://codesandbox.io/s/nervous-visvesvaraya-9go4z
Steps to reproduce
Div set width, radar set width, text wrapping does not work
What is expected?
radar.name. overflow = 'break'
text break
What is actually happening?
setting width does not work

Hi! We've received your issue and please be patient to get responded. 🎉
The average response time is expected to be within one day for weekdays.
In the meanwhile, please make sure that you have posted enough image to demo your request. You may also check out the API and chart option to get the answer.
If you don't get helped for a long time (over a week) or have an urgent question to ask, you may also send an email to<EMAIL_ADDRESS>Please attach the issue link if it's a technical question.
If you are interested in the project, you may also subscribe our mailing list.
Have a nice day! 🍵

hello, do you reslove this problem? i meeted the same problem

when can we expect this fix?

"echarts": "^5.2.0",
遇到了同样的问题 设置宽高后  指示器文字设置换行或者省略号 都没有生效   在官方示例上操作也没有生效


Install w/o using extension

We're on AWS RDS, which doesn't support install custom extensions (see their docs). There doesn't seem to be much C code involved in this extension.
Would it be possible to provide to install this by manually copying the SQL functions etc.? If so, could you provide instructions?

Just CREATE SCHEMA emoji manually and then copy/paste the content of the emoji--1.0.sql file except the first two lines.
In command line you could for instance do:
psql -c "CREATE SCHEMA emoji" && tail -n +3 emoji--1.0.sql | psql


chrome 78 and saving passwords

test chrome, chrome-beta, chrome-dev to see that new logins can be saved.
first find a website that has a registration form.
for a two-field registration or 'create account' form.
type the username or email in first field
and type password in second field.
a key icon should appear in the address bar, to save the login info. but it doesn't.
and if you create account it still won't prompt for saving passwords. even though all the settings are correct in the browser.
its broken since googlechrome 78.0.3904.70. and the same beta-version.

[x] broken in googlechrome-beta 78.0.3904.85
[x] broken in googlechrome-dev 79.0.3945.16
[x] broken in googlechrome-canary 80.0.3955.0
[x] works in chromium 78.0.3904.70

scoop can't do anything to fix it as I think its a issue with chrome 78.

closing as I'm not going to use any scoop installed browser to save logins. this use-case is little more than idle curiosity, until firefox implements a feature that chrome has.

regards ratatoeey


Keras CNN Classifier

Neural network approach for best performance and potential integration into app.
Inception and VGG16 both do a good job classifying eyes open vs eyes closed EEG spectrograms. In order to make this work for Neurodoro data we'll need to

Tweak CNN input so that it takes numerical data rather than images

Figure out how to take a pretrained image classification CNN from classification to regression

rewrite final few layers?
train on examples with difficulty/performance labels?

Train & tweak

For datasets I would recommend MonicaGRawEEG0.csv. It's the longest session of Neurodoro data anyone has ever collected at one time :open_mouth:


Question about sample process

Hi Ma,
I appreciate your work and patience. I have one question, in ODE, why can't I set reverse process?

Hi,
The reverse process (likelihood computation) has yet to be fully implemented and tested. We plan to release the related code in the future.


[BUG] ModuleNotFoundError: No module named 'pydantic_settings'

Describe the bug
Trying to import beanie and ModuleNotFoundError raises.
To Reproduce
import beanie

Expected behavior
Successful import.
Additional context
I am also running pydantic v2.
Error:
ModuleNotFoundError: No module named 'pydantic_settings'

Hi! Which version do you use? '1.21.0' doesn't use settings

Pydantic v2 split settings to dedicate module, pydantic_settings. See migration guild .
If you are using new FastAPI version, I think you need to install it: pip install pydantic_settings.


TextField from this package overrides global variant prop

The Problem
In Material-UI, it is possible to set global default props (see here).
However the TextField component in this package defaults to always setting the variant prop to standard, which effectively overrides any default values set for this prop.
That means, that something like this is not possible:
import MuiThemeProvider from '@material-ui/core/styles/MuiThemeProvider';
import createMuiTheme from '@material-ui/core/styles/createMuiTheme';
import { TextField as FormikTextField } from 'formik-material-ui';
import MuiTextField from '@material-ui/core/TextField';
import { Field } from 'formik';

import * as React from 'react';

const theme = createMuiTheme({
  props: {
    MuiTextField: {
      variant: 'outlined'
    },
  }
});

export class App extends React.Component {
  public render() {
    return (
      <MuiThemeProvider theme={theme}>
        ...formik form
        <Field
          // will incorrectly be variant 'standard'
          component={FormikTextField}
        />
		// will correctly be variant 'outlined' from the theme
		<MuiTextField/>
      </MuiThemeProvider>
    );
  }
}

The Cause
I believe that this issue comes from #85 (see the offending line here). That PR doesn't have much info on it, so I can't really tell why this change was made.
Maybe @9renpoto can shed some light on that.
Current workarounds
Pinning the version of this library to v0.0.18, the version before the mentioned pull request, fixes the issue. An alternative is to always pass the variant prop, and not rely on the default props feature that Material-UI has.

Silly of me to miss that. Will fix soon

Just came here to raise this bug which took me 20 minutes to work out! Happy if I quickly raise a PR?

Sorry for the wait. Released in 0.22


update comparison log in container config

update comparison log in container config

Make warning log in comparison more consistency in both unix and windows;
use more accurate log message can not be less than instead of be larger than.

Signed-off-by: allencloud<EMAIL_ADDRESS>

Overall, I like these changes, but I have to agree with @vdemeester that we're not consistent (some warn about the flag, some about the name of the property/setting).

Updated. @vdemeester @thaJeztah
PTAL

think that's better, thanks!

Any update？

LGTM, thanks!

LGTM 🐹

Let's wait for 1.12.0 before merging this though 👼

I just discussed this with @vdemeester and this is not strictly needed for 1.12. Given that we still have a lot of high priority issues/PR's for 1.12, we decided to not merge yet, but we can merge directly after 1.12 GA.
Sorry for all the delays, @allencloud!

@vdemeester @thaJeztah
It is totally OK for me. Thanks for your review and feedback.

LGTM


Z-Index Fix for Proper Ordering.

This fixes the z-index of the lightbox overlay which now appears behind
the header, and the muting notification to be above everything else on
the page.

Automated message from Dropbox CLA bot
@brockwhittaker, it looks like you've already signed the Dropbox CLA. Thanks!

Merged, thanks @brockwhittaker!


Update Project Year to 2024

This stops wpilib prompted the user that the project is incompatible and to import the project.

This seems trivial so I will just merge this.


feat(remix-adapter): add default config

Just like we have in @netlify/remix-edge-adapter
CC/ @nickytonline

@nickytonline Is there something I should still do to get this one merged?


BXMSPROD-1558 using @kie/lock-treatment-tool

https://issues.redhat.com/browse/BXMSPROD-1558
referenced pull requests:
https://github.com/kiegroup/kogito-editors-java/pull/183
https://github.com/kiegroup/kie-jenkins-scripts/pull/1175
https://github.com/kiegroup/lock-treatment-tool/pull/1
https://github.com/kiegroup/lock-treatment-tool/pull/2
related to:

https://github.com/kiegroup/kogito-editors-java/pull/172

The (build) kogito-tooling-editors-java check has failed. Please check the logs.

It seems it's still failing :(
[2021-12-02T09:02:53.279Z] [ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.12.0:npx (lock-treatment-tool execution) on project appformer-js-monaco: Failed to run task: 'npx @kie/lock-treatment-tool -- --registry=https://repository.engineering.redhat.com/nexus/repository/registry.npmjs.org/' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[2021-12-02T09:02:53.279Z] [ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.12.0:npx (lock-treatment-tool execution) on project kogito-editors-js: Failed to run task: 'npx @kie/lock-treatment-tool -- --registry=https://repository.engineering.redhat.com/nexus/repository/registry.npmjs.org/' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1]

@yesamer thanks for checking it...
https://github.com/kiegroup/kie-jenkins-scripts/pull/1175 needs to be merged and slave images generated (I will do it) and then Jenkins's jobs will be relaunched

testing a new approach by https://github.com/kiegroup/kogito-editors-java/pull/184

replaced by https://github.com/kiegroup/kogito-editors-java/pull/184


where can I find “hexagon_nn_skel.run” ?

from "tensorflow/lite/g3doc/performance/hexagon_delegate.md" :
Run “hexagon_nn_skel.run” - Note: you will need to accept the license agreement. It should provide 3 different shared libraries “libhexagon_nn_skel.so”, “libhexagon_nn_skel_v65.so”, “libhexagon_nn_skel_v66.so”
but I can not find hexagon_nn_skel.run, where can I download  “libhexagon_nn_skel.so”, “libhexagon_nn_skel_v65.so”, “libhexagon_nn_skel_v66.so”  ??

If you read the instructions here, you can see they have included a link to download that
I extracted that link here for you, in case you don't want to search through the instructions: hexagon_nn_skel.run

thanks

thanks

If you read the instructions here, you can see they have included a link to download that
I extracted that link here for you, in case you don't want to search through the instructions: hexagon_nn_skel.run

HI There,
When I'm trying to run the file it's stuck on
Verifying archive integrity...  100%   All good.
Uncompressing Hexagon NN Shared Libs  100%
:
That's it.. I have been waiting for almost 15-20 min and no progress.
Can you please help me in finding what I'm doing wrong.
Thanks

thanks

If you read the instructions here, you can see they have included a link to download that
I extracted that link here for you, in case you don't want to search through the instructions: hexagon_nn_skel.run

HI There,
When I'm trying to run the file it's stuck on
Verifying archive integrity... 100% All good.
Uncompressing Hexagon NN Shared Libs 100%
:
That's it.. I have been waiting for almost 15-20 min and no progress.
Can you please help me in finding what I'm doing wrong.
Thanks

I finally managed to make it work. For people wondering you need to type "I ACCEPT" without quotes after ":" to make it extract files. Maybe "Y/n" option would've made more sense.


Breaking Change: Replace full ContractKit with MiniContractKit

What:
Rather than useContractKit().kit return a full contractKit instance it now will give back a MiniContractKit which has a subset of the features.
Why:
Bringing in the Full ContractKit means the Contract Classes, Wrappers, and JSON ABIs for every core Celo Contract are loaded into the dapp. For most dapps this is extra weight that provides no benefit. MiniContractKit only includes a couple of Contracts thus bundle size is dramatically reduced.
size comparison based on node modules of example app
using Minikit

using Full Contract Kit

Comptability:
For developers that want close to the old behavior a new option has been added to ContractKitProvider, buildContractsCache.  providing this with a function that returns a Wrapper Cache and then access it like const {contactsCache} =useContractKit()
Issues
fixes #176

Codecov Report

Merging #175 (8973256) into master (2998d4e) will decrease coverage by 0.15%.
The diff coverage is 20.00%.

@@            Coverage Diff             @@
##           master     #175      +/-   ##
==========================================
- Coverage   36.70%   36.55%   -0.16%
==========================================
  Files          43       44       +1
  Lines        1196     1212      +16
  Branches      170      173       +3
==========================================
+ Hits          439      443       +4
- Misses        599      608       +9
- Partials      158      161       +3

Impacted Files
Coverage Δ

...ckages/use-contractkit/src/contract-kit-reducer.ts
25.71% <0.00%> (ø)

packages/use-contractkit/src/ethers.ts
19.14% <0.00%> (ø)

packages/use-contractkit/src/types.ts
75.00% <ø> (ø)

...kages/use-contractkit/src/connectors/connectors.ts
23.75% <6.25%> (-0.08%)
:arrow_down:

...es/use-contractkit/src/use-contract-kit-methods.ts
6.89% <16.66%> (+0.94%)
:arrow_up:

...kages/use-contractkit/src/ContractCacheBuilder.tsx
33.33% <33.33%> (ø)

...ages/use-contractkit/src/contract-kit-provider.tsx
36.58% <33.33%> (-0.92%)
:arrow_down:

packages/use-contractkit/src/use-contractkit.tsx
10.71% <50.00%> (-0.40%)
:arrow_down:

packages/use-contractkit/src/utils/helpers.ts
17.50% <100.00%> (ø)

packages/use-contractkit/src/utils/metamask.ts
77.58% <100.00%> (ø)

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 2998d4e...8973256. Read the comment docs.


[rosetta-cli-conf] Cleanup Configs

This PR cleans up the rosetta-bitcoin configs!

Pull Request Test Coverage Report for Build 712

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 70.607%

Totals

Change from base Build 704:
0.0%

Covered Lines:
1523

Relevant Lines:
2157

💛  - Coveralls


onEnter hook from the docs

Who can tell me what exactly onEnter hook from Router Configuration page do?
{ path: 'messages/:id',
            onEnter: function (nextState, replaceState) {
              replaceState(null, '/messages/' + nextState.params.id)
            }
          }

Its looks to me like it do nothing: just replacing nextState with nextState.
And I suppose that it will be triggered infinite times (recursion).
Am I right?

You can either cancel the navigation or redirect by replacing state.


chez: add env hook

Motivation for this change
As a follow-up to #97927, chez can now find its libraries in a
nix-shell, and derivations for such libraries don't need to handle the
search path themselves.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)

[x] scheme has been tested interactively, try echo '(import (srfi :1))' | nix-shell -I nixpkgs=$(pwd) -p chez chez-srfi --run scheme

[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Thanks!


Git conflict notifications

A bot that will check for conflicts in active pull requests and post comment to notify user

We've opened it already here


Gen tabular datasets

Goal:
This PR aims to make writing benchmarking code a bit easier for developers by parametrizing the datasets dimension.
Additions to linfa-datasets:

A function to allow generation of fictitious tabular datasets.
Two optional dependencies (statrs and rand)

resolves #259
Example
use ndarray::Array;
use linfa::Dataset;
use ndarray_rand::RandomExt;
use statrs::distribution::{Binomial, DiscreteUniform};
use rand::distributions::Distribution as randDistribution;

fn main() {
    let feat_distr = Binomial::new(0.5, 5 ).unwrap();
    let target_distr = DiscreteUniform::new(0, 5).unwrap();
    let data = make_dataset(5, 5, 2, feat_distr, target_distr);

    println!("{:#?}", data);
}

fn make_dataset<X, Y>(num_rows: usize, num_feats: usize, num_targets: usize, feat_distr: X, target_distr: Y) -> Dataset<f64, f64>
where
    X: randDistribution<f64>,
    Y: randDistribution<f64>
{
    let features = Array::random((num_rows, num_feats), feat_distr);
    let targets = Array::random((num_rows, num_targets), target_distr);

    println!("{:#?}", features);
    println!("{:#?}", targets);

    Dataset::new(features, targets)
}

Associated output
[[1.0, 2.0, 0.0, 3.0, 2.0],
 [3.0, 1.0, 2.0, 4.0, 2.0],
 [2.0, 3.0, 5.0, 2.0, 2.0],
 [2.0, 1.0, 4.0, 2.0, 2.0],
 [2.0, 4.0, 3.0, 1.0, 3.0]], shape=[5, 5], strides=[5, 1], layout=Cc (0x5), const ndim=2
[[3.0, 4.0],
 [5.0, 3.0],
 [5.0, 5.0],
 [2.0, 1.0],
 [2.0, 5.0]], shape=[5, 2], strides=[2, 1], layout=Cc (0x5), const ndim=2
DatasetBase {
    records: [[1.0, 2.0, 0.0, 3.0, 2.0],
     [3.0, 1.0, 2.0, 4.0, 2.0],
     [2.0, 3.0, 5.0, 2.0, 2.0],
     [2.0, 1.0, 4.0, 2.0, 2.0],
     [2.0, 4.0, 3.0, 1.0, 3.0]], shape=[5, 5], strides=[5, 1], layout=Cc (0x5), const ndim=2,
    targets: [[3.0, 4.0],
     [5.0, 3.0],
     [5.0, 5.0],
     [2.0, 1.0],
     [2.0, 5.0]], shape=[5, 2], strides=[2, 1], layout=Cc (0x5), const ndim=2,
    weights: [], shape=[0], strides=[0], layout=CFcf (0xf), const ndim=1,
    feature_names: [],
}

the feature array can look like this with a Laplace distribution so we are able to handle both continuous and discrete cases
[[-4.360595740165293, 8.155513405816892, -8.478208753936332, 17.23637839788624, 1.7384987675286867],
 [2.6468478875196775, -0.0055614415309673815, 3.6241064859319967, 5.072362710780806, 7.617604811173227],
 [0.79789581354939, -1.4199269716778213, 0.18709110069858814, 1.4115467400849417, -0.8056722910319407],
 [-11.46311409107569, 3.2708729527840843, 4.16040511713887, 1.6879416430935898, 2.451106903259817],
 [-2.7718365458998515, 1.941470709966388, 14.061929511357462, 5.111381148046025, 0.7341567591021234]], shape=[5, 5], strides=[5, 1], layout=Cc (0x5), const ndim=2

Adjustments to replicate with the above example
use statrs::distribution::{Binomial, DiscreteUniform, Laplace};
let feat_distr = Laplace::new(0.5, 5. ).unwrap();

Outstanding Questions

Should an example be added to an "examples" directory?
How do we go about documenting?

Codecov Report
Base: 39.17% // Head: 39.24% // Increases project coverage by +0.07% :tada:

Coverage data is based on head (7b519fd) compared to base (1f260de).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #260      +/-   ##
==========================================
+ Coverage   39.17%   39.24%   +0.07%
==========================================
  Files          92       92
  Lines        6096     6095       -1
==========================================
+ Hits         2388     2392       +4
+ Misses       3708     3703       -5

Impacted Files
Coverage Δ

datasets/src/generate.rs
60.00% <0.00%> (-25.72%)
:arrow_down:

algorithms/linfa-nn/src/linear.rs
45.16% <0.00%> (-1.72%)
:arrow_down:

algorithms/linfa-nn/tests/nn.rs
78.04% <0.00%> (ø)

algorithms/linfa-linear/src/glm/mod.rs
52.77% <0.00%> (ø)

...linfa-clustering/src/gaussian_mixture/algorithm.rs
44.10% <0.00%> (+0.88%)
:arrow_up:

algorithms/linfa-nn/src/kdtree.rs
50.00% <0.00%> (+1.35%)
:arrow_up:

...rithms/linfa-trees/src/decision_trees/algorithm.rs
37.05% <0.00%> (+1.78%)
:arrow_up:

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

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

For documentation just describe what the function generates. Something like: "This function generates a random, multi-target dataset with the specified number of rows, features, and targets. The values of the features and targets are determined using the provided distributions". You can just put the example into the function docs as a doctest.

cool I'll do that tomorrow.


Jvenstad/deployments

@bratseth please review.
I suppose this (last commit) could have been avoided with some foresight; having a "final status" which is derived from data which could change in such a way as to change the "final status" is probably unwise. This would have been the case if a step (type) which had failed for a run was later removed from the code -- the run could then look as if it hadn't failed.
I think it's also nice to have a more explicit and detailed status, as it allows for a better view (it's exposed in the HTTP API) and possibly improved logic in deployment orchestration, later on. (No need to keep redeploying something which fails validation, etc..)

LGTM, I suggest holding off merge until factory is green.

Sure!


Filter deprecated enum values

Let's assume we have an enum.
enum OldEnum {
  none,
  itemOneFirst
  itemOneSecond,
  itemTwoFirst,
  itemTwoSecond,
  itemThree,
}

So indexes are 0,1,2,3,4,5.
Then they decided to combine items itemOneX and itemsTwoX to single ones.
enum NewEnum {
  none,
  itemOne,
  itemTwo,
  @deprecated
  itemOneFirst,
  @deprecated
  itemOneSecond,
  @deprecated
  itemTwoFirst,
  @deprecated
  itemTwoSecond,
  itemThree,
}

And indexes are only 0,1,2,5. Moreover they are already in database.
The problem is when this newEnum is used as source for generation of DropdownButtonFormField as
DropdownButtonFormField(
  items: NewEnum.values.map((item) => DropdownButtonItem(value: item. child: Text(describeEnum(item))));
)

it displays items which are should not be visible to user. It would be good to skip @depreated items from values collection or even create new annotation for this feature.
P.S. Of course, I can create an extension which will filter specific items but maybe this feature have a sense?

Hi @bambinoua
From what I can see, the issue is related to Dart rather than to Flutter itself. Please open the issue in the dedicated repository.
Closing, as this isn't an issue with Flutter itself.
If you disagree, please write in the comments,
providing your flutter doctor -v, your flutter run -v,  your pubspec.yaml
a minimal reproducible code sample that does not use 3rd party plugins,
and I will reopen it.
Thank you


Issue with customrecordparser-

Hi,
We have a file with variable length and length is determined by first 6 bytes-(has multiple copybook so merged all of them-)
I am using custom record parser for this file, below are the sample parser and main class which is used-
Issue:
Nothing is matching with that 6 bytes and all are throwing an error-
and also tried to read the rejected records given size as 1000 as a sample but all the records are blank/nulls-
In the below code I have given 5 sample patterns for the file, however we have around 22 different patterns-
Can you please give us a suggestion, whether we are on the right path and how to achieve this?
Appreciate your cooperation-
Thanks-
package com.example.spark.cobol.app
import za.co.absa.cobrix.cobol.parser.common.Constants
import za.co.absa.cobrix.cobol.parser.headerparsers.{RecordHeaderParser, RecordMetadata}
class CustomRecordHeadersParser extends Serializable with RecordHeaderParser {
/** RDW header is a 5 byte header */
override def getHeaderLength: Int = 6
override def isHeaderDefinedInCopybook: Boolean = true
override def getRecordMetadata(header: Array[Byte], fileOffset: Long, fileSize: Long, recordNum: Long): RecordMetadata = {
val rdwHeaderBlock = getHeaderLength
if (header.length < rdwHeaderBlock) {
RecordMetadata(-1, isValid = false)
}
else if(header.map(_ & 0xFF).mkString("") == "01KJUG"){
RecordMetadata(8034, isValid = true)
}
else if(header.map(_ & 0xFF).mkString("") == "40NJHY"){
RecordMetadata(18034, isValid = true)
}
else if(header.map(_ & 0xFF).mkString("") == "87BGHO"){
RecordMetadata(6575, isValid = true)
}
else if(header.map(_ & 0xFF).mkString("") == "09GHGT"){
RecordMetadata(2678, isValid = true)
}
else if(header.map(_ & 0xFF).mkString("").take(3) == "HDR"){
RecordMetadata(65, isValid = false)
}
else {
//throw new IllegalStateException(s"Custom RDW headers is not matching with any of the patterns-")
RecordMetadata(1000, isValid = true)
}
}
}
package com.example.spark.cobol.app
import org.apache.log4j.{Level, Logger}
import org.apache.spark.sql.SparkSession
object SparkCodecApp {
def main(args: Array[String]): Unit = {
// Switch logging level to WARN
Logger.getLogger("org").setLevel(Level.WARN)
Logger.getLogger("akka").setLevel(Level.WARN)
val spark = SparkSession
  .builder()
  .appName("Spark-Cobol Custom header parser example")
  .getOrCreate()

val df = spark
  .read
  .format("cobol")
  .option("copybook", "../example_data/copybook_codec.cob")
  .option("is_record_sequence", "true")
  .option("generate_record_id", true)
  .option("schema_retention_policy", "collapse_root")
  .option("record_header_parser", "com.example.spark.cobol.app.CustomRecordHeadersParser") // Custom record header parser class
  .load("../example_data/data_codec/somefile.dat")

df.printSchema()

df.show

}
}

I'm not sure
header.map(_ & 0xFF).mkString("")

does what you expect. It might depend on the encoding of the header.
If you have an example of binary representation of your headers, I can advice of how to decode.
For ASCII header you can use new String(...):
val header = Array[Byte](0x54.toByte, 0x55.toByte, 0x56.toByte, 0x57.toByte)

header.map(_ & 0xFF).mkString("")         // res0: String = 84858687
new String(header, "ASCII")               // res1: String = TUVW


Add aten::glu_jvp and its variants

Register glu_jvp and glu_jvp_backward for XPU. Only glu_jvp needs xpu kernel. glu_jvp_backward will use pytorch's common implementation just like cuda at code.


Configure PHP Installation to include --with-pear flag

Sail Version: docker-compose version 1.28.5, build c4eb3a1f
Laravel Version: 8.35.1
PHP Version: PHP 8.0.3

Description:
I'm trying to install gRPC following these instructions. In "Installing PECL" there is a comment saying

If using PHP 7.4+, PHP must have been installed with the --with-pear flag.

but I could not figure out where should I put that flag.
Even ignoring the comment, when running RUN pecl install grpc on 8.0 Dockerfile, this error shows:
 => ERROR [ 5/13] RUN pecl install grpc                                                                                0.4s
------
 > [ 5/13] RUN pecl install grpc:
#8 0.401 PHP Fatal error:  Array and string offset access syntax with curly braces is no longer supported in /usr/share/php/PEAR/Config.php on line 2095
------
executor failed running [/bin/sh -c pecl install grpc]: exit code: 255
ERROR: Service 'laravel.test' failed to build

Steps To Reproduce:
php artisan sail:publish
Open 8.0 Dockerfile
Add autoconf zlib1g-dev php-pear to Line 15
Add following lines after the RUN apt-  one
RUN pecl install grpc
RUN echo "extension=grpc.so" > /etc/php/8.0/cli/php.ini

Run sail build --no-cache

Feel free to attempt a PR


Changes to Linting

:tada: This PR is included in version 4.5.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.5.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Mac_build_test flutter_gallery__transition_perf_e2e_ios failing on macOS 13

Is there an existing issue for this?

[X] I have searched the existing infra issues

Type of Request
bug
Infrastructure Environment
LUCI, Devicelab
What is happening?
Mac_build_test flutter_gallery__transition_perf_e2e_ios fails to build on macOS 13 with the following error:
Error (Xcode): No signing certificate "iOS Development" found: No "iOS Development" signing certificate matching team ID "S8QB4VV633" with a private key was found.

https://ci.chromium.org/ui/p/flutter/builders/try/Mac_build_test flutter_gallery__transition_perf_e2e_ios/3/overview
Steps to reproduce
N/A
Expected results
N/A

@yusuf-goog Do you know how certificates for codesigning works on VM bots?

@XilaiZhang did work with codesigning and should be able to provide information

umm I haven't used a "iOS Development" certificate before, the certificate I previously used was ""FLUTTER.IO LLC""

Okay I believe I figured it out. So we download the provisioning profile via CPID, but the certificate has to be added manually by chromium team (go/googler-flutter-signing#update-certificate-and-provision-file).
It seems that not all of our bots have the certificate. It's unclear to me why not all of them have it. At first I thought perhaps only the older bots that were available at the time it was initially added had it, but I tried it on a newer Mac-12 x86 bot and it passed, so I don't think that's the case.
I plan to follow up with @keyonghan next week.

@kentnguyen99 @yusuf-goog putting this in the devicelab.

The posted build ran on [mac-47-g572](https://chromium-swarm.appspot.com/bot?id=mac-47-g572) which I believe doesn't have the dev certificate installed.
For context: we have requested certificate installed in our Mac host only bots maintained by chromium team via: https://crbug.com/1370813. New testbeds added later miss those certificates.
Created https://crbug.com/1494932 to request.

All bots have been installed with the dev certificate. Please reopen if you see same issues.


indexing derivatives folder  is costly

Right now, pybids indexes everything in a bids_dir, including the derivatives/ folder. This can be a problem because it can take a very long time to launch if there is a lot in that folder.
On the other hand, it could be useful to query data from derivatives/, such as preprocessed niftis for a subject.
By default, maybe derivatives/ should be blacklisted to avoid this problem.

#64 should fix this when merged.

Merged and closing!


860

To start web client with embedded Tomcat:
Build web client project using mvn;
Run java -jar target/standalone.jar [-extractDirectory] [-resetExtract]

please, add start command to the page below:
https://github.com/griddynamics/jagger/blob/master/doc/pages/WebUiInstallation.txt
smth like:
"Starting from commit XXX, to start WebUI please do: ..."
don't delete old instruction
also I would like to know how to change WebUI properties

is there a chance to set web client properties (DB settings) before or during jar launching. current approach:

launch war => it is unpacked
go to unpacked directory and change properties
relaunch war

it will be great to avoid second relaunching. like:

set properties
launch jar

+1

👍


pkg/clusteragent/admission: introduce deployment patcher

What does this PR do?

Introduce a deployment patcher
Introduce a patch request provider, it's supposed to be implemented by a RC provider

Motivation

Additional Notes

The file patch provider is just a stub at this point and will get replaced by RC

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

@davidor thanks for the review! Could you re-approve the PR on behalf of the team now that it's not a draft anymore? 🙇


Issue with RAS coordinate system for EEG

It seems there is a new requirement of the BIDS validator that channel locations should be in the RAS coordinate system.
I was under the impression that we could specify the coordinate system but, apparently, “RAS” is the only coordinate system allowed now (which makes defining the field "EEGCoordinateSystem" useless).
Note that of the 40 EEG datasets on OpenNeuro, NONE uses the RAS system right now (to my knowledge) and all use the ARS coordinate system. This new requirement seems it will create problems in terms of backward compatibility.
I have talked to people who exported some EEG data recently. Since the BIDS validator generated an error on defining the coordinate system as ARS, then simply removed the "EEGCoordinateSystem" JSON field (so now BIDS assumes by default channel locations are in the RAS coordinate system, while they are in fact the ARS one).
@robertoostenveld @sappelhoff please share your thoughts.

hi @arnodelorme :wave: thanks for raising this issue.

It seems there is a new requirement of the BIDS validator that channel locations should be in the RAS coordinate system.

Where do you get that impression from? RAS was in fact never an accepted coordinate system, see Appendix VIII.
Currently the only "accepted" keywords for EEG are CapTrak, and Other. If users specify Other, they have to make an extensive description of the coordinate system in the EEGCoordinateSystemDescription field.
If you have a well defined and commonly used coordinate system, it would be great if we could add that to the BIDS specification, so that users may choose between CapTrak, Other, and your new ExampleName coordinate system. For you that'd have the benefit that you can outsource the big EEGCoordinateSystemDescription to the BIDS specification.
Please note that we are asking for exactly that in the appendix: It says:

If you believe a specific coordinate system should be added to the list of restricted keywords for MEG, EEG, or iEEG, please open a new issue on the bids-standard/bids-specification GitHub repository.

This new requirement seems it will create problems in terms of backward compatibility

It seems like that, that's true. However, the issue arises not because the specification has changed, but because the validator is now covering parts that it did not cover before. Thus, old issues that passed silently so far, are now revealed. RAS / ARS were always "invalid" as values for the EEGCoordinateSystem. The reason for that is, that the information is not sufficient: If you specify RAS, where is the origin of the coordinate system?
I mentioned the two solutions above (using Other+EEGCoordinateSystemDescription, or adding a new coordsystem to BIDS).

Finally, please have a look at #700 where I want to remedy several aspects for CoordinateSystems.

hi @arnodelorme :wave: thanks for raising this issue.

It seems there is a new requirement of the BIDS validator that channel locations should be in the RAS coordinate system.

Where do you get that impression from? RAS was in fact never an accepted coordinate system, see Appendix VIII.
Currently the only "accepted" keywords for EEG are CapTrak, and Other. If users specify Other, they have to make an extensive description of the coordinate system in the EEGCoordinateSystemDescription field.
If you have a well defined and commonly used coordinate system, it would be great if we could add that to the BIDS specification, so that users may choose between CapTrak, Other, and your new ExampleName coordinate system. For you that'd have the benefit that you can outsource the big EEGCoordinateSystemDescription to the BIDS specification.
Please note that we are asking for exactly that in the appendix: It says:

If you believe a specific coordinate system should be added to the list of restricted keywords for MEG, EEG, or iEEG, please open a new issue on the bids-standard/bids-specification GitHub repository.

This new requirement seems it will create problems in terms of backward compatibility

It seems like that, that's true. However, the issue arises not because the specification has changed, but because the validator is now covering parts that it did not cover before. Thus, old issues that passed silently so far, are now revealed. RAS / ARS were always "invalid" as values for the EEGCoordinateSystem. The reason for that is, that the information is not sufficient: If you specify RAS, where is the origin of the coordinate system?
I mentioned the two solutions above (using Other+EEGCoordinateSystemDescription, or adding a new coordsystem to BIDS).

Finally, please have a look at #700 where I want to remedy several aspects for CoordinateSystems.

Thank you @sappelhoff,

If you specify RAS, where is the origin of the coordinate system?

Could it be at (0, 0, 0) based on the coordinate system used for the electrodes?
I am reluctant to use "Others" and then add a text description to "EEGCoordinateSystemDescription". The goal is to be able to export/import channel coordinates automatically (and unambiguously). Could we add "EEGLAB" as a keyword for "EEGCoordinateSystem"?
Otherwise, what would you recommend?

Thank you @sappelhoff,

If you specify RAS, where is the origin of the coordinate system?

Could it be at (0, 0, 0) based on the coordinate system used for the electrodes?
I am reluctant to use "Others" and then add a text description to "EEGCoordinateSystemDescription". The goal is to be able to export/import channel coordinates automatically (and unambiguously). Could we add "EEGLAB" as a keyword for "EEGCoordinateSystem"?
Otherwise, what would you recommend?

Adding eeglab as a keyword would be fine with me, if there is a commonly used coordinate system that eeglab uses internally. However it would have to be properly documented, including a description of where the origin is. I think robert may be able to chime in on this in a couple of days.
I recommend that you take a look at the documentation of the captrak coordinate system in the fieldtrip wiki (link is in the appendix viii that I linked to above). You'll see that there is not too much information required.

Adding eeglab as a keyword would be fine with me, if there is a commonly used coordinate system that eeglab uses internally. However it would have to be properly documented, including a description of where the origin is. I think robert may be able to chime in on this in a couple of days.
I recommend that you take a look at the documentation of the captrak coordinate system in the fieldtrip wiki (link is in the appendix viii that I linked to above). You'll see that there is not too much information required.

Thanks. We could potentially use Captrack. I will see if it is compatible with the EEGLAB format.

Thanks. We could potentially use Captrack. I will see if it is compatible with the EEGLAB format.

Comment contributed by @cll008
I think we previously determined the EEGLAB system is closest to the CTF (or 4D Bti if ignoring units). i.e. nose +X, origin exactly between LPA and RPA:
Captrack nose is +Y and the origin is not exactly in between LPA and RPA:
This means the system is not the same from 90-degree rotation around the Z-axis. We would need the 3 fiducial points to recalculate the coordinate system.

Comment contributed by @cll008
I think we previously determined the EEGLAB system is closest to the CTF (or 4D Bti if ignoring units). i.e. nose +X, origin exactly between LPA and RPA:
Captrack nose is +Y and the origin is not exactly in between LPA and RPA:
This means the system is not the same from 90-degree rotation around the Z-axis. We would need the 3 fiducial points to recalculate the coordinate system.

I personally think it would not be intuitive for users to store files with the CTF coordinate systems and would vote to have "EEGLAB" keyword as well.

I personally think it would not be intuitive for users to store files with the CTF coordinate systems and would vote to have "EEGLAB" keyword as well.

I personally think it would not be intuitive for users to store files with the CTF coordinate systems and would vote to have "EEGLAB" keyword as well.

Yes, that would be fine with me. Could you perhaps prepare a page on your SCCN wiki (which I assume is the main EEGLAB documentation) about the "EEGLAB" coordinate system? That page would have to include all necessary information, similar to the entries in the fieldtrip wiki.
Then, afterwards, we could prepare a PR to BIDS specification to introduce "EEGLAB" as a valid keyword, and link from the BIDS specification to the SCCN wiki/EEGLAB documentation.
What do you think?

I personally think it would not be intuitive for users to store files with the CTF coordinate systems and would vote to have "EEGLAB" keyword as well.

Yes, that would be fine with me. Could you perhaps prepare a page on your SCCN wiki (which I assume is the main EEGLAB documentation) about the "EEGLAB" coordinate system? That page would have to include all necessary information, similar to the entries in the fieldtrip wiki.
Then, afterwards, we could prepare a PR to BIDS specification to introduce "EEGLAB" as a valid keyword, and link from the BIDS specification to the SCCN wiki/EEGLAB documentation.
What do you think?

OK, that sounds good. Let me get back to you in a week or two.

OK, that sounds good. Let me get back to you in a week or two.

progress is also tracked here: https://github.com/sccn/bids-matlab-tools/issues/51

We implemented the EEGLAB keyword with @cll0008 . Is it possible to add this as a recognized keyword for the BIDS validator?

Is it possible to add this as a recognized keyword for the BIDS validator?

yes, thanks for the news. Do you have a wiki entry / website now that is describing the "EEGLAB" keyword? That is, its axes, origin, and units that are conventionally being used?
Then we can make a PR to this repo (bids-specification), and bids-validator ... and potentially even release this as part of the upcoming (in a few weeks) 1.6 release.


⚠ PrivateHD has degraded performance

In 85f75e5, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2772 ms

Resolved: PrivateHD performance has improved in 9cda701.


Active Control max velocity default value fix

The default value for m_ctrl_velMax was set to -1.0 in PeleLM.H
The updated velocity in PeleLMFlowControler.cpp is not limited by the maximum velocity parameter if the parameter value is less than zero.
This result in the active_control.velMax input file parameter being truly optional (see issue #232).
Active control was able to converge without setting the active_control.velMax parameter:

Thanks for doing this!
Can you also modify the docs here to reflect the slightly updated behavior?
https://github.com/AMReX-Combustion/PeleLMeX/blob/62b496ca0abf7bad0ef971cb53fde6eb0226a781/Docs/source/manual/LMeXControls.rst?plain=1#L387C11-L387C11
Closes https://github.com/AMReX-Combustion/PeleLMeX/issues/232


Incompatibility with Create Fabric

Game crashes on start when Create Fabric is launched alongside Better Archery.
Appears to be an incompatibility between Create's Porting-lib and Better Archery.
Error/crash: https://mclo.gs/dYn7hmL
Create Fabric: https://www.curseforge.com/minecraft/mc-mods/create-fabric

Sorry for having to wait this long, I have just noticed this issue. I'll look into fixing it.

Found and replaced the mixin which caused the issues.

I uploaded a new version to Modrinth and Curseforge as well.

Unfortunately, the new version seems to still break create AND break several other mods.
Crashlog: https://mclo.gs/swhWzcA
I know for sure that it's this mod causing the problem, as removing any other mentioned mods just makes different mods break in their place.

https://github.com/Bendimester23/better-fletching/suites/8722282724/artifacts/394309934 this build should work.


Really hope you can share your dataset!

In the construction phase. A comprehensive documentation will be published very soon.

I'm looking forward to your dataset too! Thank you~

In README file:
Currently Used Dataset is DEU Liver Segmentation Dataset: https://eee.deu.edu.tr/moodle/mod/page/view.php?id=7872
You must apply for getting dataset.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 934 ms

Resolved: Bofrost.at performance has improved in 4b5b416.


TAlib not enabled error

Note: this is the technical bug tracker, please use other platforms for getting support and starting a (non technical) discussion. See the getting help page for details.
I'm submitting a bug report
[X] bug report
[ ] question about the decisions made in the repository
Action taken (what you did)
I installed Talib and added a Talib indicator to my strategy (BBands) as described in https://gekko.wizb.it/docs/strategies/talib_indicators.html
Expected result (what you hoped would happen)
The strategy to execute
Actual result (unexpected outcome)
I get the error:
Gekko encountered an error and can't continue
Error:
Talib is not enabled
Meta debug info:
Gekko version: v0.6.8
Nodejs version: v9.11.2
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)

Please try installing it again:

Go to the root directory of your Gekko clone (directory with the gekko.js file)
Run npm i talib
In that same directory open the package.json file and in the dependencies key, make sure you do have talib

Your package.json should look something like this (I've removed most of it for readability's sake):
{
  "name": "gekko",
  "version": "0.6.8",
  "description": "A bitcoin trading bot for auto trading at various exchanges",
  "author": "Mike van Rossum<EMAIL_ADDRESS>  "dependencies": {
    "talib": "^1.0.6",
    ...otherDependencies
  },
  ...otherStuff
}

If you do see the talib dependency in there, you should be able to run your strategy and not have the Talib is not enabled error.
Note: This modified the package.json file. In the documentation you'll see that it's recommended to install Talib with the --no-save flag to avoid this modification. If you want to update Gekko through git later, you'll have to first npm uninstall talib then install it again after the update.
Of course, if you're comfortable with git and using branches, you'll just manage it yourself without having to uninstall it.

Many thanks. That worked!

`gekko/core/talib.js:40
throw new Error(talibError + methodName + ' requires ' + paramName + '.');
^
Error: Gekko was unable to configure talib indicator:
stoch requires optInFastK_Period.`
Getting this error on backtest


Fix Conditional Compilation for Non-Raspberry Pi ARM64 Targets

Currently, Matricks will use the target architecture to determine whether to include rs_ws281x to drive the matrix or opencv to simulate the matrix, and will switch between matrix control thread functionality accordingly. We need to switch away from using a blanket cfg(target_arch = "aarch64") because it presents issues when compiling for non-Raspberry Pi devices that also use ARM64, such as M1 Macs.

No longer an issue. The simulator was removed from Matricks in #14 and moved to a different project.


FAQ

want to add few questions in FAQs section. please assign me

Hi, I would like to work on this project. Please assign it to me.

@Dsmita03 sure go ahead

Make sure to join the discord server for further communication
Don't forget to star the repository
Complete the task in next 2 days and kindly mention your issue # in your pr like:
Closes #IssueNumber

Note: the level of the issue may change based on the quality of the PR code

Hey i think i can add my knowledge and help with the FAQ  section .Please assign me this task.


Refactor content deletion

Simplify the init method in models/index.js so that it no longer
returns a promise. Easier to use.
Eliminates the deleteAllContent method from models/index.js as it
can all be handled at the API layer in a single spot.
Optimize destroyAllContent in api/db.js. Eliminates
double-fetching every post from the database and converting it to
JSON. Also only fetches ids from the database instead of the entire
model.
Eliminates the custom static method destroy in the Post model in
favor of handling detaching tag relations in a single place (the
destroying event). This also eliminates a big source of unneeded
database round trips--needing to get post ids to feed into
Post.destroy() which then re-fetches the post again.

This refactor is all the :+1:! Only thing is I've slightly buggered it up by getting some other PRs merged in first which add new instances of Models.init().then.. to the tests. I think, therefore, that this PR needs to be rebased against master.
Note, I think #6622 has a line that might conflict. If it doesn't get merged before, I'll rebase it after this gets merged.

Sorry for the merge conflict! The whole refactor looks very good :+1:!!

No worries, I'll fix it up.

Rebased.


Transaction Manager: file locking bug - switch away from Redis

Appears that the key value store that stores challenge tokens is choking, causing an error on load tests in https://github.com/digitalcredentials/dcc-server-tester/blob/main/README.md
Possible fix may be to switch away from Redis.
Part of the Load Testing Epic here: https://github.com/digitalcredentials/dcc-admin-dashboard/issues/40

@jchartrand Could not reproduce locally, but should be tested on AWS

Also cannot reproduce locally or on AWS, closing


about the layoutDM+ in paper "Retrieval-Augmented Layout Transformer for Content-Aware Layout Generation"

Thank you for your contribution to the layout work. I read the paper "Retrieval-Augmented Layout Transformer".  it point that:
LayoutDM† [19] is a discrete state-space diffusion model that can handle many constrained generation tasks. Since the model is originally designed for content-agnostic layout generation, we extend the model to accept an input image.
Can you provide some ideas about the layoutDM+. thanks very much.

Hi, thank you for your interest in our projects!
LayoutDM+ inserts the cross-attention layer (typical one in Transformer decoder) into the building block to attend to attend flattened image feature maps.

thanks for your reply.


Windowsservercore image is not working

Expected behavior
Wanted to pull the image from docker hub but it is showing the following error message:
Actual behavior
(HTTP code 500) server error - manifest unknown: manifest unknown
admin@DESKTOP-E30NQ4J MINGW64 /c/Program Files/Docker Toolbox
$ docker pull mcr.microsoft.com/windows/servercore
Using default tag: latest
Error response from daemon: manifest for mcr.microsoft.com/windows/servercore:latest not found
Information about the Issue
I am new to Docker containers, if someone is aware about the occurring issue please help me out the issue
Steps to reproduce the behavior

...
...

same error
#docker pull mcr.microsoft.com/windows/servercore
Using default tag: latest
Error response from daemon: manifest for mcr.microsoft.com/windows/servercore:latest not found: manifest unknown: manifest unknown

The mcr.microsoft.com/windows/servercore repository does not have a :latest tag, so you will have to specify a specific tag to use; here's the steps to do so (steps below are for the elasticsearch image, but the steps are similar for the image you're using):

Click on the ... button to view the image's details

Click on the Selected tag: latest to open the "tag selection" window

Click the tag / version of the image you want to run

Click the (X) to close the tag selector window

Click on the Create button to pull the image and start the container


Migrate is failing

Getting the same error as in #115
/opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/gems/3.2.0/gems/net-imap-0.3.4/lib/net/imap.rb:2170:in `get_tagged_response': Character not allowed in mailbox name: '.' (0.001 + 0.170 + 0.169 secs). (Net::IMAP::NoResponseError)
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/gems/3.2.0/gems/net-imap-0.3.4/lib/net/imap.rb:2224:in `block in send_command'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/3.2.0/monitor.rb:202:in `synchronize'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/3.2.0/monitor.rb:202:in `mon_synchronize'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/gems/3.2.0/gems/net-imap-0.3.4/lib/net/imap.rb:2206:in `send_command'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/gems/3.2.0/gems/net-imap-0.3.4/lib/net/imap.rb:1130:in `create'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/3.2.0/forwardable.rb:240:in `create'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/client/automatic_login_wrapper.rb:23:in `method_missing'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/account/folder.rb:55:in `block in create'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/retry_on_error.rb:9:in `retry_on_error'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/account/folder.rb:54:in `create'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/migrator.rb:19:in `run'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli/transfer.rb:54:in `block in run'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli/folder_enumerator.rb:42:in `block in each'
	from <internal:dir>:220:in `glob'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli/folder_enumerator.rb:38:in `glob'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli/folder_enumerator.rb:38:in `each'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli/transfer.rb:51:in `run'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli.rb:146:in `migrate'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/thor-1.3.0/lib/thor/command.rb:28:in `run'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/thor-1.3.0/lib/thor/invocation.rb:127:in `invoke_command'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/thor-1.3.0/lib/thor.rb:527:in `dispatch'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/thor-1.3.0/lib/thor/base.rb:584:in `start'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli.rb:64:in `start'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/bin/imap-backup:13:in `block in <top (required)>'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/logger.rb:42:in `sanitize_stderr'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/bin/imap-backup:12:in `<top (required)>'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/bin/imap-backup:25:in `load'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/bin/imap-backup:25:in `<main>'

What can I set/do to fix this?

Hi @TriPSs
Thanks for opening this issue.
Please run the restore with the --verbose parameter and send me the sanitized output.
In the meantime, I'll have a look at the code.

Here:
/opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/gems/3.2.0/gems/net-imap-0.3.4/lib/net/imap.rb:2170:in `get_tagged_response': Character not allowed in mailbox name: '.' (0.001 + 0.155 + 0.154 secs). (Net::IMAP::NoResponseError)
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/gems/3.2.0/gems/net-imap-0.3.4/lib/net/imap.rb:2224:in `block in send_command'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/3.2.0/monitor.rb:202:in `synchronize'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/3.2.0/monitor.rb:202:in `mon_synchronize'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/gems/3.2.0/gems/net-imap-0.3.4/lib/net/imap.rb:2206:in `send_command'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/gems/3.2.0/gems/net-imap-0.3.4/lib/net/imap.rb:1130:in `create'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/3.2.0/forwardable.rb:240:in `create'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/client/automatic_login_wrapper.rb:23:in `method_missing'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/account/folder.rb:55:in `block in create'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/retry_on_error.rb:9:in `retry_on_error'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/account/folder.rb:54:in `create'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/migrator.rb:19:in `run'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli/transfer.rb:54:in `block in run'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli/folder_enumerator.rb:42:in `block in each'
	from <internal:dir>:220:in `glob'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli/folder_enumerator.rb:38:in `glob'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli/folder_enumerator.rb:38:in `each'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli/transfer.rb:51:in `run'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli.rb:146:in `migrate'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/thor-1.3.0/lib/thor/command.rb:28:in `run'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/thor-1.3.0/lib/thor/invocation.rb:127:in `invoke_command'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/thor-1.3.0/lib/thor.rb:527:in `dispatch'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/thor-1.3.0/lib/thor/base.rb:584:in `start'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli.rb:64:in `start'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/bin/imap-backup:13:in `block in <top (required)>'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/logger.rb:42:in `sanitize_stderr'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/bin/imap-backup:12:in `<top (required)>'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/bin/imap-backup:25:in `load'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/bin/imap-backup:25:in `<main>'

Hi @TriPSs
Sorry, please use --verbose twice - it's now necessary to do that to get full client-server debugging

...also, are you restoring or migrating?
Please include the command you are giving as well as the debug output.

Okay, full command here
imap-backup migrate old-email new-email --verbose --verbose
D, [2023-11-20T15:35:27.565887 #32031] DEBUG -- : Creating IMAP instance: mail.privateemail.com, options: {:port=>993, :ssl=>{:ssl_version=>:TLSv1_2}}
C: RUBY0003 CREATE "xxxx.01 of 07-02-24 xxx xxxx"
S: RUBY0003 NO [CANNOT] Character not allowed in mailbox name: '.' (0.001 + 0.150 + 0.149 secs).
/opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/gems/3.2.0/gems/net-imap-0.3.4/lib/net/imap.rb:2170:in `get_tagged_response': Character not allowed in mailbox name: '.' (0.001 + 0.150 + 0.149 secs). (Net::IMAP::NoResponseError)
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/gems/3.2.0/gems/net-imap-0.3.4/lib/net/imap.rb:2224:in `block in send_command'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/3.2.0/monitor.rb:202:in `synchronize'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/3.2.0/monitor.rb:202:in `mon_synchronize'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/gems/3.2.0/gems/net-imap-0.3.4/lib/net/imap.rb:2206:in `send_command'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/gems/3.2.0/gems/net-imap-0.3.4/lib/net/imap.rb:1130:in `create'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/3.2.0/forwardable.rb:240:in `create'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/client/automatic_login_wrapper.rb:23:in `method_missing'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/account/folder.rb:55:in `block in create'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/retry_on_error.rb:9:in `retry_on_error'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/account/folder.rb:54:in `create'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/migrator.rb:19:in `run'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli/transfer.rb:54:in `block in run'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli/folder_enumerator.rb:42:in `block in each'
	from <internal:dir>:220:in `glob'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli/folder_enumerator.rb:38:in `glob'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli/folder_enumerator.rb:38:in `each'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli/transfer.rb:51:in `run'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli.rb:146:in `migrate'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/thor-1.3.0/lib/thor/command.rb:28:in `run'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/thor-1.3.0/lib/thor/invocation.rb:127:in `invoke_command'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/thor-1.3.0/lib/thor.rb:527:in `dispatch'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/thor-1.3.0/lib/thor/base.rb:584:in `start'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/cli.rb:64:in `start'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/bin/imap-backup:13:in `block in <top (required)>'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/lib/imap/backup/logger.rb:42:in `sanitize_stderr'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/gems/imap-backup-14.3.0/bin/imap-backup:12:in `<top (required)>'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/bin/imap-backup:25:in `load'
	from /opt/homebrew/Cellar/imap-backup/14.3.0/libexec/bin/imap-backup:25:in `<main>'

OK, you need to see what the delimiter is on the new server:
Here's an example for GMail:
imap-backup remote namespaces YOUR_EMAIL -c YOUR_CONFIG
Name       Prefix     Delimiter
personal   ""         "/"
other      (Not defined)
shared     (Not defined)

When you've got the "personal" delimiter, pass that as the --destination-delimiter parameter:
imap-backup help migrate
Usage:
  imap-backup migrate SOURCE_EMAIL DESTINATION_EMAIL [OPTIONS]

Options:
  -c, [--config=CONFIG]                                      # supply the configuration file path (default: ~/.imap-backup/config.json)
  -q, [--quiet], [--no-quiet]                                # silence all output
  -v, [--verbose], [--no-verbose]                            # increase the amount of logging. Without this option, the program gives minimal output.
Using this option once gives more detailed output. Whereas, using this option twice also shows all IMAP network calls
      [--automatic-namespaces], [--no-automatic-namespaces]  # automatically choose delimiters and prefixes
      [--destination-delimiter=DESTINATION-DELIMITER]        # the delimiter for destination folder names
  -d, [--destination-prefix=DESTINATION-PREFIX]              # the prefix (namespace) to add to destination folder names
  -r, [--reset], [--no-reset]                                # DANGER! This option deletes all messages from destination folders before uploading
      [--source-delimiter=SOURCE-DELIMITER]                  # the delimiter for source folder names
  -s, [--source-prefix=SOURCE-PREFIX]                        # the prefix (namespace) to strip from source folder names

Description:
  All emails which have been backed up for the "source account" (SOURCE_EMAIL) are
  uploaded to the "destination account" (DESTINATION_EMAIL).

  Some configuration may be necessary, as follows:

  Some IMAP servers use namespaces (i.e. prefixes like "INBOX"), while others, while
  others concatenate the names of subfolders with a charater ("delimiter") other than
  "/".

  In these cases there are two choices.

  You can use the `--automatic-namespaces` option. This wil query the source and
  detination servers for their namespace configuration and will adapt paths accordingly.
  This option requires that both the source and destination servers are available and
  work with the provided parameters and authentication.

  If automatic configuration does not work as desired, there are the `--source-prefix=`,
  `--source-delimiter=`, `--destination-prefix=` and `--destination-delimiter=`
  parameters. To check what values you should use, check the output of the `imap-backup
  remote namespaces EMAIL` command.

Okay, i ran the following:
imap-backup remote namespaces email
Name       Prefix     Delimiter
personal   ""         "/"
other      (Not defined)
shared     (Not defined)

After that I ran imap-backup migrate old_email new-email --destination-delimiter="/" but the error stays the same

Thanks, renaming the files with a dot in it fixes it!


Light color issue

With our configuration for our stoplights, we have a threshold of 5 configured for the number of errors to switch the light to red. However, I've noticed in the stoplight admin interface the light color changes to red in the GUI when it hits 3 errors instead of 5 (the stoplight is still functioning properly and waits for 2 more errors before preventing requests).

Stoplights changed a while ago (https://github.com/orgsync/stoplight/pull/61) to not store the threshold in the data store. That means stoplight-admin can't do the right thing here because the information simply isn't available.

Is that something that can be put back into stoplight? Or maybe make it configurable on the stoplight admin side? Maybe as an option when initializing the sentry application?

You should be able to configure it by overriding the default threshold. I think setting Stoplight::Default::THRESHOLD = 5 would suffice.
The problem with making it configurable is that it can vary per stoplight. It can even vary per run of a stoplight! In practice that's probably a terrible idea, but the API does allow it.
light = Stoplight('crazy') {}
(1 .. 3).each do |n|
  light.with_threshold(n).run
end

Setting the default threshold when we initialized the sinatra app worked. Thanks for your help!


delegate call check broken on optimism

Environment information

ape and plugin versions:
0.7.1

$ ape plugins list
  alchemy      0.7.1
  etherscan    0.7.0
  foundry      0.7.1
  optimism     0.7.1
  safe         0.7.0b0
  solidity     0.7.1

Python Version: 3.9.0
OS: osx/linux/win linux

What went wrong?
Please include information like:

what command you ran

        with networks.optimism.mainnet.use_default_provider():
            contract = Contract(address=address,abi=json.loads(abi))
            txn = multisend.MultiSend()
            txn.add(contract.transfer,"0xxxxxxxxxxxxxxxx",1000000,delegatecall=True)
            txn(sender=self.safe)

the code that caused the failure (see this link for help with formatting code)

The error props up in provider.py under the estimate_gas_cost where estimation fails, most likely it's related to txn_params being improperly configured for that gas estimation.

full output of the error you received

Traceback (most recent call last):

  File ~/miniconda3/envs/monitor/lib/python3.9/site-packages/ape_ethereum/provider.py:240 in estimate_gas_cost
    return self.web3.eth.estimate_gas(txn_params, block_identifier=block_id)

  File ~/miniconda3/envs/monitor/lib/python3.9/site-packages/web3/eth/eth.py:311 in estimate_gas
    return self._estimate_gas(transaction, block_identifier)

  File ~/miniconda3/envs/monitor/lib/python3.9/site-packages/web3/module.py:75 in caller
    result = w3.manager.request_blocking(

  File ~/miniconda3/envs/monitor/lib/python3.9/site-packages/web3/manager.py:326 in request_blocking
    return self.formatted_response(

  File ~/miniconda3/envs/monitor/lib/python3.9/site-packages/web3/manager.py:287 in formatted_response
    apply_error_formatters(error_formatters, response)

  File ~/miniconda3/envs/monitor/lib/python3.9/site-packages/web3/manager.py:104 in apply_error_formatters
    formatted_resp = pipe(response, error_formatters)

  File cytoolz/functoolz.pyx:680 in cytoolz.functoolz.pipe

  File cytoolz/functoolz.pyx:655 in cytoolz.functoolz.c_pipe

  File ~/miniconda3/envs/monitor/lib/python3.9/site-packages/web3/_utils/contract_error_handling.py:161 in raise_contract_logic_error_on_revert
    raise ContractLogicError(message, data=data)

ContractLogicError: execution reverted: MultiSend should only be called via delegatecall

How can it be fixed?
I changed switched the to in the tx_params variable, to the address of the contract being interacted with in the individual send, rather then the multisend and it seems to have not reverted in the multicall.
tx_params is as follows:
{'chainId': 10, 'to': '0x998739BFdAAdde7C933B942a68053933098f9EDa', 'from': 'MY_SAFE_ADDRESS', 'value': 0, 'data': '0x8d80ff0a00000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000079014200000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000242e1a7d4d000000000000000000000000000000000000000000000000000000000000006400000000000000', 'type': '0x02', 'maxFeePerGas': 5373609, 'maxPriorityFeePerGas': 1000000, 'accessList': []}

Fill this in if you have ideas on how the bug could be fixed.

closing this ticket, as it has been addressed in the latest optimism release


Dust is not working in node v0.6

Hi,
Just wanted to let you know that Dust is not working in the latest version of node. It throws the following exception
Error: require.paths is removed. Use node_modules folders, or the NODE_PATH environment variable instead.
at Function. (module.js:376:11)
at Object. (/Users/satheesh/NodeTraining/Express/node_modules/dust/lib/server.js:6:8)
at Module._compile (module.js:432:26)
at Object..js (module.js:450:10)
at Module.load (module.js:351:31)
at Function._load (module.js:310:12)
at Module.require (module.js:357:17)
at require (module.js:368:17)
at Object. (/Users/satheesh/NodeTraining/Express/node_modules/dust/lib/dust.js:511:7)
at Module._compile (module.js:432:26)
Thanks!

Solved here: https://github.com/akdubya/dustjs/pull/39


Mr

[Enter feedback here]

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

ID: ae3dbcad-9d0d-c32d-7b02-2a3ffe291b2e
Version Independent ID: 4f716e15-73a2-71a0-53ba-801b6097c479
Content: Azure Active Directory passwordless sign-in (preview)
Content Source: articles/active-directory/authentication/concept-authentication-passwordless.md
Service: active-directory
Sub-service: authentication
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

Hello @MarkPhillips00763, Thank you for reaching out! Can you please elaborate more on the issue faced?

Hello @MarkPhillips00763,  Since we have not heard back from you we will now proceed to close this thread.


Modify Design of Person Card

Create Hbox to hold Attribute type and value
create a Box to hold all Attribute Descriptors
Change background colour of Person Card

Would it be possible to split a person card into 2 columns, attributes on the left and first order attributes on the right?
I plan to implement this in #46.

Done

LGTM


Audit Links on Documentation Site

http://docs.ens.domains

@Arachnid Please -

[ ] confirm first two links in this spreadsheet are linked to proper place

[ ] fix second two links in same spreadsheet


Trades summary panel hardcoded USDT as currency

The values seem correct, but the stake currency is displayed as USDT no matter what you use, BUSD in my case.

Yes, this is because I'd have to read each config / run show_config and grab it from there. It's possible I suppose!