[AI]; Chasing Player Loop

Okay so, I'm not sure if this is a bug or not but, I put debugging on the OnChaseEnded OnChaseStarted events;
Note: Theres a [StringValue] titled "State" in the AI which controls some things like playing a spotted sound after the player has been seen and I modify its value upon the firing of the events (if that makes sense)
When the AI chases, it prints Not Chasing and Chasing(from the debugging I put) at the same time while the AI is chasing a Player
now I haven't tested this AI yet with 2 Players but it does that for some reason
before I put the modification of the State value on the OnChaseEnded and OnChaseStarted events but since they were repeating I had to move them to where the AI chases the Player AI.Movement:MoveTo(PlayerPosition) and that works but I still don't get why it repeats it

Are you using the Chase Example mechanic from the source?
Keep in mind examples are made for users to understand the uses of AIEngine.
Can you provide more details such as the lua code of where the issue happen?

Yes, I'm getting on studio in a bit and I will send you the printed info and the lines of code.

Do keep in mind; I don't have much experience with making AIs
And there's another bug where the AI runs into walls and stops there [Roaming Mechanism] but it's probably the AgentParams that I have to modify

Apologies for the crappy quality : Roblox being itself

Where are the prints located for you debugging on when the AI stops chasing and starts?

If the state changes rapidly it could well effect the Chase.
Try using the AI's api OnStateChange and print the value of the new State, and while testing check for any rapid changes in the State.
Another debug attempt you can try is print/warn inside the heartbeat, you should print AI.TargetPlayer, and the Player from scanner, before ChaseStarted is fired.
I would have to take a look at the example mechanics myself.

The state does not change, in the image I sent where the AI was chasing, on the other side the Output is visible; showing the prints

Oh, the prints on the code?

I'll send in a bit.

Can you add me on [Discord]: ( 7_81C )[Username]
Since, I have to wait like at least [a hour] for a reply on here
And if you're asking if I do need help, then yes; it's not a small bug that I can pass on from, it affects the gameplay (how?) I will explain there

Solved


Add classes to title and description inputs in html.

Added classes to title and description in html for jquery to interact with.

I guess this is good, JK!


Fix: Date format in order details

Issue: #556
As issue states it was just about wrong formatting string, for reference see: https://momentjs.com/docs/#/parsing/string-format/
Now it prints the date as expected.

Solved in #637


video player error Cannot read property 'supportedLocalesOf' of undefined

iLib build
after integrating the video player with enact.js I installed all necessary packages and imported all the modules but still, it is throwing this error called
Uncaught TypeError: Cannot read property 'supportedLocalesOf' of undefined
main.js:1493 The above error occurred in the  component:
and these are the versions I am using
"dependencies": {
"@enact/core": "^4.7.6",
"@enact/i18n": "^4.7.6",
"@enact/moonstone": "^4.5.4",
"@enact/sandstone": "^2.7.10",
"@enact/spotlight": "^4.7.6",
"@enact/template-webostv": "^4.5.5",
"@enact/ui": "^4.7.6",
"@enact/webos": "^4.7.6",
"ilib": "^14.18.0",
"prop-types": "^15.8.1",
"react": "^18.2.0",
"react-dom": "^18.2.0",
"web-vitals": "^3.4.0"
},
Environment
npm, chromium browser, lg webos device
Code:
import React, { useEffect } from 'react';
import BodyText from '@enact/moonstone/BodyText';
import Button from '@enact/moonstone/Button';
import MoonstoneDecorator from '@enact/moonstone/MoonstoneDecorator';
import Image from '@enact/sandstone/Image';
import Heading from '@enact/sandstone/Heading';
import deviceinfo from '@enact/webos/deviceinfo';
import { Video } from '@enact/sandstone/VideoPlayer';
import VideoPlayer from '@enact/sandstone/VideoPlayer';

const App = () => {
  useEffect(() => {
    deviceinfo((info) => {
      console.log(info);
    });
  }, []);
  return (
    <div style={{ height: '100vh' }}>
      <BodyText style={{ color: "#fff", padding: "20px" }}>
        test</BodyText>

      <VideoPlayer
        style={{
          width: '640px',
          height: '360px',
        }}
        title="Hilarious Cat Video"
        poster="https://wallpapercave.com/wp/wp4288169.jpg"
      >
        <Video>
          <source src="https://action-ott-live.s3.ap-south-1.amazonaws.com/MMM_Telugu/mmm_telugu_1080p.mp4" type="video/mp4" />
        </Video>
      </VideoPlayer>

    </div>
  );
};

const MyMoonstoneApp = MoonstoneDecorator(App);

export default MyMoonstoneApp;
export { App };

https://github.com/iLib-js/iLib/pull/436

@BhanuMathurthi please let us know if the above PR resolved the issue


New version: NumericIO v0.3.1

Registering package: NumericIO
Repository: https://github.com/ma-laforge/NumericIO.jl
Created by: @ma-laforge
Version: v0.3.1
Commit: 63c231f7c6f4d2e0af10dd207a63e2ac92d1c997
Reviewed by: @ma-laforge
Reference: https://github.com/ma-laforge/NumericIO.jl/commit/63c231f7c6f4d2e0af10dd207a63e2ac92d1c997#commitcomment-33858938
Release notes:

Add support for Project.toml
(Add support for Julia 1.1.1)

@ma-laforge consider using
[compat]
julia = "1"

instead of https://github.com/ma-laforge/NumericIO.jl/blob/63c231f7c6f4d2e0af10dd207a63e2ac92d1c997/Project.toml#L10 which is not true.

Could you explain why julia = "≥ 1.0.0" is not true?
I don't mind being pointed to the documentation.  I have been looking for it, but ended up basing my Project.toml from other projects.
Thanks.

It's just that you claim to be compatible with e.g. Juia 2.X, which will be a breaking release.


Configuration contain the url also

It would be better if the apidoc.php configuration would contain the url config param, because in Lumen there is no app.php config file, and that url is needed for the api doc generator.

Not sure I get you. Could you explain better?

Of course, if I want to generate useful example urls in documentation that include my domain, I have to configure the url config param, but now I can set it in the configure/app.php config file follow the instructions in the readme. I propose to be able to configure it in the config/apidoc.php, because this package use it to generate the url.


Update sbt to 1.4.5

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

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

labels: library-update, semver-patch

Codecov Report

Merging #309 (2a83ad2) into master (1c30adf) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #309   +/-   ##
=======================================
  Coverage   99.51%   99.51%
=======================================
  Files           7        7
  Lines         410      410
  Branches       41       41
=======================================
  Hits          408      408
  Misses          2        2

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 1c30adf...2a83ad2. Read the comment docs.


Replacing the Buffer constructor

new Buffer(...) is deprecated and unsafe. Could it be replaced with Buffer.from(...) in these places?

just added a pull request fixing this as well

Fixed in #10


emp run tries to pull from Docker Hub even though using Quay.io

Hi everyone,
I setup an empire cluster using stacker 0.6.0 with the latest blueprints, using Quay.io as registry, and managed to deploy my applications. Everything works properly except the emp run command, which tries to pull from docker hub, whereas my original deployment is from Quay.io. This results in the following:
runner: pull: Error: image username/repo:tag not found

Empire seems to be trying to pull from Docker Hub despite DOCKER_REGISTRY being set to Quay.io in the seed file.
Sincerely yours,

Good catch. I'm 99% positive this is caused [here] (https://github.com/remind101/empire/blob/master/pkg/runner/runner.go#L73-L77), which doesn't duplicate the logic here (putting the registry portion in the Repository field). We should extract that into pkg dockerutil and re-use it for pulling.


Form pages responsiveness

We need to make the form pages responsive and theme friendly.

This was fixed with following commits: 4345e66034922d9b389f5d69add12926b9efc12e, 16e023fb880e64371f86250b479f0196a88954e5, c52226122d692e6f04d9425aeafeb7ad387d2a68 and others


Copy pasting does not work

Every time I copy paste and send a request, Insomnia treats the pasted text as empty.
Steps to reproduce:

Copy a URL
Create a new request or modify an existing request
Paste the URL to the request
Send the request
Click on another request and come back to the newly created/modified request. Notice that the URL is blank
Note: this behaviour also happens for request body, headers, etc. Also, if you type something after the text you copy pasted,  it would magically work.

Expected behavior
Copy pasting should work
Screenshots
Step 2.

Step 4.

Step 5.

Context
OS: Ubuntu 18.04.3 LTS
Insomnia version:

Hiya, this has been resolved in the latest release - 2020.3.3. Please update your client. 😊

I am experiencing the same error after upgrading to Insomnia 2020.3.0 (macOS Catalina 10.15.4)
Recording of copying and pasting values into headers and seeing them disappear:

Confirmed that issue is fixed in v2020.3.3!


USHIFT-1401: rebase should only clean up files it creates

We use the _output directory for tools and test files, which should
not be deleted when running a rebase.
/assign @pmtk

/lgtm


Since Laravel 5.0 "models" directory doesnt exist anymore

Depends. I have a models folder on my install.

For now we'll leave it as is. Thanks for the contribution.


[material-ui][Chip] Disable blur() event on escape key should be opt-in

Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch<EMAIL_ADDRESS>for the project I'm working on.

Here is the diff that solved my problem:
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index 5f9d12e..f0110dd 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -330,7 +330,7 @@ const Chip = /*#__PURE__*/React.forwardRef(function Chip(inProps, ref) {
       if (onDelete && isDeleteKeyboardEvent(event)) {
         onDelete(event);
       } else if (event.key === 'Escape' && chipRef.current) {
-        chipRef.current.blur();
+        // Commented out by httpete with patch-package chipRef.current.blur();
       }
     }
     if (onKeyUp) {

This issue body was partially generated by patch-package.
Search keywords:

Hey @httpete! thanks for reaching out
I added the waiting for upvotes label so the community can vote for this new feature.


oddity with delegation of isDebugEnabled

I have configured my underlying logger to debug log, but I'm not getting any output.
I then error logged a look at the logger and the underlying logger. The underlying logger says debug is enabled, but when I ask the KotlinLogger about debug, it says it is not enabled.
It's weird. I see in LocationIgnorantKLogger that it uses delegation to the underlying logger, but it doesn't seem to be working since the values differ.
Any thoughts on this?
logger.error { "logger.javaClass.simpleName = ${logger.javaClass.simpleName}" }
        logger.error { "logger.underlyingLogger.javaClass.simpleName = ${logger.underlyingLogger.javaClass.simpleName}" }
        logger.error { "logger.isDebugEnabled = ${logger.isDebugEnabled}" }
        logger.error { "logger.underlyingLogger.isDebugEnabled = ${logger.underlyingLogger.isDebugEnabled}" }

output:
ERROR: logger.javaClass.simpleName = LocationIgnorantKLogger
ERROR: logger.underlyingLogger.javaClass.simpleName = TinylogLogger
ERROR: logger.isDebugEnabled = false
ERROR: logger.underlyingLogger.isDebugEnabled = true

Can you please provide more details: versions, what is the underlying logger its configuration and ideally a small repo on github to reproduce it?

Is there any update on the issue?

I'm afraid I'm not going to be able to spend time following up on this.


Replace URL and use vscode.URI on local paths (#11624)

Use vscode.URI for local paths

Use vscode.uri file method to set the name for remotebookfull path compressed file

Add await on extract tar function

Replace remote paths too

Use vscode.uri.file instead of parse for local paths

This PR fixes #11602

Coverage increased (+2.5%) to 40.279% when pulling b5560b6260d01c72f207b3ce3a155e33fb0d12b8 on bavaldez-release/1.21 into dc3b5df0479ed6d12b496caae5744654381d6485 on release/1.21.


REDACT password when test user is created

Hi,
Currently when test user is created by admin, username and password is logged in test output. This is not issue if user is deleted after test runs but if the tests are using test_password because operators have password policy set on their CF deployment, it would be easy to discover a password that meets the policy criteria.
Regards
Shash

Hey @shashwathi, thanks for finding this. I managed to get the password to leak. I'll use this issue as a story to redact the password.

@dsabeti is this done?

@rosenhouse, yes it is. It looks like I forgot to close the issue after accepting the story. Thanks for following up!


TFBootstrap Deployment

Todo

Develop procedures to

deploy TFBootstrap (how to install new node)

Related issue

See tfgrid validator stack main project issue for overview

in progress: https://github.com/threefoldtech/tf_operations/issues/2113

Bootstrap is actually quite different:

There is no database (except a legacy sqlite for mac address not used anymore AFAIK)
There are a on-the-fly iPXE bootloader compilation executed to ship a bootloader customized with farmerid inside
A directory which contains all the kernel available / we used

I think i got it almost working based on https://github.com/threefoldtech/0-bootstrap , but have some questions before documenting everything.
https://bootstrap.grid.tf/

Got it fully working with the help of Maxime, now documenting and finding a way to deploy it easily with the rest of the stack

Thanks for the update @coesensbert. And thanks @maxux for the work too.
You can make some basic documentation with the necessary steps then I can take it from there and make some official documentation, if that can save you some time.

Thanks @Mik-TF but not yet, the docs I have now are raw things to run the service with python etc .. I had no idea how to run it, now I do. @maxux will first make a container out of it, publish it in ghcr and then I will make a compose file for it. Once that works and is tested, I will write docs on how to deploy with compose (and the possible accompanied scripts) and then you can push that to the manual and improve. If that's ok.

That's a perfect plan IMO. Thanks!

Some WIP in info_grid: https://github.com/threefoldtech/info_grid/pull/598

bootstrap added to hub compose files:
https://github.com/threefoldtech/grid_deployment/commit/57582ce48e66aa15bb8f95eda5c33b55822d6067
https://github.com/threefoldtech/grid_deployment/commit/d2f22e91595cd295639ffb721a3260804614c202
https://bootstrap.ninja.tf/
test instance has an issue where link generation leads one to https://0-bootstrap:5555

Can we set that by default the docker-compose of the bootstrap generator downloads the last year of all kernels?
Via the tool here: https://github.com/threefoldtech/0-bootstrap/blob/development-v3/tools/kernel-sync.py

done: https://github.com/threefoldtech/grid_deployment/blob/development/grid-hub/install-hub.sh#L57-L59
POC: https://bootstrap.ninja.tf/images
changing the text will have to happen before creating the image I believe, so you'll have to request that on the hub repo

all issues resolved, we got a working release: https://github.com/threefoldtech/grid_deployment/tree/development/grid-hub
Need to write docs next

You rock. Good job.
LMK if you need help for the docs.

https://github.com/threefoldtech/grid_deployment/tree/development/grid-hub

all docs finished: https://github.com/threefoldtech/grid_deployment/blob/development/grid-hub/readme.md
Thx @maxux for all the help!
deploying two new read-only instances: https://github.com/threefoldtech/tf_operations/issues/2733


Fix NuGet Package Multitarget

Fixes NuGet package issue where global tool will not always attempt to run with a matching framework when attempting to build a project with multiple target frameworks.

This was tested with local builds. Waiting for build pipeline to complete so I can verify the fix.

@daalcant can you add a change log update as well?

@daalcant can you add a change log update as well?

Thanks for the reminder! Will do.


possible self breach case

Your environment

version of lnd: 0.5.2-beta commit=v0.5.2-beta
which operating system (uname -a on *Nix): CentOS 6
version of btcd, bitcoind, or other backend 0.17.1

The user DEREC contacted in Slack channel with me. After a careful study of what he wrote, I was horrified, to be honest. My node LND-21 broadcasted old state of channel and his node broadcasted breach transaction. After the funds (2M satoshies) was sent to his node. After my investigation i found that the node was not stopped and not restarted in that day. So old state of channel was broadcated by LND by not-catched bug i think. And after investigation of logs i didn't found some warnings about this case! In my side this to be viewed as force closing of channel!
Please help to me: what symptomps in my logs may indicate such situations?
I attached his state of channel, transactions and my logs:
From his side:
Then :lncli closedchannels
{
   "channels": [
       {
           "channel_point": "c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d:0",
           "chan_id": "618156432394223616",
           "chain_hash": "000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f",
           "closing_tx_hash": "35008a2b6182431ca635960349a6901b98891b5ef19450753569fe56e7ed1dfd",
           "remote_pubkey": "02c91d6aa51aa940608b497b6beebcb1aec05be3c47704b682b3889424679ca490",
           "capacity": "2000000",
           "close_height": 565348,
           "settled_balance": "45",
           "time_locked_balance": "0",
           "close_type": "BREACH_CLOSE"

From my side:
2019-02-08 21:11:14.757 [INF] FNDG: Target commit tx sat/kw for pendingID(1d4aa3bb6086ffc296c057bdf255d93356ec2d4ff3820eb5874741300841dda3): 3769
2019-02-08 21:11:14.757 [INF] FNDG: Starting funding workflow with <IP_ADDRESS>:9735 for pendingID(1d4aa3bb6086ffc296c057bdf255d93356ec2d4ff3820eb5874741300841dda3)
2019-02-08 21:11:18.004 [INF] FNDG: Recv'd fundingResponse for pendingID(1d4aa3bb6086ffc296c057bdf255d93356ec2d4ff3820eb5874741300841dda3)
2019-02-08 21:11:18.007 [INF] FNDG: pendingChan(1d4aa3bb6086ffc296c057bdf255d93356ec2d4ff3820eb5874741300841dda3): remote party proposes num_confs=3, csv_delay=240
2019-02-08 21:11:18.007 [INF] FNDG: Generated ChannelPoint(c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d:0) for pendingID(1d4aa3bb6086ffc296c057bdf255d93356ec2d4ff3820eb5874741300841dda3)
2019-02-08 21:11:18.184 [INF] FNDG: Broadcasting funding tx for ChannelPoint(c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d:0): (*wire.MsgTx)(0xc0580f14c0)({
2019-02-08 21:11:18.184 [INF] LNWL: Inserting unconfirmed transaction c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d
2019-02-08 21:11:18.190 [INF] CNCT: Creating new ChannelArbitrator for ChannelPoint(c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d:0)
2019-02-08 21:11:18.191 [INF] CNCT: ChannelArbitrator(c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d:0): starting state=StateDefault
2019-02-08 21:11:18.192 [INF] NTFN: New spend subscription: spend_id=244, outpoint=c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d:0, height_hint=562191
2019-02-08 21:11:18.206 [INF] FNDG: Finalizing pendingID(1d4aa3bb6086ffc296c057bdf255d93356ec2d4ff3820eb5874741300841dda3) over ChannelPoint(c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d:0), waiting for channel open on-chain
2019-02-08 21:11:18.206 [INF] CNCT: Close observer for ChannelPoint(c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d:0) active
2019-02-08 21:11:18.206 [INF] NTFN: New confirmation subscription: txid=c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d, numconfs=3
2019-02-08 21:11:18.206 [INF] FNDG: Waiting for funding tx (c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d) to reach 3 confirmations
   PreviousOutPoint: (wire.OutPoint) c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d:1,
2019-02-08 23:25:45.627 [INF] LNWL: Marking unconfirmed transaction c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d mined in block 562210
2019-02-08 23:40:48.222 [INF] NTFN: Dispatching 3 conf notification for c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d
2019-02-08 23:40:48.222 [INF] FNDG: ChannelPoint(c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d:0) is now active: ChannelID(3db9473242cbf83e2e4efc2323aa614e71d1fbcfff70680afaf0ef4ed3691dc6)
2019-02-08 23:40:52.455 [INF] CRTR: New channel discovered!  Do this do the LND? If the LND has a new commitment transaction the previous transaction should be removed from memory immediately, right?

Can the phrase "Unprompted commitment broadcast" to be as symptom of breach from my side for remote node? If yes i see many same phrases in logs by grep... Please help to define same situations in log files.

What kind of storage do you use on the nodes? Do you modify the on disk storage at all during normal operation of the node?
That log message just means that the remote party did a unilateral close.

What kind of storage do you use on the nodes? Do you modify the on disk storage at all during normal operation of the node?

This server has only one SSD disk: 512GB SSD Samsung 840 PRO
I have backups to other server through rsync (only readonly of course) but in that day i am not even logged to server.
I think blaming the disc in this case is the last thing.

That log message just means that the remote party did a unilateral close.

Yes, i see. So because i asked to you how define by logs this breach from my side? In any case, what happened happened. And this is confirmed on both sides.
Addition info:
The next transaction after funding one was 35008a2b6182431ca635960349a6901b98891b5ef19450753569fe56e7ed1dfd. I see this transaction in LND-21 side in listchaintxns as:
{
    "tx_hash": "35008a2b6182431ca635960349a6901b98891b5ef19450753569fe56e7ed1dfd",
    "amount": "0",
    "num_confirmations": 744,
    "block_hash": "00000000000000000018de36a61e553db5c2872d23a57466b1da9667fe9f1dfe",
    "block_height": 565348,
    "time_stamp": "1551532535",
    "total_fees": "0",
    "dest_addresses": [
        "bc1qxnxqjw237pd9th6ztd3tqaaemuh2nrr7e38g4hjdhnd3y9fs9wwq6cp3my"
    ]
},

There is amount is "0" so i understood this as penalty. The next transaction in blockchain is 65614f140e8845c9b0ce1271f9e44e1cb398574f4cca762e3bec6444c0decf14. I see this transaction in listchaintxns too as:
{
    "tx_hash": "65614f140e8845c9b0ce1271f9e44e1cb398574f4cca762e3bec6444c0decf14",
    "amount": "0",
    "num_confirmations": 745,
    "block_hash": "0000000000000000001bc3aded57fa2959eb1251c29b9eb10bbb8a6ae2d83169",
    "block_height": 565349,
    "time_stamp": "1551532690",
    "total_fees": "0",
    "dest_addresses": [
        "bc1qtpxaqqft7jrv8jzfh7f3yyc2ecyxjvaf70hejs"
    ]
},

There is amount is "0" too. The next TX f939caff81816356c31fb71b1db8bdf18d5fc12cf1f24007a3c3e43969c6b799 my LND wallet doesn't see. It's right because it was not controlled by my node. It's full penalty.

I think blaming the disc in this case is the last thing.

I ask as it appears that the on-disk state and the in-memory state diverged. All operations to modify this state are synchronized, and there's a durability assumption in all the writes. From what I gather:

We update the on disk state to store commitment n+1
The in-memory state is updated to store commitment n+1
We try to force close, and read the state from disk, but we get commitment n
During the force close, we see that what was confirmed wasn't our on disk state of n+1, but was n, so we assume it was the remote party force closing

May be this will help
2019-03-02 14:06:46.639 [INF] HSWC: ChannelLink(c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d:0) is stopping
2019-03-02 14:06:46.739 [INF] HSWC: ChannelLink(c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d:0) has exited
2019-03-02 14:06:46.741 [INF] CNCT: Broadcasting force close transaction, ChannelPoint(c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d:0): (*wire.MsgTx)(0xc0b289b340)({
 Version: (int32) 2,
 TxIn: ([]*wire.TxIn) (len=1 cap=1) {
  (*wire.TxIn)(0xc092cf8d20)({
   PreviousOutPoint: (wire.OutPoint) c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d:0,
   SignatureScript: ([]uint8) {
   },
   Witness: (wire.TxWitness) (len=4 cap=4) {
    ([]uint8) <nil>,
    ([]uint8) (len=72 cap=144) {
     00000000  30 45 02 21 00 fc 6a 40  91 95 2e 6e 46 b4 5d 88<EMAIL_ADDRESS>     00000010  29 55 01 d8 cf 4c 46 eb  cf 44 ff cd e3 ea 1d 8b  |)U...LF..D......|
     00000020  b0 ef e8 d8 6d 02 20 11  a5 c1 c5 6b 29 12 5b 98  |....m. ....k).[.|
     00000030  0e 60 fe 94 03 86 4c 61  d3 b3 d0 90 20 c4 20 1d  |.`....La.... . .|
     00000040  d6 dd 73 f7 df a8 9e 01                           |..s.....|
    },
    ([]uint8) (len=71 cap=144) {
     00000000  30 44 02 20 3e 13 e1 32  75 ed 07 c3 79 da ab 09  |0D. >..2u...y...|
     00000010  83 22 e2 d8 09 b5 e9 30  ef 18 2a 6f 3d 45 e4 37  |.".....0..*o=E.7|
     00000020  d0 c1 0a df 02 20 49 ad  62 a5 32 96 ae 6d e1 82  |..... I.b.2..m..|
     00000030  e9 74 c8 90 b4 9c 5c 33  5c d1 83 c6 73 86 06 86  |.t....\3\...s...|
     00000040  3a ba b8 60 77 34 01                              |:..`w4.|
    },
    ([]uint8) (len=71 cap=500) {
     00000000  52 21 02 56 74 38 60 e6  8b d6 15 e4 b1 5f 2b c4  |R!.Vt8`......_+.|
     00000010  18 33 9e 50 cb c2 1f e2  7b fc 2c de 47 fd f4 22  |.3.P....{.,.G.."|
     00000020  2c d8 47 21 02 6c 54 c6  51 25 16 6b 47 fa 66 a5  |,.G!.lT.Q%.kG.f.|
     00000030  3a 65 2f 7a a8 6d ad 31  eb 06 41 9a a6 14 ab 0b  |:e/z.m.1..A.....|
     00000040  ac 40 35 81 9d 52 ae<EMAIL_ADDRESS>    }
   },
   Sequence: (uint32)<PHONE_NUMBER>
  })
 },
 TxOut: ([]*wire.TxOut) (len=1 cap=1) {
  (*wire.TxOut)(0xc07ac8db60)({
   Value: (int64) 1996301,
   PkScript: ([]uint8) (len=34 cap=34) {
    00000000  00 20 34 cc 09 39 51 f0  5a 55 df 42 5b 62 b0 77  |. 4..9Q.ZU.B[b.w|
    00000010  b9 df 2e a9 8c 7e cc 4e  8a de 4d bc db 12 15 30  |.....~.N..M....0|
    00000020  2b 9c                                             |+.|
   }
  })
 },
 LockTime: (uint32) 542063054
})

2019-03-02 14:06:46.741 [INF] LNWL: Inserting unconfirmed transaction 35008a2b6182431ca635960349a6901b98891b5ef19450753569fe56e7ed1dfd
2019-03-02 14:06:46.774 [INF] CNCT: ChannelArbitrator(c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d:0): noop trigger chainTrigger

During the force close, we see that what was confirmed wasn't our on disk state of n+1, but was n, so we assume it was the remote party force closing

It happened in anyway from the remote party force closing because:

I was not logged to server in that day and i didn't force closing

I didn't use any API in that time

So remote side made force closing. May be i had autopilot as active but i am not sure (i think in that time the autopilot was turned off there). But i think in anyway your autopilot doesn't force channels. Therefore, it may be the following: remote side did force closing, my LND saw this and issued the last transaction (above) but this transaction was as previous state commitment transaction for the remote side and the remote side already had signed by my LND the breach transaction for my whoe funds. So in that time the remote side immediately after this had published the breach transaction. Right?

The remote side didn't force close, you did. It was closed due to an
expired HTLC likely.
On Thu, Mar 7, 2019, 2:37 PM LNBIG.com Project<EMAIL_ADDRESS>wrote:

During the force close, we see that what was confirmed wasn't our on
disk state of n+1, but was n, so we assume it was the remote party force
closing

It happened in anyway from the remote party force closing because:

I was not logged to server in that day and i didn't force closing
2.
I didn't use any API in that time
So remote side made force closing. May be i had autopilot as active but i
am not sure (i think in that time the autopilot was turned off there). But
i think in anyway your autopilot doesn't force channels. Therefore, it may
be the following: remote side did force closing, my LND saw this and issued
the last transaction (above) but this transaction was as previous state
commitment transaction for the remote side and the remote side already had
signed by my LND the breach transaction for my whoe funds. So in that time
the remote side immediately after this had published the breach
transaction. Right?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/lightningnetwork/lnd/issues/2741#issuecomment-470726333,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA87Ln2knr6bzwtWjdA0bEUQlaEhjxW7ks5vUZSOgaJpZM4bjw1x
.

The remote side didn't force close, you did. It was closed due to an expired HTLC likely.

I did not consider this option. And how did you determine that it was due an expired HTLC?
Ok, may be due an expired HTLC... And what is next? I checked now the kernel logs - i didn't have any
problems with disk. The LND was started:
2019-02-19 10:09:26.749 [INF] LTND: LightningWallet opened
2019-03-04 19:35:50.259 [INF] LTND: LightningWallet opened

Between these intervals this bug occured: 2019-03-02 14:06:45.182
If I could identify such situations from log files I would look for them. But I do not know how to do it. Only if I will sum up all satoshies. But i have many pending channels with unexisted transactions (it's other bug i already wrote this) so i will get incorrect sums. I did by manually the sum of all satoshies from opened channels, pending ones and from list of wallet transactions. So i think it was one same case in LND-21. But there is difficult to do it same with other nodes.
Please don't close this ticket. I found the two closed channels with same status BREACH_CLOSE from my side already. I think the bug is there. But he doesn't captured.

These BREACH_CLOSE channels from my side are:
{
"channels": [
    {
	"channel_point": "b94043dd3a64a7981edf43f22c224388c399109b084ae422347957018d3cede8:1",
	"chan_id": "618243293758619649",
	"chain_hash": "000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f",
	"closing_tx_hash": "857ae48df1e9ae5b13087c72838d4221a1bee258989cba8c8b57e6640952066f",
	"remote_pubkey": "02ad6fb8d693dc1e4569bcedefadf5f72a931ae027dc0f0c544b34c1c6f3b9a02b",
	"capacity": "354936",
	"close_height": 565192,
	"settled_balance": "123",
	"time_locked_balance": "0",
	"close_type": "BREACH_CLOSE"
    }
]
}

And from LND-31:
$ l closedchannels --breach
{
"channels": [
    {
	"channel_point": "0628bbbd9091d447f0f897a4762e6ac698c44a9a68caf6166e79920b09461593:1",
	"chan_id": "615344981066383361",
	"chain_hash": "000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f",
	"closing_tx_hash": "984f9919fb4a23eea64c20113bdd15468369810f0bece610a312dc9b80bbd78e",
	"remote_pubkey": "02e6a169b0826dfea51ee8bb81f629ec7445b267ef36354f2dd5012e1e8b69088c",
	"capacity": "281197",
	"close_height": 563951,
	"settled_balance": "0",
	"time_locked_balance": "0",
	"close_type": "BREACH_CLOSE"
    }
]
}

We know it was an HTLC expiry due to this line:
2019-03-02 14:06:45.182 [INF] CNCT: ChannelArbitrator(c61d69d34eeff0fa0a6870ffcffbd1714e61aa2323fc4e2e3ef8cb423247b93d:0): force closing chan

@LNBIG-COM would you by chance be able to provide full logs during that start of LND? I'm curious to see what else was going on in the daemon at the time. You can send them on slack if you don't wish to post here

@LNBIG-COM would you by chance be able to provide full logs during that start of LND? I'm curious to see what else was going on in the daemon at the time. You can send them on slack if you don't wish to post here

No problem. I will bring. Do you need logs of start before this problem (2019-02-19 10:09:26.749) or after (2019-03-04 19:35:50.259)? And i can send to you to email because the log file can be big. I can bring to here if you need only some first log lines.

Here all logs from begining up to present time
https://drive.google.com/file/d/1__OF47DEWvurfqW1Aj2pHgAmFfdbyu4-/view?usp=sharing
The file gzipped and encrypted by key B8BD8132 / 5ADFB098 (Olaoluwa Osuntokun laolu32@gmail.com). This key you use for release signing.

I would be interested to see them.

I have backups to other server through rsync (only readonly of course) but in that day i am not even logged to server.

I'd recommend you stop doing this, as it's possible that rsync will mutate the source file if it's being updated while rsync is running.

I have backups to other server through rsync (only readonly of course) but in that day i am not even logged to server.

I'd recommend you stop doing this, as it's possible that rsync will mutate the source file if it's being updated while rsync is running.

For example: the machine A is working LND, the machine B is backup server. If i do at B:
rsync -az bitcoin@A:./.lnd/ ./backup/./lnd/

In this case the rsync in machine B cannot affect files in machine A because the instance of rsync at machine A only read files and states. Everywhere in the world backups work same way (and mirorring).

Meant the target file (to be copied) not the source file.

Fixed by #2749.


Error message is not clear enough

Repro Steps:
• Navigate to https://makecode.microbit.org/beta
• Drag "show number" block, "length of array" block and "create array with" block
• Put them together and change "234" to "AAA" on block "create array with"
Expect Result:
The error message should be more clear
Actual Result:
The error message is not clear enough and shows as "cannot find name NAN"

close as not repro


Support more than one logical operator for pattern

Description:
There are multiple requests from community users on $subject in https://github.com/siddhi-io/siddhi/issues/1611 , https://github.com/siddhi-io/siddhi/issues/1610 and https://github.com/siddhi-io/siddhi/issues/1461.  We need to revisit the pattern implementation/design of Siddhi to achieve this.

In #1461 and #1610 some workarounds are given for rewriting queries...but after checking with the simple pattern A and B and C the workaround seems not to be working for me:
define stream A (value int);
define stream B (value int);
define stream C (value int);

@sink(type='log')
define stream output(msg string);

from every A and B select "A and B" as msg insert into o1;
from every o1 AND C select "A and B and C" as msg insert into output;

I have verified that the above app is not detecting A, B, and C in any order as expected. For example, the output is not emitting any event for the following inputs:
c1 b1 a1
a1 c1 b1
b1 a1 c1

which looks like a bug to me. I was expecting the above app to detect any possible permutation for A, B and C...can you confirm whether there is a bug here @mohanvive ?

@mohanvive There are basically two workarounds that have worked for me so far:

Generating all the permutation patterns as discussed in #1610 (and along the lines of the match_recognize permute operator, see this):

from A -> B -> C select "A and B and C" as msg insert into output;
from A -> C -> B select "A and B and C" as msg insert into output;
from B -> A -> C select "A and B and C" as msg insert into output;
from B -> C -> A select "A and B and C" as msg insert into output;
from C -> A -> B select "A and B and C" as msg insert into output;
from C -> B -> A select "A and B and C" as msg insert into output;

Using an in-memory table:

define table tableABC(id string);

-- Update state
from A select "A" as id update or insert into tableABC on tableABC.id == id;
from B select "B" as id update or insert into tableABC on tableABC.id == id;
from C select "C" as id update or insert into tableABC on tableABC.id == id;

-- Check conditions on arrival of events
from A[("A" == tableABC.id in tableABC) and ("B" == tableABC.id in tableABC) and ("C" == tableABC.id in tableABC)] select "A and B and C" as msg insert into outputs;
from B[("A" == tableABC.id in tableABC) and ("B" == tableABC.id in tableABC) and ("C" == tableABC.id in tableABC)] select "A and B and C" as msg insert into outputs;
from C[("A" == tableABC.id in tableABC) and ("B" == tableABC.id in tableABC) and ("C" == tableABC.id in tableABC)] select "A and B and C" as msg insert into outputs;

Overall I think option 2 is preferable, since it scales linearly with the number of conditions, whereas option1 requires n! pattern queries in the general case (6 for the case at hand, n=3).
I don't know how the support for multiple logical operator patterns will be implemented, but maybe the table approach in option 2 can provide some guidelines.

We can use patterns to achieve this A and B and C within 15 mins
define stream RegulatorStream(roomNo int, deviceId long)
define stream tempStream (value int);
define stream tempStream1 (value int);
@sink(type='log')
define stream output(msg string);
from RegulatorStream[roomNo == 24]
select 0 as value
insert into tempStream;
from RegulatorStream[roomNo == 25]
select 1 as value
insert into tempStream;
from RegulatorStream[roomNo == 26]
select 1 as value
insert into tempStream1;
from every e1 = tempStream ->  e2 = tempStream[(e1.value == 0 and e2.value == 1) or (e1.value == 1 and e2.value == 0) ] within 15 mins
select 0 as value
insert into tempStream1;
from every e1 = tempStream1->  e2 = tempStream1[(e1.value == 0 and e2.value == 1) or (e1.value == 1 and e2.value == 0) ] within 15 mins
select "alert" as msg
insert into outputStream;

@suhothayan What is the current state? Could you please share your thoughts on how to deal with this issue?


forward slash before key is not correct

When adding the unique keys one should not add the forward slash, this gives an error in the Azure Portal. So from the example above just specify lastName or lastName,firstName

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bf261de8-a6fa-9497-ffff-106550e2a537
Version Independent ID: ee0468ba-1b3b-6ba4-d9f6-c60da3e7c486
Content: Unique keys in Azure Cosmos DB
Content Source: articles/cosmos-db/unique-keys.md
Service: cosmos-db
GitHub Login: @rafats
Microsoft Alias: rafats

@Sihomiri Thank you very much for the detailed feedback. I have assigned this to the content author to evaluate and update as appropriate.

test

@Sihomiri thanks for the feedback, and sorry for the delayed response. The unique key format is different based on the API you have used. If you have a Cosmos DB SQL API account, the forwardslash is required as shown in the

#please-close


Project applications should have details and links

Details linking to TOS and Glossary
Links to fix errors that come up during process

@Gratipay To apply for a "team" (2.0???), I apparently need to link a PayPal account, but don't see the option to do so.

https://twitter.com/untitaker/status/670667868133019649
Also e.g., if you don't have an email address:

400
Bad Request
You must have a verified email address to apply for a new Team.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Should be simple edit of https://github.com/gratipay/gratipay.com/blob/master/www/new.spt with /about/me links.

Also at https://github.com/gratipay/gratipay.com/issues/3654.

Nope, it's some other silliness with error code templates that I don't have time to figure out right now.

Related: https://github.com/gratipay/team-review/issues/126#issuecomment-164890133

As a future enhancement you might think about actually defining those terms out a little more (unless you already have this somewhere).

I apparently need to link a PayPal account, but don't see the option to do so.

This might actually be https://github.com/gratipay/gratipay.com/issues/3654, ya?

+1 from https://github.com/gratipay/team-review/issues/201#issuecomment-208356510

I thought by on-boarding you meant "how to use this."

I thought by on-boarding you meant "how to use this."

We did away with the onboarding links in #4222.

Details linking to TOS and Glossary

We already link to TOS, and the glossary doesn't exist yet (and is hopefully unneeded with #4221).

Links to fix errors that come up during process

Better addressed in https://github.com/gratipay/gratipay.com/issues/3654.
Closing.


Update dependencies.

Description
Update dependencies.
Test Coverage

[x] unit

References

N/A

Have released a new version subsequent to this update?

Not yet. Going to update dependencies again today and then publish.


9/03 PM Publish

Docs Build status updates of commit cfd6bd1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-6.3.0/install-az-ps.md
:white_check_mark:Succeeded
View (azps-6.3.0)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


add conda install instructions

cheers, thanks for building this cool model! I added the library to conda-forge to make it accessible to more folks. let's mention the conda install instruction in the readme :)

Nice thank you!


Fix new node metadata

Fix a couple of dangling issues with the NewNodeMetadata constructor pattern from a ~week ago.
Extracted from an upcoming branch.

@tomwilkie squashed and rebased, ready for your last pass.

LGTM


Ak and .chain names

#220

Firefox login with extension:

Start a new meeting: click on Go button

Wait a sec:

Click on Pop up —> Confirm button

Redirect to Prejoin screen with ak_address or .chain name

Click on Join meeting button

Redirect to the Room

Chrome login with Web wallet:

Start a new meeting: click on Go button

Click on Login with Web wallet button

Click on Confirm on Pop up (Send address to)

Click on Confirm on Pop up (Generate JWT token)

Redirect to Prejoin screen with ak_address or .chain name (avatar is visible)

Click on Join meeting button

Redirect to the Room

Firefox with iframe wallet:

Login with iframe wallet
Start a new meeting: click on Go button
Redirect to Prejoin screen

Seems that option to Join meeting with iframe Wallet doesn’t work...


Tag nodes

See https://github.com/stitchfix/hamilton/discussions/254

Need a commit message that informs of design decisions please.


read_ch_connectivity fails when channel has no neighbours defined.

I computed a neighbours structure for an EGI 256 electrodes layout using fieldtrip and tried to read that mat file with read_ch_connectivity.
Electrode 31 in my montage has no neighbours, so the entire function failed, at two places.

_recursive_flatten assumes the cell parameter passed has at least one element.

This is a possible fix (just added the if condition):
def _recursive_flatten(cell, dtype):
    """Unpack mat files in Python."""
    if len(cell) > 0:
        while not isinstance(cell[0], dtype):
            cell = [c for d in cell for c in d]
    return cell

_ch_neighbor_connectivity computes the set subtraction to raise an error:
rest = set(ch_names) - set_neighbors with the error "Some of your neighbors are not present in the list of channel names". In this case the error message and the operation do not match. The way I see it, it is an error only if the neighbours list has at least one electrode that it is not present in ch_names. If this is the point, then the operation should be rest = set_neighbors - set(ch_names)

Is there a reason this never made it to a pull request? The fixes LGTM.

Not a popular issue apparently... PR coming.


chore add back 'License Check' and 'Clang Formatter'

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


[Nord v3] font name emojis

Hi,
You use emojis / unicode characters in your waybar configuration.
I couldnt find the fontname in your configuration and installing various unicode/emoji fonts didnt help.
Could you tell me the name of the fonts you use?

found it here https://github.com/lokesh-krishna/dotfiles/issues/8


Does the community support adding myscaledb for performance testing

Myscaledb's official introduction states that its vector search is quite powerful.
And we don't know how it performs compared to Milvus in terms of performance.
Does the community support adding myscaledb for performance testing？

Anyone want to contribute and test on myscale is welcomed


Idea: our-cache add in cache indicator

Would be handy to be able to have a setting that displays when a block or page, or partial has been called from the cache for debugging purposes on none local envrionments

Hi @jaymarvels
How do you imagine this working? An example of markup or some more details will help me understand your needs better.

I was thinking something similar to how image resizer handled unlicensed products where it would place a red dot in one of the corners


[WIP] Add cargo-risczero build command

Work in progress command to build a selected crate for the RISC Zero target.
Wrote up this very basic version to help in developing a patch for the Rust Crypto crypto-bigint
crate.
Usage
Example of building a crate using this command
cargo run -p cargo-risczero -- risczero build --manifest-dir ~/risc0/rust-crypto/bigint/

Example of building tests (does not actually generate functional binaries right now)
cargo run -p cargo-risczero -- risczero build --test --manifest-dir ~/risc0/rust-crypto/bigint/

I tried a few things to track down why binaries, including tests, were getting built without a .text section. Starting from a new project with cargo new hello_cargo I got the following to partially work:
use risc0_zkvm as _;

fn main() {
    println!("Hello, world!");
}

#[cfg(test)]
mod test {
    #[test]
    fn pass() {}

    #[test]
    fn fail() {
        panic!("aaaaaaaaaahhhhhhhhhhh");
    }
}

I found that the key to getting something to be included in the resulting binary is to import risc0_zkvm, hence the otherwise useless use line at the top.
This also worked to get test binaries to be non-empty. Unfortunately, actually trying to run the resulting binary yielded the following.
cargo run -p risc0-r0vm -- --elf tmp/hello_cargo/target/riscv32im-risc0-zkvm-elf/release/deps/hello_cargo-e900338484bdc307
    Finished dev [optimized + debuginfo] target(s) in 0.14s
     Running `target/debug/r0vm --elf tmp/hello_cargo/target/riscv32im-risc0-zkvm-elf/release/deps/hello_cargo-e900338484bdc307`
thread 'main' panicked at 'time not implemented on this platform', target/rust-std_4f29d950e101936e934eafe043bfaa02f991c74575a6dfc8647c3c7fbbdede58/library/std/src/sys/zkvm/../unsupported/time.rs:13:9
thread 'main' panicked at 'internal error: entered unreachable code', risc0/zkvm/src/opcode.rs:168:22
stack backtrace:
   0: rust_begin_unwind
             at /rustc/0da281b6068a7d889ae89a9bd8991284cc9b7535/library/std/src/panicking.rs:575:5
   1: core::panicking::panic_fmt
             at /rustc/0da281b6068a7d889ae89a9bd8991284cc9b7535/library/core/src/panicking.rs:65:14
   2: core::panicking::panic
             at /rustc/0da281b6068a7d889ae89a9bd8991284cc9b7535/library/core/src/panicking.rs:115:5
   3: risc0_zkvm::opcode::OpCode::decode
             at ./risc0/zkvm/src/opcode.rs:168:22
   4: risc0_zkvm::exec::Executor::step
             at ./risc0/zkvm/src/exec/mod.rs:252:22
   5: risc0_zkvm::exec::Executor::run_with_callback::{{closure}}
             at ./risc0/zkvm/src/exec/mod.rs:184:42
   6: risc0_zkvm::exec::Executor::run_with_callback
             at ./risc0/zkvm/src/exec/mod.rs:226:25
   7: r0vm::main
             at ./risc0/r0vm/src/bin/r0vm.rs:99:9
   8: core::ops::function::FnOnce::call_once
             at /rustc/0da281b6068a7d889ae89a9bd8991284cc9b7535/library/core/src/ops/function.rs:251:5
             ````

Note on the above, it looks like the second panic is a bug in the executor, since an unreachable statement should not be reachable https://github.com/risc0/risc0/blob/8ce5105f35d3201de1bfcc71f159c9dc66539033/risc0/zkvm/src/opcode.rs#L168

So I was able to hack around the panic related to time by modifying the included standard library source. The second error happens when the guest program panics, which appears to currently trigger illegal instruction. Passing tests run without issue.

Trying to compile the tests for crypto-bigint, I currently have hit the following linker errors:
crypto-bigint:   = note: rust-lld: error: undefined symbol: __stack_init$
crypto-bigint:           >>> referenced by musl_memcpy.c
crypto-bigint:           >>>               risc0_zkvm-8bfe57008d2b9111.risc0_zkvm.9e8065e5-cgu.7.rcgu.o:(.text._start+0x8) in archive /Users/victorgraf/risc0/rust-crypto/bigint/target/riscv32im-risc0-zkvm-elf/release/deps/librisc0_zkvm-8bfe57008d2b9111.rlib
crypto-bigint:
crypto-bigint:           rust-lld: error: undefined symbol: __bss_begin
crypto-bigint:           >>> referenced by musl_memcpy.c
crypto-bigint:           >>>               risc0_zkvm-8bfe57008d2b9111.risc0_zkvm.9e8065e5-cgu.7.rcgu.o:(__start) in archive /Users/victorgraf/risc0/rust-crypto/bigint/target/riscv32im-risc0-zkvm-elf/release/deps/librisc0_zkvm-8bfe57008d2b9111.rlib
crypto-bigint:           >>> referenced by musl_memcpy.c
crypto-bigint:           >>>               risc0_zkvm-8bfe57008d2b9111.risc0_zkvm.9e8065e5-cgu.7.rcgu.o:(__start) in archive /Users/victorgraf/risc0/rust-crypto/bigint/target/riscv32im-risc0-zkvm-elf/release/deps/librisc0_zkvm-8bfe57008d2b9111.rlib
crypto-bigint:
crypto-bigint:           rust-lld: error: undefined symbol: __bss_end
crypto-bigint:           >>> referenced by musl_memcpy.c
crypto-bigint:           >>>               risc0_zkvm-8bfe57008d2b9111.risc0_zkvm.9e8065e5-cgu.7.rcgu.o:(__start) in archive /Users/victorgraf/risc0/rust-crypto/bigint/target/riscv32im-risc0-zkvm-elf/release/deps/librisc0_zkvm-8bfe57008d2b9111.rlib
crypto-bigint:           >>> referenced by musl_memcpy.c
crypto-bigint:           >>>               risc0_zkvm-8bfe57008d2b9111.risc0_zkvm.9e8065e5-cgu.7.rcgu.o:(__start) in archive /Users/victorgraf/risc0/rust-crypto/bigint/target/riscv32im-risc0-zkvm-elf/release/deps/librisc0_zkvm-8bfe57008d2b9111.rlib
crypto-bigint:           >>> referenced by musl_memcpy.c
crypto-bigint:           >>>               risc0_zkvm-8bfe57008d2b9111.risc0_zkvm.9e8065e5-cgu.7.rcgu.o:(__start) in archive /Users/victorgraf/risc0/rust-crypto/bigint/target/riscv32im-risc0-zkvm-elf/release/deps/librisc0_zkvm-8bfe57008d2b9111.rlib
crypto-bigint:
crypto-bigint:           rust-lld: error: undefined symbol: __main
crypto-bigint:           >>> referenced by musl_memcpy.c
crypto-bigint:           >>>               risc0_zkvm-8bfe57008d2b9111.risc0_zkvm.9e8065e5-cgu.7.rcgu.o:(__start) in archive /Users/victorgraf/risc0/rust-crypto/bigint/target/riscv32im-risc0-zkvm-elf/release/deps/librisc0_zkvm-8bfe57008d2b9111.rlib

Superseded by work currently in nils/cargo-risczero-test-spike


How to properly use the ROS-bag convert tool

|----------------------------------------|------------------------------------------- |
| Camera Model                        | D400                               |
| Firmware Version                   |  2.29.0                               |
| Operating System & Version  |  Ubuntu 18.04  |
| Kernel Version (Linux Only)    |  5.0.0-31                          |
| Platform                                  |  PC                                       |
| SDK Version                           |  2.0                                |
| Language                               |  C++/Python                              |
| Segment			         |  VR/AR                                     |
Issue Description
I am attempting to convert the RGB-D .bag file (recorded using the RealSense Viewer tool) to a sequence of RGB/D .png files. However, when I try to cmake the built-in conversion tool, I get the error:
CMake Error at CmakeLists.txt:28 (install): \tinstall TARGETS given no RUNTIME DESTINATION for executable target "rs-convert"
I changed the ${CMAKE_INSTALL_BINDIR} to a new build file I created, which results in no error, but the files aren't built when I run cmake.
Any tips for building this properly?

Somebody else who encountered this CMake error when changing the default build location fixed it by adding this line to the top of their cmakelists.txt file to "define some sensible defaults":
include(GNUInstallDirs)
https://github.com/leela-zero/leela-zero/issues/1901

@collinabidi hi, all the SDK's "CMaking" must refer to librealsense root directory, as defined in the installation guide. Invoking CMake from sub-directories will end up with missing properties as in the presented case.
#4747, #4335
Specifically for the rs-convert tool the -DBUILD_EXAMPLES=true flag should be configured.

Ah, I wasn't aware that the -DBUILD_EXAMPLES would include the tools.
I followed the installation guide and set the flag to true, but the rs-convert still doesn't appear in the /usr/local/bin file along with the other rs-* files created there.
Is there something else I'm missing?

Ah, never mind, I was able to locate it in the build folder. Thank you for the help!


example target name

Please, change example target name to something like kiui_example. Due to possible naming collision and easy lookup (default /usr/local/bin/example is not self-explaining. )

Fixed in the last commit


refactor: FreeImage dependency update

PR Details
This PR mainly removes the duplicate FreeImageNET source code, which is not used anywhere.
In addition, I decided to refactor code and remove the useless compatibility with System.Drawing.Bitmap, which is also not used anywhere.
Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[x] I have built and run the editor to try this change out.

There's a bunch of tabs/space mismatch in this PR, can't merge it as is sadly

Huh... Maybe Rider uses spaces instead of tabs when I fixed the warnings. Now I formatted with VSCode,  so I hope that will do

Thanks !


Fixed unnecessary map usage

➜ ruff check --select=C417
django/core/management/templates.py:121:32: C417 Unnecessary `map` usage (rewrite using a generator expression)
Found 1 error.

Rule description: https://docs.astral.sh/ruff/rules/unnecessary-map/
Why is this bad?
Using map(func, iterable) when func is a lambda is slower than using a generator expression or a comprehension, as the latter approach avoids the function call overhead, in addition to being more readable.

Already rejected in the #17649.


Consider moving from mutex to CAS in pubsub

In current code (in several places) the common impl of PubSub looks like this -
func (n *Net) SubscribeClosingConnections() chan Connection {
	n.clsMutex.Lock()
	ch := make(chan Connection, 20) // todo: set a var for the buf size
	n.closingConnections = append(n.closingConnections, ch)
	n.clsMutex.Unlock()
	return ch
}
 func (n *Net) publishClosingConnection(connection Connection) {
	n.clsMutex.RLock()
	for _, c := range n.closingConnections {
		c <- connection
	}
	n.clsMutex.RUnlock()
}

Instead we can replace with CAS on the slice's append

we need to understand if CAS suites this usecase better then mutex..

Marking as low priority since pubsub isn't used in production


To Adjust the address area in the contact page

Fixes:  #3054
Fixed the contaact form format and address div
Before:
https://github.com/user-attachments/assets/b3e0cfb8-cacf-4a4f-a6c4-c469d9312477
After:
https://github.com/user-attachments/assets/de2b69ab-1150-48fd-920a-e7dadf2b71e3
Checklist:

try to rework on this again like i want the image in contact section beside details @Shekhar-Raj

try to rework on this again like i want the image in contact section beside details @Shekhar-Raj
create new issue

Ya sure

@Shekhar-Raj someone has did it thanks for ur time :)

@Shekhar-Raj someone has did it thanks for ur time :)

Ok ☺

try to allign contact section and adress section in same width


Dist file generated in workspace, makes dist unusable

Description
There is this bug inside importBuild.cjs which is generated automatically here:
   const { setImportBuildGetters } = await import('${importPath}');,
In NPM workspace, node_modules/vike is located under root directory of the whole monorepo, which causes something of this sort:
const { setImportBuildGetters } = await import('../../../../node_modules/vike/dist/esm/node/runtime/globalContext/loadImportBuild.js');

Instead of resolving the location during build time, this could be modified as follows:
const loc = require.resolve("vike");
const basePath  = loc.split("node_modules/vike")[0];
const { setImportBuildGetters } = await import(`${basePath}node_modules/vike/dist/esm/node/runtime/globalContext/loadImportBuild.js`);

Or even better, loadImportBuild.js could be added to exports in package.json so that it can simply be imported like so:
const loc = require.resolve("vike");
const basePath  = loc.split("node_modules/vike")[0];
const { setImportBuildGetters } = await import('vike/dist/esm/node/runtime/globalContext/loadImportBuild.js');

For now, I am manually updating importBuild.cjs, as otherwise the import is just invalid when dist is deployed without the rest of the monorepo.

You aren't supposed to move node_modules/ into your production environement (e.g. $ rsync node_modules/ user@remote:/node_modules), instead you're supposed to run $ pnpm install and then $ pnpm run build in your production environment. The path in importBuild.cjs will then be correct.
I undertand this is very limiting (which I find unacceptable) and I'll be working on https://github.com/vikejs/vike/issues/562 and https://github.com/vikejs/vike/issues/1165 (which will solve the issue) right after the V1 design is out-of-beta.
Closing in favor of https://github.com/vikejs/vike/issues/562.
Until #526 is implemented I guess you can continue using your workaround?


Implementing secret scanning tools Gitleaks and Precommit

Description

Related ticket(s)

MDCT-

How to test

Important updates

Author checklist

[X] I have performed a self-review of my code
[X] I have added thorough tests, if necessary
[X] I have updated relevant documentation, if necessary

convert to a different template: test → val | val → prod

@braxex This one is ready too


runtime/pprof: new test TestLabelSystemstack is flaky

greplogs --dashboard -md -l -e 'TestLabelSystemstack':
2021-12-05T12:50:44-ecf6b52/freebsd-arm-paulzhol
2021-12-05T12:50:44-ecf6b52/linux-mipsle-rtrk
2021-12-04T17:16:07-3396878/freebsd-arm-paulzhol
2021-12-04T17:16:07-3396878/openbsd-mips64-jsing
2021-12-04T11:59:35-1876b38/freebsd-arm-paulzhol
2021-12-04T11:59:35-1876b38/openbsd-mips64-jsing
2021-12-04T04:50:55-549cfef/freebsd-arm-paulzhol
2021-12-04T01:07:21-821bf04/linux-386
2021-12-03T21:25:05-d20a0bf/linux-ppc64le-buildlet
2021-12-03T21:25:05-d20a0bf/openbsd-mips64-jsing
2021-12-03T16:11:38-9b0de08/linux-riscv64-unmatched
Test originally added in https://golang.org/cl/351751 for #48577 and reverted in https://golang.org/cl/360757 because it was extremely flaky. Re-added https://golang.org/cl/367200. It is much less flaky now, but still a bit flaky.
cc @felixge @bcmills

It looks like this is exposing a legitimate bug. Every one of these logs I've looked at looks something like this:
        1: 0x80ed151 (fmt.Fprintf:203) 0x817f28c (runtime/pprof.labelHog:1500) 0x817ec3b (runtime/pprof.TestLabelSystemstack.func2.1.1:1481) labels: map[]
        1: 0x80ece1b (fmt.newPrinter:140) 0x80ed14d (fmt.Fprintf:203) 0x817f28c (runtime/pprof.labelHog:1500) 0x817ec3b (runtime/pprof.TestLabelSystemstack.func2.1.1:1481) labels: map[key:[value]]
        1: 0x80f2ac0 (fmt.(*pp).doPrintf:1026) 0x80ed181 (fmt.Fprintf:204) 0x817f28c (runtime/pprof.labelHog:1500) 0x817ec3b (runtime/pprof.TestLabelSystemstack.func2.1.1:1481) labels: map[key:[value]]
        1: 0x80f355c (fmt.(*pp).doPrintf:1009) 0x80ed181 (fmt.Fprintf:204) 0x817f28c (runtime/pprof.labelHog:1500) 0x817ec3b (runtime/pprof.TestLabelSystemstack.func2.1.1:1481) labels: map[key:[value]]

Notice that the first entry is missing the label. Every runs seems to have the first sample missing the label. Perhaps we are dropping that somewhere?

😞 Sorry this is flaky again. I'll do some debugging now to see if I can figure out what's going on. Thanks for the details you provided @prattmic . Looks like there are no linux/amd64 failures so far?

I am looking as well to see if I can find the discrepancy.

Found the bug!
profBuf.write uses an index in b.tags for each entry, even if that entry has no tag (that slice entry just remains 0). profBuf.read similarly returns a tags slice with exactly as many entries as there are in data ("entries" in data may use multiple uint64s in that slice).
profileBuilder.addCPUData iterates through the tags in lockstep with the data entries. Except in the special case of the first record, where it forgets to increment tags. Thus the first read of profiling data has all tags off-by-one.
 I only got as far as verifying that the tagPtr is still in-tact when cpuprof.add(tagPtr, stk[:n]) gets called for the first sample :).
Given what you found, do you think this this will fix the test flakiness? Or would it just help with the tag accuracy of the first batch of samples?

Given what you found, do you think this this will fix the test flakiness? Or would it just help with the tag accuracy of the first batch of samples?

I'm not certain. I hope it is the only bug and perhaps could even resolve this TODO, but I don't know yet.

and perhaps could even resolve this TODO, but I don't know yet.

Just took your patch for a spin, and it looks very promising! I'd be happy to send a change for removing that TODO once your patch lands. Or feel free to make it part of your change if you think it's worth a shot.
https://gist.github.com/felixge/b3a2436035ccfc24d3a0aa0fe98b3c57

https://golang.org/cl/369984 is expected to fix this. Will file a new bug if more issues come up.

Will file a new bug if more issues come up.

Looks like there is at least one failure mode remaining — filed #50050.


Update CentOS 7

Regular update as image expires now

Checking the checksum may already be good, but it will likely result in a big download.
In the future we could try to instantiate the VM to be sure it works, like with some of your terraform magic, but not sure it's worth to spend/invest time in it right now.


Update EO to 0.36.0

PR-Codex overview
This PR updates the version to 0.36.0, changes package names, and improves object documentation and metadata.
Detailed summary

Updated version to 0.36.0
Changed package names
Improved object documentation and metadata

The following files were skipped due to too many changes: objects/org/eolang/switch.eo, objects/org/eolang/memory.eo, objects/org/eolang/tuple.eo, tests/org/eolang/tuple-tests.eo, tests/org/eolang/goto-tests.eo, tests/org/eolang/io/tupled-stdout-test.eo, tests/org/eolang/try-tests.eo, objects/org/eolang/cage.eo, objects/org/eolang/goto.eo, tests/org/eolang/io/tupled-stdout.eo, pom.sh, tests/org/eolang/float-tests.eo, tests/org/eolang/seq-tests.eo, tests/org/eolang/nan-tests.eo, tests/org/eolang/int-tests.eo, tests/org/eolang/bool-tests.eo, objects/org/eolang/negative-infinity.eo, tests/org/eolang/malloc-tests.eo, objects/org/eolang/positive-infinity.eo, tests/org/eolang/memory-tests.eo, tests/org/eolang/cage-tests.eo, tests/org/eolang/rust-tests.eo, tests/org/eolang/while-tests.eo, tests/org/eolang/runtime-tests.eo, tests/org/eolang/negative-infinity-tests.eo, tests/org/eolang/positive-infinity-tests.eo

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@yegor256 please check

@rultor merge

@rultor status

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor status

@yegor256 This is what's going on here:

request<PHONE_NUMBER> is in processing, command is merge
request has 6 parameter(s):
fork: git@github.com:maxonfjvipon/home.git
fork_branch: update-eo-to-0.36.0
head: git@github.com:objectionary/home.git
head_branch: master
pull_id: 225
pull_title: Update EO to 0.36.0
build is not running

More information about Rultor commands you can get here.

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 10min)


Regression(0.12.X): Revocation Notifications not getting emitted

It looks like #2558 introduced a bug where revocation notifications are no longer getting emitted when using the /revocation/publish-revocations endpoint. It seems to be fine when revocation is immediately published on revoke but if the issuer desires to batch them together and publish all pending revocations at once, no notifications are emitted to the holder connection.
This seems to be an issue in both 0.12.0 and 0.12.1rc0. Not sure why we didn't catch this one sooner :thinking:

Actually no, it wasn't #2558; it looks like it was #2812. @jamshale it looks like we might have deleted some notification emissions for so they could be handled in Askar-AnonCreds but maybe didn't account for the plain old Askar wallet case?

In particular, these lines: https://github.com/hyperledger/aries-cloudagent-python/pull/2812/files#diff-21df84291ab9a8290fcb3f396c10df170eb5c891236ad3a9dcbdec9df885749fL299-L302

I thought I removed this on purpose because I changed the flow to only notify after the revocation id's were written to the ledger instead of right when the endpoint was called. If this isn't happening, I must have messed something up. I can look. I thought I had covered this case.

@jamshale I think conditions of the deleted lines were such that it would only send that notification only if not using an endorser. It makes sense to only notify after the transactions are actually published in the endorser case but these lines were preventing the self-endorsed revocations to ever trigger a notification, I think.
See #2916; the changes in that PR get things working for me again

In case it's useful, I used this minimal example to reproduce and diagnose the issue: https://github.com/Indicio-tech/acapy-minimal-example/tree/main/examples/presenting_revoked_credential
With the image of alice pointing to 0.12.1rc0. docker-compose run example to actually run it.

Ughh. I think that must have been the issue. I was trying to fix the problem where using an endorser didn't send revocation notifications. This was introduced and then fixed for 0.11.0. I must have overlooked the self-endorsed case and got trigger happy here.


Sensor temperature missing unit of measure

I am running the latest pyloxone with latest firmware <IP_ADDRESS> and for the temperature sensor the unit of measure is missing hence its not showing a graph in home assistant
no issues with the humidity sensor.
see screenshot below of temperature sensor

@elRadix
Have you setup a unit in the loxone for the sensor like you did it with the hum sensor?
you must leave a blank for the unit something like %.2f C°

@JoDehli it is new brand new installation, all settings are default (<v.1>) for the temperature sensors, the humidity sensor is also set by default to  %
I have changed these temperature units to <v.2>C° and its working now.
had to delete home assistant DB to get he new graphs direclty visible


Bad linky on pypi page

Hi,
nice to see slovak stemmer, but on Python package index is bad link to homepage:
https://github.com/mrshu/mrshu/stemm-sk
krásny zvyšok dňa ;)

@slavkoja Thanks a ton.
I fixed this is f3d2e181fd1d2eb473ca840184b65e918d8eea86 and a new version should already by live on PyPI (https://pypi.python.org/pypi/stemmsk).
The stemmer is in a very early stage, I am very open to contributions of any kind =)
Thanks again!


download from node-versions and fallback to node dist

Node distributions are now available from https://github.com/actions/node-versions for reliability since the releases are backed by a CDN.  That repo offers a versions-manifest.json which abstracts away the location of each version.  Therefore in the future it could move from releases to some other CDN or endpoint.  This set of changes queries the versions-manifest against the node version semver spec provided by the workflow to resolved to latest for that spec.  If not found in the versions-manifest, it falls back to the node dist ( https://nodejs.org/dist/index.json )

https://github.com/actions/setup-node/pull/147


Variable names as a function crashes oslc

Hi,
Originally was reported to the Blender's bug tracker [1] but this issue can be reproduced with the current oslc (compiled from 5c8c973).
Easy to reproduce:
Create test.osl with the following content:
void bug(float cos){cos(1);}
shader test(){}

and try to compile it using oslc.
[1] https://developer.blender.org/T49597

Fix proposed in #684

Checked it locally here just because.. Works fine, thanks for a quick fix :)
Any particular steps from our side to be done to move forward?

I'm also merging this into RB-1.7.
It'll be in the next set of point releases I do at the end of the month. (It doesn't seem critical enough to make an off-schedule release just for that.)


Settle-free testing

This PR is (Yet Another) experiment in making tests simpler to write. The testing mechanism introduced here runs settles when needed, so that a test writer never needs to write a Settle himself. Tools for synchronizing processes are also introduced. The downside? Use of side effects in process code needs to be restricted to provided primitives, because the process runtime restarts processes behind the scenes (effectively, backtracks them) when synchronization fails.
How is it different from the current way of testing?

Coroutine syntax (async/await) is used instead of generator syntax (yield). This makes the code cleaner in my opinion.
No uncontrolled side effects in processes. This includes modifying global variables, queues, and others; however, controlled replacements for these are provided. Debug prints work, but they may be written multiple times per cycle because of backtracking.
The process code is executed completely once per cycle, there is no primitive for waiting a cycle (like yield was doing previously). I'd very much like to have this feature, however - because there is no simple way to implement a nondeterminism effect in Python's coroutines - this can't really be done without making the syntax awful. As most of our testing code is basically in method mocks, this isn't a big limitation.
Signal writes are provided in two varieties:

Instantaneous writes (like blocking assignment in Verilog); written values are visible by other processes in the same cycle. If there are other signals which depend on the written signal in the simulated circuit, changes are automatically propagated (no settles!).
Final writes (like nonblocking assignment in Verilog); written values are visible in the next cycle.

Writes are restricted so that only one process can write a given signal in a clock cycle, and it can do it only once. This is to guarantee that inter-process dependencies are correctly resolved.
Two synchronization primitives are provided: signals and FIFOs.

Behavior of signals mirror Amaranth signals, but they are handled by the simulation runtime and can contain arbitrary values. They can be used to store state, and also to synchronize processes (as an instantaneously written value is guaranteed to be seen by processes in the same clock cycle).
FIFOs allow a single push and pop in a given clock cycle. In doing so, they mirror the behavior of in-circuit FIFOs.

TestbenchIO is not used; instead, method calling and mocking are reimplemented.

As you can see in the tests I've rewritten to use this new mechanism, tests look mostly like before - but there are no Settles and sched_prios. One can use as many FIFOs, method calls etc. in each process as one wants, and as long as there is no dependency cycle, everything should work just fine.
To-do:

[ ] Minor cleanups. The main simulation code still has some copy-pastes and needs to be refactored a little.
[ ] Performance improvements. The new mechanism has some performance loss compared to the old one. On my computer, the old retirement test took ~0.75 s, the new one took ~0.95s, a 25% loss. It should be possible to reduce it by scheduling processes in such a way that the number of internal Settles and backtracks are minimized.
[ ] Assertions. It turns out failure is a side effect ;) Currently, consistency is enforced by waiting for values to become stable before calling asserts. This is possibly error-prone, as one must remember to insert the wait. Edit: maybe introduce a read-only phase for processes?
[ ] Code organization. I'm not sold on all these static methods, but I have no better idea right now.
[ ] Documentation.

What do you think? Can this save us from the test hell?

So we're making tests behave more like hardware? ;)
Before I look at the code, I have some initial objections:

Debug prints work, but they may be written multiple times per cycle because of backtracking.

Debug prints are essential part of debugging tests - having them saved me countless times. Maybe you could provide "controlled replacement" for these too (I'm thinking of a queue type thing where if you backtrack, prints from the "wrong" branch are removed, but when correct path is finally resolved they're printed in the order that follows the expected semantics)

As most of our testing code is basically in method mocks, this isn't a big limitation.

I disagree. Some of our tests rely on being able to explicitly yield so this requirement seemingly disqualifies the use of your solution in them. Though a workaround that I have in mind are processes that work like continuations - one process does small part of the processing, inserts results (or unit value or whatever) into a 1-FIFO and another process can pop from the FIFO in the next cycle (emulating yield that way) and do the next processing step. This requires that a process isn't run in a cycle where it can't write to a FIFO - no idea if this can be reasonably implemented.

@Kristopher38:

So we're making tests behave more like hardware? ;)

Yes indeed! The idea is that this will make the tests more predictable.

Debug prints are essential part of debugging tests - having them saved me countless times. Maybe you could provide "controlled replacement" for these too (...)

Indeed, this can be done. Will add to the todo list.

I disagree. Some of our tests rely on being able to explicitly yield so this requirement seemingly disqualifies the use of your solution in them.

I believe that such cases will (typically?) be expressible using the available synchronization primitives. Look at the code - already did that in retirement testing, wasn't too hard. Basically, sequential behavior can be expressed in a state-machine-like form.
Another possibility which can be implemented to get sequential behaviors is to add a process spawn primitive.

This requires that a process isn't run in a cycle where it can't write to a FIFO - no idea if this can be reasonably implemented.

Yes, it can. If you look at the code, the implementation should allow adding new primitives easily.
@lekcyjna123:

On the other hand there is a lot of boilerplate connected with await's everywhere which worry me.

Could you elaborate? Give an example of what you consider boilerplate.

Reading this code I started to think if we can construct in online way an execution DAG connected with list of sorted nodes, so that to pay the backtracking cost only once. I am sadly not sure if this will be a performance gain, or not, taking into account a number of branch points in tests and slowness of lists in python.

I don't think that's possible in general. First, the dependencies are created dynamically, and they can be different every cycle - so the pesky halting problem gets in the way. Second, part of the dependency graph is hidden in the circuit - it would require analyzing the Amaranth ASTs to discover the dependencies. Still, one could use the information gathered during one cycle to instruct the another, hoping it will execute similarly. I also don't know if this is worth the effort.

On the other hand there is a lot of boilerplate connected with await's everywhere which worry me.

Could you elaborate? Give an example of what you consider boilerplate.

I am not simply a fan of await keywords, but I think that I will have to live with it. What I mean can be represented here:
        def free_reg_process():
            while self.rf_exp_q:
                reg = yield from retc.free_rf_adapter.call()
                self.assertEqual(reg["reg_id"], self.rf_exp_q.popleft())

async def free_reg_process():
  if await self.rf_exp_q.not_empty():
       reg = await Sim.call(retc.free_rf_adapter)
       await WaitSettled()
       self.assertEqual(reg["reg_id"], await self.rf_exp_q.pop())
  else:
      await Exit()

Instead of one yield we get five await, on each fifo use there is needed an await. But on the other hand it is low costs for a predicable and easy to read tests.

I do plan to introduce async/await based testbenches that automatically settle in Amaranth, as an alternative (and, in practical use, largely a replacement) to the current generator based testbenches. I have not solved the concurrency issues that arise from 'autosettling' and at this point I opted to not attempt it as the existing yield based user interface is difficult enough to teach that it should be replaced with anything better before wider adoption.
I'm very interested in the approach taken here and am going to closely inspect this PR to understand the tradeoffs.

The current test system addresses most of the issues this PR was addressing. Closing.


Create an interactive Dice Roller app: Android Basics with Compose

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-compose-build-a-dice-roller-app
In which task and step of the codelab can this issue be found?
All steps
Describe the problem
The word "dice" is incorrectly used as if it is a singular for.  "Dice" is plural.  "Die" is singular.  The codelab only uses one virtual die so there should be no references to "dice".
See the definition of the noun "die" here: https://www.merriam-webster.com/dictionary/die
Steps to reproduce?

Go to...
Click on...
See error...

Versions
Android Studio version:
API version of the emulator:
Additional information
Include screenshots if they would be useful in clarifying the problem.

Hi @David-B-Kelley
Thank you for writing in.
Per Collins dictionary..."In old-fashioned English, dice was used only as a plural form, and the singular was die, but now dice is used as both the singular and the plural form."
Hope you are enjoying the course!
Regards.


Fix wrong sentence about maxNumberOfAttempts

Fixes #76887

@Sti2nd : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ggailey777 Could you review this proposed update to your article and enter #sign-off in a comment if it's approve for merge?
Thanks!

FYI, this change looks right to me, @ggailey777 :)

Thanks @Sti2nd for the fix and @davidmrdavid for the review! #sign-off


[Removal]: Salty Mahogany Salmon

Hotspot Name
Salty Mahogany Salmon
Hotspot b58 Address
11yaZKMEMh9HGmNGYQXyJYBPJMBQH92huyojAGqMjuqqH4QmcNL
Discord Handle
@messses
Hotspot Manufacturer
RAK
Removal Reason
My is in the right Location please remove it.
Modifications
Yes
Extra forwarders
No
Extra antennas
Yes
Additional Information
Hello,
I have given prrof that my Location is real.
This is my Rak Miner with the GPS Location proof.

My Miner Location via Hotspotty.

Street is Hoher Weg.

The Antenna.

Thats the building.

Nearby there is a Gasstation.

I'm open to any questions.
Kind regards.

Where are these abnormally high RSSI and SNR values coming from then?

rx_power
rx_snr
frequency
channel
distance
rx_name
tx_name

-5
7
867.3
1
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-5
7
867.3
1
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-6
8.2
867.9
4
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-6
7.2
867.1
0
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-6
8.2
867.9
4
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-6
8.5
867.9
4
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-6
6.5
867.1
0
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-6
8.2
868.3
6
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-6
7.2
867.7
3
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-7
8
868.1
5
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-7
8
868.1
5
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-7
8
868.1
5
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-7
8
868.1
5
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-10
8
867.7
3
3,303.25
salty-mahogany-salmon
helpful-chartreuse-seahorse

-11
7.5
867.9
4
3,303.25
salty-mahogany-salmon
helpful-chartreuse-seahorse

-11
7.8
867.9
4
3,303.25
salty-mahogany-salmon
helpful-chartreuse-seahorse

-14
7.5
867.7
3
4,185.85
salty-mahogany-salmon
fresh-ruby-boar

-14
8
867.1
0
4,185.85
salty-mahogany-salmon
fresh-ruby-boar

-14
8.5
867.7
3
4,185.85
salty-mahogany-salmon
fresh-ruby-boar

-15
6.8
867.5
2
4,185.85
salty-mahogany-salmon
fresh-ruby-boar

-16
7.5
867.7
3
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-17
6.2
868.5
7
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-17
8
867.3
1
3,303.25
salty-mahogany-salmon
helpful-chartreuse-seahorse

-18
7.2
868.3
6
3,303.25
salty-mahogany-salmon
helpful-chartreuse-seahorse

-18
8
867.3
1
3,303.25
salty-mahogany-salmon
helpful-chartreuse-seahorse

-18
7
868.1
5
3,303.25
salty-mahogany-salmon
helpful-chartreuse-seahorse

-18
7.5
867.1
0
3,303.25
salty-mahogany-salmon
helpful-chartreuse-seahorse

-19
5.5
868.5
7
3,303.25
salty-mahogany-salmon
helpful-chartreuse-seahorse

-24
7.5
867.3
1
4,185.85
salty-mahogany-salmon
fresh-ruby-boar

-25
6.5
867.5
2
4,185.85
salty-mahogany-salmon
fresh-ruby-boar

-26
8.5
867.9
4
4,185.85
salty-mahogany-salmon
fresh-ruby-boar

-26
7
867.9
4
4,185.85
salty-mahogany-salmon
fresh-ruby-boar

-26
7
867.9
4
4,185.85
salty-mahogany-salmon
fresh-ruby-boar

-27
7.8
867.3
1
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-27
7.2
868.3
6
4,185.85
salty-mahogany-salmon
fresh-ruby-boar

-27
7.5
868.5
7
4,185.85
salty-mahogany-salmon
fresh-ruby-boar

-27
7.2
867.3
1
1,760.61
salty-mahogany-salmon
proper-sangria-mandrill

-28
7.5
867.9
4
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-29
8.5
868.1
5
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-29
8
867.9
4
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-29
7.2
868.5
7
1,760.61
salty-mahogany-salmon
proper-sangria-mandrill

-29
7
867.3
1
685.83
salty-mahogany-salmon
helpful-chartreuse-seahorse

-30
7
867.5
2
1,760.61
salty-mahogany-salmon
proper-sangria-mandrill

-31
8.2
867.1
0
1,760.61
salty-mahogany-salmon
proper-sangria-mandrill

-31
8.2
867.3
1
1,760.61
salty-mahogany-salmon
proper-sangria-mandrill

-32
8
867.9
4
1,760.61
salty-mahogany-salmon
proper-sangria-mandrill

-33
7.5
867.1
0
1,760.61
salty-mahogany-salmon
proper-sangria-mandrill

-34
8.2
868.1
5
1,760.61
salty-mahogany-salmon
proper-sangria-mandrill

-39
8.5
868.1
5
1,760.61
salty-mahogany-salmon
proper-sangria-mandrill

-42
5.5
868.5
7
1,760.61
salty-mahogany-salmon
proper-sangria-mandrill

-43
8
867.1
0
3,113.55
salty-mahogany-salmon
trendy-wintergreen-bison

-45
6.8
868.3
6
3,113.55
salty-mahogany-salmon
trendy-wintergreen-bison

-48
6.5
868.5
7
1,276.52
salty-mahogany-salmon
best-velvet-hamster

-55
8.8
867.9
4
3,113.55
salty-mahogany-salmon
trendy-wintergreen-bison

-56
8
868.1
5
3,113.55
salty-mahogany-salmon
trendy-wintergreen-bison

-58
8
868.3
6
3,113.55
salty-mahogany-salmon
trendy-wintergreen-bison

-61
7
868.5
7
3,113.55
salty-mahogany-salmon
trendy-wintergreen-bison

-63
7.2
868.3
6
3,113.55
salty-mahogany-salmon
trendy-wintergreen-bison

-63
7.5
868.3
6
3,113.55
salty-mahogany-salmon
trendy-wintergreen-bison

-63
7.2
867.7
3
1,748.68
salty-mahogany-salmon
dandy-cobalt-rook

-63
7
867.9
4
3,113.55
salty-mahogany-salmon
trendy-wintergreen-bison

-63
7.2
867.1
0
1,748.68
salty-mahogany-salmon
dandy-cobalt-rook


Only install wrapper and run tools from container

Migrated to https://github.com/uniget-org/cli/issues/16


Error 500 on Android Termux

OS/Web Information

Web Browser: Chrome for Android
Local OS: Android 9 Pie
Remote OS: Server? If so, Android 9 Pie on Termux
Remote Architecture: ARM
code-server --version: 3.9.2 109d2ce3247869eaeab67aa7e5423503ec9eb859

Steps to Reproduce

Install code-server as normal with yarn
Start it
Log in to localhost:8080

Expected
VSCode would appear
Actual
500 error is displayed on the screen, alongside with the "go home" button which gives the exact same error
Screenshot
https://user-images.githubusercontent.com/77033690/113613110-18dd9d80-9627-11eb-8ed3-778ab7d682ac.mp4
Notes

This issue can be reproduced in VS Code: No

Wait, wtf? The video didn't upload, lemme try to upload it again

@jsjoeio Sorry for the video delay, I didn't see that it didn't record chrome, then I had to install edge, make a new recording, and also compress it due to GitHub limitations, now it's available

No worries at all! Thanks for opening this up so quickly. I should be able to investigate today.
P.S. the video isn't working on my side. I just see a black screen

No worries at all! Thanks for opening this up so quickly. I should be able to investigate today.
P.S. the video isn't working on my side. I just see a black screen

I'm gonna break somethingLet me try and upload it to YouTube!

https://youtu.be/w2MCCDTNfsU Okay, quality may not be the best because of YouTube, it should be at full res soon

That worked! Hmm...so strange. Okay, let me try to reproduce locally on my Android.

Well, I have good news and bad news.
Good News
I was able to successfully reproduce this on my Pixel 2 in both Chrome and Firefox.
https://user-images.githubusercontent.com/3806031/113616529-115bcb80-960a-11eb-88b8-864f251f520d.mp4
Bad News
Even running with --log debug leads to no hints as to what's wrong.
I'll add this to the next milestone so can investigate further. Thanks for helping us find this.

 Well, in that case, shouldn't a temporal warning be made on the repo telling that 3.9.2 isn't working in these devices?

Yes, good idea! I will pin this issue so people see it and I'll make an announcement in Discussions.

Yes, good idea! I will pin this issue so people see it and I'll make an announcement in Discussions.

Oki, hmu with any updates on the issue

Update:
Starting working on this today. This is terribly difficult to debug. I tried cloning and running code-server on my Android in Termux but couldn't get it working due to issues with native modules needed by vscode. I'll update this thread as I continue to investigate.

@leKamikaze1 can you try upgrading to 3.9.3 and seeing if that fixes it?
I just tried on my Pixel 2 and it's semi-working. The backspace is being funky 🤔
https://user-images.githubusercontent.com/3806031/114103165-79feae80-987d-11eb-81e0-510941d366da.mp4

Sure, wait a sec
PD: About the backspace thing, I noticed the same issue occurred in 3.9.1 in my samsung galaxy tab, it's not something specifically wrong with 3.9.3

About the backspace thing, I noticed the same issue occurred in 3.9.1 in my samsung galaxy tab, it's not something specifically wrong with 3.9.3

Interesting. I wonder if it's something we changed or upstream. I can try to reproduce with Codespaces to check.

The backspace works in Codespaces, but it looks like the cursor jumps one. Probably separate issue.
https://user-images.githubusercontent.com/3806031/114104868-86383b00-9880-11eb-9e3a-9e5115037f6a.mp4

Actually, I found out what it is. It's an upstream issue here:

upstream: Issues with Backspace in Codespaces on Android (Surface Duo)
underlying issue: Support mobile platforms

Alright, so I shouldn't make a new issue? Also, code-server 3.9.3 is building, when its done, ill test if everything works

No, because it's upstream. What we can do is document the issue in the Termux docs though. I'll create a separate issue for that.

Alright, v3.9.3 is working now, and there's something strange with backspace, it sometimes works and sometimes it doesn't, lemme try to record it

Now backspacing when able CRASHES code-server?! https://youtu.be/WOGQubsOjoo

Well, the backspacing thing is now a completely different thing, now code-server is working and the 500 error isn't present anymore. I'm gonna close this and make a different issue regarding the crash. Thanks for the help @jsjoeio !


Boolean aria attribute values are not handled correctly

Describe the bug
Currently, all true boolean attribute values are set to the name of the attribute when true. E.g., a disabled button ends up having the following HTML rendered:
<button disabled="disabled" >
    Do Something
</button>

This behavior comports with the HTML standard for most attributes. However, ARIA attributes with boolean values are special snowflakes in this regard.
Here is a sampling of ARIA attributes that have boolean values:

aria-busy
aria-disabled
aria-hidden
aria-selected
aria-required

Notice that the valid value for true is "true" and not the attribute name. There are more, but I think I've made my point. I've already encountered a situation where this causes issues: using ARIA with TailwindCSS.
Leptos Dependencies
leptos = { version = "0.6" }
leptos_meta = { version = "0.6" }
leptos_router = { version = "0.6" }
leptos_actix = { version = "0.6", optional = true }

To Reproduce
Steps to reproduce the behavior:

Create a simple Leptos UI (perhaps using one of the starter templates)
Put a boolean ARIA attribute, e.g. aria-pressed, on one of the elements and assign it true
Run cargo leptos serve
Open the served page
Open your browser's dev tools
Inspect the element you added the boolean ARIA attribute to

Expected behavior
The attribute has the value "true".
Actual Behavior
The attribute has its own name as a value if true, e.g.

Nice to have
While not causing any problems, it would be nice if non-ARIA boolean attributes only have the attribute present with no value when true, e.g.
<button disabled>
    Do Something
</button>

The amount of generated HTML would be marginally reduced this way, although I doubt it would be enough to make a difference in the vast majority of cases.

I think there's a confusion in terms here. aria-busy="true" is not a boolean attribute; it has a string value, which can either be "true" (the string, not the boolean) or "false" (the string, not the boolean)
HTML containing aria- attributes as boolean attributes is not parsed to these values:
let x = document.createElement("div");
x.innerHTML = "foo";
console.log(x.firstElementChild.ariaHidden);
// logs '', not 'true'

Boolean values on attributes in Leptos mean "include this boolean attribute." From my perspective, the correct behavior here is to pass a string ("true" or "false") or use .to_string() to convert a boolean to a String.

Just an added piece of context — I was double-checking myself on boolean attributes here and in fact the ARIA-style ="false" is specifically invalid for actual boolean attributes. Per MDN on Boolean attributes:

If the attribute is present, it can have one of the following values:

no value at all, e.g. attribute
the empty string, e.g. attribute=""
attribute's name itself, with no leading or trailing whitespace, e.g. attribute="attribute"

Note: The strings "true" and "false" are invalid values. To set the attribute to false, the attribute should not be present in the element tag. Though modern browsers treat any string value as true, you should not rely on that behavior.

So for true boolean attributes, like checked, checked="false" is actually true, although not technically spec compliant. (It certainly isn't false.)
Gotta love the weirdness of the web.

Just an added piece of context — I was double-checking myself on boolean attributes here and in fact the ARIA-style ="false" is specifically invalid for actual boolean attributes. Per MDN on Boolean attributes:

Funnily enough, I linked that same page in my original post.


BUG:units for Uv & U1, convective thermal coefficient for Faiman and PVsyst, m/s should be in denominator

Describe the bug
the units are unclear, m/s should be in the denominator, but looks like numerator
https://github.com/pvlib/pvlib-python/blob/e526b55365ab0f4c473b40b24ae8a82c7e42f892/pvlib/temperature.py#L216
and
https://github.com/pvlib/pvlib-python/blob/e526b55365ab0f4c473b40b24ae8a82c7e42f892/pvlib/temperature.py#L306
Expected behavior
There probably isn't a standard, and we could argue, but IMHO the units should always be as explict as possible. I like the way wikipedia makes them very explicit using parentheses

Screenshots
pvsyst:

Faiman:

Versions:

pvlib.__version__: e526b55365ab0f4c473b40b24ae8a82c7e42f892

Additional context
IMHO these units should uses parentheses like Wikipedia does for clarity:

Uv & U1: [W/(m^2 K)/(m/s)] or [W/m^2/K/(m/s)] or [(W/m^2)/K/(m/s)]
Uc & U0: [W/(m^2 K)] or [W/m^2/K] or [(W/m^2)/K]

also FYI, the HTML code ² makes a superscript 2 similar to 2, there's also ³ too, EG:

W/m^2 = W/m² = W/m2
W/m^3 = W/m³ = W/m3


Added datasets in 5 languages

Hi,
I used googletrans==<IP_ADDRESS> for languages: Russian, Kazakh, Spanish, Italian, French
translated-datasets/databricks-dolly-15k-{language}.jsonl

translation of databricks-dolly-15k.jsonl for language
part of the data (up to 600) was lost during the translation

translated-datasets/databricks-dolly-15k-parallel-corpus-6.csv

includes a uid for which there are translations into several languages
contains the original data set

Oh that's neat. I'm not sure whether the other project folks want this hosted here vs just letting people host their own derived datasets. It's a great point though, you can probably get fairly far in making a model for a different language by machine-translating the fine-tuning dataset. It still doesn't mean the base model's dataset is in that language, and that's where it 'learned' most of the language from. But I'm personally curious how well the results work for these languages!

https://www.kaggle.com/datasets/mygaps/databricks-dolly-15k-parallel-corpus-6
I have published a dataset on kaggle

You can put them on HF too! I'm seeing things like https://huggingface.co/datasets/kunishou/databricks-dolly-15k-ja as well

Rather than check in translations of the dataset into this repo I think it's preferable to upload the translation to Hugging Face.  We can add a not in the README to suggest checking Hugging Face for various translations.


Node server crash when bad torrent request

Hi !
I'm here to report a bug: When doing a bad search, my node server went down.
Here's the log:
undefined:1

assert(): Assertion failed

^
SyntaxError: Unexpected token <
    at Object.parse (native)
    at /var/www/node_modules/t411/index.js:198:21
    at Request.callback (/var/www/node_modules/t411/node_modules/superagent/lib/node/index.js:691:12)
    at Stream.<anonymous> (/var/www/node_modules/t411/node_modules/superagent/lib/node/index.js:922:12)
    at Stream.EventEmitter.emit (events.js:117:20)
    at Unzip.<anonymous> (/var/www/node_modules/t411/node_modules/superagent/lib/node/utils.js:108:12)
    at Unzip.EventEmitter.emit (events.js:117:20)
    at _stream_readable.js:920:16
    at process._tickCallback (node.js:415:13)

Maybe you should add a try, catch at t411/index.js line 198
Did the trick for me:
try {
    var data = JSON.parse(res.text);

    if(data.error) {
      var err = new Error(data.error);
      err.code = data.code;
      return callback(err);
    }

    callback(null, data);
  } catch (e) {
    callback("Error: " + e);
  }

Could you open a PR with your fix using "new Error" as above ?

hello,
there's a pending PR for that https://github.com/thibauts/t411/pull/10
On Fri, May 26, 2017 at 9:49 AM, Thibaut Séguy<EMAIL_ADDRESS>wrote:

Could you open a PR with your fix using "new Error" as above ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/thibauts/t411/issues/13#issuecomment-304216359, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AB13oomv8ZIDhjQ4abdkId-qY8LZAPj0ks5r9oQhgaJpZM4NnRyq
.

Sorry, forget it, the above is not good
On Fri, May 26, 2017 at 11:05 AM, openlemon<EMAIL_ADDRESS>wrote:

hello,
there's a pending PR for that https://github.com/thibauts/t411/pull/10
On Fri, May 26, 2017 at 9:49 AM, Thibaut Séguy<EMAIL_ADDRESS>wrote:

Could you open a PR with your fix using "new Error" as above ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/thibauts/t411/issues/13#issuecomment-304216359, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AB13oomv8ZIDhjQ4abdkId-qY8LZAPj0ks5r9oQhgaJpZM4NnRyq
.