WIP: Integrate withF and withG context to transactions

Description
The withF and withG generalises resource acquisition and release. The DB transaction is one of those resources. Since we share a DB being used in PK, having these methods would be useful.
Long term, the withF and withG types and utility functions would be extracted into its own package like js-context so it can be shared.
Over time this should replace the DB.transact and DB.withLocks methods, and instead just provide the DB.transaction method.
Downstream packages EFS and PK will need to be updated.
Issues Fixed

Related to https://github.com/MatrixAI/js-polykey/issues/294

Tasks

[ ] 1. ...
[ ] 2. ...
[ ] 3. ...

Final checklist

[ ] Domain specific tests
[ ] Full tests
[ ] Updated inline-comment documentation
[ ] Lint fixed
[ ] Squash and rebased
[ ] Sanity check the final build

In order to allow some streaming based functionality, we have to allow the creation of iterators inside the transaction.
We will preserve the read-committed isolation level, which means we create iterators against the DB inside the transaction, and each iterator then needs to operate against the snapshot and the real DB.
This means our snapshot needs to become an ordered key value structure.
This means we are creating another temporary DB to be the snapshot. However I'm going to first just try with a sublevel.
This would mean that there is a reserved area in the DB where transactions are working against, and this sublevel should never be used by any other places.

The usage of the snapshot sublevel does impact any usage of streaming on the root DB though, because using would iterate over the sublevel snapshots too.
Furthermore we cannot just use snapshot sublevel, we would need to create a new sublevel for each snapshot that is bound to a transaction.
Alternatively we forego using a snapshot level entirely and just use an in-memory ordered map structure, but that is its own can of worms.
Most efficient would be:

Snapshots sublevel with snapshot sublevels keyed to unique transaction IDs
This enables later persistent snapshots too, though not sure if this would be useful. At the very least, snapshot can grow beyond memory size?
This would need the root DB to create a sublevel to actually be used, which is to say, the root db level woudn't be the real root db, but instead something under the root database. We could have data and snapshots as the 2 root sublevels.
Would this impact existing users? I don't think so, it should be fine.

These additional "root" sublevels can be extended to deal with automatic indexing #1 which would then supersede #2.

The https://github.com/Level/abstract-level might be a good foundation for a new DB, which would then still use leveldown "now known as classic-level" as the node underlying database.

I've rolled up a bunch of issues in js-db into larger epic https://github.com/MatrixAI/js-db/issues/11 that would be one big change to DB, that would be breaking relative to EFS and PK. So this PR will focus on just integrating withF and withG and the ability to use iterator inside a transaction. However this may be removing the transact and withLocks method which does break EFS, but that is an easy fix, since EFS doesn't actually use any of the DB locking, so it can just have withF integrated with the resource types.

The DBTransaction now uses transactionDb instead of snapshot. The tran.iterator(['d1', 'd2']) can take DBDomain, this makes our iterator method a bit different from leveldb's iterator method. This is because our tran methods tend to operate from the root, and that's how the get, and put works. Remember that since levels are not using the DB interface, we had to do this.
Furthermore the transactionDb is encrypted because it is on disk.
The iterator method is a bit strange, I need to test what happens when the keys are different between transactionDb and the dataDb it is operating over... And the usage of seek. Further prototyping required.

The changes to DB has impacted some tests.
    ✓ async construction constructs the filesystem state (13 ms)
    ✓ async destruction removes filesystem state (3 ms)
    ✓ async start and stop preserves state (18 ms)
    ✓ async start and stop preserves state without crypto (4 ms)
    ✓ async start and stop requires recreation of db levels (6 ms)
    ✓ creating fresh db (5 ms)
    ✓ get and put and del (11 ms)
    ✓ batch put and del (13 ms)
    ✕ db levels are leveldbs (6 ms)
    ✓ db levels are just ephemeral abstractions (4 ms)
    ✓ db levels are facilitated by key prefixes (12 ms)
    ✓ clearing a db level clears all sublevels (10 ms)
    ✕ lexicographic iteration order (9 ms)
    ✕ lexicographic buffer iteration order (112 ms)
    ✕ lexicographic integer iteration (7 ms)
    ✓ db level lexicographic iteration (10 ms)
    ✓ get and put and del on string and buffer keys (6 ms)
    ✕ streams can be consumed with promises (11 ms)
    ✓ counting sublevels (15 ms)
    ✓ parallelized get and put and del (428 ms)
    ✓ parallelized batch put and del (464 ms)
    ✓ works without crypto (6 ms)

I'm creating Transaction.test.ts now to test different usages of transaction and prototype the iterator usage.

I have a working prototype for the db.
It is able to handle this sort of data:

KEYS
DB
SNAPSHOT
RESULT

a
a = a
a = 1
a = 1

b
b = b

b = b

c

c = 3
c = 3

d
d = d

d = d

e
e = e
e = 5
e = 5

f

f = 6
f = 6

g

h
h = h

h = h

Tests have been done for the transactional iterator.
Now it's time to clean up the tests for the DB.test.ts, and we can start to merge this and apply it to the NodeGraph.

In this PR, we are removing the withLocks and other async-mutex usages.
Having locks in the DB muddles the separation of responsibilities.
It turns out our read-committed transactions doesn't actually need locking at all.
You only need locks if you want to also prevent:

non-repeatable reads
phantom reads
lost-updates

However this all depends on the end-user and their specific situation when using transactions. Sometimes they may use only simple mutexes, in other cases they need to use read/write locks.. etc.
So therefore locking functionality is removed from the DB.
We are however using withF and withG here. And we may import this from: https://github.com/MatrixAI/js-resources

We now have tests for each isolation property:
[nix-shell:~/Projects/js-db]$ npm test -- ./tests/Transaction.test.ts

><EMAIL_ADDRESS>test /home/cmcdragonkai/Projects/js-db
> jest "./tests/Transaction.test.ts"

Determining test suites to run...
GLOBAL SETUP
 PASS  tests/Transaction.test.ts
  Transaction
    ✓ snapshot state is cleared after releasing transactions (34 ms)
    ✓ get, put and del (17 ms)
    ✓ no dirty reads (17 ms)
    ✓ non-repeatable reads (9 ms)
    ✓ phantom reads (11 ms)
    ✓ lost updates (7 ms)
    ✓ iterator with same largest key (16 ms)
    ✓ iterator with same largest key in reverse (15 ms)
    ✓ iterator with snapshot largest key (12 ms)
    ✓ iterator with snapshot largest key in reverse (12 ms)
    ✓ iterator with db largest key (12 ms)
    ✓ iterator with db largest key in reverse (10 ms)
    ✓ iterator with undefined values (20 ms)
    ✓ iterator using seek and next (19 ms)
    ✓ queue success hooks (5 ms)
    ✓ queue failure hooks (7 ms)
    ✓ rollback on error (7 ms)

Test Suites: 1 passed, 1 total
Tests:       17 passed, 17 total
Snapshots:   0 total
Time:        1.003 s, estimated 3 s
Ran all test suites matching /.\/tests\/Transaction.test.ts/i.
GLOBAL TEARDOWN

And matches this table:

The db.db should no longer be used when attempting to access the internal DB at root.
You can use db.dataDb.
However that shouldn't be necessary either.
We now expose:

DB.clear() - use this to clear the dataDb
DB.dump() - use this to dump the dataDb
DB.iterator() - use this to get an iterator on dataDB
DB.count() - use this to count from dataDB

And with that, the DB.test.ts now passes.

One issue is the difference in API between DB and Transaction for some methods like clear, iterator, dump and count.
And the fact that I'm only supporting promise-API, like for iterator. So callback style won't work.

The DBTransaction interface is removed. In place, I'm going to rename Transaction class to DBTransaction.

Rather than using the AbstractIterator, both DB.iterator and DBTransaction.iterator now both return DBIterator. This will be used as a stopgap until #11 is done.
The APIs between DB and DBTransaction is still different because we want to eventually move to where you can just specify a key path instead of directly maintaining particular sublevel objects.
This means later in #11, we should have:
// root iterator at dataDb
DB.iterator(options);
// same
DB.iterator(options, []);
// down level 1
DB.iterator(options, ['level1']);
DB.iterator(options, ['level1', 'level2]);
DBTransaction.iterator(options, ['level1', 'level2']);

DB.count();
DB.count(['level1', 'level2']);
DBTransaction.count();
DBTransaction.count(['level1']);

DB.clear();
DB.clear(['level1']);
DBTransaction.clear(['level1']); // this should be a transactional clear, to do this, we must iterator and then do `db.del`

DB.get('key');
DB.get(['level1', 'key']);
// these are not allowed, or they are equivalent to asking for undefined
DB.get([]);
DB.get();

DB.put('key', 'value');
DB.put(['level1', 'key'], 'value');

DB.del('key');
DB.del(['level1', 'key']);
DBTransaction.del('key');
DBTransaction.del(['level1', 'key']);

Still need to add DBTransaction.clear method to be a transactional clear that iterates over a sublevel and deletes all the entries.

Ok this is ready to merge.


Simplification - Improvement Proposals

One major component of the Haskell backend is the simplifier. It takes care of:

function evaluation
lemma application (simplification rules)
ML reasoning, simplifying predicates to some normalized form
sending predicates to the SMT solver

We'd like to know what users' experiences with the simplifier are and what changes they would like to see.
Any ideas are welcome, so feel free to "think big". For example, I would like to be able to step through the simplification procedure, like a "functional" kore-repl.

I would like to be able to quickly test if a simplification applies to an expression. From a user perspective, being able to click on a subexpression in my configuration, and then write a simplification for it and see if it applies, then being able to go back to the original configuration and see if it applies would be magnificent.
On the backend side I suspect this means being able to:

store a point of execution
inject a new simplification into the set of simplification rules
run the simplifier on a subexpression only
go back to the original configuration with ease
... and switch back and forth in this way

Essentially, being able to inject, manipulate and store points of execution and rules, in a way that is reliable and makes it easy to try things out, roll back, etc.


Error while persisting cache: TransformError

Hi,
i have this issue:
Error while persisting cache: TransformError:
/Users/saro/Projects/openshift/reactNative/node_modules/redux-actions/lib/index.js:
[BABEL] /Users/saro/Projects/openshift/reactNative/node_modules/redux-actions/lib/index.js:
Using removed Babel 5 option:
/Users/saro/Projects/openshift/reactNative/node_modules/redux-actions/.babelrc.stage -
Check out the corresponding stage-x presets http://babeljs.io/docs/plugins/#presets

Any suggestions?

Looks like you are using an older version. Upgrading to 0.9.1 should resolve this bug due to ignoring .babelrc in .npmignore.


Is there a way to change the binding to jump to next token?

Feature Requested
Currently it uses Tab but is it possible to configure it to something else?
I am using this plugin without LuaSnip
Relevant Screenshot
No response
Checklist

[X] The feature would be useful to more users than just me.

No, jumping to the next token is done by your snippet engine, not by nvim-scissors. In fact, this plugin does not create any keybinding for tab.
If you do not Luasnip, it depends on whatever snippet engine plugin you use; I'd check their respective documentation.

That makes sense, thanks!
On Sat, 11 May 2024, 6:23 pm Chris Grieser, @.***>
wrote:

No, jumping to the next token is done by your snippet engine, not by
nvim-scissors. In fact, this plugin does not create any keybinding for tab
.
If you do not Luasnip, it depends on whatever snippet engine plugin you
use; I'd check their respective documentation.
—
Reply to this email directly, view it on GitHub
https://github.com/chrisgrieser/nvim-scissors/issues/13#issuecomment-2105590737,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A64P3EAEDGA4PK5DXN7UCTTZBW2MZAVCNFSM6AAAAABHRVGDYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBVGU4TANZTG4
.
You are receiving this because you authored the thread.Message ID:
@.***>


Exception thrown when trying to open the bottom sheet

Hello @DanKyungu .
I encountered an exception when I was working with the library. I've installed the lib and I create a simple button that had a click event. the click event calls the Application.Current.MainPage.ShowBottomSheet(new DetailsPage(),cornerRadius:10,false);
the DetailsPages is a simple MauiContentPage with a label. but its  throws this exception
Java.Lang.IllegalArgumentException: 'The view is not a child of CoordinatorLayout. How can I solve this issue

Your DetailsPage is a ContentPage or a ContentView ?

It's a contentPage
But i think that i get what's going on
I didn't use ContentView I used ContentPage instead

Maybe it will be good to specify it in the readme

I don't know why but i still get the same exception even with the ContentView

Can you share your sample project?

how to proceed??

Here is the sample https://github.com/Eel2000/MauiAppBottomSheet

Should I update the library??


Sys Info message not updated when you do a change kernel operation

Testing #9435
Not a big issue that I see, but if you launch with a kernel that doesn't have ipykernel and choose to swap to a different kernel that also needs an install the sys info message isn't updated.

In the example above I launched with newEnv2 (has no ipykernel) and choose to swap to newEnv3 (has no ipykernel) while performing the install the sys info message still says connected to newEnv2.

duplicate of https://github.com/microsoft/vscode-jupyter/issues/9454
got a pr in progress that fixes this


SPIKE: refactor router tests to split tests for functionality and configuration

Would it be possible to clarify our unit tests for the router to test:

Custom behaviour / functionality added to the router

beforeEach requiresAuth navigation guard
afterEach page title navigation guard

Routes configuration

Does each route specify the correct requiredAuth value?
Does each route specify the correct page title?
Does each route have the correct path?
Does each route render the correct component?
Does each route have the correct children, etc.?

Router configuration

Is 'history' mode enabled?

@warrensearle has this been superceded?  Can the issue be closed?

Hey @ClaireTroughtonJAC this is still valid so have moved to 'Phase 2' rather than closed.


cannot read properties of undefined (reading 'marker')

with shell integration on macOS with pwsh, run some commands and clear the terminal

, source: vscode-file://vscode-app/Users/meganrogge/Repos/vscode/out/vs/platform/log/common/log.js (221)
[31944:0603/084904.575887:INFO:CONSOLE(231)] "%c  ERR color: #f33 Cannot read properties of undefined (reading 'marker'): TypeError: Cannot read properties of undefined (reading 'marker')
    at e._getKey (vscode-file://vscode-app/Users/meganrogge/Repos/vscode/node_modules/xterm/lib/xterm.js:1:369197)
    at e.delete (vscode-file://vscode-app/Users/meganrogge/Repos/vscode/node_modules/xterm/lib/xterm.js:1:286006)
    at vscode-file://vscode-app/Users/meganrogge/Repos/vscode/node_modules/xterm/lib/xterm.js:1:369972
    at e.fire (vscode-file://vscode-app/Users/meganrogge/Repos/vscode/node_modules/xterm/lib/xterm.js:1:234872)
    at t.dispose (vscode-file://vscode-app/Users/meganrogge/Repos/vscode/node_modules/xterm/lib/xterm.js:1:372512)
    at DecorationAddon.clearDecorations (vscode-file://vscode-app/Users/meganrogge/Repos/vscode/out/vs/workbench/contrib/terminal/browser/xterm/decorationAddon.js:104:34)
    at DecorationAddon._dispose (vscode-file://vscode-app/Users/meganrogge/Repos/vscode/out/vs/workbench/contrib/terminal/browser/xterm/decorationAddon.js:98:18)
    at vscode-file://vscode-app/Users/meganrogge/Repos/vscode/out/vs/workbench/contrib/terminal/browser/xterm/decorationAddon.js:46:69
    at vscode-file://vscode-app/Users/meganrogge/Repos/vscode/out/vs/base/common/lifecycle.js:130:17
    at Object.dispose (vscode-file://vscode-app/Users/meganrogge/Repos/vscode/out/vs/base/common/functional.js:18:25)
    at dispose (vscode-file://vscode-app/Users/meganrogge/Repos/vscode/out/vs/base/common/lifecycle.js:99:27)
    at DisposableStore.clear (vscode-file://vscode-app/Users/meganrogge/Repos/vscode/out/vs/base/common/lifecycle.js:166:17)
    at DisposableStore.dispose (vscode-file://vscode-app/Users/meganrogge/Repos/vscode/out/vs/base/common/lifecycle.js:153:18)
    at DecorationAddon.dispose (vscode-

Still reproduce sometime when close debug task:

Version:
 Version: 1.69.0-insider (Universal)
Commit: 0b3574dcef8f35fec4ee4f83dc958c1f16ef6fce
Date: 2022-07-01T05:16:52.086Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 21.5.0

Line in the screenshot above:
https://github.com/xtermjs/xterm.js/blob/e77a0ec886355d560e7a93fa2b354449694ed668/src/common/services/DecorationService.ts#L22
Triggered from:
https://github.com/xtermjs/xterm.js/blob/e77a0ec886355d560e7a93fa2b354449694ed668/src/common/services/DecorationService.ts#L44

I can stiil occur this issue:

workbench.desktop.main.js:808 TypeError: Cannot read properties of undefined (reading 'marker')
    at e._getKey (DecorationService.ts:22:90)
    at e.delete (SortedList.ts:41:14)
    at DecorationService.ts:44:33
    at e.fire (EventEmitter.ts:55:16)
    at t.dispose (DecorationService.ts:136:21)
    at a.clearDecorations (workbench.desktop.main.js:1713:9965)
    at a._dispose (workbench.desktop.main.js:1713:9707)
    at workbench.desktop.main.js:1713:8035
    at workbench.desktop.main.js:19:30348
    at Object.dispose (workbench.desktop.main.js:11:8937)
    at i (workbench.desktop.main.js:19:30061)
    at l.clear (workbench.desktop.main.js:19:30580)
    at l.dispose (workbench.desktop.main.js:19:30518)
    at a.dispose (workbench.desktop.main.js:19:31119)
    at e._wrappedAddonDispose (AddonManager.ts:53:25)
    at a.t.dispose (AddonManager.ts:33:35)
    at e.dispose (AddonManager.ts:22:32)
    at e.dispose (Terminal.ts:207:24)
    at i (workbench.desktop.main.js:19:30061)
    at Ki.clear (workbench.desktop.main.js:19:30580)
    at Ki.dispose (workbench.desktop.main.js:19:30518)
    at Fi.dispose (workbench.desktop.main.js:3064:793)
    at workbench.desktop.main.js:3170:31736
    at new Promise (<anonymous>)
    at z.safeDisposeTerminal (workbench.desktop.main.js:3170:31700)
    at a.run (workbench.desktop.main.js:3061:68538)
    at handler (workbench.desktop.main.js:697:13150)
    at m.invokeFunction (workbench.desktop.main.js:599:325)
    at m._tryExecuteCommand (workbench.desktop.main.js:1685:3664)
    at m.executeCommand (workbench.desktop.main.js:1685:3021)
    at Io.run (workbench.desktop.main.js:697:12232)
    at k.runAction (workbench.desktop.main.js:82:17056)
    at k.run (workbench.desktop.main.js:82:16959)
    at f.onClick (workbench.desktop.main.js:803:24250)
    at HTMLLIElement.<anonymous> (workbench.desktop.main.js:177:15792)
onDidChangeNotification @ workbench.desktop.main.js:808

@tjx666 can you paste in version info from Help > About?

Version: 1.70.0-insider (Universal)
Commit: 3104db414c8fedcf6e4493f14da7df0b7413853a
Date: 2022-07-08T05:16:29.757Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 21.5.0

@Tyriar

I think this issue should be reopen. This issue occur very often. @Tyriar


Update to newer k3d version

k3d is already at version v5.4.6.
It would be great to update this action with it.

Hi @mowies , thx for comment. Starting from k3d-action v2.1.0 users can explicitly set k3d version via k3d-version input e.g. k3d-version: v5.4.6 otherwise k3d uses default version (currently v5.4.1). However we will set the default to the latest k3d soon.


Bump up the dependency for appCompatVersion to fix ViewModel instance creation crash.

Somehow Lifecycle 2.2.0 version of AppCompatActivity does not have HasDefaultViewModelProviderFactory which is causing issues for all viewModels extending AndroidViewModel.
Some more discussion is here. Apparently, the new version fixes it.

@googlebot I signed it!

This didn't work for me.
I had to explicitly mention the fragment version to 1.2.0 under module build.gradle
   implementation "androidx.fragment:fragment:1.2.0"

@MurshidMac I think appCompat covers it unless you before hand only explicitly had implementation "androidx.fragment:fragment" dependencies in your project. I ran it and checked before making a PR.

Thanks for creating this.
Another PR was merged that bumps all versions. Closing this


mill: 0.9.9 -> 0.10.0-M2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/com-lihaoyi/mill/releases.
meta.description for mill is: "A build tool for Scala, Java and more"
meta.homepage for mill is: "https://www.lihaoyi.com/mill"
meta.changelog for mill is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/mfl1xi1ngbav8r3vwfky0zbcza7j6j6f-mill-0.10.0-M2/bin/.mill-wrapped passed the binary check.

/nix/store/mfl1xi1ngbav8r3vwfky0zbcza7j6j6f-mill-0.10.0-M2/bin/mill passed the binary check.

1 of 2 passed binary check by having a zero exit code.

2 of 2 passed binary check by having the new version present in output.

found 0.10.0-M2 with grep in /nix/store/mfl1xi1ngbav8r3vwfky0zbcza7j6j6f-mill-0.10.0-M2

found 0.10.0-M2 in filename of file in /nix/store/mfl1xi1ngbav8r3vwfky0zbcza7j6j6f-mill-0.10.0-M2

directory tree listing: https://gist.github.com/8d54027a0a8f8d8c4ecc37df598f6120

du listing: https://gist.github.com/c1d17b6783eda81b921cfbbe3e9e1580

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
mill

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mfl1xi1ngbav8r3vwfky0zbcza7j6j6f-mill-0.10.0-M2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A mill https://github.com/r-ryantm/nixpkgs/archive/ec40a0f7b6fc9a50da089eb46e77b411d129b649.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mfl1xi1ngbav8r3vwfky0zbcza7j6j6f-mill-0.10.0-M2
ls -la /nix/store/mfl1xi1ngbav8r3vwfky0zbcza7j6j6f-mill-0.10.0-M2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

mill

Maintainer pings
cc @scalavision for testing.

This is a milestone, I think we should await a proper release.

Requested upstream modify their release metadata in https://github.com/com-lihaoyi/mill/issues/1506

Upstream has modified the release metadata so this can be closed now.


Add discount cases for CC, Klarna, and iDEAL Payment methods

@maf-embraceit please review the pull request.

@saadidrees711 the changes have been reviewed


No property models of calamancy

Hi
I am trying to download the models but the models property doesn't exist, as described in the README
pip install --upgrade calamancy
Collecting calamancy
.........
Installing collected packages: calamancy
Successfully installed calamancy-0.0.1

Then in Python I cannot see an attribute models of calamancy
>>> for model in calamancy.models():
...     print(model)
...
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: module 'calamancy' has no attribute 'models'

>>> dir(calamancy)
['__annotations__', '__builtins__', '__cached__', '__doc__', '__file__', '__loader__', '__name__', '__package__', '__path__', '__spec__', '__version__']

Hi @woodthom2 , I'm still working on the packages as I'm currently waiting for the treebank data from a uni here in the Philippines, so the packages still don't exist (hopefully by August!). Sorry I wasn't able to made that clear in the README. I'll ping you once everything's ready, and I appreciate your interest!
In the meantime, you can replicate the NER model as a spaCy project here. (write-up)

Closing this for now! I have already trained the first few models but I want to run some few benchmarks first. I think we're still on track on the August promise.

Hi @woodthom2 , the first few models have been released now. Feel free to update your calamanCy installation from 0.0.1 to 0.1.0.

Thanks so much!
On Sun, 2 Jul 2023, 05:58 Lj Miranda, @.***> wrote:

Hi @woodthom2 https://github.com/woodthom2 , the first few models have
been released now. Feel free to update your calamanCy installation from
0.0.1 to 0.1.0.
—
Reply to this email directly, view it on GitHub
https://github.com/ljvmiranda921/calamanCy/issues/15#issuecomment-1616371169,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADUBTVNSEOH5HNWNVKBFVODXOD5XNANCNFSM6AAAAAAVN4NFPY
.
You are receiving this because you were mentioned.Message ID:
@.***>


not recognized

Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/install
Operating System: windows
C:\Users\sundarraj.A>dotnet
'dotnet' is not recognized as an internal or external command,
operable program or batch file.

Please close and reopen command prompt windows. The installer updates PATH variables that need to be re-read.

Closing out due to lack of response. Please reopen if you're still having an issue and able to provide more details.


autoplay if the prop changed from false to true

Is it a bugfix ?

Yes
if autoplay = false and after change it to true, the pages will not autoplay. this patch can fix it.

Is it a new feature ?

No ?

Describe what you've done:
call the method autoplay() in componentDidUpdate() when the autoplay prop changed from false to true
How to test it ?
.

This repo dead: https://github.com/leecade/react-native-swiper/issues/713

#1002  fixed


Base64 Image not rendering in Image component and container background property.

Describe the bug
The Base64 property is not functioning when applied to the image component. Additionally, the image does not appear when the Base64 code is used in the container's background property.
To Reproduce
Steps to reproduce the behavior:

. Go to  https://function-adminportal-test.shesha.dev/dynamic/TestModule/Backgroud
Open the designer
On the image component, change the image source type to Base64
Paste a base64 image code  on  " Base 64 content"

Actual Results
The image is not pulled. ( it shows the picture loading failure icon )
Expected behavior
Image must be pulled using base64 properties
Screenshots

To Reproduce
Steps to reproduce the behavior:

Go to 'https://function-adminportal-test.shesha.dev/dynamic/TestModule/member-1023'
Drill down to the details view.
Click the radio button labeled  yellow

Actual Results
Images using the base 64 property are not pulled  / not displayed. ( it shows the picture loading failure icon )
Expected behavior
The Base64 Image Source Type pulls the 3 images.
Screenshots

Related Item #https://github.com/shesha-io/shesha-framework/issues/1963


Take slow path on parse errors

Motivation
Fixes #1554; we were incorrectly taking the fast path on syntax error when we should have been taking the slow path.
Test plan

See included automated tests. Added two LSP test traces: one with no syntax error, one with.

@jvilk-stripe I don't think I'll have time to properly review this. Please take over!


When searching for a city getting return as Altstadt

Section 5 Lecture 62, about 4:50 min into it when I do a search for any city I get Altstadt. I have registered the with openweathermap.org and I have my api key.

How did you solve the problem ?? I've the same

Make sure index.js in actions/ has this
const ROOT_URL = http://api.openweathermap.org/data/2.5/forecast?appid=${API_KEY};

Yes, It was solved, thanks =)

The url needs to be "http" not "https". I had to spend some minutes trying to figure out every time openweatherapi was returning the same result.
Thanks, Antoskin


Stop Disabling root access

Connecting directly as root is considered bad practice.
Connect as standard user, and use sudo to run individual commands as root, or su to switch to root.


No Match for Platform - running on a M1 Apple Chip

Hi, Thanks for providing this resource...
When I try to run the following:
docker pull minus34/gnafloader:latest
I get the following ....
What's next:
    View a summary of image vulnerabilities and recommendations → docker scout quickview minus34/gnafloader:latest
Error response from daemon: no match for platform in manifest: not found

When I run the following:
docker scout quickview minus34/gnafloader:latest
I get the following:
    ✗ Pull failed
ERROR   Status: failed to get image minus34/gnafloader:latest: failed to pull image minus34/gnafloader:latest: no child with platform linux/arm64 in index minus34/gnafloader:latest, Code: 1

What are my options around this?
I am considering building the database on a docker image directly, however I have serious misgivings regarding of my lack of docker and Postgres experience. ;)
Appreciate some guidance.
Thanks in advance!

Hi @PeerLabs, try adding --platform linux/amd64 to your pull command. That should work.
FYI - I've got linux/arm64 support for the Docker container in my backlog. Unfortunately, the current Dockerfile has a build that doesn't work with ARM64, so it'll require some major rework to support both AMD64 and ARM64 natively.


STOP UPDATING

More updations, more pains!!!

@creatist
Please provide details about what platform you are using (operating system, architecture). Also include your TensorFlow version.
Make sure you also include the code snippet to reproduce the issue. If you are unclear what to include see the issue template displayed in the Github new issue template.Thanks!

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


[BEAM-13828] Fix stale bot

Right now stale bot is not running correctly - it looks like it stopped working around a year ago (last pr I could find with stale bot activity). I'm guessing this was unintentional and caused by probot not being supported anymore, just like the pr labeler (see https://issues.apache.org/jira/browse/BEAM-13779)
As a consequence of this breakage, we have a lot of stale prs that have been around for a while. As of the writing of this issue, we have 218 prs in the repo, with 129 older than 60 days old (59% stale assuming these don't have more recent activity). This makes the repo feel less active and makes it harder to see the legitimate PRs that have fallen through the cracks. This fixes the problem by adding the GitHub stale action

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

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

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

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @kennknowles
This is extremely similar to https://github.com/apache/beam/pull/16665 which you reviewed before - another broken probot configuration that needs to be replaced by actions. I copied all the config options just as they were in the previous setup


Resend Client Token

When I initialize the shadow of the device, the SDK creates a default client token, however, as this client token does not change with each request, it is not sent when I perform a "PerformUpdateAsync", how can I force the client token to be sent?
Thanks!

Hi @YeisonCL ,
Thank you for your interest in AWS IoT!
If I understand you correctly, you want the client token to be sent in every PerformUpdateAsync request? Would this have to be sent in every request even if there is no other difference in the rest of the shadow json?
Also could you please explain what your use case is and why you need the client token to be sent in every update (if you don't have to divulge any proprietary information that is)?
Please let us know if you have any more questions.
Thanks!
Varun

Hi @YeisonCL ,
We haven't heard from you in over a week so we are closing this issue. Please feel free to open a new issue if you have any questions about the C++ SDK.
Thanks!
Varun


test(list): add characterization tests for list

also adds builder methods on list state to make it easy to construct
a list state with selected and offset as a one-liner. Uses with_ as
the prefix for these methods as the selected method currently acts as
a getter rather than a builder.
cargo tarpaulin suggests only two lines are not covered (the two
match patterns of the self.start_corner match 223 and 227).
the body of these lines is covered, so this is probably 100%

Contextually, this PR is about putting in place some tests for the list widget so that we can easily refactor some of the complexity of the methods to be easy to read and maintain.
Note: this sits on #161 which is not yet merged, so ignore the changes to buffer / sparkline for now.

Would you mind rebasing against main now that #161 is merged? Nothing in here is objectionable, just not sure what's different from main now.

Would you mind rebasing against main now that #161 is merged? Nothing in here is objectionable, just not sure what's different from main now.

Done


fix link to examples

We should think about moving the examples to the pytket repo, this is not a good placed for them. We still should fix the link issue for now.

And I have changed the link to pointing to the main branch, which avoids this kind of issues.


github.com/klauspost/compress for snappy

Hey there!
I noticed that this library doesn't use the snappy library from klauspost/compress, but it does import this library for zstd.
A cursory look makes it appear to be faster. Is there a reason why you aren't using it? Is it worth a PR?

Hi, I'm not as familiar with snappy compared to lz4 and zstd. I'd be happy to switch if you benchmarked and found @klauspost's implementation faster though.

It can either be faster or compresses more and sometimes both.
https://github.com/klauspost/compress/tree/master/s2#snappy-compatibility
Replace snappylib "github.com/golang/snappy" -> github.com/klauspost/compress/s2. If you don't want options snappylib github.com/klauspost/compress/snappy.
	c.poolCompressor.New = func() interface{} {
		w := s2.NewWriter(ioutil.Discard, s2.WriterSnappyCompat())
		return &writer{Writer: w, pool: &c.poolCompressor}
	}

Options to consider: WriterBetterCompression gives better compression. WriterConcurrency(1) if you want to disable multithreaded compression.
	if !inPool {
		newR := s2.NewReader(r, s2.ReaderMaxBlockSize(64<<10))
		return &reader{Reader: newR, pool: &c.poolDecompressor}, nil
	}

Yeah, adding it as a separate option would be nice (and trivial)
FWIW here is a comparison of different types: https://twitter.com/sh0dan/status/1532298056082804736

@mostynb You can do that either way. It does not keep goroutines active.

OK, it's just that the s2.NewWriter docs say that resources might not be released if Close isn't called (as would happen with sync.Pool):

Users must call Close to guarantee all data has been forwarded to the underlying io.Writer and that resources are released. They may also call Flush zero or more times before calling Close.

@jzelinskie: I created a PR which you can experiment with if you like: #12.


Fix ics and url generation when alternate date format is used

This fixes #31 .
Also adds testing with another event fixture.

Coverage increased (+1.4%) to 97.222% when pulling cebf106e19274d22248f96bd8b72a75762a27733 on bignall:ics-fix into cbe2b469aa48dc611a5f58504628b0366f6fa81c on jshor:master.


feat(build): supports cleanup of rpm/deb residual files after uninstall

Summary
when installing Kong via rpm/deb and then uninstalling it, there may be residual files and directories left in the system from the installation. The current commit supports cleaning up these leftover files through postremove.

Checklist

[x] The Pull Request has tests
[x] A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Full changelog

add postremove to perform clean-up after uninstallation
add CI step and test cases

Issue reference

Fix: FTI-5553

@tzssangglass let's not use script to automatically remove them at uninstall. Instead, mark those folders as conffiles in the package, those files will be kept when user uses apt-get remove but will be removed when user uses apt-get purge.

conffiles

let's not use script to automatically remove them at uninstall. Instead, mark those folders as conffiles in the package, those files will be kept when user uses apt-get remove but will be removed when user uses apt-get purge.

I tried it quickly and it works, but there are some edge cases to consider, such as folders that still exist after purging. However, I feel that using conffiles for this purpose is a bit strange. Is there any benefit to doing so?

@tzssangglass this is the standard way for package maintainers to declare files created during runtime or would be modified by user, so that 1) it will only get removed when user choose to, 2) doesn't overwrite modified files on a package upgrade.

such as folders that still exist after purging.

Yes, if there're extra files that are not declared as conffiles but the directory is, then the directory is kept to keep the untracked file.


Temporary commit.

Remember the comment expanded/collapsed state when scrolling. Previously,
the state was remembered inside the Node composable. When the users scroll,
and Node re-composes, the state was being reset.
In this commit, we add the collapsed state into the CommentNode. This makes
sure that the state is retained even when the UI is re-composed.
Closes #651

I think the general approach looks reasonable, but it really needs to be able to live inside the top-level CommentsPage composable and not leak mutable mutable state belonging to that screen into the CommentNode file.

I think this current version works pretty well, but the scroll position goes completely out of whack when collapsing a comment. Go to any post with a comment tree that has 4-5 nested items and try to collapse the topmost parent, you get scrolled way up far away from where you started.
I don't have a surefire solution at the moment, triggering a delayed scroll back to the comment which was collapsed might be worth looking into but I'm not sure if it's possible.

I think this current version works pretty well, but the scroll position goes completely out of whack when collapsing a comment. Go to any post with a comment tree that has 4-5 nested items and try to collapse the topmost parent, you get scrolled way up far away from where you started.
I don't have a surefire solution at the moment, triggering a delayed scroll back to the comment which was collapsed might be worth looking into but I'm not sure if it's possible.

Yeah i see that. Should be good with AnimatedVisibility.

Oh can you update the title? If not then I'll do it tomorrow

I found a bug while testing, with these changes I can only collapse the topmost comments and not ones under them which works correctly on the main branch. Can you take a look?

I found a bug while testing, with these changes I can only collapse the topmost comments and not ones under them which works correctly on the main branch. Can you take a look?

Yeah i found the issue. Because when updating the expanded/collapsed state I only do it in the parent. I will have to check for the shortId in the children as well. See the updateListNode function.

I found a bug while testing, with these changes I can only collapse the topmost comments and not ones under them which works correctly on the main branch. Can you take a look?

Yeah i found the issue. Because when updating the expanded/collapsed state I only do it in the parent. I will have to check for the shortId in the children as well. See the updateListNode function.

Do you wanna try to fix that? If not I can merge this as-is and fix it later myself.

I found a bug while testing, with these changes I can only collapse the topmost comments and not ones under them which works correctly on the main branch. Can you take a look?

Yeah i found the issue. Because when updating the expanded/collapsed state I only do it in the parent. I will have to check for the shortId in the children as well. See the updateListNode function.

Do you wanna try to fix that? If not I can merge this as-is and fix it later myself.

Yeah maybe a different MR all together. I'm not getting any elegant solution at the moment :P


TypeChecker not Running on Repl

Doesn't type check expressions from the repl, but does typecheck the program.

fixed at some point.


Add functions to scrap all followers, following

We already have getPaginateFollowers/ getPaginateFollowing but we can't scrap all followers/following with them.
https://github.com/postaddictme/instagram-php-scraper/blob/master/src/InstagramScraper/Instagram.php#L1302
public function getPaginateFollowers($accountId, $count = 20, $pageSize = 20, $delayed = true, $nextPage = '')
{
    //
}

https://github.com/postaddictme/instagram-php-scraper/blob/master/src/InstagramScraper/Instagram.php#L1400
public function getPaginateFollowing($accountId, $count = 20, $pageSize = 20, $delayed = true, $nextPage = '')
{
    //
}

For these two functions, we must pass $count argument (the total number of followers we need to retrieve)
So i added functions to scrap all followers/following:

Followers: getPaginateAllFollowers
Following: getPaginateAllFollowing

Sorry if I misunderstand, but can't we already achieve this with getPaginateFollowers?

Exactly! We can't do it with getPaginateFollowers
https://github.com/postaddictme/instagram-php-scraper/blob/master/src/InstagramScraper/Instagram.php#L1302
Please see it:
public function getPaginateFollowers($accountId, $count = 20, $pageSize = 20, $delayed = true, $nextPage = '')
{
    // code here
}

For getPaginateFollowers, we must pass $count argument (the total number of followers we need to retrieve).

@congkv thanks for contribution


Update the Image links

Summary

The links earlier provided for the images were not accessible. Updated all the images' links so that they are now visible to the user.
Ticket Link

Hello @atishaye,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

@cwarnermm, @justinegeffen If the provided solution fixes the respective issue, then could you please merge this commit?

Yes, they are working perfectly.

Thanks @atishaye, for confirming that the images are working for you! Feel free to close this PR.


Multiple GPUs slower than single GPU

I am training keras-yolo3 with COCO and I find that the speed of using multiple GPUs is much slower than using one.
Enviroments:
tensorflow-gpu==1.8.0
Keras==2.1.6
Below are my results:

GPUs
Epochs
Interations/epoch
Batch size
Time

1
3
80
8
7m

2
3
40
16
14m

4
3
20
32
18m

Can anyone give me some advice?

I too am facing the same problem. Can someone please help?
Thanks!

Most likely because the CPU is the bottleneck, and by increasing the number of GPU you just ask the CPU to do even more data generation.
Check your bottleneck and there is no use adding more GPU if your CPU can't keep up.
Change the PIL image manipulation with OpenCV and add threading in the batch generation.


[All Versions] Performance issue when combining combining text and graphics within the same container

When adding a Graphic and Text object to the same container performance is MASSIVELY effected.
Testing on an iPad Mini I'm able to get only 60 elements when combining in the same container but 1200 when placing in separate containers. There also seems to be an issue if the Text and Graphics are different containers but share a parent but I didn't have time to make a test for this.
The issue only appears to happen when using WebGL. I've also tested on a selection of iOS and Android devices and get similar results. It's not as noticeable on Desktop.
http://jsfiddle.net/shinybob/5486u6ps/32/

I have also tested against the latest RC and the issue is still present.

This is due to the way pixi renders stuff. in the second slower example you are forcing pixi to switch render states as it draws text -> graphics -> text -> graphics..
In the faster example pixi is batching the calls text -> text -> text -> text... graphics->graphics->graphics..
Pixi is at its fastest when it can batch sprites. It can achieve this when elements that are next to each other in a container are the same type of object. Further optimisation can be found by using spriteSheets and making multiple objects use the same texture.
Hope this helps! thanks!

Just thought I'd clarify that when I say Graphic I mean the PIXI.Graphic object and not a preloaded image or sprite sheet. If I load a image (individual texture or sprite sheet) I do not notice the issue.
I did find that by setting cacheAsBitmap to true on the graphics object it solves the performance issue. However, if the object is set to be interactive, the hit area behaves erratically, normally being reset to the top left of the screen. This issue appears in V2 but seems to be fixed in V3 so I didn't raise an issue.


[$500] Required label in push row should be removed if value is present

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.42-1
Reproducible in staging?: y
Reproducible in production?: y
Issue reported by: @shawnborton
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1708010208553859
Action Performed:
You need to have a workspace that required categories and tags

go to workspace chat
Click + and request money
Go to Manual
Add amount
Click continue
Add a category and a tag

Expected Result:
"Required" shouldn't appear on the category, tag, or merchant fields if already a value present. Note the required label isn't showing on the merchant field in the screenshot below because the PR to add that was just merged and I pulled the screenshot from stagign
Actual Result:
The required label persists even after the value is there.
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~012f130f43465b030a
Upwork Job ID:<PHONE_NUMBER>555239424
Last Price Increase: 2024-02-15
Automatic offers:

aimane-chnaif | Reviewer | 0
Pujan92 | Contributor | 0

Proposal
Please re-state the problem that we are trying to solve in this issue.
Required label shows even though the value is present for the push row
What is the root cause of that problem?
At the moment we do not have any condition to not show the required label when the value for the push item is present.
What changes do you think we should make in order to solve the problem?
I can see we used rightLabel only for showing the required value for the MenuItems, so to generic solution we can consider the title value to prevent rendering the rightLabel.
!title && !!rightLabel

https://github.com/Expensify/App/blob/2fe384c5a2279d65f083d828f825dc9368a3f2ef/src/components/MenuItem.tsx#L605-L609

Result
https://github.com/Expensify/App/assets/14358475/18f7f517-3a84-466c-9221-5c63ba5b8f91

@aimane-chnaif @cead22 I have updated my proposal, Can you plz give a look at it as I think it helps to reduce the conditions and be more generic.

Ok, I thought it makes sense to add it as it defines the intended behavior. Bcoz for right side content we already have rightComponent prop.

I like @Pujan92 's proposal better because all the required labels work the same today in that if there's a value to display (title) in the menu item, we shouldn't show the required label. This is kinda similar to the approach that we took in this issue https://github.com/Expensify/App/issues/35843#issuecomment-1944591292, where the component has all the logic it needs to decide whether to display something or not, and therefore, the logic should be inside the component and not outside of it (like with !iouCategory && isCategoryRequired ? translate('common.required') : '')
We wouldn't be introducing a new prop, we'd be replacing rightLabel with showRequiredLabel.
If we want to keep the change a bit smaller, and keep the ability of putting something other than Required on the right label, we can keep the rightLabel as is, and do something like this on MenuItem.tsx
{!title &&  (
    <View style={styles.justifyContentCenter}>
        <Text style={styles.rightLabelMenuItem}>{rightLabel}</Text>
    </View>
)}

@aimane-chnaif @cead22 To confirm, do we need to proceed by updating the prop to showRequiredLabel or keep the rightLabel and use title value to render?

Yeah. Let's keep the rightLabel and use title value to render?

Thanks, PR is ready for review!

This on the payment stage, so not overdue

Was ooo, handling now

All paid up

@aimane-chnaif @Pujan92 could you confirm if we need a regression test?


remove preview tags for enterprise tier GA

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

will update the version in #4844


Implement Pause menu.

Currently the players mouse isn't being caught and can easily escape. However, caging the mouse inside of the window is super annoying as well, since you can't easily escape the window anymore.
A pause menu would fix such issues, when in paused state, the mouse caging would be disabled, when the game gets resumed, it would enable again.

[x] Simple pausing screen that stops scene processing
[ ] Switching between mouse confinement and no mouse confinement
[ ] Add menu items

[ ] Resume
[ ] Exit

https://github.com/Bios-Marcel/top-down-pew-pew/pull/14


[Task]: Fix error the mnemonic was already stored during migration

Task description
During migration, after the protect view (before migrating), when we call await asyncStoreMnemonic(m) the get the error:
message: "`the mnemonic was already stored`"
time:<PHONE_NUMBER>221
type: "StrongholdError"

Requirements
Error doesnt appear anymore
Creation checklist

[ ] I have assigned this task to the correct people
[X] I have added the most appropriate labels
[X] I have linked the correct milestone and/or project

moved to backlog as I dont experience it anymore

moved to backlog as I dont experience it anymore


Json value with redux-form?

I have a requirement for a field that is plain JSON.
I can use a textarea for input, and use this as a component but as a result I get a string value.
In the documentation I found "normalize" as a way to change the value afterwards.
It kind of does what I want but now I have another problem:
If I change the value of a field normalize changes my value and the textarea updates which causes my text cursor to jump to the end.
--> Is there a way to do normalize but only in the background? I want to store the value like it is after normalize but not see the result immediately.
Thanks for building redux-form, it's a great library!

Not specific to redux form, the general solution I use is to have shouldComponentUpdate compare the refs.theTextArea.value against the nextProps.value and choose not to update if they are the same.

@huan086 solution is probably the ideal thing to do.
Or, you could provide your field a format function, so you can transform your JSON object back to a string, like this:
<Field name="json" format={value => JSON.stringify(value, null, 2) } parse={value => JSON.parse(value)} />

This would work as long as the user types the JSON the same way the format function formats.
This is not the best thing UX-wise, though.


Action "sold"

Can you add quick reply that sends "sold" to buyer like Mercury trade?

Yeah I will but I just dont know how to implement the UI yet any idea?

Instead of clickable corners you can have multiple rows over the whole square shown on hover. You could fit more actions there.
Or have the square expand on hover. (it should expand up instaed of left or right if you go this route to not mess up position of other squares)
Mercury trade has really good UI for trades in my opinion I just dislike the rest of it and would preffer to use your .NET solution

How about using modify keys for more than 3 actions? Ctrl and/or alt. Then you can keep the UI small and have up to 12 actions (none / c / a / c+a) * 3.

How about some rollout bar with custom buttons for what ever message/action user wants (sold and close, no ty and close, 1 min and party inv etc)

I love you guys <3

How about using modify keys for more than 3 actions? Ctrl and/or alt. Then you can keep the UI small and have up to 12 actions (none / c / a / c+a) * 3.
Edit: + Shift

I like the idea alot

What about this?

@Blekota2k
Vertical rollout ?

Ps: I love you guys <3

it rly doesnt matter where or how the rollout will work since it dosnt need to be compact anymore. you want small ikon, like it is now, when you r maping or boss fighting and dont want whole screen filled with trading ikons, but when you want to trade, you hover over the ikon and some variable list of actions cen pop up. and yes, for example as you showed on the image :)

This feature is in the Release 1.0.2 (CTRL + Click) on the Main action


fix duplicate commandant make error

Breaking

None

Enhancements

None

Bug Fixes

Fixes Issue #2 by capitalizing Carthage in Package.swift

Thank you so much!


Benchmark

Hi
The benchmark of the diary project seem to be a little unusually since it reconfigure ulog every time.
https://github.com/maraisr/diary/blob/0170945748168a5fa4b9b2927371f5d7d20bb3b5/bench/index.ts#L70-L86
ulog() {
    let events: any[] = [];
    ulog.use([
	    {
		    outputs: {
			    custom: {
				    log(...args) {
					    events.push(args);
				    },
			    },
		    },
	    },
    ]);
    const suite = ulog('standard');
    suite.output = 'custom';
    suite.info('info message');
    return events;
}

I think you should make an issue that every log framework owner should write the test by himself.

Benchmark
diary      x 840,954 ops/sec ±1.18% (89 runs sampled)
ulog       x 25,409 ops/sec ±40.24% (10 runs sampled)

As far as i know is the console log call directly mapped on the logger. So it can't be faster than a direct call. I think a good benchmark would be to see

the memory usage of an logger object and the ulog.
the time usage to initialize
the performance to configure an new logger

@Messj1 Yes well he is testing a certain scenario in which he wants to intercept log messages and store them in an array. He is setting up the configuration and then logging a message. And then runs that a whole bunch of times. Now I personally don't think that's a very realistic scenario. In fact I think you will most probably create and configure a custom output only at the very start of the program. It's not an operation I expect to perform hundreds or thousands of times. But hey maybe he has a good reason to test it that way. And yes you are right that by default, all log messages are bound directly to the console methods, or whatever underlying output, introducing the minimum amount of overhead possible. But loglevel does the same and I have also seen benchmarks of libraries claiming to be faster than loglevel.
In any way the guy built a great logging library from what I can see and honestly I'm honored he has mentioned me among all the greats so I got no beef with him.

Was only as a hint. :wink:


Allow workerNodeGroupConfigs to be empty

Issue #, if available:
Description of changes:
For creating single-node cluster

Allow workerNodeGroupConfigs to be empty
Check if control plane taints is empty when there is no worker node
Warn when there is no worker node

Testing (if applicable):

unit-test
Invoke eksa create cluster without workerNodeGroups. Validation pass

2022-09-09T11:26:48.464-0400    V0      Private key saved to single-node/eks-a-id_rsa. Use 'ssh -i single-node/eks-a-id_rsa <username>@<Node-IP-Address>' to login to your cluster node
2022-09-09T11:26:50.968-0400    V0      ✅ Tinkerbell Provider setup is valid
2022-09-09T11:26:50.968-0400    V0      ✅ Validate certificate for registry mirror
2022-09-09T11:26:50.968-0400    V0      ✅ Validate authentication for git provider
2022-09-09T11:26:50.968-0400    V0      ✅ Create preflight validations pass

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Docker renewing certificate(s) on startup even if certificate exists

We are trying to switch a client to use jrcs for certificates so we can use v2 for letsencrypt certificates.
I have a test environment set up using docker-compose since there are big changes to the docker-compose.yml  file.
I was using the staging URL in the YML file but wanted to check to make sure that we could retrieve a "real" certificate for the site and not have to accept a self-signed certificate. (I think that was what the browser needed...)
So I commented out the line "#      ACME_CA_URI: https://acme-staging-v02.api.letsencrypt.org/directory" in the YML file and everything seemed well. The certificate was accepted in the browser no problem.
But we noticed that each time I performed a "docker-compose down" and then a "docker-compose up" it would reload/pull new certificates for the site.
I don't think this should be normal operation as the certificates should already be persistent according to all I have read.
A couple of excerpts that I think might be relevant from the logs:
letsencrypt-proxy    | Info: running acme-companion version v2.1.0-5-g1b01042
nginx-proxy          | WARNING: /etc/nginx/dhparam/dhparam.pem was not found. A pre-generated dhparam.pem will be used for now while a new one
nginx-proxy          | is being generated in the background.  Once the new dhparam.pem is in place, nginx will be reloaded.
...
nginx-proxy          | dockergen.1 | 2021/05/04 17:29:33 Generated '/etc/nginx/conf.d/default.conf' from 4 containers
nginx-proxy          | dockergen.1 | 2021/05/04 17:29:33 Running 'nginx -s reload'
...
letsencrypt-proxy    | Warning: '/etc/acme.sh' does not appear to be a mounted volume.
letsencrypt-proxy    | Info: Custom Diffie-Hellman group found, generation skipped.

My YML file is as follows:
version: "2"

services:

  nginx-proxy:
    image: jwilder/nginx-proxy
    container_name: nginx-proxy
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - /var/run/docker.sock:/tmp/docker.sock:ro
      - letsencrypt-certs:/etc/nginx/certs
      - letsencrypt-vhost-d:/etc/nginx/vhost.d
      - letsencrypt-html:/usr/share/nginx/html

  letsencrypt-proxy:
    image: jrcs/letsencrypt-nginx-proxy-companion
    container_name: letsencrypt-proxy
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - letsencrypt-certs:/etc/nginx/certs
      - letsencrypt-vhost-d:/etc/nginx/vhost.d
      - letsencrypt-html:/usr/share/nginx/html
    environment:
#      ACME_CA_URI: https://acme-staging-v02.api.letsencrypt.org/directory
      DEFAULT_EMAIL<EMAIL_ADDRESS>      NGINX_PROXY_CONTAINER: nginx-proxy

  mariadb:
    image: mariadb:latest
    expose:
      - 3306
    volumes:
      - ./logs/mariadb:/var/log/mysql
      - ./mariadb-data:/var/lib/mysql
    restart: unless-stopped
    environment:
      MYSQL_ROOT_PASSWORD: pass
      MYSQL_DATABASE: db
      MYSQL_USER: user
      MYSQL_PASSWORD: pass
    container_name: mariadb

  wordpress:
    depends_on:
      - mariadb
    image: wordpress:latest
    expose:
      - 80
    restart: unless-stopped
    volumes:
      - ./webroot:/var/www/html
      - ./logs/wordpress:/var/log/wordpress
    environment:
      VIRTUAL_HOST: HOST.com
      LETSENCRYPT_HOST: HOST.com
      WORDPRESS_DB_HOST: mariadb:3306
      WORDPRESS_DB_USER: user
      WORDPRESS_DB_NAME: dbname
      WORDPRESS_DB_PASSWORD: dbpass
      WORDPRESS_TABLE_PREFIX: prefix
    container_name: wordpress

networks:
  default:
    external:
      name: nginx-proxy

volumes:
  letsencrypt-certs:
  letsencrypt-vhost-d:
  letsencrypt-html:

Is it normal behavior to re-fetch certificates on startup?  If it is my concern is that on the production server if we are doing other updates or changes that might require multiple restarts I might run out of quota for certificates and mess up the website for customers as far as certificates go.
According to the 120,000 YML files I have reviewed the certificate(s) should be persistent but that does not seem to be the case.
Any idea what I am missing?
Thanks!

Hi, the front of the README has a warning about this:

Required read if you use the latest version : the v2.0.0 release of this project mark the switch of the ACME client used by the Docker image from simp.le to acme.sh. This switch result in some backward incompatible changes, so please read this issue and the updated docs for more details before updating your image. The single most important change is that the container now requires a volume mounted to /etc/acme.sh in order to persist ACME account keys and SSL certificates. The last tagged version that uses simp_le is v1.13.1.

Also please note that this project's name and DockerHub registry have changed. We are still pushing to jrcs/letsencrypt-nginx-proxy-companion but it's considered legacy, the new registry is nginxproxy/acme-companion.
Lastly, I'd strongly advise against using latest version of any image in production. I'd rather use versioned tags whenever available, and read projects release notes before updating to avoid surprises like this one.

Thank you for your response.
I had read that section but did not really comprehend how to implement it. I followed the links and did not gather any information that was specific enough for me and actually confused me on what I needed to do.
In fact I spent part of the day searching for items pertaining to acme.sh and implementing it in a YML file - which really took me further off course.
But! I finally did realize that what I needed to do was to create a volume in the volumes section of both my letsencrypt-proxy and nginx-proxy containers in the YML containing:
  - letsencrypt-acme:/etc/acme.sh

This was not obvious to me from that snippet. Also there is a link further down in that page that was supposed to be related to persistence. There was no reference information there about needing that volume. So that maybe should be adjusted?
Thanks again for your response.

Thank you for your responses. I was really suffering not knowing what I was doing wrong.


Update aws-core, http-client-spi, ... to 2.17.268

Updates

software.amazon.awssdk:aws-core
software.amazon.awssdk:http-client-spi
software.amazon.awssdk:netty-nio-client

from 2.17.104 to 2.17.268.
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!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #266.


Annotated FieldInfo instance is mutated and reused if using type aliases

Checks

[x ] I added a descriptive title to this issue
[ x] I have searched (google, github) for similar issues and couldn't find anything
[ x] I have read and followed the docs and still think this is a bug

Bug
Output of python -c "import pydantic.utils; print(pydantic.utils.version_info())":
             pydantic version: 1.8.2
            pydantic compiled: False
                 install path: /tmp/tmp.pnuPT7tTpf/lib/python3.9/site-packages/pydantic
               python version: 3.9.6 (default, Jun 30 2021, 10:22:16)  [GCC 11.1.0]
                     platform: Linux-5.13.0-rc7-x86_64-with-glibc2.33
     optional deps. installed: ['devtools', 'typing-extensions']

Working version
from pydantic import BaseModel, constr, Field
from typing import Annotated

class MyModel(BaseModel):
  a: Annotated[str, Field(max_length=3)] = ''
  b: Annotated[str, Field(max_length=3)]

MyModel(a="123", b='123', c='123')
MyModel(a="1234", b='1234', c='1234')  # ValidationError

Failing version:
from pydantic import BaseModel, constr, Field
from typing import Annotated

StrField3 = Annotated[str, Field(max_length=3)]

class MyModel(BaseModel):  # ValueError: `Field` default cannot be set in `Annotated` for 'b'
  a: StrField3 = ''
  b: StrField3

The .default is set to '' on the FieldInfo instance at fields.py:404.
This can be fixed by copying the FieldInfo before mutating it and associating it with ModelField.
from copy import copy
...
class ModelField(Representation):
     ...
    @staticmethod
    def _get_field_info(
        field_name: str, annotation: Any, value: Any, config: Type['BaseConfig']
    ) -> Tuple[FieldInfo, Any]:
          ....
          if field_info is not None:
               field_info = copy(field_info)
               ....

+1 ran into this issue, it's a very valid use case and should be an easy fix

Seems like we are also affected by this issue. Any chance to fix this soon?

@PrettyWood any chance the team can get to this bug soon?

This appears related to #3714.
@Jaakkonen - did you try running the unit tests after changing to a copy of the FieldInfo object? I got some failures so it might be that this mutation is required in other places.
FAILED tests/test_generics.py::test_replace_types - IndexError: tuple index out of range
FAILED tests/test_schema.py::test_unenforced_constraints_schema[kwargs9-type_9] - IndexError: tuple index out of range

Results (36.46s):
    2287 passed
       2 failed
         - tests/test_generics.py:761 test_replace_types
         - tests/test_schema.py:1520 test_unenforced_constraints_schema[kwargs9-type_9]
       7 skipped
make: *** [Makefile:63: test] Error 1

@adriangb any chance you could have a go at a fix? 😄 🙏
I think this is also causing #3714 which in turn in one of the only remaining blockers to v1.9.1.


New documentation: Right Sidebar formatting makes really hard to quickly glance for methods

New documentation makes right-sidebar formatting unusable:

Unnecessary code style for method names.
Arguments added to the list of methods. JS does not support method overloading - this is not needed.
They don't fit on small screens.

Suggestins:

Remove code formatting use default link style.
Remove method arguments.
Remove common prefix, e.g. webFrame.setZoomFactor() vs setZoomFactor.
Here is an example of new doc and old doc:

Hi @oleg-slapdash, thanks for the suggestion! For the time being, I've moved this issue over to the correct repository.


share to social (twitter, fb) & copy to clipboard features

when no repo is being looked at:
Find active forks of a github repo: https://techgaun.github.io/active-forks/index.html

when repo is being looked at:
Active forks of <source_github_url> : https://techgaun.github.io/active-forks/index.html/#techgaun/github-dorks

Hey, can I work on this issue!?

sure @rajgautam-cloud


[1.10.2] setBlockDrops help? (might be a bug)

https://gist.github.com/JAWSAWN/987d7ea8ae1c24be066c7e15b0ebfaeb
Why this is not working?
It supposed to drop 1 oak_seed everytime when mining grass with a philosophers stone, but not other tool.
Also played with setBlockDrops and upon /ch reload ing it, it just doesn't do that its supposed to do. Is there a bug with that or whats wrong with my code?

reloging fixed it


Automatically updated dev build

There might be a lag between feature updates of payu and tagging and releasing a new version of this conda environment. For good reasons we might not want to create a large number of versions which might confuse users as to which to use. Also each environment consumes a not insignificant amount of resources:
$ du -shc /g/data/vk83/apps/payu/1.1
625M    /g/data/vk83/apps/payu/1.1
625M    total
$ find /g/data/vk83/apps/payu/1.1 | wc -l
23745

Once deployed it is difficult to remove a payu version in case it is being actively used.
This creates unnecessary work for developers, or users who want to test new features, as they have to install their own local copy of payu to access bleeding edge features.
One solution is to have a payu/dev module which is updated when there are new versions of payu published on the accessnri conda channel.
The most recent version of payu in the channel can be extracted with conda and jq
$ conda search --override-channels -c accessnri --json payu | jq '.payu[-1].version'
"1.1.2"

This would require polling the anaconda channel.

See https://github.com/ACCESS-NRI/payu-condaenv/issues/7 regarding polling

On reflection maybe we want to make this as bleeding edge as possible. Not waiting for conda publishing (i.e. tagging of versions). Just try and pip install it into a payu/dev environment every night. Could short-circuit by checking for any updates in the last 24 hours and only publishing then, or have it as a push workflow that runs on push to master?

Third thought: we should put this in /g/data/vk83/prerelease/apps/ so users don't mistakenly used it.

or have it as a push workflow that runs on push to master?

Well that won't work @aidanheerdegen because this isn't the payu repo. Duh.

Yeah I think a push workflow on push to master would require storing some secrets on payu-org, as discussed in #7. So cron job that checks for updates in last 24hrs or that can be triggered manually could be the way to go.
So are you thinking of having an existing conda environment and just having an action that logs in gadi, updates a local clone of payu, activates an existing payu/dev environment, then runs pip install on the payu directory?
I think that might need a micromamba/conda install to create and/or activate an environment. Unless we used an conda-pack environment similar to the current payu environments just without the payu package. Then the module files would be the same in that case.
If we go for only updating on new tags, we can include the payu package and the action could just log in gadi and run conda update payu inside the payu/dev environment (if there's an install of micromamba/conda somewhere). Deploying a whole new payu/dev environment similar to the current payu deployments is also an option.

So are you thinking of having an existing conda environment and just having an action that logs in gadi, updates a local clone of payu, activates an existing payu/dev environment, then runs pip install on the payu directory?

Well that is one possibility. It would mean we could have a dev environment that doesn't require pushing tags to the payu-org/payu to build the conda package.

I think that might need a micromamba/conda install to create and/or activate an environment. Unless we used an conda-pack environment similar to the current payu environments just without the payu package. Then the module files would be the same in that case.

We have the option of a static environment (one not generated by a deployment) that we activate and pip install git+git://github.com/payu-org/payu@master, or we could deploy everytime and have the pip install in the env.yaml
https://stackoverflow.com/a/32799944
This is potentially a nice solution, as we could share the rest of the conda env specification with the main deployment to keep them in sync. How we share I'm not quite sure seeing as yaml doesn't support this natively. Possibilities include: using jinja templating and generating the environment files with CI. Sure! Why not!? More CI is always good right?

If we go for only updating on new tags, we can include the payu package and the action could just log in gadi and run conda update payu inside the payu/dev environment (if there's an install of micromamba/conda somewhere). Deploying a whole new payu/dev environment similar to the current payu deployments is also an option.

I like the idea of deploying directly from the master branch on GitHub. It means we can test without tagging a new version. Otherwise we tag just to get it to build a conda package. So we can merge, test, and maybe end up reverting, or doing another PR if we borked something.
It would mean we can merge a fix like https://github.com/payu-org/payu/pull/423 and then ask the user to module load that payu environment and confirm it fixes their issue.

Thanks, I didn't know about pip installing directly from git so that's really good to learn!
Ok, so options are:

Have a static envt, run activate and pip install git+git://github.com/payu-org/payu@master
Use env.yaml for payu/dev deployment but modify it to remove payu and add in the pip install payu from git.
Could use jinja templating for above.
Have a separate env-dev.yml and env-release.yml

Options 2 & 3 would  require a rethink on the deploy trigger for the released environments of payu, which runs when any change to the env.yml file is merged to main. Also for example, say there's some new features in payu's git main branch, so payu/dev requires some new dependencies but that doesn't warrant a re-deployment of payu/1.1. The deploy trigger for release envts of payu could be changed to a manual call that is given the payu version as an input.
Having separate files for env-dev.yml and env.yml, could create an issue for files getting out of sync, but it would allow for testing of changes to env-dev.yml.


fix leaderelection:  release lock when error occour and graceful shot…

What type of PR is this?
/kind bug
What this PR does / why we need it:
release lock when error occour and graceful shotdown
Which issue(s) this PR fixes:
Fixes #278
Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

NONE

/assign @roycaihw

This repo has been merged into the main python repo. We are archiving this repo. Please submit the PR to the main repo. Thanks!
/close


Add Quid Ika Token

Adding Quid Ika Token (ERC20)

website: https://quidverse.com/
etherscan: https://etherscan.io/token/0x9d38f670d15c14716be1f109a4f453e966a2b6d4
coingecko: https://www.coingecko.com/en/coins/quid-ika
telegram: https://t.me/quidika

@MRabenda bump?

Am I still missing something here?

@MRabenda updated

Please remove PNG from PR
Your SVG has ~ 800kb regular one should have < 10 - can you improve it?

Please remove PNG from PR
Your SVG has ~ 800kb regular one should have < 10 - can you improve it?

Done
I am not too familiar with SVGs so I am not able to get it much smaller before starting to lose details on the image. I cut it down to about 50% of the original.

From what I can see on Etherescan and Coinmarket cap Quid Ika has a different icon that this gray used here

From what I can see on Etherescan and Coinmarket cap Quid Ika has a different icon that this gray used here

We have been rebranding. It takes time for CMC and Etherscan to update. Our Telegram, Discord and Dextools all have the new symbol/logo.

@MRabenda let me know if you need more info or need me to prove that this is the new logo for the token

Bump @MRabenda

@MRabenda bump?

How long does it take for this to show up in the app?

@ShailChoksi - QUID token has 18 or 9 decimals https://etherscan.io/address/0x9d38f670d15c14716be1f109a4f453e966a2b6d4#readContract ?


fix cover, highlight syntax for js

Hi @haneenmahd! Nice idea for library

Thanks @jeetis for The Help.


prevent sigpipe

Solves #37 according to this SO post: http://stackoverflow.com/questions/108183/how-to-prevent-sigpipes-or-handle-them-properly
This does not make any breaking changes so it should work as a patch fix.

This fails on Linux. I think this solution in curassow should work pretty well on both platforms: https://github.com/kylef/Curassow/pull/9

Replaced by #44.


Compare and document resource usage (CPU & memory) after engine updates

Acceptance criteria:

For our test set, compare old and new

Runtime
Max memory usage

Summary
Required memory per node: 1,5 GB + 512 MB / CPU core
Performance for 2 x 4 Core Intel Skylake node:

Files / s: 53.7
MB / s: 55.2

Benchmarks

2 Nodes
4 cores (8 threads)
Intel Skylake
12 GB RAM

Ressources used under full load

CPUs: 100% of node
Memory:

per node 4 GB (Scanner)
Once 0,5 GB (Gateway + Redis)

Peak performance

Number of files: 27297
Total size: 28065M
Average file size: 1.03M
Files / s: 53.7
MB / s: 55.2


Show selected entity when opening Component Inspector

The GUI Component Inspector plugin always starts with the World properties shown. If I have an entity selected, then I would like the Component Inspector to open with the properties of the selected entity displayed.

The main problem implementing this is that there's no central place keeping the ground truth about what entities are selected. The 3D scene only knows about the entities with a visual, the entity tree knows about them all but that plugin is optional...
For this reason, we've been purposely deselecting all entities when a plugin that relies on selections to work is loaded. This way we can be sure that all selections are caught by the plugin.
So how about this alternative: adding an item to the entity's context menu saying "Inspect", which loads the inspector for that entity? I think it should accomplish what you're trying to achieve.


Enable the plugin in other types of project

Could the plugin be activated for other types of projects (other than Android)? I'd like to use it for debugging a Cordova applucation.

Hi @Kobzol we need the Android sdk path to be able to use adb from the plugin. If you want to use the plugin you need to configure the android dependency into your IntelliJ installation.


Set the sdk_station_config bssid_set to zero.

See mention in some other esp code that if the bssid_set value is not zero then the bssid must be set. Should the examples be initializing this to zero explicitly?

The C99 standard specifies that if there's an intiializer list for an aggregate type (aggregates include structs) then any non-specified fields are initialized to zero. So this PR doesn't change the compiler output.
That said, there is a bit of a gap around understanding of these structures. I think it would be really useful to have some comments in include/espressif/esp_sta.h explaining what each field should be set to (including details like "bssid_set should be 0 if using SSID, 1 if using bssid").

Thanks. Changed the PR to just add some comments as suggested.


Create the form

Hello. Help please, I need to create the form for editing table data from the
database leveldb

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 31 May 2012 at 4:55

Ask on https://groups.google.com/forum/?fromgroups#!forum/leveldb.  You will
need to provide more info, too.

Original comment by<EMAIL_ADDRESS>on 1 Jun 2012 at 11:53

Changed state: Invalid


Chainquery: Upload baseline SQL database seed to lbryio S3 container.

This will likely have to come as a question to the end user during initial setup to offer the user the ability to download our latest snapshot database checkpoint of the LBRY checkpoint.
This stuff, should we decide to,  would be GPG signed as well as the repository itself.

I need to zip and ship the base SQL seed and then run a sha256 sum on it, then what I'll do rather than downloading the entire blob to my local just GPG sign the seed's hash.

The 14Gb data.zip
sha256sum data.zip
6c456f3c3687fab98b1bb3869578ccae1e5ccfd351f8907b3870d204a21ea82e  data.zip

am I needed for something? can I unassign this from me?

This is mostly ready we just need to debug the mysql configuration issue and then automation can be setup for uploading latest checkpoint data.  This requires time from both @Leopere and @tiger5226

Sounds good! I think we need a bash script here to make sure we upload every x blocks, so the seed doesnt get too far behind. Is that done?

yeah, blocks are 2.5 minutes apart on average so we can backup once a week and that should be fine.


Some cache container doc fixups

Made a tweak while resolving the conflict: instead of

The following example uses the single partition documented above.

I made it

The following example uses the single partition setup documented above.

because the service file is reusing the entire config scheme and not just the partition itself.


[Databricks] Allow users to install python packages at job and task level

This PR adds the ability to define pip packages at both the task group and task level within the DatabricksWorkflowTaskGroup. This new parameter notebook_packages which is exposed at both taskgroup-level and task-level is an array of dictionaries that specify dependency packages to be installed.
The big caveat here is that there is no job-level definition for python packages in the Databricks Jobs API. So the taskgroup-level package definition we offer is applied against all its tasks along with their own corresponding package definitions at the notebook task level.
Below is an example of what the DAG could look like:
dag = DAG(
    dag_id="example_databricks_workflow",
    start_date=datetime(2022, 1, 1),
    schedule_interval=None,
    catchup=False,
    default_args=default_args,
    tags=["example", "async", "databricks"],
)
with dag:
    task_group = DatabricksWorkflowTaskGroup(
        group_id="test_workflow",
        databricks_conn_id=DATABRICKS_CONN_ID,
        job_clusters=job_cluster_spec,
        notebook_params=[],
        notebook_packages=[
            {
                "pypi": {
                    "package": "simplejson==3.18.0",  # Pin specification version of a package like this.
                    "repo": "https://pypi.org/simple",  # You can specify your required Pypi index here.
                }
            },
        ],
    )
    with task_group:
        notebook_1 = DatabricksNotebookOperator(
            task_id="notebook_1",
            databricks_conn_id=DATABRICKS_CONN_ID,
            notebook_path="/Shared/Notebook_1",
            notebook_packages=[{"pypi": {"package": "Faker"}}],
            source="WORKSPACE",
            job_cluster_key="Shared_job_cluster",
        )
        notebook_2 = DatabricksNotebookOperator(
            task_id="notebook_2",
            databricks_conn_id=DATABRICKS_CONN_ID,
            notebook_path="/Shared/Notebook_2",
            source="WORKSPACE",
            job_cluster_key="Shared_job_cluster",
            notebook_params={
                "foo": "bar",
            },
        )
        notebook_1 >> notebook_2

closes: #120

do you mind adding a description showing an example of how to use it?

For the most part this all looks good, but can you please add more description into the PR description. I want to make sure that if we have to look back at this in the future we know exactly what we're looking at.

@dimberman I have updated the description. Please check.


Migrate from environment to clusterName

The graph schema is migrating from environment to clusterName. Update schema, subscription, and code.

Fixed on 59fc2f11f2011c9f5ddcd49f58550bd8a89abfb4


callbacks - adopt a client only solution (#140328)

This PR fixes #140328
I was not really sure about this TODO:
https://github.com/microsoft/vscode/blob/23598a0575bf6cf8e70884804bfc39cc3fea5247/src/vs/code/browser/workbench/workbench.ts#L204-L213
Sample extension code to test this:
vscode.window.registerUriHandler({
	handleUri(uri: vscode.Uri): vscode.ProviderResult<void> {
		if (uri.path === '/did-authenticate') {
			console.log(uri.toString());
		}
	}
});

const callableUri = await vscode.env.asExternalUri(vscode.Uri.parse(`${vscode.env.uriScheme}://<extension id>/did-authenticate`));
await vscode.env.openExternal(callableUri);

The TODO is related to https://github.com/microsoft/vscode/blob/f67a8b753f55e452f38b61497662839c4691fb12/extensions/github-authentication/src/githubServer.ts#L129-L130. @TylerLeonhardt will eventually fix this, I think.

Also I think you fixed my bug maybe? https://github.com/microsoft/vscode-test-web/issues/19 :)

@aeschli needs to comment on that, my change still needs support from the server and I don't know about Martins server implementation.

@TylerLeonhardt I still need to adopt vscode-test-web.
@bpasero Can we put the code that computes the callback uri on the server to the callback.html page? I think @joaomoreno does that.

Yes I will take a look.

Pushed. @joaomoreno @aeschli please review: https://github.com/microsoft/vscode/commit/b1b2bd6c848b72dc2791bf474d50742da941c0ea


Inheritance upgrade / Add more features

Enhancements for the inheritance feature.
This code will add the features for:

Nested schema inheritance
Array Items inheritance
@modelOptions inheritance
Multi-level inheritance

This merge request ist not ready to merge.
There is a bug with the connection options for extended classes.
Please don't merge this into the master at this point.

Solved the bug - was just a configuration problem on our site.

Sure, I will rebase this and make all requested changes tomorrow.
Just a question: Is there any style guide beyond the tslint rules? If I would know the style I could solve the style issues aswell.

Current style "guides":

tsc (npm run build)
tslint (with all the settings, we might migrate over to eslint when it gets better typescript integration)

some rules can sometimes somehow not be applied, or are not existing yet in tslint.json

vscode
CONTRIBUTING

Update to https://github.com/hasezoey/typegoose/pull/21#issuecomment-528139782
in c7c979cbd000057da43e5ec9d0810fc717837905 i added the rule, that was most concerning me in this pr, just run npm lint to see all style-errors and npm lint -- --fix to automaticly fix them

I think we might need to implement the decorator cache in v6, because "i" found the first victim of the issue (@fabioformosa) with https://github.com/fabioformosa/typegoose-validation-error

for what is 7cc628adb1f2ba7350d187dc1e1959fa510dd4f7 necessary?

If you desing a class like this:
class Parent {
  @prop()
  public type: string
}
@modelOptions({
   schemaOptions: {
       discriminatorKey: "type"
   }
})
class Child extends Parent {
   @prop
  public someOther: string
}

if you call getDiscriminatorModelForClass(Child) you will get an  error like "The class can't override the discriminatorKey property"

im confused, i will trust you for now, because i still have to look at #23

Question: what did you do to the commits? (a rebase | a merge?)

Tried to rebase but I think I messed up :D
Will look into this to solve this and get a clean state

I have a clean local state for this branch but I have to figure out why some tests fail.

Found the reason why tests are failing: https://github.com/hasezoey/typegoose/blob/r6/master/src/internal/utils.ts#L165 need the metadata of the class level. Tests should pass after #23  is finished.

im still confused about #23 (& #24), lets see how it will turn out

@B-Stefan could you rebase this pr onto latest r6/master again?

@hasezoey  I merged all pending merge-request on Friday together (only local). It worked as expect.
I will rebase this merge-request as soon as #24 got merged into the r6/master.

@B-Stefan because #24 got merged, could you update this PR?

@hasezoey Thanks for the hint! I will update this PR on Monday

@hasezoey  Thanks for all the work you did!
Most of my code is not necessary anymore or you implemented a similar solution! 👍

could you do some documentation for the "new" discriminator? (because of the new "default" i see on a discriminator porp)

@hasezoey  Do you mean documentation for the test class (https://github.com/typegoose/typegoose/pull/21/files#diff-5ea243b73204be263b19204e1f63a933R7)?
If so I would like to modify the test class to make it more explicit what you can do with this feature.
With this change, we support more complex cases but don't change any current behavior.

@B-Stefan sorry if i was not clear enough, i meant documentation on prop and/or make an advanced guide for this in this folder

i will merge it for now, but if you could, could you do some documentation as described above for discriminator change?


could not broadcast input array from shape (636,732,4) into shape (636,48,4)

hi !
i am trying with
python scripts/sampling/simple_video_sample.py --input_path assets/berry.png --version sv3d_u

but have error (in title):
generative-models/scripts/sampling/simple_video_sample.py", line 155, in sample
    padded_image[
ValueError: could not broadcast input array from shape (636,732,4) into shape (636,48,4)

with test image all OK.
whats wrong ?

same issue here even though I provide an image with resolutions (576, 1024, 3) same as test image. I get broadcasting error

check input, should be rbga images

I got the very same question and still found no reason or workaround.

I've found a workaround, try modifing
            side_len = (                 int(max_size / image_frame_ratio)                 if image_frame_ratio is not None                 else in_w # here             )
to
            side_len = (                 int(max_size / image_frame_ratio)                 if image_frame_ratio is not None                 else max(in_w, in_h) # here             )
，by applying this workaround, the script could avoid wrong segement mask from simple cv2.threshold(                 np.array(image.split()[-1]), 0, 255, cv2.THRESH_BINARY causing array be small incorrectly.
HOWVERE, it's just a workaound which may lead to performance degrading, we may need an elegent fix.

I've found a workaround, try modifing
side_len = ( int(max_size / image_frame_ratio) if image_frame_ratio is not None else in_w )
to
side_len = ( int(max_size / image_frame_ratio) if image_frame_ratio is not None else max(in_w, in_h))
，by applying this workaround, the script could avoid wrong segement mask from simple cv2.threshold( np.array(image.split()[-1]), 0, 255, cv2.THRESH_BINARY causing array be small incorrectly.
HOWEVERE, it's just a workaound which may lead to performance degrading cauz it warns "WARNING: The conditioning frame you provided is not 576x576. This leads to suboptimal performance as model was only trained on 576x576.", thus we may need an elegent fix.

I've found a workaround, try modifing side_len = ( int(max_size / image_frame_ratio) if image_frame_ratio is not None else in_w ) to side_len = ( int(max_size / image_frame_ratio) if image_frame_ratio is not None else max(in_w, in_h)) ，by applying this workaround, the script could avoid wrong segement mask from simple cv2.threshold( np.array(image.split()[-1]), 0, 255, cv2.THRESH_BINARY causing array be small incorrectly.
HOWEVERE, it's just a workaound which may lead to performance degrading cauz it warns "WARNING: The conditioning frame you provided is not 576x576. This leads to suboptimal performance as model was only trained on 576x576.", thus we may need an elegent fix.

it`s working -
https://github.com/Stability-AI/generative-models/assets/29411817/c5ee0831-39bd-4529-9e1f-2853eab3d9ca


Add files via upload

@pmubangizi file/lib/domains/org/peponischool.txt: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@pmubangizi First stage of verification passed, official domain for Peponi School is peponischool.org as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@pmubangizi Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Added Travis configuration file

I built a simple Travis configuration for automatically building and testing clingo with gcc 5.
The configuration is working, as you can verify with the latest commit’s build status on Travis.
The only thing left to do is to connect the potassco/clingo project with Travis and to merge this commit into any branch that should be tested in the future.

Thanks going to merge and see what happens. :)


Very slow stacktraces when using debug: true

I'm using karma with browserify to run my Jasmine tests in PhantomJS.
Here's my test:
var React = require('react/addons');
var _ = require('lodash');

function recursiveFail(n) {
    if (n <= 0) {
        expect(true).toBe(false);
    } else {
        recursiveFail(n-1);
    }
}

it('aaa', function () {
    recursiveFail(100);
});

And here's the relevant part of the Karma config:
    browserify: {
        debug: true, // for meaningful stacktraces
    },

When I run this test, it runs very fast (Karma reports the time of test run, and it is a fraction of second), but then Karma stops before displaying the stacktrace. Total run time is around 20 seconds (measured by time command).
This is the base version. And then:

If I remove the require(...) statements, the total run time drops to 2.5s.
If I change recursiveFail(100); to recursiveFail(1); (without changing anything else), the total run time drops to 6.5s.
If I remove debug: true from the browserify config (without changing anything else), the total run time drops to 5s.

It looks like this specific combination (that is, using multiple modules, using debug: true and having long stack traces), makes the stacktrace generation slow.

:+1:

A few notes on this issue:

Karma translates stacktraces to its sourced version and displays the original file locations next to each stacktrace entry.
The translation takes more time with longer stack traces/bigger source maps.

The behavior you are experiencing can probably be explained as follows:

react/addons is a huge dependency that browserify will attach a huge source map for. Parsing the source map takes time.
Shorter stack trace, less stuff to do.
No source map, nothing to parse


How to get the target ID when dropping a foreign element?

I have jsTree configured like so:
jQuery(document).ready(function(){
var treeMain = jQuery('#folder-tree').jstree({ 'core' :
{
'data' : folders,
},
'force_text' : true,
'themes' : {
'responsive' : false,
'variant' : 'small',
'stripes' : true
},
'types' : {
'default' : { 'icon' : 'folder' }
},
'sort' : function(a, b) {
return this.get_type(a) === this.get_type(b) ? (this.get_text(a) > this.get_text(b) ? 1 : -1) : (this.get_type(a) >= this.get_type(b) ? 1 : -1);
},
'plugins' : [ 'sort','types' ]
});
This code allows an HTML element, which is not a part of the tree, to be dropped into a node:
jQuery('#folder-tree').droppable( {
        accept: 'li a.media-attachment',
        hoverClass: 'droppable-hover',
        drop: handleTreeDropEvent
});

This function will process the drop event:
function handleTreeDropEvent(event, ui ) {
}
What do I do in handleTreeDropEvent to get the ID of the target node of the drop event? Also, is there a better way to define droppable target element? It does not work using the jstree-anchor class.

To check the ID of the element refer to jQuery UI and the droppable documentation - I can not help you with that.
jsTree provides its own way of dropping elements, here is the code: https://groups.google.com/forum/#!topic/jstree/BYppISuCFRE
That does not mean hooking up droppable is not possible, but you need to refer to their docs.
Best regards,
Ivan

The problem with using the DND plugin is that it allows nodes to be moved which I don't want that to happen. Is there a way to totally stop node dragging when DND is in use?

Following Ivan's advice I was able to get the ID of the node:
function handleTreeDropEvent(event, ui ) {
var target = event.target || event.srcElement;
var node_id = $(target).attr("aria-activedescendant");
...
}

To totally stop dragging use the is_draggable callback in dnd settings, and always return false from it.