text:
[macOS] casing of returned paths doesn't match filesystem

/cc @citycide
nimble test
[Suite] pattern walking / listing
  [OK] basic
  [OK] leading magic
  [OK] `Directories` includes matching directories in the results
    /Users/timothee/git_clone/temp/glob/tests.nim(380, 21): Check failed: seqsEqual(toSeq(walkGlob("TEMP/**", options = o)), @[p"temp/deep/dir/file.nim",
    p"temp/not_as/deep.jpg", p"temp/not_as/deep.nim", p"temp/shallow.nim"])
  [FAILED] `IgnoreCase` enables case insensitive matching

I'm on OSX. this is on a fresh clone

The results are actually correct, it's just a casing difference between expected & actual.
We're expecting:
temp/deep/dir/file.nim
temp/not_as/deep.jpg
temp/not_as/deep.nim
temp/shallow.nim

But on macOS we receive:
TEMP/deep/dir/file.nim
TEMP/not_as/deep.jpg
TEMP/not_as/deep.nim
TEMP/shallow.nim

I'm not entirely sure yet why this is different on macOS than it is on Windows which is also case insensitive.

authors: citycide timotheecour

repo: citycide/glob


text:
inbox folder is only selectable at automate creation

Description
When we create a new automate, we can select inbox as the destination folder. But if we edit an existing automate, inbox doesn't appear in the drop down
Expected
Automate creation and editing should be consistent, and inbox shoud always be selectable
Info:

OS: CentOS 7, manual install (no Docker)
Browser Chromium
Database Postgres 13
Papermerge Version 1.5.0

@dani, thank you for opening this bug!

source: gharchive/issue

authors: ciur dani

repo: ciur/papermerge

license_type: permissive

license_source: github-api


text:
Feature request: Entertainment lens

I normally use the City Overlap lens for this, but I noticed how convenient the Power lens is for eyeballing which cities I should build power plants in and I was wondering if CQUI could provide an "Entertainment" lens that shows a similar radius for amenities from entertainment for zoos and aquariums.

Now that I think about it, it would be awesome to have a lens for every kind of area-effect building. For example, I would love to also have a "Factory" lens (or perhaps roll up both the entertainment and factory lenses as highlight modes in the city overlap lense).

license: MIT


text:
Add confirmation before discarding question drafts

Is your feature request related to a problem? Please describe.
When editing questions, the "discard draft" button is very close to edit.  If you click it by accident, your question might get deleted unexpectadly.
Describe the solution you'd like
Prompt for confirmation before deleting.

The original screenshot from this issue is outdated; the new one still has a "Discard Draft" button we should add a confirmation to.

authors: MichaelZetune kmcnellis

repo: civiform/civiform


text:
Fixes for bin/run-browser-tests-local

This fixes several issues found with running bin/run-browser-tests-local.

Adds a --local flag to bin/run-browser-test-env, which sets BASE_URL to http://localhost:9999, which the local browser tests expect. Otherwise, upon logout, it will attempt to go to civiform:9000 instead and fail. It also includes an additional compose file that exposes port 3390, as local tests will need to be able to talk to dev-oidc directly for redirects. Because this will conflict with bin/run-dev, this is not enabled by default.

Sets LOCALSTACK_URL to point to port 6645 in bin/run-browser-tests-local, which is what is specified in browser-test-compose.yml.

Adds the flag for starting the JVM debugger on port 9457 to allow connecting the debugger during browser tests.

Updates the test_oidc_provider.js file to add the paths for localhost:9999 as allowed redirect URIs.

Checklist
General

[x] Added the correct label: < feature | bug | dependencies | infrastructure | ignore-for-release >
[x] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Still need to update docs

Tested manually (with a locally rebuilt dev-oidc container) with the latest changes, everything still works 🎉

Docs update: https://github.com/civiform/docs/pull/262

source: gharchive/pull-request


text:
Branch application_navigation_buttons.test.ts for North Star

Description
Please explain the changes you made here.
Release notes
Remove this section if the title of the pull request can be used as the default release notes description. If more detail is needed to communicate to partners the scope of the PR's changes, use this release notes section (and remove this placeholder text).
Checklist
General
Read the full guidelines for PRs here

[ ] Added the correct label: < feature | enhancement | bug | under-development | dependencies | infrastructure | ignore-for-release | database >
[ ] Assigned to a specific person, civiform/developers, or a more specific round-robin list
[ ] Added an additional reviewer from outside your organization as FYI (if the primary reviewer is in the same organization as you)
[ ] Removed the release notes section if the title is sufficient for the release notes description, or put more details in that section.
[ ] Created unit and/or browser tests which fail without the change (if possible)
[ ] Performed manual testing (Chrome and Firefox if it includes front-end changes)
[ ] Extended the README / documentation, if necessary

Database evolutions
Read the guidelines here

[ ] Assigned two reviewers
[ ] Guarded against already existing resources using IF NOT EXISTS and IF EXISTS
[ ] Downs created to undo changes in Ups
[ ] Data migrations aren't being done (please use a Durable Job if doing a data migration)

Durable jobs
Read the docs here

[ ] Assigned two reviewers
[ ] Included a rollback plan and a job to undo the data changes if appropriate

User visible changes

[ ] Followed steps to internationalize any new strings

[ ] Added context strings to new messages
[ ] Didn't use a message in applicant facing code that isn't translated yet (unless behind a flag)

[ ] Wrote browser tests using the validateAccessibility method
[ ] Made equivalent changes in Thymeleaf for applicant-facing features and changes (or created an issue in the Northstar epic to track that it's missing from Thymeleaf)
[ ] Tested on mobile view. See mobile device mode
[ ] Manually tested at 200% size
[ ] Manually evaluated tab order

New Features

[ ] Add new FeatureFlag env vars to server/conf/helper/feature-flags.conf
[ ] Conditioned new functionality on a FeatureFlag
[ ] Wrote browser tests with the feature flag off and on, etc.

Instructions for manual testing
If instructions are needed for manual testing by reviewers, include them here.
Issue(s) this completes
Fixes #<issue_number>; Fixes #<issue_number>...

#8525  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ssandbekkhaug and the rest of your teammates on  Graphite


text:
🛑 Wikipedia is down

In 71b7974, Wikipedia (https://en.wikipedia.org) was down:

HTTP code: 500
Response time: 107 ms

Resolved: Wikipedia is back up in 0bd4346.


text:
Relative paths in dependencies

... should be treated as relative to the folder containing the deps file.

Fixed on main.


text:
Sprite sheet

Link #46
Please comment below if you would like this. This will be a lot of overhead to maintain when new icons are added...

You can indicate in the readme the possibility to create a sprite, but I think it is better that everyone creates their own sprites according to their needs (related to the size of the icons). It depends a lot on the size that the icons must have in publication. If you are quick to generate the 16x16 icon set for your export process, you might consider adding that format. Otherwise, each one generates the format optimized for its use.

Perhaps a script could generate a sprite sheet automatically from the SVG icons. That would get rid of the overhead, as we could auto-generate them with travis-ci when somebody pushes to master.

authors: cjdowner gallisiardi lunaroyster

repo: cjdowner/cryptocurrency-icons


text:
Ability to turn of LEDs on switch through home assistant

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
I own a Netgear GS308EPP and I have the LEDs disabled at night as my SO is very sensitive to light when sleeping. Right now i have to do this manually through the switch GUI but it seems possible through this integration. I do have some programming experience but no experience with home assistant so I am not sure how to add this functionality to your integration.
Describe the solution you'd like
Have a switch in Home Assistant that enables or disables the LED's so this can be automated.
Describe alternatives you've considered
Making a switch/automation/script in homeassistant to manually call the port_led.cgi endpoint, but i have not gotten this to work.
Additional context
I noticed in the network tab on my browser that the page port_led.cgi was called with a hash(I assume the hashed password) and an option named portled. This option is set to 2 for turning the LED's off and set to 0 to turn the LED's on.

I think the switch_leds function should probably look like this:
def switch_leds(self, state: str) -> bool:
    """Switch leds on or off."""
    if state not in SWITCH_STATES:
        return False
        for template in self.switch_model.LED_CONFIG_TEMPLATES:
            url = template["url"].format(ip=self.host)
            data = {
                "hash": self._client_hash,
                "portled": 0 if state == "on" else 2,
            }
            resp = self._request("post", url, data=data)
            if resp.status_code == requests.codes.ok:
                return True
    return False

Where LED_CONFIG_TEMPLATES is a member of the GS308EPP and contains:
LED_CONFIG_TEMPLATES: ClassVar = [
        {"method": "get", "url": "http://{ip}/port_led.cgi"}
]

But I am not sure how to implement the switch in homeassistant itself

Nice! The PoE power switch has some side effects. Does the LED switching form have additional fields as well?

No, its just an ON/OFF switch which you press apply on that disables the LEDs on the RJ45 ports, the power and POE max LED stay on. The request just has the hash and portled values.

authors: AcidWizard foxey

repo: ckarrie/ha-netgear-plus


text:
Fails to build in openSUSE Tumbleweed

When running 'make' I get this error

[ 27%] Building CXX object src/plugins/server/CMakeFiles/server.dir/HttpServer.cpp.o
In file included from /home/user/Git/musikcube/src/plugins/server/HttpServer.cpp:35:
/home/user/Git/musikcube/src/plugins/server/HttpServer.h:60:16: error: ‘MHD_Result’ does not name a type
60 |         static MHD_Result HandleRequest(
|                ^~~~~~~~~~
/home/user/Git/musikcube/src/plugins/server/HttpServer.cpp: In member function ‘bool HttpServer::Start()’:
/home/user/Git/musikcube/src/plugins/server/HttpServer.cpp:325:26: error: ‘HandleRequest’ is not a member of ‘HttpServer’
325 |             &HttpServer::HandleRequest,                 /* request handler callback */
|                          ^~~~~~~~~~~~~
/home/user/Git/musikcube/src/plugins/server/HttpServer.cpp: At global scope:
/home/user/Git/musikcube/src/plugins/server/HttpServer.cpp:359:1: error: ‘MHD_Result’ does not name a type
359 | MHD_Result HttpServer::HandleRequest(
| ^~~~~~~~~~
make[2]: *** [src/plugins/server/CMakeFiles/server.dir/build.make:96: src/plugins/server/CMakeFiles/server.dir/HttpServer.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:658: src/plugins/server/CMakeFiles/server.dir/all] Error 2
make: *** [Makefile:150: all] Error 2

I have all the dependencies as well. Though all the 'libboost' pkgs listed in dependencies are a bit older than the ones provided by Tumbleweed. Tumbleweed has version 71, not 68. Doubt that's relevant, but I figured I'd mention it.

Yep, looks like I got this line wrong: https://github.com/clangen/musikcube/commit/e8e9dbd30822be13a8b15a0e705ecee2c76eadd6#diff-c381f47b5a1c83dc019b1ab41a30e7c3R46
I'll try to get this patched up this evening or tomorrow. Thanks for the report!

Fixed https://github.com/clangen/musikcube/commit/ae1b2ee233cc6870294190ac57056d799470a431

authors: Nano-Ocelot clangen

repo: clangen/musikcube

license_source: bigquery


text:
[cudamapper] Moved cudaStreamSynchronize for merged_basepairs_h after the call to SketchElementImpl::generate_sketch_elements()

As suggested in #543 moved the call to cudaStreamSynchronize() for merged_basepairs_h  after the call to SketchElementImpl::generate_sketch_elements() in IndexGPU
Closes #543

rerun tests

repo: clara-parabricks/GenomeWorks


text:
Can i use this DND lib in NextJs or in any SSR ??

If i can use in any SSR(eg. Nextjs, etc) then that would be great..

It should work fine yes.

It is ready for use in production Apps ?

This project is in beta because there are currently some features that are not well supported. Having said that, this project is using semantic versioning, so major breaking changes will be identified and have clear migration steps outlined.
If the use case you're planning to build is similar to any of the examples on https://examples.dndkit.com, chances are that your use-case is well supported and production-ready.
We use @dnd-kit at scale at Shopify for millions of users, so you should feel fairly confident that it is a production-ready library.

Thank You for your answer

repo: clauderic/dnd-kit


text:
Calendar is jumping to the center of the screen on open

Hi!
First of all, thank you for such a great component!
I've experienced a problem.
I have a side panel which has nice slide CSS-animation.
However if I put this calendar into it this animation behaves very strange:

it push all panel to the center of the screen.
and move it back to the place where animation should stop.

I suppose it happen when plugin calculates absolute postitions.
Unfortunately can't share any code (project of my client), so it's just FYI.

Use autoFocus={false}. Helped me.

Use autoFocus={false}. Helped me.

authors: hedaktibo kahurangitama

repo: clauderic/react-infinite-calendar

license: mit


text:
Add option to change markdown delimiters.

Whilst it's common for math to use the $ delimiter, on Code Review it is specified by \$.
Can the ability to change the delimiters be made available in conf.py?
This would require changing doctree2md.py#L484, but I don't know how to get data from conf.py.

DISCONTINUED: This project is no longer maintained. The active version of this project is now being maintained at liran-funaro/sphinx-markdown-builder.

authors: Peilonrayz clayrisser

repo: clayrisser/sphinx-markdown-builder


text:
🛑 livevault is down

In 3c20fe7, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in e617e44.

repo: claytonplong/backup-uptime


text:
🛑 livevault is down

In cb7cf70, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in 0433224.


text:
🛑 www.offsitedatasync.com is down

In 97f73b1, www.offsitedatasync.com (https://www.offsitedatasync.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: www.offsitedatasync.com is back up in f621860.


text:
🛑 livevault is down

In 0d15ba5, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in 009c7c4.


text:
Should probably go into etc/parameters.csv or into raw

In this case, where the dataset is developed with the author of the raw data, the parameter descriptions (see
https://github.com/cldf-datasets/audersetinterrog/blob/7d5c51d9ad3876baede4260fa77f758803e5abe3/cldfbench_audersetinterrog.py#L10-L18 ) should probably go into raw - otherwise in etc.

Thanks, will move this.

authors: chrzyki xrotwang

repo: cldf-datasets/audersetinterrog


text:
fix: installation requirements and model-path updated

Added matplotlib in the requirements.txt
Code was breaking due to wrong model path : trained_models, which i renamed back to models

Keeping it a draft for now. I will check if I find more problems.

repo: clemkoa/ntm


text:
Fix user.update username not working

Type of change

[x] 🐛 Bug fix

Packages affected

[x] @clerk/types

Description

[x] npm test runs as expected.
[x] npm run build runs as expected.

Removes username from the user.update method (which does not work).
Fixes issue number #1494.

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

authors: ammarmbe clerk-cookie

repo: clerk/javascript


text:
Issue with User UpdateMetadata Function

I've been trying to use this method to update the public metadata and it doesn't seem to work. I've used the backend api restfully with no problem.
        client, err := clerk.NewClient(os.Getenv("CLERK_SECRET_KEY"))
	if err != nil {
		return nil, err
	}

	cx := map[string]interface{}{
		"workspaces": map[string]bool{
			"123": true,
		},
	}
	_, err = client.Users().UpdateMetadata("user_2XXXXXXXXXXXX", &clerk.UpdateUserMetadata{
		PublicMetadata: cx,
	})

When I make this call the user comes back with a public metadata of empty. Logging inside the package it appears to be sending it in the request however it does nothing.
Printing out the req and res in the package internally i see this.
req/res
&{PATCH https://api.clerk.dev/v1/users/user_2XXXXXXXXXXXX/metadata HTTP/1.1 1 1 map[X-Clerk-Sdk:[go/1.36.1]] {{"public_metadata":{"workspaces":{"123":true}},"private_metadata":null,"unsafe_metadata":null} |  +176ms  } 0x10441f590 112 [] false api.clerk.dev map[] map[] <nil> map[]   <nil> <nil> <nil> 0x14000038118} |  +375ms  &{200 OK 200 HTTP/2.0 2 0 map[Cf-Cache-Status:[DYNAMIC] Cf-Ray:[7ab14e6cf8502e64-DFW] Content-Type:[application/json] Date:[Mon, 20 Mar 2023 22:14:08 GMT] Server:[cloudflare] X-Cloud-Trace-Context:[ec7d191b85f3c99ebb21ceaac484a24b]] 0x1400018c040 -1 [] false true map[] 0x140002a2200 0x14000128790}
Not really sure what could be causing the problem here but it is responding with a 200 status. Happy to write my own rest request but I thought it was worth calling out or at least showing me what I could be doing wrong.
Appreciate the help in advance

This code worked without issue. Just figured i'd share
func (a clerky) SetWorkspaceIDs(ctx context.Context, userID string, workspaceID string) error {
	url := fmt.Sprintf("https://api.clerk.dev/v1/users/%s/metadata", userID)
	method := "PATCH"

	payload := map[string]interface{}{
		"public_metadata": map[string]interface{}{
			"workspaces": map[string]bool{
				workspaceID: true,
			},
		},
	}

	json, err := json.Marshal(payload)
	if err != nil {
		return err
	}
	fmt.Println(string(json))
	client := &http.Client{}
	req, err := http.NewRequest(method, url, bytes.NewReader(json))
	if err != nil {
		fmt.Println(err)
		return err
	}
	req.Header.Add("Authorization", fmt.Sprintf("Bearer %s", os.Getenv("CLERK_SECRET_KEY")))
	req.Header.Add("Content-Type", "application/json")

	res, err := client.Do(req)
	if err != nil {
		fmt.Println(err)
		return err
	}
	defer res.Body.Close()

	return nil
}

@dgocoder Thanks for reporting.
The metadata properties on the users service should be []byte (or json.RawMessage to be exact). Meaning that you should send the JSON encoded bytes to the response and not a map.
I can see why this is confusing though. The metadata fields have the wrong type. They are typed as interface{} which implies that a map can be used. This is wrong and we should update it.
In the meantime, can you try the same operation but encode the metadata first?
client, err := clerk.NewClient(os.Getenv("CLERK_SECRET_KEY"))
if err != nil {
  return nil, err
}

cx := map[string]interface{}{
  "workspaces": map[string]bool{
    "123": true,
  },
}

enc, err := json.Marshal(cx)
if err != nil {
  return nil, err
}

_, err = client.Users().UpdateMetadata("user_2XXXXXXXXXXXX", &clerk.UpdateUserMetadata{
  PublicMetadata: enc,
})

It would be awesome if you'd be willing to contribute a PR to fix this. We basically have to change all the user metadata types (PublicMetadata, PrivateMetadata and UnsafeMetadata) to json.RawMessage, similar to how it is for organizations for example.

would it not be best to have the type be map[string]interface{} and have library marshal it?

@dgocoder I think json.RawMessage offers more flexibility. If we type the metadata as map[string]interface{} then we limit the options of the consumer.
What if consumers have custom types (structs) for their metadata?
I think it's best if we accept the JSON encoded value and leave it up to the consumer to take care of serialization/deserialization.

@gkats pr is up ^

Closing issue as pr was merged

authors: dgocoder gkats

repo: clerkinc/clerk-sdk-go


text:
错误：用户管理，修改用户NickName名称保存后，手机号码被改变，存入数据库变成”180****5310“

master 分支完成修复。

repo: clickvisual/clickvisual


text:
Setting Content Length on GZip Requests

This adds a Content-Length to the response, if an original Content-Length was present, and less than 1MB. This prevents jetty from adding Transfer-Encoding: chunked to the response, without requiring Connection: Close

Hello Maintainers,
Do you have any feedback on this pull request?

Hi there, this looks like a good patch to include, are you able to add any tests? I realise it's been a long time since the original PR, so can understand if you've moved on.

Let me check. I know that we rely on this behaviour, but I can't remember what are the reasons are. IIRC, it was that some proxies were refusing to cache the response, as it believed that it was receiving a stream, or something like that.

I took a sensible default of only buffering responses up to 1mb in memory. This should cover most HTML responses and API responses, while only consuming < 1mb of memory. I doubt anyone will serve files more than 1 mb from ring.

authors: danielcompton gja

repo: clj-commons/ring-gzip-middleware


text:
Add foreign_key_check method to migrations

This implements a method to validate that all foreign keys are still valid after a migration as discussed in #4.
~This still lacks tests, feel free to comment on anything else.~

Surprisingly I get a different error within the test I am writing than when trying to run it within the project I want to use this for.

Thanks for the PR and for the edits to please the CI!
I’ll take a deeper look in the next few days.

Thanks for your contribution!

authors: Jokler cljoly


text:
NHN: Add more VM image info

NHN

Add more VM image info

https://github.com/cloud-barista/cb-spider/issues/1405

authors: ish-hcc powerkimhub

repo: cloud-barista/cb-spider


text:
Baremetal update

Description
First attempt to have network-perf tests check infrastructure type for BareMetal.
Fixes
Once BareMetal is detected as the infrastructure type, separate code is used to assign client and server worker nodes for the benchmark tests. Currently, it only assigns the first two worker nodes that are returned. The current code fails to assign the env vars as it is written for aws.
Secondly, I had to update PyYAML version as currently it seems to use a deprecated version that yaml.FullLoader does not exist and will cause the code to fail.

Do you mind squashing your commits cleanly, please?

Do you mind squashing your commits cleanly, please?


text:
Run all the litmus resources in a single namespace

Description
- This eases the usage and debuggability by running the fault injection pods in
  the same namespace as other resources of litmus. This will also ease the
  deletion process and ensure that there are no leftover objects on the cluster.

- This commit also enables users to use the same rbac template for all the litmus
  scenarios without having to pull in a specific one for each of the scenarios.

Would be nice to have a default cpu cores and nodes affected percentage in node_cpu_hog_engine similar to node_mem_engine
As well as a place holder for the node name
ex) '<node_name>'

repo: cloud-bulldozer/kraken


text:
Deliver July 2022 ConMon results by 8/2

In order for us to update the JAB on our compliance in a consistent way, we need to deliver a Continuous Monitoring report on [due date]. (our standard due date is the 2nd of the month. If these dates fall on a weekend or federal holiday, adjust to the last business day before the date.)
For context, see our Continuous Monitoring Strategy, including the monthly reporting summary explanation.
We need to process our scan results and prepare documentation for any updated or new items, including updating the vulnerability tracker and POA&M.
We always have to do these tasks:

List any new identified vulnerabilities in the vulnerability tracker.

Check for sneaky Nessus findings that apply to only a subset of components. Use the Nessus parse script to help.
Discard the ones listed as false positives.
The OWASP ZAP parse script can help.

Move any scanner items that should be moved to closed (items originally found by a scanner where we have new scans that prove these things are fixed).
Update all columns to include the most recent info about remediations, milestones, statuses, etc., including updating the status date column.
Cloud Operations needs to review the Nessus findings and ensure all daemons are managed by BOSH (see CG04 for context).
Add any late vulnerabilities to the POA&M worksheet (i.e. vulnerabilities that will be remediated later than 30, 90 or 180 days old).
Update cell D3 to be the current date for this POA&M (date of submission).
Copy the the summary cover sheet template and fill it out.

Depending on scan results, we sometimes also have to do these tasks:

For any items that require a monthly checkin with a vendor, Cloud Operations needs to make the appropriate support request to the vendor.
Write Deviation Requests for operational requirements, risk adjustments, and false positives.
Update our boards with current info about vulnerabilities and open POAM items and any necessary followup stories about compliance work and related technical work to prepare for the next month's report.
Open a PR to update our ConMon checklist template.

Rough notes on Peter's hacky tracking

Set up Google FileStream - Use from GSA SelfService, the upstream version doesn't seem to work for GSA.
Have cg-scripts in your $PATH
PIP install nessus-file-reader

I keep everything in ~/Documents/ConMon, so
cd ~/Documents
git clone file:///Volumes/GoogleDrive/My Drive/cloud.gov/Security and Compliance/Compliance/conmon_project.git ConMon
cd ConMon
source conmon.sh

That sets up a bunch of shell functions that we run, then copy/paste if they look correct.

setup_dir MM DD - Set up the correct names and places for our copies of the scan
Drag over from /Volumes/GoogleDrive/My Drive/18F_ISSO/FedRAMP JAB - cloud.gov - 3PAO Access/ZAP and Nessus results the

ZAP both XML and HTML
RDS *.nessus into the RDS folders
Compliance and Vuln *.nessus scans into folders. End result

    tree 2021/03
2021/03
├── 20210323-ZAP.html
├── 20210323-ZAP.xml
├── Production-and-Tooling-Vulnerability-and-Compliance-scans_2021-03-23
│   ├── Production_Compliance_scan_wkl5wr.nessus
│   ├── Production_Vulnerability_scan_241iec.nessus
│   ├── Tooling_Compliance_scan_odrbso.nessus
│   └── Tooling_Vulnerability_scan_aogr63.nessus
└── RDS_Compliance_Scans_2021-03-23
    ├── RDS_Compliance_-_Credhub_Prod_xctauy.nessus
    ├── RDS_Compliance_-_Credhub_Tooling_hi0ovb.nessus
    ├── RDS_Compliance_-_OpsUAA_Tooling_lnptdj.nessus
    ├── RDS_Compliance_Scan_-_ATC_Tooling_fmtjza.nessus
    ├── RDS_Compliance_Scan_-_Bosh_Tooling_6maygg.nessus
    ├── RDS_Compliance_Scan_BOSH_Prod_9nbxn6.nessus
    └── RDS_Compliance_Scan_CF_Prod_k9ysxd.nessus

Run prep_nessus function

This generates MM.nessus_summary and MM.nessus_work - This month's summary is compared, using comm to last month's summary.

Review MM.nessus_summary, and Git add/commit it if it's OK.
The file MM.nessus_work looks like this:

LAST MONTH (fixed)
	THIS MONTH (new)
		BOTH  (persisting)
	147163, Risk: Medium, Plugin Name: Apache Tomcat 7.0.0 < 7.0.108 RCE, https://www.tenable.com/plugins/nessus/147163
   ..hostnames or number of impacted hosts

The items left-aligned are ones that we're in last months' report but are now fixed, the next indent are those that are new (present now, absent last month), and the third indent are present in both months' scans (persisting issues)

Move the fixed items to Done in the vulnerability tracker, updating the status date
Add the new items

run parse-nessus-xml.py and get the CVS output.
paste into vulnerability tracker, then use the Data menu to convert to Split Text to Columns
fix up the entry
copy down the formula for Column M, "Scheduled Completion Date", to generate the due date based on severity

Use the prep_zap function for ZAP scan consolidation

Likewise, work through the MM.zap_work file
Mostly ignore the Low findings

Move fixed issues from Open to Closed tabs. Be sure to

Update the Status Date
Update the Supporting Documents, unless routine stemcell patch covered by the scan output

Be sure to

Review the RDS scans:

cd to the directory with the RDS compliance scans,
run ../../../parse-rds.sh

Review the Compliance scans:

No good parsing yet, review manually

Address all gravely late POA&Ms

Go to the POA&M Dashboard
For each 90+day late POA&M, be sure to update the Milestone Changes filed
of the POA&M sheet

Review the Inventory

Update RDS postgres versions if necessary

Acceptance criteria

[x] We uploaded our POA+M summary to MAX.gov https://community.max.gov/display/FedRAMPExternal/18F+Continuous+Monitoring 'POA&M and Inventory' folder
[x] We uploaded our Inventory sheet to MAX.gov https://community.max.gov/display/FedRAMPExternal/18F+Continuous+Monitoring 'POA&M and Inventory' folder
[ ] We uploaded our Nessus and OWASP scan results to MAX.gov to https://community.max.gov/display/FedRAMPExternal/18F+Vulnerability+Scans
[x] We uploaded the Summary Excel sheet to https://community.max.gov/display/FedRAMPExternal/18F+Continuous+Monitoring
[ ] We created next month's issue for this task and for running the scans.

I have uploaded the ConMon results for July to Max.gov

repo: cloud-gov/product


text:
Update document to adding argocd CLI to create applications

We need to update document to adding argocd CLI to create applications, so that the CICD or some test tools can leverage argocd CLI to do gitops.

we can also use the CLI like kubectl/oc apply -f application.yaml to create the gitops applications which is also kubernetes native.

We can update 3.2 document first @liyanwei93


text:
java.lang.NoClassDefFoundError: com.squareup.okhttp.Authenticator

I see that okhttp is optional and we're seeing Caused by: java.lang.NoClassDefFoundError: com.squareup.okhttp.Authenticator
Please include the following information in your ticket.

CloudantClient (java-cloudant) version(s) that are affected by this issue.
2.6.0
Java version (including vendor and platform).
1.7
If you're using the optional okhttp dependency.
Not using okhttp
A small code sample that demonstrates the issue.

Caused by: java.lang.NoClassDefFoundError: com.ibm.ecm.box.auth.helper.GafHelper (initialization failure)
at java.lang.J9VMInternals.initializationAlreadyFailed(J9VMInternals.java:87)
at com.ibm.ecm.box.auth.tai.GalaxyTAI.processGafToken(GalaxyTAI.java:76)
at com.ibm.ecm.box.auth.tai.GalaxyTAI.negotiateValidateandEstablishTrust(GalaxyTAI.java:392)
at com.ibm.ws.webcontainer.security.internal.TAIAuthenticator.authenticate(TAIAuthenticator.java:110)
at com.ibm.ws.webcontainer.security.WebProviderAuthenticatorProxy.handleTAI(WebProviderAuthenticatorProxy.java:250)
at com.ibm.ws.webcontainer.security.WebProviderAuthenticatorProxy.authenticate(WebProviderAuthenticatorProxy.java:109)
at com.ibm.ws.webcontainer.security.WebAuthenticatorProxy.authenticate(WebAuthenticatorProxy.java:69)
at com.ibm.ws.webcontainer.security.WebAppSecurityCollaboratorImpl.authenticateRequest(WebAppSecurityCollaboratorImpl.java:950)
at com.ibm.ws.webcontainer.security.WebAppSecurityCollaboratorImpl.determineWebReply(WebAppSecurityCollaboratorImpl.java:770)
at com.ibm.ws.webcontainer.security.WebAppSecurityCollaboratorImpl.performSecurityChecks(WebAppSecurityCollaboratorImpl.java:600)
at com.ibm.ws.webcontainer.security.WebAppSecurityCollaboratorImpl.preInvoke(WebAppSecurityCollaboratorImpl.java:524)
at com.ibm.wsspi.webcontainer.collaborator.CollaboratorHelper.preInvokeCollaborators(CollaboratorHelper.java:457)
at com.ibm.ws.webcontainer.osgi.collaborator.CollaboratorHelperImpl.preInvokeCollaborators(CollaboratorHelperImpl.java:267)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1124)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:4867)
... 18 more
Caused by: java.lang.NoClassDefFoundError: com.squareup.okhttp.Authenticator
at com.cloudant.client.org.lightcouch.CouchDbClient.(CouchDbClient.java:95)
at com.cloudant.client.org.lightcouch.CouchDbClient.(CouchDbClient.java:140)
at com.cloudant.client.api.CloudantClient.(CloudantClient.java:138)
at com.cloudant.client.api.ClientBuilder.build(ClientBuilder.java:330)
at com.ibm.ecm.box.auth.helper.GafHelper.tryAcquireDatabase(GafHelper.java:120)
at com.ibm.ecm.box.auth.helper.GafHelper.getCloudantInfo(GafHelper.java:82)
at com.ibm.ecm.box.auth.helper.GafHelper.DBPrep(GafHelper.java:164)
at com.ibm.ecm.box.auth.helper.GafHelper.(GafHelper.java:209)
at com.ibm.ecm.box.auth.tai.GalaxyTAI.processGafToken(GalaxyTAI.java:76)

Ah i see this is a duplicate of https://github.com/cloudant/java-cloudant/issues/294

Thanks for spotting its a duplicate, closing.

repo: cloudant/java-cloudant


text:
🛑 cbn.id is down

In 8538722, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in ef5aded.

repo: cloudbip/upptime


text:
🛑 masterweb.com is down

In 4937ec2, masterweb.com (https://masterweb.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: masterweb.com is back up in 8013651 after 32 minutes.


text:
🛑 lintas.net.id is down

In f7a1002, lintas.net.id (https://lintas.net.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: lintas.net.id is back up in 54a69e0 after 20 minutes.


text:
🛑 masterweb.com is down

In 8c0a425, masterweb.com (https://masterweb.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: masterweb.com is back up in e520069 after 34 minutes.


text:
🛑 sarang.id is down

In ee85951, sarang.id (https://sarang.id) was down:

HTTP code: 500
Response time: 1323 ms

Resolved: sarang.id is back up in 27dcc02.


text:
🛑 connectindo.com is down

In b0e7463, connectindo.com (https://connectindo.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: connectindo.com is back up in f91b1b3.


text:
🛑 cbn.id is down

In 4dc32cd, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in 142c736.


text:
🛑 dijaminmurah.com is down

In ef8e7ef, dijaminmurah.com (https://dijaminmurah.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: dijaminmurah.com is back up in 446ee68.


text:
🛑 cbn.id is down

In 127fe7a, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in 83b31db.


text:
Allow controller hook methods to return an error response

It makes sense in the controller to use something like the creating() hook to abort with a JSON API error. There are two approaches that could be used:

Allow the hook method to return a response, i.e. to do return $this->reply()->errors()
Add an abort() method that throws a JsonApiException: this would need to support passing a string key that can be resolved as an error key from the errors repository.

If (2) the abort method could be added to the reply trait helper.

An additional option is to add JSON API versions of Laravel's abort, abort_if and abort_unless helpers. I.e. jsonapi_abort etc.

An example of why this is needed is in this question:
https://github.com/cloudcreativity/laravel-json-api/issues/152

The abort helpers are definitely a good idea, but do still need to support the controller hooks returning responses. For example, we have a case where we need to return 202 Accepted for an update request. Throwing an exception with abort seems overkill. The other option is to overload the doUpdate method, but it's a lot of code just to return a different response:
    protected function doUpdate(
        StoreInterface $store,
        $record,
        ResourceObjectInterface $resource,
        EncodingParametersInterface $parameters
    ) {
        parent::doUpdate($store, $record, $resource, $parameters);

        return $this->reply()->meta([
            'accepted-at' => Carbon::now()->toW3cString()
        ], 202);
    }

This would be neater:
    protected function updated()
    {
        return $this->reply()->meta([
            'accepted-at' => Carbon::now()->toW3cString()
        ], 202);
    }

Decided to not add the abort helpers for the moment. Returning a response from a controller hook is now fully supported, and that meets the immediate requirement for the moment.

repo: cloudcreativity/laravel-json-api


text:
'Path used multiple times' when migrating to v2

(Also on Stackoverflow)
Hello
I tried to follow the steps to migrate to v2 (appengine app) and faced what seems to be a bug.
I have multiple APIs under the same AppEngine service (pretty much like here), and changed my app.yaml, downloaded the cloud-endpoints library, put it in the /lib folder...
Then I pushed the code to AppEngine, using  gcloud app deploy only (at this time I did not know about gcloud service-management, we were not using this before).
When trying to call one of my endpoints then, I got this error 'ApiConfigurationError: POST path "synchro" used multiple times, in classes SQL and Synchro'
That's true, but those two methods are under differents APIs so it should work (it does, in v1).
My code
@endpoints.api(name="sql", version='v1.0')
class SQL(remote.Service):
   @endpoints.method(
        CREATE_SYNCHRO,
        message_types.VoidMessage,
        path='synchro',
        http_method='POST',
        name='synchros.start'
    )

@endpoints.api(name='synchro', version='v1.0')
class Synchro(remote.Service):
    @endpoints.method(
        DayUserList,
        UserList,
        path='synchro',
        http_method='POST',
        name='synchronisation'
    )

(So migrating from v1 to v2 does not seem to be as simple as Google says... :) )

Facing a similar issue.

Thanks for the report. I'll look into this soon.

Not 100% sure this was fixed; reopening to double-check.

Blocked by #47.

This has been added to the endpoints Known Issues page.

authors: ValentinCoudert inklesspen m-murad

repo: cloudendpoints/endpoints-python


text:
Hue does not provide the option to provide krb5.conf path

hue does not have any option to set krb5.conf other than default /etc/krb5.conf. What is the workaround for this issue ?

This can be changed by:
[desktop]
[[kerberos]]
ccache_path=/some/alternate/path/to/ticket/cache

@romainr : Request is for KRB5CCNAME ( krb5.conf). property you mentioned is cache path but not the conf path.

repo: cloudera/hue


text:
For Go, are we allowed to use net/http?

The instructions are a little vague. For Go, are we allowed to use the net/http package? Or are we expected to make the HTTP request without it?
It seems to be the most basic way to make an HTTP request, but I'm not sure if this violates the guideline of not using libraries to "handle" HTTP requests.

You are expected to make the HTTP request without it.
Joaquin
On Mon, Oct 19, 2020 at 12:48 PM 'Pranav Singh' via
cloudflare-assignment-application <
cloudflare-assignment-application@cloudflare.com> wrote:

The instructions are a little vague. For Go, are we allowed to use the
net/http package? Or are we expected to make the HTTP request without it?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cloudflare-hiring/cloudflare-2020-systems-engineering-assignment/issues/4,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARBVIAOGETX5YG3DQAS75ZTSLR3XRANCNFSM4SWO2WMQ
.
--
You received this message because you are subscribed to the Google Groups
"cloudflare-assignment-application" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to cloudflare-assignment-application+unsubscribe@cloudflare.com.
To view this discussion on the web visit
https://groups.google.com/a/cloudflare.com/d/msgid/cloudflare-assignment-application/cloudflare-hiring/cloudflare-2020-systems-engineering-assignment/issues/4%40github.com
https://groups.google.com/a/cloudflare.com/d/msgid/cloudflare-assignment-application/cloudflare-hiring/cloudflare-2020-systems-engineering-assignment/issues/4%40github.com?utm_medium=email&utm_source=footer
.
For more options, visit
https://groups.google.com/a/cloudflare.com/d/optout.

--
Joaquin Madruga | Engineering Director
joaquin@cloudflare.com
1 888 99 FLARE  |  www.cloudflare.com

@cloudflare-hiring We Could use "net" but not http? or we can't use both?

@cloudflare-hiring Can we use std::net::TcpStream in Rust?

So in our profile program, do we need to support http2, http3?
And could we use the tls (golang) package for https traffic?

@cloudflare-hiring Can we use std::net::TcpStream in Rust?

See https://github.com/cloudflare-hiring/cloudflare-2020-systems-engineering-assignment/issues/8#issuecomment-713549195

You are expected to make the HTTP request without it. Joaquin
…
On Mon, Oct 19, 2020 at 12:48 PM 'Pranav Singh' via cloudflare-assignment-application < @.> wrote: The instructions are a little vague. For Go, are we allowed to use the net/http package? Or are we expected to make the HTTP request without it? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARBVIAOGETX5YG3DQAS75ZTSLR3XRANCNFSM4SWO2WMQ . -- You received this message because you are subscribed to the Google Groups "cloudflare-assignment-application" group. To unsubscribe from this group and stop receiving emails from it, send an email to @. To view this discussion on the web visit https://groups.google.com/a/cloudflare.com/d/msgid/cloudflare-assignment-application/cloudflare-hiring/cloudflare-2020-systems-engineering-assignment/issues/4%40github.com https://groups.google.com/a/cloudflare.com/d/msgid/cloudflare-assignment-application/cloudflare-hiring/cloudflare-2020-systems-engineering-assignment/issues/4%40github.com?utm_medium=email&utm_source=footer . For more options, visit https://groups.google.com/a/cloudflare.com/d/optout.
-- Joaquin Madruga | Engineering Director joaquin@cloudflare.com 1 888 99 FLARE | www.cloudflare.com

are we allowed to use the bare net package in Go?

@cloudflare-hiring  clarifications are must needed as we are approaching to the end of the 1st week which is suggested submission timing simple question can we use https://golang.org/pkg/net/ package? I believe it's same as 'net' package in RUST which you gave a green signal to

The net package is fine.
Thanks!
Joaquin
On Wed, Oct 21, 2020 at 4:11 PM 'Varnit Sharma' via
cloudflare-assignment-application <
cloudflare-assignment-application@cloudflare.com> wrote:

@cloudflare-hiring https://github.com/cloudflare-hiring clarifications
are must needed as we are approaching to the end of the 1st week which is
suggested submission timing simple question can we use
https://golang.org/pkg/net/ http://url package? I believe it's same as
'net' package in RUST which you gave a green signal to
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cloudflare-hiring/cloudflare-2020-systems-engineering-assignment/issues/4#issuecomment-713879810,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARBVIAJHR3FK62EODGO3GQLSL5E7VANCNFSM4SWO2WMQ
.
--
You received this message because you are subscribed to the Google Groups
"cloudflare-assignment-application" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to cloudflare-assignment-application+unsubscribe@cloudflare.com.
To view this discussion on the web visit
https://groups.google.com/a/cloudflare.com/d/msgid/cloudflare-assignment-application/cloudflare-hiring/cloudflare-2020-systems-engineering-assignment/issues/4/713879810%40github.com
https://groups.google.com/a/cloudflare.com/d/msgid/cloudflare-assignment-application/cloudflare-hiring/cloudflare-2020-systems-engineering-assignment/issues/4/713879810%40github.com?utm_medium=email&utm_source=footer
.
For more options, visit
https://groups.google.com/a/cloudflare.com/d/optout.

--
Joaquin Madruga | Engineering Director
joaquin@cloudflare.com
1 888 99 FLARE  |  www.cloudflare.com

authors: LunaticProgrammer cloudflare-hiring hcrdtc jihchi pranavs99 qinyudiao


text:
[Chore] Fix code blocks, pt 1

Summary
Large block, mostly CF1

relates to #16210

repo: cloudflare/cloudflare-docs


text:
add delete for url normalization

Description
Adds delete function for url normalization that will disable the feature.
What sort of change does your code introduce/modify?

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

do we have the public API docs for this yet? we already have #1078 but that takes a different approach which leads me to want to wait the docs for this to confirm stability.

is this still required?

closing this off due to being stale. if we still need this, let's open a new PR and port the changes there to get this over the line.

hi

authors: jacobbednarz jafowler jameskillough627

repo: cloudflare/cloudflare-go


text:
rulesets: add support for http_request_redirect phase and redirect action

Description
The from_list parameter is used in the redirect action (see https://developers.cloudflare.com/rules/bulk-redirects/create-api/#3-create-a-bulk-redirect-rule-via-api), among others.
Types of changes
What sort of change does your code introduce/modify?

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] This change is using publicly documented (api.cloudflare.com or developers.cloudflare.com) and stable APIs.

we'll also need to add http_request_redirect to the phases to be able to use this. check out #924 for an example of adding this.

i added these changes to get them into the main branch and available for testing with other systems.

authors: jacobbednarz piperswe


text:
Interop test API compliance

I tested the container image cloudflare/daphne-worker-helper:sha-b150547 and ran into three issues, all with the test API and not DAP.

The process in the container listens on port 8787 instead of 8080.

Nice-to-have: an EXPOSE directive in the Dockerfile would simplify manual use, as it would let you use --publish-all.

It expects requests to /internal/test/add_task to have a verify_key attribute instead of vdaf_verify_key. (this changed in a subsequent draft version)
It expects VDAF types to be "Prio3Aes128Count" and "Prio3Aes128Sum" instead of "Prio3Count" and "Prio3Sum".

Fixed by #273 and docker improvements in #278.

authors: bhalleycf divergentdave

repo: cloudflare/daphne


text:
Better to be able to load JSON schema files in runtime

Is it possible not to compile JSON schema files. Instead, load schema files in runtime, especially from a URL?

@shenghu what do you mean by runtime?  Do you want to use this to browse dynamically generated documentation in some way?  Or are you talking about interacting with the API (making calls over HTTP) based on the schemas?  In both cases, the answer is "not currently, but it is something I'm actively looking into."
If neither is what you have in mind, could you go into a bit more detail?
Either way, I would love to hear more about your use cases.

@handrews I mean whether doca can provide a similar online editor like http://editor.swagger.io/ which can load schemas from a url. If editor is not easy, a viewer is mostly wanted to allow user to view json schema in a nice way.
Today, Doca is good. It would be better if it needn't compile schema files, but simply load ones from anywhere.
BTW, another benefit of online viewer/editor is that users can embed it as an iframe to their page.

BTW, I create this theme, doca-events-api-theme,  (just start) which is to generate non-REST document, e.g. events. The theme can group schema files by category. category is not standard in JSON schema. But let's see if there is a better way.

@shenghu I will respond to your other points later, but just so that you know I've been changing the output of json-schema-example-loader (eventually it will not be so different from the standard schema, just with some convenience data added).  The current doca-bootstrap-theme does not use this new version of the example loader, so you might want to look at the example loader's changelog in its repository to see if you would like to build your theme on newer code.
There is a roadmap document in this repository outlining where I'm going with things, although it's not a firm commitment.

I would love to have an editor like that, but don't see a way to staff that work from within the company right now.  Of course if anyone wants to work on it as an open source contribution I'd be happy to coordinate :-)
I am also an author/editor of the JSON Schema draft specifications, and my focus right now is on publishing draft-07.  Future doca work will probably prioritize moving to that draft and hopefully making it easier to extend the system with things like editors.

@shenghu there is now a new doca back-end (and hopefully soon a new set of themes) at the JSON Schema Tools monorepo.  The new doca is @cloudflare/doca, to keep it separate from the existing doca, which is still usable but will not be update except by volunteer contributions.
The new back-end outputs valid JSON Schemas (optionally with extensions), so the interface for building themes is now different.  But standard JSON Schema tools can now be used with the output schemas in case you want to further process them before display.  Or build an editor :-)
We believe that aligning Doca with the JSON Schema standard for both input and output will make it easier to support and extend the project, and draw on the larger JSON Schema community.
I'm closing this because this repo is now more or less dormant, but feel free to open an issue at the new repo.

authors: handrews shenghu

repo: cloudflare/doca


text:
Missing Dependency "LuaSocket" for running unit tests

After a fresh clone of the project repo and installation lunit, luaposix as specified in the README.md, unit tests still won't run.
$ make test
lua: tests/test_exceptions.lua:3: module 'socket' not found:
    no field package.preload['socket']
    no file '/usr/local/share/lua/5.2/socket.lua'
    no file '/usr/local/share/lua/5.2/socket/init.lua'
    no file '/usr/local/lib/lua/5.2/socket.lua'
    no file '/usr/local/lib/lua/5.2/socket/init.lua'
    no file './socket.lua'
    no file '/usr/local/lib/lua/5.2/socket.so'
    no file '/usr/local/lib/lua/5.2/loadall.so'
    no file './socket.so'
stack traceback:
    [C]: in function 'require'
    tests/test_exceptions.lua:3: in function 'chunk'
    /usr/local/share/lua/5.2/lunit.lua:628: in function 'loadtestcase'
    /usr/local/share/lua/5.2/lunit.lua:657: in function 'main'
    stdin:11: in main chunk
    [C]: in ?
make: *** [test] Error 1

It did run after LuaSocket is installed though.
$ luarocks install luasocket
Installing https://luarocks.org/luasocket-3.0rc1-2.src.rock...
Using https://luarocks.org/luasocket-3.0rc1-2.src.rock... switching to 'build' mode
Archive:  v3.0-rc1.zip
22cd5833fcc0e272f26004a79c8545e959ba406b
   creating: luasocket-3.0-rc1/
  inflating: luasocket-3.0-rc1/.gitignore
  inflating: luasocket-3.0-rc1/.travis.yml
  inflating: luasocket-3.0-rc1/FIX
  inflating: luasocket-3.0-rc1/LICENSE
  inflating: luasocket-3.0-rc1/Lua51.props
  inflating: luasocket-3.0-rc1/Lua52.props
  inflating: luasocket-3.0-rc1/NEW
  inflating: luasocket-3.0-rc1/README
  inflating: luasocket-3.0-rc1/TODO
  inflating: luasocket-3.0-rc1/WISH
   creating: luasocket-3.0-rc1/doc/
  inflating: luasocket-3.0-rc1/doc/dns.html
  inflating: luasocket-3.0-rc1/doc/ftp.html
  inflating: luasocket-3.0-rc1/doc/http.html
  inflating: luasocket-3.0-rc1/doc/index.html
  inflating: luasocket-3.0-rc1/doc/installation.html
  inflating: luasocket-3.0-rc1/doc/introduction.html
  inflating: luasocket-3.0-rc1/doc/ltn12.html
  inflating: luasocket-3.0-rc1/doc/lua05.ppt
  inflating: luasocket-3.0-rc1/doc/luasocket.png
  inflating: luasocket-3.0-rc1/doc/mime.html
  inflating: luasocket-3.0-rc1/doc/reference.css
  inflating: luasocket-3.0-rc1/doc/reference.html
  inflating: luasocket-3.0-rc1/doc/smtp.html
  inflating: luasocket-3.0-rc1/doc/socket.html
  inflating: luasocket-3.0-rc1/doc/tcp.html
  inflating: luasocket-3.0-rc1/doc/udp.html
  inflating: luasocket-3.0-rc1/doc/url.html
   creating: luasocket-3.0-rc1/etc/
  inflating: luasocket-3.0-rc1/etc/README
  inflating: luasocket-3.0-rc1/etc/b64.lua
  inflating: luasocket-3.0-rc1/etc/check-links.lua
  inflating: luasocket-3.0-rc1/etc/check-memory.lua
  inflating: luasocket-3.0-rc1/etc/cookie.lua
  inflating: luasocket-3.0-rc1/etc/dict.lua
  inflating: luasocket-3.0-rc1/etc/dispatch.lua
  inflating: luasocket-3.0-rc1/etc/eol.lua
  inflating: luasocket-3.0-rc1/etc/forward.lua
  inflating: luasocket-3.0-rc1/etc/get.lua
  inflating: luasocket-3.0-rc1/etc/links
  inflating: luasocket-3.0-rc1/etc/lp.lua
  inflating: luasocket-3.0-rc1/etc/qp.lua
  inflating: luasocket-3.0-rc1/etc/tftp.lua
   creating: luasocket-3.0-rc1/gem/
  inflating: luasocket-3.0-rc1/gem/ex1.lua
  inflating: luasocket-3.0-rc1/gem/ex10.lua
  inflating: luasocket-3.0-rc1/gem/ex11.lua
  inflating: luasocket-3.0-rc1/gem/ex12.lua
  inflating: luasocket-3.0-rc1/gem/ex2.lua
  inflating: luasocket-3.0-rc1/gem/ex3.lua
  inflating: luasocket-3.0-rc1/gem/ex4.lua
  inflating: luasocket-3.0-rc1/gem/ex5.lua
  inflating: luasocket-3.0-rc1/gem/ex6.lua
  inflating: luasocket-3.0-rc1/gem/ex7.lua
  inflating: luasocket-3.0-rc1/gem/ex8.lua
  inflating: luasocket-3.0-rc1/gem/ex9.lua
  inflating: luasocket-3.0-rc1/gem/gem.c
  inflating: luasocket-3.0-rc1/gem/gt.b64
  inflating: luasocket-3.0-rc1/gem/input.bin
  inflating: luasocket-3.0-rc1/gem/ltn012.tex
  inflating: luasocket-3.0-rc1/gem/luasocket.png
  inflating: luasocket-3.0-rc1/gem/makefile
  inflating: luasocket-3.0-rc1/gem/myps2pdf
  inflating: luasocket-3.0-rc1/gem/t1.lua
  inflating: luasocket-3.0-rc1/gem/t1lf.txt
  inflating: luasocket-3.0-rc1/gem/t2.lua
  inflating: luasocket-3.0-rc1/gem/t2.txt
  inflating: luasocket-3.0-rc1/gem/t2gt.qp
  inflating: luasocket-3.0-rc1/gem/t3.lua
  inflating: luasocket-3.0-rc1/gem/t4.lua
  inflating: luasocket-3.0-rc1/gem/t5.lua
  inflating: luasocket-3.0-rc1/gem/test.lua
  inflating: luasocket-3.0-rc1/linux.cmd
  inflating: luasocket-3.0-rc1/logo.ps
  inflating: luasocket-3.0-rc1/ltn012.wiki
  inflating: luasocket-3.0-rc1/ltn013.wiki
  inflating: luasocket-3.0-rc1/luasocket-scm-0.rockspec
  inflating: luasocket-3.0-rc1/luasocket.sln
  inflating: luasocket-3.0-rc1/macosx.cmd
  inflating: luasocket-3.0-rc1/makefile
  inflating: luasocket-3.0-rc1/makefile.dist
  inflating: luasocket-3.0-rc1/mime.vcxproj
  inflating: luasocket-3.0-rc1/mime.vcxproj.filters
  inflating: luasocket-3.0-rc1/mingw.cmd
   creating: luasocket-3.0-rc1/samples/
  inflating: luasocket-3.0-rc1/samples/README
  inflating: luasocket-3.0-rc1/samples/cddb.lua
  inflating: luasocket-3.0-rc1/samples/daytimeclnt.lua
  inflating: luasocket-3.0-rc1/samples/echoclnt.lua
  inflating: luasocket-3.0-rc1/samples/echosrvr.lua
  inflating: luasocket-3.0-rc1/samples/listener.lua
  inflating: luasocket-3.0-rc1/samples/lpr.lua
  inflating: luasocket-3.0-rc1/samples/mclisten.lua
  inflating: luasocket-3.0-rc1/samples/mcsend.lua
  inflating: luasocket-3.0-rc1/samples/talker.lua
  inflating: luasocket-3.0-rc1/samples/tinyirc.lua
  inflating: luasocket-3.0-rc1/socket.vcxproj
  inflating: luasocket-3.0-rc1/socket.vcxproj.filters
   creating: luasocket-3.0-rc1/src/
  inflating: luasocket-3.0-rc1/src/auxiliar.c
  inflating: luasocket-3.0-rc1/src/auxiliar.h
  inflating: luasocket-3.0-rc1/src/buffer.c
  inflating: luasocket-3.0-rc1/src/buffer.h
  inflating: luasocket-3.0-rc1/src/except.c
  inflating: luasocket-3.0-rc1/src/except.h
  inflating: luasocket-3.0-rc1/src/ftp.lua
  inflating: luasocket-3.0-rc1/src/headers.lua
  inflating: luasocket-3.0-rc1/src/http.lua
  inflating: luasocket-3.0-rc1/src/inet.c
  inflating: luasocket-3.0-rc1/src/inet.h
  inflating: luasocket-3.0-rc1/src/io.c
  inflating: luasocket-3.0-rc1/src/io.h
  inflating: luasocket-3.0-rc1/src/ltn12.lua
  inflating: luasocket-3.0-rc1/src/luasocket.c
  inflating: luasocket-3.0-rc1/src/luasocket.h
  inflating: luasocket-3.0-rc1/src/makefile
  inflating: luasocket-3.0-rc1/src/mbox.lua
  inflating: luasocket-3.0-rc1/src/mime.c
  inflating: luasocket-3.0-rc1/src/mime.h
  inflating: luasocket-3.0-rc1/src/mime.lua
  inflating: luasocket-3.0-rc1/src/options.c
  inflating: luasocket-3.0-rc1/src/options.h
  inflating: luasocket-3.0-rc1/src/select.c
  inflating: luasocket-3.0-rc1/src/select.h
  inflating: luasocket-3.0-rc1/src/serial.c
  inflating: luasocket-3.0-rc1/src/smtp.lua
  inflating: luasocket-3.0-rc1/src/socket.h
  inflating: luasocket-3.0-rc1/src/socket.lua
  inflating: luasocket-3.0-rc1/src/tcp.c
  inflating: luasocket-3.0-rc1/src/tcp.h
  inflating: luasocket-3.0-rc1/src/timeout.c
  inflating: luasocket-3.0-rc1/src/timeout.h
  inflating: luasocket-3.0-rc1/src/tp.lua
  inflating: luasocket-3.0-rc1/src/udp.c
  inflating: luasocket-3.0-rc1/src/udp.h
  inflating: luasocket-3.0-rc1/src/unix.c
  inflating: luasocket-3.0-rc1/src/unix.h
  inflating: luasocket-3.0-rc1/src/url.lua
  inflating: luasocket-3.0-rc1/src/usocket.c
  inflating: luasocket-3.0-rc1/src/usocket.h
  inflating: luasocket-3.0-rc1/src/wsocket.c
  inflating: luasocket-3.0-rc1/src/wsocket.h
   creating: luasocket-3.0-rc1/test/
  inflating: luasocket-3.0-rc1/test/README
   creating: luasocket-3.0-rc1/test/auth/
 extracting: luasocket-3.0-rc1/test/auth/.htpasswd
  inflating: luasocket-3.0-rc1/test/auth/index.html
   creating: luasocket-3.0-rc1/test/cgi/
  inflating: luasocket-3.0-rc1/test/cgi/cat
  inflating: luasocket-3.0-rc1/test/cgi/cat-index-html
  inflating: luasocket-3.0-rc1/test/cgi/env
  inflating: luasocket-3.0-rc1/test/cgi/query-string
  inflating: luasocket-3.0-rc1/test/cgi/redirect-loop
  inflating: luasocket-3.0-rc1/test/cgi/request-uri
  inflating: luasocket-3.0-rc1/test/dicttest.lua
  inflating: luasocket-3.0-rc1/test/excepttest.lua
  inflating: luasocket-3.0-rc1/test/find-connect-limit
  inflating: luasocket-3.0-rc1/test/ftptest.lua
  inflating: luasocket-3.0-rc1/test/hello.lua
  inflating: luasocket-3.0-rc1/test/httptest.lua
  inflating: luasocket-3.0-rc1/test/index.html
  inflating: luasocket-3.0-rc1/test/ltn12test.lua
  inflating: luasocket-3.0-rc1/test/luasocket.png
  inflating: luasocket-3.0-rc1/test/mimetest.lua
  inflating: luasocket-3.0-rc1/test/smtptest.lua
  inflating: luasocket-3.0-rc1/test/stufftest.lua
  inflating: luasocket-3.0-rc1/test/tcp-getoptions
  inflating: luasocket-3.0-rc1/test/test_bind.lua
  inflating: luasocket-3.0-rc1/test/test_getaddrinfo.lua
  inflating: luasocket-3.0-rc1/test/test_socket_error.lua
  inflating: luasocket-3.0-rc1/test/testclnt.lua
  inflating: luasocket-3.0-rc1/test/testmesg.lua
  inflating: luasocket-3.0-rc1/test/testsrvr.lua
  inflating: luasocket-3.0-rc1/test/testsupport.lua
  inflating: luasocket-3.0-rc1/test/tftptest.lua
  inflating: luasocket-3.0-rc1/test/udp-zero-length-send
  inflating: luasocket-3.0-rc1/test/udp-zero-length-send-recv
  inflating: luasocket-3.0-rc1/test/udpconnectclnt.lua
  inflating: luasocket-3.0-rc1/test/udpconnectsrvr.lua
  inflating: luasocket-3.0-rc1/test/unixclnt.lua
  inflating: luasocket-3.0-rc1/test/unixsrvr.lua
  inflating: luasocket-3.0-rc1/test/upload.html
  inflating: luasocket-3.0-rc1/test/urltest.lua
  inflating: luasocket-3.0-rc1/test/utestclnt.lua
  inflating: luasocket-3.0-rc1/test/utestsrvr.lua
  inflating: luasocket-3.0-rc1/win32.cmd
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/mime.c -o src/mime.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -bundle -undefined dynamic_lookup -all_load -o mime/core.so -L/usr/local/lib src/mime.o
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/buffer.c -o src/buffer.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/auxiliar.c -o src/auxiliar.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/options.c -o src/options.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/timeout.c -o src/timeout.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/io.c -o src/io.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/usocket.c -o src/usocket.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/unix.c -o src/unix.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -bundle -undefined dynamic_lookup -all_load -o socket/unix.so -L/usr/local/lib src/buffer.o src/auxiliar.o src/options.o src/timeout.o src/io.o src/usocket.o src/unix.o
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/luasocket.c -o src/luasocket.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/timeout.c -o src/timeout.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/buffer.c -o src/buffer.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/io.c -o src/io.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/auxiliar.c -o src/auxiliar.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/options.c -o src/options.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/inet.c -o src/inet.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/except.c -o src/except.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/select.c -o src/select.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/tcp.c -o src/tcp.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/udp.c -o src/udp.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/usocket.c -o src/usocket.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -bundle -undefined dynamic_lookup -all_load -o socket/core.so -L/usr/local/lib src/luasocket.o src/timeout.o src/buffer.o src/io.o src/auxiliar.o src/options.o src/inet.o src/except.o src/select.o src/tcp.o src/udp.o src/usocket.o
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/buffer.c -o src/buffer.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/auxiliar.c -o src/auxiliar.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/options.c -o src/options.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/timeout.c -o src/timeout.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/io.c -o src/io.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/usocket.c -o src/usocket.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -O2 -fPIC -I/usr/local/include -c src/serial.c -o src/serial.o -DLUA_COMPAT_APIINTCASTS -DLUASOCKET_DEBUG -DUNIX_HAS_SUN_LEN -DLUASOCKET_API=__attribute__((visibility("default"))) -DUNIX_API=__attribute__((visibility("default"))) -DMIME_API=__attribute__((visibility("default")))
env MACOSX_DEPLOYMENT_TARGET=10.8 gcc -bundle -undefined dynamic_lookup -all_load -o socket/serial.so -L/usr/local/lib src/buffer.o src/auxiliar.o src/options.o src/timeout.o src/io.o src/usocket.o src/serial.o
Updating manifest for /usr/local/lib/luarocks/rocks-5.2
luasocket 3.0rc1-2 is now built and installed in /usr/local (license: MIT)

[ye@Yes-MacBook-Pro raven-lua (master)]$ make test
Loaded testsuite with 12 tests in 3 testcases.

    ..........[ERROR]   Failed to send to Sentry:   connection refused      {"culprit":"error","timestamp":"2016-03-30T19:25:54","message":"tests\/test_exceptions.lua:28: bad","server_name":"undefined","level":"error","logger":"root","event_id":"5ad325c251004f2d8fb684c63844c357","platform":"lua","exception":[{"value":"tests\/test_exceptions.lua:28: bad","stacktrace":{"frames":[{"filename":"[C]","lineno":-1},{"filename":"stdin","lineno":11},{"filename":"\/usr\/local\/share\/lua\/5.2\/lunit.lua","lineno":540},{"filename":"\/usr\/local\/share\/lua\/5.2\/lunit.lua","lineno":522,"function":"runtest"},{"filename":"\/usr\/local\/share\/lua\/5.2\/lunit.lua","lineno":504,"function":"callit"},{"filename":"\/usr\/local\/share\/lua\/5.2\/lunit.lua","lineno":108,"function":"mypcall"},{"filename":"[C]","lineno":-1,"function":"xpcall"},{"filename":"tests\/test_exceptions.lua","lineno":28},{"filename":"[C]","lineno":-1,"function":"xpcall"},{"filename":"tests\/test_exceptions.lua","lineno":28},{"filename":"[C]","lineno":-1,"function":"error"}]}}]}
.[ERROR]    Failed to send to Sentry:   connection refused      {"culprit":"tests\/test_exceptions.lua:17","timestamp":"2016-03-30T19:25:54","message":"IF YOU ARE READING THIS IT IS CORRECT; THIS TEST SHOULD GENERATE AN ERROR.","server_name":"undefined","level":"error","logger":"root","event_id":"5b8279bfc3d64efb8c5cf3446cfaa291","platform":"lua"}
.

60 Assertions checked.

Testsuite finished (12 passed, 0 failed, 0 errors).

Follow https://github.com/cloudflare/raven-lua/blob/master/.travis.yml#L30 should get the tests running (that's how Travis runs it as well).

authors: dndx ye

repo: cloudflare/raven-lua


text:
Try to fix a rare issue with invalid labels in the modal

When user clicks on a label modal window shows invalid label, can't reproduce but there are reports of it, this commit tries to fix that

Not sure if this fixes the issue, but that's the only place I suspect so far.

I look over the code and don't think this will fix anything, will try to reproduce to find the real root cause

repo: cloudflare/unsee


text:
🐛 Bug Report — Runtime APIs: workerd asserts on GET/HEAD request with 'Content-Length: 0'

GET/HEAD requests that include a Content-Length: 0 header assert when running CF workers locally in miniflare (ran through wrangler 3.0.0). E.g. take any worker, and make a GET request to it with this header:
$ curl -H 'Content-Length: 0' http://localhost:8001/

Yields:
workerd/server/server.c++:2528: error: Uncaught exception: workerd/jsg/_virtual_includes/jsg/workerd/jsg/value.h:1343: failed: remote.jsg.TypeError: Request with a GET or HEAD method cannot have a body.
stack: /app/dashboard/node_modules/workerd/lib/downloaded-@cloudflare-workerd-linux-arm64-workerd@19e138c /app/dashboard/node_modules/workerd/lib/downloaded-@cloudflare-workerd-linux-arm64-workerd@19e1ff7 /app/dashboard/node_modules/workerd/lib/downloaded-@cloudflare-workerd-linux-arm64-workerd@18b4880 /app/dashboard/node_modules/workerd/lib/downloaded-@cloudflare-workerd-linux-arm64-workerd@18b4de4 /app/dashboard/node_modules/workerd/lib/downloaded-@cloudflare-workerd-linux-arm64-workerd@18b5c14 /app/dashboard/node_modules/workerd/lib/downloaded-@cloudflare-workerd-linux-arm64-workerd@18b6198 /app/dashboard/node_modules/workerd/lib/downloaded-@cloudflare-workerd-linux-arm64-workerd@1faf7b4 /app/dashboard/node_modules/workerd/lib/downloaded-@cloudflare-workerd-linux-arm64-workerd@1fb2284

Doing the same request against the CF workers playground is fine (omitted some headers for clarity here):
$ curl 'https://29cb9a0e78771a2831a65e4f7065da77.cloudflareworkers.com/' -H 'Content-Length: 0'
Hello world

My guess is this pointer should not be set when Content-Length: 0 is passed in (or there should be another check for headers here):
https://github.com/cloudflare/workerd/blob/d28b0e1241d443c3e474a8814c3e0d73672e462d/src/workerd/api/http.c%2B%2B#L854
Setting the Content-Length header on GET requests is f.e. used by Docker whenever it pulls manifests from Docker Hub (found this behavior when proxying these requests through a worker).

The error in question is thrown by the Request constructor (or fetch()) when called from JavaScript and given an initializer object which specifies method: "GET" and a non-null body. The system does not call this implicitly; it must be invoked from JavaScript.
@mrbbot does Miniflare inject an ingress worker that handles requests before passing them on to the user's worker? If so I think this may be a bug in that ingress worker.

For a little background here: The fetch() and Request API spec say that GET requests cannot have a body. But, the HTTP spec actually does allow GET requests to have a body, and people do use this. Specifying Content-Length or Transfer-Encoding headers in a GET request causes it to have a body (even if zero-size).
The Workers Runtime, as a compromise, permits bodied GET requests to proxy through, but does not allow a bodied GET to be constructed directly from JavaScript. This pass-through works even if you do new Request(newUrl, oldRequest) to rewrite the URL of the request -- in this case, theoretically, oldRequest is being used as the options object to the Request constructor, which "just works" because all the defined options that this structure can have correspond to same-named properties of Request. Theoretically, though, this should fail in the case of a bodied GET because it's specifying method: "GET" and non-null body. However, the runtime explicitly notices when you are using a full Request object as the second parameter and treats this specially, so that the bodied GET can pass through after all.
It looks like miniflare might be deconstructing a Request object somewhere into its component properties, and then constructing a new initializer dict from that. This defeats the special handling of Request objects used as an options object, so the bodied GET is not permitted through. Ideally miniflare's code should be adjusted to avoid decomposing the Request object in this way. Note that individual properties can be modified if needed by doing new Request(oldRequest, {...options...}) -- the options will update specific properties of the request while other properties are copied over from oldRequest.

Yep, invoking the Request constructor twice is the right solution here, as silly as it may appear.

Thanks for the quick response all, and great to see the quick patch upstream!
For anyone running into this before the next miniflare release (I see the patch hasn't landed in master yet): I've put a Node proxy in front of my local workers that stripped off the header to workaround this:
import http from 'http';

const PROXY_HOST = process.env.PROXY_HOST || 'localhost';
const PROXY_PORT = process.env.PROXY_PORT || '4502';
const PORT = process.env.PORT || '4501';

http.createServer((clientReq, clientRes) => {
    let strippedContentLength = false;
    if (clientReq.method === 'GET') {
        if (clientReq.headers['content-length']) {
            delete clientReq.headers['content-length'];
            strippedContentLength = true;
        }
    }

    if (strippedContentLength) {
        console.log('serving ' + clientReq.method + ' ' + clientReq.url + ' (stripped Content-Length header)');
    } else {
        console.log('serving ' + clientReq.method + ' ' + clientReq.url);
    }

    const options = {
        hostname: PROXY_HOST,
        port: Number(PROXY_PORT),
        path: clientReq.url,
        method: clientReq.method,
        headers: clientReq.headers
    };

    const proxy = http.request(options, (res) => {
        clientRes.writeHead(res.statusCode || 500, res.headers);
        res.pipe(clientRes, {
            end: true
        });
    });

    clientReq.pipe(proxy, {
        end: true
    });

    proxy.on('error', err => {
        console.log('error proxying ' + clientReq.method + ' ' + clientReq.url + ': ' + err);
        clientRes.writeHead(500, { 'Content-Type': 'text/plain' });
        clientRes.write('error proxying ' + clientReq.method + ' ' + clientReq.url + ': ' + err + '\n');
        clientRes.end();
    });
}).listen(Number(PORT), '0.0.0.0');

console.log(`Proxying 0.0.0.0:${PORT} -> ${PROXY_HOST}:${PROXY_PORT}`);

authors: janjongboom kentonv

repo: cloudflare/workerd


text:
Add Windows Server 2022 Desktop Packer templates

This commit adds a tools/devboxes/windows-2022 directory, which contains Packer templates and related scripts to aid in building a QEMU VM running a Windows Server 2022 Desktop guest OS, intended to help test workerd on Windows, when you do not have a Windows machine handy. At present, this has only been tested on a Linux host.
This was originally based on https://github.com/StefanScherer/packer-windows/blob/main/windows_2022.json, then heavily modified.
The build is split up into two separate Packer builds: an installation build, and a provisioning build which works on a copy-on-write image backed by the installation build's output. This is done so that working on the provisioning step doesn't require you to complete a full reinstallation of Windows first.

I see we now have the https://github.com/cloudflare/workerd-tools/ repo. I wonder if that's a better place for this.


text:
dont install wasm-pack for webpack type projects

fixes #745
if folks want to use wasm-pack-plugin or some other tool, they should install and manage the necessary dependencies to do so. wrangler should only vendor what we know we need for the default use cases.
also we claimed to fix this in the 1.7.0 changelog and didn't actually do it

Whoo! 🎉

@xtuc - didn't we make wasm-pack-plugin do the installation for you instead? I dont think that logic belongs in wrangler

As far as I can remember wasm-pack plugin used to do the installation before we introduced it in wrangler and I'm unsure why we needed to.

🤷

authors: EverlastingBugstopper ispivey xtuc

repo: cloudflare/wrangler


text:
🐛 BUG: A request to the Cloudflare API failed

``### What version of Wrangler are you using?
2.1.11
What operating system are you using?
Mac
Describe the Bug
I am going through https://developers.cloudflare.com/workers/wrangler/get-started/. When I tried to run npm start. It showed that:
✘ [ERROR] Error while creating remote dev session: ParseError: A request to the Cloudflare API (/accounts/xxxxx/workers/subdomain/edge-preview) failed.

      at throwFetchError
  (.../my-project/node_modules/wrangler/wrangler-dist/cli.js:143459:17)
      at fetchResult
  (.../my-project/node_modules/wrangler/wrangler-dist/cli.js:143428:5)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)
      at async createPreviewSession
  (.../my-project/node_modules/wrangler/wrangler-dist/cli.js:143694:28)
      at async start
  (.../my-project/node_modules/wrangler/wrangler-dist/cli.js:144345:9) {
    text: 'A request to the Cloudflare API
  (/accounts/xxxxx/workers/subdomain/edge-preview) failed.',
    notes: [ { text: 'workers.api.error.subdomain_required [code: 10063]' } ],
    location: undefined,
    kind: 'error',
    code: 10063
  }

Sorry, I found that it's because I didn't add a subdomain.


text:
Enable pprof block profiling (parameterized)

As per request: https://github.com/cloudfoundry-incubator/cf-debug-server/pull/2

Hi @milkotodorov,
Thank you for the pull request. We want to merge this, but we also think it would fit better as a handler endpoint so that the block profile rate can be set dynamically instead of just on startup.
Would you mind changing the PR to remove the flag option and add a handler before we merge it? We suggest the path /block-profile-rate with the rate being the body of the request (much like the log-level one).
Lastly, can you also squash the commits so we have a cleaner git history when we do merge it?
Thank you very much,
@luan & @adowns01, CF Diego Team

Hi @luan & @adowns01,
I've done the changes, however I saw that the dbgFlag is there so I left both - with flag and as a handler endpoint. Commits are squashed.
Regards,
Milko

Hi @milkotodorov,
Handler looks great, added a line comment to change the error reporting.
I still think the flag is not necessary here, I'd like to avoid having the debug server add too many command line flags, since it's embedded in other processes. The reason DebugFlag is there is because you absolutely need to have an address to start the debug server, whereas for the profile rate you can always change dynamically. Furthermore, I think that it's not the debug server responsibility to initialize that value, the process using the debug server can call the runtime.SetBlockProfileRate method before initializing the server to have the same effect.
How does that sound? Happy to merge as soon as you can remove the flag, and thanks again for the contribution.
Thanks,
@luan, CF Diego Team

Hi @luan,
no problem - I've made the changes.
Regards,
Milko

Thanks @milkotodorov -- Merged!

authors: luan milkotodorov

repo: cloudfoundry-incubator/cf-debug-server


text:
Can we please add pre-compiled bosh-init into releases?

I'm trying to do pipelining to ensure the bosh-init-redis, *-bosh, etc projects keep working for new version of bosh-init based on releases.
Creating ticket so @cppforlife can let me know when releases (rather than tags) are being uploaded so I can simplify my pipelines. Currently will trigger pipeline based on any git commit (afaik thats all git-resource can do)

We have two buckets that bosh-init binaries are published. See these two resources for the location: https://concourse-1739433260.us-east-1.elb.amazonaws.com/resources/release-bucket-linux and https://concourse-1739433260.us-east-1.elb.amazonaws.com/resources/release-bucket-darwin

authors: cppforlife drnic

repo: cloudfoundry/bosh-init


text:
WIP : Add retries for adding/removing VMs from nsgroups.

Description
Added retries for add and remove VMs from nsgroups.
Added corresponding unit tests.
Related PR and Issues
Fixes https://pivotal-spike.atlassian.net/browse/PKS-607
Impacted Areas in Application
List general components of the application that this PR will affect:
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Test Configuration:

Environment Variables for Integration test:
Hardware Requirements in ESXi:
Toolchain:
SDK:

Checklist:

[ ] My code follows the standard ruby style guide
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

BOSH retyable is a complete code framework and will help you a write a
maintainable solution for future. If you need to add retries on more
failures, it will be easier and cleaner to do with it.
On Thu, Apr 2, 2020, 12:05 PM SanikaGawhane notifications@github.com
wrote:

@SanikaGawhane commented on this pull request.
In src/vsphere_cpi/lib/cloud/vsphere/nsxt_provider.rb
https://github.com/cloudfoundry/bosh-vsphere-cpi-release/pull/260#discussion_r402546071
:

   begin

     grouping_obj_svc.add_or_remove_ns_group_expression(

       nsgroup.id,

       *to_simple_expressions(lports),

       'ADD_MEMBERS'

     )

   rescue NSXT::ApiCallError => e

     retry if e.code == 409 || e.code == 412 #Conflict or PreconditionFailed

     raise e

   end

Would adding a sleep(certain duration) after rescuing the error and
before retrying work?
Does using BOSH retryable give us some advantage over this?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/cloudfoundry/bosh-vsphere-cpi-release/pull/260#discussion_r402546071,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABRV6KVS7XH3F6C3CFQXXHTRKTOXFANCNFSM4LVLHFHQ
.

authors: EleanorRigby SanikaGawhane

repo: cloudfoundry/bosh-vsphere-cpi-release


text:
Feature request: target bosh deployment by name

Currently I can do bosh download manifest foo /tmp/foo.yml && bosh deployment /tmp/foo.yml to target a deployment (to ssh in, for instance). It'd be much nicer if I could just bosh deployment foo, or bosh deployment --name foo.

Thanks for feedback! This is a duplicate of #1312 so I'll close and link this, but feel free to add any additional thoughts on that issue.

repo: cloudfoundry/bosh


text:
Feature request: bosh should read AWS creds from env. variables

When uploading a final release or blobs, BOSH should be able to read final.yml to find out blobstore information and for credentials, if private.yml is missing or doesn't contain credentials, it should use standard AWS way of providing credentials (supported by many AWS libraries) - via environment variables:
AWS_SECRET_ACCESS_KEY and AWS_ACCESS_KEY_ID
I was a bit surprised that the library bosh cli uses doesn't already support that...
bosh cli version BOSH 1.3262.0

https://github.com/cloudfoundry/bosh/pull/1402 will fix this.

Closing - the new golang bosh CLI supports this behavior by configuring credentials_source as env_or_profile.

authors: combor dpb587-pivotal mtekel


text:
Storing bound service VCAP env. vars in manifest.yml?

As far as I see, there is no way to specify env. vars for a bound service in a manifest.
Right now, all you can do is list the service name.
The docs say to use VCAP_Services, but there is no YAML equivalent (maybe there shouldn't be, could be by design and there's a way to reference this).
Hopefully that makes sense. I can provide further examples if need be.

Hi @kevinSuttle,
Can you help us understand your question? From what we can tell, you are asking that in an application manifest you can specify environment variables that will contain credentials of the services specified?
If so, this feature is not currently supported in CloudFoundry. Currently we use VCAP_SERVICES as a generic location for service information. It allows us to prevent environment variable pollution and provides a consistent pattern for apps to access service credentials. Therefore I do not believe there is a plan to change this currently.
Thanks,
@jfmyers9 && @zaksoup, CF Runtime Team

Thanks @jfmyers9. That makes sense. I was referencing this: http://12factor.net/config, and was wondering how a team would share VCAP_Services + environment variables, in both their local environment and their PAAS. I guess that just happens on a per-app basis in the space/org by default?

Hi @kevinSuttle,
Cloud Foundry has no notion of sharing service information in a manifest for a couple of reasons. The manifest serves as a request to Cloud Foundry of the state you would like your app to be in with information specific to Cloud Foundry. A service is any 3rd party add-on and so some deployments might share the same service while others will not. This makes it impossible to add add service specific details in the manifest.
After starting your application, you can retrieve the VCAP_SERVICES from cf env APP_NAME.
Hope this helps,
@jfmyers9 && @DanLavine, The Runtime Team

authors: DanLavine jfmyers9 kevinSuttle


text:
add organization and space guids to cert OUs

[#154533193]
Signed-off-by: Nima Kaviani nkavian@us.ibm.com
The PR comes from Diego to add org-guid and space-guid to organizational units in the instance identity certs. The story number is included above.

[ x] I have reviewed the contributing guide

[ x] I have viewed, signed, and submitted the Contributor License Agreement

[ x] I have made this pull request to the master branch

[x ] I have run all the unit tests using bundle exec rake

did not run CATs but we are confident the change wouldn't affect cats.

LGTM, tests passed

authors: ericpromislow nimakaviani


text:
Add Maria Shaldybin as Networking approver

I'd like to be added as an approver in the Diego working group.
@ameowlia would you be willing to nominate me?
Submitted substantial PRs:

https://github.com/cloudfoundry/routing-release/pull/275
https://github.com/cloudfoundry/silk-release/pull/61
https://github.com/cloudfoundry/silk-release/pull/54
https://github.com/cloudfoundry/silk-release/pull/53
https://github.com/cloudfoundry/cf-networking-release/pull/123
https://github.com/cloudfoundry/cf-networking-release/pull/117
https://github.com/cloudfoundry/cf-networking-release/pull/113
https://github.com/cloudfoundry/silk-release/pull/40
https://github.com/cloudfoundry/envoy-nginx-release/pull/4
https://github.com/cloudfoundry/haproxy-boshrelease/pull/285

Involved in technical discussions:

Dynamic ASGs
C2C over TLS

Authored Cloud Foundry blog post: Securing Container-to-Container Networking with TLS

👍 I approve Maria's nomination.
Besides the things she listed she was also one of the two architects behind the dynamic ASG feature and she was the sole architect for TLS for c2c. Both of these large features spanned  cf-networking, silk, and diego.

authors: ameowlia mariash

repo: cloudfoundry/community


text:
Move Anthony Dahanne to Buildpacks and Java tools approver

App Runtime Interfaces: Buildpacks Java Contributions
PRs Commented on/Reviewed:
Issues that may be relevant:

2020-02-25T13:41:32Z: Add reactive certificate mapping support
2022-05-27T19:45:01Z: Spring Auto Reconfiguration & Spring Cloud Connectors Deprecation Notice
2023-04-11T18:45:21Z: Remove Java 19, add 20
2023-08-22T19:54:18Z: Fix #1027: properly detect new mysql connector
2023-08-23T00:57:54Z: Fix documentation
2023-09-11T20:19:28Z: Remove profile inclusion
2023-10-04T05:29:28Z: Java 21 Support
2023-10-30T23:20:59Z: Fix #1035: Add Java 21
2023-10-31T11:44:35Z: Migrate dynatrace integration to LD_PRELOAD and support FIPS mode
2023-11-03T02:42:44Z: Update to Jakarta EE / Java 17
2023-11-08T20:41:04Z: Add client certificate mapper ability to choose version
2023-11-13T22:36:17Z: Jakarta Support
2023-12-13T01:17:47Z: Add pom metadata and script for central
2024-01-03T22:41:13Z: Remove the DefaultMaxDirectMemory configuration
2024-01-11T13:07:55Z: Download sealights agent from 'customAgentUrl'
2024-03-11T12:46:48Z: NoSuchMethodError after upgrade of json-io
2024-03-12T11:51:34Z: Instana Agent Implementation
2024-03-19T01:44:31Z: add aws-mysql-jdbc*.jar

Code contributions:

2023-04-11T18:44:42Z: Remove Java 19, add 20
2023-04-12T13:16:04Z: Remove Java 19, add 20
2023-08-22T19:52:40Z: Fix #1027: properly detect new mysql connector
2023-08-23T00:57:28Z: Fix documentation
2023-08-23T00:59:57Z: Fix documentation
2023-08-28T14:42:34Z: Fix #1027: properly detect new mysql connector
2023-09-11T18:44:27Z: Remove profile inclusion
2023-09-11T20:24:56Z: Remove profile inclusion
2023-10-30T23:20:45Z: Fix #1035: Add Java 21
2023-11-08T22:35:23Z: Fix #1039: Make client certificate mapper support Spring Boot 3
2023-11-10T03:59:11Z: Fix #1039: Make client certificate mapper support Spring Boot 3
2023-11-29T16:39:37Z: Fix auto registered beans
2023-12-13T01:08:12Z: Add pom metadata and script for central
2023-12-14T02:41:39Z: Add pom metadata and script for central
2023-12-14T02:42:02Z: v2.0.1-SNAPSHOT Development
2023-12-14T16:05:51Z: Fix cloudfoundry#1039
2023-12-14T21:52:34Z: Fix cloudfoundry#1039
2023-12-18T20:20:43Z: v2.0.1-SNAPSHOT Development
2023-12-18T20:49:45Z: Revert Generics Addition to support Spring Boot 1.5 a little longer.
2023-12-18T21:09:05Z: Disable Java compiler warning for javax module
2023-12-19T01:20:01Z: v2.0.2-SNAPSHOT Development
2024-03-01T16:38:56Z: Test for improvement to condition to trigger java-cfenv framework
2024-03-01T16:46:34Z: Test for improvement to condition to trigger java-cfenv framework
2024-03-01T16:46:34Z: improvement to condition to trigger java-cfenv framework

App Runtime Interfaces: Java Tools Contributions
PRs Commented on/Reviewed:
Issues that may be relevant:

2023-07-07T13:08:16Z: Adopting  Security Groups API V3
2023-08-28T10:09:04Z: Mask off non-permission parts of unix file mode for resource match
2023-09-07T12:29:52Z: Adopting V3 API in routes
2023-10-03T20:51:13Z: Upgrade cf-java-client to support Spring Boot 3.1.x and 3.2.x with Java 17
2023-10-16T19:31:07Z: Update Environment Variables call is not able to delete Environment Variable v3
2023-12-21T20:51:41Z: Add Spotless plugin for style
2024-02-07T01:49:20Z: Fix integration tests
2024-02-07T06:57:04Z: Add readiness health check support in client
2024-02-08T17:02:00Z: Integration fixes
2024-02-09T15:04:57Z: Migrate integration tests to Junit 5 and selectively apply changes from  #1174 and #1185
2024-02-12T22:45:52Z: Pr 1192 rebase + reformat
2024-02-13T00:58:58Z: Pr 1194
2024-02-19T20:15:40Z: Enhance deploy
2024-02-21T00:18:32Z: Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.0
2024-02-28T04:15:52Z: Chunk matching resource requests with more than 5000 elements
2024-02-28T04:25:48Z: Fix #1222: Chunk request with large number of matched resources
2024-03-01T14:47:22Z: Disable flaky tests
2024-03-11T13:44:34Z: Update commons-compress
2024-04-15T18:23:48Z: v2/info call getting triggered internally while creating CloudFoundryClient and consuming v3 api's

Code contributions:

2023-12-21T20:32:20Z: Add spotless maven plugin
2023-12-21T20:49:35Z: Add spotless maven plugin
2023-12-21T21:08:02Z: Add spotless maven plugin
2023-12-21T21:08:03Z: Add spotless maven plugin
2024-02-06T17:28:26Z: Revert removal of Test import
2024-02-07T23:14:41Z: Junit4 to Junit4 Integration Tests migration
2024-02-08T16:07:04Z: Do not use ExtendWith
2024-02-08T16:17:35Z: Ignore .idea/ for real now
2024-02-08T16:48:43Z: Migration to Junit5
2024-02-08T16:49:24Z: Make integration tests chatty
2024-02-08T17:11:00Z: updates Conditonal CloudFoundry version based test to JUnit 5
2024-02-08T17:13:25Z: Do not use ExtendWith
2024-02-09T01:30:23Z: Add globally enabled
2024-02-09T14:57:38Z: Junit4 to Junit4 Integration Tests migration
2024-02-09T14:59:11Z: Modified getOrganizationId() & getSpaceId() as per V3
2024-02-09T14:59:11Z: adding security groups v3 create api
2024-02-09T14:59:12Z: Add globally enabled
2024-02-09T14:59:12Z: Ignore .idea/ for real now
2024-02-09T14:59:12Z: Make integration tests chatty
2024-02-09T14:59:12Z: Migration to Junit5
2024-02-09T16:06:18Z: Spotless apply; include integration-test
2024-02-12T22:21:44Z: mask off non-permission bits
2024-02-12T22:44:49Z: apply spotless formatting
2024-02-12T23:58:12Z: PR #1194: rebase and format with spotless
2024-02-13T15:29:30Z: PR #1194: rebase and format with spotless
2024-02-13T15:29:30Z: porting check route to v3 api
2024-02-19T20:12:03Z: Provide more info about deploy
2024-02-19T20:15:00Z: Revert to 5.11.0
2024-02-29T16:41:18Z: Fix #1222: Chunk request with large number of matched resources (#1223)
2024-03-01T15:08:47Z: Disable flaky tests (#1225)
2024-03-11T14:11:50Z: Update commons-compress (#1226)

The Buildpacks Java and Java Tools areas have less than 4 approvers each that is why one approve from each area will be enough to get this pr ready for merge.

I approve.

authors: anthonydahanne beyhan dmikusa


text:
Feature/add action syntax color

This PR depends on #8, Can only be reviewed once #8  is merged.
Reviewer - Notice the following:
Color is an action that accepts bgColor as an actionType, as opposed as just accepting the color as an argument, please make sure this is acceptable.

@patrick-tolosa , this includes two actions - color (which is not a real action) and resize.pad which looks ok

We'll revisit how 'Color' looks in the context of an argument to other actions.

repo: cloudinary/cloudinary-js-base


text:
Docker REST

[x]  Slides:
[x]  Handbook: https://github.com/cloudmesh/book/blob/master/section/container/docker-rest.md
[x]  Integrated into handbook:

There are no specific slides created for this section, this is a section of the handbook. Docker was discussed as a lecture and it is in
https://github.com/cloudmesh/book/blob/master/section/container/container.tex
The docker rest material can be found here and it is already in the handbook.
https://github.com/cloudmesh/book/blob/master/section/container/docker-rest.tex

authors: tbalson vibhatha

repo: cloudmesh/book


text:
fix: use a temporary file to host the new instance manager binary

Avoid using an hardcoded file name to store the newly uploaded
instance manager, preventing a possible race condition to happen.
Closes #659

This code is based on #655, and should be merged after it and rebased over the latest main.

/test

/ok-to-merge

/ready-to-test

/ready-to-test

authors: armru jsilvela leonardoce

repo: cloudnative-pg/cloudnative-pg