[IOTDB-3172] Support CreateMultTimeseries API for new cluster

Description
Content1 ...
Content2 ...
Content3 ...

This PR has:

[ ] been self-reviewed.

[ ] concurrent read
[ ] concurrent write
[ ] concurrent read and write

[ ] added documentation for new or modified features or behaviors.
[ ] added Javadocs for most classes and all non-trivial methods.
[ ] added or updated version, license, or notice information
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious
for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold
for code coverage.
[ ] added integration tests.
[ ] been tested in a test IoTDB cluster.

Key changed/added classes (or packages if there are too many classes) in this PR

Coverage decreased (-0.008%) to 45.842% when pulling 46f38b0a7588972e99bc32eb3a5fd88e653787ce on multitimeseries into 465b0cffbe02770058365c7e35723044bf3e7d5c on master.


Artifact versions with '+' character not supported

First of all thank you so much for building and running an immensely useful service such as javadoc.io! 😄
We're using semantic versioning for our artifacts (at least we're trying to), which means that the version could contain a '+' character to separate build metadata from the rest of the version string (also see https://semver.org/#spec-item-10).
It looks like javadoc.io currently doesn't support artifacts which contain a '+'  character in their version.
Examples
Failing

https://javadoc.io/doc/org.graylog.jest/jest/2.4.12+jackson
https://javadoc.io/doc/org.graylog.jest/jest/2.4.12%2Bjackson

Working

https://javadoc.io/doc/org.graylog.jest/jest/2.4.5

Interesting enough, this seems to be an encoding issue, too:
Failing

https://static.javadoc.io/org.graylog.jest/jest/2.4.12+jackson/index.html

Working

https://static.javadoc.io/org.graylog.jest/jest/2.4.12%2Bjackson/index.html

Likewise, using something like sbt-dynver for git commits+tags based versioning leads to the same issue, see https://javadoc.io/doc/io.laserdisc/laserdisc-core_2.12/0.1.0+3-fedc3f12

This bug also affect latest URLs.
For example, https://javadoc.io/page/com.thoughtworks.dsl/dsl_2.12/latest/com/thoughtworks/dsl/index.html redirects to https://static.javadoc.io/com.thoughtworks.dsl/dsl_2.12/1.0.0-RC22+36-6a0631d6/com/thoughtworks/dsl/index.html, which is a broken URL. The proper URL should be https://static.javadoc.io/com.thoughtworks.dsl/dsl_2.12/1.0.0-RC22%2B36-6a0631d6/com/thoughtworks/dsl/index.html.

fixed and deployed

This bug is not resolved.
https://javadoc.io/page/com.thoughtworks.binding/latestevent_sjs0.6_2.12/latest/com/thoughtworks/binding/LatestEvent.html is still a broken URL

ah, not aware there is another one. Fixed.


Add SNS mail notification in service state changes

Add SNS mail notifications deployment in terraform.
This creates automatic mail notifications en each task state change (container state changed). It is based in native cloudwatch event system.
In order to use it, use the new variable sns_subscription_email_address_list. Example:
sns_subscription_email_address_list =<EMAIL_ADDRESS><EMAIL_ADDRESS>

Team, I'm moving this to draft just in case.
For some reason now it doesn't work...
I'm researching why. The exact manual cloned it is working. There must be some super tiny details I don't see...

Ready for review after the last change. Doing this operation manually in the AWS web created a new policy entry in the Topic, which was not easy to catch. Now, the whole access policy is defined in the terraform code


Deploy on a real robot

Hi,
Thank you for sharing your work.
How would you deploy this on a real robot?
Thanks!

Thank you for your attention. If you want to deploy it on a real robot, you need to figure out the interface (IMU/joint data) between the algorithm and the robot. These interfaces are the same for the simulator and the real robot. You should input IMU and joint pos/vel etc. data to the controller, and the controller can output the joint torque required by the robot. Then the other work is to adjust the parameters.

Thank you for your attention. If you want to deploy it on a real robot, you need to figure out the interface (IMU/joint data) between the algorithm and the robot. These interfaces are the same for the simulator and the real robot. You should input IMU and joint pos/vel etc. data to the controller, and the controller can output the joint torque required by the robot. Then the other work is to adjust the parameters.

Thank you @Derek-TH-Wang, I'll play a little bit with this!

Thank you @Derek-TH-Wang, I'll play a little bit with this!


show autostart status in LspInfo

autostart can explain why a server is not active so I think it deserves a place in :LspInfo. Seems like this PR wont work though because the autostart setting is not forwarded to the generated client, there is an autostart() function in its stead.
Maybe we can rename the autostart() function ?

I ended up using saving the autostart client value in _autostart


Clicking the leave lobby button should remove you from the lobby entirely

This was not meant to be created. I misclicked a button on my task list


Automated Package Upgrade

:tada: This PR is included in version 5.0.157 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Prisma Stopping koajs server

For some reason koa works fine when I do not initialise the prisma client, but whenever I do, it breaks.
Here is a minimal reproducible example
Does not Work.
import Koa, { Context } from 'koa';
import Router from 'koa-router';
import { PrismaClient } from '@prisma/client';

const HOST = "<IP_ADDRESS>";
const PORT = process.env.PORT || 7000;

const router = new Router();
export const app = new Koa();
router.get('/', (ctx) => ctx.body = { message: 'Welcome to MikroORM Koa TS example, try CRUD on /author and /book endpoints!' });

(async () => {
    const prisma = new PrismaClient();
    app.use(router.routes())
    app.use(router.allowedMethods())
    console.log("Added Routes");
    app.use((ctx, next) => {
      ctx.status = 404;
      ctx.body = { message: 'No route found' };
    });

    app.on("error", err => {
      console.log(err);
    })

    app.listen(PORT, () => {
      console.log("Ready to roll");
    });

})();

Works.
import Koa, { Context } from 'koa';
import Router from 'koa-router';
import { PrismaClient } from '@prisma/client';

const HOST = "<IP_ADDRESS>";
const PORT = process.env.PORT || 7000;

const router = new Router();
export const app = new Koa();
router.get('/', (ctx) => ctx.body = { message: 'Welcome to MikroORM Koa TS example, try CRUD on /author and /book endpoints!' });

(async () => {
    app.use(router.routes())
    app.use(router.allowedMethods())
    console.log("Added Routes");
    app.use((ctx, next) => {
      ctx.status = 404;
      ctx.body = { message: 'No route found' };
    });

    app.on("error", err => {
      console.log(err);
    })

    app.listen(PORT, () => {
      console.log("Ready to roll");
    });

})();

Some really strange behavior here. If I try running connect on prism and running some ops it all works fine.
import Koa, { Context } from 'koa';
import Router from 'koa-router';
import { PrismaClient } from '@prisma/client';

const HOST = "<IP_ADDRESS>";
const PORT = process.env.PORT || 7000;

const router = new Router();
export const app = new Koa();
router.get('/', (ctx) => ctx.body = { message: 'Welcome to MikroORM Koa TS example, try CRUD on /author and /book endpoints!' });

  const prisma = new PrismaClient();
prisma.$connect().then(() => {
  console.log("gg");
})
prisma.tokens.count().then((c) => console.log(c));

(async () => {
    app.use(router.routes())
    app.use(router.allowedMethods())
    console.log("Added Routes");
    app.use((ctx, next) => {
      ctx.status = 404;
      ctx.body = { message: 'No route found' };
    });

    app.on("error", err => {
      console.log(err);
    })

    app.listen(PORT, () => {
      console.log("Ready to roll");
    });

})();

All of the print statements work but the order is problem. The ready to roll is printed before prisma.
TLDR;
When prisma starts it somehow kills the main koa app. So not only does the app no longer work,, even in browser/postman its  ECONNREFUSED.
Prisma information
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = "postgres://daggy:sex@localhost:5432/postgres"
}

model application {
  uu             String   @id @db.Uuid
  appname        String   @db.VarChar(255)
  appdescription String   @db.VarChar(255)
  appurl         String   @db.VarChar(255)
  appuserid      BigInt   @unique
  approved       Boolean
  premium        Boolean
  created_at     DateTime @default(now()) @db.Timestamptz(6)
  updated_at     DateTime @updatedAt @db.Timestamptz(6)
}

model tokens {
  userid     BigInt   @id
  apikey     String   @unique @db.VarChar(64)
  totaluses  Int
  enhanced   Boolean
  ratelimit  Int
  created_at DateTime @default(now()) @db.Timestamptz(6)
  updated_at DateTime @updatedAt @db.Timestamptz(6)
}

Environment & setup

OS:  Wisons
Database:  Postgresql
Node.js version:  14.15.4
Prisma version:

prisma               : 2.21.1
@prisma/client       : 2.21.1
Current platform     : windows
Query Engine         : query-engine e421996c87d5f3c8f7eeadd502d4ad402c89464d (at<EMAIL_ADDRESS>Migration Engine     : migration-engine-cli e421996c87d5f3c8f7eeadd502d4ad402c89464d (at<EMAIL_ADDRESS>Introspection Engine : introspection-core e421996c87d5f3c8f7eeadd502d4ad402c89464d (at<EMAIL_ADDRESS>Format Binary        : prisma-fmt e421996c87d5f3c8f7eeadd502d4ad402c89464d (at<EMAIL_ADDRESS>Default Engines Hash : e421996c87d5f3c8f7eeadd502d4ad402c89464d
Studio               : 0.371.0
Done in 3.68s.

Hmmm, I could run your "Does not Work." example just fine with no modifications. I put my repro repo on Github:  https://github.com/janpio/repro6602 npm install and then npx ts-node index.ts Where did I go wrong?

After trying your example, it worked. I'm trying to figure out the difference.


Fix tutorial step 7

This changes the code so that the forking of the child processes are done as intended i.e. from the parent.
Submitting under the MIT license.

Merged. Thanks!


Fix "Invalid Host/Origin" on Firefox in Angular template

The one way I've found to do this so far is by passing --disable-host-check in the ng serve command. That has security implications though, so I'm going to see if I can get it to work in a way that's safer.

I've found no way to make this work without the --disable-host-check command, and to the best of my knowledge this is purely a problem between webpack-dev-server and Firefox (it seems Firefox doesn't send the Origin header in this case which is expected by webpack-dev-server).
I talked it over with @blowdart and we agreed that applying the --disable-host-check setting in the templates would be bad. The plan for now is to wait for webpack-dev-server to fix this and for that to bubble up through Angular.
Options for people experiencing this issue:

Ignore it (it only affects Hot-Module reloading, regular site functionality still works).
Use a different browser.
Set the --disable-host-check on your ng serve command (Be sure you don't put this setting in production as it has security implications, and also be sure to revert this when the fix is available).

Dupe of https://github.com/aspnet/AspNetCore/issues/7812

Not really. You created this issue to separate the Firefox "Invalid Host/Origin" thing from https://github.com/aspnet/AspNetCore/issues/7812, which now tracks the WebSocket connection to 'ws://localhost:4568/ws/379/lsb17jhg/websocket?X....' failed: WebSocket is closed before the connection is established error.
I do think we should close this issue though as we have no plan to take an action (except eventually take a new version of Angular, which will happen anyway).


fix: better type, make it node safe

Improved types
Made it work on node

@trassmann You changes have been released in 1.1.2 https://www.npmjs.com/package/react-debounced/v/1.1.2


Idenfifying a word as token in the editor

monaco-editor version: 0.14.3
Browser:Chrome
OS: Windows
Steps or JS usage snippet reproducing the issue:
From Hover provider example in monaco playground
i got the Hovers word with the below code
var keyword=model.getWordAtPosition(position).word
but how can i identify whether the word is a keyword or identifier or some other token that we have registered??

There is currently no API to retrieve the token types because they are not stored anywhere. Only the resulting colors are stored.
You can use the independent API monaco.editor.tokenize(text, languageId).


Add support for stream responses

Currently hypernova-node returns all rendered html as a string which doesn't allow us to do response streaming in a hypernova setup.
https://github.com/airbnb/hypernova-node/blob/e19a76152689dc1c46d2233481abc3b9d15ee65f/src/index.js#L4-L6
https://github.com/airbnb/hypernova-node/blob/e19a76152689dc1c46d2233481abc3b9d15ee65f/src/index.js#L35
Proposal, create a plugin to enable streaming responses

Were you able to figure out response streaming?

Didn't explore this any further, we use varnish to assemble our components in our page. As a side effect we benefit from the HTML streaming that Varnish provides.


BadAuthentication Error

After entering my account credentials and setting Raccoon up as a new device I am getting the error Error=BadAuthentication
Sometimes I am also getting a message that two-factor authentication may be enabled directly after entering the credentials, which is not true in my case.
I even tried to create a new Google Account but it had the same error.
Here is the full log:
2017-06-03 17:50:18.267:INFO:oejs.Server:jetty-8.y.z-SNAPSHOT 2017-06-03 17:50:18.366:INFO:oejs.AbstractConnector:Started SelectChannelConnector@<IP_ADDRESS>:36435 com.akdeniz.googleplaycrawler.GooglePlayException: Error=BadAuthentication 	at com.akdeniz.googleplaycrawler.GooglePlayAPI.executeHttpRequest(GooglePlayAPI.java:585) 	at com.akdeniz.googleplaycrawler.GooglePlayAPI.executePost(GooglePlayAPI.java:543) 	at com.akdeniz.googleplaycrawler.GooglePlayAPI.executePost(GooglePlayAPI.java:522) 	at com.akdeniz.googleplaycrawler.GooglePlayAPI.loginAC2DM(GooglePlayAPI.java:182) 	at com.akdeniz.googleplaycrawler.GooglePlayAPI.checkin(GooglePlayAPI.java:165) 	at de.onyxbits.raccoon.setup.UploadLogic.onDoInBackground(UploadLogic.java:89) 	at de.onyxbits.raccoon.setup.WizardWorker.doInBackground(WizardWorker.java:36) 	at javax.swing.SwingWorker$1.call(SwingWorker.java:295) 	at java.util.concurrent.FutureTask.run(FutureTask.java:266) 	at javax.swing.SwingWorker.run(SwingWorker.java:334) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 	at java.lang.Thread.run(Thread.java:745)
I am running Antergos Linux with JDK & JRE 8 installed

http://blog.onyxbits.de/and-google-broke-raccoon-again-2-625/

Oh okay, my fault. Didn't see that blog post there...

It's possible now use "App password"
App passwords let you sign in to your Google Account from apps on devices that don't support 2-Step Verification. You'll only need to enter it once so you don't need to remember it. Learn more
Create specific password for racoon and use that on it.


Make expectations in FactCheckingEvaluator's prompt more explicit

FactCheckingEvaluator has the following prompt template:
Document: \n {document}\n
Claim: \n {claim}

But there is no clear expectation set as to how the LLM should respond. Meanwhile, the decision as to whether the evaluation passes or not, is based simply on whether the response to that prompt be "yes" or not.
What I've found is that more often than not, the response to that prompt is a long-winded explanation as to why (or why not) the claim is supported by the document. Even if the response includes the word "yes", it's not solely "yes" and therefore equalsIgnoreCase() returns false.
I propose that the prompt be modified to include very explicit instructions to direct it to return "yes" or "no". Something like this:
Respond with only the single word "yes" if the document supports the claim made. Otherwise respond "no".
Document: \n {document}\n
Claim: \n {claim}

When run against Minstral:7B and Llama3.2 in Ollama, the result is more consistently in line with the factuality of the claim.

See also this PR from October: https://github.com/spring-projects/spring-ai/pull/1605


[feat] Use pyproject.toml in current path by default

The flag --toml-path  to provide --toml-path pyproject.toml can have default pyproject.toml .
I think the flag is useful whenever the file is not in my current path.

Changing the default is not backwards compatible


Better comments in eviction policy.

@zuyu This will help explain better the meaning of 'block' in the Eviction Policy classes.

LGTM!


⚠ Bofrost.be has degraded performance

In a02864a, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1566 ms

Resolved: Bofrost.be performance has improved in 0caa818 after 6 minutes.


the train loss is nan

hi! thanks for your work ,when  i train this repo i get nan loss no matter use the resnet18 or using the resnet50. can you give me some advices,thank you !

Me Too.this problem will occur while i use loss_coor in final loss.

Maybe, drop learning rate by ten times or five times.


FreeBSD and general POSIX

Changes:
POSIX_NANA for common code bits.
thread_t for the thread id (unsigned didn't work on 64 bit).
NANA_UNICODE defaults to "UTF-32LE" unless you say otherwise on the command-line.
Primitive audio for OSS compliant systems like FreeBSD.
nana::system::open_url works - if you have Firefox. Code is written so that generalizing to detect browsers is easy.
Risks:
I have not tested Windows or Linux. I estimate risk to Windows platform is very low. I am more concerned about Linux in case I over-generalized POSIX commonality. Mac OSX should be no worse than before. I suspect the unicode fix here also applies to Mac.
I can test on Windows 7/8/10 and Linux (either Slackware or Ubuntu) but will need more time. I cannot test Mac OSX.
The use of posix_spawn for open_url should be reviewed for any security concerns.

Hi Jinhao,
I suggest you to open a new "feature" branch based on your develop branch to hold this. We need that someone else more test this, to be included in the next version.
Great contribution.
Thank @Unitrunker

Our user blab compiled this in MacOSX  !!

I started a new feature-freebsd-posix branch for this PR

awesome!


Implement Enclave Pool for Docker backend

Background & motivation
The enclave pool v0 was released on 17 Jul and it's enabled for Kubernetes Backend.
We can implement the enclave pool v1 described in this document: for enabling Docker support
Desired behaviour
Enclave pool works on the Docker backend, it will reduce the create enclave time.
How important is this to you?
Nice to have; this feature would make using Kurtosis more enjoyable.

@leoporoli can we do this with all the persistence work?
I'm adding myself as an assignee so that I don't forget.


⚠ Bofrost.be has degraded performance

In 4c7b01b, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1471 ms

Resolved: Bofrost.be performance has improved in 0946aac.


[c++] Use core 2.21.2

Issue and/or context: 2.21.2 is out and ready to use.
Changes:
Notes for Reviewer:

Ahh thanks @eddelbuettel maybe we should pin 2.21.1 within this Conda feedstock's recipe/meta.yml ... 🤔
Per @jdblischak on a previous PR we'd left it loose on purpose (>= 2.21.0) but maybe on this occasion we do need that tighter pin ... thanks, I'll put up my next attempt as a commit very soon ...

@johnkerl What do you think about comparing 'a.b' out of 'a.b.c' for equality?  It is the minor we increment with Core releases, and it is that part that bites us.  Methinks we were too eager and I need to adjust #2410 with a follow-up.  Thoughts?

We need to enforce that.

"Yes but ..."  If you enforce that then you just got yourself a new (recurring) task of ensuring such tiledb-r versions are built.  This is neither a goal nor target  of tiledb-r.  Happy to tag releases at GH but if you want lockstep releases (that are very much out if sync with coarser 'major only' CRAN releases) you have to ensure you have them.  It's very doable via r-universe and you (as 'consumer of the builds' via SOMA) can drive and schedule their 'production'.  And as you say, once the C++-ification finishes it won't be an issue.

@eddelbuettel thank you and I'll take that risk, and I'll revert #2410. I will not make undefined behavior a Plan A -- and having two distinct copies of core in memory is very much undefined behavior.

Note
https://github.com/single-cell-data/TileDB-SOMA/actions/runs/8619791560/job/23625231688
shows us finding correct core versions:
Run Rscript -e 'tiledbsoma::show_package_versions()'
tiledbsoma:    <IP_ADDRESS>
tiledb-r:      0.25.0
tiledb core:   2.21.2
libtiledbsoma: 2.21.2
R:             R version [4](https://github.com/single-cell-data/TileDB-SOMA/actions/runs/8619791560/job/23625231688#step:9:5).3.3 (2024-02-29)
OS:            Ubuntu 22.04.4 LTS

These are compatible with one another: 2.21.2 == 2.21.2.
Meanwhile on the Python side (same job) we have
Run python -c 'import tiledbsoma; tiledbsoma.show_package_versions()'
  python -c 'import tiledbsoma; tiledbsoma.show_package_versions()'
  python scripts/show-versions.py
  shell: /usr/bin/bash -e {0}
  env:
    pythonLocation: /opt/hostedtoolcache/Python/3.11.9/x64
    PKG_CONFIG_PATH: /opt/hostedtoolcache/Python/3.11.9/x64/lib/pkgconfig
    Python_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.9/x64
    Python[2](https://github.com/single-cell-data/TileDB-SOMA/actions/runs/8619791560/job/23625231688#step:12:2)_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.9/x64
    Python3_ROOT_DIR: /opt/hostedtoolcache/Python/[3](https://github.com/single-cell-data/TileDB-SOMA/actions/runs/8619791560/job/23625231688#step:12:3).11.9/x64
    LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.11.9/x6[4](https://github.com/single-cell-data/TileDB-SOMA/actions/runs/8619791560/job/23625231688#step:12:4)/lib
tiledbsoma.__version__        1.[5](https://github.com/single-cell-data/TileDB-SOMA/actions/runs/8619791560/job/23625231688#step:12:5).0rc0.post293.dev101001[6](https://github.com/single-cell-data/TileDB-SOMA/actions/runs/8619791560/job/23625231688#step:12:6)52
TileDB-Py tiledb.version()    (0, 27, 1)
TileDB core version           2.21.1
libtiledbsoma version()       libtiledb=2.21.2
python version                3.11.9.final.0
OS version                    Linux 6.5.0-101[7](https://github.com/single-cell-data/TileDB-SOMA/actions/runs/8619791560/job/23625231688#step:12:7)-azure
tiledbsoma.__version__    1.5.0rc0.post293.dev101001652
tiledb.version()          0.27.1
core version              2.21.1
anndata.__version__  (ad) 0.10.7
numpy.__version__    (np) 1.26.4
pandas.__version__   (pd) 2.2.1
pyarrow.__version__  (pa) 15.0.2
scanpy.__version__   (sc) 1.10.1
scipy.__version__    (sp) 1.13.0
python__version__         3.11.[9](https://github.com/single-cell-data/TileDB-SOMA/actions/runs/8619791560/job/23625231688#step:12:9)

which are also compatible with one another -- 2.21.1 == 2.21.1 -- but not at 2.21.2.
Therefore I'll pause this PR until there is a TileDB-Py bump up to depending on 2.21.2. cc @ihnorton @nguyenv .

@johnkerl Awesome find.  I live under 2.23.0 but had somehow (wrongly convinced myself we'd get 2.21.1 not .2. So disregard my concern (at least for now).

It looks like we'll have a tiledbsoma 1.10 with core 2.20 soon, so, I'll abandon this.


Add support for Provider version involvement check resolution

Is your feature request related to a problem? Please describe.
When evaluating checks, the version of the provider should be taken into account. This is brought to light by recent changes to GCP provider to v3 which has breaking changes
Describe the solution you'd like
When there is a material change between provider versions, the used version should be taken into account
Additional context
See https://github.com/aquasecurity/tfsec/issues/1024 for an example

The adapters can take care of this once we hit v1.

I think this is now an adapter responsibility - they will have to handle different provider implementations e.g. trying multiple attributes when an attribute has been renamed etc. I guess they could read provider blocks and act specifically on the version there too.


index.html did not match any routes - react js

I'm confused. without html-webpack-plugin plugin I can run my project and it works fine:
yarn start

url:
http://localhost:3000/
My project is finished. now I want to build my project and I want to upload on server.
my project works with Api.
now, I think I should use html-webpack-plugin to get a build file.
to do this I run this command:
npm run build

and It makes a dist directory that inside of it is:

after click on index.html I got this error message:
index.html" did not match any routes
I have installed:
npm install -g serve

then use this comment:
serve -s build

now, I upload whole dist directory on my server and I got this error message:
Warning: [react-router] Location "/test20/index.html" did not match any routes

http://www.shadyab.com/test20/index.html
whole my project:
https://github.com/smemamian/shadyab

This is a bug tracker, not a support system. For usage questions, please use Stack Overflow or Reactiflux where there are a lot more people ready to help you out. Thanks!

I used stackoverflow and I cannot find any solutions.
https://stackoverflow.com/questions/49953670/index-html-did-not-match-any-routes-react-js


Add examples for multisig propose of generic method/params

We need to add an example (or support if not possible yet) for multisig operations that can handle generic methods and parameters.

Whats the status of this?


docs: add script to push latest docs from cli repo to the website

Description
This pull request creates the workflow to push latest docs from the cli repo to asyncapi.com/docs
Related issue(s)
This pull request is a continuation from Docs: add CLI docs to tools content bucket #1078 and also resolves issue Integrate CLI docs with asyncapi website #448

/rtm

@activus-d now to make sure it works, we need to make some changes in docs folder. You can open a PR that updates the usage markdown document and above COMMANDS add:
TOPICS
  config    CLI config settings
  generate  Generate models and template
  start     Start AsyncAPI studio

to make sure it works, we need to make some changes in docs folder. You can open a PR that updates the usage markdown document and above COMMANDS ad

@derberg I have made the required changes and made a pull request

@activus-d look, automation worked like a charm -> https://github.com/asyncapi/website/pull/1591/files

@activus-d look, automation worked like a charm -> https://github.com/asyncapi/website/pull/1591/files

@derberg Whooho🕺🕺🕺! So amazing to see🎉🎉🎉

ok, but something got wrong, in preview only one doc is visible https://deploy-preview-1591--asyncapi-website.netlify.app/docs/tools/cli/usage 🤔

ok, but something got wrong, in preview only one doc is visible https://deploy-preview-1591--asyncapi-website.netlify.app/docs/tools/cli/usage 🤔

@derberg I can see that. The index and the installation docs are missing. That's strange

@activus-d I think it is website bug, investigating

@activus-d ok, got the fix, do you want to fix it? small PR to CLI repo. I can explain

actually I opened a PR https://github.com/asyncapi/cli/pull/525 as there were bit more things to fix


Update image/text : Render Target -> GPU Texture  &  few typo.

Update image and text : Render Target -> GPUTexture.

Few typo, Skinned-Model & Script Restriction.

Thanks!


combine imparative and declarative containers

This is a feature request as I did not see a template for feature requests. I like nixos-containers, and I would like to have a mixed approach:

declare the container and its network parameters and capabilities in configuration.nix BUT without specifying any config = {...}; for it
install/update the container only via nixos-container update --config-file ...

so I made this possible by slightly changing modules/virtualisation/nixos-container.nix
I changed the definition of the path option to

            path = mkOption {
              type = types.nullOr types.path;
              default = null;
              ...

and in the file created via environment.etc."/nixos-containers/" I changed the first line to
              ${optionalString (cfg.path != null) "SYSTEM_PATH=${cfg.path}"}

and when I tried to update/start the container I simply created the directories manually that it complained about where non-existant. I suppose one could easily fix this as well...


Apply: Comments beautifier and library consolidation

Added: Convar flags for separate and server controlled convars to library
Optimized: Add material to library so it can be used in other sources
Rearange: TransformPortal Shorten variable names and return created zero vectors. Use angle copy instead of assign

It has to use a SOLID enum for not to break physics when the value of the solid is changed.

This consolidates the library and ditches the dedicated local function inside every sent making it a lot nicer. Remove the functions and send them to the dedicated library.

https://user-images.githubusercontent.com/9112662/159005867-3cc760e8-f822-4baf-8017-7dbde782dac8.mp4

Hello @Mee12345
What changes do you require to merge this. As I see you are worried about calling a global table is a tiny bit slower. I can:

Localize the SeamlessPortals library reference

Anyone will be able to add custom methods to it
If they replace a method and crash the addon it is their fault ;)

Localize the the library functions themselves by doing local setPlacement = SeamlessPortals.SetPortalPlacement:

This will reduce the extra method hash lookup and improve performance
You have to reload the other files that depend on the library when you develop them

Use the old style of making modules:

This thing is less secure
Some systems have deprecated this to some extend.

Use the new style of making the module ( First example )

It is more secure
It is not deprecated
Files will use their own reference to the library

hm, ok
personally I like option 1, but id have to playtest your fork to make sure it works exactly the same, (or hopefully smoother) since any small imperfect detail (mostly when teleporting) ruins the immersion of the portals


Delayed job 3.0.1 not working, breaks on to_yaml

Backtrace
[GEM_ROOT]/gems/delayed_job-3.0.1/lib/delayed/psych_ext.rb:6:in `encode_with'
[GEM_ROOT]/gems/activerecord-3.2.0/lib/active_record/base.rb:646:in `to_yaml'
/usr/local/rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/syck/rubytypes.rb:19:in `node_export'
/usr/local/rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/syck/rubytypes.rb:19:in `add'
/usr/local/rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/syck/rubytypes.rb:19:in `block (3 levels) in to_yaml'
/usr/local/rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/syck/rubytypes.rb:18:in `each'
/usr/local/rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/syck/rubytypes.rb:18:in `block (2 levels) in to_yaml'
/usr/local/rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/syck/rubytypes.rb:17:in `map'
/usr/local/rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/syck/rubytypes.rb:17:in `block in to_yaml'
/usr/local/rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/syck.rb:401:in `call'
/usr/local/rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/syck.rb:401:in `emit'
/usr/local/rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/syck.rb:401:in `quick_emit'
/usr/local/rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/syck/rubytypes.rb:16:in `to_yaml'
[GEM_ROOT]/gems/delayed_job-3.0.1/lib/delayed/backend/base.rb:80:in `payload_object='
[GEM_ROOT]/gems/activerecord-3.2.0/lib/active_record/attribute_assignment.rb:85:in `block in assign_attributes'
[GEM_ROOT]/gems/activerecord-3.2.0/lib/active_record/attribute_assignment.rb:78:in `each'
[GEM_ROOT]/gems/activerecord-3.2.0/lib/active_record/attribute_assignment.rb:78:in `assign_attributes'
[GEM_ROOT]/gems/activerecord-3.2.0/lib/active_record/base.rb:488:in `initialize'
[GEM_ROOT]/gems/delayed_job-3.0.1/lib/delayed/backend/base.rb:28:in `new'
[GEM_ROOT]/gems/delayed_job-3.0.1/lib/delayed/backend/base.rb:28:in `enqueue'
[GEM_ROOT]/gems/delayed_job-3.0.1/lib/delayed/message_sending.rb:13:in `method_missing'

$ rails -v
Rails 3.2.0
$ ruby -v
ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-darwin11.3.0]

I have verified that the call works when called normally. The database migration for 3.0 has been applied.

Any updates to this issue?

Yeah I am a little confused by this (in psych_ext.rb):
class ActiveRecord::Base
def encode_with(coder)
coder["attributes"] = @attributes
coder.tag = ['!ruby/ActiveRecord', self.class.name].join(':')
end
end
...  ActiveRecord's has in it:
  # Hackery to accomodate Syck. Remove for 4.0.
  def to_yaml(opts = {}) #:nodoc:
    if YAML.const_defined?(:ENGINE) && !YAML::ENGINE.syck?
      super
    else
      coder = {}
      encode_with(coder)
      YAML.quick_emit(self, opts) do |out|
        out.map(taguri, to_yaml_style) do |map|
          coder.each { |k, v| map.add(k, v) }
        end
      end
    end
  end

So, in my case, YAML::ENGINE.yamler is syck, so encode_with() is being called with {} (an empty hash) as the argument...  Then encode_with is being overwritten by delayed_job's psyche_ext.rb, and it's trying to call .tag= on that empty hash, which does not respond to that method name.

Ok-- for me there were two issues here...

we are using Syck instead of Psych...  When the server launches, the gems are loaded before the environment / initializers, so delayed_job's yaml_ext.rb was hit first, and the YAML.parser.class was Psych..
require 'yaml'
if YAML.parser.class.name =~ /syck|yecht/i
require File.expand_path('../syck_ext', FILE)
require File.expand_path('../serialization/active_record', FILE)
else
require File.expand_path('../psych_ext', FILE)
end

But then in our environment we were setting YAML::ENGINE.yamler = "syck"
... So ActiveRecord would know we were using Syck, but DelayedJob would still be thinking we're using Psych...  So the solution was to put the YAML::ENGINE.yamler setter into boot.rb so that it got set prior to gems being loaded.

Several months ago, Delayed Job's syck_ext.rb file had in it:
def yaml_tag_read_class(name)
Constantize the object so that ActiveSupport can attempt
its auto loading magic. Will raise LoadError if not successful.

When requiring yaml, the parsers redefine the YAML constant. This causes an
issue with poorly formatted yaml, specifically in the case of a Bad Alias.
When you'd expect to see Syck::BadAlias, the name we're getting is
YAML::Syck::BadAlias and trying to constantize this results in an uninitialized constant Syck::Syck.
name.gsub(/^YAML::/, '').constantize
name
end

This method is now currently:
def yaml_tag_read_class(name)
  # Constantize the object so that ActiveSupport can attempt
  # its auto loading magic. Will raise LoadError if not successful.
  name.constantize
  name
end

... So the solution was to create a config/initializers/delayed_job.rb file and put in it:
# to fix issue with uninitialized constant Syck::Syck error
class Module

  def yaml_tag_read_class(name)
    # Constantize the object so that ActiveSupport can attempt
    # its auto loading magic. Will raise LoadError if not successful.
    name.gsub!(/^YAML::/, '') if name =~ /BadAlias/
    name.constantize
    name
  end

end

and now everything is working...

Go into your rails console and type "YAML.parser.class" ...  Is is Psych or Syck?

1.9.3p0 :004 > YAML.parser.class
 => Syck::Parser

Am I missing an initializer somewhere that forces it to be psych?

Yeah so this is the same thing that was happening for me..  when your rails app boots up, it is using Psych, and DelayedJob picks up on that and therefore uses the psych_ext.rb file instead of syck_ext.rb...  but then somewhere during or after your app's initialization, the yaml parser is being set to Psych.
You could try putting in your environment.rb file:
require 'yaml'
YAML::ENGINE.yamler = 'psych'

either that or do what I did and put in boot.rb before your gemfile is picked up:
require 'yaml'
YAML::ENGINE.yamler = 'syck'

Forcing psych in environment fixed it. Thanks.


Fable Privacy

Sam B is developing some guidance to align product teams on how to approach privacy using fable. I'm helping her collect info on how our team currently approaches using fable. Some Qs looking to answer:


Evaluation of Lidar-only model works, but Camera-only fails

Hi,
My GPU is one 4060(laptop, 8GB). Cuda version: 11.8
Environment:
mmcv-full = 1.4.0
mmdet = 2.20.0
mmdet3d = 0.0.0
nuscenes-devkit = 1.1.10
torch = 1.9.1+cu111
When I use "torchpack dist-run -np 1 python tools/test.py configs/nuscenes/det/transfusion/secfpn/lidar/voxelnet_0p075.yaml pretrained/lidar-only-det.pth --eval bbox" to evaluate the lidar-only model, it works:

However, when I use "torchpack dist-run -np 1 python tools/test.py configs/nuscenes/det/centerhead/lssfpn/camera/256x704/swint/default.yaml pretrained/camera-only-det.pth --eval bbox" to evaluate the camera-only model, it fails:

Is this an environment version issue or OOM issue?
Best wishes!

It was an environmental problem, and now it is solved. Thanks.

@Terencedu  How did you solve the Issue? I have the exact opposite, Image worked, Lidar is failing with the same error handle


[ai-form-recognizer] Updated CHANGELOG for release

I neglected to add a changelog entry, so this PR fixes that.

/azp run js - ai-form-recognizer - tests

/azp run js - ai-form-recognizer - tests

/check-enforcer evaluate

/check-enforcer override


removing scratch to tiled instead of float

How make removing scrathpad automaticaly tiled? By default it's float after removing. Guess it would be more convinient.

Add this in scratchpad_remove-s nested if-elseif-elseif -s:
selmon->sel->isfloating = 0;
focus(NULL); // or focus(scratchpad_last_showed_1);
arrange(selmon);


[bugfix] Update verify popup in homepage to wrap on overflow and copy text

Problem
If you go to the nostr.directory homepage right now and click on the verification popup, there are two issues:

The verification text overflows which is unfriendly for mobile clients or smaller window sizes
The copy to clipboard button doesn't do anything

See screenshot below:

Proposed Fix
Adding overflow-wrap property to the code block so line breaks can be inserted for a better visual experience, and an onclick method to the copy button so the verification text can be copied to the user's clipboard.
Tested by running the changes with gitpod

Relatively small change so I skipped making an issue, feedback/review welcome! :)

@ng5jr @pseudozach first PR in this repo, not sure what the etiquette is so tagging you here for review 😃

awesome thanks!


ci: Release job is failing

https://github.com/GaloisInc/cclyzerpp/actions/runs/3208051718/jobs/5243563944
unauthorized: unauthenticated: User cannot be authenticated with the token provided.

This is probably a result of https://github.com/GaloisInc/cclyzerpp/pull/44

Fixed the first issue by logging into GHCR, new issue is:

#10 [5/5] COPY ./build/libPAPass.so /opt/cclyzer++/lib/
#10 sha256:62992c4c091d608f8733a2d8c621f50c1e094507da24425f850d9bc3c66da6d8
#10 ERROR: failed to walk /var/lib/docker/tmp/buildkit-mount2243961720/build: lstat /var/lib/docker/tmp/buildkit-mount2243961720/build: no such file or directory

#7 [3/5] COPY ./build/factgen-exe /opt/cclyzer++/bin/
#7 sha256:f2cf734cb6270c4661433ca46ff795745037b0c149083332ffce3006411a0fc3
#7 ERROR: failed to walk /var/lib/docker/tmp/buildkit-mount2431196952/build: lstat /var/lib/docker/tmp/buildkit-mount2431196952/build: no such file or directory

#9 [4/5] COPY ./build/libSoufflePA.so /opt/cclyzer++/lib/
#9 sha256:f44fcee00647fab1dd6f582716d97bb6156b8e7e0deaedced923c5d540fbc22e
#9 ERROR: failed to walk /var/lib/docker/tmp/buildkit-mount3815555695/build: lstat /var/lib/docker/tmp/buildkit-mount3815555695/build: no such file or directory
------
 > importing cache manifest from ghcr.io/galoisinc/cclyzerpp-dist:b62d2c126e84cd0e2ec7c3e5a63124db2aebd8d8~1:
------
------
 > [3/5] COPY ./build/factgen-exe /opt/cclyzer++/bin/:
------
------
 > [4/5] COPY ./build/libSoufflePA.so /opt/cclyzer++/lib/:
------
------
 > [5/5] COPY ./build/libPAPass.so /opt/cclyzer++/lib/:
------
failed to compute cache key: failed to walk /var/lib/docker/tmp/buildkit-mount2243961720/build: lstat /var/lib/docker/tmp/buildkit-mount2243961720/build: no such file or directory
Error: Process completed with exit code 1.

Fixed: https://github.com/GaloisInc/cclyzerpp/actions/runs/3208162995/jobs/5243771029


Remove sensors init

The initialization code is redundant and incomplete (only the first sensor
is done). I verified that all drivers already set this on startup.
For the mags, they all set their maximum supported update rate.
For the baro, the call (in sensor init) can silently fail, as for example the MS5611 which
does not support 150Hz update. But it also sets the maximum in
initialization.
Tested on Pixhawk & pixracer.

Tested with Gazebo again, and it was ok.


Why is the minimum keep alive 30 seconds?

Why is the minimum keep alive 30 seconds?
This seems like an arbitrary number and quite high. Why not allow smaller times?

I would ask the opposite question, do you have a use-case where you would need a shorter time than that?
The only reason you would need a keep alive under 30 seconds would be if your database server closes connections automatically that have been quiet for 30 seconds, and this seems like an unlikely situation.

Yes, we would like to have a 15 second keep alive. Yes, our DB is currently configured to close connections every 15 seconds in some circumstances.

But why would you have such a configuration. What problem does that solve?
This context would be helpful to be able to understand what actually needs
exist. It seems like if your database closes connections that quickly you
wouldn’t really want to use a keepalive in the first place. Would it make
more sense to increase the idle timeout in the database for this known
application rather than require the application to send otherwise
unnecessary traffic just to keep the connection open.
If the short timeout is to avoid leaked connections, surely you don’t have
that problem with the application running HikariCP.
On Tue, Sep 19, 2023 at 8:20 PM Jordan Zimmerman @.***>
wrote:

Yes, we would like to have a 15 second keep alive. Yes, our DB is
currently configured to close connections every 15 seconds in some
circumstances.
—
Reply to this email directly, view it on GitHub
https://github.com/brettwooldridge/HikariCP/issues/2112#issuecomment-1725308968,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHTCJFJPPNFDADOWCHQCB3X3F5YXANCNFSM6AAAAAA46DAHKE
.
You are receiving this because you commented.Message ID:
@.***>

After investigating even more and actually trying to set the value to something less than 30 seconds I found where the check is. I also looked over the original pull request, and have come to the determination that I still do not know why there is a minimum and nothing in the original pull request seems to shed any light on it.
I'm not completely against lowering that minimum check, but I would like to know the specifics of the situation that actually requires such a short idle timeout.

I apologize if my tone sounded argumentative.

No worries - thank you for your time

I'm not completely against lowering that minimum check, but I would like to know the specifics of the situation that actually requires such a short idle timeout.

We are going to change our timeout to 30s. But, for the future I'll try to put together a PR with a proposed change and an explanation of what we're trying to accomplish.
Thank you.

Except if there is a reason for it, I think the lib should just let the user sets the value it wants. Its pretty sneaky to disable keepalive when below 30s. A use case: fast detection of writer becoming a reader, without relying on max lifetime. (ok it relies on the fact that the keep alive task uses the validation query AND evicts the connection on failure, so maybe thats also a little sneaky on my part).

How about giving a warning log when keepaliveTime is set below 30 or a number ??

I haven't really investigated this yet, but I'm concerned about how the scheduling of the housekeeper thread works. It seems plausible that even with a setting below 30, if the housekeeper doesn't run it won't matter. So if the housekeeper is running in increments of 30 seconds, then a setting less than 30 seconds wouldn't be honored anyway.
But again, I haven't really investigated this. It's just a feeling.

@lfbayer I can help investing , but can you explain more about what should be investigate clear ?  Im not quite understand what folks above are trying to say (Sorry for that, I'm not english native speaker so it's a lil hard for me sometime to get others meaning)

I haven't really investigated this yet, but I'm concerned about how the scheduling of the housekeeper thread works. It seems plausible that even with a setting below 30, if the housekeeper doesn't run it won't matter. So if the housekeeper is running in increments of 30 seconds, then a setting less than 30 seconds wouldn't be honored anyway.
But again, I haven't really investigated this. It's just a feeling.

@lfbayer Hi! I also do some investigated, but found out there isn't any keepaliveTime related code you mentioned in that commit left?

I haven't really investigated this yet, but I'm concerned about how the scheduling of the housekeeper thread works. It seems plausible that even with a setting below 30, if the housekeeper doesn't run it won't matter. So if the housekeeper is running in increments of 30 seconds, then a setting less than 30 seconds wouldn't be honored anyway.
But again, I haven't really investigated this. It's just a feeling.

I check what HouseKeeper thread handle., but don't see anything in HouseKeeper related with keepAlive.

As I said, it was just a suspicion. The real question is probably if we allow the setting, does it actually cause the keep alive to run at the expected time?

I create a simple SpringBoot project on my local machine, which have configuration in applicaiton.properties like below
spring.datasource.hikari.keepalive-time=20000
spring.datasource.hikari.minimum-idle=1
spring.datasource.hikari.maximum-pool-size=5

and -Dcom.zaxxer.hikari.housekeeping.periodMs=40000 set in system properties.

From the console log above , we can see the keepAlive do run every 18 seconds and houseKeeper do run every 38 seconds, which is correspond to configuration.
So i guess, no matter of what keepAliveTime and HouseKeeper are set to, keepAlive task will still in the way we configure.

@lfbayer , I see you put "volunteer-needed" label. Does it mean you came to conclusion that 30s minimum for keep-alive doesn't have enough arguments to exist and you just need someone to open PR?


⚠ Processors has degraded performance

In 0280f9d, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 102 ms

Resolved: Processors performance has improved in b694eb4.


Make dispatch benchmark functions unroll multiple iterations to amortize overhead

The current benchmark functions are not useful for timing as they involve a full round trip through the synchronous API: this means that for each kernel being executed once we are calling into the VM, allocating buffers (soon to be reduced by some work will still happen), creating and recording a command buffer, submitting that command buffer to the queue, {{adding random variance}}, executing the single kernel on the queue, and then winding all the way back out again. This makes the numbers largely meaningless. They can still be useful for correctness testing (isolating the dispatches and debugging them independently), but to get useful timing we need to increase the work being done relative to the overhead of doing the work.
The benchmark tool has the KeepRunningBatch feature for this:
https://github.com/google/benchmark/blob/7fa6f1f91a96d8763de754810710d457f7fea575/include/benchmark/benchmark.h#L485-L495
This allows us to generate code for dispatching N times (128, 256, 1024, etc) and then telling that to the benchmark tool such that it prints us nice statistics as if we had run them individually.
A pass should then find the dispatches and duplicate them - so for example each dispatch would get repeated into multiple. If the current pass creates the exported functions then a new RepeatDispatchesPass that runs after HAL transformation is easy: walk functions and find each hal.command_buffer.dispatch and just clone it N times (or put it in a for loop) based on a flag indicating the repetition count.
Example:
func @my_exported_dispatch_benchmark_fn() {
  ...
  hal.command_buffer.dispatch.symbol %arg0, @ex::@backend::@entry0, workgroup_xyz = [%0, %1, %2]
  ...
}

-> -iree-hal-repeat-dispatches=6 ->
func @my_exported_dispatch_benchmark_fn() {
  ...
  hal.command_buffer.dispatch.symbol %arg0, @ex::@backend::@entry0, workgroup_xyz = [%0, %1, %2]
  hal.command_buffer.dispatch.symbol %arg0, @ex::@backend::@entry0, workgroup_xyz = [%0, %1, %2]
  hal.command_buffer.dispatch.symbol %arg0, @ex::@backend::@entry0, workgroup_xyz = [%0, %1, %2]
  hal.command_buffer.dispatch.symbol %arg0, @ex::@backend::@entry0, workgroup_xyz = [%0, %1, %2]
  hal.command_buffer.dispatch.symbol %arg0, @ex::@backend::@entry0, workgroup_xyz = [%0, %1, %2]
  hal.command_buffer.dispatch.symbol %arg0, @ex::@backend::@entry0, workgroup_xyz = [%0, %1, %2]
  ...
}

To keep it simple to start we can just pick a value (128, 256, etc) and use that on both the compiler pass and the runtime KeepRunningBatch call, but ideally what we'd do here is add an attribute to the exported function that we queried at runtime with iree_vm_function_reflection_attr, allowing iree-benchmark-module to remain batch 1 by default (so same as today).

I think I get the point to do batch mode benchmark. It's like we unroll (or put it in a for loop) like this:
func @my_exported_dispatch_benchmark_fn() attributes {iree.module.export, iree.reflection = {bt = 128}}} {
  ...
  hal.command_buffer.dispatch.symbol %arg0, @ex::@backend::@entry0, workgroup_xyz = [%0, %1, %2]
  ...
}

(using 128 times as example)
In runtime we can extract the number of batch with iree_vm_function_reflection_attr, and benchmark with batch mode. My question would be -- how do we handle 129 times or the rest of times?
// extract batch_size with iree_vm_function_reflection_attr
while (state.KeepRunningBatch(batch_size)) {
  // invoke the exported function with batch mode?
}
// any batch_size=1 function to call?

I got some options here, but would like to know if you have something in your mind.

Ignore the rest of iterations, only invoke the function when there are more than batch_size runs.
Pass a runtime argument to the module (as function argument?), so we can run both mode.

Yep!
If I understand correctly you only run with batch_size - no need to handle leftovers. The benchmark tool will process everything in steps of that batch size.
The big end-to-end functions won't have the batch size attribute - or a default of 1 - and when that happens the state.KeepRunningBatch(batch_size) == state.KeepRunning(), so they'll work just like they do today. It's only the generated per-dispatch functions that would be running with batch_size>1.

cool, I just want to clarify if we need to handle leftovers. Looks like the benchmark tool will handle it, and it's great. I think it shouldn't be hard to add, I'll put it on my plate. :)


Additive lighting

About the PR
This PR started off as a simple thought: "how easy would it be to do additive lighting without touching the engine?"
As it turns out: it's incredibly straight-forward! We wrote the initial code months ago for Illucid Fieldtrip (a fork we've been chipping away at on our own), and even shared a heavily stripped-down variant of IF's postprocess shader (containing exclusively the additive lighting effect) back in May for code example purposes (https://discord.com/channels/310555209753690112/770682801607278632/1241912021700837487). This PR is a cleaning-up of our example code.
Additive lighting is a post-process pass wherein excess light is processed and added on top of the existing image.
In laymen's terms, that means this:

Now looks like this:

Additionally, the effect is stronger at the edges of the screen, which achieves an effect somewhat similar in spirit to what volumetric lighting achieves. Here's that same bonfire, except it's near the far edge of the screen:

This effect can be toggled on and off via the settings menu, through the new "Cosmetic Post-processing" option in the graphics tab, under the quality section.
Why / Balance
We're gonna be real: this is a change that does not have any strong reasoning behind it beyond that it simply looks nice. Whenever we've shared screenshots of our experimentations with post-processing (such as ones we've shared during extremely early development of Illucid Fieldtrip), the reception tends to be fairly positive across the board. Additive lighting is one such effect in particular that we've noticed consistently garner positive responses, and is one that we feel genuinely fits pretty nicely within baseline SS14.
However, with additive lighting comes a drawback: quite a few lights with outright absurd values (such as the xenoarchaeology effect that gives an artifact a light strength of 10) simply need to be nerfed. Without this light value audit pass, this PR would otherwise result in sights like this:

(That last one is just a standard flare!)
Technical details
The primary thing that makes this PR tick is the addition of a new overlay that client's entrypoint.cs will automatically add on startup: BasePostProcessOverlay. This single overlay and its associated shader (base_postprocess.swsl) is intended to serve as the foundation for future omnipresent post-processing effects (for example: if someone were to want to add tonemapping, this would just be added on top of the existing base post processing shader). The reason this isn't instead designated as its own isolated shader is to encourage devs to try to keep future global post-processing effects within that file for the sake of keeping needless overhead to a minimum (as many effects can be achieved fairly efficiently with just one single shader pass).
The additive lighting shader itself is fairly self-explanatory for anyone familiar with shader code. It sets up a circle gradient to use as a falloff, multiplies a grayscale of the lighting sample to get the target luminosity for the additive light on a given pixel, multiplies the light sample by that target luminosity, then adds the result directly to the underlying image. Additionally, every major value within the shader can be modified at runtime, as they're all exposed as uniforms.
Media
Here is set of a before/afters of a few maps. Do note that this effect is extremely subtle under normal conditions! The following are all under spoilers, and the maps have been cherrypicked specifically for being ones where the effect is noticeable out of the box.

Oasis
BEFORE:

AFTER:

Core
BEFORE:

AFTER:

Fland
BEFORE:

AFTER:

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes
N/A
Changelog
:cl: Bhijn and Myr

add: Added additive lighting. In laymen's terms, this means excessively bright lights in a given spot will end up creating an overbright bloom effect, instead of just oversaturating the image! This effect can be toggled in the options menu through the "Cosmetic Post-processing" checkbox under the graphics tab.
tweak: Due to the introduction of additive lighting, many lights that previously had excessively high energy values have had those values toned down.  You do not want to know how bad some of the previous values were when additive lighting was added in, trust us.

This is so insanely cool..

this is cool, but i think it might not be a good idea since from the screenshots it just kinda looks like its blurry all the time

oh god, fog machines

Breaks all light if the map has a MapLight component, such as a terminal or expedition.

Breaks all light if the map has a MapLight component, such as a terminal or expedition

It is broken, but I love the "sunny" vibe


docker logs "unable to locate plugin : calico"

I installed calico with docker on centos7.2.1511, and it failed when I finally created the network. I tried both 3.22.1 and 3.10.4. The log always prompts "unable to locate plugin : calico"
docker version: 1.13.1
calico: 3.22.1 and 3.10.4
command: docker network create --driver calico --ipam-driver calico-ipam net1
How do I need to configure my docker or calico to successfully create the network?

Calico doesn't include a docker plugin directly any more - we use a CNI plugin to integrate with Kubernetes and other runtimes that use CNI (of which Docker is not one).
Did you follow some specific set of docs to try this?

Yes,i trid from some articles.
And i should install CNI plugin first, right? do you have some artical links for me?
Thanks Bro!

Supported install documentation can be found here: https://projectcalico.docs.tigera.io/getting-started/kubernetes/


called Result::unwrap() on an Err value: ParseFailed at parser/src/grammar/module.rs:58:34

Compiling this file:
))

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ParseFailed', parser/src/grammar/module.rs:58:34
stack backtrace:
   0:     0x5564ae338060 - std::backtrace_rs::backtrace::libunwind::trace::h9d49145f95eb5894
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/std/src/../../backtrace/src/backtrace/libunwind.rs:90:5
   1:     0x5564ae338060 - std::backtrace_rs::backtrace::trace_unsynchronized::hab1d020365bb6864
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2:     0x5564ae338060 - std::sys_common::backtrace::_print_fmt::h7659588431e304bd
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/std/src/sys_common/backtrace.rs:67:5
   3:     0x5564ae338060 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h09f4a9e3befae3c7
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/std/src/sys_common/backtrace.rs:46:22
   4:     0x5564ae35300c - core::fmt::write::hf3fdfde304b9a088
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/core/src/fmt/mod.rs:1092:17
   5:     0x5564ae334fc2 - std::io::Write::write_fmt::h1cb850689c7116f0
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/std/src/io/mod.rs:1568:15
   6:     0x5564ae33a225 - std::sys_common::backtrace::_print::hdbccd5aa093ba544
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/std/src/sys_common/backtrace.rs:49:5
   7:     0x5564ae33a225 - std::sys_common::backtrace::print::hc639c4f320222558
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/std/src/sys_common/backtrace.rs:36:9
   8:     0x5564ae33a225 - std::panicking::default_hook::{{closure}}::hdb012dd7a485bb5d
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/std/src/panicking.rs:208:50
   9:     0x5564ae339cd3 - std::panicking::default_hook::h75facbce77b6ba91
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/std/src/panicking.rs:225:9
  10:     0x5564ad71d76f - fe_compiler::errors::DEFAULT_PANIC_HOOK::{{closure}}::{{closure}}::h224bb075fdc4cbe1

You've hit an internal compiler error. This is a bug in the Fe compiler.
Fe is still under heavy development, and isn't yet ready for production use.

If you would, please report this bug at the following URL:
  https://github.com/ethereum/fe/issues/new
Aborted

for fuzzing.  Using https://github.com/agroce/afl-compiler-fuzzer

(imagine over the next week I'll see a few more, since the fuzzer is now getting to know the new parser; started it up a couple of hours ago, and these latest three are what I've hit so far)


Grants content

Perform the following tasks for the Grants (a combination of Local equity grants and Resources for law enforcement) page:

[x] Review for content design principles
[x] Get final accuracy approval from Christina/Alex
[x] Airtable fields confirmed
Title
Slug
Menu
Page description (short text that appears in bookmarks and social media page shares)
Body content

Content loaded into Airtable with required info.


Make install fails to include base.h file

Describe the bug
Make install command in cups fails to install base.h file in the include directory due to which libcupsfilters fails to make.
Screenshots

Make commands in libcupsfilters gives the following error :

[master 200124285] Fix 'make install' for base.h (Issue #809)

Note: CUPS 2.5 isn't even ready for beta testing and shouldn't be used for production builds...


LLava Integration

Is your feature request related to a problem? Please describe.
Implement image-to-text Llava model to describe images.
Describe the solution you'd like
The model can be found on Ollama and here there is an article showing how to correctly upload an image.
Right now the only multi-modal llm we have is GPT4-Vision which can be found on the models/openai_itt.py class
Describe alternatives you've considered
Suggest also other models

@DiTo97 thanks for the suggestions!


VS2019 internal compiler error

Severity	Code	Description	Project	File	Line	Suppression State
Error	C1001	 An internal error has occurred in the compiler.
(compiler file 'd:\agent_work\4\s\src\vctools\Compiler\CxxFE\sl\p1\c\convert.cpp', line 674)
To work around this problem, try simplifying or changing the program near the locations listed above.
Please choose the Technical Support command on the Visual C++
Help menu, or open the Technical Support help file for more information	G2Lua	D:\Lua Projects\Gothic2\G2Lua\packages\sol.hpp	23388
getting this error when trying to compile my project with sol included and c++ language standard set to c++17.

how to fix this ? thanks in advance

I think you'll probably need to provide a specific repro, right now there's little actionable here? Ideally you report this to MSVC, as they never want the compiler to ICE:
https://docs.microsoft.com/en-us/cpp/overview/how-to-report-a-problem-with-the-visual-cpp-toolset?view=vs-2019
The same information (compiler version, repro file) can also be used to potentially find a work around for you.

`#pragma once
#include <Windows.h>
#include
extern "C" {
#include "lauxlib.h"
#include "lua.h"
#include "luaconf.h"
#include "lualib.h"
}
#ifdef _WIN32
#pragma comment (lib, "lua51.lib")
#endif // _WIN32
#ifndef LUA_OK
#define LUA_OK 0
#endif
#include <sol/sol.hpp>
#include
bool CheckLua(lua_State* Lua, int result) {
if (result != LUA_OK)
{
//lua_Debug ar;
//lua_getstack(L, 1, &ar);
//lua_getinfo(L, "nSl", &ar);
//int line = ar.currentline;
std::string error = lua_tostring(Lua, -1);
std::cout << "[LUA]ERROR: " << error << std::endl;
return false;
}
return true;
}
void TestFunction(std::string name) {
std::cout << "[C++]HostFunction called" << std::endl;
std::cout << "Hello "<< name << std::endl;
}
int main() {
sol::state Lua;
Lua.open_libraries(sol::lib::base, sol::lib::package, sol::lib::string);
Lua["Hostfunction"] = &TestFunction;
while (true)
{
if (CheckLua(Lua, Lua.do_file("scripts\Gothic2.lua")))
{
//all went well
}
}
return 0;
}`
i just tried it with this simple test , i dont know if included everything right at all (im new to lua, but i worked with standalone lua)

This is because you are using /permissive-, the compiler flag that is broken but on-by-default for MSVC.
Turn it off: https://github.com/ThePhD/sol2/issues/821


Added fixes to bugs found earlier - were missed

The following were missed fixes - minor.  Fixed them

Delete the Cognitive Computing row.
Revise  CloudWatch for Visual Studio Application Insights.
Please remove "(can also be purchased with Office 365)".

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/aws-professional/services.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


vscode-swift extension does not recognize bridging header

I know vscode-swift is not supposed to do iOS development, but I am just one step away.
I use vscode and vscode-swift extension to do iOS development according to this guide, https://medium.com/swlh/ios-development-on-vscode-27be37293fe1.
All goes very well, until I have to use a swift bridging header file.
These are my code project structure
sourcekit-lsp setting:

bridging header file:

the imported C header file:

swift extension does not recognize the extractnews() function from the C header file:

But you can see every other thing is recognized, like UIKit, WebKit

I don't think Swift Package Mansger recognises bridging headers is the issue here. Without SwiftPM I don't get Sourcekit-LSP support and I can't then provide this in the extension.

We can figure out what Xcode does when it creates and uses Bridging Header files, if there is a way to output the compiling and linking command in Xcode. We can build Makefiles based on that then. Objective-C Bridging Header is great, it works on macOS and iOS. Both C and C++ features are available there.

Is it bridging headers you want or is it to include Objective-C? Because if it is the latter then you could use the following https://github.com/apple/swift-package-manager/blob/main/Documentation/Usage.md#creating-c-language-targets

Closing as this hasn't had a response for 2 months


Exported variables

Implement the Export attribute including a PropertyUsage enum (Actually, the PROPERTY_USAGE_* constants will be exposed; preferable as enum constants) and a PropertyHint (PROPERTY_HINT_* constants will be exposed too) interface with its implementations classes.
There is range for improvement here in comparison with GDScript's keyword. C# is a statically typed language so the type does not need to be inferred or manually specified. C# supports enums, so the enum hint is unnecessary.

Has this been implemented?

Yes, but there are still improvements we can make compared to GDScript. e.g.: Filling hint_string automatically for enums.

Great! Are there any examples about how to export variables as in GDScript?

The most basic one would be:
[Export]
float speed = 200f;

Nice to know this is working... I think it also needs to be public, so
[Export]
public float speed = 200f;

BTW, is that ok? Should we also allow it for non-public fields as well?
Another TODO is to make it work for properties as well.

Thanks for asking. Since we're explicitly placing an attribute, I think it would be good to do it for private fields too. You may want to change these fields per node in the editor, but still keep the code clean by keeping them private from other classes.

Yeah it should be public and I don't know if it makes sense to expose also private ones. Normally private variables are manipulated in C# either through methods or through a public propriety with getter/setter logic.

Yes, I think the good practice is to allow it only for public members. The problem is C# attributes cannot be made to target only public fields, so it would be a runtime error printed by the editor or silently ignoring it like it's done right now.

As an example, in Unity they automatically export all public variables, but you can place an attribute in order to expose a private field to the editor. Just so I don't misrepresent myself, I like having to add an attribute on all exported variables, as this keeps the inspector clean :)
Several Unity developers/plugins do expose private variables to the inspector. I think the most common reason for this is that there are sometimes values you want the user to be able to change as initial values, but they shouldn't be changed at runtime. So they're exposed to the inspector, but not via the API.
If a person feels they should only have exported variables be public, they can always simply choose not to put the export attribute on any of their private variables. In other words, allowing for both public and private variables to be exported allows everybody to work according to their own style.

@neikeq New script variables appear in the property editor only after restarting the editor. I tried saving the script file, closing and reopening the scene but it hasn't worked so far.


openshift: implement existing vnet e2e test

@jim-minter, closing as this https://github.com/Azure/acs-engine/pull/3274 PR merged.


Add support for Adafruit temperature/humidity sensors

Adds a new sensor component reading temperature and humidity, for example from a DHT22 attached to a Raspberry GPIO pin.
Needs testing, documentation and some minor fixes, see TODO and FIXME.
Edit: The Travis check fails because the Adafruit library is not compiled on a Raspberry Pi or a Beaglebone. What can I do about it?
Edit2: Fixed. Now the user needs to install the problematic library.

It looks good. Merging it, thanks!


Merge overloaded method definitions from typeshed

Summary of changes
Works towards #2345

Bring over all setuptools method that are @overloaded from typeshed

Pull Request Checklist

[x] Changes have tests (existing static and unit tests should pass)
[x] News fragment added in newsfragments/. (no user facing changes)
(See documentation for details)

Thank you!


Add test comparing Erlang distribution and an appropriate fpdistribution

Probably compare mean and variance, as well as pdf() evaluated at same points.

Done.


vscode indicates problems in launch.json

Both underlined strings have same problem

The closest issue I found is Confusing "Property is not allowed" error, when property is allowed, just slightly misconfigured

Ok, this is irrelevant to this tutorial, I removed the file


mlflow model cannot be deployed

/kind bug
What steps did you take and what happened:
I tried to deploy a MLflow model using KServe.
However, the inferenceService Pod was in an error state. I checked the logs using kubectl logs <pod_name> and found a pydantic.errors.PydanticImportError .
$ kubectl -n <namespace> logs pytorch-tar-predictor-00001-deployment-5549cc798b-xfcb6
(omitted)
bin/activate
bin/deactivate
bin/conda-unpack
--> Sourcing new environment at ./envs/environment...
--> Calling conda-unpack...
usage: conda-unpack [-h] [--version]
conda-unpack: error: unrecognized arguments: --quiet
--> Disabling user-installed packages...
/opt/mlserver/envs/environment/lib/python3.8/site-packages/pydantic/_migration.py:283: UserWarning: `pydantic.error_wrappers:ValidationError` has been moved to `pydantic:ValidationError`.
warnings.warn(f'`{import_path}` has been moved to `{new_location}`.')
/opt/mlserver/envs/environment/lib/python3.8/site-packages/pydantic/_migration.py:283: UserWarning: `pydantic:PyObject` has been moved to `pydantic.types:ImportString`.
warnings.warn(f'`{import_path}` has been moved to `{new_location}`.')
Traceback (most recent call last):
File "/opt/mlserver/envs/environment/bin/mlserver", line 5, in <module>
from mlserver.cli import main
File "/opt/mlserver/envs/environment/lib/python3.8/site-packages/mlserver/__init__.py", line 2, in <module>
from .server import MLServer
File "/opt/mlserver/envs/environment/lib/python3.8/site-packages/mlserver/server.py", line 7, in <module>
from mlserver.repository.factory import ModelRepositoryFactory
File "/opt/mlserver/envs/environment/lib/python3.8/site-packages/mlserver/repository/__init__.py", line 1, in <module>
from .repository import (
File "/opt/mlserver/envs/environment/lib/python3.8/site-packages/mlserver/repository/repository.py", line 8, in <module>
from ..settings import ModelParameters, ModelSettings
File "/opt/mlserver/envs/environment/lib/python3.8/site-packages/mlserver/settings.py", line 8, in <module>
from pydantic import PyObject, Extra, Field, BaseSettings as _BaseSettings
File "/opt/mlserver/envs/environment/lib/python3.8/site-packages/pydantic/__init__.py", line 386, in __getattr__
return _getattr_migration(attr_name)
File "/opt/mlserver/envs/environment/lib/python3.8/site-packages/pydantic/_migration.py", line 296, in wrapper
raise PydanticImportError(
pydantic.errors.PydanticImportError: `BaseSettings` has been moved to the `pydantic-settings` package. See https://docs.pydantic.dev/2.7/migration/#basesettings-has-moved-to-pydantic-settings for more details.
For further information visit https://errors.pydantic.dev/2.7/u/import-error

This appears to be because MLServer did not support Pydantic V2 until version 1.5.0. MLServer v1.6.0 supports Pydantic V2, so I hope patching the MLServer image tag to 1.6.0.
I was able to deploy the model after downgrading the pydantic version
References:

https://github.com/SeldonIO/MLServer/releases/tag/1.6.0
https://hub.docker.com/layers/seldonio/mlserver/1.6.0/images/sha256-00d793258d1ae582bfb0c236650e4d3afe3ae866be4b95532ec52c9497ac2f52?context=explore

What did you expect to happen:
The inference service was deployed.
What's the InferenceService yaml:
apiVersion: "serving.kserve.io/v1beta1"
kind: "InferenceService"
metadata:
  name: "pytorch-tar"
spec:
  predictor:
    serviceAccountName: mlf-ksrv
    model:
      modelFormat:
        name: mlflow
      protocolVersion: v2
      storageUri: "s3://mlf-bucket/3/51632a54df1c400180bc68d502c18944/artifacts/pytorch-model/"

Anything else you would like to add:
I'm considering modifying the MLServer tag (1.15.0 -> 1.16.0) in the following files referencing this request #3740.
files

charts/kserve-resources/README.md
charts/kserve-resources/values.yaml
config/runtimes/kustomization.yaml

If you're okay with it, I'd like to fix this and commit the changes.
Could you please let me know if any of the following files should also be modified?

kserve/install/vNN.NN.NN/kserve-cluster-resources.yaml
ex) kserve-cluster-resources.yaml#L80

Environment:

Istio Version: v1.21.0
Knative Version: v1.13.1
KServe Version: v0.12.0
Kubeflow version:
Cloud Environment: k8s_istio
Minikube/Kind version:
Kubernetes version: v1.29.3
OS: ubuntu22.04

I confirmed that the issue was resolved by modifying the following three files and building KServe locally:

charts/kserve-resources/README.md
charts/kserve-resources/values.yaml
config/runtimes/kustomization.yaml

The changes (git diff) are as follows:
diff --git a/charts/kserve-resources/README.md b/charts/kserve-resources/README.md
index 167d75f6..ebe302c2 100644
--- a/charts/kserve-resources/README.md
+++ b/charts/kserve-resources/README.md
@@ -72,7 +72,7 @@ $ helm install kserve oci://ghcr.io/kserve/charts/kserve --version v0.13.0
 | kserve.servingruntime.lgbserver.tag | string | `"v0.13.0"` |  |
 | kserve.servingruntime.mlserver.image | string | `"docker.io/seldonio/mlserver"` |  |
 | kserve.servingruntime.mlserver.modelClassPlaceholder | string | `"{{.Labels.modelClass}}"` |  |
-| kserve.servingruntime.mlserver.tag | string | `"1.5.0"` |  |
+| kserve.servingruntime.mlserver.tag | string | `"1.6.0"` |  |
 | kserve.servingruntime.modelNamePlaceholder | string | `"{{.Name}}"` |  |
 | kserve.servingruntime.paddleserver.image | string | `"kserve/paddleserver"` |  |
 | kserve.servingruntime.paddleserver.tag | string | `"v0.13.0"` |  |
diff --git a/charts/kserve-resources/values.yaml b/charts/kserve-resources/values.yaml
index 82fbb719..42f51828 100644
--- a/charts/kserve-resources/values.yaml
+++ b/charts/kserve-resources/values.yaml
@@ -95,7 +95,7 @@ kserve:
       tag: 2.6.2
     mlserver:
       image: docker.io/seldonio/mlserver
-      tag: 1.5.0
+      tag: 1.6.0
       modelClassPlaceholder: "{{.Labels.modelClass}}"
     sklearnserver:
       image: kserve/sklearnserver
diff --git a/config/runtimes/kustomization.yaml b/config/runtimes/kustomization.yaml
index 92dedae5..2eab8ed1 100644
--- a/config/runtimes/kustomization.yaml
+++ b/config/runtimes/kustomization.yaml
@@ -25,7 +25,7 @@ images:

 - name: mlserver
   newName: docker.io/seldonio/mlserver
-  newTag: 1.5.0
+  newTag: 1.6.0

 - name: kserve-xgbserver
   newName: kserve/xgbserver

Would you like me to create a pull request with these changes?
Resolving this would be helpful as it would allow us to use pydantic v2.x for model development.


How do I increase the center lod?

This is not a bug, more a question:
I am optimizing for lo-end devices with these settings:
Ocean Detail Params:
min - max scale: 32 - 128
lod data res: 64
down sample factor: 1
lod count: 2
which brings only a small square of details, where foam is created. But borders are clearly visible and it´s not where the camera is pointing sometimes. Is there a way to increase that center square?

I found increasing the lod count seems to solve it. have to check how the cpu impact is. is this the way to go?

The general issue is that there are a lot of waves that are rendering into lod 0 with your settings. You could increase amplitude of bigger wavelengths, or reduce smaller wavelengths to balance it out.
Increasing lod data resolution would expand the range of those waves so it isn't such a small square, but you are looking at low end perf so may not be an option.

great - will look into that. anyhow I found out, that a higher LOD is not so much a performance killer. it´s more the size of the textures. I also found out, that dynamic waves depend somehow on the resolution of the LODs - half resolution would mean I have to multiply the size of waterinteraction objects by 2.


Added timsTOF support

This PR adds support for timsTOF data, which uses index= in its scan headers.

I wonder if just to be safe we should add a if not hasattr(self, "_index_template") -> could not determine the index names for the file or something like that ...

Done!

Thanks!
accepted and merged

Since the spec header is         <spectrum index="0" defaultArrayLength="24521" id="index=1">
I think we need to change the regex from
self._index_template = ".*(scan|index)={SCAN_NUM}(\\s|$)"

to
self._index_template = "(.*scan|index)={SCAN_NUM}(\\s|$)"

because i got with the current version
RuntimeError: Cound not determine scan names for the file.

I don't understand why the former wouldn't work, but the latter one would...

I take it back (still sebastian, just different computer ...) the issue was smaller than i thought ... since the id was "index=1", it didnt have match to the word 'scan', which led to the runtime error ... so we need to add it ...
@wfondrie
@jspaezp


Fix terminology in L02rw.lean

This pull request includes a small change to the Game/Levels/Tutorial/L02rw.lean file. The change clarifies the language by replacing "proof" with "assumption" in the context of rewriting with the rw tactic.

After reading this another time, perhaps the best would just be to say "We do this in Lean by rewriting the proof, using the rw tactic.", since we are not rewriting h in this case, but the proof.

@kbuzzard @joneugster thanks for both of your reviews. I see that we haven't come to a consensus yet. However, due to the way GitHub creates a separate thread for each review, I suggest that we discuss the wording in this main thread to make the discussion easier to follow.
From my understanding (and correct me if this is inaccurate), in Lean we start by stating a goal as a statement and transform this goal into a new statement each time we use a tactic. This then becomes our new current goal. We stop when we reach the statement "true" which indicates that we've accomplished our goal. The whole process, including all the intermediary goals, constitutes the proof.
Hence, when we use the rewrite tactic with the assumption h (ie. rw[h]), we are rewriting the current goal by "substituting in" all instances of the left-hand side of the assumption with the right-hand side. Based on that interpretation, the phrasing could be:
- We do this in Lean by *rewriting* the proof `h`, [...]
+ We do this in Lean by *rewriting* the goal with `h`, [...]

This wording makes it clear to me that we are rewriting the goal and not the entire proof nor h (since h is an assumption that which remains unchanged).
Let me know if this works and I'll make the change. I see that there is also some files in the .i18n that I haven't edited. I can also fix that.

I think the issue here is whether "rewriting" is something which you do to a hypothesis or to the goal. In my mind, you rewrite a hypothesis, and this changes the goal.

Based on the docs, it seems that the intended interpretation is that the goal is rewritten:

In the following example, we use this basic form to rewrite the goal using a hypothesis.


Fix Canada fr localization

Proposed change

Fix Memorial Day translation typo.
Type of change

[ ] New country holidays support (thank you!)
[x] Supported country holidays update (calendar discrepancy fix, localization)
[ ] Existing code/test/process improvement (best practice, cleanup, refactoring, optimization)
[ ] Dependency upgrade (version update)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (a code change causing existing functionality to break)
[ ] New feature (new python-holidays functionality in general)

Checklist

[x] I've followed the contributing guidelines
[x] This PR is filed against beta branch of the repository
[x] This PR doesn't contain any merge conflicts and has clean commit history
[x] The code style looks good (make pre-commit)
[x] I've added tests to verify that the new code works and all tests pass locally (make test, make tox)
[ ] The related documentation has been added/updated (check off the box for free if no updates is required)

Coverage: 100.0%. Remained the same when pulling 782571749cca81da100370f860f29289eff943cf on KJhellico:fix-canada-loc into d34e0b3eee6720ca1be64066bec7159c5624e482 on dr-prodigy:beta.


No UI on Fedora

Running nitroshare produces only one line in console:
$ nitroshare
QSystemTrayIcon::setVisible: No Icon set

When files are sent, they seem to be received (because other device shows it), but no UI is accessible on receiving Fedora, no command line params to invoke settings of check them, or select computer name and target directory.

I noticed that to, on fc27 the rpm versions seems outdated, I compiled nitroshare from source and it worked, it still wasn't perfect, but I am able to send file from my host pc.

It's v0.3.4, so it is up-to-date. I guess the only issue you may be see is https://github.com/nitroshare/nitroshare-desktop/issues/204, which is a missing tray icon, but you could install TopIcons plus as a workaround for now, e.g.


.fmc cover guessing game

Guess whose .fmc it is.

Choose a random month long period since day of first scrobble.


add new hook for when sw is activated

I'm currently using the pwa plugin in 'InjectManifest' mode since that's the only way I could find to add an event listener for messages on the service worker.
So far, this has been useful when we want to skip waiting on user input.  For example, I prompt a user when there's an updated service worker.  Something like this:

New version available   'Refresh' or  'Dismiss'

However, I'm trying to figure out how to reload the page after the user clicks refresh.
I can't do the following because the service worker has no context of the window object. its out of scope
self.addEventListener('message', (e) => {
  if (e.data.action === 'skipWaiting') {
    self.skipWaiting()
    window.location.reload()
  }
})

My thought was to add a new hook or to re-use the 'ready' hook in register-service-worker which would be triggered whenever the installing worker state === 'activated'
For example:
if (installingWorker.state === 'installed') {
  if (navigator.serviceWorker.controller) {
    // At this point, the old content will have been purged and
    // the fresh content will have been added to the cache.
    // It's the perfect time to display a "New content is
    // available; please refresh." message in your web app.
    emit('updated', registration)
  } else {
    // At this point, everything has been precached.
    // It's the perfect time to display a
    // "Content is cached for offline use." message.
    emit('cached', registration)
  }
} else if (installingWorker.state === 'activated') {
  emit('activated', registration)
}

This would allow the ability to reload the page safely from the registerServiceWorker.js file after a user has clicked 'Refresh'
Am I overthinking this?  Perhaps there's a better way to handle this?

In this project I separate self.skipWaiting from window.location.reload.  So in service-worker.js I have a message listener:
self.addEventListener('message', (e) => {
  if (!e.data) return;
  if (e.data === 'skipWaiting') self.skipWaiting();
});

and in registerServiceWorker.js, in the updatefound section, I have:
  let refreshing;
  navigator.serviceWorker.addEventListener('controllerchange', () => {
    if (refreshing) return;
    window.location.reload();
    refreshing = true;
  });

and in the updated section:
const UpdatedEvent = new CustomEvent('swUpdated', { detail: registration });
document.dispatchEvent(UpdatedEvent);

So, when a new SW is detected, I create a new event with the SW rego as payload and send it to the document.  In my app, I am listening for this event in a Main component, and when it comes, a function runs to change an alert boolean to true and set the rego prop on the Main component's data to the SW rego payload.  The boolean is used to render an Alert component and the rego is sent as a prop.  The Alert component thus appears on-screen and when you close it, a function runs that calls waiting.postMessage on the rego object, with the message of skipWaiting.  The SW is listening for that to call self.skipWaiting.  When self.skipWaiting is called, the new SW activates.  This triggers the controllerchange event that we are listening for in registerServiceWorker, and that is where we call reload.

@jamessouth This is a better solution.  I didn't think about putting the event listener for controllerchange directly in the registerServiceWorker.js.  I added it to mine, and it negates the need for another hook.
Great suggestion!

😊😁👍


tests: Add test of Mbed TLS on various architectures with QEMU

Add test of Mbed TLS on various architectures with QEMU.
Together with https://github.com/ARMmbed/mbedtls-test/pull/187, fixes #3855.
Successfully tested against the docker image tagged pr-187-ubuntu-18.04 (digest: sha256:ce166a2f7bde60f8cbc461bfcfd35803481c1d9a5468178fa017090e1b149405) generated by the Jenkins dockerfile-builder job #48 from https://github.com/ARMmbed/mbedtls-test/pull/187/commits/6a7152209f6d8cd80095b3873ca06d15443ca4e8 in which qemu-user and the necessary cross-compilers are installed.
Status
READY but CI cannot pass until the Ubuntu 18.04 docker image used by the CI is updated along the lines of https://github.com/ARMmbed/mbedtls-test/pull/187.
Requires Backporting
No

I think this should be backported. We aren't starting to test architectures that we're only now starting to support. We're starting to test architectures that we always supported, at least in the sense of caring about bugs.

I think this should be backported. We aren't starting to test architectures that we're only now starting to support. We're starting to test architectures that we always supported, at least in the sense of caring about bugs.

Agreed, that would be ideal but given the workload I don't think it is justified. I think it's still a step forward to only do this for development.

The workload for backporting this is very small. Most of the work is in setting up the CI, and this is independent of specific branches.

To be continued in Q4.

We are now converting older PRs to draft PRs where the following conditions are met: They have not been updated in the last 3 months, and they need more than non-trivial work to complete.


brew upgrade func command did not updated func v0.18.0 to the latest 0.19.0

I have func plugin version 0.18.0 installed.
Using brew upgrade func command output
Warning: knative-sandbox/kn-plugins/func v0.18.0 already installed
Latest release under Release is 0.19.0 built on Nov 3.

This has been fixed.


address outstanding TODOs (one is outstanding)

Closes #74

Removes TODOs which (I think) have already been resolved
Handles a TODO about letting the owner of an account rotate the auth account capability
Leaves one TODO (happy to address in this PR) about how to handle publishing to a parent a second time.

Link to offline discussions:
https://discord.com/channels/613813861610684416/1087374662100602920/1120753477338009660

@sisyphusSmiling re-requested just to be safe 🙂


Catch the install to cargo/bin on Windows

The path lookup doesn't respect PATHEXT so nu doesn't find nu.exe

looks good to me. thanks!


fix: an issue with modified files due to lfs

This is an attempt to fix #1186 .
I haven't quite figured out the exact issue but it appears that when looking for commits with get_package_diff the repository is left in a modified state due to some weird interaction with lfs files being moved from- or into git lfs that previously weren't or shouldn't. Im not entirely sure.
Anyway, the "fix" that I implemented is to "force" the checkout of a certain commit by adding '-f' to the arguments of git checkout. This fixes the issue that occurs in #1186 but I cant fully comprehend if this has some negative consequences for other parts the execution. Feedback is very welcome.

I wanted to try fix this today, but I didn't get to it :/
If you want to try to fix it, let me know how can I help.
I'm afraid that git checkout -f could bring to user data loss somehow, so I prefer to find a more careful approach

I would indeed love some help because Im kinda unsure on where to go from here.
Since the problem with git checkout only seems to happens in the checkout_head function I could also add a force_checkout method that is only called there. I assume that since this function is only called after trying to figure out the diffs on a fresh clone of the repository there is very little risk of data loss. Let me know what you think.

Hey sorry if I didn't provide the right guidance on this.
Anyway I think we need a better way to dealing with lfs which is not force checkout.
Not sure how to do it yet. I haven't had the time to look into it.
By the way if I remember correctly you found a workaround. 👍
So I'm closing this PR and hopefully we'll find a good solution to deal with lfs in the future.


Remove Final Global Variable

On two of the files I thought I had changed them once before, not sure how all the vars came back, anyway they are going away now.
As far as I can tell, there should be no more globals left in the code.

:tada: This PR is included in version 0.344.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


As an admin, I want to export a custom CSV after searching in the backend so that I can use the backend’s search functionality to create targeted data sets.

dev notes

[x] Remove old DigitizedWorkCSV view and links
[x] configure and use django-import-export; use the same fields as the existing csv export

Decreasing from 2pts to 1 because django-import-export was so straightforward to set up.

Exporting all records works great (takes a few seconds to download, but lag time isn't too bad) - I tried xlsx and csv. I think it's fine to keep the name labels as is matching the code.
One thing: There's a cluster column, but instead of the alphanumeric IDs we gave them, they're all numbers. You mentioned this was because you forgot to exclude cluster, but it might be good to keep cluster on the export and show the alphanumeric IDs we input, if possible? And could we move it near collections?
Exporting a subset after searching is SO powerful! I tested with "ballad" and with "for use in schools." It successfully works via the action button and via the export button.

This looks great! Thank you for making the adjustments to the cluster column. I retested exporting the full set and a subset after search. (FYI, the speed still isn't great for the full set but it's not horrendous.)


Rebase our repo back to main oci-hpc

Would need to retest the following:

Creating/Deploying a cluster
Creating users
NFS integration
Job allocation
Figure out good distributed ML test to run

We need to create a TAG/Release of the code we have before we do a rebase.


Add bpkg.json

📚 Description
Related to: https://github.com/bpkg/bpkg.github.io/pull/82
🔖 Changes

Create a bpkg.json following https://bpkg.sh/guidelines/

Once you get this file into your project, you can start testing out your project with the BPKG utility, even before listing it on bpkg.sh.

Once you get this file into your project, you can start testing out your project with the BPKG utility, even before listing it on bpkg.sh.

Merge, pleas let us know how it goes

@khru, did you need me to perform some action?  My suggestion to test bashunit once the bpkg.json is in the project, was for someone in your team to try your project out.  From system wide install as root and non-root user to as dependency in another project (even just a test project). Document using BPKG for installing or using as dependency.


fields.nested_form[:update_only] should always be false by default.

See the "first bug" in this stack overflow answer.
It's a personal opinion, but I think that interpreting accept_nested_attributes_for: ..., update_only:true as "disable the form when creating the object" is a potential misunderstanding of the option, (for Rails 4), and should at least be documented in the wiki?

@antoine-lizee as a first step, I've created a gist to reproduce the issue here: https://gist.github.com/ericcf/f4da02ca5bb80d889131f603448ee10c
There is a difference between update_only: true and update_only: false, which seems like a bug to me as well based on the description in the Rails documentation. In my example, accepts_nested_attributes_for :dog, update_only: false leads to being able to add a Dog record upon creation of a Person, which seems to be correct.
@sferik is this interpretation correct? Would you like a failing spec for this case or is more discussion necessary? Thanks.

We're having the same issues because of the misunderstanding of this option by Rails Admin. It's unexpected that you can't create a new association for a model when update_only is set to true for accept_nested_attributes_for

BTW, if you do the following:
RailsAdmin.config do |config|
  config.model 'User' do
    base do
      configure :location do
        nested_form[:update_only] = false
      end
    end
  end
end

In order to get Rails Admin to show the child form when creating a instance, you will actually change the settings on the model as nested_form returns the same hash used to configure the model.
You should do this instead:
      configure :location do
        nested_form(nested_form.clone)
        nested_form[:update_only] = false
      end


Fix typo

Docs Build status updates of commit 98e7207:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in https://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Closing and reopening PR to trigger build.

Docs Build status updates of commit 98e7207:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in https://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Thank you for catching this error! I will correct it directly on the master branch since the build is throwing an exception. Thanks again!


MenuDisplay enum, fixes #354

Menu items are currently Option<MenuDisplay> and separators are considered as None. dyn_stack canno't hash? the Nones properly which causes missing menu items. Switching to enum and giving it something as id fixes this.

diff looks large but the change looks good to me dzhou121

diff looks large but the change looks good to me dzhou121

yep menu items are created with this huge chunk of code inside if statement, now match instead, shifting it by few line/ident or two which makes it look larger than what it actually does


Which handlebar variables can be used in converters?

Handlebars expression that are used in converters (termref converters as well as mrgref converters) are typically expected to be able to use {{<variablename>}}, where <variablename> is the name of a field in an MRG-entry. Examples are {{glossaryText}}, or {{hoverText}}, or {{termtype}}, etc.
I can see there is a merit in being able to use variables that exist in the MRG's terminology section or its scopes section.
Questions:

does this make sense?
can we do this already, and if so, how

if so: how (where is it documented)?
if not: should we specify it (turning this issue into a feature/enhancement request)?

Seems as this is a plan. So there will be variables of the form {{mrg.terminology.<fieldname>}}, where <fieldname> identifies a field in the terminology section of the current MRG. The variables of this form will produce the value of that field.

The newest versions of the tools now reflect these changes.