Added xDnsClientGlobalSetting Resource - Fixes #111

This adds support for setting the DNS client global suffix search list (and devolution level) as per #111.

This change is

@tysonjhayes  - any chance I could get you to do a code review for me? :smile:

Reviewed 7 of 8 files at r1, 3 of 3 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Tests/Integration/MSFT_xDnsClientGlobalSetting.Integration.Tests.ps1, line 21 [r2] (raw file):

# Backup the existing settings
$CurrentDnsClientGlobalSetting = Get-DnsClientGlobalSetting

Shouldn't we move this into the try catch so if this or the set fails we try to roll back?

Comments from Reviewable

Review status: 9 of 10 files reviewed at latest revision, 1 unresolved discussion.

Tests/Integration/MSFT_xDnsClientGlobalSetting.Integration.Tests.ps1, line 21 [r2] (raw file):
Previously, tysonjhayes (Tyson J. Hayes) wrote…
> Shouldn't we move this into the try catch so if this or the set fails we try to roll back?

Good catch as always sir! Cheers! Fixed.

Comments from Reviewable

Review status: 9 of 10 files reviewed at latest revision, 1 unresolved discussion.

Tests/Integration/MSFT_xDnsClientGlobalSetting.Integration.Tests.ps1, line 21 [r2] (raw file):
Previously, PlagueHO (Daniel Scott-Raynsford) wrote…
> Good catch as always sir! Cheers! Fixed.

Done.

Comments from Reviewable

Reviewed 1 of 1 files at r3.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Call user's on_show method before card is actually shown.

Awesome use of copy and pasting there... :smile:


Fails to render the "⊥" symbol

Bug Report
I am trying to render some Math symbols with pdfkit but for some reason the .text() function fails to render the ⊥ symbol.
Description of the problem
I use the corresponding hexcode (\u22A5) for the ⊥ symbol but pdfkit renders it as an error/fail symbol (looks like a rectangle with a cross in it).
Code sample

const PDFDocument = require("pdfkit");
var doc = new PDFDocument();
doc.text(`\u22A5`);

Your environment

pdfkit version: ^0.11.0
Node version: v8.17.0
Browser version (if applicable):
Operating System: macOS Catalina, 10.15.4

you should use a font that support that character

Changing font fixed it.


Possibile addition to https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3548

Related to https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3548 probably it would be a good idea, to abandon the "404 Hosts" and incorporating it in "Redirection Hosts" with the possibility specifying return codes 4XX and 5XX and custom pages for the 4XX and 5XX errors in form of some simple html snippets.

Nobody interested...?


AwsLambdaIntegration and Scope?

When using this SDK with the AwsLambdaIntegration, the SDK is performing some sort of magic to create scope on the lambda handlers. The question is, with that, is there a global method to add tags to the current scope, or do I need to create a new scope? The documentation isn't exactly clear. It seems like I should be able to do it without creating a separate scope, but I'm not sure how.

Please refer to https://docs.sentry.io/enriching-error-data/context/?platform=python#tagging-events
You do not have to create another scope, you have to mutate the existing one


Prepare for release

Packages impacted by this PR
@azure-rest/core-client
@azure-rest/purview-catalog
@azure/data-tables
Issues associated with this PR
N/A
Describe the problem that is addressed by this PR
Update Changelog to prepare for release
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
N/A
Are there test cases added in this PR? (If not, why?)
N/A
Provide a list of related PRs (if any)
N/A
Command used to generate this PR:**(Applicable only to SDK release request PRs)
N/A

API change check for @azure/data-tables
API changes are not detected in this pull request for @azure/data-tables

API change check for @azure-rest/purview-catalog
API changes are not detected in this pull request for @azure-rest/purview-catalog

API change check for @azure-rest/core-client
API changes are not detected in this pull request for @azure-rest/core-client


Switch to a extension function , LiveData.observe

GardenFragment and PlantListFragment import androidx.lifecycle.observe

@googlebot I signed it!

Thank you for the PR!

Thank you for the PR!


Drop ProxyMan support for applications using http_proxy environment variable

The major motivation behind creating ProxyMan was handling the cases when applications were not able to function properly, primarily due to

Not using http_proxy environment variable.
Not being launched from shell, so variables are set.
Not using system's proxy settings (depending on OS).

However, as of now, almost all tools like git, npm, yarn (#46 ), bower (#40 ), maven (#47 ), etc. work well with http_proxy, the need to configure them manually becomes insignificant. There's just one kind of use case where you'd require a different proxy for git and http_proxy, which is a very rare use-case.
I would like to have feedback on if there shall be cleanup in ProxyMan to expect applications to pick up http_proxy as most of them do.
https://github.com/himanshub16/ProxyMan/tree/v3#how-this-is-going-to-be-different-from-v2

sounds good!
or maybe we can just change Labels of the menu. eg git to git specific


typo: aligned Docs with deno-fresh-demo convention.

Figured it'd make sense to be consistent.

Where are these other mentions? Couldn't find them in the docs.

Try searching my-project. The file paths that include this are:

[ ] /www/routes/index.tsx
[ ] /www/routes/update.tsx


Propose to include a Changelog file

It is nice to have a Changelog file since there are many tags. And it will be easy for other developers to track the changes.

Definitely something we'll be doing post-1.0

we have a changelog in docs/Changelog.md since 2.0 alpha releases now.


WIP LUMI to 'Applications by availability'

https://csc-guide-preview.rahtiapp.fi/origin/apps-lumi/apps/by_system/
TODO:

Add missing system description for LUMI into system_desc variable of scripts/generate_by_system.sh

Suggestion for LUMI description: EuroHPC supercomputer for CPU and, especially, GPU jobs


add optional reconciliation id to the payload

Cybersource will generate reconciliation id and pass it to gateways and also put it in the response to upstream.
Then this reconciliation id will be present in later statements from bank side, and allow us link the records in the statements to the original transactions.
However, if the transaction failed, there is no reconciliation in the response payload. And have confirmed with Cybersource team, they won't provide this number in the response for failed transactions.
This causes a problem when we need to do analysis on the auth failures (want to know the reason of failures)
Thus, Cybersource team provides another workaround that this reconciliation actually can either generate by Cybersource or we can pass it as request payload to them.
So, I'm going to make the code changes here to allow upstream passing reconciliation_id to Cybersource plugin and pass this id in the request payload to Cybersource.
@pierre @sbrossie any suggestion or concern on this? thanks!

Sounds good, can you prepare a PR for review?

thanks! sure, will do that.

@unieagle I am unable to release the plugin due to failing tests, could you take a look?
https://travis-ci.org/killbill/killbill-cybersource-plugin/builds/268267074
Failures:
  1) Killbill::Cybersource::PaymentPlugin with reconciliation id successful transactions should send passedin reconciliation id to Cybersource
     Failure/Error: gw_response.params_reconciliation_id.should == '1F16A6C017F12C15'
       expected: "1F16A6C017F12C15"
            got: "78591468H6QMUEVQ" (using ==)
     # ./spec/cybersource/remote/integration_spec.rb:794:in `(root)'

sure, checking.. strange, it all passed before i push final code changes.

oh, just remembered, i met this error the first time. there is a switch in the back office of cybersource with the testing account. I asked the cybersource contact to enable it for my testing account, then Cybersource will read the reconciliationID in the payload. other wise it will ignore this value.
How can we fix this?

I see -- I've disabled the test for CI purposes (8f25964b27b76b7e37e2c27f9c8dbddcadcd6151).
Thanks!


No results have been reported less of an eyesore.

OLD:

NEW:

Based off of this to keep consistency:

With padding now:

@qwertyquerty Thanks!
Merged 🚀


Synchronize swagger definition with implementation

Right now the swagger.yaml definition is used for documentation purpose and service discovery (twintip) only. The actual implementation of the rest service is not created from it. The problem with this is, that the implementation can run out of sync with the swagger definition. The JAX-RS implementation should be created from the swagger.yaml with an automated process integrated into the maven build.

fixed with this commit


Support Compiling TypeScript with --declaration Flag

Description
Fixes #27
As much as I'd prefer to keep a single file for all code, this feels like a better trade-off than exporting types I don't want to make publicly available…
Weirdly this seems to fix a common issue when creating libraries dependent on cva 🤷
Additional context
cc @brattonross

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Follow the Style Guide.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).

Really appreciate you supporting this, will give it a try when I can, thanks again! 🙏

No worries! Let me know how you get on 🤞


Add description for rendering/limits/spatial_indexer/threaded_cull_minimum_instances

Adds a description for the property rendering/limits/spatial_indexer/threaded_cull_minimum_instances based on my reading of its use in renderer_scene_cull.cpp.
Accessing:
https://github.com/godotengine/godot/blob/2d0ee20ff30461b6b10f6fdfba87511a0ebc6642/servers/rendering/renderer_scene_cull.cpp#L4164
Using:
https://github.com/godotengine/godot/blob/2d0ee20ff30461b6b10f6fdfba87511a0ebc6642/servers/rendering/renderer_scene_cull.cpp#L3028-L3033
https://github.com/godotengine/godot/blob/2d0ee20ff30461b6b10f6fdfba87511a0ebc6642/servers/rendering/renderer_scene_cull.cpp#L3129-L3145

Thanks!

Cherry-picked for 4.2.2.

Cherry-picked for 4.1.4.


License text in LICENSE file

This should help various automated tools such as licensee recognize the license. Licensee is used, among other things, for the GitHub API.

:+1:


.fresh config run_args incompatible with space-separated args passed with Go's flag.Func

example:
flag.Func("trusted origins", "Trusted CORS origins",
		func(val string) error {
			trustedOrigins = strings.Fields(val)
			return nil
		})

and in my .fresh.yaml:
run_args: "--cors-trusted-origins http://localhost:9000 http://localhost:9001"

But only the first arg is received.

@adamwoolhether I'm wondering if you would be willing to test this patch
go install github.com/zzwx/fresh@1485bd8852cef70b70b63411df388afccf1502bd

Keeping it open while testing

Hi @zzwx
Still no success. I've tried placing single quotes around the space-separated args without luck.
For reference, If i'm just using go run: --cors-trusted-origins='http://localhost:9000 http://localhost:9001'
In .fresh.yaml I've tried both:
run_args: "--cors-trusted-origins http://localhost:9000 http://localhost:9001"
and
run_args: "--cors-trusted-origins 'http://localhost:9000 http://localhost:9001'"
and
run_args: '--cors-trusted-origins "http://localhost:9000 http://localhost:9001"'
without success.

What's your environment?

MacOS Darwin 21.3.0 i386
go1.17.6
i should note that, the fresh-runner log output now includes the all the args, but the application's var is only the first flag arg, confirmed with a fmt.Println.
go run works fine.


⚠ Bofrost.de has degraded performance

In 23f5468, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1655 ms

Resolved: Bofrost.de performance has improved in 9d7fac1 after 19 minutes.


Add ThreeFold Connect App in manual

ThreeFold Connect app is not a component in new manual, not up-to-date in wiki :

need info on KYC feature
(support TFT on Substrate to be added once available)
also use TF Connect secret for TFGrid3 ?

I think the manual exists here https://github.com/threefoldfoundation/info_threefold_pub/blob/development/wiki/main/concepts/blockchain/tfconnect.md
i'll move it to the correct repo


new pi 4 and 2023 version

I was not getting pi to connect to my network and did not see picobrew.  I downloaded the 2023 lite version and now I see the picobrew network, but it is still not connecting to my home network even though I did change the ssid and password to my 2.4 network.  Can I can the setup from the picobrew network....if so, how do i sign in ...I am attempting to use Putty
thanx, Peter Curtin<EMAIL_ADDRESS>

Login for the device unless modified in either the initial boot file or post installation is the default username:password combination for raspbian OS.

Likely what is happening is we need to base the image off of the newer raspbian builds that have support for the newer silicon firmware.
I just received my RPi 5 dev device to do additional testing on related to firmware modifications.

Check one of these builds which were one of our together for another individual  https://drive.google.com/drive/folders/1pxt0ivVPzOXRseO6Lk39lHK9z2dJJBu3?usp=drive_link
I haven't had time to test these fully myself.
There will be 4 different ones. 2 will be "lite" (latest and stable - relating to the wifi firmware to use) - these variants are headless meaning no desktop experience, just terminal output
2 will be "full" (same latest and stable) and these will have a more desktop experience included

Thx for quick response…will try
Peter
Sent from Yahoo Mail for iPhone
On Tuesday, January 9, 2024, 3:28 PM, Trevor Mack @.***> wrote:
Check one of these builds which were one of our together for another individual https://drive.google.com/drive/folders/1pxt0ivVPzOXRseO6Lk39lHK9z2dJJBu3?usp=drive_link
I haven't had time to test these fully myself.
There will be 4 different ones. 2 will be "lite" (latest and stable - relating to the wifi firmware to use) - these variants are headless meaning no desktop experience, just terminal output
2 will be "full" (same latest and stable) and these will have a more desktop experience included
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Trevor, I loaded 2023-08-20-picobrew-pico-lite and it worked!!!...I was able to get into the console on my lan using putty....
Now what...Is there a manual I can read for setting up my pico on the picobrew network (which I see on my analyzer) AND is there anything I need to do on the raspberry side to actually setup my brew.  I have one of the plastic bin kits and am now excited again to get started.....
Does this version have a gui interface?  If not, will there be one coming?
I tried to get even this far about a year ago with an old raspberry and failed.
Thanx again for all your help!!!
Peter
On Tuesday, January 9, 2024 at 08:59:09 PM PST, Peter Curtin<EMAIL_ADDRESS>wrote:

Thx for quick response…will try
Peter
Sent from Yahoo Mail for iPhone
On Tuesday, January 9, 2024, 3:28 PM, Trevor Mack @.***> wrote:
Check one of these builds which were one of our together for another individual https://drive.google.com/drive/folders/1pxt0ivVPzOXRseO6Lk39lHK9z2dJJBu3?usp=drive_link
I haven't had time to test these fully myself.
There will be 4 different ones. 2 will be "lite" (latest and stable - relating to the wifi firmware to use) - these variants are headless meaning no desktop experience, just terminal output
2 will be "full" (same latest and stable) and these will have a more desktop experience included
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

The GUI is web based. The Pi hosts a python+flask webserver and uses nginx as a way to provide self signed certificates and run on both http and https depending on the interface used by the Pico device.
https://trevor-mack.com/picobrew-raspberrypi-setup/ has most of the setup instructions as well as the Release Notes on GitHub here.
Basically you connect the Pico device to the PICOBREW network and setup recipe instructions on the web interface defaulted exposed at http://raspberrypi/ (some networks you need to access the IP address of the Pi as some residential routers block local domain resolution by hostname as this can often times be insecure access patterns attempted by attackers.

Progress is being made....I got in using a normal browser and attempted to look at the library...it is empty....how do I load existing recipes?
thanx again for getting me this far....now I have to see if my picobrew which has been sitting for over a year will even work again!!!
Peter
Sent from Yahoo Mail for iPhone
On Saturday, January 13, 2024, 5:33 AM, Trevor Mack @.***> wrote:
The GUI is web based. The Pi hosts a python+flask webserver and uses nginx as a way to provide self signed certificates and run on both http and https depending on the interface used by the Pico device.
https://trevor-mack.com/picobrew-raspberrypi-setup/ has most of the setup instructions as well as the Release Notes on GitHub here.
Basically you connect the Pico device to the PICOBREW network and setup recipe instructions on the web interface defaulted exposed at http://raspberrypi/ (some networks you need to access the IP address of the Pi as some residential routers block local domain resolution by hostname as this can often times be insecure access patterns attempted by attackers.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

There are some sample base style recipes to reference in the help section.
Though as far as the pi experience it was purely developed to be simple and purely to control the Pico device vs craft recipes directly.
I also have a free to use crafter hosted online that is specifically targeting Pico device efficiencies at crafter.pilotbatchbrewing.com that has one way syncing to our rPi solution you can use to populate the machine instructions into the 'recipe library', but for me I typically have 1-2 mash schedules and adhoc set up to the maybe 5-7 hopping schedules making for only 15-18 unique "recipes" that I've used to brew 100s of batches of beer over the years.

so to do the syncing, i have to have my picobrew online?...there is no way to just populate with .xml files(I tried, it fails)
I am visiting my mom, so if I need physical access to pico...will have to wait till I am home
Admission:  Although I was a programmer and can get around.  I loved the pico for its plug and play.  I want to make beer again, but I don't want all the complexities of making up recipes.  I just want to copy and paste and brew!
Peter
On Saturday, January 13, 2024 at 12:37:04 PM PST, Trevor Mack<EMAIL_ADDRESS>wrote:

There are some sample base style recipes to reference in the help section.
Though as far as the pi experience it was purely developed to be simple and purely to control the Pico device vs craft recipes directly.
I also have a free to use crafter hosted online that is specifically targeting Pico device efficiencies at crafter.pilotbatchbrewing.com that has one way syncing to our rPi solution you can use to populate the machine instructions into the 'recipe library', but for me I typically have 1-2 mash schedules and adhoc set up to the maybe 5-7 hopping schedules making for only 15-18 unique "recipes" that I've used to brew 100s of batches of beer over the years.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

The RPi doesn't support importing xml, only the JSON format that the RPi server is built on which isn't a common beer recipe format.
However... My BrewCrafter website linked earlier will import and scale a beerxml for the Pico machines (or should, let me know if you have issues with that).
Then when your desired beerxml is uploaded to BrewCrafter you can sync it to the RPi (needs to be network local to your device browsing BrewCrafter since I use local JavaScript ajax queries to get it over - unless you put your RPi on a public IP address or a VPN tunnel or something of that sort... ).
Really the RPi recipe interface just controls time at temperature of the machine and doesn't care one bit about ingredients... So if you use BrewFather or just source kits, create a new recipe in the RPi interface and set up the "machine instructions" accordingly for the mash and hopping/boil schedule you desire for that session. It really doesn't have to be complicated.
Default new recipe is even good enough for a large number of styles (as long as you change the hop schedule appropriate to what you are brewing).

Trevor,   I have successfully connected my picobrew to the next work and am presently doing g a deep clean.  The pump on the black hose was initial stuck but now is working.  Presently on adjunct 1…adjunct 2, adjunct 3 and 4 …so I think it all works again.   Now to find some grains and hops in Santa Barbara!!
Thx for all your help!!!
Sent from Yahoo Mail for iPhone
On Saturday, January 13, 2024, 7:18 PM, Trevor Mack @.***> wrote:
The RPi doesn't support importing xml, only the JSON format that the RPi server is built on which isn't a common beer recipe format.
However... My BrewCrafter website linked earlier will import and scale a beerxml for the Pico machines (or should, let me know if you have issues with that).
Then when your desired beerxml is uploaded to BrewCrafter you can sync it to the RPi (needs to be network local to your device browsing BrewCrafter since I use local JavaScript ajax queries to get it over - unless you put your RPi on a public IP address or a VPN tunnel or something of that sort... ).
Really the RPi recipe interface just controls time at temperature of the machine and doesn't care one bit about ingredients... So if you use BrewFather or just source kits, create a new recipe in the RPi interface and set up the "machine instructions" accordingly for the mash and hopping/boil schedule you desire for that session. It really doesn't have to be complicated.
Default new recipe is even good enough for a large number of styles (as long as you change the hop schedule appropriate to what you are brewing).
Screenshot_20240113-221643.png (view on web)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Actually adjunct 4 then 3??
Sent from Yahoo Mail for iPhone
On Saturday, January 13, 2024, 7:18 PM, Trevor Mack @.***> wrote:
The RPi doesn't support importing xml, only the JSON format that the RPi server is built on which isn't a common beer recipe format.
However... My BrewCrafter website linked earlier will import and scale a beerxml for the Pico machines (or should, let me know if you have issues with that).
Then when your desired beerxml is uploaded to BrewCrafter you can sync it to the RPi (needs to be network local to your device browsing BrewCrafter since I use local JavaScript ajax queries to get it over - unless you put your RPi on a public IP address or a VPN tunnel or something of that sort... ).
Really the RPi recipe interface just controls time at temperature of the machine and doesn't care one bit about ingredients... So if you use BrewFather or just source kits, create a new recipe in the RPi interface and set up the "machine instructions" accordingly for the mash and hopping/boil schedule you desire for that session. It really doesn't have to be complicated.
Default new recipe is even good enough for a large number of styles (as long as you change the hop schedule appropriate to what you are brewing).
Screenshot_20240113-221643.png (view on web)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Trevor, Not sure if you got my last email...but I finally got around to deep cleaning my pico once it was connect to the PI....I am using your brewcrafter 2, but when I try to sync to the picobrew machine, it does not and I do not have a pico z....just the basic picobrew.
Am I missing something?
Peter
On Saturday, February 3, 2024 at 01:07:34 PM PST, Peter Curtin<EMAIL_ADDRESS>wrote:

Actually adjunct 4 then 3??
Sent from Yahoo Mail for iPhone
On Saturday, January 13, 2024, 7:18 PM, Trevor Mack @.***> wrote:
The RPi doesn't support importing xml, only the JSON format that the RPi server is built on which isn't a common beer recipe format.
However... My BrewCrafter website linked earlier will import and scale a beerxml for the Pico machines (or should, let me know if you have issues with that).
Then when your desired beerxml is uploaded to BrewCrafter you can sync it to the RPi (needs to be network local to your device browsing BrewCrafter since I use local JavaScript ajax queries to get it over - unless you put your RPi on a public IP address or a VPN tunnel or something of that sort... ).
Really the RPi recipe interface just controls time at temperature of the machine and doesn't care one bit about ingredients... So if you use BrewFather or just source kits, create a new recipe in the RPi interface and set up the "machine instructions" accordingly for the mash and hopping/boil schedule you desire for that session. It really doesn't have to be complicated.
Default new recipe is even good enough for a large number of styles (as long as you change the hop schedule appropriate to what you are brewing).
Screenshot_20240113-221643.png (view on web)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Trevor, I made my first post chapter 13 of picobrew beer yesterday....it is a west coast ipa and I just used one of the standard recipes.  Luckily the brewery at the local craft brewery (Draughtsman in Goleta) took pity on my and got me my first ingrediants. Hand cracked the grain, so we will see how that works....
thanx again for all your help...I think I now understand the process....which I never did before....just put in water and the packs and pushed a button.
On Monday, February 5, 2024 at 12:29:02 PM PST, Peter Curtin<EMAIL_ADDRESS>wrote:

Trevor, Not sure if you got my last email...but I finally got around to deep cleaning my pico once it was connect to the PI....I am using your brewcrafter 2, but when I try to sync to the picobrew machine, it does not and I do not have a pico z....just the basic picobrew.
Am I missing something?
Peter
On Saturday, February 3, 2024 at 01:07:34 PM PST, Peter Curtin<EMAIL_ADDRESS>wrote:

Actually adjunct 4 then 3??
Sent from Yahoo Mail for iPhone
On Saturday, January 13, 2024, 7:18 PM, Trevor Mack @.***> wrote:
The RPi doesn't support importing xml, only the JSON format that the RPi server is built on which isn't a common beer recipe format.
However... My BrewCrafter website linked earlier will import and scale a beerxml for the Pico machines (or should, let me know if you have issues with that).
Then when your desired beerxml is uploaded to BrewCrafter you can sync it to the RPi (needs to be network local to your device browsing BrewCrafter since I use local JavaScript ajax queries to get it over - unless you put your RPi on a public IP address or a VPN tunnel or something of that sort... ).
Really the RPi recipe interface just controls time at temperature of the machine and doesn't care one bit about ingredients... So if you use BrewFather or just source kits, create a new recipe in the RPi interface and set up the "machine instructions" accordingly for the mash and hopping/boil schedule you desire for that session. It really doesn't have to be complicated.
Default new recipe is even good enough for a large number of styles (as long as you change the hop schedule appropriate to what you are brewing).
Screenshot_20240113-221643.png (view on web)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Awesome, glad you have cracked the nut.
BrewCrafter2 syncing to RPi only works 1) with the client device (browser) on the same network as the RPi (or at least available to access the FQDN of where the webserver of the RPi is hosted) and 2) if using the out of the box installation as you are, you will need to explicitly accept the "unsecure / self-signed ssl certificates" as trusted to allow your browser to communicate to it form the BrewCrafter2 website.


Implement brewdle upgrade command.

This PR is a work in progress. See discussion on this issue: https://github.com/Homebrew/homebrew-brewdler/issues/37.

Coverage decreased (-13.17%) to 67.71% when pulling 5ab122279aeea3397ac510532ea67de86cb774a1 on AlJohri:upgrade into bd82066af0abd50475decc6e341df423687156fa on Homebrew:master.

FYI some of this is going to conflict with https://github.com/Homebrew/homebrew-brewdler/pull/39

@AlJohri #39 has been merged now, can you rebase against master and fix the conflicts?

@AlJohri any progress on this?

Closing this due to no activity. Feel free to reopen a new PR later!


Csv Writer easier to write Iterable<? extends CharSequence[]>

I have coordinate based inputs which are stored in List<String[]> and it would be great to use them directly with CsvWriter class.

@ryanthara just pushed new version for a List<String[]> the code would look likethat
try(ClosableCsvWriter writer = CsvWriter.dsl().to(file)) {
list.forEach(writter::appendRow);
}
the new CsvWriter is in package org.simpleflatmapper.lightningcsv.CsvWriter, not the same as the one in org.simpleflatmapper.csv

Sounds good.
When will it be available via maven?

it's there
https://repo1.maven.org/maven2/org/simpleflatmapper/lightning-csv/8.1.0/
On Fri, Nov 1, 2019 at 5:11 AM Sebastian<EMAIL_ADDRESS>wrote:

Sounds good.
When will it be available via maven?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/arnaudroger/SimpleFlatMapper/issues/686?email_source=notifications&email_token=ABPAJLMIC6QZGYPMO6AEDUDQRO27HA5CNFSM4JC2MNX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC2AJPI#issuecomment-548668605,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABPAJLN3FKB5VFAMD6GNJUTQRO27HANCNFSM4JC2MNXQ
.

I checked this site here.
Still 8.0.3, but with your link @arnaudroger everything works fine.

I took a look for it at this site.
You are wright @arnaudroger.

That’s a clone of maven central always a bit late.

@arnaudroger
Some addition, maybe for other users too.
try(ClosableCsvWriter writer = CsvWriter.dsl().to(file)) {     list.forEach(writer::appendRow); }
has to be changed to
try (ClosableCsvWriter writer = CsvWriter.dsl().to(path.toFile())) {             csv.forEach(values -> {                 try {                     writer.appendRow(values);                 } catch (IOException e) {                    // do whatever you want                 }             });         } catch (IOException e) {             // do whatever you want         }
You have to try catch every element of the forEach-loop.

you can try also
try(ClosableCsvWriter writer = CsvWriter.dsl().to(file)) {
    list.forEach(CheckedConsumer.toConsumer(writer::appendRow));
}

that should work

@arnaudroger +1
Works like a charm.


Fix restrax small bug in warning module

AttributeError: 'ReStrax' object has no attribute 'warning'

coverage: 91.27% (-0.06%) from 91.328%
when pulling c11b7af261c820463d9cd9947eab73a6765dd2a9 on restrax-warning-bug-fix
into 2075e4a2d73bbeec9a065a6d86802d151c04faa1 on master.

Was already fixed in https://github.com/XENONnT/straxen/pull/1402/files


resolve #64 - Pull columns out. Implement subqueries in update

Pull columns out from sqlite folder
Implements subqueries in update statement
Implement clone on column

LGTM. Thanks Chase!


Fix issue #114 (ChainKey is not saved at the end of Frost keygen)

@adr1anh any chance this could get a look? It looks like a bug/omission. The property is there on the config object and is mysteriously left untouched.


CLI Crash

🐞 Bug report
Command (mark with an x)

- [ ] new
- [x] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Description
Angular cli runs the project for first to times and it compiled successfully. The third time it throws the followning error code in the terminal. Assertion !(n > 0) || (ret != nullptr)' failed.` Not able to continue the compilation process. It happened multiple times.
🔥 Exception or Error
Assertion `!(n > 0) || (ret != nullptr)' failed.

@santhoshnv Hi, can you please fill the issue template to get help https://github.com/angular/angular-cli/blob/master/CONTRIBUTING.md#submit-issue

Thanks for reporting this issue. However, you didn't provide sufficient information for us to understand and reproduce the problem. Please check out our submission guidelines to understand why we can't act on issues that are lacking important information.
If the problem persists, please file a new issue and ensure you provide all of the required information when filling out the issue template.


deploy seems to put state file in the wrong place

I ran the following command:
± |master S:3 ✗| → bbl \
--aws-access-key-id=$(cat ~/workspace/deployments-rmd/bbl-concourse/aws_access_key_id) \
--aws-secret-access-key=$(cat ~/workspace/deployments-rmd/bbl-concourse/aws_secret_access_key) \
--state-dir="~/workspace/deployments-rmd/bbl-concourse/state" \
--aws-region=us-east-1 \
unsupported-deploy-bosh-on-aws-for-concourse

and received the following error:

step: generating cloud config
step: applying cloud config

open ~/workspace/deployments-rmd/bbl-concourse/state/state.json: no such file or directory

Taking a look at what is on the filesystem, it seemed the --state-dir was not respected, and put the file in the wrong place, meaning it couldn't find it later:
 2016-04-08 19:44:41 ☆ ruby 2.1.8p440 rmd-macbook in ~/workspace/deployments-rmd
± |master S:3 ✗| → gst
On branch master
Your branch is up-to-date with 'origin/master'.
Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)

	new file:   bbl-concourse/aws_access_key_id
	new file:   bbl-concourse/aws_secret_access_key
	new file:   state.json

Running the command without the --state-dir flag seemed to succeed.

@robdimsdale the problem is that you passed in a literal ~ in your path, and that directory doesn't exist. I've added a fast fail check https://github.com/pivotal-cf-experimental/bosh-bootloader/commit/e7c67dd3f8f9be5df6ea7ff1a26a844d18f5620d for a state-dir which doesn't exist.
Thanks for reporting the issue!

Ah, right, because the ~ was inside quotes, so the shell doesn't expand it, and the literal ~ is passed to bbl.
Thanks for adding the fast-fail. I think that would have helped in my case.


allow custom colors props for Radar.js

@skanderbm could you squash these commit down into 1 commit


eas build error: "ExpoAppStaging" requires a provisioning profile. Select a provisioning profile in the Signing & Capabilities editor

Summary
Hey team, I get this error when trying to run the command below. Any idea how to resolve this because it seems like my provisioning profile and certificate match.

Command
eas build --platform ios --profile development --local
eas.json file
{
  "cli": {
    "appVersionSource": "local"
  },
  "build": {
    "development": {
      "credentialsSource": "local",
      "android": {
        "buildType": "apk"
      },
      "ios": {
        "buildConfiguration": "release"
      }
    }
}

Note:

I have not logged into my apple account cause it hasn't prompted me.
I also can't log in due to having a federated account when just running eas build without any flags

Managed or bare?
Managed
Environment
expo-env-info 1.2.0 environment info:
System:
OS: macOS 14.6.1
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 18.18.0 - ~/.nvm/versions/node/v18.18.0/bin/node
Yarn: 1.22.22 - ~/.nvm/versions/node/v18.18.0/bin/yarn
npm: 9.8.1 - ~/.nvm/versions/node/v18.18.0/bin/npm
Managers:
CocoaPods: 1.15.2 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 23.5, iOS 17.5, macOS 14.5, tvOS 17.5, visionOS 1.2, watchOS 10.5
IDEs:
Android Studio: 2024.2 AI-242.21829.142.2421.12409432
Xcode: 15.4/15F31d - /usr/bin/xcodebuild
npmPackages:
expo: ~51.0.37 => 51.0.37
expo-router: ~3.5.23 => 3.5.23
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.74.5 => 0.74.5
react-native-web: ~0.19.10 => 0.19.12
npmGlobalPackages:
eas-cli: 12.5.1
Expo Workflow: managed
Error output
error: "NAMEOFAPP" requires a provisioning profile. Select a provisioning profile in the Signing & Capabilities editor. (in target 'NAMEOFAPP' from project 'NAMEOFAPP')
Reproducible demo or steps to reproduce from a blank project

Create expo project
Configure eas.json and use local credentials
Run eas build --platform ios --profile development --local

Hi,
Can you check if the bundle ID for which the profile was generated matches the bundle ID of the app you want to build? This can sometimes get out of sync if you use env vars to set your bundle ID and some of them are present in the build process other then ones used in EAS CLI.

Hi,
Can you check if the bundle ID for which the profile was generated matches the bundle ID of the app you want to build? This can sometimes get out of sync if you use env vars to set your bundle ID and some of them are present in the build process other then ones used in EAS CLI.

yeap it matches!

Nvm that worked thank you 😅


Tracing API Operations

Can we attach a UUID to each API operation so that tracing it becomes easier among the massive amounts of logs in servers/controllers? This would make tracing that operation very easy, compared to how it is right now. This would entail putting a UUID to the MDC and transferring it across threads and configuring log4j to log the key with every statement.
(There must be some reason to why this isn't being done right now which, if true, I am not aware of). Thanks!

I think this is especially useful for query request, where we can easily associate the log to the query. Broker id + query id can be used for such purpose


Update README.md

I believe there was a typo in the documented firmware update command.

thanks! Right, better with the right command.


Bug in API ? Need help ?

I am not sure if it's a bug or implementation error by our team, but we get the following API error response on production. It's very inconsistent. Does anyone else get a similar error?
{
  "error": {
    "message": "Error while communicating with one of our backends.  Sorry about that!  We have been notified of the problem.  If you have any questions, we can help at https://support.stripe.com/.",
    "type": "api_error"
  }
}

Hi! We're looking into this. Can you give me more context on this problem here? Specifically, what calls or tasks are you making? Also are you noticing these errors on the Dashboard or somewhere else? What is being affected here?

Hi,
We mostly tested it manually on test/production accounts. The Stripe dashboard sometimes fails to load or times out the app. It is usually 500 error.
I do have additional data. Is it possible to share that via email? I have some screenshots that I can share via email, but not publicly.
Regards

Hi @karmapandya
Send us an email at<EMAIL_ADDRESS>and we will take a look.

@auchenberg-stripe I have sent an email. thank you

Closing as this issue has been resolved


reading nifti files

Do this library support reading nifti (nii.gz) files?
I tried just like tutorial for dicom files but got the error of this issue.

Try calling load with parameter fmt = 'nii'. Our load function uses nibabel library to load nifti images to arrays, so you need to install it too.


Southeast Asia region naming inconsistency

We are fetching the regions with Java SDK where Southeast Asia is returned as
"South East Asia".
In the meantime we are using Azure CLI  (v2.0.26) as well, which returns the region name "Southeast Asia":

The two does not match, causing error in our application.

hi @xccc-msft could you pls confirm this is service issue? or Azure CLI did some normalization. thanks.

@pdarvasi This is the label set from SDK. The value we send to server is southeastasia, which is the same as Azure CLI.

@pdarvasi You should be able to get same value southeastasia if you select the name of regions both Java and Azure CLI. Please feel free to reopen if you still have any questions.


Bug with contact update

When a bbw user makes a payment to another bbl user with their username, the contact gets saved for both parties. However, when a bbw user generates a btc lightning invoice and another bbw user pays it, we don't save the user as a contact. Whereas, the data returned in the transactions list shows the settlement counterparty (i.e. the username of the payer and payee).
We want to also save contacts if a lightning payment is made between two bbw users.
Below is @nicolasburtey experience on this
-- recipient showed me a lightning QR code from BBW
-- sender paid the invoice from BBW
--> transaction detail show the username of the recipient for the sender in Transaction Detail
--> transaction detail show the username of the sender for the recipient in Transaction Detail
--> unexpetedly
--> username for sender not present to the recipient list in Contact list
--> username for recipient not present to the sender list in Contact list

@Extheoisah  Please would like to work on this, can I go ahead

Hi @tonyguesswho Yeah, sure. It'd be best to sync with @vindard and @dolcalmi (cc @nicolasburtey) as they have more context on the structure of the backend. Feel free to join the Mattermost channel here -> https://chat.galoy.io/galoy/channels/dev to get real time updates and support along the way.


Add hyperlinks to badges in the main page

What:
Add hyperlinks to badges in the main page
Why:
Closes: https://app.asana.com/0/0/1196225495304493/f
How:

Refactor Badge component to accept a href prop
Add links to main slider badges

Media
https://www.loom.com/share/10fe7205c3e54f8cbe79eee0721fdfbd

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


WIP: Feature/subscription

Closes #7

@vic Great! This will be really useful to me! Thanks, I will do some testing on this later today.

@conor-mac-aoidh great! Please let me know if you try this with the example phoenix backend, that would be awesome. Only issue would be that right now, we use the same topic for sending the subscription and for listenning for subscription messages. Middlewares' can now read context.operation  which can be subscription or query, so that middlewares can change the context.options.channel.topic or anything depending if being used for a subscription or query.

@vic Sorry I haven't had a chance to test this yet! The example app does not actually use apollo or apollo-phoenix-websocket, so in order to test it I will have to do some work on the frontend to use those libs. Hopefully I'll get around to it in the next week or so.

@conor-mac-aoidh No problem, I've also been not close to the computer this month, hopefully will find some time this or next week to explore this further.

Update on this branch progress... [cc @G3z]
Just merged master on this branch, but still not properly subscribing to the backend.
Made a phoenix_chat_example apollo branch on which I'm trying to rewrite the app.js to use APW (apollo-phoenix-websocket). On the APW side, the subscription would be really easy, we would just need to send the subscription document to the server and then use channel.on(msg_name, listener) and forward those messages to the apollo subscription callback.
I was thinking the server would send the message-name under which new subscription data will be received, but looking at the example app.js looks like its always listening for a hardcoded name

today I made some changes and got this branch working with the example chat application. Here's how you can help testing this.. (cc @conor-mac-aoidh @G3z)
# clone, or fetch and checkout the feature/subscription branch
git clone git@github.com:vic/apollo-phoenix-websocket --branch feature/subscription
cd apollo-phoenix-websocket
npm install && npm run compile

# then clone my chat app fork on apollo branch
git clone github.com:vic/phoenix_chat_example.git --branch apollo
cd phoenix_chat_example
npm install

# either npm link or just symlink to our recently compiled APW
rm -rf node_modules/apollo-phoenix-websocket
ln -s /path/to/apollo-phoenix-websocket node_modules/

# run the server
mix deps.get
mix phoenix.server

Open two browsers and they should be able to talk to each other.
You might want to take a look at the client side app using APW here (I've renamed the original bare-sockets App as App0 for reference)
On the backend, the only change I made to the original phoenix_chat_example
was this one so that new subscription data gets sent with a different event name -something like ___absinthne__:62335222__- (this way you can get data updates for different gql subscriptions) instead of always getting them on a single subscription:data event as the original code did.
On the client side, and important change is the addition of a required configuration option channel.subscriptionEvent that has the following signature:
(subscriptionResponse, {request, options}) => eventName:String
This function gets called with the resolution of the subscription operation (the chat example generates a new identifier for them that looks like {ref: '___absinthe___:62335222'}). Thus we just extract this ref value so that APW can subscribe to data coming from it.

Oh forgot to mention, things are highly experimental haha as I didn't implement tests for this :/ and some things like unsubscribing are not implemented.

Been following the main Absinthe Subscription issue, your library is mentioned there!
@benwilson512 made the following comment a few weeks back. :
 Do note that while apollo-phoenix-websocket will indeed run graphql queries and mutations, it will not run subscriptions it looks like. Nonetheless that project is super handy as far as solving the JS side of the equation. I'm very excited to integrate it with the proof of concept we did of subscriptions in https://github.com/benwilson512/phoenix_chat_example/tree/absinthe
Looks like you did implement it with the POC he is mentioning - may want to jump in that thread and let them know what you have learned!

Hey everyone!
Absinthe subscriptions is coming along soon, kudos to @benwilson512 et al. for their awesome work on it. So I've updated this branch and I guess it's finally time to merge it into master.
I've updated the README and released APW 0.6.0, if you have been waiting for GQL websocket subscriptions, this is the moment to try them. I've setup an example app here https://github.com/vic/verily


Weekly Template tags are off

I use the template tags in order to insert backlinks to each daily note for the weekly note, as such:
Backlinks: [[{{monday:YYYY-MM-DD_ddd}}|Monday]], [[{{tuesday:YYYY-MM-DD_ddd}}|Tuesday]], [[{{wednesday:YYYY-MM-DD_ddd}}|Wednesday]], [[{{thursday:YYYY-MM-DD_ddd}}|Thursday]], [[{{friday:YYYY-MM-DD_ddd}}|Friday]], [[{{saturday:YYYY-MM-DD_ddd}}|Saturday]], [[{{sunday:YYYY-MM-DD_ddd}}|Sunday]]

However, I get the following results when creating a new weekly note:

with week starting on Sunday:

Backlinks: [[2020-12-20_Sun|Monday]], [[2020-12-21_Mon|Tuesday]], [[2020-12-22_Tue|Wednesday]], [[2020-12-23_Wed|Thursday]], [[2020-12-24_Thu|Friday]], [[2020-12-25_Fri|Saturday]], [[2020-12-26_Sat|Sunday]]

with week starting on Monday:

Backlinks: [[2020-12-22_Tue|Monday]], [[2020-12-23_Wed|Tuesday]], [[2020-12-24_Thu|Wednesday]], [[2020-12-25_Fri|Thursday]], [[2020-12-26_Sat|Friday]], [[2020-12-27_Sun|Saturday]], [[2020-12-21_Mon|Sunday]]

For now, my workaround is to start the backlinks at Sunday even tho it's going to become a link to Monday:
with week starting on Monday:
[[{{sunday:YYYY-MM-DD_ddd}}|Monday]] -->  [[2020-12-21_Mon|Monday]]

Great catch, sorry about that! Will have a fix out shortly.

Hey, @etiennepellegrini I just released v1.4.7 which should fix this issue (sorry for the delay, was hoping to include it as part of a bigger release but decided to just get some bug fixes in first)

Works like a charm thanks a lot!


Add Node 10 to Travis config and remove Node 6

Update Travis config to add support for Node 10 and remove Node 6.

Appveyor config also needs to be updated but I'm not sure if they support Node 10 yet. Actually I'm not sure if Travis does either so let's see what happens. 😀🍿

Both support it.
Can you update the PR or trigger a new build?

Do we plan to remove support for Node 6?

@gaearon @Timer and I discussed dropping support for Node 6. It's in maintenance now. EOL is April 2019.

I will merge some of our recent test improvements into this branch which will re-trigger the tests.

Cool. I'm cool with dropping it

Ugh. Tests passed on Node 10 for simple and monorepo but failed for install and kitchensink. They just timed out. For the simple test suite it took twice as long to run on Node 10 as it did on Node 8. Still want me to merge this?

I want to get a PR passing before we merge ... what in the world is going on. 😅

I don't know but it's a real mess. Sometimes Travis fails, sometimes Appveyor fails, sometimes they both fail and every once in a while they both miraculously pass. Often they will go from passing to failing and the only difference is a change in the README. 🤷♂

Sounds like some race conditions.

Can you add --timeout 30000 to the mocha calls?

This seems like a bit of an improvement. Kitchensink is very flaky on both Node 8 and 10. It passed on Travis but only because I re-ran it 4 times. It seems to fail in different places with different errors.
Installs is consistently failing on Node 10 at the same place on Travis and Appveyor, although it fails in different ways on both. This could be due to the different version of yarn.
This is what the logs look like on Travis and it just hangs here for 30+ minutes until the test times out:
+npx create-react-app --scripts-version=/tmp/tmp.hATqpWFGgY/enoah-scripts-0.9.0.tgz test-app-scoped-fork-tgz
npx: installed 289 in 14.817s
Creating a new React app in /tmp/tmp.hATqpWFGgY/test-app-scoped-fork-tgz.
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and @enoah_netzach/react-scripts...
yarn add v1.3.2
(node:4567) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
info No lockfile found.
[1/4] Resolving packages...

On Appveyor it actually fails on the same part and this is what the logs look like there:
+ npx create-react-app --scripts-version=/tmp/tmp.MzXAX6CkKW/enoah-scripts-0.9.0.tgz test-app-scoped-fork-tgz
npx: installed 289 in 8.779s
Creating a new React app in C:\Users\appveyor\AppData\Local\Temp\1\tmp.MzXAX6CkKW\test-app-scoped-fork-tgz.
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and @enoah_netzach/react-scripts...
yarn add v1.5.1
(node:504) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
info No lockfile found.
[1/4] Resolving packages...
Aborting installation.
Unexpected error. Please report it as a bug:
{ Error: Cannot find module<EMAIL_ADDRESS>    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:594:15)
    at Function.Module._load (internal/modules/cjs/loader.js:520:25)
    at Module.require (internal/modules/cjs/loader.js:650:17)
    at require (internal/modules/cjs/helpers.js:20:18)
    at checkNodeVersion (C:\Users\appveyor\AppData\Roaming\npm-cache\_npx\2372\node_modules\create-react-app\createReactApp.js:544:23)
    at getPackageName.then.then.then.packageName (C:\Users\appveyor\AppData\Roaming\npm-cache\_npx\2372\node_modules\create-react-app\createReactApp.js:345:7)
    at process._tickCallback (internal/process/next_tick.js:68:7) code: 'MODULE_NOT_FOUND' }
Deleting generated file... package.json
Deleting test-app-scoped-fork-tgz/ from C:\Users\appveyor\AppData\Local\Temp\1\tmp.MzXAX6CkKW
Done.
++ set +x
e2e-installs.sh: ERROR! An error was encountered executing line 200.
Cleaning up.
yarn config v1.5.1
(node:444) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
success Set "registry" to "https://registry.yarnpkg.com".
Done in 0.05s.
Exiting with error.
Command exited with code 1

Can we install the latest Yarn?

I added a before_install script to install the latest version of Yarn on Travis. I'm not sure if it made a difference though. The tests did pass but I had to rerun a couple of them. The old-node test failed because it tried to install Yarn with Node 0.10 which doesn't work.
I'm trying to figure out if I can skip installing Yarn with Node 0.10. Alternatively we could update our old-node test to use Node 4 or 6.

Looks like all the tests are now passing on Travis. I had to restart two of them because they failed to install the latest version of Yarn. It looked like a temporary issue with the Yarn site unrelated to our tests.
Appveyor tests are queued...
🍿

Appveyor!!

It works! 🎉
Updating Yarn seems to make a difference with Appveyor. On Travis the process of updating Yarn itself seems to be a bit flaky. The download failed a couple of times and there was a checksum error another couple of times. I'm not sure if this is an issue with the Yarn download site or with Travis. Either way, this seems like a big improvement.

The README is based on CRA 1.0. We will be updating all the documentation before 2.0 is released.


[WIP] Devnet state refactor

Usage related changes

Development related changes

Checklist:

[ ] Applied formatting - ./scripts/format.sh
[ ] No linter errors - ./scripts/clippy_check.sh
[ ] Performed code self-review
[ ] Rebased to the last commit of the target branch (or merged it into my branch)
[ ] Documented the changes
[ ] Linked the issues which this PR resolves
[ ] Updated the tests
[ ] All tests are passing - cargo test

closing because changes are in this PR https://github.com/0xSpaceShard/starknet-devnet-rs/pull/193


Architect 4(!)

After a ton of community feedback we’re preparing to release Architect 4.x to tighten up the core and make onboarding to AWS Lambda functions even easier.
Things that are different

One repo to rule them all: arc-repos/architect
New npm package name: npm i @architect/architect

@architect/workflows will be marked deprecated but will NOT be destroyed, and will remain up
Opt into these changes whenever you're ready!

Simplified to five Lambda function types:

@http (API Gateway)
@events (SNS)
@queues (SQS)
@scheduled (Cloudwatch Events)
@tables (DynamoDB triggers)

Things we added

Generic HTTP functions (@http)

Arc users will no longer be bound by a limited set of content-type based functions, limited methods, and limited number of status codes

@http will support any status code, any HTTP method, and any content-type

Zero deps by default!
Zero config by default!
CORS is a boolean flag on any route
Arc’s anonymous signed sessions are now opt-in
Middleware will now be opt-in (and the old arc route style will be supported by opt-in)

/public

Much faster, easier (and clear default!) path for getting static assets onto S3 / CF
/public will always be present in Arc projects moving forward, and be mounted locally in sandbox. However, it will be inert if you haven’t defined buckets with @static in your .arc manifest.
Improvement: when mounted locally in sandbox, public will only match filenames found in the local fs (as opposed to by filetype today); requests for non-matching files will be passed through if using the req._static() helper

Things we plan to remove

Content-Type functions: @html, @css, @js, @json, @xml, and @text

With the addition of generic HTTP functions, you can deliver any kind of content, not just html, css, js, json, xml and text
Content-Type based HTTP routes was a difficult tradeoff that we made early on in Architect that was necessary at the time because API Gateway did not have the necessary custom header support for this to be configurable
Content-Type based HTTP routes have created a brittle and difficult to scale maintenance problem for Architect, as these paths rely on a complex set of velocity templates
Arc users have consistently told us that content-type based routes didn’t make sense, and were clumsy and difficult to work with
Arc docs are massively duplicative because of the overlapping functionality of content types, thereby adding confusion and difficulty to ramping new Arc developers

.static

We heard a lot of feedback from the community around Arc's static asset story; .static was not discoverable, difficult to learn, and not intended to be checked into source, which made it ineligible for the most common uses of static assets
As a result, .static wasn’t used very much, so we wanted to make something more in line with what folks are used to and looking for

Next steps

Contribute feedback!
Big docs refactor to reflect these new features, functionality, examples, and thinking
Upgrade to 4.x

Timeline

Aiming for initial release 10/22/2018

+1

For posterity, from the Architect community Slack:
glenngillen: The only feedback I have is these all seem sensible and worthwhile to me. :shipit:
jkarsrud: Holy :poop:, that is awesome news! I can’t wait to actually try this out!

A quick heads up:

4.0 RC1 is available now at https://www.npmjs.com/package/@architect/architect
Updated docs staged at https://stage.arc.codes/

Upgrade guide: https://stage.arc.codes/guides/upgrade

Announcement coming early this week!

Closing issue for now. Thanks for your feedback, everybody – looking forward to your 4.x bug reports and feature requests! 🕵🏽♀


Cannot set property default of # which has only a getter

TypeScript Version:  3.7.x-dev.201xxxxx

Search Terms: which has only a getter
Code
https://github.com/bluelovers/ws-react/blob/master/packages/react-use-localstorage/src/core.ts
export * from './core/v4';
import createStorageHook from './core/v4';
export default createStorageHook

"use strict";
var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
    if (k2 === undefined) k2 = k;
    Object.defineProperty(o, k2, { enumerable: true, get: function() { return m[k]; } });
}) : (function(o, m, k, k2) {
    if (k2 === undefined) k2 = k;
    o[k2] = m[k];
}));
var __exportStar = (this && this.__exportStar) || function(m, exports) {
    for (var p in m) if (!exports.hasOwnProperty(p)) __createBinding(exports, m, p);
}
var __importDefault = (this && this.__importDefault) || function (mod) {
    return (mod && mod.__esModule) ? mod : { "default": mod };
};
Object.defineProperty(exports, "__esModule", { value: true });
__exportStar(require("./core/v4"), exports);
const v4_1 = __importDefault(require("./core/v4"));
exports.default = v4_1.default;
//# sourceMappingURL=core.js.map

Expected behavior:
no crash error
Actual behavior:
TypeError: Cannot set property default of # which has only a getter
Playground Link:
Related Issues:
https://github.com/microsoft/TypeScript/issues/37092

if move down export * after export default will not have this error
but i think this should not happen
import createStorageHook from './core/v4';
export default createStorageHook
export * from './core/v4';

Related PR:
https://github.com/microsoft/TypeScript/pull/35967

Maybe related: https://github.com/microsoft/tslib/issues/103
I went through the same issue and I solved it by downgrading tslib to 1.13.0

This was fixed by #38808.


GH-39136: [C++] Remove needless system Protobuf dependency with -DARROW_HDFS=ON

Rationale for this change
Our HDFS related codes don't depend on Protobuf because we process HDFS via external libhdfs.so and it's dlopen()-ed.
What changes are included in this PR?
Remove a needless CMake configuration.
Are these changes tested?
Yes.
Are there any user-facing changes?
Yes.

@github-actions crossbow submit java-jars -g cpp


Auto release artifacts for Maven Central

Releases to Maven Central should be automatically released (instead of waiting for a manual release button pressed by some Camundi, as this slows down releases for community members and can also create bottlenecks on the Camunda side).

@akeller I recall that you had some discussions around this in the past - anything interesting to add?
@xomiamoore Any objections to adjust this behavior?

I think this needs to be changed here: https://github.com/camunda-community-hub/community-hub-release-parent/blob/master/pom.xml#L147
(just for the record, related issue https://github.com/camunda-community-hub/community-action-maven-release/issues/45 - @remcowesterhoud).

@berndruecker, there was some concern by (now ex-) Camundi that this was potentially insecure and risky. Given that I, personally, was too stretched to review any of the assets, I relied on the maintainer making good choices about what they add to their project (and, therefore, what is released).

Thanks for the feedback Amara - inline with my memories. Unless anybody objects (@xomiamoore / @mary-grace?) I would switch to auto-releases by default - which means, that there will be no manual step involved to get a release to Maven Central

@berndruecker I'm ok with this change. Mia is out sick and it's unsure when/if they'll be back online this week, so I'm ok with moving forward with the acknowledgment of the prior concerns and a potential need to keep a closer eye on things moving forward to make sure there aren't any security issues or concerns.

I believe currently this issue can be closed, since we have a property in the docs allowing to close the staging repository after successful release. I just documented the feature

Thanks for this hint, but I have this activated from the very beginning on. It doesn't bring the desired effect.

Yeah - I agree - I think it is not picked up as it is not used (I just introduced this yesterday and I think it was removed again already - I have a look at it today: https://github.com/camunda-community-hub/community-hub-release-parent/blob/3e48e4da7de23e44505122145abb06efecc2f1c4/pom.xml#L190)

Interesting - the latest HEAD version does a proper auto-release (see example for https://oss.sonatype.org/service/local/repositories/releases/content/org/camunda/community/community-hub-extension-example/0.0.3/community-hub-extension-example-0.0.3.pom build by https://github.com/camunda-community-hub/community-hub-extension-example/actions/runs/4062895558/jobs/6994482279) - maybe that was some other problem that you just resolved with your cleanup work this night @zambrovski - so I agree that we can close this. Thank you so much!

@stephanpelikan Switching to the parent 1.4.0 and making sure you are using the latest action (which you should automatically if you use v1) should give you auto releases. Please let me know if it does not work as expected!

Not lucky. This is not about becuase of auto-close. As you can see, the Nexus OSS server just broke. @berndruecker you should be able to login into the Nexus Console and should find the orgcamunda-2240 repository still unclosed. Just click on the button and it should be ok.
So I hope this was just bad luck of Sonatype glitches. Will observe it further.
Cheers,
Simon
On Wed, 2023-02-01 at 05:05 -0800, stephanpelikan wrote:
Ok, parent 1.4.0 was missing. I released a new version, but it failed due to OSSRH problemshttps://github.com/camunda-community-hub/vanillabp-camunda7-adapter/actions/runs/4064552067/jobs/6998122008#step:5:2684. I don't know if this is because of the auto-release or because of a common instabilitiy of oss.sonatype.org. Do you have an idea?
—
Reply to this email directly, view it on GitHubhttps://github.com/camunda-community-hub/community-action-maven-release/issues/48#issuecomment-1412025464, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAFEK2AYLRKSW5OMA2LL6YDWVJNP5ANCNFSM6AAAAAAULA7WOM.
You are receiving this because you were mentioned.Message ID: @.***>

I will rerun the Github action later.
Others who faced the same problem got the advise to request for migrating to s01.oss.sonatype.org. Maybe you should consider this for Camunda Community Hub as well?

We have some things on s01.oss.sonatype.org - but this affects whole package id's (e.g. org.camunda), so this is not a completely easy undertaking. Let's just keep an eye on how often this happens for the moment.

By-the-way: Next time we to rerun the Git action because now the Maven deployment was not completed and I have to upgrade the version manually.

Yeah - sounds better - then I could simply drop the release from maven central. Sorry for the inconvenience - it seems to be really not your lucky week... 🧸


Unknown130 Parameter Solved

Hey guys,
I have figured out what Unknown130 Parameter is.
It is the Delay the AI will use to send units to attack the walls if SiegeEngines are alive during the Assault.
I tested this with The Snake, where his default is set to 0. I changed it to 50 and tested it and while he has his 1 catapult alive he would not sent his units to attack the wall for a very long time. I don't know what unit of measurement is used, game ticks, seconds, mins, months etc? But 50 is a long time before he will send units in while his catapult is alive.
-Once his catapult dies, he will then revert back to the "normal" delay he uses to send in units to attack the wall.

-If the Siege equipment breaches the wall they will proceed normally as when any breach is created.
Other things to note:
-AttUnitEngage are unaffected, they will attack nearby enemy units the moment the assault starts regardless of the SiegeEngines status.
-AttUnit2 will also engage, but they will not send units to attack the wall until the delay is over or the catapult dies.
AttUnitPatrol - will still engage no matter what.
AttUnitBackup will go to their normal spot upon beginning of the siege.
AttUnitSiegeDefence - will go to their spot by the SiegeEngine units while they engage.
Laddermen won't engage until the delay is met or the SiegeEngine units die.
Tunnelers didn't test.
Assassins - won't engage until the delay is met or the SiegeEngine units die.
AttDiggingUnit - won't engage until the delay is met or the SiegeEngine units die.
AttUnitMain - won't engage until the delay is met or the SiegeEngine units die.
I also did not test what constitutes as siege equipment, I assume anything under the SiegeEngine Array will count but I didn't test that. So I don't know if it is the same for Catapult as it would be for Battering Rams or Siege Towers.
If it is, I think it would be really good for some AI's to wait a bit and see if their Battering Rams/Catapults can knock down a gatehouse before they throw their lives away running in to assault the walls by hand, or get killed by their own Catapults(cough Pig cough Abbot)
These are the vanilla Values for all the AI
RAT - 0
SNAKE -0
PIG - 5
WOLF - 12
SALADIN - 4
CALIPH - 2
SULTAN - 0
RICHARD - 20
FREDERICK - 20
PHILLIP - 0
WAZIR - 4
EMIR - 0
NIZAR - 0
SHERIFF - 5
MARSHAL - 0
ABBOT - 0
Something like ATTSIEGEEngUnitsDELAY would be what i'd call the parameter.

wow
, great to know that, thanks alot buddy!!!

Wow!!!

this is a greated and detialed description, love it :D
i am looking forward to you finding out even more abt this in the future :D

Parameter 130 got solved, for discussing the ghost engineers, there are plenty of other issues currently open.


feat: astro-3.0 and all dependencies updated

closes https://github.com/satnaing/astro-paper/issues/111
Description: This PR aims to be a simple port of astro-paper to Astro 3.0, no new features introduced in that update were added. A lot of styles were broken in the update, so this PR also fixes them.

I purposefully avoided fixing that because I did not find it on the changelog and didn't want to break it. However, I just found it documented at the very end of the page, so will try to fix it later.

Should be solved now

Works for me, I think there might have been another warning in rss.xml.ts, but i've modified/forked my original and since then done other things. So I think that one might need something too?
return new Response(JSON.stringify(rss({     title: SITE.title,     description: SITE.desc,     site: SITE.website,     items: sortedPosts.map(({ data }) => ({       link: posts/${slugify(data)},       title: data.title,       description: data.description,       pubDate: new Date(data.pubDatetime),     })),   })));
such as ^^

I truly appreciate your PR and your dedication to this. Thank you for your hard work.
I've also been working on the same issue locally, and I noticed that many of the changes in your PR are similar or identical to what I've been working on. If there are any changes, features, or bug fixes that you've made, which are not present in my PR, would you be open to merging them into my PR?

I truly appreciate your PR and your dedication to this. Thank you for your hard work.
I've also been working on the same issue locally, and I noticed that many of the changes in your PR are similar or identical to what I've been working on. If there are any changes, features, or bug fixes that you've made, which are not present in my PR, would you be open to merging them into my PR?

I will check it out!

Guys, may I ask you to add RTFM how to update existing blog with this release?

@alec-c4
That will also be added soon. In the meantime, if you'd like, you can start experimenting with the new version on your own by examining the commit history, such as this PR or mine.

@alec-c4
That will also be added soon. In the meantime, if you'd like, you can start experimenting with the new version on your own by examining the commit history, such as this PR or mine.

@alec-c4
That will also be added soon. In the meantime, if you'd like, you can start experimenting with the new version on your own by examining the commit history, such as this PR or mine.


Aborted Core Dump - node_http_parser

ready - started server on <IP_ADDRESS>:3000, url: http://localhost:3000 info  - Loaded env from /var/www/node/umami/.env info  - Using webpack 4. Reason: future.webpack5 option not enabled https://nextjs.org/docs/messages/webpack5 node[18880]: ../src/node_http_parser.cc:567:static void node::{anonymous}::Parser::Initialize(const v8::FunctionCallbackInfo<v8::Value>&): Assertion args[3]->IsInt32()' failed.
1: 0xb12b40 node::Abort() [node]
2: 0xb12bbe  [node]
3: 0xb2a2c2  [node]
4: 0xd6014b  [node]
5: 0xd615ec  [node]
6: 0xd61c66 v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [node]
7: 0x160c699  [node]
Aborted (core dumped)
`
I am receiving the above error. I am on ubuntu 20.04 LTS and -
ubuntu@ip-172-31-19-129:/var/www/node/umami$ npm -v 7.11.2
Any thoughts on how to fix this?

How did you solve this?


Problem view shows . next to problems in untitled notebooks

Type: Bug

Open workspace
Create a new notebook
Create a syntax or other error in a cell
Open problems view

bug
There's an extra . to the right of the notebook file title

VS Code version: Code - Insiders 1.88.0-insider (Universal) (b0d975fc6370f15570c380f41015b1ca2cdcb791, 2024-03-25T05:50:56.142Z)
OS version: Darwin arm64 23.4.0
Modes:

System Info

Item
Value

CPUs
Apple M2 Max (12 x 24)

GPU Status
2d_canvas: unavailable_softwarecanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onopengl: disabled_offrasterization: disabled_softwareraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: disabled_softwarevideo_encode: disabled_softwarewebgl: unavailable_softwarewebgl2: unavailable_softwarewebgpu: unavailable_software

Load (avg)
5, 4, 4

Memory (System)
64.00GB (0.02GB free)

Process Argv
--crash-reporter-id 0fffb5da-9cd7-46fd-9e7f-a1564e8c5fda

Screen Reader
no

VM
0%

It is also same in Search

Probably this should be something handled by the IResourceLabel
CC @bpasero

Its possible to omit . in the label widget for setFile because there we know we are in a file context and . is not very meaningful for descriptions.
But for the problems view there is an explicit call to setResource with an explicit description passed in:
https://github.com/microsoft/vscode/blob/002041ffcb3bd264350816d1b32e333e16b98682/src/vs/workbench/contrib/markers/browser/markersTreeViewer.ts#L184-L188
@sandy081 any reason setFile is not used?

I do not remember why we have two branches here - setFile and setResource. Is there a general suggestion for this?

Or maybe we need to enlist the cell scheme as well as we do for untitled scheme.

I am looking for this before digging deep. Is there a way to know this?

Yeah I would pick the setFile and see what breaks, but maybe there is something in the history of that change that could explain it?
I think schemes are pretty much hardcoded, here unfortunately while the notebook scheme is untitled, the cell schemes are not. @rebornix is there a way to know if a cell scheme is untitled?

It goes back before we used to have label service. I was also not showing the parent of the resource if the resource has no file provider. Showing parent was introduced here.
I believe using setFile is the right way to go. I also see Search doing the same.


fix: Twitch global emotes not loading

The attempt to load Twitch global badges failed because it was made before initialize had been called on AccountController, causing Helix to be in anonymous mode, causing the request to fail.
This was a bit harder to notice since we have a list of backup badges in case a user is not logged in, but it was reported in Discord just now.
Alongside the fix, I've updated our list of Twitch global badges.


Verification of a signature from a client running C# NBitcoin

Hello,
I'm developing an application with Unity and C# and I'm using NBitcoin to get a signature so I can verify that same signature on the server with Bit-Wasp.
So far I've been able to Bit-Wasp install the library with the composer and I've implemented the example case for signature verification using Bit-Wasp. The main problem right now it's that it doesn't seem to recognize as valid the signature, so everytime that I called the verification: $signer->verify($signedMessage, $address) I'm getting false when it should be true. I'm using Test Net both in the client and in the server so it's not a problem that I'm working on different networks.
What am I missing? Are there multiple ways to verify a signature on Bit-Wasp? What other possible configurations could I use for the verfication process?
Any help would be greatly appreciated.

I forgot to put the data:
The signature on Test Net:
-----BEGIN BITCOIN SIGNED MESSAGE-----
HOLA MON, COM ESTEM
-----BEGIN SIGNATURE-----
IKQLruydze++zscBBNd4UN9wqNZFV03VaH1PZ2zpqeI9JskSUzrI4RLQhaKMtpkZCZzv3BIDQjZfZNqPGjuyCRA=
-----END BITCOIN SIGNED MESSAGE-----
The Public Address on Test Net:
mosRoizxQyCyt7Y2DGpr5rrbyid5FYCNn3

I've checked with success the verification on these online signature verification webservices:
https://blockexplorer.com/messages/verify
https://reinproject.org/static/bitcoin-signature-tool/index.html#verify
In the last one is pretty similar to the format used by Bit-Wasp. Just copy and paste:
-----BEGIN BITCOIN SIGNED MESSAGE-----
HOLA MON, COM ESTEM
-----BEGIN SIGNATURE-----
mosRoizxQyCyt7Y2DGpr5rrbyid5FYCNn3
IKQLruydze++zscBBNd4UN9wqNZFV03VaH1PZ2zpqeI9JskSUzrI4RLQhaKMtpkZCZzv3BIDQjZfZNqPGjuyCRA=
-----END BITCOIN SIGNED MESSAGE-----
What am I doing wrong? This is the code that I'm using. Any help would be greatly appreciated:
		$network = NetworkFactory::bitcoinTestnet();
		Bitcoin::setNetwork($network);
		$addrCreator = new AddressCreator();
		$sig = "-----BEGIN BITCOIN SIGNED MESSAGE-----
".$original_message_par."
-----BEGIN SIGNATURE-----
".base64_decode($message_signed_par)."
-----END BITCOIN SIGNED MESSAGE-----";

		$address = $addrCreator->fromString($publicaddress_par);
		$compactSigSerializer = EcSerializer::getSerializer(CompactSignatureSerializerInterface::class);
		$serializer = new SignedMessageSerializer($compactSigSerializer);
		$signedMessage = $serializer->parse($sig);
		$signer = new MessageSigner();
		if ($signer->verify($signedMessage, $address)) {
			return true;
		} else {
			return false;
		}

<?php
require "vendor/autoload.php";
use BitWasp\Bitcoin\Crypto\EcAdapter\EcSerializer;
use BitWasp\Bitcoin\Crypto\EcAdapter\Serializer\Signature\CompactSignatureSerializerInterface;
use BitWasp\Bitcoin\MessageSigner\MessageSigner;
use BitWasp\Bitcoin\Network\NetworkFactory;
use BitWasp\Bitcoin\Bitcoin;
use BitWasp\Bitcoin\Address\AddressCreator;
use BitWasp\Bitcoin\Serializer\MessageSigner\SignedMessageSerializer;

$network = NetworkFactory::bitcoinTestnet();
Bitcoin::setNetwork($network);
$addrCreator = new AddressCreator();
$sig = "-----BEGIN BITCOIN SIGNED MESSAGE-----
HOLA MON, COM ESTEM
-----BEGIN SIGNATURE-----
IKQLruydze++zscBBNd4UN9wqNZFV03VaH1PZ2zpqeI9JskSUzrI4RLQhaKMtpkZCZzv3BIDQjZfZNqPGjuyCRA=
-----END BITCOIN SIGNED MESSAGE-----";

$address = $addrCreator->fromString("mosRoizxQyCyt7Y2DGpr5rrbyid5FYCNn3");
$compactSigSerializer = EcSerializer::getSerializer(CompactSignatureSerializerInterface::class);
$serializer = new SignedMessageSerializer($compactSigSerializer);
$signedMessage = $serializer->parse($sig);
$signer = new MessageSigner();
if ($signer->verify($signedMessage, $address)) {
    echo "yay\n";
} else {
    echo "noooooooop\n";
}

I tried this one and it worked. Can you provide the library version, whether secp256k1 is installed, and can you verify what network is in use just before you call $signer->verify?

Sorry, I went with another solution. It was for a punctual problem and I needed a response back then.

cool, ok


upgrade: consider all 'active+clean' states as valid pgs

In cluster with a large number of PGs, it can be expected some of them
scrubbing, it's a normal operation.
Preventing from scrubbing operation force to set noscrub flag before a
rolling update which is a problem because it pauses an important data
integrity operation until the end of the rolling upgrade.
This commit allows an upgrade even while PGs are scrubbing.
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1616066
Signed-off-by: Guillaume Abrioux<EMAIL_ADDRESS>

jenkins test pipeline

jenkins test pipeline

@guits are there automated tests for this scenario (updates during scrubbing) in the testing pipeline? Or was this fix tested manually?


me not support hls on ie8 ?

I try to use hls on ie8, but it does't work.

sorry , official demo support hls.


Handle the combination of a write and a void return

When the return type is void, there's no returnValueProperty, but that
doesn't mean we don't need a return at the call site.
Fixes #18140.

@amcasey,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


npm-on-ipfs: the desktop app! A long lived client to encourage co-hosting

Having teams co-host the modules they use would be rad! But that needs a long running process on the developers machine. We could have the npm-on-ipfs client spawn one, but it's not very visible to the user, and the current expectation of the npm command is that it does its work and then exits, so there would be a UX challenge to alter that.
What if we had a menubar app like ipfs desktop that ran an ipfs daemon process to re-host modules you fetch? It could show you stats about what modules you use a lot, and which ones other folks have fetched from you.
Would this be valuable? Could it help us usher in the network effect of having many smaller, partial caches of popular npm modules available on the network?

This came up again in the GUI team OKR discussions, but I figured it'd make more sense to discuss it here

I like it! It would be a great way to have people to feel engaged with the process of replicating the registry.
Also, it would be great if this Desktop app would know how to connect to multiple nodes (e.g. IPFS Desktop, some other local or remote daemon)

I think this would be really useful & increase visibility

I am bit worried about adding another desktop app responsible for daemon orchestration.
We should avoid creating new apps, and provide more and more incentives for people to use existing one :)
Could this idea could be somehow folded into existing IPFS Desktop?
What if..

For gathering local stats: IPFS Desktop exposes a separate port for use in npm-on-ipfs that proxies requests to real Gateway, but in the process of proxying gathers stats on npm downloads
For progressive UX: If this special Gateway registers a hit, it means it is used by npm-on-ipfs, then we could either display NPM stats in Web UI or add a menu item to open a dedicated screen with them.

it'd be rad to be able to get "bandwidth per CID" stats from IPFS, so we can say "you have shared the async module 6 times".  Right now we can only say which peer IDs you've shared with which is less interesting than what you've got that is popular.

@lidel this could go either way on "npm-on-ipfs.app vs ipfs-desktop + npm skills". It'd be rad to figure out a plugins mechanism for ipfs-desktop, but I think I'd be more likely to install a focused app like "npm-on-ipfs.app" than i would "install ipfs-desktop and enable npm proxing"... but as you mention, it'd be nice not to have to maintain more apps...
I was imagining npm-on-ipfs.app having very little surface area, just a menubar icon that shows you some stats, and an excuse to keep a long running ipfs daemon going... with the npm-on-ipfs cli doing the work.

My main fear is that adding another menubar app will just  feel noisy and wasteful to users who also choose to install IPFS Desktop at some point.
Separate app adds unnecessary user confusion and maintenance burden of duplicated features such as auto-update, daemon orchestration: If I have both, do I have two daemons, or one? Which app is the owner of the daemon? Do we promote both apps at https://ipfs.io/#implementations ?
I believe we could design UX so that npm-on-ipfs detects IPFS Desktop  and enables "NPM support" in it automatically. It should incentivize people to run a single IPFS node, not multiple ones.

My assumption is that we would be focusing on "exising npm users", rather than "existing ipfs users". If we can make a really simple and slick UX around ipfs-on-npm then we could get a huge number people co-hosting packages over ipfs.
That said, I do see there is an overhead, both for us to have multiple apps, and potential ipfs + npm-on-ipfs users, and there is a potential win of getting more folks using ipfs desktop. I think either way, we'd build it so that we use an existing daemon where available, so I think the "one daemon vs many" is less of a consideration.
It be worth converging on what our top goal / desired outcome for an npm-on-ipfs app would be. My assumption is it's "large increase in end users co-hosting pacakges via ipfs rather than http". I think the best way to do that is a focused app. If the goal is "get more devs using IPFS in general" then I think we'd probably go for an extention to ipfs desktop.
Or we could do both? A targeted app for the npm user that is decentralisation curious, and an extention to desktop for the IPFS user that wants to share their modules.

Just a fast feedback: I think we could somehow work a way to add this to IPFS Desktop 😄 instead of creating a new app. Some kind of extension or some kind of option on IPFS Desktop that would download the required additional files for the functionality.

Some kind of extension or some kind of option on IPFS Desktop that would download the required additional files for the functionality.

AFAIU, If an MFS folder gets exposed on the IPFS Gateway (not the case today), then effectively what an IPFS node needs to do is to keep replicating a CID (through IPNS or registry.js.ipfs.io) and any npm client could just point the install at the local IPFS Gateway

I think the user experience could be better & more focussed if it's a new app rather than adding features to the existing app, plus not everyone running IPFS Desktop will be an npm user so they are likely to see the addition of npm-stuff as bloat.
As long as the maintenance burden doesn't get too much I'm vaguely pro new-app.

Sorry to parachute into the conversation, but in my opinion it's worth it considering integrating IPFS as a storage backend for Verdaccio, an open source npm registry/cache/proxy which has been gaining a lot of popularity.
It's super easy to get started with, has a beautiful React-based UI on the way, and integrates seamlessly into regular npm/yarn/private-corporate-registry workflows.
The IPFS plugin could fork from the local-storage plugin, and I think it would be more familiar and low-energy to adopt than a dedicated solution.
If this isn't the right place to suggest it I can open a separate issue and delete this one, np. (I have no affiliation to the project btw.)

Thanks @agentofuser, I'd not heard of verdaccio but that looks like a great project to integrate with!

As @olizilla said:

I was imagining npm-on-ipfs.app having very little surface area, just a menubar icon that shows you some stats, and an excuse to keep a long running ipfs daemon going

As @lidel said:

I believe we could design UX so that npm-on-ipfs detects IPFS Desktop and enables "NPM support" in it automatically

I'm not sure if these would need to be mutually exclusive if designed with a progressive user experience in mind, e.g.:

Some users just want something that's not much different than the ordinary experience of using npm. They benefit from @olizilla's menubar icon model, where they get a little bit in the way of stats and general assurance that the thing is working.
Some users might already be running IPFS Desktop, and they'd benefit the most from having npm-on-ipfs features in IPFS desktop exposed to them automagically once they start using npm-on-ipfs (@lidel model; new features in existing tool rather than new tool)
Some users might be using IPFS in the browser, and could potentially be incented to move to the desktop app through the promise of better integration with npm-on-ipfs in desktop rather than having to go between menubar features + browser features?

Strictly speaking, this would be duplicating feature creation effort for us, but for the user, it's gradually exposing functionality by presenting a lite -> fully-featured progression and a means of wading into the IPFS waters bit by bit.

For npm-on-ipfs to be successful at distributing the load of serving npm traffic it needs lots of long running daemons, to achieve that currently you need to:

install npm-on-ipfs in the command line
install and run a long running ipfs daemon that connects to the js.registry.ipfs.io swarm
remember to use $ ipfs-npm whenever you would use $ npm or $ yarn in the command line plus pass the —IPFS-node option to your long running ipfs daemon
remember to start their ipfs daemon again after restarting their computer

Very few people are going to do all of those things manually every time they go to install something via npm, so having a set-and-forget installer would have a big impact.
Ideally installing the “app” (whether it is ipfs desktop or a separate npm-on-ipfs app) should:

Start a long running ipfs daemon (that connects to the js.registry.ipfs.io swarm)
Prompt to install npm-on-ipfs command line tools, aliasing it as $ npm and $ yarn
Run the npm-on-ipfs express server
Launch on startup

Extra features like stats on sharing are nice but likely beyond the scope of Q2 given IPFS camp and other GUI work.
The other problem that we’ll quickly run into is that for first few users, the initial performance of npm-on-ipfs is going to be significantly worse than using regular npm over http.
The quicker we can get more people sharing packages over IPFS the faster it gets for everyone, reducing the poor first user experience which may discourage those users from telling their friends to install it too.
Adding the option to install+enable npm-on-ipfs to the existing desktop app would give a significant
bootstrap effect for adding more users who are already bought into IPFS.
I’m also a big fan of @jessicaschilling’s suggestion, having a progressive pathway into IPFS desktop by having the option to essentially install an npm-specific fork of ipfs desktop that can give them the option to learn more about IPFS when they are ready.
There's also probably some trademark issues around "npm" but IANAL 🙈
TL;DR

First add npm-on-ipfs opt-in support to IPFS Desktop that installs and aliases and configures ipfs-npm to get an initial wave of already primed people sharing packages and testing performance
re-release updated IPFS desktop as a slightly altered, npm branded version for people who aren't already in the IPFS world but think distributed npm is cool

On a related note, I opened up ipfs desktop this morning and within a few minutes the coffee shop wifi had completely fallen over, could be a coincidence but that coincidence seems to happen a lot!


no whitespace or empty string

Hi, @Nightapes nice work.
I like noWhitespace validator for check if is no whitespace,
but, if in my input I write 'aaa bbb' says that is invalid because have a whitespace.
Hi, is posible to add a validator that can check if a form is empty or a string with only 1 whitespace character?
I think adding this could be good for check if input is not only a whitespace string.
like this, for example, http://stackoverflow.com/questions/39236992/how-to-validate-white-spaces-empty-spaces-angular-2
UniversalValidators.noEmptyString = function (control) {
    if (Util.isNotPresent(control))
        return undefined;
    let isWhitespace = (control.value || '').trim().length === 0;
    let isValid = !isWhitespace;
    return isValid ? undefined : { 'noEmptyString': true }
};

what do you think?
Pere

Hey,
i can add this validator.
But first i will upgrade to angular 4 :)

Should be there now in 2.1.0. Give it a try :)

many thanks for the new validator feature @Nightapes.
tested and works ok.
we have another validator in the collection ;)

When you need a new one, open a new Issue or even better a Pull Request.
Good that everything works 👍


[stable/fluent-bit] set default pull policy to Always

Reverting change introduced in #10578.
Signed-off-by: Eduardo Silva<EMAIL_ADDRESS>
What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] DCO signed
[ ] Chart Version bumped
[ ] Variables are documented in the README.md

/lgtm

Why reverting this ?