Harmonize swapfile creation and add checks

Further changes to harmonize the two per-boot scripts and make it easier to change the location of the ephemeral disk. Also added check to not create swapfile if it already exists.

#sign-off


Cannot read property 'on' of undefined

I have some weird issue that sometimes occurred when I try to run printText()with https://github.com/alepee/node-printer/blob/master/printer.js at line 303
lpq.stdout.on('data', function(data) {}
that sometimes give me an error TypeError: Cannot read property 'on' of undefined and shuts the node server down. My attempt to localize the problem with try{}catch() doesn't work either, it just throws another error
Error: spawn lpq EMFILE     at exports._errnoException (util.js:856:11)     at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)     at onErrorNT (internal/child_process.js:344:16)     at nextTickCallbackWith2Args (node.js:474:9)     at process._tickCallback (node.js:388:17)
It seems that you have problem with node-process or something.

It may comes from spawn module.
As specified in node documentation child_process.spawn returns an object with a stdout method. This is a core module, maybe you could check your nodejs version. This module has been added in v0.1.90


fif: Fix missing fzf option --preview-window

Signed-off-by: Gerard Bosch<EMAIL_ADDRESS>License Acceptance

[x] This repository is Apache version 2.0 licensed (some scripts may have alternate licensing inline in their code) and by making this PR, I am contributing my changes to the repository under the terms of the Apache 2 license.

I fixed the Markdown linter complain that made the pipeline to fail in #59 :)

I think people might get annoyed if we stuff in an editorconfig and their editor changes theri settings out from under them. Let's discuss that in a separate issue so we can merge the other changes.
Thanks!

Sure, no problem! I will remove the .editorconfig then. I just thought it would be good to keep the consistency across the scripts as they will potentially be added and modified by different people with different settings for indentation for example. What usually leads to very inconsistent mixture of tabs, spaces and stuff in the same project and even same file.

Thanks for the contribution!


Fabric Roadmap

From fabric website, stated that Fabric Dashboard can be access until mid 2019.  So if that happen, still we can use fabric plugin for Crashlytics on firebase?

Yes. We have setup Crashlytics on Firebase and it is working well. My understanding is that eventually the Fabric Dashboard will go away, but at that point, you should be migrated to Firebase and be viewing your crash data over there instead. Follow the migration instructions and you will be fine.


Auto manage data and document; CI with travis and appveyor

This isn't quite done yet but I'm going to pull it in anyway before doing the submodule thing


Insertion of time:TimeOfDay with zone offset does not work as expected.

Description:
Insertion of time:TimeOfDay with utcOffset defined inserts incorrect values.
Steps to reproduce:
int rowId = 8;
time:TimeOfDay timeWithTimezoneRecord = {
    utcOffset: {hours: -8, minutes: 0},
    "timeAbbrev": "-08:00",
    hour: 16,
    minute: 33,
    second: 55
};

ParameterizedQuery sqlQuery = `
    INSERT INTO DateTimeTypes (row_id, time_tz_type)
    VALUES(${rowId}, ${timeWithTimezoneRecord})
`;
validateResult(check executeQueryMockClient(sqlQuery), 1);

The above code would be expected to insert 16:33:55-08:00. However 08:33:55-08:00.
Seems the time is converted to UTC without dropping the zone offset.

Related issue: https://github.com/ballerina-platform/ballerina-standard-library/issues/10

Issue is due to H2 database not support TIME WITH TIMEZONE.


Feature/transects quadrats as samples

Add

sosa:isSampleOf a transitive property
ManagedFeature class

Remove

tern:siteType
references to the Site for Sampling and Observation
duplicate properties in subclasses (I have a handy python script for this)
file tern.shacl.shapes.shapes.ttl - no longer needed as the main ontology tern.ttl now defines SHACL constraints

@dr-shorthair I just want to clarify how the ManagedFeature class is intended to be used.
Any feature-of-interest can be an instance of Sample with ManagedFeature as a mixin class.

Plot_1 and Subplot_1 are instances of Sample as well as instances of the ManagedFeature class. Therefore, they must record the commissioned date and optionally record the decommissioned date.
Is this how you imagine using this ManagedFeature class? Thanks.

Is this how you imagine using this ManagedFeature class?

Yep. You got it.

Did you see my comment about cardinality of tern:featureType property. It is plausible that a sample (or another feature) might be classified with more than one feature-type.
However, I know unlimited cardinality is difficult for a database.

Yes I did see your comment on the cardinality of tern:featureType. I have some thoughts below.
I agree in some cases there may be multiple feature types. However, most of the time the multiple feature types are either a narrower or broader relationship to the single explicit feature type declared in the data. From a data exchange perspective, it makes it a bit simpler to have only one feature type. And when required, generate the additional feature types from the broader relationships defined in the concept scheme. This means our current set of constraints may only be suitable for data exchange and it may be appropriate to have a different set of constraints like having min 1 instead of exactly 1 for a data integration system.
Another perspective from an application level (our EcoPlots web app), it may be problematic to show multiple feature types in a table-based data structure. See below where we show the feature type of an observation's feature of interest.

These are some of the thoughts I had.

Good analysis. I agree that most often multiple types could have relationships in the vocab hierarchy. And I suspected there would be a other side-effects, which was why I only made it a comment.
Leave it as 1 for the moment, and only consider changing, or a work-around, if a real need appears in the data.


userHasRatedCurrentVersion private

Hey there !
In my App I display a rate button, I want to hide that button if the user already rated the actual version of the app. Looking around I found this func userHasRatedCurrentVersion which will work great but turns out it's private and there is no public access in the actual API to perform such validation.
Maybe I'm missing some another way to do this?
Thanks!

For interface elements within your app, it may be better to track the state within your app, not Armchair. To do this, setup a onDidOptToRate closure, then set a boolean you can save for your state.
Armchair.onDidOptToRate(didOptToRateClosure: ArmchairClosure?)

That might work ok, but makes the client to add much more boilerplate to keep track of versions.
Why userHasRatedCurrentVersion has to be private? is just a getter, a read only property 🤔

Most people have no reason to read this value. This is the first time ever requested, so I am reluctant to make it public.
You can also do it by checking the Armchair.userDefaultsObject() by reading the key for  Armchair.keyForArmchairKeyType(ArmchairKey.RatedCurrentVersion)

Ok I get it..
I will try using Armchair.userDefaultsObject(), looks like I will be able to achieve the same result.
Thanks for your help, really appreciated.


Delegate to hse-util package

The only objectionable bit in this PR (mostly) is the addition of an orphan Default instance for SrcSpanInfo in HSE.Util; the alternative would be to newtype it.

The Appveyor failure is because HSE-util isn't yet in nightly - that's not an issue. The Travis failure is because it won't build in GHC 7.8 or below, because of a missing import Data.Monoid - see https://travis-ci.org/ndmitchell/hlint/jobs/268372812. Any thoughts about making this work further back? I'm not too fussed, but following the same GHC version tolerance as HSE itself seems like a reasonable default.

I see no inconvenient with adding the missing module import and making HSE-util more backward compatible. Let’s see how it goes after I upload a new version of HSE-util and amend this PR.

On 25 Aug 2017, at 21:37, Neil Mitchell<EMAIL_ADDRESS>wrote:
The Appveyor failure is because HSE-util isn't yet in nightly - that's not an issue. The Travis failure is because it won't build in GHC 7.8 or below, because of a missing import Data.Monoid - see https://travis-ci.org/ndmitchell/hlint/jobs/268372812 https://travis-ci.org/ndmitchell/hlint/jobs/268372812. Any thoughts about making this work further back? I'm not too fussed, but following the same GHC version tolerance as HSE itself seems like a reasonable default.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/ndmitchell/hlint/pull/381#issuecomment-325016906, or mute the thread https://github.com/notifications/unsubscribe-auth/AABoAoLce1GqgLZb3xVuEyy3EdYXCDbtks5sbyJ2gaJpZM4PCrjp.

As a tip, if you have unused import warnings, you should do import Data.Monoid first then import Prelude after. That way you are free of import warnings across all compilers - it's what I do in HLint.

Done. I've pushed a new version of HSE-util with the orphan instance and the missing import. It will be in Stackage nightly soon as well, as my PR to build-constraints was merged this morning.

Seems like unknown flag in  {-# OPTIONS_GHC #-} pragma: -Wno-orphans happens with GHC 7.10 and below.

I imagine -fno-orphans or similar would be compatible further back.

Thanks!


Morse decoder

In this Milestone we @JonahKayizzi  and @Miliyonayalew

Run a program using the command line.
Used Ruby syntax for basic programming operations.
Used Ruby to solve basic coding challenges.
Create a method called decode_char  to decode a Morse code character, take a string parameter, and return the corresponding character in uppercase
Create a method called decode_word  to decode an entire word in Morse code, take a string parameter, and return the string representation.
Create a method called decode_message  to decode the entire message in Morse code, take a string parameter, and return the string representation.
Fixed linters and followed Ruby's best practices.

Hi @Omar-Muhamad  Thanks for the review, Happy Coding :smile:


Debian: mp4v2 obsolete

mp4v2 was removed from Debian and Ubuntu as it seems.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921127

Interesting, not sure what the impact will be long term of this. It would appear that this would remove the ability to capture cover art as part of the conversion.

The Debian bug says "better alternatives exist".
Indeed, mp4v2 is unavailable on the current Ubuntu LTS and m4b is created without cover art.


Responsive banner2

Add _includes/navbar-lower-menu.html to recover banner/nav responsive behavior. Also (re)-fix two minor yml errors.

@nathanweeks - I have added you for this PR review because I am puzzled by the reported conflict for _includes/navbar-lower-menu.html.
It looks to me like that file is absent from "main", so there shouldn't be a conflict(?)
I suspect this means that I am not understanding the relation to the theme. Is this navbar-lower-menu.html now not local to jekyll-soybase?

@nathanweeks - I have added you for this PR review because I am puzzled by the reported conflict for _includes/navbar-lower-menu.html. It looks to me like that file is absent from "main", so there shouldn't be a conflict(?) I suspect this means that I am not understanding the relation to the theme. Is this navbar-lower-menu.html now not local to jekyll-soybase?

I'd guess responsive-banner2 wasn't branched off of main (or was branched from an older commit of main, before _includes/navbar-lower-menu.html was removed)? Otherwise, it would show the addition of a new file _includes/navbar-lower-menu.html, instead of a one-line whitespace change (plus a couple other misc. whitespace differences in other files). If that's the case, one possible solution is to copy the _includes/navbar-lower-menu.html from your (local) responsive-banner2 branch to somewhere outside the repo, rename your local responsive-banner2 branch (e.g., responsive-banner2.bak), switch to main, git pull origin main to update your local main, git branch responsive-banner2 to create a new responsive-banner2, copy & git-add the _includes/navbar-lower-menu.html into that branch, commit, and force-push to the remote responsive-banner2.

Thanks for the instructions, @nathanweeks. Your suggestion seemed to work. Ready for review now.


Error when importing

I have included angel_diagnostics in my pubspec.yaml file like so: angel_diagnostics: ^1.0.2.
However when I attempt to import 'package:angel_diagnostics/angel_diagnostics.dart'; in my dart file, I get the following error:
Unable to spawn isolate: 'package:angel_diagnostics/src/log_requests.dart': malformed type: line 12 pos 30: cannot resolve class 'AngelPlugin' from '_RequestLogger@39222342'
class _RequestLogger extends AngelPlugin {

Would someone be able to help me understand what the issue is please?

package:angel_diagnostics is completely deprecated as of Angel >=1.1.0-alpha.
Check out the migration guide for any further concerns:
https://angel-dart.gitbook.io/angel/1.1.0-migration-guide
I'm going to go ahead and mark this repo as deprecated; thanks for bringing it to my attention.


Multiple account/wallet support

Description
It seems multiple wallet support was dropped recently.  I used to be able to add several wallets, but now I can only add or create one wallet to a new installation.  Previously added or created wallets remain.
I found tickets related to this from the old repo, that I had to dig very hard:

Handling multiple wallets
(EPIC) Multi-wallet support
UI: Multi-account

These above are links to archive.today caches of Yandex caches of the deleted issues from the old repo.  That's how hard I had to dig this information.

it was never dropped, and is still there and working nominally

I see.  So I need to unlock a wallet before I can add another wallet.
Why?
This is a UX problem.  It isn't obvious at all.

It seems this is the case. I cannot speak for the dev that wrote the code in any version before v1.20.0
Well it's more of a problem to the user if they can't unlock a wallet before adding another.


Overnight test is failing: freedesktop-sdk being used need to be updated to support buildstream master

See original issue on GitLab
In GitLab by [Gitlab user @jjardon] on Jun 2, 2020, 11:43
Job #576177727 failed for 32a531747c45fb96df64da6c7e3514cedeaaf53a:
Update: We've now merged https://gitlab.com/BuildStream/buildstream/-/merge_requests/1987, and expect the overnight tests to start passing. If the overnight job(s) pass on the next schedule, this issue ought to be closed.

In GitLab by [Gitlab user @jjardon] on Jun 2, 2020, 11:44
changed title from Overnigth test is failing: to Overnigth test is failing:{+ freedesktop-sdk being used need to be updated to support buildstream master+}

In GitLab by [Gitlab user @jjardon] on Jun 2, 2020, 11:44
changed title from Overnigth test is failing: to Overnigth test is failing:{+ freedesktop-sdk being used need to be updated to support buildstream master+}

In GitLab by [Gitlab user @traveltissues] on Jun 2, 2020, 14:33
assigned to [Gitlab user @traveltissues]

In GitLab by [Gitlab user @traveltissues] on Jun 2, 2020, 14:33
assigned to [Gitlab user @traveltissues]

In GitLab by [Gitlab user @traveltissues] on Jun 2, 2020, 14:41
mentioned in merge request !1953

In GitLab by [Gitlab user @traveltissues] on Jun 2, 2020, 14:41
mentioned in merge request !1953

In GitLab by [Gitlab user @traveltissues] on Jun 2, 2020, 16:15
the expected target valentindavid/bst2 will need some work (eg. pip is now in bst-plugins-experimental). Some plugins will need to be ported to use the new vdir api also
i'm updating on top of this branch on a fork currently

In GitLab by [Gitlab user @traveltissues] on Jun 2, 2020, 16:15
the expected target valentindavid/bst2 will need some work (eg. pip is now in bst-plugins-experimental). Some plugins will need to be ported to use the new vdir api also
i'm updating on top of this branch on a fork currently

In GitLab by [Gitlab user @traveltissues] on Jun 3, 2020, 11:06
assigned to [Gitlab user @willsalmon]

In GitLab by [Gitlab user @traveltissues] on Jun 3, 2020, 11:06
assigned to [Gitlab user @willsalmon]

In GitLab by [Gitlab user @traveltissues] on Jun 4, 2020, 08:26
[Gitlab user @willsalmon] has been working on modifications to valentindavid/bst2 that will fix more of the branch against bst master.

In GitLab by [Gitlab user @traveltissues] on Jun 4, 2020, 08:26
[Gitlab user @willsalmon] has been working on modifications to valentindavid/bst2 that will fix more of the branch against bst master.

In GitLab by [Gitlab user @jjardon] on Jun 9, 2020, 23:54
[Gitlab user @willsalmon] [Gitlab user @traveltissues] any further progress on this?

In GitLab by [Gitlab user @jjardon] on Jun 9, 2020, 23:54
[Gitlab user @willsalmon] [Gitlab user @traveltissues] any further progress on this?

In GitLab by [Gitlab user @willsalmon] on Jun 10, 2020, 09:03
Umm, I have got FD building a lot further it now gets as far as elements that have plugins that need converting to bst-master (all the plugins can be configured but some still have not been converted to 'virtual'/'cas based' diretories)
I am waiting for buildbox to release a new tag so that i can merge what my work needs to the master branch of FD-docker-images.
This dose not block fixing the plugins but i have been waiting for the new tag. This should be done some time this week but [Gitlab user @juergbi] is just trying to get a few more bits merged but like i say this is not a hard blocker on working on the plugins.
Please see, https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/jobs/580051634 for details.

In GitLab by [Gitlab user @willsalmon] on Jun 10, 2020, 09:03
Umm, I have got FD building a lot further it now gets as far as elements that have plugins that need converting to bst-master (all the plugins can be configured but some still have not been converted to 'virtual'/'cas based' diretories)
I am waiting for buildbox to release a new tag so that i can merge what my work needs to the master branch of FD-docker-images.
This dose not block fixing the plugins but i have been waiting for the new tag. This should be done some time this week but [Gitlab user @juergbi] is just trying to get a few more bits merged but like i say this is not a hard blocker on working on the plugins.
Please see, https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/jobs/580051634 for details.

In GitLab by [Gitlab user @traveltissues] on Jun 11, 2020, 11:09
plugins are tracked at https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/issues/990

In GitLab by [Gitlab user @traveltissues] on Jun 11, 2020, 11:09
plugins are tracked at https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/issues/990

In GitLab by [Gitlab user @jjardon] on Jun 19, 2020, 06:15
[Gitlab user @willsalmon] [Gitlab user @traveltissues] I think a new tag has been released; is anything blocking this? Does a WIP MR exist somewhere?

In GitLab by [Gitlab user @jjardon] on Jun 19, 2020, 06:15
[Gitlab user @willsalmon] [Gitlab user @traveltissues] I think a new tag has been released; is anything blocking this? Does a WIP MR exist somewhere?

 I believe [Gitlab user @DouglasWinship] is working on this?

 I believe [Gitlab user @DouglasWinship] is working on this?

In GitLab by [Gitlab user @traveltissues] on Jun 19, 2020, 08:36
I've had a look at the plugins in question though and i think for most of these it should be a drop in replacement of api

In GitLab by [Gitlab user @traveltissues] on Jun 19, 2020, 08:36
I've had a look at the plugins in question though and i think for most of these it should be a drop in replacement of api

In GitLab by [Gitlab user @willsalmon] on Jun 19, 2020, 08:47
I think there have been some issues caused by what bst can accept as unique keys now, as well. But most of the work should be changing the way the plugins access the sandbox directory. Which in theory should be fairly straight forward. finggers crossed

In GitLab by [Gitlab user @willsalmon] on Jun 19, 2020, 08:47
I think there have been some issues caused by what bst can accept as unique keys now, as well. But most of the work should be changing the way the plugins access the sandbox directory. Which in theory should be fairly straight forward. finggers crossed

In GitLab by [Gitlab user @DouglasWinship] on Jun 19, 2020, 14:33
Can confirm, have been working through these. I've done 4/5.
Updating them to the new API has been fairly straightforward.
Figuring out the new API, when I wasn't even familiar with the old API, has been a lot less straightforward. But I got there.

In GitLab by [Gitlab user @DouglasWinship] on Jun 19, 2020, 14:33
Can confirm, have been working through these. I've done 4/5.
Updating them to the new API has been fairly straightforward.
Figuring out the new API, when I wasn't even familiar with the old API, has been a lot less straightforward. But I got there.

In GitLab by [Gitlab user @jjardon] on Jun 28, 2020, 22:34
[Gitlab user @willsalmon] [Gitlab user @DouglasWinship] nice, can you please create a WIP: Merge Request with what you have at the moment?

In GitLab by [Gitlab user @jjardon] on Jun 28, 2020, 22:34
[Gitlab user @willsalmon] [Gitlab user @DouglasWinship] nice, can you please create a WIP: Merge Request with what you have at the moment?

In GitLab by [Gitlab user @christopherphang] on Jun 29, 2020, 11:29
marked this issue as related to freedesktop-sdk/freedesktop-sdk#990

In GitLab by [Gitlab user @christopherphang] on Jun 29, 2020, 11:29
marked this issue as related to freedesktop-sdk/freedesktop-sdk#990

In GitLab by [Gitlab user @christopherphang] on Jun 29, 2020, 11:29
removed the relation with freedesktop-sdk/freedesktop-sdk#990

In GitLab by [Gitlab user @christopherphang] on Jun 29, 2020, 11:29
removed the relation with freedesktop-sdk/freedesktop-sdk#990

In GitLab by [Gitlab user @christopherphang] on Jun 29, 2020, 11:29
marked this issue as related to freedesktop-sdk/freedesktop-sdk#990

In GitLab by [Gitlab user @christopherphang] on Jun 29, 2020, 11:29
marked this issue as related to freedesktop-sdk/freedesktop-sdk#990

In GitLab by [Gitlab user @jjardon] on Jun 29, 2020, 21:03
[Gitlab user @willsalmon] I tried to build the current willsalmon/overnight branch (which uses the bst2 branch from freedesktop-sdk, which seems to be the correct one: https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/issues/990#note_369075452)
But it doesnt' seems to work: https://gitlab.com/BuildStream/buildstream/-/jobs/616390670
Am I missing something?

In GitLab by [Gitlab user @jjardon] on Jun 29, 2020, 21:03
[Gitlab user @willsalmon] I tried to build the current willsalmon/overnight branch (which uses the bst2 branch from freedesktop-sdk, which seems to be the correct one: https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/issues/990#note_369075452)
But it doesnt' seems to work: https://gitlab.com/BuildStream/buildstream/-/jobs/616390670
Am I missing something?

In GitLab by [Gitlab user @willsalmon] on Jun 29, 2020, 21:55
So that looks like on of the plugins ill have a look, bst is not good at reporting which one but the big issue is that the branch [Gitlab user @DouglasWinship] and myself are working on for FD-SDK is targeting the bst-1.93.4 dev tag and bst-master has already changed the junction API so im not sure were we are going to find the resources to maintain too many branches..

In GitLab by [Gitlab user @willsalmon] on Jun 29, 2020, 21:55
So that looks like on of the plugins ill have a look, bst is not good at reporting which one but the big issue is that the branch [Gitlab user @DouglasWinship] and myself are working on for FD-SDK is targeting the bst-1.93.4 dev tag and bst-master has already changed the junction API so im not sure were we are going to find the resources to maintain too many branches..

In GitLab by [Gitlab user @jjardon] on Jun 30, 2020, 12:20
[Gitlab user @willsalmon] I would suggest to change the CI job to (temporarily) use that tag; make the CI pass, then other a new issue to move from 1.93.4 to master

In GitLab by [Gitlab user @jjardon] on Jun 30, 2020, 12:20
[Gitlab user @willsalmon] I would suggest to change the CI job to (temporarily) use that tag; make the CI pass, then other a new issue to move from 1.93.4 to master

In GitLab by [Gitlab user @willsalmon] on Jun 30, 2020, 12:23
[Gitlab user @jjardon] my branch was based on the 1.93.4 tag, i dont know what you have done with your branch.

In GitLab by [Gitlab user @willsalmon] on Jun 30, 2020, 12:23
[Gitlab user @jjardon] my branch was based on the 1.93.4 tag, i dont know what you have done with your branch.

In GitLab by [Gitlab user @jjardon] on Jun 30, 2020, 12:35
[Gitlab user @willsalmon] no changes in my branch apart from allow the schedule job to run
can you please a MR here so we are sure we are talking about the same change?

In GitLab by [Gitlab user @jjardon] on Jun 30, 2020, 12:35
[Gitlab user @willsalmon] no changes in my branch apart from allow the schedule job to run
can you please a MR here so we are sure we are talking about the same change?

In GitLab by [Gitlab user @DouglasWinship] on Jul 6, 2020, 11:08
I believe everyone in this conversation already knows this, but just to keep the issue up to date:
The closest thing we have to a canonical bst 2 branch of freedesktop-sdk is now freedesktop-sdk-20.08beta.1-buildstream2.
However that branch is incomplete, waiting on https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/merge_requests/2851 and https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/merge_requests/2853.
The source branch for https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/merge_requests/2853 is our current best contender for a complete CI pass on bst 1.93.4, but it still fails on the 32 bit jobs.
[Gitlab user @abderrahimk] seems to be working on changes to buildbox-fuse, which I think are intended to resolve that. https://gitlab.com/freedesktop-sdk/infrastructure/freedesktop-sdk-docker-images/-/merge_requests/120
[Gitlab user @jjardon] I didn't completely follow your question, but are you still asking for an MR?

In GitLab by [Gitlab user @DouglasWinship] on Jul 6, 2020, 11:08
I believe everyone in this conversation already knows this, but just to keep the issue up to date:
The closest thing we have to a canonical bst 2 branch of freedesktop-sdk is now freedesktop-sdk-20.08beta.1-buildstream2.
However that branch is incomplete, waiting on https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/merge_requests/2851 and https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/merge_requests/2853.
The source branch for https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/merge_requests/2853 is our current best contender for a complete CI pass on bst 1.93.4, but it still fails on the 32 bit jobs.
[Gitlab user @abderrahimk] seems to be working on changes to buildbox-fuse, which I think are intended to resolve that. https://gitlab.com/freedesktop-sdk/infrastructure/freedesktop-sdk-docker-images/-/merge_requests/120
[Gitlab user @jjardon] I didn't completely follow your question, but are you still asking for an MR?

In GitLab by [Gitlab user @abderrahimk] on Jul 6, 2020, 16:40
I'll add that freedesktop-sdk/infrastructure/freedesktop-sdk-docker-images!120 is just a workaround for https://gitlab.com/BuildGrid/buildbox/buildbox-fuse/-/issues/40

In GitLab by [Gitlab user @abderrahimk] on Jul 6, 2020, 16:40
I'll add that freedesktop-sdk/infrastructure/freedesktop-sdk-docker-images!120 is just a workaround for https://gitlab.com/BuildGrid/buildbox/buildbox-fuse/-/issues/40

In GitLab by [Gitlab user @DouglasWinship] on Jul 6, 2020, 18:26
mentioned in merge request bst-plugins-experimental!125

In GitLab by [Gitlab user @DouglasWinship] on Jul 6, 2020, 18:26
mentioned in merge request bst-plugins-experimental!125

In GitLab by [Gitlab user @DouglasWinship] on Jul 6, 2020, 18:31
I think I've got the problem with [Gitlab user @jjardon]'s job resolved. There's a problem in get_unique_key for the flatpak_image plugin.
The fix is here: https://gitlab.com/BuildStream/bst-plugins-experimental/-/merge_requests/125
Compare: https://gitlab.com/BuildStream/buildstream/-/jobs/616390670 [Gitlab user @jjardon]'s original failing job
With: https://gitlab.com/BuildStream/buildstream/-/jobs/625901528 (The same job, except using the updated branch of bst-plugins-experimental)
The only thing I don't understand, is why it wasn't an issue in the freedesktop-sdk jobs, and why it was an issue here.

In GitLab by [Gitlab user @DouglasWinship] on Jul 6, 2020, 18:31
I think I've got the problem with [Gitlab user @jjardon]'s job resolved. There's a problem in get_unique_key for the flatpak_image plugin.
The fix is here: https://gitlab.com/BuildStream/bst-plugins-experimental/-/merge_requests/125
Compare: https://gitlab.com/BuildStream/buildstream/-/jobs/616390670 [Gitlab user @jjardon]'s original failing job
With: https://gitlab.com/BuildStream/buildstream/-/jobs/625901528 (The same job, except using the updated branch of bst-plugins-experimental)
The only thing I don't understand, is why it wasn't an issue in the freedesktop-sdk jobs, and why it was an issue here.

In GitLab by [Gitlab user @DouglasWinship] on Jul 7, 2020, 10:39
UPDATE - We now have a completely successful pipeline that runs the overnight job, using bst2. See the overnight job at: https://gitlab.com/BuildStream/buildstream/-/jobs/625935362
The fix for this particular issue seems to be:

Use a branch of bst-plugins-experimental that fixes the unique_key issue in flatpak_image. (This can be master, as soon as https://gitlab.com/BuildStream/bst-plugins-experimental/-/merge_requests/125 merges)
Use a branch of freedesktop-sdk that includes the sandbox build-arch fix from https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/commit/c956395dfe5634529d74cfe797944a827b37eefb. Currently the best available branch is - the source branch from https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/merge_requests/2853. When that that MR merges, we'll be able to use update-plugins-to-bst-1.93.4.

That means we've figured out the technical issues, but I'm not clear what we actually want to do with this. Do we need to maintain a branch where the overnight tests pass? When do we want to merge this into master? etc.

In GitLab by [Gitlab user @DouglasWinship] on Jul 7, 2020, 10:39
UPDATE - We now have a completely successful pipeline that runs the overnight job, using bst2. See the overnight job at: https://gitlab.com/BuildStream/buildstream/-/jobs/625935362
The fix for this particular issue seems to be:

Use a branch of bst-plugins-experimental that fixes the unique_key issue in flatpak_image. (This can be master, as soon as https://gitlab.com/BuildStream/bst-plugins-experimental/-/merge_requests/125 merges)
Use a branch of freedesktop-sdk that includes the sandbox build-arch fix from https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/commit/c956395dfe5634529d74cfe797944a827b37eefb. Currently the best available branch is - the source branch from https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/merge_requests/2853. When that that MR merges, we'll be able to use update-plugins-to-bst-1.93.4.

That means we've figured out the technical issues, but I'm not clear what we actually want to do with this. Do we need to maintain a branch where the overnight tests pass? When do we want to merge this into master? etc.

In GitLab by [Gitlab user @christopherphang] on Jul 7, 2020, 13:17
[Gitlab user @DouglasWinship] [Gitlab user @jjardon] might want to comment, but I would ensure the MR in bst-plugins-experimental gets merged, and merge any required changes to the the 'canonical' bst-2 branch in freedesktop-sdk
Once you have both items, I would prepare an MR in buildstream that will change gitlab-ci and point to those new refs for bst-plugins-experimental and freedesktop-sdk. That MR can be merged to master.

In GitLab by [Gitlab user @christopherphang] on Jul 7, 2020, 13:17
[Gitlab user @DouglasWinship] [Gitlab user @jjardon] might want to comment, but I would ensure the MR in bst-plugins-experimental gets merged, and merge any required changes to the the 'canonical' bst-2 branch in freedesktop-sdk
Once you have both items, I would prepare an MR in buildstream that will change gitlab-ci and point to those new refs for bst-plugins-experimental and freedesktop-sdk. That MR can be merged to master.

In GitLab by [Gitlab user @abderrahimk] on Jul 7, 2020, 15:16

UPDATE - We now have a completely successful pipeline that runs the overnight job, using bst2. See the overnight job at: https://gitlab.com/BuildStream/buildstream/-/jobs/625935362

Well, not yet. You have a branch on top of 1.93.4 that's successful. Rebasing it on top of master will make it fail again because of !1901

In GitLab by [Gitlab user @abderrahimk] on Jul 7, 2020, 15:16

UPDATE - We now have a completely successful pipeline that runs the overnight job, using bst2. See the overnight job at: https://gitlab.com/BuildStream/buildstream/-/jobs/625935362

Well, not yet. You have a branch on top of 1.93.4 that's successful. Rebasing it on top of master will make it fail again because of !1901

In GitLab by [Gitlab user @DouglasWinship] on Jul 7, 2020, 16:30
Oh, to be clear, I meant that we had a pipeline that worked with some version of bst2. I didn't mean to imply that we had one working with bst master.
But now that you mention it, I tried rebasing it on master earlier today. And it looks like it did pretty well: https://gitlab.com/BuildStream/buildstream/-/pipelines/163947859

In GitLab by [Gitlab user @DouglasWinship] on Jul 7, 2020, 16:30
Oh, to be clear, I meant that we had a pipeline that worked with some version of bst2. I didn't mean to imply that we had one working with bst master.
But now that you mention it, I tried rebasing it on master earlier today. And it looks like it did pretty well: https://gitlab.com/BuildStream/buildstream/-/pipelines/163947859

In GitLab by [Gitlab user @DouglasWinship] on Jul 7, 2020, 16:32
Ah, I clearly have selective vision. That pipeline didn't pass at all. I was seeing what I wanted to see.

In GitLab by [Gitlab user @DouglasWinship] on Jul 7, 2020, 16:32
Ah, I clearly have selective vision. That pipeline didn't pass at all. I was seeing what I wanted to see.

In GitLab by [Gitlab user @DouglasWinship] on Jul 7, 2020, 19:10
I have an MR now in freedesktop-sdk, to resolve the junction conflict: https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/merge_requests/2925
And I'm testing it buildstream's CI jobs here: https://gitlab.com/BuildStream/buildstream/-/merge_requests/1987 (2nd / most recent pipeline)
UPDATE: MR 2925 won't be accepted. The change works well with current buildstream master (see the job above), but it's not compatible with bst 1.93.4 (which the freedesktop-sdk branch currently targets).

In GitLab by [Gitlab user @DouglasWinship] on Jul 7, 2020, 19:10
I have an MR now in freedesktop-sdk, to resolve the junction conflict: https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/merge_requests/2925
And I'm testing it buildstream's CI jobs here: https://gitlab.com/BuildStream/buildstream/-/merge_requests/1987 (2nd / most recent pipeline)
UPDATE: MR 2925 won't be accepted. The change works well with current buildstream master (see the job above), but it's not compatible with bst 1.93.4 (which the freedesktop-sdk branch currently targets).

In GitLab by [Gitlab user @traveltissues] on Jul 8, 2020, 09:40
[Gitlab user @DouglasWinship] looks like you'll need to rebase that on https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/commits/valentindavid/bst2
edit: actually, [Gitlab user @willsalmon] you seem to be missing a commit from there on https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/commits/willsalmon/bst2 too

In GitLab by [Gitlab user @traveltissues] on Jul 8, 2020, 09:40
[Gitlab user @DouglasWinship] looks like you'll need to rebase that on https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/commits/valentindavid/bst2
edit: actually, [Gitlab user @willsalmon] you seem to be missing a commit from there on https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/commits/willsalmon/bst2 too

In GitLab by [Gitlab user @DouglasWinship] on Jul 8, 2020, 11:03
[Gitlab user @traveltissues] freedesktop-sdk-20.08beta.1-buildstream2 is the new main branch for buildstream2 development on freedesktop-sdk.
It was built on top of [Gitlab user @willsalmon]'s branch, which was built on top of valentindavid's branch. But they've both been rebased on master more recently than valentin's has been. (And beta.1-buildstream2 has been re-ordered and had a few commits squashed together as well).
That might be why there's some commits apparently missing.

In GitLab by [Gitlab user @DouglasWinship] on Jul 8, 2020, 11:03
[Gitlab user @traveltissues] freedesktop-sdk-20.08beta.1-buildstream2 is the new main branch for buildstream2 development on freedesktop-sdk.
It was built on top of [Gitlab user @willsalmon]'s branch, which was built on top of valentindavid's branch. But they've both been rebased on master more recently than valentin's has been. (And beta.1-buildstream2 has been re-ordered and had a few commits squashed together as well).
That might be why there's some commits apparently missing.

In GitLab by [Gitlab user @jjardon] on Jul 9, 2020, 11:45
mentioned in merge request !1987

In GitLab by [Gitlab user @jjardon] on Jul 9, 2020, 11:45
mentioned in merge request !1987

In GitLab by [Gitlab user @DouglasWinship] on Jul 9, 2020, 11:49
changed title from Overnig{-th-} test is failing: freedesktop-sdk being used need to be updated to support buildstream master to Overnig{+ht+} test is failing: freedesktop-sdk being used need to be updated to support buildstream master

In GitLab by [Gitlab user @DouglasWinship] on Jul 9, 2020, 11:49
changed title from Overnig{-th-} test is failing: freedesktop-sdk being used need to be updated to support buildstream master to Overnig{+ht+} test is failing: freedesktop-sdk being used need to be updated to support buildstream master

In GitLab by [Gitlab user @marge-bot123] on Jul 15, 2020, 03:17
closed via merge request !1987

In GitLab by [Gitlab user @marge-bot123] on Jul 15, 2020, 03:17
closed via merge request !1987

In GitLab by [Gitlab user @marge-bot123] on Jul 15, 2020, 03:17
mentioned in commit a13693ea54fdc16db4d51c7162a71f008df7132d

In GitLab by [Gitlab user @marge-bot123] on Jul 15, 2020, 03:17
mentioned in commit a13693ea54fdc16db4d51c7162a71f008df7132d

In GitLab by [Gitlab user @DouglasWinship] on Jul 15, 2020, 10:29
changed the description

In GitLab by [Gitlab user @DouglasWinship] on Jul 15, 2020, 10:29
changed the description


Sample: Working with Cloud Events

Summary
With CloudEvent being added as a common abstraction in Azure.Core, it provides a neutral type for working with event data across the Azure messaging services.  It would be helpful to have a set of samples fore core Event Hubs scenarios that demonstrate translating between CloudEvent and EventData.
Scope of Work

A sample for Azure.Messaging.EventHubs focused on interacting with CloudEvent and Event Hubs should be written, covering:

Translating between CloudEvent and EventData, including where commonly used data/attributes map between them
Using CloudEvent with the EventHubProducerClient and EventHubBufferedProducerClient for publishing data
Using CloudEvent with the EventHubConsumerClient and EventProcessorClient for consuming data

A sample for Azure.Messaging.EventHubs.Processor focused on interacting with CloudEvent and Event Hubs should be written, covering:

Using CloudEvent with EventProcessorClient for consuming data

Out of Scope

Demonstrating interactions between Event Hubs and other messaging libraries using CloudEvent as an intermediate format; this would cross library boundaries and should be considered as a stand-alone sample in the common samples area of the repository.

Demonstrating use in an Azure Functions context; that should be considered as a stand-alone effort for the extensions package.

Success Criteria

The topics detailed by the scope have been documented in the samples.

All code in the samples are snippet-driven, with the code being built and smoke tested as part of nightly runs.

The existing samples have been reviewed for accuracy and are in a good state for release of the Event Hubs client libraries.

The tests necessary for sample validation have been created or adjusted and pass reliably.

The existing test suite continues to produce deterministic results and pass reliably.

References and Resources

Cloud Event source

Hello, I would like to work on this. Any guidance is appreciated.

Hi @ruvyas.   It's a pleasure to make your acquaintance and thank you for your interest in helping to improve the Azure SDK experience.   We'd love to have you pick this issue up, and I'm happy to serve as your contact for doing so.
A good place to get started would be to look through our contributing guide for Event Hubs; that will help you get a development environment set up and links out to other important sources, such as the main repository contributing guide.    Since our samples are structured as markdown files with code snippets injected from tests, the Updating Sample Snippets section would also be helpful.
For Event Hubs, the samples themselves can be found in the samples directory, and code is injected from snippets created in the tests/Snippets area of the project.   We'll probably want to look at this as a new sample rather than trying to integrate the content into an existing one.   Please feel free to create a new file for the markdown and tests.   Otherwise, just following the patterns from the other samples so that things are consistent in presentation would by my biggest thought.
As you're looking through things, please feel free to ping me with any questions or blockers for working in the repository, and as a reviewer for PRs.

@jsquire Thank you for the above information. I have few clarifying questions.

Using CloudEvent with the EventHubProducerClient and EventHubBufferedProducerClient for publishing data

I don't see any overloads that accepts CloudEvent for publishing events. Does this mean we have to create a sample CloudEvent json, convert/map it to EventData then publish the event?

Using CloudEvent with the EventHubConsumerClient and EventProcessorClient for consuming data

Similarly, for Consumer we read EventData  and convert/map it to CloudEvent?

I don't see any overloads that accepts CloudEvent for publishing events. Does this mean we have to create a sample CloudEvent json, convert/map it to EventData then publish the event?
Similarly, for Consumer we read EventData and convert/map it to CloudEvent?

Yes.  I'd start with Azure.Messaging.CloudEvent from Azure.Core - whether you pull that in from JSON or create it directly - and map that to/from EventData.

Revisiting - this is not a scenario for which we've received much customer interest and doesn't fit the current direction of the Event Hubs product.  Closing this out.


Remove the retries gem

Retries is only used by the CLI providers. Puppet itself also provides retry functionality. This avoids the need to ensure a gem is installed in the right environment, which may not even work if it's a disconnected environment.
This does ignore a parameter for the maximum time to sleep. I'm looking for feedback on how to best deal with this.

I like it, but does it create any breaking changes?

Maybe. From a user perspective the max total sleep time is ignored and that's a change. Perhaps we should go further and actually remove the parameter from the types. That would be a breaking change, but more honest.

It looks like the tests are failing because something doesn't pass. With the exponential backoff I think it takes too long. Probably need to tune the 30 retries a bit.

retries
seconds

0
0

1
0

2
0

3
0

4
1

5
2

6
5

7
12

8
24

9
50

10
101

11
203

12
408

13
817

14
1636

15
3275

16
6551

17
13105

18
26212

19
52426

20
104855

21
209713

22
419428

23
838858

24
1677719

25
3355440

26
6710883

27
13421770

28
26843542

29
53687088

30
107374179

I think 10 retries is a good number. 30 retries is about 3,4 years which is a bit excessive.

It still times out where Ubuntu was previously green. I created https://github.com/voxpupuli/puppet-jenkins/pull/986 so we don't need pending anymore.

I've rebased this. Still need test fixes :/


[windows] Update ccache to 4.7

As mentioned in #88, ccache has made updates to further support the Windows environment. This bumps the version used to 4.7 which has the latest fixes.

There seem to be unrelated changes (logging and yarn lock file). Can you please make two separate PRs for that?

Thanks for the PR! It seems something is wrong with your build setup. No problem! Can you reduce the PR to only have the changes in restore.ts or with other words: revert the js changes? I can fix the build afterwards, which I have to do anyway after merging dependabot changes.

Nice! Looking forward to greatly sped-up Windows builds
Is anything else blocking the merge?

Actually, might as well go straight to 4.7.2 instead of 4.7.0

Thanks, merging it now, happily take another PR to bump ccache for windows to >= 4.7.2


add Delete method to Dot class

Add a delete() static method to the Dot class to unset a provided key if set in the array.

This work will be completed as part of #8


Donut charts

Finished the donut charts in a scaleable way.  Each category will have a different color. I will also change the code to allow for more modification once everything is in master and I can actually run the front-end code on my computer.
JSFiddle: https://jsfiddle.net/ncdqm8hs/1/
And if that doesn't work, screen recording: https://drive.google.com/file/d/1zxy3eArrNZG_fTeJYt00xAc_gZFPBgKy/view?usp=sharing

@gracetian6 I made it so both of yall are "editors" and can share it. Everyone else who has the link may comment.

Will include these in better pull request.


Bulk writes

JSON API doesn't support bulk writes out of the box, nor does it support extensions (yet), but it seems like Fortune has all of the pieces to enable this.

The DB adapters support bulk write operations
This is just a thin HTTP layer on top of those

I did a quick perusal of the documentation to try to figure out how to get this working for JSON API, but nothing immediately stood out to me. I don't need a fully working example, or anything, but I'm curious: would it be easy to extend this serializer to support bulk writes? If the answer is yes, could you point me to any relevant docs that could help me set that up?
Thanks!
p.s. Fortune, and this serializer, are both 👌

Yep, I know about this. The bulk extension used to be official and this serializer used to support it, but they backtracked and now it's not really supported anymore so I removed it here too.
You would just need to modify the processRequest method here.

Thanks for the quick and helpful reply, @daliwali ! I'm going to try this out. I'll close this issue for now.


Promocodefix

Description
Promo code case sensitivity issue
https://github.com/SalesforceCommerceCloud/pwa-kit/issues/219

Types of Changes

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Documentation update
[ ] Breaking change (could cause existing functionality to not work as expected)
[x] Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

Removing a public function or component or prop
Adding a required argument to a function
Changing the data type of a function parameter or return value
Adding a new peer dependency to package.json

Changes
Removed the code that was capitalizing the Promo Code in the Cart and Checkout pages
How to Test-Drive This PR

npm start
Add any product to cart
Input the promo code orderLevel

Checklists

General

[x] Changes are covered by test cases
[ ] CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance
You must check off all items in one of the follow two lists:

[ ] There are no changes to UI

or...

[x] Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
[x] Changes comply with WCAG 2.0 guidelines levels A and AA
[x] Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

[ ] Changes include a UI text update in the Retail React App (which requires translation)

Resubmitted as #224. Closing


nginx+php doesn't work

ip+port
php-fpm.config
listen = <IP_ADDRESS>:9000
nginx.conf
 location ~ \.php$ {         #       # With php-cgi (or other tcp sockets):                fastcgi_pass <IP_ADDRESS>:9000;                 fastcgi_index  index.php;                 fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;                 include        fastcgi_params;         }
php restart
nginx restart
nginx.error.log
2018/09/02 23:24:22 [error] 13899#13899: *9 upstream timed out (110: Connection timed out) while reading upstream, client: <IP_ADDRESS>, server: _, request: "GET /i.php HTTP/1.1", upstream: "fastcgi://<IP_ADDRESS>:9000", host: "local.tbk.com"
/var/log/php7.2-fpm.log:
[02-Sep-2018 23:12:36] NOTICE: exiting, bye-bye! [02-Sep-2018 23:12:36] ERROR: failed to retrieve TCP_INFO for socket: Protocol not available (92) [02-Sep-2018 23:12:36] NOTICE: fpm is running, pid 13852 [02-Sep-2018 23:12:36] NOTICE: ready to handle connections [02-Sep-2018 23:12:36] NOTICE: systemd monitor interval set to 10000ms [02-Sep-2018 23:12:37] ERROR: failed to retrieve TCP_INFO for socket: Protocol not available (92) [02-Sep-2018 23:12:39] ERROR: failed to retrieve TCP_INFO for socket: Protocol not available (92)
why ?

#1982


cannot import name 'to_pyrecords_with_preppy' from 'azureml.dataprep.api._dataframereader'

mltable:
1.3.0:
Synapse notebook:
Python 3.10:

Describe the bug
I am trying to create a ML table from delimited CSV paths. As I am using Synapse and python SDK v2, I have to ML table and I am facing issues while creating it from spark dataframe
To Reproduce
Steps to reproduce the behavior:

Use any spark dataframe
Upload the dataframe to datastore
`datastore = ws.get_default_datastore()
training_pd = training_data.toPandas().to_csv('training_pd.csv', index=False)

datastore.upload_files(files = ['training_pd.csv'],
target_path = 'train-dataset/tabular/',
overwrite = True,
show_progress = True)
4.import mltable
paths = [
{
'file': 'azureml://subscriptions//datastores/workspaceblobstore/paths/train-dataset/tabular/training_pd.csv'
}
]
tbl = mltable.from_delimited_files(paths=paths)

Thank you for feedback @aayushsin . We will investigate and get back to you asap.
cc @azureml-github


[C#] Physics2DDirectSpaceState IntersectRay causes crash

Godot version:
3.0 beta 2 (with mono)

OS/device including version:
Windows 10 Version 10.0.16299 build 16299

Issue description:
Trying to query the 2D physics space for ray intersections causes the program to crash.

Steps to reproduce:
Run the provided minimal reproduction project. Click the screen and observe the crash. Code is in ErrorDemo.cs
Minimal reproduction project:
Error.zip

[x] I searched the existing GitHub issues for potential duplicates.

When Godot crashes it should print a backtrace to the console; I would believe that's true of the mono flavor as well.  What does that say?
I'm not setup with mono, but I ported your ErrorDemo.cs to GDScript.
extends Node2D

func _unhandled_input(event):
	if event.is_pressed():
		doIntersect()

func doIntersect():
	var space = get_world_2d().get_direct_space_state()
	print(space)

	var from = global_position
	var to = global_position + Vector2(100, 0)

	var result = space.intersect_ray(from, to, [], 1)
	print(result)

Clicking produces the following results:
[Physics2DDirectSpaceStateSW:945]
(collider:[StaticBody2D:959]), (collider_id:959), (metadata:Null), (normal:(-1, 0)), (position:(243.863998, 70.263199)), (rid:[RID]), (shape:0)

Note that GDScript complained about passing null to intersect_ray(); an empty array allowed me to continue.  You might want to try that in C# too.

Thanks for the suggestion, unfortunately changing the important line to:
var result = space.IntersectRay(from, to, new object[0], 1);
Still causes a crash


add jp locale

Here's the locale data for jp. 🇯🇵
(I am not Japanese but lived in Japan for a couple of years.)

@jasonwaiting-dev Thank you! And tell me please following things:

What is postal code format in Japan.
What is Japan international phone number code.
What is Japan ISBN group code.
What is address format in Japan.

For example in Russia we have following format {siffux} {street_name} {street_number}

Also run tests, please. Just add class to tests/test_locales.py
class JapaneseTest(LocaleBase, TestCase):
    LANG = 'jp'

Current coverage is 99.10% (diff: 100%)

Merging #114 into master will increase coverage by 0.05%

@@             master       #114   diff @@
==========================================
  Files            45         45
  Lines          1894       1894
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1876       1877     +1
+ Misses           18         17     -1
  Partials          0          0

Powered by Codecov. Last update d263fad...e2f90ab

@lk-geimfari Thanks for your feedback! I

What is postal code format in Japan.

###-####, e.g. 100-0001

What is Japan international phone number code and format of phone number.

+81 ### #### ####

What is Japan ISBN group code.

4

What is address format in Japan.

Japanese addressing system is very different from other countries. We basically use district + block + building only.
For example,

〒100-8994
Tōkyō-to Chūō-ku Yaesu 1-5-3
Tōkyō Chūō Yūbin-kyoku

|Postal code|
|Prefecture| |Ward| |Town| |District|-|Block|-|Building|
|Building Name|
reference
Most streets in Japan don't even have names. The street names I used in address.py are all the main streets in the cities.
The current address format I am using is {street_name}{street_number} {suffux} so that all tests can be passed. However, I think we have to address this issue! I noticed that there are some customizations for different locales, e.g.
if self.locale == 'ru':
    nations = self.data['nationality'][gender]
    return choice(nations)
else:
    return choice(self.data['nationality'])

Should we do the same for Japan addressing system?

@jasonwaiting-dev If this is one correct way then yes, we should.


attachToExpress() , attachToLambda() function renaming

Sorry to be the process guy, but this one really needs a CHANGELOG entry and something in UPGRADING. It's so much easier to take the habit of documenting API changes while small changes are made than have to go through git history before a release and hope to uncover every single thing, don't you think? Lets make it easy on our users?

Looks like @mreinstein deleted his fork, probably following https://github.com/alexa-js/alexa-app-server/pull/56. Closing this, renaming these functions is a good idea, but not required and can wait.


Setup gRPC handlers

Add gRPC to the project and change structure to handle accordingly.

Yes grpc+grpc_gateway
No mux required really now


Repeated SSR configuration [enhancement]

While developing applications for the snitch we've come up with a potential improvement:
When the developer configures only one SSR he does not know if the other registers may have still some configuration and will also behave as SSR when we call snrt_ssr_enable().
So we'd propose to have some function like snrt_ssr_clear() which resets all registers (that they behave like normal registers) and the developer knows that all registers he configures afterwards will be enabled when calling snrt_ssr_enable() and no other registers.

Do you have an example on when this functionality may be helpful? For most config registers, the reset value is not necessarily helpful for real streams, so you would probably set them initially anyways and then leave them unchanged for following streams.
Can you elaborate on what you mean by "normal registers"? The launch registers having side effects is intentional, and the lower-address registers having some field restrictions and being shadowed are intentional design choices, too.

As it's semantically incorrect (as mentioned in #449) to use one register as SSR and another as a regular FPR this is needless.
I meant to use ft1 as a regular FPR / normal register (or actually the compiler) and ft0 as SSR.

just for completeness: you can use some registers as SSRs and some as FPRs simultaneously; it's just that the subset of registers connected in HW to SSR datapaths (ft0, ft1, and ft2 by default) can only switched into and out of SSR mode together, but all other FPRs continue to work as regular registers even while SSRs are enabled, so you could use ft3 and all other non-SSR registers as temporaries.


1.1.0_wmagent version of add Campaign and PrepID in fwjr

1.0.21 wmagent version of #7664

Still need to update to all the agent

@amaltaro, To convince Alan that it was tested. 😄

Fake picture :P

It is hard to trick you :-)

FYI @ticoann @vkuznet this patch has been pushed to all the production agents as of yesterday later in the afternoon.


When making a get request that should return a Json body, the RequestContext returns nothing

I am testing Zuul out as an edge gateway to a micro service that returns json for a GET request. I used the sample route filter in the simple-webapp, but nothing is returned. When I inspect the HttpResponse in the sendResponse() method I do see the json content in the entity.content , however when it is converted to a httpServerletResponse for the RequestContext all response body, code, and content length is lost. Is the example route filter incorrect or am I doing something wrong?

I figured this out, you need the post/SendResponse.groovy filter to actually write responses back to the client. I wish there was a way to make PR against the wiki to include this under the Writing Filters part, but since there is not, can someone at netflix please update the Wiki with this tidbit as it may save others some time.


Lazily load mapbox-gl-rtl-text plugin

Load the BSD-licensed mapbox-gl-rtl-text plugin from a CDN to ensure that Arabic- and Hebrew-language labels appear with the correct text shaping. The plugin is only loaded when needed.

Fixes #580.

Looks great!


fix: update entity ids of removed members

Updating the id of the old removed members can allow us to keep the id uniqueness and have only one hash(id commitment + group id) member id (the one related to the last active leaf).
Removed members ids will be equal to hash(removedMember.id, removedMember.index).
@jdhyun09

It makes sense. great solution!
@cedoor

https://github.com/interep-project/subgraph/blob/bc1a6e38323d5c9fc052eee29247f92752f7bcac/src/mapping.ts#L117

You're right! Thank you :)


Revert #6632 for Kodi

fixes #6674

Actually, going to try @pvizeli's recommendation and have the lib create it's own task.


Multiple JOINS

Implemented a support for multiple join statements by introducing an array with required info such as JOIN type, ON clause (which could be a Filter or raw SQL) and USING clause.
.syntaxError value is almost the same with exception that both .on and .using methods is checking JOIN clause existence when they are used and not on .build.
Also added tests to check if Select query with multiple joins is correct.
Issue: IBM-Swift/Swift-Kuery#29

Thanks, it looks good! We will be able to accept this within several days.


Devices not appear up in Home app.

Describe Your Problem:
LG ACs does not appear in Homekit. First appeared in Homebrdige accessories, I could turn on and off the ACs, but now it isn't appear there too. So nowhere able to control.
Logs:
[4/22/2022, 1:30:33 PM] [homebridge-lg-thinq] Loaded homebridge-lg-thinq v1.2.14 child bridge successfully
[4/22/2022, 1:30:33 PM] Loaded 0 cached accessories from cachedAccessories.0E2D3611CB5B.
[4/22/2022, 1:30:34 PM] Homebridge v1.4.0 (HAP v0.10.0) (homebridge-lg-thinq) is running on port 46982.
[4/22/2022, 1:30:37 PM] [homebridge-lg-thinq] Successfully connected to the ThinQ API.
Plugin Config:
{
"country": "HU",
"language": "hu_HU",
"auth_mode": "token",
"refresh_token": "5794948692ce8ce4fe80a32046--idk this is public or not--4b623e2ec91bb546460b5b651b27",
"username"<EMAIL_ADDRESS>"password": "private",
"devices": [
{
"id": "d27c0210-7149-11d3-80b1-2c2bf9fc6a6b",
"name": "Bedroom",
"type": "AC",
"ac_air_quality": false,
"ac_mode": "BOTH",
"ac_swing_mode": "BOTH",
"ac_temperature_sensor": true,
"ac_fan_control": true
},
{
"id": "d27c5030-7149-11d3-80b3-2c2bf9ce371a",
"name": "Living room",
"type": "AC",
"ac_air_quality": false,
"ac_mode": "BOTH",
"ac_swing_mode": "BOTH",
"ac_temperature_sensor": true,
"ac_fan_control": true
}
],
"thinq1": false,
"refresh_interval": 20,
"platform": "LGThinQ",
"_bridge": {
"username": "0E:2D:36:11:CB:5B",
"port": 46982
}
}
Environment:

Plugin Version: v1.2.14
Homebridge Version: v1.4.0
Node.js Version: v16.14.2
NPM Version: v8.5.0
Operating System: CoreElec, Docker

please turn on homebridge debug mode and upload some debug logging

Thank you @nVuln . I found this settings, I turned it on, bot where to see the debug logging? Sorry Im new in Homebridge, and I could not found any Wiki about it.
Thanks,
Adam

[4/23/2022, 11:08:23 AM] Loaded plugin<EMAIL_ADDRESS>[4/23/2022, 11:08:23 AM] Registering platform 'homebridge-lg-thinq.LGThinQ'
[4/23/2022, 11:08:25 AM] Loading 6 platforms...
[4/23/2022, 11:08:25 AM] [Config] Initializing config platform...
[4/23/2022, 11:08:25 AM] [Config] Running in Service Mode
[4/23/2022, 11:08:25 AM] [LGThinQ] Initializing LGThinQ platform...
[4/23/2022, 11:08:25 AM] [LGThinQ] Executed didFinishLaunching callback
[4/23/2022, 11:08:28 AM] [LGThinQ] [request] get https://route.lgthinq.com:46030/v1/service/application/gateway-uri
[4/23/2022, 11:08:29 AM] [LGThinQ] [request] post https://kic.lgthinq.com:46030/api/common/gatewayUriList
[4/23/2022, 11:08:30 AM] [LGThinQ] [request] post https://hu.lgeapi.com/oauth/1.0/oauth2/token
[4/23/2022, 11:08:30 AM] [LGThinQ] [request] post https://eic.lgthinq.com:46030/api/member/login
[4/23/2022, 11:08:31 AM] [LGThinQ] [request] get https://hu.lgeapi.com/users/profile
[4/23/2022, 11:08:31 AM] [LGThinQ] Successfully connected to the ThinQ API.
[4/23/2022, 11:08:31 AM] [LGThinQ] [request] get https://eic-service.lgthinq.com:46030/v1/service/homes
[4/23/2022, 11:08:31 AM] [LGThinQ] [request] get https://eic-service.lgthinq.com:46030/v1/service/homes/165056763487151627
[4/23/2022, 11:08:32 AM] [LGThinQ] Thinq1 device is skipped:  d27c0210-7149-11d3-80b1-2c2bf9fc6a6b: Bedroom (AC RAC_056905_WW)
[4/23/2022, 11:08:32 AM] [LGThinQ] Thinq1 device is skipped:  d27c5030-7149-11d3-80b3-2c2bf9ce371a: Living room (AC RAC_056905_WW)
I hope this is what we need.

I turned on ThinQ1 in HB plugin settings, and now I see in accessories in Homebridge. But in Hk don't.

More logs:
[4/23/2022, 12:37:26 PM] [LGThinQ] [request] post https://eic.lgthinq.com:46030/api/rti/rtiResult
[4/23/2022, 12:37:26 PM] [LGThinQ] [Bedroom] Received snapshot:  {"airState.opMode":0,"airState.operation":false,"airState.tempState.current":26,"airState.tempState.target":30,"airState.windStrength":2,"airState.wDir.vStep":100,"airState.wDir.hStep":13,"airState.circulate.rotate":0,"airState.lightingState.signal":0,"airState.quality.overall":0,"airState.quality.sensorMon":0,"airState.quality.PM1":0,"airState.quality.PM2":0,"airState.quality.PM10":0,"airState.wMode.jet":0,"online":true,"raw":{"Operation":"0","OpMode":"0","WindStrength":"2","TempUnit":"NS","TempCur":"26","TempCfg":"30","GroupType":"1","SleepTime":"0","OnTime":"0","OffTime":"0","RacAddFunc":"NS","ExtraOp":"0","DiagCode":"00","TimeBsOn":"0","TimeBsOff":"0","AirClean":"0","AutoDry":"0","PowerSave":"0","WDirVStep":"100","WDirHStep":"13","TempLimitMax":"0","TempLimitMin":"0","DuctZoneType":"0","ZoneControl":"0","DRED":"0","SensorPM1":"0","SensorPM2":"0","SensorPM10":"0","AirPolution":"0","HumidityCfg":"0","WaterTempCoolMin":"NS","WaterTempCoolMax":"NS","WaterTempHeatMin":"NS","WaterTempHeatMax":"NS","HotWaterTempMin":"NS","HotWaterTempMax":"NS","SensorHumidity":"0","TotalAirPolution":"0","SensorMon":"0","CleanDry":"0","ProductStatus":"0","AirMonitoring":"0","Humidification":"0","AirFast":"0","AirRemoval":"0","AirUVDisinfection":"0","WatertankLight":"0","SignalLighting":"0","WDirUpDown":"0","WDirLeftRight":"0","WSwirl":"0","Jet":"0","LowHeating":"0","CirculateStrength":"0","CirculateDir":"0","AntiBugs":"0","IceValley":"0","Humsave":"0","WaterTempCur":"0","HotWaterTempCur":"0","HotWaterTempCfg":"0","HotWaterMode":"0","HotWater":"0","AWHPTempCfgSwitch":"0","AirTempCoolMin":"NS","AirTempCoolMax":"NS","AirTempHeatMin":"NS","AirTempHeatMax":"NS","WaterInTempCur":"0","AWHPWATempControlSta":"0","DisplayControl":"0","SmartCare":"0","TwoSetCoolTemp":"0","TwoSetHeatTemp":"0","TwoSetCoolUSL":"0","TwoSetCoolLSL":"0","TwoSetHeatUSL":"0","TwoSetHeatLSL":"0","TwoSetACOState":"0","TwoSetModeDeadband":"0","TwoSetState":"0"}}
[4/23/2022, 12:37:26 PM] [LGThinQ] [request] post https://eic.lgthinq.com:46030/api/rti/rtiResult
[4/23/2022, 12:37:26 PM] [LGThinQ] [Living room] Received snapshot:  {"airState.opMode":6,"airState.operation":false,"airState.tempState.current":26,"airState.tempState.target":22,"airState.windStrength":2,"airState.wDir.vStep":100,"airState.wDir.hStep":35,"airState.circulate.rotate":0,"airState.lightingState.signal":0,"airState.quality.overall":0,"airState.quality.sensorMon":0,"airState.quality.PM1":0,"airState.quality.PM2":0,"airState.quality.PM10":0,"airState.wMode.jet":0,"online":true,"raw":{"Operation":"0","OpMode":"6","WindStrength":"2","TempUnit":"NS","TempCur":"26.5","TempCfg":"22","GroupType":"1","SleepTime":"0","OnTime":"0","OffTime":"0","RacAddFunc":"NS","ExtraOp":"0","DiagCode":"00","TimeBsOn":"0","TimeBsOff":"0","AirClean":"0","AutoDry":"0","PowerSave":"0","WDirVStep":"100","WDirHStep":"35","TempLimitMax":"0","TempLimitMin":"0","DuctZoneType":"0","ZoneControl":"0","DRED":"0","SensorPM1":"0","SensorPM2":"0","SensorPM10":"0","AirPolution":"0","HumidityCfg":"0","WaterTempCoolMin":"NS","WaterTempCoolMax":"NS","WaterTempHeatMin":"NS","WaterTempHeatMax":"NS","HotWaterTempMin":"NS","HotWaterTempMax":"NS","SensorHumidity":"0","TotalAirPolution":"0","SensorMon":"0","CleanDry":"0","ProductStatus":"0","AirMonitoring":"0","Humidification":"0","AirFast":"0","AirRemoval":"0","AirUVDisinfection":"0","WatertankLight":"0","SignalLighting":"0","WDirUpDown":"0","WDirLeftRight":"0","WSwirl":"0","Jet":"0","LowHeating":"0","CirculateStrength":"0","CirculateDir":"0","AntiBugs":"0","IceValley":"0","Humsave":"0","WaterTempCur":"0","HotWaterTempCur":"0","HotWaterTempCfg":"0","HotWaterMode":"0","HotWater":"0","AWHPTempCfgSwitch":"0","AirTempCoolMin":"NS","AirTempCoolMax":"NS","AirTempHeatMin":"NS","AirTempHeatMax":"NS","WaterInTempCur":"0","AWHPWATempControlSta":"0","DisplayControl":"0","SmartCare":"0","TwoSetCoolTemp":"0","TwoSetHeatTemp":"0","TwoSetCoolUSL":"0","TwoSetCoolLSL":"0","TwoSetHeatUSL":"0","TwoSetHeatLSL":"0","TwoSetACOState":"0","TwoSetModeDeadband":"0","TwoSetState":"0"}}

I turned on ThinQ1 in HB plugin settings, and now I see in accessories in Homebridge. But in Hk don't.

please follow step by step

remove homebridge bridge in home app
in homebridge setting page, clean cached accessories
try re-add homebridge to home app


Plans for Circuit breaker, BulkHead etc

Hi,
Are there any plans for incorporating Circuit Breaker, Timeout, Bulkhead Isolation patterns(alongwith PolicyWrap) just like done in the orginal Polly.NET framework?
Regards,
Sandip

Hi @sandipray63in,
I don't have any current plans or time to do so myself.
I am fine with accepting pull requests though.
Regards,
Maurice


[tests] Use random custom runtime classes to avoid cleanup collisions

What this PR does / why we need it:
Ensure that vm configuration tests use random runtime classes, to avoid colliding with delayed deletions of the custom runtime class from previous tests.
The failing runtime test in https://storage.googleapis.com/kubevirt-prow/reports/flakefinder/kubevirt/kubevirt/flakefinder-2022-10-24-168h.html#row0 shows that the test does not have the runtime class present.
Digging into the artifacts logs shows that the runtime class is indeed not present. It turns out that when we crate the runtime class, we don't check for an error. This allows that we will still start the test if the runtime class exists, but is already makred for deletion.
Switch to random runtime classes, to give runtime classes all the time they need to be finally removed (when all pods using it are teared down).
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

Rebased.

/lgtm

/hold cancel


Characters rendering different parts in each eye camera

Describe the bug
Opened it up on Quest 2 using virtual desktop, VR boots up nicely, watch the start of the game story of the truck driver all is good. Leon's driving scene starts, each eye renders different parts of him, only his head is rendered in both. Get to the gas station, see a headless model of him i think rendered in one eye standing by the cop car, his own body still rendered wonkily. Start playing, arms are rendered in one eye not the other.
Relaunch after deleting openvr_api file same thing.
Tried it through oculus with link cable, total chaos, renders on desktop, headset keeps saying "waiting" when in vr view
Upload logs and any crash dumps
Locate the re2_framework_log.txt in your game directory and upload it along with the issue.
If you crashed, upload the reframework_crash.dmp file as well.
Identify the REFramework version
1.5.1
To Reproduce
See description
Expected behavior
everything rendered in both eyes
Screenshots
Doesnt work
Desktop and VR (please complete the following information):

OS (e.g. Windows 11)
Win11
Graphics card
AMD 6600 XT
CPU
AMD 5600

Steam Deck/Linux (please complete the following information):
NA
Virtual Reality (please complete the following information):

Headset model
Quest 2
Runtime (OpenVR or OpenXR)
Tried both by later deleting the openvr_api file

Additional context
Add any other context about the problem here.
re2_framework_log.txt
re2_framework_log.txt

Duplicate issue #400.
Options:

Use the pd-upscaler branch
Use the old non-RT version of RE2 with TDB66 build
Change Leon's outfit


chore: modifying logger with write file

Pull Request Template
Description
modifying logger with write file
Please select the options that are relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] Pull Request follow only a single responsibility.
[x] Code follows the style guidelines of this project
[x] Performed a self-review of my own code
[ ] Commented my code, particularly in hard-to-understand areas
[ ] Made corresponding changes to the documentation
[ ] Changes generate no new warnings
[ ] Added tests that prove fix is effective or the feature works
[ ] New and existing unit tests pass locally with the changes
[ ] Any dependent changes have been merged and published in downstream modules
[x] Checked the code and corrected any misspellings

Updated


Allow to set terminationCallback without using waitForChildren()/listenForChildren()

@njam Please review. There is a slight change to use EventHandler for handling process events. Not sure about that, as pcnt_singal has this special callback SIG_DFL which I cannot reproduce using EventHandler. Is this good idea or rather revertable?

I think that's a good idea!
What pcntl_signal(<some signal>, SIG_DFL); does is to reset any signal handling (dfl = default). This is needed because child processes "inherit" installed signal handlers from the parent process, so we want to reset that after forking.

ProcessTest: Let's also add a test with sending a TERM signal to the process (instead of triggering an event) - as this is the real-world use case!

Well, my idea was to replace signal handlers with event-handler and then simply unbind when we fork (create new process), but unfortunately tests are failing with that. Seems we need that SIG_DFL - do you know what does it do?

Well, idea is considered "not the best" as it needs to use both models pcntl_handler and event-handler, wdyt @njam?

If you call pcntl_signal(SIGTERM, SIG_DFL); it resets a previously set signal handler, e.g. pcntl_signal(SIGINT, $handler, false);. So _reset() reverts what was done in _installSIgnalHandlers() in the children.
You probably would have the same issue when using an event bus - the child process should unbind from any signal-events that it inherits from the parent?

Hmm, I understand, but that was the problem - unbinding all events still resulted with different behaviour.
I will investigate and paste results in free time.

I looked into the problems I've encountered and seems there is some strange (imo undesired) implementation of the singal handlers.
Once we instantiate process, we installSignalHandlers which are replacing default ones. This means in case of process being killed, it won't execute any code, but silently continue...
I think additionally to binding to events we should throw exception that process has exited.
@njam thoughts?

As discussed:

Let's use eventHandler
Only install signal handlers when needed (event binding?)
Only bind killChildren on fork()

@njam Please take a final look. I am pretty much happy with current implementation.
Wdyt?

CM_Cli_CommandManager::unlockCommand: Can we now make it protected?
CM_ProcessTest: Add a test with binding on exit?
CM_Process: Remove $_terminationCallback
CM_Process::trigger: Don't the $arguments include $event too now?
Cover in tests
CM_Process::fork: What if you fork once, then the child terminates and then you fork again - won't we bind to exit twice then?

I'll try :)
Ok
Ok
Oh, right...
We will. I remeber I thought about unbinding there. But it's not so easy. Should we have some event namespaces? :)

I remeber I thought about unbinding there. But it's not so easy.

How about just a boolean flag to keep track of binding...?

Depends on 1732

@njam Please review

Hmm, but unbinding in _wait() won't catch all cases?
I mean one could _fork(), and then not wait for children (but still have a child exit), in which case the even won't be unbinded and we will end up with two bindings?

Well, that's true we don't really have information when child process exits, unless we use wait.
On the other hand it wil work well, as we did not as unbind and won't bind again as there are forks on the CM_Process.... which is bad, but this in general is bit strange.
I think concept used in CM_Process is two-level, structural way and is getting hard to overview and maintain when processes are nested multiple times. Fork could potentially return some kind of CM_Process instance and use the same bindings.  Parent could listen to those child events. Neverthless we probably don't want to implement it this way as it triggers quite refactoring.

That is true of course!
I'm okay with this approach then!

@njam Ive added unbind also when manually killing children...

makes sense


404 error when attempting to downloading WAC packages with a PowerShell script

I get a 404 error (see screenshot) when attempting to download the WAC extensions for offline installation.
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9a2d369c-6803-46fb-6409-f8b4d3e5d279
Version Independent ID: 663acae0-9203-ac17-d9b4-85abb6d1460e
Content: Install and Manage Extensions
Content Source: WindowsServerDocs/manage/windows-admin-center/configure/using-extensions.md
Product: windows-server
Technology: windows-admin-center
GitHub Login: @daniellee-msft
Microsoft Alias: jol

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


"Process finished with exit code 1" without any other logs in a Spring-boot project

I was trying to configure json logging using this encoder in Spring boot (1.4.2) application, following this post
I added a dependency in pom.xml:
<dependency>
    <groupId>net.logstash.logback</groupId>
    <artifactId>logstash-logback-encoder</artifactId>
    <version>4.7</version>
</dependency>

(tried also with other versions up to 4.11)
and simply after that, I couldn't startup my application, getting: Process finished with exit code 1 without any other logs
After debugging it turned out that there was a mismatch between ch.qos.logback dependencies versions, I solved it by excluding these dependencies in my pom under spring dependencies and added them separately with proper versions below:
<dependencies>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-hateoas</artifactId>
            <version>${spring.boot.version}</version>
            <exclusions>
                <exclusion>
                    <groupId>ch.qos.logback</groupId>
                    <artifactId>logback-core</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>ch.qos.logback</groupId>
                    <artifactId>logback-classic</artifactId>
                </exclusion>
            </exclusions>
        </dependency>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-batch</artifactId>
            <version>${spring.boot.version}</version>
            <exclusions>
                <exclusion>
                    <groupId>ch.qos.logback</groupId>
                    <artifactId>logback-core</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>ch.qos.logback</groupId>
                    <artifactId>logback-classic</artifactId>
                </exclusion>
            </exclusions>
        </dependency>
        <dependency>
            <groupId>ch.qos.logback</groupId>
            <artifactId>logback-core</artifactId>
            <version>1.2.3</version>
        </dependency>
        <dependency>
            <groupId>ch.qos.logback</groupId>
            <artifactId>logback-classic</artifactId>
            <version>1.2.3</version>
        </dependency>
        <dependency>
            <groupId>ch.qos.logback</groupId>
            <artifactId>logback-access</artifactId>
            <version>1.2.3</version>
        </dependency>
        <dependency>
            <groupId>net.logstash.logback</groupId>
            <artifactId>logstash-logback-encoder</artifactId>
            <version>4.11</version>
        </dependency>
</dependencies>

I suppose it's not a solvable issue here, but I'm creating it in case someone has the same problem. Maybe it's worth to mention it in readme or somewhere in docs.

Good idea.  Done.
Recommend using dependencyManagement versus exclude and include.


Add DNS failure and response timeout filter methods

This PR adds two new lifecycle filters for error scenarios:

proxyToServerResolutionFailed(String hostAndPort) -- called when DNS resolution fails
serverToProxyResponseTimedOut() -- called when the proxy-to-server connection goes idle before the response is received

We already have an existing filter method for connection failure: proxyToServerConnectionFailed(). This PR also fixes a defect with that error condition where the proxyToServerRequest(...) method would be called even when the connection failed because the proxy was writing an EmptyLastHttpContent after a connection failure. (The unit test in HttpFilterTest#testConnectionFailedCalledAfterConnectionFailure() demonstrates the failure when executed against the current code in master.)

This looks good to merge to me @jekh. Any reason not to on your end?

Thanks, @adamfisk. If everybody else is happy with it, I'm happy with it!

I'll go ahead and merge this, since it's been reviewed and there are no outstanding concerns.


Delaunay3D is failing triangulation for some rooms

I can't wrap my head around this, but Triangulate() method is sometimes failing thus leaving stray, unconnected rooms

I kind of could go around this with removing the check for AlmostEqual for all triangles

Hi, I also had this issue when using the library. I believe it's related to the variation in room y position being much smaller than the variation in x and z. I found a somewhat hacky solution which was to add an extra vertex at a high position (i.e if your grid is 64x5x64, add a vertex at 32, 64, 32) so that the bounding box for all the vertices used to triangulate roughly forms a cube. You can then ignore any edges leading to that vertex.

Damn @samuelbigos, nice trick, I will give it a try!

This is because the 3D triangulation requires a lot of rooms to be on different levels. If the rooms are mostly on the same level, either from having a small height variance, or from having a small number of rooms.
The solution @samuelbigos gives is probably the best way to deal with this if you need it to be 3D. Otherwise you could use the 2D generation code and just make a single room that is 2 levels tall.

This helped with the generation, thanks guys!

How did you implement this fix to solve this situation? I am having trouble doing so.
You can replicate the issue by using seed 977, it will give you a stray room.
I added the following code to my Triangulate function:
var newHelperPos = new Vector3(size.x / 2f, size.y * 12.8f, size.z / 2f);  var newHelperPosInt = new Vector3Int((int)newHelperPos.x, (int)newHelperPos.y, (int)newHelperPos.z);  vertices.Add(new Vertex<Room>(newHelperPosInt, new Room(newHelperPosInt, new Vector3Int(1, 1, 1))));
The 12.8 was simply the amount @samuelbigos pointed out between the grid's y and the vertex's y.

@Snow-Okami I ended up using a more robust solution of putting additional vertices at all 8 corners of a cube encasing my original grid (i.e. take the largest dimension in your grid and form a cube with sides of that length). Then as before just ignore edges leading to those 8 vertices. I haven't encountered stray rooms again using this approach.


project id required

Hi there,
I have deployed my contract and yarn start in the frontend. But when I try to mint nft, I get the following error:
Unhandled Rejection (HTTPError): project id required
Stack frame: https://i.imgur.com/wyCm1zK.png
How do I fix this?

Your image link is not working, try uploading using this vvvv below.

This error usually arises when infura ID is invalid or you don't change the infura ID on both hardhat,config.js and constants,js

Yes, update the Infura ID and alchemy key

@christopheragnus I believe this is due to the IPFS changes when calling api you need auth from infura project id. See here https://github.com/scaffold-eth/scaffold-eth-challenges/tree/challenge-0-simple-nft the code has been updated to accommodate these changes.

closing this


Design Notes

This is an overview of the architecture of the raft library. Familiarity with the Raft Consensus Algorithm is assumed.
From a user perspective, there are three fundamental components of the raft library: the StateMachine, the Server, and the Client. Subsequent sections will detail these components individually, and their interactions.
StateMachine
StateMachine is a Rust trait, which users of the raft library must provide. A StateMachine is a single instance of a distributed application. It is the raft libraries responsibility to take commands from the Client and apply them to each StateMachine instance in a globally consistent order.
The StateMachine is interface is intentionally generic so that any distributed application needing consistent state can be built on it.  For instance, a distributed hash table application could implement StateMachine, with commands corresponding to insert, and remove. The raft library would guarantee that the same order of insert and remove commands would be seen by all replicas.
Server
Server is a Rust type which is responsible for coordinating with other remote Server instances, responding to commands from the Client, and applying commands to a local StateMachine replica. A Server may be a Leader, Follower, or Candidate at any given time as described by the Raft Consensus Algorithm.
Internals
In order to implement the Raft Protocol, the Server must respond to events (messages from other Server or Client instances, as well as timeouts) in highly context-dependent ways. We found while trying to implement the Server that mixing Raft Protocol logic with network logic led to incomprehensible and unmaintainable code. Accordingly, we decomposed the problem into an inner Replica type which is responsible for the Raft Protocol logic, which left the Server only responsible for receiving and dispatching events.
Replica Implementation
The Replica is a state-machine (not to be confused with the StateMachine trait) which implements the logic of the Raft Protocol. A Replica receives events from the local Server.  The set of possible events is specified by the Raft Protocol:
Event = AppendEntriesRequest | AppendEntriesResponse
      | RequestVoteRequest | RequestVoteResponse
      | ElectionTimeout | HeartbeatTimeout
      | ClientCommand

In response to receiving an event, the Replica may mutate its own state, apply a command to the local StateMachine, or return an event to be sent to one or more remote Server or Client instances.
Server Implementation
The Server is responsible for receiving events from remote Server or Client instances, as well as setting election and heartbeat timeouts.  When an event is received, it is applied to the local Replica. The Replica may optionally return a new event which must be dispatched to either the Server or Client which sent the original event, or to all Server instances.
Because messages are passed asyncronously between Server instances, a Server could get into a situation where multiple events are ready to be dispatched to a single remote Server. In this situation, the Server will replace the existing event with the new event, except in one special circumstance: if the new and existing messages are both AppendEntryRequests with the same term, then the new message will be dropped.
Client
The Client allows users of the raft library to connect to remote Server instances and issue commands to be applied to the StateMachine.

existing event type
new event type
action

AppendEntriesRequest
AppendEntriesRequest
drop the new event

AppendEntriesRequest
AppendEntriesResponse
drop the existing event

AppendEntriesRequest
RequestVoteRequest
drop the existing event

AppendEntriesRequest
RequestVoteResponse
drop the existing event*

AppendEntriesResponse
AppendEntriesRequest
drop the existing event

AppendEntriesResponse
AppendEntriesResponse
drop the existing event

AppendEntriesResponse
RequestVoteRequest
drop the existing event

AppendEntriesResponse
RequestVoteResponse
drop the existing event

RequestVoteRequest
AppendEntriesRequest
drop the existing event

RequestVoteRequest
AppendEntriesResponse
drop the existing event

RequestVoteRequest
RequestVoteRequest
drop the existing event

RequestVoteRequest
RequestVoteResponse
drop the existing event*

RequestVoteResponse
AppendEntriesRequest
drop the existing event

RequestVoteResponse
AppendEntriesResponse
drop the existing event

RequestVoteResponse
RequestVoteRequest
drop the existing event

RequestVoteResponse
RequestVoteResponse
drop the existing event

oops

This looks good to me and is accurate according to our discussions.

What's the mechanism for preventing a server which thinks it is in leaderstate from serving stale replicas? I think diego recommends disabling the rpc if a heartbeat hasn't been heard in some time. Of course there's always quorum reads (but then why use raft at all)

Disabling RPC as in not responding at all?

@posix4e: the only way to ensure that a read is not stale is to 1) serve it from a master, 2) have the master delay responding to the request until after the next successful append-entries event.  This (short of some optimizations which don't fundamentally change the situation) is the only way to guarantee a non-stale read, since raft allows multiple concurrent masters.  This is, incidentally, what Aphyr's Call Me Maybe Analysis revealed as weaknesses in some raft implementations.  This raft implementation does not properly support this right now.

Right! Leaders are only unique per term
On Wed, May 20, 2015 at 10:19 PM, Dan Burkert<EMAIL_ADDRESS>wrote:

@posix4e https://github.com/posix4e: the only way to ensure that a read
is not stale is to 1) serve it from a master, 2) have the master delay
responding to the request until after the next successful append-entries
event. This (short of some optimizations which don't fundamentally change
the situation) is the only way to guarantee a non-stale read, since raft
allows multiple concurrent masters. This is, incidentally, what Aphyr's
Call Me Maybe Analysis revealed as weaknesses in some raft implementations.
This raft implementation does not properly support this right now.
—
Reply to this email directly or view it on GitHub
https://github.com/Hoverbear/raft/issues/24#issuecomment-104140039.

That sounds great! Any plans for compaction?

@posix4e With this new architecture that is definitely in the cards. We haven't implemented it yet but because of how we abstract the log it will be something consuming applications can implement.

I pulled some of these comments into the source with 81c4817036014ae0b7743c6d2449e80dc830184e. @danburkert Should we close this?

Sounds good to me.


Bump 0.1.36

Pull Request Test Coverage Report for Build 1791

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

Totals

Change from base Build 2093:
0.0%

Covered Lines:
3999

Relevant Lines:
4630

💛  - Coveralls


Nuxt not building due to upstream @babel/preset-env change

Versions

nuxt: 2.15.1
node: 15.0.1

Reproduction
Make a new project and try to build it.
Steps to reproduce
See above
What is Expected?
It should build and show the welcome page.
What is actually happening?
The build fails with the error log.
This is caused by upstream package @babel/preset-env. Starting from version 7.12.17 which is the current minimum version, the utils.js file no longer exists.
To fix this, Nuxt would either need to upgrade to support or lock the package version to 7.12.16. I've done this on my local package.
 ERROR  in ./.nuxt/client.js                                                                                friendly-errors 17:55:29

Module build failed (from ./node_modules/babel-loader/lib/index.js):                                                                                friendly-errors 17:55:29
Error: /Users/tj/Development/my.springs/.nuxt/client.js: Cannot find module '@babel/preset-env/lib/utils'
Require stack:
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>- /Users/tj/Development/my.springs/node_modules/babel-loader/lib/index.js
- /Users/tj/Development/my.springs/node_modules/loader-runner/lib/loadLoader.js
- /Users/tj/Development/my.springs/node_modules/loader-runner/lib/LoaderRunner.js
- /Users/tj/Development/my.springs/node_modules/webpack/lib/NormalModule.js
- /Users/tj/Development/my.springs/node_modules/webpack/lib/NormalModuleFactory.js
- /Users/tj/Development/my.springs/node_modules/webpack/lib/Compiler.js
- /Users/tj/Development/my.springs/node_modules/webpack/lib/webpack.js
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>- /Users/tj/Development/my.springs/index.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:900:15)
    at Function.Module._load (node:internal/modules/cjs/loader:745:27)
    at Module.require (node:internal/modules/cjs/loader:972:19)
    at n (/Users/tj/Development/my.springs/node_modules/jiti/dist/v8cache.js:2:2364)
    at PluginPass.Program (/Users/tj/Development/my.springs/node_modules/@nuxt/babel-preset-app/src/polyfills-plugin.js:15:34)
    at newFn (/Users/tj/Development/my.springs/node_modules/@babel/traverse/lib/visitors.js:175:21)
    at NodePath._call (/Users/tj/Development/my.springs/node_modules/@babel/traverse/lib/path/context.js:55:20)
    at NodePath.call (/Users/tj/Development/my.springs/node_modules/@babel/traverse/lib/path/context.js:42:17)
    at NodePath.visit (/Users/tj/Development/my.springs/node_modules/@babel/traverse/lib/path/context.js:92:31)
    at TraversalContext.visitQueue (/Users/tj/Development/my.springs/node_modules/@babel/traverse/lib/context.js:116:16)
    at TraversalContext.visitSingle (/Users/tj/Development/my.springs/node_modules/@babel/traverse/lib/context.js:85:19)
    at TraversalContext.visit (/Users/tj/Development/my.springs/node_modules/@babel/traverse/lib/context.js:144:19)
    at Function.traverse.node (/Users/tj/Development/my.springs/node_modules/@babel/traverse/lib/index.js:82:17)
    at traverse (/Users/tj/Development/my.springs/node_modules/@babel/traverse/lib/index.js:62:12)
    at transformFile (/Users/tj/Development/my.springs/node_modules/@babel/core/lib/transformation/index.js:107:29)
    at transformFile.next (<anonymous>)
                                                                                friendly-errors 17:55:29
 @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js
                                                                                friendly-errors 17:55:29

I've reported this issue to the Babel team: https://github.com/babel/babel/issues/12856

the same for me

Any workaround at the moment?

Workaround is to pin @babel/preset-env to version 7.12.17 in the yarn.lock file using resolutions.

Workaround is to pin @babel/preset-env to version 7.12.17 in the yarn.lock file using resolutions.

Doesn't work either

Worked for me:
  "resolutions": {
    "@babel/preset-env": "7.12.17"
  }

Is there a workaround for people using npm instead of yarn?

@thederekkaplan npm doesn't support natively, but you can check this package

@tkrause
Delete initialization   uninstall @babel/preset-env    install specified version<EMAIL_ADDRESS>

@thederekkaplan , I found the answer here by hzoo.

Following

Worked from me:
Add this on devDependencies:
"@babel/preset-env": "7.12.17"

Install corejs@3
yarn add --dev core-js@3 @babel/runtime-corejs3

and update build.babel in nuxt.config.js
babel: {
        presets() {
          return [
            [
              '@nuxt/babel-preset-app',
              {
                corejs: {
                  version: 3,
                },
              },
            ],
          ];
        },

Worked from me:
Add this on devDependencies:
"@babel/preset-env": "7.12.17"

or

Workaround is to pin @babel/preset-env to version 7.12.17 in the yarn.lock file using resolutions.

Install corejs@3
yarn add --dev core-js@3 @babel/runtime-corejs3

and update build.babel in nuxt.config.js
babel: {
        presets() {
          return [
            [
              '@nuxt/babel-preset-app',
              {
                corejs: {
                  version: 3,
                },
              },
            ],
          ];
        },

yes it works for me 👍

Thanks for report. Issue is solved in 2.15.2 by pinning @babel-preset/env to ~7.12 until properly upgrading.

If for any reason cannot upgrade to 2.15, you can use resolutions field in package.json (requires using yarnpkg):
  "resolutions": {
    "@babel/preset-env": "~7.12.17"
  }

If using npm, should additionally use npm-force-resolutions
"scripts": {
  "preinstall": "npx npm-force-resolutions"
}

Following

FYI, you can just press the subscribe button on the right side, no need to comment ;)

@thederekkaplan , I found the answer here by hzoo.
Basically have your dependencies look like this
"dependencies": { "core-js": "^3.8.3", "nuxt": "^2.14.12", **"@babel/preset-env": "~7.12.0"** },
it should do the trick.

now only this one is working for me, I am using cnpm without yarn nor npm..

https://stackoverflow.com/questions/66325582/nuxt-js-cannot-find-module-babel-preset-env-lib-utils/66364437#66364437
You can try to do：
// package.json
"devDependencies": {

"@babel/preset-env": "7.12.17",
"cross-env": "^5.2.0",
"css-loader": "^3.2.0",
"node-sass": "^4.14.1",

"sass-loader": "^8.0.2",
"style-loader": "^1.0.0"

},
// package-lock.json
"@babel/preset-env": {
+"version": "7.12.17",
...,
"@nuxt/babel-preset-app": {
"requires": {
"@babel/preset-env": "7.12.17",
...
}
}
}

Thanks for report. Issue is solved in 2.15.2 by pinning @babel-preset/env to ~7.12 until properly upgrading.
If for any reason cannot upgrade to 2.15, you can use resolutions field in package.json (requires using yarnpkg):
  "resolutions": {
    "@babel/preset-env": "~7.12.17"
  }

If using npm, should additionally use npm-force-resolutions
"scripts": {
  "preinstall": "npx npm-force-resolutions"
}

Works for me! :)
Tks.

Just to clarify status of this issue it is fixed in latest versions of both preset-env and nuxt. So it is recommended to recreate-lock file and avoid pinning to 7.12

Thank you all.
I may be still astray, shouldn't this https://github.com/nuxt/nuxt.js/commit/173f48b20eaa448cb1f6d09ca5d45e41d1475baf be reverted? @nuxt/babel-preset-app keeps requiring @babel/preset-env~7.12.17

@n1ngu It is reverted by 931d1cf89e033bd9e7637110d71b107d9481d251 :)

you can run this comment for this issue
yarn add @babel/plugin-proposal-private-property-in-object --dev

在欢乐时，朋友们会认识我们；在患难时，我们会认识朋友。谢谢，来信！！！