Display impl for FBig gives wrong result

The following code outputs 0.1:
println!("{}", FBig::<Up>::try_from(0.5)?);

However, the internal representation is correct. This passes and outputs 1 * 2 ^ -1 (prec: 53):
assert_eq!(FBig::<Up>::try_from(0.5)?.to_f64().value(), 0.5);
println!("{:?}", FBig::<Up>::try_from(0.5)?);

If you use FBig, then the representation is in binary digits. That is, 0.1 is the floating point notation in base 2, which is equivalent to 0.5 in base 10. This is a desired behavior (documented here), though I will make it clearer in the user guide.

Ah, sorry, I wasn't expecting floats to print in base-2, but I guess it makes sense to print in the same B. Thanks for the lib as always!

The major reason I don't want to print in base-10 is that, base conversion can be pretty expensive, and I think it's better to make the conversion explicit,


Unique column validator for table variable

A validator which ensures that all values in a column are unique. This would be useful when column values are used as a key in the templates.

Things to do:

[ ] Add new unique property to validator schema https://github.com/futurice/jalapeno/blob/main/pkg/recipe/variable.go#L50
[ ] Edit validator function to support the new property https://github.com/futurice/jalapeno/blob/main/pkg/recipe/variable.go#L102
[ ] Add unit test for the validator https://github.com/futurice/jalapeno/blob/main/pkg/recipe/variable_test.go#L52
[ ] Pass additional data to CreateValidatorFunc() since currently it can only use the value itself. We can discuss this how this could be done https://github.com/futurice/jalapeno/blob/main/pkg/recipe/variable.go#L170
[ ] Support the unique validator in the table UI component https://github.com/futurice/jalapeno/blob/main/pkg/ui/survey/prompt/table.go#L35


Create pull request template

Closed as per https://github.com/upymake/urequest/commit/8f516029120070a11fc507280b2470058614a9f2


[AKS] Vendor in 2020-09-01 API

This PR just vendors in the September API to unblock development work. It doesn't switch the CLI commands to use the API just yet.
This should be a no-op.
This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/marwanad/azure-cli-extensions.git@vendor-in-sept-api#subdirectory=src/$EXT&egg=$EXT"

AKS

hi @arrownj could you pls review the PR?


Error  "export 'version' was not found in 'vue'

Bug
I get a console warning when using VFile. Error  "export 'version' was not found in 'vue'
Setup
Component.vue
<template>

    <VFile v-model="files" label="Files" />

      You've selected the file "{{ files[0].name }}" ({{ files[0].type }}). It
      was last modified
      {{ files[0].lastModifiedDate }}

</template>

package.json
{
  ...
  "dependencies": {
    "@carbon/layout": "^10.29.0",
    "@carbon/vue": "^2.39.0",
    "axios": "^0.21.1",
    "bootstrap-vue": "^2.21.2",
    "core-js": "^3.6.5",
    "vue": "^2.6.11",
    "vue-router": "^3.2.0",
    "vuelidate": "^0.7.6",
    "vuetensils": "^0.8.0",
    "vuex": "^3.4.0"
  },
  "devDependencies": {
    "@vue/cli-plugin-babel": "~4.5.0",
    "@vue/cli-plugin-eslint": "~4.5.0",
    "@vue/cli-plugin-router": "~4.5.0",
    "@vue/cli-plugin-vuex": "~4.5.0",
    "@vue/cli-service": "~4.5.0",
    "@vue/eslint-config-standard": "^5.1.2",
    "babel-eslint": "^10.1.0",
    "css-loader": "^3.6.0",
    "eslint": "^6.7.2",
    "eslint-plugin-import": "^2.20.2",
    "eslint-plugin-node": "^11.1.0",
    "eslint-plugin-promise": "^4.2.1",
    "eslint-plugin-standard": "^4.0.0",
    "eslint-plugin-vue": "^6.2.2",
    "sass": "^1.36.0",
    "sass-loader": "^10.2.0",
    "vue-template-compiler": "^2.6.11"
  }
  ...
  }

Steps to recreate

Installed Vuetensils 0.9.*
Run npm run serve
Get console warning Error  "export 'version' was not found in 'vue'

Posible causes

When I changed to using Vuetensils 0.8.0 the warning disappeared
It persisted across any Vuetensils component
Inside my component I checked for the version on the Vue instance and it was undefined. I think it could be something to do with this line (const isVue3 = version && version.startsWith('3');)[https://github.com/AustinGil/Vuetensils/blob/4dc05886f1c8b15a5ee4015f67df468e69f8846d/src/components/VFile/VFile.vue#L61]. This repo is legacy and has a few dependencies so it could also be one of those conflicting.

Hey @stuartjnelson, thanks for reporting this. It's actually a known issue. Im working on supporting both Vue 2 and Vue 3. There are only some minor changes, but in order to address them, I need to detect which version of Vue is running. The good news is that this won't negatively affect anything. The bad news is I dont know of a better way to detect what version is running.

Hey @AustinGil,
Thanks for quick reply and sorry if this was already reported.  I was able to check if it was Vue 2 by doing the following;
const isVue3 = this.render  === 'function' || false

This only worked if it was done inside the exported object not where you have it nicely at the top. I wonder if this would cause issues if you use Composition API plugin with Vue 2...

Oh that's a pretty clever approach. I was also considering modifying the code so its more like
import * as namedExports from 'vue'

const isVue3 = namedExports && namedExports.version && namedExports.version.startsWith('3')

It's a bit more verbose, but I think that should work. I just wonder if it would impact the bundle size differently.

I feel  it not a bad verbose though but like you said for this check you wouldn't want to affect bundle size. Let me know if I can help with this

Unfortunately, the solution above does not work. Back to the drawing board. I'd like to avoid something withing the component, but may end up with your solution.

Ended up just adopting vue-demi as it's the recommended solution from the core team. I didnt want to add an external dependency, but fixing this issue was required for Vite support


Fix write_text_file_atomic

This patch corrects two problems with phlsys_fs.write_text_file_atomic:

The temporary file was created in default location which might be in different filesystem than target file. This would make final os.rename operation invalid.
The code did not address atomicity of the operation in case of system crash. A minimal consideration is making sure that relevant os-level file descriptors are fsynced before rename.

No automated tests are provided for (1) because manipulating mountpoints requires superuser privileges. Issue (2) is inherently nondeterministic, rare and quite difficult to reproduce.

Thanks!


fix: fix broken custom lb config caused by eb249d69

What this PR does / why we need it:
Add your description
Which issue(s) this PR is related to (optional, link to 3rd issue(s)):
Fixes #
Reference to #

Special notes for your reviewer:
/cc @hicaistar

Release note:

NONE

/cherrypick release-0.5-2020

/lgtm

/cherrypick release-0.5-2020

/cherrypick release-0.7


Component name not shown when mounting app under subfolder

This can be reproduced in https://github.com/kitbagjs/router-preview by modifying as following:
In vite.config.ts:
import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'
import vueDevTools from 'vite-plugin-vue-devtools'

const BASE_PATH = '/f'

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [vue(), vueDevTools()],
  base: BASE_PATH,
})

In router/index.ts, change the createRouter line to:
export const router = createRouter([home, settings, profile, keys], {
  base: import.meta.env.BASE_URL
})

Now, all pages are shown as routerView when seeing in VueDevTools:

@hongquan But it works fine if you don't use a base path? 🤔

It works without using base path.

@hongquan the version you're looking for is v0.11.2
<EMAIL_ADDRESS>


Windows 11: After installing Julia from the Microsoft Store, VSCode cannot find it

Hello everyone,
I installed the newest version of Julia (1.7) on my Windows 11 computer using the most up-to-date version of VSCode and the Julia VSCode extension. However, VSCode cannot find the julia installation. I verified that Julia is on the path and executing it from the command line works without problems. Also, there are no issues on Windows 10 with the same setup.
Does anybody know how I can fix this?
Best,
Ilja

Do you maybe have something configured in VS Code for the Julia: Executable Path setting? That should be empty.

It is indeed empty, but it stil does not work.
On Thu, Dec 2, 2021, 7:50 PM David Anthoff @.***> wrote:

Do you maybe have something configured in VS Code for the Julia:
Executable Path setting? That should be empty.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/JuliaLang/juliaup/issues/188#issuecomment-984903161,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADG4GA4DZIZACLYXII5J6GTUO65WZANCNFSM5JHSCKIQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

And just to be sure: you installed Julia from the Windows Store, you don't have any other Julia versions installed, and things like juliaup -V work, and when you type for example julia +release on the command line it works?

Yes, just checked all of that.
From: David Anthoff @.>
Sent: 02 December 2021 21:01
To: JuliaLang/juliaup @.>
Cc: Ilja Kantorovitch @.>; Author @.>
Subject: Re: [JuliaLang/juliaup] Windows 11: After installing Julia from the Microsoft Store, VSCode cannot find it (Issue #188)
And just to be sure: you installed Julia from the Windows Store, you don't have any other Julia versions installed, and things like juliaup -V work, and when you type for example julia +release on the command line it works?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/JuliaLang/juliaup/issues/188#issuecomment-984957873 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ADG4GAZYEAU5B2JDS2DJHWLUO7GBRANCNFSM5JHSCKIQ .
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675  or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .   https://github.com/notifications/beacon/ADG4GA2NQBSYMJ73NHL2UR3UO7GBRA5CNFSM5JHSCKI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHK2UHMI.gif

I am also getting this error message, if I try to execute a line nonetheless:
Command failed: julia.exe --startup-file=no --history-file=no -e using Pkg; println(dirname(Pkg.Types.Context().env.project_file)) ERROR: ArgumentError: Package Pkg not found in current path: - Run `import Pkg; Pkg.add("Pkg")` to install the Pkg package. Stacktrace: [1] require(into::Module, mod::Symbol) @ Base .\loading.jl:967

Is the problem that VS Code can't start a Julia REPL, or is the problem with the language server? Also, I merged some stuff in the VS Code extension a while ago that might also have helped (if the problem was on the language server side of things).

I tried it again today and everything worked just fine. Seems to have been some fluke or fixed in other updates! :)


Update popup handling when using Chrome.

Due to changes in Chrome version 69, the original method of handling popups no longer successfully recognises and attaches to the popup window/tab. This changes the check to look for a successful sessionID.
For details check issue #275

Thanks @Aussiroth ! Tagging @ryzalk as I think he may not get a notification (not watching repo).
Hi Ryzal, this fix is in response to some change in behavior for new release of Chrome that breaks TagUI popup step. I guess you can do a merge commit on Alvin's PR. The change relaxes some condition check to allow the popup step to pass through base on the latest Chrome behavior in #275.

Hi guys. Thanks @kensoh for tagging and notifying me on this. Just updated my 'watch' notifications for this repo. Didn't realise it was so. Thanks for your hard work @Aussiroth! Cheers :)


add APA plane change definition of Donut add voxelisation

207Bismuth_PDHD.pdf
LAst version of SingleHit_module with which I can reconstruct Bismuth source in PDHD

I updated the fcl files sorry for this issue


Allow SPAs to process an HTML file before and after it is handled by Webpack

Instead of directly merging Webpack's config, I created a pre (before) and post (after) hook into one of the Builder's loaders ("before" and "after" were used because "post" could be confused with the HTTP method POST). Currently, this feature only supports HTML files, but it could easily introduce other loaders for different extensions.
Use-case is located here.
skyuxconfig.json:
{
  "mode": "easy",
  "compileMode": "aot",
  "plugins": [
    "./plugins/stache-code-block"
  ]
}

./plugins/stache-code-block/index.js (located in the SPA's repo):
module.exports = {
  beforeHtml: (content) => {
    return content;
  },
  afterHtml: (content) => {
    return content;
  }
};

Codecov Report

Merging #103 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #103   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          22     25    +3
  Lines         535    588   +53
  Branches       65     67    +2
=====================================
+ Hits          535    588   +53

Impacted Files
Coverage Δ

config/webpack/common.webpack.config.js
100% <ø> (ø)
:arrow_up:

index.js
100% <0%> (ø)
:arrow_up:

loader/sky-pages-module/index.js
100% <0%> (ø)

loader/sky-assets/index.js
100% <0%> (ø)

plugin/save-metadata/index.js
100% <0%> (ø)

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 aab5087...5a3719f. Read the comment docs.

@Blackbaud-BobbyEarl and I talked about this and have a few changes to propose:

Instead of limiting the Webpack loader to HTML files, we recommend you have all files come through the Webpack loader and leave it up to the plugin to filter out the appropriate files.
Because you would no longer be limiting the plugin to HTML files, we suggest you change beforeHtml and afterHtml to preload and postload.
You will need to write unit tests for your new code.

@Blackbaud-PaulCrowder @Blackbaud-BobbyEarl Ready for another round of reviews.

LGTM.  @Blackbaud-PaulCrowder have anything to add?


fix: checkbox type

fix checkbox type

Artifact can be viewed here: :
https://62-280051086-gh.circle-artifacts.com/0/packages/components/storybook-static/index.html


Changed apply exif data orientation

Changed applied exif data orientation with intervention for fix incorrect orientation on upload image from iphone or others devices.

Thank you @blenderdeluxe !

Your Welcome!!, @g0110280 thanks for project team!


data load is failing with empty dimension column

data load is failing with empty dimension column

hi shahid, i think we are raise the same issue.
empty dimension can work,but with exclude_dictionary,if the number of exclude_dictionary + the number of empty dimension >row size,data load will failure.
i have raise a pr to fix this,please check:
#475

Agree, closing issue #476 duplicate of #475

Reopening the issue as the data load will fail if the (columns in a row)  >
meta.memberMapping.length + meta.noDictionaryCols.length;
and the some of dimension is having empty values.
Data:
ID,date,country,name,phonetype,serialname,salary,as,ds
1,2015/7/23,,aaa1,phone197,ASD69643,15000,,
2,2015/7/24,,aaa2,phone756,ASD42892,15001,,
Query:
CREATE TABLE IF NOT EXISTS t3
(ID Int, date Timestamp, country String,
name String, phonetype String, serialname String, salary Int)
STORED BY 'org.apache.carbondata.format' TBLPROPERTIES('DICTIONARY_EXCLUDE'='country')
LOAD DATA LOCAL INPATH 'csv file path' into table t3

you are giving a data mismatch to the table structure u created.

Closing this issue will be fixed with PR #475


Added Huber loss

[x] Added loss

[x]  Added test cases

[x]  Formatted the code with black

[x]  Added the documentation

@cgarciae @charlielito  Please review.

Thanks @abhinavsp0730, overall it looks amazing!

Codecov Report

Merging #121 (5327c32) into master (5549de5) will increase coverage by 0.10%.
The diff coverage is 95.45%.

@@            Coverage Diff             @@
##           master     #121      +/-   ##
==========================================
+ Coverage   77.51%   77.62%   +0.10%
==========================================
  Files         106      108       +2
  Lines        4856     4893      +37
==========================================
+ Hits         3764     3798      +34
- Misses       1092     1095       +3

Impacted Files
Coverage Δ

elegy/losses/huber_test.py
93.47% <93.47%> (ø)

elegy/losses/__init__.py
100.00% <100.00%> (ø)

elegy/losses/huber.py
100.00% <100.00%> (ø)

elegy/data/data_adapter.py
57.14% <0.00%> (-6.28%)
:arrow_down:

elegy/data/generator_adapter.py
41.30% <0.00%> (-4.70%)
:arrow_down:

elegy/data/data_handler.py
70.00% <0.00%> (-1.63%)
:arrow_down:

elegy/metrics/metric.py
68.18% <0.00%> (-1.39%)
:arrow_down:

elegy/losses/loss.py
78.18% <0.00%> (-0.77%)
:arrow_down:

elegy/data/list_adapter.py
89.74% <0.00%> (-0.74%)
:arrow_down:

elegy/data/array_adapter.py
88.33% <0.00%> (-0.38%)
:arrow_down:

... and 6 more

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 5549de5...5327c32. Read the comment docs.

Thanks a lot @abhinavsp0730!


When adjusting the left border of the window, the window right area flashes

Describe the bug
When adjusting the left border of the Winui3 window, the right area of the window continues to blink, but Winui2 and the system standard window do not blink
Steps to reproduce the bug
1、Run the Winui 3 gallery App
2、press the mouse resize the window left border
3、look the window right area
Expected behavior
No response
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.4.3: 1.4.231115000
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response

Dupe #5148


Add read/write varint

Purpose
Introduce the capability to read/write varint through data-io channel.
Goals

Introduce the capability to read/write varint
Add the relevant test cases

Approach
The following functions were introduced to read/write varint
dataChannel.writeVarInt(value);
dataChannel.readVarInt();
Release note
Introduces capability to read/write varint.
Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
Ran FindSecurityBugs plugin and verified report? yes
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Test environment
JDK 1.8

:white_check_mark: Build ballerina-lang 55 completed (commit https://github.com/ballerina-platform/ballerina-lang/commit/6df11344dc by @pamod)

:x: Build ballerina-lang 111 failed (commit https://github.com/ballerina-platform/ballerina-lang/commit/b619ab3c89 by @pamod)

:white_check_mark: Build ballerina-lang 112 completed (commit https://github.com/ballerina-platform/ballerina-lang/commit/d1c0a57b9a by @pamod)


disjunctive union inference

Suggestion
disjunctive union inference
🔍 Search Terms
union destruction, disjunctive union inference
✅ Viability Checklist
My suggestion meets these guidelines:

[ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
adding destruction in infer to infer Head and Tail.
T extends infer (Head| ...Tail)

adding type level function disjunctive where we can infer Head and Tail.
= T extends disjunctive<infer Head, infer Tail> ?

📃 Motivating Example
i trying to write type level function Elems, which will result for type Elems<'a'|'b'>  following tuple ['a','b']
function should look like:
type Elems<T> = T extends infer (Head | ...Tail)  ? [Head, ...Elems<Tail>] : T;

closest implementation of this function is:
type Elems<T> = T extends infer Head | infer Tail ? [Head, ...Elems<Tail>] : [T];
// result: Elems<'a'|'b'>  -> ["a", "a", "a", "a", "a", "a",...

// or

type Elems<T> = T extends infer Head | infer Tail ? [Head, ...Elems<Exclude<Head, Tail>>] : [T];
// result: Elems<'a'|'b'> -> never

however none of them is working.
main problem is that T extends infer Head | infer Tail infers Head and Tail not as disjunctive unions (however then following example confuses me even more).
type Elems<T> = T extends infer Head | infer Tail ? [Head, Tail] : [];
// result: Elems<'a' | 'b'>  --> ["a", "a"] | ["b", "b"]

Use Cases
one example will be deriving keys for object types. however i think there are others.
type Object {
    a: number;
    b: number;
}

type Keys = Elems<keyof Object> // ['a'|'b']

You reslly, really don’t want to be inferring tuples from unions, as the order of union constituents is not guaranteed and will depend on what other code tsc has processed before it encounters the union.  Sometimes you’ll get [ 'a, 'b' ]` like you expect and everything will work great but another time you might get the reverse and the whole thing falls apart.

i trying to write type level function Elems, which will result for type Elems<'a'|'b'> following tuple ['a','b']

Just FYI, union type order is an implementation detail. "a" | "b" might just as well be "b" | "a".

@MartinJohns  @fatcerberus thanks. i just experimenting with inference in ts. did not really considered seriously ordering. but then possible output types would be:  ["b","a"] | ["a","b"]  which would be also fine. however it could explode ts calculation for high numbers of variants.

still confusing why we get then ["a", "a"] | ["b", "b"] for this exmaple.
type Elems<T> = T extends infer Head | infer Tail ? [Head, Tail] : [];
// result: Elems<'a' | 'b'>  --> ["a", "a"] | ["b", "b"]

It will explode with low numbers already. Such suggestions have come up several times already.

still confusing why we get then ["a", "a"] | ["b", "b"] for this exmaple.

Because infer Head | infer Tail makes no sense. It resolves to the same type. You pass along a union, so you end up with distributive behaviour, meaning the type is resolved for ["a", "a"] and ["b", "b"] individually.

but if it infers same type, should it not resolve then: ["a" | "b" , "a" | "b" ]?

Like Martin said, it’s because conditional types distribute.  The condition is evaluated once for each type in the union and then reassembled into a new union.
refer to https://www.typescriptlang.org/docs/handbook/2/conditional-types.html#distributive-conditional-types

You pass a union of two types in, so you get a union of two types back (since none of them resolves to never).

@nalchevanidze BTW, both of what you request can be implemented already, just with a bit of black magic. (I know how the TS team passionately hate the U2T type but it's there anyway)


Create AIUWA

American International University West Africa, The Gambia

@walataza As far as I can see, American International University, West Africa, The Gambia has a domain aiu.edu.gm, and if you wish to add it to this repository, the file path has to be /lib/domains/gm/edu/aiu.txt. I close this request without merging, please create a new one with correct file path. Please notice that .txt extension is manadatory. Thank you.


Eye emoji not appearing

I am trying to show this emoji 👁 as an image using this package but it's not working.
Instead it's showing its unicode number.

your font file doesn't support emoji. Not all font files will support emoji. You may have to pick another font file.


Warn when above maximum water threshold

Problem
When a user pours in too much water, we don't validate whether the amount of water in the machine is above the threshold (causing overflows).
Expected Results
Warn when water is above threshold.
Actual Results
Machine overflows because user can accidentally go over threshold.
Proposed Solution
In Reservoir.ts, in the validate method we should check the water level and throw an error if its above the maximum threshold. We will need to define a new error constant, WATER_ABOVE_THRESHOLD_ERROR with a code. Ensure test coverage is added so we don't regress.

Since it's OBVIOUS @wired-cupofjoe gave up on this, I can take it.

@wired-cupofjoe it looks like we have an open PR #17 for this change! 😄

@wired-cupofjoe it looks like we have an open PR #17 for this change! 😄


Where can I download mocoV2 pre-trained model on imagenet

Hi, thanks for the nice code.
Could you please provide some information on where can I obtain the public mocoV2 pre-trained model.

You can find it here: https://github.com/facebookresearch/moco


feat: implement cache on getPrompt and getPromptById methods

Add Prompt Caching Functionality
Changes

Implemented a prompt caching system using a separate class SharedCachePrompt

Implementation Details

Cache keys are generated in three formats:

id

name

name:version

Caching logic implemented on both getPrompt and getPromptById

On each successful get prompt we will cache the prompt with keys id, name, name:version

Added fallback to cached prompts when API calls fail, with warning logs

To keep in mind this cache will be cleared each time the application Is restarted

I'm going to  wait for the PR on the python sdk to be approved to merge both at the same time


feat: Memoize filters/sorting/pagination at backoffice

Task was about maintaining sorting during opening/editing, but basically same problem happens during canceling, deletion of records, etc. At beginning, I have started to put to every influenced link or form q param so this gets remembered, but it got quickly out of hand --> there is just too many places where this param needs to be added and  it is so easy to forget to add it to every new piece of code. In the end, I have decided to use session which keeps saved used filters and last page of table per every controller. Until you reset filters manually (or you logout --> login again) q and page params are kept at session and pull out from there everytime when you open some Backoffice table.
Testing instructions
Open backoffice and verify that sorting/pagination/filters are remembered between jumps to edit forms.
Tracking
https://vizzuality.atlassian.net/browse/LET-955

I have a mixed feeling about this. In one project we have exactly this, because client wanted to persist filters. This is kind of feature, but that depends on preference. For me, it was weird going back to the page and having some filters applied already (also not synced with query string). I don't know, I normally would just pass those filter params to actions url, maybe with simple helper_method like this
def memoized_params
  params.permit(:q, :page).to_h
end

I have a mixed feeling about this. In one project we have exactly this, because client wanted to persist filters. This is kind of feature, but that depends on preference. For me, it was weird going back to the page and having some filters applied already (also not synced with query string). I don't know, I normally would just pass those filter params to actions url, maybe with simple helper_method like this
def memoized_params
  params.permit(:q, :page).to_h
end

It was actually my first idea to use something similar to memoized_params, but this needs to be added to a lot of places (my guess is like 20-30 places) so I decided to use sessions which do all the work at background. On other hand I agree that forwarding params is more transparent then some magical session :). What do you think @agnessa , params or session? I dont mind to refactor this feature and use Tomasz idea ;).

well I see the point about the query string, but it works and as far as I'm concerned that's perfect :)


Disable IPv6 for Windows agents

This PR adds the Ansible logic windows/requirements to disable IPv6 on all the Windows agents.
This fixes https://github.com/openvswitch/ovn-kubernetes/issues/491.

LGTM


Problems with requirements

Why does your package have so many dependencies?!
In addition to some of the incorrect local files specified for the packages, some other package names are also wrong and create errors.
Do we need to install all of these packages to test your code? This makes it very difficult to use your package.

The following list was adequate on google colab:
backoff
retrying
openai==0.27.9
I gave up trying on my own system due to numerous errors I received for installing the packages.


[Question] How to inline format a query without splitting or adding a new line after commands ?

I would like to use sql-formatter for case formatting and spaces consistency without needing to split the statement into multiple lines.
Is it possible ?
Example:
Select * from   Table1  ;
I expect
SELECT * FROM Table1;

I see you already noticed an already existing feature request for this #360


header_rewrite: Allow set-debug in READ_RESPONSE_HDR_HOOK.

This doesn't work currently:
cond %{READ_RESPONSE_HDR_HOOK}
cond %{STATUS} =302
set-debug

I see no reason it shouldn't. I tweaked the code to enable it and it worked fine both globally and remap.

[approve ci autest]


pppd command-line options renamed

I am not sure when this happened, but on my version of pppd  (2.4.7), ipv6cp-accept-local and ipv6cp-accept-remote do not exist.
However, ipcp-accept-local and ipcp-accept-remote seem to work fine after patching pkg/client.go.
Not sure what the best resolution is, trying to parse output of pppd --version as a version seems hacky.
diff --git a/pkg/client.go b/pkg/client.go
index 269c21c..85e6435 100644
--- a/pkg/client.go
+++ b/pkg/client.go
@@ -241,8 +241,8 @@ func Connect(server, username, password string, closeSession bool) error {
                // VPN
                if favorite.Object.IPv6 {
                        config.PPPdArgs = append(config.PPPdArgs,
-                               "ipv6cp-accept-local",
-                               "ipv6cp-accept-remote",
+                               "ipcp-accept-local",
+                               "ipcp-accept-remote",
                                "+ipv6",
                        )
                } else {

@leonbreedt I'm working on removing the pppd dependency.

@leonbreedt you can try to test gof5 in Linux with the following config option:
hdlc: false

@kayrus I tried latest master. Good news is that I could open a connection, but its still a bit flaky (paniced a few times), so I'm probably going to go back to a commit that still uses pppd, since I use this VPN for work :)

@leonbreedt can you share the panic trace?

@kayrus I think I was on a slightly old master, I can't reproduce it, and somehow, a commit which I had locally (with a different commit message to the one it has now) has vanished. Did you force push at some point? There was a commit 84376ad84df3fa56b06e303818cba3726ee54b4e, but now it's gone.
Also, a tonne of debug output along with the raw bytes dumped, whereas on refreshed master (@ 369fe4cf600e010c08acf0757810f056edd7cadb), I just see periodic ping/pong messages.
The crash was preceded by a message like 2020/05/07 20:01:29 Fatal write to tun: write tun: invalid argument.
I still see that message from time to time, but no crash now. If I see a crash again I'll open a new issue.
Thanks!

@leonbreedt the work is still in progress and the project is far away to the first release. I completely refactored and amended the https://github.com/kayrus/gof5/commit/84376ad84df3fa56b06e303818cba3726ee54b4e because it was way too bad.

@kayrus your work is much appreciated. using gof5 connecting to VPN is <5 seconds vs 30-60 seconds with the official F5 tools and the overcomplicated from corporate IT. it is already a big improvement to my life :beers:.

Consider closed, when pppd is not used.


merge from master into nanoproto (code only)

Please regenerate checked-in jar files (java-build and cpp-build; anything else?) before making more changes.

As discussed, we won't be checking in generated files until ready to merge back into master (though we'll check them locally).


make method names more consistent

all other methods follow the set_X_fgcolor() and X_fgcolor() naming scheme.

Thanks. I'll merge this but also keep the old names until a 2.0 release.

Should this be added to the ROADMAP?

Yes


Include node ID in the install API request

When using the API to install Presto, we should optionally allow inclusion of a UUID in the request, which may be used by the Agent to configure the Presto isntallation.

What is the use of this? (Might be its better for if a single system generates all the node.id).


Schematic of the production system

Diagram presented in the Spring O&C 2018 plus minor improvements.
Seangchan, if it looks Ok, please merge. If not, just let me know what to fix

Thanks Alan, it looks good.


User collection query has limit set to 10 for a single item fetch

Link to reproduction
No response
Describe the Bug
The following is the query passed to the DB adapter from the flow mentioned the file in the following link:
https://github.com/payloadcms/payload/blob/ae7d6f97d205491390f15850e5104c7abded1550/packages/payload/src/auth/strategies/apiKey.ts#L41
{"collection":"users","locale":"en","where":{"and":[{"apiKeyIndex":{"equals":"my-api-key-index"}}]},"limit":10,"pagination":true,"page":1}

The limit: 10 causes it to do a full collection scan and later once the query is resolved, payload only refers to the first item in the result.
CMIIW, apiKeyIndex is supposed to be unique for each API-Key, right ?
If so, the limit should be 1
To Reproduce
Any API call with payload-token in its cookie would trigger this flow.
Payload Version
2.22.0
Adapters and Plugins
No response

Another thing to add. apiKeyIndex is not an indexed field per the schema.
During load testing, we observed that the first request takes a decent amount of time (compared to the successive). The query with apiKeyIndex would take longer at first, and the same query later took significantly less time. I guess that the DB cached that query internally.
Have you considered indexing that key since every time authentication makes a query upon that field?

Hey @vibhor-web-headout — good catches. We will index the apiKeyIndex (wow) and also limit the documents to 1. Can also set pagination: false because that's also unnecessary within that find operation.
These changes should be made to v2 and v3.


Error in FreeRTOS port

I want to express my gratitude for your work and point out ( unfortunately ) an error -
https://github.com/MaJerle/lwgsm/blob/433e80a49f1951c25466ab3e7f18b7c3471f5df5/lwgsm/src/system/lwgsm_sys_freeRTOS.c#L51-L56
sys_mutex is created as recursive and try give ( ? ) as regular.
And unprotect ( L91-L95 ) correctly like this -
uint8_t
lwgsm_sys_unprotect(void) {
return xSemaphoreGiveRecursive(sys_mutex);
}
https://www.freertos.org/a00123.html
<This macro must also not be used on semaphores created using xSemaphoreCreateRecursiveMutex().>

Thanks, I have updated the code.

Thank you for your work.


Set parent with query params

how to set parent with query params?

@maplerain1984 Hi, I'm not sure what this should happen by query params, сould you set an example or describe the reasons for this need?


repository not found in HACS

Running all the latest version of HA (2023.10.1 OS 10.5) and HACS (1.33.0), I get a
Repository nechry/elco-remocon-net-appdaemon not found
when calling the repository from HACS through the link provided in the readme.md file. Anything I missed?

Please ignore,'Enable AppDaemon in HACS' was not properly set. It could make sense to add the prerequisite before the HACS link ;-).


Evidence of element handle corruption on the remote

selendroid-0.9.0 on Android 19 (4.4)
Randomly, when retrieving multiple elements from the remote with POST session/:sessionId/elements, the returned elements will seemingly either be in the wrong order, or they will be duplicated. This has been seen multiple times, only with selendroid, on maybe 10% of test runs, on the following assertions:
Using 'tag name' strategy:
https://github.com/theintern/intern/blob/48e810dcf5b5861b41b94572fcd6479274f82cfe/tests/lib/leadfoot/Session.js#L696
Test main - lib/leadfoot/Session - #getElements FAILED on selendroid 0.9.0 on ANDROID 19:
AssertionError: expected [ 'b4', 'b4', 'f', 'g' ] to deeply equal [ 'b3', 'b4', 'f', 'g' ]

Using 'xpath' strategy:
https://github.com/theintern/intern/blob/48e810dcf5b5861b41b94572fcd6479274f82cfe/tests/lib/leadfoot/Session.js#L699
Test main - lib/leadfoot/Session - #getElements FAILED on selendroid 0.9.0 on ANDROID 19:
AssertionError: expected [ 'g', 'f' ] to deeply equal [ 'f', 'g' ]

Because I have not been able to reliably reproduce this issue, I can’t say whether the first one is due to the remote returning the same element ID twice, or whether it is due to the remote pointing two distinct element IDs to the same DOM element. My best guess would be that both of these failures are due to parallel HTTP requests for retrieving the IDs from the elements, causing some sort of race condition/state corruption in the remote, leading it to sometimes return the wrong data for parallel request, but that is entirely speculative.

I'm closing this issue due to inactivity.
If is a question rather than an issue, please send questions to the selendroid user group.
If you think it's an actual problem with selendroid and still experience the issue described on the latest release of selendroid feel free to file a new issue. If you do please provide a concise reproducible test case and describe what results you are seeing and what results you expect.


Trying to drop a type with edb migration create causes a crash

EdgeDB Version: EdgeDB CLI 1.0.0+5724c50, 1.0+9ecadfc
OS Version: Windows 10 running WSL w/ Ubuntu 20.04 😬

Steps to Reproduce:

Initialize a project with the following schema definition:

module default {
  type Document {
    multi link entries -> Entry {
      constraint exclusive;
    }
    multi link fields := .entries.field;
    required link form -> Form;
  }

  type Entry {
    required link field -> Field;
    required property value -> str;
    link form := .field.form;
  }

  type Field {
    required property name -> str;

    link form := .<fields[IS Form];
  }

  type Form {
    required property name -> str {
      constraint exclusive;
    }

    multi link fields -> Field;
  }
}

edb migration create; edb migrate;
delete the Document type
edb migration create
crash

edgedb error: InternalServerError:
  Hint: This is most likely a bug in EdgeDB. Please consider opening an issue ticket at https://github.com/edgedb/edgedb/issues/new?template=bug_report.md
  Server traceback:
      Traceback (most recent call last):
        File "/home/ianch/.local/share/edgedb/portable/1.0/lib/python3.10/site-packages/edb/server/compiler_pool/worker.py", line 309, in worker
          res = meth(*args)
        File "/home/ianch/.local/share/edgedb/portable/1.0/lib/python3.10/site-packages/edb/server/compiler_pool/worker.py", line 202, in compile_in_tx
          units, cstate = COMPILER.compile_in_tx(cstate, *args, **kwargs)
        File "/home/ianch/.local/share/edgedb/portable/1.0/lib/python3.10/site-packages/edb/server/compiler/compiler.py", line 2137, in compile_in_tx
          return self._compile(ctx=ctx, source=source), ctx.state
        File "/home/ianch/.local/share/edgedb/portable/1.0/lib/python3.10/site-packages/edb/server/compiler/compiler.py", line 1654, in _compile
          return self._try_compile(ctx=ctx, source=original)
        File "/home/ianch/.local/share/edgedb/portable/1.0/lib/python3.10/site-packages/edb/server/compiler/compiler.py", line 1710, in _try_compile
          comp, capabilities = self._compile_dispatch_ql(
        File "/home/ianch/.local/share/edgedb/portable/1.0/lib/python3.10/site-packages/edb/server/compiler/compiler.py", line 1593, in _compile_dispatch_ql
          query = self._compile_ql_migration(ctx, ql)
        File "/home/ianch/.local/share/edgedb/portable/1.0/lib/python3.10/site-packages/edb/server/compiler/compiler.py", line 1091, in _compile_ql_migration
          proposed_ddl = s_ddl.statements_from_delta(
        File "/home/ianch/.local/share/edgedb/portable/1.0/lib/python3.10/site-packages/edb/schema/ddl.py", line 707, in statements_from_delta
          stmts = ddlast_from_delta(
        File "/home/ianch/.local/share/edgedb/portable/1.0/lib/python3.10/site-packages/edb/schema/ddl.py", line 688, in ddlast_from_delta
          ql_ast = command.get_ast(schema, context)
        File "/home/ianch/.local/share/edgedb/portable/1.0/lib/python3.10/site-packages/edb/schema/types.py", line 2173, in get_ast
          return super().get_ast(schema, context, parent_node=parent_node)
        File "/home/ianch/.local/share/edgedb/portable/1.0/lib/python3.10/site-packages/edb/schema/delta.py", line 2593, in get_ast
          return self._get_ast(schema, context, parent_node=parent_node)
        File "/home/ianch/.local/share/edgedb/portable/1.0/lib/python3.10/site-packages/edb/schema/objtypes.py", line 567, in _get_ast
          return super()._get_ast(schema, context, parent_node=parent_node)
        File "/home/ianch/.local/share/edgedb/portable/1.0/lib/python3.10/site-packages/edb/schema/types.py", line 779, in _get_ast
          return super()._get_ast(schema, context, parent_node=parent_node)
        File "/home/ianch/.local/share/edgedb/portable/1.0/lib/python3.10/site-packages/edb/schema/delta.py", line 2159, in _get_ast
          self._apply_fields_ast(schema, context, op)
        File "/home/ianch/.local/share/edgedb/portable/1.0/lib/python3.10/site-packages/edb/schema/delta.py", line 2240, in _apply_fields_ast
          assert all(
      AssertionError

Confirmed.


Use tree-sitter

Hello, https://github.com/atom/atom/issues/8669 is solved I believe. Would be awesome if you can get this working again! Would love to try this out!

Atom used to support only TextMate-style grammars. Now, Atom supports TextMate-style grammars and Tree Sitter grammars.
But to my knowledge, there is still no public API for letting arbitrary code do the parsing, so we are still blocked.


Initial tests of the Weak module

I realized we didn't have tests of Weak yet, so I played last night with writing some.
Because the GC may kick in, the interface is generally not sequentially consistent (nor is it intended to be safe to use in parallel).
Nevertheless, this was producing strange, out-of-thin-air(?) values:
Messages for test Lin DSL Weak test with Domain:

  Results incompatible with sequential execution

                                               |
                                Weak.set t 9 Some (9) : Ok (())
                                               |
                         .------------------------------------------.
                         |                                          |
            Weak.set t 9 None : Ok (())         Weak.get t 9 : Ok (Some<PHONE_NUMBER>0632))

Rebased on main and simplified src/weak/dune-rules to (test ...)s.
Curious to see if the new debug mode can help to reproduce ocaml/ocaml#11800 since the failing test case originates from this PR.

Rebased on latest main

In an attempt to get these into a mergable state,

I updated the Lin Hashset tests to allow exception throwing since most of these functions can raise Invalid_argument when used in parallel
I wrote STM tests of Weak Hashsets. Here I managed to extend @OlivierNicole's extensible ty type with a Tup6 constructor - and as a side-benefit figure out how we can add tuple combinators to STM :slightly_smiling_face:

Locally both of these now succeed. I'm hoping this is also the case for the CI targets.
Finally we don't need to run both Lin and STM tests in the CI. Here I'm leaning towards the STM ones - as they test stricter properties. This means the Lin tests should be disabled before merging (assuming CI actually is green... :crossed_fingers:)

Ouch, STM tests trigger a BUS error on the Weak Hashset tests on macOS 5.0.0
https://github.com/ocaml-multicore/multicoretests/actions/runs/3913104092/jobs/6688588995
random seed: 470692489
generated error fail pass / total     time test name

[ ]    0    0    0    0 / 1000     0.0s STM Weak test sequential
[ ]    0    0    0    0 / 1000     0.0s STM Weak test sequential (generating)
[✓] 1000    0    0 1000 / 1000     0.3s STM Weak test sequential

[ ]    0    0    0    0 / 1000     0.0s STM Weak test parallel
[ ]   53    0    0   53 / 1000    63.2s STM Weak test parallel
[ ]  141    0    0  141 / 1000   124.4s STM Weak test parallel
[ ]  196    0    0  196 / 1000   186.8s STM Weak test parallel
[ ]  271    0    0  271 / 1000   252.0s STM Weak test parallel
[ ]  375    0    0  375 / 1000   315.7s STM Weak test parallel
[✓]  383    0    1  382 / 1000   336.4s STM Weak test parallel

[ ]    0    0    0    0 / 1000     0.0s STM Weak HashSet test sequential
[✓] 1000    0    0 1000 / 1000     0.4s STM Weak HashSet test sequential

[ ]    0    0    0    0 / 1000     0.0s STM Weak HashSet test parallel
[ ]   51    0    0   51 / 1000    38.9s STM Weak HashSet test parallel (shrinking:   19.0052)
[ ]   51    0    0   51 / 1000    98.9s STM Weak HashSet test parallel (shrinking:   23.0034)
[ ]   51    0    0   51 / 1000   159.0s STM Weak HashSet test parallel (shrinking:   25.0124)
[ ]   51    0    0   51 / 1000   219.1s STM Weak HashSet test parallel (shrinking:   27.0081)
[ ]   51    0    0   51 / 1000   279.1s STM Weak HashSet test parallel (shrinking:   29.0113)
[ ]   51    0    0   51 / 1000   339.2s STM Weak HashSet test parallel (shrinking:   32.0109)
[ ]   51    0    0   51 / 1000   399.3s STM Weak HashSet test parallel (shrinking:   35.0062)
[ ]   51    0    0   51 / 1000   459.3s STM Weak HashSet test parallel (shrinking:   38.0082)
[ ]   51    0    0   51 / 1000   519.5s STM Weak HashSet test parallel (shrinking:   41.0050)
File "src/weak/dune", line 4, characters 7-16:
4 |  (name stm_tests)
           ^^^^^^^^^
(cd _build/default/src/weak && ./stm_tests.exe --verbose)
Command got signal BUS.
[ ]   51    0    0   51 / 1000   579.6s STM Weak HashSet test parallel (shrinking:   44.0023)

STM tests updated to reflect that find_all on Hashsets also may raise Invalid_argument

The previous CI runs had time outs due to excessive shrinking.
7ea00cb therefore adjusts the string argument shrinker to only reduce the string length (not the individual chars).
Even that may be too much, as Weak Hashsets depend on the GC which the tests have no control over.
To further reduce shrinking time, this is rebased on the stm-reduce-retries branch from #282.

Since Weak depends on the GC (which is out of our hands) the latest commit splits the test files in two, in an attempt to minimize the effects of a longer-running execution (with more GC calls).

Focusing on the lower-level API didn't trigger any crashes.
It timed out due to excessively long runs. The winner was on a Linux bytecode trunk run
which took 325min - or almost 5.5 hours :grimacing:
https://github.com/ocaml-multicore/multicoretests/actions/runs/3957933654/jobs/6778887520
Starting 2-th run

random seed: 429518331
generated error fail pass / total     time test name

[ ]    0    0    0    0 / 1000     0.0s STM Weak test sequential
[ ]    0    0    0    0 / 1000     0.0s STM Weak test sequential (generating)
[✓] 1000    0    0 1000 / 1000     2.1s STM Weak test sequential

[ ]    0    0    0    0 / 1000     0.0s STM Weak test parallel
[ ]    8    0    0    8 / 1000    84.8s STM Weak test parallel
[ ]   21    0    0   21 / 1000   146.4s STM Weak test parallel
[ ]   56    0    0   56 / 1000   208.0s STM Weak test parallel
[ ]   78    0    0   78 / 1000   268.7s STM Weak test parallel
[ ]   82    0    0   82 / 1000   358.6s STM Weak test parallel (shrinking:    0)
[ ]   82    0    0   82 / 1000  1410.1s STM Weak test parallel (shrinking:    0.0002)
[ ]   82    0    0   82 / 1000  2457.6s STM Weak test parallel (shrinking:    0.0003)
[ ]   82    0    0   82 / 1000  3505.2s STM Weak test parallel (shrinking:    0.0004)
[ ]   82    0    0   82 / 1000  3843.3s STM Weak test parallel (shrinking:    1)
[ ]   82    0    0   82 / 1000  4894.7s STM Weak test parallel (shrinking:    1.0002)
[ ]   82    0    0   82 / 1000  5141.1s STM Weak test parallel (shrinking:    2)
[ ]   82    0    0   82 / 1000  6192.7s STM Weak test parallel (shrinking:    2.0002)
[ ]   82    0    0   82 / 1000  6551.5s STM Weak test parallel (shrinking:    3)
[ ]   82    0    0   82 / 1000  7603.1s STM Weak test parallel (shrinking:    3.0002)
[ ]   82    0    0   82 / 1000  7786.8s STM Weak test parallel (shrinking:    4)
[ ]   82    0    0   82 / 1000  8838.3s STM Weak test parallel (shrinking:    4.0002)
[ ]   82    0    0   82 / 1000  9885.8s STM Weak test parallel (shrinking:    4.0003)
[ ]   82    0    0   82 / 1000 10933.1s STM Weak test parallel (shrinking:    4.0004)
[ ]   82    0    0   82 / 1000 11980.6s STM Weak test parallel (shrinking:    4.0005)
[ ]   82    0    0   82 / 1000 12623.3s STM Weak test parallel (shrinking:    5)
[ ]   82    0    0   82 / 1000 13675.0s STM Weak test parallel (shrinking:    5.0002)
[ ]   82    0    0   82 / 1000 14722.3s STM Weak test parallel (shrinking:    5.0003)
[ ]   82    0    0   82 / 1000 14926.9s STM Weak test parallel (shrinking:    6)
[ ]   82    0    0   82 / 1000 15978.6s STM Weak test parallel (shrinking:    6.0002)
[ ]   82    0    0   82 / 1000 17026.1s STM Weak test parallel (shrinking:    6.0003)
[ ]   82    0    0   82 / 1000 17163.9s STM Weak test parallel (shrinking:    7)
[ ]   82    0    0   82 / 1000 18215.4s STM Weak test parallel (shrinking:    7.0002)
[ ]   82    0    0   82 / 1000 18290.6s STM Weak test parallel (shrinking:    8)
[ ]   82    0    0   82 / 1000 19341.9s STM Weak test parallel (shrinking:    8.0002)
[ ]   82    0    0   82 / 1000 19521.4s STM Weak test parallel (shrinking:    9)
Error: The operation was canceled.

This indicates that the crashing is caused by the higher-level Weak Hashset API.
Since Weak.t values live in nested arrays there, they probably live longer - which may explain why the timing improvements from https://github.com/ocaml/ocaml/pull/11743 make them less likely (or eliminate them).

The parallel STM tests are not consistently triggering a failure.
I'm therefore trying a combination of sequential STM tests + parallel Lin tests.
(also rebased on latest main)

OK, this seems to work reasonably. There were 2 Windows threadomain failures:

one trunk bytecode crash and
one 5.0.0 timeout

I'll clean up the commits, rerun the CI and then hope to merge :crossed_fingers:

CI is happy Weak-test wise, so I'll merge.
The CI is however failing with the following unrelated errors:

a parallel Dynlink Windows 5.0.0 crash
2 threadomain timeouts on Windows trunk native+bytecode
a macOS trunk timeout on Out_channel tests


refactor: apply webpack-defaults

Note: there is more refactoring that will need to be done here that will be handled when tests are added. A Major needs to be released for a deprecation issue already fixed in master, need the breaking portions of defaults to go in with it.

Intended to be merged & released with fa800c6 as a part of 1.0.0 on a beta dist-tag once this has been finished and properly tested.
Further refactoring is required to align with the defaults eslint configuration.
BREAKING CHANGE:
Enforces NodeJS > 4.3 via engines

There in lies the problem, i'm no more familiar with it than you are. For the first pass, the intent was to make as few structural changes as possible while still getting the portions of defaults that require a semver major in place.
If you look at the transpiled output, less the obvious ES module / Import changes the change was kept as minimal as possible.

@michael-ciniawsky - Unless you have a strong objection, I'd prefer to leave functionality alone and just get the standards in place along with the breaking change already in master that people are waiting on.
I've tested this as it is manually in consuming projects, should be fine to get into master and out into a beta dist-tag for further testing. @sullenor and I will work out some testing & then try to address the long standing #6 & #16 before pushing an rc for 1.0.0

Nope please go ahead, I will also stop to do any refactorings other then plain webpack-defaults and make separate PR instead afterwards, the other way doesn't work out that well unfortunately 😛


docs: improve swr documentation

🔗 Linked issue
https://github.com/unjs/nitro/issues/603#issuecomment-1415832639
❓ Type of change

[x] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
The current documentation of swr is not correct: it is not a static build but SSR + cache headers.
📝 Checklist

[x] I have linked an issue or discussion.
[x] I have updated the documentation accordingly.

I need to add prerender as well too, don't you think?

Shouldn't this PR be merged?


Project serializer cleanup

Current coverage is 88.08% (diff: 100%)

Merging #579 into master will not change coverage

@@             master       #579   diff @@
==========================================
  Files           209        209
  Lines          8421       8421
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           7418       7418
  Misses         1003       1003
  Partials          0          0

Powered by Codecov. Last update 552d15f...91ae6ad

:+1:  lgtm!


Plaint text in default slot is not captured in a mounted snapshot

Version
1.0.0-beta.31
Reproduction link

tjw-lint/jest-serializer-vue-tjw/pull/46

Steps to reproduce
<template>
  <button>
    <slot></slot>
  </button>
</template>

test('Slot text', () => {
  const wrapper = mount(MyComponent, {
    slots: { default: 'text' }
  });

  // Expected: <button>text</button>
  // Actually: <button></button> ❌
  expect(wrapper)
    .toMatchSnapshot();
});

test('Slot markup', () => {
  const wrapper = mount(MyComponent, {
    slots: { default: '
text
' }
  });

  // Expected: <button>
text
</button>
  // Actually: <button>
text
</button> ✔
  expect(wrapper)
    .toMatchSnapshot();
})

What is expected?
<button>text</button>
What is actually happening?
<button></button>

This was originally reported in https://github.com/vuejs/vue-test-utils/issues/718

The example here fits within the documentation for Vue 2.6 and VTU. I feel like this should be included as part of the TODO list for VTU v1.

Hi @TheJaredWilcurt! Just check and tests not relying on snapshot serializer are properly working. Is it possible that this is related to the serialization of the component in Jest snapshots rather than an issue in VTU?

@afontcu No. This is not related to the serializer. I have updated the test case to prove this.

Hum, I might be missing something here, but I couldn't seem to reproduce the issue you are facing – ran both your tests in local and got them passing instantly (beta.31):

Tried with a SFC too (just in case), and they still pass.

I tried in CodeSandbox and could not reproduce the issue. So now I just need to find out what about my set up causes it to happen in my repo :confused:

Sure! I'm gonna close this, feel free to reopen or create a new one if you find any additional issue in VTU 😄


Configure browser redirects per custom domain

Preflight checklist

[X] I could not find a solution in the existing issues, docs, nor discussions.
[X] I agree to follow this project's Code of Conduct.
[X] I have read and am following this repository's Contribution Guidelines.
[X] I have joined the Ory Community Slack.
[X] I am signed up to the Ory Security Patch Newsletter.

Ory Network Project
dazzling-chandrasekhar-msru5m4b1c
Describe your problem
On the Account Experience > Browser redirects page, you can configure the redirect settings for your Ory project.
There are no issues if you use the default project URL or only have a single custom domain.
But if you have multiple custom domains, then configuring the redirects may be problematic.
Path values are limited since, if the redirect value is a path instead of a full URL, the path is relative to the project URL and not the Custom UI base URL. Since you can't host pages under the project URL (even with a custom domain), you'll likely need to set the redirect value using a full URL. But if you have multiple custom domains, then the full URL may not work with all of the custom domains.
Describe your ideal solution
Similar to the Account Experience > UI URLs page where you set the Custom UI Base URL and flow UI values separately for each custom domain, you should be able to set the redirects separately for each custom domain. Or at least be able to set a custom base URL for each custom domain, and then path redirect values should be relative to the base URL.
Workarounds or alternatives
Right now I am setting a return_to value in my code when there isn't already one specified, which can be dynamic based on where the code is running
Version
Ory Network
Additional Context
No response

Hey Brandon, I think that makes sense! Currently, multi-domain system is making it complicated to do what you're asking. We have it on the backlog to improve this architecture which would allow changes like the one you mentioned. Unfortunately, that's not going to happen soon as it's a quite complicated process to ensure there are no breaking changes.

No rush @aeneasr, it is not an urgent request. But I had noticed the limitation and wanted to jot it down.


cannot select video files on iOS

Hi,
Thanks for great plugin. on Android it works as expected with both videos and images. iOs works fine with images, but once I select even one video file, press 'Done' and nothing gets returned. If I console results here is what I get:
{"eventName":"getFiles","object":{"_observers":{"getFiles":[{}]},"output":""},"files":""}

If I select longer video, I click 'Done' and nothing happens.
Any help or advice is appreciated.

@bachras Yes, big video file create problem because in iOS that file will copy to your app directory. So, if the file is too big then it will failed sometime. I don't have a perfect solution now. Here:
https://github.com/jibon57/nativescript-mediafilepicker/blob/e9eb1daa444448312811149043744fba4daeb08e/src/mediafilepicker.ios.ts#L144
I have written code to copy the file to app directory. So, you can try to avoid it & use AVURLAsset or PHAsset directly. In this case you may need to add your own customize code to handle further process because iOS won't allow you to use/make file's url like Android do.
You can follow up here: https://github.com/jibon57/nativescript-mediafilepicker/issues/11


Synchronized scrolling

When having two (or more) windows side by side (thumbs up for the split lay-out!) it would be nice if synchronized scrolling was available.

Duplicate (apparently filter was to strict, because it did not show up when checking)


fixes #698, renamed multi-caps tparam in algebra system

Submission Checklist

[x] Run unit tests: ./runTests.py -j4 test/unit/math/rev/mat/functor/algebra_solver_test.cpp
[x] Run cpplint: make cpplint
[x] Declare copyright holder and open-source license: see below

Summary:
Renamed template parameter TS to S.
Intended Effect:
Allow Solaris compilation.
How to Verify:
Unit tests.
Side Effects:
no
Documentation:
n/a
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company):
Columbia University
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

Is this fix likely to work without changing anything in Stan Library? Also, do we have any other all capital problems, something like
git grep -E "typename [[:upper:]]{2}" stan/math

The template parameters are just local variable names, so the name doesn't matter (except apparently to Solaris).
Thanks for the grep ju ju.  I'll go back in and fix the rest.  I may not have computer power to run tests locally befor I have to leave tonight, but I'll push.
stan/math/prim/scal/fun/lb_constrain.hpp:template <typename T, typename TL>
stan/math/prim/scal/fun/lb_constrain.hpp:template <typename T, typename TL>
stan/math/prim/scal/fun/lb_free.hpp:template <typename T, typename TL>
stan/math/prim/scal/fun/lub_constrain.hpp:template <typename T, typename TL, typename TU>
stan/math/prim/scal/fun/lub_constrain.hpp:template <typename T, typename TL, typename TU>
stan/math/prim/scal/fun/lub_free.hpp:template <typename T, typename TL, typename TU>
stan/math/prim/scal/fun/ub_constrain.hpp:template <typename T, typename TU>
stan/math/prim/scal/fun/ub_constrain.hpp:template <typename T, typename TU>
stan/math/prim/scal/fun/ub_free.hpp:template <typename T, typename TU>
stan/math/rev/mat/fun/multiply.hpp:template <typename TA, int RA, int CA, typename TB, int CB>
stan/math/rev/mat/fun/multiply.hpp:template <typename TA, int CA, typename TB>
stan/math/rev/mat/fun/multiply.hpp:template <int RA, int CA, typename TB, int CB>
stan/math/rev/mat/fun/multiply.hpp:template <int CA, typename TB>
stan/math/rev/mat/fun/multiply.hpp:template <typename TA, int RA, int CA, int CB>
stan/math/rev/mat/fun/multiply.hpp:template <typename TA, int CA>
stan/math/rev/mat/fun/multiply.hpp:template <typename TA, int RA, int CA, typename TB, int CB>
stan/math/rev/mat/fun/multiply.hpp:template <typename TA, int CA, typename TB>
stan/math/rev/mat/fun/quad_form.hpp:template <typename TA, int RA, int CA, typename TB, int RB, int CB>
stan/math/rev/mat/fun/quad_form.hpp:template <typename TA, int RA, int CA, typename TB, int RB, int CB>
stan/math/rev/mat/fun/quad_form.hpp:template <typename TA, int RA, int CA, typename TB, int RB, int CB>
stan/math/rev/mat/fun/quad_form.hpp:template <typename TA, int RA, int CA, typename TB, int RB>
stan/math/rev/mat/fun/quad_form_sym.hpp:template <typename TA, int RA, int CA, typename TB, int RB, int CB>
stan/math/rev/mat/fun/quad_form_sym.hpp:template <typename TA, int RA, int CA, typename TB, int RB>
stan/math/rev/mat/fun/trace_gen_quad_form.hpp:template <typename TD, int RD, int CD, typename TA, int RA, int CA, typena
stan/math/rev/mat/fun/trace_gen_quad_form.hpp:template <typename TD, int RD, int CD, typename TA, int RA, int CA, typena
stan/math/rev/mat/fun/trace_gen_quad_form.hpp:template <typename TD, int RD, int CD, typename TA, int RA, int CA, typena
stan/math/rev/mat/fun/trace_quad_form.hpp:template <typename TA, int RA, int CA, typename TB, int RB, int CB>
stan/math/rev/mat/fun/trace_quad_form.hpp:template <typename TA, int RA, int CA, typename TB, int RB, int CB>
stan/math/rev/mat/fun/trace_quad_form.hpp:template <typename TA, int RA, int CA, typename TB, int RB, int CB>
stan/math/rev/mat/functor/algebra_solver.hpp:template <typename FS, typename F, typename T, typename FX>

OK, just fixed all those and ran local unit tests for the files I changed.

@bgoodri  Passed tests, so feel free to review and merge.

What's this new pr-merge job?  It's failing due to some kind of I/O problem.

@seantalts  How do I restart the pr-merge Jenkins job?  It looks like some kind of I/O flakiness.  This passed before I updated the readme, but I'm not sure that pr-merge thing ever ran the first time around.

Jenkins, retest this please.
I'm trying to finally switch us over to pipelines in the Math repo but I think I have a couple of final bugs to work out. For now we can use the legacy stuff, which I just re-enabled.

Thanks, @seantalts.  I have the upstream PR resubmitted for this, at which point the PR should work.  I'll kick off testing again then.

At this point the "default" Jenkins build passed, and the "pr-merge" thing will continue to be an "x" until I fix the new Pipeline builds (hopefully today). But you can safely ignore that x since the other two passed and I know what's wrong with that one.


proposal: time: add time.AddMonth to add  a month without normalization

While the time.AddDate is mathematically correct with the normalization results. The need to add/substract a month in date without nomalization is there in several areas.
func (t Time) AddMonth(months int) Time

AddMonth returns the time corresponding to adding the given number of months, increment/decrement years if needed and set days to t by staying in the range days of the month added, without normalize the result.
Example:
start := time.Date(2022, 10, 31, 0, 0, 0, 0, time.UTC)
oneMonthLater := start.AddMonth(1)
threeMonthLater := start.AddMonth(3)

fmt.Printf("oneMonthLater: start.AddMonth(1) = %v\n", oneMonthLater)
fmt.Printf("threeMonthLater: start.AddMonth(3) = %v\n", threeMonthLater)

// Output:
oneMonthLater: start.AddMonth(1) = 2022-11-30 00:00:00 +0000 UTC
threeMonthLater: start.AddMonth(3) = 2023-01-31 00:00:00 +0000 UTC

Same if we reduce the date by one month.
Example:
start := time.Date(2022, 03, 31, 0, 0, 0, 0, time.UTC)
oneMonthBefore := start.AddMonth(-1)

fmt.Printf("oneMonthBefore: start.AddMonth(-1) = %v\n", oneMonthBefore)

// Output:
oneMonthBefore: start.AddMonth(-1) = 2022-02-28 00:00:00 +0000 UTC

// The results should be the same for march 30, march 29 and march 28 for non leap year.

What is exactly meant by 'normalization'?

I took the term from the specification of AddDate method here

We have to have some kind of normalization, and in your example of 2022-03-31 minus one month, you can see that happening, in that we don't wind up with 2022-02-31.  I think that what you are suggesting is that if AddMonth produces a date that is past the end of the new month, we normalize by returning the last day of that month.

Yes exactly @ianlancetaylor. This could be practical to have that in addition of AddDate, there are certain areas where we consider each month separately.

I tend to find the need to add months/years indicates that a "civil time" representation may be better "instant time" (time.Time). Eg, here is a public civil time implementation: cloud.google.com/go/civil.Date.
time.Date already normalizes out of range days into the next month (eg, October 32 converts to November 1). It would be confusing to have 2 different conversations within the time package. Custom normalisation may be better handled outside the standard library.

I would expect that AddDate and AddMonth would do the same thing with what look like equivalent parameter lists.
One should not normalize differently from the other.
#19700 is the proposal (unprocessed) for civil time generally.

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

Why not use AddDate?
func AddMonth(t time.Time, m int) time.Time {
	x := t.AddDate(0, m, 0)
	if d := x.Day(); d != t.Day() {
		return x.AddDate(0, 0, -d)
	}
	return x
}

Thank you for your comments.
Yes since time.day() with a value of zero represents the last day of the previous month, it will be easy to achieve that.
Sames as you, I don't expecting different behaviour for using AddDate in Go, it's just strange to say, the last month of march, 31 is march, 03.
Like Ian said we have to have some kind of normalization for the days, even for other calendars than gregorian. All calendars contains 12 months, lunar month contains between 29 and 30 days, solar month contains 30 and 31 days, adding the regulations.
After reflexion, I feel like AddDate is very complete, unless if someone has something to add, we may close the proposal.


[SPARK-46207][SQL] Support MergeInto in DataFrameWriterV2

What changes were proposed in this pull request?
Add MergeInto support in DataFrameWriterV2
Why are the changes needed?
Spark currently supports merge into sql statement. We want DataFrame to have the same support.
Does this PR introduce any user-facing change?
Yes. This PR introduces new API like the following:
      spark.table("source")
        .mergeInto("target", $"source.id" === $"target.id")
        .whenNotMatched()
        .insertAll()
        .merge()

How was this patch tested?
new tests
Was this patch authored or co-authored using generative AI tooling?
No

cc @aokolnychyi @cloud-fan @dongjoon-hyun @viirya
This PR is ready for review. Could you please take a look when you have a moment? Thanks a lot!
There is still a mima check failure. It passed on my local, though. I will figure out what is wrong.

The test failure doesn't seem to be related to my changes.

Merged to master.
Thank you @huaxingao @cloud-fan @viirya

Thank you all very much for reviewing the PR!


test for nix-env regressions

nix-env has a reputation for being unreliable, but i would contend that this is not the fault of nix-env, but instead is the result of three factors:

there are a few pieces of metadata that are vitaly important to the operation of nix-env, but almost entirely irrelevant everywhere else
there is no automated testing done on any of this data
there is very little manual testing of nix-env

point 2 is definitely something that can be addressed.

Add a :+1: reaction to issues you find important.

What do people actually use nix-env for that can't be handled better by some other commands?
PS some other reasons why nix-env is terrible: https://web.archive.org/web/20240310235021/https://stop-using-nix-env.privatevoid.net/

advantages of nix-env:

interface more familiar to traditional package manager users.
allows upgrading individual packages (useful for users with slow internet connections)
allows easy installation of local derivations (useful for installing packages not yet included in any package sets)

until nix profile is considered stable, we should support nix-env.
there's actually not that much surface area to test, it's basically just changes to meta.priority and derivation names.

PS some other reasons why nix-env is terrible: https://web.archive.org/web/20240310235021/https://stop-using-nix-env.privatevoid.net/

several of those

nix-env is to be deprecated and not really recommend to be used. I think it is not worthwhile to invest more time into trying to keeps its broken mechanics working especially with the big footguns it has. Also it would hinder innovation and reworks.

allows upgrading individual packages (useful for users with slow internet connections)

This is a big footgun as NixOS doesn't guarantee binary combability when doing this and mixing different glib/driver/etc versions often results in strange and byzantine errors. Also this speaks against the NixOS philosophy of having one true source to your configuration.

allows easy installation of local derivations (useful for installing packages not yet included in any package sets)

It is trivial to do pkgs.callPackage on a downloaded file from a PR and include that in your configuration.

there's actually not that much surface area to test, it's basically just changes to meta.priority and derivation names.

pname can change and enforcing them to be stable just for nix-env would hindere so many tasks (like normalizing pnames in python packages but I doubt that with the current structure how pythonPackages's pname are generated even works good with nix-env) and the correct stable interface nix has is the attr for which we also create aliases when changing. Tools that use pname are broken by design and should be fixed instead.


Unable to find a specification for RNInputMask depended upon by react-native-text-input-mask

When i try  pod install this error returns
[!] Unable to find a specification for RNInputMask depended upon by react-native-text-input-mask
You have either:

mistyped the name or version.
not added the source repo that hosts the Podspec to your Podfile.

To resolve this:
add in podfile
pod 'react-native-text-input-mask', :path => '../node_modules/react-native-text-input-mask'
pod 'RNInputMask', :path => '../node_modules/react-native-text-input-mask/ios/InputMask'


🐛 [firebase_auth] com.google.android.gms:play-services-safetynet:17.0.0

Bug report
Describe the bug
Just submitted my app in PlayStore and received this:
com.google.android.gms:play-services-safetynet:17.0.0
This SDK version has a note from the SDK developer. Here's what the SDK developer told us:
The SafetyNet Attestation API is being discontinued and replaced by the new Play Integrity API. Begin migration as soon as possible to avoid user disruption. The Play Integrity API includes all the integrity signals that SafetyNet Attestation offers and more, like Google Play licensing and better error messaging. Learn more and start migrating at https://developer.android.com/training/safetynet/deprecation-timeline
I did a bit of research and saw someone mentioning that firebase auth is causing this.
Anyone face the same issue?

@ZXERSTON
This issue need to be handled and fixed by native firebase sdk itself, so flutterfire plugins can't do much about it.
There's similar issue open in android firebase sdk github in which you can follow-up for further updates: https://github.com/firebase/firebase-android-sdk/issues/3890
Closing from here.


UI sends usage statistics - possible production concern

The Egeria UI currently throws an error that can be seen in 'developer tools' '(index):1 Uncaught SyntaxError: The requested module '../vaadin-usage-statistics/vaadin-usage-statistics.js' does not provide an export named 'usageStatistics''
I noticed that the vaadin components perform useage tracking, and our UI is including<EMAIL_ADDRESS>The components themselves look ok being Apache 2.0, but the stats gathering is disconcerting. Even the vaadin site suggests that during production useage the stats are disabled - and the .js replaced with empty bodies. We at least need to ensure this happens when we deploy. The docs at https://github.com/vaadin/vaadin-usage-statistics also cover how to disable the stats gathering
It's crucial we are transparent and need to take the utmost care with any form of data gathering
Note - I cannot confirm 100% data is being captured, but this needs to be verified
This was found when debugging #1129
cc: @bogdan-sava @davidradl

Note during the build this appears
19:26:05 [INFO]     Vaadin collects development time usage statistics to improve this product. To opt-out, either run:
19:26:05 [INFO]     npm explore @vaadin/vaadin-usage-statistics -- npm run disable
19:26:05 [INFO]     to store disable statistics for the machine, or add
19:26:05 [INFO]     "vaadin": { "disableUsageStatistics": true }
19:26:05 [INFO]     to the project package.json and re-run npm install to disable statistics for the project.
19:26:05 [INFO]
19:26:05 [INFO]     For more details, see https://github.com/vaadin/vaadin-usage-statistics
19:26:05 [INFO]

This should be done before next release/any production useage IMO cc: @mstrelchuk

This is still being reported and could be a concern for any production use case. I would suggest they are disabled

still need to be investigate

@sarbull @bogdan-sava  Is this addressed now? If so can be closed

yes, i saw it some days ago, it can be disabled by a package.json property.. "vaadin": { "disableUsageStatistics": true }

@planetf1 this is because vaadin has an open-source components version and also paid components version, enhanced, updated, whatever, i think those statistics are for gathering components data on what people use and how, it's quite dangerous.
this is what they state they collect:
Collected data
- Vaadin products used in the application, including version numbers
- Frameworks used in the application, including version numbers
- Flow features used in the application, including version numers
- The first and last time a product was used
- The first time statistics were gathered
- Your Vaadin user account
- Whether you are a Vaadin Pro user or not (true/false)
- Browser user-agent string
- The IP address the statistics is sent from

in my opinion we can drop vaadin components and use @paper components or create new ones.

I'm not an expert on vaadin - it does seem widely used. It looks as if the docs do discuss how to remove stats capture -- my main concern was just to ensure this was absolutely clear to consumers, and most likely disabled by default. Over to the UI team to figure out best technology for the UI though. :-)

@planetf1 it seems that it is disabled by default here [0].
[0] - https://github.com/odpi/egeria-ui/blob/master/package.json#L8

Hopefully - that's good and we could close the issue. However I think it would be worthwhile checking for nothing untoward in the debugger/network trace. I know we had a few funnies in the early days with the vaadin code though that may well now be resolved.

@planetf1 this is visible in the build logs at npm install phase:
$<EMAIL_ADDRESS>postinstall /Users/lk61fu/projects/latest/egeria-ui/node_modules/@vaadin/vaadin-usage-statistics
$ node check.js


mxnet on spark ?

Is runing mxnet on top spark a thing that we can dream of ?

All dmlc projects are designed to be portable. If you see related project like xgboost, they are readily run on YARN, which means on most spark cluster which runs on YARN.


Nuke Image

Import image of a Nuke and assign it to the turtle.

#-----Nuclear Explosion-----
Explosion = 'Nuke_Explosion.gif'
wn.addshape(Explosion)
mascot3 = trtl.Turtle(shape = Explosion)
mascot3.penup()
mascot3.hideturtle()

Very clean and well written.


create a new method AbstractAPI._validate_spec

Created a new method AbstractAPI._validate_spec  to encapsulate the specification validation.
I need this feature because I have a custom validator that I used instead the swagger_spec_validator.

Coverage remained the same at 100.0% when pulling 7ee0d6288696e74b955979fef8a666c5d3c30c3b on dutradda:encapsulate_api_validate_spec into 4486438e70788c1bb24e35035f38c1550663dea1 on zalando:master.

lgtm

:+1:


QuickSort : Instead of taking pivot as 1st element, we should take the pivot as last element, due to time complexity

Instead of this
const pivotElement = array.shift(); // O(n)
we should use
const pivotElement = array.pop(); // O(1)
When taking the pivot as last element 2 test cases are failing.

QuickSort › should do stable sorting
QuickSort › should visit NOT SORTED array element specified number of times

Can I work on this issue ?

i would like to take this. can someone assign it to me please?


implemented handleing of _all request

closes #104

Coverage decreased (-0.9%) to 83.473% when pulling 2dfcdc769fea5225434de75de3afe34e1d83990d on einorler:issue104 into 5f996cfa8060c3c3195edbd8f190b8edd44948d0 on ongr-io:master.

Coverage increased (+0.2%) to 84.594% when pulling 6b5a1c69a8d0c8885fa14f3b2f0ef3196bf45e75 on einorler:issue104 into 5f996cfa8060c3c3195edbd8f190b8edd44948d0 on ongr-io:master.


How to start?

I like ideas of this project
Reading docs and examples for 3 days and still did not get the idea how to start
I created simple project https://github.com/coderany/publish
Running it by ./node_modules/.bin/noflo graphs/publish.fbp
but i got error
/Users/oleg/publish/node_modules/noflo/lib/Network.js:515
throw new Error("No component defined for inbound node " + edge.to.node);
^
Error: No component defined for inbound node Test
at Network.addEdge (/Users/oleg/publish/node_modules/noflo/lib/Network.js:515:15)
...
Tried to debug code, difficult to understand why component is not loaded
I think to covert this project to es6 and run with webpack, so i can easy debug and hot reload
Is it good idea to have fork of this project in es6?
Best regards
Oleg

@coderany have you npm installed the dependencies? What does ./node_modules/.bin/noflo list . say?

Olegs-iMac:publish oleg$ ./node_modules/.bin/noflo list .

Graph (/Users/oleg/publish/node_modules/noflo/src/components/Graph.coffee)
Inports: GRAPH
Outports:

core/Callback (/Users/oleg/publish/node_modules/noflo-core/components/Callback.coffee)
This component calls a given callback function for each IP it receives.  The Callback component is typically used to connect NoFlo with external Node.js code.
Inports: IN, CALLBACK
Outports: ERROR

core/Copy (/Users/oleg/publish/node_modules/noflo-core/components/Copy.coffee)
deep (i.e. recursively) copy an object
Inports: IN
Outports: OUT

core/DisconnectAfterPacket (/Users/oleg/publish/node_modules/noflo-core/components/DisconnectAfterPacket.coffee)
Forwards any packets, but also sends a disconnect after each of them
Inports: IN
Outports: OUT

core/Drop (/Users/oleg/publish/node_modules/noflo-core/components/Drop.coffee)
This component drops every packet it receives with no action
Inports: IN
Outports:

core/Group (/Users/oleg/publish/node_modules/noflo-core/components/Group.coffee)
Adds a set of groups around the packets received at each connection
Inports: IN, GROUP, THRESHOLD
Outports: OUT

core/Kick (/Users/oleg/publish/node_modules/noflo-core/components/Kick.coffee)
This component generates a single packet and sends it to the output port. Mostly usable for debugging, but can also be useful for starting up networks.
Inports: IN, DATA
Outports: OUT

core/MakeFunction (/Users/oleg/publish/node_modules/noflo-core/components/MakeFunction.coffee)
Evaluates a function each time data hits the "in" port and sends the return value to "out". Within the function "x" will be the variable from the in port. For example, to make a ^2 function input "return x*x;" to the function port.
Inports: IN, FUNCTION
Outports: OUT, FUNCTION, ERROR

core/Merge (/Users/oleg/publish/node_modules/noflo-core/components/Merge.coffee)
This component receives data on multiple input ports and sends the same data out to the connected output port
Inports: IN
Outports: OUT

core/Output (/Users/oleg/publish/node_modules/noflo-core/components/Output.coffee)
Sends the data items to console.log
Inports: IN, OPTIONS
Outports: OUT

core/ReadEnv (/Users/oleg/publish/node_modules/noflo-core/components/ReadEnv.coffee)
Reads an environment variable
Inports: KEY
Outports: OUT, ERROR

core/ReadGlobal (/Users/oleg/publish/node_modules/noflo-core/components/ReadGlobal.coffee)
Returns the value of a global variable.
Inports: NAME
Outports: VALUE, ERROR

core/Repeat (/Users/oleg/publish/node_modules/noflo-core/components/Repeat.coffee)
Forwards packets and metadata in the same way it receives them
Inports: IN
Outports: OUT

core/RepeatAsync (/Users/oleg/publish/node_modules/noflo-core/components/RepeatAsync.coffee)
Like 'Repeat', except repeat on next tick
Inports: IN
Outports: OUT

core/RepeatDelayed (/Users/oleg/publish/node_modules/noflo-core/components/RepeatDelayed.coffee)
Forward packet after a set delay
Inports: IN, DELAY
Outports: OUT

core/RunInterval (/Users/oleg/publish/node_modules/noflo-core/components/RunInterval.coffee)
Send a packet at the given interval
Inports: INTERVAL, START, STOP
Outports: OUT

core/RunTimeout (/Users/oleg/publish/node_modules/noflo-core/components/RunTimeout.coffee)
Send a packet after the given time in ms
Inports: TIME, START, CLEAR
Outports: OUT

core/SendNext (/Users/oleg/publish/node_modules/noflo-core/components/SendNext.coffee)
Sends next packet in buffer when receiving a bang
Inports: DATA, IN
Outports: OUT, EMPTY

core/Split (/Users/oleg/publish/node_modules/noflo-core/components/Split.coffee)
This component receives data on a single input port and sends the same data out to all connected output ports
Inports: IN
Outports: OUT

filesystem/BaseName (/Users/oleg/publish/node_modules/noflo-filesystem/components/BaseName.coffee)
Get the base name of the file
Inports: IN, EXT
Outports: OUT

filesystem/CopyFile (/Users/oleg/publish/node_modules/noflo-filesystem/components/CopyFile.coffee)
Inports: SOURCE, DESTINATION
Outports: OUT, ERROR

filesystem/CopyTree (/Users/oleg/publish/node_modules/noflo-filesystem/components/CopyTree.coffee)
Inports: FROM, TO
Outports: OUT, ERROR

filesystem/DirName (/Users/oleg/publish/node_modules/noflo-filesystem/components/DirName.coffee)
Get the directory path of a file path
Inports: IN
Outports: OUT

filesystem/DirectoryBuffer (/Users/oleg/publish/node_modules/noflo-filesystem/components/DirectoryBuffer.coffee)
Inports: COLLECT, RELEASE
Outports: OUT

filesystem/DirectoryGroupBuffer (/Users/oleg/publish/node_modules/noflo-filesystem/components/DirectoryGroupBuffer.coffee)
Inports: COLLECT, RELEASE
Outports: OUT

filesystem/ExtName (/Users/oleg/publish/node_modules/noflo-filesystem/components/ExtName.coffee)
Get the file extension for a file path
Inports: IN
Outports: OUT

filesystem/MakeDir (/Users/oleg/publish/node_modules/noflo-filesystem/components/MakeDir.coffee)
Create a directory
Inports: IN
Outports: OUT, ERROR

filesystem/MimeDocumentRouter (/Users/oleg/publish/node_modules/noflo-filesystem/components/MimeDocumentRouter.coffee)
Inports: ROUTES, IN
Outports: OUT, MISSED

filesystem/MimeRouter (/Users/oleg/publish/node_modules/noflo-filesystem/components/MimeRouter.coffee)
Inports: TYPES, ROUTES, IN
Outports: OUT, MISSED

filesystem/Normalize (/Users/oleg/publish/node_modules/noflo-filesystem/components/Normalize.coffee)
Normalize a path
Inports: IN
Outports: OUT

filesystem/ReadDir (/Users/oleg/publish/node_modules/noflo-filesystem/components/ReadDir.coffee)
Get a list of file paths inside a directory
Inports: SOURCE
Outports: OUT, ERROR

filesystem/ReadFile (/Users/oleg/publish/node_modules/noflo-filesystem/components/ReadFile.coffee)
Read a file and send it out as a string
Inports: IN, ENCODING
Outports: OUT, ERROR

filesystem/ReadFileRaw (/Users/oleg/publish/node_modules/noflo-filesystem/components/ReadFileRaw.coffee)
Read a file and send it out as a buffer
Inports: IN
Outports: OUT, ERROR

filesystem/ReadFileSync (/Users/oleg/publish/node_modules/noflo-filesystem/components/ReadFileSync.coffee)
Just like ReadFile, but blocks until content is read
Inports: IN, ENCODING
Outports: OUT, ERROR

filesystem/Resolve (/Users/oleg/publish/node_modules/noflo-filesystem/components/Resolve.coffee)
Resolve a relative path to an absolute one
Inports: IN
Outports: OUT

filesystem/Stat (/Users/oleg/publish/node_modules/noflo-filesystem/components/Stat.coffee)
Read statistics of a file
Inports: IN
Outports: OUT, ERROR

filesystem/Unlink (/Users/oleg/publish/node_modules/noflo-filesystem/components/Unlink.coffee)
Remove a file
Inports: IN
Outports: OUT, ERROR

filesystem/WriteFile (/Users/oleg/publish/node_modules/noflo-filesystem/components/WriteFile.coffee)
Write a string into a file
Inports: IN, FILENAME
Outports: OUT, ERROR

filesystem/WriteFileRaw (/Users/oleg/publish/node_modules/noflo-filesystem/components/WriteFileRaw.coffee)
Write a buffer into a file
Inports: IN, FILENAME
Outports: OUT, ERROR

publish/Test (/Users/oleg/publish/components/Test.js)
This component receives data on a single input  port and sends the same data out to the output port
Inports: IN
Outports: OUT

Yea i see now
changed this
Read(filesystem/ReadFile) OUT -> IN Test()
Test() OUT -> IN Display(core/Output)

'package.json' -> IN Read

to this
Read(filesystem/ReadFile) OUT -> IN Test(publish/Test)
Test(publish/Test) OUT -> IN Display(core/Output)

'package.json' -> IN Read

now works, thanks

Now i want to load this app in noflo-ui, but did not find the place where to read about how i can to it.
Also still did not understand can i write code in my IDE and reload it in noflo-ui instead of writing code inside flo-ui?

@coderany two options: noflo-nodejs and then Flowhub live mode, or sync the project to Flowhub from GitHub. I'm closing this issue here since this is more about noflo-ui.


init, Introspection: Tells me that schema postgres is not empty, does not even exist though

When introspecting a Postgres DB for a "Starter Kit" init run, I entered database postgres and schema my_db. Something goes wrong, and the error message tells me that schema 'postgres' is not empty. Something is getting confused here.

C:\Users\Jan\Documents\throwaway>prisma2 init dafasdf3422

 SUCCESS  Connected to PostgreSQL database as postgres

The PostgreSQL schema `postgres` is not empty.
When using a starter kit, you must provide an empty schema.
Create a new PostgreSQL schema or use an empty one.

┌─ Database options ──────────────────────────────────────────────────────┐
│                                                                         │
│ > Create new PostgreSQL schema   Start from scratch                     │
│                                                                         │
└─────────────────────────────────────────────────────────────────────────┘

< Back (Database credentials)

I am able to reproduce this.
This occurs when you put the schema in the Schema(optional) field in the database credentials form. It is not being used by the cli

@pantharshit00 can you please quickly re-triage this one?

This is currently not reproducible as the database/schema entered in the credentials form is completely ignored. Will have to be retested when this is fixed.


Feature - Create wallet for broker

Description
This PR adds all applicable RPCs and command for sparkswap wallet create
Related PRs
List related PRs if applicable
Todos

[ ] Tests
[ ] Documentation
[ ] Link to Trello

@treygriffith thanks for reviewing


make IsValidAddr private and extend regex to account for 0 length string

Description

closes: #687

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (see CONTRIBUTING.md)
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Code follows the module structure standards.
[x] Wrote unit and integration tests
[x] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[x] Added relevant godoc comments.
[x] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[x] Re-reviewed Files changed in the Github PR explorer
[x] Review Codecov Report in the comment section below once CI passes

Codecov Report

Merging #723 (252a6f1) into main (dd9c385) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #723   +/-   ##
=======================================
  Coverage   79.63%   79.63%
=======================================
  Files         145      145
  Lines       10676    10676
=======================================
  Hits         8502     8502
  Misses       1757     1757
  Partials      417      417

Impacted Files
Coverage Δ

...dules/apps/27-interchain-accounts/types/version.go
100.00% <100.00%> (ø)


Installation of @tensorflowtfjs-node is not possible

This is when I installed it.
I can't solve it.
What shouldI do?
E:\jslife_WX\wxjslife_rebuild_face>npm install

<EMAIL_ADDRESS>install E:\jslife_WX\wxjslife_rebuild_face\node_modules@tensorflow\tfjs-node
node scripts/install.js

Downloading libtensorflow
events.js:173
throw er; // Unhandled 'error' event
^

Error: connect ETIMEDOUT <IP_ADDRESS>:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1083:14)
Emitted 'error' event at:
at TLSSocket.socketErrorListener (_http_client.js:397:9)
at TLSSocket.emit (events.js:197:13)
at emitErrorNT (internal/streams/destroy.js:82:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
at processTicksAndRejections (internal/process/next_tick.js:76:17)
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^3.0.0 || ^4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed.
You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node scripts/install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

network error, Try using vpn

Closing because it's not related to face-api.js.


Carthage build warnings

ld: warning: directory not found for option '-F/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS9.1.sdk/Developer/Library/Frameworks'
Similar problem

/Carthage/Checkouts/SwiftyUserDefaults/SwiftyUserDefaultsTests/SwiftyUserDefaultsTests.swift:44:23: warning: '?=' is deprecated: Please migrate to static keys and use this gist: https://gist.github.com/radex/68de9340b0da61d43e60

//Carthage/Checkouts/SwiftyUserDefaults/SwiftyUserDefaultsTests/SwiftyUserDefaultsTests.swift:72:24: warning: '+=' is deprecated: Please migrate to static keys to use this.

/Carthage/Checkouts/SwiftyUserDefaults/SwiftyUserDefaultsTests/SwiftyUserDefaultsTests.swift:86:23: warning: '++' is deprecated: Please migrate to static keys to use this.

ld: warning: directory not found for option '-F/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS9.1.sdk/Developer/Library/Frameworks'

@mrahmiao do you still have this problem? The other warnings are working as designed.

Ah, nevermind, I see the same warning. Not sure what's the cause but I'll accept a fix.

Hello,
I still get a warning for stuff like:
Carthage/Checkouts/SwiftyUserDefaults/SwiftyUserDefaultsTests/SwiftyUserDefaultsTests.swift:44:23: warning: '?=' is deprecated
...
ld: warning: directory not found for option '-F/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS9.2.sdk/Developer/Library/Frameworks'
ld: warning: directory not found for option '-F/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS9.2.sdk/Developer/Library/Frameworks'

@ton03 I'll accept a patch.

I receive quite a lot of deprecation warnings when building through carthage.

@ton03 I no longer reproduce any warnings except for deprecation warnings (working as intended) while updating with carthage. I'm closing this issue, but let me know if you can still see the problem.


'code' is not recognized as an internal or external command, operable program or batch file.

"code" commend doesn't work in my cmd. O/S windows.

According to the documentation, this setting is different for each OS.

Note: Users on macOS must first run a command (Shell Command: Install 'code' command in PATH) to add VS Code executable to the PATH environment variable. Read the macOS setup guide for help. Windows and Linux installations should add the VS Code binaries location to your system path. If this isn't the case, you can manually add the location to the Path environment variable ($PATH on Linux). For example, on Windows, VS Code is installed under AppData\Local\Programs\Microsoft VS Code\bin.

I fixed the issue:
setting the environment variable path to C:\Users\chawki\AppData\Local\Programs\Microsoft VS Code\bin fixed the issue, now I can open the vs code through cmd using the code commend


Fixed README formatting

Fixed some Markdown formatting issues

Ahhh yes. I've been meaning to do this for a while. Just low down on the priority list.
Thanks Lindsay.


update storage README

Pull Request Checklist
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.

[ ] C++ Guidelines
[ ] Doxygen docs
[ ] Unit tests
[ ] No unwanted commits/changes
[ ] Descriptive title/description

[ ] PR is single purpose
[ ] Related issue listed

[ ] Comments in source
[ ] No typos
[ ] Update changelog
[ ] Not work-in-progress
[ ] External references or docs updated
[ ] Self review of PR done
[ ] Any breaking changes?

@Jinming-Hu, this PR is a little old, do you still need it? Did you get the info you needed from Rick?

@antkmsft I'll resume this work when I finish the test-proxy thing.


The splatting operator '@' cannot be used to reference variables  in an expression. '@vis' can be used only as an argument to a c ommand. To reference variables in an expression use '$vis'

Description
At line:1 char:13

npm install @vis.gl/react-google-maps

        ~~~~

The splatting operator '@' cannot be used to reference variables
in an expression. '@vis' can be used only as an argument to a c
ommand. To reference variables in an expression use '$vis'.
+ CategoryInfo          : ParserError: (:) [], ParentContai
nsErrorRecordException
+ FullyQualifiedErrorId : SplattingNotPermitted
Steps to Reproduce
npm install @vis.gl/react-google-maps
Environment

Library version:
Google maps version: weekly
Browser and Version:
OS:

Logs
No response

@hitecSmartHome was that PowerShell / Windows?

Yes. It was vscode terminal on windows. But as soon as i submitted the issue, seen the solution in the Readme. Sorry for that

No worries 👍