Not able to get jobs with task_id using CVAT_SDK,

My actions before raising this issue

[X] Read/searched the docs
[X] Searched past issues

Documentation is very bad, I'm going through all docs, and I don't know why I'm getting the error.
I got paginated tasks using project id, but not for jobs with task_id, using the same types of functions.

from functools import reduce
from flask import request, jsonify
from helpers.auth import auth
from cvat_sdk.api_client import ApiClient, Configuration
from cvat_sdk.core.helpers import get_paginated_collection
def get_all_jobs(project_id, task_id):
print(project_id, task_id)
tokens = auth(request.headers.get("Authorization"))
if not tokens:
    return {"error":"Unauthorized"}, 401

configuration = Configuration(host="http://localhost:8080",
                              api_key={
                                "sessionAuth": tokens[2],
                                "csrfAuth": tokens[3],
                                "tokenAuth": tokens[4],
                              })

with ApiClient(configuration) as api_client:
    data= get_paginated_collection(api_client.tasks_api.list_jobs_endpoint, id=task_id, return_json=True)

    data = reduce(lambda x, y: x + y, data)

return jsonify({"data": data}), 200, { "Content-Type": "application/json"}

Getting error:-
raise ApiTypeError(
cvat_sdk.api_client.exceptions.ApiTypeError: Got an unexpected parameter 'page' to method list_jobs
Steps to Reproduce (for bugs)

Check above

PLease provide an update soon.

Operating System and version (e.g. Linux, Windows, MacOS):
Code example or link to GitHub repo or gist to reproduce problem:
Other diagnostic information / logs:
Logs from `cvat` container

@SpecLad , could you please look at the issue?


[Apple Notes] Do not search recently deleted

Extension – Apple Notes

Author:@tumispro

Describe the feature and the current behavior/state.
Currently when getting on the search screen, the top items are those from the Recently deleted list. While I could see cases when I'd want a search to include those, mostly I'm looking at the non-deleted files.

Taking a quick look at the code, it looks like the Recently deleted should be filtered out so I'm wondering why am I seeing these.

Is anyone looking at these extensions?


BIGTOP-3208. Exception in master branch (and branch-1.4): kafka-server failed to launch due to missing zookeeper AsyncCallback.MultiCallback

Revert "BIGTOP-3185. Bump Kafka to 2.1.1 (#493)"

This reverts commit ca52568591010884687ac7616d09d97c63a89ebf.

Revert "BIGTOP-3187. Bump Flume to 1.9.0"

This reverts commit 173d80e381cf8b527812e321f1908d90aeba9823.

Revert "BIGTOP-3171. Update Kafka Puppet module for version 1.1.1 (#477)"

This reverts commit 6d5705e3e023caae39410888713f7bbf77578e09.

Revert "BIGTOP-3164. Bump Kafka to 1.1.1 (#476)"

This reverts commit 12cb0ad24edb29e8cdac8d571a0472814629a40f.

As I understand we need a new zookeeper. Would you mind to rebase and commit your patches to bigtop-alpha  branch instead ? We can update zookeeper here.

Yeah. Sure, lets see whether we can build up Kafka there. I'll merge this and try something in bigtop-alpha.


Some cursor themes contain empty cursor files (numix-cursor-theme, capitaine-cursors)

Describe the bug
Some cursor packages (e.g. numix-cursor-theme and capitaine-cursors) contain zero-byte cursor files, causing applications to fall back to the default X cursor theme.
To Reproduce
Build the numix-cursor-theme package.
nix-build 'https://github.com/NixOS/nixpkgs/archive/master.tar.gz' -A numix-cursor-theme

Inspect the resulting files in result/share/icons/Numix-Cursor/cursors.
ls -l result/share/icons/Numix-Cursor/cursors

Expected behavior
The cursor files are valid (notably not empty).
Actual behavior
The cursor files are empty (size of zero bytes).
Additional context
The issue started with commit 35deaa45a182d18858ae56c300ab786bdb6cb621. Other packages are affected (e.g. capitaine-cursors). The build output contains errors and warnings:
# For numix-cursor-theme
Unknown option -f
FAIL: src/config/alias.cursor xcursorgen: PNG error while reading x1/alias.png

# For capitaine-cursors
Warning: Option --without-gui= is deprecated
Unknown option -e
xcursorgen: PNG error while reading x1/alias.png

This reproduces the issue:
nix-build 'https://github.com/NixOS/nixpkgs/archive/35deaa45a182d18858ae56c300ab786bdb6cb621.tar.gz' -A numix-cursor-theme

The generated cursor files are valid with the previous commit:
nix-build 'https://github.com/NixOS/nixpkgs/archive/a45e68be364d751414a406bf78fadf9b60f8c606.tar.gz' -A numix-cursor-theme

Notify maintainers
@jtojnar
Metadata

system: "x86_64-linux"
host os: Linux 5.3.0-7648-generic, Pop!_OS, 18.04 LTS
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.7
channels(root): "nixpkgs-20.09pre236138.970b2b853d4"
channels(stephane): "home-manager, nixpkgs-21.03pre243895.72b9660dc18"
nixpkgs: /home/stephane/.nix-defexpr/channels/nixpkgs

Maintainer information:
# a list of nixpkgs attributes affected by the problem (non-exhaustive)
attribute:
  - numix-cursor-theme
  - capitaine-cursors

It turns out that https://gitlab.com/inkscape/inkscape/-/merge_requests/2056 did not re-introduce all of the legacy flags – it does not support using long options without equal sign and the short aliases.
I would suggest either patching the build script as described in https://github.com/NixOS/nixpkgs/issues/86930 or adding the other legacy options to Inkscape.

Thank you for your answer. I submitted a PR to numix-cursor-theme. Regarding capitaine-cursors, it looks like there's already a fix in the upstream repository but no new release yet.


Fix micro (color) file syntax

Some of the words were missing, so this adds those.
I added everything that was in the doc, but I have the feeling I might be missing something. For example, what's start= and end= do?

start= and end= are from the old syntax file format before we switched to yaml. In the past syntax files were also .micro files (not just colorschemes).

Should I remove those or not bother?

It's fine to keep I guess.


Resolve attribute from resource using "dot" notation

Hi @hello-liang-shan
Thank you for you contribution. We already merge a similar pull request. See v0.2.0.


Metrics Dashboard (Grafana) showing "None" in top bar

The metrics top bar seems to be a little broken -- when opening the dashboard without a project, (link) I get:
.
When opening a project from the front-end website (link), I get:

(Note "None" next to "Select Project.)

@scovetta I believe this can be closed. The behavior now defaults to using the purl pkg:github/translationexchange/tml-js-angular if no project is included in the link. I'm creating a follow up ticket because now that a purl is the key, I don't believe the Project box is doing anything


Toggle layer visibility with a keyboard shortcut

Having the ability to turn on/off the visibility of a given layer within a canvas is extremely useful. However, one has to click the checkbox with a mouse pointer, which gets a bit tedious especially when one wants to repeatedly toggle the visibility of a layer (e.g. to visually compare it to the layer below). It would be very convenient to have keyboard shortcuts support for this action, e.g. CMD/CTRL + <layer_id>.

Great suggestion!

Thank you for adding this feature, it's incredibly useful!
I noticed that if a page has multiple canvases, the shortcut toggles the given layer across all the canvases simultaneously. Would it be possible to modify the behaviour so that the visibility is toggled only within a single "in focus" canvas?


bug: code output is often truncated

Version
v1.12.0
Describe the bug
Code is shown in a code box that is often truncated before it is done. This does not happen with text generated outside of code blocks.
Say I have a coversation like this,
Q) Explain concept and write code that does something
A) Concept explained
code block with truncated lines
Q) Document the above code and write comments
same code block with comments again truncated
The first code block can be truncated mid-line or mid-file.
Examples (last line of code block shown below)
mid-line example
if (dog !=
mid-file
while (b < a) {
Expected behavior
no truncation or an option to regenerate the answer / continue
Additional context

related #3648

Thanks for reporting! We have increased Cody's output limit, it should now be much rarer to see Cody truncating the response like this. Let us know if you encounter any more issues!
This change will be available in this weeks Cody release, which is scheduled to go out either today or tomorrow.

@umpox Thanks a ton!
Will this require an extension update (i use vscode) or is this a backend update?

it's available in v1.14! upgrade away :)


No spiders option

The sole reason I downloaded Bag of Tricks for Kingmaker was the option to replace giant spider models with another enemy (wolves in that case). Any chance you'll be adding that feature to a future update?

I think we can do this.

Can you come onto our discord: https://discord.gg/yd2Gj3PT and send me a hard save file where you are near some spiders so I can test this.  My user name is Narria on that server.

Sounds good - I'll need to reinstall the game, but there's one mere minutes after the opening scene - one of the downsides of being an arachnophobic fan of crpgs. And seriously, thanks for looking into this.


Finalize decision on package.json field name

Known constraints:

May not collide with existing ecosystem usage.
Should be a valid JavaScript identifier, e.g. camelcase or single word.

Options we discussed while drafting the proposal:

exports
nodejs.module, avoids the awkwardness between singular and plural and is namespaced so as not to conflict with the commonly used top-level module
export
entries
moduleExports

We wrote the proposal with esm-exports as a deliberately awful name to encourage replacement, but changed it at the last minute as we realized it wasn’t a valid identifier (that would’ve been esmExports but that felt too awful even as a placeholder).

externalImports

Would align with the "imports" property in import maps. external because it only affects imports from outside of the package.
This leaves room for adding internalImports as import map for package internal specifiers.

@sokra we previously considered "imports" or something like Parcel's "aliases" as the internal dual here. Definitely open to further discussion on that. "exports" already has consensus though for now, so it would be shame to go back to that bikeshed at this point, but we could for good reasons.

To echo @guybedford I feel like we should close this issue. There doesn't seem to be much pushback to exports and it's what already is implemented. I would like to treat it as an exception if we'd have to change the field name(s) at this point.


(refactor) Move backend into server folder

@heatherpark Please review my pull request!

Great job, Chase!


[2.4.2] cattle-cluster-agent goes unhealthy, clusters show up in Rancher as "Unavailable"

What kind of request is this (question/bug/enhancement/feature request): Bug
Steps to reproduce (least amount of steps as possible):
Difficult to determine precise steps for reproducing. We took the path of provision new K8s 1.17.4 cluster, and let it sit for > 10 days. Eventually, the cluster went unavailable and the cattle-cluster-agent logs showed: watch of *summary.SummarizedObject ended with: unexpected object:
Other details that may be helpful:
W0413 15:27:31.112849       1 reflector.go:326] github.com/rancher/steve/pkg/clustercache/controller.go:187: watch of *summary.SummarizedObject ended with: unexpected object: &{{{Status v1} {      0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] []  []}} }
W0413 15:36:11.421095       1 reflector.go:326] github.com/rancher/steve/pkg/clustercache/controller.go:187: watch of *summary.SummarizedObject ended with: unexpected object: &{{{Status v1} {      0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] []  []}} }
W0413 15:36:23.141545       1 reflector.go:326] github.com/rancher/steve/pkg/clustercache/controller.go:187: watch of *summary.SummarizedObject ended with: unexpected object: &{{{Status v1} {      0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] []  []}} }
W0413 15:50:48.470615       1 reflector.go:326] github.com/rancher/steve/pkg/clustercache/controller.go:187: watch of *summary.SummarizedObject ended with: unexpected object: &{{{Status v1} {      0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] []  []}} }
W0413 15:51:27.245361       1 reflector.go:326] github.com/rancher/steve/pkg/clustercache/controller.go:187: watch of *summary.SummarizedObject ended with: unexpected object: &{{{Status v1} {      0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] []  []}} }
W0413 15:59:11.566124       1 reflector.go:326] github.com/rancher/steve/pkg/clustercache/controller.go:187: watch of *summary.SummarizedObject ended with: unexpected object: &{{{Status v1} {      0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] []  []}} }
W0413 16:07:32.347236       1 reflector.go:326] github.com/rancher/steve/pkg/clustercache/controller.go:187: watch of *summary.SummarizedObject ended with: unexpected object: &{{{Status v1} {      0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] []  []}} }

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.4.2
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Custom
Machine type (cloud/VM/metal) and specifications (CPU/memory): Not Relevant
Kubernetes version (use kubectl version): 1.17.4

Having exactly the same problem with Rancher 2.4.2 after upgrading. On top of that, there seems to be a memory leak on the cluster agent pod which ends up in consuming the whole RAM of the machine, rendering it unusable:

Just as @Oats87 wrote, there doesn't seem to be much happening in the pod itself, it barely logs one line every 5 minutes, but it's always exactly the same line - with summary.SummarizedObject ended with: unexpected object.

This is a duplicate of https://github.com/rancher/rancher/issues/26633, closing.

Is there a fix for this. Did the memory leak been identified.
Eks clusters show up in Rancher as "Unavailable" Restarting cattle node agent and rancher is not a solution


C#: add distribtest for  .NET 5 and dotnet core runtime 3.1 (netcoreapp3.1)

To add coverage for fixes such as https://github.com/grpc/grpc/pull/24485.

Rebased now that #24485 is merged.
Adhoc distribtest run: https://g3c.corp.google.com/results/invocations/2e0501c5-0572-4944-adbf-b668b78938dc

Distribtests are green. Merging.


Error with Galois 16-bit

Hey there, with Rust 1.68.2, I get the following error when trying the original test code with Galois_16:
error[E0277]: the trait bound `Vec<{integer}>: AsRef<[[u8; 2]]>` is not satisfied
   --> src/tests.rs:616:11
    |
616 |         r.encode(&mut master_copy).unwrap();
    |           ^^^^^^ the trait `AsRef<[[u8; 2]]>` is not implemented for `Vec<{integer}>`
    |
    = help: the following other types implement trait `AsRef<T>`:
              <Vec<T, A> as AsRef<Vec<T, A>>>
              <Vec<T, A> as AsRef<[T]>>
note: required by a bound in `ReedSolomon::<F>::encode`
   --> /home/peter/.cargo/registry/src/github.com-1ecc6299db9ec823/reed-solomon-erasure-6.0.0/src/core.rs:600:12
    |
600 |         U: AsRef<[F::Elem]> + AsMut<[F::Elem]>,
    |            ^^^^^^^^^^^^^^^^ required by this bound in `ReedSolomon::<F>::encode`

I used reed-solomon-erasure = "6.0.0" + this test:
use reed_solomon_erasure::galois_16::ReedSolomon;

#[test]
fn test_dsafd() {
    let r = ReedSolomon::new(3, 2).unwrap(); // 3 data shards, 2 parity shards

    let mut master_copy = shards!(
        [0, 1, 2, 3],
        [4, 5, 6, 7],
        [8, 9, 10, 11],
        [0, 0, 0, 0], // last 2 rows are parity shards
        [0, 0, 0, 0]
    );

    // Construct the parity shards
    r.encode(&mut master_copy).unwrap();

    // Make a copy and transform it into option shards arrangement
    // for feeding into reconstruct_shards
    let mut shards: Vec<_> = master_copy.iter().cloned().map(Some).collect();

    // We can remove up to 2 shards, which may be data or parity shards
    shards[0] = None;
    shards[4] = None;

    // Try to reconstruct missing shards
    r.reconstruct(&mut shards).unwrap();

    // Convert back to normal shard arrangement
    let result: Vec<_> = shards.into_iter().filter_map(|x| x).collect();

    assert!(r.verify(&result).unwrap());
    assert_eq!(master_copy, result);
}

Thank you, I'll take a look right now. Maybe change the README to make it less confusing?

Feel free to submit a PR, I think having two examples: for gf8 and gf16 separately would be helpful.

It is clear for me now after reading the tests, I'll close this issue. I'll make a PR later!


feat(build-time): #647

Proposed changes
Implemented the function createUseComponent that replaces createUseClasses and adds:
Flat style object
const useComponent = createUseComponent({
    bg: 'primary'
})

instead of
const useComponent = createUseClasses({
   component: {
       bg: 'primary'
   }
})

Possibility to pass functions to the style object for an interaction between build-time and run-time:
const useComponent = createUseComponent({
    bg: props => props.bg
})

Return value
createUseComponent returns an object that contains the className, the style and other default component properties (if componentName is specified):
const useButton = createUseComponent({
   componentName: 'Button'
})

function Button() {
  const { className, style } = useButton();
   return <button className={className} style={style} />
}

Closes #647
Types of changes

[ ] 🐛 Bugfix (non-breaking change which fixes an issue)
[x] ✨ New feature (non-breaking change which adds functionality or enhancements)
[x] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] ✅ Tests (added tests for an existing feature)
[ ] 📚 Documentation Update (if none of the other choices apply)
[ ] 🙌 Other (please, write a clear and concise description of the proposal in the section above)

Checklist

[x] 👀 I have read the CONTRIBUTING doc
[x] ✅ Lint and unit tests pass locally with my changes
[x] 🧪 I have added tests that prove my fix is effective or that my feature works
[x] 📚 I have added the necessary documentation (if appropriate)
[x] 🔀 Any dependent changes have been merged and published in downstream modules

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (b9d98d2) 100.00% compared to head (d8b760b) 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff            @@
##              main      #692   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           96       100    +4
  Lines          754       836   +82
  Branches       131       146   +15
=========================================
+ Hits           754       836   +82

Impacted Files
Coverage Δ

packages/utils/src/deepMerge.ts
100.00% <ø> (ø)

packages/utils/src/parseNumber.ts
100.00% <ø> (ø)

packages/babel-plugin/src/constants.ts
100.00% <100.00%> (ø)

packages/babel-plugin/src/utils/css.ts
100.00% <100.00%> (ø)

packages/babel-plugin/src/utils/dynamicClasses.ts
100.00% <100.00%> (ø)

packages/babel-plugin/src/utils/getStyleObject.ts
100.00% <100.00%> (ø)

...ages/babel-plugin/src/utils/isThemeableProperty.ts
100.00% <100.00%> (ø)

packages/babel-plugin/src/utils/splitStyles.ts
100.00% <100.00%> (ø)

packages/babel-plugin/src/utils/toJS.ts
100.00% <100.00%> (ø)

packages/babel-plugin/src/visitor.ts
100.00% <100.00%> (ø)

... and 12 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Add Void Linux resources

Void Linux comes with two flavors: glibc and musl-libc. I have created separate WSL repositories for each, which will produce releases after this changes is merged and WSLDL's new release is published.

Thanks!

Thank you!
Could you please push a tag so we get new release artifact? I will then be able to consume it in Void Linux WSL repos. :)


Added font size to bar

This PR adds variable font size to the bar.
Font size is defined as a float in the font.size setting in the Bar block alongside the font itself.

lgtm, thank you!


Fix error when deleting all "sv-part" list.

Fixed a bug that caused an error when deleting all with an application that has the function to delete "sv-part".
angular
    .module('testApp', ['angular-sortable-view'])
    .controller('AppController', function($scope) {
        $scope.lists = [
            [1, 2, 3],
            [4, 5, 6],
            [7, 8, 9]
        ];
        $scope.allDelete = function() {
            $scope.lists = []
        };
    });

                {{card}}

        <button ng-click="allDelete()">all delete</button>

The following error occurs when pressing "all delete" button.
TypeError: Cannot read property 'filter' of undefined

@kamilkp this would avoid errors in certain component destroy cases. Can you please merge it?


[WIP]Implementing Naive Bayes

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines or the commits will be squashed into one.
[ ] Tests for the changes have been added.
[ ] Docs have been added / updated.

What kind of change does this PR introduce?
Basic Implementation of Gaussian Naive Bayes

Does this PR introduce a breaking change?
No

Closing issues
Resolves #27

Pull Request Test Coverage Report for Build 410

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

Totals

Change from base Build 408:
0.0%

Covered Lines:
783

Relevant Lines:
809

💛  - Coveralls

Pull Request Test Coverage Report for Build 410

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

Totals

Change from base Build 408:
0.0%

Covered Lines:
783

Relevant Lines:
809

💛  - Coveralls

@mohdkashif93

Please use [flake8](http://flake8.pycqa.org/en/latest/) for PEP8 fixes.
Use intuitive variable names.

@mohdkashif93 ping


Small clarifications and typos fixes in the tutorials

small fixes

Pull Request Test Coverage Report for Build 474880598

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

Totals

Change from base Build 474724286:
0.0%

Covered Lines:
5986

Relevant Lines:
6646

💛  - Coveralls

Pull Request Test Coverage Report for Build 474880598

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

Totals

Change from base Build 474724286:
0.0%

Covered Lines:
5986

Relevant Lines:
6646

💛  - Coveralls


Jakarta EE java 17 support ?

Hello,
Are there any plans to support Java advancements like jdk 17 or jdk 25 as well as Jakartaee 10?
Jakarta.persistence, jakarta.transaction, jakarta.servlet etc. apis are not supported.

The Jakarta EE API Jars contain OSGi Manifests.
For special specifications like:
https://docs.osgi.org/specification/osgi.cmpn/8.1.0/service.servlet.html
https://docs.osgi.org/specification/osgi.cmpn/8.1.0/service.jakartars.html
we already have Jakarta support.
The JPA support is planned / work in progress.
https://docs.osgi.org/specification/osgi.cmpn/8.1.0/service.jpa.html
E.G. for transaction or jaxb, we dont have additional specifications. So everything should already work.

Yo can run all OSGi-Spec-Apis and Ihe compatible Implementations on JDK 17 and JDK 25. But also on JDK 8


Implement linq methods using generator functions?

What do you think about using generator functions for lazy execution?

Yep, I have been thinking about this for a long time.
My conclusions were:

I would like to use [Symbol.Iterator] and generator functions in the library
Those are part of ES6, but this library is targetting ES5

I don't know if there is any way to disable some parts of the code depending on the target (maybe with gulp?). It would be very nice to achieve this, but I have no idea how. Any ideas?
The best idea I have is to create a fork of this repo (and new package) targetting ES6

Maybe the best idea would be to release the ES5 version first with all the methods and features you want implemented. This could be, lets say 1.0.0 version. The 2.0.0 version would target ES6 and use generator functions. It would allow users to choose what to use without splitting the project and the user-base unnecessarily.

working on this (part of v2 refactor)


Support MatchType in metap

Follow up for https://github.com/scalameta/scalameta/pull/2681
Confirmed locally, and looks good :+1:
Symbols:
example/MatchType$package.Concat# => type Concat[Xs <: Tuple, +Ys <: Tuple] = Xs match { EmptyTuple => Ys, *:[x, xs] => *:[x, Concat[xs, Ys]] }
...
example/MatchType$package.Elem# => type Elem[X] = X match { String => Char, Array[t] => t, Iterable[t] => t }
...

Here's how I confirmed the behavior

sbt publishLocal (in scalameta/scalameta)

published, for example, 2.13, 4.5.0-SNAPSHOT

Go lampepfl/dotty with the branch https://github.com/lampepfl/dotty/pull/14608
sbt scalac -Xsemanticdb tests/semanticdb/expect/MatchType.scala
coursier launch --main-class scala.meta.cli.Metap org.scalameta:scalameta_2.13:4.5.0-SNAPSHOT -- META-INF/semanticdb/tests/semanticdb/expect/MatchType.scala.semanticdb

@tanishiking please let me know if you're planning an additional commit, I am looking to release a new version.

There's no additional commit :)


Automatically close MongoDbTemplate streams to mitigate/prevent issues with too many open cursors.

[X] Brief description of changes applied
Modified DefaultCasMongoDbTemplate to override doStream method.  Made the method call the super method with a try-with-resources method, then collected the results as a list, and returned a stream of the list.

Why?
The MongoDbTemplate.doStream method returns a ClosableIterator implementation with an open MongoDb cursor in it.  There is nothing in the usages of the code that close the stream after using it, thus after the stream is used, the class is garbage collected, but the MongoDb cursors can be left open, and is left to the MongoDB server to close upon timeout.  The cursor is left open when the cursor has to iterate through batches of data.  Under high authentication load, making use of all known BaseAuthenticationRequestRiskCalculator implementations when electrofence is enabled, it is possible to cause the MongoDB to run out of available cursors, causing the clients to start throwing errors.  This is somewhat akin to what eventually happens if one fails to close statements/result sets on a JDBC connection.  I considered adding the try-with-resources on implementations making use of the mongodbTemplate.stream() methods,  but I thought it might be better to have it close closer to the source to prevent it from accidentally causing the problem again with a new usage of it.  The current usages of the stream method are in MongoDbCasEventRepository and MongoDbTicketRegistry.

[X] Test cases for all modified changes, where applicable
Created test case that fails at the commit below.
https://github.com/dmalia1/cas/commit/7dfa6374a72211f3fe1e617992383ece5937f5b6
[X] Any documentation on how to configure, test
To run the test, make sure you have a mongodb instance running on localhost using credentials specified in the test.
Then run testcas.sh -category mongodb
[X] Any possible limitations, side effects, etc
This may slow down processing of data of from mongodb as it will have to fetch the entire resultset before processing.  CasEventRepostiory.load() for example would fetch the entire collection before processing, potentially running into OOM errors.  Other implementations of CasEventRepository do something similar, so I'm not sure this is a showstopper.  The Eclipse link jpa implementation does this as an example.

As a side note, the hibernate jpa implementation may have the same issue that this pull request corrects. However, the underlying stream is also making use of autoclosable, so it may work as intended even though the hibernate documentation explicitly says one should close the stream as soon as possible to free up resources. https://docs.jboss.org/hibernate/orm/6.1/javadocs/org/hibernate/query/Query.html#stream().   I have not run any tests to confirm that there is issue with the hibernate jpa implementation, just read the code while reviewing how the other CasEventRepository implementations are implementing 'stream' to make sure I wasn't doing something too horrible.

I just thought of something else I should look at with regards to this.  I'm going to close this for now.


Support ability to change ID prefix. See #630

There seems to be a little instability in the test, as jruby <IP_ADDRESS> worked on the push but not the pull_request

Any chance this UUID prefix enhancement can merge it into master? Not showing up on 1.15.0 - thanks


BUG on docs page

Please view this page
https://carbon-components-svelte.onrender.com/components/UIShell
Notice that the right side bar is off the screen.
Not sure if I should use the UI library if the UI library breaks.

I have no idea what you are referring to.
Please at least describe what you mean and ideally add a screenshot + browser version.

@brunnerh

Note this holds for Firefox too!

This only happens on "smaller" screens which is why I did not see it.
Some page content is not shrinking correctly (which has nothing to do with the component library itself, it's just the docs).

@brunnerh strange. Can the docs be fixed then? As "smaller" is like full-size laptop (14") and it is only on this page, suggesting it is the UIShell component taking up too much horizontal space (e.g. using width:vh)

Well, I work on 27" screens (of course the resolution and system/browser scale settings are more important than the physical size).
Does not look like this is isolated; the Accordion page also overflows for me if I reduce the width.
Should be fixable by adjusting the layout.

I've noted the bug and we'll fix it in time. Since responsive design impacts usability, I agree it should be fixed.

I can see similar behaviour on https://carbon-components-svelte.onrender.com/components/OrderedList as well, the numbering is outside the bounding box. That said, this probably isn't a component that gets much use anyhow....


Kinesis Firehose ExtendedS3Configuration support for FileExtension

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details
Kinesis Firehose ExtendedS3Configuration current does not support the optional FileExtension property. This property is described in the AWS Destination Settings documentation. This causes issues when you are trying to import files in S3 into other systems that require specific file extensions. For example, Datadog log rehydration only supports files with the extension .json.gz.

Hi @dygfloyd. Thanks for letting us know about this. The pulumi-aws provider is bridged from https://github.com/hashicorp/terraform-provider-aws. The best way to get this feature added is to open an issue there.

I posted a feature request in that repo as well. https://github.com/hashicorp/terraform-provider-aws/issues/35989
Unfortunately, I am unfamiliar with the terraform provider so if anyone has any details they can add to the request, that would be great.

Looks like there was a duplicate ticket and this feature was added 3 days ago:
https://github.com/hashicorp/terraform-provider-aws/pull/35969

Great. Then pulumi-aws will pick up the feature shortly after terraform-provider-aws's next release.

Closing as implemented upstream in https://github.com/hashicorp/terraform-provider-aws/issues/35957


feat: slim down vortex-array metadata

Never store an array's own length in metadata.

In memory, it is stored in the TypedArray.
On disk/network, the top-level array length is in the flatbuffer Batch.
On disk/network, non-top-level array lengths are derivable from their parent's length and metadata.

DTypes can often be PType.
Scalar can often be ScalarValue (because the dtype is derivable by the Array's dtype).

cc: @lwwmanning. I'll clean up tomorrow, but I think this is essentially right.

There's couple of places where we store usize which we shouldn't which also could just be u16 (or just gone)

There's couple of places where we store usize which we shouldn't which also could just be u16 (or just gone) - BitPackedArray is the prime example

Will took on the non-vortex-array arrays, but, @lwwmanning , I could take those on too if you prefer?

Oh, I missed this is just the vortex-array crate. This makes sense. Let me have a another look


Consolidation of Deconvolution1D

Closes #173

Thank you both for all your comments @jakobsj, @amal-ghamdi.
I took them all into account and it improved this PR significantly. Please have another look!

Thank you both for all your comments @jakobsj, @amal-ghamdi.
I took them all into account and it improved this PR significantly. Please have another look!

Thank you both for all your comments @jakobsj, @amal-ghamdi.
I took them all into account and it improved this PR significantly. Please have another look!

Thank you both for all your comments @jakobsj, @amal-ghamdi.
I took them all into account and it improved this PR significantly. Please have another look!

Added the phantom suggested in our discussions.


Partition picklist in table Oracle

Is it possible to add in the detail of the table the possibility to see only the data of a specific partition? Example :
Detail Table - select partition 20201231 and show only the data of that partition. A picklist of partitions ...

Good idea! We are going to implement it.

Good idea! We are going to implement it.

there is a problem for this issue?

news?


grad is working, jacobian is not

First of all, autograd is an amazing tool! The grad function works great, but I am not able to make the jacobian function work.  I am on Python 3.4.3, numpy 1.10.1 and autograd 1.1.1 (pip).
The call to the jacobian function works, but the function it returns does not accept my argument and throws a TypeError: The first input argument needs to be a sequence
The error seems to occur in the concatenate function, defined at line 44 in autograd/core.py (although I do believe this error is actually an error raised by numpy).
A minimum example to reproduce this:
import autograd.numpy as np
from autograd import grad
from autograd import jacobian

x = np.array([5, 3], dtype=float)

def cost(x):
    return x[0]**2 / x[1] - np.log(x[1])

grad_cost = grad(cost)
jaco_cost = jacobian(cost)

print(grad_cost(x)) # works correctly!
print(jaco_cost(x)) # error

Another unrelated question (I am not sure if this is the correct place for this): If I wrote the above cost function in a separate module that imports numpy by itself (so not the autograd.numpy). Is it possible to somehow import this function from the module directly, instead of copy-pasting the code? Right now I get the following AttributeError: 'FloatNode' object has no attribute 'log'
The import is as follows:
import autograd.numpy as np
from autograd import grad

#This module contains an 'import numpy as np' line
from my_module import cost

x = np.array([5, 3], dtype=float)
#Function from 'my_module' for which I'd like to calculate the gradient
grad_cost = grad(cost)
grad_cost(x) # error

If I remove the np.log call from my cost function the error disappears. So I guess I somehow need to override the 'regular' numpy import with the autograd numpy import, if possible.

As to your question, you need the cost function (and anything it calls that uses numpy code) to use autograd's wrapped numpy. The easiest fix would be to change the import statement in my_module.py.
As a hack, your code could munge the numpy module before importing my_module, as in
import autograd.numpy as np
from autograd import grad

import numpy as unwrapped_numpy
unwrapped_numpy.log = np.log
from my_module import cost

The import of my_module has to happen after munging the loaded numpy module in case any numpy functions are bound directly to names in my_module.py, i.e. in case there are lines in my_module.py like from numpy import log. If the code in my_module.py only uses import numpy as np and references numpy functions through that module reference, then the import order doesn't matter.
This hack is not a good long-term recipe, and it might even depend on CPython module loading details. (I didn't test it, but something along these lines should work.)

Actually, I wasn't able to test this fix, so I'm reopening the issue until I can test it later today. If you notice it's still broken, please paste the full error traceback.

Thank you for the swift response! I tested the fix but I don't think it works.. (Note that I manually hacked fix #64 in my code, as I am using pip. But from the error output you can see that the change is there).
Here is the full error traceback:
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-1-d12611e5619b> in <module>()
     14
     15 print(grad_cost(x)) # works correctly!
---> 16 print(jaco_cost(x)) # error

/Users/bruno/anaconda3/lib/python3.4/site-packages/autograd/core.py in gradfun(*args, **kwargs)
     51         grads = list(map(partial(backward_pass, start_node, tape=tape), end_nodes))
     52         shape = dummy.outshape + getshape(args[argnum])
---> 53         return np.reshape(concatenate(grads), shape) if shape else grads[0]
     54     return gradfun
     55

/Users/bruno/anaconda3/lib/python3.4/site-packages/autograd/core.py in <lambda>(lst)
     42         return list(np.ravel(val))
     43
---> 44     concatenate = lambda lst: np.concatenate(map(np.atleast_1d, lst))
     45
     46     @attach_name_and_doc(fun, argnum, 'Jacobian')

TypeError: The first input argument needs to be a sequence

As regarding my question, I will look into your proposed hack solution, thanks!

Oh, the traceback shows the problem! the call to map on line 44 needs a call to list wrapped around it. That's how it is in the current git master, but apparently the pip version doesn't include that fix.
I'll revert the change I made; it wasn't necessary because the fix is already in master. We'll have to update the pip version.
I'm going to close the issue because the bug doesn't exist on master, and we'll update the pip version at some point soon.

Perfect, it works and sorry for the confusion.
For other who might be interested, I used pip to install the latest master as follows:
pip install git+git://github.com/HIPS/autograd.git

I'm not sure whether this is the right place for this follow up (as the original issue has been closed) but I put some more thought into my question regarding switching between the stripped down autograd.numpy and the original numpy. This is what I came up with.
My my_module.py starts as follows:
import config

if not config.AUTOGRAD:
    import numpy as np
    from scipy import special
else:
    import autograd.numpy as np
    from autograd.scipy import special

# rest of my_module remains unchanged.

The config module that is imported contains the following boolean:
# Set autograd to active or not
AUTOGRAD = True

If is True, the autograd.numpy is loaded, else the normal numpy is loaded.
For my use case, this means I no longer have to copy paste functions from my_module.py to an external Python file. I can just set AUTOGRAD to True and import the functions on which I want to apply autograd methods. I believe that this handles my situation pretty well, as I don't impose any restrictions on the functions within my_module.py. If I want to use autograd on any of them, I can now directly import these functions if AUTOGRAD is set to True.
The price I pay is that if AUTOGRAD is set to True, then functions in my_module.py that rely on contents from 'regular numpy' that is not in autograd.numpy won't work. But at least I implicitly acknowledged this by setting AUTOGRAD to True.
Another option could be to move all the functions in my_module.py that are autograd 'related' to a different module, but to me that feels like I'm changing too much in the structure of my code. This seems like a nice solution that handles my situation pretty well, with very limited impact on my current codebase.

That seems like a reasonable enough solution. Of course, if there are specific things in 'regular numpy' that are not in autograd.numpy, you can let us know by opening an issue!


Added Timestamp to Log

#660

Hey @SilentSobs, is the PR ready for review? If so, let's mark is as such

Hey @SilentSobs, is the PR ready for review? If so, let's mark is as such

Yes.


F# Open Standup: Tuesday 2/2/2015 --- 10:00 AM PT 10:30 AM PT

Welcome to the F# Open Standup,
It is primarily for those who are contributing to, or are interested in contributing to the Visual F# tools open source project. If you are in that group please join us on this Skype for business meeting, phone in should work if you don't have access to Skype for business.
Agenda
It’s a standup … no agenda … A few brief words about what you are working on, what interesting issues have cropped up and what you will to work on next. If the time doesn’t work for you, then post an issue with your stand-up progress, we will review it.
Thanks
Kevin
.........................................................................................................................................
Join Skype Meeting: https://meet.lync.com/microsoft/kevinr/4B4MS4FS
This is an online meeting for Skype for Business, the professional meetings and communications app formerly known as Lync.
Join by Phone
Toll-free number: +1<PHONE_NUMBER>
Toll number: +1<PHONE_NUMBER>
Find a local number
Conference ID: 630930
Help
Welcome to Skype for Business Online Meetings! Please note, all participants using the Join by Phone option must dial the full number for access to the call!

@enricosada, @NumberByColors, @otawfik-ms : it's back-on.

Mondays 10 am? (Y)

This week i cannot do it, next tuesday is ok for me.
I'll add the standup as recurring appointment :smile: .
I didnt see the issue in time so wasnt expecting this tuesday too, the rest of the week i am pretty busy

@fsharp-compiler  Testing

@Microsoft/fsharp-compiler More testing

Ah, didn't see this until just now  :/


Stress the Apache HUDI Branch for the different input file size and identify the threshold

Please try out with 10 MB, 50 MB , 100 MB, 500 MB, 1GB

Completed and tested and part of 0.2.0 release


[sentencepiece] Build macOS M1 and aarch64 JNI for sentencepiece

Description
Brief description of what this PR is about

If this change is a backward incompatible change, why must this change be made?
Interesting edge cases to note here

Codecov Report
Base: 72.08% // Head: 74.41% // Increases project coverage by +2.32% :tada:

Coverage data is based on head (4214528) compared to base (bb5073f).
Patch coverage: 75.08% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #2324      +/-   ##
============================================
+ Coverage     72.08%   74.41%   +2.32%
- Complexity     5126     6714    +1588
============================================
  Files           473      659     +186
  Lines         21970    29153    +7183
  Branches       2351     3016     +665
============================================
+ Hits          15838    21694    +5856
- Misses         4925     5990    +1065
- Partials       1207     1469     +262

Impacted Files
Coverage Δ

api/src/main/java/ai/djl/modality/cv/Image.java
69.23% <ø> (-4.11%)
:arrow_down:

...rc/main/java/ai/djl/modality/cv/MultiBoxPrior.java
76.00% <ø> (ø)

...rc/main/java/ai/djl/modality/cv/output/Joints.java
71.42% <ø> (ø)

.../main/java/ai/djl/modality/cv/output/Landmark.java
100.00% <ø> (ø)

...main/java/ai/djl/modality/cv/output/Rectangle.java
72.41% <0.00%> (ø)

...i/djl/modality/cv/translator/BigGANTranslator.java
21.42% <0.00%> (-5.24%)
:arrow_down:

.../modality/cv/translator/ImageFeatureExtractor.java
0.00% <0.00%> (ø)

.../ai/djl/modality/cv/translator/YoloTranslator.java
27.77% <0.00%> (+18.95%)
:arrow_up:

...ain/java/ai/djl/modality/cv/util/NDImageUtils.java
67.10% <0.00%> (+7.89%)
:arrow_up:

api/src/main/java/ai/djl/modality/nlp/Decoder.java
63.63% <ø> (ø)

... and 604 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


TypeError when publishing from Kinesis to Redis

When fetching from a Kinesis stream and pushing to Redis (AWS Elasticache), I get the following error in CloudWatch:

Error occured while preparing Redis command: [TypeError: list argument must be an Array of Buffers.]

Not being familiar with Redis does some preparation need to be done before writing data?

I had not seen your issue before (GitHub configuration issue). Do you have any stack trace about this?

I think I have found the cause. Can you check again?


Build script that does nothing

Eventually we will want a build script that enables Serde impls for i128 and u128 -- https://github.com/serde-rs/serde/issues/1136. As a first step here is a build script that does nothing to see whether we can roll this out without breaking anyone's workflow, without having a supported feature at stake in the event that it needs to be rolled back.

After releasing this I would like to give people a week to complain before we start using this to enable any observable behavior.

Would it be overkill to use the rustc_version crate?
Good idea on the slow rollout. We could probably publish an rc version first when we try out an actual feature.

The rustc_version crate adds 2.5 CPU-seconds of compile time on my computer above what this build script adds, which seemed excessive. We don't need a production quality semver parser or complete rustc metadata handling.

FYI there is also the version_check crate which compared to rustc_version is much more lightweight feature-wise and doesn't have dependencies.

Nice, I hadn't seen version_check before. That looks a lot more reasonable for our use case.

Thanks for demonstrating the implementation with version_check! In my own applications I would definitely use it. But for Serde I am going to stick with some simple parsing in the build script. I believe one of the defining challenges for Serde over the next few years will be avoiding bloat (or the perception of bloat) and there is a vast difference in perception between having dependencies and having no dependencies. I took a look at cargo clean && time cargo build --no-default-features before this PR, with just a build script, and with build script + version_check and the build script by itself adds 9% to compile time which is already close to the limit of what it makes sense to accept for the sake of i128 impls; build script + version_check adds 18%. But let's revisit if this approach turns out unreliable or unmaintainable.


Restart zerotect after install

Reinstalling zerotect may have modified the configuration file. It is important to restart it (if already running.)

@jsera-polyverse can you fix this? Here's the crux of the issue:

If the install script is run twice with two different configurations,
The config in /etc/zerotect/zerotect.toml changes properly.
But the running service doesn't pick up those changes.

The install script starts zerotect in whatever way possible, but if already running, does not restart it. So new config does not get picked up.


luci-app-statistics: add support for cUrl

Add collectd-mod-curl plugin support. Which can do some complex track,
such as grab stock, but by now, only response time are supported.
#2138

Apart from that one tab change, the code compiles and could be merged.
But I just noticed that you have not "signed-off-by" the commit. That is required.

Hi @hnyman
I have rewrite my commit to add signed-off-by.
And fixed the space/tab problem.


regarding reindex priority statement in zh-tw is incorrect

Traditional Chinese version of following statement is incorrect.
zh-tw: "索引轉換會使用您布建的 ru，但優先順序高於 CRUD 作業或查詢。"
should be modified to:
zh-tw: "索引轉換會使用您布建的 ru，但優先順序低於 CRUD 作業或查詢。"
original in en-us: "The index transformation uses your provisioned RUs but at a lower priority than your CRUD operations or queries."
doc link:
[zh-tw] https://docs.microsoft.com/zh-tw/azure/cosmos-db/index-policy#modifying-the-indexing-policy
[en-us] https://docs.microsoft.com/en-us/azure/cosmos-db/index-policy#modifying-the-indexing-policy

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

ID: d3aeab4a-343d-b492-f9dc-a3233a117101
Version Independent ID: 075ccfaf-9b5c-aa6d-8a35-a57b4344773c
Content: Azure Cosmos DB indexing policies
Content Source: articles/cosmos-db/index-policy.md
Service: cosmos-db
Sub-service: cosmosdb-sql
GitHub Login: @timsander1
Microsoft Alias: tisande

@chshihMSFT Thank you for taking the time to report this issue.
I have filed an internal work item for the localization team to have a look.
We will proceed to close this issue on GitHub.
If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


Create colour_composite.ipynb

Code for forming colour composite, first commit

Please make a folder named notebooks, then add the jupyter notebook to that folder and make the commit.

Documentations not clear.


Issue with Extracting Options Using manpage_parser.py

Hello,
Thank you for your open-source project! I'm currently using the Docker container you provided and ran the following commands:
docker run -it 4ugustus/prophetfuzz_base bash
cd ~/ProphetFuzz
mkdir manpage_parser/output
python3 ./manpage_parser/parser.py --file ./manpage_parser/input/bison.1

However, I encountered an issue where the manpage_bison.json file did not successfully extract the options. Here is the output I received:
root@1ab3f4130f7c:/ProphetFuzz# cat manpage_parser/output/manpage_bison.json
{"description": "", "options": {}, "synopsis": ""}

I also tried other program (e.g., tiffcp, exiv2, mutool), but received the same result.
Could you please provide some assistance on how to resolve this issue?
Thank you!

Sorry, after reviewing the parser.py, I found that this part of the code needs to be run in an environment with the man command. I was able to successfully run the script on the host machine. As the issue is resolved, I am closing this issue.

Thanks for the update! Great to hear you’ve resolved the issue.


Incorrect moment validation on 2.11.0

A bug has appeared in 2.11.0 regarding moment validation.  In this case a perfectly valid date is returned as invalid.
moment('25-May-2015', 'DD-MMM-YYYY', true).isValid() // Returns false

This code returned true in 2.10.6
I've only been able to replicate this issue using MMM as part of the date string, so possibly the bug is there

This is probably the same as #2841

Not the same.  The example in #2841 shows true in the description, but returns false under 2.11.0

Also seeing this in my applications The two digit date moment('Jan-01-49', 'MMM-DD-YY', true).isValid(); returns false as well only for 2.11.0
Very simple reproduction showing some valid dates next to the "invalid" bugs. This JSBin should console.log true for all four dates
http://jsbin.com/qepelowoqa/2/edit?html,js,console

It is indeed the same as #2841, caused by addition of gd locale, more precisely -- adding - as a "word" character.
Closing in favor of #2841.


[Feature] CLI Parameter for packages-install-path

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
Add a CLI parameter for the packages-install-path, similar to how target-path has one.
In the docs, under target-path, it says:

Just like other global configs, it is possible to override these values for your environment or invocation by using the CLI option (--target-path) or environment variables (DBT_TARGET_PATH).

Describe alternatives you've considered
Using the env var DBT_PACKAGES_INSTALL_PATH.
The issue here is that some orchestration tools, such as Databricks DBT Workflows make setting environment variables very difficult. By adding this cli parameter, we maintain consistency across global configs.
Who will this benefit?
People using orchestration tools with awkward limitations.
Are you interested in contributing this feature?
Yes, the PR is https://github.com/dbt-labs/dbt-core/pull/9933

Thanks for opening this @stevenayers !
Can you share more about the specific use cases where combining a CLI flag with an environment variable is necessary or beneficial versus just merely including the packages-install-path configuration in dbt_project.yml?

Hi @dbeatty10, sure no problem! Let me break this down a bit.
Hardcoding packages-install-path
1. In scenarios when docker containers are being used this can raise difficulties. I won't go into too much detail because it's been documented quite well in this issue https://github.com/dbt-labs/dbt-core/issues/1710.
2. When you are dealing with a lot of orchestration/workflow systems you will often find that the working directory of each step does not share the same working directory as the previous, and they can often be dynamic. Take this pipeline as an example:
  graph LR;
      A[dbt debug]-->B[dbt run];
      B-->C[dbt test];
      C-->D[dbt docs generate];

Each working directory could look something like /tmp/job-id/step-id

dbt debug: /tmp/1ad0ceb/ee74a60082b34c3a3d0df8a0d5d5cbfd7ec5ed6a
dbt run: /tmp/1ad0ceb/607646b627e80fe5e45545589fc8c09482010978
dbt run: /tmp/1ad0ceb/7e164e3ab723c357cb638ad6c1e1beef19a7fec6
dbt test: /tmp/1ad0ceb/cb56f4fdc16d5a79953af3003645a1af5a000926

With this, you don't want to be re-installing your deps at every stage, and likely want to reuse them. This is where, like in issue #1710, you will want to use an environment variable like:
config-version: 2
packages-install-path: "{{ env_var('DBT_PACKAGES_INSTALL_PATH', 'dbt_packages') }}"

You could set packages-install-path: "../dbt_packages", but that's making assumptions when you sometimes need to use shell script logic to figure out what that directory path needs to be.
3. Say you have set packages-install-path to /tmp/my_custom_packages_path so it can be shared between steps. What if you're also running your CI/CD test pipeline in that environment?
Your packages.yml is changed in your feature branch, which updates the package contents in /tmp/my_custom_packages_path. Your live data pipeline is in the middle of running, and when it goes to run, it fails because your feature branch has removed packages your live data pipeline was using when it was running.
This is where you'll want to do something like:
config-version: 2
packages-install-path: "{{ env_var('DBT_PACKAGES_INSTALL_PATH', 'dbt_packages') }}"

and in your pipeline you'll want to set DBT_PACKAGES_INSTALL_PATH to something like /tmp/${ENVIRONMENT}/dbt_packages.
Flag vs env var for packages-install-path
As I mentioned in the original issue, sometimes setting an environment variable can be a pain in some workflow systems. This also isn't very consistent or clean:
DBT_PACKAGES_INSTALL_PATH=/tmp/${ENVIRONMENT}/dbt_packages dbt run --target-path /tmp/${ENVIRONMENT}/target
You're setting config paths via two different methods.


Clone a challenge

It would be neat if you could clone a challenge. Would look like this:

Hitting 'Clone' would open the new challenge creation screen pre-populated with the values of the source  challenge.
Use case is when you have challenges that are very similar but require only small tweaks to description and / or overpass query.

Will be part of my next PR.

Added in most recent PR.


Feat/upgrade to vite v3

Summary
Upgrade to Vite v3

PR Checklist

[ ] Does not introduce dependencies
[ ] Functional: all changes do not break existing APIs and if so, bump major version.
[ ] Tests pass: check the output of yarn test packages/
[ ] Naming: the files and the method and prop variables use the same naming conventions as other Kongponents
[ ] Framework style: abides by the essential rules in Vue's style guide
[ ] Cleanliness: does not have formatting issues, unused code (e.g., console.logs), or leftover comments
[ ] Docs: includes a technically accurate README, uses JSDOC where appropriate

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.4 out of 5 committers have signed the CLA.:white_check_mark: adamdehaven:white_check_mark: aanchalm01:white_check_mark: Leopoldthecoder:white_check_mark: dustinryerson:x: semantic-release-botYou have signed the CLA already but the status is still pending? Let us recheck it.


Create README-ja.md

I translated the README.me into Japanese.  I hope more and more Japanese users will use this repository if we have a Japanese version of README. I'll update its Japanese version following official master branch's update.

Hi, @t-cool thats very cool thank you !

If you want so, you can also translate the php-X Branches and its Readme.

@MrOffline77
All right! I'll translate them too later!

Cool thank you very much !


added windows 11

after reading this article, i confirmed windows 11 is supported

Learn Build status updates of commit fc140e4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows/security/threat-protection/security-policy-settings/network-security-do-not-store-lan-manager-hash-value-on-next-password-change.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


(FM-7550) Convert cisco_aaa_authorization_login_cfg_svc acceptance te…

…st to dual mode

Codecov Report

Merging #52 into puppet6 will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           puppet6     #52   +/-   ##
=======================================
  Coverage     5.82%   5.82%
=======================================
  Files          172     172
  Lines        20616   20616
=======================================
  Hits          1200    1200
  Misses       19416   19416

Impacted Files
Coverage Δ

lib/puppet/provider/radius_server/cisco_nexus.rb
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


fix ask block inside on a / b pressed controller event

fix https://github.com/microsoft/pxt-arcade/issues/2738
fix https://github.com/microsoft/pxt-arcade/issues/1639
Someday we should probably see about better handling for controller events creating new scenes / maybe think on the queuing behavior~

Is this is a problem with our other dialogs? like show long text or ask for string

Is this is a problem with our other dialogs? like show long text or ask for string

The other ones all handle it properly already~

The other ones all handle it properly already~


#[cfg(test)] only works for unit tests

Just opened this to see if you know a better way of doing this. The #[cfg(test)] unfortunately does not work for integration tests: https://users.rust-lang.org/t/cfg-test-does-not-work-with-integration-tests/36630/5.
#1068

Yah,cfg(test) is never true in binaries. You can integration_test() which is in main.rs to see if you're running in an integration test.

See my comments in #1068, maybe we can fix this by modifying just the test that's causing the issue, and not the default behavior of all tests.

ok, then i'll close this


Optimize count() for BooleanQuery disjunction

Description
Context: we (Amazon customer facing product search team, and also AWS) are attempting to understand the amazing performance Tantivy (Rust search engine) has over Lucene, iterating in this GitHub repo.  That repo is sort of a merger of Lucene's benchmarking code (luceneutil), including its tasks and enwiki corpus, and the open source Tantivy benchmark.  Tantivy is impressively fast :)
This issue is a spinoff from this fascinating comment by @fulmicoton, creator and maintainer of Tantivy.
Tantivy optimizes count() for BooleanQuery disjunctions much like Lucene's BooleanScorer, by scoring in a windowed bitset of N docs at once, and then pop-counting the set bits in each window.  This is not technically a sub-linear implementation: it is still linear, but I suspect with a smaller constant factor than the default count() fallback Lucene implements.
Perhaps, for all cases where BooleanQuery uses the windowed BooleanScorer, we could also implement this count() optimization.
From my read of Lucene's BooleanWeight.count, I don't think Lucene has this optimization?  Maybe we should port over Tantivy's optimization?  It should make disjunctive counting quite a bit faster?

From my read of Lucene's BooleanWeight.count, I don't think Lucene has this optimization? Maybe we should port over Tantivy's optimization? It should make disjunctive counting quite a bit faster?

BooleanWeight#count doesn't allow to do this kind of thing currently, because its contract is that it should run in constant-time or so, so that you can compute its result and then ignore it if you can't actually make use of it. E.g. for conjunctions, we call BooleanWeight#count over all clauses one by one and stop when more than one clause returns a results that is different from numDocs, and then we fall back to regular counting with TotalHitCountCollector.
+1 to update the Weight#count API contract or introduce a new API to better optimize counting.

I checked the repository. When Tantitvy says it is 2 times faster then this is also unfair: It does not warm up the JVM. It runs the list of queries in cold, unoptimized state - COLD!
Very unfair, sorry. See code:

https://github.com/Tony-X/search-benchmark-game/blob/a6f71237e84aeb47ee8f5b923f16b760b032e1fc/engines/lucene-9.5.0/src/main/java/DoQuery.java
https://github.com/Tony-X/search-benchmark-game/blob/a6f71237e84aeb47ee8f5b923f16b760b032e1fc/engines/lucene-9.5.0/query.sh (no extra options passed)

So basically it runs the queries on a cold JVM so the first queries in the list are all running in interpreted mode, especially when the new vector features or mmapdir are used.
Did I oversee something?

OK, it seems to have some warmup in the python code, but I did not find the number of warmup queries.

When Tantitvy says it is 2 times faster then this is also unfair

It's called tantivy. We do have a warmup phase.

Very unfair, sorry.
Did I oversee something?

Yes, you did oversee something.

I found the python code (see my 2nd comment), but where's the number of warmup queries?

It is given as an environnement variable. You can find the default value in the Makefile. It is 1 round.
1 round means run the entire benchmark once.
The bench does not run queries in a AAAAABBBBBCCCC order but in a ABCABCABC order.
So one round means running ABC.
Also the results shown are always showing the minimum of the n runs. Not the mean.

Ok thanks, so it executes all queries once and then starts over in the same JVM? - I hope it does not start a new JVM each round.
The default default config of mike's luceneutil benchmark is also not optimal with that and needs tuning (there are some discussions in recent commits about vector support and mmap). Especially with the brand new optimizations in recent Lucene 9.7 commits it gets more and more important to give Lucene enough time to warm itsself up. Hotspot is very slow with applying those optos (that is what Rust does better) and due to the incubation state of those vector optos, the garbage collector has much to do in early phases. So it is important to let run Lucene for a few minutes to let GC clean up the "optimization garbage" till it starts measuring in the same JVM. If you start a new JVM, you have to wait the warmup time again.
The problem of many Lucene tests on the web is that they start after 100 or 200 queries with measuring or restart JVMs. So please excuse my complaint as the pure Java code did not look how it warms up; I did not see it externally did that in python.

Yes it is the same JVM.
We can try to increase the warmup iter to let it run for one hour, and see if the results change?
Also, do you have an idea of what is the best JVM and the best settings we should use.

@uschindler I think the benchmark is quite fair at this point, from what I can tell -- we've been iterating on that repo working to pull over luceneutil's enwiki corpus + tasks, ensuring the returned top N hits are very nearly identical, ensuring warmup + N iterations and take the fastest run is happening, measuring time on the server not the client, running both on a single segment index (makes results more comparable but not necessarily realistic to production cases), sprinkle 2% deletes on both indices, statically sorting both indices by the same id field, etc.
It does indeed run a single JVM, but I an of the opposite opinion -- we need to run multiple JVM iterations to see how much hotspot noise is hurting.  Darned java/hotspot coddling! The Rust results look quite consistent from one run to the next.
It's also simple to run -- fork/clone the repo and follow the README steps.  I'd love to see results from more diverse hardware than just my home beast boxes lol.

Still the mix of several languages makes it hard to understand.

Ha!  Java and Python and Rust!
Start at client.py -- I think it's quite understandable if you launch off from there.  More so than luceneutil!!

When Tantitvy says it is 2 times faster then this is also unfair

It's called tantivy. We do have a warmup phase.

Oh -- sorry -- you mean no capitalization?  So tantivy not Tantivy?  I'll try to spell it correctly going forward.

BooleanWeight#count doesn't allow to do this kind of thing currently, because its contract is that it should run in constant-time or so, so that you can compute its result and then ignore it if you can't actually make use of it. E.g. for conjunctions, we call BooleanWeight#count over all clauses one by one and stop when more than one clause returns a results that is different from numDocs, and then we fall back to regular counting with TotalHitCountCollector.

Ahh -- gotchya -- only if the impl will be constant time is it allowed to run, else -1 (also in constant time).
OK so it's a bit tricky to add this opto to Lucene ... we need an API change of some sort.
It's as if when IndexSearcher.count realizes it must fallback to counting each hit individually, it should then call maybe another API, which BQ would implement, to try to do that count more efficiently.  Hmm.

Also, do you have an idea of what is the best JVM and the best settings we should use.

I think @uschindler is referring to the recent changes to let Lucene use Panama (rough SIMD access from way up in javaland) if the user opts in at runtime.  We could test this (add --add-modules jdk.incubator.vector) but I suspect it's unlikely to help since so far Lucene only uses Panama for KNN search, I think?
We should fix the JVM heap size I suppose -- I'll try that to see if it alters results.

Hi. It looks like the DoQuery.java code does not for a throughput measurement, but instead it runs all queries in a single thread one after each other with Nanotime before and after (thanks for the fix, Mike). So we measure exactly duration of each query. So we should use also ParallelGC. The default G1GC works better when you hammer a server multithreaded, but if there's only one thread doing queries, ParallelGC is better.
Of course a real world benchmark should also measure throughput by hammering a server with hundreds of parallel queries (many more than there are CPU cores) to saturate all CPU cores. Of course in such throughout scenarios I have seen sometimes single queries taking long time, but you need to also look at percentiles then.
I know that lucene is very good in throughput measurements.
I know this comment goes too far and beyond this issue, but we should really look at other scenarios than measuring the duration a query takes.
About vector: this does not apply here because there's no vector search involved. Still with modern Java version like jdk-20 the warmup time in combination with parallelgc is higher due to tiered compilation.
Please use java 20 for benchmarks to also see benefits from mmap, especially with indexes optimized to one segment. Also enable parallel GC, although it's not real world, but the benchmark isn't, too.
Please do not pass any extra JVM args, except GC and heap size.

The default G1GC works better when you hammer a server multithreaded, but if there's only one thread doing queries, ParallelGC is better.

Ahh great catch @uschindler!  I just made that change in the benchy.

Hi. It looks like the DoQuery.java code does not do a parallel throughput measurement, but instead it runs all queries in a single thread one after each other with Nanotime before and after (thanks for the fix, Mike)

Right -- we are only measuring single threaded query latency (just like luceneutil).
I agree a red-line test (saturate CPU) is also really important -- we have an issue open for this.  It's a bit trickier to do...
Note that neither tantivy nor Lucene is using more than one thread for each query, nor any OS level concurrency like async IO (I think?), so the "lightly loaded single query latency" metric should be fair to compare across both engines.

Here is is also missing, that's the code I looked at: https://github.com/Tony-X/search-benchmark-game/blob/4402d42c906830e85d8d79a30ae776f204ade770/engines/lucene-9.5.0/query.sh

Oh -- sorry -- you mean no capitalization? So tantivy not Tantivy? I'll try to spell it correctly going forward.

@mikemccand No no. There is no specific capitalization :). I was correcting tantivity -> tantivy.

Oh -- sorry -- you mean no capitalization? So tantivy not Tantivy? I'll try to spell it correctly going forward.

@mikemccand No no. There is no specific capitalization :). I was correcting tantivity -> tantivy.

too late in evening and on smartphone. Whatever Google decided to be the correct term :-)

Oh -- sorry -- you mean no capitalization? So tantivy not Tantivy? I'll try to spell it correctly going forward.

@mikemccand No no. There is no specific capitalization :). I was correcting tantivity -> tantivy.

OH!  Ha, OK, phew :)

Here is is also missing, that's the code I looked at: https://github.com/Tony-X/search-benchmark-game/blob/4402d42c906830e85d8d79a30ae776f204ade770/engines/lucene-9.5.0/query.sh

Oh yeah that does look scary at first, but that is the sh script to start up the "server" that handles many queries through pipes.  It is how client.py launches Lucene's server to run its benchmarks (many queries in one exe invocation).
It's invoked from Lucene's Makefile in that same directory for the make serve target.

Please use java 20 for benchmarks to also see benefits from mmap, especially with indexes optimized to one segment. Also enable parallel GC, although it's not real world, but the benchmark isn't, too.

Small correction as I noticed you are on Lucene 9.5:

for Lucene 9.5, use Java 19
for Lucene 9.6, use Java 20

Of course a real world benchmark should also measure throughput by hammering a server with hundreds of parallel queries (many more than there are CPU cores) to saturate all CPU cores.

The goal of the original benchmark is to identify performance headrooms in tantivy.
That's why it measures different kind of queries, does not deal with multithreading, works over a single segment, and compares "min" and not "mean".
"min" removes a lot of the noise and is for this reason a bit generous for Java...
but it is much better to give us the right insights.
BTW I suspect changing the GC won't have any effect on the min statistics, but it does not hurt to try.
I'd love to see a fair bench of multithreaded search throughput / indexing of course.
Making it fair is however much trickier.

BTW I suspect changing the GC won't have any effect on the min statistics, but it does not hurt to try.

The problem is that Java's default GC G1 brings up to 10% decrease in speed due to addition of barriers, but cleans up garbage much faster with less pauses. This is fine for multithreaded apps, but not single threaded apps doing wall clock measurements.

Just caught up on this thread -- the design tenet of the current benchmark game is to measure time taken to do the same work in contention-free environment.
As of now I'm still trying to build trust of the benchmarks so thank you for your evaluation and feedbacks @uschindler !
So far I believe there are doing the "same" work as I have chased down a few tokenization issues. Right now the indexes on both side have  --

almost "same" tokenization -- split by whitespaces and remove tokens with length >=256
same index sort
same set of deleted docs (2% in total)
single segment

Regarding the JVM here is what we do now

warm up the JVM with 6.1k query for each COUNT and TOP_10_COUNT.  We could increase the warmup iterations easily here. As I was typing, I already changed warmup iter to 3 and kicked off a run.

Admittedly we haven't looked into playing with different JVM arguments. @mikemccand thanks for creating https://github.com/Tony-X/search-benchmark-game/issues/37 to explore the heap sizes :)
IMO, GC here is less of an issue since we measure the best latency (min) across 10 runs for each query (a slight favor for JVM). The probability that every 10 of 10 run of the same query hit an GC is very tiny.
It would be great to share your insights about an optimal JVM setting for this case.

https://github.com/Tony-X/search-benchmark-game/blob/a6f71237e84aeb47ee8f5b923f16b760b032e1fc/engines/lucene-9.5.0/query.sh

This is not used in benchmarks. I should remove it.

@uschindler I updated the bench of the search benchmarks with:

1 hour warmup (1800 iteration) https://tantivy-search.github.io/bench/
lucene 9.6.0
tantivy 0.20
rust 1.70
a proper AWS c5n.xlarge instance

Hi, thanks for crosschecking. 1 hour warmup is therefor not changing anything.
Anyways, I'd use a newer JDK like 20.

After roughly catching up with the threads, I would like to go back to

+1 to update the Weight#count API contract or introduce a new API to better optimize counting.

So we probably can have two count API, constantCount and fastCount?
Then the contract can become, IS will call constantCount first, then if:

it returns -2 then it means there's no possible constant time count, but a possible faster than normal count, then IS will call fastCount to retrieve count;
it returns -1 then it means no faster count possible, go back to use query and do count normally?
it returns a natural number then it's the count.

Does that makes sense?

I was wondering about a possible alternative approach that would consist of handling this optimization more at the collector level. E.g. we could add a new method to LeafCollector to take a set of doc IDs (pseudo code):
void collect(DocIdSet set) {
  // default implementation
  for (int docID : set) {
    collect(docID);
  }
}

Then BooleanScorer could pass a DocIdSet to the collector for each window, and TotalHitCountCollector could override the above method to do more something like this:
void collect(DocIdSet set) {
  // total hit count implementation
  count += set.size(); // internally uses Long#bitCount rather than iterating bits one by one
}

E.g. we could add a new method to LeafCollector to take a set of doc IDs (pseudo code):

I like this idea!  Sort of like BulkScorer, which can score/collect N docs at a time.

we could add a new method to LeafCollector to take a set of doc IDs (pseudo code)

+1, I think this is a better/cleaner approach

I like it better too but I think it's going to need more work, e.g. we will need to remove the Scorable#docID() API to avoid running into cases when the doc ID passed to LeafCollector#collect is not the same as the doc ID exposed by Scorable#docID()?

Maybe we need a BulkScorable or something which holds multiple Scorable (or just holds an array of scores) and set the contract that collect(DocIdSet should use BulkScorable but not normal Scorable? (This sounds a little bit hacky tho...)

It felt to me like it would be doable to remove Scorable#docID without introducing a replacement, so I gave it a try at #12407.

I opened a proof of concept for the idea that I suggested above at #12415.


Update documentation, clarify some varnames

The name m_decorations was misleading, replace it with m_decoration_map.
This change was originally proposed in #621

Eyeballed the renamings. Tested the Decoration<1>(1 + 1 + typeIn.i) parts by confirming AutoFilterFunctionTest and all Decoration tests still pass.


Wrong severity check

Repository URL
https://github.com/primefaces/primevue-tailwind/blob/main/presets/wind/splitbutton/index.js

In the splitbutton Wind preset there is a check for secondary on lines 84 and 272 instead of for success:
`
// Success Text Button
{ 'text-surface-500 dark:text-surface-400': parent.props.text && parent.props.severity === 'secondary' && !parent.props.plain },
// Success Text Button
{ 'text-surface-500 dark:text-surface-400': parent.props.text && parent.props.severity === 'secondary' && !parent.props.plain },
`

Create PR #215 to address

Thank you for your PR, but the Wind preset is no longer part of the official presets. It has been replaced with the Aura Preset.
You can add this PR and the issue to the Wind Preset Github repo. I would be happy to merge it.
❗Wind Preset has been moved (w/ v0.9.0)❗ #242


[SuperEditor] Does MutableDocument intentionally allow nodes to be modified outside of the document?

When working on #1648, I noticed that currently MutableDocument allows for nodes to be modified outside of the methods provided by the document.
Currently, MutableDocument is defined as:
https://github.com/superlistapp/super_editor/blob/fa9ad4483f46b6091a108e7f00e764a187a21530/super_editor/lib/src/core/editor.dart#L493-L497
However, this setup allows for the caller to modify nodes from outside the document if they keep a reference to the nodes.
For instance, doing:
  final nodes = <DocumentNode>[];
  final document = MutableDocument(nodes: nodes);

  nodes.insert(0, TextNode(id: '<id>', text: AttributedText()));

  print(document.nodes); // prints [[TextNode]...]
  print(document.getNodeById('<id>')); // prints null

Is this behaviour expected or is the intent that the nodes always stay private and that the constructor should behave as:
  MutableDocument({
    List<DocumentNode>? nodes,
  }) : _nodes = [...?nodes] {}

All changes to the MutableDocument should be done through Editor commands. The MutableDocument API is largely due to the fact that we didn't used to have requests and commands, but now we do.
I don't know if we'll ever completely hide MutableDocument because anyone can provide any object they want as an editable inside the Editor. Instead, users should recognize that any objects they put inside an Editor as an Editable shouldn't be mutated outside of commands.


dxform submit in Angular 2 - question

How can I submit a dxform in Angular 2? Could you give me a simple example ?
Thanks in advance

Hi!
I see the same ticket in our Support Center that might be created by you, so I suggest you continue discussing the issue there.


TableCards don't support links in expanded rows

Describe the bug
TableCards support click-able links in their rows, but we need to support in expanded rows as well.
Expected behavior
TableCard expanded rows should support linkTemplate hrefs as clickable links.

Duplicate of #1216


Efficient Entity View Result Streaming

JPA 2.2 added the method getResultStream() to the TypedQuery interface with a default implementation that first loads all the results into memory and then returns a stream.
Blaze Persistence has multiple classes which implement TypedQuery, for example ObjectBuilderTypedQuery and TypedQueryWrapper.
I would suggest adding implementations of getResultStream() to those classes so that they do not use the inefficient default implementation.
TypedQueryWrapper.java:
//...
    @Override
    public Stream<X> getResultStream() {
        return delegate.getResultStream();
    }
//...

ObjectBuilderTypedQuery.java:
//...
    @Override
    public Stream<X> getResultStream() {
        return super.getResultStream().map(tuple -> {
            if (tuple instanceof Object[]) {
                return builder.build((Object[]) tuple);
            } else {
                return builder.build(new Object[] { tuple });
            }
        });
    }
//...

These changes allow entity view results to be streamed without first being fully loaded into memory if the underlying JPA provider supports it. I've tested it to work with Hibernate 5.4.

Hi,
I don't think this will in general do what you want unfortunately. It's a bit more complex when collections are involved, but maybe there are none in your case and it's fine? Anyway, there is an open issue about supporting this #254
I will still try to see what I can do about this specific issue. Thanks for the report!

You're right, there are no collections involved in my use case. Thanks for looking into this.

Hibernate 5.2 and up require Java 8 anyway, so we could set the language level in these modules to Java 8 and extend TypedQueryWrapper and ObjectBuilderTypedQuery there. Then these implementations can delegate the stream() call. However, that likely also means moving these from com.blazebit.persistence.impl.query to com.blazebit.persistence.spi. And I am not sure if all places where TypedQueryWrapper and ObjectBuilderTypedQuery  are currently have access to ExtendedQuerySupport.

As discussed today with @jwgmeligmeyling, it's just not doable to support this without bumping the language level to 1.8 because we need Stream in the method signature of our query implementations, so we will defer this to 2.0


Add Demo GIF

Add a GIF under How it works section, showing how One of Example Code Compiles and generate TCs

@aashutoshrathi  how do i run it? Gets stuck on the last iteration of ZIP generation

Is it throwing some error @bigpythonimish?

Check the demo, I have updated it.

https://image.ibb.co/khsiyw/out.gif Here is GIF, your task is to minimize its size and add it to README

Can i Add this gif?


Router should automatically wrap Arrays and non-sentinel Objects in Atom when delivered in PathValue

Title self-explanatory. This issue keeps tripping up beginners.

+1
On Wed, Sep 2, 2015 at 9:24 PM Jafar Husain<EMAIL_ADDRESS>wrote:

Title self-explanatory. This issue keeps tripping up beginners.
—
Reply to this email directly or view it on GitHub
https://github.com/Netflix/falcor-router/issues/127.


Support dynamic update cache config

Motivation
Support dynamic  update cache config :
managedLedgerCacheEvictionTimeThresholdMillis
managedLedgerCacheSizeMB
managedLedgerCacheEvictionWatermark
evictionTriggerThresholdPercent
Documentation
Check the box below or label this PR directly (if you have committer privilege).

Referring everything to the Service Configuration is a waste of resource and we should avoid this  especially inside synchonized methods.
I suggest to not evaluate the values of the configuration parameters everything but to try to notify the components that the Configuration changed and to update the current local configuration when such notification happens

I will  fiz

ping

Fixed.
PTAL,thanks! @eolivelli @Jason918

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

Fixed.
PTAL,thanks!  @Jason918

@eolivelli PTAL,thanks!

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

We should also add tests
Fixed.
PTAL,thanks! @eolivelli


[Event Request] -codeunit 211 "Res. Jnl.-Check Line"

    [IntegrationEvent(false, false)]
    local procedure OnBeforeCheckDimensions(var GenJnlLine: Record "Gen. Journal Line"; var CheckDone: Boolean)
    begin
    end;

Dimensionscheck in codeunit 211:

Dimensionscheck in Codeunit 11:

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Update node tag to 1.0.0-rc1

I tested manually with the new tag (storageos/node:1.0.0-rc1) along the init container.

Sorry, the tag was updated by another PR that's already merged. Closing this.


VSTS Agents Self Hosted on a Mac

Question, I would like to run my self hosted Mac build agents as a daemon on my Mac mini so that I don't have to login to the Mac using the service account.
I have them running as launchd services, they work perfectly if I login to the Mac mini using our service account. This presents a problem if the server reboots for something, we are mostly working from home, so if it reboots and the build agents don't start. Somebody has to drive into the office and login and get them running.
Yes I know we can configure the mini to automatically login, however our security team would prefer to not do this.
I've also reviewed the following documentation, we do not want to automatically login and lock.
https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/v2-osx?view=azure-devops#automatic-login-and-lock
So is it possible to get the build agent running as a launchd service to run as a daemon ?
If so, any specific documentation that somebody could provide would be greatly appreciated.

I haven't actually tried it myself but https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/v2-osx?view=azure-devops#alternative-service-mechanisms has an Apple site link (https://developer.apple.com/library/content/documentation/macOSX/Conceptual/BPSystemStartup/Chapters/CreatingLaunchdJobs.html) to setup Launch Deamon/Agent.
In my case, I setup port forwarding of ssh along with screen share to the mini so that I don't have to run to the office unless it's shutdown and does not start back up.

@neoswallow I appreciate the response, I gave the apple document a try and couldn't get it to work.
Thanks

Hi @dmccolloughOneGas as I know there is no other supported ways to run it - have you checked the links below as well (mentioned in docs)?
https://www.engadget.com/2011/03/07/terminally-geeky-use-automatic-login-more-securely/
https://lifehacker.com/5779922/make-os-x-load-your-desktop-before-you-log-in
I would suggest to reach out to the Apple support for the best practices for your case.


Add benchmark for fabric_transport

Close #2
Using implementation of fabric_transport from tests.rs, ran the same implementation using criterion crate.
More might needed to be  investigated, but adding this initial PR to have a baseline to add more benchmarks.
$cargo bench
   Compiling fabric-rpc-rs v0.1.0 (C:\Users\juzuluag\Documents\GitHub\fabric-rpc-rs)
    Finished bench [optimized] target(s) in 3.11s
     Running unittests src\lib.rs (target\release\deps\fabric_rpc_rs-383ad51807cdfafe.exe)

running 7 tests
test fabricrpc_header::tests::header_test ... ignored
test sys::tests::test_callback ... ignored
test sys::tests::test_ctx ... ignored
test sys::tests::test_msg ... ignored
test tests::fabric_transport ... ignored
test tests::hello_test::test_fabricrpc_helloworld ... ignored
test tests::test_grpc::test_server ... ignored

test result: ok. 0 passed; 0 failed; 7 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running src/benches/fabric_rpc_benchmark.rs (target\release\deps\fabric_rpc_benchmark-b8b613112c7c4a52.exe)
Gnuplot not found, using plotters backend
Benchmarking fabric_transport: Warming up for 3.0000 s
Warning: Unable to complete 100 samples in 5.0s. You may wish to increase target time to 18.5s, or reduce sample count to 20.
fabric_transport        time:   [37.363 ms 68.103 ms 103.86 ms]
                        change: [-79.681% -57.543% -25.470%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 18 outliers among 100 measurements (18.00%)
  5 (5.00%) high mild
  13 (13.00%) high severe

Codecov Report

Merging #9 (37570da) into main (9302a69) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff           @@
##             main       #9   +/-   ##
=======================================
  Coverage   90.84%   90.84%
=======================================
  Files           8        8
  Lines         972      972
=======================================
  Hits          883      883
  Misses         89       89


JSON syntax error when POST body is over 81920 bytes

(Apparently I submitted this issue by accident before I finished it, sorry!)
Howdy-
We ran into an interesting issue that I don't actually think is a Nancy issue, but I'm not sure where else to report it. I wrote up a gist to provide a full reproduction -- I just followed all the directions in the gist and reproduced it locally on my mac easily. It's also reproducible for me on Ubuntu 13.x, I haven't tried reproducing it anywhere else. The gist is here: https://gist.github.com/aaronlerch/7594503
In a nutshell, when running Nancy on Mono (OWIN) behind nginx, request bodies over 81920 bytes are becoming corrupted. It is directly related to the MemoryStream/FileStream optimization going on in RequestStream. I do not believe this class holds the root cause but like I said, I'm not sure where else to report this.
When running on Mono and POSTing a large body directly to the app, things work correctly. The temp-file-based FileStream is created and switched to without a problem. But when you access the exact same process behind an nginx proxy front-end, 8000 NUL values are inserted into the request body stream, starting at offset 81920.
What an odd coincidence. ;)
And the error message you get, in my case, is "JSON syntax error" as the JSON parser encounters a NULL character when it doesn't expect one and fails. Very confusing to uncover the root cause.
I don't have a windows machine readily available, so I didn't go so far as to compile Nancy locally and debug the state of the streams as the memory stream is copied to the file stream, and thus I'm not exactly sure where the problem is. But when I increased the threshold to a value higher than my content length, all was well. I would have just specified the disableStreamSwitching constructor argument to RequestStream, but as I'll mention in another bug report, that's broken and not an option.
Let me know if you have any more questions, and especially if you have an idea of where I should be submitting this bug report. I suspect it's a bug in Mono itself but I haven't debugged it any further to find out.
Thanks-
Aaron

Is there any update for this problem? I just came across this issue and disabling the async FileStream worked. I think it would be a good idea to disable it by default for mono, as long as there's no fix for it, maybe by using the __MonoCS__ define.


Move invalid attributes from PodSecurityContext

What this PR does / why we need it:
allowPrivilegeEscalation and capabilities are not allowed in the PodSecurityContext
https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.14/#podsecuritycontext-v1-core
but only in the SecurityContext
https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.14/#securitycontext-v1-core
The old version was silently ignored.
Move the attributes to actually enable them.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

The issue was introduced in #7183. A similar fix was done in #10042 by @steven-sheehy.

This looks to be a duplicate of PR #13261. Let's close this one and try to get the other merged

Closing in favor of #13261.


Feature gate dependencies

With the new arrow support, I think connector-x has value as a rust crate as well. However, as a crate owner writing a library, I'd not want to depend on connector-x because it has a lot of dependencies (increasing compile times), I'd don't want to compile.
I think it would be really valuable if the dependencies could be opt-in and activated with feature gates.

Yes, correct! I'm also considering releasing the rust crate after the 0.2.0 python version is released. There are more than dependency problems on the Rust crate before we can release it (e.g. documentation).
Luckily I think the release of the Rust crate can be decoupled with the python version.

@ritchie46 Now I moved all the {sources, destinations} under their own feature gates. Most of the dependencies are now optional. Does it look good to you?
https://github.com/sfu-db/connector-x/blob/ad47e84e65b1c8f0a98f8e5e5bbccb12e308c370/connectorx/Cargo.toml.

If you don't specify any feature, the dependencies required are reduced from 338 to 47.

That's a great improvement. :) Congrats on the release.
Do you think that a future release on stable may be possible, perhaps behind a feature gate as well? For binaries, nightly isn't a problem, but I can imagine that libraries are reluctant depending on nightly features.

If you don't specify any feature, the dependencies required are reduced from 338 to 47.

That's a great improvement. :) Congrats on the release.
Do you think that a future release on stable may be possible, perhaps behind a feature gate as well? For binaries, nightly isn't a problem, but I can imagine that libraries are reluctant depending on nightly features.

We use the GAT feature in the core part of the code so I guess it is not easy to move it to a feature gate. The best case is GAT becoming stabilized in October (https://github.com/rust-lang/rust/issues/44265#issuecomment-869888398).


Bring back unit testing for all supported python versions

#283 removed the integration test matrix for anything that wasn't 3.11 python.
This was due to some difficulties we were having in getting ubuntu to accept other versions and successfully restore packages using poetry.
For now, integration testing is only being performed in 3.11, but we should add back 3.7 and onwards.

Closing this ticket as we are moving to Jira to reduce noise. You can access it there.


further relaxed the check on total functions

Fixes #2305

Review checklist
The author performs the actions on the checklist. The reviewer evaluates the work and checks the boxes as they are completed.

[ ] Summary. Write a summary of the changes. Explain what you did to fix the issue, and why you did it. Present the changes in a logical order. Instead of writing a summary in the pull request, you may push a clean Git history.
[ ] Documentation. Write documentation for new functions. Update documentation for functions that changed, or complete documentation where it is missing.
[ ] Tests. Write unit tests for every change. Write the unit tests that were missing before the changes. Include any examples from the reported issue as integration tests.
[ ] Clean up. The changes are already clean. Clean up anything near the changes that you noticed while working. This does not mean only spatially near the changes, but logically near: any code that interacts with the changes!

I was also unable to reproduce even a simple example of the property test failing. I suggest we change exceptionHandler in the property test to discard all cases that produce errors.

Never mind my last comment, I was able to reproduce the property test failure.

This PR will no longer be required once we fix Issue #2468


Fix unit tests

Which issue this PR addresses:

Fixes bug caused by merging #3957 -> https://github.com/Azure/ARO-RP/actions/runs/11897904353/job/33153195580
Fixes unit test bug caused by merging #3890
What this PR does / why we need it:

Test plan for issue:

Is there any documentation that needs to be updated for this PR?

How do you know this will function as expected in production?

/azp run e2e

/azp run e2e

Dupe -> https://github.com/Azure/ARO-RP/pull/3961