No pre-build event support? How to capture git describe --dirty?

I have an embedded C project that builds with CMake, Ninja, and gcc-arm-none-eabi.
I want to capture the output (string) of a git describe --dirty ... command as (1) a string variable in my program, and (2) in the generated executable filename. I think the sensible way to do this would be with a pre-build event, which ninja does not appear to support.
Without the --dirty argument, I have it working using this git_describe CMake function. But that is only run by CMake at configure time (and it hard codes the output strings in build.ninja). So for example, if I just add the --dirty arg in my current setup, then CMake configure (on a clean git working tree), then modify a source file (making the worktree dirty), then build again, it does not re-run CMake configure, and does not re-run the git describe command, and so does not detect the dirty.
Questions:

Am I correct that ninja does not support pre-build events?
Is it possible to use ninja to reliably do what I'm describing here? On every build, without requiring the user to manually trigger a CMake configure before triggering the build.

Ideally, I think, I'd want to be able to make ninja execute and  check the output of my preferred git describe command on every build, and trigger the dependent targets to rebuild if it changes.

This type of questions are better asked and answered on the mailing list. See https://groups.google.com/group/ninja-build

CMake allows you to run commands at build time. Check this documentation [add_custom_command](https://cmake.org/cmake/help/latest/command/add_custom_command.html

@asit-dhal
Discussion here:
https://groups.google.com/g/ninja-build/c/W407yFUY-AM/m/jXMLPY9MAgAJ
I've not yet attempted the various solutions proposed to me there.
I don't believe your proposal will do what I want, since PRE_BUILD only executes pre-build for the Visual Studio Generator (as documented on the page you linked).
I guess I'll close this issue, at least for now, pending the outcome on the discussion linked above.


Give a warning when a kit/a pattern is about to be cleared?

I've been through this a few times..
Trying to compose something in the internal sequencer -> accidentally cleared it with a chain write -> no pattern, no kit, no nothing :(

undo feature perhaps?
The save mode definitely needs it. i've accidently used save page instead of write a few times.

We also have copy/paste buffer now.
I think the additional latency required to copy RAM to a recovery buffer before write,
is not feasible. Particularly in chain mode when timing is already tight.


[BUG] Weight not carrying over

Module Version: v0.5.7
Describe the bug
Unidentified items don't have weight even after selecting the option in the properties manager.
To Reproduce
Steps to reproduce the behavior:

Go to the module settings.
Click Open Property Manager.
Select "weight" for every item that has the option.
Click Submit to save the changes.
Choose Mystify for any item.
Open the new unidentified item.
The item has 0 weight.

Expected behavior
The unidentified items should have the same weight as the originals.
Screenshots

Browser:

Chrome v 111.0.5563.64 (Official Build) (x86_64)

Foundry Version:
10.291
Game System:
D&D 5e v 2.1.5
Additional context
I'm having the same issue in 2 games. I set up a test game that doesn't have any other active modules.

is not a bug is the default behaviour, you can set on the module settings the single property you don't want to mistify.

The weight doesn't carry over if I have the Weight checkbox selected or deselected. I've been testing it with multiple item types.


Trouble installing on Mac

I believe I followed the instructions correctly, but the install ended with:
   Compiling dijo v0.1.2
error[E0432]: unresolved import `notify::INotifyWatcher`
 --> /Users/username/.cargo/registry/src/github.com-1ecc6299db9ec823/dijo-0.1.2/src/app/mod.rs:4:30
  |
4 | use notify::{DebouncedEvent, INotifyWatcher};
  |                              ^^^^^^^^^^^^^^ no `INotifyWatcher` in the root

error: aborting due to previous error

For more information about this error, try `rustc --explain E0432`.
error: failed to compile `dijo v0.1.2`, intermediate artifacts can be found at `/var/folders/gq/6g5prsts0knc_vlvwfhz63mr0000gn/T/cargo-installOYUMfV`

Caused by:
  could not compile `dijo`.

The fix for this issue was merged and released earlier today (dijo >= v0.1.3) , could try updating with:
# if you installed from source
$ git pull origin master
$ cargo install --path . --force

# if you installed from crates.io
$ cargo install dijo

This did get me up and running, thank you very much for the support!


RE3: Game display not appearing on VR headset

Hi,
I have RE2 with your VR mod working fine on my Lenovo Legion 7 laptop using Virtual Desktop on a Quest 2.  :)
However . .
I cannot get RE3 VR mod working correctly.
When I launch the game from virtual desktop on the headset (Quest 2), it initially loads in the desktop view, then just after the "Nvidia gameworks" banner, it switches to Steam VR mode and I am in the Vive "holodeck", I can hear the game music/sounds, if I lift my headset, I can see on my laptop screen that the game is indeed at the main menu in VR mode and the headset movement and controller buttons & keys are working.
If I hit the insert key the mod menu pops up and I can switch the game between 1st/3rd person view (on the laptop screen), but still nothing changes in the headset, still stuck at Vive "holodeck".
I have tried disabling any HDR settings in windows display settings and also Nvidia control panel.
NOTE: I dont have the option for choosing the color format / dynamic range as has been suggested on some forums.
(Using latest Nvidia driver 497.29 for GeForce RTX 3080)
Also tried with all combinations of Steam Theatre and Overlay options on/off.
Also tried adding RE3 to VR library and launching it from inside Vive "holodeck" or Steam VR Home, same issue, stuck in "holodeck".
UPDATE 05/01: Got it working (sort of)
The attached RE3_CONFIG.INI file works, until you exit the game, at which point the config file gets changed
It seems that the HDR setting keeps getting turned on even though you don't enable it in-game.
File can be made READ-ONLY to prevent this.
Running Game:

Edit/overwrite file "C:\Program Files (x86)\Steam\steamapps\common\RE3\RE3_config.ini" with contents of attached file.
Ensure Steam VR is not running.
Launch RE3 from Steam GUI.
Once game loads to start screen, click on it on laptop so it has main focus, this should make it appear in headset.

re3_config.ini.-working.txt

I have the same problem with quest 2 (either with cable or airlink or vd). Once enabling and disabling hdr the game started randomly. Then it didn't start anymore: i can hear the audio but not the image, i refer to the steam valley

Hello, I found the solution for RE3 and RE8, you need in NVIDIA control panel, Output color depth at 8 bpc
Output color format set to yCbCr422
The output dynamic range should be limited

This worked but unfortunately vr doesn't work, I can't move my hands I can move the head but that doesn't control the body only controls the camera I have to use the joystick to move around. Any idea?

This worked but unfortunately vr doesn't work, I can't move my hands I can move the head but that doesn't control the body only controls the camera I have to use the joystick to move around. Any idea?

That's the way its supposed to work.
Look with headset, move with joystick.

This worked but unfortunately vr doesn't work, I can't move my hands I can move the head but that doesn't control the body only controls the camera I have to use the joystick to move around. Any idea?

That's the way its supposed to work. Look with headset, move with joystick.

No I mean moving my head dosnt change the Direction my character moves. the only thing it controls is the camera I have to use the right joystick to turn left and right nothing apart from the camera works.

https://youtu.be/aw_Db9JcShU sorry it's so dark but as you can see. I can't my arms, and I need to use the right stick to make jill move left and right it works like it would with a controller but the camera is free for me to move but not jill

This worked but unfortunately vr doesn't work, I can't move my hands I can move the head but that doesn't control the body only controls the camera I have to use the joystick to move around. Any idea?

That's the way its supposed to work. Look with headset, move with joystick.

Can you tell us in more detail how you got to include the picture in the helmet? I can try in NVIDIA control panel change olor depth at 8 bpc and etc. but it can't help. When start game  I see in helm only  the Vive "holodeck"(((

I am having the same issue. Resident Evil 2 VR mod worked with 0 issues and now I can't even get Resident Evil 3 VR to launch

I have the same problem with quest 2 (either with cable or airlink or vd). Once enabling and disabling hdr the game started randomly. Then it didn't start anymore: i can hear the audio but not the image, i refer to the steam valley

Did you ever find a fix for this ?

I have the same problem with quest 2 (either with cable or airlink or vd). Once enabling and disabling hdr the game started randomly. Then it didn't start anymore: i can hear the audio but not the image, i refer to the steam valley

Did you ever find a fix for this ?

No and I gave up looking for a solution. Just stuck to re2

I had this issue and after 8 hours of troubleshooting I finally got the game to play in VR on my quest 2.
All I had to do is click enable HDR on the home screen then it launched in my headset and said it would only enable HDR on Fullscreen . Then the game worked just fine.
 Let me know if it works for you please

Fixed in https://github.com/praydog/REFramework/commit/163704a8521e01916abfd78ae863a46135c7228d for D3D12. Improvements will come later. Colors will still be washed out or incorrect in HDR but there will at least be video output. It will still be playable with HDR on if you can tolerate not having correct colors. HDR should still be turned off as as complete fix.
New builds can be found here: https://github.com/praydog/REFramework-nightly/releases/


A working example with AVAudioPCMBuffer

Hi everyone,
I’m currently working on a project using AVAudioEngine and need assistance with properly encoding and decoding AVAudioPCMBuffer to and from the Opus format.
Would anyone be able to share a working solution or example, please?
Any help or pointers would be greatly appreciated!
Thank you,
Ondrej

It's actually fairly simple to do using this package.
// set the opus encoding format
var encodingFormat = AVAudioFormat(
  opusPCMFormat: .float32,
  sampleRate: .opus48khz,
  channels: 1
)

// Initialize the encoder
guard var opusEncoder = try? Opus.Encoder(format: encodingFormat) else {
  print("Failed to create opus encoder")
  return
}

// and now you can use the encoder to encode your AVAudioPCMBuffer. The encoding migh fail if the samplerate does not match, sou you might need to convert the sample rate first
var buffer: AVAudioPCMBuffer = example_buffer // your buffer
var opusData = Data(count: 10000) // not sure why, but setting the data count to something like this fixes weird errors I've encountered
_ = try opusEncoder.encode(buffer, to: &opusData)
print(opusData)

Was stuck on this myself for weeks.
Thank you @ydnar for creating this!


CON-2379: usage of new history manipulation modules and bugfixes

Coverage decreased (-4.04%) to 17.029% when pulling 16c73a3a8afb5a0d95140b5fb6101dfb398038cb on CON-2379-split-actions-history-changehistory into 5829b9797b5424bd6da075d4ea7e1b1e075a2450 on development.

Coverage decreased (-8.9%) to 12.175% when pulling 049cf63e8e86dd4218d4b84b9e1fda5429e76c93 on CON-2379-split-actions-history-changehistory into 5829b9797b5424bd6da075d4ea7e1b1e075a2450 on development.


Autoconfigure --ipv4-pod-subnets / --ipv6-pod-subnets in cloud environments

When Cilium is configured with cloud integration modes (ENI, Azure) and encryption, ideally it would autoconfigure --ipv4-pod-subnets / --ipv6-pod-subnets (as necessary) based on information provided from the cloud APIs.

Completed.
commit 58f7f700a37023f79886bd6ce4b543fd7e08bff6
Author: John Fastabend<EMAIL_ADDRESS>Date:   Mon Mar 15 23:09:26 2021 -0700
cilium: auto-detect network interfaces for IPAMENI case

[ upstream commit 2c878a512de941d3557965cdba0f02d84528bc90 ]


Make getWindow null/undefined safe again

Make getWindow null/undefined safe again to fix some IE11 issues.
See #1159 for details.

Thx a lot!


fix spi st7789 example for v0.8

This is the only one I know how to fix, the others hal packages don't seem to be at eh1 yet.
Related to #99
NOTE: this cannot be merged until v0.8 is released

This is the only one I know how to fix, the others hal packages don't seem to be at eh1 yet.

I don't know about the ESP32 one, but there is e-h 1 support for the pico. The feature to enable support is still called eh1_0_alpha, but the latest release uses the final version of e-h 1.

NOTE: this cannot be merged until v0.8 is released

Because CI is failing? We will need to change CI anyway to make sure it uses the latest development version to build the examples. The simplest solution would be to use path dependencies in the examples. But this would make anyone how just wants to try one of the examples also use the latest development version. I'm not sure if that's a problem, but all solutions I can come up with have some drawback.

I don't know about the ESP32 one

you can use the eh1 feature on the latest version of the HAL

Because CI is failing? We will need to change CI anyway to make sure it uses the latest development version to build the examples. The simplest solution would be to use path dependencies in the examples. But this would make anyone how just wants to try one of the examples also use the latest development version. I'm not sure if that's a problem, but all solutions I can come up with have some drawback.

IMHO the path dependency is the best way for such examples - it ensures that you examples always match what's currently in the repo (and anyone looking at the examples is looking at the repo). it's really confusing if the two don't match.

superseded


rsync error with Windows 1803

This bug-tracker is monitored by developers and other technical types.  We like detail!  So please use this form and tell us, concisely but precisely, what's up.  Please fill out ALL THE FIELDS!
If you have a feature request, please post to the UserVoice.
If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker.
Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues.  Instead, send dumps/traces to<EMAIL_ADDRESS>referencing the GitHub bug number. Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".

Your Windows build number:  (Type ver at a Windows Command Prompt) Microsoft Windows [Version 10.0.16299.431]

What you're doing and what's happening:  (Copy&paste specific commands and their output, or include screen shots)

When I use rsync with a USB drive, I get errors:
rsync: chgrp "/mnt/f/Gamification/TechLand/TPS/Illuminotecnica/Immagini/03/A/Stanza.dwg" failed: Operation not permitted (1)
rsync: mkstemp "/mnt/f/Gamification/TechLand/TPS/Illuminotecnica/Immagini/03/A/.Stanza.dwg.vU7MSj" failed: Operation not permitted (1)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1183) [sender=3.1.1]
This started happening after upgrading from 1709 16299.431 to 1803 17134.48, and fixed itself after a rollback. This is the code, which worked in 1709:
cd /mnt/d/Mauro/Documenti/Insegnamento/
rsync -Rauv --del --chown Mauro --chmod=ugo=rwX \
  'Gamification' \
  /mnt/f/ \
  >/mnt/c/Users/Mauro/Desktop/lista.txt \
  2>/mnt/c/Users/Mauro/Desktop/errori.txt

It still works syncing from internal hard drive to internal hard drive, and from internal to external hard drive. I tried formatting the USB drive, reformatting it as NTFS, recreating permissions, formatting again as FAT32; I also tried to remove entirely the folders and run the script again, to no avail.

What's wrong / what should be happening instead:

The folders should sync.

Strace of the failing command, if applicable:  (If some_command is failing, then run strace -o some_command.strace -f some_command some_args, and link the contents of some_command.strace in a gist here)

See our contributing instructions for assistance.

I'm going to cite #2770 for this one.

By the way, I also tried with
--no-owner --no-group
but got this error:
failed to set times on "/mnt/f/2017-2018": Operation not permitted (1)
(Not sure if the sync went through, will check as soon as possible.)

Yes you should do that. Or you can just use wsl.conf to set the metadata option. In your case, you may also want to use fstab to mount your drives vice the auto drvfs. I would try either way and see if it helps. Also try running an elevated and non-elevated session to ensure Windows permissions aren't also a blocker. Oh and I should say that it will require you to upgrade to build 17134. The fix I'm describing doesn't exist in 16299.

Also, there is possibly another related issue since I just realized you're on 16299: #1869

Will try that as soon as I will reupgrade do 17134, thanks. Just not sure what do you mean by "to mount your drives vice the auto drvfs"?

Yes but he mentioned he's new to Linux so just recommending he does some research so he can understand more about Linux.

Now I'm on 1803 17134.1, and I still got the same errors, also using --no-owner and -o metadata.
rsync: mkstemp "/mnt/f/2017-2018/.5A.xlsx.hOeFu7" failed: Operation not permitted (1)

I was able to solve using this option: https://github.com/Microsoft/WSL/issues/3187#issuecomment-388904048

Any idea about how to add uid=1000,gid=1000 as default using wsl.conf? I tried editing it and adding
[automount] options = "uid01000,gid=1000"
but it doesn't work; using mount -l I can't see the external drive listed, so maybe it's that?

Hi all,
Using the windows insider build 2004 (19033.1), I still have errors using rsync to an external USB drive used for backups.

$ rsync -vrltxz --rsync-path="wsl rsync" --delete --no-p --progress /mnt/d/filename knux@<IP_ADDRESS>:/mnt/e/
...
rsync: failed to set times on "/mnt/e/filename.0APmfD": Operation not permitted (1)

mount confirms that my device is mounted with uid=1000,gid=1000 as suggested in this issue:

$ mount
...
e: on /mnt/e type 9p (rw,relatime,dirsync,aname=drvfs;path=e:;uid=1000;gid=1000;symlinkroot=/mnt/,mmap,access=client,msize=65536,trans=fd,rfd=3,wfd=3)

It occurs only with newer files uploaded by rsync. Each time I run rsync the same files will be uploaded this the timestamp isn't the same as the source file...
My E: drive is bitlocked, I manually mount it after having unlocked it.

I was able to solve using this option: https://github.com/Microsoft/WSL/issues/3187#issuecomment-388904048

/dupe #3187 ➡ #2770


Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'scopes')

When I block all network requests to https://app.tolgee.io (eg. to simulate a server-downtime of tolgee), I am expecting that the static data / fallback data will be applied. However, once I block these requests, I get a runtime error:
tolgee.esm.mjs?c93d:1643 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'scopes')
    at CoreService.eval (tolgee.esm.mjs?c93d:1643:1)
    at step (tolgee.esm.mjs?c93d:75:1)
    at Object.eval [as next] (tolgee.esm.mjs?c93d:56:46)
    at fulfilled (tolgee.esm.mjs?c93d:46:43)

Using @tolgee/react 4.9.1 in a Next.JS (12.2.5) application.

Hello. Can you also share your Tolgee configuration (probably provided to TolgeeProvider component)?

_app.tsx
import deLocale from "../lang/resources/de.json";
import enLocale from "../lang/resources/en.json";

  ...

  const { locale: nextJsLocale } =
    useRouter();

    return (
    <>
      <Head>
        <title>Test</title>
        <link rel="icon" href="/favicon.ico" />
      </Head>
      <TolgeeProvider
        forceLanguage={nextJsLocale}
        apiKey={process.env.NEXT_PUBLIC_TOLGEE_API_KEY}
        apiUrl={process.env.NEXT_PUBLIC_TOLGEE_API_URL}
        staticData={{
          de: deLocale,
          en: enLocale,
        }}
      >
        ...MoreProviders START...
                    <Component {...pageProps} />
        ...MoreProviders END...
      </TolgeeProvider>
    </>
    )

pages/example.tsx
import { NextPage } from 'next';
import { T } from '@tolgee/react';

const Example: NextPage = () => {
  return (
    <T keyName="myTest" >
     FALLBACK TEST
    </T>
  );
};
export default Example;

What I noticed:
Using npm run build and npm run start actually produces a valid result. If Tolgee server is unavailable or network requests are blocked, the static data is shown, or the fallback text if no matching key can be found within the static data.
However, if I run npm run dev, then I get above error. What do I need to configure, to support using Tolgee with the Next.JS development server?

Hey, I've tried to replicate this and the fallback is working fine for me (it displays translations from staticData). However problem is that next.js overwhelmed by errors from console as each translate method throws an error. This is now quite hard to change. I'm working on new version of core, where I want to change this logic completely so it shouldn't be a problem in the future, so I would leave this for the new core.

The same issue exists, when the API url in the tolgee browser extensions ends with an slash
instrument.ts:129 Error: Api http error
    at new t (ApiHttpError.ts:3:5)
    at Function.<anonymous> (ApiHttpService.ts:21:21)
    at tslib.es6.js:102:23
    at Object.next (tslib.es6.js:83:53)
    at tslib.es6.js:76:71
    at new Promise (<anonymous>)
    at i (tslib.es6.js:72:12)
    at e.handleErrors (ApiHttpService.ts:19:37)
    at ApiHttpService.ts:42:22
-----------------------------------------------------------------------------------
instrument.ts:129 Error getting scopes. Trying to switch to production mode!
-----------------------------------------------------------------------------------
instrument.ts:129 Couldn't connect to Tolgee
-----------------------------------------------------------------------------------
TypeError: Cannot read properties of undefined (reading 'scopes')
    at e.<anonymous> (CoreService.ts:71:40)
    at tslib.es6.js:102:23
    at Object.next (tslib.es6.js:83:53)
    at s (tslib.es6.js:73:58)

if you removing the ending slash in the API url it works fine. The extension should validate this.

Solved in https://github.com/tolgee/tolgee-js/pull/3109


Customer assigned to wrong server - stuck at test case 3 of project

Summary
Hi, was anyone stuck at test case 3 of the project where the customer is being assigned to the wrong server for the wait event, I am struggling to get back this test case? Any help will be really appreciated.
Description
Describe the problem and code snippets if necessary
Screenshots (if any):
Insert Images here if necessary

Hihi, I tilted so hard at this exact same problem also, so I hope that what I write below will be able to save your time.
Let me give you an example to help you understand where you might have gone wrong.
Let's say server 1 has customers 2 and 3 in its queue, and is currently serving customer 1. Let's put it all in a list [1, 2, 3]. We can all agree that queuelength is 2.
Let's say server 1 has finished serving customer 1, and the Done event is being executed right now. What I suspect your current implementation does is just remove customer 1 from the list, and then this makes the list become [2, 3]. However, what happens is that when you do this, your queuelength becomes 1. This would typically work for most circumstances, but things change when rest comes into play. While the server is resting, your queuelength needs to remain as 2, as identified in the specs. Only after your server has finished resting, would your queuelength become 1.
How I got around this was instead of removing customer 1 from the list during the Done event, I have a Rest event that removes customer 1 from the list only after server has finished resting.

In simpler terms, your queue should only move up when your server is done resting, but it seems that your queue is moving up once your server is done serving the customer.

Ohh that makes sense, thank you so much for the help. I was stuck on this for long.


not working with reanimated

Somehow does not work with when Reanimated 3.14.0 installed

Thank you for pointing that, will test it when I get the time

Thank you for pointing that, will test it when I get the time

thank you.. i hope you fix it soon

https://github.com/user-attachments/assets/bfd42e58-03be-47b4-92a5-9371defb1f9c
tested it works fine with latest 3.15, this could be either problem with reanimated 3.14 in that case you can upgrade it or use 4.10 since it is the latest expo supported version. or it could be some build issue that is not related.


[WIP] Enable sort function by creation time

Related Issue: https://github.com/clear-code/redmine_full_text_search/issues/115
Related PR: https://github.com/clear-code/redmine_full_text_search/pull/118
What I did

Added sort function by creation time

User can sort each item by creation time on the search page.

ref: http://localhost:3000/search

Before
After

It's already been implemented in upstream.


DB-compare-glyphs: Names and Metrics don't show up

I'm running the script as is (with the only change being that I added paths for fonts) using the DrawBot script in Drawbot Version 3.68, and no Names or Metrics show up.

Possibly this is a OS X issue. Which version are you running?

10.10.5

This is still a problem in 10.11.6 and the most recent versions of Drawbot and the Drawbot Extension.
Maybe @typemytype knows more about this?


fix crash when unmarshaling specially-crafted ADTS packets

Codecov Report

Merging #4 (44b5798) into main (3a6d108) will increase coverage by 0.14%.
The diff coverage is 100.00%.

:exclamation: Current head 44b5798 differs from pull request most recent head e0f6185. Consider uploading reports for the commit e0f6185 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main       #4      +/-   ##
==========================================
+ Coverage   84.97%   85.11%   +0.14%
==========================================
  Files          28       28
  Lines        2502     2506       +4
==========================================
+ Hits         2126     2133       +7
+ Misses        320      318       -2
+ Partials       56       55       -1

Impacted Files
Coverage Δ

pkg/codecs/mpeg4audio/adts.go
91.17% <100.00%> (+3.42%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


NIFI-10277 Refactor ConnectionLoadBalanceServerTest

Summary
NIFI-10277 Refactors the ConnectionLoadBalanceServerTest to use a dynamic available TCP port for the server instead of a static port. The new test includes methods for success and failure conditions.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[X] Apache NiFi Jira issue created

Pull Request Tracking

[X] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[X] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[X] Pull Request based on current revision of the main branch
[X] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[ ] Build completed using mvn clean install -P contrib-check

[ ] JDK 8
[ ] JDK 11
[ ] JDK 17

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

ran local full clean build contrib check including full system test runs.  all looking good.  going to see how ci works out then merge.  thanks


PlaceholderAPI could not load the messages file

Please provide these fields before submitting an issue.
SpongeAPI version: 7.1.0-SNAPSHOT-7105dfc
PlaceholderAPI version: 4.5.1
Plugins installed: Doesn't seem to be related to other plugins
Error log [if any]: https://pastebin.com/RWp1BYkt
Description: PlaceholderAPI throws an error during startup, and all placeholders stop working.
Steps to reproduce:
Start the server with the latest PlaceholderAPI.
The problem persisted when I deleted the messages file, where PlaceholderAPI regenerated the file and still failed to load it.

This is a strange compiler error.
The source of Message has a zero arg constructor.
Use this unofficial release, which doesn't have that problem. That build is already in use on large server networks, it is proven to be good.


Thumb size for feature selection

We need to allow the user of the tangram API to set up a thumb size in logical pixel size for our mobile platform. This size would be convenient for feature selection queries where high density display makes it hard to select features without reading the framebuffer on a wider range.

@karimnaaji I didn't see that you had assigned yourself, I was working on this today and I should have noted it! Oh well.
I've made a proof-of-concept implementation for on approach to this: https://github.com/tangrams/tangram-es/commit/2cec9e5496a57dab624286e56011b40bf0bee932
This samples a square area of the framebuffer with a configurable size and returns the most common (non-zero) color in that area. The sampled area could be further refined into a circle or ellipse. This works alright, and does allow selecting some features when your mouse is just a little bit off. However, it has problems. Mainly, small selectable features surrounded by larger selectable features can actually be harder to select! In an extreme case, a feature whose area on screen is less than half of the area sampled could be impossible to select.
The next approach I want to try is to sample a configurable area of the framebuffer and return the first non-zero color that is closest to the center of the selection area. This will still cover some "near-miss" scenarios but will also allow selecting arbitrarily small features.


Fix disabled cursor mode over remote desktop

There were two major issues:

RDP uses MOUSE_MOVE_ABSOLUTE for its input events, and the
implementation of this was incorrect.  Although poorly documented,
the values actually range from 0-65535 and represent monitor positions,
instead of being positions beforehand.  The equally poorly documented
MOUSE_VIRTUAL_DESKTOP flag specifies whether or not to use the
SCREEN or VIRTUALSCREEN system metrics.

Using SetCursor(NULL) causes SetCursorPos to behave incorrectly
over RDP; it doesn't actually move it on the connected machine.
This has been fixed by creating an invisible cursor, which does
get moved correctly.

Aside from that, the center of the window is now cached and the cursor
test now supports pressing M to move the cursor to the center.
Fixes #1276.

This is closed with the merge of #2431 in https://github.com/glfw/glfw/commit/c8521b7fda997a9d8c0a1e03ede3cf9f942d3d2e. Many thanks for the bug report and PR.


[WFCORE-5135] Add a test case to verify that banned modules are not provisioned

Jira issue: https://issues.redhat.com/browse/WFCORE-5135

Core - Full Integration Build 9978 outcome was UNKNOWN using a merge of<PHONE_NUMBER>6d22519baba0e528b5d10675074105
Summary: Canceled (Tests passed: 4262, ignored: 75; exit code 143 (Step: Build & test full (Maven)) (new)) Build time: 01:07:52

Core - Full Integration Build 9931 outcome was UNKNOWN using a merge of<PHONE_NUMBER>6d22519baba0e528b5d10675074105
Summary: Canceled (Tests passed: 3429, ignored: 27; exit code 143 (Step: Build & test full (Maven)) (new)) Build time: 01:22:23

I think some kind of scoping mechanism is needed.  For example, the org.jboss.as.security module is not banned in all contexts, only in most.  We actually have a legacy-security layer that explicitly provides it and it's valid to include that layer in combination with others in an overall config being tested.

Yes right Brian, I've just added such possibility. The idea is to be able to configure a banned module and a list of expected installations where that module can be found.
I don't like so much such coupling between the pom.xml declaration where the layer is provisioned and the test itself though, but it should work as it is.
It forces us to always have at least a provision of each new layer in isolation, which sounds very reasonable to me, at least for full, where the provision that installs a server with all the layers together should be ignored due to legacy-security

Core - Full Integration Build 9933 outcome was UNKNOWN using a merge of 4e3acaf69462ab915091715ffcc5750cd315a982
Summary: Canceled (Tests passed: 3448, ignored: 27; exit code 143 (Step: Build & test full (Maven)) (new)) Build time: 01:30:40


[Snyk] Upgrade @mui/material from 5.14.17 to 5.14.18

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @mui/material from 5.14.17 to 5.14.18.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 22 days ago, on 2023-11-14.

Release notes

Package name: @mui/material

5.14.18 - 2023-11-14 Read more

5.14.17 - 2023-11-06Nov 6, 2023
A big thanks to the 12 contributors who made this release possible.
This release was mostly about 🐛 bug fixes and 📚 documentation improvements.
<EMAIL_ADDRESS>
[Dialog] Should not close until the IME is cancelled (#39713) @ megos
[InputBase] Add sx type to input and root slot (#39569) @ sai6855

<EMAIL_ADDRESS>
[ModalDialog] Remove redundant code (#39719) @ sai6855
[ToggleButtonGroup] Fix toggling button state when Button is not immediate children (#39571) @ sai6855

<EMAIL_ADDRESS>
Make list components more reliable (#39380) @ michaldudak

<EMAIL_ADDRESS>
[InputBase] InputBase slotProps accepts sx type (#39714) @ mj12albert
[OutlinedInput] Copy v5 OutlinedInput (#39698) @ mj12albert

<EMAIL_ADDRESS>
[TreeView] Remove tree view import from @ mui/lab (#39685) @ alexfauquette

Docs

Update Taiwan country name in demos (#39729) @ chiahao
Update release doc for unchanged packages (#39487) @ brijeshb42
[joy-ui] Make code readable to set next color in color inversion demos (#39669) @ ZeeshanTamboli
[material-ui] Remove numeric input workaround from TextField docs (#39629) @ mj12albert
[material-ui] Add comment about code to be removed from Drawer demo (#39678) @ samuelsycamore

Core

[docs-infra] Fix path bloat client-side (#39708) @ oliviertassinari
[docs-infra] Render footer in SSR (#39710) @ oliviertassinari
[docs-infra] Simplify footer (#39709) @ oliviertassinari
[docs-infra] Fix dark theme color (#39720) @ alexfauquette
[docs-infra] Remove the design feedback alert (#39691) @ danilo-leal
[docs-infra] Bring back scroll gradient in API page with table (#39689) @ alexfauquette
[docs-infra] Clarify the content of the ads @ oliviertassinari
[docs-infra] Link to ScaffoldHub v2 @ oliviertassinari
[docs-infra] Improve access to the component demos via the API page (#39690) @ danilo-leal
[docs-infra] Add appropriate aria-label to docs buttons (#39638) @ danilo-leal
[docs-infra] Fix crawler on API pages (#39490) @ alexfauquette
[docs–infra] Small polish on API toggle (#39704) @ oliviertassinari
[core] Speed up the CI by removing the second build (#39684) @ michaldudak
[core][docs] Fix broken MUI System link in README.md (#39734) @ samuelsycamore
[website] List benefits for sponsors (#39640) @ oliviertassinari
[website] Add Vadym teamMember card to 'About' (#39701) @ hasdfa
[test] Fix flaky screenshot (#39711) @ oliviertassinari

All contributors of this release in alphabetical order: @ alexfauquette, @ brijeshb42, @ chiahao, @ danilo-leal, @ hasdfa, @ megos, @ michaldudak, @ mj12albert, @ oliviertassinari, @ sai6855, @ samuelsycamore, @ ZeeshanTamboli

    from @mui/material GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (b476a02) 78.22% compared to head (da60039) 78.22%.
 Consider uploading reports for the commit 41c656b to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1957   +/-   ##
=======================================
  Coverage   78.22%   78.22%
=======================================
  Files          39       39
  Lines        3068     3068
  Branches      619      619
=======================================
  Hits         2400     2400
  Misses        488      488
  Partials      180      180

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add support for inheriting hooks

This PR implements support for inheriting hooks defined in ancestors.
A previous PR has also targeted this issue; however, that solution does not support hooks declared in ancestors at runtime. This solution does:
class ParentInteractor
  include Interactor
end

class ChildInteractor < ParentInteractor
end

ParentInteractor.before do
  puts "Before in parent"
end

ChildInteractor.call
=> "Before in parent"

I had to move around the internals of the Hooks module a bit to make this work, which might break things, should people attempt to mutate the values of #around_hooks, #before_hooks and #after_hooks in their applications. I hope this is acceptable if we target this fix for the next major version, which seems to be 4.0.
Let me know if I'm missing anything.
Fixes: #114

Could you review this if you get a chance? @gaffneyc @danielmorrison

This is really nice, and I'd support seeing this merged as well.

Sorry that it's taken so long to get eyes on this. I think this looks good and it's tentatively slated for 4.0 since it's a possible breaking change. No word on exactly when that will be but it's something I'm working toward as time permits.


PHOENIX-6163 Move CI to ASF Jenkins for connectors

post-commit job and Yetus for GitHub PR

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
docker
0m  3s
Dockerfile '/home/jenkins/jenkins-agent/workspace/ectors-PreCommit-GitHub-PR_PR-32/yetus-general-check/src/dev/docker/Dockerfile.yetus' not found.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/phoenix-connectors/pull/32

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-32/1/console

versions
git=2.17.1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

This is now on par with solution in core, including all addendums.

I see that most of this change has been copied from Phoenix core, it seems to be well adapted to Phoenix-connectors.
I found some comments that could be updated as well, in dev/jenkins_precommit_github_yetus.sh line num 71 and dev/phoenix-connectors-personality.sh 142, 143? 207, 232, 253.
Otherwise this change looks good to me.

Thank you. I have updated the comments.


[Autocomplete] cursor resets highlighted item when using arrow keys

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
I begin with my mouse hovering over the first item. When I reach the bottom of the list (navigating via d-pad), the final down keypress results in The Godfather, the second item in the list, being selected (due to mouse hover).
https://mui.com/components/autocomplete/#combo-box

Expected behavior 🤔
Expected behavior is for the mouse to not interfere with the highlighted selection while using the d-pad. Here's an example of jQuery's autocomplete component.
https://jqueryui.com/autocomplete/#maxheight

Steps to reproduce 🕹
Steps:

Go to https://mui.com/components/autocomplete/#combo-box
Open autocomplete, hover over first item
Navigate down using d-pad
Once scrolling occurs, the highlighted item is erroneously selected

Context 🔦
It increases the difficulty of using the autocomplete component. The user has to to move their cursor for the arrow keys to function as expected.
Your environment 🌎
Repro'ed from docs site-- N/A

This indeed could be considered a bug, but I would say it's low priority. Firstly, the workaround is pretty simple (moving the mouse). Secondly, we are working on a change in Autocomplete internals that will be free of this issue. It likely won't be released before the next major version, though.
We may reconsider working on it in v5 if we see a significant need for it in the community (measured by upvotes on this issue).


Type error in Pylance that's not present in Pyright

Environment data

Language Server version: 2021.8.0
OS and version: macOS 11.5.1
Python version (& distribution if applicable, e.g. Anaconda): miniconda 3.9.4

Expected behaviour
Passing a Tensor to a TensorType should raise no error or warning, and Pyright does this correctly.  Pylance however flags it as an error.
Actual behaviour
In vscode, this code
import torch
from torchtyping import TensorType

def f(a: TensorType):
    pass

f(torch.zeros(()))

gives a Argument of type "Tensor" cannot be assigned to parameter "a" of type "TensorType" in function "f"   "Tensor" is incompatible with "TensorType" warning, but running Pyright directly on the same file (correctly!) gives no error:
No configuration file found.
No pyproject.toml file found.
stubPath /Users/andy/code/tmp/typings is not a valid directory.
Assuming Python platform Darwin
Searching for source files
Found 1 source file
0 errors, 0 warnings, 0 infos
Completed in 0.709sec

Here's a full copy of the warning in vscode:
{
	"resource": "/Users/andy/code/tmp/test.py",
	"owner": "_generated_diagnostic_collection_name_#1",
	"code": {
		"value": "reportGeneralTypeIssues",
		"target": {
			"$mid": 1,
			"external": "https://github.com/microsoft/pylance-release/blob/main/DIAGNOSTIC_SEVERITY_RULES.md#diagnostic-severity-rules",
			"path": "/microsoft/pylance-release/blob/main/DIAGNOSTIC_SEVERITY_RULES.md",
			"scheme": "https",
			"authority": "github.com",
			"fragment": "diagnostic-severity-rules"
		}
	},
	"severity": 8,
	"message": "Argument of type \"Tensor\" cannot be assigned to parameter \"a\" of type \"TensorType\" in function \"f\"\n  \"Tensor\" is incompatible with \"TensorType\"",
	"source": "Pylance",
	"startLineNumber": 7,
	"startColumn": 3,
	"endLineNumber": 7,
	"endColumn": 18
}

Logs
Pylance logs, and then pyright --verbose logs below:
[Info  - 10:49:06] Pylance language server 2021.8.0 (pyright dfb796d8) starting
[Info  - 10:49:06] Server root directory: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist
[Info  - 10:49:06] Background analysis(1) root directory: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist
[Info  - 10:49:06] Background analysis(1) started
[Info  - 10:49:06] Loading configuration file at /Users/andy/code/tmp/pyrightconfig.json
[Info  - 10:49:06] Assuming Python version 3.9
[Info  - 10:49:06] Assuming Python platform Darwin
[Info  - 10:49:06] No include entries specified; assuming /Users/andy/code/tmp
[Info  - 10:49:06] Setting pythonPath for service "tmp": "/Users/andy/code/tmp/.env/bin/python"
[Warn  - 10:49:06] stubPath /Users/andy/code/tmp/typings is not a valid directory.
Search paths for /Users/andy/code/tmp
  /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib
  /Users/andy/code/tmp
  /Users/andy/code/tmp/typings
  /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stubs/...
  /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/bundled/stubs
  /Users/andy/code/tmp/.env/lib/python3.9
  /Users/andy/code/tmp/.env/lib/python3.9/lib-dynload
  /Users/andy/code/tmp/.env/lib/python3.9/site-packages
[Info  - 10:49:06] Searching for source files
[Info  - 10:49:06] Found 1 source file
Background analysis message: setConfigOptions
Background analysis message: ensurePartialStubPackages
Background analysis message: setTrackedFiles
Background analysis message: markAllFilesDirty
Background analysis message: analyze
[BG(1)] parsing: /Users/andy/code/tmp/test.py [fs read 2ms] (14ms)
[BG(1)] parsing: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 2ms] (50ms)
[BG(1)] binding: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/builtins.pyi (19ms)
[BG(1)] binding: /Users/andy/code/tmp/test.py (0ms)
[BG(1)] indexing: /Users/andy/code/tmp/test.py [found 1] (0ms)
Indexing Done: /Users/andy/code/tmp/test.py
[Info  - 10:49:06] Indexer background runner(2) root directory: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist
[Info  - 10:49:06] Indexing(2) started
[IDX(2)] index libraries /Users/andy/code/tmp ...
[IDX(2)]   read stdlib indices (46ms)
[IDX(2)]   scan packages [found 21 modules over 1 exec env] (84ms)
[IDX(2)]   index execution environment /Users/andy/code/tmp ...
[IDX(2)]     parsing: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stubs/certifi/certifi.pyi [fs read 0ms] (15ms)
[IDX(2)]     parsing: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 1ms] (34ms)
[IDX(2)]     binding: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/builtins.pyi (5ms)
[IDX(2)]     binding: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stubs/certifi/certifi.pyi (0ms)
[IDX(2)]     indexing: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stubs/certifi/certifi.pyi [found 1] (0ms)
[IDX(2)]     parsing: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stubs/jmespath/jmespath/__init__.pyi [fs read 2ms] (5ms)
[IDX(2)]     binding: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stubs/jmespath/jmespath/__init__.pyi (0ms)
[IDX(2)]     indexing: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stubs/jmespath/jmespath/__init__.pyi ...
[IDX(2)]       parsing: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/bundled/stubs/jmespath/__init__.pyi [fs read 0ms] (2ms)
[IDX(2)]       binding: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/bundled/stubs/jmespath/__init__.pyi (0ms)
[IDX(2)]       parsing: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/bundled/stubs/jmespath/visitor.pyi [fs read 0ms] (1ms)
[IDX(2)]       binding: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/bundled/stubs/jmespath/visitor.pyi (0ms)
[IDX(2)]     indexing: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stubs/jmespath/jmespath/__init__.pyi [found 4] (3ms)
[IDX(2)]     parsing: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stubs/setuptools/pkg_resources/__init__.pyi [fs read 1ms] (9ms)
[IDX(2)]     binding: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stubs/setuptools/pkg_resources/__init__.pyi (1ms)
[IDX(2)]     indexing: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stubs/setuptools/pkg_resources/__init__.pyi [found 70] (0ms)
[IDX(2)]     parsing: /Users/andy/code/tmp/.env/lib/python3.9/xml/__init__.py [fs read 0ms] (0ms)
[IDX(2)]     binding: /Users/andy/code/tmp/.env/lib/python3.9/xml/__init__.py (0ms)
[IDX(2)]     indexing: /Users/andy/code/tmp/.env/lib/python3.9/xml/__init__.py [found 0] (0ms)
[IDX(2)]     parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/pip/__init__.py [fs read 0ms] (0ms)
[IDX(2)]     binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/pip/__init__.py (0ms)
[IDX(2)]     indexing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/pip/__init__.py [found 2] (0ms)
[IDX(2)]     parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/setuptools/__init__.py [fs read 0ms] (6ms)
[IDX(2)]     binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/setuptools/__init__.py (1ms)
[IDX(2)]     indexing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/setuptools/__init__.py ...
[IDX(2)]       parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/setuptools/_deprecation_warning.py [fs read 0ms] (0ms)
[IDX(2)]       binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/setuptools/_deprecation_warning.py (0ms)
[IDX(2)]       parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/setuptools/extension.py [fs read 0ms] (1ms)
[IDX(2)]       binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/setuptools/extension.py (0ms)
[IDX(2)]       parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/setuptools/dist.py [fs read 0ms] (16ms)
[IDX(2)]       binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/setuptools/dist.py (0ms)
[IDX(2)]       parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/setuptools/depends.py [fs read 1ms] (2ms)
[IDX(2)]       binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/setuptools/depends.py (0ms)
[IDX(2)]     indexing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/setuptools/__init__.py [found 8] (20ms)
[IDX(2)]     parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/__init__.py [fs read 0ms] (20ms)
[IDX(2)]     binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/__init__.py ...
[IDX(2)]       parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_C/__init__.pyi [fs read 1ms] (32ms)
[IDX(2)]       binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_C/__init__.pyi (4ms)
[IDX(2)]       parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_C/_VariableFunctions.pyi [fs read 1ms] (32ms)
[IDX(2)]       binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_C/_VariableFunctions.pyi (15ms)
[IDX(2)]       parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/functional.py [fs read 0ms] (4ms)
[IDX(2)]       binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/functional.py (0ms)
[IDX(2)]     binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/__init__.py (91ms)
[IDX(2)]     indexing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/__init__.py ...
[IDX(2)]       parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_tensor.py [fs read 0ms] (2ms)
[IDX(2)]       binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_tensor.py (0ms)
[IDX(2)]       parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/random.py [fs read 1ms] (1ms)
[IDX(2)]       binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/random.py (0ms)
[IDX(2)]       parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/serialization.py [fs read 1ms] (3ms)
[IDX(2)]       binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/serialization.py (0ms)
[IDX(2)]       parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_tensor_str.py [fs read 1ms] (2ms)
[IDX(2)]       binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_tensor_str.py (0ms)
[IDX(2)]       parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_lowrank.py [fs read 0ms] (1ms)
[IDX(2)]       binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_lowrank.py (0ms)
[IDX(2)]       parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/autograd/__init__.py [fs read 1ms] (2ms)
[IDX(2)]       binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/autograd/__init__.py (0ms)
[IDX(2)]       parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/autograd/grad_mode.py [fs read 0ms] (1ms)
[IDX(2)]       binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/autograd/grad_mode.py (0ms)
[IDX(2)]       parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_lobpcg.py [fs read 0ms] (2ms)
[IDX(2)]       binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_lobpcg.py (0ms)
[IDX(2)]     indexing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/__init__.py [found 846] (19ms)
[IDX(2)]     parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/typeguard/__init__.py [fs read 0ms] (6ms)
[IDX(2)]     binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/typeguard/__init__.py (0ms)
[IDX(2)]     indexing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/typeguard/__init__.py [found 36] (1ms)
[IDX(2)]   index execution environment /Users/andy/code/tmp [found 8885 in 428 files] (244ms)
[IDX(2)] index libraries /Users/andy/code/tmp [found 8885 in 1 exec envs] (376ms)
[Info  - 10:49:07] Indexer done(2). indexed 428 files
Background analysis message: setFileOpened
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
[FG] parsing: /Users/andy/code/tmp/test.py (24ms)
[FG] parsing: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 2ms] (57ms)
[FG] binding: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/builtins.pyi (22ms)
[FG] binding: /Users/andy/code/tmp/test.py (0ms)
Background analysis message: getSemanticTokens full
[BG(1)] getSemanticTokens full at /Users/andy/code/tmp/test.py ...
[BG(1)]   parsing: /Users/andy/code/tmp/test.py (1ms)
[BG(1)]   parsing: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 0ms] (47ms)
[BG(1)]   binding: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/builtins.pyi (21ms)
[BG(1)]   binding: /Users/andy/code/tmp/test.py (1ms)
[BG(1)]   parsing: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/typing.pyi [fs read 0ms] (17ms)
[BG(1)]   binding: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/typing.pyi (6ms)
[BG(1)]   parsing: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi [fs read 1ms] (3ms)
[BG(1)]   binding: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi (1ms)
[BG(1)]   parsing: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/typing_extensions.pyi [fs read 0ms] (2ms)
[BG(1)]   binding: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/typing_extensions.pyi (1ms)
[BG(1)]   parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/__init__.py [fs read 0ms] (28ms)
[BG(1)]   binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/__init__.py ...
[BG(1)]     parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_C/__init__.pyi [fs read 1ms] (62ms)
[BG(1)]     binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_C/__init__.pyi (27ms)
[BG(1)]     parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_C/_VariableFunctions.pyi [fs read 18ms] (52ms)
[BG(1)]     binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_C/_VariableFunctions.pyi (39ms)
[BG(1)]     parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/functional.py [fs read 0ms] (16ms)
[BG(1)]     binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/functional.py (2ms)
[BG(1)]   binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/__init__.py (205ms)
[BG(1)]   parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torchtyping/__init__.py [fs read 0ms] (0ms)
[BG(1)]   binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torchtyping/__init__.py (0ms)
[BG(1)]   parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torchtyping/tensor_type.py [fs read 0ms] (2ms)
[BG(1)]   binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torchtyping/tensor_type.py (1ms)
[BG(1)]   parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_tensor.py [fs read 0ms] (11ms)
[BG(1)]   binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_tensor.py (3ms)
[BG(1)]   parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/types.py [fs read 0ms] (1ms)
[BG(1)]   binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/types.py (0ms)
[BG(1)] getSemanticTokens full at /Users/andy/code/tmp/test.py (375ms)
Background analysis message: getSemanticTokens range
[BG(1)] getSemanticTokens range 0:0 - 7:0 at /Users/andy/code/tmp/test.py (1ms)
Background analysis message: analyze
[BG(1)] analyzing: /Users/andy/code/tmp/test.py ...
[BG(1)]   checking: /Users/andy/code/tmp/test.py (1ms)
[BG(1)] analyzing: /Users/andy/code/tmp/test.py (1ms)
Background analysis message: resumeAnalysis
[BG(1)] indexing: /Users/andy/code/tmp/test.py [found 1] (0ms)
Indexing Done: /Users/andy/code/tmp/test.py
[FG] parsing: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/typing.pyi [fs read 1ms] (17ms)
[FG] binding: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/typing.pyi (7ms)
[FG] parsing: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi [fs read 0ms] (4ms)
[FG] binding: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi (1ms)
[FG] parsing: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/typing_extensions.pyi [fs read 0ms] (1ms)
[FG] binding: /Users/andy/.vscode/extensions/ms-python.vscode-pylance-2021.8.0/dist/typeshed-fallback/stdlib/typing_extensions.pyi (0ms)
[FG] parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torchtyping/__init__.py [fs read 0ms] (0ms)
[FG] binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torchtyping/__init__.py (1ms)
[FG] parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torchtyping/tensor_type.py [fs read 0ms] (5ms)
[FG] binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torchtyping/tensor_type.py (1ms)
[FG] parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/__init__.py [fs read 0ms] (28ms)
[FG] binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/__init__.py ...
[FG]   parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_C/__init__.pyi [fs read 0ms] (41ms)
[FG]   binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_C/__init__.pyi (23ms)
[FG]   parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_C/_VariableFunctions.pyi [fs read 0ms] (42ms)
[FG]   binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_C/_VariableFunctions.pyi (21ms)
[FG]   parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/functional.py [fs read 1ms] (16ms)
[FG]   binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/functional.py (3ms)
[FG] binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/__init__.py (151ms)
[FG] parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_tensor.py [fs read 1ms] (11ms)
[FG] binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/_tensor.py (4ms)
[FG] parsing: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/types.py [fs read 0ms] (0ms)
[FG] binding: /Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/types.py (0ms)
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange
Background analysis message: getDiagnosticsForRange

Pyright:
(/Users/andy/code/tmp/.env) andy@ajones-m1 tmp % pyright --verbose test.py
Loading configuration file at /Users/andy/code/tmp/pyrightconfig.json
Assuming Python version 3.9
Assuming Python platform Darwin
stubPath /Users/andy/code/tmp/typings is not a valid directory.
Search paths for /Users/andy/code/tmp
  /opt/homebrew/lib/node_modules/pyright/dist/typeshed-fallback/stdlib
  /Users/andy/code/tmp
  /Users/andy/code/tmp/typings
  /opt/homebrew/lib/node_modules/pyright/dist/typeshed-fallback/stubs/...
  /Users/andy/code/tmp/.env/lib/python3.9
  /Users/andy/code/tmp/.env/lib/python3.9/lib-dynload
  /Users/andy/code/tmp/.env/lib/python3.9/site-packages
Searching for source files
Found 1 source file
Could not import 'DLFCN' in file '/Users/andy/code/tmp/.env/lib/python3.9/site-packages/torch/__init__.py'
  Looking for typeshed stdlib path
  Attempting to resolve using root path '/opt/homebrew/lib/node_modules/pyright/dist/typeshed-fallback/stdlib'
  Typeshed path not found
  Looking in stubPath '/Users/andy/code/tmp/typings'
  Attempting to resolve using root path '/Users/andy/code/tmp/typings'
  Attempting to resolve using root path '/Users/andy/code/tmp/typings'
  Looking in root directory of execution environment '/Users/andy/code/tmp'
  Attempting to resolve using root path '/Users/andy/code/tmp'
  Attempting to resolve using root path '/Users/andy/code/tmp'
  Looking in python search path '/Users/andy/code/tmp/.env/lib/python3.9'
  Attempting to resolve using root path '/Users/andy/code/tmp/.env/lib/python3.9'
  Attempting to resolve using root path '/Users/andy/code/tmp/.env/lib/python3.9'
  Looking in python search path '/Users/andy/code/tmp/.env/lib/python3.9/lib-dynload'
  Attempting to resolve using root path '/Users/andy/code/tmp/.env/lib/python3.9/lib-dynload'
  Attempting to resolve using root path '/Users/andy/code/tmp/.env/lib/python3.9/lib-dynload'
  Looking in python search path '/Users/andy/code/tmp/.env/lib/python3.9/site-packages'
  Attempting to resolve using root path '/Users/andy/code/tmp/.env/lib/python3.9/site-packages'
  Attempting to resolve using root path '/Users/andy/code/tmp/.env/lib/python3.9/site-packages'
  Looking for typeshed path
  Looking for typeshed stubs path
  Typeshed path not found
0 errors, 0 warnings, 0 infos
Completed in 0.677sec

Code Snippet / Additional information
requirements.txt:
certifi==2021.5.30
torch==1.9.0
torchtyping==0.1.4
typeguard==2.12.1
typing-extensions==<IP_ADDRESS>

As some background, my principle issue here is that params marked TensorType complain about being passed Tensor. As a first step to debugging that I wanted to dive into Pyright, but it appears Pyright treats it correctly. It'd be unfair to ask the Pylance team to debug an issue arising from the interaction between two niche libraries, but I would like to know where this error is coming from so I can chase it up myself.
Making the type of a: int and passing "x" to it throws an error in Pyright, so it's not that Pyright is non-functional!
My Pyright version is 1.1.159, which - looking at the changelog - I believe is the same one that's in Pylance 2021.8.0

There are a couple of things here.
First, the version we list isn't exactly correct, as we usually have a few more changes than exactly that version, and the changelog lists them. It could be that things are different due to a bugfix or change in pyright and we aren't perfectly in sync. Can you try with 1.1.160?
Secondly, Pylance's defaults are different than pyright's, namely that useLibraryCodeForTypes is enabled by default in Pylance but not in pyright; can you make sure that this setting is sent consistently between the two and retry?

useLibraryCodeForTypes reproduces the error! Thank you! I'll go dive into Pyright now then 😁

This can mean multiple things, but largely this would mean that torch isn't fully typed for this function. When that option is disabled, we don't do any inferencing for libraries, so probably end up with an Unknown.
I recommend writing reveal_type(torch.zeros(())) and comparing them with the option both ways to see; I'm betting it will say Unknown or something odd (in which case the fix should be in torch).

Thanks for the tip! Unfortunately it turns out to be Tensor in both cases 🙁 . Some important context here is that TensorType is from the torchtyping library, which adds support for typing the properties of tensors. Very likely there's something about how torchtyping is being clever that's incompatible with Pyright, and I'm keen to figure out what that is and if it can be fixed on the torchtyping side. And the first step in that direction was getting a direct pyright repo!

If anyone else comes across this by Googling 'vscode' and 'torchtyping', the solution is

Upgrade to torchtyping 0.1.4
Use TensorType[...] rather than TensorType alone.

See this issue for details.


Need additional fixes

The tests are passing locally, I'm guessing it is a version issue, looking into it more

@NikolaR01 I don't think the problem is with the version. test_dfs are global and are accessed by other functions. Thus, you'd want to use the copy in every function if you want to make sure the initial DataFrame shouldn't change.

@bi-kash thanks for the fix


Fix MPU9250 calibration matrix multiplication

Split applying calibration values into 2 loops - first the bias, then the matrix(like for BMI160)
If done in a single loop the matrix multiplication uses uninitialized temp[] values, which is wrong

I have realized #246 exists, which is basically the same thing
Always remember to check existing pulls first -w-

The PR #246 got merged. So feel free to test the main.


Don't use randomly generated IDs in actions

In our storybooks we use seedrandom to seed Math.random because we use them for visual regression. That means that the randomly generated IDs can result in duplicate keys:
Randomly generated id: https://github.com/storybooks/storybook/blob/master/addons/actions/src/preview.js#L16
Use of the ID in a key: https://github.com/storybooks/storybook/blob/master/addons/actions/src/components/ActionLogger/index.js#L22
And we all know how React feels about duplicated keys... 😞
Could a uuid be used instead?

@marcfallows Seems reasonable to me! Wanna make a quick PR?

Happy to raise a PR. Do you have a preference:

Using node-uuid to generate a uuid
Keeping it simple and have a runtime counter

uuid please 👍

Sorry for the delay, finally make a PR for this: https://github.com/storybooks/storybook/pull/1347


Update Ukrainian translation of &versionXIncY and &creationClubPlugins

Translations by @IllusiveMan196

Worth noting is, that the change in &versionXIncY is the deletion of two "Zero Width Space" signs in front of the у, they read E2 80 EB in the hex editor HxD. Discussion took place in the translations channel in Discord.


[Tensorize] Fix compute reusing

As discussed in #7879, this PR fixes the reusing case.

Hi @comaniac, can you please take a short look? :)

Thanks @leeexyz


Google Task extension keeps "login out"

Extension
https://www.raycast.com/elliotdes/google-tasks
Description
After sometime of not using the extension, when I try I get "Bad request" and than I have to do the login process all over again.
Steps To Reproduce

1 week not using the extension
Click to see all tasks
It gives an error "Bad request"
Remove credential
Add credential again
Follow the full set-up
Goes back to work

Current Behaviour
It "logs-out" after some unused time
Expected Behaviour
No response

I believe you need to change the Publishing status under the OAuth consent screen.
It has been awhile since I did this, but I remember GCP would have the OAuth client go bad after a week or so. Once it happened, had to do the above step.


Prometheus goes to a OOM loop and states "unknown series references"

Bug Report
What did you do?
Running prometheus as a docker container on a stand-alone box.
What did you expect to see?
Prometheus running without any issues.
What did you see instead? Under which circumstances?
Prometheus is going in an endless crashing state and getting the below error, once it restarts.
level=warn ts=2019-05-13T09:02:15.270Z caller=head.go:454 component=tsdb msg="unknown series references" count=1085

Environment
Prometheus version:
2.9.2
Alertmanager version: N/A
Prometheus configuration file:
global:
  scrape_interval: 1m
  scrape_timeout: 10s
  evaluation_interval: 1m
scrape_configs:
- job_name: nodeexporter
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  ec2_sd_configs:
  - endpoint: ""
    region: ap-south-1
    refresh_interval: 1m
    port: 9100
    filters: []
  relabel_configs:
  - source_labels: [__meta_ec2_tag_monitoring]
    separator: ;
    regex: "true"
    replacement: $1
    action: keep
  - source_labels: [__meta_ec2_tag_Name]
    separator: ;
    regex: (.*)
    target_label: asg_group
    replacement: $1
    action: replace
- job_name: elasticexporter
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /_prometheus/metrics
  scheme: http
  ec2_sd_configs:
  - endpoint: ""
    region: ap-south-1
    refresh_interval: 1m
    port: 9200
    filters: []
  relabel_configs:
  - source_labels: [__meta_ec2_tag_elasticsearch]
    separator: ;
    regex: "true"
    replacement: $1
    action: keep
- job_name: prod-blue-traefik-external
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - <endpoint>
- job_name: prod-blue-traefik-internal
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - <endpoint>
- job_name: prod-blue-traefik-concierge
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - <endpoint>
- job_name: stage-blue-traefik-external
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - <endpoint>
- job_name: stage-blue-traefik-internal
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - <endpoint>
- job_name: stage-blue-traefik-concierge
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - <endpoint>
- job_name: <env>-green-traefik-external
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - <endpoint>
- job_name: <env>-green-traefik-internal
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - <endpoint>
- job_name: <env>-green-traefik-concierge
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - <endpoint>
- job_name: <env>-blue-traefik-external
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - <endpoint>
- job_name: <env>-blue-traefik-internal
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - <endpoint>
- job_name: <env>-blue-traefik-concierge
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - <endpoint>
- job_name: prod-blue-kube-state-metrics
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: https
  static_configs:
  - targets:
    - <endpoint>
  tls_config:
    insecure_skip_verify: true
- job_name: stage-blue-kube-state-metrics
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: https
  static_configs:
  - targets:
    - <endpoint>
  tls_config:
    insecure_skip_verify: true
- job_name: <env>-green-state-metrics
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: https
  static_configs:
  - targets:
    - <endpoint>
  tls_config:
    insecure_skip_verify: true
- job_name: <env>-blue-state-metrics
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: https
  static_configs:
  - targets:
    - <endpoint>
  tls_config:
    insecure_skip_verify: true
- job_name: prod-blue-kube-cadvisor
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  ec2_sd_configs:
  - endpoint: ""
    region: ap-south-1
    refresh_interval: 1m
    port: 4194
    filters: []
  relabel_configs:
  - source_labels: [__meta_ec2_tag_Name]
    separator: ;
    regex: prod-blue.*
    replacement: $1
    action: keep
- job_name: <env>-green-kube-cadvisor
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  ec2_sd_configs:
  - endpoint: ""
    region: ap-south-1
    refresh_interval: 1m
    port: 4194
    filters: []
  relabel_configs:
  - source_labels: [__meta_ec2_tag_Name]
    separator: ;
    regex: <env>-green.*
    replacement: $1
    action: keep
- job_name: <env>-blue-kube-cadvisor
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  ec2_sd_configs:
  - endpoint: ""
    region: ap-south-1
    refresh_interval: 1m
    port: 4194
    filters: []
  relabel_configs:
  - source_labels: [__meta_ec2_tag_Name]
    separator: ;
    regex: <env>-blue.*
    replacement: $1
    action: keep
- job_name: stage-blue-kube-cadvisor
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  ec2_sd_configs:
  - endpoint: ""
    region: ap-south-1
    refresh_interval: 1m
    port: 4194
    filters: []
  relabel_configs:
  - source_labels: [__meta_ec2_tag_Name]
    separator: ;
    regex: stage-blue.*
    replacement: $1
    action: keep
- job_name: prod-blue-etcd-metrics
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: https
  ec2_sd_configs:
  - endpoint: ""
    region: ap-south-1
    refresh_interval: 1m
    port: 2379
    filters: []
  tls_config:
    insecure_skip_verify: true
  relabel_configs:
  - source_labels: [__meta_ec2_tag_Name]
    separator: ;
    regex: prod-blue-etcd.*
    replacement: $1
    action: keep
- job_name: <env>-green-etcd-metrics
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: https
  ec2_sd_configs:
  - endpoint: ""
    region: ap-south-1
    refresh_interval: 1m
    port: 2379
    filters: []
  tls_config:
    insecure_skip_verify: true
  relabel_configs:
  - source_labels: [__meta_ec2_tag_Name]
    separator: ;
    regex: <env>-green-etcd.*
    replacement: $1
    action: keep
- job_name: <env>-blue-etcd-metrics
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: https
  ec2_sd_configs:
  - endpoint: ""
    region: ap-south-1
    refresh_interval: 1m
    port: 2379
    filters: []
  tls_config:
    insecure_skip_verify: true
  relabel_configs:
  - source_labels: [__meta_ec2_tag_Name]
    separator: ;
    regex: <env>-blue-etcd.*
    replacement: $1
    action: keep
- job_name: stage-blue-etcd-metrics
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: https
  ec2_sd_configs:
  - endpoint: ""
    region: ap-south-1
    refresh_interval: 1m
    port: 2379
    filters: []
  tls_config:
    insecure_skip_verify: true
  relabel_configs:
  - source_labels: [__meta_ec2_tag_Name]
    separator: ;
    regex: stage-blue-etcd.*
    replacement: $1
    action: keep
- job_name: prod-blue-kube-router-metrics
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /kube-router/metrics
  scheme: http
  ec2_sd_configs:
  - endpoint: ""
    region: ap-south-1
    refresh_interval: 1m
    port: 63330
    filters: []
  relabel_configs:
  - source_labels: [__meta_ec2_tag_environment]
    separator: ;
    regex: prod
    replacement: $1
    action: keep
  - source_labels: [__meta_ec2_tag_role]
    separator: ;
    regex: blue
    replacement: $1
    action: keep
- job_name: <env>-green-kube-router-metrics
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /kube-router/metrics
  scheme: http
  ec2_sd_configs:
  - endpoint: ""
    region: ap-south-1
    refresh_interval: 1m
    port: 63330
    filters: []
  relabel_configs:
  - source_labels: [__meta_ec2_tag_environment]
    separator: ;
    regex: cde
    replacement: $1
    action: keep
  - source_labels: [__meta_ec2_tag_role]
    separator: ;
    regex: green
    replacement: $1
    action: keep
- job_name: <env>-blue-kube-router-metrics
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /kube-router/metrics
  scheme: http
  ec2_sd_configs:
  - endpoint: ""
    region: ap-south-1
    refresh_interval: 1m
    port: 63330
    filters: []
  relabel_configs:
  - source_labels: [__meta_ec2_tag_environment]
    separator: ;
    regex:<env>
    replacement: $1
    action: keep
  - source_labels: [__meta_ec2_tag_role]
    separator: ;
    regex: blue
    replacement: $1
    action: keep
- job_name: stage-blue-kube-router-metrics
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /kube-router/metrics
  scheme: http
  ec2_sd_configs:
  - endpoint: ""
    region: ap-south-1
    refresh_interval: 1m
    port: 63330
    filters: []
  relabel_configs:
  - source_labels: [__meta_ec2_tag_environment]
    separator: ;
    regex: stage
    replacement: $1
    action: keep
  - source_labels: [__meta_ec2_tag_role]
    separator: ;
    regex: blue
    replacement: $1
    action: keep
- job_name: push-gateway
  honor_timestamps: true
  scrape_interval: 10m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - localhost:9091
- job_name: prometheus-self
  honor_timestamps: true
  scrape_interval: 15s
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - localhost:9090

System information:
Linux 4.14.11-coreos x86_64

Prometheus version:
2.9.2 (Faced same with 2.7.0)

Alertmanager version:
NA

Logs:

level=warn ts=2019-05-13T08:44:32.392Z caller=head.go:454 component=tsdb msg="unknown series references" count=997
level=info ts=2019-05-13T08:44:50.284Z caller=main.go:655 msg="TSDB started"
level=info ts=2019-05-13T08:44:50.284Z caller=main.go:724 msg="Loading configuration file" filename=/etc/prometheus/prometheus.yaml
level=info ts=2019-05-13T08:44:50.297Z caller=main.go:751 msg="Completed loading of configuration file" filename=/etc/prometheus/prometheus.yaml
level=info ts=2019-05-13T08:44:50.297Z caller=main.go:609 msg="Server is ready to receive web requests."
fatal error: runtime: out of memory

Also the initial start is also taking more than 15 minutes.

It has increased to over 4 lakh in a single day. Need some help here.
level=warn ts=2019-05-14T08:11:04.764Z caller=head.go:454 component=tsdb msg="unknown series references" count=426445

we have the same issue here
level=warn ts=2019-05-28T07:47:55.988Z caller=head.go:454 component=tsdb msg="unknown series references" count=665328

sometimes, it OOMed even we have one machine with a really big memory.

sometimes, it OOMed even we have one machine with a really big memory.

It is happening the same for us as well.

I am also seeing too many tmp files in the tsdb path
ls -la | grep tmp
drwxr-xr-x.  3 root root  4096 Jan 11 19:03 01D0Z4S4WJ00KA5QMFF4P8WG33.tmp
drwxr-xr-x.  3 root root  4096 Jan 28 11:00 01D2A1VC969K0G0TDTJ4X2WCEG.tmp
drwxr-xr-x.  3 root root  4096 Jan 28 13:00 01D2A8Q37JPGS2GR2X2ZNC3A9T.tmp
drwxr-xr-x.  3 root root  4096 Jan 28 13:12 01D2A9DRCQBNJEQ4QFZPVHYXKE.tmp
drwxr-xr-x.  3 root root  4096 Jan 29 19:04 01D2DFYY5MC1PVG0VAZCT98SZJ.tmp
drwxr-xr-x.  3 root root  4096 Jan 30 13:01 01D2FDKX4774BWQPEXE7DQJHG5.tmp
drwxr-xr-x.  3 root root  4096 Jan 30 13:05 01D2FDT716C98N5HZABEC3BEED.tmp
drwxr-xr-x.  3 root root  4096 Jan 30 13:08 01D2FE0C1J2YPPA4RZY40KCMG9.tmp
drwxr-xr-x.  3 root root  4096 Jan 30 13:12 01D2FE6NTTFEVW73KF6EWYWQAN.tmp
drwxr-xr-x.  3 root root  4096 Jan 30 13:15 01D2FEDCGEQ7MS1RZK9EP09ZG4.tmp
drwxr-xr-x.  3 root root  4096 Jan 30 13:19 01D2FEKR330THYYZ12QNGJ9KXD.tmp
drwxr-xr-x.  3 root root  4096 Jan 30 13:22 01D2FETG24VEV57N09SEZP0FWH.tmp
drwxr-xr-x.  3 root root  4096 Jan 30 13:26 01D2FF1B32JQH47ZD7XCVV0MZT.tmp
drwxr-xr-x.  3 root root  4096 Jan 30 13:30 01D2FF7RS410P19BF6WWA6GT5N.tmp
drwxr-xr-x.  3 root root  4096 Jan 31 11:01 01D2HS464Z1FJE2Q1X44V24690.tmp
drwxr-xr-x.  3 root root  4096 Jan 31 13:03 01D2J033MNQJ23T8660W4DD5QK.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 07:00 01D2S2HZ2K9TJ3HST0CWV44HWY.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 07:04 01D2S2R1TNNTGSPN8MTJFD1XYM.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 07:07 01D2S2XZFFW28EQXVEACE6J4AX.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 07:11 01D2S34D02RXSYF8EQBQK1AV0W.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 07:14 01D2S3AV01N98VB3MK2C3DZHQD.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 07:17 01D2S3H4NCFQMMNV55S9YWTREQ.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 07:21 01D2S3QGV78FA3WJ2GRWTAAK6S.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 07:24 01D2S3XZD985SQ7RVACD3HJDKQ.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 07:28 01D2S44E26WR5MHB59B4DNBDA9.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 07:32 01D2S4AW8HDSQQBF3FW5PR62E6.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 07:35 01D2S4HA5WT6QRRWP7KA1K1Q3R.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 07:38 01D2S4QKGHWP6GGSNQ4448FWQW.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 07:42 01D2S4XYWT2R2MS8QHKHBRRAZT.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 07:46 01D2S54JJA7NNRX1S67GPBWVSF.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 07:49 01D2S5AB1M5AEMCW3GYWD343GF.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 07:52 01D2S5GTWVWNRGM2NQDYST6ASN.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 07:56 01D2S5Q8W0RFVQ6HNH6BM4XAK3.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 07:59 01D2S5XQ2BRSHV1JF5HZA7MQXQ.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 08:03 01D2S6417QRFQW4RF9FR1CZEYK.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 08:06 01D2S6ADTZZ0K3KG1881AG534H.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 08:10 01D2S6GYPHCX1GF41VQK62SRDH.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 08:13 01D2S6Q22QXMYDERAPCKESXNBN.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 08:17 01D2S6XA1D2ZFSTJQJDF5P6XGN.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 08:20 01D2S73D9DMRXX6J6P1NVQCVWQ.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 08:23 01D2S79HKTB24CGFGTS778MNNV.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 08:27 01D2S7FW4K5X51TNWPE5GW88VP.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 08:31 01D2S7QXB735588224PQMMM6WF.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 08:35 01D2S7Y8Y7NWF221GGD1FAFTE9.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 08:38 01D2S84NVSNYRYFN3XBKJDD7VZ.tmp
drwxr-xr-x.  3 root root  4096 Feb  3 08:42 01D2S8BCKH74FSRG84EF7VNQS1.tmp
drwxr-xr-x.  3 root root  4096 Mar  1 09:00 01D4W7PMX55CDDC7B8WTQ5RBHQ.tmp
drwxr-xr-x.  3 root root  4096 Mar  8 09:00 01D5E8FNWWN2HPYTNB3TV3RNWM.tmp
drwxr-xr-x.  3 root root  4096 Mar 13 11:00 01D5VBB07WTFS1H12YSVPSPS31.tmp
drwxr-xr-x.  3 root root  4096 Mar 18 17:03 01D68W3FBKJAH13N6ZBEVP1C87.tmp
drwxr-xr-x.  3 root root  4096 May 10 13:00 01DAGX8D5F6RMNC816YTQ2EAQS.tmp
drwxr-xr-x.  3 root root  4096 May 10 13:53 01DAH0AQVZ2WDFEJ2WTCVE41RC.tmp
drwxr-xr-x.  3 root root  4096 May 10 14:09 01DAH17DPRGFSC843GCE3AYS5A.tmp
drwxr-xr-x.  3 root root  4096 May 10 14:25 01DAH25Q8QQNZ99KP8MKAH5JFZ.tmp
drwxr-xr-x.  3 root root  4096 May 10 14:42 01DAH345CAJTYZZ2E7SRTW5B25.tmp
drwxr-xr-x.  3 root root  4096 May 10 14:58 01DAH420TNJA3Q8GK1ANJW67A0.tmp

Our retention time is for 30d, don't know why these files are there and if this is causing things to break.

@brian-brazil @simonpasquier Can you guys plz help us here. Sorry for the direct tag.

Having the same issue with version 2.8.

Anyone able to get along with this. This is resulting into high startup times.

Hi, does anyone tried 2.11.1 as recommended in prometheus/tsdb#590 ?

Yes, tried this today. Still getting similar errors.

Is this fixed in a specific version? We were just hit by this in production, running v2.11.1.

This has not been fixed, generally if Prometheus OOMs once, it is very possible that it will OOM again shortly after starting up as it replays all the previous state back into memory. Without losing data it will be challenging to fix that issue unless you increase the memory Prometheus has access to after an OOM.
Prometheus v2.12.0 has some improvements around this such as general memory improvements inside of tsdb, and logging to help see the WAL replay progress (generally what is causing the long startup times). There has been some discussion on ways to improve the WAL startup time as well, but no work has been merged yet. One example is: https://github.com/prometheus/prometheus/pull/6059.

Thank you for the quick response! I'll investigate the issue some more tomorrow and if I find anything relevant I'll share it here.
We're running in Kubernetes with rather huge memory limits + low retention so I am a bit surprised that it OOMd.

Was hit by this too with v2.11.1 in production cluster. One Prometheus pod's memory usage gets very high at times although in our case the pod's not OOM killed, but it caused the node to go down and the node have to be restarted. Since the pod can't start due to component=tsdb msg="unknown series references" count errors, we decided to start fresh and erase the existing database.

Hi we've looked at this in our bug scrub and decided to close this. We've since fixed the "unknown series references" issue and the OOM loop indicates not enough memory.


Intellisense stopped working after latest update

Editing chunks of codes of different languages has become impossible.

/needsMoreInfo


Bar Labels in Group Bar Chart

Hi all. I'm using Group Bar Chart and I need to add Bar Label Layer - to display label above each bar. Can somebody help me? How do I find chartPoints for this layer in Group Bar Chart (I am using code form example).
Thank you!

Hmm, well, the grouped bars layer currently doesn't have anything to retrieve directly the screen coordinates of the groups and elements. Pull request? :) You can create your own layer as a copy of the grouped bars layers and do the necessary changes.
Other than that, you have already the y-coordinate (in the case of vertical bars, otherwise x) of the bars in the models, which would be the the y coordinate of the chart points, can pass an unused value as x coordinate and, using the index, do the maths based on how many groups you have, your bar width/spacing settings, etc. to calculate the screen x coordinate in the generator. This is is rather ugly workaround though and the best would be to have convenient accessors to retrieve this from the layer.

I tried to create copy of ChartPointsBarGroup with changes but I probably made wrong changes or I'm not sure what exactly should I change. Could you please help me to find what changes should I do? :) Thank you.

Just "remembering" the generated groups / bars and offer convenient accessors for things like getting the screen position of the bars, the center of the group. etc.

Just for the record, there's now GroupedBarsCompanionsLayer which can be used for this.


alternative names in glottolog-cldf?

Will alternative names of languoids ever be included in future glottolog-cldf releases? It could be either in the languages table or values.

+1 I also came here to ask this question.

I think an additional table would be the best solution here, something like names.csv

Glottocode
Name
provider
lang

abcd1234
Sprache
someone
de

Sure thing, sounds good to me. As long as it's in there somewhere :)


Unify internal observability documentation - 3 of 3

This PR is the last of three. Together they will create a new internal observability document on opentelemetry.io, combining and migrating multiple markdown files from the Collector repo. This PR covers the section on monitoring the Collector with internal telemetry.
The Collector repo documents have some overlap between monitoring and troubleshooting, and this PR makes changes to both of those sections on the website.
Link to tracking issue: https://github.com/open-telemetry/opentelemetry-collector/issues/8886. (Not triggering a closure on this until I can update/remove the Collector repo docs.)
Also fixes #3894.
Also relates to:

#4192. For ease of review, this larger PR is being split into three smaller ones.
#4246
#4322

Previews:
Monitoring
Troubleshooting

Still working on copy edits. I hope to move it out of draft mode tomorrow, but there's a good chance it won't happen until after the US holiday on Monday.

Ready for review. I flagged one section that I'm having trouble with. Thanks!

@open-telemetry/collector-approvers PTAL

/fix:format

@open-telemetry/collector-approvers, does anyone have time to give this PR a look?
It's a pretty straightforward transfer and edit of the content from the Collector repo docs. And I've pointed out one section that might need some extra work. Thanks!

Hi @mx-psi, @svrnm: I think this one is ready to go. Thanks!

🚀 You did it! Wohoo!


Cannot run migrations with RemoteUserOpenIdConnectProfile

Running all migrations from an initial state using the RemoteUserOpenIdConnectProfile is unsuccessful.
The order of migrations 0001, 0002 and 0003 and dependencies on the OpenIdConnectProfile make it impossible to successfully run all migrations.

I've this issue too when try to migrate using RemoteUserOpenIdConnectProfile and local user storage.
django.db.utils.ProgrammingError: relation "django_keycloak_openidconnectprofile" does not exist
Is there any workaround for this issue?

I too (

@Malinich I forked the project and created new migrations.

@bossan Will you be opening a PR for the new migrations?

Can someone share the sql definition of table django_keycloak_remoteuseropenidconnectprofile? I'll have to create it manually to be able to use remote user mode.

I'm still having this issue, I think it is because here the RemoteUserOpenIdConnectProfile.Meta is inheriting the abstract flag, and if you have KEYCLOAK_OIDC_PROFILE_MODEL = 'django_keycloak.RemoteUserOpenIdConnectProfile' set it will never create the django_keycloak_remoteuseropenidconnectprofile. is there a specific reason why it should be abstract?

to repair the migrations, it would be interesting to reset and do the --fake-initial, that way it would solve without generating so many complications

I am also stuck on this issue, I get the following error when trying to run a migration:
django.db.utils.ProgrammingError: relation "django_keycloak_openidconnectprofile" does not exist

I was struggling with the same error, but I fixed it as below.
Delete or comment on lines related to the 'remote user', and migrate again.
After the migration, just roll back the lines, and it works.
KEYCLOAK_OIDC_PROFILE_MODEL = 'django_keycloak.RemoteUserOpenIdConnectProfile'
MIDDLEWARE = [
...
'django_keycloak.middleware.BaseKeycloakMiddleware',
'django_keycloak.middleware.RemoteUserAuthenticationMiddleware',
]
KEYCLOAK_REMOTE_USER_MODEL = 'django_keycloak.remote_user.KeycloakRemoteUser'


Updated workflow to reflect registration of ClimaCore

Since ClimaCore.jl is now registered, we should be able to treat it like any other package in our GH workflows.

bors try


⚠ RPC server - Harmony Test has degraded performance

In 80b5690, RPC server - Harmony Test ($HARMONY_TEST_RPC_URL) experienced degraded performance:

HTTP code: 0
Response time: 0 ms

Resolved: RPC server - Harmony Test performance has improved in 140a277.


Add logos to home page

right now its not very clear that the home has links to other websites. We should add the logos we have

Just visited your website, and I agree that it's not obvious that the headings Academy, Community, NMDA and Open Publishing are links as they don't have the same color as the other links.


Clarify source of API docs

Signed-off-by: Q<EMAIL_ADDRESS>Arose whilst trying to fix issue #237

/ok-to-test

Wow, I'd not seen this before and I really like the idea of adding this. I was caught out by this more than once when I started contributing to cert-manager!
Unfortunately we've got a new website refresh coming up and since this PR has been open for so long (sorry about that) I don't think it'll make sense in the refreshed version (and I'd actually like to always check in the generated docs just so there's something in the repo).
As such I'm going to close this, but thanks again @TheEnbyperor  - really great idea and I love the thought behind it!