[SPARK-24774][SQL] Avro: Support logical decimal type

What changes were proposed in this pull request?
Support Avro logical date type:
https://avro.apache.org/docs/1.8.2/spec.html#Decimal
How was this patch tested?
Unit test

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/1945/
Test PASSed.

Test build #94427 has started for PR 22037 at commit bbc5434.

Test build #94427 has finished for PR 22037 at commit bbc5434.

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

Merged build finished. Test FAILed.

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

Test build #94428 has finished for PR 22037 at commit e9dc019.

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

Merged build finished. Test PASSed.

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

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2015/
Test PASSed.

Test build #94519 has started for PR 22037 at commit 1c5d228.

Test build #94519 has finished for PR 22037 at commit 1c5d228.

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

Merged build finished. Test FAILed.

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

retest this please

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2025/
Test PASSed.

Merged build finished. Test PASSed.

Test build #94538 has started for PR 22037 at commit 1c5d228.

Test build #94538 has finished for PR 22037 at commit 1c5d228.

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

Merged build finished. Test FAILed.

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

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2033/
Test PASSed.

Test build #94546 has started for PR 22037 at commit 9eefbe5.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2038/
Test PASSed.

Test build #94552 has started for PR 22037 at commit 24dbada.

Test build #94546 has finished for PR 22037 at commit 9eefbe5.

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

Merged build finished. Test FAILed.

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

Test build #94552 has finished for PR 22037 at commit 24dbada.

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

Merged build finished. Test FAILed.

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

retest this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2040/
Test PASSed.

Test build #94558 has started for PR 22037 at commit 24dbada.

Test build #94558 has finished for PR 22037 at commit 24dbada.

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

Merged build finished. Test FAILed.

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

Test build #94579 has started for PR 22037 at commit 0384a1a.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2056/
Test PASSed.

Test build #94579 has finished for PR 22037 at commit 0384a1a.

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

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

retest this please.

Test build #94616 has started for PR 22037 at commit 0384a1a.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2081/
Test PASSed.

Test build #94623 has started for PR 22037 at commit 6b11292.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2084/
Test PASSed.

Test build #94616 has finished for PR 22037 at commit 0384a1a.

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

Merged build finished. Test PASSed.

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

Test build #94628 has started for PR 22037 at commit 508a340.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2088/
Test PASSed.

Test build #94623 has finished for PR 22037 at commit 6b11292.

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

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

Merged build finished. Test PASSed.

Test build #94628 has finished for PR 22037 at commit 508a340.

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

Merged build finished. Test PASSed.

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

thanks, merging to master!


Improve management of outbound connections from one secondary to others

Describe the bug

Outbound clients are currently created in two places:

OutboundClientManager (in at_secondary_server/lib/src/connection/outbound
NotifyConnectionsPool (at_secondary_server/lib/src/notification)

Both create their own independent OutboundClientPools, and each of those pools is initialized with a 'size' which is configured by at_secondary_config with a default value of 10. (Overridable by env and yaml). So given we have two pools, the actual number of OutboundClients allowed would be 20 across both pools.

Is this the intended behaviour, or should the limit be 10 across both pools?
And why do we need two independent pools?
If we need two independent pools for $reasons then we should have two config settings

Pool management

The pools contain OutboundClients for each pair of (1) target atSign and (2) inbound connection
OutboundClients are removed from the pool by OutboundClientManager and NotifyConnectionsPool when they need to create a new OutboundClient (i.e. none currently exists in the pool) if, and only if, the inbound connection is no longer valid. (See clearInvalidClients() in outbound_client_pool.dart)
Given the above then if a secondary, for some given client connection, needs to create more outbound clients than the limit of outbound connections (current default 10), then it will fail to do so.

Thinking about the other side of the connection:

Each outbound connection from one server is an inbound on another
We will have 'super-connected' secondaries which handle colossal numbers of inbound connections from other secondaries
OutboundClientPool does not currently have regular (scheduled) reaping of outbound connections, so outbound connections may continue to hang around long after they are required and we are therefore dependent on the other side reaping its idle inbound connections to protect itself from inbound connection overload. (We also don't have this, and we will need it in order to defend against DoS attacks whether deliberate or as an inadvertent result of badly-written clients; have raised another issue for this, #503)

Expected behavior
This needs further analysis, but

We should strive to keep the number of outbound clients to a minimum, but a simple hard-limit pool will not work. We could consider

reaping outbound clients from the pool on a LRU basis once a low-water-mark limit has been reached
while also allowing the pool size to continue to grow up to a high-water-mark if all outbound clients in the pool are currently in use and can't be reaped
and logging WARNING and SEVERE log messages as we approach the high-water-mark, so that some appropriate action can be taken whether by human or automation (e.g. increase the limits for this secondary)

We should consider adding scheduled reaping of outbound clients. The decision as to what idle time which makes an outbound client eligible for reaping should be made together with the decision for, on the other end, what the idle time should be for inbound connections that renders them eligible for reaping.
We need to harden the OutboundClients so that if they happen to be reused from the pool but the receiving end has reaped the inbound connection for some reason, then we don't just throw a hard exception but we gracefully attempt a retry
at_lookup.AtLookupImpl.findSecondary currently does a lookup to the root server every time it is called. We can easily cache this, with cache invalidation done by clients (client-side or server-side) which are failing to connect to a cached secondary address

Additional context
As the network of connections between atSigns grows, we need to have policies which will optimise for the "normal" number of inter-server connections but will gracefully handle much larger numbers

@cconstab @cpswan @VJag @murali-shris @kalluriramkumar @nickelskevin Interested in any initial comments or thoughts you have on this

@gkc will move to the arch discussion log for the team to talk through.


Question about the prompt format for CodeRankLLM

Hello authors, thank you for your great work.
My question is about how to prompt CodeRankLLM. Maybe I'm missing something, but it doesn't seem like there are any examples of how to actually use it (either in the HF repo or here in GH). Let me know if I'm missing something, or if I'm not, a very short example would be helpful!
Thank you!

Thanks for the interest! We are working on the release and will include examples and documentation soon.


Improve Self Hosted ExceptionLess Experience

Hi,
I have installated Redis & MongoDb via Chocolatey (as service) on my Windows 2012 Server.
=> Redis & Mongo Db as running.
On this same server, i am trying to install Exceptionless.Api.IIS in IIS. But's it's not working.... no log, nothing. I haven't login screen.
The website is :
on dedicaced pool, on .Net 4.0.
Binded to xxx.domain.ltd on port 80.
web.config :
BaseURL : => url binded to website in IIS
WebsiteMode : Production
Could you help me ?
How can i activate log ?
Thansk by advance.

@Nonobis we added an account creating setting in 2.0 (EnableAccountCreation). I'm going to close this issue with specifics on how we intend to improve the self hosted experience. I also reated an issue to look into the websockets issue.


Add CI and Deploy Snapshots workflows for Github Actions

Fixes #105, fixes #144

Hmm, sometimes Github Actions picks these pull requests up right away, and sometimes not.  I'm not sure what I'm missing, perhaps in this case it is the Travis hook?

Based on this process in another repo, it appears this pull request needs to be merged before GA will pick up

Another option would be to change it to run off of a non master branch and develop it there until it's ready (assuming that would work to get it running)

Thanks, @lbergelson!  I'll merge to get CI started and then will port the end-to-end tests over later.

Opened issue https://github.com/disq-bio/disq/issues/160 to track


Issue with stringified pdb file

Hi @samirelanduk ,
thanks for the great utility :) I am trying to debug what's going wrong, but I can't seem to get to the bottom of it... I receive a PDB file from a server in string format, which I then convert to Blob and serve to the component. My react class looks like this:
import React from "react";
import Molstar from "molstar-react";

class StructurePrediction extends React.Component {

  constructor(props) {
    super(props);

    this.state = {
      url: null,
      pdbBlob: null,
      string: null
    };
  }

  componentWillReceiveProps(newProps) {
    let data = newProps.data;

    let pdbBlob = new Blob([data], {
      type: "pdb",
    });

    this.setState({
      url: URL.createObjectURL(pdbBlob),
      pdbBlob: pdbBlob,
      string: data
    });
  }

  render() {
    return (
        <div id="structureViewer" style={{float: 'inherit',  width: 'inherit', height: '700px', position: 'relative'}}>
          {this.state.pdbBlob && <Molstar file={this.state.pdbBlob} useInterface={true} />}
        </div>

    );
  }
}

export default StructurePrediction;

While the data attribute passed to newProps looks something like this:
data.txt (sorry, had to put in a TXT file; was too large to post in an issue)
My console output is:
TypeError: Cannot read properties of undefined (reading 'entry')
    at trajectoryProps (index.js:67802:1)
    at Object.<anonymous> (index.js:67874:1)
    at step (index.js:1209:1)
    at Object.next (index.js:1189:1)
    at fulfilled (index.js:1175:1)

This seems to refer to the mol* base code?

Would really appreachiate the help :) Note that the reason why I wrapp the call into a componentWillReceiveProps is that the same instance will display multiple structures from different strings based on user input.

The file object passed to the component is supposed to be an object with a key property and a filestring property. So something like {key: "pdb", filestring: "PDB-filestring-here"}. No conversion to blob is required.

Awesome! Thanks :)


Support of older Yeelock devices

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
Hey there,
I'm not entirely sure if those old locks are just unsupported, or my Bluetooth setup in HA is just not working.
These are locks I'm trying to set up, but they're not discovered in HA:

I never had Bluetooth set-up in HA, so it can absolutely be my setup; apologies if it is :(
Here's what I did:

Enabled a Shelly 2PM to be a BT Proxy, basically by ticking this:

After that, installed your integration via HACS, rebooted HA
After reboot, the lock doesn't show up. I also tried adding manually but also says "No devices found on the network". The Shelly is in the wall just across the room, probably 4m away, so can't really be a range issue, I think...
I tried locking and unlocking it via the app, but still doesn't show up.
I tried adding this block to my HA config, rebooted but still nothing:

bluetooth:

device_tracker:
  - platform: bluetooth_le_tracker
    track_new_devices: true
    track_battery: true
    track_battery_interval: 3600

I do see a few devices popping up in known_devices.yaml, but no idea if one of them is the lock :/
Maybe u already know if those locks are supported, or not.
Thanks already for the help ans greetings,
Andy!
Describe the solution you'd like
x
Describe alternatives you've considered
x
Additional context
x

OK, new findings:
To eliminate if it's the Shelly or the Yeelock, I've set up a simple ESP32 with ESPHome as BT Proxy... aaaaaand: it works :) It instantly discovered all three locks. So I can confirm that those locks work with your integration, maybe want to list them under "Compatible devices" here: https://github.com/codyc1515/ha-yeelock?tab=readme-ov-file#compatible-devices
Greetings and thanks for this, this is awesome and a long term painpoint in my home to not have those in HA! Well done!!


Add multiple response for festival intents

I update the chat module and the data JSON schema to support multiple response that corresponding to the date condition
as shown:
One-day example
"new_year_en": {
    "response": {
        "fes": [
            "Happy new year! I hope next year would be a great year!"
        ],
        "nonfes": [
            "It's not new year yet."
        ]
    },
    "list_of_words": ["happy", "new", "year"],
    "is_single_response": false,
    "required_word": ["new", "year"],
    "date": 31,
    "month": 12
}

A response object with two keys, fes and nonfes, each corresponding to a list of messages. If the current date is the same as the festival date, the bot will respond with a message from the fes list. If not, it will reply with a message from the nonfes list.
Variable-length example
"new_year2_en": {
    "response": {
        "fes": [
            "Happy new year! I hope next year would be a great year!"
        ],
        "nonfes": [
            "It's not new year yet."
        ]
    },
    "list_of_words": ["happy", "new", "year"],
    "is_single_response": false,
    "required_word": ["new", "year"],
    "date": [1, 2],
    "month": 1
}

If the current date is in festival date range, the bot will respond with a message from the fes list. If not, it will reply with a message from the nonfes list.

It's very nice.


Update documentation for node.js backend

The documentation for the pylot.codes backend is not up to date with the server.js application in the backend/src folder.
Update the documentation to match the server.js file.

Documentation can be found in the gh-pages branch of the repository and involves updating the included markdown files, Jenkins handles the rest.

@ryzbaka ,can I work on this issue?

Sure thing @nk183 , just create a pull request with the changes.

@ryzbaka ,where can I edit Documentation
I am not able edit in  Documentation ([https://ryzbaka.github.io/PyLot/]) directly

d

@ryzbaka  please guide where I can edit Documentation

@nk183 if you clone the repo and move to the gh-pages repo, you'll find an index.md file which can be edited.

Hi @ryzbaka  have made a pull request please check - #13


Database rebuilding breaks with multiple persistence providers

Follow up issue: https://github.com/DescartesResearch/Pet-Supply-Store/issues/50


Update Sequence to use List CRDT

Based on the work in https://github.com/rust-crdt/rust-crdt/pull/104
@iancoleman You may want to take a look at this, it replaces the internal identifier representation in LSeq with an arbitrary precision rational number. The code no longer panics after too many inserts.

The code no longer panics after too many inserts.

Nice. The List code looks very tidy and much simplified over LSeq. But as for the details, my knowledge is not deep enough there and the previous comments are more useful than anything I'd add.
I ran a test including serialization which closely simulates a client/node interaction, and it passes no worries.
#[test]
fn test_append_many() {
    let mut client = List::new();

    // client serializes the list for storage on the node
    let client_serialized = rmp_serde::to_vec(&client).unwrap();

    // node receives the serialized list from the client
    let mut node_serialized = client_serialized.clone();

    // client uploads the list to the node
    let mut node: List<String, SiteId> = rmp_serde::from_read_ref(&node_serialized).unwrap();

    // node serializes for storage
    node_serialized = rmp_serde::to_vec(&node).unwrap();

    let appends = 10000;
    for i in 0..appends {
        // client gets the list over the wire from serialized node storage
        client = rmp_serde::from_read_ref(&node_serialized).unwrap();
        // client appends a new value
        let val = format!("value {}", i);
        let op = client.append(val, 0);
        client.apply(op.clone()); // optional?
        // serialize op to send to node
        let op_serialized = rmp_serde::to_vec(&op).unwrap();
        // node deserializies op
        let op_deserialized: Op<String, SiteId> = rmp_serde::from_read_ref(&op_serialized).unwrap();
        // node applies op to the node list
        node.apply(op_deserialized);
        // node serializes their new list for storage
        node_serialized = rmp_serde::to_vec(&node).unwrap();
    }

    assert_eq!(client.len(), appends);
    assert_eq!(node.len(), appends);
}

Excellent @iancoleman
@davidrusu
In terms of Delete requiring order, I agree, but for this reason and to ensure we remain a semi-lattice CRDT type I would not allow deletes.
I really think we need to consider data types as CRDT (semi-lattice) or not.
However even CRDT types were we deterministically resolve forks, then we need to be certain forks are not harmful (i.e. doublespend). Forks created by mistake or malice for CRDT is no worry, as long as the fork has no side effects. CRDT is OK there.
Where we cannot allow forks (i.e. crypto currency) then we must enforce an order co-ordinated order to prevent the creation of a fork. So we need a clear ruleset here of data and the capabilities (or not) of such data.


CLA Assistant Unlinked -- All Data Missing

URL to the linked Repository or Organization
https://github.com/prysmaticlabs/prysm
Steps to reproduce the problem

Wake up one day (I'm not sure when this started)
Hear reports that CLA Assistant is no longer linked with the Prysm project
Log into cla-assistant.io, no data is present. The branch protection checks for CLA assistant are gone in Github.

What is the expected result?
CLA assistant is linked to the prysm project with hundreds of contributors previously signed.
What happens instead?
Nothing is there :(
Any other information? (attach screenshot if possible)

Used browser and browser version?
Chrome
Any other tested browsers/devices(OK/FAIL):

Here's a link to a CLA assistant comment from a PR: https://github.com/prysmaticlabs/prysm/pull/11698#issuecomment-1329253188
Clicking the CLA button shows an error of "Bad credentials"

@Shegox Thank you!!! That resolved my problem. Is there anything we could do to prevent this from happening again or receive notification that it has become unlinked? We just happened to notice that it wasn't a requirement one day, but not sure how long it has been broken.

At the moment not really, however a colleague is currently working on adding better support for GitHub App based authentification, which will make the authentification independent of an user account/permissions.
In addition to more quickly notice this, would be making the CLA-check a "required status checks". This way you would see directly when it fails and ensures that you can't merge a PR without a CLA-check.


Aggregating Test Failures

Contact Details
<EMAIL_ADDRESS>I have read the dbt Developer Blog contribution guidelines.

[X] I have read the dbt Developer Blog contribution guidelines.

Which of these best describes you?

[X] I am a dbt Community member or partner contributing to the Developer Blog
[ ] I work for dbt Labs and am creating this issue for a community or marketing approved piece.

What is the topic of your post?
I work at Tempus Labs, an oncology research company that centers itself around clinical data. We're currently doing a massive push to fix data quality issues in our dbt-based data warehouse.  I see a few different directions for this post, since we've done quite a lot.
The first direction I could take is outlining the Data Quality Aggregation component of our framework. We've essentially built an aggregation method on our data quality tests, to better visualize and act on them. We did this by storing test failures and then using GCP's wildcard syntax to pull from all similarly named tests, joining this on a seed table with test metadata.
The second direction I could take is outlining our entire data quality framework, which comprises of three separate components. I outlined all three of these in the outline linked below. I'm open to just writing about one of these frameworks, or doing all three, but if all three I would say a three part blog post may be the most easily digestible.
Link to an initial outline.
https://docs.google.com/document/d/1oi99CxXK8CN0aUV-1QW11vwDpHceBoX5-KoReB6Cq7g/edit?usp=sharing

Hi @noahfkennedy - this is a really awesome topic I can't wait to read.
Generally for posts like these we prefer to keep things nice and modular and be very ok doing multi-part series.
How would you feel about starting with the Data Quality Aggregation component with the understanding that we might want to turn this into a three parter in the future? If that sounds good let's move to drafting phase. Next steps would be for you to let us know when you would anticipate having a draft going as well as scheduling some time to chat through this with me if you're interested.

Hey @jasnonaz , sorry for being late here, I forgot to reply.
That sounds like a great approach. I can start working on drafting this now. I anticipate being able to start the draft later today / tomorrow, and can shoot for getting a final draft over to you around September 9th if that sounds good? I would be able to do earlier but I'm traveling quite a bit through the end of August.
I already have quite a bit written up so it shouldn't be a huge lift. Let me know how that sounds.

That sounds wonderful - thank you Noah looking forward to reading.

Hey @jasnonaz  - still working on this, anticipating to wrap up the draft over the weekend! I'll send it to you on Monday.

Hey Jason,
Sorry to do this, but would it be alright with you to bump this back 4
weeks?
Timing is pretty bad. I have a super week with 5 interviews
Wednesday/Thursday and I'm leaving for Europe on Thursday - I ended up
studying all weekend instead of writing. I wasn't expecting having all
these interviews. I'll be in Europe until the end of September, and if all
goes as planned I'll get some of the technical writing done then but don't
want to hard commit to it, since I'll be on vacation.
Could potentially still get you a draft but I figured this would be better
than me sacrificing sleep/studying time and stressing myself out.
Best,
Noah
On Mon, Sep 12, 2022 at 11:29 AM Jason Ganz @.***>
wrote:

Awesome thanks for the update Noah - looking forward to checking this out!
—
Reply to this email directly, view it on GitHub
https://github.com/dbt-labs/docs.getdbt.com/issues/1853#issuecomment-1243912145,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEOIFDZPDVQCJG2CMZZFA4LV55D3ZANCNFSM56E6M43A
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
*University of Delaware Alumni *
Chemical Engineering | Computer Science | Triathlon

Please do not stress / sacrifice sleep / any of the above. There is no time pressure on this - focus on the things you need to do and we can reconnect in a month!

Appreciate it Jason! Very excited to wrap up the draft and thank you for
the flexibility.
Noah
On Mon, Sep 12, 2022 at 4:29 PM Jason Ganz @.***> wrote:

Please do not stress / sacrifice sleep / any of the above. There is no
time pressure on this - focus on the things you need to do and we can
reconnect in a month!
—
Reply to this email directly, view it on GitHub
https://github.com/dbt-labs/docs.getdbt.com/issues/1853#issuecomment-1244394033,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEOIFD6WUU7GUXFKDKZUNODV56HCNANCNFSM56E6M43A
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
*University of Delaware Alumni *
Chemical Engineering | Computer Science | Triathlon

Hey Jason,
Thanks so much for your patience. Here is a link to the rough draft -
https://docs.google.com/document/d/1VgxrY_KZAH-2Tu0MURyYYlsdwyE7RK0PBWDOgMqxo4o/edit?usp=sharing
Let me know if you have any trouble accessing it, or if you have any
questions. It's still in the rough stages and I definitely need to clean
things up and shorten it, but I would love some perspective on what parts
of it are unnecessary and I should delete, and what parts I should
elaborate on (e.g. I talk specifically about my company and provide code
blocks, but maybe I should do less of that and more of something else).
Looking forward to hearing from you!
Best,
Noah
On Mon, Sep 12, 2022 at 4:57 PM Noah @.***> wrote:

Appreciate it Jason! Very excited to wrap up the draft and thank you for
the flexibility.
Noah
On Mon, Sep 12, 2022 at 4:29 PM Jason Ganz @.***>
wrote:

Please do not stress / sacrifice sleep / any of the above. There is no
time pressure on this - focus on the things you need to do and we can
reconnect in a month!
—
Reply to this email directly, view it on GitHub
https://github.com/dbt-labs/docs.getdbt.com/issues/1853#issuecomment-1244394033,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEOIFD6WUU7GUXFKDKZUNODV56HCNANCNFSM56E6M43A
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
*University of Delaware Alumni *
Chemical Engineering | Computer Science | Triathlon

--
*University of Delaware Alumni *
Chemical Engineering | Computer Science | Triathlon

Hi @noahfkennedy! Apologies on the delay getting back to you - missed this in the runup to Coalesce.
This is really strong!! I'll provide some feedback and edits this week and then we can do a round of revisions and plan to publish in early January.

Great! I'm taking a look now and I'll see how I can use that to create a
better hook in the introduction. Also super excited to get this out!
Best,
Noah
On Thu, Dec 15, 2022 at 10:27 AM Jason Ganz @.***>
wrote:

Hi @noahfkennedy https://github.com/noahfkennedy ! Left some comments
in the sheet. This shaping up to be a really incredible post. My main
suggestion is around framing - you mention a really great framing
device in the conclusion about how you dropped from 800 to 25 tests and
increased your actionability within them. This is SO cool and really makes
a great hook for the article. I'd love to bring that up to the introduction
and use that to guide the story that we're walking through during the post.
Other than that I had some relatively minor wording / formatting thoughts
but overall this is excellent - really excited to get it into the world.
—
Reply to this email directly, view it on GitHub
https://github.com/dbt-labs/docs.getdbt.com/issues/1853#issuecomment-1353266706,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEOIFDYUB2OP2RRROWC5IDLWNM2GLANCNFSM56E6M43A
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
*University of Delaware Alumni *
Chemical Engineering | Computer Science | Triathlon

Hey Kira,
I definitely lost track of this over the holidays! Thank you for bumping
it.
I'm putting on the finishing touches + doing some peer review with a
colleague. Should be ready to be published tomorrow, so if you want to
start kicking off that process that would be great!
Noah
On Thu, Jan 19, 2023 at 11:46 AM Kira Furuichi @.***>
wrote:

Hey @noahfkennedy https://github.com/noahfkennedy! I'm Kira, a
technical writer at dbt Labs and one of the folks who works with Jason on
editing and publishing posts on the Developer Blog. Jason has told me your
post is near the finish line, and I wanted to check-in to see if you're
ready for us to open up a PR for it and get it published? Please let me
know if you are, so I can start getting your content live and promoted :)
—
Reply to this email directly, view it on GitHub
https://github.com/dbt-labs/docs.getdbt.com/issues/1853#issuecomment-1397287655,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEOIFD7UX3YJZXMTWGUITZDWTFVXTANCNFSM56E6M43A
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
*University of Delaware Alumni *
Chemical Engineering | Computer Science | Triathlon

Hey @noahfkennedy thanks for the update! It's pretty quick + easy for me to upload once you're done, so just ping me here once you're finished and I'll focus on getting it live :)

Kira,
Just put on the finishing touches! I think the only other thing is ensuring
code blocks are properly formatted within the document - right now it's
just raw text.
Here's a link!
https://docs.google.com/document/d/1VgxrY_KZAH-2Tu0MURyYYlsdwyE7RK0PBWDOgMqxo4o/edit?usp=sharing
Best,
Noah
On Thu, Jan 19, 2023 at 5:36 PM Kira Furuichi @.***>
wrote:

Hey @noahfkennedy https://github.com/noahfkennedy thanks for the
update! It's pretty quick + easy for me to upload once you're done, so just
ping me here once you're finished and I'll focus on getting it live :)
—
Reply to this email directly, view it on GitHub
https://github.com/dbt-labs/docs.getdbt.com/issues/1853#issuecomment-1397702104,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEOIFD6SCIJQWQ3PBYKSMWTWTG6VRANCNFSM56E6M43A
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
*University of Delaware Alumni *
Chemical Engineering | Computer Science | Triathlon

no worries about the code formatting, @noahfkennedy ! I'll handle that in the PR and request your review, so you can confirm it aligns with your expectations. Can you send me a brief description you want to use for your author profile? Example author bio here

Yep!
Noah Kennedy is a Senior Software Developer at Tempus Labs, helping manage

the worlds largest repository of clinical and molecular patient data. Noah
picked up dbt at Tempus 2 years ago, and has worked extensively on internal
dbt development for Tempus - creating macros, custom materializations, and
testing frameworks that allow scientists to experiment more and data
engineer less. Outside of Tempus, Noah spends his time running, biking,
playing music, and exploring coffee shops. You can find more of his writing
at noahkennedy.co https://noahkennedy.co/about/.

On Fri, Jan 20, 2023 at 11:08 AM Kira Furuichi @.***>
wrote:

no worries about the code formatting, @noahfkennedy
https://github.com/noahfkennedy ! I'll handle that in the PR and
request your review, so you can confirm it aligns with your expectations.
Can you send me a brief description you want to use for your author
profile? Example author bio here
https://docs.getdbt.com/author/emily_riederer
—
Reply to this email directly, view it on GitHub
https://github.com/dbt-labs/docs.getdbt.com/issues/1853#issuecomment-1398607559,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEOIFDY6HFUI4UJNCDDBXGTWTKZ7TANCNFSM56E6M43A
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
*University of Delaware Alumni *
Chemical Engineering | Computer Science | Triathlon

Hey @noahfkennedy and @jasnonaz, PR here and deployment preview here!

Hey @noahfkennedy, happy to share that your blog post is live!! We have plans to share your post on the dbt Labs LinkedIn and dbt Twitter accounts next week, so I'll ping you in the Community Slack when that happens. In the meantime, please feel free to share with your network and in the #i-made-this channel in the Community Slack if you feel comfortable doing so :)
Thanks again on all your great work here--the team is looking forward to collaborating on more of these with you in the future!

Wooo! Thank you so so much! Really appreciate all your help making it
happen. Just shared it with my network.
Would love to work more with you two in the future, it was a pleasure. I
have some other ideas for articles, going to take a break and set a
reminder to touch base in the next few weeks. Please let me know if there
are other ways I can contribute and stay involved with the dbt community in
a more formal capacity!!
Best,
Noah
On Mon, Jan 23, 2023 at 4:50 PM Kira Furuichi @.***>
wrote:

Hey @noahfkennedy https://github.com/noahfkennedy, happy to share that
your blog post is live
https://docs.getdbt.com/blog/aggregating-test-failures-with-dbt!! We
have plans to share your post on the dbt Labs LinkedIn and dbt Twitter
accounts next week, so I'll ping you in the Community Slack when that
happens. In the meantime, please feel free to share with your network and
in the #i-made-this channel in the Community Slack if you feel comfortable
doing so :)
Thanks again on all your great work here--the team is looking forward to
collaborating on more of these with you in the future!
—
Reply to this email directly, view it on GitHub
https://github.com/dbt-labs/docs.getdbt.com/issues/1853#issuecomment-1401041943,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEOIFD3ADNDQWRGGWCEHB53WT34LVANCNFSM56E6M43A
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
*University of Delaware Alumni *
Chemical Engineering | Computer Science | Triathlon


[Bug] [dolphinscheduler-api] Data Analysis Service API responds with jackson deserialization exception

fix #11854

@SbloodyS @caishunfeng pls review, tks!

Codecov Report

Merging #11858 (a6b68f1) into dev (e101a5c) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev   #11858      +/-   ##
============================================
- Coverage     38.53%   38.52%   -0.02%
+ Complexity     4038     4035       -3
============================================
  Files           993      993
  Lines         36716    36687      -29
  Branches       4273     4266       -7
============================================
- Hits          14150    14133      -17
+ Misses        20940    20929      -11
+ Partials       1626     1625       -1

Impacted Files
Coverage Δ

.../apache/dolphinscheduler/api/dto/TaskCountDto.java
94.44% <ø> (ø)

...erver/master/processor/queue/TaskEventService.java
75.00% <0.00%> (-5.36%)
:arrow_down:

...r/plugin/task/sqoop/parameter/SqoopParameters.java
55.12% <0.00%> (-1.29%)
:arrow_down:

...rver/master/runner/task/BlockingTaskProcessor.java
75.86% <0.00%> (-0.55%)
:arrow_down:

...heduler/api/service/impl/ResourcesServiceImpl.java
51.99% <0.00%> (-0.49%)
:arrow_down:

...eduler/api/service/impl/DataSourceServiceImpl.java
27.90% <0.00%> (ø)

...cheduler/server/master/utils/DependentExecute.java
0.00% <0.00%> (ø)

.../dolphinscheduler/plugin/task/datax/DataxTask.java
0.00% <0.00%> (ø)

...phinscheduler/plugin/task/chunjun/ChunJunTask.java
0.00% <0.00%> (ø)

...cheduler/plugin/task/api/ShellCommandExecutor.java
0.00% <0.00%> (ø)

... and 7 more

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

I had rerun the fail CI.

@caishunfeng @SbloodyS changes has been approved, could you merge into dev ?


Update live with current master

Publish new landing page
Remove old installation guides
Small typo fixes

Docs Build status updates of commit 5c4232f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

articles/TOC.yml
:white_check_mark:Succeeded
View (qsharp-preview)

articles/docfx.json
:white_check_mark:Succeeded

articles/index.yml
:white_check_mark:Succeeded
View (qsharp-preview)

articles/install-guide/command-line.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/install-guide/csharp.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/install-guide/jupyter.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/install-guide/python.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/install-guide/update.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/install-guide/vs-2017.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/install-guide/vs-code.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/language/statements.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/relnotes/index.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/techniques/working-with-qubits.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/welcome.md
:white_check_mark:Succeeded
View (qsharp-preview)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Users database schema

Create a schema for users collection in the database, there's going to be a future update to implement relations among the other collections once created.

users collection is finished and integrated with users controller. The 'restore' route will be removed because there's no support for this operation using Mongoose.


is there a need to match diagram name against a hardcoded list, rather than forwarding the argument to the kroki server?

what it says on the tin.
If checking the value against a hardcoded list wasn't required, then new diagram types would not need to be manually added (and no issues with absent maintainers either...)
The 'checking' mechanism could still be used for known aliases, but fall back to a direct pass through

I am also looking in to this.
I tired to look if kroki has a api for it but I can't find any.
I posted the question up to kroki https://kroki.zulipchat.com/#narrow/stream/232085-users/topic/Api.20endpoint.20to.20list.20supported.20diagrams.3F

i'm referring to these lines - https://github.com/sphinx-contrib/kroki/blob/2665ddf784498abc14917ac7a1ab391b1a2e9bc0/sphinxcontrib/kroki/kroki.py#L19-L64
seems to me the types dict is redundant, and forces you to create a new PR to support every new diagram supported upstream. When you could instead have something like-
ALIASES = {
    "bob": "svgbob",
    "c4": "c4plantuml",
    "c4puml": "c4plantuml",
    "dot": "graphviz",
    "dsl": "structurizr",
    "er": "erd",
    "gv": "graphviz",
    "iuml": "plantuml",
    "pu": "plantuml",
    "puml": "plantuml",
    "uxf": "umlet",
    "vg": "vega",
    "vgl": "vegalite",
    "vl": "vegalite",
    "wsd": "plantuml",
}

def diagram_name(name: str) -> str:
    return ALIASES.get(name, name)

Yea I agree. I got back från kroki that we can use https://kroki.io/health to get a list of available diagrams. I will see if I can get a PR together


Is this legal?

I have a question... Will this get taken down? I promise, I won't report this.

Maybe.

Piracy of course isn't legal... @Igglybuff

but links are not piracy, right?

Right :)

Promoting piracy websites is illegal afaik

SCOTUS:

We hold that one who distributes a device with the object of promoting its use to infringe copyright, as shown by clear expression or other affirmative steps taken to foster infringement, is liable for the resulting acts of infringement by third parties.

“Clear expression” and “affirmative steps” are a high bar, but the name, history, and content in this repo make it a slam dunk. I think you should delete it

"Distribute a device" is very vague. I would assume that would refer to streaming boxes, not links to websites. If linking to websites were illegal, Wikipedia would be in trouble, since the wiki page of thepiratebay has the link to the site.

It certainly depends. I have copied the repo down to my PC, so if it gets taken down, i can send over the files to Igglybuff in case he dosen't have them. Furthermore, the list is also available on pastebin.
Github shouldn't have a problem with the list. I've found really destructive stuff on Github.

What piracy? Aren't these all Linux ISOs mirrors?


Removed links to the mobile apps (iPhone/Android).

Just to remove some dead links.

I close this PR since there is an app for iOS. It is an "official" app?
We can see later for Android. My personal instance of Trovebox is already running without theses links (on a dedicated branch).

@jmathai and @cedricbonhomme for the Android app we could upload the APK to Google Play. I just need to check if the binaries are ok. Also, I would like to remove the old login we have it. Added to my todo list


Rename master branch to main

Many communities, both on GitHub and in the wider Git community, are considering renaming the default branch name of their repository from master.

Thx done. This is the problem with using old IDEs, they still use master as default 😅


fix: Fix package.json url

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Allow for commands to be executed on rebuild

Hi, and first of all thanks for this wonderful tool :)
It would be nice to be able to specify a command that is run every time the code is rebuilt (ideally before the live-reload)
This would allow people to use tools like elm-css with the dev server, running the elm-css command every time the code changes.

Hey, great idea! I’ve been thinking about this myself 🙂
It’s very likely I’ll be setting up another project with elm-live soon – if that’s the case, I’ll surely extend elm-live to cover this.
Until then, I’m afraid I can’t do much to make this happen myself – a PR would be much appreciated though 😀

I'm looking into writing a PR, and I've got a few questions :)

Is it okay to put the code into the build() function? Seems to be the place to put it from my perspective
cross-spawn doesn't seem to implement an exec-function (point being to supply a full command with the --on-build option. Are there any objections to adding child_process? Alternative would be to manually extract the executable name and arguments)

Hey Gabriel, thanks a lot for your help and enthusiasm! As for your questions,

Is it okay to put the code into the build() function? Seems to be the place to put it from my perspective

Yep, seems like the right place to put it. I’ve been doing my best to make any error messages as helpful and beautiful as possible (in line with the compiler). Please look around and try to match the output in tone and style.

cross-spawn doesn't seem to implement an exec-function (point being to supply a full command with the --on-build option. Are there any objections to adding child_process? Alternative would be to manually extract the executable name and arguments)

cross-spawn came there as we introduced Windows support. I can’t remember what the reason was that child_process (which I had used previously) didn’t bite it. @bdukes may have more context than I do. If you need an answer now, your best bet would be to look at related PRs and issues.

Of course, if you have any more question, I’ll be more than happy to help 🙂

@peacememories, the main thing that we're getting from cross-spawn is escaping arguments and using default extensions (e.g. finding elm-make.cmd when I ask to run elm-make).  If you're passing in a command line yourself, I'd be okay with that going through child_process.exec, since individual users can control how they're passing that argument (e.g. adding .cmd manually).
Hope it helps!

@bdukes thanks for the answer :) Then I'll implement it using child_process for the time being I think.

I think I'll move discussion on how to implement this into a WIP pull request if that's okay with you.

👍 Thanks for your help so far!


Application error: a client-side exception has occurred

when selecting MNTL to WBTC pool on Osmosis Frontier, the application crash.
see console log attached.
frontier.osmosis.zone-1680986361129.log
Way to reproduce:

go to swap
select from MNTL
selct to WBTC
=> crash

Currently looking into this

Exception no longer makes it to window


feat/825-setup-bug-ssh-naming

Codecov Report

Merging #206 (98ed916) into main (b6d4ce9) will decrease coverage by 0.20%.
The diff coverage is 13.04%.

@@            Coverage Diff             @@
##             main     #206      +/-   ##
==========================================
- Coverage   36.31%   36.11%   -0.21%
==========================================
  Files          29       29
  Lines        1743     1764      +21
==========================================
+ Hits          633      637       +4
- Misses       1110     1127      +17

Flag
Coverage Δ

unittests
36.11% <13.04%> (-0.21%)
:arrow_down:

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

Impacted Files
Coverage Δ

dbt_coves/tasks/load/airbyte.py
20.54% <ø> (ø)

dbt_coves/tasks/setup/dbt.py
36.00% <0.00%> (-0.49%)
:arrow_down:

dbt_coves/tasks/setup/utils.py
52.38% <0.00%> (+2.38%)
:arrow_up:

dbt_coves/tasks/setup/ssh.py
31.42% <15.15%> (-3.10%)
:arrow_down:

dbt_coves/__init__.py
100.00% <100.00%> (ø)

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 a12a439...98ed916. Read the comment docs.


Formulate instructions for participants

The e-mail to the previous workshop is here.

is this enough for you?
Instructions for all attendees
You need to have admin rights to your computer in order to install software:

All attendees: please install R and RStudio: https://posit.co/download/rstudio-desktop/
Attendees to the Julia workshop: please install Julia, VSCode and Julia extension for VSCode following these instructions: https://formal-methods-mpi.github.io/Workshop.jl/stable/0_preparation/preparation/
Other software (namely Git) will be installed during the workshops.


scope c methods are yellow not green

I've been running dracula theme for nvim for a while and can't figure out why my methods calls are yellow and not green. For example in this screenshot printf in yellow and char/string in yellow makes it hard to read, distinct between a method name and char/strings.
Installed through lazy and loading theme and using dracula.setup({ ..
what am I doing wrong?

Tried a bunch of stuff, it works in JS as expected but not C.
as soon as you do semicolon at end lines the green method name turns yellow.

Its lsp symantic token i guess We need to add support for that. I will do that asap


Abitlity to modify BeeInput in overriden _run() method in bee agend

Is your feature request related to a problem? Please describe.
In the use case I was working with I needed to modify  the system prompt
in my _run() method for some invocations before calling super.run().
I  ended up having to modify the state of the agent (this.input.templates.system) before
calling super.run() and then restore the state afterwards. This works and seems to be
ok since the agent currently enforces that only one request is running at time, but
its not ideal.
Describe the solution you'd like
Adding another parameter 'beeInput: BeeInput = this.input' the value of which would then be used in
this line - https://github.com/i-am-bee/bee-agent-framework/blob/9054deb30c59986186410667bc2852e9595033b4/src/agents/bee/agent.ts#L105C3-L106C1
instead of this.input or something along those lines.
Describe alternatives you've considered
Modifying the agent state (this.input.templates.system) before/after calling super._run()
Additional context
I'm not sure if my case will be common enough to warrant the change but if you think it would be useful I'm happy to submit a PR.

You can modify the template like this without overriding the agent's behavior.
See: https://github.com/i-am-bee/bee-agent-framework/blob/main/examples/agents/bee_advanced.ts#L40-L45

You can modify input/output by registering callback for events (think of it as middleware).
See https://i-am-bee.github.io/bee-agent-framework/#/emitter?id=agent-usage

@Tomas2D I figured out I could modify the default prompt when the agent was created but I want to modify it not for all interactions but just for some specific ones based on analysis of the question itself.
I don't think the ways you mention allow you to do that, but if you think they can I'll take another look.

To make it a bit more concrete this is what I'm doing:
async _run(input, options, run) {
    if (CHECK_FUNCIONS_RELEVANCE) {
      const useFunctions = await this.functionsRelevant(input.prompt, this.memory.messages);
      if (!useFunctions) {
        // modifying the state of the agent is not ideal but works
        // because the agent only allows one request to be executing
        // at a time.
        if (!this.input.templates)
          this.input.templates = {};
        this.input.templates.system = this.noToolsPrompt;
      }
    };

    let result;
    try {
      result = await super._run(input, options, run);
    } finally {
      // restore the modified state
      this.input.templates = this.originalTemplates;
    }
    return result;
  }
}

I see. So, would you like an override parameter for each iteration? This is a very specific usage, and I don't see any way to smoothly integrate it into the framework without overcomplicating it. Hence, your solution is fine.

Ok so the suggestion is just to keep doing what I'm doing versus adding an another paramter, right? If so I'll close this issue.

From v0.0.34, you can override BeeAgentRunner with your custom one, which may help. But we will not add new parameters to the run / _run method right now.


Custom Commission Plan

Dear all,
how can I create a custom commission plan?
Thank you
Alex

@dipialx
Edit the Execution object to match your brokers commision. Your question to vague and you need to provide more details to get a serious answer.
Regards
James


Notifee Android Build Not getting Generated and throwing error.

Hi there,iam using notifee version 7.8.0 with RN 0.72.3 but in Android build is not getting generated.In Ios its working fine.

Where:
Build file<EMAIL_ADDRESS>line: 46

What went wrong:
A problem occurred evaluating project ':notifee_react-native'.

Circular referencing during evaluation for project ':app'.
This the error logs that has been thrown.
My Gradle version is 7.5.1,

I faced the same issue with the same error. Here is how I solved it (Please correct me if my approach is wrong)
Let me know if any more details are required from me
First of all, here is my configuration for Gradle and react native:
React Native version: 0.66.5
@notifee/react-native version: ^7.8.0
gradle version: 7.5.1
JDK version: 11
android\build.gradle
// Top-level build file where you can add configuration options common to all sub-projects/modules.

buildscript {
    ext {
        buildToolsVersion = "33.0.0"
        minSdkVersion = 21
        compileSdkVersion = 33
        targetSdkVersion = 33

        // We use NDK 23 which has both M1 support and is the side-by-side NDK version from AGP.
        ndkVersion = "23.1.7779620"
    }
    repositories {
        google()
        mavenCentral()
    }
    dependencies {
        classpath('com.android.tools.build:gradle:7.3.1')
        classpath 'com.google.gms:google-services:4.3.15'
        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

allprojects {
    repositories {
        mavenCentral()
        tasks.withType(Javadoc).all { enabled = false }
        mavenLocal()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url("$rootDir/../node_modules/react-native/android")
        }
        maven {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }

        google()
        maven { url 'https://www.jitpack.io' }
    }

    // #  Makes lint continue the build if there is an error occurred in any dependencies
    afterEvaluate {
        if (getPlugins().hasPlugin('android') || getPlugins().hasPlugin('android-library')) {
            configure(android.lintOptions) {
                abortOnError false
                checkReleaseBuilds false
            }
        }
    }
}

android\app\build.gradle
buildscript {
    repositories {
        maven { url 'https://plugins.gradle.org/m2/' } // Gradle Plugin Portal
    }
    dependencies {
        classpath 'gradle.plugin.com.onesignal:onesignal-gradle-plugin:[0.12.6, 0.99.99]'
    }
}

apply plugin: 'com.onesignal.androidsdk.onesignal-gradle-plugin'

apply plugin: "com.android.application"

apply plugin: 'com.google.gms.google-services'

import com.android.build.OutputFile

/**
 * The react.gradle file registers a task for each build variant (e.g. bundleDebugJsAndAssets
 * and bundleReleaseJsAndAssets).
 * These basically call `react-native bundle` with the correct arguments during the Android build
 * cycle. By default, bundleDebugJsAndAssets is skipped, as in debug/dev mode we prefer to load the
 * bundle directly from the development server. Below you can see all the possible configurations
 * and their defaults. If you decide to add a configuration block, make sure to add it before the
 * `apply from: "../../node_modules/react-native/react.gradle"` line.
 *
 * project.ext.react = [
 *   // the name of the generated asset file containing your JS bundle
 *   bundleAssetName: "index.android.bundle",
 *
 *   // the entry file for bundle generation. If none specified and
 *   // "index.android.js" exists, it will be used. Otherwise "index.js" is
 *   // default. Can be overridden with ENTRY_FILE environment variable.
 *   entryFile: "index.android.js",
 *
 *   // https://reactnative.dev/docs/performance#enable-the-ram-format
 *   bundleCommand: "ram-bundle",
 *
 *   // whether to bundle JS and assets in debug mode
 *   bundleInDebug: false,
 *
 *   // whether to bundle JS and assets in release mode
 *   bundleInRelease: true,
 *
 *   // whether to bundle JS and assets in another build variant (if configured).
 *   // See http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Build-Variants
 *   // The configuration property can be in the following formats
 *   //         'bundleIn${productFlavor}${buildType}'
 *   //         'bundleIn${buildType}'
 *   // bundleInFreeDebug: true,
 *   // bundleInPaidRelease: true,
 *   // bundleInBeta: true,
 *
 *   // whether to disable dev mode in custom build variants (by default only disabled in release)
 *   // for example: to disable dev mode in the staging build type (if configured)
 *   devDisabledInStaging: true,
 *   // The configuration property can be in the following formats
 *   //         'devDisabledIn${productFlavor}${buildType}'
 *   //         'devDisabledIn${buildType}'
 *
 *   // the root of your project, i.e. where "package.json" lives
 *   root: "../../",
 *
 *   // where to put the JS bundle asset in debug mode
 *   jsBundleDirDebug: "$buildDir/intermediates/assets/debug",
 *
 *   // where to put the JS bundle asset in release mode
 *   jsBundleDirRelease: "$buildDir/intermediates/assets/release",
 *
 *   // where to put drawable resources / React Native assets, e.g. the ones you use via
 *   // require('./image.png')), in debug mode
 *   resourcesDirDebug: "$buildDir/intermediates/res/merged/debug",
 *
 *   // where to put drawable resources / React Native assets, e.g. the ones you use via
 *   // require('./image.png')), in release mode
 *   resourcesDirRelease: "$buildDir/intermediates/res/merged/release",
 *
 *   // by default the gradle tasks are skipped if none of the JS files or assets change; this means
 *   // that we don't look at files in android/ or ios/ to determine whether the tasks are up to
 *   // date; if you have any other folders that you want to ignore for performance reasons (gradle
 *   // indexes the entire tree), add them here. Alternatively, if you have JS files in android/
 *   // for example, you might want to remove it from here.
 *   inputExcludes: ["android/**", "ios/**"],
 *
 *   // override which node gets called and with what additional arguments
 *   nodeExecutableAndArgs: ["node"],
 *
 *   // supply additional arguments to the packager
 *   extraPackagerArgs: []
 * ]
 */

project.ext.react = [
    enableHermes: false,  // clean and rebuild if changing
]

apply from: "../../node_modules/react-native/react.gradle"
apply from: "../../node_modules/react-native-code-push/android/codepush.gradle"

/**
 * Set this to true to create two separate APKs instead of one:
 *   - An APK that only works on ARM devices
 *   - An APK that only works on x86 devices
 * The advantage is the size of the APK is reduced by about 4MB.
 * Upload all the APKs to the Play Store and people will download
 * the correct one based on the CPU architecture of their device.
 */
def enableSeparateBuildPerCPUArchitecture = false

/**
 * Run Proguard to shrink the Java bytecode in release builds.
 */
def enableProguardInReleaseBuilds = false

/**
 * The preferred build flavor of JavaScriptCore.
 *
 * For example, to use the international variant, you can use:
 * `def jscFlavor = 'org.webkit:android-jsc-intl:+'`
 *
 * The international variant includes ICU i18n library and necessary data
 * allowing to use e.g. `Date.toLocaleString` and `String.localeCompare` that
 * give correct results when using with locales other than en-US.  Note that
 * this variant is about 6MiB larger per architecture than default.
 */
def jscFlavor = 'org.webkit:android-jsc:+'

/**
 * Whether to enable the Hermes VM.
 *
 * This should be set on project.ext.react and mirrored here.  If it is not set
 * on project.ext.react, JavaScript will not be compiled to Hermes Bytecode
 * and the benefits of using Hermes will therefore be sharply reduced.
 */
def enableHermes = project.ext.react.get("enableHermes", false);

/**
 * Architectures to build native code for in debug.
 */
def nativeArchitectures = project.getProperties().get("reactNativeDebugArchitectures")

android {
    ndkVersion rootProject.ext.ndkVersion

    compileSdkVersion rootProject.ext.compileSdkVersion

    defaultConfig {
        applicationId "com.saudkh.yuehlia"
        minSdkVersion rootProject.ext.minSdkVersion
        targetSdkVersion rootProject.ext.targetSdkVersion
        versionCode 550
        versionName "2.5.5"
        multiDexEnabled true
    }
    splits {
        abi {
            reset()
            enable enableSeparateBuildPerCPUArchitecture
            universalApk false  // If true, also generate a universal APK
            include "armeabi-v7a", "x86", "arm64-v8a", "x86_64"
        }
    }
    signingConfigs {
        debug {
            storeFile file('debug.keystore')
            storePassword 'android'
            keyAlias 'androiddebugkey'
            keyPassword 'android'
        }
        release {
            if (project.hasProperty('MYAPP_UPLOAD_STORE_FILE')) {
                storeFile file(MYAPP_UPLOAD_STORE_FILE)
                storePassword MYAPP_UPLOAD_STORE_PASSWORD
                keyAlias MYAPP_UPLOAD_KEY_ALIAS
                keyPassword MYAPP_UPLOAD_KEY_PASSWORD
            }
        }
    }
    buildTypes {
        debug {
            signingConfig signingConfigs.debug
                        if (nativeArchitectures) {
                ndk {
                    abiFilters nativeArchitectures.split(',')
                }
            }
        }
        release {
            // Caution! In production, you need to generate your own keystore file.
            // see https://reactnative.dev/docs/signed-apk-android.
            signingConfig signingConfigs.release
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
        }
    }

    // applicationVariants are e.g. debug, release
    applicationVariants.all { variant ->
        variant.outputs.each { output ->
            // For each separate APK per architecture, set a unique version code as described here:
            // https://developer.android.com/studio/build/configure-apk-splits.html
            def versionCodes = ["armeabi-v7a": 1, "x86": 2, "arm64-v8a": 3, "x86_64": 4]
            def abi = output.getFilter(OutputFile.ABI)
            if (abi != null) {  // null for the universal-debug, universal-release variants
                output.versionCodeOverride =
                        defaultConfig.versionCode * 1000 + versionCodes.get(abi)
            }

        }
    }
}

dependencies {
    implementation fileTree(dir: "libs", include: ["*.jar"])
    // implementation "com.facebook.react:react-native:+"  // From node_modules

    implementation "androidx.swiperefreshlayout:swiperefreshlayout:1.0.0"

    implementation 'androidx.multidex:multidex:2.0.1'

    // implementation 'com.google.firebase:firebase-analytics:21.3.0'

    implementation 'com.facebook.fresco:animated-gif:2.5.0' // Animated GIF support

    debugImplementation("com.facebook.flipper:flipper:${FLIPPER_VERSION}") {
        exclude group:'com.facebook.fbjni'
    }

    debugImplementation("com.facebook.flipper:flipper-network-plugin:${FLIPPER_VERSION}") {
        exclude group:'com.facebook.flipper'
        exclude group:'com.squareup.okhttp3', module:'okhttp'
    }

    debugImplementation("com.facebook.flipper:flipper-fresco-plugin:${FLIPPER_VERSION}") {
        exclude group:'com.facebook.flipper'
    }

    if (enableHermes) {
        def hermesPath = "../../node_modules/hermes-engine/android/";
        debugImplementation files(hermesPath + "hermes-debug.aar")
        releaseImplementation files(hermesPath + "hermes-release.aar")
    } else {
        implementation jscFlavor
    }
}

// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
    from configurations.implementation
    into 'libs'
}

apply from: file("../../node_modules/@react-native-community/cli-platform-android/native_modules.gradle"); applyNativeModulesAppBuildGradle(project)
apply from: "../../node_modules/react-native-vector-icons/fonts.gradle"

Error stack:
Where:
Build file<EMAIL_ADDRESS>line: 46

What went wrong:
A problem occurred evaluating project ':notifee_react-native'.

Circular referencing during evaluation for project ':app'.

with this known, this is how I managed to go around the error (not convinced that this is the optimal workaround, but it worked for me):
in notifee gradle.build file I managed to remove the line 46 that is mentioned in the error stack

Build file<EMAIL_ADDRESS>line: 46

// remove this
else {
    project.evaluationDependsOn(":app")
}

vreoo's solution also works for me. Would be nice if this gets fixed in the next version.

@pinktonio Try removing OneSignal Dependency from the gradle File,

could you provide more context on why should the one signal dependency be removed? How will that affect onesignal itself on the app and how this is related to notifee issue?

@vreoo It is possible that both are Notifications library and one dependency is dependent on the same resource and both are in a deadlock situation,from what I have figured it,After removing the OneSignal Dependency it build successfully.and this issue happens only in Android and not on iOS,iOS works fine.

@pinktonio Try removing OneSignal Dependency from the gradle File,

Thanks @LakshuEshakti, that worked. I commented out the two lines for the OneSignal plugin in the /android/app/build.gradle file:
buildscript {
    repositories {
        gradlePluginPortal()
    }
    dependencies {
        // classpath 'gradle.plugin.com.onesignal:onesignal-gradle-plugin:[0.12.10, 0.99.99]'
    }
}

// apply plugin: 'com.onesignal.androidsdk.onesignal-gradle-plugin'

The build was successfull after that and notifee and OneSignal push notifications still work.

What procedure did you take to make sure that OneSignal still worked after you commented these two lines out? I am afraid removing such a line without knowing the risks can lead to so many troubles than notifee not working. I'd really appreciate sharing this info with us. Because if it's proved that it won't harm the build for Onesignal or its functionality, then I might apply this change to my version.

After i created the build I ran it on my simulator, triggered a test notifee notification and a test OneSignal notification and it all worked fine.

@pinktonio iOS works fine, the issue is with the Android Build, So try confirming the Test Notification from Onesignal for both Live/Debug Android Build,(also try testing in real devices sometimes emulators behave weirdly.)
Hope that this will help you in figuring out the root cause.

@pinktonio What procedure did you take to make sure that OneSignal still worked after you commented these two lines out? I am afraid removing such a line without knowing the risks can lead to so many troubles than notifee not working. I'd really appreciate sharing this info with us. Because if it's proved that it won't harm the build for Onesignal or its functionality, then I might apply this change to my version.

@vreoo i think both Notifee and Onesignal reference the same resources from the Android Kernel,hence one is dependent on the other,and that is the reason we are busted with Circular Referencing Error from notifee,Moreover in iOS the resource allocation is different as compared to Android,so we dont get any error from iOS Platform.
Maybe OneSignal will patch this error in the future but till then this workaround maybe the possible solution.

I am not an Android Expert, but that Makes sense to me. Thank you...
I will try this approach and see how it will behave.

For anyone who comes across this issue, please refer to this doc page it will help you solve this issue if you are using onesignal.
https://notifee.app/react-native/docs/integrations/onesignal


Implementing a Generic Singly linked list Data Structure in Java

Article checklist
Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[ ] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes

Remove the backticks and add the issue number below to link and close your Topic Suggestion (issue) when your article has been published (PR has been merged). See this video for more details.

This closes #4382

Finally, delete the article checklist notes in blockquotes and submit your PR. We look forward to reviewing your article.

@lalith1403 @Dawe-7
This is the new PR
Duplicate of #4691

@Dawe-7 we will be closing this PR to allow the author the proper time to make any and all needed corrections.
This is a duplicate PR - if any more changes were needed (in general) we should close the PR immediately especially if its a duplicate PR (generally there are always exceptions).
cc @LynnMumo
It seems this PR is still quite a bit aways from being completed.  As a rule of thumb - please only submit articles (pull requests) with a complete and fully polished article - ready to be published.
All revisions and edits should be completed on your own forked repo (as to not take up room in the queue).
We will be closing this and please re-submit when it is ready to be published as a new PR (and you can add the duplicate label) and ping the reviewer and myself.
Closing a PR does NOT mean the article can not be published (or fixed) it simply means that the edits, revisions, and fixes will happen outside of the queue.

@Dawe-7 we will be closing this PR to allow the author the proper time to make any and all needed corrections.
This is a duplicate PR - if any more changes were needed (in general) we should close the PR immediately especially if its a duplicate PR (generally there are always exceptions).
cc @LynnMumo
It seems this PR is still quite a bit aways from being completed. As a rule of thumb - please only submit articles (pull requests) with a complete and fully polished article - ready to be published.
All revisions and edits should be completed on your own forked repo (as to not take up room in the queue).
We will be closing this and please re-submit when it is ready to be published as a new PR (and you can add the duplicate label) and ping the reviewer and myself.
Closing a PR does NOT mean the article can not be published (or fixed) it simply means that the edits, revisions, and fixes will happen outside of the queue.

Okay @hectorkambow

@Dawe-7
I have done some edits for the requested changes. You can reopen the PR and have a look at my last commit. Thanks.
cc @hectorkambow

@linetachieng, reopening so changes can be effected.

@LynnMumo
Good afternoon and thank you for submitting your topic to the EngEd program.
If it seems this PR is still quite a bit aways from being completed.
As a rule of thumb - please only submit articles (pull requests) with a complete and fully polished article - ready to be published.
All revisions and edits should be completed on your own forked repo (as to not build up a backlog in the queue).
We will be closing this and please re-submit when it is ready to be published as a new PR (and you can add the duplicate label) and ping the reviewer and myself.
Closing a PR does NOT mean the article can not be published (or fixed) it simply means that the edits, revisions, and fixes will happen outside of the queue.
👍

@hectorkambow the article was ready. I did some changes when the article was closed. I don't understand why you closed it again.

@hectorkambow, the author created a new PR and it was in final review on my end. I was going through everything to ensure it was ready for publishing. The article did not have extensive revisions, any delays caused were on my end.

@hectorkambow, reopening to finish review.

I'll be jumping on this one

@LynnMumo
Question how did you start to submit your article without signing up with the program?

We were having a discussion about EngEd with my friends and that's how I
found out that I never enrolled. All I knew was that you only submit a
topic and the other activities follow. I'm sorry.
On Wed, Dec 8, 2021, 2:16 AM hectorkambow @.***> wrote:

@LynnMumo https://github.com/LynnMumo
Question how did you start to submit your article without signing up with
the program?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/section-engineering-education/engineering-education/pull/5261#issuecomment-988331894,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVN5LCNPRX3V7FP7SMWMCUDUP2IUBANCNFSM5I4D2KTQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Application Libraries tracking.

Must use at least one new library, package, or technology that we haven’t discussed

GIS tested.

"dependencies": {
"bcrypt": "^5.0.1",
"connect-session-sequelize": "^7.1.1",
"dotenv": "^8.2.0",
"express": "^4.17.1",
"express-handlebars": "^5.2.1",
"express-session": "^1.17.1",
"food": "^0.3.5",
"g-i-s": "^2.1.6",
"handlebars": "^4.7.7",
"mysql2": "^2.2.5",
"sequelize": "^6.5.1"

This issue is created as a reminder to create a library to host the user's information as well as what they add to their cart in the dashboard

Handlebars have been completed


CN S1G 761.5 Channel can not be set

Dear newracom sir,
I found some problems when testing open AP on CN channel. When I set S1G_CH:7615, the following error is displayed.
[------------LOG------------]
[ctrl_iface_receive_response] cmd: set country CN
wim: 0 country code:CN freq:0
api: 0 CC(CN) from driver is different from CC(US) from cal. data
s1g: 0 index:5 CC: 'CN', # of CH:14
wim: 0 auto txgain is activated
reply_len: 2
reply: OK
[wifi_init] TX Power (18 dBm)
[wifi_task] wifi_init Success !!
[wifi_start_softap] Trying to start Soft AP (SSID:my_demo, S1G_CH:7615 , BW:1)
[ctrl_iface_receive_response] cmd: add_network
reply_len: 1
reply: 0
[0][_nrc_wifi_set_state] state=DISCONNECTED
[STAGetNonS1GFreqWithBw] invalid frequency, s1g_freq:7615
[0][nrc_wifi_softap_set_conf] invalid s1g_freq:7615, bw:1
[wifi_start_softap] Fail to set sotftap config
[wifi_task] ASSERT! Fail to start softap
[------------END------------]
In addition, when I tested S1G 7555, I could turn on the AP normally, but it was turned on to 5210. The corresponding value should be 5180 according to the table.
[------------LOG------------]
[ctrl_iface_receive_response] cmd: set country CN
wim: 0 country code:CN freq:0
api: 0 CC(CN) from driver is different from CC(US) from cal. data
s1g: 0 index:5 CC: 'CN', # of CH:14
wim: 0 auto txgain is activated
reply_len: 2
reply: OK
[wifi_init] TX Power (18 dBm)
[wifi_task] wifi_init Success !!
[wifi_start_softap] Trying to start Soft AP (SSID:my_demo, S1G_CH:7555 , BW:1)
[ctrl_iface_receive_response] cmd: add_network
reply_len: 1
reply: 0
[0][_nrc_wifi_set_state] state=DISCONNECTED
[ctrl_iface_receive_response] cmd: set_network 0 mode 2
reply_len: 2
reply: OK
[ctrl_iface_receive_response] cmd: ndp_preq 1
wim: 0 set ndp probe request: 1
reply_len: 2
reply: OK
[ctrl_iface_receive_response] cmd: set_network 0 frequency 5210
reply_len: 2
reply: OK
[ctrl_iface_receive_response] cmd: set_network 0 scan_freq 5210
reply_len: 2
reply: OK
[ctrl_iface_receive_response] cmd: set_network 0 ssid "my_demo"
reply_len: 2
reply: OK
[ctrl_iface_receive_response] cmd: set_network 0 pairwise CCMP
reply_len: 2
reply: OK
[ctrl_iface_receive_response] cmd: set_network 0 group CCMP
reply_len: 2
reply: OK
[ctrl_iface_receive_response] cmd: set_network 0 key_mgmt WPA-PSK
reply_len: 2
reply: OK
[ctrl_iface_receive_response] cmd: set_network 0 proto RSN
reply_len: 2
reply: OK
[------------END------------]

It seems that there are some discrepancies between the channel mapping table in the library and the documentation (UG-7292-003-S1G_Channel.pdf).

UG-7292-003-S1G_Channel.pdf
7555 in DOC is not mapping to 5210, but in LIB is.
CHANNEL_MAPPING_TABLE <7555, 5210, 1, 0xD, 9, 0, 0x1D42, 0x2A, 5, 0>
LIB CHANNEL_MAPPING_TABLE


After recovery with seed and channel.backup only offchain funds recovered not onchain

Is there another way to recover the onchain funds beside resync the raspiblitz node from scratch again? I got around 1million sat from the channels back but I am mising 2 million sat from onchain wallet.

Now that you closed all channels with the channel.backup file. Shutdown RaspiBlitz and install the LND Desktop App on your laptop: https://github.com/lightninglabs/lightning-app/releases and use the seed words to recover on-chain funds again.
Somehow the LND Desktop App has more success in recovering the on-chain funds by seed words. Not sure why yet and what we do different with LND on the Blitz compared to the LND Desktop App - because recovery window is set to 250 (what should be the same the Desktop App is using). We tested already with very big recovery windows (--recovery_window=250000), but it just made recovery very very slow and had not always success.
See details on issue https://github.com/rootzoll/raspiblitz/issues/278
In the RaspiBlitz the important code is to find in:
raspiblitz/home.admin/config.scripts/lnd.initwallet.py
see lines 153/183
@halseth from lightning labs will be at the ligthning hackathon in munich - hope he can take a look at this and help out

thanks for your respone rootzoll
I actually read this part but could not proceed further because I saw no way to add the cipher passphrase extra word into the lightning app. Do I miss something?

Best to get feedback on the LND Slack channel for the LND Dektop App: https://dev.lightning.community

@lebowski36 There's no way around rescanning the chain to get on-chain funds back.
@rootzoll How are you getting new addresses from lnd? If you don't use the UNUSED_ address types, then extensive polling of the API can cause address inflation and make it harder to find the uses addresses on rescan.

"I do get the error invalid passphrase, the seed is entered correct tried 3 times"
any solution about the passphrase error on LND desktop wallet?
i have the same problem with the Lightning app 0.5.1-alpha , can't recover

I helped a user to restore funds recently. Managed to get off-chain funds back using the seed and SCB on the RaspiBlitz, but on-chain funds were not restored.
Once cashed out the channel balances proceeded to restore with the seed in the desktop Lightning app.
Funds appeared, but unfortunately the autopilot is on by default in the app, so done some unnecessary channel opening and closing to be able to get all the funds into cold storage eventually.
Do we still think that the restore process on the RaspiBlitz is missing to scan the addresses with the balances?
It is interestingly quite consistent at that.
I will try to reproduce the problem with a couple of sats myself.

@halseth the raspiblitz gets new addresses for funding in mostly two ways:
BBfundWallet.sh (used from SSH main menu)
lncli --chain=${network} --network=${chain}net newaddress np2wkh

and thru the RTL WebGUI (when activated) thru the /newaddress API endpoint .. the user can choose the type. I cannot find any documentation on a UNUSED_ parameter. Can you point us into the right direction here?
@halseth also see the procedure described above how RaspiBlitz users at the moment handle fund recovery: https://github.com/rootzoll/raspiblitz/issues/632#issuecomment-500121764 - within this process users that set a seed-encryption password seem to fail - but users that created a seed without a password can recover on-chain funds with the lnd-desktop app, but not with the RaspiBlitz. What is the RaspiBlitz doing different here? This is how the raspiblitz is trying to recover a wallet from seed at the moment:
/config.scripts/lnd.iniwallet.py (python protobuff interface)
    request = ln.InitWalletRequest(
        wallet_password=walletpassword,
        cipher_seed_mnemonic=seedwords,
        recovery_window=250,
        aezeed_passphrase=seedpassword
    )

    try:
        response = stub.InitWallet(request)

before v1.3 we used simply lncli call with initwallet and seed info, but also was not able to recover on-chain funds durign scan - even with a very very big recoverywindow.

I could recover the onchain wallet funds by generating the private keys of the wallet using a couple of web utilities.
https://guggero.github.io/cryptography-toolkit/#!/aezeed
In this web pasting the seed and the passphrase in the decode mnemonic section and obtaining the HD node root key.
Then pasting the root key on Ian Coleman's BIP39 mnemonic code converter
https://iancoleman.io/bip39/
(Bip 32 root key) and generating as many adresses/private keys pairs  as wished using the Bip84 derivation path.

@mikelmore thanks for sharing your knowledge!
I am also trying to recover funds without channel.backup. There are funds that are sent back to my wallet (because I requested the peer to force close the payment channel).
With only my seed I was trying to recover the funds that where sent back.

The first step, putting the seed on an offline html:
https://guggero.github.io/cryptography-toolkit/#!/aezeed
Works nice, but I have to say that I don't have a passphrase (rapiblitz).

Putting the HD node root key into the BIP 32 root key with the html tool https://iancoleman.io/bip39/ gives me the ability to generate different keys.

I tried the following things;

For each Derivation Path (BIP32, BIP44, BIP49, BIP84 and BIP141);
I have tried the results from  "account extended private key" en "BIP32 Extended Pirivate Key" into the Electrum master key recover.
Results; no funds

Than I generate 50k addresses from the BIP84, and try to recover it from private key,
In Electrum recovery with private key.

Results: no funds
What am I doing wrong? I know the seed I have is the good one, because I already used to recover the onchain funds. No I want to recover the funds that where sent back from forced closed channel.
I hope you can help me out here.

Hello, I only tried with wallets created from seed + passphrase and it worked like a charm. You only need the first address to wich you sent  your initial funds to find out if it works.
Once you get your HD derivation key  use the Bip84 derivation path on Ian Coleman' s Bip39 web utility. I only needed like 40 adresses and 40 change adresses to get all the funds.
From the aezeed spec:
Init quote
aezeed enciphering/deciperhing
Next, we’ll take the plaintext seed described above and encipher it to procure a final cipher text. We’ll then take this cipher text (the CipherSeed) and encode that using a 24-word mnemonic. The enciphering process takes a user-defined passphrase. If no passphrase is provided, then the string “aezeed” will be used.
End quote
I would try using "aezeed" but I have not tried myself.
I hope it helps.
Mikel
El 8 de julio de 2019 0:45:16 CEST, RED29<EMAIL_ADDRESS>escribió:

@mikelmore thanks for sharing your knowledge!
I am also trying to recover funds without channel.backup. There are
funds that are sent back to my wallet (because I requested the peer to
force close the payment channel).
With only my seed I was trying to recover the funds that where sent
back.

The first step, putting the seed on an offline html:
https://guggero.github.io/cryptography-toolkit/#!/aezeed
Works nice, but I have to say that I don't have a passphrase
(rapiblitz).

Putting the HD node root key into the BIP 32 root key with the html
tool https://iancoleman.io/bip39/ gives me the ability to generate
different keys.

I tried the following things;

For each Derivation Path (BIP32, BIP44, BIP49, BIP84 and BIP141);
I have tried the results from  "account extended private key" en
"BIP32 Extended Pirivate Key" into the Electrum master key recover.
Results; no funds

Than I generate 50k addresses from the BIP84, and try to recover it
from private key,
In Electrum recovery with private key.

Results: no funds
What am I doing wrong? I know the seed I have is the good one, because
I already used to recover the onchain funds. No I want to recover the
funds that where sent back from forced closed channel.
I hope you can help me out here.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/rootzoll/raspiblitz/issues/632#issuecomment-509036661

--
Enviado desde mi dispositivo Android con K-9 Mail. Por favor, disculpa mi brevedad.

@rootzoll Looks like the Lightning App is also using 250: https://github.com/lightninglabs/lightning-app/blob/7b055a2704631c344bc0add526d86da35a92be20/src/config.js#L31
Are you saying that recovery never works for you, or just sometimes fail? If it never works my guess is that maybe something is wrong with how the seed/password bytes are handled on the python side. I would try logging the raw bytes of the InitWalletRequest both from your python script and from the Lightning App to see where they differ.

You can find the definition of the address types here, doesn't look like they are picked up by the API doc generator for some reason: https://github.com/lightningnetwork/lnd/blob/93aad89f4c132089d77181a7aec5d717bf1c621a/lnrpc/rpc.proto#L1014

Are you saying that recovery never works for you, or just sometimes fail?

@halseth recovering the on-chain balance is not working out of the box. As you can see in this issue people were able to recover thru other workarounds ... like using the app or manual scripts. But when doing it with RaspiBlitz it almost always failed. Older lnd versions sometime showed parts of the on-funds - when people made very big recovery windows ... but that was also just a lucky shot and not working all the time.

my guess is that maybe something is wrong with how the seed/password bytes are handled on the python side. I would try logging the raw bytes of the InitWalletRequest both from your python script and from the Lightning App to see where they differ.

@halseth We had the problems with not recovering the on-chain funds also in ealier versions of RaspiBlitz were we used the original lncli dialog to init/recover from seed words. No we use the python/gRPC call like this
    request = ln.InitWalletRequest(
        wallet_password=walletpassword,
        cipher_seed_mnemonic=seedwords,
        recovery_window=250,
        aezeed_passphrase=seedpassword,
        channel_backups=scbHexString
    )

So not sure were we can do someting wrong with the byte handling of the seed words -. because they are just a basic string and they seem to produce the same node id after recovery .. so its the same/correct seed (and password). Seems this so far correct?

You can find the definition of the address types here, doesn't look like they are picked up by the API doc generator for some reason

@halseth how can the address type help? I dont get the context within recovery process - please explain. Thanks.

I could recover the onchain wallet funds by generating the private keys of the wallet using a couple of web utilities.
https://guggero.github.io/cryptography-toolkit/#!/aezeed
In this web pasting the seed and the passphrase in the decode mnemonic section and obtaining the HD node root key.
Then pasting the root key on Ian Coleman's BIP39 mnemonic code converter
https://iancoleman.io/bip39/
(Bip 32 root key) and generating as many adresses/private keys pairs as wished using the Bip84 derivation path.

For completeness and to aid recovering funds pasting the recent article from @guggero about restoring only from the seed and using the information from 1ml.com to generate a "fake" channel backup file: https://medium.com/@guggero/did-you-lose-funds-on-the-lightning-network-because-of-a-disk-crash-8971b6a92494

Not sure if this is the underlying issue regarding the LND desktop app but somethign happend on LND side: Issue: #3168 Wallet recovery with passphrase is not working
I think it's not yet released though.

@escapedcat thanks for the link ... what they discuss mostly passing parameters correctly to the LND REST API - in RaspiBlitz we use the gRPC thru python. I dont see this related.

Ah sorry, I was hoping it's somehow relevant to the workaround recovery using the LND desktop app as discussed above. Because I also get the invalid passphrase error message when trying to recover with the 24 words seed as @lebowski36 mentioned. The app isn't even asking for a passphrase.

Yes that the LND Desktop is not asking for a password is a bummer and makes it impossible to recover old RaspiBlitz Wallets with it. Thats why the newer RaspiBlitz versions, dont ask for a seedpassword anymore.

Hm, I guess I'll wait till this works someho, will create a new wallet when 1.4 is coming out and start fresh withour trying a recovery. Eventually this will work in a easy way I guess. The suggested approach from @mikelmore seems a bit over head to be honest.

@rootzoll an idea here:
The RaspiBlitz menu defaults to fund the LND wallet on a nested witness key hash address (3...)
The channel closures will return to Bech32/witness key hash (bc1.. ) addresses.
It seems that on restore from the seed (+/- SCB) the RaspiBlitz only shows the funds on the Bech32 addresses.
I think it is time to default to fund the wallets on Bech32 addresses as they are the cheaper option and those are supported by majority of CoinJoin clients too (Wasabi and Whirpool  - JoinMarket is working with nested witness key hash (3...).
It could help to solve this issue too.
In the meantime I was funding my LND wallet with Bech32 addresses anyway manually:
lncli newaddress p2wkh
- p2wkh:  Pay to witness key hash = Bech32 (bc1...)
- np2wkh: Pay to nested witness key hash = P2SH (3..)

@openoms added that idea to the final v1.4 release: #1018

Default funding changed to bech32, this can be closed.


Add support for errors on inline snapshots

Summary

Test plan

I'm not sure why "Node LTS on Ubuntu with coverage" is failing. I can't reproduce it locally. Given that all the other CI workflows pass, including other ubuntu with node LTS in the matrix, I am inclined to merge this as-is.

@ayazhafiz should we remove those checks from the matrix before merge?

I don’t feel strongly. I feel okay merging as is if you do

From: Michael Glass @.>
Sent: Monday, July 24, 2023 7:27:01 AM
To: rwx-research/jest-abq @.>
Cc: Ayaz @.>; Mention @.>
Subject: Re: [rwx-research/jest-abq] Add support for errors on inline snapshots (PR #36)
@ayazhafizhttps://github.com/ayazhafiz should we remove those checks from the matrix before merge?
—
Reply to this email directly, view it on GitHubhttps://github.com/rwx-research/jest-abq/pull/36#issuecomment-1647816937, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AE6GL6UTVRRME76CMA67TRLXRZSZLANCNFSM6AAAAAA2R6CHYY.
You are receiving this because you were mentioned.Message ID: @.***>


[85] [Chore] Add unit test for Survey Detail module

Resolves https://github.com/llleyelll/ic-surveys-ios/issues/85
What happened 👀

Add unit tests for Survey Detail Module

Proof Of Work 📹

Please resolve your conflicts please 🙏

Please resolve your conflicts please 🙏

@markgravity The conflict has been resolved 🙇♀


Move too specific code from  AbstractVersionControlService to GitLab service

Description
Moves the CI_TOKEN value parameter and all related code from the AbstractVersionControlService to the GitLab service. The reason is, that we currently only need this code for the GitLab + Jenkins combination. We might want to revert this change if we ever add new CI and VCS combinations or connect Bitbucket to Jenkins, but for now this is cleaner.

I updated the application-artemis.yml and the test application.yml configs.
I also update the setup.md with the new config values and comments.