Array expansion

Thanks for your work on json2csv.
I'm using node 8.11.3, json2csv 4.2.1
I have a large number of JSON objects with several arrays. A subset of one of my records, for example,
{
	"time": "2018-08-07T22:00:35.575Z",
	"inlet": {
		"flows": [207, 317, 345, 352, 348, 346, 349, 345, 336, 330, 346, 332, 339, 365, 385, 409, 417, 419, 421, 429, 423, 422, 418, 439, 443, 448, 432, 419, 429, 439, 383, 366, 237],
		"means": [0.548951717333687, 0.8406354671220563, 0.9149810689134787, 0.933206817932239, 0.9247471610762611, 0.9168788128949606, 0.9254150874775281, 0.9170068953927532, 0.8911966615783491, 0.8749473964939183, 0.9155256514211296, 0.8829758872332784, 0.8989634548844809, 0.9657303679087027, 1.0246303084118025, 1.0887194118379835, 1.108067517044572, 1.111594746323376, 1.1146008656495832, 1.1358446883132844, 1.1245821772758002, 1.119729111463641, 1.108425133801527, 1.1646496916729985, 1.1751733505851558, 1.1886971762528373, 1.147694797984108, 1.1150703436507605, 1.140010305499161, 1.164056160033142, 1.0158580993586541, 0.9728217362440625, 0.6286119309347284, 12441.70041100624],
		"stdevs": [0.00005497610380381435, 0.00008843662860852586, 0.00008283540767296093, 0.00013295673516695584, 0.00017497786183360284, 0.00019084337585346, 0.00010871833209188608, 0.00020656837508053138, 0.00006857962287586395, 0.00011521769886983614, 0.000384152157829325, 0.0002734810471114413, 0.00009638047574794804, 0.00041522057619945983, 0.0004167716135420285, 0.00047361578729767647, 0.00020471680681546366, 0.00004962179871125904, 0.00037840468318034226, 0.00037648688407498026, 0.00028926847520908353, 0.000024912389564306636, 0.00012330933629747242, 0.000052628916609411824, 0.00006570607701290587, 0.000029302237876587255, 0.000179043172294584, 0.0004468921052008312, 0.000218601285335942, 0.00013741915087460034, 0.00007817260583762753, 0.00021871779188830542, 0.00004837312684992989, 0.9572015723202276]
	}
}

To explore this data in Excel, I'd like it in CSV format.
If my field list contains "inlet.flows", I get a single CSV volumn containing the whole array.
I couldn't work out how to specify the field list to extract a single member of the array (e.g. inlet.flows.0).
I'd like to be able to tell json2csv to "give me every element of this array in its own column".

Hi @johnyesberg,
Unfortunately, the flatten option doesn't unwind arrays.
We might add more options to it in the future but for now, it's just not there.
For now, you can achieve your goal with some pre-processing:
const Json2CsvParser = require("json2csv").Parser;

const data = [{
	"time": "2018-08-07T22:00:35.575Z",
	"inlet": {
		"flows": [207, 317, 345, 352, 348, 346, 349, 345, 336, 330, 346, 332, 339, 365, 385, 409, 417, 419, 421, 429, 423, 422, 418, 439, 443, 448, 432, 419, 429, 439, 383, 366, 237],
		"means": [0.548951717333687, 0.8406354671220563, 0.9149810689134787, 0.933206817932239, 0.9247471610762611, 0.9168788128949606, 0.9254150874775281, 0.9170068953927532, 0.8911966615783491, 0.8749473964939183, 0.9155256514211296, 0.8829758872332784, 0.8989634548844809, 0.9657303679087027, 1.0246303084118025, 1.0887194118379835, 1.108067517044572, 1.111594746323376, 1.1146008656495832, 1.1358446883132844, 1.1245821772758002, 1.119729111463641, 1.108425133801527, 1.1646496916729985, 1.1751733505851558, 1.1886971762528373, 1.147694797984108, 1.1150703436507605, 1.140010305499161, 1.164056160033142, 1.0158580993586541, 0.9728217362440625, 0.6286119309347284, 12441.70041100624],
		"stdevs": [0.00005497610380381435, 0.00008843662860852586, 0.00008283540767296093, 0.00013295673516695584, 0.00017497786183360284, 0.00019084337585346, 0.00010871833209188608, 0.00020656837508053138, 0.00006857962287586395, 0.00011521769886983614, 0.000384152157829325, 0.0002734810471114413, 0.00009638047574794804, 0.00041522057619945983, 0.0004167716135420285, 0.00047361578729767647, 0.00020471680681546366, 0.00004962179871125904, 0.00037840468318034226, 0.00037648688407498026, 0.00028926847520908353, 0.000024912389564306636, 0.00012330933629747242, 0.000052628916609411824, 0.00006570607701290587, 0.000029302237876587255, 0.000179043172294584, 0.0004468921052008312, 0.000218601285335942, 0.00013741915087460034, 0.00007817260583762753, 0.00021871779188830542, 0.00004837312684992989, 0.9572015723202276]
	}
}];

const processedData = data.map(record => ({
    ...record,
    inlet: {
        flows: { ...record.inlet.flows },
        means: { ...record.inlet.means },
        stdevs: { ...record.inlet.stdevs },
    }
}));

const parser = new Json2CsvParser({ flatten: true })
parser.parse(processedData);

Closing this since we haven't heard from you in a while. Feel free to reopen.

I am facing the same challenge and would love it if someone were willing to work on this.
Basically I want to tell json2csv in an option somewhere that a field a should be treated as an "array column" of a given/fixed/max size, say 128 elements. Then that field should be "exploded"/"split"/"multiplied" into 128 fields: a:0, a:1, ...., a:127

@jacobq
Is it correct that from:
const data = [{
	"time": "2018-08-07T22:00:35.575Z",
	"means": [1,2,3],
	"stdevs": [4,5,6]
}];

you'd like to get:
"time","means[0]","means[1]","means[2]","stdevs[0]","stdevs[1]","stdevs[2]"
"2018-08-07T22:00:35.575Z",1,2,3,4,5,6
}];

???
How would you deal with different elements having arrays of different length?
If you set a max lenght as you suggest, what would you do with arrays larger than that?
As of today:
You can achieve that using the fields option. Although, I admit that it might be a bit verbose.
{
  fields: [
    {
      label: 'time',
      value: 'time'
    },
    {
      label: 'means[0]',
      value: 'means[0]'
    },
    {
      label: 'means[1]',
      value: 'means[1]'
    },
    {
      label: 'means[2]',
      value: 'means[2]'
    },
    {
      label: 'stdevs[0]',
      value: 'stdevs[0]'
    },
    {
      label: 'stdevs[1]',
      value: 'stdevs[1]'
    },
    {
      label: 'stdevs[2]',
      value: 'stdevs[2]'
    }
  }
}

You can achieve it with some preprocessing as I showed above (the same thing could be applied to an object stream easily).

That's close. Thanks for mentioning the work-around; I didn't realize I could use [...] in path specifications (and I haven't tried using flatten yet). I'm working on a fork / PR right now to do it more ergonomically / the way I want to.

How would you deal with different elements having arrays of different length?

The CSV format itself is restricted to a fixed number of columns/fields so it would be up to the user of json2csv to specify an appropriate size for the expansion.

If you set a max length as you suggest, what would you do with arrays larger than that?

Arrays that have fewer elements would just have no values in the unused fields. Arrays with more would have excess elements omitted. We may also want to emit a warning message or perhaps throw an error (if the user opts-in to that behavior).

I think it's a little trickier than your example shows too because I need support for nesting & unwinding.
Input
const items = [{
  name: "One",
  measurements: [{
    xs: [1, 2, 3],
    ys: [2, 4, 6],
    zs: [3, 6, 9]
  }, {
    xs: [42],
    ys: [53],
    zs: [64]
  }]
}, {
{
  name: "Two",
  measurements: [{
    xs: [10, 20, 30],
    ys: [20, 40, 60],
    zs: [30, 60, 90]
  }]
}}]

Desired output
name,x:0,x:1,x:2,y:0,y:1,y:2,z:0,z:1,z:2
One,1,2,3,2,4,6,3,6,9,
One,42,,,53,,,64,,,
Two,10,20,30,20,40,60,30,60,90


fix(size): replaced SI prefixes with IEC prefixes

I tidied up the code (from the first commit). Things to note:

added explicit whitespace (" ") in string concatenation
added explicit const for "i" for use in string concatenation
added alias for 1024 (because it's used several times)
if only 1 value is converted to string, then used more readable .toString() in string concatenation
the function runs in O(1) using log with base 1024 to get the power, but not more than UNIT_CHARS.length - 1 (because YiB is the last unit which is 2^10^8)
I think I followed all the styling conventions from this project (I also used prettier)

Closes #2139.

Thanks for looking into this

@razzeee, could you please tell me when the main branch is released into production? Is there a constant interval or is it done on-demand?

It should start to show up as soon as the builds are done, but it sometimes takes some more time to get cleared out of the different caches.
So wait for https://github.com/flathub/website/actions and then some more :)


quote the output of git status -s

:pushpin: Commit 665a6a8 has been approved by japaric

@homunkulus r+

:hourglass: Testing commit 665a6a8 with merge 665a6a8...

:sunny: Test successful - status-travis
Approved by: japaric
Pushing 665a6a8fb496b626f4618e2b2a56b30ee7412736 to master...


connection tracking

Add to connecting tracking information on specific flow:
(1) Total Bytes
(2) Total Packets
(3) Avg. packet size
etc.
(Preferable per direction)

Design doc
https://docs.google.com/document/d/12rNCWyishTMjKLWKk-Orq68hymcEMqm__ETaLxc59Xg/edit?usp=sharing


Update Rust crate thiserror to v2

This PR contains the following updates:

Package
Type
Update
Change

thiserror
dependencies
major
1.0 -> 2.0

Release Notes

dtolnay/thiserror (thiserror)
v2.0.3
Compare Source

Support the same Path field being repeated in both Debug and Display representation in error message (#383)
Improve error message when a format trait used in error message is not implemented by some field (#384)

v2.0.2
Compare Source

Fix hang on invalid input inside #[error(...)] attribute (#382)

v2.0.1
Compare Source

Support errors that contain a dynamically sized final field (#375)
Improve inference of trait bounds for fields that are interpolated multiple times in an error message (#377)

v2.0.0
Compare Source
Breaking changes

Referencing keyword-named fields by a raw identifier like {r#type} inside a format string is no longer accepted; simply use the unraw name like {type} (#347)
This aligns thiserror with the standard library's formatting macros, which gained support for implicit argument capture later than the release of this feature in thiserror 1.x.
#[derive(Error, Debug)]
#[error("... {type} ...")]  // Before: {r#type}
pub struct Error {
    pub r#type: Type,
}

Trait bounds are no longer inferred on fields whose value is shadowed by an explicit named argument in a format message (#345)
// Before: impl<T: Octal> Display for Error<T>
// After: impl<T> Display for Error<T>
#[derive(Error, Debug)]
#[error("{thing:o}", thing = "...")]
pub struct Error<T> {
    thing: T,
}

Tuple structs and tuple variants can no longer use numerical {0} {1} access at the same time as supplying extra positional arguments for a format message, as this makes it ambiguous whether the number refers to a tuple field vs a different positional arg (#354)
#[derive(Error, Debug)]
#[error("ambiguous: {0} {}", $N)]
//                  ^^^ Not allowed, use #[error("... {0} {n}", n = $N)]
pub struct TupleError(i32);

Code containing invocations of thiserror's derive(Error) must now have a direct dependency on the thiserror crate regardless of the error data structure's contents (#368, #369, #370, #372)

Features

Support disabling thiserror's standard library dependency by disabling the default "std" Cargo feature: thiserror = { version = "2", default-features = false } (#373)

Support using r#source as field name to opt out of a field named "source" being treated as an error's Error::source() (#350)
#[derive(Error, Debug)]
#[error("{source} ==> {destination}")]
pub struct Error {
    r#source: char,
    destination: char,
}

let error = Error { source: 'S', destination: 'D' };

Infinite recursion in a generated Display impl now produces an unconditional_recursion warning (#359)
#[derive(Error, Debug)]
#[error("??? {self}")]
pub struct Error;

A new attribute #[error(fmt = path::to::myfmt)] can be used to write formatting logic for an enum variant out-of-line (#367)
#[derive(Error, Debug)]
pub enum Error {
    #[error(fmt = demo_fmt)]
    Demo { code: u16, message: Option<String> },
}

fn demo_fmt(code: &u16, message: &Option<String>, formatter: &mut fmt::Formatter) -> fmt::Result {
    write!(formatter, "{code}")?;
    if let Some(msg) = message {
        write!(formatter, " - {msg}")?;
    }
    Ok(())
}

Enums with an enum-level format message are now able to have individual variants that are transparent to supersede the enum-level message (#366)
#[derive(Error, Debug)]
#[error("my error {0}")]
pub enum Error {
    Json(#[from] serde_json::Error),
    Yaml(#[from] serde_yaml::Error),
    #[error(transparent)]
    Other(#[from] anyhow::Error),
}

v1.0.69
Compare Source

Backport 2.0.2 fixes

v1.0.68
Compare Source

Handle incomplete expressions more robustly in format arguments, such as while code is being typed (#341, #344)

v1.0.67
Compare Source

Improve expression syntax support inside format arguments (#335, #337, #339, #340)

v1.0.66
Compare Source

Improve compile error on malformed format attribute (#327)

Configuration
📅 Schedule: Branch creation - "before 12am on sunday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path libixx/Cargo.toml --package<EMAIL_ADDRESS>--precise 2.0.3
    Updating crates.io index
error: failed to select a version for the requirement `thiserror = "^1.0.64"`
candidate versions found which didn't match: 2.0.3
location searched: crates.io index
required by package `tree-sitter-highlight v0.24.3`
    ... which satisfies dependency `tree-sitter-highlight = "^0.24"` (locked to 0.24.3) of package `ixx v0.0.0-git (/var/lib/renovate/repos/github/NuschtOS/ixx/ixx)`


Directories in store cannot contain colons

pnpm version:
0.45.0
Code to reproduce the issue:
pnpm i<EMAIL_ADDRESS>
Expected behavior:
Successful installation
Actual behavior:
There is an error when creating a folder in the store for the git-hosted package. The reason for that is because the folder name cannot contain a colon.
Additional information:

node -v prints: 7.1.0
Windows, OS X, or Linux?: Windows

oh gosh


[CARBONDATA-3020] support lz4 as column compressor

lz4  looks not much difference than snappy.
Test Case 1
Data generated by tpch-dbgen(lineitem)
Loading Performance(compress)
create table with different 'carbon.column.compressor'
scale factor=10 / 7.3G

compressor
load time
file size after loading

snappy
453.82s
2.1G

zstd
466.752s
1.6G

lz4
443.373s
2.1G

Query Performance(decompress)
To force carbon to decompress the data, we create a spark project to select * from TABLE and iterate the result rdd. The total execution time is recorded for comparison.
scale factor=10 / 7.3G

compressor
full scan time (s)

snappy
128.379

zstd
134.4814

lz4
131.732

Test Case 2
Data generated by org.apache.carbondata.spark.util.DataGenerator
Loading Performance(compress)
100 millions records / 8.7G

compressor
load time
file size after loading

snappy
289.337s
2.5G

zstd
219.1s
1.1G

lz4
285.072s
2.3G

Query Performance(decompress)
100 millions records / 8.7G

compressor
full scan time (s)

snappy
133.752

zstd
144.801

lz4
134.938

Reference
Benchmark from https://github.com/lz4/lz4

Compressor
Ratio
Compression
Decompression

LZ4 default (v1.8.2)
2.101
730 MB/s
3900 MB/s

Snappy 1.1.4
2.091
525 MB/s
1750 MB/s

[Zstandard] 1.3.4 -1
2.877
470 MB/s
1380 MB/s

LZ4 HC -9 (v1.8.2)
2.721
40 MB/s
3920 MB/s

Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[ ] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8578/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/508/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/341/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8588/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/518/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/349/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/350/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/527/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8597/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/360/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8607/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/537/

better to provide performance test result for this

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/705/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8772/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/527/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/806/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9071/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/1096/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1307/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9359/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/1098/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9361/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1309/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/1984/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2161/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/56/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/55/

Build Failed  with Spark 2.4.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.4/56/


[CI] Fix tuto deps

The vmas dep was missing in the docs requirement

yep i downloaded the artifact and this fixed it


Setup Windows builds

Will need to be open-sourced to do this for free.

Changed the title of this; TravisCI supports a Windows build environment.


Switch from SentEmailHarness to QueuedEmailHarness in notify_participant tests

We have two test helpers for testing emails - SentEmailHarness and QueuedEmailHarness. The former mocks the actual mailer call, whereas the latter picks values from the database queue (bypassing the mailer call).
We don't use the SentEmailHarness almost everywhere in our test suite, except for

FlushEmailQueue, which is valid - since we're testing the queue itself.
TestNotifyParticipants - we shouldn't have to do this, QueuedEmailHarness should work just fine since notify_participants writes to the email queue

Hey, I am looking to contribute to my first open source project, and I was wondering if you'd be open to me making a fix to this issue.

@redixhumayun: absolutely :) Let us know if you need help.

@redixhumayun And be sure to check out #4555 from @misara for their previous attempt. Maybe you can work out a solution together?

@whit537 I'll make sure to do that :)

Hey, so I have a pretty noob question here. I have been trying to get this running locally on my Mac and I am running into some issues. When I run the
scripts/bootstrap-debian.sh command, I get the following error after entering my password
sudo: apt-get: command not found. My question is should I install all the required dependencies myself using homebrew? I already have postgresql up and running, but probably the others?
Also, I tried running the make -j$(nproc) schema fake command but that eventually errors out with the following errors
make: env/bin/honcho: No such file or directory make: *** [fake] Error 1
fatal error: too many errors emitted, stopping now [-ferror-limit=]     20 errors generated.     error: command 'cc' failed with exit status 1
Not sure how to proceed

Yeah, you don't want to run bootstrap-debian.sh, that's only for Linux Debian based distros.
You want to make sure you have the postgres depdenencies and Python 2.7. After you do that you'll want to create the DB like instructed here: https://github.com/gratipay/gratipay.com#table-of-contents
and then make env and let us know the output of that command.

Do you use homebrew? I think that's how I installed postgresql.

Alright, so I set up the required dbs using psql. Now, when I run the make test command, it looks like the tables are created but it eventually errors out with the following
env/bin/honcho run -e defaults.env,tests/test.env,tests/local.env env/bin/py.test -vv --cov gratipay ./tests/ /bin/sh: env/bin/py.test: No such file or directory make: *** [test] Error 127
And on running the make run command, I get the following error message.
from cryptography.fernet import Fernet, MultiFernet ImportError: No module named cryptography.fernet [2017-08-11 23:44:08 +0530] [30588] [INFO] Worker exiting (pid: 30588) [2017-08-11 23:44:08 +0530] [30585] [INFO] Shutting down: Master [2017-08-11 23:44:08 +0530] [30585] [INFO] Reason: Worker failed to boot. make: *** [run] Error 3
Do I need to manually install the crytography.fernet module using pip? Why is it not installed as part of the requirements.txt file?

Did you make env?

Did you make env?

You shouldn't need to as make test includes env in its dependency chain, but if py.test and cryptography aren't installed then a make clean env could be what you need to get back on track.

Running make clean env gives me an error with the cryptography module
Running setup.py install for cryptography ... error
This then prints out a whole stack trace of errors, resulting in
fatal error: too many errors emitted, stopping now [-ferror-limit=]     20 errors generated.     error: command 'cc' failed with exit status 1
Right now, it just seems to be the cryptography module and this is one of the errors from the trace
build/temp.macosx-10.10-intel-2.7/_openssl.c:578:30: error: expected function body after function declarator     typedef LHASH_OF(CONF_VALUE) Cryptography_LHASH_OF_CONF_VALUE;

From a few Googles, I'm wondering what version of pip you're running.

Hey, sorry it took me so long to fix this. I was just having massive troubles with getting the project up and running.
https://github.com/gratipay/gratipay.com/pull/4576
The fix should work. Thanks again for letting me contribute.

:+1: Thanks @redixhumayun.
The fix looks good, a couple of linter errors left and we're good to go.

Awesome work, @redixhumayun! If there's one thing we could change about our install docs or onboarding process, what would it be?

@whit537 The biggest issue I had with was resolving dependencies.
Specifically, getting the cryptography module to work. The link @mattbk shared helped solve the issue. I had another issue with the mock module (link to SO question), where the mock module had a dependency on another module, which had versioning issues.
I'm guessing this is bound to happen with such a massive project, but maybe documenting common errors and fixes with module dependencies would help?

documenting common errors and fixes with module dependencies would help?

You're part of the solution! Now this problem is searchable in our issue queue.

Re: cryptography ... was it C dependencies or Python dependencies that gave the problem? I'd expect C, and therefore a bit out of our scope. :-/
For mock I'd expect Python deps were the problem. If that sounds plausible to you then we should review network-less installation to see if we have a leak in vendor/ ...  our aim is to bundle all Python deps at fixed versions in vendor/ precisely to avoid dependency h*ck.


Add .node-version file to support automatic version switching

It is supported by avn and nodenv. When you use these tools the Node version is switched automatically.
As I work on projects with older Node versions a lot it is nice that the version is switched automatically to the one that Este uses when I work on it or when I start a new project.

Thank you!


support: Return json_error if the POST request is invalid

@timabbott Updated to make use of json_error.
The endpoint is not a json endpoint but using json_error should be fine here since only the support staff see that error. Also, it's an error that will happen only if the support form tries to make changes to two things. And that would happen only if the browser do something really weird or the frontend HTML form code is written incorrectly. The support forms are written in such a way that only one property is updated at a time.

Tests failing in CI are unrelated to the PR.

Merged, thanks @hackerkid!


Moving the mouse even while out of the editor window causes ~6% usage for the editor process

It should be further investigated if this can be reduced. This is especially strange because we do not do anything with mouse input at the moment.

Editor is no longer being worked on, and has been removed from the repo. Closing.


IoR table

@devshgraphicsprogramming I have sent you nice website that might solve our troubles with
chemical compounds etc, because in majority of cases those chemicals are placed in such a part of "Handbook Of Optical Constants of Solids" that access to them is paid. Check out Discord please.

@devshgraphicsprogramming most of troubles solved, obtained 3 toms of Plaik's book, but despite it I can't find anything about "d-C" :D

d-C is cubic diamond


[FLINK-17116] [connectors / elasticsearch] support UsernamePasswordCredentials for elasticsearch sink

What is the purpose of the change
(For example: This pull request makes task deployment go through the blob server, rather than through RPC. That way we avoid re-transferring them on each deployment (during recovery).)
Brief change log
(for example:)

The TaskInfo is stored in the blob store on job creation time as a persistent artifact
Deployments RPC transmits only the blob storage reference
TaskManagers retrieve the TaskInfo from the blob cache

Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (100MB)
Extended integration test for recovery after master (JobManager) failure
Added test that validates that TaskInfo is transferred only once across recoveries
Manually verified the change by running a 4 node cluser with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Thanks a lot for your contribution! It seems that this pull request is referring to a closed JIRA ticket.
There's a ticket (https://issues.apache.org/jira/browse/FLINK-16788) which references to this PR https://github.com/apache/flink/pull/11822.
@wuchong can you clarify what to do here?

Sorry, I didn't notice this pull request before. There is already a pull request (#11822) for this feature which is a good shape to be merged. So I will close this then. Thanks a lot for the contribution again @yuchuanchen !


chore(deps): react 19 stable

#151  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


fix: FluentE Group doesn't work the first menu element.

🐛 Bug Report
Hello, it seems that an old problem has happened again with FluentNavGroup, the first element in the list is not working.
💻 Repro or Code Sample

<FluentNavMenu Width="320" CustomToggle="true">
    <FluentNavLink Icon="@(new Icons.Regular.Size24.Home())">Inicio</FluentNavLink>

    <FluentNavGroup Title="Board" Icon="@(new Icons.Regular.Size24.UsbPlug())" >
        <FluentNavLink Icon="@(new Icons.Regular.Size24.Info())">Informação</FluentNavLink>
        <FluentNavLink Icon="@(new Icons.Regular.Size24.CloudSync())">Centro Atualização</FluentNavLink>
    </FluentNavGroup>

    <FluentNavGroup Title="Manager" Icon="@(new Icons.Regular.Size24.Apps())">
        <FluentNavLink Icon="@(new Icons.Regular.Size24.TicketDiagonal())">Eventos</FluentNavLink>
        <FluentNavLink Icon="@(new Icons.Regular.Size24.DrinkMargarita())">Bebidas</FluentNavLink>
        <FluentNavLink Icon="@(new Icons.Regular.Size24.DrinkToGo())">Doses</FluentNavLink>
    </FluentNavGroup>

    <FluentNavGroup Title="PDV" Icon="@(new Icons.Regular.Size24.DesktopToolbox())">
        <FluentNavLink Icon="@(new Icons.Regular.Size24.Desktop())">Terminal</FluentNavLink>
        <FluentNavLink Icon="@(new Icons.Regular.Size24.Settings())">Configuração</FluentNavLink>
    </FluentNavGroup>
</FluentNavMenu>

🤔 Expected Behavior
The expected behavior is that all FluentNavGroup dropdowns
😯 Current Behavior

💁 Possible Solution
I think it's a javascript problem.
🌍 Your Environment

Blazor MUAI
.Net8.0

This has been reported already and ids fixed with #2293. Will be in next release (soon)


Changes fetch-depth in test workflow to 0

Problem
Danger fails on PRs from forks.
Solution
According to https://github.com/danger/danger/issues/1103, setting the fetch-depth to 0, i.e. fetching all branches and tags, should fix this.

Will fix the PR run in #67.


[Request] /closerequest for users if CloseStaffOnly is true

When closeStaffOnly is set to true, it could be an excellent idea that users can request to have the ticket closed by Staff.
For example, by using /closerequest, the bot will send a message to the channel the user wants the ticket channel to be closed.

Hey, could you provide more explanation about this feature request? For example:

What do you think such an embed for a close request should look like?
Should it ping the support roles of the ticket category so staff can be notified about this close request?

Other than that I think the embed will probably contain a close button, which staff can use to close the ticket.

What do you think such an embed for a close request should look like?
For example, it could be:

USERNAME has requested to have his ticket closed.

Should it ping the support roles of the ticket category so staff can be notified about this close request?
It should be optional whether staff should be tagged or not.

Other than that I think the embed will probably contain a close button, which staff can use to close the ticket.
Correct, so staff don't have to scroll to the top or from the pin. There can often be a lot of messages.

Thank you for your suggestion, this is now added in the latest commit. 3a0c578


"Queue trigger, look up ID from JSON" Example is invalid python

The "Queue trigger, look up ID from JSON" references invalid variables, and I can't get cosmos db input to bind to the message payload. Could this example be updated so that it works?

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

ID: f9e3fe74-1d65-41eb-6a5e-0595e6d06029
Version Independent ID: 8933389b-f4c0-acbd-afe3-86f18738c1f9
Content: Azure Cosmos DB input binding for Functions 2.x and higher
Content Source: articles/azure-functions/functions-bindings-cosmosdb-v2-input.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@merrickheley
Thanks for your feedback! We will investigate and update as appropriate.


[BUG] Log explorer chart shows incorrect data

What is the bug?
There are a few issues with the Log Explorers visualization in the event tab:

The log Explorer chart and the table below show different data.
Actions on the chart such as selecting a time range do not update the time filter (It does on discover and on dashboards)

https://github.com/opensearch-project/dashboards-observability/assets/20453492/840e48e6-87fe-4eda-a895-a02678de599a

The default graph shown also does not make a lot of sense in auto since it looks like there is missing data between the dates where the bars have a gap. See below screenshots

The time frequency selector is incorrect after page navigation. To reproduce, change the frequency to a minute and then navigate away from the page and navigate back to the page. The graph resets but the picker does not.

3-87ed-8b27d606168e)

How can one reproduce the bug?
Steps to reproduce the behavior:

Go to /app/observability-logs#/explorer
Selecta. time range on the graph
Scroll down to '....'
See error

What is the expected behavior?
A clear and concise description of what you expected to happen.
What is your host/environment?

OS: [e.g. iOS]
Version [e.g. 22]
Plugins

Do you have any screenshots?
Do you have any additional context?
Add any other context about the problem.

Thanks for raising the issues @ashwin-pc ! I will be assigning this to @mengweieric and Sumukh Swamy @sumukhswamy to follow up on this


fix(versions): update Activiti/activiti-cloud-full-chart-security versions

UpdateBot pushed helm dependency: activiti-cloud-full-example to: 7.1.422

UpdateBot commands:
updatebot push-version --kind helm activiti-cloud-full-example 7.1.422


I just got python3-pip and done pip3 install thefuck
I got errors on install which i give you in these link (second is the debug file)
http://paste.ubuntu.com/13282680/
http://paste.ubuntu.com/13282685/
Running thefuck gives
Traceback (most recent call last):
  File "/usr/local/bin/thefuck", line 7, in <module>
from thefuck.main import main
  File "/usr/local/lib/python3.5/dist-packages/thefuck/main.py", line 6, in <module>
from . import logs, types, shells
  File "/usr/local/lib/python3.5/dist-packages/thefuck/types.py", line 6, in <module>
from psutil import Process, TimeoutExpired
ImportError: No module named 'psutil'

It was missing psutil and decorator, which i installed.
And finally i got this thefuck error
http://paste.ubuntu.com/13282783/
Sorry i think this may be bad news, or hopefully i'm missing another dependency ?

 It seems it is not able to install psutils when some dependencies (here probably python3-dev) are not met but it fails to report that and fails ungracefully. On Ubuntu you could install python3-psutil before you install The Fuck.

Well indeed i removed thefuck and reinstall without errors.
However i still got this bug (same as my last link on previous comment):
http://paste.ubuntu.com/13282990/
I just tried getting thefuck from repo, and having eval "$(thefuck --alias)" with repo version 2.5.6-1, running with python2 made a fork bomb - just so you know -
So i ran wget -O - https://raw.githubusercontent.com/nvbn/thefuck/master/install.sh | sh - && $0 as in Readme and back from start point of course.
So ultimately again, using pip3, i got this error http://paste.ubuntu.com/13282990/

Do you have a ~/.cache/thefuck file?

Indeed i tried deleting it and still same issue
here it is
https://www.freethepepper.com/owncloud/index.php/s/F6XQd9xperIt1Qw

Nice :smile:
So that last problem was because Python 2 and Python 3 shelves are not compatible (how convenient) and your file was a Python 2 shelf. I'll do something about that.

@mcarton wrote:

That's yet another problem with Unicode and Python 2.


Report the use of deprecated stuff

golint should be able to report cases user is depending on deprecated things. For the case below, it should be able to output "Deprecated: Use Client or Transport in package net/http instead".
$ cat main.go
package main

import (
    "net/http/httputil"
)

func main() {
    httputil.NewClientConn(nil, nil)
}

For reference: golang/go#10909

This change will also encourage the use of the same deprecation message formatting in the third party packages.

We want golint to be able to report third party library deprecations as well. I don't think (1) is something we should go with. The ecosystem wants to be able to break APIs but our tools don't do a good job helping the authors communicating these breakages.
I tried to prototype (2) a while ago by modifying the loader package and I personally didn't like the solution, because all of a sudden package loading has to deal with loading dependencies and handling them. But to be fair, I cannot think of any perfect solution right now.

A couple of thoughts:

Is golint really the right place for this check? As I understand it, golint is primarily about style. Is using deprecated identifiers a style issue?
staticcheck includes a check for use of deprecated identifiers, so feel free to copy from it. Be warned, though, it depends on some parts of my framework that you'd have to replace.
I'd also be concerned with forcing golint to work on entire packages, and type-check all dependencies (which will make it significantly slower) for a single check.
@rakyll, what modifications to the loader package did you feel were necessary? go/loader takes care of dependencies, parsing and type-checking for you. It would be trivial to use it to load a package, and its dependencies, from source. Though of course see point 3.

I'd also be concerned with forcing golint to work on entire packages, and type-check all dependencies (which will make it significantly slower) for a single check.

Note that using the loader doesn’t force us to work on entire packages. Via the CreatePkgs field in loader.Config, we can specify an individual file in what the loader calls an ad-hoc package.
Also note that we only load and type-check direct dependencies, not all dependencies.

You can create ad-hoc packages, but if you depend on them to type check without error (which you might not), then the ad-hoc package needs to contain all files of the package.
In order to type-check direct dependencies successfully (which, again, may not be necessary just for the sake of parsing deprecation comments), you need to check dependencies recursively, or build your own version of go/loader that only parses direct dependencies from source, and uses object files for transitive dependencies (which has its own issues.)

Though I do think you want to load transitive dependencies, to be able to flag deprecated uses in code like this:
import "A"

func fn() {
  A.Fn().Foo()`
}

where A.Fn returns a type from package B (or C or ...) and where Foo is deprecated.

Fair point.
The remaining question is about whether the slow-down is acceptable in golint. How do we make that decision?

I sent PR #318 so that we have some actual code to discuss this over (I find that always helps).
Regarding the slow-down, here are numbers on my workstation of running go test github.com/golang/lint:
before:
ok  	github.com/golang/lint	0.130s

after:
ok  	github.com/golang/lint	3.053s

Thoughts?

My opinion is that this check, in this tool, isn't worth it.  It cannot operate on invalid input anymore (a clear change in behaviour). And it isn't a style issue and hence out of scope.
The following advice is clearly biased, but I'd recommend people use my staticcheck if they want to check for deprecated identifiers. There's no need to burden golint with this check.

Thanks for the issue.
This appears to be out of scope and so is being closed. If you feel this is in error please feel free to re-open.
Please note this is not the forum to discuss edits to CodeReviewComments. If you wish to propose changes to it please send a mail to golang-nuts.

I have no opinion as to whether this is considered "out of scope" of the lint tool, but just wanted to note that if we consider this out-of-scope, then so should #302, which is really just one special-case application of this more general issue.
I feel like use of deprecated is halfway between a style issue and a correctness one. I'll happily use statticcheck.

Even if this is out of scope for the lint tool, is there any other suggestion currently being discussed to expose deprecation information?
I see that the proposal to hide deprecated items from godoc has been accepted, but will the go toolchain ever warn users of those APIs? If not, should this discussion be moved to a different issue somewhere else?

@empijei, see staticcheck.
In regards to godoc, I've been blocked on trying to unify the front-ends for all the different godoc tools that exist.


Jumpscale Testing

This storycard covers the most important topics to be tested in jumpscale

Installations

in system installation
docker installation
need to find a service that allows us to automate tests on OSX

Security Layer

NACL and configmanager

with sshkey
without sshkey

functionality

should be secure, meaning data that is encrypted should be verified to be encrypted unless being retrieved through the nacl module
should be able to set new config
should be able to get config
should be able to delete config
should be able to recover config if provided with seed
should be able to export data
should be able to import data

Core

baseclasses (see:https://github.com/threefoldtech/jumpscaleX/blob/development_jumpscale/docs/Internals/baseclasses/readme.md)

Data Layer

schemas

already we have some tests, but need to be extended with more scenarios

BCDB

already we have some tests, but need to be extended with more scenarios
performance tests

SALs

behavioral testing
start with:

fs
rsync
process

Tools (not high priority)

behavioral/unit testing

TFChain

more tests for reservation flow

Clients

some will be mocked, some not.
start with:

Servers

some will be mocked, some not.
start with:

digitalocean
github
ssh
sshkey
zdb
zero_hub
zero_os

Servers:

start with:

tmux
corex
startcmd
zdb

Builders

we already have the tests

DigitalMe

server rack
Actors

Behavioral. Scenario could be:

create a test actor with schema in and schema out
load test actor
use redis protocl to verify

jsclient (see: https://github.com/threefoldtech/digitalmeX/blob/development/docs/webserver/websocket-gedis.md)
gundbjs integration

Architecture to run tests:

Trigger on PR is exactly the same but without the builder tests.


[5.5] Fix mapping eagerly loaded multiple related records in eloquent

The pull request does not include any breaking changes. It does not introduce any new features but simply converts the dictionary key to lowercase (if the foreign key values are varchars instead of integers).
In cases when the relationships define foreign keys as strings and the values of the foreign keys differ in terms of uppercase/lowercase then the eagerly loaded multiple records would fail to be mapped/attached to the parent record.
The dictionary technique of mapping the related data is transitional and therefore its mapping keys do not affect anyhow the DB records at the end.
Consider the following example:
Items table

uuid
name

ABC
First

bbb
Second

ccc
Third

Labels table

id
name

1
label 1

2
label 2

3
label 3

items_labels table

item_uuid
label_id

ABC
1

abc
2

bbb
3

Item::with('labels')->find('ABC');
MySQL collation by default is case-insensitive and the SQL statements would return both label 1 and label 2 but prior to the fix only label 1 would be mapped and attached (via the dictionary technique) to the item record.
After the fix I am proposing, both label 1 and label 2 would be attached to the item record.
For case sensitive DB collations (like SQLite by default or MySQL _cs collations) the fix would not matter but would not break anything either.
@taylorotwell, I included an integration test and had to define the SQLite table columns via raw statements. I could not find a better way to define the collation of the columns via the schema builder.

MySQL is case insensitive
For case sensitive DBs (like SQLite by default)

You've probably misunderstood the cause. The case sensitivity of string comparisons depends on the columns string collation, and these differ based on the database. You can use a case sensitive string collation (latin1_general_cs) or a case insensitive string collation (latin1_general_ci, utf8mb4_general_ci). There's also binary collations (latin1_bin, utf8mb4_bin) where the comparison is done by the actual binary values stored in the database, instead of comparing the string content. This touches the subject of unicode normalization and the fact that there are several ways (and thus byte sequences) to write the same character in a string.
The mentioned collation names are just a few of hundreds available in mysql. You can find these with SHOW COLLATION; and I wouldn't be surprised if the available collations differ between installations. SQLite only have three "collations", or more like three comparison modes, where all three uses byte sequence (binary) comparison of the strings, and one provides case insensitivity of ascii characters.
We cannot assume that the comparison should be case insensitive, and that the key A is the same as a. This use-case is based on the fact that the actual value is stored in hexadecimal representation. Would it perhaps be better handled by adding support for hexadecimal keys (or uuids) instead of assuming all strings are case insensitive?

I understand what the cause is and that MySQL has multiple case-sensitive and case-insensitive collations. I just gave an example that MySQL default collation is _ci ('latin1_swedish_ci' is not mistaken) and that most MySQL DB installations, in general, are case-insensitive compared to SQLite where is case-sensitive by default unless you specify COLLATE NOCASE for the columns.
What I am proposing as a pull request is that we make the code case insensitive and allow the DB layer (DB administrator) decides if the business model should be case sensitive or not.

There isn't any likelihood of me changing this behavior on a LTS release.

There isn't any likelihood of me changing this behavior on a LTS release.

@taylorotwell, the reason I submitted the PR to 5.5 (LTS) is that I consider it as a bug fix since it gives unexpected behavior on case-insensitive DB collations and based on the contributions guide it should be sent to the latest stable or LTS branch.
Do you think this is more appropriate to be considered as a new feature?

I created a package addressing the issue above.
https://github.com/TishoTM/eloquent-ci-relations


Recipe for Java

Recipe for documentation tool in Java.
This needs to output api output under /api/java under the project folder.

this is blocked by data retrieval's decision


extracting arrays

queried elements may contain children with the same selector. we should allow people to define some fields as arrays.
example:

Related commit: https://github.com/aykutkardas/muninn/commit/a836eb7b6a927845dd711ac9291b45901352ddcf


Should not use deep-extend

I am getting this error since Meteor 1.5 no longer automatically makes the Buffer polyfill available on the client.
I was able to resolve it by adding this code:
global.Buffer = function() {}
global.Buffer.isBuffer = () => false

But it seems deep-extend is not designed to be used on the client side, see this issue.
Thank you!

Thanks, we will need to find a replacement


feat: apply wasm opts

Description
Closes: https://github.com/line/lfb-sdk/issues/308
Add wasm opts to enable telemetry.
Motivation and context

https://github.com/CosmWasm/wasmd/blob/93e2e669402dd96b99f223bc6176abef6e794455/cmd/wasmd/root.go#L204
The telemetry metrics is included :1317(API Server metrics).
e.g) recorded instantiate
{"Name":"wasm.contract.instantiate","Count":1,"Rate":2.222800064086914,"Sum":22.22800064086914,"Min":22.22800064086914,"Max":22.22800064086914,"Mean":22.22800064086914,"Stddev":0,"Labels":{}}]}
How has this been tested?

Screenshots (if appropriate):
Checklist:

[ ] I followed the contributing guidelines.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.

Closes: line/lfb-sdk#308

I think this PR is a part of this issue and does not directly close the issue. Is it right?

Closes: line/lfb-sdk#308

I think this PR is a part of this issue and does not directly close the issue. Is it right?

I think This PR resolve the entire issue.
Instantiate time includes compilation time, and Execute time includes execution time.
So it looks like we don't need to add additional metrics.
Are there any more metrics that need to be added?

please note The metric measurement code using telemetry is already in wasm keeper.
https://github.com/line/lfb-sdk/blob/7214594363f82d35245b7a0ea6d98397dfa3a78f/x/wasm/keeper/keeper.go#L236
https://github.com/line/lfb-sdk/blob/7214594363f82d35245b7a0ea6d98397dfa3a78f/x/wasm/keeper/keeper.go#L334
https://github.com/line/lfb-sdk/blob/7214594363f82d35245b7a0ea6d98397dfa3a78f/x/wasm/keeper/keeper.go#L383
https://github.com/line/lfb-sdk/blob/7214594363f82d35245b7a0ea6d98397dfa3a78f/x/wasm/keeper/keeper.go#L462
https://github.com/line/lfb-sdk/blob/7214594363f82d35245b7a0ea6d98397dfa3a78f/x/wasm/keeper/keeper.go#L639
https://github.com/line/lfb-sdk/blob/7214594363f82d35245b7a0ea6d98397dfa3a78f/x/wasm/keeper/keeper.go#L663

Ah, Sorry. I missed our version of wasm has the metric feature. Thanks.

Me too, I didn't even know it was added. thanks for the review!


mx.symbol.Scale not found

I installed MXNET using instructions from http://mxnet.io/get_started/osx_setup.html
with  git clone --recursive https://github.com/dmlc/mxnet
then
I used git clone --recursive https://github.com/zhreshold/mxnet-ssd.git
I still have the same error  when I try to excute demo.py
AttributeError: 'module' object has no attribute 'Scale'
I even tried
1-git clone --recursive https://github.com/zhreshold/mxnet.git  and
2-edit  the file tools/find_mxnet  as mentioned in issue 11
but problem is not resolved
Thanks

You have misunderstand the structure of this project.

git clone --recursive zhreshold/mxnet-ssd.git
cd mxnet-ssd/mxnet
regard this mxnet as the official one. follow the official instruction. Thus you will enable some extra layers, such as Scale and MultiboxPrior...

Thanks for clarification, now I do not have this error any more

@Walid-Ahmed, @zhreshold  could you please elaborate more on this? Could you please give more details about how to install the new layers using the new mxnet? I am not having any luck. Thanks

@Walid-Ahmed, @zhreshold .  I was still using the original mxnet installation. Thanks! Solved!


[Snyk] Security upgrade node from 20.1-alpine3.17 to 20.9-alpine3.17

This PR was automatically created by Snyk using the credentials of a real user.Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Changes included in this PR

Dockerfile

We recommend upgrading to node:20.9-alpine3.17, as this image has only 1 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:

Severity
Priority Score / 1000
Issue
Exploit Maturity

514
Out-of-bounds Read SNYK-ALPINE317-OPENSSL-5438697
No Known Exploit

514
Allocation of Resources Without Limits or Throttling SNYK-ALPINE317-OPENSSL-5661570
No Known Exploit

514
Excessive Iteration SNYK-ALPINE317-OPENSSL-5821141
No Known Exploit

614
CVE-2023-5363 SNYK-ALPINE317-OPENSSL-6032385
No Known Exploit

614
CVE-2023-5363 SNYK-ALPINE317-OPENSSL-6032385
No Known Exploit

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Allocation of Resources Without Limits or Throttling

we will not update to specific version


Improve the UI

The UI is simple and the color combinations are not soothing to the eye.
I would like to change the color combination to a single color. For example: Shades of blue and a different shade for some other important options. This will maintain the uniformity of the project.
I have worked on same type of projects making clones of website. Please do assign me this one. I am a participant of GSSOC'21.

Somebody assign me to this issue, I have a figma design ready to tackle and therefore I'd also like to work on it. Here are the images of the UI that I designed, @Suvojit-roy let me know if you want to make any changes to the UI since I am starting to work on it.

Yeah i think that you should go for some other color combination.This is a high contrast design that makes it look funky rather than something official.

Yeah but if you consider Twitter's or Instagram's dark theme, keeping a color palette, in contrast, makes it even more attractive. I tried to follow their design rules because firstly they were not only simple and minimal but also easy to eyes even with the contrast. What do you think?

Yeah everything looks good just changing the neon shade a little will help it

Can you make the changes you'd like? Check your email I have sent you an invite from figma.

I didnt receive the mail .Please do resend me again or send it here.

This issue should close #64

hey @Jaagrav  you can send me that link and we can work on this together

The new UI is available at: https://recess-n3jc6ggz3-jaagrav.vercel.app/home
Still working on it... If you can, please design the 404 and under dev pages,
Thank you.

Loved the Implementation @Jaagrav


UNIQUE constraint failure building example projection.

When submitting a OpenAccountForNewCustomer command, resulting in an CustomerAcquired event the customer projection is failing with and SQL error UNIQUE constraint failed: customer.id, which seems to correct itself immediately after.
I think there's likely an off-by-one error with the eventstream-offset/projection-resource mapping.
engine  hosting @bank application, identity key is 22028264-0bca-43e1-8d9d-cd094efb10b7
engine  [queue@bank] loading up to 40 message(s)
engine  [queue@bank] loaded 0 message(s) from store (exhaustive: yes)
engine  [stream@bank -> account-list@bank] consuming 'events.AccountOpened' events
engine  [stream@bank -> account-list@bank] consuming 'events.AccountCredited' events
engine  [stream@bank -> account-list@bank] consuming 'events.AccountDebited' events
engine  [stream@bank -> customer-list@bank] consuming 'events.CustomerAcquired' events
engine  [stream@bank -> account-list@bank] consuming 3 event type(s), beginning at offset 0
engine  [stream@bank -> customer-list@bank] consuming 1 event type(s), beginning at offset 0
engine  [queue@bank] bbf4b194-3fc1-4ec8-b9c6-a69273a77bd9 requested tracking successfully
engine  [queue@bank] bbf4b194-3fc1-4ec8-b9c6-a69273a77bd9 is now tracked (pending: 1, tracked: 1/40)
engine  [queue@bank] bbf4b194-3fc1-4ec8-b9c6-a69273a77bd9 is ready to be handled immediately
engine  [queue@bank] bbf4b194-3fc1-4ec8-b9c6-a69273a77bd9 was sent to a consumer
engine  [queue@bank] not loading messages, 1 message(s) already tracked
@bank  = bbf4b194  ∵ bbf4b194  ⋲ bbf4b194  ▼    OpenAccountForNewCustomer ● {99f3e91e-9340-4403-803a-6f783b77b58d James 2970f108-411d-4409-ac98-f55e666b2dab Savings}
@bank  record added: 99f3e91e-9340-4403-803a-6f783b77b58d (0xc0002ff180)
@bank  = 839721f3  ∵ bbf4b194  ⋲ bbf4b194  ▲    CustomerAcquired ● {99f3e91e-9340-4403-803a-6f783b77b58d James 2970f108-411d-4409-ac98-f55e666b2dab Savings}
engine  [queue@bank] bbf4b194-3fc1-4ec8-b9c6-a69273a77bd9 is no longer tracked, handled successfully (pending: 0, tracked: 0/40)
engine  [queue@bank] not loading messages (exhaustive: yes)
engine  [stream@bank -> customer-list@bank] delaying next attempt for 77.712049ms: UNIQUE constraint failed: customer.id
engine  [stream@bank -> customer-list@bank] consuming 'events.CustomerAcquired' events
engine  [stream@bank -> customer-list@bank] consuming 1 event type(s), beginning at offset 1

See #197 for details of the problem and its fix.

This issue is still present when an event-type filter causes the message AT the offset specified in the request to be skipped.


Prover-function based fast witgen

We would like to have prover-function based fast witgen. This issue is not about auto-generating prover functions [-> #2066], it assumes correct prover functions are provided by the user. We can roughly break it down into the following steps:

allow access (read and write) to all rows in a block of a block machine
potentially modify the whole pattern of how new values are provided in the prover function evaluation process
implement the required built-in functions
implement missing pieces for JIT if needed
find a mechanism to directly return the result of a query to a sub-machine, so that filling the actual cells in the submachines can be done in a separate thread

Related explorative PR with some numbers: #2028

We implemented this without going through pil. We might revisit this at a later point in time, first auto-generating prover functions and then compiling pil to rust.


Add TODOs Badge

Hi there! I wanted to propose adding the following badge to the README to indicate how many // TODO comments are in this codebase:

The badge links to tickgit.com which is a free service that indexes and displays TODO comments in public github repos. It can help surface latent work and be a way for contributors to find areas of code to improve, that might not be otherwise documented.
The markdown is:
[![TODOs](https://img.shields.io/endpoint?url=https://api.tickgit.com/badge?repo=github.com/buildondata/deno-postgres)](https://www.tickgit.com/browse?repo=github.com/buildondata/deno-postgres)

Thanks for considering, feel free to close this issue if it's not appropriate or you prefer not to!

I think will close this for now, but may turn this on in the future.
Interesting project!


PR #2500 Followup

[ ] https://github.com/openshift/odo/pull/2500#discussion_r372890591 let's use the fake package here and write the stuff in memory instead of the disk. That will speed up the testing.
[ ] https://github.com/openshift/odo/pull/2500#discussion_r372891177 why not use the Fs Filesystem which is part of the DevfileCtx? What will help us with unit tests using the fake system.
[ ] https://github.com/openshift/odo/pull/2500#discussion_r372891839 We can pass the fake filesystem here in DevfileCtx
[ ]  https://github.com/openshift/odo/pull/2500#discussion_r372895747 since the description says run command not present, should this be build app?
[ ] https://github.com/openshift/odo/pull/2500#discussion_r372906855 can we convert these tests to the tabular format we currently use in odo?

/assign @kanchwala-yusuf
/kind devfile
/label state/Ready

/kind cleanup
/area devfile

/triage ready


Feature request: Example to use with SQFLITE file

Hi, I preload an SQL database file from the root bundle and load into my app. Could you provide directions on how I would redirect this path into secure_storage?
Here is example code of how it loads today:
var databasesPath = await getDatabasesPath();
var path = join(databasesPath, "newfile.db");
print(path);
ByteData data = await rootBundle.load(join("assets", "preload.db"));
List bytes =
data.buffer.asUint8List(data.offsetInBytes, data.lengthInBytes);
await new File(path).writeAsBytes(bytes);
Thank you!

Hi @bremington
I do not get the question, can you please elaborate?

Hi German,
My app is using a database file using SQFLITE. I create a db file to store 6 SQL tables, and import a pre existing db file to load from the root bundle.
I was hoping to encrypt this file with your solution. In looking at the few examples it appears this is more to secure key value pairs as opposed to a single file (i.e finance.db which is my file)?
If I can encrypt this file how would I do so:
This is my current code to create the finance.db file:
assert(version > 0, "Version number must be greater than one!");
var databasesPath = await getDatabasesPath();
var path = join(databasesPath, "finance.db");
print(path);
ByteData data = await rootBundle.load(join("assets", "seed.db"));
List bytes =
data.buffer.asUint8List(data.offsetInBytes, data.lengthInBytes);
await new File(path).writeAsBytes(bytes);
So would I replace the databasePath above with final storage = new FlutterSecureStorage();??
I am trying to understand how to use this secure area to place my db file. Then I assume I can use my normal SQL commands to query and update the db file, which would be located in this encrypted location?
Thank you,
Brian Remington

On Jul 26, 2019, at 10:41 PM, German Saprykin<EMAIL_ADDRESS>wrote:
Hi @bremington https://github.com/bremington
I do not get the question, can you please elaborate?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/mogol/flutter_secure_storage/issues/64?email_source=notifications&email_token=AISMZJTKYN7XCHQYMKYI6MLQBOYXBA5CNFSM4IFTDOM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD26CAGA#issuecomment-515645464, or mute the thread https://github.com/notifications/unsubscribe-auth/AISMZJT7D2Q2LMJKV7PA42DQBOYXBANCNFSM4IFTDOMQ.

The plugin supports only key-value string pairs. It doesn't support your use case.
Please check https://pub.dev/packages/flutter_sqlcipher for encrypted SQLite

German, thank you.
Yes I have looked at flutter_sqlcipher, but it is only for Android, and I need a solution that also supports iOS.

On Jul 27, 2019, at 11:13 AM, German Saprykin<EMAIL_ADDRESS>wrote:
The plugin supports only key-value string pairs. It doesn't support your use case.
Please check https://pub.dev/packages/flutter_sqlcipher https://pub.dev/packages/flutter_sqlcipher for encrypted SQLite
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/mogol/flutter_secure_storage/issues/64?email_source=notifications&email_token=AISMZJRU5M37G4FCRARUQGTQBRQ3PA5CNFSM4IFTDOM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD26NHMQ#issuecomment-515691442, or mute the thread https://github.com/notifications/unsubscribe-auth/AISMZJXYNVI63XCQN6OZYMLQBRQ3PANCNFSM4IFTDOMQ.


"Popcorn-like"

@Dr-Horv pls add description

What is there to like? Re-open if and when this issue becomes applicable.


dyld: lazy symbol binding failed

I use OSX10.12, I try to use OpenCV in tensorflow, I use the first method which is mentioned here.
I build my code successfully but there are some questions as following when I execute it:
Referenced from: /Users/philokey/Practice/github/tensorflow/./bazel-bin/tensorflow/examples/test_cv/test_cv
Expected in: flat namespace```

The build file is as following:

cc_binary(
name = "test_cv",
srcs = [
"test_cv.cc",
],
deps = [
"@opencv//:opencv",
],
)
How can I sovle this problem?
By the way, the question is also asked in [stackoverflow](http://stackoverflow.com/questions/40259156/osx-tensorflow-opencv-symbol-not-found-expected-in-flat-namespace)

I solved this problem.
I should use .dylib instead of .so


Folia Support?

Can you add support for folia?

I'll check how can I do that, because the way folia scheduling work is very different and I'll need to extend the API or create a custom API for folia.


Add stand alone MetPy Introduction

Mostly the ideas that were in the primer, but with exercises and a pretty chart. Probably not going to take the 40 mins we have slated currently.

No test failures are related - remote data issues with GOES. Have a look at the notebook and should be good to merge.


Fix typo in health-checks doc

The healthz endpoint is documented above and presumably this word is referring to it.

/lgtm

/assign @kbhawkey


Error executing command 'x': document is not defined

Am trying to use docx-templater in supabase edge function (Deno). But I dont seem to be able to get the library to work?
Error: Error executing command 'quote_number': document is not defined
at runUserJsAndGetRaw (https://unpkg.com/docx-templates@4.11.1/lib/browser.js:26:224)
at processCmd (https://unpkg.com/docx-templates@4.11.1/lib/browser.js:26:6387)
at processText (https://unpkg.com/docx-templates@4.11.1/lib/browser.js:26:5561)
at walkTemplate (https://unpkg.com/docx-templates@4.11.1/lib/browser.js:26:4592)
The template is a docx file, with simple direct tags:
{quote_number}, {quote_name}.
There is no Query, EXEC or INIT anywhere in the file. As I prepare the data before hand and then pass it to createReport.
const quote_data = await req.json();
let template:Blob = data;
const buffer = await createReport({
  template,
  quote_data,
  cmdDelimiter:  ['{','}'],
  noSandBox: true
});

Attached is the template and the dummay data used for testing.
oa_quote_template.1.0.docx
dummy_data.txt
Other information:

This is the first time using docx-templates on Supabase Edge Functions.
We are using the Free cloud hosted supabase dev setup to perform the test. (Its not a local development environment)

any help is always appreciated.
Cheers

createReport expects an arguments object with the data property. You're providing an object with the quote_data property, which docx-templates does not use and is likely a mistake.
You probably want to write:
const quote_data = await req.json();
let template:Blob = data;
const buffer = await createReport({
  template,
  data: quote_data,
  cmdDelimiter:  ['{','}'],
  noSandBox: true
});

Lmk if this does not fix your issue.
Recommend adding strict tsconfig and eslint rules so you can rely on intellisense more to avoid stuff like this.

Sorry, I am struggling to get this working. I am not very experienced with Typescript.
Have been trying different combinations of the following:
"docx-templates": "https://unpkg.com/docx-templates/lib/browser.js",
const buffer = await createReport({
template,
data: {
quote_number: '1234',
quote_date: '2023-04-18',
},
cmdDelimiter:  ['{','}']
});
and still I get same result.
"Error executing command 'quote_number': document is not defined"

@rhys-phelps-labs Eyeballing your code, I think the vm polyfill does not behave as expected in your deno environment. I think it expects the document global to be available, like it would be in a browser environment.
You can try disabling sandbox mode by setting noSandbox: true. This will run the code of each command in a simple eval call rather than a vm sandbox.
You should only disable the sandbox if you understand the security implications. See https://github.com/guigrpa/docx-templates#performance--security. If you disable sandboxing, make sure you trust your template; think of your template as JS code (it actually is JS code). Don't let users upload template.
Let me know if this solves your problem.

Begging your forgiveness. I spelt noSandBox instead of noSandbox.
Thankyou, your library is a life saver.


FeeAsset is Empty

Hey Jan,
I used the bingx restclient to load order infos, everything is filled, but not the FeeAsset
To Reproduce
Endpoint: restClient.SpotApi.Trading.GetOrdersAsync(tradeSymbol)
Expected behavior
All properties filled, but FeeAsset is not.

Hi, based on the documentation the FeeAsset is only returned when requesting order details for one specific order (SpotApi.Trading.GetOrderAsync), it's not returned when requesting multiple orders.

Ok, i see, thank you for checking...


Intradocument links

How should a document/entity/collection instance refer to another document?  Possibilities for a URL include

absolute  https://ecom.org/api/product/123
relative to API  product/123
relative to server /api/product/123

Duplicate of #17


apispec_to_template definition bugfix

Generate spec dict after loading definitions

@rochacbruno can you take a look at this pull request to see if it's good? It fixes the problem for me as well. It looks like the spec dictionary was being generated before the schema registration and this fixes that.


Rename submodule under cupyx.scipy.fft

Rel #3420.
This PR renames submodules under cupyx.scipy.fft to indicate that they are CuPy's private submodule and not intended to be used by users.

Jenkins, test this please

This PR blocks #3896.

Jenkins CI test (for commit 1966fef4269bf19cdd8e0b748e540387827a431c, target branch master) succeeded!

@kmaehashi PTAL.

pfnCI, test this please.

Jenkins CI test (for commit 1966fef4269bf19cdd8e0b748e540387827a431c, target branch master) succeeded!

pfnCI, test this please.

Jenkins CI test (for commit 8539e29a289bf42991912b6c572ca448750b55cc, target branch master) succeeded!


Provide source and attribution for zoom.min.js

Add attribution for origin repository. This allows source check and easier modifying of zoom behavior without grepping GitHub guessing what library is used.

@TheDidek why include the non-minimized version of the JS lib?

Want to close a release today @TheDidek will include this PR but will remove the source. Let's discuss here or open a new ticket for that addition. Thanks

It is a practice to prevent bad scenarios when linked repos disappear.
Also it make source available to the visitor up in front, on many projects user can remove .min and get the source.
But that is more marginal case, the important part was to add the attribution :).

@TheDidek did you test if including the source in the static folder exports it to the final site? I would assume so


Refactor error handling for rc.Close in GetObject function GCS storage

What this PR does / why we need it:
Unify error handling for rc.Close() in GetObject function of GCS storage.
ref: https://github.com/pipe-cd/pipe/pull/1485#discussion_r564272156
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

Nice.
/approve

Nice.
/approve


Clarify how joi should be installed

Joi is listed as a dependency of IcedFrisby. The install instructions suggest installing it separately, which makes sense since it needs to be required directly in the user's code.
It wouldn't be good to have multiple versions of Joi installed. So, the user could keep their joi version in sync with the version required by IcedFrisby. That could be fussy though.
Another option is to make it a peer dependency, meaning it has to be required separately, and npm will complain loudly when it is not installed. I've used this a lot with good success, and it tends to simplify upgrades quite a bit.
We could consider doing the same with chai.
Mocha is already a peer dependency.

We could also make Joi an export, but that ties the user to whatever version of Joi IcedFrisy uses.

Right. It would also require an application using Joi to make icedfrisby a dependency instead of a devDependency.
Another option is to make it an optionalDependency. The Joi support in icedfrisby requires a Joi schema to be passed in, so the user will need to require Joi and create it themselves. This makes optionalDependency a nice option: the user needs to declare it as a dependency if and only if they are using – and requiring – it. The user also gets a lot of flexibility.
It seems like this is the situation optionalDependency is designed for!


Add webpage raxielvt.is-cool.dev

Requirements

[x] You have completed your website.
[x] The website is reachable.
[x] The CNAME record doesn't contain https:// or /.
[x] There is sufficient information at the owner field.
[x] Your website is not hosting on the following due to SSL issues: Vercel, Netlify

Description

Using this domain to host a friend's portfolio — a simple web similar to a linktree featuring links to him social media
Link to Website

https://raxielvt.pages.dev/

CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

You can retrigger this bot by commenting recheck in this Pull Request

I have read the CLA Document and I hereby sign the CLA

recheck


Inconsistent useBuyerJourneyIntercept block behaviour with Apple Pay

I have an app that offers a checkout extension to collect required information from buyers. I have noticed that in some stores offering Apple Pay, checkout useBuyerJourneyIntercept block is inconsistent:

Shop 1: Buyer proceeds to checkout and clicks the Apple Pay button at the top. Proceeds with the Apple Pay payment and the order is placed despite missing required information.
Shop 2: Buyer proceeds to checkout and clicks the Apple Pay button at the top. Proceeds with the Apple Pay payment and it is redirected back to Shopify Checkout that shows the error message about missing required information.

Both stores have enabled checkout blocking, which works whenever checking out with a credit card. So I am wondering why there is inconsistency in the checkout process. Is there any documentation available on this, or is this an experiment being run on a small percentage of stores?

i am also facing the similar issues but with Shop pay.  Sometimes our extension is not loading on shop pay express checkout page under shipping method. Because of that some users are able to bypass our logic.
After reloading the page the extension appear but it does not appear always on first load.

It seems like Shop Pay overall is causing so many issues but I don't see any responses for any of them in these issue threads. Hope to get an update soon.


Fix  useCalendarCell Failed to execute 'releasePointerCapture' on 'Element': No active pointer with the given id is found by wrapping in try catch

Closes https://github.com/adobe/react-spectrum/issues/5998
✅ Pull Request Checklist:

[x] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

Thanks for the PR and Issue. I don't quite follow when this happens. Can you show a sample which reproduces the error? Preferably in a codesandbox or stackblitz or on our docs? as well as some steps to follow to verify the issue?
Would it make more sense to call hasPointerCapture to determine if we should release it?
If we're able to reproduce it, then hopefully we'll be able to write a test against it and make sure we don't break it again.
Thanks again!


My whole project got removed

Describe the bug
I was trying to create a website and all of a sudden i get an error and everything gets deleted and I paid for this.

Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-j3zcyo
Steps to reproduce
1.Login
2.Click on Chats
3. Click on most recent chat
4. It will say there is an error
Expected behavior
It wouldn't load the project
Screen Recording / Screenshot

Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 130
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 57104134,
  "usedJSHeapSize": 39442210,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = W-EXOTIC-W
Chat ID = 45e1e1d1c356

Additional context
Error:
An unknown error occured while running an action.

@W-EXOTIC-W please use the instructions here to reload your project into Bolt


Misleading border on plots of non-periodic tree meshes

When you run a simulation on a tree mesh and plot it via the Plots package, it creates a border which seems to be the arithmetic mean of the left and right or the top and bottom values of the solution respectively. While this (maybe) makes sense on a periodic tree mesh, it also happens on a non-periodic tree mesh, where it is just misleading. At least for non-periodic tree meshes it should be removed.
I attached a 2D advection example on a non-periodic tree mesh where you can see that behavior on the top and bottom and in the middle on the left and right border. If you plot just one variable the border is somewhat thin, so you may have to zoom in a bit. The border is specific to the plot function, it does not appear in ParaView for example.

Thanks for reporting this! I agree, this is a real annoyance 😢 . The culprit is cell2node in https://github.com/trixi-framework/Trixi.jl/blob/main/src/visualization/utilities.jl, where we convert cell-centered values to node-centered values for plotting, and which assumes periodicity to create the interpolation stencils at the boundaries:
https://github.com/trixi-framework/Trixi.jl/blob/06635139bf88808601552d751c642563ae8faa76/src/visualization/utilities.jl#L463-L477
Possible fixes include

use a one-sided interpolation stencil at the boundaries and the corners
interpolate (e.g., linearly) from the inside to fill up the interpolation stencil
avoid cell2node entirely and use a new approach that immediately produces the values at the desired locations

The easiest approach would probably be to use one-sided interpolation at the boundaries, as it would be a local fix. If you feel up to it, it would be great if you can give it a try @dlbach. I'd be happy to walk you through the relevant code.

This is related to issue #1256

It definitely does look more dramatic with the surface plot. I'll take a look into the code. Since it's the default behavior if you just use the plot function I do not think a comment, however prominent, is going to do.

No, I didn't want do suggest we just add a comment and that's it. The current approach is horrible, so we should definitely do something about it :-)


Minor modifications to some links in "Windows containers in Kubernetes" page.

This is a Feature Request
In concepts/windows/intro.md file, some document links are over-addressed(?).
For example, links for line 241 and 245 contain the full address to the target location,
and I think it is accessible with only using #, since they exist in same file.
Is there any reason to reference an entire address, instead of using only # ?
What would you like to be added
remove needless part
241: #compatibility-v1-pod-spec-containers-hostnetwork
245: #compatibility-v1-pod-spec-containers-securitycontext

/assign

yes, we can replace the full link with subsection ID

please do it yourself. thank you

Thank you !
/assign


[#626][FOLLOWUP] fix: typo in build.yml

What changes were proposed in this pull request?
Fix a typo in build.yml
Why are the changes needed?
Follow up of #631
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Verified by another github action.

Codecov Report

Merging #633 (6beeff3) into master (ffa26b4) will increase coverage by 2.29%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #633      +/-   ##
============================================
+ Coverage     60.90%   63.19%   +2.29%
  Complexity     1799     1799
============================================
  Files           214      200      -14
  Lines         12381    10410    -1971
  Branches       1042     1042
============================================
- Hits           7541     6579     -962
+ Misses         4437     3488     -949
+ Partials        403      343      -60

Impacted Files
Coverage Δ

deploy/kubernetes/operator/pkg/utils/util.go

...y/kubernetes/operator/pkg/webhook/inspector/pod.go

...oy/kubernetes/operator/pkg/controller/util/util.go

deploy/kubernetes/operator/pkg/utils/config.go

deploy/kubernetes/operator/pkg/utils/rss.go

...oy/kubernetes/operator/pkg/utils/shufflerserver.go

...eploy/kubernetes/operator/pkg/utils/coordinator.go

...bernetes/operator/pkg/controller/controller/rss.go

...tor/pkg/controller/sync/coordinator/coordinator.go

...rnetes/operator/pkg/webhook/inspector/inspector.go

... and 4 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


fix: 修复 MultiFilter 组件选择状态丢失问题。

{PR title}
MultiFilter 组件在第二次打开时会丢失已选择项的状态。

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Documentation bug for auto-suggest

The documentation is wrong both in README.md (where it doesn't mention searchByPlaceId) and index.js (where it mentions getByPlaceId which doesn't exist in the code, also has the wrong returned values for both getByPlaceId and getSuggestions).
This adds unnecessary pain to developers, since they need to reverse-geocode the code to understand how to implement search with auto suggest.

Looks like this was resolved by #108, if this is not the case please open a new issue.


Clean up handling of Uri

This PR is a refactoring of how we handle URIs. Most importantly, we do no more String -> URI -> AbsolutePath - URI -> String roundtrips. While working on this PR observed that Path.toUri.toString produces file:///path instead of file:/path which lsp expects. The logic to produce s"file:$path" was spread all over the place and made it really tricky to debug when things went wrong. Now we only manipulate Uri which is a plain wrapper around a String.

I'll review the changes tomorrow, just a note about

file:///path instead of file:/path which lsp expects

Both formats are correct URIs and LSP doesn't enforce any particular format. The latter one is a more recent standard. Check https://github.com/sbt/sbt/issues/3801, Eugene has a good explanation and references to the standards there. Using the file:///path is better in the sense that it should be supported by older implementations. Does it cause any problems in VSCode? I thought that it uses exactly this format and file:/path comes from the Java file.toURI method.

Interesting, the reason it matters to us is that we persist these URIs as strings and look them up as strings so we'll have to enforce either one. I have no preference which one, with everything under Uri we can decide to use file:/// instead.

This makes no sense 😿
@ URI.create("file:///blah") == URI.create("file:/blah")
res6: Boolean = true

@ URI.create("file://blah") == URI.create("file:/blah")
res7: Boolean = false

@ URI.create("file:/blah") == URI.create("file:/blah")
res8: Boolean = true

I didn't know about that @laughedelic interesting. I updated the implementation to enforce file:///path, now that everything is under Uri we can easily adapt if we prefer to work with java.net.URI etc

Why doesn't it make sense? file://blah is a relative path, isn't it? and file:/blah is an absolute path. So I think it makes sense.. I think the simple trick to transform such string URI (with either format) to path is to do .stripPrefix("file://")


Add leave button to groups

Fixes #286
A Leave Group button is shown in a group view to users that are member of said groups.
Clicking the button removes the currently logged-in user to be removed from the member list.
Also, fixes a bug where the second login with the same OIDC user sets everything on fire.
PR  checklist

[x] dev-branch has been merged into local branch to resolve conflicts
[x] tests and linter have passed AFTER local merge
[x] localization is supported (Guide)
[ ] another dev reviewed and approved
[ ] if feature-Branch: Teams PO has approved (show via e.g. screenshots/screencapture/live demo)

https://user-images.githubusercontent.com/45318774/215099403-65e1eb6b-ac9c-4be7-a152-938d25c95aad.mp4

The code looks good to me, but I think this still needs some css rework until we can merge it. @dasGoogle can give you a helping hand if you want, or you can fix it yourself, as you like :)

I cannot reproduce your screenshots. At what resolution/browser/mode did you take them?


Minor typo in line 36, page 771, version 2023-04-01

graphical model structure learning techhniques
"techhniques"  should be "techniques"

fixed


[Help] cannot hook stat

JNIEXPORT jint JNICALL JNI_OnLoad(JavaVM *vm, void *)
{
struct stat buf;
char *res="/system/xbin/su";
int resultNow = stat(res, &buf) == 0 ? 1 : 0;
if (resultNow == 1) {
AKLog("IS ROOTED");
} else
{
AKLog("NOT ROTED");
}
return JNI_VERSION_1_6;
}
Link Code : https://codeshare.io/2jObyB
i cannot hook "stat" . Please help me. i try AKHook(stat) but not working

Since stat is a kind of ambiguous symbol, you probably have to make it clear (e.g. get its function pointer first and then use AKHookFunction directly).

Can you give me the example above?

I did check again, Source build with NDK =>  AKHook(stat) working fine , but source build with Cmake, AKHook(stat) not working ? pls help me :(

Please attach the CMake error message.

Sorry, my Cmake not error message, I want to ask you how hook function stat :(
i cannot hook it with AKHook(stat), please give me the any examples. thanks you
struct stat buf; char *res="/system/xbin/su"; int resultNow = stat(res, &buf) == 0 ? 1 : 0; if (resultNow == 1) { AKLog("IS ROOTED"); } else { AKLog("NOT ROTED"); }

My AKHook(stat)
`int(*sys_stat)(const char *name, struct stat *value);
int my_stat(const char *name, struct stat *value) {
if (strstr(name, "/system/xbin/su") != NULL)
{
    return -1;
}
return sys_stat(name, value);

}`

Are you sure AKHook(stat) is called properly before stat?

Yes, i sure AKHook(stat) call before run stat;

That's impossible, inline hook should never fail without crashing the application.

OK, thanks you, i think my mistake. i will build again .


[Federation] Replacing deployment definition does not evenly distribute replicas across clusters

 Issue by ajwootto
Friday May 19, 2017 at 18:16 GMT
Originally opened as https://github.com/kubernetes/kubernetes/issues/46119

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): No
What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): federation, deployment, replace

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Kubernetes version (use kubectl version): 1.6.2
Environment:

Cloud provider or hardware configuration: GCP/GKE

What happened:
With a three cluster federation and a deployment with 16 replicas, replacing the deployment using
kubectl replace -f deployment.yaml
results in all the updated pods going to one cluster rather than being evenly distributed.
What you expected to happen:
The pods should be evenly distributed (especially given the fact that they were correct before the replace operation)
How to reproduce it (as minimally and precisely as possible):

Create a deployment resource in the federation control plane (which is managing multiple underlying clusters)
Scale the deployment (mine is set to 16). Pods should then be evenly distributed, between 4-6 in each cluster
Replace the deployment with an updated version (new image, etc.) using
kubectl replace -f deployment.yaml
Watching the list of pods in each cluster, I see the pods starting to be replaced correctly, but at some point the newly updated running pods will all get terminated in two of the clusters and everything will be moved to the third cluster.

Anything else we need to know:
Full deployment spec:
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: users
spec:
  replicas: 16
  template: # create pods using pod definition in this template
    metadata:
      annotations:
        federation.kubernetes.io/deployment-preferences: |
          {
            "rebalance": true,
            "clusters": {
              "us-central": {
                  "minReplicas": 3
              },
              "eu-west": {
                  "minReplicas": 3
              },
              "asia-se": {
                  "minReplicas": 3
              }
            }
          }
      labels:
        app: users
    spec:
      containers:
        - name: users
          image: gcr.io/myimage
          ports:
          - containerPort: 8000
          env:
            - name: GO_ENV
              valueFrom:
                configMapKeyRef:
                  name: environment
                  key: GO_ENV
            - name: REDIS_CLUSTER
              valueFrom:
                configMapKeyRef:
                  name: environment
                  key: user_redis
            - name: DISABLE_REDIS
              value: "false"
          readinessProbe:
            httpGet:
              path: /healthz
              port: 8000
            periodSeconds: 1
            timeoutSeconds: 1
            successThreshold: 1
            failureThreshold: 10
---
apiVersion: v1
kind: Service
metadata:
  name: users
spec:
  selector:
    app: users
  ports:
    - protocol: TCP
      port: 80
      targetPort: 8000
  type: NodePort

Despite the federation annotation that should require a minimum of 3 pods (and allow rebalancing) the state remains incorrect with no hosted pods in two of the clusters.
If I scale the replicas down to zero using
kubectl scale --replicas 0 deployment users
and wait long enough for all the user pods to be killed, then scale back up to 16, they will be correctly distributed between the three clusters. Thusfar I've had to do this every time I update the image for the deployment.

 Comment by perotinus
Thursday May 25, 2017 at 01:00 GMT

Does this happen consistently? Would you happen to have a log from the Federation controller manager? It may have more details about what's going on.
You can get this log by first finding the controller manager pod (kubectl get pods --namespace=<your_federation_system_namespace> --context=<host_cluster_context>) and running kubectl logs <cm_pod_name> --namespace=<your_federation_system_namespace> --context=<host_cluster_context>).

 Comment by ajwootto
Thursday May 25, 2017 at 17:09 GMT

It happens consistently, every time I do a replacement, and it seems that all of the pods always get sent to the same cluster. There isn't much of interest in the controller log, it basically just says:
I0525 17:02:06.341069       1 deploymentcontroller.go:595] Updating users in us-central
I0525 17:02:06.341101       1 deploymentcontroller.go:595] Updating users in asia-se
I0525 17:06:12.730444       1 deploymentcontroller.go:595] Updating users in eu-west

I've managed to get the annotation for minimum replicas partially working (turns out I had it in the wrong part of the yaml), but this also seems to come with its own problem. When I have a configuration like:
annotations:
    federation.kubernetes.io/deployment-preferences: |
      {
        "rebalance": true,
        "clusters": {
          "us-central": {
              "minReplicas": 3
          },
          "eu-west": {
              "maxReplicas": 0
          },
          "asia-se": {
              "maxReplicas": 0
          }
        }
      }

And the # of replicas for the deployment set at 6, I only end up with three pods total, all in the us cluster. It seems like the system is treating the minReplicas directive as a max or something.

 Comment by bspradling8
Wednesday Jun 07, 2017 at 21:16 GMT

I'm noticing the same behavior that everything is dumped into the same cluster as a replacement. I did a quick test of the annotations to see if I could get a workaround by:
    federation.kubernetes.io/deployment-preferences: |
      {
        "rebalance": true,
        "clusters": {
          "us-central": {
              "minReplicas": 3
          },
          "eu-west": {
              "minReplicas": 3
          }
and even then I noticed that the existing pods weren't getting rebalanced correctly.

 Comment by bspradling8
Thursday Jun 08, 2017 at 22:21 GMT

@ajwootto have you found a workaround for this?

 Comment by ajwootto
Friday Jun 09, 2017 at 16:54 GMT

@bspradling8 Right now I've just been using the min annotations to force each cluster to have at least 3 pods. Problem at the moment is that it seems there can never be more than the min number in the annotation. I'm going to start playing with autoscaling soon as well, so we'll see if it remains a problem.

 Comment by bspradling8
Friday Jun 09, 2017 at 17:14 GMT

@ajwootto Gotcha, I'll be interested to see how autoscaling affects this. I just got the annotations working as you just described this morning. Turns out I had them in the wrong spot as well :)

 Comment by perotinus
Monday Jun 12, 2017 at 19:06 GMT

@ajwootto @bspradling8 I believe that I have a workaround for the second problem (the one that occurred when you had the annotation in the right place): add a "weight": 1 entry under each of the minReplicas and maxReplicas entries, and you should get enough replicas in each cluster:
annotations:
  federation.kubernetes.io/deployment-preferences: |
    {
      "rebalance": true,
      "clusters": {
        "us-central": {
          "minReplicas": 3,
          "weight": 1
        },
        "eu-west": {
          "maxReplicas": 0,
          "weight": 1
        },
        "asia-se": {
          "maxReplicas": 0,
          "weight": 1
        }
      }
    }

 Comment by perotinus
Monday Jun 12, 2017 at 23:38 GMT

I believe I understand the reason for the first failure as well. The federated deployment controller watches pods in the underlying cluster to get information that it uses to determine capacity and schedule pods. When a deployment is being updated to a new image, it creates a new replica set for the new pods and scales down the old replica set. For some reason, it looks like the federated deployment controller is taking the pods that are being spun down into account in its calculations for scheduling, which causes it to think that the first cluster that it happens to process for scheduling has more replicas than it should. Depending on when exactly the scheduling occurs, the first cluster processed can steal some or all of the replicas from others. Since rebalance is false by default, when the first cluster is given the replicas, it keeps them until the deployment is scaled down and back up.
For now, the workaround is as you've described: scale down to 0 then scale back up. This is not a reasonable workaround for a production environment, though, so we need to determine the right way to fix this.

 Comment by kishorekumark
Wednesday Oct 25, 2017 at 17:52 GMT

Same issue observed with version, even with "weight:1 "
{code}
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.0", GitCommit:"6e937839ac04a38cac63e6a7a306c5d035fe7b0a", GitTreeState:"clean", BuildDate:"2017-09-28T22:57:57Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.0", GitCommit:"6e937839ac04a38cac63e6a7a306c5d035fe7b0a", GitTreeState:"clean", BuildDate:"2017-09-28T22:46:41Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
{code}

cc @ajwootto

I've experienced this as well using a 1.9.x based federation.


how to deploy windows IIS production level

i want run this project in IIS , locally its working fine ,but I want to deploy my Web application in IIS, it's not working properly I am searching 3 to hours but doesn't success.
how to work this project on IIS. if you need anything else for understand I am here. I share Two images for you understand my problem
var app = angular.module('app', ['ui.router', 'ui.bootstrap', 'flash',
       //main modules
       'login', 'dashboard','staffregistration']);

   app.config(['$stateProvider', '$locationProvider', '$urlRouterProvider', function ($stateProvider, $locationProvider, $urlRouterProvider, $modalInstance) {

       //IdleScreenList
       $stateProvider
          .state('app', {
              url: '/app',
              templateUrl: 'app/common/app.html',
              controller: 'appCtrl',
              controllerAs: 'vm',
              data: {
                  pageTitle: 'Login'
              }
          });

       $urlRouterProvider.otherwise('login');

       //$urlRouterProvider.otherwise('app/dashboard');
       //$urlRouterProvider.otherwise('/app/dashboard');
   }]);

   // set global configuration of application and it can be accessed by injecting appSettings in any modules
   app.constant('appSettings', appConfig);

webconfig
 <configuration>
     <system.webServer>
        <defaultDocument>
          <files>
            <clear />
            <add value="index.html" />
          </files>
        </defaultDocument>
    </system.webServer>
    </configuration>

https://stackoverflow.com/questions/46336656/simple-angularjs-application-run-iis?noredirect=1#comment79643331_46336656
https://i.stack.imgur.com/KyI1u.jpg

HI @addikhann. Pretty sure this is not the repository you're looking for. IIS is itself an HTTP server, so if you're using IIS you don't "need" http-server.
It looks like you're building a client-side Angular.js app--the example code for which may have used http-server during development. So. If you go back to that repo (or tutorial), hopefully the folks there can be of more help.
Cheers!