pyrmont.launchpad's "Get GöETH" links to rate-capped faucet

Summary
When using prymont.launchpad, the "Connect Wallet" step provides a link to "Get GöETH". This links to the Goerli: Authenticated Faucet, which can provide a maximum of 1 Ethers every 1 day. A user would need to wait 32 days to use this service to obtain the 32 Ethers in order to proceed to the next step.
Proposed Solution
This is a hard one. Nobody probably wants to run a service to give out lots of GöETH.
It used to be possible to get it from Prysmatic Labs' Discord server's #request-goerli-eth channel... but this faucet ran out around 2021-05-26, and normal services have not yet resumed.
Aside from this, I have so far been unable to find anywhere to get 32 GöETH, in order to launch a Validator on a testnet.
Screenshots
Showing the link to "Get GöETH":

Showing the rate-cap on getting GöETH through this suggested channel.

@CarlBeek @wackerow @hwwhww - do we know of any faucets that supply 32 GöETH ETH?

@samajammin it is possible to get a 32 GöETH deposit made on your behalf via the ethstaker discord server. The process involves sharing the full transaction data for making the deposit. Extracting this transaction data requires the HTML of a page on pyrmont.launchpad to be edited, in order to activate a button, to allow a user to proceed to the next step.
While this process does work, it could be much easier.

I have no idea. 😅
@q9f Any chance you know any faucets that supply 32 GöETH ETH now?

I have no idea. sweat_smile
@q9f Any chance you know any faucets that supply 32 GöETH ETH now?

No, I'm in the same boat. 😓  See also: https://github.com/goerli/testnet/issues/85 https://github.com/goerli/testnet/issues/84
The problem is the huge abuse of the faucets. The Eth2 deposit contracts for the testnets put some pressure on Goerli but not too much, nothing Goerli wouldn't be able to handle. But apparently, the Swarm tests on Goerli killed it because people misunderstood (?) the procedure and where offering many people real money OTC to buy Goerli Eth, i.e., @Buttaa https://twitter.com/Butta_eth/status/1412428424816349185
The faucet comes with social authentication, captchas, IP-based limits, and ETH-address-based limits, still, there was a massive pressure on the faucets. @maxsam4 did a lot of work to keep it up but I guess now the only solution was to reduce the amounts that can be requested from the faucets further.
That said, the reserves of the Goerli whales are being drained as well. I personally handed out more than 30 million Goerli Eth in the last 12 months. At this rate, Goerli would probably run dry anytime soon.
The most straight-forward solution would be, in my opinion, the following (hear me out, don't judge):

Give Goerli a value and list it on Exchanges or bridge it to mainnet as ERC-677 token. There is no better way to guarantee liquidity long-term.
Use Goerli only for larger applications that require the massive existing infrastructure and can afford spending money on usage (looking at you, Swarm).
Launch a subsequent testnet that will allow for long-term stable and free testing (think: Goerli v2).

This comes with huge downsides though and I guess that's why nobody has done it so far:

Adding a price tag to something that has been promised for free, see also Mudit's comments here: https://twitter.com/Mudit__Gupta/status/1412529001860534274
The Goerli Eth distribution is largely arbitrary and giving it value would be extremely unfair.
There are many legal uncertainties.

Besides, an incentivized testnet would be actually useful for some cases, e.g., https://twitter.com/DeanEigenmann/status/1419289668324057095 - It just needs to be planned and rolled out very carefully.
But I don't want to derail the conversation. Maybe PoA-testnets have an implicit end-of-life date built in and we never thought that Goerli would be so broadly used back in the day when we launched it. Maybe a new testnet would indeed be an idea worth exploring? Downside here is that all infrastructure has to be duplicated. Or, we hardfork Goerli and increase total supply...

@q9f As a temporary fix, I can bump the faucet to drip a bit over 32 ETH.
Apart from the rate limits you mentioned, I've added the following stuff recently

Twitter account age, followers, and tweets requirement. This has basically stopped the current bots that were creating new accounts and instantly requesting funds.
WebSocket request limits and timeout. Without this, the IP rate limits weren't as effective.

Someone with enough motivation can still spam the faucet but given that ethswarm is no longer actively giving GoETH value, I doubt anyone will go to the troubles.
I propose that I raise the drip limit to just over 32 ETH while we keep looking for an alternative solution. If we see the spam return, I'll lower the limits again.

FYI, The drip limit on https://faucet.goerli.mudit.blog/ has been increased. You can now get up to 37.5 ETH in a single request.

I've dropped the max drip to 6.25 ETH to extend the life of the faucet. It has already dropped 60% of its remaining balance and is being used more frequently than ever now.
@q9f we need to eventually think about minting more goerli eth that can be disbursed.

I still have 23kk. Eventually, if we run out, we might want to launch a clean, merged testnet anyways.

Hello, I’m new to this site and just made an account. I’ve been interested in crypto and blockchain technology and more recently have been reading about upcoming “web3.0”. I have a few wallets and have been trying to learn about the different methods to get crypto on the different networks. I was able to get the 6.25 Eth on the Goerli test network from the faucet drip! I was wondering if you can run a node once I have 32 Eth? Thanks

Hi @cynicalyeezus - welcome! Yes, once you have 32 goETH (plus some goETH to pay the gas), you would be able to deposit into a contract on the Goerli testnet, which would allow you to run a Proof-of-Stake Validator node on a testnet.
Do you have any more questions?

That's great to know! I waited 2 days to try the drip again but it still said wait 48 hours. Do you guys have any information or tips to get more Ethereum? And also how to start a node on my computer. Thanks

@maxsam4
good night sir, now how to get GOERLI TESTNET for free?
various sites for my faucet, all can't.
please answer. thank you

@q9f we need to eventually think about minting more goerli eth that can be disbursed.

Please check out https://github.com/goerli/testnet/issues/97

I support this effort. Thanks!

我不知道。  汗水微笑
@q9f 你有没有机会知道现在提供 32 GöETH ETH 的水龙头？

不，我在同一条船上。 😓 参见： goerli / testnet #85  goerli / testnet #84
问题是水龙头的大量滥用。 测试网的 Eth2 存款合约给 Goerli 带来 _了一些 _压力，但压力不大，没有 Goerli 无法处理的。 但显然，对 Goerli 的 Swarm 测试杀死了它，因为人们误解了（？）程序以及向许多人提供真钱场外交易以购买 Goerli Eth 的地方，即 @Buttaa https://twitter.com/Butta_eth/status/1412428424816349185
水龙头带有社交身份验证、验证码、基于 IP 的限制和基于 ETH 地址的限制，但水龙头仍然承受着巨大的压力。 @maxsam4 做了很多工作来保持它，但我想现在唯一的解决方案是进一步减少可以从水龙头请求的数量。
也就是说，Goerli 鲸的储备也正在枯竭。 在过去的 12 个月里，我个人分发了超过 3000 万个 Goerli Eth。 以这样的速度，歌尔力可能很快就会枯竭。
在我看来，最直接的解决方案是以下（听我说，不要评判）：
1. 给 Goerli 一个值并在交易所上架或将其作为 ERC-677 代币桥接到主网。  没有更好的方式来保证长期流动性。

2. 仅将 Goerli 用于需要大量现有基础架构并且能够负担得起使用费用的大型应用程序（看着你，Swarm）。

3. 启动后续测试网，允许长期稳定和免费的测试（想想：Goerli v2）。

不过，这有很大的缺点，我想这就是为什么到目前为止没有人这样做的原因：
1. 为免费承诺的东西添加价格标签，另请参阅 Mudit 的评论： [https ](https://twitter.com/Mudit__Gupta/status/1412529001860534274)

2. Goerli Eth 的分布在很大程度上是任意的，赋予它价值是非常不公平的。

3. 有很多法律上的不确定性。

此外，激励测试网在某些情况下实际上是有用的，例如， https - 它只需要非常仔细地计划和推出。
但我不想破坏谈话。 也许 PoA 测试网内置了一个隐含的生命周期结束日期，我们从未想过 Goerli 在我们推出它的那天会被如此广泛地使用。 也许一个新的测试网确实是一个值得探索的想法？ 这里的缺点是所有基础设施都必须复制。 或者，我们硬分叉 Goerli 并增加总供应量......
sir i buy goerli


TileWMS source getTileUrlFunction can not be called outside OL

Describe the bug
TileWMS source getTileUrlFunction can not be called from application code. Gives error 'this is undefined'. This used to work with v6.3.1 but since v6.4.0 is broken. Can be fixed by binding function to source manually. See attached code sample.
ol-tilewms-bug.zip
To Reproduce
Steps to reproduce the behavior:

Open attached html
Check console to see error

Expected behavior
Function should be callable from application code without manual binding.

Thanks for reporting this. See #11548 for a fix.

That was fast. Thank you!


Adding Grant-CsTeamsEmergencyCalling and CallRoutingPolicy

Worked with @danny-levin to add these files into the repo.
@kenwith please review and merge.

Docs Build status updates of commit bb52bbe:
:clock10: Full build: the average full build time is 11 min(s) 48 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit bb52bbe:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Grant-CsTeamsEmergencyCallRoutingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsEmergencyCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/skype.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 0b5c148:
:clock10: Full build: the average full build time is 11 min(s) 48 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 0b5c148:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Grant-CsTeamsEmergencyCallRoutingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsEmergencyCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/skype.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add sierra college

@Petrivah This domain is blacklisted because the college allows to register an email address there even if you are not a student of the college. If you are the student of this college, please apply with official document ("OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students).


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 1840 ms

Resolved: Bofrost.lu performance has improved in cc8ee53 after 14 minutes.


Fixes from running npm-audit

Fixes to dependencies as reported by npm audit

Codecov Report

Merging #533 (ec8693b) into develop (3d4caeb) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #533   +/-   ##
========================================
  Coverage    80.01%   80.01%
========================================
  Files           38       38
  Lines         1291     1291
  Branches       226      226
========================================
  Hits          1033     1033
  Misses         258      258

Continue to review full report at Codecov.

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


[docs] enable docs on registry

Move docs to a spot where the Terraform registry can pick them up.
Once we do another release, the docs should show up
here.
We won't be able to test this completely until a release is done.
Docs for the docs -
https://www.terraform.io/docs/registry/providers/docs.html.
Test Plan

[ ] CI

References

https://www.terraform.io/docs/registry/providers/docs.html

Codecov Report

Merging #227 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #227   +/-   ##
=======================================
  Coverage   65.81%   65.81%
=======================================
  Files          50       50
  Lines        3698     3698
=======================================
  Hits         2434     2434
  Misses        937      937
  Partials      327      327

Impacted Files
Coverage Δ

pkg/provider/provider.go
69.62% <100.00%> (ø)

Continue to review full report at Codecov.

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


Fix undefined error when clicking cancel button while receiving

Error message clicking cancel button while sending
sendRequest: connected to <IP_ADDRESS>
sendRequest: connected to <IP_ADDRESS>
(node:12448) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading '1')
    at Sender.deleteJob [as _deleteCallback] (C:\Users\dlguswo\workspace\tishare-desktop\src\back\Client.js:267:18)
    at Socket.<anonymous> (C:\Users\dlguswo\workspace\tishare-desktop\src\back\Sender.js:192:14)
(Use `electron --trace-warnings ...` to show where the warning was created)
(node:12448) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)

The problem originates from that when creating new instances of Sender or Receiver,
Server or Client hands over deleteJob method of its own, but since it was not bound to Server or Client,
this in deleteJob method was set to Sender or Receiver, which results in the error.


Uncheck Demo account checkbox in iTunesConnect

New Issue Checklist

[x] Updated deliver to the latest version
[x] I have read the Contribution Guidelines

Issue Description
The submission process failed with this error Enter a demo account user name and password, but my app doesn't need demo account. Does deliver support in uncheck demo account checkbox?
Stack trace:
INFO [2016-04-17 19:21:56.53]: Submitting the app for review...
.../gems/spaceship-0.25.1/lib/spaceship/tunes/tunes_client.rb:174:in `handle_itc_response': [!] The request could not be completed because: (Spaceship::TunesClient::ITunesConnectError)
	Enter a demo account user name and password. Enter a demo account user name and password.
.../gems/spaceship-0.25.1/lib/spaceship/tunes/tunes_client.rb:686:in `prepare_app_submissions'
.../gems/spaceship-0.25.1/lib/spaceship/tunes/app_submission.rb:117:in `create'
.../gems/spaceship-0.25.1/lib/spaceship/tunes/application.rb:288:in `create_submission'
.../gems/deliver-1.11.0/lib/deliver/submit_for_review.rb:8:in `submit!'
.../gems/deliver-1.11.0/lib/deliver/runner.rb:87:in `submit_for_review'
.../gems/deliver-1.11.0/lib/deliver/runner.rb:30:in `run'
.../gems/deliver-1.11.0/lib/deliver/commands_generator.rb:49:in `block (2 levels) in run'
.../gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
.../gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
.../gems/commander-4.3.5/lib/commander/command.rb:153:in `run'
.../gems/commander-4.3.5/lib/commander/runner.rb:428:in `run_active_command'
.../gems/fastlane_core-0.41.2/lib/fastlane_core/ui/fastlane_runner.rb:23:in `run!'
.../gems/commander-4.3.5/lib/commander/delegates.rb:15:in `run!'
.../gems/deliver-1.11.0/lib/deliver/commands_generator.rb:132:in `run'
.../gems/deliver-1.11.0/lib/deliver/commands_generator.rb:12:in `start'
.../gems/deliver-1.11.0/bin/deliver:5:in `<top (required)>'
.../bin/deliver:23:in `load'
.../bin/deliver:23:in `'

I was about to open the very same issue, how great is that :)
To illustrate it a bit further, the apps won't get submitted and if you login manually to iTunes connect this is the reason:

It seems like this affects every user trying to ship an app with deliver, right? I'll take a look into this

@KrauseFx I had the same problem the other day so I unchecked the demo account (it comes checked by default)

@lacostej How could u uncheck the demo account via deliver or fastlane? (manually doesn't count)

@gran33 Haha, working on it 😉

@KrauseFx In our case this happens when we want to add the contact information but don't add a demo account. For example:
app_review_information(
  first_name: "John",
  last_name: "Smith",
  phone_number: "+555555555",
  email_address<EMAIL_ADDRESS>)

Thanks everyone, already in the middle of writing some code 🚀 I'll keep you up to date

This seems to also occur with pilot just after logging "Distributing new build to testers"

PR is live, waiting for the build and a PR review https://github.com/fastlane/fastlane/pull/4245 🎉

in my case the PR does not fix the error

@hjanuschka Could you share more information? In particular: is the checkbox currently enabled or disabled? Do you have a demo user and/or password

@KrauseFx How about the fields on the iTunes Connect's Build page? These are annoying because somehow I HAVE to put something in there. The checkbox on the AppStore tab is unchecked. Can't find a way to use Spaceship to set those fields 😕.

@KrauseFx If I do this…
app = Spaceship::Tunes::Application.find(params[:app_identifier])

build = app.builds.sort_by {|app| app.upload_date}.last
build.update_build_information!(whats_new: params[:whats_new])

I end up with this
Spaceship::TunesClient::ITunesConnectError: A demo account user name is required. A demo account password is required. A demo account user name is required. A demo account password is required.
from /Users/carlos/.gems/gems/spaceship-0.25.1/lib/spaceship/tunes/tunes_client.rb:174:in `handle_itc_response'

@carlosefonseca the fix will be in 0.26 I think not 0.25.1 which you appear to be running.
if have you checked if the field on the App Front page is checked or not ?

@lacostej I said on my first comment "The checkbox on the AppStore tab is unchecked." 🙂
Although that version isn't yet live. Maybe that makes some difference…
But I have apps just for testing that will never be live, so I kind of need a way to set the Demo Account for the uploaded build via Spaceship… (until Apple notices they messed up those builds)

@carlosefonseca
I looked at the code on Apple's side and here's what I see
		"reviewUserName": {
			"value": "",
			"isEditable": true,
			"isRequired": false,
			"errorKeys": null,
			"maxLength": 400,
			"minLength": 1
		},
		"reviewPassword": {
			"value": "",
			"isEditable": true,
			"isRequired": false,
			"errorKeys": null,
			"maxLength": 400,
			"minLength": 1
		},
		"reviewAccountRequired": {
			"value": true,
			"isEditable": true,
			"isRequired": false,
			"errorKeys": null
		}

                                <input type="text" placeholder="User name" ng-model="testinfo.data.reviewUserName.value" ng-required="testinfo.data.reviewUserName.isRequired" itc-field-server-error="testinfo.data.reviewUserName.errorKeys" itc-field-orig-val="originaltestinfo.data.reviewUserName.value" itc-field-cur-val="testinfo.data.reviewUserName.value" itc-field-pop-up-errors="true" maxlength="100" class="ng-isolate-scope ng-pristine ng-valid ng-valid-required">
                                 0">
                                    This field is required.

                                 0">

                                <input type="text" placeholder="Password" ng-model="testinfo.data.reviewPassword.value" ng-required="testinfo.data.reviewPassword.isRequired" itc-field-server-error="testinfo.data.reviewPassword.errorKeys" itc-field-orig-val="originaltestinfo.data.reviewPassword.value" itc-field-cur-val="testinfo.data.reviewPassword.value" itc-field-pop-up-errors="true" maxlength="100" class="ng-isolate-scope ng-pristine ng-valid ng-valid-required">

                                    This field is required.

So I am sending #4250 as tentative to work around Apple server side issue.

@carlosefonseca U can simply submit the app using the deliver flags, in your case
--skip_binary_upload Skip uploading an ipa or pkg to iTunes Connect
Anyway u can see all flags, just type deliver -h

@lacostej Thank you! Seems about right. Will try to test it! I did look into the raw_data but I didn't figure out how to apply the modifications.

New release is live https://github.com/fastlane/spaceship/releases/tag/0.26.0. Let us know how that works for you

Expanded @lacostej's fix to also work on update_build_information.

Thanks to @carlosefonseca I just pushed https://github.com/fastlane/spaceship/releases/tag/0.26.1, could you update and give it a try? 👍

Just to make it clear, I use deliver and Not spaceship directly.
The default demo account is uncheck or check?
As far as I checked (using deliver latest version (1.11.1) which uses the latest spaceship version 0.26.1) the error still occur. Do I need to change the way I use deliver?
I use deliver like this:
bundle exec deliver --skip_binary_upload --skip_screenshots --skip_metadata --force --submit_for_review --automatic_release --verbose
With this Deliverfile:
###################### App Metadata ######################
app_identifier "com.app.bundle.id"
automatic_release true

submission_information({
    export_compliance_encryption_updated: false,
    export_compliance_is_exempt: false,
    export_compliance_uses_encryption: false,
    export_compliance_contains_proprietary_cryptography: false,
    export_compliance_contains_third_party_cryptography: false,
    content_rights_contains_third_party_content: false,
    content_rights_has_rights: false,
    add_id_info_uses_idfa: false,
    add_id_info_serves_ads: false,
    add_id_info_limits_tracking: false,
    add_id_info_tracks_action: false,
    add_id_info_tracks_install: false
})
app_review_information(
  first_name: "my name",
  last_name: "my last name",
  phone_number: "+1<PHONE_NUMBER>",
  email_address<EMAIL_ADDRESS>  notes: ""
)

@gran33 Yeah, it seems deliver isn't yet aware of the checkbox. Check PR #4281.

I've checked the @carlosefonseca patch, it isn't working for me.
Steps I've done:

updated to lastest deliver (1.11.1) and spaceship (0.26.1)
uninstalled old versions of deliver and spaceship via "gem cleanup"
locally patched upload_metadata.rb like this
Tried with different configs:

app_review_information(
  first_name: "my name",
  last_name: "my last name",
  phone_number: "+1<PHONE_NUMBER>",
  email_address<EMAIL_ADDRESS>  notes: "bla bla"
)

and
app_review_information(
  first_name: "my name",
  last_name: "my last name",
  phone_number: "+1<PHONE_NUMBER>",
  email_address<EMAIL_ADDRESS>  demo_user: "",
  demo_password: "",
  notes: "bla bla"
)

Still getting
[!] The request could not be completed because:
Enter a demo account user name and password. Enter a demo account user name and password

I just pushed a new release, could you try https://github.com/fastlane/deliver/releases/tag/1.11.2

Having the same error on 1.11.2

I m with @iPavel92, Same demo account error

Just out of curiosity and clarification: have anyone tried setting demo_user and demo_password to non-empty strings?

@iPavel92 Thanks for following up. Have you tried entering a non-empty string as suggested above? We are still going to look into this. Thanks!

@TKBurner and @fwal I entered this:
app_review_information(
  first_name: "my name",
  last_name: "my last name",
  phone_number: "+1<PHONE_NUMBER>",
  email_address<EMAIL_ADDRESS>  notes: ""
)

@fwal never tried. It wouldn't help because of this condition: https://github.com/fastlane/fastlane/pull/4266
build_info['reviewAccountRequired']['value'] = ((review_user_name || "").to_s + (review_password || "").to_s).length > 0

If I add --skip_metadata flag, the review information skip to? I suspect it skip both.

Yes, I'm in the same boat as @iPavel92.
Getting this error. I don't have demo_user or demo_password set in app_review_information.  On deliver 1.11.2.
  [!] The request could not be completed because:
	Enter a demo account user name and password. Enter a demo account user name and password.

@kaomte Thanks for following up. We will have a look and update on this thread. Thanks!

@TKBurner I finally got things working on my end. I misunderstood how the fix worked. I was thinking that during the app submission that deliver would uncheck the box. Now I realize the the box is checked/unchecked when the build information is updated, not during submission. I had updated build information with an older version of deliver and after the fix was submitting with the latest version of deliver and still getting the same error.
Now, after updating the build information with the latest deliver, submission works fine.

Yeah great to hear @kaomte 👍

@kaomte @gran33 @iPavel92 could you please share the final, working Deliverfile that you are using which allows unattended delivery?

This issue is closed but I am still getting this issue. Is there a way to have deliver uncheck that box or do we have to put in some kind of dummy info for user and pass?
Our app does not need a test user, so normally we uncheck the box and leave it at that. How does this work with deliver?

@evilDave Thanks for following up. You need to update your build information for the app first, and then the box should be unchecked by default. Thanks!

Excellent, that is it. It seems like if you create an app version manually, this checkbox gets checked by default now. Also if you create a version with deliver and let it keep the defaults for build information, this box will also be checked.
I now have deliver set up to create new versions for me so as long as I specify, as you say, the app_review_information then the box will be unchecked.
Thanks!

@fulldecent this works for me to fix the demo account issue
app_review_information(
  first_name: "Rob",
  last_name: "MY_NAME",
  phone_number: "MY_NUMBER",
  email_address: "MY_EMAIL",
  demo_user: "",
  demo_password: "",
  notes: ""
)

@ConfusedVorlon:
I'm having some issues figuring out where this fits in my Fastfile. I'm using Pilot, not deliver

I keep that in my deliverfile. I'm not familiar with pilot - but worth trying the deliverfile to see if it uses the same source.

@simme Did you have a chance to give this a test? You might need to run both commands to get the outcome you are looking for. Hope you have a wonderful day! 👍

Is this info used by pilot? I don't think I have seen any such checkbox when adding a build to testflight.

I put the stuff that ConfusedVorlon posted into a Deliverfile (modified for my needs obviously). Didn't work.
There's a checkbox when pushing a build out to external testers.

@simme Can you share you full input and output? First run sudo gem update fastlane. Thanks!

I'm just starting up with Pilot so I might be doing something wrong, but I'm also still hitting this. I uncheck the Demo Account checkbox it explicitly in my uploaded (and approved) TestFlight builds, but when creating the next one with Pilot, the checkbox is always there.
fastlane actions pilot
doesn't indicate there's any way of setting this, or of passing app_review_information via the equivalent of a Deliverfile?

I too have just pushed a build to TestFlight and the checkbox has become checked. I do have the entries in the deliverfile that prevent the box from being checked by deliver.

@evilDave Thanks for reaching out. Does this occur every time and on multiple apps? Thanks!

@TKBurner Is it expected that pilot will pick up the app_review_information from the Deliverfile?

To answer my own question after looking at the code, it seems that pilot does not read in the Deliverfile. So where exactly are we supposed to set the demo account info assuming we actually have one? Perhaps there needs to be a Pilotfile?

@TKBurner yes it's happening on a few projects. I do believe that I've found that once you go into iTunes connect and manually uncheck the box, new builds have it unchecked.
I second the notion that what we probably need is a pilotfile with the appropriate section in it.

@evilDave I've marked this with a few more flags to see if anyone is interested in implementing this. Thanks for working with us!

I'm planning on doing a pull request to add a Pilotfile (or to read the Deliverfile... not sure which makes more sense), but to be honest I'm terrified of breaking my current fastlane setup when checking out a fork instead.

Let me know where you are doing this and I will check it out of your repo and try it out. As for which file, I would suggest Pilotfile.

The reason I have against a separate Pilotfile is that the app_review_information is mostly likely identical to the one you'd use for deliver. I think it makes more sense to add any pilot-specific deliverable fields to the Deliverfile. I suppose both could source some other common file, though.

What would you do if the app_review_information was not the same for the testflight build and the production release? This could easily be true for anyone that does need a demo user login.
Once could presumably use the tools separately also... The fact that for one tool, pilot, the settings file is called Deliverfile might be a point of confusion.

Yeah, you're right. I'll make it Pilotfile, and anyone with commonality between the two will just have to source a third file.


F# 4.0 not on homebrew

It should be added so that you can install F# just like any other programming language.

I don't think F#3.1 installs properly on home brew yet either.

On 26 Jul 2015, at 22:52, Henrik Feldt<EMAIL_ADDRESS>wrote:
It should be added so that you can install F# just like any other programming language.
—
Reply to this email directly or view it on GitHub.

F# 3.1 installs ok, and has done for a while. There is a reported issue with the project scaffold, see https://github.com/fsharp/fsharp/issues/451. Any help in investigating would be appreciated.

checking along the #451 angle.  See #451.

This is fixed, fsharp is now part of "mono" homebrew


various fixes from e2e test

This addresses the issues I described in #246.

It probably makes sense to look at the commits one by one since they are mostly unrelated. It just felt like lots of overhead to create a PR for each of those. But let me know if you prefer me to split them.


Move the P Query Parameter to the URL

Being that p is a custom parameter, it fits better in the URL then the query parameters.  It is a more "standards compliant" way.

@spottedmahn : Thanks for your contribution! The author, @davidmu1, has been notified to review your proposed change.

Thoughts 💭?

#sign-off


Wrong online players after server crash and reboot

I have little problem with online players on server. When my server crash and restart, the bot shows the last number of players on the server, not the current number (this should be zero on startup). To fix this, I need to restart bot after Satisfactory server crash. It is possible to fix this issue?

Hi @BartekSz95,
Thank you for raising this. Yes, it should. When the Satisfactory Dedicated Server crashes, it should create a new log file. This bot should detect that and reset the player count. Here is the code that should do that: https://github.com/DJWoodZ/Satisfactory-Discord-Bot/blob/main/bin/server.js#L211
Assuming you are referring to the activity status within Discord which says 'Playing online: 2/4' or similar, that can take a few moments to update sometimes.
Assuming you have tried waiting a minute or two before restarting this bot, the next thing to check would be whether the Satisfactory Dedicated Server log is actually being re-created correctly when it crashes. You can confirm this by looking at the files in the Satisfactory Dedicated Server's log directory and the timestamps shown within the files. If the Satisfactory Dedicated Server does not appear to be rotating the log file properly, it's most likely due to a file permission issue that is preventing it from doing so.
Once you have confirmed that the Satisfactory Dedicated Server is creating a new log file with the same filename following a crash, the next thing you could try would be setting this option to true, which will force it to use a method for monitoring the file which can sometimes be more reliable.
SATISFACTORY_BOT_LOG_USE_WATCH_FILE=true

If none of the above helps, please can you provide details to help me to further understand and possibly re-create the issue.
Firstly, can you provide details from the Discord bot's log file around the time a crash occurs (several minutes before and after).
Secondly, can you provide some details of your setup and how you are running both the Satisfactory Dedicated Server and this bot. For example, which branch of the game are you running (stable vs experimental), is the bot accessing the log file in an unusual way (e.g. via a mounted remote file system or similar), etc.
Thanks.


Check crowbarctl upgrade repocheck return code

It may happen that 'crowbarctl upgrade repocheck crowbar' fails but we
don't catch that error. Added an explicit check for the return value so
later on we can check the command output.

That's indeed better. I also thought safely would apply for the grep command, so I wasn't hoping for such simple solution.


OutOfMemoryError when run eval.py

Hi @drprojects
Thank you for your research, it is very useful.
I completed training the model on s3dis data and got the checkpoint. But when I run the command line for evaluate the model, the log shows as bellow.
I am using RTX 4090 Ti, my GPU memory is free at that time (~24 GB).
torch.cuda.torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate 7.62 GiB (GPU 0; 23.62 GiB total capacity; 15.77 GiB already allocated; 7.08 GiB free; 15.78 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CON: CUDA out of memory. Tried to allocate 7.62 GiB (GPU 0; 23.62 GiB total capacity; 15.77 GiB already allocated; 7.08 GiB free; 15.78 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CON

Oh, I move to higher GPU memory server, I can run eval.py. I test with public checkpoints,
the GPU memory consumption is ~ 48GB. Could the model run eval.py on 24GB GPU

Hello, I've also been trying to test the evaluation script on DALES, and I also run into a OutOfMemoryError, this time in the  demo_dales.ipynb file, fourth cell:
OutOfMemoryError: CUDA out of memory. Tried to allocate 22.00 MiB (GPU 0; 10.75 GiB total capacity; 10.44 GiB already allocated; 18.50 MiB free; 10.54 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF

Hi @vvuonghn thanks for your interest in the project.
Can you please clarify:

which model (SPT, SPT-nano) did you train on which dataset (S3DIS, KITTI-360, DALES) ? (ie which python src/train.py ... command did you use)
are you evaluating on the same dataset ?
are you using the same GPU at inference time as the one you used at train time ?
have you made any modification to the project, even minor ? (ie what is you git diff 2e155e7c95cb88b24c30c7faaf108951176e17fd)

Hi @drprojects
I am using the same gpu for training and inference. (one gpu NVIDIA 4090TI - 24 GB). The training process completed and report score. But when I run eval.py (this bug was showed)
I am using S3DIS. my machine have a gpu, I try to set export CUDA_VISIBLE_DEVICES=0 and the bug still hapend

CUDA_LAUNCH_BLOCKING=1 is a debug env variable used to block kernel launches and to report the proper stacktrace once an assert is triggered. You should not use it in production, but only during debugging. In other words, when you debug code running on CUDA, you need to set CUDA_LAUNCH_BLOCKING=1 if you want to have access to the proper traceback error message. Otherwise the message you get may be unhelpful in locating the source of error.
I had a look at the logs you shared. I notice you are using the s3dis_11g config at training but not at evaluation time. This is probably the reason for your memory error. If you have a look at the difference between these two configs, you will notice that they prepare the data differently.
The provided pretrained weights are trained with s3dis and not s3dis_11g. We do not provide pretrained weights for s3dis_11g so you will have to train yours and evaluate them using the s3dis_11g config (and not the s3dis as you did).
Also, using the s3dis_11g on a 24G GPU is a waste of memory. I recommend you use the s3dis config as a default instead and modify some settings to fit into a 24G GPU. Have a look at the README for a list of settings you can play with to mitigate CUDA errors. I do not have a 24G GPU at hand to help you with that, but I recommend using datamodule.xy_tiling=2 or 3 for a start, and playing with datamodule.sample_graph_k and datamodule.sample_graph_r from there. Have a look and the configs and code to get a grasp of what each does.

I trained s3dis_11 on 11g 1080Ti, and I have a same error when eval. I have fixed it by modify datamodule.pc_tiling: null
--->pc_tiling: 3


What is the pulse container for?

In kube-configs/blockchain.yaml the pod spec for Deployment named blockchain-orderer has a container named pulse. The container executes the following script (lines added for readability):
UUID=$(cat /proc/sys/kernel/random/uuid) && while [ true ];
do
    curl https://ics-endpoint.mybluemix.net/pulse/beat/$UUID;
    sleep 10;
done

What is this for?

The pulse container is sending a heart beat so someone it can be known how many instances are running.


begin significant updates to test suite structure

add ts-mocha

add several new npm test scripts:
test:browser-specific, test:browser-universal, test:node-specific,
test:node-universal, test:browser-all, test:node-all, test:module

add an initial implementation for the node tests

npm test script runs module tests (module import and require), all node
tests, and the original PhantomJS test suite

new test scripts will be located in a 'test' directory off of the
directory that contains the module being tested. tests that should
perform equally in browser and node will be in the main 'test'
directory, while browser and node specific tests will have their own
directories.
Ergo, the structure should eventually look something like:

src/common/test - universal tests for modules in src/common
src/common/test/node - node specific tests for modules in src/common
src/common/test/browser - browser specific tests for modules in
src/common

updates to browser based testing will be in a future changeset

Events tests (test/events.spec.ts) moved to
src/common/test/events.spec.ts

Added unit test for src/quagga/transform as
src/quagga/test/transform.spec.ts

test/tsconfig.json is still used as the base tsconfig for running tests.
It is now running with module type 'commonjs' to avoid odd
"import can only be used in a module" types of errors.

add mocha to types in main tsconfig, to prevent tests from appearing as
files full of errors in editor

cheers, this actually completes on the CI.
New test setup is working great, although coverage is not exactly brilliant yet.  I'm hoping that we can get code coverage from both browser and node nicely into the same report, without having to look at two different reports.  That's not exactly working well.
The integrationtests from the old suite are still being run, there's some changes that need to be done to make asynchronous tests work properly in cypress, and i'm hoping that we can also find a way to run them in node as well without having to duplicate them.
There's plenty of code that doesn't have a clear test being run on it, but coverage reports should reveal that all, hopefully.
CameraAccess tests also suffer from being asynchronous and will need to be changed to fit cypress.  At least those are browser only, so it shouldn't be too difficult to handle that, and make sure that we write a proper test to ensure that those fail properly in node.

hmm.  this is very weird.  on my laptop where i wrote this, it mostly works for coverage reports, although it looks weird.  on my desktop, i just cloned this, ran it, and all it gives me coverage for are the spec files .. despite the spec files being specifically excluded.

Should be done with this just as soon as I get one of the actual barcode reader tests in in such a way that it runs in both node and browser.  After the feature is validated, the rest will get to come in in separate pull reqs.

I will not close #75 until after all the tests are moved to it, and then we can dump all the PhantomJS support and stuff like that, get some of the other packages moved into the modern era .. and really get testing and coverage up to modern standards.


Project disabled as can't find git

Not sure if others are experiencing this but due to an apparent bug in Azure, the Application Pool path variable for Git is showing "D:\Program Files (x86)\Git\cmd' when in fact the 64 bit version of Git has been installed.   This means the the Projects functionality of node-red will not work as it cannot find the Git executable.
This can be worked around by adding the following line to the server.js file:
process.env.Path = 'D:\\Program Files\\Git\\cmd;D:\\Program Files\\Git\\usr\\bin;' + process.env.Path;

Thank you for the tip. This is an essential bit if you want to use projects in Node-Red. I use them all the time and this makes it very easy to change your dashboards to a different project.
I would suggest this be added a default. Also the settings.js file is missing the commented out section to enable projects. Add this if you want to enable projects along with the server.js suggestion.
editorTheme: {
       projects: {
           enabled: true
       }
   }

The latest node-red it now at 0.20.7, so it would be nice if these things were updated. This is such a useful project. Thank you for sharing!

Nice suggestions, thanks. I added the path and enabled projects.


Could not load fightw.hdfs

Hi,
Thanks for sharing your great work.
I'm trying to run predict_video1/2 without any success
I'm getting this warning:
2021-04-08 14:02:28.227955: W tensorflow/core/util/tensor_slice_reader.cc:95] Could not open ./fightw.hdfs: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
It may affect the results? it's not accurate at all, not even close.

Same with me
Kindly share the solution!


Capitalize "enable" and "disable"

This is under Whitelist tab

Also, put Origin/Method into two lines, same as Amount(IOTX)


Updated JOU's Duplicate card generation issue

Created a function to generate unique indexes. The indexes are then turned into cardsobjects before being added to the booster class

Sorry, I already fixed the duplicate issue with the generic pack making utility. I hadn't pushed it up yet. It's in now


⬆ Update development requirement for FastAPI from ^0.68.0 to ^0.68.1

SQLmodel requires FastAPI version 0.68.1, as this has support for read_with_orm_mode. Issue raised describing this is issue #37.
This is required for backref to searched and added to the Pydantic models.

Cool, thank you! :rocket: :cake:


converted ScriptOpts to v2

Converted ScriptOpts to v2.
I'm not sure if setting the working dir is working. Something about running through a pipe?
But, setting a different AutoHotkey executable is working.

I'm not sure if setting the working dir is working. Something about running through a pipe?

AHKv2 sets the working directory to A_ScriptDir by default, with the original working directory kept in A_InitialWorkingDir. If you have not run tests checking that variable, it may be that it works as designed and you did not notice because of the confusion this change has caused.


changeFieldControl doesn't allow multiple fields to be updated

Expected Behavior
Be able to change multiple editor interface in multiple fields together
Actual Behavior
Error: Cannot save CT {content type} because it does not exist
Steps to Reproduce
Executing the below migration script returns an error:
import { MigrationFunction } from 'contentful-migration';

export = function(migration) {
  // News Content Type with fields showAt and hideAt
  const news = migration.editContentType('news');
  ['showAt', 'hideAt'].forEach(fieldId => {
    news.changeFieldControl(fieldId, 'builtin','datePicker', {
      format: 'time'
    });
  });
} as MigrationFunction

I get the following error:
Error: Cannot save CT news because it does not exist
Context
I can replicate this with both changeFieldControl and deprecated changeEditorInterface.
Potentially similar to issue listed here: https://github.com/contentful/contentful-migration/issues/150
Environment

Node Version: 10.15.0
Package Manager Version: 6.4.1
Operating System: macOS Mojave - 10.14.6
Package Version: 0.19.0

Also seeing this issue:
const block = migration.editContentType('block');

block.changeFieldControl('title', 'singleLine', 'builtin', {
    helpText: 'Only shown in the admin.',
});

block.changeFieldControl('isSquareAspect', 'singleLine', 'builtin', {
    helpText: 'If Yes, block will remain square after the mobile break. Useful for blocks with a Background image set.',
});

Displays this error when running the migration:
Error: Cannot save CT block because it does not exist

I am also seeing this issue in contentful-migration 0.19.8 with the error:
Error: Cannot save the content type (id: tag) because it does not exist
Single field control changes work fine but multiple break it.

this is solved in v1.0.2


syncthing: don't run in host network mode, specify uid/gid

What this PR does / why we need it:

adds ability to specify as which user syncthing should run (files can have owner other then root)
removes requirement to run syncthing in host network mode.

:+1:


[BUG] WingetUI doesn't remember Administrator privileges preferences; resets to random settings every startup

Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have tested that this issue has not been fixed in the latest (beta or stable) release.
[X] I have checked the FAQ section for solutions
[X] This issue is about a bug (if it is not, please use the correct template)

Describe your issue
I am using the newest WingetUI, v2.0.1.
I have my "Administrator priveleges preferences" set up to the following:

[X] Ask only once for administrator privileges (not recommended)
[X] Always elevate Winget installations by default
[ ] Always elevate Scoop installations by default
[ ] Always elevate Chocolately installations by default
[ ] Always elevate Pip installations by default
[ ] Always elevate Npm installations by default
[ ] Use installed GSudo instead of the bundled one (requires app restart)

I only use WingetUI for Winget.  I have not enabled support for Scoop, Chocolatey, Pip or Npm.
After a reboot of my PC, WingetUI will start up in the system tray automatically as expected.  However, when I bring up the UI, then go to Settings -> Adminstrator privileges preferences, random checkboxes are checked, many times, the Winget option is unchecked and one or many of the other options (Scoop, Chocolatey, Pip or Npm) will be checked instead.
Steps to reproduce the issue
Set desired options under Settings -> Adminstrator privileges preferences.  Set WingetUI to autostart to the system tray.  Perform a reboot of your PC.  Check the options under Settings -> Adminstrator privileges preferences; they will differ from the options you manually specified; even with support for those other package managers not enabled at all in WingetUI.
WingetUI Log
Can't disconnect
🟢 Install tab loaded successfully
🔵 Reloading sources...
🔵 Reloading Winget sources...
🟢 Searching for string ""
Can't disconnect
Can't disconnect
🟢 Install tab loaded successfully
🔵 Starting Winget search for installed packages
🟢 Searching for string ""
Can't disconnect
🟢 Settings tab loaded!
🟢 About tab loaded!
🟢 Main application loaded...
Win32Mica Error: win32 version 19045 is not supported
🟢 Total packages: 4951
🟢 Winget packages cached successfuly
🔵 Reloading Scoop sources...
🔵 Starting Winget search for updates
🟢 Winget search for installed packages finished with 147 result(s)
🟢 Searching for string ""
🟢 Searching for string ""
🟢 Total packages: 147
🔵 Announcement URL: https://www.marticliment.com/resources/wingetui.announcement
🟢 Winget search for updates finished with 82 result(s)
🟡 Package AutoHotkey.AutoHotkey is ignored
🟡 Package BlueStack.BlueStacks is ignored
🟡 Package DownloadHelper.VdhCoApp is ignored
🟢 Searching for string ""
🟢 Searching for string ""
🟢 Total packages: 4
🔵 Image URL: https://www.marticliment.com/resources/translate.png
🔵 Loading log...

Package Managers Logs
Not relevant.

Relevant information
I have tried uninstalling and reinstalling WingetUI numerous times, does not help.
This bug affects not only my Windows 10 desktop, but my Windows 11 desktop, Windows 10 laptop and Windows 11 laptop as well.
Screenshots and videos
No response

An update.  I've noticed that I don't even need to restart my PC to see the admin settings change.  Just quitting the application, then reopening it will cause the same random checkbox issue again.

This issue was already reported, and the fix has now ben implemented.
However, changes will be effective when the next release is published

Link to the original issue?

Try installing WingetUI 2.0.2, this issue has been fixed


Widget - can't change size with kiss launcher

Describe the bug
With the kiss launcher, the rain wiget size is less than one line and can't be changed (no enlarge/reduce option). The text is therefore not readable.
Unlike other widgets, I can't change the size of the widget (the only options are move up, move down or delete widget, no enlarge or reduce option).
With the standard launcher, the size of the rain widget can be changed.
Smartphone (please complete the following information):

Device: Samsung Galaxy S10+
OS: Android 13

Additional context
Since I'm not sure wether this is a bug of the rain widget or the kiss launcher, I will submit the issue to both apps.

I have this too, on the pixel 9 top and bottom are cropped


Make inspector text options more widely available.

Fixes #1562
Problem:
We've been using a permit list for the inspector sections, which means it's easy to miss out elements that ideally should have sections like the font sections.
Fix:
For the text sections we now use a deny list, with only img and video in it.
Commit Details:

Fixes #1562.
Reworked StyleSubSectionForType to support permit, deny or allow all
options.
Updated useIsSubSectionVisible with the above changes.
Put img and video in as deny options for the text and textShadow
inspector sections.
Put img in for the permit list of the img inspector section.
Every other inspector section set with the allow all option.

I'm merging this so it's ready for tomorrow morning!


Added exception when line-endings are incorrect

Aims to make line-ending errors more visible by raising an exception.
Fixes #7, in a round-about way. :smiley:

Great! Thanks! :)


Overlay not moving with canvas

When resizing the window for the multiple canvas demo, canvases are repositioned, but their overlay DIVs remain in their initial positions. Need to trigger overlay resizings from window size changes, not just canvas size changes.

Fixed in https://github.com/xeolabs/xeoengine/commit/bf30116f2dc64fa0f911f71dfe0105d68262e481


[MB-15339] uploads a migration to correct the movehq sha

Warnings

:warning:
Please include a description of your PR changes.

Messages

:book:
:link: MB-15339

  Generated by :no_entry_sign: dangerJS against ccc872fe17e4fbbebb881792a09fb9c60cbf3798


Add retries to GH release creation

To avoid failing due to transient network/server errors, retry the
release a couple time if it fails.
Resolves: #360
Signed-off-by: Mike Kolesnik<EMAIL_ADDRESS>

I think this is worth backporting to 0.13 and 0.12 as it can be quite useful

Backported as #414 and #415


AWS ES - Datetime Field is imported as String in Explore Screen

When Querying an index alias on AWS ES instance with a timestamp datatype field, SQL LAB displays the correct column datatype. But when using explore to create a chart, the field is imported as a String.
Expected results
It should be imported as Date/Time.
Actual results
Imported as String.
Screenshots
SQL LAB:

Explore:

Environment
(please complete the following information):

superset version: 1.0.1
python version: 3.8
node.js version: 12

resolved by: https://github.com/apache/superset/pull/14894

Looks like this was resolved, but never closed.


[SPARK-40434][SS][PYTHON] Implement applyInPandasWithState in PySpark

What changes were proposed in this pull request?
This PR proposes to introduce the new API applyInPandasWithState in PySpark, which provides the functionality to perform arbitrary stateful processing in Structured Streaming.
This will be a pair API with applyInPandas - applyInPandas in PySpark covers the use case of flatMapGroups in Scala/Java API, applyInPandasWithState in PySpark covers the use case of flatMapGroupsWithState in Scala/Java API.
The signature of API follows:
# call this function after groupBy
def applyInPandasWithState(
    self,
    func: "PandasGroupedMapFunctionWithState",
    outputStructType: Union[StructType, str],
    stateStructType: Union[StructType, str],
    outputMode: str,
    timeoutConf: str,
) -> DataFrame

and the signature of user function follows:
def func(
    key: Tuple,
    pdf_iter: Iterator[pandas.DataFrame],
    state: GroupStateImpl
) -> Iterator[pandas.DataFrame]

(Please refer the code diff for function doc of new function.)
Major design choices which differ from existing APIs:

The new API is untyped, while flatMapGroupsWithState in typed API.

This is based on the nature of Python language - it's really duck typing and type definition is just a hint. We don't have the implementation of typed API for PySpark DataFrame.
This leads us to design the API to be untyped, meaning, all types for (input, state, output) should be Row-compatible. While we don't require end users to deal with Row directly, the model they will use for state and output must be convertible to Row with default encoder. If they want the python type for state which is not compatible with Row (e.g. custom class), they need to pickle and use BinaryType to store it.
This requires end users to specify the type of state and output via Spark SQL schema in the method.
Note that this helps to ensure compatibility for state data across Spark versions, as long as the encoders for 1) python type -> python Row and 2) python Row -> UnsafeRow are not changed. We won't change the underlying data layout for UnsafeRow, as it will break all of existing stateful query.

The new API will produce Pandas DataFrame to user function, while flatMapGroupsWithState produces iterator of rows.

We decided to follow the user experience applyInPandas provides for both consistency and performance (Arrow batching, vectorization, etc). This leads us to design the user function to leverage pandas DataFrame rather than iterator of rows. While this leads inconsistency of the UX from the Scala/Java API, we don't think this will come up as a problem since Pandas is considered as de-facto standard for Python data scientists.

The new API will produce iterator of Pandas DataFrame to user function and also require to return iterator of Pandas DataFrame to address scalability.

There is known limitation of applyInPandas, scalability. It basically requires data in a specific group to be fit into memory. During the design phase of new API, we decided to address the scalability rather than inheriting the limitation.
To address the scalability, we tweak the user function to receive an iterator (generator) of Pandas DataFrame instead of a single Pandas DataFrame, and also return an iterator (generator) of Pandas DataFrame. We think it does not hurt the UX too much, as for-each and yield would be enough to deal with the requirement of dealing with iterator.
Implementation perspective, we split the data in a specific group to multiple chunks, which each chunk is stored and sent as "an" Arrow RecordBatch, and then finally materialized to "a" pandas DataFrame. This way, as long as end users don't materialize lots of pandas DataFrames from the iterator at the same time, only one chunk will be materialized into memory which is scalable. Similar logic applies to the output of user function, hence scalable as well.

The new API also bin-packs the data with multiple groups into "an" Arrow RecordBatch.

Given the API is mainly used for streaming workload, it could be high likely that the volume of data in a specific group may not be huge enough to leverage the benefit of Arrow columnar batching, which would hurt the performance. To address this, we also do the opposite thing what we do for scalability, bin-pack. That said, an Arrow RecordBatch can contain data for multiple groups, as well as a part of data for specific group. This address both aspects of concerns together, scalability and performance.
Note that we are not implementing all of features Scala/Java API provide from the initial phase. e.g. Support for batch query and support for initial state will be left as TODO.
Why are the changes needed?
PySpark users don't have a way to perform arbitrary stateful processing in Structured Streaming and being forced to use either Java or Scala which is unacceptable for users in many cases. This PR enables PySpark users to deal with it without moving to Java/Scala world.
Does this PR introduce any user-facing change?
Yes. We are exposing new public API in PySpark which performs arbitrary stateful processing.
How was this patch tested?
N/A. We will make sure test suites are constructed via E2E manner under SPARK-40431 - #37894

cc. @viirya @HyukjinKwon
Please take a look into this. Thanks. I understand this is huge and a bit complicated in some part, logic around binpack/chunk. Please feel free to leave comments if the code comment isn't sufficient to understand, I'll try my best to cover it.

Will take a close look next Monday in KST.

I tried to add method level doc as many as possible, except the case I think it's unnecessary (I might still miss some pieces).
I don't go with the approach trying to explain all of the parameters with types though, for reasons:

For Python code, it'd be really hard to maintain the doc in sync with the code.
For Scala/Java we have been omitting the explanation of parameters or even methods if it's obvious from the name.

In both languages, we strongly encourage to have method doc and parameter explanation for public APIs. Here we technically add only one public method in group_ops, and one public class GroupState in PySpark. Others are all internal and private.

https://github.com/HeartSaVioR/spark/actions/runs/3098349789/jobs/5019498380
BasicSchedulerIntegrationSuite.super simple job
org.scalatest.exceptions.TestFailedException: Map() did not equal Map(0 -> 42, 5 -> 42, 1 -> 42, 6 -> 42, 9 -> 42, 2 -> 42, 7 -> 42, 3 -> 42, 8 -> 42, 4 -> 42)
 [Check failure on line 210 in YarnClusterSuite](https://github.com/HeartSaVioR/spark/commit/f1000487960fa19aff9979211db68e63ec4384e0#annotation_4680752580)

YarnClusterSuite.run Spark in yarn-client mode with different configurations, ensuring redaction
org.scalatest.exceptions.TestFailedDueToTimeoutException: The code passed to eventually never returned normally. Attempted 190 times over 3.001220665 minutes. Last failure message: handle.getState().isFinal() was false.
 [Check failure on line 210 in YarnClusterSuite](https://github.com/HeartSaVioR/spark/commit/f1000487960fa19aff9979211db68e63ec4384e0#annotation_4680752582)

YarnClusterSuite.run Spark in yarn-cluster mode with different configurations, ensuring redaction
org.scalatest.exceptions.TestFailedDueToTimeoutException: The code passed to eventually never returned normally. Attempted 190 times over 3.001046460266666 minutes. Last failure message: handle.getState().isFinal() was false.
 [Check failure on line 210 in YarnClusterSuite](https://github.com/HeartSaVioR/spark/commit/f1000487960fa19aff9979211db68e63ec4384e0#annotation_4680752584)

YarnClusterSuite.yarn-cluster should respect conf overrides in SparkHadoopUtil (SPARK-16414, SPARK-23630)
org.scalatest.exceptions.TestFailedDueToTimeoutException: The code passed to eventually never returned normally. Attempted 190 times over 3.0008878969166664 minutes. Last failure message: handle.getState().isFinal() was false.
 [Check failure on line 210 in YarnClusterSuite](https://github.com/HeartSaVioR/spark/commit/f1000487960fa19aff9979211db68e63ec4384e0#annotation_4680752586)

YarnClusterSuite.SPARK-35672: run Spark in yarn-client mode with additional jar using URI scheme 'local'
org.scalatest.exceptions.TestFailedDueToTimeoutException: The code passed to eventually never returned normally. Attempted 190 times over 3.0009406496 minutes. Last failure message: handle.getState().isFinal() was false.

None of test failures is related to the change of this PR. Since we update the PR again let's see the build.

My comments are just nits. I will merge this in first to move forward.
Merged to master.

Thanks @HyukjinKwon and @alex-balikov for thoughtful reviewing and merging!
I'll handle the latest comments as a follow-up PR.


Playlist download: Unable to extract title

Hi all,
Have an issue downloading a playlist:
youtube-dl "https://www.youtube.com/watch?v=M4ppCrnhKrM&list=ELm_tYSDyeORg" --verbose
Here's the output:
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['https://www.youtube.com/watch?v=M4ppCrnhKrM&list=ELm_tYSDyeORg', '--verbose']
[debug] Encodings: locale 'UTF-8', fs 'UTF-8', out 'UTF-8', pref: 'UTF-8'
[debug] youtube-dl version 2014.02.17
[debug] Python version 2.7.6 - Linux-3.13.0-44-generic-x86_64-with-Ubuntu-14.04-trusty
[debug] Proxy map: {}
[youtube:playlist] Downloading playlist PLELm_tYSDyeORg - add --no-playlist to just download video M4ppCrnhKrM
[youtube:playlist] ELm_tYSDyeORg: Downloading page #1
WARNING: [youtube:playlist] ELm_tYSDyeORg: Playlist page is missing OpenGraph title, falling back ...
ERROR: Unable to extract title; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 1511, in _real_extract
playlist_title = self._og_search_title(page)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 428, in _og_search_title
return self._og_search_property('title', html, **kargs)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 416, in _og_search_property
escaped = self._search_regex(self._og_regexes(prop), html, name, flags=re.DOTALL, **kargs)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 356, in _search_regex
raise RegexNotFoundError(u'Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract OpenGraph title; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/youtube_dl/YoutubeDL.py", line 493, in extract_info
ie_result = ie.extract(url)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 158, in extract
return self._real_extract(url)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 1517, in _real_extract
r'(.*?)', page, u'title')
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 366, in _html_search_regex
res = self._search_regex(pattern, string, name, default, fatal, flags)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 356, in _search_regex
raise RegexNotFoundError(u'Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract title; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.

You are using an outdated version of youtube-dl (one year old), Youtube has done some breaking changes since then. Please upgrade to the last version, see our FAQ if you have problems updating.

Thanks

Thanks
On Fri, Mar 6, 2015 at 7:36 PM, Jaime Marquínez Ferrándiz <
<EMAIL_ADDRESS>wrote:

You are using an outdated version of youtube-dl (one year old), Youtube
has done some breaking changes since then. Please upgrade to the last
version, see our FAQ
https://github.com/rg3/youtube-dl/blob/master/README.md#how-do-i-update-youtube-dl
if you have problems updating.
—
Reply to this email directly or view it on GitHub
https://github.com/rg3/youtube-dl/issues/5148#issuecomment-77589522.


LimitSubqueryOutputWalker: fix aliasing of property in OrderBy from MappedSuperclass

http://www.doctrine-project.org/jira/browse/DDC-3679

Thanks - i'll merge after nitpick :+1:

I'm not sure if it's fixed properly. Is this enough?

@fprochazka I think so - though there's no functional test for this case...

@zeroedin-bill now I'm thinking it might be better to reverse the condition and only change the alias if the entity is in inheritance and it's the type of inheritance where you use multiple tables.

@zeroedin-bill now I'm thinking it might be better to reverse the condition and only change the alias if the entity is in inheritance and it's the type of inheritance where you use multiple tables. Because it still might break with STI.

@fprochazka we need more functional test cases...

Sure, there is never enough tests :) But I won't be able to write more right now. Soonest would be somewhere around monday.

@fprochazka For now I'll merge this. I'd really appreciate if you could write some functional tests on Monday to cover this scenario if you have time!
Thanks!

I'll try!


Update force field in README and remove AlkEthOH

I noticed the force field in the README was quite old, and since this is the first thing people see when going to the project, I thought it would be useful to keep this up to date. I also removed a reference to AlkEthOH because, I think, that's also "historical" at this point (and the phrasing made it seem like that was the force field to use for small molecules containing those functional groups, whereas I believe everyone should be using the official force fields at this point).

[N/A ] Tag issue being addressed
[N/A ] Add tests
[N/A ] Update docstrings/documentation, if applicable
[N/A ] Lint codebase
[N/A ] Update changelog

Thanks for the submission, @slochower. I've merged the changes into a branch, and added some more in #710 -- I'll take it from here.


Generate index pages for download.docker.com

The apt.dockerproject.org and yum.dockerproject.org repositories have index pages, allowing people to navigate the repositories, and easily find the RPM's / deb packages.
download.docker.com does not have index pages, which leads to a lot of confusion (e.g. https://github.com/docker/docker/issues/31940), because trying to browse the repository shows 403 access denied and an ugly XML error message.
It also makes it difficult to find out which packages are available, and which architectures are supported (also see https://github.com/docker/docker.github.io/issues/2085)
ping @andrewhsu @dmp42 PTAL

Understood. I'll work towards getting those index up soon.

Directories are now browsable for the linux repos for docker-ce: https://download.docker.com/linux/

There is an error with the following index:
From instruction for package installation:
https://docs.docker.com/engine/installation/linux/ubuntu/#install-from-a-package
Click this link:
https://download.docker.com/linux/ubuntu/pool/stable-17.03/amd64/
Error (as shown in iexplore):
404 Not Found
•Code: NoSuchKey
•Message: The specified key does not exist.
•Key: linux/ubuntu/pool/stable-17.03/amd64/index.html
•RequestId: EB24CFD173CEAD6B
•HostId: VdkPH8m6XMFPhYXJ2tRRQxVtnGPNLpsASSjvu3BlgRRRGjSGky4c+of5bMIFKZrgml44z4+7ar0=
An Error Occurred While Attempting to Retrieve a Custom Error Document
•Code: NoSuchKey
•Message: The specified key does not exist.
•Key: error.html

Looks like that should be https://download.docker.com/linux/ubuntu/dists/xenial/pool/stable/amd64/ (for xenial)

Agreed, then it looks like this issue can be closed & follow-up actions:
Update link @ https://docs.docker.com/engine/installation/linux/ubuntu/#install-from-a-package

Thanks @andrewhsu !


python36Packages.node-semver: 0.4.2 -> 0.5.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/python3.6-node-semver/versions.
meta.description for python36Packages.node-semver is: '"A port of node-semver"'.

Checks done (click to expand)

built on NixOS

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.5.0 with grep in /nix/store/ib7nxnr38854wix5an029d9nqnqvgy4a-python3.6-node-semver-0.5.0

directory tree listing: https://gist.github.com/2324a9e99b108f5478750094e153bfac

du listing: https://gist.github.com/94433b1b6a4030c85648f0503ceddf60

Rebuild report (click to expand)

8 total rebuild path(s)
2 package rebuild(s)
2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
python27Packages.node-semver
python36Packages.node-semver

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ib7nxnr38854wix5an029d9nqnqvgy4a-python3.6-node-semver-0.5.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A python36Packages.node-semver https://github.com/r-ryantm/nixpkgs/archive/ec9b28ea9ec87872bde73f93e7929961f5574d4e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ib7nxnr38854wix5an029d9nqnqvgy4a-python3.6-node-semver-0.5.0
ls -la /nix/store/ib7nxnr38854wix5an029d9nqnqvgy4a-python3.6-node-semver-0.5.0/bin

Success on aarch64-linux (full log)
Attempted: python36Packages.node-semver
Partial log (click to expand)
writing manifest file 'node_semver.egg-info/SOURCES.txt'
running build_ext
============================= test session starts ==============================
platform linux -- Python 3.6.6, pytest-3.7.4, py-1.5.4, pluggy-0.7.1
rootdir: /build/node-semver-0.5.0, inifile: setup.cfg
collected 0 items

========================= no tests ran in 0.01 seconds =========================
pytestcachePhase
/nix/store/i9b69r6wvzgg9h35xmdvv1sxjv8hnlhi-python3.6-node-semver-0.5.0

Success on x86_64-darwin (full log)
Attempted: python36Packages.node-semver
Partial log (click to expand)
writing manifest file 'node_semver.egg-info/SOURCES.txt'
running build_ext
============================= test session starts ==============================
platform darwin -- Python 3.6.6, pytest-3.7.4, py-1.5.4, pluggy-0.7.1
rootdir: /private/tmp/nix-build-python3.6-node-semver-0.5.0.drv-0/node-semver-0.5.0, inifile: setup.cfg
collected 0 items

========================= no tests ran in 0.01 seconds =========================
pytestcachePhase
/nix/store/d9hpmhpi09pyi1wv8kka03vxldhsks4f-python3.6-node-semver-0.5.0

Success on x86_64-linux (full log)
Attempted: python36Packages.node-semver
Partial log (click to expand)
writing manifest file 'node_semver.egg-info/SOURCES.txt'
running build_ext
============================= test session starts ==============================
platform linux -- Python 3.6.6, pytest-3.7.4, py-1.5.4, pluggy-0.7.1
rootdir: /build/node-semver-0.5.0, inifile: setup.cfg
collected 0 items

========================= no tests ran in 0.02 seconds =========================
pytestcachePhase
/nix/store/ib7nxnr38854wix5an029d9nqnqvgy4a-python3.6-node-semver-0.5.0

@GrahamcOfBorg build python27Packages.node-semver

Success on aarch64-linux (full log)
Attempted: python27Packages.node-semver
Partial log (click to expand)
writing manifest file 'node_semver.egg-info/SOURCES.txt'
running build_ext
============================= test session starts ==============================
platform linux2 -- Python 2.7.15, pytest-3.7.4, py-1.5.4, pluggy-0.7.1
rootdir: /build/node-semver-0.5.0, inifile: setup.cfg
collected 0 items

========================= no tests ran in 0.01 seconds =========================
pytestcachePhase
/nix/store/g3j5rs36h3zr69rwka896d6p6jaifyg4-python2.7-node-semver-0.5.0

Success on x86_64-darwin (full log)
Attempted: python27Packages.node-semver
Partial log (click to expand)
writing manifest file 'node_semver.egg-info/SOURCES.txt'
running build_ext
============================= test session starts ==============================
platform darwin -- Python 2.7.15, pytest-3.7.4, py-1.5.4, pluggy-0.7.1
rootdir: /private/tmp/nix-build-python2.7-node-semver-0.5.0.drv-0/node-semver-0.5.0, inifile: setup.cfg
collected 0 items

========================= no tests ran in 0.01 seconds =========================
pytestcachePhase
/nix/store/8kq05j3h5vp2l13yw4v01h6v8d7pb45j-python2.7-node-semver-0.5.0

Success on x86_64-linux (full log)
Attempted: python27Packages.node-semver
Partial log (click to expand)
writing manifest file 'node_semver.egg-info/SOURCES.txt'
running build_ext
============================= test session starts ==============================
platform linux2 -- Python 2.7.15, pytest-3.7.4, py-1.5.4, pluggy-0.7.1
rootdir: /build/node-semver-0.5.0, inifile: setup.cfg
collected 0 items

========================= no tests ran in 0.02 seconds =========================
pytestcachePhase
/nix/store/h7813rvqd6x6rr1pls264crshzwabdg2-python2.7-node-semver-0.5.0


Debug _.each loop or functions of delegates

Hello, I am using vsCode 1.19.1 and try to debug my electron app with javascript. The debugger is working correctly. But there is a problem: the debugger is unable to go stepwise through _.each loops e.g.:
    _.each(startNodes, function(root) {
       if (root.type == 0) {
   	  hiddenNodes.push(root);
         functionNodes = functionNodes.concat(root.children);
       } else {
         functionNodes.push(root);
       }
     });

Here the debugger does not go inside it or when I set a breakpoint inside the block it does not stop there. Is there no way in vscode to debug the block of code in such a .each loop?
The same problem exists for functions in delegates:
graphContainer
	.delegate(
			'g.cluster',
			'click',
			function() {
				editorController.unhighlight();
				editorController.highlightNodeInCode(nodeData[this.id]);
			});

Also here I have no possibility to debug the code in the anonymous function. Setting a breakpoint there, also does not make the debugger stop.
So is there way to debug these codes in vscode?

What's your setup like? Debugging the main process of Node? Using Babel? Any transpilers?
Could be a sourcemap issue.

I am programming an application in Electron. If it helps, here is the source code: https://github.com/MbProg/BT
You could debug it with vscode and you will see the problems I have stated here

Another problem that I realized with vscode is that if I write any console.log in such a function, then the console is not writing in the terminal!!! Here the code:
graphContainer.delegate('g.node', 'dblclick', function(
	event) {
console.log("g.node dblclick");
...
});


fix(registry/issue-3429): registry boot script can now get bucket name from etcd

Looks like this also exists in the docs, so no changes required there :)
Could you please amend your commits such that it looks like this:
fix(registry): retrieve bucket name from etcd

We want the scope to be a component name so the changelog shows which components are affected by this issue. e.g. http://docs.deis.io/en/latest/contributing/standards/#example

We may want to continue to support the environment variable in case anyone's using it.
We've also been bitten in the past trying to read an etcd key right after it's been set - we have no guarantees that the write has persisted and is there by the time we need it.
Maybe a solution is to move the bucket name into /app/bin/create_bucket, since it's being managed by confd anyway.

We've also been bitten in the past trying to read an etcd key right after it's been set - we have no guarantees that the write has persisted and is there by the time we need it.

Good point. That's why we switched to etcdctl mk to create the keys instead of etcdctl set/get in an older PR. I like the idea of moving it over to create_bucket so we can rely on confd.

Bear with me... confd is something new for me.
I am trying as you have suggested and am updating create_bucket, line 14 as so:
name = '{{ getv "/deis/registry/bucketName" }}'

Oddly, this is giving me an error like the following even though this key is set:
sh[3313]: 2015-04-22T22:50:38Z 435e216bdabc confd[41]: ERROR template: create_bucket:14:11: executing "create_bucket" at <getv "/deis/registry...>: error calling getv: key does not exist

Being new to this, I am sure there is something here that I simply don't understand.

Altho in my case, that key has a value set because I set it.  (Still strange that that's not resolving.) But I'm not sure how it would be set in the average case.  I guess confd needs to run to create bin/create_bucket before bin/boot can possibly succeed and bin/boot is where the logic for setting an initial value for deis/registry/bucketName currently resides...
Long story short... I guess I am very confused on how the proposed alternative was supposed to work... though I'd like to try and understand it.

Nevermind... I see now... bin/boot runs, gets at least as far as setting a default value (if not existing?) for /deis/registry/bucketName and then waits for confd to run once.  So now I get how it's supposed to work... still don't get why it isn't.  :-/

I can nse to the floundering registry and run etcdctl -C $HOST:4001 get /deis/registry/bucketName and I do see the key is set with the value I expect.  Not sure why confd wouldn't also see it.

Had to rtf confd m.  I had not updated the create_bucket.toml.  Knowing is half the battle.
Got this working.  I am going to close this PR and open a new one.


[MODEL] Qwen 2 VLM 2B instruct and Qwen 2 VLM 7B instruct

HF URLS:

2b: https://huggingface.co/Qwen/Qwen2-VL-2B-Instruct
7b: https://huggingface.co/Qwen/Qwen2-VL-7B-Instruct

vLLM support:

https://github.com/vllm-project/vllm/pull/7905

SGLang Support:

https://github.com/sgl-project/sglang/issues/1352

Resolved here; https://github.com/stikkireddy/mlflow-extensions/pull/47 will not do sglang they are not prioritizing it


Include Template can't read parent's variables

4.6.2
Description
I have to explicitly pass variables to Include templates when using renderWith().
Is this the correct behaviour?
Steps to Reproduce
return $this->renderWith('MyTemplate', [
    'MyVar' => new MyClass()
]);

This works
MyTemplate.ss

$MyVar.SomeMethod

This doesn't work
MyTemplate.ss
<% include MyInclude %>

MyInclude.ss

$MyVar.SomeMethod

This works
MyTemplate.ss
<% include MyInclude MyVar=$MyVar %>

MyInclude.ss

$MyVar.SomeMethod

Just out of curiosity - does this behave differently if you use:
return $this->customise([
    'MyVar' => new MyClass()
])->renderWith('MyTemplate');

Just out of curiosity - does this behave differently if you use:
return $this->customise([
    'MyVar' => new MyClass()
])->renderWith('MyTemplate');

I believe this is by design

I believe this is by design

related? to https://github.com/silverstripe/silverstripe-framework/issues/8580#issuecomment-436578137 and also links to "by design".

related? to https://github.com/silverstripe/silverstripe-framework/issues/8580#issuecomment-436578137 and also links to "by design".

I'm not sure those two are related, but includes are not meant to inherit scope; their context needs to be passed in as show in the "this works" section.
I even had this "problem" way back in ss3, I think. It's not necessarily intuitive (as in PHP an "include" will inherit the variables declared in scope), but the templates aren't PHP and I don't think there's any desire from maintainers to change this behaviour especially when a thought out and reasonable decision was made at the time to explicitly exclude the external scope.
As such, I'm going to close this issue

I'm not sure those two are related, but includes are not meant to inherit scope; their context needs to be passed in as show in the "this works" section.
I even had this "problem" way back in ss3, I think. It's not necessarily intuitive (as in PHP an "include" will inherit the variables declared in scope), but the templates aren't PHP and I don't think there's any desire from maintainers to change this behaviour especially when a thought out and reasonable decision was made at the time to explicitly exclude the external scope.
As such, I'm going to close this issue

Thanks for the clarifications guys, it's ok that it's by design just something to keep in mind moving forward :)
Thanks again.

Thanks for the clarifications guys, it's ok that it's by design just something to keep in mind moving forward :)
Thanks again.


Improve docker-compose healthcheck

What kind of change does this PR introduce?
Modest improvements to docker-compose
What is the current behavior?
docker-compose.yaml's depends_on does not depend on the success of the health check.
https://github.com/peter-evans/docker-compose-healthcheck
https://github.com/compose-spec/compose-spec/blob/e8db8022c0b2e3d5eb007d629ff684cbe49a17a4/spec.md#long-syntax-1
What is the new behavior?
We can make it dependent on the success of the health check by writing the following
    depends_on:
      db:
        condition: service_healthy

Additional context
condition: service_healthy waits for the container to start. This is the same as if we had not written any condition.
In the compose spec, the version field is not required

With the docker-compose update I'm getting
ERROR: The Compose file './docker-compose.yml' is invalid because:
Unsupported config option for services: 'graphiql'

docker-compose version 1.25.4, build 8d51620a
ubuntu 20.04

A health check would be great but please do not adjust the indentation. We have a precommit hook to check that the formatting is valid here

I've turned the Intend back on.
Pre-commit is now also enabled.
Sorry. Implementation according to Compose Spec seems to be valid from Docker Compose v1.27.0+

These topics describe the Docker Compose implementation of the Compose format. Docker Compose 1.27.0+ implements the format defined by the Compose Specification. Previous Docker Compose versions have support for several Compose file formats – 2, 2.x, and 3.x. The Compose specification is a unified 2.x and 3.x file format, aggregating properties across these formats.

https://docs.docker.com/compose/compose-file/
It also works with the docker compose command integrated into the docker CLI.
docker compose up

https://docs.docker.com/engine/reference/commandline/compose/

@utamori thank you for the PR and the update. I checked the release date of docker-compose 1.27 and it was 2020-12
while we don't want to get in the habit of supporting outdated software, the main purpose of that docker-compose file is to power the quickstart guide. I'm hesitant to use newer syntax that will break on older docker installs during users' first experiences with this project
we can (and should) revisit this once the syntax is supported by a larger portion of the docker-compose install base. closing PR for now
thanks again!


Build fails on 0.13.0

Hi, just updated zig to 0.13.0 and got below error while building.
C:\Users\Rahul\AppData\Local\zig\p\122079a0dd43f5b26a584f2cde6c2580de775ed5e1b48d80e9946eef3edc4a510a04\build.zig:29:27: error: no field named 'path' in union 'Build.LazyPath'
            .lua51 => .{ .path = "src/ziglua-5.1/lib.zig" },
                          ^~~~
C:\Users\Rahul\scoop\apps\zig\0.13.0\lib\std\Build.zig:2171:22: note: union declared here
pub const LazyPath = union(enum) {
                     ^~~~~
referenced by:
    runBuild__anon_15738: C:\Users\Rahul\scoop\apps\zig\0.13.0\lib\std\Build.zig:2116:27
    dependencyInner__anon_14608: C:\Users\Rahul\scoop\apps\zig\0.13.0\lib\std\Build.zig:2097:29
    remaining reference traces hidden; use '-freference-trace' to see all reference traces

My build.zig looks like:
const std = @import("std");

pub fn build(b: *std.Build) void {
    const target = b.standardTargetOptions(.{});

    const optimize = b.standardOptimizeOption(.{});

    const exe = b.addExecutable(.{
        .name = "phoenix",
        .root_source_file = b.path("src/main.zig"),
        .target = target,
        .optimize = optimize,
    });

    const sdl_dep = b.dependency("SDL", .{
        .optimize = optimize,
        .target = target,
    });
    exe.linkLibrary(sdl_dep.artifact("SDL2"));
    exe.linkLibC();

    const ziglua = b.dependency("ziglua", .{
        .target = target,
        .optimize = optimize,
    });

    exe.root_module.addImport("ziglua", ziglua.module("ziglua"));

    b.installArtifact(exe);

    const run_cmd = b.addRunArtifact(exe);

    run_cmd.step.dependOn(b.getInstallStep());

    if (b.args) |args| {
        run_cmd.addArgs(args);
    }

    const run_step = b.step("run", "Run the app");
    run_step.dependOn(&run_cmd.step);

    const exe_unit_tests = b.addTest(.{
        .root_source_file = b.path("src/main.zig"),
        .target = target,
        .optimize = optimize,
    });

    const run_exe_unit_tests = b.addRunArtifact(exe_unit_tests);

    const test_step = b.step("test", "Run unit tests");
    test_step.dependOn(&run_exe_unit_tests.step);
}

Fails with same error on zig v0.14.0-dev.6+0ba64e9ce

OK, I see commit: https://github.com/natecraddock/ziglua/commit/d853aa9450ae568a39ea02d7082e85bafc33f735, which fixes the same. Please push new release

Got it working as of now using: zig fetch --save git+https://github.com/natecraddock/ziglua.git#d853aa9450ae568a39ea02d7082e85bafc33f735

Thanks for looking into this! 0.13.0 surprised me, so I'm still trying to get caught up on the fixes required

Just made an official release :) https://github.com/natecraddock/ziglua/releases/tag/0.3.0


Use overviews in reference section

The Docsy theme makes much more of section overview compared to the somewhat custom-for-Kubernetes documentation theme this site previously used.
Now we've switched to Docsy, some pages and sections have spartan overviews. This PR aims to help out there.

Move https://kubernetes.io/docs/reference/using-api/api-overview/ to https://kubernetes.io/docs/reference/using-api/
Move Controlling Access to the Kubernetes API out of the reference section and into https://kubernetes.io/docs/concepts/security/controlling-access/ [preview]
Update the overview for https://kubernetes.io/docs/reference/access-authn-authz/ [preview]

also fixing links and redirects.

/hold

/approve cancel

Hi @irvifa
What needs to happen to move this PR forward?

/hold cancel
Previously it needs rebase now it’s good
/approve


Build

wanted to add something to add.project respo

Can one of the admins verify this patch?

This is my branch and isn't ready to be filed as a PR.

@coderSHeE what is going on?  There's this PR, your bizarre comment on https://github.com/ceph/teuthology/commit/ee6ee70fcc47747b094464388631106408e794cf#commitcomment-69894144, and the totally-wrong https://github.com/ceph/teuthology/pull/1733, and the wrong comments on https://github.com/ceph/teuthology/commit/fd598ee0cf34f91e65dc7ae9c5e7fee0c469d0d4#commitcomment-69792477.   I'm confused.


Update Post “2022-07-12-sudah-kenal-computer-vision-belum-berikut-ini-penjelasan-secara-singkat-dan-mudah-dipahami”

Automatically generated by Netlify CMS

👷 Deploy Preview for mystifying-heyrovsky-e13280 processing.

Name
Link

🔨 Latest commit
a2803a8506a96c391861f763434f863bc3001b06

🔍 Latest deploy log
https://app.netlify.com/sites/mystifying-heyrovsky-e13280/deploys/62e8d3946cf3ad0008a4d68b


Disable hash bookmarks

I have some troubles when I try to add a new link which contains a hash symbol. It's structured like localhost:8080/#/user. After the link creation I hover it and press edit button. And what I see is that the link domain name was erased and there is only a string which contains the rest of the url after the has symbol.
So, is it possible to disable such behavior? The point is that my app's router is based on this hash symbol, so I can't just remove it from the url.

The 2.43.0 version has been updated.
If this issue has not been resolved, please reopen this issue.
Thank you.


Integrated kerberos authentication on windows clients

I can't tell from the documentation or examples, but does this library support integrated authentication on Windows clients? If so, are there any examples of how to authenticate that way?

does this library support integrated authentication on Windows clients?

It doesn't. Kerberos/GSSAPI support is a lot of work, especially if you'd like the result to be cross-platform. I didn't need it so far, so I haven't considered implementing it.

Bummer, that's the one thing stopping me from using rust at work. I'm still very much a noob to rust so if it's a lot of work I probably have no hope of being able to implement it, but I might try anyways. Tiberius seems to handle integrated authentication for MSSQL, at least on the windows side and probably from the linux/gssapi side as well as it has that listed as a feature, so maybe I can learn from that.

I looked at Tiberius some time ago, and I think that it uses NTLMv2 auth on Windows. But yes, it would be a good starting point in general.

I spent a few hours looking over the documentation for this, and now that I somewhat know what I'm looking for, I see somebody else has already tried to do this in PR #33, together with their own SSPI implementation in the form of the sspi-rs crate, though reading over the code I can only see a username and password authentication example in that branch.
All things considered, this is way over my head :) I'm learning rust for personal reasons, and I've just wanted to start using it at work so that I've got an excuse to spend even more time learning it as opposed to spending more time with the only other language I know, C#.

@1Dragoon heads up: there is experimental Kerberos/GSSAPI support on the master branch. Consider testing it if you're still wrangling AD.

This is awesome! By the way, do you happen to know of a universal method of auto detecting the domain controller in linux without needing to be root?

do you happen to know of a universal method of auto detecting the domain controller in linux without needing to be root?

On the DNS level, a SRV query for _ldap._tcp.dc._msdcs in the client's domain is resolved. Your Kerberos library should do this automatically (the MIT library does). I don't think being root enters into it.


[Task]: Prop Models

Rubric Criteria

[X] Gameplay
[ ] Graphics
[ ] Design
[ ] User Experience
[ ] Scripting
[ ] Sound
[ ] Quality
[ ] Process

Overview
I want to design props to fill the library environment with - specifically a table, chairs, and bookshelving units. I will also design the books.
Visualization

What is needed to implement the task?
Developing assets via Blender or Unity. I could also find them from an asset pack, and provide it to the team.
What is the biggest risk it will not get done?
That it somehow does not render in the library environment or does not stand still in place.
Test case
You start the game and the props can not be knocked over and are in place without glitching, and can be rendered fine.

https://assetstore.unity.com/packages/2d/textures-materials/nice-materials-pack-vol-2-67599
https://assetstore.unity.com/packages/3d/props/furniture/ds-furniture-pack-01-121404
https://assetstore.unity.com/packages/3d/props/interior/snack-machines-3517#description
https://github.com/rowanspain/Props_Rspain.git


Ignore *~

Signed-off-by: Michael McCracken<EMAIL_ADDRESS>

/me ducks a :bomb:

Emacs sucks but I'll merge this anyway.


Support browser extensions (for example, dat-fox)

This is out of scope of the SDK for now, but presumably you'd be able to use webextify to compile it to run with libdweb.


Issue in modal bottom sheet

I am using a bottem sheet and pass the focusnodes to it.
However i can't focus a node within the sheet, this results in the following glitch:

it should highlight the device card

I made a new onboarding inside the bottom sheet and now the focus node stays at the bottom. I think he doesn't like that the bottom sheet slides up.

Delaying the onboarding with a second solves the issue, showing when the bottom sheet is fully opened solves the issue.


Uncaught ReferenceError: process is not defined for injectManifest

I have a config like this:
			SvelteKitPWA({
				strategies: 'injectManifest',
				// // this affect whether workbox output log and the bundle is minified or not
				// mode: "development",
				mode: "production",
				registerType: "prompt",
				injectManifest: {
					globIgnores: ["server/**", "**/*.{css,js}"],
					globPatterns: ["**/*.{ico,jpg,jpeg,png,svg,woff,woff2}"],
				},
				minify: true,
			})

And a simple service worker like this:
/// <reference lib="WebWorker" />
/// <reference types="vite/client" />
/// <reference no-default-lib="true"/>
/// <reference lib="esnext" />
import {
  cleanupOutdatedCaches,
  createHandlerBoundToURL,
  precacheAndRoute,
} from "workbox-precaching";
import { NavigationRoute, registerRoute } from "workbox-routing";
import { CacheFirst, StaleWhileRevalidate } from "workbox-strategies";
import { ExpirationPlugin } from "workbox-expiration";
import type { ManifestEntry } from "workbox-build";

declare let self: ServiceWorkerGlobalScope;

self.addEventListener("message", (event) => {
  if (event.data && event.data.type === "SKIP_WAITING") {
    self.skipWaiting();
  }
});

const manifest = self.__WB_MANIFEST as Array<ManifestEntry>;

precacheAndRoute(manifest);

// clean old assets
cleanupOutdatedCaches();

And I can see the generated sw is not minified, nor replaced process.env.NODE_ENV. Is it intended for the user to fix themselves with rollup plugins?

Closing as I found solution here
https://github.com/vite-pwa/sveltekit/blob/2fa2591ebf6a8739ba4e249158d235d73dc2af40/examples/sveltekit-ts/vite.config.ts#L18


Last at data race bugfix

As mentioned issues#44
I found the data race by running the nano app with -race flags.

Can you use the atomic operation instead of mutex?

@lonng yes atomic is better, and sync was reverted to atomic

@chalvern Thanks a lot.


Can't buy loads of food.

My people are starving, I want to fill my storehouse quickly without waiting for a harvest.  Am I understanding the issue correctly? The bank UI let's me buy ten million of anything at once max. Seems like that ain't much wheat, right? A few lords?

we can't lob off 0s unless we do a fundamental rewrite - which we are not going to do. We can adjust everything client side if needed.
We can just increased the max purchasable to 100m which is going to be enough

Right. Adjusting client side sounds perfectly fine to me. I don't actually think it matters what happens under the hood (to the player experience, I mean). Under the hood there can be a gazillion digits for all I care, what I am saying is that in the client, the smallest unit that a player would ever consider making any use of should appear as 1, not 10000.
Having a player type in 100000000 is totally silly. It's also quite hard to visually distinguish between orders of magnitude as soon as there are more than four digits involved. 100 million? 10 billion? Let me go count some zeros. Tedious.


Add Latitude Scalar Type

Add LatitudeType to Hotchocolate.Types
Addresses: #2927

Isn't this covered by the position scalar?

@steveoh These lat an lon would also allow the following format
48° 27' 30.0672'' N
7° 47' 4.5924'' E

oh so degrees minutes and seconds... Do you plan to allow this to work with the rest of the spatial types?