YOLOv7 convert fail

Hi, Im faced with such a problem when trying to convert yolo.onnx model its process failed.
OS: Linux 20.4
architecture: x86_64
Here is code:
from rknn.api import RKNN

rknn = RKNN(verbose=True, verbose_file="./verbose_log")

ret = rknn.config(target_platform='rk3588')
if ret != 0:
    print('config failed')
    exit(ret)

ret = rknn.load_onnx(model="yolov7-ort-tiny.onnx")

if ret != 0:
    print("load failed")
    exit(ret)

ret = rknn.build(do_quantization=True)

if ret !=0:
    print("build failed")
    exit(ret)

name = "_quantized_rknn"
ret = rknn.export_rknn("yolov7_rknn.rknn")
if ret != 0:
    print("export failed!")
    exit(ret)

And here is output:
W __init__: rknn-toolkit2 version: 1.4.0-22dcfef4
I Save log info to: ./verbose_log
W load_onnx: The config.mean_values is None, zeros will be set for input 0!
W load_onnx: The config.std_values is None, ones will be set for input 0!
I base_optimize ...
I base_optimize done.
I
I fold_constant ...
E build: The input 0 of NonMaxSuppression('NonMaxSuppression_205') need to be constant! It will cause the graph to be a dynamic graph!
W build: ===================== WARN(3) =====================
E rknn-toolkit2 version: 1.4.0-22dcfef4
E build: Catch exception when building RKNN model!
E build: Traceback (most recent call last):
E build:   File "rknn/api/rknn_base.py", line 1541, in rknn.api.rknn_base.RKNNBase.build
E build:   File "rknn/api/graph_optimizer.py", line 567, in rknn.api.graph_optimizer.GraphOptimizer.fold_constant
E build:   File "rknn/api/graph_optimizer.py", line 323, in rknn.api.graph_optimizer._dynamic_check
E build:   File "rknn/api/rknn_log.py", line 113, in rknn.api.rknn_log.RKNNLog.e
E build: ValueError: The input 0 of NonMaxSuppression('NonMaxSuppression_205') need to be constant! It will cause the graph to be a dynamic graph!
build failed

Process finished with exit code 255

I observe the same problem. Does anyone know any workarounds?

I think you should remove the NMS layer from the model graph, this worked for me with another model.

I removed NMS layers from the YOLOv7 network, and it no longer has this error. However, it has another floating point exception (core dumped) error at the end of converting. anyone has any clues?

have you managed to resolve this?

any update this problem ? we have face the same error when using Yolov5

Has this problem been solved? I'm having the same problem with YOLOE.


Secret logistics for RDS

Currently Orthweb generates DB secret and stores it to Secret Manager in AWS.
Secret Manager is more expensive than Secure string in System Manager Parameter store

If continue using Secret Manager, it should be rotated and update to Docker compose
If secret is intended to be static, use Parameter store instead.

there's no elegant way to rotate secret and update a file in EC2.
there is only one secret in this deployment, and the cost isn't significant.


Improve unit test

Summary
I noticed that the VQE instance in a unit test seemed to be passed an estimator twice. The latter parameter named estimator was however an optimizer from the ddt data. Given it's confusing I changed the parameter name as well as the test case name which maybe more what it was in the past but is rather out of date now/
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
6452

Relevant Lines:
7127

💛  - Coveralls


Merge fastchat Conversation‘s stop words/tokens to OpenAI API server.

Many models, such as Yi-34B, Baichuan2, etc., have their own special tokens as part of the Chat template, and these tokens need to be used as default stop words.

Please see: https://github.com/vllm-project/vllm/pull/1756 which totally replaces this implementation.

Closing as superseded by #1756


It is a calculator for the Sprig.
How to play your game?
WASD to Move Cursor
K to Select
L to Solve
I for Backspace
J to Clear Screen

Code
Check off the items that are true.

[x] The game was made using the Sprig editor.
[x] The game is placed in the in the /games directory.
[x] The code is significantly different from all other games in the Sprig gallery (except for games labeled "demo").
[x] The game runs without errors.
[x] The name of the file/game contains only alphanumeric characters, -s, or _s.
[x] The game name is not the same as the others from gallery

Image (If an image is used)

[x] The image is in the /games/img directory.
[x] The name of the image matches the name of your file.

Thanks for PR!

It does work with a second input like the other operations.  I'm assuming you thought the radical button was square root? It is supposed to be the nth root. For example, you can input 512 and click the "√" (Radical Button), and then select 3, it will return 8, because the cube root of 512 is 8. You can also do square roots, 4th roots and so on. I also tried to draw an x above the root symbol to show that the user could input any number.

It does work with a second input like the other operations. I'm assuming you thought the radical button was square root? It is supposed to be the nth root. For example, you can input 512 and click the "√" (Radical Button), and then select 3, it will return 8, because the cube root of 512 is 8. You can also do square roots, 4th roots and so on. I also tried to draw an x above the root symbol to show that the user could input any number.

ooohhh right!

https://github.com/hackclub/sprig/commit/0f27e075a77e2b74bc7660b07f0bc354af2e91c6


Update README

Codecov Report

Merging #2 (6816397) into main (2dfbf4b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #2   +/-   ##
=======================================
  Coverage   94.87%   94.87%
=======================================
  Files           1        1
  Lines          39       39
=======================================
  Hits           37       37
  Misses          2        2

Flag
Coverage Δ

unittests
94.87% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


v3.20.1 mouse click

there is a bug：when i click the map twice, the map will moved fellow my mouse move, and the console get an error

otherwise, i try other version, only the v3.13.1 is not this problem

Can you provide a working JSFiddle or a link to an official example, along with information on which browser and device you are using, so others can reproduce the issue?

I think this is because mouseclick start moving the map from this version, another strange behavior i noticed on simple click is that the view trigger a center change event
look at this jsfiddle:
Step to reproduce:

Click on the map
change:center is called but center didn't change.

https://jsfiddle.net/qs7y5f8s/2/
Ps: didn't have this event handler with < 3.19.1
don't know about 3.20.0 , i jumped from 3.19.1 to 3.20.1

the center change is definitely an issue, from 3.20. You can reproduce this on examples, such as simple example, and do map.getView().on('change:center', function(evt){console.log(evt)}), and single click fires event.
I can't reproduce the reported issue though.

I cannot reproduce the reported issue either.

ps: my jsfiddle will not reproduce the reported issue, it just show the "change:center" event triggered by just clicking on the map:
With ol.3.19.1: click on map (without dragging) doesn't trigger changer:center event
https://jsfiddle.net/Lak07nwo/1/
With ol.3.20.1: click on map (without dragging) trigger changer:center event
https://jsfiddle.net/qs7y5f8s/2/

@DavidHequet Then maybe you should report the issue shown in your fiddle in a separate ticket? Also, what makes you think that the unconfirmed issue is caused by the one shown in your fiddle?


Merge master back into swift_2.0

Conflicts:

.travis.yml
Resolved by choosing the version from the swift_2.0 branch that requires the
xcode7 build environment.

Classes/DDFileLogger.h
Resolved by choosing the changes from 58ae948 by sinoru over changes from
b765caf by stephencelis.
See discussion on issue #592

Lumberjack.xcodeproj/project.pbxproj
Resolved by choosing the version from the swift_2.0 branch and manually
redoing what was done in 9f41918.
Since it was branched off master, there have been three new commits modifying
the project file:

f1cd4b8 Make CocoaLumberjackSwift-iOS Target depend on CocoaLumberjack-iOS
Similar change was done when re-adding CocoaLumberjackSwift-iOS
target again (after it had been removed) in fa57e49

9f41918 Mark CocoaLumberjack dynamic libraries as Require Only App-Extension-Safe API
Manually applied changes again in GUI after choosing project file from
swift_2.0 branch. Switched the 'Require Only App-Extension-Safe API' to
'Yes' on CocoaLumberjack, CocoaLumberjackSwift, CocoaLumberjack-iOS and
CocoaLumberjackSwift-iOS targets.
CocoaLumberjack(Swift)-watchOS targets already had this option set.

96b1dfd Silence the Xcode 7 upgrade check.
Similar change was done in aee07079

CI checks fixed in #615
On my fork, there is a fixbuilderrors_swift_2.0 branch, that contains timbodeit:swift_2.0 plus the two commits from #615
This branch builds successfully on travis

I think it's good to re-add NS_DESIGNATED_INITIALIZERs reference on #592

I think this is something we can merge and work on top of.


new CLI structure

@sayakpaul
Currently, as we add more steps, the number of argument of CLI grows so big. I think this is not a good thing in the DX/UX perspective. Hence, I want to discuss about making changes in the following manner:
provide separate CLI script for each step.

for instance, run python batch_inference.py --options for batch inference, run python eval.py --options for evaluation, and etc.,

then provide a entry_point.py that automatically selects which script to run based on --step option. For instance, when --step is setp to eval, all other options will be passed down to the eval.py script. But this is just a little enhancement for the users, so this is optional. we can choose.

We could configure YAML config parsing and provide separate configurations for each step. I think that might be easier.

And yes, providing separate CLI script for each step is definitely better and more robust.

We could configure YAML config parsing and provide separate configurations for each step. I think that might be easier.

This was something that I had in mind too.
Like, we have separate config files for each step, then just feed them in for each step, right?

Yup.


add example about the localization of eigenvectors

Travis broken as https://downloads.skewed.de/apt doesn't provide graph-tool packages for Xenial or Trusty anymore. Will be fixed later.


Added Sqoop option for direct mode to API

Adding this option will enable Sqoop to use native database features for importing or exporting data, if they are available.

I am guessing you will need to update the sbt file

@stephanh Have updated the comment

@sibisasidharan I have updated the sbt script on master so your build should now pass. Can you please rebase onto master and update the branch.

@stephanh I have updated the branch. Is this good to merge.

:+1: when you merge it please don't use the merge button but instead do a fast forward merge locally and push it to master.

@stephanh I believe I don't have write permission on the repo. Will I need to be part of 'Omnia Engineering' team to do so.

Done


Cow: Watch +91-9105056999

Cow requests the watch of the watch_number +91-9105056999. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by Makyen in Charcoal HQ


.p12 service account keys PyOpenSSL errors

Hi, I've been trying to set this up and have been unsuccessful for several hours now. I've followed the documentation exactly like this:
# Setup gcloud CLI
      - uses: GoogleCloudPlatform/github-actions/setup-gcloud@master
        with:
          version: '275.0.0'
          service_account_email: ${{ secrets.SA_EMAIL }}
          service_account_key: ${{ secrets.GOOGLE_APPLICATION_CREDENTIALS}}

Where the two secrets are provided in the environment using GitHub Secrets and the GOOGLE_APPLICATION_CREDENTIALS is the base64 encoding of the JSON secret key created for the service account. The service account is activated and I believe it has the right permissions, but the actions workflow fails every time with:
/bin/tar xz -C /home/runner/work/_temp/d808259f-fc3f-4628-8c8f-d8d611055a81 -f /home/runner/work/_temp/097fc0ed-8610-4d65-8481-6ae4de38eb3b
gcloud auth activate-service-account $GOOGLE_SERVICE_ACCOUNT_EMAIL --key-file=/tmp/tmp-7195qsuIHwy3Vvhx
WARNING: .p12 service account keys are not recomended unless it is necessary for backwards compatability. Please switch to a newer .json service account key for this account.
ERROR: (gcloud.auth.activate-service-account) PyOpenSSL is not available. If you have already installed PyOpenSSL, you will need to enable site packages by setting the environment variable CLOUDSDK_PYTHON_SITEPACKAGES to 1. If that does not work, see https://developers.google.com/cloud/sdk/crypto for details or consider using .json private key instead.
##[error]The process 'gcloud' failed with exit code 1

I've even tried installing PyOpenSSL but got the same error. I've also looked at the other 2 or 3 closed issues here with similar errors but didn't find any solution yet.
I'm not sure if I missed some documentation steps, but I am really at a dead-end to figure out what I am missing. Thanks for any advice you may have!

Hi @bonham000 thanks for reaching out. Please take a look at our documentation regarding the action's inputs: https://github.com/GoogleCloudPlatform/github-actions/tree/master/setup-gcloud#inputs
Specifically, make sure your SA Key is base64 encoded. Let me know if that helps.

It definitely is, I figured it out. In the env setup in GitHub Actions you cannot reference environment variables, you have to reference secrets directly. For instance
env:
   service_account_key: $GOOGLE_SERVICE_ACCOUNT_KEY

Will not work but
env:

env:
service_account_key: ${{ secrets.GOOGLE_SERVICE_ACCOUNT_KEY }}

Will work.

If anyone else runs into similar problems, I found [this article](https://medium.com/better-programming/publish-your-cloud-run-app-with-github-actions-6c18ff5c5ee4) which provides a great walkthrough for the entire setup process.


Improvements to OSL tangent frame

Generate normalized tangent and bitangent vectors in vanilla OSL.
Generate custom tangent and bitangent vectors for the parametric sphere in testrender, aligning them with Lengyel/Mikkelsen conventions for a polygonal sphere.
Add a reference quality option for render tests.

Here are a few comparisons of GLSL and OSL renders with the latest code:
Standard Surface Tiled Brass (GLSL vs. OSL):

Standard Surface Procedural Brick (GLSL vs. OSL):

Standard Surface Brushed Metal (GLSL vs. OSL):


gffread should not have a namespace

The gffread component has a namespace gffread configured and this should not be the case.
This makes sense only for tools that have multiple subcommands.

Just fixed this in PR #52, thank you for noticing!


Handling of write_tab, checking if self.write_tab is False before deciding how to handle the tab key.

Addressing #8107

Maintainer merge checklist

[X] Title is descriptive/clear for inclusion in release notes.
[ ] Applied a Component: xxx label.
[ ] Applied the api-deprecation or api-break label.
[ ] Applied the release-highlight label to be highlighted in release notes.
[ ] Added to the milestone version it was merged into.
[ ] Unittests are included in PR.
[ ] Properly documented, including versionadded, versionchanged as needed.

This modified version of the keyboard_on_key_down method checks if self.write_tab is False before deciding how to handle the "tab" key. If self.write_tab is False, it manually inserts a tab character ('\t') into the text input. Otherwise, it continues with the original behavior where the "tab" key moves the focus to the next widget.

Hey @misl6! How are you doing? If you have some spare time, would you mind reviewing this PR?
Thanks in advance!

The write_tab is checked before hand in on_key_down. Do you have a issue that this is solving ?


Add support for environments

As of https://github.com/middleman/middleman/pull/1293/files middleman splits the notion of :mode and :environment. This PR updates middleman-blog to also handle this distinction.
This allows generation of blogposts using config for a particular environment using the --environment flag. e.g:
middleman article 'Awesome new post' --environment blog would look for config within the configure :blog do ... end block.
The main gotcha I see is that this requires Time.zone to be set in config.rb also. I wonder though if that is related to one of the various other date-related issues:
https://github.com/middleman/middleman-blog/issues/238, https://github.com/middleman/middleman-blog/issues/191, https://github.com/middleman/middleman-blog/issues/143
Additionally, the -e alias is already used for editing on this project, while for middleman itself, and other extensions, this is used for environment specification. I've left out that alias for now.

Hey @eellson 👋🏼 I'm helping to maintain this project now, could you please summarize why we need this feature?


GL ES 3.0 shader support

There is a trivial CI change that needs rebased

Some of the checks failed?


Support @const JSDoc tag

TypeScript Version: 2.5.3
Code
/**
 * @const {boolean} This constant is falsy
 */
export const MyFalsyConstant: boolean = false;

Expected behavior:
Type expression and comment should be separate for @const (http://usejsdoc.org/tags-constant.html) tags. See below for further explanation.
Actual behavior:
Parsing the above JSDoc (with help from tsutils which as far as I can see is just using Typescript parsing tools), I get the following node for the @const JSDoc tag.
NodeObject {
  pos: 1299,
  end: 1306,
  flags: 0,
  transformFlags: undefined,
  parent:
   NodeObject {
     pos: 1292,
     end: 1368,
     flags: 0,
     transformFlags: undefined,
     parent:
      NodeObject {
        pos: 1290,
        end: 1406,
        flags: 0,
        transformFlags: undefined,
        parent: [Object],
        kind: 208,
        decorators: undefined,
        modifiers: undefined,
        declarationList: [Object],
        jsDoc: [Object],
        _children: [Object] },
     kind: 275,
     tags: [ [Circular], [Object], pos: 1299, end: 1348 ],
     comment: undefined },
  kind: 276,
  atToken: TokenObject { pos: 1299, end: 1300, flags: 0, parent: undefined, kind: 57 },
  tagName:
   IdentifierObject {
     pos: 1300,
     end: 1305,
     flags: 0,
     parent: undefined,
     escapedText: 'const' },
  comment: '{false} This constant is falsy' }

Destructuring the relevant ts.JSDocTag object (const { typeExpression, comment } = tag), I get the following:
typeExpression: `undefined`
comment: `{false} This constant is falsy`

My expectation would be for the type expression to be separate as outlined in http://usejsdoc.org/tags-constant.html

PRs welcomed.

@mhegazy Maybe you want to add help wanted label to this issue (based on your previous comment).

I’d like to work on this.

has any progress been made on this issue? from what I can tell, it looks like #39768 was finished but closed.

This can be closed Typescript now Supports:
export const CBLErrorDomainByCode = /** @type {const} */ ([, "LITE_CORE","POSIX","SQLITE","FLEECE","NETWORK","WEB_SOCKET"]);

I don't think this is fixed - can we reopen, @RyanCavanaugh? #39768 was closed without being merged, and the example in the previous comment uses the @type tag, not the @const tag which this issue is referring to.

@bjarkler i guess there is no real implementation ongoing with the @const JSDoc tag what now works is the so called typecasting to const so the same as in typescript with as const

Note that the documentation for Typescript points to this issue as being open on this tag.


Improve resolver speed again

What does this PR try to resolve?
Follow-up of #14663 which has been splitted.
How should we test and review this PR?
Commit 1 enables the clippy::derive_ord_xor_partial_ord lint to be sure that Ord and PartialOrd are implemented correctly everywhere in the repository.
Commit 2 moves the ActivationKey type in core.
Commit 3 adds interning for the resolver activation keys so they can be used with nohash-hasher, decreasing resolving time by another 30%. This is possible since the interning is implemented with a static HashSet, so each interned element can be reduced to its address.
Performance comparison with the test added in the previous PR by setting LAST_CRATE_VERSION_COUNT = 100:

commit
duration

master
16s

with rustc-hash
6.7s

with nohash
4.6s

Firefox profiles, can be read with https://profiler.firefox.com:
perf.tar.gz
r? Eh2406

I benchmarked against an earlier version of this code. Running across all of crates.io (including solana)  went from 235.88min to 218.03min that is a solid 7.5% improvement. solana-transaction-status v1.3.10 improve the most going from 49.2s to 35.1s a 14s improvement! On the other hand solana-core v1.0.5 went from 99s to 114s that is 14s  worse. Here is the disaggregated data for crates that took >=0.02 to build.
sort_join.csv

I tested solana-core v1.0.5 on my machine, it resolves in exactly the same time before and after this PR.

Good to know! I will have to rerun when I get a chance. The most likely explanation is a random hiccup on my computer, that's pretty likely when carefully measuring time  of a process that runs for an hour.

I tested solana-core v1.0.5 on my machine, it resolved in exactly the same time before and after this PR.

The results are strange: I ran solana-core v1.0.5 on another machine where I can do a perf, and I observe a 30% improvement with this PR.

For solana-core v1.0.5, cargo spent more than 30s dropping the ResolverContext:
flamegraph.svg.tar.gz

A more targeted run, that  only looked at crates containing the word solana  went from 180.61min from master to 162.47min on this PR. With this run solana-core v1.0.5 went from 139s to 112s! So that one may have been a fluke on my part.
out_join.csv

I wanted to spend some time teasing apart exactly what part of the old hash was slow. The old hash but modified to hash the pointer of the InternedString instead of its contents got me 25% of the savings. It would be hard to believe that the SemverCompatibility is slow, it's basically two numbers. Hashing for SourceId is surprisingly complicated. (note to self, using SourceId::full_hash is fast but gets the wrong answer.) But I kept getting distracted. Not hashing the SourceId (with the InternedString fix) got about 80% of the savings. If keys only differ by their SourceId a hash map becomes O(n), but n is the number of packages with the same name and major version that only differ by source. Makes me wonder if hashing only by the pointer of the InternedString would also be effective.
With the holiday I will probably not work on this till Monday. Sorry for the delay.

I think we should also define a custom Hash for Dependency, as it is used in the conflict cache and hashing it amounts to 5-10% of the total resolving time.

So I was able to get about 50% of benefit was much less churn. I change the order so that we only do the Eq test for SourceId after the others are determined to be equal, and I overrode Hash to look at the InternedString address and not look at SourceId.
#[derive(Clone, PartialEq, Eq, Debug)]
pub struct ActivationsKey(InternedString, SemverCompatibility, SourceId);

impl std::hash::Hash for ActivationsKey {
    fn hash<H: std::hash::Hasher>(&self, state: &mut H) {
        std::ptr::NonNull::from(self.0.as_str()).hash(state);
        self.1.hash(state);
        // self.2.hash(state); // Packages that only differ by SourceId are rare enough to not be worth hashing
    }
}

So the other half the performance is because despite being interned SourceId::Eq is not a ptr::eq. Which in turn is because SourceIds concept of identity is a complete mess. The code relies on having to IDs that are Eq but do not have the same values for their fields.
So that leads to two questions about maintainability. Pinging @epage for strong and useful opinions about cleaning up our code base:

Any ideas about how to clean up the definition of "what is a SourceId" so that the structs we've defined actually match the semantics were using? The only thing I can think of is splitting it up into a CanonicalSource that just has the kind and canonical URL, and a SourceInfo that has the other fields. Then struct SourceId {canonical: &'static CanonicalSource, info: &'static SourceInfo}. Then EQ and fast_hash (a new method for us to use in ActivationsKey) can look at the ptr to canonical. But I'm open to other suggestions.
Is the remaining performance benefit worth merging this PR as is, specifically involving adding core::activation_key::ActivationKey with the bike shedding and documentation work? I'm leaning toward no for now. @x-hgg-x has come across a number of good leads for making resolution faster and we should reevaluate this after we followed up on those. Ed had some initial feedback in https://github.com/rust-lang/cargo/pull/14663, so I wanted his opinion here.

:umbrella: The latest upstream changes (presumably #14692) made this pull request unmergeable. Please resolve the merge conflicts.

If we can get the performance benefit without storing the activation key inside of a PackageId, we shouldn't.  The activation key is specific to the resolver and should be scoped to it.
If there are cheap things we can do, like re-order fields, that seems like an easy win.
Cleaning up SourceId would be nice and if it means we can then hash / eq on a cheaper value, then great!


feat: store previously-visited custom networks

High Level Overview of Change
Title says it all.
Context of Change
You don't need to keep entering the same URLs over and over again, there's a handy link.
Type of Change

[x] New feature (non-breaking change which adds functionality)

TypeScript/Hooks Update
N/A
Before / After
Custom Network Page
Before:

After:

Network Picker
Before:

After:

Test Plan
Works locally.

Should you be able to remove the custom networks on the homepage?

Should you be able to remove the custom networks on the homepage?

That wasn't part of the initial design, but I could add that if you want (replace the arrows with an X)

Should you be able to remove the custom networks on the homepage?

That wasn't part of the initial design, but I could add that if you want (replace the arrows with an X)
I think it is fine for now just something to consider.


add configuration value for sitemap.xml filename

resolves #8
I hope this is correct. This is the first python code that I wrote.

Sure, the new suggestion is better. I simply took the suggestion from the issue.

Ah, that makes sense :) It's merged now, I'll cut a release soon. Thanks again!


MM-47443 : Removed gobal state from 'status_actions.ts'

Summary
Removed global state from "status_actions.ts" in mattermost webapp.
Ticket Link
Fixes https://github.com/mattermost/mattermost-server/issues/21354
Jira https://mattermost.atlassian.net/browse/MM-47443
Release Note
NONE

Hello @codewithshariq,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.

@codewithshariq excellent work! Apologies if this wasn't clear in the ticket but we are also hoping to address the
state = getState() assignment which is passing the application state into the function. Here is an example of us doing it in actions/views/channel.js https://github.com/mattermost/mattermost-webapp/pull/4402/files#diff-92c78d8d4fa1772d360c0c76d8015539cb890a80eb98390a5e6514cb442b9dd7

To clarify, we want to only access the redux store from within actions using the provided getState function instead of by importing the store singleton from stores/redux_store directly like we do in some parts of this file.
As a more concrete example, we want to replace code that looks like
import store from 'stores/redux_store';

export function doSomethingBad() {
    const state = store.getState();
    store.dispatch({
        type: 'DO_SOMETHING',
        data: state.someValue,
    });
}

with code that looks like
export function doSomethingGood() {
    return (getState, dispatch) => {
        const state = getState();
        dispatch({
           type: 'DO_SOMETHING',
           data: state.someValue,
        });
    };
}

@codewithshariq  there are some conflicts with master, if you could please update your fork.

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/254171

E2E tests not automatically triggered, because the PR is not in a mergeable state. Please update the branch with the base branch and resolve outstanding conflicts.


pull request for e2e test at 11/23/2016 13:26:03

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


InspectSDFElement should allow duplicate plugin names

Environment

OS Version: Ubuntu 20.04
Source or binary build?
Binary: 9.6.1

Description

Expected behavior: Have multiple child elements with the same name should not produce an error if the element type is "plugin"
Actual behavior:
If an element in the SDF contains multiple child plugin elements with the same name:
The recursiveSameTypeUniqueNames function and the recursiveSiblingUniqueNames function in parser.cc (called by Gazebo) output an error message containing the entire element followed by the message

[Err] [Server.cc:98] SDF is not valid, see errors above. This can lead to an unexpected behaviour.

Model.cc also produces a warning:
Warning [Model.cc:212] Non-unique names detected in XML children of model with name[element_name]

Steps to reproduce

Define a model with a plugin in the definition. For example we have a buoy model (https://github.com/osrf/vrx/blob/master/vrx_gazebo/models/mb_marker_buoy_red/model.sdf) that uses an attached bouyancy plugin.
Define a nested model that uses several instances of the model you defined the previous step. For example, we have a nested model that arranges several of these buoys into a navigation course.
Launch Gazebo using a world that has the nested model in it.

Output
Using a version of the example above with only two buoys, we see:
Error: Non-unique names detected in type plugin in
<model name='short_navigation_course_0'>
  <frame name='red_bound_0::__model__' attached_to='red_bound_0::link'>
    <pose relative_to='__model__'>0 0 0 0 -0 0</pose>
  </frame>
  <link name='red_bound_0::link'>
    <inertial>
      <pose>0 0 -2 0 -0 0</pose>
      <mass>20</mass>
      <inertia>
        <ixx>1</ixx>
        <ixy>0</ixy>
        <ixz>0</ixz>
        <iyy>1</iyy>
        <iyz>0</iyz>
        <izz>0.1</izz>
      </inertia>
    </inertial>
    <collision name='collision_inner'>
      <pose>0 -0.02 0.02 0 -0 0</pose>
      <geometry>
        <cylinder>
          <radius>0.15</radius>
          <length>1.15</length>
        </cylinder>
      </geometry>
    </collision>
    <collision name='collision_outer'>
      <pose>0 0 -0.3 0 -0 0</pose>
      <geometry>
        <cylinder>
          <radius>0.325</radius>
          <length>0.1</length>
        </cylinder>
      </geometry>
    </collision>
    <visual name='visual'>
      <pose>0 0 0 1.57079 -0 0</pose>
      <geometry>
        <mesh>
          <uri>model://mb_marker_buoy_red/meshes/mb_marker_buoy.dae</uri>
        </mesh>
      </geometry>
      <material>
        <script>
          <uri>model://mb_marker_buoy_red/materials/scripts/mb_marker_buoy.material</uri>
          <name>mb_marker_buoy/Red</name>
        </script>
      </material>
    </visual>
    <pose relative_to='red_bound_0::__model__'>0 0 0 0 -0 0</pose>
  </link>
  <plugin name='BuoyancyPlugin' filename='libbuoyancy_gazebo_plugin.so'>
    <wave_model>ocean_waves</wave_model>
    <fluid_density>1000</fluid_density>
    <fluid_level>0.0</fluid_level>
    <linear_drag>25.0</linear_drag>
    <angular_drag>2.0</angular_drag>
    <buoyancy name='buoyancy_sphere'>
      <link_name>red_bound_0::link</link_name>
      <pose>0 0 -0.12 0 0 0</pose>
      <geometry>
        <sphere>
          <radius>0.325</radius>
        </sphere>
      </geometry>
    </buoyancy>
  </plugin>
  <frame name='green_bound_0::__model__' attached_to='green_bound_0::link'>
    <pose relative_to='__model__'>0 -20 0.2 0 -0 0</pose>
  </frame>
  <link name='green_bound_0::link'>
    <inertial>
      <pose>0 0 -2 0 -0 0</pose>
      <mass>20</mass>
      <inertia>
        <ixx>1</ixx>
        <ixy>0</ixy>
        <ixz>0</ixz>
        <iyy>1</iyy>
        <iyz>0</iyz>
        <izz>0.1</izz>
      </inertia>
    </inertial>
    <collision name='collision_inner'>
      <pose>0 -0.02 0.02 0 -0 0</pose>
      <geometry>
        <cylinder>
          <radius>0.15</radius>
          <length>1.15</length>
        </cylinder>
      </geometry>
    </collision>
    <collision name='collision_outer'>
      <pose>0 0 -0.3 0 -0 0</pose>
      <geometry>
        <cylinder>
          <radius>0.325</radius>
          <length>0.1</length>
        </cylinder>
      </geometry>
    </collision>
    <visual name='visual'>
      <pose>0 0 0 1.57079 -0 0</pose>
      <geometry>
        <mesh>
          <uri>model://mb_marker_buoy_red/meshes/mb_marker_buoy.dae</uri>
        </mesh>
      </geometry>
      <material>
        <script>
          <uri>file://media/materials/scripts/gazebo.material</uri>
          <name>Gazebo/White</name>
        </script>
      </material>
    </visual>
    <pose relative_to='green_bound_0::__model__'>0 0 0 0 -0 0</pose>
  </link>
  <plugin name='BuoyancyPlugin' filename='libbuoyancy_gazebo_plugin.so'>
    <wave_model>ocean_waves</wave_model>
    <fluid_density>1000</fluid_density>
    <fluid_level>0.0</fluid_level>
    <linear_drag>25.0</linear_drag>
    <angular_drag>2.0</angular_drag>
    <buoyancy name='buoyancy_sphere'>
      <link_name>green_bound_0::link</link_name>
      <pose>0 0 -0.12 0 0 0</pose>
      <geometry>
        <sphere>
          <radius>0.325</radius>
        </sphere>
      </geometry>
    </buoyancy>
  </plugin>
  <pose>-475 185 0 0 0 -2.14</pose>
</model>

[Err] [Server.cc:98] SDF is not valid, see errors above. This can lead to an unexpected behaviour.
Warning [Model.cc:212] Non-unique names detected in XML children of model with name[short_navigation_course_0].

Additional Notes
I haven't yet found documentation confirming that duplicate plugin names are allowed, but the comment on line 1476 of parser.cc in sdformat suggests this is the case.
Additionally, the sdformat implementation of the <include> tag does not rename plugins to avoid name conflicts, as it does with other elements, and plugin names also can't be overridden when a model is invoked. As illustrated in the above example, this means that whenever a model definition includes a plugin and that model is used more than once in a nested model, Gazebo will report that the SDF is invalid.

Here's the helper function that we use to detect if we have unique child names:
https://github.com/ignitionrobotics/sdformat/blob/sdf11/src/Element.cc#L825
So potentially, we could modify this function for ignoring plugins.

As of version 1.7 of SDFormat, all sibling elements must have unique names. It is absolutely necessary for frame semantics that sibling //model, //link, //joint, and //frame elements have unique names to avoid duplicate names in the frame graph, and we decided that the rule would be most clear if it applied to all sibling elements in a file. To comply with the specification, you may apply a different name to each plugin, perhaps incorporating the link name to which they correspond, such as redBuoyancyPlugin and greenBuoyancyPlugin.
If you think the specification is too restrictive, feel free to retitle this issue accordingly.

Thank you for this response. I don't feel the specification is too restrictive (I don't have an opinion either way), but I don't think it's possible to fix the problem by re-titling the plugin names as you suggest. The reason is that if I have a nested model that includes two red buoys (which is the case), I will still get the error unless there is some way to override the plugin name of the child model when including it into the parent model.
Put another way, if the policy is as you describe, it seems that the implementation of the "include" tag should rewrite the plugin names in the same way that it rewrites the link names. That would also resolve the issue.

Related: https://github.com/ignitionrobotics/sdformat/issues/294

Fixed in Fortress, needs backport to Citadel


Error while adding Integration

Hi, I get an error message while trying to ad Integration to HA.

Could you support?

Does it work now? It worked for me, but currently i get the error 403 (forbidden). Maybe refresh token problem.


Final design for tapeout

Final design for tapeout

Doesn't look like it is running the automated verification on this. I'm not sure what the issue is here.


"Javascript disabled" is not translated

Javascript is disabled.
JavaScript is required to use this site. Please enable JavaScript and reload.
https://github.com/cross-solution/YAWIK/blob/develop/module/Core/view/layout/_noscript-notice.phtml#L21-L22

the string will be translated, if the view contains

translate('JavaScript is required to use this site. Please enable JavaScript and reload.')?>

The translate() pattern will ensure, that the string will go to the transifex platform next time, we'll run bin/translate module/Core


Cannot use .sublime-project as project directory

If the project directory is set as "projects_path": ["SOMEPATH/.sublime-project"], then workspace files are created both in that directory and in ".sublime-workspace". Also if using ".sublime-projects", they are created in ".sublime-workspaces".
I think the problem is in pm.py line 268, where the replacement of ".sublime-project" with ".sublime-workspace" is applied to the whole path and not just to the extension.

should be fixed by  0b29413


docs(exec): exec options only work for v0.11+

Resolves #350
As far as I can tell, node v0.10 doesn't support many options to child_process.exec(). This doesn't really fix it, but it does document that these options don't work for that platform.
Whether or not we officially support v0.10 (currently we test against it for unit tests), there are still users out there using v0.10, and I'm sure some of them will still try to mix ShellJS with it. I think, since this is a known issue, it's worth documenting (since there's no good workaround). Most users won't be affected by it, and the few that are affected will be aware (and maybe switch to a newer version of node because of it).

I say just don't support v0.10. It's approaching EOL (In October), and it's a headache.
Alternatively, we could figure out a way to polyfill the options, and then say that we support all actively supported versions of node (As of right now, v0.10, v0.12, and v4).

I view these options as kind of an edge-use-case. Why drop support for all v0.10 users over this? If I were a v0.10 user, I'd rather see the one non-working feature documented, rather than just assume the whole thing doesn't work because package.json says so, or worse: assume everything works because I don't think to check which versions are in package.json.
An alternative would be to "officially" support v0.12+, declare this in our README, and to just also test against v0.10 to see if there are easy breaks that we can fix. And if we hit a huge number of unsupported features, we can consider dropping v0.10 early.
But I agree, once it hits EOL, let's drop it regardless. At that point, the new Ubuntu LTS will use node 4, so I think very few users will actually use v0.10.

@nfischer: npm does warn if the versions don't match, but I think we should officially support v0.12+, but test against v0.10.

I'll submit a PR to do that.

I'm fine with that. Either way, I think we should update the docs here and also at the top of the README, declaring what versions we officially support

@ariporad What do you think of this? Should we merge it in, or close this? Now that we only support v0.11+, this is probably less necessary. The pro is that v0.10 users won't have as many surprises. The con is that it clutters the docs a bit.

I'm going to vote :-1:, I think it's going to be confusing.


Change dependency from pycrypto

Is your feature request related to a problem? Please describe.
Pycrypto has not been maintained since 2014. So it susceptible to vulnerabilities like CVE-2013-7459 and CVE-2018-6594, and lacks some compatibility with the latest versions of python. Thus should not be in the tox file, documentation, etc.
Describe the solution you'd like
Replace pycrypto with an active, well-maintained python crypto library for development and testing
Describe alternatives you've considered
pycryptodome is "an almost drop-in replacement for the old PyCrypto library", but other libraries can still be considered.

Hi @alanyee,
I'm going to close this issue as pycrypto was removed in #799 .


Subdomain Takeover via CloudApp

Service name
CloudApp - getcloudapp.com
Proof

Documentation
1- There's no proof page, but the subdomain redirects you to getcloudapp.com.
2- The subdomain is usually called share or cloud.
Cheers

Hi,
How were you actually able to takeover? Doesn't it require the user to confirm the asset by uploading SSL certs?
Please do let me know.
Cheers!

@hussain0x3c, does it require a paid suscription?


Fix shutdown problem

FILL IN THE PR DESCRIPTION HERE
FIX #xxxx (link existing issues this PR will resolve)

I have tried to check if the python is during shutdown, but we need use sys.is_finalizing or sys.meta_path is None  and it will use sys, while sys cannot be import or use as it becomes None during shutdown


⚠ Jerry Savelle Ministries International Australia has degraded performance

In 4c3f67a, Jerry Savelle Ministries International Australia (https://jsmiaustralia.org) experienced degraded performance:

HTTP code: 200
Response time: 6721 ms

Resolved: Jerry Savelle Ministries International Australia performance has improved in 7991ab5 after 1 hour, 3 minutes.


Add hyperterm-dark-dracula theme

Checklist for submitting an awesome plugin, theme, or resource:

[x] The title for my package or theme uses its npm title (hyperterm-dark-dracula)
[x] The link for my package or theme uses the npmjs.com link (https://www.npmjs.com/package/hyperterm-dark-dracula)
[x] There is a visual representation of what my plugin or theme does in the repo. (Plugin: screenshot or gif || Theme: screenshot of the theme applied to HyperTerm)
[x] Put your awesome item at the BOTTOM of the correct (plugin, theme, or resource) list.
[x] VERY IMPORTANT: I've written a short (one sentence) description for my package or theme as the description of the awesome plugin, theme, or resource in the README.md file I'm submitting in the PR.

Thanks for the contribution! ☺


p2p: Implement Supervisor

Work In Progress
This is a placeholder PR to hold all the outstanding changes for the p2p work, will be broken apart further.
Stacked on top of #904

I've been looking through the abstractions again in the p2p/src/transport.rs module, and wanted to ask if there's a particular reason why "read/write" and "send/receive" naming conventions are mixed in the P2P architecture?
For example, the Connection trait has StreamRead and StreamSend associated types (instead of StreamRead/StreamWrite or StreamSend/StreamReceive).

For example, the Connection trait has StreamRead and StreamSend associated types (instead of StreamRead/StreamWrite or StreamSend/StreamReceive).

In order to distinguish physical connection semantics I'm keen on using send/receive for streams. The inconsistency you are pointing out is definitely an oversight and needs to be addressed.


Operations on SinglyLinkedList in Java

Description
A comprehensive description about the Pull Request
Reference Issue number #issue_no
issue_no must refer to the issue related to this PR, visit here
Type of change
Choosing one or more options from the following as per the nature of your Pull request.
NOTE: Check boxes using [x]

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Documentation Update

Checklist:

[x] I have named my files and folder, according to this project's guidelines.
[x] My code follows the style guidelines of this project.
[x] My Pull Request has a descriptive title. (not a vague title like Update index.md)
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] I have created a helpful and easy to understand README.md, with problem description and my name.
[ ] I have included a requirements.txt file (if external libraries are required.)
[x] My changes do not produce any warnings.
[x] I have starred this repository.
[ ] I have added a working sample/screenshot of the script.
[x] I have checked for trailing spaces in file names and none have them.

Added code for operations on SingleLinkedList in Java

@kusumapriyankaajjarapu Refer the issue

#366
Added code for operations on SingleLinkedList in Java


tail: add a --force flag to bypass the DO prompt

This PR adds a --force flag to wrangler tail to bypass the confirmation prompt for WebSocket/DO.

It will still print the warning text
Adds a changeset

cc @lrapoport-cf

This looks good to me, do you mind opening a PR in cloudflare-docs to update this page with the new option?

@jspspike - already done / already mentioned in both PRs: https://github.com/cloudflare/cloudflare-docs/pull/11827

hey @elithrar :) we discussed this as a team a bit more and agreed it would be good to have a test --  could you please add one? apologies we didn't catch it on the initial review!


New task structure

The following changes to PoAMs are proposed:

Internally to the code, rename/refactor PoAM to Task.
Add the following fields to Tasks

Projected Completion (of type Date)
Planned Completion (of type Date)
Custom field (String, to be named in dictionary and used to map to an external ID)
Status (enum, possible choices to be defined in dictionary. To be used later as Kanban-type tracking)

Refactor PoAM to Task. I'll perform the refactor according to the following workflow:

[x] Refactor front end UI
[ ] Refactor GraphQL
[ ] Refactor DAO and Resources
[ ] Refactor server side models and DB scheme


Fix crash on app launch Thread 1: Simultaneous accesses to 0x11a4e5158, but modification requires exclusive access #5770

Fixes #5770

tried few times, works for me

Hmm.. value vs. reference semantics seems to be really hard to get right sometimes. I remember there was a bug where behavior just silently breaks when we swap class and struct…


.net framework 4.8 supportability

Hello,
I could not find if Skype for Business Server works with 4.8 .net framework. There should be a list with all supported .net framework and what level of CU patch is needed for a .net framework.

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

ID: cd40e9bf-6fb5-b597-5494-b9ccc17e4660
Version Independent ID: 46d0d0a0-2ea9-efbd-1ef8-63686f7fef62
Content: System requirements for Skype for Business Server 2019
Content Source: Skype/SfBServer2019/plan/system-requirements.md
Product: skype-for-business-itpro
GitHub Login: @MicrosoftHeidi
Microsoft Alias: heidip

@Erdem-Oz  Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Info added on PR #2966

@Erdem-oz
The article refers specifically to support for 4.7 which was accurate at initial release. I've verified that 4.8 is also supported now The matrix you're suggesting is premature, since there's only two .NET versions supported and only one CU so far for Server 2019.
@microsoftheidi I'll leave you to approve the PR.

@scanum  Added the correct sentence to the PR.


feat(app): add send feature

Tasks

[x] Adapt components from Transaction and DApp/TransactionRequest to be able to re-use them
[x] Add missing components no core module
[x] Create all transactions-related screens and feature

https://user-images.githubusercontent.com/2029172/209880638-93d75732-0532-4812-803d-d2c4488780d0.mp4

I'm reviewing this PR code already, but will first mention functional problems I found
Send Screen:

in first frame of video, we see a blink of “ConfirmSend” screen before showing unlock dialog
can we ask password to unlock wallet later in the flow? we only need signature for actually sending the transaction right @luizstacio ?
transaction errors happening, but no feedback to the user.

we should not try to simulate the transaction if we know that:

invalid address

validate To field using  isB256 and isBech32 methods exposed by TS SDK

amount bigger than balance

validate InputAmount
if we click on “Max”, balance is set but considering fee. can we fake a transaction as soon as the user access the screen, enabling us to show the transaction fee earlier and cover all scenarios?

anyway after validation, if error occurs when trying to simulate, we might want to show TxErrors component as feedback

regarding Transaction Details card.

should be always visible with value of faked transaction mentioned in prev topic
if we won’t do this transaction fee predict, at least it should be hidden when inputs get clear after getting transaction. Right now it’s still visible showing 0.000 ETH fee.

here's a record showing all topics mentioned:
https://user-images.githubusercontent.com/8636507/207742791-c3603ee2-c192-49eb-a556-01e9eecbee54.mov

@luizstacio I did all changes you mentioned in the last comment (the video above is simulating slow 3g network)
https://user-images.githubusercontent.com/2029172/209875784-5257c88d-991b-4627-a2d7-09dbaaf0dbe6.mp4

@luizstacio I did all changes you mentioned in the last comment (the video above is simulating slow 3g network)
Kapture.2022-12-28.at.18.44.58.mp4

Perfect just two more things;

After approval and sending, the header could be titled sending the transaction.
On the transaction view after sending, the status is not green, but the tx is already confirmed.

functional when running locally

we have this "suggested" address, is this intended?

if yes it's a dev only thing?

final of amount input is cut (notice Max button)

https://user-images.githubusercontent.com/8636507/211689475-66efa75c-b970-41c8-b74a-81dda0ed3643.mov
can we validate if amount is bigger than balance before sending the transaction?
and show feedback similar to

storybook Send page is broken in PR`s preview


Install SDKs separately?

Please answer my question: Is it generally necessary to install the SDK separately as described on the page or is it included in the Applovin sdk? ShowMediationDebugger says the SDKs are missing.
https://dash.applovin.com/documentation/mediation/flutter/mediation-adapters/ios

So, I have now tried it on my own. I simply added the pods. But I don't know if this is the right way in Flutter because the pods are installed automatically.
It would be helpful if a tutorial on Flutter could be added to the docs.
target 'Runner' do
  use_frameworks!
  use_modular_headers!
  pod 'AppLovinSDK'
  pod 'AppLovinMediationGoogleAdapter'
  pod 'AppLovinMediationYandexAdapter'

  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end

@desmeit - We're investigating better ways to install SDKs without having to go into the underlying Android / iOS projects. If you have some suggestions, we're open.
The snippet you posted looks good to me though.

@desmeit - Fair. Let's use this thread for seeing the demand for integrating adapters as standalone Flutter packages. We'll add it to our queue in the meantime.


MAINTAINERS: add Aleksa Sarai

I'll send an email to the ML soon with a proper description and open for a
vote. I apologise for making this proposal so late in the -rc cycle, and if
you prefer we can have a vote on this topic after the release (despite this
being a purely organisational change).
/cc @opencontainers/image-spec-maintainers
Signed-off-by: Aleksa Sarai<EMAIL_ADDRESS>

I have appreciated the contributions and debate that @cyphar has added to the spec process so far. I am supportive of this addition.

Hey @cyphar, you have enough votes now to become a maintainer, there's 5/7 +1 votes on the mailing list. I'd say we keep this open until Monday to let any other folks vote and then merge this PR in :)

Close in favour of #724.


Add ansible provider

This is a proof-of-concept for ansible provider. If you're OK with adding it, I can work on the documentation, example, and more general setting later.
Please let me know should you have any concern on this. Thanks :beer:

Thanks for reviewing and accepting this PR! I'd like to add some doc and examples for ansible provider, and I'll do it with a new PR. Thanks :D


Deepwalk results consistency

I have used the default parameters of deepwalk to train on a node embedding as well as the config file in a yaml file. The embedding results look different in one of my downstream task. Is that possible to make the two implementations (deepwalk & graphvite) to be consistent? Since I do not see some parameters like "window-size" in the yaml file, I don't know whether they are still parameter options for graphvite.

Hi. Implementation of deepwalk is slightly different from the original one, but they share the same high-level design and reach similar results in our experiments.
In graphvite, augmentation_step corresponds to the window_size in deepwalk. They may not take the exact same value, since we removed some tricks like random window subsampling from the original deepwalk.
By the way, it's really necessary to tune the augmentation step for each dataset. My heuristic is to use augmentation_step = floor(log(n) / log(|E| / |V|)), where n is about 1000.

Thanks. So if my understanding is correct, you do not really run the "random walk" in your deepwalk implementation right? The augmentation steps are more related to the local augmentation in LINE paper?
I am working on some unsupervised task and I don't have labels for each node. How should I tune the parameter?
In addition, could you please give some simple and high-level explanations for each parameters in the config file? Maybe that document exists somewhere, but I fail to find that.

Not really. The only difference is that we don't explicitly store all random walks, for reducing memory cost.
Original DeepWalk

generate k random walks from each node
train skip grams within a sliding window on all walks
repeat 2 for several times

Note the original implementation doesn't repeat step 1, so the samples are not purely stochastic.
GraphVite's DeepWalk

generate one random walk from a random node
train skip grams within augmentation step on the walk
repeat 1, 2 for many times

The augmentation step is equivalent to a directed sliding window. That is, only skip grams like (i, i+s) where 0 < s <= augmentation step is accepted. Since as_undirected is true by default, it is equivalent to standard sliding window.

I apologize that we didn't provide a tutorial on the hyperparameters. We are going to compose some in the next version update. You may find the description of hyperparameters here, in GraphSolver.train.
Here are some basic insights for tuning hyperparameters of node embedding.

augmentation_step matters much. It highly depends on the sparsity of your graph and the granularity of your downstream task. The granularity means how large is the community of nodes you would like to regard as similar. Higher value should be used for sparser graphs and larger granularity.
episode size and num_negative determine your training speed. Larger episode size is faster, but consumes more CPU memory. Smaller num_negative is faster, but sometimes harms convergence.
num_negative * negative_weight may influence the performance. Our default settings is found to be robust on sparse social networks. I am not sure for others.
The default num_epoch and lr is good for a reasonable result. For dense datasets, you can turn down the num_epoch.

Thanks for you explanations. It makes the setting clear.
So for the difference between your deepwalk and the original ones. Actually you will generate more "random walk" in the augmentation step than using the original implementation?
For the parameter setting, what is "random_walk_batch_size"? Will it influence the convergence rate or final embedding results?
For the evaluation, you said the graphvite has a link prediction as the evaluation task. How should that work? Also, what's the classifier you used in the link prediction?
Thank you for your help!

Yes. We generate somehow more, but consume less memory.
random_walk_batch_size determines after generating how many random walks we should generate their skip gram samples. It's the batch size for CPU sampling, not for GPU training. In other words, it doesn't influence convergence. The best value may vary according to CPU cache size, but generally the default value works fine.
The interface of link prediction can be found here. Our link prediction works as follows

Infer the probability of each test edge
Sort the test edges in descending order
Compute the AUC metric of this sequence.
Ideally, all positive samples should be ranked before negative samples. There isn't any classifier, since we found that using the dot product in DeepWalk / LINE / node2vec is more robust to dimension changes.

Hi. Implementation of deepwalk is slightly different from the original one, but they share the same high-level design and reach similar results in our experiments.
In graphvite, augmentation_step corresponds to the window_size in deepwalk. They may not take the exact same value, since we removed some tricks like random window subsampling from the original deepwalk.
By the way, it's really necessary to tune the augmentation step for each dataset. My heuristic is to use augmentation_step = floor(log(n) / log(|E| / |V|)), where n is about 1000.

Hi, I have some questoins about the default settings. Dose the default value "auto" for augmentation_step  means that augmentation_step = floor(log(1000) / log(|E| / |V|))? If so, my dataset has |E|=116471433 and |V|=3299324, which gives augmentation_step=1, and it seems unreasonable. Shoud I avoid to use the default value and set augmentation_step to a larger number? Thx.


Ensure usage of unique store instance in config combo boxes

This PR improves the base combo box Shopware.apps.Config.view.element.Select, which is used e.g. when viewing plugin configuration forms via the settings module, to allow passing a store ID as the store parameter. This is escpecially usefull when providing selections of e.g. payment methods (Shopware.apps.Base.store.Payment) or dispatch methods (Shopware.apps.Base.store.Dispatch). In order to avoid side effects of other backend modules using the same store instance (and e.g. setting filters on it), the combo box does not use the instance that is registered by the passed store ID, but creates and uses a new instance of that store instead.
See also PR #525 for the original change of the base combo box, which is used when viewing plugin config forms in the plugin manager. This PR fixes the viewing of the same plugin config forms in the settings module. Furthermore it already includes the latest fix to support old storeIDs (22f5cacc17358161d7d0109de679973cba2c8906).
This PR does not introduce any breaking changes.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/#/issues/SW-15412.
Please use this issue to track the state of your pull request.

I've gone a step further and refactored the whole component since it's nearly an 1:1 copy of the base combo box.
Merged with c301e70a2eacd1b5c99fc5fa6fb1ca714906740e

Great, thank you 👍


Code for generating data from Darcy flow?

Hi, is there any way of recovering the code used to generate the data in load_darcy_flow_small ? Thanks!

Hi @plcrodrigues , there is some legacy code at an old commit here: https://github.com/neuraloperator/neuraloperator/blob/master/data_generation/darcy/solve_gwf.m
Hope this helps!


To add languages to support

What languages do we want to support (and have translators) as a first step?

English
Spanish
French

When the list is defined, I'll add the code to support all of them.

Hi @OlivierJourdan, please add Chinese.
thanks!!!

The source now includes 4 languages: English, Spanish, French, and Chinese.


Move metadata to sql-parser-binder module

Fixes #4691.

Pull Request Test Coverage Report for Build 2062

52 of 74 (70.27%)  changed or added relevant lines in 36 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.08%) to 59.067%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

shadow-core/shadow-core-rewrite/src/main/java/org/apache/shardingsphere/shadow/rewrite/context/ShadowSQLRewriteContextDecorator.java
0
1
0.0%

sharding-core/sharding-core-rewrite/src/main/java/org/apache/shardingsphere/sharding/rewrite/parameter/ShardingParameterRewriterBuilder.java
2
3
66.67%

sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/communication/jdbc/JDBCDatabaseCommunicationEngine.java
0
1
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-binder/src/main/java/org/apache/shardingsphere/sql/parser/binder/segment/select/projection/engine/ProjectionEngine.java
1
2
50.0%

shardingsphere-underlying/shardingsphere-rewrite/shardingsphere-rewrite-engine/src/main/java/org/apache/shardingsphere/underlying/rewrite/SQLRewriteEntry.java
0
1
0.0%

shardingsphere-underlying/shardingsphere-rewrite/shardingsphere-rewrite-engine/src/main/java/org/apache/shardingsphere/underlying/rewrite/context/SQLRewriteContext.java
2
3
66.67%

shardingsphere-underlying/shardingsphere-merge/src/main/java/org/apache/shardingsphere/underlying/merge/MergeEntry.java
0
3
0.0%

shardingsphere-underlying/shardingsphere-rewrite/shardingsphere-rewrite-engine/src/main/java/org/apache/shardingsphere/underlying/rewrite/sql/token/generator/SQLTokenGenerators.java
0
3
0.0%

sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/communication/jdbc/wrapper/PreparedStatementExecutorWrapper.java
0
5
0.0%

sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/communication/jdbc/wrapper/StatementExecutorWrapper.java
0
5
0.0%

Files with Coverage Reduction
New Missed Lines
%

sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/util/IpUtils.java
2
80.0%

Totals

Change from base Build 10165:
0.08%

Covered Lines:
12153

Relevant Lines:
20575

💛  - Coveralls

Codecov Report

Merging #4700 into master will increase coverage by <.01%.
The diff coverage is 67.56%.

@@             Coverage Diff              @@
##             master    #4700      +/-   ##
============================================
+ Coverage     55.43%   55.43%   +<.01%
  Complexity      426      426
============================================
  Files          1136     1133       -3
  Lines         20624    20575      -49
  Branches       3827     3819       -8
============================================
- Hits          11432    11405      -27
+ Misses         8470     8450      -20
+ Partials        722      720       -2

Impacted Files
Coverage Δ
Complexity Δ

...ngproxy/backend/schema/impl/MasterSlaveSchema.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...ardingjdbc/executor/AbstractStatementExecutor.java
41.3% <ø> (ø)
0 <0> (ø)
:arrow_down:

...ngproxy/backend/schema/impl/TransparentSchema.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...ardingproxy/backend/schema/impl/EncryptSchema.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...pt/metadata/loader/EncryptTableMetaDataLoader.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...e/encrypt/merge/dql/EncryptDQLResultDecorator.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...e/init/loader/impl/DefaultTableMetaDataLoader.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...dingsphere/sharding/route/hook/SPIRoutingHook.java
100% <ø> (ø)
0 <0> (ø)
:arrow_down:

...ine/decorator/impl/TransparentResultDecorator.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...sphere/encrypt/metadata/EncryptColumnMetaData.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

... and 53 more

Continue to review full report at Codecov.

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


Compatibility issue

Hello !
Here is the situation, I am using another addon that modifies quests. When I exit MM+ the WoW quest module reactivates on top of it. I could see in the code that you created an exception for the KT tracker. I made the modification directly in the Core.lua but with each update we are good at redoing it.
So I come to my question, would there be a solution for addons other than KT tracker?
Thanks in advance ! :D

Closed in #44


Add reply arrow example

Summary

Ticket Link

@justinegeffen looks good

Thanks @bbodenmiller, this is a really helpful update. :)


[Transform] Cannot comment inside a transform block

transform {
e.fname = p.first_name;
e.lname = p.last_name;
// e.marks =
}
Issue
Transform.bal:79:7: unwanted token '// e.marks ='

Comments are supported in transform statement now.


Feature Request: Create a manual activity

Hi!
I wish it were possible to create an activity. Similar to what is possible here, but embedded in a HomeAssistant automation:
https://connect.garmin.com/modern/activity/manual
Background:
I use a treadmill whose activity I can read on a current meter. From these minutes of activity, I can then also calculate a distance.
These two values provide enough information to create an activity.
 With a little guidance from you, I might be able to contribute this feature if you think it would be useful.

Thank you for your issue, is this a request for Garmin Connects Home Assistant integration or the underlaying python-garminconnect package? (which is also maintained by me) I could have a look to implement it in the lather first...
https://github.com/cyberjunky/python-garminconnect


docs(rust): fix mispointed link

Current Behavior

the docs pointed to start_processor() when it shhould have pointed to start_worker instead
Proposed Changes

replaced Self::start_processor with Self::start_worker.
Checks

[x] All commits in this Pull Request are signed and Verified by Github.
[x] All commits in this Pull Request follow the Ockam commit message convention.
[x] I accept the Ockam Community Code of Conduct.
[x] I have accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam-contributors repository.

Thank you 👍


Gym DRL

add support for training Navigation policies using Deep reinforcement learning like isaac-gym

add support for training Navigation policies using Deep reinforcement learning like isaac-gym

This pull request does not add any code regarding supporting training using deep-reinforcement learning, therefore it will be closed as it makes no sense.


Wolf.com Manhua Raws Source Request

Source name
늑대닷컴  /  Wolf.com
Source link
wfwf354.com
Source language
Korean
Other details
Hosts raws for korean manhua / webtoons.
18+/NSFW = yes
Acknowledgements

[X] I have checked that the extension does not already exist by searching the extension listing and verified it does not appear there.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a meaningful title with the source name.
[X] I will fill out all of the requested information in this form.

Duplicate of #3987
Search the existing issues before opening a new one

So sorry. I did search but that issue didn't pop up cause it's using an old domain name.


stream.end() synchronously closes the worker.

Pull Request Test Coverage Report for Build 856364422

11 of 12 (91.67%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 88.352%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

index.js
8
9
88.89%

Files with Coverage Reduction
New Missed Lines
%

index.js
1
86.8%

Totals

Change from base Build 836240688:
-0.3%

Covered Lines:
237

Relevant Lines:
257

💛  - Coveralls

Pull Request Test Coverage Report for Build 856364422
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

11 of 12 (91.67%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 88.352%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

index.js
8
9
88.89%

Files with Coverage Reduction
New Missed Lines
%

index.js
1
86.8%

Totals

Change from base Build 836240688:
-0.3%

Covered Lines:
237

Relevant Lines:
257

💛  - Coveralls


Add package vcard.

Add package implementing a standards-compliant parser and serializer for VCard3 files.

Great work!

Thank you! I hope others find it useful.


[RESOLVED] High ICMP ping response time

Problem started at 10:27:16 on 2023.04.13
Problem name: High ICMP ping response time
Host: ST-FG
Severity: Warning
Operational data: Value: 905ms
Original problem ID: 16144
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23135&eventid=16144

Problem has been resolved in 6m 0s at 10:33:16 on 2023.04.13
Problem name: High ICMP ping response time
Host: ST-FG
Severity: Warning
Original problem ID: 16144