Internal Server Connection Error

Description
steps:

fresh install from binary
create test empty repository
try to push through ssh
try to push through https

results:

from ssh method:

Gitea: Internal Server Connection Error
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

from https method:

Enumerating objects: 3, done.
Counting objects: 100% (3/3), done.
Writing objects: 100% (3/3), 215 bytes | 215.00 KiB/s, done.
Total 3 (delta 0), reused 0 (delta 0), pack-reused 0
remote:
remote: Gitea: Internal Server Connection Error
To https://<IP_ADDRESS>:3000/home/test.git
! [remote rejected] dev -> dev (pre-receive hook declined)
error: failed to push some refs to 'https://<IP_ADDRESS>:3000/home/test.git'

attempts to fix:

setting LOCAL_ROOT_URL=http://<IP_ADDRESS>:1881/ in /etc/gitea/app.ini
'Reinitialize all missing Git repositories for which records exist' from 'Maintenance Operations' of 'Site administration' menu
switching in different branches

Gitea Version
1.20.0+rc0-28-g5191ab644
Log Gist
https://gist.github.com/M-Arthur-A/7968b553373a5e67095f633fcbb31e0e
Screenshots

Git Version
2.34.1
Operating System
Ubuntu 22.04.2
How are you running Gitea?
systemd
Database
SQLite

You have aspects set to port 1881 but are trying to push to port 3000
LOCAL_ROOT_URL=http://<IP_ADDRESS>:1881/

You have aspects set to port 1881 but are trying to push to port 3000
LOCAL_ROOT_URL=http://<IP_ADDRESS>:1881/

I just copied from another topic literally. Corrected in the description

Can you post your app.ini and full debug logs
This feels like a port issue since you will have

Http
Https
SSH

Can you post your app.ini and full debug logs
This feels like a port issue since you will have
1. Http

2. Https

3. SSH

app.ini: https://gist.github.com/M-Arthur-A/491a0247a8441da8919db866d5cc1c5e
debug log: https://gist.github.com/M-Arthur-A/1d1cd905568c181f8ea7dac06c44206c

It would be quite tricky if you mix PROTOCOL= https + LOCAL_ROOT_URL=http://<IP_ADDRESS>:3000/
I have no idea about how to make them work together.
Either:
PROTOCOL=https
LOCAL_ROOT_URL=https://domain-with-valid-cert:3000/

Or
PROTOCOL=http
LOCAL_ROOT_URL=http://your-host-or-ip:3000/

It would be quite tricky if you mix PROTOCOL= https + LOCAL_ROOT_URL=http://<IP_ADDRESS>:3000/
I have no idea about how to make them work together.
Either:
PROTOCOL=https
LOCAL_ROOT_URL=https://domain-with-valid-cert:3000/

Or
PROTOCOL=http
LOCAL_ROOT_URL=http://your-host-or-ip:3000/

PROTOCOL=https
LOCAL_ROOT_URL=https://domain-with-valid-cert:3000/

it helps! thank you!


C++ demo

The provided instructions for running the C++ demo no longer works as the link returns 404. I found out with this link:
https://docs.openvino.ai/2024/omz_demos_human_pose_estimation_demo_cpp.html
That demo is provided via Open Model Zoo at demos/human_pose_estimation_demo:
https://github.com/openvinotoolkit/open_model_zoo/tree/master
Could you please update the instructions on README?

Hi! Thanks, updated in #328


Support merging editor panel with terminal panel.

For large monitors, it would be really fantastic if we could merge and editor panel with the terminal panel. The following image is an illustration of this idea.

With this feature, it would be much more flexible to change the layout of panels, and makes it easier to either code following the paper or fix bugs about generating some PDF file.

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

Sidebar Open Editors panel should open OVER the folder panel to prevent unexpected double click behaviour (#96759)

No, that's a bug, and this is a feature request.

/duplicate https://github.com/microsoft/vscode/issues/10546


Package perl-Compress-Raw-Zlib build not isolated

When building the package 'perl-Compress-Raw-Zlib' on OS X 10.6.8, the builder tells me that my version of the zlib header file (1.2.7) doesn't match the version of zlib I have installed (1.2.3).
I think this means the build environment is being contaminated by the operating system's built-in libraries.

running nix-env -iA nixpkgs.perlPackages.CompressRawZlib appears to work for me (osx 10.9, nixos-unstable), although there is this curious output:
LD_RUN_PATH="/nix/store/0s5i71y9rjnbzxlmr6msdvf48qva5v99-zlib-1.2.8/lib" cc  -bundle -undefined dynamic_lookup -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-Libsystem-osx-10.9.5/lib -fstack-protector Zlib.o  -o blib/arch/auto/Compress/Raw/Zlib/Zlib.bundle 	\
   -L/nix/store/0s5i71y9rjnbzxlmr6msdvf48qva5v99-zlib-1.2.8/lib -lz  	\

ld: warning: directory not found for option '-L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-Libsystem-osx-10.9.5/lib'


The models trained on 128x128 dataset

Hi, @zhixinshu
I want to train the model with 128x128 input on CelebA dataset.
Thus, i add additional layers in both encoder and decoder.
The codes are as follows:
class waspDenseEncoder(nn.Module):
    def __init__(self, opt, ngpu=1, nc=1, ndf = 32, ndim = 128, activation=nn.LeakyReLU, args=[0.2, False], f_activation=nn.Sigmoid, f_args=[]):
        super(waspDenseEncoder, self).__init__()
        self.ngpu = ngpu
        self.ndim = ndim

        self.main = nn.Sequential(
                # input is (nc) x 128 x 128
                nn.BatchNorm2d(nc),
                nn.ReLU(True),
                nn.Conv2d(nc, ndf, 4, stride=2, padding=1),

                # state size. (ndf) x 64 x 64
                DenseBlockEncoder(ndf, 6),
                DenseTransitionBlockEncoder(ndf, ndf*2, 2, activation=activation, args=args),

                # state size. (ndf*2) x 32 x 32
                DenseBlockEncoder(ndf*2, 12),
                DenseTransitionBlockEncoder(ndf*2, ndf*4, 2, activation=activation, args=args),

                # state size. (ndf*4) x 16 x 16
                DenseBlockEncoder(ndf*4, 24),
                DenseTransitionBlockEncoder(ndf*4, ndf*8, 2, activation=activation, args=args),

                # state size. (ndf*8) x 8 x 8
                DenseBlockEncoder(ndf*8, 24),
                DenseTransitionBlockEncoder(ndf*8, ndf*16, 2, activation=activation, args=args),

                # state size. (ndf*16) x 4 x 4
                DenseBlockEncoder(ndf*16, 16),
                DenseTransitionBlockEncoder(ndf*16, ndim, 4, activation=activation, args=args),
                f_activation(*f_args),
        )

    def forward(self, input):
        output = self.main(input).view(-1,self.ndim)
        return output

class waspDenseDecoder(nn.Module):
    def __init__(self, opt, ngpu=1, nz=128, nc=1, ngf=32, lb=0, ub=1, activation=nn.ReLU, args=[False], f_activation=nn.Hardtanh, f_args=[0,1]):
        super(waspDenseDecoder, self).__init__()
        self.ngpu   = ngpu
        self.main   = nn.Sequential(
            # input is Z, going into convolution
            nn.BatchNorm2d(nz),
            activation(*args),
            nn.ConvTranspose2d(nz, ngf * 16, 4, 1, 0, bias=False),

            # state size. (ngf*16) x 4 x 4
            DenseBlockDecoder(ngf*16, 16),
            DenseTransitionBlockDecoder(ngf*16, ngf*8),

            # state size. (ngf*8) x 8 x 8
            DenseBlockDecoder(ngf*8, 24),
            DenseTransitionBlockDecoder(ngf*8, ngf*4),

            # state size. (ngf*4) x 16 x 16
            DenseBlockDecoder(ngf*4, 24),
            DenseTransitionBlockDecoder(ngf*4, ngf*2),

            # state size. (ngf*2) x 32 x 32
            DenseBlockDecoder(ngf*2, 12),
            DenseTransitionBlockDecoder(ngf*2, ngf),

            # state size. (ngf) x 64 x 64
            DenseBlockDecoder(ngf, 6),
            DenseTransitionBlockDecoder(ngf, ngf),

            # state size (ngf) x 128 x 128
            nn.BatchNorm2d(ngf),
            activation(*args),
            nn.ConvTranspose2d(ngf, nc, 3, stride=1, padding=1, bias=False),
            f_activation(*f_args),
        )
    def forward(self, inputs):
        return self.main(inputs)

Although the training processing is normal, the texture is wired.
Texture：

Output：

Could you give me some advice for training 128x128 size image?
Many thanks!

Additionally, these are the loss diagrams.

I download the latest code and train the model with 64x64 size image on CelebA dataset.
Then, I met this error.
Traceback (most recent call last):   File "train_InstinsicDAE_CelebA.py", line 252, in <module>     dp0_S, dp0_T, dp0_I, dp0_W, dp0_output, dp0_Wact = decoders(dp0_zS, dp0_zT, dp0_zW, baseg)   File "/usr/local/lib/python2.7/dist-packages/torch/nn/modules/module.py", line 477, in __call__     result = self.forward(*input, **kwargs)   File "/data2/valentina/DeformingAutoencoders-pytorch-latest/DAENet_InstanceNorm.py", line 566, in forward     self.shading = self.decoderS(zS.view(-1,self.sdim,1,1))   File "/usr/local/lib/python2.7/dist-packages/torch/nn/modules/module.py", line 477, in __call__     result = self.forward(*input, **kwargs)   File "/data2/valentina/DeformingAutoencoders-pytorch-latest/DAENet_InstanceNorm.py", line 391, in forward     return self.main(inputs)   File "/usr/local/lib/python2.7/dist-packages/torch/nn/modules/module.py", line 477, in __call__     result = self.forward(*input, **kwargs)   File "/usr/local/lib/python2.7/dist-packages/torch/nn/modules/container.py", line 91, in forward     input = module(input)   File "/usr/local/lib/python2.7/dist-packages/torch/nn/modules/module.py", line 477, in __call__     result = self.forward(*input, **kwargs)   File "/usr/local/lib/python2.7/dist-packages/torch/nn/modules/instancenorm.py", line 49, in forward     self.training or not self.track_running_stats, self.momentum, self.eps)   File "/usr/local/lib/python2.7/dist-packages/torch/nn/functional.py", line 1305, in instance_norm     eps=eps)   File "/usr/local/lib/python2.7/dist-packages/torch/onnx/__init__.py", line 68, in wrapper     return fn(*args, **kwargs)   File "/usr/local/lib/python2.7/dist-packages/torch/nn/functional.py", line 1293, in _instance_norm     training=use_input_stats, momentum=momentum, eps=eps)   File "/usr/local/lib/python2.7/dist-packages/torch/nn/functional.py", line 1251, in batch_norm     raise ValueError('Expected more than 1 value per channel when training, got input size {}'.format(size)) ValueError: Expected more than 1 value per channel when training, got input size [1, 1600, 1, 1]
Is there any problem while using instance norm?

I saw it.
I found that the reason why the texture had been placed in the left upper corner is that i didn't split the training set into several parts.
After doing this, the texture will stay in the center of the image.
In addition, i want to know why you replace batch normalization with instance normalization instead of fixing the bias of batch normalization while testing?

Hi, @zhixinshu.
I met another problem.
When i use the pretrained model your provided to produce the texture, the texture seems to be well-aligned.
However, when i train the model with 128x128 input, the texture it produces is not well-aligned and diverse.
The input images, texture images and the output images are as follows.
For the model with 64x64 size input:
1.The input image

2.The texture image

3.The output image

For the model with 128x128 size input:
1.The input image

2.The texture image

3.The output image

Should i decrease the weight of loss_tvw? But, i found it useless for this problem.
Could you give me some advice? Many thanks!

What are the length (dimensionality) of the latent codes for the experiments with 64x64 and 128x128 respectively? It seems the texture learned here in 128x128 images contain significant variability of shape deformation. In practice better alignment could be achieved by shorten the latent code of texture while enlarge or maintain the capacity for deformation to push more variability to the deformation branch.

I use the default settings from the code repository while training 128x128.
The texture is composed of shading and albedo.
So i only need to shorten the latent codes of them?
Like opt.sdim = 8, opt.tdim = 8?


Update to Bevy 0.14 rc

Closes #280

@Friz64 could we bump this PR to the 0.14 release candidate?
diff --git a/Cargo.toml b/Cargo.toml
index 07803dd..6aff021 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -39,7 +39,7 @@ name = "ui"
 required-features = ["render"]

 [dependencies]
-bevy = { git = "https://github.com/bevyengine/bevy.git", rev = "519abbc", default-features = false, features = [
+bevy = { version = "0.14.0-rc.2", default-features = false, features = [
     "bevy_asset",
 ] }
 egui = { version = "0.27", default-features = false, features = ["bytemuck"] }
@@ -52,7 +52,7 @@ thread_local = { version = "1.1.0", optional = true }

 [dev-dependencies]
 version-sync = "0.9.4"
-bevy = { git = "https://github.com/bevyengine/bevy.git", rev = "519abbc", default-features = false, features = [
+bevy = { version = "0.14.0-rc.2", default-features = false, features = [
     "x11",
     "png",
     "bevy_pbr",

Yes, I have that in mind for later today, when I am able to.

Thanks for doing this!

Bump this to 0.14.0 now that it's released! Thanks :)

There you go!!! 🎉

The colours seem to be wrong on WASM. I won't be blocking the release, but if anyone could help me with fixing those, that would be great.
And thank you for the PR @Friz64!


Viewer buttons from multiple viewers connected to last created viewer

🐛 Bug
When using multiple viewers, the viewer buttons in the bottom left do not change the camera scene of the viewer they belong to. Instead, they change the camera scene of the last created viewer. This might be related to #1530 .
To Reproduce
Steps to reproduce the behavior:

Run the following code to open two napari viewers

from napari import Viewer
from skimage.data import cells3d, astronaut

viewer1 = Viewer(title="viewer 1")
viewer1.add_image(cells3d()[30, 1])

viewer2 = Viewer(title="viewer 2")
viewer2.add_image(astronaut())

Go to viewer 1 and click one of Toggle ndisplay, Change order ..., Transpose order ....
The scene in viewer 1 will not change.
Observe that the scene in viewer 2 changes.
Close viewer 2.
Click on Show/Hide IPython ... in viewer 1. This results in the following error message

raceback (most recent call last):
  File "d:\napari-3d-ortho-viewer\.win-napari-3d-ortho-viewer\lib\site-packages\napari\utils\action_manager.py", line 53, in <lambda>
    self._command_with_context = lambda: call_with_context(
  File "d:\napari-3d-ortho-viewer\.win-napari-3d-ortho-viewer\lib\site-packages\napari\utils\action_manager.py", line 42, in call_with_context
    return function(**ctx)
  File "d:\napari-3d-ortho-viewer\.win-napari-3d-ortho-viewer\lib\site-packages\napari\_qt\qt_viewer.py", line 739, in toggle_console_visibility
    viz = not self.dockConsole.isVisible()
RuntimeError: wrapped C/C++ object of type QtViewerDockWidget has been deleted

Although viewer 2 is closed now, clicking Toggle ndisplay, Change order ..., Transpose order ... in viewer 1 does not have any effect on the scene of viewer 1.

Expected behavior
I expect that clicking on the viewer buttons in viewer 2 changes the scene in viewer 2. Clicking the buttons in viewer 1 should change the scene in viewer 1.
Environment
napari: 0.4.12
Platform: Windows-10-10.0.22000-SP0
Python: 3.9.5 (tags/v3.9.5:0a7dcbd, May 3 2021, 17:27:52) [MSC v.1928 64 bit (AMD64)]
Qt: 5.15.2
PyQt5: 5.15.6
NumPy: 1.21.4
SciPy: 1.7.3
Dask: 2021.11.2
VisPy: 0.9.4
OpenGL:

GL version: 4.6.0 - Build <IP_ADDRESS>64
MAX_TEXTURE_SIZE: 16384

Screens:

screen 1: resolution 2560x1440, scale 1.0
screen 2: resolution 2560x1440, scale 1.0

Plugins:

console: 0.0.4
napari-3d-ortho-viewer: 0.0.1
scikit-image: 0.4.12
svg: 0.1.5

Additional context

Hi @gatoniel, I believe this is the same thing that was just fixed in #3692 (i.e. duplicate of #2977 and #2897).  If you are able to work on the master branch, can you confirm?  (it would be pip install -U https://github.com/napari/napari.git) ... if not, you can wait until the next release to give it a try.  should be soon

Yes, works with current master branch.


Add Elastic File System & Cloud Directory VPC Endpoints - Terraform 0.11

Description
Add VPC Endpoint Support for EFS & Cloud Directory

Could you make a additional PR for the 0.12 version? That would be great. Thanks!

Will do
On Tue, Nov 5, 2019, 15:07 Niklas Wagner<EMAIL_ADDRESS>wrote:

Could you make a additional PR for the 0.12 version? That would be great.
Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/terraform-aws-modules/terraform-aws-vpc/pull/349?email_source=notifications&email_token=AIA2W7QEQSAMMJTJ5TSLISLQSFVZ5A5CNFSM4JFNVTV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDCYGSQ#issuecomment-549815114,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIA2W7RWDMIIQNH3S6FFYSLQSFVZ5ANCNFSM4JFNVTVQ
.

closing this to sunset support of terraform 11 fork


term.echo does not respect whitespace

Issue summary
When using echo() if you feed in a string on multiple lines when each line has whitespace at the beginning, and you use keepWords the resulting output trims the whitespace from the begginning of each line
  let test = `This
                is
                   a
                      test`
  term.echo(test, { keepWords: true });

Trims whitespace.
  let test = `This
                is
                   a
                      test`
  term.echo(test);

Echos normally
It is also worth mentioning that this happens on both echo and less.
Expected behavior
This
                    is
                       a
                          test

Actual behavior
Ouput
This
is
a
test

Steps to reproduce
  let test = `This
                is
                   a
                      test`
  term.echo(test, { keepWords: true });

vs
  let test = `This
                is
                   a
                      test`
  term.echo(test);

Browser and OS
This does not matter.

This is expected behavior. The whitespace need to be trimmed from the beginning because the original code when wrapped sometimes have single whitespace that was at the end of the line.
foo bar baz

foo bar
 baz

This is was the reason for trimming in the code.
What is the use case when you need word wrapping and space in front?
Maybe I can do something with this, the trim was added to quickly fix the space in the front of the line issue, but it probably can be handled without the trim.

Released in version 2.32

Hi Sorry, I just saw this.
The reason for needing this was I have code blocks inside the echo. Which obviously use whitespace as indentation.
I see a fix went live, what was it?
Thanks and apologies for the delay in the response.

I'm not sure what you mean by "what was it?" the issue was because in the split_equal function sometimes there were trailing spaces when keepWords was used, so I've fixed this by using trim, but this also removed spaces in front of the lines which was your problem.
The fix is that it doesn't remove spaces in front.
I just realized that in the original issue I sometimes had one single space in front, I need to check it.

I was right this introduced a bug https://codepen.io/jcubic/pen/oNoaGyv?editors=0010 there are leading spaces that should not be there.


The Import path mentioned in document not working

import { CountryPicker } from '@/components/ui/CountryPickerModal/CountryPicker' is one doc suggested but
when we import this it's importing like this import { CountryPicker } from '@/components/ui/CountryPickerModal/src'
the index file should be in the root CountryPickerModal folder

Okay @ChamaraWP. I'll check

Android Bundling failed 19631ms C:\zysk\reactNative\lazim-mobile-app\node_modules\expo\AppEntry.js (1 module)
Unable to resolve "./assets/data/countries-emoji.json" from "components\CountryPickerModal\src\CountryService.ts"

@yushanwebdev  can you check this??

import { CountryPicker } from "@components/CountryPickerModal/src/CountryPicker";
import { DEFAULT_THEME, FlagButton } from "@components/CountryPickerModal/src";


[Bug]: Manual Citekey not accepted

Bug Description
When using the workflow to extract annotations, alfred returns a "no citekey found" error (error message in screenshot). The citekey is a custom citekey that is listed in the relevant bibTeX file.

Check your BibTeX Library for the correct citekey.
' to Conditional
[8:53:19.545 pm] PDF Annotation Extractor[Conditional] Processing complete
[8:53:19.546 pm] PDF Annotation Extractor[Conditional] Passing output 'No citekey found.

Check your BibTeX Library for the correct citekey.
' to Large Type
[8:53:19.547 pm] PDF Annotation Extractor[Large Type] Processing complete
[8:53:19.548 pm] PDF Annotation Extractor[Large Type] Passing output 'No citekey found.

Check your BibTeX Library for the correct citekey.
' to Play Sound

Workflow Configuration

Checklist

[X] I have updated to the latest version of this workflow.
[X] I checked out the available options under aconf and there isn't one that enables the desired behavior.

could you attach a small sample of your bibtex file, containing the citation in question?

@article{Bedard(2005)SexPreferencesMarital,
title = {Sex Preferences, Marital Dissolution, and the Economic Status of Women},
author = {Bedard, Kelly and Deschênes, Olivier},
year = {2005},
month = mar,
journal = {Journal of Human Resources},
volume = {XL},
number = {2},
pages = {411--434},
publisher = {University of Wisconsin Press},
issn = {0022-166X, 1548-8004},
doi = {10.3368/jhr.XL.2.411},
langid = {english},
file = {/Volumes/GoogleDrive/My Drive/Everything/Work/Reference Attachments/Bedard & Deschênes (2005) Sex Preferences, Marital Dissolution, and the Economic Status of Women.pdf}
}
@book{Beddard(1992)EconomicSocialCultural,
title = {Economic, Social and Cultural Rights},
editor = {Beddard, Ralphand and Hill, Dilys M},
year = {1992},
publisher = {Macmillan},
address = {Hampshire},
keywords = {Unread}
}

The issue is that as far as I know,Beddard(1992)EconomicSocialCultural is an invalid citekey due to the brackets. While I haven't found a proper documentation online what characters in a citekey are valid, I tested it with Pandoc as well as mgmeyers Pandoc Reference list plugin, which both also don't work because they consider it an invalid citekey.
So I pushed an update that should fix the issue for this workflow, since for the extraction of annotations the validity of a citekey actually does not matter. Nevertheless, you should consider changing your citekey pattern, if you plan on using the citekeys for anything pandoc-related.

Thanks so much! I have no plans to use pandoc any time and am too fond of word as a writing tool so it's unlikely, thanks for the update!

well, you also miss out on mgmeyers' fantastic Pandoc reference list plugin though ;)

I can't change it now though - my obsidian already has the file names for annotations from the custom citekeys, re-exporting all the notes means that links to it from my actual writing notes won't be updated...


Slack channel or discord?

Question
This is an incredibly cool framework - I wonder if there are some folks we could talk to about it? Would love to collab!
Suggestion (Optional)

Hi. Thank you for your interest in the project!
As of now we don't have any kind of messenger based community set up. We of course can set one up later if there will be more interest in it, but for now perhaps we can use issues and discussions forum in this repo?


[QA] Move here button should be enable when we browse to other folders

Also we should disable this option in Public Links, due to you access to files with no user account and it should not be possible to move the file

the gif anim looks like you are in the same folder?

the gif anim looks like you are in the same folder?

Yes, it is the same folder/path. IMHO Move button should be only enable once you move to other path

I'm also seeing in your gif that the translations are not really working correctly

I'm also seeing in your gif that the translations are not really working correctly


Skype for Business Stability issuess

Bot Info

App ID: f079f4c0-39a6-4825-81e2-0da3a7c13b53
SDK Platform:  Node.js
Active Channels: Skype, Webchat,Skype For Business
Deployment Environment: ngrok

Issue Description
We have registered a bot as a contact on skype for business. But it has stability issue. Many times the bot goes down all of a sudden. Then after few hrs it starts working on its own.
Expected Behavior
I expect skype for business to show stability. All channels are very stable and work properly almost everytime. But with Skype for business we face issues, which affects our demos, as the bot goes down many times when we are to give the demo
Actual Results

Is the inconsistency only occurring on the Skype for Business channel?

Yes only on Skype for Business. Webchat and Skype work almost everytime

@anujaparikh23 For reference, can you provide a conversationId and the time(s) + timezone when the error happened?


RDS page does not display

https://instances.vantage.sh/rds/
just gives a white page, no data

Hmm that is not good @BFJonk. What browser are you using? Looks okay in Chrome to me but eager to debug this.

If you can share a screenshot of the developer console as well that would be helpful.

No data from the page:
curl -v 'https://instances.vantage.sh/rds/'
...
< HTTP/2 200
< content-type: text/html
< content-length: 0
< date: Thu, 09 Nov 2023 20:25:54 GMT
< server: nginx/1.18.0 (Ubuntu)
< last-modified: Thu, 09 Nov 2023 00:28:28 GMT
< etag: "654c27ac-0"
< expires: Fri, 10 Nov 2023 20:25:54 GMT
< cache-control: max-age=86400
< cache-control: public, no-transform
< accept-ranges: bytes
< x-cache: Miss from cloudfront

Hmm guessing something changed on the AWS side. Investigating..

Found the culprit. New Auroria I/O optimized instances. Fix incoming

Hey folks, thanks for the filing. Should be good to go now. re:Invent is very active for updates 😅


Add exclude-regex option

Support skipping PRs based on title. For example:
exclude-regex:
  '^Bump important-dep|in /important/directory$

Normal run, vs with in /qa$ as exclude-regex:

As for use-case: we don't like to merge Dependabot updates of our /sql dependencies without testing them beyond what CI does. So I think we'd want mergeabot to skip them.


"Source: Null Extension Description" in messages

Issue Type: Bug
VS Code version: Code - Insiders 1.26.0-insider (dae69dbf00357ff8a3fe740a1f211d66b0b4681c, 2018-07-27T05:17:55.890Z)
OS version: Windows_NT x64 10.0.17134
The "Source" string for show*Message() calls is Null Extension Description in current Insider's builds:

In 1.25.1 it's fine:

import * as vscode from "vscode";

export function activate(context: vscode.ExtensionContext) {
	vscode.window.showErrorMessage("Foo");
}

@Gama11 that works for me as expected when running the extension out of source or when creating a vsix. Anything special about your setup?

/needsMoreInfo

Oh, interesting, it works when I run the extension through the launch config with --extensionDevelopmentPath... For 1.25, this is not required.
I guess there is something special about my setup: for all extensions I work on, I use "development installations" (https://github.com/Microsoft/vscode/issues/25159). It seems this workflow is not officially documented or endorsed, but many developers use it regardless (and for good reason, it's quite convenient).

Well, this is a more recent issue / regression, since it seems to work in 1.25. Of course it might technically not be considered a bug at all if development installations are not supported to begin with..


Grenadier Parasite Immunity is either very poorly communicated in-game, or more frustrating than intended.

Description
The Grenadier's helmet now has 6 attempts at blocking a Parasite before it occurs, but conveys zero information to the Xeno player besides that the attempt has failed entirely, up to 6 times, discouraging even trying to infect unless you already know the mechanics from an external source.
This leads to a lot of mechanics confusion as the current proper way of infecting a Grenadier specialist is by either

A combat caste dragging them on top of 7 entirely different eggs, with each egg before the last being opened and unfixable by said combat caste as they can not re-package parasites into eggs.

A drone/hivelord smashing a parasite into them 7 times with no obvious indicator that what they're doing isn't just useless, couple this with this being fairly difficult to actually pull off input wise (you must not be dragging the host or you can not hold a parasite, you must repeatedly toggle combat mode as you pick up the parasite, place the parasite, and keep shoving, and repeating all this while not even sure if it's possible to do in the first place).

This causes a lot of frustration as the fact you must repeat something that seems incredibly menial (manual) and/or destructive (ripping apart LOTS of eggs to infect one guy) exactly 7 times before it works is not well conveyed to the player.
Videos
Drone POV, must do 7 times exactly, while the popup message discourages you from doing so, making you think you're on the wrong track
https://github.com/user-attachments/assets/60ad0011-c817-4782-b6b6-276908daed0c
Combat Caste POV, must use 7 unique eggs, makes a big mess of opened eggs that you can't fix, no message that tells you that you're making progress, the only feedback given to the Xeno is the attempt failed and the egg is now broken, 6 times
https://github.com/user-attachments/assets/2ab1f175-196d-412b-961a-0698608da20b
Additional notes
I am not even sure if this Egg interaction is parity or not, and would appreciate a check on that.

idea:
it takes 6 hits to remove the grenadier helmet, so depending on how many hits it takes it says something like "The grenadier helmet weakens. A few more leaps to go." to the xenos or something

it takes 6 hits to remove the grenadier helmet, so depending on how many hits it takes it says something like "The grenadier helmet weakens. A few more leaps to go." to the xenos or something

This would be very good, yes, anything that encourages the Xenos to do it rather than discourages them
I would still like a parity check for the Eggs stuff though, as it makes a very, very large mess


 To
silence this warning, remove the "${ sequence from the start and the }"
sequence from the end of this expression, leaving just the inner expression.

Template interpolation syntax is still used to construct strings from
expressions when the template includes multiple interpolation sequences or a
mixture of literal strings and interpolations. This deprecation applies only
to templates that consist entirely of a single interpolation sequence.

(and 7 more similar warnings elsewhere)

Apply complete! Resources: 11 added, 0 changed, 0 destroyed.

Outputs:

account_id =<PHONE_NUMBER>36
aws_partition = aws
aws_region = us-east-1
resource_aka = arn:aws:elasticbeanstalk:us-east-1:986325076436:environment/turbottest18015/turbottest18015
resource_id = e-m6wx7pxzk6
resource_name = turbottest18015

Running SQL query: test-get-query.sql
[
  {
    "akas": [
      "arn:aws:elasticbeanstalk:us-east-1:986325076436:environment/turbottest18015/turbottest18015"
    ],
    "application_name": "turbottest18015",
    "environment_id": "e-m6wx7pxzk6",
    "environment_name": "turbottest18015",
    "partition": "aws",
    "region": "us-east-1",
    "tags": [
      {
        "Key": "elasticbeanstalk:environment-name",
        "Value": "turbottest18015"
      },
      {
        "Key": "elasticbeanstalk:environment-id",
        "Value": "e-m6wx7pxzk6"
      },
      {
        "Key": "Name",
        "Value": "turbottest18015"
      }
    ],
    "title": "turbottest18015"
  }
]
✔ PASSED

Running SQL query: test-hydrate-query.sql
[
  {
    "akas": [
      "arn:aws:elasticbeanstalk:us-east-1:986325076436:environment/turbottest18015/turbottest18015"
    ],
    "environment_name": "turbottest18015",
    "tags": [
      {
        "Key": "elasticbeanstalk:environment-name",
        "Value": "turbottest18015"
      },
      {
        "Key": "elasticbeanstalk:environment-id",
        "Value": "e-m6wx7pxzk6"
      },
      {
        "Key": "Name",
        "Value": "turbottest18015"
      }
    ],
    "title": "turbottest18015"
  }
]
✔ PASSED

Running SQL query: test-list-query.sql
[
  {
    "application_name": "turbottest18015",
    "environment_arn": "arn:aws:elasticbeanstalk:us-east-1:986325076436:environment/turbottest18015/turbottest18015",
    "environment_id": "e-m6wx7pxzk6",
    "environment_name": "turbottest18015",
    "partition": "aws",
    "region": "us-east-1"
  }
]
✔ PASSED

Running SQL query: test-not-found-query.sql
null
✔ PASSED

Running SQL query: test-turbot-query.sql
[
  {
    "account_id": "986325076436",
    "akas": [
      "arn:aws:elasticbeanstalk:us-east-1:986325076436:environment/turbottest18015/turbottest18015"
    ],
    "region": "us-east-1",
    "title": "turbottest18015"
  }
]
✔ PASSED

POSTTEST: tests/aws_elastic_beanstalk_environment

TEARDOWN: tests/aws_elastic_beanstalk_environment

SUMMARY:

1/1 passed.

### Basic ElasticBeanstalk Environment info

### list of Environments whose AbortableOperationInProgress is set enable
+------------------+---------------------------------+
| environment_name | abortable_operation_in_progress |
+------------------+---------------------------------+
+------------------+---------------------------------+
(Note: Since AbortableOperationInProgress is false for all the Environments present in Account )
select
  environment_name,

from
  aws_elastic_beanstalk_environment
where
  abortable_operation_in_progress = 'false';

+------------------+---------------------------------+
| environment_name | abortable_operation_in_progress |
+------------------+---------------------------------+
| Turbot-env       | false                           |
| Rups-env-007     | false                           |
+------------------+---------------------------------+
### list the Environments whose health is not responsive
+------------------+----------------+--------+
| application_name | environment_id | health |
+------------------+----------------+--------+
+------------------+----------------+--------+
(Note: It's showing Empty As there is no Environments whose heath is 'Red')
select
  environment_name
  application_name,
  environment_id,
  health
from
  aws_elastic_beanstalk_environment
where
  health = 'Grey';

+------------------+----------------+--------+
| application_name | environment_id | health |
+------------------+----------------+--------+
| Turbot-env       | e-daai6sq2mc   | Grey   |
| Rups-env-007     | e-xnpckaqsgp   | Grey   |
+------------------+----------------+--------+
### list of applications running in environment whose health status disabled
+------------------+---------------+
| environment_name | health_status |
+------------------+---------------+
| Rups-env-007     | Suspended     |
| Turbot-env       | Suspended     |
+------------------+---------------+

Run the integration test after making the changes

I have run the test again. It's working fine.


Add a copy of the MIT license

It is good practice to add a copy of the license to the repository.

I always forget that part. Thank you :)


Demo: Automatically kill http server process

Starting the demo Director (demo_director) or demo Image Repository (demo_oem_repo) Popens an http simple server process. Currently, users are instructed to kill this background process before exiting by running do.kill_server() or dd.kill_server() (respectively) before running exit().
Automate this so that when the Python shell exits, these are killed without user intervention.

please have a look PR #39
https://github.com/uptane/uptane/pull/39


broken 4.1.0 release

There is a massive quality downgrade in the latest release.
The internal directory is named 'yubioath-desktop-yubioath-desktop-4.1.0' and there is no more standard setup.py file.
Please revert these back.

It's not a python package in itself anymore, that is why there is no setup.py. If you are looking for build instructions, see #143.

I have started to convert to qt and cmake and still look messy.
I'll file a separate issue


line_draw always draws with width=1

Operating system or device - Godot version: Godot 3(master), Linux
Issue description:
Using any width value in draw_line seems to be useless, the drawn line is always 1px(?) in width.

From IRC logs:
[17:33] <reduz_> nunod, in 3.0? not sure what to do about it, opengl 3.x does not support it
[17:33] <reduz_> nunod, as well as antialiasing, it's not supported either
[17:34] <reduz_> nunod, there probably should be a way around this, but i have no idea how to solve it
[17:34] <reduz_> for line width, a triangle could be used, which is not too bad
[17:34] <reduz_> well, two triangles
[17:34] <reduz_> but for antialiasing, no clue
[17:34] <nunod> reduz_, antialiasing seems to work fine
[17:34] <nunod> only the width is ignored
[17:35] <reduz_> i know, i mean antialiased thick lines
[17:39] <reduz_> nunod, it could be done with a shader without that much difficulty i guess, will have to see how to fix this eventually
[17:40] <reduz_> it must be fixable somehow
[17:40] <reduz_> i can think of ways to fix it, it's just not simple
[17:41] <Akien> reduz_: https://mattdesl.svbtle.com/drawing-lines-is-hard
[17:42] <Akien> Looks useful

In Godot master it's possible to draw polygon-based thick lines with Line2D ;)

@Zylann I tried it, but can't get anything to show on the screen. Any examples available?

2D shapes themselves aren't broken, but this is: https://github.com/godotengine/godot/issues/7840#issuecomment-280926186

@Zylann so... it doesnt work at the moment, right? :)

It works but you can't see it (in the issue I linked you can see the wireframe is correct), so... for the end user it doesn't works indeed^^

so I guess its safe to close this, since the problem is basically in #7840 , right?

I found SpatialMaterial has an option for line width, which I needed to make some debug lines more visible, but it has no effect. Should it be removed or are there plans to implement general purpose line rendering in both 2D and 3D?

If not done already, it could probably be reimplemented in the GLES2 backend. According to @reduz in https://github.com/godotengine/godot/issues/8289#issuecomment-292216210 the usual method is not supported in GLES3, so it needs a different implementation (or it will be fixed only when properly implemented in the Vulkan backend).

I have tested GLES2 on Godot 3.1 alpha 2, and it is the same.
So maybe we should drop or disable Line Width property  in GeometryInstance for now?
It can be quite confusing, at current state.

I have researched this a bit, and apparently this is not a bug.
According to some standards (sorry no source) rendering API should support rendering a line with at least 1px width.
What I managed to dig up is that modern Opengl, and DirectX support line_width=1 and that is all.
This is probably because drawing a line as a geometry is usually used only for debuging (e.g. ray tracing) and wireframe rendering. For game purposes you will most of the time use textured quads, So this is why they might have dropped it.
Regarding Line Width property in GeometryInstance. If we want to render lines that are thicker, we need to write our own method for doing so. Line Width property is just not supported.
Unless I'm completely wrong, we might just need to drop Line Width property altogether, and think about Lines3D node.
As mentioned before drawing-lines-is-hard.

I'm having this problem in 3D in Godot 3.1.1, in both GLES2 and 3.

@Skaruts It seems the 3D issue has been mentioned above in this thread, no need to create a new issue.

@Calinou, indeed. I was just wondering.
Although, I'm also wondering how the editor's 3D gizmos are drawn. Because they have thick lines. Could you point me to the place in Godot's source where this happens? I've no clue where to find it, but I wonder if I might find a workaround there.

@Skaruts It's in spatial_editor_gizmos.cpp:
https://github.com/godotengine/godot/blob/ad0d87b4dddfe6b9e88510dd526bcd4028ba3030/editor/spatial_editor_gizmos.cpp#L203
Gizmos are drawn using procedural meshes generated using ArrayMesh.

@Calinou interesting... I always thought the manipulators would be made with ImmediateGeometry.
Anyway, thanks a lot for pointing me to it.

For me (v3.1.2 stable, Linux) the width seems to be working, but it is the antialiased=true which doesn't seem to have any effect:

Is this expected / tracked by this or another issue?

For me (v3.1.2 stable, Linux) the width seems to be working, but it is the antialiased=true which doesn't seem to have any effect:
draw_line(Vector2(0, 0), Vector2(100, 200), Color(255, 0, 0), 3.0, true)

Is this expected / tracked by this or another issue?

I'm on v3.2 stable, Linux, having the same issue with anti-aliasing

@bluenote10 Color(255, 0, 0) will create an extremely overbright red color (255 times brighter than a non-overbright red)! This is why you can't see the antialiasingh effect at all. You want to use Color(1, 0, 0) or Color8(255, 0, 0) instead :wink:

Can anyone still reproduce this bug in Godot 3.2.3 or any later release?
If yes, please ensure that an up-to-date Minimal Reproduction Project (MRP) is included in this report (a MRP is a zipped Godot project with the minimal elements necessary to reliably trigger the bug). You can upload ZIP files in an issue comment with a drag and drop.

@KoBeWi it's not working for me in 3D, netiher in GLES2 nor GLES3. Lines are all 1 width. However, GLES3 doesn't work well anyway in my old Radeon HD 4870, and I don't know if it's supposed to work in GLES2 to begin with.
I suppose I can try to find time to make an MRP, if this is supposed to work in GLES2. I won't fiddle with GLES3, as it stalls a lot on my end.

@KoBeWi it's not working for me in 3D, netiher in GLES2 nor GLES3. Lines are all 1 width. However, GLES3 doesn't work well anyway in my old Radeon HD 4870, and I don't know if it's supposed to work in GLES2 to begin with.
I suppose I can try to find time to make an MRP, if this is supposed to work in GLES2. I won't fiddle with GLES3, as it stalls a lot on my end.

However, GLES3 doesn't work well anyway in my old Radeon HD 4870, and I don't know if it's supposed to work in GLES2 to begin with.

GLES2 should work on old GPUs, but GLES3 isn't expected to work correctly indeed.

However, GLES3 doesn't work well anyway in my old Radeon HD 4870, and I don't know if it's supposed to work in GLES2 to begin with.

GLES2 should work on old GPUs, but GLES3 isn't expected to work correctly indeed.

GLES2 should work on old GPUs, but GLES3 isn't expected to work correctly indeed.

I meant the line widths, though. But I guess you answered my question, and it's not supposed to work at all in my gfx card, at least in 3.2.x. (I'll be switching to an NVIDIA soon anyway.)

GLES2 should work on old GPUs, but GLES3 isn't expected to work correctly indeed.

I meant the line widths, though. But I guess you answered my question, and it's not supposed to work at all in my gfx card, at least in 3.2.x. (I'll be switching to an NVIDIA soon anyway.)

I don't think this a problem in master, especially after fixes like https://github.com/godotengine/godot/pull/69851. Hardware limitation still applies of course, as described above.


Game crashing when making Terraforged worlds.

When attempting to generate a new world the game crashes and I get the exit code -1. Steps to reproduce the behavior: It happens when I try to make a new world using Terraforged. Everything should be compatible, I have the mod that makes the two compatible and I'm 95% certain I've got the right versions of all 3 mods, but the crash reports says something about there being an issue with generating the bushes? I am not using Optifine.
CRASH REPORT:
https://gist.github.com/Chann3l-Chas3r/5d48a9cf9fec0e37c2d4652ae349faf6
VERSIONS:

Dynamic Trees: 1.16.5-0.10.0-Beta27
Forge: 1.16.5-forge-36.2.34
Java: 8.0.3330.2
OS: Windows 10

I'm fairly certain this issue has already been resolved. Please update to the latest version of DT and try again.


Arg metatdata in Guild.create_scheduled_event is optional, but Discord API requires it

Summary
If metadata (optional) is not set, it will result in a 400 Bad Request Error
Reproduction Steps

Make a simple basic bot
Get any guild
Create a event without metadata
See the error

Minimal Reproducible Code
No response
Expected Results
Event should be created with just no metadata
Actual Results
Exception has occurred: HTTPException
400 Bad Request (error code: 50035): Invalid Form Body
In entity_metadata: This field is required
Intents
Default
System Information

Python v3.11.6-final
nextcord v2.6.0-final
aiohttp v3.9.1
system info: Linux 6.6.6-pikaos #4 SMP PREEMPT_DYNAMIC Tue Dec 12 11:16:44 UTC 2023

Checklist

[X] I have searched the open issues for duplicates.
[X] I have shown the entire traceback, if possible.
[X] I have removed my token from display, if visible.

Additional Context
I dont have time to make a PR for this atm, so I will leave this issue here, and if I find the time make a PR for it.

Actually it's not a bug, it's expected behaviour: https://discord.com/developers/docs/resources/guild-scheduled-event#guild-scheduled-event-object-guild-scheduled-event-entity-metadata - "*required for events with 'entity_type': EXTERNAL".
Although I wonder if this shouldn't be better documented or something. Maybe some note in the docs.

yea, this is just a docs issue. nothing to add to the code's logic here.


Android: ACCESS_FINE_LOCATION permission required after NS ~6.1.0

As of NS 6.1.0 or so, ACCESS_COARSE_LOCATION is not sufficient to use BLE; ACCESS_FINE_LOCATION is required. The plugin does not request this permission, requiring the use of nativescript-permissions or other method to explicitly request ACCESS_FINE_LOCATION prior to use.

This isn't related to NS 6.1.0, but Android 10. If you deploy to Android 8, for example, the coarse location will still function correctly.
https://developer.android.com/about/versions/10/privacy/changes#location-telephony-bluetooth-wifi
(Note that I agree that this should be fixed in this library.)


tests: subsys: shell: shell.core and drivers.can.shell fails at shell_setup

Describe the bug
The tests/subsys/shell/shell/shell.core and  tests/drivers/can/shell/drivers.can.shell fails
Observed for:

nrf52840dk_nrf52840
nrf52dk_nrf52832
nrf9160dk_nrf9160
nrf9160dk_nrf9160_ns
nrf5340dk_nrf5340_cpuapp
nrf5340dk_nrf5340_cpuapp_ns
nrf5340dk_nrf5340_cpunet

To Reproduce
Steps to reproduce the behavior:

have nrf52840dk_nrf52840 connected
go to your zephyr dir
call ./scripts/twister -T tests/subsys/shell/shell -p nrf52840dk_nrf52840 --device-testing --device-serial /dev/ttyACM0 -v --inline-logs
See console output with error

Expected behavior
Valid console output
Impact
Not clear
Logs and console output
[2022-09-07T22:19:07.153Z] ERROR   - *** Booting Zephyr OS build zephyr-v3.1.0-4878-g897ae4a2d5df  ***
[2022-09-07T22:19:07.153Z] Running TESTSUITE shell
[2022-09-07T22:19:07.153Z] ===================================================================
[2022-09-07T22:19:07.153Z] Assertion failed at ../../../../../../../../../zephyr/zephyr/tests/subsys/shell/shell/src/main.c:498: shell_setup: (shell_ready(sh) is false)
[2022-09-07T22:19:07.153Z] timed out waiting for dummy shell backend
[2022-09-07T22:19:07.153Z] START - test_cmd_clear
[2022-09-07T22:19:07.153Z] FAIL - test_cmd_clear in 0.001 seconds
[2022-09-07T22:19:07.153Z] ===================================================================
[2022-09-07T22:19:07.153Z] START - test_cmd_dict
[2022-09-07T22:19:07.153Z] FAIL - test_cmd_dict in 0.001 seconds
[2022-09-07T22:19:07.153Z] ===================================================================
[2022-09-07T22:19:07.153Z] START - test_cmd_history
[2022-09-07T22:19:07.153Z] FAIL - test_cmd_history in 0.001 seconds
[2022-09-07T22:19:07.153Z] ===================================================================
[2022-09-07T22:19:07.153Z] START - test_cmd_mand_1_opt_raw
[2022-09-07T22:19:07.153Z] FAIL - test_cmd_mand_1_opt_raw in 0.001 seconds
[2022-09-07T22:19:07.153Z] ===================================================================
[2022-09-07T22:19:07.153Z] START - test_cmd_resize
[2022-09-07T22:19:07.153Z] FAIL - test_cmd_resize in 0.001 seconds
[2022-09-07T22:19:07.153Z] ===================================================================
[2022-09-07T22:19:07.153Z] START - test_cmd_select
[2022-09-07T22:19:07.153Z] FAIL - test_cmd_select in 0.001 seconds
[2022-09-07T22:19:07.153Z] ===================================================================
[2022-09-07T22:19:07.153Z] START - test_cmd_shell
[2022-09-07T22:19:07.153Z] FAIL - test_cmd_shell in 0.001 seconds
[2022-09-07T22:19:07.153Z] ===================================================================
[2022-09-07T22:19:07.153Z] START - test_mand_2_opt_raw
[2022-09-07T22:19:07.153Z] FAIL - test_mand_2_opt_raw in 0.001 seconds
[2022-09-07T22:19:07.153Z] ===================================================================
[2022-09-07T22:19:07.153Z] START - test_max_argc
[2022-09-07T22:19:07.153Z] FAIL - test_max_argc in 0.001 seconds
[2022-09-07T22:19:07.153Z] ===================================================================
[2022-09-07T22:19:07.153Z] START - test_section_cmd
[2022-09-07T22:19:07.153Z] FAIL - test_section_cmd in 0.001 seconds
[2022-09-07T22:19:07.153Z] ===================================================================
[2022-09-07T22:19:07.153Z] START - test_set_root_cmd
[2022-09-07T22:19:07.153Z] FAIL - test_set_root_cmd in 0.001 seconds
[2022-09-07T22:19:07.153Z] ===================================================================
[2022-09-07T22:19:07.153Z] START - test_shell_fprintf
[2022-09-07T22:19:07.153Z] FAIL - test_shell_fprintf in 0.001 seconds
[2022-09-07T22:19:07.153Z] ===================================================================
[2022-09-07T22:19:07.153Z] START - test_shell_module
[2022-09-07T22:19:07.153Z] FAIL - test_shell_module in 0.001 seconds
[2022-09-07T22:19:07.153Z] ===================================================================
[2022-09-07T22:19:07.153Z] START - test_shell_wildcards_dynamic
[2022-09-07T22:19:07.153Z] FAIL - test_shell_wildcards_dynamic in 0.001 seconds
[2022-09-07T22:19:07.153Z] ===================================================================
[2022-09-07T22:19:07.153Z] START - test_shell_wildcards_static
[2022-09-07T22:19:07.153Z] FAIL - test_shell_wildcards_static in 0.001 seconds
[2022-09-07T22:19:07.153Z] ===================================================================
[2022-09-07T22:19:07.153Z] TESTSUITE shell failed.
[2022-09-07T22:19:07.153Z] Running TESTSUITE shell_1cpu
[2022-09-07T22:19:07.153Z] ===================================================================
[2022-09-07T22:19:07.153Z] Assertion failed at ../../../../../../../../../zephyr/zephyr/tests/subsys/shell/shell/src/main.c:498: shell_setup: (shell_ready(sh) is false)
[2022-09-07T22:19:07.153Z] timed out waiting for dummy shell backend
[2022-09-07T22:19:07.153Z] START - test_cmd_help
[2022-09-07T22:19:07.153Z] FAIL - test_cmd_help in 0.001 seconds
[2022-09-07T22:19:07.153Z] ===================================================================
[2022-09-07T22:19:07.153Z] TESTSUITE shell_1cpu failed.
[2022-09-07T22:19:07.153Z] ------ TESTSUITE SUMMARY START ------
[2022-09-07T22:19:07.153Z] SUITE FAIL -   0.00% [shell]: pass = 0, fail = 15, skip = 0, total = 15 duration = 0.015 seconds
[2022-09-07T22:19:07.153Z] - FAIL - [shell.test_cmd_clear] duration = 0.001 seconds
[2022-09-07T22:19:07.153Z] - FAIL - [shell.test_cmd_dict] duration = 0.001 seconds
[2022-09-07T22:19:07.153Z] - FAIL - [shell.test_cmd_history] duration = 0.001 seconds
[2022-09-07T22:19:07.153Z] - FAIL - [shell.test_cmd_mand_1_opt_raw] duration = 0.001 seconds
[2022-09-07T22:19:07.153Z] - FAIL - [shell.test_cmd_resize] duration = 0.001 seconds
[2022-09-07T22:19:07.153Z] - FAIL - [shell.test_cmd_select] duration = 0.001 seconds
[2022-09-07T22:19:07.153Z] - FAIL - [shell.test_cmd_shell] duration = 0.001 seconds
[2022-09-07T22:19:07.153Z] - FAIL - [shell.test_mand_2_opt_raw] duration = 0.001 seconds
[2022-09-07T22:19:07.153Z] - FAIL - [shell.test_max_argc] duration = 0.001 seconds
[2022-09-07T22:19:07.153Z] - FAIL - [shell.test_section_cmd] duration = 0.001 seconds
[2022-09-07T22:19:07.153Z] - FAIL - [shell.test_set_root_cmd] duration = 0.001 seconds
[2022-09-07T22:19:07.153Z] - FAIL - [shell.test_shell_fprintf] duration = 0.001 seconds
[2022-09-07T22:19:07.153Z] - FAIL - [shell.test_shell_module] duration = 0.001 seconds
[2022-09-07T22:19:07.153Z] - FAIL - [shell.test_shell_wildcards_dynamic] duration = 0.001 seconds
[2022-09-07T22:19:07.153Z] - FAIL - [shell.test_shell_wildcards_static] duration = 0.001 seconds
[2022-09-07T22:19:07.153Z] SUITE FAIL -   0.00% [shell_1cpu]: pass = 0, fail = 1, skip = 0, total = 1 duration = 0.001 seconds
[2022-09-07T22:19:07.153Z] - FAIL - [shell_1cpu.test_cmd_help] duration = 0.001 seconds
[2022-09-07T22:19:07.153Z] ------ TESTSUITE SUMMARY END ------
[2022-09-07T22:19:07.153Z] ===================================================================
[2022-09-07T22:19:07.153Z] RunID: 2bb8e2712b4acb012d716e5505d6f355
[2022-09-07T22:19:07.153Z] PROJECT EXECUTION FAILED

Environment (please complete the following information):

OS: Ubuntu 20.04.1 LTS
Toolchain Zephyr SDK 0.14.1
Commit SHA or Version used: v3.1.0-4878-g897ae4a2d5d

I think this is correlated with CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC=32768. WAIT_FOR() divides this by USEC_PER_SEC, which is 1000000 resulting in a cycle_count of 0:
#define WAIT_FOR(expr, timeout, delay_stmt)                                                        \
	({                                                                                \
		uint32_t cycle_count = (sys_clock_hw_cycles_per_sec() / USEC_PER_SEC) * (timeout); \
		uint32_t start = k_cycle_get_32();                                                 \
		while (!(expr) && (cycle_count > (k_cycle_get_32() - start))) {                    \
			delay_stmt;                                                                \
		}                                                                                \
		(expr);                                                                            \
	})

@nordic-piks Please see #50058

Setting priority to medium since this will cause a lot of hardware-in-the-loop tests to fail during our v3.2 stabilisation phase.


Ensure the metafields are preserved when amending a document

When amending a document, which happens when the publishing API sends an update, copy the _type and _id fields directly to the new Elasticsearch item. Currently, they are copied from the nested _source data, which has caused problems when the main _type and the _source _type are out of sync.
This will help prevent some of the bad data that has been appearing in search results over the past week: search results with the wrong _type value and duplicate results with the same URL but different _types.
https://trello.com/c/npsstuyq/103-elasticsearch-document-type-is-wrong-for-specialist-documents
Paired with @MatMoore

LGTM.
A bit more context:
The document type returned in ['_type'] and the document type returned in ['_source']['_type'] are different. We believe ['_source']['_type'] to be missing for most documents as a result of https://trello.com/c/mkn7SAn0/84-fix-reserved-field-name-errors-in-elasticsearch-2-x-upgrade.
Deploying this will stop us from creating duplicate documents when we should be updating existing ones.


Update es.json

Translation in native Spanish.

Thanks!
I'll make a new release with this update (and hopefully some other stuff that's currently in progress) later this week.


Duplicate and contradictory CSS rule in viewer.css

Hi team,
I've just noticed a duplicate definition of a CSS rule:
.toolbarField {
  ...
  border: 1px solid transparent;
   ...
  border: 1px solid hsla(0,0%,0%,.35);
  border-color: hsla(0,0%,0%,.32) hsla(0,0%,0%,.38) hsla(0,0%,0%,.42);

IMHO there's one or two rules too many.
For the sake of convenience, here's the link to the line in the repo.
Best regards,
Stephan

I'd like to claim this, if possible? See if I can figure out & fix it.
Thanks
Jessica

It's yours! I would check which rules are actually applied by the browser for .toolbarField using the developer console. I'm pretty sure the border: 1px solud transparent is overwritten by the other border entry, but I don't know which border color is used. I also think there are a few more CSS entries where the border has a color, but there is also a separate border-color property; I think the latter overrules the former.

As this issue was still opened, I had an initiative: https://github.com/mozilla/pdf.js/pull/11268. This PR refactors the viewer.css a bit + removes duplications mentioned above.
I hope it will be useful.
Thanks.

Hi, I guess @Zdobnov fixed it, let me know if there's still something to check here?
Thanks,
Jessica

Given that someone had already expressed interest in working on this less than a day ago, in https://github.com/mozilla/pdf.js/issues/11264#issuecomment-544543001 above, generally speaking it seems like somewhat bad form to just "steal" the issue.

@Virtual1 If you want to help the project, you could have a quick look at #11264 and confirm this bug has been solved. You could also have a look at a second code duplication. Originally, I wanted to open a second ticket, but chances are it has been solved, so we can probably simplify the process:

https://sonarcloud.io/project/issues?id=stephanrauh_ngx-extended-pdf-viewer&open=AW3qm3-l-dJmagWAuDEh&resolved=false&types=BUG
BTW: as soon as someone has confirmed the two duplicate rules have been fixed, we can close this ticket. :)

Closing since both problems are fixed by #11268. There was a lot of interest in the issue, so thank you all for helping out. If there are more things to fix in the CSS, please open a new issue.


Add CI

We need some sort of CI, possibly Travis. Once we get https://github.com/typelead/etlas/issues/39 done we can just have etlas take care of the eta installation for us.

If we use the typelead/eta:latest (or replace latest with the commit hash for the version you want). I'm comfortable with CircleCI so I can set that up for this using the docker image if you give me a basic idea of what test commands you want this to be able to run.

@rahulmutt Awesome! All that should need to run is ./gradlew assemble test


XPU Tensor fails in copy-on-write cases

🚀 The feature, motivation and pitch
To support or make XPU Tensor compatible with copy-on-write feature.
Case: TestCompositeCompliance::test_cow_input
AssertionError: False is not true : Keyword argument 'output grad 0' during backward call unexpectedly materializes. Either set supports_cow_input_no_materialize_backward=False in this operation's OpInfo, add the arg to the OpInfo's allow_cow_input_materialize_backward list, or change the implementation to avoid materialization.
Alternatives
No response
Additional context
No response

Need to discuss with @EikanWang

Three cases left:
"test_cow_input_addr_xpu_float32", because onednn addmv
"test_cow_input_cdist_xpu_float32", because onednn mm
"test_cow_input_nn_functional_multi_head_attention_forward_xpu_float32",because onednn addmm

PR merged and all the relevant UTs passed.


DeadClient when running on WSL

Which version of PhantomJS are you using? Tip: run phantomjs --version.
Version 2.1.1 with Poltergeist 1.10

What steps will reproduce the problem?

Attempt to run Cucumber tests on Capybara on Bash on Ubuntu on Windows 10 (tests run and pass on a pure Ubuntu set-up, code itself can be run up fine under WSL).

Result:
PhantomJS client died while processing {"id":"0053b3f4-ea57-4217-bcf0-895a1d49ba0a","name":"visit","args":["http://<IP_ADDRESS>:64001/users/sign_in",30]} (Capybara::Poltergeist::DeadClient)
This applies to any of the tests and any of the steps.

Which operating system are you using?
Bash on Ubuntu on Windows 10 - PhantomJS is installed under Ubuntu.

Description:  Ubuntu 14.04.5 LTS
Codename:   trusty

Did you use binary PhantomJS or did you compile it from source?
Binary - did have to add the bin path to the environment variables.

Please provide any additional information below.
Initially tried this with PhantomJS 1.9.8 on Poltergeist 1.9, this lead to a crash with no dump file - which I believe possibly indicates a permissions error? I'm a Linux newbie so while I'm happy to investigate I will need a bit of hand-holding I'm afraid.

Repo is https://github.com/xanthipe/bladesdb

Bash on Ubuntu on Windows 10
No surprise. Bash on Windows 10 has limited API.

There is a similar issue reported on BashOnWindows
Microsoft/BashOnWindows#903

Some headway over there:
"I was able to repro this and it looks like an Access Violation in PhantomJS i.e it is doing a NULL access/dereference somewhere. I don't know where exactly that is happening, yet. It requires the setup to be run under gdb or put enough print logs within PhantomJS. Anyone has ideas on how to run the whole setup ./node_modules/.bin/karma start --browsers PhantomJS under gdb or some other form of debugging PhatomJS here?"
Can anybody here provide some insight/guidance?

FYI, I'm reasonably sure the source of the crash is the lack of nonblocking connect() support in WSL causing a low-level QT error when using WebSockets.


Could you include our paper in the "General Prompt Learning paper list"?

Hi Zheng LI,
I hope you're doing well.
My name is Marco Mistretta, and I am a researcher at MICC (Florence, Italy). I wanted to express my appreciation for your work on the "Awesome Prompt Learning Paper" repository. It has been an invaluable resource for me.
I'm excited to share that my latest research paper has been accepted for publication at ECCV 2024.
Our work is orthogonal to your great work PromptKD and explores the unsupervised knowledge distillation but in the standard 16-shots setting
Could you please consider including it in the repository?
Thank you for your time and consideration!
TITLE: Improving Zero-shot Generalization of Learned Prompts via Unsupervised Knowledge Distillation
CONFERENCE: ECCV24
PAPER:  https://arxiv.org/abs/2407.03056
CODE; https://github.com/miccunifi/KDPL

Thank you so much for your prompt and positive response!
I appreciate your suggestion regarding these recent studies. We will definitely include them in the related work section in the ECCV camera-ready version!
Thank you again for your valuable feedback and for considering our paper for inclusion in your repository.
Best regards,
Marco Mistretta

Hi Zheng LI,
The ECCV24 camera-ready version of our paper is now available. It includes the missing references and additional results as you suggested.
Could you please include it in your repository?
Thank you!
Best regards,
Marco Mistretta

Hi @marcomistretta
I updated this list a week ago and it already includes your paper.


python3Minimal does not build on macOS with current staging

Describe the bug
#84072 seems to have broken the build for python3Minimal on macOS. The error is:
$ clang -L/nix/store/53kj31vsfqa4j8p1dz2y6n85sn5dbn3d-zlib-1.2.11/lib -L/nix/store/i36f95v4mjdx7bll0kzhl5mwqk49cj1m-bzip2-<IP_ADDRESS>.1/lib -L/nix/store/xv5zvirmalz6x7fx2h3axzkqxfpxicb6-expat-2.2.8/lib -L/nix/store/my4hsdi9hhp6lgh90vf6v8rsqmwaqwh5-xz-5.2.5/lib -L/nix/store/ppm2qmsxip74vxzrdvwg14f66ar9hzv9-libffi-3.3/lib -L/nix/store/53kj31vsfqa4j8p1dz2y6n85sn5dbn3d-zlib-1.2.11/lib -L/nix/store/i36f95v4mjdx7bll0kzhl5mwqk49cj1m-bzip2-<IP_ADDRESS>.1/lib -L/nix/store/xv5zvirmalz6x7fx2h3axzkqxfpxicb6-expat-2.2.8/lib -L/nix/store/my4hsdi9hhp6lgh90vf6v8rsqmwaqwh5-xz-5.2.5/lib -L/nix/store/ppm2qmsxip74vxzrdvwg14f66ar9hzv9-libffi-3.3/lib   -Wl,-stack_size,1000000  -framework CoreFoundation -o Programs/_testembed Programs/_testembed.o -L. -lpython3.8 -lintl -ldl    -framework CoreFoundation
ld: warning: ld: warning: object file (/nix/store/0lsij4jl35bnhqhdzla8md6xiswgig5q-Libsystem-osx-10.12.6/lib/crt1.10.6.o) was built for newer OSX version (10.12) than being linked (10.6)object file (/nix/store/0lsij4jl35bnhqhdzla8md6xiswgig5q-Libsystem-osx-10.12.6/lib/crt1.10.6.o) was built for newer OSX version (10.12) than being linked (10.6)

Reverting that MR seems to work fine.
To Reproduce
Steps to reproduce the behavior:

check out staging
nix-build . -A pkgs.python3Minimal

Expected behavior
The package should build correctly.
Notify maintainers
@gnprice @FRidh
Metadata
 - system: `"x86_64-darwin"`
 - host os: `Darwin 19.4.0, macOS 10.15.4`
 - multi-user?: `no`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.3.3`
 - channels(parthy): `"nixpkgs-20.09pre226586.571212eb839"`
 - nixpkgs: `/Users/parthy/.nix-defexpr/channels/nixpkgs`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

cc @NixOS/darwin-maintainers
Does python38 built currently on darwin? Aside from the optimizations we changed default Python from 3.7 to 3.8, that goes also for python3Minimal.

After reverting that PR I mentioned, I was able to build /nix/store/jxjwj1aa7srdkaivv72ifgf60ryprj3a-python3-minimal-3.8.3.

One part got reverted, the other significant part is behind a switch, which is put to false for python3Minimal.
If you take staging (where it failed), and you would set python3 = python37, does it build then?

If I do python3Minimal = (python37.override { instead of python3Minimal = (python38.override {, it still doesn't work.
Only the revert does the trick for me.

BTW, default python38 is also affected (non-minimal), e.g. this build.

This has been fixed.


Fix line endings in build.sh within template package

When trying to run the build.sh from a new project creation from the template, you are met with the following:

This is due to line endings in the file not being compatible when running on a Mac.
This will likely require the addition of a .gitattributes file to the repository to ensure that the line endings are correct.

This also impacts the build.config file, since the comparison of version number in the build.sh file doesn't work, since the line feeds in the build.config file are CR/LF.
It goes from this:

To this, once line feeds are adjusted to LF:


Updated swear words

If you know what happened in the past, you know why im adding "rape" and different variants of it to the swear list"

Maybe add "rap3" combined with those other variants

This is a terrible PR. The word was removed in This merge. The reason is how the system works. Words like "Grape" and other types of words will be blocked. Nobody uses the word enough for it to need to be blocked. You seem to just be but hurt people keep bringing it up.
There are a TON of words like this as well not just grape. Like "SkyScrapper, Scrape" and others so I don't see the point of this PR.

🤦

This is a terrible PR. The word was removed in This merge. The reason is how the system works. Words like "Grape" and other types of words will be blocked. Nobody uses the word enough for it to need to be blocked.
There are a TON of words like this as well not just grape. Like "SkyScrapper, Scrape" and others so I don't see the point of this PR.

raw facts


Add lock/unlock to deploy task

Q
A

Bug fix?
Yes

New feature?
No

BC breaks?
No

Deprecations?
No

@mficzel What do you think about this?


undefined reference to 'JVM_LatestUserDefinedLoader'

I am trying to compile a first basic version of my software for Android but after 41 minutes of building it fails with the following error message: undefined reference to 'JVM_LatestUserDefinedLoader'
(See attached log file for more detailed output.) I have no idea where that comes from and after searching on Google it seems I am not the only one with this problem. It is also strange that this exact same code builds just fine on my Mac. I can also build the HelloFX from the client samples with my setup for Android without problems.
This attempt of an Android build was done on:
Windows 10 running WSL2 with Ubuntu 20.04
Gluon Client plugin for Maven 0.1.23
https://download2.gluonhq.com/substrate/graalvm/graalvm-svm-linux-20.1.0-ea+28.zip
client-debug0.log.1.zip

Is this still an issue with the latest versions? Else, can we close it?

This seems very old (from May). I think that can be closed.


Pims sookeke to Dev

Codecov Report

Merging #15 (74168b8) into dev (0fce5f0) will decrease coverage by 3.01%.
The diff coverage is 97.90%.

@@            Coverage Diff             @@
##              dev      #15      +/-   ##
==========================================
- Coverage   80.16%   77.15%   -3.02%
==========================================
  Files         653      370     -283
  Lines       15713     6556    -9157
  Branches     2241      604    -1637
==========================================
- Hits        12596     5058    -7538
+ Misses       2838     1336    -1502
+ Partials      279      162     -117

Flag
Coverage Δ

unittests
77.15% <97.90%> (-3.02%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...end/api/Areas/Admin/Controllers/ClaimController.cs
0.00% <0.00%> (ø)

...d/api/Areas/Keycloak/Controllers/UserController.cs
100.00% <ø> (ø)

...kend/api/Areas/Tools/Controllers/LtsaController.cs
100.00% <ø> (ø)

backend/api/Controllers/AuthController.cs
0.00% <0.00%> (ø)

backend/api/Controllers/ErrorController.cs
0.00% <0.00%> (ø)

...api/Helpers/Authorization/KeyCloakClaimsFactory.cs
0.00% <ø> (ø)

...ackend/api/Helpers/Converters/PropertyConverter.cs
85.71% <ø> (ø)

...ckend/api/Helpers/Extensions/DateTimeExtensions.cs
0.00% <0.00%> (ø)

backend/api/Helpers/Extensions/MapperExtensions.cs
0.00% <0.00%> (-38.10%)
:arrow_down:

...end/api/Helpers/Swagger/ConfigureSwaggerOptions.cs
0.00% <0.00%> (ø)

... and 542 more


[QUESTION] Distinguishing different clients

I am developing a client-server architecture using aeron in C. Multiple publishers connect to a single subscriber.  When subscriber receives a message, it has to identified from which client the message is receiving and send a message back to the client.

How the identification should be done?
How to get the channel from which the message is receiving?

You might check into how the Java client handles this for the Archive and Cluster.

I have tried the following:
When the subscriber received a message, I get the session id using
sess_id = aeron_header_session_id(header);
But message from different clients are having same session ID. Why is it having same session ID. Isn't session ID suppose to be different for different clients?

First make sure that the value returned, if -1, doesn't indicate an error.
Also, Session ID is only guaranteed to be different for the same media driver. Between media drivers, they may not be unique. Using Session ID is not enough to be unique.
If you look at the Archive and Cluster clients, the server side assigns an ID to the client and sends it back. The request has a respond-to type field (stream ID and channel) to send responses to. The response acts as both an ACK of the request and can hold whatever information (client ID, for example, is only part of it) is required to continued operation.

I am using a single external media driver and exclusive publication. So client identification problem is solve using the session ID of the received message as session id is guaranteed to be different in same media driver.
I have multiple clients running its own subscriber. The subscriber stream ID and port is different for each client. Whenever a client connects to the server for the first time, it sends its subscriber info (stream ID and port) to the server. Then the server creates a publisher to connect to the subscriber of the client.
In short, the server creates a publisher for each client. All the publishers have different stream ID and port.
The problem is, when I run with 6-7 clients, two publishers (created on server side) are having same publication session ID. Below is the log:

Setup new aeron publisher done. channel: [aeron:udp?endpoint=<IP_ADDRESS>:2000], stream_id: [2000], pub_sess_id: [2041103187], msg_hdr_session_id: [2041103186]```

Here the stream ID and port are different but they are having the same publication session ID. As a result when I respond to the clients, one client is getting the messages for both the clients.

NOTE:
`pub_sess_id` in the log is the publication session ID. I get the session ID using `aeron_publication_session_id`
I am running the server and clients on same machine.
I tried with the exclusive publications also. Same result.

My question is: Why the publishers are having same session id even if they have different port and stream ID?

If you can replicate it in a test, let us know.

Actually, what version are you using? If using the C API, you should really be using the head of the repo.

After using the head of the repo, the issue is gone.


Not working

I followed the instructions exactly and it's not working for me.
Here's the error I get:
[Message:   BepInEx] BepInEx <IP_ADDRESS> - Plan B Terraform (2/18/2023 12:42:18 AM)
[Info   :   BepInEx] Running under Unity v2<IP_ADDRESS>55304
[Info   :   BepInEx] CLR runtime version: 4.0.30319.42000
[Info   :   BepInEx] Supports SRE: True
[Info   :   BepInEx] System platform: Bits64, Windows
[Message:   BepInEx] Preloader started
[Info   :   BepInEx] Loaded 1 patcher method from [BepInEx.Preloader <IP_ADDRESS>]
[Info   :   BepInEx] 1 patcher plugin loaded
[Info   :   BepInEx] Patching [UnityEngine.CoreModule] with [BepInEx.Chainloader]
[Message:   BepInEx] Preloader finished
[Message:   BepInEx] Chainloader ready
[Message:   BepInEx] Chainloader started
[Info   :   BepInEx] 0 plugins to load
[Message:   BepInEx] Chainloader startup complete
Screenshot of plugins in the correct folder: https://ibb.co/D1HhyhD

Got it working.

Got it working

You have to use the various zips, not download the source code.


Clarify punishment types and lengths

It should be a lot clearer to see what punishments are for what infringements, and what classes as an infringement in the first place.
ISSUE
At the moment, the punishments seems very vague, with vague rules about what is or isn't allowed, specifically with regards to 'doxing', and with seemingly non-existent mod guidelines about what a suitable punishment is for various infringements.
Recently, as I'm sure everyone is aware, me and Rowan were both temporarily banned for a whole 14 days, for 'doxing' and 'harassment'.
Firstly, I think the mods need to seriously reconsider what constitutes as doxing. The images me and Rowan posted (that I also removed out of guilt a mere second after posting), were from youtube videos on a members channel that was linked directly to their discord account.
Personally, it is my opinion that if information is 2 clicks away from someone's discord account, posting said info does not constitute doxing in any form. It is also particularly frustrating when mods who aren't aware of the situation make rash and uninformed comments, as people look up to them, and in my opinion as a mod, commenting on a ban before you have the full picture is simply unacceptable and downright negligent.
Secondly, lets address the only real criticism of what me and Rowan did, the harassment.
It is obviously very difficult to decide what is a suitable punishment, as harassment is a very broad spectrum. However, what was said by me in particular was completely SFW, and absolutely pales in comparison to some of the things that have been directed towards members before. Granted, what Rowan said was definitely more offensive, but again, things a lot worse, or roughly on the same level as that have been said frequently before in a much more serious manner, but have only resulted in short mutes, and ultimately nothing much has come of it.
I definitely think the way I and others have acted towards new and less experienced members of the server has to change, as looking from an outsiders perspective it does seem a bit daunting, I've been there myself, but also we shouldn't give too much sympathy towards people who insist on demanding help, and want to be carried through the entire course from an early stage.
Fundamentally, I think the issues that I have tried to touch on in this issue penetrate much deeper than just mine and Rowan's ban, and it is a fundamental issue of extreme mod bias and no proper system for mods to determine appropriate punishments.
PROPOSED SOLUTION
It is very hard for me to decide what I should write here, as realistically I don't think this issue will cause any change, especially considering the weight of the issues. Personally, I feel like this won't be fully fixed until several unnamed mods are demoted or at the very least change their downright extreme positions, or until someone who actually cares is appointed Sudo, or one of the Sudos who cares is appointed Root, if not preferably Owner.
One 'bandaid' fix I do propose though, is a public, comprehensive, and community-approved guideline for punishments, increasing clarity with regards to punishments 100-fold. It has become clear now that mods refuse to justify their decisions, and that in their opinion, we shouldn't even be questioning them in the first place. I am unwilling to accept this until we have something that clearly sets out reasoning behind punishments, and I believe such a guideline would act as a temporary fix, until some serious re-evaluation took place behind the scenes.
I would also of course like to see Rowan and I's cases re-evaluated, and I would propose either an immediate unban, or a reduction of the ban length, in accordance with what several respected members of the community feel is fair, and in accordance with past punishments.
Please feel free to add your opinions, I hope this post at the very least causes some discussion.

I agree with this, there have been many occasions where certain mods that I won't name seem to just make up rules and justify them with "I'm sudo so you do what I say".  There are also extremely bad double standards due to there being no guidelines set in stone for the moderators, sometimes a moderator will punish one person for something much less severe than something someone else has done, or punish two people differently for the same offence and severity. May it be due to the mood they're in currently, or whether they like/dislike that person, their decisions should not be affected by this, yet they still seem to be.

You want a full on judiciary system for a volunteer run Discord server... the mods spent a large part of the evening in question justifying their decisions, as they do all the time, people just don't always like the answer. Instead of moaning because you believe you're entitled to a 100% consistent system (you know real-life actual courts don't acheive that right?), you could just wait two weeks and move on with your life. Your proposed solution largley boils down to "I don't like the mods and want things to conform to be convenient for me specifically".

I'm going to comment on this, as this issue includes me specifically. I fully accept that what I did was wrong, and that I shouldn't be unbanned. However, I do think that more clarification and consistency on punishments would be a positive change - a change that the mods could benefit from too.

@teamshortcut

Your proposed solution largely boils down to "I don't like the mods and want things to conform to be convenient for me specifically".

This is bollocks. His proposed solution would actually save countless hours for the moderators as they wouldn't have to spend so long arguing over someones punishment, as it would most likely be in the guidelines. It might also lower the amount of incidents, as more people know what is and isn't acceptable.

Personally, I feel like this won't be fully fixed until several unnamed mods are demoted or at the very least change their downright extreme positions, or until someone who actually cares is appointed Sudo, or one of the Sudos who cares is appointed Root, if not preferably Owner.
"bollocks".

 Nothing wrong with that, if he and many others see that certain moderators act out of line, then there is clearly a problem.

I think you're missing the point here shortcut. We do not want a full judiciary system. That wouldn't be appropriate and probably would work.
What is being proposed is for us to help create a system which will improve the server and the moderators ability to achieve consistency, which although complete consistency may not be possible, more consistency is a goal.
And yes, this is a volunteer run server, but the volunteers took up responsibility to run this server and to try and run it well. While I will not comment on this exact example, the meta issue is not setting out to resolve this isolated case but instead try to improve the system and help with the moderation of the server.

One 'bandaid' fix I do propose though, is a public, comprehensive, and community-approved guideline for punishments
```This is not only a pipe dream, but it would be horribly unfair on the (human, mind you) mods to expect them to follow a "comprehensive guideline" for punishments. Either it's so comprehensive that it's impossible for a human, and so it gets merged into the bot instead, or it's not "comprehensive enough" because the mods are still allowed to, shock horror, decide things, and people complain about their decisions.

Look, I don't want to get involved in CD politics anymore but I feel like this needs to be said. Shortcut, you're not an admin anymore. Please stop being a backseat admin, you're making everyone's life worse, it doesn't help the admins because you still have a fair bit of perceived authority so it makes it more difficult for them when you're wrong, it doesn't help the community because they end up not being able to actually have meaningful discussions with each other and instead have to "debate" you, and it's just a waste of your time. You're intentionally misinterpreting what is being said to protect your friends. I get that, it's human instinct however if you really cared about the community, you'd let the issues be raised and you'd let your friends on the staff team get on with their job uninterrupted.

I think a public set of guidelines would still be beneficial.
Although mod actions are often made very quickly due to the nature of situations so guidelines would need some flexibility a public set of guidelines that mods can bear in mind when they take actions would allow for more consistency and the ability to go back, review and amend decisions later would help this.

Additionally, I hardly see how this is productive. I may not be in the community at the moment but I still care about it thriving, and it's clear to me that Shortcut has not actually read what Rak posted originally, but what he wanted to instead. While Rak's solution may not be the most practical, I appreciate that he's willing to step out and make the effort to actually fucking suggest something to make the server a better place, and doesn't need people like Shortcut rejecting an idea that quite frankly he chose not to read, and instead offer nothing to the contrary.
Cute how he sticks up for his friends, regardless.

Also totally unrelated but can you not change your verification settings to stop me responding, I own a mail server ffs.

I didn't realise ex-admins were barred from having and expressing their opinions, just like any other server member can; evidently my mistake.

I think the problem here is that you were expressing an opinion that didn't line up with the actual issue and was mostly irrelevant. You were attacking members for making suggestions to try and improve the server. Yes, rak being banned was probably the trigger for the issue, but it certainly wasn't what the issue boiled down to.
Also I think rejigging the staff would be beneficial. We have one active root who cares about the server and seems to be under a lot of stress because of it which isn't great.

I never said you couldn't express an opinion. The issue is with the way you do it, you're trying to deliver a definitive no when that's simply not for you to do anymore, instead of just blindly shooting down suggestions, try actually suggesting an alternative. The server needs some serious change, in part because of the precedent your caliber of response has set, you're no longer an admin so it's no longer your responsibility but you're still trying to stop change. You're not attempting to even provide a reason that the suggestion is invalid, you just resort to ridiculing the issue straight away, all that does is make you look bad. If a different person opened the exact same issue, you would have had a very different response. It's been clear for a long time that the punishment system needs reworking, so what's your suggestion?

Hi,
I understand your concern, and that it's frustrating that there is very little clarification on what situation warrants which punishment. The issue is that, with every case being vastly different in terms of context leading up to the event and the severity of the offence, it would be both unrealistic for us to anticipate everything and unfair to apply a fixed punishment for every variation. In addition, as far as mutes are concerned, the emphasis is on dealing with the problem as swiftly as possible, which means that we often only get a few seconds to evaluate and judge a suitable solution. It's unideal that there's variation between moderators, but the tradeoff is we are dynamic and able to quickly react to a large number of situations.
Your points are valid, however, we try to balance fair discussion with each moderator having room for discretion. In my opinion, the improvement can be made to documenting each case and providing a short, clear justification which doesn't seem unreasonable to me.
Regards,
Trefonix
This post and any other post I make are reflective of my personal opinions and do not necessarily reflect the stance of the staff team as a whole or any other individuals on the staff team

I understand that issues need to be acted upon quickly so it is difficult to judge and different moderators will act differently, but I think that a rough set of guidelines would still help with this as ideally they would be short enough that you would be able to remember them and not have to reference them.
I also fully support documenting cases with brief justification as I mentioned in #283

Seems like this will never happen.

rak i miss u already

Thanks

can this be re-opened?
it is a legit issue that needs solving.

Yep we should re-open this

It is a legit issue, but after no replies for 20 days I'm sceptical anything will change.

yes but it should remain open to show it is still an issue

Ok, I've reopened this because it is still an issue.

This issue was temporarily closed because GitHub banning is kinda a mess.

Opened on November 9th, 25 comments over a span of 3 weeks, with most commemters agreeing and very few disagreeing, yet nothing came from it. #meta in a nutshell.

This issue is also soon to be resolved by #315

Right closing time, since #315 covered this.


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>

Codecov Report

Merging #337 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #337   +/-   ##
=====================================
  Coverage      75%    75%
=====================================
  Files           1      1
  Lines           8      8
=====================================
  Hits            6      6
  Misses          2      2

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 afde594...73e75da. Read the comment docs.

Coverage remained the same at 70.0% when pulling 73e75dabfd165768deeb7fdd60dbf7a23e780fcb on template-sync-1 into afde5947c729d8b022919c0c066eb469c03103b1 on master.


Conflict with NativeScript push notification plugin

I am experiencing a conflict issue with the Google Services library used in this plugin. Errors are thrown in the Android build process when I try to use the NativeScript push notification plugin alongside yours.  After doing some research, I found that the problem is probably related to the following line:
https://github.com/transistorsoft/nativescript-background-geolocation-lt/blob/master/platforms/android/include.gradle#L12
Using a wildcard '+' character should not be done in NativeScript plugins.  It should be locked to a specific version to prevent conflicts.  Removing the geolocation plugin allows the application to be built successfully.
Here is some literature on the issue:
https://github.com/NativeScript/push-plugin/issues/101
https://github.com/EddyVerbruggen/nativescript-plugin-firebase#found-play-services900-but-version-10xy-is-needed
Please let me know when this is corrected and pushed to NPM.
Thanks
Austin Harris
Loadchief Developer

I've been doing this for over 3 years with Cordova and React Native.  play-services dependency issues are very common.
Ultimately, it's your own Application which should have the final word on your desired dependencies.  It's not up to any particular plugin to dictate this.
[Read this](How to solve Google Play Services version collision in gradle dependences) and take control over your dependencies in your own platforms/android/build.gradle.

For a paid plugin that advertises having support, I would have imagined a better response than this.
By using a '+' wildcard, it is probably the worst thing you could do and you're not doing yourself any favors because when Google changes the library and your entire plugin breaks, what are your customers going to do?  Would be nice if you could be more specific in the supported version like '10.0.+' or something. What should @loadchief build.gradle file look like without having to dig through a bunch of plugin source code?
Also, I'm not sure the relevancy of Apache Cordova or React Native responses in a NativeScript ticket. Are you implying that this is an unenthusiastic NativeScript port?
My two cents...

I've been using :+ for about 3 years, with Cordova and React Native, long before this NativeScript port existed.  That's why I mention the other versions.
There have been no issues with Google changes "breaking everything".

We're just trying to get help and offer suggestions.  We're not trying to belittle your experience.  I'm not sure why all you're so rude in all of your responses on this ticket and others that were opened.

I don't think I'm being rude nor do I feel you're trying to belittle me.
I mention the "3 years" only to make it clear that this is not unusual to me to hear about play-services dependency clashes. The issue is most often related to some other 3rd party plugin pinning their plugin at a specific version.
Fortunately with NativeScript, you can take control over your own build.gradle and provide your desired version of any particular play-services dependency.

If you hear about this issue so frequently, wouldn't it make sense to document this in your plugin documentation?  Document the problem as well as how to resolve it? Taking a link adventure is cool, but it is even better when it is clear in the documentation.
Would be nice to see an actual functioning build.gradle file with the changes.

If you hear about this issue so frequently, wouldn't it make sense to document this in your plugin documentation?

The problem is always with some other plugin pinning their play-services version.  For example, when a Cordova customer reports a similar problem, the first question I ask is "Are you using the cordova-plugin-googlemaps plugin?".  90% of time, it's "Yes, why?".  Over there, they're pinning play-services at 9.8.0.
Show me the result of $ tns plugin list

Now your next task is to determine all those plugins which include play-services as a dependency.
At a glance, I'd say that would be only nativescript-push-notifications (in addition to nativescript-background-geolocation-lt, which I don't see there.

Obviously the nativescript-push-notifications people are going to be causing issues pinning their google dependencies like they are

And you can see others expressing similar conflicts there with other plugins due to their pinned dependencies.

ok, thank you Chris.  Nic and I are going to work together on Wednesday to see if we can resolve the google play conflict and get both push and tracking to work together.

Clearly the problem is with push-plugin pinning firebase (which comes from play-services) at 10.0.1.  If you were to fork their repo and modify their build.gradle and modify that dependency version to :+, or 10.:+ it will work.
And @nraboy there's no way I'd pin to 10.0.+.  If anything, I'd pin to 10.2.:+, which would still cause push-plugin to break the build.
The current version of play-services is 10.2.4

ok, we will give that a shot, thank you!

@loadchief @nraboy  Were you guys able to fix this? I am thinking about buying this plugin but I also have Push Notifications installed...

@Daxito the problem is not at all with this plugin.  It's 100% an issue with the push-plugin.  Worst case, you fork push-plugin and fix their pinned play-services dependency.

Yes, we fixed the problem @Daxito. However, it is inaccurate to say that the issue is "100% an issue with the push-plugin" as that is not the case. The problem is with Android plugins in general and having shared dependencies that require different versions. @christocracy consistently tries to deflect the issue to someone else.
We fixed the issue by forking this background-geolocation plugin and changing the versions within this plugin. We did not touch the push notification plugin as it was already locked to a specific version where as the background-geolocation plugin had a wildcard to the latest.
For now it seems to be fine, but long term I imagine there will be other issues with this approach.
Best,

@nraboy When one plugin pins play-services as push-plugin does, it is 100% the fault of the other plugin.  No plugin should dictate to all other dependencies the specific version of play-services we must all abide.
The best solution is to contact push-plugin and tell them to stop forcing all other dependences to use an out-dated play-services version 10.0.1 where the current version is 10.2.4.
@Daxito:  @nraboy is 100% wrong here.

For now it seems to be fine, but long term I imagine there will be other issues with this approach.

I have 4 years experience dealing with this.  Your imagination is wrong.

I've never heard of someone going into production with a wildcard version. When you do that, what you build today may not match what you build tomorrow. Pinning your dependencies is the correct thing to do.
@Daxito in all honesty, I wouldn't recommend buying this plugin. For a paid plugin, the support you get from @christocracy is just terrible. Look through the closed tickets if you don't believe me. It is just a NativeScript port and his responses show this due to their little love.

Pinning dependencies is perfectly fine but it's your application build.gradle's responsibility -- It's not for some 3rd party plugin to dictate to your app.

Support is rapid and excellent.


Upgrade to sdk 5.3

5.3 is out, can you please upgrade sdk to latest

The newest version of this sample is now on master with version 5.3.