Add a whole balance limit to UserDeposit

which is configurable at the deployment time.
Currently we keep the option of limiting deposits in all smart contracts (https://github.com/raiden-network/team/issues/324#issuecomment-465100567).
I chose against using the contract's token balance because that poses a DOS attack possibility.
This closes #585.

I'm not sure which requirements we have for the choice of our limits. Having a per-account limit would be simpler and more gas efficient than having a global limit. But I assume you know that and did it this way for a good reason.

@karlb the reason for the total limit can be seen here: https://github.com/raiden-network/team/issues/333
In general, one person can create an unlimited number of Ethereum accounts, so usually per-account limitations are not very effective.


Fix Release Command/Task

After the plugin has been upgraded to cross-built with 1.0.1, orgPublishRelease is not working when orgAfterCISuccess is invoked.

I think this is an example of a silent failure: https://travis-ci.org/frees-io/sbt-freestyle/builds/277277811
orgPublishRelease just didn't run even though it was supposed to according to the logs. At least, there was no logs showing that orgPublishRelease ran.


Upgrade prototype kit to v13

This PR migrates the Publish prototype code from v12 to v13. This takes advantage of a simpler set-up and matches other prototypes being built in BAT.
A number of things have changed:

package dependencies
layouts
filters used in the views
application styles - for example, tag style changes

There will likely be more changes needed to bring the styles in line with govuk-frontend v5.

@avinhurry, can you please confirm the changes you suggest I make? 🙌 I'm trying not to change the prototype page designs; I'm just migrating them to v13 of the prototype kit.
Having said that, I've updated the tags to match production. This also matches the v12 prototype.
From the second screenshot, do you think the summary list shouldn't be full-width? It's full-width because of the long-form content, but it looks odd when there isn't any content.
Finally, the footer links. They're small compared to the newer designs. If needed, someone on the Find and Apply team could update them.


uglyURLs - Permalink and RelPermalink of home page not ugly

When using ugly-URLs, links to the homepage render as "/" instead of the expected "/index.html". This causes problems when trying to host Hugo sites on hosts that disable DirectoryIndex. In my particular use-case, it's when I use the gitlab "exposed artifact"-feature to preview website changes for mesa3d.org.
What version of Hugo are you using (hugo version)?

$ hugo version
Hugo Static Site Generator v0.68.3/extended linux/amd64 BuildDate: 2020-03-25T06:15:45Z

Does this issue reproduce with the latest release?
Yes

I'm still seeing this:
$ hugo version
hugo v0.89.2-63E3A5EB+extended windows/amd64 BuildDate=2021-11-08T15:22:24Z VendorInfo=gohugoio

I'm not sure I follow the code entirely, but it looks like before 14227351f, this was kinda just an artifact of the logic, whereas after it seems very intentional. So maybe I'm having some unreasonable expectations here. I guess ugly URLs isn't intended for this use-case, just to render non-index pages with a different scheme.
But I would really like to be able to support my use-case. So what would be the right way of doing that? It kinda seems like adding yet another boolean option isn't the best plan...

I'm experiencing the same issue, also in the context of using GitLab and exposing job artifacts.
My workaround solution is to check hugo environment in templates and append index.html for non-production builds
      {{- with .Site.Home -}}

        {{- $suffix := cond hugo.IsProduction "" "index.html" -}}

          {{ .Title }}

      {{- end -}}

This is still relevant, nothing has changed. Please drop the "stale"-tag.

Any update?

Issue #11878 may describe a partial work-around for this problem, but I wouldn't trust it.
I spent about 90 minutes diving into Hugo's source, and I think the problem lies in function page.CreateTargetPaths.  The code flow is rather tricky to follow, but I found that adding:
		if isUgly && link == slash {
			link = pagePath
		}

after line 315 fixes the problem with manual testin.  The tests in page_paths_test.go break.  Fixing the tests proves difficult (and I don't have adequate time).  Part of this reason for this is the multi-layer logic of wrapped loops in the table test definitions (cf. Testing on the Toilet: Data Driven Traps).
I suspect the tests could be made more maintainable by:

Splitting them into two: one for ugly URLs and one for not

Inlining the test data expectations instead of having test.d computed/manipulated with the net effect being:
for _, test := range []struct{
  scen ScenarioState  // It seems like there is ancillary state used to power the test (unclear what purpose it serves).
  in Input
  out Output
}{
  ...
}{
  env := setup(test.scen)  // Use env to do whatever needs to happen to test.in (if anything)
  out := CreateTargetPaths(test.in)
  if diff := cmp.Diff(test.out, out); diff != "" {
    t.Errorf("CreateTargetPaths(%v) = %v, want %v\ndiff (-want, +got):\n%v", test.in, out, test.out, diff)
  }
}

The amount of inline data in the table test definition would grow significantly, but I reckon literal data is easier to manage and follow than computed/derived test data.

I'd be curious about the maintainers' opinions.  This is just a guess, and I imagine that the real fix is a lot simpler and more targeted, but it seems that page.CreateTargetPaths is the code responsible for the link target per my debugging.

Hello I have a related issue with the language selector https://github.com/orgs/hbstack/discussions/57#discussioncomment-9488895


Allow changing app contents url when in dev mode

Nice, thanks Adam. I pulled & tested. One minor improvement could be that when you enter the URL and press "enter" it does a "reload" for you. I entered "localhost:3000" and pressed enter, and there was no visual indication that it was or wasn't fetching the URL.


Add paging in delete collections in rfhub2.cli

Where there is more than 100 Collections delete_collections willl delete only first 100 Collections

PR in #33


Sass support

Could you add support for classes defined in Sass files?

#10

Closed as it's a duplicate of #10.


Adding the Git for Windows tools to the path if they are present

This includes helpful unix tools like ssh, scp, etc. Once a Windows users has ran our custom desktop shortcut or chef shell-init powershell then they will have access to these tools. I put it at the end of the path because some of these tools are already bundled into the ChefDK.
@tpetchel @randomcamel @btm @schisamo @ksubrama @PrajaktaPurohit

:+1:


Pie 7476 update git cache

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Preview environment: https://ci.pr.harness.io/pr-297

Preview environment: https://ci.pr.harness.io/pr-297

Preview environment: https://ci.pr.harness.io/pr-297

Preview environment: https://ci.pr.harness.io/pr-297

Preview environment: https://ci.pr.harness.io/pr-297


Feature: On-chain proof verification

Description
The Stone Prover is a tool for generating STARK proofs of Cairo programs.
The Integrity Verifier enables the on-chain verification of proofs generated by the Stone Prover.
In this example, we will demonstrate how to generate a proof of a Cairo computation locally and verify it using the verifier contract on testnet.
Criteria:

Provide an explanation of the proof generation process.
Include an example of verifying a proof on testnet, along with a link to the transaction on Voyager.
List potential use-cases (e.g., Layer-3 solutions, ZKML, etc.).

Resources:

Stone Prover
Integrity Verifier
The Integrity verifier: A leap toward Starknet hyperscaling

ODHack
To be eligible for additional rewards, be sure to review and follow the ODHack Common Guidelines and Contributing Guidelines.
Be sure to join the telegram group and introduce yourself.

i will like to jump on it

@julio4 I'll like to work on this

I'm interested in working on this issue

I am interested in working on this.
I have a good idea how I can go about this.
Please assign me.

Hi @julio4 i will love to work this

Hello everyone! I assigned @vibenedict for this time!

Just to update you that I am still working on rounding up the pr for this issue. I will be pushing the completed work pretty soon.

Just to update you that I am still working on rounding up the pr for this issue. I will be pushing the completed work pretty soon.

Thank you very much. ODHack hackathon has already finished, so today will be the last day if you want to be eligible!

Hi @julio4,
I would like to be assigned on this issue and tackle this interesting issue ! :)

@hudem1 Hey! Are you still working on this?

Hi @julio4 , If he/she is not, I’ll love to work on it please?


The Sidebar component has a prop Collapsed, but nothing is done with it?

Is this component a WIP? Or am I missing something? Thanks

Hello, the sidebar component is not ready yet, but I'm working on it.

Sidebar component released in version 0.0.17-next.11


Landing page

Yesterday when we talked, didn't someone mention that we don't need this anymore?

Yeah let me close this issue.


Initial benchmarks

Benchmark setup for initial use cases, extensively documented in test/benchmark/README.md, also configured in CI performance validation test, which will confirm against one benchmark variant (console deployment of simple lambda) whether we do not observe notable performance regression
Additionally:

Improve external extension telemetry server response time (so far response was sent after processing the payload, with this update it'll be sent after obtaining the payload but before processing it)
Fix handling of doubled resolution (case where lambda handler resolves with both callback and returned promise - apparently express handler does that)
Configure all basic error test fixtures
Add a test for the handled error case
Improve naming of lambda fixtures
Improve internal naming to match agreed terminology
Improve function processing (in integration tests and benchmarks)

and I can confirm I am using the same environment variables as the integrations tests 🤔

The only difference against integration tests is that with benchmarks there's no isolated home directory and that we do not filter what environment variables are accessible to the logic.
So that means that probably AWS takes precedence on some other env variables you have in env (as AWS_PROFILE), or that it's affected by config you have in ~/.aws dir.
I think the best way to debug it would be if you can set a short simple script that uses AWS SDK and try to run it and see if you also get credential errors (I believe it should behave exactly the same as with benchmark run)

@medikoo Oh man you are right for some reason my unset profile command didn't work 🤦 Once I removed AWS_PROFILE I stopped getting that issue lol sorry about that. After I removed the AWS_PROFILE thing the performance tests ran no problem 😎 Nice work


Rewrite exec using execsync-ng (which uses node-ffi)

Hi,
Shelljs has been awesome so far, except for exec. I know how it works, with the write-to-a-temporary file loop, and I know that its a hack necessary due to the lack of child_process.execSync.
Unfortunately, exec has been very buggy for me, randomly not working on various developer and server machines. Usually it gets stuck in an endless loop. I never seem to be able to satisfyingly reproduce the issue or find the cause.
So I decided to give that up and write shelljs-ffi based on execsync-ng which in turn is based on node-ffi. execsync-ng is a fork of execSync that also works on windows.
You can check out these modules at https://github.com/doxout/shelljs and https://github.com/doxout/execSync or try them out: npm install shelljs-ffi execsync-ng
I know that a native module dependency such as node-ffi is probably unacceptable for shelljs. However I decided to ask anyway... Is it possible that this fork may be accepted into shelljs?

Node now supports child_process.execSync https://nodejs.org/api/child_process.html#child_process_child_process_execsync_command_options

Closing this, since we no longer support v0.10, and can utilize the synchronous functions.


Tag releases

Could you git-tag releases, please? :)

Tagged head as 0.1.2a. Will be more disciplined with tagging future releases :)


Branching doesn't track PCB Changes

It seems if I make a branch and make changes it only track changes on the schematic. The PCB doesn't produce an SVG it seems, and there is no output on the actual PCB view.

This is the output spit from the verbose
    script_dir: /home/jordan/kicad/kdiff

     repo_root: /home/jordan/kicad/high-level-feedback-board
   project_dir: src

     kicad_pcb: src/HLFB_Breakout.kicad_pcb
     sch_files: src/HLFB.sch src/HLFB_Breakout.sch src/IO_Ports.sch
    board_name: HLFB_Breakout

    output_dir: /home/jordan/kicad/high-level-feedback-board/kidiff/src
       web_dir: /home/jordan/kicad/high-level-feedback-board/kidiff/src/web/

git-kdiff-log Jordan_Revision -- src/HLFB_Breakout.kicad_pcb src/HLFB.sch src/HLFB_Breakout.sch src/IO_Ports.sch

Commits list:
3c7c699 | 2021-05-18 13:04:37 -0700 | Jordan Lee | Moved 5V trace down
03a3ddb | 2021-05-18 11:35:56 -0700 | Jordan Lee | Added source files as well as changed README to reflect PCB

Generating artifacts for 2 commits.
Totaling 2 possible comparisons.

Schematic Pages
     1  HLFB_Breakout

Layers
     1  F_Cu
     2  B_Cu
     3  B_Adhes
     4  F_Adhes
     5  B_Paste
     6  F_Paste
     7  B_SilkS
     8  F_SilkS
     9  B_Mask
    10  F_Mask
    11  Dwgs_User
    12  Cmts_User
    13  Eco1_User
    14  Eco2_User
    15  Edge_Cuts
    16  Margin
    17  B_CrtYd
    18  F_CrtYd
    19  B_Fab
    20  F_Fab

Starting webserver at http://<IP_ADDRESS>:9092

Any idea?

Nevermind it is working fine again

Hmm, no ideia yet. I will have to check.
But try this:

git pull on kdiff repo to get latest changes
git pull on plotgitsh repo to get latest changes
reinstall plotgitsch with "./install"

Can you share this high-level-feedback-board repo so I can test this it too?

It seems to be working fine again on a separate branch. I believe it comes from this command I run in order for changes not to be recorded for time stamps. It seems to be working fine for now, I'll reopen this if I encounter more problems. The next thing I will test is what happens after merging branches.


refactor: restructure project to follow MVC pattern

fyi, tested :3

@Lxkas how how how, teach me


chef-expander does not respect config.solr_url value

Currently there is no way to configure chef-expander to use other then default Solr URL. This patch should fix the problem

[https://github.com/opscode/chef/pull/163](Pull request 163) seems like a better idea to fix the problem.

Thank you for supporting Chef! Our process has a couple prerequisites before we can merge your contribution. We need to ensure you've completed a Contributor License Agreement (CLA) and a ticket on our ticket tracker for the release workflow. Pull requests are optional, but should always include the ticket number that they're related to for cross-referencing. Please take a moment to review the below wiki page for the appropriate steps:
http://wiki.opscode.com/display/chef/How+to+Contribute

I see that pull request 163 was closed, so I'm closing this pull request as well based on your comments. Thanks again!


Container factory root folder is not writable on aarch64

Description of problem
Starting a kata container on aarch64 returns this:
# docker run -it --rm --runtime kata-runtime alpine
docker: Error response from daemon: OCI runtime create failed: rpc error: code = Unknown desc = mkdir /tmp/libcontainer: read-only file system: unknown.

This is using the standard config file and a rootfs image based on suse.
/tmp/libcontainer is the root used by libcontainer to store container data.
I found that this error is triggered on ARM because the root filesystem is mounted in read-only mode (by virtcontainers) and /tmp is not mounted as tmpfs (it's like this on many distros).
This issue is not present on x86_64, as the file system is mounted as R/W (and despite /tmp not being mounted as tmpfs, you can still write in it). And using nvdimm  without share=on prevents writes to /tmp to be written back in the image file.
ARM is not yet using nvdimm, and so mounting filesystem R/W is not an option, so changes to filesystem would be propagated back to the image file.
I'd propose to use /run/libcontainer instead of /tmp/libcontainer to store container data.
I checked on {SUSE,centos,clearlinux,ubuntu,Fedora} and on all of them /run is mounted as tmpfs.

Hi~ @marcov Supporting nvdimm is on progress. you can see detailed info on issue runtime#843. It needs to refactoring multiple modules (host kernel, guest kernel, qemu, etc) to be fully working well, so it may need a while😭.


[SPARK-25196][SQL] Extends Analyze commands for cached tables

What changes were proposed in this pull request?
This pr extended ANALYZE commands for cached table.
In common use cases, users read catalog table data, join/aggregate them, and then cache the result for following reuse. Since we are only allowed to analyze column statistics in catalog tables via ANALYZE commands, the current optimization depends on non-existing or inaccurate column statistics of cached data. So, it would be great if we could analyze cached data as follows;
scala> def printColumnStats(tableName: String) = {
     |   spark.table(tableName).queryExecution.optimizedPlan.stats.attributeStats.foreach {
     |     case (k, v) => println(s"[$k]: $v")
     |   }
     | }

scala> sql("SET spark.sql.cbo.enabled=true")
scala> sql("SET spark.sql.statistics.histogram.enabled=true")

scala> spark.range(1000).selectExpr("id % 33 AS c0", "rand() AS c1", "0 AS c2").write.saveAsTable("t")
scala> sql("ANALYZE TABLE t COMPUTE STATISTICS FOR COLUMNS c0, c1, c2")
scala> spark.table("t").groupBy("c0").agg(count("c1").as("v1"), sum("c2").as("v2")).createTempView("temp")

// Prints column statistics in catalog table `t`
scala> printColumnStats("t")
[c0#7073L]: ColumnStat(Some(33),Some(0),Some(32),Some(0),Some(8),Some(8),Some(Histogram(3.937007874015748,[Lorg.apache.spark.sql.catalyst.plans.logical.HistogramBin;@9f7c1c)),2)
[c1#7074]: ColumnStat(Some(944),Some(3.2108484832404915E-4),Some(0.997584797423909),Some(0),Some(8),Some(8),Some(Histogram(3.937007874015748,[Lorg.apache.spark.sql.catalyst.plans.logical.HistogramBin;@60a386b1)),2)
[c2#7075]: ColumnStat(Some(1),Some(0),Some(0),Some(0),Some(4),Some(4),Some(Histogram(3.937007874015748,[Lorg.apache.spark.sql.catalyst.plans.logical.HistogramBin;@5ffd29e8)),2)

// Prints column statistics on cached table `temp`
scala> sql("CACHE TABLE temp")
scala> printColumnStats("temp")
<No Column Statistics>

// Analyzes columns `v1` and `v2` on cached table `temp`
scala> sql("ANALYZE TABLE temp COMPUTE STATISTICS FOR COLUMNS v1, v2")

// Then, prints again
scala> printColumnStats("temp")
[v1#7084L]: ColumnStat(Some(2),Some(30),Some(31),Some(0),Some(8),Some(8),Some(Histogram(0.12992125984251968,[Lorg.apache.spark.sql.catalyst.plans.logical.HistogramBin;@49f7bb6f)),2)
[v2#7086L]: ColumnStat(Some(1),Some(0),Some(0),Some(0),Some(8),Some(8),Some(Histogram(0.12992125984251968,[Lorg.apache.spark.sql.catalyst.plans.logical.HistogramBin;@12701677)),2)

// Analyzes one left column and prints again
scala> sql("ANALYZE TABLE temp COMPUTE STATISTICS FOR COLUMNS c0")
scala> printColumnStats("temp")
[v1#7084L]: ColumnStat(Some(2),Some(30),Some(31),Some(0),Some(8),Some(8),Some(Histogram(0.12992125984251968,[Lorg.apache.spark.sql.catalyst.plans.logical.HistogramBin;@49f7bb6f)),2)
[v2#7086L]: ColumnStat(Some(1),Some(0),Some(0),Some(0),Some(8),Some(8),Some(Histogram(0.12992125984251968,[Lorg.apache.spark.sql.catalyst.plans.logical.HistogramBin;@12701677)),2)
[c0#7073L]: ColumnStat(Some(33),Some(0),Some(32),Some(0),Some(8),Some(8),Some(Histogram(0.12992125984251968,[Lorg.apache.spark.sql.catalyst.plans.logical.HistogramBin;@1f5c1b81)),2)

How was this patch tested?
Added tests in CachedTableSuite and StatisticsCollectionSuite.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/8733/
Test PASSed.

Test build #103290 has started for PR 24047 at commit 81b225d.

Test build #103290 has finished for PR 24047 at commit 81b225d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/103290/
Test PASSed.

Test build #103370 has started for PR 24047 at commit cda792d.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/8799/
Test PASSed.

Test build #103374 has started for PR 24047 at commit cda792d.

Test build #103374 has finished for PR 24047 at commit cda792d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/103374/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/8888/
Test PASSed.

Test build #103471 has started for PR 24047 at commit b3e9e10.

Retest this please.

Test build #103509 has started for PR 24047 at commit b3e9e10.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/8922/
Test PASSed.

Test build #103509 has finished for PR 24047 at commit b3e9e10.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/103509/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/8949/
Test PASSed.

Test build #103538 has started for PR 24047 at commit 342e566.

Test build #103538 has finished for PR 24047 at commit 342e566.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/103538/
Test FAILed.

Could you fix the build failure~?

Retest this please.

Locally, I can build this PR. So, I retriggered the Jenkins. Let's see the result, @maropu .

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/8962/
Test PASSed.

Test build #103551 has started for PR 24047 at commit 342e566.

Test build #103551 has finished for PR 24047 at commit 342e566.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/103551/
Test FAILed.

I see. @maropu . It seems that this PR needs to be rebased to master. Please rebase once more. Thanks!

ok

Done, thanks~

Test build #103552 has started for PR 24047 at commit 3b0f6df.

Thank you, @maropu !

Test build #103552 has finished for PR 24047 at commit 3b0f6df.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/103552/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/8964/
Test PASSed.

Hi, @maropu .
Sorry, I was confused.
Recently, lock is removed by SPARK-26917 Further reduce locks in CacheManager.

https://github.com/apache/spark/commit/8819eaba4db9a20c60a423fe08bee82cb8595ad0#diff-04b333ef6416de455e072b2bbbeff9ef

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/8978/
Test PASSed.

Test build #103569 has started for PR 24047 at commit 9c798a6.

Test build #103569 has finished for PR 24047 at commit 9c798a6.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/103569/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/8984/
Test PASSed.

Test build #103576 has started for PR 24047 at commit 22d8303.

Test build #103576 has finished for PR 24047 at commit 22d8303.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/103576/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/9001/
Test PASSed.

Test build #103596 has started for PR 24047 at commit 41c2c90.

Test build #103596 has finished for PR 24047 at commit 41c2c90.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/103596/
Test PASSed.

Retest this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/9079/
Test PASSed.

Test build #103682 has started for PR 24047 at commit 23d4063.

Test build #103682 has finished for PR 24047 at commit 23d4063.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/103682/
Test FAILed.

Retest this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/9085/
Test PASSed.

Test build #103690 has started for PR 24047 at commit 23d4063.

Test build #103690 has finished for PR 24047 at commit 23d4063.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/103690/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/9130/
Test PASSed.

Test build #103752 has started for PR 24047 at commit c6f0fb5.

Thanks for your active reviews, @dongjoon-hyun !

Test build #103752 has finished for PR 24047 at commit c6f0fb5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/103752/
Test PASSed.


Add a feature to build a vendored OpenSSL

This will be enabled through rust-lang/rust to ensure that for dist builds we
can build a Cargo with a vendored OpenSSL

r? @matklad
(rust_highfive has picked a reviewer for you, use r? to override)

@bors r+

:pushpin: Commit 585c7d43f923da4c35cdf6bd711e8fed28e09d03 has been approved by matklad

:hourglass: Testing commit 585c7d43f923da4c35cdf6bd711e8fed28e09d03 with merge 582f0cdbc78185eb2a499b3cf274945aaa299469...

:sunny: Test successful - status-appveyor, status-travis
Approved by: matklad
Pushing 582f0cdbc78185eb2a499b3cf274945aaa299469 to master...


Fix web shells logging

As @theMiddleBlue suggested, logging whole RESPONSE_BODY doesn't seems to be very clever.

Thanks @azurit
I just figure out that we do the same thing on logdata on all RESPONSE-*.conf :(

Thanks @azurit
I just figure out that we do the same thing on logdata on all RESPONSE-*.conf :(

@theMiddleBlue Should i close this PR and send a new which will fix it all?

@theMiddleBlue Should i close this PR and send a new which will fix it all?

thanks!!

thanks!!


glasgow: fix tests on darwin

Description of changes

Attempts to fix Glasgow check phase on Darwin (AArch64/x86_64).
Failure log: https://hydra.nixos.org/build/236090691/nixlog/1
Setting HOME=/tmp should make appdirs.user_cache_dir("GlasgowEmbedded", appauthor=False) in software/glasgow/target/hardware.py return /tmp/Library/Application Support (via appdirs).
Haven't tested on Darwin as I don't have access to a machine with it, deferring to CI on this one.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@ofborg build glasgow