feat: show when new version is available

Closes #178
Limitations: If you are currently using a pre-release version, this does not check for an update. We could improve this in the future.
Verification Steps

Build the CLI with a version which is below the current latest version:

RHOAS_VERSION=0.1.0 make binary

Run any command in debug mode OR login.

$ ./rhoas version -d
rhoas version 0.1.0

A new version of rhoas is available: 0.22.2
https://github.com/redhat-developer/app-services-cli/releases/tag/0.22.2

❯ ./rhoas login
Logging in...
Logged in successfully
Logging in to MAS-SSO...
Logged in successfully to MAS-SSO

You are now logged in as "craicoverflow"

A new version of rhoas is available: 0.22.2
https://github.com/redhat-developer/app-services-cli/releases/tag/0.22.2

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation change
[ ] Other (please specify)

Checklist

[x] CI and all relevant tests are passing
[ ] Code Review completed
[ ] Verified independently by reviewer

👁

I've added it to the version command now too.


Supported browsers and versions

I cant find any information about what the browser support is like for this project.
I am currently creating my own simple css grid system and would like to suggest to people who use it, to use your navigation, but unsure what to say is supported.
Many thanks in advance.

Hi, right now it's tested on every major browser(safari, chrome, firefox) however there is a minor bug on chrome for windows, for more info see (this)[https://github.com/balzss/luxbar/issues/5 ])

Thanks for the reply.
I was actually more interested in for instance if someone was running for instance a very old iphone or android phone, if it would behave itself and if not how it degraded. (I hope this makes sense.)
For my needs I simply need something that only is single tier and expands and collapses on very small screens. Im also looking for something light and that does not need JS or JQuery, but would work on older browsers.. From the demo this looks great and for me its a toss up between this and the menu component of pure.css

Oh OK. So the CSS features that might be unsupported are flexbox and maybe translate. As far as I know it works fine on old phones if the browser is updated but I'm not sure how regularly it's done on stock browsers. I hope this helped.


Made a note to drop some types when a TS bug is fixed for NamedNodeMap.

Relates to #1735. Just added a note to remove some types we merge on once TypeScript ships with a fix for https://github.com/Microsoft/TypeScript/issues/30928.

I thought we were gonna drop TODOs, not add more :P

Yeah, wasn't trying to clutter up the code with another TODO, but I thought this one merited a TODO. 😉


Optimize RunLineHelper in BufferedInputStream

The old implementation of ReadLineHelper will append chars one at a time to the tstring result, which may cause multiply memcpy or reinitialization. This PR change from using
tstring& append(size_t n, char c)

to
tstring& append(const char* str, size_t len)

to append multiple chars once.
This optimziation will help TextlineDataset which iteratively calls ReadLineHelper.
Thank you for your time on reviewing this PR.

@zhuzilin  Can you please check @allenlavoie's comments and keep us posted ? Thanks!

@gbaned Sorry... I missed the email alert for this...
@allenlavoie
I'm not sure how to use result->reserve to simplify the logic. The logic is:

If we read to the end of the buffer, we need to append the remaining to result and refill the buffer.
If the current character is \n we need to append to it and return.
skip \r.

I've removed all the if (start_pos != pos_) because I found that there is already an early return in append when the appending string is of zero length. Would this make the code a little better?


PullSecrets are not applied to configchecker from Agent Spec

Specifying imagePullSecrets in config check pod is not possible, which make the whole thing not working when using private repositories.

Hi @bartekle! Thanks for the issue.
I'll take a look soon at how to set up passing imagePullSecrets to the configCheck pods.

Fixed in v0.0.31 release


BUG: fix uninitialized use in lartg 0.16 backport

lartg returns the cosine as a double leaving the imaginary part
uninitialized while the code assumes it is a valid complex number.
Fix this by initializing the number. This fixes test failures on i386
and removes a bunch of valgrind errors.
backport of gh-5193

I was going to suggest we defer all backporting to the RM, but heck, when Ralf comes back online, he'll have enough on his plate. This looks good to me, so in it goes. Thank you Julian.


New package: Geeks3D.FurMark version <IP_ADDRESS>

Description

Resolve #137134

Checks

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

/AzurePipelines run

This may happen for URLs pointing to domains that do not align with the publisher domain or package domain.

This is intended, as the official download URL blocks third-party automatic downloading. We have to use another link posted in their forum.

See https://github.com/microsoft/winget-pkgs/issues/137134#issuecomment-1918481344
See https://github.com/microsoft/winget-pkgs/issues/137134#issuecomment-1918931138

See https://github.com/microsoft/winget-pkgs/pull/137299#discussion_r1473779991

This PR also resolve #137775

/AzurePipelines run

@wingetbot waivers Add Validation-Domain


Sailfish OS support

I want to run the flutter application on sailfish operating system.

The home page says it's fully compatible with Android applications https://sailfishos.org/
Were you not able to run an app on your OS?

What will happen to Google services Turkey does not work?
Google services may be interrupted at any time.

I'm thinking of creating an Android open source project or sailfish OS devices.

@phanirithvij  I think the sailfish operating system does not have vulcan support.


fundle init --profile should display time in microseconds (ms)

Actually it displays in "us" lol
That's confusing and hard to read
.config/fish/fundle 1: 23430us

ms is short for milliseconds, not microseconds.
microseconds is normally written as "μs", but I prefer to stick with non-extented ascii in a shell environment, so the closest I could get to is "us". I have no strong opinion on this, so if you would like to change it to "μs", please send a PR.
Thank you.

I meant it should display in milliseconds, not microseconds :P


pui-react-tools doesn't seem to contain the update including vinyl

This is quite a useful project.
Currently, if you download, install and run as is (git close + npm install + gulp) the build shows an error for a missing vinyl dependency in the pui-react-tools module.  It looks like there is a commit in that repo to include vinyl, but the change doesn't seem to have made it's way into the npm install for this project.
Stacktrace:
module.js:340
    throw err;
          ^
Error: Cannot find module 'vinyl'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/Users/marlena/Github/react-starter/node_modules/pui-react-tools/assets/assets.js:10:12)
    at Module._compile (module.js:456:26)
    at Module._extensions..js (module.js:474:10)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/marlena/Github/react-starter/node_modules/babel-core/node_modules/babel-register/lib/node.js:138:7)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/Users/marlena/Github/react-starter/node_modules/pui-react-tools/index.js:4:11)
    at Module._compile (module.js:456:26)
    at Module._extensions..js (module.js:474:10)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/marlena/Github/react-starter/node_modules/babel-core/node_modules/babel-register/lib/node.js:138:7)

I thought the most recent version of pui-react-tools (0.0.5) has fixed this, will look into it. We should be updating it shortly regardless.
In the short term, you can add vinyl yourself npm install vinyl --save-dev
The project is still a work in progress, suggestions are very welcome.

should be fixed now


Enable secure grpc++/grpc deps and ssl features on s390x

Since boringssl has not been supported on s390x yet, @com_github_grpc_grpc//:grpc_unsecure and @com_github_grpc_grpc//:grpc++_unsecure deps used to be chosen when building TensorFlow on s390x.
However, we can enable secure grpc++/grpc deps and ssl related features for TensorFlow on s390x via openssl by using TF_SYSTEM_LIBS="boringssl" flag in bazel commands.
This PR aims to enable the above-mentioned features on s390x by removing the specific grpc_unsecure and grpc++_unsecure deps from BUILD files and adding the TF_SYSTEM_LIBS="boringssl" flag as a default option for Bazel during the configuration stage on s390x.
After applying the above change, the following test cases would pass on s390x:
//tensorflow/core/platform/cloud:compute_engine_metadata_client_test
//tensorflow/core/platform/cloud:compute_engine_zone_provider_test
//tensorflow/core/platform/cloud:curl_http_request_test
//tensorflow/core/platform/cloud:gcs_file_system_test
//tensorflow/core/platform/cloud:google_auth_provider_test
//tensorflow/core/platform/cloud:oauth_client_test

Fixes https://github.com/tensorflow/tensorflow/issues/51770 .

Thanks @sagunb !

Looks like the following error shown in the PR checking logs wasn't caused by the code change in this PR:
external/llvm-project/llvm/include/llvm/IR/Attributes.h:91:14: fatal error: 'llvm/IR/Attributes.inc' file not found
    #include "llvm/IR/Attributes.inc"
             ^~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.

@sagunb @Neilblaze Could you please help me check the status of this PR? Please let me know if there is any change I should make at my end. Thank you very much!

@gbaned Thanks for checking!


better ignoring / of errors

In relation to #606 i'd like to see some way of ignoring any type of error or exception ...
Currently some errors are ignoreable via the shouldCaptureFatalError() function. But shouldn't the handleError and handleException have the same option to exclude some error / exception?
By way of i.e. 'shouldCaptureError' and 'shouldCaptureException' (and maybe keep the
'shouldCaptureFatalError' for consistency sake?
The code change seems fairly simple, but before i hack in a PR, i'd like to question why the original issue #606 and subsequent PR #583 deliberately didn't go for a wider solution to allowing ignoring every type of exception / error... ?

As of now, we have the 2.0 branch under development, where a single before_send callback would be used as a stopgap for any kind of event ready to be sent to Sentry. Would this solve your need?

deliberately didn't go for a wider solution to allowing ignoring every type of exception / error... ?

I may be missing something but, at least in 2.0, the excluded_options uses instanceof which means that you can catch all types of errors or exceptions by configuring it using the base classes \Exception or \Throwable

@Jean85  @ste93cry I am currently using a 1.x version of the client as the 2+ isn't (officially) released yet...
If the before_send callback is there this would 'fix' my issue comepletely! Excellent...
As for the excluded_exceptions, this wouldn't catch non exception errors thus the before_send seems like the only proper way to solve this issue :)
Thanks!
Any timeline available for 2.x?

I am currently using a 1.x version of the client as the 2+ isn't (officially) released yet...

Sorry, I know less the 1.x version but AFAIK the behavior of the excluded_exceptions was ported there from the 2.0 version so they should work the same

As for the excluded_exceptions, this wouldn't catch non exception errors

Since PHP 7 some errors can be catched because they are thrown as exceptions

Any timeline available for 2.x?

I think that it should be ready for the end of the year, maybe before. You should ask @HazAT that knows the timeline better than me

Yeah, plan for 2.x is to ship before EOY.

@fruitl00p I just saw that 1.x has a send_callback option that you can use to do whatever you need before an event is sent including not sending it at all if you return false from it. I think that that with the combination of excluded_exceptions should be enough, can you check and let us know if it helps you fix your issue?
https://github.com/getsentry/sentry-php/blob/7b7e88d93027c4f149c3cb5e929b3b9f8427e01c/lib/Raven/Client.php#L1035-L1040

@fruitl00p I just saw that 1.x has a send_callback option that you can use to do whatever you need before an event is sent including not sending it at all if you return false from it. I think that that with the combination of excluded_exceptions should be enough, can you check and let us know if it helps you fix your issue?
https://github.com/getsentry/sentry-php/blob/7b7e88d93027c4f149c3cb5e929b3b9f8427e01c/lib/Raven/Client.php#L1035-L1040

@ste93cry Excellent! This works like a charm and gives me full control over exactly what is eventually sent and if it's actually sent at all!
Great!


uar-384 log & exclude ceased

JIRA link
Bug fixing https://companieshouse.atlassian.net/browse/UAR-384
Change description
Work checklist

[ ] Tests added where applicable
[ ] UI changes meet accessibility criteria

Merge instructions
We are committed to keeping commit history clean, consistent and linear.  A BREAKING CHANGE can be part of commits of any type,
types other than fix: and feat: are allowed, for example build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others,
footers other than BREAKING CHANGE: <description> may be provided.

unit test(s) probably need added

unit test(s) probably need added

MO will be done by MO review tickets. Did not have prior conevrage.


[Mutator] latest OLStats is 3.09

Only v3.01 can be found.
The latest version is 3.09 and it can be found here (along with all the versions between 3.01 und 3.09):
https://www.dr-lex.be/software/olstats.html
Upload failed with a 'No new content found' error message, probably because 2 of the 3 .u files inside the archive are identical to 3.01, only OLStats.u was changed.

Added: https://unrealarchive.org/mutators/unreal-tournament-2004/O/olstats_d01c76ad.html


USDM_CT: Encounter.encounterContactMode needs updating in valid value sets

"DDF valid value sets" sheet has a Encounter.encounterContactMode attribute
"DDF Entities&Attributes" references Encounter.encounterContactModes (this matches the EAP)
The "DDF valid value sets" reference needs updating

@glow-mdsol - since we are now in internal review we are tracking comments using the JIRA system.
I have therefore transferred this comment to https://jira.cdisc.org/browse/DDF-397

Thanks!

Thanks!


Negative numbers

Good day, I get an issue for such case. Package doesn't recognize this like a magic number
$limit = Carbon::now()->addYears(-123123);

Interesting that with the second example works fine
$limit = Carbon::now()->addYears(123123);

As I understand it's bug or I'm wrong

Hey,
Thanks for the issue!
Apparently, you are correct, it is a bug:)
Do you want to contribute? And this one? :)
Regards

This looks to be resolved now so the issue can be closed ?


Dataset iterator support for dynamically created training samples

Currently, you can only pass in static numpy.ndarray objects for training.  Ideally, these could also be generated on the fly, e.g. mirroring/jittering/scaling/rotating input images during training.
The Iterator pattern has been applied in other similar libraries in various languages, so it could fit well here.  This would need to be compatible with PyLearn2 so minimal redundant work is done outside of the library...

#23 is probably a sensible thing to do first, then generalize.  Provide a sknn.dataset module for this purpose?


Donations chatbot

What's this PR do?
This isn't a completely 100% dev complete Science Sleuth, but it does submit donations to the DC API, and it's quite a bit of changes - so merging intodevelop now to keep future pull requests readable.  Here's what's going on:

Refactors Donors Choose Science Sleuth donations to use a single endpoint: /donations/donors-choose, inspired by how custom Slack apps use a single Action URL to implement custom actions.

Removes now deprecated endpoints and related functions

/donations/donors-choose/start
/donations/donors-choose/retrieve-firstname
/donations/donors-choose/retrieve-email
/donations/donors-choose/retrieve-zip

Removes unnecessary donation controller interface code to simplify codebase

Refactors Donation MoCo Campaigns to use 3 OIP's: 1) Start 2) Chatbot and 3) Conversation Ended.

We now store the majority of conversation content into new dcConfig variable instead of legacy convention of storing a collection of OIP's (where we'd set conversation copy in each OIP's conversation settings, ad need to set relevant mData's, e.g. #546).  The desired dcConfig message is stored to the MoCo slothbot_response Custom Field and displayed via Liquid within our OIP conversations (refs #537)

dcConfig object will be refactored as a new config document (see todos section)

Adds new helper functions for sending SMS messages:

respondAndListen(member, messageText, customFields) - opts the member into the Chatbot OIP and saves the messageText to the slothbot_response MoCo custom field. The Chatbot OIP will post back to our endpoint to continue responding to the member

respond(member, messageText, customFields) - opts the member into the Conversation Ended OIP, which does not post to an mData.

Stores required user donation info into Mobile Commons custom fields (email, first_name, and postal_code) if values don't exist, instead of storing in donation_infos documents

Changes flow to prompt for all member information first. When we have all information stored, query for closest project and donate. This closes #550 and closes #567 -- if donation fails, we can start over without worrying about incomplete donation_infos documents and fetching an incomplete donation

Stores count of user donations as a Mobile Commons custom field instead of the sg_users document corresponding to the user, removes now deprecated functions like incrementDonationCount. The new ss2016_donation_count MoCo Custom Field  is updated within sendSuccessMessages (which may make sense to rename as something like respondWithSuccessConfirmation)

Alters app.json to require less config variables. I changed our Heroku pipeline so that Review Apps are cloned from staging instead of production (#555)

How should this be reviewed?
Pull down locally and post to the /donations/donors-choose endpoint. You can mimic the conversation flow by posting additional body params along with the phone:

profile_postal_code
profile_first_name
profile_email

Any background context you want to provide?
Looking to simplify our configuration by using the 3 OIP's for a whole Donation campaign, with slothbot_response as Liquid instead of keeping track of multiple OIP id's (and making sure each OIP is configured with the correct mData in MoCo), which introduces many opportunities for configuration errors. Especially since we need two functional donation campaigns, one for production and another for staging.
If this turns out to be a terrible idea, we can revert back to 1.1.1, which uses individual OIP's for each message within the conversation (Request Email, Invalid Email, Request Zip, Invalid Zip, Request First Name, Donation Successful 1-3, etc)
Relevant tickets

#539 - simplifies creation and maintenance of staging and production Donation MoCo campaigns

closes #567: Don't have to worry about filtering donation_infos documents for this year's run because we're only creating documents for completed donations, and inspecting a MoCo custom field value instead of anything in Mongo

closes #550 and closes #559: Avoid gotchas by immediately donating to project once it's found (vs storing a project but not donating until a few steps later in the conversation) , hopefully right track for ways to help #463

closes #552: Don't prompt for zip, first name, and email on subsequent donations because we'll have them stored to MoCo profile already

todo

[ ] Update documentation
[ ] Store completed donations into the ds-mdata-responder database, probably in a new donations_donorschoose collection instead of existing donation_infos
[ ] Add docblocks, fix up legacy variable declarations to adhere to best practices
[ ] End conversation with messaging if member has reached maximum # of donations
[ ] Add secret Clean Slate keyword to clear out your first name, email, and zip code to easily test and re-test whole Donation conversation
[ ] If user's 2nd+ donation, inform them we're finding a new project to donate to based on their zip code (e.g. We already have your zip (87101), so we're sending your donation to Mr. White's Beakers for Believers project at Albuquerque High School)
[ ] Create staging/production instances (currently hardcoded to single campaign)
[ ] Modify donorschoose config collection:

[ ] store new conversation msg_ variables instead of conversation OIP's
[ ] Store OIP's as properties in the config document of respond and respondAndListen

Before
OIPs
(Note -- still missing an OIP if we wanted to display messaging for invalid emails)

Sample OIP conversation

After
OIPs

Sample OIP conversation


Fixes small grammatical error/typo in using-query-parameters-to-create-a-pull-request.md

Why:
It's a grammatical error/typo.
"a" should be used before a word that starts with a consonant sound.
What's being changed (if available, include any code snippets, screenshots, or gifs):
Before:

and an pull request title

After:

and a pull request title

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@VictorIreri Thanks so much for opening a PR with this fix! I'll update the branch and get this merged once tests are passing 🍏


Fix DPA reconcile on empty BSL secret name and key

This PR addresses:
https://issues.redhat.com/browse/OADP-2940
I added coverage for fail DPA reconcile on empty BSL credential name and key.
Also, I fixed the logic condition which was not accurate.
I added 4 more unit tests for more coverage.

/ok-to-test

/hold
this issue has been kicked out to 1.3.2

/retest

to add to this PR: https://github.com/openshift/oadp-operator/pull/1220#pullrequestreview-1719036142 for 1.3.2

/retest

anybody know what  Context retired without replacement. means? Looking around don't see any reference

/retest

anybody know what  Context retired without replacement. means? Looking around don't see any reference

See here

/cherry-pick oadp-1.3

/lgtm


Add Bugsnag Import

Resolved #1714

:tada: This PR is included in version 5.3.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Handling SIGINT and SIGTERM system messages

When using castor-core in docker, SIGTERM or SIGINT system message will be sent to nodejs process when docker want the process to be stopped.
I think this code could help to cleanup the application and quit faster (without that, docker wait few seconds before killing hard the process)
I don't know exactly where this code should be put (in starter.js ?) and maybe it should also take care of closing mongodb connections and/or http server connections before process.exit(1).
// exit on CTRL+C
exitOnSignal('SIGINT');
exitOnSignal('SIGTERM');
function exitOnSignal(signal) {
  process.on(signal, function() {
    console.log('Caught ' + signal + ', exiting');
    process.exit(1);
  });
}

 Permettre de stopper l'application avec un CTRL+C

I don't think exitOnSignal() is a nodejs function.
But one could use process.on('SIGINT')

@parmentf

function exitOnSignal(signal) {
process.on(signal, ...)
}

:+1: I need to learn to read. Or to sleep more ;)


improve logic when we import tests with transformers fixes #761

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.

Merged.
Thanks for your contribution !


Implement Peripheral Device Locking Feature

Description of the new feature / enhancement
Introduce a feature to lock peripheral devices such as mice and keyboards, with the exception of registered hotkeys or shortcuts. This feature aims to prevent unintended input from peripherals, particularly in scenarios where physical objects are placed on keyboards or where external factors cause inadvertent keypresses.
Proposed Functionality

The locking mechanism would be triggered by a designated hotkey combination or through the PowerToys interface, with the 'Scroll Lock' key serving as the default trigger.
Once activated, the lock would prevent any input from designated peripheral devices, except for specified hotkeys or shortcuts.
Users would have the flexibility to configure which peripheral devices are locked and define exceptions for specific keys or combinations.
Visual indicators or notifications would communicate the activation status of the lock to the user.

Scenario when this would be used?
Consider a scenario where a user is working with physical documents placed on top of their keyboard. Inadvertent keypresses occur when objects such as pens or notepads press down on keys, disrupting workflow.
By activating the peripheral device lock via PowerToys, triggered by the 'Scroll Lock' key, the user can temporarily disable input from the keyboard while still retaining functionality for essential shortcuts or hotkeys.
This feature enhances user productivity and minimizes interruptions caused by unintended peripheral input.
Supporting information
No response

/dup 21313


raising precision of custom wakeword

I'm curious whether the precision of custom wakeword improves if you provide more sound files, e.g. 50 files from different people? or is that meaningless?
We want to use a custom wakeword for a public interaction system, and want it to recognize voice input from a wide range of people (young&old, male&female, etc).
Thank you for letting me know.

Exactly, the more amount of variety in samples, better the model accuracy. And also keep an eye on the threshold, change the value of it according to your requirement.

Thank you for clarifying! I will try out with about 20 samples to start with and see how it goes.
About the threshold value, it does not seem to be taken into account by the checkFrame method: https://github.com/Ant-Brain/EfficientWord-Net/issues/9#issue-1142751467

rather than just increasing the samples , consider increasing the variety of the samples that might work


fix: bitcoin send all

Try out this version of the Hiro Wallet - download extension builds.

Addressing: https://github.com/hirosystems/stacks-wallet-web/pull/3068#issuecomment-1422541911
This fixes subtracting pending txs balance from the Send all button for both STX and BTC. The current functionality was broken in that it never checked for if the account address was sending or receiving, but it always subtracted out the balance. I think STX txs moved so quickly from pending to microblocks that we never noticed.
cc @markmhx I don't think we ever intended to add incoming pending txs to the balance, did we? We never have with STX. Currently, txs in a mircoblock show an increased subBalance as a caption in the balance list but it doesn't add to the send max balance value in the send form.
I can change that here if we want to?

@kyranjamie should I merge this into your branch?


Config in templates are not DB specific

TODO
Provide option in init command to choose from database, and accordingly generate config for it. Current default config are postgres specific.

love it!


Error Section for Scan QR code screen

Acceptance criteria:

[ ] if user scan the QR code and the app is not found
[ ] if the user scan qr code and This app is running in the testing environment (Check detail with jack)
[ ] If the user scan the invalid qr code
[ ]
For more detail check the document section :
Qr Scanner error messages
https://docs.google.com/spreadsheets/d/1fwrxPl_pJYudji7gNIhULAKUwunMtk4Wm2Y_9KnzOeM/edit?gid=0#gid=0&range=A578:D578

1. if user scan the QR code and the app is not found
this is and should be thrown on the accounts website, not in the app here:
https://github.com/Tonomy-Foundation/Tonomy-App-Websites/blob/master/src/accounts/pages/Login.tsx#L233
this error is thrown:

https://github.com/Tonomy-Foundation/Tonomy-ID-SDK/blob/master/src/sdk/services/blockchain/contracts/TonomyContract.ts#L377 or
https://github.com/Tonomy-Foundation/Tonomy-ID-SDK/blob/master/src/sdk/services/blockchain/contracts/TonomyContract.ts#L392 or
https://github.com/Tonomy-Foundation/Tonomy-ID-SDK/blob/master/src/sdk/services/blockchain/contracts/TonomyContract.ts#L412

we should ask Pavel to redesign this page for when the app is not found. The screen should happen after this one: https://www.figma.com/design/Enit7SHcGKiYULpi51Hg36/Accounts-website?node-id=1-4337&t=MizVMBOGHzywg146-4
2. if the user scan qr code and This app is running in the testing environment
currently we cannot test this as we don't know the schema of the other Pangea/Tonomy apps. so this is indistinguishable at the moment fro #3 so just treat it the same as #3
3. If the user scan the invalid qr code
error thrown:

https://github.com/Tonomy-Foundation/Tonomy-ID-SDK/blob/master/src/sdk/util/qr-code.ts#L19 or
https://github.com/Tonomy-Foundation/Tonomy-ID-SDK/blob/master/src/sdk/util/qr-code.ts#L13

you can see this is already handled here https://github.com/Tonomy-Foundation/Tonomy-ID/blob/development/src/containers/ScanQRCodeContainer.tsx#L147 (this should be updated to the new UI)

design changes remaining:

point 1 needs a new design within the Apps website


[SPARK-38345][SQL] Introduce SQL function ARRAY_SIZE

What changes were proposed in this pull request?
Introduce SQL function ARRAY_SIZE.
ARRAY_SIZE works the same as SIZE when the input is an array. ARRAY_SIZE raises an exception for non-array input.
Why are the changes needed?
Counting elements within an array is a common use case. ARRAY_SIZE ensures the input to be an array and then returns the size.
Other DBRMS like Snowflake supports that as well: Snowflake ARRAY_SIZE. Implementing that improves compatibility with DBMS and makes migration easier.
Does this PR introduce any user-facing change?
Yea. array_size is available now.
scala> spark.sql("select array_size(array(2, 1))").show()
+-----------------------+
|array_size(array(2, 1))|
+-----------------------+
|                      2|
+-----------------------+

scala> spark.sql("select array_size(map('a', 1, 'b', 2))").show()
org.apache.spark.sql.AnalysisException: cannot resolve 'array_size(map('a', 1, 'b', 2))' due to data type mismatch: argument 1 requires array type, however, 'map('a', 1, 'b', 2)' is of map<string,int> type.; line 1 pos 7;
'Project [unresolvedalias(array_size(map(a, 1, b, 2), None), None)]

How was this patch tested?
Unit tests.

May I ask for a review when you are free? Thanks! @cloud-fan @gengliangwang @MaxGekk @entong

Pardon me for one last rebase in order to update sql-expression-schema.md.

There are compilation errors.

thanks, merging to master!


Added proper handling for back button on Android

With this PR, the back button will exit to the homescreen without stopping Kivy, just like the home button.
I think this is correct behaviour because, although SDL2 maps the back button to the esc keycode, it doesn't have the same implications as on the desktop. That said, I just threw this together from the code in my own app and have made the PR to raise discussion, the best solution may not be the same as this.
Something definitely needs changing, as right now kivy halts without informing Android, so it appears to have crashed and will raise an error popup when the user navigates back to the app.
Edit: I also haven't tested this exact code, even if you really love it then that needs doing before merging.

I'm not sure if this is a good idea, because it reminds me some of the games made with Unity which didn't have back button implemented at all and the only thing that could be done was using home button, which only paused the game and left a lot of stuff in memory (not sure for how long or if it is removed later, I just purged it with force). With Kivy there's always packaged the whole interpreter, so what would happen if there were more Kivy apps on a phone with this behavior launched one after another and exited only with home button (the new back button behavior)?
Will be everything collected from memory, or will it hang there and if, for how long? Leaving app paused is a good thing (with home button as an intentional pause), yet I expect a back button to exit the app, not just put it in background.

With Kivy there's always packaged the whole interpreter, so what would happen if there were more Kivy apps on a phone with this behavior launched one after another and exited only with home button (the new back button behavior)?

Android would quietly halt the app and reclaim the memory if it ever needs it. This is the recommended Android activity model.

What about data loss while paused and the memory would get reclaimed? I haven't really poked into how Java apps handle the back button, but if there's no real danger making the back button behave like that, I'm for that. Except the potential memory & data issues I mentioned it can only bring the good stuff such as quicker loading (if in memory) and converging to the Java Android app model. 👍

When the app is paused, it gets a few seconds to store data (via
onPause), but after that Android provides no guarantee that it will ever
run again. It is expected as part of this execution model that if you
don't save data, it may be lost.
On 15/10/16 00:32, Peter Badida wrote:

What about data loss while paused and the memory would get reclaimed? I
haven't really poked into how Java apps handle the back button, but if
there's no real danger making the back button behave like that, I'm for
that. Except the potential memory & data issues I mentioned it can only
bring the good stuff such as quicker loading (if in memory) and
converging to the Java Android app model. 👍
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kivy/kivy/pull/4670#issuecomment-253943807, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABNQmxldiTq7jR40bIJSmANJIDSMNyvOks5q0BEegaJpZM4KXgqr.

Will it be possible to cleanly exit without pausing when the back button is pressed?

@inclement in the standard Android Activity model, when you press back button, Activity's onDestroy() is called and activity is killed. Only when you'll override onBackPressed(), you can achieve behavior from the PR. While I like it, it is not the default that Android activities are working like.
@dessant to achieve that you'll need to bind to Window's on_keyboard, and from there call app.stop() when key 27 is pressed.

I again feel this is not a good idea mainly because of Activity lifecycle:

There are a few scenarios in which your activity is destroyed due to normal app behavior, such as when the user presses the Back button or your activity signals its own destruction by calling finish().

When your activity is destroyed because the user presses Back or the activity finishes itself, the system's concept of that Activity instance is gone forever because the behavior indicates the activity is no longer needed.

These quotes show that the current behavior of back button in Kivy app is actually the most accurate if compared to the Java Android app.

@inclement, @KeyWeeUsr: so, was it settled? 😋

Well, all apps seem to have back button to exit/close an app, even android seems to do so in its docs, so I don't feel it's a good change. Let's leave this behavior to Home button.

I realise I was wrong about this being the most correct thing to do according to the docs, but I still think we should consider it - it seems that one reason for the java model is that the java ui can be quickly regenerated, but restarting a Kivy app means completely restarting the python process which is very slow. I think apps like games often override the back button in the same way, presumably for the same reason

But this way everything remains as if the app was paused, which just kills everyone else's app that might depend on cleaning the environment properly each time. Maybe a better approach would be a property set in App.build() or in config.ini?

It should be toggleable, but I'm not sure there's really a concern about
killing other peoples apps - it depends on how Android decides what to
halt, but it seems more likely that the Kivy app would be the first one
killed if it's consuming resources disproportionately.
On 16/12/16 20:24, Peter Badida wrote:

But this way everything remains as if the app was paused, which just
kills everyone else's app that might depend on cleaning the environment
properly each time. Maybe a better approach would be a property set in
|App.build()| or in |config.ini|?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kivy/kivy/pull/4670#issuecomment-267687688, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABNQm0KbBgc2bwUcfQOF9PC5ZOIV8DZVks5rIvOGgaJpZM4KXgqr.

Ah, bad wording. Let's say you make a casual application, not a game. You have there some variables that need to reset each time an App starts e.g. you fetch some token, get a key from url or something. This change doesn't allow the app to exit properly, only relies on Android taking care of it and

... that if you don't save data, it may be lost.

in the worst case Android might even restore the data e.g. if you have on_pause enabled, press home button and quickly run the app again. I see the same thing I left it when paused. When a user works with files it might be even less desirable just as out-of-box feature. That's why if it should be included, let user decide how to handle this stuff with Config.

I think this idea makes sense since Kivy app starts much longer then Java-based Android apps.
On other hand if app uses to process files, this PR right now may lead to crush.

What about Config.set('kivy', 'pause_on_minimize', 1)? Wouldn't be better to reuse this functionality to pause the app instead of making back button behave as the second home button?

@KeyWeeUsr that's more about pausing the event loop or keeping it runnig, but you don't have a choice for that on mobile afaik. Respecting exit_on_escape might be a better fit.

I meant something like this:
if WindowBase.on_keyboard.exit_on_escape:
    if key == 27 or all([is_osx, key in [113, 119], modifier == 1024]):
        if not self.dispatch('on_request_close', source='keyboard'):
            if platform == 'android' and Config.getbool('kivy', 'pause_on_minimize'):
                # back button on Android should not be treated
                # the same as desktop's ESC
                from jnius import autoclass, JavaException
                .
                .
                .
            else:
                stopTouchApp()
                self.close()
            return True

Which basically means a user would have an option to toggle this functionality.

There isn't a way to signal in java that the app wants to exit now instead of waiting for the process to be stopped by android?

@KeyWeeUsr, yeah, but if we do that it just means we hide the bug by default instead of fixing it, just like the pr does in its current form. I agree about this being an undesired change.

It's not a bug, it's just Kivy being loaded a little bit more than desired, which I think we can't really do anything about it except attempt to hide it like in this PR or on_pause->return True or another alternative.
I do agree that it's not nice to have hanging app just because it loads long enough for an end-user to notice and if I had some big app with Kivy I'd probably make it pause by default too, but there shouldn't be just a big switch from a common android behavior to pausing everything just because Kivy can become a loading beast similar to Unity if you really want to make it so.
Hence the bool option. Maybe pause_on_minimize isn't the best choice and another variable directly related to this functionality would be better.
Also, about the signal in java, I don't know anything except finishActivity() and system exit(like exit() in py), which probably won't help here.

Just came across this during my deep dive into the p4a bootstrap behaviors. As someone who's been using cross-platform toolkits for many years now, I've found that I always want to be given the choice of what to do in my app code. e.g. I'd just like to have some on_back_key event or on_android_back_key to stress that it's an android-specific callback. If the callback isn't handled, then close the app.
The 'close the app' behavior is generally correct in the case when you're at the app's home screen, but, for example, if you're building an ebook reader and the user has started reading a book, users would probably expect the back key to take them back to the book list. It also serves as a "go to previous screen" button. That's how Kindle, Chrome and the Settings app works.
Once that callback is available, devs who don't want their app to fully close on back would have the choice to change that behavior as well. And then if they get complaints about users that back should close the app and free resources, then they can change it back too. ;)

I just wanted to say; I do not like the idea of Config setting as compared to a method or callback. Callbacks give you the power to be dynamic like in the e-reader example above. But the Config settings are hard coded and can not be changed after loading Kivy.

Current setup allows you listen to escape key like so and specify your own behaviour of what to do? Go Back in Screen Higherarchy or to pause app  like so
or to follow the default behaviour of closing the app as the it does for a Java App.
This issue has been open for a long time; Closing the app is the expected behaviour now for a long time.
I feel the correct solution here is to give a example in doc on how to customise your app to change default behaviour If the developer so chooses.

Do you think it would make sense to create an event method that would be fired when the back button is pressed on Android and that the user could overwrite to implement their own handling (just like what is done with on_pause for instance)? I was thinking it could be easier to use, especially since I think handling this back button is a quite common use case @akshayaurora

@RobinPicard For custom back button/gesture handling, one way is to bind the keyboard and test for key == 27 , like this https://github.com/Android-for-Python/Android-for-Python-Users#back-button-and-gesture
Btw, I just submitted a PR that addresses a different issue with the back button/gesture. https://github.com/kivy/kivy/pull/7989#issuecomment-1231037983

#7989 (comment)
I use the binding of the keyboard and the test on test for key == 27 for my own app and it works fine, but I just thought there could be a way of making it more accessible by already doing a part of the work with something like that (before you own modifications):

```def on_keyboard(self, key, scancode=None, codepoint=None,
                modifier=None, **kwargs):
    [...]
    if WindowBase.on_keyboard.exit_on_escape:
        if platform == 'android' and key == 27:
            if not self.dispatch('on_request_close', source='keyboard') and not self.dispatch('on_back_key_android'):
                stopTouchApp()
                self.close()
                return True
    [...]```

```def on_back_key_android(self):
    pass```

Then the user would just have to add Window.on_back_key_android = custom_function to handle what happens when the back button is pressed (just like what you'd do with on_enter, on_pause...)


Update txflow.rst

This line tells about ledger.

Thanks for the contribution! However, this is a read-only mirror. please read the contribution guide. Also, feel free to join us on chat!


feat: add Invocable scripts API

Proposed Changes

Added API for InvocableScripts.
Changed supported InfluxDB version from InfluxDB 2.0 to InfluxDB 2.x

Checklist

[ ] CHANGELOG.md updated
[x] Rebased/mergeable
[x] A test has been added if appropriate
[x] swift test completes successfully
[x] Commit messages are in semantic format
[x] Sign CLA (if not already signed)

Codecov Report

Merging #48 (d710a70) into master (da50d69) will increase coverage by 32.06%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           master      #48       +/-   ##
===========================================
+ Coverage   51.05%   83.11%   +32.06%
===========================================
  Files         137       16      -121
  Lines        8528     1001     -7527
===========================================
- Hits         4354      832     -3522
+ Misses       4174      169     -4005

Impacted Files
Coverage Δ

Sources/InfluxDBSwift/DeleteAPI.swift
95.08% <ø> (ø)

...ources/InfluxDBSwift/Generated/Models/Script.swift
0.00% <0.00%> (ø)

...DBSwift/Generated/Models/ScriptCreateRequest.swift
0.00% <0.00%> (ø)

...wift/Generated/Models/ScriptInvocationParams.swift
0.00% <0.00%> (ø)

...DBSwift/Generated/Models/ScriptUpdateRequest.swift
0.00% <0.00%> (ø)

...urces/InfluxDBSwift/Generated/Models/Scripts.swift
0.00% <0.00%> (ø)

Sources/InfluxDBSwift/InfluxDBClient.swift
83.33% <0.00%> (-0.61%)
:arrow_down:

Sources/InfluxDBSwift/InvocableScriptsAPI.swift
0.00% <0.00%> (ø)

Sources/InfluxDBSwift/QueryAPI.swift
87.12% <ø> (ø)

Sources/InfluxDBSwift/WriteAPI.swift
78.03% <ø> (ø)

... and 127 more

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 da50d69...d710a70. Read the comment docs.

@rhajek this PR depends on #49


Test Git Functions

[ ] Test that a remote can be added
[ ] Test that a remote URL can be modified
[ ] Test that a commit can be made and pushed to a remote
[x] Test that when the path is changed, that the .git/ dir is moved to the new path

Working on a few of these- Have a WiP but will have to continue tomorrow

Dope, looking forward to seeing it.

@pyasi Even if you didn't finish whatever you were working on, I can work from it if you push it.

@alichtman My bad! Sent up a PR of some of the WIP I had. I've been busy

All good, man. I've been crazy busy myself. @pyasi, I'll take a look.


V13

Codecov Report

Merging #193 (33bb9ae) into main (5525c90) will decrease coverage by 4.09%.
The diff coverage is 35.04%.

@@            Coverage Diff             @@
##             main     #193      +/-   ##
==========================================
- Coverage   85.01%   80.91%   -4.10%
==========================================
  Files          56       57       +1
  Lines        1401     1504     +103
  Branches      195      209      +14
==========================================
+ Hits         1191     1217      +26
- Misses        178      243      +65
- Partials       32       44      +12

Impacted Files
Coverage Δ

src/discordBot/commands/faculty/disable_bridge.js
96.15% <ø> (ø)

src/discordBot/commands/faculty/edit_topic.js
96.29% <ø> (-0.14%)
:arrow_down:

src/discordBot/commands/faculty/enable_bridge.js
96.15% <ø> (ø)

src/discordBot/commands/student/instructors.js
93.33% <ø> (ø)

src/discordBot/commands/student/join.js
92.30% <ø> (-0.38%)
:arrow_down:

src/discordBot/commands/student/workshops.js
100.00% <ø> (ø)

src/discordBot/commands/admin/list_courses.js
12.50% <12.50%> (ø)

src/discordBot/commands/faculty/add_instructors.js
91.30% <25.00%> (-6.32%)
:arrow_down:

.../discordBot/commands/faculty/remove_instructors.js
91.48% <25.00%> (-6.19%)
:arrow_down:

src/discordBot/commands/faculty/rename_channel.js
26.31% <26.31%> (ø)

... and 9 more

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 dababfe...33bb9ae. Read the comment docs.


node-elm-compiler receiving warn option

Anytime I save my a .elm source file, everything seems to compile just fine, but whenever I save my app.js file I get the following error:
Uncaught Error: Module build failed:
Error: Compiler process exited with error "node-elm-compiler received the `warn` option,
but that was removed in Elm 0.19.
Try re-running without passing the `warn` option."

My webpack
const path = require('path');
const glob = require('glob');
const MiniCssExtractPlugin = require('mini-css-extract-plugin');
const UglifyJsPlugin = require('uglifyjs-webpack-plugin');
const OptimizeCSSAssetsPlugin = require('optimize-css-assets-webpack-plugin');
const CopyWebpackPlugin = require('copy-webpack-plugin');

console.log("THE PATH: ", path.resolve(__dirname, 'elm'))

module.exports = (env, options) => ({
  optimization: {
    minimizer: [
      new UglifyJsPlugin({ cache: true, parallel: true, sourceMap: false }),
      new OptimizeCSSAssetsPlugin({})
    ]
  },
  entry: {
    './js/app.js': ['./js/app.js'].concat(glob.sync('./vendor/**/*.js'))
  },
  output: {
    filename: 'app.js',
    path: path.resolve(__dirname, '../priv/static/js')
  },
  module: {
    rules: [
      {
        test: /\.js$/,
        exclude: /node_modules/,
        use: {
          loader: 'babel-loader'
        }
      },
      {
        test: /\.elm$/,
        exclude: ["/elm-stuff", "/node_modules"],
        loader: "elm-webpack-loader",
        options: {
          cwd: path.resolve(__dirname, 'elm'),
          debug: options.mode === 'development',
          verbose: options.mode === 'development',
          optimize: options.mode !== 'development'
        }
      },
      {
        test: /\.scss$/,
        use: [
          MiniCssExtractPlugin.loader,
          'css-loader',
          'sass-loader',
          'postcss-loader'
        ]
      }
    ],
    noParse: [/.elm$/]
  },
  plugins: [
    new MiniCssExtractPlugin({ filename: '../css/app.css' }),
    new CopyWebpackPlugin([{ from: 'static/', to: '../' }])
  ]
});

and my app.js file
import { Elm } from "../elm/src/Onboarding.elm"

const elmElement = document.getElementById("elm-onboard")

if (elmElement) {
  Elm.Onboarding.init({ node: elmElement })
}

Any idea what's going on here?

@simonh1000 this did not have an effect.
I recently noticed that I've also been getting another error
Uncaught Error: Module build failed: Error: Compiler process exited with error Compilation failed
-- NO elm.json FILE ------------------------------------------------------------

It looks like you are starting a new Elm project. Very exciting! Try running:

    elm init

It will help you get set up. It is really simple!

I feel that the elm source isn't being compiled after saving my main JS entry point. Whenever I change and save my elm source, it all compiles fine and works as expected.


Add FC097, FC098, FC099, and FC100 for deprecated mixin usage

Signed-off-by: Tim Smith<EMAIL_ADDRESS>

Any reason to not make these all one rule?

I considered making it one rule, but we'll have deprecation docs linked for these and the remediation for each is going to be different. Also if we ever deprecate a new mixin it would be less than cool to just add another one to the rule randomly. This makes it super explicit what we're checking and what failed. Also if the contents of the supermarket are any judge very few people are going to hit any of these. They're barely public APIs that weren't used much outside of Opscode.

I'm mostly just concerned about rule sprawl, but I suppose that ship already sailed :-/

The rules are pretty fine grained, but IMO that's a feature not a bug. The tags are where the sprawl needs to be contained. You shouldn't be disabling individual rules you should be disabling tags


How can I copy paste tags?

@ErlanBazarov you mean copying existing tags and pasting it back ?

Mostly I just need to paste multiple tags copied from a text. Let's say I have text: "fruit, vegetable, machine". I want to paste them to ReactTags together without having to type/copy them one by one

Sure you can do that, you need to pass allowAdditonFromPaste as true and pass the comma key code in delimiters as well. You can check out the working example

@ErlanBazarov I hope this is working for you now so closing. Incase if it doesn't feel free to reopen


Incorrect timezone on cards

The time on cards are either not converted or incorrect.
suspect: req.headers["x-forward-for"]` is not getting what i expected it to get through ngnix

[Solved]

Cause: Created a cloned time object
Solve: Use setzone() method directly on obtained zulu time

commit ref: 2b3a090


Fix: Remove default test tags

Description
Remove default test tag.
My intention was that cluster tests are omitted when running locally, but the result was that tests were omitted in CI too as the TEST_TAGS was set to "" -> default with "not cluster" was used.
Type of change

[x] Bug fix

/retest

/lgtm

/approve


Styles blank slate content using flexbox

👀 Overview
Styles the blank slate contents layout in exactly the same way, but using makes the contianer dispaly: flex instead of display: block
👫 Related PRs (optional)
https://github.com/gathercontent/app/pull/1878
✅ Checklist

[ ] Tests written
[ ] Browser tested
[ ] Added to documentation
[ ] Added to storybook

 Blank slate: Create item, new folder, all items


Update register-devices-self.md

Added a note about editing the file in excel and saving it as CSV make the file unusable

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/5505

@jaimeo Please merge this PR. Thanks

Copy editors: we do not use "please."
@jwmurraycmu are you OK with the tech accuracy of this edit?

@AlexBlain are you OK with the tech accuracy of this edit?

@jaimeo fine with that


CLI MLCube Timeout

This PR adds functionality for specifying timeouts for each task independently. Closes https://github.com/mlcommons/medperf/issues/140.

Implement rest tests

Removed unused dependency

Simplify text setter

fix hidden input not returning anything

Implement cli ui tests

Remove duplicated authenticate method

remove unnecessary pass statements

REST follows comms init signature

Fix Associate command

Provide more user-friendly error on Dataset init

Replace exceptions to pretty errors

Remove UI circular import

Test new pretty errors

Fix comment typo

Implement associate tests

Move prompt logic to comms login method

Fix test with login method

Add missing abstract method hidden prompt

Implement login command tests

Fix login method

Implement additional tests

split execution into methods

reorder methods

Add cleanup after benchmark execution

fix comms not receiving ui instance

Fix registration not using ui for prompt

Refactor prepare command into methods

Add cleanup to preparation flow

Store datasets under their generated_uid

Split dset preparation and registration commands

Adjust tests to dataset changes

Initial submit command

Fix Benchmark Execution not finding results path

DRY up comms and ui fixtures

Remove unused deprecated method

Implement prepare command tests

start working on datasets command tests

Test preparation flow

Implement benchmark execution tests

Fix results_path not returning anything

add results filename to config

Implement missing benchmark exec tests

Implement register tests

Move shared function to utils

Implement submit tests

Fix execute command data uid as str

Fix pretty error not receiving ui

Remove leftover files from merge

Recover comms and ui fixtures

Fix broken comms fixture

Remove deprecated file

Fix result not using dataset server uid

Fix ensure storage is setup before anything

Fix prepare not storing/registering datset

Fix detection of already prepared datasets

Add docstring to submit command

Fix login test not mocking "exist" method

Implement draft for test command

Add method to create local cubes

Split init logic from preparation logic

[WIP] Develop methods for test command

Store config variables as module variables

Convert config references to new structure

Convert config references to new structure

Convert outdated config references to new struct

Add helper function for storage relative paths

Fix storage path parsing

Fix credentials_path not relative to storage

Formatting

Fix outdated references to config

Undo config changes

Add initial testing implementation

Add run_test parameter to benchmark exec

Fix resolve argument paths instead of forcing abs

Implement cube caching

Add local cube prefix to config

Add ui object to cube get calls

Add logging to set_registration

Add run_test to prepare step

Move cleanup outside of function declaration

Fix decorators disorder

Add testing prefixes

Remove unused print

Add uid to dataset

Ensure comparison is done with same datatype

Remove unnecessary print

Only check mlcube path vailidity if provided

Return ids after finishing the test

Add logging messages to test flow

Change name to evade pytest issues

Fix outdated test execution imports

Reorder init args. Fix model validation

Remove unused import

Implement initial tests

Fix dataset using incomplete path

Move comms and ui to config singleton

Remove unused argument for registration write

Fix medperf logs not working correctly

Fix results not being stored in correct path

Fix results_path_testing

Run tests on test storage path

Implement mlcube list method

Add tests for mlcube list

Implement mlcube submit method

Implement mlcube associate command

Implement submit tests

Implement associate tests

Implement REST additional tests

Add new dependencies to medperf cli

Implement benchmark list subcommand

Implement get_user_benchmarks test

Implement benchmark submit subcommand

Implement list all benchmarks

Implement list all mlcubes

Update CLI readme

Update outdate config and import calls

Add demo_dataset related info to test benchmark

Fix typo

Add benchmarks directory to medperf storage fs

Implement local benchmark storage

restructure is_valid

Display approved status

Add demo dataset to benchmark submission

Fix dset list bugs. Add Server UID to list

Benchmark Association initial implementation

Add ui messages on successful association request

Add associate command

Fix outdated import

Download demo dataset for test. Disable validation

Implement testing for all cubes in benchmark

Add compatibility test to bmk submit

Update seed benchmark

Fix test command evaluator arg

Remove demo dataset prefix from benchmark

Add mlcube association to benchmark

Fix typo in parameters url

Fix not being able to submit cubes without tarball

Fix results entity tests

Move compatibily test unit tests

Fix utils test errors

Fix compatibility test unit tests

Fix submit errors

Fix dataset create tests

Fix tests for results_path

Fix result create tests

Fix result entity tests

Fix dataset entity tests

Write additional tests

Add tests to benchmark object

Implement additional comp_test tests

Add download_demo_data tests

Rename dset assoc test

Add missing tests to benchmark assoc

Add additional tests to submit

Fix pytest not stunting listdir

Add return description to docstring

Fix bmk-dset association

Fix list typing error

Move comptest tests to correct location

Move comptests to correct location

Update comptest references

Update all imports to new structure

rename ui and comms interfaces

Run Comptest on dataset assoc

Fix tarfile creating superfluous files

Fix compatibility tests

Fix: use correct uid for result creation

Fix missing ui error

Add compatibility tests to associations

Pass result tests through associations

Fix test error

Implement list associations command

Fix associations

Add associations tests

Imlement rest tests

Implement approval commands

Move associations to list command

Rename list to ls

Implement approval tests

Fix dataset assoc approval implementation

Add missing tests

remove unused cache command

Store demo datasets in a persistent location

Fix run comp test with local demo dataset

Allow running tests with demo dataset

Fixed ui and comms imports

Remove python3.9 dependency

Add missing self.ui

Fix remove tmp_submission on cleanup

Fix return user benchmarks

Add tests for user benchmarks returned

Fix comp test failing for demo dset already prep

Add init files to command tests

Fix registration tests

Fix bug set approval status always approves

Update decorator order of execution

Cli remove init files (#89)

Update all imports to new structure

rename ui and comms interfaces

Fix decorator imports

Fix symlink failing

Force benchmark update when not testing

Remove redefinition of Benchmark

Fix formatting errors

Fix formatting

Cli offline testing (#128)

Authenticate only when needed

Fix outdated auth_req test

Add optional timeouts to all mlcube executions

Fix/Add timeout testing

Reformat code

Failed transfer from Fork branch to local branch. Closing this


Immutable.hash and arrays

Following on from #1176, specifically the second bullet point in my comment
Consider:
import * as Immutable from "immutable";

let x = [1,2];

let a = Immutable.hash(x);
let b = Immutable.hash(x);

let c = Immutable.hash([1,2]);
let d = Immutable.hash([1,2]);

Now a === b holds, but c === d does not.
If this is the intended semantics that's absolutely fine but can I request a couple of things:

we update the docs to be clear on the behaviour of Immutable.hash on collection types (maps, arrays)
we expose Immutable.hashMerge (or similar) which allows the caller to achieve the effect of c === d by iterating a collection type themselves

@leebyron any thoughts here?

Sorry for letting this issue sit.
This is definitely the intended semantics. Plain objects and arrays are mutative and use reference equality and their generated hash codes reflect that. Each instance will have a unique hash.
I just added a commit which updates the documentation for hash() to include this


Documentation for rows().every()

In the example below rowIdx is not defined anywhere. Although it may be perfectly valid code with rowIdx defined globally, however with this example it makes sense to use something like var rowIdx = this.index(); inside the function.

var table = $('#example').DataTable();

table.rows().every( function () {
    this
        .child(
            $(
                '
'+
                    ''+rowIdx+'.1	'+
                    ''+rowIdx+'.2	'+
                    ''+rowIdx+'.3	'+
                    ''+rowIdx+'.4	'+
                '
'
            )
        )
        .show();
} );

The first parameter passed into the every function is the row index. I had missed that from the function's parameter list. Thanks for pointing that out.
I've added it here and will push it out to the site soon.

Allan, can you also please update the example above on the same page for the sake of clarity so it reads:

Using rows().every() this can be rewritten as:

table.rows().every( function (index) {
var data = this.data();
// ... do something with data(), or this.node(), etc
} );

Yes - positively sensible that! Thanks :-)
Committed
Allan

hello, guys, can you help me
table.rows().every( function (index) {
var data = this.data();
// ... break ; or return false wich one will stop function ?
} );

None. There is no way to get out of that loop - its a callback that will be executed for every row. If you need some support with a specific function, feel free to post your question in the forums.


Magic Bows with Infinity Duplication Arrows

Hey there!
I've had a couple of players on my server mention that they can get unlimited arrows by simply putting infinity on their magic bow. Not completely sure if this fits in here on GitHub but I would think that it would be more of a bug then a support question.
Thanks

Sorry! This is fixed in the latest dev build, which I will probably release later today as 10.1

Ok, no problems. Thanks!


The Hungry Variable

Again some misunderstanding
There is a small difference between

/[/ + "javascript"[0] + '///'

and

/[/ + "javascript"[0] + '///'

sorry can you clarify the post this relates to?


Unknown status code throws when using ResponseLogFilter

From<EMAIL_ADDRESS>on January 10, 2015 12:07:23
What steps will reproduce the problem? 1. Use<EMAIL_ADDRESS>2. Call RestAssured.enableLoggingOfRequestAndResponseIfValidationFails()
3. Invoke HTTP resource that return an unknown code, like 601 What is the expected output? What do you see instead? java.lang.IllegalArgumentException: Status code must be greater than 100 and less than 600, was 601.
at com.jayway.restassured.builder.ResponseBuilder.build(ResponseBuilder.java:175)
Without logging enabled things works well.
Enabling logging should not fail tests that pass without it.
From my understanding, HTTP RFCs do not forbid usage of status codes >599, they are simply unspecified.
Original issue: http://code.google.com/p/rest-assured/issues/detail?id=382

From<EMAIL_ADDRESS>on January 16, 2015 11:06:28
You're right. Thanks for reporting.
Status: Accepted

Hi,
I created a pull request 1773 where I removed the check from the Builder class. We really need this fix to check our application because we're using "911" as application specific error code.


Android back button on chat window minimize Sphinx

When I'm on chat window and I click on Android back button, instead of go to Sphinx main window, it minimize Sphinx. I reproduce this on Xiaomi phones.
On older Sphinx versions this was working ok. So I think this is a regression.

Same problem on scan qrcode window.

download the new APK

Fixed, thanks.


Quick Remove Rule button

We need a "Remove" button in the "Modify Hilight Rule" window, there we can remove easily.
Rules added with right click menu should be saved to "Solution Rules" not to "Global Rules"
When we add new rule, the shape option should be defaulted to the last chosen one

Thanks for the feedback. Solution Rules are still in development, but yes once they're active it will be the default.
I'll try to implement all 3 in the next release in a week or so.

All 3 suggestions have been implemented (albeit a little late), and will be released shortly once tested.


Add test for when limit is reached on cursor

Description
This test reveals contradicting behavior of what is defined here, i.e.

Starting with 5.0, all cursor-producing operations will return a cursor ID if the end of the batch being returned lines up with the limit on the cursor.

Adding this test for visibility.

Readiness checklist

[ ] I added/updated unit tests.
[ ] I added/updated integration/compatibility tests.
[ ] I added/updated comments and checked rendering.
[ ] I made spot refactorings.
[ ] I updated user documentation.
[ ] I ran task all, and it passed.
[ ] I ensured that PR title is good enough for the changelog.
[ ] (for maintainers only) I set Reviewers (@FerretDB/core), Labels, Project and project's Sprint fields.
[ ] I marked all done items in this checklist.

@b1ron, what is the issue number for that test?

@AlekSi there's no issue it was just something I found while reading the spec:

Adding this test for visibility.

#4318


Migrating: Grackle GraphQL

Migration Checklist
Project Submission Issue: #110
For Organization Projects:

[x] Create a team for the repo with maintainer as team member
[ ] After repo transfer, add repo with write permissions to the created team

For All Projects:

[ ] Add project to the site by adding an entry to the projects.yml file

Announcements
These steps are optional but encouraged.

[ ] Write a blog post announcing the change
[ ] Post to our social channels (Mastodon)

Created the @typelevel/grackle team with @milessabin as initial member.  Let me know if there are any comaintainers.  We'll get it attached to the repo after transfer.

Could you add @tpolecat, @dantb and @jf-botto as comaintainers. Thanks!

Invites sent.
Is the plan to transfer the repo, rather than fork it into the org?

Better to transfer if possible, then it carries issues/PRs/etc.

Yes, the plan is to transfer. @tpolecat will be able handle things on the Gemini end.

Could you also add @camimora ... or is there some way I can do that?

Invite sent.  Happy to add any more, but we're at our GitHub seat cap, and will need to retire some dormant members and/or buy seats before any additional.


changed example code to send ipc messages to and from the Main Process

The existing example didn't work for me, but I tried this variation and it now works. Using latest production Electron..

Oops, there is a new syntax. Withdrawn.


Error loading mesh

Half of the examples crash with an error like:
bloom: /builddir/build/BUILD/assimp-3.1.1/code/ObjFileParser.cpp:261: void Assimp::ObjFileParser::getVector(std::vector<aiVector3t >&): Assertion `!"Invalid number of components"' failed.
I'm using my distro's (Fedora 23) version of assimp which is 3.1.1, since I'm not sure which version the Windows binary is and there isn't a Linux binary.

Earlier issues suggests you need 3.2

Yes, you need at least ASSIMP 3.2. Older version can't load animations from the COLLADA file. The animation is not perfectly repeatable anyway, so I'm looking for a different mesh to use for the example.
I'll also address the linux ASSIMP issue in the future.

I have added a paragraph about building on Linux that hints at assimp and that version 3.2 is required.


Add Opentelemetry health check and add to v1/status

Tracking issue to address required change from #802 .

I'm not sure that adding a basic health service for Otel is as much work as you're thinking it is. All we need to do is use the pre-compiled protos provided by tonic, attach the service to the same tonic server, and implement a very basic health check. Since we just want to know that the server is up, it could probably just always return Ok. To be clear, no GRPC service definition "satisfies GRPC health checks", servers need to implement that themselves.
Also, it looks like for the Flight endpoint you're just connecting to the GRPC server and considering it healthy if you can connect, is there a reason that is sufficient for the Flight endpoint but not the Otel endpoint?

Originally posted by @mitchdevenport in https://github.com/spiceai/spiceai/pull/802#pullrequestreview-1937054649

Resolved in https://github.com/spiceai/spiceai/pull/847


⚠ Bofrost.lu has degraded performance

In 25c551c, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1715 ms

Resolved: Bofrost.lu performance has improved in 148b315 after 6 minutes.


[FLOC-3008] Idempotent repo installation on CentOS

Fixes: https://clusterhq.atlassian.net/browse/FLOC-3008
The command to install the repo YUM package on CentOS needs to work on both systems where Flocker has been installed previously, and on systems where it hasn't.
Although yum install handles a repeated install fairly cleanly, it does exit with non-zero, causing problems for our automated testing.
A previous attempt to solve this changed the command to yum update which works on systems where Flocker has been installed before, but fails on fresh systems.
The whole exercise was obscured by the fact that for Buildbot tests, another repo is added to make the branch repos available, thus masking the absence of the production repo, until the actual instructions in the docs are followed.
This PR checks whether the yum package is installed before attempting to install it, thus working in all environments.
To test, start a Docker instance using docker run -it --rm centos:7 /bin/bash, and then run the first command in the Installing on CentOS instructions.
For 1.3.0, these instructions are at https://docs.clusterhq.com/en/1.3.0/install/install-node.html#installing-on-centos-7 and running the first command will fail with non-zero exit.
Replacing yum update with yum install in this command will succeed on the first attempt, but fail for subsequent attempts.
Running the new command from this branch http://build.clusterhq.com/results/docs/yum-install-update-FLOC-3008/build-9900/install/install-node.html#installing-on-centos-7 should work, no matter how many times you run it. However, a real error (e.g. changing the URL to point to a non-existent file) will fail with non-zero status, as expected and desired.

Thanks @jongiddy
I checked the new command line manually and it works as you described. Great.
I restarted the three failed builds.
Please merge once those go green.

Thanks @wallrj - I also checked yum reinstall but it fails if the package is not currently installed.


Remved primary and accent unnecessary specificty

Focus, active and hover styles not being applied to .primary and .accent buttons because of unnecessary specificity -- the primary and accent selectors being used twice in the rules.

I signed it!

On 25 Sep 2015, at 10:25, googlebot<EMAIL_ADDRESS>wrote:
I signed it!

Thomas Hudspith-Tatham
<EMAIL_ADDRESS><EMAIL_ADDRESS>Please consider the environment before printing this email.
E-mail messages may contain viruses, worms, or other malicious code. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective action against such code. Thomas Hudspith-Tatham is not liable for any loss or damage arising from this message.
The information in this email is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this e-mail by anyone else is unauthorised

Thanks for the PR, @tomatau! Is there an issue for this? I'd like to see an example of the problems this is causing before we make any changes (looking at http://www.getmdl.io/components/index.html#buttons-section I don't see any problems).

Most of the buttons here don't have :hover/:active/:focus styling applied. This isn't so apparent in the demo page as many of the pseudo background colours are the same as the normal colour.
You can see the problem more clearly if you:
$button-hover-color: unquote("rgb(#{$color-primary-dark})");
$button-active-color: unquote("rgb(#{$palette-red-500})");
$button-hover-color-alt: unquote("rgb(#{$color-primary-dark})");
$button-active-color-alt: unquote("rgb(#{$palette-red-500})");

Thanks for the details, @tomatau! A quick check seems to indicate everything still works correctly after the patch.
@surma, would you mind taking a look? Was there any problem you were trying to fix by repeating the class name?

Hm, I was pretty sure the classes weren’t working without out the bumped specificity. I’ll gladly take a look to make sure this still works :)

The bumped specificity seems more important for the disabled buttons.

From issue #1633

The problem becomes apparent when you set custom hover/focus/active colours for the buttons.

I think it would be best for now that developers increase specificity as-needed in their apps, even for pseudo states. Changing this now can cause breaks in how people have implemented sites depending upon the existing specificity.

Ping for any last comments before closing this? Reducing specificity is something potentially breaking. This should be handled with V2 if done at all.

@Garbee can you come up with a non-contrived example of how this could be breaking? (given the class name being pretty uncommon)
I would think that this is totally in the realm of acceptable v1 "breaking" changes (because I do not think it will actually be breaking)

@samccone Welcome to the problem with Semver. Even the most contrived examples matter, because they can exist. Whether I agree or not, the Semver contract exists for 1.x and we should hold to it.
This can cause existing sites with broad targets on coloring to now have button colors change since we are reducing our specificity, other things could override it now more easily which wasn't accounted for before.

Oh trust me, I am all about semver and enforce it on my OSS projects, however this one walks the line for me only because I can not think of how this could actually be breaking

This can cause existing sites with broad targets on coloring to now have button colors change since we are reducing our specificity,

Can you give me an example (hopefully this will make it clear to me how this breaks things and I will join your side)?

Example on codepen. Removing the extra specificity means the material button would have its color changed now, where the developer was expecting it before to keep the provided color.

In a BEM CSS library - it will only lead to a can worms to support of developers using non-Bem selector strategies. I agree this is a "breaking" change but it's still a change in the correct direction.
Double selectors puts developers who are correctly using BEM in their projects at a disadvantage and means they either have to resort back to specificity wars or dirty hacks.

fiar enough :+1: v2 it is :dancer:

The library itself uses BEM as a guide for naming. We still need to support non-BEM implementations possibly breaking. You may feel it isn't since you are "doing BEM properly", but that doesn't mean every other site using MDL is.
Sorry, but this is a breaking change and can only be dealt with in a major release. SemVer demands this. As such I'm closing this out so the tracker is more organized. We will make a point when working on 2.x to verify our selectors are as specific with the least amount  of specificity reasonably possible.


BUG: signal.decimate returns NaN with large float32 arrays

Describe your issue.
When using decimate with large float32 arrays often arrays will all NaN values are returned.
Reproducing Code Example
import numpy as np
from scipy.signal import decimate

ar = np.random.random((10_000, 2))

out1 = decimate(ar, 10, axis=0)  # this works fine

out2 = decimate(ar.astype(np.float32), 10, axis=0)  # returns all NaN

# It also works fine if the arrays smaller

out3 = decimate(ar.astype(np.float32)[::100], 10, axis=0)  # No NaNs in array

Error message
None

SciPy/NumPy/Python version information
scipy: 1.6.2, Numpy: 1.18.5, Python: 3.8.5

I have replicated this issue with scipy:1.7.1, Numpy: 1.21.2, Python 3.9.5.
This error seems to happen only if the filter type is set iir and the downsampling factor q is 9 or greater. I was able to trace down the error to the _linear_filter function.
# No NaNs
out1 = signal.decimate(ar.astype(np.float32), 10, axis=0, ftype='fir')

# No NaNs
out2 = signal.decimate(ar.astype(np.float32), 8, axis=0, ftype='iir')

# returns NaNs
out3 = signal.decimate(ar.astype(np.float32), 9, axis=0, ftype='iir')

This is a dupe of gh-13529, though this report is better since it has a motivating example.
I tested with a hacked version of decimate that uses sosfilt instead of lfilter, and the NaNs disappear.
This should be fixed by gh-14371, though that PR seems to be stalled.


.babelrc causing babel transpile issues

Babel (according to it's website as of November 13, 2015) does not have an option for stage or loose and these cause babel to blow up on transpile. Wondering if this serves some other purpose?

Please see the versions. The examples use Babel 5. Please consult Babel docs for migration instructions. We don't offer support for Babel in this repo. We'll switch to Babel 6 eventually, but for now, remember the examples are Redux examples, not project boilerplates. Consult them for the Redux-related parts of the code, but please don't consider them to always reflect the latest tools available.

Gotcha I will fork and not install your copy from npm. It fails from your module. This is not bolierplate, it is a library that causes my code to fail when building. I should not have to edit your accepted install just to build...

This is not bolierplate, it is a library that causes my code to fail when building.

The problem you have is due to you transpiling code from node_modules. You should not do that. That's a mistake in your build process.
If you process your code with babel-loader (Webpack) or babelify (Browserify), you must exclude node_modules from your build process. For example, in Webpack, in loader configuration you can write
  {
    loader: 'babel-loader',
    exclude: /node_modules/
  }

or equivalent. You can also use include option to explicitly include the source of your application (this works better).

I see. I'll toss that in then. Thanks for the better explanation!

You'll enjoy faster builds :wink:

Thanks Gaeron, that worked for me.


Generating large NAPOT regions

At the moment RISCV-DV generates addresses randomly including when the PMP encoding is set to NAPOT. Since the NAPOT range is encoded in the address, it means that it is unlikely that we will generate larger regions, since these require a series of ones at the end of the address (see Table 3.11 in the RISC-V privileged spec).
We should constrain RISCV-DV full randomization to first randomly select a random range and then randomly generate the top bits of the address to create more coverage.
Coverage points for this should be added to the coverage plan and implemented

estimate 8

Add a sentence about adding coverage for this, shouldn't be complex given the rest of the PMP stuff is already there so didn't alter the estimate.

I made a first attempt to adding coverage points for large NAPOT regions: https://github.com/lowRISC/ibex/pull/1818
In the process I removed some impossible to reach PMP coverage: https://github.com/lowRISC/ibex/pull/1817

spent 3

It took me a while to find out that the Spike version I was using didn't compile because xrun gave a vague error.
Besides that I updated the PR https://github.com/lowRISC/ibex/pull/1818 based on suggestions from @ctopal.

spent 4

There is a PR for RISCV-DV, which generates these large NAPOT regions now: https://github.com/google/riscv-dv/pull/903

Cover points still need to be added for this.


[SPARK-43014] Do not overwrite spark.app.submitTime in k8s cluster mode driver

What changes were proposed in this pull request?
Do not overwrite spark.app.submitTime in k8s cluster mode driver
Why are the changes needed?
If spark.app.submitTime is overwritten, we can not get real submit time.
Does this PR introduce any user-facing change?
'No'
How was this patch tested?
Add test "SPARK-43014: Do not overwrite spark.app.submitTime in k8s cluster mode driver"

Failed tests are irrelevant

cc @yaooqinn @dongjoon-hyun

I understand what you aim to achieve in this PR. In case of K8s Cluster Mode, the driver pod has a driver ConfigMap containing spark.app.submitTime already. So, you want to keep that. However, this is not safe because of the timezone between the user machine and the K8s control plane server.
If we want to propose this improvement to include the driver pod pending time, we need to add a configuration to control this feature, @zhouyifan279 . Could you try to add a configuration and add an integration test case too?

@dongjoon-hyun Can you elaborate about how timezone affects the computed driver pod pending time.
As I understand, both spark.app.submitTime and spark.app.startTime is milliseconds between the current time and midnight, January 1, 1970 UTC.

Sorry for misleading you. You are right about timezone. What I imagined was more like the following case.
$ docker run -it --rm --cap-add SYS_TIME openjdk:latest bash

bash-4.4# date -s '@2147483647'
Tue Jan 19 03:14:07 UTC 2038

bash-4.4# jshell
|  Welcome to JShell -- Version <IP_ADDRESS>
|  For an introduction type: /help intro

jshell> java.lang.System.currentTimeMillis()
$1 ==><PHONE_NUMBER>595

Any updates, @zhouyifan279 ?

@dongjoon-hyun sorry for response late.
Speaking from my limited experience, I think very few users may encounter the case you mentioned.
We'd better not to handle this case in Spark's code.
Besides, if user changed system time by intention, he can handle it by himself easily:

Inject a custom spark property, such as spark.app.systemTimeBias into SparkConf.
The real driver pod pending time would be: startTime - systemTimeBias - submitTime.

No because it will be a new regression in terms of the vulnerability. You are aiming to fix one thing and open another bug.

We'd better not to handle this case in Spark's code.

That's the reason why I counter-propose you to add a configuration to support this proposed behavior and the existing behavior, @zhouyifan279 .

https://github.com/apache/spark/pull/40645#pullrequestreview-1370202973

@dongjoon-hyun Added a new configuration spark.kubernetes.setSubmitTimeInDriver to control which submitTime Spark should use.
Now Spark will set spark.app.submitTime in the following cases:

The application is deployed using spark-submit in client/cluster mode.
SubmitTime is the time spark-submit executed.
The application is deployed by other ways, such as spark-on-k8s-operator
SubmitTime is the time driver pod started.
The application is deployed using spark-submit in cluster mode and spark.kubernetes.setSubmitTimeInDriver is true.
SubmitTime is the time driver pod started.

@dongjoon-hyun do you have any more inputs on this PR?

Gently ping @dongjoon-hyun

Unfortunately, it seems to fail again.

Unfortunately, it seems to fail again.

Let me trigger it again.

Thank you, @zhouyifan279 .
BTW, when I said the following.

Please re-trigger the failed test pipeline.

It means this. Re-run failed jobs is always faster.

Thanks for the information. Didn't know that before. 😂

This PR never passes the unit tests. According to the GitHub Action log, you had better verify the following test suite locally, @zhouyifan279 . In the community, we are unable to merge a PR with UT failures.
[info] ReplE2ESuite:
sh: 1: cannot open /dev/tty: No such device or address
sh: 1: cannot open /dev/tty: No such device or address
sh: 1: cannot open /dev/tty: No such device or address
sh: 1: cannot open /dev/tty: No such device or address
sh: 1: cannot open /dev/tty: No such device or address
sh: 1: cannot open /dev/tty: No such device or address

@dongjoon-hyun CI succeeded after I rebase on master branch.


Fails on Fedora23 for apiserver_runtime_config undefined variable

TASK: [master | write the config file for the api server] *********************
fatal: [x.x.x.x] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'apiserver_runtime_config' is undefined", 'failed': True}
ansible/roles/master/templates/apiserver.j2:26
Appears it's possibly the same issue as #323

@jayunit100

might require a similar patch,  let me see

@MrMitch17  hi !
For now, uncomment group_vars/all.yml  that should be enough for it to work.
Meanwhile ill submit a quick patch!

Hi @MrMitch17 is this now all working for you?  I tested it on os x but i think ansible behaviour can vary a little esp . since I make a few changes to the files before running.  Just let us know.  thanks again for rapidly reporting these.


icons/table view never changes after a navigating error happens

Hi.
When a navigating error happens (e.g. the backend bridge responses a 500 error when requested listing some dir), the FileNavigator.error is set to some string ( by default, "Unknown error listing, check the response" ). However, the FileNavigator.error is never set back to empty string ("") even when a status 200 action happens afterwards, thus causing the icons/table view sticks with the message "Unknown error listing, check the response". I think a quick fix would be adding these lines of code to FileNavigator.prototype.deferredHandler function at filenavigator.js line 24:
if (code == 200) {
    this.error = '';
}

Hi.. this is fixed now. Thanks!


Visual Basic files for markdig conversion

Visual Basic files for markdig conversion
Related to #7201

Build report has some warnings


tabPress listener not working when wrapped in Stack.Navigator

Current Behavior
The listener for tabPress event is not working when the screen component is an instance of Stack.Navigator. Works fine when the screen component is an instance of Stack.Screen.
Expected Behavior
The 'tabPress' listener to fire.
How to reproduce
Expo - https://snack.expo.io/@slusatel/react-navigation-tabpress
1st tab works fine with direct Stack.Screen component.
2nd tab fails - with Stack.Navigator component.
Your Environment

software
version

Platform
iOS

react-navigation
5.0.3

react-navigation-tabs
5.0.3

react-native-reanimated
5.0.3

react-native-gesture-handler
5.0.3

react-native-screens
master

react-native
latest

expo

node
latest

npm or yarn
latest

Is this what you mean? https://reactnavigation.org/docs/en/nesting-navigators.html#nested-navigators-dont-receive-parents-events

🤦🏻♂Missed it.
Thanks @WoLewicki


Luci chooses WPA3

When I try to connect to a network when I use the network browser even though it does not use WPA3, it always chooses it.
Use snapshots.

yes, I notice this issue, maybe it is a bug.
ping @Ansuel @jow-

@castillofrancodamian can you post a screenshot or a gif of the problem?

Scan wifi and try to connect to somewhat ssid (and it is WPA2), but the default config is set to WPA3.
I have to change from WPA3 to WPA2 manually

Scan wifi and try to connect to somewhat ssid (and it is WPA2), but the default config is set to WPA3.
I have to change from WPA3 to WPA2 manually

That's what I meant, and I can't get a screenshot.

i would have preferred a screenshot but fin i will try to reproduce a push a fix for this.

i would have preferred a screenshot but fine i will try to reproduce and push a fix for this.

It is easy to reproduce. Following the logic of connecting from the search engine, it can be observed.

@castillofrancodamian can you tell me if your case with what is saved by default if you don't modify the encryption?
I reproduced the bug but it looks like the bug is not really the fact that it wrongly show wpa3 instead of the right one but the fact that it doesn't recognize the right encryption at all and save the first one (in my case luci set the connection with owe with a connection that should be wpa2)

@Ansuel At no point did I say that it does not show the correct encryption, but that it always chooses WPA3 even if the network to connect does not use that encryption and I have to manually change the corresponding one.

You are saying the same thing in different words...
I'm saying that luci wrongly set the wrong encryption.
You are saying that luci by default show wpa3 and you need to change that manually.
If you don't change wpa3 manually luci gen a conf with sae set ahahha
Anyway i think i have fixed this and i will push a fix after some test

@Ansuel Maybe I have used the same words because I am using Google Translator. What I mean is that it does not show or choose the encryption in LuCI correctly.

I mean that we are saying the same thing. Anyway found the problem will be fixed as soon as jow merge the fix I will push ;)
Thx a lot for the report

@Ansuel Thanks for giving me attention! 😊😊😊


Issue while create release apk

What went wrong:
Execution failed for task ':flutter_twitter_login:verifyReleaseResources'.

java.util.concurrent.ExecutionException: com.android.builder.internal.aapt.v2.Aapt2Exception: Android resource linking failed
C:\Users\Shubham\AndroidStudioProjects\go_flite_12_12\build\flutter_twitter_login\intermediates\res\merged\release\values\values.xml:247: error: resource android:attr/fontVariationSettings not found.
C:\Users\Shubham\AndroidStudioProjects\go_flite_12_12\build\flutter_twitter_login\intermediates\res\merged\release\values\values.xml:248: error: resource android:attr/ttcIndex not found.
error: failed linking references.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 4m 59s
Finished with error: Gradle task assembleRelease failed with exit code 1

getting same issue... I have posted question on StackOverFlow
https://stackoverflow.com/questions/59496368/execution-failed-for-task-flutter-twitterverifyreleaseresources?noredirect=1#comment105248897_59496368
Didn't find the solution

Fix this issue by referencing an AndroidX fork of this repo in pubspec.yaml
flutter_twitter_login:
    git: git://github.com/minitasks/flutter_twitter_login.git

It's just one commit ahead for now, and it fixes the Android build for me. Let me know if a problem comes up, I'll try to find a fix for that.

Fix this issue by referencing a fixed fork of this repo in pubspec.yaml
flutter_twitter_login:
    git: git://github.com/eudangeld/flutter_twitter_login.git

Delete build folder and flutter clean to be absolutely sure.

This one worked for me :D

Fix this issue by referencing a fixed fork of this repo in pubspec.yaml
flutter_twitter_login:
    git: git://github.com/eudangeld/flutter_twitter_login.git

Delete build folder and flutter clean to be absolutely sure.

can you create a PR so its also fixed in "official" repo?

@venil7 #13 is a PR by the original creator of the fixed fork (eudangeld), it didn't get accepted as this project doesn't seem to be actively maintained by anyone.
My advice is to use this hack (referencing fixed fork in pubspec.yaml).

@roughike Could you please accept the PR?


Hassio bad variable

I had the addon running smooth in Hassio. After the update i get

(Why the issue was filed)/init: export: line 12: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin: bad variable name.

I cannot find any help/fix for this.
Please could someone tell me whats going on?
Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Can you post the full log please?

This is the whole log chrony gives me.
/init: export: line 12: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin: bad variable name

Can you share the Supervisor Log, from Supervisor/System/System Log

20-02-16 15:42:31 INFO (MainThread) [hassio.addons] Create Home Assistant add-on data folder /data/addons/data/a0d7b954_chrony
20-02-16 15:42:31 INFO (SyncWorker_4) [hassio.docker.interface] Pull image hassioaddons/chrony-armv7 tag 1.0.7.
20-02-16 15:43:01 INFO (MainThread) [hassio.addons] Add-on 'a0d7b954_chrony' successfully installed
20-02-16 15:43:36 INFO (SyncWorker_19) [hassio.docker.addon] Start Docker add-on hassioaddons/chrony-armv7 with version 1.0.7

Thats all system log gives. Then I get the error in the Chrony log and Chrony wont start

It's not a particularly easy issue to troubleshoot, to confirm you just updated and the error occurred.
I assume you have attempted to remove and re add the addon?  Have you had issues with any other addons?

Yes have tried to remove and reinstall and then restarted with no luck. Other addons run fine

Just some more info. Im on HassioOS 3. 10 and Supervisor 200

Can you also confirm your Operating System so I can attempt to duplicate?

Tried few time to get chrony running. Below system logs.
20-02-16 16:05:28 INFO (SyncWorker_0) [hassio.docker.interface] Clean addon_core_configurator application
20-02-16 16:05:46 INFO (SyncWorker_0) [hassio.docker.addon] Start Docker add-on homeassistant/armv7-addon-configurator with version 4.2
20-02-16 16:07:21 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
20-02-16 16:09:03 INFO (SyncWorker_10) [hassio.docker.interface] Clean addon_a0d7b954_chrony application
20-02-16 16:09:43 INFO (SyncWorker_10) [hassio.docker.addon] Start Docker add-on hassioaddons/chrony-armv7 with version 1.0.7
20-02-16 16:11:02 INFO (SyncWorker_14) [hassio.docker.interface] Clean addon_a0d7b954_chrony application
20-02-16 16:11:43 INFO (SyncWorker_14) [hassio.docker.addon] Start Docker add-on hassioaddons/chrony-armv7 with version 1.0.7
20-02-16 16:12:30 INFO (SyncWorker_2) [hassio.docker.interface] Clean addon_a0d7b954_chrony application
20-02-16 16:12:55 INFO (SyncWorker_2) [hassio.docker.addon] Start Docker add-on hassioaddons/chrony-armv7 with version 1.0.7

Unfortunately I cannot duplicate on a Pi3 here (the addon installs and runs fine), can you please share the addon config?
Also you may wish to try running hassio su repair or ha su repair from the SSH/Web Terminal addon (depending which version you have)

Running the stock Chrony config. Busy running repair.

Just ran a repair and it fixed the problem. Thanks for the prompt response and guidance to get the problem resolved. Youre a legend.

Glad we got it resolved! 👍


NetAssociation enables itself on foreground even when not previously enabled

I'm trying to do one-off queries of the NTP server using sendTimeQuery. I thus never enable my NetAssociation but it gets enable by the foregrounding event. I just commented those sections out for my own use, but you might want to do some kind of check of whether the user wants the services enabled at all.

I agree .. I'm rewriting NetAssociation to get rid of a lot of monkeying around with averages and statistics that don't gain you anything on a device where the first priority is fast user response.  We'll see if "enable" and "finish" survive this process!