Allow binary-only and text-only websocket connects (#389)

This allows the various formats (e.g., CBOR) that can't be converted in or out of Text to be used in a websocket by specifying you want to use a binary-only connection.  A text-only connection is provided for symmetry.

@jstarry How's this? As per my previous PR, this code works for me, but I'm happy to do more with guidance.

Oh, one thing my previous PR did that I didn't do here is add a line of documentation to each of the binary-only formats mentioning that they are binary only. I'm guessing that such information, and a reference to connect_binary might be useful, and I meant to add them, but forgot.

Closed in favour of #847. Thanks @ctm!


How to define vzero and vreinterpret

Dear all,
     We are adding new intrinsics which is depending on riscv-v-spec 0.9 recently,  but there remain two new intrinsics "vzero and vreinterpret" which I have never seen in riscv-v-spec 0.9.
     The definition of vzero and  vreinterpret we have defined is as following in
src/llvm/include/llvm/IR/IntrinsicsRISCVVector.td
def int_riscv_vzero_i8m1
  : Intrinsic<[llvm_nxv1i8_ty],
              [],
              [IntrNoMem]>;

def int_riscv_vreinterpret_u64_i64_u64m2
  : Intrinsic<[llvm_nxv2i64_ty],
              [llvm_nxv2i64_ty],
              [IntrNoMem]>;

     But in src/llvm/include/llvm/IR/RISCVInstrInfoV.td,  the riscv-v-spec 0.9 doesn't give any illustration of the encoding definition to vzero and  vreinterpret, Do you know how to define them?
//__builtin_riscv_vzero_i8m1()
def : Pat<(int_riscv_vzero_i8m1), ()>;

//___builtin_riscv_vreinterpret_u64_i64_u64m2(src)
def : Pat<(int_riscv_vreinterpret_u64_i64_u64m2), ()>;

One example is as following, vzero and vreinterpret don't have the encoding definition.
let hasSideEffects = 0, mayLoad = 1, mayStore = 0 in
multiclass VLoad_UnitStride<bits<3> nf, bits<1> mew, bits<2> mop,
                            bits<3> width, string opcodestr> {
  def _m  : RVInstVLoad<nf, mew, mop, width, RVV_Masked, OPC_LOAD_FP,
                  (outs VR:$vd), (ins GPR:$rs1, Zero:$zero, VMR:$vm),
                  opcodestr, "$vd, ${zero}(${rs1}), $vm"> {
    let Inst{24-20} = 0b00000;
  }
  def _um : RVInstVLoad<nf, mew, mop, width, RVV_Unmasked, OPC_LOAD_FP,
                  (outs VR:$vd), (ins GPR:$rs1, Zero:$zero),
                  opcodestr, "$vd, ${zero}(${rs1})"> {
    let Inst{24-20} = 0b00000;
  }
}

defm VLE8_V : VLoad_UnitStride<0b000, 0b0, 0b00, 0b000, "vle8.v">, Sched<[]>;
defm VLE16_V : VLoad_UnitStride<0b000, 0b0, 0b00, 0b101, "vle16.v">, Sched<[]>;

//__builtin_riscv_vle8_v_i8m1(base)
def : Pat<(int_riscv_vle8_v_i8m1 GPR:$rs1), (VLE8_V_um GPR:$rs1, 0)>;

//__builtin_riscv_vle16_v_i16m1(base)
def : Pat<(int_riscv_vle16_v_i16m1 GPR:$rs1), (VLE16_V_um GPR:$rs1, 0)>;

Thank you
Best Regards
William

Those intrinsics don't correspond to an actual instruction. They are here to help with writing high-level code.
̀vzero outputs an all-zero vector (of the appropriate type), i.e. __builtin_riscv_vzero_i8m1() outputs a zero-valued vint8m1_t. The compiler has some freedom on how to achieve that (using a zero-generating idiom like xor a,a,a, reusing a previously-known-to-be-zero vector, etc.)
vreinterpret like ___builtin_riscv_vreinterpret_i64_u64m2 merely changes the high-level types without changing any bit in the vector. In this case it merely changes the 'signedness' of the type, reinterpreting vint64m2_t to vuint64m2_t.
Both are described as 'utilisy functions' in https://github.com/riscv/rvv-intrinsic-doc/blob/master/rvv-intrinsic-rfc.md#utility-functions

Those intrinsics don't correspond to an actual instruction. They are here to help with writing high-level code.
̀vzero outputs an all-zero vector (of the appropriate type), i.e. __builtin_riscv_vzero_i8m1() outputs a zero-valued vint8m1_t. The compiler has some freedom on how to achieve that (using a zero-generating idiom like xor a,a,a, reusing a previously-known-to-be-zero vector, etc.)
vreinterpret like ___builtin_riscv_vreinterpret_i64_u64m2 merely changes the high-level types without changing any bit in the vector. In this case it merely changes the 'signedness' of the type, reinterpreting vint64m2_t to vuint64m2_t.
Both are described as 'utilisy functions' in https://github.com/riscv/rvv-intrinsic-doc/blob/master/rvv-intrinsic-rfc.md#utility-functions

Thank you for your reply, dear Romain Dolbeau
I have known the use of vzero and vreinterpret, so due to all of these definition, we don't need to define the vzero and vreinterpret pat in src/llvm/include/llvm/IR/RISCVInstrInfoV.td like int_riscv_vle8_v_i8m1, right?
//__builtin_riscv_vzero_i8m1()
def : Pat<(int_riscv_vzero_i8m1), ()>;

//___builtin_riscv_vreinterpret_u64_i64_u64m2(src)
def : Pat<(int_riscv_vreinterpret_u64_i64_u64m2), ()>;


Remove outdated docc index

IncrementalParseTransition.swift has been moved to SwiftParser.

@swift-ci please test


Upgrade to TeaVM 0.5.1

@winniehell Thanks! With previous version of TeaVM it can't transpile some of my code like this
public static void main(String[] args) {
    HTMLDocument.current().getElementById("id").setInnerHTML("Ahaha!");
}

It works now though I need to clone your fork and publish it to my local maven repository.
@edibleday Thank you for this great tool. It's more comfortable to use it from gradle. I kindly ask you to merge this PR and publish plugin to jitpack or whatever you're using.

ping @n3o59hf. Any reason to not merge this PR?

@andriipanasiuk I suggest to move to @renatoathaydes' fork

Just for everyone's information: @vic-cw will take over the fork instead of me :) I will try to help as much as I can. Let's hope this plugin gets the treatment it deserves from now on, and hope others also join the effort to maintain it!

For easy reference here's my fork: https://github.com/vic-cw/teavm-gradle-plugin


nsc-events-nextjs-7-397-clean-up-error-msgs

Resolves #397
Adds more descriptive error messages when creating events

@ken-ni The branch for this PR is behind, you need to resolve the branch conflict so that you can pull the recent changes from the main branch.

@heosman Thank you for the feedback! I was able to resolve the branch conflict and merge main into this branch I think.. Let me know if I did it incorrectly.

LGTM

LGTM


Resize h3

Expected Behavior
h3 please adjust to 24px at least on desktop
Current Behavior
h3 is 28px

font-size 24px
line-height 28px


Create function to create outline client

Fixes #45
What do you think? 🤔

IMO this is not the ideal way. We should employ function closures and config structs rather than parsing same args again and again.


Release v1

Hi jpoehls,
Thanks for creating this package!
Will you release a v1 version? The gopkg v0 isn't intended to be used as a release, more as a pre-release "still in development" tag. Actually, when you create branch v1, the gopkg.in/gophermail.v0 will become unavailable.

I do plan to release a v1 at some point. I'm aware of the implications of a v0 and still see gophermail as in a pre-release state. Honestly, this is just because I don't have the time to spend on it right now to do additional testing and validate that the API design is good for long term.
I've spent some time this morning creating issues for the things I think need done before we bump to v1. Hopefully this makes the state of the project a bit more transparent.
https://github.com/jpoehls/gophermail/milestones/v1


use/order corrupts data with some DODS datasets

Reported by sirott on 16 Apr 2002 23:45 UTC
Example:
use order=-x-y \
http://stout.pmel.noaa.gov:9090/dods/proxy/ferret.wrc.noaa.gov/cgi-bin/nph-
nc/data/MO04MDD1.sst.ADD2002092.003.2002099174020.hdf"
shade sst_mean[i=1:8192:16,j=1:8192:16]
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/389

Comment by<EMAIL_ADDRESS>on 17 Apr 2002 20:14 UTC
one-line fox in IS_REGRID
The problem was that following the implicit regrid that occurs when
delta-strides are invoked, the cx_delta flag was not removed from the result.
Version 5.4 had a complete rework of the handling of delta-strides in order to
accomodate mixed strides and modulo.  This appears to have been a bug left-over
from those changes.

Comment by<EMAIL_ADDRESS>on 21 Oct 2003 20:16 UTC
Moving from the<EMAIL_ADDRESS>user to the<EMAIL_ADDRESS>user.

Comment by<EMAIL_ADDRESS>on 10 Feb 2004 21:15 UTC
Put bugs that were in component "All" into "Main"


Dockstore documentation for 0.4-beta.3

Our documentation needs to cover the new features of the last two releases

Note from meeting: associate this with the news page and the incorporation of the wiki content

Completed


Change actions to mapActionsToProps

The connect HOF exported by Brigade takes two arguments, one to map state to props conventionally named mapStateToProps, the other to map actions to props, unconventionally named actions.
This PR updates stories and docs to rename actions to mapActionsToProps. It does not change any executable code. Rather it is to set a good example for users of the library.

Pull Request Test Coverage Report for Build 155

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 100.0%

Totals

Change from base Build 152:
0.0%

Covered Lines:
186

Relevant Lines:
186

💛  - Coveralls


docs: fix a typo

just a small typo

Coverage remained the same at 97.075% when pulling 0294d65546d87af706e1f5d571488a6478defde8 on malor:master into c13078c3ceb6441dbd37d21b4823364d89e437e0 on ikalnitsky:master.


More descriptive errors

Added the following error if no args are passed in:
➜  src git:(master) ./tldr
usage: tldr <command>
Which page do you want to see?
try: tldr tldr
➜  src git:(master)

And the following message if the wrong args are passed in:
➜  src git:(master) ./tldr thisdoesntexist
This page doesn't exist yet!
Submit new pages here: https://github.com/tldr-pages/tldr
➜  src git:(master)

fixes #7 #8
Let me know what you guys think :smile:

Please adjust your editor settings to keep the current formatting.

Oh, sorry about that, will fix

@Leandros should be fixed now

Great. Looks good. One tiny improvement and it's ready for the merge. It's better to use argv[0] instead of hardcoding the command, the executable could be named different.

Good idea, should be fixed now.

You missed the tldr two lines below. ;)

Got it! And I checked a few commands and it seems that this type of situation is indeed considered "failure"
➜  src git:(master) git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
➜  src git:(master) echo $?
0
➜  src git:(master) git
usage: git [--version] [--help] [-C <path>] [-c name=value]
           [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
           [-p | --paginate | --no-pager] [--no-replace-objects] [--bare]
           [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
           <command> [<args>]

The most commonly used git commands are:
   add        Add file contents to the index
   bisect     Find by binary search the change that introduced a bug
   branch     List, create, or delete branches
   checkout   Switch branches or restore working tree files
   clone      Clone a repository into a new directory
   commit     Record changes to the repository
   diff       Show changes between commits, commit and working tree, etc
   fetch      Download objects and refs from another repository
   grep       Print lines matching a pattern
   init       Create an empty Git repository or reinitialize an existing one
   log        Show commit logs
   merge      Join two or more development histories together
   mv         Move or rename a file, a directory, or a symlink
   pull       Fetch from and integrate with another repository or a local branch
   push       Update remote refs along with associated objects
   rebase     Forward-port local commits to the updated upstream head
   reset      Reset current HEAD to the specified state
   rm         Remove files from the working tree and from the index
   show       Show various types of objects
   status     Show the working tree status
   tag        Create, list, delete or verify a tag object signed with GPG

'git help -a' and 'git help -g' list available subcommands and some
concept guides. See 'git help <command>' or 'git help <concept>'
to read about a specific subcommand or concept.
➜  src git:(master) echo $?
1
➜  src git:(master)

I can cite other examples if you'd like

@Leandros

Please merge the current master thread into your branch, it'll run the travis build. And you should notice the bug in your code, since it won't compile.

Is it all good now?

Yes. Build passed. Looks good! Merged!

Thanks! :+1:


Delete remains of reset function

Codecov Report

Merging #616 (0cce700) into develop (898b10b) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 0cce700 differs from pull request most recent head 057004c. Consider uploading reports for the commit 057004c to get more accurate results

@@           Coverage Diff            @@
##           develop     #616   +/-   ##
========================================
  Coverage    49.82%   49.82%
========================================
  Files           25       25
  Lines         3952     3952
========================================
  Hits          1969     1969
  Misses        1702     1702
  Partials       281      281

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 898b10b...057004c. Read the comment docs.


right devops interview questions link

Hi,
Thanks for your efforts.
This PR fixes the DevOps Interview Questions link in https://github.com/Tikam02/DevOps-Guide/tree/master/Interview (if you click on DevOps Interview Questions underneath Contents you will get 404 page).
Thanks

@all-contributors please add @mahmoodahmad100  for docs


document path.arc(…anticlockwise) must be true or 1, not true-ish

We have cw = 1 ^ ccw

0, "0", undefined, false => draws a clockwise arc
1, "1", true => draws an anticlockwise arc

So far so good, but trying with anticlockwise = "anticlockwise" or anticlockwise = 3 (or most other true-ish values) will give a very weird path with an inverted curvature, because it will have both ccw true-ish, and cw = 1.
I don't think the code should be fixed as this is probably the fastest approach, but maybe the documentation?
Currently we say

If anticlockwise is true, the arc is drawn in the anticlockwise direction; otherwise, it is drawn in the clockwise direction

"otherwise" could be changed to "if false or undefined", or "if false"…
Another possibility:

If anticlockwise, a boolean, is true, the arc is drawn in the anticlockwise direction; otherwise, it is drawn in the clockwise direction.

(I got bitten by using a checkbox’s value, which gave me anticlockwise="On".)
See interactive test at https://observablehq.com/d/d8c04cb491a6c444

That’s a bug.


Rebuild v1.6.0 for proj810

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@ocefpaf and @gillins, should we migrate the pin to v1.7.0?  That would avoid having to build v1.6.0 as other pins get updated, but presumably risks tangling up current migrations.

The bot is raring to go :-)
https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/1662


 Then I moved to the manual setup and it threw the same error.
While installing, the bdust_wheel for scipy errors which gives me:

Failed building wheel for scipy
Failed cleaning build dir for scipy
Failed building wheel for scikit-learn

which then breaks the install with:
Command "/usr/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-build-Je8Y7m/scipy/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-VPk4Mt-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-Je8Y7m/scipy/

Hi @Longshotpro2! It looks like scipy build problem on your machine. I'd recommend using docker, you can start it only with one command: https://github.com/lukalabs/cakechat#quick-start
Otherwise, you could have all these installation problems with scipy/numpy/theano/whatever external libs on your machine and you need to figure out the way how to install each one

I did a fresh install of the os, installed docker and then ran the quick-start. The first line exited with standard_init_linux.go:190: exec user process caused "exec format error"
which made the second line not work at all.

It's one-line command actually. It's formatted in two lines for better visual perception
Which OS do you use on your host machine?

I am using Raspbian, Debian Stretch.

I think that's the problem. I'd not recommend even try to run or train Cakechat model on Raspberry Pi (I guess you have it as you mention Raspbian) because the model is required heavy computations. Also, you'll have a ton of problems with libs installation as you have right now.
We tested cakechat on MacOS High Sierra, Ubuntu (14.04, 16.04) and Windows 10. You could try any of these, should work

Okay, the thought process was to train on paperspace after playing around with the sample model but implement on the pi or docker swarm.

For training model, you could try any cloud provider with Nvidia GPU VMs. But again, I really doubt that it's possible to launch a trained model on the pi.

@Longshotpro2 Do you have any other questions about cakechat setup?

No, not at this time. Thank you for your help!

I have the same problem. I am using manual setup. I can't install Docker on this machine as I am using Windows 10 Home edition


Update stable version in repo from 0.0.6 to 1.0.0

Think about update stable version to 1.0.0
Version: stable=0.0.6 (394 days old) => latest=1.0.0 (15 days old)
Installs: stable=50 (87.72%), latest=4 (7.02%), total=57
Click to use developer portal
Click to edit
Do not close this issue manually as a new issue will be created if condition for update still exists.
Please drop a comment if any reason exists which blocks updating to version 1.0.0 at this time.
Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

This issue seems to be outdated.
This issue suggests to update the stable version of this adapter to 1.0.0 but the current stable version is already 1.0.0.
So this issue should be closed.
@mcm1957 for evidence


DCOS-2274: Show error message to make it clear that command is not valid

Rebase to fix the build problem in the tests

Please rebase on top of master and squash your commits.

what's the status on this? @ssk2 @truskovskiyk

@ssk2 @tamarrow PR updated please review, all tests passed

one small comment, rebase your commits and then lgtm.

@tamarrow done


speed is slow when use as cross-compile solution

Is this a bug report, feature (enhancement) request or question? (leave only one on its own line)
kind question
Description:
hi, i use qemu-user-static as a cross-compile solution, but found the time of compile consumed is average 2~5 times more than directly compile on the targe platform.
since i'm not familiar with qemu, my question is this normal or there is some way to speed up?
i do some search and found kvm is a relative topic, but looks like kvm only suitable for the same architecture of both host and target platform(e.g. both host and target are x86_64 platform), so can i have some brief answer for this question?
my host is ubuntu 20.04 lts with x86_64 cpu, and a docker of arm64v8/ubuntu for cross-compile for a arm64v8 target, before i use the cross-compile docker i run the lastest multiarch/qemu-user-static as demonstrated in readme.
any suggestion?thanks very much.
Steps to reproduce the issue:
as above
Describe the results you received:
as above
Describe the results you expected:
as above
Environment:
as above

so can i have some brief answer for this question?

brief answer: yes, it is normal that emulated execution is several times slower than the same command on a real hardware

thanks for the brief and strong confirm,
so it's not a misuse and there is no way to improve just by configuring something?
and is my understanding about kvm is right?

there is no way to improve just by configuring something?

at least I am not aware of such way

and is my understanding about kvm is right?

yes, I think so, but I am not very familiar with the KVM internals
If you need an ARM64 system for personal needs then I'd recommend you to use Oracle Cloud. They provide free VMs. I've explained more here: https://martin-grigorov.medium.com/github-actions-arm64-runner-on-oracle-cloud-a77cdf7a325a

thank you for the more detailed discussion, and also for the useful link.
for anyone who wish a brief answer, hope this discussion could be a quick reference :)

I think maybe libhoudi.so can resolve your problem,but I can not known  libhoudini.so how to be used in centos or ubuntu.


Runtime error on windows

This was experience by Ulli @ulrikew trying it out during our meeting!

Thank you @fedorov. Apparently, hit is not pre installed on windows machines as it's usually on mac.
I don't think setting up got from a slicer extension is a good idea (if possible) as the average user likely won't expect a slicer extension to install third party programs on their system.
I see two more options. Either we specify it as dependency / requirement such as docker. Alternatively we can package the python packages and add them to the pypi index to avoid git. As these packages are not (yet) meant to be used outside of the MHub context, I don't recommend option 2.
I'll look into this after my vacation, happy to hear your thoughts on this @fedorov.

As yet another option, you can make a release of that repo, and pull zipped package with the source code using wget.
But now that you mention it - the extension should check for the presence of docker on the system, and if not available - ask the user to install and point to the instructions, and not proceed until docker is detected. It doesn't make sense to do anything else until docker is detected.

Thats a Great Option @fedorov. We're planning to create releases of all our dependencies for every stable release. Binding the slicer extension to one of our stable releases (instead of latest) is also in line with our recommendation for MHub integrations in general.
I'm planing a initialization screen for a while, also because the app takes a while to load (caused by the installations of all dependent packages at startup). Adding a docker check and installation tips or at least links to the resources there looks like a good fit and is on top of the todo list for the extension.


Update LICENCE to quansight

This has been created during quansight work hours, it is the property of quansight.

This is fixed with this commit https://github.com/Quansight/ksmm/tree/d2646f272ecee2a9c37357207f2743715571da5d


Add script for quick development

Running "images/bin/devbuild" will compile the lifecycle executables
locally and then generate "packs/samples:dev" from "packs/samples" with
the new lifecycle binaries. This enables the abililty to quickly modify
the lifecycle binaries and then test them out.

Could we call it images/bin/build-dev?

@sclevine File name changed


Avolites plugin

They have a huge library!
Though it seems that they use multiple different formats (Diamond 4 .d4, Pearl/Azure/Sapphire .r20, Diamond II/Diamond III .d2, Sapphire 96 .r96, Visualiser .vis). Maybe they are so similar that we can combine them into one plugin?

QLC+ parser for Avolites d4: https://github.com/mcallegari/qlcplus/blob/master/engine/src/avolitesd4parser.cpp

They also have a fixture editor (personality builder): https://www.avolites.com/software/downloads/personality-builder


npm install runas fails in OS X

having trouble getting runas to install. here is an example session:
$ npm install runas
-
><EMAIL_ADDRESS>install /Users/mrose/git/api-workbench/node_modules/runas
> node-gyp rebuild

  CXX(target) Release/obj.target/runas/src/main.o
  CXX(target) Release/obj.target/runas/src/runas_darwin.o
  CXX(target) Release/obj.target/runas/src/fork.o
  SOLINK_MODULE(target) Release/runas.node
ld: library not found for -lgcc_s.10.5
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [Release/runas.node] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/opt/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1074:12)
gyp ERR! System Darwin 14.5.0
gyp ERR! command "node" "/opt/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/mrose/git/api-workbench/node_modules/runas
gyp ERR! node -v v0.12.7
gyp ERR! node-gyp -v v2.0.2
gyp ERR! not ok
npm ERR! Darwin 14.5.0
npm ERR! argv "/opt/local/bin/node" "/opt/local/bin/npm" "install" "runas"
npm ERR! node v0.12.7
npm ERR! npm  v2.14.3
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls runas
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/mrose/git/api-workbench/npm-debug.log

do i unserstand this error message correctly? it is looking for a rather old library?
ld: library not found for -lgcc_s.10.5

follow up: i have a different machine at home and it has no problem with npm install runas. on this one it installs just fine, no issues at all. it would be great to get some help understanding what might be the difference between the two.

 Try echo $DYLD_LIBRARY_PATH.
As for the 10.5 bit, I'm pretty sure that refers to OS X 10.10.5, which also makes sense since you're indeed running Yosemite.
Another thing worth checking, have you updated the Xcode command line tools?

on both machines echo $DYLD_LIBRARY_PATH returns nothing. However, the machine where it installs successfully is running 10.11 and has a freshly installed Xcode 7.1 with command line tools. The machine where it fails is running 10.10 and does have Xcode and command line tools installed, but the version of Xcode is a bit outdated, it has 6.1. I will try updated Xcode and the command line tools.

Yup, that was it. The outdated version of Xcode was the culprit. Brought Xcode up to date on my 10.10 machine and now everything installs without a hitch. Thank you for your swift and sage advice.


Is there a way to get the Kingpin annotation that an annotation is contained in?

I have a dictionary of my annotations, and i want to be able to call selectAnnotation:animate: on the king pin annotation that the correct one is contained within. Is there a way to do this using kingpin? Thanks!
(sorry if this is the wrong avenue for asking this question!)

also if i add this feature myself would a pull request be welcomed?

@mjmayank, pull request is more than welcome! Also I didn't get your question quite well: do you actually mean dictionary of annotations?
I am pretty sure that you are of this piece of documentation: Accessing cluster's annotations so I believe you're asking something different here.
Please elaborate or suggest Pull Request.

@stanislaw Basically I have a way to find an annotation in my own dataset, and previously I would just call selectAnnotation on it. However now that those annotations are hidden within Kingpin and not actually on the map themselves, I cannot programmatically select an annotation.
So it would be nice to be able to query for the kingpin annotation that's on the map that contains the annotation I want to select, so that the callout for that annotation is shown.

Hello @stanislaw I got the same request, any way to do that? I want to find a specific annotation...

Hello there @stanislaw @mjmayank , did you addressed this need?
How can we select programmatically an annotation that's part of a kingpin?

For my own project I made an NSDictionary within Kingpin that hashed each annotation to its cluster. You must designate something as a unique ID for the key in the dictionary (I used the objectID for the object my annotation was representing).
I wish I could have pushed it to the project but it wasn't really implemented robustly enough for any purpose other than my specific one. It was pretty hacky but I think the method could easily be abstracted though.

we are currently following another path, but we'll have a look at your approach, tnx! :)

You can look at my code here: https://github.com/mjmayank/kingpin


errorMonitor not correctly flagging errors on positive tests

Noticed this in updating DynamicOffsetWithInactiveBinding for #1212
On branch tobin_gh1212_positive_test_unexpected_errors I've pushed the updated version of that test without my fix. This causes unexpected errors in the test but even though it's ExpectSuccess() the test does not fail.

Fixed with 689ea76741


VSC Insiders windows can't be manipulated by external apps anymore

Issue Type: Bug
I can't reposition or resize the windows of VSCode anymore on Mac. This is a major painpoint. I can't be sure when it was introduced, but it's only broken in Insiders.
Have tried both Magnet and BetterTouchTool and neither of them can move or resize the windows. Did something happen on a fundamental level, perhaps with Electron? I hope this can be corrected soon.
I wish I could be more detailed steps to reproduce or refer to freeware apps. I'm sure plenty of people on the VSCode team must be using windows managers on their MacBooks though, so hopefully this shouldn't be hard to reproduce.
VS Code version: Code - Insiders 1.28.0-insider (31bf4ccab388c082fcf4edafeaae5b703f211b5b, 2018-09-12T05:12:04.730Z)
OS version: Darwin x64 18.0.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz (8 x 2500)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledrasterization: unavailable_softwarevideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
3, 3, 3

Memory (System)
16.00GB (0.03GB free)

Process Argv
/Users/gandalf/Documents/portable/Visual Studio Code - Insiders.app/Contents/MacOS/Electron

Screen Reader
no

VM
0%

Nothing has changed in VSCode as far as I know. I am closing this as it seems like an issue with the tools you are using, not VSCode itself. I suggest to follow up with them.

Two important facts point to this not being an issue with the tools:

I have never had this issue with any app before on Mac.
It only happens on Insiders.

So it's obviously something that's changed with VSCode. Surely there must be someone on the VSCode team that uses any sort of window manager on Macbook that could confirm?
Meanwhile I can contact the developers of the tools also. But the problem is with VSCode, that much I'm 99.9% certain of.


How to enable and to display connection option metadata?

Hello :),
probably someone can help me.
I used  "felixge's - node-mysql" for my thesis. There i got column-informations (variable "fields") like name, table, db, orgTable for each column of the returned query-data.
Now i am searching something similar for mariasql.
I found this commit:
"Added metadata option to return column type and charsets"
I tried to enable for connection by setting "metadata = true".
c.connect({
  host: '<IP_ADDRESS>',
  user: 'foo',
  password: 'bar',
  metadata: true
});

Then i tried to get the metadata output in this was, but i failed:
c.query('SHOW DATABASES')
 .on('result', function(res) {
   res.on('row', function(row, metadata) {
     console.log('Result row: ' + inspect(row));
     console.log(metadata);  // added code line, but undefined returned
   })
   .on('error', function(err) {
     console.log('Result error: ' + inspect(err));
   })
   .on('end', function(info) {
     console.log('Result finished successfully');
   });
 })
 .on('end', function() {
   console.log('Done with all results');
 });

Now I have 2 questions and i hope someone can help or give an advice.
1.) How can i get metadata?
2.) Is there a plan to extend such metadata informations or how I can extend it?

Can you explain what you mean by "extending" the metadata? What information are you missing?

Hello,
thank you for asking, but I added the metadata information required for my thesis project and you merged it into node-mariasql some time ago. Look here at pull request "Metadata information extension #52".
There are more metadata, which could be basically supported, look here:
http://dev.mysql.com/doc/refman/5.6/en/c-api-data-structures.html

v0.2.0 is released now and is more or less a complete rewrite. This version adds the column flags in the metadata object. If you need some other missing metadata, let me know which you are looking for.


fix: minor readme fixes / formatting

:tada: This PR is included in version 1.25.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Planned maintanance on Euphorbia and Pachycereeae From 11.03.2023 13:00 to 16.03.2023 22:00 GMT+2

We are taking measures to counter the recent increase in disruptions in order to better guarantee the stability and accessibility of our systems. For this reason, the Pachycereeae server will be switched off and replaced by the Euphorbia server.
During the maintenance period, the above-mentioned systems will be unavailable or only partially accessible from 11.03.2023 18:00 to 16.03.2023 22:00. This has no effect on the productive systems.

We started the replacement process.
Services and systems on this servers may not be available for now.

We have removed the server Pachycereeae from the server network and removed all associated connections.

We have successfully completed performance and integration tests. Maintenance can therefore be completed early.


fetching a dictionary type result with column name

The result we were getting were of list format and difficult to map the column names, added a new method docResult to give a dictionary type result. By default it'll be a list like it is now, but if you give doc=True in fetchall(), fetchmany() or fetchone(), it'll return a dictionary type result.

Thanks. I have refactored the code a little bit, so use a pattern similar to what it's used in psycopg2 or PyMySQL.
Now you can use this:
db = phoenixdb.connect(..., cursor_factory=phoenixdb.cursor.DictCursor)
cursor = db.cursor()

Or this:
cursor = db.cursor(cursor_factory=phoenixdb.cursor.DictCursor)

In both cases, all the fetch* methods will return dicts instead of lists.


Allow to deploy a HCP cloud.

Lame question, for witch meaning of HCP[1] are we referring here?
https://en.wikipedia.org/wiki/HCP


Cleanup dependencies

Removes unused dependencies, explicitly adds dependencies required for compilation which were transitively pulled, and cleans up the scopes.

@thyandrecardoso: As discussed offline, I've moved the dependencies of akka-actor and akka-stream back to the provided scope in apso-akka-http since the requirements for an ActorSystem and a Materializer are explicit.


numpy.pad() error

Hello, when I try running the provided code after installing everything, I get a numpy.pad() error:

TypeError                                 Traceback (most recent call last)
 in
13     results=[
14         mg.pcm16("my_song_master_16bit.wav"),
---> 15         mg.pcm24("my_song_master_24bit.wav"),
16     ],
17 )
~/opt/anaconda3/lib/python3.7/site-packages/matchering/core.py in process(target, reference, results, config, preview_target, preview_result)
82         need_no_limiter=any(not rr.use_limiter and not rr.normalize for rr in results),
83         need_no_limiter_normalized=any(
---> 84             not rr.use_limiter and rr.normalize for rr in results
85         ),
86     )
~/opt/anaconda3/lib/python3.7/site-packages/matchering/stages.py in main(failed resolving arguments)
267         need_no_limiter,
268         need_no_limiter_normalized,
--> 269         config,
270     )
271
~/opt/anaconda3/lib/python3.7/site-packages/matchering/stages.py in __finalize(result_no_limiter, final_amplitude_coefficient, need_default, need_no_limiter, need_no_limiter_normalized, config)
200     result = None
201     if need_default:
--> 202         result = limit(result_no_limiter, config)
203         result = amplify(result, final_amplitude_coefficient)
204
~/opt/anaconda3/lib/python3.7/site-packages/matchering/limiter/hyrax.py in limit(array, config)
92
93     debug("Modifying the gain envelope: hold / release stage...")
---> 94     gain_release = __process_release(np.copy(gain_hard_clip_slided), config)
95
96     debug("Finalizing the gain envelope...")
~/opt/anaconda3/lib/python3.7/site-packages/matchering/limiter/hyrax.py in __process_release(array, config)
57     hold = ms_to_samples(config.limiter.hold, config.internal_sample_rate)
58
---> 59     slided_input = __sliding_window_fast(array, hold, mode="hold")
60
61     b, a = signal.butter(
~/opt/anaconda3/lib/python3.7/site-packages/matchering/limiter/hyrax.py in __sliding_window_fast(array, window_size, mode)
37         return maximum_filter1d(array, size=(2 * window_size - 1))
38     half_window_size = (window_size - 1) // 2
---> 39     array = np.pad(array, (half_window_size, 0))
40     return maximum_filter1d(array, size=window_size)[:-half_window_size]
41
TypeError: pad() missing 1 required positional argument: 'mode'
I have tried multiple different wav files to see if that changed anything, and it did not. I also tried just making the 16 bit recording, but that also did not work. Any help would be greatly appreciated!

Nothing in this stack trace refers to soundfile. I think your problem is elsewhere.

Nothing in this stack trace refers to soundfile. I think your problem is elsewhere.

Hello, right I agree. But there is still an error with the code then. I copied and pasted the code on your page and used two .wav files. This is an internal numpy error that I cannot trouble shoot because it is within the package.

Hello, right I agree. But there is still an error with the code then. I copied and pasted the code on your page and used two .wav files. This is an internal numpy error that I cannot trouble shoot because it is within the package.

@jasongabler762 It is unclear which example code you are referring to. But it is not likely to be python-soundfile related. I guess your issue should be submitted at matchering: https://github.com/sergree/matchering/issues

@jasongabler762 It is unclear which example code you are referring to. But it is not likely to be python-soundfile related. I guess your issue should be submitted at matchering: https://github.com/sergree/matchering/issues


Annotation isn't draggable if drawing enabled

Hi,
After migration to OSD version 4.0.0 and Annotoriuos v.2.7.10 existing annotations became undraggable if drawing mode enabled, but everything is fine it's disabled. I tried to debug it a bit and found out that it doesn't raise clickAnnotation event in draw mode. The second problem happens if I try to click in just random place and draw annotation after it so it doesn't draw anything, but after disabling and enabling draw mode everything is fine. I think both issues are related but don't understand why they happen and how to solve them.

OSD version: 4.0.0
Annotoriuos version: 2.7.10
React version: 17.0.2
OS: Ubuntu 20.04.4
Browser: Google Chrome Version 102.0.5005.61 (Official Build) (64-bit)

Yikes, thanks for reporting. There seem to be a couple of changes in OSD 4.0 that broke Annotorious/OSD interop. I've been working out some of them, but it might still take a while until I can iron them all out. I'll put that one on the list!

@rsimon Thank you for quick response. I will wait for you to fix this problem, but for now will stay on the older version of OSD and Annotoriuos

@rsimon Hey. Do you have any progress with this issue?


Update nifclous-sdk-go to v1.7.0

Description

Upgraded the nifcloud-sdk-go to v1.7.0 🎉

How Has This Been Tested?

[ ] Build Successful with make install command

Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Refactoring (improves code quality but has no user-facing effect)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation

lgtm


Websockets and Reverse Proxy

I see a lot of issues on here about using web sockets. It certainly took a little fudgery for me to get it working.
If you are going to expose the same port that is listed in the --port=7890 parameter, then you should be able to get the .html output file to reference that port and connect to it.
But connecting to it securely via an Nginx reverse proxy is the angle I went for.
Setup and Nginx virtual host with TLS cert from Let's Encrypt and let it serve the static .html page. I also wanted to use Nginx to serve the web sockets, but because it's served on a port that is detailed in the static .html you can never get to it.
It works, but only because something doesn't behave as expected.
I used a docker-compose.yml to serve GoAccess.
version: '3.7'

services:
  goaccess:
    image: allinurl/goaccess
    command: "/var/log/nginx/access.log --log-format COMBINED --real-time-html -o /output/index.html --ws-url=wss://HOST.DOMAIN/ws/"
    volumes:
      - "/usr/share/nginx/html:/output:rw"
      - "/var/log/nginx:/var/log/nginx:ro"
    ports:
      - "12390:7890"

The clever bit that makes this work is the --ws-url In my Nginx config I'm going to capture /ws and redirect it to port 12390. But what actually happens is that the url that gets put into the html file is wss://host.domain/ws:7890 Why does this work? It's not a valid url the port should be before the /ws/ - thankfully it's not, because traffic is sent to wss://host.domain/ws/:7890 but the :7890 gets ignored, and web sockets gets served currently over port 443, the same as the static page is on!
upstream goaccess {
    server server:12390 weight=1 fail_timeout=30s;
}

server {
    listen 	443 ssl;
    server_name  host.domain;

    ssl_certificate_key     /etc/letsencrypt/live/host.domain/privkey.pem;
    ssl_certificate         /etc/letsencrypt/live/host.domain/fullchain.pem;
    ssl_trusted_certificate /etc/letsencrypt/live/host.domain/fullchain.pem;

    location / {
        root /usr/share/nginx/html;
        try_files /index.html =404;
    }

    location /ws {
        proxy_pass http://goaccess;
        # force timeouts if the backend dies
        proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504;

        # set headers
        proxy_buffer_size                  128k;
        proxy_buffers                      4 256k;
        proxy_busy_buffers_size            256k;
        proxy_set_header Referer           $http_referer;
        proxy_set_header X-Real-IP         $remote_addr;
        proxy_set_header X-Forwarded-Host  $host;
        proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
        proxy_set_header X-Server-Select   $scheme;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Port  $server_port;
        proxy_set_header X-Url-Scheme      $scheme;
        proxy_set_header Cookie            $http_cookie;
        proxy_set_header Host              $host;
        proxy_http_version                 1.1;
        proxy_set_header                   Upgrade $http_upgrade;
        proxy_set_header                   Connection ‘upgrade’;

        # by default, do not forward anything
        proxy_redirect off;
    }

}

My suggestion here is to not fix the --ws-url and if is specified please don't add the port, let that be done manually.

Thanks for sharing these findings! I'm glad we're on the same page about the issue with the port. I'm happy to submit a patch for this, but I wanted to make sure you will be able to update your configuration after this change.

I can always update my config. But need to be sure that fixing the port does not break the --ws-url. I would suggest that if a --ws-url is specified that it does not rebuild it from other parameters, but overrides it. So even if a port is specified, it gets ignored unless no --ws-url is specified.

I made some changes to this where it should work as expected. The idea behind configuring the port via the ws-url is to get to goaccess via a reverse proxy. For instance, if you only have port 443 available/open, you could reach a goaccess instance running on 7890 as:
goaccess access.log --log-format=COMBINED --port=7890 --ws-url=wss://goaccess.io:443 --real-time-html -o out.html

Please feel free to build from development and let me know if that addresses the issue on your end. Otherwise, it will be shipped in v1.7.2 soon. Thanks again!


Data is not pulled from Yasno correctly

Hello @denysdovhan ,
First of all, thank you for this wonderful integration! However, since yesterday, I’ve noticed that the electricity outage plans have been updated on Yasno, but these updates are not reflected in your integration.
Data in HA:

Data at Yasno:

It seems that, for some reason, "possible outages" are still present in your integration, even though Yasno has removed them from their website.

Hey, I am aware of this issue. Yasno now returns two types of schedule on their unofficial API: regular and daily schedule.

regular - is the schedule currently being used. It's still relevant, but it doesn't include data from Ukrenergo.
daily - is a schedule that gets published on daily basis. Basically, it's an intersection of regular schedule and timeframes from Ukrenergo.

This change shouldn't be hard to make, but I don't have much time for that. I will try my best to make necessary changes as soon as possible.

@denysdovhan it's looks same
curl  https://api.yasno.com.ua/api/v1/pages/home/schedule-turn-off-electricity | jq '.components[] | select( .template_name == "electricity-outages-schedule" and ( .available_regions[] | contains("kiev"))) | .schedule.kiev.group_2'
and
curl  https://api.yasno.com.ua/api/v1/pages/home/schedule-turn-off-electricity | jq '.components[] | select( .template_name == "electricity-outages-daily-schedule" and ( .available_regions[] | contains("kiev"))) | .schedule.kiev.group_2'
or you know other api?

@asp24
Yes, dictionary electricity-outages-daily-schedule contains a new schedule of outage.
@denysdovhan
I tried to implement it in my fork but wasn't able to test it before PR. I added my repo to HA instead yours (before removed it), but the integration didn't appear. Why it can be?

@Maxim-Inv in this case it will not help. Data returned inside electricity-outages-daily-schedule differs from rendered on the page. Proper schedule rendered into HTML on the backend. The minimal request to recieve it looks like this curl -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36' --cookie 'region=%7B%22id%22%3A44%2C%22name%22%3A%22%D0%9A%D0%B8%D1%97%D0%B2%22%2C%22key%22%3A%22kiev%22%2C%22subdomain%22%3A%22kyiv%22%7D' https://yasno.com.ua/schedule-turn-off-electricity
Nobody likes to parse HTML, but I did not find any XHR request returning "right" schedule

You should look for dailySchedule property, not schedule.

You should look for dailySchedule property, not schedule.

My bad, forgot to say that new schedule called dailySchedule.
Almost ready, I just want to check it tomorrow. Unfortunately, I only get data for today, there will be need to process data for tomorrow.
P.S. I'm noob in Python, use ChatGPT and developer experience in other languages. :)

@denysdovhan, can we expect an update to this plugin to include dailySchedule?

can we expect an update to this plugin to include dailySchedule?

Yes, you can. I am in the process of integrating a new type of schedules. Work in progress. Can't give you any precise estimates, since I have my day-to-day job anyway.


Skipped tests are marked as Passed

Any tests which are marked as Skipped in Postman collection and when running these test using Newman on TeamCity pass the tests, this creates confusion in the overall result.
Please suggest if there is a workaround to handle this case or kindly provide a fix.

@leafle: I have opened a PR which would resolve this issue (#33).


Added tests to MiqReport::Generator#generate - calculating slope for daily trend

Added tests to MiqReport::Generator#generate - calculating slope for daily trend
@miq-bot add-label test, reporting
/cc @gtanzillo

@yrudman couple of comments above, but LGTM otherwise :thumbsup:

👍 LGTM


can't use localhost:8000/rest-auth/registration/ to add new user.

Using angular-django-registration-auth from "python manage.py runserver" (not gunicorn) I am able to utilize the /login/ api url "http://localhost:8000/rest-auth/login/".  But when I attempt to use the /registration/ api url "http://localhost:8000/rest-auth/registration/", I get HTTP 405 METHOD NOT ALLOWED, and a form showing only "Content:" and a textbox.
This is a new installation.  Here is my "requirements.txt" content:
Django==1.7.6
dj-database-url==0.3.0
dj-static==0.0.6
django-appconf==1.0.1
djangorestframework==3.0.5
django-rest-auth==0.3.4
django-allauth==0.19.1
drf-nested-routers==0.9.0
drf-extensions
gunicorn==19.1.1
six==1.9.0
static3==0.5.1
wsgiref==0.1.2
I believe I have correctly followed the instructions in "http://django-rest-auth.readthedocs.org/en/latest/installation.html#registration-optional" for INSTALLED_APPS , and myapp/urls.py.
Here are the relevant contents of myapp/settings.py:
INSTALLED_APPS = (
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
'rest_framework',
'rest_framework.authtoken',
'rest_auth',
'allauth',
'allauth.account',
'rest_auth.registration',
)
TEMPLATE_CONTEXT_PROCESSORS = (
# Required by allauth template tags
"django.core.context_processors.request",
# allauth specific context processors
"allauth.account.context_processors.account",
"allauth.socialaccount.context_processors.socialaccount",
)
AUTHENTICATION_BACKENDS = (
# Needed to login by username in Django admin, regardless of allauth
"django.contrib.auth.backends.ModelBackend",
# allauth specific authentication methods, such as login by e-mail
"allauth.account.auth_backends.AuthenticationBackend",
)
Thanks!

Facing the same issue. What I am able to figure out is that the /registration/ api doesn't exist in rest_auth.urls. Going through the docs here: http://django-rest-auth.readthedocs.org/en/latest/api_endpoints.html#registration it seems that using a custom signup form would be the better thing to do.

@ThomasGrzybowski Are you sure you are sending POST request to correct url?
You can also try python manage.py show_urls command from django extensions and make sure you have your urls configured properly.

The file "../lib/python3.2/site-packages/allauth/account/urls.py" has the code:
urlpatterns = patterns(
"",
url(r"^signup/$", views.signup, name="account_signup"),
But I'm not sure how to expose the "/signup/" api url for use.  It would be helpful if this was implemented as part of the django-rest-auth distribution :-)

But signup API is already exposed in rest_auth.registration app. Please see documentation http://django-rest-auth.readthedocs.org/en/latest/installation.html#registration-optional
If it doesn't help, please try out our demo project. This should be also very helpful http://django-rest-auth.readthedocs.org/en/latest/demo.html

@ThomasGrzybowski Did you figure out what was causing your issue? Was it improper configuration or something else?

The demo works fine with the /signup/ url. From the documentation I was
expecting to use /register/ for use with the angular-django-registration-auth
client.
From what I can tell, angular-django-registration-auth does not yet support
/signup/.
Thanks for your support,
Tom
On Wed, Mar 18, 2015 at 9:22 AM, Mateusz Sikora<EMAIL_ADDRESS>wrote:

@ThomasGrzybowski https://github.com/ThomasGrzybowski Did you figure
out what was causing your issue? Was it improper configuration or something
else?
—
Reply to this email directly or view it on GitHub
https://github.com/Tivix/django-rest-auth/issues/57#issuecomment-82968302
.

I'm confused. I think you are mixing up two urls. /signup/ from demo project is for serving template with signup form and inside this template you can find a form which send a POST request to /rest-auth/registration/ where django-rest-auth registration is handled.
Here are all urls from demo project https://github.com/Tivix/django-rest-auth/blob/master/demo/demo/urls.py
In my opinion if you still have this issue:

But when I attempt to use the /registration/ api url "http://localhost:8000/rest-auth/registration/", I get HTTP 405 METHOD NOT ALLOWED

then I think you still have improper url configuration and it's not an issue in django-rest-auth.

@ThomasGrzybowski Check this link out this Not sure if this is the case. The user is actually registered but you get a traceback error

I think this issue was closed even b4 it was solved I have the same issue using react and django, when i signup with rest-framework registration then it works but if i use axios to post data to django from localhost:8000 then it gives error Forbidden: /rest-auth/registration/
but using localhost:3000 which is the pure react with exact same code the user is registered, i came to believe that at the localhost:8000 django is trying to get the session key that is not suppose to even be getting since my authentication is suppose to be using token authentication
if this issue is to be delt with, someone to try using the restauth one page app like react front end under the django server port 8000 and see the error they are getting


Unable to convert onnx model to TRT model

I have converted this model "20180402-114759" for face recognition to onnx format with onnx==1.14.1. and When I want to convert the onnx model to TRT I get these errors:
"[E] Error[4]: [graphShapeAnalyzer.cpp::processCheck::862] Error Code 4: Internal Error (StatefulPartitionedCall/inception_resnet_v1/Conv2d_2a_3x3/Conv2D: spatial dimension of convolution/deconvolution output cannot be negative (build-time output dimension of axis 2 is -2))
[12/16/2023-15:52:45] [E] Engine could not be created from network
[12/16/2023-15:52:45] [E] Building engine failed
[12/16/2023-15:52:45] [E] Failed to create engine from model or file.
[12/16/2023-15:52:45] [E] Engine set up failed
&&&& FAILED TensorRT.trtexec [TensorRT v8601] # ...."
I use TensorRT 8.6 for CUDA 12.1. This doc said that for tensorrt 8.6 the onnxruntime should be 1.15 or higher. but I am not able to convert the tensorflow model to onnx model with onnx==1.15.0. and I face some errors. How can I fix this problem to successfully convert the tensorflow model to onnx and then TRT model.
Best Regards!

@k-khosravi can you provide the code you used for onnx conversion?


[Concurrency ABI] Add standard substitutions for _Concurrency types.

Introduce a second level of standard substitutions to the mangling,
all of the form Sc<character>, and use it to provide standard
substitutions for most of the _Concurrency types.
This is a precursor to rdar://78269642 and a good mangling-size
optimization in its own right.

@swift-ci please smoke test macOS


Grammatical error

In Section The Problem
In India, there is a problem of Electricity Outage every now and then, especially in some states. So,Elektra is an ML based Web App by which will be use for real-time monitoring of theElectricity Outages in an area and display them in form of maps, Dashboard with pie charts, line graph, etc, where people will be able to report the electricity outages in their area of the city, in response to which the Electricity Department will try to track and solve the fault and we are able to monitor and predict the frequency of Electricity Outage in our area or in any part of the city.
There are some error which i will like to fix as the wording dont make sence somewhere i will like to fix that issue after getting assigned !!

Can i work on this??

I would like to work on this issue under gssoc'21 .

I would like to work on this issue under gssoc'21 .

I am working on this sorry @shreya9301


Allow a function to be passed for action url meta param

Coverage remained the same at 100.0% when pulling 2ae249f0e33953fca44047debcb85f964690d37c on shodanuk:master into d669e8b483c686339a86656f6ac3f62267ec046b on viniciusdacal:master.

Awesome implementation! 👍


Allow password change on login if forced

System information:

Windows
DBeaver Community Version <IP_ADDRESS>202051448

Connection specification:

SAP HANA 2
JDBC

Describe the problem you're observing:
If password is required to be reset due to password expire, this cannot be done by DBeaver because initial login is not possible .
Steps to reproduce, if exist:
As an admin, reset the password for a certain user. When the user now tries to login, he is required to reset the password. This cannot be done via DBeaver. I have to log in via SAP HANA Studio.

Thank you for the idea.

might have similar rootcause as #14064

Here is the original error message. Is forced password reset possible for other database types like Oracle or MS SQL?
SQL-Fehler [414] [HY000]: SAP DBTech JDBC: [414]: user is forced to change password: alter password required for user

Changing the forced password works for Oracle in DBeaver.
And for some other databases: https://github.com/dbeaver/dbeaver/wiki/Change-current-user-password

same as #22206

I am working on this feature


Add UDS log to CNI plugin.

For #32437
Make CNI plugin also sends log to CNI install container. This PR also contains a fix to make log level really work for CNI network plugin, and a clean up of plugin log messages to make it really usable. Also make CNI integration test sends log to CNI daemonset.
At info level, CNI network plugin logs looks like the follow in the cni container for a pod: https://gist.githubusercontent.com/bianpengyuan/a7cabdc1651df1dd3709fd386176e0e0/raw/7f1760bb7f01f9b7347a451bf6cf0989ed6ccb53/cni-info.log. At debug level, CNI network plugin logs looks like: https://gist.githubusercontent.com/bianpengyuan/1e3a4b905935e92b35c05cd386d76d57/raw/842fc2c68cab38895319c58c2c72c019262fa9ff/cni-debug.log

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
38fad94d614c04989d934627a0134ed140d13d37
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
39278e3c0e78b38434c9b19b9b80213967074725
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
39278e3c0e78b38434c9b19b9b80213967074725
link
/test lint_istio

integ-cni-k8s-tests_istio
39278e3c0e78b38434c9b19b9b80213967074725
link
/test integ-cni-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
39278e3c0e78b38434c9b19b9b80213967074725
link
/test lint_istio

integ-cni-k8s-tests_istio
39278e3c0e78b38434c9b19b9b80213967074725
link
/test integ-cni-k8s-tests_istio

unit-tests_istio
39278e3c0e78b38434c9b19b9b80213967074725
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-cni-k8s-tests_istio
39278e3c0e78b38434c9b19b9b80213967074725
link
/test integ-cni-k8s-tests_istio

unit-tests_istio
9731ae604bb924feee69b7adc46162cab9fb3455
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Played around with this locally, we end up with a lot of logs like:
2021-07-09T15:26:37.662344Z     info    Running command: iptables-restore --noflush /tmp/iptables-rules-1625844397662294469.txt604761520
2021-07-09T15:26:37.667146Z     info    Writing following contents to rules file: /tmp/ip6tables-rules-1625844397667116264.txt133047631

2021-07-09T15:26:37.667215Z     info    Running command: ip6tables-restore --noflush /tmp/ip6tables-rules-1625844397667116264.txt133047631
2021-07-09T15:26:37.669162Z     info    Running command: iptables-save

It would be ideal if we had context (pod name) on all of these

@bianpengyuan: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-k8s-tests_istio

integ-cni-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-cni-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-k8s-tests_istio

integ-cni-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-cni-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-mc-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-k8s-tests_istio

integ-cni-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-cni-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-mc-k8s-tests_istio

integ-operator-controller-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-operator-controller-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-k8s-tests_istio

integ-cni-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-cni-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-mc-k8s-tests_istio

integ-operator-controller-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-k8s-tests_istio

integ-cni-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-cni-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-mc-k8s-tests_istio

integ-operator-controller-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test analyze-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-k8s-tests_istio

integ-cni-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-cni-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-mc-k8s-tests_istio

integ-operator-controller-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-ipv6-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-k8s-tests_istio

integ-cni-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-cni-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-mc-k8s-tests_istio

integ-operator-controller-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-k8s-tests_istio

integ-cni-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-cni-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-mc-k8s-tests_istio

integ-operator-controller-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-pilot-k8s-tests_istio

lint_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-k8s-tests_istio

integ-cni-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-cni-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-mc-k8s-tests_istio

integ-operator-controller-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-pilot-k8s-tests_istio

lint_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test lint_istio

release-test_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test release-test_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-k8s-tests_istio

integ-cni-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-cni-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-mc-k8s-tests_istio

integ-operator-controller-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-pilot-k8s-tests_istio

lint_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test lint_istio

release-test_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test release-test_istio

release-notes_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-k8s-tests_istio

integ-cni-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-cni-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-mc-k8s-tests_istio

integ-operator-controller-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-pilot-k8s-tests_istio

lint_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test lint_istio

release-test_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test release-test_istio

release-notes_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test release-notes_istio

integ-security-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-k8s-tests_istio

integ-cni-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-cni-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-mc-k8s-tests_istio

integ-operator-controller-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-pilot-k8s-tests_istio

lint_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test lint_istio

release-test_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test release-test_istio

release-notes_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test release-notes_istio

integ-security-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-security-k8s-tests_istio

gencheck_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-k8s-tests_istio

integ-cni-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-cni-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-mc-k8s-tests_istio

integ-operator-controller-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-pilot-k8s-tests_istio

lint_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test lint_istio

release-test_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test release-test_istio

release-notes_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test release-notes_istio

integ-security-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-security-k8s-tests_istio

gencheck_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test gencheck_istio

integ-helm-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-helm-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-k8s-tests_istio

integ-cni-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-cni-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-mc-k8s-tests_istio

integ-operator-controller-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-pilot-k8s-tests_istio

lint_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test lint_istio

release-test_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test release-test_istio

release-notes_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test release-notes_istio

integ-security-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-security-k8s-tests_istio

gencheck_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test gencheck_istio

integ-helm-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-helm-tests_istio

integ-multicluster-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-k8s-tests_istio

integ-cni-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-cni-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-mc-k8s-tests_istio

integ-operator-controller-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-pilot-k8s-tests_istio

lint_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test lint_istio

release-test_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test release-test_istio

release-notes_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test release-notes_istio

integ-security-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-security-k8s-tests_istio

gencheck_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test gencheck_istio

integ-helm-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-helm-tests_istio

integ-multicluster-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-multicluster-k8s-tests_istio

integ-pilot-multicluster-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-k8s-tests_istio

integ-cni-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-cni-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-multicluster-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-security-multicluster-tests_istio

integ-ipv6-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-pilot-k8s-tests_istio

release-test_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test release-test_istio

integ-security-k8s-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-security-k8s-tests_istio

integ-helm-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-helm-tests_istio

integ-pilot-multicluster-tests_istio
833c48e89b005f0d286efdb24bd5d49057ab4fc6
link
/test integ-pilot-multicluster-tests_istio

unit-tests_istio
53d59205df7de94d24d3a0380687fff973d93a56
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn @mandarjog re pod identifier for iptables log, I've added two separator log lines to denote start and end of iptables output for a pod. https://gist.githubusercontent.com/bianpengyuan/28de8f4a7c6d943b9d63ee9431a456c8/raw/faceb7d46257cfe5f90aa7fa32fa3c78291df458/cni-log-new.log is what it looks like now.
CNI/Iptables logs from different pods won't interleave because

CNI/iptables logs for a pod is reported in a single request
the logger locks the log printing for each request.

If we find out logs from CNI/IPTables is too large and needs to be divided into separated requests, we can revisit and think about ways to add identifier to each log lines.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
ae815c08ffdd10674d052e34db97d38f914493bb
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@mandarjog @howardjohn gentle ping for review, thanks!

/cherry-pick release-1.11

@bianpengyuan: #33926 failed to apply on top of branch "release-1.11":
Applying: Add UDS log to CNI plugin.
.git/rebase-apply/patch:722: trailing whitespace.
          "log_uds_address": "__LOG_UDS_ADDRESS__",
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	cni/pkg/cmd/root.go
M	cni/pkg/install/cniconfig.go
M	cni/pkg/plugin/iptables.go
Falling back to patching base and 3-way merge...
Auto-merging cni/pkg/plugin/iptables.go
CONFLICT (content): Merge conflict in cni/pkg/plugin/iptables.go
Auto-merging cni/pkg/install/cniconfig.go
Auto-merging cni/pkg/cmd/root.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Add UDS log to CNI plugin.
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.11

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@bianpengyuan: new issue created for failed cherrypick: #34087

In response to this:

/cherry-pick release-1.11

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/cherry-pick release-1.11

@bianpengyuan: #33926 failed to apply on top of branch "release-1.11":
Applying: Add UDS log to CNI plugin.
.git/rebase-apply/patch:722: trailing whitespace.
          "log_uds_address": "__LOG_UDS_ADDRESS__",
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	cni/pkg/cmd/root.go
M	cni/pkg/install/cniconfig.go
M	cni/pkg/plugin/iptables.go
Falling back to patching base and 3-way merge...
Auto-merging cni/pkg/plugin/iptables.go
CONFLICT (content): Merge conflict in cni/pkg/plugin/iptables.go
Auto-merging cni/pkg/install/cniconfig.go
Auto-merging cni/pkg/cmd/root.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Add UDS log to CNI plugin.
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.11

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@bianpengyuan: new issue created for failed cherrypick: #34094

In response to this:

/cherry-pick release-1.11

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


How many neurons are there in the last fully-connected layer of R-Net?

In the paper, you said "we use a ResNet-50 network [22] to regress these coefficients by modifying the last fully-connected layer to 239 neurons." , but when I debug your code, and I found the count of output coefficients of R-Net is 257 ? I think that's because the count of lighting coefficients, in your paper it should be 9, but in your code, it's 27. which is right?

Yes, we change lighting coefficients from 9 to 27 so that illumination can be colored light. We find that it is better than assuming a white scene light under some extreme cases, where textures have to compensate for light color and lead to strange results.

OK，thanks for your answer. And I got another question when I tried to generate the projection image by using rasterizer method you mentioned in your paper, and I found that some vertex's color (defined in face_color) may out of range 255, what should I do with this strange color?

We simply clip face colors within the range of 0 to 255. While training, we do the same procedure before sending reconstruction image to facenet for feature extraction.

Got it and thank you


#8 Fixed duplicate import directive

I have separated the import directive into another liquid template.
Closes https://github.com/RSuter/SigSpec/issues/8

Updated PR with NJS alignment.

Thanks for the PR!

How are you using this project ATM?

Hi! Thanks for the quick fix!
We are developing microservices with asp.net core and my team is responsible for backend services. We are using openapi and Swagger to generate C# controllers and TypeScript clients for the API between frontend and backend. Now we are implementing server push functionality using SignalR. So we wanted to do something similar.
We have a project with abstract hub classes and we generate nuget package from it and also using SigSpec we generate the TypeScript to be used by Frontend team.

And you are using the sigspec code as copy in your solution? You know that this is an experimental project?

Yeah I know it's experimental.  I have made a nuget package out of it (for our dedicated nuget server).
Is that a problem? I know, that you cannot guarantee anything, but I don't mind as long as the source code is available. It's not a crucial functionality, we can always write the TypeScript manually, but I like this tool.
Are you OK with it?

Of course this is fine, but please dont publish an “inofficial” public nuget package :-)

No I am not planning on publishing anything, It is really our private company nuget server.
Thanks again for all your work!


Add contributing guideline and test because of semantic-release

This project uses semanctc-release to release, so it is import to add commit message correctly.
To know everyone this, I should add contributing guideline or ci for test that checks commit message.

The commit message rule is  commitlint-conventional .
https://github.com/conventional-changelog/commitlint#what-is-commitlint


updated readme and requirements.txt for easier installation.

Thankyou for doing this! To make it easier for me to manage I have taken your updates and just pasted them into my project to prevent merging and github headaches..


Adjust the Getting Started guide

I've just cloned the project and tried to get the project running as described in the README. I needed to rerun a few of the commands before it actually worked. Here is what I did:
git clone git@github.com:supermario/lamdera-realworld.git
cd lamdera-realworld
lamdera reset
elm-spa make
lamdera reset
lamdera make src/Frontend.elm
elm-spa make
lamdera live

Hey @Orasund – thanks for pointing this out!
It seems the issue I didn't spot here was that elm-spa make isn't using the Lamdera compiler. Unfortunately it also doesn't seem to support the ELM_COMPILER env override.
In any case, this made me realise that .elm-spa source needs to be committed anyway for a Lamdera deploy to succeed.
Once that's the case and that source is already present on checkout, building the project should be a lot simpler and not require the elm-spa make part, thus avoiding the build cache conflicts, so I've updated the readme to that effect for now.
Let me know if that helps, or if you still have issues! 😊

I've recloned and followed the constructions. Worked perfectly 👌


Need a manual restart to do the job

Hello,
When i start OpenWrt, the deamon is running but don't mirror any packet.
If i manually stop / start the process everything work as expected.
Any idea ?
Why did you choose priority 83 ?
OpenWrt IP : <IP_ADDRESS>
My config :
option 'target' '<IP_ADDRESS>'
option 'source_ports' 'eth0,wlan0,wlan1'
option 'filter' ''
option 'promiscuous' '1'
option 'protocol' 'TEE'

Sorry for the late reply. I'm assuming you're using version 1.4.2-1 and will mark the daemon startup issues as a bug. As to the choice of 83, that was a design decision from the original developer and I'm not sure why that was selected. I imagine that was to ensure all the other init scripts ran before port-mirroring. Do you have a recommendation for what it should be?

Could not reproduce bug.