auto-suggestions

i would like a feature that would give you suggestions on the code your typing.
(i tried implenting this on my own and it failed. what i did was basically access the language module and then keep checking if something is similar and then when the user presses TAB it autocompletes it. the cons of whatever i just said is that it does not care if the use is indexing a table). Sorry for bothering and thanks :D

This is a syntax highlighting module. Implementing auto complete is out of scope for this project. This isn't a code editor, it's a highlighter.


Features Request: Limit Simultaneous Speed Tests and Prevent Abuse

Hi again @openspeedtest,
I am proposing two new features: the ability to limit the number of simultaneous speed tests that can be run, and the ability to set a daily limit on the number of speed tests that can be run from a single IP address.
Limiting the number of simultaneous speed tests would ensure that all users can get a fair and accurate measurement of their internet connection speed, without being affected by other users who are also running tests. This would be especially beneficial for users with high-speed internet connections, as it would prevent their results from being skewed by other users who are running multiple tests at the same time.
Setting a daily limit on the number of speed tests that can be run from a single IP address would help to prevent the abuse of the OpenSpeedTest service by bots or automated scripts. This type of abuse can saturate the service and make it unavailable to other users. By limiting the number of speed tests that can be run from a single IP address, we can help to ensure that the service is available to all users, even during periods of peak usage.
I believe that these features would be a valuable addition to OpenSpeedTest.
Regards,
Jack

It's already planned, but it won't be happening in the near future. Prior to that, we have to create our own Server in a low-level language, which isn't a simple task. Right now, I'm occupied with other projects. For now you can implement Nginx rate limits or IP-based access controls on your server.

Thank you for the reply. I understand that developing a new server is a complex task, and I appreciate your transparency about the timeline. For now, I will implement Nginx limit_conn_module and limit_req_module.
By any chance have you already thought of a configuration for these Nginx modules?
I am excited to see the new server when it is ready. I believe that it will be a valuable addition to the OpenSpeedTest service, and I look forward to using it.


Library does not work in production

My Code:
import Avatar, { AvatarFullConfig, genConfig } from 'react-nice-avatar'

{...}

const [firstPlayerAvatar, setFirstPlayerAvatar] = useState<AvatarFullConfig>({})

useEffect(() => {
    setFirstPlayerAvatar(
      genConfig({
        bgColor: 'transparent',
      })
    )
  }, [])

{...}

 <Avatar
    {...firstPlayerAvatar}
    style={{ width: '7rem', height: '7rem' }}
 />

{...}

On localhost it works

In production it doesn't work, error message:

Uncaught Error: Minified React error #130; visit https://reactjs.org/docs/error-decoder.html?invariant=130&args[]=object&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

full code: https://github.com/rhuangabrielsantos/dots-game
production: https://dots-game.vercel.app/
I use vite with reactjs
Help me :(

I fixed this problem, changed the vite to react-scripts
https://github.com/rhuangabrielsantos/dots-game/pull/1

I'm curious why it doesn't work in Vite?

hey bro ,I fixed this problem too ,but I did not change vite to react-scripts , here is my package.json:
"devDependencies": {
"@types/react": "^18.2.15",
"@types/react-dom": "^18.2.7",
"@typescript-eslint/eslint-plugin": "^6.0.0",
"@typescript-eslint/parser": "^6.0.0",
"@vitejs/plugin-react": "^4.0.3",
"eslint": "^8.45.0",
"eslint-plugin-react-hooks": "^4.6.0",
"eslint-plugin-react-refresh": "^0.4.3",
"typescript": "^5.0.2",
"vite": "^4.4.5"
}


sdist release in addition to wheel

I'll push a source release of asgi-csrf.

Originally posted by @simonw in https://github.com/simonw/datasette/pull/1043#issuecomment-715585140

It might be a bit of a slog, but I'm looking to see about getting datasette (and friends!) available on conda-forge. There are a few missing upstreams (asgi-csrf, python-basecov, mergedeep) and some of the plugins don't even appear to have tarballs (just whl!), but the little stuff like licenses are nice to get out handled upstream vs separately grabbing them.

Actually it already has one.


Get rid of Orchard.Web/Tools/csc.dll

So, by referencing the Microsoft.Net.Compilers.netcore package, at runtime we can retrieve the roslyn csharp compiler csc.exe. This from the runtime directory in a published context, because it is now published in ./runtimes/any/native/csc.exe. And, in a dev context, from the packages storage.
We already automatically create csc.runtimeconfig.json, now we can also create the required csc.dll from csc.exe. So, it seems that we don't need anymore ./Tools/csc.dll grabbed from the dotnet sdk.
Best

Seems to work as before. So, i'll update this PR to not only create csc.dll but also automatically update it, this based on the WriteTimeUtc of csc.exe grabbed from the packages storage or runtime directory.
Best

Done


[BUG] __PYX_STD_MOVE_IF_SUPPORTED doesn't work well with MSVC

Windows 10, Python 3.8.3, Cython 3.0a5, Visual Studio 2017 version 15.9.20.
Let's consider the following example:
a.h:
#pragma once
#include <memory>

std::unique_ptr<int> f() {
    return std::make_unique<int>(123456);
}

b.pyx:
from libcpp.memory cimport unique_ptr

cdef extern from "a.h":
    unique_ptr[int] f() except +

def g():
    cdef unique_ptr[int] p = f()

setup.py:
from setuptools import setup, Extension
from Cython.Build import cythonize

extensions = [Extension(
    "b",
    ["b.pyx"],
    language='c++'
)]
setup(ext_modules=cythonize(extensions, compiler_directives={"language_level" : "3"}))

Expected behavior
python setup.py build builds a .pyd-file.
Observed behavior
python setup.py build produces a message referencing error C2280, doesn't build a .pyd-file.
Workaround
Adding extra_compile_args=["/Zc:__cplusplus"] to the arguments of Extension fixes the problem.
Likely reason
MSVC defines __cplusplus as 199711L by default (details)
Cython defines __PYX_STD_MOVE_IF_SUPPORTED like this:
(source)
#if __cplusplus >= 201103L
  #include <utility>
  #define __PYX_STD_MOVE_IF_SUPPORTED(x) std::move(x)
#else
  #define __PYX_STD_MOVE_IF_SUPPORTED(x) x
#endif

The generated .cpp file tries to copy a unique_ptr, and thus doesn't compile.

Does MSVC provide a way to detect C++11 support? Or is it the case that MSVC > "some version" always supports std::move whatever command line arguments it's called with? Because if not then we're kind of stuck.
You're currently no worse off now than with for Cython <3, since earlier versions would also have tried to copy the unique_ptr. We do want to default to supporting c++98 (so we can't just replace __PYX_STD_MOVE_IF_SUPPORTED with std::move).
Unless we can reliably detect support then your workaround sounds like the correct solution.

I think if both __cplusplus and _MSVC_LANG are defined, whatever their value, then std::move should work. The documentation says:

_MSVC_LANG Defined as an integer literal that specifies the C++ language standard targeted by the compiler. It's set only in code compiled as C++. The macro is the integer literal value 201402L by default, or when the /std:c++14 compiler option is specified. The macro is set to 201703L if the /std:c++17 compiler option is specified. It's set to a higher, unspecified value when the /std:c++latest option is specified. Otherwise, the macro is undefined. The _MSVC_LANG macro and /std (Specify Language Standard Version) compiler options are available beginning in Visual Studio 2015 Update 3.

As for earlier versions, I, sadly, don't know.

I'm getting the impression that it std::move should probably work on at least Visual Studio 2015 onwards (with no obvious way to turn it off). I don't have a huge amount of enthusiasm to download every version of Visual Studio to prove that this is true.
I guess the thing to do would be to turn it on in a PR and see if anything breaks in the Windows tests. The compiler version on Windows is largely dictated by Python anyway, so there aren't a huge variety of options.

AFAIK std::move was already available in VS2010.
Microsoft only started adding language version switches for their experimental C++17 support; everything up to C++14 is always enabled and cannot be turned off.
Unless you are dealing with older VS versions or legacy code where this is causing compatibility problems, you should be compiling with /Zc:__cplusplus.

I think this was closed in https://github.com/cython/cython/commit/00e34553343606b7452a515a0ff8b4b7df311423


"Received invalid state update!" error could be more helpful

Start weave on two hosts, then connect them (breaking the rules on initpeercount):
host1$ sudo weave launch-router
host1$ sudo weave run -ti ubuntu
host2$ sudo weave launch-router
host2$ sudo weave run -ti ubuntu
host1$ sudo weave connect host2

weave logs:
INFO: 2015/07/17 11:01:41.893191 ->[<IP_ADDRESS>:6783|3e:b0:2f:de:5e:da(host1)]: connection added (new peer)
ERRO: 2015/07/17 11:01:41.894079 ->[<IP_ADDRESS>:6783|3e:b0:2f:de:5e:da(host1)]: connection shutting down due to error: Received invalid state update!

Related: https://github.com/weaveworks/weave/issues/760#issuecomment-119629652 - the message there is different but similarly unhelpful

In addition, it seems there is a memory leak that in the router when all these connections fail with the "Received invalid state update!" error. The router took more than 1,5Gb in my Vagrant before it was killed...

it seems there is a memory leak

@inercia Do you see that with the exact same steps that @bboreham posted?

@rade Basically the same steps, while testing Discovery in my Vagrants. If I launch the router with no -initpeercount, Discovery sends /connects  to the router, so I think it is basically the same (maybe the only different would be that connects would be in random order)

Hmm. Running @bboreham's example I too see a steady memory growth. So this is rather more serious then. Please file a separate bug.


Bandcamp only loads one track from album on WACUP

If I load my purchases, I get a list of most (not all) the albums / purchases I have made. When I select play or enqueue, only one track of the album is added to the playlist.

I think it depends on the settings, I have to check.

In the settings, what is Playback -> Archives -> Playlist Handling set to?


chore(main): release 1.0.7

:robot: I have created a release beep boop
1.0.7 (2024-03-16)
Bug Fixes

prepack script (d0b3424)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/mljs/linear-sum-assignment/releases/tag/v1.0.7 :sunflower:


Android: Add autofocus

On camera initialization, set the Camera.Parameters.FOCUS_MODE_CONTINUOUS_PICTURE focus mode.

This change causes this error:
java.lang.RuntimeException: setParameters failed
  at android.hardware.Camera.native_setParameters(Native Method)
  at android.hardware.Camera.setParameters(Camera.java:1941)

You're right, this maybe should have been wrapped in a try/catch, some cameras might not support this.


feat(deps): Support 1.19.3

I used #25 and fixed a few things, so it works on 1.19.3. I also added Polish translations.

Did you manage to make it work? It seems that I was doing something wrong, and I am getting this error

ClassNotFoundException: io.github.ezforever.thatorthis.internal.ModInjector
    at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
    at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
    at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
    at io.github.ezforever.thatorthis.internal.Bootstrap.<clinit>(Bootstrap.java:22)
    at io.github.ezforever.thatorthis.PreloadInitializer.onInitializing(PreloadInitializer.java:34)
    at io.github.ezforever.thatorthis.PreloadAdapter.<clinit>(PreloadAdapter.java:16)
    at java.base/java.lang.Class.forName0(Native Method)
    at java.base/java.lang.Class.forName(Class.java:467)
    at net.fabricmc.loader.impl.FabricLoaderImpl.setupLanguageAdapters(FabricLoaderImpl.java:439)
    at net.fabricmc.loader.impl.FabricLoaderImpl.finishModLoading(FabricLoaderImpl.java:349)
    at net.fabricmc.loader.impl.FabricLoaderImpl.freeze(FabricLoaderImpl.java:112)
    at net.fabricmc.loader.impl.launch.knot.Knot.init(Knot.java:149)
    at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:68)
    at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)

It worked for me... Are you using correct version?  With correct dependencies? I don't think I changed something that could cause this error.

Honestly, i've no idea... I'm new to this, so I just compiled your repository and it doesn't look like it worked. Maybe you can post your build here or make a release in your repo?

Strange... When I run it with gradle runClient it works, but If I compile it and run it in normal minecraft it doesn't work. I am trying to fix this error...

@SettingDust maybe you have idea how we can fix this problem?

https://github.com/FabricMC/fabric-loader/issues/682
As I mentioned, that's the reason of the PR is WIP.
The class loader isn't the one

Okay. Thanks for help!

@SettingDust created a new project which supports 1.19.2.

@SettingDust created a new project which supports 1.19.2.

It's in review on modrinth

It's in review on modrinth

@Norbiros @Felix14-v2 Listed :)


Incompatibility with Redis Client

Hi,
Facing Issues with cls-tracer going out of context and returning id as 'undefined' while using it with redis.
There were some suggestions to use https://github.com/abhiche/cls-redis-patch.
Please let me know if there is any better way to resolve this.

Are you using the latest version of redis client? It's present there, I'd suggest to try the monkey patching approach that cls-redis-patch suggests.

Thanks, Andrey for the suggestion. Will co-ordinate with redis maintainers.


Fix deprecations #215

Issue #215

Nice and clean cut. This should fix #215 and #222.

Nice fix, thank you!


markitondemand DataApis seem to be offline

the look up api just keeps loading and not generating anything
same with the interactive chart api

+1
I'm getting dev.markitondemand.com refused to connect. when I navigate to a lookup url

+1
I'm getting the same problem

This issue has cleared up for me now. Thanks!

Feel free to reopen if you see it again.  We should have failed over seamlessly to another datacenter, so I'm not sure what was up.  I'll ask around about how this site is configured...


Add a dependency to Radical.Bootstrapper?

We have this https://github.com/RadicalFx/Radical-Boostrappers and Radical has its own boostrapping process, that does a lot more that that.
But...why not extend https://github.com/RadicalFx/Radical-Boostrappers here to add support to what WPF and Universal Apps need?

What is the purpose of Radical-Bootstrappers? It is a generic boostrapper that you can also use in console application for instance? Sorry if I ask this, but I've never used, and I need more details to reply this.

Yes it is, it is a generic bootstrapper based on the same conventions model as the built-in Radical one

So you are thinking to inherits from base BootstrapConventions for example here on the Castle BootstrapConventions, and inherits the same stuff like IsConcreteType, IsService, and so on... If yes, I think it could be nice, at the end is called Radical-Bootstrappers right? so it is supposed to be used in Radical packages, otherwise how you can trust such a unused package, eheheh :smile:

:-) yes exactly something like that.

This issue was moved to RadicalFx/Radical.Windows.Presentation#10


refactor: change default linked target name to 'pkg'

pkg is a better default for this compared to {dirname}, especially when running gazelle since it has trouble switching rules types if the default target of package is already a different rule and then that package is turned into a linkable package

I think a test somewhere needs to be updated to use {dirname} so it's still tested?


Introduce Platform metadata that can be updated by the platform

Alternative to the implementation proposed in #544
Based on the hypothesis:

Set of service instances that will consume information like name is less than service instances which will, so this PR tries to make updating of metadata optional
Platforms would have emergent requirements to update things other than name, like org/namespace when it is change for the service instance

If we do this then I think we should do it in place of #544. We should also then define some of the properties that can appear in there - probably in the profile.md doc.


Refactor mas styles to leverage consonant for CTAs

remove spectrum variable dependencies
with some exceptions.
Resolves: MWPW-163621
Test URLs:

Before: https://main--milo--adobecom.aem.live/libs/features/mas/docs/ccd.html
After: https://mwpw-163621--milo--adobecom.aem.live/libs/features/mas/docs/ccd.html

@yesil Seeing the following issues:

slice card widths are not correct, the cards are smaller on ccd page with the width of 305px or 307.2 etc, ccd page has them on max width of 322px
Background color is changed. Should be light grey for light mode (specifically asked i think) rgb (248,248,248), now it is white rgb(255,255,255). Also is different for the dark mode: should be rgb(70,70,70) but here is rgb(30,30,30)
border color is changed for bot light and dark mode:

light is now rgb(234,234,234), was and should be rgb(230,230,230)
dark is now rgb(63,63,63), was and should be rgb(70,70,70)

Title color mismatch:

suggested light: was rgb(34,34,34), now rgb(36,36,36)

Description text color mismatch:

suggested card light: was and should be gray rgb(70,70,70), now rgb(36,36,36)
slice card light: was rgb(34,34,34), rgb(36,36,36)

Price color mismatch for all cards the same as no.4
CTA color:

suggested dark: was rgb(235, 235, 235), now full white rgb(255,255,255)
slice card dark: was and should be rgb((3, 103, 224), now rgb(2, 101, 220). Note that CTA color should not be the same for light and dark mode, you made it the same now. The value you have here is correct for the light theme but not for the dark

CTA highlight dark mode - was transparent grey, not solid white

See terms link color:

suggested:  was rgb(20, 122, 243), now rgb(20, 115, 230)
slice: the same as no.4

@narcis-radu thanks for the review, just got a feedback from CCD team and I can close this one and continue https://github.com/adobecom/milo/pull/3289 which is a similar fix with Spectrum CSS.


How to cluster markers

Is it possible to cluster markers as done here - https://openlayers.org/en/latest/examples/cluster.html ?

No, it's not currently possible, at least not with declarative API. To be honest I don't understand this feature. I've never used it before and I wouldn't have an idea for the "web components" way for implementing this.
That said, you can extend the base vector layer element to do your bidding. See the GeoJSON element as example. All you would need for starters is implement _createSource to return a Cluster. Styling is also supported
Let me know if can help you some more.

Thanks :+1:


Add Nong Song:

Song Name
(FL) Home - We're Finally Landing
Artist Name
AintKelvin
Source
Youtube
Youtube Link
https://www.newgrounds.com/audio/listen/1215249
Direct File Link
No response
Song ID
1215249
Start Offset [ms]
No response
Extra
No response

Also, it's not Youtube, sorry.

reject
thats not a youtube link


pd: fix a dead lock

Read lock won't be dropped inside of the match block.

I remember that we meet the similar deadlock many times, we should fully check our code to see whether we use the same way for the lock. @overvenus

There are still some "match-lock", but they are all in tests, I think they won't cause any trouble.
Try grep -Ersn 'match .*(wl|rl|read|write|lock)\(\).*' for more details.

@overvenus
This potential deadlock in the test may cause test failed, we should fix them later.
LGTM

/run-all-tests


Add ngrok to list of Gateway API implementations

What would you like to be added:
ngrok is working on an implementation for the Gateway API, we want to be added to the implementation list
Why this is needed:
ngrok is a popular service and we want to make sure users are able to find out about it and get the information they need to use it.
FYI: I am a PM at ngrok working on this initiative.

Thanks @salilsub, that's great.
This will need a PR to the "implementations" page, but I'd also recommend that ngrok look at adding a conformance report too, which documents which Gateway API features are supported.


chore: include all supported connectors in the create fuels template

Closes #2677
Closes #2465

Release notes

Added support for multiple new connectors in the create fuels template

Summary
This PR bumps the @fuels/connectors package to 0.8.1 which includes all the new connectors.

This PR also fixes the 'slowness' associated with the 'Connect Wallet' button.
Checklist

[x] I added — tests to prove my changes
[x] I updated — all the necessary docs
[x] I reviewed — the entire PR myself, using the GitHub UI
[x] I described — all breaking changes and the Migration Guide

Marking this as a draft as it seems like there is some additional configuration that needs to be done in order for these new connectors to work on localhost and testnet

Should be good to go now ✅

@Torres-ssf apparently we were incorrectly importing/exporting the isBrowserWalletConnected state from the useBrowserWallet hook and that was causing the status to change slowly or not change at all.


Run codecov from make venv than travis

Fixes #94

The point where it fails has been fixed in a recent PR. If you rebase to master it should pass.

The point where it fails has been fixed in a recent PR. If you rebase to master it should pass.

👍 Just did, thanks for pointing this out. Fingers crossed

Codecov Report

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

@@           Coverage Diff           @@
##           master      #95   +/-   ##
=======================================
  Coverage   76.45%   76.45%
=======================================
  Files          37       37
  Lines        1614     1614
=======================================
  Hits         1234     1234
  Misses        380      380

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4e738be...00d6e3e. Read the comment docs.

Tests passed @aCampello, maybe you could have a look now


ignore fields specifically

Hi, at first congratulations, you've done a great job with the lib, the performance is astonishing.
I was wondering if there is a way to ignore a field specifically for either serializing/parsing, instead of ignoring for both operations.
It is quite common in APIs to have a service that is sent and the server answers with an object of the same type. For instance, a service that updates the profile of a user normally sends a user object with some fields filled and receives as response an updated user. Moreover, sometimes the response can have other fields that we do not want to serialize and although the server check only the needed fields, I find a bad practice to send parameters that wouldn't need to be sent.
Another example could be having a BaseApiResponse super class that acts as a wrapper (contains the response) and other fields like for instance those ones related to error handling. It is something usual that those fields are repeated in most of the services, but those fields shouldn't be sent when sending an instance of the object to the server.
Maybe there is just a way to handle this, I have had a look and I have not found a way to do this, but just in case I am missing something, please excuse me.
I know that a simple way to handle this is to remove chars from the inputstream before sending, but I don't like this approach, I think that this should be done before.
1- I think that a good way to handle this should be using a kind of annotation that lets you exclude a field to be taken into account when serializing or parsing, for instance "@IgnoreSerialization" and "@IgnoreParsing" or just a single one like "@IgnoreSpecifically(op = "serialization").
2- Another way would be to have an annotation like those ones you are using when operations have finished (i.e. "@OnJsonParseComplete") but that is taken into account in the process of the operation. By this way returning a kind of facade have a method ignoreField(field) and this removes unwanted fields.
I would like to know your thoughts, maybe you think that this could affect a little bit the performance and you discard an option like that, but first option would not damage so much performance.
As I told maybe there is just a way to do this, if there is, many apologies.
Thanks a lot

Thanks for all the detail on this! I think this is a great idea, and I'll be adding support for it in the next version, which should be sometime early next week. I'm planning to add an optional argument to the current @JsonIgnore annotation called ignoreFor that can be PARSE_AND_SERIALIZE (the default), PARSE_ONLY, or SERIALIZE_ONLY. Sound good?

Sounds great. If you need some help, let me know and I will help to develop this feature.

Already started :)

Alright, this is done in commit 3f120c2012fdf75ed142d9fdfdc2b62ca670a4d5. It's not live on JCenter or Maven Central yet, so you'll have to build from source if you want to use it ASAP. I'll probably push it on Friday or so.

This is what is called being faster than a lightning bolt! haha Thanks a lot :) no worries, I think that I can wait for the release, else I will clone the repo ;) Thanks again

Hi Eric,
Just wanted to know if there are any news on this update. I also wanted to know if you would consider an addition to skip null values for object serialization. It is the default behaviour for Gson and can also be customized using Jackson:
mapper.setSerializationInclusion(Include.NON_NULL)

I think that this could be a good addition, but I wanted to know if you are happy with this feature before developing it and pushing a PR. If you think so, we can label this as a new issue.
Thank you a lot


adapt langchain tool

移植langchain的sleep和shell工具

#52

移植sql工具

#67 This pr has build an implementation that enables all LangChain tools.

移植sql工具

We can build an implementation though LangChain has provide the ability to do it.


iPad A9 (5th gen) unable to boot from SSHRamdisk

I have an A9 5th gen Wi-Fi iPad(6,11). When I run ./sshrd.sh boot, two progress bars show up and reach 100%, then my iPad boots into normal iOS and I get an error “unable to connect to device”. I have tried it on Ubuntu 22.04, and MacOS Monterey (M1 Pro), with two different usb cables (one Anker and one generic), and I get the same results. I’m running iPadOS 15.2.1.

Hello?

Try the latest commit


No security by default?

From https://github.com/snyball/Hawck/blob/841e563a3be93fbc1e0f9d428a08191f576201a5/README.md#security

The keyboard daemon contains a whitelist of keys that the macro daemon is allowed to see, this whitelist is derived from the Lua scripts used.

But Lua scripts are user controlled. Does that mean that user is still able to read all keyboard input?

No, you need to run hawck-add, which will ask for elevated priviliges (via sudo or pkexec.)

And when hawck-add adds the script, the keys that are whitelisted can be read by any user level program, right?

@abitrolly Yes
Alternative approaches and motivations for the current model can be found here: https://github.com/snyball/Hawck#alternative-security-strategies-and-motivations

Thanks. Now it is clear. I did read that paragraph, but could not understand.


Actually support old dnaplotlib

added try except to renderDNA call

dont mind the commit number, look at the changed files


The wechat QR code has expired

I want to join IM WeChat discussion groups, but the QR code shown in the readme has expired.

hello @un-knight, updated, please try again.


Add support for Node Info

Add support for triggering node-collector job in cluster.
the collector will collect info from node and output it.
require to support both for trivy and operator.
Related :

epic
story

@josedonizetti all comments has been addressed , I'm merging the PR to be able to continue with other dependents PR.


Tachyons without media queries?

I want to use a custom build of tachyons because I don't need media queries, so 75% of the code.
How do I do it?
Right now I'm importing tachyons from js like this import 'tachyons' (using webpack), but it would be great to do something like import 'tachyons/css/tachyons-minimal'

why don’t you create your own app.css where you may import a module or not. also you can get rid of unuses css at the build stage via css cleaner or a similar plugin

ah, my bad; i thought that mq are in separate files

You can achieve this with the Tachyons generator. Or, you can customize the Tachyons build by providing an additional postcss plugin like postcss-unmq.


KAFKA-5117: Add password masking for kafka connect REST endpoint

More detailed description of your change,
Mask all password type config parameter with "********" instead of displaying the plain text in kafka connect REST endpoint.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

I'm new to kafka and not an expert on Java. So if anyone has better idea to achieve this, please let me know. I'm happy to make changes.

@bharatviswa504 Sorry I can only find you since your name was involved in the ticket KAFKA-5117. Do you mind take a look at this PR or direct to anyone who can?

@ewencp Could you take a look at this PR?

@guozhangwang Do you mind take a look?

@qiao-meng-zefr It seems from the JIRA someone has already started working on this ticket, have you coordinated with the other contributors for resolving this issue? cc @rhauch as well for reviewing.

@guozhangwang Yeah I tried to find the person "Thomas Holmes" who was working on this in the People page in github, but couldn't find him. That jira issue seems old so I assumed no one is still working on it. Thanks for redirect this to rhauch.
@rhauch Thank you very much for the review I'll make change accordingly.

A better solution is provided: https://cwiki.apache.org/confluence/display/KAFKA/KIP-297%3A+Externalizing+Secrets+for+Connect+Configurations


Define 3 XCM / DeFi  use cases

Define 3 uses cases that integrates the DEX pallet located in https://github.com/Wiezzel/substrate-dex with Trappist parachain.
We might use the HOP native token of Trappist to define a some liquidity pool and have a custom logic around the LP token.

[x] 1. https://github.com/paritytech/trappist/issues/44
[ ] 2.
[ ] 3.

@Wiezzel @bidzyyys @pawanbisht62

Yes I think so. Let's re-discuss further what a good use case for the ExchangeAsset instruction would be, and then we'll create a new issue for it with a proper spec.


Use next ipfs-log

This PR adds changes needed to support the new version of ipfs-log with loading optimizations.

I'm 100% guilty of this myself, but I'm thinking there's got to be a better way to store these IPFS fixture blocks in git. 😆 I'm thinking I might try my hand at a zip file or tar.gz that is uncompressed via make build. What do you think?

what about git lfs? https://git-lfs.github.com/

This PR depends on:

https://github.com/orbitdb/ipfs-log/pull/275
https://github.com/orbitdb/orbit-db-identity-provider/pull/53
new release of https://github.com/orbitdb/orbit-db-store
new release of https://github.com/orbitdb/orbit-db-io


boolean options can never be set to false

The options array passed to the init function will not work properly when the option has a boolean value and that value is FALSE because in array_get function the default value is used when the empty function returns true for the option array value.
To reproduce:
Just add 'to_stderr' => FALSE to your options array and you will see the to_stderr setting stays set to the default of TRUE.

This has been fixed. Thanks for reporting it!


resolve null CS8603 Possible null reference return in JsonFileProductService

how to resolve possible null reference return in GetProducts

also having this issue

Copy and Paste this code in your index.cshtml.cs file
public class IndexModel : PageModel
{
private readonly ILogger _logger;
public JsonFileProductService _productService;
public IEnumerable Products { get; private set; }
    public IndexModel(ILogger<IndexModel> logger, JsonFileProductService productService)
    {
        _logger = logger;
        _productService = productService;
    }

    public void OnGet()
    {
        Products = _productService.GetProducts();
    }
}

After debugging i found that we did not give our field from class JsonFileProductService a value in the constructor.


Exercise 9 doesn't compile

Exercise 9 doesn't compile with the given solution, not sure if intended as the book doesn't mention this.
error[E0600]: cannot apply unary operator `-` to type `u32`
  --> exercises/09_ambiguity_and_ordering/main.rs:50:36
   |
50 |         NumberType::NegativeNumber(-$negative)
   |                                    ^^^^^^^^^^ cannot apply unary operator `-`
...
70 |     get_number_type!(-5).show();
   |     -------------------- in this macro invocation
   |
   = note: unsigned values cannot be negated
   = note: this error originates in the macro `get_number_type` (in Nightly builds, run with -Z macro-backtrace for more info)

For more information about this error, try `rustc --explain E0600`.
error: could not compile `macrokata` due to previous error

Perhaps unrelated, but would it be better for positive literal to be
( $(+)?$positive: literal ) => {...}

So the macro works for +5 as well as 5?


translation

Hi Rubens,
I use your plugin with datarapper 1.9.5 but the locale strings are not recogniced.
is there anything I have to do after installing and enabling your plugin?
Joerg

This is still an issue. None of the locale strings display properly.


Shouldn't export greet

In my opinion, you shouldn't need to export greet in this package. (You can of course do whatever you want)
https://github.com/azeredo-e/BrazilCentralBank.jl/blob/71907424c57cc77d551b415a2880fb6a8d9a73f8/src/BrazilCentralBank.jl#L15

I thought it was a fun little thing to left on, but yeah, I guess I should not export and just left for access directly through calling the name of the module. Thanks for the advice!


Differences with other plaintext time-trackers

I'm trying to evaluate the relative strengths and weaknesses of different plaintext time trackers, like Emacs/Ledger/Hledger timeclock (especially with a helper script like tt), Watson, and Timewarrior.
It might be useful to have a small comparison, or even an explanation of why the existing tools fell short leading you to write klog.

I’ve written two posts on my blog covering some of the background thoughts: this one shortly after I published the project initially, and this one a few months ago.
It’s not a systematic comparison, but I also didn’t look too deeply into other CLI-based tools. The “tldr” is that I wanted a pleasant and meaningful data format primarily, that would allow me to view and edit the data in an editor, without needing to rely on specific tools, or be forced into specific workflows. The klog CLI tool is only for data evaluation, and for a few other use-cases for convenience. The most important thing is the file format.


feat(search): Add dynamic SQL query generation for pgvector search

Hi @timonv,
I’d like to align quickly on this.
This PR addresses our recent discussion, particularly the idea:

"Or we could go lazy (not so lazy, it's not trivial) and add a custom strategy that takes an SQLx query, or a closure that returns an SQLx query with the nodes yielded. That would enable a lot of doors in fully controlling the search process."

As part of this PR, I’ve implemented a Dynamic Search Strategy to enable dynamic SQL query generation for pgvector search.
Key benefits:

Combines vector similarity with metadata filtering
Allows users to fully customize query construction
Provides precise control over filtering and ordering

Looking forward to your feedback on how this can be refined further!

Hey @shamb0, the concern I have with this, is that it only works with Sql. I was thinking of a broader solution such that Swiftide makes several big wins:

More complex solutions might require custom queries
Can't provide defaults for every use case
Still allowing for the underlying library to be used is, I believe, a very good practice.

It also removes the need / pressure to implement every search strategy for every storage, as there's always the manual option. Might be a bit harder, but huge relieve when it works.
For instance, say we have a CustomSearchStrategy<Q>, where Q is the internal query type of the storage provider. Then only that has to be implemented, everything is possible, and we can add it to providers on our own pace.
For instance, for what we have now, Q could be:
sqlx -> QueryBuilder https://docs.rs/sqlx/latest/sqlx/struct.QueryBuilder.html
qdrant -> SearchPointsBuilder https://docs.rs/sqlx/latest/sqlx/struct.QueryBuilder.html
lancedb -> Query https://docs.rs/sqlx/latest/sqlx/struct.QueryBuilder.html
In pseudo code, something like this might work:
struct CustomQuery<Q> {
  query: Q
}

impl<Q: Send + Sync + Clone> CustomQuery<Q> {
    pub fn from_query(
        query: impl Fn(&CustomQuery<Q>, &Query<states::Pending>) -> Q + Send + Sync + 'static,
    ) -> Self {
        CustomQuery {
            query: Arc::new(query),
        }
    }

    pub fn build_query(&self, query_node: &Query<states::Pending>) -> Q {
        (*self.query)(self, query_node)
    }
}

impl Retrieve<CustomQuery<QueryPoints>> for PgVector {
    async fn retrieve(
        &self,
        search_strategy: &CustomQuery<sqlx::QueryBuilder>,
        query: Query<states::Pending>,
    ) -> Result<Query<states::Retrieved>> {
       ...
       let builder = search_strategy.build_query(&query);

       ... // anything else and execute
    }
}

// A user can then use it as follows:

let strat = CustomQuery::from_query(|strat, query_node| sqls::QueryBuilder::new ... })

This way, there's no uphill battle in trying to implement every conceivable query method, and users can do whatever they want. Other query strategies are there for sane and quick defaults. We could also let the provider (i.e. PGVector) provide a build_custom_query to make it a bit easier. What do you think?

Just to be clear, I'd be happy to merge an implementation that only supports SqlxBuilder at the moment, then I or someone else can expand on it in the future 👍

Just to be clear, I'd be happy to merge an implementation that only supports SqlxBuilder at the moment, then I or someone else can expand on it in the future 👍

Hi @timonv,
Apologies for the delay :), and thank you for sharing the detailed design guidelines! I'll aim to complete the SqlxBuilder implementation this week.
Next week, I'll start working on the search strategy for the remaining storage. 👍🏾

Hi @timonv,
I’ve implemented the custom search strategy for sqlx::QueryBuilder based on our recent discussion. The key updates include:

Dynamic SQL query generation for vector similarity search
Integration with pgvector
Comprehensive integration test coverage

Please review and let me know if further adjustments are needed.
Thank you! :)

Hi @timonv,
Thank you for your review comments :). I have reworked the code and cleaned it up as suggested.

Initially, I wrapped CustomQuery<Q> inside a new type PgVecCustomStrategy as I thought it would make the code more concise and Rust-idiomatic. However, as part of this patch, I have removed that additional layer.
pub struct PgVecCustomStrategy(pub CustomQuery<sqlx::QueryBuilder<'static, sqlx::Postgres>>);

I believe the PR is now ready for intake. Please let me know if any further enhancements are needed. :)

Thank you @timonv for your thorough and constructive feedback :). I appreciate your patience in guiding me through these improvements.
I have addressed both key points from your review:

Updated the terminology from "provider" to "retriever" throughout the documentation to better reflect the architectural intent
Simplified the CustomStrategy implementation by moving configuration into the query generator closure, reducing structural complexity

The documentation has been enhanced with:

Clearer examples demonstrating the new configuration pattern
Detailed explanation of the query generator's responsibilities
Updated implementation notes for users of the custom search strategy API

I believe these changes have made the code more maintainable and the API more intuitive to use. Please let me know if you'd like to see any further improvements or have additional suggestions.

Looks good! I want to go over the docs one more time before merging, I'll do the changes. I will merge this asap.


[WIP] [PoC] Container graph refresh

Experimenting with gradually converting save_inventory_container to use graph refresh.
Deliberately not following higher-level graph refresh helpers and organization/naming/style. Building InventoryCollections as simply as possible (so I understand what's going on), keeping our parser unmodified producing hashes, cutting off to old save_inventory after graph-saved entities.
useful (well for me) byebugs kept in grafresh-DEBUG branch.
@miq-bot add-label wip, providers/containers, refactoring

Lessons learned about configuring InventoryCollection [will update as I go]
First, thanks @Ladas for {acyclic_,}graph_of_inventory_collections_spec, with the epic comments with ascii art graphs!
Other priority reading: manager_refresh/save_collection/helper.rb doing the actual save/update/delete; inventory_collection.rb object_index and its uses.

:model_class and :parent are mandatory.

:parent has to be a fixed pre-existing object, typically the EMS.

If your Foos are reachable as ems.foos, use :association => :foos.
If not, you need :parent => ems, :arel => ...joins(...).

The :association / :arel is also used to delete entities refresh didn't find (targetted refresh will have to either constrain it — see graph_of_inventory_collections_targetted_refresh_spec — or disable delete_allowed?).
If you get arel wrong, subtle problems will happen!  Saving doesn't check the arel covers the saved objects, so first refresh may work, but second refresh will delete innocent objects.
Example: EMS has_many container_quotas has_many container_projects.  First I tried for quotas :arel => ems.container_projects.joins(:container_quotas) but that actually returns enriched Project objects (that have at least one quota), and my Projects were getting mysteriously deleted :-(
The right direction is ContainerQuota.joins(:container_project).where('container_projects.ems_id' => ems.id).

Tables without unique ems_ref require defining unique :manager_ref column combination.  That's what find[_by], lazy_find etc refer to objects by.  That's what update/delete identify records by.

find, lazy_find is by stringified ref joined with double underscore ("foo__bar").
There is no hash-taking lazy_find_by, perhaps should be.

cc @simon3z @agrare @durandom still very early but if you want to look...

@cben sorry for the lack of documentation, it is on the way :-) I see that you try to rewrite it incrementally to the new refresh, while using the old parser code and processing in the saving code, but that might lead to some ugly pre-processing, once you will have all models in
So it other providers, we are ditching the old parser and saving code entirely and just focusing on passing the same refresher_specs. The latest greatest example of the new refresh is ansible https://github.com/manageiq/manageiq/tree/master/app/models/manageiq/providers/ansible_tower/inventory
But you can get there also using this way of a incremental rewrite, but it will be much more painful I suppose. :-)
Also we tend to keep the old refresh around as the backup plan, that can be switched on with configuration.

@cben I see, haven't read the first comment that the incremental approach is on purpose :-) It's good for learning. :-) Also I know that @agrare and @Fryguy wanted this approach as a switchable saving part only, keeping 1 parser, so maybe it is a valid approach too. But our main motivation of the total rewrite was doing it nicer&cleaner way. :-)

@cben I really like that you didn't change the parser at all (I'm not a big fan of total rewrite like @Ladas is :wink: ), but I think it'd be better to either use graph or hashes to save rather than mix them.
Its great to do it incrementally but we should leave the current save_ems_container_inventory the way it is and add graph saving separately, even if it doesn't save all collections yet.

@cben taking care of BZ#1443740 first is going to make the graph refresh easier?

Container/Containers Definion - not sinificantly. But good idea because
doing it later would require changing 2 places.  Performance effect should
also be negligible, as it's 1:1 relation.

Inline env vars - not simpler, probably faster, would rather do later.

BZ @zakiva is studying about children not getting deleted because
target=nil will hopefully result in more tests, which would help.
(Current refresher specs don't check deleting nor disconnecting at all...)

On May 18, 2017 3:55 PM, "Federico Simoncelli"<EMAIL_ADDRESS>wrote:

@cben https://github.com/cben taking care of BZ#1443740
https://bugzilla.redhat.com/show_bug.cgi?id=1443740 first is going to
make the graph refresh easier?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ManageIQ/manageiq/pull/14337#issuecomment-302395191,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQtGINkhbJeOVfLgJVORVgnVF0AU2Ngks5r7D--gaJpZM4MdtHm
.

@cben FYI, I have simple stubbed integrations tests in AWS that do a checks of deleting, e.g: https://github.com/Ladas/manageiq-providers-amazon/blob/87f80dcbf0227ee1fba99c9ef6ad2e0481331809/spec/models/manageiq/providers/amazon/cloud_manager/stubbed_refresher_spec.rb#L42-L42

@cben hm, lets ditch the idea with :ems_id, we would get to inconsistent state when disconnecting records. E.g. when disconnecting node, you would want to keep the label, but it would get deleted (or disconnected too)
So, writing the query is actually pretty easy. It will be just a bit bigger for the labels (but you should be able to generate it from a list of model classes)
so inside of the specific persister
     :name = :computer_systems,
     :association => nil,
     :arel => ComputerSystem.where(:managed_entity_type => "ContainerNode", :managed_entity_id => manager.container_nodes.select(:id)).or(
                  ComputerSystem.where(:managed_entity_type => "Hardware", :managed_entity_id => manager.hardwares.select(:id)))

Interesting.  Your queries are generating a nested select:
> puts ContainerCondition.where(:managed_entity_type => "ContainerNode", :managed_entity_id => ems.container_nodes).to_sql
SELECT "container_conditions".* FROM "container_conditions" WHERE "container_conditions"."managed_entity_type" = 'ContainerNode' AND "container_conditions"."managed_entity_id" IN (SELECT "container_nodes"."id" FROM "container_nodes" WHERE "container_nodes"."ems_id" = 3)

compared to through relations generating a join:
> > puts ems.container_node_conditions.to_sql
SELECT "container_conditions".* FROM "container_conditions" INNER JOIN "container_nodes" ON "container_conditions"."container_entity_id" = "container_nodes"."id" WHERE "container_nodes"."ems_id" = 3 AND "container_conditions"."container_entity_type" = 'ContainerNode'

And the trick is that the nested-select ones are "structurally compatible" for .or().
Actually I'm not sure I want union queries, I'm playing now with just function generating separate collection per parent, but should be able to switch to one union query easily.

@cben right, so you can't do JOIN, if you do polymorphic relation over many models. You could do actual sql UNION of the joins. But for me just doing OR and nested selects is much easier. Later we could benchmark the 2 approaches on a high number of records.
Right, doing 1 collection per parent on the models sounds great. Then the EMS model can have method that will put them together to 1, based on given ems_refs and types. (we should push all the logic to the models, the Persistor would just use the existing methods)

This is nearly 💯 complete (except some untested parts).
Will soon close this and work on new PRs,
collecting todos on https://github.com/ManageIQ/manageiq/issues/15243

Closing in favor of the new PRs.  See https://github.com/ManageIQ/manageiq-providers-kubernetes/issues/27.


Add GitHub link in app

Maybe can put it in about page

Thank you for reporting.
I will implement this feature in the future.


SimpleSigner.load_pkcs12() passphrase utf-8 character error

signer = SimpleSigner.load_pkcs12(pfx_file = "pfx_file.pfx", passphrase = bytes("password1á34", encoding='utf-8'))
if I call this code, it throws me:
Could not load key material from PKCS#12 file Traceback (most recent call last):   File "C:\falk\fem\lib\site-packages\pyhanko\sign\signers\pdf_cms.py", line 1532, in load_pkcs12     ) = pkcs12.load_key_and_certificates(pfx_bytes, passphrase)   File "C:\falk\fem\lib\site-packages\cryptography\hazmat\primitives\serialization\pkcs12.py", line 157, in load_key_and_certificates     return ossl.load_key_and_certificates_from_pkcs12(data, password)        File "C:\falk\fem\lib\site-packages\cryptography\hazmat\backends\openssl\backend.py", line 603, in load_key_and_certificates_from_pkcs12     pkcs12 = self.load_pkcs12(data, password)   File "C:\falk\fem\lib\site-packages\cryptography\hazmat\backends\openssl\backend.py", line 632, in load_pkcs12            raise ValueError("Invalid password or PKCS12 data") ValueError: Invalid password or PKCS12 data
If i use utf8 character in the password string then it throws me error!

This almost certainly means the PKCS#12 MAC did not validate and/or your payload decrypted to bogus data, i.e. the password is wrong, or you chose the wrong encoding. PKCS#12 passwords are binary data, not strings. So especially with non-ASCII passwords you have to be very careful to pick the same encoding as the one that was used to create the PKCS#12 file.
You seem to be on Windows, which is not exactly known for its sane defaults when it comes to encodings... Assuming you generated the file yourself: the "correct" encoding is probably not UTF-8, but some old 256-bit codepage from the 80s or 90s that Microsoft doesn't dare to change because they don't want to break compatibility for people still running the '96 edition of WordPerfect.
Joking aside, try latin1 instead of utf-8 and see if that works. Failing that, you'll have to figure out your system's default encoding and try to work out how to use it from Python.


chore: remove react-bootstrap package

Summary of changes
removed react-bootstrap package
Modal component replaced by native html modal element

Checklist

[x] I have read and followed the contribution guidelines.
[x] I have read through the Code of Conduct and agree to abide by the rules.
[x] This PR is for one of the available issues and is not a PR for an issue already assigned to someone else.
[x] My PR title has a short descriptive name so the maintainers can get an idea of what the PR is about.
[x] I have provided a summary of my changes.

closes #1211

agree, the native dialog is much more elegant solution!
will change pr asap

It looks like there are some conflicts that need to be resolved


Docs: Add example for Reusing Reducer Logic

What docs page needs to be fixed?

Section: Recipes
Page: Structuring Reducers -> Reusing Reducer Logic

What is the problem?
This part explains some methods on how to reusing reducer. But I think this part should explains more on configuring action creator.
What should be changed to fix the problem?
Please add example how to write action creators for these extended reducers.

Can you clarify what you mean by "configuring action creators" ?

...
const rootReducer = combineReducers({
  counterA: counter,
  counterB: counter,
  counterC: counter
})

Unfortunately, this setup has a problem. Because combineReducers will call each slice reducer with the same action

The documentation has solution for this such problems.

function createCounterWithNamedType(counterName = '') {
  ...
}

function createCounterWithNameData(counterName = '') {
  ...
}
const rootReducer = combineReducers({
  counterA: createCounterWithNamedType('A'),
  counterB: createCounterWithNamedType('B'),
  counterC: createCounterWithNamedType('C')
})

store.dispatch({ type: 'INCREMENT_B' })
console.log(store.getState())
// {counterA : 0, counterB : 1, counterC : 0}

What missing here is how to do dispatch({ type: 'INCREMENT_B' }); with action creators.


Ratchet + mbstring.func_overload

Hey! Just wanted to contact you to say, I was suffering from ratchet returning me 400 on connection request. The reason was, when HandshakeVerifier tries to verify the key, strlen returns weird values due to mbstring.func_overload value 2 or more. So maybe you make it clear for future users that mbstring.func_overload could be an issue?
Also, awesome library, and you sir are awesome. thank you!

Thank you for the kind words! There's a check in App.php about this but that doesn't cover all scenarios. 0.4 will have the check against this moved in WsServer so it will always be caught.


Parallel API

Improve throughput by using multi-threading (rayon).
In most cases, the simd functions are fast enough that we may not benefit from multi-threading. And some functions are not divisible.
Crates with parallel api:

https://github.com/uhmarcel/rbase64

Parallel threshold
$$
\frac{n}{pv}+c<\frac{n}{v}
$$
$$
n > \frac{p}{p-1}cv
$$
$n$: input size (B)
$p$: num threads
$v$: throughput (B/ns)
$c$: threading overhead (ns)

just bench static-experimental --bench base64 --plotting-backend disabled -- 'base64-encode/base64-simd'

base64-encode (GiB/s)

16
32
64
256
1024
4096
65536
262144
524288
1048576

base64-simd/auto
1.827
1.977
3.503
8.008
11.826
12.980
13.494
12.852
12.751
12.723

base64-simd/parallel
1.174
0.004
0.008
0.029
0.114
0.433
5.623
16.196
24.001
31.267

Would it be useful to have option to parse multiple items, which the cache and instruction level parallelism can probably help here.
Use case will be something like being able to use it in polars to read a column of uuid.

Would it be useful to have option to parse multiple items, which the cache and instruction level parallelism can probably help here.
Use case will be something like being able to use it in polars to read a column of uuid.

Could you explain this use case in more detail? How can we accelerate it by multithreading?

Not really multi-threading but aligning on cache lines and being able to process multiple items at once maybe can make it faster? When we need to process batches of it, maybe there are better way to process items in bulk compared to processing each item one by one?

Sounds interesting. We can discuss it in another issue #45


Demonstrate Senzing stack deployment on Microsoft Azure

References
Azure

Azure documentation

Azure Resource Manager

Documentation

ARM Templates

Documentation

What are ARM templates?

Azure Kubernetes Service (AKS)

Documentation

Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using an ARM template

Example URL to deploy ARM template:
https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.kubernetes%2Faks%2Fazuredeploy.json

Storage

Storage options for applications in Azure Kubernetes Service (AKS)
Choose "Azure Files" (not "Azure Disks") because of

Since Azure Disks are mounted as ReadWriteOnce, they're only available to a single pod.
on https://docs.microsoft.com/en-us/azure/aks/concepts-storage#volumes

Terraform

Hashicorp Terraform Registry

Terraform examples

Kubernetes (AKS)
Database
Storage

Azure Kubernetes Service (AKS)

Documentation

Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using an ARM template

Scaling

Scaling containers and serverless applications

Video

Understanding and Using Project BICEP - The NEW Azure Deployment Technology - 2021-03-09

Bicep

Bicep playground


Standardise on initialized

See discussion in https://github.com/ably/wiki/issues/68
blind whole-repo s/nitialis/nitializ/' - haven't tested this (don't know how and don't think I can on a non-mac), so please test before merging

Tests are passing, so LGTM.

LGTM

Nice one @SimonWoolf, good spot


[Beam-7925] Add column projection to ParquetIO

User can specify the columns to read with string representation of the requested projection when they read parquet file.

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

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

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

R: @ihji

R: @chamikaramj

Run Java PreCommit

Run Spotless PreCommit

/cc @chamikaramj


✨ Add Typer integration

This PR adds an integration for Typer
The integration works by mocking typer.main.except_hook, I was chatting with Sebastian and he's willing to add a hook in typer to avoid mocking, but I think it's also fine to keep the code as is 😊
The code is inspired by the ExcepthookIntegration, same thing for the test, unfortunately there's no way to test a custom except_hook with pytest, so I'm running the CLI using subprocess.
Shall I add this to the default integrations? 😊
Closes #1612
Closes #1604

Thank you @patrick91 ❤ We will take a look at this next week!

Shall I add this to the default integrations? 😊

As with all new integrations I'd prefer we leave this as opt-in for a couple of releases and then re-evaluate, just to be safe.


Unmet peer dependecy<EMAIL_ADDRESS>

I gather sinon-express-mock currently lists sinon ^4.1.13 as a peer dependency.
Sinon's current release is now 5.0.7.
Is there a plan to update to, or otherwise allow current Sinon releases? Or do I need to downgrade Sinon to use sinon-express-mock?
Thanks!

Someone had updated this previously in a PR but I forgot to push the code to NPM. Can you try v2.0.2 and reopen if it still doesn't work?

I don't think I can reopen this, but I think it is still unresolved: the package.json peerDependency is still configured as ^4.1.3.

Fixed in v2.0.4 👍


RuntimeError: cuDNN error: CUDNN_STATUS_INTERNAL_ERROR what():  CUDA error: an illegal memory access was encountered

As I ran the Inference for single-gpu testing as written in the README, the inference process stopped at 10/2000 with the following error:
Use load_from_local loader
[                              ] 10/2000, 0.9 task/s, elapsed: 11s, ETA:  2161spython-BaseException
RuntimeError: cuDNN error: CUDNN_STATUS_INTERNAL_ERROR
terminate called after throwing an instance of 'c10::Error'
  what():  CUDA error: an illegal memory access was encountered
Traceback (most recent call last):
  File "/home/peter/PycharmProjects/Swin-Transformer-Semantic-Segmentation/mmseg/apis/test.py", line 60, in single_gpu_test
    result = model(return_loss=False, **data)
  File "/home/peter/Applications/anaconda3/envs/swin-seg/lib/python3.7/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/peter/Applications/anaconda3/envs/swin-seg/lib/python3.7/site-packages/mmcv/parallel/data_parallel.py", line 42, in forward
    return super().forward(*inputs, **kwargs)
  File "/home/peter/Applications/anaconda3/envs/swin-seg/lib/python3.7/site-packages/torch/nn/parallel/data_parallel.py", line 153, in forward
    return self.module(*inputs[0], **kwargs[0])
  File "/home/peter/Applications/anaconda3/envs/swin-seg/lib/python3.7/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/home/peter/Applications/anaconda3/envs/swin-seg/lib/python3.7/site-packages/mmcv/runner/fp16_utils.py", line 84, in new_func
    return old_func(*args, **kwargs)
  File "/home/peter/PycharmProjects/Swin-Transformer-Semantic-Segmentation/mmseg/models/segmentors/base.py", line 124, in forward
    return self.forward_test(img, img_metas, **kwargs)
  File "/home/peter/PycharmProjects/Swin-Transformer-Semantic-Segmentation/mmseg/models/segmentors/base.py", line 106, in forward_test
    return self.simple_test(imgs[0], img_metas[0], **kwargs)
  File "/home/peter/PycharmProjects/Swin-Transformer-Semantic-Segmentation/mmseg/models/segmentors/encoder_decoder.py", line 265, in simple_test
    seg_logit = self.inference(img, img_meta, rescale)
  File "/home/peter/PycharmProjects/Swin-Transformer-Semantic-Segmentation/mmseg/models/segmentors/encoder_decoder.py", line 250, in inference
    seg_logit = self.whole_inference(img, img_meta, rescale)
  File "/home/peter/PycharmProjects/Swin-Transformer-Semantic-Segmentation/mmseg/models/segmentors/encoder_decoder.py", line 217, in whole_inference
    seg_logit = self.encode_decode(img, img_meta)
  File "/home/peter/PycharmProjects/Swin-Transformer-Semantic-Segmentation/mmseg/models/segmentors/encoder_decoder.py", line 88, in encode_decode
    out = self._decode_head_forward_test(x, img_metas)
  File "/home/peter/PycharmProjects/Swin-Transformer-Semantic-Segmentation/mmseg/models/segmentors/encoder_decoder.py", line 110, in _decode_head_forward_test

I have googled this error (https://github.com/pytorch/pytorch/issues/21819) and the culprits could be too big batch_size.
But the samples_per_gpu was set to 1 and I have a GPU with a huge memory of 48GB, and during the inference it gradually took all 48GB till it overflowed. so it must be something wrong with the setting or within the code, but I cannot find it out.
Can you help me to solve it? Thanks in advance.

Solve it by myself:
it seems like pytorch 1.6.0 and cudatoolkit 10.1 are not compatible with cudnn 8.1.0 or higher. As I downgrade my cudnn version to 8.0.5, this problem got solved... it was a very wired bug, tried so many methods to solve it


Search not working on mobile phones

The search button bar  is now 'pinned' to the bottom of the screen, and does not work.

Ready for testing in test2

@PatReynolds and @richpomfret to test.

Still pinned, but now works.
Advantages to the pinned search:

it allows the user to skip to the search as soon as they've entered what information they think will get them to a reasonable number of records.

(Possible) disadvantages to the pinned search:

it may cause conflicts with a pinned advertisement.
if there is no conflict with a pinned advertisement, it may take up in total too much screen space on a small phone


Getting exception from server on C# client

I have an ASP.NET SignalR server on .NET Core 2.1 and a .NET 4.6.2 C# Client on Microsoft.AspNetCore.SignalR.Client 1.0.3.
This is my hub:
public class MyHub : Hub
{
	public async Task<Boolean> Connect(String identifier)
	{
		if (identifier == null)
		{
			throw new Exception("Identifier null");
		}
		return true;
	}
}

And my client:
try
{
	var response = await _hubConnection.InvokeCoreAsync<boolean>("connect", new Object[] { null });
}
catch (Exception ex)
{

}

When I send the request the server throws a custom Exception (identifier null), but the exception on the client is An unexpected error occurred invoking 'connect' on the server. and the actual exception cannot be accessed.

By default, for security reasons, we don't expose detailed error messages to the client. There are two ways to the more detailed information:

Turn on EnableDetailedErrors to allow the server to send detailed error messages. This is not recommended in production
Check the server logs, the full exception should be logged there for you to see (this is the recommended approach in production environments).

Ok makes sense. This is a fully internal app so there is a need to have the exceptions come over as is, EnableDetailedErrors works fine in this case.

Re-reading your example, there is a third option that may be better:

Leave EnableDetailedErrors disabled and throw HubException or exceptions derived from HubException. Those errors will be sent to the client regardless of your EnableDetailedErrors setting (as they are designed for use when you want to explicitly communicate the error to the client). This would mean that other exceptions (runtime errors, database connection problems) won't have their details sent to the client, but the exceptions you choose will.

Yes that's even better, that way I can only send over intended exceptions that need to be acted on, thanks!


Search on field with AND

As documented (https://lunrjs.com/guides/searching.html):

we must use something like 'tags:foo' if we want to search on field 'tags'.
we must use '+foo +bar' if we want to search 'foo' AND 'bar'

I would like to search all documents having 'tags:foo' AND containing 'bar'.
I tried:

'tags:foo +bar' ==> WRONG result (Applied as a OR)
'tags:+foo +bar' ==> WRONG result (no result, may be because +foo is not a tag)
'+tags:foo +bar' ==> SYNTAX ERROR (unrecognised field '+tags', possible fields: 'text', 'title', 'tags')

How should I do?
Is it a bug.

First, check what version of Lunr you are using, term presence queries are only supported in version 2.2 and up.
Second, I think there might be a bug, you can try this out on the demo site:
Searching for documents with alan AND skylab: +alan +skylab returns just one result, this is correct. Restricting the term "alan" to the name field does not seem to work, the presence modifier seems to get ignored: +name:alan +skylab returns three results.
I'll take a closer look at this, thanks for reporting.

Thank you for this quick answer.
For your information, I'm using lunr 2.1.5 (the version installed by npm install).
Regards.

Yeah, 2.1.5 does not have term presence support, you will need to upgrade to 2.2.0 to get term presence support.

I successfully installed Lunr 2.2.0.

I've just pushed 2.2.1 with a fix for the bug that caused the issues mentioned here, please take a look and let me know if you run into problems.

Hi,
This works well.
Thank you for this VERY VERY fast correction !


No package metadata was found for EukDetect

Hello,
I'm running into an error after installing EukDetect following the instructions listed here.
Here is what prints to screen when I run the test:
python tests/test_eukdetect.py
EEEE.
======================================================================
ERROR: test_class (__main__._01_HelpText)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "tests/test_eukdetect.py", line 18, in test_class
    code, stdout, stderr = run(command)
  File "tests/test_eukdetect.py", line 11, in run
    process = subprocess.run(shlex.split(command), stdout=subprocess.PIPE, stderr=subprocess.PIPE)
  File "/home/jpshaffer/software/miniconda3/lib/python3.8/subprocess.py", line 493, in run
    with Popen(*popenargs, **kwargs) as process:
  File "/home/jpshaffer/software/miniconda3/lib/python3.8/subprocess.py", line 858, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/home/jpshaffer/software/miniconda3/lib/python3.8/subprocess.py", line 1704, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'eukdetect'

======================================================================
ERROR: test_class (__main__._02_RunRunall)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "tests/test_eukdetect.py", line 25, in test_class
    code, stdout, stderr = run(command)
  File "tests/test_eukdetect.py", line 11, in run
    process = subprocess.run(shlex.split(command), stdout=subprocess.PIPE, stderr=subprocess.PIPE)
  File "/home/jpshaffer/software/miniconda3/lib/python3.8/subprocess.py", line 493, in run
    with Popen(*popenargs, **kwargs) as process:
  File "/home/jpshaffer/software/miniconda3/lib/python3.8/subprocess.py", line 858, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/home/jpshaffer/software/miniconda3/lib/python3.8/subprocess.py", line 1704, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'eukdetect'

======================================================================
ERROR: test_class (__main__._03_RunAlnCmd)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "tests/test_eukdetect.py", line 32, in test_class
    code, stdout, stderr = run(command)
  File "tests/test_eukdetect.py", line 11, in run
    process = subprocess.run(shlex.split(command), stdout=subprocess.PIPE, stderr=subprocess.PIPE)
  File "/home/jpshaffer/software/miniconda3/lib/python3.8/subprocess.py", line 493, in run
    with Popen(*popenargs, **kwargs) as process:
  File "/home/jpshaffer/software/miniconda3/lib/python3.8/subprocess.py", line 858, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/home/jpshaffer/software/miniconda3/lib/python3.8/subprocess.py", line 1704, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'eukdetect'

======================================================================
ERROR: test_class (__main__._04_RunAln_and_filter)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "tests/test_eukdetect.py", line 40, in test_class
    alncode, alnstdout, alnstderr = run(command)
  File "tests/test_eukdetect.py", line 11, in run
    process = subprocess.run(shlex.split(command), stdout=subprocess.PIPE, stderr=subprocess.PIPE)
  File "/home/jpshaffer/software/miniconda3/lib/python3.8/subprocess.py", line 493, in run
    with Popen(*popenargs, **kwargs) as process:
  File "/home/jpshaffer/software/miniconda3/lib/python3.8/subprocess.py", line 858, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/home/jpshaffer/software/miniconda3/lib/python3.8/subprocess.py", line 1704, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'eukdetect'

----------------------------------------------------------------------
Ran 5 tests in 0.011s

FAILED (errors=4)

This is what prints to screen when running help:
eukdetect --help
Traceback (most recent call last):
  File "/home/jpshaffer/software/miniconda3/bin/eukdetect", line 33, in <module>
    sys.exit(load_entry_point('EukDetect==1.0.1', 'console_scripts', 'eukdetect')())
  File "/home/jpshaffer/software/miniconda3/bin/eukdetect", line 22, in importlib_load_entry_point
    for entry_point in distribution(dist_name).entry_points
  File "/home/jpshaffer/software/miniconda3/envs/eukdetect/lib/python3.6/site-packages/importlib_metadata/__init__.py", line 558, in distribution
    return Distribution.from_name(distribution_name)
  File "/home/jpshaffer/software/miniconda3/envs/eukdetect/lib/python3.6/site-packages/importlib_metadata/__init__.py", line 215, in from_name
    raise PackageNotFoundError(name)
importlib_metadata.PackageNotFoundError: No package metadata was found for EukDetect

I did not receive any errors during installation - here is what printed to screen during installation:
python setup.py install
running install
/home/jpshaffer/software/miniconda3/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
/home/jpshaffer/software/miniconda3/lib/python3.8/site-packages/setuptools/command/easy_install.py:158: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
running bdist_egg
running egg_info
writing EukDetect.egg-info/PKG-INFO
writing dependency_links to EukDetect.egg-info/dependency_links.txt
writing entry points to EukDetect.egg-info/entry_points.txt
writing top-level names to EukDetect.egg-info/top_level.txt
reading manifest file 'EukDetect.egg-info/SOURCES.txt'
adding license file 'LICENSE'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
copying build/lib/eukdetect/runall.py -> build/bdist.linux-x86_64/egg/eukdetect
copying build/lib/eukdetect/__init__.py -> build/bdist.linux-x86_64/egg/eukdetect
copying build/lib/eukdetect/count_primary_and_secondary.py -> build/bdist.linux-x86_64/egg/eukdetect
copying build/lib/eukdetect/bam_to_pid.py -> build/bdist.linux-x86_64/egg/eukdetect
copying build/lib/eukdetect/eukdb_config_create.py -> build/bdist.linux-x86_64/egg/eukdetect
zip_safe flag not set; analyzing archive contents...
creating 'dist/EukDetect-1.0.1-py3.8.egg' and adding 'build/bdist.linux-x86_64/egg' to it
Processing EukDetect-1.0.1-py3.8.egg
EukDetect 1.0.1 is already the active version in easy-install.pth
Installing eukdetect script to /home/jpshaffer/software/miniconda3/bin

Installed /home/jpshaffer/software/miniconda3/lib/python3.8/site-packages/EukDetect-1.0.1-py3.8.egg
Processing dependencies for EukDetect==1.0.1
Finished processing dependencies for EukDetect==1.0.1

I'm running on a Linux cluster:
conda 4.11.0
Python 3.8.12
Please let me know if you have any insight into this issue, and thanks in advance for your help and the tool.

Hi Justin,
Thanks for reaching out and thanks for your interest. I haven't been able to reproduce this error. What happens when you open a python shell from within this conda env and run import eukdetect?

Thank you! The issue turned out to be with my miniconda environment not properly detecting the EukDetect environment during installation, and specifically that the wrong version of Python (3.8) was being called.


Macro trouble

/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:41:11: 41:20 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:41:11: 41:20 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:42:11: 42:18 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:42:11: 42:18 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:42:11: 42:18 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:42:11: 42:18 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:42:55: 42:58 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:42:55: 42:58 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:68:11: 68:20 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:68:11: 68:20 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:69:11: 69:18 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:69:11: 69:18 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:69:11: 69:18 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:69:11: 69:18 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:69:55: 69:58 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:69:55: 69:58 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:86:11: 86:20 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:86:11: 86:20 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:87:11: 87:18 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:87:11: 87:18 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:87:11: 87:18 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:87:11: 87:18 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:87:55: 87:58 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:87:55: 87:58 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:132:11: 132:20 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:132:11: 132:20 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:133:11: 133:18 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:133:11: 133:18 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:133:11: 133:18 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:133:11: 133:18 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:133:55: 133:58 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:133:55: 133:58 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:170:11: 170:20 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:170:11: 170:20 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:171:11: 171:18 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:171:11: 171:18 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:171:11: 171:18 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:171:11: 171:18 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:171:55: 171:58 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/dlib-0.2.0/src/lib.rs:171:55: 171:58 note: The above warning will be a hard error in the next release.
<dlib macros>:4:1: 4:10 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
<dlib macros>:4:1: 4:10 note: The above warning will be a hard error in the next release.
<dlib macros>:6:1: 6:8 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:6:1: 6:8 note: The above warning will be a hard error in the next release.
<dlib macros>:6:1: 6:8 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:6:1: 6:8 note: The above warning will be a hard error in the next release.
<dlib macros>:6:59: 6:62 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
<dlib macros>:6:59: 6:62 note: The above warning will be a hard error in the next release.
<dlib macros>:4:1: 4:10 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
<dlib macros>:4:1: 4:10 note: The above warning will be a hard error in the next release.
<dlib macros>:6:1: 6:8 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:6:1: 6:8 note: The above warning will be a hard error in the next release.
<dlib macros>:6:1: 6:8 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:6:1: 6:8 note: The above warning will be a hard error in the next release.
<dlib macros>:6:59: 6:62 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
<dlib macros>:6:59: 6:62 note: The above warning will be a hard error in the next release.
<dlib macros>:20:1: 20:10 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
<dlib macros>:20:1: 20:10 note: The above warning will be a hard error in the next release.
<dlib macros>:22:1: 22:8 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:22:1: 22:8 note: The above warning will be a hard error in the next release.
<dlib macros>:22:1: 22:8 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:22:1: 22:8 note: The above warning will be a hard error in the next release.
<dlib macros>:22:59: 22:62 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
<dlib macros>:22:59: 22:62 note: The above warning will be a hard error in the next release.
<dlib macros>:54:1: 54:10 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
<dlib macros>:54:1: 54:10 note: The above warning will be a hard error in the next release.
<dlib macros>:56:1: 56:8 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:56:1: 56:8 note: The above warning will be a hard error in the next release.
<dlib macros>:56:1: 56:8 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:56:1: 56:8 note: The above warning will be a hard error in the next release.
<dlib macros>:56:59: 56:62 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
<dlib macros>:56:59: 56:62 note: The above warning will be a hard error in the next release.
<dlib macros>:4:1: 4:10 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
<dlib macros>:4:1: 4:10 note: The above warning will be a hard error in the next release.
<dlib macros>:6:1: 6:8 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:6:1: 6:8 note: The above warning will be a hard error in the next release.
<dlib macros>:6:1: 6:8 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:6:1: 6:8 note: The above warning will be a hard error in the next release.
<dlib macros>:6:59: 6:62 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
<dlib macros>:6:59: 6:62 note: The above warning will be a hard error in the next release.
/home/servo/.cargo/registry/src/github.com-0a35038f75765ae4/x11-2.3.0/src/lib.rs:9:10: 9:28 warning: lint raw_pointer_derive has been removed: using derive with raw pointers is ok
<dlib macros>:4:1: 4:10 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
<dlib macros>:4:1: 4:10 note: The above warning will be a hard error in the next release.
<dlib macros>:6:1: 6:8 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:6:1: 6:8 note: The above warning will be a hard error in the next release.
<dlib macros>:6:1: 6:8 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:6:1: 6:8 note: The above warning will be a hard error in the next release.
<dlib macros>:6:59: 6:62 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
<dlib macros>:6:59: 6:62 note: The above warning will be a hard error in the next release.
<dlib macros>:4:1: 4:10 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
<dlib macros>:4:1: 4:10 note: The above warning will be a hard error in the next release.
<dlib macros>:6:1: 6:8 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:6:1: 6:8 note: The above warning will be a hard error in the next release.
<dlib macros>:6:1: 6:8 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:6:1: 6:8 note: The above warning will be a hard error in the next release.
<dlib macros>:6:59: 6:62 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
<dlib macros>:6:59: 6:62 note: The above warning will be a hard error in the next release.
<dlib macros>:20:1: 20:10 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
<dlib macros>:20:1: 20:10 note: The above warning will be a hard error in the next release.
<dlib macros>:22:1: 22:8 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:22:1: 22:8 note: The above warning will be a hard error in the next release.
<dlib macros>:22:1: 22:8 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:22:1: 22:8 note: The above warning will be a hard error in the next release.
<dlib macros>:22:59: 22:62 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
<dlib macros>:22:59: 22:62 note: The above warning will be a hard error in the next release.
<dlib macros>:54:1: 54:10 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
<dlib macros>:54:1: 54:10 note: The above warning will be a hard error in the next release.
<dlib macros>:56:1: 56:8 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:56:1: 56:8 note: The above warning will be a hard error in the next release.
<dlib macros>:56:1: 56:8 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:56:1: 56:8 note: The above warning will be a hard error in the next release.
<dlib macros>:56:59: 56:62 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
<dlib macros>:56:59: 56:62 note: The above warning will be a hard error in the next release.
<dlib macros>:4:1: 4:10 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
<dlib macros>:4:1: 4:10 note: The above warning will be a hard error in the next release.
<dlib macros>:6:1: 6:8 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:6:1: 6:8 note: The above warning will be a hard error in the next release.
<dlib macros>:6:1: 6:8 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:6:1: 6:8 note: The above warning will be a hard error in the next release.
<dlib macros>:6:59: 6:62 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
<dlib macros>:6:59: 6:62 note: The above warning will be a hard error in the next release.
<dlib macros>:4:1: 4:10 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
<dlib macros>:4:1: 4:10 note: The above warning will be a hard error in the next release.
<dlib macros>:6:1: 6:8 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:6:1: 6:8 note: The above warning will be a hard error in the next release.
<dlib macros>:6:1: 6:8 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:6:1: 6:8 note: The above warning will be a hard error in the next release.
<dlib macros>:6:59: 6:62 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
<dlib macros>:6:59: 6:62 note: The above warning will be a hard error in the next release.
<dlib macros>:4:1: 4:10 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
<dlib macros>:4:1: 4:10 note: The above warning will be a hard error in the next release.
<dlib macros>:6:1: 6:8 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:6:1: 6:8 note: The above warning will be a hard error in the next release.
<dlib macros>:6:1: 6:8 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:6:1: 6:8 note: The above warning will be a hard error in the next release.
<dlib macros>:6:59: 6:62 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
<dlib macros>:6:59: 6:62 note: The above warning will be a hard error in the next release.
<dlib macros>:20:1: 20:10 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
<dlib macros>:20:1: 20:10 note: The above warning will be a hard error in the next release.
<dlib macros>:22:1: 22:8 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:22:1: 22:8 note: The above warning will be a hard error in the next release.
<dlib macros>:22:1: 22:8 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:22:1: 22:8 note: The above warning will be a hard error in the next release.
<dlib macros>:22:59: 22:62 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
<dlib macros>:22:59: 22:62 note: The above warning will be a hard error in the next release.
<dlib macros>:54:1: 54:10 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
<dlib macros>:54:1: 54:10 note: The above warning will be a hard error in the next release.
<dlib macros>:56:1: 56:8 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:56:1: 56:8 note: The above warning will be a hard error in the next release.
<dlib macros>:56:1: 56:8 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:56:1: 56:8 note: The above warning will be a hard error in the next release.
<dlib macros>:56:59: 56:62 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
<dlib macros>:56:59: 56:62 note: The above warning will be a hard error in the next release.
<dlib macros>:4:1: 4:10 warning: `$stype:ty` may be followed by `functions`, which is not allowed for `ty` fragments
<dlib macros>:4:1: 4:10 note: The above warning will be a hard error in the next release.
<dlib macros>:6:1: 6:8 warning: `$stype:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:6:1: 6:8 note: The above warning will be a hard error in the next release.
<dlib macros>:6:1: 6:8 warning: `$fret:ty` may be followed by `varargs`, which is not allowed for `ty` fragments
<dlib macros>:6:1: 6:8 note: The above warning will be a hard error in the next release.
<dlib macros>:6:59: 6:62 warning: `$vargs:ty` may be followed by `...`, which is not allowed for `ty` fragments
<dlib macros>:6:59: 6:62 note: The above warning will be a hard error in the next release.

Uh.
Do you know what change in rustc caused that ?

@Ms2ger wayland-client v0.5.9 has been published and should remove any encountered problems.


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_6cor1azok8/clone/recipe/meta.yaml:18: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_6cor1azok8/clone/recipe/meta.yaml:23: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_6cor1azok8/clone/recipe/meta.yaml:24: missing_wheel: For pypi packages, wheel should be present in the host section
WARNING: /tmp/abs_6cor1azok8/clone/recipe/meta.yaml:29: python_build_tool_in_run: The python build tool pip is in run depends
WARNING: /tmp/abs_6cor1azok8/clone/recipe/meta.yaml:30: python_build_tool_in_run: The python build tool setuptools is in run depends
ERROR: /tmp/abs_6cor1azok8/clone/recipe/meta.yaml:47: missing_dev_url: The recipe is missing a dev_url
WARNING: /tmp/abs_6cor1azok8/clone/recipe/meta.yaml:47: missing_description: The recipe is missing a description
ERROR: /tmp/abs_6cor1azok8/clone/recipe/meta.yaml:47: missing_license_family: The recipe is missing the about/license_family key.
ERROR: /tmp/abs_6cor1azok8/clone/recipe/meta.yaml:47: missing_documentation: The recipe is missing a doc_url or doc_source_url
Errors were found


AI with collision layers + masks refuse to move

Description

Replicate

Spawn Xeno
It won't move

This isn't the case for other mobs.

Fixed. (Kinda).


cis_audit_profile Config Update: 'cis_' Prefix Required for Cron Job but Causes Issues with NRPE Checks

When updating the cis_audit_profile configuration in the NRPE charm, the use of the "cis_" prefix creates an inconsistency. If we set cis_audit_profile="level2_server", the cron job fails to run, but the NRPE check for CIS audit works correctly.
Conversely, when we set cis_audit_profile="cis_level2_server", the cron job runs successfully, but the NRPE check produces an error, stating that the profile is an invalid choice.
This inconsistency requires manual intervention and creates a conflict where the configuration works for one aspect but fails for the other. Ideally, the charm should handle the prefix internally to allow both the cron job and NRPE checks to function correctly without manual adjustment.

I just had a look at this and realized: This is already fixed in
https://github.com/canonical/charm-nrpe/releases/tag/rev125
However, it didn't land on stable yet, which is why we ran into this issue. Anyway, you can close the issue here.


Unable to use underscore in Enums

Enums cannot contain _ in current version.
E.g. the following JDL
entity SpecialDiet {
    type SpecialDietValue,
    other String
}
enum SpecialDietValue {
    NONE, NO_PORK, VEGETARIAN, VEGAN, OTHER
}

causes the following error
Expected ",", "}" or a space but "_" found.
undefined

I'll fix it this week-end.


Design system MVP

[x] Create repo
[x] Sync Tokens Studio tokens from Wellcome Figma with repo
[x] Set up style dictionary actions(? maybe not even necessarily MVP)
[x] Create npm module
[x] Import/use module somewhere

There's now a repo and an npm package with a very bare-bones set of tokens exported as a JS Object.
And a branch that imports the design system module and uses it to generate spacing values on wellcomecollection.org
Possible work flow

Designer creates styles in Figma
Designer saves styles in Tokens Studio
Designer pushes to GitHub repo through Token Studio ui
Developer pulls from GitHub repo
Developer runs build script in repo and increments package version number
Developer publishes package on npm
Developer tags commit with package version number and pushes back to GitHub
Developer(or bot?) communicates new package available for import with details about the changes

Next steps

Include different transforms for different products (e.g. ones that need css instead of a JS object for styles)
Include TypeScript for design system


Inconsistent errors with different commands

Bug description
The error output differs in color and pacing with different migration and introspection commands.

db pull is completely red.
db push has the Error: in red, other text in white. Missing whitespace after the Datasource.
db migrate dev is like db push, but has whitespace after the Datasource.

How to reproduce
npx prisma db pull
npx prisma db push
npx prisma migrate dev

Expected behavior
Some consistency would be great here.
Prisma information

Environment & setup
Every OS in the world.
Prisma Version
2.26.0

moar

I can reproduce this.

Fun fact, mongodb error comes from engine (similar one is in TS as well)
https://github.com/prisma/prisma-engines/blob/master/introspection-engine/core/src/rpc.rs#L80
With PR looks like