[Server] Remove extraneous kubeopenapi-json related error log

Current Behavior
The following error should not be logged while kubeopenapi-json is running and in the process of generating components.
ERRO[2022-03-27T09:48:18-05:00] Kubernetes config is not initialized with Meshery  app=meshery code=1001 probable-cause= severity=2 short-description="Kubernetes client not initialized" suggested-remediation="Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized"

Acceptance Tests

This error is not logged while kubeopenapi-json is actively running.
This error should not continue to be logged after kubeopenapi-json has completed its task.

Contributor Guides and Resources

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

Ping, ping.

@Revolyssup was this removed? Point to the PR?

@Revolyssup was this removed? Point to the PR?

https://github.com/meshery/meshery/pull/5698


Revert "Replace --whole-archive with --start-group"

Reverts electron/brightray#228.
Closes https://github.com/electron/electron/issues/6178.
It is causing crashes on Linux.

@zcbenz Are you sure #228 is the reason for https://github.com/electron/electron/issues/6178? My build of Electron 1.2.4 on Linux works fine, and I've been using that patch even before it was merged.

@tensor5 Yeah I'm sure, not all Linux distributions are affected by this, but for those do, reverting this change can fix the crash.


Line numbers missing in C# stack traces

It seems C# is compiled without debug support so the line numbers in the stack traces are missing:

Latest commit should fix this, will close this issue once it is deployed.

This may take some time to deploy since upstream changes have broken some aspects of the build system.

Seems to be working now, thanks!

Only took me a month ;)


Interpreter: fix some conversion primitives

For some reason 6 specs were failing locally on my machine. I don't know why these didn't fail on CI, but from my side it was a bit annoying. And thinking about it, it was done in an incorrect way.
This fixes them by introducing specialized primitives that don't perform intermediate conversions.

💭 Maybe we are missing some more specs that convert from floats to integers, especially near or at the min/max boundaries.
If anyone wants to do that, please go ahead! 🙏


mdx docker codeblock

I'd like to have installation instructions run "live", so that we can regression test our installation instructions in RWO and ocaml.org.
For that, we would need to have some way to redirect a codeblock into docker.  E.g. something like:
# apk add --update opam
# opam init -ya
# opam install rwo

And have that execute the commands and fill them in.

The use case is to test their output only ?
Or should it be able to run commands in an other block in the same environment ?
Or even OCaml code ? (This requires a lot of work)
Also, downloading an image and initializing opam will take a very long time and commands that can run automatically may be different than commands run by users. (eg. -y --quiet)
So if this is the main use case, wouldn't it be better to test that somewhere else than in the build of rwo ? (Eg. in a global CI run for every ocaml releases)

All good questions -- I had in mind that this would run less often than other tests.  It would be useful to be able to classify some mdx blocks with a tag, and only run those tags (e.g. this could be an install tag in the block).
The usecase is to test their output only.  We have installation instructions for >10 distros now, so automating it is extremely useful, especially to see when they start failing.  The output could be considered nondeterministic, as with benchmarks.


Send debugging telemetry to the backend

Depends on https://github.com/akitasoftware/akita-libs/pull/142.

This PR just focuses on whether the client was healthy on startup.  I'll look at continuous telemetry in a future PR.


Updates to IPsec/IKE Policy Howtos

Changes incorporated for:

Matching IPsec/IKE algorithms and Diffie-Hellman group names from VPN FAQ
Added instructions on dead peer detection to PowerShell guide
Removing deprecated SKUs (Standard/High Performance)

Learn Build status updates of commit 2aa4494:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/vpn-gateway/ipsec-ike-policy-howto.md
:white_check_mark:Succeeded

articles/vpn-gateway/vpn-gateway-ipsecikepolicy-rm-powershell.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@cherylmc,
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#reassign:deeharris-23

Reading back through some of changes I made to the docs, I thought of a more efficient approach. My PR hard-codes information from azure-docs/blob/main/includes/vpn-gateway-faq-ipsecikepolicy-include.md rather than using the include directly. I will revise my changes and resubmit.
#please-close


Improve cron job logging

We get no notification that a cron job has failed.

Any update @inglesp ?


Uncaught exception in http request.

Just had an uncaught exception in http request:
25 Nov 23:25:00 - TypeError: Cannot read property 'handleStatus' of undefined
    at delegateStatus (/usr/src/node-red/node_modules/node-red/red/runtime/nodes/flows/index.js:196:47)
    at Object.handleStatus (/usr/src/node-red/node_modules/node-red/red/runtime/nodes/flows/index.js:205:9)
    at HTTPRequest.Node.status (/usr/src/node-red/node_modules/node-red/red/runtime/nodes/Node.js:267:11)
    at IncomingMessage.<anonymous> (/usr/src/node-red/node_modules/node-red/nodes/core/io/21-httprequest.js:186:26)
    at emitNone (events.js:72:20)
    at IncomingMessage.emit (events.js:166:7)
    at endReadableNT (_stream_readable.js:921:12)
    at nextTickCallbackWith2Args (node.js:442:9)
    at process._tickCallback (node.js:356:17)

Flow is pretty complex so difficult to post but perhaps there's a check that could be done ?

No need to share the whole flow, but could you describe where you have any http request nodes? Are they in subflows? Are you nesting subflows in subflows? Things like that.
What version of node-red?

Here's the actual subflow with the http requests:
[
    {
        "id": "3f16b37f.87e2a4",
        "type": "subflow",
        "name": "NetBooterHttp",
        "info": "# netBooter control\n\nThis subflow will take the following commands as a string:\n\n- `on n`  Switches outlet n on where n is outlet number\n- `off n`  Switches outlet n off where n is outlet number\n- `on *`  Switches all outlets on\n- `off *`  Switches all outlets off\n- `reboot n`  Reboots outlet n where n is outlet number\n- `stats`  Returns the outlets status as a JSON object\n\nIP address of the netBooter should be set as `msg.host` before the sublow.",
        "in": [
            {
                "x": 60,
                "y": 160,
                "wires": [
                    {
                        "id": "204807bb.40b01"
                    }
                ]
            }
        ],
        "out": [
            {
                "x": 1460,
                "y": 220,
                "wires": [
                    {
                        "id": "a8dcded9.7b681",
                        "port": 1
                    },
                    {
                        "id": "6b8b3263.2a9814",
                        "port": 0
                    }
                ]
            },
            {
                "x": 920,
                "y": 280,
                "wires": [
                    {
                        "id": "3ee848cd.40c398",
                        "port": 0
                    }
                ]
            }
        ]
    },
    {
        "id": "3ee848cd.40c398",
        "type": "http request",
        "z": "3f16b37f.87e2a4",
        "name": "",
        "method": "GET",
        "ret": "txt",
        "url": "http://{{host}}/cmd.cgi?{{code}} {{arg1}} {{arg2}}",
        "tls": "",
        "x": 410,
        "y": 160,
        "wires": [
            [
                "3ad92432.a50df4"
            ]
        ]
    },
    {
        "id": "204807bb.40b01",
        "type": "function",
        "z": "3f16b37f.87e2a4",
        "name": "commandDispatch",
        "func": "msg.operation = msg.payload;\n\nvar code;\nvar arg1;\nvar arg2;\n\nif (msg.payload === \"stats\") {\n    msg.code = \"$A5\\r\";\n    return msg;\n}\n\nvar inputCode;\nvar inputArg;\n\nif (msg.payload.includes(\"on\") || msg.payload.includes(\"off\") || msg.payload.includes(\"reboot\")) {\n    inputCode = msg.payload.split(' ')[0];\n    inputArg = msg.payload.split(' ')[1];\n}\n\nif (inputCode === \"on\" || inputCode === \"off\") {\n    msg.code = \"$A3\";\n    msg.arg1 = inputArg;\n    \n    if (inputCode === \"on\") msg.arg2 = 1;\n    if (inputCode === \"off\") msg.arg2 = 0;\n    \n    if (msg.arg1 === \"*\") {\n        msg.code = \"$A7\";\n        msg.arg1 = msg.arg2;\n        msg.arg1 = null;\n    }\n}\n\nif (inputCode === \"reboot\") {\n    msg.code = \"$A4\";\n    msg.arg1 = inputArg;\n}\n\nreturn msg;",
        "outputs": 1,
        "noerr": 0,
        "x": 210,
        "y": 160,
        "wires": [
            [
                "3ee848cd.40c398"
            ]
        ]
    },
    {
        "id": "3ad92432.a50df4",
        "type": "function",
        "z": "3f16b37f.87e2a4",
        "name": "parse",
        "func": "String.prototype.reverse=function(){return this.split(\"\").reverse().join(\"\");}\n\nvar str = msg.payload;\n\nif (str.startsWith(\"Error\")) {\n    return;\n}\n\nif (str === '$A0\\r\\n\\r\\n') {\n    msg.payload = msg.operation;\n    return msg;\n}\n\nif (msg.operation == 'stats') {\n    msg.stats = {};\n    msg.stats.outlets = [];\n    \n    var date = new Date();\n    msg.stats.date = {\n        raw : date,\n        local: date.toLocaleString(),\n        epoch: date.getTime(),\n        offset: -(date.getTimezoneOffset() / 60),\n    };\n    \n    var args = str.split(',');\n    var returnCode = args[0];\n    \n    msg.stats.acCurrentDraw1 = parseFloat(args[2]);\n    msg.stats.acCurrentDraw2 = parseFloat(args[3]);\n    \n    var outlets_string = args[1].reverse();\n    \n    for (var _outlet in outlets_string)\n    {\n        var outlet = {};\n        outlet.port = parseInt(_outlet) + 1;\n        outlet.name = \"Outlet \" + outlet.port;\n        if (outlets_string[_outlet] === \"1\") {\n           outlet.powered = true;\n           msg.stats.outlets.push(outlet);\n        }\n        if (outlets_string[_outlet] === \"0\") {\n           outlet.powered = false;\n           msg.stats.outlets.push(outlet);\n        }\n        \n    }\n    \n    msg.topic = msg.topic + '/stats';\n    \n    if (msg.stats.outlets.length) {\n        return msg;\n    }\n}\n",
        "outputs": 1,
        "noerr": 0,
        "x": 590,
        "y": 160,
        "wires": [
            [
                "a8dcded9.7b681"
            ]
        ]
    },
    {
        "id": "a8dcded9.7b681",
        "type": "switch",
        "z": "3f16b37f.87e2a4",
        "name": "",
        "property": "operation",
        "propertyType": "msg",
        "rules": [
            {
                "t": "eq",
                "v": "stats",
                "vt": "str"
            },
            {
                "t": "else"
            }
        ],
        "checkall": "true",
        "outputs": 2,
        "x": 750,
        "y": 160,
        "wires": [
            [
                "5946c078.88f6a8"
            ],
            []
        ]
    },
    {
        "id": "5946c078.88f6a8",
        "type": "http request",
        "z": "3f16b37f.87e2a4",
        "name": "getNames",
        "method": "GET",
        "ret": "txt",
        "url": "http://{{host}}",
        "tls": "",
        "x": 950,
        "y": 100,
        "wires": [
            [
                "2bfdd5ae.042832"
            ]
        ]
    },
    {
        "id": "2bfdd5ae.042832",
        "type": "html",
        "z": "3f16b37f.87e2a4",
        "name": "",
        "tag": "#display table tr",
        "ret": "html",
        "as": "single",
        "x": 1140,
        "y": 100,
        "wires": [
            [
                "95c3cfc2.c8426"
            ]
        ]
    },
    {
        "id": "95c3cfc2.c8426",
        "type": "function",
        "z": "3f16b37f.87e2a4",
        "name": "getNames",
        "func": "var outletRegex = /^\\d+<\\/td>\\s/;\n\nfor (var i in msg.payload)  {\n    if (outletRegex.test(msg.payload[i])) {\n        var outlet = parseInt(msg.payload[i].split('')[1].replace('	', ''));\n        var name = msg.payload[i].split('')[4].replace('	\\n\\t\\t', '');\n        msg.stats.outlets[outlet-1].name = name;\n    }\n}\n\nreturn msg;",
        "outputs": 1,
        "noerr": 0,
        "x": 1330,
        "y": 100,
        "wires": [
            [
                "7e42f7c4.20e19"
            ]
        ]
    },
    {
        "id": "7e42f7c4.20e19",
        "type": "http request",
        "z": "3f16b37f.87e2a4",
        "name": "getAC",
        "method": "GET",
        "ret": "txt",
        "url": "http://{{host}}/status.xml",
        "tls": "",
        "x": 1490,
        "y": 100,
        "wires": [
            [
                "e90f85b8.656898"
            ]
        ]
    },
    {
        "id": "e90f85b8.656898",
        "type": "xml",
        "z": "3f16b37f.87e2a4",
        "name": "",
        "attr": "",
        "chr": "",
        "x": 1660,
        "y": 100,
        "wires": [
            [
                "6b8b3263.2a9814"
            ]
        ]
    },
    {
        "id": "6b8b3263.2a9814",
        "type": "function",
        "z": "3f16b37f.87e2a4",
        "name": "getAC",
        "func": "//node.warn(msg.stats);\n//node.warn(msg.payload);\n\nvar response = msg.payload.response;\n\nfor (var item in response) {\n    if (item.startsWith('ac') && response[item][0] !== \" \") {\n        var index = parseInt(item[2]) + 1;\n        var readings = response[item][0].split(\" - \");\n        var acCurrentDraw = parseFloat(readings[0]);\n        var maxDetectedAmps = parseFloat(readings[1]);\n        msg.stats[`acCurrentDraw${index}`]= acCurrentDraw;\n        msg.stats[`maxDetectedAmps${index}`]= maxDetectedAmps;\n    }\n}\nmsg.payload = msg.stats;\nreturn msg;",
        "outputs": 1,
        "noerr": 0,
        "x": 1800,
        "y": 100,
        "wires": [
            []
        ]
    },
    {
        "id": "6b6d2ea.4e039d",
        "type": "subflow:3f16b37f.87e2a4",
        "z": "4521bf6a.e8ac58",
        "name": "",
        "x": 580,
        "y": 320,
        "wires": [
            [
                "388b5e5f.5a8eb2"
            ],
            [
                "62a739.0b8d20c8"
            ]
        ]
    }
]

It's with node-red 0.15.2

It's seems to happen mostly when we deploy, if it doesn't fail after deploy it's usually stable afterwards.

Confirmed on slack, this is a 'large' flow - so possible that nodes are trying to report status before the receive has been instantiated.
If a flow relies on status messages to keep state in sync, it could be problematic to swallow them if the receiver hasn't started yet. Maybe buffer them up? Needs thinking about.

Do you still have this flow active? Would like to understand this issue better before I put any error handling in.
You've shared the subflow containing the HTTP Request. I would like a bit more information about where that subflow is used.

how many tabs do you have?
by index, which tabs is that subflow used?
is that subflow used from within other subflows?
are you doing full deploys or just modified nodes/flows deploys?

I'm struggling to explain how the parent flow of a node could be null at the point in time the status event arrives.

Hello,

7 tabs
5th tab from the left
No, only a single instance of the subflow is used on the 5th tab
Full deploys.

Ah... link nodes!
The Mqtt_protocol tab is instantiated and messages start arriving. Thanks to a link node, a message can jump from that tab over to the Hardware_control tab.
I suspect you'd fix it if you moved the Hardware_control tab to the left of any tab that links to it...


[VirtualCluster] Fix clusterversions CRD, add kind support and review the demo flow

This PR introduces 3 major updates for VirtualCluster:

Fix the CRD as the generated one for clusterversions doesn't work
Add kind support, together with existing minikube
Review the demo flow with more comments for users to better understand VirtualCluster through the process

/assign @Fei-Guo
/assign @christopherhein

/ok-to-test

please squash your commit

This looks great. Thanks a lot for working on this.
/lgtm
/approve


Backend registration form validation

to ensure email and/or username are unique in the database

Issue solved with latest commit.


Adjust arg types of Credentials::with_blob

... to avoid redundant utf-8 checking

3x error while caching...

Seems smart. Maybe add a comment surrounding that code for future reference? (other than git blame)

@Johannesd3 OK to merge?


PointZilla - Add Excel reading support

Allow for the CSV parsing parameters to be used to parse Excel spreadsheets too.

Fixed by #139 in v1.0.99


Training Realtime Agent with 5 Minutes Price Interval Dataset Returns Reward 0?

I tried Training Realtime Agent with 5 Minutes Price Interval Returns Reward 0
Can you please suggest what parameters i have to twerk to train the Realtime Agent with a 5 Minutes Interval Dataset not just 1 day Interval
Thanks

5-min dataset has a lot more "noise" than day to day aggregates. To really get this to work on intraday data you would need to add (open, high, low) values to your parameters or add some technical analysis to your columns as (ma, 7-day-ma, ema, BB.....) or make more weights jittering per iteration or do sort of elite selection on your population or make your NN-weights "deep" by adding more layers (this would make training slow as this is mainly running on CPU). Since your dataset is different your approach to model selection will be a little different at the end of day. I would say if you want a out of the box solution then either keep training it until you reach some maxima (probably 1000's of iteration as you have noisy data), else I would try the suggestions above.


localStorage issue

Hey,
I'm having an issue with the localStorage plugin of meteor-desktop. In dev mode, all saved values are loaded without problems, but in production mode the values are not available anymore after a restart of the app. This is how I get the local storage object:
localStorage() {

    return (!Meteor.isDesktop) ? window.localStorage : Meteor._localStorage;
},

In my React component, I have a switch button which enables or disables auto download:
 const localStorage = DefaultHelper.localStorage();

 setAutoDownload(val) {
    localStorage.setItem("settings.download",val);
}

The button switches over to enabled, but after a restart it is disabled. The same function works without problems within the browser.

I've replaced it with your new localStorage solution. This one works without problems :)


add Google Apprenticeship

Added Google Apprenticeship to the Apprenticeship list

✅ By submitting this PR, I have verified the following

[] Checked to see if a similar PR has already been opened 🤔
[] Reviewed the contributing guidelines 🔍
[] Added my name to the bottom of the list under the Credits section in the README.md with a link to my website or GitHub profile 👥

Looks good, thank you for helping!

You are welcome @FrancesCoronel , Thank you for coming up with this helpful project


unable to override package 'WalletConnect' because its identity 'walletconnectswiftv2' doesn't match override's identity (directory name) 'walletconnectswiftv2-main'

Hi,
I have downloaded the code from this git for iOS and try to run the code and got failed as giving number of error.
Compile Errors :

unable to override package 'WalletConnect' because its identity 'walletconnectswiftv2' doesn't match override's identity (directory name) 'walletconnectswiftv2-main'
multiple similar targets 'Auth', 'Commons', 'Database' and 20 others appear in package 'walletconnectswiftv2' and 'walletconnectswiftv2-main', this may indicate that the two packages are the same and can be de-duplicated by using mirrors. if they are not duplicate consider using the moduleAliases parameter in manifest to provide unique names

Thanks,

I found a workaround that help to build the app.
In ExampleApp project, expand the Frameworks group, and remove the references to both the Package.swift and WalletConnectSwiftV2


I can see two dependencies in https://mvnrepository.com/ - which one is correct.

Hi,
I am building a Spring Boot application using Parallel consumer. When I try to add the dependency I saw below two dependencies, which one is correct.

parallel-consumer-parent (https://mvnrepository.com/artifact/io.confluent.parallelconsumer/parallel-consumer-parent)
parallel-consumer-core (https://mvnrepository.com/artifact/io.confluent.parallelconsumer/parallel-consumer-core)

Previously I had completed my POC using parallel-consumer-core as mentioned at this url: https://developer.confluent.io/tutorials/confluent-parallel-consumer/kafka.html
Could you please confirm what's the difference between both and which one to use.

Hi,
Please refer to readme - usage section - https://github.com/confluentinc/parallel-consumer#usage
In a nutshell - parallel-consumer-parent - is a parent POM for all submodules in the project, but for actual application usage you need to pick the right artefact depending on threading model:
Java thread pool - parallel-consumer-core
Verte.x - parallel-consumer-vertex
Reactor - parallel-consumer-reactor


Add doc about filtering create flags

cc @ehazlett
Signed-off-by: Nathan LeClaire<EMAIL_ADDRESS>

nice! :+1:

yay, LGTM

awesome! :+1: :+1:


[cwc-v2]: Allow change the cds-side-nav width

Description
https://carbon-design-system.github.io/carbon-for-ibm-dotcom/beta/carbon-web-components-v2/?path=/story/components-ui-shell--header-base-w-navigation-actions-and-side-nav

Currently, changing the width it's not allowed (at least in a way offered by the component itself) because there is no part and/or custom property to do it.
Component(s) impacted
UI Shell
Carbon for IBM.com version
v2 beta
Severity
Severity 1 = The design is broken in a critical way that blocks users from completing tasks or damages the brand. Affects major functionality, no workaround.
Package
@carbon/web-components
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate issues

We should take into account that, in addition to the width, there is also a max-width.

@oliviaflory any update on this? Thank you!

Hi @abdonrd apologies that this fell off my radar! Would one of your designers be able to answer the question from our previous Slack thread? Does your team have a proposal for how this would affect the page grid? I assume this is a grid influencer panel?
The UI shell and left panel are core building blocks of the design system and have a lot of thought and logic behind how they behave and perform with our grid, we have to be really thoughtful about opening up something like the max width of the left panel. So having a proposal and example of how it could effect other screens would be really helpful. Thank you!

Hi @oliviaflory! I'm a designer who works with @abdonrd. I'm happy to to think through the implications of this update, although I don't fully understand what we need to consider with regards to max-width. Can you explain that?
Also, we're only increasing the width of the fixed panel by 16px to accommodate a second icon. Would you want me to explore a panel width that's wider than 272px, or is this width okay?
Lastly, my team does not have other product screens that would be impacted by this update. Do you have any mockups / layouts with influencer panels I could solve for, so I don't have to create a design from scratch?

Hi @jeanservaas! Thank you so much for following up here. This is definitely not a Sev 1 problem, not sure why it was tagged that way. In all honesty, I was pulled into this late yesterday and should have dug into the issue before asking my questions.
@abdonrd and I discussed alternative treatments and decided to revert back to the default width and wrap titles to two lines to preserve legibility.
Please feel free to close this issue. Thanks!

Thanks @atalle, @abdonrd, and @jeanservaas !


Configure CI to build and release executables for many platforms

[ ] Windows
[ ] Linux ARM
[ ] Linux MIPS
[ ] Linux MUSL
and so on...

Someone emailed me about getting this working on their UniFi devices. It works better than the Go one by many factors.
Fun fact: An original, pie-in-the-sky target for this tool was an ARM9/Armv5E ARM926EJ-S platform.  Rust ARM9 support wasn't ready at the time. Maybe it's fine now too.
Try to use something off the shelf and mix it all together.

Didn't get to the crazy Linux stuff, but I got the rest so good enough.


add simple oCIS deployment

add a simple oCIS deployment chart:

for at home use / with single or double digit user numbers
resource saving by not starting every service individually
allow flexible configuration to eg. use an external OIDC IDP

(ownCloud internal info: base that on the ocis-beta instances deployment)

So far there is no capacity to add / maintain a second simpler Helm Chart :disappointed:


[ep-matrix] Only allow the Europyton client to authenticate to Matrix

If we want to have a custom experience with Element. we have to block other clients to login in our Matrix servers

We might be able to do this at the nginx level?


Current pep8 fails unit test mezzanine.core.tests.CoreTests.test_syntax

Mezzanine's unit tests require package pep8>=1.4.1 (source https://github.com/stephenmcd/mezzanine/blob/master/setup.py). This unit test functions properly when you install pep8==1.4.1. However running unit tests with pep8==1.6.2 causes a unit test failure. Am I using this correctly? It seems like Mezzanine should be configured to comply with pep8==1.6.2, or the requirements should be changed to be more restrictive.

Unit test error from running pep8==1.6.2
======================================================================
FAIL: test_syntax (mezzanine.core.tests.CoreTests)
Traceback (most recent call last):
File "/Users/admin/.virtualenvs/mezzanine/lib/python2.7/site-packages/mezzanine/core/tests.py", line 72, in test_syntax
self.fail("Syntax warnings!\n\n%s" % "\n".join(warnings))
AssertionError: Syntax warnings!
mezzanine/accounts/forms.py:221: visually indented line with same indent as next logical line
mezzanine/bin/mezzanine_project.py:68: do not assign a lambda expression, use a def
mezzanine/blog/management/commands/import_blogger.py:57: block comment should start with '# '
mezzanine/blog/management/commands/import_blogger.py:61: block comment should start with '# '
mezzanine/blog/management/commands/import_blogger.py:76: block comment should start with '# '
mezzanine/blog/management/commands/import_rss.py:56: visually indented line with same indent as next logical line
mezzanine/blog/templatetags/blog_tags.py:69: do not assign a lambda expression, use a def
mezzanine/conf/init.py:200: do not assign a lambda expression, use a def
mezzanine/conf/forms.py:55: do not assign a lambda expression, use a def
mezzanine/core/managers.py:83: too many leading '#' for block comment
mezzanine/core/managers.py:92: too many leading '#' for block comment
mezzanine/core/managers.py:110: do not assign a lambda expression, use a def
mezzanine/core/managers.py:124: too many leading '#' for block comment
mezzanine/core/middleware.py:164: do not assign a lambda expression, use a def
mezzanine/core/middleware.py:214: visually indented line with same indent as next logical line
mezzanine/core/tests.py:295: too many leading '#' for block comment
mezzanine/core/tests.py:305: too many leading '#' for block comment
mezzanine/core/tests.py:318: too many leading '#' for block comment
mezzanine/core/views.py:142: do not assign a lambda expression, use a def
mezzanine/core/views.py:182: do not assign a lambda expression, use a def
mezzanine/core/views.py:184: do not assign a lambda expression, use a def
mezzanine/core/management/commands/collecttemplates.py:34: do not assign a lambda expression, use a def
mezzanine/core/templatetags/mezzanine_tags.py:590: do not assign a lambda expression, use a def
mezzanine/forms/admin.py:108: do not assign a lambda expression, use a def
mezzanine/forms/fields.py:85: do not assign a lambda expression, use a def
mezzanine/forms/forms.py:198: visually indented line with same indent as next logical line
mezzanine/pages/fields.py:23: do not assign a lambda expression, use a def
mezzanine/pages/managers.py:27: visually indented line with same indent as next logical line
mezzanine/pages/models.py:138: do not assign a lambda expression, use a def
mezzanine/pages/tests.py:145: test for membership should be 'not in'
mezzanine/pages/templatetags/pages_tags.py:51: do not assign a lambda expression, use a def
mezzanine/pages/templatetags/pages_tags.py:52: do not assign a lambda expression, use a def
mezzanine/project_template/fabfile.py:129: do not assign a lambda expression, use a def
mezzanine/project_template/fabfile.py:233: do not assign a lambda expression, use a def
mezzanine/project_template/settings.py:116: do not assign a lambda expression, use a def
mezzanine/project_template/settings.py:187: module level import not at top of file
mezzanine/project_template/settings.py:251: block comment should start with '# '
mezzanine/project_template/settings.py:252: block comment should start with '# '
mezzanine/project_template/wsgi.py:9: module level import not at top of file
mezzanine/utils/conf.py:40: do not assign a lambda expression, use a def
mezzanine/utils/conf.py:42: do not assign a lambda expression, use a def
mezzanine/utils/conf.py:44: do not assign a lambda expression, use a def
mezzanine/utils/conf.py:46: do not assign a lambda expression, use a def
mezzanine/utils/docs.py:94: do not assign a lambda expression, use a def
mezzanine/utils/docs.py:154: line break before binary operator
mezzanine/utils/docs.py:154: visually indented line with same indent as next logical line
mezzanine/utils/docs.py:199: visually indented line with same indent as next logical line
mezzanine/utils/email.py:57: do not assign a lambda expression, use a def
mezzanine/utils/models.py:224: do not assign a lambda expression, use a def
mezzanine/utils/tests.py:142: line break before binary operator
mezzanine/utils/tests.py:142: visually indented line with same indent as next logical line

Thanks for the report - I presume you're using the current release as I believe these issues are already resolved in the development branch.


[Events] Fix issues on anomalies filters and on anomalies snoozing

This PR is about the issue we had on anomalies filters and anomalies snoozing (the fact that we couldn't add or delete filters and we couldn't snooze or unsnooze anomalies).

@jgchoppe I don't know which IDE/Text editor you are using, but most of them have plugins that can run gofmt and goimports fo you when saving your files ;)


Install hadoop+hive on airflow docker to be able to connect

I'm developing a new example for my site and wanted to use the "hive" and "beeline" commands. I can only use that when hadoop+hive have a client installation in the airflow worker container.
I'm not a docker practice expert, yet this PR demonstrates what I've been able to do to get the example working, attempting to go for minimal changes and impact.
Can we use this PR to evaluate together what the best method is to get these mundane packages installed and configured?
Unless you're happy to accept them verbatim of course.
The relevant docker compose fragment would look like this:
      - hive
  environment:
      - LOAD_EX=n
      - EXECUTOR=Local
      - INSTALL_HIVE=y
  volumes:
      - ./examples/hive-example/dags:/usr/local/airflow/dags
      - ./examples/hive-example/sql:/usr/local/airflow/sql
      - ./examples/hive-example/core-site.xml:/core-site.xml
      - ./examples/hive-example/hadoop-env.sh:/hadoop-env.sh
      - ./examples/hive-example/hdfs-site.xml:/hdfs-site.xml
      - ./examples/hive-example/mapred-site.xml:/mapred-site.xml

Thanks for your PR, but docker-airflow is for a "base" example purpose. I invite your to use your own fork for your needs


Check for whether username exists after signup button pressed

Summary:
When signing up through the app the checking for whether the user exists in the system done after pressing the signup button. Most of the times it ends up in multiple signup attempts.
Steps to reproduce:
A signup with existing user name will reproduce.
Expected behavior:
The check up for the user existence should be checked after the 'onchange' trigger of the username field. Then the requirement for multiple attempts can be avoided.
Observed behavior:
System check for the user existence after pressing the signup button requires to go through the entire signup process in case of the username exists.
Device and Android version:
HUAWEI SCC U21
Android 5.0
(Anyway it does not matter which device or Android version as the activity is a webview)
Commons app version:
2.6.7

@nicolas-raoul, should I take this up as a sub-task for #1298?

I think it can be considered a different task :-)
One may affect the other, though.
On Mon, Apr 2, 2018 at 1:08 AM, Suchit Kar<EMAIL_ADDRESS>wrote:

@nicolas-raoul https://github.com/nicolas-raoul, should I take this up
as a sub-task for #1298
https://github.com/commons-app/apps-android-commons/issues/1298?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/commons-app/apps-android-commons/issues/1325#issuecomment-377797125,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGFBsOVJxhwHk_b_fVlih4YMWHwCxdQks5tkPtkgaJpZM4Su7uY
.

@nicolas-raoul Hi I would like to work on this, if no one is assigned to it.

@aa-rikimaru OK it is yours :-)


Demo for DE Forum -- Kevin Gaynor

Hi Kevin- you contributed to my own private repo (not sure if you forked my upstream or not) :)


Adding new module, documentation, and complete example

what

All changes associated w/ the new module

why

This module automates the deployment of the Terraform Cloud Agent to an existing Kubernetes cluster

hey @osterman I made the rest of the updates and tested everything, although there's one more item I'd like to inquire about..
Do you think that the TCF_AGENT_TOKEN should be considered "sensitive" and stored/accessed via a k8s secret?

Do you think that the TCF_AGENT_TOKEN should be considered "sensitive" and stored/accessed via a k8s secret?

I suppose you're right. It's sensitive because any agent with that can receive dispatches from TFE/TFC and those dispatches could contain secrets. It's probably not too much more work and for correctness should be a Secret

Maybe this module should be called terraform-kubernetes-tfc-cloud-agent instead since HashiCorp never seems to refer to it as TFE (Even though TFE/business is required)

Hey @osterman , I forgot to send a note late last week, but all of the changes to this one were made and its ready for final review 👍

Ok all fixed @osterman 👍


Turi Create save model to Cloud storage directly

Hi,
This is not an issue but i need some help. I wanted to know if there is anyway to save the model dorectly to cloud storage with saving it locally?

Save should let you write to s3 directly. Please let us know if you have issues with it.


Storage doc: add howtos

Add and expand how-to guides for working with storage volumes.

Documentation preview available at: https://linuxcontainers.org/lxd/docs/pr.10556/


ARROW-12228: [CI] Create base image for conda environments

Using a base image we can reduce the number of installed packages for the conda-integration image. cc @pitrou

@github-actions crossbow submit -g conda


Can't change default port?

Hello,
how can I change the default port?
"-e server-port" doesn't work.

root@ubuntu# docker run -d -it -e EULA=TRUE -p 19135:19135/udp -e server-port=19135 -e online-mode=false -e max-players=50 -v $locpath:/data -e LEVEL_TYPE=DEFAULT -e GAMEMODE=creative -e DIFFICULT=peaceful --restart unless-stopped --name minecraft-crea itzg/minecraft-bedrock-server
e4b26d87c3476c6d98f2cb45bccf3a988e5453cae5ed78ad0e11baa0974b3ae0
root@ubuntu# docker logs minecraft-crea
DEBU[0000] Using /data to match uid and gid
DEBU[0000] Resolved UID=0 from match path
DEBU[0000] Resolved GID=0 from match path
Starting Bedrock server...

Since Docker containers allow port mapping to arbitrary external ports, I purposely left out the server-port configuration option.
Your docker run usage was very close...use a -p of -p 19135:19132/udp to expose that particular container on port 19135.
BTW, you'll need to use upper snakecase for the -e's, so you'll need ONLINE_MODE and MAX_PLAYERS. (It's easy to mix up the two, so I'll work on enhancing the property setter to accommodate either.)

Good point, thank you!


salimfadhley/jenkinsapi vs jenkinsapi/jenkinsapi policy

Hi,
Could you explain me why the issue https://github.com/salimfadhley/jenkinsapi/issues/448 has been fixed on the salimfadhley/jenkinsapi master branch and has not been in the jenkinsapi/jenkinsapi repository.
More generally could you tell me what is the policy between these 2 repositories ?
Regards.

@salimfadhley ?

To complete the original question, it's not clear for us which repo of the two we should use to benefit from the latest bug fixes.
If we check https://github.com/salimfadhley/jenkinsapi/network, we see that most of the activity is done on salimfadhley fork, yet the released version on PyPI comes from the jenkinsapi repo but doesn't include all the commits (for example #448 for Jenkins 2.x compat). IMHO, the releases should either be done directly from salimfadlhey repo, or else the changes on this fork should be merged into the main repo before publishing a new release.
Thanks,

Fair point @piwai. I merged this repo into jenkinsapi/jenkinsapi.
@salimfadhley, please release new version.

This is the main repo. I was the original author of the project, however 99% of the work is done by @lechat . We have a plan to migrate everything to the jenkinsapi/jenkinsapi repo... eventually.
@lechat your wish is my command! :-)

@salimfadhley I've heard that moving project to organization using Github magic instead of using git clone/push to org will properly move all issues/PRs there. Never tried that myself though... Worth checking it up, I guess, to remove that hanging duality.

Thanks guys for the explanation :)
@salimfadhley Did you release the new version? I can't see it on PyPI...

I will do it this week.
On Tue, 5 Jul 2016, 08:24 Pierre-Yves Rofes<EMAIL_ADDRESS>wrote:

Thanks guys for the explanation :)
@salimfadhley https://github.com/salimfadhley Did you release the new
version? I can't see it on PyPI...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/salimfadhley/jenkinsapi/issues/454#issuecomment-230405196,
or mute the thread
https://github.com/notifications/unsubscribe/AAvzWT_cGzLV_ef4wfySNA3o7hZTwXTRks5qSgaygaJpZM4I3Lmv
.

Release is done.
I'd like to do the next major release from our new project space. I'd also like to make some changes over there so that the release process is a bit less messy. I'd like to get it into a state where it can be safely handed over.

Repository now moved to pycontribs. All releases will go from this new location.


taser sprite fix

makes the glowy part on the taser all one line since it doesn't have 4 shots anymore
also gets rid of the old sprites from when it did have ammo

Making it a binary state seems like a bad idea.

this pr was already discussed in the discord and it was ultimately decided that the taser sprite should not be changed.


Keyboard Shortcuts Don't Respond After Selecting Text

If I highlight a section of text, but do not move my mouse at all after completing the selection, keyboard shortcuts stop responding. I am still able to type and use the keyboard, but until I move my mouse, shortcuts (ctrl+c, ctrl+v, ctrl+s) do not work at all. As soon as I move the mouse, they begin working again. Extremely annoying when trying to use copy and paste.

Deleting my %appdata%/Brackets folder seems to have solved this issue


add codefix for stub method/function

offer a codefix as an option (among others, for example importing) that would create a stub of a function or method, when undeclared identifier is used in a call expression

duplicate of https://github.com/Microsoft/TypeScript/issues/10140

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.


Support reduce aggregate function in MQE.(#11031)

reduce function

[ ] If this is non-trivial feature, paste the links/URLs to the design doc.

[x] Update the documentation to include this new feature.

[ ] Tests(including UT, IT, E2E) are added to verify the new feature.

[x] If it's UI related, attach the screenshots below.

[x] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #11031 .

[x] Update the CHANGES log.

@wu-sheng @wankai123  It is not the final code, I want to confirm the following questions:

whether reduce is a good name?
reduce should be defined as function or aggregate function?
whether reduce avg agorithm should filter null values?
I use (COMMA parameter)* define aggregate function param list, It means aggregation function can have 0-N params, I'm worried it may effect other agg function，should I define it like 'function0' 'function1'?

Reduce seems a strange name, Could you explain the logic?

Reduce seems a strange name, Could you explain the logic?

reduce merge several time serial data into one，in dashboard it looks like several line merged into one line. Essentially, it aggregate labelvalue to singlevalue.
reduce name is reference from java stream reduce. I feel it strange too, so I ask you for help.

I think we should use aggregate with function name, with a parameter to match labels, star(*) or a list of known labels.

I think we should use aggregate as function name, with a parameter to match labels, star(*) or a list of known labels.
And, how would you process the number? avg, max, min? I think it should be a parameter too.

Like this?
aggregate(metric_name, by_label, sum|avg|max)

I think that makes more sense and clear.

Ok, thanks. I will adjust code like this.

whether reduce is a good name?

aggregate_label or something? I think it's only for the labeled_value series.

reduce should be defined as function or aggregate function?

see https://github.com/apache/skywalking/pull/11036#discussion_r1250789220

whether reduce avg agorithm should filter null values?

I think should reserve NULL if the result is NULL

I use (COMMA parameter)* define aggregate function param list, It means aggregation function can have 0-N params, I'm worried it may effect other agg function，should I define it like 'function0' 'function1'?

please refer to https://github.com/apache/skywalking/pull/11036#discussion_r1250789220

@wu-sheng I think aggregate function does not need a label param to match labels, because metric name expression already have this ability implemented by @wankai123 , the following two expression is equivalent：
aggregate_label(mongodb_cluster_connection{label="1,2,3,4"}, SUM)

aggregate_label(mongodb_cluster_connection, {label="1,2,3,4"}, SUM)

What do you mean? D you mean it is supported or what?

What do you mean? D you mean it is supported or what?

I means label match is supported, if we aggregate all label values, we can define MQE like this:
aggregate_label(mongodb_cluster_connection, SUM)

If we just want aggregate part of labels, we can define MQE like this:
aggregate_label(mongodb_cluster_connection{label='1,2,3,4'}, SUM)

So, no need for a new PR to support?

@wu-sheng I think aggregate function does not need a label param to match labels, because metric name expression already have this ability implemented by @wankai123 , the following two expression is equivalent：
aggregate_label(mongodb_cluster_connection{label="1,2,3,4"}, SUM)

aggregate_label(mongodb_cluster_connection, {label="1,2,3,4"}, SUM)

yes, the aggregate_label should base on the result of the labeled_value expression. Just .ike avg/min or other functions.

So, no need for a new PR to support?

Sorry, I didn't explain it clearly.
aggregate_label function is need, and I will perfect this pr according to your requirements we talked yesterday.
But this function does not need a label param to match label because it is already supported by metric_expression.

mongodb_cluster_connection{label="1,2,3,4"}

This style works for me. Question would be, are labels always predicted? If not, do we support all or some sub expression?

This style works for me. Question would be, are labels always predicted? If not, do we support all or some sub expression?

mongodb_cluster_connection{label="1,2,3,4"} is a metric_expression already supported by MQE and returns time series labeled value.  So the labels should be predicted, and the  new aggregate_label  func just needs to aggregate the labels in the result of mongodb_cluster_connection{label="1,2,3,4"}.

OK. Make sense. One tip, the word label seems not precious. Could you support labels and put that in the docs?
I know it is a breaking change, but a label with multiple values seem not good for the longer term. @wankai123

OK. Make sense. One tip, the word label seems not precious. Could you support labels and put that in the docs? I know it is a breaking change, but a label with multiple values seem not good for the longer term. @wankai123

I think it's related to Skywalking's label mechanism, we could discuss it later.

Sync discussion conclusion, the default label key would be change to _(under line).

I hava completed the code adjustment, add introduce docs and tests about aggregate_label function, please help me review.

Could you add an e2e case to verify the new expression? You can use service _percentile metric and refer here: https://github.com/apache/skywalking/blob/8aab7d7ac7386e2a1b0dc8af995ceb1c6715d2ff/test/e2e-v2/cases/mqe/mqe-cases.yaml#L48

Could you add an e2e case to verify the new expression? You can use service_percentile metric and refer here:
https://github.com/apache/skywalking/blob/8aab7d7ac7386e2a1b0dc8af995ceb1c6715d2ff/test/e2e-v2/cases/mqe/mqe-cases.yaml#L48

Ok, I will add a e2e case.

One thing about the function name, from your current logic, it seems all labels are going to be merged, right?

Yes, all labels will be merged.

One thing about the function name, from your current logic, it seems all labels are going to be merged, right?

Yes, all labels will be merged.

Is aggregate_labels better?

One thing about the function name, from your current logic, it seems all labels are going to be merged, right?

Yes, all labels will be merged.

Is aggregate_labels better?
aggregate_labels beter than aggregate_label, I will change name to this, thanks.

I have changed function name to aggregate_labels and add an e2e case for this function.

Anything I can do? I found there are 4 failings.

I rerun, it works.


Gen2 OCR Demo

[Error] Reported while running Gen2 OCR example on armv7l;
Using libraries -
numpy==1.19.5
opencv-python==<IP_ADDRESS>
depthai==<IP_ADDRESS>+e88c98c8a7681dd16cd754a832df1165380ac305
Error -
(venv2) pi@raspberrypi:~/depthai-experiments/gen2-ocr $ python3 main.py
main.py:15: DeprecationWarning: setCamId() is deprecated, use setBoardSocket() instead.
  colorCam.setCamId(0)
terminate called without an active exception
Aborted

Thanks for the report!

I think the depthai version there is missing this fix: https://github.com/luxonis/depthai-python/commit/87247bfb645027a30c68191d88fe1b69b70e39ac
We'll need to update the demo to use the latest version.


Added sf::VertexBuffer class

Also added an example demonstrating VertexBuffer, Shader and Thread usage.
If anybody feels like tweaking the generation parameters a bit to make the example output look better feel free to do so. Being an artist is not one of my strong points...

@LaurentGomila All the issues should be addressed in the current version.

Looks perfect.
What about:

Have you tried to replace VA with VB in SFML implementation, to see the impact on performances (and usability)? The most interesting candidate would probably be sf::Text.

And shouldn't we mark sf::VertexArray deprecated?

If I could be sure that VBOs are supported everywhere then it wouldn't be a problem. The reason why there is sf::VertexBuffer::isAvailable() is because SFML still claims to support everything OpenGL 1.2+. VBO support was only merged in OpenGL 1.5, so we might end up breaking some older systems unless we have code for both paths.
I also wouldn't mark sf::VertexArray as deprecated for the same reason. If we intend on staying backwards compatible with older systems, then they are still necessary. I would rather provide a recommendation to use sf::VertexBuffer whenever compatibility with 20 year old systems isn't a big concern of the user.

An alternative would then be to add an implementation of sf::VertexBuffer that falls back to vertex array when VBOs are not supported, but that might complicate the code too much.

Maybe the added example would deserve its own separate PR, so that it can be reviewed and discussed properly without blocking this one?

An alternative would then be to add an implementation of sf::VertexBuffer that falls back to vertex array when VBOs are not supported, but that might complicate the code too much.

We can merge this first and think about optimizing the existing classes with VBO support one by one in their own PRs. It involves some work but maybe having both paths in the implementation is still the least complicated way to go forward.

Maybe the added example would deserve its own separate PR, so that it can be reviewed and discussed properly without blocking this one?

I was already thinking about doing this anyway. SFML needs way more examples anyway, might as well start with this.

Ok, so after you move the example to its own PR, I think we'll be ok here :+1:

Done. Example here: https://github.com/SFML/SFML/tree/feature/island_example

Had a chance to test this a little. Today, I moved my game's current implementation from sf::VertexArrays over to sf::Vertex/sf::VertexBuffer and thought I would give my casual observations.

Everything converted over fine. Had 0 problems. Haven't noticed any oddities.
Tested a game level that uses multiple tilemaps, with the largest being 36,736 verts.
I observed a small drop in GPU usage (25% -> 23% from Windows Task Manager, 16% -> 13% from GPUz).
I observed an increase in video memory usage (to be expected). ~79MB to ~93 MB.
Didn't seem to be a major change in CPU usage. What I'm creating isn't very demanding to be honest.
On my system, a casual profile saw the Draw time on my Tilemap class (all objects) go from 3.73s (on a 60s run) to 1.1s (!).

Note: I haven't tried to "break" this yet. Will be sure to report issues if I run into them.
Here's the sizes of the tilemaps in the level I tested.
Loaded 36736 Verts
Loaded 4092 Verts
Loaded 1144 Verts
Loaded 584 Verts
Loaded 384 Verts
Loaded 52 Verts
Loaded 120 Verts
Loaded 352 Verts
Loaded 2248 Verts
Loaded 30436 Verts
Loaded 32 Verts

Fixed.


Rebuild for Python 3.7, GCC 7, R 3.5.1, openBLAS 0.3.2

Fixes #5

@conda-forge-admin please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you but ran into some issues, please ping conda-forge/core for further assistance.

@conda-forge-admin please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin please rerender


Fix atscfg strings.ReplaceAll to Replace

Fix atscfg strings.ReplaceAll to Replace.
The strings.ReplaceAll func doesn't exist in our current pinned
version of Go, 1.11.
Is a unit test.
No docs, no interface change.
No changelog, no interface change.

[x] This PR is not related to any other Issue

Which Traffic Control components are affected by this PR?

Traffic Ops ORT

What is the best way to verify this PR?
go test
If this is a bug fix, what versions of Traffic Control are affected?
Not a bug fix.
The following criteria are ALL met by this PR

[x] This PR includes tests OR I have explained why tests are unnecessary
[x] This PR includes documentation OR I have explained why documentation is unnecessary
[x] This PR includes an update to CHANGELOG.md OR such an update is not necessary
[x] This PR includes any and all required license headers
[x] This PR ensures that database migration sequence is correct OR this PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Additional Information

UTs all pass now with 1.11 -- thanks!

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/4888/


Remove pycocotools dependency

What changes are proposed in this pull request?
Reimplement the IoU calculation from pycocotools to remove the dependency on it. Removed all instances of pycocotools.
Closes #447
How is this patch tested? If it is not, in a single sentence please explain why.
Results from the new implementation matched the original one. The runtime was unchanged.
What areas of FiftyOne does this PR affect?

[ ] App: FiftyOne application changes
[ ] Build: Build and test infrastructure changes
[x] Core: Core fiftyone Python library changes
[ ] Documentation: FiftyOne documentation changes
[ ] Other

@brimoor This is ready for rereview.


1.1.0 does not install properly or work at all

Something is wrong with the module, it doesn't function at all in 1.1.0.

resolved in v1.1.2


Clean-up:  Remove celery beat?

Technical clean-up discussion / task:  remove celery beat?
CC:  @sidprobstein and @dnicodemus

Is there a reason to keep the references to Celery Beat around?

Celery Beat is used for the retention policy https://github.com/sidprobstein/swirl-search/wiki/2.-User-Guide#expiration and will support the search.subscription property planned for a future release...


getModel deeplearning | Cannot read property 'cm' of null at createOutput (http://localhost:54321/flow/js/flow.js:6456:30)

inside of renderMultinomialConfusionMatrix

which in turn is in src/h2oModelOutput.js


For SMAC Qimx/MADDPG config

It's really a nice work and according to your paper, running Qmix/MADDPG is really fast. But we didn't find a config about Qmix/MADDPG algorithm, We don't know how to run your Qmix/MADDPG program，so can you give us a config for the Qmix/MADDPG algorithm?

Have you solved this problem bro? I have some questions of this framework, shall we talk about this.

The repo has been refactored, thus I closed this issue


💡[Feature]: Endometrial cancer Prediction

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Hi @TAHIR0110 @Atharv714
I want to add Endometrial Cancer Prediction.
Endometrial cancer, which originates in the lining of the uterus, is the most common gynecologic cancer. Early detection is crucial for successful treatment and improving survival rates.
Use Case
.
Benefits
Early Detection
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@TAHIR0110  @Avdhesh-Varshney sir, please assign this issue to me.

@Khushi-Pushkar show me the dataset which you will be using?

https://www.kaggle.com/datasets/yeganehbavafa/uterine-corpus-endometrial-carcinoma

Please assign this issue to me @TAHIR0110 @Atharv714


Add glyphicon font paths to export.json

Overview of the Issue - When bundling/exporting the skeleton app, Glyphicon fonts (provided by Bootstrap) are not exported.
Motivation or Use Case - While font-awesome is also used, if a beginner to Aurelia tries to use Glyphicon fonts as per Bootstrap docs, they will have to investigate bundling, which can be quite complex to a beginner.
Related Issues - Could not find related issues

@ahmedshuhel Can you review this please?

@ahmedshuhel Can you review and test?

@EisenbergEffect @tomtomau Is bundle task using this export.json file?

OK I understand now.  this is related to export task and not with bundling in general. What is the problem export task trying to solve here exactly?

@tomtomau Would you mind rebasing on master?

@ahmedshuhel - if someone were to try to use the bootstrap glyphicons, they would not work when exported. This fixes that.
@EisenbergEffect - I have rebased on latest master. Cheers!

@tomtomau Thanks for this contribution. I'm really sorry it took us so long to get it in. Thank you for your patience.


[Websocket] Couldn't send the corrupted frame by using WebSocket client

Description:
$Subject

This is covered with newly added https://github.com/ballerina-platform/module-ballerina-websocket/blob/main/websocket-ballerina/tests/corrupted_frame_client_test.bal, https://github.com/ballerina-platform/module-ballerina-websocket/blob/main/websocket-ballerina/tests/corrupted_frame_server_test.bal
tests


Initial development

Create the first version of the plugin
To do

[x] Make folder-scoped secret fetching work
[ ] Config merging (maybe?)
[x] Docs
[ ] Plugin icon (Secrets Manager icon with a little Jenkins folder icon superimposed on it, in the bottom-right or bottom-left, whichever is the Jenkins UI convention)
[x] Tests
[ ] Code cleanup
[ ] Refactor upstream plugin as needed to support this

Looping in @edwardprzeniczny

In its current state the folder-scoped provider is called, however due to the code paths that are followed the ItemGroup that's passed in is always Jenkins.get() i.e. the root Hudson object. This is wrong because we want the relevant AbstractFolder (which subclasses ItemGroup) to be passed in instead.

@edwardprzeniczny I've now got something early stage and experimental which should let you configure the plugin at a folder level, and let jobs in that folder fetch folder-scoped credentials.
Would you be able to test it* and let me know if it generally does what you're looking for?
If you're comfortable building the plugin from source then please do that, if not then I can compile a .hpi plugin file for you.
(Note that there are some features missing at the moment: I haven't implemented credential caching, or hierarchical config merging. It also has a hard dependency on the main Secrets Manager plugin at the moment, so that will attempt a connection to Secrets Manager with its own settings, irrespective of your folder-level settings.)

(*) Please only use this on a test Jenkins, don't let it anywhere near production for now

CC @NoamGoren @tuxy85 @alandevine @maqzee-git @sun-mir @Sickafant

Thank you for testing!
Re the duplicate credential you saw which was in both the global store and a folder store - was this credential for the same underlying secret (in the same AWS account)?
Or were the global store and the folder store pointed at different AWS accounts, in which case there just happen to be 2 secrets with the same name in your different accounts? (This often occurs when you have an AWS account per environment and you use templating e.g. with Terraform to make them look identical)

@chriskilding Yes, It was the same underlying secret from the same account (the one where the controller is launched). The default is to use the controllers profile and so every folder is pulling the secrets from the controllers aws account, unless its configured to look elsewhere. Not every folder will require credentials and so I think the default should be to be disabled.

Hmm... the folder-scoped CredentialsProvider has a null guard on the folder-level configuration. This is supposed to ensure that if there's no folder-level configuration present on the specified folder, the folder-scoped CredentialsProvider will act like it does not exist, and return an empty list of credentials.
This should mean that these folders will only see the global scoped credentials, and there won't be a duplicate.
If, however, you have folder-level configuration present, and it points at the same AWS account as your global config, then both providers will attempt to resolve it. In this scenario you would see duplicate credentials.
Does this match up with what you've seen?

Ahhh right, I see now. In the unit/integration tests everything was driven from CasC / JobDSL, so I hadn't checked the Web UI approach.
Yes, we'll definitely need a way to stop this implicit configuration of the folder-scoped credential provider, on folders where it's not wanted.

Hi again, I've pushed a change which puts the folder-scoped credentials provider's configuration behind an 'Enabled` checkbox. This addresses the problem you found, allowing you to set folder configuration in the Web UI, while letting you control whether the folder-scoped credentials provider is enabled on that folder.
Give it a spin and let me know if it works for you :)

@edwardprzeniczny would you be able to test the updated version of the plugin, and let me know if it fixes the problem you encountered?


Automated cherry pick of #6221: cloudprovider: add methods for getting http client

Cherry pick of #6221 on release/3.2.
#6221: cloudprovider: add methods for getting http client

Codecov Report

Merging #6222 into release/3.2 will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           release/3.2    #6222      +/-   ##
===============================================
- Coverage         7.04%    7.03%   -0.01%
===============================================
  Files              646      646
  Lines           110882   110888       +6
===============================================
- Hits              7813     7804       -9
- Misses          102467   102484      +17
+ Partials           602      600       -2

Flag
Coverage Δ

#aFlag
7.03% <0.00%> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/cloudprovider/cloudprovider.go
1.53% <0.00%> (-0.11%)
:arrow_down:

pkg/multicloud/aws/aws.go
0.00% <0.00%> (ø)

pkg/multicloud/ucloud/ucloud.go
0.00% <0.00%> (ø)

pkg/cloudcommon/cronman/cronman.go
48.83% <0.00%> (-5.12%)
:arrow_down:

pkg/appsrv/response.go
70.58% <0.00%> (+2.94%)
:arrow_up:

Continue to review full report at Codecov.

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


We are getting issue again while trying to send invite via powershell. Below is the issue.

Azure documentation issue guidance
Thanks for opening an issue in the Azure technical documentation repository.
We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.
Creating an issue
We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.
You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

[ ] The relevant Azure service or technology.
[ ] A link to the published documentation article that you have feedback about.
[ ] Clear, specific feedback that the author can act on.

Pull requests and article contributions
If you know the change that is needed in an article, we encourage you to submit the changes directly using a pull request. If the change is large, or if you want to contribute an entire article, follow these guidelines:

[ ] Don't surprise us with a big pull request or a pull request with a new article! Submit an issue that describes the details of the proposed large change or new article.
[ ] Include the service or technology area.

We'll route the issue to the appropriate content team for review and discussion.
Tech support and product feedback
If you would like to contact Microsoft about other things, such as product feedback or tech support, please review these guidelines:

If you need technical support using Azure, the paid and free support options are described here: https://azure.microsoft.com/support/options/.

Each article in the Azure technical documentation contains a product feedback button - it's best to submit product feedback directly from a relevant article. Otherwise, you can submit product feedback for most Azure products in the following product feedback forum: https://feedback.azure.com/forums/34192--general-feedback.

New-Object : Cannot find type [Microsoft.Open.MSGraph.Model.InvitedUserMessageInfo]: verify that the assembly containing this type is loaded.
At C:\ExternalSharing\GuestUsersProvisioning\GuestUsersProvisioning_V1.ps1:161 char:27

... ssageInfo = New-Object Microsoft.Open.MSGraph.Model.InvitedUserMessag ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidType: (:) [New-Object], PSArgumentException
FullyQualifiedErrorId : TypeNotFound,Microsoft.PowerShell.Commands.NewObjectCommand

@vayinapurapu thanks for reaching out. Since this repo is for document related issues, can you please share the document you are referencing so we can assign to the appropriate team? Thanks.


Added tooltips to all Icon buttons

@iwiznia Can you please review this?
Details
Wrapped all TouchableOpacity + Icon components with Tooltip.
Fixed Issues

$ #4499
Tests

Verified tooltips for IOUModal, Search, ReportActionCompose, AttachmentView, VideoChat.
Verified Tooltips for Web and Desktop
Tested for no impact on Mobile Web, iOS and Android

QA Steps

Tested On

[x] Web
[ ] Mobile Web
[x] Desktop
[ ] iOS
[ ] Android

Screenshots

Web

Mobile Web
NA

Desktop

iOS
NA

Android
NA

@iwiznia PR raised.
Need help:

to confirm coverage. I'd search all Icon across the codebase and updated all relevant pressable icon
Translations in Spanish.
I haven't added Tooltips to the following buttons:
a. Main Send button in the Chat Input Box
b. Green FAB on the LHN
c. + button that opens up "Add attachment" option

Let me know if you feel tooltips are required for those too.

I haven't added Tooltips to the following buttons:

Why not?

Oh, also can you make sure to test in the other platforms? Even if it is to check there are no regressions and buttons look/work properly

I'll update the translation changes.

Why not?
One of them was a primary action. Other is a menu. I can add. Can you help with the translations for these two buttons ?

Oh, also can you make sure to test in the other platforms? Even if it is to check there are no regressions and buttons look/work properly
I've checked the other platforms - Mobile Web, iOS, and Android.

One of them was a primary action. Other is a menu. I can add. Can you help with the translations for these two buttons ?

Sure. Let me tag the @Expensify/marketing team so they can check the copy (all new copy is in this file, they are the green lines) and give us copy for the tooltips of these buttons:
a. Main Send button in the Chat Input Box
b. Green FAB on the LHN
c. + button that opens up "Add attachment" option
I can then translate the new ones for you.

@iwiznia One quick question, what are your thoughts on opening the FAB menu and the + icon menu on hover? rather than adding Tooltip?

I am personally not quite fond of things that open on hover. In any case that's just one opinion, you can propose and discuss changes like that one in the slack channel.

PR Updated with suggested translations and tooltip for send button.

b. Green FAB on the LHN
c. + button that opens up "Add attachment" option
We are still waiting for those, right?

Yes waiting.

@marklouisdeshaun Thanks, Mark. Will update. Can you help with the copy of the other two buttons? Floating Action Button in the sidebar and + button to open Add Attachments in the chat?

@iwiznia @marklouisdeshaun Left with the copy & translation for the + action on ReportActionCompose.  Can you help with that to close it at the earliest?

I've set the labels as Actions and Acción right now.

@iwiznia @marklouisdeshaun Left with the copy & translation for the + action on ReportActionCompose. Can you help with that to close it at the earliest?

@marklouisdeshaun Can you help me with the copy of this button? So that this can be moved to closure?

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to production by @roryabraham in version: 1.0.88-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

This has been deployed to production and is now subject to a 7-day regression period.
If no regressions arise, payment will be issued on 2021-09-08.  :confetti_ball:

Leaving a note here that the PR has caused a regression: https://github.com/Expensify/App/issues/14043
The 'close' and 'download' tooltips are slightly misaligned


Add rspec expectations and some tweaking

Hi, thanks for paying attention to use v0.14 Parser Plugin API.
I read this article https://qiita.com/imunew/items/632616b59820272a5447 and your plugin code.
Then, I noticed that this plugin does not have rspec expectations.
I added and some tweaking to run rspec expectations with actual monolog style text.
You can confirm to run added rspec expectations with [bundle exec] rake spec.
Thanks.

Oh, actual tests written at text. 😓


Dependencies and dependency versions

It's not clear to me what versions of the various dependencies are required (jquery, jquery-ui, d3, etc).

The examples have all been tested and all work with jQuery 1.8.3 and jQueryUI 1.9.2. It's a good bet that later versions will work well, and it's kind of a crapshoot if you want to use later versions.
Version 3.0 of d3 I believe works, but if you want to use c3 you'll need a compatible version of d3 (which I believe is the very latest one)


How to change environment by adding dynamic and static obstacles?

I've changed the environment using examples in the usage of intelligent-robot-simulator, but where can I implement this environment in gym_env and policy_train_process? Thank you.

Basically, how should we add all the varied environments like dynamic obstacles and different shapes of obstacles from 'Intelligent robot simulator' to this project? i.e. which file do we need to add or edit, or the reward function...

Hi, thanks for your interest on my work.
To change the env in the training process, you can modify the file train_world.yaml directly in the policy_train folder or using your own yaml file by changing the argument --world_path in the train_process.py.
Most of the environment can be set by the yaml file, such as the different size of obstacles. But for the dynamic obstacles, the function obs_cirs_step is necessary to assignment velocity of obstacles. All these modifications can be transformed in the step_ir function in the mrnav.py

Hi, thank you for your reply.
I've successfully added dynamic obstacles to the environment under gym_test_world.yaml and gy_env_test.py. But for static obstacles, it seems that the environment doesn't reset if robots collide with static obstacles, do I need to write a new VO reward function to fix it? Thank you.

Hi, thank you for your reply.
I've successfully added dynamic obstacles to the environment under gym_test_world.yaml and gy_env_test.py by adding obs_cirs_stpe() in step_ir, but when I tried to run train_process the dynamic obstacles seem static, do I need to edit ppo.training_loop? And for static obstacles, it seems that the environment doesn't reset if robots collide with static obstacles, do I need to write a new VO reward function to fix it? Thank you very much.

Hi,
I have added a file dynamic_obs_test.yaml to set the world with dynamic obstacles, and added obs_cirs_step() in step_ir in the latest version.
It works well. You can change the --world_path to dynamic_obs_test.yaml to use without other change. The rvo reward function calculates these obstacles too.

Hi, thank you so much for your help.
But I noticed that dynamic obstacles on plots of train_process and pre_trained_model still seem static (obstacles don't move at all for an epoch), even though robots did avoid those obstacles in pre_trained_model. Is this normal? Thank you.

Hi, the normal animation with dynamic obstacles should be as follows, which is generated with the latest version by policy_test_pre_train.py

Hi ruihua,
It works well now. Thank you for your help, I will close the issue.


Crash in native code on Mac OS 11 (Big Sur)

I get a crash in native code when using xamarin-bluetooth-le on Mac OS 11 (Big Sur). Happens both with the BLE.Client.macOS sample as well as my own app.
Steps to reproduce

Open BLE.sln in VS for Mac.

Build the BLE.Client.macOS project in Debug mode.

Run it.

Expected behavior
The sample app starts up without error.
Actual behavior
The app crashes instantly.
Crashlog
=================================================================
	Native Crash Reporting
=================================================================
Got a abrt while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

=================================================================
	Native stacktrace:
=================================================================
	0x1060f48b6 - /Users/janus/github/xamarin-bluetooth-le/Source/BLE.Client/BLE.Client.macOS/bin/Debug/BLE Sample.app/Contents/MacOS/BLE Sample : mono_dump_native_crash_info2021-04-09 02:25:40.474 BLE Sample[25350:586001] Warning: The declared constraints for <NSToolbarItemViewer: 0x7fbeea55a1f0 'ToolbarGroup'> were previously invalidated only because a declared constraint was snipped or manually deactivated. This indicates missing invalidation for a view's changing state that affects its declared constraints. To debug, set a breakpoint on `_NSViewRemovedDeclaredConstraintBreakpoint`
2021-04-09 02:25:40.475 BLE Sample[25350:586001] Warning: The declared constraints for <NSToolbarItemViewer: 0x7fbeea552f40 'TitleGroup'> were previously invalidated only because a declared constraint was snipped or manually deactivated. This indicates missing invalidation for a view's changing state that affects its declared constraints. To debug, set a breakpoint on `_NSViewRemovedDeclaredConstraintBreakpoint`
2021-04-09 02:25:40.475 BLE Sample[25350:586001] Warning: The declared constraints for <NSToolbarItemViewer: 0x7fbeea54a080 'NavigationGroup'> were previously invalidated only because a decl
	0x1060e848e - /Users/janus/github/xamarin-bluetooth-le/Source/BLE.Client/BLE.Client.macOS/bin/Debug/BLE Sample.app/Contents/MacOS/BLE Sample : mono_handle_native_crash
	0x1060f3ebf - /Users/janus/github/xamarin-bluetooth-le/Source/BLE.Client/BLE.Client.macOS/bin/Debug/BLE Sample.app/Contents/MacOS/BLE Sample : sigabrt_signal_handler
	0x7fff20469d7d - /usr/lib/system/libsystem_platform.dylib : _sigtramp
	0x7fff203618b9 - /usr/lib/system/libsystem_c.dylib : __v2printf
	0x7fff2041420b - /usr/lib/system/libsystem_kernel.dylib : __darwin_check_fd_set_overflow.cold.1
	0x7fff24c881b4 - /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC : __TCCAccessRequest_block_invoke_2
	0x7fff24c889e6 - /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC : __TCCAccessRequest_block_invoke.136
	0x7fff24c8660a - /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC : __tccd_send_message_block_invoke
	0x7fff20169ab8 - /usr/lib/system/libxpc.dylib : _xpc_connection_reply_callout
	0x7fff20169a40 - /usr/ared constraint was snipped or manually deactivated. This indicates missing invalidation for a view's changing state that affects its declared constraints. To debug, set a breakpoint on `_NSViewRemovedDeclaredConstraintBreakpoint`
2021-04-09 02:25:40.498 BLE Sample[25350:586001] WARNING <NSToolbarItemGroup: 0x6000027811d0> -> view was automatically measured but had an ambiguous height or width and the view's frame size had a zero height or width. Did you forget to add constraints on your view or its subview(s)? Try adding constraints or give the view an intrinsicContentSize
2021-04-09 02:25:40.498 BLE Sample[25350:586001] WARNING <NSToolbarItemGroup: 0x6000027811d0> -> view was automatically measured but had an ambiguous height or width and the view's frame size had a zero height or width. Did you forget to add constraints on your view or its subview(s)? Try adding constraints or give the view an intrinsicContentSize
2021-04-09 02:25:40.501 BLE Sample[25350:586001] WARNING <NSToolbarItemGroup: 0x600002781770> -> view was automatically measured but had an ambiguous height or width and the view's frame size had a zero height or width. Did you forget to add constraints on your view or its subview(s)? Try adding constraints or give the view an intrinsicContentSize
2021-04-09 02:25:40.501 BLE Sample[25350:586001] WARNING <NSToolbarItemGroup: 0x600002781770> -> view was automatically measured but had an ambiguous height or width and the view's frame size had a zero height or width. Did you forget to add constraints on your view or its subview(s)? Try adding constraints or give the view an intrinsicContentSize
lib/system/libxpc.dylib : _xpc_connection_call_reply_async
	0x7fff2027a831 - /usr/lib/system/libdispatch.dylib : _dispatch_client_callout3
	0x7fff20293010 - /usr/lib/system/libdispatch.dylib : _dispatch_mach_msg_async_reply_invoke
	0x7fff2028a564 - /usr/lib/system/libdispatch.dylib : _dispatch_kevent_worker_thread
	0x7fff204224e1 - /usr/lib/system/libsystem_pthread.dylib : _pthread_wqthread
	0x7fff20421467 - /usr/lib/system/libsystem_pthread.dylib : start_wqthread

=================================================================
	Telemetry Dumper:
=================================================================
Thread 0x70000416d000 may have been prematurely finalized* Assertion at /Users/builder/jenkins/workspace/archive-mono/2020-02/mac/release/mono/utils/mono-threads.c:650, condition `info' not met, function:mono_thread_info_current,

Configuration
Version of the Plugin: 2.1.1 / current master (1a7536ff0ce6ddc503d19736dd40348b3343e3f9)
Platform: MacOS 11.2.3
Device: MacBook Pro

Hi @janusw,
I'm the friendly issue checker.
Thanks for using the issue template :star2:
I appreciate it very much. I'm sure, the maintainers of this repository will answer, soon.

In my own app, accessing CrossBluetoothLE.Current is enough to trigger the crash.

It turns out that the crash goes away when adding NSBluetoothAlwaysUsageDescription to Info.plist.
Interestingly, Apple's official documentation does not mention that this is needed on Mac OS at all, however I found several references that confim that it seems to be necessary on Big Sur, e.g.:

https://stackoverflow.com/questions/64829740/prompting-for-bluetooth-permission-on-bug-sur-11-0-1
https://developer.apple.com/forums/thread/668174
https://github.com/deviceplug/btleplug/issues/106

Another thing that is a bit strange (and unfortunate) is that there is no proper error message, but just a "crash in native code", which gives no hint regarding its origin.


Create a GSI/global-workflow addon environment

Is your feature request related to a problem? Please describe.
The GSI, GSI_Utils, GSI_Monitor, GFS_Utils, EMC_Verif-Global, and global-wokflow repositories are all using older versions of BUFR (11.7.0) and the EMC_Verif-Global and global-workflow repositories are also using older versions of MET and METplus (9.1.3 and 3.1.1, respectively).
Describe the solution you'd like
An environment has been created under the spack-stack/1.5.1 installations on Hera, Orion, Jet, Gaea, and S4 and an environment template should be created to capture these required libraries.  Additionally, it would be ideal to have this as a downstream environment to the unified-env.
Additional context
The BUFR library is being investigated for a slowdown between versions 11.7.0 and 12.0.0 to see what optimizations can be made.  When completed, the GSI* repositories can be upgraded to use the newest BUFR tag.
The EMC_Verif-Global repository relies on the older versions of MET and METplus and will not go through an upgrade to newer versions.  Instead, the EVS repository is being developed as a replacement (production handoff date 11/19; R&D TBD).  Until then, it is necessary to have these older versions to run the package.

I have created a baseline addon template for the GSI, but am having trouble getting MET/9.1.3 to compile.  The branch is available here.
The error I am getting is during the configure step when it tests the C++ compiler using the -qversion flag, which does not seem to be a usable flag with Intel 2021.5.0, at least on Orion.  The spack build log is available here: /work/noaa/global/dhuber/SPACK/spack-stack/envs/gsi-addon/log.install.  The MET configuration log is available here: /work/noaa/global/dhuber/SPACK/spack-stack/cache/build_stage/spack-stage-met-9.1.3-sn3cqzpksokdmymuginaxskd7sdktkei/spack-src/config.log.
Is there a trick I am missing @AlexanderRichert-NOAA?

I can't see any of the files under /work/noaa/global/dhuber/SPACK/spack-stack/cache/build_stage/spack-stage-met-9.1.3-gvyd6xfyg6uzygfeg4swz4jqxymr56oi, can you change the permissions?

@AlexanderRichert-NOAA Yes, it's opened up now.  Thanks.

Ah yeah I think I've run into this before, it was a 9.1.3-specific problem so I ended up ignoring it. Further down in the config.log, note the ./conftest: error while loading shared libraries: libpython3.10.so.1.0: cannot open shared object file: No such file or directory (also: not all $? = 1 cases in config.log necessarily indicate a failure, sometimes it's just a test like for the -qversion flag but it doesn't necessarily cause ./configure to fail, so it's best to look at the most recent instance).

Actually I partially take that back-- It looks like it's using paths under your gsi-addon directory structure, not the unified-env one. That's pretty weird, I've never seen spack fail to handle that before. In any case I'll keep digging.

Okay, apparently the issue is that python is the wrong dependency type in the met recipe, so the spack rpath scheme isn't working. The fix (which will go into 1.6.0; looks like met is broken in 1.5.1) is to change depends_on("python@3.6.3:", when="+python", type=("build", "run")) to depends_on("python@3.6.3:", when="+python")

Good to know.  Thanks for the hunting, @AlexanderRichert-NOAA!  I'll make that change locally and continue testing.

8-byte builds for ip and w3emc are in spack-stack develop, so they'll be in the next release. To tweak them in the existing configuration, just modify common/packages.yaml, or set those variants explicitly in spack.yaml.

We merged the gsi-addon-dev template last week. There are still issues with the Python version, but as far as this issue is concerned, it's done.


Feedback messages submit style updated instead of give alert.

Description
I've added a message saying 'Thank you for your feedback!' in green color, which appears after submitting the feedback form instead of displaying an alert. This provides a smoother user experience. Additionally, if the user submits the form without selecting any star rating, a message 'Please fill in all fields before submitting.' in red color will be displayed. This immediate feedback ensures that users notice any missing information right away.
Type of PR

[ ] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes]

Checklist:

[x] I have performed a self-review of my code
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Additional context:
[Include any additional information or context that might be helpful for reviewers.]

mention issue number

issue #563


Occasional Unit test failures due to PowerMock

FileReaderWriterFactoryTest#mockDelimitedTextFileWriter will occasionally have issues when trying to mock the FileSystem class. These issues appear to be the same as the documented issue in FileReaderWriterFactoryTest#mockSequenceFileWriter.
Caused by: java.lang.IllegalStateException: Failed to transform class with name org.apache.hadoop.fs.FileSystem$Cache. Reason: org.apache.hadoop.fs.FileSystem$Cache$Key class is frozen

Will you be able to make the fix similar to
49f56938f7a987511d278ef7d1965cb27839a1e0?
On Fri, Nov 6, 2020 at 9:59 PM Jonathan Stein<EMAIL_ADDRESS>wrote:

FileReaderWriterFactoryTest#mockDelimitedTextFileWriter will occasionally
have issues when trying to mock the FileSystem class. These issues appear
to be the same as the documented issue in
FileReaderWriterFactoryTest#mockSequenceFileWriter.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pinterest/secor/issues/1686, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABYJP76EXAVVSOP4RXQIND3SOTO4RANCNFSM4TNOJSOA
.


Remove abstraction layers from EventHubs WebJobs extensions

There are some layers in EventHubs WebJobs extensions that were the artifact of Track 2 refactoring. Remove them to simplify the code a bit.
Major changes:

Merge Processor and EventProcessorHost
Merge ProcessorPartitionContext and Partition, rename to EventProcessorHostPartition
Remove ICheckpointer

/azp run net - eventhub - tests


Issue 2247: powershell_script exit status should be nonzero for syntax errors

See #2247 @jdmundrawala, @smurawski, @btm, @carpnick.
If a script processed by the powershell_script resource has a syntax error, we are returning 0, i.e. success, and the chef-client run will continue with no error even though the script did not actually execute (#2247).
To address this issue, we're going to add an explicit "syntax verification-only" similar to what was proposed in #2247.
Root cause description
The root cause of this entire issue centers around the desire to preserve the quite useful conventions around script exit codes honored by the Unix script interpreters and their associated resources, and even honored by cmd.exe: the interpreter exits with a non-zero error code if the last command (internal or external) executed by the script returned a nonzero exit code OR if the script itself is invalid. The PowerShell interpreter violates this in multiple ways:

powershell.exe -command correctly returns a non-zero exit status (1) if the script is not well-formed, but does not propagate non-zero process exit codes from Win32 processes -- those exit codes are always returned as 1, even if a script is terminated explicitly via PowerShell's exit statement with a specific exit code. There is a pretty large dependency in existing Windows (and non-Windows) cookbooks on exit codes being propagated with full fidelity specifically because this is a very useful convention and there is a significant body administration practice built on it over decades.
powershell.exe -file correctly handles Win32 exit statuses -- if the exit statement is used in the script to set the exit status. Also, it does not propagate cmdlet exit status (i.e the value of $?) nor does it return a non-zero exit for non well-formed scripts. In both cases it will return 0.
powershell.exe in either the -command or -file cases does not support the idea of returning a status code based on a boolean test result as can be done with Unix shells like sh with test and related commands -- this is the feature enabled by the convert_boolean_return attribute for the powershell_script resource.

All of these issues requirements around returning useful status codes according to conventions supported by other interpreters / Chef script resources require explicit code in the powershell_script resource to implement these desired behaviors. Workarounds for all these issues are implemented there, except for the syntax issue, which is addressed by this pull request.
Implementation notes
The following options were considered as solutions:

Continue to launch powershell.exe with -file and find a way to evaluate the syntax without executing the script more than once.

a. The script can be placed inside a script block and then evaluated in a separate `powershell.exe` invocation. **This is the solution implemented in this pull request.**
b. The script can be placed inside a separate file, and then "dot-sourced" via the `.` operator in PowerShell inside the script that Chef actually executes.
2. Switch to `-command` for launching the script and implement workarounds for other limitations of `-command` such as the inability to propagate exit codes.
The drawback of 1a is that it executes two PowerShell processes for each resource invocation instead of one. Advantages are that the -File invocation is also used in currently released versions of Chef Client, so we don't hae to account for regressions due to iodiosyncrasies of -Command, and the fact that this is conceptually simple -- we check the syntax explicitly prior to running the script.
As implied above, a drawback of 2 is that -Command has some subtle differences compared to -File, and there is a risk of those differences causing regressions even if all current specifications pass cleanly. Another issue is that to get the Win32 exit status, we would most likely not be able to rely on Mixlib::Shellout to raise an exception for unexpected return codes; we'd have to simulate such exceptions outside of Mixlib::Shellout in Chef.
Regardless, we can consider how a solution involving -Command would work; it would probably involve doing the following:

Continue using a wrapper script as we do currently.
Insert the user's code into a script block (we do this currently) AND add a line to capture $LASTEXITCODE in a global variable.
Ensure that all exit points of the wrapper script write out $LASTEXITCODE to a file if needed.
After the script is executed by Mixlib::Shellout, retrieve the Win32 exit status from the file
If necessary, from Chef raise the exceptions that Mixlib::Shellout would raise if the returns attribute on the powershell_script resource did not match the process exit code, including what we leared about Win32 exit status from reading the file. This would require simulating the relevant exception behavior from Mixlib::Shellout in Chef.

While approach 1a has the performance drawback of executing PowerShell twice, it has less complexity compared to the -Command approach which has to explicitly replicate Mixlib::Shellout's exception behavior.
Future simplifications
In hindsight, combining the Win32 exit status and other statuses (cmdlet status and boolean result) in the single exit status of the interpreter when executed by Mixlib::Shellout was not worth the complexity it introduced in merging those concepts to make it seem "easy." Instead, the Win32 status should have been tested against a different attribute than returns, say last_exit_code. This would have matched PowerShell's design decision to keep these separate, and would have allowed us the benefits of using -Command, which handles the syntax check while still allowing failed Win32 exit statuses to return a failing (i.e. non-zero) exit code, which is the most common case. The separate attribute would then allow users with the need to test for specific statuses to explicitly test for a particular status code.
So in the future such an attribute could be introduced alongside existing functionality. Then the existing "combined" status could become deprecated and available only in some form of compatibility mode. Eventually, the old combined status could be removed.

@adamedx  1a is the right way to go about this, but instead of launching PowerShell twice, make the scriptblock, if that succeeds, call in Invoke() on it.. This might be a better way of doing all our PowerShell invocations anyway, as it can give us individual access to streams and such.

@smurawski, you're just saying have one script, but do the following?
{
usercode
}
{
usercode
}.invokereturnasis()

Or maybe you mean dynamically generate the scriptblock from within powershell @smurawski ?

Seems like I can do this:
$job = $null
try
{
  $job = register-scheduledjob -name 'syntaxonly' -scriptblock { usercode }
}
catch
{
  # Assume syntax error
}
finally
{
  unregister-scheduledjob $job
}

@adamedx - If you go with your last comment - that is PS3 capable and above.
I found 2 to be ripe with regressions when I did my own implementation of this logic.  So I would discount that immediately.  There are quote issues and many other scenarios I found that were lacking that work fine with -file
1 works well.  I have been toying with the idea of something like this, which suffice for your current implementation.  Cant take credit for it
function Test-Powershell
{
    [CmdletBinding()]
    param (
        [Parameter(Mandatory = $true)]
        [string]
        $Path
    )

    $contents = Get-Content -Path $Path -ErrorAction Stop

    $errors = $null
    $null = [System.Management.Automation.PSParser]::Tokenize($contents, [ref]$errors)

    return ($errors.Count -eq 0)
}

if(Test-Powershell $tempfile){
  #Run code as is today
}
else{
  #Exit with error code that LWRP is looking for.  Might need to doc it or use a special string in the error the LWRP is looking for.
}

Forgot to mention, this would mean write 2 files for every PS call.  One file with your current script code.  2nd one with this wrapper script.  I realize that complicates all the work you have done to return the correct exit code and all, but you might be able to take the wrapper logic and add it to this wrapper instead.  But still some change testing will need to be tested.
I think this is the cleanest way, without multiple processes, to do it though, even if it means integrating another wrapper script.

@adamedx from within PowerShell, read in the script file, create a scriptblock and if that doesn't error, invoke it.. e.g.
$scriptFromResource = gc $pathToScript -readcount 0
trap {write-error 'failed'; exit 1}
$ScriptBlock = $executioncontext.invokecommand.newscriptblock($scriptfromresource)
$ScriptBlock.Invoke()

@carpnick The parser option works, but creating a scriptblock from the content uses the parser, but leaves you (in the case of success) an invoke-able object - allowing you to do it with one call to PowerShell.exe.

@adamedx Invoke or InvokeReturnAsIs (the latter being more efficient) would work.  Not sure off hand if InvokeReturnAsIs is in PS1.

@smurawski - Agreed.  Using the parser option on an external script and then calling it if it parsed correctly is still one powershell call.  Either way - both doing pre-parsing - several ways to skin a cat.

I'll update the pr with some "1-call" options. The specs are there, so if the approach works we should be good.

@smurawski, I'm not actually concerned about ps1, so I think I'll start with your dynamic script block approach. My other variation for that was to dot-source, which has significant problems, but otherwise it handled the use case.

I would say your first phase in this PR @adamedx is good.  We are talking about optimizations down to one process call at this point, if it just works, great, otherwise you still have this as an option.

@btm, @thommay, can we get this in after 12.3?

There's an existing pattern of tests here without an expectation. They fail appropriately because an exception is raised, but I think the tests are easier to understand with an expectation.
Otherwise looks good. :+1:
@chef/client-windows, review?

:+1:

:+1:

None of my comments where a big deal btw, so this is ready to merge now. Someone could clean up the tests or whatever if they felt so inclined.

@adamedx says he's going to incorporate some feedback before merge.

@chef/client-windows re-review please.

:+1:

Actually... my white-hat spidey senses just went off...
With this functionality, are we saying that the powershell_script provider won't run/produce any side effects on an invalid script?  What about the script " }; rm -rec -force C:\Windows; { "

It might produce such side effects @ksubrama, but remember you're already running as admin, so you could just write a script that said rm -r -force c:/windows.

The bad case @ksubrama would be if you took input from an unprivileged source and inserted it into your script. Again, that can be done with a perfectly valid script unrelated to this particular change.

True...  and presumably you shouldn't run scripts that you don't trust.  I guess this is more of a "We'll attempt to catch syntax errors in your PS file and raise but if you solely depend on Chef to validate your script, you might suffer some side-effects."

Merged in 6362e96e3b71484e68eb3296c6743d592e78f3a7


fix(component extension): Debugging issues with component extension

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


ux: hotjar observations

This is a list of observations made via the hotjar recordings feature during our initial testing phase:

Some testers did not understand that they need to drag the elements from the drawer into the content, or it happened by accident
People understood much quicker what they need to do once they had to explicitly launch the editor
Having the toolbar active from the start resulted in people trying to edit / move stuff right away, before (sometimes) resorting to the toolbar on the right
Mobile experience needs much improvement
Some users tried to move layout cells as well
Some users double clicked on content to make it editable before noticing the edit thing

Resulting tasks:

[ ] Instead of starting in preview mode, start with edit mode
[ ] Improve the drawer drag & drop. Maybe have insert toggles instead (like on squarespace)?

Instead of starting in preview mode, start with edit mode --> is implemented in 0.15.0
Improve the drawer drag & drop. Maybe have insert toggles instead (like on squarespace)? --> would be nice, but i close for now to keep issue count low.