Improve lazy-loading of images within carousels.

The Image component will now create more than one IntersectionObserver if the Image is within a scrollable container that is not the body or html elements.
This means that images within a carousel that uses overflowX: auto would only render if the image is visible within the carousel and the carousel is visible within the body. Previously, the first few images in the carousel would render right away since only one IntersectionObserver could be created.

Jest will pass once #690 is merged.

This code now contains the contents of #690. I really should have built this PR on top of #690 rather than the other way around, but 🤷♂. I'll admin merge once tests pass since both PRs were approved.

@lavelle — Did cross-browser testing and found out that Edge 15 doesn't support the isIntersecting property. Changed the code to use entry.intersectionRatio > 0 instead.
Can you take another look?

Ok I've finished my second round of cross-browser testing.


Use UInt8 instead of Int8 for buffer types

Motivation:
The underlying BoringSSL BIO APIs used by NIOSSLCertificate,
NIOSSLPrivateKey take a raw byte buffer and a count,
and do not need the input buffers to be NUL-terminated. However, the API
currently takes an Array<Int8> (which is a typealias of Array<CChar> on
platforms where NIO is primarily developed). This suggests an incorrect
completion in Xcode (utf8CString) which includes a trailing NUL byte.
In fact, all of the NIOSSL unit tests make this mistake. The more common
use case of creating a these types from a Data, ByteBuffer, or
String.UTF8View is made more awkward as these are easy to convert to
[UInt8] but harder to convert to [CChar] without extending them with
an unnessary NUL byte.
Modifications:
Add new bytes: overloads to the convenience initializers and deprecate
the buffer: convenience initalizers. Use these new initializers in the
unit tests.
Result:
A more ergnomic way to correctly create these types from Data,
ByteBuffer, and String.UTF8View.

@swift-nio-bot add to whitelist


Add caching adapter

In a bigger deployment of Gollum, we've seen very slow performance from parts of Gollum. This adds the ability to pass a cacher that handles this. In our deployment, we use Memcached to share this state across workers.
@fw42 @camilo can you guys take a look at this too?

It's really a shame that this got closed and the devs just let it, this is a significant contribution that got hung up on some technicalities from my impression. Gollum-lib is awesome, but it's -slow-. It needs caching to be used in any production environment.

@Naatan, thanks for pointing out this PR. Although I think the Cache adapter implementation is nice and clean, and could potentially be used to cache more stuff, note that the most important potential performance increase has already been implemented in this commit, which implements caching for Page#formatted_data.
I think at the moment the highest performance increase for gollum-lib can be gained from rewriting the tag filter. See discussion here.

Good to hear the devs are giving performance the needed attention. Note that I tried the caching code in this PR and noticed a significant performance improvement on restructured text pages in particular. So it seems the commit you referenced does not manage to cache certain information properly. I'm still having a bit of trouble reading Ruby (so much magic going on) but shouldn't it be yielding @formatted_data?

@Naatan, that's interesting. I think @etienneCharignon  and @jonathanperret's caching of #formatted_data is working correct -- as the tests show, it should yield doc and return @formatted_data. If the cache implementation in this PR still improves performance, there must be some other part that's doing it, possibly the improvements to Page#find_sub_page?

Actually I ended up dumping the find_sub_page code as it was being troublesome in merging it into the latest version of gollum-lib and it seemed insignificant. I'll try and run some more tests once I have this code stabilized.

I think the issue is that gollum-lib stores the information on the class instance, and gollum does not preserve this instance for followup requests to the same page, it creates a new instance (assumption). So @formatted_data would be unset for each followup request.
Want me to create a new bug for this? We're getting fairly off-topic.

Ah, that seems right. You could open a separate issue yes. Perhaps the best thing would be to see if we can use some kind of pre-existing cache gem, so we don't have to handle things like releasing caches ourselves.

If anyone is interested in picking this up, that's cool with me, but I've since lost complete context. We just ended up putting the thing on a RAM-based filesystem. The problem is that there are tons of O(N) IO calls all over IIRC.

That's an interesting approach, how big were the performance gains from that?

Massive, I think we went from 2-3s, page loads with probably a few thousand pages, to ~100ms. It's a super dirty ops approach though.


feat: implement dsl for creating pact matchers

Codecov Report

Merging #2 (7760748) into main (f241fe3) will decrease coverage by 2.16%.
The diff coverage is 70.96%.

@@            Coverage Diff             @@
##             main       #2      +/-   ##
==========================================
- Coverage   82.97%   80.81%   -2.17%
==========================================
  Files           7        8       +1
  Lines         141      172      +31
==========================================
+ Hits          117      139      +22
- Misses         24       33       +9

Impacted Files
Coverage Δ

lib/src/errors.dart
0.00% <0.00%> (ø)

lib/src/interaction.dart
93.02% <ø> (ø)

lib/src/matchers.dart
78.57% <78.57%> (ø)

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 f241fe3...7760748. Read the comment docs.


If Trello gives the "slow down, too many messages..." api response, hubot crashes

I tried listing the boards available to my bot due to another issue 3 times in a row, which must have hit Trello's API limit.  It crashed hubot upon receiving that message 6 times.

Are you using the Slack adapter? I believe this is might be a Slack rate limiting error.


Where I put my bot token

I can’t find env file

Just create one ('.env') and fill with BOT_TOKEN=YOUR_TOKEN_HERE


Plugin crash with 100+ images

Describe the bug
This is a clear and concise description of what the bug is.
When trying to export a note that contains more than ~100/200 images the plugin will crash:

Thanks for the report, does this occur if they are all the same image or do they have to be unique?

Thanks for the report, does this occur if they are all the same image or do they have to be unique?

Hello. I did not tried with a single image repeated many times, my issue come from a note containing 200+ different unique images.
Let me know if I can give any help in replicating the bug.
Have a nice one.

Hello, with the new version it works perfectly. Awesome job, awesome plugin. Keep up the good work.


Subscription support

https://github.com/SignalK/specification/wiki/Subscription-based-Streaming

Wip at https://github.com/SignalK/signalk-servear-node/tree/subscriptions

Done quite some time ago, to an extent.


Staticman self-hosted on AWS S3 or Google Cloud Storage bucket

To self-host staticman (with or without Docker), would it be possible to do this on
AWS S3 storage bucket or Google cloud storage?

As I understand it, this user wants the easiest way to host a private instance. From what I've seen Heroku is by far the simplest method.


Logstash Exporter - ServiceMonitor - PrometheusRules - Kubernetes deployment

Describe the feature:
Why we don't have the capability to have an exporter from elastic with the official logstash helm chart.
Describe a specific use case for the feature:
All the metrics are centralized on Prometheus/Grafana stack.
Elastic allows to use metricbeats, but in my case i need to use prometheus operator for metrics scraping.
With this implementation we need an exporter, some other teams in the opensource community have this kind of sidecar
Retrieving the metrics directly from logstash replica.
Do you plane to have this kind of feature ??

I hope this functionality is also added but in the meantime I'm trying the following:
I have made the elastic chart a subchart of my own and added the missing service and service monitor manifests from the deprecated stable chart. This seems to be working to get the missing manifests but I can't seem to use the extraContainers helm value on the elastic chart to create the prometheus exporter container in the daemonset manifest. It just seems to ignore the text value, am wondering if this is a problem with using the tpl function on sub charts. Maybe this PR (https://github.com/elastic/helm-charts/pull/906) will help with my issue ? .
But if you know how to get the extraContainers value to work with subcharts that would be great!

Hey @alexandre-vaussant-axway, as mentioned in #895, #802 and #231, ServiceMonitor isn't a Kubernetes standard but is specific to Prometheus. We want to avoid managing integration with third party resources outside of Elastic products and Kubernetes standard resources in Elastic charts currently.


Needs smart error handling

sometimes a new property is added to an object in the API, and a PowerShell object will not be instantiated but will return an error. A method is needed to return user-friendly errors describing that problem and the list of properties returned from the API.
Needs

a Onelogin.Exception class for easily building new errors
exception message enum
can this all be handled centrally in Invoke-OneLoginRestMethod, rather than in each function?

sometimes a new property is added to an object in the API, and a PowerShell object will not be instantiated but will return an error. A method is needed to return user-friendly errors describing that problem and the list of properties returned from the API.
A new exception class may simplify this.

Other errors to handle

token has expired
no connection/token
api credential pair is not authorized to perform action

Added error handling for unknown API object properties in cfcd82e9ecb0bd917dae3dd8a29f5348e4bc29a5


Why does ig.user.accountDetails work for some users but not for others?

General Question
Form
Put an [x] if you meet the condition, else leave [ ].

[x] I've searched the Issues
[x] I've read the basic concepts
[x] I'm using the latest version

Question
I am trying to understand why the accountDetails method of the user repository works for some users but throws a 404 on work on others.
Here is an example of when it works.
code:
    const pk = await ig.user.getIdByUsername('<username-1>');
    const accountDetails = await ig.user.accountDetails(pk);
    console.log(accountDetails);

The resulting log in my console is as follows:
{ date_joined:<PHONE_NUMBER>,
    former_username_info: { has_former_usernames: true },
    primary_country_info: { is_visible: true, has_country: true, country_name: 'India' },
    shared_follower_accounts_info: { has_shared_follower_accounts: false },
    ads_info: { has_ads: false, ads_url: '' },
    status: 'ok' }

However when I change the username to another valid user with a public profile, the accountDetails method returns a 404 error. An example of this is as follows:
Code:
    const pk = await ig.user.getIdByUsername('<username-2>');
    const accountDetails = await ig.user.accountDetails(pk);
    console.log(accountDetails);

The following error is thrown:
  IgNotFoundError: GET /api/v1/users/<user-id-2>/account_details/ - 404 Not Found;
      at Request.handleResponseError (.../functions/node_modules/instagram-private-api/dist/core/request.js:98:20)
      at Request.send (.../functions/node_modules/instagram-private-api/dist/core/request.js:50:28)
      at <anonymous>

Does someone know what is different about these accounts that makes the api method work on the first account but not on the second? Both are business accounts and both are public.

Why did you close this issue, did you find a solution? Im facing the same issue as described above.

Im having the same issue. Anyone solved it so far? @pabloVoorvaart  @azimpradhan ?
For example im havin the following 2 public profiles:

conejo_de_humo
palma_santa

code
let profileInfo1;
let profileInfo2;
(async () => profileInfo1 = await ig.user.accountDetails(5367756700))(); // palma_santa =>
(async () => profileInfo2 = await ig.user.accountDetails(23302557191))(); // Conejo de Humo => 404 not found error

This function only works with accounts that once created advertisements.

This function only works with accounts that once created advertisements.


UNC paths are not supported

Thank you so much to share this to us.
This is a problem I'm facing now.
I want to store my shiny app  in a shared file system  where my friends can use directly without downloading it. The app work fine locally.
But when I double click it ,an error show up: UNC paths are not supported.  Defaulting to Windows directory
Best regards,
Thanks

Rather than using the UNC path directly, can your users map a drive letter to the network share?

Rather than using the UNC path directly, can your users map a drive letter to the network share?

sorry, I don't quite understand that, but it seems we have already have a driver letter for that ( R:// ),but this error shows  again.
What's wrong with that?

Is the app library fully installed in the network share?
It seems this error pops up when trying to install packages to a remote location.
https://support.rstudio.com/hc/en-us/articles/203775903-Fixing-startup-error-where-manipulate-and-rstudio-packages-will-not-install-with-networked-drives

Is the app library fully installed in the network share?
It seems this error pops up when trying to install packages to a remote location.
https://support.rstudio.com/hc/en-us/articles/203775903-Fixing-startup-error-where-manipulate-and-rstudio-packages-will-not-install-with-networked-drives

I have pre-install all the needed package. the I uploaded in the R:/ dir. the uploaded app I test locally, it works fine.
AND I finally  find a way to make it work.
If I click "my computer" > "R:/" > "dir i use" , the app work fine.
But if I click the spin of the whole dir  i use.  the error will pop up.
Don't know what's going on. Can you fix it?

If I click "my computer" > "R:/" > "dir i use" , the app work fine.
But if I click the spin of the whole dir i use. the error will pop up.

Sorry, I'm not understanding what you are doing different in these two cases. Can you clarify?

This question is solved by creating a short cut to the .bat file,when it works.
the short cut can work perfectly.


import taq should populate the taq namespace with the basic classes

Once this is working, notebooks and things should be updated in dlab-finance.

See #1 for history.

Edited raw_taw.py: removed "from" with 80e89a3ea30ccffe661537de72b70feea01bfcf1.
Added init.py, importing BytesSpec and TAQ2Chunks with 46b7c854c4f85c056ff98791156916a75f6548e1


Database Test fix

This fixes the DatabaseTest failing when using DBAL >= 2.8.0.
I honestly dont know what they changed, but changing back to DBAL 2.7.2 does not throw any errors.
What happens (and why it failed) is:

The primary key was dropped
The table-data is sended to Voyagers-UI and saved
The primary-key is back (This is where the problem starts)
assertFalse() fails

All I can say that its not Voyagers fault as there was no commit at the time the tests started failing.
The outcome/functionality of the can_change_index() test should still be the same.

This actually breaks the test.  The assert lines are checking for the state AFTER that line runs.  By moving the line after the asserts, you made it so it's only testing that previous state, which is before any change was made.


Vault for multiple instances

There are at least two instances of Vault.  One for OpenShift one for something else.  Set up the Vault helper to work with either.

There are only currently plans to support OneTeam's Vault.  Ticket exists for that.


Cleanup initial node tree implementation

Clean up the node tree documentation and adapt the structure to the common practices.
In addition, a results iterator is added to the ResultNode that iterates the results recursively.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (27c4a15) 100.00% compared to head (846b47e) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #19   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           16        16
  Lines         1278      1292   +14
  Branches       216       218    +2
=========================================
+ Hits          1278      1292   +14

Files
Coverage Δ

src/labone/nodetree/__init__.py
100.00% <100.00%> (ø)

src/labone/nodetree/entry_point.py
100.00% <100.00%> (ø)

src/labone/nodetree/enum.py
100.00% <100.00%> (ø)

src/labone/nodetree/errors.py
100.00% <100.00%> (ø)

src/labone/nodetree/helper.py
100.00% <ø> (ø)

src/labone/nodetree/node.py
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add Bwc test for Observability

Description

Add bwc specific Integration Test
Update gradle.build to run bwc tests from opensearch 1.1 to opensearch 1.2
Included snapshot of Notebooks 1.1 and Observability 1.2

Issues Resolved
#276
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #310 (8720daa) into main (da0cc10) will increase coverage by 3.05%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main     #310      +/-   ##
============================================
+ Coverage     71.86%   74.91%   +3.05%
  Complexity      269      269
============================================
  Files            81       37      -44
  Lines          2804     2029     -775
  Branches        334      231     -103
============================================
- Hits           2015     1520     -495
+ Misses          624      347     -277
+ Partials        165      162       -3

Flag
Coverage Δ

dashboards-observability
?

opensearch-observability
74.91% <ø> (ø)

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

Impacted Files
Coverage Δ

...rg/opensearch/observability/ObservabilityPlugin.kt
100.00% <ø> (ø)

...mon/helpers/ppl_docs/functions/full_text_search.ts

...ic/components/common/helpers/ppl_docs/overview.tsx

...components/common/helpers/ppl_docs/commands/top.ts

...omponents/common/helpers/ppl_docs/commands/sort.ts

...ty/public/components/visualizations/charts/bar.tsx

...nts/common/flyout_containers/flyout_containers.tsx

...onents/common/helpers/ppl_docs/functions/string.ts

...ic/components/custom_panels/custom_panel_table.tsx

...ents/common/helpers/ppl_docs/functions/datetime.ts

... and 35 more

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 da0cc10...8720daa. Read the comment docs.

DCO check is failing- also I see commits from a few months ago that don't look related to the BWC testing?

DCO check is failing- also I see commits from a few months ago that don't look related to the BWC testing?

Yeah those commits are not related to bwc and i'm not sure how it was included in this, but i removed those unnecessary files

DCO check is failing- also I see commits from a few months ago that don't look related to the BWC testing?

Yeah those commits are not related to bwc and i'm not sure how it was included in this, but i removed those unnecessary files

Got it - my guess is maybe some leftover local branch that contained those old commits was used at some point. Could you resolve the DCO failure?

DCO check is failing- also I see commits from a few months ago that don't look related to the BWC testing?

Yeah those commits are not related to bwc and i'm not sure how it was included in this, but i removed those unnecessary files

Got it - my guess is maybe some leftover local branch that contained those old commits was used at some point. Could you resolve the DCO failure?

Yeah i'm trying that currently


Master Assigned to Worker Nodes

It seems that in some cases, the VIP is given to worker nodes. Is there a way to make it so that it's only assigned to control-plane nodes?
[WARNING] Non-preferred master advertising: reasserting control of VIP with another gratuitous arp is displayed for multiple nodes, and the VIP is assigned to multiple nodes as well.
Some searching indicates this could be due to a time sync issue (I am not running an NTP server) so it's likely their clocks are not in-sync.

Yes, you can definitely do it with the Helm chart!
Edit the values.yaml here: https://github.com/immanuelfodor/kube-karp/blob/master/helm/values.yaml
nodeSelector:
    kubernetes.io/role: master

The tolerations in place allow the pods to run on master nodes, the node selection can restrict the pods only to the master nodes.
I only have clusters with master nodes, so I can't test this, please report back if it doesn't work.
Reference: https://stackoverflow.com/questions/60404630/kubernetes-daemonset-only-on-master-nodes

Thanks for responding swiftly!!
I know that's a possibility via nodeSelector but I was under the assumption that CARP must be active on all nodes, no?

That label doesn't seem to work anymore. I've used it once before but when I try installing the Helm chart with that label for nodeSelector, no pods are spawned.
Taking a look at the master labels, it seems it's been replaced with these:

It looks like their values are blank. I'm trying to get it functional

Yes, it seems my cluster also doesn't have that, this happens when blindly trusting online resources 😃
I have node-role.kubernetes.io/controlplane: "true" labels that I could use in my cluster.
Check what labels and values do you have with `kubectl describe no NODENAME -o yaml". Check master and worker notes as well, should you find a label that is only present on master nodes, you can use that. You can also label any node with anything then use that in the selector.

Thanks! I ended up just assigned an arbitrary label (color=red) and using that for nodeSelector. It seems this is somewhat of a common issue. I tried using the operator but that didn't work.
However, now my 3 master nodes are all assigned the VIP and in MASTER state...is that expected behavior?

Hmmm, that shouldn't happen, VIP management is not even related to k8s labels. Master nodes are all within the same subnet? Can master nodes communicate with the general multicast IP addresses to advertise themselves? See https://github.com/lorf/UCarp MULTICAST IP SELECTION section for more info. This issue seems to be related to network, the wrapped ucarp binary is probably not able to communicate to other pod's binaries, so they all think they are alone, so they all elect themselves as master and assign the VIP.

Yes I agree with you; likely a networking issue somehow. They are all in the same subnet. Thanks for linking and pointing that out. I will continue trying to solve this and get post back.

Is `tcpdump -n net <IP_ADDRESS>/24' a surefire way to tell if the host can communicate with the multicast IPs?
If so, no packets captured. Even when not using nodeSelector.

Honestly, I never needed to debug multicast packets

I had the same issue. Adding this to the end of values.yaml solves the issue for me.
affinity:
  nodeAffinity:
    requiredDuringSchedulingIgnoredDuringExecution:
      nodeSelectorTerms:
      - matchExpressions:
        - key: "node-role.kubernetes.io/master"
          operator: Exists


Update /leave endpoint for caller/callee.

@jiayliu @tkchin

Update with suggestions and added tests for those cases. PTAL.

Sorry, accidentally closed this by accidentally deleting the branch :S Thanks for reopening.

Ran lint tools, fixed many of the errors on the files I touched in this PR.

@jiayliu @tkchin did either if you want to look at this further? There are a lot of things going on so I wanted to be sure.

I'll take a look.
On Thu, Feb 5, 2015 at 1:21 PM, Chuck Hays<EMAIL_ADDRESS>wrote:

@jiayliu https://github.com/jiayliu @tkchin https://github.com/tkchin
did either if you want to look at this further? There are a lot of things
going on so I wanted to be sure.
—
Reply to this email directly or view it on GitHub
https://github.com/webrtc/apprtc/pull/28#issuecomment-73131376.

--
Jiayang Liu

lgtm! Really like the tests.

lgtm


UI is not updating when user email is verified in EmailPasswordActivity

each time when EmailPasswordActivity Start verify button is showing even wehn email is verified

@VikasKumarPatel thanks for the PR. This does seem like a bug but can you explain a little more why your fix is the right solution?

@VikasKumarPatel thanks for the PR. This does seem like a bug but can you explain a little more why your fix is the right solution?

@VikasKumarPatel LGTM thank you!

@VikasKumarPatel LGTM thank you!


Use OnceCell to cache Python operations

Summary
We were previously using RefCell to handle the interior mutability for the Python-operation caches.  This works fine, but has two problems:

RefCell<Py<PyAny>> is two pointers wide
we had to do heavier dynamic runtime checks for the borrow status on every access, including simple gets.

This commit moves the caching to instead use OnceCell.  The internal tracking for a OnceCell<T> is just whether an internal Option<T> is in the Some variant, and since Option<Py<PyAny>> will use the null-pointer optimisation for space, this means that OnceCell<Py<PyAny>> is only a single pointer wide.  Since it's not permissible to take out a mutable reference to the interior, there is also no dynamic runtime checking---just the null-pointer check that the cell is initialised---so access is faster as well.
We can still clear the cache if we hold a mutable reference to the OnceCell, and since every method that can invalidate the cache also necessarily changes Rust-space, they certainly require mutable references to the cell, making it safe.
There is a risk here, though, in OnceCell::get_or_init.  This function is not re-entrant; one cannot attempt the initialisation while another thread is initialising it.  Typically this is not an issue, since the type isn't Sync, however PyO3 allows types that are only Send and not Sync to be put in pyclasses, which Python can then share between threads.  This is usually safe due to the GIL mediating access to Python-space objects, so there are no data races.  However, if the initialiser passed to get_or_init yields control at any point to the Python interpreter (such as by calling a method on a Python object), this gives it a chance to block the thread and allow another Python thread to run.  The other thread could then attempt to enter the same cache initialiser, which is a violation of its contract.
PyO3's GILOnceCell can protect against this failure mode, but this is inconvenient to use for us, because it requires the GIL to be held to access the value at all, which is problematic during Clone operations. Instead, we make ourselves data-race safe by manually checking for initialisation, calcuting the cache value ourselves, and then calling set or get_or_init passing the already created object.  While the initialiser can still yield to the Python interpreter, the actual setting of the cell is now atomic in this sense, and thus safe.  The downside is that more than one thread might do the same initialisation work, but given how comparitively rare the use of Python threads is, it's better to prioritise memory use and single-Python-threaded access times than one-off cache population in multiple Python threads.

Details and comments
GILOnceCell would likely be better here, but it doesn't derive Clone, nor would that make sense, since it uses the GIL to mediate even getter access.  When we're able to move to PyO3 0.22 and disable the py-clone feature of it, we might be able to reorganise this a little bit to avoid needing to handle the GIL-atomic initialisation manually.
I measured this as saving 165MB (around 10%) in resident-set size from this benchmark:
from qiskit.circuit import QuantumCircuit

qc = QuantumCircuit(1_000)
for _ in range(3_000):
    for q in qc.qubits:
        qc.rz(0.0, q)
    for q in qc.qubits:
        qc.rx(0.0, q)
    for q in qc.qubits:
        qc.rz(0.0, q)
    for a, b in zip(qc.qubits[:-1], qc.qubits[1:]):
        qc.cx(a, b)

over its parent commit.  That's the same microbenchmark we used in #12730.  That should have a (small) impact on copy and circuit-build performance due to needing to move around less memory, and access times on the Python operation cache should be smaller too, though that shouldn't be in the critical path.
The biggest memory problem remaining in the CircuitData model (by far) is the parameter storage at the moment - in this particular benchmark, we spend something around 559MB storing the parameters of the 9,000,000 parametric gates, of which 15% is malloc overhead (on macOS, at least, but probably most Unix-likes and not dissimilar on Windows) and within the actual allocation, about 70% is just padding bytes.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

38 of 39 (97.44%)  changed or added relevant lines in 4 files are covered.
20 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-0.01%) to 89.739%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

crates/circuit/src/circuit_instruction.rs
10
11
90.91%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/expr.rs
1
94.02%

qiskit/transpiler/passes/synthesis/unitary_synthesis.py
2
88.39%

crates/qasm2/src/lex.rs
5
92.98%

crates/qasm2/src/parse.rs
6
97.61%

qiskit/synthesis/two_qubit/xx_decompose/decomposer.py
6
90.84%

Totals

Change from base Build<PHONE_NUMBER>9:
-0.01%

Covered Lines:
67403

Relevant Lines:
75110

💛  - Coveralls

I had previously approved this PR but it seems to be failing CI now. Any clue as to why @jakelishman ?

Ray: it's ok, it's just that #12943 merged in the meantime that had a logical but not syntactic conflict.  I've rebased this PR to account for the additional cache interaction added in that PR.


Cannot use a VHD file in an Azure storage account to create a managed disk with a different subscription

This answer is wrong:

Can I use a VHD file in an Azure storage account to create a managed disk with a different subscription?
Yes.

The Azure CLI gives this error when attempting this operation:

Message: The source blob https://labtainersblob.blob.core.windows.net/labtainersblobcontainer/labtainersbase.vhd does not belong to a storage account in subscription 0b2f9b91-93da-4d14-8279-813a24bb4f51.

Try it yourself (first create a labtainerResources group):
#!/bin/bash
if [ "$#" -ne 1 ]; then
    echo "create_disk.sh <disk name>"
    exit
fi
disk=$1
az disk create -g labtainerResources -n $disk --source https://labtainersblob.blob.core.windows.net/labtainersblobcontainer/labtainersbase.vhd --output none

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

ID: 7f329597-345e-2f0c-2db3-26b1277ef428
Version Independent ID: e184dc65-2103-8629-c857-a4873744a54e
Content: Frequently asked questions about disks - Azure Virtual Machines
Content Source: articles/virtual-machines/faq-for-disks.yml
Service: storage
Sub-service: disks
GitHub Login: @roygara
Microsoft Alias: rogarana

Thanks for the feedback! We are currently investigating and will update you shortly.

@roygara @v-hearya Can you please help confirm on the same? Thanks :)

Cannot use a VHD file in an Azure storage account to create a managed disk with a different subscription
This answer is wrong:
Can I use a VHD file in an Azure storage account to create a managed disk with a different subscription?
Yes.
The Azure CLI gives this error when attempting this operation:
Message: The source blob https://labtainersblob.blob.core.windows.net/labtainersblobcontainer/labtainersbase.vhd does not belong to a storage account in subscription 0b2f9b91-93da-4d14-8279-813a24bb4f51.

Hi, I honestly can no longer say.  I moved on by offering a community
image, and no longer recall the issues with the vhd.
--Mike
On Fri, Mar 10, 2023 at 4:12 PM rogara @.***> wrote:

@mfthomps https://github.com/mfthomps Sorry for the delayed response.
Just to make sure, this sample doesn't work for vhd files in different
subscriptions?
https://learn.microsoft.com/azure/virtual-machines/scripts/create-managed-disk-from-vhd
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/87994#issuecomment-1464701742,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFCIJW2BHC4QLKSM4VVF5TLW3O7OFANCNFSM5OJIAEWA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@mfthomps Thanks for letting us know. The sample should work so I'm going to go ahead and close this out.
Thanks again!
#please-close


TAVOSS-TR:Molecule

Version of the project
3.4.0
Tech Stack
DevOps [DO]
Project details
Molecule project is designed to aid in the development and testing of Ansible roles.
Molecule provides support for testing with multiple instances, operating systems and distributions, virtualization providers, test frameworks and testing scenarios.
Molecule encourages an approach that results in consistently developed roles that are well-written, easily understood and maintained.
Languages used
GO
Domain
No response
Industry
All
Open Source Project type
Community led
Repo URL
https://github.com/ansible-community/molecule
Webpage
https://molecule.readthedocs.io/en/latest/
License
MIT
Other license
No response
Reason , why we must track this project.
No response

Closing this issue request as it is duplicate


Infinite Recursion limit installing neovim

Describe the bug
running home-manager switch provides the following error with a minimal home.nix
unpacking channels...
error: while evaluating the attribute 'buildCommand' of the derivation 'home-manager-generation' at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:197:11:
while evaluating the attribute 'text' of the derivation 'activation-script' at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:197:11:
while evaluating 'mkCmd' at /Users/ronan/.nix-defexpr/channels/home-manager/modules/home-environment.nix:502:17, called from undefined position:
while evaluating the attribute 'data' at /Users/ronan/.nix-defexpr/channels/home-manager/modules/lib/dag.nix:91:37:
while evaluating the attribute 'data' at /Users/ronan/.nix-defexpr/channels/home-manager/modules/lib/dag.nix:85:9:
while evaluating the attribute 'data' at undefined position:
while evaluating 'g' at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/attrsets.nix:294:19, called from undefined position:
while evaluating anonymous function at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/modules.nix:139:72, called from /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/attrsets.nix:297:20:
while evaluating the attribute 'value' at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/modules.nix:523:9:
while evaluating the option `home.activation.copyFonts.data':
while evaluating the attribute 'mergedValue' at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/modules.nix:555:5:
while evaluating the attribute 'values' at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/modules.nix:549:9:
while evaluating the attribute 'values' at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/modules.nix:648:7:
while evaluating anonymous function at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/modules.nix:535:28, called from /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/modules.nix:535:17:
while evaluating definitions from `/Users/ronan/.nix-defexpr/channels/home-manager/modules/targets/darwin/fonts.nix':
while evaluating 'dischargeProperties' at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/modules.nix:607:25, called from /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/modules.nix:536:137:
while evaluating the attribute 'value' at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/modules.nix:390:44:
while evaluating the attribute 'passAsFile' of the derivation 'home-manager-fonts' at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:197:11:
while evaluating the attribute 'passAsFile' at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/pkgs/build-support/buildenv/default.nix:77:5:
while evaluating the attribute 'meta.outputsToInstall' at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:384:19:
while evaluating the attribute 'meta' at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/pkgs/applications/editors/neovim/wrapper.nix:111:5:
while evaluating the attribute 'package' at undefined position:
while evaluating 'g' at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/attrsets.nix:294:19, called from undefined position:
while evaluating anonymous function at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/modules.nix:139:72, called from /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/attrsets.nix:297:20:
while evaluating the attribute 'value' at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/modules.nix:523:9:
while evaluating the option `programs.neovim.package':
while evaluating the attribute 'mergedValue' at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/modules.nix:555:5:
while evaluating the attribute 'values' at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/modules.nix:549:9:
while evaluating anonymous function at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/modules.nix:545:19, called from /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/modules.nix:545:14:
while evaluating the attribute 'value._type' at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/modules.nix:646:73:
while evaluating the attribute 'value.content' at /nix/store/a0i53yvm44v4avy3n8hmbzlb672vr526-nixpkgs-21.05pre283745.93184413f21/nixpkgs/lib/modules.nix:706:14:
while evaluating the attribute 'default' at /Users/ronan/.nix-defexpr/channels/home-manager/modules/programs/neovim.nix:157:9:
while evaluating the attribute 'neovim-unwrapped' at /nix/store/syra4zq6zmc99fczzl778yw0rvk3w7ac-source/flake.nix:15:9:
while evaluating the attribute 'packages.x86_64-darwin.neovim' at /nix/store/l2nixghz5q3p8chjskqmwwfsz0p2krif-source/contrib/flake.nix:98:18:
while evaluating the attribute 'neovim-unwrapped.overrideAttrs' at /nix/store/syra4zq6zmc99fczzl778yw0rvk3w7ac-source/flake.nix:15:9:
while evaluating the attribute 'packages.x86_64-darwin.neovim' at /nix/store/l2nixghz5q3p8chjskqmwwfsz0p2krif-source/contrib/flake.nix:98:18:
infinite recursion encountered, at /nix/store/l2nixghz5q3p8chjskqmwwfsz0p2krif-source/contrib/flake.nix:98:18

There are 98 unread and relevant news items.
Read them by running the command 'home-manager news'.

Additional context
entire home.nix
{ Config, pkgs, ... }:

{
  programs.home-manager.enable = true;
  home.username = "ronan";
  home.homeDirectory = "/Users/ronan";
  programs.neovim = {
    enable = true;
  };
}

Metadata
 - system: `"x86_64-darwin"`
 - host os: `Darwin 20.3.0, macOS 10.16`
 - multi-user?: `no`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.3.7`
 - channels(ronan): `"home-manager, nixpkgs-21.05pre283745.93184413f21"`
 - nixpkgs: `/Users/ronan/.nix-defexpr/channels/nixpkgs

You should open an issue on the Home Manager tracker: https://github.com/nix-community/home-manager/issues
I think @mjlbach might be able to provide more help?

You should file an issue on the neovim nightly overlau. Where are you adding the overlay? I recently changed it to wrap the neovim flake in contrib which may be causing issues for some (it works fine on my system fwiw)

You should file an issue on the neovim nightly overlay. Where are you adding the overlay? I recently changed it to wrap the neovim flake in contrib which may be causing issues for some (it works fine on my system fwiw)

Ah I was using the an earlier version of your repo which was set up as follows in overlays/
import (builtins.fetchTarball {
  url = https://github.com/mjlbach/neovim-nightly-overlay/archive/master.tar.gz;
 })

Using the recommended code in home.nix makes it build. Thanks


We need to profile the ecc measurement code

Would be good to understand which part of the code is slowest, etc.

@md-arif-shaikh: I think this is probably a high priority item now, as we get ready to review gw_ecc. We need to understand:

How fast is the gw_ecc evaluation time for a single waveform for a 20 orbit signal and a 100 orbit signal.
Which part of the code is dominating the cost? Can that be improved with some optimization?
Should we only compute ecc using a small segment of the signal? What is the error introduced by this?

@vijayvarma392 sure I check this out. I will work on it after #215 is merged.


Change log policy to require PEM public keys

PEM is easier and more commonly used than DER.
https://groups.google.com/a/chromium.org/d/topic/ct-policy/M9Vchxs9gvY/discussion

Following discussion, counter-arguments were made about how DER was the better format. It's more specific (PEM may contain BER rather than DER), straightforward to manipulate with tools (base64 on Linux/Mac, certutil on Windows) and is the format consumed by at least two CT monitoring systems.


[Feat] : Add Membership page

@sunny0625
we can add offers/membership.html for footer Exclusive Offers page

@sunny0625
please assign me


ParAff applicative should abort on uncaught exception

Fixes #134

@natefaubion Thanks, will review this today!

I've changed the test to use never with a timeout guard around it.


You must reload the CAM-UI to force pv discovery at lab 6 - section 6.3

During some manual lab testing I faced a simple but annoying bug in the product, it can generate confusion to the lab participants.
If you come from the lab 5 (mssql migration) straightforward to the lab 6 and you don't reload the CAM-UI, the next migration plan will fail trying to discover the project's PVCs, it will only display the previous namespace PVCs (lab5) regardless of the current ns selecction.
I suggest to put a strongger note in the lab to avoid confusion, I will send a PR as soon as i can.

Stale

Stale


Error when running server.js on localhost:3000 "Cannot GET /"

When I try running node server.js from the Terminal in the folder the extension is unzipped to, I get the following error:

Transcribed messages:
Error. Make sure you're running the server by following the
instructions on https://github.com/gragland/chatgpt-chrome-
extension. Also make sure you don't have an adblocker preventing
requests to localhost:3000.

Cannot GET /

same issue. Have you found any solution? @oakif

Not yet unfortunately, hoping someone will have a solution

same issue here

same error: Error. Make sure you're running the server by following the instructions on https://github.com/gragland/chatgpt-chrome-extension. Also make sure you don't have an adblocker preventing requests to localhost:3000.   also getting this when running - chatgpt-chrome-extension-main % node server.js
/Users/milevin/Downloads/ChatGPT/chatgpt-chrome-extension-main/node_modules/dotenv-safe/index.js:31
throw new MissingEnvVarsError(allowEmptyValues, options.path || '.env', example, missing, dotenvResult.error);
^
MissingEnvVarsError: The following variables were defined in .env.example but are not present in the environment:
OPENAI_API_KEY
Make sure to add them to .env or directly to the environment.
If you expect any of these variables to be empty, you can use the allowEmptyValues option:
require('dotenv-safe').config({
allowEmptyValues: true
});
at Object.config (/Users/milevin/Downloads/ChatGPT/chatgpt-chrome-extension-main/node_modules/dotenv-safe/index.js:31:19)
at file:///Users/milevin/Downloads/ChatGPT/chatgpt-chrome-extension-main/server.js:2:8
at ModuleJob.run (node:internal/modules/esm/module_job:194:25) {
missing: [ 'OPENAI_API_KEY' ],
sample: '.env.example',
example: '.env.example'

How did you get past the current issue with the localhost? other people also have that issue.
As for your issue, npm install chatgpt should fix. But i still want to know how to fix the server.

В мене така ж проблема. Як local host:3000 як її подолати?


hubble: Change uint64 -> uint32 in getters interfaces

As identity and endpoint ID are considered to be uint32 after #11161 has been merge, this PR changes their type in getters interfaces accordingly and adjusts them to be uint32 as well. Includes related changes in parsers, daemon as well as tests.
Fixes: #11241
Signed-off-by: Matej Gera<EMAIL_ADDRESS>hubble: Change uint64 -> uint32 in getters interfaces

Coverage increased (+0.03%) to 44.643% when pulling 9b657b2637bd8be11382544a547221b3c70e6633 on matej-g:update-uint-getters into 97f8299d6c1a0da4a3f23c296f1e719c72e94c35 on cilium:master.

test-me-please


bump tensorflow to 2.4.1

bump tensorflow to 2.4.1
update dependencies in pre-commit config

Codecov Report

Merging #72 (dd4b79c) into dev (3c833cf) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev      #72   +/-   ##
=======================================
  Coverage   47.65%   47.65%
=======================================
  Files          36       36
  Lines        4707     4707
=======================================
  Hits         2243     2243
  Misses       2464     2464

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 3c833cf...dd4b79c. Read the comment docs.


[Enhancement] Support auto_refresh_partitions_limit for periodic refresh mv task

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[x] 2.5
[ ] 2.4
[ ] 2.3

[FE PR Coverage Check]
:heart_eyes: pass : 46 / 55 (83.64%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/scheduler/MvTaskRunContext.java
1
2
50.00%
[95]

:large_blue_circle:
com/starrocks/server/LocalMetastore.java
8
13
61.54%
[1510, 1511, 3034, 3978, 3979]

:large_blue_circle:
com/starrocks/scheduler/TaskRunContext.java
2
3
66.67%
[70]

:large_blue_circle:
com/starrocks/scheduler/TaskRun.java
3
4
75.00%
[107]

:large_blue_circle:
com/starrocks/sql/common/SyncPartitionUtils.java
17
18
94.44%
[393]

:large_blue_circle:
com/starrocks/scheduler/PartitionBasedMaterializedViewRefreshProcessor.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/TaskRunBuilder.java
5
5
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/TaskManager.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/scheduler/ExecuteOption.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/transaction/PublishVersionDaemon.java
2
2
100.00%
[]

run starrocks_admit_test

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5


Feature/170 verify credential using external context

Tasks

[x]  Modified the fetchVeridaUri() to use  Client class to open external context

[x]  Modified share-credential test cases

@cmcWebCode40  Tests are failing for me. Just for verify-credentials

@pranavburnwal, sorry about these errors,
I just pulled now and noticed that my changes were not up to date , i have just updated the branch now

@pranavburnwal, sorry about these errors,
I just pulled now and noticed that my changes were not up to date , i have just updated the branch now

@cmcWebCode40  Still not working. Please let me know if its just my side.

@pranavburnwal, sorry about these errors,
I just pulled now and noticed that my changes were not up to date , i have just updated the branch now

@cmcWebCode40  Still not working. Please let me know if its just my side.

Edit: The last comment was not posted earlier and saved in drafts.
After a call with @cmcWebCode40  It may have been there been some problem in my local setup. need to redo the installation and see what's up.

Client-ts tests amount to 2 errors. I think these are not related to the current updated code.

@nick-verida  @tahpot  Can confirm if these errors are not related to this PR?

Thanks @cmcWebCode40 -- This is all good.

@taphot,
But in the share-credential.test.ts file the getClientContext()  from the vc utils.ts file was imported to open an openExternalContext()  using the Client class .

@cmcWebCode40
Yes, you can just do:
import { Utils } from '../src/utils';

https://github.com/verida/verida-js/blob/379653623ce9f5b820ce41c48169770fb7a88472/packages/verifiable-credentials/test/share-credentials.test.ts#L4

@tahpot,
I have tested reading a VC using the package (yarn link) works as expected.
one more thing I noticed after I ran yarn build was the folder structure in the dist folder.
this is an example of the output
|-dist
    |-did-resolver
    |-verifiable-credentials

This affected how the Classes were imported  like this
 import { Credentials } from '@verida/verifiable-credentials/dist/verifiable-credentials/src/';

I have been investigating the causes of this, but haven't figured it out yet.
can you see if the dist output has the same folder structure on your end?

@tahpot, this PR is ready to be merged now


[Feature]: NVM automatic version change based on .nvmrc file Using JS Script Available to use

Description of the new feature / enhancement
I have created this script and it is for user convince to go to check script
Automatic Node.js Version Checker Script
This JavaScript script automates the process of checking and managing Node.js versions based on specific conditions:

Check Current Node.js Version:

The script begins by checking the currently installed Node.js version on your system.

Comparison with Required Version from .nvmrc File:

If the currently installed Node.js version matches the required version, the script logs a success message and terminates.

Using Node Version from .nvmrc File:

If the installed Node.js version doesn't match the required version, the script looks for a Node.js version specified in a .nvmrc file in your project directory.
If an .nvmrc file is found and contains a valid Node.js version, the script switches to and uses that version.

Installing Missing Node.js Version:

If there's no .nvmrc file or the specified version is not installed, the script prompts the user with a confirmation message.
If the user chooses to install the required version, the script proceeds to install it using a nvm install versioncommand
After installation, the script switche and uses the newly installed version.

Terminating the Script:

If the user chooses not to install the required version, the script gracefully terminates.

This script provides an automated and user-friendly way to ensure that your Node.js environment is set to the required version for your project.
Usage
the script is available  at https://github.com/proCoderSid/nvm-chk.git
You can use this file in package.json file as follow or as you feel comfortable to use
{
    "scripts": {
        "prestart": "node nvm-chk.js",
        "start": "Your start command"
    }
}

I have tested this script in node v4.9.11 to latest,
It works fine and if not working in any specific version then let me know I will update the script
Prerequisites as follow

Must have nvm installed on your machine
Current in use version of node need to be grater then v4.9.11

Scenario when this would be used?

Can be use before starting your local environment
Can be use to switch version automatically

Supporting information
const childProcess = require("child_process");
const fs = require("fs");
const readline = require("readline");
const execSync = childProcess.execSync;

// Read .nvmrc file
const nvmrcPath = ".nvmrc"; // Replace with your .nvmrc file path

const main = () => {
  try {
    // Read the content of the .nvmrc file
    const nvmrcVersion = fs.readFileSync(nvmrcPath, "utf-8").trim();

    // Get the current version of Node.js installed on the system
    const currentVersion = execSync("nvm current", { encoding: "utf-8" }).trim();

    if (currentVersion !== nvmrcVersion) {
      console.log("Current Node.js version:", currentVersion);
      console.log("Trying to use .nvmrc file version:", nvmrcVersion);

      try {
        nvmUseVersion(nvmrcVersion);
      } catch (err) {
        console.error("Error using Node.js version from .nvmrc:", err);
        console.log(`Please manually run 'nvm use ${nvmrcVersion}' to switch to the desired version.`);
      }
    } else {
      console.log("Node.js versions match:", currentVersion);
    }
  } catch (err) {
    console.error("Error reading .nvmrc file:", err);
  }
};

const requestToInstallNewVersion = (nvmrcVersion) => {
  // Prompt the user for installation confirmation
  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
  });

  rl.question("Do you want to install this version? (y/n): ", (answer) => {
    rl.close();
    if (answer.toLowerCase() === "y") {
      try {
        // Install the desired version using `nvm install`
        const installOutput = execSync(`nvm install ${nvmrcVersion}`, { encoding: "utf-8" }).trim();
        console.log(installOutput);
        nvmUseVersion(nvmrcVersion);
      } catch (err) {
        console.error("Error installing Node.js:", err);
      }
    }
  });
};

const checkVersionAfterUpdate = (nvmrcVersion) => {
  const updatedVersion = execSync("nvm current", { encoding: "utf-8" }).trim();
  if (updatedVersion !== nvmrcVersion) {
    console.log("Node.js version did not switch successfully. Please run the nvm use command manually.");
  } else {
    console.log("Updated Node.js version:", updatedVersion);
  }
};

const nvmUseVersion = (nvmrcVersion) => {
  // Attempt to switch to the desired Node.js version using `nvm use`
  const useOutput = execSync(`nvm use ${nvmrcVersion}`, { encoding: "utf-8" }).trim();

  if (useOutput.includes("is not installed.")) {
    // If the desired version is not installed, check available versions
    const versions = execSync("nvm ls", { encoding: "utf-8" });

    if (!versions.includes(nvmrcVersion)) {
      console.log(`Node.js version ${nvmrcVersion} is not installed.`);

      requestToInstallNewVersion(nvmrcVersion);
    }
  } else {
    checkVersionAfterUpdate(nvmrcVersion);
  }
};

main();

Since this is a feature I'm not implementing in NVM4W, I'm closing this. However; I'm going to link to this from the wiki for people who want this functionality.

This now linked in the common issues wiki page.

Just for those trying to use this script, it doesn't work with 1.1.12. However, it does work with 1.1.11. See https://github.com/coreybutler/nvm-windows/issues/1068

In addition I had to tweak two lines because when comparing values it would fail since some versions have leading "v" before version i.e. 'v18.0.0' === '18.0.0' would fail, though technically they are the same version.
currentVersion = currentVersion.startsWith( 'v' ) ? currentVersion.slice( 1 ) : currentVersion;


[Automated] Merge release into main

Automated Pull Request

@ProKil @yangalan123 I tried to fix the test errors by switching models, but somehow the tests did not read the latest files. Any ideas on this?


Treat warnings as errors

For all F# projects:

Raise to warning level 5
Enable unused value warning
Treat warnings as errors

It's a bit strict, but it will make maintenance easier in the long term.

Great.


Crash on launch

Crash Log:
https://pastebin.com/eHE4CU2n
Only happens when Aqua Acrobatics is installed

It looks like you have TickCentral installed. Please apply this workaround as mentioned near the bottom of the mod page; that should solve your issue. :slightly_smiling_face: However, you will unfortunately not be able to use bubble columns.


Fix display of method name when using async

If the $log is called within a method that is defined as async, the output will display  _callee$ instead of the actual method name.
Example:
async myFn() {
    this.$log.debug('testing');
}

myFn();

Output:
debug |  _callee$ | testing
Expected Output:
debug | myFn | testing

Hi @ejwaibel,
Thanks for reporting this. Unfortunately this cannot be fixed ( to my knowledge ).  Async await code :
function resolveAfter2Seconds() {
  return new Promise(resolve => {
    setTimeout(() => {
      resolve('resolved');
    }, 2000);
  });
}

async function asyncCall() {
  console.log('calling');
  var result = await resolveAfter2Seconds();
  console.log(result);
  // expected output: "resolved"
}

Transpiles to ( ES5 )  @ https://babeljs.io/repl/  :
var asyncCall = function () {
  var _ref = _asyncToGenerator( /*#__PURE__*/regeneratorRuntime.mark(function _callee() {
    var result;
    return regeneratorRuntime.wrap(function _callee$(_context) {
      while (1) {
        switch (_context.prev = _context.next) {
          case 0:
            console.log('calling');
            _context.next = 3;
            return resolveAfter2Seconds();

          case 3:
            result = _context.sent;

            console.log(result);
            // expected output: "resolved"

          case 5:
          case 'end':
            return _context.stop();
        }
      }
    }, _callee, this);
  }));

  return function asyncCall() {
    return _ref.apply(this, arguments);
  };
}();

This library relies on the new Error().stack property to determine the parent function name.  Unfortunately the transpiling causes the function to be wrapped in a function called _callee$, which is logged as the parent function.
I do not see a solution for this problem at this point in time. Feel free to propose something / or create a pull request.


Don't use Bind() to register event listeners

After writing some sample application with Zenject, I found it rather confusing that Container.Bind() seems to handle two different concerns.
For example, the following code reads like "bind a contract type IBar to a concrete type Bar, so that every subsequent request for IBar should be resolved to a single instance of Bar.":
Container.Bind<IBar>().To<Bar>().AsSingle();

But when it comes to binding event listeners, like ITickable, or IInitializable, semantic of the same method changes significantly, which I believe could cause some confusion.
For instance, the following example cannot be read the same way as the above example, even though the syntax is the same, because in this case, the intention is not to bind ITickable contract type to a single instance of Foo (there can be multiple objects in the container which implements ITickable), but to simply register itself as an event listener:
Container.Bind<ITickable>().To<Foo>().AsSingle();

And from the cheatsheet, the following example is supposed to register a single instance of Foo, and register the same object to listen for initialize and dispose callback:
Container.Bind<Foo>().AsSingle();
Container.Bind<IInitializable>().To<Foo>().AsSingle();
Container.Bind<IDisposable>().To<Foo>().AsSingle();

However, in most other DI containers(i.e. Spring Framework), an equivalent code would register three different singletons, because normally they manage bindings based on each distinct contract types, not actual implementation types like Zenject apparently does.
It seems that the limitation came from the fact that we need to manually declare what event handling interfaces we like to register. But is there any reason why this cannot be done automatically?
We have determinate number of such event listeners, so wouldn't it be possible for the container to check if the newly created object implements any of them, and register it automatically if it does?
I suppose it'd also be very helpful, in such cases user objects have a deep class hierarchy, because it'd be very easy to forget to declare IInitializable, for instance, if it was implemented by an ancestor class buried deep down in the class hierarchy.

I don't view these two lines as being fundamentally different actually:
Container.Bind<IBar>().To<Bar>().AsSingle();
Container.Bind<ITickable>().To<Foo>().AsSingle();

They are both treated the exact same by Zenject.
It sounds like some of the confusion lies in the way that Zenject handles multiple bindings with the same contract type.
So given this binding:
Container.Bind<IBar>().To<Bar>().AsSingle();

It will only match parameters of type IBar.  However, given these bindings
Container.Bind<IBar>().To<Bar>().AsSingle();
Container.Bind<IBar>().To<Bar2>().AsSingle();

It will only match parameters of type List.
This is exactly how ITickable works.  There is a TickableManager that is bound inside every 'context' (eg. SceneContext, ProjectContext, GameObjectContext), which simply has a constructor parameter of type List<ITickable>.
Also, in terms of having multiple bindings to the same concrete type: Yes, a 'singleton' in Zenject is a singleton in the context of the DiContainer.  I haven't used spring but it sounds like in that case it is a 'singleton' in the context of the given binding?  (which sounds like Zenject's concept of AsCached)
I suppose we could just automatically add every newly created instance that implemented ITickable to TickableManager.  But there are many drawbacks and risks to doing that (including the fact that it would break all existing code which is enough reason not to do it).
One thing that occurs to me is, why can't you just use BindInterfacesAndSelfTo?  Doesn't that provide essentially the same result where you don't have to remember to bind ITickable, etc.?

It turns out that I was confused about the contract about how multiple binding method calls for the same contract type are handled by Zenject, as you pointed out.
The reason I feel a bit hesitant about using BindInterfacesAndSelfTo was that I prefer to see my setup class as a self explanatory documentation for the whole system, explaining what contract types are there and which concrete classes are bound to them, and etc.
With BindInterfacesAndSelfTo, some of such information could be hidden, and potentially generate a lot of unintentional bindings (probably because I tend to overuse interfaces).
But as long as I was mistaken about the binding behavior, I suppose it's not a very important point.
I still believe callbacks, or system bindings better be handled differently from business bindings. And I think it wouldn't be a good idea to use IDisposable in such a context anyway, because for instance, it won't make much sense to call ITickable.Tick() manually (maybe except for a testing purpose) and the same should go for IDisposable.
But I understand it might break the compatibility, it looks much more reasonable to be then it did before, as my confusion about the binding behavior is cleared now.
Thanks much for the clarification. And sorry about the confusion!


[BUG] There is a problem with the 'entity to input conversion constructor' in the generated input class when an alias is specified in the input dto

The input dto:

The generated input class:

It seems to me that there should be no need to convert from entity to input for the input dto to be correct.

Try 0.8.64


Update url path for deprecated endpoint calls

Reading from here
http://dev.datasift.com/docs/platform/api/rest-api/endpoints
the currently endpoints used in
https://github.com/datasift/datasift-python/blob/master/datasift/pylon_task.py
needs to be updated, actually task {type} is not considered

Hi Vittorio,
Yes that's right. The library needs to be updated for v1.5 of the API. Version 1.4 of the API will be supported for the next 12 months, so the library will continue to work as it is.
That said, we have updated the code here, but we are still testing the update. We will be releasing the updated library in the next couple of weeks.
Thanks,
Rich

Thank you for the clarification
Vittorio


Add SingeliSort

Still WIP, SingeliSort crashes for certain patterns, and sort u64 missing.

Crash can be reproduce with OVERRIDE_SEED=1215502009629807262 cargo t descending_saw. See the project README on how to build the code.

Not super surprising: various components like parity_cuts to do branchless merging on any length combination are new, and none of it's that well tested. Is there a way to log the data being sorted, or build the sort with debug symbols?

Missing a *4 on the aux size argument to sort32 (also, debug diff)

And I've changed sort64 to unsigned sort_u64 for a new compiled/sort.c. The obvious singelisort_u64 implementation seems to work; I don't know how to interpret all the test output but nothing looks wrong.

@dzaima good catch. You are right the aux len is passed as size in bytes, not as size in elements. That's a kind of unfortunate inconsistency to how the input len is passend.

And I've changed sort64 to unsigned sort_u64 for a new compiled/sort.c. The obvious singelisort_u64 implementation seems to work; I don't know how to interpret all the test output but nothing looks wrong.

Thanks will check out.

Not super surprising: various components like parity_cuts to do branchless merging on any length combination are new,

I have a generalized version of parity merge https://github.com/Voultapher/sort-research-rs/blob/main/src/graveyard/ipn_stable_with_probe_common.rs#L1064 if you don't care about Ord safety you can even remove some of the checks.

Aux is interpreted as many different types by different algorithms, so I felt like bytes was the only measure that made sense.
The parity_cuts method is different from your version (or glidesort) in that every merge step it does is unguarded. Those checks in the bi_directional_merge while loop look potentially costly. My version is kind of over-engineered though. If the size imbalance is large enough it's better off skipping the cuts and doing a galloping-style merge that skips through the larger argument quickly. Probably only one set of cuts is useful.

Tests now pass, but I didn't do any fancy fuzzing or so.

Running benchmarks now, will post results here.

Aux is interpreted as many different types by different algorithms, so I felt like bytes was the only measure that made sense.

That is an internal story, you could easily divide by sizeof(T). From an API standpoint I suggest you follow the approach other implementations use uniform metrics. Also it would be great to get an error if the aux size is too small instead of a crash. I took the aux size from the benchmark code, probably could do with some wrappers that take care of the allocation.

Interactive graphs analysis.tar.gz
Results look impressive. Surprisingly though the pattern perf sees large difference between i32 and u64, random_d20 and random_z1 seem to be affected the most.

SingeliSort is modular, so if you want say a pure counting sort you can make a variation on sort.singeli and compile one for yourself. Building in a division makes this more confusing. Also aux is consistently a void pointer and I just think it's weird to measure it in varying units—it's bench.c that's sloppy about this, not SingeliSort. There's a lot to clean up about aux usage, and I'd like to be able to operate with less space for large arrays. The distribution base cases generally check aux size; merging in glidesort should use swaps to cut down on space if there isn't enough. I'll add an allocating version at some point.
I can reproduce the random_d20 slowdown in your benchmarks, but not in C (including compiled as C++) using rand()%20. There u64 is a little better than half as fast as i32, as expected: it goes to counting sort and most of the time is just writing the results. And it should perform the same on any random-ish list of integers in [0,20), no matter how they're distributed. Any ideas as to what would be different?

Any ideas as to what would be different?

I guess the way I produce my u64 :
.map(|val| -> u64 {
    // Extends the value into the 64 bit range,
    // while preserving input order.
    let x = ((*val as i64) + (i32::MAX as i64) + 1) as u64;
    x.checked_mul(i32::MAX as u64).unwrap()
})

All right, so it no longer fits into a small range. Using INT32_MAX*((T)(rand()%20) + ((T)INT32_MAX+1)) I get much slower results (incidentally, I believe let x = ((*val as i64) - (i32::MIN as i64)) as u64 is equivalent and find it clearer).
The slower results from Zipf make sense given than Robin Hood sorting doesn't apply to such a distribution, so it has to actually do some merging. The quicksort low-cardinality handling should be doing something, but the cardinality's apparently not low enough; it improves to be nearly equal to uniform random when the size is bumped to a million.
I'd suggest having at least one benchmark that does some distribution over a small number of values picked randomly from the entire range (or some large range in the case of strings etc.).

I'd suggest having at least one benchmark that does some distribution over a small number of values picked randomly from the entire range (or some large range in the case of strings etc.).

I have a collection of additional patterns https://github.com/Voultapher/sort-research-rs/blob/5e07fb6ebb61920ff9f5e896badd88502fe40e35/benches/bench.rs#L187 I'm totally open to adding new patterns there. In terms of default patterns, I want to have 8 at most, for reasons of readability and color palette. Which means any new default pattern has to replace an existing one, I've done that a couple times in the past. But it needs a good reason why that new pattern is more meaningful than one of the existing ones.

I believe let x = ((*val as i64) - (i32::MIN as i64)) as u64 is equivalent and find it clearer).

That doesn't seem to be true. 0 -><PHONE_NUMBER>279904256 vs<PHONE_NUMBER> 3 -><PHONE_NUMBER>722355197 vs<PHONE_NUMBER>.

I'd suggest randomizing the range of z1 then. Zipf is the most like "generic data", and a sort optimizing it just because it fits in a small [0,k) range isn't very interesting; it's better accounted for in the d20 case anyway. I think it makes sense to have variations with a fixed cardinality and random range (random_c20 etc. maybe) but there's no reason to put them in the main set of 8. Unrelated comment, I doubt descending benchmarks are relevant very often in real use, certainly much less than ascending ones. But people may start asking questions if you leave that case out.
Sorry for the confusion: the i32::MIN expression just replaces one line, and you still need the multiplication after.

The 99p_zero_1p_random-10000 test uncovered a segfault caused by parity_cuts, which I've fixed allowing all EXTRA_PATTERNS=1 tests (on 10000 elements at least) to be run. I'm still seeing wrong results on this data in my testing, so more fixes to come.
SingeliSort does poorly with repeated element tests like u64-random_d1024-10000, somewhat worse than fluxsort and more like pdq. This is a case where Robin Hood sorting is used but is detrimental. The ratio of ~10 unique copies of each element is the worst case because it doesn't get caught by a sample but ends up with about 5 collisions per hash insertion, which is a lot. On the other hand if there were a way of dealing with exact duplicates, probably gated on some sort of collision counter, then RH would end up much faster than other sorts. I tested out a method using a hash table with 4-byte ints in BQN, and it came out even better than a radix sort. This would be a not-even-unstable optimization like counting sort.
For larger numbers of duplicates as in u64-random_d64-10000, switching to merge sort so quickly (<192) is detrimental because it doesn't adapt to duplicates. Also that threshold was tuned with i32 and it looks like something around 96 is better for u64. When the number gets large enough like u64-random_d64-10000 this no longer matters, but SingeliSort is still a little behind fluxsort. Annoying since I designed fluxsort's low-cardinality handling in the first place (with reference to pdqsort). I think SingeliSort is doing too much work when it gets to a partition that has all equal values.
I haven't said it yet: thanks for all your work on these tests!

I'd suggest randomizing the range of z1 then. Zipf is the most like "generic data", and a sort optimizing it just because it fits in a small [0,k) range isn't very interesting; it's better accounted for in the d20 case anyway. I think it makes sense to have variations with a fixed cardinality and random range (random_c20 etc. maybe) but there's no reason to put them in the main set of 8. Unrelated comment, I doubt descending benchmarks are relevant very often in real use, certainly much less than ascending ones. But people may start asking questions if you leave that case out.

I want to look into that in detail, thanks for the suggestion. Not sure when I'll find the time.

The 99p_zero_1p_random-10000 test uncovered a segfault caused by parity_cuts, which I've fixed allowing all EXTRA_PATTERNS=1 tests (on 10000 elements at least) to be run. I'm still seeing wrong results on this data in my testing, so more fixes to come.

Interesting, you are right in addition to my test suite the benchmark suite can by virtue of running many times and with additional patterns be seen as a kind of test.

SingeliSort does poorly with repeated element tests like u64-random_d1024-10000, somewhat worse than fluxsort and more like pdq. This is a case where Robin Hood sorting is used but is detrimental. The ratio of ~10 unique copies of each element is the worst case because it doesn't get caught by a sample but ends up with about 5 collisions per hash insertion, which is a lot. On the other hand if there were a way of dealing with exact duplicates, probably gated on some sort of collision counter, then RH would end up much faster than other sorts. I tested out a method using a hash table with 4-byte ints in BQN, and it came out even better than a radix sort. This would be a not-even-unstable optimization like counting sort.

I have to admit that I haven't looked closely at radix, or counting sorts yet. So I only understood half of that.

For larger numbers of duplicates as in u64-random_d64-10000, switching to merge sort so quickly (<192) is detrimental because it doesn't adapt to duplicates. Also that threshold was tuned with i32 and it looks like something around 96 is better for u64. When the number gets large enough like u64-random_d64-10000 this no longer matters, but SingeliSort is still a little behind fluxsort.

One idea I can provide that also fixes some of issues in glidesort is to have sqrt(len) min run below which runs are rejected and unsorted runs of that min run len are created.

Annoying since I designed fluxsort's low-cardinality handling in the first place (with reference to pdqsort). I think SingeliSort is doing too much work when it gets to a partition that has all equal values.

I wasn't aware you were involved in the development of fluxsort. You are not credited as far as I can tell.

Glidesort's using a sqrt(n/2) threshold as of v0.1.2: commit. This seems not very principled to me. Working it out now, if merge is 20% slower than partition and the whole array is made of length-r runs, you'd want to switch over when 1.2 log(n/r) = log(n), or 0.2 log(n) = 1.2 log(r), which gives r = n^(1/6). Square root would be appropriate for a factor of 2 difference, but the more important concern is low-cardinality versus natural runs where the length of the run is just not enough information. And for only one run, even making the top step a merge costs 0.2 n, so O(n), for a savings of O(sqrt(n)log(n)) so the asymptotics are still not right there.
I've mangled glidesort quite a bit. The run finder actually always searches until it finds a long enough run, so unsorted sections all get grouped together. Then in the logical merge part it ignores sortedness if it would merge an unsorted section with a substantially smaller sorted one. Still not perfect, but one run in the middle can't force everything to use merges.
I just thought of a simple test for a single repeated element: once you find the run, compare the elements 1/3 and 2/3 along it: they're equal if and only if 2/3 of elements are the same. Not a full solution but it seems nice and practical.
The issue with u64-random_d64-10000 was quicksort switching to the base merge though: the glide layer never gets involved as there aren't natural runs.
There's a comment in fluxsort's source. I don't care about attribution though, and have told Scandum that.


⚠ Samsung has degraded performance

In 6bbe106, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2359 ms

Resolved: Samsung performance has improved in 0780ea7.


Selectpicker is hidden how to refresh ?

Hello,
I have question because I can't resolved this problem.
I use bootstrap-select and everything is work corectlly.
But I have some issue is : If I select option in search , results is hidden ....
I use option
I must refresh entire page then I see my choice.
What I do wrong ? Can someone ...
( Gif screen )
http://recordit.co/WHsP5LSaOW
Thank you

What version of bootstrap-select are you using? What is your resolution? It seems like your screen is really small and there's not enough room for the menu.

Hello,
I use new version : 1.12.4  No no it's only example screen with my monitror. I use 24" monitror.
Please see again : http://recordit.co/zoBM4xNT4B
Plugin works ok but i have problem I need refresh page If i want to see selected result. Selected option isn't loading.
thank you

Seems like there is a conflict somewhere - I'd be happy to investigate further if you can link me to an example. Try giving v1.13.0-beta a try as well: https://github.com/snapappointments/bootstrap-select/releases/tag/v1.13.0-beta.

Hello ,
Please see sample live website. Left column. Selectet filters is hidden ( select.bs-select-hidden, select.selectpicker { /* display: none!important; */}
https://goo.gl/CeMvWe
thank you

I have the same problem, the DDL disappears when I change status.
Could you solve it?

@Vameo You need to load the bootstrap-select CSS later - it's being overwritten by some of your other CSS.


Problemmatcher not work over ssh

OS and Version:win7 x64
VS Code Version:1.40.2
task.json
{
	"version": "2.0.0",
	"tasks": [
		{
			"label": "zcsshbuild",
			"type": "shell",
			"command": "d:\\putty\\plink.exe -pw passwd user@server \"cd workspace/${workspaceFolderBasename} && ./zcmake.sh\"",
			"group": {
				"kind": "build",
				"isDefault": true
			},
			"problemMatcher" : {
				"fileLocation" : ["relative", "${workspaceFolder}"],
				"pattern" : {
					//"regexp": "^.*$",   // not work too
					"regexp" : "/home/workspace/testproject/([^:]*):(\\d+):(\\d+): (E|e)rror:(.*)"
					"file" : 1,
					"line" : 2,
				}
			}
		}
	]
}

Steps to Reproduce:
1.ctrl+shift+b to build
2. Terminal show message:
/home/workspace/testproject/src/test.c:423:26: error: 'a' undeclared (first use in this function)
3. It's nothing happen when double click message above. Terminal show message above not highlight
plink.exe is a tool that can connect to ssh server and do something in batch. It include in putty software

I made a test task:
        {
			"label": "zcsshbuild",
			"type": "shell",
			"command": "echo",
			"args": ["/home/workspace/testproject/src/test.c:423:26: error: 'a' undeclared (first use in this function)"],
			"group": {
				"kind": "build",
				"isDefault": true
			},
			"problemMatcher" : {
				"fileLocation" : ["relative", "${workspaceFolder}"],
				"pattern" : {
					"regexp" : "/home/workspace/testproject/([^:]*):(\\d+):(\\d+): (E|e)rror:(.*)",
					"file" : 1,
					"line" : 2,
				}
			}
		}

It created a problem:

Problem looks good:

If plink does a bunch of re-writing of existing terminal content or some other unexpected operation with the terminal then Tasks might have trouble reading what's in the terminal and be unable to use problem matchers. You can see what lines tasks is reading by placing a breakpoint here https://github.com/microsoft/vscode/blob/79970801922dfabd5be3711ea7869e483655a0e8/src/vs/workbench/contrib/tasks/browser/terminalTaskSystem.ts#L721


Move documentation out of word doc and into the OpenAPI and ReadTheDocs

Component to be refactored
restapi.docx with initial documentation on the repository.
Purpose of refactoring
Allows for better versioning as documentation can live alongside the source (instead of uploading a new word doc for every change).
Proposed method
Applicable documentation should be contained within the OpenAPI documentation and anything more verbose should be migrated to the OpenDCS ReadTheDocs.

oh FYI, I used pandoc to do the conversion to rst for the main OpenDCS documentation. I don't remember having major issues - though there was a lot of manual work dealing with the tables. Shouldn't be as bad as the main docs though.


Fix typo in documentation of Value::F64

There were the following issues with your Pull Request

Commit: 161c5d6e264350869d9105cdc53c0b05c8bb3a28
Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/serde-rs/json

This message was auto-generated by https://gitcop.com


Node.js 14 preview

Resolves https://github.com/Azure/azure-functions-nodejs-worker/issues/327

Hey @anthonychu and @pragnagopa - mind reviewing? thanks!


Unable to run demo example

Hi,
First time trying to get the demo example running, I followed the README instructions (also copied lv_conf.h and lv_drivers_conf.h to this repo root dir) but ended up with this error (similar to #152). There seems to be an empty -D after DLV_CONF_INCLUDE_SIMPLE:
$ DEP_LV_CONFIG_PATH=`pwd` cargo run --example demo --features="alloc"
   Compiling lvgl-sys v0.6.2 (/home/d3bug/Desktop/lv_binding_rust/lvgl-sys)
The following warnings were emitted during compilation:

warning<EMAIL_ADDRESS><command-line>: error: no macro name given in #define directive

error: failed to run custom build command for `lvgl-sys v0.6.2 (/home/d3bug/Desktop/lv_binding_rust/lvgl-sys)`

Caused by:
  process didn't exit successfully: `/home/d3bug/Desktop/lv_binding_rust/target/debug/build/lvgl-sys-3e9d9eb4b2672d68/build-script-build` (exit status: 1)
  --- stdout
  cargo:rerun-if-changed=/home/d3bug/Desktop/lv_binding_rust/fonts
  cargo:rerun-if-changed=/home/d3bug/Desktop/lv_binding_rust/examples/include/lv_conf.h
  cargo:rerun-if-changed=/home/d3bug/Desktop/lv_binding_rust/examples/include/lv_drv_conf.h
  cargo:rerun-if-env-changed=LVGL_INCLUDE
  cargo:rerun-if-env-changed=LVGL_LINK
  OUT_DIR = Some(/home/d3bug/Desktop/lv_binding_rust/target/debug/build/lvgl-sys-3bb4c439822ae584/out)
  OPT_LEVEL = Some(0)
  TARGET = Some(x86_64-unknown-linux-gnu)
  HOST = Some(x86_64-unknown-linux-gnu)
  cargo:rerun-if-env-changed=CC_x86_64-unknown-linux-gnu
  CC_x86_64-unknown-linux-gnu = None
  cargo:rerun-if-env-changed=CC_x86_64_unknown_linux_gnu
  CC_x86_64_unknown_linux_gnu = None
  cargo:rerun-if-env-changed=HOST_CC
  HOST_CC = None
  cargo:rerun-if-env-changed=CC
  CC = None
  cargo:rerun-if-env-changed=CC_ENABLE_DEBUG_OUTPUT
  RUSTC_WRAPPER = None
  cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some(true)
  CARGO_CFG_TARGET_FEATURE = Some(fxsr,sse,sse2)
  cargo:rerun-if-env-changed=CFLAGS_x86_64-unknown-linux-gnu
  CFLAGS_x86_64-unknown-linux-gnu = None
  cargo:rerun-if-env-changed=CFLAGS_x86_64_unknown_linux_gnu
  CFLAGS_x86_64_unknown_linux_gnu = None
  cargo:rerun-if-env-changed=HOST_CFLAGS
  HOST_CFLAGS = None
  cargo:rerun-if-env-changed=CFLAGS
  CFLAGS = None
  cargo:warning=<command-line>: error: no macro name given in #define directive

  --- stderr

  error occurred: Command "cc" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-gdwarf-4" "-fno-omit-frame-pointer" "-m64" "-I" "/home/d3bug/Desktop/lv_binding_rust/lvgl-sys/vendor/lvgl/src" "-I" "/home/d3bug/Desktop/lv_binding_rust/lvgl-sys/vendor" "-I" "/home/d3bug/Desktop/lv_binding_rust/examples/include" "-I" "/home/d3bug/Desktop/lv_binding_rust/fonts" "-I" "/home/d3bug/Desktop/lv_binding_rust/lvgl-sys/vendor/lv_drivers" "-I" "/usr/include" "-I" "/usr/local/include" "-DLV_CONF_INCLUDE_SIMPLE=1" "-D=" "-o" "/home/d3bug/Desktop/lv_binding_rust/target/debug/build/lvgl-sys-3bb4c439822ae584/out/99299a8c29a71c18-fonts_noto_sans_numeric_80.o" "-c" "/home/d3bug/Desktop/lv_binding_rust/fonts/fonts_noto_sans_numeric_80.c" with args cc did not execute successfully (status code exit status: 1).

Fixes with #177


add online-monitor plugin for area vs width

What is the problem / what does the code in this PR do
There is a request for online monitoring.  This PR provides the user with the data to very easily make area vs widht plots. See the demo here for an example:
https://xe1t-wiki.lngs.infn.it/doku.php?id=xenon:xenonnt:angevaare:onlinemonitor#demo
Can you briefly describe how it works?
Make the output in a histogram, write that to the mongo database
Can you give a minimal working example (or illustrate with a figure)?
https://xe1t-wiki.lngs.infn.it/doku.php?id=xenon:xenonnt:angevaare:onlinemonitor#demo

As to your question Daniel, please see:
https://xe1t-wiki.lngs.infn.it/doku.php?id=xenon:xenonnt:angevaare:onlinemonitor

@feigaodm , @skazama , are there any requests for this tool? At the moment it looks like the lone hit-rate over time but are there any others?
Please keep in mind that the data has to be compact, I can make histograms but either using predefined cuts or none at all. As such, I like keeping the aggregation per chunk as you know you cannot make larger documents as the length is fixed to 1 data-field per chunk.
If there are no more requests at the moment, I can merge this PR and add new features later too.

I can make histograms but either using predefined cuts or none at all. As such, I like keeping the aggregation per chunk as you know you cannot make larger documents as the length is fixed to 1 data-field per chunk.

Maybe we can implement some default cuts on the following parameters:

n_channels
area_fraction_top
rise_time
tight_coincidence

and

type

This gives the analyzers alot of freedom for the online monitoring. The first four option would look by default like this ```
Option(field_name (None, None)`
and in the code:

m = np.zeros(len(data), dtype=np.bool_)
for option in options:
m &= data > ...
 so that one can specify and lower and upper bound. The last one would then be invoked in an additional step.

Hi Daniel! This unfortunately does not work! If you change the options, the user won't be able to change the config that is running on the eventbuilder. Only when we somehow add all this info we can do cuts but that then again implies the data would be too big. In fact this requires all those properties to be shipped individually.
Of course I can add it as an option and add the implementation as we do here (https://github.com/AxFoundation/strax/blob/master/strax/context.py#L1032) but the effect is not as you describe.

Ah I see. Not sure I am just thinking out of the blue, but could we ship the context itself via mongo?

Ah I see. Not sure I am just thinking out of the blue, but could we ship the context itself via mongo?
Oh for sure we can, but I don't want non-experts touching anything going on with the live-processing.

I agree on that, but could not we have a second "online_monitoring_context" which runs the required processes?

Hi Joran, thanks for adding this feature, I think it's important. At different stage, we might need to add different features. For example, during the cathode light emission test, we would add the lone-hit rate. For Kr83m, we may add Kr83 double-S1 peaks in addition to the standard peak width vs are. But I believe this example is helpful for analyzers to develop and contribute.


TestLocalShellRunner fails if stanley user is not available

https://github.com/StackStorm/st2/blob/78ea95791b24f34ab6f113b176ae0de7497ad4c1/st2actions/tests/integration/test_localrunner.py#L32
Either the test should guarantee the user or have a way to easily provide an alternate user. Assuming stanley becomes messy.

I thought this was a known pre-requisite since integration tests have many other pre-requisites as well (MongoDB needs to be running, etc.).
In any case, that's something we should make explicit in the docs.

I thought this was a known pre-requisite

Not saying user will not be provided just that the user has to be stanley would be an issue.

@manasdk That's fair.
It sounds like we should use the value from the tests configuration?

It sounds like we should use the value from the tests configuration?

Yes. That would work.

Doesn't seem to be relevant any more.


reporting cwt18 archlinux boots successfully

Here is what I did:
write vf2 debian minimal desktop to sdcard
sudo bash
lsblk
 ### umount anypartitions on /dev/sda
wipefs --all /dev/sda
bunzip2 starfive-jh7110-VF2_515_v3.8.2-66-SD-minimal-desktop-wayland.img.bz2
dd bs=4M if=starfive-jh7110-VF2_515_v3.8.2-66-SD-minimal-desktop-wayland.img of=/dev/sda status=progress
#don't forget to resize its root partition to take advantage of any free sdcard capacity
gparted /dev/sda

boot into vf2 debian minimal desktop to flash the latest spl and the uboot
apt-get install mtd-utils
cat /proc/mtd
### dev: size erasesize name
### mtd0: 00040000 00001000 "spl"   <<<----blasting this one
### mtd1: 00010000 00001000 "uboot-env"
### mtd2: 00300000 00001000 "uboot"    <<<<----blasting this one
### mtd3: 00100000 00001000 "data"
flashcp -v u-boot-spl.bin.normal.out /dev/mtd0
flashcp -v visionfive2_fw_payload.img /dev/mtd2
sync
sync
shutdown -h now

write cwt18 vf2 archlinux minimal image to sdcard
lsblk
umount /run/media/cissy/root
wipefs --all /dev/sda
xzcat ./ArchLinux-VF2_5.15.2_v3.8.2-cwt18.img.xz | sudo dd bs=4M conv=fsync of=/dev/sda

#don't forget to resize its root partition to take advantage of any free sdcard capacity
gparted /dev/sda

I inserted the cwt18 archlinux sdcard into the vf2.

cwt18 archlinux reboots correctly.
cwt18 archlinux shuts down correctly as well.
displays clinfo successfully

I have some questions:

what desktop have you attempted to install with archlinux?
with cwt18 archlinux, may we pacman -Syuu now?

@omac777 Thanks for your report. I don’t use GUI or desktop on my VF2, I use it headlessly most of the time. However, there are many people who try to use GUI on this image, such as Gnome, KDE, Wayfire, as you can see in this thread . I occasionally use wayland/weston to test the GUI capability. If you want to talk to people who trying to make this image become a fully desktop, join us on https://matrix.to/#/#archlinux-riscv:matrix.org

* with cwt18 archlinux, may we `pacman -Syuu` now?

I'm always run that command first thing in the morning. :-)

cwt, please never forget you're a superhero!


Cannot start nuxt:  Cannot read properties of undefined (reading 'options')

Environment
I installed i18n on my nuxt3 project that has pinia and tailwind css and color mode installed and nothing more, when I add i18n to my nuxt.config.ts what happens is that gives this error :
Cannot start nuxt:  Cannot read properties of undefined (reading 'options')
this is my nuxt.config.ts file :
// https://nuxt.com/docs/api/configuration/nuxt-config export default defineNuxtConfig({   devtools: { enabled: false },   css: ['~/assets/css/main.css'],   modules:['@pinia/nuxt','@nuxtjs/color-mode', '@nuxtjs/i18n'],   i18n: {     vueI18n: './i18n.config.ts' // if you are using custom path, default    },   colorMode: {     classSuffix: '',     preference: 'light',     fallback: 'light',   },   postcss: {     plugins: {       tailwindcss: {},       autoprefixer: {},     },   }, })
Reproduction
just follow basic instructions of adding tailwind css since in @nuxtjs/tailwind the dark mode class doesnt work :
https://tailwindcss.com/docs/guides/nuxtjs
pinia :
https://pinia.vuejs.org/ssr/nuxt.html
and color-mode
https://color-mode.nuxtjs.org/
and i18n :
https://nuxt.com/modules/i18n
Describe the bug
Doesnt let the dev server to start for this error :
Cannot start nuxt:  Cannot read properties of undefined (reading 'options')
Additional context
No response
Logs
ERROR  Cannot start nuxt:  Cannot read properties of undefined (reading 'options')                                                                                1:32:12 PM

  at _default (D:/Projects/Production/Personal/website 2/portfolio-website/portfolio-website/node_modules/@nuxtjs/i18n/src/index.js:15:92)
  at installModule (/D:/Projects/Production/Personal/website%202/portfolio-website/portfolio-website/node_modules/@nuxt/kit/dist/index.mjs:2439:101)
  at async initNuxt (/D:/Projects/Production/Personal/website%202/portfolio-website/portfolio-website/node_modules/nuxt/dist/index.mjs:3696:7)
  at async NuxtDevServer._load (/D:/Projects/Production/Personal/website%202/portfolio-website/portfolio-website/node_modules/nuxi/dist/chunks/dev2.mjs:255:5)
  at async NuxtDevServer.load (/D:/Projects/Production/Personal/website%202/portfolio-website/portfolio-website/node_modules/nuxi/dist/chunks/dev2.mjs:187:7)
  at async NuxtDevServer.init (/D:/Projects/Production/Personal/website%202/portfolio-website/portfolio-website/node_modules/nuxi/dist/chunks/dev2.mjs:182:5)
  at async Object.run (/D:/Projects/Production/Personal/website%202/portfolio-website/portfolio-website/node_modules/nuxi/dist/chunks/dev-child.mjs:103:5)
  at async runCommand$1 (/D:/Projects/Production/Personal/website%202/portfolio-website/portfolio-website/node_modules/nuxi/dist/shared/nuxi.c6444792.mjs:1647:7)
  at async runCommand$1 (/D:/Projects/Production/Personal/website%202/portfolio-website/portfolio-website/node_modules/nuxi/dist/shared/nuxi.c6444792.mjs:1638:11)
  at async runMain$1 (/D:/Projects/Production/Personal/website%202/portfolio-website/portfolio-website/node_modules/nuxi/dist/shared/nuxi.c6444792.mjs:1770:7)

I think you installed older version by using npm i -D @nuxtjs/i18n
it should be npm i -D @nuxtjs/i18n@next as they mentioned in the docs

I've encoutered the same issue on a Windows machine. Using WSL to perform the nuxt prepare is a potential workaround. I don't know if the issue could come back when I'll have to install another dependency in my project.

Thanks everyone for the kind support and guidance
the version of I18n I had to use to fix this issue was different, I fixed it fortunately, Thanks everyone. ❤

@AdeoRemiDoolaeghe if you're still experiencing this issue, could provide a reproduction?
Glad to hear this issue has been resolved for you @amirsafaricg!


Add support for webapp instance restart

The current restart restarts all the instances at once, we need to add support to restart a specific instance

@btardif can you comment on this one? Thank you.

Closing this issue as obsolete for lack of activity.


updated select story events

Added

on:populated to Select story

:tada: This PR is included in version 3.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


FAILURE_BUCKET_ID:  0x139_1e_INVALID_NEXT_THREAD_nt!KiFastFailDispatch

Please document what parameter 1 1E means for BUGCHECK 0x139. If it is actually that the next thread is invalid, a hint regarding what the invalid thread object address is would be helpful. At least with that data debug logs might be useful for establishing a root cause.

@Cheoljin . Which article are you referring?

@HollisTech - Thanks for this request. I don't see a value of param 1 equal to 1E, so will close this issue. Let me know if this is something you have seen in !analyze -v. You can see the known values for 0x139 using !analyze -show. You may be aware that the thread commands in the debugger can be used to look at the thread objects. Good luck with resolving the issue you encountered, and thanks for providing feedback on the stop code docs.