Restore calibration parameters

Adding for the platform currently in main a calibration.json to store the calibration parameters.
See https://github.com/qiboteam/qibocal/pull/1021 for more information.

Yes, calibration is closer to the content of parameters.json, while the current calibration.json mostly contains characterization parameters (values that identify the specific physical, rather than the optimal ones to control it in a certain way).
However, it is true that it may even contain parameters which are neither (as validation ones, e.g. the RB fidelities), so it is harder to find it a perfectly suitable name (other than parameters-leftover.json). The idea of calibration.json is just to mirror the cal in Qibocal - we could call it qibocal.json, but it may be weird as well for other reasons.
If you have a fuzzier term than calibration, we could use that. We can even use characterization.json, as in general more accurate (though not completely) - but it is further from Qibocal and harder to type :P
We just need any random name, and to document it well. And giving meaningful names is one of the hard problems in CS... (and science in general)

My initial idea was parameters -> calibration and calibration -> characterization, but this requires breaking qibolab 0.2 so it's not an option. In any case, I am fine leaving as it (following the qibo-cal argument) is or just renaming calibration -> characterization.
Another thing to note is that QM platforms may also have a calibration_db.json (autogenerated - not sure if I can change the name but I can check), which may add more confusion but it's not an exact conflict so it won't be an issue in practice.

Thanks @stavros11, indeed we should merge. I will double check if I forgot to push something since a few things were changed in https://github.com/qiboteam/qibocal/pull/1021 in the meanwhile. If it works we can merge.

I thought that it might be a good idea to add here also channels for the 12 transition before merging this PR.
I've just pushed the updated version for the qubit_spectroscopy_ef protocol in https://github.com/qiboteam/qibocal/pull/1021. Here are the results.
It seems to work however, if I am not mistaken before we were measuring an anharmonicity of around 211 MHz now it is roughly 300 MHz.
@alecandido @stavros11 feel free to have a look to check that the way in which I added the new channels is correct.
If so, feel free to merge.

@andrea-pasquale I will check it better later on, but at first it seems good to me.
I'm still thinking of implementing an easy way to expand the platforms' channels during the experiment definition, since the information you're providing for the transitions is the exact same of the corresponding drive channel (since the physical medium is the same), and you should not be forced to repeat it.
Since the instrument object is still mutable, an easy way would be to do something like:
class Controller(...):
    def add_transition(self, drive: ChannelId, transition: TransitionId):
        ...

But it may be even better to do it immutably
class Controller(...):
    def with_transition(self, drive: ChannelId, transition: TransitionId) -> Self:
        ...

and then expose somehow in the execute method of the Platform, e.g.
class ExecutionParameters:
    ...
    transitions: list[TransitionId]

The only pain point is that you will need to calibrate natives assigning them channels which do not exist in the original platform. We could try to do something to improve do situation, like:
class ExecutionParameters:
    ...
    transitions: Optional[list[TransitionId]] = None

and in the case in which is None, we try to infer the extra channels from the natives (but we will need to extend the Pulse to have a TransitionId, and do something convoluted, since we should look at the RX to check which is the drive channel, since in principle we do not know even in which instrument is the physical channel - everything quite messy).
This is just a rough sketch, but if you believe it may be useful to have something of this, or keep discussing the thing, we could open an issue in Qibolab to continue the design process.
If you believe the current setup is just good, we can leave it as it is.
My perspective is that it is actually useful to play at the level of logical channels in the sequences, since it makes it closer to the actual execution. But the physical part should remain confined to the initial platform layout, we should not need to be modified because further transitions are calibrated (you should not need to find which is the relevant Octave to calibrate a new transition). So, we may be missing a separate physical layer abstraction... @stavros11

Both the channel addition and the routine update look correct to me. Btw, I think the link under "results" is not correct, it is linked to a PR instead of the actual results (I was expecting a report).

You are right, here is the correct link http://login.qrccluster.com:9000/_lJj3FqjSSuHY5mRd7C1hg==/

I am not sure what is causing the difference in anharmonicity. If we want to exclude potential issue with 0.2, I would repeat the same measurement, on the same qubits, with the same calibration, using 0.1. If the results agree then most likely it's not a qibolab issue, otherwise I would check the QUA scripts to find the difference. The first part (reproducing and comparing 0.1 and 0.2 results) is quite tedious especially without an automated way of converting platforms, so if we want to go to that direction in may be worth investing time in the conversion script. A quicker check would be to just generate and compare the QUA scripts without worrying about actual executions.

I was doing something wrong with the anharmonicity, I fixed the problem in https://github.com/qiboteam/qibocal/pull/1036/commits/b094c4eb1ed53530641eb9a97c67863348e60750

In any case, I would probably move this discussion to a qibolab issue, as I would expect this PR to be merged soon, since the corresponding qibocal PR is already merge (to 0.2 branch). I agree that it might be worth retesting on hardware before merging (I will also try to do that), as many changes happened since I last tried.

I agree, from my side we can merge.

I agree, from my side we can merge.

Even from my side, the proposal to improve was not to be implemented right now. I'll move the discussion into an issue and tag both of you :)


[T2A4] [T15-A2] Muhammad Irwan Bin Hussin

Ready for Review

@nawri14

Good job in refactoring it into bad code by making some frequently used methods to be inline. This indeed spoil the code by reducing readability.
There are still many more ways to refactor the code to make it worse. They can be found from http://refactoring.com/catalog , where u can do the reverse of those to make the code bad.


Update context-menu

This change is

Should be done through platform/versions.json. If you want this into V10 update that file as well, and regenerate the core bower file.

Ok move this to platform
https://github.com/vaadin/platform/pull/200


0.2.0 Failed to resolve dependencies

Issue while trying to use 0.2.0

because no versions of FLite match the requirement 0.2.1..<1.0.0 and package flite is required using a version-based requirement and it depends on unversion package fluent-sqlite-driver, FLite >=0.2.0 is forbidden.
And because root depends on FLite 0.2.0..<1.0.0, version solving failed.

Temp solution
Use the master branch

Fixed in 0.2.1


first commit, smoke test working

Looks good, J! Will merge
Would we want to consider adding in app.use(express.static('public')); ?


Add link to NetSparkleUpdater as option for Win

Disclaimer: I am the author/maintainer of NetSparkleUpdater, a Sparkle-style Windows software update framework written in C#. Before suggesting this change, I asked permission of the WinSparkle library (https://github.com/vslavik/winsparkle/issues/213) to make this change, and we agreed on the verbiage to use.
This PR simply adds a link to NetSparkleUpdater along with the existing link to WinSparkle.

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

#sign-off


Could we add more index for BKD LeafNode?

Description
Currently in BKD LeafNode,  we scan all 512 values and call visitor.visit  in CELL_CROSSES_QUERY case, this is usually not a issue for range query, but for point query, such as PointInSetQuery, maybe only one value hit at a leaf node, but it still scan all the block. in 1D case, values will visited in increasing order. maybe we can create a special index structure for these 512 values, for instance, write the point value/offset per 32 values, used to skip some point values that will not match, i had wrote some POC code, it will improve query performance by 20% in high cardinality(10  million), but no improve in  lower cardinality,  and expected that a lot of changes

I am not sure this is the right trade off. The BKD tree was developed to perform efficient range queries. If your use case is to perform efficient PointInSetQuery, you might be better indexing your data using the inverted index as the performance should be better for this type of query.
Another option might be to lower the maxPointsInLeafNode from 512 to a lower value. That might provide you a similar effect without having to introduce an extra data index structure. The tradeoff here will be the index size.


fix helm install failed if ns doesn't be created beforehand

What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #100
Special notes for your reviewer:
Does this PR introduce a user-facing change?
N/A

Thanks! @jxs1211
👍 👍 👍

cc @Vacant2333 for final checking

Thanks！
/lgtm


qa_crowbarservice: fix service-list command in nova.

Breaks gating in SOC7

+1

+1

Sorry, hit the wrong button, didn't mean to close this.

+1


Attempt to fix status function body (PAYM-502)

Motivation

I'd like to be able to set the status function on the interface and make sure it doesn't fail on the interface check

Modification

Updated the request interface to be any

https://centeredge.atlassian.net/browse/PAYM-502

/merge


Added viewport meta tag

- Summary
Forgot to add it to two sites, so I think I would be good in the default 'template'. It won't do harm, but will do good if you look at your site on a real device 💯
- Test plan
Viewed on real device.
- Description for the changelog
Added viewport meta tag to header partial
- A picture of a cute animal (not mandatory but encouraged)

I will fix this shortly :) Thank you for the hint.


Thoughts on "Eliminate render-blocking JavaScript and CSS in above-the-fold content"?

Love this project.  It's my go to for all wordpress sites!
Question as you plan for FoundationPress v6...
My FoundationPress sites always get penalized in Google's PageSpeed insights for render-blocking JavaScript and CSS.
For example: https://developers.google.com/speed/pagespeed/insights/?url=parsleyhealth.com
Is there another approach that can be taken as you design the new V6 codebase?

Hi @dberz ,
Page Speed is, and should always be, a top priority. In FoundationPress there are two javascripts loaded in the header out of the box; fastclick and modernizr. Unfortunately both of these scripts needs to be added in the head section of the document in order to function properly.
FastClick is a simple library for eliminating the 300ms delay between a physical tap and the firing of a click event on mobile browsers. The aim is to make your application feel less laggy and more responsive while avoiding any interference with your current logic.
Modernizr is used for feature detection such as portrait and landscape. It's also used for the visibility classes.
On your web site it seems that you have 28 render-blocking script resources and 27 render-blocing style resources. From what I can see, this comes mainly from the use of external plugins

Chris Coyier has written a blog post that sheds light on this issue, with different solutions to fix this.
The main focus of the Foundation 6 release has been to ditch the bloat and make a lighter framework. This will (hopefully) result in improved performance and optimized page speed.
I have no set date for when FoundationPress will be upgraded to Foundation 6. But it will happen. Earlier versions based on F5 will always be available for download in the release archive.

Fantastic response.  Very helpful.  Yes, my sites use a ton of plugins and I'll look to the CSS-Tricks post to get these guys under control!


Deflake secure.py test_restart method.

@sougou

Remove extra wait for pid port; pid is served from the main port now.
Use wait_step instead of fixed wait for test condition.

lgtm
I complain, and you fix?
I'm just gonna keep complaining :).

Try it and see what happens. What's certain though is that if you don't complain, I won't fix it. :)

+10 for deflaking tests. I'm going to put a low priority item on my TODO list to get rid of all fixed waits in our Python tests.


HDStats is private, can we make it public

Hey Dale
Can we please make this repo public and perhaps hosted in the ODC organisation?
It's apache licensed, but it's not open if it is not discoverable.
Is there any good reason for it to remain private?

Anyway, thanks very much @daleroberts


feat: Record original user agent for spans and logs

Which problem is this PR solving?
Refinery loses the original user agent of the sending application because it aggregates spans until a trace decision is made. This PR records the original user agent for both HTTP and gRPC requests to the event, batch and OTLP trace/log endpoints in a new metadata field meta.refinery.incoming_user_agent.

Closes #1356

Short description of the changes

Update event, batch, OTLP trace/logs endpoints to record original user agent in new field
Update tests to verify events have the new field set
Add defer for bad API key test to restore allowed keys so subsequent tests can pass

We'll also want to make an update in shepherd telemetry to capture this like we do the user_agents strings today.


Fixed reading po file with multiline plural msgstr

If a po file contains multiline entries for plural strings like
msgid ""
"foo"
msgid_plural ""
"bar"
msgstr[0] ""
"baz"
msgstr[1] ""
"druggeljug"

the compiler complains with errors like
2017-12-20 08:28:51.160 [error] translation     Cannot interpret line because there is no key to append to, line 6, lastKey: '', line: 'baz'
2017-12-20 08:28:51.161 [error] translation     Cannot interpret line because there is no key to append to, line 8, lastKey: '', line: 'druggeljug'

and drops the msgstr[...] entries:
msgid "foo"
msgid_plural "bar"
msgstr[0] ""
msgstr[1] ""

The command set(lastKey, line, true) can handle entries like this, but is not called because of the condition in line 212.
The fix checks adds an additional check if the entry ends with [<number>].

3 days, all aproved. merged.
Thanks @mbgonicus!


How to autoplay cards towards right?

Auto play is working but cards are moving in left direction but I want to move it to right. What property i have to use to move in right direction?

You can try using this property:
axisDirection: AxisDirection.right,


When EditorSettings:use_external_editor is on, right-click on a Script icon to open Godot Script Editor

Feature request!
Now and then, you'd want the best of both world.
Right-click on Script icon doesn't do anything for now and seems available for this.

I agree with adding a feature for that, but I'm not sure that right-click on the Script icon would be intuitive for that.

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.
The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.
If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!


fix ecccodes lib dir in cosmo package

set to lib64 instead of lib for version after 2.19.0

launch jenkins --test=root cosmo<EMAIL_ADDRESS>real_type=double cosmo_target=gpu +eccodes +claw +verbose<EMAIL_ADDRESS>

launch jenkins --test=root cosmo<EMAIL_ADDRESS>real_type=double cosmo_target=gpu +eccodes +claw +verbose<EMAIL_ADDRESS>

Note : we need to merge this asap, because the change from yesterday change the default so that now it fails in master.

Note : we need to merge this asap, because the change from yesterday change the default so that now it fails in master.

The error in jenkins is related to netcdf. Not sure if it is coming from eccode change

The error in jenkins is related to netcdf. Not sure if it is coming from eccode change

@elsagermann I suggest to merge this if review ok since master is currently not working - I'll look at the netcdf error separately

@elsagermann I suggest to merge this if review ok since master is currently not working - I'll look at the netcdf error separately

launch jenkins --test=root cosmo<EMAIL_ADDRESS>real_type=double cosmo_target=gpu +eccodes +claw +verbose

launch jenkins --test=root cosmo<EMAIL_ADDRESS>real_type=double cosmo_target=gpu +eccodes +claw +verbose

@elsagermann can you approve the PR so that I can merge if I find the issue

@elsagermann can you approve the PR so that I can merge if I find the issue

launch jenkins --test=root cosmo<EMAIL_ADDRESS>real_type=double cosmo_target=gpu +eccodes +claw +verbose

launch jenkins --test=root cosmo<EMAIL_ADDRESS>real_type=double cosmo_target=gpu +eccodes +claw +verbose

I had to revert the 2.18.0 change, becuase it does not allow me to use 2.19.0, somehow we would need a default but that we can change

I had to revert the 2.18.0 change, becuase it does not allow me to use 2.19.0, somehow we would need a default but that we can change

This branch is working when testing from cosmo_PR the libnetcdf issue seems related to the different way the test is being run spack_PR and cosmo_PR. I merge will merge it.

This branch is working when testing from cosmo_PR the libnetcdf issue seems related to the different way the test is being run spack_PR and cosmo_PR. I merge will merge it.


Property 'mutedSegmentData' must allow null

Type:  #Bugfix

Fixes: #388

mutedSegmentData
Array of muted segments in the video.
If there are no muted segments, the value will be null.
twitch reference
my solution
muted_segments: HelixVideoMutedSegmentData[];  // -> muted_segments: HelixVideoMutedSegmentData[] | null;

Modified to return [] using the nullish coalescing operator if mutedSegmentData is null
https://github.com/twurple/twurple/blob/058d669ed0bc24d05b833a8bc01963ab4f10f97d/packages/api/src/api/helix/video/HelixVideo.ts#L218-L220

Why did you undo the change to the internal data interface? It should be true to the original Twitch data as exactly as possible. If Twitch can return null, it should include null. This does not affect the getter, and indeed resolves the linter issue shown in the build log.

It was my mistake. I'm sorry


IngressBackend not updating for changes on source Pods

Bug description:
We've a setup very similar to https://release-v1-2.docs.openservicemesh.io/docs/demos/ingress_k8s_nginx/.
It works fine, except that when the ingress-nginx pods change (rollout restart on the Deployment for instance), it seems OSM doesn't notice it (logs are silent) and envoy is not updated,  which means all ingress traffic from the new ingress-nginx Pods is then blocked.
Affected area (please mark with X where applicable):

Install                    [ ]
SMI Traffic Access Policy  [ ]
SMI Traffic Specs Policy   [ ]
SMI Traffic Split Policy   [ ]
Permissive Traffic Policy  [ ]
Ingress                    [X]
Egress                     [ ]
Envoy Control Plane        [ ]
CLI Tool                   [ ]
Metrics                    [ ]
Certificate Management     [ ]
Sidecar Injection          [ ]
Logging                    [ ]
Debugging                  [ ]
Tests                      [ ]
Demo                       [ ]
CI System                  [ ]

Expected behavior:
OSM should watch the IngressBackend's Source Pods and update the allowed Ingress automatically.
Steps to reproduce the bug (as precisely as possible):

Setup https://release-v1-2.docs.openservicemesh.io/docs/demos/ingress_k8s_nginx/
Everything works fine
Trigger a rollout-restart on the ingress-nginx controller Deployment
Ingress traffic is blocked

How was OSM installed?:
AKS built-in addon
Environment:

OSM version (use osm version): 1.2.3
Kubernetes version (use kubectl version): 1.25.6
Size of cluster (number of worker nodes in the cluster): ~20

Not stale


Sub-menu support

It'd be great to be able to do deeper level with menus. I was thinking the syntax could be  something like this.
---
name: FooComponent
parent: Project 1
menu: Components
route: /project-1/components/foo-component
---

That's a really good point dude, we already have an issue on our roadmap that's about the menu order and I think that this can fit together with it, please give us your vote and idea there's and in a near future we can make this changes for you 🙏

Is there any update on this? I saw that it was put on the roadmap has been voted on, and it appears to be labeled as "planned". What stage in development is this at, and how can I help out?
I'm trying to create sub-menus, but not seeing a way to do it yet.

In case any one else finds this later, the good folks at Docz created a new feature to support this in the v12.4 build.

Not sure on how to achieve 3 level sub menus
Adding the below still does not nest menu's Badge and Alert into Components
menu: [
    "Home",
    "Getting Started",
    {
      name: "Foundation",
      menu: ["Colors", "Global Styles", "Typography", "Content"]
    },
    {
      name: "Components",
      menu: [
        { name: "DataDisplay", menu: ["Badge"] },
        { name: "Feedback", menu: ["Alert"] },
        "Others"
      ]
    },
    "Utilities"
  ],

@phaneendra isn't possible to achieve this level of menu yet

Any update?


Lw fix webhook 1024

⚠ Pre Checklist

Please complete ALL items in this checklist, and remove before submitting

[x] I have read through the Contributing Documentation.
[x] I have added relevant tests.
[x] I have added relevant documentation.
[x] I will add labels to the PR, such as pr-type/bug-fix, pr-type/feature-development, etc.

Summary
What does this PR do?
A webhook is created, user can post issue via /api/plugins/webhook/connections/{connection_id}/issues, but it doesn't work as expected. This pr just fixes it.
Does this close any open issues?
Closes N/A
Screenshots
Include any relevant screenshots here.

Other Information
Any other information that is important to this PR.

Note that:

Whj4e
The command is incorrect. It missed the required field original_status, please add it:
"original_status":"TODO",

@mintsweet


Update website

I notice the website hasn't been updated since the 29th of October. A new version of caniusepython3 has been released and we should have at least 275 packages by now. Can you do an update, and is there any way I can help?

Good luck with that ! And thanks for the update - git-python is green now, which makes my day :) !

Ladies and gentlemen,
Auto-update (daily) should work now. Thanks for bearing patience.

Great to see, and thanks again for hosting the site !
You wouldn't believe what kind of psychological impact it made when I realised that my project was in the top-300 packages. All of the sudden, I found the motivation to push it into the python 3 realm, and was happy when it finally turned green on the site :) !

wow that's very flattering comment ... I am glad that it made positive impact :)


api documentation

I just gave a sad face to "Was this page helpful" at https://matteo-gabriele.gitbook.io/vue-gtag/methods/events and wanted to provide feedback why.
I was expecting this to have the full API documentation for the method, ie. what exact parameters can I pass.
Coming from native gtag the method is gtag('event', 'action', { 'event_category', category, 'event_label', label, 'value', value }) how to do this with $gtag is unclear.

I get it's I'll try to improve the examples, but it's literally your event data left: the library provides the boilerplate so u technically pass only the data.
I will write some more snippets

Yeah I just worked this out a second ago checking the source https://github.com/MatteoGabriele/vue-gtag/blob/master/src/api/event.js. Thanks.

You basically only pass this part 'action', { 'event_category', category, 'event_label', label, 'value', value }

added some more clearance on the event structure and some links to the method in the official documentation. hope it helps
will for sure improve more along the way


the KG data

I need the KG data of the model HieRec. Can you share with me? my email is<EMAIL_ADDRESS>

Yes, I shared the file with your email.


Chore: testing nextra version

What's the purpose of this pull request?

How it works?

How to test it?

Starters Deploy Preview

References

The issue is another PR: https://github.com/vtex/faststore/pull/1851


[Update]cloud deployment commands and preprocessing file

pass, update more commands and instructions for cloud deployment.

pass


terraform init fails with "Error: Failed to install provider"

I am using the following config
terraform {
    required_providers {
        xenorchestra = {
            source = "terra-farm/xenorchestra"
            version = "0.9.1"
        }
    }
}

# Configure the XenServer Provider
provider "xenorchestra" {
    # Must be ws or wss
    url      = "ws://hostname-of-server" # Or set XOA_URL environment variable
    username = "<username>"              # Or set XOA_USER environment variable
    password = "<password>"              # Or set XOA_PASSWORD environment variable
}

But encounter the following error when I run terraform init
Initializing provider plugins...
- Finding latest version of hashicorp/xenorchestra...
- Finding terra-farm/xenorchestra versions matching "0.9.1"...
- Installing terra-farm/xenorchestra v0.9.1...
- Installed terra-farm/xenorchestra v0.9.1 (self-signed, key ID DDBA1674AA3EA0EE)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/plugins/signing.html

Error: Failed to install provider

Error while installing hashicorp/xenorchestra: provider registry
registry.terraform.io does not have a provider named
registry.terraform.io/hashicorp/xenorchestra

$ terraform -v
Terraform v0.13.5
+ provider registry.terraform.io/terra-farm/xenorchestra v0.9.1

@andbut can you run TF_LOG=trace terraform init? Please search that output to make sure your XO credentials are not in it.
From looking at your code it seems correct and I'm surprised that it's trying to install the hashicorp version of the plug-in (which wouldn't exist)

Here you go
TF_LOG=trace terraform init
2020/11/24 08:21:59 [INFO] Terraform version: 0.13.5
2020/11/24 08:21:59 [INFO] Go runtime version: go1.15.3
2020/11/24 08:21:59 [INFO] CLI args: []string{"/usr/bin/terraform", "init"}
2020/11/24 08:21:59 [DEBUG] Attempting to open CLI config file: /home/andyb/.terraformrc
2020/11/24 08:21:59 [DEBUG] File doesn't exist, but doesn't need to. Ignoring.
2020/11/24 08:21:59 [DEBUG] ignoring non-existing provider search directory terraform.d/plugins
2020/11/24 08:21:59 [DEBUG] ignoring non-existing provider search directory /home/andyb/.terraform.d/plugins
2020/11/24 08:21:59 [DEBUG] ignoring non-existing provider search directory /home/andyb/.local/share/terraform/plugins
2020/11/24 08:21:59 [DEBUG] ignoring non-existing provider search directory /home/andyb/.local/share/flatpak/exports/share/terraform/plugins
2020/11/24 08:21:59 [DEBUG] ignoring non-existing provider search directory /var/lib/flatpak/exports/share/terraform/plugins
2020/11/24 08:21:59 [DEBUG] ignoring non-existing provider search directory /usr/local/share/terraform/plugins
2020/11/24 08:21:59 [DEBUG] ignoring non-existing provider search directory /usr/share/terraform/plugins
2020/11/24 08:21:59 [DEBUG] ignoring non-existing provider search directory /var/lib/snapd/desktop/terraform/plugins
2020/11/24 08:21:59 [INFO] CLI command args: []string{"init"}
2020/11/24 08:21:59 [TRACE] ModuleInstaller: installing child modules for . into .terraform/modules
Initializing modules...
2020/11/24 08:21:59 [DEBUG] Module installer: begin cloud-init
2020/11/24 08:21:59 [TRACE] ModuleInstaller: Module installer: cloud-init <nil> already installed in ../../modules/cloud-init
2020/11/24 08:21:59 [TRACE] modsdir: writing modules manifest to .terraform/modules/modules.json

2020/11/24 08:21:59 [TRACE] Meta.Backend: built configuration for "gcs" backend with hash value<PHONE_NUMBER>
Initializing the backend...
2020/11/24 08:21:59 [TRACE] Preserving existing state lineage "b1e747fe-9bb3-8593-1dd3-ba2ee7b46be0"
2020/11/24 08:21:59 [TRACE] Preserving existing state lineage "b1e747fe-9bb3-8593-1dd3-ba2ee7b46be0"
2020/11/24 08:21:59 [TRACE] Meta.Backend: working directory was previously initialized for "gcs" backend
2020/11/24 08:21:59 [TRACE] Meta.Backend: using already-initialized, unchanged "gcs" backend configuration
2020/11/24 08:22:00 [TRACE] Meta.Backend: instantiated backend of type *gcs.Backend
2020/11/24 08:22:00 [TRACE] providercache.fillMetaCache: scanning directory .terraform/plugins
2020/11/24 08:22:00 [TRACE] getproviders.SearchLocalDirectory: .terraform/plugins is a symlink to .terraform/plugins
2020/11/24 08:22:00 [TRACE] getproviders.SearchLocalDirectory: found registry.terraform.io/terra-farm/xenorchestra v0.9.1 for linux_amd64 at .terraform/plugins/registry.terraform.io/terra-farm/xenorchestra/0.9.1/linux_amd64
2020/11/24 08:22:00 [TRACE] providercache.fillMetaCache: including .terraform/plugins/registry.terraform.io/terra-farm/xenorchestra/0.9.1/linux_amd64 as a candidate package for registry.terraform.io/terra-farm/xenorchestra 0.9.1
2020/11/24 08:22:00 [DEBUG] checking for provisioner in "."
2020/11/24 08:22:00 [DEBUG] checking for provisioner in "/usr/bin"
2020/11/24 08:22:00 [INFO] Failed to read plugin lock file .terraform/plugins/linux_amd64/lock.json: open .terraform/plugins/linux_amd64/lock.json: no such file or directory
2020/11/24 08:22:00 [TRACE] Meta.Backend: backend *gcs.Backend does not support operations, so wrapping it in a local backend
2020/11/24 08:22:00 [TRACE] providercache.fillMetaCache: scanning directory .terraform/plugins
2020/11/24 08:22:00 [TRACE] getproviders.SearchLocalDirectory: .terraform/plugins is a symlink to .terraform/plugins

Initializing provider plugins...
2020/11/24 08:22:00 [TRACE] getproviders.SearchLocalDirectory: found registry.terraform.io/terra-farm/xenorchestra v0.9.1 for linux_amd64 at .terraform/plugins/registry.terraform.io/terra-farm/xenorchestra/0.9.1/linux_amd64
2020/11/24 08:22:00 [TRACE] providercache.fillMetaCache: including .terraform/plugins/registry.terraform.io/terra-farm/xenorchestra/0.9.1/linux_amd64 as a candidate package for registry.terraform.io/terra-farm/xenorchestra 0.9.1
2020/11/24 08:22:00 [DEBUG] Service discovery for registry.terraform.io at https://registry.terraform.io/.well-known/terraform.json
2020/11/24 08:22:00 [TRACE] HTTP client GET request to https://registry.terraform.io/.well-known/terraform.json
- Using previously-installed terra-farm/xenorchestra v0.9.1
- Finding latest version of hashicorp/xenorchestra...
2020/11/24 08:22:01 [DEBUG] GET https://registry.terraform.io/v1/providers/hashicorp/xenorchestra/versions
2020/11/24 08:22:01 [TRACE] HTTP client GET request to https://registry.terraform.io/v1/providers/hashicorp/xenorchestra/versions
2020/11/24 08:22:01 [TRACE] providercache.fillMetaCache: using cached result from previous scan of .terraform/plugins
2020/11/24 08:22:01 [DEBUG] GET https://registry.terraform.io/v1/providers/-/xenorchestra/versions
2020/11/24 08:22:01 [TRACE] HTTP client GET request to https://registry.terraform.io/v1/providers/-/xenorchestra/versions

Error: Failed to install provider

Error while installing hashicorp/xenorchestra: provider registry
registry.terraform.io does not have a provider named
registry.terraform.io/hashicorp/xenorchestra

@andbut I see the issue now. You have two parts of your code declaring the provider.
The first is the modern terraform syntax
terraform {
    required_providers {
        xenorchestra = {
            source = "terra-farm/xenorchestra"
            version = "0.9.1"
        }
    }
}

The second is legacy and should only be used if you are on a terraform version < 0.12
# Configure the XenServer Provider
provider "xenorchestra" {
    # Must be ws or wss
    url      = "ws://hostname-of-server" # Or set XOA_URL environment variable
    username = "<username>"              # Or set XOA_USER environment variable
    password = "<password>"              # Or set XOA_PASSWORD environment variable
}

Remove the second code block and your terraform init will run properly. Sorry for not catching that sooner as I was on mobile the first time and didn't see the duplicated block.
Closing this issue since this is not an issue with the provider.

Thanks for that - but please consider updating your Getting Started instructions accordingly, as I literally just copied it from there.

Sadly that still does not work - my config is now
terraform {
    backend "gcs" {
        bucket  = "<bucket_name>"
        prefix  = "<bucket_prefix>"
    }
    required_providers {
        xenorchestra = {
            source = "terra-farm/xenorchestra"
            version = "0.9.1"
            # I assume the below is still needed - else how do I configure the provider??
            url      = "ws://hostname-of-server" # Or set XOA_URL environment variable
            username = "<username>"              # Or set XOA_USER environment variable
            password = "<password>"              # Or set XOA_PASSWORD environment variable
        }
    }
}

But the issue still occurs
$ rm -rf .terraform
$ TF_LOG=trace terraform init
2020/11/25 08:47:15 [INFO] Terraform version: 0.13.5
2020/11/25 08:47:15 [INFO] Go runtime version: go1.15.3
2020/11/25 08:47:15 [INFO] CLI args: []string{"/usr/bin/terraform", "init"}
2020/11/25 08:47:15 [DEBUG] Attempting to open CLI config file: /home/andyb/.terraformrc
2020/11/25 08:47:15 [DEBUG] File doesn't exist, but doesn't need to. Ignoring.
2020/11/25 08:47:15 [DEBUG] ignoring non-existing provider search directory terraform.d/plugins
2020/11/25 08:47:15 [DEBUG] ignoring non-existing provider search directory /home/andyb/.terraform.d/plugins
2020/11/25 08:47:15 [DEBUG] ignoring non-existing provider search directory /home/andyb/.local/share/terraform/plugins
2020/11/25 08:47:15 [DEBUG] ignoring non-existing provider search directory /home/andyb/.local/share/flatpak/exports/share/terraform/plugins
2020/11/25 08:47:15 [DEBUG] ignoring non-existing provider search directory /var/lib/flatpak/exports/share/terraform/plugins
2020/11/25 08:47:15 [DEBUG] ignoring non-existing provider search directory /usr/local/share/terraform/plugins
2020/11/25 08:47:15 [DEBUG] ignoring non-existing provider search directory /usr/share/terraform/plugins
2020/11/25 08:47:15 [DEBUG] ignoring non-existing provider search directory /var/lib/snapd/desktop/terraform/plugins
2020/11/25 08:47:15 [INFO] CLI command args: []string{"init"}
Initializing modules...
2020/11/25 08:47:15 [TRACE] ModuleInstaller: installing child modules for . into .terraform/modules
2020/11/25 08:47:15 [DEBUG] Module installer: begin cloud-init
2020/11/25 08:47:15 [TRACE] ModuleInstaller: cloud-init is not yet installed
2020/11/25 08:47:15 [TRACE] ModuleInstaller: cleaning directory .terraform/modules/cloud-init prior to install of cloud-init
2020/11/25 08:47:15 [TRACE] ModuleInstaller: cloud-init has local path "../../modules/cloud-init"
2020/11/25 08:47:15 [TRACE] ModuleInstaller: cloud-init uses directory from parent: ../../modules/cloud-init
2020/11/25 08:47:15 [DEBUG] Module installer: cloud-init installed at ../../modules/cloud-init
2020/11/25 08:47:15 [TRACE] modsdir: writing modules manifest to .terraform/modules/modules.json
- cloud-init in ../../modules/cloud-init

Initializing the backend...
2020/11/25 08:47:15 [TRACE] Meta.Backend: built configuration for "gcs" backend with hash value<PHONE_NUMBER>
2020/11/25 08:47:15 [TRACE] Meta.Backend: backend has not previously been initialized in this working directory
2020/11/25 08:47:15 [DEBUG] New state was assigned lineage "bf08fb33-53ee-341b-7f57-dcec0acf937b"
2020/11/25 08:47:15 [TRACE] Meta.Backend: moving from default local state only to "gcs" backend
2020/11/25 08:47:15 [DEBUG] checking for provisioner in "."
2020/11/25 08:47:15 [DEBUG] checking for provisioner in "/usr/bin"
2020/11/25 08:47:15 [INFO] Failed to read plugin lock file .terraform/plugins/linux_amd64/lock.json: open .terraform/plugins/linux_amd64/lock.json: no such file or directory
2020/11/25 08:47:15 [TRACE] backend/local: state manager for workspace "default" will:
 - read initial snapshot from terraform.tfstate
 - write new snapshots to terraform.tfstate
 - create any backup at terraform.tfstate.backup
2020/11/25 08:47:15 [TRACE] statemgr.Filesystem: reading initial snapshot from terraform.tfstate
2020/11/25 08:47:15 [TRACE] statemgr.Filesystem: snapshot file has nil snapshot, but that's okay
2020/11/25 08:47:15 [TRACE] statemgr.Filesystem: read nil snapshot
2020/11/25 08:47:15 [TRACE] Meta.Backend: ignoring local "default" workspace because its state is empty
2020/11/25 08:47:15 [DEBUG] New state was assigned lineage "66a1ee50-b877-1fd8-bb63-f2e3df661d8d"
2020/11/25 08:47:15 [TRACE] Preserving existing state lineage "66a1ee50-b877-1fd8-bb63-f2e3df661d8d"

Successfully configured the backend "gcs"! Terraform will automatically
use this backend unless the backend configuration changes.
2020/11/25 08:47:16 [TRACE] Meta.Backend: instantiated backend of type *gcs.Backend
2020/11/25 08:47:16 [DEBUG] checking for provisioner in "."
2020/11/25 08:47:16 [DEBUG] checking for provisioner in "/usr/bin"
2020/11/25 08:47:16 [INFO] Failed to read plugin lock file .terraform/plugins/linux_amd64/lock.json: open .terraform/plugins/linux_amd64/lock.json: no such file or directory
2020/11/25 08:47:16 [TRACE] Meta.Backend: backend *gcs.Backend does not support operations, so wrapping it in a local backend
2020/11/25 08:47:17 [TRACE] providercache.fillMetaCache: scanning directory .terraform/plugins
2020/11/25 08:47:17 [TRACE] getproviders.SearchLocalDirectory: failed to resolve symlinks for .terraform/plugins: lstat .terraform/plugins: no such file or directory

2020/11/25 08:47:17 [TRACE] providercache.fillMetaCache: error while scanning directory .terraform/plugins: cannot search .terraform/plugins: lstat .terraform/plugins: no such file or directory
2020/11/25 08:47:17 [WARN] Failed to scan provider cache directory .terraform/plugins: cannot search .terraform/plugins: lstat .terraform/plugins: no such file or directory
2020/11/25 08:47:17 [DEBUG] Service discovery for registry.terraform.io at https://registry.terraform.io/.well-known/terraform.json
2020/11/25 08:47:17 [TRACE] HTTP client GET request to https://registry.terraform.io/.well-known/terraform.json
Initializing provider plugins...
- Finding latest version of hashicorp/xenorchestra...
2020/11/25 08:47:17 [DEBUG] GET https://registry.terraform.io/v1/providers/hashicorp/xenorchestra/versions
2020/11/25 08:47:17 [TRACE] HTTP client GET request to https://registry.terraform.io/v1/providers/hashicorp/xenorchestra/versions
2020/11/25 08:47:17 [DEBUG] GET https://registry.terraform.io/v1/providers/terra-farm/xenorchestra/versions
- Finding terra-farm/xenorchestra versions matching "0.9.1"...
2020/11/25 08:47:17 [TRACE] HTTP client GET request to https://registry.terraform.io/v1/providers/terra-farm/xenorchestra/versions
2020/11/25 08:47:18 [DEBUG] GET https://registry.terraform.io/v1/providers/terra-farm/xenorchestra/0.9.1/download/linux/amd64
2020/11/25 08:47:18 [TRACE] HTTP client GET request to https://registry.terraform.io/v1/providers/terra-farm/xenorchestra/0.9.1/download/linux/amd64
2020/11/25 08:47:18 [DEBUG] GET https://github.com/terra-farm/terraform-provider-xenorchestra/releases/download/v0.9.1/terraform-provider-xenorchestra_0.9.1_SHA256SUMS
2020/11/25 08:47:18 [TRACE] HTTP client GET request to https://github.com/terra-farm/terraform-provider-xenorchestra/releases/download/v0.9.1/terraform-provider-xenorchestra_0.9.1_SHA256SUMS
2020/11/25 08:47:18 [TRACE] HTTP client GET request to https://github-production-release-asset-2e65be.s3.amazonaws.com/175864600/b013b400-2917-11eb-958e-586925694118?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20201125%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20201125T084528Z&X-Amz-Expires=300&X-Amz-Signature=501191f5d9faf1952f833a31a20ef49172b94fb6c0fae67f4a696cf57c89b309&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=175864600&response-content-disposition=attachment%3B%20filename%3Dterraform-provider-xenorchestra_0.9.1_SHA256SUMS&response-content-type=application%2Foctet-stream
2020/11/25 08:47:18 [DEBUG] GET https://github.com/terra-farm/terraform-provider-xenorchestra/releases/download/v0.9.1/terraform-provider-xenorchestra_0.9.1_SHA256SUMS.sig
2020/11/25 08:47:18 [TRACE] HTTP client GET request to https://github.com/terra-farm/terraform-provider-xenorchestra/releases/download/v0.9.1/terraform-provider-xenorchestra_0.9.1_SHA256SUMS.sig
2020/11/25 08:47:18 [TRACE] HTTP client GET request to https://github-production-release-asset-2e65be.s3.amazonaws.com/175864600/a0946b00-2917-11eb-8643-983286645812?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20201125%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20201125T084529Z&X-Amz-Expires=300&X-Amz-Signature=832341e1f27f0427efcd69d96c1ba31a7a964cb87b39fdb3f4f6c92688a0b023&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=175864600&response-content-disposition=attachment%3B%20filename%3Dterraform-provider-xenorchestra_0.9.1_SHA256SUMS.sig&response-content-type=application%2Foctet-stream
2020/11/25 08:47:18 [TRACE] providercache.Dir.InstallPackage: installing registry.terraform.io/terra-farm/xenorchestra v0.9.1 from https://github.com/terra-farm/terraform-provider-xenorchestra/releases/download/v0.9.1/terraform-provider-xenorchestra_0.9.1_linux_amd64.zip
2020/11/25 08:47:18 [TRACE] HTTP client GET request to https://github.com/terra-farm/terraform-provider-xenorchestra/releases/download/v0.9.1/terraform-provider-xenorchestra_0.9.1_linux_amd64.zip
- Installing terra-farm/xenorchestra v0.9.1...
2020/11/25 08:47:19 [TRACE] HTTP client GET request to https://github-production-release-asset-2e65be.s3.amazonaws.com/175864600/a8eca600-2917-11eb-9709-924b9588e0ae?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20201125%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20201125T084529Z&X-Amz-Expires=300&X-Amz-Signature=1da93dba3ee72c83291fc786743491bdad85006a7330a54dd37a16a07d177471&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=175864600&response-content-disposition=attachment%3B%20filename%3Dterraform-provider-xenorchestra_0.9.1_linux_amd64.zip&response-content-type=application%2Foctet-stream
2020/11/25 08:47:28 [DEBUG] Provider signed by DDBA1674AA3EA0EE Dom Del Nano<EMAIL_ADDRESS>2020/11/25 08:47:29 [TRACE] providercache.fillMetaCache: scanning directory .terraform/plugins
2020/11/25 08:47:29 [TRACE] getproviders.SearchLocalDirectory: .terraform/plugins is a symlink to .terraform/plugins
2020/11/25 08:47:29 [TRACE] getproviders.SearchLocalDirectory: found registry.terraform.io/terra-farm/xenorchestra v0.9.1 for linux_amd64 at .terraform/plugins/registry.terraform.io/terra-farm/xenorchestra/0.9.1/linux_amd64
2020/11/25 08:47:29 [TRACE] providercache.fillMetaCache: including .terraform/plugins/registry.terraform.io/terra-farm/xenorchestra/0.9.1/linux_amd64 as a candidate package for registry.terraform.io/terra-farm/xenorchestra 0.9.1
2020/11/25 08:47:29 [TRACE] providercache.fillMetaCache: using cached result from previous scan of .terraform/plugins
- Installed terra-farm/xenorchestra v0.9.1 (self-signed, key ID DDBA1674AA3EA0EE)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/plugins/signing.html
2020/11/25 08:47:29 [DEBUG] GET https://registry.terraform.io/v1/providers/-/xenorchestra/versions
2020/11/25 08:47:29 [TRACE] HTTP client GET request to https://registry.terraform.io/v1/providers/-/xenorchestra/versions

Error: Failed to install provider

Error while installing hashicorp/xenorchestra: provider registry
registry.terraform.io does not have a provider named
registry.terraform.io/hashicorp/xenorchestra

Ok - I think I found the issue.
The problem is caused by me using modules - if I place the config block
terraform {
    required_providers {
        xenorchestra = {
            source = "terra-farm/xenorchestra"
            version = "0.9.1"
        }
    }
}

In both the terraform module - and the state file that uses the modules then init runs successfully
$ terraform init
Initializing modules...

Initializing the backend...

Initializing provider plugins...
- Using previously-installed terra-farm/xenorchestra v0.9.1

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Thanks for highlighting that the instructions are wrong. I've opened #93 to fix the documentation issue.
And yea for any module that references the provider you will need to add that block. Glad you got it working and thanks for improving the documentation of the project!


[BUG] [data plane] list parsing is not correctly

Describe the bug
value of sonata response property in list type is in strange format
 "tags": [         "\"\\\"offnet\\\"\"",         "\"\\\"free\\\"\""       ],
value from target side
    "tags": [       "offnet",       "free"     ],
Expected behavior
list parsing should be working normally

pass


Add 0.55 release notes

### Tasks
- [x] engineering release notes
- [x] release highlights

resolved in d4a3208 and f84459b


Use AD B2C and AAD with MVC 5 Owin

Hi, my app was built using MVC 5 and Owin, we added AD B2C and AAD to it, but today we are facing issues with refresh token. I added created an issue in the Katana repository. https://github.com/aspnet/AspNetKatana/issues/512
Now we are trying to update our code to use Microsoft.Identity.Web.OWIN and see if we can have those issues with refresh token fixed.
I was trying to follow this sample but I could not see how I could have configuration for both AD B2C and AAD for Web Application.
I see here that is not possible to use AD B2C in Web App with Owin https://github.com/AzureAD/microsoft-identity-web/issues/2312
Do you know how I could implement it? What is the recommendation?

Can you move to .NET? there we support both AAD and B2C side by side.


[Loc] update to xlfs for 2-23-2023

This PR fixes #

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 41.917%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
28691

Relevant Lines:
63557

💛  - Coveralls


nixos/nginx: revert config validation

Description of changes
Revert of https://github.com/NixOS/nixpkgs/pull/205561 (and https://github.com/NixOS/nixpkgs/pull/207532)
It is currently too fragile. We can workaround the weaknesses we know about (proposed in https://github.com/NixOS/nixpkgs/pull/207413 ) but I'm hesitated to go this way because it's arguably hacky. If we don't agree that we should go with https://github.com/NixOS/nixpkgs/pull/207413 by, say, the end of the month, let's just give up and revert.
cc nginx maintainers @thoughtpolice @fpletz @globin @ajs124 @7c6f434c
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@symphorien Can you fix the merge conflicts please?

done


subscription of "ietf-netconf-notifications" failed

Hi,
While running netopeeer2-server , I got below on netopeer2-server.So after doing make sr_clean and reinstall of netopeer ,it worked.
Since I was testing on x86 machine where the complete source code was also present, so I was able to clean the sysrepo and got rid off the issue.
My doubt is how to catch such  errors on real time while running on target where there will be no source code and how to clean the sysrepo.
[ERR]: SR: Waiting for subscription of "ietf-netconf-notifications" failed, previous event "notif" ID 1 was not processed. [WRN]: NP: Failed to send a notification (Timeout expired).
Regards
Biswajit

What netopeer2 version are you using?

I am using 2.2.19
$ Install/sbin/netopeer2-server -V
netopeer2-server 2.2.19

I see, ideally, these kinds of errors should not occur in the latest version. Without reproducing it, I will not be able to fix this. But I am working on improving and refactoring notification subscriptions currently, so it is possible it will still be fixed in the next release.

Hi,
Let me know if you need any other logs so that I can share next time whenever I will see the same issue.
Regards,
Biswajit

The only logs that could perhaps help are the full netopeer2-server logs (or not full but with logs in reasonable past before the error) with INF log level (-v2).

Hi,
Please find the forground logs collected during the execution of netopeer2-server below.
./netopeer2-server -d -v3 -p ~/temp.pid
[INF]: SR: Connection 40 created.
[INF]: SR: Session 125 (user "biswajit", CID 40) created.
[WRN]: SR: Connection with CID 27 is dead.
[WRN]: SR: Recovering RPC/action "/ietf-netconf:get-config" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/ietf-netconf:edit-config" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/ietf-netconf:copy-config" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/ietf-netconf:delete-config" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/ietf-netconf:lock" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/ietf-netconf:unlock" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/ietf-netconf:get" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/ietf-netconf:kill-session" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/ietf-netconf:commit" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/ietf-netconf:cancel-commit" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/ietf-netconf:discard-changes" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/ietf-netconf:validate" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/ietf-netconf-monitoring:get-schema" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/notifications:create-subscription" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/ietf-netconf-nmda:get-data" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/ietf-netconf-nmda:edit-data" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/ietf-subscribed-notifications:establish-subscription" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/ietf-subscribed-notifications:modify-subscription" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/ietf-subscribed-notifications:delete-subscription" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/ietf-subscribed-notifications:kill-subscription" subscription of CID 27.
[WRN]: SR: Recovering RPC/action "/ietf-yang-push:resync-subscription" subscription of CID 27.
[WRN]: SR: Recovering module "ietf-netconf-monitoring" operational get subscription of CID 27.
[WRN]: SR: Recovering module "nc-notifications" operational get subscription of CID 27.
[WRN]: SR: Recovering module "iana-ssh-public-key-algs" operational get subscription of CID 27.
[WRN]: SR: Recovering module "iana-ssh-key-exchange-algs" operational get subscription of CID 27.
[WRN]: SR: Recovering module "iana-ssh-encryption-algs" operational get subscription of CID 27.
[WRN]: SR: Recovering module "iana-ssh-mac-algs" operational get subscription of CID 27.
[WRN]: SR: Recovering module "ietf-subscribed-notifications" operational get subscription of CID 27.
[WRN]: SR: Recovering module "ietf-subscribed-notifications" operational get subscription of CID 27.
[INF]: SR: Triggering "ietf-netconf-server" "done" event on enabled data.
[INF]: LN: Call Home client "default-client" endpoint "default-tls" connecting...
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4335.
[INF]: LN: getsockopt() error (Connection refused).
[INF]: SR: Triggering "ietf-keystore" "done" event on enabled data.
[INF]: SR: Triggering "ietf-truststore" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-acm" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-acm" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-acm" "done" event on enabled data.
[INF]: SR: Triggering "ietf-netconf-acm" "done" event on enabled data.
[WRN]: SR: Recovering module "sysrepo-monitoring" operational get subscription of CID 27.
[INF]: LN: Call Home client "default-client" timeout of 5 seconds expired, reconnecting.
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4335.
[INF]: LN: getsockopt() error (Connection refused).
[INF]: LN: Call Home client "default-client" timeout of 5 seconds expired, reconnecting.
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4335.
[INF]: LN: getsockopt() error (Connection refused).
[INF]: LN: Call Home client "default-client" timeout of 5 seconds expired, reconnecting.
[INF]: LN: Call Home client "default-client" endpoint "default-tls" failed connection attempt limit 3 reached.
[INF]: LN: Call Home client "default-client" endpoint "default-tls" connecting...
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4335.
[INF]: LN: getsockopt() error (Connection refused).
[INF]: LN: Call Home client "default-client" timeout of 5 seconds expired, reconnecting.
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4335.
[INF]: LN: getsockopt() error (Connection refused).
[INF]: LN: Call Home client "default-client" timeout of 5 seconds expired, reconnecting.
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4335.
[INF]: LN: getsockopt() error (Connection refused).
[INF]: LN: Call Home client "default-client" timeout of 5 seconds expired, reconnecting.
[INF]: LN: Call Home client "default-client" endpoint "default-tls" failed connection attempt limit 3 reached.
[INF]: LN: Call Home client "default-client" endpoint "default-tls" connecting...
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4335.
[INF]: LN: getsockopt() error (Connection refused).
[INF]: LN: Call Home client "default-client" timeout of 5 seconds expired, reconnecting.
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4335.
[INF]: LN: getsockopt() error (Connection refused).
[INF]: LN: Call Home client "default-client" timeout of 5 seconds expired, reconnecting.
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4335.
[INF]: LN: Successfully connected to localhost:4335 over IPv4.
[INF]: LN: Cert verify: depth 1.
[INF]: LN: Cert verify: subject: /C=CZ/ST=South Moravia/L=Brno/O=CESNET z.s.p.o./OU=TMC/CN=example<EMAIL_ADDRESS>[INF]: LN: Cert verify: issuer:  /C=CZ/ST=South Moravia/L=Brno/O=CESNET z.s.p.o./OU=TMC/CN=example<EMAIL_ADDRESS>[INF]: LN: Cert verify CTN: entry with a matching fingerprint found.
[INF]: LN: Cert verify CTN: new client username recognized as "tls-test".
[INF]: LN: Cert verify: depth 0.
[INF]: LN: Cert verify: subject: /C=CZ/ST=South Moravia/L=Brno/O=CESNET<EMAIL_ADDRESS>[INF]: LN: Cert verify: issuer:  /C=CZ/ST=South Moravia/L=Brno/O=CESNET z.s.p.o./OU=TMC/CN=example<EMAIL_ADDRESS>[INF]: LN: Client certificate verified.
[INF]: LN: Session 1: Call Home client "default-client" session 1 established.
[INF]: SR: Session 135 (user "biswajit", CID 40) created.
[INF]: NP: Callhome data:1
[WRN]: SR: Connection with CID 38 is dead.
[WRN]: SR: Recovering module "ietf-netconf-notifications" notification subscription of CID 38.
[WRN]: SR: Recovering module "ietf-netconf-notifications" notification subscription of CID 38.
[WRN]: SR: Recovering module "ietf-netconf-notifications" notification subscription of CID 38.
[INF]: SR: EV ORIGIN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 1 priority 0 for 1 subscribers published.
[INF]: SR: EV LISTEN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 1 priority 0 processing (remaining 1 subscribers).
[INF]: NP: Module "ietf-datastores@" was requested.
[INF]: SR: EV LISTEN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 1 priority 0 success (remaining 0 subscribers).
[INF]: SR: EV ORIGIN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 1 priority 0 succeeded.
[INF]: NP: Session 1: thread 2 event new RPC.
[INF]: SR: EV ORIGIN: "/ietf-netconf:get" "rpc" ID 1 priority 0 for 1 subscribers published.
[INF]: SR: EV LISTEN: "/ietf-netconf:get" "rpc" ID 1 priority 0 processing (remaining 1 subscribers).
[INF]: SR: EV LISTEN: "/ietf-netconf:get" "rpc" ID 1 priority 0 success (remaining 0 subscribers).
[INF]: SR: EV ORIGIN: "/ietf-netconf:get" "rpc" ID 1 priority 0 succeeded.
[INF]: NP: Session 1: thread 0 event new RPC.
[INF]: SR: EV ORIGIN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 2 priority 0 for 1 subscribers published.
[INF]: SR: EV LISTEN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 2 priority 0 processing (remaining 1 subscribers).
[INF]: NP: Module "o-ran-wg4-features@2023-12-11" was requested.
[INF]: SR: EV LISTEN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 2 priority 0 success (remaining 0 subscribers).
[INF]: SR: EV ORIGIN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 2 priority 0 succeeded.
[INF]: NP: Session 1: thread 1 event new RPC.
[INF]: SR: EV ORIGIN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 3 priority 0 for 1 subscribers published.
[INF]: SR: EV LISTEN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 3 priority 0 processing (remaining 1 subscribers).
[INF]: NP: Module "o-ran-usermgmt@2023-12-11" was requested.
[INF]: SR: EV LISTEN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 3 priority 0 success (remaining 0 subscribers).
[INF]: SR: EV ORIGIN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 3 priority 0 succeeded.
[INF]: NP: Session 1: thread 1 event new RPC.
[INF]: SR: EV ORIGIN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 4 priority 0 for 1 subscribers published.
[INF]: SR: EV LISTEN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 4 priority 0 processing (remaining 1 subscribers).
[INF]: NP: Module "o-ran-supervision@2022-12-05" was requested.
[INF]: SR: EV LISTEN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 4 priority 0 success (remaining 0 subscribers).
[INF]: SR: EV ORIGIN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 4 priority 0 succeeded.
[INF]: NP: Session 1: thread 2 event new RPC.
[INF]: SR: EV ORIGIN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 5 priority 0 for 1 subscribers published.
[INF]: SR: EV LISTEN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 5 priority 0 processing (remaining 1 subscribers).
[INF]: NP: Module "notif-augment@" was requested.
[INF]: SR: EV LISTEN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 5 priority 0 success (remaining 0 subscribers).
[INF]: SR: EV ORIGIN: "/ietf-netconf-monitoring:get-schema" "rpc" ID 5 priority 0 succeeded.
[INF]: NP: Session 1: thread 1 event new RPC.
[INF]: SR: EV ORIGIN: "/ietf-netconf:get" "rpc" ID 2 priority 0 for 1 subscribers published.
[INF]: SR: EV LISTEN: "/ietf-netconf:get" "rpc" ID 2 priority 0 processing (remaining 1 subscribers).
[INF]: SR: EV LISTEN: "/ietf-netconf:get" "rpc" ID 2 priority 0 success (remaining 0 subscribers).
[INF]: SR: EV ORIGIN: "/ietf-netconf:get" "rpc" ID 2 priority 0 succeeded.
[INF]: NP: Session 1: thread 1 event new RPC.
[ERR]: SR: Waiting for subscription of "ietf-netconf-notifications" failed, previous event "notif" ID 4 was not processed.
[WRN]: NP: Failed to send a notification (Timeout expired).
`

Please use the latest releases and try again, the changes I have mentioned before have been finished.


Swift 4 support

For some reason Im not able to pull the Swift4 version support on Pod install.. the version I’m pulling has an issue calling UIView.layer not in the main Thread.. can you provide advice ?

Not related to the library, was and old lock,. my mistake


Add X btn

connects unicef/etools-issues#412

Closing because during the redesign a button was added so this is not needed anymore


To make better use of JSON, use the $type signifier instead of a prefix

Newtonsoft JSON supports a special $type property in a serialized JSON string.  Where this is present it tells the serializer which object type to choose when deserializing.  This is exactly what the current type prefix does.
The type-selection functionality could easily be rolled-into the JSON serialization process and removed from the main logic.

In fact, this need not be a breaking change, if handled properly.
The logic to detect and parse prefixed JSON may remain, for backwards compatibility.  It would only be used when prefixed JSON is detected, though.
When writing any credentials, the new style would be used, but when reading them, either old or new styles may be used, based on detection.
Strictly speaking, this is a backwards-compatible change, but not a forwards-compatible one. Because old versions won't be able to read the output of later versions, the upgrade will be forward-only. I think that this is good enough not to need to release a new major version, though.


bytesToString returns an invalid value

When I try to convert the payload of a tag, this comes back to me two initial additional characters en.
I write in this way:
nfc.write([
      ndef.textRecord('1234'),
      ndef.textRecord('John')
      ],
      (d) => console.log('done write', d),
      (e) => console.log('errr write', e));

when I read the tag with bytesToString back to me:
nfc.bytesToString(tag.ndefMessage[0].payload) // return "en1234"
nfc.bytesToString(tag.ndefMessage[1].payload) // return "enJohn"

It is not a problem writing, in fact when I read the tag with the native reader returns the correct values!

You are seeing the correct behavior for an NDEF message with TNF well known, RTD text. The payload has multiple bytes prepended to the text. The first byte is the length of the language code, the next 2 bytes are the language code. Your text begins at the 4th byte.
payload = [0x02, 'e', 'n', 'J', 'o', 'h', 'n' ]
If you know all your messages have a 2 letter language code, slice the array to remove the length and language code.
nfc.bytesToString(ndefMessage[0].payload).substring(3))

A better way to do this is to check the length of the language code and remove it.
languageCodeLength = ndefMessage[0].payload[0]
nfc.bytesToString(ndefMessage[0].payload).substring(languageCodeLength +  1))


[Wait for #2342] [ Weight ] Add packed property and output axis in weight spec

In This PR includes,
. enable packed (bool) property for layer node. It is only for the
weight. If it is false, it follows the global activation datatype; if it is true,
it will follow the global weight datatype.
. add output axis in Weight Spec and set the private variable in weight.
it is to find the right direction for multiplying scales and zero-point
Self evaluation:

Build test:	 [X]Passed [ ]Failed [ ]Skipped
Run test:	 [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: jijoong.moon<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2343. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

:octocat: cibot: @jijoongmoon, nntrainer/layers/common_properties.h does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md


Correctly add STREAM_WEIGHT header in InboundHttp2ToHttpAdapter.onPus…

…hPromiseRead(...)
Motivation:
The weight header with the default value is not set but it should be (rfc7540#5.3.5: …Pushed streams initially depend on their associated stream … are assigned a default weight of 16).
Modifications:
Add STREAM_WEIGHT header.
Result:
Correctly add headers.

@Scottmitch @nmittler PTAL... Was reported here: https://github.com/netty/netty/pull/5879#pullrequestreview-2358040

Also @evgenyvsmirnov

I'm not against this PR (or https://github.com/netty/netty/pull/5879) but I'm not sure how much effort we should spend priority/dependency in the HTTP/1<->HTTP/2 conversion layer as it doesn't really fit well into the HTTP/1.x lifecycle. It was originally just provided for informational purposes and the contract was if you needed more visibility you would drop down the the raw HTTP/2 API.

LGTM

@Scottmitch yeah... that said this one was easy and I think it is more correct now. Let me merge it.

Cherry-picked into 4.1 (be8b6c6f24e21eb8704720200b84a4a9c8b0ce9f)


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/opstest2/docs-archive-test-source.git

Docs Build status updates of commit 64c7534:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


[WIRES] Implement wires refactor

This PR makes the qiskit device compatible with the PennyLane master after the wires refactor was merged.

@mariaschuld looks like the TestWiresIntegration test in the shared plugin test suite is failing 🙁


Add Alibaba Cloud to ip ranges

At least this one
https://ipinfo.io/AS45102/<IP_ADDRESS>/17
has been crawling, ignoring robots.txt, and using a non-bot user agent header :angry:

FWIW in my code I put
	if strings.HasPrefix("47.76", caddyLog.Request.GetRemoteIP()) {
		return 16 // 16: alibaba cloud
	}


fishPlugins.sponge: init at 1.1.0

Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

It doesn't seem to work on my end.
Did I forget to configure something? Or should I open an issue here?

are you sure? no you don't need to configure anything

Yes: no matter how wrong failing commands I input, they all stay in the history.
I added the plugin through environment.systemPackages, just like the other ones (and these other ones work).

In order for Sponge to work, I have to manually call _sponge_on_prompt.

ok, i actually got it working by setting set sponge_allow_previously_successful false, otherwise sponge would just remove all my new history
i actually stopped using sponge after a while, because i ran into the same problem of it removing all new history and i didn't find it that useful after all, because even before it started removing all new history, it annoyed me more than feeling useful
maybe sponge is a bit buggy 😬


How to get  astro-i18next to work in React Components inside Astro

What works inside .astro components  doesn't in React components  (.tsx) in SSR mode.
Is there any plan to make it work ? or some work around ?

Hey, thanks for the issue. I've setup an example for react using the react-i18next plugin. https://stackblitz.com/edit/github-xdzdkv?file=src/components/Counter.tsx
It doesn't work because i18next is only initialized server side.
Getting these errors:

So when using the client:visible directive, the react component cannot locate the translation string. astro-i18next may need to load i18next both on client and server side.

astro-i18next may need to load i18next both on client and server side.

Any ideas on how to achieve this?

And also, what about other frameworks like solidjs etc?

Any ideas on how to achieve this?

I've started implementing client side translations, I've created some example folders on the develop branch (including react). Trying things out for now.

And also, what about other frameworks like solidjs etc?

I think my experimenting with react will solve the same issues for other frameworks. Basically, frameworks render client side js, so the i18next instance should exist client side as well to retrieve translation keys.
It's not ideal to have all translations handled client side in my opinion because it would hurt SEO. So I'll have to think of ways to make SSR and client side rendering work together for i18n.
I have some questions that need more investigating:

Would SSR and client side i18next instances share the same config? Same plugins?
Should they both load the same translation keys? (some keys are likely to be used only on SSR, and others for client side)

Anyways, thank you for your interest. If you have any insight, I'm all ears!

On astro docs website, they create dedicated pages for each translation (using md files). Only the UI part that using the translation key. And I will follow that convention.


Update to include nuget-validation build.cake

fixes #723

OPS Build status updates of commit 101765e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

build.cake
:white_check_mark:Succeeded

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

OPS Build status updates of commit 5c8a044:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

build.cake
:white_check_mark:Succeeded

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

OPS Build status updates of commit 37e6173:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

build.cake
:white_check_mark:Succeeded

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

OPS Build status updates of commit 37e6173:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

build.cake
:white_check_mark:Succeeded

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

OPS Build status updates of commit 87c809c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

build.cake
:white_check_mark:Succeeded

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

OPS Build status updates of commit 8dd2448:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

build.cake
:white_check_mark:Succeeded

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


Add test_mlir_execution.py

Test plan: python3 -m pytest -s test/test_mlir_execution.py

Cool!
Did a first pass; will review more at home. I have to leave to pickup my son shortly


Prefetch / Despawn Systems

Changing the purpose of this to just be for despawning. Prefetching camera translates is #40, and camera radius is #48.

This ticket is cursed. We need it back for both pre-fetch and despawn 🤦♂


No issue: made a script to switch cameras and a new overlay

So, I have a Chevrolet Volt, which has pretty poor vision to the front.
I wanted to be able to switch camera's when I need to park.
I copied the cam_overlay folder and changed the names of the folder and bin file to some thing with rearcam and frontcam.
I made these overlays.
Frontcam overlay

Rearcam overlay

Illustration of the buttons the script makes

Bash Script
#!/bin/bash
device='/dev/input/event0'

coord_x_check='*type 3 (EV_ABS), code 0 (ABS_X), value*'
coord_y_check='*type 3 (EV_ABS), code 1 (ABS_Y), value*'
running_cam=1
echo "Rearcam activated on default"
~/rearcam_overlay/bin/rearcam.bin -d /dev/v4l/by-id/usb-ARKMICRO_USB2.0_PC_CAMERA-video-index0 &
sudo evtest "$device" | while read line; do
    case $line in
        ($coord_x_check)    x=$(echo $line | awk -F value '{ print $2 }' | tr -dc '0-9');;
        ($coord_y_check)    y=$(echo $line | awk -F value '{ print $2 }' | tr -dc '0-9')
        if (( $x>=1920 && $y<=850 && $running_cam==1 ));
        then
                echo Rearcam deactivated
                killall -wq rearcam.bin &

                echo Frontcam activated X $x  Y $y
                ~/frontcam_overlay/bin/frontcam.bin -d /dev/v4l/by-id/usb-ARKMICRO_USB2.0_PC_CAMERA-video-index0 &
                running_cam=2
                sleep 1
        elif (( $x>=1920 && $y<=850 && $running_cam==2 ));
        then
                echo Frontcam is running allready
        elif (( $x<=1919 && $y<=850 && $running_cam==2 ));
        then
                echo Frontcam deactivated
               killall -wq frontcam.bin &
                echo Rearcam activated X $x Y $y
                ~/cam_overlay/bin/rearcam.bin -d /dev/v4l/by-id/usb-ARKMICRO_USB2.0_PC_CAMERA-video-index0 &
                running_cam=1
                sleep 1
        elif (( $x<=1919 && $y<=850 && $running_cam==1 ));
        then
                echo Rearcam is running allready
        elif (( $y>850 && $running_cam==1 ));
        then
                echo Camview deactivated X $x Y $y
                killall -wq rearcam.bin
                killall -wq test-2.sh
                exit 1
        elif (( $y>850 && $running_cam==2 ));
        then
                echo Camview deactivated X $x Y $y
                killall frontcam.bin &
                killall camview.sh    #this script
                exit 1

        fi
        ;;
    esac
sleep 0.1
done

You should find out using evtest what the min X & Y values and max X & Y values are. Also check where you like to have the buttons and check the values. Use them in this script.

Nice little script. I'm sure others will appreciate this.


Tests fail only during package upload - "CalloutException uncommitted work pending"

A problem probably connected to a recent system change (Winter '18 release?) makes the upload of packages fail that contain the MetadataService fail with
MetadataServiceTest.coverGeneratedCodeFileBasedOperations1 | System.CalloutException: You have uncommitted work pending. Please commit or rollback before calling out | Class.NS.MetadataService.MetadataPort.retrieve: line 11450, column 1 Class.NS.MetadataServiceTest.coverGeneratedCodeFileBasedOperations1: line 97, column 1
MetadataServiceTest.coverGeneratedCodeFileBasedOperations2 | System.CalloutException: You have uncommitted work pending. Please commit or rollback before calling out | Class.NS.MetadataService.MetadataPort.deleteMetadata: line 11320, column 1 Class.NS.MetadataServiceTest.coverGeneratedCodeFileBasedOperations2: line 117, column 1
The same problem occurs in the ToolingApi Wrapper by Andy Fawcett.

I also posted this on StackExchange https://salesforce.stackexchange.com/questions/196996

Solved in https://salesforce.stackexchange.com/questions/196996 by the great @BritishBoyinDC and Uwe Heim. I will submit a PR that fixes that.


Private field member value assignment's of child classes should occur before super call

Suggestion
Fields marked with the "private" keyword in child classes should have their initialization (if an inline assignment is provided) occur before the super call in the emitted JS.
such as:
private _field: string = 'Test';

🔍 Search Terms
child private field assignment initialization before super call
✅ Viability Checklist

My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[ ] This wouldn't change the runtime behavior of existing JavaScript code
[ ] This could be implemented without emitting different JS based on the types of the expressions
[ ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

📃 Motivating Example
Currently I am extending a class from an imported npm library, which I would rather not touch the code of directly, whether through a fork or local code edit. The issue being that I need to override methods and accessors from the base class in the library while utilizing my own child class's private fields in these methods and accessors. The accessors and methods I am overriding are called directly in the parent class's constructor. This is an issue because my field initializations do not occur until after the super call in the emitted code. The only way around this would to check if the field value is set in the getter of the property, and assign the default value, while also assigning the default value inline at the definition or in the constructor after the super call, which is necessary as i have the '"strictPropertyInitialization": true' TS config compiler option set.
See the simple typescript playground example outlining the issue (open browser console to see the error)
Simple TS Playground Example Using TS v4.1.3
💻 Use Cases
As said above in the motivating example, more accurately, I am using an angular component library and extending a component to use my stateChanges RXjs Subject to detect changes inside relevant display related property setters, in order to refresh the view with up-to-date values (for reference I am using the OnPush change detection strategy).
Having to work around this by both checking for set values in getters and assigning a default value elsewhere, is quite ugly and inconvenient.
If there is an easier/ cleaner workaround, great, but for now I think the best would be to have child private field assignments occur before super calls. This would not cause any adverse side-effects that I can think of with existing typescript code, as derived classes cannot have same named property declarations.

This is not going to happen. JavaScript disallows access to this before super() is called. Therefore it's impossible to initialize instance properties before the super constructor is executed.

This is not going to happen. JavaScript disallows access to this before super() is called. Therefore it's impossible to initialize instance properties before the super constructor is executed.

Quite unfortunate, because it limits overriding quite a bit, if the super() call relies on overridden members. As a side note a cleaner looking workaround I've come up with to satisfy "strictPropertyInitialization" is to initialize the field with null and only use the accessors internally:
// Simple Type Example
private _simpleField: string | null = null;

get simpleProperty(): string {
  if (this._simpleField === null) {
    this._simpleField = "Default Value";
  }

  return this._simpleField!;
}

set simpleProperty(value: string) {
  this._simpleField = value;
}

// Complex Type Example
private _complexField: ComplexType | null = null;

get complexProperty(): string {
  if (this._complexField === null) {
    this._complexField = new ComplexType();
  }

  return this._complexField!;
}

Quite unfortunate, because it limits overriding quite a bit, if the super() call relies on overridden members. As a side note a cleaner looking workaround I've come up with to satisfy "strictPropertyInitialization" is to initialize the field with null and only use the accessors internally:
// Simple Type Example
private _simpleField: string | null = null;

get simpleProperty(): string {
  if (this._simpleField === null) {
    this._simpleField = "Default Value";
  }

  return this._simpleField!;
}

set simpleProperty(value: string) {
  this._simpleField = value;
}

// Complex Type Example
private _complexField: ComplexType | null = null;

get complexProperty(): string {
  if (this._complexField === null) {
    this._complexField = new ComplexType();
  }

  return this._complexField!;
}

As @ajafff noted, this is literally impossible.

As @ajafff noted, this is literally impossible.


incompatible with socket.io@3 and @4 - Exception thrown "TypeError: Cannot read property 'on' of undefined"

The socket.io probe https://github.com/RuntimeTools/appmetrics/blob/master/probes/socketio-probe.js works fine with socket.io@2
However socket.io was rewritten for it's v3 and v4. The socket.io interface has changed slightly, causing the following exception to be thrown when socket.io is require'd and the probe attempts to hook in:
FATAL Node server exiting due to exception: TypeError: Cannot read property 'on' of undefined
                        at C:\firefly\repos\firefly-ui\node_modules\appmetrics\lib\aspect.js:56:26
                        at Array.forEach (<anonymous>)
                        at Object.exports.before (C:\firefly\repos\firefly-ui\node_modules\appmetrics\lib\aspect.js:55:9)
                        at SocketioProbe.attach (C:\firefly\repos\firefly-ui\node_modules\appmetrics\probes\socketio-probe.js:79:12)

I've done a little debugging and can see:

socket.io@2 exports a function with a prototype containing the methods the probe wants to patch.

socket.io@4 exports a factory function. The class is available as as export .Server (ie  requre('socket.io').Server) however it's now a proper javascript Class, and it's constructor can't be hooked in the way used previously.

Until this is fixed. is there any way to prevent the socket.io probe from installing? We only use data from other probes.

Does https://github.com/RuntimeTools/appmetrics#appmetricsdisabletype work?

appMetrics.disable('socketio') doesn't help. It looks to me that all probes are installed very early, by the appmetrics index.js, and whether a probe is disabled doesn't affect it attempting to hook in during the require of the target library.
Our code is approximately:
    appMetrics = require('appmetrics')
    appMetrics.configure({ mqtt: 'off' })
    const appMetricsMonitor = appMetrics.monitor()
    appMetrics.disable('socketio')

    // ... later ...
    require('socket.io')

Same issue, I need socket.io v3, and that impedes me to use appmetrics-dash due to this issue with appmatrics. I used it in the past, before using v3, and I'd like to continue...
Has this problem been acknowledged by the devs?

If you require socket.io BEFORE appmetrics then it will not be instrumented by appmetrics regardless of the later disable call.


Improve witness testing feedback and documentation

Description:
I've encountered an issue with the witness testing process in zkit. Currently, there's a lack of clear feedback when running tests, which makes it difficult to determine if tests have passed or failed.
Current Behavior:

There's no output related to test results when running npx hardhat zkit make.
Even when asserting false in a test file, the console doesn't indicate a failed test.

Expected Behavior:

Clear console output indicating whether tests have passed or failed.
Detailed error messages for failed assertions.
Documentation or examples showing how to interpret test results.

Steps to Reproduce:

Create a test file with an intentionally failing assertion.
Run npx hardhat zkit make.
Observe the lack of feedback about the failed test.

Example
import { zkit } from "hardhat"; // hardhat-zkit plugin
import { expect } from "chai"; // chai-zkit extension
import { IntergerDivision } from "@zkit"; // zktype circuit-object
async function main() {
  const circuit: IntergerDivision = await zkit.getCircuit("circuits/interger_division.circom:IntergerDivision");
  await expect(circuit)
    .with.witnessInputs({ a: "4", b: "2" })
    .to.have.witnessOutputs({ c: "2" });
  const proof = await circuit.generateProof({ a: "4", b: "2" });
  expect(await circuit.verifyProof(proof)).to.be.false; //@dev here it should fail because the results are true
}

main()
  .then()
  .catch((e) => console.log(e));

Hey, @Brianspha, npx hardhat zkit make command only launches circuits compilation and generation of zkeys. In order to run the test, you need to execute it through hardhat separately. Use npx hardhat run <your file> or npx hardhat test if you are using mocha.

Clarified the plugin usage section in hardhat-zkit readme.


Fixing mistaken erasure of effectful type applications

Fixes issue #3473
An effectful polymorphic function f at type a:Type -> Dv t was typed in the ML extraction as unit -> t.
This fix types it now as unit -Impure-> t, ensuring that an application  f a is extracted as f () with effect Impure and so is ineligible for erasure, even if t is an erasable type.

I have a check-world green with this: https://github.com/FStarLang/FStar/actions/runs/11153756864


#35000 GestureDetector problem

the red Container GestureDetector can not catch tap event
import 'package:flutter/material.dart';

class DemoOnePage extends StatefulWidget {
  DemoOnePage({Key key}) : super(key: key);

  @override
  createState() => DemoOnePageState();
}

class DemoOnePageState extends State<DemoOnePage> {

  @override
  void initState() {
    super.initState();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: Text("demo"),),
      body: _build(context)
    );
  }

  _build(BuildContext context) {
    return Container(
      color: Colors.yellow,
      width: 300,
      height: 300,
      child: Center(
        child: GestureDetector(
          onTap: () {
            print(" green is tapped ");
          },
          child: Container(
            color: Colors.green,
            width: 50,
            height: 50,
            child: Stack(
              overflow: Overflow.visible,
              children: <Widget>[
                Positioned(
                  left: -50,
                  top: 0,
                  child: GestureDetector(
                    behavior: HitTestBehavior.opaque,
                    onTap: () {
                      print("tap....");
                    },
                    onPanDown: (DragDownDetails details) {
                      print("onPanDown....");
                    },
                    child: Container(
                      width: 50,
                      height: 50,
                      color: Colors.red,
                    ),
                  ),
                )
              ],
            ),
          ),
        )
      ),
    );
  }

}

[✓] Flutter (Channel master, v1.15.3-pre.17, on Mac OS X 10.15.1 19B88, locale zh-Hans-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[!] Xcode - develop for iOS and macOS (Xcode 11.3)
✗ CocoaPods installed but not working.
You appear to have CocoaPods installed but it is not working.
This can happen if the version of Ruby that CocoaPods was installed with is different from the one being used to invoke it.
This can usually be fixed by re-installing CocoaPods. For more info, see https://github.com/flutter/flutter/issues/14293.
To re-install CocoaPods, run:
sudo gem install cocoapods
[✓] Chrome - develop for the web
[✓] Android Studio (version 3.5)
[✓] VS Code (version 1.42.1)

Hi @wasabia
Running your code
Definitely an issue, GestureDetector inside Stack doesn't get detected.

Thank you

Duplicate of https://github.com/flutter/flutter/issues/19445.


Bancor Price Integration

This is issue has been a sage and you can read the comments below to follow that saga. Hopefully, this can be solved.  We want to get bancor prices in this aggregator in a similar way to how we have gotten Uniswap and Kyber price discovery going on. You can see the latest work in the develop branch with this contract: https://github.com/ProofSuite/OrFeedSmartContracts/blob/develop/contracts/multiexchangewithbancordraft.sol
If you have questions, Gitcoin doesn't have messaging yet so you can message me on telegram @mikeproof
Previous post:
So far, OrFeed supports pricing data sources such as Kyber and Uniswap. One of the most liquid decentralized exchanges is  Bancor (this was formerly for IDEX but please see the first few comments below).
In contracts/draftpremium (https://etherscan.io/address/0x5e00a16eb51157fb192bd4fcaef4f79a4f16f480#code), we should add the option for sending the venue paramter of "BUX-IDEX-EXCHANGE" and "SELL-IDEX-EXCHANGE"  to the getExchangeRate function so that users can get pricing data like they can when sending a venue parameter of "BUY-KYBER-EXCHANGE"
This is referenced by the proxy contract (main orfeed aggregator contract) and can be updated, so once this new contract is ready, we can point it here, so that users and smart contracts can then start getting IDEX pricing data synchronously, and this whole thing can be more of an aggregator :)

Hi, @mikedeshazer! Just a few comments on your bounty description. I thought it would be easy as chat to implement this, but, I realised it makes no sense to query IDEX prices, since you have to know the address of the maker. IDEX is not a liquidity pool (like Uniswap, or Kyber) hence, no "price" for a token in exchange for another. Instead, just like ForkDelta or RadarRelay, you need to know the address of the maker of the order to get his price, which is not under the scope of your application, as I understand.

@uivlis good point. I have looked into the issue and it seems you are right. I will update this issue to Bancor.

@uivlis I fixed a few errors and deployed your contract here: https://etherscan.io/address/0x90d6d0c22673ca6fb269b3c918ad025654b24c81#code
I tested it, however, it does not work. I'm assuming it has to do with the contract address you are using or the PATH... perhaps its that the smart tokens have unique addresses and perhaps you need that based on the token.

I added further notes to the issue here:
https://github.com/ProofSuite/OrFeedSmartContracts/blob/develop/contracts/multiexchangewithbancordraft.sol
In the develop branch

Not sure if this will be incredibly useful but found this https://github.com/bancorprotocol/contracts/issues/282

Check this comment: https://github.com/bancorprotocol/contracts/issues/282#issuecomment-562046437

@uivlis deployed your solution here: https://etherscan.io/address/0x253b6f3e72d504f550ff04fec1d467d9459cd8cb#readContract
From the recent pull request. Still does not seem to work
Perhaps @k06a comment share will help
I can certainly say, once this problem is solved, will probably save alot of people headaches.

Third party oracle integrated via the registry.
Example call on mainnet:
uint price = orfeed.getExchangeRate("ETH", "DAI", "BANCOR",<PHONE_NUMBER>000000);


metadata: Add arch label

Signed-off-by: Kemal Akkoyun<EMAIL_ADDRESS>Why?

What?

🤖 Generated by Copilot at 560d61a
Add "arch" label to parca-agent metadata and refactor metadata collection. This change uses a new kernel.Machine function to get the architecture information and adds TODO comments to Java function in pkg/metadata/java.go for future improvements.
How?

🤖 Generated by Copilot at 560d61a

Add architecture information to the metadata labels of the parca-agent (link, link, link, link)

Define a new function Machine in the kernel package that returns the machine string of the current kernel using syscall.Uname (link)
Declare a variable architecture in the setMetadata function in the system package and initialize it to "unknown" (link)
Call the Machine function and assign its result to architecture if no error occurs (link)
Add the architecture variable as a value for the "arch" key in the label set returned by setMetadata (link)

Add TODO comments to the Java function in the metadata package to indicate future improvements for the caching logic (link, link)

Suggest moving the caching logic to the metadata layer instead of the profile layer (link)
Suggest caching the whole label set instead of individual values (link)

Test Plan

Nice one!


feat: register token refresh callback

Description
Depends on: https://github.com/snyk/go-application-framework/pull/54 (which depends on https://github.com/snyk/go-application-framework/pull/51)
Language Server must notify its client when a token is refrefreshed. With this PR, it registers a custom token refresher func in Go Application Framework that adds credential updates to Language Server on token refresh.
Checklist

[x] Tests added and all succeed
[x] Linted
[ ] README.md updated, if user-facing
[ ] License file updated, if new 3rd-party dependency is introduced

Screenshots / GIFs
Visuals that may help the reviewer. Please add screenshots for any UI change. GIFs are most welcome!

Closed as I merged these commits to the other PR because of the bug fixes implemented there


chore: add dependabot configuration for GitHub actions

Note: this should help fix CI/CD warnings such as:
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3.
For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

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

0 of 0   changed or added relevant lines in 0 files are covered.
8 unchanged lines in 6 files lost coverage.
Overall coverage decreased (-0.05%) to 90.432%

Files with Coverage Reduction
New Missed Lines
%

components/renku_data_services/base_api/auth.py
1
89.61%

components/renku_data_services/base_api/error_handler.py
1
90.28%

components/renku_data_services/secrets/db.py
1
91.92%

components/renku_data_services/storage/blueprints.py
1
94.65%

components/renku_data_services/base_api/pagination.py
2
87.72%

components/renku_data_services/crc/models.py
2
84.91%

Totals

Change from base Build<PHONE_NUMBER>1:
-0.05%

Covered Lines:
9026

Relevant Lines:
9981

💛  - Coveralls


How to fail .netcore2.0 build on stylecop warnings

Is there a way to make the build fail on warning?
I can update ruleset and make all rules action="Error" but that is very tedious.

You can turn on Treat Warnings as Errors, but make sure to only do so for command line builds:
https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/2592d5b3572490da5196dd730af95882348f9565/StyleCop.Analyzers/Directory.Build.props#L25-L28

Can we do this at solution level or pass it as additional parameter ?