cant install- loads of node errors

I get a crazy list of node errors when I try and install this. I'm using:
npm 6.11.3
node v11.13.0
I've tested with just inspector, here is the package.json:
{
  "name": "app",
  "version": "0.1.0",
  "private": true,
  "dependencies": {
    "inspector": "0.5.0"
  }
}

Here is a sample of the errors, I will not copy it all:
Andrews-MBP:RealityCardsFrontEnd mcplums$ npm install

><EMAIL_ADDRESS>install /Users/mcplums/Repos/RealityCardsFrontEnd/node_modules/bufferutil
> node-gyp rebuild

  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
In file included from ../src/bufferutil.cc:16:
In file included from ../node_modules/nan/nan.h:82:
../node_modules/nan/nan_new.h:29:56: warning: 'ToInteger' is deprecated: Use maybe version [-Wdeprecated-declarations]
To<v8::Integer>(v8::Handle<v8::Integer> i) { return i->ToInteger(); }
                                                       ^
/Users/mcplums/Library/Caches/node-gyp/11.13.0/include/node/v8.h:2550:10: note: 'ToInteger' has been explicitly marked deprecated here
  inline V8_DEPRECATED("Use maybe version",
         ^
/Users/mcplums/Library/Caches/node-gyp/11.13.0/include/node/v8config.h:326:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../src/bufferutil.cc:16:
In file included from ../node_modules/nan/nan.h:82:
../node_modules/nan/nan_new.h:34:56: error: no matching member function for call to 'ToInt32'
To<v8::Int32>(v8::Handle<v8::Integer> i)   { return i->ToInt32(); }
                                                    ~~~^~~~~~~
/Users/mcplums/Library/Caches/node-gyp/11.13.0/include/node/v8.h:2531:43: note: candidate function not viable: requires single argument 'context', but no arguments were provided
  V8_WARN_UNUSED_RESULT MaybeLocal<Int32> ToInt32(Local<Context> context) const;
                                          ^
/Users/mcplums/Library/Caches/node-gyp/11.13.0/include/node/v8.h:2544:30: note: candidate function not viable: requires single argument 'isolate', but no arguments were provided
                Local<Int32> ToInt32(Isolate* isolate) const);
                             ^
In file included from ../src/bufferutil.cc:16:
In file included from ../node_modules/nan/nan.h:82:
../node_modules/nan/nan_new.h:39:65: error: too few arguments to function call, single argument 'context' was not specified
To<v8::Uint32>(v8::Handle<v8::Integer> i)  { return i->ToUint32(); }
                                                    ~~~~~~~~~~~ ^
/Users/mcplums/Library/Caches/node-gyp/11.13.0/include/node/v8.h:2529:3: note: 'ToUint32' declared here
  V8_WARN_UNUSED_RESULT MaybeLocal<Uint32> ToUint32(
  ^
/Users/mcplums/Library/Caches/node-gyp/11.13.0/include/node/v8config.h:418:31: note: expanded from macro 'V8_WARN_UNUSED_RESULT'
#define V8_WARN_UNUSED_RESULT __attribute__((warn_unused_result))
                              ^
In file included from ../src/bufferutil.cc:16:
In file included from ../node_modules/nan/nan.h:82:
In file included from ../node_modules/nan/nan_new.h:189:
../node_modules/nan/nan_implementation_12_inl.h:49:38: error: too few arguments to function call, expected 2, have 1

Wat do?

I would suggest using https://github.com/puppeteer/puppeteer instead. If I remember correctly puppeteer is partially maintained by the chromium team, so it will stay up to date.
This module is very old, and no longer actively maintained.

I had the same issue with Node 13.14.0 and npm 6.14.4. Upgrading to Node 14.16.0 didn't solve them, but upgrading npm to 7.8.0 did, and now I can npm install inspector without errors.
I know this is an old module, but I use it because I've found no better solution to return whether the process is being debugged.


Bug in Routing

After creating a new application (admin) in platform/applications/admin & public/admin, routing is not working as expected.

There is no administration page yet. I will make it, but first things first. There is a lot to be done at low level.


Introduce LambCI for testing

Introduce LambCI, the nice alternative to SaaS CI.
Also, it may reveal some advantages (and disadvantages) of this kind of tools.

I worked on this issue on the branch lambci, but decided to use Wercker instead. It was difficult to complete builds without ECS support, and I don't want to maintain ECS clusters.
I will try to introduce LambCI again when it becomes possible to run builds without ECS.


Zachmu/test refactor

Refactored the SQL engine tests to make it possible to validate schemas of result sets are as expected. This involved moving a lot of code around to avoid import cycles.

This looks huge, but it's almost 100% moved files. I deleted the files that were full of test queries and inlined those queries into the relevant test files. (This was an artifact from when we had two SQL engines that we were testing, no longer useful). I mostly want you to look at the structure of the package moves and see if they seem sensible to you.


[Rancher2] Section in 2.5 docs did not carry over to 2.6 docs

https://rancher.com/docs/rancher/v2.5/en/cluster-provisioning/rke-clusters/windows-clusters/#rancher-on-vsphere-with-esxi-6-7u2-and-above
is missing from 2.6 docs.

Original PR https://github.com/rancher/docs/pull/3385

There may be a fix for this in RKE2 v1.21.6+rke2r1+ see https://suse.slack.com/archives/C02CZP6Q7BP/p1639588238052400?thread_ts=1639520379.048000&cid=C02CZP6Q7BP


SendToAzureML procedure cannot be used for 'Extension' development

Hi!
In NAV 2018 and BC Spring release SendToAzureML method in codeunit "Azure ML Connector" had "External" visibility. But in Fall release it became Internal. And now I can use it in AL Development only with target = internal.
Is it a bug or now we need to use some other method?
Checked on sandbox and on-premise versions - both Internal.

This repository is no longer dedicated to handling application bugs, application requests and application enhancements.
I will move your issue to https://github.com/Microsoft/ALAppExtensions and please log future application requests in that repository


Drop code related to Rails < 5.0 & Ruby < 2.3.0

Another cleanup attempt (former: #2225).
In Changelog we state that we drop support for Ruby versions below 2.3, even though Rails 5.2 supports Ruby 2.2.2.

I can reproduce yard doc --no-cache failure locally:
[warn]: ...{lib}...
[warn]: In file `README.md':17: Cannot resolve link to lib from text:

It seems that JRuby's doc generation is awfully broken:

For the reference, same generated on master and MRI 2.5.5:

Still not pixel perfect (list numbering is off, code block layout) match to what's published:

Maybe it's acceptable to disable doc checks on JRuby?

@JonRowe It's a big one, but mostly removals of old Rubies/Rails 3/4 support. Appreciate if you glance over.

For Rails 4.2 did you read this comment https://github.com/rspec/rspec-rails/pull/2071#issuecomment-466551497
I am wondering how much we should clean code related to Rails 4.2
Thanks for the work.

Pretty much all of this was good to go @pirj I'd reopen it as is mostly.

At 4.0 release time, 4.2 will be removed from the build matrix, but not the gem spec

This means we can remove all of our spec / feature tests for Rails 4.2

4.2 will not be officially supported in RSpec Rails 4, and bugs against that version will not be fixed

This means that we should leave the checks for 4.2 methods to check they are supported before calling in lib, and the same for files. However anything that is old Ruby is ok to be dropped. We're hard supporting 5.0 and soft supporting 4.2 but not old Ruby, thats gone.

A warning will be issued at require time, if a user is using Rails 4.2, indicating to them that while the version is unlikely to be supported, bug fixes will not be issued against 4.2

This needs to be added somewhere.

Sorry @pirj I was maby not clear enough. But I don't this PR should be closed. :)

@pirj let me know when this is ready to review again :)

@JonRowe @benoittgt Please take another look.
I broke four examples on 4.2, mailer_generator_spec.rb and configuration_spec.rb, by removing < 5.0 checks in those specs. The code should work fine. If you comment them out
RAILS_VERSION=4.2.11 rake

expectedly get stuck at the point where @rails_post_5 tags were.

@JonRowe @benoittgt Green!

One change really, only due to our process, currently the dev build should apply cleanly to rspec-rails and I'd like to keep it that way for centrally managed files

All green. Reverted changes to predicate functions. Squashed commits.


feat: added table component

Hey @assasin0076,
Thanks for making the PR! @cogor can you please check it out?

Hi, @zoltanszogyenyi . Its not ready yet) I just started my work

LGTM


Add vByteFactorDelegation to RentStructure

https://github.com/iotaledger/tips-draft/pull/24/files/51c445ef58ae9610de2d8c38c7f68380405ff5e1..93227c50259fdc413b1beaec56c35360a14a3efb

Closed by https://github.com/iotaledger/iota-sdk/pull/1195


refactor(examples): adjust discounted-cartrade to API design

resolve #1424
Signed-off-by: Takuma TAKEUCHI<EMAIL_ADDRESS>

Codecov Report

Merging #1425 (1da7c7c) into main (8a0d182) will increase coverage by 0.01%.
The diff coverage is n/a.

:exclamation: Current head 1da7c7c differs from pull request most recent head 842f2ea. Consider uploading reports for the commit 842f2ea to get more accurate results

@@            Coverage Diff             @@
##             main    #1425      +/-   ##
==========================================
+ Coverage   70.51%   70.53%   +0.01%
==========================================
  Files         302      302
  Lines       10902    10902
  Branches     1332     1332
==========================================
+ Hits         7688     7690       +2
+ Misses       2510     2508       -2
  Partials      704      704

Impacted Files
Coverage Δ

...main/typescript/rustc-container/rustc-container.ts
68.53% <0.00%> (+2.24%)
:arrow_up:

Continue to review full report at Codecov.

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


Godot gets confused with the tilemap and his shotrcuts

Godot version
v3.5.2.stable.official [170ba337a]
System information
w10 64
Issue description
When you use the M key to copy an area of the tilemap, once you have it copied if you press the spacebar to move around the map and then release it, godot gets confused and thinks that you are still holding it down and acts something erratic.
Summary:
Godot gets confused when you have copied a rectangular area of the tilemap with the M key, you copy the area, now you press space to move across the tilemap and release space, godot goes crazy.
Steps to reproduce
With a tilemap node selected.
Press the M key to select a rectangular section.
Copy the section (CTRL + C).
Press spacebar to move through the tilemap.
Release the space bar.
Godot is confused.
Minimal reproduction project
...

There is no M shortcut in the TileMap.
And what do you mean by "confused"? The only unusual thing that I can observe is that the cursor doesn't change back after moving, but it's unrelated to TileMap.

There is no M shortcut in the TileMap. And what do you mean by "confused"? The only unusual thing that I can observe is that the cursor doesn't change back after moving, but it's unrelated to TileMap.

I mean this:

Default editor shortcuts

Ah sorry, I didn't read that it's about 3.5.


fix(cherry-pick)fix exception when querying map data through http

Proposed changes
Issue Number: close #xxx
pick from https://github.com/apache/doris/pull/29686
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


vcpkg is out of date

the vcpkg for this lib is over 14 months old

From the readme:

If you are using vcpkg on your project for external dependencies, then you can install the nlohmann-json package with vcpkg install nlohmann-json and follow the then displayed descriptions. Please see the vcpkg project for any issues regarding the packaging.

I am not the maintainer for this.

(The package at https://github.com/Microsoft/vcpkg/tree/master/ports/nlohmann-json is from last month)


feat: use azure key vault and its secrets

:tada: This PR is included in version 0.61.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


PrismaClient is unable to be run in the browser.

Bug description
Error: PrismaClient is unable to be run in the browser. //   prisma = global.prisma;
12 | // }

13 | prisma = new PrismaClient();
|         ^
14 |
15 | export default prisma;

How to reproduce

Expected behavior
No response
Prisma information

// Add your schema.prisma

// Add your code using Prisma Client

Environment & setup

OS:
Database:
Node.js version:

Prisma Version

it's not possible to run prisma in frontend/browser

@Prasiddhidahal It looks like you didn't provide most information in the description template in this issue. Without more information, we won't be able to help you. Could you fill the info in the description?

ive got the same problem, ive created a file named db.ts for using prisma globally, thats whats inside
 import { PrismaClient } from "@prisma/client";

const globalForPrisma = global as unknown as {
  prisma: PrismaClient | undefined;
};

export const prisma =
  globalForPrisma.prisma ??
  new PrismaClient({
    log: ["query"],
  });

if (process.env.NODE_ENV !== "production") globalForPrisma.prisma = prisma;

i am trying to get the data back in my browser with
 export const getServiceSideProps: GetServerSideProps = async () => {
  const notes = await prisma.note.findMany({
    select: {
      title: true,
      id: true,
      content: true,
    },
  });

  return {
    props: {
      notes,
    },
  };
};

but im receiving the same error Error: PrismaClient is unable to be run in the browser.
#Environment & setup

OS: Linux
database: sqlite
Node: v18.16.0

I am having the same issue with NextJS 13 app router.

schema.prisma
// This is your Prisma schema file,
// learn more about it in the docs: https://pris.ly/d/prisma-schema

generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider     = "mysql"
  url          = env("DATABASE_URL")
  relationMode = "prisma"
}

model User {
  id         String  @id @default(cuid())
  name       String
  email      String? @unique
  url        String?
  contact    Int?
  aboutMe    String
  image      String?
  clerk_id   String  @unique
  attributes Json?
}

client.ts (same folder as schema.prisma)
import { PrismaClient } from '@prisma/client';
const globalForPrisma = global as unknown as { prisma: PrismaClient };
export const prisma = globalForPrisma.prisma || new PrismaClient();
if (process.env.NODE_ENV !== 'production') globalForPrisma.prisma = prisma;

createUser.ts
import { prisma } from '@/prisma/client';
import { Prisma } from '@prisma/client';

export async function createUser(user: Prisma.UserCreateInput){
  try {
    await prisma.user.create({ data: user })
    console.log('try')
  } catch (error) {
    console.log(error)
  }
}

Why don't you create an API endpoint first and then use it in a client component or server component?

@rajanshresth your idea worked. Thank you.

Closing for now. If you can provide more information @Prasiddhidahal, please open a new issue. Thank you.


New chart type: Linear gauge

I’m in need of a chart type that currently isn’t available with chart.js… and while I’d love to create it and contribute it to the project, my skills aren’t up to the task. So, I’m hoping someone here would be willing to take it on for a small fee. Anyone interested please contact me directly so we can coordinate — I can’t really afford to have multiple people deliver a linear gauge all expecting payment!
My hope is that someone will be able to create a linear gauge chart type which can then be contributed back to the chart.js project… and that will meet the needs I have for a project I’m working on currently (i.e., I don’t have a long timeline for this).
The ideal linear gauge would have many of the same options as those examples settable per chart:

geometry (horizontal/vertical)
range (startValue/endValue)
axis color
axis width (should include ability to set to 0 so no axis line is displayed)
tick marks interval
tick mark labels
value indicator

at least including options for a ‘range’ indicator or a ‘point’ indicator
shapes of the ‘point’ indicator are less important, although size is probably important

value indicator offset (from center of the axis line)
value indicator color

value color ranges would be good for the range indicator type

tooltips (like current chart.js charts)

ideally tooltips would also allow some if/else statements so tooltips could change depending on value

legend
chart title
ability to place an image in the background (see example linked to below)

Having the ability to display more than one value on a single chart might also be useful (but probably isn't critical) — see http://tapintu.net/testing/trimergence/s-e-graphic.html
http://tapintu.net/testing/trimergence/s-e-graphic4.html — this one shows the two “subvalues” from the above chart separated out into their own linear gauge charts.
For all of those examples I used the devexpress trial to create a vertical linear gauge where I made all but the value indicators invisible and then placed an image behind the chart (i.e., background image on the div with the chart).
Here are some examples of the linear gauge charts of the devexpress commercial package which are along the lines of what I'm hoping for:
http://js.devexpress.com/Demos/WidgetsGallery/#demo/gaugeslineargaugeslineargaugebasicelementsscalecustomtickinterval/generic/light/default
http://js.devexpress.com/Demos/WidgetsGallery/#demo/gaugeslineargaugeslineargaugebasicelementsbasevalueforrangebar/generic/light/default
http://js.devexpress.com/Demos/WidgetsGallery/#demo/gaugeslineargaugeslineargaugebasicelementsscalecustomtickvalues/generic/light/default

I hired someone to write a linear gauge chart as a new chart type for Chart.js for a project I'm doing. I'd like to contribute the new linear gauge chart type to the Chart.js project. What's the best way to do this?
I have a github account, and could host it -- but I can't really maintain the code.
I also want to make sure the developer I used gets some credit (i.e., at least a link to his elance.com profile), although I don't expect he wants to be the maintainer either.
Thanks.

I can host it if you want. I'll make sure that it gets updated and maintained along with Chart.js. If (or as soon as) it's looking great, we'll get it put on the sanctioned chart extensions in the docs.

Great @tannerlinsley !
What's the best way to get the files to you (the .js file and an example html page) ?

Zip them up and send them to<EMAIL_ADDRESS>Be sure to include
all of the credit information as well.
On Mon, Apr 27, 2015 at 12:27 PM Scott McCulloch<EMAIL_ADDRESS>wrote:

Great @tannerlinsley https://github.com/tannerlinsley !
What's the best way to get the files to you (the .js file and an example
html page) ?
—
Reply to this email directly or view it on GitHub
https://github.com/nnnick/Chart.js/issues/1033#issuecomment-96770672.

They're on the way.

Awesome! Thanks
On Mon, Apr 27, 2015 at 12:37 PM Scott McCulloch<EMAIL_ADDRESS>wrote:

They're on the way.
—
Reply to this email directly or view it on GitHub
https://github.com/nnnick/Chart.js/issues/1033#issuecomment-96774343.

https://github.com/chartjs/Chart.LinearGauge.js

Cool - thanks!

Closing since the linear gauge is hosted in the Chartjs github organization.

https://github.com/chartjs/Chart.LinearGauge.js is not on the official chartjs repository
no mention of any gauge in https://github.com/nnnick/Chart.js/ docs
even searching for gauge that repository shows no results
same with chartjs
i'm a little confused, i was going to skip chartjs since i was not finding gauges, but at the last click i find them hidden in a different repository...
i guess something went wrong
¯_(ツ)_/¯
r*

@rufasterisco One of the devs can correct me if I'm wrong, but you won't find it in the repo since it's considered a community extension, rather than a core chart type. I believe there was some discussion on if/where to host officially-recognized extensions, but there currently isn't anything in place for V1 (that I know of, anyway).

@tiesont is correct, we consider it an extension. There is a list of community extensions at http://www.chartjs.org/docs/#advanced-usage-community-extensions but the linear gauge is not included. At some point we will transition this repo into the chartjs org and it will make it much easier to find those extensions

Thanks for clarifying :)

Does anyone know if there is a similar extension compatible with Chart.js v2? If not, then it might be worth (re-)considering including this chart type in the actual project.

I think here it is : https://github.com/scottmcculloch/Chart.LinearGauge.js

I'd love to implement this, but there is no installation guide and the example is offline. Can anyone please help?

I think here it is : https://github.com/scottmcculloch/Chart.LinearGauge.js

I'd love to implement this, but there is no installation guide and the example is offline. Can anyone please help?

@bastifix  The example is the same as the index.html page found in the repo, https://github.com/scottmcculloch/Chart.LinearGauge.js/blob/master/index.html - have you tried cloning the repository and just running it? The only thing you might have to change is the Chart.bundle.js reference, unless you have node.js installed.

@bastifix  The example is the same as the index.html page found in the repo, https://github.com/scottmcculloch/Chart.LinearGauge.js/blob/master/index.html - have you tried cloning the repository and just running it? The only thing you might have to change is the Chart.bundle.js reference, unless you have node.js installed.

@bastifix The example is the same as the index.html page found in the repo, https://github.com/scottmcculloch/Chart.LinearGauge.js/blob/master/index.html - have you tried cloning the repository and just running it? The only thing you might have to change is the Chart.bundle.js reference, unless you have node.js installed.

Thanks for the hint, I tried it again and it's working!
Now there are new problems to integrate it in my project ;-)

@bastifix The example is the same as the index.html page found in the repo, https://github.com/scottmcculloch/Chart.LinearGauge.js/blob/master/index.html - have you tried cloning the repository and just running it? The only thing you might have to change is the Chart.bundle.js reference, unless you have node.js installed.

Thanks for the hint, I tried it again and it's working!
Now there are new problems to integrate it in my project ;-)

It there any plans to move the https://github.com/scottmcculloch/Chart.LinearGauge.js and https://github.com/haiiaaa/chartjs-gauge to v3?


err_empty_response

I freshly installed the latest 2.9.15 version, configured one proxy host to do HTTP only proxying but when accessing it I get ERR_EMPTY_RESPONSE.
Tried to search the logs but there is nothing related to this issue.

Hello
I have the same issue.
I found in my log this error :

nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-10/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-10/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)

Thanks for your help

Hello again
I have mounted a new docker from scratch. Works fine. Issue on my side and my config files. Can be close for me :)

@andriesh, can you share more details about the configuration of your proxy host ?

i meat the same problem, the nginx config:
`
server_name  photo.xxx.com;
location  ^~ /  {
proxy_pass http://<IP_ADDRESS>:22342;
proxy_http_version 1.1;
proxy_pass_header Authorization;
proxy_set_header Connection "upgrade";
proxy_set_header Upgrade $http_upgrade;
proxy_set_header X-Real-IP $remote_addr;
`

I freshly installed the latest 2.9.15 version, configured one proxy host to do HTTP only proxying but when accessing it I get ERR_EMPTY_RESPONSE. Tried to search the logs but there is nothing related to this issue.

I am having the same issue on a fresh install with the latest tag, it worked for a few days but keeps going down.

Hello, no update ? same issue on tag 2.11.2 nothing changed in the config


Rock infers generic type exclusively from the first instance it can

Foo: class { init: func }
Bar: class extends Foo { init: super func }

f: func <T> (a, b: T) {
    T name println()
}

f (Bar new(), Foo new())

This should print Foo but it prints Bar, as T is infered from the first argument it appears in a.
Instead, findCommonRoot should be used here.

Ooh, that looks good

Just a question... what is the performance impact of such unification with say, an array literal of 500 elements?

Ehhh now is not the time for such questions.

(But it'd be interesting to make a stress test & optimize from there. Later.)

So, there'll probably be about a dozen duplicates of this in the future.. but at least for this case, I have a fix.
I've tried going further but then the sdk starts showing cracks everywhere so uh, better left for another time. At least we're on the path to basic sanity.

fair enough ;-)


Update "Fetch a subscriber" documentation so it shows that either "SUBSCRIBER_ID" or "EMAIL_ADDRESS" can be used as argument

The "Fetch a subscriber" API states that the argument should be a "SUBSCRIBER_ID", but "EMAIL_ADDRESS" works just as well, just like in the official documentation https://developers.mailerlite.com/docs/subscribers.html#fetch-a-subscriber.

Docs updated in v1.3.1. Thanks for contributing!


Add PHP 7.1 support and set active by default

Although the README has been updated to reflect the changes made, the shared images would still need to be created and uploaded.
I am not 100% sure if this is the most optimal way of doing it but the built image is only 9MB larger than the PHP 7.0 version.

there was already PHP 7.1 support

Hey @richdynamix, thank you!
We forgot to update the docs when we started building 7.1, sorry!
If you use quay.io/continuouspipe/php7.1-nginx:stable it should have you covered already.
Thank you for updating the docs and nice to see a familiar username :)

No problem at all. I should probably just make a note to check the docker-compose.yml first for any updates :) And I think you might hear from me more. I am working on getting the new company setup with CP. A lot of housekeeping to do first though :D


getDropTableID -> getDropTableId

This must've made it through in the AbstractBlock changes

Should this be renamed to loot table than drop table?

I do agree with you there, though really this was just the single bugfix

A bug is still a refactor
Also I suggest just calling it "loot table". drop table is really a legacy name https://github.com/FabricMC/yarn/commit/6d3075daebae22e7938460743ba82a5f6618e329#diff-0fc22c45ea8a7363223df24d31b7f7caR202 and no longer applies because we call this type of things loot tables now (before it's loot supplier)

Okay, updated. I hope this doesn't turn into another massive bikeshedding. Just wanted to get a simple bugfix in :P

Hm, maybe AbstractBlock.Settings.dropTableId should also be changed.


Issue with Wordpress and PHP 8.1

Hi there guys,
I installed the Pirsch plugin on a WP site, and it hasn't been sending hits. But checking the logs these are the errors below, it isn't the WP plugin, but seems the SDK? Or maybe its values being passed to it?
[09-Jul-2023 13:00:45 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 507
[09-Jul-2023 13:00:45 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 507
[09-Jul-2023 13:00:45 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 507
[09-Jul-2023 13:00:45 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 507
[09-Jul-2023 13:00:45 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 507
[09-Jul-2023 13:00:45 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 507
[09-Jul-2023 13:00:45 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 507
[09-Jul-2023 13:00:45 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 507
[09-Jul-2023 13:00:45 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 507
[09-Jul-2023 13:00:45 UTC] PHP Warning:  Undefined property: Pirsch\HitOptions::$cf_connecting_ip in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 120
[09-Jul-2023 13:00:45 UTC] PHP Warning:  Undefined property: Pirsch\HitOptions::$x_forwarded_for in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 121
[09-Jul-2023 13:00:45 UTC] PHP Warning:  Undefined property: Pirsch\HitOptions::$forwarded in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 122
[09-Jul-2023 13:00:45 UTC] PHP Warning:  Undefined property: Pirsch\HitOptions::$x_real_ip in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 123
[09-Jul-2023 13:00:45 UTC] PHP Warning:  Undefined variable $http_response_header in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 137
[09-Jul-2023 13:00:45 UTC] PHP Warning:  Trying to access array offset on value of type null in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 137
[09-Jul-2023 13:00:45 UTC] PHP Deprecated:  strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 467
[09-Jul-2023 13:00:45 UTC] Error sending page view:
[09-Jul-2023 13:00:46 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 507
[09-Jul-2023 13:00:46 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 507
[09-Jul-2023 13:00:46 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 507
[09-Jul-2023 13:00:46 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 507
[09-Jul-2023 13:00:46 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 507
[09-Jul-2023 13:00:46 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 507
[09-Jul-2023 13:00:46 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 507
[09-Jul-2023 13:00:46 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 507
[09-Jul-2023 13:00:46 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 507
[09-Jul-2023 13:00:46 UTC] PHP Warning:  Undefined property: Pirsch\HitOptions::$cf_connecting_ip in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 120
[09-Jul-2023 13:00:46 UTC] PHP Warning:  Undefined property: Pirsch\HitOptions::$x_forwarded_for in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 121
[09-Jul-2023 13:00:46 UTC] PHP Warning:  Undefined property: Pirsch\HitOptions::$forwarded in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 122
[09-Jul-2023 13:00:46 UTC] PHP Warning:  Undefined property: Pirsch\HitOptions::$x_real_ip in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 123
[09-Jul-2023 13:00:46 UTC] PHP Warning:  Undefined variable $http_response_header in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 137
[09-Jul-2023 13:00:46 UTC] PHP Warning:  Trying to access array offset on value of type null in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 137
[09-Jul-2023 13:00:46 UTC] PHP Deprecated:  strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /usr/www/users/user28e1/wp-content/plugins/pirsch-analytics/vendor/pirsch-analytics/sdk/src/Client.php on line 467
[09-Jul-2023 13:00:46 UTC] Error sending page view:

Hey Reece,
thank you for reporting! I'll take a look :)
I have a small test setup on wp.marvinblum.de which seems to be working fine: https://wp-mb.pirsch.io/?domain=wp.marvinblum.de&interval=7d&scale=day
What PHP, plugin, and WordPress version do you use? What's your configuration?
We can definitely get rid of the warning, but I think it should be working. Maybe errors aren't logged properly.

Hey Marvin, thanks for getting back and I forgot to add the versions, sorry. They are below:
Wordpress: 6.2.2
PHP: 8.1.20
Plugin: v1.5.5
I am pretty sure it should be working as no one else has posted an issue, may just be the hosting setup currently, if so it's getting a bit buggy from the company then and that sucks.

I published an update for the SDK fixing the warnings from your logs and a few other minor details: https://github.com/pirsch-analytics/pirsch-php-sdk/releases/tag/v1.8.1
The plugin will also be updated to make it less noisy and get rid of the warnings. But I don't think they are the reason why the plugin doesn't work for you. It's working for me on WordPress 6.2.2 and PHP 8.1.21.
Maybe we can figure out what's happening if I improve the error logging. Only having Error sending page view: isn't really useful, although I think it should have appended the exception message...

Just noticed that the exception is created by the SDK which probably means that the token could not be refreshed. Can you try using an access key (create a new one on the integration settings page) and remove the client ID. Just the secret is needed if you use an access key.


[FEATURE] Configure automated weekly releases

As discussed in our strategy meeting today, we plan to cut weekly releases of the ongoing development on unstable, which we can then promote to major/minor/patch releases whenever we think its justified.
I'll update here with details of the planned release process before I begin implementation.

This sketches out the general principle we’ll employ. Technical details will be
added subsequently.
We will implement trunk based development, with the following features:

Branching models

A single trunk for all development (this is just our current unstable,
should we rename?)
Since we work remotely and asynchronously, instead of committing directly to
trunk, we will work via small, short lived (i.e., 1-3 days) feature branches (we are
already aiming for this), enabling

Code Review
CI to protect against breaking master

Releases
We will follow late creation of release branches.

Releases are cut from a tag off the trunk.
When bugs are reported:

Branch or no branch?

If possible, we just fix the bug in the trunk and cut a new release (note,
this assumes that breaks to master are extraordinary, which they should be!).
If a release needs ongoing support, because users cannot update to the
latest version, then we cut a branch off of the tag.

Reproduce the bug in the trunk.
Add a test.
Fix the bug the bug with a feature branch.
Once it is integrated into trunk, cherry pick the fix into the release branch.

This sketches out the general principle we’ll employ. Technical details will be
added subsequently.
We will implement trunk based development, with the following features:

Branching models

A single trunk for all development (this is just our current unstable,
should we rename?)
Since we work remotely and asynchronously, instead of committing directly to
trunk, we will work via small, short lived (i.e., 1-3 days) feature branches (we are
already aiming for this), enabling

Code Review
CI to protect against breaking master

Releases
We will follow late creation of release branches.

Releases are cut from a tag off the trunk.
When bugs are reported:

Branch or no branch?

If possible, we just fix the bug in the trunk and cut a new release (note,
this assumes that breaks to master are extraordinary, which they should be!).
If a release needs ongoing support, because users cannot update to the
latest version, then we cut a branch off of the tag.

Reproduce the bug in the trunk.
Add a test.
Fix the bug the bug with a feature branch.
Once it is integrated into trunk, cherry pick the fix into the release branch.

Implementation plan

Keep unreleased changes in a file UNRELEASED.md.
Configure a github workflow triggered by a manual event:
https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows#manual-events

This will take two inputs, releaseVersion and nextVersion. See a dummy example here:
https://github.com/shonfeder/apalache/actions?query=workflow%3Arelease

The workflow will trigger the following sequence:

build and run the tests (including integration)
Prepare the release

Run mvn versions:set -DnewVersion={{releaseVersion}}-RELEASE
Move the UNRELEASED.md into a file RELEASE-NOTES.md
Add an empty UNRELEASED.md
Commit these changes, tag the commit with v{{releaseVersion}}, push the
changes to unstable

Build the package
Release the artifact to github

Using the github action sequence detailed here:  https://github.com/actions/upload-release-asset#example-workflow---upload-a-release-asset

Mark unstable as a snapshot

Run mvn --batch-mode release:update-versions -DautoVersionSubmodules=true -DdevelopmentVersion={{nextVersion}}-SNAPSHOT
Commit the changes, push them to unstable

Implementation plan

Keep unreleased changes in a file UNRELEASED.md.
Configure a github workflow triggered by a manual event:
https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows#manual-events

This will take two inputs, releaseVersion and nextVersion. See a dummy example here:
https://github.com/shonfeder/apalache/actions?query=workflow%3Arelease

The workflow will trigger the following sequence:

build and run the tests (including integration)
Prepare the release

Run mvn versions:set -DnewVersion={{releaseVersion}}-RELEASE
Move the UNRELEASED.md into a file RELEASE-NOTES.md
Add an empty UNRELEASED.md
Commit these changes, tag the commit with v{{releaseVersion}}, push the
changes to unstable

Build the package
Release the artifact to github

Using the github action sequence detailed here:  https://github.com/actions/upload-release-asset#example-workflow---upload-a-release-asset

Mark unstable as a snapshot

Run mvn --batch-mode release:update-versions -DautoVersionSubmodules=true -DdevelopmentVersion={{nextVersion}}-SNAPSHOT
Commit the changes, push them to unstable

After looking into logistics of pushing the release changes to unstable, I now see that this opens a security vulnerability (as per https://github.community/t/how-to-push-to-protected-branches-in-a-github-action/16101/5). The only way to enable this is to either make unstable unprotected or expose an admin API token to the workflow (and configuring our branch perms to allow admins to override the branch protection). That could be fine, except that either options then opens up the possibility that anyone could write an action would write to our main development branch just by opening a PR into the repo (unless we disabled running CI on PRs, but that's obviously not desirable).
So, until there is some mechanism to safely automate writes to protected branches from github actions, I think we we can instead do this in 3 steps:

Step 1: triggered by manual & scheduled workflows:

create a new RC candidate branch, including all steps EXCEPT for tagging and cutting the release:

prepare notes & mark release version (including generation of the RELEASE-NOTES.md file)
make release commit
increment version
make version bump commit

automatically open PR with changes into unstable

Step 2: manually

approval and merge of PR (since we plan to put STEP 1 on a schedule, this will be the only manual step needed)
wait for CI to succeed on the release commit, and push a version tag to the release commit

Step 3: triggered by version tags

release an artifact to github using the RELEASE-NOTES.md

This ensures that:

Randos can't write to our development branch through the CI.
We only tag release candidates that pass CI
The release commit is on our main development branch, and the artifact is built from the exact same commit that was committed to and passed CI on that branch.

After looking into logistics of pushing the release changes to unstable, I now see that this opens a security vulnerability (as per https://github.community/t/how-to-push-to-protected-branches-in-a-github-action/16101/5). The only way to enable this is to either make unstable unprotected or expose an admin API token to the workflow (and configuring our branch perms to allow admins to override the branch protection). That could be fine, except that either options then opens up the possibility that anyone could write an action would write to our main development branch just by opening a PR into the repo (unless we disabled running CI on PRs, but that's obviously not desirable).
So, until there is some mechanism to safely automate writes to protected branches from github actions, I think we we can instead do this in 3 steps:

Step 1: triggered by manual & scheduled workflows:

create a new RC candidate branch, including all steps EXCEPT for tagging and cutting the release:

prepare notes & mark release version (including generation of the RELEASE-NOTES.md file)
make release commit
increment version
make version bump commit

automatically open PR with changes into unstable

Step 2: manually

approval and merge of PR (since we plan to put STEP 1 on a schedule, this will be the only manual step needed)
wait for CI to succeed on the release commit, and push a version tag to the release commit

Step 3: triggered by version tags

release an artifact to github using the RELEASE-NOTES.md

This ensures that:

Randos can't write to our development branch through the CI.
We only tag release candidates that pass CI
The release commit is on our main development branch, and the artifact is built from the exact same commit that was committed to and passed CI on that branch.


Delete last point with  deleteLastVertex(), limit polyline to two vertexes

I want to limit the drawing/editing of a polyline to only two points, to get a line instead of a polyline, because I need to make calculations based on the start and end point of a single line that the user draws
I tried to remove the last point from a polyline after the on created event, but was not able to do, the typescript does not find the deleteLastVertex() using the following script.
 onMapReady(map: Map) {
     this._map.on(
         L.Draw.Event.CREATED,
         function(e) {
             if ((e as L.DrawEvents.Created).layerType === 'polyline') {

                const line = this.polylineToLine((e as L.DrawEvents.Created).layer as L.Polyline);

                line.deleteLastVertex();
             }
         }
      );
   }

When I use a different approach, like editing the latlngs of the line, it works more or less, because when you want to edit the line, you see all the original vertexes, see screenshot.
 polylineToLine(line: L.Polyline): L.Polyline {
      //line.editing.enable();
     // line.deleteLastVertex();

      let latlngs = line.getLatLngs() as LatLng[];
      if (latlngs.length > 2) {
         latlngs = latlngs.slice(0, 2);
         line.setLatLngs(latlngs);
      }

      // line.editing
      return line;
   }

Do you have an idea/suggestion?

I'm not sure how you'd add this behavior. It sounds more like a question for the leaflet.draw plugin itself. Or, you could ask on Stack Overflow.

I'm going to close this as it's not specifically an issue/question related to this plugin. Rather, it's specific to leaflet.draw, which can be found here: https://github.com/Leaflet/Leaflet.draw


[5.7] Remove --gc-sections for all targets for now

Similar to the comment here about wasm-ld, lld recently switched a
default that broke this for all elf targets. This is a low risk fix
since we weren't passing this flag before either. People who really need
this behavior can still pass something like -Xlinker --gc-sections -Xlinker -z -Xlinker nostart-stop-gc
Fixes https://github.com/apple/swift-package-manager/issues/5698

cc @airspeedswift

@swift-ci please test

Something wrong with the CI?

@swift-ci please smoke test


[BUG] VMs stuck terminating when provisioning through rancher

Describe the bug
When provisioning through rancher, some nodes did not get to the final step to register with k8s. Rancher deleted the existing node and brought up a new one, however that existing node never deleted in harvester.
To Reproduce
Steps to reproduce the behavior:

provision a single node-per-role rke1 cluster through rancher using rke1
wait for nodes to become active

Expected behavior
all nodes should come to a healthy state. any node(s) removed in the process should be properly removed from harvester.
Support bundle

supportbundle_f97ef78f-9917-4e2e-bcec-e8cf206e1090_2022-04-07T06-10-02Z.zip
Environment:

Harvester ISO version:  1.0.1-rc2
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): dell poweredge r510

this setup has rancher running on one of the harvester VMs.

Hi @slickwarren, I cannot reproduce this issue in Harvester v1.0.1 with Rancher v2.6.4. I can create RKE1 v1.22.7 with focal image (2 vCPU, 4G RAM and 40G storage).

Based on your support-bundle, I think you environment is:

1-node Harvester (24 CPU, 126G RAM)
9 VMs with 2 vCPU and 4G RAM
1 VM with 4 vCPU, 8G RAM

So your cluster should have enough resource to afford 10 VMs. However, in pods.yaml, it shows 6 VM pods has exited code 137 which is OOMKilled. Previously, we also have some VM OOMKilled issues, but they are not like this one.

https://github.com/harvester/harvester/issues/1823#issuecomment-1040004927
https://github.com/harvester/harvester/issues/1730#issuecomment-1057655226

I also notice there are some weird message in rke2-server.log:
rke2-server.service: Found left-over process 18135 (kubectl) in control group while starting unit. Ignoring.
This usually indicates unclean termination of a previous run, or service implementation deficiencies.

rke2[18551]: time="2022-04-06T21:54:22Z" level=warning msg="Failed to remove cgroup (will retry)" error="rmdir /sys/fs/cgroup/devices/kubepods/burstable/pod44d948f2100daf9e648ed38764ed4af7/32bb12a089a423d87ac14497b56e4f017e43632b59573eec61361fb3a08a1402: device or resource busy"

May you help me clarify these questions? Thank you!

Is this issue always reproducible on your cluster? If yes, may you try to run systemctl restart rke2-server.service and try again? Thank you.
Is there any special setting about RKE1?
Did you restart Harvester cluster with any error?

this is not consistently reproducible for me
there isn't anything special afaik about rke1/settings
I regularly restart my harvester setup, but this was on a fresh install of the RC.

RKE2 version is different on Harvester. v1.0.1-rc2 uses RKE2 1.22.7+rke2r1 and v1.0.1 uses RKE2 1.21.11+rke2r1.
On Harvester v1.0.1-rc2 cluster,  there is log like Failed to remove cgroup (will retry)" error="rmdir /sys/fs/cgroup/systemd/kubepods/burstable/podc37b8b12c8f57845c0ed443b5ac3d1ee/4f8391cfb6dea799bbaabcec3655eba00ea0728b83dc9f097cd8036b24d31279: device or resource busy, but this doesn't happen in Harvester v1.0.1.
I also can provision RKE1 on Harvester v1.0.1-rc2 without error.

In support-bundle, we can see the robustness of LH Volume is unknown. Also, logs in LH engine manager show Setting replica tcp://xxx to ERR due to: r/w timeout first, and then many I/O error: No backend available. So I think there may be network issue between the LH engine manager and replica manager.
I try to kill the connection between the engine manager and replica manager with the following steps. VM pod will be stuck in Terminating and its containerStatuses shows exitCode: 137. Also, logs in kubelet are similar to https://github.com/harvester/harvester/issues/2137.
E0428 08:10:24.558722   15240 nestedpendingoperations.go:335] Operation for "{volumeName:kubernetes.io/csi/driver.longhorn.io^pvc-d042adad-8254-4eba-b4dd-b378647e276f podName:c67e7a78-d489-4cf8-acb9-e8da287db975 nodeName:}" failed. No retries permitted until 2022-04-28 08:12:26.558706566 +0000 UTC m=+14240.221959502 (durationBeforeRetry 2m2s). Error: UnmapVolume.UnmapBlockVolume failed for volume "disk-0" (UniqueName: "kubernetes.io/csi/driver.longhorn.io^pvc-d042adad-8254-4eba-b4dd-b378647e276f") pod "c67e7a78-d489-4cf8-acb9-e8da287db975" (UID: "c67e7a78-d489-4cf8-acb9-e8da287db975") : blkUtil.DetachFileDevice failed. globalUnmapPath:/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/pvc-d042adad-8254-4eba-b4dd-b378647e276f/dev, podUID: c67e7a78-d489-4cf8-acb9-e8da287db975, bindMount: true: failed to unmount linkPath /var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/pvc-d042ada
d-8254-4eba-b4dd-b378647e276f/dev/c67e7a78-d489-4cf8-acb9-e8da287db975: unmount failed: exit status 32
Unmounting arguments: /var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/pvc-d042adad-8254-4eba-b4dd-b37864
7e276f/dev/c67e7a78-d489-4cf8-acb9-e8da287db975
Output: umount: /var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/pvc-d042adad-8254-4eba-b4dd-b378647e276f
/dev/c67e7a78-d489-4cf8-acb9-e8da287db975: target is busy.

Reproduce steps:

Start a 1-node cluster with harvester version v1.0.1-rc2.
Create a VM.
Get volume name of VM.
Login instance-manager-r-xxx.
Use ss to list socket connections and ss -K to kill connection.

root@instance-manager-r-37fa71ad:/# ss
Netid    State    Recv-Q    Send-Q             Local Address:Port               Peer Address:Port     Process
tcp      ESTAB    0         0            [::ffff:<IP_ADDRESS>]:10001       [::ffff:<IP_ADDRESS>]:38406
tcp      ESTAB    0         0            [::ffff:<IP_ADDRESS>]:8500        [::ffff:<IP_ADDRESS>]:41918
tcp      ESTAB    0         0            [::ffff:<IP_ADDRESS>]:10016       [::ffff:<IP_ADDRESS>]:38832
tcp      ESTAB    0         0            [::ffff:<IP_ADDRESS>]:10031       [::ffff:<IP_ADDRESS>]:57766
root@instance-manager-r-37fa71ad:/# ss -K dport = 57766
Netid    State    Recv-Q    Send-Q             Local Address:Port               Peer Address:Port     Process
tcp      ESTAB    0         0            [::ffff:<IP_ADDRESS>]:10031       [::ffff:<IP_ADDRESS>]:57766

I try the above steps on harvester master-head and I cannot reproduce anymore,  so I think the root cause is the same as #2137.

close as this issue can't be reproduced after fixing the issue https://github.com/harvester/harvester/issues/2137, feel free to reopen it if u encounter it again, thanks.


[analyzer] [Extension type] No error if member is called on nullable representation type

The following code produces errors in CFE but not in an analyzer
// SharedOptions=--enable-experiment=inline-class

extension type ET<T>(T _) {
  void test() {}
}

main() {
  ET(null).test();  // CFE: Error: Method 'test' cannot be called on 'ET<Null>' because it is potentially null.
  ET<int?>(42).test();  // CFE: Error: Method 'test' cannot be called on 'ET<int?>' because it is potentially null.
}

cc @eernstg to confirm that it is an analyzer issue
Tested on Dart SDK version: 3.3.0-edge.849459109a364f7f80ca82647ad088a4a6157ebc (be) (Sat Oct 21 02:18:48 2023 +0000) on "macos_x64"

@scheglov

Not sure I agree.
The extension type itself might not be non-nullable, but it doesn't have to be to get methods called, just like you can call regression methods on nullable types.
The test method exists on all instantiations of ET, and you should be able to invoke it using the code shown here. No member of the representation object is invoked, so it shouldn't matter that it's null.
I think it's CFE who's wrong here.

Not sure I agree.
The extension type itself might not be non-nullable, but it doesn't have to be to get methods called, just like you can call regression methods on nullable types.
The test method exists on all instantiations of ET, and you should be able to invoke it using the code shown here. No member of the representation object is invoked, so it shouldn't matter that it's null.
I think it's CFE who's wrong here.

Agreeing with @lrhn, this is a CFE issue.
It makes no difference for an extension type E whether it is potentially nullable or it is non-nullable, it is in any case allowed to invoke a member of the interface of E on a receiver whose static type is E.
This is similar to the treatment of extension members (extension, not extension type), where the on-type can be potentially nullable or nullable, but that won't make it an error to call the extension method on any receiver that matches that on-type.
extension E on int? {
  int? operator +(int? other) => switch ((this, other)) {
    (null, _) || (_, null)=> null,
    _ => this + other,
  };
}

void main() {
  int? i = null;
  print(i + i);
}

On the other hand, a type of the form T? has the usual effect:
extension type E(int it) {
  E operator +(E other) => E(it + other.it);
}

void main() {
  E? e;
  print(e + E(1)); // Error: `e` can be null.
}


AUR package question

@shaggytwodope
I wanted to try out installing the AUR package for myself so I setup a VM using this vagrant image: https://github.com/terrywang/vagrantboxes/blob/master/archlinux-x86_64.md
The installation went fine, but when I tried to launch rtv I got this error:
pkg_resources.DistributionNotFound: The 'requests>=2.4.0' distribution was not found and is required by rtv

I looked into it and found that some of the dependencies were installed to my system's python 3.5 packages
/usr/lib/python3.5/site-packages/rtv
/usr/lib/python3.5/site-packages/kitchen
/usr/lib/python3.5/site-packages/six

But some of them were installed into python 3.6
/usr/lib/python3.6/site-packages/requests
/usr/lib/python3.6/site-packages/bs4
/usr/lib/python3.6/site-packages/decorator

I guess this is because my system's default python is 3.5, but some of the dependencies don't respect that and pin the installation into 3.6 instead? As somebody who hasn't used Arch before, is this something that I should expect yaourt to handle for me, or is this my fault for not having my default python at the latest version?
Also, I saw that you dropped the mailcap-fix dependency from the package. What was the motivation for that? rtv won't start without it
Traceback (most recent call last):
  File "/usr/local/bin/rtv", line 7, in <module>
    from rtv.__main__ import main
  File "/usr/local/lib/python3.4/dist-packages/rtv/__main__.py", line 19, in <module>
    from .terminal import Terminal
  File "/usr/local/lib/python3.4/dist-packages/rtv/terminal.py", line 23, in <module>
    from mailcap_fix import mailcap
ImportError: No module named 'mailcap_fix'

So I'm unsure about the VM image in use, but when updates to python are made, typically arch enforces them pretty extreme. That is to say any depends should default to newest python version. Nothing gets held back. Why you even have 3.5 unless manually installed is very odd. Only 3.6 should be available to an arch install. Save for any custom user setup of course. It is odd to see that, most cases just reinstalling an aur package would suffice to use the system default (3.6), or version bump rebuild in official repos.
I was under the impression mailcap_fix would not be needed for python3.6 which is the default for Arch. I must have installed it via pip and not thought about it. Terrible mistake on my part. There are two options here, reintroduce mailcap_fix in the aur. Or add some type of check on python version. And then only import mailcap on 3.6. Whatever you prefer fine with me. I need to check out updates on a fresh install in the future, very sorry.

@michael-lazar What I have in mind, would be something to the effect of this.
import sys
if sys.hexversion >= 0x03060000:
    import mailcap
else:
    from mailcap_fix import mailcap

Of course if you find it simpler to add the dependency back I can do that.

@shaggytwodope I'll fix this on my end and push out a new release with conditional dependencies. I think in the long run that will be the better, I was avoiding it because it's kind of tricky to setup with pip.

I just released v1.15.1 which should allow the AUR package to work without mailcap_fix.

@michael-lazar updated mate.

👍


reloader: ignore chmod events, ensure same config state do not cause config reload

2021/11/02 14:23:18 Event: "/etc/nats-config/..2021_11_02_13_04_19.318044751": CHMOD
2021/11/02 14:23:18 Sending signal to server to reload configuration
2021/11/02 14:23:18 Event: "/etc/nats-config": CHMOD
2021/11/02 14:23:18 Sending signal to server to reload configuration
2021/11/02 14:24:36 Event: "/etc/nats-config/..2021_11_02_13_04_19.318044751": CHMOD
2021/11/02 14:24:36 Sending signal to server to reload configuration
2021/11/02 14:24:36 Event: "/etc/nats-config": CHMOD
2021/11/02 14:24:36 Sending signal to server to reload configuration
2021/11/02 14:25:44 Event: "/etc/nats-config/..2021_11_02_13_04_19.318044751": CHMOD
2021/11/02 14:25:44 Sending signal to server to reload configuration
2021/11/02 14:25:44 Event: "/etc/nats-config": CHMOD
2021/11/02 14:25:44 Sending signal to server to reload configuration
2021/11/02 14:26:58 Event: "/etc/nats-config/..2021_11_02_13_04_19.318044751": CHMOD
2021/11/02 14:26:58 Sending signal to server to reload configuration
2021/11/02 14:26:58 Event: "/etc/nats-config": CHMOD
2021/11/02 14:26:58 Sending signal to server to reload configuration
2021/11/02 14:26:58 Event: "/etc/nats-config": CHMOD
2021/11/02 14:26:58 Sending signal to server to reload configuration
2021/11/02 14:28:27 Event: "/etc/nats-config/..2021_11_02_13_04_19.318044751": CHMOD
2021/11/02 14:28:27 Sending signal to server to reload configuration
2021/11/02 14:28:27 Event: "/etc/nats-config": CHMOD
2021/11/02 14:28:27 Sending signal to server to reload configuration
2021/11/02 14:29:55 Event: "/etc/nats-config/..2021_11_02_13_04_19.318044751": CHMOD
2021/11/02 14:29:55 Sending signal to server to reload configuration
2021/11/02 14:29:55 Event: "/etc/nats-config": CHMOD
2021/11/02 14:29:55 Sending signal to server to reload configuration
2021/11/02 14:29:55 Event: "/etc/nats-config": CHMOD
2021/11/02 14:29:55 Sending signal to server to reload configuration

Closed by: https://github.com/nats-io/nack/issues/46


[stable/consul] Adding path option to ingress

What this PR does / why we need it:
I deploy regularly the helm charts for consul but this time I needed to deploy them on a subpath (ie: mydomain.com/consul) instead of a subdomain (ie: consul.mydomain.com) due to different requirement. I came to realize the charts didn't have that option.
Which issue this PR fixes

Adds a path field in both charts in order to add the option to deploy the charts on a subpath instead of a subdomain.

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @davidkarlsen

/ok-to-test
/assign
/lgtm


Reduce include recursion limit

I found that the current recursion limit does not work with TinyGo, it probably has a smaller max stack size than Go. I could confirm that 200 is too high and 100 works, didn't check in the middle. 100 seems high enough (even just 1 maybe ?) so I changed the constant, an alternative would be to use build tags to set to 500 normally and 100 only on TinyGo.

Thank you for contributing to Coraza WAF, your effort is greatly appreciated
Before submitting check if what you want to add to coraza list meets quality standards before sending pull request. Thanks!

Note: that go.mod and go.sum can only be modified for tested dependency updates or justified new features.
Make sure that you've checked the boxes below before you submit PR:

[X] My code includes positive and negative tests.
[X] I have an appropriate description with correct grammar.
[X] I have read Contribution guidelines, maintainers note and Quality standard.

Thanks for your PR :heart:

Up to @jptosso and @fzipitria. A good starting could be to see why 500 as
chosen in the first place and then decide wether we want to use same value
across go/tinygo, different or configurable.
On Thu, 4 Aug 2022, 09:38 Anuraag Agrawal, @.***> wrote:

I found that the current recursion limit does not work with TinyGo, it
probably has a smaller max stack size than Go. I could confirm that 200 is
too high and 100 works, didn't check in the middle. 100 seems high enough
(even just 1 maybe ?) so I changed the constant, an alternative would be to
use build tags to set to 500 normally and 100 only on TinyGo.
Thank you for contributing to Coraza WAF, your effort is greatly
appreciated
Before submitting check if what you want to add to coraza list meets quality
standards
https://github.com/corazawaf/coraza/blob/master/CONTRIBUTING.md#quality-standards
before sending pull request. Thanks!
Note: that go.mod and go.sum can only be modified for tested
dependency updates or justified new features.
Make sure that you've checked the boxes below before you submit PR:

My code includes positive and negative tests.
I have an appropriate description with correct grammar.
I have read Contribution guidelines
https://github.com/corazawaf/coraza/blob/master/CONTRIBUTING.md#contribution-guidelines,
maintainers note
https://github.com/corazawaf/coraza/blob/master/CONTRIBUTING.md#maintainers
and Quality standard
https://github.com/github.com/corazawaf/coraza/v2sso/coraza-waf/blob/master/CONTRIBUTING.md#quality-standards
.

Thanks for your PR ❤
You can view, comment on, or merge this pull request online at:
https://github.com/corazawaf/coraza/pull/307
Commit Summary

febacb9
https://github.com/corazawaf/coraza/pull/307/commits/febacb9a49baac17487397760f58aafd398ec878
Reduce include recursion limit

File Changes
(1 file https://github.com/corazawaf/coraza/pull/307/files)

M seclang/parser.go
https://github.com/corazawaf/coraza/pull/307/files#diff-f73e6b849d0fa747f9e706cbdb5ec76083f712530e21d64ea917cc37eb6347c5
(2)

Patch Links:

https://github.com/corazawaf/coraza/pull/307.patch
https://github.com/corazawaf/coraza/pull/307.diff

—
Reply to this email directly, view it on GitHub
https://github.com/corazawaf/coraza/pull/307, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYAUZSYQB5XZCXP6PCTLVXNXQXANCNFSM55RPSOOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

No problem, nobody should even reach 100.


compatible(integration_test_charm.yaml): Add jhack tail to logs

Reverts #224
Uses huge speed improvement from https://github.com/canonical/jhack/pull/175 —thank you @PietroPasotti!

should be live soon on <IP_ADDRESS>


SnackbarConfiguration properties: PositionClass, PreventDuplicates and others in Startup.cs are ignored

Bug type
Component, Docs (mudblazor.com)
Component name
MudSnackbarProvider
What happened?
The Snackbar configuration in Startup.cs seems to be ignored, I've configured it like so:

I can only get them to work if I manually set these properties before executing a Snackbar.Add() method call.
Expected behavior
SnackbarConfiguration properties should be applied.
Reproduction link
https://try.mudblazor.com/snippet/maQGEtQWSrcejFmA
Reproduction steps

Configure Snackbar in Startup.cs
Execute Snackbar.Add() method in any page

Relevant log output
No response
Version (bug)
6.0.16
Version (working)
No response
What browsers are you seeing the problem on?
Firefox, Chrome, Microsoft Edge
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Which .NET are you using? I have this config also but in the Program.cs (.NET 6).

I updated MudBlazor to the latest version and cleared the browser cache and still had this issue.

I have this issue as well. I am using MudBlazor 6.0.16 on .NET 6

Which .NET are you using? I have this config also but in the Program.cs (.NET 6).

I’m using .NET 6 and MudBlazor 6.0.16

Any updates?

Any updates?

V 6.0.17, still not fixed (

@SwipeX You're right and that's why I will consider this issue solved and closed.

This bug is because you have multiple calls to builder.Services.AddMudServices

How come? Where are multiple calls?
       public static void Configure(WebAssemblyHostBuilder builder) {             builder.Services.AddMudServices(config => {                 config.SnackbarConfiguration.PositionClass = Defaults.Classes.Position.TopCenter;                 config.SnackbarConfiguration.PreventDuplicates = false;             });         }

This bug is because you have multiple calls to builder.Services.AddMudServices

How come? Where are multiple calls?
public static void Configure(WebAssemblyHostBuilder builder) { builder.Services.AddMudServices(config => { config.SnackbarConfiguration.PositionClass = Defaults.Classes.Position.TopCenter; config.SnackbarConfiguration.PreventDuplicates = false; }); }

Can you post a gist link to your entire file? There may be alternative causes, but what I found was most users examples had multiple calls to AddMudServices

Same thing here, with only one call to AddMudServices().


[BUG]: A timeout occurred on api.together.xyz

How are you running AnythingLLM?
Docker (remote machine)
What happened?
On running the image and try to use the workspace thread, it was timed out.

Are there known steps to reproduce?
No response

This is not a bug with AnythingLLM. TogetherAI's API was/is down so chats were failing. If you continue to get the Cloudflare downtime page then it is your specific connection to TogetherAI (probably VPN related?)

Hi @timothycarambat , thanks for the clarification, I have verified that together api seems to wokring fine,  Is there anyway to verify that via anything llm?

We dont pre-verify a connection to any specific providers - so sending a chat would be the only way at this time to ensure the same API call reaches TogetherAI

I did just use my own key with Together AI and was able to successfully send a chat and get a streamed response back

Okay.  Looks like issue on together ai api on some specific models.  Im having issue running the zero-one-ai/Yi-34B-Chat where as 'Lllama-3' seeems to be working fine.  Anyway thanks for the help.


OperationalError: no such column: django_x509_ca.organization

Hi ,
it was working well for long time. Suddenly "OperationalError: no such column: django_x509_ca.organization " error came. not able to use Ca and Cert tables. Even in django admin page also it shows same error. please help me in this.
Thanks.

Closing because can't replicate this issue.


added permission 6660 6661 6650 6651

added permission table data 6660 6661 6650 6651 rmid

@AlessandroLongoni thanks, approved


#581 add description to templates

Resolves #581

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

8 of 8 (100.0%)  changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 96.192%

Files with Coverage Reduction
New Missed Lines
%

CourageScores/ClientApp/src/components/admin/Templates.js
1
97.09%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
8502

Relevant Lines:
8580

💛  - Coveralls


refactor: Configurator state side effects

This PR extracts the side effect of changing a field or one of its options to the UI encodings. I believe this should make it much more clear what happens when a given option is changed.
The reason for this change was that currently, the logic to create chart option selectors, and what happens when they change, is hugely separated, which made it difficult to handle changes to the app in the past, as unexpected things would happen if you forgot to check / add a new side effect in the configurator state – now it's all consolidated in UI encodings.
So, instead of having:

UI encodings defined in /charts/config-ui-options,
rendering of UI encodings in /configurator/components/chart-options-selector,
side effects logic defined in /configurator/configurator-state,

we have:

UI encodings and side effects defined in  /charts/config-ui-options,
rendering of UI encodings in /configurator/components/chart-options-selector.

Configurator state reducer calls getChartFieldChangeSideEffect or getChartFieldOptionChangeSideEffect respectively when field or option changes.

👍 Really nice change. It should reduce the number of touched files when introducing a new field / feature, that's really nice 💯

Thanks for reviewing @ptbrowne! Yes, that should be done like you suggested, I'll make the change 👍


error: can show custom image as bg in a View React-native

"nativewind": "^2.0.11",
"react": "18.1.0",
"react-native": "0.70.6",
tailwind.config.js

how can I show this custom image ? Thx

React Native does not support background image styles - so they are unsupported in NativeWind.


Initialize Contributors list

Utilizing @all-contributors bot, add contributors.

@all-contributors please add @tangollama for code
@all-contributors please add @tangollama for ideas

@all-contributors please add @tangollama for code, ideas

@all-contributors please add @danielgolden for ideas, code and design

@all-contributors please add @wesleyradcliffe for ideas, code

@all-contributors please add @devfreddy for tool, code


Cant run

Error: Cannot find module '/home/bean07/Desktop/AGAR-XPBOT/Facebots.js'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:902:3
module.js:340
throw err;
^
Error: Cannot find module '/home/bean07/Desktop/AGAR-XPBOT/Facebots.js'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:902:3

I have the same error.

You need to be in the src folder.
The bots are patched...

Le 20 mars 2016 à 08:11, Wrooar<EMAIL_ADDRESS>a écrit :
I have the same error.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub


feat(DataTable): add support for alphanumeric, datatable, and custom sort functions

Closes https://github.com/github/primer/issues/1832
Closes https://github.com/github/primer/issues/1833
Changelog
New

Add alphanumeric sort strategy
Add datetime sort strategy
Add support for a CustomSortStrategy
Add support for custom sort strategy

Changed

Update stories to use alphanumeric and datetime sort strategies

Removed

@colebemis if you have a second, would love your help on some of the TS issues I'm running into in the sort method 🤔 Really not sure what to do (it's the todo comments over in this file)


Backrest: Add version 1.4.0

Adds a manifest for the Backrest software. Tested with a local and global installation and uninstallation. Also checked the manifest updates automatically.
Closes #13978

[x] I have read the Contributing Guide.

/verify

I made the modification on my side, and I didn't know any change will be pushed to the PR 😅.

/verify

Please update to the latest version, otherwise looks good.

/verify

Updated to the latest version

/verify


Failed to connect to couchdb.openwhisk port 5984: Connection timed out

Here is the log tail when tried to bring CouchDB on K8S.
`+ ansible-playbook -i environments/local setup.yml -e db_host=couchdb.openwhisk -e db_prefix=test_ -e db_username=whisk_admin -e db_password=some_passw0rd -e db_port=5984 -e openwhisk_home=/openwhisk
CouchDB is up and running
/openwhisk/ansible /openwhisk /var/lib/couchdb
PLAY [localhost] ***************************************************************
TASK [Gathering Facts] *********************************************************
Monday 11 September 2017  18:31:50 +0000 (0:00:00.024)       0:00:00.024 ******
ok: [localhost]
TASK [find the ip of docker-machine] *******************************************
Monday 11 September 2017  18:31:50 +0000 (0:00:00.548)       0:00:00.572 ******
skipping: [localhost]
TASK [get the docker-machine ip] ***********************************************
Monday 11 September 2017  18:31:50 +0000 (0:00:00.027)       0:00:00.600 ******
skipping: [localhost]
TASK [gen hosts for docker-machine] ********************************************
Monday 11 September 2017  18:31:50 +0000 (0:00:00.032)       0:00:00.633 ******
skipping: [localhost]
TASK [add new db host on-the-fly] **********************************************
Monday 11 September 2017  18:31:50 +0000 (0:00:00.029)       0:00:00.662 ******
skipping: [localhost]
TASK [check if db_local.ini exists?] *******************************************
Monday 11 September 2017  18:31:50 +0000 (0:00:00.025)       0:00:00.688 ******
ok: [localhost]
TASK [prepare db_local.ini] ****************************************************
Monday 11 September 2017  18:31:51 +0000 (0:00:00.267)       0:00:00.955 ******
changed: [localhost -> localhost]
TASK [gen untrusted server certificate for host] *******************************
Monday 11 September 2017  18:31:51 +0000 (0:00:00.437)       0:00:01.392 ******
changed: [localhost -> localhost]
TASK [gen untrusted client certificate for host] *******************************
Monday 11 September 2017  18:31:51 +0000 (0:00:00.320)       0:00:01.713 ******
changed: [localhost -> localhost]
PLAY RECAP *********************************************************************
localhost                  : ok=5    changed=3    unreachable=0    failed=0
Monday 11 September 2017  18:31:52 +0000 (0:00:00.394)       0:00:02.108 ******
Gathering Facts --------------------------------------------------------- 0.55s
prepare db_local.ini ---------------------------------------------------- 0.44s
gen untrusted client certificate for host ------------------------------- 0.39s
gen untrusted server certificate for host ------------------------------- 0.32s
check if db_local.ini exists? ------------------------------------------- 0.27s
get the docker-machine ip ----------------------------------------------- 0.03s
gen hosts for docker-machine -------------------------------------------- 0.03s
find the ip of docker-machine ------------------------------------------- 0.03s
add new db host on-the-fly ---------------------------------------------- 0.03s
/openwhisk /var/lib/couchdb

popd
curl -X PUT http://couchdb.openwhisk:5984/_config/admins/whisk_admin -d '"some_passw0rd"'
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
curl: (7) Failed to connect to couchdb.openwhisk port 5984: Connection timed out

`

Sounds like your issue is that you cannot use a Pod's service to communicate back with the pod. I had put a troubleshooting guid in another section of the READMEs for this, but maybe I need a more general section. This used to only happen for Kafka. Link

Not tried promiscuous mode but updating container env var DB_HOST to localhost worked in one of clusters. In another cluster it just worked without change. We yet to figure out the inconsistency in our cluster.
Thanks Dan for the quick response!


Date picker

A date picker 😍😍😍

I've added a demo date picker item in master
https://github.com/alexaubry/BulletinBoard/blob/b196f08c8a8b648a23decdd04fe702d51f80fc79/Example/Swift/Bulletin/DatePickerBulletinItem.swift#L13
The API used to create it will be available in the next release.


[Toolkit feature]: Flashlight Feature

Contact Details (Optional)
No response
What is the context of the feature/improvement?
In the RTX-Remix toolkit, while viewing the captures in Asset Replacements, I think it'd be beneficial to add a "flashlight" feature while viewing/moving around the world. As of now, if a scene doesn't have existing lights, I have to manually add a light to a random mesh just to be able to see my scene sometimes. Rather than doing this, I think adding a little flashlight feature while moving around would help while navigating captures.
Please describe the feature/improvement?
This feature would help assist in scenes that are dim, allowing the modder to see better, without actually adding a light to the scene.
What would be your solution? (optional)
...
Version
2024.3.1
Media
No response

Jira created: REMIX-3218

This is a duplicate of https://github.com/NVIDIAGameWorks/rtx-remix/issues/331 and has been resolved.


Update math tests to JUnit Jupiter

Upgrade the tests in the math package to use JUnit Jupiter as part of the effort to remove the dependency on the Vintage Engine.
While most of these changes are drop-in replacements with no functional benefit, there are some non-obvious changes worth mentioning.
Unlike org.junit.Test, org.junit.jupiter.api.Test does not have an expected argument. Instead, an explicit call to org.junit.jupiter.api.Assertions.assertThrows is used.
Unlike org.junit.Assert.assertEquals(double, double, double), org.junit.jupiter.api.Assertions.assertEquals(double, double, double) does not support deltas of zero, only strictly positive deltas. This issue will be addressed in JUnit Jupiter 5.4 (see https://github.com/junit-team/junit5/pull/1613 for details). In the meanwhile, assertTrue(expected==actual) was used, and TODO comments were placed in the code to refactor it to assertEquals once JUnit 5.4 is available.
It's also worth noting this is a minimal patch for migrating the package's tests to Jupiter. There are several tests that can be made more elegant with Jupiter's new features, but that work is left for subsequent patches.

Coverage remained the same at 95.253% when pulling 47a9ea7c828772625b9e26c0c7a6db494ea626a3 on mureinik:junit-jupiter-math into f110da945a8af0914f348cfe576b5a8257159fd9 on apache:master.

Thanks! 👍


Add settings navigation menu on Plugin toolbar menu

Another way to easily navigate to the Waifu Motivator Plugin settings page.

Resolved by #71


zen audit config and svc addition

https://github.ibm.com/IBMPrivateCloud/roadmap/issues/50812
https://github.ibm.com/IBMPrivateCloud/roadmap/issues/50813
https://github.ibm.com/IBMPrivateCloud/roadmap/issues/50817

Can we make logDNA support available if zen is not deployed?

@yannizhang2019 ,  Yes it is available even if zen is not enabled.


New+ Dated Folders and Text Files

Description of the new feature / enhancement
Enhance the New+ tool as follows:
If we create a template folder or file with a name that includes e.g. yyyy_mm_dd then this will be replaced with the current date.
If we create a template text file containing e.g. dd/mm/yyyy then this is replaced with the current date in the file.
Other tags for time, etc.
Scenario when this would be used?
It would make the already useful New+ much more powerful
Supporting information
No response

+1

+1

Really like this idea, thank you for sharing!
Note: I think this might be the first issue related to this. but I just came across this one. There are a number similar issues that we could probably merge (I don't have permission for to do that).
I've started working on some variable support (date and time related, environment variables, and the parent folder name), and hope to release those in a future update. See also https://github.com/microsoft/PowerToys/issues/35287#issuecomment-2495176827


53034 timeout interceptor

What
Enable timeout customization for HttpConnection
How
Created a TimeoutCustomizationInterceptor.
Changed ConnectOptions for timeouts.
Constructed a TimeoutCustomizationInterceptor from the options and added it to the list of interceptors.
Testing
New tests for read and connect timeouts.
reviewer @emlaver
reviewer @brynh

+1

+1


Updating tests and example to use Grunt 1.0.0-rc1

Opening for follow up work from #236.

Closing in favor of #243 and #244.


Documentation updates: pr template

Add in PR template **full changelog**: https://github.com/obervinov/_templates/compare/1...2 by @ obervinov https://github.com/obervinov/_templates/pull/1

done
https://github.com/obervinov/users-package/pull/9/commits/7ea03cdf001ab889098784454de7d3d961a8ee8b


IMAP "Show only subscribed folders" doesn't work for "standard" (well-known) folders

Expected behavior
Archive, Drafts Inbox, Sent, Spam and Trash should be hidden if they are unsubscribed and "Show only subscribed folders" (Account settings -> Fetching mail -> Incoming server) is set for an IMAP account.
Presumably the non-IMAP K9mail-errors folder would remain but that's a separate issue.
Actual behavior
These folders are always shown even if they are unsubscribed and "Show only subscribed folders" is set. Other unsubscribed IMAP folders are hidden correctly by this setting.
This means that those folders can only be hidden by duplicating folder management effort using K-9's (client-specific, client-side) folder class mechanism.
It also complicates subsequent IMAP folder creation, since folder class display needs to be changed to see the new folder, the new folder classed, and then folder class display changed back again.
Environment
K-9 Mail version: 5.207
Account type (IMAP, POP3, WebDAV/Exchange): IMAP

I think they're always subscribed actually. The reality is that the app needs to subscribe to the core folders for the app to work properly. What we should actually do is prevent you from thinking you can unsubscribe from them at all IMO.

They're not always subscribed (and there's nothing special about any IMAP folder except INBOX, per RFC 3501). It's completely valid to unsubscribe from all folders, even including INBOX.
It's possible for a client to interact properly with a server and any relevant folders without them being subscribed - IMAP doesn't care if the folder is subscribed or not for relevant operations (e.g. COPY/STORE), so provided the client isn't for example checking for the existence of folders with LSUB instead of LIST (which it shouldn't), it should work fine. And I have other clients that work without issue (including e.g. moving messages to Trash when Trash is unsubscribed).
What functions would not work if K9 followed the subscriptions list equally for the above folders?
Preventing the user from thinking they can be unsubscribed from is the wrong end of the stick - this is entirely permissible per IMAP (and is server-side, so unsubscription may well have been done elsewehere).
It might be a substantial amount of work/validation, so fair enough then if it's wontfix on that basis, but this is a valid bug, and there is nothing in IMAP that prevents its resolution ;)

I mean in K-9 they're always subscribed.
i.e. it's not the listing of folders that's broken but the subscription process itself.
The reason is we have always treated special folders differently.

If you don't need the special folders to actually be special you should be able to get rid of them in K-9 Mail by going to 'Account settings > Folders' and settings the various special folders to "-NONE-". Then refresh the folder list.

I mean in K-9 they're always subscribed.

So K-9 ignores the IMAP subscription info for these and treats them internally as "subscribed" regardless you mean?
So is this just a fairly deeply entrenched architectural barrier to fixing this bug?

If you don't need the special folders to actually be special you should be able to get rid of them in K-9 Mail by going to 'Account settings > Folders' and settings the various special folders to "-NONE-". Then refresh the folder list.

Doesn't work unfortunately - all the special folders are still shown. It also wouldn't have covered Trash if I want to still be able to delete messages without having to see the folder (presumably setting Trash to -NONE- prevents deletion, or maybe not?)

Any plans for this? Would be nice to be able to unsubscribe from some folders.


Create metarepo with documentation

Should we create a centralized repository with documentation that links out to all of the CIS workflow repositories? We can use RTD or GitHub pages so that there's an actual website for users to reference.

I'm thinking we could name the new one something like cis-infrastructure. If we can build the cis-bidsutils Sphinx documentation in the cis-infrastructure site, that would be great too.

Can we just call it something like cis-meta or cis-infra? The whole cis-infrastructure name just looks long and unwieldy to me.

Sure, cis-infra sounds good. cis-meta sounds more like it's related to meta-analysis to me. Or the analysis of CIS metadata (like scans and stuff).

I forgot that GitHub limits domains based on the organization name, so it would actually end up being fiu-neuro.github.io/cis-infra/, which I don't love. What about making a FIU-Neuro.github.io repo for the parent website.

I've started work in https://github.com/FIU-Neuro/FIU-Neuro.github.io so I will close this now.