I have installed two Newts in two different server, melaka and banting. When I started the Newt in banting it pulled Resources which were configured for melaka. I didn't remember seeing this in previous version.
Pangolin version: beta.9
Newt version: beta.5
Sites
Resources
Newt melaka (Expected behavior)
INFO: 2025/01/31 01:01:57 Not adding target because not running
INFO: 2025/01/31 01:01:57 Not adding target because not running
INFO: 2025/01/31 01:01:57 Not adding target because not running
INFO: 2025/01/31 01:01:57 Started tcp proxy from 100.89.128.4:61907 to pihole:80
INFO: 2025/01/31 01:01:57 Started tcp proxy from 100.89.128.4:57631 to wgeasydns:xx
INFO: 2025/01/31 01:01:57 Started tcp proxy from 100.89.128.4:47178 to wgeasyfull:xx
Newt banting (Wrong behavior?)
INFO: 2025/01/31 00:40:16 Starting ping check
INFO: 2025/01/31 00:40:16 Not adding target because not running
INFO: 2025/01/31 00:40:16 Not adding target because not running
INFO: 2025/01/31 00:40:16 Not adding target because not running
INFO: 2025/01/31 00:40:16 Started tcp proxy from 100.89.128.8:61907 to pihole:80
INFO: 2025/01/31 00:40:16 Started tcp proxy from 100.89.128.8:57631 to wgeasydns:xx
INFO: 2025/01/31 00:40:16 Started tcp proxy from 100.89.128.8:47178 to wgeasyfull:xx
Originally created by @nixielectra on GitHub (Jan 31, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/117
Hi,
I have installed two Newts in two different server, `melaka` and `banting`. When I started the Newt in `banting` it pulled Resources which were configured for `melaka`. I didn't remember seeing this in previous version.
Pangolin version: `beta.9`
Newt version: `beta.5`
Sites
Resources
Newt `melaka` (Expected behavior)
```
INFO: 2025/01/31 01:01:57 Not adding target because not running
INFO: 2025/01/31 01:01:57 Not adding target because not running
INFO: 2025/01/31 01:01:57 Not adding target because not running
INFO: 2025/01/31 01:01:57 Started tcp proxy from 100.89.128.4:61907 to pihole:80
INFO: 2025/01/31 01:01:57 Started tcp proxy from 100.89.128.4:57631 to wgeasydns:xx
INFO: 2025/01/31 01:01:57 Started tcp proxy from 100.89.128.4:47178 to wgeasyfull:xx
```
Newt `banting` (Wrong behavior?)
```
INFO: 2025/01/31 00:40:16 Starting ping check
INFO: 2025/01/31 00:40:16 Not adding target because not running
INFO: 2025/01/31 00:40:16 Not adding target because not running
INFO: 2025/01/31 00:40:16 Not adding target because not running
INFO: 2025/01/31 00:40:16 Started tcp proxy from 100.89.128.8:61907 to pihole:80
INFO: 2025/01/31 00:40:16 Started tcp proxy from 100.89.128.8:57631 to wgeasydns:xx
INFO: 2025/01/31 00:40:16 Started tcp proxy from 100.89.128.8:47178 to wgeasyfull:xx
```
@oschwartz10612 commented on GitHub (Jan 31, 2025):
Okay this was a missing where clause and will be fixed in beta.10 which we will release tonight with a couple of hot fixes. Sit tight!
<!-- gh-comment-id:2626123698 -->
@oschwartz10612 commented on GitHub (Jan 31, 2025):
Okay this was a missing where clause and will be fixed in beta.10 which we will release tonight with a couple of hot fixes. Sit tight!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @nixielectra on GitHub (Jan 31, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/117
Hi,
I have installed two Newts in two different server,
melakaandbanting. When I started the Newt inbantingit pulled Resources which were configured formelaka. I didn't remember seeing this in previous version.Pangolin version:
beta.9Newt version:
beta.5Sites
Resources
Newt
melaka(Expected behavior)Newt
banting(Wrong behavior?)@oschwartz10612 commented on GitHub (Jan 31, 2025):
Okay this was a missing where clause and will be fixed in beta.10 which we will release tonight with a couple of hot fixes. Sit tight!