Length indicator must be non-negative.: TryFromIntError()

Hi, I am using arrow-odbc-py with db2. I have a table that has column zip that is VARCHAR(16). I am using this code to run it:
    result = read_arrow_batches_from_odbc(
        query=sql,
        connection_string=conn,
        batch_size=batch_size,
        max_text_size=4000,
    )

And I am getting this error:

Seems the problem is when the column contains null values.
Any idea, how can I deal with it? Thanks a lot!

@tomsej Thanks for reporting the issue.

Note to self: https://github.com/pacman82/odbc-api/blob/a45b2023d14d2cdcdc632c3a7e80207266bea659/odbc-api/src/buffers/indicator.rs#L15C1-L29C1

Link to issue about erroneous indicators reported by db2 driver: https://github.com/pacman82/odbc-api/issues/398

Hi @tomsej , this is a symptom of a known (to me) bug of the db2 ODBC driver. This bug is really serious as reporting basically random memory garbage as string length indicators can have all kinds of side effects for data integrity and security. I tried to report that bug. Yet I am a maintainer of an Open Source artifact, not a paying customer of IBM. If there is a process for me to tell them about an error in their ODBC driver, I did not find it. I even created an IBM account, but in the end I always hit some kind of red tape. After spending almost an entire Saturday on this I gave up.
If you would be able to open a Bug report with them, I am willing to help and precisely what part of the ODBC spec they are violating.
In two sentences: They must not assume that an application relies on terminating zeroes to determine string lengths. If an indicator buffer is bound to a column, after a bulk fetch the values within it must be either -1 to indicate a NULL or be the length of the string without the terminating zero.

Seems the problem is when the column contains null values.

This is an interesting observation. I am curious. Does this error only occur if the Schema allows for NULL, or must there be actual NULL values in the fields.
There would be ways to work around this problem which could do the right thing most of the time. However I suspect sometimes they would silently loose data. I maybe wrong about this, but at the moment I am afraid to publish a "fix" which might harm someones data integrity. A fix by IBM is IMHO by far the best solution.
Best, Markus

Hello @tomsej ,
arrow-odbc 2.0.3 is released. It contains a workaround for IBM DB2. I could not test it against this database, so please tell me if this works.
Best, Markus

Thanks a 💯 @pacman82 for working during the weekend!!!  Therefore, I don't anticipate any significant changes happening in the near future. Even if we would able to fill the bug report 😢
The workaround you have deployed is way better than previous version, but there is an issue when you have a column that is mandatory (schema does not allow Nulls) and value is empty string. Than I get a error (column name is STRING):
thread '<unnamed>' panicked at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/arrow-odbc-4.1.0/src/reader/to_record_batch.rs:103:85:
called `Result::unwrap()` on an `Err` value: InvalidArgumentError("Column 'STRING' is declared as non-nullable but contains null values")

That is something I am able to live with, since I can write a condition like case when string = '' then ' ' else string.
Once again, I deeply appreciate your efforts. Thank you very much for what you are doing!

Thank you @tomsej ! Weird as it may sound, I find contributing to Open Source is a relaxin spare time activity. At least ever since Conway's law forced me into management. It is extra rewarding if the work is appreciated, though.
To the issue at hand. The indicators (i.e. the thing which is garbage memory in the db2 driver) is not only responsible for reporting string lengths, but is supposed to be -1 for NULL strings.  My not so well thought out workaround, had been to simply treat empty strings as NULL.
I never did test with a mandatory schema though. I wonder if a better workaround would be, to never return NULL but to just always return the string, which may be empty. Rational: Due to the invalid indicator buffer empty string and NULL are indistiguishable for the application. At least the empty string representation can be consistentently applied.
Of course depending on the situation you would need to map empty string to NULL in application code.

Hey @tomsej, I noticed something from your prior issue that you were using libdb2.so as your driver:
[DB2 Driver]
Description = DB2 Driver
Driver      = /var/lang/lib/python3.10/site-packages/clidriver/lib/libdb2.so
FileUsage   = 1
DontDLClose = 1

However, you may want to use libdb2o.so instead as noted by this documentation. I've noticed issues before using the libdb2.so driver and IBM's documentation states that it is used for the 32-bit ODBC Driver Manager as well as the 32-bit and 64-bit CLI application. The libdb2o.so library on the otherhand, is for the 64-bit ODBC Driver Manager.
The change to the odbcinst.ini file should be pretty straightforward, but unfortunately the libdb2o.so file is located behind one of IBM's login walls unlike the libdb2.so file.

Also, arrow-odbc 2.0.4 has been released. It no longer maps empty strings to NULl

@tomsej super interesting...
Where did you download the libdb2o.so driver? The packages provided here only provide libdb2.so?

@tomsej @keraion super interesting...
Where did you download the libdb2o.so driver? The packages provided here only provide libdb2.so?

@rupurt they are behind a login on Fix Central, but this should get you about 90% there.
I'd suggest selecting the "odbc_cli" version (e.g. DSClients-linuxx64-odbc_cli-<IP_ADDRESS>-FP000) for your platform, version, and fix pack.

 I'm from Australia and for some reason can't download anything from there because it says it's against US export restrictions.

Managed to grab libdb2o.so.
I'm still running into the non-nullable column error on arrow-odbc 2.1.4 and the latest on main with both drivers.
evac odbc sql -c 'SELECT * FROM DB205DBA.TINCNTL'
thread '<unnamed>' panicked at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/arrow-odbc-6.1.0/src/reader/to_record_batch.rs:103:85:
called `Result::unwrap()` on an `Err` value: InvalidArgumentError("Column 'INV_NM' is declared as non-nullable but contains null values")
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Aborted

Hi, thanks for all the information. Minor nitpick, this is a not a segfault, nobody is accessing invalid memory. Instead the driver returned a value to unfit for a signed 64 Bit integer. Interestingly enough the value is supposed to be -98 given your issue in odbc-api (https://github.com/pacman82/odbc-api/issues/509). My understanding is the driver update did fix this for you?
The error tomsej  reported has the same symptom, but the cause is a different one.

@rupurt You might be able to mitigate the error about the non nullable columns by providing an arrow schema (using the schema parameter), with nullable columns. Other than that, this seems like a driver error (again). It just should not claim a column to be non-nullable, if it in actuality conatains nulls.

@pacman82 thanks for the clarification. I've updated the title.
This is the verbose output I get for the nullability error.
> evac odbc sql -c 'SELECT NUM FROM MYSCHEMA.MYTABLE' -v
DEBUG - ODBC Environment created.
DEBUG - SQLAllocHandle allocated connection (Dbc) handle '0x21976e0'
DEBUG - Database managment system name as reported by ODBC: DB2
DEBUG - ODBC driver reported for column 0. Relational type: Varchar { length: Some(20) }; Nullability: NoNulls; Name: 'NUM';
DEBUG - SQLColAttribute called with attribute 'ConciseType' for column '1' reported 12.
DEBUG - SQLColAttribute called with attribute 'DisplaySize' for column '1' reported 20.
DEBUG - Relational type of column 0: Varchar { length: Some(20) }
INFO - Column 'INV_NM'
Bytes used per row: 89
INFO - Total memory usage per row for single transit buffer: 89
thread '<unnamed>' panicked at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/arrow-odbc-6.1.0/src/reader/to_record_batch.rs:103:85:
called `Result::unwrap()` on an `Err` value: InvalidArgumentError("Column 'NUM' is declared as non-nullable but contains null values")
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Aborted

DEBUG - ODBC driver reported for column 0. Relational type: Varchar { length: Some(20) }; Nullability: NoNulls; Name: 'NUM';

Seems, db2 driver got that wrong.

@rupurt would you kindly copy the log and create a separate issue for this?

I would like to link to a dedicated issue in the documentation

@pacman82 done https://github.com/pacman82/arrow-odbc-py/issues/78
I've also added the column definition if it helps


Route redirect on back/forward in "pathname" mode doesn't work with query strings

I was trying to switch from "hash" to "pathname" mode for routing and running into an issue where mithril doesn't invoke a redirect when going back/forward and the route only differs by the query string.  I've been using query strings (e.g., "?param1=value&param2=value2") as a way to serialize state from my controllers to the URL for bookmarking.  With "hash" mode this was working perfectly.
It looks like the onpopstate callback that mithril registers doesn't consider query string differences when comparing the routes, which is the source of the problem.
I ended up working around this issue by using "search" mode instead, but it would be nice to fix this for consistency.  If I have time, I'll work on the pull request myself.

Fixed in origin/next and scheduled to be released in the next version


Add perl version checking in test suite

t/03-pcre-testinput1-02.t .. 211/?
#   Failed test 'TEST 37: testinput1:113 - bad regex: ^\ca\cA\c[\c{\c:: Use ";" instead of "\c{" at t/SRegex.pm line 162.
# '
#   at t/SRegex.pm line 166.
# Looks like you failed 1 test of 359.
t/03-pcre-testinput1-02.t .. Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/359 subtests
t/03-pcre-testinput1-03.t .. ok

@socketpair Seems like you're using a recent version of perl to run these tests. The tests on the master branch requires perl 5.16.x (like 5.16.2) at the moment.

Anyway, add perl version range checking in tests ( ,= SOME_VER or >= SOME_VER)

@socketpair Those tests are imported directly from PCRE and I think we just need to skip those tests in the PCRE test suite importer (in the file util/pcre_tests.pl of this repos).

@socketpair Well, just fixed in git master. Now both perl 5.16.2 and perl 5.24.0 can run the whole sregex test suite without failures on my side :)


Excessive Database Connections When Using Prisma with PgBouncer in PM2 Clustered Environment

Bug description
We are encountering an issue where Prisma opens an excessive number of database connections in a clustered environment managed by PM2, despite using PgBouncer for connection pooling. This behavior persists even when the application is not actively utilizing these connections, leading to an unnecessarily high number of open connections to the PostgreSQL database.
How to reproduce

Configure a NestJS application with Prisma and set up PgBouncer for connection pooling.
Deploy the application in a clustered environment using PM2 with multiple instances (e.g., 35 instances).
Observe the number of connections Prisma establishes with the PostgreSQL database.

Expected Behavior
Prisma should manage its connection pool efficiently, especially when used in conjunction with PgBouncer. The expectation is that Prisma would open a minimal and reasonable number of connections, considering PgBouncer's own pooling capabilities.
Actual Behavior
Prisma opens a connection pool with a significant number of connections for each PM2 instance, leading to a total number of database connections that far exceeds reasonable limits. This occurs even when there is no active demand for such a high number of connections from the application.
Additional Context
This issue is critical in a production environment where resource optimization is crucial. The excessive number of connections can strain the database server and affect the overall performance and stability of the application.
Any insights or recommendations on configuring Prisma and PgBouncer to work harmoniously in a PM2 clustered environment would be greatly appreciated. Additionally, if there are any known best practices or adjustments that can be made either in the NestJS-Prisma integration or in the deployment configuration to mitigate this issue, that information would be extremely valuable.
Thank you for your attention to this matter.
Prisma information

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

datasource db {
  provider  = "postgres"
  url       = env("DATABASE_URL")
  directUrl = env("DIRECT_URL")
}

Environment & setup

NestJS Version: 10.0.0
PgBouncer Version: 1.21.0
Libevent 2.1.12-stable
Adns: c-ares 1.18.1
Tls: OpenSSL 3.0.2 15 Mar 2022
Systemd: yes
PM2 Version: 5.3.0
Database (PostgreSQL) Version: 14
Deployment Environment: Ubuntu 22

Prisma Version
5.7.1

No Connection timeout or pooling added this is default result
prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
PM2        | prisma:info Starting a postgresql pool with 73 connections in PgBouncer mode.
After 10 min of run which idle timeout in pgbouncer is 10 sec
 this.prisma.notifications PM2        | → 559             .create( PM2        | Error in connector: Error querying the database: FATAL: no more connections allowed (max_client_conn) PM2        |     at si.handleRequestError (/var/www/panel-api/node_modules/@prisma/client/runtime/library.js:125:7007)

From your description it seems that you have configured Prisma to run with a connection pool size / connection limit of 73, and run 35 instances of that. On startup or first query each of those instances will open one connection to run that, and then open more connections when other queries are run at the same time - until the connection limit is reached (the log output above just shows that the pool can handle as many connections, not that it opens these connection at that time). With such a configuration you hence need to ensure that the responding database or pooler can handle at least 73x35 connections at the same time. Is that the case?
Generally this will mostly depend on how you configured PgBouncers. If it can deal with the open 73x35 connections and route these to whatever number of connections you have available on your actual database, this should not be a problem at all.


feat: add Payload SDK package

Adds Payload SDK package, which can be used to query Payload REST API in a fully type safe way. Has support for all necessary operations, including auth and simplified file uploading.
Its interface is very similar to the Local API, can't even notice the difference:
Example:
import { PayloadSDK } from '@payloadcms/sdk'
import type { Config } from './payload-types'

// Pass your config from generated types as generic
const sdk = new PayloadSDK<Config>({
  baseURL: 'https://example.com/api',
})

// Find operation
const posts = await sdk.find({
  collection: 'posts',
  draft: true,
  limit: 10,
  locale: 'en',
  page: 1,
  where: { _status: { equals: 'published' } },
})

// Find by ID operation
const posts = await sdk.findByID({
  id,
  collection: 'posts',
  draft: true,
  locale: 'en',
})

// Auth login operation
const result = await sdk.login({
  collection: 'users',
  data: {
    email<EMAIL_ADDRESS>    password: '12345',
  },
})

// Create operation
const result = await sdk.create({
  collection: 'posts',
  data: { text: 'text' },
})

// Create operation with a file
// `file` can be either a Blob | File object or a string URL
const result = await sdk.create({ collection: 'media', file, data: {} })

// Count operation
const result = await sdk.count({ collection: 'posts', where: { id: { equals: post.id } } })

// Update (by ID) operation
const result = await sdk.update({
  collection: 'posts',
  id: post.id,
  data: {
    text: 'updated-text',
  },
})

// Update (bulk) operation
const result = await sdk.update({
  collection: 'posts',
  where: {
    id: {
      equals: post.id,
    },
  },
  data: { text: 'updated-text-bulk' },
})

// Delete (by ID) operation
const result = await sdk.delete({ id: post.id, collection: 'posts' })

// Delete (bulk) operation
const result = await sdk.delete({ where: { id: { equals: post.id } }, collection: 'posts' })

// Find Global operation
const result = await sdk.findGlobal({ slug: 'global' })

// Update Global operation
const result = await sdk.updateGlobal({ slug: 'global', data: { text: 'some-updated-global' } })

// Auth Login operation
const result = await sdk.login({
  collection: 'users',
  data: { email<EMAIL_ADDRESS>password: '123456' },
})

// Auth Me operation
const result = await sdk.me(
  { collection: 'users' },
  {
    headers: {
      Authorization: `JWT  ${user.token}`,
    },
  },
)

// Auth Refresh Token operation
const result = await sdk.refreshToken(
  { collection: 'users' },
  { headers: { Authorization: `JWT ${user.token}` } },
)

// Auth Forgot Password operation
const result = await sdk.forgotPassword({
  collection: 'users',
  data: { email: user.email },
})

// Auth Reset Password operation
const result = await sdk.resetPassword({
  collection: 'users',
  data: { password: '1234567', token: resetPasswordToken },
})

Every operation has optional 3rd parameter which is used to add additional data to the RequestInit object (like headers):
await sdk.me({
  collection: "users"
}, {
  // RequestInit object
  headers: {
    Authorization: `JWT ${token}`
  }
})

To query custom endpoints, you can use the request method, which is used internally for all other methods:
await sdk.request({
  method: 'POST',
  path: '/send-data',
  json: {
    id: 1,
  },
})

Custom fetch implementation and baseInit for shared RequestInit properties:
const sdk = new PayloadSDK<Config>({
  baseInit: { credentials: 'include' },
  baseURL: 'https://example.com/api',
  fetch: async (url, init) => {
    console.log('before req')
    const response = await fetch(url, init)
    console.log('after req')
    return response
  },
})

Can't wait for this. By the way you've got a typo at packages/sdk/src/auth/rseetPassword.ts.

We could and I thought about this. And actually the same can be in e2e's, we have a custom SDK there but untyped


Nt/tweaks

What does this PR?

pin code modal fixes to achieve expected behaviour - check video
themefied input and welcome modal

Screenshots/Video
https://user-images.githubusercontent.com/6298342/111686188-9729f980-884a-11eb-9294-6f0e1abd22d7.mp4

handling mismatched pin while creating new pin
added translation entries

fixed issue with login popup appearing upon login after reset,

showing pincode popup for re-logging in user that had pin set previously without reset.

patched up issue logging out on login using pin code

Summary
Issue was from loginContainer, the pinCode screen was being called only for verification while essentially user logging in with pinCode means the keys should also update according user set pin code.
Now I am also setting new keys in realm on login with pin code.
The reason I am calling this a patch is because this logout issue was taking too much time, when I figured the issue I just tried patch as cleanly as possible. but overall, the whole pinCodeContainer class can be cleaned to become something very simple.

updated crypto.js to avoid UTF-8 malfunction issue during pin code verification

Improved encryption and handling failure for pin code related decryptions.

done

better handling decryption exception
stamping new encryptions


Pass props to map function

This should've always been there so it is passed to the map fn. Gonna release this as 1.2.6

Not complete - should update preact, also not passing props to map correctly.
For now, we worked around this in the app and don't need to update.


Wrong URL in README.md - NavigationAdvancedSample

Sample name - NavigationAdvancedSample
Link to UI Test (in Readme) redirects to 404 page
Thanks :)

Fixed, thanks!


Introduce nested test suites.

Right now we are unable to create nested test suites using this adapter even though YUI framework does support them. The goal of an issue is to bring this support to this adapter without breaking currently written tests.

See also https://github.com/benderjs/benderjs/issues/225


Go back to GitHub.  Go to Settings → Pages and change none to gh-pages.

There is no option "ph-pages" but only "none" (chosen) and "main" ... What did I do wrong here?

You have to go to "Actions" and investigate further what exactly did go wrong. There should be a red cross and error message that should be helpfull to debug this. It can have many reasons.


[FEATURE]

Description
I want to make the preview of the Border Radius automatically update as we slide the input. Currently it's only changed after we slide the input. Please assign me to this and I will open a PR right away. Thanks!
Screenshots
No response
Additional information
No response
👀 Have you checked if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read and understood the rules in the Contributing Guidelines

Are you willing to work on this issue ?
Yes I am willing to submit a PR!

It already does that

@Dun-sin Please take a look and see if you want this to be implemented.
Before:

After:

Already implemented

Closing this


Javascript loading issue

#93
Specific javascript files from a page are no longer loaded at app/assets/javascripts/application.js
Now these javascript files are loaded in their respective pages.
Another way to achieve the expected result from #93 is using "Event Delegation" as suggested here. However, by doing so would result in far more changes.

@lucianojfj , it's seems good, I've created a review app that we can play around.
You fix a lot of js issues with this, but it still have some other ones attached. Maybe they are not imported

This one should collapse:

This one should have a more actions menu:

I  will merge and we will create new issues to these bugs


Refactoring: exact recipe_step and crash_recipe

Slight replacement of #47
Given that had the go ahead on an equivalent PR, I'll merge this presently.


Example?

This is really great! I was just trying to do something similar. Do you have any examples usage?

Hey,
What kind of examples would you like to see? Displaying the different types of typography?

Yeah, that would be perfect!
By the way, for form controls, I've been using styled-components using the CSS from either https://github.com/dudeofawesome/MaterialCSS or https://github.com/muicss/mui. I don't have it organized into a nice theme like you have here (and also not using typscript), so this was an excellent best practice example.

I would recommend using this to show off the components: https://storybooks.js.org/


provenance hash, versions, etc missing from https://jhpoelen.nl/bats https://jhpoelen.nl/rats

For some reason, the expected provenance hash (see e.g., https://jhpoelen.nl/bees ) is missing from https://jhpoelen.nl/bats and https://jhpoelen.nl/rats. they were created using preston v0.3.0 .
See attached screenshots of expected (from bees)

and actual (rats and bats) -

minor errors in template generation fixed.


Add an MIT license

@ubien See if you agree with using an MIT license for the project, and whether we should use our own names for the copyright, or leave it as is now (PermanentLoss).


Preventing token from being created on ENTER

Hi,
This should be quite simple, but I can't get it to work...
I'm trying to prevent tokens from being created when the ENTER key is used.
I found this issue, but it doesn't seem to work for me? It creates the token every time.
https://github.com/sliptree/bootstrap-tokenfield/issues/166
This is my code:
$('#myInput').parent().on('keyup', function(e) {
	if(e.which === 13) {
		e.preventDefault();
	}
});

Also; I use keyup, because keydown nor keypress seem to pick up on the ENTER key.
Example:
.on('keydown keypress', function(e) {
var key = e.which
console.log(key);
This log returns no value on ENTER.

Solved by editing the JS!


The filename or extension is too long

I've been trying to find a solution for this for a very long time, is there any?
Caused by: java.io.IOException: CreateProcess error=206, Filnavnet eller filtypen er for lang
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.(Unknown Source)
at java.lang.ProcessImpl.start(Unknown Source)
... 9 more

I think that I've encountered this before but, it was a while ago...
If I'm remembering correctly, I believe thattThis happens when the number of characters exceeds 255 characters. This is a NTFS filesystem limit.
I think that I had solved this issue by simply reducing the number of characters in the file.
If I'm wrong, then it would be great for someone (like @iBotPeaches) could provide a correction to this because I'm just going by memory.

If you can post the apk, I can probably provide a solution

@CunningLogic https://octolus.net/example.rar

Correct. This is a duplicate of #1272
I am working on a solution to stage "groups" of changes to the application. So we do not exceed system limits of maximum command length.


Release 0.5.1

:cat2:

Hi @jonatanklosko, Could you please add .dmg files in the 0.5.1 release?

@tedhexaflow they will come eventually. They have not been automated yet, so there will be some delay until they are out of beta!

Oh! I see. Thank you so much 🙏 @josevalim

I just uploaded .dmg files, sorry for the delay!


Failed to install on OSX

This is more than likely just a shell/brew configuration problem my end, but it's proving very hard to work out how to fix, and would appreciate any help.
portaudio
> brew info portaudio
portaudio: stable 19.20111121, HEAD
http://www.portaudio.com
/usr/local/Cellar/portaudio/19.20111121 (8 files, 304K) *
  Built from source
From: https://github.com/Homebrew/homebrew/blob/master/Library/Formula/portaudio.rb
==> Dependencies
Build: pkg-config ✔
==> Options
--universal
        Build a universal binary
--HEAD
        install HEAD version

mpg123
> brew info mpg123
mpg123: stable 1.20.0
http://www.mpg123.de/
/usr/local/Cellar/mpg123/1.20.0 (20 files, 732K) *
  Built from source
From: https://github.com/Homebrew/homebrew/blob/master/Library/Formula/mpg123.rb

install
> gem install soundcloud2000
Building native extensions.  This could take a while...
ERROR:  Error installing soundcloud2000:
        ERROR: Failed to build gem native extension.

    /Users/ian/.rbenv/versions/2.0.0-p353/bin/ruby extconf.rb
checking for mpg123.h... no
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
        --with-opt-dir
        --without-opt-dir
        --with-opt-include
        --without-opt-include=${opt-dir}/include
        --with-opt-lib
        --without-opt-lib=${opt-dir}/lib
        --with-make-prog
        --without-make-prog
        --srcdir=.
        --curdir
        --ruby=/Users/ian/.rbenv/versions/2.0.0-p353/bin/ruby
please install mpg123 headers

Gem files will remain installed in /Users/ian/.rbenv/versions/2.0.0-p353/lib/ruby/gems/2.0.0/gems/audite-0.3.0 for inspection.
Results logged to /Users/ian/.rbenv/versions/2.0.0-p353/lib/ruby/gems/2.0.0/gems/audite-0.3.0/ext/mpg123/gem_make.out

So I tried installing the v1.14.4 of mpg123 as your README states 1.14, but that didn't help. I know know as this is a path issue, but worth a shot!
If I provide the path to the header it complains about the lib, so I add the path the lib, which then results in it complaining about portaudio.h missing!
> gem install soundcloud2000 -- --with-opt-include=/usr/local/Cellar/mpg123/1.14.4/include --with-opt-lib=/usr/local/Cellar/mpg123/1.14.4/lib
Building native extensions with: '--with-opt-include=/usr/local/Cellar/mpg123/1.14.4/include --with-opt-lib=/usr/local/Cellar/mpg123/1.14.4/lib'
This could take a while...
ERROR:  Error installing soundcloud2000:
        ERROR: Failed to build gem native extension.

    /Users/ian/.rbenv/versions/2.0.0-p353/bin/ruby extconf.rb --with-opt-include=/usr/local/Cellar/mpg123/1.14.4/include --with-opt-lib=/usr/local/Cellar/mpg123/1.14.4/lib
checking for portaudio.h... no
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
        --with-opt-dir
        --without-opt-dir
        --with-opt-include=${opt-dir}/include
        --with-opt-lib=${opt-dir}/lib
        --with-make-prog
        --without-make-prog
        --srcdir=.
        --curdir
        --ruby=/Users/ian/.rbenv/versions/2.0.0-p353/bin/ruby
portaudio.h not found
please brew install portaudio
or apt-get install portaudio19-dev

Gem files will remain installed in /Users/ian/.rbenv/versions/2.0.0-p353/lib/ruby/gems/2.0.0/gems/audite-0.3.0 for inspection.
Results logged to /Users/ian/.rbenv/versions/2.0.0-p353/lib/ruby/gems/2.0.0/gems/audite-0.3.0/ext/portaudio/gem_make.out

brew doctor does show a few problems, but nothing related that would effect this, I think.
brew doctor

Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!

Warning: Unbrewed dylibs were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected dylibs:
    /usr/local/lib/libosxfuse_i32.2.dylib
    /usr/local/lib/libosxfuse_i64.2.dylib

Warning: Unbrewed .la files were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected .la files:
    /usr/local/lib/libosxfuse_i32.la
    /usr/local/lib/libosxfuse_i64.la

Warning: Unbrewed .pc files were found in /usr/local/lib/pkgconfig.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected .pc files:
    /usr/local/lib/pkgconfig/osxfuse.pc

Warning: You have unlinked kegs in your Cellar
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run `brew link` on these:

    macvim

Installing xcode-select --install [1] did it for me.
I was sure I had Xcode already setup, but maybe I forgot to update it with latest update in OS
[1]http://stackoverflow.com/a/24541621/71994

@zdrummond worked for me! Thanks. I added it to the README and opened a pull request.


BETA-40 : Automatic Decryption not working

The Automatic Decryption Option is set but not working with Outlook 2013.
Always have to decrypt the message by Hand.

Automatic decryption will not work in the preview window. However if you open the message it will decrypt automatically.

Adding a feature request to track #63.


Rename Kotlin Files With Spaces

Some of the .kt files have spaces in the filenames.  Replace these with camel-case or underscore.

Remove spaces in Component View Class.kt
Also, change case checkBoxfilter.kt to CheckBoxFilter.kt


Helm chart install failure due to missing apiVersion policy/v1 on K8s 1.20

Describe the bug:
The vault and vault-secrets-webhook Helm charts could not be installed after #1404 on Kubernetes <v1.21.
Expected behaviour:
Expected the install to succeed.
Steps to reproduce the bug:
Just following the steps described here:
$ kubectl create secret generic aws --from-literal=AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID --from-literal=AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY
$ helm install vault banzaicloud-stable/vault --set "vault.customSecrets[0].secretName=aws" --set "vault.customSecrets[0].mountPath=/vault/aws"
Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "PodDisruptionBudget" in version "policy/v1"

Additional context:
In #1404, more precisely here the PDB's apiVersion has been changed from policy/v1beta1 to policy/v1. The latter is only available from Kubernetes version 1.21 according to the migration guide.
Environment details:

Kubernetes version (e.g. v1.10.2): v1.20.6
Cloud-provider/provisioner (e.g. AKS, GKE, EKS, PKE etc): PKE
bank-vaults version (e.g. 0.4.17): 1.14.0
Install method (e.g. helm or static manifests): helm
Logs from the misbehaving component (and any other relevant logs): -
Resource definition (possibly in YAML format) that caused the issue, without sensitive data: -
Helm version: v3.5.4

/kind bug

This should have been fixed in https://github.com/banzaicloud/bank-vaults/commit/d03bedf261cf4f1bf1bac32af7ccb397d4ba6d0d are you using this version @adamantal ?


Trigger validation on component render

Hi there!
Is it possible to validate AvField right after component has been rendered? I'm rewriting UI which gets bogus data every now and then from the database. I would like to point to user right away that some of the data needs attention.

Hey @tuok, if you want this functionality you can just submit the form once its rendered by calling the submitForm on the FormCtrl context.
We are working on a re-write to hooks and we will provide a better API for making these modifications but at the moment you can use the native dom.
Maybe create a submit button like this:
export default () => {

useEffect(() => {
document.forms.<your-form-name>.submit();
},[]); // runs only on mount

 return(<Button>Submit</Button>)
}

The form is always validated when it loads, but the styles are tied to whether or not the input has been "touched". So you could use custom CSS to style the fields. (for AvField, the error message is only rendered when touched so CSS will not help there).
If you are using AvField, I would get a ref to AvForm and call setTouched on that ref providing the list of input names you want to validate. It will show the errors to the UI without attempting to submit the form (so your onValidSubmit callback would not be called if the form was valid).
Check out: https://stackblitz.com/edit/reactstrap-validation-v2-9hgegg?file=Example.js

Thanks a lot for the comments, I will give these a try!


nixos/openconnect: Add NixOS module for declarative OpenConnect VPNs

Description of changes
OpenConnect is a free reimplementation of various proprietary VPNs like Cisco AnyConnect. This module allows declaratively configuring them, exposing the most commonly used options as submodule options and leaving an extraConfig field for the rest of them.
I tested this with my university VPN (Cisco AnyConnect), any input is welcome.

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Probably @pradeepchhetri @tricktron because you maintain OpenConnect

Thanks for the review @pennae ! :) I've implemented most of the suggestions now.

@aanderse In my opinion, the problem with the non-key-value pair flags like --no-dtls is that while a boolean KV pair is an accurate representation, it might still be confusing for users reading the docs seeing that both non-KV and KV options are KV pairs in the module config. Intuitively, you'd also expect a config option like deflate = false; to have an effect on the generated config, but if I understand your reasoning correctly, you are proposing to filter for true values and put the corresponding keys into the configfile without the boolean value.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/vpn-slice-in-nixos-wants-write-access-to-etc-hosts/18540/3

I've added a couple of hardening flags now. These are not very fine grained for now, the problem here is that openconnect is built to function with a wide range of proprietary VPNs, and stricter hardening like ProtectKernelTunables might break some edge use cases.

Update: Even the relatively few hardening flags I've added broke my VPN after about 5 minutes of continuous operation. I've only put in ProtectHome now to stay on the safe side.

very unfortunate that hardening breaks this. :slightly_frowning_face: but that's how it is then.


The Performance score is true?

Found one new CP in github
https://github.com/Chris2018998/BeeCP

Tomcat, in its default configuration, is also faster than HikariCP.  Unfortunately, it is also unreliable due to ignoring basic principles of correctness.  The same goes for BeeCP.  See:
"My benchmark doesn't show a difference."
And in particular: What does correctness and reliability mean?

Hi Brett,
Thanks for your reply, You have reviewed  its source code or run it with your benchmark?  About reliability, you have some test case to validate CP ?


GeoIP database needs to be loaded

MaxMind database needs to be loaded to retrieve geo location.

Fixed in the develop branch.
https://github.com/xavier-hernandez/goaccess-for-nginxproxymanager/commit/651b180cba038799a2d64b59b3c00fdba2b6f170


Add flexibility to emails

Right now I feel like email templates are too rigid and I think it can be improved. Looking at the code in email.ts
https://github.com/nhost/hasura-auth/blob/666b411b6fcd8b8e265d7668b07cd385fc9f816b/src/email.ts#L32-L41
We can see that you are replacing the placeholders with the variables and then here: https://github.com/nhost/hasura-auth/blob/666b411b6fcd8b8e265d7668b07cd385fc9f816b/src/email.ts#L118-L132 you are exporting the client to be used anywhere you need to send an email.
Looking at send-verification-email: https://github.com/nhost/hasura-auth/blob/666b411b6fcd8b8e265d7668b07cd385fc9f816b/src/routes/user/email/send-verification-email.ts#L63
We are sending the email using emailClient and in locals (I think it's a misleading variable name) https://github.com/nhost/hasura-auth/blob/666b411b6fcd8b8e265d7668b07cd385fc9f816b/src/routes/user/email/send-verification-email.ts#L82-L91
we are sending the variable that are going to replace the placeholders in the email templates.
I'd like to propose some flexibility in the email templates, why not allow the BodyType to accept a emailData option that would allow us to pass our own data into the email template and we could simply forward this to the template engine.
We could have this
type BodyType = {
  email: string;
  options?: {
    redirectTo?: string;
  };
   emailData?: Record<string, string>
};

await emailClient.send({
    template,
    message: {
      to: email,
      headers: {
        'x-ticket': {
          prepared: true,
          value: ticket,
        },
        'x-redirect-to': {
          prepared: true,
          value: redirectTo,
        },
        'x-email-template': {
          prepared: true,
          value: template,
        },
      },
    },
    locals: {
      link: `${ENV.AUTH_SERVER_URL}/verify?&ticket=${ticket}&type=emailVerify&redirectTo=${redirectTo}`,
      displayName: user.displayName,
      ticket,
      redirectTo,
      locale: user.locale ?? ENV.AUTH_LOCALE_DEFAULT,
      serverUrl: ENV.AUTH_SERVER_URL,
      clientUrl: ENV.AUTH_CLIENT_URL,
     ...emailData,
    },
  });

I could have an html template like so
<!doctype html>

        <title>
          $title
        </title>

$greeting $displayName

$content

$verifyParagraph link

$footerContent

    </body

Then when using the SDK to send a verification email I could do this
nhost.auth.sendVerificationEmail({
    email<EMAIL_ADDRESS>    options: {
      redirectTo: 'https://my-cool-website.com/redirect',
    },
    emailData: {
      title: 'my email title',
      greeting: 'Hi',
      content: 'This is the content that will be replaced, it can even use html',
      verifyParagraph: 'Please verify your email addres using this',
      footerContent: 'Thank you

Have a great day'
    },
  })

This would allow me to, first, it would allow me to have only one locale for the email, since you default to en when none is provided since I could check what's the user locale and translate the content of my strings accordingly (multilingual emails out of the box), second, allow me to pass some more data in the email than I already can and still be able to handle it.
I'd love to have your thoughts on this and I'd be more than happy to open a PR for this.

I don't think it's a good idea that we let clients decide the content of the email. I can see lots of problems with this.
For example, what if a hacked do this on your app:
nhost.auth.sendVerificationEmail({
    email<EMAIL_ADDRESS>    options: {
      redirectTo: 'https://my-cool-website.com/redirect',
    },
    emailData: {
      title: 'URGENT: Change password now',
      greeting: 'Hi',
      content: 'Our database was hacked and you need to change your password immediately. Go to https://yourapp1.com/change-password and update your password now.',
      footerContent: 'Thank you

Have a great day'
    },
  })

This email will be sent from your (app's) SMTP server.
Meaning, any hacker can send an email to any email address with almost any content.
That's why I don't think this approach is a good idea.

Hi Johan,
If someone hacked into my app, this would be the last of my problems as he could have greater chances of doing what more damage than this.
He could read all my database content, he could do way more nasty things than sending users to a website to change their email.
Is it any different than having us handling emails on our side? I mean if we decide to bypass the SDK and handle email our selves, I don't see how it would be any different.
I don't think the argument of being hacked is a valid one.

I think you misunderstood me.
I'm not saying that "someone hacked into" your app and has access to your database.
But the change you're proposing would mean that anyone would be able to send basically any email they want to any email address using your SMTP credentials. That's not good.
I think it's important that the email templates and variables are defined securely on the server.

@elitan is there a way to use the SDK on the server-side to achieve similar results? right now the way templates are handled is not flexible enough for our needs.

@elitan by the way you got me thinking - what kind of security is there on this API? From your response, are you saying anyone right now can send templated-email content to anyone? Injecting the content is one way to "hack" but it does look to me like this type of functionality should be handled on the server-side to prevent abuses.

is there a way to use call nhost.auth.sendVerificationEmail on the server-side to achieve similar results?

Similar to what?

right now the way templates are handled is not flexible enough for our needs.

What is it that you want to be able to do, that's not currently possible with the current setup with email templates?

From your response, are you saying anyone right now can send templated-email content to anyone?

Depends on what you mean with "templated-email content". WHa you can do now is define different templates for different languages.
As an example, we've created an example here. In the example we have email templates for two languages; English and French.
If the user has their locale value set to en in the database (auth.users table) the English templates are used. If the locale value is set to fr the French templates are used.
These templates are defined by the developer and exist only server-side and can not be edited by end-users (client-side).
The variables injected into these email templates are also defined server-side. here's an example: https://github.com/nhost/hasura-auth/blob/main/src/routes/signin/passwordless/email.ts#L119-L126
As you can see in the code above, Hasura Auth injects:

link (link to be used in the email for the user to click)
displayName (user's display name)
email (user's email)
ticket (ticket, internal usage)
redirectTo (where to redirect the user)
locale (user's locale)
serverUrl (URL to Hasura Auth)
clientUrl (Default client URL. Usually the frontend app URL)

Injecting the content is one way to "hack" but it does look to me like this type of functionality should be handled on the server-side to prevent abuses.

Totally agree. Exactly my point.

Hi @elitan,
I'm sorry for the misunderstanding, it's mainly because of my inexperience with backend :) Indeed, I totally forgot that we would be executing this code in the client side, thus making it vulnerable to unwanted things.
I am going to close this issue and resin myself to use email templates as it is :D
Thank you for your time


Improving The Animation

Is your feature request related to a problem? Please describe.
Instead of Animating the whole card at once, We can let them come in a staggered manner.
This appears much better than the whole.
Describe the solution you'd like.
Use framer motion's delay property
Describe alternatives you've considered.
No response
Additional context.
No response
Show us the magic with screenshots
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)
[X] I am a GSSoC'23 contributor

I would like to a solve this issue . Please assign me this issue.


Cannot build gtk2hs-buildtools with latest nixos-unstable

Issue description
One of my personal packages uses gtk2hs and thus gtk2hs-buildtools and with the latest nixos-unstable channel I cannot build it.  Picking out the relevant lines among the others of my build (some may be elided because they are mixed in with the other things being built):
setupCompileFlags: -package-db=/tmp/nix-build-gtk2hs-buildtools-<IP_ADDRESS>.drv-0/package.conf.d -j1 -threaded
[1 of 1] Compiling Main             ( Setup.hs, /tmp/nix-build-gtk2hs-buildtools-<IP_ADDRESS>.drv-0/Main.o )
Configuring gtk2hs-buildtools-<IP_ADDRESS>...
Setup: At least the following dependencies are missing:
Cabal >=<IP_ADDRESS> && <1.25
builder for ‘/nix/store/fqwvkw0sffjdy93208cmzl2dnr2r55n6-gtk2hs-buildtools-<IP_ADDRESS>.drv’ failed with exit code 1
cannot build derivation ‘/nix/store/f0ngf479q5nl18687djiplnl96s19ja6-glib-<IP_ADDRESS>.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/61f9y9hxxkqmnn5n7y9xk844rn9c76li-gtk-0.14.5.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/wxwkzb8f3cqh8fa4kc846zcwc6nbdq75-gtkmenu-<IP_ADDRESS>.drv’: 1 dependencies couldn't be built

This seems related to the recent commit 7619f88eb850b4e4b2fc551665cef53839041d43  from @peti as it doesn't appear that the override was moved anywhere else (at least within the channel update).
Steps to reproduce
I was running an update of my NixOS system with a package that depends on gtk2hs enabled:
sudo nixos-rebuild switch --upgrade

Technical details

System: NixOS  16.09pre90254.6b20d5b (Flounder)
Nix version: nix-env (Nix) 1.11.3
Nixpkgs version: "17.03pre91207.2b0eace"

This happens on trying to update to:
downloading Nix expressions from ‘https://nixos.org/releases/nixos/unstable/nixos-17.03pre91207.2b0eace//nixexprs.tar.xz’...

haskellPackages.gtk2hs-buildtools builds fine.
Build fails for haskell.packages.ghc7103.gtk2hs-buildtools (verified against 7b65daaab45fd3c6fc8c871e4a1f5ab155547068):
rasen@ashmalko ~/nixpkgs> nix build haskell.packages.ghc7103.gtk2hs-buildtools
these derivations will be built:
  /nix/store/fqwvkw0sffjdy93208cmzl2dnr2r55n6-gtk2hs-buildtools-<IP_ADDRESS>.drv
building path(s) ‘/nix/store/m5gb8myq3apwih45yndw6dg2xmqs07ng-gtk2hs-buildtools-<IP_ADDRESS>’
setupCompilerEnvironmentPhase
Build with /nix/store/i18mff3kbhpf4n6bvl779yfm1v1swb86-ghc-7.10.3.
unpacking sources
unpacking source archive /nix/store/js7dzh5scd3gi2969sgmai5hg21f8x8y-gtk2hs-buildtools-<IP_ADDRESS>.tar.gz
source root is gtk2hs-buildtools-<IP_ADDRESS>
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file gtk2hs-buildtools-<IP_ADDRESS>/src/Gtk2HsSetup.hs
patching sources
compileBuildDriverPhase
setupCompileFlags: -package-db=/tmp/rasen/nix-build-gtk2hs-buildtools-<IP_ADDRESS>.drv-0/package.conf.d -j8 -threaded
[1 of 1] Compiling Main             ( Setup.hs, /tmp/rasen/nix-build-gtk2hs-buildtools-<IP_ADDRESS>.drv-0/Main.o )
Linking Setup ...
configuring
configureFlags: --verbose --prefix=/nix/store/m5gb8myq3apwih45yndw6dg2xmqs07ng-gtk2hs-buildtools-<IP_ADDRESS> --libdir=$prefix/lib/$compiler --libsubdir=$pkgid --with-gcc=gcc --package-db=/tmp/rasen/nix-build-gtk2hs-buildtools-<IP_ADDRESS>.drv-0/package.conf.d --ghc-option=-optl=-Wl,-rpath=/nix/store/m5gb8myq3apwih45yndw6dg2xmqs07ng-gtk2hs-buildtools-<IP_ADDRESS>/lib/ghc-7.10.3/gtk2hs-buildtools-<IP_ADDRESS> --enable-split-objs --disable-library-profiling --disable-executable-profiling --enable-shared --enable-library-vanilla --enable-executable-dynamic --enable-tests
Configuring gtk2hs-buildtools-<IP_ADDRESS>...
Setup: At least the following dependencies are missing:
Cabal >=<IP_ADDRESS> && <1.25
builder for ‘/nix/store/fqwvkw0sffjdy93208cmzl2dnr2r55n6-gtk2hs-buildtools-<IP_ADDRESS>.drv’ failed with exit code 1
error: build of ‘/nix/store/fqwvkw0sffjdy93208cmzl2dnr2r55n6-gtk2hs-buildtools-<IP_ADDRESS>.drv’ failed

Ah, yes, that was my problem.  I thought I had updated my compiler references in the right place to use the latest default compiler in nixos-unstable, but I was still referencing ghc7103.  Updating it to use ghc801 made things work.
So this bug can be closed if it is known that gtk2hs-buildtools will not build on ghc7103.

I will leave this for @peti to decide.


Refactored tests.serializers.test_data.

These changes were discussed in #18799 (cc @bmispelon @adamzap) as part of the work of ticket-21286

buildbot, test on oracle.

buildbot, test on oracle.

buildbot, test on oracle.

buildbot, test on oracle.


feat: Add more commands

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

v1.6.0
v1.6.0
GitHub release

Your semantic-release bot :package::rocket:


Outdated roadmap and no news in last 2 months

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[X ] Documentation issue or request
[ ] Other... Please describe:

Browser:

[ ] Chrome version XX
[ ] Firefox version XX
[ ] IE version XX
[ ] Edge version XX
[ ] Safari version XX

Library version

Library version: X.Y.Z

Current behavior

Wiki, roadmap and news are outdated. MSAL 1.2 and 1.3 are still marked for September, when there is no sign of 1.2 getting out of beta.
Expected behavior

It should be easier to understand where the project is at and is going to, by adding monthly news / update and updating wiki.
Minimal reproduction of the problem with instructions

@yann-combarnous A newsletter for timely announcements is something we have been considering for some time. cc @DarylThayil.
Regarding 1.2 release, we think we are close to it now as the betas are now tested well around and we have received great feedback from the community. We plan to announce it soon and wiki will be updated. We have been holding off the wiki updates for betas and planned it for the major release.


Can't click on stuff

and the text is cut away too I guess

oh nvm it works you just cant click the tabs at the top but have to click next lol


Updated and improved Latvian translations

This PR updates Latvian translation files with some missing messages since the last time Latvian translation files were reviewed.
Also fixed some small typos and changed name of "components" to equally similar Latvian word which sounds better and is used more often in daily language.

Thanks @arvislacis!


FF-RN-19Jan23

Added FF SDK release notes for 19th January 2023. These SDK releases happen outside of the Harness release cycles.
Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Preview environment: https://ci.pr.harness.io/pr-392

Preview environment: https://ci.pr.harness.io/pr-392


Demo is not working

The demo throws the following error, which happens because the imported matchSorter.rankings is undefined.

The demo is using<EMAIL_ADDRESS>which needs to be bumped to the latest version and moved from npmcdn to unpkg.

Thanks for finding that! It should be working now :)

Ooooh, actually it's not... Looks like something's wrong with the export of the rankings object... Probably an issue that happened with #9

@rogeliog, I've filed a PR that should fix these issues. Let me know what you think.


Disable window border when on fullscreen

yabai -m window --toggle zoom-fullscreen

Toggles a window to fullscreen, but how can I disable the window border on any full-screened window? I'm assuming I have to use a signal, but I do not know how to set it up. Thanks

If you in general always have window borders enabled; you can just do `yabai -m window --toggle zoom-fullscreen --toggle border


Add tokens for single text attribute

For newly created attributes the whole project is tokenized to add the tokens for the new attribute.
To speed up the process and keep the already tokenized attributes working, we need a possibility to create tokens for the added attribute and add them to the already existing tokens (record_tokenized, docbin).
Similarly, it would be nice to have a way to remove these tokens again.
See
https://github.com/code-kern-ai/refinery-ac-exec-env/issues/3
https://github.com/code-kern-ai/refinery-ac-exec-env/issues/4

This is only an issue anymore for calculated text attributes. All other attributes are simply added to the docbin and the tokenization is not triggered again.
Removing user-created attributes without retokenization is also possible by now.

included in pr


Use delegates strategy for checkValidation

checkValidation should validate or undecided types. In order to achieve this, it is effective to use delegates.

:octocat: cibot: Thank you for posting issue #387. The person in charge will reply soon.

We no longer have checkValidation, rather we have 'finalize' which is in charge of making the layer valid after the call


Hosting suddenly stopped applying custom headers set from customHttp.yml

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id

AWS Region
eu-west-1
Amplify Hosting feature
Custom headers
Frontend framework
React
Next.js version

Next.js router
N/A
Describe the bug
I am setting custom headers from customHttp.yml file like this:
applications:
  - appRoot: my-app
    customHeaders:
      - pattern: '/assets/*.js'
        headers:
        - key: 'Access-Control-Allow-Origin'
          value: '*'

Reason for this being is, that our app is embedded onto customers site by loading the necessary files from the hosting, and since our app is loaded using <script type="module"... , we run into CORS settings without setting these headers.
Everything has been working fine, but suddenly with no changes at all in production we started running into the CORS problem, just as it simply stopped adding those headers. Re-deploying the latest build fixed this issue, which did not occur in our dev or staging environments. How could this happen? If necessary, I can provide the app id privately with email for example.
Expected behavior
Hosting should not out of nowhere stop applying the specified custom headers.
Reproduction steps
I have no idea how to re-produce this.
Build Settings
No response
Log output

# Put your logs below this line

Additional information
No response

Hi @parvusville 👋 , thanks for reaching out to us!
Since I was unable to reproduce this behavior on my end, can you please provide us the following information:

Amplify App ID
Are you actively able to reproduce this behavior with your app where your custom headers are only applied when redeploying the latest build?
Approximately when did the issue first surface?

You can share your Amplify App ID related details privately via a DM on our community discord server. My username is Jay Raval. Alternatively, you can also send an email to<EMAIL_ADDRESS>Either method works fine!

As a very rapid resolution, redploying should bring back your custom headers. We will continue to investigate.
Please see @Jay2113's questions above. We will better be able to troubleshoot with additional information.

Hello, I have provided the App ID for @Jay2113  in Discord.
I am not actively able to re-produce. This is the first time I run into this, and after re-deploying the latest build it has been working for now.
We received the first error report yesterday, 3.7. 11:19  (UTC), and around 11:32 I confirmed that everything works again after the de-deployment.

Thanks for sharing the additional details @parvusville. We have identified this as a bug and are actively working on mitigating it. I will keep you posted with any updates on the fix.
We really appreciate your continued patience and cooperation.

@Jay2113 - I'm noticing issues as well with our teams Amplify application.  Could you confirm if the following is related to the bug you found?
We're currently hosting webapp A, with re-write redirect rules for certain sub-paths of A pointing to webapp B.
We were able to get around CORS issues by adding a customHttp.yml file to webapp B with the following contents and saw webapp B loading from https://webappa.com/webappb.
## customHttp.yml
customHeaders:
  - pattern: '**'
    headers:
      - key: 'Access-Control-Allow-Origin'
        value: '*'
      - key: 'Access-Control-Allow-Headers'
        value: '*'
      - key: 'Access-Control-Allow-Methods'
        value: 'GET'

However now we're seeing a CORS issue when trying to load webapp B. The JavaScript file (https://<webappb>.amplifyapp.com/assets/index.js), requested by webapp B's index.html after being loaded from webapp a's redirect rule, is not returning the CORS headers.
The index.html page that is being loaded does have the correct CORS headers.
We tried re-deploying the branch of webapp B, but no luck.

After more investigation, it looks like the headers aren't getting applied to responses for sub-paths.
https://<webappb>.amplifyapp.com/asdf returns the configured CORS headers, but https://<webappb>.amplifyapp.com/asdf/asdf does not return the CORS headers.  Both use the same redirect rule and serve up our index.html page.


Installation on Windows (win7) fails

When I try npm install ws (on my win7 machine), I get the following errors:
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\x64\Microsoft.Cpp.x64.Targets(152,5): error MSB6006: "CL.exe" exited with code
-1073741515. [D:\Sandbox Consulting\node_modules\ws\build\bufferutil.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\x64\Microsoft.Cpp.x64.Targets(152,5): error MSB6006: "CL.exe" exited with code
-1073741515. [D:\Sandbox Consulting\node_modules\ws\build\validation.vcxproj]

I am using npm 1.2.32 and node 0.10.  I have just re-installed Visual Studio 2010 Express for Windows Phone, the win 7.1 sdk and python 2.7.5.   I was getting a slightly different error message before.  However both times, the errors seem to be about some inconsistency between MSBuild and the vcxproj files.
Googling, you can see quite a few questions about npm install errors on windows, sometimes stemming from trying to install bcrypt.  My suspicion is that these issues are related, and may be related to an internal inconsistency snafu with MS products, as discussed here:  http://stackoverflow.com/questions/1901279/windows-7-sdk-installation-failure.  But in my case, following their advice did not fix the problem for me (though it did change the error message)
I'm not enough of a windows dev to really debug the problem.  And I don't know how the build process is supposed to work on windows (how are the vc project files being generated, for example).   But I think if someone figures it out, there are a lot of related issues out there that would be fixed.

28\node_modules\npm\bin\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
MSBUILD : error MSB4132: The tools version "2.0" is unrecognized. Available tools versions are "4.0".


feat: add status hint to start command.

I didn't know supabase status command existed. This can help tell folks about it. Wdyt?

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 62.688%

Totals

Change from base Build<PHONE_NUMBER>:
0.006%

Covered Lines:
3839

Relevant Lines:
6124

💛  - Coveralls


“Send “ and “Request” buttons on Home screen are not enabled while creating an account when phone number confirmation is skipped.

Frequency: 100%
Repro on build version: Android Internal Build V1.24.0, Test Flight Build V1.24.0
Repro on devices: iPhone 13 mini (15.1.1), iPhone 12 (14.7.1), Samsung Galaxy A8+(8.0), One plus 7t(11.0), Google Pixel 2XL(11.0), iPhone 6+(12.5.4)
Does Not Repro on build version: Android Play store Build V1.23.3, Android internal build  V 1.24.0,  Test flight Build V1.23.3, V1.24.0
Does Not Repro on devices: One plus 7t(11.0), Google Pixel 2XL(11.0), iPhone 13 mini (15.1.1),  iPhone 6+(12.5.4)
Pre-condition:

User must have installed the app.
User must be on the Phone Number Screen while creating a new account.

Repro Steps:

Tap on the “Skip” button from the top right corner from the “Phone number screen”.
Tap on the “Skip for now” button from “Are you sure?” popup.
User navigates to the home screen & observe.

Current Behavior: “Send” and “Request” buttons on the Home screen are not enabled while creating an account when phone number confirmation is skipped.
Expected Behavior: “Send” and “Request” buttons on the Home screen must get enabled while creating an account when phone number confirmation is skipped.
Investigation:

While creating an account by confirming the  phone number,  “Send” and “Request” buttons are not enabled.
“QR code” button besides the Request button appears enabled but is not tappable.
This issue is not reproducible while the user restores an account having some account balance.

Impact: Bad user experience as the user is not able to tap on the Send and request button after creating a new account.
Attachment: Send and receive button.mp4

This is on purpose for sending since you can't send if you have no balance. Requesting should work though

Hey @MuckT, Thanks for the information.

Hey @MuckT we have provided our observation in the ticket #1809


[Bug Report] El-Upload displays native input button along the el-button

Element UI version
2.4.7
OS/Browsers version
Mac Os / Chrome 68.0.3440.106
Vue version
2.1.8
Reproduction Link
https://jsfiddle.net/mmx38qxw/
Steps to reproduce
I am implementing ElementUI inside a already existing project. All components are displaying fine except the el-upload. It shows the native input alongside the el-button:
<el-row>
    <el-col :span="6">
      <el-upload
        class="image-uploader"
        ref="imageUploader"
        action="http://localhost:5000/api/blog/upload"
        :auto-upload="false"
        :file-list="fileList"
        :limit="1"
        accept=".jpg, .jpeg, .png"
        list-type="picture">
        <el-button slot="trigger" size="small" type="primary">select file</el-button>

jpg/png files with a size less than 500kb

      </el-upload>
    </el-col>
  </el-row>

https://imgur.com/a/22LXvyu
What is Expected?
Only the el-button, like in the example and in the reproduction-link
What is actually happening?
Both buttons is showing

@simonkaspersen Could you please provide a right link?

Hello!
I had the same problem and i fixed with this:
input[type=file] {     display:none; }
Grettings!!


Process finished with exit code 136 (interrupted by signal 8: SIGFPE)

Thanks for your owesome work and There some problems when i try to run samples/bevformer/plugin/tiny/onnx2trt.sh with 2080Ti

Please provide your environments like PyTorch, coda, onnx, tensorrt versions.

TensorRT-<IP_ADDRESS>     onnx==1.8.0   torch==1.12.0+cu116

sh samples/bevformer/plugin/tiny/pth2onnx.sh
bevformer_tiny_epoch_24_cp.onnx 链接
链接: https://pan.baidu.com/s/1Q0x1p7_Nh3LItqdkDIx9rQ  密码: b0su

if I change onnx version to 1.7.0, just like your bevformer_tiny_epoch_24_cp.onnx, it works.

Glad to here that! BTW, my onnx version is 1.12.0 and pytorch version is 1.12.1+cu116.

Do you meet this warning when running  samples/bevformer/plugin/tiny/pth2onnx.sh
I think it's the reason of core dumped

Yes, this warning appears many times, but it dose not affect the model transformation.


Update specs2-core, specs2-scalacheck to 4.10.3

Updates

org.specs2:specs2-core
org.specs2:specs2-scalacheck

from 4.10.0 to 4.10.3.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.specs2" } ]

labels: test-library-update, semver-patch

Superseded by #51.

Superseded by #51.


Network in Linux 3.18 doesn't work

On the page it's written:

With internet access, udhcpc, wget and links.

However I'm testing Linux 3.18 and links which is installed and it doesn't open anything, secondly ifconfig doesn't return any network interfaces. Was this working before?
I've tried also: /etc/init.d/S40network start with with no success.

Run dhcpcd first. I'll document this.

Thanks, it works, ignoring some crash:

But after that it seems the networking is on. Pity there is no curl.
I've tried something like: wget -qO- ifconfig.co and there is 'Network is unreachable', however host response to pings. The same with wget www.google.com.
Looks like it's trying to IPv6.

Tested in Chrome 45 on OS X.

Indeed, there seems to be an issue with ipv6. Some websites work (copy.sh, for instance). Using links -source google.com works too.

telnet 4.ifcfg.me works aswell


Fix copy path in windows runtime e2e test Dockerfiles

Description
Fix copy path in windows runtime e2e test Dockerfiles. This should be the last broken windows test.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #1906
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

/ok-to-wintest

/ok-to-wintest


Make the combinators configurable

We need to design combinators to specify only valid configurations. We can possibly use phantom types.

We need to design combinators to specify only valid configurations. We can possibly use phantom types.


Temporary solution for #13975 - make documentation of current behaviour more clear

Workaround for #13975 - document current behaviour more clearly.

Q
A

Is bugfix?
no

New feature?
no

Breaks BC?
no

Merged. Thanks!


Add CBC cipher support

Add CBC support

Thank @jerrychenhf , I will add 192bit key support.

Thank @jerrychenhf @vanzin for your review, I have updated the patch

+1

Thank @jerrychenhf @vanzin for your review.


Added utility to auto-fetch eslint rule config settings

tools/convertEslintConfig.ts methods return drop in configuration options that can be plugged into the rules object of your tslint.json. This allows sharing of eslint and tslint configs, which is pretty dang useful.

This is a really cool idea 👍  I think there's a bit more work involved to see it through and I'd love to make that happen. There's rules that exist in native TSLint and with those the format is a lot different to the ESLint config options. I'll need to check, but isn't there also a difference in how the options are specified?

Good to know. I haven't done much testing for the native rules, but the tests that I've done for non-native rules have all worked when using the exact configs returned from eslint.
I'm definitely open to discussion on this. My use case isn't super well defined yet, as I've got several eslint configs (essentially one for the browser, one for testing, one for a node environment (builds)) and I haven't fully figured out how to ensure I'm using the most correct one when this tool is used.
To address your issue (differences in options/config) a simple immediate solution could be adding a boolean field to IRule that indicates if there is a difference in config and testing that for false. Longer term we could add config transformer functions to each rule.

Any idea why Travis is taking so long to build for node 6? Nice tool by the way.
@blakeembrey I can't remember if there are rules in this project that change the config but if this is the case we could change them to match the ones from eslint. The goal of the project after all is to have eslint compatible rules.
@apexskier Run gulp self-lint to point out the errors that node 4 is giving out on travis.

@jmlopez-rod Thanks for the heads up. I was thinking about the native TSLint rules though, or is this skipping those altogether (I know there's links in the README pointing to the TSLint native rules)? If this lands, it'd be good to support those mapping too and probably expose this as a script so people can use it right away. I know I probably would for https://github.com/blakeembrey/tslint-config-standard.

@buzinas Any way of finding out what is wrong with travis? Its been running for 3 hours now with node 6.
@blakeembrey You are correct, the native rules don't actually map. Those links are there because we think those closely match the eslint rule. At this point I'm not sure how to go about creating a map though since they may not behave according to the eslint rule. I suppose we could write notes in the rule about the differences.

I'd be happy to take a look at how we can extend it to more closely convert all the rules in an ESLint file, since it's something that'll probably benefit me if we can get it working well. As for Travis, we can just cancel the job and restart it for now.

I was thinking, perhaps we can add another property to IRule to define the map we need to use between the native TSLint and the ESLint rules. Right now it is like this:
interface IRule {
  available: boolean;
  eslintRule: string;
  tslintRule: string;
  category: Category;
  description: string;
  eslintUrl: string;
  tslintUrl?: string;
  provider: Provider;
  usage?: string;  // deprecated: Specify in the rule metadata
  note?: string;   // deprecated: Specify in the rule doc file
}

Perhaps optionsMap:? any and this would define a default map for a given native rule.

Hi,
Looking through the comments and seeing that this hasn't been updated in a few months. Is this still being worked on? Its a really useful feature that I'd love to use! LMK if you would like some help on this.

Hey @apexskier! First of all, sorry for the very very very long delay (more than an year) :(
This idea is awesome! Wow, I have no idea how I missed this. Thanks very much for the insight and also for your contribution.
@davidturissini I have no idea if it's being worked one (I guess not), but I'd love if you wanna chime in, rebase it against latest master and contribute to make it work :)


Project split

Hey,
do you consider splitting what's callled Wangscape now (with Wangscape, WangscapeTest and Wangview "subprojects") into separate projects (tests should stay with a source code, that's clear)?
It may seem counterintuitive for now, but I'm not very confident if adding an another separate application (I mean that GUI application, under "Issues", for options; Wangview is already one) is a good idea. As I see all of them will be linked by options and output format and that's a problem, but it could be resolved with proper versioning (or setting final format of them :wink:).
The big advantage of keeping them together is ease of reusing code between these modules (e.g. codecs and adding Python bindings for Wangview). With separate projects, there should be probably some base to use as submodule for all of them.
What's you opinion on this?

Wangscape already has three different executables, a fourth is proposed, and if the common code is moved to a separate library we'll have five different projects... It's definitely a good idea to split them up.
I think it would be best to host the projects in an organisation account for Wangscape, to make sure the inactive ones don't get buried.

I'm making the organisation now, so this repository's moving to https://github.com/Wangscape/Wangscape.

Nice, that's what I thought about :smile:.

Wangview was already moved to a separate repository and for now the only thing that could be done in this issue is renaming Wangscape to src and WangscapeTest to test/tst... but that's not a part of "split".

for now: metaoutput has become a library and it could be moved to another repository as well, cause it will be most likely needed in the Qt tool for options generation; we will see
could: it's just a quite common convention; I leave this decision to @serin-delaunay

I think renaming to src and test should be done soon (after #50 is merged).
The Qt tool for options generation should eventually be able to generate sample tiles, and even invoke the tileset generator without needing to use the command line. When that happens, probably metaoutput codecs, options codecs, noise, and tile generation should all be moved into one or more library repositories. Then Wangscape would be quite a thin wrapper, just calling library methods in order.
I don't think that needs to be done immediately, though; we can move features into libraries when the Qt tool needs them.


OpenVPN: expose NBDD servers option and fix gui bugs

[x] Redmine Issue: https://redmine.pfsense.org/issues/13085
[x] Ready for review

I left the white spaces as they are and force pushed for a cleaner code to review
Again, the last two are optional as described in the redmine issue

@jim-p
is the first commit fine at least ? Or you want to only expose NBDD server options without fixing the current WINS servers GUI bug neither the CSC page bug ?
The last one in CSC is really annoying because we end up with a situation where it is impossible to say if the settings will be saved or not. At some time, the NTP server check box is enabled while the server field is hidden !
I can only expose NBDD and keep all current GUI bugs if you prefer, or just remove the last two commits

I removed the two last commits to limit the scope
@jim-p
is the first commit fine at least ? Or you want to only expose NBDD server options without fixing the current WINS servers GUI bug neither the CSC page bug (the changes are really limited in first commit to only what exists elsewhere in code)?
The last one in CSC is really annoying because we end up with a situation where it is impossible to say if the settings will be saved or not. At some time, the NTP server check box is enabled while the server field is hidden ! Since the GUI options are one close to the other, the changes are identical.
I can only expose NBDD and keep all current GUI bugs if you still prefer

Each bug/feature should be a separate Redmine issue and separate PR.

Ok, I'll close and think at it how to submit the nbdd servers broken because of the depending netbios JS function is broken
So, maybe I will push the other fixes first, and this one depending on them


Remove tools: copy_data, datastore.

As the backup-restore cycle to update staging seems to be easy, there is no need for tools like the two scripts (which will get outdated soon as we do more model changes).

Does this give some datastore tables we can remove?

I meant cloud storage buckets

No, these scripts were working with local files.

Thanks!


Strippy is fast but fat.

Strippy needs to lose weight.
I'm watching it process 2.3gb of log files rn and the main process is using a whopping 13gb and climbing. This is a bit of an issue. This is during the scout-stripper routine so there must be something we can do in there to improve either garbage collection or something further as that is a ridiculous amount of memory to consume.
plz fix

I had a thought that we could output the keylist found from each file to a tmp file rather than leaving it in the job system. Piping it to disk is apparently very fast and it could/should slim down what's kept in memory. We could then remove jobs as they're finished.
Clearing the content variable after scouting should also slim strippy down. That might be a fix that can go into Milestone1

Okay, so Strippy was getting fat on error messages and I believe that the key-finding bloatage is now fixed with ebc2342cc110bb79da8eb8ea8f5655162192ce68. There was something strange going on with a bad casting error.
Commit 2b3cb4e5106eafe55b173bf4cc4bad94e80481e0 also prevents the manage-job function from starting/running more than $MaxThreads number of processes at a time. Sometimes the progress of a process would become -1 and that wouldn't register with the collecting program.

https://github.com/cavejay/Strippy/commit/5728d14df1609066b1d21bb69edc339dafeeb5a8 also fixed a memory issue that was caused by using the older, regex based -replace function rather than the newer (.NET?) .replace function

From using strippy with these changes in place on site I can confirm that Strippy runs much slimmer now. This ticket can be considered resolved


docker-compose initial run Error

After generating project with cookiecutter when I run
docker-compose up -d
I am getting this error:
`ERROR:
Can't find a suitable configuration file in this directory or any
parent. Are you in the right directory?
    Supported filenames: docker-compose.yml, docker-compose.yaml`

Project folder looks like this: https://github.com/Rigel772/fastapi-test
There is no docker-compose.yml file...
What am I doing wrong?
Thanks

I have run cookiecutter again and it generated docker-compose file this time :)

Thanks for reporting back and closing the issue! :+1:


tf.keras.backend.temporal_padding crashes(bad_alloc) when padding is large

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 18.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below):2.1.0
Python version:3.7.6
Bazel version (if compiling from source):N/A
GCC/Compiler version (if compiling from source):N/A
CUDA/cuDNN version:N/A
GPU model and memory:N/A

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with:

TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"

Describe the current behavior
tf.keras.backend.temporal_padding crashes(abort, bad_alloc) when padding is large
Describe the expected behavior
Expect no crashes
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.

import tensorflow as tf
tf.keras.backend.temporal_padding(x=tf.ones((2,1,1)), padding=(6400000000000000000,<PHONE_NUMBER>000000000))

Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.
In TF2.1
  what():  std::bad_alloc
Aborted (core dumped)

In TF nightly
2020-08-13 01:04:13.669045: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
2020-08-13 01:04:13.683160: F tensorflow/core/framework/tensor_shape.cc:345] Check failed: size >= 0 (-7732434073709551615 vs. 0)
Aborted (core dumped)

Was able to reproduce the issue with TF v2.1, TF v2.3 and TF-nightly.
Session crashes on running the tf.keras.backend.temporal_padding line. Please find the gist of it here.

This is expected, since TF is trying to allocate the memory for a huge tensor with shape (2,<PHONE_NUMBER>000000000 + 1 +<PHONE_NUMBER>000000000, 1), and it will certainly OOM.
I am closing this issue since I don't think it is working as intended. Feel free to reopen if you feel otherwise.


Added option to verify ssl or not

Added option to verify ssl or not. This can be usefull for testing purposes. As it has proven to be usefull to me :D

I honestly don’t use Cpanel anymore. Switched to Kubernetes with a custom made dashboard.
So I really don’t remember what this was about and I’ll close it


Update README.md

Edge extension Url added.

This is right but if its also on chrome please add it its what I use

I'll publish it on Chrome and Firefox very soon. 🧑💻


is there a typings for this to be used in Angular 2?

I have converted this into an angular service for my own purposes but it would be great if there was a typings file for your tool.
Here's a link to my service: https://gist.github.com/tylerlindell/130586743d41fede94c464f0b66a7126
it only generates one random color at a time but it does the job for what I need right now

https://www.npmjs.com/package/@types/randomcolor ?

@tylerlindell thank you so much for that service script!

@SmallhillCZ that looks promising, have you tested it?

@suparnavg you got it sir!

No in the end I just used the service.

Closing for now. Please direct these inquiries to DefinitelyTyped. I don't consider this the responsibility of randomColor.


add more description

Codecov Report

Merging #39 into develop will not change coverage.
The diff coverage is 0%.

@@          Coverage Diff           @@
##           develop    #39   +/-   ##
======================================
  Coverage        0%     0%
======================================
  Files          131    133    +2
  Lines         5787   5831   +44
  Branches       569    574    +5
======================================
- Misses        5787   5831   +44

Impacted Files
Coverage Δ

...2d/dmsexplorer/domain/entity/CdsContentEntity.java
0% <0%> (ø)
:arrow_up:

...ava/net/mm2d/dmsexplorer/domain/AppRepository.java
0% <0%> (ø)
:arrow_up:

...m2d/dmsexplorer/domain/formatter/CdsFormatter.java
0% <0%> (ø)

...sexplorer/view/adapter/ContentPropertyAdapter.java
0% <0%> (ø)
:arrow_up:

...n/java/net/mm2d/dmsexplorer/util/StringJoiner.java
0% <0%> (ø)

Continue to review full report at Codecov.

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


Remove unnecessary HTTP related dependencies

There are a number of HTTP transport, Netty etc. related dependencies defined in various Gradle files across the project. Need to check these through and remove any of the stuff that aren't required.

We are closing this issue due to inactivity. If you need further assistance or have additional input, feel free to reopen it. Thank you for helping us maintain a relevant and focused issue list!


fixes #65

Catch mouse click outside DatetimePicker to close it only if DatetimePicker is open.

looks like travis-ci has some problems in configuration


Packaging of the release nl-NL 09.10.01 is incorrect

The install pack is not correct. The following error on install:
Failure File specified in the dnn could not be found in the zip file: - ...\Website\Install\Temp\1j5fhcnr\DesktopModules\Admin\ModuleCreator\App_LocalResources\CreateModule.ascx.nl-NL.resx
Failure File specified in the dnn could not be found in the zip file: - ...\Website\Install\Temp\1j5fhcnr\DesktopModules\Admin\ModuleCreator\App_LocalResources\ViewSource.ascx.nl-NL.resx

The translation of ModuleCreator is NOT in the pack (and must not be).
Apparently, the manifest is not generated correctly (automatically, I assumed).
Something wrong that has to be done manually?

Manifest is not generated automagically, so it must be maintained manually.