KeyError in tasks.PropagateResponse.source_url()

while propagating this Response:
Traceback (most recent call last):
  File "/base/data/home/apps/s~brid-gy/3.377468959475730450/tasks.py", line 394, in send_webmentions
    self.do_send_webmentions()
  File "/base/data/home/apps/s~brid-gy/3.377468959475730450/tasks.py", line 416, in do_send_webmentions
    source_url = self.source_url(target)
  File "/base/data/home/apps/s~brid-gy/3.377468959475730450/tasks.py", line 600, in source_url
    activity = self.activities[urls_to_activity[target_url]]
KeyError: u'http://runkeeper.com/user/adamprocter/activity/399523496?activityList=false&tripIdBase36=6lv6aw&channel=web.activity.shorturl'

for the record, we still see this occasionally. the propagate task usually eventually succeeds after a few retries. whee.

still happening.

saw a new symptom of this today: https://console.cloud.google.com/errors/8833924187179738464
Traceback (most recent call last):
File "/base/data/home/apps/s~brid-gy/7.395968697636195513/tasks.py", line 469, in send_webmentions
  self.do_send_webmentions()
File "/base/data/home/apps/s~brid-gy/7.395968697636195513/tasks.py", line 496, in do_send_webmentions
  source_url = self.source_url(target)
File "/base/data/home/apps/s~brid-gy/7.395968697636195513/tasks.py", line 691, in source_url
  activity = self.activities[0]
IndexError: list index out of range

searched logs for github.com/snarfed/bridgy/issues/237 on 2017/07/24, didn't find it in the last week at least. may be gone?

error reporting hasn't seen it in the last 30d either:
https://console.cloud.google.com/errors?time=P30D&filter=KeyError&order=LAST_SEEN_DESC&resolution=OPEN&resolution=ACKNOWLEDGED&project=brid-gy
tentatively closing.

It's back, saw an instance today 😂 😭

I've got two new instances of this issue. You can see one here: https://brid.gy/log?start_time=1648555482&key=agdicmlkLWd5cjYLEghSZXNwb25zZSIodGFnOnR3aXR0ZXIuY29tLDIwMTM6MTUwNTA1MzMyNTQwMTc2Mzg0Nww
Isn't https://github.com/snarfed/bridgy/commit/bb45cb351c48ca9147cc595ffda3178ec54c19ed released yet or didn't that fully resolve the issue?
You want me having a go at it? I can't promise anything, tho.

The bug that wouldn't die. 😁 😢
Thanks for the reports. bb45cb3 is definitely released, but it was aimed more a different (related) bug, #1124, not at this one directly.
I'm not actively working on this bug right now, but I'm happy to fix these two instances of yours manually, or you're also welcome to use them to debug on your own if you want!

One more example:

https://twitter.com/kevinmarks/status/1518999221692682242
tag:twitter.com,2013:1518999221692682242
agdicmlkLWd5cjYLEghSZXNwb25zZSIodGFnOnR3aXR0ZXIuY29tLDIwMTM6MTUxODk5OTIyMTY5MjY4MjI0Mgw
https://brid.gy/log?start_time=1651095909&key=agdicmlkLWd5cjYLEghSZXNwb25zZSIodGFnOnR3aXR0ZXIuY29tLDIwMTM6MTUxODk5OTIyMTY5MjY4MjI0Mgw

Notably, this one has four target URLs:

https://xoxo.zone/@kevinmarks
https://www.kevinmarks.com/distributed-verify.html
https://www.kevinmarks.com/
http://epeus.blogspot.com/2012/12/the-antifragility-of-web.html

I 2022-04-27 21:45:08.976727+00:00 Created by this poll: https://brid.gy/log?start_time=1650996502&key=agdicmlkLWd5cg4LEgdUd2l0dGVyIgF0DA
I 2022-04-27 21:45:08.977989+00:00 Starting Response comment tag:twitter.com,2013:1518999221692682242 https://twitter.com/kevinmarks/status/1518999221692682242
...
I 2022-04-27 21:45:09.885008+00:00 Returning 304: Hit https://github.com/snarfed/bridgy/issues/237 KeyError!
target url http://epeus.blogspot.com/2012/12/the-antifragility-of-web.html not in urls_to_activity: None
activities: [] {}
I 2022-04-27 21:45:09.885424+00:00
Traceback (most recent call last):
  File "/workspace/tasks.py", line 772, in source_url
    activity = self.activities[0]
IndexError: list index out of range

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/workspace/tasks.py", line 579, in do_send_webmentions
    source_url = self.source_url(target)
  File "/workspace/tasks.py", line 778, in source_url
    error(f"""Hit https://github.com/snarfed/bridgy/issues/237 KeyError!
...
oauth_dropins.webutil.flask_util.NotModified: 304 Not Modified: Hit https://github.com/snarfed/bridgy/issues/237 KeyError!
target url http://epeus.blogspot.com/2012/12/the-antifragility-of-web.html not in urls_to_activity: None
activities: []
W 2022-04-27 21:45:09.894081+00:00 Error 304, response body: '
Hit https://github.com/snarfed/bridgy/issues/237 KeyError!
target url http://epeus.blogspot.com/2012/12/the-antifragility-of-web.html not in urls_to_activity: None
activities: []
'
W 2022-04-27 21:45:09.894737+00:00 Error sending to endpoint: None
I 2022-04-27 21:45:09.895088+00:00 Returning 304: Hit https://github.com/snarfed/bridgy/issues/237 KeyError!
target url https://www.kevinmarks.com/ not in urls_to_activity: None
activities: [] {}
I 2022-04-27 21:45:09.895281+00:00
Traceback (most recent call last):
  File "/workspace/tasks.py", line 772, in source_url
    activity = self.activities[0]
IndexError: list index out of range
...
oauth_dropins.webutil.flask_util.NotModified: 304 Not Modified: Hit https://github.com/snarfed/bridgy/issues/237 KeyError!
target url https://www.kevinmarks.com/ not in urls_to_activity: None
activities: []
...

Another example:

https://twitter.com/btconf/status/1517140237159256070
https://brid.gy/log?start_time=1650765136&key=agdicmlkLWd5cjYLEghSZXNwb25zZSIodGFnOnR3aXR0ZXIuY29tLDIwMTM6MTUxNzE0MDIzNzE1OTI1NjA3MAw
https://console.cloud.google.com/datastore/entities;kind=Response;ns=__$DEFAULT$__/edit;key=0%252F%257C8%252FResponse%257C45%252Fname%253Atag%253Atwitter.com%252C2013%253A1517140237159256070?project=brid-gy

Only one target URL: https://beyondtellerrand.com/events/dusseldorf-2022/schedule/monday
I 2022-04-24 01:52:16.070367+00:00 Created by this poll: https://brid.gy/log?start_time=1650551488&key=agdicmlkLWd5chcLEgdUd2l0dGVyIgptYXJjdGhpZWxlDA
I 2022-04-24 01:52:16.070896+00:00 Starting Response comment tag:twitter.com,2013:1517140237159256070 https://twitter.com/btconf/status/1517140237159256070
I 2022-04-24 01:52:16.072150+00:00 Returning 304: Hit https://github.com/snarfed/bridgy/issues/237 KeyError!
target url https://beyondtellerrand.com/events/dusseldorf-2022/schedule/monday not in urls_to_activity: None
activities: [] {}
I 2022-04-24 01:52:16.072404+00:00
Traceback (most recent call last):
  File "/workspace/tasks.py", line 772, in source_url
    activity = self.activities[0]
IndexError: list index out of range
...
target url https://beyondtellerrand.com/events/dusseldorf-2022/schedule/monday not in urls_to_activity: None
activities: []

Key lead so far: both Response.activities_json and .urls_to_activity are empty in these cases.

Trying out a very brute force fix here. Not hugely confident in it, I give it 50/50 that it fixes the bug and doesn't introduce other problems. Will see!

Fwiw, this fixed the two examples above from earlier today. I had to delete their existing Response entities, than ran discover on the tweets, and Bridgy created new Response entities with activities_json populated, and propagate worked. I just also expect the fix to have other unintended side effects. 🤷🤷🤷

Confirmed, this change made us add and propagate arbitrary responses (likes, reposts, etc) on other people's tweets. Eg https://brid.gy/twitter/BillSeitz is now full of likes and retweets of https://twitter.com/meekaale/status/1517839838816477184, which seems totally unrelated. I can't even find how that tweet is connected to @BillSeitz. 🤦
Reverting and reopening.

Still useful learning though. I guess the fix is to keep extending the logic for populating Response.activities, in this case if the response links to the user's site.

Thanks for the details, and sorry for the trouble! Still hoping to fix the actual bug here eventually, but for now, I've fixed this one manually.

Another one: https://brid.gy/log?start_time=1656352924&key=agdicmlkLWd5cjYLEghSZXNwb25zZSIodGFnOnR3aXR0ZXIuY29tLDIwMTM6MTU0MTIwNTY1ODQ1MTU3NDc4NAw&module=background
D 2022-06-27 18:02:04.257321+00:00 Params: [('response_key', '[agdicmlk...](https://console.cloud.google.com/datastore/entities;kind=Response;ns=__$DEFAULT$__/edit;key=0%252F%257C8%252FResponse%257C45%252Fname%253Atag%253Atwitter.com%252C2013%253A1541205658451574784?project=brid-gy)')]
I 2022-06-27 18:02:04.365763+00:00 Source: OpenMentions (Twitter) openmentions, https://brid.gy/twitter/openmentions
I 2022-06-27 18:02:04.543324+00:00 Created by this poll: https://brid.gy/log?start_time=1656287751&key=agdicmlkLWd5chkLEgdUd2l0dGVyIgxvcGVubWVudGlvbnMM&module=
I 2022-06-27 18:02:04.543975+00:00 Starting Response comment tag:[twitter.com](http://twitter.com/),2013:1541205658451574784 https://twitter.com/sxybio/status/1541205658451574784
I 2022-06-27 18:02:04.546026+00:00 Returning 304: Hit https://github.com/snarfed/bridgy/issues/237 KeyError!
target url https://openmentions.com/topics/conversation-starters/ not in urls_to_activity: None
activities: [] {}
I 2022-06-27 18:02:04.546390+00:00
Traceback (most recent call last):
  File "/workspace/[tasks.py](http://tasks.py/)", line 779, in source_url
    activity = [self.activities](http://self.activities/)[0]
IndexError: list index out of range

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/workspace/[tasks.py](http://tasks.py/)", line 585, in do_send_webmentions
    source_url = self.source_url(target)
  File "/workspace/[tasks.py](http://tasks.py/)", line 785, in source_url
    error(f"""Hit https://github.com/snarfed/bridgy/issues/237 KeyError!
  File "/layers/[google.python.pip/pip/lib/python3.9/site-packages/oauth_dropins/webutil/flask_util.py](http://google.python.pip/pip/lib/python3.9/site-packages/oauth_dropins/webutil/flask_util.py)", line 221, in error
    abort(int(status), msg, **kwargs)
  File "/layers/[google.python.pip/pip/lib/python3.9/site-packages/werkzeug/exceptions.py](http://google.python.pip/pip/lib/python3.9/site-packages/werkzeug/exceptions.py)", line 879, in abort
    _aborter(status, *args, **kwargs)
  File "/layers/[google.python.pip/pip/lib/python3.9/site-packages/werkzeug/exceptions.py](http://google.python.pip/pip/lib/python3.9/site-packages/werkzeug/exceptions.py)", line 862, in __call__
    raise [self.mapping](http://self.mapping/)[code](*args, **kwargs)
oauth_dropins.webutil.flask_util.NotModified: 304 Not Modified: Hit https://github.com/snarfed/bridgy/issues/237 KeyError!
target url https://openmentions.com/topics/conversation-starters/ not in urls_to_activity: None
activities: []
W 2022-06-27 18:02:04.546860+00:00 Error 304, response body: '
Hit https://github.com/snarfed/bridgy/issues/237 KeyError!
target url https://openmentions.com/topics/conversation-starters/ not in urls_to_activity: None
activities: []
'
W 2022-06-27 18:02:04.547088+00:00 Error sending to endpoint: None
I 2022-06-27 18:02:04.547259+00:00 Some targets failed

Thanks! cc @lordmatt. Root cause here for both of the recent failed wms on https://brid.gy/twitter/openmentions is a bit different. The original tweet https://twitter.com/lordmatt/status/1541205044757929986 mentions (links to) https://openmentions.com/topics/conversation-starters/, and it sent correctly. However, it's not a syndicated copy, either explicitly or implicitly, and both of these are replies to it, so they shouldn't have been picked up or sent as wms at all. I'll file a new issue.

Added an assert in https://github.com/snarfed/bridgy/commit/7438d4d2d095b88793940d41a65873f1d7b0a9c3 at poll time, when these Respones with empty activities are created, and it started firing immediately. Collected nine examples, all reply tweets, that break down into a few categories. Useful!

Reply by someone else that links to user's site

https://brid.gy/twitter/Flo_H : https://twitter.com/supergraf/status/1545141739513692160, log
https://brid.gy/twitter/FCCIDio : https://twitter.com/andrew771211/status/1545323873851285504, log
https://brid.gy/twitter/EdgarInsider : https://twitter.com/picadix829/status/1545435065580228608, log

Reply by user that links to user's site

https://brid.gy/twitter/Betriebsfamilie : https://twitter.com/Betriebsfamilie/status/1545404764711751680, log
https://brid.gy/twitter/EddieHinkle : https://twitter.com/EddieHinkle/status/1545226690930130944, log
https://brid.gy/twitter/JamieTanna : https://twitter.com/JamieTanna/status/1545387849125609473, log

Unrelated reply, same one for all three users below!, haven't found a connection to any of them yet. https://twitter.com/librarianbe/status/1545419836079185922

https://brid.gy/twitter/_vincentritter, log
https://brid.gy/twitter/ShortFormErnie, log
https://brid.gy/twitter/RolandLegrand, log

The three different users above with the same tweet triggering this raise an interesting point: we don't separate Responses by user. That tweet is stored in the same single Response that's shared by all three users' poll and propagate tasks.
I don't know if that's a problem. If OPD looks up stored syndication links for just the user it's operating on, we could miss the other users' synd links. We should also look to see if any Response handling isn't transactional and needs to be. Otherwise, maybe this is ok?

^ e9ae80d is a partial fix here. In PropagateTask.source_url(), if we find that Response.activities_json is empty, we use Response.response_json instead. This still has problems though: in the examples above, we don't crash, but instead we now miss the targets entirely. I still haven't come up with a test that reproduces that. 😐

^ This fix is looking promising, testing worked. Tentatively closing!
First opened this bug 8y ago, what a run. End of an era. 🤞🤞🤞


[Question] Compatibility with stable-baselines3

Question
Hi,
how do I initialize a gymnasium-robotics environment such that it is compatible with stable-baselines3. E.g., I tried:
def make_env():
    env = gymnasium.make('FetchSlide-v2')
    return env
env = stable_baselines3.common.vec_env.DummyVecEnv([make_env])

which returns an error:
  File "/path/to/stable-baselines3/stable_baselines3/common/vec_env/util.py", line 68, in obs_space_info
    assert not hasattr(obs_space, "spaces"), f"Unsupported structured space '{type(obs_space)}'"
AssertionError: Unsupported structured space '<class 'gymnasium.spaces.dict.Dict'>'

I found this repo from Rodrigo de Lazcano: validate-mujoco-bindings-gym-robotics. However, it seems to use an older version of gymnasium-robotics (gym-robotics).
I couldn't find any more recent examples or documentation.

This error is related to SB3 and not to gymnasium-robotics.
To answer your question, SB3 is not yet compatible with gymnasium. See https://github.com/DLR-RM/stable-baselines3/pull/780.


Optimization: static binding of callbacks in Link

Probably this will also allow to use PureComponent in child, but unfortunately I have not tested it..

I'm going to close the PR to prevent it from laying around but we'd be happy to take in this change once the tests pass 🙏


Last blank element in array expression

Array expression is expected to be of the form:
[EXPR, EXPR, ..., EXPR]
in Esprima, while the following form:
[EXPR, EXPR, ..., EXPR,]
should be accepted and reflected as such (note the last blank element).
undefined value is not the same as the element not existing.
This breaks compatibility with prototype chain behavior expressed in the following test case from Mozilla Firefox:
var funky =
  {
    toString: function()
    {
      Array.prototype[1] = "chorp";
      Object.prototype[3] = "fnord";
      return "funky";
    }
  };
var trailingHoles = [0, funky, /* 2 */, /* 3 */,];
assertEq(trailingHoles.join(""), "0funkyfnord");

Since trailingHoles resulted in [0, funky, /* 2 /, / 3 */] tree from Esprima (the number of elements in array is missing one from Esprima), then the Object.prototype[3] is not inherited, resulting in trailingHoles.join("") to evaluate to "0funky" instead of "0funkyfnord".
EDIT: I hacked a solution to this error by adding changing the definition of parseArrayInitializer function to the following:
    function parseArrayInitializer() {
        var elements = [], node = new Node(), restSpread;

        expect('[');

        while (!match(']')) {
            if (match(',')) {
                lex();
                elements.push(null);
                if(match(']')) {
                    elements.push(null);
                }
            } else if (match('...')) {
                restSpread = new Node();
                lex();
                restSpread.finishSpreadElement(inheritCoverGrammar(parseAssignmentExpression));

                if (!match(']')) {
                    isAssignmentTarget = isBindingElement = false;
                    expect(',');
                }
                elements.push(restSpread);
            } else {
                elements.push(inheritCoverGrammar(parseAssignmentExpression));

                if (!match(']')) {
                    expect(',');
                    if(match(']')) {
                        elements.push(null);
                    }
                }
            }
        }
        lex();

        return node.finishArrayExpression(elements);
    }

the added code is:
if(match(']')) {
   elements.push(null);
}

I'm so sorry. I wasn't thinking straight when I open this issue. The behavior is correct. The statement "[,]" has exactly 1 element.
But to preserve semantics, I should actually always close an array with ",]" instead of "]". I'm closing this issue. So sorry for the trouble.


Update publish guide to new publish workflow

Closing as this has gone stale and we've introduced many changes since this was started.


Consolidated DM5 & DM26 Status Bit Outcome Improvements

Improve status bit outcomes for DM5 and DM26.
In particular, modify Table A-6-1 and Table A-6-2 for Continuous Misfire Monitoring changes for 2019MY+ engines where select forms of continuous monitoring are to be shown as complete.

27 is likely correct.
from 13 CCR 1971.1 (h)(4)
(4.1.1) The readiness status for the following component/system readiness bits shall always indicate “complete”: (A) Diesel misfire (section (e)(2)) for engines with a single monitor designed to detect both misfires identified in section (e)(2.2.1) and subject to the monitoring conditions of sections (e)(2.3.1) and (e)(2.3.2) and misfires identified in section (e)(2.2.2) and subject to the monitoring conditions of (e)(2.3.3); (B) Gasoline misfire (section (f)(2)); and (C) Diesel and gasoline comprehensive component (section (g)(3)).
(4.1.3) For 2016 and subsequent model year engines, for components and systems not listed in section (h)(4.1.1) above, the readiness status for each component/system readiness bit listed below shall immediately indicate “complete” if any of the following conditions occur: (1) all the respective supported monitors listed below for each component/system have fully executed and determined that the component or system is not malfunctioning, or (2) at least one of the monitors listed below for each component/system has determined that the component or system is malfunctioning after the requisite number of decisions necessary for determining the MIL status have been fully executed, regardless of whether or not the other monitors listed have been fully executed: (A) Diesel Fuel System: sections (e)(1.2.1), (e)(1.2.2), and (e)(1.2.3) (B) Diesel Misfire: section (e)(2.2.1) for engines with a separate monitor designed to detect misfires identified in section (e)(2.2.1) and subject to the monitoring conditions of sections (e)(2.3.1) and (e)(2.3.2) (C) Diesel EGR/VVT: sections (e)(3.2.1), (e)(3.2.2), (e)(3.2.3), (e)(3.2.5), (e)(3.2.6), and (e)(10.2) (D) Diesel Boost Pressure Control System: sections (e)(4.2.1), (e)(4.2.2), (e)(4.2.3), and (e)(4.2.4) (E) Diesel NMHC Converting Catalyst: sections (e)(5.2.2) and (e)(5.2.3)(A) (F) Diesel NOx Converting Catalyst: section (e)(6.2.1) (G) Diesel NOx Aftertreatment: sections (e)(7.2.1) and (e)(7.2.2) (H) Diesel PM Filter: (i) For 2016 through 2023 model year engines, sections (e)(8.2.1), (e)(8.2.2), (e)(8.2.5), and (e)(8.2.6) (ii) For 2024 and subsequent model year engines, sections (e)(8.2.1) and (e)(8.2.5) (I) Diesel Exhaust Gas Sensor: (i) For 2016 and subsequent model year engines on vehicles using the SAE J1939 protocol for the standardized functions required in section (h), and for 2016 through 2023 model year engines on vehicles using the ISO 15765-4 protocol for the standardized functions required in section (h), sections (e)(9.2.1)(A)(i), (e)(9.2.1)(A)(iv), (e)(9.2.1)(B)(i), (e)(9.2.1)(B)(iv), (e)(9.2.2)(A), (e)(9.2.2)(D), and (e)(9.2.3)(A) (ii) For 2024 and subsequent model year engines on vehicles using the ISO 15765-4 protocol for the standardized functions required in section (h), sections (e)(9.2.1)(A)(i), (e)(9.2.1)(A)(iv), (e)(9.2.1)(B)(i), (e)(9.2.1)(B)(iv), (e)(9.2.2)(A), (e)(9.2.2)(D), (e)(9.2.3)(A), and (e)(9.2.4)(A) (J) Diesel Exhaust Gas Sensor Heater: section (e)(9.2.4)(A) for vehicles using the SAE J1939 protocol for the standardized functions required in section (h) (JK) Gasoline Fuel System: section (f)(1.2.1)(C) (KL) Gasoline EGR/VVT: sections (f)(3.2.1), (f)(3.2.2), (f)(9.2.1), (f)(9.2.2), and (f)(9.2.3) (LM) Gasoline Secondary Air System: sections (f)(5.2.1), (f)(5.2.2), (f)(5.2.3), and (f)(5.2.4) (MN) Gasoline Catalyst: section (f)(6.2.1) (NO) Gasoline Evaporative System: sections (f)(7.2.2)(A) and (f)(7.2.2)(B) (OP) Gasoline Oxygen Sensor: sections (f)(8.2.1)(A), (f)(8.2.1)(D), (f)(8.2.2)(A), and (f)(8.2.2)(C) (Q) Gasoline Oxygen/Exhaust Gas Sensor Heater: section (f)(8.2.3)(A) (4.1.4) For 2016 and subsequent model year engines, for monitors that detect faults of more than one major emission-related component (e.g., a single monitor that is used to detect both oxygen sensor faults that are tied to the oxygen sensor readiness bit and air-fuel ratio cylinder imbalance faults that are tied to the fuel system readiness bit), the manufacturer shall include the monitor only in the readiness status for the component/system that the monitor is primarily calibrated, intended, or expected in-use to detect faults of. (4.1.5) Except for the readiness bits listed under section (h)(4.1.1) above, the readiness status for each of the monitored components or systems shall indicate “not complete” whenever fault memory has been cleared or erased by a means other than that allowed in section (d)(2). Normal vehicle shut down (i.e., key off, engine off) may not cause the readiness status to indicate “not complete”.
(4.1.7) Manufacturers are not required to use the following monitors in determining the readiness status for the specific component or system: (A) Circuit and out-of-range monitors that are required to be continuous; (B) Gasoline and diesel exhaust gas sensor feedback monitors specified in sections (e)(9.2.1)(A)(iii), (e)(9.2.1)(B)(iii), (e)(9.2.2)(C), (f)(8.2.1)(C), and (f)(8.2.2)(E); (C) Diesel feedback control monitors specified in sections (e)(1.2.4), (e)(3.2.4), (e)(4.2.5), (e)(6.2.2)(D), (e)(7.2.3), and (e)(8.2.7); (D) Gasoline fuel system monitors specified in sections (f)(1.2.1)(A), (f)(1.2.1)(B), (f)(1.2.2), and (f)(1.2.4), and (f)(1.2.5).

Consolidated DM5 and DM26 criteria provided by .txt3 version and will not be added here.
Table A-6 Changes to be provided by #1125
Keep open for Task 5 criteria improvements.

Check for undesired DM26 outcomes in next release.

A.6 Table Implementation tracked in #1174


Duplicate Family Member Record Types created on package installed

Because we are using the ensure_record_type CCI command on the contact object, we created duplicate Family Member record types.  This didn't appear in scratch orgs due to not having namespaces.
Our options are to either create an OCC Master record type that can be deleted.  OR to remove one of the record types from the package.   I'd recommend the OCC Master as a post install step could be to deactivate or delete.
Thoughts @mkolodner?

I'll go with your recommendation. I'm not entirely sure I actually follow what you're describing.

This is what is happening right now - two Family Member record types.

I think if we change the unmanaged one to be OCC Master, we'd be ok.  Sole reason for this "master" is packages and record types have some quarks in order to add on install.

Renamed ensure record type to OCC Master and this fixed the issue. Adding how to delete in instructions.


Tests build failures on armv7hl, ppc64le, s390x

Hey, I'm trying to package xsimd for Fedora and I have weird failures on armv7hl, ppc64le and s390x architectures.
I run basically:
cmake -DBUILD_TESTS=ON .
make
make install
make xtest

ppc64le says: unrecognized command line option '-march=native'
armv7hl and s390x have more failures:
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:40:58: error: 'XSIMD_DEFAULT_ALIGNMENT' was not declared in this scope; did you mean 'XSIMD_DEFAULT_ALLOCATOR'?
   40 |     std::vector<double, xsimd::aligned_allocator<double, XSIMD_DEFAULT_ALIGNMENT>> aa(93, 123), ba(93, 123), ca(93);
      |                                                          ^~~~~~~~~~~~~~~~~~~~~~~
      |                                                          XSIMD_DEFAULT_ALLOCATOR
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:40:58: error: template argument 2 is invalid
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:40:81: error: template argument 2 is invalid
   40 |     std::vector<double, xsimd::aligned_allocator<double, XSIMD_DEFAULT_ALIGNMENT>> aa(93, 123), ba(93, 123), ca(93);
      |                                                                                ^~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:40:94: error: expression list treated as compound expression in initializer [-fpermissive]
   40 |     std::vector<double, xsimd::aligned_allocator<double, XSIMD_DEFAULT_ALIGNMENT>> aa(93, 123), ba(93, 123), ca(93);
      |                                                                                ^
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:40:87: warning: left operand of comma operator has no effect [-Wunused-value]
   40 |     std::vector<double, xsimd::aligned_allocator<double, XSIMD_DEFAULT_ALIGNMENT>> aa(93, 123), ba(93, 123), ca(93);
      |                                                                                ^~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:40:107: error: expression list treated as compound expression in initializer [-fpermissive]
   40 |     std::vector<double, xsimd::aligned_allocator<double, XSIMD_DEFAULT_ALIGNMENT>> aa(93, 123), ba(93, 123), ca(93);
      |                                                                                ^
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:40:100: warning: left operand of comma operator has no effect [-Wunused-value]
   40 |     std::vector<double, xsimd::aligned_allocator<double, XSIMD_DEFAULT_ALIGNMENT>> aa(93, 123), ba(93, 123), ca(93);
      |                                                                                ^~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:50:25: error: request for member 'begin' in 'aa', which is of non-class type 'int'
   50 |     xsimd::transform(aa.begin(), aa.end(), ba.begin(), c.begin(),
      |                         ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:50:37: error: request for member 'end' in 'aa', which is of non-class type 'int'
   50 |     xsimd::transform(aa.begin(), aa.end(), ba.begin(), c.begin(),
      |                                     ^~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:50:47: error: request for member 'begin' in 'ba', which is of non-class type 'int'
   50 |     xsimd::transform(aa.begin(), aa.end(), ba.begin(), c.begin(),
      |                                               ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:55:25: error: request for member 'begin' in 'aa', which is of non-class type 'int'
   55 |     xsimd::transform(aa.begin(), aa.end(), b.begin(), c.begin(),
      |                         ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:55:37: error: request for member 'end' in 'aa', which is of non-class type 'int'
   55 |     xsimd::transform(aa.begin(), aa.end(), b.begin(), c.begin(),
      |                                     ^~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:60:45: error: request for member 'begin' in 'ba', which is of non-class type 'int'
   60 |     xsimd::transform(a.begin(), a.end(), ba.begin(), c.begin(),
      |                                             ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:65:25: error: request for member 'begin' in 'aa', which is of non-class type 'int'
   65 |     xsimd::transform(aa.begin(), aa.end(), ba.begin(), ca.begin(),
      |                         ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:65:37: error: request for member 'end' in 'aa', which is of non-class type 'int'
   65 |     xsimd::transform(aa.begin(), aa.end(), ba.begin(), ca.begin(),
      |                                     ^~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:65:47: error: request for member 'begin' in 'ba', which is of non-class type 'int'
   65 |     xsimd::transform(aa.begin(), aa.end(), ba.begin(), ca.begin(),
      |                                               ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:65:59: error: request for member 'begin' in 'ca', which is of non-class type 'int'
   65 |     xsimd::transform(aa.begin(), aa.end(), ba.begin(), ca.begin(),
      |                                                           ^~~~~
In file included from /usr/include/gtest/gtest.h:59,
                 from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:15:
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:67:65: error: request for member 'begin' in 'ca', which is of non-class type 'int'
   67 |     EXPECT_TRUE(std::equal(expected.begin(), expected.end(), ca.begin()) && expected.size() == ca.size());
      |                                                                 ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:67:99: error: request for member 'size' in 'ca', which is of non-class type 'int'
   67 |     EXPECT_TRUE(std::equal(expected.begin(), expected.end(), ca.begin()) && expected.size() == ca.size());
      |                                                                                ^~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:68:18: error: request for member 'begin' in 'ca', which is of non-class type 'int'
   68 |     std::fill(ca.begin(), ca.end(), -1); // erase
      |                  ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:68:30: error: request for member 'end' in 'ca', which is of non-class type 'int'
   68 |     std::fill(ca.begin(), ca.end(), -1); // erase
      |                              ^~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:70:25: error: request for member 'begin' in 'aa', which is of non-class type 'int'
   70 |     xsimd::transform(aa.begin(), aa.end(), b.begin(), ca.begin(),
      |                         ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:70:37: error: request for member 'end' in 'aa', which is of non-class type 'int'
   70 |     xsimd::transform(aa.begin(), aa.end(), b.begin(), ca.begin(),
      |                                     ^~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:70:58: error: request for member 'begin' in 'ca', which is of non-class type 'int'
   70 |     xsimd::transform(aa.begin(), aa.end(), b.begin(), ca.begin(),
      |                                                          ^~~~~
In file included from /usr/include/gtest/gtest.h:59,
                 from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:15:
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:72:65: error: request for member 'begin' in 'ca', which is of non-class type 'int'
   72 |     EXPECT_TRUE(std::equal(expected.begin(), expected.end(), ca.begin()) && expected.size() == ca.size());
      |                                                                 ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:72:99: error: request for member 'size' in 'ca', which is of non-class type 'int'
   72 |     EXPECT_TRUE(std::equal(expected.begin(), expected.end(), ca.begin()) && expected.size() == ca.size());
      |                                                                                ^~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:73:18: error: request for member 'begin' in 'ca', which is of non-class type 'int'
   73 |     std::fill(ca.begin(), ca.end(), -1); // erase
      |                  ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:73:30: error: request for member 'end' in 'ca', which is of non-class type 'int'
   73 |     std::fill(ca.begin(), ca.end(), -1); // erase
      |                              ^~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:75:45: error: request for member 'begin' in 'ba', which is of non-class type 'int'
   75 |     xsimd::transform(a.begin(), a.end(), ba.begin(), ca.begin(),
      |                                             ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:75:57: error: request for member 'begin' in 'ca', which is of non-class type 'int'
   75 |     xsimd::transform(a.begin(), a.end(), ba.begin(), ca.begin(),
      |                                                         ^~~~~
In file included from /usr/include/gtest/gtest.h:59,
                 from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:15:
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:77:65: error: request for member 'begin' in 'ca', which is of non-class type 'int'
   77 |     EXPECT_TRUE(std::equal(expected.begin(), expected.end(), ca.begin()) && expected.size() == ca.size());
      |                                                                 ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:77:99: error: request for member 'size' in 'ca', which is of non-class type 'int'
   77 |     EXPECT_TRUE(std::equal(expected.begin(), expected.end(), ca.begin()) && expected.size() == ca.size());
      |                                                                                ^~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:78:18: error: request for member 'begin' in 'ca', which is of non-class type 'int'
   78 |     std::fill(ca.begin(), ca.end(), -1); // erase
      |                  ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:78:30: error: request for member 'end' in 'ca', which is of non-class type 'int'
   78 |     std::fill(ca.begin(), ca.end(), -1); // erase
      |                              ^~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp: In member function 'virtual void xsimd_unary_transform_Test::TestBody()':
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:86:58: error: 'XSIMD_DEFAULT_ALIGNMENT' was not declared in this scope; did you mean 'XSIMD_DEFAULT_ALLOCATOR'?
   86 |     std::vector<double, xsimd::aligned_allocator<double, XSIMD_DEFAULT_ALIGNMENT>> aa(93, 123), ca(93);
      |                                                          ^~~~~~~~~~~~~~~~~~~~~~~
      |                                                          XSIMD_DEFAULT_ALLOCATOR
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:86:58: error: template argument 2 is invalid
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:86:81: error: template argument 2 is invalid
   86 |     std::vector<double, xsimd::aligned_allocator<double, XSIMD_DEFAULT_ALIGNMENT>> aa(93, 123), ca(93);
      |                                                                                ^~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:86:94: error: expression list treated as compound expression in initializer [-fpermissive]
   86 |     std::vector<double, xsimd::aligned_allocator<double, XSIMD_DEFAULT_ALIGNMENT>> aa(93, 123), ca(93);
      |                                                                                ^
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:86:87: warning: left operand of comma operator has no effect [-Wunused-value]
   86 |     std::vector<double, xsimd::aligned_allocator<double, XSIMD_DEFAULT_ALIGNMENT>> aa(93, 123), ca(93);
      |                                                                                ^~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:96:25: error: request for member 'begin' in 'aa', which is of non-class type 'int'
   96 |     xsimd::transform(aa.begin(), aa.end(), c.begin(),
      |                         ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:96:37: error: request for member 'end' in 'aa', which is of non-class type 'int'
   96 |     xsimd::transform(aa.begin(), aa.end(), c.begin(),
      |                                     ^~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:101:45: error: request for member 'begin' in 'ca', which is of non-class type 'int'
  101 |     xsimd::transform(a.begin(), a.end(), ca.begin(),
      |                                             ^~~~~
In file included from /usr/include/gtest/gtest.h:59,
                 from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:15:
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:103:65: error: request for member 'begin' in 'ca', which is of non-class type 'int'
  103 |     EXPECT_TRUE(std::equal(expected.begin(), expected.end(), ca.begin()) && expected.size() == ca.size());
      |                                                                 ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:103:99: error: request for member 'size' in 'ca', which is of non-class type 'int'
  103 |     EXPECT_TRUE(std::equal(expected.begin(), expected.end(), ca.begin()) && expected.size() == ca.size());
      |                                                                                ^~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:104:18: error: request for member 'begin' in 'ca', which is of non-class type 'int'
  104 |     std::fill(ca.begin(), ca.end(), -1); // erase
      |                  ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:104:30: error: request for member 'end' in 'ca', which is of non-class type 'int'
  104 |     std::fill(ca.begin(), ca.end(), -1); // erase
      |                              ^~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:106:25: error: request for member 'begin' in 'aa', which is of non-class type 'int'
  106 |     xsimd::transform(aa.begin(), aa.end(), ca.begin(),
      |                         ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:106:37: error: request for member 'end' in 'aa', which is of non-class type 'int'
  106 |     xsimd::transform(aa.begin(), aa.end(), ca.begin(),
      |                                     ^~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:106:47: error: request for member 'begin' in 'ca', which is of non-class type 'int'
  106 |     xsimd::transform(aa.begin(), aa.end(), ca.begin(),
      |                                               ^~~~~
In file included from /usr/include/gtest/gtest.h:59,
                 from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:15:
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:108:65: error: request for member 'begin' in 'ca', which is of non-class type 'int'
  108 |     EXPECT_TRUE(std::equal(expected.begin(), expected.end(), ca.begin()) && expected.size() == ca.size());
      |                                                                 ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:108:99: error: request for member 'size' in 'ca', which is of non-class type 'int'
  108 |     EXPECT_TRUE(std::equal(expected.begin(), expected.end(), ca.begin()) && expected.size() == ca.size());
      |                                                                                ^~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:109:18: error: request for member 'begin' in 'ca', which is of non-class type 'int'
  109 |     std::fill(ca.begin(), ca.end(), -1); // erase
      |                  ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:109:30: error: request for member 'end' in 'ca', which is of non-class type 'int'
  109 |     std::fill(ca.begin(), ca.end(), -1); // erase
      |                              ^~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp: At global scope:
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:115:80: error: 'XSIMD_DEFAULT_ALIGNMENT' was not declared in this scope; did you mean 'XSIMD_DEFAULT_ALLOCATOR'?
  115 |     using aligned_vec_t = std::vector<double, xsimd::aligned_allocator<double, XSIMD_DEFAULT_ALIGNMENT>>;
      |                                                                                ^~~~~~~~~~~~~~~~~~~~~~~
      |                                                                                XSIMD_DEFAULT_ALLOCATOR
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:115:80: error: template argument 2 is invalid
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:115:103: error: template argument 2 is invalid
  115 |     using aligned_vec_t = std::vector<double, xsimd::aligned_allocator<double, XSIMD_DEFAULT_ALIGNMENT>>;
      |                                                                                ^~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:120:5: error: 'aligned_vec_t' does not name a type
  120 |     aligned_vec_t vec = aligned_vec_t(num_elements, 123.);
      |     ^~~~~~~~~~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:121:5: error: 'aligned_vec_t' does not name a type
  121 |     aligned_vec_t small_vec = aligned_vec_t(small_num, 42.);
      |     ^~~~~~~~~~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp: In member function 'virtual void xsimd_reduce_unaligned_begin_unaligned_end_Test::TestBody()':
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:136:34: error: 'vec' was not declared in this scope
  136 |     auto const begin = std::next(vec.begin());
      |                                  ^~~
In file included from /usr/include/gtest/gtest.h:382,
                 from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:15:
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:139:5: error: template argument 1 is invalid
  139 |     EXPECT_EQ(std::accumulate(begin, end, init), xsimd::reduce(begin, end, init));
      |     ^~~~~~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:141:8: error: 'small_vec' was not declared in this scope; did you mean 'small_num'?
  141 |     if(small_vec.size() > 1)
      |        ^~~~~~~~~
      |        small_num
In file included from /usr/include/gtest/gtest.h:382,
                 from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:15:
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:146:9: error: template argument 1 is invalid
  146 |         EXPECT_EQ(std::accumulate(sbegin, send, init), xsimd::reduce(sbegin, send, init));
      |         ^~~~~~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp: In member function 'virtual void xsimd_reduce_unaligned_begin_aligned_end_Test::TestBody()':
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:152:34: error: 'vec' was not declared in this scope
  152 |     auto const begin = std::next(vec.begin());
      |                                  ^~~
In file included from /usr/include/gtest/gtest.h:382,
                 from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:15:
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:155:5: error: template argument 1 is invalid
  155 |     EXPECT_EQ(std::accumulate(begin, end, init), xsimd::reduce(begin, end, init));
      |     ^~~~~~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:157:8: error: 'small_vec' was not declared in this scope; did you mean 'small_num'?
  157 |     if(small_vec.size() > 1)
      |        ^~~~~~~~~
      |        small_num
In file included from /usr/include/gtest/gtest.h:382,
                 from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:15:
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:162:9: error: template argument 1 is invalid
  162 |         EXPECT_EQ(std::accumulate(sbegin, send, init), xsimd::reduce(sbegin, send, init));
      |         ^~~~~~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp: In member function 'virtual void xsimd_reduce_aligned_begin_unaligned_end_Test::TestBody()':
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:168:24: error: 'vec' was not declared in this scope
  168 |     auto const begin = vec.begin();
      |                        ^~~
In file included from /usr/include/gtest/gtest.h:382,
                 from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:15:
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:171:5: error: template argument 1 is invalid
  171 |     EXPECT_EQ(std::accumulate(begin, end, init), xsimd::reduce(begin, end, init));
      |     ^~~~~~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:173:8: error: 'small_vec' was not declared in this scope; did you mean 'small_num'?
  173 |     if(small_vec.size() > 1)
      |        ^~~~~~~~~
      |        small_num
In file included from /usr/include/gtest/gtest.h:382,
                 from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:15:
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:178:9: error: template argument 1 is invalid
  178 |         EXPECT_EQ(std::accumulate(sbegin, send, init), xsimd::reduce(sbegin, send, init));
      |         ^~~~~~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp: In member function 'virtual void xsimd_reduce_aligned_begin_aligned_end_Test::TestBody()':
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:184:24: error: 'vec' was not declared in this scope
  184 |     auto const begin = vec.begin();
      |                        ^~~
In file included from /usr/include/gtest/gtest.h:382,
                 from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:15:
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:187:5: error: template argument 1 is invalid
  187 |     EXPECT_EQ(std::accumulate(begin, end, init), xsimd::reduce(begin, end, init));
      |     ^~~~~~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:189:8: error: 'small_vec' was not declared in this scope; did you mean 'small_num'?
  189 |     if(small_vec.size() > 1)
      |        ^~~~~~~~~
      |        small_num
In file included from /usr/include/gtest/gtest.h:382,
                 from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:15:
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:194:9: error: template argument 1 is invalid
  194 |         EXPECT_EQ(std::accumulate(sbegin, send, init), xsimd::reduce(sbegin, send, init));
      |         ^~~~~~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp: In member function 'virtual void xsimd_reduce_using_custom_binary_function_Test::TestBody()':
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:200:24: error: 'vec' was not declared in this scope
  200 |     auto const begin = vec.begin();
      |                        ^~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:205:8: error: 'small_vec' was not declared in this scope; did you mean 'small_num'?
  205 |     if(small_vec.size() > 1)
      |        ^~~~~~~~~
      |        small_num
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp: In member function 'virtual void xsimd_iterator_Test::TestBody()':
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:216:56: error: 'XSIMD_DEFAULT_ALIGNMENT' was not declared in this scope; did you mean 'XSIMD_DEFAULT_ALLOCATOR'?
  216 |     std::vector<float, xsimd::aligned_allocator<float, XSIMD_DEFAULT_ALIGNMENT>> a(10 * 16, 0.2);
      |                                                        ^~~~~~~~~~~~~~~~~~~~~~~
      |                                                        XSIMD_DEFAULT_ALLOCATOR
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:216:56: error: template argument 2 is invalid
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:216:79: error: template argument 2 is invalid
  216 |     std::vector<float, xsimd::aligned_allocator<float, XSIMD_DEFAULT_ALIGNMENT>> a(10 * 16, 0.2);
      |                                                                               ^~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:216:96: error: expression list treated as compound expression in initializer [-fpermissive]
  216 |     std::vector<float, xsimd::aligned_allocator<float, XSIMD_DEFAULT_ALIGNMENT>> a(10 * 16, 0.2);
      |                                                                                ^
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:216:87: warning: left operand of comma operator has no effect [-Wunused-value]
  216 |     std::vector<float, xsimd::aligned_allocator<float, XSIMD_DEFAULT_ALIGNMENT>> a(10 * 16, 0.2);
      |                                                                                ~~~^~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:217:79: error: template argument 2 is invalid
  217 |     std::vector<float, xsimd::aligned_allocator<float, XSIMD_DEFAULT_ALIGNMENT>> b(1000, 2.);
      |                                                                               ^~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:217:92: error: expression list treated as compound expression in initializer [-fpermissive]
  217 |     std::vector<float, xsimd::aligned_allocator<float, XSIMD_DEFAULT_ALIGNMENT>> b(1000, 2.);
      |                                                                                ^
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:217:84: warning: left operand of comma operator has no effect [-Wunused-value]
  217 |     std::vector<float, xsimd::aligned_allocator<float, XSIMD_DEFAULT_ALIGNMENT>> b(1000, 2.);
      |                                                                                ^~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:218:79: error: template argument 2 is invalid
  218 |     std::vector<float, xsimd::aligned_allocator<float, XSIMD_DEFAULT_ALIGNMENT>> c(1000, 3.);
      |                                                                               ^~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:218:92: error: expression list treated as compound expression in initializer [-fpermissive]
  218 |     std::vector<float, xsimd::aligned_allocator<float, XSIMD_DEFAULT_ALIGNMENT>> c(1000, 3.);
      |                                                                                ^
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:218:84: warning: left operand of comma operator has no effect [-Wunused-value]
  218 |     std::vector<float, xsimd::aligned_allocator<float, XSIMD_DEFAULT_ALIGNMENT>> c(1000, 3.);
      |                                                                                ^~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:220:17: error: request for member 'begin' in 'a', which is of non-class type 'int'
  220 |     std::iota(a.begin(), a.end(), 0.f);
      |                 ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:220:28: error: request for member 'end' in 'a', which is of non-class type 'int'
  220 |     std::iota(a.begin(), a.end(), 0.f);
      |                            ^~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:221:32: error: request for member 'begin' in 'a', which is of non-class type 'int'
  221 |     std::vector<float> a_cpy(a.begin(), a.end());
      |                                ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:221:43: error: request for member 'end' in 'a', which is of non-class type 'int'
  221 |     std::vector<float> a_cpy(a.begin(), a.end());
      |                                           ^~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:224:58: error: invalid types 'int[int]' for array subscript
  224 |     auto begin = xsimd::aligned_iterator<batch_type>(&a[0]);
      |                                                          ^
In file included from /builddir/build/BUILD/xsimd-7.2.3/include/xsimd/xsimd.hpp:20,
                 from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:13:
/builddir/build/BUILD/xsimd-7.2.3/include/xsimd/stl/iterator.hpp: In instantiation of 'class xsimd::aligned_iterator<float>':
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:224:59:   required from here
/builddir/build/BUILD/xsimd-7.2.3/include/xsimd/stl/iterator.hpp:86:15: error: 'float' is not a class, struct, or union type
   86 |         using value_type = typename B::value_type;
      |               ^~~~~~~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:225:56: error: invalid types 'int[int]' for array subscript
  225 |     auto end = xsimd::aligned_iterator<batch_type>(&a[0] + a.size());
      |                                                        ^
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:225:62: error: request for member 'size' in 'a', which is of non-class type 'int'
  225 |     auto end = xsimd::aligned_iterator<batch_type>(&a[0] + a.size());
      |                                                              ^~~~
In file included from /usr/include/gtest/gtest.h:59,
                 from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:15:
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:237:19: error: request for member 'size' in 'a', which is of non-class type 'int'
  237 |     EXPECT_TRUE(a.size() == a_cpy.size() && std::equal(a.begin(), a.end(), a_cpy.begin()));
      |                   ^~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:237:58: error: request for member 'begin' in 'a', which is of non-class type 'int'
  237 |     EXPECT_TRUE(a.size() == a_cpy.size() && std::equal(a.begin(), a.end(), a_cpy.begin()));
      |                                                          ^~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:237:69: error: request for member 'end' in 'a', which is of non-class type 'int'
  237 |     EXPECT_TRUE(a.size() == a_cpy.size() && std::equal(a.begin(), a.end(), a_cpy.begin()));
      |                                                                     ^~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:239:53: error: invalid types 'int[int]' for array subscript
  239 |     begin = xsimd::aligned_iterator<batch_type>(&a[0]);
      |                                                     ^
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:242:33: error: 'batch_type' is not a class, namespace, or enumeration
  242 |     for (std::size_t i = 0; i < batch_type::size; ++i)
      |                                 ^~~~~~~~~~
In file included from /usr/include/gtest/gtest.h:382,
                 from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:15:
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:244:24: error: invalid types 'int[std::size_t {aka long unsigned int}]' for array subscript
  244 |         EXPECT_NEAR(a[i], sinf(a_cpy[i]), 1e-6);
      |                        ^
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:217:82: warning: unused variable 'b' [-Wunused-variable]
  217 |     std::vector<float, xsimd::aligned_allocator<float, XSIMD_DEFAULT_ALIGNMENT>> b(1000, 2.);
      |                                                                                ^
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_algorithms.cpp:218:82: warning: unused variable 'c' [-Wunused-variable]
  218 |     std::vector<float, xsimd::aligned_allocator<float, XSIMD_DEFAULT_ALIGNMENT>> c(1000, 3.);
      |                                                                                ^
make[3]: *** [test/CMakeFiles/test_xsimd.dir/build.make:92: test/CMakeFiles/test_xsimd.dir/xsimd_algorithms.cpp.o] Error 1
/usr/bin/cmake -S/builddir/build/BUILD/xsimd-7.2.3 -B/builddir/build/BUILD/xsimd-7.2.3 --check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/make -f CMakeFiles/Makefile2 xtest
make[1]: Entering directory '/builddir/build/BUILD/xsimd-7.2.3'
/usr/bin/cmake -S/builddir/build/BUILD/xsimd-7.2.3 -B/builddir/build/BUILD/xsimd-7.2.3 --check-build-system CMakeFiles/Makefile.cmake 0
make[1]: Leaving directory '/builddir/build/BUILD/xsimd-7.2.3'
make[1]: Entering directory '/builddir/build/BUILD/xsimd-7.2.3'
/usr/bin/cmake -E cmake_progress_start /builddir/build/BUILD/xsimd-7.2.3/CMakeFiles 19
make[1]: Leaving directory '/builddir/build/BUILD/xsimd-7.2.3'
/usr/bin/make -f CMakeFiles/Makefile2 test/CMakeFiles/xtest.dir/all
/usr/bin/make -f test/CMakeFiles/test_xsimd.dir/build.make test/CMakeFiles/test_xsimd.dir/depend
make[3]: Entering directory '/builddir/build/BUILD/xsimd-7.2.3'
cd /builddir/build/BUILD/xsimd-7.2.3 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /builddir/build/BUILD/xsimd-7.2.3 /builddir/build/BUILD/xsimd-7.2.3/test /builddir/build/BUILD/xsimd-7.2.3 /builddir/build/BUILD/xsimd-7.2.3/test /builddir/build/BUILD/xsimd-7.2.3/test/CMakeFiles/test_xsimd.dir/DependInfo.cmake --color=
Dependee "/builddir/build/BUILD/xsimd-7.2.3/test/CMakeFiles/test_xsimd.dir/DependInfo.cmake" is newer than depender "/builddir/build/BUILD/xsimd-7.2.3/test/CMakeFiles/test_xsimd.dir/depend.internal".
Dependee "/builddir/build/BUILD/xsimd-7.2.3/test/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/builddir/build/BUILD/xsimd-7.2.3/test/CMakeFiles/test_xsimd.dir/depend.internal".

In file included from /builddir/build/BUILD/xsimd-7.2.3/include/xsimd/types/xsimd_traits.hpp:15,
                 from /builddir/build/BUILD/xsimd-7.2.3/include/xsimd/xsimd.hpp:14,
                 from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_basic_test.hpp:17,
                 from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_basic_test.cpp:16:
/builddir/build/BUILD/xsimd-7.2.3/include/xsimd/types/xsimd_types_include.hpp:74:4: warning: #warning "Please compile with SIMD instructions enabled or activate the fallback mode. (e.g. for x86 -march=native or for ARM -mfpu=neon)" [-Wcpp]
   74 |   #warning "Please compile with SIMD instructions enabled or activate the fallback mode. (e.g. for x86 -march=native or for ARM -mfpu=neon)"
      |    ^~~~~~~
In file included from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_basic_test.cpp:16:
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_basic_test.hpp: In function 'bool xsimd::test_char_loading(int8_t, S&)':
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_basic_test.hpp:1056:33: warning: requested alignment 64 is larger than 8 [-Wattributes]
 1056 |         alignas(64) char algn[64];
      |                                 ^
In file included from /builddir/build/BUILD/xsimd-7.2.3/test/xsimd_basic_test.cpp:17:
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_complex_basic_test.hpp: In function 'bool xsimd::test_complex_simd_load_store(std::ostream&, T&)':
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_complex_basic_test.hpp:643:15: warning: typedef 'using real_batch_type = typename T::real_batch_type' locally defined but not used [-Wunused-local-typedefs]
  643 |         using real_batch_type = typename T::real_batch_type;
      |               ^~~~~~~~~~~~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_complex_basic_test.hpp:644:15: warning: typedef 'using float_vector = typename T::float_vector' locally defined but not used [-Wunused-local-typedefs]
  644 |         using float_vector = typename T::float_vector;
      |               ^~~~~~~~~~~~
/builddir/build/BUILD/xsimd-7.2.3/test/xsimd_complex_basic_test.hpp:645:15: warning: typedef 'using double_vector = typename T::double_vector' locally defined but not used [-Wunused-local-typedefs]
  645 |         using double_vector = typename T::double_vector;
      |               ^~~~~~~~~~~~~
make[2]: *** [CMakeFiles/Makefile2:95: test/CMakeFiles/test_xsimd.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:134: test/CMakeFiles/xtest.dir/rule] Error 2

Note that there is "Please compile with SIMD instructions enabled or activate the fallback mode. (e.g. for x86 -march=native or for ARM -mfpu=neon)" yet I'm not sure exactly what to use on those architectures. Is there some arch detection here that needs to be adapted?

armv7hl.build.log
armv7hl.hw_info.log
ppc64le.build.log
ppc64le.hw_info.log
s390x.build.log
s390x.hw_info.log

Thanks for help.

@hroncok thanks for reporting!
@serge-sans-paille indeed it seems we need to improve both the architecture detection and the error message.
I'll have a look later in the afternoon, I have some tasks to finish before I can do that.

Actually the test suite cannot be built if no SIMD instruction set is available.
I'm working on a fix so that even if the architecture detection fails, the test suite can be run.
Regarding PPC, we do not support its SIMD instruction set yet, so it is expected to get the warning.
I am more concerned regarding the wrond detection on ARMv7 architecture, it should work.

See the hw_info.logs - we build on such architecture.

I have  added the ability to force the the instruction set via cmake in #292. Once it is merge, can you try to build master with the following:
cmake -DBUILD_TESTS=ON -DXSIMD_FORCE_ARM_INSTR_SET=70000000 .

If you cannot build master and need a release, let me know, I will tag a new one.

I'll try to use that as a patch. No need to merge yet, let me test it first.

https://github.com/QuantStack/xsimd/pull/292 with -DXSIMD_FORCE_ARM_INSTR_SET=70000000 works. thanks

Great! So we definitely have a detection problem, I need to figure it out.
I'm gonna release a new version, we definitely need the fix of the test suite, and I will investigate the arm problem after.

Closing this one since the test suite now builds fine, I opened a dedicated issue for the neon detection problem.

just to be clear, this means I can build xsimd on all arched? does it however make sense to ship it on platforms where it fails?

Indeed, this means the test suite can be built on any architecture, even the ones that do not provide SIMD instructions. For an unknown reason, the detection of instruction set fails on armv7hl.
I think it makes sense to ship it on ARM achitecture, since we are going to investigate and fix the issue. Regarding IBM architectures, we do not plan to support the PPC instruction set in the near future, so you might skip ppc64le and s390x for now.

Thanks.

@JohanMabille : the scalar hear are still valid for all architectures right? They're not the major feature of xsimd, but the interoperability layer they provide is already a good thing on its own.

Said otherwise, pythran in salar mode, once it compiles find on the above arch, still needs the xsimd dep.

@serge-sans-paille yes the scalar and the fallback instructions are still available, so actually I will change my previous statement, xsimd shoudl be shiped to all architectures, even if we do not support their provided SIMD instruction set.

ack. the build failed on ppc64le but succeeded on s390x
ppc64le.build.log

@hroncok I tried to fix the issue, however I have no mean to test on PPC architecture, could you check that #296 builds fine?
Thanks!


moved decos.tsx from utils/folder to components/

Hey! PLease merge my codes as i have completed issue #195


Gracefully handle bad feature files

Currently if the generator finds a .feature file that is empty or does not start with Feature: it errors out and a report is not generated.
We should either fail with a helpful error message (indicating the bad file) or we should just ignore bad feature files.

:tada: This issue has been resolved in version 1.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[GSoC] Move since and until population and raise exception in init

I have moved self.since and self.until population in case of None to compute_timeseries. This way, there is nothing out of place in __init__ of Commit class in commit.py.
Also, all __init__ methods in the Algorithm hierarchy now raise NotImplementedError.

@jgbarah , please have a look whenever convenient :)

Maybe you could rebase this (if you feel it is still convenient) after #177 was merged? Or maybe re-start from scratch, I m not sure what would be better...

@jgbarah, following the patch you merged, in conditions.py, the class Code and its children all have a pass statement in their __init__ methods (here). But I think you wanted them to raise a NotImplementedError exception as you mentioned in previous reviews. Which one do you prefer?
I'll have a look as to what can be done with this pull request.

Please have a look @jgbarah. This is a temporary solution to the problem of having since and until being populated in the __init__ method of commit.py.

Please have a look @jgbarah, @aswanipranjal.

Sorry for the delay. I wasn't feeling to well the past couple of days. I'll add changes to the notebook if you approve of the changes.

Closes #175.

Please have a look @jgbarah.


Installation, training and morphometrics

Describe the bug
I have a few issues I would like to resolve.
First, AxonDeepSeg fails to install on multiple computers (Windows, OpenSUSE, Ubuntu), the only version that works is on python 3.6 instance of miniconda. Here is the error log I receive everytime I try to install it.
error.txt
Second, after I manually updated the AxonDeepSeg, it requests that I install Tensorflow 2.2 everytime I try to train the , but when I try the install fails; it requires 2 dependencies to install which when I try installing, it doesn't actually install even though it says install successful, my guess is that it is just an issue with my OS, I think it might be best to clean install a new linux version. What do you guys think?
Third, I tried testing the morphometrics on the manual masks to test the efficacy of the data compared to my manual measurements. I do understand that it was the manual masks and not the segmented images so it might be the reason the data differs significantly. The reason I haven't used the masks to train and the use the segmented images to analyze is because of the second problem mentioned above.
Neuron Morphometrics.pdf
I only used a very small sample of 4 masks but there seems to be a significant difference in g-ratio, and myelin thickness with smaller but present differences in axon diameter. Is it possible because my masks aren't high quality enough?
Images.zip
Desktop (please complete the following information):

OS: [OpenSUSE/Windows]
Version [15.1/10]

Hi @neuropoly/qdlab
Per our documentation (https://axondeepseg.readthedocs.io/en/latest/documentation.html#installation), we don't actively test the installation on Windows using our continuous integration tests, so working with Windows is expected to be very unstable. One of us that have a Windows computer (I don't) can likely take a look at the bug to see if is easily fixable, however for better stability I would strongly recommend you use a virtual machine running Linux (e.g. see here) or if you don't plan to use the FSLeyes addon, Docker could be an alternative.

I understand I do all my tests on linux based OS, the problem is the issue shows up even on linux. I do create a conda environment on my linux and then install AxonDeepSeg, maybe that's the problem? And what's your take on the other 2 issues?

>  And what's your take on the other 2 issues?
@Paasu it makes management more difficult for us when a single issue on Github includes multiple issues that are unrelated. Could you please open separate issues, with a specific title pertaining to each issue you are having, specifying the version of ADS you are running, example data, the syntax you are using, etc. Then, we will address each of your issue separately.

@jcohenadad
Sorry about that, I just separated into different issues. Let me know if you need anything else!

I just installed ADS successfully on my OpenSUSE following the documentation for installation. The issue still exists for Windows but seems to be absent in Linux, if I get the issue again on a Linux system, I'll open up a new issue.
Thank you everyone for helping me with the situation!


build own llm agent

without using gemini openai and other ai stuff we need to develop the ai Vishwamai has datasets of coding we  https://huggingface.co/collections/VishwamAI/agi-devlopment-l1-66e01ca96848301e387d23fb let's elobrate the ai agentic view

Hello @kasinadhsarma ,
its not quite clear what you are asking for here? OpenHands does not deal with training models which is independent of agents.

Own llm ai agent like devin ai

I believe there is already an issue open for this to create a competitive LLM. However, that is not a simple task.

well can we try it i have some dataset collections and development and we can also interlink with code gemma and other stuff also

What you're asking is out of scope for this repository. Feel free to join the OpenHands Slack server to discuss LLM models etc., but we are not building/training LLM's here.


Fix BREAD Validation issues #1963 and #2179

Hello maintainers,
This is a cleaned up version of an PR I've sent before that fixes two BREAD validation issues:
Fixes #1963: Validation scroll to first error not work
Fixes #2179: Validation fails when display name and field name of a BREAD field don't match
Closes #2612
This uses custom attributes to show $field->display_name on validation error messages, and that's why I'm reverting #2077.
I hope this will be included in the next release as, currently, BREAD form validation is broken when display_name and field_name don't match.
Thank you in advance.

Looks like it should be good.  I don't have time to test it, but perhaps @emptynick or @akazorg does.  If one of them say it's good, I'll get this merged in.
Thanks!

Part of this PR is related to PR #2612.

@regiszanandrea, can you be more specific? Both PRs touch ~20 files, so it's a royal pain to truly compare them.  What part of this is related to #2612?

@fletch3555 This part: "Validation fails when display name and field name of a BREAD field don't match". The only difference is that @blitux use JS. Personally, I think this PR, better, because resolve two problems. If you accept this PR, you should close the #2612.

This indeed fixes the problem. This also looks good too me @fletch3555.

Awesome guys, thank you for your time!

@fletch3555 @samtheson The PR 2198 should also be closed

Good catch, thanks @blitux

@fletch3555 @blitux Hey gents. Sorry was away on a long holiday and then came back to tight work in January. Back to a normal life starting next week. Thanks for all the work on this.

No problem, welcome back!

Thank ye!


Mozilla Firefox Issue: Selection is not working properly from the drop-down list

Once I selected the drop-down in Mozilla Firefox, I am not able to see what i selected and the ng-model also not updating.
It is not working only in Mozilla-Firefox

Sorry for not replying sooner.
Please take a look at #262. It seems to be the same issue as yours.

This issue was selected to be spring-cleaned by a script. More information can be found here.
If anyone thinks this was a mistake and this issue should be reopened, please leave a message below explaining why. Before doing so, please consider reading the CONTRIBUTING file.


Managed buffer support

As mentioned when #16 was closed, it would be nice if softbuffer could provide a managed buffer to avoid the cost of copying. I'm imagining a double-buffered setup where you can call a function to swap the buffers.
Currently softbuffer can take up to 3-4ms to upload the buffer to the window, which is really slow. (edit: even slower with larger windows; see #18)
API design for this could be somewhat difficult but I doubt it'll be too hard. I can propose designs if you like

Closing in favor of https://github.com/rust-windowing/softbuffer/issues/40, since that has more discussion at this point.


Move types to devDependencies and remove version ranges for dependencies

This PR makes a few minor modifications to package.json:

Move all @types/* packages that were listed as dependencies to devDependencies
Remove ^ caret symbol from dependencies to avoid regressions introduced by bumped minor or patch version releases.

Thanks @frankhinek, adding @shamilovtim to the PR for comment, as he is advocating for the opposite or removing ^. ie. he suggests adding ^ to all dependencies is the right way to go.

Approved. We can continue to track the ^ discussion and decision in #385.


OpenID Exception?

Fatal error: Uncaught exception 'ErrorException' with message 'No OpenID Server found at http://steamcommunity.com/openid' in /usr/share/nginx/html/steamauth/openid.php:538 Stack trace: #0 /usr/share/nginx/html/steamauth/openid.php(671): LightOpenID->discover('http://steamcom...') #1 /usr/share/nginx/html/steamauth/SteamAuth.class.php(168): LightOpenID->authUrl() #2 /usr/share/nginx/html/page.php(12): SteamAuth->GetLoginURL() #3
Could anyone give me a pointer as to why this happens? It causes my site to throw this error and be unable to load.

This may occur when your server cannot establish connection with OpenID server or Steam OpenID Service is down and returning error (not valid openid) response.
You should secure your site for this exception because Steam Community quite often has problems.

How should I handle this exception? Also, I can login to other OpenID sites perfectly fine when only mine returns this error on all pages that require steamauth, was I firewalled or something?

If you think the problem is in your code or your server, please run example from this repository.
For handling exceptions you can put SteamAuth functions execution in try catch block.

Yeah this happens when Steam's openid server is down. Use a try..catch to avoid this.


Add recommended configuration

Can be added using
extends: plugin:promise/recommended

Resolves #53

cool 👍

Will merge!


Update health checks

This update includes the following:

change client.Client parameter to client.Reader, to support non-cached client in early init function
bug fix for ClusterOperator condition check
add checks for ClusterOperator Progressing=false and Degraded=false
add Node "Ready" check, as well as node-role labels
add ClusterVersion Available=true check
update health check polling interval to 30 seconds

/test all

/cc @browsell @pixelsoccupied @Missxiaoguo

/lgtm

/approve


20000000 or???

python create_bPfile.py 20000000 bPfile.bin
my computer has 32 gigabyte  RAM, how many million should I put in a file?

for 120 pazzle

I think it's better to use the mcpu script using 4 cpu (or more) when creating bPfile "create_bPfile_mcpu.py"
1 Biilion items makes 5GB bloom file to fill in the RAM. bPfile will be bigger, but does not matter after the bloom file is ready.

So perhaps you can try to use<PHONE_NUMBER> items. Use the latest file "bPfile_2_bloom_dll.py" when your bPfile is ready.
i am fixing a RAM bug now in it.

Yes thank you! Let me know as soon as the "bug" is fixed.

Yes thank you! Let me know as soon as the "bug" is fixed.
What an argument  "-n<PHONE_NUMBER>0000"  ?

Bug is fixed. Argument -n<PHONE_NUMBER>0000 means you search 50 Trillion keys in 1 go, and then proceed according to sequential or random mode selected.

When you run "python bPfile_2_bloom_dll.py bpfile.bin bloomfile.bin" you get an error. FileNotFoundError: Could not find module 'bloom.dll' (or one of its dependencies). Try using the full path with constructor syntax.
Help!


refactor scripts further to use config dicts per exp

My preference for organizing this would just be to have a config.json for each file, then pass in the filename as an argument. I think it looks a bit more organized than the setup now, and we don't need to register configs or anything.

OK I don't really have a preference, so I switched to json.

lol why didn't I think of that XD

looks good to me :)


Add "Follow this Game" button to posts

While browsing the main feed, you will see pictures of games that catch you eye.

It would be good if you could bookmark this game for later. Then when it's time to play+rate games, you have a list of bookmarks, plus your random selection.

Is this a partial feature of #961 ? Aslo I don't see how this would work since the main feed aren't games but posts about games (perhaps) or do you mean that bookmarking a post on someones game on say LD44 would bookmark their game rather than the post?
Further is this simply a duplicate? Maybe close in that case.


Model object property suggestion.

From now we can use this extension to show our model property in in eloquent Function. But is it possible to show it's property when a new instance of eloquent class is created?
         $user=new User();
$user->email=$request->email;
is it possible to get suggestion the property name
when I type
$user->
and the email filed as suggestion ?

Hi @eajajul ! Not it is not an option for now! But it will surely be added on the future! Will add the issue open

Thanx!
These will be so helpful if you add this in future!
Waiting for that!


feat: add cli options for server configuration

What :computer:
Added --allow-origin cli option;
Added --no-cors cli option;
Why :hand:
Feature parity with anvil;

LGTM, but is there an easy way to test this? At least manually but would be nice if we could do something in e2e tests.

Added e2e tests


Result validate status

Add validation checks for Result.status so that they begin with either "passed", "failed", "pending", etc.

Implemented in 1.1.1 with commit ec1377a48b5e21de43fe33e0c3466d102c330b38


Improve fsck handling and output

better use of git
better use of error messages
smarter behavior around importing public keys from gopass to the user's gpg keyring

Fixes #2494

hi,
thank you for reviewing this!

"QOL" is "Quality of life", so not really new features or bugfixes, just removing some friction from things.
Basically, there are two ideas:

make more messages happen at the end of the fsck process, instead of having them interrupt the progress bar (which then needs to be re-drawn, taking more console space, and making everything harder to read)
make sure a single call to fsck results in a single git commit, which tells which secrets were re-written. useful when manual intervention is done in the keyring's repo

the ability to pass around contexts in the queue allows to send info from one task to the next (although, that was useful when fsck had a non-nil queue, as the context object had its own error collector). This goes well with tasks effectively having two contexts, one from the queue and one from the add-task-to-queue caller.
the error collector helps delay error messages, so they could be displayed at once not interrupting the progress bar at each message

As for the non-go-idiomatic stuff, I'll see what I can do.

made it more idiomatic, but it seems that the error message for a non --decrypt fsck run is really misleading, so I'll need to fix that (or more likely its root cause) tomorrow.

@niacdoial Thanks a lot. Could you please have a look at the build errors? Then we should be good to go.

Concerning the build errors, I have no idea what is happening. I know it builds on my side (with nix, build script modified from the official one, under the cut in case it is relevant)
However, the CI build gives me empty errors when I check the "actions" tab of my copy of gopass (no stdout or stderr visible, but a return code of 2 for the main step of the build for all 3 platforms)

{ lib
, stdenv
, makeWrapper
, buildGo118Module
, fetchurl
, installShellFiles
, git
, gnupg
, xclip
, wl-clipboard
, passAlias ? false
}:

buildGo118Module rec {
  pname = "gopass";
  version = "dev";

  nativeBuildInputs = [ installShellFiles makeWrapper ];

  src = ./src;
#  src = fetchurl {
#    url = "file:///home/niac/gopasss/src";
#    url = "/home/niac/gopasss/src";
#    rev = "ad18f385f3b95ad8f42b8e6146a6adaf3f52ab59";
#    sha256 = "sha256-0000000000000000000000000000000000000000000=";
#  };

#  vendorSha256 = "sha256-ESIlmY3SzmfWLqLxf62dOhAsHPOKc2YYSOhzpJCjvCQ=";
  vendorSha256 = null;

  subPackages = [ "." ];

  ldflags = [ "-s" "-w" "-X main.version=${version}" "-X main.commit=000000000000" ];

  wrapperPath = lib.makeBinPath (
    [
      git
      gnupg
      xclip
    ] ++ lib.optional stdenv.isLinux wl-clipboard
  );

  postInstall = ''
    installManPage gopass.1
    installShellCompletion --zsh --name _gopass zsh.completion
    installShellCompletion --bash --name gopass.bash bash.completion
    installShellCompletion --fish --name gopass.fish fish.completion
  '' + lib.optionalString passAlias ''
    ln -s $out/bin/gopass $out/bin/pass
  '';

  postFixup = ''
    wrapProgram $out/bin/gopass \
      --prefix PATH : "${wrapperPath}" \
      --set GOPASS_NO_REMINDER true
  '';

  meta = with lib; {
    description = "The slightly more awesome Standard Unix Password Manager for Teams. Written in Go";
    homepage = "https://www.gopass.pw/";
    license = licenses.mit;
    maintainers = with maintainers; [ rvolosatovs sikmir ];
    changelog = "https://github.com/gopasspw/gopass/raw/v${version}/CHANGELOG.md";

    longDescription = ''
      gopass is a rewrite of the pass password manager in Go with the aim of
      making it cross-platform and adding additional features. Our target
      audience are professional developers and sysadmins (and especially teams
      of those) who are well versed with a command line interface. One explicit
      goal for this project is to make it more approachable to non-technical
      users. We go by the UNIX philosophy and try to do one thing and do it
      well, providing a stellar user experience and a sane, simple interface.
    '';
  };
}

turns out, the nix build script only runs some of the tests, so that's a bunch of fixes I needed to add.
And CI now builds on windows and macos, but still not linux. (still exit code 2, no stdout, no stderr)
(also I found that rcs_test.go depends on the user having a configured global git name/email to work)

Temporarily disabling 'gci' seems to unblock the linters.
Feel free to add ' gci'  to the list of disabled linters in .golangci.yml and fix the remaining issues.
Once that looks good I hope we can merge the PR.

The CI works!
(I didn't know what was the right place to look for failed CI runs, so now I got to fix all the lint hints)
it also seems that the build step on linux depends on the linter


Adding suport for interfacing with global variables in native libraries

Problem: Some libraries not only export functions, they also export variables. Current implementation doesn't support
a way to access global variables in native libraries.
Solution: Introduce new syntax that allows creation of bindings to global variables in native libraries. It should be specified only type of variable in ffi.Library object.
Example:
var library = ffi.Library("somelib", {
   "somelib_var1": [int],
   "somelib_func1": [int, [ref.types.void]]
});

Closing for now.
Honestly, I wanna move ffi.Library out into its own module, like I've done for dlfcn. It's too high-level for an ffi module, which should be just focused on creating ForeignFunction instances.


Fix filename for API testing

The filenames was originally parsed with code like the following, probably a less maintainable way we want.
test_file_name = f"{overloaded_func_name.split('_')[3]}.c"

This PR fixes this by passing the actual mnemonic as a parameter and assigning it as the filename. Files are deleted / added due to this change, but the actual contents of the unit-test don't change.

Landing this implies to adjust the test cases under llvm-project too to keep them in-sync.

Maybe encoding that info to inst_info?

Good point, changed 1st commit to reuse mnemonic already recorded under inst_info.


Create a Blog gird component for the fifth theme

As per provided designs, Create a Blog gird component for the fifth theme

Reference for the design: https://www.figma.com/file/0ISIz6XklEToDd4KXfIWRB/SCoRe-Lab-Theme-designs?node-id=3%3A4
Cc: @charithccmc, @dinithminura

hi i would like to contribute to this issue can you assign me this issue

@charithccmc hi please can you assign this issue to me i want to be part of this project of scorelab in GSOC

Hey I could work on this, is there a need to be aassigned or I just make a PR ?

@Abhijay007 i would like to work on this issue

Is this still open? I want to work on this issue.


validateFormPerSchema ignoring required = false

Possible bug, or possibly I am missing something, but even if I set "required" = false, the validateFormPerSchema routine comes back requiring it still.
Here is my code...
In the schema:
{
id: 'familyPostalCode',
component: 'QInput',
subLabel: 'Postal Code',
errorFieldName: 'Postal Code',
emitValue: true,
dense: true,
showCondition: true,
required: false
},
const result = validateFormPerSchema(formData, this.schema)
In the output...
familyAddress: null
familyBarangay: "Field is required"
familyCity: null
familyCountry: null
familyName: null
familyPostalCode: "Field is required"
familyProvince: null
Thanks for any help.

@rdemo should be fixed on latest<EMAIL_ADDRESS>(i hope you're not on the vue 2 version... 😅 )
can you test and let me know if this helped? : )
--Blitzar was made with love by Luca Ban.You cannot sponsor every project, but next time you do, think of this one for its prolonged maintenance. 💜

btw, next time don't forget to add this above your code blocks: ```js
and at the end close with ```

Yes!  That fixed it!  Thank you.
I've not posted much on github, thank you for letting me know about the js and .  I'll remember that next time.
Thanks again for such a quick response.


[FEATURE] log user information for all APIs

Is your feature request related to a problem?
At the moment user information is not logged - this is required in rest of the plugins for audit information. We should do the same for notifications plugin

Find a standard pattern for audit user information

I will try to implement this feature

we can reference the log pattern from alerting plugin which is one consumer of notification plugin. Log example
as all notification actions are extends from PluginBaseAction, we could add the logs in this class


Generate API documentation

It would be good if it can automatically generate some API documentation using swagger specification (swagger.json) or API Blueprint (*.apib) or Postman (*.postman_collection.json)

Thank you for this beautiful work and a great start .. To my understanding it is a combination of SQL and No SQL to reduce the load on the SERVER .
But my question did you think about  The rules of users are also of the right to view, edit or delete For one row or count rows in table
and if there are requests dad need to hook (code) what is the way ?

@majado2 : If I understand correctly, the question is about access control list (ACL) and hooks. Please refer to #26

Currently, there is no plan of API documentation. If anybody has solutions or suggestions - feel free to reopen this.


MCMC: Metropolis Algorithm

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
close #1260
Implementation of Markov Chain Monte Carlo algorithm, i.e. Metropolis Algorithm.
What are the significant changes in functionality due to this change request?

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[ ] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

Job Mingw Test on a17ae22 : invalidated by @wangcj05
tests\framework\PostProcessors\BasicStatistics\general  failed due to diff, retest to see if fail consistently

Job Mingw Test on a17ae22 : invalidated by @wangcj05
/opt/build_root/: rm -rf raven rm: cannot remove 'raven/tests/framework/Samplers/AdaptiveLimitSurfaceSearch/limitSurfaceMultiGrid': Device or resource busy

A new PR will be opened for this feature.


Location locations CRUD. Refs UIORG-69

Refs UIORG-69

@JohnC-80, FilteredSelect.js is a refinement of Select in order to allow one select-element to be used as a filter for the values in another, e.g. given List A of institutions and List B of campuses, if you choose an institution from A, then only campuses affiliated with that institution are displayed in B.
Should I move this to stripes-components in case we have other hierarchical menus? If so, should I stash it in lib/Select since it's just a refinement of <Select> or in its own directory?


ci: add NO_DIST to sklearnex workload

Description
Fix for public CI (LinuxSklearnex Python311)

PR should start as a draft, then move to ready for review state after CI is passed and all applicable checkboxes are closed.
This approach ensures that reviewers don't spend extra time asking for regular requirements.
You can remove a checkbox as not applicable only if it doesn't relate to this PR in any way.
For example, PR with docs update doesn't require checkboxes for performance while PR with any change in actual code should have checkboxes and justify how this code change is expected to affect performance (or justification should be self-evident).
Checklist to comply with before moving PR from draft:
PR completeness and readability

[x] I have reviewed my changes thoroughly before submitting this pull request.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have updated the documentation to reflect the changes or created a separate PR with update and provided its number in the description, if necessary.
[x] Git commit message contains an appropriate signed-off-by string (see CONTRIBUTING.md for details).
[x] I have added a respective label(s) to PR if I have a permission for that.
[x] I have resolved any merge conflicts that might occur with the base branch.

Testing

[ ] I have run it locally and tested the changes extensively.
[ ] All CI jobs are green or I have provided justification why they aren't.
[ ] I have extended testing suite if new functionality was introduced in this PR.

Looks like the env. variable NO_DIST=1 worked for the tests, but arg --nodist didn't work for the examples:
Traceback (most recent call last):
  File "/home/vsts/work/1/s/sklearnex/examples/daal4py/naive_bayes_spmd.py", line 36, in <module>
    talgo = d4p.multinomial_naive_bayes_training(20, distributed=True)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "build/daal4py_cy.pyx", line 17656, in daal4py._daal4py.multinomial_naive_bayes_training.__cinit__
TypeError: __cinit__() got an unexpected keyword argument 'distributed'

That being said, the examples are also executed as part of the tests anyway, so you could remove them entirely from the CI.

So far unable to reproduce locally

Looks like the env. variable NO_DIST=1 worked for the tests, but arg --nodist didn't work for the examples:
Traceback (most recent call last):
  File "/home/vsts/work/1/s/sklearnex/examples/daal4py/naive_bayes_spmd.py", line 36, in <module>
    talgo = d4p.multinomial_naive_bayes_training(20, distributed=True)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "build/daal4py_cy.pyx", line 17656, in daal4py._daal4py.multinomial_naive_bayes_training.__cinit__
TypeError: __cinit__() got an unexpected keyword argument 'distributed'

That being said, the examples are also executed as part of the tests anyway, so you could remove them entirely from the CI.

@david-cortes-intel green now - but I see recent OneDAL PRs do not have this public CI failure - was something else changed to fix this?

Looks like the env. variable NO_DIST=1 worked for the tests, but arg --nodist didn't work for the examples:
Traceback (most recent call last):
  File "/home/vsts/work/1/s/sklearnex/examples/daal4py/naive_bayes_spmd.py", line 36, in <module>
    talgo = d4p.multinomial_naive_bayes_training(20, distributed=True)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "build/daal4py_cy.pyx", line 17656, in daal4py._daal4py.multinomial_naive_bayes_training.__cinit__
TypeError: __cinit__() got an unexpected keyword argument 'distributed'

That being said, the examples are also executed as part of the tests anyway, so you could remove them entirely from the CI.

@david-cortes-intel green now - but I see recent OneDAL PRs do not have this public CI failure - was something else changed to fix this?

No changes that I'm aware of. Odd that it just randomly failed for one specific PR that didn't touch the .yaml files.
Nevertheless, it wouldn't hurt to remove the custom run_examples.py from the pipelines here, considering that those are still getting executed through the pytest scripts.


Possibly a bad path on Linux

My son has been trying to run FortRise, but there seems to be an issue on Linux. This is the error that I am seeing when I select the "Launch TowerFall" button:
   at FortLauncher.Launcher.MenuButtons_LaunchTowerFall() in D:\Project\FNA Project\FortLauncher\Launcher\Widgets\MenuButtons.cs:line 127
System.ComponentModel.Win32Exception (8): An error occurred trying to start process '/home/mungus/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/TowerFall/TowerFall.exe' with working directory '/home/mungus/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/TowerFall'. Exec format error

My guess is that it is assuming an .exe file, but being Linux, that won't work. Other than the TowerFall.exe the path would be correct.

Use the new launcher called pyrgos. I am no longer maintaining the old launcher anymore.


Unicode error setup

I had the same issue than #65 while building with docker. Setting the locale didn't work for me, but another solution seems to use codecs.open() rather than the builtin open().

Coverage remained the same at 68.696% when pulling b36718fc4304ae36ad184c6386c3ca3e5bd5394c on browniebroke:unicode-error-setup into 48ff4f1049f67714a131c41a1dfd1598f6db97d6 on antonagestam:master.

Sorry for the long delay here, I'll merge this if you'd mind rebasing this? 🍰

Closing this since #65 seems fixed :)