unable to find a path to destination while having a direct channel open

So, buying stickers.
lncli decodepayreq lnbc576792910p1pdt2vk2pp5q9936mulrmwd0ecvejpntv49vtjcwpfca79hdrvycjzsw4jy0vrqdzsgfkx7cmtwd68yetpd5azqdpw8yujq42ngssxvmeqv9hxggzvd9nksarwd9hxwgznw35kx6m9wgs8sgp3cqpgaw6prmh7ydru0qp9pghvgxt59an6ls4vdynqaarckx5tcqfk3jfx9sz7hvamxx90j8ucuzeslvd30tva6adfm6n08rhsu76yymj4zlgpj4ky0e

{
    "destination": "02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432",
    "payment_hash": "014b1d6f9f1edcd7e70ccc8335b2a562e5870538ef8b768d84c4850756447b06",
    "num_satoshis": "57679",
    "timestamp": "1521824458",
    "expiry": "3600",
    "description": "Blockstream: 4.99 USD fo and Lightning Sticker x 1",
    "description_hash": "",
    "fallback_addr": "",
    "cltv_expiry": "8"
}

I have a direct channel open with the destination:
lncli listchannels
{
    "channels": [
...
        {
            "active": true,
            "remote_pubkey": "02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432",
            "channel_point": "b5b307532a96e15f7217cbe37ead2f737f75c4a1b7102ab0e81a1584fff4728a:0",
            "chan_id": "565822977311309824",
            "capacity": "303567",
            "local_balance": "303386",
            "remote_balance": "0",
            "commit_fee": "181",
            "commit_weight": "600",
            "fee_per_kw": "250",
            "unsettled_balance": "0",
            "total_satoshis_sent": "0",
            "total_satoshis_received": "0",
            "num_updates": "0",
            "pending_htlcs": [
            ],
            "csv_delay": 144
        },
...

And yet, while trying to pay:
lncli payinvoice lnbc576792910p1pdt2vk2pp5q9936mulrmwd0ecvejpntv49vtjcwpfca79hdrvycjzsw4jy0vrqdzsgfkx7cmtwd68yetpd5azqdpw8yujq42ngssxvmeqv9hxggzvd9nksarwd9hxwgznw35kx6m9wgs8sgp3cqpgaw6prmh7ydru0qp9pghvgxt59an6ls4vdynqaarckx5tcqfk3jfx9sz7hvamxx90j8ucuzeslvd30tva6adfm6n08rhsu76yymj4zlgpj4ky0e

{
	"payment_error": "unable to find a path to destination",
	"payment_preimage": "",
	"payment_route": null
}

... And just like that, it suddenly worked. Sorry to bother!

I'm having the same issue

It took a few minutes after I opened that direct channel before the payment went through. Also (just a thought) does the channel have enough capacity to relay your payment amount?

On Apr 12, 2018, at 8:26 PM, Manveer Jarosz<EMAIL_ADDRESS>wrote:
I'm having the same issue
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/lightningnetwork/lnd/issues/931#issuecomment-380983885, or mute the thread https://github.com/notifications/unsubscribe-auth/AEPsSLJd8VuR2Y7Ka6O54m2n0nHwzBadks5tn_DCgaJpZM4S5IAP.

I forgot we have to wait for the channel to go from "pending" to "active" 😅
Everything worked once it became active.


feat: [#243] Optimize the return of controller

Closes #
📑 Description

✅ Checks

[x] My pull request adheres to the code style of this project
[x] My code requires changes to the documentation
[x] I have updated the documentation as required
[x] All the tests have passed

ℹ Additional Information

Codecov Report
Patch coverage is 91.04% of modified lines.

Files Changed
Coverage

context_request.go
84.21%

context_response.go
91.04%

context.go
100.00%

response.go
100.00%

utils.go
100.00%

view.go
100.00%

:loudspeaker: Thoughts on this report? Let us know!.


[Feat]: Allow customisation of script type on accept (mainly for use with Partytown)

https://github.com/orestbida/cookieconsent/blob/540c235fd2b945d3e49d152f209762fed2716796/src/cookieconsent.js#L1624
It would be nice to be able to change the type to type="text/partytown" and trigger a ptupdate after consent is given
https://partytown.builder.io/partytown-scripts#dynamically-appending-scripts
Idea 💡
on a script you add data-type="text/partytown"
change line 1624 to:
// 99% of the time people will want the default
curr_script.type = curr_script.getAttribute('data-type') || 'text/javascript';

then a user can handle their own callback

//...
cc.run({
    // ...
    onAccept: function(cookie){
        window.dispatchEvent(new CustomEvent('ptupdate'));
    },
    // ...
});

What do you think?

Hi @spacedawwwg,
this feature is already implemented in v3. However, since this is a very tiny code addition, we can also implement it in v2.

Boom 💥

@orestbida
I tested this in 2.9.0 and 3. But it looks like only the first script is activated, other scripts get ignored. Am I doing something wrong?
If you look at the screenshot, first script is now active type="text/partytown-x". the second is still type="text/plain"

Thanks

@spacedawwwg,
the first script in the screenshot has a src attribute, and the current implementation will wait for the onload/onerror event to fire before loading other script tags, to ensure that all script tags are loaded sequentially.
https://github.com/orestbida/cookieconsent/blob/1efe109194f38143d074e66bb7ce53df70397c62/src/utils/scripts.js#L164-L170
The onload/onerror event — however — is never fired due to the invalid javascript mime type: type="text/partytown-x". This also prevents all the other scripts from loading.

@spacedawwwg please try this branch and let me know if that fixes it!


[Feature Request] add SDK support of a new transaction type: ValidatorTransaction

🚀 Feature Request Description
Add SDK support of a new transaction type: ValidatorTransaction.
Motivation
ValidatorTransactions (node API, AIP) are designed to be only proposed by validators to publish system-level resources.
It's a building block of ZKID, on-chain randomness (and perhaps more things in the future).
1.10 release will be its debut, and therefore when SDK support is needed.

@zjma could you clarify the SDK requirements?

Does the SDK need to support read and write ValidatorTransaction operations?
If write, could you share code snippets to how a ValidatorTransaction should be constructed?

@0xmaayan i assume write = submit a txn?
If so, only read support is needed. This new type of txns is only proposed by validators.


Improve watch performance by using stable identities for Snapshot iterables

A large monorepo my team works on is seeing an issue where Webpack rebuilds report as finished, but webpack-dev-server doesn't respond until a minute later.
Summary
Starting with performance changes up front. (See below for a description of what we were seeing.) Here's the LazySet merge performance for compilation.fileDependencies in this monorepo before/after:

merge Loop Iterations
Timing(ms)

Before
1,198,677
23,045.10

After
464,918
1,726.25

These aren't scientific timings ran over multiple trials. I can perform that if needed.
Investigation
CPU Profiling
Running the build in a CPU profiler revealed a large amount of time spent calling watchpack's watch function. This is after the initial Webpack build. The white space in the profile below is in between the initial build, and saving a file in the repo that has just been modified.
https://github.com/webpack/webpack/blob/e2f1592f7e4d8f0578e5bb23d6a863b4a2b5f309/lib/Watching.js#L303-L307

Going down the call stack, it looks like watchpack iterates over compilation.fileDependencies, triggering LazySet's merge function.
https://github.com/webpack/webpack/blob/93ce24d2dc40ee972a2ea5138f3c181563c913fd/lib/util/LazySet.js#L16-L22
I patched the merge function to output how many items were being iterated over and their time.
const { performance } = require("perf_hooks");
const merge = (targetSet, toMerge) => {
    let count = 0;
    const before = performance.now();
    for (const set of toMerge) {
        for (const item of set) {
            targetSet.add(item);
            count++
        }
    }
    if (count > 5000) {
        const duration = performance.now() - before;
        console.log(`Items iterated during merge: ${count}, ${duration} ms`)
    }
};

The results:
Items iterated during merge: 1198677, 23045.103875994682 ms
Items iterated during merge: 726370, 8386.988652005792 ms

The 1st set iterated corresponds to compilation.fileDependencies.
LazySet toMerge Duplicates
Inspecting compilation.fileDependencies in an interactive debugger shows that this LazySet has a lot of duplicates in its toMerge field.
Adding a breakpoint to the merge function commented on above and inspecting the toMerge argument:
❯ toMerge.size
128116
❯ new Set([...toMerge].map(snapshotIterable => snapshotIterable.snapshot)).size
62175

This is after LazySet._toMerge has had its contents moved from LazySet._toDeepMerge. Attaching a screenshot of the call stack in VS Code's debugger if that helps.

What kind of change does this PR introduce?
One of the reasons _toMerge gets so large is because every SnapshotIterable is uniquely constructed, even if they're derived from the same underlying Snapshot class.
This PR gives snapshot iterables stable identifiers, which reduces the items in the _toMerge set and significantly improved performance in this app.
After this change, the log output from above becomes:
Items iterated during merge: 464918, 1726.2539209723473 ms
Items iterated during merge: 561334,<PHONE_NUMBER>0397873 ms

Did you add tests for your changes?
I added tests to ensure the snapshot iterables returned are stable across multiple calls, but the tests could probably be written better. I'd appreciate a gut check from the Webpack team that this change makes sense before improving tests more.

Does this PR introduce a breaking change?
It does not.

What needs to be documented once your changes are merged?

Questions for Reviewers
Thanks for looking at this!

Does this change make sense, or should I investigate improving performance of this watch call in a different way?
Would it make sense to use WeakRef to prevent these saved iterable objects from living longer than necessary? I think we'd have to check for the API's existence and gracefully fallback to support older Node.js versions.

Opening as ready for review. I contacted my company's CLA management team to work out the EasyCLA.

I believe I saw the same bottleneck before, then reported as https://github.com/webpack/webpack/issues/15231.

@JoostK Thanks for linking that. I was curious if others had seen this issue. I would be interested to know if the patch here alleviates the problem for your team if you have a moment to manually apply and test.
While this PR brought our team's merge time down from 1 minute, I did notice times still vary from 1s to 4s. I think Snapshot can non-deterministically end up in a deeply nested state that takes SnapshotIterator a bit of time to flatten. I was hoping to continue investigating there, but I'm not sure if it's worthwhile yet unless it would help others.

I just checked with this patch applied and it didn't seem any faster. I haven't taken measurements but it doesn't seem like it resolves #15231.

Got it. I'd wager there's more work needed here too. The next step I was thinking of was attempting to serialize the Snapshot tree and comparing it between the fast ~1s merge case and slow ~4s case.
As a heads up, the watch -> merge slowness this PR addresses can be difficult to perceive without measuring/profiling. The watch call happens after Webpack says it's ready/done, so the timings here aren't typically printed on the console. If you have time, I would be curious if the lib/Watching.js timings are different in @mattlewis92's profiling here: https://github.com/webpack/webpack/issues/15231#issue-1111649057

Does this change make sense, or should I investigate improving performance of this watch call in a different way?

Makes sense to me

Would it make sense to use WeakRef to prevent these saved iterable objects from living longer than necessary? I think we'd have to check for the API's existence and gracefully fallback to support older Node.js versions.

I don't think that makes sense, since each iterator only keeps a referenced to the Snapshot, so it doesn't add any large memory overhead. Actually it reduces memory since only a single iterator is created per Snapshot.

Items iterated during merge: 1198677, 23045.103875994682 ms

Items iterated during merge: 464918, 1726.2539209723473 ms

It's interesting that reducing the count by 50% improves performance by 13x. Why is that? Maybe the SnapshotIterables are far more expensive than the remaining Iterables during merge, and the number of SnapshotIterables was also reduced by ~13x.

I think Snapshot can non-deterministically end up in a deeply nested state

The way Snapshots are optimized is really non-deterministic, since it depends a lot on the order and speed in creating them (which depends on fs operations).

I contacted my company's CLA management team to work out the EasyCLA.

:+1:
The PR looks good and I'll merge it afterwards

I don't think that makes sense, since each iterator only keeps a referenced to the Snapshot, so it doesn't add any large memory overhead. Actually it reduces memory since only a single iterator is created per Snapshot.

Nice. Glad to have a second pair of eyes to confirm that.

It's interesting that reducing the count by 50% improves performance by 13x. Why is that? Maybe the SnapshotIterables are far more expensive than the remaining Iterables during merge, and the number of SnapshotIterables was also reduced by ~13x.

I was surprised by this too and came to the same conclusion as you. I think the SnapshotIterable objects that were duplicated were typically more nested/larger than the more unique objects.
I hadn't thought of this until your memory comment just now, but I'd expect garbage collection of SnapshotIterable objects to happen less in this watch -> merge call now. There may have been performance improvements from just not running GC as frequently.

The way Snapshots are optimized is really non-deterministic, since it depends a lot on the order and speed in creating them (which depends on fs operations).

👍 Thanks for confirming that. That's nice to know.

Are the codecov status errors something that's been seen before in the Webpack repo?

It is possible that the changes here affected code paths in tests, but wanted to check if this was seen before investigating how my changes would have affected logic in lib/Compiler.js and lib/Compilation.js.

@gluxon Ignore it, it is normal for big changes, especial for 0.01 :smile:

Understood. Thanks! 😄

Thanks

Thanks for the reviews and fast turnaround time! Hope this helps Webpack's users. 🤞


ValueError: Linear is expecting 2D arguments: [2, None, 50]  while 'python qrn.py'

with tf1.2
(venv) ali-186590cc37a5:Mango$ python qrn.py
aname
('the value of ccc is  ', 'this is a string')
on func:test at file:andy_common.py #28
('the value of aname is  ', 111111)
qa1_single-supporting-fact
3242 (seed)
vocab = [u'.', u'?', u'Daniel', u'John', u'Mary', u'Sandra', u'Where', u'back', u'bathroom', u'bedroom', u'garden', u'hallway', u'is', u'journeyed', u'kitchen', u'moved', u'office', u'the', u'to', u'travelled', u'went']
X.shape = (1000, 10, 7)
Xq.shape = (1000, 4)
Y.shape = (1000, 22)
story_maxlen, query_maxlen = 10, 4
Traceback (most recent call last):
File "qrn.py", line 542, in
model = RNN_Model(config)
File "qrn.py", line 53, in init
story_question_state = self.add_model(self.inputs_story, self.inputs_question)
File "qrn.py", line 176, in add_model
dtype=tf.float32)
File "qrn.py", line 443, in custom_bidirectional_dynamic_rnn
time_major=time_major, scope=fw_scope)
File "/Users//ve_tf1.0_py2/venv/lib/python2.7/site-packages/tensorflow/python/ops/rnn.py", line 546, in dynamic_rnn
dtype=dtype)
File "/Users//ve_tf1.0_py2/venv/lib/python2.7/site-packages/tensorflow/python/ops/rnn.py", line 713, in _dynamic_rnn_loop
swap_memory=swap_memory)
File "/Users//ve_tf1.0_py2/venv/lib/python2.7/site-packages/tensorflow/python/ops/control_flow_ops.py", line 2605, in while_loop
result = context.BuildLoop(cond, body, loop_vars, shape_invariants)
File "/Users//ve_tf1.0_py2/venv/lib/python2.7/site-packages/tensorflow/python/ops/control_flow_ops.py", line 2438, in BuildLoop
pred, body, original_loop_vars, loop_vars, shape_invariants)
File "/Users//ve_tf1.0_py2/venv/lib/python2.7/site-packages/tensorflow/python/ops/control_flow_ops.py", line 2388, in _BuildLoop
body_result = body(*packed_vars_for_body)
File "/Users//ve_tf1.0_py2/venv/lib/python2.7/site-packages/tensorflow/python/ops/rnn.py", line 696, in _time_step
skip_conditionals=True)
File "/Users//ve_tf1.0_py2/venv/lib/python2.7/site-packages/tensorflow/python/ops/rnn.py", line 177, in _rnn_step
new_output, new_state = call_cell()
File "/Users//ve_tf1.0_py2/venv/lib/python2.7/site-packages/tensorflow/python/ops/rnn.py", line 684, in
call_cell = lambda: cell(input_t, state)
File "/Users//ve_tf1.0_py2/venv/lib/python2.7/site-packages/tensorflow/contrib/rnn/python/ops/core_rnn_cell_impl.py", line 524, in call
output, new_state = self._cell(inputs, state, scope)
File "/Users//Mango/qrn/qrncell.py", line 28, in call
c = self._activation(linear(tf.concat(inputs, 1), self._num_units))
File "/Users//Mango/qrn/qrncell.py", line 51, in linear
raise ValueError("Linear is expecting 2D arguments: %s" % str(shape))
ValueError: Linear is expecting 2D arguments: [2, None, 50]
(venv) ali-186590cc37a5:Mango$

I forgot to push the right script version, sorry. It should be fixed now, please let me know if you encounter more issues.


Create iccamera.txt

lib/domains/it/iccamera.txt
School website
www.iccamera.edu.it

@giuamm First stage of verification passed, official domain for Istituto Comprensivo Camera Sala Consilina (Salerno) is iccamera.it as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@giuamm Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


Draft review - Katy Huff

The M&C paper draft is ready for review.
Due to the 10-page limit, I cut down the scope to only 1-D models & results. I still need to cut it down by one page. I'm considering removing some of the middle energy group plots in Figures 5 & 6. Please let me know if you have any other suggestions for cutting.
main.pdf

Thank you for the quick turnaround!

Nice paper -- looks good. Not sure how to shorten. Honestly, maybe it could be split into two papers if they give you a chance with a deadline extension.


Fixes 579: add status filter

Todo:

[ ] Tests?

Todo:

[ ]  Tests?

Hmm yeah. Tests would be good but rather complicated 🙄.
I probably should have added some earlier.

I'll add some tests to this later.

Hi, it is I, with a question. If I select Invalid, I only see Invalid repos. However, if I then select Valid as well, the Valid repo comes back but in the middle of the two Invalid repos, it does not sort them again. Is that to be expected? It only sorts once?
Before:

After:

Thank you.

@swadeley  i'm not sure i can quite reproduce what you mean, or maybe i don't fully understand what you mean.  In your screenshot, both shots seem sorted by name?

@swadeley i'm not sure i can quite reproduce what you mean, or maybe i don't fully understand what you mean. In your screenshot, both shots seem sorted by name?

ahh, Filter by Status not equal to Sorted by Status, OK, sorry. So its working as designed then.


Mitmproxy dont working on windows 10

Problem Description
Mitmproxy completely installed on windows10. But dont working. All of them is empty. There is no flow. Also ım using windows that's why "mitmproxy --version command" not working on cmd.
Steps to reproduce the behavior:

System Information
windows 10 2004, wsl installed, mitmproxy version 5

screenshot:
https://i.ibb.co/427SjGJ/Screenshot-2.png

You need to configure your browser/device/... to use mitmproxy. Are you doing that?

yes ı did and solved. I used mozilla. But however ı dont sniff internet data of other devices of connect to same modem.

For further support and how-to questions, please use StackOverflow. Thanks!


Issue with apostrophe?

Hey :wave:,
This is a really user-friendly and nice package! Thanks a lot :-)
I noticed that punctfix has some problems with apostrophe it seems. E.g.:
>>> from punctfix import PunctFixer
>>> model = PunctFixer(language="en")

>>> example_text = "Let's go"
>>> print(model.punctuate(example_text))

doesn't seem to work as it gives:
AssertionError: Something went wrong due to handling of a long text... Tried matching the word: Let with Let's

I'm running the following versions:
torch==1.13.1+cu116
tokenizers==0.11.6
transformers==4.26.0

Hey! Thank you for trying out this model and for helping us improve it by filing an issue.
As you write in https://github.com/huggingface/speechbox/issues/2, we only take raw text into consideration when reconstructing punctuation, so the model has been trained on text normalized to no punctuation. This was also assumed to be the case during inference which is the cause of the error.
We will fix this normalization upstream such that this should run without error.
-- Søren


formControlName not working with nz-select

Version
0.6.14
Environment
Ubuntu 16.04, Chrome 63.0.3239.108, 0.6.14
Reproduction link
https://stackblitz.com/edit/ng-zorro-antd-nz-select-formcontrolname?file=app%2Fapp.component.html
Steps to reproduce
Run the example, look in the developer console for error
What is expected?
No error
What is actually happening?
ERROR TypeError: control.registerOnChange is not a function
at setUpModelChangePipeline (shared.js:131)
at setUpControl (shared.js:48)
at FormGroupDirective.addControl (form_group_directive.js:125)
at FormControlName._setUpControl (form_control_name.js:201)
at FormControlName.ngOnChanges (form_control_name.js:114)
at checkAndUpdateDirectiveInline (provider.js:250)
at checkAndUpdateNodeInline (view.js:482)
at checkAndUpdateNode (view.js:425)
at debugCheckAndUpdateNode (services.js:525)
at debugCheckDirectivesFn (services.js:466)
Other?
Works with nz-input but not nz-select

Actually I think I needed to use formArrayName - my bad

have u soled this problem?i use formArrayName,but i can not get the value

Can you reproduce?


Permanently excluding paths/files

Certain files are very common among open applications. Some examples I see includes ci_stdlib.metallib, ci_filters.metallib, Cache.db*. They're rarely of interest and more of a distraction.
It could be quite helpful if we had the ability to save a list of patterns with paths/filenames that we'd like to exclude permanently from the listing.

Good idea. Will implement in Sloth 3.0.

Will implement in 3.1.


Multiple LinkAdrRequests after join

Hi,
We are having some connectivity issues with our nodes where we are missing uplinks from the node. After some research we found that when the node joins the network it receives multiple LinkAdrRequests in under a minute.
The scenario can be described like the following:

Join request
Join accept
Uplink, application payload, f_cnt: 1
Downlink, Link ADR request dr: 5, tx_power: 1
Uplink, MAC data only, Link ADR answer, f_cnt: 2
Downlink, Link ADR request dr: 5, tx_power: 4
Uplink, MAC data only, Link ADR answer, f_cnt: 3
Downlink, Link ADR request dr: 5, tx_power: 7
No further data until next periodic uplink.

Note that the time it takes from the first uplink (3.) to the last uplink (7.) takes place in about 16 seconds. To my current understanding tx_power: 7 indicates that our node is requested to output 14dBm below our maximum capable transmit power. For our node this would mean that our tx power will be lowered from +14dBm to 0dBm (if my calculations are correct).
Because of how aggressive the transmit power of our node is lowered I went looking into the default ADR algorithm located in chirpstack/src/adr/default.rs. I found that almost exactly matches the algorithm as described in https://www.thethingsnetwork.org/forum/uploads/default/original/2X/7/7480e044aa93a54a910dab8ef0adfb5f515d14a1.pdf. Although this is an old preliminary document but as of current I couldn't find a newer version of it on the Semtech website.
I mentioned that it almost matched the reference algorithm because the Chirpstacks implementation seems to be not taking into account that the algorithm requires at least 20 uplinks as an input with frame counters from Fn to Fn-19 however in the scenario described earlier this doesn't seem to be the case. The ADR algorithm is executed while the frame counter hasn't exceeded 20 frames.
From reviewing the default.rs the 20 uplinks seem to be only taken into account when increasing the spreading factor (decreasing the data rate) to prevent oscitation. However the document describes that the algorithm requires 20 uplink frames. The document also describes a strategy on when to send the LinkAdrRequest, one of which is to only send an ADR request when the node sets the ADR_ACK_REQ bit and the other describes to send the request every Nth frame.
I would expect that after a Join we would only receive an ADR command to update the chanel mask but the next ADR message to actually change the data rate or tx power of the end node after the uplink frame counter has exceeded 20 (at least according to the documentation I have available). The next ADR change I would then expect to be 20 uplinks after (fCnt >= 40) the first etc. (or when ADR_ACK_REQ is set). At least when Chiprstack has enough data to safely increase the datarate and lower the tx power.
Also after a join I would expect the history to be cleared but I'm currently unsure if this is true.
Is it possible to change the ADR algorithm to use apply the 20 frame history after a join? Or am I missing something else?
We are running Chirpstack 4.9.0 on the network server.
A port of https://github.com/Lora-net/SWL2001/releases/tag/v4.3.0 on the node.
I've atached a log file that contains more information releated to this issue.
log adr on join.json

At least when Chiprstack has enough data to safely increase the datarate and lower the tx power.

Please note that the tables contains the best SNR of each uplink (in case reported by multiple gateways). Then the best SNR of the last 20 items is used to calculate the number of data-rate increases and / or tx-power decreases. ChirpStack resets the table on every ADR change, as an ADR change invalidates previously collected values.
Therefore I believe it doesn't matter to wait until the table is full or not before starting the algorithm, because it will only get more optimistic (increasing the data-rate / lowering the tx-power even more), not less.

The AdrACKReq bit (now) serves a different purpose. If ADR is enabled at the end-device, and it doesn't receive a downlink for ADR_ACK_LIMIT uplinks, it will set this flag to request a downlink from the network-server, even if it is empty to confirm that the device is still connected.

Therefore I believe it doesn't matter to wait until the table is full or not before starting the algorithm.

I understand that if the ADR algorithm works on the best SNR it shouldn't really matter if you wait until the table is full or on the next uplink that happens to have a better SNR. However in our case an ADR request triggers an instant reply when received by the node. The chirpstack then uses this ADR reply to again determine a new DR and tx power limit. This proces repeats until there is not enough margin left to lower the datarate or tx power. So instead of having a table with data that is filled with due to the behavior of the node (it's send interval or events), it's being filled with ADR replies that are received within a minute after joining. The ADR algorithm is now working on data that would otherwise not be available if the node didn't answer instantly.

because it will only get more optimistic (increasing the data-rate / lowering the tx-power even more), not less.

Sorry I don't really understand, how having more samples over a prolonged time at a static datarate and tx power would lead to a more optimistic result? Or do you mean that over time, even using a full table the node would eventually get an ADR request to the same datarate and tx power as it did after joining?

The AdrACKReq bit (now) serves a different purpose. If ADR is enabled at the end-device, and it doesn't receive a downlink for ADR_ACK_LIMIT uplinks, it will set this flag to request a downlink from the network-server, even if it is empty to confirm that the device is still connected.

Totally agree, I think the document doesn't intent to replace that behavior but rather adding to it. So in addition to the (possible empty) downlink also use it as a moment to run the ADR algorithm and send a ADR request.

Or do you mean that over time, even using a full table the node would eventually get an ADR request to the same datarate and tx power as it did after joining?

Correct. The ADR algorithm uses the best SNR from the table, thus more items would never result in a lower data-rate.

I think the document doesn't intent to replace that behavior but rather adding to it.

The ADR_ACK_LIMT is 64. Which means this ADRACKReq bit is only set in case there have been 64 uplinks without any (data) downlink. Thus if there are regular downlinks, the ADRACKReq bit might never been set during the lifetime of the device. Thus this is not a good trigger for ADR mac-commands.

However in our case an ADR request triggers an instant reply when received by the node.

Please note that this is end-device application specific. Not all nodes will immediately respond to mac-commands. Some devices will postpone the confirmation until the next uplink.
I'm going to close this issue because I do not see a reason to change the implementation. I do however understand that the default implementation does not suit all implementation. Please note that it is possible to implement your own ADR algorithm (in JS). Please see the ChirpStack configuration options. Here is an example skeleton:
https://github.com/chirpstack/chirpstack/blob/master/examples/adr_plugins/plugin_skeleton.js


not returning dictionary of the results

when I run db.result(<>) I get:
TypeError: cannot convert dictionary update sequence element #0 to a sequence
I don't see where the code is getting the column names and adding those to the tuple or dictionary. the only thing that I can successfully return is the 'proxy'

Fixed by #24

Fixed by https://github.com/nerium-data/sqla-raw/pull/24


Fixes operatorkit delete error

Towards https://github.com/giantswarm/giantswarm/issues/2749
Not super towards the PM, but I noticed it when I was debugging. We don't take any action in delete anyway, so it's not a big deal.

We should just update vendor. Closing.


feat: event modal

Description
This PR adds the modal to add a new event.
Rresolves PADV-1761
Visual results
Before

After

How to test

Configure the flag enable_instructor_calendar in the site admin 18000 or override the content  of the request http://localhost:18000/api/mfe_config/ to have the flag in true

Go to '/instructors/:instructorUsername' if enable_instructor_calendar is true you should be able to see the calendar along with the events/ request, if the flag is false you shouldn't see any of both.

Functionality no longer required.


framework: have bitmap textures created by the asset loader tested for alpha too

Related to https://github.com/gearvrf/GearVRf-Tests/issues/126 and https://github.com/Samsung/GearVRf/pull/1433

GearVRf-DCO-1.0-Signed-off-by: Mihail Marinov<EMAIL_ADDRESS>

Can we check for transparency in GVRBitMapTexture.update() ? On the other hand, this will not be easy with the whole class being a bit messy with mBitmap fairly useless and update() method with a thread switch. Anyway, this is fixed in the Vulkan branch.

Will wait and see what's the situation in the vulkan branch.

#1370 is the Vulkan implementation.
In Vulkan, bitmap updates are routed through GVRBitmapTexture.setBitmap() to the native code. In the native code, BitmapImage::update(JNIEnv*, jobject, bool) checks for bitmap transparency.

Planning to merge on Friday


annot8-common-data has unneccessary dependency

Currently, annot8-common-data has a dependency on Guava, yet it does not appear to be used within the project. This dependency should be removed to keep file sizes down.

Appears to have been removed already


can we programmatically move using emit

Is it possible to move (using movement-controls the user (camera) either by some increment (say 1 m) or to an absolute position (kind of like teleporting but a very small distance say 1 m) in some manner using some emit? This is using nav-mesh constraint. Such a need may arise as part of some other gesture (click on an object) that the user may do. Thanks

Affecting movement-controls with events isn't supported, although you can certainly move the rig around using components like event-set. If you want to move the rig and have that respect nav-mesh constraints, you would need to write a custom controls component that "plugs into" the movement-controls system. This can be fairly simple (e.g. listen for an event) and will automatically get nav-mesh constraints applied. See: https://github.com/donmccurdy/aframe-extras/tree/master/src/controls#customizing-movement-controls

Thanks @donmccurdy . Will give event-set a shot before trying out a custom-control.

@donmccurdy : Related to this is my need is to (customise) animate the movement when a user via the keyboard keys or via the emit moves the rig. What I am building is a Robot (like an R2D2 as an avatar) that moves around using nav-mesh constraints (that is important to my need). Now, for every key forward press, I need to trigger a set of hinge based rotations and translations (as per robot elements) to move forward. This combination of rotations and translational movements based on the robot design is simple physics for a given desired distance. What I am trying to understand is: how do I coordinate the timings of the animation and (b) how do I get the distance that the robot must move. My assumption is that I will have to make a custom control overriding some of the functions of the base control  component. Any advise will be helpful. Thanks

Your custom component will be able to determine the speed that the robot moves, or you can choose a speed property on the movement-controls component. But yes your code would need to manage the animation, and I don't have a good answer for you there... the three.js forum may be worth a try? You could also look for tutorials about creating a "walk cycle" in tools like Blender. If you can export a few basic animations (walk, strafe left, strafe right) you can fade between them more easily than managing individual joints.

Thanks @donmccurdy . But that would mean that the animations within the model would have to match (on duration) with the speed of the custom component, right? Hence, lets say the user presses the up key to move the avatar forward,  the animation would have to be completed within the same time because the change in position of the rig would be done by the custom movement-controls. Am I right?
Will check the approach you are suggesting.

Oh. ok. That gives me enough fodder to pursue. Thanks @donmccurdy. Will hopefully find a way


correct the EvalModelTemplate methods - template

🚀 Feature
The EvalModelTemplate has some standard methods like train_step the template is such as <model_method>__<other_describtion>
Motivation
it is much easier to read the used methods if there are visually separated by two _

This won't be needed anymore as we are going to deprecate EvalModelTemplate in favour variation of BoringModels


Add doc with proofs for assertions in Marpa::R2::Semantics::Rank

Add proof of assertions in Marpa::R2::Semantics::Rank?  I have a Proof.pod in the Marpa::R2 docs as a source for this.

Issue moved from #123.


Update Appsody to 0.3.0 in Kabanero 0.5.0

Appsody v0.3.0 is available in certified operators.  We should pull it into Kabanero.

fixed with #360


Tried the tanstack router plugin with latest version of tanstack react router and its giving errors.

Mainly, in the route.gen.tsx file, its unable to find 2 imports -
import { createReactRouter, createRouteConfig, lazy, RouterProvider } from '@tanstack/react-router'

createReactRouter, createRouteConfig.
If we move back @tanstack/react-router version to what is used in example, it does work.

Hey, thanks for opening this. Yes @tanstack/react-router had some API changes recently and it will be updated in the generouted plugin soon.

Bro, you are a champ, fixing it so quickly. 🎉

Thanks man! Please let me know if all works as expected!


Flush response headers always when proxy gets a response

Headers were automatically flushed when response got data. That might not happen with watch requests and that's why we need to force flush.
Fixes #1988

One integration test seems to fail (even after retry). Maybe this has side-effects 🤔


Feat: Add Audit Log Feature for IDIR Administrators - 1037

This PR implements a comprehensive audit log feature for IDIR administrators, including backend API, frontend table view, sorting, filtering, search, and export functionality.
Suggestion
As the table grows, automatic archiving (e.g., moving older logs to an archive table) and purging (e.g., deleting very old logs) can be implemented in the future to maintain performance and manage storage efficiently.
Archiving

Create an audit_log_archive table with the same structure as audit_log.
Use a scheduled job (e.g., with pg_cron) to move records older than a certain threshold (e.g., 1 month) from audit_log to audit_log_archive.
Alternatively, consider creating date-based archive tables (e.g., audit_log_archive_2025_01) to organize logs by time periods.

Purging

Use a scheduled job (e.g., with pg_cron) to delete records older than a defined retention period (e.g., 1 years) from audit_log_archive.

Closes #1037

Looks like the backend tests are failing:
E   ModuleNotFoundError: No module named 'lcfs.tests.audit_log.conftest'

Looks like the backend tests are failing: E ModuleNotFoundError: No module named 'lcfs.tests.audit_log.conftest'

I fixed the issue with the failed organization tests. Thanks for your feedback, Daniel!


Image Intensity Discrepancies

As I mentioned via email, my team has observed some discrepancies in intensity and contrast when uploading GSE206391 human skin tissue images (https://www.ncbi.nlm.nih.gov/geo/query/acc.cgi?acc=GSE206391) in TissUMapps. The images appear to exhibit higher levels of reds when viewed in TissUMapps compared to when we use other programs such as QUPath or Windows Photo Viewer.
Following your recommendations, we have tried versions <IP_ADDRESS> and <IP_ADDRESS>, but the issue persists.

Hi, and thank you for opening an issue about this!
Can you check that you don't have the temporary tiff file created by TissUUmaps still present in the image folder? For that, remove the .tissuumaps folder next to the original jpg image, and then load the jpg image in the new version of TissUUmaps.
Let me know if it helps!

We have followed your instructions and removed the .tissuumaps file, and the problem is now fixed with the newest release of TissUUMaps.
Thank you for your assistance in resolving this issue!


Not loading when available_locales is set

Hi
I have a rails app, and when i set the available_locales to ANY value, is the translation not loaded, and i get "missing translation" everywhere. However this is only in production, not in development or test.
My configuration looks like this:
# config/initializers/locale.rb
I18n.load_path += Dir[Rails.root.join('config', 'locales', '*.{rb,yml}')]
I18n.available_locales = [ :en, :da ] # Will not load translations, unless this line is removed.
I18n.enforce_available_locales = true
I18n.default_locale = :da
I18n.locale = :da

Any suggestions?

I am unable to reproduce this issue on the latest master version of i18n.
If you're able to reproduce this issue, please let me know and I'll investigate.
Thanks!


add a library (apiapp) section missing in the doc

There are a section to add an opds feed (https://thorium.edrlab.org/docs/220_organizing/222_catalogs/) but nothing to add a french library with ApiAPP protocol.
Need to add a french documentation to target french users of these library services

Available in the (soon to be released) french epub: https://github.com/edrlab/thorium-reader-doc/blob/epub-doc/epub-doc/fr/src/pages/111_catalogs_actions.md#créer-un-compte-dans-une-bibliothèque-publique-française


Fix: Documentation of --only in tests cmd

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

According to the output of brew tests --help the --only flag should be used like this:
~ % brew tests --help
brew tests [-v] [--coverage] [--generic] [--no-compat] [--only=test_script/test_method] [--seed seed] [--trace] [--online] [--official-cmd-taps]:
    Run Homebrew's unit and integration tests.

But unfortunately, this syntax does not work:
~ % brew tests --only=audit/trailing_newline
Pass files or folders to run

Instead, the flag has to be used with a : instead of a / according to the implementation:
~ % brew tests --only=audit:trailing_newline
Using recorded test runtime
1 processes for 1 tests, ~ 1 tests per process

# Running tests with run options --name=test_trailing_newline --seed 18351:

.

Finished tests in 0.006506s, 153.7043 tests/s, 461.1128 assertions/s.

1 tests, 3 assertions, 0 failures, 0 errors, 0 skips

3 assertions, 0 errors, 0 failures, 0 skips, 1 test

Took 0 seconds

For this reason, I created this pull-request to fix the documentation error for brew tests --help

Nice catch! Can you run brew man and commit the generated changes? Thanks!

Thanks @MikeMcQuaid! Here are the manuals updates.

Still seeing a failure here: https://travis-ci.org/Homebrew/brew/jobs/200016179 Can you check it out? Thanks and sorry!

@MikeMcQuaid Thank you for the hint. I had to re-run the man page generator.

Thanks for your contribution to Homebrew!  You rock!


install problem

I bought a new virtual server and I'm trying to install it. but I get the errors in the images. what could be the problem?
I added the error log below
command used: "npm install -g humanifyjs"

log.txt

What's your node --version

What's your node --version

What's your node --version

I have v20.10.0 installed on my computer. I installed the same on the virtual server and tried again. First, it gave the error "Python is not installed" and then it gave the errors I added below.
operating system: server 2019
node version : v20.10.0
python version : Python 3.12.6

Do you have any solution suggestions?

Potentially duplicate of/similar root cause as the following issues:

https://github.com/jehna/humanify/issues/10
https://github.com/jehna/humanify/issues/71

With some notes from there:

If anyone still cannot make it work in Windows then my suggestion is to use WSL, it works with a couple of tweaks (I didn't test with GPU yet)
Originally posted by @neoOpus in https://github.com/jehna/humanify/issues/10#issuecomment-2359492811

There is a note about needing node.js 20 in the readme, but it seems to be easy to miss. I wonder which place would be better. Maybe a preinstall hook thst ensures the version?

So, you advise using this in WSL instead of directly on Windows NodeJS ?
Originally posted by @neoOpus in https://github.com/jehna/humanify/issues/71#issuecomment-2328180259

Unfortunately I have no idea how Windows works on development, the last time I used Windows as my main dev machine was over 10 years ago 😅
I'd guess both WSL and non-wsl should work fine, as long as you have recent enough version. You can use e.g. nvm to switch between versions on WSL
Originally posted by @jehna in https://github.com/jehna/humanify/issues/71#issuecomment-2329153373

log.txt

Skimming through the initial attached log, there seem to be a number of errors/warnings.
This part might not matter (not 100%, just guessing):
npm warn cleanup   [
npm warn cleanup     'C:\\Users\\Administrator\\AppData\\Roaming\\npm\\node_modules\\humanifyjs\\node_modules',
npm warn cleanup     [Error: EPERM: operation not permitted, rmdir 'C:\Users\Administrator\AppData\Roaming\npm\node_modules\humanifyjs\node_modules\isolated-vm\src'] {
npm warn cleanup       errno: -4048,
npm warn cleanup       code: 'EPERM',
npm warn cleanup       syscall: 'rmdir',
npm warn cleanup       path: 'C:\\Users\\Administrator\\AppData\\Roaming\\npm\\node_modules\\humanifyjs\\node_modules\\isolated-vm\\src'
npm warn cleanup     }
npm warn cleanup   ],
npm warn cleanup   [
npm warn cleanup     'C:\\Users\\Administrator\\AppData\\Roaming\\npm\\node_modules\\humanifyjs\\node_modules\\node-llama-cpp',
npm warn cleanup     [Error: EPERM: operation not permitted, rmdir 'C:\Users\Administrator\AppData\Roaming\npm\node_modules\humanifyjs\node_modules\node-llama-cpp\llama\llama.cpp'] {
npm warn cleanup       errno: -4048,
npm warn cleanup       code: 'EPERM',
npm warn cleanup       syscall: 'rmdir',
npm warn cleanup       path: 'C:\\Users\\Administrator\\AppData\\Roaming\\npm\\node_modules\\humanifyjs\\node_modules\\node-llama-cpp\\llama\\llama.cpp'
npm warn cleanup     }
npm warn cleanup   ],
npm warn cleanup   [
npm warn cleanup     'C:\\Users\\Administrator\\AppData\\Roaming\\npm\\node_modules\\humanifyjs',
npm warn cleanup     [Error: EPERM: operation not permitted, rmdir 'C:\Users\Administrator\AppData\Roaming\npm\node_modules\humanifyjs'] {
npm warn cleanup       errno: -4048,
npm warn cleanup       code: 'EPERM',
npm warn cleanup       syscall: 'rmdir',
npm warn cleanup       path: 'C:\\Users\\Administrator\\AppData\\Roaming\\npm\\node_modules\\humanifyjs'
npm warn cleanup     }
npm warn cleanup   ]
npm warn cleanup ]

This is probably a breaking error:
npm error code 1
npm error path C:\Users\Administrator\AppData\Roaming\npm\node_modules\humanifyjs\node_modules\node-llama-cpp
npm error command failed
npm error command C:\Windows\system32\cmd.exe /d /s /c node ./dist/cli/cli.js postinstall

This is probably only needed because no prebuilt binary was found:
npm error ^[[?25h+ Downloading cmake
npm error × Failed to download cmake

Failing to load a prebuilt binary is probably based on a combination of node version and system architecture. Then the 'build from source' might be failing because you're running it in cmd.exe rather than a shell like bash/similar (assuming it's written to be built on a *nix type system), or because you don't have appropriate dev tools installed/similar:

npm error Failed to load a prebuilt binary for platform "win" "x64", falling back to building from source. Error: Error: The specified module could not be found.
npm error<EMAIL_ADDRESS>npm error     at Module._extensions..node (node:internal/modules/cjs/loader:1586:18)
npm error     at Module.load (node:internal/modules/cjs/loader:1288:32)
npm error     at Module._load (node:internal/modules/cjs/loader:1104:12)
npm error     at Module.require (node:internal/modules/cjs/loader:1311:19)
npm error     at require (node:internal/modules/helpers:179:18)
npm error     at loadBindingModule (file:///C:/Users/Administrator/AppData/Roaming/npm/node_modules/humanifyjs/node_modules/node-llama-cpp/dist/bindings/getLlama.js:390:25)
npm error     at loadExistingLlamaBinary (file:///C:/Users/Administrator/AppData/Roaming/npm/node_modules/humanifyjs/node_modules/node-llama-cpp/dist/bindings/getLlama.js:276:37)
npm error     at async getLlamaForOptions (file:///C:/Users/Administrator/AppData/Roaming/npm/node_modules/humanifyjs/node_modules/node-llama-cpp/dist/bindings/getLlama.js:133:27)
npm error     at async Object.handler (file:///C:/Users/Administrator/AppData/Roaming/npm/node_modules/humanifyjs/node_modules/node-llama-cpp/dist/cli/commands/OnPostInstallCommand.js:12:13) {
npm error   code: 'ERR_DLOPEN_FAILED'
npm error }
npm error ^[[?25l^[[?25h'xpm' is not recognized as an internal or external command,
npm error operable program or batch file.
npm error Failed to build llama.cpp with no GPU support. Error: SpawnError: Command npm exec --yes --<EMAIL_ADDRESS>install @xpack-dev-tools/cmake@latest --no-save exited with code 1
npm error     at createError (file:///C:/Users/Administrator/AppData/Roaming/npm/node_modules/humanifyjs/node_modules/node-llama-cpp/dist/utils/spawnCommand.js:34:20)
npm error     at ChildProcess.<anonymous> (file:///C:/Users/Administrator/AppData/Roaming/npm/node_modules/humanifyjs/node_modules/node-llama-cpp/dist/utils/spawnCommand.js:47:24)
npm error     at ChildProcess.emit (node:events:519:28)
npm error     at cp.emit (C:\Users\Administrator\AppData\Roaming\npm\node_modules\humanifyjs\node_modules\cross-spawn\lib\enoent.js:34:29)
npm error     at ChildProcess._handle.onexit (node:internal/child_process:294:12)
npm error SpawnError: Command npm exec --yes --<EMAIL_ADDRESS>install @xpack-dev-tools/cmake@latest --no-save exited with code 1
npm error     at createError (file:///C:/Users/Administrator/AppData/Roaming/npm/node_modules/humanifyjs/node_modules/node-llama-cpp/dist/utils/spawnCommand.js:34:20)
npm error     at ChildProcess.<anonymous> (file:///C:/Users/Administrator/AppData/Roaming/npm/node_modules/humanifyjs/node_modules/node-llama-cpp/dist/utils/spawnCommand.js:47:24)
npm error     at ChildProcess.emit (node:events:519:28)
npm error     at cp.emit (C:\Users\Administrator\AppData\Roaming\npm\node_modules\humanifyjs\node_modules\cross-spawn\lib\enoent.js:34:29)
npm error     at ChildProcess._handle.onexit (node:internal/child_process:294:12)

'xpm' is not recognized as an internal or external command, npm error operable program or batch file.

https://xpack.github.io/

The xPack Reproducible Build Framework
Tools to manage, configure and build complex, package based, multi-target projects, in a reproducible way.

https://xpack.github.io/xpm/install/

Failed to load a prebuilt binary for platform "win" "x64", falling back to building from source. Error: Error: The specified module could not be found. npm error<EMAIL_ADDRESS>

https://github.com/withcatai/node-llama-cpp#installation

This package comes with pre-built binaries for macOS, Linux and Windows.
If binaries are not available for your platform, it'll fallback to download a release of llama.cpp and build it from source with cmake. To disable this behavior, set the environment variable NODE_LLAMA_CPP_SKIP_DOWNLOAD to true.

https://node-llama-cpp.withcat.ai/guide/building-from-source

INFO
If cmake is not installed on your machine, node-llama-cpp will automatically download cmake to an internal directory and try to use it to build llama.cpp from source.
If the build fails, make sure you have the required dependencies of cmake installed on your machine.

We can see the prebuilt dependencies in the node-llama-cpp package.json here:

https://github.com/withcatai/node-llama-cpp/blob/4ee10a90e954df26e9e7782d4e2f9e98daab24a5/package.json#L212-L224

  "optionalDependencies": {
    "@node-llama-cpp/linux-arm64": "0.1.0",
    "@node-llama-cpp/linux-armv7l": "0.1.0",
    "@node-llama-cpp/linux-x64": "0.1.0",
    "@node-llama-cpp/linux-x64-cuda": "0.1.0",
    "@node-llama-cpp/linux-x64-vulkan": "0.1.0",
    "@node-llama-cpp/mac-arm64-metal": "0.1.0",
    "@node-llama-cpp/mac-x64": "0.1.0",
    "@node-llama-cpp/win-arm64": "0.1.0",
    "@node-llama-cpp/win-x64": "0.1.0",
    "@node-llama-cpp/win-x64-cuda": "0.1.0",
    "@node-llama-cpp/win-x64-vulkan": "0.1.0"
  }

The source for these are here:

https://github.com/withcatai/node-llama-cpp/tree/master/packages/%40node-llama-cpp

Since there is a @node-llama-cpp/win-x64, the Failed to load a prebuilt binary for platform "win" "x64" part of the error is definitely.. interesting.
@Yusufkulcu Does the machine you're installing this on have access to the internet? I'm guessing it tries to dynamically decide which optional binary package it will need based on the system and install that.
We can see that when building the package, it runs npm run addPostinstallScript:

https://github.com/withcatai/node-llama-cpp/blob/4ee10a90e954df26e9e7782d4e2f9e98daab24a5/.github/workflows/build.yml#L465-L493

Which we can see is defined in package.json, and basically tells the built package to trigger node ./dist/cli/cli.js postinstall:

https://github.com/withcatai/node-llama-cpp/blob/4ee10a90e954df26e9e7782d4e2f9e98daab24a5/package.json#L51

"addPostinstallScript": "npm pkg set scripts.postinstall=\"node ./dist/cli/cli.js postinstall\"",

In cli/cli.js we can see that it registers the OnPostInstallCommand:

https://github.com/withcatai/node-llama-cpp/blob/4ee10a90e954df26e9e7782d4e2f9e98daab24a5/src/cli/cli.ts#L39

Which is defined here, and calls getLlamaForOptions:

https://github.com/withcatai/node-llama-cpp/blob/4ee10a90e954df26e9e7782d4e2f9e98daab24a5/src/cli/commands/OnPostInstallCommand.ts#L8-L30

Which is defined here, and seems to be the part of the package that gets the systems platform/architecture, and tries to determine if it can use prebuilt binaries or not/etc:

https://github.com/withcatai/node-llama-cpp/blob/4ee10a90e954df26e9e7782d4e2f9e98daab24a5/src/bindings/getLlama.ts#L291-L462

Within that, we can see there is a call to loadExistingLlamaBinary:

https://github.com/withcatai/node-llama-cpp/blob/4ee10a90e954df26e9e7782d4e2f9e98daab24a5/src/bindings/getLlama.ts#L367-L387
https://github.com/withcatai/node-llama-cpp/blob/4ee10a90e954df26e9e7782d4e2f9e98daab24a5/src/bindings/getLlama.ts#L464-L623

We can see the 'failed to load a prebuilt binary' message here within loadExistingLlamaBinary, within a catch block:

https://github.com/withcatai/node-llama-cpp/blob/4ee10a90e954df26e9e7782d4e2f9e98daab24a5/src/bindings/getLlama.ts#L598-L611

The actual triggering error is appended to the end of that message, so the root issue appears to be this part:
Error: Error: The specified module could not be found.
npm error<EMAIL_ADDRESS>npm error     at Module._extensions..node (node:internal/modules/cjs/loader:1586:18)
npm error     at Module.load (node:internal/modules/cjs/loader:1288:32)
npm error     at Module._load (node:internal/modules/cjs/loader:1104:12)
npm error     at Module.require (node:internal/modules/cjs/loader:1311:19)
npm error     at require (node:internal/modules/helpers:179:18)
npm error     at loadBindingModule (file:///C:/Users/Administrator/AppData/Roaming/npm/node_modules/humanifyjs/node_modules/node-llama-cpp/dist/bindings/getLlama.js:390:25)
npm error     at loadExistingLlamaBinary (file:///C:/Users/Administrator/AppData/Roaming/npm/node_modules/humanifyjs/node_modules/node-llama-cpp/dist/bindings/getLlama.js:276:37)
npm error     at async getLlamaForOptions (file:///C:/Users/Administrator/AppData/Roaming/npm/node_modules/humanifyjs/node_modules/node-llama-cpp/dist/bindings/getLlama.js:133:27)
npm error     at async Object.handler (file:///C:/Users/Administrator/AppData/Roaming/npm/node_modules/humanifyjs/node_modules/node-llama-cpp/dist/cli/commands/OnPostInstallCommand.js:12:13) {
npm error   code: 'ERR_DLOPEN_FAILED'
npm error }

@Yusufkulcu So I guess the first thing I would be doing is checking whether that file actually exists, and if there is anything that might be blocking it from being able to be loaded (permissions, antivirus, etc):

<EMAIL_ADDRESS>

I have v20.10.0 installed on my computer. I installed the same on the virtual server and tried again. First, it gave the error "Python is not installed" and then it gave the errors I added below.
operating system: server 2019
node version : v20.10.0 python version : Python 3.12.6

@Yusufkulcu The error in your screenshot here is a different error to the one in your initial post. The error you're getting on the virtual server here is related to there not being a prebuilt binary for isolated-vm for that server; which is basically the root cause of this issue:

https://github.com/jehna/humanify/issues/71

But solving that won't solve the issues you're having on your main system install.

This part might not matter (not 100%, just guessing):
npm warn cleanup   [
npm warn cleanup     'C:\\Users\\Administrator\\AppData\\Roaming\\npm\\node_modules\\humanifyjs\\node_modules',
npm warn cleanup     [Error: EPERM: operation not permitted, rmdir 'C:\Users\Administrator\AppData\Roaming\npm\node_modules\humanifyjs\node_modules\isolated-vm\src'] {
npm warn cleanup       errno: -4048,
npm warn cleanup       code: 'EPERM',
npm warn cleanup       syscall: 'rmdir',
npm warn cleanup       path: 'C:\\Users\\Administrator\\AppData\\Roaming\\npm\\node_modules\\humanifyjs\\node_modules\\isolated-vm\\src'
npm warn cleanup     }
npm warn cleanup   ],
npm warn cleanup   [
npm warn cleanup     'C:\\Users\\Administrator\\AppData\\Roaming\\npm\\node_modules\\humanifyjs\\node_modules\\node-llama-cpp',
npm warn cleanup     [Error: EPERM: operation not permitted, rmdir 'C:\Users\Administrator\AppData\Roaming\npm\node_modules\humanifyjs\node_modules\node-llama-cpp\llama\llama.cpp'] {
npm warn cleanup       errno: -4048,
npm warn cleanup       code: 'EPERM',
npm warn cleanup       syscall: 'rmdir',
npm warn cleanup       path: 'C:\\Users\\Administrator\\AppData\\Roaming\\npm\\node_modules\\humanifyjs\\node_modules\\node-llama-cpp\\llama\\llama.cpp'
npm warn cleanup     }
npm warn cleanup   ],
npm warn cleanup   [
npm warn cleanup     'C:\\Users\\Administrator\\AppData\\Roaming\\npm\\node_modules\\humanifyjs',
npm warn cleanup     [Error: EPERM: operation not permitted, rmdir 'C:\Users\Administrator\AppData\Roaming\npm\node_modules\humanifyjs'] {
npm warn cleanup       errno: -4048,
npm warn cleanup       code: 'EPERM',
npm warn cleanup       syscall: 'rmdir',
npm warn cleanup       path: 'C:\\Users\\Administrator\\AppData\\Roaming\\npm\\node_modules\\humanifyjs'
npm warn cleanup     }
npm warn cleanup   ]
npm warn cleanup ]

Some further ideas/google results based on Error: EPERM: operation not permitted, rmdir 'C:\Users\Administrator\AppData\Roaming\npm\node_modules\humanifyjs\node_modules\node-llama-cpp\llama\llama.cpp'

https://stackoverflow.com/questions/34600932/eperm-operation-not-permitted-on-windows-with-npm

Some suggestions involve running npm cache clean --force
Some suggest changing the npm install location prefix
Others suggest changing security permissions on folders
I don't know enough about node/npm on windows to say what the best choice/solution here is; but in any case, it sounds like it's not humanifyjs specific.

https://learn.microsoft.com/en-us/answers/questions/1466658/erorr-using-npm-package-manager-eperm-operation-no

One suggestion here includes:

Run command in CMD Window as an administrator trying to delete the folder.
Try again when disabling any other 3rdparty antivirus/security software.
Check file and folder permission:

https://github.com/npm/npm/issues/10826

One user here suggests npm cache clean
Another suggests disabling antivirus
Another suggests checking if another application is using the project folder (like an IDE/editor)

Some notes from upstream:

it would be helpful if you can check if<EMAIL_ADDRESS>exists.
Originally posted by @giladgd in https://github.com/withcatai/node-llama-cpp/discussions/353#discussioncomment-10853697

Actually, this may indeed be the permission issue I mentioned.
The attached error shows that node-llama-cpp is installed under the Administrator user, which should never be done, and is very prone to permission issues.
Originally posted by @giladgd in https://github.com/withcatai/node-llama-cpp/discussions/353#discussioncomment-10853713

Full comment:

I run some tests on the latest version (3.0.3), and it seems to work as expected on Windows.
I've tested it on both a Windows 10 machine and on a Windows 11 machine.
From the logs you attached, I think there's something wrong in the installation on the user machine, whether it's npm that hasn't installed the prebuilt binaries properly (maybe they're using some npm mirror that doesn't work as expected), maybe it's related to permissions on the machine itself (like running npm install in the folder from one user and trying to use it from another use that doesn't have proper access to the node_modules directory), and maybe it has something to do with some program on the machine the blocks the access to the .node file.
From the linked issue I can see in the logs that it attempted to fallback to building from source, and since CMake is not installed on the user's machine, it tried to call xpm to install CMake locally inside node-llama-cpp, but it failed with this error:
npm error ^[[?25l^[[?25h'xpm' is not recognized as an internal or external command,
npm error operable program or batch file.
npm error Failed to build llama.cpp with no GPU support. Error: SpawnError: Command npm exec --yes --<EMAIL_ADDRESS>install @xpack-dev-tools/cmake@latest --no-save exited with code 1

The ^[[?25l^[[?25h'xpm' part seems to indicate one of the following:

There's and issue with the installation of nodejs/npm on the user machine.

npm exec --yes is equivalent to npx -y, but npm exec --yes works better with other runtimes such as Bun, which is why I used it.

There's an issue with the escaping done by cross-spawn to run the npm exec --yes --<EMAIL_ADDRESS>command. I used cross-spawn because it solved many issues with process spawning on Windows, so I think this is less probable.

What I would suggest to try to fix this issue would be:

Uninstall all global npm modules, including npm, and reinstalling nodejs, since it seems like there's an issue with its installation.
Try to use Bun, since it seems they've fixed many Windows compatibility issues.
Install CMake manually, so node-llama-cpp can use it.

Before doing all of the above, it would be helpful if you can check if<EMAIL_ADDRESS>exists.
Originally posted by @giladgd in https://github.com/withcatai/node-llama-cpp/discussions/353#discussioncomment-10853697


Fixes to horizontal zoom & tests

Fixes the issue that zooming when already at maximum zoom level
started to move the time window.
To reproduce: Zoom in until at max zoom level. Trying to zoom further
will start moving the time window slightly to the left or right, depending
on the position of the mouse.
Also fixes some smaller inconsistencies in the tests.

But I think that the solution should be 100% implemented in SetMinMax(). For example I guess that holding ctrl + right click (for selecting an interval to zoom-into) is still moving the screen although the user can't zoom-in anymore.

To implement this in SetMinMax(), I'd need to pass in the reference timestamp that was used as "center of zooming". But this parameter is only needed when zooming with the mouse, and I didn't want to pollute the public SetMinMax() API (which will also be part of the TimelineInfoInterface later) with a confusing and often unneeded parameter. So I decided to rather implement this in ZoomTime because it already relates the zooming functionality to the mouse position.
As for ctrl + right click: I think the behavior makes more sense here, because it still centers the window around the selected interval even if Orbit won't zoom further.


fix MssqlDialect streaming not handling backpressure.

fixes #879.
fixes #971.
Now MSSQL driver handles backpressure properly using tedious's pause and resume methods.
Also aligns the dialect's types with tedious newly exported types.

Very helpful... thank you so much

Very nice, in my tests this works :+1:


[BUG]: Flickering transition from poster image to video

Version
6.6.0
What platforms are you having the problem on?
iOS, Android
System Version
ios 15
On what device are you experiencing the issue?
Real device, Simulator
Architecture
New architecture with interop layer
What happened?
Caused by https://github.com/TheWidlarzGroup/react-native-video/pull/3972
Reverting poster style to not include display:none fixes this
Reproduction Link
repository link
Reproduction
Just a video component with a poster.
Before the video plays there is a flicker.

According to https://github.com/TheWidlarzGroup/react-native-video/pull/3972#issue-2390717311

Fixed bug -> When the video wasn't fully loaded but its image was visible, both the video and the poster were simultaneously visible

Was this a bug or a feature? We were using this as a feature for vimeo videos where the poster is the first frame of the video. It was seemless before this fix. Now it's a poster then a frame of black then the video plays

Let us release next version, and I will double check this issue.

same in version 6.7.0 :(

any news on this ?


Scrolling programatically

New issue checklist

[x] I have reviewed the README and documentation
[x] I have searched existing issues and this is not a duplicate
[ ] I have attempted to reproduce the issue and include an example project.

General information

IGListKit version: 3.4.0
Xcode version: 10.2
Devices/Simulators affected: all

Debug information
Dear IG team,
I'm happy to say that all of our app is build on IGListkit. Starting from the Login-Screen up to the Checkout - All views are flexible. And based on this I'm hoping to get one of our main problems finally solved:

Having a starting scrolling section
Programatically scrolling to a section

Considering 1:
So we have this dialog where our users may select a time range in which they will receive their delivery. When the user re-opens this dialog to edit the selection we'd like to have the horizontal-CollectionView position itself so the previously selected time range is centered.
Having tried this is not solving the problem:

let adapter = ListAdapter(updater: ListAdapterUpdater(), viewController: nil)
adapter.collectionView = collectionView
adapter.dataSource = self
self.collectionView.scrollToItem(at: IndexPath(item: 0, section: selectedPosition), at: .left, animated: true)

Here we kinda know what the problem could be: When we're calling the collectionView to scroll the sections most probably "are not there yet". But what could be the solution? Some kind of callback indicating the complete loading of the section?
As mentioned in the beginning were building all are views with CollectionViews and IGListKit so what you see here is an embedded horizontal CollectionView inside a vertical one.

Considering 2: From time to time we want to focus certain sections: E.g. When the user selected a payment method and should now see the summary of his purchase. Unfortunately we were not able to have the collectionView scroll down after the user selected a payment method.
We tried following solution from another post

extension UICollectionView {
    func scrollToLast() {
        guard numberOfSections > 0 else {
            return
        }

        let lastSection = numberOfSections - 1

        guard numberOfItems(inSection: lastSection) > 0 else {
            return
        }

        let lastItemIndexPath = IndexPath(item: numberOfItems(inSection: lastSection) - 1,
                                          section: lastSection)
        scrollToItem(at: lastItemIndexPath, at: .bottom, animated: true)
    }
}

Also bear with me for my "noobish" question here. Since we got a bit desperate on this problem I decided to post my first ever ticket on github 😄

Is your collection view using a custom UICollectionViewFlowLayout? I had an issue when using an estimated size for the cells. Removed this and the issue went away. It's not ideal as it means you can't have dynamic heights for cells but it did solve the issue.

IGListAdapter->scrollToObject: supplementaryKinds: scrollDirection: scrollPosition:animated:

@Bruce-pac Thanks for the answer. Calling this method after adding all the models and waiting 0.5 seconds worked for us.
The problem that we have now is that the wrong starting position shows up and after 0.5 secs the scrolling is performed. Do you have an idea on how to have the scrolling position set from the very beginning?

I think we got it solved by just doing the following:
(didMoveToSuperView)
collectionView.alpha = 0
scrollToObject (after delay 0.1 secs)
collectionView.alpha = 1
You really can't tell the difference. It looks as if it's there from the beginning on


Lambda auth minor fixes

Description of changes

Use function category to create the lambda auth rather than creating it within api package.
Enhance function category to pass the defaultRuntime and template.
Add GraphQL Lambda Authorizer to the list of NodeJS templates.
Prompt user to edit the function created through amplify add and update api workflow.

Description of how you validated changes

yarn test
e2e test in local

Checklist

[x] PR description included
[x] yarn test passes
[x] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #8741 (28f539a) into master (8c73713) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #8741      +/-   ##
==========================================
- Coverage   56.88%   56.88%   -0.01%
==========================================
  Files         756      756
  Lines       42247    42252       +5
  Branches     8650     8656       +6
==========================================
  Hits        24033    24033
- Misses      17393    17397       +4
- Partials      821      822       +1

Impacted Files
Coverage Δ

...mation/service-walkthroughs/appSync-walkthrough.ts
14.62% <0.00%> (+0.15%)
:arrow_up:

...tion/src/provider-utils/awscloudformation/index.ts
13.15% <0.00%> (-0.12%)
:arrow_down:

...rmation/service-walkthroughs/lambda-walkthrough.ts
19.69% <0.00%> (-0.31%)
:arrow_down:

...ls/awscloudformation/utils/functionPluginLoader.ts
6.36% <0.00%> (-0.31%)
:arrow_down:

...vider-utils/awscloudformation/utils/layerParams.ts
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 8c73713...28f539a. Read the comment docs.


Enhancement of Data Point Interaction Capabilities for Improved Analytical Depth

Dear FL Chart Contributors,
I hope this message finds you well. I am reaching out to propose an enhancement that could significantly augment the analytical utility of the FL Chart library. Having utilised your library extensively, I've found it to be remarkably versatile and user-friendly. However, there is an opportunity to deepen the user interaction with individual data points across various chart types.
Issue Description:
Currently, the interaction with data points on charts such as LineChart and ScatterChart is somewhat limited. Users can tap on a point to perhaps see a tooltip, but the potential for interaction stops there. For analysts and data enthusiasts, the ability to further interrogate a data point could be invaluable. This could include functionalities such as drilling down into more detailed data, linking a point to another chart or dataset, or even custom actions defined by the developer.
Proposed Solution:
I suggest we enhance the data point interaction model to include:

A callback mechanism when a data point is long-pressed, allowing developers to define custom actions.
The ability to link data points to secondary datasets or charts, enabling a drill-down capability.
An expanded tooltip system that can display more detailed information, including metadata associated with data points.

Benefits:

This enhancement would empower users to perform more detailed data analysis directly within the charts.
It would add an interactive dimension to data presentation, making it more engaging and informative.
Developers would have the flexibility to create a more interactive and integrated data visualisation experience.

I believe this feature could be a substantial addition to the FL Chart library, aligning with the ethos of providing a highly customisable and feature-rich charting experience. I am keen to hear your thoughts on this proposal and would be delighted to contribute to the discussion and development process.
Thank you for considering this enhancement. Your dedication to the FL Chart project is greatly appreciated by the community.
Best regards,
yihong1120

Hi @yihong1120

A callback mechanism when a data point is long-pressed, allowing developers to define custom actions:
For the interactions, we already support customizations, you can override the touchCallback() function of LineTouchData receive the touch interactions and do whatever you want.
(Don't forget to disable handleBuiltInTouches property to disable the default behaviour)

It would add an interactive dimension to data presentation, making it more engaging and informative:
I didn't understand this one clearly, but I think you're looking for a way to open another chart when user taps on something.
So you can customize the interaction and do this at the moment.

An expanded tooltip system that can display more detailed information, including metadata associated with data points:
For this one, you can customize the showing tooltip and put some texts. We don't support customized widgets here, I agree that we can improve this part to support widgets inside the tooltip (follow this issue: #72)
Check the below sample (source code is here) to see how you can customize the showing test.

btw, I really appreciate your request


Add files via upload

The Pull Request resolves Issue #[Issue-Number]
Description:
A brief description about the addition or edits made.
Notes: Delete all the text including this!

The #[Issue-Number] should be replaced with the specific Issue being referenced.

add words and description


Update Deps

This addresses a number of vulnerabilities in dependencies. It doesn't fix everything, but does clear a significant number of issues.

Detected Secrets
:red_circle: Secrets Found
If you are seeing this message, it means that the secret scanning tool that Apollo uses to prevent secrets from entering our repositories has identified a secret in your branch. Information about what was detected and steps to move forward are below.
If the secret scanner detected a valid secret, please take immediate action to remove it from your branch. Apollo also recommends that you invalidate the secret in the system it grants access to. While there are additional steps to prepare the branch for merging, protecting the secret is the top priority.
If the scanner detected a value that is not actually secret or it detected a value that was a secret but has been invalidated, follow the steps in the "Resolution Process" section below to mark it as a false/benign positive. One common reason for benign positive detections is test values. For example, if you are committing a value (like a private key, JWT, etc.) that would usually be secret but is being used in a test case to validate functionality, a detection will be generated. This is safe to allowlist.
Values Detected

Signature
File
Commit
Start Line
Start Column
Link To Secret

generic-api-key
.out/sb-preview/runtime.js
ea27f9070569b3d4545a7aece3c1b25decba16e2
1
40100
Link

generic-api-key
.out/sb-preview/runtime.js
ea27f9070569b3d4545a7aece3c1b25decba16e2
1
57436
Link

generic-api-key
.out/sb-preview/runtime.js
ea27f9070569b3d4545a7aece3c1b25decba16e2
1
65442
Link

generic-api-key
.out/sb-manager/chunk-KCJCJECS.js
ea27f9070569b3d4545a7aece3c1b25decba16e2
4
45872
Link

generic-api-key
.out/sb-manager/chunk-KCJCJECS.js
ea27f9070569b3d4545a7aece3c1b25decba16e2
4
49319
Link

generic-api-key
.out/sb-manager/chunk-KCJCJECS.js
ea27f9070569b3d4545a7aece3c1b25decba16e2
4
71424
Link

generic-api-key
.out/sb-manager/chunk-KCJCJECS.js
ea27f9070569b3d4545a7aece3c1b25decba16e2
4
90650
Link

Resolution Process

[!NOTE]
Apollo does not use all of the native options provided by Gitleaks to perform allowlisting. We use Gitleaks' standard line comments but rely on a custom convention written in a .gitleaks.toml file at the root of each repository for allowlisting detections in Git history.

To resolve the issue, you will need to:

Prevent new detections of the "secret":

Add a comment containing gitleaks:allow to the line containing the detected value.
Skip this step if it's not feasible. For example, the detection is in file types like JSON or Markdown, you've completely removed the value, etc.

Configure the scanner to ignore the "secret" in git history.

Follow the instructions below for either "Allowlist by Commit Hash" or "Allowlist by File Path"
You will need to ensure that a .gitleaks.toml file exists at the root of this repository in your branch. If not, create one!

Allowlist by Commit Hash
This is the preferred option. Update the .gitleaks.toml file with the following contents:
[[ rules ]]
    id = "signature-from-table-above"
    [ rules.allowlist ]
        commits = [
            "full-commit-hash-1",
            "full-commit-hash-2"
        ]

If a [[rules]] block already exists for the signature involved in your detection, simply append your list of commits.
If a matching [[rules]] block is already present but has a paths attribute rather than commits, proceed to the next option.
This configuration tells the scanner to ignore the specified signature in the list of commits provided.

Allowlist by File Path
This is a backup option to allowlist specific detections. Add/update the .gitleaks.toml file with the following contents:
[[ rules ]]
    id = "signature-from-table-above"
    [ rules.allowlist ]
        paths = [
            '''path/to/detected/file1.json$''',
            '''path/to/other/detected/file.md$'''
        ]

This configuration tells the scanner to ignore any detections with the specified signature generated for the list of files.

Getting Help
The Apollo Security team has been notified and is available to assist in resolving this issue. Please tag us on this PR using  @apollographql/security if you need assistance!

How do I know I fixed this correctly?
Once you have resolved the issue completely, this message will disappear! If you're still seeing this message, there is more to do prior to merging.

Detected SAST Vulnerabilities
Output redirected to be in the build step output of 'Comment in PR' in your CircleCI build, as otherwise comment would be too long.


Annotations on non-dynamic nodes

Currently, it is only possible to add annotations on dynamic nodes because the annotations collection is an immutable view and the addAnnotation method is only available on AbstractClassifierInstance objects.

Oh, that is not great. I guess that DynamicNode should extend AbstractClassifierInstance

I plan to look into this tomorrow

Which nodes have you encountered that were not extending DynamicNode or AbstractClassifierInstance?

Or do you think that addAnnotation should go directly on Node?
So far Node is about making nodes readable, and not writable but perhaps that is inconvenient

Which nodes have you encountered that were not extending DynamicNode or AbstractClassifierInstance?

None, because I've used this in the context of Kolasu import/export which uses dynamic nodes.

Or do you think that addAnnotation should go directly on Node?
So far Node is about making nodes readable, and not writable but perhaps that is inconvenient

I don't know, because I miss the grand design picture. My gut feeling is that an annotation is something you may want to add to a node independently of the creator of the node. Also I see that Node being a ClassifierInstance has setPropertyValue and setReferenceValues methods that mutate it (but nothing for containments?). Maybe addAnnotation should go in ClassifierInstance?

Thank you Alessio, you raise good points.
I think we should indeed add this method to ClassifierInstance. If some Node is read-only it could always throw an exception in case this method is called

As LW-C# is open source now, you could have a look at the design there: We have IReadableNode as root of the inheritance hierarchy, then IWritableNode, and INode is essentially just an alias of IWritableNode.
Language entities extend e.g. ConceptBase, which only implements IReadableNode. All generated classes implement INode.
So, in a nutshell:

IReadableNode

ReadableNodeBase

ConceptBase

IKeyedBase

ClassifierBase

ConceptBase

IWritableNode

INode

NodeBase

MyGeneratedConceptClass


Banner doesn't stay there in section page

The banner stays there when on the homepage but when going into section pages the banner doesn't stay there.

This was an intentional design choice and I really like it this way


Breakpoint doesn't hit / shows up at wrong place

Hi,
NTVS version: 1.2.40329.01
Visual Studio version: 14.0.25123.00 Update 2 (Community 2015)
Node.js version: v6.1.0
Steps to Reproduce:

Create a new project using the template "Basic Node.js Express 4 Application".
Open index.js file in routes directory.
Set a breakpoint at line 6.
Press F5. Browse opens up, shows the page but the breakpoint is not hit.
Hit reload in browser, now the breakpoint is hit in app.js line 1.

Do I need to set some option so the breakpoint is hit at the desired location?
Regards,
Madhu.

Thanks for the report. Since you are Node 6.1, this look like another manifestation of #934 to me. Closing this issue in favor of that one.
We're still actively investigating the problem, but determine what has changed since Node 5.x regarding the Node debugging behavior has been difficult. It appears to be a timing issue of some sort right now.


Wrapper method in subproject results in error since version 4

Expected Behavior
When Gradle is invoked in the parent project, a subproject that has a wrapper method shouldn't cause a failure.

Current Behavior
When Gradle is invoked in the parent project, a subproject that has a wrapper method causes a failure:
$ ./gradlew tasks

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/amaloy/boog/g4/subproject/build.gradle' line: 7

* What went wrong:
A problem occurred evaluating project ':subproject'.
> Could not find method wrapper() for arguments [build_3hahijwjmgwyw035at2gjxwy3$_run_closure1@74204f25] on project ':subproject' of type org.gradle.api.Project.

Context
In this particular case, the subproject is a project that can be independently build and otherwise worked with, so it's useful for it to have its own wrapper (and having the wrapper method (previously in Gradle 3 it was a task) is desirable). The subproject is a git submodule in the parent project repository, which I bring up to show that, again, the subproject is a separate project/repository and can be worked with on its own.
I'm in the process of upgrading from Gradle 3 to 4.
I did come across this comment: https://github.com/gradle/gradle/issues/5042#issuecomment-384182328
But from my experience (see below) this feels like a regression.

Steps to Reproduce (for bugs)
Working example with Gradle 3:
$ cat build.gradle
task wrapper(type: Wrapper) {
    gradleVersion = '3.5.1'
}
$ cat subproject/build.gradle
task wrapper(type: Wrapper) {
    gradleVersion = '3.5.1'
}
$ cat settings.gradle
rootProject.name = 'g3'
include ':subproject'
$ ./gradlew tasks
:tasks

------------------------------------------------------------
All tasks runnable from root project
<...snip...>
BUILD SUCCESSFUL

Total time: 0.985 secs

Failing example with Gradle 4 (the wrapper section is modified as recommended by warnings):
$ cat build.gradle
wrapper {
    gradleVersion = '4.8.1'
}
$ cat subproject/build.gradle
wrapper {
    gradleVersion = '4.8.1'
}
$ cat settings.gradle
rootProject.name = 'g4'
include ':subproject'
$ ./gradlew tasks

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/amaloy/boog/g4/subproject/build.gradle' line: 1

* What went wrong:
A problem occurred evaluating project ':subproject'.
> Could not find method wrapper() for arguments [build_3hahijwjmgwyw035at2gjxwy3$_run_closure1@42a233d6] on project ':subproject' of type org.gradle.api.Project.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 0s

Your Environment
$ ./gradlew -v

------------------------------------------------------------
Gradle 4.8.1
------------------------------------------------------------

Build time:   2018-06-21 07:53:06 UTC
Revision:     0abdea078047b12df42e7750ccba34d69b516a22

Groovy:       2.4.12
Ant:          Apache Ant(TM) version 1.9.11 compiled on March 23 2018
JVM:          1.8.0_65 (Oracle Corporation 25.65-b01)
OS:           Mac OS X 10.12.6 x86_64

Since subprojects are not supposed to be run by themselves, they should not redefine the wrapper task. Please remove it from subproject/build.gradle.

I'm going to comment on this, since it's the newer of the two issues that I could find (the other being #5042 (comment)).
This really seems like a regression, to me. Subprojects which are also stand-alone projects is extremely common. I can think of 3 projects off the top of my head which I use, as well as a few by myself which use them this way.
However, until this can be (hopefully) addressed, I've come up with a workaround that should suffice for myself and @amaloy.
// Only supply the wrapper method if being called from the rootProject.
if (rootProject == project) {
    wrapper {
        distributionUrl = "https://services.gradle.org/distributions/gradle-$gradleVersion-all.zip"
    }
}

It's unfortunate that this is a necessary (and dirty) fix, but it'll get the job down, for now.

I agree with @FerusGrim where subprojects could be stand-alone - ex. building a jhipster based application with several microservice projects..
If you try to import all projects into eclipse, you'll encounter this error. It is frustrating to have to import each project one by one.

@big-guy Thanks! includeBuild works like a charm!


irust: 1.71.24 -> 1.71.29

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for irust is: Cross Platform Rust Repl
meta.homepage for irust is: https://github.com/sigmaSd/IRust
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.71.29 with grep in /nix/store/2j1l317ldaqhxp5b44nfgyqls6q0wnv0-irust-1.71.29
found 1.71.29 in filename of file in /nix/store/2j1l317ldaqhxp5b44nfgyqls6q0wnv0-irust-1.71.29

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

irust

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/e2661ee1682ebbc3e5857ad9d753ceaab3fa0c1b#irust

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2j1l317ldaqhxp5b44nfgyqls6q0wnv0-irust-1.71.29
ls -la /nix/store/2j1l317ldaqhxp5b44nfgyqls6q0wnv0-irust-1.71.29/bin

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

x86_64-linux

:white_check_mark: 1 package built:

irust

Maintainer pings
cc @lelgenio for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Working fine, it's a relatively simple bugfix update.


Security issue in synapse 0.16.1

Security issue in synapse 0.16.1

:(

Updated in 157babd, pending build

Build: https://hub.docker.com/r/ianweller/synapse/builds/bz3agloybddkyvjrvjwfhkh/


Question about Fig. 4 in the latest arxiv version.

Hi,
Thank you for sharing this wonderful work!
I have a question about Fig. 4 and corresponding presentation in main text, where the distributions of weights and biases seem unchanged after full fine-tuning, while SSF modulates the distributions. However, in most cases, full fine-tuning should be an upper bound compared to other parameter-efficient fine-tuning methods (except for some few-shot settings), which may indicates that we don't need to change the distribution of parameters. It seems to challenge the rationality of "the scale and shift parameters adjust the original weights and biases".
In other words, I am confused that whether we really require modulating the distribution of parameters to adapt the pre-trained model to downstream tasks for better performance? (Also, I note that SSF achieves better performance over full fine-tuning (93.99% vs. 93.82%), but this gap is slight.)
Looking forward to your reply, thanks in advance!

I see, thank you for quick reply.


Additional information about people

[ ] Is the person part of the core team? Add a badge for it.
[ ] Is the person a contributor? Add a badge for it.
[ ] Is the person an organiser? Add a badge for it.
[ ] Is the person a curator? Add a badge for it.

:+1: Like the idea.

Ideas for iconography on this one, @bascht ? :smile:


Add support for multiple containers to bash completion for docker pause

docker [container] pause used to only work on one container but now supports multple containers:
Usage:  docker container pause CONTAINER [CONTAINER...]

ping @thaJeztah this is a bugfix, would be nice to get it into 1.13.

LGTM


CREATE EXTERNAL TABLE

Was there supposed to be an ODBC-specific example for CREATE EXTERNAL TABLE?

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

ID: dad6b54f-7b8d-0d9b-0ece-815b8874f751
Version Independent ID: dee28cea-a153-0d80-b3f1-982aa4d16a87
Content: Access external data: ODBC generic types - PolyBase - SQL Server
Content Source: docs/relational-databases/polybase/polybase-configure-odbc-generic.md
Product: sql
Technology: polybase
GitHub Login: @MikeRayMSFT
Microsoft Alias: mikeray

@BeginTry -- Dave, thank you for your question.  I am looking into this issue.

@MikeRayMSFT -- Mike, apologies for my delay here.  Please look into this issue.

@BeginTry Hello. Mike is out of the office. I'm going to try to get someone else to look at this question in his absence. Thank you!

@BeginTry Hello There and thank you for this feedback. This article is designed to show you how to create all the dependent objects but not create the external table itself. Once you have the dependent objects correctly set you can create external tables just by referencing these standard objects. The CREATE EXTERNAL TABLE article is referenced at the bottom of the article. I will revisit the article to see if the language can be improved to avoid any confusion here. Thanks again for the feedback.

Thanks for the follow up.
For what it's worth, I was able to create an external table to an odbc-type external data source. There was some trial and error with the CREATE EXTERNAL TABLE statement...mostly with the LOCATION argument/parameter. I suppose it may vary a bit from one ODBC provider to another.
Cheers!

@jrowlandjones -- thank you for your explanation.
I am closing this issue now.  You are welcome to @ mention me for any followup.
We hope to hear from you again.


Reenable PrintAsObjC/extensions.swift

This test was disabled to work around a bug in the ObjC generics implementation in clang. That bug was corrected by https://reviews.llvm.org/D66696, so we should now be able to turn the Swift test back on.
Fixes rdar://problem/54414986.

@swift-ci please smoke test


fix: panel: fix panel animation while closing

SUMMARY:
fix: panel: fix panel animation while closing
GITHUB ISSUE (Open Source Contributors)
JIRA TASK (Eightfold Employees Only):
CHANGE TYPE:

[x] Bugfix Pull Request
[ ] Feature Pull Request

TEST COVERAGE:

[ ] Tests for this change already exist
[ ] I have added unittests for this change

TEST PLAN:

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@2ab62d0). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #414   +/-   ##
=======================================
  Coverage        ?   85.38%
=======================================
  Files           ?      658
  Lines           ?    13961
  Branches        ?     4759
=======================================
  Hits            ?    11920
  Misses          ?     1987
  Partials        ?       54

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


expert insights promo images

Description of the change:
Reason for the change:
Link to original source:

Closes #

Hello @Whatthefoxsays,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


camera intrinsics issues

Hi,
Why intrinsic is different for each image in the sample dataset. I assume one camera only have one intrinsic at a time.
1612099151.512330,0,1455.059570,1455.059570,956.688232,692.592407<PHONE_NUMBER>.545653,1,1459.042847,1459.042847,955.986572,693.707703<PHONE_NUMBER>.578977,2,1457.904785,1457.904785,956.351501,692.896729<PHONE_NUMBER>.612300,3,1457.904785,1457.904785,956.180359,693.358337<PHONE_NUMBER>.678947,4,1455.628662,1455.628662,956.031311,693.236450<PHONE_NUMBER>.712270,5,1456.766602,1456.766602,956.246460,693.202209<PHONE_NUMBER>.745594,6,1456.766602,1456.766602,956.072388,692.978027

I'm guessing that's due to autofocus.


Add alternate install location for MakeAppx.exe

In the latest Windows SDK (https://developer.microsoft.com/en-us/windows/downloads/windows-sdk/) MakeAppx.exe is installed to "C:\Program Files (x86)\Windows Kits\10\App Certification Kit\makeappx.exe"

Haven't done any additional checking, only: https://github.com/MicrosoftDocs/msix-docs/pull/299/commits/42d20eb568af9052143c75d29f84eb9bfc079f46

Alternatively, it may located in:

You're missing "be"

Thanks @johngagefaulkner . Added that in.


functiontrace: add functiontrace-server dependency

Description of changes
This is needed for functiontrace foo.py to work, as functiontrace-server must be in your path.
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2082

duplicate #222970

Hmm, I'll resolve that.  I suspect this approach should take precedence.
How do we generally feel about breaking changes (moving packages)?

What's mean? If you want to fix or change this package, you can do it on file which has been merged. No need to moving packages.

Functiontrace isn't really a python package, but is instead a version-agnostic tool that works with Python programs, so a top-level functiontrace makes more sense than python3XPackages.functiontrace.

I think there's a decent argument that this should still be a pythonPackage, so I updated this PR to work with that module.

Result of nixpkgs-review pr 224570 run on aarch64-darwin 1

4 packages built:

python310Packages.functiontrace
python310Packages.functiontrace.dist
python311Packages.functiontrace
python311Packages.functiontrace.dist