Fix for verifychain

Fixes #630
See issue for more details.
Changes introduced

New RPC command getcfunddbstatehash covered by functional test cfunddb-statehash.py
New state for payment requests 6 when those are paid.
The payment request parameter paidOnBlock is substituted by stateChangedOnBlock when state is 6
New structure for storing the state history of CFundDB entries. Those are stored in a map associating blockhash and state, allowing to directly revert state transitions when reorganizations are seen.
verifychain now checks for the consistency of the CFundDB state hash when level 4 is specified.

Important
This set of changes will require older clients to reindex on launch, keeping the node offline for some hours at best. In order to reduce downtime, node operators can proceed as follows if needed:

Close node with old version.
mkdir /tmp/reindexdata; cp -rf <data_folder>/blocks /tmp/reindexdata/; cp -rf <data_folder>/chainstate /tmp/reindexdata/
Reopen node with old version. It will be again online
Launch in parallel a second instance of the node, this time using the new version with the parameters -reindex -datadir=/tmp/reindexdata/
Once the reindex finishes, close both nodes and copy back the reindexed data.
rm -rf <data_folder>/blocks <data_folder>/chainstate; cp -rf /tmp/reindexdata/* <data_folder>
Relaunch new version of the node.

What to test

Launch a wallet with an old copy of the blockchain. It should show that the database is corrupted and that reindex is needed. Test both gui and headless
Launch a fully synced wallet and execute verifychain 4 0. This should return true.
Partial runs of verifychain 4 n return true (being n an arbitrary value between 1 and the length of the chain).
Wallet should be able to sync correctly

A new build of 91e731d07c7ffafbd32d4de6581cec8220f5047e has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

A new build of 70a96a75b2be274a233d943b982b763fb27b34d0 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

Tested locally and fixed with @fcc66d1, ready for review

A new build of fcc66d1fdb468ded89dbffe5d0e2017a7afd3771 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

A new build of ceb4a5ea12f90089e9b28b8a8e75a98db0cfc2c6 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

Although verifychain 4 0 is returning true in all my systems, partial runs of the check are returning false in certain conditions. As an explanation of its function, verifychain disconnects the amount of blocks specified in the second parameter, and connects them again. If 0 is specified as second parameter the whole chain is disconnected and reconnected again. Partial runs can be done passing an amount different from 0 (up to the current height).
I've initially found that partial runs were failing in mainnet, but each run of verifychain was taking too long. So I've tried to reproduce this is in a private devnet to get a smaller context which would allow me to test quicker.
Archive.zip
verifychain 4 10 returns false using the above attached chain data. I've chosen 10 randomly, but I was curious to see exactly what was failing, so I wrote a bash script to automate the search.
datadir=/Users/alex/navcoin-core/data
navcli="/Users/alex/navcoin-core/src/navcoin-cli -devnet -datadir=$datadir"

for i in $(seq 1 `$navcli getinfo|jq .blocks`);
do
   verifyoutput=`$navcli verifychain 4 $i`
   if [[ "$verifyoutput" == "false" ]];
   then
       verifyoutput+=`echo ' - ' && echo failed at $(grep 'ERROR: VerifyDB()' $datadir/devnet/debug.log |tail -1|sed 's/.*block at \(\d*\)/\1/')`
   fi
   echo Rewinding to \
   $(bc <<< `$navcli getinfo|jq .blocks`-$i) \
   - reconnecting to `$navcli getinfo|jq .blocks` \
   - verifychain 4 $i $verifyoutput;
done

Running this script would be very useful against a mainnet fully synced node, as it would give us certainty about how well the cfunddb behaves with long reorganizations. But it would take an immense amount of time. How to efficiently run this test in mainnet is an open question. A possible solution would be to run it against an stressed testnet, which could even give a richer context than mainnet (due to an elevated count of injected proposals and payment requests). Any other ideas?
Coming back to the script output, I was able to find it was failing disconnecting down to the following ranges:

Disconnected down to any block in the range
Failed when reconnecting
Reason

330-363
363
IsValidPaymentRequest: Could not find parent proposal dd01134fe270e00b79d6685b4f2b49ba19750227fdad0efeb4b99f2fc1c100d6 for payment request 39c8d0c451bf1b52bce3d60f022f53541d6a51ce4abffa1567c514baf6ab9de5 CProposal(hash=dd01134fe270e00b79d6685b4f2b49ba19750227fdad0efeb4b99f2fc1c100d6, nVersion=2, nAmount=10.000000, available=10.000000, nFee=0.000100, address=mtVZbCiSuBW7pE7zUeFTPscTE1dZd616t1, nDeadline=100000, nVotesYes=0, nVotesNo=0, nVotingCycle=2, fState=pending, strDZeel=test, blockhash=0000000000)

364-419
426
CheckBlock() : cant find payment request block<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000

511-579
579
IsValidPaymentRequest: Could not find parent proposal 5ca639ac2c0da9a47cdfd40a59f2c2ccd2d29a07e969c95131e33cb0ccba5b36 for payment request 860e07e6a36f16f53579cf96ebc9f37bc2841905c055703ebc3e04a3d3f8a0be CProposal(hash=5ca639ac2c0da9a47cdfd40a59f2c2ccd2d29a07e969c95131e33cb0ccba5b36, nVersion=2, nAmount=1.000000, available=1.000000, nFee=0.000100, address=mu39oWSRd1TKa7zsxS52BjHczd4fYwBpuE, nDeadline=100, nVotesYes=0, nVotesNo=0, nVotingCycle=3, fState=pending, strDZeel=test, blockhash=0000000000)

580-629
636
CheckBlock() : cant find payment request block<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000

In devnet, voting cycles last 30 blocks. Blocks cycle from 0 to 29 as in height%30 to determine the position inside of a cycle. The cycle number is determined by int(height/30). Payouts happen in the 7th block of a voting cycle after a payment request has been accepted.
Let's see when there's been votes in the chain:

Entry
Vote
When

Proposal 1
Yes
303-329

Payment request 1
Yes
385-389

Payment request 1
Yes
396-419

Proposal 2
Yes
486-509

Payment request 2
Yes
610-629

Having a closer look at what happened in the critical blocks:

Height
What

329
Proposal 1 is accepted

330
Nothing of interest in the block, voting cycle 11, first block with proposal 1 accepted

363
Payment request 1 is created

364
Nothing of interest besides being the first block of payment request 1

419
Last block of the voting cycle 13, payment request 1 is accepted, proposal 1 expires

426
Payment request 1

509
Proposal 2 is accepted

511
Nothing of interest in the block, voting cycle 17

579
Payment request 2 is created

580
Nothing of interest besides being the first block of payment request 2

629
Last block of the voting cycle  20, payment request 2 is accepted

636
Payout of payment request 2

363 and 579 are both seeing the creation of new payment requests. The creation fails because the parent proposal is not accepted. 426 and 636 see the payouts of the payment requests. Those fail because the node can't validate if the block when the payment request was accepted is in the main chain.
Why?
When we disconnect a block, the state of all the entries which had an update in that block is reseted. This is a wrong design of the cfunddb, because it assumes the entry state will be correctly calculated in the next reorganization, which does not happen all the time.
For example, when we disconnect 419, proposal 1 and payment request 1 will transition like this:
Proposal 1:

State: 3 (expired) -> 0 (nil)
Blockhash: 0x6c504bb8ae6a80bc7b118450dd40e52976951701684cdf86345973faf27263dd -> 0x0
Payment request 1:
State: 1 (accepted) -> 0 (nil)
Blockhash: 0x6c504bb8ae6a80bc7b118450dd40e52976951701684cdf86345973faf27263dd -> 0x0

Now we can stop disconnecting and reconnect 419 and higher blocks, or keep disconnecting lower blocks to reconnect them later. Whatever we do, the votes in the ranges 385-389 and 396-419 won't be counted, because the parent proposal has not the accepted state anymore. If the votes are not counted, the payment request is never accepted, the block hash is never set again and the payout is rejected.
This situation happens unless we reorganise lower than 363. Then we find a different situation when we reconnect 363. We will see an error when the payment request is created, because the proposal is not in an accepted state. For this we would need reorganise lower than 330, so 329 is reconnected and proposal 1 recovers its accepted state.
I have an idea on how to fix this, but would need every wallet to reindex/resync.
I'll leave it here waiting for feedback from others.

I've committed a fix for the previously described issue in 29f404d.
This will require every node to reindex the first time it's opened. Verified with the aforementioned script, verifychain now passes for partial runs.
With the new patch, the whole history of entries states is stored in a map. When an entry is reorganised the last state is erased and the previous one automatically assumed as the valid.

A new build of 29f404dcb30c07a56c260ba3ff06c8d14b261c29 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

This PR is failing thet test_navcoin binary with:
../../src/test/cfunddb_tests.cpp(431): error: in "coins_tests/cfunddb_state": check prequest == it.second has failed

It is fixed in 23337d5 @mxaddict

A new build of 2eee7d5d07df4462a9c38e08bc4ead4885aa0cce has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

@aguycalled  the cfunddb-fork-reorg-* tests seem to be failing in this build.

A new build of 86503ead6d221f9693cc8f37348bee01822dad16 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

$ qa/rpc-tests/cfund-fork-reorg-preq.py
Initializing test directory /var/folders/qh/7_l8lmqx2sb5ncxgtzzyb51r0000gn/T/testupjecmo8/9355
Stopping nodes
Cleaning up
Tests successful

passes locally but fails on travis

A new build of 100ad5e05ebfb98844fdcfe34dd4c2fd62eb378b has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

A new build of 175ed022fea6db0245a5a8efdc773d32dc1aceab has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

A new build of 0d9f99aed473ac428d466c692ce4ca1415550d00 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

A new build of 84f90d3ee20ef978bbad97b1c2ea29226aaa4923 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

A new build of 1ccac6411f45725b5ac7fed1f07b018747766e80 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

Compiled on OSX, running the RPC tests now.

The following test are failing for me when i run the full test suite;

[ ] cfund-paymentrequest-extract-funds.py
[ ] cfund-paymentrequest-payout.py
[ ] cfund-fork-reorg-proposal.py
[ ] cfund-paymentrequest-hardfork-452.py
[ ] cfund-paymentrequest-duplicate.py
[ ] cfund-paymentrequest-state-accept-expired-proposal.py
[ ] cfund-paymentrequest-state-accept.py
[ ] cfund-proposal-state-accept.py
[ ] cfund-rawtx-paymentrequest-create.py
[ ] getstakereport.py

rerunning now to double check

A new build of ffcea7f2c3a24f9b71135fa283aa3abfb4849e14 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

A new build of 1bf3ff917ffdc8f6ab81dc69b1768e8616a040ab has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

A new build of c4961a4c2d0b1372d16440b601b8f060f97d45d8 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

A new build of 5c9c60ddef94f744a44d3c916d3bc1f2b408f49c has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

A new build of 8369d1f36ff0c54c709c07b293e7fa18b5bae312 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

A new build of b20383558db3a698f26c0085aa1732a50590ac69 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

A new build of cd0181d35b16595a50d2e597e51dfedeb8486bd9 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

A new build of 774df53473ffdfc2ad1608afa2a4a99a293b42a7 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

can you push the changes of PR 638 here as well?

merged master from upstream

gitian build with commit 774df53, on first start a warning window will pop up asking to reindex, after clicking yes, wallet starts reindexing but stucked at 2762327 header sync

cc1e063 should fix that, as this pr was missing the fix for #631

yeah I figured. will start it again now that master is merged.

A new build of cc1e063fcab097a484b4c024b0c1da32ea4864e8 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

A new build of 994e4a99314b2441c2a98cb1349d2b799bd3f3c8 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

tested gitian build for windows 10 64 bit with various verifychain 4 XXX. Confirmed that current master fails on some XXX values but this PR passes all of them so far. Will be doing more testing on a self-built version including verifychain 4 0.

@chasingkirkjufell I'm starting my testing on this PR as well, so far so good.
It might be a good idea to post the list of verifychain 4 XXX commands that you tested with.

@mxaddict yup, very true.
on current master, block height 3703724, verifychain 4 X starts failing when X is greater than 1000.
on commit 664e4a9 , i remember verifycahin 4 X passes on X = 1, 10, 100, 1000, 10000, 100000, 200000, will do them again to confirm. And then I will do a verifychain 4 0.
confirms commit 41c44f0 now notices old bootstrap.
both GUI and headless

Tested e340751 OSX both gui and headless detect old db structure and wallet does reindex-chainstate to reconstruct it

A new build of 41c44f0de5fd834787f08e61175eaf22f8a1b154 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

A new build of e3407511b876febf9b372a165ea25269b4f1d167 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

A new build of b3d8aac0e27051cd57fdf4f80b0403280b90ca29 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

I've written a stresser script for devnet.
https://gist.github.com/aguycalled/13f362c29ea9c38624e8dd4593bc37f8
After correctly setting the parameters indicated in the beginning of the script, running the script will:

Launch a network with 2 nodes in devnet.
Generate (mine) blocks up to height 510 to enable soft forks and distribute coins between nodes.
Randomly generate proposals, payment requests and votes.
Check for correct synchronisation between nodes (no forks) and no CFunDB state inconsistencies (by comparing getcfunddbstatehash)
Detect reorganizations
Track the count of different states seen for proposals and payment requests
Generate a random amount of blocks after the stress phase to allow proposals and payment requests to transition to final states (expired, accepted, rejected, paid)
Test partial runs of verifychain when the process is done

A new build of 1bd70c8c0aef1befb3d37d9918dca132c57771f2 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

A new build of 475cf7b2ea46c1f28b4a41f1ab94aa433d87df54 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

compiles, running tests. Will review the diff in the morning.

RPC test suite passes, except getting some error with it not being able to find the file stakeimmaturebalance.py which definitely exists in the file system and has the same permissions as the other files. Travis passes, so I will move on.

Reindex initiated on OSX both testnet & mainnet

A new build of f630567726fb7d17acd75e333daa16b76ec7d833 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

A new build of 561339da34c4c981a629f422df943587a6fee375 has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

The RPC tests are failing in travis now. For me, either cfund-fork-reorg-preq.py or getstakereport.py seem to be non-deterministically timing out

A new build of 3b9d623f298256685699481e3c2a7099439af99c has completed succesfully!
Binaries available at https://build.nav.community/binaries/verifychain-view

I'm still running the scenarios:

[ ] verifychain 4 0
[ ] verifychain 4 10
[ ] verifychain 4 100
[ ] verifychain 4 1000
[ ] verifychain 4 10000
[ ] verifychain 4 100000
[ ] verifychain 4 1000000

Ubuntu 19.10 self compiled using depends dir.

I've also verified that running this branch on an old datadir forces a reindex.


separate osmo boost

What is the purpose of the change

ClickUp Task
ClickUp Task URL
Brief Changelog

Testing and Verifying

Documentation and Release Note

@sunnya97 different from this? https://github.com/osmosis-labs/osmosis-frontend/pull/2570/files

@MaxMillington Yeah, that PR got bonked for some weird yarnlock reasons I didn't want to fix rn, so just recreated the PR


What is the purpose of the sample.json file?

Sample.json seems to provide metadata regarding the prompt which we provide in the README. Will this be used to populate some kind of prompt directory? Can you share the purpose of this file?
Thanks!

Hello @mjfusa  - You are right. The metadata details which will be specified in the sample.json file will be used to show the details about the prompt sample in the M365 Solution Gallery page so that users can quickly search about prompts. Hope that is clear for you.
Let us know if you have any other questions on the same.
You can also refer this article (Just in case if you have not seen) which talks about how to use and contribute to the prompt labs repo.
@rabwill  - Please feel free to chime in if I have missed out any other information on this front.

Thanks @arjunumenon - That makes sense - However the Solutions Gallery as the destination for the contributed prompts is not mentioned in the blog post or anywhere in the repo.

Good point, we will definitely add this in the repo @mjfusa thanks for the suggestion.

Added to above suggestion to the readme : https://github.com/pnp/copilot-prompts?tab=readme-ov-file#copy-the-sample-json-file


Create the new Collation RLP object

What is wrong?
(Updated the issue, separated this ticket from VMC contract)
CollationHeader
shard_id           uint256 // pointer to shard
parent_hash        bytes32 // pointer to parent header
chunks_root        bytes32 // pointer to collation body
period             uint256 // timestamp
height             uint256 // height in collation tree
proposer_address   address
proposer_bid       uint256
proposer_signature bytes

Collation
header     CollationHeader
blobs        list of blob

How can it be fixed
Since there are two other issues are related to VMC, it might be better to create a new Collation class to avoiding influencing VMC.

I think I can work on this.
Change the collation structure according to the new spec, and do VMC optimization

@mhchia

Some fields renamings are still in discussion.
Removing state_root of Collation may make some tests fails due to this line: https://github.com/ethereum/py-evm/blob/3784a87d0850c92d5865d97ce4bb6f5075d47896/evm/vm/forks/sharding/vm_state.py#L45
Which means we may have to make another temporary NewCollation class or decouple state execution.

I suggest something you can do before this issue:

Move VMC out of evm/vm because (1) it's not part of VM and (2) help for decoupling state execution and other processes.
Ping @pipermerriam , what do you think of we move VMC contract to ethereum/sharding repository and we make sharding repository to be a submodule of py-evm? If it's okay, @mhchia would you help to move?
Write down basic VMC API doc. (don't need to be perfect)

@hwwhww Thank you for the suggestion. I would like to help. But I think I should finish GUESS_HEAD first, and then come to this issue after. So sorry for this.
If anyone would like to do this please feel free to take it.

This seems to overlap with #436

@jannikluhn A little bit, but my plan is that  #420 defines the CollationHeader and the blobs in CollationBody are just binary data; #436 handles the blobs encoding and the binary chunk Merkle tree.

Updated to ticket description.

@jannikluhn

Some fields have type uint256, which I assume means that encoded integers are padded with zeros to a size of 32 bytes. This makes sense for the SMC (easier to decode) but not so much for RLP encoding (takes unnecessary space). Can we encode integers for the RLP format in the traditional way (like block headers are today) and then provide some kind of "encode for SMC" method?

If we do this, it seems

we will need to implement the minimal rlp decoder for big_endian_int. I'm not sure if it is worthwhile or not.
Or we just use the rlp decoder contract. But it needs an additional contract call.

Related: What's the hash of a collation header? A block header hash is keccak(rlp(header)), in the existing collation implementation it's keccak(shard_id ++ period ++ ...). Do we want to have both, should the SMC learn RLP, or should we go with the field-concatenated hash everywhere?

IMO for simplicity, using field-concatenated hash seems easier. I'm not sure if it is worthwhile to make SMC able to RLP encode. We will have to implement it and test it further. And maybe it will cost more gas to do rlp encoding compared to the field-concatenated hash.

There's no reference to the main chain anymore (in the previous version there used to be a "period_start_prevhash"). Is that intentional?

I'm not sure of it either. Maybe need to ask @hwwhww

Is there any format for the proposer signature? I think at least a maximum size would be necessary, but we could also go further and have v/r/s integers just like (old-style) transactions (although I kind of like having a single signature field).

I think we can use the previous format of signature. It is the just the concatenation of v, r, s. (https://github.com/ethereum/sharding/blob/develop/old_sharding_poc/sharding/contract_utils.py#L19-L22). And it can be verified through the validation code we used before.

What's the proposer signature exactly? Same as transaction signature, but without the replay protection hacks?

I don't know it for now either. It is not currently included in the spec and need to be clarified as well. If we want to do it now, maybe we can start off letting the sig_hash_of_proposer to be keccak(concat(shard_id ++ parent_hash ++ ... ++ proposer_bid)) or something like this.
Just some thoughts. Please correct me if there is anything wrong :)
And we can discuss about these on the meeting tomorrow.

There's no reference to the main chain anymore (in the previous version there used to be a"period_start_prevhash"). Is that intentional?

yes!
Also, we're thinking about removing height too since I couldn't find a scenario of why we definitely need height in header ... I can say it's convenient in some cases, but now we're thinking of just log height in the EVM log or just query the score from SMC (in JMRS, score still equals height).
shard_id           uint256 // pointer to shard
parent_hash        bytes32 // pointer to parent header
chunks_root        bytes32 // pointer to collation body
period             uint256
proposer_address   address
proposer_bid       uint256
proposer_signature bytes

closed via #462


Automate with Travis-CI

This project should have automated tests in Travis-CI

This project moved to kafka-assets


comments

cimgui has auto comments generator.
Is it possible here too?

allowed now editing generator.bat (.sh)


Create 0000-01-02-ven.md

created a branch, created a file and made a commit, and opened a pull
request

done

done

rtj


update(events/helper): add the DoNothing helper

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind documentation

/kind tests

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area commands

/area pkg

/area events

What this PR does / why we need it:
The DoNothing helper can be used together with SpawnAs helper function when we just need to test execve events, cmdlines arguments and so on.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: loresuso
Once this PR has been reviewed and has the lgtm label, please assign fededp for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Thank you @leogr! I think we are good to go then :)

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leogr, loresuso
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: a5fc738dd56c1251805f67153a792339fbdab77d


distinctUntilChanged strange behavior with Join

have anyone tried using distinctUntilChanged and then using join after it ?
it is not behaving properly.

How is it not working properly? Please provide more details and code that demonstrates your problem including the actual and expected behavior.

i should simplify the code to make it easier to follow,will do that and post it, thank you.

Closing until further details are provided.


Add Enemy Killed Sound Effect

Add Enemy Killed Sound Effect
Currently when the player character jumps on an enemy character, the enemy dies. However, there is no sound effect for this.
Add a short sound clip for this. Make sure any sounds used are copyright free and add their source into the copyrights.txt file.
If you need and help or have a suggestion, just leave a comment.

@EdwardDunn  I would like to work on this issue. Can you help me giving suggestions as how can I add the sound effects as I don't know how to do so and would like to learn that.

@chotuaashiq thanks for your interest in the project. If you have a look at how the jump sounds are implemented it will be very similar for the enemy killed sound effect. Have a look at the game.js file and try to understand the different parts.
This part of the code in the KeyDown function activates the jump audio;
if (keysPressed[UP]) {
jump_audio=document.getElementById("jump")
jump.autoplay=true;
jump.load();
moveUp();
}
If you do a similar thing in the updateGameArea function in the enemy characters for loop.
Give it a go and let me know how you get on.

@EdwardDunn I did the same thing but the sound is still not working.

@chotuaashiq if you submit a PR  with your progress so far I will take look.

Is this issue solved?

@Redarcher9 No, feel free to take it up.

Hi @EdwardDunn  Is this issue still open ? Would like to work on this issue ?Thanks

Completed by @tata81


Student attendance can become negative

Steps to reproduce:

Start a lesson
Mark Student as Present
Set lesson of Class to 0. Due to implementation of setlesson command, all Student who have attendance above 0 will be reduced to 0.
Student will be marked as Present for a 0/0 class. [See second image]
Mark Student as Absent

Fixed in #138


Allow passing environment variables through

Apologies if this exists, I can't find a way. Today when I run my tests I set a bunch of env variables in the CI script for things like log and coverage paths that I'll upload later:
env.DC_TEST_LOGS = path.join(cwd, ".dart_code_test_logs", `${testRunName}_${dartFriendlyName}_${codeFriendlyName}`);
env.COVERAGE_OUTPUT = path.join(cwd, ".nyc_output", `${testRunName}_${dartFriendlyName}_${codeFriendlyName}.json`);
env.TEST_XML_OUTPUT = path.join(cwd, ".test_results", `${testRunName}_${dartFriendlyName}_${codeFriendlyName}.xml`);
env.TEST_CSV_SUMMARY = path.join(cwd, ".test_results", `${dartFriendlyName}_${codeFriendlyName}_summary.csv`);

I can't see any obvious way to do this, if it's not supported would you consider it?

testRunnerEnv is available in 0.4.0 now.

It doesn't look like this is working properly in 1.2.3. Despite passing in the entirety of process.env to runTests(), no environment variables are available in the test runner script specified by extensionTestsPath:
await runTests({
  extensionDevelopmentPath,
  extensionTestsPath,
  extensionTestsEnv: process.env,
  launchArgs: [extensionWorkspacePath, "--disable-extensions"]
});

In the extensionTestsPath file:
export function run(): Promise<void> {
	console.log(process.env)  // prints nothing
}


[BUG] deploy.sh uninstall does not remove update scripts from crontab

Describe the issue
If automatic updates are selected during installation, they are not removed during un-installation.
To Reproduce
Steps to reproduce the behavior:

deploy.sh install
select 'y' when prompted to enable automatic updates
deploy.sh uninstall
crontab -e to see the scripts

Expected behavior
The crontab entries for /opt/lme/lme_update.sh and /opt/lme/dashboard_update.sh are removed.

Adding a few lines like:
crontab -l | sed '/30 1 * * * \/opt\/lme\/lme_update.sh/d' | crontab -
crontab -l | sed '/0 1 * * * \/opt\/lme\/dashboard_update.sh' | crontab -

added to the deploy.sh uninstall section should suffice (untested).


#105 Allow the ability to include or exclude keys using the CLI

I added to additional options to the CLI.

includes: Allows a list of patterns that is used when cleaning up the existing list. all keys that match one of the patterns will not be removed when cleaning up the keys
excludes: Allows a list of patterns that is used after the extraction of the keys. All keys that match one of the patterns will be removed of the extracted collection.

Why do you need to be able to include/exclude keys? If you don't want keys in your language files, don't use them with TranslateService or the marker-function.


Add example with authentication

The documentation for environments mentions creating a new environment instance whenever the user logs in or out in order to prevent data for different users being cached together. This seems like a very common usage pattern, but the documentation doesn't show any examples of how to do it. The todo example in this repository doesn't handle logging in and logging out, so it doesn't show how to do it, either.
There is a StackOverflow question that discusses how to do this, but it's light on details. It also refers to storing the environment in component state, which is not shown in the todo example in this repository.
Could you add an example to this repository that shows how to create a fresh environment instance when a user logs in?

The documentation also discusses handlerProvider, but doesn't explain what the benefit is of using it. Based on the code sample in the documentation, it seems like the ViewerHandler might be useful for handling authentication, but there's no documentation for what this ViewerHandler object is or what it actually does. This also seems like it merits an example.

Specific authentication implementation is outside the scope of Relay, which is a GraphQL client to handle GraphQL data. It's recommended to make a completely new environment when users log in and/or out like specified in Stackoverflow in order to start fresh without potential privacy issues. It's pretty error prone if you try to share partial data between users. When the new environment is created is dependent on your authentication logic. handleProvider is used for custom logic when storing graphql data in Relay, but is not relevant for authentication.

Specific authentication implementation is outside the scope of Relay, which is a GraphQL client to handle GraphQL data.

I understand that there are many different ways to implement authentication, and server-side authentication handling is outside the scope of Relay. However, client-side authentication handling is definitely within the scope of Relay, since Relay needs to be able to make authenticated requests to the GraphQL endpoint. The whole point of a relay-examples repository is to show examples of how to use Relay correctly, and authentication is a complicated topic that deserves an example.

It's recommended to make a completely new environment when users log in and/or out like specified in Stackoverflow in order to start fresh without potential privacy issues. It's pretty error prone if you try to share partial data between users.

The fact that there is a recommendation like this, clearly illustrates that Relay needs to handle authentication somehow.

When the new environment is created is dependent on your authentication logic.

Of course. I'm asking for a simple example that shows one possible way of creating a new environment.

handleProvider is used for custom logic when storing graphql data in Relay, but is not relevant for authentication.

This is useful information: thank you! The documentation wasn't clear on this, which is why I thought that handleProvider might be relevant to authentication. An example of handling authentication with a Relay-enabled app would make it even clearer.
There is already a User model for the todo example. I would recommend making the following changes, in order to make an example that illustrates how to handle authentication with Relay:

Extend the User model by adding three fields: username, password, and apiToken.
Create login mutation, that takes username and password as input. If the username and password match a user in the database, return that user's apiToken.
After the client executes the login mutation, create a new environment (this is what I'm most interested in seeing!) and save the apiToken to sessionStorage or localStorage.
Every time Relay makes a query, check sessionStorage or localStorage for an apiToken. If one exists, add an Authorization request header with that token.

However, client-side authentication handling is definitely within the scope of Relay, since Relay needs to be able to make authenticated requests to the GraphQL endpoint.

Github listed three potential ways to authenticate here: https://medium.com/the-graphqlhub/graphql-and-authentication-b73aed34bbeb. We recommend doing authentication through a different endpoint and make sure your custom network layer has the relevant info to send authenticated request to the GraphQL endpoint. I would like to echo that post and also say that the third option is something that I've not seen done in production and thus not sure it a pattern we want to encourage. Doing a simple mutation won't resetting existing data in the cache, so you would still have to Create a new environment (to clear out data from potential previous users) and make sure your network layer can use the token for requests.
Info about that here:
https://facebook.github.io/relay/docs/relay-environment.html#a-simple-example https://facebook.github.io/relay/docs/network-layer.html

Extend the User model by adding three fields: username, password, and apiToken.

I think it will be a terrible idea to add password to any Model. The server should not send that down for authentication. Please please don't do this.

Create login mutation, that takes username and password as input. If the username and password match a user in the database, return that user's apiToken.

You can get the apiToken in graphql, but you can do that with any endpoint. Relay is agnostic to that. As mentioned above, I have not seen this pattern in production. You still have to create a new environment to avoid cross user data sharing. It's not very interesting to commit the mutation in the Relay store because we should theoretically be making a new store/environment anyways.

Thank you for providing this information, as well. The docs are sorely lacking on this, and I wasn't aware of that blog post about authentication. However, this still doesn't resolve my issue.
You say that I have to create a new environment when a user logs in. That's fine, that's what I was expecting from the start of filing this issue. What I need is some example code that does that. I don't know how to create a new environment.
Could you (or someone else who works on Relay) show me how to create a new environment? That's really what I'm looking for in an authentication example.

Hi @singingwolfboy,
Just stumbled on your issue while looking for something else, but I can help. Here's my environment config file. You can see that I fetch my session ID on each request (which is just stored in the browser's localStorage) and adds it the the HTTP Authorization header (which is what my API checks).
import {
	Environment,
	Network,
	RecordSource,
	Store,
} from 'relay-runtime';

import * as session from './session';

const source = new RecordSource();
const store = new Store(source);
const network = Network.create(async (
	operation,
	variables,
	cacheConfig,
	uploadables,
) => {
	const headers = {
		'Content-Type': 'application/json',
	};

	// get our session identifier
	const sessionId = session.get();
	if (sessionId) {
		headers['Authorization'] = `Bearer ${sessionId}`;
	}

	// make the HTTP request
	const response = await fetch('/graphql', {
		method: 'POST',
		headers: headers,
		body: JSON.stringify({
			query: operation.text,
			variables: variables,
		}),
	});

	// we are using an invalid session, get rid of it
	if (response.status === 401) {
		session.clear();
	}

	// there was an error communicating with the API
	if (!response.ok) {
		console.error(`API ERROR: ${await response.text()}`);
		throw new Error(response.statusText);
	}

	// parse the JSON response
	return response.json();
});

const environment = new Environment({
	handlerProvider: null,
	network,
	store,
});

export default environment;

Elsewhere in the app, I use a Relay mutation to authenticate (using my API's authenticate mutation). I use authority and proof here, which is abstract over a bunch of different authentication strategies (ID/Email + Password, ID + Password Reset Token, Google, Facebook, etc) but you can just replace these with whatever you want to use, like username and password. The mutation, if successful, returns a new Session, so we'll make sure to grab it's ID. We then stuff that ID in localStorage so that the next time we make a GraphQL query, we're authenticated!
const mutation = graphql`
	mutation AuthenticateFormMutation($authority: Authority!, $proof: String!) {
		authenticate(authority: $authority, proof: $proof) {
			message
			session {
				id
			}
		}
	}
`;

Of course, with this strategy you can't put the entirety of your API behind authentication, since at least the authenticate mutation needs to be accessible without a session.

Perhaps a simpler strategy would be to simply send a username/password pair with each request, using something like http Basic in the Authorization header. This certainly has its security and visibility downsides, but might be an easier way to get a working prototype.
Hope that helps.

I have an example in https://github.com/este/este


 Or at the very least stop spamming.

Please describe your issue here: I do not provide support through email.


✨ feat: nested types (closes #53)

closes #53

Codecov Report

Merging #55 (bad63ec) into main (7241da9) will decrease coverage by 0.06%.
The diff coverage is 93.10%.

@@            Coverage Diff             @@
##             main      #55      +/-   ##
==========================================
- Coverage   94.53%   94.46%   -0.07%
==========================================
  Files          24       24
  Lines         841      867      +26
==========================================
+ Hits          795      819      +24
- Misses         46       48       +2

Impacted Files
Coverage Δ

...ftPlantUMLFramework/Internal/SyntaxStructure.swift
98.03% <ø> (ø)

...antUMLFramework/Configuration/ElementOptions.swift
96.96% <66.66%> (-3.04%)
:arrow_down:

...ftPlantUMLFramework/Internal/PlantUMLContext.swift
88.15% <85.71%> (-0.25%)
:arrow_down:

...ramework/Internal/SyntaxStructure+Extensions.swift
97.67% <100.00%> (+0.90%)
:arrow_up:

...ources/SwiftPlantUMLFramework/PlantUMLScript.swift
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


release .deb

Please release .deb

I don't think I can pull request a release but you can get it from this fork

I created a new version with the releases for linux
https://github.com/cerebroapp/cerebro/releases/tag/v0.5.0
However some plugins stopped working in this version, we will investigate to fix that!


Don't override GRPC_DEFAULT_SSL_ROOTS_FILE_PATH

By default, spice-py will override the environment variable GRPC_DEFAULT_SSL_ROOTS_FILE_PATH to the LetsEncrypt root certificate. While this works for Spice, it will break other python libraries that depend on gRPC and need to connect to endpoints which aren't secured by LetsEncrypt, i.e. Google BigQuery.

We should not set an environment variable, but pass the detected file path directly to pyarrow.


chore: update to<EMAIL_ADDRESS>

Summary
Why not 😀

Test plan
Green CI

Parsing error from Babel: https://github.com/babel/babel/issues/12957

@orta is this mess expected from TS 4.2? I don't see import type t = require('t'); in the changelog, babel parser threw an error until today's release, I just filed a bug with WebStormsince they throw. And now our type tests fail withOnly ECMAScript imports may use 'import type'.`. Which vibes horribly with
packages/jest-globals/src/index.ts:10:1 - error TS1371: This import is never used as a value and must use 'import type' because 'importsNotUsedAsValues' is set to 'error'.

10 import importedExpect = require('expect');

ESLint gives a parse error on the import type thing = require('thing') syntax...

Blocked by #12220 (and #12219 for 4.5)

Yes!


remove bias parameter

How can remove bias parameter: so I tried to include the bias=None where I define my neural net but it didn't work.
net1 = NeuralNet(
    layers=[  # three layers: one hidden layer
        ('input', layers.InputLayer),
        #('hidden', layers.DenseLayer),
        ('output', layers.DenseLayer),
        ],
    # layer parameters:
    input_shape=(None,2),  # 2 inputs
    #hidden_num_units=200,  # number of units in hidden layer
    output_nonlinearity=None,  # output layer uses identity function
    output_num_units=1,  # 1 target value

    # optimization method:
    update=nesterov_momentum,
    update_learning_rate=0.01,
    update_momentum=0.9,

    regression=True,  # flag to indicate we're dealing with regression problem
    max_epochs=400,  # we want to train this many epochs
    verbose=1,
    bias = None
    )

You have to prefix that bias argument with the name of the layer you want to remove the bias parameter from.  So for example write output_bias=None instead of bias=None.


Add "Edit Shape" to Right-Click menu of Custom Shapes

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Is your feature request related to a problem? Please describe.
Currently it can take up to five clicks and a modal change (switching to the Style tab) to get to the "Edit Shape" dialog of a pre-existing Custom (aka stencil()?) Shape.
Describe the solution you'd like
When right clicking on an object that was created with the "Shape..." option in the create object tool (plus sign on the toolbar) there could be an option for "Edit Shape" to bring up the same dialog that appears when you have the object selected and choose "Edit Shape" from the Edit dropdown menu in the Style tab of the right side panel (in classic theme)
Describe alternatives you've considered
As far as I can tell, the only way to edit a custom shape in this way is through the dropdown in the Style tab.  I thought I remember it being in one of the other menus but I keep accidentally opening "Edit Geometry" and "Edit Diagram".

Added in the Simple theme.


undefined: admin.AssetManager?

I fork the open source that it uses admin.AssetManager, admin.go have AssetManager ago? Now, what do I use to replace it? Thx.

Hi @thinkerou
It has been move to this repo https://github.com/qor/media_library/blob/master/asset_manager.go
Sorry for the inconvenience.


[ART-1106] Revert "elliott find options fix"

This reverts commit 3f68739a87b222aa14b7700cb41f42652121e77a.
https://jira.coreos.com/browse/ART-1047 states that one, and only one option out of --kind, --from-diff and --kind should be allowed.
But the described use case does need 2 of those options to work --kind and --build).
Given that, I'd say the premise of ART-1047 is wrong, so we should just revert that commit.

Codecov Report

Merging #55 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #55   +/-   ##
=======================================
  Coverage   32.25%   32.25%
=======================================
  Files          22       22
  Lines        1987     1987
  Branches      307      307
=======================================
  Hits          641      641
  Misses       1331     1331
  Partials       15       15

Continue to review full report at Codecov.

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

Closing in favor of https://github.com/openshift/elliott/pull/57


Project 1: Initialize project with components

I have set up a bookstore app using CRA
Created a directory for reusable components called components
Installed React Router
Added two  routes inside  component :   and
Added Navigation for the two routes

Alright, Thank you for the feedback I would do that


docs-bug(Card): Testing with MatCardHarness Example

Documentation Feedback
What's the point of ?? [] in https://github.com/angular/components/blob/04d3b63de2fb843beb55836e39e930c3342d26f1/src/components-examples/material/card/card-harness/card-harness-example.spec.ts#L34 ?
Seems like it can be removed
Affected documentation page
https://material.angular.io/components/card/examples#card-harness

Agreed, I don't think it's necessary.

If no one is already working on it, I would like to do this change.


Remove load-image-ios

The latest release of blueimp-load-image does not provide the module load-image-ios anymore

Thanks @rhymes!


python crash after typing cal = vobject.iCalendar()

I've downloaded this and run the setup and tests.  I get this after running python tests.py:
.............vobject.base ERROR Skipped line 6, message: At line 6: Failed to parse line: X-BAD/SLASH:TRUE
.......................
Ran 36 tests in 0.263s
OK
If I try a very basic item:
Python 2.7.3 (v2.7.3:70274d53c1dd, Apr  9 2012, 20:52:43)
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

import vobject
cal = vobject.iCalendar()
Segmentation fault: 11

I get a crash right away.  I'm assuming it has something to do with the failed test?
Has anyone seen this before?  Any idea what I do to fix this?

Switching to using Code Runner seems to have stopped the crashes (at least while I run it from within the program)


How to remotely connect to mysql and restart a service in your lemp.

Hi can you tell me how to remotely connect to mysql and restart a web service in your lemp.
It helps me a lot but I am still stuck on some questions.
@help @noamanahmed

What stack? PHP or node. There is a restart-site script.
Remote connection is something that would NEVER be allowed.
There is a possibility to add OpenVPN or wire guard setup to access it securely. There is alot of security issues involved in opening it publicly
But if this is something you definitely want. You can bind mysql address to public ip and use ufw allow command to expose it on the internet.

Exactly as you said. Disallow remote connection but there are some way like public ip to allow remote into mysql. I'm looking for a way to use this to make pushing data easier. However, there is a lot of documentation and you are not sure how to get your library up and running. If possible you can spend a little time teaching people to read and learn more about mysql or mongodb remote connection.
Above is just wish if yes I think it is very helpful  ! Really thanks for your library it helps me a lot.

I am using strapi with mysql.
But my own project usually write it with nodejs and mongodb.
It took me 2 days to learn about your library about permission to access ssh and connect to upload data to sever.
Currently there are some problems such as wanting to install pm2 start but don't know how. I will learn more about how to get started on specific projects step by step.

You don't need to use PM2. Node JS process will be run using systemd scripts. This allows more granular control and will also allow alerts in a Monit in future too. The concept of whole architecture is that the person having the user privileges is just to upload and deploy code.
Regarding documentation, I haven't updated it in a long time.

I really want to share this library to my friends as well as those who need it I see a lot of people need it. They should be known and used with guidance. Because there are definitely users like me stuck at ssh. Or stuck at the database access step. Or they have trouble using systemclt to start when they're getting used to pm2 or nodemon.
Because this repository is quite new to people like me and it focuses a lot of knowledge to be able to use it methodically and effectively. I would love to offer you a cup of coffee to thank you for your contributions.

You don't need to use PM2. Node JS process will be run using systemd scripts. This allows more granular control and will also allow alerts in a Monit in future too. The concept of whole architecture is that the person having the user privileges is just to upload and deploy code.
Regarding documentation, I haven't updated it in a long time.
You can contact me over LinkedIn ( the link is in my profile description) and I can guide you how to set it up.


feat: LEAP-1097: Allow to update annotation only with changes

With FF on Update button will be disabled if there were no changes made to annotation. Also Update button will always say "Update" to fix some legacy leftover.
PR fulfills these requirements

[ ] Commit message(s) and PR title follows the format [fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made ex. fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
[ ] Tests for the changes have been added/updated (for bug fixes/features)
[ ] Docs have been added/updated (for bug fixes/features)
[ ] Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.)
[ ] Self-reviewed and ran all changes on a local instance (for bug fixes/features)

Change has impacts in these area(s)
(check all that apply)

[ ] Product design
[ ] Backend (Database)
[ ] Backend (API)
[ ] Frontend

Describe the reason for change
(link to issue, supportive screenshots etc.)
What does this fix?
(if this is a bug fix)
What is the new behavior?
(if this is a breaking or feature change)
What is the current behavior?
(if this is a breaking or feature change)
What libraries were added/updated?
(list all with version changes)
Does this change affect performance?
(if so describe the impacts positive or negative)
Does this change affect security?
(if so describe the impacts positive or negative)
What alternative approaches were there?
(briefly list any if applicable)
What feature flags were used to cover this change?
(briefly list any if applicable)
Does this PR introduce a breaking change?
(check only one)

[ ] Yes, and covered entirely by feature flag(s)
[ ] Yes, and covered partially by feature flag(s)
[ ] No
[ ] Not sure (briefly explain the situation below)

What level of testing was included in the change?
(check all that apply)

[ ] e2e
[ ] integration
[ ] unit

Which logical domain(s) does this change affect?
(for bug fixes/features, be as precise as possible. ex. Authentication, Annotation History, Review Stream etc.)

wrong task name


Rename Set Output Properties

Describe the bug
On the execution screen. We currently have a button to display "set output properties" that language needs to be changed to "set result parameters" per our updated language throughout the application.

@BenjaminRuby I didn't find this button. As I could see, the Set Output Properties is a task and seems to be already been renamed to Set Result Parameters.

Hey @Okisa I believe this button is a shadow button located on the Workflow Activity Detail page and only shows up when there a result parameters set as part of the workflow.

This was the only place I found the text a bit different, so I updated from Output to Result.

Still not able to find the button in the workflow activity detail, even if we have a result parameters set.

Thanks @Okisa i think this can be moved to verify as part of release


Unable to Reproduce ALMA-7b-LoRA Performance, Seeking Assistance

Thank you for your excellent work.
While fine-tuning the ALMA-7b-Pretrain model and testing with the checkpoint you provided, I was unable to reproduce the performance of ALMA-7b-LoRA as described in the paper. I would appreciate any guidance or suggestions you could offer.
I used the code, data, and scripts provided in this repository (including runs/parallel_ft_lora.sh and evals/alma_7b_lora.sh), with a training batch size of 256 and four V100 GPUs.
Please feel free to ask if you need more details about my experiments.

Thanks for your interest! Could you please provide the transformer, accelerate, and deepspeed version? And also, could you please provide the results you got?

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Thanks for your interest! Could you please provide the transformer, accelerate, and deepspeed version? And also, could you please provide the results you got?
I use transformers==4.33.0, accelerate==0.33.0, deepspeed==0.14.4
Here are the results of mine:

Download https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file password: changeme In the installer menu, select "gcc."

What is it? Could you please explain further

It looks like the results you got are very close to the checkpoint we released under the same virtual env. I suspect the main issue could come from the version mismatch.
Please try uninstall transformers, deepspeed and accelerate and reinstall them by

pip install git+https://github.com/fe1ixxu/ALMA.git@alma-r-hf
pip3 install deepspeed==0.13.1
pip install accelerate==0.27.2
pip install peft==0.5.0
Re-evaluate the checkpoint

Hope this is helpful

It looks like the results you got are very close to the checkpoint we released under the same virtual env. I suspect the main issue could come from the version mismatch.
Please try uninstall transformers, deepspeed and accelerate and reinstall them by

pip install git+https://github.com/fe1ixxu/ALMA.git@alma-r-hf
pip3 install deepspeed==0.13.1
pip install accelerate==0.27.2
pip install peft==0.5.0
Re-evaluate the checkpoint

Hope this is helpful

Thank you for your suggestion! I will try it out and provide feedback in this issue.

It looks like the results you got are very close to the checkpoint we released under the same virtual env. I suspect the main issue could come from the version mismatch.
Please try uninstall transformers, deepspeed and accelerate and reinstall them by

pip install git+https://github.com/fe1ixxu/ALMA.git@alma-r-hf
pip3 install deepspeed==0.13.1
pip install accelerate==0.27.2
pip install peft==0.5.0
Re-evaluate the checkpoint

Hope this is helpful

I try your suggestion, and it does lead to some performance improvement.

However, the reproduced performance still falls short of what the paper reports. Could you advise on any other potential factors that might affect the performance?
Any further suggestions for improvement would be greatly appreciated.

By the way, could you please provide the versions of the datasets, tokenizer, and huggingface-hub that you are using?


Laragon

Assuming I use Largon
I understand that to make this work I must not use "php artisan serve" command. When I use PHP ARTISAN SERVE I get the ip:port clearly indicated which I copy and use in .env config file on the frontend Vue side.
In this case I don't get any IP, what do I enter then for variable  vor VUE_APP_API_BASE_URL ?
Currently mine are this one follow:
VUE_APP_APP_BASE_URL=http://<IP_ADDRESS>:8080/
VUE_APP_API_BASE_URL=http://localhost/laravel-json-api/public/api/v1
When I try to login I get a "Invalid credentials!" but when I look into the Laragon database table I see the admin and secret passowrd properly created into table and when I try to register I get a "Oops something went wrong"

Hi @cococococococo
Thanks for using our products.
Can you please make sure you have installed Laragon?
The VUE_APP_API_BASE_URL should look like this if you would have installed it: http://laravel-json-api.test/api/v1
Please follow up after you installed Laragon for the JSON API
Thank you

Hi @cococococococo
Thanks for using our products.
Can you please make sure you have installed Laragon?
The VUE_APP_API_BASE_URL should look like this if you would have installed it: http://laravel-json-api.test/api/v1
Please follow up after you installed Laragon for the JSON API
Thank you

If you need help with any of your projects, we're happy to get in touch. We do custom development for start-ups and companies across the globe (you can check out our portfolio here https://updivision.com/portfolio and some happy clients over here https://updivision.com/testimonials). Don`t hesitate to drop us a line at<EMAIL_ADDRESS>or by using our contact form (https://updivision.com/contact).


choco install chocolateygui.... and then?

After installing chocolateygui using choco, then do what precisely, to actually start the GUI version?
I see no new apps when I press the windows key
I see no GUI executables in the programFiles (/32) dirs
I can't find any documentation on how to actually start chocolateygui after installing :/
Where have I missed any followup steps?

Reinstalling using --force now somehow does add 2 executables and I can find them when I search for chocolateygui using the windows key / menu.


[No QA] Additional Validation for RequestorStep + ACHContractStep

Details
cc @NikkiWines @ctkochan22
Final PR to add form validation to the RequestorStep and ACHContract/BeneficialOwners steps.
Fixed Issues
Fixes https://github.com/Expensify/Expensify/issues/167761
Fixes https://github.com/Expensify/Expensify/issues/166041
Tests

Add a test account by following instructions to add a dev account here and continue until you reach the "Requestor Information" step

Attempt to submit this form with the checkbox at the bottom unchecked and verify you are unable to do so + growl appears

Enter invalid values for the following fields and verify a growl appears for each (use suggestions for bad values):

street - e.g. add a "P.O. Box 123" to it
zip code - too many or too few numbers
date of birth - not a date at all
last 4 ssn - too many or too few numbers

Advance to the "Beneficial Owners" step

Try to submit this form without checking the bottom two boxes and verify error growls appear for each.

Add additional beneficial owners and repeat steps for the Requestor Step to see error growls appear as before

QA Steps
No additional QA
Tested On

[x] Web
[ ] Mobile Web
[ ] Desktop
[ ] iOS
[ ] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

Thanks all ! Updated 🙇

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging in version: 1.0.73-4🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production in version: 1.0.74-0🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


bug fix: Add CPU write access flag

In the last commit #90, I just removed the write access flag from the texture, but didn't change everything involving this texture to read-only, which caused a lot of problems, so instead of obsessing about whether or not the texture is writable, just add D3D11_CPU_ACCESS_WRITE to it to quickly fix the problems caused by the previous bug.

This bug brings up the issue that the existing test cases do not cover the basic scenarios.

This bug brings up the issue that the existing test cases do not cover the basic scenarios.

The issue is that there are no existing test cases at all 😅. but yeah one of the encoder functions needed this flag.


Provide raw log view for a pod

maybe kibana is overkill for looking at the log of just 1 live pod?

Right now this is trickier than it sounds... Logs endpoint doesn't support websockets: only spdy or chunked. Not sure of if xhr supports chunked responses? There is an open issue in kubernetes fit this IIRC, as there is for exec which has the same problem.

Agreed. Showing a static view would be OK (with an icky Refresh button) until websockets are available

honestly a static view is probably easier to deal with from a user's perspective, i.e. it's easy to copy/paste lines from it to create a gist without having to worry about the view scrolling away on you :-)


Revert "Update document for new Face SDK"

Reverts MicrosoftDocs/azure-docs#122212 since the new SDK hasn't been published yet.

#sign-off


Multiple recipient emails

Add support for multiple recipients to send_email
to_email_addresses can be a string or a list of strings.
Emails to multiple recipients are sent with preserve_recipients
flag set to False, which makes Mandrill send a separate 'To:' email
for each address.
Removed ignored ip_pool option and optional recipient name.
Set async=True on mandrill API send email requests
Since we're not checking the status of messages in the API response
there's no reason to wait for them to be sent. Emails with more than
10 recipients are always sent asynchronously, but for messages with
less than 10 to addresses the API response can still take some time.
From mandrill docs:

enable a background sending mode that is optimized for bulk sending.
In async mode, messages/send will immediately return a status of
"queued" for every recipient.

Looks good :+1:


Suggestion: If find tab is open invoking find just puts the selection into the tab

In other words don't open the dialog again.

user can always just go directly to the tab... and we don't want to move the mouse etc for you (that is weird), so I think the dialog is best -- can do it either way.


[WIP] Pre-commit hooks for cpp files

Downstream of #2955, #2965
To achieve Cpp pre-commit, I  need to install external dependencies, which is kind of troublesome since those dependencies I have are distributed as binaries. I can rely on the local system to install them. So I need further discussion here.
Otherwise, I should make this pre-commit check optional so that developers can opt-in and opt-out.

Feel free to grab it here. Close it due to inactivity.


Why are ther no New cases reported in st. Louis county 11/11

Almost certainly Veteran's Day meant that they were not working, and thus the dashboard was not updated.

Chris,
My apologies. I should have realized that.
Sorry to have bothered you with this.
Larry
On Friday, November 12, 2021, 09:22:10 AM CST, Christopher Prener @.***> wrote:
Almost certainly Veteran's Day meant that they were not working, and thus the dashboard was not updated.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

No worries - two things to keep in mind - this is going to become more frequent over the holidays, and public health departments are starting to re-evaluate whether resources spent on this type of reporting are the best use of their time.


Show errors from all models

$user->validate() && $profile->validate()  It shows errors only the first model.

Thanks!


Add handling of non existing folder to file copy logic - fixes #60

Went ahead and created changes in the master branch ... feel free to reject, and I will do it in dev instead

Awesome!  Thanks Christian - will leave this open for a few days to see if anyone has any feedback, merge it in if nothing comes up.  Feel free to ping me if I haven't gotten around to it by Monday.
Cheers!

You're welcome Warren - happy to help

Ping ... :-)

Alrighty, merging, thanks for the reminder!


cannot install fiddler

Installing 'fiddler' (5.0.20194.41348) [64bit]
FiddlerSetup.exe (6.3 MB) [==================================================================================] 100%    Checking hash of FiddlerSetup.exe ... ok.
Extracting dl.7z ... done.
Running installer script...
Linking ~\scoop\apps\fiddler\current => ~\scoop\apps\fiddler\5.0.20194.41348
Program 'cmd.exe' failed to run: The directory name is invalidAt
C:\Users\Pika\scoop\apps\scoop\current\lib\install.ps1:881 char:5
+     & "$env:COMSPEC" /c mklink /j $currentdir $versiondir | out-null
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~.
At C:\Users\Pika\scoop\apps\scoop\current\lib\install.ps1:881 char:5
+     & "$env:COMSPEC" /c mklink /j $currentdir $versiondir | out-null
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (:) [], ApplicationFailedException
    + FullyQualifiedErrorId : NativeCommandFailed

Creating shim for 'Fiddler'.
Can't shim 'Fiddler.exe': File doesn't exist.

What is result of manual execution of & "$env:COMSPEC /c mklink /j `"$env:SCOOP\apps\fiddler\current`" `"$env:SCOOP\apps\fiddler\5.0.20194.41348`"" in powershell?

& : The term 'C:\WINDOWS\system32\cmd.exe /c mklink /j "\apps\fiddler\current" "\apps\fiddler\5.0.20194.41348"' is
not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name,
or if a path was included, verify that the path is correct and try again.
At line:1 char:3
+ & "$env:COMSPEC /c mklink /j `"$env:SCOOP\apps\fiddler\current`" `"$e ...
+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (C:\WINDOWS\syst....0.20194.41348":String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

@ThatNerdyPikachu Is this issue still happening when you attempt to run scoop install fiddler?
Some steps to try out:

If files for fiddler exist in your apps folder stuff (%USERPROFILE%\scoop\apps\), delete them and try rerunning scoop install fiddler. If that doesn't work, proceed to the next step.
Although the message is a bit ambiguous, I'm guessing the error in your last command run comes from not having $env:SCOOP set (which is fine because you probably don't have a custom scoop directory set up). Therefore, I believe the correct command to test out is:

& "$env:COMSPEC /c mklink /j `"$env:UserProfile\apps\fiddler\current`" `"$env:UserProfile\apps\fiddler\5.0.20202.18177`""

NOTE: I updated the command to use the most recent fiddler version. Replace the version number string 5.0.20202.18177 with 5.0.20194.41348 if you still want to test the older version of fiddler.


Refactor GitOpsConfig Status Update Code

Is your feature request related to a problem? Please describe.

No, this is a code refactoring enhancement.
Describe the solution you'd like

I would like the code(pkg/controller/gitopsconfig/jobmonitor.go) that updates the .status section of the GitOpsConfig CR to use the same approach(k8s Informers) as Event creation.
Describe alternatives you've considered

The current code that updates the .status section is not as reliable as we would like.
What version of eunomia are you using?
eunomia version: v0.0.5
Additional context

We believe using k8s Informers for updating the .status section will be more robust than than current approach. See PR #212.

When completing this work, please remove the relevant TODO in jobmonitor.go.
Also related: #179.


⚠ Bofrost.at has degraded performance

In 69200a8, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1568 ms

Resolved: Bofrost.at performance has improved in d37e1f5 after 17 minutes.


[SPARK-13415] [SQL] Visualize subquery in SQL web UI

What changes were proposed in this pull request?
This PR support visualization for subquery in SQL web UI, also improve the explain of subquery, especially when it's used together with whole stage codegen.
For example:
>>> sqlContext.range(100).registerTempTable("range")
>>> sqlContext.sql("select id / (select sum(id) from range) from range where id > (select id from range limit 1)").explain(True)
== Parsed Logical Plan ==
'Project [unresolvedalias(('id / subquery#9), None)]
:  +- 'SubqueryAlias subquery#9
:     +- 'Project [unresolvedalias('sum('id), None)]
:        +- 'UnresolvedRelation `range`, None
+- 'Filter ('id > subquery#8)
   :  +- 'SubqueryAlias subquery#8
   :     +- 'GlobalLimit 1
   :        +- 'LocalLimit 1
   :           +- 'Project [unresolvedalias('id, None)]
   :              +- 'UnresolvedRelation `range`, None
   +- 'UnresolvedRelation `range`, None

== Analyzed Logical Plan ==
(id / scalarsubquery()): double
Project [(cast(id#0L as double) / cast(subquery#9 as double)) AS (id / scalarsubquery())#11]
:  +- SubqueryAlias subquery#9
:     +- Aggregate [(sum(id#0L),mode=Complete,isDistinct=false) AS sum(id)#10L]
:        +- SubqueryAlias range
:           +- Range 0, 100, 1, 4, [id#0L]
+- Filter (id#0L > subquery#8)
   :  +- SubqueryAlias subquery#8
   :     +- GlobalLimit 1
   :        +- LocalLimit 1
   :           +- Project [id#0L]
   :              +- SubqueryAlias range
   :                 +- Range 0, 100, 1, 4, [id#0L]
   +- SubqueryAlias range
      +- Range 0, 100, 1, 4, [id#0L]

== Optimized Logical Plan ==
Project [(cast(id#0L as double) / cast(subquery#9 as double)) AS (id / scalarsubquery())#11]
:  +- SubqueryAlias subquery#9
:     +- Aggregate [(sum(id#0L),mode=Complete,isDistinct=false) AS sum(id)#10L]
:        +- Range 0, 100, 1, 4, [id#0L]
+- Filter (id#0L > subquery#8)
   :  +- SubqueryAlias subquery#8
   :     +- GlobalLimit 1
   :        +- LocalLimit 1
   :           +- Project [id#0L]
   :              +- Range 0, 100, 1, 4, [id#0L]
   +- Range 0, 100, 1, 4, [id#0L]

== Physical Plan ==
WholeStageCodegen
:  +- Project [(cast(id#0L as double) / cast(subquery#9 as double)) AS (id / scalarsubquery())#11]
:     :  +- Subquery subquery#9
:     :     +- WholeStageCodegen
:     :        :  +- TungstenAggregate(key=[], functions=[(sum(id#0L),mode=Final,isDistinct=false)], output=[sum(id)#10L])
:     :        :     +- INPUT
:     :        +- Exchange SinglePartition, None
:     :           +- WholeStageCodegen
:     :              :  +- TungstenAggregate(key=[], functions=[(sum(id#0L),mode=Partial,isDistinct=false)], output=[sum#14L])
:     :              :     +- Range 0, 1, 4, 100, [id#0L]
:     +- Filter (id#0L > subquery#8)
:        :  +- Subquery subquery#8
:        :     +- CollectLimit 1
:        :        +- WholeStageCodegen
:        :           :  +- Project [id#0L]
:        :           :     +- Range 0, 1, 4, 100, [id#0L]
:        +- Range 0, 1, 4, 100, [id#0L]

The web UI looks like:

This PR also change the tree structure of WholeStageCodegen to make it consistent than others. Before this change, Both WholeStageCodegen and InputAdapter hold a references to the same plans, those could be updated without notify another, causing problems, this is discovered by #11403 .
How was this patch tested?
Existing tests, also manual tests with the example query, check the explain and web UI.

Thanks for adding the screenshot and the explain output!
What's the "(id / scalarsubquery()): double" in Analyzed Logical Plan ?

@rxin I think that the schema of the query. The sql string of ScalarSubquery is scalarsubquery
s"$prettyName($childrenSQL)"

Test build #52140 has started for PR 11417 at commit 24757f1.

Test build #52141 has started for PR 11417 at commit bc2c66b.

Test build #52140 has finished for PR 11417 at commit 24757f1.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class InputAdapter(child: SparkPlan) extends UnaryNode with CodegenSupport
case class WholeStageCodegen(child: CodegenSupport) extends UnaryNode with CodegenSupport

Test build #52141 has finished for PR 11417 at commit bc2c66b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class WholeStageCodegen(child: SparkPlan) extends UnaryNode with CodegenSupport

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52140/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52141/
Test FAILed.

Test build #2589 has started for PR 11417 at commit bc2c66b.

Test build #2589 has finished for PR 11417 at commit bc2c66b.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class WholeStageCodegen(child: SparkPlan) extends UnaryNode with CodegenSupport

Test build #52208 has started for PR 11417 at commit 2a27cd8.

@yhuai @nongli  Had update the doc string of innerChildren and treeChildren to include a example.

Test build #52209 has started for PR 11417 at commit cff0871.

Test build #52208 has finished for PR 11417 at commit 2a27cd8.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52208/
Test FAILed.

Test build #52209 has finished for PR 11417 at commit cff0871.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52209/
Test FAILed.

Test build #52252 has started for PR 11417 at commit 3293994.

Test build #52252 has finished for PR 11417 at commit 3293994.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52252/
Test PASSed.

Test build #52268 has started for PR 11417 at commit e69262a.

Test build #52268 has finished for PR 11417 at commit e69262a.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52268/
Test FAILed.

Merged build finished. Test FAILed.

Test build #2601 has started for PR 11417 at commit e69262a.

Test build #2601 has finished for PR 11417 at commit e69262a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Thanks. Looks good. I am merging this to master. Let's think about how to improve the name and doc of treeChildren and innerChildren.


Beta

I've added the mod Find Item in List & updated Convert Variable

Author opened new pull request #122


RSDK-623: remove position_reporting from Motor.Status

This field was moved to the properties struct.
This is an api breaking change, but one that shouldn't really be used externally. The only known use case was for remote control, which was updated in https://github.com/viamrobotics/rdk/pull/1684.
This must be merged before SDKs and RDK are rebuilt.

This will require SDK changes

Indeed. Draft PR waiting on a proto rebuild: https://github.com/viamrobotics/viam-python-sdk/pull/198


Test walkthrough

Description
Test walkthrough and creating issues for technical debt in tests
Acceptance criteria

Test walkthrough has taken place by all devs (individually)
Create issues for the most obvious test debt (where we have got already knowledge)
At the end all devs are aligned (dedicated call)
Research how to improve tests

Tasks

[ ]

Feedback from @taleldayekh @nephix needed for One fixture to rule 'em all #1377

The was done.
Feedback on #1377 , and possibly new suggestion on new issue


Setting follow to 0 does not prevent redirects

Passing 0 in options for 'follow' gets turned into 20 as 0 is "falsy".
If I change this line to allow 0 then a maximum redirect error is thrown handling the response.

my doc might be misleading, 0 to disable redirect limit, not disable following redirect
you can use 1 to achieve what you desire, if i understand correctly.

zero would never ever be set because options.follow = opts.follow || 20; would result in the follow being set to 20 as zero would be false. If this were set to one it would allow one redirect, rather than only allowing one request.

ah i confused myself, should be fixed in next release.

npm 1.0.5 should fix this issue.

:+1: Awesome!

This would always be an error though right? I mean if I wanted to access the headers from the redirect would that be possible? because it looks like it would only ever return an Error instance I notice in the spec there is a reference to a "manual redirect flag" https://fetch.spec.whatwg.org/#concept-request-manual-redirect-flag which looks like it would suffice for this situation.

@sonewman i don't think peeking into redirect header is possible at the moment (definitely not on client side), multiple reasons, first being security.


Revisit temperature limits and report over/under-temp load shutdown correctly

If the measured battery temperature gets above 50°C (configurable setting), discharging of the battery is disabled. The load output only realizes that it is not allowed to discharge anymore and assumes it is because of low voltage, so it goes into LOAD_STATE_OFF_LOW_SOC state. This does not make much sense.
Related to this issue: If no external sensor is connected, the sensor on the charge controller PCB is used, which can get considerably much hotter than ambient temperature at high load. This should be considered, either by a model-based approach or something more simple that increases the limits if charge controller load is high.

Well, main issue: easiest thing would be to rename LOAD_STATE_OFF_LOW_SOC to LOAD_STATE_OFF_BAT_PROTECT which applies to both cases.
The temp thing:
Is there any general correlation between the charge controller temp sensor's temperature and the battery temperature? If the battery is separated from the charge controller, the answer is probably: no. If the charge controller is mounted in thermal proximity of the battery, the answer is probably: yes sometimes.
In addition we have the load issue which is unrelated to the battery's state itself. If the battery is large enough, even a high load (which causes high controller temperature) may not bother the battery at all.
To cover the different cases best with overcomplicating things I think we should give the controller's temperature sensor a separate (configurable) limit meant to be used to protect the board from issues due to overheating (i.e. to reduce load). And the battery temp sensor is used if present, otherwise no battery temperature monitoring occurs and the respective limits are simply not used.

Interesting! I personally think that the temperature measurement from inside the casing is equally as interesting as the battery temperature. But you are right, the measurement does not reflect what it's supposed to.

Yes, we can keep the internal temperature measurement and send it out if needed, but it shouldn't be called battery temperature :)

So should we be setting different limits for the internal and external temperatures separately?
~80°C for internal
Stay with 50°C for external

Nice idea. I still think we should keep those limits quite high for those hot countries.


makefile: do not install mockgen automatically

As with golintci-lint, it should be left up to the developer to manually install mockgen on their local development environment.
Also, provide a means for running builds locally using the build image.

make build-build-image will build the build image
./hack/make script will run make in a container using the build image

I need to move the changes to the build image to a separate PR that will need to merge before this PR.

/cancel ok-to-test

/ok-to-test cancel

/hold
This requires #737.

/hold cancel
#737 has merged.

/lgtm


pull request for data magic

change the prompts.yml file

update 'topic' to 'Topic' in generate_markdown.py

@howard989 thank you!! Please go ahead and make a branch from the main repo for future PRs.
It's much easier to review your code that way, and you are a member of the organization.


Add method to retrieve CacheItem rather than the value of the item

Alternative implementation, more generic, for https://github.com/patrickmn/go-cache/pull/47

@patrickmn Any thoughts on the same?

Found this fork: https://github.com/arp242/zcache


new assets domain

sample URL: https://cdn.glitch.global/8e6cdc77-20b9-4209-850f-d2607eeae33a/kr8s1.png
could it have to do with fastly?
old URLs still seem to work for now

done a824b5372bf8e548dadf415bdd7f4163a674e6d5 back in 2.11.0


[PR][CLOSED] Moved pr-format-clang facility to plugins-good folder

 Issue by geunsik-lim
Tuesday Jun 12, 2018 at 09:28 GMT
Originally opened as https://github.sec.samsung.net/STAR/TAOS-CI/pull/23

This PR is to move the existing pr-format-clang function
to plugins-good category.
Changes proposed in this PR:

Moved clang feature to plugins-good folder
Fixed typos
Removed unnecessary files

Signed-off-by: Geunsik Lim<EMAIL_ADDRESS>
geunsik-lim included the following code: https://github.sec.samsung.net/STAR/TAOS-CI/pull/23/commits

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


chore(main): release 0.1.0

:robot: I have created a release beep boop
0.1.0 (2023-01-09)
Initial release! 🎉
This package is currently in an early alpha stage and supports only the fundamental Storybook features. Compatibility with more advanced features and addons is work in progress. Please open an issue if you encounter any bugs or missing integrations.
🧹 Miscellaneous

add debug logging (8099174)

add story template as source code (1c2ddf2)

add storybook addon (f767fcd)

add support for component option in default export (3cf7fb0)

allow comments before main <Stories> tag (cfc2358)

combine imports for multiple stories (b9541ff)

implement transform of simple cases (3a8fed2)

prototype of how vue -> storybook transform can work (b14378c)

support script and setup script (db343dc)

support special characters in story names (f545607)

support vue plugin in pipeline (d4f1b18)

add devcontainer (6dd4038)

add example vite application (fbe662a)

add exception for spelling (946d56c)

add missing pnpm install (24fda93)

add plugin to storybook vite config (8812b73)

change owner in license to Tobias Diez (7997113)

deps: update all non-major dependencies (#14) (b7ff47e)

deps: update all non-major dependencies (#19) (e1d2504)

deps: update all non-major dependencies (#8) (2d90aca)

deps: update dependency unplugin to v1 (#15) (eda0d0d)

deps: update devdependency @nuxtjs/eslint-config-typescript to v12 (#16) (0b7c484)

deps: update devdependency @vitejs/plugin-vue to v4 (#20) (3b0b830)

deps: update devdependency babel-loader to v9 (#21) (e08bc26)

deps: update devdependency rollup to v3 (#9) (d9a5812)

deps: update devdependency vite to v3 (#11) (20fdcbf)

deps: update devdependency vite to v4 (#18) (ec756c0)

deps: update devdependency vue-tsc to v1 (#22) (73b67ae)

enable pnpm in build (638ef3d)

fix a few eslint errors (8cd1f25)

fix devcontainer build (83b45af)

fix storybook start with new node versions (f522d16)

fix test command (9cf8b93)

fix ts and lint errors (619fe17)

ignore missing peer dependencies (66abfcd)

include examples in renovate update (9585baa)

initial release (a1e937d)

reformat everything (802b5c0)

remove unnecessary scripts from package.json (6ba7da5)

setup eslint and prettier (fe7aaaf)

setup funding (baa8e6f)

setup playground (75188bf)

setup renovate (e785d47)

update github action workflows (4a4f2e9)

update lock file (b182f1f)

update package metadata (89a16bf)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/tobiasdiez/unplugin-storybook-vue/releases/tag/v0.1.0 :sunflower:


Feat: Want to add auto filling of details in the Profile Modal

Describe the feature
I want to add the auto filling feature where details will be autofilled automatically when user will open the edit modal
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[ ] I'm a VSoC'24 contributor
[X] I want to work on this issue

@Ayushmaanagarwal1211 assigned


Spanish translation

By Neido Translations

Merging this into a new branch where I'll work on getting it running nicely. Thank you so much for this incredible work!


Scalar shorthand methods case should match SDL representation

In SDL we refer to types of String Bool Int etc. In Nexus we have shorthands for them of t.string t.bool t.int etc.
I think the casing should be consistent so that Nexus declarative API looks a bit closer to SDL.
So t.String t.Bool t.Int etc.
It's also more consistent for the fact that t.string is shorthand for type: 'String'.
It's also an important change if we ever want to have shorthands for all custom types defined in the schema as alluded to in https://github.com/graphql-nexus/schema/issues/591#issuecomment-720872365. Because then we would really want the methods to match their SDL type names case-sensitivity consistently.

@Weakky @tgriesser wdty?

Ehhh, I typically reserve capitalized names for constructors in js... but that aside - not sure I see a strong value in making this change. See comments re: t.Bar in #591

@tgriesser Yep I think without t.Bar this is a lot less appealing as an idea. Will close, people can chime in if ever they want to see the idea discussed again.


ngMocks.findInstance should support tokens

v13.3.0 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.


Import directly inside component, not globally

Hello,
How do you import SmartTable components (VTable, VTh...) directly into a component instead of importing them globally?
I can't find an example in the documentation and it doesnt work if I try to import them one by one :
import { VTable } from "vuejs-smart-table"
Thanks for your work

Same Here


Use Engine API to manage containers

Docker provides standardized Engine API through UNIX socket (and TCP socket for Windows). This way would be more standardized and well documented than current command output parsing.
Also another advantage would be the Podman support. Podman is rootless alternative for Docker which has fully compatible commands. But command outputs are different from Docker, thus currently extension cannot be used with it. But Podman supports Engine API.

Moved to https://codeberg.org/esensar/nvim-dev-container/issues/77


Bug: infinite loop on circular reference

Example:
$factory = new Factory(null, [
	'x' => Reference::to('y'),
	'y' => Reference::to('x'),
]);

// infinite loop
$factory->create('x');

Should throw exception.

Should count cycles in the same way as container, I guess.


How to support context filetype?

In https://github.com/tyru/caw.vim:

The comment behavior only depends on 'filetype' by default. But if you have installed Shougo/context_filetype.vim, caw.vim also depends on the filetype of the context of the current cursor location. So you can comment/uncomment JavaScript in HTML correctly.

How can Comment.nvim support context filetype? i.e., Comment code fence in markdown, js in HTML, yaml front matter in markdown...

I'm having this same problem with embedded code inside of Nix files.


Docs UI: Fix the behavior of the browsers Back and Forward buttons (so nav. menu does not refresh)

The Back and Forward buttons in the browser cause a page load and since the default state of the navigation menu (specified in the CSS) is "closed", when you click either the Back or Forward buttons in the browser, you see the menus open and close (because the javascript finds the corresponding menu item after the page is loaded and the opens and highlights it).
The fix for this might be to override the default actions of the browser's Back and Forward button actions so that they do not perform a page load and instead load the corresponding topic (from out of the history) into the "doccontent" div (for reference, see the following line in the _includes/documention.html file: "$('#doccontent').animate({scrollTop: 0}, 500).load(href + ' #doccontent > ');" - *this is how we avoid that menu opening and closing each time someone clicks a nav menu item).
See #12092 for how we open the nav menu and highlight the corresponding menu item on page load (so user can navigation directly to a specific topic/url and the nav menu opens to it).

@thockin

Closing -> fixed in #12437


clone op dialog: does not close anymore

https://github.com/user-attachments/assets/5a0bf500-0321-468c-83d7-d266cfcbeb09

https://github.com/cables-gl/cables_ui/commit/006b135dc51508421c6acae56f297782228f777d
i think "creating op" opened/and closed the modals but now does not anymore


ldapsearch: command not found

I was trying to do a full ldif export from fusiondirectory and it gives the following error: "Failed to generate ldap export, error was "sh: ldapsearch: not found"".  i thought it might be related to my settings somehow so i exec in container to try ldapsearch from there and receive the following error: "bash: ldapsearch: not found".  i checked the bin directories and did not see ldapsearch.  would it be possible to add the binary to the container to restore this functionality? i like to do the export from time to time as a backup. thanks.

Strange, I see it in /usr/bin - Check again?
As for LDIF exports, I've built in backup routines to help you with that. However they may different from what you may be used to: From the README of the parent image (tiredofit/docker-openldap):
| Variable | Description |
|-----------|-------------|
| `BACKUP_CONFIG_CRON_PERIOD` | Cron expression to schedule OpenLDAP config backup. Defaults `0 4 * * *` Every day at 4am. |
| `BACKUP_DATA_CRON_PERIOD` | Cron expression to schedule OpenLDAP data backup. Defaults `0 4 * * *`  Every day at 4am. |
| `BACKUP_TTL ` | Automatically cleanup backup after how many days. Default `15` |

Also, you can do it while inside the container with slapcat -n0 >/tmp/config.ldif and slapcat -n1 >/tmp/data.ldif. To readd in this manner you would need to shutdown openldap inside the container by executing s6-svc -d /var/run/s6/services/10-openldap followed by a pkill slapd then, this is where it gets a bit gnarly. rm -rf /var/lib/openldap/* and rm -rf /etc/slapd.d. Then you could add your backed up data back in with the slapadd command. Restart OpenLdap with s6-svc -u /var/run/s6/services/10-openldap

thanks for the quick reply, you are correct that this is the case with the openldap-fusiondirectory (LDAP) container, but it does not seem to be present in the fusiondirectory container (web app), i was trying to do this from the fusion directory app by going to LDAP import/export menu.  i hope i didnt post in the wrong place, it seems we are discussing different containers.  i am using the cron backups with the LDAP container, as you hint, i am not used to doing it this way so while i familiarize myself with these features i was trying to backup from the fusiondirectory app.  i do appreciate your work with this, i recently setup a new server and had my ldap up and running in no time.

Oh jeesh, my bad. Late in the day for me, you are in the frontend container and ARE posting in the right spot. I don't see a problem with adding the openldap-clients package in Alpine to support this!

No worries, just making sure since i am using several of your containers.  thanks for sharing your work,  look forward to the addition!

Glad they are of use to you! I've just pushed a new release (it might take an hour or so to hit Docker Hub) tagged :latest or :1.14 that should give you access to ldapsearch and the other utilities along with a few other fixes. I believe FusionDirectory 1.3 is imminent so there should be another release following within the month.

thanks for the update!  ldap search is working but i now have a different error, "Failed to generate ldap export, error was "ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)"", again this is when using export complete ldif function.  i was able to use ldap search as root inside container, but i assume the app is running as nginx user.  if i run ldap search as nginx then this error is produced.  i am also using user namespaces so that may be contributing. definitely seems like a permissions issue.  either way it seems getting this function to work isn't a quick fix as i hoped.  i realize that this may be beyond the scope of your intended use of the containers, especially since you have a backup function built in already.  that being said feel free to close this issue if you dont want to proceed down this rabbit hole.  i will start to better educate myself on how your backup solution works, primarily how to restore from one. thanks again.

Can you try this? chmod +s /usr/bin/ldapsearch from inside the container and see if your export now works? It's hackish but I can work this into the image if necessary.

so i still get the same error, however it does allow ldapsearch from nginx user now.  so i guess i was wrong about permissions, must be something with my configuration.  ill need to look at the plugin code and see where its going wrong.  it does give a hint, fusiondirectory/plugins/addons/ldapmanager/class_ldapmanager.inc line 183. ill keep investigating.


Update KSP version to any

This mod is just a MM patch that should be fine with any version of KSP. Setting the version to any makes it easier to find in CKAN and to install without doing a compatibility override.
@linuxgurugamer What do you think? Would this be okay?

I just once again abused my SD admin powers to update one of LGG's mods to current compatibility, since the entire last page of its forum thread is people pestering about compatibility and CKAN. Should make this PR less necessary once that change propagates into the metadata.

https://spacedock.info/mod/1854

It's up to 1.10.1; Let's let the architecture work as designed for now.

https://github.com/KSP-CKAN/CKAN-meta/commit/cef708e3714a07a148f230a679b3ce9f95eddfec


Add SpectralCentroid transform

Closes #1059
This PR adds a new SpectralCentroid layer, along with the spectral_centroid function.
I have the following design question:
Currently, SpectralCentroid and spectral_centroid take the raw waveform as input, and call spectrogram(...) internally. It might make more sense for them to take the spectrogram tensor as input instead? The reason I didn't go for that is that for the computation to be correct, the spectrogram must be computed with power=1 (to get the amplitude values).
One thing I find slightly awkward with the current design is that sample_rate must be passed at the initialization of SpectralCentroid and waveform is only passed when calling the object. But as far as I understand, sample_rate and waveform should ideally be tied together?
Still TODO:

[ ] More tests
[ ] Fix Linting (probably)
[ ] Allow for bounds as suggested in https://github.com/pytorch/audio/issues/1059#issuecomment-754622917
[ ] Check if spectrogram is complex and error in this case (not sure if relevant)

CC @mthrok :)

Quick glance, the code looks good. Can you add torchscript compatibility test and batch consistency test?

torchscript_bc_test is broken, so you can ignore it.
I will disable the segfaulting in tests soon. It's added yesterday and causing issues.

Quick glance, the code looks good. Can you add torchscript compatibility test and batch consistency test?

torchscript_bc_test is broken, so you can ignore it.
I will disable the segfaulting in tests soon. It's added yesterday and causing issues.