MQException: MQJE001: Completion Code '2', Reason '2033'

Hello,
These error codes appear when I start the client.
Could you help me understand why they are due?
2020-09-11 12:49:18.617 INFO - Successfully parsed configuration file!
2020-09-11 12:49:49.378 ERROR - Failed!
com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2033'.
at com.ibm.mq.MQDestination.getInt(MQDestination.java:707) ~[com.ibm.mq.allclient-<IP_ADDRESS>.jar:<IP_ADDRESS> - p912-L190308]
at com.ibm.mq.MQDestination.get(MQDestination.java:452) ~[com.ibm.mq.allclient-<IP_ADDRESS>.jar:<IP_ADDRESS> - p912-L190308]
at ru.cinimex.exporter.ExporterLauncher.getAllPublishedMetrics(ExporterLauncher.java:83) [mq_exporter.jar:?]
at ru.cinimex.exporter.ExporterLauncher.main(ExporterLauncher.java:49) [mq_exporter.jar:?]
2020-09-11 12:50:08.036 ERROR - Connection with queue manager was closed:
com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '6124'.
at com.ibm.mq.pcf.PCFMessageAgent.send(PCFMessageAgent.java:210) ~[com.ibm.mq.allclient-<IP_ADDRESS>.jar:<IP_ADDRESS> - p912-L190308]
at ru.cinimex.exporter.mq.MQPCFSubscriber.run(MQPCFSubscriber.java:142) [mq_exporter.jar:?]
Thank you very much and greetings

2020-09-11 12:50:08.181 ERROR - Error occurred during sending PCF command:
com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '6124'.
at com.ibm.mq.pcf.PCFMessageAgent.send(PCFMessageAgent.java:210) ~[com.ibm.mq.allclient-<IP_ADDRESS>.jar:<IP_ADDRESS> - p912-L190308]
at ru.cinimex.exporter.mq.MQPCFSubscriber.updateWithDirectPCFCommand(MQPCFSubscriber.java:104) [mq_exporter.jar:?]
at ru.cinimex.exporter.mq.MQPCFSubscriber.updateMetricsWithWildcards(MQPCFSubscriber.java:92) [mq_exporter.jar:?]
at ru.cinimex.exporter.mq.MQPCFSubscriber.run(MQPCFSubscriber.java:144) [mq_exporter.jar:?]
2020-09-11 12:50:20.135 INFO - Goodbye!

According to the IBM website, the problem could be related to:
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.tro.doc/q041040_.htm
Explanation
An MQGET call was issued, but there is no message on the queue satisfying the selection criteria specified in MQMD (the MsgId and CorrelId fields), and in MQGMO (the Options and MatchOptions fields). Either the MQGMO_WAIT option was not specified, or the time interval specified by the WaitInterval
This reason code can also be returned by the mqGetBag and mqExecute calls. mqGetBag is similar to MQGET. For the mqExecute call, the completion code can be either MQCC_WARNING or MQCC_FAILED:
If the completion code is MQCC_WARNING, some response messages were received during the specified wait interval, but not all. The response bag contains system-generated nested bags for the messages that were received.
If the completion code is MQCC_FAILED, no response messages were received during the specified wait interval.
Completion Code
MQCC_WARNING or MQCC_FAILED
Programmer response
If this is an expected condition, no corrective action is required.
If this is an unexpected condition, check that:
The message was put on the queue successfully.
The unit of work (if any) used for the MQPUT or MQPUT1 call was committed successfully.
The options controlling the selection criteria are specified correctly. All of the following can affect the eligibility of a message for return on the MQGET call:
MQGMO_LOGICAL_ORDER
MQGMO_ALL_MSGS_AVAILABLE
MQGMO_ALL_SEGMENTS_AVAILABLE
MQGMO_COMPLETE_MSG
MQMO_MATCH_MSG_ID
MQMO_MATCH_CORREL_ID
MQMO_MATCH_GROUP_ID
MQMO_MATCH_MSG_SEQ_NUMBER
MQMO_MATCH_OFFSET
Value of MsgId field in MQMD
Value of CorrelId field in MQMD
Consider waiting longer for the message.

Hello,
Will it be necessary to adjust any parameter in the development of mq_exporter?
Please your comments.
Thank you.

Hello,
It seems like connection to MQ was broken during exporter processing. We have an issue #137 about reconnecting to queue manager. At the moment the most correct way of using mq exporter is running it as MQ service. Check more info here,
Best regards.


Details of a model and list of playground environments

Following #842, it would be nice to have the list of the playground environment that have been created with the model, as a new tab in the details of the model.

Done


fix: dev: ISS-298: Fixed and improved debug logs

Printing file name in "Got Read" log.
Printing proper buffer name suffix/prefix/destination in "Trying to copy" log line.
Printing proper blockSize in BookKeeper.java:549 instead of startBlock
We are setting child thread-name as parent thread-name for readRequestChain and it's respective child threads. Instead, we can print parent-child thread-name for better debugging.

Codecov Report

Merging #306 into master will decrease coverage by 0.09%.
The diff coverage is 75%.

@@            Coverage Diff            @@
##           master     #306     +/-   ##
=========================================
- Coverage   50.36%   50.26%   -0.1%
=========================================
  Files          60       60
  Lines        3036     3036
  Branches      334      334
=========================================
- Hits         1529     1526      -3
- Misses       1418     1420      +2
- Partials       89       90      +1

Impacted Files
Coverage Δ

...java/com/qubole/rubix/core/CachingInputStream.java
0% <0%> (ø)
:arrow_up:

...om/qubole/rubix/core/NonLocalReadRequestChain.java
0% <0%> (ø)
:arrow_up:

...va/com/qubole/rubix/core/NonLocalRequestChain.java
0% <0%> (ø)
:arrow_up:

.../com/qubole/rubix/core/CachedReadRequestChain.java
81% <100%> (ø)
:arrow_up:

.../com/qubole/rubix/core/DirectReadRequestChain.java
67.85% <100%> (ø)
:arrow_up:

...ole/rubix/bookkeeper/FileDownloadRequestChain.java
84.53% <100%> (ø)
:arrow_up:

.../com/qubole/rubix/core/RemoteReadRequestChain.java
71.13% <100%> (ø)
:arrow_up:

...n/java/com/qubole/rubix/bookkeeper/BookKeeper.java
70.6% <100%> (ø)
:arrow_up:

...ole/rubix/bookkeeper/validation/FileValidator.java
68.96% <0%> (-6.9%)
:arrow_down:

...qubole/rubix/bookkeeper/CoordinatorBookKeeper.java
87.17% <0%> (-2.57%)
:arrow_down:

Through this, can you also take up the work to change logs which swallow exceptions and use the correct logger methods to log stack traces.

Through this, can you also take up the work to change logs which swallow exceptions and use the correct logger methods to log stack traces.

+1 for that.


Small indentation improvements in readme file

Removed closing php tags, because it is recommended to leave them out, so don't show them to your users.

@aloha Updated PR.


Normalize button

Hi, I’ve been following your project. And I have a little proposition: in the any file (style css) add rule:
.button-body{
min-width:  172px;
}
.column.is-2{
min-width: 25%;
}

Because of this condition, when the screen width is reduced, the buttons behave unnaturally. Send screens.
Site: https://hwtech.club/

For example:

Hey @issamansur ,
Thanks for bringing up this issue.
Unfortunately, this is the repo for links.hwtech.club
Here's the place for the right repo.
You can put this issue there and I'm sure we can help you out 😄
~CSK


ALB controller always restarting due to Controller health check failed

Hello all.
I have faced with issue once installed release version 1.0.0.
AWS ALB Ingress controller
  Release:    v1.0.0
  Build:      git-8115b25
  Repository: https://github.com/kubernetes-sigs/aws-alb-ingress-controller
-------------------------------------------------------------------------------

W1119 16:24:00.773769       1 config.go:46] Environment variable configuration is deprecated, switch to the --aws-region flag.
W1119 16:24:00.774023       1 client_config.go:552] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I1119 16:24:00.828036       1 :0] kubebuilder/controller "level"=0 "msg"="Starting EventSource"  "Controller"="alb-ingress-controller" "Source"={"Type":{"metadata":{"creationTimestamp":null},"spec":{},"status":{"loadBalancer":{}}}}
I1119 16:24:00.828264       1 :0] kubebuilder/controller "level"=0 "msg"="Starting EventSource"  "Controller"="alb-ingress-controller" "Source"={"Type":{"metadata":{"creationTimestamp":null},"spec":{},"status":{"loadBalancer":{}}}}
I1119 16:24:00.828405       1 :0] kubebuilder/controller "level"=0 "msg"="Starting EventSource"  "Controller"="alb-ingress-controller" "Source"={"Type":{"metadata":{"creationTimestamp":null}}}
I1119 16:24:00.828627       1 :0] kubebuilder/controller "level"=0 "msg"="Starting EventSource"  "Controller"="alb-ingress-controller" "Source"={"Type":{"metadata":{"creationTimestamp":null},"spec":{},"status":{"daemonEndpoints":{"kubeletEndpoint":{"Port":0}},"nodeInfo":{"machineID":"","systemUUID":"","bootID":"","kernelVersion":"","osImage":"","containerRuntimeVersion":"","kubeletVersion":"","kubeProxyVersion":"","operatingSystem":"","architecture":""}}}}
I1119 16:24:00.828800       1 leaderelection.go:185] attempting to acquire leader lease  nginx/ingress-controller-leader-alb...
I1119 16:24:19.049773       1 leaderelection.go:194] successfully acquired lease nginx/ingress-controller-leader-alb
I1119 16:24:19.150170       1 :0] kubebuilder/controller "level"=0 "msg"="Starting Controller"  "Controller"="alb-ingress-controller"
I1119 16:24:19.250323       1 :0] kubebuilder/controller "level"=0 "msg"="Starting workers"  "Controller"="alb-ingress-controller" "WorkerCount"=1
E1119 16:24:39.439349       1 healthcheck.go:38] Controller health check failed: [ec2.DescribeTagsWithContext]: InvalidParameterValue: Value ( 1 ) for parameter maxResults is invalid. Expecting a value greater than 5.
	status code: 400, request id: 0e1beb6e-f482-4e52-9364-a05257b1d611
E1119 16:24:49.447230       1 healthcheck.go:38] Controller health check failed: [ec2.DescribeTagsWithContext]: InvalidParameterValue: Value ( 1 ) for parameter maxResults is invalid. Expecting a value greater than 5.```

@eserden I have the same issue with v1.0.0 I guess this should be fixed

will fix this asap, it's an degrade from 1.0-beta.7 by https://github.com/kubernetes-sigs/aws-alb-ingress-controller/commit/f7382830d1e212e5e7f3e9f00e59a6ea170adec0.
I didn't capture this without configure the health probe

A temp mitigation can be remove the liveness/readiness probe from controller yaml.
I'll send an PR to fix this shortly and re-release v1.0.0 to contain it

Hi, I just re-tagged the v1.0.0 tag and have rebuilt the v1.0.0 image by travis.
Sorry for the inconvenience caused. I'll add health checks into my integration test suit.


Heat capacity

Made a correction to the formula for heat capacity. Also removed the two test .traj-files since the ones providided in the equilibrium-condition branch are of superior quality.

Yes this should merge to develop.


sqlite: suggest XDG_CACHE_HOME instead of XDG_DATA_HOME

Since it is a history file, i would consider it non-essential.

After thinking about it a little, I think this makes sense. When I ported the arch wiki page, I set it to DATA_HOME for most history files, but the only files for which this actually makes sense are probably the shell history files.


Verify tests

Cover Verify with unit tests

Codecov Report

:exclamation: No coverage uploaded for pull request head (verify-tests@a118f27).

Continue to review full report at Codecov.

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

@armiol PTAL.

@dmytro-grankin please remember, you'll also have to Update branch before merging.

@armiol PTAL.

@dmytro-grankin LGTM. Now you'll have to use Update branch, then wait until the checks pass.
If the checks are passed, you'll need to merge this PR and delete the branch.


blank project

nothing ，but a blank project

@wwwang89 you need run pod install.

@wwwang89 I haven't push local commits to github. And I just wrote about check whether IMAP account is valid.


Misleading "(percentage point)" labels on two "Baseline Growth Assumptions" input boxes

The documentation info (via the i pop-up box) is inconsistent with the "(percentage point)" labels.
Best strategy would seem to be dropping the "(percentage points)" text in both labels and let the pop-up documentation explain to the TaxBrain user what units to enter.
@MattHJensen @PeterDSteinberg @brittainhard @talumbau

@martinholmer, could you describe the inconsistency?
The first parameter allows the user to supply a percentage point deviation from the existing CBO growth rate. i.e., the user adjusts a percent growth rate by a percentage point factor.
The second parameter allows the user to supply a growth rate that replaces the CBO growth rate. i.e., the user replaces a percent growth rate with a percent growth rate.
As far as I can tell, we are using the "percentage point" and "percent" terms properly.

@MattHJensen said:

The first parameter allows the user to supply a percentage point deviation from the existing CBO growth rate. i.e., the user adjusts a percent growth rate by a percentage point factor.

No, that is not what is happening in the source code.  The real GDP growth rates in Tax-Calculator are expressed in decimal, not percentage, terms.  So, while CBO says real GDP grows at 2.1 percent in a given year, Tax-Calculator says real GDP grows at 0.021 in that year.  Any user putting in 1.1 as the deviation --- thinking it would increase 2.1 to 3.2 percent --- would be shocked to see massive increases in the blown-up variables (because each blowup factor would have 1.1 added to its value, which is typically just a little bit larger than one).
Tax-Calculator pull request 1160 attempts to clarify things by revising the long_name and description of both of the Growth parameters.

Tax-Calculator pull request 1160, which attempts to clarify things by revising the long_name and description of both of the Growth parameters, has been merged into the Tax-Calculator master branch.

Thanks @martinholmer -- I understand the inconsistency now.

@MattHJensen,  What's the status of issue #455?

Beginning with release 0.7.7, the TaxBrain GUI does not contain growth-related parameters, so issue #455 has been resolved and is now being closed.


buildSnapPackage: use the default snapcraft target

Use the default snap target for snapcraft to create the snap (build is an
intermediate lifecycle step).
Signed-off-by: Sergio Schvezov<EMAIL_ADDRESS>

Hi @sergiusens, thanks for this. Does it address any specific issue or you just think it's best we run the default target instead of explicitly running build?

Sorry for taking so long to get back to you, this is just a default target thing.

No worries, thanks for this.


General issues

I'd like to see an old-school glossary
links to http://docs.wunderbarregistration.apiary.io should vanish because they are very confusing, but probably Swgger isn't there yet...

Glossary is going up


Update 02-listing-records.md

If using the static prefix you get the following error Cannot make non static method Filament\Resources\Pages\ListRecords::table() static in class
Making non static works

Thanks!

This is wrong, the docs clearly state table() method of the resource

Sorry, I did check but missed that final word apparently...


[Snyk] Security upgrade react-scripts from 4.0.2 to 5.0.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

package.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

551/1000  Why? Recently disclosed, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-JS-LOADERUTILS-3042992
Yes
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: react-scripts
    The new version differs by 76 commits.

221e511 Publish
6a3315b Update CONTRIBUTING.md
5614c87 Add support for Tailwind (#11717)
657739f chore(test): make all tests install with `npm ci` (#11723)
20edab4 fix(webpackDevServer): disable overlay for warnings (#11413)
69321b0 Remove cached lockfile (#11706)
3afbbc0 Update all dependencies (#11624)
f5467d5 feat(eslint-config-react-app): support ESLint 8.x (#11375)
e8319da [WIP] Fix integration test teardown / cleanup and missing yarn installation (#11686)
c7627ce Update webpack and dev server (#11646)
f85b064 The default port used by `serve` has changed (#11619)
544befe Update package.json (#11597)
9d0369b Fix ESLint Babel preset resolution (#11547)
d7b23c8 test(create-react-app): assert for exit code (#10973)
1465357 Prepare 5.0.0 alpha release
3880ba6 Remove dependency pinning (#11474)
8b9fbee Update CODEOWNERS
cacf590 Bump template dependency version (#11415)
5cedfe4 Bump browserslist from 4.14.2 to 4.16.5 (#11476)
50ea5ad allow CORS on webpack-dev-server (#11325)
63bba07 Upgrade jest and related packages from 26.6.0 to 27.1.0 (#11338)
960b21e Bump immer from 8.0.4 to 9.0.6 (#11364)
134cd3c Resolve dependency issues in v5 alpha (#11294)
b45ae3c Update CONTRIBUTING.md

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)

❌ Deploy Preview for affectionate-babbage-7132a7 failed.

Name
Link

🔨 Latest commit
a17736e85c51634cc763a1ad30f8c20ce780eb79

🔍 Latest deploy log
https://app.netlify.com/sites/affectionate-babbage-7132a7/deploys/6385022a46421d000b26ad63


Cards updated

🛠 Fixes Issue
Closes #89

👨💻 Changes proposed

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers
Inshorts and Quora Clone cards added

Inshorts Clone: Live preview only open in Mozilla firefox
Quora Clone: There is no live preview till now, Contributor will send the link in 1-2 days so I will update the link in the next PR
Changed a little bit CSS in .card-details so the description will fit easily

📷 Screenshots

Changed the levels in an issue as I said before there are so many PR in a single issue add the same label here so it's easy to calculate scores @Rayman-Sodhi


[AEM 6.4 + SP2] - Jackson Dependency Issue

AEM version: AEM 6.4.2
The Core bundle relies on a dependency on com.fasterxm.jackson.* version 2.9.7.
However, on AEM 6.4 + SP2 the dependency included is 2.8.4. This causes the bundle to fail to start:
com.fasterxml.jackson.annotation,version=[2.9,3) -- Cannot be resolved

I understand there is a security issue with version 2.8.4, perhaps the latest version of the bundle can be embedded in the project? Or maybe in AEM 6.4 + SP3 this dependency can be updated?

Thanks Gordon for your feedback.
Unfortunately com.fasterxm.jackson 2.8.4 has a security vulnerability, see http://www.cvedetails.com/vulnerability-list.php?vendor_id=15866&product_id=42991&version_id=237509&page=1&hasexp=0&opdos=0&opec=0&opov=0&opcsrf=0&opgpriv=0&opsqli=0&opxss=0&opdirt=0&opmemc=0&ophttprs=0&opbyp=0&opfileinc=0&opginf=0&cvssscoremin=0&cvssscoremax=0&year=0&month=0&cweid=0&order=1&trc=3&sha=1e493f7b77ddee795faddfb91c709c2c5272cb4c. This should be addressed in AEM 6.4 latest SP, I will check for the status and investigate either in documentation or embedding the dependency.

Decision has been taken: com.fasterxml.jackson dependencies with match the 6.4 dependencies from SP3 and therefore set back to 2.8.4.
We will push for an update.


Allow library functions to provide their own documention

Pull Request Test Coverage Report for Build 597512048

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 79.528%

Totals

Change from base Build 595247179:
0.0%

Covered Lines:
610

Relevant Lines:
761

💛  - Coveralls


Need help , i am trying to setup Angular 5 installation error  "npm install -g<EMAIL_ADDRESS>npm ERR! code ENOLOCAL npm ERR! Could not install from when i run npm install<EMAIL_ADDRESS><EMAIL_ADDRESS>as it does not contain a package.json file.

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request

Area
- [ ] devkit
- [ ] schematics

Versions

Repro steps

The log given by the failure

Desired functionality

Mention any other details that might be useful

Looks like you really want to npm install -g<EMAIL_ADDRESS>(notice the @ on @angular).

@hansl Yeah got it thanks.. And now i had this issue    after runing it , it installed but when i check the ng -v i see these error

@hansl  Thank you its working now, but i have other issue when i run ng serve


Question about expandable items sample

Hey thanks for the awesome effort you've put into this lib, looks very solid.
I'm just trying it out for the first time and am following the ExpandableSampleActivity. When an item expands, the RecyclerView expands and everything looks great.
The issue I'm running into is when I collapse that item, the bottom items get quickly clipped by the bounds of the RecyclerView. My RecyclerView is wrap_content so I'm guessing when the item is tapped, the view bounds are recalculated for the post-animation so the bottom items are clipped before the animation finishes. Is there a simple solution to fix this or am I missing something? Thanks again!
Edit: additional question: is there any way to get notified when items expand or collapse? If we set an OnClickListener and modify the parent view when it expands (like flipping the arrow) the arrow will stay flipped if we are calling withOnlyOneExpanedItem(true) since that will auto collapse the view without the OnClickListener being involved (sorry for the wordiness)

Hi. Thank you.
For the first issue, I have no idea as this is something handled by the RecyclerView and LayoutManager and not the adapter. So you may have to ask this somewhere like StackOverflow (expanding / collapsing is basically adding and removing items, so you might can ask it in a more general way)
Your second question. You are right, right now there is no solution that you can also get the OnClick event from the ExpandableItem as this is internally managed of the item. I made this decision as in general people will just want the single functionality from this item. I really should add the possibility to add an additional OnItemClickListener on it.
https://github.com/mikepenz/FastAdapter/blob/develop/app/src/main/java/com/mikepenz/fastadapter/app/items/ExpandableItem.java#L89
As an additional note. The general listener won't fire as we consume the click event here:
https://github.com/mikepenz/FastAdapter/blob/develop/app/src/main/java/com/mikepenz/fastadapter/app/items/ExpandableItem.java#L98

Will be in the next version


Annotation-based configuration

The option to use comments to ignore lines/specific rules doesn't seem to be working when running from the command line.
I'm running against the following code:
<cfcomponent displayname="test" output="false" hint="test">

	<cffunction name="init" access="public" output="false" returntype="test">
        <cfscript>
		var testa = ''; //cflint ignore:line
		return this;
	</cfscript>
    </cffunction>

</cfcomponent>

testa is never ignored. I have tried multiple variations.
Environment
Version: 1.5.0 (also tested 1.4.1)
Windows 10
java -version
java version "1.8.0_291"
Java(TM) SE Runtime Environment (build 1.8.0_291-b10)
Java HotSpot(TM) 64-Bit Server VM (build 25.291-b10, mixed mode)

Since you are within a tag context, try the tag-style comment <!--- --->

Ah yes, wasn't the best example. However I used this and still the same
<cfcomponent displayname="test" output="false" hint="test">

    <cffunction name="init" access="public" output="false" returntype="test">
        <cfset var testA = '' /> <!--- @CFLintIgnore line --->
        <cfreturn>
    </cffunction>

</cfcomponent>

Used combinations of @CFLintIgnore and just cflint. Thanks for the quick reply though.

I write mostly in CFScript and have found that the annotations do not work at all and the rules themselves have a lot of false positives.
/*
    @CFLintIgnore MISSING_SEMI,AVOID_USING_CREATEOBJECT,UNUSED_LOCAL_VARIABLE
*/

Yeah, it seems the same with me. The tag comment only works for the whole file as long as it's before a component/function, doesn't support individual lines.
The cfscript comments support seems like it supports some annotations and not others. For example with this mixed snippet:
Works
<cfcomponent displayname="test" output="false" hint="test">
	<cffunction name="init" access="public" output="false" returntype="test">
        <cfscript>
            testB = ''; // cflint ignore:line
        </cfscript>
        <cfreturn />
    </cffunction>
</cfcomponent>

Doesn't work
<cfcomponent displayname="test" output="false" hint="test">
	<cffunction name="init" access="public" output="false" returntype="test">
        <cfscript>
            var testB = ''; // cflint ignore:line
        </cfscript>
        <cfreturn />
    </cffunction>
</cfcomponent>

Note the addition of the var.
Strange one.

I can confirm that (tag-based) annotations have to be the first thing to put in a file, before <cfcomponent ...> for them to work on the whole file.

Ok, I'm not crazy, I can't get the annotations to work for me,
I tried all the variations... doesn't seem to work.
I'm in all script, in queryExecute, I tried almost every syntax, and nothing.
I'm running with the commandbox cflint command.


Chunk GC + Improvements to storing Chunks

This PR includes a configurable Chunk GC as well as some improvements to the memory structure of the LevelChunkManager.

Why is chunk GC needed?
Can't we just reference count and free by hand?

@Techcable Reference counting is very issue-prone.


[FEATURE] Consider agent-based node join

Is your feature request related to a problem? Please describe.
Installing on various hardware in remote datacenters can take hours due to limited resources in the region or a higher cost to add resources close to target bare metal machines. Please remember that much of this hardware and underlying network is unmanaged or requires remote hands, which is very expensive. This would work on VMs too, of course.
Describe the solution you'd like
Create agent-based joining where a supported OS is installed on bare metal and the then installed agent is customized via cli or SSH to connect to admin designated Rancher or master node.
Possible Benefits:

OS and underlying hardware would be configured by standardized methods and workflows
OS ISO installs take minutes, where Harvester ISO is taking hours in some cases (Even with ISOs in the same DC)
Networking is confirmed at time of OS install in using standard methods and tools, allowing sysadmin types to validate public and private networks at this stage instead of adding Harvester to the calculus (On Slack, this seems to be a very common area of failure/confusion and therefore requires increased support that will/is likely a limit to adoption)
Troubleshooting underlying issues before Harvester is added increases ownership of issues by the individuals doing the work and lowers issues attributed to Harvester

Describe alternatives you've considered

Current documented options for install are limited in some datacenter scenarios.
Adding more interactive scripts to install and validate underlying configurations and test connectivity, including the cluster token, before the full install completes.

Additional context
Because we rent commodity hardware from unrelated datacenters, usually when deep price cuts are available, we do not have standardized infrastructure. We can always count on spine and leaf switches, but networking/connectivity issues are hard for us to troubleshoot with Harvester. Asking the DC to work with us on determining why our servers work when any other OS is installed, but not when we install Harvester is not possible for obvious reasons. It is for this reason that I believe an agent-based option would simplify matters and increase adoption rates. I don't know whether this is or would become a common use case. I do see a pulling back from lock-in with the usual hyperscale providers and a great desire from me and my clients to avoid their high prices for large projects.
I genuinely appreciate how committed the Suse team has been in delivering a fantastic product. I believe it has a great future. Unfortunately, I have spent MANY thousands of USD in various datacenters and manhours trying to get a consistent experience, in hopes of deploying dozens of clusters for long-term installs in this same manor. Yet, we have not been successful. I can chalk that up to a lack of understanding how to troubleshoot the issues. For now, I will table my company's interests in deploying Harvester and see if there are indicators that this will not be an issue for us in the future. Thank you for your time.

@axsms Sorry we haven't got time to look at this request yet. Is there any reason you've closed it? (besides it's taking a while...)

Hmm, provisioning over L3 is going to be a much bigger effort. And Harvester is designed to managed the hardware from the OS layer, it won't be possible to switch out the OS.
However, we're working on an alternative way of installing Harvester via cloud-init enabled disk image (instead of ISO). See #2198

#2198 looks pretty good. With bare metal options at edge, we are hoping to avoid the need for L2 infrastructure until it can be provided through Harvester, since most of the vendors we work with provide a VLAN and public IP blocks for each node. They will often option a second NIC, but there's no L2 available until we build it.
At the moment, we set up a hypervisor with necessary VMs to mimic a typical on-prem environment — virtual firewall (pfSense), LAN, DHCP, DNS, and VPN. We are hoping we can avoid using a node for that purpose when we really only intend on using Harvester at each DC. This is how we envision HCI at the edge. Are we off course in our thinking? Would #2198 and #2346 get us to where we think we can go?

In our case (we're using Hetzner), it extremly complicated to do this because we have 1 NIC and their virtual networking solution does not allow us to have access to internet through the pfSense router..
It would be awesome if we can configure from Harvester 3 network types:

mgmt network (no internet access, used by nodes to communicate between them)
storage network (usually a switch with static ip addresses)
internet network (this interface will be used to have internet access in VMs)
internal VM network (this network will be used for VM-to-VM communication)

In our case, we will have something like this:

mgmt network (static ip on mgmt-br.4000 + VIP static ip)
storage network (static ip on mgmt-br.4001)
internet network (DHCP mgmt-br) <- this is a custom use-case for Hetzner case
internal VM network (static ip on mgmt-br.4002)

I've added more details here: https://github.com/harvester/harvester/issues/1762#issuecomment-1600656879


Use the require and remove cmp.Diff where possible

@bcl to answer your previous question whether or not require.Equal prints the difference for more complex data structures:
I've modifed one of the scenarios in api_test.go  (which calls TestRoute) and the result is:
=== RUN   TestBasic
--- FAIL: TestBasic (0.01s)
    helpers.go:131:
        	Error Trace:	helpers.go:131
        	Error:      	Not equal:
        	            	expected: map[string]interface {}{"blueprints2":[]interface {}{}, "changes":[]interface {}{}, "errors":[]interface {}{map[string]interface {}{"id":"UnknownBlueprint", "msg":"foo: "}}}
        	            	actual  : map[string]interface {}{"blueprints":[]interface {}{}, "changes":[]interface {}{}, "errors":[]interface {}{map[string]interface {}{"id":"UnknownBlueprint", "msg":"foo: "}}}

        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1,3 +1,3 @@
        	            	 (map[string]interface {}) (len=3) {
        	            	- (string) (len=11) "blueprints2": ([]interface {}) {
        	            	+ (string) (len=10) "blueprints": ([]interface {}) {
        	            	  },
        	Test:       	TestBasic

I think that's good enough, right ?


Update scala to 2.12.0-RC1

Addresses #14

if you're able to publish for RC1, please add it to https://github.com/scala/make-release-notes/blob/2.12.x/projects-2.12.md

@SethTisue surely!


How to input the skeleton of the first frame

Thank you for your great job!
I tried to follow the preprocessing of the HumanML3D dataset for the first frame of the mesh data, but since the output of the motion process is the number of frames -1 of the input, I would like to ask you how to insert the first frame

Can you let me know which script were you running, and the error print you got?

Thank you for your help.
When I process the motion_representation.ipynb file in HumanML3D, the length of the input before executing the def process_file function is sequence, and the length of the output is sequence-1. Currently, I only have one pose, and I don't know how to execute this method correctly to complete data preprocessing.

To the best of my knowledge, this process doesn't support single-frame poses, since it involves velocity calculation. Please contact the humanml team in https://github.com/EricGuo5513/HumanML3D

Thank you for your reply. I have caused you a lot of trouble recently. Thank you very much for your help during this period.

Haha don't worry you are welcome:)


break up glamor (even more)

The core glamor package can be split up into even more, smaller, useful parts.
The first I would like to split out is the murmur hash implementation in hash.js. I'm not sure why this wasn't proposed by the styled-components crew, but they're using it in vendored form right now so publishing it as it's own package is useful.
The other part I would like to split out is sheet.js. This is mostly for testing purposes as it is a single, contained unit and it would seem that this file is the only reason we need to use Karma/cross-browser testing. It is also seemingly useful on it's own as a unified stylesheet implementation.
Here's the checklist for what I want to accomplish.

[ ] split out hash.js into glamor-hash

[ ] write basic test

[ ] #243 -- split out sheet.js into glamor-stylesheet and move the tests.

[ ] Ensure that all stylesheet functions are well-tested.
[ ] isolate Karma use to glamor-stylesheet and move the rest of the tests to Jest, which IMO will improve the DX of repeatedly running glamor's test suites (which I do fairly often at this point).

[ ] depend on inline-style-prefixer instead of vendoring it. (cc/ @threepointone do you have opinions on this specifically?)

I'm also happy to move these packages to typescript as I split them out. Not sure if @donaldpipowitch has made any progress on that transition yet. I plan to do the above checklist as separate PRs to be easily reviewable, etc. There should be no functionality changes to glamor as a result of this work.
cc/ @donaldpipowitch @otbe

I'm also happy to move these packages to typescript as I split them out. Not sure if @donaldpipowitch has made any progress on that transition yet.

Sadly not. Feel free to start with that. I hoped I'd find time to do that to learn more of Glamors core, but I couldn't find spare time :(
Changes sound reasonable! LGTM.

I'd recommend not doing this. Don't want to maintain apis for sheet/hash/prefixer, and we might  change those implementations/apis in the future.

@threepointone I hear you on the additional maintenance burden, but it seems like we have some core pieces of general CSS-in-JS infrastructure here. Changing the APIs in the future seems like a semver problem right? (or am I missing something).
The prefixer part was more to depend on either an npm package or have a build step that compiles the inline package with the desired browser settings instead of having it vendored as source code.

Any chances on at least allowing prefix options? I'm getting gnarly rule generation from using calc and flex together.

@souporserious you could whack out the plugins and add your own prefixer
import {plugins} from 'glamor'
plugins.clear()
closing this issue, nothing really actionable here, but will consider ideas for immediate future.

Interesting 🤔 didn't know I could do that. Just want to make sure I understand correct, would I just clear all plugins and then add my own plugin that did the prefixing?

Yes correct. You might want to include the fallbacks plugin, that's pretty useful, but feel free to use any prefixer, or any others you'd like.

That's great!!! Will do, thank you! 🙌


Fix illegal raise,

Raising a pain string object results in a TypError, you probably don't want this as it may crash the script.

@googlebot I signed it!
Email is<EMAIL_ADDRESS>

It looks like the email or Github account you used to sign the CLA is different to the one on the git commits, which is why CLA-bot is sad. Can you verify that you have the correct details on file with the CLA bot, and verify that the email addresses on your git commits match the CLA?

Closing this PR in favor of #2571 .
(We never resolved the CLA issue here, so I can't merge this version. But thanks for the PR!)


how to fix parse dbf garbled?

const str = cptable.utils.decode(936, buf);
I used cpexcel.full.js  ,other  issus ever fixed csv , then  I got a correct string  ,but  when  I use
const workbook = XLSX.read(str, { type: "string" });   this obj workbook   like  this  :

is parse failed ?

Can you share the file?  If you can't do it publicly, email<EMAIL_ADDRESS>

It makes no sense to try to decode the entire DBF.  To override the embedded DBF codepage, assuming buf is a Uint8Array:
var wb = XLSX.read(buf, {type: "array", codepage:936 });

To verify this is the fix:
> XLSX.read(buf, {type: "array"}).Sheets.Sheet1.B35076
{ v: 'Íõ½à', t: 's' }

> XLSX.read(buf, {type: "array", codepage:936}).Sheets.Sheet1.B35076
{ v: '王洁', t: 's' }


e2e tests for generating + building a web API

e2e tests for generation are working, building is pending the builder


Verify by key fails but verify by hashivault is success

Describe the bug
I'm configuring sign-check in k8s with kyverno but stopped by an issue when my sign didnt check properly.
When I started checking this behavior i found next:
root@srv:/home# cosign verify --key hashivault://cosign harbor.domain.local/test/tomcat@sha256:b74dd6880fb1cd194fe23f3d2bec0cd0e89e79b609302632eb666c09c9e77709 --insecure-ignore-tlog=true --insecure-ignore-sct=true
and got:
Verification for harbor.domain.local/test/tomcat@sha256:b74dd6880fb1cd194fe23f3d2bec0cd0e89e79b609302632eb666c09c9e77709 --
The following checks were performed on each of these signatures:

The cosign claims were validated
The signatures were verified against the specified public key

But if i do this:
root@srv:/home# cosign public-key --key hashivault://cosign > key.key
root@srv:/home# cosign verify --key key.key harbor.domain.local/test/tomcat@sha256:b74dd6880fb1cd194fe23f3d2bec0cd0e89e79b609302632eb666c09c9e77709 --insecure-ignore-tlog=true --insecure-ignore-sct=true
I got:
Error: no matching signatures: crypto/rsa: verification error
main.go:69: error during command execution: no matching signatures: crypto/rsa: verification error
When I looking logs in debug-mode i didnt find any clear error, last step - checking blob and answers are the same when checking by key and by vault.
To Reproduce

Create keys in vault
Sign image by vault
Get public-key from vault
Try to verify image by local public-key

Expected behavior
Veryfing image by key from vault and by local key is successfull
Console Output

Debug by local key:
root@srv:/home# cosign verify --key key.key harbor.domain.local/kb/test/tomcat@sha256:b74dd6880fb1cd194fe23f3d2bec0cd0e89e79b609302632eb666c09c9e77709 --insecure-ignore-tlog=true --insecure-ignore-sct=true -d
WARNING: Skipping tlog verification is an insecure practice that lacks of transparency and auditability verification for the signature.
2023/11/16 11:48:50 --> GET https://harbor.domain.local/v2/
2023/11/16 11:48:50 GET /v2/ HTTP/1.1
Host: harbor.domain.local
User-Agent: cosign/v2.1.1 (linux; amd64) go-containerregistry/v0.15.2
Accept-Encoding: gzip
2023/11/16 11:48:50 <-- 401 https://harbor.domain.local/v2/ (96.826479ms)
2023/11/16 11:48:50 HTTP/1.1 401 Unauthorized
Content-Length: 76
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Thu, 16 Nov 2023 08:48:50 GMT
Docker-Distribution-Api-Version: registry/2.0
Server: nginx
Set-Cookie: sid=d058ab4dadb8e1f794d971fcf0aec0f9; Path=/; HttpOnly
Www-Authenticate: Bearer realm="https://harbor.domain.local/service/token",service="harbor-registry"
X-Request-Id: 722e944b-6415-46cb-96f1-acdde8fad03f
{"errors":[{"code":"UNAUTHORIZED","message":"unauthorized: unauthorized"}]}
2023/11/16 11:48:50 --> GET https://harbor.domain.local/service/token?scope=repository%3Akb%2Ftest%2Ftomcat%3Apull&service=harbor-registry [body redacted: basic token response contains credentials]
2023/11/16 11:48:50 GET /service/token?scope=repository%3Akb%2Ftest%2Ftomcat%3Apull&service=harbor-registry HTTP/1.1
Host: harbor.domain.local
User-Agent: cosign/v2.1.1 (linux; amd64) go-containerregistry/v0.15.2
Authorization:
Accept-Encoding: gzip
2023/11/16 11:48:51 <-- 200 https://harbor.domain.local/service/token?scope=repository%3Akb%2Ftest%2Ftomcat%3Apull&service=harbor-registry (49.25939ms) [body redacted: basic token response contains credentials]
2023/11/16 11:48:51 HTTP/1.1 200 OK
Connection: keep-alive
Content-Security-Policy: frame-ancestors 'none'
Content-Type: application/json; charset=utf-8
Date: Thu, 16 Nov 2023 08:48:51 GMT
Server: nginx
Set-Cookie: sid=0adde6f2e3a48214a796a437a036be45; Path=/; Secure; HttpOnly
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Frame-Options: DENY
X-Request-Id: bfcce794-4a03-4209-90db-1246bf2ab6a6
2023/11/16 11:48:51 --> GET https://harbor.domain.local/v2/test/tomcat/referrers/sha256:b74dd6880fb1cd194fe23f3d2bec0cd0e89e79b609302632eb666c09c9e77709
2023/11/16 11:48:51 GET /v2/test/tomcat/referrers/sha256:b74dd6880fb1cd194fe23f3d2bec0cd0e89e79b609302632eb666c09c9e77709 HTTP/1.1
Host: harbor.domain.local
User-Agent: cosign/v2.1.1 (linux; amd64) go-containerregistry/v0.15.2
Accept: application/vnd.oci.image.index.v1+json
Authorization:
Accept-Encoding: gzip
2023/11/16 11:48:51 <-- 200 https://harbor.domain.local/v2/test/tomcat/referrers/sha256:b74dd6880fb1cd194fe23f3d2bec0cd0e89e79b609302632eb666c09c9e77709 (10.297905ms)
2023/11/16 11:48:51 HTTP/1.1 200 OK
Content-Length: 300
Connection: keep-alive
Content-Security-Policy: frame-ancestors 'none'
Content-Type: application/json; charset=utf-8
Date: Thu, 16 Nov 2023 08:48:51 GMT
Server: nginx
Set-Cookie: sid=8b112d1caa3e784b91f139ec298c0fd5; Path=/; HttpOnly
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Frame-Options: DENY
X-Request-Id: 20d2a502-4122-49ea-9186-ac1ccc5c2820
X-Total-Count: 1
{"schemaVersion":2,"mediaType":"application/vnd.oci.image.index.v1+json","manifests":[{"mediaType":"application/vnd.oci.image.manifest.v1+json","digest":"sha256:b45b2da7cc36031dc256469e621f56dece4fbf7e2bda3559920c83af35267d69","size":1641,"artifactType":"application/vnd.oci.image.config.v1+json"}]}
2023/11/16 11:48:51 --> GET https://harbor.domain.local/v2/test/tomcat/manifests/sha256-b74dd6880fb1cd194fe23f3d2bec0cd0e89e79b609302632eb666c09c9e77709.sig
2023/11/16 11:48:51 GET /v2/test/tomcat/manifests/sha256-b74dd6880fb1cd194fe23f3d2bec0cd0e89e79b609302632eb666c09c9e77709.sig HTTP/1.1
Host: harbor.domain.local
User-Agent: cosign/v2.1.1 (linux; amd64) go-containerregistry/v0.15.2
Accept: application/vnd.docker.distribution.manifest.v1+json,application/vnd.docker.distribution.manifest.v1+prettyjws,application/vnd.docker.distribution.manifest.v2+json,application/vnd.oci.image.manifest.v1+json,application/vnd.docker.distribution.manifest.list.v2+json,application/vnd.oci.image.index.v1+json
Authorization:
Accept-Encoding: gzip
2023/11/16 11:48:51 <-- 200 https://harbor.domain.local/v2/test/tomcat/manifests/sha256-b74dd6880fb1cd194fe23f3d2bec0cd0e89e79b609302632eb666c09c9e77709.sig (21.477203ms)
2023/11/16 11:48:51 HTTP/1.1 200 OK
Content-Length: 1146
Connection: keep-alive
Content-Security-Policy: frame-ancestors 'none'
Content-Type: application/vnd.oci.image.manifest.v1+json
Date: Thu, 16 Nov 2023 08:48:51 GMT
Docker-Content-Digest: sha256:b45b2da7cc36031dc256469e621f56dece4fbf7e2bda3559920c83af35267d69
Docker-Distribution-Api-Version: registry/2.0
Etag: "sha256:b45b2da7cc36031dc256469e621f56dece4fbf7e2bda3559920c83af35267d69"
Server: nginx
Set-Cookie: sid=55b666ead8189b5cf99e8d9348551ef8; Path=/; HttpOnly
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Frame-Options: DENY
X-Request-Id: 189325e5-5b21-4431-b6b7-c1881b485070
{"schemaVersion":2,"mediaType":"application/vnd.oci.image.manifest.v1+json","config":{"mediaType":"application/vnd.oci.image.config.v1+json","size":248,"digest":"sha256:8017b161b26b330beec138cc4bd529021c76c7e8d2bc360c52bd0e90bdad9461"},"layers":[{"mediaType":"application/vnd.dev.cosign.simplesigning.v1+json","size":247,"digest":"sha256:edc06179faadbe516edba2e5b91d37e992ca0cb19c1f79a2ee2862253d0ba7b3","annotations":{"dev.cosignproject.cosign/signature":"kC6ENoScap3Du8cfjs0pjxaRlbN6hDhjn0KlPQpwdnoLwSzluD7BJUwJdRh2VV9NzqT1SJ0TThGl50iIOXkqJWdFxNJP+cCPWC46ZX6zhSRemkSBAOqjELsRGWFNV5RMkPQaG+jtdV59h033cKIkhuZGOeCJa0WNF7uc7+eBdj63TrtwC1RtP0tcWSdeUvYhTZJXamyxKFGQub3B6vL4z5QL04c7Yy6DmlyFDZLhs1Fq4c7X+a2OOTSTjaDJJuMPxxFO7EvJ+hD7uIbEDUOzjb+KLfCaKT6zZxFfIgihDHzx79zA5ob6fMwquZNXWtsBapTEhZx4DDtuvkJYw0Xz6+tnQlZ7Im8THUaWqOwu6Yjgn0pFr7LRrF3Ffcz2c63hFHFPquzOTKj2A8G4EbEXA+Avvj5ERoomFFxQvB1w+pph1D0fsmXuVjkGTm0/zEkZH73tzjQ34dbi8uRtawJxXMZ2C8A0nZPIv6WpvV/P7lJjFd6vXerZVUD5lXLTXopEu/re5W1b+k8UAkYhIfh1GPBxzsIo2HKcgc3As37GqAVfXE9Jebu0GEAr8h2mCVjg11rsoA+d6tELnajhRKcaK8jmk0csu/9xVlfLOJTryhNKgDKKZ9j3WJ41YybrKR2r/gTfiz8EDgRAnS1J2e+MAPdOgNXWVf8Un6LE3C8lbk8="}}]}
2023/11/16 11:48:51 --> GET https://harbor.domain.local/v2/test/tomcat/blobs/sha256:edc06179faadbe516edba2e5b91d37e992ca0cb19c1f79a2ee2862253d0ba7b3 [body redacted: omitting binary blobs from logs]
2023/11/16 11:48:51 GET /v2/test/tomcat/blobs/sha256:edc06179faadbe516edba2e5b91d37e992ca0cb19c1f79a2ee2862253d0ba7b3 HTTP/1.1
Host: harbor.domain.local
User-Agent: cosign/v2.1.1 (linux; amd64) go-containerregistry/v0.15.2
Authorization:
Accept-Encoding: gzip
2023/11/16 11:48:51 <-- 200 https://harbor.domain.local/v2/test/tomcat/blobs/sha256:edc06179faadbe516edba2e5b91d37e992ca0cb19c1f79a2ee2862253d0ba7b3 (15.95357ms) [body redacted: omitting binary blobs from logs]
2023/11/16 11:48:51 HTTP/1.1 200 OK
Content-Length: 247
Accept-Ranges: bytes
Cache-Control: max-age=31536000
Connection: keep-alive
Content-Security-Policy: frame-ancestors 'none'
Content-Type: application/octet-stream
Date: Thu, 16 Nov 2023 08:48:51 GMT
Docker-Content-Digest: sha256:edc06179faadbe516edba2e5b91d37e992ca0cb19c1f79a2ee2862253d0ba7b3
Docker-Distribution-Api-Version: registry/2.0
Etag: "sha256:edc06179faadbe516edba2e5b91d37e992ca0cb19c1f79a2ee2862253d0ba7b3"
Server: nginx
Set-Cookie: sid=ef3169b2a54bfa33b97bd364e1b09113; Path=/; HttpOnly
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Frame-Options: DENY
X-Request-Id: a84c1888-51b8-40ed-8ee5-8193aeedc1d1
Error: no matching signatures: crypto/rsa: verification error
main.go:69: error during command execution: no matching signatures: crypto/rsa: verification error

Debug by hashivault:
root@srv:/home# cosign verify --key hashivault://cosign harbor.domain.local/kb/test/tomcat@sha256:b74dd6880fb1cd194fe23f3d2bec0cd0e89e79b609302632eb666c09c9e77709 --insecure-ignore-tlog=true --insecure-ignore-sct=true -d
WARNING: Skipping tlog verification is an insecure practice that lacks of transparency and auditability verification for the signature.
2023/11/16 11:57:11 --> GET https://harbor.domain.local/v2/
2023/11/16 11:57:11 GET /v2/ HTTP/1.1
Host: harbor.domain.local
User-Agent: cosign/v2.1.1 (linux; amd64) go-containerregistry/v0.15.2
Accept-Encoding: gzip
2023/11/16 11:57:11 <-- 401 https://harbor.domain.local/v2/ (67.551572ms)
2023/11/16 11:57:11 HTTP/1.1 401 Unauthorized
Content-Length: 76
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Thu, 16 Nov 2023 08:57:11 GMT
Docker-Distribution-Api-Version: registry/2.0
Server: nginx
Set-Cookie: sid=65118b27beaa2f1dcf71a3a98b079eed; Path=/; HttpOnly
Www-Authenticate: Bearer realm="https://harbor.domain.local/service/token",service="harbor-registry"
X-Request-Id: f23d8802-2292-4e21-b316-c28d6c98176a
{"errors":[{"code":"UNAUTHORIZED","message":"unauthorized: unauthorized"}]}
2023/11/16 11:57:11 --> GET https://harbor.domain.local/service/token?scope=repository%3Akb%2Ftest%2Ftomcat%3Apull&service=harbor-registry [body redacted: basic token response contains credentials]
2023/11/16 11:57:11 GET /service/token?scope=repository%3Akb%2Ftest%2Ftomcat%3Apull&service=harbor-registry HTTP/1.1
Host: harbor.domain.local
User-Agent: cosign/v2.1.1 (linux; amd64) go-containerregistry/v0.15.2
Authorization:
Accept-Encoding: gzip
2023/11/16 11:57:11 <-- 200 https://harbor.domain.local/service/token?scope=repository%3Akb%2Ftest%2Ftomcat%3Apull&service=harbor-registry (49.038027ms) [body redacted: basic token response contains credentials]
2023/11/16 11:57:11 HTTP/1.1 200 OK
Connection: keep-alive
Content-Security-Policy: frame-ancestors 'none'
Content-Type: application/json; charset=utf-8
Date: Thu, 16 Nov 2023 08:57:11 GMT
Server: nginx
Set-Cookie: sid=ca057432d212faa21cbc90d40900f459; Path=/; Secure; HttpOnly
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Frame-Options: DENY
X-Request-Id: 8ca1dd45-597e-45ed-b150-f4bbb25fa7de
2023/11/16 11:57:11 --> GET https://harbor.domain.local/v2/test/tomcat//referrers/sha256:b74dd6880fb1cd194fe23f3d2bec0cd0e89e79b609302632eb666c09c9e77709
2023/11/16 11:57:11 GET /v2/test/tomcat//referrers/sha256:b74dd6880fb1cd194fe23f3d2bec0cd0e89e79b609302632eb666c09c9e77709 HTTP/1.1
Host: harbor.domain.local
User-Agent: cosign/v2.1.1 (linux; amd64) go-containerregistry/v0.15.2
Accept: application/vnd.oci.image.index.v1+json
Authorization:
Accept-Encoding: gzip
2023/11/16 11:57:11 <-- 200 https://harbor.domain.local/v2/test/tomcat//referrers/sha256:b74dd6880fb1cd194fe23f3d2bec0cd0e89e79b609302632eb666c09c9e77709 (9.45321ms)
2023/11/16 11:57:11 HTTP/1.1 200 OK
Content-Length: 300
Connection: keep-alive
Content-Security-Policy: frame-ancestors 'none'
Content-Type: application/json; charset=utf-8
Date: Thu, 16 Nov 2023 08:57:11 GMT
Server: nginx
Set-Cookie: sid=ccd90f371c3b007236f79940a5bd11d1; Path=/; HttpOnly
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Frame-Options: DENY
X-Request-Id: 02ca0998-a6d4-4f45-8b6b-06958f37e87e
X-Total-Count: 1
{"schemaVersion":2,"mediaType":"application/vnd.oci.image.index.v1+json","manifests":[{"mediaType":"application/vnd.oci.image.manifest.v1+json","digest":"sha256:b45b2da7cc36031dc256469e621f56dece4fbf7e2bda3559920c83af35267d69","size":1641,"artifactType":"application/vnd.oci.image.config.v1+json"}]}
2023/11/16 11:57:11 --> GET https://harbor.domain.local/v2/test/tomcat//manifests/sha256-b74dd6880fb1cd194fe23f3d2bec0cd0e89e79b609302632eb666c09c9e77709.sig
2023/11/16 11:57:11 GET /v2/test/tomcat//manifests/sha256-b74dd6880fb1cd194fe23f3d2bec0cd0e89e79b609302632eb666c09c9e77709.sig HTTP/1.1
Host: harbor.domain.local
User-Agent: cosign/v2.1.1 (linux; amd64) go-containerregistry/v0.15.2
Accept: application/vnd.docker.distribution.manifest.v1+json,application/vnd.docker.distribution.manifest.v1+prettyjws,application/vnd.docker.distribution.manifest.v2+json,application/vnd.oci.image.manifest.v1+json,application/vnd.docker.distribution.manifest.list.v2+json,application/vnd.oci.image.index.v1+json
Authorization:
Accept-Encoding: gzip
2023/11/16 11:57:11 <-- 200 https://harbor.domain.local/v2/test/tomcat//manifests/sha256-b74dd6880fb1cd194fe23f3d2bec0cd0e89e79b609302632eb666c09c9e77709.sig (15.9058ms)
2023/11/16 11:57:11 HTTP/1.1 200 OK
Content-Length: 1146
Connection: keep-alive
Content-Security-Policy: frame-ancestors 'none'
Content-Type: application/vnd.oci.image.manifest.v1+json
Date: Thu, 16 Nov 2023 08:57:11 GMT
Docker-Content-Digest: sha256:b45b2da7cc36031dc256469e621f56dece4fbf7e2bda3559920c83af35267d69
Docker-Distribution-Api-Version: registry/2.0
Etag: "sha256:b45b2da7cc36031dc256469e621f56dece4fbf7e2bda3559920c83af35267d69"
Server: nginx
Set-Cookie: sid=a9a06fdfc8f5b2af12a30eadff590bc5; Path=/; HttpOnly
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Frame-Options: DENY
X-Request-Id: a94210a2-63d4-4b76-96a5-91b6b27f472e
{"schemaVersion":2,"mediaType":"application/vnd.oci.image.manifest.v1+json","config":{"mediaType":"application/vnd.oci.image.config.v1+json","size":248,"digest":"sha256:8017b161b26b330beec138cc4bd529021c76c7e8d2bc360c52bd0e90bdad9461"},"layers":[{"mediaType":"application/vnd.dev.cosign.simplesigning.v1+json","size":247,"digest":"sha256:edc06179faadbe516edba2e5b91d37e992ca0cb19c1f79a2ee2862253d0ba7b3","annotations":{"dev.cosignproject.cosign/signature":"kC6ENoScap3Du8cfjs0pjxaRlbN6hDhjn0KlPQpwdnoLwSzluD7BJUwJdRh2VV9NzqT1SJ0TThGl50iIOXkqJWdFxNJP+cCPWC46ZX6zhSRemkSBAOqjELsRGWFNV5RMkPQaG+jtdV59h033cKIkhuZGOeCJa0WNF7uc7+eBdj63TrtwC1RtP0tcWSdeUvYhTZJXamyxKFGQub3B6vL4z5QL04c7Yy6DmlyFDZLhs1Fq4c7X+a2OOTSTjaDJJuMPxxFO7EvJ+hD7uIbEDUOzjb+KLfCaKT6zZxFfIgihDHzx79zA5ob6fMwquZNXWtsBapTEhZx4DDtuvkJYw0Xz6+tnQlZ7Im8THUaWqOwu6Yjgn0pFr7LRrF3Ffcz2c63hFHFPquzOTKj2A8G4EbEXA+Avvj5ERoomFFxQvB1w+pph1D0fsmXuVjkGTm0/zEkZH73tzjQ34dbi8uRtawJxXMZ2C8A0nZPIv6WpvV/P7lJjFd6vXerZVUD5lXLTXopEu/re5W1b+k8UAkYhIfh1GPBxzsIo2HKcgc3As37GqAVfXE9Jebu0GEAr8h2mCVjg11rsoA+d6tELnajhRKcaK8jmk0csu/9xVlfLOJTryhNKgDKKZ9j3WJ41YybrKR2r/gTfiz8EDgRAnS1J2e+MAPdOgNXWVf8Un6LE3C8lbk8="}}]}
2023/11/16 11:57:11 --> GET https://harbor.domain.local/v2/test/tomcat//blobs/sha256:edc06179faadbe516edba2e5b91d37e992ca0cb19c1f79a2ee2862253d0ba7b3 [body redacted: omitting binary blobs from logs]
2023/11/16 11:57:11 GET /v2/test/tomcat//blobs/sha256:edc06179faadbe516edba2e5b91d37e992ca0cb19c1f79a2ee2862253d0ba7b3 HTTP/1.1
Host: harbor.domain.local
User-Agent: cosign/v2.1.1 (linux; amd64) go-containerregistry/v0.15.2
Authorization:
Accept-Encoding: gzip
2023/11/16 11:57:11 <-- 200 https://harbor.domain.local/v2/test/tomcat//blobs/sha256:edc06179faadbe516edba2e5b91d37e992ca0cb19c1f79a2ee2862253d0ba7b3 (17.899596ms) [body redacted: omitting binary blobs from logs]
2023/11/16 11:57:11 HTTP/1.1 200 OK
Content-Length: 247
Accept-Ranges: bytes
Cache-Control: max-age=31536000
Connection: keep-alive
Content-Security-Policy: frame-ancestors 'none'
Content-Type: application/octet-stream
Date: Thu, 16 Nov 2023 08:57:11 GMT
Docker-Content-Digest: sha256:edc06179faadbe516edba2e5b91d37e992ca0cb19c1f79a2ee2862253d0ba7b3
Docker-Distribution-Api-Version: registry/2.0
Etag: "sha256:edc06179faadbe516edba2e5b91d37e992ca0cb19c1f79a2ee2862253d0ba7b3"
Server: nginx
Set-Cookie: sid=7e24ddb15e7a7164be7aac51095933dc; Path=/; HttpOnly
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Frame-Options: DENY
X-Request-Id: 1a6b5989-4836-4e3d-b09b-6874de041d1b
Verification for harbor.domain.local/test/tomcat/@sha256:b74dd6880fb1cd194fe23f3d2bec0cd0e89e79b609302632eb666c09c9e77709 --
The following checks were performed on each of these signatures:

The cosign claims were validated
The signatures were verified against the specified public key

Additional context
Policy in vault:
path "transit/keys/cosign" {
capabilities = ["read"]
}
path "transit/hmac/cosign/*" {
capabilities = ["update"]
}
path "transit/sign/cosign/*" {
capabilities = ["update"]
}
path "transit/verify/cosign" {
capabilities = ["update"]
}

Move it to bug, please

Can you confirm the output of “cosign public-key” outputs a properly formatted key?

Can you confirm the output of “cosign public-key” outputs a properly formatted key?

Yeah, i can, will do it tomorrow.
Also i tried to get public-key with an option "--output-file" but there is no effect :C

I'm not very familiar with the public-key command, but my guess is there's an issue with the output and cosign's error message isn't clear.

I'm not very familiar with the public-key command, but my guess is there's an issue with the output and cosign's error message isn't clear.

Can you give me an advice how i can get public-key another way?

The first way you noted here would be what I would recommend.

The first way you noted here would be what I would recommend.

I like way with "--key hashivault://cosign" but i cant use it in kyverno.
My key looks like that:

-----BEGIN PUBLIC KEY-----
MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAy1XfHdS/xzpIVYD1sWy9
zWrsZg6P/+NIxGI/ncUTURo0CUw07JcZtsNduevtaZtaQLWwyJi6+Ad1Ru0xQ6LW
fTfVrAyAickZ+lrOh01PH9H6DQxAPy+PFEt+KKIHlckqrxeUJUVINGZg3ZDpqp0p
CoweK3d1de3m7+MtQAxBkV4HtL4xT7zs10v0oOFGrsMMVnZljWrjKA/SPqnTmnOG
zTFLVFOjjQvD2slzMaN/3gHgE40cdi/GVIPIQuPMqHJxRgvHZRyty8SwUu37fIbp
/7Rz/TVqFdxfBjhEYuhCiljhDOnpKY4jPr4cokw6T/oT7fI7ojcH3WeRCDMI+39w
lNBY7xczHkkfQmCzbCstdBMCc89KXbFf2xGYByHlx5S14IImQ7DoS1AFfts+iMwJ
SUVkIiYYOGvnTHNpzODTPgYF5SEYzksHNFVboCrwSquPIJSH4EwEIgv/S6iEZVOX
+yo2KHWgVjusb8By6Zs7MFqWcf8Oy2B9S9+5fQ80a/R4tTodnXbcwYp6cSkNwmE9
U3tw24tHfcGRiuDzt0hwXFssEvfAKzFGE1RZDKmOnkZTfIL+80Kri2PhVO8QSpJk
ThMb7/wHDiXYfkvDeed6eX64tmpp4h0hiDViItIbqk5XNh4v9ZNq+gXtvk3K2uoY
ueE2m/klQOm8gvan8xyXcq8CAwEAAQ==
-----END PUBLIC KEY-----

In the Internet i found one example i saw key like (2-3 strings, not 10+):
-----BEGIN PUBLIC KEY-----
exampleexampleexample
exampleexampleexample
-----END PUBLIC KEY-----
Mb trouble with it

Well, thanks for a help.

kms: hashivault://cosign
add variables VAULT_ADDR and VAULT_TOKEN to kyverno-admission-controller deployment
and It works.


Update integration tests for application management rest API

Updates the tests to check for newly introduced mappedLocalSubjectMandatory service provider configuration
Related PRs

https://github.com/wso2/carbon-identity-framework/pull/5110
https://github.com/wso2/identity-api-server/pull/521

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6730336627

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6730336627
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6734331772


Consider consolidating Account and Contract into an Address in soroban_auth::Identifier

As a follow up to #707 we should consider conlidating the Account and Contract variants of soroban_auth::Identifier into a single Address variant that contains a Address. It would make the type a little more opaque at the surface, although it will also increase the cost of using the type.
There is nothing urgent about this thought, and this issue is something for us to consider for a future iteration.

This should be resolved once soroban-auth is removed and auth-next takes its place. (cc. @dmkozh)

Closing this now in favor of Auth Next related issues.


Automatically bump package.json version

@semantic-release supports this with their plugin @semantic-release/git (see plugins)
It would have to be added in this order in the package.json plugin list for it to make a post-release commit that updates the version: https://github.com/Faire/mjml-react/blob/2e70ee23a8841489bfe5e2e4c378e765378b77f0/package.json#L114
The plugin was removed after the post-release commit failed, since we were having trouble letting a token/bot commit on the protected main branch, requiring PR reviews.
related?: https://github.com/semantic-release/git/issues/196#issuecomment-601310576

won't do


[stable/filebeat] updated filebeat to 6.4.1

What this PR does / why we need it:

updates filebeat to 6.4.1

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:

/assign @lachie83

/ok-to-test


feat(AIP-133): enforce required request fields

Enforces the following from AIP-133:
The request message must not contain any other required fields ...
except those described in this or another AIP.

Do we have a complementary Rule that checks that fields that should be required have REQUIRED field_behavior on them?

Do we have a complementary Rule that checks that fields that should be required have REQUIRED field_behavior on them?

Yep we're covered there:
https://linter.aip.dev/133/request-resource-behavior
https://linter.aip.dev/133/request-parent-behavior

Do we have a complementary Rule that checks that fields that should be required have REQUIRED field_behavior on them?

Yep we're covered there:
https://linter.aip.dev/133/request-resource-behavior https://linter.aip.dev/133/request-parent-behavior

Great!


Fix MSVC warning C26495: ZwQuerySystemInformation, m_MetaDataObjectValue uninitialized

Fixed Visual Studio 2019 Code Analysis warnings from both MetaDataObject and WindowsMemoryUsageObserver, saying:

warning C26495: Variable is uninitialized. Always initialize a member variable (type.6)

Note that MSVC/Code Analysis does not always produce this warning about uninitialized member variables, when it should. As I reported at developercommunity.visualstudio.com: False negative (missing) /analyze warning C26495: Variable is uninitialized. Always initialize a member variable (type.6). For a code example, see https://godbolt.org/z/c4GhdPMc8
So even when all of those "C26495" warnings would be fixed, there might still be some more uninitialized member variables...  So please upvote my MSVC bug report: https://developercommunity.visualstudio.com/t/False-negative-missing-analyze-warnin/10239447


Potential fix for "cannot compute fingerprint of empty X" #2152

This patch is one way of seemingly fixing the inability to compute
the fingerprint of an empty list (or set!), as reported in #2152.
It seems like empty containers can take part in fast lookup but
only if more op codes are added. Whether this is a valid approach,
given possible nuances, and the general "adding more opcodes"
going against the principle of fast lookup, is to be determined.
It should be noted that using '[' for an empty list seemingly
works too.

@pitrou, can you review this?

The solution looks fine to me, but I think it would be nice to add a test for the higher-level bug, for example:
>>> def f(x):
...:    x.append(123)
...:    return x
...:
>>> f = njit(f)
>>> f([])
Traceback (most recent call last):
  File "<ipython-input-4-279ae96cabbb>", line 1, in <module>
    f([])
ValueError: cannot compute fingerprint of empty list

>>> f([1])
[1, 123]

Thanks for the review @pitrou , I'll add the tests, I wanted to make sure the approach was valid prior to additional effort :)

As we discussed with @stuartarchibald, this is actually the wrong fix altogether. Fingerprinting needs only work for values that can be accepted as nopython mode arguments, which empty lists and sets are not. Instead, a failed fingerprint should simply signal that loop-lifting cannot succeed and that we should fallback on object mode...

Agreed. After much debugging it indeed does make it work for the wrong reasons and the fail should act as a signal to abandon the loop-lift and fall back. Thanks for looking @pitrou. Closing this as it's dead.


renaming project

Coverage decreased (-3.8%) to 96.154% when pulling c8d43f4c6654cd9b3c432aec227592356800612e on feature-rename into b172c7be19e36554f0226ce6dadfdb371fa9096e on master.

Coverage decreased (-1.5%) to 98.469% when pulling edc84e7f886be7c97b8d7ede1ead1920869a6b3d on feature-rename into b172c7be19e36554f0226ce6dadfdb371fa9096e on master.


Bug in install-src

I am trying to install the source files for QtWebEngine, linux desktop 5.9.9 gcc_64. However, this is what I get:
cradcore@localhost: ~ $ aqt install-src -m qtwebengine -O /dev-tools linux desktop 5.9.9
aqtinstall(aqt) v2.0.2 on Python 3.8.10 [CPython GCC 9.3.0]
The packages ['qtwebengine'] were not found while parsing XML of package information!
==============================Suggested follow-up:==============================
* Please use 'aqt list-qt linux desktop --modules 5.9.9 <arch>' to show modules available.
cradcore@localhost: ~ $ aqt list-qt linux desktop --modules 5.9.9 gcc_64
qtcharts qtdatavis3d qtnetworkauth qtpurchasing qtremoteobjects qtscript qtspeech qtvirtualkeyboard qtwebengine

It seems to not find qtwebengine when trying to install, but correctly lists it as a module

Looks like the "Suggested follow-up" message in this case is inappropriate. The aqt list-qt command correctly shows output pertinent to the install-qt command; it is not designed to provide data relevant to install-src/doc/example.
See the Updates.xml file at https://download.qt.io/online/qtsdkrepository/linux_x64/desktop/qt5_599_src_doc_examples/Updates.xml: there is no source module for qtwebengine. The archive qtwebengine-opensource-src-<IP_ADDRESS>z is part of the qt.qt5.599.src PackageUpdate; that means that you can install it by running aqt install-src linux desktop 5.9.9.
As far as I can tell, there are no valid options that you can pass to the -m flag for install-src. Unless I have overlooked something, maybe we should remove the flag.
The list-qt command is technically capable of to showing data relevant to install-src/doc/example, by using --extension src_doc_examples, but it doesn't list modules and it isn't documented properly. Right now, these are the only commands that work:
aqt list-qt linux desktop --extension src_doc_examples --archives 5.9.9 src
aqt list-qt linux desktop --extension src_doc_examples --archives 5.9.9 doc
aqt list-qt linux desktop --extension src_doc_examples --archives 5.9.9 examples

Todo:

Remove/replace the "Suggested follow-up" message for install-src/doc/example when a module cannot be located
Consider adding commands for list-src/doc/example.
Consider removing the -m flag for aqt install-src.
Remove src_doc_examples from the list of valid extensions for list-qt, since list-qt is not designed to use it properly.

Also worth noting, and indirectly related to this bug: install-src/doc/example will only work on the "desktop" target. I think there are three potential ways to fix this:

Remove the target parameter from the cli for install-src/doc/example (Probably the right solution, but I am reluctant to do this because it's a big change to the interface)
Ignore the target parameter for install-src/doc/example, and just fill it in with "desktop" regardless of what the user types
If the user puts anything into the target parameter that's not "desktop", give an error message that says "There are no src/doc/examples for any target other than desktop".

I prefer 1.

Remove the target parameter from the cli

but 2 may be better for consistency of UI with other command argument.

Ignore the target parameter

Which one is better on  "no surprise for user" basis?

I prefer 1.

Remove the target parameter from the cli

but 2 may be better for consistency of UI with other command argument.

Ignore the target parameter

Which one is better on "no surprise for user" basis?

I think if we released aqt v2.1.0 with option 1, we would break a lot of people's code. That would badly surprise users.
Maybe there is a way to make the target parameter optional for these commands, for backwards compatibility, so we can have the benefits of option 1 without breaking existing code?
I think that removing the -m flag for install-src qualifies as a bug fix rather than an interface change, because there's no way to use it without experiencing the bug that @cradcore is seeing. I expect that -m all might not trigger the bug, but it won't actually do anything.


Using zOS-Web Enablement toolkit from CICS

Hello,
I am wondering if i can use the zos web toolkit from a CICS application ? Are there any environment considerations . Would appreciate any pointers to documentation.
Thanks.

Hi,
good question. I was asking mysef the same - well, actually I asked @ian-burnett and got a very wholesome answer.
In short: No, you cannot use the toolkit within CICS, because it requires the LE-Option POSIX(ON), which is not available in CICS-LE. As far as I understood, CICS could provide the correct environment, if all modules were linked with the option XPLINK, but that Option is only applicable to C and C++ language modules. Here is the bit of documentation, see "Runtime options ignored under CICS" https://www.ibm.com/support/knowledgecenter/en/SSGMCP_5.5.0/applications/developing/le/dfhp3_langenv_runopts.html
With Ian's permission I could post our little Q&A here - it's a good read!
What I still don't know, though, is why the POSIX(ON)-Option is required by the toolkit...
Kind regards

Thanks @CexyChris - feel free to add that conversation here if you wish.
I still have the original email somewhere if you would rather I posted.
Ian.

Hi Everyone,
@ian-burnett thank you for handling the email! i saw you replied and explained the CICS situation and then i dropped the ball
@CexyChris Q&A would be a welcomed addition!
My overdue answer for why HTTP/HTTPS Enabler requires POSIX(ON):
HTTP/HTTPS Enabler takes advantage of the POSIX signal handling semantics to ignore SIGPIPEs while it's interacting with the socket on behalf of the user.

@CexyChris @ian-burnett @gorelikg Thank you for your responses. It saved me a bunch of time :) My colleague, who has tried the toolkit from batch and REXX was curious if this would work in CICS. In fact, he did mention reading the documentation about the toolkit needing POSIX(ON) and it not being available in CICS. But we both were not really sure and wanted to code up  something quick to try out. Glad I checked here before spending too much time.

These were the emails:
Q:
Hi Galina, Hi Ian,
we are currently working towards adapting the toolkit in to our traditional z/OS batch jobs to enable them to use software functions written in JEE, which are provided as web services. This works out rather smoothly so far.
Now, the question was raised wether it'd be possible for COBOL programs, which use the toolkit and are primarilly written for batch, to be run in CICS. From a CICS point of view this seems a little odd, because there are inevitable differences between online and batch programs (OPEN and READ come to mind first, when talking about batch programs), but from the application developer's point of view this makes a lot of sense. Being able to write code which runs in batch as well as in CICS is very desirable. So even though it might make more sense to use the CICS-provided WEB API, there is still a good reason for developers to ask for their program to be agnostic of wether it is batch or online.
When I tried out running a test program, I got an error message from the HWTHCONN callable interface with ReturnCode: 000003845 and description:The required POSIX(ON) run-time option is not set.
I then statically linked a CEEUOPT module into my program to set POSIX(ON), but this still doesn't work as CICS ignores the POSIX-Option as is stated in the documentation here: https://www.ibm.com/support/knowledgecenter/en/SSGMCP_5.5.0/applications/developing/le/dfhp3_langenv_runopts.html
But the documentation also states, the option would take effect if the running program was linked with option XPLINK. So I was wondering: If the callable interfaces of the toolkit  were linked with option XPLINK they might be running under CICS, right? I do not have an understainding of what implications come with using this option, though... Also I do not understand why POSIX(ON) is even needed. Would you please be so kind as to explain to me the need for POSIX and whether it is possible to link the callable interfaces with XPLINK. I would also like to hear your opinion about using the toolkit in CICS instead of the CICS-provided APIs.
Thank you very much for your time!
Kind regards
Christoph
Answer:
Hi Christoph,
I cannot speak as to why the z/OS Client Web Enablement Toolkit (CWET) requires POSIX: I'll leave Galina to answer that question.
While I understand the desire to keep source code common across both batch and CICS, there are some limitations which will prevent you from doing so if you are using COBOL. It is possible to run POSIX-enabled programs in CICS, however there are some caveats. The first is that, as you have found out, you need to compile and link with the XPLINK option enabled in order for CICS to provide the correct environment. The second is that only the z/OS C and C++ languages support the XPLINK convention.
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ceea200/ceea20029.htm
You mentioned your batch programs are written in COBOL so unless you write the applications in C or C++, you will not be able to obtain a POSIX environment inside CICS.
This is related to the implementation of Language Environment (LE) used within CICS. COBOL in CICS runs with CICS-LE, but you need to use batch-LE to run with POSIX enabled. Only the JVM and C applications compiled XPLINK run with batch-LE inside CICS.
Using the supplied CICS API services for network I/O, rather than the CWET functions has many advantages.
System administration is easier, because various aspects of the CICS web APIs can be configured using resource definitions, without the requirement to recompile the application. For example, changing cipher suites or target endpoints can be accomplished by modifying a URIMAP definition, whereas a caller of the CWET needs to alter the parameters passed to the API. The CICS web support provides timeout management via external configuration, both on a per-request basis and on a whole-transaction basis.
Diagnostic data is easier to obtain and use when using the CICS web APIs, because the CICS trace points can highlight the flow of data from the application, into the CICS subsystem, out to the network, then back in and back to the application. This trace can be dynamically controlled while the CICS region is running, with numerous diagnostic aids available should deeper investigation be required.
There are several monitoring benefits that can be gained by using the CICS APIs too. There are many CICS statistics fields which allow the system programmer to track the number of calls made to remote services at a global level, plus the CICS monitoring data allows the tracking of the number of calls made, elapsed time in remote calls, SSL ciphers used, amount of data transmitted etc. on a per-transaction basis.
https://www.ibm.com/support/knowledgecenter/en/SSGMCP_5.5.0/reference/monitoring/dfht3_mon_perfclass_dfhsock.html
If using the CWET within CICS, any calls to the CWET API will just appear as part of the application and CICS will not be able offer any diagnostic information as to why a transaction suffered a slowdown without instrumentation of the application code.
When using the CICS web implementation, clients can take advantage of socket pooling and SSL session caching - improving performance especially where many transactions are targeting the same endpoints.
Let me know if you need any further information.
Regards,
Ian Burnett

Thanks for that @CexyChris
While we have this discussion open, can I ask @nk2164  what your use-case was? Were you looking to use the HTTP/HTTPS handler or was it for the JSON processing?
As above, Christoph's requirement was to allow COBOL source to be shared between batch and CICS. If you only want to use some functionality in CICS and are willing to code in C, then it should be possible. CICS will allow you to EXEC CICS LINK from any language to an XPLINK C module which could then call the toolkit. I've never tried it myself, but that doesn't mean it's impossible.
If you have a use-case and are willing to keep this CICS-specific and use C (rather than shared source with batch), then I may be able to code up a sample.
Some considerations ahead of time:

Calling an XPLINK module in CICS from COBOL is relatively expensive in terms of CPU. We need to switch from the standard COBOL stack frame to the XPLINK stack frame, plus switch to a new TCB (X8 or X9). Then switch back when we return to COBOL (presumably that's your base application language).
As above, I cannot guarantee this will work - I will need to see what happens if/when I code this. There may be some hidden curiosities if we start calling the toolkit from multiple TCBs within the same address space. Using the JSON processing more likely to work (hence asking for the use-case).
None of this processing will be zIIP-eligible. If you are happy to switch languages from COBOL to Java, then Java is zIIP-eligible and there are plenty standard libraries which perform both HTTP outbound requests and JSON parsing / generation.
As per the email in the comment above, this won't offer the same configuration flexibility or RAS options as you get with the native CICS services.

Regards,
Ian

@ian-burnett , Our Use-case was to try calling REST API's from cics application and process the json response . C might not work for us.  We mostly use PLI. Reading all the considerations you documented here makes me think we need to pursue something different. Maybe explore native cics provided services or z/OS Connect EE.
I thank you all for your detailed responses.

@nk2164
From an HTTP/HTTPS Enabler + CICS perspective, agreed, until CICS supports POSIX(ON), HTTP/HTTPS enabler is not your ideal option.
Regarding, z/OS Connect EE, under the covers for batch they do use the HTTP/HTTPS enabler and for CICS they use the native CICS support, so they're definitely a good option if you don't want to deal with dual path coding.
From a JSON Parser perspective, there are no restrictions/requirements for POSIX(ON), you should have no issues invoking from a CICS application.
Just keep in mind only AMODE(31) is supported at the moment for both entities.

Sure . Thank you @gorelikg .

For CICS, look at EXEC CICS WEB OPEN/CONVERSE/CLOSE statement.
Some Cobol examples are available at :
https://github.com/walmartlabs/zECS/tree/master/Source

For CICS, look at EXEC CICS WEB OPEN/CONVERSE/CLOSE statement.
Some Cobol examples are available at :
https://github.com/walmartlabs/zECS/tree/master/Source

Thank you. This is what i ended up doing.


Shifter Components: 3jnt leg Issues

Several issues have been reported for this component in the past months:
http://forum.mgear-framework.com/t/leg-3jnt-01-cant-be-reversed/2423


Ensure that user service directory exists on upgrade (PROJQUAY-5039)

/assign @HammerMeetNail @jonathankingfc

@dmage  Hmm, upgrading from v1.2.x to v1.3.0 isn't going to be straightforward. In v1.2.x, root installs systemd services. In v1.3.0, a non-root user will not be able to stop and remove those services. How do you think we should handle this? Just document a process for cleaning up the old service? Something like:

Stop all mirror registry services
Perform upgrade (with the change in this PR)

Since this is a previous root install, running user must continue to have root access to access previous install directories and pgRoot and quayRoot flags must be specified

Delete systemd services


Singular Resource

Is your feature request related to a problem? Please describe.
Sometimes a resource will only ever be singular, for example you might have a top-level 'Site' that has site-level config. However this can only be represented as a collection. In this case it makes no sense for a collection of 'sites' as there is and will only ever be a single site
Describe the solution you'd like
It would be great to be able to define a singular / singleton collection, either in a separate category in the sidebar, or so that clicking on its type in the sidebar opens it for editing. This could be done in the collection config via an isSingleton flag.
Describe alternatives you've considered
The current workaround is to have a collection with a single item in it, however this is confusing for users of the CMS.

Hi @Undistraction, can we close as duplicate of https://github.com/netlify/netlify-cms/issues/535?

@erezrokah Ah. I did look for an existing issue, but didn't see that one.


Add MetricExportDatadogConfig & MetricExportCloudWatchConfig resources

Add a new MetricExportDatadogConfig resource, which manages
the Datadog metric export configuration for a cluster.
Add a new MetricExportCloudWatchConfig resource, which manages
the AWS CloudWatch metric export configuration for a cluster.
Add a description of the problem this PR addresses and an overview of how this PR works.

Here is a crl google doc with manual testing examples


Update base docker image

Rebased to the latest master.

LGTM. Could you resolve the conflict again?


Tracking issue for PR #3361

Per @alexcrichton in this comment, I am opening a tracking issue for the plan to eventually change cargo to assume that a build.rs file in the same directory as a Cargo.toml file is a build script. Right now cargo just issues a warning when it sees a build.rs file in the same directory as a Cargo.toml file that lacks a build = ... value.
Original PR:
https://github.com/rust-lang/cargo/pull/3361

@alexcrichton hello again! now that 1.15 is out with this change, what do you think of completing the change on the current nightly? Assuming it gets in to 1.17, that would mean users would get the build = false warning for 2 stable releases before the behavior changes.

Good question! @rust-lang/tools -- thoughts about whether we're far enough along to implement this change?

Could you clarify what exactly the change is? My understanding is that currently if build = false and there exists a build.rs in the project root, then we warn and we would change this to a hard error? Or does the warning happen when there is no build entry and a build.rs file and we would change this to silently accepting?
Is this a backwards incompatible change?

@nrc sure yeah, the state of play is this:

We'd like to automatically infer build.rs as the build script
This is backwards-incompatible to projects which have build.rs but it's not a build script
We added the ability to specify build = false to Cargo.toml to work around this.
Cargo currently warns if build.rs exists, isn't a build script, and build = false is missing.
Older Cargos will reject build = false as an invalid manifest.

The concrete change to make here is to automatically infer build.rs as a build script unless otherwise configured. This would also entail removing the warning. Crates which have build.rs, it's not a build script, and haven't configured build = false will likely break.
A preliminary list of crates with build.rs but not having it as a build script were compiled. This may not be an exhaustive list.

How does Cargo know if build.rs is a build script or not?
To be clear, this is only crates with build.rs in the root? Or would this break for src/foo/build.rs too?

Cargo does no inference based on file contents, just location. And yeah it's only build.rs at the root (next to Cargo.toml), which is quite rare in practice.
Cargo's proposed logic is that if build.rs exists next to Cargo.toml it's automatically inferred as a build script, no configuration necessary.

Thanks for the clarifications!
I think this is OK to go ahead with - we'll have had 2 whole warning cycles and the fix is pretty trivial.


Rerender the child styles (React)

Hi everyone, especially the ET staff. Could you kindly help me out on this issue?
Problem Description
I have a child component that renders the CSS that I have added to the static method css(props) into a style tag inside the child module output.
Inside the css method I use the prop.element_width to style the element width. So far so good.
That prop is updated when the element is loaded: when the element is loaded an event is triggered, the event handler update the component and the component renders again BUT the CSS is still the same!!!
However, when I mouse over the container section, the child module renders correctly.
Any help here is really appreciated since I don't manage to rerender the child module style, thank you!

@jcdotnet could you please show some code?

@lanresmith, sure!
I just created a pretty basic module so you can see the problem. I'm almost there, I feel like I'm overcomplicating this, though.
Repo:
https://github.com/jcdotnet/divi-extension-image-load

@jcdotnet could you please check out the PR I sent to the repo above?
If you check the browser console, you'll see the following error msg:
Uncaught TypeError: Cannot add property image_width, object is not extensible
    at ImageLoadItem._onImgLoad (ImageLoadItem.jsx:26)

In react, a component should not update its own props(having a component update its own props even if possible is an anti-pattern), but can update its state and the props of its children.
After the changes I made, upon saving in the settings modal (by clicking the check mark button by the bottom right corner) gives the desired result - the
Image Width (px): { this.props.image_width }
 part is updated in the UI.
Please do let me know if there are other issues.

@lanresmith thank you for the PR and sorry for not checking this.props.content (I created the example very quickly)
Yeah, you are right, but I'm still having the same issue: when loading the page the child module is not updated. Please check (save the page and reload it, instead of saving in the settings modal).
This is important because the VB page preview will be different from the front-end page until the user hovers over the container section, and this way, I can't even think of including this behavior in one of my plugins.
We are almost there...

The child needs to be updated again, so I'm changing the key only if we haven't passed the image width yet (ImageLoad.jsx, line 12):
_updateParent(childProps) {
    this.props.content.forEach( (elem, i) => {
      if (i === childProps.moduleInfo.order && elem.props.attrs.image_width !== childProps.image_width) { // ADDED CONDITION
        elem.key = Math.random(); // changing the key renders the child and the issue is solved // ADDED
        elem.props.attrs.image_width = childProps.image_width;
      }
    });
    this.forceUpdate(); // we actually change the component state, we are just forcing the update for testing purposes
  }

Even though this solves the issue, I don't like this solution at all. Also, I'm overriding the key value set by Divi:
deil_image_load_item-<IP_ADDRESS>-0
@lanresmith How would you update the child at this point in a "React and Divi" way? Thanks.

The child needs to be updated again, so I'm changing the key only if we haven't passed the image width yet (ImageLoad.jsx, line 12):
_updateParent(childProps) {
    this.props.content.forEach( (elem, i) => {
      if (i === childProps.moduleInfo.order && elem.props.attrs.image_width !== childProps.image_width) { // ADDED CONDITION
        elem.key = Math.random(); // changing the key renders the child and the issue is solved // ADDED
        elem.props.attrs.image_width = childProps.image_width;
      }
    });
    this.forceUpdate(); // we actually change the component state, we are just forcing the update for testing purposes
  }

Even though this solves the issue, I don't like this solution at all. Also, I'm overriding the key value set by Divi:
deil_image_load_item-<IP_ADDRESS>-0
@lanresmith How would you update the child at this point in a "React and Divi" way? Thanks.


NIMBUS-21::logout link defect

Description
logout link defect
The author of this pull request failed to include a description or DELETE this line.
Overview of Changes

N/A
Type of Change

N/A
Test Details

N/A
Additional Notes

N/A

You did it @vivekkamineni2018!
Thank you for signing the Anthem Opensource Software CLA.


Why can't I create one client immediately after I close another client?

Describe what you would like to know or do
I'm trying to create one client between the same ip address immediately after I close one wsclient. Just like code down here.
            try {
                WsClient client = new WsClient(new URI("ws://localhost:8080/websocket/chat"), "client");
                client.connect();

                UserDto user = buildUser();
                WsChatMsg init = buildInitMsg(user);
                client.send(JSONObject.toJSONString(init));
                log.info("send-init-{}", init);
                client.close();
            } catch (URISyntaxException e) {
                throw new RuntimeException(e);
            }

        try {
            WsClient client1 = new WsClient(new URI("ws://localhost:8080/websocket/chat"), "client1");
            client1.connect();
            UserDto user = buildUser();
            WsChatMsg init = buildInitMsg(user);
            client1.send(JSONObject.toJSONString(init));
            log.info("send-init-{}", init);
            client1.close();
        } catch (URISyntaxException e) {
            throw new RuntimeException(e);
        }

If I run this code, I got org.java_websocket.exceptions.WebsocketNotConnectedException
Describe the solution you'd considered
I've tryed catch tcp/websocket package use wireshark, It seems the the second will send RST immediatly after handshake.

Additional context
Add any other context or links about the question here.

Try using connectBlocking() instead of connect(), that way it should block the code until the connection succeeds or not.

Thank you very much, it works!!
Althought, why would that happen?

connect() returns (almost) immediately and schedules the connection on a separate thread. Sometimes it appears to work but that depends on computer and network speed, etc.
connect() is useful for when you expect the server to send the first message.


Referring to issue #9

Hello,
I could not find seperate dataset for validation and testing. As even the validation dataset is same as test_dataset3 (fs lost and found). And as far as I have understood with the datasets provided in the repo we can reproduce only table2.
I would be grateful if you provide the dataset which you used to find metric in table1.
Thank You

Hi Shanmukh,
The results in table 1 are directly coming from our Fishyscapes submission. This benchmark only gives you limited validation data (the one used in table 2) and holds out the rest for the test side (we do not get to see the data).
As such, we never had the test data used for table 1. We just submitted our code in the Fishyscapes website (in the right format) and they told us what was our results for each metric.
You can see the Fishyscapes paper where they explained in detail why they do it like this
To this end, we (i) only release a small validation set with
associated ground truth masks, while keeping larger test sets
hidden

Thank You for a quick response , I will take a look at the paper.
Congrats for producing such an excellent paper !

Hi Shanmukh,
The results in table 1 are directly coming from our Fishyscapes submission. This benchmark only gives you limited validation data (the one used in table 2) and holds out the rest for the test side (we do not get to see the data).
As such, we never had the test data used for table 1. We just submitted our code in the Fishyscapes website (in the right format) and they told us what was our results for each metric.
You can see the Fishyscapes paper where they explained in detail why they do it like this
To this end, we (i) only release a small validation set with
associated ground truth masks, while keeping larger test sets
hidden

I'm sorry to bother you, could you upload your code which submitted to the Fisherscapers submission?


Add HollowIncrementalProducer support for withThreadsPerCpu

This introduces the threadsPerCpu  for HollowIncrementalProducer.
HollowIncrementalProducer incrementalProducer = new HollowIncrementalProducer(producer, 2.0d);

Devs can still use the constructor as before
HollowIncrementalProducer incrementalProducer = new HollowIncrementalProducer(producer);

It also introduces the usage of SimultaneousExecutor in addRecords while running a cycle. By default it uses 1.0d threads per CPU

Thanks for the feedback @toolbear!
I fixed the formatting and cleaned up the final attributes

ready for review again @toolbear @kineshsatiya

ready for review again @toolbear @dkoszewnik


Add Custom ConfigMap Support for ingress-nginx

By default ingress-nginx require for 3 ConfigMap but I leave it as empty in original implementation, in order to simplify for debug :-P
With this patch we could apply custom ConfigMap to ingress-nginx in yaml dict format, which is very useful, e.g. I hope to use ingress-nginx to handle a backend BitBucket port 7999 in TCP for git connection ;-)
See:

https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/configmap.md
https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/exposing-tcp-udp-services.md

Thanks @Atoms ;-)


docs(site): Update next documentation to v11

Documentation Feedback
I need to check the examples/updates from version v11, but the site still uses RC from v10.
We should update http://next.material.angular.io/ to work with v11

Closing because it has been done.


chore(package): update joi to 13.4.0

Coverage remained the same at 100.0% when pulling 9840740ab614a04a0a1e25e462c2c6ed4b8bfc31 on update-dependencies into 75ccfb7d4062efb4d55b9e0d7d40a0206a695814 on master.


Player may get unlimited money

*Detailed description of the issue:
I found a bug which can get unlimited money ....
My player select Miner job and I set it like
    diamond_ore:
      income: 50```

This situation player will get $50 for each diamond ore mined.
But I found out player able to get unlimited income from that with the method :
1) Get a *silk touch* pickaxe and keep mining and place it

If I add another rules which is
```  Place:
    diamond_ore:
      income: -50.0```
They will ask their friend to place it.... so is there any ways that can detect the player mine the *diamone_ore* that generate naturally?
---

**CONFIG SECTION (DELETE IF NOT RELEVANT):**
```Miner:
  fullname: Miner
  shortname: M
  FullDescription:
  - "Earns money mining minerals and ores."
  ChatColour: DARK_GRAY
  chat-display: full
  leveling-progression-equation: 10*(joblevel)+(joblevel*joblevel*4)
  income-progression-equation: baseincome-(baseincome*0.1)
  points-progression-equation: basepoints+(basepoints*(joblevel-1)*0.01)-((basepoints+(basepoints*(joblevel-1)*0.01))
    * ((numjobs-1)*0.05))
  experience-progression-equation: baseexperience-(baseexperience*((numjobs-1) *0.01))
  rejoinCooldown: 10
  maxDailyQuests: 1
  Gui:
    Item: wooden_pickaxe
    slot: 11
  Break:
    coal_ore:
      income: 5.0
    lapis_ore:
      income: 15.0
    redstone_ore:
      income: 15.0
    diamond_ore:
      income: 50.0
    emerald_ore:
      income: 80.0
    nether_quartz_ore:
      income: 15.0
  Smelt:
    iron_ingot:
      income: 20.0
    gold_ingot:
      income: 30.0
    netherite_scrap:
      income: 100.0
  Place:
    coal_ore:
      income: -5.0
    lapis_ore:
      income: -15.0
    redstone_ore:
      income: -15.0
    diamond_ore:
      income: -50.0
    emerald_ore:
      income: -80.0
    nether_quartz_ore:
      income: -15.0

Jobs version:
Jobs<IP_ADDRESS>.jar
Server Type (Spigot/Paper/etc):
Paper
Server Version (using /ver):
This server is running Paper version git-Paper-706 (MC: 1.16.5) (Implementing API version 1.16.5-R0.1-SNAPSHOT)
You are 76 version(s) behind
Previous version: git-Paper-704 (MC: 1.16.5)
Relevant plugins (Delete if this isn't needed):

You can set a time for which they cannot be paid if they remine a placed block to prevent this somewhat, or you can create a job that everyone has that charges for placing blocks like this that pay well.

“set a time for which they cannot be paid if they remine a placed block”
How do I set a time ?Is there any example for that?

@Xuan1418
You have restrictedBlocks file where you can define how long we should wait before we will pay for placed block. This is a fix/workaround to issue with players placing and braking same block over and over again. You do need to enable PlaceAndBreakProtection in generalConfig file, which should be enabled by default but you might still need to add
  DIAMOND_ORE: -1 into restrictedBlocks files blocksTimer list


Independent ON/OFF + Full interop

Sensor ON/OFF controlled programmatically
BLESensor ON means sensor follows bluetooth adapter state
BLESensor OFF means sensor is off regardless of bluetooth adapter state
BLESensor OFF stops the process gracefully, so there is a short delay between programmatically setting it to OFF, and actual stopping of BLEReceiver and BLETransmitter
InertiaSensor ON/OFF supported
Validated on Samsung A10, A20, with iPhone 6+

Closes #47
Signed-off-by: c19x<EMAIL_ADDRESS>

Full interop with OpenTrace to read from and write to OpenTrace only devices
Enables detection of Herald devices by legacy OpenTrace devices
BLEDevice reuse approach migrated from iOS to improve efficiency


Support legacy webpack config

Prevent @drewpc's mystery for other users: https://github.com/redfin/react-server/commit/a23199e5506794feeefca16228001645b19b1a27

This is a one-off implementation of https://github.com/redfin/react-server/issues/783 for only this config key


Fix resource failure, change requirements handling, and refactor test config

It turns out that even though Juju claims that it is attaching resources when you deploy a bundle referring to store charms w/ resources along with an overlay that points to local copies of the charms, it actually doesn't. So the resources were failing, but because of how the handlers were working, the status was not being surfaced properly and the charm seemed like it was functional when it wasn't.
This also switches to pipenv to manage and lock the requirements, with an update target for updating the dependencies. It also switches the operator framework to pull from GitHub rather than PyPI to pick up some newer, as yet unreleased fixes (specifically the config default value handling in the test harness). Finally, it refactors the tox config to use pipenv, remove the unused build env, and makes running tox in the repo root actually run the tests for the charms.

Looks good to me!