ARTEMIS-2336 Use zero copy to replicate journal/page/large message file

Use sendfile to replicate files during backup sever bootstrap.

I'm yet reviewing it, but do you have already some numbers to show how it performs in comparison with the original version? Great work!

@franz1981 @clebertsuconic  Thanks for the review. I've modified as you commented.  There is no issue in our production env using buffer send:) We just want to squeeze performance(sometimes tens of GB files needs to be transferred although it's only happening during catchup). Also in a few months, we'll use 10-gigabit cards for our cluster which maybe make cathup more fast by using sendfile.  We deployed the test and saw that the change saved a visible amount of CPU.
Flamegraph of master:

Flamegraph of the PR:

As we can see, at least 29% of the total time(21% FileChannelImpl::read and 8% PacketImpl::encode) is saved.

@franz1981 Thanks for the great suggestions. All should be done:)

@wy96f Just a qq: DefaultFileRegion is supported by windows/MacOS too?

@wy96f Just a qq: DefaultFileRegion is supported by windows/MacOS too?

It should work on both. I tried it successfully in windows. Wikipedia notes "macOS supports zero-copy through the FreeBSD portion of the kernel", should be sendfile system call i guess.

@wy96f
I'm more concerned about Windows TBH: I don't know if Netty supports zero copy on it...
let me take a look :+1:

Where are we with this id like to merge it? It seems to run fine locally on windows. Any other concerns?

@franz1981, is this ready to merge?

@jbertram I would like to profile the improvement, but it seems ok to me bud, can be merged!


Remove any mention of VSWorkspaceSettings.json

Hey Michael and Colin,
Per a conversation with Will and Steven from the AnyCode team, we have decided to remove VSWorkspaceSettings.json from the documentation. The user was never intended to be user-editable - so it's our fault it's included in the first place and has led to some customer confusion. I've tried to clean up this file - let me know if I'm missing something, if there are other files I need to address, or if you have any questions. Thanks for your help!

@esweet431 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Silencing broken after major upgrade

I have recently upgraded Sensu from 0.20.3-1 to 0.26.5-2 and Uchiwa from 0.10.3-1 to 0.21.0-1 in Ubuntu 14.04. Before, Stashes worked. Now, Silencing does not. Stashes tab is still showing, even though I deleted the Redis database. I have not touched the configuration files on disk.
Expected Behavior
When I create a Silencing entry, Sensu stops sending mails.
Current Behavior
It does not.
Silencing entry:
_id Sensu:client:mtr01.homeatcloud.cz:local_system_disk_usage
check local_system_disk_usage
creator admin
dc Sensu
expire -1
expire_on_resolve true
id client:mtr01.homeatcloud.cz:local_system_disk_usage
reason Still fine.
subscription client:mtr01.homeatcloud.cz
Host entry:
_id Sensu/mtr01.homeatcloud.cz
address <IP_ADDRESS>
cluster default
fqdn mtr01.homeatcloud.cz
graphite_name mtr01_homeatcloud_cz
hostname mtr01
keepalive
{
"handler": "default",
"thresholds": {
"critical": 180,
"warning": 120
}
}
name mtr01.homeatcloud.cz
silenced false
subscriptions local-ceilometer-server, local-sensu-client, local-ntp-client, local-linux-storage, local-linux-system, local-linux-network, local-openssh-server, local-mongodb-server, local-salt-minion, local-ubuntu-system, local-debian-system, mtr01-homeatcloud-cz, local-common
timestamp 2016-12-09 12:06:33
version 0.20.3
Check entry:
command PATH=$PATH:/usr/lib64/nagios/plugins:/usr/lib/nagios/plugins check_disk -w 15% -c 5% -p / -p /var -p /usr -p /tmp -p /var/log
duration 0.008
executed 2016-12-09 12:06:42
handlers default
interval 60
issued 2016-12-09 12:06:42
name local_system_disk_usage
occurrences 1
output DISK WARNING - free space: / 2513 MB (15% inode=86%);| /=13570MB;13684;15294;0;16099
status 1
subscribers local-common
type standard
history 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1

OK, I got it myself. The older sensu client on the node mtr01 did not create a "per-client subscription" (see https://sensuapp.org/docs/0.26/reference/silencing.html), which Uchiwa uses when creating the check. Upgrading all clients to post-0.26 Sensu resolves the issue.


Make sure label and normal symbol can be used together

Coverage increased (+0.1%) to 70.366% when pulling b9460199c35dffdfd5ef945b44968452a4c0867c on fix-label into f4dd01ee59c026b9d743fecbe3fa2a3226a6b0f5 on master.


Refactor from Result.Infix to Result.Syntax

In bb47bcd64a3fb8ca585b69d1260140b11727a815 the Result module got a submodule Syntax using the let-syntax for bind and map. It is in my opinion nicer to read the let-syntax than the infix syntax. It would be nice to rewrite all usage of the infix syntax to use the let-syntax.

done in #143


Do you plan to provide dataset part code for training imagenet vid and det?

As what I mention above.

You might be interested in https://github.com/open-mmlab/mmtracking


Refs RHIROS-576 - add env params in clowdapp.yaml

[Urgent] Need this change to override env vars related to Garbage collector processor for testing and for future use.

Merging this PR!


I can't use it

the error:
17/08/25 18:18:08 WARN ScalaRowValueReader: Field 'lxdh' is backed by an array but the associated Spark Schema does not reflect this;
(use es.read.field.as.array.include/exclude)
17/08/25 18:18:08 WARN ScalaRowValueReader: Field 'imei' is backed by an array but the associated Spark Schema does not reflect this;
(use es.read.field.as.array.include/exclude)
17/08/25 18:18:08 WARN ScalaRowValueReader: Field 'imsi' is backed by an array but the associated Spark Schema does not reflect this;
(use es.read.field.as.array.include/exclude)
17/08/25 18:18:08 WARN ScalaRowValueReader: Field 'cardno' is backed by an array but the associated Spark Schema does not reflect this;
(use es.read.field.as.array.include/exclude)
17/08/25 18:18:08 WARN ScalaRowValueReader: Field 'mac' is backed by an array but the associated Spark Schema does not reflect this;
(use es.read.field.as.array.include/exclude)
17/08/25 18:18:08 WARN ScalaRowValueReader: Field 'lxdh' is backed by an array but the associated Spark Schema does not reflect this;
(use es.read.field.as.array.include/exclude)
17/08/25 18:18:08 WARN ScalaRowValueReader: Field 'imei' is backed by an array but the associated Spark Schema does not reflect this;
(use es.read.field.as.array.include/exclude)
17/08/25 18:18:08 WARN ScalaRowValueReader: Field 'imsi' is backed by an array but the associated Spark Schema does not reflect this;
(use es.read.field.as.array.include/exclude)
17/08/25 18:18:08 WARN ScalaRowValueReader: Field 'cardno' is backed by an array but the associated Spark Schema does not reflect this;
(use es.read.field.as.array.include/exclude)
17/08/25 18:18:08 WARN ScalaRowValueReader: Field 'mac' is backed by an array but the associated Spark Schema does not reflect this;
(use es.read.field.as.array.include/exclude)
the code as follows:
SparkConf conf = new SparkConf();
conf.set("es.index.auto.create", "true");
conf.set("es.nodes", "<IP_ADDRESS>");
conf.set("es.port", "9200");
conf.setAppName(VMAnalyse.class.getName());
if (Shell.WINDOWS) {
conf.setMaster("local");
}
JavaSparkContext sc = new JavaSparkContext(conf);
SQLContext sqlContext = new SQLContext(sc);
Map<String,String> esOptions =new HashMap<String, String>();
esOptions.put("es.nodes", "<IP_ADDRESS>");
esOptions.put("es.port", "9200");
esOptions.put("es.index.auto.create", "true");
esOptions.put("es.scroll.size", "10000");
esOptions.put("es.field.read.as.array.include", "mac");
esOptions.put("es.field.read.as.array.include", "lxdh");
esOptions.put("es.field.read.as.array.include", "imsi");
esOptions.put("es.field.read.as.array.include", "imei");
esOptions.put("es.field.read.as.array.include", "cardno");
    String trs_info_relations="wsx_trs_info_relations";

    sqlContext.read().format("org.elasticsearch.spark.sql").options(esOptions)
  		.load(trs_info_relations+"/"+trs_info_relations).show();

Please fill out the template provided for Github issues. Issues with the title "I can't use it" are not helpful to contributors on the project and your post lacks important information, like what versions of the connector and Spark that you are using. If you are unsure of what to put in the github issue then please post on the forums and the community will attempt to assist you. Github is reserved for confirmed bugs and feature tracking only.
You are using es.field.read.as.array.include but the property is es.read.field.as.array.include.


Move imports in crimereports component

Breaking Change:
None
Description:
Moved import from function to top-level as requested in #27284
Checklist:

[ ] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

Note: imports sorted using isort

This PR has been superseded by #27973


Dom manipulation in jailed

Is there a way to manipulate parent dom in jailed iframe.

Yes, by making a function that does this manipulation accessible to the jailed script. The first example shows how to do this with alert().


Update to PyTorch 2.0

2.0 is now stable.

Using the RMM memory allocator is also now possible. The only issue is backwards compatibility with 1.x.


JSDoc: @example tag does not parse inline tags like {@link myProperty}

Bug Report
🕗 Version & Regression Information
Win 11, HP Spectre x360
Seen in VS Code 1.79.2, using JavaScript display formatting (.js file), "About" data from VS program:
Version: 1.79.2
Commit: 695af097c7bd098fbf017ce3ac85e09bbc5dda06
Date: 2023-06-14T08:57:04.379Z
Electron: 22.5.7
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Does occur when extensions are disabled
🔎 Search Terms
JSDoc, example, @/example (without the slash), inline, vscode, tags, doctags
Found similar issues but couldn't find a non-closed duplicate. Some similar ones, microsoft/vscode#56223 microsoft/TypeScript#55056 microsoft/vscode#26338
(Also some similar stuff in the /typescript repo, eg #15749)
⏯ Playground Link
Playground link with relevant code
I just copied the function I linked but tbh this is overkill lol
💻 Code

/** const ref to Grieger Triptychial Projection name, take THAT spelling mistakes */
export const grieger = 'grieger';

/**
 * Gets the const reference name of the given map property (accommodating for alternate names). Returns null if not found.
 *
 * @param {string} map name of map projection you want
 * @return {string} map projection name, per const refs at top of maps.js
 * @example Eg, inputting "triptychial" returns {@link grieger [grieger]}
 * @see {@link maps} for all valid map name inputs
 */
export function ParseMap(map) {
    // let id = GetMapID(map);
    // if (id < 0) {
    //     console.error("ERROR: could not parse map " + map + ", invalid ID " + id + ", returning null");
    //     return null;
    // }
    // return maps[id][1];
}

// copy of the function that I noticed the issue on
// for more info see src file maps.js:
// https://github.com/duckpondstudio/mapper/blob/afa2929b90a8434451e57f65619aa0ed34f3d5c5/src/js/maps.js

🙁 Actual behavior
Using an inline {@/link myProperty} jsdoc tag in an @/example tag does not render properly, instead rendering what looks like the full command input that should turn into a hyperlink.

🙂 Expected behavior
The @/link property should just be a clickable link to the linked property, like what's in the @/see tag just below the @/example

Minimal example:
/**
 * @example 1 + 1 {@link foo foo}
 */
const foo = 1;

@example tags render their content as code snippets. This matches how JSDoc works. So the bug here is that {@link ... should likely just be rendered as source text in this case

@example tags render their content as code snippets. This matches how JSDoc works. So the bug here is that {@link ... should likely just be rendered as source text in this case

Thank you for clarifying!


feat: removes return model from reactor-formula delete

Description

removes return model from reactor-formula delete

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

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


version 1.18 onwards requires DNS and online connectivity to install VSIX files

VSCode Version: 1.18.1
OS Version: Windows 10 Enterprise Version 1703

Steps to Reproduce:

Without an internet connection, attempt to install Powershell 1.5.1 vsix file either in Application or by running "code --install-extension "D:\installs\PowerShell-1.5.1.vsix"
The following error occurs when going from command line:
Error: getaddrinfo EAI_AGAIN marketplace.visualstudio.com:443
at Object.exports._errnoException (util.js:1050:11)
at errnoException (dns.js:33:15)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:73:26)

If you enter in a hosts file entry you get an error connecting.  I am using this in an environment with no internet connectivity capabilities.
If I downgrade to version 1.17.2 I am able to install the 1.5.1 Powershell extension fine.  This online check seems to be part of the new version

Reproduces without extensions: Yes

I'm experiencing the same issue. We have administrative servers without an active internet connection. On previous versions i could manually update the plugins just fine, now it does not work anymore. Please fix this.

@sandy081 Notice that if we can't reach the Marketplace, the installation of a VSIX should still work.

Duplicate of #37973


Failure to create a container leaves others created

If deis scale cmd=5 creates 4 containers but fails on the 5th, it raises an exception and leaves 4 containers in the "created" state, not running. The code in question is here: https://github.com/deis/deis/blob/master/controller/api/models.py#L272-L292
It would be more intuitive and useful behavior if instead Deis made a "best effort" to start whichever containers it was able to create. In this particular case we used deis limits:set -c cmd=1024 to ensure some containers wouldn't be created due to resource limitations, then scaled up, and were left with this:
$ deis info
=== zigzag-drumroll Application
{
  "updated": "2015-04-30T22:05:12UTC",
  "uuid": "0c0dd591-5d9c-45c4-914d-52d703886cb3",
  "created": "2015-04-30T21:53:21UTC",
  "url": "zigzag-drumroll.local5.deisapp.com",
  "owner": "test",
  "id": "zigzag-drumroll",
  "structure": {
    "cmd": 1
  }
}

=== zigzag-drumroll Processes

--- cmd:
cmd.1 created (v3)
cmd.2 created (v3)
cmd.3 created (v3)
cmd.4 created (v3)
cmd.5 destroyed (v3)

Interesting. In this particular scenario, they should've been removed from fleet because we roll back changes if they fail to create. Does the controller confirm https://github.com/deis/deis/blob/master/controller/api/models.py#L284-L287 was triggered? If so, why weren't they removed? Did we accidentally remove that rollback feature?

It happened with Swarm not yet hit this particular use case with Fleet. @mboersma  set the cpu limits to 1024 and scaled the app to 5 on a 4 node cluster .
Expected behavior is 4 Containers of the app should be started on 4 nodes and 5th container should hit failure case.

Maybe this is effectively specific to the Swam Scheduler then, but it looks like we could fall into the same code regardless. I'll try to fix it since I have a reproducible case here using Swarm.

There is a high probability of hitting this scenario if the scheduler is resource aware.

It's not hard to fix the models.py code to start the containers which were created successfully, which fixes this case. The tricky part is bubbling up the particular errors so the deis CLI can see that some containers started, but also know why some were not.

Thinking of the two use cases, if someone calls deis scale web=20 with a resource-constrained scheduler like Swarm, we could

abort the operation saying that there's not enough resources for this request, rolling back
scale up as high as possible, then report that there's not enough resources for the rest of the containers (@mboersma's proposal)

@carmstrong any thoughts on which is the best solution? Both are correct, it's just a matter of what behaviour we should enforce.

@bacongobbler I would think in your examples, number 2 is the most correct. I could think of a few instances where someone would want a specific number of containers.

I strongly suggest we abort the operation if there are not enough resources (option 1).  If I ask for 20 containers and I only get 10, that should be rolled back immediately since a) it's not what I asked for and b) the cluster might be resource-starved and we should release the resources.

@gabrtv best effort scaling is one of the solutions but with deis we want users to be cluster agnostic. So if deis scale web=x failed how would a user would know what is the best 'x' to scale next if the previous 'x' value failed.  I think we should give best effort as an option while scaling the containers, deis scale web=x. Here user is stressing that I want either 'x' containers or nothing and deis scale web=~x or deis scale web <= x A soft constraint where user wants to scale upto a some value less than or equal to 'x' .  I also agree with @bacongobbler  deis scale web++ or  deis scale web+1.
Its also hard for the user to guess the best value of 'x' if the resources in the cluster are changin dynamically

failed how would a user know what is the best 'x' to scale next if the previous 'x' value failed

Maybe a Cannot scale web=20, requested mem=2G, available=1G? Basically a "I cannot accept your request. I got x resources, but I only have y resources available for your use." I agree with @gabrtv that we should completely fall back when the cluster cannot handle the amount of requested resources.

yeah but we should not make user calculate the X value by himself and by the time he calculated the X value the available resources in the cluster might change. We should either give him an option to schedule to X or <= X. Basically we cannot guarantee to what value user can scale unless we have our own custom scheduler that locks the available resources until he makes the next decision.

yeah but we should not make user calculate the X value by himself and by the time he calculated the X value the available resources in the cluster might change.

That is true, but it's also a rare case that only occurs when all users are sharing all of the resources of a cluster. In a multi-tenant Deis environment (which is something I've briefly mentioned in https://github.com/deis/deis/issues/2007#issuecomment-57721203), each user (or a group of users) would be given a slice of the cluster's resources which they would have access to, so the resource pool wouldn't necessarily change all that much. I still think that having a strict and a lazy way to scale would still be the best way to solve this.

We should either give him an option to schedule to X or <= X

Yes, I think we're both agreeing on the same thing here. We can have both worlds with deis scale web=20 being a hard scale (today's behaviour, which is what most people would expect anyways) and deis scale web=~20 being a soft scale. Does that sound good to you, or is there something else missing?

Yup exactly. We should also give a feature like soft scale or come up with our own arithmetic operators (<= , ++ , -- , web+y )

If I have an app with 40 containers running, and I do deis scale cmd=41 and it can't create the 41st container...what should happen? Currently Deis leaves the existing 40 alone and tries to create only the one needed, then fails and leaves this:
$ deis info
...
=== rugged-teaspoon Processes

--- cmd:
cmd.1 up (v3)
cmd.2 up (v3)
...
cmd.39 up (v3)
cmd.40 up (v3)
cmd.41 destroyed (v3)

But the behavior described above indicates we should destroy the 40 running containers as well.
Which is fine if that's how it should behave. I'm just pointing out this is a tricky area and we must proceed cautiously.

But the behavior described above indicates we should destroy the 40 running containers as well.

Sorry, I meant a roll back to the previous state, so only the 41st container would be destroyed.


Update dependencies and Rust version

Just a routine for niche bug fixes, linkage errors, perf improvements, etc.
Closes #2295

r? @wycats
(rust_highfive has picked a reviewer for you, use r? to override)

Gonna wait for travis/appveyor to pass before merging

@bors: r+ 8a715044560942446ead8ae4fac8d1c40874a880

:hourglass: Testing commit 8a71504 with merge 24b96eb...

:broken_heart: Test failed - cargo-win-msvc-64

@bors: r+

:pushpin: Commit 5d5cd86 has been approved by alexcrichton

:hourglass: Testing commit 5d5cd86 with merge e964527...

@bors: r+ force

:pushpin: Commit c3486f6 has been approved by alexcrichton

:hourglass: Testing commit c3486f6 with merge e5c76cb...

:broken_heart: Test failed - cargo-win-msvc-32

@bors: r+ dd34296

:hourglass: Testing commit dd34296 with merge 44c0d7b...

:sunny: Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64

Note that with some MSVC troubles I landed this without the Rust version upgrade

I believe this breaks compilation on Rust 1.2.0: https://travis-ci.org/rust-lang/cargo/jobs/104703954

Hm, yes indeed...


Demo: "Error while signing in with Github: Email can't be blank"

I can't login through GitHub.

I'm not really supporting that demo as in bugfixes, but thanks for reporting 👍


Improve Fastly Compute@Edge Example

Do you know Worktop's next version has a capability to work with Fastly Compute@Edge & Faunadb JS Driver can Work with Compute@Edge?
Also there are GraphQL Server Frameworks that are Compatible with Edge Environments. GraphQL Helix & GraphQL Yoga are the most Dominant One's.
Could You Update the Example to use Worktop or FlightPath & add a GraphQL Example?

I don't know why, but AbortController isn't defined in Compute@Edge JS Runtime. How I can Polyfill it?

Hi, thats a good idea but Compute@Edge requires outgoing requests to go to a predefined backend passed in via then backend property through fetch(). Since worktop does not include any utility to pass in that option, I don't think it'll be very useful. Incidentally, the custom fetch() requirement also prevents us from using the Fauna js client.
To help with routing, a good alternative is itty-router, which should work. For the purposes of this sample, we're limiting use of 3rd party dependencies for maintainability.

I have used the fetch option in faunadb JS client instance like these:
const client = new faunadb.Client({
  secret: 'your secret',
  fetch: (url, params) => {
    return Promise.race([abortPromise, fetch(url, { backend: "faunadb", ...params })])
  },
})

Oh, it's treaky to integrate Faunadb JS Driver with Fastly Compute@Edge, but I have a Working Demo.
https://github.com/amancoder28/fauna-compute-edge-example

Thanks for all this. The abort-controller polyfill, timeout workaround and custom fetch seems to do the trick. I'll test this out and update the sample if we don't run into any major issues.

Also What About GraphQL? We can use GraphQL Yoga with Remote Schema Loader from GraphQL Tools(https://www.graphql-tools.com/).

We don't have a solution yet for setTimeout polyfill.  For GraphQL, there's another sample here albeit its in Rust.

Oh, It's hard to Read a Rust Code. I will try to implement it with GraphQL Yoga with minimal code & we will see if it's good enough.

Wow, it's easy to create a GraphQL gateway with Fastly Compute@Edge & FaunaDB.
https://github.com/amancoder28/fauna-compute-edge-example

Please create with-worktop & with-graphql-yoga branches for me to create pull requests because I don't need to just override your implementations.

I don't know why but the GraphQL Examples are Working on My Machine, but after Deploying to Fastly Compute@Edge, all of them have Stopped Working. but they Work on Cloudflare Worker.

I don't know why but the GraphQL Examples are not Working after Deploying to Fastly Compute@Edge, but they Working on My Machine. Also I have tried them on Cloudflare Workers & the Examples are Working. There is a Serious Problem with Fastly. Please Tell me if they are Working for You.

There's no GraphQL example in this project. Which are you referring to?

I don't know why but the GraphQL Examples are not Working after Deploying to Fastly Compute@Edge, but they Working on My Machine. Also I have tried them on Cloudflare Workers & the Examples are Working. There is a Serious Problem with Fastly. Please Tell me if they are Working for You.

There's no GraphQL example in this project. Which are you referring to?

In My Repo:
https://github.com/amancoder28/fauna-graphql-compute-edge-example
https://github.com/amancoder28/fauna-graphql-compute-edge-example-2

In My Github Repos: https://github.com/amancoder28/fauna-graphql-compute-edge-example https://github.com/amancoder28/fauna-graphql-compute-edge-example-2

Oh I see. Realize that Cloudflare and Fastly are vastly different runtime environments. Though, I'm not sure why it works locally on not when deployed...you may have to find help from Fastly. None of this is an issue for THIS project though.

I Think know we have Solved the Issues that's making Fauna JS Driver not to work in Fastly Compute@Edge. Just Contact me for future Contribution. Thanks.


transport: converts Endpoint interface into a struct

This PR converts transport.Endpoint interface into a struct in order to make easier build third-party transports .
For better understanding of this pr refer to https://github.com/src-d/go-git/pull/650/commits/d9385afb02e18b19102764e460cb445b43d6dc91
Fixes #437, #424

Hey, what's the reasoning behind this? The link you show just points to some code change but I don't see why that change is beneficial.
Thanks


a new error i never seen before

2023-06-06 16:29:31
Generating ESM language model embeddings[C:\Users\lsy\anaconda3\envs\diffdock\lib\site-packages\torch\jit_check.py:181](file:///C:/Users/lsy/anaconda3/envs/diffdock/lib/site-packages/torch/jit/_check.py:181): UserWarning: The TorchScript type system doesn't support instance-level annotations on empty non-base types in __init__. Instead, either 1) use a type annotation in the class body, or 2) wrap the type in torch.jit.Attribute.
warnings.warn("The TorchScript type system doesn't support "
0it [00:00, ?it/s]OMP: Error #15: Initializing libiomp5md.dll, but found libiomp5md.dll already initialized.
OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://www.intel.com/software/products/support/.
Processing 1 of 2 batches (15 sequences)
Processing 2 of 2 batches (4 sequences)
HAPPENING | confidence model uses different type of graphs than the score model. Loading (or creating if not existing) the data for the confidence model now.
Size of test dataset:  19
could you pleaes provide some suggestions how to fix up the issues?
many thanks,
Sh-Y

import os
os.environ["KMP_DUPLICATE_LIB_OK"]  =  "TRUE"

put the code on the py file, to avoid the extra loading of libiomp5md.dll
that works for me


Canalrcn

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] Searched the bugtracker for similar pull requests
[x] Read adding new extractor tutorial
[x] Read youtube-dl coding conventions and adjusted the code to meet them
[x] Covered the code with tests (note that PRs without tests will be REJECTED)
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[x] New extractor
[ ] New feature

Description of your pull request and other information
Add support for canalrcn.com videos. Canal RCN is a Colombian television channel. The extractor:

Extracts video metadata from JSON-LD data
Handles geo-restricted content (videos are only available in Colombia)
Delegates video playback to DailyMotion extractor through url_transparent

Example URLs:

https://www.canalrcn.com/la-rosa-de-guadalupe/capitulos/la-rosa-de-guadalupe-capitulo-58-los-enamorados-3619

Thanks for your work!
Some initial comments:

investigate the _search_json_ld(), or else _search_json(), methods
investigate the traverse_obj utility function
what happens if you aren't in CO and just carry on passing the video ID to DM?

You should find examples of using the mentioned methods and functions in newer extractors.
The existing ld+json parsing in the core code won't work for this site if what you need is the embedURL but it could/should be modified to separate finding and parsing as in yt-dlp, giving you access to the ld+json Pythonised JSON before it's made into an info-dict.
The test video at DM says that it's marked as private. Does that happen in CO, or does the site pass additional data (cookies, eg) to DM? Maybe that can be reproduced, if necessary, in the extractor for foreign telenovela fans.


init Modular Service Abstraction Layer, proof of concept

Description of changes

A proof of concept to hopefully illustrate what I had in mind for https://github.com/NixOS/rfcs/pull/163

It implements a bit more than necessary, allowing an abstract service to potentially create multiple systemd services, if it seeks out options?systemd to figure out the kind of process manager it's loaded into.
I think that's nice functionality, but the proof of concept could be changed to something more restrictive if that's the direction you want to take. (ie don't define process-manager specific options; only read the data from the abstract service)
I can't spend much time on this at all, but I hope this gives some insight into what's possible with the module system.
Or maybe you can learn some useful techniques. This kind of module based infrastructure doesn't exist in NixOS yet. Closest thing would be flake-parts, for which I originally wrote types.deferredModule.
Anyway, a good starting point is the example directory. It's the closest thing to actual documentation.
(Again, sorry, proof of concept status, time, etc etc)
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Rendered docs

services.abstract

All services that are configured on the system.
Type:
lazy attribute set of (submodule)
Default:
{ }
Declared by:

<nixpkgs/nixos/modules/services/abstract/systemd.nix>

<nixpkgs/nixos/modules/services/abstract/generic.nix>

services.abstract.<name>.enable

Whether to enable the service. A service is enabled by default, because you took the effort to define its attribute.
Type:
boolean
Default:
true
Declared by:

<nixpkgs/nixos/modules/services/abstract/instance/generic.nix>

services.abstract.<name>.args

Arguments to pass to the foreground.process or daemon.process. In other words, these arguments are passed regardless of process manager choice.
Type:
list of (string or path convertible to it)
Default:
[ ]
Declared by:

<nixpkgs/nixos/modules/services/abstract/instance/generic.nix>

services.abstract.<name>.daemon.args

Arguments to pass to the daemon.process.
Type:
list of (string or path convertible to it)
Default:
config.args
Declared by:

<nixpkgs/nixos/modules/services/abstract/instance/generic.nix>

services.abstract.<name>.daemon.process

Path to an executable that launches a process in daemon mode.
Type:
string or path convertible to it
Default:
config.process
Declared by:

<nixpkgs/nixos/modules/services/abstract/instance/generic.nix>

services.abstract.<name>.foreground.args

Arguments to pass to the foreground.process.
Type:
list of (string or path convertible to it)
Default:
config.args
Declared by:

<nixpkgs/nixos/modules/services/abstract/instance/generic.nix>

services.abstract.<name>.foreground.process

Path to an executable that launches a process in foreground mode.
Type:
string or path convertible to it
Default:
config.process
Declared by:

<nixpkgs/nixos/modules/services/abstract/instance/generic.nix>

services.abstract.<name>.process

When this property is specified, it translates both to: foreground.process and daemon.process.
Type:
string or path convertible to it
Declared by:

<nixpkgs/nixos/modules/services/abstract/instance/generic.nix>

services.abstract.<name>.systemd.services

This module configures systemd services, with the notable difference that their unit names will be prefixed with the abstract service name.This option’s value is not suitable for reading, but you can define a module here that interacts with just the unit configuration in the host system configuration.
Type:
lazy attribute set of module
Declared by:

<nixpkgs/nixos/modules/services/abstract/instance/systemd.nix>

I can't spend much time on this at all

Unfortunately the devil really is in the details on these things; until you've built and booted a complete example it's impossible to know that you've solved (or even encountered!) all the hard problems.

Yes, it's only a proof of concept at this stage.
Some next steps could be

add more of the service properties
write a module for a process manager that isn't the NixOS systemd module
port a few services

Would you be interested to collaborate on this?

Renamed the pr: Abstract -> Portable.
It matches the RFC and is more accurate. These services are not abstract.
Layer feels a bit redundant to me. We don't need to think of parts of the NixOS option tree as layers, but it's not entirely wrong, in the sense that an evaluation order is implicit in the dependencies created by various option definitions (ie the expressions that are merged into the option value, and cause ordering by referencing config).
services.abstract also needs a rename. Not sure which

service (top level, singular): nice and simple, but perhaps easy to forget or mistype the s
services.portable: wrong in the sense that once the definitions have ended up there, they're not portable anymore; also part of the reason why abstract was wrong
serviceGroups: leaning into the fact that in this proof of concept, a Portable Service can define multiple daemons, units, etc.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/community-calendar/18589/99

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/announcing-services-flake/41338/13

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/portable-submodules/54109/5


Revert addition of p as alias for s gate on QuantumCircuit.

Summary
#3255 added qc.p as an alias for qc.s, but p is planned to be used in another context.

I'm fine with removing it, but I'm curious what the other planned use for it is

Not solidified yet, but more like an rz.


Allow installation of unreleased node versions?

what about giving nvm some sort of experimental pre-tag version installation ability?
for example, I know the branch hasn't been tagged yet for release but maybe we could add a step to compile and install like a 0.12.pre off github or something? maybe 0.12.pre-tag?

@ljharb given that io.js out, would it make sense to reconsider this?

I'd definitely like to support very-opt-in installation of release candidates - and then nightlies. However, this would primarily be useful for the node core team, and nobody else should really be doing it.

I'd definitely like to support very-opt-in installation of release candidates - and then nightlies. However, this would primarily be useful for the node core team, and nobody else should really be doing it.

I was asked just today by the Node team to try a nightly, which is how I found this bug ("Hey, I wonder if I can do this with nvm?"). I'm not a Node.js core team dev :)

@NuSkooler in that case you have the precise use case for why I eventually want to support nightlies :-)
The order things need to happen is:

support installing io.js from source (done except travis tests time out)
support installing node >= 4 from source (easy after 1)
support installing io.js rc's (almost done, but blocked by 1 and 2)
support installing node >= 4 rc's (easy after 3)
support installing nightlies of node >= 4 (blocked by 1-4)

@ljharb Sounds great. I just happened to fall into this situation over the last couple days so thought I'd chime in.

Looks like there's binary distributions of nightly builds: https://nodejs.org/download/nightly
So I was able to install latest v6 nightly with nvm with the following command:
NVM_NODEJS_ORG_MIRROR=https://nodejs.org/download/nightly nvm install 6

@valeriangalliat sure, that should work just fine right up until actual v6 comes out :-)

It doesn't seem to work in Windows 7. Any workarounds?

@puncha nvm should work on BashOnWindows. Otherwise, it currently does not support Windows at all - the readme lists windows alternatives.

@ljharb Oh, I forgot I'm using the nvm-windows which is a different repo. Thanks.

Hello guys, I tried to use the same trick with Node v8, and it didn't work (log output below). I think that NVM is trying to download the wrong file. Is there a way to point NVM to exact version that it should download and install?
NVM_NODEJS_ORG_MIRROR=https://nodejs.org/download/nightly nvm install 8
Downloading https://nodejs.org/download/nightly/v8.0.0/node-v8.0.0-darwin-x64.tar.gz...
######################################################################## 100.0%
WARNING: checksums are currently disabled for node.js v4.0 and later
tar: Unrecognized archive format
tar: Error exit delayed from previous errors.
Binary download failed, trying source.
######################################################################## 100.0%
Checksums empty
tar: Unrecognized archive format
tar: Error exit delayed from previous errors.
Binary download failed, trying source.
Installing node v1.0 and greater from source is not currently supported


Playwright see/grabNumberOfVisibleElements do not filter out elements with visibility:hidden css

What are you trying to achieve?
Playwright see/grabNumberOfVisibleElements should implement the visibility check as it is suggested in the library documentation https://playwright.dev/docs/actionability/#visible
Visible
Element is considered visible when it has non-empty bounding box and does not have visibility:hidden computed style. Note that elements of zero size or with display:none are not considered visible.

CodeceptJS Playwright helper doesn't take css into account:
  /**
   * {{> grabNumberOfVisibleElements }}
   *
   */
  async grabNumberOfVisibleElements(locator) {
    let els = await this._locate(locator);
    els = await Promise.all(els.map(el => el.boundingBox()));
    return els.filter(v => v).length;
  }

Provide test source code if related
on the page with one container visible

<!DOCTYPE html>

<meta http-equiv="content-type" content="text/html; charset=UTF-8">

hello

hello

playwright helper sees two visible elements (instead of one):
Scenario('Test numberOfVisibleElements', async ({ I }) => {
    await I.amOnPage("http://localhost:8080");
    await I.seeNumberOfVisibleElements('.container', 1);
})

Details

CodeceptJS version: 3.0.5
NodeJS Version:
Operating System:
puppeteer || webdriverio || protractor || testcafe version (if related)
Configuration file:

# paste config here

same applies to seeElement(x) and dontSeeElement(x)


Slow IntelliJ Idea import caused by long init script dependency timeouts

Expected Behavior
IntelliJ Idea doesn't have any serious performance degradation after upgrading gradle to next version.
Current Behavior
Gradle v. 6.1.1 works without this problem.
All gradle versions after try write the following line: Gradle: Download groovy-all-1.3-2.5.8.pom.... This line is appeared for 30 seconds for each subproject (looks like downloading stops after timeout of something like this), or sometimes it is visible forever (import should be cancelled, because IDE is looks like frozen).
Context
Computer has no access to the internet. All repositories are internal (Artifactory Proxy repositories are used too - both for plugins and normal dependencies). Probably (I'm not sure) Gradle inside IntelliJ Idea tries to download groovy-all from internet.
This issue is not dependent on IntelliJ Idea version. It is disappeared with Gradle version 6.1.1 or lower.
Console build works fine, no any delays are.
Steps to Reproduce
Just try to re-import valid gradle project into the IntelliJ Idea.
Your Environment
OS: Win 7 x64
JVM: v.11, Azul, x64
Gradle is used through wrapper. distributionUrl is like "https://internal-artifactory-server/proxy/gradle-6.2.2-all.zip". E.g. zip file is downloaded from Artifactory, not from Gradle web server.
Computer has no access to the interned. All repositories are internals (Artifactory Proxy repositories are used).
The same issue for IntelliJ Idea

The root cause: Gradle has too large download timeouts for init script dependencies.
What Gradle does:

The if we have init script (and IntelliJ Idea has it) - execute steps below
1.1. Download Groovy compiler, if init script ends with .gradle
1.2. If internet connection is broken - wait for 5-8 minutes (this is different from site to site) <-- this is the root cause, this is the essence of this issue
1.3. In case of connection failure - fallback to embedded Groovy compiler

Workaround:

Before init script applying (e.g. before importing into IntelliJ Idea) - define proxies at the gradle.properties
Run gradle with init scripts (in the other words: re-import gradle configuration into the IntelliJ Idea)
Comment proxies (because usually build agents doesn't have access to proxy)

@imanushin Oh boy, thank you, I was going nuts with this problem. I have a pretty powerful machine and Internet connection but the build was soooo slow, than I figured out by this issue that I was outside of the VPN.

Any chance you can share stack traces of what the daemon is doing when this happens?
There is exponential backof in Gradle dependency resolution, that is used to blacklist unreachable repositories. I wonder if your setup causes this to happen when everything is serial, meaning that you pay the maximum price.

I'm just coming across this problem for the first time having upgraded my version of Gradle.
Unfortunately, the workaround suggested above (configure proxy settings) doesn't make any difference for me. I can see that the proxy is set correctly and is being used by IntelliJ because I get this line of output.
> Task :prepareKotlinBuildScriptModel UP-TO-DATE Download https://services.gradle.org/distributions/gradle-7.6-src.zip succeeded, took 795 ms (44.78 MB)
But later on in the build when it tries to download the groovy libraries, I get the very long timeouts. The longest I've let it run before killing it is 1 hour 20 minutes.
I don't see any stacktraces in the daemon log. In fact, after it gets to the point where it is trying to download the groovy libraries I don't see any more output at all.
I'm happy to help try and diagnose the issue if I'm able to help.
Can you think of any other workaround in the meantime?
I'm using:

Gradle 7.4
OpenJDK 17.0.4
IntelliJ 2022.1

The fix with adding proxy settings to gradle.properties worked in my case, but I had lost 2 hours trying to find out what's the issue before I found this ticket :|

i suspect it is the behaviour of IDEA, it tries to download the groovy dependencies to inspect the gradle script, but i don't know what gradle tasks it executes, and the timeout config it is really long


Feat/contributor controller scoping

TDD on contributors controller scoping

Hey @mattwr18 and @roschaefer, I would like to have your opinion on some changes that are introduced in the branch:

To test the changes in the controller logic, I added specific matchers to the request specs (after aligning with @mattwr18 that that we want the changes to be tested as e2e as it makes sense)
I introduced a PORO data object for the existing index logic that could be alternatively or additionally be used to test against
I moved the contributors controller into the organizations module namespace (as this controller will only live underneath the organizations context)

It would be great if we could have a sync on these ideas and what are worth to carry on with when implementing the other needed changes.


TTL

How can we mention TTL of the object stored in Redis

How to pass it with the node-redis? It got closed but there is no answer in docs

@murbanowicz Nothing special - In the case of SET, each argument of the function maps to the argument in Redis. Otherwise, EXPIRE is a command in Redis that will set the TTL of any key.


Create API services

Use gin to create API services.
Note that we should keep in mind at the beginning to have swagger doc for each API: https://github.com/swaggo/gin-swagger

replaced by https://github.com/oam-dev/velacp/issues/7

replaced by https://github.com/oam-dev/velacp/issues/7


AB#24762: Adds Smaller Test Pipeline for (Policy/RBAC,MG,SubscriptionMove)

Overview/Summary
Allow ALZ-Bicep contributor to quickly validate the modules listed below by adding a specific PR comment:

Management group structure
Move subscription to management group
Custom roles
Custom policies definitions & sets
Policy assignments

Create smaller tests
This PR fixes/adds/changes/removes

Adds pipeline for AB#24762

Breaking Changes

No breaking changes as this is a brand new pipeline.

Testing Evidence
Tested pipeline logic within personal Azure tenant using hard-coded subscription values.

Update: Successfully tested in internal ALZ organization using variable group, test PR, and Subscription vending machine.

As part of this Pull Request I have

[x] Read the Contribution Guide and ensured this PR is compliant with the guide
[x] Ensured the resource API versions in .bicep file/s I am adding/editing are using the latest API version possible
[x] Checked for duplicate Pull Requests
[x] Associated it with relevant GitHub Issues
[x] (ALZ Bicep Core Team Only) Associated it with relevant ADO Items
[x] Ensured my code/branch is up-to-date with the latest changes in the main branch
[x] Performed testing and provided evidence.
[x] Updated one or more of the following tests (if required)

Unit
Linting
E2E (End-To-End)
ValidateAzCloud (Base validation in Azure Cloud)
ValidateMcCloud (Base validation in Azure China Cloud)

[x] Updated relevant and associated documentation (e.g. Contribution Guide, Module READMEs, Wiki Docs etc.)
[x] If relevant, created or updated Code Tours here

No longer needed.


Save stack compose without updating the stack

Is your feature request related to a problem? Please describe.
Often I modify a single service inside my stack (Env, Label, ...) and want to persist this change inside the stack's compose file, but I don't want to re-deploy the whole stack and restart all services.
Describe the solution you'd like
A simple "Save file" button next to the "Update the stack" button.
Describe alternatives you've considered
You can edit the file directly inside portainer's volume but via portainer's UI would be so much easier.
Additional context
Mockup:

Hi @gbhrdt
Updating a single service in the stack file andhitting update the stack should normally redeploy the updated service only and not all the services in the stack.
Based on this behavior, I'm not sure that this feature request is actually needed.

Anthony,
I have wished I could do that as well. Though it is more so I can stage a production change before the outage window and then just select the services during the outage window and update them.

@cyberlink1 how is it related to the ability to save a stack without deploying it? What prevents you from preparing the changes and using the "Update the stack" button during the outage window?

@deviantony You're totally right, the services are not all being restarted.
But there are still cases (like @cyberlink1 said) where you want to "prepare" changes to the stack file in portainer before updating the stack. I use the portainer compose editor heavily and sometimes I have stuff to change at the compose files (e.g. some new ENV vars) but don't want to restart the associated service. So what I miss is the ability to prepare those stack changes directly in portainer.

@cyberlink1 how is it related to the ability to save a stack without deploying it? What prevents you from preparing the changes and using the "Update the stack" button during the outage window?

Make the changes during the day at work, then shutdown the laptop and deploy the changes in the evening during the outage window. If you cant save it, it will not be there later.
Though thinking about this and mulling it over I wonder if it would be better to be able to save to and pull the stack yaml from a repo like gitlab. At least that way there would be a way to back them up should you also have the issue in #2731

Maybe related to https://github.com/portainer/portainer/issues/1753 instead of #2731 ?

Hi @gbhrdt
Updating a single service in the stack file and hitting update the stack should normally redeploy the updated service only and not all the services in the stack.
Based on this behavior, I'm not sure that this feature request is actually needed.

@deviantony I sometimes get further services updates when I change only one of them. Is there any chance that whitespaces or something could let Portainer think one service or another has changed when it actually hasn't?
Just asking, I will open a new issue if there's no reason for that to happen.

@deviantony but maybe that's only a frontend problem ("Last Update" showing that all services have been updated in the list), but not a backend one?

Would like to have this feature, too. My conrete use case is the following:

I wan't to update the label of one of my service. More concrete, I am using restic-compose-backup to backup my services and I want to change one of the labels which belongs to restic, e. g. adding restic-compose-backup.volumes: true
There is no technical reason to redeploy the service. I can simply add / edit / remove the label on the container during runtime
I would like to persist this new label in the compose stack

The current way to persist the changes is to edit the compose-file created by portainer manually.
Yes, I could do that within a maintenance window and simply redeploy the service. But its possible to prevent the downtime. And I dont have to get up early in the morning for those changes.

Adding on my two cents about this feature request. This missing functionality really surprised me. How can I stage changes to multiple stacks, but only commit them later when in a maintenance window? Sometimes it's just a small correction to the name of an output file, backup file, etc and I'm fine if it just gets picked up the next time the stack is restarted for another reason. I can't make a change, save it for later, and change another stack. I'm stuck on that Editor screen until I either abandon the changes or update the stack.
Same functionality as the button we already have but leaves out the step to update the affected services. Seems straightforward?

I'm a little sick about this... always copying/pasting/editing docker-compose settings and config in order to avoid to do all that during a maintenance window.
It is useful though to see the exact configuration actually running, so the original config should be visible elsewhere, while the one I see in the editor should be editable without beeing forced to restart everything.

Hi there,
To keep this open request alive: if I might add : it would be very nice if we could create "drafts" at some points without redeploying.
Quite frequently and especially during prep work, I would like to save some modifications without deploying and it's not possible.
So +1 for this functionality! 😉

Another reason why this would be good is for people who uses a compose set up where they also type in their username and password into the compose file. Being able to erase that part and save it as "changeme" or the like helps it not just sit there.

Also surprised this does not exist-  i was trying to build / setup a new docker environment (and this time use entertainer),  and didnt want to deploy yet.
also the specific app was setting up needed 2x separate docker-compose files, thus i wanted to save both, setup their proper environmental vars,  and  then when i was ready,  deploy them.  (but i dont see where that is possible in portainer)

Do I miss this feature in the GUI or isn't it in yet?

:+1:

Do I miss this feature in the GUI or isn't it in yet?

it still does not exist yet-  It's not clear why, but one still has to deploy or deploy anytime editing compose file in portainer.
(unfortunate in my opinion, and hopefully this will change) , If I had the coding skills to implement this I would issue a PR with changes.

plz take care on this topic. it ist very important to save changes without deploy immediately.
Sometimes changes are already made in the Docker and for documentation or later reinstall some kind of e.g. Environment variables are added, but no need to deploy, just saving would be enough!

Sometimes is useful to take a look at other stack files to copy some values from them or get a reference to be able to finish creating a new one, other times it could be useful to "inspect" the file to make sure the env vars I used were added properly. I currently cannot do so without losing my changes for the new stack file, it's odd that this functionality isn't there already considering that the files do get saved when deployed, it seems it's just a matter of providing a button that calls the "save file" function that should already exist.

+1

+1
We need to be able to stage changes ...
I am literally updating the stack to add a comment, so I do not really need any containers restarted.

+1 or simply add a toggle that exposs compose's --no-start  flag, to recreate the containers without starting them
I often make changes to containers that are not running (as I run them when they are needed) and it is annoying that they all start every time I have to update the stack

If it weren't for all the extra functionality in Portainer, I would be using Dockge for my homelab. Dockge doesn't have much for other docker-related features (networks, volumes, etc...) but you can save changes before deploying them. I'll reiterate some of the concerns listed here as they are important to me.
Sometimes, I need to refer to another stack for something. At that point, I have to open another Portainer tab in the browser to get to that info. Not a big deal, but a source of friction. Other times, I'm setting up a new stack and may need to stop to do something else. In Dockge, I'd hit save and come back later. With Portainer, I have to cut/paste to a text editor and save it somewhere I can get to it, possibly on a different device. May not sound like much but it happens to me a lot.
Sad that a feature request like this has sat for so many years...

I've just created this PR where the "save only" functionality is added. It's not polished, there are probably some validations to be made there but at least the "happy path" works. I'm open to addressing any missing pieces once I get some feedback from the maintainers.


Resources release

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.

adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

Hello @chenjianfei2017, I noticed there were some breaking change failures in your PR:
id: '1010',
code: 'AddingRequiredParameter',
message: "The required parameter 'sourceSubscriptionId' was added in the new version."

Could you please resolve them first?

Hello @chenjianfei2017, I noticed there were some breaking change failures in your PR:
id: '1010',
code: 'AddingRequiredParameter',
message: "The required parameter 'sourceSubscriptionId' was added in the new version."

Could you please resolve them first?

do you mean this breaking change:
[ChangeLog] Breaking changes
[ChangeLog]
[ChangeLog]   - Model AliasPathType no longer has parameter pattern
this breanking has been confirmed to merged into python sdk

Hello @chenjianfei2017, I noticed there were some breaking change failures in your PR:
id: '1010',
code: 'AddingRequiredParameter',
message: "The required parameter 'sourceSubscriptionId' was added in the new version."

Could you please resolve them first?

do you mean this breaking change:
[ChangeLog] Breaking changes
[ChangeLog]
[ChangeLog] - Model AliasPathType no longer has parameter pattern
this breanking has been confirmed to merged into python sdk

Oh, I mean there were check failures for your PR, one is related to "Breaking Change Failure":
{
    id: '1009',
    code: 'RemovedRequiredParameter',
    message: "The required parameter 'subscriptionId' was removed in the new version.",
    old: {},
    new: {},
    type: 'Error',
    docUrl: 'https://github.com/Azure/openapi-diff/tree/master/docs/rules/1009.md',
    mode: 'Removal'
  },
  {
    id: '1010',
    code: 'AddingRequiredParameter',
    message: "The required parameter 'sourceSubscriptionId' was added in the new version.",
    old: {},
    new: {},
    type: 'Error',
    docUrl: 'https://github.com/Azure/openapi-diff/tree/master/docs/rules/1010.md',
    mode: 'Addition'
  }

But I think you are resolving the duplicate "subscriptionId" ( "subscription_id1") issue, and this breaking change should be inevitable. Not sure if we can override this error or we can merge the pr with the failures.

Hello @chenjianfei2017, I noticed there were some breaking change failures in your PR:
id: '1010',
code: 'AddingRequiredParameter',
message: "The required parameter 'sourceSubscriptionId' was added in the new version."

Could you please resolve them first?

do you mean this breaking change:
[ChangeLog] Breaking changes
[ChangeLog]
[ChangeLog] - Model AliasPathType no longer has parameter pattern
this breanking has been confirmed to merged into python sdk

Oh, I mean there were check failures for your PR, one is related to "Breaking Change Failure":
{
    id: '1009',
    code: 'RemovedRequiredParameter',
    message: "The required parameter 'subscriptionId' was removed in the new version.",
    old: {},
    new: {},
    type: 'Error',
    docUrl: 'https://github.com/Azure/openapi-diff/tree/master/docs/rules/1009.md',
    mode: 'Removal'
  },
  {
    id: '1010',
    code: 'AddingRequiredParameter',
    message: "The required parameter 'sourceSubscriptionId' was added in the new version.",
    old: {},
    new: {},
    type: 'Error',
    docUrl: 'https://github.com/Azure/openapi-diff/tree/master/docs/rules/1010.md',
    mode: 'Addition'
  }

But I think you are resolving the duplicate "subscriptionId" ( "subscription_id1") issue, and this breaking change should be inevitable. Not sure if we can override this error or we can merge the pr with the failures.

Got it.
actually, i just want to confirm whether my change is corrent, since i noticed you submited the part which i changed today(i guess you own this service).
i am releasing python sdk of this RP, and found this problem
if you can confirm this change is correct, i think we can merge this pr

Hi @chenjianfei2017, the change looks good to me. @Tiano2017 is the code owner, and he can confirm.

Hi, @chenjianfei2017. The PR has be closed for a long time and it's related branch still exist. If no further used for over 14 days, I will delete this related branch. Please tell me if you still need this branch.

Hi, @chenjianfei2017. The PR has be closed for a long time and it's related branch still exist. Please tell me if you still need this branch or i will delete it in 14 days.

Hi, @chenjianfei2017. The PR has be closed for a long time and it's related branch still exist. Please tell me if you still need this branch or i will delete it in 14 days.

Hi, @chenjianfei2017. The PR has be closed for a long time and it's related branch still exist. Please tell me if you still need this branch or i will delete it in 14 days.


Security Compliance review of the use of Lambdas in the team toolkit

Describe the issue

There is an app that is already using lambdas and we wish to backfill the compliance and path forward for other teams to use it as part of their toolkit.

Which Sprint Goal is this issue related to?

Note: 'Milestone' is a ZenHub term that we use synonymously with 'Sprint'.

The 'Milestone' description (created in ZenHub) should clearly list Sprint Goals. This section should indicate which 'goal' this issue is related to.
Additional context

This work is only scoped to Lambda and Lambda  @ Edge and enclave
These are production app services
Is it Canada, how does it deal with data, no it's not in Canada, it's temporary processing (FOIPPA connection)

Definition of done

Meet with tech team to discuss (timeboxed to 30 min)
Discuss encrypted and non-encrypted (talk to Shea and Warren) (temp processing of data)
Check for regional usage
Check with Privacy
define the compliance (no pi/no business in non-Canadian region)
Ensure routing of distribution lists stays in Canada for the destination
Update SOAR/PIA if needed/applicable
Confirm expectation that lambda can be constrained to Canadian Region and that Lambda (a) Edge can be used in the global region as long as good patterns for using it and along with the anti-patterns to fail compliance are avoided.  Rationale to explain why this is ok because x, y, z (encryption, temporary processing setup, etc).
Written Process to handle non-region specific services that could be provided to Ministry Compliance and Teams to aid understand use cases & risks for onboarding/teams using the uses

705 is a duplicated. Closed 705, working on 761

#706 is a duplicate, closed 706 as complete. Working on 761

meeting w/AWS 04/09 for questions around controls

clarified cloudfront's distribution list: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/PriceClass.html

wrote cloud custodian controls to find all lambdas
working on documentation for good/bad patterns.

Spoke with PO and Scrum master on May 5th.
Broke the SoAR edits/approval piece into 861.
PO suggested to meet with tech team to advise on settings/configurations.
Booked meeting for next week.


optional original AST after error tokens, make defined work with typed args

closes #242
Similar to #221 except that untyped now acts the same as typed (which is now added), the original AST is at the start of the error tokens and not at the end, and only the errors described in #242 keep the original AST for now.
defined and for now declared manually strip all errors from the AST they receive and build strings from them, with defined now also supporting dotted identifiers. In the future declared could fully type its argument and check for specific errors instead of looking up an identifier based off of the raw AST.
AllowUndeclared is added that keeps identifier tokens as is instead of wrapping them in error tokens when they are undeclared. semCall uses this for the callee part so that we don't have to specifically strip undeclared identifier errors for now.
Unfortunately the code is not very pretty between the intermediate buffers/cursors and recursion in takeWithoutErrors/getDottedIdent, will apply any suggestions.

What's up with takeWithoutErrors? Just reprocess the resulting (err...) in the declared/defined logic, that's why we did it this way.

The (err) nodes are skipped while reading now (assuming they are not stacked like (err (err ...) ...)? if so isError needs to be a counter), for some reason I thought rebuilding it was the most general way of doing it.


Upgrade pandas version from 1.2.3

Describe the Task
Look into the problem of using a version of pandas other than 1.2.3.  Minna and Hank will run tests on pandas 1.5 and Venita will look into the problems with 1.4.  NCO indicated it would be possible and preferable to upgrade pandas to 1.5.x instead of downgrading to pandas 1.2.3.
Time Estimate
Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.
Sub-Issues
Consider breaking the task down into sub-issues.

[ ] Add a checkbox for each sub-issue here.

Relevant Deadlines
??
Funding Source
??
Define the Metadata
Assignee

[x] Select engineer(s) or no engineer required
[ ] Select scientist(s) or no scientist required

Labels

[x] Select component(s)
[x] Select priority
[x] Select requestor(s)

Projects and Milestone

[x] Select Repository and/or Organization level Project(s) or add alert: NEED PROJECT ASSIGNMENT label
[x] Select Milestone as the next official version or Future Versions

Define Related Issue(s)
Consider the impact to the other METplus components.

[ ] METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy

Task Checklist
See the METplus Workflow for details.

[ ] Complete the issue definition above, including the Time Estimate and Funding Source.
[ ] Fork this repository or create a branch of develop.
Branch name: feature_<Issue Number>_<Description>
[ ] Complete the development and test your changes.
[ ] Add/update log messages for easier debugging.
[ ] Add/update unit tests.
[ ] Add/update documentation.
[ ] Push local changes to GitHub.
[ ] Submit a pull request to merge into develop.
Pull request: feature <Issue Number> <Description>
[ ] Define the pull request metadata, as permissions allow.
Select: Reviewer(s) and Development issues
Select: Repository level development cycle Project for the next official release
Select: Milestone as the next official version
[ ] Iterate until the reviewer(s) accept and merge your changes.
[ ] Delete your fork or branch.
[ ] Close this issue.

Changes made to run METdbLoad with pandas 1.5.1


Add some organization to utils.py

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#941  👈
#940
main

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

Join @rohinb2 and the rest of your teammates on  Graphite

Merge activity

Jun 26, 3:33 PM EDT: @rohinb2 started a stack merge that includes this pull request via Graphite.


pip install deepspeed Assertion `err == hipSuccess' failed

(base) [sirus@serenitynow ~]$ pip install deepspeed
Defaulting to user installation because normal site-packages is not writeable
Collecting deepspeed
  Using cached deepspeed-0.9.3.tar.gz (807 kB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: -6
  ╰─> [1 lines of output]
      python: /usr/src/debug/hip-runtime-amd/hipamd-rocm-5.5.1/src/hip_platform.cpp:665: void PlatformState::init(): Assertion `err == hipSuccess' failed.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

(base) [sirus@serenitynow ~]$ rocminfo
ROCk module is loaded
=====================
HSA System Attributes
=====================
Runtime Version:         1.1
System Timestamp Freq.:  1000.000000MHz
Sig. Max Wait Duration:<PHONE_NUMBER>3709551615 (0xFFFFFFFFFFFFFFFF) (timestamp count)
Machine Model:           LARGE
System Endianness:       LITTLE

==========
HSA Agents
==========
*******
Agent 1
*******
  Name:                    AMD Ryzen Threadripper 2950X 16-Core Processor
  Uuid:                    CPU-XX
  Marketing Name:          AMD Ryzen Threadripper 2950X 16-Core Processor
  Vendor Name:             CPU
  Feature:                 None specified
  Profile:                 FULL_PROFILE
  Float Round Mode:        NEAR
  Max Queue Number:        0(0x0)
  Queue Min Size:          0(0x0)
  Queue Max Size:          0(0x0)
  Queue Type:              MULTI
  Node:                    0
  Device Type:             CPU
  Cache Info:
    L1:                      32768(0x8000) KB
  Chip ID:                 0(0x0)
  ASIC Revision:           0(0x0)
  Cacheline Size:          64(0x40)
  Max Clock Freq. (MHz):   3500
  BDFID:                   0
  Internal Node ID:        0
  Compute Unit:            32
  SIMDs per CU:            0
  Shader Engines:          0
  Shader Arrs. per Eng.:   0
  WatchPts on Addr. Ranges:1
  Features:                None
  Pool Info:
    Pool 1
      Segment:                 GLOBAL; FLAGS: FINE GRAINED
      Size:                    32723468(0x1f3520c) KB
      Allocatable:             TRUE
      Alloc Granule:           4KB
      Alloc Alignment:         4KB
      Accessible by all:       TRUE
    Pool 2
      Segment:                 GLOBAL; FLAGS: KERNARG, FINE GRAINED
      Size:                    32723468(0x1f3520c) KB
      Allocatable:             TRUE
      Alloc Granule:           4KB
      Alloc Alignment:         4KB
      Accessible by all:       TRUE
    Pool 3
      Segment:                 GLOBAL; FLAGS: COARSE GRAINED
      Size:                    32723468(0x1f3520c) KB
      Allocatable:             TRUE
      Alloc Granule:           4KB
      Alloc Alignment:         4KB
      Accessible by all:       TRUE
  ISA Info:
*******
Agent 2
*******
  Name:                    gfx1100
  Uuid:                    GPU-XX
  Marketing Name:          AMD Radeon RX 7900 XTX
  Vendor Name:             AMD
  Feature:                 KERNEL_DISPATCH
  Profile:                 BASE_PROFILE
  Float Round Mode:        NEAR
  Max Queue Number:        128(0x80)
  Queue Min Size:          64(0x40)
  Queue Max Size:          131072(0x20000)
  Queue Type:              MULTI
  Node:                    1
  Device Type:             GPU
  Cache Info:
    L1:                      32(0x20) KB
    L2:                      6144(0x1800) KB
    L3:                      98304(0x18000) KB
  Chip ID:                 29772(0x744c)
  ASIC Revision:           0(0x0)
  Cacheline Size:          64(0x40)
  Max Clock Freq. (MHz):   2304
  BDFID:                   3072
  Internal Node ID:        1
  Compute Unit:            96
  SIMDs per CU:            2
  Shader Engines:          12
  Shader Arrs. per Eng.:   2
  WatchPts on Addr. Ranges:4
  Features:                KERNEL_DISPATCH
  Fast F16 Operation:      TRUE
  Wavefront Size:          32(0x20)
  Workgroup Max Size:      1024(0x400)
  Workgroup Max Size per Dimension:
    x                        1024(0x400)
    y                        1024(0x400)
    z                        1024(0x400)
  Max Waves Per CU:        32(0x20)
  Max Work-item Per CU:    1024(0x400)
  Grid Max Size:<PHONE_NUMBER>(0xffffffff)
  Grid Max Size per Dimension:
    x<PHONE_NUMBER>(0xffffffff)
    y<PHONE_NUMBER>(0xffffffff)
    z<PHONE_NUMBER>(0xffffffff)
  Max fbarriers/Workgrp:   32
  Pool Info:
    Pool 1
      Segment:                 GLOBAL; FLAGS: COARSE GRAINED
      Size:                    25149440(0x17fc000) KB
      Allocatable:             TRUE
      Alloc Granule:           4KB
      Alloc Alignment:         4KB
      Accessible by all:       FALSE
    Pool 2
      Segment:                 GROUP
      Size:                    64(0x40) KB
      Allocatable:             FALSE
      Alloc Granule:           0KB
      Alloc Alignment:         0KB
      Accessible by all:       FALSE
  ISA Info:
    ISA 1
      Name:                    amdgcn-amd-amdhsa--gfx1100
      Machine Models:          HSA_MACHINE_MODEL_LARGE
      Profiles:                HSA_PROFILE_BASE
      Default Rounding Mode:   NEAR
      Default Rounding Mode:   NEAR
      Fast f16:                TRUE
      Workgroup Max Size:      1024(0x400)
      Workgroup Max Size per Dimension:
        x                        1024(0x400)
        y                        1024(0x400)
        z                        1024(0x400)
      Grid Max Size:<PHONE_NUMBER>(0xffffffff)
      Grid Max Size per Dimension:
        x<PHONE_NUMBER>(0xffffffff)
        y<PHONE_NUMBER>(0xffffffff)
        z<PHONE_NUMBER>(0xffffffff)
      FBarrier Max Size:       32
*******
Agent 3
*******
  Name:                    gfx1010
  Uuid:                    GPU-XX
  Marketing Name:          AMD Radeon RX 5700 XT
  Vendor Name:             AMD
  Feature:                 KERNEL_DISPATCH
  Profile:                 BASE_PROFILE
  Float Round Mode:        NEAR
  Max Queue Number:        128(0x80)
  Queue Min Size:          64(0x40)
  Queue Max Size:          131072(0x20000)
  Queue Type:              MULTI
  Node:                    2
  Device Type:             GPU
  Cache Info:
    L1:                      16(0x10) KB
    L2:                      4096(0x1000) KB
  Chip ID:                 29471(0x731f)
  ASIC Revision:           2(0x2)
  Cacheline Size:          64(0x40)
  Max Clock Freq. (MHz):   2100
  BDFID:                   3840
  Internal Node ID:        2
  Compute Unit:            40
  SIMDs per CU:            2
  Shader Engines:          4
  Shader Arrs. per Eng.:   2
  WatchPts on Addr. Ranges:4
  Features:                KERNEL_DISPATCH
  Fast F16 Operation:      TRUE
  Wavefront Size:          32(0x20)
  Workgroup Max Size:      1024(0x400)
  Workgroup Max Size per Dimension:
    x                        1024(0x400)
    y                        1024(0x400)
    z                        1024(0x400)
  Max Waves Per CU:        40(0x28)
  Max Work-item Per CU:    1280(0x500)
  Grid Max Size:<PHONE_NUMBER>(0xffffffff)
  Grid Max Size per Dimension:
    x<PHONE_NUMBER>(0xffffffff)
    y<PHONE_NUMBER>(0xffffffff)
    z<PHONE_NUMBER>(0xffffffff)
  Max fbarriers/Workgrp:   32
  Pool Info:
    Pool 1
      Segment:                 GLOBAL; FLAGS: COARSE GRAINED
      Size:                    8372224(0x7fc000) KB
      Allocatable:             TRUE
      Alloc Granule:           4KB
      Alloc Alignment:         4KB
      Accessible by all:       FALSE
    Pool 2
      Segment:                 GROUP
      Size:                    64(0x40) KB
      Allocatable:             FALSE
      Alloc Granule:           0KB
      Alloc Alignment:         0KB
      Accessible by all:       FALSE
  ISA Info:
    ISA 1
      Name:                    amdgcn-amd-amdhsa--gfx1010:xnack-
      Machine Models:          HSA_MACHINE_MODEL_LARGE
      Profiles:                HSA_PROFILE_BASE
      Default Rounding Mode:   NEAR
      Default Rounding Mode:   NEAR
      Fast f16:                TRUE
      Workgroup Max Size:      1024(0x400)
      Workgroup Max Size per Dimension:
        x                        1024(0x400)
        y                        1024(0x400)
        z                        1024(0x400)
      Grid Max Size:<PHONE_NUMBER>(0xffffffff)
      Grid Max Size per Dimension:
        x<PHONE_NUMBER>(0xffffffff)
        y<PHONE_NUMBER>(0xffffffff)
        z<PHONE_NUMBER>(0xffffffff)
      FBarrier Max Size:       32
*** Done ***
(base) [sirus@serenitynow ~]$

I have both a 5700xt and a 7900xtx. I will try the override shortly

I've been trying to build ROCM from source because for my 7900xtx it appears that gfx1100 has to be set as a compile target. once I do that ROCM should have support for both of my video cards. I don't know if I can use them both for rocm at the same time though. I'm also planning on moving my graphics cards from my current threadripper system to an epyc milan-x system, but I had to manually make PCI-E power cables and now I have to solder them on to my server's power distribution block because despite the high wattage this system wasn't meant for gpus. do you know if you can set two overrides like HSA_OVERRIDE_GFX_VERSION="10.3.0;11.10"


Does not open after update

After updating Atom to 1.6.0 , term3 refuses to open, either by using keys or from the menu.

I had the same problem. Today a red bug icon appeared in the atom statusbar for me. Clicking it opened a tab called Incompatible Packages that let me rebuild the native module for atom-term3. Now it works.
Looks like you can get there through the command palette as well: Incompatible Packages: View
I don't believe the red icon was present yesterday after I initially installed the package and it didn't work.

Thanks so much, that solved it.


add links to live benchmarks

what about a place for live benchmarks you can run against your current browser? for example, asm.js section could link to:
https://kripken.github.io/Massive/

this idea due to Martin Best

Would that fit in a "Samples" link?
@brendandahl what do you think about "more" links that can have a custom label?

Not sure how crowded we want to make the index page. If we do a page per feature we could add more links there.

Extended #88 to cover benchmarks as well.


Show browser and clicks when using BrowserWebDriverContainer

Hi,
I'm using BrowserWebDriverContainer with chrome driver. Is it possible to show browser and test's clicks?

Hi @meldmy
The getVncAddress() method on BrowserWebDriverContainer gives you a VNC URL through which you can watch (and interact with) the browser during the test run.
Note that using this URL is platform specific and depends on what VNC viewing tools are installed.
I hope this answers your question.
Richard


ANTLR grammar has an ambiguity

typeArgument: constexpression | Identifier ;

constexpression
    : literal
    | Identifier

The Identifier could be either the typeArgument or the constexpression

The solution is probably just to remove constexpression : Identifier because we don't have type variables in the language any more.


Added swipe to refresh to drawer

Closes #4018

After you fixed my workaround for manual refresh, I needed to come up with another solution :D
Some thoughts:

I think this will also work with the new MaterialDrawer library (at least they still use that layout in master)
The RelativeLayout that might look useless is necessary for the footer views (the library assumes it can assign RelativeLayout.LayoutParams and crashes without that RelativeLayout)
Would it be a good idea to also refresh the folder list here?

After you fixed my workaround for manual refresh, I needed to come up with another solution :D

I like it :smile:

Some thoughts:

I think this will also work with the new MaterialDrawer library (at least they still use that layout in master)

Thanks for checking :+1:

The RelativeLayout that might look useless is necessary for the footer views (the library assumes it can assign RelativeLayout.LayoutParams and crashes without that RelativeLayout)

Please add a comment to the layout stating that.

Would it be a good idea to also refresh the folder list here?

We should probably always refresh the folder list when checking mail for an account. This can be a different PR, though.
I think I'd like it better if the spinning progress indicator was displayed on top of the folder list. IMHO that makes it more obvious that only the currently selected account will be refreshed. It looks like swipeRefreshLayout.setProgressViewOffset() can be used for this.

Another thing: can you please rebase this branch on current master?

Thanks. I tweaked the swipe behavior a little bit.
We still need to figure out what to do when the account list is displayed. Disable swipe to refresh? Or check all accounts?
It also looks like we the code currently doesn't handle the Unified Inbox. The refresh listener isn't set when the Unified Inbox is selected.
Note to future self: I don't like that the drawer is interacting with MessagingController directly. Fix this eventually.

We still need to figure out what to do when the account list is displayed.

Just tell me what you prefer. I only use one account, so I never open the list or unified inbox.
Many users seem to be obsessed with the "Account overview" page. Maybe there could be an option (I know, options are not always a good thing) that opens the app in the account selector to please those users. In that case, refreshing all accounts with pull-to-refresh would probably be preferable.

I desire to have two email accounts configured in k-9, and want a page that shows unread in each, just like 5.600 does (semantically; I don't care much what it looks like).  I personally want both accounts use IMAP IDLE style push.   With swipe to refresh, I am assuming this is a "poll them now" command, similar to 5.600 refresh button, and I don't care if I push a button or swipe.   I also don't have a reason to want to check one and not the other, so if "check now" always checks all accounts, with no option to select which, that's ok.   I consider "check now" to be a workaround for network problems or push not working right.    In all of the above I think I'm pretty normal.

Then I guess we should refresh all accounts when the user swipes down while the account list is being displayed.

Nice. Thanks :+1:


Easiest Diabetes Classification

The dataset consists of 100+ patient records. Each record contains the following information:
Age: The patient's age, in years.
Gender: The patient's gender, male or female.
BMI: The patient's body mass index (BMI), a measure of weight relative to height.
Blood pressure: The patient's blood pressure, in mmHg.
FBS: The patient's fasting blood sugar, in mg/dL.
HbA1c: The patient's hemoglobin A1c, a measure of blood sugar control over the past 3 months.
Family history of diabetes: Whether the patient has a family history of diabetes.
Smoking: Whether the patient smokes.
Diet: Whether the patient has a poor or healthy diet.
Exercise: Whether the patient exercises regularly.
Diagnosis: The patient's diagnosis, either diabetes or no diabetes.

hi @NisargPipaliya
I would really like to work on this issue. Please assign this issue to me. I have worked on projects in the same field. I am a contributor of GSSOC'23.

@snehasingh3013 - we already have diabetes classification issue (#69). Hence, we will not be able to assign you the same.


Find an alternative to ZenHub to use as a kanban board for GitHub Issues.

Sent the founder of Codetree an email – will see if he responds.

Going to stick with ZenHub for now.


Python: planner love

Motivation and Context

Based on #5474 went into the using-the-planner notebook and made sure it works with the latest code.
Description

Moved all the planners to use '-' in line with the current work on new templates and planners, once that is in several extension classes can be changed.
Encountered several small bugs left over from changes over the last months.
Got through the whole notebook with results.
Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[x] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

Python 3.8 Test Coverage Report • FileStmtsMissCoverMissingsemantic_kernel   kernel.py3172891%195–199, 201–205, 207–211, 219–221, 240, 246, 248–252, 254–258, 260–265, 267, 312–316, 333–338, 345, 349–353, 366semantic_kernel/planners   basic_planner.py644825%19–21, 24, 135, 143–169, 181–204, 213–244   plan.py2344680%48, 151–155, 187, 202–212, 246, 250, 258–259, 269–272, 287, 292–295, 310, 313–318, 336, 341, 344, 346, 353, 366–368, 373–377semantic_kernel/planners/sequential_planner   sequential_planner.py66592%71, 75, 106, 125, 133   sequential_planner_extensions.py51982%28–29, 50, 101–115   sequential_planner_parser.py80396%29, 67, 88semantic_kernel/planners/stepwise_planner   stepwise_planner.py22213838%12, 96, 110–128, 137–206, 227–230, 238–249, 252, 260–275, 278–314, 317–345, 348–353, 356–368, 371–374, 387–399TOTAL522298581%
Python 3.8 Unit Test Overview

Tests
Skipped
Failures
Errors
Time

1131
11 :zzz:
0 :x:
0 :fire:
23.422s :stopwatch:


*: tiny clean up

exclude more directories to build smaller package
run clippy via cargo clippy instead, so we don't have "*" version in Cargo.toml, which is prohibited by crates.io

LGTM

CI failed @BusyJay


removed data files

Codecov Report

:exclamation: No coverage uploaded for pull request base (add-builtin-plugin@9dd5be7). Click here to learn what that means.
The diff coverage is n/a.

@@                  Coverage Diff                  @@
##             add-builtin-plugin     #348   +/-   ##
=====================================================
  Coverage                      ?   31.54%
=====================================================
  Files                         ?       14
  Lines                         ?      989
  Branches                      ?        0
=====================================================
  Hits                          ?      312
  Misses                        ?      626
  Partials                      ?       51

Continue to review full report at Codecov.

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


Repo sync for protected CLA branch

The pull request is created from master637719938126297743 to master to fix git push error for protected CLA branch

@opbld17 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Add predesigned pages

We need a possibility to add pages that are designed independently of the latex export.
(Let's call them "meta-pages" like: "About the Project" etc. but also the cover, imprint etc.)
I will provide them as PDF files.
Technical options

A: Split the LaTex export into single PDFs and join als PDFs together afterwards
B: Import premade PDF pages into the LaTeX project

Possible problems

Page numbers could pose a problem. We discussed that we could use the numbering only in the generated content. Option B might be the better solution in this case.

TOC: Do we want to have the meta pages in the TOC at all?

I opt for option B, using pdfpages. They even have an option to include the pages into the TOC!

Sounds perfect!

Will provide example PDF

example pdf file with trim.
mfnf_example_import_wtrim.pdf

I have included the examples in 2e8f9c2. @elbotho please have a look, the included pages to not really fit our geometry.
Note that you will only see the first page of the included PDF repeated. This is because of \usepackage[Export]{adjustbox}. The issue is known, see stackoverflow. @kulla you have added the use of that package in 425d9ae67c7ebc784c6b63c223df88836ebf2a43. Is it possible to modify your code like in the linked article?

@Lodifice As mentioned they include trim(3mm) on all sides and therefore result in a different format. The white borders don't make sense to me.
Might be fixed with #99.

Second PDF mockup
mfnf_example_import_after.pdf
@Lodifice does your implementation depend on a fixed number of pages? Or does it add all the pages automatically?

Fixed the Export issue in 5a23d042d4a1e7102f59b5dc3997316965ae46b6.
As of 99d53265c44c2c3cd995b615ec0c3b06fcd828b4, there are two included PDFs in the predesigned_pages directory:

mfnf_prelude.pdf is inserted in the beginning, before title page and toc
mfnf_epilogue.pdf is inserted in the end, after the list of figures

@elbotho the number of pages is not relevant, all are inserted. The counting of the internal document starts afterwards. However, it does not seem possible to add the epilogue to the toc (at least I can't get it to work).

👍  looks good to me!
will open new issue if we need another insert / changes.


is there a tutorial ? I get the following message. how to configure it ?

Message: Request textDocument/completion failed with message: Cannot read property 'fileTree' of undefined  Code: -32603

Hi. For basic use there's not really any need for configuration. You just open a .robot file and should be good to go. Could you provide the steps to reproduce the error you got? I.e. the command you did and on what file.

just input anything. then get the error message.  below is the screent shot.

Seems the extension didn't work that well opening a single file instead of a folder. That should be fixed in the newly released 0.8.1 version.
The extension itself doesn't necessarily require any configuration. You can see the supported features in the README.md. If you're looking for how to use Robot Framework, you can check its website here.


Too much recursion

I've got Ember model category:
// pseudocode
category-model {
  parent: belongsTo('category', { inverse: 'children' }),
  children: hasMany('category', { inverse: 'parent' }),
}

I've created a similar mirage model for it, and then in mirage factory
// pseudocode
category-factory {
  parent: association()
}

As soon as I added association() I got error too much recursion.
How should I define such relationship in Ember Mirage?

@ioleo The problem is if you use association() on the root of your factory, every category that gets created will try to create a parent category, ad infinitum.
One solution is to put the association under a trait:
Factory.extend({

  withParent: trait({
    parent: association()
  })

})

That way you can call server.create('category', 'withParent'), and only the top-level category will get its parent created.
The other is to just create the parent manually:
let parent = server.create('category');
let child = server.create('category', { parent });

Make sense?

@samselikoff Thanks, it does make sense indeed.


Something wrong in data_process.sh

Thank you for your CONTRIBUTION!!!
I encountered an Error when i ran "CUDA_VISIBLE_DEVICES=0 data_gen/nerf/process_data.sh $VIDEO_ID":
……
processed parsing 5800
processed parsing 5900
processed parsing 6000
--- Step 4: extract background image ---
1400 2.6689155101776123 -7.109971523284912
1500 2.680889129638672 -7.723774433135986
1600 2.6866374015808105 -8.287768363952637
find best focal 1400
2.7772014141082764 -7.718302249908447
Traceback (most recent call last):
File "data_util/face_tracking/face_tracker.py", line 219, in
render_imgs = renderer(rott_geo.to(device_render),
File "/home/gammalab/anaconda3/envs/geneface/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
result = self.forward(*input, **kwargs)
File "/home/gammalab/CS/TalkingHeadGeneration/GeneFace/data_util/face_tracking/render_3dmm.py", line 189, in forward
rendered_img = self.renderer(mesh)
File "/home/gammalab/anaconda3/envs/geneface/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
result = self.forward(*input, **kwargs)
File "/home/gammalab/anaconda3/envs/geneface/lib/python3.8/site-packages/pytorch3d/renderer/mesh/renderer.py", line 56, in forward
images = self.shader(fragments, meshes_world, **kwargs)
File "/home/gammalab/anaconda3/envs/geneface/lib/python3.8/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
result = self.forward(*input, **kwargs)
File "/home/gammalab/CS/TalkingHeadGeneration/GeneFace/data_util/face_tracking/render_3dmm.py", line 74, in forward
images = softmax_rgb_blend(
File "/home/gammalab/anaconda3/envs/geneface/lib/python3.8/site-packages/pytorch3d/renderer/blending.py", line 188, in softmax_rgb_blend
z_inv = (zfar - fragments.zbuf) / (zfar - znear) * mask
RuntimeError: The size of tensor a (50) must match the size of tensor b (2) at non-singleton dimension 3

Hello,
I have not encountered this bug yet. It seems something gets wrong when executing the step 6 in process_data.sh, in which the code tries to extract 3D head poses from each video frame. Maybe you can try two ways:

Try processing another video such as May.mp4, to figure out whether it is the problem raised by your own target video.
If so, it might be something wrong (such as in some frames the head is missing, or hard to calculate the head pose) with your target video, and you need to process it with an external video editor (such as Adobe Premiere).

I will stay tuned for this issue. And if there are any new findings, please let me know!

Hello,
I have not encountered this bug yet. It seems something gets wrong when executing the step 6 in process_data.sh, in which the code tries to extract 3D head poses from each video frame. Maybe you can try two ways:

Try processing another video such as May.mp4, to figure out whether it is the problem raised by your own target video.
If so, it might be something wrong (such as in some frames the head is missing, or hard to calculate the head pose) with your target video, and you need to process it with an external video editor (such as Adobe Premiere).

I will stay tuned for this issue. And if there are any new findings, please let me know!

I find this error always happening after "find best focal 1400", I'm going to check details about this.

Maybe this problem is caused by pytorch3d. My pytorch3d version is 0.4.0, it would lead to this error, and it can be solved with version 0.6.2.
Or solution can be found in https://github.com/facebookresearch/pytorch3d/issues/652

Thanks for pointing out that, I will update this pytorch3d version requirement in the next commit.


Binary Search implementation is C needed to be added

We have an implementation of BST in C language but you can implement it in any other language.


Add docker based cluster quick start method

Besides the vagrant and bare metal setup, this will give new users a quick try.
Many teams show interests with this setup, might be good idea to put here.
Signed-off-by: Baohua Yang<EMAIL_ADDRESS>

I've seen a couple people creating docker images which is awesome. As these are not official or maintained by the Hyperledger Project, I think it would be best to keep a list in the wiki. Thoughts?
I've created a page at https://github.com/hyperledger/fabric/wiki/Docker-Images. I think it makes sense to move most of your proposed text to this page and add a link in the README. This will allow others to post their own docker images without filling up the README.

@srderson that's a good thought, but I think we want to provide for their development and evolution under the terms of the hyperledger project governance (apache licensing etc). Further, I think that this could also lead to different deployment options. I guess we could treat like StackForge or cloudfoundry-community, but again those are separate and not under the formal governance of the main project.

@christo4ferris Agreed, I'd like to see these images, tools, etc. have a path to be included officially included in Hyperledger. The wiki feels less formal to me so I thought it may be a good starting point for people to link to contributions currently residing in their personal repositories. I'm open to linking to these in the README or wiki though, whatever makes sense for Hyperledger.

@srderson @christo4ferris
Thanks for the comments!
That makes sense to me, I will close this pr first.
Thanks!


Updated CI stuffs

Updated Danger and CircleCI

Current coverage is 62.85% (diff: 100%)

Merging #80 into master will not change coverage

@@             master        #80   diff @@
==========================================
  Files            31         31
  Lines          1268       1268
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            797        797
  Misses          471        471
  Partials          0          0

Powered by Codecov. Last update dcfcab9...bb75871


⚠ Bio Links has degraded performance

In 5a4434a, Bio Links (https://bio.rheinklang.events/links) experienced degraded performance:

HTTP code: 200
Response time: 2379 ms

Resolved: Bio Links performance has improved in c1a66b2 after 12 minutes.