API calls failing with Error querying the database: db error: FATAL: remaining connection slots are reserved for non-replication superuser connections

Bug description
I have been running my app on GCP that connects to a postgres instance also running in GCP, for the past few months. However, since yesterday, my REST API calls are only working intermittently.
I have been getting this error about 50% of the time. Other times, it seems to work fine:
Error querying the database: db error: FATAL: remaining connection slots are reserved for non-replication superuser connections
I have been initializing one prisma instance per endpoint (total 8 endpoints) and till date have had zero issues using connection_limit=80&pool_timeout=50 on the DB string.
I am not sure if it is from have idle open connections that aren't closing or if it is from my prisma queries or some other issue. Can you kindly advise me on how to fix this issue? Any help would be much appreciated. I am unable to reproduce this issue as it is quite sporadic.
Thank you
Default
2021-05-17 17:10:00.614 GMTInvalid `prisma.instance.findMany()` invocation:
Default
2021-05-17 17:10:00.614 GMT
Default
2021-05-17 17:10:00.614 GMT
Default
2021-05-17 17:10:00.614 GMT Error querying the database: db error: FATAL: remaining connection slots are reserved for non-replication superuser connections
Default
2021-05-17 17:10:00.614 GMT at cb (/server/models/prisma-client/runtime/index.js:79166:17)
Default
2021-05-17 17:10:00.614 GMT at processTicksAndRejections (internal/process/task_queues.js:97:5)
Default
2021-05-17 17:10:00.614 GMT(node:14) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
Default
2021-05-17 17:12:00.721 GMT(node:14) UnhandledPromiseRejectionWarning: Error:
Default
2021-05-17 17:12:00.721 GMTInvalid `prisma.events.findMany()` invocation:
Default
2021-05-17 17:12:00.721 GMT

Here is an example of the an endpoint where prisma instance gets initiated:
require('../../config/config');
const express = require('express');
const router = express.Router();

const prisma = require('../models/prismaClient.js');
const sendEmailSummary = require('../functions/sendEmailSummary');

router.post('/', async (req, res) => {
    await sendEmailSummary(prisma);
    res.sendStatus(200);
});

module.exports = router;

And here is the prisma client:
require('../../config/config');
const { PrismaClient } = require('./prisma-client');

const url = process.env.DATABASE_URL;
let prisma;

if (process.env.NODE_ENV === "production") {
  prisma = new PrismaClient({
    datasources: { db: { url } },
  })
} else {
  if (!global.prisma) {
    global.prisma = new PrismaClient({
      datasources: { db: { url } },
    })
  }
  prisma = global.prisma
}

module.exports = prisma;

How to reproduce

Expected behavior
Should be returning values from database
Prisma information

Environment & setup

OS:  MacOS
Database: PSQL
Node.js version:  14
Prisma version: 2.18.0

Prisma Version
2.18.0

Hi @shwethashyam1, the error message you mention in the title indeed means that all connections are in use and no new ones can be opened. Do you maybe have monitoring on that database that can show you the open and idle or active connections, optimally in relation to your database connection limit?
The connection_limit=80 you mentioned, times 8 instances/endpoints would mean that in theory your applications can in parallel open 640 connections. Is that lower than the number of maximum supported connections of your database instance?
Your 8 instances are all running constantly I assume?

Hi janpio, apologies for the late reply! I completely missed this comment. You are right in (the implication) that the # connections may be higher than the number of maximum supported connections of your database instance.
That is exactly the case. My cloudSQL database supports up to 250 connections.
As for the 8 instances, about 5 of them are cron jobs. The remaining three are REST APIs.
Does this mean I will need to reduce the connection limit?

Probably yes, or add some retry middleware that catches the error message, waits a bit and just tries again (this assumes that e.g. the cronjobs make sure to free the connections again after they have been used and do not just keep them open for an hour until the next run). The math should work out in a way that you will not go over the number available.
(Often the cheaper and easier solution is to just increase the limit by paying a bit more though.)

So I figured out what the issue was. Sometimes (maybe 1 in 10 times or less often), when the prisma query is incorrect (for e.g. if I have incorrectly specified a field or a field doesn't exist), prisma is not throwing the error itself.
Instead it opened a lot of prisma connections and doesn't seem to close it -- so subsequent prisma queries ended up throwing the "fatal db.." error. I haven't enforced typescript so that could a way I can prevent incorrect queries to begin with. But perhaps could there be an issue also with prisma's error handling messages?

Absolutely, if you have a reproduction for this it would be amazing. We should really try to fix this of course.

Hi @janpio
struggling to repro this error even though it still happens sometimes (especially now when running my jest tests). Should I close this for now, or keep it open?

Let's keep it open a bit and you just come back to it if you find a reproduction or get more information - otherwise we will close it in a few weeks or months.

Hi @janpio an update: this also seems to happen more when I am running my app on localhost and then deploying it to google cloud after. There is a lot of query-engine-darwin processes that I then manually have to kill to prevent this error from happening in google cloud. Should I try adding ?pgbouncer=true in my connection string?

If you are not using PgBouncer for Postgres, no.
Are you talking to the same database locally as on your deployment on Google Cloud? If you have many local query engine processes running, this would make sense that it blocks a lot of connections. The question then becomes: Why do you have these many local connections open?
If I understand your code snippet above correctly, it should make sure you only have 1 PrismaClient instance running usually that gets reused across the app, not instantiate new ones all over the place. Can you observer how the number of open Query Engine Processes increases?
We currently have a preview feature nApi which uses a different architecture to run the Engine, which should not be in danger of having the same behavior. Maybe you can try that out: https://github.com/prisma/prisma/issues/6301

Yes, the database url is exactly the same and you are right, technically, with the above prisma client in the code snippet, it shouldn't spawn new instances so rapidly.
Running app on localhost w/o pgAdmin 4:  It usually goes up to ~50 query-engine-darwin processes on my activity monitor when the error happens.
Deploying as a container on google cloud: Sometimes I have about 6-8 query-engine-darwin processes open (even after killing/quitting pgAdmin 4), when this error pops up.
I will look into nApi, thank you!

Running app on localhost w/o pgAdmin 4: It usually goes up to ~50 query-engine-darwin processes on my activity monitor when the error happens.

Does it go up first, and then the error or the other way around? I would expect it going up over time to cause the error sooner or later.

I usually check the processes after encountering the error and it is around 50+. Then I terminate all of them locally and wait for the error to happen again - by then the # processes would have increased to the same.

Ok then this is the reason for your problem.
Maybe observe the process list to see how it goes from 1 to 2 (or whatever starts that increase) and see if you can identify the action that does that. Something you are doing - or your code is - has that effect and should be fixed.

Ok I will look into it :)

Connection pool not killing idle connections is expected, I am working on it on https://github.com/importcjj/mobc/pull/60
In localhost make sure that if you are running ts-node or npx or other that it properly kills children. i had instances where the engine was not properly killed if the parent didnt call sigterm or if the application catched the signal and didnt call close on the prisma client.

I have experienced this twice in a production app. The situation resolves itself after 5-10 minutes usually, but all Prisma queries return this error during that time.

Hi, I am facing the same issue, I am using cloud SQL and running a containerized nestjs app on cloud run.

@garrensmith This is due to the reaper not doing its job after a load spike (and being bad in general). My PR on original mobc should help/point in the right direction. https://github.com/importcjj/mobc/pull/60

@callumlocke can you confirm what version of Prisma you are using?
@Sytten thanks. Once I have a moment I'll take a look.

I'm having this issue with "@prisma/client": "^4.10.1" :(

To fix this issue ,Actually
💁

I added  prisma.$disconnect(); after each query.

    const degreeData = await prisma.degree.findUnique({
      where: where,
    }).finally(() => {
      prisma.$disconnect();
    });

Then we added connection_limit=20&pool_timeout=50
Based on the maximum pool connection we have
To see the maximum connection in postgres
SHOW max_connections;
OR
SELECT name, setting FROM pg_settings WHERE name = 'max_connections' OR name = 'max_worker_processes';

And also to terminate all the  connected connection
SELECT pg_terminate_backend(pg_stat_activity.pid) FROM pg_stat_activity WHERE pg_stat_activity.datname = 'db_name'  AND pid <> pg_backend_pid();

Then , I removed await Promise.all([query1, query2]) and make that as seperate query.

Now it was fixed.
Prisma Team , kindly confirm this changes , I have made are correct and about each points.
**Thank you **  😃😍

Hi @shwethashyam1, @Sytten, and @Venkat03003, we are investigating how to reproduce this issue.
From my understanding, this issue presents itself when a long-running server has a Prisma Client connected to a Postgres database, as some connections from the pool are leaking. What's not clear is whether this only happens with the GCP Postgres instances, or with any Postgres instance. Would you consider this a faithful reproduction of this issue? If so, it looks like the problem is solved as of mobc 0.8.1 (https://github.com/importcjj/mobc/issues/63), which we have pulled in as of<EMAIL_ADDRESS>(https://github.com/prisma/prisma-engines/pull/3905). Just in case, I encourage you all to try again with the most recent Prisma version (5.0.0) to assess whether this issue is still present. Thanks!

i had instances where the engine was not properly killed if the parent didn't call sigterm or if the application catched the signal and didnt call close on the prisma client.

As far as I know, we've fixed a bug related to the Prisma Query Engine not terminating properly several months ago, but that doesn't exclude some other bug still exists.

Prisma Team, kindly confirm these changes

@Venkat03003, which Prisma version did you use in this comment above?

Hello!
Unfortunetely, we are also experiencing this issue. Same scenarioas everyone else has discussed: Everything seems to be working fine then suddenly our connection spikes and the app becomes inactive for ~5 min until it eventually fixs itself.
We have a web app that uses Prisma to interact with a PostgreSQL DB.
Originally we were using Prisma version 3.14, but after reading this we updated our packages to version 5.0. Sadly, the issue still comes up.

Here is a graph from AWS showing the connection spikes where we are encountering the issues.
I have not been able to reproduce the issue. The spikes seem to be completely random.
Reading through this tread. I saw that @Venkat03003 manually disconnected his connection. This is something I have not tried yet. However, my assumption is that this is not necessary with Prism’s connection pooling. Also, reading this connection guide from Prisma (https://www.prisma.io/docs/guides/performance-and-optimization/connection-management) it explicitly says: “You do not need to explicitly $disconnect().”
I am not sure if this is an issue with Prisma or if this is some kind of issue on our end. We are continuing to investigate the situation. Just thought I would contribute to the matter to keep the discussion alive.
Thanks

I got this, too!
We are building things on Vercel with Prisma + Supabase DB.

Hi Jacky!
Sorry, it has been a few weeks since you commented. I figured I would share some updates we had though.
Originally, I do not think we had the pooling set up properly. We were just connecting directly to our db: "postgresql//...." Then I was made aware of Prisma's Data Proxy service. THIS was the connection pooling service we were looking for. Now we would connect to the pooling service: "prisma//..." So, we had set that up. Unfortunately, we were still having problems. However this time it was different. Instead of it being the connection limit, we were getting 504 errors because our requests were timing out. After reaching out to Prisma, in turned out it was a bug on their end. Nurul worked with me on this and his service was fantastic.
Eventually I was informed it was fixed, and we were invited to use Prisma Accelerate which contains their Data Proxy service and things seem to working great. We even noticed significant improvements in our load times. Here is what our connection chart looks like now for the past 4 weeks:

Hope this helps!
-Joey

Does anyone have an idea on how to reproduce this behavior of the in-use connection exploding?
Does this go beyond your configured Pool connection_limit when it happens or does it just use all of them?

@janpio its been a while since I touched that code, but here is a typical usecase:

Smaller postgres DB with connection limit of 100
Service with connection pool of max 20 x 3 instances (60 connections total max)
You do a blue/green type update of services, that spawns 3 new instances
If you are under load the new services will try to grab new connections as soon as they receive traffic
GCP Cloud Run doesnt have guarantees and I have seen some containers take up to 10m to get killed
Usually to counter that you set an aggressive idle timeout, but for a long time the connection pool of prisma didnt enforce those (in the background at least). I think this is fixed?
That results in connection limit errors that was originally posted 2y ago

So my take away before closing would be:

Write documentation around this issue and the connection limit of postgres
Suggest users use some kind of pooler or prisma proxy to fix it
if not possible, suggest they increase the connection limit of postgres if they can (usually I set the limit to 2x the expected usage to have my rolling update buffer)
Also suggest and explain how to set the connection idle timeout and how this will impact (pros and cons) the application

Also double check that the idle timeout is actually respected before all that 😅
I think it can be a strong argument to use prisma proxy for many potential customers since technical and non technical will be able to appreciate the non negligible effort that needs to be done to avoid hitting a DB connection limit when running many instances of an application.

@Sytten @aliedp @garrensmith @janpio @callumlocke @jackypan1989 @Jolg42  could you guys give detailed view about pool management in NodeJS with Prisma  and Postgres db.
Why we need to append in this postgres db url with connection_limit=20&pool_timeout=50
what is connection_limit and pool_timeout
About Ram Size , and buffer Size (For Every Query , for operations it will use some memory) in Postgres reated to Postgres.
while managing pool , we have to consider Ram , buffer size , pool timeout , and connection_limit for each instance.
Anyone kindly explain this about above points in detailed view and share your points and thoughts regarding that.

@venkateshb-icanio It is not appropriate to mention a list of users in a comment that is not about the original issue. Please don't do this (I will edit teh @ mentioned out of your message) and open a new discussion instead (without at-mentioning anyone). Thank you.

Service with connection pool of max 20 x 3 instances (60 connections total max)
You do a blue/green type update of services, that spawns 3 new instances
If you are under load the new services will try to grab new connections as soon as they receive traffic
GCP Cloud Run doesnt have guarantees to kill old containers and I have seen some containers take up to 10m to get killed

So, the situation you describe it is more or less expected to run into this error, correct?

Usually to avoid that problem that you set an aggressive idle timeout (10-60s), but for a long time the connection pool of prisma didnt enforce those (in the background at least). I think this is fixed?

Isn't an idle timeout enforced on the database side (considering that Prisma does not offer an option to set one for the connection pool, it has to be) so the connections should be closed from the server side and hence not take up connections any more? (Only Prisma will still potentially think the connection is still open, but as that is on the old deployment it will not try to run a query any more).
Am I missing something?
Your other points are of course correct.

So, the situation you describe it is more or less expected to run into this error, because the deployment can indeed end up using more connections than the database can provide, correct?

Correct but the pool and the engine can help mitigate this. It can retry when it sees this error and it can kill idle connections.

Isn't an idle timeout enforced on the database side (considering that Prisma does not offer an option to set one for the connection pool, it has to be) so the connections should be closed from the server side and hence not take up connections any more? (Only Prisma will still potentially think the connection is still open, but as that is on the old deployment it will not try to run a query any more).

Usually the idle timeout is handled by the client pool. I know the setting postgres idle_in_transaction_session_timeout exists but usually its locked by the cloud provider and AFAIK prisma doesn't have a way to run code on connection open so you cant easily set it on each connection.
I believe I added the support for idle timeout in quaint more than a year ago, but it never was documented? But also it didnt work in the past because you need a reaper background thread or tokio task to kill the connections. I think that was fixed in mobc by someone at Prisma a couple months ago.
So like I said it kinda "works as intended" but prisma could help devs handle the error better and reduce the occurrence of it (and its a good selling point for your managed service).

any update on this? I'm currently having this issue using Prisma, Postgres and Digital Ocean.

This problem also exists on supabase and github actions images. Any updates on this please?

any update here, every time i need to restart the db server.

any update on that ?

There's a similar problem where hot reloading causes too many connections to be open. If you're one of those, please use the following to resolve this:
https://www.prisma.io/docs/orm/prisma-client/setup-and-configuration/databases-connections#prevent-hot-reloading-from-creating-new-instances-of-prismaclient
More specifically, just create a client.ts file to ensure a single instance of PrismaClient stays. Hope this helps!

I solved it with this code. I hope it can be helpful to someone.
`import { INestApplication, Injectable, OnModuleInit, Inject } from '@nestjs/common';
import { PrismaClient, Prisma } from '@prisma/client';
import { REQUEST } from '@nestjs/core';
import { ApmHelper } from '...';
import apm from 'elastic-apm-node';
import { transformSqlShort, transformSqlDetailed } from './instrumentationUtil';
type Event = { timestamp: Date; query: string; params: any; duration: number };
const MAX_LABEL_LENGTH = 1000;
@Injectable()
export class PrismaService extends PrismaClient implements OnModuleInit {
constructor(@Inject(REQUEST) private request: Request) {
super({
log: [
{
level: 'query',
emit: 'event',
},
{
level: 'info',
emit: 'event',
},
{
level: 'warn',
emit: 'event',
},
{
level: 'error',
emit: 'event',
},
],
});
this.$use(async (params, next) => {
  const span = ApmHelper.Instance.getApmAgent().startSpan(
    `${params.model}.${params.action}`,
    `prisma`,
    params.dataPath.join('.'),
  ) as apm.Span;
  ApmHelper.Instance.getApmAgent().currentSpan?.setLabel('prisma:model', params.model);
  try {
    return await next(params);
  } catch (error) {
    throw error;
  } finally {
    if (span) span.end();
  }
});
// This will in fact log the queries but they will not be correctly shown in the span tree.
this.$on('query' as never, async (e) => {
  const e2 = e as Event;
  const agent = ApmHelper.Instance.getApmAgent();
  const isTransactionSampled = (agent.currentTransaction as any)?.sampled || false;
  if (agent.currentTransaction && isTransactionSampled) {
    const span = agent.currentSpan;
    if (span) {
      assignLabels(span, e2);
    } else {
      const endTime = e2.timestamp.getTime();
      const startTime = new Date(endTime - e2.duration);
      const options: apm.SpanOptions = { startTime: startTime.getTime() };
      const span2 = agent.currentTransaction?.startSpan(transformSqlShort(e2.query), 'db', options);
      if (span2) {
        assignLabels(span2, e2);
        span2?.end(endTime);
      }
    }
  }

  function assignLabels(span: apm.Span | null, _e: Event) {
    span?.setLabel('db_statement', transformSqlDetailed(_e.query));
    span?.setLabel('db_statement_raw', getStr(_e.query));
    span?.setLabel('db_params', getStr(_e.params));
  }
});

}
async onModuleInit() {
await this.$connect();
}
async enableShutdownHooks(app: INestApplication) {
process.on('beforeExit', async () => {
await app.close();
});
}
function getStr(params: any): apm.LabelValue {
try {
return JSON.stringify(params).substring(0, MAX_LABEL_LENGTH);
} catch (error: any) {
return 'Error parsing params: ' + typeof params + ' ' + error?.message;
}
}
`


Parse -api graphql schema and determine what is available

When an api is defined and thus a new graphql client created, download the schema, parse and work out what is available and what is not.

Currently, when the root component is mounted, all defined apis are iterated through and a graphql client created for each defined api by calling CoreApi.createClient().  In createClient(), it stores the client state in vuex:
// Add a vuex apis entry
          this.$store.commit('addApi', {
            title: api,
            value: { ...{ state: false, auth: false, icon: null, uuid: null }, ...clientdata }
          })

The 'state' is set to false by default, and only set to true if a Status message is received from the api which marks it as alive.
Periodically (once per second), the root component (src/App.vue) fires a timer which scans each client and if it hasn't been seen active within the last ten seconds it marks the 'state' as false again.
Then, a component will add GraphQL queries/subscription that it needs, by calling something like:
        this.createQuery('NavSatFix', navSatFixQuery, api, 'navSatFixData', !api.state)
It passes the 5th parameter !api.state, which corresponds to the skip parameter of createQuery().   This means that if the api state is false (ie. if it hasn't yet successfully received a single Status message), then the skip state of the query is set to True - in other words all calls or blocked while skip is True - it's disabled.
This is quite effective, but limited.  It assumes that if it receives a Status message, all other messages are available.  So when Status is received, it turns on all the various Mavlink queries/subscriptions, even if they're not enabled in -api.  This will lead to failures and errors.  We can't do a similar thing for any or all of the mavlink and other graphql messages, because we have to know that they're available in order to create the query, activate it and listen for messages.
We assume that the Status message is always available - it's effectively the core metadata message of the -api instance and must always be available.
There are two methods to work round this problem:

Add a modules list to the Status message, which is updated by -api to include the active modules available.  The Status message is a subscription, so the -web client will automatically update immediately upon receiving a message update from -api and reflect the changes in the api metadata held in vuex.
Retrieve and parse graphql schema, work out what is available, and store this in the api metadata in vuex.

Naively, can we replace !api.state with !verifyQuery(navSatFixQuery, api)?

Naively, can we replace !api.state with !verifyQuery(navSatFixQuery, api)?
Yes, absolutely!

What you're describing will work, but it's awfully complicated and requires multiple pulls/parses of the remote schema.
Isn't it just easier to add a schema/modules field to the Status message that keeps an up to date list of what is available?  This will be automatically updated through the Status message subscription in the client, with 1/100th of the code and effort, and will be more immediate and faster without the remote schema pull/parsing.  I get the schema parse is more 'correct', but technically -api should be able to reliably set in Message.schema what is in the schema anyway?

I think it will be much more fragile by consuming API data via graphql as you propose (rather than using the published schema). The code to pull and verify the schema is already in place in -web where as I would need to write python code to grab all the graphql info and then a graphql message(s) to discribe the queries. We would then need to somehow match the -web graphql queries against the details published by -api via naming or similar.  IMO it's a not a good idea.

If you are agreeable to let me do the leg work on this issue I'll happily go down the python route if / when the JavaScript route fails spectacularly.

Sure, your ideas usually work out better than mine anyway!!

verifyQuery() needs the gql document which isn't always available.  For example in plugins/core/CoreApi.js there is a watcher set that fires whenever the window is not visible, to turn off all the gql queries.  When it becomes visible again, it turns them all on.  However this now turns on all the 'skipped' queries that verifyQuery was used to disable.  There's no way to verify all the queries in all the components because we don't know what gql documents were used to create them.

If verifyQuery() gets a schema which isn't complete or correct (eg. incomplete schema happens during component bootstrap, sometimes is still present during mounted()), then the validation fails and produces errors.  I've trapped the errors but it returns incorrectly and causes failure.
But apart from that working well now.
Probably the hashing should be removed in favour of the api key?

The hash used for lookup is a hash of the (gql) query string which is stored against the api key. So if we remove the hash we still need a unique, hashable, and reproducible key for each schema defined query.
I was thinking to use the queryKey you created here: https://github.com/goodrobots/maverick-web/blob/master/src/plugins/core/CoreApi.js#L161 but that looks like many unique queries can use the same underling gql code. So.... maybe it makes sense to map the queryKeys to verifiedQuery checks so that gql->hash->verified and queryKey->hash->verified lookups can occur?
Re the incomplete schema during component bootstrap, can we move the schema request to the start of the client creation and run the client creation in an async call (at the same time) as the schema request. Then at the end of the client creation we await the schema call to return (if it hasn't already). This way we know for sure when the modules find the client instance the validation code is ready to go?

re

Re the incomplete schema during component bootstrap, can we move the schema request to the start of the client creation and run the client creation in an async call (at the same time) as the schema request. Then at the end of the client creation we await the schema call to return (if it hasn't already). This way we know for sure when the modules find the client instance the validation code is ready to go?

See https://github.com/goodrobots/maverick-web/commit/91c884657592c7b6914db01e8996e67bd7e502d6

It's all getting a bit complicated.. I've been trying to keep the graphql setup as simple as possible, with as little code as possible, because the setup is very delicate.
What about leaving the schema fetch and any validation requests until after the api has been marked good?  When a client is created, a connection is made straight away.  It then creates a Status query/subscription for that api, and when it gets a successful Status message back from -api, it marks apis[api].state = true.  As long as the api.state==true then it's fully ready for use.

Wont the Status query/subscription for that api fail without validation? or are we not validating that?Either way we have to wait for the schema before we can attach any more queries...

Yeah currently we just assume that the Status query is available - I think that's a reasonable assumption, a reasonable basic dependency that -api provides Status at all times.


⚠ Panoramas has degraded performance

In 29c69d6, Panoramas ($SITE_URL_PANORAMAS) experienced degraded performance:

HTTP code: 200
Response time: 3337 ms

Resolved: Panoramas performance has improved in 13a4b5d after 10 minutes.


Is there a way to pass store from app, down into route components?

Hey there!
So i'm kinda new to Svelte js - and am experimenting with using it for a small new project.
Just wondering if there's a trick to getting the store to be passed down to the route
components...?
I'm currently using: "svelte: ^1.47.1"
Store is currently created and passed into the app like so:
index.js (webpack entry):
import App from './app.html';
import { Store } from 'svelte/store.js';

const store = new Store({
  animal: 'dog',
  sheep: 'baaah',
});

const app = new App({
  target: document.body,
  store,
});

export default app;

app.html:

  mooo
  <RouterLink to="/">Home</RouterLink>
  <RouterLink to="/welcome">Welcome</RouterLink>

animal: {{$animal}}

home.html:

home page!

inside app.html:

animal: {{$animal}}

renders as:

animal: dog

as expected.
If i try and access:

{{$animal}}

from home.html, i get the following error:
Uncaught TypeError: Cannot read property '_init' of undefined

Actually, it would also be awesome to know how to pass other props down to Route components...?
ATM, it looks like Route components are completely isolated from any options / state / store data that exists in the app where the router is configured (in my case, app.html).

#https://github.com/jikkai/svelte-router/pull/6

😀 Merged.


json disappeared from readme

Would like to know how to add a json file with my .m3u playlist and xmltv data in if possible. Noticed the example code has gone from the readme file also.

I have been working on documenting the app in greater detail on the
website. Information on the JSON is available here:
http://cumulustv.herokuapp.com/docs/Syncing/Editing_JSON.html
On Jan 23, 2017 9:04 AM, "cumulususer"<EMAIL_ADDRESS>wrote:

Would like to know how to add a json file with my .m3u playlist and xmltv
data in if possible. Noticed the example code has gone from the readme file
also.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Fleker/CumulusTV/issues/238, or mute the thread
https://github.com/notifications/unsubscribe-auth/ADI587WvTghPGBsAsQn7f7rS15G8UzY3ks5rVLNWgaJpZM4LrE0m
.


bug: Gemini1.5 Pro & Flash 002

Version
v1.35.1727367923 (pre-release)
Describe the bug
I would like to be able to use and try the new models: Gemini1.5 Pro 002 & Flash 002
Expected behavior
Choose between Gemini 1.5 Pro, Gemini 1.5 Pro 002, Gemini 1.5 Flash, & Gemini 1.5 Flash 002
Additional context
No response

Same here. Dont have those models.

As an update to anyone curious: the current implementation uses as far as I can tell gemini-latest which points to the 002 models


Python Module Option Now Off in CMake

As discussed here:
https://github.com/AcademySoftwareFoundation/openvdb/blame/master/tsc/meetings/2019-10-10.md#L46
Disable the Python Module in CMake by default so that it's more likely that a first time user attempting to build OpenVDB will succeed.

Just noticed, there's a comment at the top of the root CMakeLists.txt which states that the python module is built by default - needs to be updated with this.

Just noticed, there's a comment at the top of the root CMakeLists.txt which states that the python module is built by default - needs to be updated with this.
in build.txt, the OpenVDB Components table also needs updating

Thanks, updated!


In some instances, the deck seem to "unlink" from the cards, and becomes disfunctional.

In some situations, all basic functions of the deck are lost completely. It seems that while some functions seem to fail without errors being thrown, if you reload the game they will begin to throw errors.
Discard: Error happens without refresh
Uncaught (in promise) Either this card isn't part of this deck, or it's not been properly drawn yet!

Post refresh:
Draw: Draw dialog opens, but after choosing "take cards" this error is thrown
Uncaught (in promise) TypeError: Cannot read property 'drawCard' of undefined
    at tileHud.js:145
    at Generator.next (<anonymous>)
    at tileHud.js:7
    at new Promise (<anonymous>)
    at __awaiter (tileHud.js:3)
    at Object.callback (tileHud.js:127)
    at Dialog.submit (foundry.js:13537)
    at Dialog._onClickButton (foundry.js:13498)
    at HTMLButtonElement.dispatch (jquery.min.js:2)
    at HTMLButtonElement.v.handle (jquery.min.js:2)

View discard pile
Uncaught (in promise) TypeError: Cannot read property '_discard' of undefined
    at tileHud.js:156
    at Generator.next (<anonymous>)
    at tileHud.js:7
    at new Promise (<anonymous>)
    at __awaiter (tileHud.js:3)
    at showDiscard (tileHud.js:154)
    at HTMLElement.<anonymous> (tileHud.js:94)
    at HTMLElement.dispatch (jquery.min.js:2)
    at HTMLElement.v.handle (jquery.min.js:2)

Reset
Uncaught (in promise) TypeError: Cannot read property 'resetDeck' of undefined
    at tileHud.js:162
    at Generator.next (<anonymous>)
    at tileHud.js:7
    at new Promise (<anonymous>)
    at __awaiter (tileHud.js:3)
    at resetDeck (tileHud.js:161)
    at HTMLElement.<anonymous> (tileHud.js:98)
    at HTMLElement.dispatch (jquery.min.js:2)
    at HTMLElement.v.handle (jquery.min.js:2)

Shuffle
Uncaught (in promise) TypeError: Cannot read property 'shuffle' of undefined
    at tileHud.js:166
    at Generator.next (<anonymous>)
    at tileHud.js:7
    at new Promise (<anonymous>)
    at __awaiter (tileHud.js:3)
    at shuffleDeck (tileHud.js:165)
    at HTMLElement.<anonymous> (tileHud.js:102)
    at HTMLElement.dispatch (jquery.min.js:2)
    at HTMLElement.v.handle (jquery.min.js:2)

View Deck
Uncaught (in promise) TypeError: Cannot read property '_state' of undefined
    at tileHud.js:175
    at Generator.next (<anonymous>)
    at tileHud.js:7
    at new Promise (<anonymous>)
    at __awaiter (tileHud.js:3)
    at viewDeck (tileHud.js:169)
    at HTMLElement.<anonymous> (tileHud.js:105)
    at HTMLElement.dispatch (jquery.min.js:2)
    at HTMLElement.v.handle (jquery.min.js:2)

Additional info
At this point as well, having refreshed the page, the "Discard" button no longer functions at all (no error), and doesn't appear to have an event listener attached. The "hand" persists, the cards can be flipped, played to the table, returned from the table to hand, reordered, etc.
But the deck is totally broken. Deleting the deck from the scene, and dropping it on again from the Journal doesn't fix it, in fact it can not be dropped onto the scene again. Doing so does output a log:
DragEvent {isTrusted: true, dataTransfer: DataTransfer, screenX: 4712, screenY: 1595, clientX: 872, …}altKey: falsebubbles: truebutton: 0buttons: 0cancelBubble: falsecancelable: trueclientX: 872clientY: 413composed: truectrlKey: falsecurrentTarget: nulldataTransfer: DataTransfer {dropEffect: "none", effectAllowed: "all", items: DataTransferItemList, types: Array(0), files: FileList}defaultPrevented: truedetail: 0eventPhase: 0fromElement: nullisTrusted: truelayerX: 872layerY: 413metaKey: falsemovementX: 0movementY: 0offsetX: 872offsetY: 413pageX: 872pageY: 413path: (5) [canvas#board, body.vtt.game, html, document, Window]relatedTarget: nullreturnValue: falsescreenX: 4712screenY: 1595shiftKey: falsesourceCapabilities: InputDeviceCapabilities {firesTouchEvents: false}srcElement: canvas#boardtarget: canvas#boardtimeStamp:<PHONE_NUMBER>001266toElement: canvas#boardtype: "drop"view: Window {parent: Window, opener: null, top: Window, length: 0, frames: Window, …}which: 1x: 872y: 413__proto__: DragEvent
drop.js:19 CardTS:

However nothing appears in the scene.
The only remedy is to delete the journal folder for the deck, and re-import it. However the issue returns later.

Additional Information:

Foundry 0.6.5
Server: Node.js v14.3.0
Client: Google Chrome Version 86.0.4229.0 (Official Build) dev (64-bit)
Deck: 54 card sample deck

It would appear that deck becomes undefined after a page refresh in all cases. Even just importing the deck, then reloading, results in the deck no longer functioning.

Can not confirm in recent testing, closing.

Yes, this seems to be resolved now. The multiple folders called "Decks" problem seems to have been the root cause.


[Bug]: File Picker for gsheets needs to be shown on blank page

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When I create google sheet datasource with specific sheets option, I am seeing file picker being displayed on top of datasource review page, it should be displayed on top of blank page as per designs
Steps To Reproduce

Create google sheet datasource
Select specific sheets as option
Once authorisation is done, observe the file picker being shown on datasource review page

Public Sample App
No response
Environment
Deploy Preview
Issue video log
No response
Version
NA

Moving this to product backlog as it is a low/medium priority issue


Migration to .NET Core

.NET Core Migration (nearly) complete
All tests pass (remember to start the storage emulator on Windows
before starting the tests, see
https://docs.microsoft.com/en-us/azure/storage/common/storage-use-emulator)

Awesome work @paviad, let me know when you think you're complete.

I think it's complete :)
On Wed, Jun 19, 2019 at 2:40 AM Richard Astbury<EMAIL_ADDRESS>wrote:

Awesome work @paviad https://github.com/paviad, let me know when you
think you're complete.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/azure-contrib/AzureDirectory/pull/31?email_source=notifications&email_token=AAJNV2GKFTLTYPFE5DXULTLP3FW6JA5CNFSM4HYSDZY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYAINUQ#issuecomment-503350994,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJNV2AWYK3PYBCDPZVYVJDP3FW6JANCNFSM4HYSDZYQ
.

awesome :¬)


Validate schema against examples

What problem do you want to solve?
We create json schema reference for our system and associate test to it.
What do you think is the correct solution to problem?
Because examples are a part of the json schema specification since DRAFT-06, we should also validate examples. This validation must be optional to prevent breaking change and also because "Each entry should validate against the schema in which is resides" (not a MUST... it's a SHOULD 😢 ).
Will you be able to implement it?
I need a closer look to the code to say that.
Example of possible usage
// First proposal, not breaking change
ajv.validateSchemaExamples(schema);

// Second proposal, no breaking change if default value set to false
ajv.validateSchema(schema, true);

// Third proposal, breaking change, strict validation of examples
ajv.validateSchema(schema);

// Fourth proposal, no breaking change, fluent interface
ajv.validateSchema(schema).validateExamples();

It can be a plugin - it doesn't have to be in Ajv. See https://github.com/epoberezkin/ajv#annotation-keywords and https://github.com/epoberezkin/ajv#plugins

@epoberezkin I purpose because ajv is about validation json schema validation and examples is a part of the spec. Nevermind, thx for the suggestion ;)
Have a nice day ;)


Any ideas how to use it on multiple instances?

I'm sorry, but I'm a little bit confused here. Image I have a huge batch that needs processing. I want to process it on multiple server instances. How can I ensure that the data will be assigned  proper version?

Hi @olegserov,
A few questions to clarify your scenario:

Should all the files from the batch be processed the same way in (theoretically) parallel?
What are you going to do with the outputs? Choose only the best output or combine\assemble all the outputs?
Would you like to create all the outputs in a new branch or the same (master) branch is fine?

Dmitry, thanks for the quick response.

Yes, I was thinking about feature extraction on thousands of input files. It can be easily sped up by processing it on multiple instances/cpus.
I am thinking about collecting them into one batch-revision-checkpoint (I don't know the right terminology in the project's context). I am not talking about a map-reduce (when the individual outputs are disregarded and only merged output is saved).
I don't see any restrictions here...

Performing computation in the cloud is not implemented in the current DVC version. So, you need to run cloud machines and clone the git repository to the machines manually.
Then you just run computations on separate machines file by file, dvc commits the changes. After all the computations are done - don't forget to push your changes to a correct (master) branch of the repository and don't forget to sync data to a cloud storage dvc sync on each machine.
If everything is done correctly you will have your repository with all the changes and all the files in your cloud storage. git pull && dvc sync will update all the data into your machine.
All the version will be correctly assigned. Versions through Git repository and data/content through cloud storage.

Thank you!


correct documentation for windows powershell based on issue #12393

Correct documentation for powershell  based on issue #12393
Describe correct behavior of powershell and pwsh

@steved0x
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team

Could you also add #hacktoberfest-accepted label in order to count the commit?

#sign-off


📎 Update ESLint benchmark to v9

Description
ESLint v9 was released yesterday, and it enables flat config by default, deprecating the old config format. We should update the benchmark infra to update ESLint and its config

I'd like to handle this issue

@Conaclos
Thank you for your guidance!
I've updated conaclos/update-bench in my local environment and did git push -f upstream conaclos/update-bench but it seems I couldn't update the branch.
So I created the new branch and sbumitted https://github.com/biomejs/biome/pull/2407
Is this correct approach?

i think conaclos' branch is out of date, you could submit a pr with just your changes instead


Animations make me nervous and distract me from debugging

Testing https://github.com/microsoft/vscode/issues/127362
To be honest, I believe this is a VS Code core issue, but the TPI asks to create all issues here 🤷♂ .
Notice how the progress bar is animated on top of the cell and how the time is rotating and updating every .1s. This is making me feel like I need to hurry up with my debugging and gives me an uncomfortable feeling:
https://user-images.githubusercontent.com/5047891/123930117-b975fc00-d98f-11eb-9f4f-e7ad0d116ab4.mp4

This was fixed on Monday, maybe it missed yesterday's Insiders? @DavidKutu said it works today

You're right, sorry about the noise!


Quick start sample code wrong output

Hi,
I tried
chmod +x demo_test.sh
./demo_test.sh

But the .jpg image and .png images are same. Actually, no segmentation happened on output image.
I am trying your code on google colab.

Shouldn't be, maybe you can check what happened here:
https://github.com/CSAILVision/semantic-segmentation-pytorch/blob/master/test.py#L30

I've reviewed the code and it seems right, but I did not have enough time to check the numerical values. But I have got the same result. I will try to share a notebook with corresponding results.
Thank you

Sorry, you were right.
My browser problem!


AppVeyor Build Problems

Hello @jberezanski :)
Can you help us with cocur/slugify#157?
Installing KB3035131...
WARNING: Update KB3035131 installation failed (exit code 1058).
WARNING: More details may be found in the installation log (C:\Users\appveyor\AppData\Local\Temp\1\chocolatey\KB3035131.Install.evt) or the system CBS log (C:\windows\Logs\CBS\CBS.log).
ERROR: Update KB3035131 installation failed (exit code 1058).
The install of kb3035131 was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\KB3035131\Tools\ChocolateyInstall.ps1'.
 See log for details.

Too old issue.


Accelerator delete modal

Goal
Create a accelerator delete modal with the ability to bulk delete and cascade delete compatible images
Dependency issue

https://github.com/opendatahub-io/odh-dashboard/issues/1375
A way to fetch compatible images from a device

Itemized goals

Delete modal is opened in single delete mode by selecting a rows ellipsis action button or by the bulk select ellipsis when only one row is selected
Delete modal is opened in bulk delete mode when multiple rows are selected and the bulk select ellipsis is selected v(not the rows delete ellipsis)
Confirm deletion by typing the device name i.e. A100
If deleting multiple devices, confirm deletion by selecting a radio select option
If there are compatible images to the device, then display a list of those images

each list item should include the name, a checkbox to select it, and a expandable section
the expandable section should include:

a dropdown select option for each version found for the image
a list of software and packages present in the image. This is found from the image annotations
selecting a version from the dropdown does nothing for selecting which version is removed. they all get removed regardless of the selected version. this is for informational purposes only

if bulk deleting devices, the compatible images are shown under each device respective to the device they are attached to
if no compatible images then hide the list and accompanying text
follow how pipelines does bulk deleting with the option to abort, and showing deletion progress.

Aspects continued elsewhere

https://github.com/opendatahub-io/odh-dashboard/issues/1375

Mocks

https://www.sketch.com/s/d8550d2f-fae4-44fd-82df-9f400563d459/a/3oxP1aD
https://www.sketch.com/s/d8550d2f-fae4-44fd-82df-9f400563d459/a/vRLwOLe

UX Needed
@yannnz
This is for the delete modal for the accelerator admin panel. Is bulk deleting still a desired function? If not, should the table still be checkboxes?

@Gkrumbach07 If there are not many accelerators practically, we can remove the bulk deleting. And we will not need the checkboxes. I will update the design. cc: @xianli123

Hi @yannnz @Gkrumbach07 Based on the discussion and requirements, I updated the original design and removed the bulk deletion. Here is the design link for reference. Please take a look and leave your comments if you have any suggestions for the design. Thanks!


High Memory Usage

Hi, I'm experiencing high RAM and SWAP memory usage when using Jobs. I'm sending a heap dump report from Eclipse Memory Analyzer: https://i.imgur.com/zU3qolN.png
Jobs version: <IP_ADDRESS>
Server Type (Spigot/Paper/etc): Pufferfish
Server Version (using /ver): 1.19.3

Hello!
I found out that this exact same thing is happening to some people using jobs reborn.
Some of my co-workers might be able to tell more if asked, but we have found that there might be some cleaning required in the plugins code.
a screenshot from one of my co-workers:


Add watermark to downloaded circuit image

I have added a light grey watermark that's saying "Made with CircuitVerse" at the bottom of any circuit image that will be exported.

@satu0king Thank you so much for pointing this out to me and explaining the issue in more details! I'll update the pull request again with my new changes.

Hey @mohammedsafwat, do we have any update on this, thank you.

@satu0king Safe to close this PR I guess.

Hey @mohammedsafwat, do we have any update on this, thank you.

@armudgal Very sorry for my late reply! I worked on some improvements but unfortunately, I didn't have the chance to review them and create a pull request. But for now, I guess it's safe to close this PR too.


Mention the environment variable TEALDEER_CONFIG_DIR in the README

This may help people looking for a way to place their configuration file into a different directory.

Thanks!


Images_OLA

Closed test issue: link for getting images to wiki https://ardalis.com/add-images-easily-to-github/


Some emojis aren't big when they have a skin tone applied to them

No content

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @CSab6482 in #android-bugs.

Request to reopen. The emoji combination 🤏🕶😳 was small for me on the latest PlayStore release as of June 20, 2021

This issue has been fixed


It is possible to uncheck all display options

And you never see the application again. I can run it and kill it but I cannot get back to the options menu. Tried uninstalling and reinstalling.

ill issue a fix tomorrow!

By Default SpotMenu should always be shown on the menubar when it's running. If no info should be shown, the default icon is visible.
Run the following command in terminal to make the SpotMenu icon setting checked
defaults write com.KMikiy.SpotMenu showSpotMenuIcon true

Then just to be sure start a song or skip to the next song on Spotify


Using toast-ui.vue-image-editor, memory release issues

When I use toast-ui.vue-image-editor, I encounter memory unreleased when I close.
I loaded a PNG image of about 5MB and initialized the component (and loaded the picture) on the Chrome browser.Memory will increase by about 100MB-300MB. When I quit, I called clearUndoStack (), clearRedoStack (), destroy () and destroyed the element.But memory will not be released, even if it waits for a period of time.
Here is the data monitored by memory(use:node process.memoryUsage()).
Object {rss: 188645376, heapTotal: 77209600, heapUsed: 42227456, external: 19802529}
Object {rss: 291049472, heapTotal: 47980544, heapUsed: 42436336, external: 322589150}

The title is incorrect. I use tui. image - editor directly.

@MoyanLiu I'll check about it.

Did you find any problems? I use windows Chrome.

@junghwan-park Hello, because this component is an important part of my project, please help solve this problem.


✨quilt_rails as Rails Engine

Description
Fixes https://github.com/Shopify/quilt/issues/839
This PR converts the quilt_rails gem into a Rails Engine. There is more we can do to take full advantage of what Engines offer (better/consistent error handling, etc...), but with this PR a consumer of the gem simply needs to mount the Engine at a path they want, and the controller and routes are no longer required (though still supported). This simplifies the installation process.
Question: I did not add tests, should I delete the test/dummy directory or learn how to write tests or neither?
Type of change

[x] gems/quilt_rails Minor: New feature (non-breaking change which adds functionality)

Checklist

[x] I have added a changelog entry, prefixed by the type of change noted above
[x] I have prefixed my pull request title with the corresponding emoji from this guide

We noticed that this PR modifies the behaviour of CSRF tokens in this application. Our team will take a look soon, but for now please consider what the best CSRF behaviour for your application is. If the controller in question is meant to be used mostly as an API by non-browser clients, a sane option is protect_from_forgery with: :null_session (since APIs don't usually send CSRF tokens or use sessions anyway). If this endpoint is interacted with from a browser (via a form POST or similar), then it is good to use the stricter protect_from_forgery with: :exception. If you'd like to read more about Rails CSRF protection, there's some great Rails documentation on it: https://guides.rubyonrails.org/security.html#csrf-countermeasures.

Can we get the Rails dev you were going to pair with, or Rafael to provide a second  👀, please?  This is a great opportunity to get cross-Kernel feedback 😺


Add array of submenu interfaces

Add array to show menu in pages edit of assign's interfaces submenu

The edit screens, as a general standard, don't have tabs of their parent screens. To retain consistency across them, we'll leave that as-is.

Looks like interfaces_groups_edit.php still have it, I'll remove to be consistent with others.


Python programiz in Python Language

Fixes Issue
Closes #612
Changes proposed
Add new resource in Python, Subcategory of "Languages".
Screenshots

Note to reviewers

Hey, please update title of your PR (ex. chore: added python programmiz in Python Languages). Also, read contributing guidelines for more information :)

@rupali-codes title updated.

thank you @CBID2!!

hey @CBID2 proofreading error fixed. Please merge the PR.


opt avoid print too much log when get partitions failed

If get partitions failed, there may be too much logs to print partition values.

run buildall


[Feature] Pre loader Page (preloading)

As this is an upcoming and editing website ,this would required more no of features , and when more no of feature comes loading time increases so adding a pre-loader page would improve user attraction and user engagement ....
It would be fair deal to add this feature.
If this feature is required do assign me under GSSOC 2023!

Caught a good point, i was thinking the same
Anyways let's go 🌟


fix: Ensure that getShortType regex wildcard is non-greedy

Hello!  First, let me thank you for writing this library!  Please enjoy a cup of coffee on me!
We use your library for a project at my company and it's made our lives a lot easier!  We've been using v0.5.3 for a while, but as part of another effort, I'm updating to v1.4.1.  I noticed that some of our OAPI documents are tripping up the react query codegen and wanted to investigate.
I forked your repo and built it locally (which btw required some liberal use of any casting to get the project to build on my M3 mac--node 20, TS 5.5.x--but I removed all of those before committing my fix).  I threw in some console.logs in createUseMutation, and in the methodParameters section, refParam.type.getText(param) was returning something  in the following shape (paths, param names and type names edited, of course):
'{ type1?: import("/path/to/project/requests/types.gen").Type1; type2: import("/path/to/project/requests/types.gen").Type2; type3: import("/path/to/project/types.gen").Type3; }'

This was producing a mutation type signature that looked like this:
export const useDefaultServiceMyEndpoint = <
  TData = Common.DefaultServiceMyEndpointMutationResult,
  TError = unknown,
  TContext = unknown,
>(
  options?: Omit<
    UseMutationOptions<
      TData,
      TError,
      {
        companyId: number
        requestBody: {
          type1?: Type3
        }
      },
      TContext
    >,
    'mutationFn'
  >,
) => ...

As you can see, it's setting type1's type to Type3, which is incorrect.  I discovered that the wildcard in getShortType was greedy, and that making it non-greedy would indeed fix the problem.  I included a test with data in the same shape as my case.
Barring any issues with the PR, it would be very helpful for us if we could get this releases ASAP.  Please let me know if there's anything further you need from me!

@7nohe @seriouslag this one should be pretty uncontroversial, haha.  Hope it helps!  Thanks again for the lib!


Create array of organizations

Please follow these steps to complete this task:-

Make a folder named utils inside the src directory.
Make a file named Orgs.store.js inside the utils folder.
In this file create array of organizations in the following format:-

const organizations = [
    {
        name: 'Mozilla',
        summary: 'Keeping the internet open and accesible to all'
    },
    {
         name: '...',
         summary: '...'
    },
    .
    .
]

Note: You can take the names and summary of the organizations from here - https://summerofcode.withgoogle.com/organizations/?sp-page=2 .
Please ensure that the organizations have their projects hosted on Github. This is because we will use the Github API to fetch the projects. You can check this by clicking on the organizations and look for their ideas.

Can i tame up the issue

I've done it you may check and let me know
#11


Replace SHA256 hash with Pedersen for commitments

Approximately 90% of the circuit constraints are taken up with SHA hashes.  We can reduce the proof size considerably if we replace SHA hashing, although we have to be careful that we don't increase Gas costs by so doing in cases where the SHA calculation also needs to be done on-chain (SHA being very Gas-efficient compared to most other hashes).
Commitment hashes are not used on-chain and thus replacing SHA with the more Snark-friendly Pedersen for commitments should be beneficial.  Pedersen is hiding and binding but not pseudorandom.  However, that is acceptable for this application.

This is no longer required because we use Poseidon hashes.


[CMake] Support code coverage analysis

This patch adds support to the build system to allow instrumenting the Swift compiler for measuring code coverage.
@gribozavr Please review this patch.

Is this for measuring coverage of the compiler’s source code, or of Swift code built with the compiler?

@dabrahams Measuring coverage of the compiler’s source code.

@gribozavr I've made the requested changes.


[darjeeling,dv] Fix xbar_main test failures

This should fix most of the problems that currently cause multiple of Darjeeling's xbar_main tests to fail. Please see the commit messages for details.

CHANGE AUTHORIZED: hw/ip/tlul/rtl/tlul_socket_1n.sv

CHANGE AUTHORIZED: hw/ip/tlul/rtl/tlul_socket_1n.sv

Thanks for fixing this, @andreaskurth!
Does it make sense to carry over the first commit to master?
Because it looks like this is something that might fail there as well...

Thanks for fixing this, @andreaskurth!
Does it make sense to carry over the first commit to master?
Because it looks like this is something that might fail there as well...

I agree; PR created: https://github.com/lowRISC/opentitan/pull/20647


Use of dataclasses to store blackjack games

Is your feature request related to a problem? Please describe.
Using a tuple to unpack data values seems quite counter-intuitive and creates more problems as opposed to solutions. So we're considering creating dataclass instances that hold a user's blackjack game metadata for as long as the game exists
Describe the solution you'd like
@dataclass(slots=True, repr=False)
class BlackjackGame:
    deck: list[int]
    player_hand: list[int]
    dealer_hand: list[int]
    player_hand_ui: list[str]
    dealer_hand_ui: list[str]
    bet: int

Fixed in https://github.com/SGA-A/c2c/commit/fc0bc33fddf424c96e8b0e435b7c407b01633e81


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Please do a new release

The last release is ~2 years old, and there are some interesting fixes in the git repo. Could you please do a new release ? (I could get the code from git, but I'd like to simply to pip install).

Which FOSS projects I have time to work on is currently dictated by what funding is available. I'll get back to it, but probably not for another few months at least.

Very surprising response. I'm sure you could find others (like myself) who would be willing to help with this...

I'd like to bump this. Please release or find help.

+1

+1 and also would be willing to help

+1, also willing to maintain.

+1. Need the ssl option

Can someone just fork it and incorporate all of the pull requests already out there?  I'd do it myself, but I'm not an expert on Github.  I don't particularly like the idea of taking over someone's project, but it doesn't look like we are going to get anything done on this anytime soon.


Move doc

Per Alex, move Advertise Kubernetes service IP addresses to /Configure networking in TOC

Merge to nightly

Deploy preview for calico ready!
Built with commit bd673db2275845b327f33925aea0fe44ae7582da
https://deploy-preview-3296--calico.netlify.com


feat(*): add amFromNow pipe to mimic moment().fromNow() behavior

Closes #45

@urish are there any changes required in order to have this one merged and released?

Thank you for your contribution!
Seems like it does exactly what the amTimeAgo pipe does, can you please explain the rationale behind this?

hm... the amTimeAgo pipe didn't look like the thing I needed, so I haven't even digged into it. My bad, will close this PR now, since, as you mentioned, this case is already handled. Do you mind closing #45 then ?

The bad thing with amTimeAgo though consists in its name - moment().from() can also report on future dates, like "in 6 months", and this pipe does not correctly represent such possibility

true, though - from what I have seen, it is a common practice on the web (e.g. even in github I sometimes see "in a few seconds" for comments that were just posted, and probably there is some time drift between client and server)


Expose primary handles

These will be useful later.

The idea is to be able to wait on the handles (Marc seems to have issues with main exiting too early when running the memory profiler)


"Cannot allocate memory" error

Hi
I'm on debian, xfce.
lillo@MBPDebian:~$ ddcutil detect --verbose
Output level:               Verbose
Reporting DDC data errors:  false
Trace groups active:        none
Traced functions:           none
Traced files:               none
Force I2C slave address:    false
User defined features:      disabled

Performance and Retry Options:
   Deferred sleep enabled:                      false
   Sleep suppression (reduced sleeps) enabled:  false
   Dynamic sleep adjustment enabled:            false

No displays found
lillo@MBPDebian:~$ echo "SUBSYSTEM==\"i2c-dev\", GROUP=\"root\", MODE=\"0660\"" | sudo tee /etc/udev/rules.d/50-i2c.rules
SUBSYSTEM=="i2c-dev", GROUP="your-group-here", MODE="0660"
lillo@MBPDebian:~$ sudo udevadm trigger
Failed to write 'change' to '/sys/devices/virtual/input/input18/uevent': Cannot allocate memory
lillo@MBPDebian:~$

Might be this udev/kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=207695

Thanks!
I do not understand how to implement that patch. What should I do in order to make it work? :) (sorry for being a noob)

Do you happen to have the ckb-next-daemon daemon running?

How do I check is running?

sudo ddcutil detect --verbose

Output level:               Verbose
Reporting DDC data errors:  false
Trace groups active:        none
Traced functions:           none
Traced files:               none
Force I2C slave address:    false
User defined features:      disabled
Performance and Retry Options:
Deferred sleep enabled:                      false
Sleep suppression (reduced sleeps) enabled:  false
Dynamic sleep adjustment enabled:            false
No displays found

What's the output of sudo ddcutil environment?


fix(mempool): pre-allocate capacity for the db key

Fixes #881
Summary

Categories: protocol-units.

The amount allocated was not enough, wasting a re-allocation.
Testing
Existing tests should pass.

The failing check is #866.

Superseded by #902.


fix(rpc): commit tx state changes when tracing block

when tracing an entire block, transaction by transaction we need to commit changes which we didn't do

Codecov Report

Merging #2605 (18bec56) into main (7ca8a29) will decrease coverage by 55.49%.
The diff coverage is 0.00%.

:exclamation: Current head 18bec56 differs from pull request most recent head 67e1151. Consider uploading reports for the commit 67e1151 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##             main    #2605       +/-   ##
===========================================
- Coverage   71.38%   15.90%   -55.49%
===========================================
  Files         496      496
  Lines       62551    62562       +11
===========================================
- Hits        44651     9949    -34702
- Misses      17900    52613    +34713

Flag
Coverage Δ

integration-tests
15.90% <0.00%> (-1.99%)
:arrow_down:

unit-tests
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crates/rpc/rpc/src/debug.rs
16.59% <0.00%> (-0.44%)
:arrow_down:

crates/rpc/rpc/src/trace.rs
0.00% <0.00%> (-47.00%)
:arrow_down:

... and 366 files with indirect coverage changes


Error on training: stack expects a non-empty TensorList

Hello,
I am trying to reproduce the results on Google Collab. I followed the instructions, but maybe I have mistaken something:
I have all the needed files on a Google Drive and, therefore, the datasets structure looks like this: VKD-master/datasets/mars and there are 3 folders (info, bbox_train, bbox_test).
However,  when I start running the training command, I get the following error:
"RuntimeError: stack expects a non-empty TensorList"
I have attached a file of the entire log. Also, when I tried on the pre-trained model, the same error occurred.
Any change I do, brings me back to this same error. Please, guide me towards a solution. Any idea is welcomed.
Thank you,
Anca

I guess that it's a problem due to wrong paths. The code assumes that the datasets' tree is placed in the current working directory. Therefore, please check if VKD-master is being set as your current working directory within the notebook environment.

I have configured the absolute path in the colab notebook enviroment. Also, to be sure, I have added the path in every .py file (attached a photo). Still, when hitting the train command I get the same error. This is the link from the notebook env.:
https://colab.research.google.com/drive/1sPZJIyUXNiFfzdzSkgltY4OvrgE7BOY-?usp=sharing
I have added there a "tree" command so you can visualize how the project structure looks like, but I skipped the bbox_train/bbox_test directories because of their large files. However, the folders are where specified, under the /datasets/mars directory. Could you please have a look? Maybe you notice something. I really do not know what else to change.
Many Thanks!

Thank you for checking my code. I do really appreciate it! Unfortunately, I tried with your suggestion and I am still having the same error. I tried with the previous version of code (original code) and printed the conf.nas_path and it is: /content/drive/My Drive/Licenta/VKD/datasets (attached photo).
I also took the installations again one by one with all the prerequisites (I think in the beginning I was not having the right version of conda). Do you know, what else could be checked...?
Thank you, again!

Ok, please email me at<EMAIL_ADDRESS>and let's solve the issue together.


I would like to get instructions on what parameters need changing (account settings) to run the white label api from github

(Srastos_masrer)? Do we need to change the gem file parameters? We attempted to run the github download on IBM Bluemix using Rubyand encounter this error (
FAILED
Server error, status code: 400, error code: 170004, message: App staging failed in the buildpack compile phase)

When attempting to run from web hosting we get this:
Ruby on Rails
Start a Ruby Application
The system could not start the Ruby on Rails application.
NOTE: Gem::SourceIndex.from_installed_gems is deprecated with no replacement. It will be removed on or after 2011-10-01. Gem::SourceIndex.from_installed_gems called from /usr/lib/ruby/gems/1.8/gems/gem_plugin-0.2.3/lib/gem_plugin.rb:109. NOTE: from_installed_gems(arg) is deprecated. From /usr/lib/ruby/site_ruby/1.8/rubygems/deprecate.rb:63:in `send' NOTE: Gem::SourceIndex.from_gems_in is deprecated with no replacement. It will be removed on or after 2011-10-01. Gem::SourceIndex.from_gems_in

Hi @lsdace30095 we are currently under development as you can check under https://github.com/softlayer/stratos/issues/1
I've been working on stratos and a new client for SoftLayer, so you can expect something new next month.
Thank you


can`t connect tlsv1.2

Hi , TakahikoKawasaki . Do you know how to connect tlsv1.2 server on android？I tried to connect SSLv3 and TLSv1 successfully。I have said that since API 9 ,some protocols were supported . Besides that , since API 16 , TLSV1.1 and TLSV1.2 are also supported on android . But I can not do it . I`m looking forward that to you can help me to solve it !
Here is my code:
public SSLContext getSSLContextOld(String imUrl) throws KeyStoreException,
		NoSuchAlgorithmException, CertificateException, IOException,
		KeyManagementException {
	KeyStore keyStore = KeyStore.getInstance("BKS");
	keyStore.load(getInputStream(imUrl), "000000".toCharArray());
	// TrustManager decides which certificate authorities to use.
	TrustManagerFactory trustManagerFactory = TrustManagerFactory
			.getInstance(TrustManagerFactory.getDefaultAlgorithm());
	trustManagerFactory.init(keyStore);
	// Since API 9,the following protocols have been
	// supported:Default,SSL,SSLv3,TLS,TLSv1
	SSLContext sslContext = SSLContext.getInstance("TLSv1.2");
	Log.e(TAG, "protocol-->" + sslContext.getProtocol());
	sslContext.init(null, trustManagerFactory.getTrustManagers(), null);
	return sslContext;
}

public void initWs(String imAddress, String encoderToken)
		throws IOException, WebSocketException, URISyntaxException,
		NoSuchAlgorithmException, KeyStoreException, CertificateException,
		KeyManagementException, UnrecoverableKeyException {
	// "wss://domain:port/im"
	String imUrl = imAddress + "?token=" + encoderToken;
	WebSocketFactory webSocketFactory = new WebSocketFactory();
	SSLContext sslContext = getSSLContextOld(imUrl);
	// webSocketFactory.setSSLContext(sslContext);// method 1
	SSLSocketFactory factory = (SSLSocketFactory) sslContext
			.getSocketFactory();//method 2
	webSocketFactory.setSSLSocketFactory(factory);
	webSocket = webSocketFactory
			.setConnectionTimeout(WEBSOCKET_CONNECT_TIME_OUT)
			.createSocket(imUrl).setPingInterval(PING_PONG_INTERVAL)
			// .setPongInterval(PING_PONG_INTERVAL)
			.addListener(webSocketAdapter);
	webSocket.connect();

}

Read this answer in StackOverflow. Below is an excerpt from the answer.

The Android API docs [correctly state](http://developer.android.com/reference/javax/net/ssl/SSLEngine.html) that TLSv1.2 is only supported for SSLEngine in API Level 20 or later (Lollipop) while SSLSocket supports it since level 16.

Ask your question at StackOverflow.


4chan (is2.4chan.org) issues

Operating system / операционная система
Windows 10 22H2
Running as service / Запуск программы как сервис
I run it as a regular program / Запускаю программу обычным образом
Describe the bug / Опишите ошибку программы
4chan.org works perfectly, but whenever I try to click a image to get it bigger, it doesn't work. I discovered that it only happens with pics linked with is2.4chan.org, which is a site for holding images i guess. It works when i right click the pic and open it in a new tab which directs me to i.4cdn.org (but it's the compressed version of the pic). same with videos. other than that specific site everything works flawlessly with goodbyedpi.
Additional information / Дополнительная информация
-changing browsers or turning off kyber didnt do anything
-I was using an older version of goodbyedpi with gui it got working after 5-10 clicks or reloads on that specific site. then changed to latest build (22), worked good for 1-2 months now it doesn't open any images or videos at all.
there is certainly some pattern here but i can't see it. anyone experiencing the same issue or manage to fix it?

I checked edge, and it works after few tries. still curious about what causes this though

Yep, i got the same problem with 4chan recently. Don't know how to solve this yet though.

This doesn't seem like a bug report for me. If you have any other information, feel free to add it.

Yep, i got the same problem with 4chan recently. Don't know how to solve this yet though.

I tweaked the fragment values yesterday. It started working stably after increasing the values to 10 from 2, for both HTTP and HTTPS. Though 10 is way too much, I guess; Chrome wasn't very stable with 5, so trying a middle ground could help maybe. I don't know how much these values would affect CPU usage and speed in general. I'm not very savvy about all this, so extra info from a more knowledgeable person would be nice. Also, it's compatibility changes on different browsers as well. Edge and Firefox needed less fragmentation to get the site working compared to Chrome, but it's probably a personal thing; I can't assure it would be the same for everyone else. Changing to other modesets didn't help either.
Another thing I tried is adding the IP ID of is2.4chan.org to .exe using the --ip-id parameter. I wasn't expecting it to work since the IPs of every image/video link should be different from each other, but surprisingly, it worked, at least for a while. Then back to normal, I don't know what happened there. If you wanna try out yourself the IP IDs of is2.4chan.org are:
--ip-id <IP_ADDRESS> --ip-id <IP_ADDRESS> --ip-id <IP_ADDRESS> --ip-id <IP_ADDRESS>
What boggles my mind is what causes it to stop working after working perfectly fine for 1-2 months. The same happened when using older versions as well.


101-vm-linux-create Template has CentOS 7.3 but the latest ISO is 7.2

In the parameters file:
https://github.com/Azure/AzureStack-QuickStart-Templates/blob/master/101-vm-linux-create/centos.7.3.azuredeploy.parameters.json

the SKU is 7.3 but the latest CentOS ISO located here (from docs link):
http://olstacks.cloudapp.net/latest/

is 7.2

@deathly809 , submit a PR please.


kube-aws: Fix two bugs with subnets & existing VPCs

Bug #1: Before this patch, when specifying a route table ID in the
cluster.yml file, the substitution on line 618 fails because the
RouteTableID is not available in that scope. This patch modifies the
substitution to read from the correct scope.
Bug #2: Before this patch, the validation code that is run during
'kube-aws up' expects c.InstanceCIDR to be a valid CIDR even when
the Subnets parameter is set instead. This patch modifies the validation
to avoid raising errors in this case.

I'm not at all sure that this is the best way to solve these issues, but they worked for my local testing and I figured I'd pass them along. In particular, I think the check that I'm modifying in  multi-node/aws/pkg/config/config.go may actually be redundant and can just be deleted.

As the author of the PR and commits introduced these bugs, LGTM, and thanks @michaeldiscala !
Personally, I'd like these cases to be tested in TestMultipleSubnets in config_test.go.
Forwarding further review to @colhom as I'm not an owner of this repository 🙇

@michaeldiscala could you back out your fix for bug #2 (subnets/existingVPC). The first patch is LGTM, the second is unfortunately going to require some additional finagling to validate all subnets against the VPC instead of just one.

@michaeldiscala thanks for reporting not one, but two show-stopping bugs! I've got your first fix up in #514, so I'm going to close this one out.


Add a specific bounds check.

I spent bunch of time on this one -- subspan throws an exception which is translated into IndexError in Python without a stacktrace, making it difficult to locate the source of problem. By duplicating this boundary check it is easier to track down future bugs.

One travis test did not pass through because of network timeout on the server, not sure if I can restart the check (without a new commit).


[PDI-16819]-Copying a Timestamp to result cannot be de-serialized whe…

…n running on Slave Server

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -Dsurefire.runOrder=alphabetical -B -fn -f 'pom.xml' -pl 'core' -P '!assemblies' -amd clean install && mvn -B -f 'pom.xml' -pl 'core' -P '!assemblies' -amd site

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  core/src/main/java/org/pentaho/di/core/row/RowMeta.java
  core/src/main/java/org/pentaho/di/core/row/value/ValueMetaBase.java
  core/src/main/java/org/pentaho/di/core/row/value/ValueMetaFactory.java
  core/src/main/java/org/pentaho/di/core/xml/XMLHandler.java
  core/src/test/java/org/pentaho/di/core/row/RowMetaTest.java
  core/src/test/java/org/pentaho/di/core/row/value/ValueMetaBaseTest.java
  core/src/test/resources/org/pentaho/di/core/row/rowMetaNode.xml

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: <0.1% (click to expand)
org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change: -0.4% :small_red_triangle_down:
Complexity Change: -0.5% :small_red_triangle_down:

org.pentaho.di.job.entries.getpop.MailConnectionMeta

Branch Change: -1% :small_red_triangle_down:
Complexity Change: -1.5% :small_red_triangle_down:
Instruction Change: -0.3% :small_red_triangle_down:

org.pentaho.di.job.entries.sql.JobEntrySQL

Instruction Change: -3.3% :small_red_triangle_down:
Line Change: -3.9% :small_red_triangle_down:

org.pentaho.di.trans.step.StepMeta

Branch Change: -0.7% :small_red_triangle_down:
Complexity Change: -0.6% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:
Line Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.checksum.CheckSumMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Method Change: -1% :small_red_triangle_down:

org.pentaho.di.trans.steps.insertupdate.InsertUpdateMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change: -1.2% :small_red_triangle_down:
Complexity Change: -1.3% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.5% :small_red_triangle_down:

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.sort.SortRowsMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.webservices.WebServiceMeta

Branch Change: -1.7% :small_red_triangle_down:
Complexity Change: -1.2% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.www.TransformationMap

Branch Change: -9.1% :small_red_triangle_down:
Complexity Change: -6.2% :small_red_triangle_down:
Instruction Change: -10% :small_red_triangle_down:
Line Change: -10% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceupsert.SalesforceUpsertMeta

Instruction Change: -0.1% :small_red_triangle_down:

@pamval , @mbatchelor Could you please take a look?


expecting binary predicted output but getting greyscale

Hello, I have a small issue with the code, I have used binary masks and greyscale input image, and I am expecting a binary predicted image but always get greyscale. Therefore it is hard to compare the ground truth and prediction images in matlab etc.
In the predicted images in this code that use membrane data it looks more binary so I'm wondering if anything else needs to be done.
Many thanks in advance
H

Predicted images in this code that use membrane data are also grey images.
The testGenerator function in your data.py,
replace "img = img/255" into" img = img/255.".
This will give you binary images instead of grey images.

Predicted images in this code that use membrane data are also grey images.
The testGenerator function in your data.py,
replace "img = img/255" with" img = img/255.".
This will give you binary images instead of grey images.

Hey @teamo429,
That fix does not work and still leads with gray/black predictions

Here is another solution,
def saveResult(save_path,npyfile,flag_multi_class = False,num_class = 2):
for i,item in enumerate(npyfile):
if flag_multi_class:
img = labelVisualize(num_class,COLOR_DICT,item)
else:
img=item[:,:,0]
print(np.max(img),np.min(img))
img[img>0.5]=1
img[img<=0.5]=0
print(np.max(img),np.min(img))
io.imsave(os.path.join(save_path,"%d_predict.png"%i),img)
You can adjust the threshold(0.5).

Here is another solution,
def saveResult(save_path,npyfile,flag_multi_class = False,num_class = 2):     for i,item in enumerate(npyfile):         if flag_multi_class:             img = labelVisualize(num_class,COLOR_DICT,item)         else:             img=item[:,:,0]             print(np.max(img),np.min(img))             img[img>0.5]=1             img[img<=0.5]=0             print(np.max(img),np.min(img))             io.imsave(os.path.join(save_path,"%d_predict.png"%i),img)
You can adjust the threshold(0.5).

In a separate post, increasing epochs and reducing steps per epochs was suggested, but that did not help for me.

Has someone come up with an alternative solution? Something wrong in the output script besides replacing img = img/255 with img = img/255. ?


Update "Team sharing" in Assistant builder

As per here and here
(2 modes depending on role builder or member)
Full figma (source of truth)
Full issue

Depends on #3270

Related to #3272


Changed spelling of Extreme IO to XtremIO

I like your change but the pull request has this flag: "This branch is out-of-date with the base branch"
which prevents a merge
I believe one solution may be to rebase the "Array-naming" feature branch this came from.
Another might be to do the change in the master branch and submit the pull from there.
I am not a git guru so there may be other, better solutions as well.

Will give it a try - I'm relatively new to Git as well.

rebase worked, merged


panic while typing in the input box

Getting random panics while typing, mostly when using backspace:
panic: runtime error: slice bounds out of range
goroutine 19 [running]:
github.com/erroneousboat/slack-term/vendor/github.com/nsf/termbox-go.PollEvent(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
	/home/kalbasit/code/profiles/opensource/src/github.com/erroneousboat/slack-term/vendor/github.com/nsf/termbox-go/api.go:330 +0x44f
github.com/erroneousboat/slack-term/handlers.eventHandler.func1(0xc420433600)
	/home/kalbasit/code/profiles/opensource/src/github.com/erroneousboat/slack-term/handlers/event.go:50 +0x30
created by github.com/erroneousboat/slack-term/handlers.eventHandler
	/home/kalbasit/code/profiles/opensource/src/github.com/erroneousboat/slack-term/handlers/event.go:52 +0x3f

Just to be sure, you are using version 0.2.2?
slack-term -h

@erroneousboat that's correct.

Ok, I'm trying to exclude things here, because I'm not able to trigger it myself. Are you also able to trigger it when using the binary? I'm asking this, because from the stacktrace it seems you've installed it by go get. It could be happening because of a local version of termbox, but I'm not sure.
I've also made some changes to the code that might help, you can try it out by checking out the branch v02.3-termbox_events and see if you're able to trigger it there.

@erroneousboat my apologies for not being clear, had a busy week. I did build it myself, but I did so on the branch for https://github.com/erroneousboat/slack-term/pull/57 which in turn uses nlopes/slack at https://github.com/nlopes/slack/pull/176. Can you try the branch from my PR and update slack's branch as well. I'll give your branch a shot.

No problem at all, we all do this in our free time :) I'll try what you suggested and see if I'm able to trigger it. Thanks!

With version v0.2.3 I'm still able to trigger it when scrolling in de editbox

Closing this issue for now, it doesn't seem to be happening anymore. Will re-open it when it does.


Time-series MTL

Hi,
First of all, this is a fantastic library! Amazing work.
My question: can LibMTL can be used in time-series applications? I.e. do we only need to provide encoder/decoder architectures such as LSTMs? Would the loss-weighting methods need to be extended in any way?
I'm fairly new to MTL, so pardon the naive question.
Thanks,
Madhu

Yes, you just need to provide appropriate encoder/decoder architectures to LibMTL according to your problem.

Sounds good, thanks!


How to reload a generated CRUD into the Visual builder?

Hello,
I could not find a forum where I could ask questions so I came here.
I just downloaded your latest version and was trying the Visual builder(generator).
It looks good but I just created a table and made a mistake(forgot 2 fields), How to reload the crud fields into the generator please?
Thank you.

@FreddyCrugger You can use Rollback Command for rollback all generated files and generate new crud.
rollback docs: https://labs.infyom.com/laravelgenerator/docs/6.0/generator-commands#rollback


fails to minify

I added your package to my React app and now I'm unable to compile my production build because of the following error.
Failed to minify the code from this file:

 	./node_modules/abort-controller/dist/abort-controller.mjs:20

We're experiencing the same issue with older UglifyJS.

I am having the same issue create-react-app

has anyone found a fix for this?

我也遇到这个问题暂时找不到解决方案


Tag TuringModels v1.0.0 - added upper bounds and CompatHelper

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/5395
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" c1f75af8eebcbc1562ac4fd9fb20838a41c27d00
git push origin v1.0.0


Support error message verification in Fourslash

Currently, we can only verify number of errors and position of errors through marker. However, in some scenarios, ability to verify correctness of diagnostic messages and their arguments can be useful.

What do we want to specifically track here? What extra information would this give us?

@RyanCavanaugh this can probably be closed since verify.errorExistsAtRange accepts code and message

I think we also have baselining for diagnostics.


Can [Feature Request] el-form form form validation be performed after the validateField validate method is executed

Existing Component
是
Component Name
el-form
Description
el-form 表单验证可不可以在执行validateField validate 方法之后再执行验证

Please provide a demo link.

Please provide a demo link.

thanks . is solved


SDXL-LoRA-PPS TypeError: upld() missing 1 required positional argument: 'ren'

The lora encoder has been working great the last few days. Just updated it and getting this message when running the Instance_Images cell.
File /notebooks/sdxllorapps.py:443, in uplder(Remove_existing_instance_images, Crop_images, Crop_size, IMAGES_FOLDER_OPTIONAL, INSTANCE_DIR, CAPTIONS_DIR)
441   display(uploader, Upload, out)
442 else:
--> 443    upld(Remove_existing_instance_images, Crop_images, Crop_size, IMAGES_FOLDER_OPTIONAL, INSTANCE_DIR, CAPTIONS_DIR, uploader)
444    done()
TypeError: upld() missing 1 required positional argument: 'ren'
Any idea how to solve?
Cheers

run the first cell again, it's fixed

awesome. thanks for the super quick fix


Transfer learning

Done

config: add param retrain_model --> null if training from scratch, path/to/pretrained-model otherwise
ivadomed/main.py: load pre-trained model
ivadomed/main.py: freeze model weights
ivadomed/main.py: replace model.last_conv and model.last_film
ivadomed/main.py: filter out the params you want to fine-tune and send the remaining to the optimiser
testing/test_transferLearning.py

>>> from testing.test_transfer_learning import test_transfer_learning
>>> test_transfer_learning()
Using GPU number 1
Layers included in the optimisation:
	 decoder.last_conv.weight
	 decoder.last_conv.bias
1,147,009 total parameters.
577 training parameters.

To run the testing function with FiLM:
test_transfer_learning(film_layers=[0,0,0,0,0,0,0,1], path_model='log_film/best_model.pt')

Apparently testing_data/model_unet_test.pt is missing. I'll uppload one.

Test failed when loading the model on cpu. Same problem with PR #114. working on it

Looks good to me! Thx @charleygros

Thanks for review
Let's wait for #114 merge :-)

Great! Added retrain_model to the config description in the wiki


Brief summary of what is missing or incorrect

Description
Mysql is also supported in Gcloud IAM database authentication. So -enable_iam_login flag should work with it and I have tested it does work.
Solution
Update the Note in readme to show Mysql is also supported.

Hi @bilalahmad99. Thanks for opening this issue. See https://github.com/GoogleCloudPlatform/cloudsql-proxy/pull/865#issuecomment-892798794 for context. In short, MySQL is only supported for manual IAM DB Authentication, not automatic. Rest assured when automatic IAM DB Authn is available, we'll make sure it's clear in the README.


chore: declarationMap

This PR adds the property declarationMap to the build-tsconfig of the packages.
This enables VSCode to jump to the actual source files instead of the compiled declaration files. This increases productivity by at least 2.3%.
Status

[x] Code documentation for the relevant parts in the code have been added/updated by the PR author
[x] The functionality has been tested by the PR author
[ ] The functionality has been tested by NRK

I think this is a good idea.
It would be better to enable it https://github.com/nrkno/tv-automation-sofie-code-standard-preset/blob/master/ts/tsconfig.lib.json instead, so that we get this for all of our libraries.
The only negative is see here is the increase in npm package size (340k vs 252k), but I dont think that matters

Good point! We could also look into ignoring those files when publishing the npm-package. I suppose if the original source isn't included in the npm-package anyway, it won't make sense to include any map files either.

I've pushed the change to https://github.com/nrkno/tv-automation-sofie-code-standard-preset/blob/master/ts/tsconfig.lib.json


iOS - Allow user to recover when Bluetooth permission is denied

TODO

When Bluetooth permission is denied, the user should be shown a text about the missing permission.
Provide a way to enable Bluetooth permission again
Once the permission is provided, the user should be able to move to next state

@Alka1703 will be looking into this.

Dhivya is looking into this.

Kindly provide the error message text regarding the bluetooth permission and action button text.
@nayakrounak

Hi @dhivya0413 , Please find the messages below:

Bluetooth Permission not available: "Please enable bluetooth permissions to support local sharing"
Bluetooth is turned off: "Please turn on bluetooth to support local sharing."
Action Button: "Allow Bluetooth Permissions"

As per @krishnakumar4a4  the behaviour/ changes are  only applicable in iOS platform


cert-manager failing to generate certificate in kubernetes, how to fix that?

In the aks cluster, the helm chart I installed:
And the ingress chart I used
helm repo add jetstack https://charts.jetstack.io

helm repo update

helm upgrade --install \
cert-manager jetstack/cert-manager \
--namespace cert-manager \
--set ingressShim.defaultIssuerName=letsencrypt-prod \
--set ingressShim.defaultIssuerKind=ClusterIssuer \
--set ingressShim.defaultIssuerGroup=cert-manager.io \
--set installCRDs=true \
--version v1.8.2

The issuer I applied.
The deployment,service,ingress,issuer mentioned in below file.

apiVersion: cert-manager.io/v1
kind: Issuer
metadata:
  name: letsencrypt-prod
  namespace: cert-manager
spec:
  acme:
    server: https://acme-v02.api.letsencrypt.org/directory
    email<EMAIL_ADDRESS>    privateKeySecretRef:
      name: letsencrypt-staging
    solvers:
      - http01:
          ingress:
            class: nginx
---
apiVersion: v1
kind: Namespace
metadata:
  name: testapp

---
apiVersion: v1
kind: Service
metadata:
  name: testapp-svc
  namespace: testapp
spec:
  ports:
    - port: 80
      targetPort: 80
  selector:
    app: testapp
  type: ClusterIP
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: testapp-ingress
  namespace: testapp
  annotations:
    kubernetes.io/ingress.class: nginx
    cert-manager.io/cluster-issuer: cert-manager/letsencrypt-prod
spec:
  tls:
    - hosts:
        - testing123.mycompany.com # Replace with your own domain
      secretName: testing123-tls
  rules:
    - host: testing123.mycompany.com
      http:
        paths:
          - pathType: Prefix
            backend:
              service:
                name: testapp-svc
                port:
                  number: 80
            path: /
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: testapp
  namespace: testapp
spec:
  replicas: 2
  selector:
    matchLabels:
      app: testapp
  template:
    metadata:
      labels:
        app: testapp
    spec:
      containers:
        - name: testapp
          image: nginx
          ports:
            - containerPort: 80

When I checked the cert-manager pod, it is showing errors as below.

I0320 08:54:48.550515       1 start.go:75] cert-manager "msg"="starting controller"  "git-commit"="f1943433be7056804e4f628ff0d6685a132c407b" "version"="v1.8.2"
I0320 08:54:48.550568       1 controller.go:242] cert-manager/controller/build-context "msg"="configured acme dns01 nameservers" "nameservers"=["<IP_ADDRESS>:53"]
W0320 08:54:48.550617       1 client_config.go:617] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0320 08:54:48.551297       1 controller.go:70] cert-manager/controller "msg"="enabled controllers: [certificaterequests-approver certificaterequests-issuer-acme certificaterequests-issuer-ca certificaterequests-issuer-selfsigned certificaterequests-issuer-vault certificaterequests-issuer-venafi certificates-issuing certificates-key-manager certificates-metrics certificates-readiness certificates-request-manager certificates-revision-manager certificates-trigger challenges clusterissuers ingress-shim issuers orders]"
I0320 08:54:48.554022       1 controller.go:134] cert-manager/controller "msg"="starting leader election"
I0320 08:54:48.554340       1 leaderelection.go:248] attempting to acquire leader lease kube-system/cert-manager-controller...
I0320 08:54:48.554744       1 controller.go:91] cert-manager/controller "msg"="starting metrics server"  "address"={"IP":"::","Port":9402,"Zone":""}
I0320 08:54:48.598517       1 leaderelection.go:258] successfully acquired lease kube-system/cert-manager-controller
I0320 08:54:48.601483       1 controller.go:182] cert-manager/controller "msg"="not starting controller as it's disabled" "controller"="certificatesigningrequests-issuer-acme"
I0320 08:54:48.601632       1 controller.go:182] cert-manager/controller "msg"="not starting controller as it's disabled" "controller"="certificatesigningrequests-issuer-ca"
I0320 08:54:48.601714       1 controller.go:182] cert-manager/controller "msg"="not starting controller as it's disabled" "controller"="certificatesigningrequests-issuer-vault"
I0320 08:54:48.601800       1 controller.go:182] cert-manager/controller "msg"="not starting controller as it's disabled" "controller"="certificatesigningrequests-issuer-venafi"
I0320 08:54:48.606344       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificates-request-manager"
I0320 08:54:48.606517       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificates-issuing"
I0320 08:54:48.606810       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificates-metrics"
I0320 08:54:48.612522       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificaterequests-issuer-acme"
I0320 08:54:48.612575       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificaterequests-issuer-ca"
I0320 08:54:48.612665       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificaterequests-issuer-vault"
I0320 08:54:48.612979       1 controller.go:182] cert-manager/controller "msg"="not starting controller as it's disabled" "controller"="certificatesigningrequests-issuer-selfsigned"
I0320 08:54:48.613867       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificaterequests-approver"
I0320 08:54:48.614531       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificaterequests-issuer-venafi"
I0320 08:54:48.615125       1 controller.go:205] cert-manager/controller "msg"="starting controller" "controller"="certificates-revision-manager"

Your Ingress resource has a cert-manager.io/cluster-issuer annotation and you have configured cert-manager with --set ingressShim.defaultIssuerKind=ClusterIssuer , but you are actually creating an Issuer not a ClusterIssuer.
https://cert-manager.io/docs/configuration/