Enable trilinear filtering on OpenGL

This PR aims to improve downscaling quality. See https://github.com/Genymobile/scrcpy/issues/40#issuecomment-591917787 for more details.

add an option --render-driver to force a renderer
enable trilinear filtering if the renderer is OpenGL and if it supports mipmapping
add an option --no-mipmaps to force-disable trilinear filtering

scrcpy --window-height=500 --window-title=BEFORE --no-mipmaps
scrcpy --window-height=500 --window-title=AFTER

cc @cjxgm
I'm hesitant to set opengl as the default render driver on Windows and macOS. I'm afraid that it could cause problems. What do you think?
Please test with --render-driver=opengl on these platforms, and report any problems :)
Note that this improves quality only for client downscaling (the device sends the video at full definition, and the client resizes the window).
The quality is still bad if the content is resized before encoding (scrcpy -m 500 for example).

@rom1v . I tried platying pixel art games, however the trilinear filter affects the clarity of the pixel art games. I tried this branch out. Tested on Windows 10 20H1 (insiders)

Thank you for your test. Could you post screenshots showing the difference, please?

Sure, I will post the screenshots in some time.

@rom1v, after the update, the scrcpy on my desktop has been a lot slower. I am able to act faster on the older scrcpy and not on the mipmaps branch
Before

After

Sorry for the bad screenshots, but is there any way to fix the lag on scrcpy now.

Sorry for the bad screenshots

Is your screenshot zoomed from what see on your computer, or is it a 1:1 screenshot from your computer screen?

I am able to act faster on the older scrcpy and not on the mipmaps branch

Oh, interesting. Which platform?
Does adding --no-mipmaps solve your issue?

The change is hardly noticeable, but I would like to have triliinear filter as the optional args

It is optional (but enabled by default for now), with --no-mipmaps.
Since it improves text quality, I would like to keep it enabled by default, but it depends on whether it has too many drawbacks.

Yes, both are a 1:1 screenshot taken on the PC.

Does adding --no-mipmaps solve your issue?

Nope,

Nope, I did a few restarts on my phone, to ensure nothing's hanging around.

And on dev, it works fine?

Nope, I did a few restarts on my phone, to ensure nothing's hanging around.

And on dev, it works fine?

I meant stable. (master). I am not on dev. scrcpy 1.12.1 is super fast for me. Just tested after the reboot. Until the reboot, everything was slow. After reboot, everything's fast again. I just tested the mipmap again, and the whole thing becomes slow again

Could you compare dev (this PR is based on dev) and master, please?
If it's slow on dev but fast on master, we need to find the culprit commit (with git bisect or something).

Ok, will check in 5 min. (My builds are really slow)

@rom1v, Ok, I did the test. Its slow only on the mipmap branch. The dev branch is similar to the master branch. Maybe my device doesn't support that much rendering, but idk, you might know what happened better

OK, thank you. So could you git bisect to find which commit introduced the slowdown between master and dev, please?

I am not familiar with git bisect. I might take some to learn how it works. My bad :face_with_head_bandage:

git checkout dev
git bisect start
git bisect bad  # slowness problem on dev branch
git checkout master
git bisect good  # works correctly on master
# loop:
# it checkouts some commit between master and dev
# build and run
ninja -Cx && ./run x
# if it's slow: git bisect bad
# if it works correctly: git bisect good
# if it knows which commit introduced the problem, it will tell you
# otherwise, goto loop

woah. cool. thanks for this cool snippet. I will let you know asap.

Ok, my findings seems contradictory.
The lag starts somewhere near ee2894779aa85a7a78a3e57aa154bfeb1025e55c and 927d655ff66fa439ccd27e054ae6d54a651640cc.
But the git diff gives normal variables, and the change you have made in the to commits doesn't make a much great difference in the frame rate.

Until 1c6207f8ce88e89a9d80157881d8012fe14d4463, it works quite smooth

So 1c6207f8ce88e89a9d80157881d8012fe14d4463 works fine, but from ee2894779aa85a7a78a3e57aa154bfeb1025e55c it lags? Does fd63e7eb5a60af8e5e52ecfddb9d0f3b7f3740af make a difference compared to ee2894779aa85a7a78a3e57aa154bfeb1025e55c?
Indeed, it is weird :confused:

So 1c6207f works fine, but from ee28947 it lags? Does fd63e7e make a difference compared to ee28947?

@srevinsaju Could you please test this if you have time?

Merged in dev.

@rom1v I apologize. I had a sudden inflow of online educational classes which messed up my open source work temporarily. I am extremely sorry that I couldn't do anything yesterday.
Should I test https://github.com/Genymobile/scrcpy/pull/1284#issuecomment-613468685 as you have asked? I am now free.
I am sorry again.

@srevinsaju Don't be sorry, everyone has other things to do :wink:
I would like you confirm since which commit between master and dev you encounter slowness problems.

Ok, I will let you know it asap.

It might be better if the mipmap is only enabled when the scaling factor is below a threshold (e.g. when computer-window-width < 0.75 * phone-width), this should fix the pixel art being blurry issue.

@rom1v I tested it on three devices. On three devices, I did not get the same results. I did a repeated iteration of git bisect over commits from master and dev. I found that the lag still happens as mentioned here https://github.com/Genymobile/scrcpy/pull/1284#issuecomment-612670780 on Samsung Galaxy Note 2, but it doesn't happen on Note 5 / Samsung A 70. Maybe the lag might be due  hardware issues.

Sid you find a specific commit where it strt to happen?
Also, is it a lag on touch events, mouse events, keyboard events...?

Its a lag on FRAME_RATE. The touch events works fine.

Totally unrelated to the PR; I am building an AppImage for scrcpy, after some trial and error, I have tried to find the libraries which are required by scrcpy.
Out of all of the libraries found by ldd, I have selected these:
This is my shortlist
libSDL2-2.0.so.0     libcrystalhd.so.3  libpanelw.so.5      libva-drm.so.2
libXau.so.6          libffi.so.5        libreadline.so.5    libva-x11.so.2
libXdmcp.so.6        libgdbm.so.2       libshine.so.3       libva.so.2
libavcodec.so.57     libgme.so.0        libsnappy.so.1      libvdpau.so.1
libavformat.so.57    libgsm.so.1        libsndio.so.6.1     libvpx.so.5
libavutil.so.55      liblzma.so.0       libsqlite3.so.0     libwebp.so.6
libbluray.so.2       libncursesw.so.5   libssh-gcrypt.so.4  libx264.so.152
libbz2.so.1          libnsl.so.1        libswresample.so.2  libx265.so.146
libchromaprint.so.1  libopenjp2.so.7    libtcl8.4.so        libxvidcore.so.4
libcrypt.so.2        libopenmpt.so.0    libtk8.4.so         libzvbi.so.0

These were the list given by ldd
libasound.so.2       libfontconfig.so.1      libk5crypto.so.3        libpixman-1.so.0        libtheoradec.so.1       libx265.so.146
libasyncns.so.0      libfreetype.so.6        libkeyutils.so.1        libpng16.so.16          libtheoraenc.so.1       libXau.so.6
libavcodec.so.57     libgcc_s.so.1           libkrb5.so.3            libpthread.so.0         libtwolame.so.0         libxcb-render.so.0
libavformat.so.57    libgcrypt.so.20         libkrb5support.so.0     libpulsecommon-11.1.so  libunistring.so.2       libxcb-shm.so.0
libavutil.so.55      libgdk_pixbuf-2.0.so.0  liblz4.so.1             libpulse.so.0           libuuid.so.1            libxcb.so.1
libblkid.so.1        libgio-2.0.so.0         liblzma.so.5            libresolv.so.2          libva-drm.so.2          libXcursor.so.1
libbluray.so.2       libglib-2.0.so.0        libmount.so.1           librsvg-2.so.2          libva.so.2              libXdmcp.so.6
libbsd.so.0          libgme.so.0             libmp3lame.so.0         librt.so.1              libva-x11.so.2          libXext.so.6
libbz2.so.1.0        libgmodule-2.0.so.0     libmpg123.so.0          libSDL2-2.0.so.0        libvdpau.so.1           libXfixes.so.3
libcairo.so.2        libgmp.so.10            libm.so.6               libselinux.so.1         libvorbisenc.so.2       libXinerama.so.1
libchromaprint.so.1  libgnutls.so.30         libnettle.so.6          libshine.so.3           libvorbisfile.so.3      libXi.so.6
libcom_err.so.2      libgobject-2.0.so.0     libnsl.so.1             libsnappy.so.1          libvorbis.so.0          libxkbcommon.so.0
libcroco-0.6.so.3    libgomp.so.1            libnuma.so.1            libsndfile.so.1         libvpx.so.5             libxml2.so.2
libcrystalhd.so.3    libgpg-error.so.0       libogg.so.0             libsndio.so.6.1         libwavpack.so.1         libXrandr.so.2
libc.so.6            libgraphite2.so.3       libopenjp2.so.7         libsoxr.so.0            libwayland-client.so.0  libXrender.so.1
libdatrie.so.1       libgsm.so.1             libopenmpt.so.0         libspeex.so.1           libwayland-cursor.so.0  libXss.so.1
libdbus-1.so.3       libgssapi_krb5.so.2     libopus.so.0            libssh-gcrypt.so.4      libwayland-egl.so.1     libxvidcore.so.4
libdl.so.2           libharfbuzz.so.0        libp11-kit.so.0         libstdc++.so.6          libwebpmux.so.3         libXxf86vm.so.1
libdrm.so.2          libhogweed.so.4         libpango-1.0.so.0       libswresample.so.2      libwebp.so.6            libz.so.1
libexpat.so.1        libicudata.so.60        libpangocairo-1.0.so.0  libsystemd.so.0         libwrap.so.0            libzvbi.so.0
libffi.so.6          libicuuc.so.60          libpangoft2-1.0.so.0    libtasn1.so.6           libX11.so.6
libFLAC.so.8         libidn2.so.0            libpcre.so.3            libthai.so.0            libx264.so.152

Have I missed out any important libs from my shortlist? I have tested my shortlist on Ubuntu 20.04 and Arch Linux.

Its a lag on FRAME_RATE.

Oh! If you record with scrcpy -r file mkv, and play the fike, does it still lag?
Did you find a specific commit where it lags, and works fine on its parent commit?

Scrcpy only depends on ffmpeg and sdl, the others are transitive depencies, depending on your ffmpeg build configuration. Ideally, you should build your own ffmpeg with only the minimum required for scrcpy (H.264 decoding, and probably other stuff from libavutil...).


Some United States Region data is Nil

The United States Region breakdown data is null for Recovered, and Deaths columns.

Currently there are no reliable sources for recovered numbers, but I'll add number of deaths soon.

Data for deaths have been added.


"Use let instead of an instance variable" in before(:all)

Currently when using an instance variable in a before(:all) or an after(:all) call you get the usual:
C: Use let instead of an instance variable

However if you change it over to a let instead of an ivar, RSpec will throw the following warning:
`let` and `subject` declarations are not intended to be called
in an `after(:context)` hook, as they exist to define state that
is reset between each example, while `after(:context)` exists to
cleanup state that is shared across examples in an example group.

I'm inclined to agree with RSpec in this case but I'm looking for feedback, thanks!

I don't think there's much that rspec-rubocop can do in this situation. It reports the problem, but it assumes a basic understanding of RSpec to fix it.

@conzett let and subject come at a higher level, outside your before block:
describe 'something' do
  let(:a_thing) { Thing.new }

  before do
    # any setup
  end

  it 'does stuff' do
    expect(a_thing.do_stuff).to eq 'stuff'
  end
end

More in the docs here: https://www.relishapp.com/rspec/rspec-core/v/3-1/docs/helper-methods/let-and-let

@mockdeep I'm aware of that, perhaps my initial example was unclear. This demonstrate the issue:
describe 'something' do
  let(:a_thing) { Thing.new }

  before(:all) do
    # This should be shared for all specs
    # Rubocop rspec is not happy
    @clean_me_up_later = { some: :thing }
  end
end

The RSpec warning above does say:
`after(:context)` exists to cleanup state that is shared
across examples in an example group

I think discouraging ivars in general makes sense, especially inside describes, but can there be an exception for things like before(:all)? The docs themselves show this.

Hmm, can you give me more details on what you're trying to achieve with this? I suspect there's a way to do it either without the ivar or without the before(:all). The before(:all) approach introduces shared state across your specs, which can cause them to be inconsistent if they interact with the ivar set up there. One option is to use a before(:each) instead, or you might just define your thing as a constant at the top of your spec:
describe 'something' do
  let(:a_thing) { Thing.new }
  MY_SHARED_CONST = 'foo'

  it 'does stuff' do
    expect(a_thing.do_stuff(MY_SHARED_CONST)).to eq 'stuff'
  end
end

Worst case, though, you can always disable the rule selectively if you like:
@my_shared_var.do_stuff # rubocop:disable RSpec/InstanceVariable

Or entirely in your .rubocop.yml file:
RSpec/InstanceVariable:
  Enabled: false

How about an extra configuration option IgnoreBeforeAllBlocks?

Not sure about a special case config option here. Since @conzett didn't followup with @mockdeep I'll close for now. In my opinion this is exactly what rubocop:disable is for.


Compile-time detection of MADV_FREE availability is unfortunate on Linux

Currently the detection of whether the system supports MADV_FREE is done at compile time: https://github.com/gperftools/gperftools/blob/gperftools-2.5/src/system-alloc.cc#L65-L70. This means that if the compiling system supports it, MADV_FREE will be used instead of MADV_DONTNEED. Executables compiled on such a system will not be able to return memory to the OS when run on a system that doesn't support MADV_FREE.
This is a realistic situation now that Linux has added support for MADV_FREE in 4.5 (http://kernelnewbies.org/LinuxChanges section 1.6). Long term, it would be ideal if tcmalloc could use runtime detection of MADV_FREE availability with a fallback to MADV_DONTNEED. As a short-term solution, it is probably worth always using MADV_DONTNEED on linux, possibly with a compile-time option for users who know they will only run on systems that support MADV_FREE.

Great point. I've missed this thing that we're detecting it at compile time.
In fact I don't want us to use MADV_FREE without further testing. IMHO
lack of clear signal "we're using this pages again" in this entire approach
is suboptimal (the risk is that active page ends up on inactive list
without good reason; compromising overall kswapd efficiency). And I'd
prefer API closer to what windows or andoid have with explicit "please feel
free to take this pages" and "hey I want them back".
So in addition to runtime detection I'd like us to have runtime on/off
switch for that.
If you can offer a quick patch that adds runtime detection (compile time
might still be needed so that constant for MADV_FREE is known) and
ability to enable/disable at runtime I'd be happy.
Thanks.
On Wed, Mar 16, 2016 at 1:49 PM, Mathias Stearn<EMAIL_ADDRESS>wrote:

Currently the detection of whether the system supports MADV_FREE is done
at compile time:
https://github.com/gperftools/gperftools/blob/gperftools-2.5/src/system-alloc.cc#L65-L70.
This means that if the compiling system supports it, MADV_FREE will be used
instead of MADV_DONTNEED. Executables compiled on such a system will not be
able to return memory to the OS when run on a system that doesn't support
MADV_FREE.
This is a realistic situation now that Linux has added support for
MADV_FREE in 4.5 (http://kernelnewbies.org/LinuxChanges section 1.6).
Long term, it would be ideal if tcmalloc could use runtime detection of
MADV_FREE availability with a fallback to MADV_DONTNEED. As a short-term
solution, it is probably worth always using MADV_DONTNEED on linux,
possibly with a compile-time option for users who know they will only run
on systems that support MADV_FREE.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/gperftools/gperftools/issues/780

Sorry, I don't have time for that right now, nor am I quite clear on how you'd like that to work. For now I submitted #781 which implements a short-term solution of just pretending that linux doesn't have MADV_FREE.

Applied. Thanks.
I've also added subsequent commit that adds define to enable usage of MADV_FREE. I.e. so that testing it is easier.

For future travellers that may be digging into a related Issue, Linux MADV_FREE had a race condition where Direct I/O reads may incorrectly return a zeroed page due a race between MADV_FREE and Direct I/O that happens under memory pressure.
Noticed and solved due to being hit as checksum failures in Ceph:
https://tracker.ceph.com/issues/22464
Fixed in Linux v5.18+ here with a very comprehensive and detailed commit message:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6c8e2a256915a223f6289f651d6b926cd7135c9e (also with stable backports to many older versions)
Notably was being hit on Ubuntu 18.04 as it shipped gperftools v2.5 without this change to disable MADV_FREE but a new enough kernel to hit the issue.

Closing this ticket as I think we should keep doing plain MADV_DONTNEED.


Laptop issue that fall asleep at low percantage but its still just turn off(

I noticed that the laptop issues a warning that it will fall asleep, but it does not fall asleep and turns off at a low capacity
I think I found a solution, but I don't understand the code, maybe you can implement these fixes
https://applelife.ru/threads/hibernate-pri-razrjade-batarei.2874421/
If you cannot translate something on this forum, I can help because this is my native language

This issue was resolved by replacing first bat

I think this is solution
testing now with hbfx-ahbm=39 (is sum of values below)
hbfx-ahbm=abhm_value controls auto-hibernation feature, where abhm_value is an arithmetic sum of respective values below:
EnableAutoHibernation = 1: If this flag is set, system will hibernate instead of regular sleep (flags below can be used to limit this behavior)
WhenLidIsClosed = 2: Auto hibernation can happen when lid is closed (if bit is not set - no matter which status lid has)
WhenExternalPowerIsDisconnected = 4: Auto hibernation can happen when external power is disconnected (if bit is not set - no matter whether it is connected)
WhenBatteryIsNotCharging = 8: Auto hibernation can happen when battery is not charging (if bit is not set - no matter whether it is charging)
WhenBatteryIsAtWarnLevel = 16: Auto hibernation can happen when battery is at warning level (osx and battery kext are responsible for this level)
WhenBatteryAtCriticalLevel = 32: Auto hibernation can happen when battery is at critical level (osx and battery kext are responsible for this level)
DisableStimulusDarkWakeActivityTickle = 128: Disable power event kStimulusDarkWakeActivityTickle in kernel, so this event cannot trigger a switching from dark wake to full wake
Next 4 bits are used to specify minimal capacity percent remaining value when hibernation will be forced. Can be used together with WhenBatteryIsAtWarnLevel or WhenBatteryAtCriticalLevel, when IOPMPowerSource cannot detect warning or critical battery level
RemainCapacityBit1 = 256
RemainCapacityBit2 = 512
RemainCapacityBit3 = 1024
RemainCapacityBit4 = 2048


rename dev-resources to data

the name "dev resources" is mis-leading, this is data that is required to make the app run.

merged folder name change with master.


convert final results into GIS-ready netcdf files

Break them up by ENSO phase and month. Such that the file structure would look like:

@matt-csiro - another day, another NCI downtime event?  Work killed and no longer access from my location.

What are my chances of getting any reply from help on a Saturday?

writing 288 files bogging down

moved work off gdata6
pre-computed before applying zlib compression
using compression level 1

end state: about 2.5 minutes per file - thus appears it will take order 12 hours to write all these netcdf files and size will be order 2.5GB per file.

@matt-csiro
GIS-ready files are written, but over on xv83 (do you have access to that account?) - currently trying to squeeze them over onto gdata/es60.
Have not yet had the chance to do any sanity checks.

[ ] add back in a month coordinate for each file


Host is NOT alive: 0-0 when Istio is enabled

We are changing up our Deployment of Clickhouse using the Operator. We also wrote some tests, that pull up a cluster and run queries on it. Everything works great, however, when I activate Istio injection, I get the following in the Operator. When deactivating Istio, everything works like a charm again...
E1113 14:29:59.532223       1 cluster.go:95] QueryAny():FAILED to run query on all hosts [chi-clickhouse-default-0-0-0.clickhouse-test.svc.cluster.local]
W1113 14:29:59.532280       1 worker-app-version.go:33] getHostClickHouseVersion():Failed to get ClickHouse version on host: 0-0
W1113 14:29:59.532291       1 worker-app-version.go:53] func1():Host is NOT alive: 0-0
I1113 14:29:59.532306       1 poller.go:111] Poll():clickhouse-test/0-0:WAIT: clickhouse-test/0-0

and
2024.11.13 14:32:14.821706 [ 75 ] {} <Debug> HTTP-Session: 78fed55d-8821-4db4-84a7-88f26440bdaa Authenticating user 'clickhouse_operator' from [::ffff:<IP_ADDRESS>]:41895
2024.11.13 14:32:14.822093 [ 75 ] {} <Error> Access(user directories): from: ::ffff:<IP_ADDRESS>, user: clickhouse_operator: Authentication failed: Code: 193. DB::Exception: Invalid credentials. (WRONG_PASSWORD), Stack trace (when copying this message, always include the lines below):

0. DB::Exception::Exception(DB::Exception::MessageMasked&&, int, bool) @ 0x000000000bac0324
1. DB::Exception::Exception(PreformattedMessage&&, int) @ 0x00000000076bf89c
2. DB::Exception::Exception<>(int, FormatStringHelperImpl<>) @ 0x00000000076cbe34
3. DB::IAccessStorage::throwInvalidCredentials() @ 0x000000000e82b994
4. DB::IAccessStorage::authenticateImpl(DB::Credentials const&, Poco::Net::IPAddress const&, DB::ExternalAuthenticators const&, bool, bool, bool) const @ 0x000000000e82b694
5. DB::MultipleAccessStorage::authenticateImpl(DB::Credentials const&, Poco::Net::IPAddress const&, DB::ExternalAuthenticators const&, bool, bool, bool) const @ 0x000000000e85e19c
6. DB::IAccessStorage::authenticate(DB::Credentials const&, Poco::Net::IPAddress const&, DB::ExternalAuthenticators const&, bool, bool) const @ 0x000000000e82ae98
7. DB::AccessControl::authenticate(DB::Credentials const&, Poco::Net::IPAddress const&, String const&) const @ 0x000000000e7976c4
8. DB::Session::authenticate(DB::Credentials const&, Poco::Net::SocketAddress const&) @ 0x000000000f7f3eac
9. DB::authenticateUserByHTTP(DB::HTTPServerRequest const&, DB::HTMLForm const&, DB::HTTPServerResponse&, DB::Session&, std::unique_ptr<DB::Credentials, std::default_delete<DB::Credentials>>&, std::shared_ptr<DB::Context const>, std::shared_ptr<Poco::Logger>) @ 0x00000000109a8264
10. DB::HTTPHandler::processQuery(DB::HTTPServerRequest&, DB::HTMLForm&, DB::HTTPServerResponse&, DB::HTTPHandler::Output&, std::optional<DB::CurrentThread::QueryScope>&, StrongTypedef<unsigned long, ProfileEvents::EventTag> const&) @ 0x0000000010911f14
11. DB::HTTPHandler::handleRequest(DB::HTTPServerRequest&, DB::HTTPServerResponse&, StrongTypedef<unsigned long, ProfileEvents::EventTag> const&) @ 0x0000000010918680
12. DB::HTTPServerConnection::run() @ 0x000000001099fe20
13. Poco::Net::TCPServerConnection::start() @ 0x00000000131ec578
14. Poco::Net::TCPServerDispatcher::run() @ 0x00000000131eca54
15. Poco::PooledThread::run() @ 0x00000000131b76d4
16. Poco::ThreadImpl::runnableEntry(void*) @ 0x00000000131b5b10
17. ? @ 0x000000000007d5c8
18. ? @ 0x00000000000e5edc
 (version <IP_ADDRESS>12 (official build))
2024.11.13 14:32:14.822307 [ 75 ] {} <Debug> HTTP-Session: 78fed55d-8821-4db4-84a7-88f26440bdaa Authentication failed with error: clickhouse_operator: Authentication failed: password is incorrect, or there is no user with such name.

in a Clickhouse Pod.

Attached our CHI
apiVersion: clickhouse.altinity.com/v1
kind: ClickHouseInstallation
metadata:
  annotations:
    meta.helm.sh/release-name: clickhouse
    meta.helm.sh/release-namespace: clickhouse-test
  creationTimestamp: "2024-11-13T14:27:13Z"
  finalizers:
  - finalizer.clickhouseinstallation.altinity.com
  generation: 1
  labels:
    app.kubernetes.io/managed-by: Helm
  name: clickhouse
  namespace: clickhouse-test
  resourceVersion: "22025"
  uid: d3dba6e0-7b0d-4def-8050-a9ea826acc57
spec:
  configuration:
    clusters:
    - layout:
        replicasCount: 2
        shardsCount: 1
      name: default-0
      secret:
        auto: "true"
      templates:
        podTemplate: clickhouse-default-pod-template
    files:
      users.d/roles.xml: |
        <clickhouse>
            <roles>
                <role_admin>
                    <grants>
                        <query>GRANT SELECT, INSERT, UPDATE, DELETE ON *.*;</query>
                    </grants>
                </role_admin>
                <role_test_user>
                    <grants>
                        <query>GRANT All ON redacted.*;</query>
                        <query>GRANT SELECT ON system.users;</query>
                    </grants>
                </role_test_user>
            </roles>
        </clickhouse>
    profiles:
      clickhouse_operator/http_connection_timeout: 10
      clickhouse_operator/log_queries: 0
      clickhouse_operator/max_concurrent_queries_for_all_users: 0
      clickhouse_operator/os_thread_priority: 0
      clickhouse_operator/skip_unavailable_shards: 1
      default/connect_timeout_with_failover_ms: 1000
      default/distributed_aggregation_memory_efficient: 1
      default/do_not_merge_across_partitions_select_final: 1
      default/load_balancing: nearest_hostname
      default/log_queries: 1
      default/os_thread_priority: 2
      default/parallel_view_processing: 1
      default/prefer_localhost_replica: 0
      default_resources/max_memory_usage:<PHONE_NUMBER>
      default_resources/max_threads: 4
      default_resources/profile: default
      reader/profile: default_resources
      reader/readonly: 1
      writer/profile: default_resources
    settings:
      logger/console: 1
      logger/formatting: json
      logger/level: trace
      prometheus/asynchronous_metrics: true
      prometheus/endpoint: /metrics
      prometheus/events: true
      prometheus/metrics: true
      prometheus/port: 8888
    users:
      clickhouse_operator/networks/ip:
      - ::/0
      - <IP_ADDRESS>/0
      - <IP_ADDRESS>/8
      clickhouse_operator/password:
        valueFrom:
          secretKeyRef:
            key: CLICKHOUSE-CREDS-CLICKHOUSE-OPERATOR-PASSWORD
            name: clickhouse-credentials
      clickhouse_operator/profile: clickhouse_operator
      default/password:
        valueFrom:
          secretKeyRef:
            key: CLICKHOUSE-CREDS-DEFAULT-PASSWORD
            name: clickhouse-credentials
      default/profile: default
      team_redacted/grants/query:
      - GRANT role_admin
      team_redacted/networks/ip:
      - ::/0
      - <IP_ADDRESS>/0
      - <IP_ADDRESS>/8
      team_redacted/password:
        valueFrom:
          secretKeyRef:
            key: CLICKHOUSE-CREDS-TEAM-redacted-PASSWORD
            name: clickhouse-credentials
      team_redacted/profile: writer
      test_user/grants/query:
      - GRANT role_test_user
      test_user/networks/ip:
      - ::/0
      - <IP_ADDRESS>/0
      - <IP_ADDRESS>/8
      test_user/password:
        valueFrom:
          secretKeyRef:
            key: CLICKHOUSE-CREDS-TEST-USER-PASSWORD
            name: clickhouse-credentials
      test_user/profile: writer
    zookeeper:
      nodes:
      - host: keeper-clickhouse-keeper.clickhouse-test.svc.cluster.local
        port: 2181
  defaults:
    templates:
      serviceTemplate: chi-service-template
  templates:
    podTemplates:
    - metadata:
        labels:
          app: clickhouse
          version: 24.10.1-alpine
      name: clickhouse-default-pod-template
      spec:
        containers:
        - image: clickhouse/clickhouse-server:24.10.1-alpine
          name: clickhouse
          resources:
            limits:
              memory: 4Gi
            requests:
              cpu: 300m
              memory: 300Mi
          volumeMounts:
          - mountPath: /var/lib/clickhouse
            name: data-storage-vc-template
          - mountPath: /var/log/clickhouse-server
            name: log-storage-vc-template
        - args:
          - server
          env:
          - name: CLICKHOUSE_PASSWORD
            valueFrom:
              secretKeyRef:
                key: CLICKHOUSE-CREDS-CLICKHOUSE-OPERATOR-PASSWORD
                name: clickhouse-credentials
          - name: LOG_LEVEL
            value: debug
          - name: ALLOW_EMPTY_BACKUPS
            value: "true"
          - name: API_LISTEN
            value: <IP_ADDRESS>:7171
          - name: API_CREATE_INTEGRATION_TABLES
            value: "true"
          - name: BACKUPS_TO_KEEP_REMOTE
            value: "3"
          - name: REMOTE_STORAGE
            value: s3
          - name: S3_ACL
            value: private
          - name: S3_ENDPOINT
            value: http://s3-backup-minio.minio.svc.cluster.local:9000
          - name: S3_BUCKET
            value: clickhouse
          - name: S3_PATH
            value: backup
          - name: S3_ACCESS_KEY
            value: backup-access-key
          - name: S3_SECRET_KEY
            value: backup-secret-key
          - name: S3_FORCE_PATH_STYLE
            value: "true"
          - name: S3_DISABLE_SSL
            value: "true"
          - name: S3_DEBUG
            value: "true"
          image: altinity/clickhouse-backup:2.6.3
          imagePullPolicy: Always
          name: clickhouse-backup
          ports:
          - containerPort: 7171
            name: http-backup
    serviceTemplates:
    - generateName: service-clickhouse
      name: chi-service-template
      spec:
        clusterIP: None
        ports:
        - name: http-client
          port: 8123
        - name: tcp-client
          port: 9000
        - name: tcp-interserver
          port: 9009
        - name: http-backup
          port: 7171
        type: ClusterIP
    volumeClaimTemplates:
    - name: data-storage-vc-template
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 5Gi
        storageClassName: standard
    - name: log-storage-vc-template
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 2Gi
        storageClassName: standard
status:
  action: 'OK Create Service: clickhouse-test/chi-clickhouse-default-0-0-0'
  actions:
  - '2024-11-13T14:27:20.467872879Z reconcile started, task id: 63f83cc8-80ec-443e-8c07-88044da24e74'
  chop-commit: 2a829e9
  chop-date: 2024-10-15T07:15:13
  chop-ip: <IP_ADDRESS>
  chop-version: 0.24.0
  clusters: 1
  endpoint: service-clickhouse.clickhouse-test.svc.cluster.local
  error: 'Update Service: clickhouse-test/chi-clickhouse-default-0-0-0 failed with
    error: just recreate the service in case of service type change ''''=>''ClusterIP'''
  errors:
  - '2024-11-13T14:27:58.535384675Z Update Service: clickhouse-test/chi-clickhouse-default-0-0-0
    failed with error: just recreate the service in case of service type change ''''=>''ClusterIP'''
  fqdns:
  - chi-clickhouse-default-0-0-0.clickhouse-test.svc.cluster.local
  - chi-clickhouse-default-0-0-1.clickhouse-test.svc.cluster.local
  hosts: 2
  hostsUpdated: 1
  normalized:
    apiVersion: clickhouse.altinity.com/v1
    kind: ClickHouseInstallation
    metadata:
      annotations:
        meta.helm.sh/release-name: clickhouse
        meta.helm.sh/release-namespace: clickhouse-test
      creationTimestamp: "2024-11-13T14:27:13Z"
      finalizers:
      - finalizer.clickhouseinstallation.altinity.com
      generation: 1
      labels:
        app.kubernetes.io/managed-by: Helm
      name: clickhouse
      namespace: clickhouse-test
      resourceVersion: "21784"
      uid: d3dba6e0-7b0d-4def-8050-a9ea826acc57
    spec:
      configuration:
        clusters:
        - layout:
            replicas:
            - name: "0"
              shards:
              - httpPort: 8123
                interserverHTTPPort: 9009
                name: 0-0
                tcpPort: 9000
                templates:
                  podTemplate: clickhouse-default-pod-template
                  serviceTemplate: chi-service-template
              shardsCount: 1
              templates:
                podTemplate: clickhouse-default-pod-template
                serviceTemplate: chi-service-template
            - name: "1"
              shards:
              - httpPort: 8123
                interserverHTTPPort: 9009
                name: 0-1
                tcpPort: 9000
                templates:
                  podTemplate: clickhouse-default-pod-template
                  serviceTemplate: chi-service-template
              shardsCount: 1
              templates:
                podTemplate: clickhouse-default-pod-template
                serviceTemplate: chi-service-template
            replicasCount: 2
            shards:
            - internalReplication: "True"
              name: "0"
              replicas:
              - httpPort: 8123
                interserverHTTPPort: 9009
                name: 0-0
                tcpPort: 9000
                templates:
                  podTemplate: clickhouse-default-pod-template
                  serviceTemplate: chi-service-template
              - httpPort: 8123
                interserverHTTPPort: 9009
                name: 0-1
                tcpPort: 9000
                templates:
                  podTemplate: clickhouse-default-pod-template
                  serviceTemplate: chi-service-template
              replicasCount: 2
              templates:
                podTemplate: clickhouse-default-pod-template
                serviceTemplate: chi-service-template
            shardsCount: 1
          name: default-0
          pdbMaxUnavailable: 1
          schemaPolicy:
            replica: All
            shard: All
          secret:
            auto: "true"
          templates:
            podTemplate: clickhouse-default-pod-template
            serviceTemplate: chi-service-template
          zookeeper:
            nodes:
            - host: keeper-clickhouse-keeper.clickhouse-test.svc.cluster.local
              port: 2181
        files:
          users.d/roles.xml: |
            <clickhouse>
                <roles>
                    <role_admin>
                        <grants>
                            <query>GRANT SELECT, INSERT, UPDATE, DELETE ON *.*;</query>
                        </grants>
                    </role_admin>
                    <role_test_user>
                        <grants>
                            <query>GRANT All ON redacted.*;</query>
                            <query>GRANT SELECT ON system.users;</query>
                        </grants>
                    </role_test_user>
                </roles>
            </clickhouse>
        profiles:
          clickhouse_operator/http_connection_timeout: "10"
          clickhouse_operator/log_queries: "0"
          clickhouse_operator/max_concurrent_queries_for_all_users: "0"
          clickhouse_operator/os_thread_priority: "0"
          clickhouse_operator/skip_unavailable_shards: "1"
          default/connect_timeout_with_failover_ms: "1000"
          default/distributed_aggregation_memory_efficient: "1"
          default/do_not_merge_across_partitions_select_final: "1"
          default/load_balancing: nearest_hostname
          default/log_queries: "1"
          default/os_thread_priority: "2"
          default/parallel_view_processing: "1"
          default/prefer_localhost_replica: "0"
          default_resources/max_memory_usage: "1073741824"
          default_resources/max_threads: "4"
          default_resources/profile: default
          reader/profile: default_resources
          reader/readonly: "1"
          writer/profile: default_resources
        settings:
          logger/console: "1"
          logger/formatting: json
          logger/level: trace
          prometheus/asynchronous_metrics: "true"
          prometheus/endpoint: /metrics
          prometheus/events: "true"
          prometheus/metrics: "true"
          prometheus/port: "8888"
        users:
          clickhouse_operator/networks/ip:
          - <IP_ADDRESS>
          - ::/0
          - <IP_ADDRESS>/0
          - <IP_ADDRESS>/8
          clickhouse_operator/password: ""
          clickhouse_operator/profile: clickhouse_operator
          default/networks/host_regexp: (chi-clickhouse-[^.]+\d+-\d+|clickhouse\-clickhouse)\.clickhouse-test\.svc\.cluster\.local$
          default/networks/ip:
          - ::1
          - <IP_ADDRESS>
          default/password: ""
          default/profile: default
          default/quota: default
          team_redacted/grants/query:
          - GRANT role_admin
          team_redacted/networks/host_regexp: (chi-clickhouse-[^.]+\d+-\d+|clickhouse\-clickhouse)\.clickhouse-test\.svc\.cluster\.local$
          team_redacted/networks/ip:
          - ::1
          - <IP_ADDRESS>
          - ::/0
          - <IP_ADDRESS>/0
          - <IP_ADDRESS>/8
          team_redacted/password: ""
          team_redacted/profile: writer
          team_redacted/quota: default
          test_user/grants/query:
          - GRANT role_test_user
          test_user/networks/host_regexp: (chi-clickhouse-[^.]+\d+-\d+|clickhouse\-clickhouse)\.clickhouse-test\.svc\.cluster\.local$
          test_user/networks/ip:
          - ::1
          - <IP_ADDRESS>
          - ::/0
          - <IP_ADDRESS>/0
          - <IP_ADDRESS>/8
          test_user/password: ""
          test_user/profile: writer
          test_user/quota: default
        zookeeper:
          nodes:
          - host: keeper-clickhouse-keeper.clickhouse-test.svc.cluster.local
            port: 2181
      defaults:
        replicasUseFQDN: "False"
        storageManagement: {}
        templates:
          serviceTemplate: chi-service-template
      reconciling:
        cleanup:
          reconcileFailedObjects:
            configMap: Retain
            pvc: Retain
            service: Retain
            statefulSet: Retain
          unknownObjects:
            configMap: Delete
            pvc: Delete
            service: Delete
            statefulSet: Delete
        configMapPropagationTimeout: 10
        policy: unspecified
      stop: "False"
      taskID: 63f83cc8-80ec-443e-8c07-88044da24e74
      templates:
        PodTemplatesIndex: {}
        ServiceTemplatesIndex: {}
        VolumeClaimTemplatesIndex: {}
        podTemplates:
        - metadata:
            creationTimestamp: null
            labels:
              app: clickhouse
              version: 24.10.1-alpine
          name: clickhouse-default-pod-template
          spec:
            containers:
            - image: clickhouse/clickhouse-server:24.10.1-alpine
              name: clickhouse
              resources:
                limits:
                  memory: 4Gi
                requests:
                  cpu: 300m
                  memory: 300Mi
              volumeMounts:
              - mountPath: /var/lib/clickhouse
                name: data-storage-vc-template
              - mountPath: /var/log/clickhouse-server
                name: log-storage-vc-template
            - args:
              - server
              env:
              - name: CLICKHOUSE_PASSWORD
                valueFrom:
                  secretKeyRef:
                    key: CLICKHOUSE-CREDS-CLICKHOUSE-OPERATOR-PASSWORD
                    name: clickhouse-credentials
              - name: LOG_LEVEL
                value: debug
              - name: ALLOW_EMPTY_BACKUPS
                value: "true"
              - name: API_LISTEN
                value: <IP_ADDRESS>:7171
              - name: API_CREATE_INTEGRATION_TABLES
                value: "true"
              - name: BACKUPS_TO_KEEP_REMOTE
                value: "3"
              - name: REMOTE_STORAGE
                value: s3
              - name: S3_ACL
                value: private
              - name: S3_ENDPOINT
                value: http://s3-backup-minio.minio.svc.cluster.local:9000
              - name: S3_BUCKET
                value: clickhouse
              - name: S3_PATH
                value: backup
              - name: S3_ACCESS_KEY
                value: backup-access-key
              - name: S3_SECRET_KEY
                value: backup-secret-key
              - name: S3_FORCE_PATH_STYLE
                value: "true"
              - name: S3_DISABLE_SSL
                value: "true"
              - name: S3_DEBUG
                value: "true"
              image: altinity/clickhouse-backup:2.6.3
              imagePullPolicy: Always
              name: clickhouse-backup
              ports:
              - containerPort: 7171
                name: http-backup
              resources: {}
          zone: {}
        serviceTemplates:
        - generateName: service-clickhouse
          metadata:
            creationTimestamp: null
          name: chi-service-template
          spec:
            clusterIP: None
            ports:
            - name: http-client
              port: 8123
              targetPort: 0
            - name: tcp-client
              port: 9000
              targetPort: 0
            - name: tcp-interserver
              port: 9009
              targetPort: 0
            - name: http-backup
              port: 7171
              targetPort: 0
            type: ClusterIP
        volumeClaimTemplates:
        - metadata:
            creationTimestamp: null
          name: data-storage-vc-template
          spec:
            accessModes:
            - ReadWriteOnce
            resources:
              requests:
                storage: 5Gi
            storageClassName: standard
        - metadata:
            creationTimestamp: null
          name: log-storage-vc-template
          spec:
            accessModes:
            - ReadWriteOnce
            resources:
              requests:
                storage: 2Gi
            storageClassName: standard
      templating:
        policy: manual
      troubleshoot: "False"
  pods:
  - chi-clickhouse-default-0-0-0-0
  - chi-clickhouse-default-0-0-1-0
  shards: 1
  status: InProgress
  taskID: 63f83cc8-80ec-443e-8c07-88044da24e74
  taskIDsStarted:
  - 63f83cc8-80ec-443e-8c07-88044da24e74

What is really weird is, that the only thing I am changing is enabling Istio Injection in the namespace. Network access obviously works, as the Clickhouse Pod complains about a failed authentication, so the request from the operator comes through. The password however "testPassword" didn't change which is proven by me being able to curl successfully with it from the Clickhouse operator pod. This is even weirder, as traffic would also go through the mesh and with curl it works... Is the error message form the Clickhouse Pod maybe misleading?

clickhouse_operator user restricted by operator pod in clickhouse configuration

Where do you see this restriction? Do you mean it is restricted to the operator Container, so Istio-Proxy can't access? The operator and Istio-Proxy are running in the same Pod, so the Pod level shouldn't be a problem? Also I was able to spin up a new container and access Clickhouse from there using the operator credentials.

 I attached the complete operator logs. Without Istio everything is instant.
log.txt

btw: If I change the PeerAuthentication mTLS mode from STRICT to PERMISSIVE in the clickhouse namespace and deactivate Istio for the operator, everything instantly begins to work. So the error message is definitely misleading, this is not a problem of having a wrong username/password.

accodring to logs clickhouse-operator can' connect to APIServer
what is your kubernetes environment?
minikube ? aws eks? other cloud provider?

look to logs
error: 'Get "https://<IP_ADDRESS>:443/api/v1/namespaces/clickhouse-operator/secrets/clickhouse-operator": dial tcp <IP_ADDRESS>:443: connect: connection refused'

    access:
        scheme: auto
        secret:
            name: clickhouse-operator
            runtime:
                username: ""
                password: ""
                fetched: false
                error: 'Get "https://<IP_ADDRESS>:443/api/v1/namespaces/clickhouse-operator/secrets/clickhouse-operator": dial tcp <IP_ADDRESS>:443: connect: connection refused'

operator can't get secret and will try to connect with empty login and password

look to logs error: 'Get "https://<IP_ADDRESS>:443/api/v1/namespaces/clickhouse-operator/secrets/clickhouse-operator": dial tcp <IP_ADDRESS>:443: connect: connection refused'

Alright, missed those logs and was misled by the Authentication Failed error. This totally makes sense, thanks!

look to logs error: 'Get "https://<IP_ADDRESS>:443/api/v1/namespaces/clickhouse-operator/secrets/clickhouse-operator": dial tcp <IP_ADDRESS>:443: connect: connection refused'

Alright, missed those logs and was misled by the Authentication Failed error. This totally makes sense, thanks!


Last PR before the release of BigchainDB 2.0 Beta 4

Codecov Report

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

@@           Coverage Diff           @@
##           master    #2420   +/-   ##
=======================================
  Coverage   88.43%   88.43%
=======================================
  Files          39       39
  Lines        2275     2275
=======================================
  Hits         2012     2012
  Misses        263      263


Notification message - With note

Description
Create the component as shown in the video attached below.
Animation Preview

Screenshot/Video:

https://github.com/user-attachments/assets/e19fb8f6-5aaa-426c-bff5-ce193eb8c75b

[!NOTE]
Please refer to the Animata contributing guidelines available here for rules on how to contribute to the project. Let us know in the comments if you’re working on this issue, and feel free to ask any questions!

Requirements

Create a new animated component that matches the provided design.
Add example usage of the component in the documentation or storybook.

 Guidelines & Best Practices

Write reusable and clean code following the project’s style guide.
The component should be fully customizable. The user should be able to modify props such as duration, easing, color, and size where applicable.
Follow the Contributing Guidelines before submitting your pull request.

[!IMPORTANT]
To ensure more contributors have the opportunity to participate, we kindly request that:

Each contributor submits only one pull request related to this issue.
If you're interested in working on this issue, please comment below. We will assign the issue on a first-come, first-served basis.

Additional Resources
Posted on X by: https://x.com/bartek_marzec/status/1838681304814227461

[!Tip]
Join our Discord community if you need help or have any questions. We're here to help you get started and guide you through the process. Join now

hey i would like to take this issue! can you please assign it to me

@anshuman008 Assigned.

hey @hari @sudhashrestha i would like to work on this.

Hi @prince981620, This issue mistakenly duplicated #256. I've updated the correct video; please take a look. Apologies for the inconvenience.

Hi @prince981620, This issue mistakenly duplicated #256. I've updated the correct video; please take a look. Apologies for the inconvenience.

hey @sudhashrestha i have added changed as per video.


⚠ Bofrost.at has degraded performance

In 494bbeb, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2170 ms

Resolved: Bofrost.at performance has improved in 2fea012.


Document prismaExtendType

I spent a bit of time grappling with the methodology for splitting up the fields of my Query and Mutation types across different modules/files, while still maintaining access to my Prisma models.  After I read this great writeup in the Nexus docs, I thought to look for the nexus-prisma equivalent of extendType.  Lo and behold, VSCode immediately suggested prismaExtendType (thank you, IntelliSense!).
I want to save others that effort of searching for the right mechanism, so I wrote up an outline of the function and provided context for its usage.

Hey there,
Our docs are still missing some important part so many thanks for taking the time to document that function!
Merging now 🙌


Using revisions with bicep deployments

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Mention any other details that might be useful
One really nice feature of container apps is using multiple revisions and Blue Green Deployments.
I tried to structure a deployment workflow around bicep templates like in this sample repo, but I was unable to get revisions to work correctly. Is this just something that will only be supported by using iterative deployments or will this be possible using the bicep deployment workflow as well?
Documentation or an example for this would be greatly appreciated!
Thanks in advance.

Hi @TimoWilhelm when you say you couldn't get revisions to work correctly, what issue did you face?


Update cloud-services-choose-me-content.md

Changed "Websites" to "Azure App Services"

Hi @thomasberman, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@thomasberman Thanks for this contribution.  I'll have the author review.
@Thraka Would you please review and let me know if I should merge this request?  Thank you.


Yet graphical issues in my UI (Analytics)

The proper one is on my mother phone:
• Moto e32(s)
• Android 12
• TP 0.7.2

The improper one is on my phone:
• OnePlus CPH2399
• Android 13
• TP 0.7.2

I think that at the moment it is possible to make the name expand to 2 lines when a certain category is selected. Or will have to globally change the UI of all analytics, which is difficult

Let me then release a small patch with a small change and then close

Adapted the analytics UI. I also added animations to some places


Loss is NaN

Ubuntu20.04/Python2.7/Tensorflow1.15
Run script train_Sony.py, training starts but from the log it seems the Loss is not correct?


Use file-scoped namespaces everywhere in samples

Done automatically with Rider (and manually removed changes to migration files).
Note that if we have any code snippets in the conceptual pages which don't reference a region, this would break them (since line numbers will now shift). However, we almost always use regions which wouldn't be affected (since line numbers are relative).

Also simple to do automatically with Visual Studio 😉

@roji Do we want to do this? Generally, we want code copied from samples to be usable by people who might not be running the latest of everything.

I'm thinking that at least EF Core 6.0 users have to use the latest SDK anyway, so they'd have to be manually restricting the language version to pre-10 for this to fail... But am OK if you prefer we didn't do this.


After removing items from moving contraption by shift-clicking, the contraption cannot be disassembled properly and could duplicated

Describe the Bug
Extract an item from a moving contraption assembled by shift-clicking, and disassemble the contraption. It crashes (or logs an error) with the message java.lang.IllegalArgumentException: Transfer variant may not be blank..
Reproduction Steps

Construct any moving contraption with an attached chest containing some items (maybe reproducible with other storage blocks e.g. barrel) - I had reproduced w/ windmill (not crashes, but could lead to dupe bug in Singleplayer), minecart (crashes, see the comment from https://github.com/Fabricators-of-Create/Create/issues/1211#issuecomment-1842518942 for vids), gantry (crashes)
Remove item from the inventory by shift-clicking
Disassemble the contraption

Expected Result
It should be disassembled properly
Screenshots and Videos
output.webm
Crash Report or Log
No response
Operating System
Windows 11
Mod Version
0.5.1d
Minecraft Version
1.20.1
Other Mods

EMI 1.0.9
Trinkets 3.7.0
ModMenu 7.1.0

Additional Context
Related Issues

#1080 (and issues marked as duplicates)

#1208
#1134 - Discovered most of the reason, see https://github.com/Fabricators-of-Create/Create/issues/1134#issuecomment-1746084470
#1211

Possible Solutions

I have locally fixed the issue by copying the return value (L102) of StorageInteractionContainer.getItem in my dev env. It seems that the shift-click interaction modifies the return value of getItem directly. But I have no idea if the solution could produce other side effects.
https://github.com/Fabricators-of-Create/Create/blob/49cc17e3de33c965b1c409130abe436821f7410c/src/main/java/com/simibubi/create/content/contraptions/MountedStorageInteraction.java#L96-L103
Another possible solution is changing the Porting-Lib code. Apply the isEmpty filter whenever ItemStackHandler.nonEmptyViews is called.
https://github.com/Fabricators-of-Create/Porting-Lib/blob/41c9aacb30f43e0993c63f1da4438e1943fc6697/transfer/src/main/java/io/github/fabricators_of_create/porting_lib/transfer/item/ItemStackHandler.java#L101-L111

I've had this one too, with gantries.
It seems removing a stack (through shift clicking or not) of a moving contraption causes it.

duplicate of #1080


Updating the Dockerfile to latest

I see the latest Dockerfile points to 1.1.2 and we could update it.
If this happens, is it also possible to setup a docker hub entry for homebase?
This would make it easier to pull stuff for CI/CD.

I suppose it would be cool to get a new release / tag too! :)

Hey so, at the moment Homebase isn't really an active project. If you just want to create PRs, I'll merge them with a cursory overview.

OK cool, I'll get back to this and try to keep the ball rolling. Thanks for your work! For now, I've published decentral1se/homebase:ventilator on docker hub (latest master) inspired by https://chaos.social/web/statuses/103884032398691689.

For anyone who is interested, this is the Dockerfile I am using personally:
https://gitlab.com/mkroehnert/homebase-docker
It allows me to update the configuration file without having to rebuild the container.


[Agenda Item] Can we open up slack for everyone?

Overview:
Most open source foundations/communities have widely available IRC, Discord servers/Slack servers that anyone can join and ask a question, open a discussion. If It is not done so already, can we openly share slack invite link, and add an invite link to slack here: https://greensoftware.foundation/join-us . Also maybe share it on the github page?
Related topic: The type of agenda item you want to propose.

[ ] Governance: New project
[ ] Governance: Other
[ ] Process
[x] External Engagement
[ ] Technology
[ ] Other

Related working groups:

[x] Community
[ ] Open Source
[ ] Policy
[ ] Standards
[x] Oversight Committee

Related issues or discussions:
Please list all related issues so that we can see the originating conversation, e.g. #10 or https://github.com/Green-Software-Foundation/discussions/discussions/5
More information:

Any other information you want to add.

We are currently trialling having our discussions centralised on GitHub. It would be good to see how this plays out as many GSF members do not have Slack access at work.

E.g. - Zephyr Project community has a public Slack anyone can join and is widely used for project involvment, onboarding etc (while Steering Committee meetings etc are run seperately on Teams/Zoom)

Discussions around Slack for informal discussions and direct messaging. @seanmcilroy29 will review to see if we can have a channel for informal communications for DM and General Discussion? Discussion for consolidation of public channels for non-GSF members and keep private channels for internal GSF. Recommendation to resolve the non members proposal and return to the tooling.

This is an old issues and since the conversations have moved over to GitHub discussions: https://github.com/orgs/Green-Software-Foundation/discussions
Closing this issue since we have a lot open, re-open if there is more to discuss.


Phaser 3 Spine and Scaling

Hi Rich,
I read the latest newletter and am thrilled to hear about Phaser 3's Spine moving forward. There was something that mentioned about scaling and its inherent complexity. I just wanted to mention that there are specific use cases for Spine in games to consider. This is what I encountered:
I'm stuck with Spine Essentials and PhaserCE + the old Phaser Spine plugin. To simulate breathing, I scale the main body or maybe the torso, while disabling the Scale inherit on certain parts like the thighs, arms, and neck. Curiously, the old Phaser Spine puts the Spine object in a group, and this means I scale the group from Phaser's side, scaling the entire object as expected. Rotating the object resulted in something that was expected as well. This is good for scenes that repeat, like a cinematic scene where the group rotation and scaling is used for setting the scene.
Now, looking at the newer Phaser Spine plugin for PhaserCE that integrates Spine-TS, the Spine object uses the sprite object. Rotating and scaling the sprite object results in directly transforming the root bone of the Spine animation. This is good for maybe sidescrollers or something, but if I were relying on the group-scale like features as mentioned above, this is a deal breaker.
Can we have the two kinds of scaling available side-by-side as mentioned here?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

In the new Spine plugin for 3.19 you have two choices: You can either scale the object directly, which is the same as scaling the Skeleton in the Spine API, so it will impact all bones from the root and down. Or, you can target a specific Bone and scale just that. Which should provide both options you need.


NFL Update

It looks like all the pages on NFL.com have been changed for the 2020 season.  Will there be a code update?

The README should answer your question.


Check & fix Project users entity and repository

https://github.com/toggl/toggl_api_docs/blob/master/chapters/project_users.md

According to migration guide, Projects related endpoints are moved into /me and /workspace//` paths. So related logic and entity structure should be refactored.


[BUG]: Property decimal does not exist on type, when using pgTable in drizzle orm

What version of drizzle-orm are you using?
0.34.0
What version of drizzle-kit are you using?
0.25.0
Describe the Bug
I got: TS2339: Property decimal does not exist on type when writing this code
import {pgTable} from "drizzle-orm/pg-core";

export const table = pgTable(
	"table",
	(t) => ({
		column: t.decimal(),
	}),
);

Is this on purpose and should be replaced by numeric? Thank's.
Expected behavior
No response
Environment & setup
No response

Decimal and numeric are the same thing. We'll add the decimal alias to the callback syntax, but in the meantime, using numeric shouldn't affect how migrations are generated.


The "Working with DNX projects" article should document all nuspec metadata related properties

PR submitted: https://github.com/aspnet/Docs/pull/599


request_id: Add option to always set request id in response

Description: Add configuration option to return x-request-id in all cases, even if tracing is not forced.
Risk Level: LOW (disabled by default)
Testing: unit tests
Docs Changes: proto documentation
Release Notes: updated
Fixes #10807

This is a followup for one of the discussion branches in #10429.

clang-tidy looks like false positive:
2020-04-16T09:26:08.1123546Z source/common/http/conn_manager_config.h:14:10: error: 'common/stats/symbol_table_impl.h' file not found [clang-diagnostic-error]
2020-04-16T09:26:08.1124954Z #include "common/stats/symbol_table_impl.h"
2020-04-16T09:26:08.1125360Z          ^
2020-04-16T09:26:08.1129473Z
2020-04-16T09:26:08.1129806Z 59922 warnings and 1 error generated.
2020-04-16T09:26:08.1130302Z Error while processing /source/source/common/http/conn_manager_config.h.

Same for coverage:
[----------] 1 test from EvironmentCredentialsProviderTest
[ RUN      ] EvironmentCredentialsProviderTest.MissingAccessKeyId
test/extensions/common/aws/credentials_provider_impl_test.cc:51: Failure
Value of: credentials.accessKeyId().has_value()
  Actual: true
Expected: false
Stack trace:
  0x8c2e26f: Envoy::Extensions::Common::Aws::EvironmentCredentialsProviderTest_MissingAccessKeyId_Test::TestBody()
  0x121efa46: testing::internal::HandleSehExceptionsInMethodIfSupported<>()
  0x121dc011: testing::internal::HandleExceptionsInMethodIfSupported<>()
  0x121c68e2: testing::Test::Run()
  0x121c73e8: testing::TestInfo::Run()
... Google Test internal frames ...

test/extensions/common/aws/credentials_provider_impl_test.cc:52: Failure
Value of: credentials.secretAccessKey().has_value()
  Actual: true
Expected: false
Stack trace:
  0x8c2e43f: Envoy::Extensions::Common::Aws::EvironmentCredentialsProviderTest_MissingAccessKeyId_Test::TestBody()
  0x121efa46: testing::internal::HandleSehExceptionsInMethodIfSupported<>()
  0x121dc011: testing::internal::HandleExceptionsInMethodIfSupported<>()
  0x121c68e2: testing::Test::Run()
  0x121c73e8: testing::TestInfo::Run()
... Google Test internal frames ...

[  FAILED  ] EvironmentCredentialsProviderTest.MissingAccessKeyId (1420 ms)

I'm not sure what happened with circlici, it tells about compilation errors in a code which does not exist for lines which are not there in the last version of pr.
I'll just rebase to hopefully make it go away.

#10860 should fix your clang-tidy error

@yanavlasov clang-tidy is still broken:
source/common/http/conn_manager_config.h:14:10: error: 'common/stats/symbol_table_impl.h' file not found [clang-diagnostic-error]
#include "common/stats/symbol_table_impl.h"

Merge current master. You don't have the fix.
/wait

Oh, merged. Misread the comment.

@htuch @mattklein123 All tests did pass, PTAL


Specially mark events, which will happen during Code Week

Some ideas: have a Code Week view, create a custom marker for events, add a special badge to event pages, include that as a search parameter etc.

Seems like a good idea, let's see what others ambassadors think about it.

Sounds like a good idea to me (seeing the number of events declared outside
of Code Week or as "ongoing throughout the year".
But is it easily "doable" in terms of implementation on the site ?
A+,
Alan
[image: --]
Alan McCullagh
[image: https://]about.me/alan.mccullagh
https://about.me/alan.mccullagh?promo=email_sig&utm_source=email_sig&utm_medium=email_sig&utm_campaign=external_links
On 20 July 2016 at 17:36, Oana Sipos<EMAIL_ADDRESS>wrote:

Seems like a good idea, let's see what others ambassadors think about it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/codeeu/coding-events/issues/161#issuecomment-233987899,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF9UtF5uhzukuAaz1RKYkRzazDxpZNYwks5qXkBngaJpZM4BvKVU
.


Add interface to decatonClient for customizing delay

Hello, decaton team.
We are using decaton in our application and for one topic, we’d like to use the delayed event feature of decaton.
We are using decatonClient to publish events and there is no put method which can be used to custom  scheduledTime  and it’s hard to extend the DecatonClientImpl class. So I added the put method with delay duration (by duration or milliseconds) as parameter.
Please take a look at it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.weijie.fan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Build failure by doc version tag. I'll take care of it after merging.

This change has been released as part of 0.0.44


Ed25519: Switch implementation to a C based implementation

Our Ed25519 implementation benchmarks verification speed using a 11byte message. On my system, (2.8GHz, Intel i7 Kaby Lake, no other programs running), this took 193758 nanoseconds.
Converting into verifications per second, this is 5161 verifications per second. (Note this could have been subject to external interference, since this is a Ubuntu install which likely had background programs running)
DJB's reference implementation (mentioned here): reports "273364 cycles to verify a  signature on Intel's widely deployed Nehalem/Westmere lines of CPUs".  At my laptops 2.8GHz rate, that translates to 10242 single verifications per second. These were benchmarked against 59 byte messages. (Length of messages matters, due to hashing involved)
This site https://bench.cr.yp.to/results-sign.html provides benchmarking across many different cpus. For the kaby lake cpu's, it reports 160085 cycles per verification, which is 17490 verifications per second at 2.8GHz. (Again on 59 byte messages)
It may be worth considering switching to using a C version in the future, and linking via Cgo. This could potentially yield a factor of 3 increase in efficiency. Bernstein's implementation also has the batch verification implemented, which could yield another factor of 2 efficiency increase. (This batch method can be implemented in go also, just hasn't been done yet). We could also modify the source, to include the method we've been discussing for caching the uncompression of the public key, to further increase verification speed. This would make sense to do if signature verification ever became a bottle neck.

Cool. I'm in favour of a solid rust implementation and then compare that against an existing C version.


Form Context: Dynamic children crash app

Dynamically adding children to a Form context, even simple layout elements, will crash the app.
Encountered this tricky bug in a client app. For context, I had something like the following:
form(
	formField(),
	formField(),
	div({omit: !model.showErrorMsg, item: 'Error message...'}),
	formField(),
	formField(),
	formField(),
	formField()
)

When model.showErrorMsg: true and the div is no longer omitted, the subsequent FormField had their FieldModels shifted. This caused Model Change Exceptions, which brought the app down. My current theory is that the 'new' div has been given a FieldModel.
I understand that we support SubForms for dynamically adding FormFIelds, but I would expect other components to be dynamic in a Form context without issue.
My workaround for now is to set style: {display: none} rather than omit: true.

I tried to replicate this in Toolbox, but couldn't... then tried to replicate in the client app where I original saw it reliably, and also couldn't!
So not entirely sure what happened there, but think we can ignore this for now and keep it in mind if it appears again...

You bet - agree then let's close it for now.  I will keep an eye out, and still glad you posted.  Something like this usually comes back around eventually, or points at some other issue we will see again.

This has resurfaced in the process of upgrading a client-app to latest hoist-react. Will take another look.

Managed to reproduce in Toolbox.
Error occurs when re-rendering changes the order of sibling FormFields. React doesn't have a way to determine that the newly added FormField isn't one that was there before, and so tries to repurpose it with a different FieldModel, causing the error. The solution is to use key to identify each FormField, allowing React to better identify what should change on re-render.
Fixed here: https://github.com/exhi/hoist-react/pull/1063


Issue with _set_db_data when using psycopg3

How do you use Sentry?
Sentry Saas (sentry.io)
Version
2.1.1
Steps to Reproduce
I created a sample repo that reproduces the bug.

Checkout the repo

git clone https://github.com/austin-wentz/sentry-psycopg-bug.git

Install requirements

pip install -r requirements.txt

Startup postgres

docker-compose up

Run test without Sentry (test will succeed)

./manage.py test

Run test with Sentry (test will fail)

export USE_SENTRY=True && ./manage.py test

From what I can tell, the issue is that the call to get_parameters() tries to access pgconn.info, but that will throw an operational error if the connection is already closed.
A suggested fix would be something like
if is_psycopg3:
    connection_params = {}
    if not cursor_or_db.connection.closed
        connection_params = cursor_or_db.connection.info.get_parameters()

Expected Result
The expected result is for the sentry-sdk to not try and access a bad connection in _set_db_data
Actual Result
The actual result is that the call to get_parameters() results in a psycopg.OperationalError:
Traceback (most recent call last):
  File "/Users/austin/workplace/sentry-psycopg-bug/spbug/tests.py", line 11, in test_bug
    connection.connect()
  File "/Users/austin/workplace/sentry-psycopg-bug/venv_3_10/lib/python3.10/site-packages/sentry_sdk/utils.py", line 1711, in runner
    return sentry_patched_function(*args, **kwargs)
  File "/Users/austin/workplace/sentry-psycopg-bug/venv_3_10/lib/python3.10/site-packages/sentry_sdk/integrations/django/__init__.py", line 658, in connect
    _set_db_data(span, self)
  File "/Users/austin/workplace/sentry-psycopg-bug/venv_3_10/lib/python3.10/site-packages/sentry_sdk/integrations/django/__init__.py", line 693, in _set_db_data
    connection_params = cursor_or_db.connection.info.get_parameters()
  File "/Users/austin/workplace/sentry-psycopg-bug/venv_3_10/lib/python3.10/site-packages/psycopg/_connection_info.py", line 91, in get_parameters
    for i in self.pgconn.info
  File "psycopg_binary/pq/pgconn.pyx", line 90, in psycopg_binary.pq.PGconn.info.__get__
  File "psycopg_binary/pq/pgconn.pyx", line 635, in psycopg_binary.pq._ensure_pgconn
psycopg.OperationalError: the connection is closed

@austin-wentz Thank you for reporting this problem, and thanks for the detailed reproduction! I can confirm that I have also observed the same error, so we will try to get a fix ready soon.
Has what you are trying to do ever worked in a previous SDK version, and if so, which version? Also, have you been able to work around the issue?

@austin-wentz Thank you for reporting this problem, and thanks for the detailed reproduction! I can confirm that I have also observed the same error, so we will try to get a fix ready soon.
Has what you are trying to do ever worked in a previous SDK version, and if so, which version? Also, have you been able to work around the issue?

Sorry for the delay in response. We tried previous SDK versions, but the issue was still present. Yes, we were able to work around the issue by creating a new connection rather than trying to [re]connect the existing connection object.

Thanks for the additional information. We will have a fix soon.

After further investigation, I determined the exception is actually raised on this line. is_psycopg3 evaluates to False because cursor_or_db.connection is None.
So, we likely need to check whether cursor_or_db.connection is None before checking anything else, and set connection_params to {} in that case. For good measure, we can put the whole thing in a with capture_internal_exceptions block

Related to #2427


chore: Upgrade seedfarmer to 5.0.x

Describe your changes
Upgrade the SeedFarmer version to 5.0.0
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: a11522da76133dad679632622efde44b394453c5
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Unfortunately it looks like CI didn't test any of the modules. Should we add requirements.txt to https://github.com/awslabs/aiops-modules/blob/00c4c1b701f30b4fd6fb089b091d3d49adc8239a/.github/workflows/module-checks-dev-requirements-change.yml#L16?

Unfortunately it looks like CI didn't test any of the modules. Should we add requirements.txt to
https://github.com/awslabs/aiops-modules/blob/00c4c1b701f30b4fd6fb089b091d3d49adc8239a/.github/workflows/module-checks-dev-requirements-change.yml#L16
?

It doesn't really make a difference for our CI. None of those actions deploy anything using SeedFarmer. The reason requirements-dev.txt is in there is because our linting libraries (like ruff or mypy) do make a difference for the CI.


[BEAM-13713][Playground] Java graph extraction

[BEAM-13713][Playground] Preparer for java graph extraction

moved some from utils package to avoid cyclic dependencies
This PR is based on BEAM-13712 PR (python graph)

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

LGTM


Fix CTCP parsing to avoid segfault

Previously, a check for the LastIndex was just ensuring that there WAS a \x01 in the message, and not that the Last character in the string was a \x01

Done!


Add test_backward_value_is_correct_2

Closes #187

This is useless and slow and we made a mistake in the test.


Chrome 66 ubuntu :  caret height value is NaN

getCaretCoordinates(event.target, event.target.selectionEnd) returns { top: 6, left: 10, height: NaN } on Chrome 66. On Firefox, it returns { top: 6, left: 10, height: 31 }

I had the same issue, and it turns out because the computed lineHeight value (which is what textarea-caret uses for the caret height) was returned as normal rather than a numerical value. I worked around this by specifically setting a line-height value for my textarea, e.g. line-height: 1.2.

I was running into the same issue, i ended up using the height of the span that was added and it works fine.
Just before removing the div:
  if (isNaN(coordinates.height))
    coordinates.height = span.height;

Greetings


Understanding the OSI model for Software Engineers

NOTE: We tend to stray away  or tend not to publish reviews/comparisons of commercial product offerings.
Brief Summary:
Every developer should be able to understand some concepts of networking, how a request is sent from client to server and response back to the client, This article will give a friendly approach to understanding OSI model from a software engineer point of view. The article will accomplish this by bisecting the OSI model.
Key Takeaways:
Basic understanding of the encapsulation and de-encapsulation process in networking.
Understand the OSI model and its role in development.
Understand basic terms in networking
References:
https://afteracademy.com/blog/what-is-data-encapsulation-and-de-encapsulation-in-networking
https://www.freecodecamp.org/news/osi-model-networking-layers-explained-in-plain-english/

Thank you for your topic suggestion. Per the recent message posted in our EngEd Slack channel, we are pausing acceptance of new articles until further notice while we work through the backlog of submitted drafts. We will notify you when we are ready to accept new topic suggestions. Thank you for your patience.


[ISSUE 3822] When onDeleted, ruleId has been deleted, so change to getPluginNameBySelectorId to get pluginName.

When onDeleted, ruleId has been deleted, so change to getPluginNameBySelectorId to get pluginName.
Fixes #3821.
Fixes #3822.

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #3825 (62ae370) into master (1ea62be) will decrease coverage by 0.27%.
The diff coverage is 0.00%.

:exclamation: Current head 62ae370 differs from pull request most recent head 39dde08. Consider uploading reports for the commit 39dde08 to get more accurate results

@@             Coverage Diff              @@
##             master    #3825      +/-   ##
============================================
- Coverage     64.81%   64.54%   -0.28%
+ Complexity     6094     6054      -40
============================================
  Files           898      898
  Lines         24678    24678
  Branches       2238     2236       -2
============================================
- Hits          15996    15929      -67
- Misses         7275     7333      +58
- Partials       1407     1416       +9

Impacted Files
Coverage Δ

...enyu/admin/service/publish/RuleEventPublisher.java
15.15% <0.00%> (ø)

...controller/ShenyuClientHttpRegistryController.java
77.77% <0.00%> (-22.23%)
:arrow_down:

...yu/sync/data/http/refresh/AbstractDataRefresh.java
68.96% <0.00%> (-13.80%)
:arrow_down:

...ache/shenyu/plugin/grpc/cache/GrpcClientCache.java
87.50% <0.00%> (-12.50%)
:arrow_down:

...ruptor/RegisterClientServerDisruptorPublisher.java
52.94% <0.00%> (-11.77%)
:arrow_down:

...a/org/apache/shenyu/common/utils/VersionUtils.java
67.85% <0.00%> (-10.72%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
54.25% <0.00%> (-9.58%)
:arrow_down:

...che/shenyu/sync/data/http/HttpSyncDataService.java
81.63% <0.00%> (-8.17%)
:arrow_down:

.../apache/shenyu/admin/model/dto/BatchCommonDTO.java
50.00% <0.00%> (-7.15%)
:arrow_down:

...apache/shenyu/admin/model/dto/AuthPathWarpDTO.java
57.14% <0.00%> (-7.15%)
:arrow_down:

... and 31 more

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


[auth-swift] Add 'FirebaseAuth*' to iOS 13+ scheme using SPM

The Xcode project file changes come from configuration done to the settings highlighted in green.

I also moved over FirebaseAuthCombine since FirebaseAuth will require iOS 13+.

It turns out my problem was having the firebase-ios-sdk package open in another window, so the dependencies didn't show up when I got to that screen.


Separate React from ReactNative

In React Native 0.25, React Native stops wrapping shared React functionality (createClass, PropTypes etc. -- see https://github.com/facebook/react-native/commit/2eafcd45dbd42f750df1ab9aa3770fed5cdf11ae) and expects end users to import these from the react package instead. This PR implements that behavior.

Closing in favor of https://github.com/brentvatne/react-native-linear-gradient/pull/76


moloch_update_geo.sh no longer works.

Elasticsearch version: N/A
Moloch version: master
OS name and version: ubuntu 16.04
How was Moloch built/installed: (rpm, deb, easybutton, ...) easybutton
Provide logs, stack traces and steps to reproduce:
The moloch_update_geo.sh no longer works as maxmind now requires an account id.

yep, still trying to decide what we are going to do.  such a pain.

do you have the accounts of maxmind . i also catch the 401 of this problem with not build the geoip-datebase. and i have made the old geoip2 with it.

Fixed in master and will be part of 2.2.  You'll have to sign up for an account :(
https://molo.ch/faq#maxmind

Can we tell moloch to operate without any geo data?