GPU Kernel performance test with empty parameter without model load

Branch/Tag/Commit
main
Docker Image Version
nvcr.io/nvidia/pytorch:22.09-py3
GPU name
A40
CUDA Driver
525.105.17
Reproduced Steps
The command I used to set up my environment is as follows :
1. docker run -it --gpus=all --ipc=host --net=host --name=faster_transformer_performance_test  nvcr.io/nvidia/pytorch:22.09-py3 bash
2. git clone https://github.com/NVIDIA/FasterTransformer.git
3. mkdir -p FasterTransformer/build
4. cd FasterTransformer/build
5. git submodule init && git submodule update
6. cmake -DSM=86 -DCMAKE_BUILD_TYPE=Release -DBUILD_PYT=ON -DBUILD_MULTI_GPU=ON ..
7. make -j48
8. pip install -r ../examples/pytorch/gpt/requirement.txt
9. wget https://s3.amazonaws.com/models.huggingface.co/bert/gpt2-vocab.json -P ../models
10. wget https://s3.amazonaws.com/models.huggingface.co/bert/gpt2-merges.txt -P ../models

root@S4:/workspace/FasterTransformer# git log
commit 0c128050e14b65d72b3c28c0324cc9db6f677be8 (HEAD -> main, origin/main, origin/HEAD)
Author: byshiue<EMAIL_ADDRESS>Date:   Mon Apr 17 11:04:38 2023 +0800

    Update T5DecodingWeight.cc

    fix: fix loading bug of t5

root@S4:/workspace/FasterTransformer/build# nvidia-smi
Tue Apr 18 05:02:38 2023
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 525.105.17   Driver Version: 525.105.17   CUDA Version: 12.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA A40          Off  | 00000000:01:00.0 Off |                    0 |
|  0%   28C    P8    11W / 300W |      0MiB / 46068MiB |      0%      Default |

If I run the following command, I get the error. (which is as expected since I did not download the model checkpoint)
Of course I have tested the task with megatron checkpoint and it worked like a charm. :)
python ../examples/pytorch/gpt/multi_gpu_gpt_example.py --data_type fp16 --max_batch_size=32 --input_len=32 --output_len=32 --shared_contexts_ratio=0

Traceback (most recent call last):
  File "../examples/pytorch/gpt/multi_gpu_gpt_example.py", line 364, in <module>
    main()
  File "/opt/conda/lib/python3.8/site-packages/torch/autograd/grad_mode.py", line 27, in decorate_context
    return func(*args, **kwargs)
  File "../examples/pytorch/gpt/multi_gpu_gpt_example.py", line 253, in main
    if not gpt.load(ckpt_path=args.ckpt_path):
  File "/workspace/FasterTransformer/examples/pytorch/gpt/../../../examples/pytorch/gpt/utils/gpt.py", line 540, in load
    is_load = self.weights.load(ckpt_path, tp_rank=self.tensor_para_rank,
  File "/workspace/FasterTransformer/examples/pytorch/gpt/../../../examples/pytorch/gpt/utils/gpt.py", line 262, in load
    raise FileNotFoundError(f"Failed to find {ckpt_path}")
FileNotFoundError: Failed to find ../models/megatron-models/c-model/345m/1-gpu

However, what I want is GPU Kernel performance test with various configuration. In fact, I don't need the pretrained model for this task; I just need the shape of them.
And since it is quite a tiring job to create a new checkpoint for every configuration (Num_head, Head_Size, Num_layers, etc), I wanted to test with an empty parameter.
So I have looked through the code(https://github.com/NVIDIA/FasterTransformer/blob/169b8df80d568bf2337a35088c3979d207ab4495/examples/pytorch/gpt/utils/gpt.py#L105), and it seems like the feature was already implemented.
There, I have attempt to manually remove the model load call, just to check whether it would run without it.
root@S4:/workspace/FasterTransformer/build# git diff
diff --git a/examples/pytorch/gpt/multi_gpu_gpt_example.py b/examples/pytorch/gpt/multi_gpu_gpt_example.py
index 89330b2..82647c9 100644
--- a/examples/pytorch/gpt/multi_gpu_gpt_example.py
+++ b/examples/pytorch/gpt/multi_gpu_gpt_example.py
@@ -250,8 +250,8 @@ def main():
                           expert_num=expert_num,
                           moe_k=moe_k,
                           moe_layer_index=moe_layer_index)
-        if not gpt.load(ckpt_path=args.ckpt_path):
-            print("[WARNING] Checkpoint file not found. Model loading is skipped.")
+        #if not gpt.load(ckpt_path=args.ckpt_path):
+        #    print("[WARNING] Checkpoint file not found. Model loading is skipped.")
     else:
         assert moe_layer_index == []
         gpt = gpt_decoder.Gpt(

After the modification, I get the following error if I run the code.
export FT_DEBUG_LEVEL=DEBUG
export FT_LOG_LEVEL=DEBUG
python ../examples/pytorch/gpt/multi_gpu_gpt_example.py --data_type fp16 --max_batch_size=32 --input_len=32 --output_len=32 --shared_contexts_ratio=0

[FT][ERROR] [FT][ERROR] CUDA runtime error: an illegal memory access was encountered /workspace/FasterTransformer/src/fastertransformer/models/multi_gpu_gpt/ParallelGpt.cc:1264

I've attach the full logs(https://github.com/92hyungjun/test1231/blob/5b7345b781ea5f2fdcc65daf27fd7e75954025a5/log.txt#L4357).
Can you instruct me a way to use empty tensor parameter without loading the model checkpoint, for the GPU kernel performance test?
Thank you. :)

If you want to run benchmark with random weight, you can use multi_gpu_gpt_example.cc.

I will try with c++ code. However, do you have a plan to implement the feature in python "multi_gpu_gpt_example.py" ?

We will consider.


Add subtle bg colour change when hovering over table rows

Obviously we want to use the same style everywhere.

Pretty sure it didn't before but it does now.


add promtail_extra_args

Hi there,
to be able to set an extra label, for example hostname this adds the possbility to define extra-args for the binary within the service file.

Thank you for your contribution - this looks good to me overall
Some nitpicks, can you please:

squash the commits
please provide the commit as conventional commit  - may I suggest to use feat: add promtail_extra_args variable to allow configuring the service arguments

Can I ask, if you have tested the feature already?

Hi there,
squashed & reworded =)
it is already testet in mutliple deplyoments.


BETA Testing / Microsoft Collaborate

Dear Sir / Madam
I am trying to set up my Microsoft Collaborate Migration, however I am having some problems and would be appreciative if you good sort them out.
I dont see any of my programs I have participated in or wish to continue participating with, and therefore would like to know how to do this please i.e Microsoft Office, Microsoft Windows Service Pack, Microsoft SQL Server etc.
I hope you can sort this out for me please and tell me what I need to do.
Yours Faithfully
Oliver Hatton
Tel. +44 1275 373449
Email<EMAIL_ADDRESS>

Hi Oliver,
Can you clarify the problems you are having? I’m not sure what exactly you need help sorting out.
Thanks,
-Mike
From: Olio03<EMAIL_ADDRESS>Sent: Wednesday, May 2, 2018 12:30 AM
To: MicrosoftDocs/MicrosoftCollaboratePortal<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Dear Sir / Madam
I am trying to set up my Microsoft Collaborate Migration, however I am having some problems and would be appreciative if you good sort them out.
I dont see any of my programs I have participated in or wish to continue participating with, and therefore would like to know how to do this please i.e Microsoft Office, Microsoft Windows Service Pack, Microsoft SQL Server etc.
I hope you can sort this out for me please and tell me what I need to do.
Yours Faithfully
Oliver Hatton
Tel. +44 1275 373449
Email: olio03<EMAIL_ADDRESS>—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FMicrosoftCollaboratePortal%2Fissues%2F69&data=02|01|mimcco%40microsoft.com|a864085dffe147d48ebd08d5affe88e1|72f988bf86f141af91ab2d7cd011db47|1|0|636608430117306711&sdata=4fz3hHwM8YUyea%2Fu4IArq%2B23c%2FPAZoX9HlEYZDtQcH8%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAfv1kC8-XLK51hZb9EavR6QsjuhMbqe9ks5tuWCBgaJpZM4Tu-wp&data=02|01|mimcco%40microsoft.com|a864085dffe147d48ebd08d5affe88e1|72f988bf86f141af91ab2d7cd011db47|1|0|636608430117316716&sdata=rg6MN6dAG%2B2%2BKbetR7CcqtbNy3hWfnHOOeIHeCMKzeo%3D&reserved=0.

Hi Mike, any update? Ive also heard there is Microsoft Office 2019 coming this year? Can I be a tester?

Hi Oliver,
Programs are operated individually by the various program administrators within Microsoft. Just as it was with Connect, Collaborate is just the platform that the programs are run on. I work on the Collaborate platform and don’t have a lot of insights into the various requirements for each program. I do know this, all of the programs are by invite only so the program administrators usually contact the people/companies they want to participate. If you were part of a program on Connect that has moved to Collaborate, you should be able to contact whoever you always contacted to get more information. If the Connect program you were a part of is not on Collaborate, it means that the program has closed.
I have no idea if there is a beta testing program for Office 2019…
Sorry I can’t be much help.
Regards,
Mike McCoy
From: Olio03<EMAIL_ADDRESS>Sent: Monday, May 14, 2018 9:05 PM
To: MicrosoftDocs/MicrosoftCollaboratePortal<EMAIL_ADDRESS>Cc: Mike McCoy (WDG<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Mike, any update? Ive also heard there is Microsoft Office 2019 coming this year? Can I be a tester?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FMicrosoftCollaboratePortal%2Fissues%2F69%23issuecomment-389036223&data=02|01|mimcco%40microsoft.com|6dbb8830bb9b4931350f08d5ba190afd|72f988bf86f141af91ab2d7cd011db47|1|0|636619539082681664&sdata=BVLETxnBmh%2FKJMzqbrDYSMAwXfZ0OquCxKfNnW8FIj4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAfv1kEt6xdwTX9aBnreQGxfM4wbcssZPks5tylPwgaJpZM4Tu-wp&data=02|01|mimcco%40microsoft.com|6dbb8830bb9b4931350f08d5ba190afd|72f988bf86f141af91ab2d7cd011db47|1|0|636619539082681664&sdata=VyXeHVSdheWlwwdq2nxZqMidVDPtGrLyPTX1FAU9Yu4%3D&reserved=0.

Mike,
Their email address<EMAIL_ADDRESS>doesnt work.
Oliver

From: Mike McCoy (WDG<EMAIL_ADDRESS>Sent: 15 May 2018 15:11:23
To: MicrosoftDocs/MicrosoftCollaboratePortal
Cc: Olio03; Author
Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Oliver,
Programs are operated individually by the various program administrators within Microsoft. Just as it was with Connect, Collaborate is just the platform that the programs are run on. I work on the Collaborate platform and don’t have a lot of insights into the various requirements for each program. I do know this, all of the programs are by invite only so the program administrators usually contact the people/companies they want to participate. If you were part of a program on Connect that has moved to Collaborate, you should be able to contact whoever you always contacted to get more information. If the Connect program you were a part of is not on Collaborate, it means that the program has closed.
I have no idea if there is a beta testing program for Office 2019…
Sorry I can’t be much help.
Regards,
Mike McCoy
From: Olio03<EMAIL_ADDRESS>Sent: Monday, May 14, 2018 9:05 PM
To: MicrosoftDocs/MicrosoftCollaboratePortal<EMAIL_ADDRESS>Cc: Mike McCoy (WDG<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Mike, any update? Ive also heard there is Microsoft Office 2019 coming this year? Can I be a tester?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FMicrosoftCollaboratePortal%2Fissues%2F69%23issuecomment-389036223&data=02|01|mimcco%40microsoft.com|6dbb8830bb9b4931350f08d5ba190afd|72f988bf86f141af91ab2d7cd011db47|1|0|636619539082681664&sdata=BVLETxnBmh%2FKJMzqbrDYSMAwXfZ0OquCxKfNnW8FIj4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAfv1kEt6xdwTX9aBnreQGxfM4wbcssZPks5tylPwgaJpZM4Tu-wp&data=02|01|mimcco%40microsoft.com|6dbb8830bb9b4931350f08d5ba190afd|72f988bf86f141af91ab2d7cd011db47|1|0|636619539082681664&sdata=VyXeHVSdheWlwwdq2nxZqMidVDPtGrLyPTX1FAU9Yu4%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/MicrosoftCollaboratePortal/issues/69#issuecomment-389181344, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlGj3LjF0mqh4gXohRio2uZAeZT7kQAzks5tyuILgaJpZM4Tu-wp.

Hi Oliver,
I was able to find the following links:
Read this one first: https://go.microsoft.com/fwlink/?linkid=872263
Then go to this: https://go.microsoft.com/fwlink/?linkid=872092
Thanks,
-Mike
From: Olio03<EMAIL_ADDRESS>Sent: Tuesday, May 15, 2018 9:58 PM
To: MicrosoftDocs/MicrosoftCollaboratePortal<EMAIL_ADDRESS>Cc: Mike McCoy (WDG<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Mike,
Their email address, officeconnectteam<EMAIL_ADDRESS>doesnt work.
Oliver

From: Mike McCoy (WDG) <notifications<EMAIL_ADDRESS>Sent: 15 May 2018 15:11:23
To: MicrosoftDocs/MicrosoftCollaboratePortal
Cc: Olio03; Author
Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Oliver,
Programs are operated individually by the various program administrators within Microsoft. Just as it was with Connect, Collaborate is just the platform that the programs are run on. I work on the Collaborate platform and don’t have a lot of insights into the various requirements for each program. I do know this, all of the programs are by invite only so the program administrators usually contact the people/companies they want to participate. If you were part of a program on Connect that has moved to Collaborate, you should be able to contact whoever you always contacted to get more information. If the Connect program you were a part of is not on Collaborate, it means that the program has closed.
I have no idea if there is a beta testing program for Office 2019…
Sorry I can’t be much help.
Regards,
Mike McCoy
From: Olio03 <notifications<EMAIL_ADDRESS>Sent: Monday, May 14, 2018 9:05 PM
To: MicrosoftDocs/MicrosoftCollaboratePortal <MicrosoftCollaboratePortal<EMAIL_ADDRESS>Cc: Mike McCoy (WDG) <mimcco<EMAIL_ADDRESS>Comment <comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Mike, any update? Ive also heard there is Microsoft Office 2019 coming this year? Can I be a tester?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FMicrosoftCollaboratePortal%2Fissues%2F69%23issuecomment-389036223&data=02|01|mimcco%40microsoft.com|6dbb8830bb9b4931350f08d5ba190afd|72f988bf86f141af91ab2d7cd011db47|1|0|636619539082681664&sdata=BVLETxnBmh%2FKJMzqbrDYSMAwXfZ0OquCxKfNnW8FIj4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAfv1kEt6xdwTX9aBnreQGxfM4wbcssZPks5tylPwgaJpZM4Tu-wp&data=02|01|mimcco%40microsoft.com|6dbb8830bb9b4931350f08d5ba190afd|72f988bf86f141af91ab2d7cd011db47|1|0|636619539082681664&sdata=VyXeHVSdheWlwwdq2nxZqMidVDPtGrLyPTX1FAU9Yu4%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/MicrosoftCollaboratePortal/issues/69#issuecomment-389181344, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlGj3LjF0mqh4gXohRio2uZAeZT7kQAzks5tyuILgaJpZM4Tu-wp.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FMicrosoftCollaboratePortal%2Fissues%2F69%23issuecomment-389394471&data=02|01|mimcco%40microsoft.com|9e13db248b944799e45908d5bae99967|72f988bf86f141af91ab2d7cd011db47|1|0|636620434830579316&sdata=A4J%2BGqO7i6gtz0mfpnDism%2BTSJxuuD1qkfQEbgzhw78%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAfv1kMXjTfv_DIC8eujR5fxVtXP3mXwnks5ty7HYgaJpZM4Tu-wp&data=02|01|mimcco%40microsoft.com|9e13db248b944799e45908d5bae99967|72f988bf86f141af91ab2d7cd011db47|1|0|636620434830579316&sdata=EpnGclFL1Q7Y1zO40aEKJLt1sPQkzoxQsowwZHxzhIM%3D&reserved=0.

Hi Mike. I think ive got it just trying to work out where the packages are to download for the .exe
Thanks in the mean time.
Oliver

From: Mike McCoy (WDG<EMAIL_ADDRESS>Sent: 16 May 2018 23:05:08
To: MicrosoftDocs/MicrosoftCollaboratePortal
Cc: Olio03; Author
Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Oliver,
I was able to find the following links:
Read this one first: https://go.microsoft.com/fwlink/?linkid=872263
Then go to this: https://go.microsoft.com/fwlink/?linkid=872092
Thanks,
-Mike
From: Olio03<EMAIL_ADDRESS>Sent: Tuesday, May 15, 2018 9:58 PM
To: MicrosoftDocs/MicrosoftCollaboratePortal<EMAIL_ADDRESS>Cc: Mike McCoy (WDG<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Mike,
Their email address, officeconnectteam<EMAIL_ADDRESS>doesnt work.
Oliver

From: Mike McCoy (WDG) <notifications<EMAIL_ADDRESS>Sent: 15 May 2018 15:11:23
To: MicrosoftDocs/MicrosoftCollaboratePortal
Cc: Olio03; Author
Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Oliver,
Programs are operated individually by the various program administrators within Microsoft. Just as it was with Connect, Collaborate is just the platform that the programs are run on. I work on the Collaborate platform and don’t have a lot of insights into the various requirements for each program. I do know this, all of the programs are by invite only so the program administrators usually contact the people/companies they want to participate. If you were part of a program on Connect that has moved to Collaborate, you should be able to contact whoever you always contacted to get more information. If the Connect program you were a part of is not on Collaborate, it means that the program has closed.
I have no idea if there is a beta testing program for Office 2019…
Sorry I can’t be much help.
Regards,
Mike McCoy
From: Olio03 <notifications<EMAIL_ADDRESS>Sent: Monday, May 14, 2018 9:05 PM
To: MicrosoftDocs/MicrosoftCollaboratePortal <MicrosoftCollaboratePortal<EMAIL_ADDRESS>Cc: Mike McCoy (WDG) <mimcco<EMAIL_ADDRESS>Comment <comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Mike, any update? Ive also heard there is Microsoft Office 2019 coming this year? Can I be a tester?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FMicrosoftCollaboratePortal%2Fissues%2F69%23issuecomment-389036223&data=02|01|mimcco%40microsoft.com|6dbb8830bb9b4931350f08d5ba190afd|72f988bf86f141af91ab2d7cd011db47|1|0|636619539082681664&sdata=BVLETxnBmh%2FKJMzqbrDYSMAwXfZ0OquCxKfNnW8FIj4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAfv1kEt6xdwTX9aBnreQGxfM4wbcssZPks5tylPwgaJpZM4Tu-wp&data=02|01|mimcco%40microsoft.com|6dbb8830bb9b4931350f08d5ba190afd|72f988bf86f141af91ab2d7cd011db47|1|0|636619539082681664&sdata=VyXeHVSdheWlwwdq2nxZqMidVDPtGrLyPTX1FAU9Yu4%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/MicrosoftCollaboratePortal/issues/69#issuecomment-389181344, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlGj3LjF0mqh4gXohRio2uZAeZT7kQAzks5tyuILgaJpZM4Tu-wp.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FMicrosoftCollaboratePortal%2Fissues%2F69%23issuecomment-389394471&data=02|01|mimcco%40microsoft.com|9e13db248b944799e45908d5bae99967|72f988bf86f141af91ab2d7cd011db47|1|0|636620434830579316&sdata=A4J%2BGqO7i6gtz0mfpnDism%2BTSJxuuD1qkfQEbgzhw78%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAfv1kMXjTfv_DIC8eujR5fxVtXP3mXwnks5ty7HYgaJpZM4Tu-wp&data=02|01|mimcco%40microsoft.com|9e13db248b944799e45908d5bae99967|72f988bf86f141af91ab2d7cd011db47|1|0|636620434830579316&sdata=EpnGclFL1Q7Y1zO40aEKJLt1sPQkzoxQsowwZHxzhIM%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/MicrosoftCollaboratePortal/issues/69#issuecomment-389680711, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlGj3Hv8Cefti3WzD_sCTZGdLQzd1l9Tks5tzKKUgaJpZM4Tu-wp.

Hi Mike
Just a quick question, I am now a member of the office 2019 testing, but im having trouble activating it, do I use the volume code( it doesn't accept it) or what do I do?
Thanks
Oliver

From: Mike McCoy (WDG<EMAIL_ADDRESS>Sent: 16 May 2018 23:05
To: MicrosoftDocs/MicrosoftCollaboratePortal
Cc: Olio03; Author
Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Oliver,
I was able to find the following links:
Read this one first: https://go.microsoft.com/fwlink/?linkid=872263
Then go to this: https://go.microsoft.com/fwlink/?linkid=872092
Thanks,
-Mike
From: Olio03<EMAIL_ADDRESS>Sent: Tuesday, May 15, 2018 9:58 PM
To: MicrosoftDocs/MicrosoftCollaboratePortal<EMAIL_ADDRESS>Cc: Mike McCoy (WDG<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Mike,
Their email address, officeconnectteam<EMAIL_ADDRESS>doesnt work.
Oliver

From: Mike McCoy (WDG) <notifications<EMAIL_ADDRESS>Sent: 15 May 2018 15:11:23
To: MicrosoftDocs/MicrosoftCollaboratePortal
Cc: Olio03; Author
Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Oliver,
Programs are operated individually by the various program administrators within Microsoft. Just as it was with Connect, Collaborate is just the platform that the programs are run on. I work on the Collaborate platform and don’t have a lot of insights into the various requirements for each program. I do know this, all of the programs are by invite only so the program administrators usually contact the people/companies they want to participate. If you were part of a program on Connect that has moved to Collaborate, you should be able to contact whoever you always contacted to get more information. If the Connect program you were a part of is not on Collaborate, it means that the program has closed.
I have no idea if there is a beta testing program for Office 2019…
Sorry I can’t be much help.
Regards,
Mike McCoy
From: Olio03 <notifications<EMAIL_ADDRESS>Sent: Monday, May 14, 2018 9:05 PM
To: MicrosoftDocs/MicrosoftCollaboratePortal <MicrosoftCollaboratePortal<EMAIL_ADDRESS>Cc: Mike McCoy (WDG) <mimcco<EMAIL_ADDRESS>Comment <comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Mike, any update? Ive also heard there is Microsoft Office 2019 coming this year? Can I be a tester?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FMicrosoftCollaboratePortal%2Fissues%2F69%23issuecomment-389036223&data=02|01|mimcco%40microsoft.com|6dbb8830bb9b4931350f08d5ba190afd|72f988bf86f141af91ab2d7cd011db47|1|0|636619539082681664&sdata=BVLETxnBmh%2FKJMzqbrDYSMAwXfZ0OquCxKfNnW8FIj4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAfv1kEt6xdwTX9aBnreQGxfM4wbcssZPks5tylPwgaJpZM4Tu-wp&data=02|01|mimcco%40microsoft.com|6dbb8830bb9b4931350f08d5ba190afd|72f988bf86f141af91ab2d7cd011db47|1|0|636619539082681664&sdata=VyXeHVSdheWlwwdq2nxZqMidVDPtGrLyPTX1FAU9Yu4%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/MicrosoftCollaboratePortal/issues/69#issuecomment-389181344, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlGj3LjF0mqh4gXohRio2uZAeZT7kQAzks5tyuILgaJpZM4Tu-wp.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FMicrosoftCollaboratePortal%2Fissues%2F69%23issuecomment-389394471&data=02|01|mimcco%40microsoft.com|9e13db248b944799e45908d5bae99967|72f988bf86f141af91ab2d7cd011db47|1|0|636620434830579316&sdata=A4J%2BGqO7i6gtz0mfpnDism%2BTSJxuuD1qkfQEbgzhw78%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAfv1kMXjTfv_DIC8eujR5fxVtXP3mXwnks5ty7HYgaJpZM4Tu-wp&data=02|01|mimcco%40microsoft.com|9e13db248b944799e45908d5bae99967|72f988bf86f141af91ab2d7cd011db47|1|0|636620434830579316&sdata=EpnGclFL1Q7Y1zO40aEKJLt1sPQkzoxQsowwZHxzhIM%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/MicrosoftCollaboratePortal/issues/69#issuecomment-389680711, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlGj3Hv8Cefti3WzD_sCTZGdLQzd1l9Tks5tzKKUgaJpZM4Tu-wp.

Hi Mike
Just another thing, where / how do I access the Microsoft Office 2019 CDN.
Can you let me know please.
Oliver

From: Olio03 Olio03<EMAIL_ADDRESS>Sent: 17 May 2018 17:37
To: MicrosoftDocs/MicrosoftCollaboratePortal
Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Mike
Just a quick question, I am now a member of the office 2019 testing, but im having trouble activating it, do I use the volume code( it doesn't accept it) or what do I do?
Thanks
Oliver

From: Mike McCoy (WDG<EMAIL_ADDRESS>Sent: 16 May 2018 23:05
To: MicrosoftDocs/MicrosoftCollaboratePortal
Cc: Olio03; Author
Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Oliver,
I was able to find the following links:
Read this one first: https://go.microsoft.com/fwlink/?linkid=872263
Then go to this: https://go.microsoft.com/fwlink/?linkid=872092
Thanks,
-Mike
From: Olio03<EMAIL_ADDRESS>Sent: Tuesday, May 15, 2018 9:58 PM
To: MicrosoftDocs/MicrosoftCollaboratePortal<EMAIL_ADDRESS>Cc: Mike McCoy (WDG<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Mike,
Their email address, officeconnectteam<EMAIL_ADDRESS>doesnt work.
Oliver

From: Mike McCoy (WDG) <notifications<EMAIL_ADDRESS>Sent: 15 May 2018 15:11:23
To: MicrosoftDocs/MicrosoftCollaboratePortal
Cc: Olio03; Author
Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Oliver,
Programs are operated individually by the various program administrators within Microsoft. Just as it was with Connect, Collaborate is just the platform that the programs are run on. I work on the Collaborate platform and don’t have a lot of insights into the various requirements for each program. I do know this, all of the programs are by invite only so the program administrators usually contact the people/companies they want to participate. If you were part of a program on Connect that has moved to Collaborate, you should be able to contact whoever you always contacted to get more information. If the Connect program you were a part of is not on Collaborate, it means that the program has closed.
I have no idea if there is a beta testing program for Office 2019…
Sorry I can’t be much help.
Regards,
Mike McCoy
From: Olio03 <notifications<EMAIL_ADDRESS>Sent: Monday, May 14, 2018 9:05 PM
To: MicrosoftDocs/MicrosoftCollaboratePortal <MicrosoftCollaboratePortal<EMAIL_ADDRESS>Cc: Mike McCoy (WDG) <mimcco<EMAIL_ADDRESS>Comment <comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Mike, any update? Ive also heard there is Microsoft Office 2019 coming this year? Can I be a tester?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FMicrosoftCollaboratePortal%2Fissues%2F69%23issuecomment-389036223&data=02|01|mimcco%40microsoft.com|6dbb8830bb9b4931350f08d5ba190afd|72f988bf86f141af91ab2d7cd011db47|1|0|636619539082681664&sdata=BVLETxnBmh%2FKJMzqbrDYSMAwXfZ0OquCxKfNnW8FIj4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAfv1kEt6xdwTX9aBnreQGxfM4wbcssZPks5tylPwgaJpZM4Tu-wp&data=02|01|mimcco%40microsoft.com|6dbb8830bb9b4931350f08d5ba190afd|72f988bf86f141af91ab2d7cd011db47|1|0|636619539082681664&sdata=VyXeHVSdheWlwwdq2nxZqMidVDPtGrLyPTX1FAU9Yu4%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/MicrosoftCollaboratePortal/issues/69#issuecomment-389181344, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlGj3LjF0mqh4gXohRio2uZAeZT7kQAzks5tyuILgaJpZM4Tu-wp.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FMicrosoftCollaboratePortal%2Fissues%2F69%23issuecomment-389394471&data=02|01|mimcco%40microsoft.com|9e13db248b944799e45908d5bae99967|72f988bf86f141af91ab2d7cd011db47|1|0|636620434830579316&sdata=A4J%2BGqO7i6gtz0mfpnDism%2BTSJxuuD1qkfQEbgzhw78%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAfv1kMXjTfv_DIC8eujR5fxVtXP3mXwnks5ty7HYgaJpZM4Tu-wp&data=02|01|mimcco%40microsoft.com|9e13db248b944799e45908d5bae99967|72f988bf86f141af91ab2d7cd011db47|1|0|636620434830579316&sdata=EpnGclFL1Q7Y1zO40aEKJLt1sPQkzoxQsowwZHxzhIM%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/MicrosoftCollaboratePortal/issues/69#issuecomment-389680711, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlGj3Hv8Cefti3WzD_sCTZGdLQzd1l9Tks5tzKKUgaJpZM4Tu-wp.

I have no idea. Did they provide any way to contact them for support?
From: Olio03<EMAIL_ADDRESS>Sent: Thursday, May 17, 2018 9:43 AM
To: MicrosoftDocs/MicrosoftCollaboratePortal<EMAIL_ADDRESS>Cc: Mike McCoy (WDG<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Mike
Just another thing, where / how do I access the Microsoft Office 2019 CDN.
Can you let me know please.
Oliver

From: Olio03 Olio03 <olio03<EMAIL_ADDRESS>Sent: 17 May 2018 17:37
To: MicrosoftDocs/MicrosoftCollaboratePortal
Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Mike
Just a quick question, I am now a member of the office 2019 testing, but im having trouble activating it, do I use the volume code( it doesn't accept it) or what do I do?
Thanks
Oliver

From: Mike McCoy (WDG) <notifications<EMAIL_ADDRESS>Sent: 16 May 2018 23:05
To: MicrosoftDocs/MicrosoftCollaboratePortal
Cc: Olio03; Author
Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Oliver,
I was able to find the following links:
Read this one first: https://go.microsoft.com/fwlink/?linkid=872263
Then go to this: https://go.microsoft.com/fwlink/?linkid=872092
Thanks,
-Mike
From: Olio03 <notifications<EMAIL_ADDRESS>Sent: Tuesday, May 15, 2018 9:58 PM
To: MicrosoftDocs/MicrosoftCollaboratePortal <MicrosoftCollaboratePortal<EMAIL_ADDRESS>Cc: Mike McCoy (WDG) <mimcco<EMAIL_ADDRESS>Comment <comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Mike,
Their email address, officeconnectteam@microsoft.com<mailto:officeconnectteam@microsoft.commailto:officeconnectteam<EMAIL_ADDRESS>doesnt work.
Oliver

From: Mike McCoy (WDG) <notifications@github.com<mailto:notifications@github.commailto:notifications<EMAIL_ADDRESS>Sent: 15 May 2018 15:11:23
To: MicrosoftDocs/MicrosoftCollaboratePortal
Cc: Olio03; Author
Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Oliver,
Programs are operated individually by the various program administrators within Microsoft. Just as it was with Connect, Collaborate is just the platform that the programs are run on. I work on the Collaborate platform and don’t have a lot of insights into the various requirements for each program. I do know this, all of the programs are by invite only so the program administrators usually contact the people/companies they want to participate. If you were part of a program on Connect that has moved to Collaborate, you should be able to contact whoever you always contacted to get more information. If the Connect program you were a part of is not on Collaborate, it means that the program has closed.
I have no idea if there is a beta testing program for Office 2019…
Sorry I can’t be much help.
Regards,
Mike McCoy
From: Olio03 <notifications@github.com<mailto:notifications@github.commailto:notifications<EMAIL_ADDRESS>Sent: Monday, May 14, 2018 9:05 PM
To: MicrosoftDocs/MicrosoftCollaboratePortal <MicrosoftCollaboratePortal@noreply.github.com<mailto:MicrosoftCollaboratePortal@noreply.github.commailto:MicrosoftCollaboratePortal<EMAIL_ADDRESS>Cc: Mike McCoy (WDG) <mimcco@microsoft.com<mailto:mimcco@microsoft.commailto:mimcco<EMAIL_ADDRESS>Comment <comment@noreply.github.com<mailto:comment@noreply.github.commailto:comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Mike, any update? Ive also heard there is Microsoft Office 2019 coming this year? Can I be a tester?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FMicrosoftCollaboratePortal%2Fissues%2F69%23issuecomment-389036223&data=02|01|mimcco%40microsoft.com|6dbb8830bb9b4931350f08d5ba190afd|72f988bf86f141af91ab2d7cd011db47|1|0|636619539082681664&sdata=BVLETxnBmh%2FKJMzqbrDYSMAwXfZ0OquCxKfNnW8FIj4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAfv1kEt6xdwTX9aBnreQGxfM4wbcssZPks5tylPwgaJpZM4Tu-wp&data=02|01|mimcco%40microsoft.com|6dbb8830bb9b4931350f08d5ba190afd|72f988bf86f141af91ab2d7cd011db47|1|0|636619539082681664&sdata=VyXeHVSdheWlwwdq2nxZqMidVDPtGrLyPTX1FAU9Yu4%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/MicrosoftCollaboratePortal/issues/69#issuecomment-389181344, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlGj3LjF0mqh4gXohRio2uZAeZT7kQAzks5tyuILgaJpZM4Tu-wp.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FMicrosoftCollaboratePortal%2Fissues%2F69%23issuecomment-389394471&data=02|01|mimcco%40microsoft.com|9e13db248b944799e45908d5bae99967|72f988bf86f141af91ab2d7cd011db47|1|0|636620434830579316&sdata=A4J%2BGqO7i6gtz0mfpnDism%2BTSJxuuD1qkfQEbgzhw78%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAfv1kMXjTfv_DIC8eujR5fxVtXP3mXwnks5ty7HYgaJpZM4Tu-wp&data=02|01|mimcco%40microsoft.com|9e13db248b944799e45908d5bae99967|72f988bf86f141af91ab2d7cd011db47|1|0|636620434830579316&sdata=EpnGclFL1Q7Y1zO40aEKJLt1sPQkzoxQsowwZHxzhIM%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/MicrosoftCollaboratePortal/issues/69#issuecomment-389680711, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlGj3Hv8Cefti3WzD_sCTZGdLQzd1l9Tks5tzKKUgaJpZM4Tu-wp.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FMicrosoftCollaboratePortal%2Fissues%2F69%23issuecomment-389932166&data=02|01|mimcco%40microsoft.com|3e6a18d31f5d44b8959c08d5bc1533c4|72f988bf86f141af91ab2d7cd011db47|1|0|636621721681801346&sdata=PwBti4KCcK7tIi3HIAi9UvwE%2FqqgrocfAq47Ndu3QYk%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAfv1kCCE6zFcGNe1jZypdtOytYTPAWQBks5tzah-gaJpZM4Tu-wp&data=02|01|mimcco%40microsoft.com|3e6a18d31f5d44b8959c08d5bc1533c4|72f988bf86f141af91ab2d7cd011db47|1|0|636621721681801346&sdata=ubRggidxNu53GtL%2B%2Fr33hDR4x1TGOSbkOsitGepXz9U%3D&reserved=0.

Hi Mike
No luck with Microsoft.
Any ideas?
Oliver

From: Olio03 Olio03<EMAIL_ADDRESS>Sent: 18 May 2018 09:21:50
To: MicrosoftDocs/MicrosoftCollaboratePortal
Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Mike,
Hope all is well, No, the problem is that.
I have no ways to contact them, I'll have to check Microsoft Collaborate.
Many thanks
Oliver

From: Mike McCoy (WDG<EMAIL_ADDRESS>Sent: 17 May 2018 17:48
To: MicrosoftDocs/MicrosoftCollaboratePortal
Cc: Olio03; Author
Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
I have no idea. Did they provide any way to contact them for support?
From: Olio03<EMAIL_ADDRESS>Sent: Thursday, May 17, 2018 9:43 AM
To: MicrosoftDocs/MicrosoftCollaboratePortal<EMAIL_ADDRESS>Cc: Mike McCoy (WDG<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Mike
Just another thing, where / how do I access the Microsoft Office 2019 CDN.
Can you let me know please.
Oliver

From: Olio03 Olio03 <olio03<EMAIL_ADDRESS>Sent: 17 May 2018 17:37
To: MicrosoftDocs/MicrosoftCollaboratePortal
Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Mike
Just a quick question, I am now a member of the office 2019 testing, but im having trouble activating it, do I use the volume code( it doesn't accept it) or what do I do?
Thanks
Oliver

From: Mike McCoy (WDG) <notifications<EMAIL_ADDRESS>Sent: 16 May 2018 23:05
To: MicrosoftDocs/MicrosoftCollaboratePortal
Cc: Olio03; Author
Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Oliver,
I was able to find the following links:
Read this one first: https://go.microsoft.com/fwlink/?linkid=872263
Then go to this: https://go.microsoft.com/fwlink/?linkid=872092
Thanks,
-Mike
From: Olio03 <notifications<EMAIL_ADDRESS>Sent: Tuesday, May 15, 2018 9:58 PM
To: MicrosoftDocs/MicrosoftCollaboratePortal <MicrosoftCollaboratePortal<EMAIL_ADDRESS>Cc: Mike McCoy (WDG) <mimcco<EMAIL_ADDRESS>Comment <comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Mike,
Their email address, officeconnectteam@microsoft.com<mailto:officeconnectteam@microsoft.commailto:officeconnectteam<EMAIL_ADDRESS>doesnt work.
Oliver

From: Mike McCoy (WDG) <notifications@github.com<mailto:notifications@github.commailto:notifications<EMAIL_ADDRESS>Sent: 15 May 2018 15:11:23
To: MicrosoftDocs/MicrosoftCollaboratePortal
Cc: Olio03; Author
Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Oliver,
Programs are operated individually by the various program administrators within Microsoft. Just as it was with Connect, Collaborate is just the platform that the programs are run on. I work on the Collaborate platform and don’t have a lot of insights into the various requirements for each program. I do know this, all of the programs are by invite only so the program administrators usually contact the people/companies they want to participate. If you were part of a program on Connect that has moved to Collaborate, you should be able to contact whoever you always contacted to get more information. If the Connect program you were a part of is not on Collaborate, it means that the program has closed.
I have no idea if there is a beta testing program for Office 2019…
Sorry I can’t be much help.
Regards,
Mike McCoy
From: Olio03 <notifications@github.com<mailto:notifications@github.commailto:notifications<EMAIL_ADDRESS>Sent: Monday, May 14, 2018 9:05 PM
To: MicrosoftDocs/MicrosoftCollaboratePortal <MicrosoftCollaboratePortal@noreply.github.com<mailto:MicrosoftCollaboratePortal@noreply.github.commailto:MicrosoftCollaboratePortal<EMAIL_ADDRESS>Cc: Mike McCoy (WDG) <mimcco@microsoft.com<mailto:mimcco@microsoft.commailto:mimcco<EMAIL_ADDRESS>Comment <comment@noreply.github.com<mailto:comment@noreply.github.commailto:comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/MicrosoftCollaboratePortal] BETA Testing / Microsoft Collaborate (#69)
Hi Mike, any update? Ive also heard there is Microsoft Office 2019 coming this year? Can I be a tester?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FMicrosoftCollaboratePortal%2Fissues%2F69%23issuecomment-389036223&data=02|01|mimcco%40microsoft.com|6dbb8830bb9b4931350f08d5ba190afd|72f988bf86f141af91ab2d7cd011db47|1|0|636619539082681664&sdata=BVLETxnBmh%2FKJMzqbrDYSMAwXfZ0OquCxKfNnW8FIj4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAfv1kEt6xdwTX9aBnreQGxfM4wbcssZPks5tylPwgaJpZM4Tu-wp&data=02|01|mimcco%40microsoft.com|6dbb8830bb9b4931350f08d5ba190afd|72f988bf86f141af91ab2d7cd011db47|1|0|636619539082681664&sdata=VyXeHVSdheWlwwdq2nxZqMidVDPtGrLyPTX1FAU9Yu4%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/MicrosoftCollaboratePortal/issues/69#issuecomment-389181344, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlGj3LjF0mqh4gXohRio2uZAeZT7kQAzks5tyuILgaJpZM4Tu-wp.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FMicrosoftCollaboratePortal%2Fissues%2F69%23issuecomment-389394471&data=02|01|mimcco%40microsoft.com|9e13db248b944799e45908d5bae99967|72f988bf86f141af91ab2d7cd011db47|1|0|636620434830579316&sdata=A4J%2BGqO7i6gtz0mfpnDism%2BTSJxuuD1qkfQEbgzhw78%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAfv1kMXjTfv_DIC8eujR5fxVtXP3mXwnks5ty7HYgaJpZM4Tu-wp&data=02|01|mimcco%40microsoft.com|9e13db248b944799e45908d5bae99967|72f988bf86f141af91ab2d7cd011db47|1|0|636620434830579316&sdata=EpnGclFL1Q7Y1zO40aEKJLt1sPQkzoxQsowwZHxzhIM%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/MicrosoftCollaboratePortal/issues/69#issuecomment-389680711, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlGj3Hv8Cefti3WzD_sCTZGdLQzd1l9Tks5tzKKUgaJpZM4Tu-wp.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FMicrosoftCollaboratePortal%2Fissues%2F69%23issuecomment-389932166&data=02|01|mimcco%40microsoft.com|3e6a18d31f5d44b8959c08d5bc1533c4|72f988bf86f141af91ab2d7cd011db47|1|0|636621721681801346&sdata=PwBti4KCcK7tIi3HIAi9UvwE%2FqqgrocfAq47Ndu3QYk%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAfv1kCCE6zFcGNe1jZypdtOytYTPAWQBks5tzah-gaJpZM4Tu-wp&data=02|01|mimcco%40microsoft.com|3e6a18d31f5d44b8959c08d5bc1533c4|72f988bf86f141af91ab2d7cd011db47|1|0|636621721681801346&sdata=ubRggidxNu53GtL%2B%2Fr33hDR4x1TGOSbkOsitGepXz9U%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/MicrosoftCollaboratePortal/issues/69#issuecomment-389933772, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlGj3Mf6TKTw5qd5DrGZM22o9TKi7i2-ks5tzanKgaJpZM4Tu-wp.

The issue is related to participation in early preview on Microsoft products, not about Collaborate portal itself.


Search button doesn't work on Librem5 built-in screen portait mode

Describe the bug
A clear and concise description of what the bug is.
To Reproduce

Install in Librem5 via flatpak.
Open and login.
Click top-left search button.
Search pane is shown but for less than a second, so is not usable.

Expected behavior
Show search pane like other pane. E.g. Library, Saved Tracks...
General information:

Distribution: PureOS
Installation method [e. g. built from source, installed from Flathub...]: Flathub
Version [e.g. 0.1.0]: 0.4.0
Device used [e. g. desktop, phone...]: Librem5

This is going to be hard to test in my end.
Does it also happen in other libadwaita apps?

What other app can I test?

@Diegovsky you can easily reproduce this issue on the desktop by making the window very small so that it switches into the "mobile" mode where you can only see the navigation bar and then click on the search symbol. This issue appears on my librem 5 as well as on my debian laptop that way. A curios side effect of this is that if you press library or any other entry in the navigation bar after having pressed on the search symbol, you need the press the back button two times to get back to the navigation bar. I hope that helps :)


Docker build release

List of changes:

Updated README to in hopes to make install instructions a bit cleaner (can revert if needed/disagree), but it was a potential cleaner way of letting newcomers to quickly ID  the install process and docs
Added .build.sh to build the docker image
Added .release.sh to fill out all the required data and push to Docker hub automatically.
Added Dockerfile with comments about the build process in case others want to build the image manually.

Offical Images can be here: https://hub.docker.com/r/empireproject/empire/
Devs: Will be added to the Docker hub org.

@killswitch-GUI Go ahead and send this to the dev branch. I tested staging and command execution and everything seemed to be working just fine. I would only add one thing to your readme.md. Users can start the docker container with the --net=host flag to run the container in the hosts's network stack. Any ports that are opened dynamically, will be available. Thanks.

@xorrior rgr that, I plan on moving adding all the details to the wiki today. :)


[9.4.x] ISPN-11116 Invalidation commands should not load the previous value

https://issues.redhat.com/browse/ISPN-11116

integrated! thanks @danberindei !


Error: command "npm" with parameters "install,build/dist/" exited with code 1

Attach (recommended) or Link to PDF file here: none
Configuration:

Web browser and its version:  104.0.5112.101
Operating system and its version: macOS 12.4
PDF.js version: v2.16.105
Is a browser extension:

Steps to reproduce the problem:

I can open http://localhost:8888/web/viewer.html successfully following the instructions in https://github.com/mozilla/pdf.js#getting-the-code
Next I want to see some examples in https://github.com/mozilla/pdf.js/tree/master/examples/browserify#getting-started. When I run gulp dist-install, I got this:

(base) cuiyc@cuiycdeMacBook-Pro pdf.js % sudo gulp dist-install
Password:
[12:58:35] Using gulpfile ~/DLTribe/pdf.js/gulpfile.js
[12:58:35] Starting 'dist-install'...
[12:58:35] Starting 'dist-pre'...
[12:58:35] Starting 'generic'...
[12:58:35] Starting 'createBuildNumber'...

### Getting extension build number
This is not a Git repository; using default build number.
Extension build number: 0
[12:58:35] Finished 'createBuildNumber' after 22 ms
[12:58:35] Starting 'locale'...

### Building localization files
[12:58:35] Finished 'locale' after 79 ms
[12:58:35] Starting 'scriptingGeneric'...

### Building default preferences
[12:58:36] asset pdf.scripting.js 105 KiB [emitted] (name: main)

webpack 5.74.0 compiled successfully
[12:58:36] Finished 'scriptingGeneric' after 700 ms
[12:58:36] Starting 'createGeneric'...

### Creating generic viewer
[BABEL] Note: The code generator has deoptimised the styling of /Users/cuiyc/DLTribe/pdf.js/external/quickjs/quickjs-eval.js as it exceeds the max of 500KB.
[12:58:38] asset pdf.sandbox.js 616 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:58:40] asset viewer.js 416 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:58:41] asset pdf.js 490 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:58:41] asset pdf.worker.js 1.88 MiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:58:41] Finished 'createGeneric' after 5.16 s
[12:58:41] Finished 'generic' after 5.96 s
[12:58:41] Starting 'generic-legacy'...
[12:58:41] Starting 'createBuildNumber'...

### Getting extension build number
This is not a Git repository; using default build number.
Extension build number: 0
[12:58:41] Finished 'createBuildNumber' after 22 ms
[12:58:41] Starting 'locale'...

### Building localization files
[12:58:41] Finished 'locale' after 48 ms
[12:58:41] Starting 'scriptingGenericLegacy'...

### Building default preferences
[12:58:41] asset pdf.scripting.js 109 KiB [emitted] (name: main)

webpack 5.74.0 compiled successfully
[12:58:41] Finished 'scriptingGenericLegacy' after 227 ms
[12:58:41] Starting 'createGenericLegacy'...

### Creating generic (legacy) viewer
[BABEL] Note: The code generator has deoptimised the styling of /Users/cuiyc/DLTribe/pdf.js/external/quickjs/quickjs-eval.js as it exceeds the max of 500KB.
[12:58:43] asset pdf.sandbox.js 621 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:58:46] asset viewer.js 509 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:58:47] asset pdf.js 655 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:58:47] asset pdf.worker.js 1.98 MiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:58:47] Finished 'createGenericLegacy' after 5.25 s
[12:58:47] Finished 'generic-legacy' after 5.55 s
[12:58:47] Starting 'components'...
[12:58:47] Starting 'createBuildNumber'...

### Getting extension build number
This is not a Git repository; using default build number.
Extension build number: 0
[12:58:47] Finished 'createBuildNumber' after 21 ms
[12:58:47] Starting 'createComponents'...

### Creating generic components
[12:58:47] asset pdf_viewer.js 224 KiB [emitted] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:58:47] Finished 'createComponents' after 382 ms
[12:58:47] Finished 'components' after 404 ms
[12:58:47] Starting 'components-legacy'...
[12:58:47] Starting 'createBuildNumber'...

### Getting extension build number
This is not a Git repository; using default build number.
Extension build number: 0
[12:58:47] Finished 'createBuildNumber' after 20 ms
[12:58:47] Starting 'createComponentsLegacy'...

### Creating generic (legacy) components
[12:58:48] asset pdf_viewer.js 260 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:58:48] Finished 'createComponentsLegacy' after 418 ms
[12:58:48] Finished 'components-legacy' after 439 ms
[12:58:48] Starting 'image_decoders'...
[12:58:48] Starting 'createBuildNumber'...

### Getting extension build number
This is not a Git repository; using default build number.
Extension build number: 0
[12:58:48] Finished 'createBuildNumber' after 20 ms
[12:58:48] Starting 'createImageDecoders'...

### Creating image decoders
[12:58:48] asset pdf.image_decoders.js 242 KiB [emitted] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:58:48] Finished 'createImageDecoders' after 465 ms
[12:58:48] Finished 'image_decoders' after 485 ms
[12:58:48] Starting 'image_decoders-legacy'...
[12:58:48] Starting 'createBuildNumber'...

### Getting extension build number
This is not a Git repository; using default build number.
Extension build number: 0
[12:58:48] Finished 'createBuildNumber' after 20 ms
[12:58:48] Starting 'createImageDecodersLegacy'...

### Creating (legacy) image decoders
[12:58:49] asset pdf.image_decoders.js 291 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:58:49] Finished 'createImageDecodersLegacy' after 488 ms
[12:58:49] Finished 'image_decoders-legacy' after 508 ms
[12:58:49] Starting 'lib'...
[12:58:49] Starting 'createBuildNumber'...

### Getting extension build number
This is not a Git repository; using default build number.
Extension build number: 0
[12:58:49] Finished 'createBuildNumber' after 20 ms
[12:58:49] Starting 'scriptingLib'...

### Building default preferences
[12:58:49] asset pdf.scripting.js 105 KiB [emitted] (name: main)

webpack 5.74.0 compiled successfully
[12:58:49] Finished 'scriptingLib' after 166 ms
[12:58:49] Starting 'createLib'...
[BABEL] Note: The code generator has deoptimised the styling of /Users/cuiyc/DLTribe/pdf.js/external/quickjs/quickjs-eval.js as it exceeds the max of 500KB.
[12:58:50] asset pdf.sandbox.js 616 KiB [emitted] [big] (name: main)

webpack 5.74.0 compiled successfully
[12:58:52] Finished 'createLib' after 3.01 s
[12:58:52] Finished 'lib' after 3.2 s
[12:58:52] Starting 'minified'...
[12:58:52] Starting 'createBuildNumber'...

### Getting extension build number
This is not a Git repository; using default build number.
Extension build number: 0
[12:58:52] Finished 'createBuildNumber' after 23 ms
[12:58:52] Starting 'locale'...

### Building localization files
[12:58:52] Finished 'locale' after 48 ms
[12:58:52] Starting 'scriptingMinified'...

### Building default preferences
[12:58:52] asset pdf.scripting.js 105 KiB [emitted] (name: main)

webpack 5.74.0 compiled successfully
[12:58:52] Finished 'scriptingMinified' after 161 ms
[12:58:52] Starting 'createMinified'...

### Creating minified viewer
[BABEL] Note: The code generator has deoptimised the styling of /Users/cuiyc/DLTribe/pdf.js/external/quickjs/quickjs-eval.js as it exceeds the max of 500KB.
[12:58:54] asset pdf.sandbox.js 616 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:58:55] asset pdf.image_decoders.js 242 KiB [emitted] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:58:56] asset viewer.js 416 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:58:57] asset pdf.js 490 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:58:57] asset pdf.worker.js 1.88 MiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:58:57] Finished 'createMinified' after 5 s
[12:58:57] Starting 'compressMinified'...

### Minifying js files

### Cleaning js files
[12:59:02] Finished 'compressMinified' after 4.72 s
[12:59:02] Finished 'minified' after 9.95 s
[12:59:02] Starting 'minified-legacy'...
[12:59:02] Starting 'createBuildNumber'...

### Getting extension build number
This is not a Git repository; using default build number.
Extension build number: 0
[12:59:02] Finished 'createBuildNumber' after 30 ms
[12:59:02] Starting 'locale'...

### Building localization files
[12:59:02] Finished 'locale' after 44 ms
[12:59:02] Starting 'scriptingMinifiedLegacy'...

### Building default preferences
[12:59:02] asset pdf.scripting.js 109 KiB [emitted] (name: main)

webpack 5.74.0 compiled successfully
[12:59:02] Finished 'scriptingMinifiedLegacy' after 196 ms
[12:59:02] Starting 'createMinifiedLegacy'...

### Creating minified (legacy) viewer
[BABEL] Note: The code generator has deoptimised the styling of /Users/cuiyc/DLTribe/pdf.js/external/quickjs/quickjs-eval.js as it exceeds the max of 500KB.
[12:59:04] asset pdf.sandbox.js 621 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:59:06] asset viewer.js 509 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:59:07] asset pdf.js 655 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:59:08] asset pdf.worker.js 1.98 MiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:59:08] asset pdf.image_decoders.js 291 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[12:59:08] Finished 'createMinifiedLegacy' after 5.69 s
[12:59:08] Starting 'compressMinifiedLegacy'...

### Minifying js files

### Cleaning js files
[12:59:12] Finished 'compressMinifiedLegacy' after 4.74 s
[12:59:12] Finished 'minified-legacy' after 11 s
[12:59:12] Starting 'types'...
### Generating TypeScript definitions using `tsc`
[12:59:15] Finished 'types' after 2.46 s
[12:59:15] Starting 'createDist'...

### Cloning baseline distribution

### Overwriting all files
[12:59:28] Finished 'createDist' after 13 s
[12:59:28] Finished 'dist-pre' after 53 s
[12:59:28] Starting 'createDistInstall'...
Error: command "npm" with parameters "install,build/dist/" exited with code 1
[12:59:35] The following tasks did not complete: dist-install, createDistInstall
[12:59:35] Did you forget to signal async completion?

What went wrong? (add screenshot)
Error: command "npm" with parameters "install,build/dist/" exited with code 1
[12:59:35] The following tasks did not complete: dist-install, createDistInstall
[12:59:35] Did you forget to signal async completion?

I google it and I found some solutions like https://stackoverflow.com/questions/36897877/gulp-error-the-following-tasks-did-not-complete-did-you-forget-to-signal-async. But it doesn't help.
Node version : v16.16.0
gulp CLI version: 2.3.0
gulp Local version: 4.0.2

sudo gulp dist-install

sudo shouldn't be necessary to run something like gulp, have you tried using it without that (which is what all our documentation does)?
### Getting extension build number
This is not a Git repository; using default build number.
Extension build number: 0

Those repeated messages are most likely related here, since that should never happen in a properly cloned/initialized project, and they unfortunately suggest that perhaps not all steps of https://github.com/mozilla/pdf.js#getting-the-code were actually completed (successfully) exactly as written.
However, from a distance it's simply impossible for anyone to tell exactly what went wrong here.

Definitely should not usesudo: https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally. After amend this, I tried it again. However, it's still the same error. @Snuffleupagus , I'm sure I followed the instructions exactly the same.
It seems that the git command cannot recognize it as a repository. I tried git init, it's still the same error.

I just tried following https://github.com/mozilla/pdf.js#getting-the-code before running run gulp dist-install, in a new directory, and everything worked just fine. (As mentioned above, it's impossible to tell what goes wrong from a distance.)
Did you actually run the following Git-command, as the instructions tell you to, or did you perhaps manually download the source-code (since the latter won't work)?
$ git clone https://github.com/mozilla/pdf.js.git
$ cd pdf.js

I have tried both methods including git clone command and downloading the zip file. Actually, one command is differnet, it's npm install. I have to use npm install --force to bypass the conflict(one solution found in stackoverflow).  Should I have to use npm install ?
git clone https://github.com/mozilla/pdf.js.git
(base) cuiyc@cuiycdeMacBook-Pro DLTribe % git clone https://github.com/mozilla/pdf.js.git
Cloning into 'pdf.js'...
remote: Enumerating objects: 84562, done.
remote: Counting objects: 100% (131/131), done.
remote: Compressing objects: 100% (79/79), done.
remote: Total 84562 (delta 59), reused 110 (delta 50), pack-reused 84431
Receiving objects: 100% (84562/84562), 131.78 MiB | 1.73 MiB/s, done.
Resolving deltas: 100% (60548/60548), done.

npm install met error
(base) cuiyc@cuiycdeMacBook-Pro pdf.js % npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/eslint-plugin-html
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/eslint-plugin-mozilla
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/eslint-plugin-html
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/eslint-plugin-mozilla
npm ERR!     dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /Users/cuiyc/.npm/eresolve-report.txt for a full report.

npm ERR!       Upgrade to fsevents 2.
npm WARN deprecated<EMAIL_ADDRESS>Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated<EMAIL_ADDRESS>Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated<EMAIL_ADDRESS>CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated<EMAIL_ADDRESS>Support has ended for 9.x series. Upgrade to @latest
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.

> postinstall
> cross-env PUPPETEER_PRODUCT=firefox node node_modules/puppeteer/install.js

Requesting latest Firefox Nightly version from https://product-details.mozilla.org/1.0/firefox_versions.json
Downloading Firefox Nightly r106.0a1 - 139 Mb [====================] 100% 0.0s
Firefox Nightly (106.0a1) downloaded to /Users/cuiyc/DLTribe/pdf.js/node_modules/puppeteer/.local-firefox/mac-106.0a1

added 1149 packages in 2m

116 packages are looking for funding
  run `npm fund` for details

gulp dist-install
(base) cuiyc@cuiycdeMacBook-Pro pdf.js % gulp dist-install
[17:45:27] Using gulpfile ~/DLTribe/pdf.js/gulpfile.js
[17:45:27] Starting 'dist-install'...
[17:45:27] Starting 'dist-pre'...
[17:45:27] Starting 'generic'...
[17:45:27] Starting 'createBuildNumber'...

### Getting extension build number
Extension build number: 17
[17:45:27] Finished 'createBuildNumber' after 29 ms
[17:45:27] Starting 'locale'...

### Building localization files
[17:45:27] Finished 'locale' after 54 ms
[17:45:27] Starting 'scriptingGeneric'...

### Building default preferences
[17:45:28] asset pdf.scripting.js 105 KiB [emitted] (name: main)

webpack 5.74.0 compiled successfully
[17:45:28] Finished 'scriptingGeneric' after 657 ms
[17:45:28] Starting 'createGeneric'...

### Creating generic viewer
[BABEL] Note: The code generator has deoptimised the styling of /Users/cuiyc/DLTribe/pdf.js/external/quickjs/quickjs-eval.js as it exceeds the max of 500KB.
[17:45:30] asset pdf.sandbox.js 617 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:45:32] asset viewer.js 416 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:45:33] asset pdf.js 490 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:45:33] asset pdf.worker.js 1.88 MiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:45:33] Finished 'createGeneric' after 5.03 s
[17:45:33] Finished 'generic' after 5.77 s
[17:45:33] Starting 'generic-legacy'...
[17:45:33] Starting 'createBuildNumber'...

### Getting extension build number
Extension build number: 17
[17:45:33] Finished 'createBuildNumber' after 27 ms
[17:45:33] Starting 'locale'...

### Building localization files
[17:45:33] Finished 'locale' after 46 ms
[17:45:33] Starting 'scriptingGenericLegacy'...

### Building default preferences
[17:45:33] asset pdf.scripting.js 109 KiB [emitted] (name: main)

webpack 5.74.0 compiled successfully
[17:45:33] Finished 'scriptingGenericLegacy' after 206 ms
[17:45:33] Starting 'createGenericLegacy'...

### Creating generic (legacy) viewer
[BABEL] Note: The code generator has deoptimised the styling of /Users/cuiyc/DLTribe/pdf.js/external/quickjs/quickjs-eval.js as it exceeds the max of 500KB.
[17:45:35] asset pdf.sandbox.js 622 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:45:37] asset viewer.js 509 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:45:39] asset pdf.js 654 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:45:39] asset pdf.worker.js 1.98 MiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:45:39] Finished 'createGenericLegacy' after 5.5 s
[17:45:39] Finished 'generic-legacy' after 5.78 s
[17:45:39] Starting 'components'...
[17:45:39] Starting 'createBuildNumber'...

### Getting extension build number
Extension build number: 17
[17:45:39] Finished 'createBuildNumber' after 30 ms
[17:45:39] Starting 'createComponents'...

### Creating generic components
[17:45:39] asset pdf_viewer.js 224 KiB [emitted] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:45:39] Finished 'createComponents' after 363 ms
[17:45:39] Finished 'components' after 393 ms
[17:45:39] Starting 'components-legacy'...
[17:45:39] Starting 'createBuildNumber'...

### Getting extension build number
Extension build number: 17
[17:45:39] Finished 'createBuildNumber' after 27 ms
[17:45:39] Starting 'createComponentsLegacy'...

### Creating generic (legacy) components
[17:45:40] asset pdf_viewer.js 260 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:45:40] Finished 'createComponentsLegacy' after 471 ms
[17:45:40] Finished 'components-legacy' after 499 ms
[17:45:40] Starting 'image_decoders'...
[17:45:40] Starting 'createBuildNumber'...

### Getting extension build number
Extension build number: 17
[17:45:40] Finished 'createBuildNumber' after 26 ms
[17:45:40] Starting 'createImageDecoders'...

### Creating image decoders
[17:45:40] asset pdf.image_decoders.js 242 KiB [emitted] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:45:40] Finished 'createImageDecoders' after 443 ms
[17:45:40] Finished 'image_decoders' after 469 ms
[17:45:40] Starting 'image_decoders-legacy'...
[17:45:40] Starting 'createBuildNumber'...

### Getting extension build number
Extension build number: 17
[17:45:40] Finished 'createBuildNumber' after 24 ms
[17:45:40] Starting 'createImageDecodersLegacy'...

### Creating (legacy) image decoders
[17:45:41] asset pdf.image_decoders.js 290 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:45:41] Finished 'createImageDecodersLegacy' after 511 ms
[17:45:41] Finished 'image_decoders-legacy' after 535 ms
[17:45:41] Starting 'lib'...
[17:45:41] Starting 'createBuildNumber'...

### Getting extension build number
Extension build number: 17
[17:45:41] Finished 'createBuildNumber' after 24 ms
[17:45:41] Starting 'scriptingLib'...

### Building default preferences
[17:45:41] asset pdf.scripting.js 105 KiB [emitted] (name: main)

webpack 5.74.0 compiled successfully
[17:45:41] Finished 'scriptingLib' after 164 ms
[17:45:41] Starting 'createLib'...
[BABEL] Note: The code generator has deoptimised the styling of /Users/cuiyc/DLTribe/pdf.js/external/quickjs/quickjs-eval.js as it exceeds the max of 500KB.
[17:45:42] asset pdf.sandbox.js 616 KiB [emitted] [big] (name: main)

webpack 5.74.0 compiled successfully
[17:45:44] Finished 'createLib' after 3.03 s
[17:45:44] Finished 'lib' after 3.22 s
[17:45:44] Starting 'minified'...
[17:45:44] Starting 'createBuildNumber'...

### Getting extension build number
Extension build number: 17
[17:45:44] Finished 'createBuildNumber' after 25 ms
[17:45:44] Starting 'locale'...

### Building localization files
[17:45:44] Finished 'locale' after 46 ms
[17:45:44] Starting 'scriptingMinified'...

### Building default preferences
[17:45:44] asset pdf.scripting.js 105 KiB [emitted] (name: main)

webpack 5.74.0 compiled successfully
[17:45:44] Finished 'scriptingMinified' after 165 ms
[17:45:44] Starting 'createMinified'...

### Creating minified viewer
[BABEL] Note: The code generator has deoptimised the styling of /Users/cuiyc/DLTribe/pdf.js/external/quickjs/quickjs-eval.js as it exceeds the max of 500KB.
[17:45:46] asset pdf.sandbox.js 617 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:45:47] asset pdf.image_decoders.js 242 KiB [emitted] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:45:49] asset viewer.js 416 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:45:49] asset pdf.js 490 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:45:49] asset pdf.worker.js 1.88 MiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:45:49] Finished 'createMinified' after 5.08 s
[17:45:49] Starting 'compressMinified'...

### Minifying js files

### Cleaning js files
[17:45:54] Finished 'compressMinified' after 4.55 s
[17:45:54] Finished 'minified' after 9.86 s
[17:45:54] Starting 'minified-legacy'...
[17:45:54] Starting 'createBuildNumber'...

### Getting extension build number
Extension build number: 17
[17:45:54] Finished 'createBuildNumber' after 28 ms
[17:45:54] Starting 'locale'...

### Building localization files
[17:45:54] Finished 'locale' after 44 ms
[17:45:54] Starting 'scriptingMinifiedLegacy'...

### Building default preferences
[17:45:54] asset pdf.scripting.js 109 KiB [emitted] (name: main)

webpack 5.74.0 compiled successfully
[17:45:54] Finished 'scriptingMinifiedLegacy' after 202 ms
[17:45:54] Starting 'createMinifiedLegacy'...

### Creating minified (legacy) viewer
[BABEL] Note: The code generator has deoptimised the styling of /Users/cuiyc/DLTribe/pdf.js/external/quickjs/quickjs-eval.js as it exceeds the max of 500KB.
[17:45:56] asset pdf.sandbox.js 622 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:45:58] asset viewer.js 509 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:45:59] asset pdf.js 654 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:46:00] asset pdf.image_decoders.js 290 KiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:46:00] asset pdf.worker.js 1.98 MiB [emitted] [big] (name: main) 1 related asset

webpack 5.74.0 compiled successfully
[17:46:00] Finished 'createMinifiedLegacy' after 5.78 s
[17:46:00] Starting 'compressMinifiedLegacy'...

### Minifying js files

### Cleaning js files
[17:46:05] Finished 'compressMinifiedLegacy' after 4.78 s
[17:46:05] Finished 'minified-legacy' after 11 s
[17:46:05] Starting 'types'...
### Generating TypeScript definitions using `tsc`
[17:46:08] Finished 'types' after 2.92 s
[17:46:08] Starting 'createDist'...

### Cloning baseline distribution

### Overwriting all files
[17:46:24] Finished 'createDist' after 17 s
[17:46:24] Finished 'dist-pre' after 57 s
[17:46:24] Starting 'createDistInstall'...
Error: command "npm" with parameters "install,build/dist/" exited with code 1
[17:46:28] The following tasks did not complete: dist-install, createDistInstall
[17:46:28] Did you forget to signal async completion?

@Snuffleupagus  Problem solved.
I tried the error command npm install build/dist, turned out I got:
(base) cuiyc@cuiycdeMacBook-Pro pdf.js % npm install build/dist
npm ERR! code 128
npm ERR! An unknown git error occurred
npm ERR! command git --no-replace-objects ls-remote<EMAIL_ADDRESS>npm ERR! ERROR: Repository not found.
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.

npm ERR!      /Users/cuiyc/.npm/_logs/2022-09-03T03_03_30_876Z-debug-0.log

It seems that npm recognized the command to clone a repository. So I changed the demo:

Finally:
### Overwriting all files
[11:02:41] Finished 'createDist' after 5.25 s
[11:02:41] Finished 'dist-pre' after 44 s
[11:02:41] Starting 'createDistInstall'...
[11:02:46] Finished 'createDistInstall' after 5.18 s
[11:02:46] Finished 'dist-install' after 49 s


Lay your own foundation instead of Reset or Normalize

Some days ago, on this thread on QA, Blake Wilson posted an interesting link by a senior-developer that talks about not using reset.css or normalize.css in our projects.
Here the link
http://jaydenseric.com/blog/forget-normalize-or-resets-lay-your-own-css-foundation
What do you think if we try to adopt it?

I've read that article, and in general I agree, I liked it. We can possibly change some details if we need to.

Yea, I like this.  I've used normalize.css many times but building my portfolio I've been using this foundation.  It's nice because you don't notice that much of a difference and it seems a lot smaller.  There are some things to be aware of.  There is no default heading or paragraph stylings so that took some adjusting for me... and there might have been other things.  But shouldn't be a problem since we will roll our own typography styles anyway.  Hmm, I'm just only slightly concerned as how it would affect others' components that didn't build their stuff off of this.  It's opinionated... well.. but still I don't think it changes stuff that much.  Should be fine.

@Gruximillian @brianhernandez

I'm just only slightly concerned as how it would affect others' components that didn't build their stuff off of this

This is a thing that I was thinking about. We have to take care of this aspect because, as Richard said, each component should work fine as a standalone element.
If we look at our previous framework (seed UI), I think many elements were affected by the CSS rules provided by normalize.css. But what if the user downloads the CSS of a single element that does not contain any reset?

There is the all: initial; approach, but its not that widely supported yet: https://developer.mozilla.org/en-US/docs/Web/CSS/all

We can just remove the things we don't need from normalize.css and leave the migration to after the release.

@cbracco

but its not that widely supported yet:

This is the biggest problem. We need something more stable
@escorponox

We can just remove the things we don't need from normalize.css and leave the migration to after the release.

I agree with you.
@everyone
What about the need of giving to the users the ability to download single components? How could we do for allowing this?
Do you think it's better if the user must download at least two separate CSS files or a single one?
In the first case, we could have a base CSS file which contains reset, helpers and so on, and a specific CSS file which contains all the rules for a component instead.
In the second case, we need a way for incorporate all the necessary in a single file which is compiled just in time, when the user chooses what component wants to download.

@cbracco
But aren't the initial values browser dependent? I have no idea, that's why I ask.

Hmm... yea, I'm kind of going back and forth with 'your own foundation' and normalize for this project now.  I think @escorponox makes a good point.  Given we have limited time now, our priority is to try and make the deadline so sticking with something that is a little more familiar or widely used might be better.  We can always change and update later when time permits.
@GabrieleRomeo With regards to making this as modular as possible.... Right, I think that would be nice to have some kind of build process that fetches all the rests that a particular component is dependent on and incorporates them into the CSS for the component... I just don't know what would do that or setting that up.  Perhaps it isn't that difficult to do for some components manually.  Again, for now, maybe having the component html, css and js files plus the optional normalize/reset file for users to download is ok.  The two css file case, normalize and component file(s) may be modular enough for now to meet the deadline.  Richard said it doesn't have to be perfect.

If we look at our previous framework (seed UI), I think many elements were affected by the CSS rules provided by normalize.css. But what if the user downloads the CSS of a single element that does not contain any reset?

My vote is for normalize.css and the two files to download approach.  I think it gets us to our goals quicker and hits the main point of being modular enough for now.  I'm thinking in most cases, if a user downloads these components they most likely will drop them into a project that has some kind of reset.  reset.css and normalize.css are the most common currently from what I understand... so that's why I am thinking, for now, this is an ok decision to take.

But what if the user downloads the CSS of a single element that does not contain any reset?

I think that it is not uncommon to declare normalize.css as a dependecy and that's it. I also think that we should not bother with this for now. Just declare it as a dependency and we'll get back to this later to see if there is a better approach.

@cbracco
But aren't the initial values browser dependent? I have no idea, that's why I ask.

No actually what all: initial; does is resets any default browser styles to whatever the default initial value would be for each CSS property. So for example, the <blockquote> element has an opinionated margin value set in some browsers so that it appears indented from surrounding elements. all: initial; would reset the margin property to its initial value, which is auto.
There is a PostCSS plugin that acts as a polyfill for the initial keyword:

https://github.com/maximkoretskiy/postcss-initial

The idea is that this moves the reset into the local scope of a component, instead of having a bunch of components depend on one global reset.
Not sure we want to do this but its a neat idea.

@cbracco
Thanks for this info. I think that for now we should stick with what we have, but after the release we can open a feature branch to test this technique, and if it proves to be working and to be better than using normalize.css, then we'll switch to it.


Make ConfigScopes aware of enclosing scope

Right now they can only access globals.
This enable you to define them within a function, and access the local variables there.

We don't need this, and I consider it too much magic.


gzip CRC check fails

fvid installed through pip3 to bring along dependencies.
Test file: 9.1Mb Photoshop document. Successfully encoded with fvid, uploaded to YouTube, downloaded with ytdl, then run through fvid's decoder. After seeing Bits are in place, fvid unpacks the frames 100%, but:
Unziping...

Traceback (most recent call last):

  File "/usr/local/bin/fvid", line 8, in <module>
   sys.exit(main())
  File "/usr/local/lib/python3.9/site-packages/fvid/fvid.py", line 274, in main
   save_bits_to_file(file_path, bits, key)
  File "/usr/local/lib/python3.9/site-packages/fvid/fvid.py", line 144, in save_bits_to_file
   bitstring = fo.read()
  File<EMAIL_ADDRESS>line 300, in read
    return self._buffer.read(size)
  File<EMAIL_ADDRESS>line 478, in read
    self._read_eof()
  File<EMAIL_ADDRESS>line 524, in _read_eof
    raise BadGzipFile("CRC check failed %s != %s" % (hex(crc32),
gzip.BadGzipFile: CRC check failed 0xebd7fa1e != 0xc3ae18db

I notice that regardless of the command syntax, fvid run multiple times on the same input file generates MP4s of consistently varying byte counts suggesting the algorithm or one of the modules it depends on is flaky. This is consistent across the following syntaxes:
fvid -ei filename.ext
fvid --encode -i filename.ext
fvid -i filename.ext -e

file.mp4 came out as lengths of 159,351,426; 159,351,436; 159,351,435; 159,351,433 and the resulting downloaded YT videos had similar variances.

That's very interesting. I've never seen that before, I'll start googling for an answer now.

@dobrosketchkun As the person who implemented gzip support, do you think that the gzip could become problematic when run through youtube's compression and then redownloaded?

Looks like I have the same issue when uploading, then downloading from youtube as well. Works just fine if I do not upload to youtube

@smileyhogue Can you send the affected file(s) here so I can test?

Ok, well I just swallowed my pride and uploaded a test file to youtube. When I downloaded with youtube-dl with the -k option on youtube-dl (to keep the original video and the audio files separate), I found that the main .mp4 that had the .m4a audio in it had this CRC error, however decoding just the video worked fine. Test files attached for you guys to try.
Working one:
https://user-images.githubusercontent.com/43764914/108606617-0108cd80-7389-11eb-89cd-13984643f43b.mp4
Not working one:
https://user-images.githubusercontent.com/43764914/108606622-08c87200-7389-11eb-98f2-6d85d3ccbb04.mp4

OSError: CRC check failed 0xeb8845b4 != 0xf1812ef7
I just had the same error, even on a video downloaded with the -k switch without the audio.
The video is quite large tho: https://youtu.be/a0qWc_X3sN8
I tested the fvid earlier on a different smaller file and it worked ok.

I can confirm similar issue, even with downloading video/audio separately using the -k switch.
OSError: CRC check failed 0x3af5c3bd != 0x4c4d5ef
Only happens when using the file downloaded from YouTube.
Link to video: https://youtu.be/YV9dPIdqXC0


Make unirest compatible to mime 2.* versions

This is to support the higer versoin of mime from 2.* .This fix is required to avoid the error of mandate true on the mine on the retries
To avoid the below error on retries callback
Error: Attempt to change mapping for "form" extension from "application/x-www-form-urlencoded" to "application/x-www-form-urlencoded". Pass force=true to allow this, otherwise remove "form" from the list of extensions for "application/x-www-form-urlencoded".
at Mime.define (/home/user/projects/mytest/node_modules/mime/Mime.js:32:17)

Hey, any update on this? Facing this issue on one of our packages 😅

Appears that one of the tests is failing, once resolved I can merge

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


unable to connect to global chaos net

I'm unable to connect to the Global Chaosnet, getting this loop and then cbridge exists.  I haven't changed my configs in ages so dunno ...
Forward TLS to dest 0 over 03040 (router.chaosnet.net)
CHUDP: Sending RUT: 4 + 16 + 4 + 6 = 30 bytes to <IP_ADDRESS>:4402
Enabling SIGINFO
Enabling SIGUSR1
Sending SNS from 03123 (obh 0) to 03040
Sending pkt 0 (SNS) from me (03123) to 03040 (pkt dest 03040) TLS dest 03040 Static bridge 0 myaddr 03123
Forward TLS to dest 03040 over 03040 (router.chaosnet.net)
Sending SNS from 03123 (obh 0) to 03040
Sending pkt 0 (SNS) from me (03123) to 03040 (pkt dest 03040) TLS dest 03040 Static bridge 0 myaddr 03123
Forward TLS to dest 03040 over 03040 (router.chaosnet.net)
Sending SNS from 03123 (obh 0) to 03040
Sending pkt 0 (SNS) from me (03123) to 03040 (pkt dest 03040) TLS dest 03040 Static bridge 0 myaddr 03123
Forward TLS to dest 03040 over 03040 (router.chaosnet.net)
Sending SNS from 03123 (obh 0) to 03040
Sending pkt 0 (SNS) from me (03123) to 03040 (pkt dest 03040) TLS dest 03040 Static bridge 0 myaddr 03123
Forward TLS to dest 03040 over 03040 (router.chaosnet.net)
Sending SNS from 03123 (obh 0) to 03040
Sending pkt 0 (SNS) from me (03123) to 03040 (pkt dest 03040) TLS dest 03040 Static bridge 0 myaddr 03123
Forward TLS to dest 03040 over 03040 (router.chaosnet.net)
Sending SNS from 03123 (obh 0) to 03040

Are you using IPv4 or IPv6? What's your local such address, so I can look for traces of connections?

I can't seem to get anywhere on the global chaosnet with ES either.
I get a constant stream of messages from cbridge. A subset:
TLS_please_reopen_tcp (<IP_ADDRESS>)
TLS input: read MARK
TLS read record: SSL is null, please reopen
TLS_please_reopen_tcp (<IP_ADDRESS>)
TLS input: read MARK
TLS read record: SSL is null, please reopen
TLS_please_reopen_tcp (<IP_ADDRESS>)
TLS input: read MARK
TLS read record: SSL is null, please reopen
TLS_please_reopen_tcp (<IP_ADDRESS>)
TLS input: read MARK
TLS read record: SSL is null, please reopen
TLS_please_reopen_tcp (<IP_ADDRESS>)
TLS input: read MARK
TLS read record: SSL is null, please reopen
TLS_please_reopen_tcp (<IP_ADDRESS>)
TLS input: read MARK
TLS read record: SSL is null, please reopen
TLS_please_reopen_tcp (<IP_ADDRESS>)
TLS input: read MARK
TLS read record: SSL is null, please reopen
TLS_please_reopen_tcp (<IP_ADDRESS>)
TLS input: read MARK
TLS read record: SSL is null, please reopen
TLS_please_reopen_tcp (<IP_ADDRESS>)
TLS input: read MARK
TLS read record: SSL is null, please reopen
TLS_please_reopen_tcp (<IP_ADDRESS>)
TLS input: read MARK
TLS read record: SSL is null, please reopen
TLS_please_reopen_tcp (<IP_ADDRESS>)
TLS input: read MARK
TLS read record: SSL is null, please reopen
TLS_please_reopen_tcp (<IP_ADDRESS>)
TLS input: read MARK
TLS read record: SSL is null, please reopen
TLS_please_reopen_tcp (<IP_ADDRESS>)
TLS input: read MARK
TLS read record: SSL is null, please reopen
TLS_please_reopen_tcp (<IP_ADDRESS>)
TLS input: read MARK
TLS read record: SSL is null, please reopen
TLS_please_reopen_tcp (<IP_ADDRESS>)
TLS input: read MARK
wait_for_reconnect_signal done
TLS client: connecting to <IP_ADDRESS> port 42042
TCP connect: socket family 2 (IPv4)
TCP connect: connecting to <IP_ADDRESS> port 42042

Are you using IPv4 or IPv6? What's your local such address, so I can look for traces of connections?

IPv4 (either via DNS or static IP address); is MX down?
~/Private/amssite-etc [1] $ ping6 router.chaosnet.net
PING6(56=40+8+8 bytes) 2001:9b0:214:4f00:a55d:8224:3f5b:74e6 --> 2001:9b1:df8:7100:7948:dc01:a1e5:3301

--- mx12.victor.se ping6 statistics ---
10 packets transmitted, 0 packets received, 100.0% packet loss
~/Private/amssite-etc [2] $ ping router.chaosnet.net
PING mx12.victor.se (<IP_ADDRESS>): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1

--- mx12.victor.se ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
~/Private/amssite-etc [2] $

Strange. I just restarted cbridge, and immediately got (new) connections from Sanyal, N3UC, and Bogodyne (all over IPv4).
I don't know: try "git pull; make", or running with tls debug on?

Working now for me.  I can get to BV again.  The restart must have fixed things.  Remember that I was having an issue with a long-running, and working cbridge, until connections stopped working.  Restarting cbridge made things work again.  I wonder if the same issue hit you?

Well it depends what connections you mean, NCP or TLS? The NCP case I debugged and (think I) fixed recently, but there may be (!) bugs in the TLS code too, of course.

AMS, if you give me your (external) IP I could check the firewall logs, in case they are doing something bad.

Just started cbridge, and now it works.  I didn't change anything ..  was using master from origin, and make clean all.

Yes, it seems that you do have to occasionally start cbridge.  It loses its cookies after a while.

Sigh, I'll look at the TLS code (at some point).

I guess we can close this for now ...


Add New Module

Dont merge this first, created for reference

Number Lookup Module
OTP Charge Per Attempt

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@2cba732). Click here to learn what that means.
The diff coverage is 94.61%.

@@           Coverage Diff            @@
##             master      #1   +/-   ##
========================================
  Coverage          ?   94.7%
========================================
  Files             ?      18
  Lines             ?     359
  Branches          ?       0
========================================
  Hits              ?     340
  Misses            ?      19
  Partials          ?       0

Impacted Files
Coverage Δ

lib/moceansdk/modules/message/verify_validate.rb
100% <100%> (ø)

...b/moceansdk/exceptions/required_field_exception.rb
100% <100%> (ø)

lib/moceansdk/modules/account/balance.rb
100% <100%> (ø)

lib/moceansdk/modules/message/channel.rb
100% <100%> (ø)

lib/moceansdk/modules/message/sms.rb
100% <100%> (ø)

lib/moceansdk/auth/basic.rb
100% <100%> (ø)

...b/moceansdk/modules/number_lookup/number_lookup.rb
100% <100%> (ø)

lib/moceansdk.rb
100% <100%> (ø)

lib/moceansdk/modules/message/message_status.rb
100% <100%> (ø)

lib/moceansdk/modules/message/verify_request.rb
100% <100%> (ø)

... and 8 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 2cba732...60d73e7. Read the comment docs.


set default encoding for unicode

This seems like a good idea. I've done this before with:
#-*- coding: utf-8 -*-

Will this line work better and avoid the runtime cost of reloading sys, or is it equivalent? Also, what are the potential consequences of making this change?

no, it's not equivalent.
i found http://stackoverflow.com/questions/2276200/changing-default-encoding-of-python and it is solved with sitecustomize.py.

okay, maybe changing the default encoding to utf-8 will help with some of the unicodedecode exceptions that are currently tested for


Rename disease->disorder in labels for terms that conform to patterns/location.yaml

Updates
    - Ran: fix-disorders-conformsTo-location.ru and updated mondo-edit.obo

    - Added SPARQL query: select-conformsTo-location.sparql
    - Added SPARQL update query: Conforms to pattern/location.yaml and has word ‘disease’ in table. Bind label with regex replace pattern from disease to disorder. Delete old label. Insert new label
    - Updated: select-conformsTo-allergy.sparql: added a prefix

@nicolevasilevsky @matentzn I think Nico said this looked like it might be good?
But for me it looks like there are 2 issues, and I don't know what to do:

I don't see that "disorder". Is that an issue? Maybe I don't see it because most of the terms were already "disorder", and most of the diffs I'm seeing are simply selections of terms that conform to the location.yaml pattern? In that case, I would imagine that no change should have been made, but...:
Everything after the ! following the label has been deleted. This doesn't seem good to me. What do I need to do to fix this? I don't know how to query for this ! and the text that follows it, and preserve that.

diff.txt

Hi @joeflack4
Unfortunately, I don't think this worked. I don't see that  MONDO:0000001 disease or disorder was changed to disorder.
The changes you are seeing in the screenshot above are updates to the imports - to hgnc and so. Sometimes I see this where the labels are deletd, I don't know it does this.

Shucks... Well I'm at a loss as to why these 2 issues are happening.
The query: src/sparql/update/fix-disorders-conformsTo-location.ru
prefix dcterms: <http://purl.org/dc/terms/>
prefix owl: <http://www.w3.org/2002/07/owl#>
prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>
prefix xsd: <http://www.w3.org/2001/XMLSchema#>
prefix mondoPatterns: <http://purl.obolibrary.org/obo/mondo/patterns/>

DELETE {
  ?term rdfs:label ?label .
}
INSERT {
  ?term rdfs:label ?new_label .
}
WHERE {
  ?term rdfs:label ?label .
  ?term dcterms:conformsTo mondoPatterns:location.yaml .
  FILTER NOT EXISTS { ?term owl:deprecated "true"^^xsd:boolean . }
  FILTER (isIRI(?term) && regex(str(?term), "^http://purl.obolibrary.org/obo/MONDO_"))
  FILTER(regex(str(?label),"disease"))
  BIND(REPLACE(str(?label), "disease", "disorder") as ?new_label )
}

All changes to mondo-edit.obo where spurious - they happened because you used the wrong command for applying the update..
This command applies one of your 2 queries:
sh run.sh make update-merge-normalise-fix-disorders-conformsTo-location
As @nicolevasilevsky has said, it does not do anything at the moment. Most likely, the where clause does not match anything. This needs a bit of playing around: I would suggest you make sure the select query that contains the identical WHERE clause works properly first.

@matentzn Thanks; I am sorry this is not working as expected.
The select statement seems like it should work:
https://api.triplydb.com/s/bSFVrEYKb
The only difference in the WHERE clause between the Yasgui one and the one I'm making for Mondo are the following lines that were added:
  FILTER (isIRI(?term) && regex(str(?term), "^http://purl.obolibrary.org/obo/MONDO_"))
  FILTER(regex(str(?label),"disease"))
  BIND(REPLACE(str(?label), "disease", "disorder") as ?new_label )

It doesn't seem like anything complicated is going on here, though... Based on this above, do you have any idea what's wrong?

ODK docker
Also, I think I need to learn more about the merits of using the ODK docker container via sh run.sh. Relying on using a docker container as an environment (rather than as an application/service), as it would appear, is new to me. It makes me feel a bit suspect of it, but perhaps that I need to open my mind a bit more. I'm assuming that the advantage is that it bundles a bunch of different tools that have non-easy installations, and includes tools from different programming languages. If they were all written in the same programming language, then I imagine it would be better to use a package management system (e.g. Maven, PyPi, NPM) to ensure consistent versions. But maybe there are data artefacts in the environment too. Maybe this is something that we can bring up at our Wednesday meeting if we have time.

I think I'll probably be pushing this ticket to next week, as #4346 and the mondo paper will be filling up my Mondo time for this week.

This is PR is giving me a bit of trouble. I am trying to wrap my head around it: https://github.com/ontodev/robot/issues/967
Looks like your work is all correct @joeflack4
Will keep looking into this. The workaround is to use sparql construct together with robot unmerge/merge.

Nicole to do:

[ ] check out branch, open in Protege and make sure everything looks okay and check diff too