ReactJS Invalid Hook Call

Current Situation
This error periodically shows client side and will completely break IDOM, but seems to fix itself if clearing browser cache. Something notable is I have never seen this issue when Django-IDOM was using idom==0.33.0, but that may just be coincidence.
This is the exception stack shown in browser console.
react-dom.js:8 Error: Minified React error #321; visit https://reactjs.org/docs/error-decoder.html?invariant=321 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at a (react.js:2:4779)
    at n.useState (react.js:2:6903)
    at react-bootstrap.js:2:44831
    at ql (react-dom.js:6:52870)
    at Uu (react-dom.js:6:60908)
    at gs (react-dom.js:10:10631)
    at ms (react-dom.js:10:933)
    at pf (react-dom.js:10:864)
    at Et (react-dom.js:10:724)
    at xi (react-dom.js:8:10854)
ai @ react-dom.js:8
react-dom.js:10 Uncaught Error: Minified React error #321; visit https://reactjs.org/docs/error-decoder.html?invariant=321 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at a (react.js:2:4779)
    at n.useState (react.js:2:6903)
    at react-bootstrap.js:2:44831
    at ql (react-dom.js:6:52870)
    at Uu (react-dom.js:6:60908)
    at gs (react-dom.js:10:10631)
    at ms (react-dom.js:10:933)
    at pf (react-dom.js:10:864)
    at Et (react-dom.js:10:724)
    at xi (react-dom.js:8:10854)
client.js:23649 The above error occurred in the <_ImportedElement> component:

    at _ImportedElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31103:29)
    at ImportedElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31075:28)
    at Element (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31046:20)
    at div
    at StandardElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31060:28)
    at Element (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31046:20)
    at Layout (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31034:19)

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://reactjs.org/link/error-boundaries to learn more about error boundaries.
logCapturedError @ client.js:23649
client.js:2691 Uncaught Error: Minified React error #321; visit https://reactjs.org/docs/error-decoder.html?invariant=321 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at a (react.js:2:4779)
    at n.useState (react.js:2:6903)
    at react-bootstrap.js:2:44831
    at ql (react-dom.js:6:52870)
    at Uu (react-dom.js:6:60908)
    at gs (react-dom.js:10:10631)
    at ms (react-dom.js:10:933)
    at pf (react-dom.js:10:864)
    at Et (react-dom.js:10:724)
    at xi (react-dom.js:8:10854)

Proposed Actions
Determine root cause and develop a solution.
I seem to be semi-frequently able to reproduce this if leaving my webserver running django-idom up while putting my Windows 10 machine to sleep for >12 hours.
See https://github.com/idom-team/idom/discussions/610 for the original discussion.
Work Items
See above.

It kind of looks like the error here is coming from react-bootstrap.js so it might be a problem there? At the very least, we could add an error boundary as the message says to prevent hard-crashes due to issues arising in imported components.

I'm also not really sure how to debug this at the moment.

Same here, not entirely certain how to tackle this one. Just wanted to make sure it's documented, we'll probably circle back around to this eventually.

I'm gonna close and kick back to discussion until there's something tangible to do. We can create a task for the error boundary though.

@rmorshea I've determined the root cause of this is an unpinned react bootstrap version.
bootstrap = idom.web.module_from_template(
    "react", "react-bootstrap", resolve_exports=True
)

This issue can easily be replicated by pinning to @2.1.1, loading a web page, then pinning to @2.1.2.
So this issue likely occurs only when my browser has a cached version of boostrap.js, and then a there happens to be an update to react-bootstrap.

I've had this issue happen again, despite pinned versions within module_from_template call. Not sure what the cause is this time.

What version of IDOM are you on?

@Archmonger can you update the trace on this when it happens? I think the client source in the problem area has changed since this was posted.

Will do once it happens again naturally. I haven't confirmed the breaking lines are the same when I force this issue to happen, only that the error code is identical.

I had it happen today, but this trace log seems slightly different.
react-dom.js:9 TypeError: Cannot read properties of null (reading 'useState')
    at r.useState (react.js:2:6860)
    at react-bootstrap.js:2:44649
    at Ri (react-dom.js:7:19047)
    at Hu (react-dom.js:9:10756)
    at Js (react-dom.js:9:45976)
    at Xs (react-dom.js:9:39741)
    at nf (react-dom.js:9:39672)
    at Fr (react-dom.js:9:39532)
    at lo (react-dom.js:9:36698)
    at en (react-dom.js:7:3242)
Yl @ react-dom.js:9
react-dom.js:7 Uncaught TypeError: Cannot read properties of null (reading 'useState')
    at r.useState (react.js:2:6860)
    at react-bootstrap.js:2:44649
    at Ri (react-dom.js:7:19047)
    at Hu (react-dom.js:9:10756)
    at Js (react-dom.js:9:45976)
    at Xs (react-dom.js:9:39741)
    at nf (react-dom.js:9:39672)
    at Fr (react-dom.js:9:39532)
    at lo (react-dom.js:9:36698)
    at en (react-dom.js:7:3242)
client.js:23649 The above error occurred in the <_ImportedElement> component:

    at _ImportedElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31225:29)
    at ImportedElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31202:28)
    at Element (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31076:20)
    at StandardElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31094:28)
    at Element (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31076:20)
    at StandardElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31094:28)
    at Element (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31076:20)
    at StandardElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31094:28)
    at Element (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31076:20)
    at Layout (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31060:19)

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://reactjs.org/link/error-boundaries to learn more about error boundaries.
logCapturedError @ client.js:23649
client.js:2691 Uncaught TypeError: Cannot read properties of null (reading 'useState')
    at r.useState (react.js:2:6860)
    at react-bootstrap.js:2:44649
    at Ri (react-dom.js:7:19047)
    at Hu (react-dom.js:9:10756)
    at Js (react-dom.js:9:45976)
    at Xs (react-dom.js:9:39741)
    at nf (react-dom.js:9:39672)
    at Fr (react-dom.js:9:39532)
    at lo (react-dom.js:9:36698)
    at en (react-dom.js:7:3242)

GIven the

@rmorshea Given that this is still happening with preact, do you have any ideas on the cause of this?
This is a major roadblock for using exported react packages.

The switch to Preact is unrelated (that just what IDOM uses internally). What matters is the module template which is still using React and I think it has to remain that way since any component library is going to import react and not preact. The only reason we're able to use preact in IDOM is because we use an alias.
With that said, I discovered that the material-ui examples in the docs broke because it was expecting a particular version of React (was seeing similar error messages to these). As of idom 0.39.0 you can specify module_from_template("react@the-version", ...). It looks like react-bootstrap is looking for 18.1.0 but the template is using the latest (18.2.0).

I am getting the same exception when using a pinned react version
bootstrap = idom.web.module_from_template(
<EMAIL_ADDRESS><EMAIL_ADDRESS>resolve_exports=True
)

react-dom.js:9 TypeError: Cannot read properties of null (reading 'useState')
    at n.useState (react.js:2:6785)
    at react-bootstrap.js:2:44649
    at Bi (react-dom.js:7:19481)
    at bu (react-dom.js:9:1575)
    at aa (react-dom.js:9:45971)
    at ua (react-dom.js:9:39715)
    at pf (react-dom.js:9:39646)
    at Ir (react-dom.js:9:39506)
    at co (react-dom.js:9:36651)
    at on (react-dom.js:7:3250)
bl @ react-dom.js:9
react-dom.js:7 Uncaught TypeError: Cannot read properties of null (reading 'useState')
    at n.useState (react.js:2:6785)
    at react-bootstrap.js:2:44649
    at Bi (react-dom.js:7:19481)
    at bu (react-dom.js:9:1575)
    at aa (react-dom.js:9:45971)
    at ua (react-dom.js:9:39715)
    at pf (react-dom.js:9:39646)
    at Ir (react-dom.js:9:39506)
    at co (react-dom.js:9:36651)
    at on (react-dom.js:7:3250)
client.js:23649 The above error occurred in the <_ImportedElement> component:

    at _ImportedElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31225:29)
    at ImportedElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31202:28)
    at Element (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31076:20)
    at StandardElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31094:28)
    at Element (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31076:20)
    at StandardElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31094:28)
    at Element (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31076:20)
    at StandardElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31094:28)
    at Element (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31076:20)
    at StandardElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31094:28)
    at Element (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31076:20)
    at StandardElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31094:28)
    at Element (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31076:20)
    at Layout (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31060:19)

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://reactjs.org/link/error-boundaries to learn more about error boundaries.
logCapturedError @ client.js:23649
client.js:14904 Uncaught TypeError: Cannot read properties of null (reading 'useState')
    at n.useState (react.js:2:6785)
    at react-bootstrap.js:2:44649
    at Bi (react-dom.js:7:19481)
    at bu (react-dom.js:9:1575)
    at aa (react-dom.js:9:45971)
    at ua (react-dom.js:9:39715)
    at pf (react-dom.js:9:39646)
    at Ir (react-dom.js:9:39506)
    at co (react-dom.js:9:36651)
    at on (react-dom.js:7:3250)
client.js:31312 IDOM WebSocket connection lost. Reconnecting in 1 seconds...
client.js:31277 WebSocket connection to 'ws://<IP_ADDRESS>:7575/idom/conreq._core.home.components.homepage/?kwargs=%7B%7D' failed:
mountLayoutWithReconnectingWebSocket @ client.js:31277
client.js:31312 IDOM WebSocket connection lost. Reconnecting in 3 seconds...
client.js:31282 IDOM WebSocket connected.
react-dom.js:9 Error: Minified React error #321; visit https://reactjs.org/docs/error-decoder.html?invariant=321 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at Object.X (react-dom.js:7:19215)
    at n.useState (react.js:2:6785)
    at react-bootstrap.js:2:44811
    at ji (react-dom.js:7:19036)
    at Zu (react-dom.js:9:10853)
    at sa (react-dom.js:9:46246)
    at ia (react-dom.js:9:39943)
    at ff (react-dom.js:9:39874)
    at Fr (react-dom.js:9:39734)
    at co (react-dom.js:9:36883)
ql @ react-dom.js:9
react-dom.js:7 Uncaught Error: Minified React error #321; visit https://reactjs.org/docs/error-decoder.html?invariant=321 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at Object.X (react-dom.js:7:19215)
    at n.useState (react.js:2:6785)
    at react-bootstrap.js:2:44811
    at ji (react-dom.js:7:19036)
    at Zu (react-dom.js:9:10853)
    at sa (react-dom.js:9:46246)
    at ia (react-dom.js:9:39943)
    at ff (react-dom.js:9:39874)
    at Fr (react-dom.js:9:39734)
    at co (react-dom.js:9:36883)
client.js:23649 The above error occurred in the <_ImportedElement> component:

    at _ImportedElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31225:29)
    at ImportedElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31202:28)
    at Element (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31076:20)
    at StandardElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31094:28)
    at Element (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31076:20)
    at StandardElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31094:28)
    at Element (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31076:20)
    at StandardElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31094:28)
    at Element (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31076:20)
    at StandardElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31094:28)
    at Element (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31076:20)
    at StandardElement (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31094:28)
    at Element (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31076:20)
    at Layout (http://<IP_ADDRESS>:7575/static/django_idom/client.js:31060:19)

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://reactjs.org/link/error-boundaries to learn more about error boundaries.
logCapturedError @ client.js:23649
client.js:2691 Uncaught Error: Minified React error #321; visit https://reactjs.org/docs/error-decoder.html?invariant=321 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at Object.X (react-dom.js:7:19215)
    at n.useState (react.js:2:6785)
    at react-bootstrap.js:2:44811
    at ji (react-dom.js:7:19036)
    at Zu (react-dom.js:9:10853)
    at sa (react-dom.js:9:46246)
    at ia (react-dom.js:9:39943)
    at ff (react-dom.js:9:39874)
    at Fr (react-dom.js:9:39734)
    at co (react-dom.js:9:36883)

Ironically, it seems like the issue is even worse now. I can't get my react-bootstrap exports to work at all now. Even after clearing cache, the issue persists.

Since I seem to be able to replicate this with 100% consistency now, I've configured the Conreq repo in a way that you can test this out on your side.

Pull down the archmonger/conreq@app_store branch from GitHub
pip install -r requirements.txt
python manage.py run_conreq
Remove the following return div(): https://github.com/Archmonger/Conreq/blob/633d79e0002bedcdb40d9e01bb1d60a0ba0af603/conreq/_core/home/components/modal.py#L29

Closing this in favor of #786


EPMLABSBRN-2299 [BE & FrontEnd] Refactoring: merge controllers StudyH…

…istoryController and StudyHistoryControllerV2 into one class
EPMLABSBRN-XX
Description:

This task is not only about backend - it is general task about front and back.
now this changes will broke the platform
so you need to find all usages of this end-points and change them too


Paul/docker rerun dir

Different ways of running pytest on my machine are yielding conflicting results; it succeeds in the IDE but fails in the command line with messages:
FAILED pytests/test_graphs_simple.py::test_sanity_pygraph_docker - pysmelt.subscribers.error_handler.SmeltErrEx: Executor failed to execute with error : expected value at line 1 column 1
FAILED pytests/test_graphs_simple.py::test_pygraph_docker_mac_addr - pysmelt.subscribers.error_handler.SmeltErrEx: Executor failed to execute with error : expected value at line 1 column 1
FAILED pytests/test_graphs_simple.py::test_pygraph_docker_ulimit - pysmelt.subscribers.error_handler.SmeltErrEx: Executor failed to execute with error : expected value at line 1 column 1

Not sure whether they should be failing or succeeding. Side note, the error is a little obscure and I have no idea where it comes from, some way of exposing the stack trace to the user would be good.


Update rename.py

update rename.py

Hey,
How tu puch

Hey,
How tu puch

I’m not sure I understand. Can you explain that again?


Don't re-run animation on every rerender

Fixes #73

I'm pretty sure I tried this and it had unintended consequences. Maybe I didn't try it, but I did spend several hours trying to fix this and I have to imagine this is one of the first things I tried.


[ARM] Fix #25510: az bicep: Set bicep.use_binary_from_path to false when installed using Azure CLI

Related command

az bicep

Description

The bicep.use_binary_from_path config has been recently introduced to using the bicep binary available in the path which is especially useful in CI environments where bicep is already available and prevent downloading it on every run.
But for customers that rely on az bicep install --version {} to install the bicep version of their choice, the default is still to use the one available from the CI environment, which broke customer builds as called out in this issue.
This PR includes changes that set the config value to false when az bicep install or az bicep upgrade is called, which allows subsequent az bicep commands to use the manually installed version, which is expected for customers calling this command. Also, there are changes which remove explicit checking for bicep installation in the publish, restore, and generate-params commands.
resolves #25510
Testing Guide

# Install latest bicep through other means and make sure it is in the path
az bicep version # Output should be that of the binary installed

az bicep install --version {} # Use a different version, say v0.3.1
az bicep version # Output should be that of the v0.3.1 binary installed

az config get bicep.use_binary_from_path # value should be false

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

@shenglol This is an extension to a change that you have made recently. Could you please review and let me know what you think? Thanks!

@PramodValavala-MSFT Thanks for the fix. I think changing the config to false when --version is specified makes sense. I just added one comment, but otherwise it looks good!

@zhoxing-ms for awareness

Seems this PR made trouble, to break our current Azure Pipeline.
https://github.com/Azure/azure-cli/issues/25710
We have to run a command
az config set bicep.use_binary_from_path=False

before az bicep install and az deployment commands.
@zhoxing-ms @yonzhan
will you rollback this change or make a fix on it? what's the plan?

@ozbillwang - there is a PR to fix the issue: https://github.com/Azure/azure-cli/pull/25729. We may need to roll out a hotfix for it once the PR is merged.


gobject-introspection: fix on darwin

Since the update of gobject-introspection from 1.46 to 1.48 in 39af1c76e12222ddf365cd3380ff36e7fc013e51, it fails to build on Darwin. A patch no longer applies. It seems that this patch is no longer needed; thus this commit removes it.
Things done

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

[ ] NixOS
[x] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

This does not actually delete the patch from the repo, is that intentional?


Fix lambdas. Fix set drive script. Implement resize storage.

Now lambdas works, it fully tested. Fixed small bag with set drive script. Also add resize for volume. Auto delete old snapshot for ami.

Cool. Could you pull in the changes I made yesterday and check they don't interfere with this PR?

Ok, changed.

i made some changes to the lambdas. Would be worth you pulling and taking a look.

Looks good, thanks for code review.


Add check for ELB certs and uploaded certs to IAM

Not really and an issue, but we have a similar cert checking script but it also checks:

All certs uploaded to IAM
A list of ELB that are using those certs.
I can send you the script if you are interested.
It's not lambda though...

Yeah that'd be awesome! My needs are mostly for CloudFront, but I'd be happy to try and add in parts from your script. :+1:

You bet!  here is my script. Feel free to take what you want to enhance your script! :)
#!/usr/bin/env python
import boto
import boto.ec2.elb
import os
import sys
from datetime import date
import subprocess

def say(s, banner=None):
    if banner is None:
        print(str(s))
    else:
        print(banner * 50)
        print(banner + str(s))
        print(banner * 50)
    sys.stdout.flush()

say("")
say("==============================")
say("Certificate expiration checker")
say("==============================")
say("")

# Create a mapping of {cert:[elbs]}
region = get_current_region()
conn = connect(boto.ec2.elb.connect_to_region, region_name=region)
all_elbs = conn.get_all_load_balancers()
elb_certs = {}
for elb in all_elbs:
    for listener in elb.listeners:
        if listener.ssl_certificate_id is not None:
            if listener.ssl_certificate_id in elb_certs:
                elb_certs[listener.ssl_certificate_id].append(elb.name)
            else:
                elb_certs[listener.ssl_certificate_id] = [elb.name]

# Now get all the certs that are registered with AWS:
conn = connect(boto.connect_iam)
allcerts=conn.list_server_certs().list_server_certificates_response.list_server_certificates_result.server_certificate_metadata_list
total = len(allcerts)
toolate = 0
stillgood = 0
soon = 0
today = date.today()

for i in allcerts:
    elbs = None
    if i.arn in elb_certs:
        elbs = elb_certs[i.arn]
    say("Server certificate ARN.: {0}".format(i.arn))
    say("Server certificate ID..: {0}".format(i.server_certificate_id))
    say("Server certificate name: {0}".format(i.server_certificate_name))
    say("Upload date............: {0}".format(i.upload_date))
    say("Expiration date........: {0}".format(i.expiration))
    say("ELBs that use this cert: {0}".format(elbs))

    year = int(i.expiration[0:4])
    month = int(i.expiration[5:7])
    day = int(i.expiration[8:10])
    exp = date(year, month, day)
    daysleft = exp - today
    say("Days until expiration: {0}".format(daysleft.days))
    if daysleft.days < 0:
        toolate += 1
        say("*** Already expired ***")
    elif daysleft.days < 30:
        soon += 1
        say("********************")
        say("* WILL EXPIRE SOON *")
        say("********************")
    else:
        stillgood += 1

    say("")

say("Found {0} certificates, {1} still good, {2} expiring within 30 days, and {3} already expired.\n".format(total, stillgood, soon, toolate))

if soon > 0:
    say("Some certificates are going to expire soon!")
    sys.exit(1)

if toolate > 0:
    say("Some certificates have expired and need to be deleted or replaced!")
    sys.exit(2)

say("No immediate action required.")
sys.exit(0)


Atom project lacks a way to submit positive feedback 😉

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
There is no obvious way to submit positive feedback to the Atom team. While every nit an deviation from well trodden paths (insert XKCD Workflow joke here) can be considered a regession or defect and thus be rightfully submitted as an issue, this cannot be said of the things done right by the Atom team.
Steps to Reproduce

Identify an aspect of development the Atom team shines in, like its thoroughly friendly professionalism in handling the flood of issue reports in the above mentioned categories, or its ability to steer the course among devs fluttering to the new shiny while actually investing in making code editing better (as exemplified by @maxbrunsfeld patiently and repeatedly educating people in the advantages of semantically consistent syntax highlighting versus the “lovin’ me bright lights” Xmas decoration approach);
Decide to formulate positive feedback to counter the issue bias;
Seek a less fleeting place to post it than the stream of consciousness discussion board.

Expected behavior: Find an obvious place to post your feedback.
Actual behavior: There is no such place. Post a silly OT issue instead.
Reproduces how often: Every. Single. Time.
Versions
Version independent.
Additional Information
This issue is not to be taken entirely seriously; however, the express and implied praise in it very much is. Cheers, and a Happy New Year to all whose calendar advances a year tonight.

Thanks @kopischke!  I guess you're right, there's no specific single place where we tell people to go if they have positive feedback to share.  When any of us do see positive feedback (whether it's in a message board post, the Atom Slack, a tweet, an email, etc.), we try to share it with each other so everyone gets to see it :smile:  I'll say that the discussion board and the Atom Slack are probably the best places for now though but I'll mention this to the team in case folks have other ideas.
Thanks again for the kind words and we hope you have a great 2019!


Fix installation error

Wanted to check this out after your comment, but installation seems to be broken:
(jl_d5jJvG) pkg> add https://github.com/tecosaur/CheckDoc.jl
     Cloning git-repo `https://github.com/tecosaur/CheckDoc.jl`
    Updating git-repo `https://github.com/tecosaur/CheckDoc.jl`
   Resolving package versions...
ERROR: Unsatisfiable requirements detected for package StyledStrings [f489334b]:
 StyledStrings [f489334b] log:
 ├─possible versions are: 1.0.0-1.0.1 or uninstalled
 └─restricted to versions 1.7.0-1 by CheckDoc [641849b3] — no versions left
   └─CheckDoc [641849b3] log:
     ├─possible versions are: 0.1.0 or uninstalled
     └─CheckDoc [641849b3] is fixed to version 0.1.0

I think this PR should fix it? Unless my registry is somehow refusing to update and v1.7 of StyledStrings actually exists somewhere

Ah yep, this was from pre-registration when I was testing a compat version of StyledStrings and had it down to Julia 1.7. I've got a fix for this and some other tweaks applied locally, if you don't mind I'll close your PR and just push them.
Many thanks for raising this though!

Should now work as of 37833de629348b388bbd80c5b059944bcfa8b06f :slightly_smiling_face:


'root' option causing output file to be blank (0 bytes)

Running clean-css v3.1.4 via Grunt with the root option enabled, causes the output file to be empty
    cssmin:
      vendor:
        options:
          root: './public'
          target: './public'
          advanced: false
        files:
          'assets/dist/vendor.min.css': [
            "#{libPath}/bootstrap/dist/css/bootstrap.min.css"
        ]

Running "cssmin:vendor" (cssmin) task
Verifying property cssmin.vendor exists in config...OK
Files: public/lib/bootstrap/dist/css/bootstrap.min.css -> assets/dist/vendor.min.css
Options: rebase=false, report="min", sourceMap=false, keepSpecialComments=0, root="./public", target="./public"
Reading public/lib/bootstrap/dist/css/bootstrap.min.css...OK
Writing assets/dist/vendor.min.css...OK
File assets/dist/vendor.min.css created 109.52 kB → 0 B

Done, without errors.

Removing the root option allows the file to be generated as expected (but without the functionality that root is supposed to provide, of course).
Any thoughts on this?

@andrewboni No idea. Would you be able to share your setup in a similar manner to https://gist.github.com/MarcBT/2a94d67e36cb634d5c7e or uploaded to Dropbox? You can always mail it to me too via email found in package.json.

@jakubpawlowicz sure thing. Setup is as follows:
Gruntfile.coffee
module.exports = (grunt) ->
  grunt.initConfig
    cssmin:
      vendor:
        options:
          root: './public'
          target: './public'
          advanced: false
        files:
          'assets/dist/vendor.min.css': [
            "#{libPath}/bootstrap/dist/css/bootstrap.min.css"
        ]
...

bootstrap.min.css
Standard bootstrap css file, found here
Running grunt cssmin:vendor outputs the following:
Running "cssmin:vendor" (cssmin) task
Verifying property cssmin.vendor exists in config...OK
Files: public/lib/bootstrap/dist/css/bootstrap.min.css -> assets/dist/vendor.min.css
Options: rebase=false, report="min", sourceMap=false, keepSpecialComments=0, root="./public", target="./public"
Reading public/lib/bootstrap/dist/css/bootstrap.min.css...OK
Writing assets/dist/vendor.min.css...OK
File assets/dist/vendor.min.css created 109.52 kB → 0 B

Done, without errors.

vendor.min.css ends up being a blank file. But, running the task without `root: './public' generates the file as expected. Hope this helps

@andrewboni Thanks, I'll take a look later today.

@andrewboni I may know what's going on with this setup:

adding root option sets a root path all passed files should be relative to
"#{libPath}/bootstrap/dist/css/bootstrap.min.css" resolves to public/lib/bootstrap/dist/css/bootstrap.min.css - see the output above
If you set root: './public' clean-css will try to resolve the path above as public/public/lib/bootstrap/dist/css/bootstrap.min.css, so if it stays empty it will be internally resolved to the current path, i.e. ..

Some side notes:

If you take a look at https://github.com/gruntjs/grunt-contrib-cssmin/blob/master/tasks/cssmin.js#L33 you'll see clean-css errors are not propagated up to grunt, only exceptions;
Actually grunt plugin reads the files but just because it reports file size changes, see https://github.com/gruntjs/grunt-contrib-cssmin/blob/master/tasks/cssmin.js#L42, and it does it after minification takes place.

I will open couple issues in their repo and I'm closing this issue for the time being.


[WIP]Add Help icon in Realm Screen

Some user friendly enhancement in the realm screen.
Needs suggestion , what to exactly add for help message in server URL?
Also what to use? A tooltip or an actionSheet to display the message?

I would look at what other services like Slack that have different URLs for different sites use to document this concept.

Yes, indeed. We should explore way more what other apps do.
My concerns about adding 'help' are two fold:

no one reads help
we need to translate all of these

This is definitely a problem that we need to improve.  We've had users email us asking what their "server URL" is when trying to figure out how to login.  But I agree we should see if we can make it more intuitive (e.g. changing the label) first.
I will note that Zulip has a particularly difficult challenge here compared to other apps, since we support any server URL, not just e.g. subdomain.example.com.  But I think we could probably do well with just showing the examples "zulip.example.com" and "organization.zulipchat.com" in the help.
We could also consider having a way to enter "_____.zulipchat.com" on this form, since that is a super common case.

I fully agree with the problem needs fixing and partially agree with the idea of how to fix it.
I suggest we conceptually separate the URL entering into 'officially hosted' servers and 'custom/own' servers, instead of actually offering the full URL hints (though of course, the solution under the hood is exactly the same)

We will soon merge a reworked Realm screen, and this icon will not be needed.


Analyzing Numerical Stability in Linear Registration

Title
Analyzing Numerical Stability in Linear Registration
Leaders
Yohan Chatelain, Tristan Glatard, Mina Alizadeh, Ines Gonzalez Pepe
Collaborators
No response
Brainhack Global 2023 Event
Brainhack Montreal
Project Description
This project explores the numerical reliability of the FSL FLIRT linear registration tool.
We aim to investigate how computational errors can affect the accuracy of this alignment tool.
In computers, real numbers are stored with limited precision, leading to tiny inaccuracies known as rounding errors. While often negligible, these errors can accumulate and potentially affect the outcomes in delicate processes like linear registration in neuroimaging.
This project aims to understand and mitigate these errors to improve the reliability of medical imaging analysis.
To evaluate numerical stability, we will employ Monte Carlo Arithmetic (MCA). This technique, a form of stochastic arithmetic, is designed to simulate rounding errors stemming from the finite precision of numbers in computing by using random variables. Tools like Verificarlo, Verrou, and Fuzzy support MCA and are useful in adapting C, C++, FORTRAN, and Python codes for this purpose. Specifically, we'll use Fuzzy-libm, a modified version of libm, which introduces random noise into basic mathematical operations such as exp, log, cos, sin, etc.
Project 1: Testing Numerical Stability in FSL FLIRT
We aim to test FSL FLIRT's stability under varying conditions, including images, degrees of freedom, and optimization parameters. The goal is to understand how these variables impact FSL FLIRT's performance. To do so, we use the Fuzzy-libm tool on FLIRT, experimenting with a range of input parameters.
Project 2: Development Assistance for Simplified Algorithm
Developing and testing a basic version of a registration algorithm.
This task is open to those interested in algorithm development and application, especially using SciPy.
Project 3: Examining Numerical Rounding Impacts
Delving into how numerical rounding affects accuracy in neuroimaging. The objective is to analyze the computational steps of linear registration to gain a deeper understanding of the numerical behaviour.
This project is suitable for participants interested in medical imaging, computational neuroscience, and software development, and is especially relevant for those looking to understand the practical implications of computational inaccuracies in scientific research.
Link to project repository/sources
GitHub repositories:

https://github.com/verificarlo/fuzzy
https://github.com/verificarlo/verificarlo
https://github.com/edf-hpc/verrou
https://git.fmrib.ox.ac.uk/fsl/flirt

Docker images:

Fuzzy-libm: verificarlo/fuzzy:v0.9.1-lapack
Fuzzy-python: verificarlo/fuzzy:v0.9.1-lapack-python3.8.5
Fuzzy-scipy: verificarlo/fuzzy:v0.9.1-lapack-python3.8.5-numpy-scipy
Verificarlo: verificarlo/verificarlo:latest
Verrou: https://github.com/edf-hpc/verrou/blob/master/docker/Dockerfile

Goals for Brainhack Global

Analyze FSL FLIRT numerical stability.
Develop a simplified registration algorithm.
Address and propose solutions for rounding issues.

Good first issues

Provide a dataset to run FSL FLIRT on.
Provide FSL FLIRT parameters to play with.
Set up and run initial tests with FSL FLIRT.
Help in the development of the simplified algorithm (SciPy implementation?).
Provide metrics to measure numerical stability on perturbed registered images.

Communication channels
https://mattermost.brainhack.org/brainhack/channels/numerical-stability-linear-registration
Skills

Python: Intermediate to Advanced
Familiarity with FSL or similar tools: Basic
Familiarity with stochastic arithmetic: Basic

Onboarding documentation
No response
What will participants learn?

linear registration in neuroimaging
stochastic arithmetic
numerical instability metrics
algorithm development
collaborative open-source project work.

Data to use
No response
Number of collaborators
4
Credit to collaborators
Project contributors are listed on the project README using all-contributors github bot.
Image
Leave this text if you don't have an image yet.
Type
other
Development status
0_concept_no_content
Topic
reproducible_scientific_methods
Tools
FSL
Programming language
Python
Modalities
MRI
Git skills
0_no_git_skills
Anything else?
No response
Things to do after the project is submitted and ready to review.

[ ] Add a comment below the main post of your issue saying: Hi @brainhackorg/project-monitors my project is ready!
[ ] Twitter-sized summary of your project pitch.

Hi @brainhackorg/project-monitors my project is ready!


Display trade-confirmations on Steam

Add an option to settings to display the confirmations right on steams website. Could be risky in terms of security - need to reevaluate this option. Low priority.

Lowering the priority due to not being as critical as refurbishing the app currently. I need to search for a secure approach, like Iframe. Problem with Iframe is that it either needs to be sandboxed and then communicates via special onmessage-listener or it must be secured in another way.


Introduce abstract base class breaking change into container registry

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

/azp run net - containerregistry - mgmt

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.ContainerRegistry


luci-app-sqm: fix missing interface in selection

Show device instead of interface in interface selection.
Fixes: #4539
Signed-off-by: Ansuel Smith<EMAIL_ADDRESS>

@hnyman

@tohojo

Thanks!


GOOD/THANK-YOU - and a general, serious, problem with duplications in compounds

GOOD/THANK-YOU is still not right

Looking first at the 2 examples of (1h)GOOD-THANK-YOU* associated with (1h)GOOD/THANK-YOU+MORNING but listed -- incorrectly -- under main entry (1h)GOOD/THANK-YOU:
There are two occurrences listed, ID numbers 9031 and 9028, but they both correspond to the same video (frames 622-760). These both correspond to the one video shown in the composite video. This one occurrence should be moved to main entry GOOD/THANK-YOU.

Looking next at the 6 occurrences shown of (1h)GOOD/THANK-YOU* associated with (1h)GOOD/THANK-YOU+(1h)MORNING but listed -- correctly -- under main entry GOOD/THANK YOU: There are 3 videos in the composite, but 6 occurrences shown from 3 different signers.  But in the listing of occurrences, the one video from Naomi is listed 4 times (i.e., there are 3 duplicates of Naomi that need to be removed). These ID numbers all correspond to the same video:  9025, 9022, 9019, and 9016.

For the 4 occurrences of (1h)GOOD/THANK-YOU* associated with (1h)GOOD/THANK-YOU+NIGHT, also listed -- incorrectly -- under main entry (1h)GOOD/THANK-YOU, there are 4 occurrences shown, but they correspond to only 2 different videos in the composite video, from 2 different signers (Liz and Naomi).  ID number 9034 is the example from Liz, but there are 3 copies of the example from Naomi:  9037, 9040, and 9043.  Two of the duplicates of Naomi should be removed, leaving a total of 2 examples, which should be moved under
main entry GOOD/THANK-YOU

So we should end up with the following (not including data in blue, coming only from continuous signing):
GOOD/THANK-YOU
    (1h)GOOD/THANK-YOU (29)
    (1h)GOOD/THANK-YOU* ((1h)GOOD/THANK-YOU+(1h)MORNING) (3)
    (1h)GOOD/THANK-YOU* ((1h)GOOD/THANK-YOU+MORNING) (1)
    (1h)GOOD/THANK-YOU* ((1h)GOOD/THANK-YOU+NIGHT) (2)
Next, looking at the listings of the compounds themselves, unsurprisingly the same
duplications found above are manifested in the compounds as well:

For the 3 examples of the compound (1h)GOOD/THANK-YOU+(1h)MORNING),
again, the 1 example with Naomi has 3 extra copies (ID numbers 9024, 9021, 9018, and 9015).  So the 6 total occurrences should be reduced to 3, 1 from each of the signers.

And we have the same problem as above with the compound (1h)GOOD/THANK-YOU+MORNING:  2 occurrences for the same one video of Liz (ID numbers 9027 and 9030).

Same for (1h)GOOD/THANK-YOU+NIGHT:  The same duplicates of Naomi mentioned above also need to be removed here. These three are all the same:  ID numbers 9033, 9042, 9039.

Unfortunately, the problem with duplications in compounds seems to be much more general.
Compare, for example, the composite video for ALWAYS+FOREVER_2 (1 video)
with the number of occurrences listed (2: including 1 duplicate). Exactly the same situation for:  ANSWER+AGENT, BAD+DREAM, BATH+DRESS/CLOTHES,
For BECOME+QUIET, there are 2 examples in the composite video, but 4 in the occurrences shown (1 of the videos has 2 extra copies).
For ADVISE/INFLUENCE+AGENT, there are 3 examples from 3 different signers in the composite, but only 2 signers (with 2 duplicates, to make 4 examples in all) in the occurrences.  So there are 2 extras and 1 missing (the male signer):

In a random check of compounds, I have found inconsistencies between the composite videos (essentially ground truth, except in the very few cases where we have made very recent changes) and the listings of occurrences...    (And the same problems are replicated in the listing of the compound parts, unsurprisingly; but I expect that fixing the compounds will also result in fixing the listings of their parts.)  There are duplications as well as missing occurrences.
SORRY to be the messenger about this!

Fixed


PyPy support

Are you planning to add support for PyPy? It seems that the current version of PyGLM is not compatible with it, I got a lot of compilation errors when trying to install via pip.

I've thought about adding support for PyPy, however when I looked into it more, I quickly found out that CPython and PyPy extensions are not really compatible (from what I've read here).
The way PyPy and CPython are written under the hood is so different that I might have to be required to rewrite the entire library. (which is currently about 36000 lines of code, if you don't count the macros and templates which would expand into about 10 times more lines).
Additionally, I've added a few specific tweaks that greatly increase PyGLMs performance, which (from what I understand) wouldn't be possible in PyPy, due to the way objects are handled.
I've never developed for PyPy, but I could give it a try.
Most likely though, a PyPy version is just not meant to be.

I tried to build it myself and couldn't find a way of getting it to run, unfortunately.
If you do not care about performance, you can use a very old version of PyGLM.
Your "best" choice would be PyGLM 0.2.1a1, which is the last version written in pure Python (though it uses numpy under the hood) or if you really need to go bare, you have to roll back all the way to PyGLM 0.1.0a1, which is the only version that is completely pure Python.
Keep in mind that either way you are going to loose performance as well as feature-completeness.
If you do care about performance, your only chance is to try using PyGLM 0.4.8a1, which was the last version written in C, which you might have better luck compiling with.


Building<EMAIL_ADDRESS>from source fails on Mojave

I was forced to try to build<EMAIL_ADDRESS>from source due to the icu4c update to v.67.1, but the build fails:
==> ./buildconf --force
==> ./configure<EMAIL_ADDRESS>--localstatedir=/usr/local/var --sysconfdir=/usr/local/etc/php/7.0 --with-config-file-path=/usr/local/etc/php/7.0 --with-config-file-scan-dir=/usr/local/etc/php/7.0/conf.d --with-pear=/usr/local/Cellar/php<EMAIL_ADDRESS>--enable-bcmath --enable-calendar
Last 15 lines from<EMAIL_ADDRESS>checking for WebPGetInfo in -lwebp... yes
checking for jpeg_read_header in -ljpeg... yes
checking for png_write_image in -lpng... yes
If configure fails try --with-xpm-dir=
checking for fabsf... yes
checking for floorf... yes
checking for GNU gettext support... yes
checking for bindtextdomain in -lintl... yes
checking for ngettext in -lintl... yes
checking for dngettext in -lintl... yes
checking for dcngettext in -lintl... yes
checking for bind_textdomain_codeset in -lintl... yes
checking for GNU MP support... yes
checking for __gmpz_rootrem in -lgmp... no
configure: error: GNU MP Library version 4.2 or greater required.
I checked and gmp seems to be installed properly:
gmp: stable 6.2.0 (bottled)
Any ideas?

Can confirm. No ideas.

Any news on this one?

It seems that this is not a Mojave issue after all; after upgrading to Catalina, I am facing the exact same issue while trying to build<EMAIL_ADDRESS>from source.

I would recommend checking out https://github.com/shivammathur/homebrew-php. I just found out about it but it as of now is actively maintained unlike exolnet's version here.

Hi!
Thank you for your interest in this repository. Unfortunately, this repository will now be archived with no further actions. We are sorry for the inconvenience.
Why are we closing this repository? This repository was only meant as a temporary measure, not a permanent one. Its only purpose was to ease the transition, considering that formulae from the homebrew-core tap are removed almost the day they became unsupported by the vendor. We needed a few more months to allow us to upgrade the code base of the various projects we have. But it was always with the intention of doing those upgrades, not by relying on a repository to keep old php versions artificially alive. We do not condone the use of deprecated software that could lead to serious security vulnerabilities.
Why are we not redirecting to another repository? Redirecting to another repository could be interpreted as an endorsement of said repository. If we were to do such a thing, we would not do it without vetting it first. And we do not wish to put the time and energy required in a vetting process of a third party repository. As the reason why a vetting process would be required, consider this. Before installing a software library on all our developer computers from an untrusted source, we would need to make sure that this software library is free from any malicious code (Trojan, ransomware, etc.), both in the repository itself and in the packaged binaries (the homebrew bottles, if any).
Thank you for your understanding.

Hi!
Thank you for your interest in this repository. Unfortunately, this repository will now be archived with no further actions. We are sorry for the inconvenience.
Why are we closing this repository? This repository was only meant as a temporary measure, not a permanent one. Its only purpose was to ease the transition, considering that formulae from the homebrew-core tap are removed almost the day they became unsupported by the vendor. We needed a few more months to allow us to upgrade the code base of the various projects we have. But it was always with the intention of doing those upgrades, not by relying on a repository to keep old php versions artificially alive. We do not condone the use of deprecated software that could lead to serious security vulnerabilities.
Why are we not redirecting to another repository? Redirecting to another repository could be interpreted as an endorsement of said repository. If we were to do such a thing, we would not do it without vetting it first. And we do not wish to put the time and energy required in a vetting process of a third party repository. As the reason why a vetting process would be required, consider this. Before installing a software library on all our developer computers from an untrusted source, we would need to make sure that this software library is free from any malicious code (Trojan, ransomware, etc.), both in the repository itself and in the packaged binaries (the homebrew bottles, if any).
Thank you for your understanding.


question about the keypoints numbers of representation model's input

Why the representation model's input is 17 keypoints? Is it possible to pretrain a 26 keypoints( include the heel and foot big toe such as halpe) version?  Because the angle of foot is important in some videos. or where the code should be changed if i want to pretrain a 26 keypoints or more version.

@simplaj were you able to include the feet keypoints? It is much needed


New function to remove deprecated STIX objects

Hi Roberto,
While we were busy with adding support for sub-techniques in DeTT&CT we noticed that we needed to get rid of STIX objects that are deprecated. In our particular case, these were old techniques which are no longer used in the latest release of ATT&CK. I have therefore added a new function based on the already existing function remove_revoked. The new function remove_deprecated removes any objects which have the STIX property 'x_mitre_deprecated' set to true
I think it would be of value to add this to attackcti.
Regards,
Marcus

Thank you very much @marcusbakker !! I appreciate it. I would like to hear more about how you guys are handling the sub-techniques update. I will merge this and push a quick fix to the version.

Regarding the handling of the sub-techniques. Not sure if you have any questions in particular? But, we were pleased that no real changes were required in the functionality of attackcti. If that was the case, also no big deal of course as we can provide back the changes that we did via PRs. Basically, sub-techniques are just techniques with a different number within the CTI data of ATT&CK :-). So, that helped a lot.
To help users with the migration of YAML files in DeTT&CT we made heavy use of the crosswalk.json file provided by MITRE. We created some new logic and guidance to help the user to migrate their files/mappings the most efficient. Still, it can be an annoying exercise, but it has to be done.
We dropped support for any old techniques. They can still be used in some areas, but not everywhere. We also did not re-mapped any published ATT&CK mappings (like the one for CrowdStrike, Red Canary, etc.). That's almost impossible to do because we do not have access to the raw data that tells us how it should be mapped into sub-techniques.
No idea if this answers your question :-).

That's awesome @marcusbakker ! Thank you very much for taking the time to write those details. Yes that helped. I am happy to hear that there were no real changes required in the functionality of attackcti. I was working on another project and I was setting up some time to take a look at it a little bit deeper. Thank you again! I hope you enjoy the rest of your week :)

I'm happy tot help. Also enjoy the rest of your week over there too!


Frontend: Implement storing of encrypted passwords

This is a little bit related with our thoughts about security

@akuleshov7 as far as I understand, this one will never be done, as we are not planning to store passwords. If I am wrong, please reopen an issue

@akuleshov7 as far as I understand, this one will never be done, as we are not planning to store passwords. If I am wrong, please reopen an issue

it's about Git repository and we ask to provide credentials for private repo.
User can provide token instead of password. But still we store it in database


Support for geoip

Basically this includes moving the geoip support from our "old" internal project to lumbermill.
Consider geolite vs geolite2 since logstash seems to be using v2.

Fixed, https://github.com/sonyxperiadev/lumber-mill/tree/master/lumbermill-geospatial


Dev

Checkout dev branch
python3 setup.py install --user
module load openmpi/gnu
nohup python3 batch.py --dry-run > pr473.log &

testing in progress

Recombinants aren't being displayed:

Related to change made in 4f74df1286699b4934fc1f4ccfb24c26bdfdcbc7

Checking the following:

[ ] Search

[ ] Search by accession number
[ ] Search by lineage
[ ] Search by country
[ ] Search by country (with date filter)

[ ] Tree filtering
[ ] Download Time-scaled tree (nwk)
[ ] Download Time-scaled tree (csv)
[ ] Download Beadplot (svg)
[ ] Download Beadplot (nwk)
[ ] Download mutation list (csv)
[ ] Beadplot cutoff slider
[ ] Expanding Beadplot
[ ] Translated pages
[ ] Changing the colour of the tree based on divergence, collection date, etc.
[ ] Left/Right arrow key to move between beads
[ ] Tooltips
[ ] Countries/Samples/Mutations tabs are populating the correct information
[ ] Toggle for displaying recombinants

Unit tests are failing:
  11 passing (1m)
  3 failing

  1) Search Interface
       Searching 'China' results in selection and expected point count:
     AssertionError: Timed out retrying after 10000ms: Expected to find element: `.selectionH`, but never found it.
      at Context.eval (webpack:///./cypress/e2e/covizu.spec.cy.js:93:30)

  2) Search Interface
       Clicking the next button highlights the correct bead:
     TypeError: Cannot read properties of undefined (reading '0')
      at Context.eval (webpack:///./cypress/e2e/covizu.spec.cy.js:101:90)

  3) Search Interface
       Clear button resets search interface and cluster selection:
     CypressError: Timed out retrying after 10050ms: `cy.click()` failed because this element is `disabled`:

Unit test did not timeout when re-running the tests

Uncaught ReferenceError: Driver is not defined
    at HTMLDivElement.click (covizu.js:46:22)
    at HTMLButtonElement.<anonymous> (jquery-ui.min.js:11:4603)
    at HTMLButtonElement.dispatch (jquery.js:5429:27)
    at elemData.handle (jquery.js:5233:28)

To reproduce:

Click es to navigate to the Spanish translated page
Click on Tour rapido

Uncaught DOMException: Failed to execute 'querySelector' on 'Document': '.lines#India-UT-VCSGGIMS&R-VCSG416285' is not a valid selector.
    at Object.select (http://localhost:8001/js/d3.js:1689:34)
    at SVGLineElement.<anonymous> (http://localhost:8001/js/beadplot.js:752:30)
    at SVGLineElement.<anonymous> (http://localhost:8001/js/d3.js:1526:16)

To reproduce:

Open the BA.2.75.5 beadplot
Hover over the vertical line connecting the India/UT-VCSGGIMS&R-VCSG416274 and India/UT-VCSGGIMS&R-VCSG416285 beads

Can we deactivate the tests that are affected by the sporadic timeout issue, and run them manually with each PR?


Adding support for custom network namespace in the gateway operator

Description
Supporting the creation and configuration of a new network namespace for the gateway operator. The idea is to move the gateway pod in host network. In order to not put the iptables configuration in the node's namespace a new one is created. In the custom network namespace we put all the liqo configuration such as vpn tunnel and iptables rulespecs.
Fixes #(issue)
How Has This Been Tested?
Unit tests have been written for all the new functions.

/merge


support tree menu

support tree menu

hi @wmb0412 , can you please post a detailed description of your exact requirements?

closing due to inadequate decription


Fix an issue when a empty PS file is opened

@EricMSFT @AndreSayreMSFT @Microsoft/poshtools

looksgood


Try to inform user if .dockstore.yml is invalid

Is your feature request related to a problem? Please describe.
When trying to create (or transform) a workflow via GitHub apps, it's difficult to determine if it fails because there's an issue with Dockstore or because the user incorrectly formatted the .dockstore.yml.
Describe the solution you'd like
It'd be nice for the user to know their .dockstore.yml is invalid
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Sprint: Backlog
┆Issue Number: DOCK-1320

Should hook up error to validation framework so that workflow developer can tell that there is a syntax error

This has some overlap with https://github.com/dockstore/dockstore/issues/3239 and https://github.com/dockstore/dockstore/issues/3238. Definitely something that is needed for 1.9.0

Also doesn't show the .dockstore.yml on dev.dockstore.net today, might be in a different ticket

This is due to https://github.com/dockstore/dockstore-ui2/pull/963. It changed the Dockstore.yml workflows to use the old file component, which doesn't show dockstore.yml. I must've missed this when I was reviewing the PR.

Context, and I might have mis-remembered, there was an error in the number of spaces or tabs used in the .dockstore.yml for a demo. This would catch that level of error, not an error that #3239 would catch (something terribly wrong with lambdas)

After putting more thought into this I don't think we can easily inform users whether or not a dockstore.yml is invalid.
So if a dockstore.yml file is an invalid format, there will be a DockstoreYamlException and we would not be able to grab the workflow/service to associate with the dockstore.yml (can't assume no name field). So we don't know which entries on dockstore to associate the dockstore.yml with. If there is a space/tabs issue as @denis-yuen mentioned above, then it is invalid yml that we cannot parse, so we have no idea what entries it is associated with.
The only errors we can easily display are the following:
For services, we can display for validations whether or not a file in the file array exists. This already works.
For workflows, we could validate whether the primary descriptor exists and also whether the test files are present.
We cannot do the validation of YML format until we add the table that keeps track of lambda calls.

can't assume no name field

Are there more trade-offs to this than creating a potentially "extra" Dockstore entry with no name field?

It could also associate it with a workflow not using github apps (would this migrate it from full to dockstore.yml, not sure).
I think we should just get started on the error handling stuff for lambdas very soon since it is going to be important.

It could also associate it with a workflow not using github apps (would this migrate it from full to dockstore.yml, not sure).

I think that would be reasonable.

I think we should just get started on the error handling stuff for lambdas very soon since it is going to be important.

Ideally, yes. Practically, I doubt we can squeeze it into 1.9

@denis-yuen For now I'm going to add error handling for the .dockstore.yml in the situation where the primary descriptor doesn't exist or a test parameter file doesn't exist. While this isn't handling structural YML validation, it could still surface more common errors.
The version will now be added even if these files are not found, and will have validation messages (saying primary descriptor doesn't exist or test param file is missing). Previously no version was added if the primary descriptor was not found.

Note there will need to be some front end changes related to https://github.com/dockstore/dockstore/issues/3430. Will we keep the TRS endpoints for the front end or will we use custom endpoints?

Not sure, so thinking it through the issue in #3430 is that if there is no descriptor, we can't tell what language the workflow is in when there is no .dockstore.yml. However, looking at the TRS standard it appears that the descriptor_type is an array for multiple languages, it could be empty if
we do pursue the road of returning something for the two cases of:
a) a blank workflow with no .dockstore.yml
b) a blank workflow with a .dockstore.yml but broken or corrupt with no references to other descriptors
Here, we want to tell the user about errors in their .dockstore.yml which might be corrupt, formatted incorrectly, etc.
Are .dockstore.yml files currently returned by TRS and what file_type do they get?
https://github.com/ga4gh/tool-registry-service-schemas/blob/develop/openapi/ga4gh-tool-discovery.yaml#L502

They are returned only if there is a descriptor file present. The file type of the dockstore.yml is OTHER and it is returned.

So it seems that if we want to use TRS to debug invalid/corrupt .dockstore.yml without any associated descriptors. We will need to relax that and somehow infer/ignore language.
Alternatively, use a proprietary endpoint (which may not exist yet).
Might be able to add something under https://dockstore.org/api/static/swagger-ui/index.html#/extendedGA4GH to preserve the same id and version format.
/api/ga4gh/v2/extended/tools/{id}/versions/{version_id} for example

I think we could technically add a new descriptor type of ./dockstore.yml but that feels a bit hacky.

I think the ./dockstore.yml is too dockstore-specific that we should just use proprietary endpoint.  mapping the dockstore SourceFile object to TRS ToolFile has always been a pain.

So it seems like we should change the dockstore.yml workflows and services to use the non-TRS file viewer and instead use the existing proprietary (might need small tweaks).


Modified test instructions feature

Fixed Issues
#22043
Files Changed
TestConductRepository.cs-Changed feature to check category names which contain only question
TestConductRepositoryTest.cs-Added etst case for not valid testlink instructions details
instruction.component.ts-Added checking for not negative sign
instruction.html-Binded sign in html
Checks

[X] Naming Conventions
[x] Server side code comments (proper English, grammar and no spelling mistakes)
[x] Client side code comments (proper English, grammar and no spelling mistakes)
[x] Unused variables, methods, blank spaces and name spaces.
[x] Optimal Code and code formatting
[x] Commit History is proper, no merge is done.
[x] Commit/pull request messages should be proper to justify your feature
[x] All test cases are executed provided by tester.

Known Issues
N/A
Comments
N/A

This change is

SonarQube analysis reported 1 issue

 1 minor

Watch the comments in this conversation to review them.


rough shapes implemented

closes #787
you can adjust roughness and stroke width of those shapes too!
shapes with roughness 0 look like computerized shapes

- I have participated in GSSOC and CrossWoC

⚠⚠⚠⚠⚠⚠
@smaranjitghose Fill option is not yet implemented. It will come through my next PR for #777
there will be various options to modify fill appearance too!


Only add visible sonos devices

Description:
A SonosDevice is now created for all discovered sonos devices, but this fails for devices that do not have a media renderer. For me it happens because of a SUB player (which is paired with a playbar), but I would think it also applies to e.g bridges.
The soco.discover() method used further down in setup_platform handles filtering out such devices by default.

Looks good :dolphin:


Infinite spinner on cancelling Stronghold password while creating an account

Issue description
While creating an account (for software profiles), if you "Cancel" the Stronghold popup asking for your password, Firefly will be slightly stuck with the infinite spinner.
Firefly version
1.2.0 and developer
OS details
MacOS (Catalina 10.15.7)
Can the issue be reliably reproduced?
Yes
Steps to reproduce the issue

Create an account within a software profile with Stronghold locked
Click "Cancel" instead of entering your password

You should see the spinner still spinning towards the bottom left of the screen.
Expected behaviour
The state should resume normally if the user cancels the Stronghold password.
Actual behaviour
Firefly gets stuck, infinitely spinning for that button.
Errors
No response

Fixed in: https://github.com/iotaledger/firefly/pull/1209


Switch to Qiskit Ecosystem theme

The main changes are:

Gets rid of the top Qiskit nav bar.
Adds the project name and Qiskit Ecosystem logo to the left sidebar. (You can disable the logo or replace it with your own)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2559

Relevant Lines:
2821

💛  - Coveralls


Add flag to skip javadocJar in MavenJar publication

We run some internal tests against the output of publishMavenJavaPublicationTotestPublicationLocalRepository. These tests do not require the javadoc jar, but it takes about 20% of the build time. We can skip building them with -x javadocJar but then publish fails. This change adds a flag so publish does not fail. I don't like adding flags like this (feels like mvn all over again!) so I would love better ideas.
I want someone who does not work for Google to evaluate how much they dislike this flag.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[n/a] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[n/a] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Why not rewrite the build file on import?

Rewriting build files is super fragile compared to passing a parameter.

I agree that if it were really a totally weird Google thing we'd have to. But in this case it is vaguely, maybe, sorta useful for someone. And anyhow at least it says what it does on the box.

But given this feedback I'm willing to kick the can down the road with a simple rewrite. It won't break until someone gives BeamModulePlugin an overhaul, and by then maybe things will be different.

Through this conversation, I'm convinced enough that adding warts to BeamModulePlugin is actually worse than the rewrite on import. I don't like either option ;_;
Thanks for questioning.


Display error in status bar

The inline tooltip is really good. Anyway, if you are writing code and stop in the middle of a line and the autocomplete tooltip pops up, overlaps the linter one. What about an option to display the current error (in the line where the cursor is) in the status bar as a single line of text?

We already have that option, search for Line Tab in linter configuration :)

Thanks for the quick response @steelbrain !
I saw that options but what about displaying the error inline into the status bar instead of stacking them up on top of it?

I am not sure if I understand that :sweat_smile:

What I would like to see is the errors into the status bar as a single line of semicolon sepparated strings:

In the example, we should see "X 2 issues: E030 - Expected an identifier and instead saw ']', at line 45 col 5; E019 - Unmatched...", displaying as much text as fits into the status bar.

Sorry man, but bottom status bar space comes at a premium
We have already had our share of criticism after putting those 3 buttons there, showing issues there is just insane IMO :)

I can hear voices saying "SublimeLinter does exactly that" but, anyway, thanks @steelbrain! AtomLinter is just GREAT!!

SublimeLinter does that because that's its only available option, not because they wanted to. It was only recently that Sublime had the capacity for tooltips or anything else like that, yet another instance where Atom has blown far past Sublime.
Also remember that whatever is done here it needs to scale. Putting the message there might work for 1-2 issues, but what about thousands? (I've opened terrible old code with 1.9k issues myself...)

Thanks for the insights @Arcanemagus. I completely agree with you. And related to the scenario you mentioned, does the linter limit the number of issues that are displayed at once, and avoid filling the whole screen from bottom to top with them? There is no options to to that in the settings page.

It limits them (except for on a few broken themes, but there are other issues on that), it looks like to ~6.5 on my screen (and theme). The rest are accessible via the scrollbar.

Thanks again!


Ignore files/folders from intellisense

VSCode Version: 1.48.0
OS Version: macos 10.14.6

In our app repo we have a lot of generated database files which get regenerated. These files are tracked in git and are huge (thousands of lines of code). It seems like every time i regenerate these files my vscode intellisense slows to a crawl. When i try to cmd-click jump to definition it is stuck loading for 60 seconds. Same with snippet suggestions not popping up. This continues until i follow https://github.com/microsoft/vscode/issues/71751#issuecomment-480126916 and delete those caches and restart code. I think this means that those caches are full of all the changing autogenerated code instead of the files I am actually writing in.
Is there a way to ignore tracking of files in intellisense?

/needsMoreInfo
Please use this guide to provide more information: https://github.com/Microsoft/vscode/wiki/Performance-Issues. Thanks.

It seems like the tsserver is taking a lot of cpu
    0       33   68474           electron_node typingsInstaller.js typesMap.js ```

Please use this guide to provide more information: https://github.com/Microsoft/vscode/wiki/Performance-Issues. Thanks.

Do you have a tsconfig/jsconfig? Have you ensured the generated files are not included in those projects?
Also, does this reproduce in the latest VS Code insiders build with all extensions disabled?

Potentially related: https://github.com/microsoft/TypeScript/issues/36035

@mjbvz We do not have a jsconfig in the project, but maybe adding one with include/excludes might help this issue. Also it doesn't happen every time the files are generated so it is hard to reproduce consistently

Were you able to try adding a jsconfig and configuring it to include only the files that are part of your JS project?


lighthouse support

Thanks @mstoller for including lighthouse option (+@paulirish). This is awesome!
Just merged, fixed tests, bumped version and published to NPM.
Enjoy ;-)


Docker pulls the ROSM mirror and reports an error

Docker pulls the ROSM mirror to report the following error：
docker: unknown server OS: .

Hi @gp1322719830
Thanks for reaching out.
For better understanding of problem, can you please share the steps you followed.
Please share all steps to reproduce the problem.
Thank you.

Hi @gp1322719830
Thanks for reaching out.
For better understanding of problem, can you please share the steps you followed.
Please share all steps to reproduce the problem.
Thank you.

sudo docker pull rocm/tensorflow:latest

Hi @gp1322719830
Thanks for reaching out.
For better understanding of problem, can you please share the steps you followed.
Please share all steps to reproduce the problem.
Thank you.

sudo docker pull rocm/tensorflow:latest
sudo docker run -it -v $HOME:/data --privileged --rm --device=/dev/kfd --device=/dev/dri --group-add video rocm/tensorflow:latest
error:
docker: unknown server OS: .

Hi @gp1322719830
I am not able to reproduce this problem.
I have a Ubuntu 20.04.2 machine with Vega10 card in it.
I just did sudo docker run -it -v $HOME:/data --privileged --rm --device=/dev/kfd --device=/dev/dri --group-add video rocm/tensorflow:latest and docker image was pulled.
Digest: sha256:dcd14d6f1c3328eb90a0c1dd71b1693e6a98b68b6597617b88c0af3acabea91d
Status: Downloaded newer image for rocm/tensorflow:latest
root@2baf14b37d2a:/root#
Looks like its the problem with your machine and I guess issue is specific to this kernel. Can you please try on a different machine and a different kernel and update.
Thank you.

Hi @gp1322719830
I am not able to reproduce this problem.
I have a Ubuntu 20.04.2 machine with Vega10 card in it.
I just did sudo docker run -it -v $HOME:/data --privileged --rm --device=/dev/kfd --device=/dev/dri --group-add video rocm/tensorflow:latest and docker image was pulled.
Digest: sha256:dcd14d6f1c3328eb90a0c1dd71b1693e6a98b68b6597617b88c0af3acabea91d
Status: Downloaded newer image for rocm/tensorflow:latest
root@2baf14b37d2a:/root#
Looks like its the problem with your machine and I guess issue is specific to this kernel. Can you please try on a different machine and a different kernel and update.
Thank you.

Solved,thanks!


add clippy and rust_dev to pre-commit

I presume the reasoning for not including clippy in pre-commit was that it passes all files. This can be turned off with pass_filenames, in which case it only runs once.
cargo +nightly dev generate-all is also added (when excluding target is does not give false positives).
(The overhead of these commands is not much when the build is there. People can always choose to run only certain hooks with pre-commit run [hook] --all-files)

Happy to add this if helpful though I admittedly don't use pre-commit!


no log? I start the docker and nothing happen.

I check the log file :/var/lib/docker/containers/a9572ee726a5ca500857f03eae9a9078df707f164457006d0e9accca5c6da776/a9572ee726a5ca500857f03eae9a9078df707f164457006d0e9accca5c6da776-json.log
and there is nothing.

Maybe log file is generated in the docker container...
Please refer to #16, I plan to use stdout instead of the log file in the next release.

V1.5 is released, now stdout is the default log output.
You can use docker logs to get it.
Please refer to https://github.com/TimothyYe/godns/releases/tag/V1.5


Update DirectionsRenderer

Hi guys,
I am using the sample code from the docs for the DirectionsRenderer on a map. My problem here is that when I have an update to latitude/longitude props, the map doesn't update with the new directions. I'm pretty sure this is because in the sample code, it is calling componentDidMount() and that does not get recalled when it gets re-rendered. How could I change the sample code so that everytime there is a new change coming in from props, the map will change with the new directions?
Here is my DirectionsRenderer code:
const MapWithADirectionsRenderer = compose(
    withProps({
        googleMapURL: "https://maps.googleapis.com/maps/api/js?key=AIzaSyDkOgKW9d-YxAC_8kar8EZ-aL90qazdSNc&v=3.exp&libraries=geometry,drawing,places",
        loadingElement: <div style={{ height: `100%` }} />,
        containerElement: <div style={{ height: `400px` }} />,
        mapElement: <div style={{ height: `100%` }} />,
    }),
    withScriptjs, withGoogleMap,
    lifecycle({
        componentDidMount() {
            this.setState({
                onDirectionChange: () => {
                    const DirectionsService = new google.maps.DirectionsService();
                    DirectionsService.route({
                        origin: new google.maps.LatLng(this.props.latitude, this.props.longitude),
                        destination: new google.maps.LatLng(this.props.destLatitude, this.props.destLongitude),
                        travelMode: google.maps.TravelMode.DRIVING,
                    }, (result, status) => {
                        if (status === google.maps.DirectionsStatus.OK) {
                            this.setState({
                                directions: result
                        });
                    } else {
                        console.error(`error fetching directions ${result}`);
                    }
                    });
                }
            });
            const DirectionsService = new google.maps.DirectionsService();
            DirectionsService.route({
                origin: new google.maps.LatLng(this.props.latitude, this.props.longitude),
                destination: new google.maps.LatLng(this.props.destLatitude, this.props.destLongitude),
                travelMode: google.maps.TravelMode.DRIVING,
            }, (result, status) => {
                if (status === google.maps.DirectionsStatus.OK) {
                    this.setState({
                        directions: result
                });
            } else {
                console.error(`error fetching directions ${result}`);
            }
            });
        },
    }),
)(props =>
    <GoogleMap
        defaultZoom={7}
        defaultCenter={new google.maps.LatLng(37.3352, -121.8811)}
    >
    <TrafficLayer autoUpdate />
    {props.onDirectionChange()}
    {props.directions && <DirectionsRenderer directions={props.directions} />}
    </GoogleMap>
);

In the componenetDidMount, this.props.latitude and this.props.longitude are passed in from a parent component and those values get changed when a user selects a new location from a searchbox. How could I make it so that when the user selects a new location, the map will be re-rendered with the new directions?
Thanks!

#949


[rewrite] Add pending test for keyed element update bug

After implementing the fix @pygy suggested in #1278, I discovered a render bug with keyed elements. The vdom updates fine, but the actual dom itself becomes empty.
In the PR'd test, the very last assertion is failing. I found the bug in my project when clicking between tabs in the ui.

Fixed in 730c96041698e74cfbcf4d705cbe95b28adc1776


Make lib compatible to 8 MHz MCP2515-boards

Include changes made here https://github.com/peppeve/CAN_BUS_Shield to use boards with 8 instead of 16 MHz oscillator.

I just updated my changes to be based on latest Seeed and peppeve 8Mhz version + my own improvements. You can find it on https://github.com/ttlappalainen/CAN_BUS_Shield
I'll also try to make pull to Seeed.

Look awesome, thanks for sharing.


How to get aligned 16bit depth image and color image

Hello,
I use this code to get 16bit depth image and its corresponding aligned color image
import pyrealsense2 as rs
import numpy as np
import cv2
pipeline = rs.pipeline()
config = rs.config()
config.enable_stream(rs.stream.depth, 640, 480, rs.format.z16, 30)
config.enable_stream(rs.stream.color, 640, 480, rs.format.bgr8, 30)
profile = pipeline.start(config)
depth_sensor = profile.get_device().first_depth_sensor()
depth_scale = depth_sensor.get_depth_scale()
print("Depth Scale is: " , depth_scale)
clipping_distance_in_meters = 0.5 #1 meter
clipping_distance = clipping_distance_in_meters / depth_scale
align_to = rs.stream.color
align = rs.align(align_to)
try:
while True:
frames = pipeline.wait_for_frames()
aligned_frames = align.process(frames)
aligned_depth_frame = aligned_frames.get_depth_frame() # aligned_depth_frame is a 640x480 depth image
color_frame = aligned_frames.get_color_frame()
if not aligned_depth_frame or not color_frame:
continue
depth_image = (np.asanyarray(aligned_depth_frame.get_data()))
color_image = np.asanyarray(color_frame.get_data())
grey_color = 153
depth_image_3d = np.dstack((depth_image,depth_image,depth_image)) #depth image is 1 channel, color is 3 channels
bg_removed = np.where((depth_image_3d > clipping_distance) | (depth_image_3d <= 0), grey_color, color_image)
    depth_colormap = cv2.applyColorMap(cv2.convertScaleAbs(depth_image, alpha=0.03), cv2.COLORMAP_JET)
    images = np.hstack((bg_removed, depth_colormap))
    cv2.namedWindow('Align Example', cv2.WINDOW_AUTOSIZE)
    cv2.imshow('Align Example', images)
    cv2.imwrite("depth.png",depth_image)
    cv2.imwrite("color.png",color_image)
    key = cv2.waitKey(1)
    if key & 0xFF == ord('q') or key == 27:
        cv2.destroyAllWindows()
        break

finally:
pipeline.stop()
the depth image I get is as foolows:

I use a software "imagej" to see the depth value, as follows:

the depth value are several hundreds to three thousands or so. which is very small. what's the matter? I think the depth value has been shrinked. how to get the depth image that has the real depth value?

[ ]


Architecture as Code - Working Group Meeting - Tuesday 27 Feb 2024

Date
Tuesday 27 Feb 2024 - 11:00 EST / 16:00 UK
Untracked attendees

Name
Firm
Comment

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[x] Convene, roll call, welcome new people
[x] Approve previous meeting minutes - https://github.com/finos/devops-automation/issues/175
[x] Update on new JSON Meta Schema & Vocabulary for CALM (@rocketstack-matt )
[x] Demo of using the new schema to model TraderX (@rocketstack-matt )
[x] Developing reusable architecture patterns (@jpgough-ms)
[ ] Demo of advanced schema validation using Spectral (@willosborne)
[ ] Demo of a sample CALM visualizer (@aidanm3341)
[ ] Proposal for E2E solution based on TraderX (@matthewgardner)
[ ] Save the Date! Onsite Accelerator in London (@ojeb2)
[ ] AOB, Q&A & Adjourn (5mins)

Decisions Made

[ ] Decision 1
[ ] Decision 2
[ ] ...

Action Items

[ ] Action 1
[ ] Action 2
[ ] ...

Zoom info
Join Zoom Meeting

https://zoom.us/j/94904595244
Meeting ID: 949 0459 5244
Passcode: 545224
Find your local number: https://zoom.us/u/aesEqmNODb

Github Repo: https://github.com/finos/devops-automation/
Project Board: https://github.com/orgs/finos/projects/33
Mailing List: Email<EMAIL_ADDRESS>to subscribe to our mailing list

Karl Moll / FINOS

Matthew Bain / Morgan Stanley

Matthew Auburn / Morgan Stanley

Will Osborne / Morgan Stanley

Jim Gough / Morgan Stanley

:wave: :shipit: Eddie Knight / Sonatype

Aidan McPhelim / Morgan Stanley

Attila Mihaly / Morgan Stanley

Prashant Jasani / Morgan Stanley

Alex Armstrong / Morgan Stanley

Matthew Gardner/Morgan Stanley

Louis Paul / Prudential

From my demo

The issue for background: https://github.com/finos-labs/architecture-as-code/issues/11
The pattern: https://github.com/finos-labs/architecture-as-code/blob/main/calm/pattern/api-gateway.json
The instantiation of the pattern: https://github.com/finos-labs/architecture-as-code/blob/main/calm/samples/api-gateway-implementation.json

Yan Tordoff / Morgan Stanley

Denis Coffaro / Morgan Stanley

As mentioned at the end of the call, we plan to run a second onsite accelerator courtesy of @ojeb2, please reply to this issue - https://github.com/finos/devops-automation/issues/185 - if you would like to attend.

Miguel Gasca / Morgan Stanley

FINOS Meeting: February 27, 2024
Commenced: 11:05 EST
Introduction / FINOS Disclaimer: Completed
Previous minutes approved by attendees and closed out (Issue 175) : Approved
Matthew Bain : Schema walkthrough and refactoring
TraderX walkthrough
JSON schema and auto populate of required files, e.g. nodes, relationships
Jim Gough : How do we model a pattern using the CALMS schema
API example and value of including the JSON schema
Will Osbourne : Validation process extended to structural analysis
Spectral to lint API specs and define
Definitions in YAML
Spectral demo with custom definitions
Aidan McPhelim: TraderX example visualization
Right click on object to get properties
Matthew Gardner: Manifest to Infrastructure
- Terraform Run - Infrastructure
- YAML deployment configs - Application
Comments/Feedback:
Make more consistent with C4 visualization – Yan Tordoff
Make it use C4 and looking at good things from C4 and incorporate – Yan Tordoff
Maybe a “C4 mapper” feature – Matt Bain
Contributions should be forked and not branched
Changes to specifications will be a formal/agreed process
Position on language standards
Adjourned: 12:02 EST

Approved in #189


Slugified ToC Links

Description
This redesigns the toc with slugified links rather than using ascending numbers.
Issues
This does not solve a more general problem with the TOC that you cannot navigate to anchor links from off page becuase the ids are generated after the page loads
Checklist

[ ] For UI or styling changes, I have added a screenshot or gif showing before & after
[x] I have added a changeset
[ ] I have added to the docs where applicable
[ ] I have added to the VS Code extension where applicable

closing in favour of #1806


Tag naming / checking

Having just started adding my package to the package list, I was looking at the existing tags to see which were most appropriate.  I found a lot of duplication.  A few examples from the start of the alphabet:

"2d", "2D"
"authentication", "authenticator"
"algorithm", "algorithms"
"app", "application"
"benchmark", "benchmarking"
"bind", "binding", "bindings"
"Bloom", "Bloom filter"

The list goes on (and even includes "Nim", "nim" and "nimrod"!)...
If these tags are ever selected as the means of trying to search/filter packages, it's going to be very hard to actually find anything useful I suspect.

Stemming and case insensitive searches are not rocket science... I don't see any problems here.

PRs to clean up tags are always welcome!

At the very least, can "nim" and "nimrod" be removed as tags? They're rather pointless as every package is going to involve Nim anyway.

Sure
On Monday, 29 August 2016, Adam Chesak<EMAIL_ADDRESS>wrote:

At the very least, can "nim" and "nimrod" be removed as tags? They're
rather pointless as every package is going to involve Nim anyway.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nim-lang/packages/issues/399#issuecomment-243021190,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPDezZY0qQkqrLcIaV1gK425xzrc1gfks5qkkkagaJpZM4JmfYM
.


Update jboss-invocation to 1.3.1.Final

Windows Build 1077 is now running using a merge of 67dce1d40fb7557abeaca0cab181a32a0cb9a39a

Linux Build 1410 is now running using a merge of 67dce1d40fb7557abeaca0cab181a32a0cb9a39a

Core - Full Integration Build 662 is now running using a merge of 67dce1d40fb7557abeaca0cab181a32a0cb9a39a

Windows Build 1077 outcome was SUCCESS using a merge of 67dce1d40fb7557abeaca0cab181a32a0cb9a39a
Summary: Tests passed: 3067, ignored: 64 Build time: 0:19:14

Linux Build 1410 outcome was FAILURE using a merge of 67dce1d40fb7557abeaca0cab181a32a0cb9a39a
Summary: Execution timeout (new); tests passed: 2707, ignored: 49; org.wildfly.core:wildfly-core-testsuite-domain Build time: 0:45:03
Build problems:
Execution timeout
Process exited with code 137

Core - Full Integration Build 662 outcome was FAILURE using a merge of 67dce1d40fb7557abeaca0cab181a32a0cb9a39a
Summary: Tests failed: 39 (39 new), passed: 2789, ignored: 412 Build time: 0:50:05
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).failoverOnStop: <no details avaliable>

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).nestedBeanFailover: <no details avaliable>

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).connectionFactoryFailover: <no details avaliable>

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).jmsConnectionFactoryFailover: <no details avaliable>

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).noFailover: <no details avaliable>

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).simpleFailover: <no details avaliable>

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulTimeoutTestCase(SYNC-tcp).timeout: <no details avaliable>

org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase(SYNC-tcp).testBasicXPC: <no details avaliable>

org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase(SYNC-tcp).testSecondLevelCache: <no details avaliable>

org.jboss.as.test.clustering.cluster.ejb.remote.RemoteFailoverTestCase(SYNC-tcp).testSecureStatelessFailover: <no details avaliable>

org.jboss.as.test.clustering.cluster.ejb.remote.RemoteFailoverTestCase(SYNC-tcp).testStatelessFailover: <no details avaliable>

##### there are 29 more failed tests, see build details

retest this please

Windows Build 1081 is now running using a merge of 67dce1d40fb7557abeaca0cab181a32a0cb9a39a

Linux Build 1413 is now running using a merge of 67dce1d40fb7557abeaca0cab181a32a0cb9a39a

Core - Full Integration Build 666 is now running using a merge of 67dce1d40fb7557abeaca0cab181a32a0cb9a39a

Linux Build 1413 outcome was SUCCESS using a merge of 67dce1d40fb7557abeaca0cab181a32a0cb9a39a
Summary: Tests passed: 3067, ignored: 64 Build time: 0:19:01

Windows Build 1081 outcome was SUCCESS using a merge of 67dce1d40fb7557abeaca0cab181a32a0cb9a39a
Summary: Tests passed: 3067, ignored: 64 Build time: 0:19:09

Core - Full Integration Build 666 outcome was SUCCESS using a merge of 67dce1d40fb7557abeaca0cab181a32a0cb9a39a
Summary: Tests passed: 2828, ignored: 412 Build time: 0:48:45


How can I use this template with cordova?

How can I use this template with cordova? I tried to separate out this folder in the cordova projects www folder but it did not work. The cordova www folder has plain js/css/html and I would like to use this template instead.

It is not the template, all templates are here http://framework7.io/templates/

But I want to use this one as a template. Is it possible?

Put content of kitchen-sink/core into cordova project www folder

so you mean create a project with cordova create helloWorld and replace the content inside www with kitchen-sink/core from the framework7 core?


20699: Create glue enrollment actions to process non-cobra re-instates

Field
Value

Redmine Ticket Number
20699

App-Dev Road Map #
n/a

Start Date
n/a

Due Date
n/a

App-Dev Priority
UP-Disqueued

Development Story Points
n/a

Peer Review Story Points
n/a

Ticket Author
@TreyE

It has been merged to the reinstate branch.


[Security Plugin] Consolidate tests for security dashboards plugin

Problem: There are two folders semi-related to security dashboards plugin - security-dashboards-plugin and security. It seems like release time testing only uses security folder, but github runner actions are running both. We should consolidate these to match the release time behavior, and transfer any tests that are applicable.

Catch All Triage - 1 2 3 4 5 6


yarn test gets broken when I install antd package in my project. wat?! o_O

Is this a bug report?
Yes
Did you try recovering your dependencies?
Yes
Which terms did you search for in User Guide?
Troubleshoting section npm test hangs on macOS Sierra  didn't help me.
Environment

node -v: v9.8.0

npm -v: 5.6.0

yarn --version (if you use Yarn): 1.5.1

npm ls react-scripts (if you haven’t ejected<EMAIL_ADDRESS>

Operating system: macOS Sierra 10.13.3

Browser and version (if relevant): Google Chrome 64.0.3282.186

Steps to Reproduce

npx create-react-app demo
cd ./demo
yarn
yarn test (...and all works fine)
yarn add antd
yarn test (...and there is an error)

Expected Behavior
All must work fine. Because it's nonscence when installing some library have influence to environment.

Actual Behavior
Got an error:

@DexterHD I've had this problem in the past and am currently trying to remember the cause and how I solved it. The steps you've provided do not  reproduce the error for me. Is there anything else you've done to the demo app (e.g. adding Typescript or a different version of jest manually)? posting your package.json may help

@rpalermodrums I have read this guide but there is nothing about tests and/or watcher problems, so here is my repository witch doesn't work (https://github.com/DexterHD/create-react-app-issue-4131), but if I remove antd all works fine.
Maybe I have some problems with my environment but I have no idea what works wrong. :(
Also my collegue tried to reproduce it on linux, but on linux all works fine. I have read it can be some kind of problem with watchman (I found it by googling), but i don't use it so it different problem.
I also tried to use create-react-app-antd but it fails with this stack listed below.
yarn install v1.5.1
info No lockfile found.
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning "antd ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.1".
warning "antd ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.1".
warning "antd > react-slick ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "react-app-rewire-less ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^3.0.0 || ^4.0.0".
[4/4] 📃  Building fresh packages...
[-/3] ⢀ waiting...
[-/3] ⢀ waiting...
[3/3] ⢀ fsevents<EMAIL_ADDRESS>| darwin | x64
[-/3] ⢀ waiting...
warning Error running install script for optional dependency: "/Users/dexter/Projects/go/src/gitlab.com/hiteam/create-react-app-antd/node_modules/react-scripts/node_modules/fsevents: Command failed.
Exit code: 1
Command: sh
Arguments: -c node install
Directory: /Users/dexter/Projects/go/src/gitlab.com/hiteam/create-react-app-antd/node_modules/react-scripts/node_modules/fsevents
Output:
node-pre-gyp info it worked if it ends with ok
node-pre-gyp info using<EMAIL_ADDRESS>node-pre-gyp info using<EMAIL_ADDRESS>| darwin | x64
node-pre-gyp info check checked for \"/Users/dexter/Projects/go/src/gitlab.com/hiteam/create-react-app-antd/node_modules/react-scripts/node_modules/fsevents/lib/binding/Release/node-v59-darwin-x64/fse.node\" (not found)
node-pre-gyp http GET https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.2/fse-v1.1.2-node-v59-darwin-x64.tar.gz
node-pre-gyp http 404 https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.2/fse-v1.1.2-node-v59-darwin-x64.tar.gz
node-pre-gyp ERR! Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.2/fse-v1.1.2-node-v59-darwin-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v59 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp http 404 status code downloading tarball https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.2/fse-v1.1.2-node-v59-darwin-x64.tar.gz
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| darwin | x64
gyp info ok
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| darwin | x64
gyp ERR! configure error
gyp ERR! stack Error: Python executable \"/usr/local/bin/python\" is v3.6.4, which is not supported by gyp.
gyp ERR! stack You can pass the --python switch to point to Python >= v2.5.0 & < 3.0.0.
gyp ERR! stack     at PythonFinder.failPythonVersion (/usr/local/Cellar/node/9.8.0/libexec/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:492:19)
gyp ERR! stack     at PythonFinder.<anonymous> (/usr/local/Cellar/node/9.8.0/libexec/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:474:14)
gyp ERR! stack     at ChildProcess.exithandler (child_process.js:265:7)
gyp ERR! stack     at ChildProcess.emit (events.js:180:13)
gyp ERR! stack     at maybeClose (internal/child_process.js:936:16)
gyp ERR! stack     at Socket.stream.socket.on (internal/child_process.js:353:11)
gyp ERR! stack     at Socket.emit (events.js:180:13)
gyp ERR! stack     at Pipe._handle.close [as _onclose] (net.js:538:12)
gyp ERR! System Darwin 17.4.0
gyp ERR! command \"/usr/local/Cellar/node/9.8.0/bin/node\" \"/usr/local/Cellar/node/9.8.0/libexec/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js\" \"configure\" \"--fallback-to-build\" \"--module=/Users/dexter/Projects/go/src/gitlab.com/hiteam/create-react-app-antd/node_modules/react-scripts/node_modules/fsevents/lib/binding/Release/node-v59-darwin-x64/fse.node\" \"--module_name=fse\" \"--module_path=/Users/dexter/Projects/go/src/gitlab.com/hiteam/create-react-app-antd/node_modules/react-scripts/node_modules/fsevents/lib/binding/Release/node-v59-darwin-x64\"
gyp ERR! cwd /Users/dexter/Projects/go/src/gitlab.com/hiteam/create-react-app-antd/node_modules/react-scripts/node_modules/fsevents
gyp ERR! node -v v9.8.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute 'node-gyp configure --fallback-to-build --module=/Users/dexter/Projects/go/src/gitlab.com/hiteam/create-react-app-antd/node_modules/react-scripts/node_modules/fsevents/lib/binding/Release/node-v59-darwin-x64/fse.node --module_name=fse --module_path=/Users/dexter/Projects/go/src/gitlab.com/hiteam/create-react-app-antd/node_modules/react-scripts/node_modules/fsevents/lib/binding/Release/node-v59-darwin-x64' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/Users/dexter/Projects/go/src/gitlab.com/hiteam/create-react-app-antd/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:180:13)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:936:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
node-pre-gyp ERR! System Darwin 17.4.0
node-pre-gyp ERR! command \"/usr/local/Cellar/node/9.8.0/bin/node\" \"/Users/dexter/Projects/go/src/gitlab.com/hiteam/create-react-app-antd/node_modules/react-scripts/node_modules/fsevents/node_modules/.bin/node-pre-gyp\" \"install\" \"--fallback-to-build\"
node-pre-gyp ERR! cwd /Users/dexter/Projects/go/src/gitlab.com/hiteam/create-react-app-antd/node_modules/react-scripts/node_modules/fsevents
node-pre-gyp ERR! node -v v9.8.0
node-pre-gyp ERR! node-pre-gyp -v v0.6.39

It's strange because I didn't have watchman installed, but this helps me:
https://github.com/react-community/create-react-native-app/issues/281#issuecomment-313813657

Closing since resolved per previous comment.