sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: gollvm: cmd/go: httpguts, hpack, idna are not using a known version control system
Labels: NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15rc2 gollvm LLVM 12.0.0git linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br>

<pre>
$ go env

GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/oceanfish81/.cache/go-build"
GOENV="/home/oceanfish81/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/oceanfish81/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/oceanfish81/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/tools"
GCCGO="/usr/local/bin/llvm-goc"
AR="ar"
CC="/usr/bin/clang"
CXX="/usr/bin/clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build842983669=/tmp/go-build -gno-record-gcc-switches -funwind-tables"
</pre>

</details>

### What did you do?

I was trying to get [StreamSets Data Collector Edge](https://github.com/streamsets/datacollector-edge) working.

> $ go get -u github.com/streamsets/datacollector-edge

### What did you expect to see?
At least - no warning or errors.


### What did you see instead?

> package golang.org/x/net/http/httpguts: directory "/usr/local/src/golang.org/x/net/http/httpguts" is not using a known version control system
> package golang.org/x/net/http2/hpack: directory "/usr/local/src/golang.org/x/net/http2/hpack" is not using a known version control system
> package golang.org/x/net/idna: directory "/usr/local/src/golang.org/x/net/idna" is not using a known version control system

@bradfitz, @FiloSottile , @alanbato, @mpvl - any suggestions?

Ivan
Repository: rust
Issue: wasi-sdk/bin/wasm-ld regression in 1.46.0
Labels: A-linkage,P-medium,T-compiler,regression-from-stable-to-stable,O-wasm,C-bug,E-needs-bisection

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried to cross compile a hello world with WASI SDK as explained at https://doc.rust-lang.org/nightly/nightly-rustc/rustc_target/spec/wasm32_wasi/index.html:

```bash
cargo init
wget https://github.com/WebAssembly/wasi-sdk/releases/download/wasi-sdk-11/wasi-sdk_11.0_amd64_ubuntu20.04.deb
sudo dpkg -i wasi-sdk_11.0_amd64_ubuntu20.04.deb
rm wasi-sdk_11.0_amd64_ubuntu20.04.deb
export CC_wasm32_wasi=/opt/wasi-sdk/bin/clang
export CARGO_TARGET_WASM32_WASI_LINKER=/opt/wasi-sdk/bin/clang
cargo build --target wasm32-wasi
```

I expected to see this happen: the build succeeds with Rust v1.45.2 , so next versions should be compatible.

Instead, this happened when updating to Rust v1.46.0: https://github.com/TjeuKayim/wasi-link-fail/runs/1109104907

```
error: linking with `/opt/wasi-sdk/bin/clang` failed: exit code: 1
##[error]  |
  = note: wasm-ld: error: unknown argument: --eh-frame-hdr
          clang-10: error: linker command failed with exit code 1 (use -v to see invocation)
```

And 1.48.0-nightly (2020-09-12) produces another error: https://github.com/TjeuKayim/wasi-link-fail/runs/1109104926

```
error: linking with `/opt/wasi-sdk/bin/clang` failed: exit code: 1
##[error]  |
  = note: wasm-ld: error: std-5fceb8daecdd3ed8.std.5ro3oaeh-cgu.0.rcgu.o: Bad relocation type: 
          clang-10: error: linker command failed with exit code 1 (use -v to see invocation)
```

A weird exception is my Manjaro Linux system with Rust 1.46.0, it only builds succesfully when I add `RUSTFLAGS='-C link-args=-Wl,-v'`. I have no clue why, and couldn't reproduce this on Ubuntu.

See this repository for a minimal reproduction https://github.com/TjeuKayim/wasi-link-fail.
Repository: godot
Issue: Editing AABB in the inspector causes odd behaviors and freezes
Labels: bug,topic:editor,confirmed

Godot 3.2.2
Godot 3.2.3 rc6
Windows 10 64 bits

When trying to edit the fields of an AABB property in the inspector using the `Tab` key to cycle through its fields, there is a point where the editor no longer switches to the next fields, or freezes completely.

When that happens, the console is flooded with errors like this:
```
Failed method: LineEdit:_update_callback target ID: 19800
TOTAL BYTES: 1048560
NULL count: 0
CALL : 43687
CALL show_modal: 1
CALL grab_focus: 1
CALL select_all: 1
ERROR: Message queue out of memory. Try increasing 'memory/limits/message_queue/max_size_kb' in project settings.
   At: core/message_queue.cpp:55
```

Reproduction project: 
[AABBInspector.zip](https://github.com/godotengine/godot/files/5215095/AABBInspector.zip)

1) Open `main.tscn` and select the Spatial node
2) Click in the `x` field of the AABB and hit `Tab` until you get  to `d` or Godot freezes.
3) If you got to `d`, deselect the field, and try 2) again. Godot will eventually freeze.
Repository: flutter
Issue: [in_app_purchase] specify that purchaseUpdatedStream don't return previous purchases
Labels: d: api docs,p: in_app_purchase,package,team-ecosystem,P3,triaged-ecosystem

## Use case

The [docs](https://pub.dev/documentation/in_app_purchase/latest/in_app_purchase/InAppPurchaseConnection/purchaseUpdatedStream.html) says that `InAppPurchaseConnection.purchaseUpdatedStream` will return real time updates for purchases, but does that mean you will get only new purchases since you started listening to the stream, or does that also include previous purchases?

## Proposal

Maybe the docs should clearify if you don't receive previous purchases in `purchaseUpdatedStream` ( like you do with `queryPastPurchases`? ). 

Both methods have a list of `PurchaseDetails`, i suggested to combine these two methods in a single stream in #58170
Repository: flutter
Issue: Coverage results are different depend on the application structure
Labels: a: tests,tool,has reproducible steps,P2,team-tool,triaged-tool,found in release: 3.19,found in release: 3.22

I have 2 Flutter repos with different structure as below. The source content is the same but we have 2 different results in the coverage report. Do you know what cause the issue? And why `main.dart` not counted? Appreciate your help. Thanks

```
.
├── lib
├── ├── widgets
│   ├──├── circle_container_widget.dart
│   ├── main.dart
├── test
│   ├── circle_container_widget_test.dart
│   ├── material_test_widget.dart
```
Repo URL: https://github.com/SuTran/flutter_coverage
Coverage: 100%
`main.dart` not counted in the coverage report

```
├── lib
│   ├── widgets
│   │  ├── circle_container_widget.dart
│   │  ├── __test__
│   │  │  ├── circle_container_widget_test.dart
│   ├── main.dart
│   ├── material_test_widget.dart
```
Repo URL: https://github.com/SuTran/flutter_coverage_02
Coverage: 21.1%
`main.dart` counted in the coverage report
Repository: pytorch
Issue: CUDA RuntimeError unrecoverably bricks session
Labels: module: cuda,triaged

## 🐛 Bug

A bad input can completely brick a CUDA session.

## To Reproduce
```python
import torch.nn.functional as F

# CPU No issues
x = torch.zeros(10) - 2
y = torch.ones(10)
try:
    F.binary_cross_entropy(x,y)
except:
    pass
x+y

# CUDA: big problems
x = torch.zeros(10).cuda() - 2
y = torch.ones(10).cuda()
try:
    # bricks your session
    F.binary_cross_entropy(x,y)
except:
    pass
# now all operations give a RuntimeError
x+y
```
## Expected behavior

`x+y` should succeed without error.

## Environment
```
Collecting environment information...
PyTorch version: 1.6.0+cu101
Is debug build: False
CUDA used to build PyTorch: 10.1

OS: Ubuntu 18.04.5 LTS (x86_64)
GCC version: (GCC) 6.3.0
Clang version: Could not collect
CMake version: version 3.10.2

Python version: 3.8 (64-bit runtime)
Is CUDA available: True
CUDA runtime version: 9.1.85
GPU models and configuration: 
GPU 0: GeForce GTX 1060 3GB
GPU 1: GeForce RTX 2080 Ti

Nvidia driver version: 435.21
cuDNN version: /usr/lib/x86_64-linux-gnu/libcudnn.so.7.0.5

Versions of relevant libraries:
[pip3] numpy==1.19.1
[pip3] pytorch-lightning==0.9.0
[pip3] torch==1.6.0+cu101
[pip3] torchvision==0.7.0+cu101
```

## Additional context
This is especially painful for hyperparameter searches, where we want to be robust against such errors and just try again.

This problem occurs a lot in the wild:
https://stackoverflow.com/questions/60883510/pytorch-recover-from-runtimeerror-cuda-error-device-side-assert-triggered-with
https://stackoverflow.com/questions/54585685/how-to-reset-colab-after-the-following-cuda-error-cuda-assert-fails-device-sid

cc @ngimel
Repository: opencv
Issue: opencv4.4,  issue about opening the stereo camera
Labels: question (invalid tracker),category: videoio(camera),incomplete

----------------------------
- OpenCV => 4.4
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2017

****************update
- OpenCV package(downloaded from the official website, https://opencv.org/)
- Used videoio backend(unknown, but i put opencv_videoio_ffmpeg440_64.dll in ...\project\x64\Debug and ...\project\x64\Release. So i assume the backend i use is ffmpeg)

- product name(it has no brand! I bought it on Taobao, which was produced in shenzhen)

- sample code(resolution:1280x480 total)
  	Mat frameL, frameR;
	VideoCapture cap(1);
	cap.set(CV_CAP_PROP_FRAME_WIDTH, 640);
	cap.set(CV_CAP_PROP_FRAME_HEIGHT, 480);
	VideoCapture cap2(2);
	cap2.set(CV_CAP_PROP_FRAME_WIDTH, 640);
	cap2.set(CV_CAP_PROP_FRAME_HEIGHT, 480);
	while (true)
	{
		cap >> frameL;
		cap2 >> frameR;
		imshow("L", frameL);
		imshow("R", frameL);
		waitKey();
	}
****************

----------------------------
The type of the stereo camera that we currently use is that two cameras are seperated, which means you need two VideoCapture to read both cameras. 

In the version of 4.4, we can't read both cameras at the same time!  We can only read one camera once at a time.
However, such problem did not appear when we used the version of 4.0 or 4.3.
So I was wondering if there were any changes in the version of 4.4 that leads to this problem?


Thank you in advance!
Repository: flutter
Issue: Flutter tool can fail to find the Android emulator if adb isn't already running
Labels: platform-android,tool,P2,team-android,triaged-android

## Steps to Reproduce

1. Run an Android emulator.
2. `adb kill-server && flutter doctor -v`

## Result

On my Linux workstation, `flutter doctor` reports;

> ```
> [!] Connected device
>     ! No devices available
> ```

Attempting to run `flutter run` after killing `adb` results with:

> No supported devices connected.

## Other notes

* The root cause is that if `adb` isn't already running, `adb devices -l` can list the emulator as being offline:
> ```
> * daemon not running; starting now at tcp:5037
> * daemon started successfully
> List of devices attached
> emulator-5554          offline transport_id:1
> ```
The Flutter tool assumes that there's no raciness and that `adb devices -l` will list it in the `online` state instead.

* Explicitly running `adb start-server` first helps slightly; `adb kill-server && adb start-server && adb devices -l` prints:
> ```
> * daemon not running; starting now at tcp:5037
> * daemon started successfully
> List of devices attached
> emulator-5554          authorizing transport_id:1
> ```
Maybe that's good enough for the Flutter tool which explicitly checks for only the `unauthorized` and `offline` states.

* This seems sensitive to particular hosts; I can't reproduce this on my Linux laptop.  Chingjun also can reproduce this on his Linux workstation.

* I can reproduce this with `adb 30.0.1-6436771` but not with `adb 29.0.1-5644136`.  Reportedly `adb` server startup was "sped" up.

* This also seems mostly specific to emulators (which are probed differently than physical USB devices), although I don't think physical USB devices are necessarily immune from potential raciness.

* Internal bugs are b/161935440 and b/162899278.
Repository: pytorch
Issue: No pytorch_jni in StartLocal's zip
Labels: oncall: mobile

I am trying to run java-demo on Linux and downloaded pytorch lib from StartLocal page

https://download.pytorch.org/libtorch/cu102/libtorch-shared-with-deps-1.6.0.zip

Unfortunately, this archive file doesn't contain pytorch_jni

What to do?
Repository: godot
Issue: Bug when using custom camera2d on InputEventScreenTouch & InputEventMouseButton effects tilemap
Labels: topic:core,topic:input

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
<!-- Specify commit hash if using non-official build. -->
v3.2.2

**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
Win

**Issue description:**
<!-- What happened, and what was expected. -->
when try to get tile position using InputEventScreenTouch.position/InputEventMouseButton.position the return value is wrong.

This bug cased by cmaera2d when we use custom camera other than the default the mouse cord postion is wrong effected by the camera position.

**Steps to reproduce:**
Make new project try to use custom camera make it current and try to get the flowing:
get_global_mouse_position()
get_local_mouse_position()
and compare it with inside  _unhandled_input(event) function 
InputEventScreenTouch.postion
InputEventMouseButton.postion
```

func _process(delta):
	var gmp = get_global_mouse_position()
	var gmp_tile = world_to_map(gmp)
	$GMP.text = str("global_mouse_position: ", gmp,",   tile pos: ", gmp_tile);
	# local mouse
	var lmp = get_local_mouse_position()
	var lmp_tile = world_to_map(lmp)
	$LMP.text = str("local_mouse_position: ", lmp,",   tile pos: ", lmp_tile);

func _unhandled_input(event):
	if event is InputEventScreenTouch:
		if event.pressed:
			var te = event.position
			var te_tile = world_to_map(te)
			$TouchEvent.text = str("InputEventScreenTouch.position: ", te,",   tile pos: ", te_tile);
			
	if event is InputEventMouseButton:
		if event.pressed:
			var me = event.position
			var me_tile = world_to_map(me)
			$MouseEvent.text = str("InputEventMouseButton.position: ", me,",   tile pos: ", me_tile);

```

https://pasteboard.co/JrauWmz.png
when using custom camera
https://pasteboard.co/JravMpJ.png
the dfault camera
https://pasteboard.co/Jrawjrz.png


Here is test project
https://www.gulf-up.com/56g5tsmjici7

[BugTest.zip](https://github.com/godotengine/godot/files/5223668/BugTest.zip)
![bug-nodes](https://user-images.githubusercontent.com/18581054/93188746-6ad5d900-f752-11ea-9ae3-07c854e96a9f.PNG)
![bug1](https://user-images.githubusercontent.com/18581054/93188759-6f9a8d00-f752-11ea-8720-a659f4457282.PNG)
![bug-normal](https://user-images.githubusercontent.com/18581054/93188767-72957d80-f752-11ea-996d-e0da08f4ed40.PNG)
Repository: pytorch
Issue: Multi-process Dataloader and multi-parameter exceptions
Labels: module: dataloader,triaged,enhancement

## 🐛 Bug

The exception forwarding, used by utils.data.DataLoader for re-raising an exception from a worker process fails (TypeError) for exception types which require more than one parameter to initialize.

## To Reproduce

Steps to reproduce the behavior:

```
import torch as th

class MultiParamException(Exception):
    def __init__(self, a, b): super().__init__(f"Parameters were a={a} b={b}.")
        
class SingleParamException(Exception):
    def __init__(self, a): super().__init__(f"Parameter was a={a}.")
        
class SPEDataset(th.utils.data.Dataset):
    def __len__(self): return 10
    def __getitem__(self,key):
        raise SingleParamException(key)
        
class MPEDataset(th.utils.data.Dataset):
    def __len__(self): return 10
    def __getitem__(self,key):
        raise MultiParamException(key, "foo")
        
spe_dl = th.utils.data.DataLoader(SPEDataset(), batch_size=2,num_workers=2)
mpe_dl = th.utils.data.DataLoader(MPEDataset(), batch_size=2,num_workers=2)

#next(iter(spe_dl)) #OK. Gives the error "SingleParamException: Parameter was a=0."
next(iter(mpe_dl)) #Fail. Results in  "TypeError: __init__() missing 1 required positional argument: 'b'
```

```
TypeError                                 Traceback (most recent call last)
<ipython-input-3-e2f1fd79ffae> in <module>
----> 1 next(iter(mpe_dl))

/usr/local/lib/python3.8/dist-packages/torch/utils/data/dataloader.py in __next__(self)
    361 
    362     def __next__(self):
--> 363         data = self._next_data()
    364         self._num_yielded += 1
    365         if self._dataset_kind == _DatasetKind.Iterable and \

/usr/local/lib/python3.8/dist-packages/torch/utils/data/dataloader.py in _next_data(self)
    987             else:
    988                 del self._task_info[idx]
--> 989                 return self._process_data(data)
    990 
    991     def _try_put_index(self):

/usr/local/lib/python3.8/dist-packages/torch/utils/data/dataloader.py in _process_data(self, data)
   1012         self._try_put_index()
   1013         if isinstance(data, ExceptionWrapper):
-> 1014             data.reraise()
   1015         return data
   1016 

/usr/local/lib/python3.8/dist-packages/torch/_utils.py in reraise(self)
    395         #print("exc type was",self.exc_type)
    396         #raise RuntimeError(msg)
--> 397         raise self.exc_type(msg)

TypeError: __init__() missing 1 required positional argument: 'b'
```

## Expected behavior

The exception should be raised correctly. If that is not possible, a "RuntimeError" could be raised in place.


cc @SsnL @VitalyFedyunin
Repository: youtube-dl
Issue: Support Streamz
Labels: site-support-request

## Checklist
- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2020.09.14**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs
- Single video: https://www.streamz.be/streamz/afspelen/e9995abad-a3fe-4420-9053-86b25294a5f6
- Single video: https://www.streamz.be/streamz/afspelen/e6e0c2832-121b-4666-a8f4-64e17823a919
- Playlist: https://www.streamz.be/streamz/de-bende-van-jan-de-lichte~peb4ef252-871e-45a6-880e-5d096e1fe8d7
- Playlist: https://www.streamz.be/streamz/fair-trade~p06c62625-edf7-43db-858e-d70620d8e69c
Repository: rust
Issue: diagnostics: rust could suggest removing reference here
Labels: A-diagnostics,T-compiler,A-suggestion-diagnostics,E-needs-mcve,D-papercut

I was working on some clippy code and had something along the following:

```rust
/// lint for length-1 `str`s as argument for `insert_str`
fn lint_single_char_insert_string(cx: &LateContext<'_>, expr: &hir::Expr<'_>, args: &[hir::Expr<'_>]) {
    let _pos_arg = snippet_2(&cx, args[1].span, ".."); // here we need "cx" instead of "&cx" !
}

pub fn snippet_2<'a, T: LintContext>(cx: &T, span: Span, default: &'a str) -> Cow<'a, str> {
    todo!();
}
```

This did not compile:
````
error[E0277]: the trait bound `&LateContext<'_>: LintContext` is not satisfied
    --> clippy_lints/src/methods/mod.rs:3346:20
     |
3346 |     let _pos_arg = snippet_2(&cx, args[1].span, "..");
     |                    ^^^^^^^^^ the trait `LintContext` is not implemented for `&LateContext<'_>`
...
3349 | pub fn snippet_2<'a, T: LintContext>(cx: &T, span: Span, default: &'a str) -> Cow<'a, str> {
     |                         ----------- required by this bound in `snippet_2`
     |
     = help: the following implementations were found:
               <LateContext<'_> as LintContext>

````

The problem was that `snippet_2` needed `cx` instead of `&cx`. It would be great if rustc could suggest to remove the reference here.
I tried to write a small sample code from scratch but in all of these cases, rustc managed to correctly suggest to remove the `&`, so there must be some extra aspects here. :/
Repository: three.js
Issue: WebGLRenderer: Calling dispose() does not trigger dispose() on geometries, materials etc.
Labels: Needs Investigation

Each time `Pass.FullScreenQuad` is used in a new WebGLRenderer, a `dispose` listener is attached to `geometry`. But when WebGLRenderer is disposed, `geometry` is not disposed, therefore the reference to the `dispose` listener is retained.

https://github.com/mrdoob/three.js/blob/b0a1e8ca7863aa399c31692fa5b76c40feca2485/examples/jsm/postprocessing/Pass.js#L37-L40

The listener holds a reference to `info` and `bindingStates`, which further refers to many other objects.

https://github.com/mrdoob/three.js/blob/4944e56c06ed284abe11b7654348fb1ea3ac04d4/src/renderers/webgl/WebGLGeometries.js#L5

![image](https://user-images.githubusercontent.com/8373027/93076018-4548c100-f6b9-11ea-8e76-8c61a386075e.png)

![image](https://user-images.githubusercontent.com/8373027/93077190-0e73aa80-f6bb-11ea-861e-8924cc88000f.png)
Repository: godot
Issue: Camera2D anchor mode affects ParallaxBackground scroll offset
Labels: bug,topic:core

**Godot version:** 3.2.2

**OS/device including version:** 
MacBook Pro (Retina, 13-inch, Early 2015)
Intel Iris Graphics 6100 1536 MB

**Issue description:**

The behavior I expect is that if the camera view area is the same, the scroll offset should be the same. In other words, when the camera position is the same as where it's shown in the editor, the ParallaxBackground should look the same as in the editor.

Anchor mode: Center
![center-zero](https://user-images.githubusercontent.com/372476/93077258-221f1100-f6bb-11ea-9674-2928888108cf.png)

Anchor mode: TopLeft
![topleft-zero](https://user-images.githubusercontent.com/372476/93077268-24816b00-f6bb-11ea-8cf6-f67fe8d46918.png)

It seems that it's related to the origin of Camera2D. If I move the top left corner of the camera view area to the origin, the TopLeft anchor version works as expected:

Anchor mode: Center

![center-origin](https://user-images.githubusercontent.com/372476/93077477-6dd1ba80-f6bb-11ea-89c4-96f857c89b36.png)

Anchor mode: TopLeft

![topleft-origin](https://user-images.githubusercontent.com/372476/93077556-8e9a1000-f6bb-11ea-8196-779c024f3592.png)

I think inferring scroll offset from the origin is counter-intuitive. Anyway, there seems to be more things under the hood that's wrong: when the center of the camera has an initial offset, the initial scroll offset of both versions look unexpected:

Anchor mode: Center
![center-64](https://user-images.githubusercontent.com/372476/93078206-af169a00-f6bc-11ea-9e36-ca40578dcc70.png)

Anchor mode: TopLeft
![topleft-64](https://user-images.githubusercontent.com/372476/93078215-b2aa2100-f6bc-11ea-92e9-988f54f3822d.png)

---

There seems to be no description of the officially excpected behavior in the documentation. And most tutorials about ParallaxBackground use abstract patterns as the background so that the initial scroll offset does not matter that much.

**Steps to reproduce:**
Use the test project, change the camera anchor mode, and move the initial position of the camera around.

**Minimal reproduction project:** [ParallaxTest.zip](https://github.com/godotengine/godot/files/5217854/ParallaxTest.zip)