goal.js adds a trailing dash to goal names

For example:
goal('exp-x-test'); tracks exp-x-test-

Hey Beau,
I think this is happening because you need to be passing two arguments: exp-x as the first string and the goal string as the second.
TH

I thought by binding it to a property I could just pass in the goal string, which in this case is 'exp-x-test'.
const goal = require('clearhead/goal').bind(null, 'prop13');
goal('exp-1-initiative-click-mlp-logo-click');

Maybe
const goal = require('clearhead/goal').bind(null, 'prop13', 'exp-1');
goal('initiative-click-mlp-logo-click');
On Fri, Sep 18, 2015 at 10:32 AM, beaulm<EMAIL_ADDRESS>wrote:

I thought by binding it to a property I could just pass in the goal
string, which in this case is 'exp-x-test'.
const goal = require('clearhead/goal').bind(null, 'prop13');
goal('exp-1-initiative-click-mlp-logo-click');
—
Reply to this email directly or view it on GitHub
https://github.com/clearhead/clearhead/issues/20#issuecomment-141483856.

--
Tom Fuertes |<PHONE_NUMBER>
http://www.linkedin.com/in/tomfuertes

Maybe
const goal = require('clearhead/goal').bind(null, 'prop13', 'exp-1');
goal('initiative-click-mlp-logo-click');

As a temporary work around us that. I'll patch shortly b/c label is supposed to be optional but not working that way

And that'll work ok with Omniture/SiteCatalyst?

Should right?
https://github.com/clearhead/clearhead/blob/master/src/goal.js#L48

Fixed in https://github.com/clearhead/clearhead/commit/aef6c590a76b997f9f5cfc024af5c7b855a5cb34

Bumped 0.0.34 in clearhead-experiments - can you re npm install and confirm it's working as expected?

Yup, looks better!


Prepare for 10.0.0~pre2 Release

🎈 Release
Preparation for 10.0.0~pre2 release.
Comparison to 10.0.0-pre1: https://github.com/gazebosim/gz-msgs/compare/gz-msgs10_10.0.0-pre1...gz-msgs10

Needed by <PR(s)>
Checklist

[ ] Asked team if this is a good time for a release
[ ] There are no changes to be ported from the previous major version
[ ] No PRs targeted at this major version are close to getting in
[ ] Bumped minor for new features, patch for bug fixes
[ ] Updated changelog
[ ] Updated migration guide (as needed)
[ ] Link to PR updating dependency versions in appropriate repository in gazebo-release (as needed):

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

Merging without windows.


fix: page titles

fix: added title parameter for webpage title tag
refactor: converted to yaml

:tada: This PR is included in version 1.8.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Automatically use any global YAML data when rendering a component

I'm cutting the concept of "globals". Just import a layout component into another one and be explicit about component relationships. This works better for parity between FS and DB component getters, too.


Cache mermaid graph rendering

See #1021.
When typing text in a Markdown cell, the graph definition doesn't change, so we now cache the rendered SVG.
I also noticed a number of console.logs, so I bumped mermaid as it's been fixed.

Hey @dmorneau, could you please try this branch and see if it improves the performance for you?

Looks great on latest main, thank you!

Fantastic, thanks for checking! :cat:


Update repo for release v0.5.1

I missed to update the CHANGELOG file with the last two bug fixes.


Team2sprint6

Changed to draft for now since the tests are still failing at team 1's old code. Hence, we'll have to merge their final code first before our branch is ready for review.


Add an /admin page

Gated by basic auth.
Just needs a simple form to specify game and version to trigger a generate. As a coarse form of job monitoring, could show the latest result (from Redis).
Later, it would be good to show status of generate jobs. (This assumes we have some kind of job queue).

I just added a Generate button to /game/cards/version.


recover_bev function in sst_v2

The recover_bev function dose not support the 3D window condition

def recover_bev(self, voxel_feat, coors, batch_size):
        '''
        Args:
            voxel_feat: shape=[N, C]
            coors: [N, 4]
        Return:
            batch_canvas:, shape=[B, C, ny, nx]
        '''
        ny, nx = self.output_shape
        feat_dim = voxel_feat.shape[-1]
        batch_canvas = []

        for batch_itt in range(batch_size):
            # Create the canvas for this sample
            canvas = torch.zeros(
                feat_dim,
                nx * ny,
                dtype=voxel_feat.dtype,
                device=voxel_feat.device)

            # Only include non-empty pillars
            batch_mask = coors[:, 0] == batch_itt
            this_coors = coors[batch_mask, :]
            indices = this_coors[:, 2] * nx + this_coors[:, 3]
            indices = indices.type(torch.long)
            voxels = voxel_feat[batch_mask, :] #[n, c]
            voxels = voxels.t() #[c, n]

            canvas[:, indices] = voxels

            batch_canvas.append(canvas)

        batch_canvas = torch.stack(batch_canvas, 0)

        batch_canvas = batch_canvas.view(batch_size, feat_dim, ny, nx)

        return batch_canvas

Sorry for the late reply. You are right and it's very easy to modify this code for 3D cases. If you have trouble, feel free to reopen this issue.


bump(github.com/containers/{storage,image,buildah})

Bump github.com/containers/storage to v1.12.13, github.com/containers/image to v2.0.0, and github.com/containers/buildah to v1.9.1.  This brings in support for the v2 registries.conf format (https://github.com/containers/image/pull/617 and related PRs), and fixes a potential hang in chroot isolation when the child process stops reading its stdin (https://github.com/containers/buildah/pull/1668).  The updates to the storage and image libraries pull in the zstd compression library, though we don't yet support compressing image layers using it.
This pulls in more of k8s.io/api and k8s.io/apimachinery.

/retest

@nalind I would expect k8s.io bumps would be reflected in glide.lock. Did you clear the glide cache before running the bump (glide cc)?

@adambkaplan  I had not, thanks.  Refreshed it.

/hold
will likely be replaced by #86

Closing since #86 was merged.


transformMessage for Complex Rules are setting transformMessage on sub rules improperly

Complex rules such as AnyRule overwrite the transformMessage of the Rules themselves.
Expected Behavior

The transformMessage of a Rule should have higher priority than anything above it.
Current Behavior

The transformMessage of AnyRule and other similar Rules have higher priority than their subrules.
Possible Solution

We should add a contract for Complex Rules such as this so it becomes difficult to make mistakes like this.
Steps to Reproduce (for bugs)

The following Test can reproduce it

  test(
    'Sub rules use their transformMessage instead of AnyRules transformMessage',
    () {
      Rule<String> rule = AnyRule<String>([
        RequiredRule()
          ..transformMessage = (
            String message,
            Map<String, String> valueMapping,
          ) {
            return "Required";
          }
      ]);
      rule.transformMessage = (
        String message,
        Map<String, String> valueMapping,
      ) =>
          'Any';
      String message = rule.validate("Test", '');
      expect(message, 'Required');
    },
  );

Output
 Expected: 'Required'
    Actual: 'Any'
     Which: is different.
            Expected: Required
              Actual: Any
                      ^
             Differ at offset 0

Your Environment

Version used: v0.3.0
Flutter/Dart version: Dart version 2.5.0

Currently, in AnyRule we are completely ignoring enclosed Rule#transformMessage instead we should use null assignment operator so the enclosing Rule's transformMessage does not override the enclosed Rule's transformMessage. Plus this issues points out a fundamental flaw on the usage of transfomMessage in the current implementation. We'll need to rethink the implementation details of transformMessage.


usage of ProGuard causes error in release-build of hello-jni

I changed just couple lines in hello-jni project, such as enabled ProGuard, so my buildTypes  section is next
buildTypes {
            release {
                minifyEnabled = true
                //proguardFiles.add(file('proguard-rules.txt'))
                proguardFiles.add(file('proguard-rules.pro'))
            }
        }

As you can see here I've replaced proguard-rules.txt with proguard-rules.pro.
My ProGuard custom options are next
-optimizationpasses 5
-optimizations !class/unboxing/enum
-assumenosideeffects class android.util.Log {
    public static boolean isLoggable(java.lang.String, int);
    public static int v(...);
    public static int i(...);
    public static int w(...);
    public static int d(...);
    public static int e(...);
}

At this stage everything works fine, even creation of Signed APK, but after addition of standard dependencies creation of Signed APK FAILS.
So here is dependencies I've added to app's build.gradle file
dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    testCompile 'junit:junit:4.12'
    compile 'com.android.support:appcompat-v7:23.0.0'
}

After performing generation of Signed APK I've got 1 error and 5 warnings, error is next
Execution failed for task ':app:transformClassesAndResourcesWithProguardForAllRelease'.
As far as I see warnings are related with android.support.v4 and android.support.v7
Here is lines, which are colored in red in Gradle Console
Note: there were 7 duplicate class definitions.
Warning: android.support.v4.app.NotificationCompat$NotificationCompatImplBase: can't find referenced method 'void setLatestEventInfo(android.content.Context,java.lang.CharSequence,java.lang.CharSequence,android.app.PendingIntent)' in library class android.app.Notification
Warning: android.support.v4.app.NotificationCompat$NotificationCompatImplGingerbread: can't find referenced method 'void setLatestEventInfo(android.content.Context,java.lang.CharSequence,java.lang.CharSequence,android.app.PendingIntent)' in library class android.app.Notification
Warning: android.support.v4.app.NotificationCompatGingerbread: can't find referenced method 'void setLatestEventInfo(android.content.Context,java.lang.CharSequence,java.lang.CharSequence,android.app.PendingIntent)' in library class android.app.Notification
Warning: there were 3 unresolved references to library class members.
         You probably need to update the library versions.

Help me please, I don't understand what causes this problems.

both this one and issue 269 are new to me, hope someone could help out.

I found a solution on my own, as I said those warnings are related with android.support.v4 and android.support.v7, so I added -dontwarn android.support.** instruction to my proguard-rules.pro file.
As far as I see, after addition of this instruction you can still see warning messages in Gradle Console, but there is no error and creation of Signed APK performs successfully.

thanks, I will ask authority about it, and see if the warning matters: maybe keep this one open to remind us : it need to be followed up.

yes, could you still run your signed apk? I do not see I could executed it, with error:
No implementation found for java.lang.String com.example.hellojni.HelloJni.a()
[it is crash on Nexus 6]. if you could run your apk, that is good

many years from last discussion, Android studio 3.1.3 seems ok...


Capture Detailed Component Usage Metric

Enhance metric capture to support product OKR (migrate from UITK -> Salt)

Priority for Espresso

Espresso Goal: Priority goal after Button release, has to be started ASAP..
the sooner we do it, the better the quality of our OKR

Sep 3 - started some query using Source graph, while waiting for button updates

Frappe Goal: verify the data is accurate before publishing

Summary of work

Scripts to get number of imports for Salt and UITK using SourceGraph (managed-api-data-convertor repo), with aggregated summary like ManagedAPI data

SourceGraph result is semi-fluctuating (potentially due to BitBucket server stability), so would be good to take result based on average per month basis

Excel file created (Teams / General / Salt / Metrics ) to capture aggregated summary by LOB


Site not responsive on mobile.

Hi Akshay,
This tutorial is quite in-depth and over 60 pages. It is not HTML from scratch but a jupyter notebook converted to HTML, which is not responsive. Since it's not really meant to be read on a phone given the level of detail, I think it's okay!


Update postgresql to 42.3.3

Updates org.postgresql:postgresql from 42.3.1 to 42.3.3.
Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.postgresql", artifactId = "postgresql" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #380.

Superseded by #380.


Bug Report: CRC-32 Checksum Broken for Non-String Data

CRC Checksum Issues with Non-String Data
Issue: The CRC-32 Checksum operation does not work correctly if you pass it binary data instead of an ASCII string. I haven't confirmed this behavior on CRC-16 Checksum but based on a review of the code it likely also has the same issue.
Possible Root Cause: Based on my research the module currently being used by Cyberchef for CRC checksums, JS-CRC version 0.2.0, calculates inputs as strings by default and has internal checks that allow for input as byte Array, Uint8Array, and ArrayBuffer. However, Cyberchef currently passes all input to the CRC function/module as strings.
Extract from JS-CRC readme:
// It also supports byte Array, Uint8Array, ArrayBuffer input: crc32([0]); // d202ef8d crc32(new Uint8Array([0])); // d202ef8d
Example
If you input a hex byte string and use the From Hex operation to convert it to raw, then use the CRC-32 Checksum operation to obtain the CRC hash for the binary the results are incorrect.
Passing string data does work correctly.

Thanks @proud2bgeeky. I ran some tests and found some cases where we were generating the wrong checksums for CRC-16 and -32. Changing the input type to ArrayBuffer fixes the issue. I've also added some tests so that we'll notice if this ever breaks again.


Detection testing combined

Testing Detection Unload Sysmon Filter
Testing Detection Suspicious Reg Exe process
Testing Detection Schtasks scheduling on Remote System
Improved CI job

Detection Testing: Malicious PowerShell Process - Encoded Command


TypeError: fn is not a function thrown with v5.x and 6.x

Describe the bug
I just updated from v4.x to v6.x (I also tried v5.x before), and noticed the calendar was not being properly positioned, and it didn't take into consideration the available space above and below.
Then I saw these errors all over the console:

Uncaught (in promise) TypeError: fn is not a function
    at computePosition (react-datepicker.js?v=fc9deb51:678:15)

I might be wrong, but this seems to be part of @floating-ui/react code, but bundled together with react-datepicker? I'm wondering if perhaps the dependencies should not be bundled, as downstream projects will be installing them anyway.
This is probably unrelated with the issue, though.
To Reproduce
I'm trying to put together a minimum project reproducing this, to determine if there's any kind of conflict with other deps.
In the meantime, you can also see the error triggered in my project's tests, here https://github.com/shlinkio/shlink-web-component/actions/runs/7766045038/job/21181419223?pr=248 (this is dependabot's PR to update to v6.x)
Expected behavior
Calendar popover gets properly positioned.
Screenshots
You can see the wrong positioning here (ignore the triangle. I'm almost sure that's a conflict with other CSS in the page and I will sort that out myself)
Grabación de pantalla desde 2024-02-04 10-50-29.webm
Notice it renders over the input, instead of below/above it.
Desktop (please complete the following information):

OS: Ubuntu
Browser: Google Chrome
Version: 120

Same happened with me

Same happened to me, for our project the solution was to pass an array of Middleware from @floating-ui/dom to popperModifiers instead of Popper modifiers (the types from @types/react-datepicker seem outdated)

@tamasv-di can you please share code example?

@nikitadubyk Can't share the whole file unfortunately, but here are the relevant changes
on v4:
<DatePicker
...
popperModifiers={[
 {
  name: "preventOverflow",
  enabled: true,
  options: {
   padding: 0,
   boundary: document.body
  }
 }
]}
...
/>

on v6
import {shift, Middleware} from "@floating-ui/dom";
import {Modifier, StrictModifierNames} from "react-popper";
...
const middlewares = useMemo<Middleware[]>(() => [shift()], []);
...
<DatePicker
...
popperModifiers={middlewares as unknown as ReadonlyArray<Modifier<StrictModifierNames>>}
...
/>

In my case it helped to change
popperModifiers={[
  {
    name: "offset",
    options: {
      offset: [0, -6],
    },
  },
]}

to
import { autoPlacement, offset } from "@floating-ui/dom";

popperModifiers={[
  autoPlacement({
    alignment: "start",
    autoAlignment: false,
  }),
  offset({ mainAxis: -6, crossAxis: 0 }),
]}

it's basically the popperModifiers prop that has to be updated after upgrading.


Make sending SIGTERM optional.

Describe the bug
In issue SIGTERM support has been added, similar to Firebase and Sentry. Firebase and Sentry have disabled their collection by default, as they produce a very large number of false crashes. It would be cool to remove the default SIGTERM collection and make it configurable.
Steps to reproduce
During normal use.
Crash report or stack trace
No response
KSCrash version
2.0.0
Operating System
iOS
OS version
all
Device model
No response
Xcode version
No response
Additional context
No response

Thanks for a bug report. It makes perfect sense to have this feature disabled by default.
Here's the PR: #578. Once merged we'll make another RC build.


Remove diesel support

With Ruma (the homeserver) not being developed anymore, Conduit using sled and Maelstrom using sqlx, it seems pointless to keep the diesel integration. I also don't particularily like diesel.
If you want the integration to stay, let me know! Also, it can always be put back in if it is removed.

Done in 5861457.


Avoid (temporary?) integer overflow

Drive-by: simplify division by 2:
https://godbolt.org/z/sq91EMKT8

@jonsneyers to double-check if this simplification can be applied to the SIMD code too

Wow, good find! How did I ever end up with that complicated expression if it just boils down to avg + diff/2?

I did that in a thought experiment. Both addends (avg * 2 and "fixed" diff) have the rightmost bit set to 0 -> their sum have the rightmost bit set to 0 as well -> likely no surprises. But going to double-check soon.

We should also clean this up in the spec, and probably the SIMD code can be made slightly faster by doing the simplification also there.


Add a web UI in plugin settings for importing data

This will provide a button which, when clicked, will start a server-side import of data from some standard location. This allows new instances to quickly bootstrap with data from well-known sources.
While this is not strictly a "setting", the operation will be done very infrequently and only by administrators, so it makes sense to be in the plugin settings page.

This should also add a setting box for the instance's brand name.

Now fixed.


Unify Graph Generation Infra with GraphIR Integration

GraphIR is now integrated so that we now can do generation, mutation, translation, visualization (dot) in one self-hosted IR.
Notably the dot lang is translated from GraphIR from scratch now so that we can customize the style and drop the networkx dependency.
As a sample:

Later on we need to also deprecate the pygraphviz dependency for its type constraints. We also need to update the developer doc for simplifying program manipulation and translation with GraphIR.

Validated on https://github.com/ganler/nnsmith/actions/runs/3546552845.


[Map] Ortican

This current Ortican download is missing the readme and other files (including the ending map).
Seems like this would be the best replacement for the current download:
http://www.klankaos.com/USP/ortican.zip

URL: https://unrealarchive.org/unreal-tournament/maps/single-player/O/ortican_fb19ee66.html
Hash: fb19ee66b15769bcb988d9d076b216ede2f0e258
Current name: Ortican

Actually I've been informed that the correct download is here: https://unrealarchive.org/unreal-tournament/maps/single-player/O/ortican_853918a3.html .
So the version linked here is just an incomplete upload that can be removed.


Add test for subnetwork reducers

[ ] Create tests for src/reducers/subnetwork.js. PR reference: #39
[ ] Refactor src/reducers/subnetwork.js.

This issue can ben two PRs but, do the tests first to make sure nothing breaks.
Also, you can use ramda to refactor:
// current
case LOAD_NETWORK: {
  const { subnetworks } = action.payload.state.network;
  return subnetworks || [];
}
// with Ramda
import { path, defaultTo } from 'ramda';

const pathPayloadStateNetwork = path(['payload', 'state', 'network'])
const defaultToEmptyArray = defaultTo([]);

case LOAD_NETWORK: {
  return defaultToEmptyArray(pathPayloadStateNetwork(action))
}
// or
const onLoadNetwork = pipe(pathPayloadStateNetwork, defaultToEmptyArray);
case LOAD_NETWORK: {
  return onLoadNetwork(action)
}

Other details about this reducer:

There is a method called colorsNol that should be something like getRandomColor. I believe you can extract this to a new utils like /src/utils/colors or use a package for it. Just to be clear: a super-node is a sub-network that will receive a random color. Yes, I'm awere that super-node is a really bad name but I will change it in another PR.
There is a condition that I don't know if is valid: if (nodes && positions) {. This was made because we can receive two different networks: the current format and the old.

networks.zip
In this .zip you can find the two networks. You can move theses networks to a __fixtures__ folder and then use it in your tests.

first-version-network.json - the first/legacy version
simple-network.json - the current version

Well, thats it 😄

@nolleto I think that is no need to refactor with ramda because it will be verbose and it there will be refactoring for refactoring only. For example defaultToEmptyArray, onRemoveSuperNode and onLoadNetwork functions not improve code readability for developer:
const pathSubnetwork = path(['payload', 'state', 'network', 'subnetworks']);
const defaultToEmptyArray = defaultTo([]);
const onLoadNetwork = pipe(pathSubnetwork, defaultToEmptyArray);
const onRemoveSuperNode = (action) => filter(propEq('id', action.payload.id))

export default (state = [], action) => {
  switch (action.type) {
    case NEW_NETWORK:
      return defaultToEmptyArray();
    case ADD_SUPER_NODE:
      return [
        ...state,
        formatNetwork(action.payload.state),
      ];
    case REMOVE_SUPER_NODE:
      return onRemoveSuperNode(action)(state)

    case LOAD_NETWORK: {
      return onLoadNetwork(action)
    }
    default:
      return state;
  }
};

Hello @ufocoder
Yeah, the refactor of this small reducer has not a great impact on readability, for example. This is just a refactor to keep it more functional and I believe just REMOVE_SUPER_NODE will take more advantage of it.
A good thing about using ramda here is that it never will throw an error or change the object.
const removeSuperNode = (state, action) =>
  state.filter(n => n.id !== action.payload.id);

const getPayloadId = path(['payload', 'id']);
const removeSuperNodeWithRamda = (state, action) =>
  reject(propEq('id', getPayloadId(action)), state);

removeSuperNode([], {}) // throws an error
removeSuperNodeWithRamda([], {}) // returns a new state: []

Another thing, I believe the refactor will be something like:
const addNetworkProps = ({ network, nodes, positions }) => ({
  ...network,
  nodes,
  positions,
  color: getRandomColor(),
})

const formatNetwork = ifElse(hasNodesAndPositions, addNetworkProps, prop('network'))
const getPayloadState = path(['payload', 'state'])
const getPayloadSubnetworks = path(['payload', 'state', 'network', 'subnetworks'])
const getPayloadId = path(['payload', 'id'])

const getNetworkFromPayloadState = pipe(getPayloadState, formatNetwork)
const getPayloadSubnetworksOrDefault = pipe(getPayloadSubnetworks, defaultTo([]))

export default (state = [], action = {}) => {
  switch (action.type) {
    case NEW_NETWORK:
      return [];
    case ADD_SUPER_NODE:
      return append(getNetworkFromPayloadState(action), state);
    case REMOVE_SUPER_NODE:
      return reject(propEq('id', getPayloadId(action)), state);
    case LOAD_NETWORK:
      return getPayloadSubnetworksOrDefault(action);
    default:
      return state;
  }
};

😄


Duplicate URL

The collector is fetching content from duplicate URLs as below. How to fetch unique URLS only?

https://www.krinn.in/
https://www.example.com/./
https://www.example.com/././
https://www.example.com/./././
https://www.example.com/././././

I have set <canonicalLinkDetector ignore="false" />
Thank You

Have a look at GenericURLNormalizer.  Add the removeDotSegments to the default list of normalizations applied, like this:
 <urlNormalizer class="com.norconex.collector.http.url.impl.GenericURLNormalizer">
    <normalizations>
        removeFragment, lowerCaseSchemeHost, upperCaseEscapeSequence,
        decodeUnreservedCharacters, removeDefaultPort,
        encodeNonURICharacters, removeDotSegments
    </normalizations>
  </urlNormalizer>

Thank you  will try this weekend and get back you with the results

it is working . Thank you


[FLOC-3302] simple query api

This is a minimal implementation of the query interface.
The results paging is not supported, the sort order is fixed and only querying by a branch name is supported. The interface can be extended later on as necessary.
See FLOC-3774 for a proposed advanced query interface.

Thanks, @avg-I! This looks good so far.
I was also thinking that there are a few more test cases that could probably be added. The tests for the querying currently focus on the success of the filter and limit so we should add tests to cover the error conditions that could be triggered.
Please address the comments and add the additional tests and resubmit.

As @avg-I is on holiday, I've picked up this issue and fixed the review comments that I made.

It was suggested that eliot should be used for logging instead of twisted.python.log. I've filed FLOC-3811 to address this.

Looks great! I especially love the test coverage.
A couple new tests that I would like to see, otherwise I've just got some passing comments here and there. Nothing that needs action, just things to think about -- especially if this codebase grows. I think some of my optional comments would make it easier to maintain.

Thanks for the review and the additional tests, @sarum90! :smile:


Minor Fixes

Description
Makes the SimDE dependency not private, and fixes the link to the C++ API documentation that had improper capitalization.

🚀 [bumpr] Bumped! New version:v1.0.1 Changes:v1.0.0...v1.0.1


Documentation missing stream methods

Its not clear how to find Request units after using stream methods such as container.CreateItemStreamAsync()
Return response from such methods don't contain RequestCharge property.
So how do we find RequestCharge (RequestUnits) when using stream methods?
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 49b9cecf-c00d-821f-c5f4-06249c75bf55
Version Independent ID: 12ec16ac-97c7-e351-464c-93a23f67845d
Content: Find request unit charge for a SQL query in Azure Cosmos DB
Content Source: articles/cosmos-db/nosql/find-request-unit-charge.md
Service: cosmos-db
Sub-service: nosql
GitHub Login: @jcocchi
Microsoft Alias: jucocchi

Hi @Astral100, the stream operations return a ResponseMessage which doesn't directly contain the RequestCharge. However, you can still get the RUs consumed by inspecting the Headers property. It will be listed as RequestCharge in the headers.
We will work on adding RequestCharge as a top level property in the response, and it is being tracked in the SDK repo here: https://github.com/Azure/azure-cosmos-dotnet-v3/issues/4166

Thank you very much for a quick response (and adding this feature to the backlog).
I will use the headers for now.
Although if this feature implementation is going to take a while, perhaps it is worth it to add this information about headers to the documentation as well.


Add doc and source for mrpt_path_planning

Please Add This Package to be indexed in the rosdistro.

noetic
rolling

The source is here:
https://github.com/MRPT/mrpt_path_planning
Checks

[X] All packages have a declared license in the package.xml
[X] This repository has a LICENSE file
[X] This package is expected to build on the submitted rosdistro

@nuclearsandwich Fair point! It's a good moment for thinking a better name.

@nuclearsandwich Done now!


Windows build only works with old subproject

If I try to compile a windows build using the latest git upstream for OpenHMD it fails. If I use the old version it builds. (Using cmake)
[ 83%] Linking C shared library libopenhmd.dll
/usr/lib/gcc/x86_64-w64-mingw32/9.2.0/../../../../x86_64-w64-mingw32/bin/ld: CMakeFiles/openhmd.dir/objects.a(openhmd.c.obj):openhmd.c:(.text+0xac0): undefined reference to `__imp_ohmd_list_open_device_s'
/usr/lib/gcc/x86_64-w64-mingw32/9.2.0/../../../../x86_64-w64-mingw32/bin/ld: CMakeFiles/openhmd.dir/objects.a(platform-win32.c.obj):platform-win32.c:(.text+0x133): undefined reference to `__imp_ohmd_sleep'
collect2: error: ld returned 1 exit status
make[2]: *** [subprojects/openhmd/CMakeFiles/openhmd.dir/build.make:462: subprojects/openhmd/libopenhmd.dll] Error 1
make[1]: *** [CMakeFiles/Makefile2:125: subprojects/openhmd/CMakeFiles/openhmd.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

For what it is worth meson also fails.

Is it this upstream issue? https://github.com/OpenHMD/OpenHMD/issues/245

yes


API route mapping to get 404 instead of Home/Index

Changed the route mapping so that calls to API methods that don't exist return 404 and not a page

@AmrineA,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Thanks for the suggestion! This is a bit too specific for us to include by default. However I'm glad you've got a solution that meets your own needs, and if anyone else raised this requirement, I'll point them to your PR as a suggestion solution. Hope that's OK!


Uncaught TypeError: Cannot read property 'getRegions' of undefined

Atom Version: 1.9.0-beta0
System: Mac OS X 10.11.5
Thrown From: indent-guide-improved package, v1.4.9
Stack Trace
Uncaught TypeError: Cannot read property 'getRegions' of undefined
At /Users/li-xinyang/.atom/packages/indent-guide-improved/lib/indent-guide-improved.coffee:33

TypeError: Cannot read property 'getRegions' of undefined
    at updateGuide (/Users/li-xinyang/.atom/packages/indent-guide-improved/lib/indent-guide-improved.coffee:33:54)
    at up (/Users/li-xinyang/.atom/packages/indent-guide-improved/lib/indent-guide-improved.coffee:59:9)
    at debounced (/Applications/Atom Beta.app/Contents/Resources/app.asar/node_modules/babel-core/node_modules/lodash/index.js:7737:27)
    at Function.module.exports.Emitter.simpleDispatch (/Applications/Atom Beta.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:25:14)
    at Emitter.module.exports.Emitter.emit (/Applications/Atom Beta.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:125:28)
    at /Applications/Atom Beta.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/text-buffer.js:1399:25

Commands
  4x -0:59 settings-view:check-for-package-updates (atom-workspace.workspace.scrollbars-visible-when-scrolling.seti-ui-no-icons.theme-dracula-theme.theme-genesis-ui)
     -0:15 application:add-project-folder (atom-workspace.workspace.scrollbars-visible-when-scrolling.seti-ui-no-icons.theme-dracula-theme.theme-genesis-ui)

Config
{
  "core": {
    "audioBeep": false,
    "disabledPackages": [
      "background-tips",
      "markdown-preview",
      "metrics",
      "open-on-github",
      "spell-check",
      "welcome",
      "about",
      "linter-pep8",
      "linter-rubocop"
    ],
    "themes": [
      "genesis-ui",
      "dracula-theme"
    ]
  }
}

Installed Packages
# User
advanced-open-file, v0.16.3 (inactive)
atom-beautify, v0.29.7 (inactive)
atom-ternjs, v0.14.1 (active)
autoclose-html, v0.23.0 (active)
autocomplete-paths, v1.0.2 (active)
autocomplete-python, v1.8.1 (active)
autocomplete-ruby, v0.1.0 (active)
dash, v1.6.1 (inactive)
dracula-theme, v1.2.7 (active)
easy-motion-redux, v1.1.1 (active)
editorconfig, v1.4.1 (active)
ex-mode, v0.8.0 (inactive)
file-icons, v1.7.14 (active)
genesis-ui, v0.5.0 (active)
git-plus, v5.15.0 (inactive)
highlight-selected, v0.11.2 (active)
indent-guide-improved, v1.4.9 (active)
language-babel, v2.28.0 (active)
linter, v1.11.8 (active)
linter-jshint, v2.1.0 (active)
linter-pep8, v1.3.0 (inactive)
linter-rubocop, v0.4.7 (inactive)
merge-conflicts, v1.4.4 (active)
pigments, v0.29.2 (active)
project-manager, v2.9.7 (active)
script, v3.7.3 (inactive)
sort-lines, v0.14.0 (inactive)
split-diff, v1.0.2 (inactive)
Sublime-Style-Column-Selection, v1.5.1 (active)
todo-show, v1.6.0 (inactive)
vim-mode, v0.65.1 (active)
vim-surround, v0.8.1 (active)
Zen, v0.16.4 (inactive)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.51.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.43.0 (inactive)
base16-tomorrow-dark-theme, v1.1.0 (inactive)
base16-tomorrow-light-theme, v1.1.1 (inactive)
one-dark-ui, v1.3.2 (inactive)
one-light-ui, v1.3.2 (inactive)
one-dark-syntax, v1.2.0 (inactive)
one-light-syntax, v1.2.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.5.2 (inactive)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.1 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.0 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.0 (inactive)
bookmarks, v0.41.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.38.1 (active)
fuzzy-finder, v1.2.0 (active)
git-diff, v1.0.1 (active)
find-and-replace, v0.198.0 (inactive)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.1 (active)
image-view, v0.58.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (inactive)
metrics, v0.53.1 (inactive)
notifications, v0.64.1 (active)
open-on-github, v1.1.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.238.0 (active)
snippets, v1.0.2 (active)
spell-check, v0.67.1 (inactive)
status-bar, v1.3.1 (active)
styleguide, v0.46.0 (active)
symbols-view, v0.113.0 (inactive)
tabs, v0.98.0 (active)
timecop, v0.33.1 (active)
tree-view, v0.208.0 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.34.0 (inactive)
whitespace, v0.32.2 (active)
wrap-guide, v0.38.1 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.0 (active)
language-csharp, v0.12.1 (active)
language-css, v0.36.2 (active)
language-gfm, v0.86.0 (active)
language-git, v0.13.0 (active)
language-go, v0.42.0 (active)
language-html, v0.44.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.22.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.0 (active)
language-less, v0.29.3 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.0 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.68.5 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.52.0 (active)
language-shellscript, v0.22.3 (active)
language-source, v0.9.0 (active)
language-sql, v0.21.1 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.8 (active)
language-yaml, v0.26.0 (active)

# Dev
No dev packages

No issues on official release version Atom.

Heads up! I'm seeing this issue on the latest release (1.9.0) today. I haven't made any changes in my packages or settings recently.
My packages:
Built-in Atom Packages (89)
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
Community Packages (9) /Users/aaizman/.atom/packages
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
└── (empty)

I'm getting the same as anastasia and it started today. Atom version 1.9.1.
I cannot type into the editor at all.

I had the same problem today.
You should update indent-guide-improved package.
Close all tabs and restart Atom

Resolved after indent-guide-improved package update.

fixed after indent-guide-improved package update :)


A WebJob uploaded to Linux App Service is not working

App Service Plan: Linux, B1
App Service runtime: NodeJS 18
Repro steps:

Take the attached JavaScript file index.zip
Open Kudu SSH console
Create a folder /home/site/jobs/triggered/TestJob
Use nano to create a file "run.js", and copy-paste contents from the source file
Close nano, saving changes

Expected result:
The WebJob should be listed in the Portal -> WebJobs.
Actual result:
The job is nowhere to be found, and it doesn't seem to run.
Notes:
Uploading the file to any of the following folders doesn't seem to help:

/home/site/wwwroot/jobs/...
/home/site/wwwroot/app_data/jobs/...
/home/site/wwwroot/App_Data/jobs/...

Attempting to upload the file by putting it into a run.zip and from the portal results in an error "Bad request".
According to documentation WebJobs on Linux is currently in preview but the document does not say that I should enable some preview bit or opt-in to some specific feature in order to utilize it.

Also note that if I use Postman and try to issue GET /api/webjobs I am always greeted with what looks like a HTML page that says "Session expired".
If I use exact same credentials but issue GET /api/scm/info instead then I get a proper response. So, the credentials are working and so is the Kudu API in general. But for some inexplicable reason the WebJobs portion isn't.
Also note that if I try to do any of these steps in a Windows App Service Plan then everything works, the API and all.

If I monitor the Log Stream blade of the App Service while trying to use Postman, or pressing the "Refresh" button on the WebJobs blade then the following is printed to the console:
2024-04-26T12:53:27.3185176Z Exception Message : One or more errors occurred. (Connection refused (<IP_ADDRESS>:50555))
2024-04-26T12:53:27.3468771Z Exception StackTrace :    at System.Threading.Tasks.Task`1.get_Result()
2024-04-26T12:53:27.3470761Z    at Kudu.Services.Diagnostics.HttpRequestExtensions.ForwardToContainer(String route, HttpRequestMessage request) in /tmp/KuduLite/Kudu.Services/Diagnostics/HttpRequestExtensions.cs:line 51
2024-04-26T12:53:27.3470995Z    at Kudu.Services.Jobs.JobsController.ForwardJobRequestToContainer(String route) in /tmp/KuduLite/Kudu.Services/Jobs/JobsController.cs:line 198
2024-04-26T12:53:27.3471102Z    at Kudu.Services.Jobs.JobsController.ListAllJobs() in /tmp/KuduLite/Kudu.Services/Jobs/JobsController.cs:line 28
2024-04-26T12:53:27.3471223Z    at lambda_method75(Closure , Object , Object[] )
2024-04-26T12:53:27.3471324Z    at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
2024-04-26T12:53:27.3471447Z    at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()
2024-04-26T12:53:27.3471545Z    at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
2024-04-26T12:53:27.3471674Z    at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()
2024-04-26T12:53:27.3471766Z --- End of stack trace from previous location ---
2024-04-26T12:53:27.3471857Z    at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)
2024-04-26T12:53:27.3471974Z    at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
2024-04-26T12:53:27.3472074Z    at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()
2024-04-26T12:53:27.3472308Z --- End of stack trace from previous location ---
2024-04-26T12:53:27.3472408Z    at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|25_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
2024-04-26T12:53:27.3472542Z    at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)
2024-04-26T12:53:27.3472638Z    at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
2024-04-26T12:53:27.3472737Z    at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync()
2024-04-26T12:53:27.3472850Z --- End of stack trace from previous location ---
2024-04-26T12:53:27.3472946Z    at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
2024-04-26T12:53:27.3473075Z    at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
2024-04-26T12:53:27.3473173Z    at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext)
2024-04-26T12:53:27.3473293Z    at Kudu.Services.Web.Tracing.TraceMiddleware.Invoke(HttpContext context) in /tmp/KuduLite/Kudu.Services.Web/Tracing/TraceMiddleware.cs:line 107
2024-04-26T12:53:27.4920402Z fail: Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware[1]
2024-04-26T12:53:27.4922398Z       An unhandled exception has occurred while executing the request.
2024-04-26T12:53:27.4922604Z       System.Net.Http.HttpRequestException: Connection refused (<IP_ADDRESS>:50555)
2024-04-26T12:53:27.4922731Z        ---> System.Net.Sockets.SocketException (111): Connection refused
2024-04-26T12:53:27.4922839Z          at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 )
2024-04-26T12:53:27.4922941Zat System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs , ValueTask , CancellationToken )
2024-04-26T12:53:27.4923068Z          at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String , Int32 , HttpRequestMessage , Boolean , CancellationToken )
2024-04-26T12:53:27.4923159Z          --- End of inner exception stack trace ---
2024-04-26T12:53:27.4923348Z          at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String , Int32 , HttpRequestMessage , Boolean , CancellationToken )
2024-04-26T12:53:27.4923474Z          at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage , Boolean , CancellationToken )
2024-04-26T12:53:27.4923601Z          at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage , Boolean , CancellationToken )
2024-04-26T12:53:27.4923694Z          at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(HttpRequestMessage )
2024-04-26T12:53:27.4923785Z          at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken )
2024-04-26T12:53:27.4923907Z          at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage , Boolean , CancellationToken )
2024-04-26T12:53:27.4924002Z          at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage , Boolean , Boolean , CancellationToken )
2024-04-26T12:53:27.4924122Z          at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage , Boolean , CancellationToken )
2024-04-26T12:53:27.4925042Z          at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage , Boolean , CancellationToken )
2024-04-26T12:53:27.4925213Z          at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage , HttpCompletionOption , CancellationTokenSource , Boolean , CancellationTokenSource , CancellationToken )
2024-04-26T12:53:27.4925330Z          at Kudu.Services.Web.Tracing.TraceMiddleware.Invoke(HttpContext context) in /tmp/KuduLite/Kudu.Services.Web/Tracing/TraceMiddleware.cs:line 107
2024-04-26T12:53:27.4925455Z          at Microsoft.AspNetCore.ResponseCompression.ResponseCompressionMiddleware.InvokeCore(HttpContext context)
2024-04-26T12:53:27.4925551Z          at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.<Invoke>g__Awaited|6_0(ExceptionHandlerMiddleware middleware, HttpContext context, Task task)
2024-04-26T12:53:27.5116059Z X-MS-VIA-EXTENSIONS-ROUTE = true
2024-04-26T12:53:27.5199950Z httpRequest.Method = GET
2024-04-26T12:53:27.5200927Z X-MS-CLIENT-AUTHORIZATION-SOURCE = RoleBased
2024-04-26T12:53:27.5201103Z X-MS-CLIENT-ROLEBASED-CONTRIBUTOR =
2024-04-26T12:53:27.5201355Z URI path = /Error

The IP address is the same that's printed on the SSH console when I open it via Kudu but I am not sure what is supposed to be running on port 50555.

Hi
If the problem persists and is related to running it on Azure App Service, please open a support incident in Azure:
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
This way we can better track and assist you on this case
Thanks,
Joaquin Vano
Azure App Service


Readme has wrong project name

The readme still calls this a Box instead of a starter kit. Can we fix this?
cc: @andrejrakic

@StephenFluin  Yes, thanks for raising this issue! This will be fixed in the upcoming PR


Enable open-pull-requests-limit to apply only for dependabot PR

Hi dependabot team !
As described by the title we would like to have a feature which enable us to apply the limit only to dependabot user PR.
On some repositories with lot of traffic it's not un-common to have a lot of PR open.
A flag would look like open-pull-requests-limit-apply-to-dependabot-only: true / false.
If we set the limit too low dependabot will never open a PR. Also it's not always simple to fix a limit some repositories have temporary increase in PR and some month with no traffic.
Hope there was not already a similar suggestion ! Have a nice day !

That's how it works already! 😄  Have you ran into issues with it?


Speed Test

Script Title - Speed test
what will change -
Add a script that will run a speed test in the terminal
Instructions

Create a new folder for your script and file/folder name should be appropriate.
Create a README.md in your folder for program Instructions
add requirements.txt if needed

Please add/delete options that are not relevant.

[x] Adding New Code

Programming Language

[x] Python

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server  - https://discord.gg/FXyh2S3
Happy Coding,

Happy to work on this if assigned to me

May I do that?

I have actually already done it - just waiting to be assigned the issue so I can make a PR


feat: persist pxe state

This PR adds a persistent database to PXE. I've created a new package in the monorepo called @aztec/kv-store which exports a set of general data structures that can be used by components to store state in consistent manner. The only implementation right now is with LMDB (both persisted on disk and in-memory/temporary file).
This higher level abstraction allowed me to easily add storage to PXE's note processors, its synchronizer and its key store.
Fix #3364 #2709
This PR also fixes #2709 by removing the "initial L2 block" config parameter of the PXE/note processor (it always starts from last known state).

Benchmark results
Metrics with a significant change:

note_successful_decrypting_time_in_ms (32): 1,093 (+19%)
note_successful_decrypting_time_in_ms (128): 4,021 (+16%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 379b5adc and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
222,924
868,280
3,449,708

l1_rollup_execution_gas
842,011
3,595,388
22,205,077

l2_block_processing_time_in_ms
2,280 (-2%)
8,566 (+1%)
35,656

note_successful_decrypting_time_in_ms
358 (+10%)
:warning: 1,093 (+19%)
:warning: 4,021 (+16%)

l2_block_building_time_in_ms
20,268
81,095 (+1%)
324,191 (+1%)

l2_block_rollup_simulation_time_in_ms
16,719
67,079 (+1%)
268,141 (+1%)

l2_block_public_tx_process_time_in_ms
3,518
13,940
55,802

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
24,824
48,130 (+1%)

node_database_size_in_bytes
3,626,021
3,929,974

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
200 (+1%)
43,109
20,441

private-kernel-ordering
115
25,833
9,689

base-rollup
2,959
667,692
873

root-rollup
88.4 (+4%)
4,072
881

private-kernel-inner
260
64,516
20,441

public-kernel-private-input
172 (+1%)
25,203
20,441

public-kernel-non-first-iteration
169
25,245
20,441

merge-rollup
11.0 (+1%)
2,592
873

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
10,323
25,938


Build all possible plugins required for functionality

CC @hmaarrfk
Many plugins are not being built in this build ecosystem due to missing host dependencies (many of which exist as valid feedstocks).
This can be checked by reading through all the NO messages in the build logs.
Because GStreamer doesn't tolerate bundling multiple projects into one package, more feedstocks are required.
Personally, I consider these (not currently existing) feedstocks important because I work with WebRTC:
    libmicrodns                          : YES (from gst-plugins-bad)
    libnice                              : YES 1 warnings
    libsrtp2                             : YES 1 warnings (from gst-plugins-bad)
    webrtc-audio-processing              : YES (from gst-plugins-bad)
    gst-plugins-rs                       : YES 1 warnings

Other dependencies can be found in here:
Build targets in project: 585

FFmpeg 6.1.1

  Basics
    License                                           : LGPL version 2.1 or later
    static                                            : YES
    shared                                            : NO
    postprocessing support                            : YES
    network support                                   : YES
    threading support                                 : pthreads
    safe bitstream reader                             : YES

  x86
    standalone assembly                               : YES
    x86 assembler                                     : nasm
    MMX                                               : YES
    MMXEXT                                            : YES
    3DNow!                                            : YES
    3DNow! extended                                   : YES
    SSE                                               : YES
    SSSE3                                             : YES
    AESNI                                             : YES
    AVX                                               : YES
    AVX2                                              : YES
    AVX-512                                           : YES
    AVX-512ICL                                        : YES
    XOP                                               : YES
    FMA3                                              : YES
    FMA4                                              : YES
    i686 features                                     : YES
    CMOV is fast                                      : YES
    EBX available                                     : YES
    EBP available                                     : YES

  Components
    External libraries                                : alsa bzlib libxcb libxcb_shm lzma zlib
    External libraries providing hardware acceleration:
    Libraries                                         : avdevice avfilter swscale postproc avformat avcodec swresample
                                                        avutil
    Programs                                          :

libdv 1.0.0

    YUV format            : YUY2
    assembly optimizations: YES

graphene 1.10.8

  Directories
    prefix         : /opt/gstreamer
    libdir         : lib/x86_64-linux-gnu
    includedir     : include

  SIMD
    SSE            : YES
    GCC vector     : YES
    ARM NEON       : NO

  Features
    GObject types  : YES
    Introspection  : YES

  Build
    Documentation  : NO
    Tests          : NO
    Installed tests: NO

gst-editing-services <IP_ADDRESS>

    Plugins: nle, ges

gst-plugins-bad <IP_ADDRESS>

    Plugins               : accurip, adpcmdec, adpcmenc, aiff, asfmux, audiobuffersplit, audiofxbad, audiomixmatrix,
                            audiolatency, audiovisualizers, autoconvert, bayer, camerabin, codecalpha,
                            codectimestamper, coloreffects, debugutilsbad, dvbsubenc, dvbsuboverlay, dvdspu,
                            faceoverlay, festival, fieldanalysis, freeverb, frei0r, gaudieffects, gdp,
                            geometrictransform, id3tag, insertbin, inter, interlace, ivfparse, ivtc, jp2kdecimator,
                            jpegformat, rfbsrc, midi, mpegpsdemux, mpegpsmux, mpegtsdemux, mpegtsmux, mse, mxf, netsim,
                            rtponvif, pcapparse, pnm, proxy, legacyrawparse, removesilence, rist, rtmp2, rtpmanagerbad,
                            sdpelem, segmentclip, siren, smooth, speed, subenc, switchbin, timecode, transcode, unixfd,
                            videofiltersbad, videoframe_audiolevel, videoparsersbad, videosignal, vmnc, y4mdec, aja,
                            decklink, dvb, fbdevsink, ipcpipeline, kms, nvcodec, qsv, shm, v4l2codecs, uvcgadget, va,
                            aes, analyticsoverlay, aom, avtp, bz2, closedcaption, codec2json, dash, dtls, fdkaac, hls,
                            iqa, de265, microdns, openh264, openjpeg, opusparse, sctp, smoothstreaming, soundtouch,
                            srtp, svtav1, ttmlsubs, waylandsink, webrtc, webrtcdsp, webp, x265
    (A)GPL license allowed: true

gst-plugins-base <IP_ADDRESS>

    GL api     : gles2, gl
    GL platform: egl, glx
    GL winsys  : egl, surfaceless, wayland, x11
    Plugins    : adder, app, audioconvert, audiomixer, audiorate, audioresample, audiotestsrc, compositor, dsd,
                 basedebug, encoding, gio, overlaycomposition, pbtypes, playback, rawparse, subparse, tcp,
                 typefindfunctions, videoconvertscale, videorate, videotestsrc, volume, alsa, opengl, ogg, opus, pango,
                 vorbis, ximagesink

gst-plugins-good <IP_ADDRESS>

    Plugins: alpha, alphacolor, apetag, audiofx, audioparsers, auparse, autodetect, avi, cutter, navigationtest, debug,
             deinterlace, dtmf, effectv, equalizer, flv, flxdec, goom, goom2k1, icydemux, id3demux, imagefreeze,
             interleave, isomp4, alaw, mulaw, level, matroska, monoscope, multifile, multipart, replaygain, rtp,
             rtpmanager, rtsp, shapewipe, smpte, spectrum, udp, videobox, videocrop, videofilter, videomixer, wavenc,
             wavparse, xingmux, y4menc, ossaudio, oss4, video4linux2, ximagesrc, aasink, adaptivedemux2, cairo, flac,
             gdkpixbuf, jack, jpeg, lame, dv, png, pulseaudio, soup, vpx

gst-plugins-rs 0.13.0-alpha.1

    Plugins: rsaudiofx, claxon, lewton, spotify, rsfile, originalbuffer, threadshare, rsinter, mp4, fmp4, aws,
             hlssink3, ndi, rsonvif, raptorq, reqwest, rsrtsp, rsrtp, webrtchttp, rswebrtc, textahead, json, regex,
             textwrap, rstracers, uriplaylistbin, cdg, rsclosedcaption, ffv1, rsflv, gif, hsv, rspng, rav1e, rsvideofx,
             gopbuffer, quinn, fallbackswitch, livesync, togglerecord, rswebp, sodium

gst-plugins-ugly <IP_ADDRESS>

    Plugins               : asf, dvdlpcmdec, dvdsub, realmedia, x264
    (A)GPL license allowed: true

gst-rtsp-server <IP_ADDRESS>

    Plugins: rtspclientsink

gstreamer <IP_ADDRESS>

    Plugins: coreelements, coretracers

orc <IP_ADDRESS>

  Backends
    AVX             : YES
    SSE             : YES
    MMX             : YES
    NEON            : YES
    MIPS            : YES
    c64x            : YES
    Altivec         : YES

  Build options
    Tools           : YES
    Tests           : NO
    Examples        : NO
    Benchmarks      : YES
    Documentation   : NO  disabled
    Orc-test library: YES

gstreamer-full <IP_ADDRESS>

  Build options
    gstreamer-full library               : NO
    gstreamer-full target type           : shared_library
    Tools                                : gst-inspect  gst-stats  gst-typefind  gst-launch  gst-device-monitor
                                           gst-discoverer  gst-play  gst-transcoder  ges-launch
    Helpers                              : gst-plugin-scanner  gst-completion-helper
    Libraries                            : gst-editing-services-1.0
    Tests and examples disabled          : NO

  Subprojects
    FFmpeg                               : YES (from gst-libav)
    abseil-cpp                           : YES (from gst-plugins-bad => webrtc-audio-processing)
    avtp                                 : YES (from gst-plugins-bad)
    dssim                                : YES (from gst-plugins-bad)
    dv                                   : YES (from gst-plugins-good)
    fdk-aac                              : YES (from gst-plugins-bad)
    flac                                 : YES (from gst-plugins-good)
    gl-headers                           : YES (from gst-plugins-base)
    graphene                             : YES 1 warnings (from gst-plugins-base)
    gst-devtools                         : NO Feature 'devtools' disabled
    gst-editing-services                 : YES
    gst-examples                         : NO Feature 'gst-examples' disabled
    gst-integration-testsuites           : NO Feature 'devtools' disabled
    gst-libav                            : YES
    gst-plugins-bad                      : YES
    gst-plugins-base                     : YES
    gst-plugins-good                     : YES
    gst-plugins-rs                       : YES 1 warnings
    gst-plugins-ugly                     : YES
    gst-python                           : YES
    gst-rtsp-server                      : YES
    gstreamer                            : YES 3 warnings
    gstreamer-sharp                      : NO Feature 'sharp' disabled
    gstreamer-vaapi                      : NO Feature 'vaapi' disabled
    lame                                 : YES 1 warnings (from gst-plugins-good)
    libmicrodns                          : YES (from gst-plugins-bad)
    libnice                              : YES 1 warnings
    libsrtp2                             : YES 1 warnings (from gst-plugins-bad)
    ntv2                                 : YES (from gst-plugins-bad)
    orc                                  : YES
    soundtouch                           : YES (from gst-plugins-bad)
    tinyalsa                             : NO Neither a subproject directory nor a tinyalsa.wrap file was found.
    webrtc-audio-processing              : YES (from gst-plugins-bad)

  User defined options
    buildtype                            : release
    prefix                               : /opt/gstreamer
    bad                                  : enabled
    devtools                             : disabled
    doc                                  : disabled
    examples                             : disabled
    gpl                                  : enabled
    gst-examples                         : disabled
    introspection                        : enabled
    libav                                : enabled
    libnice                              : enabled
    nls                                  : disabled
    orc                                  : enabled
    python                               : enabled
    rs                                   : enabled
    rtsp_server                          : enabled
    tests                                : disabled
    tls                                  : enabled
    tools                                : enabled
    ugly                                 : enabled
    webrtc                               : enabled
    gst-plugins-bad:aom                  : enabled
    gst-plugins-bad:libde265             : enabled
    gst-plugins-bad:nvcodec              : enabled
    gst-plugins-bad:openh264             : enabled
    gst-plugins-bad:qsv                  : enabled
    gst-plugins-bad:svtav1               : enabled
    gst-plugins-bad:v4l2codecs           : enabled
    gst-plugins-bad:va                   : enabled
    gst-plugins-bad:webrtcdsp            : enabled
    gst-plugins-bad:x265                 : enabled
    gst-plugins-base:alsa                : enabled
    gst-plugins-base:gl                  : enabled
    gst-plugins-base:opus                : enabled
    gst-plugins-good:jack                : enabled
    gst-plugins-good:pulse               : enabled
    gst-plugins-good:v4l2                : enabled
    gst-plugins-good:vpx                 : enabled
    gst-plugins-good:ximagesrc           : enabled
    gst-plugins-good:ximagesrc-navigation: enabled
    gst-plugins-good:ximagesrc-xdamage   : enabled
    gst-plugins-good:ximagesrc-xfixes    : enabled
    gst-plugins-good:ximagesrc-xshm      : enabled
    gst-plugins-rs:rav1e                 : enabled
    gst-plugins-ugly:x264                : enabled

Found ninja-1.11.1.git.kitware.jobserver-1 at /usr/local/bin/ninja

Includes #61

PRs welcome.
Try to not "require" all. Multimedia is very broad and many codecs just get stale. So build what you need, help others.

Try to not "require" all. Multimedia is very broad and many codecs just get stale. So build what you need, help others.

I'll try to enable the most common ones but not the uncommon ones. Is there a handy way to make optional dependencies?

Is there a handy way to make optional dependencies?

This is generally the challenge.
If the finally libraries can handle missing shared libraries, then it may become possible. You can create a split package where the main package does not add any hard dependency on a library, but may add a constraint.
Ultimately, the hardest aspect is the imposed perpetual maintenance burden imposed on the other maintainers of this feedstock. This isn't to discourage you from adding what you need, but be mindful of the (and your) increased maintenance burden.
Generally. The strength of conda forge is to enable us to add dependencies without fear of breaking things for others!!!!
Excited to have more codecs!!!

Ultimately, the hardest aspect is the imposed perpetual maintenance burden imposed on the other maintainers of this feedstock. This isn't to discourage you from adding what you need, but be mindful of the (and your) increased maintenance burden.

OK, Great! Thank you for the tip.

This is going to take a bit longer because short-term, I dropped my plan to put in my project as a conda-forge feedstock.
However, thanks to all the new feedstocks which were dependencies, I can finally build a portable version of my project using conda-build locally and distribute using conda-pack.
Long-term, I still have a goal to fit my project into conda-forge. It will take some time.


[WIP] Allow unary var overloaded functions to also work with Matrix types

Summary
This modifies the current overloads for unary var<Matrix> functions so that they can also accept Matrix<var> functions. This should be a bit more efficient since copies to the memory arena will be done in bulk. To do this I created a new function make_callback_rev_matrix which, given the expected return type of either a Matrix<var> or var<Matrix> creates the correct return and places a callback for the reverse pass onto the reverse pass callback stack.
This is a WIP until I doc all the new functions
Tests
There should be no new tests needed as we are writing specializations for functions already tested by the test ad framework.
Side Effects
None
Release notes
Add more matrix overloads for reverse mode unary functions
Checklist

[ ] Math issue #

[x] Copyright holder: Steve Bronder
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[x] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
dependencies checks pass, (make test-math-dependencies)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

Are u planing a benchmark? Which models should benefit from this?

Yes I can writeup a benchmark. My thinking with these is that its better for memory if we are doing large allocations at once and reducing the callback stack size from N calls for each scalar to 1 call for the entire matrix.


Add field for ignored content

When experimenting (using try-libpostal), I see that the recipient to an address is dropped. For example
Jerry Seinfeld, 129 West 81st Street, Apartment 5A, New York, New York, 10024

{
  "road": "west 81st street",
  "house_number": "129",
  "unit": "apartment 5a",
  "city": "new york",
  "state": "new york",
  "postcode": "10024"
}

The ask is to not be lossy and capture ignored content in another field. If this is well known, like recipient, it could be labeled explicitly. Otherwise, something simple like extra_info would be perfect. The intent is to let the user of libpostal decide if that content is ignorable and handle appropriately.
The current behavior is reasonable. However, when parsing dirty data it may be desirable to not lose information. Unfortunately many legacy systems, like order management, have a lot of junk such as instructions in the address. I would appreciate the opportunity to capture this to avoid being lossy to handle on a case-by-case basis, depending on the integration needs.
If I change the recipient, e.g. use Jerry Seinfel, then the recipient is included as house. This property seems to be sporadically included when I try different names. Can you please explain why this might occur?
At the moment, it would seem that a very naive workaround could be to tokenize the input and query for any missing tokens. If so, then that can be included as fallback content to be careful. However, I imagine that could be riddled with problems and it seems reasonable for the parser to identify any content it deemed ignorable.

I tried using libpostal-rest-docker and realized the output is mangled in the try-postal. It seems that road is included twice, so that little webapp was dropping an entry which caused my confusion.
The curl shows of the example is,
$ curl -X POST -d \
'{"query":"Jerry Seinfeld, 129 West 81st Street, Apartment 5A, New York, New York, 10024"}' \
localhost:8080/parser \
| jq

[
  {
    "label": "road",
    "value": "jerry seinfeld"
  },
  {
    "label": "house_number",
    "value": "129"
  },
  {
    "label": "road",
    "value": "west 81st street"
  },
  {
    "label": "unit",
    "value": "apartment 5a"
  },
  {
    "label": "city",
    "value": "new york"
  },
  {
    "label": "state",
    "value": "new york"
  },
  {
    "label": "postcode",
    "value": "10024"
  }
]

What is the expected handling for this case?
Is it a bug?
Should I concatenate entries with the same labels?

As an aside, since I hadn't tested this prior to implementing an http client, I have a decent workaround for any the content is missing (as I originally thought). I formatted the parsed values back into a string, tokenize the raw address by spaces, and use a fuzzy similarity score of the token against the parsed output. If the score is less than or equal to the token length, I add the token to a buffer for the missing content, and append include it in my final results. This seems to work nicely, but may not be necessary given my findings above.

I apologize for the noise. I now understand that some labels may repeat, like roads, as stated in your readme. In finality, can we expect that no content will be missing / ignored in the parsed results?

One way of a achieving this to record the offset positions in the input text.
If those start/end positions can be output in the solution then the consumer is able to make decisions about which characters were excluded from the solution and their relative position to other fields.

Eg.
noise, 12 main st

[
  {
    "label": "housenumber",
    "value": "12",
    "start": "7",
    "end": "9"
  },
  {
    "label": "road",
    "value": "main st",
    "start": "10",
    "end": "17"
  }
]


自动时间触发savepoint状态

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
自动时间触发savepoint状态
比如1天自动触发一次，1小时触发一次等....
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

好主意，我现在是自己写了个cron定时，每天定时调api接口保存savepoint


Speed up compilation of native libraries using all available cores

Use all available cores to build with make.
There is no need to parallelize the install target because it is an IO-bound operation.
On my 16-core machine building the docker image went from 17min to roughly 4min.
As I understand, you're already caching the docker layers, so as long as nothing changes, the GitHub Action is pretty fast (~3m30s). However, whenever something changes it takes much more (~25m). I think it may be worth checking out the use of ccache to speed up compilation for those cases. It essentially caches the objects that are the output of the compiler. So, as long as the source file, the compiler and the flags are the same, you don't need to actually compile anything. I've seen a GH Action for it, but I doubt it will work out of the box to build a docker image. Most likely, you'll need to install ccache in your Dockerfile, make sure it's used (export PATH="/usr/lib/ccache:/usr/local/opt/ccache/libexec:$PATH" it's the simplest way) and of course restore and save the .cache directory across builds.
Let me know if you need any help with that. It's pretty easy to set up.

Really appreciated 👏


Redcarpet -> Kramdown

We need to move to Kramdown by May 5. We're currently using redcarpet's tables extension, hopefully kramdown supports it.

I'm working on this in the gh-pages-compliance branch.
Tables haven't been a problem (kramdown actually has support built-in) and, with a bit of configuration, I've was able to make most of the other behavior match redcarpets.
The big exception to the above is syntax highlighting, where we were relying on redcarpets to pass the language of each code block through to HTML as a class attribute, which kramdown doesn't seem to do.

:+1:

It may be a rouge issue too, rather than a kramdown one. Ref https://github.com/jneen/rouge/issues/361 https://github.com/jneen/rouge/issues/379

Rouge is very much not-maintained, so hopefully if it is we can work around it.

Is this issue closeable since #1039 was merged? :)

Yup, thanks!


Deterministic endpoints order

Please provide a description for what this PR is for.
Filter endpoints with a deterministic order, this is to make eds cache assertion without panic.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
401d7eeea7fc5d364c26f5a0cfec8edc5c43b0bd
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


alternative

Since it's already over 20 hours and it seems you disagree, I'll wait for 4 hours from now and make another PR on the Apache Spark community officially for the wider review. At that time, I'll close this PR.

@squito, @dongjoon-hyun I'm not against this PR, what I "against" is removing check from canLaunchTask method, but I agree that checking blacklisting in match offers will be better.
anyway I've merged PR(maybe I don't understand something)


8088 and CGA support ?

BootMine needs a pentium class CPU and a EGA or VGA graphic card.
This version can run with a 8088 and a CGA card too.
The same code run as boot record or DOS COM file (position independent code) and Bombs are unveiled on game over screen.

This update supports 8088/CGA/EGA/VGA/MDA and fix minor bugs : bootmine.com


[docs website] - Hint that k8s.pod.name and k8s.ns.name work with CRI socket only, no need for k8s plugin

What to document
Proposal to improve https://falco.org/docs/reference/rules/supported-fields/. Hint that k8s.pod.name and k8s.ns.name work with CRI socket only, no need for k8s plugin. Place these hints under both Field Class: k8s and Field Class: container sections, especially under the container one.
@leogr before you shared this secret with me I was not aware of it, perhaps more end users may benefit from such an explicit hint on the website.

Although I tried to explain that here :point_down:

I agree it's too hidden and too cryptic :sweat_smile:
Making it explicit and more visible would be a great improvement! :+1:
cc @vjjmiras

Maybe use some style similar to below to make the hints also visually more obvious especially under the container fields section?

I did my best trying to clarify it: https://github.com/falcosecurity/falco-website/pull/781


Reuse entity manger interface

In the current set-up the AccessTokenRepository does gets a new EntityManager this can cause problems when saving a entity in your own Repositories that all share the same EntityManger. And then creating a token with the TokenRepository. Doctrine does not recognize the newly saved entity which causes issues.
For example:
$this->entityRepo->save($entity);
$token = $this->tokenRepository->createToken($entity, 'Token Y', ['*']);

Causes:
A new entity was found through the relationship that was not configured to cascade persist operations for entity
This pull requests uses the laravel-doctrine Entity Manger Interface that is bound as a singleton to fix the issue described above.

Ended up being a fault in my own code that triggered the creation of another EM, this PR is obsolete.


Incorrect link redirect after clicking on '?' in workflow function step

Issue

Notes
Server is running on 22.9 but the link redirects to 2023.3 docs

It's fixed


[feat}: Create a Hangman Game using Python

Issue Title: Create Hangman Game using Python
Issue Description
I propose to create a Hangman game using Python as a project for this repository.
Project Details

Name: Hangman Game
Technologies: Python

Additional Information (if available)
If there are any specific guidelines or requirements for contributing to the repository, please provide the necessary details to ensure a smooth integration of the project.
I am enthusiastic about working on this project and look forward to your feedback and the opportunity to contribute it to the repository. Thank you for considering this addition.

/assign


Typo at the "Contact Methods" section

Here, https://github.com/nasirhm/nasirhm/#contact-merthods.

Thanks for opening the issue, Fixed :D


⚠ Département GEGI website (prod) has degraded performance

In c1b2131, Département GEGI website (prod) (https://www.usherbrooke.ca/genie-electrique-informatique/) experienced degraded performance:

HTTP code: 200
Response time: 872 ms

Resolved: Département GEGI website (prod) performance has improved in 7186660.


Generate chains for use with Viem/Wagmi

Changes

Adds a new viemConfig.chains() function to generate chains for use in Viem/Wagmi. @wagmi/core/chains is a proxy for viem/chains.

Addresses: https://github.com/api3dao/chains/issues/84

PR update:
I have added nativeCurrency to each chain (replacing symbol). I copied the values from each chain defined by Viem here: https://github.com/wagmi-dev/viem/tree/main/src/chains/definitions. Where the chain didn't exist, I searched for values through the respective block explorer and through some extra Googling. I hope everything is correct.
viemConfig.chains no longer merges our definitions with the Viem definitions. Everything is now our definition.
I also renamed the following networks to more closely match the definitions from Viem:

Avalanche testnet -> Avalanche Fuji testnet
Gnosis Chain testnet -> Gnosis Chiado testnet

Also note, a lot of the chain symbol values have been changed. I'm not sure if these were being used or not, but the old values didn't seem correct to me


Function returning a key with type never can be assigned to a typed Object

🔎 Search Terms
never, function, assignable, assign
🕗 Version & Regression Information

This is the behavior in every version I tried (typescript@next and v5.4.5)

⏯ Playground Link
https://www.typescriptlang.org/play/?ts=5.5.0-dev.20240518#code/C4TwDgpgBAMghgIwPYCcIqgXigbygd1QGsAuKACgEosA+KAOwFcBbBdKAXwG4AoUSWHABeIeMjQZseQilIMIAN3bcePAGaN6AY2ABLJPSgBzCMDGp05AM7pdcADa6hEACYA1B4whkrwFLvojSjJ4EXMJXB4oKDRgRhRDACkAZQB5ADkAOjA4FBtrWwcnVw97L0peDlV7UyhmEAB1YnQQxAsUXnqm2XZsEzM2iXIAIkyx4YqoAHopqGAAC10rKCt5pEZ7FwYkYCg2KAd7JHxXABoD5bAUJEgUUChhmSJhqCW58Gh6RXYAh9DRQboYY8LrNFCZJ5ULjTWb4XT2exzebXfAHXYoTR6ZgQHhAA
💻 Code
type Laborer = { work: () => number };
type LazyLaborer = { work: never };

function getLaborer(serializedValue: string): LazyLaborer {
  return JSON.parse(serializedValue);
}

let myWorker: Laborer;
myWorker = getLaborer("..."); // this should not be allowed, as property "work" is type never in "LazyLaborer"
myWorker.work(); // will throw at runtime

🙁 Actual behavior
The code compiles without an error.
🙂 Expected behavior
The code should not compile, as we assign work: never to a real object.
Additional information about the issue
My real use case is, that I want to check, if a type is serializable with JSON. Inspired by the blog mastering-type-safe-json-serialization-in-typescript, I wanted to write a small library like the following
export type JSONValue = JSONPrimitive | JSONObject | JSONArray;

export type JSONPrimitive = string | number | boolean | null

export type JSONObject = { [key: string]: JSONValue };

export type JSONArray = JSONValue[];

export type JSONSerializable<T> = unknown extends T ? never : {
  [P in keyof T]:
    T[P] extends JSONValue ? T[P] :
    T[P] extends NotAssignableToJson ? never :
    JSONSerializable<T[P]>;
};

type NotAssignableToJson = bigint
  | symbol
  | Function;

function stringify<T>(obj: JSONSerializable<T>): string {
  return JSON.stringify(obj);
}

function parse<T>(serializedValue: string): JSONSerializable<T> {
  return JSON.parse(serializedValue);
}

And the real code would look like the following:
let me: Laborer
// ...
// @ts-expect-error - this "works" already as expected
let serializedMe = stringify(me);
save(serializedMe);
// ...
serializedMe = load();
me = parse<Laborer>(serializedMe); // this should give me a compile error. This is useful to me, because I tried to de-/serialize a value, which wasn't serializable with JSON
me.work(); // will throw a runtime error. I would like to already catch this at compile time

never is the bottom type and is intentionally assignable to all other types.  This is because the type is an empty set and has no inhabitants - by definition you can never have a value of type never.  If the return type of getLaborer were accurate, the function could never return normally since it's impossible to construct a LazyLaborer.

To clarify since this is a common point of confusion: { work: never } doesn't mean an object that never has a work property.  It means an object that always has a work property whose value is type never.  You can't legally create such an object at runtime since no such value exists.

It means an object that always has a work property whose value is type never. You can't legally create such an object at runtime since no such value exists.

Or a property that throws upon access. It's fine to create a throwing getter.

Thanks for your fast replies :)

It means an object that always has a work property whose value is type never. You can't legally create such an object at runtime since no such value exists.

That is exactly my point. Yet, the example creates such a value of the impossible LazyLaborer type and assigns it to a variable of the valid Laborer type.  There is no way, the example would not produce an (unintended) runtime exception. Therefore, I expect TypeScript to not compile.
I fail to see, that assigning an impossible type to a possible type can be a correct, type safe assignment. I feel like, I am missing something here?
 But the ability to write a function parse<T>(serializedValue: string): JSONSerializable<T> and having a compile error when I try to generate a not possible type,  would be quite valuable to me.

The problem with the example, and why it’s not an error as written, is because JSON.parse returns any.  That’s a separate issue; the part where { work: never } is assignable to { work: LiterallyAnythingElse } is working as intended.  Normally you wouldn’t be able to assign anything to LazyLaborer without a compile error, but any is the “shut up and leave me alone, TypeScript” type. :smile:

I fail to see, that assigning an impossible type to a possible type can be a correct, type safe assignment.

It’s a bit weird, but the mathematical explanation is that it’s the same as how the empty set is a subset of all other sets.  More prosaically, if you have a function of type () => never, then that function by definition must always throw, so you can use it in place of () => T for any T.  And since () => T is isomorphic to T…

TLDR; We can close this issue as works as intended, right?
Thanks a lot for your detailed answers! :)
Nevertheless, I think it would be useful, if assigning an impossible value to something would  be a caught error by the compiler. I see no intentional use of writing a program, whose static types cannot reflect its runtime types. From my point of view, programming languages should be useful and help me to prevent errors: In the example me.work() will lead to a runtime error, which could have been caught by the compiler. I mean, let i = 0; ... i = 1; ... is mathematically questionable, yet surely useful in a for loop 😜
Do you think a feature request for that would be valid? If not, I will trust your judgement 👍
P.S.:

The problem with the example, and why it’s not an error as written, is because JSON.parse returns any. That’s a separate issue;

I think you missed the implicit cast due to the type annotation in the function header 😉
P.P.S:
Just in case someone finds this helpful: Instead of mapping the not JSONable keys to never, now, I map the whole type to never like JSONSerializable<T> = T extends JSONValue ? T : never. This prevents false assignments.

You still seem to mistakingly believe that having a never typed property makes it an "impossible value", but that's not the case.
type T = { value: never }
const t: T = { get value(): never { throw new Error() } }

I think you missed the implicit cast due to the type annotation in the function header 😉

That's not a cast, it's just a normal return type annotation.  If JSON.parse() returned something other than any (like unknown), then the program would have had an error.  The root of the issue in that particular example is that an unsound assignment to { work: never } isn't caught because the assignment source is any.
The bottom type means you can never access this value without throwing.  As long as that invariant is maintained, then any assignment from never to any other type is sound, which is why the type system allows it.

Just in case someone finds this helpful: Instead of mapping the not JSONable keys to never, now, I map the whole type to never like JSONSerializable = T extends JSONValue ? T : never. This prevents false assignments.

The ideal solution for this use case would be https://github.com/microsoft/TypeScript/issues/23689, but I don't know if we'll ever get it ☹

awesome, I learned something. I agree that it works as intended and https://github.com/microsoft/TypeScript/issues/23689, is the feature I am looking for. Thanks a lot for taking the time!


Compability with Linux

Hello! So I want to use this scanner on my Linux Mint 21.1 computer. I tried running the program with Wine, but it gives off this error:
Unhandled Exception:
System.ArgumentException: The requested FontFamily could not be found [GDI+ status: FontFamilyNotFound]
  at System.Drawing.GDIPlus.CheckStatus (System.Drawing.Status status) [0x001ce] in <bfbb50e127a74386baaf6a1ce3e1493f>:0
  at System.Drawing.FontFamily..ctor (System.Drawing.Text.GenericFontFamilies genericFamily) [0x0004d] in <bfbb50e127a74386baaf6a1ce3e1493f>:0
  at (wrapper remoting-invoke-with-check) System.Drawing.FontFamily..ctor(System.Drawing.Text.GenericFontFamilies)
  at System.Drawing.FontFamily.get_GenericSansSerif () [0x00000] in <bfbb50e127a74386baaf6a1ce3e1493f>:0
  at System.Drawing.Font.CreateFont (System.String familyName, System.Single emSize, System.Drawing.FontStyle style, System.Drawing.GraphicsUnit unit, System.Byte charSet, System.Boolean isVertical) [0x00011] in <bfbb50e127a74386baaf6a1ce3e1493f>:0
  at System.Drawing.Font..ctor (System.String familyName, System.Single emSize, System.Drawing.FontStyle style, System.Drawing.GraphicsUnit unit, System.Byte gdiCharSet, System.Boolean gdiVerticalFont) [0x00011] in <bfbb50e127a74386baaf6a1ce3e1493f>:0
  at System.Drawing.Font..ctor (System.String familyName, System.Single emSize, System.String systemName) [0x00000] in <bfbb50e127a74386baaf6a1ce3e1493f>:0
  at (wrapper remoting-invoke-with-check) System.Drawing.Font..ctor(string,single,string)
  at System.Drawing.SystemFonts.get_DefaultFont () [0x00000] in <bfbb50e127a74386baaf6a1ce3e1493f>:0
  at System.Windows.Forms.Control.get_DefaultFont () [0x0000e] in <5ea26500d4d340168c8a375e356ca0ac>:0
  at System.Windows.Forms.Control.get_Font () [0x00088] in <5ea26500d4d340168c8a375e356ca0ac>:0
  at System.Windows.Forms.Control.get_FontHeight () [0x000a9] in <5ea26500d4d340168c8a375e356ca0ac>:0
  at System.Windows.Forms.TextBoxBase.get_PreferredHeight () [0x00001] in <5ea26500d4d340168c8a375e356ca0ac>:0
  at System.Windows.Forms.TextBoxBase.get_DefaultSize () [0x00001] in <5ea26500d4d340168c8a375e356ca0ac>:0
  at System.Windows.Forms.Control..ctor (System.Boolean autoInstallSyncContext) [0x000e3] in <5ea26500d4d340168c8a375e356ca0ac>:0
  at System.Windows.Forms.Control..ctor () [0x00000] in <5ea26500d4d340168c8a375e356ca0ac>:0
  at System.Windows.Forms.TextBoxBase..ctor () [0x0003a] in <5ea26500d4d340168c8a375e356ca0ac>:0
  at System.Windows.Forms.TextBox..ctor () [0x0004a] in <5ea26500d4d340168c8a375e356ca0ac>:0
  at (wrapper remoting-invoke-with-check) System.Windows.Forms.TextBox..ctor()
  at JarInfectionScanner.Form1.InitializeComponent () [0x00016] in <30c8316a67b642a994f453a2ba918268>:0
  at JarInfectionScanner.Form1..ctor () [0x00006] in <30c8316a67b642a994f453a2ba918268>:0
  at (wrapper remoting-invoke-with-check) JarInfectionScanner.Form1..ctor()
  at JarInfectionScanner.Program.Main () [0x0000b] in <30c8316a67b642a994f453a2ba918268>:0
[ERROR] FATAL UNHANDLED EXCEPTION: System.ArgumentException: The requested FontFamily could not be found [GDI+ status: FontFamilyNotFound]
  at System.Drawing.GDIPlus.CheckStatus (System.Drawing.Status status) [0x001ce] in <bfbb50e127a74386baaf6a1ce3e1493f>:0
  at System.Drawing.FontFamily..ctor (System.Drawing.Text.GenericFontFamilies genericFamily) [0x0004d] in <bfbb50e127a74386baaf6a1ce3e1493f>:0
  at (wrapper remoting-invoke-with-check) System.Drawing.FontFamily..ctor(System.Drawing.Text.GenericFontFamilies)
  at System.Drawing.FontFamily.get_GenericSansSerif () [0x00000] in <bfbb50e127a74386baaf6a1ce3e1493f>:0
  at System.Drawing.Font.CreateFont (System.String familyName, System.Single emSize, System.Drawing.FontStyle style, System.Drawing.GraphicsUnit unit, System.Byte charSet, System.Boolean isVertical) [0x00011] in <bfbb50e127a74386baaf6a1ce3e1493f>:0
  at System.Drawing.Font..ctor (System.String familyName, System.Single emSize, System.Drawing.FontStyle style, System.Drawing.GraphicsUnit unit, System.Byte gdiCharSet, System.Boolean gdiVerticalFont) [0x00011] in <bfbb50e127a74386baaf6a1ce3e1493f>:0
  at System.Drawing.Font..ctor (System.String familyName, System.Single emSize, System.String systemName) [0x00000] in <bfbb50e127a74386baaf6a1ce3e1493f>:0
  at (wrapper remoting-invoke-with-check) System.Drawing.Font..ctor(string,single,string)
  at System.Drawing.SystemFonts.get_DefaultFont () [0x00000] in <bfbb50e127a74386baaf6a1ce3e1493f>:0
  at System.Windows.Forms.Control.get_DefaultFont () [0x0000e] in <5ea26500d4d340168c8a375e356ca0ac>:0
  at System.Windows.Forms.Control.get_Font () [0x00088] in <5ea26500d4d340168c8a375e356ca0ac>:0
  at System.Windows.Forms.Control.get_FontHeight () [0x000a9] in <5ea26500d4d340168c8a375e356ca0ac>:0
  at System.Windows.Forms.TextBoxBase.get_PreferredHeight () [0x00001] in <5ea26500d4d340168c8a375e356ca0ac>:0
  at System.Windows.Forms.TextBoxBase.get_DefaultSize () [0x00001] in <5ea26500d4d340168c8a375e356ca0ac>:0
  at System.Windows.Forms.Control..ctor (System.Boolean autoInstallSyncContext) [0x000e3] in <5ea26500d4d340168c8a375e356ca0ac>:0
  at System.Windows.Forms.Control..ctor () [0x00000] in <5ea26500d4d340168c8a375e356ca0ac>:0
  at System.Windows.Forms.TextBoxBase..ctor () [0x0003a] in <5ea26500d4d340168c8a375e356ca0ac>:0
  at System.Windows.Forms.TextBox..ctor () [0x0004a] in <5ea26500d4d340168c8a375e356ca0ac>:0
  at (wrapper remoting-invoke-with-check) System.Windows.Forms.TextBox..ctor()
  at JarInfectionScanner.Form1.InitializeComponent () [0x00016] in <30c8316a67b642a994f453a2ba918268>:0
  at JarInfectionScanner.Form1..ctor () [0x00006] in <30c8316a67b642a994f453a2ba918268>:0
  at (wrapper remoting-invoke-with-check) JarInfectionScanner.Form1..ctor()

Can you do something about it? Or perhaps there's a problem on my side? Thanks.

Would be best if we had a native linux version of this detector, for now, if you're a mod dev on Linux, hold off until the app is made into a linux binary, or have a windows user in your dev team run the checker for you.

I was able to run it with Mono
mono JarInfectionScanner.exe

I couldn't make it run on my computer, so I've converted the check to Python:
https://gist.github.com/ivanpu/c5347bf107fa900ac79f1fcf2f056e7c
DISCLAIMER:
It didn't find any infected jars on my computer, so I can't guarantee that it actually finds stage-0 infection.
I assume that my code is correct if the code in this repo is correct.

Does work with Mono it seems, just the browse button doesn't work, but manually typing in the path scans everything fine.

Indeed works if not clicking the "Browse" button.
But it stops on the first IOExcetption it encounters, instead of skipping that folder :facepalm:

I made a scanner that works with Linux if anyone here is interested. It does mostly the same thing, with a UI as well.
I know this is a bit of self-promotion, but the fact that this tool didn't work for linux bothered me so I made it for Linux.
If you wanted to get it you can use this link, but if I shouldn't self-promo here, then lmk and I'll remove this comment.