Configurable client requests timeout

Similar to this issue, but not quite the same, as it's in a different part of the project:

https://github.com/MarshalX/atproto/issues/489

Essentially when doing a large number of async request I'm seeing a lot of timeouts and increasing the httpx default timeout (via the httpx timeout constructor parameter) resolves it:
https://github.com/MarshalX/atproto/blob/d85a59ffda63a38b01802a4b2c59a82ccdfc41d7/packages/atproto_client/request.py#L173
Would it be possible to provide a user-configurable timeout parameter atproto.Client/AsynClient as well, that is passed to httpx?

Idk is the best way to do so. There are plenty of configuration options. At least three were asked already: retry policy, proxy, and timeout. And for now, the best way to configure it is to make a simple inherit from the class. Like this: https://github.com/MarshalX/atproto/discussions/467#discussioncomment-11384769

Are you talking about InvokeTimeoutError?  I get that a lot.

Are you talking about InvokeTimeoutError? I get that a lot.

Yes, this is the exception that bubbles up when httpx times out.

Idk it is the best way to do so. There are plenty of configuration options. At least three were asked already: retry policy, proxy, and timeout. And for now, the best way to configure it is to make a simple inherit from the class. Like this: #467 (comment)

That sounds good, as long as it is easy to inherit from AsyncRequest, for example something like this:
import asyncio
import httpx
from atproto import AsyncClient
from atproto_client.request import AsyncRequest

class CustomAsyncRequest(AsyncRequest):
    def __init__(self) -> None:
        super().__init__()
        # Here just customise whatever the user needs
        self._client = httpx.AsyncClient(follow_redirects=True, timeout=10.0)

async def foo():
    client = AsyncClient(request=CustomAsyncRequest())
    ...

asyncio.run(foo())

Alternatively, if all the configuration needed was in the httpx client, we could just pass one as a AsyncRequest constructor argument:
import asyncio
import httpx
from atproto import AsyncClient

async def foo():
    custom_client = httpx.AsyncClient(follow_redirects=True, timeout=10.0)
    client = AsyncClient(client=custom_client)
    ...

asyncio.run(foo())


[SPARK-46471][PS][TESTS][FOLLOWUPS] Reorganize OpsOnDiffFramesEnabledTests: Factor out test_assignment_*

What changes were proposed in this pull request?
Factor out test_assignment_*
Why are the changes needed?
for testing parallelism
Does this PR introduce any user-facing change?
no, test-only
How was this patch tested?
ci
Was this patch authored or co-authored using generative AI tooling?
no

thanks @dongjoon-hyun and @HyukjinKwon


Thank you!

Not really an issue. Just wanted to comment and say thanks---this is very useful.

Glad to help!


possible EventEmitter memory leak detected. 11 close listeners added. Use emitter.setMaxListeners() to increase limit.

Hi, how I can fix it?
(node) warning: possible EventEmitter memory leak detected. 11 close listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at TLSSocket.addListener (events.js:239:17)
    at TLSSocket.Readable.on (_stream_readable.js:665:33)
    at first (c:\Folders\Sand\koa2-kickstarter\node_modules\ee-first\index.js:43:10)
    at onSocket (c:\Folders\Sand\koa2-kickstarter\node_modules\on-finished\index.js:114:16)
    at attachFinishedListener (c:\Folders\Sand\koa2-kickstarter\node_modules\on-finished\index.js:119:5)
    at attachListener (c:\Folders\Sand\koa2-kickstarter\node_modules\on-finished\index.js:146:5)
    at onFinished (c:\Folders\Sand\koa2-kickstarter\node_modules\on-finished\index.js:52:3)
    at Server.<anonymous> (c:\Folders\Sand\koa2-kickstarter\node_modules\koa\lib\application.js:134:7)
    at emitTwo (events.js:87:13)
    at Server.emit (events.js:172:7)
(node) warning: possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at TLSSocket.addListener (events.js:239:17)
    at TLSSocket.Readable.on (_stream_readable.js:665:33)
    at first (c:\Folders\Sand\koa2-kickstarter\node_modules\ee-first\index.js:43:10)
    at onSocket (c:\Folders\Sand\koa2-kickstarter\node_modules\on-finished\index.js:114:16)
    at attachFinishedListener (c:\Folders\Sand\koa2-kickstarter\node_modules\on-finished\index.js:119:5)
    at attachListener (c:\Folders\Sand\koa2-kickstarter\node_modules\on-finished\index.js:146:5)
    at onFinished (c:\Folders\Sand\koa2-kickstarter\node_modules\on-finished\index.js:52:3)
    at Server.<anonymous> (c:\Folders\Sand\koa2-kickstarter\node_modules\koa\lib\application.js:134:7)
    at emitTwo (events.js:87:13)
    at Server.emit (events.js:172:7)

I get this too.  I though at first it was related to using push, where I sent a lot of files one after the other (about 40) but it has nothing to do with it, as it still occurs soon after I start my application up.
I have no idea if this is a slow leak or just going over the limit slightly, as the warning is only produced once of each event and then is never repeated.

I discovered what this was and its NOT a memory leak.  Its the way serve-static handles streams.  I've actually just raised this as an issue against that repository
https://github.com/expressjs/serve-static/issues/87


Vercel Action

Setting up Vercel Action for PR https://github.com/marketplace/actions/vercel-action

The above requires to Sign Up for Vercel.com with the Design System project owner account so that DS repo can be imported.

Fixed by https://github.com/nihruk/design-system/pull/30


Examples are broken?

Description
Seems like all the examples on the websites are broken now, for example:
http://www.videogular.com/examples/adding-your-custom-buttons/

Browser
checked on Chrome

Yes, they've been broken for a couple weeks now..

I've fixed the demos.
Sorry about it!

I can't also  see the demo now...

Is there a particular demo giving you trouble? Browser?

i could only see the code "{{ currentTime | date:'mm:ss':'+0000' }} {{ timeLeft | date:'mm:ss':'+0000' }}" under "Result"


[Event Change Request] page 682  "Schedule a Report" - OnGetReportDescription2

Hello, would it be possible to add OnGetReportDescription2 event to page 682  "Schedule a Report", like this:
There is an existing event OnGetReportDescription( that has been updated with additional parameters.
    procedure SetParameters(ReportId: Integer; RequestPageXml: Text)
...
          Validate("Object Type to Run", "Object Type to Run"::Report);
         Validate("Object ID to Run", ReportId);

         OnGetReportDescription(ReportDescription, RequestPageXml, ReportId, IsHandled);
//Existing->        OnGetReportDescription(ReportDescription, RequestPageXml, ReportId, IsHandled);
>         OnGetReportDescription2(ReportDescription, RequestPageXml, ReportId, IsHandled, Rec); //New Event
         if IsHandled then
             Description := ReportDescription;

         Insert(true);

      [IntegrationEvent(false, false)]
//Existing->    local procedure OnGetReportDescription(var ReportDescription: Text[250]; RequestPageXml: Text; ReportId: Integer; var IsHandled: Boolean)
     local procedure OnGetReportDescription2(var ReportDescription: Text[250]; RequestPageXml: Text; ReportId: Integer; var IsHandled: Boolean; var JobQueueEntry: Record "Job Queue Entry")
     begin
     end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 53874.


Bad changeset received: Assertion failed: left().nullable == right().nullable

I'm getting this cryptic error message when I try to open a synced realm:
2017-02-09 21:28:01.753 Medisage[14791:592832] Sync: Connection[1]: Session[1]: Sending: IDENT(server_file_ident=8722228443253153481, client_file_ident=14, client_file_ident_secret=8271591352897651037, scan_server_version=0, scan_client_version=0, latest_server_version=0, latest_server_session_ident=0)
2017-02-09 21:28:02.501 Medisage[14791:592832] Sync: Connection[1]: Session[1]: Bad changeset received: Assertion failed: left().nullable == right().nullable

It seems it's because of some property changed from being optional to non-optional. But it doesn't tell which property and which class is causing the error.
Realm Object Server: 1.0.2
Realm version: 2.4.2
Xcode version: 8.2.1 - Objective C
iOS/OSX version: MacOS Sierra
Dependency manager + version: CocoaPods 1.1.1

Hi @gregiii. Thank you for reaching out. We'll have one of the engineers look into this and follow-up soon. In the meantime, if you can provide us with a sample project that the problem exists in/reproducible - that'll speed up the process of resolving the issue.

I have the sample project which reproduces this issue. However, I cannot post it here and would like to send the download link directly to you.

You can send the download link to<EMAIL_ADDRESS>

I have sent the link to the sample project.
Thank you.

Awesome, thanks @gregiii. We'll review that and follow-up soon.

@gregiii you're definitely right that this is due to a schema mismatch between the server and the client. We're tracking ways to improve the error messages internally, but in the mean time, you could print the schema information from both the client (using the RLMRealm.schema property) and from the server (using the Node.js SDK) and compare them to see how they differ.
I'm sorry I don't have a more convenient way for you to do this right now.

@jpsim Thanks for the assistance.


Rewrite guestbook example to use kube-dns instead of host:port

This fixes #5091

Happy to take for review this unless @thockin thinks it's his turf.

For my benefit, please can you explain a little bit more about the motivation for the PR?
I think the issue you are trying to solve #5901 relates to frontend pods being created before the redis services have their information propagated?
If that is the case, why not launch all the services first and still use SkyDNS?
And then launch the controllers/pods?
That way the env vars or DNS name will be defined?
Sorry if I am missing something here.

Satnam briefed via out of band communication.

please don't block on me - I am out this week

I thought I merged this earlier. Perhaps I failed to confirm. Retrying.

Thanks for review!

Just PD failures on e2e so I think we're golden.

I wish this had never been committed.  Our most basic example broken for people who just set up kubernetes in it's most bare form. People now have to have a WORKING kubernetes with a WORKING dns pod before they can even start to use the very first example. @nzwulfin is right, kube doesn't COME with dns.  Sure GKE might come with dns, the salt scripts might give you dns, but it isn't a PART of kube and our most basic example shouldn't expect it to be there.
My understanding is that you started the guestbook pods before you started the right services.  I know that stinks and the ENV var has it's limitations (also why I liked the idea of explicitly declaring required services)
@bgrant0607
I'd like to hear the argument why I shouldn't try to have this reverted...

@eparis
For quite some time we have been moving towards making DNS required and eliminating the links env vars, at least by default.
Are you questioning whether we'll eventually want DNS by default for all providers, or just pointing out that that's not the current state?

DNS is also required to make other cluster components work e.g. collecting logs. Rather than reverting to a baseline for examples that can't assume DNS why not instead put energy into providing DNS functionality for the other providers?
The is a fundamental tension right now between producing good idiomatic examples (and I think this PR is a good change in this regard) vs. trying to produce examples that work across all platforms.

My original question was around the prerequisites changing in the guestbook example without clear signaling.  I know it's in the commit history, but troubleshooting on the outside (not Kubernetes contributors) took a while to track down to this PR.
The prerequisites are listed as  "working cluster" with a pointer to a directory full of getting started guides.  However, the guestbook explicitly requires DNS, which isn't provided in any of the guides I can see.  It may be implicit in GKE and therefor not listed in the GKE guide, but DNS isn't explicitly configured in any guide.
Other contributors will have a harder time replicating idiomatic examples for other platforms if assumptions aren't present.

That's a very good point. Perhaps we have to bit the bullet and have variants of guestbook with clearly stated pre-requisites?

I'll go away, but I pretty strongly disagree with the assertion that I should need to have things running and functioning on TOP of the cluster before the most basic example of hos to USE the cluster is possible.
Logging and metrics is another example of services on top of the cluster.
Really I guess that means if we are going to continue to pursue the DNS for services model it would mean to me we need to make an effort to make the DNS be part of the cluster rather than an addon (even if an addon G*E does with salt)
I guess I want to see skyDNS be merged into the kube-proxy and the kubelet automatically just set the kube-proxy as the dns server, or something like that, if DNS is our requirement....

If the change to the example would break on the current environment, then adding that change to the list should work without multiple variants.
For example, moving to DNS based services from ENV based services would break on a non-DNS cluster.  Previous examples didn't need DNS, so that goes on the list.
The API move from v1beta1 to v1beta3 is another change (if there are non-backward compatible changes) that might need to be listed, but could be handled by listing the version used to create / test the guide.

I think its reasonable for an example to assert that it requires a pod running on the kube-master to support DNS.  @eparis - i see your point, but I am not sure we ever identified a particular example as the most basic example.  Maybe we need an example that does not require DNS, but demonstrates why in example 2 you would want to add a DNS pod to provide more value to the cluster.

In the interest of being a pain in the butt, DNS is not just launching a pod.  You also have to configure all of the kubelets with knowledge of how that pod was launched.
Kubelet must be configured to use DNS service, DNS service needs kubelet to launch. Inherent inception type wackiness.

@eparis - i see your config point.  i also am aware that many getting started guides are configuring kube incorrectly aside from DNS.

@derekwaynecarr If I've read the docs right, there's a flow (if hard to find the right entry point) of 101 -> 201 -> guestbook in the walkthrough example folder.  However, they don't really build that way, and if that's not the flow then it should be changed.  Users get dumped into the examples directory without any clear direction.  A lot of the examples refer to the getting started guides having provided some set of functionality, but many of them don't list those assumptions.
Maybe some guidelines around what this community determines is a "functional cluster" and then have those be the starting points for guides and examples to be written around?

Trying to tease apart the various issues here:

Kubernetes is designed to be modular with clearly defined and loosely coupled sub-components. DNS is not part of the 'intrinsics' and it should be perfectly reasonable to use a Kubernetes cluster without DNS and allow users to provide some other method of their choice for service discovery/composition/etc. as they see fit. This speaks to several peoples' views on this thread.
DNS is an add-on... but a very weird add-on... it provides a mechanism through which pods can 'compose' and this very useful mechanism is likely to be used by many applications which makes DNS look more like an 'operating system service' rather than some 'optional add-on'. Other cluster level services (cluster level monitoring and logging) do not influence how you architect your application in the way that the DNS add-on does.
Given DNS's special role it should perhaps not be a cluster add-on pod/service but instead be supported as a core part of Kubernetes? However, this then forces upon people aspects of networking which they may not want or pay the cost for?
I don't see us changing how we do DNS before the 1.0 release so in the short term I think we do need to sort out the guestbook documentation or produce variants that assume different amounts of the onion.
I don't think @eparis should go away -- I think he makes lots of good points.

@satnam6502 changes before 1.0 isn't practical. Couldn't agree more.
/me goes to look for the 2.0 roadmap page...

The post-1.0 roadmap will be a hot topic after we're not so crazy-busy trying to wrap up 1.0.

cc @RichieEscarez regarding example flow: see https://github.com/GoogleCloudPlatform/kubernetes/pull/5284#issuecomment-107712719

Rather than just discussing these issues in a closed PR, we should file new issues for them.

Created issue #9107


Make Dashboard App HPC resource size (RAM/CPU) configurable

I presume this was solved with the new useroptions branch of cdsdashboards, where you can pick the usual Jupyter server profiles when starting a dashboard server.


Manage LUIS intents in Hierarchy way with multiple LUIS sources?

Hello all,
After I added a trigger to the main with LUIS as recognizer, I added another trigger with another LUIS source. I wonder if it's possibile to fire the second trigger in a way the second source of LUIS returns the intents specifics for the dialogue.
EX.
FIRST LUIS
Where is the shopping mall?
Intents
Info about mall
SECOND LUIS
Where is the shopping mall?
Intents
Position mall
In this way i can delegate to the luis the task to guess the specific intent of the user. But the composer doesn't send the question after passing the first source of luis.
is there a way to achive this? and is it an ideal approach?
thank you.

Hi @JonathanHades , Could you provide the dialog assets for us ?

Hello @hibrenda what mean exactly for the dialog assets?
Anyway to better understand my question i put below the scheme of the dialog.
In few words I would want take advantage of the luis to get the first intent and then resend the same question to another luis specific for a matter like general info about the shopping mall and then get a second intent between for example where and when. So the bot can give the right responses without asking any further questions.
.Main
LUIS Meta Language
Info

position of the mall, timetables

where is the shopping mall?
when the shopping mall opens?

Shops

Shops of the mall

what are the shops of the mall?
what are the electronics shops of the mall?
INFO.Dialog
LUIS Meta Language

MallPosition

where is the shopping mall?

MallTimetable

when the shopping mall opens?

User question:
Where is the shopping mall?
intent recognized by Luis:
#Info

INFO.Dialog started
second intent recognized by Luis:

MallPosition

INFOPOSITION.Dialog started
Bot response:
To get to the mall take the route 33 untill you get to the roundabout...

addressed via https://github.com/microsoft/BotFramework-Composer/pull/1996


docs: Update Bedrock documentation to show streaming example

Is your feature request related to a problem? Please describe.
The BedrockGenerator now supports streaming_callback, similar to the OpenAIGenerator. After its release, it would be beneficial to include an example of 'Streaming' in the documentation to demonstrate its usage.
Describe the solution you'd like
Add a separate example code for streaming, similar to the example provided for the OpenAIGenerator in the documentation:
OpenAIGenerator Example.
Describe alternatives you've considered
NA
Additional context
NA

I attempted to make the information about streaming support more visible to users without manually rewriting examples for each component page:

Added a column to the Generators overview table.
Explained streaming support in Choosing the Right Generator guide with a generic example.
Added a reusable snippet called "Streaming" to the pages of Generators that support streaming.

This way, all three pages are somewhat interconnected, so users should be able to easily find this information.
@Amnah199 @julian-risch  please take a look if this makes sense before I close this :)


calicoctl endpoint remove is documented but not implemented

As documented on how to stop a calico node it is advised to call calicoctl endpoint remove. This in fact results into the following.
core@xh3b4sd-k8svm-master ~ $ calicoctl endpoint remove
Usage:
  calicoctl endpoint show [--host=<HOSTNAME>] [--orchestrator=<ORCHESTRATOR_ID>]
    [--workload=<WORKLOAD_ID>] [--endpoint=<ENDPOINT_ID>] [--detailed]
  calicoctl endpoint <ENDPOINT_ID> profile (append|remove|set) [--host=<HOSTNAME>]
    [--orchestrator=<ORCHESTRATOR_ID>] [--workload=<WORKLOAD_ID>]  [<PROFILES>...]
  calicoctl endpoint <ENDPOINT_ID> profile show [--host=<HOSTNAME>]
    [--orchestrator=<ORCHESTRATOR_ID>] [--workload=<WORKLOAD_ID>]

I feel like I am doing something fundamentally wrong. Can somebody provide feedback here?

That might be a typo for calicoctl container remove.  Could you try it and let me know if the doc works modulo that substitution?  If so I can update the doc (or you could make a PR for it if you like).

I think it is a typo in the docs and calicoctl container remove does the trick.

This issue was moved to projectcalico/calico#68


Improved live_reload, guarding against multiple rapid reloads, issue #487

Added API so application has some control over the process.
API use
//after	ss.client.packAssets();
ss.client.set({
onChange:
{ DelayTime:500,
GuardTime:4000,
Validate:function(path, event,action){
console.log('onChangeValidate :', path);
return true;
},
Publish:function(path, event,action,pubs){
console.log('onChange.Publish :', action);
//modify pubs if needed return null to not send any pubs
return pubs;
}
}});

Coverage remained the same at 49.68% when pulling 1a83267d1922db49f6838c46e6819280dbd34da3 on quale-quest:issue487 into efbcf5f16d6bc37b6dc443e0366463f04a0f8a96 on socketstream:master.

Hi, Thanks for the PR. If you could make the changes as suggested by Codacy, then I'll take a look and merge it in. Thanks.

Why the capitalised names? Is that required by live-reload?

If you refer to DelayTime,GuardTime,Publish,Validate
I will fix that when I do the revision ... old habits die hard.
On 2015/02/22 05:00 PM, Henrik Vendelbo wrote:

Why the capitalised names? Is that required by live-reload?
—
Reply to this email directly or view it on GitHub
https://github.com/socketstream/socketstream/pull/499#issuecomment-75439156.

Coverage increased (+0.28%) to 49.95% when pulling d5b67c404957467cb60878216403e1d34ec75f6c on quale-quest:issue487 into efbcf5f16d6bc37b6dc443e0366463f04a0f8a96 on socketstream:master.

Coverage increased (+0.28%) to 49.95% when pulling d3df6c2b0a7b7fd05892101bf943f050bc5c7b56 on quale-quest:issue487 into efbcf5f16d6bc37b6dc443e0366463f04a0f8a96 on socketstream:master.

Hi,
Is the delayTime attribute meant to delay executing the next reload? I tried this code snippet in my app, but it didn't seem to slow down when reloads were executed:
ss.client.set({
	onChange: {
		delayTime:5000,
		guardTime:8000,
		validate: function (path, event,action) {
			console.log('onChangeValidate :', path);
			return true;
		},
		publish:function (path, event,action,pubs) {
			console.log('onChange.Publish :', action);
			//modify pubs if needed return null to not send any pubs
			return pubs;
		}
	}
});

Delay time is the initial, time the first change is delayed for,
guardTime is the time after the last change.
This is a new patch, make sure are you running it against a version with
the patch in it, check the file live_reload.js refers to guardTime
also check the location : is after setting packAssets (more or less)
if (ss.env === 'production')
ss.client.packAssets();
ss.client.set({....
On 2015/02/28 12:14 PM, Paul Jensen wrote:

Hi,
Is the |delayTime| attribute meant to delay executing the next reload? I
tried this code snippet in my app, but it didn't seem to slow down when
reloads were executed:
|ss.client.set({
onChange: {
delayTime:5000,
guardTime:8000,
validate: function (path, event,action) {
console.log('onChangeValidate :', path);
return true;
},
publish:function (path, event,action,pubs) {
console.log('onChange.Publish :', action);
//modify pubs if needed return null to not send any pubs
return pubs;
}
}
});
|
—
Reply to this email directly or view it on GitHub
https://github.com/socketstream/socketstream/pull/499#issuecomment-76520193.

My apologies, I forgot to link the test app to the cloned version of SocketStream containing your feature branch. It works, thank you.
I'm happy to merge it in now, and will add an item to the documentation to describe how to use the feature.
Thanks for your work.


iOS Flutter Plugin - Vendor Framework file integration using Podspec file

Steps to Reproduce

Create an flutter plugin
Add a third party library (.framework) files to the ios folder
Try to link them to the build process by using the .podspec file.
cd to the example folder and run flutter run

myplugin.podspec
#
# To learn more about a Podspec see http://guides.cocoapods.org/syntax/podspec.html.
# Run `pod lib lint mitek.podspec' to validate before publishing.
#
Pod::Spec.new do |s|
  s.name             = 'myplugin'
  s.version          = '0.0.1'
  s.summary          = 'A new flutter plugin project.'
  s.description      = <<-DESC
A new flutter plugin project.
                       DESC
  s.homepage         = 'http://example.com'
  s.license          = { :file => '../LICENSE' }
  s.author           = { 'Your Company' =><EMAIL_ADDRESS>}
  s.source           = { :path => '.' }
  s.source_files = 'Classes/**/*'
  s.dependency 'Flutter'
  s.platform = :ios, '8.0'

  # Flutter.framework does not contain a i386 slice. Only x86_64 simulators are supported.
  s.pod_target_xcconfig = { 'DEFINES_MODULE' => 'YES', 'VALID_ARCHS[sdk=iphonesimulator*]' => 'x86_64' }
  s.swift_version = '5.0'

  s.preserve_paths = 'MySDK.framework', 'MySDK2.framework', 'MySDKUX/UX1_Files'
  s.resources = ['MySDKUX/UXResources/*']
  s.xcconfig = { 'OTHER_LDFLAGS' => '-framework MySDK -framework MySDK2' }
  s.vendored_frameworks = 'MySDK.framework', 'MySDK2.framework'
end

Error when running flutter run:
Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_MySDKViewController", referenced from:
    objc-class-ref in MyView.o
  ld: symbols(s) not found for architecture arm64

Logs
flutter run --verbose (too long to post here as there is a 65536 character limit for GitHub body comments.
https://pastebin.com/UY8MrQfL
flutter doctor -v
[✓] Flutter (Channel stable, v1.12.13+hotfix.8, on Mac OS X 10.15.3 19D76, locale en-US)
    • Flutter version 1.12.13+hotfix.8 at /Users/myuser/Library/flutter
    • Framework revision 0b8abb4724 (2 weeks ago), 2020-02-11 11:44:36 -0800
    • Engine revision e1e6ced81d
    • Dart version 2.7.0

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/setup/#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, set ANDROID_HOME to that location.
      You may also want to add it to your PATH environment variable.

[✓] Xcode - develop for iOS and macOS (Xcode 11.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.3.1, Build version 11C504
    • CocoaPods version 1.7.5

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/setup/#android-setup for detailed instructions).

[✓] Connected device (1 available)
    • iPhone 11 Pro Max • 464AACF4-ECA0-4A61-A165-CF79DB2FD690 • ios • com.apple.CoreSimulator.SimRuntime.iOS-13-3 (simulator)

! Doctor found issues in 2 categories.

Hi @D10100111001
I see that besides the error you pointed out
there are other errors in your logs from CocoaPods
1.	[        ] Error output from CocoaPods:

	2.	           ↳

	3.	[        ]

	4.	               [!] Automatically assigning platform `ios` with version `8.0` on target `Runner` because no platform was specified. Please specify a platform for

	5.	this target

	6.	               in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.

	7.

	8.	               [!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods

	9.	integration to

	10.	               work at all, please either set the base configurations of the target `Runner` to `Target Support Files/Pods-Runner/Pods-Runner.profile.xcconfig` or

	11.	include the

	12.	               `Target Support Files/Pods-Runner/Pods-Runner.profile.xcconfig` in your build configuration (`Flutter/Release.xcconfig`).

	13.	        '

	1.	[        ] Error output from Xcode build:

	2.	           ↳

	3.	[        ]     ** BUILD FAILED **

	4.

	5.

	6.	               The following build commands failed:

	7.	                Ld /Users/myuser/Projects/New%20Mobile/plugins/myplugin-3.7.1/example/build/ios/Debug-iphonesimulator/myplugin/myplugin.framework/myplugin normal

	8.	x86_64

	9.	               (1 failure)

	10.

	11.	[        ] Xcode's output:

	12.	           ↳

	13.	[  +43 ms]     Build settings from command line:

	14.	                   ARCHS = x86_64

	15.	                   BUILD_DIR = /Users/myuser/Projects/New%20Mobile/plugins/myplugin-3.7.1/example/build/ios

	16.	                   COMPILER_INDEX_STORE_ENABLE = NO

	17.	                   FLUTTER_SUPPRESS_ANALYTICS = true

	18.	                   SCRIPT_OUTPUT_STREAM_FILE = /var/folders/rr/f81lhv5d3nx7pqfy_503pndm0000gn/T/flutter_build_log_pipe.fxgYvS/pipe_to_stdout

	19.	                   SDKROOT = iphonesimulator13.2

	20.	                   VERBOSE_SCRIPT_LOGGING = YES

	21.

	22.	               note: Using new build system

	23.	               note: Planning build

	24.	               note: Constructing build description

	25.	               CreateBuildDirectory /Users/myuser/Library/Developer/Xcode/DerivedData/Runner-bwsjsgkpdaudxtfarxejnkpnswav/Build/Products (in target

	26.	'myplugin' from

	27.	               project 'Pods')

	28.	                   cd /Users/myuser/Projects/New%20Mobile/plugins/myplugin-3.7.1/example/ios/Pods

	29.	                   builtin-create-build-directory /Users/myuser/Library/Developer/Xcode/DerivedData/Runner-bwsjsgkpdaudxtfarxejnkpnswav/Build/Products

	30.
	1.	 Undefined symbols for architecture x86_64:

	31.	                 "_OBJC_CLASS_$_MySDKViewController", referenced from:

	32.	                     objc-class-ref in MyView.o

	33.	               ld: symbol(s) not found for architecture x86_64

	34.	               clang: error: linker command failed with exit code 1 (use -v to see invocation)

could you please double check that the podfile configuration is correct
following the link reported in the logs.
Thank you

@iapicca  Thank you for the prompt reply. I have fixed the CocoaPods issues that were displayed in the log. I'm still receiving the same end resulting errors.
It should be noted that the same error occurs when build is done for different architectures (x86_64 and arm64). Also, the MySDKViewController is part of the MySDK.framework/Headers folder and MyView is a swift file (in reference to the main error above.

Related: #45850 #41900

Pinging @zoechi as well as I have seen them in multiple of these similar issues.

Resolved. This was resolved by adding other folders containing source files to the source_files property.

Resolved. This was resolved by adding other folders containing source files to the podspec's source_files property.

Hi @D10100111001 , I'm also facing same issue can you elaborate more what files you  added and how to add them


Add documentation to IntegrationTest

Please add some documentation (code comments) to the IntegrationTest base class. I assume it is a convenience class that should be used by everyone who writes integration tests so it needs some comments on how to use it. Add comments to each attribute, each method and a general comment to the class.

@ArneBinder I think this is a very small task that takes only a few minutes. Please do it when you have time so we can close the issue.

Please add

a comment to the constructor to explain the parameter in the constructor
general comment to the whole class to highglight the two most important functions - constructor and getUrl()
Then assign the issue to @josauder so he can add code comments to the loggerIgnore functions


why does xsl:value-of not return a string

XSLT
<xsl:function name="t:parentName">
    <xsl:param name="current-node"/>
    <xsl:value-of select="$current-node/../name()"/>
</xsl:function>

XSPEC
<x:scenario label="parent of 'b'">
    <x:call function="t:parentName">
        <x:param name="current-node" select="/a/b">

        </x:param>
    </x:call>
    <x:expect label="is 'a'" select="'a'"/>
</x:scenario>

Result
Failed
    Expected: a
    Result: 'a'

XSLT 2.0 Rec

The xsl:value-of instruction is evaluated to construct a new text node; the result of the instruction is the newly constructed text node.
The string value of the new text node may be defined [...] by using the select attribute

https://www.w3.org/TR/xslt20/#value-of

I already found out that this problem does not occur if I use xsl:copy-of, or type the return value of the function as xs:string.
However, I want to understand why xsl:value-of does not create a string.

Your function returns a text node and your x:expect expects an xs:string. They are different items. So the test result is a failure.
You can either make the function return an xs:string
<xsl:function name="t:parentName" as="xs:string">

or make x:expect expect a text node
<x:expect label="is a text node of 'a'">a</x:expect>

whichever meets your intention.

Thank you for your help!
It works perfectly.


Transnational Exposure Logging states Germany (still) participates

Avoid duplicates

[X] Bug is not mentioned in the FAQ
[ ] Bug affects both Android and iOS, for specific issues / questions that apply only to one operating system, please raise them in the respective repositories:

Android repository
iOS repository

[X] Bug is not already reported in another issue
See also https://github.com/corona-warn-app/cwa-website/issues/3416 and https://github.com/eu-federation-gateway-service/efgs-federation-gateway/issues/306

Technical details

Device name:  Samsung Galaxy A52 5G (SM-A526B/DS)
Android version:  13
App version: 3.1.1

Describe the bug
Transnational Exposure Logging shows:
"The following countries currently participate in transnational exposure logging:
Germany"
According to https://www.coronawarn.app/en/faq/results/#interoperability_countries
'The "Interoperability Gateway" (European Federation Gateway Service; EFGS) was deactivated EU-wide in February 2023. There is no more exchange of warnings via the gateway and the Corona-Warn-App will therefore no longer report warning messages triggered in apps from other countries.'
This is inconsistent.
Steps to reproduce the issue

With Exposure Logging Active, tap on this line on the "Status" page of the app
Tap on Transnational Exposure Logging
Note that it lists Germany (and only Germany)

Expected behaviour
If the Gateway has been shut down, then the app should not state that Germany is still participating.

I don't know if this also affects CWA on iOS, however since it is a more general issue I added it here.
The FAQ information is now correct in any case, since issue https://github.com/corona-warn-app/cwa-website/issues/3416 is resolved.

I raised this issue internally and will come back to you tomorrow.

@Ein-Tim
Does this issue also affect iOS?

@MikeMcC399 Yes

Due to the upcoming end of the development of the CWA, it was decided that this will not be changed anymore.
The corresponding screens will anyway won't be shown anymore after a certain date in the near future (you can find out more details in the corresponding PRs in the app repositories).

@Ein-Tim
Thank you for relaying the decision. I understand this with my knowledge about the ramp-down plans that can be discovered by reading PRs for the unreleased next version.
Most users will however not have received this information, so https://www.coronawarn.app/en/faq/results/#end_of_development needs to have some dates added to it.


An error occurred during the publish operation

Describe the bug
Attempting to run amplify publish I get the following error message
✖ Deployment failed! Please report an issue on the Amplify Console GitHub issue tracker at https://github.com/aws-amplify/amplify-console/issues.
An error occurred during the publish operation

Desktop (please complete the following information):

OS: MacOS 10.14.6 - Also ubuntu-latest Github Action

I don't want to use the build in CI, but I might have to go back to it because any attempt to use amplify publish just fails.

Having the same issue on latest Ubuntu OS

@benwainwright @SSAT Can I get your app ID and region? Also are there any other errors in information in your logs to help further debug this issue?

@hsspain I'm going to be honest; the Amplify development experience has been so awful over the last few months that I took the decision to rip it out of my application shortly after I posted this issue and I'm now using the CDK for everything. So I'm going to close this issue.


[rayjob] status update not as timely as expected

What would you like to be added:
When rayjob is admitted, the status is not updated, it should be Pending I think.
Also, when rayjob is preempted and status transmit to STOPPED. Then when rayjob is admitted again, the status should transmit to Pending rather stays in STOPPED.
Why is this needed:
Better describe the job status.
Completion requirements:
This enhancement requires the following artifacts:

[ ] Design doc
[ ] API change
[ ] Docs update

The artifacts should be linked in subsequent comments.

Isn't this on the rayjob side? the implementation of suspend?

@achernevskii can you take this one?
It seems to me that this would be in kuberay side, not kueue.

Sorry, I just recorded here in case of forgotten, sorry for the confusion, I will dig into the reason and close this if necessary.

/close as not kueue's responsibility.


[microNPU] Integrate the cascader

Integrate the cascader into the codegen and optionally enable it
with the enable_cascader flag. Includes placeholder MemoryRegions until
integration with the PoolInfos provided by a user.
Co-authored-by: Matthew Barrett<EMAIL_ADDRESS>

cc: @manupa-arm @lhutton1 @NicolaLancellotti

This patch supersedes https://github.com/apache/tvm/pull/10377, so that one can be closed.

Thanks @ekalda @mbaret @lhutton1 @NicolaLancellotti !
This is merged now!


Compatibiliy with moonfabric's trinkets, notably, the —> pain box

The moonfabric mod contains a number of trinkets. None of the trinkets the player was wearing are kept on the player between logins. Instead, when the player logs back into a server, the trinkets are placed in the player's inventory (or scattered about if there is no rooom). Workaround is to keep inventory free and re-eqiup them every time.
One trinket in particular poses a larger issue... the pain box. This trinket increases the number of belt slots and back slots. When relogging in, it simply disappears completely, along with every other trinket that was placed in every belt and back slot (including the original back slot). This leads to entire vanishing entire backpacks along with their contents. Strangely enough, the backpack (travelersbackpack in my case) can still be accessed through cardinal components hotkey assignment, at least until you put on another backpack, then it's wiped. It also gets wiped upon death.
The trinkets are saved properly upon quitting the game, as they appear in the playerdata.dat file. They all get unequipped, or destroyed only when logging back into the game on a later date.
Thanks!

What version of Accessories are you using? We recently recieved a similar issue, which was fixed today with the latest release of Accessories (beta 40). Could you try out this new version and see if it solves your issue?

Unfortunately, I can not try beta 40 because my server is running a MC 1.21. At the time of writing, I was using the most recent Accessories release on Modrinth, beta 35+1.21. I'd be happy to try out the new version as soon as you publish it for 1.21, though. :^)

@Aesthir Try the latest 1.1.0 version as the fix should be contained within there

okay, I just tried it. Both the client and the server (both running Minecraft v1.21) won't even start up due to Accessories v1.10-beta.4+1.21.1. I read through the crash report and managed to figure out the problem, which I solved with a little ingenuity. I don't think most people will be able to solve the problem, though, so the game is disabled for them once they upgrade to the newest version of Accessories.
Problem: the Trinkets Compat Layer for Accessories needs to be updated to beta.14 to work with the new release of Accessories, but the new version isn't offered for Minecraft v1.21.
Work Around: install the Trinkets Compat Layer for Accessories v3.10..0-beta.14 for Minecraft v1.21 and disregard the incompatibility warning.
I can play the game but every attack on a newly spawned entity gives this error:
[Server thread/ERROR]: Failed to handle packet net.minecraft.class_2824@114401f9, suppressing error
java.lang.IllegalArgumentException: Parameters not allowed in this parameter set: [<parameter minecraft:damage_source>, <parameter minecraft:attacking_entity>]
	at knot/net.minecraft.class_8567$class_8568.method_51875(class_8567.java:136) ~[server-intermediary.jar:?]
	at knot/io.wispforest.accessories.api.events.extra.LootingAdjustment.lambda$static$2(LootingAdjustment.java:35) ~[accessories-fabric-1.1.0-beta.4+1.21.1.jar:?]
	at knot/io.wispforest.accessories.api.events.extra.ExtraEventHandler.lootingAdjustments(ExtraEventHandler.java:36) ~[accessories-fabric-1.1.0-beta.4+1.21.1.jar:?]
	at knot/net.minecraft.class_125.wrapOperation$zzf000$accessories$attemptAdjustCountWithAccessoriesLooting(class_125.java:528) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_125.wrapOperation$zzf000$accessories$attemptAdjustCountWithAccessoriesLooting$mixinextras$bridge$17(class_125.java) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_125.method_522(class_125.java:66) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_120.method_521(class_120.java:37) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_120.apply(class_120.java:17) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_131.method_53347(class_131.java:90) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_117.method_514(class_117.java:16) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_77.method_433(class_77.java:36) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_85$1.method_426(class_85.java:66) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_55.method_345(class_55.java:76) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_55.method_341(class_55.java:99) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_52.method_328(class_52.java:92) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_83.method_433(class_83.java:46) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_85$1.method_426(class_85.java:66) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_55.method_345(class_55.java:76) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_55.method_341(class_55.java:99) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_52.method_328(class_52.java:92) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_52.method_51880(class_52.java:101) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_1309.method_16077(class_1309.java:1485) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_1308.method_16077(class_1308.java:527) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_1309.method_16080(class_1309.java:1434) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_1309.method_6078(class_1309.java:1399) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_1309.method_5643(class_1309.java:1252) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_1657.method_7324(class_1657.java:1303) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_3222.method_7324(class_3222.java:1743) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_3244$1.method_34218(class_3244.java:1650) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_2824$1.method_34213(class_2824.java:174) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_2824.method_34209(class_2824.java:74) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_3244.method_12062(class_3244.java:1610) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_2824.method_12251(class_2824.java:61) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_2824.method_11054(class_2824.java:15) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_2600.method_11072(class_2600.java:27) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_3738.run(class_3738.java:18) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_1255.method_18859(class_1255.java:162) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_4093.method_18859(class_4093.java:23) ~[server-intermediary.jar:?]
	at knot/net.minecraft.server.MinecraftServer.method_24306(MinecraftServer.java:864) ~[server-intermediary.jar:?]
	at knot/net.minecraft.server.MinecraftServer.method_18859(MinecraftServer.java:173) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_1255.method_16075(class_1255.java:136) ~[server-intermediary.jar:?]
	at knot/net.minecraft.server.MinecraftServer.method_20415(MinecraftServer.java:846) ~[server-intermediary.jar:?]
	at knot/net.minecraft.server.MinecraftServer.method_16075(MinecraftServer.java:840) ~[server-intermediary.jar:?]
	at knot/net.minecraft.class_1255.method_5383(class_1255.java:121) ~[server-intermediary.jar:?]
	at knot/net.minecraft.server.MinecraftServer.method_16208(MinecraftServer.java:814) ~[server-intermediary.jar:?]
	at knot/net.minecraft.server.MinecraftServer.method_29741(MinecraftServer.java:702) ~[server-intermediary.jar:?]
	at knot/net.minecraft.server.MinecraftServer.method_29739(MinecraftServer.java:281) ~[server-intermediary.jar:?]
	at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]

Would it be possible for you to create an Accessories release and TC Layer for v1.21?
Finally, I tested whether the moonstone trinkets stay or vanish upon server re-entry. They still vanish. :^/

@Aesthir This crash should be fixed with the latest release of Accessories and you should update your pack to 1.21.1 as that is the known good target for accessories and most case should be fine for you modpack

Ah, I believe I got this mixed up thinking this was the forge version of moon which was fixed but the trinkets version needed the same fix as well I believe, I can get a fix out later today for this I hope

@Aesthir Update has been pushed and it seems fixed within prod testing

Ahhh... that's the issue. I tried beta.6 release and it has fixed the issue... the trinkets are no longer vanishing. One surprise though, it's possible to cheat with this release by getting the extra trinkets slots without wearing the pain box now, which releases you from its negative effects.
I noticed beta.7 was just released. I haven't tried that one yet.
Thank you.


Tests legacy and modern endpoints simultaneously

Issue
Simultaneous creation of legacy and modern endpoints relations
Solution
Charm goes into a "blocked" state, when creating a simultaneous relation legacy and modern endpoints.

Hi @BalabaDmintri  and thank you for contribution here!
Please sign contribution agreement to merge the PR: https://github.com/canonical/postgresql-operator/actions/runs/8256188989/job/22618992227?pr=396
Tl;DR: Are we testing the right things here?  :-D
Long: I am slightly confused. I thought our current position is to disallow simultaneous legacy and modern interfaces: Please choose one endpoint to use. No need to relate all of them simultaneously!.
IMHO, charm should get into 'blocked' state forcing users to remove one relation and choose legacy or modern only.
@marceloneppel is it still valid position? I cannot find such blockers in charm.py code :-(

Hi @BalabaDmintri and thank you for contribution here! Please sign contribution agreement to merge the PR: https://github.com/canonical/postgresql-operator/actions/runs/8256188989/job/22618992227?pr=396
Tl;DR: Are we testing the right things here? :-D
Long: I am slightly confused. I thought our current position is to disallow simultaneous legacy and modern interfaces: Please choose one endpoint to use. No need to relate all of them simultaneously!. IMHO, charm should get into 'blocked' state forcing users to remove one relation and choose legacy or modern only. @marceloneppel is it still valid position? I cannot find such blockers in charm.py code :-(

Hi @taurus-forever! In my opinion, we need to fix this in the relations to forbid them from being established simultaneously (and match Note: do NOT relate both modern and legacy interfaces simultaneously! from https://charmhub.io/postgresql/docs/e-interfaces). We should allow it only if we find a valid use case.
If we agree on that, I can create issues for that.

@BalabaDmintri can you please update PR description. It doesn't represent the content. Tnx!

Hi, @BalabaDmintri, please fix the error in the unit test and sync up with main.

Hi, @BalabaDmintri, please fix the error in the unit test and sync up with main.

@dragomirp Can  you check

@dragomirp Can you run actions


New Feed Added: Fayetteville Area System of Transit

Agency name/Transit Provider:
Location
US, North Carolina, Fayetteville
Details
Data type
gtfs
Issue type
New feed
URLs

Current URL on OpenMobilityData.org
Updated/new feed URL

https://www.fayettevillenc.gov/home/showpublisheddocument/16121/638612293378070000

Authentication
Authentication type
None - 0
View more details
https://docs.google.com/spreadsheets/d/10eIUxWVtLmc2EATiwivgXBf4bOMErOnq7GFIoRedXHU/edit

Blocked because of #216


[otbn,dv] Clear the "imem is invalidated" flag when loading program

This hasn't usually mattered because we reset the dut (and also the
ISS) after injecting IMEM errors to clear the locked state. However,
there was a race window where we injected the errors just after OTBN
had finished. In this case, we don't need to reset the DUT, but we do
have to clear the flag when the IMEM contents are replaced.

@weicaiyang: Ping again!

Thanks!


Insert 'clearError' method

I've found 'clearError' missed in the example code and i inserted it.

aha thank you 🙏


Set template mode to CP only if a CP request

This PR checks that this is a CP request before changing the template mode, otherwise the plugin may break the subsequent template that should be rendered.

Thanks for the PR @bencroker, we'll have a look soon and get it merged in.
We appreciate you taking the time to help us improve this plugin.
Cheers!

Is there an update on this PR? Running into the issue mentioned by @bencroker while using the Sprig plugin.


Add xcmrelay test suite

Add a Python-based test suite that exercise the xcmrelay program, running in valgrind (in valgrind-enabled builds).

Resolved by 4d7166a41e7bc42538eea8d3bbc6534f52070d41.


Column group by dynamic

QueryDSL: 3.6.5
JPA: 2.0
I would like to create the query with QueryDSL , but I'm finding it difficult to use alias along with grouping.
PostgreSQL:
select length(my_column) as column_size from my_table group by column_size

i'am using
NumberPath<Integer> column_size= Expressions.numberPath(Integer.class, "column_size");
List<Integer> users = from().groupBy(column_size).list(usuario.login.length().as(column_size));

This returning the exception stating that the column  column_size does not exist:
Look return from console:
select length(lgn) as col_0_0_ from sgrusr01 group by column_size
"ERRO:  coluna "column_size" não existe
LINE 2: group by COLUMN_SIZE
^
********** Error **********
ERRO: coluna "column_size" não existe
SQL state: 42703
Character: 56"

Thanks for the bug report! Did you try this also with JPQL directly?

This looks similar to https://hibernate.atlassian.net/browse/HHH-1902

Exactly the issue I am currently encountering. Seems hibernate did also not solve it yet.


Simplify v2/Chat.py

Can you simplify chat.py so it is easier to follow and be used as an inference where history can be sent? Right, it seems pretty obfuscated where it using some hacks to limit output?

My code is a horrible mess (too busy to refactor)
You can use RWKV pip package: https://pypi.org/project/rwkv/ to write your own version from scratch

Getting error after converting the model.

Make sure you are using latest rwkv (0.7.2)
pip install rwkv --upgrade

My code is a horrible mess (too busy to refactor)

Just checking. You're still not interested in letting someone else clean it up. Correct?
(Mostly talking about the actual model, not the chat example.)

Just checking. You're still not interested in letting someone else clean it up. Correct?
(Mostly talking about the actual model, not the chat example.)

Please feel free to fork and write a better version :)
I will clean it when I am less busy (now training lots of models everyday)

I'd be willing to do that, but it's something that would be a significant amount of work. So it basically would only be worth putting the time into if there was a pretty good chance of the changes getting accepted.
Obviously it wouldn't be reasonable to expect you to promise to merge a pull request before even seeing it, but there's still a way to find out of something is generally the kind of change you're looking for/would accept. You can see my previous pull #47 for the type of changes I'm talking about.

I'd be willing to do that, but it's something that would be a significant amount of work. So it basically would only be worth putting the time into if there was a pretty good chance of the changes getting accepted.

Yeah I wont merge such large changes, but it will be great for understanding how the chat mode works, if you are interested :)
The best way to understand something is to write your own version

Yeah I wont merge such large changes

Fair enough. I think at some point you're going to have to clean up the code and it's going to be more difficult the larger and more complicated it becomes. Your choice though.

The best way to understand something is to write your own version.

I actually already did. I wrote a Rust based implementation here: https://github.com/KerfuffleV2/smolrsrwkv
It's CPU only and actually runs about as fast as ChatRWKV in cpu fp32 and cpu fp32i8 mode.
If you think it could help other people in the community, please feel free to link it if you want to. (Also, I'd be happy to receive any constructive criticism about it.)


New release?

I think is about time to have a new release , the last one is dated 2016 and there are new , interesting changes in the repo.

Hello,
please do not post this questions or conversation topics here, this is the issues section
of a repository, post them in the OPL dedicated threads in the psx-scene or psx-place,
thank you.
Best regards.


Kubed shows abnormal high I/O and memory usage

We use Kubed for a small task: synchronizing two SSL certificate secrets to 25 namespaces.
This ran fine for months, but over the past 4-6 weeks we saw  see cluster nodes become unavailable for scheduling as a result of connectivity problems from the kubelet towards the Docker engine, so called PLEG issues (https://github.com/kubernetes/kubernetes/issues/45419).
After further analysis, it became apparant that the affected nodes were running kubed. By using iotop, we found out that kubed was writing to disk at a sustained speed of up to 1-1,5 MB/s continously:

At the same time the kubed container grew to memory usage of > 2 GB.
Restarting the container immediately results in the above levels of I/O usage and the container grows to several hundred megabytes of memory usage within minutes.
This behaviour is observed both on kubed 0.9 and 0.10. As a result, we have disabled kubed for now. This normalizes the situation.
The whole kubed configuration was working fine until several weeks ago.
Please find the profiler output attached.
Any idea how to remedy this situation?
allocs.txt
goroutine.txt
heap.txt
threadcreate.txt

I have also seen this happening now in two other clusters running in another cloud. This happens both on AWS EKS and Azure AKS. Any idea where to get started with isolating this?

having the same problem with the high load - kubed shows some nil pointer errors:
	/go/src/github.com/appscode/kubed/vendor/github.com/robfig/cron/cron.go:161 +0x9e
panic(0x243d260, 0x7daefc0)
	/usr/local/go/src/runtime/panic.go:522 +0x1b5
github.com/appscode/kubed/pkg/recyclebin.(*RecycleBin).Cleanup(0xc0007beab0, 0xc000934790, 0x42c8af)
	/go/src/github.com/appscode/kubed/pkg/recyclebin/recycle_bin.go:115 +0x9c
github.com/appscode/kubed/pkg/operator.(*Operator).RunTrashCanCleaner.func1()
	/go/src/github.com/appscode/kubed/pkg/operator/operator.go:462 +0x2e
github.com/appscode/kubed/vendor/github.com/robfig/cron.FuncJob.Run(0xc00050c440)
	/go/src/github.com/appscode/kubed/vendor/github.com/robfig/cron/cron.go:92 +0x25
github.com/appscode/kubed/vendor/github.com/robfig/cron.(*Cron).runWithRecovery(0xc00026a870, 0x63ad840, 0xc00050c440)
	/go/src/github.com/appscode/kubed/vendor/github.com/robfig/cron/cron.go:165 +0x57
created by github.com/appscode/kubed/vendor/github.com/robfig/cron.(*Cron).run
	/go/src/github.com/appscode/kubed/vendor/github.com/robfig/cron/cron.go:199 +0x749
I0703 06:43:55.000407       1 log.go:172] cron: panic running job: runtime error: invalid memory address or nil pointer dereference
goroutine 243372 [running]:
github.com/appscode/kubed/vendor/github.com/robfig/cron.(*Cron).runWithRecovery.func1(0xc00026a870)
	/go/src/github.com/appscode/kubed/vendor/github.com/robfig/cron/cron.go:161 +0x9e
panic(0x243d260, 0x7daefc0)
	/usr/local/go/src/runtime/panic.go:522 +0x1b5
github.com/appscode/kubed/pkg/recyclebin.(*RecycleBin).Cleanup(0xc0007beab0, 0xc000b2a790, 0x42c8af)
	/go/src/github.com/appscode/kubed/pkg/recyclebin/recycle_bin.go:115 +0x9c
github.com/appscode/kubed/pkg/operator.(*Operator).RunTrashCanCleaner.func1()
	/go/src/github.com/appscode/kubed/pkg/operator/operator.go:462 +0x2e
github.com/appscode/kubed/vendor/github.com/robfig/cron.FuncJob.Run(0xc00050c440)
	/go/src/github.com/appscode/kubed/vendor/github.com/robfig/cron/cron.go:92 +0x25
github.com/appscode/kubed/vendor/github.com/robfig/cron.(*Cron).runWithRecovery(0xc00026a870, 0x63ad840, 0xc00050c440)
	/go/src/github.com/appscode/kubed/vendor/github.com/robfig/cron/cron.go:165 +0x57
created by github.com/appscode/kubed/vendor/github.com/robfig/cron.(*Cron).run
	/go/src/github.com/appscode/kubed/vendor/github.com/robfig/cron/cron.go:199 +0x749
I0703 07:43:55.000336       1 log.go:172] cron: panic running job: runtime error: invalid memory address or nil pointer dereference
goroutine 259452 [running]:
github.com/appscode/kubed/vendor/github.com/robfig/cron.(*Cron).runWithRecovery.func1(0xc00026a870)
	/go/src/github.com/appscode/kubed/vendor/github.com/robfig/cron/cron.go:161 +0x9e
panic(0x243d260, 0x7daefc0)
	/usr/local/go/src/runtime/panic.go:522 +0x1b5
github.com/appscode/kubed/pkg/recyclebin.(*RecycleBin).Cleanup(0xc0007beab0, 0xc000c09790, 0x42c8af)
	/go/src/github.com/appscode/kubed/pkg/recyclebin/recycle_bin.go:115 +0x9c
github.com/appscode/kubed/pkg/operator.(*Operator).RunTrashCanCleaner.func1()
	/go/src/github.com/appscode/kubed/pkg/operator/operator.go:462 +0x2e
github.com/appscode/kubed/vendor/github.com/robfig/cron.FuncJob.Run(0xc00050c440)
	/go/src/github.com/appscode/kubed/vendor/github.com/robfig/cron/cron.go:92 +0x25
github.com/appscode/kubed/vendor/github.com/robfig/cron.(*Cron).runWithRecovery(0xc00026a870, 0x63ad840, 0xc00050c440)
	/go/src/github.com/appscode/kubed/vendor/github.com/robfig/cron/cron.go:165 +0x57
created by github.com/appscode/kubed/vendor/github.com/robfig/cron.(*Cron).run
	/go/src/github.com/appscode/kubed/vendor/github.com/robfig/cron/cron.go:199 +0x749

@tamalsaha any news on this?

This seems to be a duplicate of #304? Also see #361

I would like to hear your feedback on https://github.com/appscode/kubed/issues/304#issuecomment-521369891 .

News on this?

I have released v0.11.0 https://github.com/appscode/kubed/releases/tag/v0.11.0 . Please give it a shot.

Have been running it in 2 clustrers, one of them for a few hours. Looks good until now.

After three days:

One cluster looks fine: kubed container has grown to 728 MB), no abornmal I/O
The other cluster remains problematic: kubed container grown to 3.2Gb, abnormal high I/O usage)
In both clusters kube is only used to simply replicate an SSL certificate in a secret to other namespaces.
Is there anything I can provide to help troubleshooting?

Just installed v0.11 in one of our clusters and we still see the extremly high IO usage of kubed. Memory is still growing, but i only started it 10 minutes ago ... will update this tomorrow.
Just syncing secrets / configmaps across namespaces. Cluster has 19 namespaces and 5 nodes ...

I have this as well. There are spikes of I/O when it writes ConfigMaps to namespace but sometimes it start doing steady I/O writes and the CPU iowait on the node kubed is running on bump up to 60% making the node barely usable.

The memory is caped to the limit I set so I suspect that it is doing swap but this is not normal. Buming the memory limit to 512MB has the same behavior.

Same behaviour on our cluster. We are using kubed v0.11 to sync secrets/configmaps to namespaces.
Running AKS v1.13.10, with 5 nodes and between 50 and 60 namespaces that kubed is syncing to.
I0923 11:41:58.123035       1 client_config.go:104] resetting Kubeconfig host to [redacted] for AKS to workaround https://github.com/Azure/AKS/issues/522
I0923 11:41:58.126396       1 lib.go:112] Kubernetes version: &version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.10", GitCommit:"37d169313237cb4ceb2cc4bef300f2ae3053c1a2", GitTreeState:"clean", BuildDate:"2019-08-19T10:44:49Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}
I0923 11:41:58.170044       1 operator.go:100] configuring kubed ...
E0923 11:41:58.276006       1 restmapper.go:117] Skipping failed API Groups: unable to retrieve the complete list of server APIs: kubed.appscode.com/v1alpha1: the server is currently unable to handle the request
I0923 11:41:58.813907       1 operator.go:100] configuring kubed ...
E0923 11:41:58.956259       1 restmapper.go:117] Skipping failed API Groups: unable to retrieve the complete list of server APIs: kubed.appscode.com/v1alpha1: the server is currently unable to handle the request
I0923 11:41:58.957509       1 secure_serving.go:116] Serving securely on [::]:8443

isn't that an error E0923 11:41:58.956259       1 restmapper.go:117] Skipping failed API Groups: unable to retrieve the complete list of server APIs: kubed.appscode.com/v1alpha1: the server is currently unable to handle the request @phpai ?

Yes, getting same error as you mentioned in your post above. Maybe i phrased in incorrectly. What i meant is besides this error on startup, no other could be errors visible in the logs.

@tamalsaha any news on this. kubed is still leaking and causing problems. Have you discovered something? Thank you

Same here in terms of memory.

@estahn That is a lot of GBs for a small process :grimacing: I set the limit in ram to 128mb and let kube kill it periodically... This is not ideal. A real fix would be appreciated.

we have unreasonable high write IO as well, which saturates node in GKE and causes iowait
iotop -bon 1
Total DISK READ :       0.00 B/s | Total DISK WRITE :      21.26 M/s
Actual DISK READ:       0.00 B/s | Actual DISK WRITE:      24.46 K/s
    TID  PRIO  USER     DISK READ  DISK WRITE  SWAPIN      IO    COMMAND
3369018 be/4 65535       0.00 B/s   21.26 M/s  0.00 % 50.82 % kubed run --v=3 --secure-port=8443 --audit-log-path=- --tls-cert-file=/var/serving-cert/tls.crt --tls-private-key-file=/var/serving-cert/tls.key --use-kubeapiserver-fqdn-for-aks=true --enable-analytics=true

its writing into /tmp/indices/ per namespace. Unfortunately helm deployment doesent let to redefine scratch volume, so it all goes towards node io limit.

Hi, I have released v0.12.0-rc.0 with a rewrite. Please try it and let me know if you are still seeing this issue. https://github.com/appscode/kubed/releases/tag/v0.12.0-rc.0

@tamalsaha
The new chart is breaking on EKS
Error: Chart requires kubernetesVersion: >=1.9.0 which is incompatible with Kubernetes v1.14.9-eks-c0eccc
Error: UPGRADE FAILED: Chart requires kubernetesVersion: >=1.9.0 which is incompatible with Kubernetes v1.14.9-eks-c0eccc

Error: Chart requires kubernetesVersion: >=1.9.0 which is incompatible with Kubernetes v1.14.9-eks-c0eccc
Error: UPGRADE FAILED: Chart requires kubernetesVersion: >=1.9.0 which is incompatible with Kubernetes v1.14.9-eks-c0eccc

Are you using Helm 2 or 3? This sounds like a Helm bug. As a workaround, I can remove this line https://github.com/appscode/kubed/blob/master/charts/kubed/Chart.yaml#L5

events is forbidden: User "system:serviceaccount:kube-system:kubed-kubed" cannot create resource "events" in API group "" in the namespace "default"

If you add something like this to the kubed ClusterRole .
- apiGroups: [""]
  resources:
  - events
  verbs: ["create"]

@tamalsaha Helm2. didn't get time to uprade yet.

I just released https://github.com/appscode/kubed/releases/tag/v0.12.0-rc.1 . Can you try that?

@mbelang , please try https://github.com/appscode/kubed/releases/tag/v0.12.0-rc.2 . This adds the missing permission. Please let me know how that goes.

All good so far @tamalsaha :+1:

Thanks @mbelang ! Closing the issue.


Remove internal properties (start with _) from interfaces

Types like Store and Pinia still include some of the internal properties (marked as @internal). This shouldn't happen as they should be removed thanks to api-extractor but something is likely blocking it.
This would prevent polluting public interfaces as said in

#937

A working example is vue reactivity:
export declare class ReactiveEffect<T = any> {
    fn: () => T;
    scheduler: EffectScheduler | null;
    active: boolean;
    deps: Dep[];
    parent: ReactiveEffect | undefined;
    /* Excluded from this release type: computed */
    /* Excluded from this release type: allowRecurse */
    onStop?: () => void;
    onTrack?: (event: DebuggerEvent) => void;
    onTrigger?: (event: DebuggerEvent) => void;
    constructor(fn: () => T, scheduler?: EffectScheduler | null, scope?: EffectScope);
    run(): T | undefined;
    stop(): void;
}

Notice the "Excluded from ..." vs leaving the @internal flag in pinia types:
 * Every application must own its own pinia to be able to create stores
 */
export declare interface Pinia {
    install: (app: App) => void;
    /**
     * root state
     */
    state: Ref<Record<string, StateTree>>;
    /**
     * Adds a store plugin to extend every store
     *
     * @param plugin - store plugin to add
     */
    use(plugin: PiniaPlugin): Pinia;
    /**
     * Installed store plugins
     *
     * @internal
     */
    _p: PiniaPlugin[];
// ...
}

Types like Store and Pinia still include some of the internal properties (marked as @internal). This shouldn't happen as they should be removed thanks to api-extractor but something is likely blocking it.

I think we can use publicTrimmedFilePath instead of untrimmedFilePath in api-extractor.json to remove internal properties. But now @internal is overused so pinia.d.ts file has a lot of errors when we use publicTrimmedFilePath.


MAC openmp issue

Hi,
I  tried to do cmake for  mkldnn-1.0.4 and found that openmp is not found on MAC clang compiler  and hence mkldnn library is built without any openmp optimizations.
Is this expected behavior? If yes, is there anyway we could enable openmp optimizatios during cmake for mkldnn build on MAC .
I have attached the cmake log for your reference log3.txt
It will be helpful to receive any suggestions regarding this.
Thank you,
Praveen.

Hi @uu-praveeng, AppleClang do not have pre-built OpenMP bits. Please try workaround from #591


adjust prettier config #3

From prettier docs regarding print width:

For readability we recommend against using more than 80 characters:
In code styleguides, maximum line length rules are often set to 100 or 120. However, when humans write code, they don't strive to reach the maximum number of columns on every line. Developers often use whitespace to break up long lines for readability. In practice, the average line length often ends up well below the maximum.
Prettier, on the other hand, strives to fit the most code into every line. With the print width set to 120, prettier may produce overly compact, or otherwise undesirable code.
See the print width rationale for more information.

We can just try with 120 and change later if we run into issues.

I guess we can see how prettier behaves and adapt


Revert "Implement content drawer"

Reverts OxideEngine/Oxide#43

Codecov Report

Merging #47 (37308ec) into main (67649f5) will increase coverage by 19.65%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main      #47       +/-   ##
===========================================
+ Coverage   39.67%   59.32%   +19.65%
===========================================
  Files          37       30        -7
  Lines        3214     2092     -1122
  Branches      477      223      -254
===========================================
- Hits         1275     1241       -34
+ Misses       1768      735     -1033
+ Partials      171      116       -55


org & workspace

Notes for Reviewers
This PR fixes #
Screencast from 2024-04-29 18-47-19.webm
Signed commits

[x] Yes, I signed my commits.

merge conflicts...

@captain-Akshay merge conflicts...

@captain-Akshay merge conflicts...


Currently can't make memory size > 96000.

Describe the bug
Currently can't make memory size > 96000.
To Reproduce
Attempting to make the memory any larger than 96000 resulted in the following error message:
[ID=1 of 2][PC=0x8000000][3.3E+00V, 6.0E+01MHz] sizemem		9600000
Set memory size to 9375 Kilobytes

	Exiting: Cannot compute required number of covariances without overflow

	Writing all node information to sunflower.out ```

This is currently preventing me from loading a .sr file with a size > 96000.

**Expected behavior**
should be able to make the memory size at least 9600000 from previous evidence

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Host OS (please complete the following information):**
 - OS: (e.g., macOS 10.9).
 - Browser (e.g., Chrome or Safari).
 - Version (e.g., 22).

**You local changes (please complete the following information):**
 - Output of `git diff`.
- Output of `git remote -v`.

**Additional context**
Add any other context about the problem here.

Ah sorry! This one is my fault.
When doing uncertainty propagation in sunflower we need a (fairly huge) amount of memory to store covariances. As the implementation was left after finishing my masters, we support covariances between any two floats stored in memory.
The amount of memory that needs allocating is ((bytes of normal memory) / 4) ^ 2 (I think?) and for fairly small values of  (bytes of normal memory) more than 2^32 bytes need allocating causing this failure.
The problem here is sunflower allocates all this memory (easily over 1GB) even when users have no intention of considering uncertainties - even if the user requests less than 960,000 bytes of memory it is still a bug to allocate all this memory that will never be used. I should have made the allocation conditional on a runtime or compile time flag - sorry!
I forget exactly where the offending code is but it should be easily found by grepping for the error message. A tempory solution would be to comment out this code (the allocation not just the assertion).

Related to #119


[ZEPPELIN-4428] Fix bug - Highlighted line number disappears

What is this PR for?
Fix bug that highlighted line number disappeared.
(Before)

(Problem)
In paragraph.css file, there was a custom css that changes background color of the line number.
Need to apply that css line to this UI together.
(After)

What type of PR is it?
Bug Fix
Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-4428

Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/
Put link here, and add [ZEPPELIN-Jira number] in PR title, eg. [ZEPPELIN-533]

How should this be tested?

First time? Setup Travis CI as described on https://zeppelin.apache.org/contribution/contributions.html#continuous-integration
Strongly recommended: add automated unit tests for any new or changed behavior
Outline any manual steps to test the PR here.

Screenshots (if appropriate)
Questions:

Does the licenses files need update?
Is there breaking changes for older versions?
Does this needs documentation?

Thanks @milooy for the fixing, LGTM

LGTM


feat: add the new toggle functionality

Description
Implement Previous selected Wallet
Video
Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

Type of change.

[ ] FIX - a PR of this type patches a bug.
[x] FEATURE - a PR of this type introduces a new feature.
[ ] BUILD - a PR of this type introduces build changes.
[ ] CI - a PR of this type introduces CI changes.
[ ] DOCS - a PR of this type introduces DOCS improvement.
[ ] STYLE - a PR of this type introduces style changes.
[ ] REFACTOR - a PR of this type introduces refactoring.
[ ] PERFORMANCE - a PR of this type introduces performance changes.
[ ] TEST - a PR of this type adds more tests.
[ ] CHORE - a PR introduces other changes than the specified above.

The music over the video was a nice touch!

Please provide more spacing between the Recent and other wallets. Otherwise, this is amazing!

Hey @trechriron
Here is the improved version :)
Video
What do you think?


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 1000 ms

Resolved: Bofrost.lu performance has improved in 2992022 after 9 minutes.


feat(FabricCAClient): addDefaultHeader && fix bugs

This pull request has been inactive for a long time so closing. Feel free to comment if you would like it reopened.


Need some information regarding the implementation

i want to know what is the limit of consecutive multiplication we can do using this implementation and how do you guys decide what should be the limit.
please help me with this information i am working on some project related to  Homomorphic Encryption.

Please ask your question in the Discourse forum: https://openfhe.discourse.group/


Example for "logo" and "status" vocabulary annotations for OM3

Hi,
I have an ontology which has (among many other things) defined "status" and "logo" by using bibo:status and schema:logo, respectively. Are these the vocabulary annotations which should be detected by FOOPS? If yes, could you give me an example ontology where FOOPS detects these?
For my vocabulary (https://w3id.org/sri) I get the following result, while I believe it should be 100%:

@stefanbischof you are correct, and your annotations are fine. I detected the following:

We check schema.org properties with https instead of http. I believe both are supported, so we should expand coverage.
For some reason, in bibo status I expect literals instead of objects/URIs. Will have to expand the support
Thanks A LOT for letting us know!

Thanks for the quick feedback! I changed schema.org to https. Yea, AFAIK bibo:status became an object property some time ago.

For some reason, I think I added this in Widoco, but not here. Will do when time allows


The result of (sha1 "你好") is error.

"http://pajhome.org.uk/crypt/md5/index.html" in this site,the result of
hex_sha1("你好") is "440ee0853ad1e99f962b63e459ef992d7c211722".
But the result of
(pandect.algo.sha1/sha1 "你好") is "4bd9abaa33ea0834383e15fef9ae377f762fc03b".
As far as I know,the correct of the result is "440ee0853ad1e99f962b63e459ef992d7c211722". Is there something wrong in pandect.algo.sha1/sha1 function?

hex_md5("你好") is "7eca689f0d3389d9dea66ae112e5cfd7". But
(pandect.algo.md5/md5 "你好") is "b94ae3c6d892b29cf48d9bea819b27b9"

Your default charset does not seem to be UTF-8. For me, it's working:
(require '[pandect.algo [sha1 :refer [sha1]] [md5 :refer [md5]]])
(let [data "你好"]
  [(sha1 data) (md5 data)])
;; => ["440ee0853ad1e99f962b63e459ef992d7c211722"
;;     "7eca689f0d3389d9dea66ae112e5cfd7"]

The following should give you the right result:
(sha1 (.getBytes "你好" "UTF-8"))

But yes, pandect should by default convert to UTF-8 bytes.

Changes were released in
[pandect "0.5.0"]

:+1:


SPCR: Forbid SGI and PPI for the GSIV field with Arm GIC

For platforms with an Arm GIC interrupt controller, the SPCR revision 4 wording does not forbid the SPCR GSIV to be set to a SGI or PPI. Neither of those Arm GIC interrupt classes is sensible for the UART. This change explicitly forbids using SGI or PPI for the UART described by the SPCR.
Contributed by: Jose Marinho<EMAIL_ADDRESS>

@tedhudek - Would be good to have you as a second set of eyes on approval of this PR.


Exclude test dependencies from production Atom binary

Description
This excludes the test dependencies from the production Atom binary. This is done by moving those dependencies to spec folder.
Benefits

The production Atom binary will be smaller and load faster
This removes the security issues involved with these old dependencies in the final Atom binary

Drawbacks
N/A

@UziTech Do you know why jasmine-tagged isn't found although it is under spec/node_modules?


Remove header license from rustup-init.sh

Related https://github.com/rust-lang/rust/pull/57108.

I don't understand why this is desirable considering the shell script is acquirable independently of rustup itself.

No, I just saw header license in rustup-init.sh. Looks like I am wrong. In that case, I will change the issue name.

Given https://github.com/rust-lang/rustup.rs/pull/1733#issuecomment-478718234 I think @nrc is in favour of this change anyway, so I'll remove my mild objection.

Closed on #1733.