Fix #371 - Run emulator-based unit tests on Travis

tl;dr
Currently, Travis CI simply builds the library but does not run any of the unit tests. This is because the unit tests are instrumented, and therefore require a running emulator or device to execute. And getting emulators to run on Travis is hard (see https://github.com/googlemaps/android-maps-utils/issues/371).
After a lot of testing, in this PR I've managed to get the magical Travis incantations for running emulators to work.
We still have one unit test  (GeoJsonPointStyleTest.testIcon()) failing on Travis (but not locally) - see TODO section below for our options.
Details
I've tested emulators for a number of API Levels (15-19, and 21-29).
Several emulators (15, 16, 19, 29) are broken on Travis - they refuse to start or hang during startup.
Emulators 17, 18, and 21-28 start up correctly and execute the unit tests - so that's good!
But, emulators 17, 18, and 21-25 have two failing tests on Travis:

GradientTest.testInterpolateColor()
GeoJsonPointStyleTest.testIcon().

The GradientTest.testInterpolateColor() failure is:
07:32:38 V/InstrumentationResultParser: Error in testInterpolateColor(com.google.maps.android.heatmaps.GradientTest):
07:32:38 V/InstrumentationResultParser: java.lang.AssertionError: expected:<-65434> but was:<-65433>
07:32:38 V/InstrumentationResultParser: at org.junit.Assert.fail(Assert.java:88)
07:32:38 V/InstrumentationResultParser: at org.junit.Assert.failNotEquals(Assert.java:834)
07:32:38 V/InstrumentationResultParser: at org.junit.Assert.assertEquals(Assert.java:645)
07:32:38 V/InstrumentationResultParser: at org.junit.Assert.assertEquals(Assert.java:631)
07:32:38 V/InstrumentationResultParser: at com.google.maps.android.heatmaps.GradientTest.testInterpolateColor(GradientTest.java:54)

Fortunately, this issue doesn't seem to exist on emulators 26-28, and GradientTest.testInterpolateColor() passes on these emulators.
TODO
So, on emulators 26-28 that leaves us with 1 test failure, GeoJsonPointStyleTest.testIcon():
09:33:02 V/InstrumentationResultParser: There was 1 failure:
09:33:02 V/InstrumentationResultParser: 1) testIcon(com.google.maps.android.data.geojson.GeoJsonPointStyleTest)
09:33:02 V/InstrumentationResultParser: java.lang.NullPointerException: IBitmapDescriptorFactory is not initialized
09:33:02 V/InstrumentationResultParser: at com.google.android.gms.common.internal.Preconditions.checkNotNull(Unknown Source:11)
09:33:02 V/InstrumentationResultParser: at com.google.android.gms.maps.model.BitmapDescriptorFactory.zzg(Unknown Source:2)
09:33:02 V/InstrumentationResultParser: at com.google.android.gms.maps.model.BitmapDescriptorFactory.defaultMarker(Unknown Source:22)
09:33:02 V/InstrumentationResultParser: at com.google.maps.android.data.geojson.GeoJsonPointStyleTest.testIcon(GeoJsonPointStyleTest.java:66)

This issue is related to the Google Maps API not being initialized prior to using it, and the solution is to call MapsInitializer.initialize() first.
However, we're already doing this in GeoJsonPointStyleTest.setUp():
@Before
public void setUp() {
	MapsInitializer.initialize(InstrumentationRegistry.getInstrumentation().getTargetContext());
	pointStyle = new GeoJsonPointStyle();
}

So, I'm not sure why this test is failing on Travis.
Unless someone else has ideas for how to get this test to pass on Travis, one option is to skip GeoJsonPointStyleTest.testIcon() only when running on Travis.
In the past I've tried to configure skipping tests via environmental variables on Travis, but this hasn't worked for me:
// Don't run this test on Travis CI
String runningOnTravis = System.getenv("RUNNING_ON_TRAVIS");
if (runningOnTravis != null && runningOnTravis.equals("true")) {
	Assume.assumeTrue("Skipping GeoJsonPointStyleTest.testIcon() - this is expected behavior when running on Travis CI", false);
}

runningOnTravis is always null, so the Travis build doesn't seem to be picking up the variable from the Travis web console config.
Another option is to simply comment out the test for now.
@jpoehnelt and @amuramoto do you have any preferences on how to address the failing test on CI, and any suggestions on how to configure Travis with an environmental variable that can be read on Android?
References

https://travis-ci.org/ankidroid/Anki-Android/builds/516486599
https://github.com/ankidroid/Anki-Android/blob/master/.travis.yml
https://github.com/OneBusAway/onebusaway-android/blob/ec5a49f0698e2fe7c00e970a788d3fe94a07feb5/.travis.yml
https://github.com/barbeau/gpstest/blob/master/.travis.yml

Hmmm...based on https://travis-ci.org/googlemaps/android-maps-utils/builds/607306060, it appears sometimes this configuration errors with:
> Task :library:connectedDebugAndroidTest
Skipping device 'test(AVD)' for 'library:': Unknown API Level
 > : No compatible devices connected.[TestRunner] FAILED
Found 1 connected device(s), 0 of which were compatible.
07:52:19 I/XmlResultReporter: XML test result file generated at /home/travis/build/googlemaps/android-maps-utils/library/build/outputs/androidTest-results/connected/TEST-TestRunner-library-.xml. Total tests 1, failure 1,
> Task :library:connectedDebugAndroidTest FAILED

I'm looking into it.

Regarding the envar skip, try just System.getenv("TRAVIS")

@jpoehnelt I tried this:
        if (System.getenv("TRAVIS") != null) {
            Assume.assumeTrue("Skipping GeoJsonPointStyleTest.testIcon() - this is expected behavior on Travis CI (#573)", false);
            return;
        }

...but the test still executes on Travis:
https://travis-ci.org/googlemaps/android-maps-utils/builds/607323180#L2862

I would just comment out the test and an a bug for now if it proves too difficult to ignore in travis.

😻

@jpoehnelt I left them in the .travis.yml, but commented out for now. To my knowledge at this time there isn't anything that would differentiate a build between APIs 26-28, so I didn't enable them to avoid burning unnecessary data center time (each build runs around 13 minutes :deciduous_tree: :recycle:). If you have a strong preference for enabling them I certainly can.

Nice work @barbeau 👏

For the record, it looks like this is the reason why the GradientTest.testInterpolateColor() test fails on emulators 17, 18, and 21-25 - it's an implementation issue with android.graphics.Color.RGBToHSV():
https://stackoverflow.com/a/28070310/937715

And, the GradientTest.testInterpolateColor() issue isn't specific to Travis - I can repro it on my desktop with an API 24 emulator.


Package request: Android Translation Layer

Project description
A translation layer that allows running Android apps on a Linux system
Metadata

home URL: https://gitlab.com/android_translation_layer
source URL: https://gitlab.com/android_translation_layer/android_translation_layer
license: gpl
platforms: linux

Add a :+1: reaction to issues you find important.

I've started some work on this, and it looks quite complicated. There's a lot of hardcoded /bin/bash, /usr/local etc, it has both Java and C# components (each of which are horrible to deal with in Nix), also at least some dependencies are trying to fetch their own dependencies from the network as part of the build process. I think it's at least a week of work if not more.

Here's my progress so far: https://gist.github.com/balsoft/8fdb414c8c29095faeb6ae3220171268
It builds and runs a couple of sample apps (com.ashwin.example.accelerometerdemo.apk, demo_app.apk, glmark2.apk, org.happysanta.gd_29.apk, views_widgets_samples_flower_finder.apk) and NewPipe (but there's no networking). Most other apps crash with different errors. I suspect at some point I'll give up and put it in buildFHSEnv, but unfortunately just doing that doesn't help either.
If you're willing to help, join #android-translation-layer:matrix.org and ping @balsoft:balsoft.ru

@balsoft would you mind creating a draft PR so we can try to improve your work :)

created a draft PR feel free to take over or give feedback :) https://github.com/NixOS/nixpkgs/pull/357220


Adds direction to larf

Closes #151

This is not urgent but I think that
(1) A similar direction flag can be used in larfg, this would enable, in geql2 to not have to use the alpha and vector representation in larfg but simply gives the full vector as is done in geqr2.
(2) in addition to implement the direction flag in larfg+larf, we will also want to implement the storev flag in larfg+larf. This way we can remove the conjugation of v in the  gelq2 code at lines
https://github.com/tlapack/tlapack/blob/78dc01b426af3ca57be127c0a76b1e160fcb1ca6/include/tlapack/lapack/gelq2.hpp#L116
and lines
https://github.com/tlapack/tlapack/blob/78dc01b426af3ca57be127c0a76b1e160fcb1ca6/include/tlapack/lapack/gelq2.hpp#L127
And in a similar way, we will be able to remove the conjugation flag in gerq2 code (which we do not have yet).
(3) That way, we would have specialized larfg+larf for the cases
QR is direction=Forward, storev = Columnwise
QL is direction=Backward, storev = Columnwise
LQ is direction=Forward, storev = Rowwise
RQ is direction=Backward, storev = Rowwise
and I think the four codes would be more readable.


Hope EF can be compatible with ADO. NET, including Enterprise Library, and support MyBatis-like framework, support Sql statements in XML file configuration

Hope EF can be compatible with ADO.NET, including Enterprise Library, and support similar MyBatis framework, support Sql statements in XML file configuration, mainly considering the performance of large projects with EF or problems, especially more than a dozen table associations, and the amount of data is very large, or ADO.NET square. Good performance, Microsoft has abandoned the update maintenance EnterpriseLibrary

support similar MyBatis framework, support Sql statements in XML file configuration

@ghd258 There doesn't seem to be any specific question here, so closing. If you have a specific question or issue, then please file a new issue including full details of what the scenario is, what's not working, and any other details that will help us understand specifically what you are asking.


fixes #106

Pull Request Test Coverage Report for Build 1881

14 of 14 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 79.782%

Totals

Change from base Build 1877:
0.3%

Covered Lines:
706

Relevant Lines:
827

💛  - Coveralls


Account sessionInfo is null

Hey all, when calling:
final response = GigyaSdk.instance.login();
final account = Account.fromJson(response);

I'm seeing the sessionInfo property as null.  When I inspect the network response - I see this sessionInfo in the response, but it seems to not de-serialize succesfully.

Hi,
Please follow this flow as described in example project:
the login call is async.
GigyaSdk.instance.login(loginId, password).then((result) {
      final response = Account.fromJson(result);
      setState(() {
        _inProgress = false;
        _requestResult = 'Login success:\n\n ${response.uid}';
      });
    }).catchError((error) {
      if (error.getInterruption() == Interruption.conflictingAccounts) {
        LinkAccountResolver resolver = GigyaSdk.instance.resolverFactory.getResolver(error);
        _resolveLinkAccount(resolver);
      } else {
        setState(() {
          _inProgress = false;
          _requestResult = 'Register error\n\n${error.errorDetails}';
        });
      }
    });

Regards,
Tal

Hey @tal-mi thanks for the response. I've updated my code snippet to show that I'm awaiting the async call and still not seeing the sessionInfo property. This happens in the example app as well.

Hi,
That's odd. I've just verified it (before I answered) on the example application with the latest version.
Can you send the exact code snippet you are using and which version/platform?
Thanks,
Tal

Here are the reproduction steps:

Fetch latest from main branch, commit 0c126bfe448526b5ebb813e7c60eb8365270a1cb
Updated GigyaApiKey in the Info.plist to point to our Gigya site
updated _sendLoginRequest method print the sessionInfo.sessionToken here:

  void _sendLoginRequest(loginId, password) async {
    setState(() {
      _inProgress = true;
    });
    GigyaSdk.instance.login(loginId, password).then((result) {
      debugPrint(json.encode(result));
      final response = Account.fromJson(result);
      print('sessionToken: ${response.sessionInfo?.sessionToken ?? 'null'}');
      setState(() {
        _inProgress = false;
        _requestResult = 'Login success:\n\n ${response.uid}';
      });
    }).catchError((error) {
      if (error.getInterruption() == Interruption.conflictingAccounts) {
        LinkAccountResolver resolver =
            GigyaSdk.instance.resolverFactory.getResolver(error);
        _resolveLinkAccount(resolver);
      } else {
        setState(() {
          _inProgress = false;
          _requestResult = 'Register error\n\n${error.errorDetails}';
        });
      }
    });
  }

The log output
flutter: {"isActive":true,"isVerified":false,"UID":"d533b1019d2d4a6fa1fb7077c8554846","isRegistered":true,"registeredTimestamp":1610991489,"registered":"2021-01-18T17:38:09.138Z","createdTimestamp":1610991488,"signatureTimestamp":"1618756173","oldestDataUpdatedTimestamp":1610991488961,"socialProviders":"site","lastUpdated":"2021-04-07T23:05:21.659Z","oldestDataUpdated":"2021-01-18T17:38:08.961Z","profile":{"firstName":"RobDog","email":"rob.g+30@test.com","lastName":"","zip":"11222"},"lastLoginTimestamp":1618756173,"created":"2021-01-18T17:38:08.961Z","loginProvider":"site","lastLogin":"2021-04-18T14:29:33.333Z","UIDSignature":"0h9WgB7ue2u1GFW7Foe+sdhwphA=","lastUpdatedTimestamp":1617836721659,"apiVersion":2}
flutter: sessionToken: null

Thank you.
We will investigate and update.

The issue will be resolved in 0.0.6 release.
In order to get the "sessionInfo" object, you will need to add the following to your custom account class in your host app:
var sessionInfo: [String: AnyCodable]?
See UserHost.swift class in the example project.
In addition, we have fixed our account model to adjust the "sessionExpiration" getter to match both core SDK serialization.
Regards,
Tal


Write service/utils that handles wallet/account acquiring

Working with multisigs, signatories and proxied wallets always leads to finding the specific wallet/account which is tedious and obviously repetitive.  We need to come up with a service/utils that abstracts all this away and stops developers from suffering trying to get another signatory for multisig wallet.
Part of this would be solved when we implement #1529
Most obvious cases:

Finding wallets for proxied wallet still must be addressed.
Do not take into account root account for PV wallet.
Filter WOW when searching through wallets.
Get wallet by signatory.

After DI and plugin approach solution this task is not more relevant.


[Dashboard] [Datasets] Add filter dropdown to datasets page

Related to #14321

retest this please


Textboxes editable updated

Breaks on text overflow:

Also, text boxes are now fixed width and cant scale with the page.


One faulty slo disables all slos

What I observed:
when one faulty slo is deployt (the prometheus metric cannot be parsed) in k8s as kind: ServiceLevelObjective, the Web-UI refuses to show any SLO that worked before.
What I expect:
when a SLO cannot be execute it should be ignored, maybe with an error message, but it should not interfere with the working SLOs. The correct SLOs should still be visible.
The version I have used is v0.6.3

FWIW the Prometheus recording rules that previously have been successfully loaded are still working and alerting within Prometheus.
I agree with the fact that we should probably in that case handle it more gracefully.


compute-scroll-into-view doesn't cope with rtl layouts

When the dir attribute of an ancestor node is set to "rtl" compute-scroll-into-view calculates the wrong scrollLeft positions.
To illustrate this I've created a jsfiddle - https://jsfiddle.net/6ckneau1/1/. When you click the "Scroll 7 into view" button in the LTR example it works just fine. When you click the "Scroll 7 into view" in the RTL example it doesn't scroll it into view.
The bug is caused by the way browsers report/use scrollLeft when in RTL. You may want to use a library like this https://github.com/alitaheri/normalize-scroll-left to address this issue.

Hi !
I'm also trying to migrate all our scroll logic to this library, unfortunately RTL is indeed not working at all. Is there any plan to add support for RTL? :)

@MarkFalconbridge , I've pushed a PR that adds support for RTL (#907 )
I only tried a few use cases I had, feel free to try it and let me know if you are encountering edge cases.


Convert the project to Typescript

Title captures everything.
Let me know if you'd be open to it.

Thanks for your interest. Let me know if you wanna collaborate!

Received! we will perform the test and merge ASAP
Thanks for the contribution


Bwt 349: park-access-statuses API endpoint filter for accessStatus field

Jira Ticket:
Bwt 349
Jira Ticket URL:
https://bcparksdigital.atlassian.net/jira/software/projects/BWT/boards/5?assignee=633db6bb61dbef2805c1f25c&selectedIssue=BWT-349

@nataliasabadysh would it be fairly easy to also add support for a accessStatus_ne parameter?
e.g. ?accessStatus_ne=Open
I think this option might accomplish the original goal of the ticket description better than checking for 9 different values.

Open
Full closure
Closed to the public
Inaccessible
Park is under evacuation alert
Park is inaccessible
Restricted; permit required
Park is under evacuation order
Park is within a fire perimeter
Warning


Fix load on enter

Overview
After https://github.com/UTDNebula/utd-trends/pull/298/files, since searching is initiated quicker, user feels some lag while waiting for search results
What Changed
Set the loading state quicker, and add a loading icon in the search button

I am calling setSearchResultsLoading() inside the useEffect that has searchResultsLoading as a dependency. Is this bad practice?

I don't really like the solution. It works but it introduces an unnecessary state I feel like combining it with results.state is probable better but idk how to fully.

Another problem:
On search from landing page to dashboard, it calls DashboardEmpty and then DashboardError before the searchResultsTable Skeletons
If I modify:
    contentComponent = <DashboardEmpty />;```
and Remove the DashboardError elseif, then for a second, it shows the "No Results" state from searchResultsTable.tsx

Ideally:
Initiate search from landing -> directly shows srt's loading state, nothing in between

Can revert but lmk what you think of these changes to use results.state and remove the flashing DashboardError and DashboardEmpty.
Opinion: I don't feel the spinner in the search bar is all that necessary when the whole page changes to a loading state.
Current issue (possibly unsolvable): There's also an issue when reloading/opening the dashboard (but not when navigating to it from the homepage) where the searchResultsTable and RHS cards flash white. I seems this is just in the split second before CSS is loaded but it is odd

the topMenu does still jump around because SSR seems to be rendering it as mobile first because of the media query it uses. there might be a css solution

solved! turns out using an actual media query instead of useMediaQuery fixes this. Probably because SSR can guess what the size should be

[ ] Do not search when user clicks on an autocomplete suggestion
[ ] If you type out cs 1200, space, cs2337, space, clicking enter does not search

Everything else works perfectly. Searches appear faster because there is less lag in between and code-wise it's very simple

Do not search when user clicks on an autocomplete suggestion
If you type out cs 1200, space, cs2337, space, clicking enter does not search

I think #298 caused both of these issues as they are present on that PR, dev, and prod.


hack max age

Hey there! So you want to contribute to a Firebase SDK?
Before you file this pull request, please read these guidelines:
Discussion

Read the contribution guidelines (CONTRIBUTING.md).
If this has been discussed in an issue, make sure to link to the issue here.
If not, go file an issue about this before creating a pull request to discuss.

Testing

Make sure all existing tests in the repository pass after your change.
If you fixed a bug or added a feature, add a new test to cover your code.

API Changes

At this time we cannot accept changes that affect the public API.  If you'd like to help
us make Firebase APIs better, please propose your change in an issue so that we
can discuss it together.

sorry, meant to point this to my fork
but tbh the absence of even something remotely official that acknowledges what steps need to be taken to address this problem is a massive disappointment.

sorry meant to point this to my fork, pointed it here instead by mistake


If cfoundry has a similar api as cf-java-client's getFile(String appName, int instanceIndex, String filePath, int startPosition, int endPosition) ?

ATT

Hi @chenwj,
We are having trouble understanding your question.
Are you asking if cfoundry and the cf-java-client use the same API endpoint? Or does cfoundry have a similar api as the cf-java-client? If not, we would appreciate more clarification.
Thanks,
@crhino and @jfmyers9, CF Runtime Team

My problem is how to get a portion of a file in cloudfoundry by the api of cfoundry , I have found that client.request(...,"Range: bytes={start}-{end}")  can solve . I will close this issue.

@crhino My problem is how to get a portion of a file in cloudfoundry by the api of cfoundry , I have found that client.request(...,"Range: bytes={start}-{end}") can solve it. I will close this issue.


packaging: use setx /m to register wazero instead

Addresses #1374.
The most important issue with this strategy is that it has
the potential to break the end-user PATH variable if for some
reason the combined length is longer than 1024 chars.
The reason the current strategy is not working are at least two:

%PATH% is not expanded in:
<CustomAction Id="ChangePath"
ExeCommand="PATH "%PATH%;[INSTALLDIR]""
Property="setx" ...
The "correct" syntax seems to be [%PATH] instead of %PATH%

SETX is not working(*) inside MSI (at least on my Win11 machine)
unless we use the flag /M which modifies the env variable
at the system level.

Furthermore:

SETX PATH "C:\Program Files\wazero;%PATH%" expands %PATH%
AND truncates it to 1024 chars. Because of this, appending may
be safer: worst case, it truncates the path you have appended

However, for some reason I couldn't make it work from within
the MSI installer, so I still had to prepend...

(*) I assume it's running as a different user than %currentuser%
and SYSTEM; maybe "Local Service"?
Signed-off-by: Edoardo Vacchi<EMAIL_ADDRESS>

Will do. I am also further investigating a different approach (using the actual WIX tool chain instead)

I have updated the wix file to v4 (it may not be strictly required TBF) and actually used the Environment section which seems to be working as expected (it shouldn't be a surprise, since I think this is the official tool). If we do go this route it'll require proper setup of the CI (but I think there are a bunch of GHA that may be used) see WIP https://github.com/evacchi/wazero/commit/464a9e37ca6905e3ab960481870d2350a5f45581#diff-217b40bac6395c4cd76179d71ebc5cda14719c5fec343444884d6faff2e61b2fR98

yes, I was just checking it and apparently we already verifying this. The issue may be that GHA is running as a privileged user so the problem doesn't present itself.
wix v3 is already present in the windows-2022 runner, it could be configured under Ubuntu but it requires to install wine and some fiddling... 🤔 so either we break the build into 2 steps or we figure out how to configure wix v3 under the Ubuntu runner... 🤔

just a thought.. if CI was working because the result path <1024 chars, maybe the CI step could be configured with a really long PATH (even if invalid entries) to force the issue..

in fact, in the meantime I have tested this smaller patch under the native wix3 toolchain and it seems to work https://github.com/evacchi/wazero/commit/wix3-native-build

I have created https://github.com/tetratelabs/wazero/pull/1385 because I wanted to show both approaches. If I may explain visually:

In this PR:

I could not manage to make the CI fail reliably when the %PATH% is corrupted. For that matter, I am not sure I was able to corrupt %PATH%
The only approach that WorksForMe™ is to prepend the install path to the system path using SETX /M, which for long PATH env may push one of the valid elements of the list off the 1024 boundary, effectively corrupting the system PATH. Notice that I am not an expert, so I am just assuming.
Another approach may be editing the registry directly; I didn't try this.

in PR #1385:

msitools do not support the Environment directive, so we can try the "official" tools
I was not able to run native WiX under macOS/Linux. They are not supported because they use native platform libraries. In theory there are ways to run it under wine: it didn't work for our project, in my tests (tried that too!)
I am running the entire make dist step under on the windows-2022 runner so that we can use native WiX Tools v3
alternative: run only make dist "msi" under a Windows runner

Thanks for the writeup. I think it is ok for us to run the release on windows until someone can compile the official tools to wasm, so we can run them on linux.
I was hoping msitools would progress, but the environment thing there went no-where.
As long as @mathetake is ok running on windows, I think we should go with PR https://github.com/tetratelabs/wazero/pull/1385. Maybe you can build an MSI on that and make sure the original person who had the problem is able to use it (e.g. attach the MSI to the PR or the issue leading to it, zipping if necessary)

closing in favor of https://github.com/tetratelabs/wazero/pull/1385


Show metric metadata

Add metadata on the metric selected in select-metric in metric-metadata .
Tasks

[ ] Decide what metric metadata to show for each metric, e.g. maximum distance from catch location, speed
[ ] Reload on new selection or when returning to default
[ ] See https://github.com/LifeWatchINBO/bird-tracking/issues/39#issuecomment-55262417 to see what interactions trigger a reload

Maybe averages are more interesting. The maxima should be pretty clear from the month calendar chart:

average distance travelled per day for this selection
average maximum distance from catch location per day. (should think of a better way to formulate this. I mean: 'on average, how far does this bird travel from his nest on one day')


Elemental fixes

Make sure all of your files end with a single blank line, https://github.com/concrete5/concrete5/pull/3860/files?w=1#diff-4e43c0fdfcc2e1175c7f23ef68ce6af0R43 does not

Good one, fixed it.
@KorvinSzanto btw, do you know if there is a way to get the php-cs-fixer to work with template files?

@a3020 typically view files are excluded from our formatting, not sure how to get cs-fixer to work well with them.

Thanks for this, it's nice to see short array syntax in here


Use 'react-transition-group/CSSTransitionGroup' package instead of 'react-addons-css-transition-group'

react-addons-css-transition-group has been deprecated and has been put in the react-transition-group package since React v15.5.0.

Fixed in 8873620, this will go out in the next release.


Draft: feat: update to Node18, remove cross-fetch and publish as ESM only

[x] Remove cross-fetch
[x] Run tests Browser && Node
[ ] ESM only

Codecov Report

Merging #386 (d8a179a) into main (c45a5d8) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #386   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           44        44
  Lines          636       636
  Branches       129       129
=========================================
  Hits           636       636

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


Increment versions for orbital releases

Increment package versions for orbital releases

API change check
API changes are not detected in this pull request.


The x86 boost-build tools must be installed to build for non-x86/x64

Hi, i follow the instructinos here to setup android toolchain/TRIPLET:
https://github.com/microsoft/vcpkg/issues/4124#issuecomment-414986538
And it works for zlib and some other libraries. but if i want to compile libtorrent, i get an error:
╰ ./vcpkg install libtorrent:arm-android
The following packages will be built and installed:
  * boost-algorithm[core]:arm-android
  * boost-asio[core]:arm-android
  * boost-atomic[core]:arm-android
  * boost-bind[core]:arm-android
  * boost-chrono[core]:arm-android
  * boost-container[core]:arm-android
  * boost-context[core]:arm-android
  * boost-coroutine[core]:arm-android
  * boost-crc[core]:arm-android
  * boost-date-time[core]:arm-android
  * boost-dynamic-bitset[core]:arm-android
  * boost-endian[core]:arm-android
  * boost-exception[core]:arm-android
  * boost-filesystem[core]:arm-android
  * boost-foreach[core]:arm-android
  * boost-function[core]:arm-android
  * boost-functional[core]:arm-android
  * boost-intrusive[core]:arm-android
  * boost-io[core]:arm-android
  * boost-iostreams[core]:arm-android
  * boost-lambda[core]:arm-android
  * boost-lexical-cast[core]:arm-android
  * boost-locale[core]:arm-android
  * boost-math[core]:arm-android
  * boost-multiprecision[core]:arm-android
  * boost-numeric-conversion[core]:arm-android
  * boost-phoenix[core]:arm-android
  * boost-pool[core]:arm-android
  * boost-proto[core]:arm-android
  * boost-random[core]:arm-android
  * boost-range[core]:arm-android
  * boost-ratio[core]:arm-android
  * boost-rational[core]:arm-android
  * boost-regex[core]:arm-android
  * boost-scope-exit[core]:arm-android
  * boost-serialization[core]:arm-android
  * boost-spirit[core]:arm-android
  * boost-system[core]:arm-android
  * boost-thread[core]:arm-android
  * boost-tokenizer[core]:arm-android
  * boost-tti[core]:arm-android
  * boost-type-index[core]:arm-android
  * boost-unordered[core]:arm-android
  * boost-variant[core]:arm-android
  * boost-winapi[core]:arm-android
  * bzip2[core]:arm-android
  * libiconv[core]:arm-android
    libtorrent[core]:arm-android
  * zstd[core]:arm-android
Additional packages (*) will be modified to complete this operation.
Starting package 1/49: boost-regex:arm-android
Building package boost-regex[core]:arm-android...
-- Using cached /home/linarcx/Development/vcpkg/downloads/boostorg-regex-boost-1.69.0.tar.gz
-- Using source at /home/linarcx/Development/vcpkg/buildtrees/boost-regex/src/ost-1.69.0-80bf9a4997
CMake Error at installed/arm-android/share/boost-build/boost-modular-build.cmake:18 (message):
  The x86 boost-build tools must be installed to build for non-x86/x64
  platforms.  Please run `vcpkg install boost-build:x86-windows`.
Call Stack (most recent call first):
  ports/boost-regex/portfile.cmake:20 (boost_modular_build)
  scripts/ports.cmake:71 (include)

Error: Building package boost-regex:arm-android failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: boost-regex:arm-android
  Vcpkg version: 2018.11.23-unknownhash

Additionally, attach any relevant sections from the log files above.

Os: arch linux

?
cat  /home/linarcx/Development/vcpkg/triplets/arm-android.cmake

set(VCPKG_TARGET_ARCHITECTURE arm)
set(VCPKG_CRT_LINKAGE dynamic)
set(VCPKG_LIBRARY_LINKAGE static)

set(VCPKG_CMAKE_SYSTEM_NAME Android)

?
uname -a

vcpkg/scripts/toolchains/android.cmake
if (VCPKG_TARGET_TRIPLET STREQUAL "arm64-android")
    set(ANDROID_ABI arm64-v8a CACHE STRING "")
elseif(VCPKG_TARGET_TRIPLET STREQUAL "arm-android")
    set(ANDROID_ABI armeabi-v7a CACHE STRING "")
elseif(VCPKG_TARGET_TRIPLET STREQUAL "x64-android")
    set(ANDROID_ABI x86_64 CACHE STRING "")
elseif(VCPKG_TARGET_TRIPLET STREQUAL "x86-android")
    set(ANDROID_ABI x86 CACHE STRING "")
else()
    message(FATAL_ERROR "Unknown ABI for target triplet ${VCPKG_TARGET_TRIPLET}")
endif()

elseif(VCPKG_TARGET_TRIPLET STREQUAL "arm-android")
    set(ANDROID_ABI armeabi-v7a CACHE STRING "")

arm-android -->> ANDROID_ABI armeabi-v7a
--host ARM =  uname -a ?

try this ))
set(VCPKG_TARGET_ARCHITECTURE arm)
set(VCPKG_TARGET_ARCHITECTURE x64)

uname -a

Linux linarcx 4.19.41-1-lts #1 SMP Wed May 8 15:58:57 CEST 2019 x86_64 GNU/Linux

x64

Nothing changed.

android toolchains not tested, apparently therefore not yet added
and you write too little debug information, I don `t know what's going on in your car
maybe someone else will answer wait

PR https://github.com/microsoft/vcpkg/pull/16479 should address this issue.

@LinArcX, the PR has been merged, could you get vcpkg latest source and try again?

This should not be a problem now, please reopen this issue if it persists for you.


Removing Project Mercury Codename from README and other documentation

PR Summary
Since we are approved to use the name AI Shell, we are removing the Project Mercury codename from the repository. There still may need to be changes to the pipeline for the future release cc @daxian-dbw
PR Context

I will submit a separate PR to update the YAML files for pipelines.


Cannot sign transaction when using npm version

It's ok when using a built version in local

Can't reproduce on 0.4.5. Close by now

Cannot reproduce this error, weird


Support terminal dimensions in gRPC runner

Solves #252
Added a section to examples/README.md to test against.

Currently need new build of protobuf definitions to continue @sourishkrout, see slack

Functionality good, would like to write unit tests before merge.


adding speech recognition news

Pull Request Template
script name -
newsapi.py
Brief about script
Pulls articles from newsapi.org and from there, summarizes the article. It then puts the article in a json format and adds it to a text folder which will get the title of the article, the summary, the url and the date.
Issue no.(must) - #311
Self Check(Tick After Making pull Request)

[x] This issue was assigned to me.
[x] One Change in one Pull Request
[ x] My file is in proper folder (Name of folder should be in lowercase with no space in between) (E.g. meet_schedular)
[x ] I am following clean code and Documentation and my code is well linted with flake8.
[x ] I have added README.md and requirements.txt (Include version numbers too e.g. pandas==0.0.1) with my script
[x ] I have used REPO README TEAMPLATE (Necessary)
[ x] Just including required dependencies in requirements.txt (Don't include Python version too)

If issue was not assigned to you Please don't make a PR. It will marked as invalid.

@pawangeek I followed the guide for lint and it seems as thought I have errors in my code?


chore: remove footer info

Description

What type of PR is this?

[x] 🍕 Feature

I removed the footer information. I think we don't need those information now.
Related Tickets & Documents

@hismethod done.


[Feature request] Support for plotting vector graphics

We could read in an SVG and plot it as a bitmap or something, it would be nice to have for plotting LaTeXStrings.

Implemented in https://github.com/JuliaPlots/MakieTeX.jl.


Make use of new colors

From: https://artsy-elan-production.herokuapp.com/colors

Closed in https://github.com/artsy/force/pull/691


[PDI-18989]-PGBulkLoader not closing connection at end of transformation

[PDI-18989]-Provided a Bug fix.

:white_check_mark: Build finished in 7m 24s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:exclamation: No tests found!
:information_source:  This is an automatic message


improvement Support to use cast when create sync materialized view

Proposed changes
Support to use cast when create sync materialized view
Such as sync mv def is as following:
you can use cast(FLOOR(MINUTE(time) / 15) as decimal(9, 0))  in mv def which is not allowed before.

CREATE MATERIALIZED VIEW sync_mv
AS
SELECT
  decision,
  code,
  app_name,
  event_id,
  event_type,
  date_trunc(time, 'minute'),
  DATE_FORMAT(
    `time`, '%Y-%m-%d'
  ),
  cast(FLOOR(MINUTE(time) / 15) as decimal(9, 0)),
  count(id) as cnt
from
  test
group by
  code,
  app_name,
  event_id,
  event_type,
  date_trunc(time, 'minute'),
  decision,
  DATE_FORMAT(time, '%Y-%m-%d'),
  cast(FLOOR(MINUTE(`time`) / 15) as decimal(9, 0));

run buildall

run performance


Change for packer 0.8.1, now plugin build successfully.

Oops, tests need fix too.

@mightydok please run a make format and commit any diffs.

@StefanScherer done

@mightydok Thanks. Compiling works! I'm currently testing a new Windows binary in my basebox-slave pipeline.

@frapposelli LGTM!

Thanks @mightydok for the patch.
and thanks @StefanScherer for the review!


Make git push heroku master not crash first, then work through details

Right now, creates Procfile. collectsatic is disabled. Build doesn't error out, but app not up because gunicorn is not installed. Fix these kinds of issues before focusing on details like db and static files.

Tasks

[ ] Add a check for AUTOCONFIGURE_ALL, and put all of this work in that block for now.
[ ] Install gunicorn.

Now getting disallowed_host, which is progress!


WASM: Fix measuring bug with TextBlock

Bugfix
Since work on performance, the TextBlock on Wasm wasn't measuring correctly
when constrains were applied to it.
What is the current behavior?
Wrong calculation, caused by an invalid css instructions (need to be max-width & max-height
but was maxWidth & maxHeight).
What is the new behavior?
Correct css instructions are now applied.
PR Checklist
Please check if your PR fulfills the following requirements:

[X] Tested code with current supported SDKs
[X] Docs have been added/updated which fit documentation template. (for bug fixes / features)
[X] Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
[X] Contains NO breaking changes
[ ] Updated the Release Notes
[X] Associated with an issue (GitHub or internal)

Internal Issue (If applicable):

https://nventive.visualstudio.com/Umbrella/_workitems/edit/151838 Uno.UI.Banner AppContent TextBlock is not wrapping

/azp run


Furi characters invisible

Title explains my issue. The character I play as, the boss and one or two of the attacks are invisible. Everything else renders fine though. This is an example of the issue, it's using 396.51 drivers in the screenshot but it still results in the same issue with 396.54.

This is an example of the characters rendering and running with wined3d11.

Software information
Furi on Beautiful graphics option @ 1080p 60Hz
System information

GPU: Nvidia GeForce GTX 980 Ti
Driver: Proprietary 396.54
Wine version: 3.14-staging
DXVK version: 0.70 then Commit 48697346c06011938ba04576cca45a5ae58d3227 (22 August)

Apitrace file(s)
Apitrace
Log files

d3d11.log
dxgi.log

D3D11Device::CreateBuffer: D3D11_BIND_STREAM_OUTPUT not supported

See #135

Closing because duplicate of above.


polymer-ready not working

Greatings. This editor "eats" code examples - so I deleted all "<" symbols in start of each line.
!DOCTYPE html>
html lang="en">
head>
meta charset="utf-8">
meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
meta name="viewport" content="width=device-width, initial-scale=1.0">
meta name="mobile-web-app-capable" content="yes">
meta name="apple-mobile-web-app-capable" content="yes">
script src="bower_components/webcomponentsjs/webcomponents.js">/script>
link rel="import" href="bower_components/polymer/polymer.html">
/head>
body fullbleed layout vertical>
p id="ma">Html /p>
script>
document.addEventListener('polymer-ready', function()
{
document.getElementById('ma').innerHTML = "JavaScript";
};
/script>
/body>
/html>
If I change
"document.addEventListener('polymer-ready', function()"
to
"window.onload = function()"
All is working.
my email is<EMAIL_ADDRESS>.Please send me feedback.
Reagrds, Bohdan K.

Closing this issue due to age and the release of version 1 of Polymer - please feel free to re-open if this is incorrect.


Handle Groups with Delimiter::None

Currently, rustc does not pass the exact original TokenStream to
proc-macros in several cases. This has many undesirable effects, such as
losing correct location information in error message.
See https://github.com/rust-lang/rust/issues/43081 for more details
In the future, rustc will begin passing the correct TokenStream to
proc-macros. As a result, some tokens may be wrapped in a
TokenTree::Group with Delimiter::None (when the tokens originally
came from a macro_rules!) macro expansion.
I've determined that this change will cause your crate to stop
compiling. This PR updates obfstr to be compatible with both the
old and new TokenStream contents.
You can verify this PR by attempting to build your crate as follows:
rustup toolchain install nightly-2020-05-29
cargo +nightly-2020-05-29 build

This will built your crate with an older nightly build that
contains the change we want to eventually roll out.
On this compiler version, your crate should fail to compile without this
PR, and successfully compile with this PR.
If you have any questions, feel free to ask me. See https://github.com/rust-lang/rust/issues/72622 for more details

I didn't notice https://github.com/CasualX/obfstr/pull/9: feel free to close this PR if it's no longer necessary :smile:

Thanks!
Don't worry about #9 as it's an experiment and needs a fairly recent nightly to compile while this crate right now works on stable.
Your breaking change just made me revisit this crate so I tried pushing const fn and const generic as far as I could. Which worked pretty well :)


ASP.NET MVC 4 with Babel 7 + server-side rendering + Fragments ?

I've just added ReactJS.NET 4.1.1 to my ASP.NET MVC 4 project and tried to do some server-side rendering using @Html.React()
I realized I couldn't use React.Fragment though because it requires Babel 7.
So I was wondering if you have any idea when ReactJS.NET with Babel 7 would be available ?
If that's not due soon, can someone advise a good tutorial on how to use the webpack integration as suggested on https://reactjs.net/2019/03/4.1.1-release.html ?
And how to generate a Babel 7-ready bundle.server.js file.
Thank you !

The webpack docs are here: https://reactjs.net/bundling/webpack.html
There is a webpack sample here: https://github.com/reactjs/React.NET/tree/master/src/React.Sample.Webpack.CoreMvc
Babel 7 is currently in one of the alpha builds, please enable it via this setting.
We'll make Babel 7 the default in 5.0 but for now it is opt in.

Using the latest 5.0 alpha 3 and adding the following line did the work, thanks !
ReactSiteConfiguration.Configuration.SetBabelVersion(BabelVersions.Babel7);


show better error message for not converted TFHub module

moved TFHub url update logic to browser http handler and show module not converted message when 404 is returned.
fix issue tensorflow/tfjs#1408

This change is

Is this something we could ask for from the TF Hub team so that we can show a better error message? It's unfortunate we can't differentiate between a 404 (wrong URL) and an unconverted model

Gentle ping


Fix ruby-2.7.0 error by specifying stack

Still getting an error from Heroku:
The Ruby version you are trying to install does not exist on this stack.
 !
 !     You are trying to install ruby-2.7.0 on heroku-20.
 !
 !     Ruby ruby-2.7.0 is present on the following stacks:
 !
 !     - cedar-14
 !     - heroku-16
 !     - heroku-18

Using a different stack, heroku-18, to resolve.

Going to merge so I can create a test service for Rate Limiting and NCC.


Light Cleanup

Removed wireframe raid binary
Updated roadmap/todo notes
Light cleanup

CI failed due to low test coverage. Adding this to the roadmap and then will force merge.


JSON output is broken ?

I simply cannot make the --output-format=json work.

Thanks for reporting, I was noticing the same. I just pushed a fix and will release v1.1.2


avmp: edit member page breaks payments table when clicking save

I'm not entirely sure why this is but I'm receiving a Uncaught TypeError: Cannot read property 'reduce' of undefined.

because we're not populating


Rate limit logging

Any thoughts on logging the % of rate limit consumed (perhaps over a certain threshold?)
When using a ton of probot apps in a single GitHub App on a super busy org, this might be possible. Or maybe it isn't, but right now there's not really any insight into this.
I'd be happy to look into implementing this, just wanted to see if there's any thoughts around this.

Great suggestion. Having better insight into rate limits would be really useful.
GitHub returns headers on each response with rate limit info, so if you set LOG_LEVEL=trace you'll see the noisy logging of all API requests, which includes these headers.
2017-11-20T02:50:39.796759+00:00 app[web.1]: HEADERS: {"server":"GitHub.com","date":"Mon, 20 Nov 2017 02:50:39 GMT","content-type":"application/json; charset=utf-8","content-length":"106","connection":"close","status":"404 Not Found","x-ratelimit-limit":"7450","x-ratelimit-remaining":"7361","x-ratelimit-reset":"1511148561","x-github-media-type":"github.v3; format=json","access-control-expose-headers":"ETag, Link, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval","access-control-allow-origin":"*","content-security-policy":"default-src 'none'","strict-transport-security":"max-age=31536000; includeSubdomains; preload","x-content-type-options":"nosniff","x-frame-options":"deny","x-xss-protection":"1; mode=block","x-runtime-rack":"0.037087","x-github-request-id":"C3A5:10684:A14E65:1170464:5A1242FF"}

Any thoughts on what logging specific to rate limits would look like or how it would work?


Ensure numMachinesPerTest is reset each loop

The way it is currently defined, the last iteration
of the loop will apply to all the tests once they
are executed. Redifining it each loop will ensure
each test gets the correct value.
Related #213
Signed-off-by: Adam Brousseau<EMAIL_ADDRESS>

Tested to be working on Semeru farm.

@llxia or @sophia-guo for review


cannot run "import ipywidgets as widgets"

When I import pyexplainer_pyexplainer, there is an error as shown below

I tried using pip install ipywidgets and conda install ipywidgets but both methods cannot fix the issue.
Do you have any idea to solve this issue?

Hello, did you manage to solve this problem?

I just comment the code that uses the library because I don't use it in my experiment.
However, I think I may have problem with my conda environment and jupyter notebook, which I think I found solution.

Thanks for the update!


Requirement missing for using the INSPIRE harmonised layer name as the layer identifier

The use of ows:Identifier element for Unique Resource Identifier and Name are discussed in chapters <IP_ADDRESS>.4.5 UNIQUE RESOURCE IDENTIFIER and <IP_ADDRESS>.4.6 NAME. However, there are no explicit requirements for using these mappings.
This should be kept in sync with the WMS Name (inspire-eu-validation/ats-view-wms#39) and Unique Resource Identifier (inspire-eu-validation/ats-view-wms#37 and inspire-eu-validation/ats-view-wms#38) requirements and tests.

This is a tricky one, if we assume that one server is allowed to provide both INSPIRE and non-INSPIRE layers. There is not way to automatically identify if a layer is intended to to be an INSPIRE layer or not, and for non-INSPIRE layers the identifier can be anything (as long as it's unique within the service).
What we could do is reserving the right to use identifiers with the INSPIRE theme specific layer name prefixes: If a layer starts with "AU.", "TN." etc. it must be one of the harmonised layer names for that theme.

My best effort on validating this in committed in https://github.com/inspire-eu-validation/ats-view-wmts/blob/master/A.04.layer.name.id.md


@broskoski: Artist module qa

This addresses the QA items in issue https://github.com/artsy/force/issues/61

Tab and header titles need to be adjusted based on rule above "Highlights" vs "History"
When no exhibition history/highlights are present on the bio tab, don't collapse the bio
Make CV button the small-button style
Make the View all articles button small-button style
There should be 20px between article title and byline

Looks good, only real blocker is the case above where exhibition_highlights.length is exactly 15.


[core] Add state.can(event)

This PR adds state.can(...):
someState.can({ type: 'TOGGLE' }); // `true` if it will cause a transition

If we're adding this in core, I would like to see the full functionality of https://github.com/VanTanev/xstate-helpers/blob/development/src/react/useIsXStateTransitionAvailable.ts - eg, type inference for both event types as strings and event objects - XState supports that in other places.
Also, I strongly believe that the result of state.can() should always be a boolean and never undefined. If there is no machine available on the state, can() should just return false.
Also, what is the best practice around memorizing this? Is machine.transition() expensive enough to want to use React.useMemo() around state.can()?

diff --git a/packages/core/src/State.ts b/packages/core/src/State.ts
index 17435556..2762c9b6 100644
--- a/packages/core/src/State.ts
+++ b/packages/core/src/State.ts
@@ -129,7 +129,7 @@ export class State<
    */
   public children: Record<string, ActorRef<any>>;
   public tags: Set<string>;
-  private machine: StateMachine<TContext, any, TEvent, any> | undefined;
+  protected machine: StateMachine<TContext, any, TEvent, any> | undefined;
   /**
    * Creates a new State instance for the given `stateValue` and `context`.
    * @param stateValue
@@ -321,16 +321,16 @@ export class State<
   /**
    * Determines whether sending the `event` will cause a transition.
    *
-   * If this state was created outside of a machine (e.g., with `State.from(...)`), `undefined` will be returned.
+   * If this state was created outside of a machine (e.g., with `State.from(...)`), `false` will be returned.
    *
    * @param event The event to test
    * @returns Whether the event will cause a transition
    */
-  public can(event: TEvent): boolean | undefined {
+  public can(event: TEvent | TEvent['type']): boolean {
     if (!this.machine) {
-      return undefined;
+      return false;
     }

-    return this.machine.transition(this, event).changed;
+    return !!this.machine.transition(this, event).changed;
   }
 }
diff --git a/packages/core/test/state.test.ts b/packages/core/test/state.test.ts
index 8b56738f..70145a3f 100644
--- a/packages/core/test/state.test.ts
+++ b/packages/core/test/state.test.ts
@@ -590,6 +590,10 @@ describe('State', () => {
             on: {
               NO_CHANGE: 'a',
               ACTION: { actions: 'someAction' },
+              ACTION_WITH_COND: {
+                actions: 'someAction',
+                cond: (_: any, e: any) => e.cond
+              },
               CHANGE: 'b'
             }
           },
@@ -598,15 +602,30 @@ describe('State', () => {
       });

       expect(machine.initialState.can({ type: 'UNKNOWN' })).toEqual(false);
+      expect(machine.initialState.can('UNKNOWN')).toEqual(false);
+
       expect(machine.initialState.can({ type: 'NO_CHANGE' })).toEqual(false);
+      expect(machine.initialState.can('NO_CHANGE')).toEqual(false);
+
       expect(machine.initialState.can({ type: 'ACTION' })).toEqual(true);
+      expect(machine.initialState.can('ACTION')).toEqual(true);
+
       expect(machine.initialState.can({ type: 'CHANGE' })).toEqual(true);
+      expect(machine.initialState.can('CHANGE')).toEqual(true);
+
+      expect(
+        machine.initialState.can({ type: 'ACTION_WITH_COND', cond: true })
+      ).toEqual(true);
+      expect(
+        machine.initialState.can({ type: 'ACTION_WITH_COND', cond: false })
+      ).toEqual(false);
+      expect(machine.initialState.can('ACTION_WITH_COND')).toEqual(false);
     });

-    it('should return undefined for states created without a machine', () => {
+    it('should return false for states created without a machine', () => {
       const state = State.from('test');

-      expect(state.can({ type: 'ANY_EVENT' })).toEqual(undefined);
+      expect(state.can({ type: 'ANY_EVENT' })).toEqual(false);
     });
   });
 });

After the last commit, this is chef's kiss~!
💯
Only thing left to fix is an incompatibility with StateConfig type.
It might be OK to make machine a public property?

Oops, my bad for leaving the 2nd machine prop there, sorry.

How should errors thrown by assign actions and guards be treated? How they should be treated when we implement error-related changes and we actually start capturing all unhandled errors? Should an error be counted as a change (errors will, most likely, try to select a transition - why way or another)?

Can this be resolved in a separate PR? Let's keep this one low-scope.

@Andarist Ready for re-review

Can this be resolved in a separate PR? Let's keep this one low-scope.

At this stage, this is a design question about this API - both for v4 and for v5 (the answer can differ for both). I feel like it should be answered before merging this PR in because whatever lands on the main branch should be "releasable" and we shouldn't release something that might change (behavior-wise) soon-ish.
If you don't want to keep this PR low-scope but you'd like to make the design of this more tight & explicit before releasing then you could always create a PR targeting this PR.
If the answer is: "nothing should happen in v4 and errors should bubble to the caller" then it's fine. We can refine this in v5 (but a ticket~ should be created so we don't forget about it) but the appropriate tests should be added to validate this and to prevent us from regressing.

If the answer is: "nothing should happen in v4 and errors should bubble to the caller" then it's fine. We can refine this in v5 (but a ticket~ should be created so we don't forget about it) but the appropriate tests should be added to validate this and to prevent us from regressing.

This is the answer IMO. Just added a test for this 👍
How would this be refined in v5?

How would this be refined in v5?

That depends on the outcome of the error handling refactor. The behavior has been settled for the v4 though so let's just don't bother with thinking how this related to v5

@Andarist Ready for final review 🏁


Nested relations

Hello,
I did a small change to add compatibility with API calls involving related models. for example: GET /books/{id}/chapters Returns the correct count result as X-Total-Count header.
Changes are explained in the README. Thanks !

That's nice. But I should change a bit in README.

No problem, please proceed.

On 3 Jul 2018, at 14:22, Nguyễn Kim Kha<EMAIL_ADDRESS>wrote:
That's nice. But I should change a bit in README.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/kimkha/loopback3-xTotalCount/pull/3#issuecomment-402136606, or mute the thread https://github.com/notifications/unsubscribe-auth/ASTa9ST_mmPl6QRv9qHxJH1M0nRbBKTqks5uC2IAgaJpZM4VAkMm.


When we open the Power BI report and data is stale (older than 7 days) we should have a visual hint to do a refresh

With the newest version, which includes an Azure Workbook to visualize recommendations, no further investments will be made in the Power BI dashboard.


1.11 CNI does not work on OpenShift

install-cni pod fails with:
Error: failed to create UDS listener: failed to listen on unix socket "/var/run/istio-cni/log.sock": listen unix /var/run/istio-cni/log.sock: bind: permission denied

OpenShift does not allow a container to bind to a unix socket unless it's a privileged container

Dup of https://github.com/istio/istio/issues/34211

@jwendell Could you try set LOG_UDS_ADDRESS env variable to a empty string at CNI daemonset and see if that fixes the issue? Asked in the other issue as well, but would be nice if you can try as well.


[Feature] Improve GatewayServer declerative setup in 1.0

Is your feature request related to a problem? Please describe.
With current implementation, creating the GatewayServer resource would generate a Secret resource with a key pair unless a secret already exists.
That makes it very hard for declarative setup that uses SealedSecret for example for creating this Secret as the sealed-secrets controller would refuse to touch the Secret if it already exists, hence there's a race condition here
Describe the solution you'd like
A way of preventing automatically creating the Secret resource with a key pair when creating the GatewayServer resource
Describe alternatives you've considered
I have no alternatives other than manual intervention or manual setup which kinda beats the purpose of declarative setup

Fixed with #2747


deps: update osbuild/images to v0.91.0

Update osbuild/images dependency
Update Go version to v1.22
Update golangci-lint version v1.61.0 (for Go v1.22)

The updated linter detects a few new issues, which have now been fixed or annotated to be ignored.

Looks like RHEL 9.4 is unhappy (Go version issue).


Summary statistics option

Might be a good idea to run all summary statistics modules at the same time (e.g. adding a --stasts option)

Solved in 5d5dc2a

Solved in 5d5dc2a


Text sizing and padding

Text sizing and spacing
Example

[ ] Reduce H1 to 16px equivalent
[ ] Reduce spacing between H1 and H2 to 8px equivalent
[x] ~Increase paragraphs from 13px to 14px to improve legibility~
[x] ~Increase subheading to 14px~

Example

[ ] Add spacing between MFA options to 16px equivalent
[ ] Add spacing to bottom of MFA graphic to 16px equivalent
[ ] Add spacing after MFA options to 16px equivalent

Paragraph sizing is coming from Admin CSS, so we won't alter those. Removed the checkboxes relating to that

Noting that this issue is not fixed by #231, I think that was a typo in the issue number

PR here.


Not pairing on first run after app data clean.

When I clear all data in app,  and launch Wallet demo app again it's not pairing. I click scan QR button, it scans but then nothing happens. Then I need to kill app, and launch it again to make Pair work.

Thanks for reporting.
I'll have a deeper look on that.

Created issue: https://github.com/WalletConnect/WalletConnectKotlinV2/issues/89

Hey, check our latest beta-100 release and test it with https://react-app.walletconnect.com/. There've been many changes and fixes.


Configure pipeline storage for images

I think you need to rebase against the current master.

I think you need to rebase against the current master.

@alexwlchan I think I have fixed things.

@alexwlchan I think I have fixed things.


fix(storage): Fix errors on eventual consistency of storage

Fixes spinnaker/spinnaker#5557 which was found by the integration tests; this applies the second solution outlined there "Instead of fetching the object from storage after creating it, just return the object we placed in storage.".

test(storage): Add some tests
Add a new test implementation of StorageService that simulates an eventually consistent storage backend, and tests on this new implementation.
Also add a test on DefaultApplicationDAO to document the current behavior which is to throw an exception when creating an application against an eventually consistent data store.

refactor(storage): Strengthen contract of StorageService
A StorageService should not implement any business logic and should just store the provided item to the backing store as given.
There are a couple of places where the storage service sets a modified timestamp (in the Azure and SQL backends); arguably this should be done upstream so that this is independent of the backing store but for now we'll leave those there.
Add javadoc to storeObject to explicitly strengthen the contract of this method, which all current implementations respect. In particular, require that the input object reflect exactly what was stored in the persistent store upon returning from the method. Thus, implmementations can mutatate the input object before storing it, but must ensure that mutation is reflected on the input object.

refactor(core): Strengthen contract of StorageServiceSupport.update
Now that StorageService.storeObject explicitly guarantees that the state of the object upon returning from the function relfects exactly what was stored, we can strengthen the contract of StorageServiceSupport.update.
In particular, we'll allow update to modify the supplied object (for example to add last modified data) but will require that the state of the input object at the end of update reflect exactly what was stored to the persistent store.
In order to help enforce this contract, we'll make update final so that implementations cannot override it in a way incompatible with this contract. There were a few implementations that did override update, but these all just did pre-update mutation/validation then called super.update. To handle these cases, expose a preUpdate function where implementations can specify this pre-update mutation/validation.

fix(storage): Short-circuit findById after update
Now that we have strengthened the contract of update, we can short-circuit places where we call update to store an object, then immediately call findById to get it back again. Given this strengthened contract, we are guaranteed that the object in the persistent store is identical to the object we just stored and can avoid an extra call to the persistent store.
This is particularly important for persistent stores that don't have strong read-after-write consistency (such as s3). In these cases, immediately fetching the the object we just wrote may actually return a prior version of the object (or a 404 if the object was just created). Returning the object we know we just wrote avoids this race condition between our call to fetch the object and the eventual consistency of the data store.

@ajordens @robzienert : I'd definitely like someone from Netflix to take a look at this to make sure that this change won't negatively affect the SQL storage implementation. As far as I can tell it won't but want someone who is more familiar with it to take a look.  Thanks!

If memory serves, the S3StorageService might be setting the last modified timestamp to some attribute of the s3 object metadata versus just trusting whatever was supplied.
I'll tag @srekapalli since he's been working with front50 most recently from our side. We're off S3 but worth confirming no impact to the SQL paths.

@ajordens : Good catch, we do indeed set the lastModified time of of the object to the s3 metadata time in fetchObject (and do the same for the GCS back-end).  (That's actually the root cause of the failing test here.)
This is tricky to solve, as the response from a PUT request to s3 doesn't include the Last-Modified header, so the only way to check what got written to the metadata is to make a subsequent HEAD or PUT request...which is exactly the request that is intermittently failing.
I wonder if the better answer here is just not returning the object at all from a create request and forcing consumers to fetch it after create if they need it (which I suspect most don't) and let those that do handle retries on a 404.

Going to close this for now; will re-open if I have time to implement a better solution for this that doesn't have the bug noted above.


No UserPass or Mailpass

I don't know why, but i don't have a UserPass or a MailPass. How do i get one of these?

Add them youself in the environment.ini file

Ik having the same problem on openbullet 2 and cannot find that folder

Okay never mind I found the file can someone please send there original file
So I don’t mess up any codings

hey, can you help me to do it plss


Stepped scaling support

For our application our main app requires 27 agents, but other pipelines only require 1 or 2. The only way we can make the stack responsive at the start of the day is to make the scaling policy +27 -27 scale out/in, but it's a waste of $ to do that for just a couple of scheduled jobs.
It'd be much better if we could use stepped scaling, and have it scale in/out in smaller increments

How could we make generic stack parameters to configure this though?

We scale based on the number of IdleAgents and ScheduledJobsCount in the Buildkite Cloudwatch metrics.
We configure step scaling and ScaleIn/ScaleOut by between 1 and 15 based on those values. Specifically, if ScheduledJobsCount > 1 for 60 seconds, spin up 1-15 instances based on the size of that queue. Likewise, if IdleAgents > 0 for 30 mins (6x 300 second intervals) start scaling in, again 1-15 at a time.
i.e.
"BuildkiteScalingScaleInPolicy": {       "Type": "AWS::AutoScaling::ScalingPolicy",       "Properties": {         "AdjustmentType": "ChangeInCapacity",         "AutoScalingGroupName": {           "Ref": "BuildkiteASG"         },         "PolicyType": "StepScaling",         "MetricAggregationType": "Average",         "EstimatedInstanceWarmup": "300",         "StepAdjustments": [           {             "ScalingAdjustment": -1,             "MetricIntervalLowerBound": 0,             "MetricIntervalUpperBound": 1           },           {             "ScalingAdjustment": -2,             "MetricIntervalLowerBound": 1,             "MetricIntervalUpperBound": 2           },           {             "ScalingAdjustment": -3,             "MetricIntervalLowerBound": 2,             "MetricIntervalUpperBound": 3           },           {             "ScalingAdjustment": -4,             "MetricIntervalLowerBound": 3,             "MetricIntervalUpperBound": 4           },           {             "ScalingAdjustment": -5,             "MetricIntervalLowerBound": 4,             "MetricIntervalUpperBound": 5           },           {             "ScalingAdjustment": -6,             "MetricIntervalLowerBound": 5,             "MetricIntervalUpperBound": 6           },           {             "ScalingAdjustment": -7,             "MetricIntervalLowerBound": 6,             "MetricIntervalUpperBound": 7           },           {             "ScalingAdjustment": -8,             "MetricIntervalLowerBound": 7,             "MetricIntervalUpperBound": 8           },           {             "ScalingAdjustment": -9,             "MetricIntervalLowerBound": 8,             "MetricIntervalUpperBound": 9           },           {             "ScalingAdjustment": -10,             "MetricIntervalLowerBound": 9,             "MetricIntervalUpperBound": 10           },           {             "ScalingAdjustment": -11,             "MetricIntervalLowerBound": 10,             "MetricIntervalUpperBound": 11           },           {             "ScalingAdjustment": -12,             "MetricIntervalLowerBound": 11,             "MetricIntervalUpperBound": 12           },           {             "ScalingAdjustment": -13,             "MetricIntervalLowerBound": 12,             "MetricIntervalUpperBound": 13           },           {             "ScalingAdjustment": -14,             "MetricIntervalLowerBound": 13,             "MetricIntervalUpperBound": 14           },           {             "ScalingAdjustment": -15,             "MetricIntervalLowerBound": 14           }         ]       }     },     "BuildkiteScalingScaleOutPolicy": {       "Type": "AWS::AutoScaling::ScalingPolicy",       "Properties": {         "AdjustmentType": "ChangeInCapacity",         "AutoScalingGroupName": {           "Ref": "BuildkiteASG"         },         "PolicyType": "StepScaling",         "MetricAggregationType": "Average",         "EstimatedInstanceWarmup": "60",         "StepAdjustments": [           {             "ScalingAdjustment": 1,             "MetricIntervalLowerBound": 1,             "MetricIntervalUpperBound": 2           },           {             "ScalingAdjustment": 2,             "MetricIntervalLowerBound": 2,             "MetricIntervalUpperBound": 3           },           {             "ScalingAdjustment": 3,             "MetricIntervalLowerBound": 3,             "MetricIntervalUpperBound": 4           },           {             "ScalingAdjustment": 4,             "MetricIntervalLowerBound": 4,             "MetricIntervalUpperBound": 5           },           {             "ScalingAdjustment": 5,             "MetricIntervalLowerBound": 5,             "MetricIntervalUpperBound": 6           },           {             "ScalingAdjustment": 6,             "MetricIntervalLowerBound": 6,             "MetricIntervalUpperBound": 7           },           {             "ScalingAdjustment": 7,             "MetricIntervalLowerBound": 7,             "MetricIntervalUpperBound": 8           },           {             "ScalingAdjustment": 8,             "MetricIntervalLowerBound": 8,             "MetricIntervalUpperBound": 9           },           {             "ScalingAdjustment": 9,             "MetricIntervalLowerBound": 9,             "MetricIntervalUpperBound": 10           },           {             "ScalingAdjustment": 10,             "MetricIntervalLowerBound": 10,             "MetricIntervalUpperBound": 11           },           {             "ScalingAdjustment": 11,             "MetricIntervalLowerBound": 11,             "MetricIntervalUpperBound": 12           },           {             "ScalingAdjustment": 12,             "MetricIntervalLowerBound": 12,             "MetricIntervalUpperBound": 13           },           {             "ScalingAdjustment": 13,             "MetricIntervalLowerBound": 13,             "MetricIntervalUpperBound": 14           },           {             "ScalingAdjustment": 14,             "MetricIntervalLowerBound": 14,             "MetricIntervalUpperBound": 15           },           {             "ScalingAdjustment": 15,             "MetricIntervalLowerBound": 15           }         ]       }     }
I'm not sure if you could make the stack completely generic, but maybe you could have some presets and use Fn::If to select between different scaling policies. i.e. have defaults to step scale by 1, 5, 10, or 20, and select them based on an Fn::If evaluated paramter?

Has something changed such that the scale up is slower? When I last looked it was scaling up to max agents in something close to 5 minutes.

Alternately, we could have a scheduled "start of day" scale up event.

I dunno how it'd even be possible to get to max agents in 5 minutes?
Say you want 50 agents max, with +10 -10 scale in/out.
It'd start with an alarm, then a scale in event, then a cool down, then another scale in event, and then a cool down… etc… 5 times. Say the cool down is 2 minutes to let the metrics catch up to the agents that have gone and accepted the work… that's 8 minutes just of cool down there.
Unless I'm going cray?
Stepped scaling means we could have rules for 1 -> 100, and almost in one hit add the number of instances we need depending on the scheduled job count.

We recently shifted to use the same logic that @npaufler mentioned above.
The tricky part is getting your InstanceWarmup value correct. If it's not accurate, you will scale your threshold amount more than once.
Which may be how some people get to their max agents in 5 minutes, if you are using SimpleScaling and you don't set your Cooldown value appropriately.


esp12

The pin's in the example are indicated in the example d2-3-4, but it doesn't work that way, I changed it to 4-0-2 (gpio) the example compiled but didn't work. Once I successfully assembled it for 4-5-13, but after the bulkhead, errors started again - I get "Time: Error: Could not read the time".
What am I doing wrong? Can pins be changed? What am I doing wrong? Can pins be changed?

@bamboo-master Thanks for your feedback. I've some questions:
Which version of the library are you using?

The pin's in the example are indicated in the example d2-3-4,

Which microcontroller are you using?

I changed it to 4-0-2 (gpio) the example compiled but didn't work.

Which example are you using? Did you make any changes?

Can pins be changed?

Yes, any digital pin can be used for AVR, ESP8266 and ESP32. I recommend to start with this example without modifications:
ErriezDS1302SetGetTime.ino

What am I doing wrong?

Another suggestion is to double check that the connected chip is a DS1302 and contains a 32kHz crystal oscillator.

[v2.0.0]
esp8266 as in the picture

ErriezDS1302Test example
changed only pin numbers
i have 32768Hz crystal oscillator.

The ESP8266 pins in the sketches are tested with a NodeMCU. There is a pin conversion needed from Dx to GPIOy when using a bare ESP8266. Can you convert to GPIO pins without D in the defines?
#elif defined(ARDUINO_ARCH_ESP8266)
// Swap D2 and D4 pins for the ESP8266, because pin D2 is high during a
// power-on / MCU reset / and flashing. This corrupts RTC registers.
#define DS1302_CLK_PIN      2 // GPIO2 NodeMCU: D4 Pin is high during power-on / reset / flashing
#define DS1302_IO_PIN       0 // GPIO0 NodeMCU: D3
#define DS1302_CE_PIN       4 // GPIO4 NodeMCU: D2

Yes I've done that before.

I tried to reproduce with:

LOLIN(WEMOS) D1 mini Lite ESP8266 mini lite (I could not find a bare ESP8266)
Default ErriezDS1302SetGetTime.ino
Arduino v1.8.19 IDE
ESP8266 Community v3.0.2
ErriezDS1302 master hash 0093bc7

Output:
Erriez DS1302 set get time example
12:00:00
12:00:01
12:00:02
12:00:03
...

Unfortunately, I could not reproduce it.

And you can check with pins ?
#define DS1302_CLK_PIN 13
#define DS1302_IO_PIN 14
#define DS1302_CE_PIN 15

That works.

Are pull-up resistors needed there? Could I have damaged the rtc?

The problem is not only with rtc, it also does not work with bmp180, some pins do not respond at all, once it was possible to start normally and then again "not found". Maybe the board is damaged or some other binding is needed, I will buy a NodeMCU and compare it.

Thanks for sharing. Using a NodeMCU is a good idea. Success!


DELIA-60700: OCDM process usage investigation

Reason for change: uses the CPU usage time allocation when PERF_SHOW_CPU is enabled.
Test Procedure: If PERF_SHOW_CPU is disabled, logs look the same. When PERF_SHOW_CPU is enabled, it will show the % and time usage of CPU for each node.
Risks: Low
Priority: P2
Signed-off-by: Mario Luzeiro<EMAIL_ADDRESS>

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Refactor Abstract Class

Pull Request Test Coverage Report for Build 132

128 of 186 (68.82%)  changed or added relevant lines in 14 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.6%) to 88.254%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mgcpy/independence_tests/abstract_class.py
11
12
91.67%

mgcpy/independence_tests/dcorr.py
33
34
97.06%

mgcpy/benchmarks/power.py
4
8
50.0%

mgcpy/independence_tests/rv_corr.py
12
19
63.16%

mgcpy/independence_tests/hhg.py
0
20
0.0%

mgcpy/independence_tests/kendall_spearman.py
0
25
0.0%

Files with Coverage Reduction
New Missed Lines
%

mgcpy/independence_tests/kendall_spearman.py
1
0.0%

Totals

Change from base Build 122:
0.6%

Covered Lines:
819

Relevant Lines:
928

💛  - Coveralls


update: intel-microcode

Name: intel-microcode
CVEs: CVE-2024-23984, CVE-2024-24968
CVSSs: 6.8, 5.6
Action Needed: update to >= 20240910
Summary:

CVE-2024-23984: Observable discrepancy in RAPL interface for some Intel(R) Processors may allow a privileged user to potentially enable information disclosure via local access.

https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01103.html

CVE-2024-24968: Improper finite state machines (FSMs) in hardware logic in some Intel(R) Processors may allow an privileged user to potentially enable a denial of service via local access.

https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01097.html

refmap.gentoo: TBD

Done in https://github.com/flatcar/scripts/pull/2364.


[python] Check for downgraded categorical write [WIP]

Issue and/or context: #1739
Changes:
Notes for Reviewer:
This PR is not ready for review. Please do not review it.

Codecov Report
All modified lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
see 109 files with indirect coverage changes
:loudspeaker: Thoughts on this report? Let us know!.

@nguyenv ready for round two!


Add missing singleton deployments

Closes #205
Closes #206
Closes #208
Closes #212
Closes #213
Closes #214
Closes #216
Closes #218
Closes #219
Closes #220
Closes #221
Closes #222
Closes #223
Closes #224
Closes #232

with artifacts/10243/deployment.json it will close #232

Thanks for adding Scroll Sepolia artifact here!
Would it be possible to merge and publish a new npm package in the next week? We're hoping to get Safe Core contracts deployed to promote in the next ETHGlobal hackathon on Oct 6th 🤞

I will mentor an hackathon in Madrid from October 7th to 8th so if we could get the updated npm package released to be able to deploy the contracts from this singleton it would help to get hackers try it.
While waiting for that, I will try a custom deployment to see if I can make it work first.
Thanks for your support.

Hi @bertux , I think the package that you need deployed is https://github.com/safe-global/safe-deployments and not this one

Hi @bertux , I think the package that you need deployed is https://github.com/safe-global/safe-deployments and not this one

Hello, I found later the problem was the naming of the package because it was still using the old naming with old versions and not the new one with the new versions. After updating the naming it found the new version without problem.


Make ERC-20 portals reject failed transfers again

📚 Context
The job of the ERC-20 portal is to manage ERC-20 token deposits to the DApp. It does so by calling the transferFrom function on the token contract and adding an input in the DApp's input box. This function returns a boolean value which signals if the transfer was successful or not.
Prior to 0.9.0, the ERC-20 portal required this boolean value to be true, which means that the DApp would only be notified of an ERC-20 if it were successful.
On 0.9.0, we decided to accept transfers in which the transferFrom function returned false, and added this information in the input itself. The rationale was that EIP-20 did not specify clearly the semantics of this value, and we would like the DApp back-end to handle this information however they want.
On October 25th, however, @gligneul pointed out that this behavior could open the possibility for DApp developers to mistakenly accept failed transfers, should they not check this boolean value within the input. @ZzzzHui, @diegonehab and I agreed.
✔ Solution
Make the depositERC20Tokens function revert if transferFrom returns false. Additionally, we may remove the success field from the ERC-20 deposit input, to avoid confusion.

This has been fixed by #117

We should keep the true return value in the input to preserve backwards compatibility.

This issue has been addressed by #117
@gligneul We'll remove the success field on the next major release (tracked by  #132)


depthWrite with add type alpha

If you have an additive type material (blendtype: 1) then it will never write to the depth buffer, even if depthWrite: true.
Why would you want to? In my case I have a HUD that overlays on the scene. I sample the depth map to ensure a post effect does not overlay the HUD. If the HUD objects use additive type alpha, then the depth map does not know the difference between the HUD and the background.

Do you mean the readable depth buffer texture? Or a general zbuffer? How do you sample it exactly?

I use a screen filter and sample the texture. You can see the filter here:
http://www.6dof.space/Inferno0.0.2/Scripts/filter.js

Ah yes, I see. So we simply omit any blended draw calls for this depth map right now: https://github.com/playcanvas/engine/blob/master/src/scene/forward-renderer.js#L1904
I wonder what the best solution API-wise would be.

Autoset drawToDepth when changing meshInstance material and allow further changes to it? Bad, because you can change the material itself, and meshInstance won't be notified.
Just draw everything only based on drawToDepth? Bad, because there will be huge opaque surfaces at wrong places.
add some kind of additional meshInstance flag, like forceDrawToDepth?

@willeastcott @daredevildave  @Maksims ?

Another way is just to make the posteffect system more flexible, so you can simply draw the HUD after the posteffect, what would be the proper options actually.

Yeah, it's tricky to handle depth map's with blended calls. I don't think there is any perfect solution
Rather than extending the posteffect system to allow the HUD to be drawn afterwards, I would prefer the ability to run multiple scenes at the same time, and the postFX to be applied on a per-scene basis.
This makes sense because the playcanvas interface already has methods of putting objects into scenes, so no UI development is required.

I'll close this ticket as suggested solution 'draw the HUD after the posteffect, what would be the proper options actually.' is already possible.
Please reopen if further work is needed.


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 1029 ms

Resolved: Bofrost.lu performance has improved in 0bf4a42 after 13 minutes.


trackswitch does not support Chrome 70

Chrome 66 was released a few days ago and trackswitch falls to the victim from the recent changes of Chromes new user interaction model:
The AudioContext was not allowed to start. It must be resume (or created)
after a user gesture on the page. https://goo.gl/7K7WLu

That means trackswitch doesn't play audio on Chrome 66 at all, so this would need to be addressed asap.

I don't know what exactly has changed in Chrome but it works fine now in 66.0.3359.139
Maybe someone else can try it on Linux/Windows?

not working at all in Version 66.0.3359.170. @nils-werner @stefan-balke can you confirm this?

Yes, I can confirm that.

Have you tried exchanging
https://github.com/audiolabs/trackswitch.js/blob/master/js/trackswitch.js#L637
with .resume()?

Still works for me on Chrome 66.0.3359.170 and macOS High Sierra.

Please completely shut down the browser (cmd + Q) and try again.

Now I tried another site and it does not work. So it seems to be configuration dependent...

I have a solution, will make a PR.

Note: The Web Audio API will be included in the Chrome autoplay policy with M70 (October 2018).

this will break trackswitch again.

Okay, gonna finish #3 then soonish.

@stefan-balke seems like Google is scared:

The Web Audio API will be included in the Chrome autoplay policy with M71 (December 2018).

so lets fix this before christmas

trackswitch now stopped working on chrome. I would propose to add a warning in the readme until this is fixed

Still running or again. Can't recall the details though.


Full contract metadata support - Off chain events and errors

Basic Contract Metadata:
Key-value pairs of scalar values
Full Contract Metadata:
Includes basic contract metadata
Adds:
Off-chain views
Off-chain errors

[ ] - [ ] Offchain events

[ ] Author
[ ] Read, run

[ ] Offchain Errors

[ ] Generate typescript errors from contract failwith and map them to the errors in the contract metadata

Type of Metadata to be included:

Project-wide metadata

[ ] Generate Metadata

[ ] Validate Metadata (TZComet)

[ ] Publish Metadata

[ ] Internal storage of contract
[ ] IPFS (focus)
[ ] HTTP endpoint

Support all reserved fields:

https://tzip.tezosagora.org/proposal/tzip-16/

When do we generate the contract metadata?

At compile
At originate
Consider DSLs supporting metadata support


enh(parser) Detect comments based on english like text, rather than specific list of keywords

Resolves #2827.

Changes
Before we boosted comments relevance by:
begin: /\b(a|an|the|are|I'm|isn't|don't|doesn't|won't|but|just|should|pretty|simply|enough|gonna|going|wtf|so|such|will|you|your|they|like|more)\b/

Now we look for "english like phrases" instead:
begin: /[ ]+(([A-Za-z'-]{3,}|is|a|I|so|us|[tT][oO]|at|if|in|it|on)[.]?[:]?([.][ ]|[ ]|\))){3}/

Checklist

[x] Added markup tests, or they don't apply here because...
[x] Updated the changelog at CHANGES.md

Now we look for "english like phrases" instead:
begin: /[ ]+(([A-Za-z'-]{3,}|is|a|I|so|us|[tT][oO]|at|if|in|it|on)[.]?[:]?([.][ ]|[ ]|\))){3}/

How did you come up with this regex?

See #2827.  Testing with a big lump of comments.  It's just attempting to match 3 english looking words in a row...


Logging in with email does not load any networks

When i try to setup the integration in HAOS on rpi4, after login i do not get any networks available to add to my instance. I confirm that i see the network when i login hsing the same method on the eero app.

Any chance you're using the sign-in-with-Amazon method for the app? If so, this integration doesn't support it.
Otherwise, can you turn on response saving via Options and share your (redacted) logs and responses? You can email or find me on Discord (same username as GitHub) if you'd rather not post publicly.

Hi Matt, thanks for your reply. Im 100% sure that i am logging in using a non-amazon account.
The first error in the log is:
This error originated from a custom integration.
Logger: custom_components.eero.config_flow
Source: custom_components/eero/config_flow.py:72
Integration: eero (documentation, issues)
First occurred: 23:39:54 (1 occurrences)
Last logged: 23:39:54
Status: 401, Error Message: error.login.unknown
Then this is followed by:
This error originated from a custom integration.
Logger: aiohttp.server
Source: custom_components/eero/config_flow.py:75
Integration: eero (documentation, issues)
First occurred: 23:39:54 (1 occurrences)
Last logged: 23:39:54
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
resp = await request_handler(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_app.py", line 504, in _handle
resp = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_middlewares.py", line 117, in impl
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 85, in security_filter_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 148, in handle
result = await handler(request, **request.match_info)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 181, in post
return await super().post(request, flow_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 72, in wrapper
result = await method(view, request, data, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 110, in post
result = await self._flow_mgr.async_configure(flow_id, data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 271, in async_configure
result = await self._async_handle_step(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 367, in _async_handle_step
result: FlowResult = await getattr(flow, method)(user_input)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/eero/config_flow.py", line 75, in async_step_user
self.user_input[CONF_USER_TOKEN] = self.response["user_token"]
~~~~~~~~~~~~~^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not subscriptable

Thanks for the detail.
The error message Status: 401, Error Message: error.login.unknown is showing the login you entered is unknown.
Are you using the same credentials (either email or phone number) to login as the app? If using a phone number, make sure you're entering the country code first.

Yes i am sure that i am entering the correct credentials

@nzneil22 Are you still having this problem? Any updates?

Hi, i will try again later today. Just noticed there is a new version
1.3.1, i will update and retry.
Thanks
On Fri, 30 Jun 2023, 12:39 Matt Schmitt, @.***> wrote:

@nzneil22 https://github.com/nzneil22 Are you still having this
problem? Any updates?
—
Reply to this email directly, view it on GitHub
https://github.com/schmittx/home-assistant-eero/issues/57#issuecomment-1614470158,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVFXQ62BEEBNYTWX3KB745TXN2UERANCNFSM6AAAAAAZCPTGW4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Seems that i am now getting this error:
This error originated from a custom integration.
Logger: custom_components.eero
Source: helpers/update_coordinator.py:262
Integration: eero (documentation, issues)
First occurred: June 30, 2023 at 13:50:28 (1 occurrences)
Last logged: June 30, 2023 at 13:50:28
Timeout fetching Eero (Neil Borg) data
On Fri, 30 Jun 2023, 12:45 Neil Borg, @.***> wrote:

Hi, i will try again later today. Just noticed there is a new version
1.3.1, i will update and retry.
Thanks
On Fri, 30 Jun 2023, 12:39 Matt Schmitt, @.***> wrote:

@nzneil22 https://github.com/nzneil22 Are you still having this
problem? Any updates?
—
Reply to this email directly, view it on GitHub
https://github.com/schmittx/home-assistant-eero/issues/57#issuecomment-1614470158,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVFXQ62BEEBNYTWX3KB745TXN2UERANCNFSM6AAAAAAZCPTGW4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Are you still getting the same Status: 401, Error Message: error.login.unknown error as before?

No the error now is:

OK, it clearly seems to be something with your login and verification methods. This integration only support the basic sign-in via Eero credentials, and it seems to be working for well for others, so there's gotta be something unique about your situation. That being said, some things to try or confirm:

Re-confirm you don't use seem weird sign-in method for Eero (Amazon, ISP credentials, etc.).
Re-confirm you're including a country code if using a mobile phone number to sign-in.
If you're truly stuck, try creating another Eero account to use for this integration. Then add that account as an admin for your existing network.

Hi i have tried all of the steps you mentioned, but it still does not show any network. I will try downgrading the version of the component maybe that helps. This used to work before
Thanks

Downgrading to version 1.3.0 did not fix the issue. I have no errors in the log

I just released 1.4.1 which adds more debug level logging to help diagnose this. Please update and try a fresh install of the integration, then share your results.

I now get this error:
This error originated from a custom integration.
Logger: custom_components.eero.api
Source: custom_components/eero/api/init.py:187
Integration: eero (documentation, issues)
First occurred: 22:31:30 (2 occurrences)
Last logged: 22:31:45
Exception raised, status code: 403, text: {'meta': {'code': 403, 'server_time': '2023-07-10T20:31:30.162Z', 'error': 'error.network.premium.not.capable'}}
Exception raised, status code: 403, text: {'meta': {'code': 403, 'server_time': '2023-07-10T20:31:45.607Z', 'error': 'error.network.premium.not.capable'}}
Also i am getting this screen now after the login.

Exception raised, status code: 403, text: {'meta': {'code': 403, 'server_time': '2023-07-10T20:31:30.162Z', 'error': 'error.network.premium.not.capable'}}
Exception raised, status code: 403, text: {'meta': {'code': 403, 'server_time': '2023-07-10T20:31:45.607Z', 'error': 'error.network.premium.not.capable'}}

This is progress at least, it's clearly letting you login and verify. This concern looks like a problem with verifying Eero Plus status.
Are you able to enable response logging and share the _2_2_networks_xxxxxxx.json file with me? I recommend you add me on Discord (same username, @schmittx) so we can chat directly and avoid posting your responses publicly.
The screenshot you shared is the advanced options screen. Previously only available if you selected Configure within Home Assistant after setting up the integration. For 1.4.1, I added it to the end of the flow for initial setup as well. Looks like to need to hard refresh your browser so the frontend refreshes and shows the text.

I am getting the same error, error.network.premium.not.capable, on version 1.4.2. Where can i find the response logging to help with troubleshooting?

I am getting the same problem, no networks show when I am configuring the integration. I do not log on with amazon credentials

Same here, the issue still persists

I also cannot log in at all with email and I don't get the code when I enter in my phone number (US:<PHONE_NUMBER>2).

I’m getting the same issue and logs as nzneil did on Jun 12. It’s a fresh install. I’m using email.
Logger: aiohttp.server
Source: /usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py:403
First occurred: 9:11:51 PM (2 occurrences)
Last logged: 9:14:36 PM
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
resp = await request_handler(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_app.py", line 504, in _handle
resp = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_middlewares.py", line 117, in impl
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 85, in security_filter_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 31, in headers_middleware
response = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 148, in handle
result = await handler(request, **request.match_info)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 63, in with_admin
return await func(self, request, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 177, in post
return await super().post(request, flow_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 72, in wrapper
result = await method(view, request, data, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 110, in post
result = await self._flow_mgr.async_configure(flow_id, data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 293, in async_configure
result = await self._async_handle_step(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 394, in _async_handle_step
result: FlowResult = await getattr(flow, method)(user_input)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/eero/config_flow.py", line 77, in async_step_user
self.user_input[CONF_USER_TOKEN] = self.response["user_token"]
~~~~~~~~~~~~~^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not subscriptable

Never mind - I forgot I had converted to an Amazon account.

Hi @schmittx Im getting same problem as nzneil22. Was there a resolution i can try?

Has anyone resolved this?

I published a beta release with multiple bug fixes, give a try and let me know if it helps.

Hi schmittx, the beta worked for me :) thanks

beta worked for me thanks

Closing this as the beta updates have been reflected into newest release here.


z-nomp don't sending funds from taddr to zaddr

Don't know where I should fix that issue:
[votecoin] sendmany "" {"t1XmGD............................................................":124.45000362}
[votecoin] Error sending payments {"code":-6,"message":"Insufficient funds, coinbase funds can only be spent after they have been sent to a zaddr"}
Any guesses?

resolve it by my self...

Dear flexmankz,
could you explain how did you fix it?
May be I have the same issue.
Thanks


Create Sreekant_Shenoy.html

Your pull request needs further work because of the following reason(s):

You have modified BSoD/Sreekant_Shenoy.html, You can only modify BSoD/geekykant.html

Once you have resolved the issues, comment on this request to be re-judged
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

c9eba6a13c0f78fc34307e98d76f50b9df968a2a

This PR has been idle for more than 24 hours, and will now be closed. Feel free to re-open.
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

c9eba6a13c0f78fc34307e98d76f50b9df968a2a