cli6rc6 vendor.js duplicate some rxjs functions

Versions
Angular CLI: 6.0.0-rc.6
Node: 10.0.0
OS: win32 x64
Angular: 6.0.0-rc.5
... common, compiler, compiler-cli, core, forms, http
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.5.8
@angular-devkit/build-angular     0.5.9
@angular-devkit/build-optimizer   0.5.9
@angular-devkit/core              0.5.8
@angular-devkit/schematics        0.5.8
@angular/cli                      6.0.0-rc.6
@ngtools/json-schema              1.1.0
@ngtools/webpack                  6.0.0-rc.7
@schematics/angular               0.5.8
@schematics/update                0.5.8
rxjs                              6.0.0
typescript                        2.7.2
webpack                           4.6.0

Repro steps
build with :
"optimization": true,
"outputHashing": "none",
"sourceMap": true,
"extractCss": true,
 "namedChunks": false,
"aot": true,
"extractLicenses": true,
"vendorChunk": true,
"buildOptimizer": true

Run source-map-explorer ./dist/de/vendor.js
Observed behavior

Desired behavior
Don't duplicate rxjs stuffs in vendor.js

Same behavior with v6.0.3
You have idea @filipesilva

You might have different versions of rxjs used by libraries. If that's the case, then the correct behavior is to have duplicates.
For instance, if your app depends on rxjs 6 and a library depends on rxjs 5, then your bundle should have both because they are different.
You can check this using npm list rxjs.

@filipesilva thanks
seems i have same version

@filipesilva can you confirm here  cli must use all operators from /rxjs/_esm5/internal folder not from /rxjs/internal
in my node_modules/rxjs i have this structure

Wonder if cli make good choice and take things from _esm5 not otherwhere


96066/legal requirements

Hey @MartinWheelerMT  & @tim-wilde-nimble , have created a draft PR so you can keep an eye on what I'm doing.  Feel free to jump in if you think there's anything daft here.

I could look to merge what's done so far just to keep the size of the PR down. @MartinWheelerMT  & @tim-wilde-nimble keen to here your thoughts on that?


only FLOAT is supported for tensorflow nodes....???

I have trained a custom tensorflow graph and when i run it for inference on a raspberry pi3, I get the following exception.
terminate called after throwing an instance of 'armnn::ParseException'
what():  Currently only FLOAT is supported for tensorflow nodes (apart from Const)
Aborted

That's interesting @vinayonchip, do you know what data types are in your graph?

I am using integers as well as floats.

Hi @vinayonchip ArmNN doesn't support integer tensors, except for the QASYMM8 quantized type. If you could describe a bit more about your use-case, we could maybe find a workaround, or add your request to our roadmap?

I've had a bit of a think about this, and if the tf.gather() operation is the last stage in your network, maybe you could just run the rest of the net in ArmNN and roll your own word lookups as the final stage?
If you fundamentaily need an integer loss function for your application then that's going to be a bigger problem, but if you can get the net to work with float except for the word embeddings, you should be able to use ArmNN for the difficult bits.
Whatever you decide, I've noted down your interest in int32 support and tf.gather() for our roadmap.

Hi @vinayonchip we're looking at requirements for language processing models at the moment. Would it be possible for you to share more details about your model? Is it an open-source architecture or something proprietary?

Hi @vinayonchip we're looking at requirements for language processing models at the moment. Would it be possible for you to share more details about your model? Is it an open-source architecture or something proprietary?

Hi @MatthewARM ,
We are using Google's Transformer model for our language processing task. Hence we have to use both the types(INTS, FLOATS) :
Ints for inputs and outputs.
Floats for loss function/weights
https://github.com/tensorflow/models/blob/master/official/transformer/model/transformer.py
Thanks in advance.!

Thanks @vinayonchip that's very useful. We're keen to support Transformer but we haven't yet figured out all of the bits of work that are necessary.

Closing this as the Tensorflow parser now supports Signed32 tensors and the Gather operator. Movement in the right direction although the full Transformer net will likely require other things too.

Can I see the commits made to support INT32 for tensor flow nodes

db2b160bf9e7759d0157dfa57ee940290f5170e3


Support an array of sliceId for setIndexDefinition?

Is your feature request related to a problem? Please describe.
We were trying to create indexes for events object by date. So that if we look for a specific date then it will return the collection of events that cover that given date.
Event { start: Date, end: Date, ...}
indexes.setIndexDefinition(
    'eventsByDate',
    'events',
    (getCell) =>  ['2022-09-19', '2022-09-20'] // eg. return array of ISO date from this code: eachDayOfInterval(getCell('from'), getCell('to')).map((date) => formatISO(date))
);

indexes.getSliceRowIds('eventsByDate', '2022-09-19') // return events that cover this date
indexes.getSliceRowIds('eventsByDate', '2022-09-20')  // return events that cover this date

Describe the solution you'd like
I think if the setIndexDefinition could support having sliceId array to index rows then it's more flexible.
Describe alternatives you've considered
We are not sure of the best way to solve this with Tinybase without manually indexing rows by listening to the row-adding event.
Additional context
N/A

OK, and if there is a date with no events you want to access an empty array, I assume?
I can imagine something like this. OK if I think about it for a few days?

The main disjoint from the current behavior here is that today, every row lives in one and just one slice. Here, you can now have a row that exists in multiple slices, so we'll need to bookkeep them all.
Nevertheless, I can think of other uses for this (eg keyword search!) so I will have go.

OK, @tienle, please see the example below, which works with the new beta release.
Let me know if that works for you. You can try it out by installing v2.1.0-beta.0 from NPM.
const store = createStore().setTable('pets', {
  fido: {species: 'dog'},
  felix: {species: 'cat'},
  rex: {species: 'dog'},
});

const indexes = createIndexes(store);
indexes.setIndexDefinition('containsLetter', 'pets', (_, rowId) =>
  rowId.split(''),
);

console.log(indexes.getSliceIds('containsLetter'));
// -> ['f', 'i', 'd', 'o', 'e', 'l', 'x', 'r']
console.log(indexes.getSliceRowIds('containsLetter', 'i'));
// -> ['fido', 'felix']
console.log(indexes.getSliceRowIds('containsLetter', 'x'));
// -> ['felix', 'rex']

Also check out https://beta.tinybase.org/demos/word-frequencies/ - I'm pretty pleased with how this worked out. Thank you for the inpsiration!

Great! Good luck with the app and I’ll close this out.
I’ll release it to GA in v2.1.

https://github.com/tinyplex/tinybase/releases/tag/v2.1.0


Feature/59 create the main menu

I've use clickable widget for my button, but isn't currently working. If you can say me what is wrong with it

Codecov Report

Merging #222 (ae0b50f) into master (db05b03) will decrease coverage by 0.13%.
The diff coverage is 0.00%.

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


Added datacap v9 actor

Summary of changes
Changes introduced in this pull request:

Added datacap v9 actor state for NV17 migration

Reference issue to close (if applicable)

Closes #111
Other information and links

Codecov Report
Patch coverage has no change and project coverage change: -0.01 :warning:

Comparison is base (b59c37a) 9.55% compared to head (ef71771) 9.55%.

Additional details and impacted files
@@           Coverage Diff            @@
##            main    #113      +/-   ##
========================================
- Coverage   9.55%   9.55%   -0.01%
========================================
  Files        308     311       +3
  Lines      28674   28686      +12
========================================
  Hits        2740    2740
- Misses     25934   25946      +12

Impacted Files
Coverage Δ

actors/datacap/src/lib.rs
100.00% <ø> (ø)

actors/datacap/src/v9/mod.rs
0.00% <0.00%> (ø)

actors/datacap/src/v9/state.rs
0.00% <0.00%> (ø)

actors/datacap/src/v9/types.rs
0.00% <0.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[Feature Request]: Cleanup Empty State Text

Feature description
On each of our sections in the Projects view, we have a subtext that is redundant.

Describe alternatives you've considered
No response
Anything else?
No response

https://issues.redhat.com/browse/RHOAIENG-1784


B1 submision

Node ID: c89e05fa4d204665
Baker ID: 544

rejected:B1
It looks like you are trying to submit B1, however it seems like the following submission criteria are problematic:

Logs are missing
We’ve thus marked B1 as rejected, however if this is a mistake, please upload the log summary and we can re-review.

rejected:B4
reason:account address not submitted, cannot verify on-chain AddBaker transaction

rejected:B4
reason:account address not submitted, cannot verify on-chain AddBaker transaction


feat: Angular2 Material Integration

It would be great to have Angular2 Material support out of the box.

Some Angular material components are here ng-2 material

@vasspilka I was aware of that, but that's nowhere near something we could use at the moment. And there isn't any official distr for that, you can only pull it from git and I would prefer to have it from npm.

Close with f8e8fa0e97bf8a4dd262da3f58956643692ee7f8


swiftAddressBook?.allPeople is raising exec bad access.

This is occurring not frequently.

Please read https://github.com/SocialbitGmbH/SwiftAddressBook/issues/55
And also check the linked issues. If the problem can't be solved in any way described there, we can reopen this issue.

Checking. Thanks for your response.


Update 10-tls-bootstrapping-kubernetes-workers.md

Missing kubeconfig option as the default kubeconfig file doesn't exist yet

I also ran into this.

Hi @jerem0808 @codecio
We have now merged a major change to bring this to v1.24.
This has been addressed as part of the upgrade.


Allow postgresql 8 module

Adds support for postgresql < 9.0.0

Thanks! Do you happen know why it fails on 6? I'm unable to view the logs.

as soon as #123 is merged, you can rebase and it should pass.

@ju5t All checks have passed now. A new release with this change included would be awesome!

@saz sorry for the delay; I've released 2.2.2.


libc:getline support backspace

Summary
getline function support backspace
Impact
None
Testing
sim qemu arm

[Experimental Bot, please feedback here]
No, this PR does not meet the NuttX requirements.
Missing Information:

Summary:

Lacks a clear explanation of why the change is necessary. Is getline  broken? Is this a new feature request?
Missing details on how the backspace functionality is implemented.

Impact:

Even if the change seems minor, you need to carefully consider and document any potential impact. For example:

Impact on user: Will existing users who rely on the old getline behavior be affected?
Impact on documentation: Does this change require updates to the NuttX documentation?

Testing:

Insufficient Detail:  "sim qemu arm" is not specific enough. Specify:

The exact simulator used (e.g., QEMU version)
The specific ARM architecture simulated
The NuttX configuration used

No Logs:  Provide actual testing logs (both before and after the change) to demonstrate the issue and the fix.

Recommendations:

Expand the Summary:  Clearly state the problem or need this PR addresses and provide a concise technical overview of your implementation.
Analyze Impact Thoroughly: Carefully consider all potential impacts, even if they seem minor.  Document your reasoning for each "NO" answer. If the impact is "YES," provide a detailed explanation.
Provide Specific Testing Information: Include the following:

Simulator details: Version, architecture, etc.
NuttX configuration:  Board, build options
Complete Logs: Copy and paste relevant sections of the build and runtime logs to demonstrate the issue before the change and the correct behavior after the change.

Isn't this already implemented and user selectable with Kconfig? See: https://nuttx.apache.org/docs/latest/applications/examples/termios/index.html.
Should getline also depend on those configuration parameters?

Isn't this already implemented and user selectable with Kconfig? See: https://nuttx.apache.org/docs/latest/applications/examples/termios/index.html.
Should getline also depend on those configuration parameters?

Don't need. After https://github.com/apache/nuttx/pull/8843, the software terminal setting always exist, CONFIG_SERIAL_TERMIOS only control the hardware specific setting (e.g. baud rate).


[CLI]: client doesn't check WANDB_ARGS environment variable when setting the command for a run

Describe the bug

wandb doesn't use wandb.env.ARGS in setting the "command" field for the run info.

import os

import wandb

os.environ["WANDB_PROGRAM"] = "test_program"
os.environ["WANDB_ARGS"] = "test_arg"

wandb.init(project="my-awesome-project")
wandb.finish()

Call script with:
python script.py unrelated args

I would expect to see "Command: test_program test_arg" in the UI, but I'm seeing "Command: test_program unrelated args".

It looks like the value is being set here which doesn't check wandb.env.ARGS. Compare this to the line where the program is set which does perform a check to see if wandb.env.PROGRAM has been set.
Note: there is a get_args function defined which attempts to parse the value from the environment variable, but this function doesn't appear to be used anywhere in the repo.
Additional Files
No response
Environment
WandB version: 0.13.9
OS: macOS-13.1-arm64-arm-64bit
Python version: 3.10.9
Additional Context
No response

Hey @jeremyjordan, apologies for the delay here. We looked into this issue and realized that WANDB_ARGS env var only works for the launch feature. We'll file a feature request for this and folllow up with you as soon as we've an update.

Sounds good, let me know if you'd like me to put up a draft PR to resolve the issue. Happy to help!


Alternative

Hi,
I there any alternative to this bundle ?
Thanks

Hi @GuillaumeSTEIN, no, as far as I know there's no alternative, sorry.


AmazonSecurityTokenServiceClient AssumeRoleAsync duplicated user agent header causes SignatureDoesNotMatch error

Describe the bug
I'm signing Amazon SP-API requests with my AWS role, I have a service which has two (or more) instances running in parallel via Tasks each instance tries to assume the same AWS role and one of them fails.
I inspected the requests and the one failing has the user-agent header which gets duplicated.
I had no problems until I ran 2 services in parallel.
Here's my code:
using var STSClient = new AmazonSecurityTokenServiceClient(AccessKey, SecretKey);

var response = await STSClient.AssumeRoleAsync(new AssumeRoleRequest() {
  RoleArn = RoleArn,
  DurationSeconds = 3600,
  RoleSessionName = Guid.NewGuid().ToString()
}, cancellationToken);

Here's the request that succeeds:
POST https://sts.amazonaws.com/ HTTP/1.1
User-Agent: aws-sdk-dotnet-coreclr/<IP_ADDRESS> aws-sdk-dotnet-core/<IP_ADDRESS> .NET_Core/6.0.13 OS/Microsoft_Windows_10.0.19043 ClientAsync
amz-sdk-invocation-id: 48d8fc02-08e2-472d-b1fe-fc512c52db73
amz-sdk-request: attempt=1; max=5
Host: sts.amazonaws.com
X-Amz-Date: 20230308T160729Z
X-Amz-Content-SHA256: 37bd71e2071571eebdbb3d377a9d44d17cd851b3263eacf1968bfc78ed69f582
Authorization: AWS4-HMAC-SHA256 Credential=<credential>/20230308/us-east-1/sts/aws4_request, SignedHeaders=content-type;host;user-agent;x-amz-content-sha256;x-amz-date, Signature=71b12f9e23a4d834f9c5beed230448b8467a59e9c5c849f88a0a3d239998f448
Content-Length: 178
Content-Type: application/x-www-form-urlencoded; charset=utf-8

Action=AssumeRole&DurationSeconds=3600&RoleArn=<role>&RoleSessionName=<value>&Version=2011-06-15

And here's the one failing:
POST https://sts.amazonaws.com/ HTTP/1.1
User-Agent: aws-sdk-dotnet-coreclr/<IP_ADDRESS> aws-sdk-dotnet-core/<IP_ADDRESS> .NET_Core/6.0.13 OS/Microsoft_Windows_10.0.19043 ClientAsync aws-sdk-dotnet-coreclr/<IP_ADDRESS> aws-sdk-dotnet-core/<IP_ADDRESS> .NET_Core/6.0.13 OS/Microsoft_Windows_10.0.19043 ClientAsync
amz-sdk-invocation-id: 24ae31e9-fc48-462a-8ff0-3e2c02595758
amz-sdk-request: attempt=1; max=5
Host: sts.amazonaws.com
X-Amz-Date: 20230308T160729Z
X-Amz-Content-SHA256: 4b00a7a3dbb5728f4b39748bd4759fa755d973ae4fcc7b6e1639eaa3a318a461
Authorization: AWS4-HMAC-SHA256 Credential=<credential>/us-east-1/sts/aws4_request, SignedHeaders=content-type;host;user-agent;x-amz-content-sha256;x-amz-date, Signature=e65dfd28b77e61c241d1ab11bc7d63fd972aef2ba50e3f6831de7e92362962c0
Content-Length: 178
Content-Type: application/x-www-form-urlencoded; charset=utf-8

Action=AssumeRole&DurationSeconds=3600&RoleArn=<role>&RoleSessionName=<value>&Version=2011-06-15

As you can see the user-agent header is repeated twice
Expected Behavior
The request should have the correct user-agent header
Current Behavior
The request fails with the response:
HTTP/1.1 403 Forbidden
x-amzn-RequestId: fb2343ea-6dc2-40b5-b510-173c7999ebe3
Content-Type: text/xml
Content-Length: 431
Date: Wed, 08 Mar 2023 16:07:55 GMT

<ErrorResponse xmlns="https://sts.amazonaws.com/doc/2011-06-15/">
  <Error>
    <Type>Sender</Type>
    SignatureDoesNotMatch
    <Message>The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.</Message>
  </Error>
  <RequestId>fb2343ea-6dc2-40b5-b510-173c7999ebe3</RequestId>
</ErrorResponse>

Reproduction Steps
Try to run two (or more) Tasks in parallel which try to assume the same role
Possible Solution
No response
Additional Information/Context
No response
AWS .NET SDK and/or Package version used
AWSSDK.SecurityToken <IP_ADDRESS>
Targeted .NET Platform
.NET 6
Operating System and version
Windows 10

Hi @Xriuk,
Good morning.
Thanks for reporting the issue. Unfortunately, I'm unable to reproduce the issue using the below code (using AWSSDK.SecurityToken <IP_ADDRESS>):
using Amazon.SecurityToken;
using Amazon.SecurityToken.Model;

string accessKey = "<<access-key>>";
string secretKey = "<<secret-key>>";
string roleArn = "<<arn-of-role-to-assume>>";

var parallelTasks = Enumerable.Range(0, 6).Select(i =>
{
    return Task.Run(async () =>
    {
        using AmazonSecurityTokenServiceClient STSClient = new AmazonSecurityTokenServiceClient(accessKey, secretKey);

        AssumeRoleResponse response = await STSClient.AssumeRoleAsync(new AssumeRoleRequest()
        {
            RoleArn = roleArn,
            DurationSeconds = 3600,
            RoleSessionName = Guid.NewGuid().ToString()
        });
        Console.WriteLine($"Iteration {i}, response: {response.Credentials}");
    });
});

await Task.WhenAll(parallelTasks);

Could you please advise on:

The environment where the code is being executed?
How many service tasks are being executed?
Share sample code reproduction that creates service tasks and tries to assume the role, and reproduces the issue.

Thanks,
Ashish

Yes, I confirm that I had Fiddler open in the background, also without it open it seems that everything works.

s-sdk-dotnet-coreclr/<IP_ADDRESS> aws-sdk-dotnet-coreclr/<IP_ADDRESS>

@Xriuk Thanks for your response. Fiddler is a network proxy tool, so I'm unsure if there is an issue with fiddler which is messing up the user agent header. Please confirm if this issue is closed since it's not feasible to troubleshoot Fiddler issue.
Thanks,
Ashish


Add more granular minimum and maximum fees per transaction type

This will introduce a fixed fee (low, medium and high) for STX transactions to prevent users from overpaying by using the default options in Leather.
https://github.com/leather-io/mono/pull/600
This contains the current min/max fees in case the fee estimator gives us a higher value and suggestion for new min/max values per setting (low, medium, high) and transaction type (STX transfer, Contract call or Contract deployment):
https://docs.google.com/spreadsheets/d/1SVtbuEtUjAvYdnbR-5bDch9wCMrkv7t4VDCZK5T0JYY/edit?gid=0#gid=0
A couple more notes:
There may be better solutions, especially for contract calls and contract deployments. There is a lot more variation, and some require more of the block budget than others. That is currently not reflected by these flat fee rates (although the fee estimator API does factor this in), In the long term, a solution based on uSTX/%block could be used to make better judgements.
Or a solution like this: https://github.com/hirosystems/stacks-blockchain-api/pull/2172. If we use a modifier like that, we can possibly use more lenient maximums. If the modification factor is applied first and still turns out higher than the maximum, we can still cap it there to avoid surprises seen in the past of users unknowingly setting a 500 STX fee (because it was the "normal" option served by the wallet).

Added this to the next cycle, though we will need some design eyes on this. @michelly / @fabric-8


Can't set different edges length between 2 nodes

I have constructed a network diagram, but I can't set edges with different length with direction: 'LR'.
Regards

Hi @DecioMachado,
I have no idea what your trying to achieve. Could you provide an MWE, please?
Thanks.


Bump vsphere-csi-driver to v2.4.2

Bumping vsphere-csi-driver to the latest release.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Actually now that I think about this, I'm not sure you can do this. We need to stay on a version which supports 1.20 until we break out into release branch builds
/hold

Actually now that I think about this, I'm not sure you can do this. We need to stay on a version which supports 1.20 until we break out into release branch builds
/hold

Downgraded to v2.4.2 which supports 1.20 through 1.22 according to the VMware docs.

/test all

/approve

/unhold


chore(main): release 4.1.0

:robot: I have created a release beep boop
4.1.0 (2024-09-30)
Features

add mini pick as provider for action_palette (#272) (7d02085)
add picker field to prompt resolution (#275) (1808fd9)

Bug Fixes

prompt library conditionals (#277) (a0518b9)
telescope extension can take opts (423447f)
telescope extension for the action palette (#267) (bf3722b)
tools: remove print statement for RAG tool (0ab3a6a)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v4.1.0
:sunflower:


Properly support setting DD_TRACE_TRANSPORT to "none"

Description
Omit the 'curl' library if DD_TRACE_TRANSPORT is set to "none"
Motivation
There is clearly the intent to be able to not include a default transport, by setting DD_TRACE_TRANSPORT=curl.
However, two things were missing:

To ignore the bundled curl library from the build
to replace the default_http_client_curl.cpp with default_http_client_null.cpp

Integrations that provide their own transport may not want to build and link a whole unused library, along with any runtime library dependencies it makes.
Additional Notes

Fantastic @kristjanvalur.
This is indeed the intended behaviour. I appreciate your contributions.

I could add a check in the config builder for a nullptr, but since this is an integration issue and not a configuration issue, in my view assuming a non-null ptr (and thus a correctly written integration) is ok.


change package version for twitter-connector unit tests

Hi @dburugupalli, thanks for doing this. It would be great if we can rename all references in the connector to point to Cisco-Kosha


UWP/Windows10 build fails when react-native-dialogflow module is imported.

I am conditionally importing Dialogflow module in my project. However, "react-native run-windows" (react-native-windows) still fails because index.js (or index.windows.js) file missing.
This is how I am importing module:
let Dialogflow_V2 = null;
if (Platform.OS === 'android' || Platform.OS === 'ios') {
Dialogflow_V2 = require('react-native-dialogflow').Dialogflow_V2;
}
And, here is the exception:
_error: bundling failed: Error: While trying to resolve module react-native-dialogflow from file W:\Projects\ReactNative\ServiceLinkMobile\src\containers\main\MainDisp.js, the package W:\Projects\ReactNative\ServiceLinkMobile\node_modules\react-native-dialogflow\package.json was successfully found. However, this package itself specifies a main module field that could not be resolved (W:\Projects\ReactNative\ServiceLinkMobile\node_modules\react-native-dialogflow\index. Indeed, none of these files exist:

W:\Projects\ReactNative\ServiceLinkMobile\node_modules\react-native-dialogflow\index(.native||.windows.js|.native.js|.js|.windows.json|.native.json|.json)
W:\Projects\ReactNative\ServiceLinkMobile\node_modules\react-native-dialogflow\index\index(.native||.windows.js|.native.js|.js|.windows.json|.native.json|.json)
at ResolutionRequest.resolveDependency (W:\Projects\ReactNative\ServiceLinkMobile\node_modules\metro\src\node-haste\DependencyGraph\ResolutionRequest.js:103:15)
at DependencyGraph.resolveDependency (W:\Projects\ReactNative\ServiceLinkMobile\node_modules\metro\src\node-haste\DependencyGraph.js:272:4579)
at dependencies.map.relativePath (W:\Projects\ReactNative\ServiceLinkMobile\node_modules\metro\src\DeltaBundler\traverseDependencies.js:376:19)
at Array.map ()
at resolveDependencies (W:\Projects\ReactNative\ServiceLinkMobile\node_modules\metro\src\DeltaBundler\traverseDependencies.js:374:16)
at W:\Projects\ReactNative\ServiceLinkMobile\node_modules\metro\src\DeltaBundler\traverseDependencies.js:212:33
at Generator.next ()
at step (W:\Projects\ReactNative\ServiceLinkMobile\node_modules\metro\src\DeltaBundler\traverseDependencies.js:297:313)
at W:\Projects\ReactNative\ServiceLinkMobile\node_modules\metro\src\DeltaBundler\traverseDependencies.js:297:473
at _

In version 3.2.0 I merged both index.xxx.js files to one index.js.
Could you try it with this version? If you still have this error, feel free to reopen this issue!


How do I set the batch size for vLLM

##Question

If I  run the vllm offline and can I set the batch size ? I mean I want to test the its e2e latency for different batch size.

In the below code, the prompts is a list and has 4 prompt, does it means the batch size is 4?
prompts = [
    "Hello, my name is",
    "The president of the United States is",
    "The capital of France is",
    "The future of AI is",
]
sampling_params = SamplingParams(temperature=0.8, top_p=0.95)

Yes because the default max sequence is 256 by default.


oop naming tweaks

I would adopt the same naming/dir structure for Styles as you did with Scripts:

Move Styles.php to Scripts\StyleRegistry.php
Move each style class to a Customizer or Frontend folder (like for scripts)

Yup, I'll do that.
Right now though I'm trying to do the separate the concept of "fields", "controls" and "settings":
The user right now defines "controls", and the plugin creates the settings and then the control.
What I wand to do is have the user create "fields".
A field is a more generic concept... and we'll need it as we move forward.
I want to have the following classes:
Builder
Field
Setting
Control

The Builder class will parse the fields and pass it on to the other classes as needed.
The Field class is mostly sanitation and takes care of any modifications we need to do to the arguments based on their type
The Setting control will create the settings
The Control class will create the controls.

Since "control" is actually the visual element we use, it's wrong that I use it for pretty much everything here. "Field" is more appropriate.
Thoughts?

Just sent a couple of beers to enjoy over the Easter break. Thanks for the awesomeness of Kirki @aristath Sent a little something via http://kirki.org/ :)

@cmwwebfx Awesome, thanks a lot man!! I really appreciate it! :beers:

@aristath I think it is a good idea to proceed like that. I also think that there needs a concept on top of the current controls so that we can build on top of them if necessary. We should not rely so heavily on the core WordPress controls.
This would require some thinking to do it properly. If I can, I will try to get something working for just a couple of control types to get you started. I'll try that before next tuesday.

I've been thinking...
It would be great if we could have separate configurations for separate fields.
If a plugin and a theme for example use Kirki simultaneously and the plugin is using options while the theme is using theme_mods, then that would cause mayhem.
So... We could do something like this in our themes:
$kirki = new Kirki( $config, $fields );

This way a configuration would be linked to the particular fields and would not be global.
Of course that would mean restructuring some things but it could be worth it...
Thoughts?

Especially if someone will use Kirki in a plugin.

God idea but you should separate the creation of the Kirki instance and the configuration. Some hooks probably need to be declared very early whereas passing the configuration may be done later.
I would do something like this when my plugin/theme is loaded:
´$my_kirki = Kirki::newInstance();´
And later on (probably in hook after_setup_theme or plugins_loaded) I would:
´$my_kirki->configure($config, $fields)´

I can help with this.  ;)   Ari ping me about it.  ;)


feat: initial codegen

Makes progress towards #226
This cleans up the codegen code somewhat, though it's still not the prettiest. It also adds codegen for codecs, as well as initial stub codegen for pallets and their storage and calls.
This has only been minimally manually tested; automatic testing should be added, but we need to figure out the best approach for this.

Tested with Polkadot and the output looks correct.
This is a great foundation: types, corresponding codecs (each explicitly typed to $Codec<T> and named in accordance with their idx, specialized codecs drawn into scope, tsdocs wherever possible, and even the beginnings of extrinsic / storage bindings! Awesome work @tjjfvi.
Would love to be able to use it through something like...
deno run -A -r https://deno.land/x/capi/codegen.ts \
  --src="wss://rpc.polkadot.io" \
  --out="polkadot.ts"


A self-contained alternative proof for L06

This proof uses $a+b$ in place of $\max a\ b$ and only properties of natural numbers (without needing to consider the two cases where $a\leq b$ and $b\leq a$). It uses have instead of specialize which is covered in today's lecture.

Nice idea!
The advantage of this method is that we only need to teach le_self_add etc rather than having to teach about <= and max.
The disadvantages are that (1) it's not what a mathematician would do and (2) we'll need the max/min anyway when we do the neighbourhood filter, which has epsilon>0 and delta>0 and asks us to find a positive real which is <= both.
So I am not sure about this approach.

I agree that this is not the most "natural" move a typical mathematician would have used. As there is currently no plan to use this approach, I'll close this for now.


Add spin cloud logs to view app logs on the CLI

It would be beneficial to be able to tail logs from the CLI when debugging issues, rather than needing to open the Cloud UI - especially when iterating on a deployment.
Example UX:
$ spin cloud logs my-app-name --tail
# continuously tail logs until interrupted

$ spin cloud logs my-app-name --since=TIMESTAMP
# fetch all available logs since the given timestamp and then exit

$ spin cloud logs my-app-name --reverse
# fetch recent logs with the _newest logs first_

-f instead of --tail PLEASE! :)

Thanks! It works like charm!


Add CMake project

Hi,
I just made a CMake script for the project, because I want to include it within another CMake project. The CMake script includes an install target (mostly for windows) and supports SIMD on the x86 platform (supporting NEON shouldn't be hard, but I don't need it). However I had to change #include "config.h" in order to support out of source tree builds. I hope you are ok with my solution.
I successfully built the library on windows with mingw-w64 gcc 4.8.2 x86_64 and Visual Studio 2015 x86/x86_64/ARM.
My script is CC0 licensed and the TargetArch.cmake is distributed under a 2-clause BSD license (please note that no one distributes a cmake script in binary form, so the second clause concerning binary distribution is more or less meaningless).
Fixes #70
Cheers,
Henrik

Well, actually I tested the modified makefile using the windows cmd and msys2/zsh and mingw :confused:.

Hi! Thanks a lot for this contribution! As you can tell from the other open pull request, this project is definitely in need of a good cross-platform build system. I think that CMake is probably the best candidate, and that your pull request is a good start. I'd like to work with you to tailor it to this project.
I really appreciate your contribution back to this project, and I understand that I have little ground to critique work done by others in their own time. That said, I have some comments, which I will place in the code. It would be nice if you could have a look at them, but you are, of course, under no obligation.

That said, I have some comments, which I will place in the code. It would be nice if you could have a look at them, but you are, of course, under no obligation.

I appreciate your feedback and will work towards an implementation we are both comfortable with. That said this one of my CMake templates with some necessary modifications and it didn't get too much love, because I was in a hurry (i.e. no NEON support etc.). Please note that (as stated in the copyright notice) I'm not the author of the TargetArch.cmake script which I haven't touched unitl now.
I think I'll answer the rest of your questions in place.

@aklomp can you estimate when you can answer my questions? I don't want to pressure you, but I'm currently planning my weekend and it would be nice if I can take this into account.

No problem. I don't think I'll be doing much on the project today as I have other plans this evening, and the same is mostly true for tomorrow. (I might have some time to work on this project, but no guarantees.) On Sunday, I actually have to be in the office for a server migration, so I think it's a safe bet to say that I won't be doing much over the weekend. Also, I planned to "comment" in the form of pushing some example code, which takes a bit more time than just typing text.

Status Update
I reworked and simplified quite some bits. Currently all target platform / instruction set detection code is disabled (no third party code anymore :tada:). I included some SIMD instruction set detection code for SSSE3 and AVX2 and an infrastructure skeleton for it located in TargetSIMDInstructionSet.cmake just in case you want to add those checks in the future.
I did some research regarding NEON, but I need an ARM platform in order to check the cmake behavior on that platform and the implications for cross compiling, i.e. that won't be added before my Odroid-C1+ arrives...
Did I forget something?

Just added cmake projects for the test driver and the benchmark.

Looks good, I'll review it on short notice! Do you consider it fit to merge as-is? Don't worry about the NEON stuff, I have a Raspberry Pi 2B which has NEON32 extensions, and I can run NEON64 in an emulator. We can iterate.
Sorry for all the delay btw. Your pull request has been on my radar for the whole time, but I've also been occupied with implementing a faster algorithm (currently in Master), and working on merging OpenMP support (see Issue #9).

Do you consider it fit to merge as-is?

The scripts work well enough for the plain, SSSE3 and AVX2 use cases to be merged :shipit:. And as you said we can will iterate :wink:. I'll probably make (a) new pull request(s) for added OpenMP support and NEON stuff after I passed my exams.

implementing a faster algorithm (currently in Master), and working on merging OpenMP support

Awesome work! :+1:

Just checked out some of your CMake stuff. I'm definitely new at this, but I'm open to learn. I wanted to build the benchmarks with AVX2 support, so I tried this:
cmake -DBASE64_WITH_AVX2=1 .
make
cd test
cmake .
make

This series of commands fails for me. It looks like the generated Makefiles in test/ want to link with a system-wide -lbase64, while they should actually just include ../lib/libbase64.o as an extra object file. Except that that file is not built anymore. Instead there is a libbase64.a in the project root, which exports way too many global symbols. (The list of "allowed" global symbols is in lib/exports.txt.) If I remove the target_link_libraries call in test/CMakeLists.txt and add ../libbase64.a as an extra source file, things break even more. Am I doing something wrong?
Other things I noticed: the bin/base64 binary is not built by default, and make clean no longer fully works. It doesn't purge generated stuff like CMakeFiles/.

FWIW, I managed to compile the tests by adding the following to test/CMakeLists.txt:
find_library(LIBBASE64 libbase64.a ..)
target_link_libraries(${TEST_NAME} ${LIBBASE64})

Well, try this (after you completely cleaned the project dir):
cd /path/to/project/src
mkdir build
cd build

cmake -DBASE64_WITH_AVX2=1 ..
make
make test

Explanation
make clean only removes the build output, but not the build files which were generated by cmake. Because of this and because generating a Makefile in the project root will overwrite your Makefile it is advised to make an out of source build, i.e. create a "build" directory where all the temporary build files reside (this doesn't necessarily have to be a subdirectory of the project root). In this scenario you don't do make clean, but rm -rf build. If you use a project subdirectory like build/ I recommend you adding build/ to your global gitignore file.
Furthermore cmake likes hierarchies, so test/CMakeLists.txt isn't really a separate cmake project which can be used/build on its own. Instead it is called from the root CMakeLists.txt providing the necessary context like where our library is located (FindLibrary(...) will find you your system base64 library...). This also means that the cmake ... command generates one master Makefile in the "build" directory which is used for everything.
One more thing to note: make test will not (re-)build the test executables, it'll only execute them and report whether one of them crashed, but I've included the test executables in the all target, so that they will get rebuild if anything (library sources, executable sources, build files) changes.
Furthermore you probably want to use either ccmake or cmake-gui, because they list all available options and let you easily tweak the compiler arguments.

@aklomp are you still interested in this? If yes I will invest some time updating the build files soon:tm:.

Sorry about the silence, I didn't intend to string you along. I am definitely still interested in cmake integration (because it's the de-facto cross-platform C buildtool), and I think your work is a very good starting point. I also think you tackled all the comments I made previously, so I should do my share. What's preventing me from merging it directly is mostly this:

I'm unfamiliar with cmake, but if I merge this, I would have to support it from now on. This is my problem, not yours, but it means that I need to spend some time learning about it before I can commit to it. I'm a man of many projects and great laziness, so I've been putting it off.

Related: I feel like I do not have the cmake knowledge to grade the quality level of your contribution. I mean, it looks fine, but maybe it's not idiomatic or whatever. I can't really get my finger behind it, which makes me hesitant to accept it. (Again, my problem.)

I'm not sure I like cmake very much. This is totally irrelevant in the light of it being the de-facto cross-platform C buildtool, but it explains something about the points above. I recognize my own bias here.

Maybe this is how we can proceed:

I should spend some time learning about cmake, no excuses.
I can merge the code into a staging branch for the time being, so that it becomes part of the master project, and proceed from there.

I don't like cmake either, but sadly as you said it's a de-facto standard and just works:tm: :smile:

I should spend some time learning about cmake, no excuses.

:+1:

I can merge the code into a staging branch for the time being, so that it becomes part of the master project, and proceed from there.

Yeah, I would like to get this into the upstream project, but I think we should wait with merging until you can maintain the build files yourself. Instead I will watch your repository and keep the cmake files in my fork in sync with the upstream repository. I suggest you add a link in the project description referring to the fork; this way I don't have to open new pull requests every time something changes and people can use the cmake tooling now, so:

I will close this pull request and rename my base64 to base64-cmake and move the cmake files to the master branch
I continue to maintain the cmake files for now
You learn cmake
New pull request + merge of the build files into the upstream repository
You maintain the build files

Are you :ok: with this?

Hi @madebr and @BurningEnlightenment,
Yes, it's high time we find a way to merge this cmake support into master. It's probably the most requested feature, and one of the oldest open issues. After putting it off for more than two years, I have no further excuses to postpone its inclusion.
I have to say that I'm still not familiar with cmake nor do I like the smell of it, which will make it less comfortable to maintain, but I'm willing to make that my problem. Same thing for the necessary changes to README.md- those are on me.
What's left? Apart from the comments above, I ran into these issues:

I noticed that feature/cmake no longer cleanly rebases against the current master.
I tried to build the library using the steps given in a previous comment, but I get a build error because ../../config.h cannot be found. Is that just my setup?

@aklomp
I'm working on it now. Is it ok if I open a new pr and merge with current master instead of rebase?

Let's give @BurningEnlightenment some time to respond first. If it's all the same, I'd like to merge cmake support under this specific issue, because I think the original author deserves some recognition/satisfaction after waiting this long.
You can of course open a new PR for your branch, though we'd be left with two PRs implementing the same basic change. I don't see much harm in it though, and it may be a more natural way to collaborate on any issues with your specific fixes.
As for the merge strategy, my preference is to rebase on master and then merge, because it gives the cleanest history. The log of recent commits for this project show what I have in mind. Each issue has a set of commits implementing one atomic change, and there's a merge commit which ties that branch to master. I'd prefer to follow that approach for this patchset too, because the changes are additive in nature and should compose cleanly on top of the rest of the codebase.

I will of course do my patches on top of his work, so unless you squash the patches no history will be lost.

@aklomp
I have opened https://github.com/BurningEnlightenment/base64-cmake/pull/3 with my suggestions.

Sorry for jumping in the middle, I went straight to the code and noticed the review comments before I even read the discussion here 😅
Anyway, I left my comments here as well, especially regarding installation. @madebr Looks like you wanted to do so anyway, so again, sorry if I interrupted the process, I can delete the review if you'd like me to.
Basically, CMake and Conan support are the only things keeping me from using it in a work project, so I'm glad there's work going on in this area.

@MrPointer
I'm going to open a new pr with my branch + your suggestions next year.
As punishment for not reading my comments before posting, I'm going to tag you for extra review 😉😛
Thanks for the checking on this.
Poking @BurningEnlightenment to see whether (s)he is alive.

@madebr With pleasure 😊

Hi all,
Is this (or any other CMake support) merged into one of the branches of the project?
I would be delighted to use it if this is the case (my project is heavily integrated with CMake).

Thanks @MrPointer and @madebr for reviewing this; I finally got around to clean this up 😌

Should we add some common cmake presets by the way?

Hi everyone.
What's the plan to get cmake support merged? It looks like the latest feedback has been taken into account, and having some support would be nice. It will be easier to iterate on cmake support as the community starts to use it.

@dotnwat Merging cmake support is with me as the maintainer of this project :crying_cat_face:
As I've written earlier in this thread, I feel conflicted about merging this PR because I have hardly any experience with cmake, I don't really understand the changes being introduced, and I'm not confident I can maintain them. The obvious solution to that problem was for me to start learning cmake so I can converse on equal footing. But I still haven't gotten round to it (made it enough of a priority), and I'm sorry about that.
(It's absolutely been on my ongoing mental to-do list for years and causing me quite some anguish as one of those points that you really need to do one day. I didn't just walk away from this. But that's not doing anyone in this thread any good.)
So at a given moment I said I was willing to merge any cmake config that demonstrably works. That offer still stands. So why am I not merging this PR now?

There are several open questions in this thread (mainly by @madebr) which I don't feel qualified to answer.
I can't get cmake to actually compile the library (more below). That makes me back off from merging.
The PR does not include an update to the README to explain how to compile the code with cmake. OK, that's minor and can be fixed later.

So that's basically why it's in limbo. As ashamed as I now am by all of this, I am seriously contemplating just merging everything sight-unseen and sorting out any breakage in later PRs. I tend to agree with you that any support is better than no support, and that once it's mainlined, it can be iterated upon.
Back to the build not working for me. I'm trying to build the code with this set of commands:
cmake -B build
cmake --build build

But I get this build error:
[  5%] Building C object CMakeFiles/base64.dir/lib/lib.c.o
[ 11%] Building C object CMakeFiles/base64.dir/lib/codec_choose.c.o
[ 17%] Building C object CMakeFiles/base64.dir/lib/arch/generic/codec.c.o
lib/arch/generic/codec.c:8:10: fatal error: ../../config.h: No such file or directory
    8 | #include "../../config.h"
      |          ^~~~~~~~~~~~~~~~
compilation terminated.
gmake[2]: *** [CMakeFiles/base64.dir/build.make:104: CMakeFiles/base64.dir/lib/arch/generic/codec.c.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:102: CMakeFiles/base64.dir/all] Error 2
gmake: *** [Makefile:146: all] Error 2

Any clue what I'm doing wrong? What do I need to do to demonstrate for myself that this patchset is good?

One large problem with this PR is that everything is compiled without optimization. The result is that the code is incredibly slow. All the tricks that we do to get good performance (SIMD, fancy algorithms, aggressive inlining) is all for nothing: plain is the fastest codec. Here's part of the benchmark compiled with stock cmake:
Testing with buffer size 100 KB, fastest of 10 * 100
AVX2    encode  146.29 MB/sec
AVX2    decode  137.06 MB/sec
plain   encode  550.22 MB/sec
plain   decode  476.14 MB/sec
SSSE3   encode  135.73 MB/sec
SSSE3   decode  146.43 MB/sec
SSE41   encode  152.59 MB/sec
SSE41   decode  154.20 MB/sec
SSE42   encode  152.85 MB/sec
SSE42   decode  154.21 MB/sec
AVX     encode  158.27 MB/sec
AVX     decode  158.16 MB/sec

Here's what it should look like:
Testing with buffer size 100 KB, fastest of 10 * 100
AVX2    encode  13745.55 MB/sec
AVX2    decode  14467.66 MB/sec
plain   encode  3475.35 MB/sec
plain   decode  3259.66 MB/sec
SSSE3   encode  7606.59 MB/sec
SSSE3   decode  8212.31 MB/sec
SSE41   encode  7603.66 MB/sec
SSE41   decode  8401.14 MB/sec
SSE42   encode  7600.30 MB/sec
SSE42   decode  8211.38 MB/sec
AVX     encode  7996.93 MB/sec
AVX     decode  9094.13 MB/sec

This second run is with a benchmark tool made by the old Makefile, which optimizes at -O3 by default.
This is clearly not something we want. Can cmake be instructed to always optimize to -O3 too?

One large problem with this PR is that everything is compiled without optimization.

CMake has four different build types (Debug, MinSizeRel, RelWithDebInfo and Release) of which it defaults to Debug which as you noticed is an unoptimized build. The other build types have the usual optimization flags set which can also be overriden by the user. You can explicitly specify a build type like so:
cmake -B build -DCMAKE_BUILD_TYPE=Release

I recommend using the more graphical ccmake rather than cmake if you want to inspect/ fiddle with the compiler flags.

@BurningEnlightenment I still think it's reasonable to set -O3 (and the equivalent for MSVC) on all builds, because the library is pretty crap without them. With the default build, you'd be better off using a plain C library than using any of the SIMD codecs. The Makefile also sets -O3 unconditionally, so there's precedence.
I'd like to add it unless it violates a core cmake principal and horrifies the gods.

If there are optimizations that are only available at -O3 then it is reasonable to hard code that for all compilers. I see on my system that -O3 is the default for GCC in cmake (with CMAKE_BUILD_TYPE=Release), but it doesn't look like clang is specifying anything specifically.
You can always use -O3 for everything and let exceptions be handled as they arise.

@BurningEnlightenment I still think it's reasonable to set -O3 (and the equivalent for MSVC) on all builds, because the library is pretty crap without them. With the default build, you'd be better off using a plain C library than using any of the SIMD codecs. The Makefile also sets -O3 unconditionally, so there's precedence.

I'd like to add it unless it violates a core cmake principal and horrifies the gods.

I think we can keep the cmake gods happy by only doing "-O3" when building a Release or RelWithDebInfo config.
Then, we can keep the lower optimization level for Debug builds, so debugging remains easier.
Something as follows: (untested)
if(NOT CMAKE_C_COMPILER_ID STREQUAL "MSVC")
    string(REGEX REPLACE "([/-])O[0-2]" "" CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE}")
    string(REGEX REPLACE "([/-])O[0-2]" "" CMAKE_C_FLAGS_RELWITHDEBINFO "${CMAKE_C_FLAGS_RELWITHDEBINFO}")
    set(CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE } -O3")
    set(CMAKE_C_FLAGS_RELWITHDEBINFO "${CMAKE_C_FLAGS_RELWITHDEBINFO} -O3")
endif()

I am writing a Yocto project recipe for this library and tools and are basing it on the cmake. Because the high level of standardization saves me work. It would be nice to base the recipe of this repo instead of @BurningEnlightenment fork. Can we get it in and then optimize later?

I still think it's reasonable to set -O3 (and the equivalent for MSVC) on all builds, because the library is pretty crap without them.

The purpose of the debug build is that you can debug in a sensible way, so optimizations need to be disabled. If you really need to debug optimized code (and willing to suffer the big pain) there is the RelWithDebInfo flag.
Has anybody seen a significant speedup from -O2 to -O3?

Thanks everyone for your patience, the @BurningEnlightenment cmake branch has finally been merged! I recognize that @htot has a point in asking for the branch to be merged first and incremental improvements to be made later, even though it goes against my perfectionist tendencies :)
Anyway, sorry this took so long. Let's iterate on this in new issues.

I will leave the fork up for a month or two in order to allow people to migrate their CI/ package manager scripts gracefully.
I'd also like to thank everyone involved for the reviews, feedback and contributions 🙂

Happy to see this merged. And great timing; I was just about to put up a PR to modify the relative include paths, as we are using Meson to integrate into our build system and it requires out-of-tree builds.


Rapayment length to update when typing new value

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Bugs:

After entering repayment plan and re-visit the same page, 'Length of repayment plan' label is empty. (Fixed)

Length of repayment plan update the value when selecting radio box frequency only, not when typing different amount value for payment plan too. (Fixed)


Unable to require anything in CoffeeScript or LiveScript

The require functionality seems completely broken as far as I can tell with at least these two languages, and possibly more. Here's the error screens I'm getting:
CoffeeScript
[23:20:01] Failed to load external module coffee-script/register

/home/{user}/dev-projects/js/sandbox/gulpfile.coffee:1
function (exports, require, module, __filename, __dirname) { fs = require 'fs'
                                                                          ^^^^
SyntaxError: Unexpected string
    at Module._compile (module.js:439:25)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Liftoff.handleArguments (/usr/lib/node_modules/gulp/bin/gulp.js:108:3)
    at Liftoff.launch (/usr/lib/node_modules/gulp/node_modules/liftoff/index.js:140:6)
    at Object.<anonymous> (/usr/lib/node_modules/gulp/bin/gulp.js:59:5)
    at Module._compile (module.js:456:26)

LiveScript
(function (exports, require, module, __filename, __dirname) { require! {
                                                                     ^
SyntaxError: Unexpected token !
    at Module._compile (module.js:439:25)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Liftoff.handleArguments (/usr/lib/node_modules/gulp/bin/gulp.js:108:3)
    at Liftoff.launch (/usr/lib/node_modules/gulp/node_modules/liftoff/index.js:140:6)
    at Object.<anonymous> (/usr/lib/node_modules/gulp/bin/gulp.js:59:5)
    at Module._compile (module.js:456:26)

JS does not have this issue, but it seems like a bug that both CoffeeScript and LiveScript should fail in exactly the same spot (namely the beginning require phase).

For anyone coming across an issue with the
Failed to load external module coffee-script/register

issue, check if you indeed have coffee-script installed:
$ npm ls coffee-script
<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
If you have it installed, delete the node_modules folder, and rerun your install:
$ npm install

Working fine on this end: https://github.com/tkellen/gulp-with-coffee-script

ye, it's something weird with the order you install coffee-script / run gulpfile.coffee. I just had this issue with a new repo that I didn't have yesterday on another repo.
Just a note should someone not know how to quickly resolve it.

Sorry about reopening here, but I got the same error: Requiring external module coffee-script/register. I tried above suggestions, but no dice. Coffee-script is local in node_modules and also globally installed and removed and reinstalled the node_modules<EMAIL_ADDRESS>and<EMAIL_ADDRESS>


Delete /xp-related messages

The bot is too spammy, delete /xp requests and responses after 2 minutes

Fixed in v1.1.0


DPL-nnn [BUG] Traction releases don't appear to cache-bust

Describe the bug
Upon making a traction release, the browser (in my case Vivaldi, but I'm assuming at least chrome) continues to serve the cached version of the assets. We should implement some form of cache busting to overcome this. Adding the release tag as a query parameter on fetching the js would probably be the easiest solution, although may be worth seeing if vue-cli provides anything to help.
RT Ticket Number
If applicable
To Reproduce
Steps to reproduce the behaviour:

Go to page '...'
Click on button '...'
See error

Expected behaviour
What was expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

Windows or Mac?
Browser Chrome, Firefox, Safari or other?
Browser version (use 'About' to look up)?

Additional context
Add any other context about the problem here.

@JamesGlover Is this still relevant? I think you added some kind of caching?


Can not download any models?

Thanks for sharing the code. Nice work.
I can not open any link of onedirve. They all show:

I can still open it, please check if it's your network's problem?

It works! Thanks a lot.


Storage\SymfonySession is not aware of AttributeBag

from https://github.com/gigablah/silex-oauth/issues/19#issuecomment-94712064
I am registering an AttributeBag
$app['session']->registerBag(
    new \Symfony\Component\HttpFoundation\Session\Attribute\AttributeBag('fooBar')
);

This leads to storage/retrieval fails when it comes to use the SymfonySession. To fix it i was in need to use $this->session->getBag('attributes')->doo() for every call to the session in https://github.com/gigablah/silex-oauth/blob/master/src/Gigablah/Silex/OAuth/Storage/SymfonySession.php#L43-43
IMO the underlying storage should be aware of the attribute bag but unfortunately it is not.
Do i use it wrong or do i need to fix the SymfonySession that way ?

Unfortunately registering a custom AttributeBag with the session object does not change the bag that it retrieves values from when you call Session::get. The AttributeBag must be passed into the session constructor: https://github.com/symfony/HttpFoundation/blob/master/Session/Session.php#L59
What you can do is override $app['session'] when registering the SessionServiceProvider and construct your own Session object. The AttributeBag should be passed in as the second argument to the constructor.

Actually i tryed exactly that and it works. Thank you :+1: But i am curious what it does not work. The AttributeBag is registered using the default name attributes . I think when i call registerBag it should overwrite the default AttributeBag registered on the name attributes but it does not ?

Yes that's true. You could check whether your previous registerBag code somehow happens after the session is read. Considering how Pimple works you might have triggered early instantiation somewhere. In fact, try using $app->extend() on the session object.

Alright, thanks for your explanation & advice! I am using now $app->extend() and it works as expected.
Thanks for the project :+1:


/bin/sh: 1: nvcc: not found

I got an error when I run the sampler in my ubuntu PC:
'''
/bin/sh: 1: nvcc: not found
File "/PyDPM4.0.1/pydpm/sampler/distribution_sampler_gpu.py", line 99, in init
dll = ctypes.cdll.LoadLibrary(compact_path)
File "/anaconda3/envs/pydpm/lib/python3.6/ctypes/init.py", line 426, in LoadLibrary
return self._dlltype(name)
File "anaconda3/envs/pydpm/lib/python3.6/ctypes/init.py", line 348, in init
self._handle = _dlopen(self._name, mode)
OSError:/PyDPM4.0.1/pydpm/sampler/_compact/distribution_sampler.so: cannot open shared object file: No such file or directory
'''
I'm green to this, how can I deal with it
Thank you

It's lack of .so file. Make sure that nvcc is in you system's path, then when you rerun the sampler code, those .cu/.h/.c files will be compiled automaticly. If not, plz click here https://github.com/BoChenGroup/PyDPM/issues/16#issuecomment-1384034217 for reference

solved


Feature: generate ROS2 compatible type naming

Fixes https://github.com/eProsima/Fast-RTPS-Gen/issues/19. @LuisGP thank you for the tips. Please check if this solution makes sense to you:

-typeros2 option sets m_type_ros2 to true, which is defined in the Context;
If isGenerateTypesROS2 is true,  meaning m_type_ros2, then it's used a scoped name generated from the IDL parser, which has the required valid structure to be used in the ROS2 context.

Requires https://github.com/eProsima/IDL-Parser/pull/39 to be merged first.

@TSC21 Please, update the IDL-Parser submodule and I'll approve the PR.

@TSC21 Please, update the IDL-Parser submodule and I'll approve the PR.

Ah yws of course. Will do

Please, update IDL parser submodule to the master's commit.

@LuisGP @richiware thank you both. This will definitely improve the experience for people using standalone Fast-RTPS apps linked in the same DDS domain as ROS2 nodes.
Before you do a release, I would like to add as a feature an option to install the script and binary system wide (in /usr/local for example), making a new PR. Is that something you can wait for or are you pushing to a 1.0.4 release already?

@LuisGP @richiware thank you both. This will definitely improve the experience for people using standalone Fast-RTPS apps linked in the same DDS domain as ROS2 nodes.
Before you do a release, I would like to add as a feature an option to install the script and binary system wide (in /usr/local for example), making a new PR. Is that something you can wait for or are you pushing to a 1.0.4 release already?

@MiguelCompany this message is for you :P.

@MiguelCompany @LuisGP @richiware are you planning to document this?


Method guard State.setRows

When consuming the table, I set rows to null when there are no rows present, so need the rows to be cleared. This is especially the case when the rows have not been initialized.
This causes a flow on affect in DataTableBody.ngOnInit() where reading the rows causes an exception.

Hmmm, by setting them to null wouldn't that de-reference the array? In the examples, I specifically make them not splice into the current one to prevent this.
I'm ok with the change to have this ability, just wanna make sure we don't break anything.

IMHO this way is more valid - it should always reset the reference of the array when we call setRows(). It will help later, if we want to change angular2-data-table to not mutate the data. (currently it mutates it - by f.e. adding $index attributes to the each row's object)
If we want to remember the each row's value, we should use trackBy or something like that.

What do you mean  Right now it's being deferenced anyway? I'm not doing that anywhere.
Ya, it works fine if you put an empty array.

@amcdnl @jtomaszewski - I certainly could put the datatable inside an *ngIf and not display the table, the issue is that a null or undefined could set the rows property and the rows property is not initialized see https://github.com/swimlane/angular2-data-table/blob/master/src/services/State.ts#L16 hence if rows is not initialized to an empty array then this throw an exception https://github.com/swimlane/angular2-data-table/blob/master/src/components/body/Body.ts#L100

Hey @amiller29au , can you tell if it has been fixed by https://github.com/swimlane/angular2-data-table/commit/d10dcd133eeb75aa22a012570557296101224b08 ?

It possibly will, but what action should be taken if for whatever reason someone passes null or undefined?

IMHO it should raise an error (that's an invalid value).
Currently it does nothing.
It could as well set the rows to empty array.

@jtomaszewski , @amcdnl - what is the outcome of method guarding StateService.setRows() ?
Should the rows be reset to an empty array, rather than the value ignored?

I'm hoping to address this in a rewrite of inputs to make it reactive. I'm going to close this for now.


Add support for Linuxbrew.

Fix https://github.com/tboox/xmake/issues/295

Modified per suggestion.

Merged, thanks!
And please commit code to dev branch next time.

Sorry, I'll be more careful next time.


refactor workspace repository handling

motivation: make supporting registry depedencies easier
changes:

rename LocalPackageContainer to FileSystemPackageContainer and move it to workspace module as internal struct
rename RepositoryPackageContainer to SourceControlPackageContainer and move it to the workspace module as internal class
remove RepositoryPackageContainerProvider and move its logic to workspace itself, including the logic to switch over dependecy type (local/remote) and providing the correct container type
conform workspace to PackageContainerProvider and change getContiner call-sites to use it
reorgnize repository related methods in a consistent manner so its easier to read the code that deals with repositories
adjust call sites and tests

rdar://81621441

@mattt this addresses some of your questions and takes some of your ideas from #3640, in effort to make it simpler (I hope!) to add registry support. lmk what you think

needs #3698 first

@swift-ci please smoke test

@tomerd Thanks so much for the "paint by numbers" comments to help guide my implementation 😄. I'll rebase #3640 against this and let you know when I'm finished.

@swift-ci please smoke test


Bug fix

Someone sent me a PR that fixes a bug that I introduced after merging in OpenGov's changes.  So I'm sending you a PR for you to add to your PR to OpenGov.

Cool! Thanks @Mashi


Convert from terraform to python fails with code generation error

What happened?
Attempted to convert terraform repo to pulumi using:
pulumi convert --from terraform --language python
but received the following error:
The Pulumi CLI encountered a code generation error. This is a bug!
We would appreciate a report: https://github.com/pulumi/pulumi/issues/
Please provide all of the below text in your report.

Pulumi Version:   v3.140.0

error: main.pp:60,1-63,2: /tmp/pulumi-convert934795143/modules/s3/iam.pp:1,76-90: unknown property 'ses_policy' among [sesPolicy bucketName ignorePublicAcls projectTag eventbridgeNotification restrictPublicBuckets s3Notification blockPublicAcls blockPublicPolicy bucketKeyEnabled]; , and 1 other diagnostic(s); /tmp/pulumi-convert934795143/modules/s3/iam.pp:1,76-90: unknown property 'ses_policy' among [sesPolicy bucketName ignorePublicAcls projectTag eventbridgeNotification restrictPublicBuckets s3Notification blockPublicAcls blockPublicPolicy bucketKeyEnabled]; , and 1 other diagnostic(s)
error: main.pp:65,1-71,2: /tmp/pulumi-convert934795143/modules/lambda/schedule.pp:8,60-73: unknown property 'functionName' among [replacementSecurityGroupIds runtime signingProfileVersionArn skipDestroy sourceCodeSize packageType urn arn codeSigningConfigArn environment lastModified reservedConcurrentExecutions s3ObjectVersion ephemeralStorage imageUri memorySize publish qualifiedArn sourceCodeHash tags version architectures deadLetterConfig invokeArn layers snapStart vpcConfig codeSha256 description handler s3Bucket s3Key kmsKeyArn loggingConfig tagsAll timeout imageConfig name role signingJobArn tracingConfig id code fileSystemConfig qualifiedInvokeArn replaceSecurityGroupsOnDestroy]; ; /tmp/pulumi-convert934795143/modules/lambda/schedule.pp:8,60-73: unknown property 'functionName' among [replacementSecurityGroupIds runtime signingProfileVersionArn skipDestroy sourceCodeSize packageType urn arn codeSigningConfigArn environment lastModified reservedConcurrentExecutions s3ObjectVersion ephemeralStorage imageUri memorySize publish qualifiedArn sourceCodeHash tags version architectures deadLetterConfig invokeArn layers snapStart vpcConfig codeSha256 description handler s3Bucket s3Key kmsKeyArn loggingConfig tagsAll timeout imageConfig name role signingJobArn tracingConfig id code fileSystemConfig qualifiedInvokeArn replaceSecurityGroupsOnDestroy];
error: could not generate output program

Example
See above for full error details
Output of pulumi about
CLI
Version      3.140.0
Go Version   go1.23.3
Go Compiler  gc

Host
OS       ubuntu
Version  22.04
Arch     x86_64

Backend
Name           pulumi.com
URL            https://app.pulumi.com
User           Unknown
Organizations
Token type     personal

Pulumi locates its logs in /tmp by default
warning: Failed to read project: no Pulumi.yaml project file found (searching upwards from /home/sagemaker-user/ops-radar-infra). If you have not created a project yet, use `pulumi new` to do so: no project file found
warning: Failed to get information about the current stack: no Pulumi.yaml project file found (searching upwards from /home/sagemaker-user/ops-radar-infra). If you have not created a project yet, use `pulumi new` to do so: no project file found

Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

I have also encountered this error but when attempting to bridge a provider and using codegen for the examples. When attempting with the provider in my scenario I get
unknown property 'defaults_version' among [... defaultsVersion ...]. This example will be dropped from any generated docs or SDKs.
When running in a debugger, I see this is happening for a UnionType. I am not sure if this is incorrect, but looking further in the debugs, YAML and Java seem to succeed, while python, go, typescript, and C# get reported as failed conversions.
When looking at the evaluation at https://github.com/pulumi/pulumi/blob/cf6fd7534845cb47743d205177090bf0b67e3a55/pkg/codegen/hcl2/model/type_object.go#L110 propertyName is defaults_version while t.Properties only contains the camel case equivalent defaultsVersion

I wasn't able to push a branch to this repo, but I was able to repro the issue and write a test for it here

Fixed by https://github.com/pulumi/pulumi-converter-terraform/pull/235.
Released in https://github.com/pulumi/pulumi-converter-terraform/releases/tag/v1.0.20


Welcome, KS & FL 🍍

Got KS & FL full integrated into the pipeline now! Historic data & in the main pipeline. Yay! You should be able to just run scmake() and create the image below (should take a few hours, not a few days!) Fixes #9

I don't know what is going on with the sites who are in the top left, will dig into that later but it looks cool :)

When I run scmake() I get this error
 Error in parse_aws_s3_response(r, Sig, verbose = verbose) :
  Moved Permanently (HTTP 301). ```

The resulting svg output has several <g> elements with transform="translate(NA NA). I suspect these are the same sites  in the upper left corner of the output. These seem to be crashing vue when the output svg is used as a standalone component

Merging, but noted that translate(NA NA) problem in #25


Updating _ to -in lib.rs. Also updating loading from rdb to use a trait instead

General refactoring changes to use a trait instead for RDB loads will eventually also have trait be updated for valkey save as well.

Thanks, looks good.


Use zulip topic permalinks

When generating links to Zulip topics, currently the link changes when the topic gets renamed. With https://github.com/zulip/zulip/issues/21505 Zulip has topic permalinks; ideally the bot would use those so that the link remains stable even if the topic gets renamed (e.g. when it gets "marked as resolved").

Is there a link/description of the link syntax? Skimming that issue I didn't see an obvious description. https://github.com/rust-lang/triagebot/blob/989e03c399b3deb1be23b416196f3d1214fc7a12/src/zulip.rs#L356-L376 is where we generate the URLs I think, so that's what would need updating.

The syntax involves #narrow/channel/{channel_id}/topic/{encoded_topic}/with/{anchor_message_id}. It's not available in Zulip Cloud yet (ETA: 1-2 weeks), so you can't use it yet.
We are still working through some bugs and then documenting it, and are not currently making use of it because we want to wait until mobile clients upgrade, since while the latest mobile apps support it, the links will not function for folks whose phones haven't updated yet. So we probably won't make the markdown processor generate them for **stream>topic** syntax for a few weeks after we make the server/web app start support processing them to wait for clients to upgrade, but we'd be excited to have folks test and shake out any bugs.

https://chat.zulip.org/api/construct-narrow#narrows-that-use-ids has v0 API docs already available, but we're planning to rewrite those over the next couple of days to be nicer.


Support class-based membership inference

Currently blackbox membership inference attack treats all data in the same manner, training a single attack model for everything.
If true labels are provided, the attack can create separate attack models per class label (which has been shown to improve attack accuracy).

Closing because of inactivity, please reopen if still current.


⚠ Bofrost.at has degraded performance

In fb69297, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2426 ms

Resolved: Bofrost.at performance has improved in a10de6e.


style: Format MDX files with Prettier.

Replacement for the #1995.

Using Percy for this is amazing - I left comments on the view pages where something weird happened. (Can I make these review visible here in GH somehow?)

Using Percy for this is amazing - I left comments on the view pages where something weird happened. (Can I make these review visible here in GH somehow?)

I know only this one, so far it was enough for me :)

Oh nice, I did not notice that. Sweet.

@janpio I couldn't reply in the percy.io, so I add comments here.
Also, not sure why some text got screwed, or some images not loading properly. Maybe it's worth to ask them by Intercom?

Added an issue for the image problem: https://github.com/prisma/docs/issues/2041

Wheeee @umidbekk!


Entity "updater.updater" not found

After install the default Tileboard page states: Entity "updater.updater" not found
How can I remove this? The updater.updater doesn't exist anymore I think.

 Off course. Was looking at it al wrong :)
Thanks!


feat: add Keyboard Cheatsheet

⚠ This continue #1309, which was long was inactive. ⚠
How it looks:

Last things:

[x] Change description for ⬇ and ⬆

If it is possible:
~- [ ] Create Cypress e2e test~
Closes https://github.com/electron/electronjs.org/pull/1309

@electron/wg-website it's ready for review.

Closing the modal with the escape key jumps focus to the search bar

All keys in modal dialog blocked, besides Esc.

Typing ? in the app search field focuses the search box

Looks like error here: https://github.com/electron/electronjs.org/blob/b03139a679268ac6a94b71dadaa0f23fd9d96ff0/scripts/modal.js#L11
but it expected behavior, very intresing.

Can we use addEventListener here or is there a reason to use onclick (same question for window.onclick below)

Yup, done 💯.

How would you feel about using a different ID here? Something like keyboard-reference-modal or something?

Changed to kb-shortcut-dialog

How would you feel about including ? in this, so it could be toggled?

I agreede make this toggleable, but it has one problem we going to infinity loop opening and closing modal, I think it can wait.

Typing ? in the app search field focuses the search box

I think this problem is originating from https://github.com/electron/search-with-your-keyboard

@BinaryMuse Is it ready for merge, or more propositions or bugs?

@HashimotoYT I think this is good to go! ✨

Thanks for getting this across the finish line 🏁


register by using maven artifact ,group and version

1.) Provide application register option using maven artifact ,group and version.
2.) The version dialog may propose optional dropdown with available version (mots recent on top)
3.) The artifact is downloaded via maven from repository.
4.) Save configuration history for registered application's arifact
5.)Configure destination path for downloaded artifacts

Hi @cforce, this doesn't accomodate on the project right now. Thanks for your ideas.

Not sure why you think such way. For many teams sharing my Microservice landscape one team might need another teams Microservice to be started for their integration test but don't need to pull it from source but use the jar artifact.
To start a spring boot app from jar you can use the same mechanism as you do now from sec, so it's just another context.

Sure, I am not saying it is a bad idea. The thing is that we need to optimize our resources and there are more priority tasks right now. I have it on backlog but will not be implemented on the near future. Thanks & Cheers!


Merge alpha into master

Gravitee.io Automatic Deployment
🚀 A prerelease version of this package has been published on Gravitee's private artifactory, you can:

use it directly by updating your project with version: 2.0.0-merge-alpha-into-master-SNAPSHOT
download it from Artifactory here

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

2.0.0
GitHub release

Your semantic-release bot :package::rocket:


link to mediacommon

Codecov Report

Merging #223 (9b841d5) into main (af3ed2b) will decrease coverage by 1.03%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #223      +/-   ##
==========================================
- Coverage   86.98%   85.95%   -1.03%
==========================================
  Files         102       81      -21
  Lines       10700     8699    -2001
==========================================
- Hits         9307     7477    -1830
+ Misses       1073      949     -124
+ Partials      320      273      -47

Impacted Files
Coverage Δ

pkg/formats/h264.go
73.22% <ø> (ø)

pkg/formats/mpeg4_audio.go
93.54% <ø> (ø)

pkg/formats/rtph264/decoder.go
81.60% <ø> (ø)

pkg/formats/rtph264/encoder.go
94.67% <ø> (ø)

pkg/formats/rtph265/decoder.go
72.22% <ø> (ø)

pkg/formats/rtpmjpeg/decoder.go
87.28% <ø> (ø)

pkg/formats/rtpmjpeg/encoder.go
54.16% <ø> (ø)

pkg/formats/rtpmpeg4audio/decoder.go
80.76% <ø> (ø)

pkg/formats/rtpmpeg4audio/encoder.go
96.64% <ø> (ø)

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Option to slow down danmakus?

Is your feature request related to a problem? Please describe.
Sometimes they can get a bit too fast.
Describe the solution you'd like
Could you please add a speed option in the settings, that lets us input a number or move a slider?

Oh thanks, I never type my own danmakus so I didn't realize that's where I needed to look ^^ I'd say it might be easier to find in the extension menu (when you left-click the icon), but at least for me I'll now know where it is!


How can i build for x64 steamclient64.dll?

Hi😅, current now i'm try to use Lib with project "SAM.API" but it's not support on x64 build
so how can i integrate to my Project and my mod game is use steamclient64.dll
thanks

You would be better served using something like Steamworks.NET than attempting to use SAM.API.

thanks you bro, it's work 👍👍


[PERFORMANCE] [master] Layer normalization code from Marian for CPU

Description
This is the master version of #19601.  There isn't much different in LayerNormalization implementation between v1.x and master.
Checklist
Essentials

[x] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage; already covered by unittest for layer normalization.
[x] Code is well-documented

Changes

[x] Copy Marian optimized CPU LayerNorm implementation and adapt to MXNet.
[x] Refactor dispatch of optimized versions using bool return value.
[x] Remove MKL call

Comments
See #19601 for benchmarks.

@mxnet-bot run ci [unix-cpu, website, windows-cpu, windows-gpu]
Playing more CI docker daemon lottery.

Failed test on edge appears to be #19630.

Passing all tests except for edge which is broken per #19630..

Passing all tests except for edge which is broken per #19630..

Retriggered after fix was completed, looks like its passing now.

@mxnet-bot run ci [unix-gpu]
Out of memory lottery [2020-12-21T12:32:00.010Z] c++: fatal error: Killed signal terminated program cc1plus

@mxnet-bot run ci [centos-cpu]
Don't see how tests/python/unittest/test_sparse_operator.py::test_sparse_unary_with_numerics is related.
[2020-12-21T12:56:11.413Z] Fatal Python error: Aborted
[2020-12-21T12:56:11.413Z]
[2020-12-21T12:56:11.413Z] Thread 0x00007f1190ea2700 (most recent call first):
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/execnet/gateway_base.py", line 400 in read
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/execnet/gateway_base.py", line 432 in from_io
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/execnet/gateway_base.py", line 967 in _thread_receiver
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/execnet/gateway_base.py", line 220 in run
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/execnet/gateway_base.py", line 285 in _perform_spawn
[2020-12-21T12:56:11.413Z]
[2020-12-21T12:56:11.413Z] Current thread 0x00007f1192b76740 (most recent call first):
[2020-12-21T12:56:11.413Z]   File "/work/mxnet/python/mxnet/autograd.py", line 269 in backward
[2020-12-21T12:56:11.413Z]   File "/work/mxnet/python/mxnet/executor.py", line 213 in backward
[2020-12-21T12:56:11.413Z]   File "/work/mxnet/python/mxnet/test_utils.py", line 1394 in check_symbolic_backward
[2020-12-21T12:56:11.413Z]   File "/work/mxnet/tests/python/unittest/test_sparse_operator.py", line 1502 in check_sparse_simple
[2020-12-21T12:56:11.413Z]   File "/work/mxnet/tests/python/unittest/test_sparse_operator.py", line 1518 in check_sparse_function
[2020-12-21T12:56:11.413Z]   File "/work/mxnet/tests/python/unittest/test_sparse_operator.py", line 1523 in test_sparse_unary_with_numerics
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/_pytest/python.py", line 184 in pytest_pyfunc_call
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/callers.py", line 187 in _multicall
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/manager.py", line 87 in <lambda>
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/manager.py", line 93 in _hookexec
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/hooks.py", line 286 in __call__
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/_pytest/python.py", line 1627 in runtest
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/_pytest/runner.py", line 163 in pytest_runtest_call
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/callers.py", line 187 in _multicall
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/manager.py", line 87 in <lambda>
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/manager.py", line 93 in _hookexec
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/hooks.py", line 286 in __call__
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/_pytest/runner.py", line 256 in <lambda>
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/_pytest/runner.py", line 310 in from_call
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/_pytest/runner.py", line 256 in call_runtest_hook
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/flaky/flaky_pytest_plugin.py", line 138 in call_and_report
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/_pytest/runner.py", line 127 in runtestprotocol
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/_pytest/runner.py", line 110 in pytest_runtest_protocol
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/flaky/flaky_pytest_plugin.py", line 94 in pytest_runtest_protocol
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/callers.py", line 187 in _multicall
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/manager.py", line 87 in <lambda>
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/manager.py", line 93 in _hookexec
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/hooks.py", line 286 in __call__
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/xdist/remote.py", line 87 in run_one_test
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/xdist/remote.py", line 70 in pytest_runtestloop
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/callers.py", line 187 in _multicall
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/manager.py", line 87 in <lambda>
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/manager.py", line 93 in _hookexec
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/hooks.py", line 286 in __call__
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/_pytest/main.py", line 313 in _main
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/_pytest/main.py", line 257 in wrap_session
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/_pytest/main.py", line 306 in pytest_cmdline_main
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/callers.py", line 187 in _multicall
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/manager.py", line 87 in <lambda>
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/manager.py", line 93 in _hookexec
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pluggy/hooks.py", line 286 in __call__
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/xdist/remote.py", line 237 in <module>
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/execnet/gateway_base.py", line 1084 in executetask
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/execnet/gateway_base.py", line 220 in run
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/execnet/gateway_base.py", line 285 in _perform_spawn
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/execnet/gateway_base.py", line 267 in integrate_as_primary_thread
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/execnet/gateway_base.py", line 1060 in serve
[2020-12-21T12:56:11.413Z]   File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/execnet/gateway_base.py", line 1554 in serve
[2020-12-21T12:56:11.413Z]   File "<string>", line 8 in <module>
[2020-12-21T12:56:11.413Z]   File "<string>", line 1 in <module>
[2020-12-21T12:56:11.667Z] tests/python/unittest/test_sparse_operator.py::test_sparse_unary_with_numerics
[2020-12-21T12:56:11.667Z] [gw1] node down: Not properly terminated
[2020-12-21T12:56:16.898Z] [gw1] [ 93%] FAILED tests/python/unittest/test_sparse_operator.py::test_sparse_unary_with_numerics
[2020-12-21T12:56:16.898Z]
[2020-12-21T12:56:16.898Z] replacing crashed worker gw1
[2020-12-21T12:56:16.898Z]

@mxnet-bot run ci [unix-cpu]
Memory roulette.
[2020-12-21T12:39:34.723Z] c++: fatal error: Killed signal terminated program cc1plus

GPU is being flaky and CPU keeps running out of RAM @mxnet-bot run ci [unix-cpu, unix-gpu]
[2020-12-21T14:33:56.005Z] tests/python/gpu/test_operator_gpu.py::test_countsketch FAILED           [ 19%]

[2020-12-21T14:33:56.564Z] tests/python/gpu/test_operator_gpu.py::test_multi_sum_sq FAILED          [ 20%]

[2020-12-21T14:33:57.486Z] tests/python/gpu/test_operator_gpu.py::test_fast_lars FAILED             [ 20%]

[2020-12-21T14:33:57.740Z] tests/python/gpu/test_operator_gpu.py::test_batchnorm_with_type FAILED   [ 21%]

[2020-12-21T14:33:58.297Z] tests/python/gpu/test_operator_gpu.py::test_batchnorm_versions FAILED    [ 21%]

[2020-12-21T14:33:58.297Z] tests/python/gpu/test_operator_gpu.py::test_convolution_with_type FAILED [ 22%]

[2020-12-21T14:33:58.297Z] tests/python/gpu/test_operator_gpu.py::test_convolution_options SKIPPED  [ 22%]

[2020-12-21T14:33:58.854Z] tests/python/gpu/test_operator_gpu.py::test_conv_deconv_guards FAILED    [ 23%]

[2020-12-21T14:33:59.108Z] tests/python/gpu/test_operator_gpu.py::test_convolution_large_c FAILED   [ 23%]

[2020-12-21T14:33:59.362Z] tests/python/gpu/test_operator_gpu.py::test_deconvolution_large_c FAILED [ 24%]

[2020-12-21T14:33:59.362Z] tests/python/gpu/test_operator_gpu.py::test_convolution_versions FAILED  [ 24%]

[2020-12-21T14:33:59.615Z] tests/python/gpu/test_operator_gpu.py::test_pooling_nhwc_with_convention FAILED [ 25%]

[2020-12-21T14:33:59.869Z] tests/python/gpu/test_operator_gpu.py::test_pooling_with_type FAILED     [ 25%]

[2020-12-21T14:34:00.123Z] tests/python/gpu/test_operator_gpu.py::test_deconvolution_with_type FAILED [ 26%]

[2020-12-21T14:34:00.376Z] tests/python/gpu/test_operator_gpu.py::test_deconvolution_options FAILED [ 26%]

[2020-12-21T14:34:00.630Z] tests/python/gpu/test_operator_gpu.py::test_pooling_versions FAILED      [ 27%]

[2020-12-21T14:34:00.883Z] tests/python/gpu/test_operator_gpu.py::test_flatten_slice_after_conv FAILED [ 27%]

[2020-12-21T14:34:01.137Z] tests/python/gpu/test_operator_gpu.py::test_global_pooling FAILED        [ 28%]

[2020-12-21T14:34:01.391Z] tests/python/gpu/test_operator_gpu.py::test_psroipooling_with_type FAILED [ 28%]

[2020-12-21T14:34:01.644Z] tests/python/gpu/test_operator_gpu.py::test_deformable_psroipooling_with_type FAILED [ 29%]

[2020-12-21T14:34:01.898Z] tests/python/gpu/test_operator_gpu.py::test_deformable_convolution_with_type FAILED [ 29%]

[2020-12-21T14:34:02.819Z] tests/python/gpu/test_operator_gpu.py::test_sequence_reverse FAILED      [ 30%]

[2020-12-21T14:34:02.820Z] tests/python/gpu/test_operator_gpu.py::test_autograd_save_memory FAILED  [ 30%]

[2020-12-21T14:34:03.073Z] tests/python/gpu/test_operator_gpu.py::test_cuda_rtc FAILED              [ 31%]

[2020-12-21T14:34:03.327Z] tests/python/gpu/test_operator_gpu.py::test_cross_device_autograd FAILED [ 31%]

[2020-12-21T14:34:03.581Z] tests/python/gpu/test_operator_gpu.py::test_multi_proposal_op FAILED     [ 32%]

@mxnet-bot run ci [unix-cpu]
Memory gambling is annoying.

@mxnet-bot run ci [unix-cpu]
Still just running out of RAM compiling numpy kernels.  https://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-cpu/detail/PR-19602/19/pipeline/

One naming issue. Looks good to me.

What are the next steps for this PR? Is this ready to be merged?

What are the next steps for this PR? Is this ready to be merged?

@fhieber I've just merged. Feel free to try it out.

@fhieber I've just merged. Feel free to try it out.


Please add support to have multiple Slack Notifications

I believe this is related to #349 but here is also an implementation suggestion that I think will work for many.
My main problem is that I want to message our #developers channel in case of success or failure, but I also want to message our #test channel in case of a successful build so that they can begin testing it.
Maybe it could be possible to add a comma separated custom channel list for each of these?
Notify Build Start
Notify Success
Notify Aborted
Notify Not Built
Notify Unstable
Notify Regression
Notify First Failure Only
Notify Repeated Failure Only
Notify Back To Normal
Include Test Summary
Include Failed Tests
Include Custom Message

@jensolsson If you have a Jenkins Pipeline job you can run in the post {} section depending on the job status, e.g.:
post {
  success {
    slackSend(channel: "#qa", message: "job finished")
  }
  unstable {
    slackSend(channel: "#qa", message: "tests failed")
  }
  failure {
    slackSend(channel: "#devops", message: "internal error")
  }
}


Avoid spurious warning on kbfstool run

Condition the warning on rpc.StartingNonFirstConnection,
similar to other implementations of OnDisconnected.

Appveyor failure looks like https://keybase.atlassian.net/browse/KBFS-1736


sizeof-agent.jar not reported in HTML output using CLI v1.4.2

The sizeof-agent.jar is not being included in the HTML output when using v1.4.2 of the CLI. It was previously included in v1.4.0 and earlier. The sizeof-agent.jar is a transitive library to ehache and is currently not vulnerable.
The attached TestApp.war (named TestApp.war.txt so that it could be uploaded) file contains two libraries: ehcache-core-2.6.12-20160203.011908-43 and commons-collections-<IP_ADDRESS>. This file can be used as a test sample to demonstrate the issue. Also attached are log files generated by v1.4.2 and v1.4.0.
test_1-4-0.txt
test_1-4-2.txt
TestApp.war.txt

Sorry for the delay on this. A reset() was missed when we added the ability to scan fully executable JAR files (from spring-boot). This has been resolved in the snapshot version and will be included in the next release.


Extract HTTP method override to middleware

I can tackle this today unless you've already started. Let me know.


Just one of the html files open

it will open one of my .html files, any other .html file doesn't open

Did you figure this out? Does the browser, open a new tab with other .html files, or does any other program?

Well, I have gave up it for several months, thanks anyway