Yi Pro 2K Home (YFUS) RTSP not working

Hello,
I formatted the SD card and used the newest release, but the RTSP stream is not working. No HD, no low quality.
VLC shows black and no stream and same with Blue Iris.
I tried the standarf RTSP mode and the alternative, no difference.
The only thing I also noticed is that low quality snapshot shows empty white page, high resolution snapshot is working.
Firmware Version | 0.3.2
Base Version | <IP_ADDRESS>_202403081746
Model Suffix | y623
Serial Number | YFUSY94I*************
This is not the first time I have used firmware from your project, on the 1080p model it worked straight away and without any problems.

I have the same problem.

Same problem for me

Workaround:
https://github.com/roleoroleo/yi-hack-Allwinner-v2/issues/915

Same problem for me.
Edit: I disabled the Screenshot mode and everything what I did not need. After this I enabled both streaming modes + sound and reboot the camera. Now it works for me with both streams.

I enabled RTSP Stream for both, RTSP Audio to pcm, disabled snapshot and onvif and now it is also working for me.

y623 is a problem for me.
There is something that I don't understand...

Similar problem with this camera.
YFUSY94P.....
<IP_ADDRESS>_202303091901
Stream and Snapshot is not working after couple minutes running.

Same problem for me.
Edit: I disabled the Screenshot mode and everything what I did not need. After this I enabled both streaming modes + sound and reboot the camera. Now it works for me with both streams.

I enabled RTSP Stream for both, RTSP Audio to pcm, disabled snapshot and onvif and now it is also working for me.

Not working for me.

Are you using my custom integration for HA?
Check the HA registry, are there error messages?

Are you using my custom integration for HA? Check the HA registry, are there error messages?

2024-09-14 19:18:35.702 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.yi_hack_a2_########_cam] Error from stream worker: Error opening stream (ERRORTYPE_111, Connection refused<EMAIL_ADDRESS>After reboot it works couple minutes.
i censored

I flashed my YFUS camera with firmware 0.3.2 and can access the webserver but rtsp isn't working. I've disabled snapshot and ONVIF and enabled hi & lo resolution streams. I've also tried it with and without the alternative rtsp server but still nothing. Any ideas?

Another one... YFUS 0.3.2, webserver is up but no rtsp... Tried all suggestions but not working...
@dwl99 by hard reboot you mean reset?

Please, test this beta:
y623_0.3.2.tgz

Thank you roleoroleo. Woks just fine.
I figured out what my issue was when I formated the SD card from within the app and reloaded the original hack. Works like a charm. Great job

Please, test this beta: y623_0.3.2.tgz

With this version I have no RTSP stream at all. With the original 0.3.2 version, the stream is there for about 10 to 30 seconds and then I got a timeout for 1 - 2 minutes and then the stream is back for again 10 to 30 seconds.
With the same settings, I have about 20000kb free memory with the patched (not working) version and about 8000kb free memory with the original version.

Check this post:
https://github.com/roleoroleo/yi-hack-Allwinner-v2/issues/753#issuecomment-2438422971


Multi language support

Summary
Multi language support
Chinese support
Use Cases
When would you use this?
Next two months

Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

Sure. I'd be happy on this.

Yea let's close this one out as duplicate since #10103 has more details. Can continue discussion there.


Support for libp2p Private Networks

Following https://github.com/libp2p/specs/pull/10

Support for private networks released in 0.23.0

Woooot! Awesome work!!


Patch 4.9

Please could you update it to patch 4.9 please thank you

Thanks for waiting. Here's the 4.9.0 wallpapers
https://github.com/paulo-iona/lor-wallpaper-downloader/releases/tag/4.9.0


@babel/runtime in dependencies

Is it intentional in package.json that @babel/runtime is in dependencies as opposed to devDependnencies?

@gwilson2151 Yes. Babel runtime is a collection of reusable helpers. It allows to prevent inlining of these helpers in each file. This package can be even reused across many packages so you don't loose anything with it.
<EMAIL_ADDRESS>

OK, just confused that a babel package showed up in our lock file when we don't use babel.


Add "spaceAround" rules for standard expressions

This tool looks great, but I found it lacking some of the general expression spacing rules that I use. I've added the following rules (with examples):
// arguments.spaceAround
foo("bar", true); // before
foo( "bar", true ); // after

// arrayExpression.spaceAround
const arr = [1, 2, 3]; // before
const arr = [ 1, 2, 3 ]; // after

// arrayPattern.spaceAround
const [first, second] = arr; // before
const [ first, second ] = arr; // after

// doWhileStatement.spaceAround
do {} while (true); // before
do {} while ( true ); // after

// forInStatement.spaceAround
for (const foo in bar) { // before
for ( const foo in bar ) { // after

// forOfStatement.spaceAround
for (const foo of bar) { // before
for ( const foo of bar ) { // after

// forStatement.spaceAround
for (let i = 0; i < 100; i++) { // before
for ( let i = 0; i < 100; i++ ) { // after

// ifStatement.spaceAround
if (true) { // before
if ( true ) { // after

// parameters.spaceAround
function foo(a: number, b: boolean) { // before
function foo( a: number, b: boolean ) { // after

// switchStatement.spaceAround
switch (foo) { // before
switch ( foo ) { // after

// tupleType.spaceAround
type Tup = [number, string]; // before
type Tup = [ number, string ]; // after

// whileStatement.spaceAround
while (true) { // before
while ( true ) { // after

As well as an umbrella spaceAround rule that controls them all.
Would love to have these baked into the base plugin so I don't need to ship my own custom version.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


What is suggested architecture to make this into an API?

I am an Android developer by trade. I'd like to use this library you've made which is the solution central to the business logic of our app thank you very much for this!
But being an android developer, I have little knowledge on how I can make REST APIs, also considering the other software needed for the library (pdftotext, antiword, etc). I have seen AWS and Heroku, but confused as to which OS the server should run on and the specifics. Could you point me in the right direction? I am studying NodeJS for Rest APIs

Let me know if this is close to your goal

Let me know if this is close to your goal:

Anyway, that's my pitch deck for hackathon competition 😅

this is a node project, so wrapping it with something like express (https://expressjs.com/) would be the first step. Then you have to host it. If you choose a service like heroku you wont have to worry about setting up the server and your linux knowledge too much. Otherwise theres a lot of options, like AWS EC2. Then point your url's dns to the server.


Problems encountered in superset 0.28.1 integrated echarts

ERROR in ./src/visualizations/index.js 85:19
Module parse failed: Unexpected token (85:19)
You may need an appropriate loader to handle this file type.
| var loadNvd3 = function () {
|   function loadNvd3() {
>     return loadVis(import( /* webpackChunkName: "nvd3_vis" */'./nvd3/adaptor.jsx'));
|   }
|
 @ ./src/modules/AnnotationTypes.js 17:22-50
 @ ./src/chart/chartAction.js
 @ ./src/explore/components/ExploreViewContainer.jsx
 @ ./src/explore/App.jsx
 @ ./src/explore/index.jsx
 @ multi babel-polyfill ./src/explore/index.jsx

Hello, every time I run 'npm run dev' to 92% it will report this error, I would like to ask why this is, looking forward to your guidance. Thanks

Same here.. Getting this issue.. on 0.28.1

I've solved this problem. It's due to the lack of packages. Go into the superset/static/assets directory and run'npm run dev'. You can see my notes for details, but it's in Chinese.https://blog.csdn.net/qq_33172735

@Llyfighting How to contact you?  I'd like to ask you some questions,Thanks!

You can contact me through Netease mailbox<EMAIL_ADDRESS>

@Llyfighting Can you help me? when i run  occur an question like your blog, but i run  can't pass it, so  i need help, can you give your  contact information. TKS


if onTap is not null, then only it should override children's onTap

if the onTap value is not provided in the CarouselView it was overriding the children's onTap if any e.g. any button or gesture dectector.
It should only effect if the value is given. Hence, the updated effect is as per below:
https://github.com/user-attachments/assets/2c8fddb2-c344-438e-8e30-3cfda87eb7d4

Closing PR due to some internal issue


Implanter draw rework

About the PR

This PR changes how the implanter works when it comes to drawing/extracting subdermal implants for an entity. The purpose of this PR is to remove the need for metashield rules around implants, and instead use mechanics to achieve the desired effects.
This is in line with the changes proposed in the design doc PR "Reduced Metagaming Mechanics" under "The Implant Problem": https://github.com/space-wizards/docs/pull/214
The PR does the following:

Implanters in Draw mode must now have a specific type of implant set.

The implant is chosen from a dropdown list of all available implants the implanter can draw.

When an implant is used, it will only attempt to draw out the implant it is set for.
If the implant exists, it gets deposited into the implanter as it works currently (or the draw fails, as is the case with acidifiers/mindshields). There is no change to this process.
If the implant doesn't exist, the implanter experiences a catastrophical failure and chunts genetic material into the user's hand (the hand of the person performing the implant check, not the person being checked). This deals major damage to the user.

This damage is set to 50 Cellular, 10 Heat in this PR.

Implant draw time is reduced from 60 seconds to 25 seconds.

After this PR is merged, implants and implant knowledge should be removed from the metashield.
Why / Balance

Implanters are one of the few "metashield" items that exist in the game, and the cause of this is quite apparent:

If implanters weren't metashielded, Security could randomly check crew at any point, for no reason.
Random checks would be very efficient since you get any implant that they have on them.
It's not that costly to do random checks. It's 60 seconds and once done you've confirmed they have zero implants, or you catch one.

As such, the metashield specifically requires either finding an implanter or seeing undisputable use of an implant before being able to check for it in an individual. This can lead to unnecessary admin work where it's unclear what exactly counts as undisputable, and players can be uncertain of whether they are allowed or not to perform an implant check. Conversely, a player may heavily suspect a character has an implant, but feel they are not allowed to check due to the rules. This PR intends to fix these issues.

Requiring specificity means SecOffs can not check randomly and just hoping to fish out an implant. They must at the very least suspect that a specific implant is in play to know to check for it.

This specificity is enforced via the damage taken when guessing wrong. SecOffs do not have the resources to perform random checks since it's directly harmful to the Security department and the personal cost to the SecOff performing the implant check discourages this on an individual level. It's simply not viable to randomly check crew due to the damage taken.
Even if they know someone is a Syndicate agent or a Thief they are still discouraged from checking the player; without concrete knowledge that a specific implant is in play, it is a risk to take major cellular damage, and while guesses can be made the uncertainty means crafty antags can still fool SecOffs into guessing incorrectly, the risk of which is likely to have a chilling effect.

The self-damage is a way to punish Security for being overzealous in their implant checking. Requiring a resource or breaking the implanter would put more strain on Cargo/Medical than it would on Security; losing access to a Security Officer for the time it takes for them to get healed in medbay is much more of a steep price that impacts Security directly.
The choice of Cellular damage is because it's a fairly rare damage type that doesn't see much use anywhere else. It's currently fairly easy to treat, so following this PR will be another that changes OD and metabolism values of Cellular treatment chems to be a slower process without complicating it for medical.
Technical details

Fairly straight-forward. If the implanter is in draw mode, it can open up a UI window where all implants whitelisted to be drawn are available. The chosen implant gets saved and then later gets checked against when drawing - if it doesn't exist, deal damage.
Media

Requirements

[x] I have read and am following the Pull Request and Changelog Guidelines.
[x] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog

:cl:

tweak: Implanters must now specificy which implant they're targeting when extracting, and deals heavy damage to the person performing the extraction if no such implant exists.

this PR given divine approval from the kingdom of heaven

New way to kill a person for antags?  Just cuff and try to draw implant from people that you need to kill

the damage is applied to the user, not the target.

sad that from this entire list of implants, only 3 are legal crew implants

sad that from this entire list of implants, only 3 are legal crew implants

its 5 but yeah... crew aren't meant to have things sec would spend a lot of work getting away from you, that's kinda the reasoning in my head for why there are so few crew ones.
Maybe #31045 would need to be reverted to give sec a better chance with this stuff for some of the implants. You're never going to be able to find storage or uplink implants without directly watching someone use them. Letting sec know what kind of implant is in a person when they find an implanter would make it much less of a hassle for sec when dealing with a DNA scramble implant or such, especially when it could kill you.

The damage has been updated to 50 Cellular, 10 Heat.
This puts you at or over the slowdown damage threshold, something that is very undesirable for a Security officer. The officer can get back down under it via having some ointment on hand, but that still leaves them at 50 Cellular, making it impossible to do another implant check without dying.

I get the basic idea of wanting sec to stop checking without cause- But damage to the person performing the extraction? That can't work on it's face, and it would have to IC be the worst, most dangerous design in the world for that.
But assumed functionality aside,  it'd actually be more detrimental for the universal implant remover to be destroyed if it can't pick up anything, given how annoying it is to ship things to sec anyway, because above all, this solution is too overkill in the direction of the antags for the following reason;
Even if the damage to the searching officer were just, the distinction being "type of implant" is a bit too hard on sec- Stopping needless searching is fine, but if we know someone is a syndie, it should NOT, from there, be a punishment on us that they used an EMP implant instead of say, a storage one, or a bomb, or an uplink, or any number of other implants that are both right to suspect an antag of, and that ironically all use an identical implant method. There are lots of variations of implant that you can get mixed up between even with probable cause, and punishing the person doing the search (in a way that only makes sense if they are horribly clumsy) over a condition you can get wrong even with probable cause will only cause people to reach for the more extreme alternate hedged bet of just killing the detainee.

Stopping needless searching is fine, but if we know someone is a syndie, it should NOT, from there, be a punishment on us that they used an EMP implant instead of say, a storage one, or a bomb, or an uplink, or any number of other implants that are both right to suspect an antag of, and that ironically all use an identical implant method.

You shouldn't be checking syndicate agents for implants unless you know for sure they have one.

There are lots of variations of implant that you can get mixed up between even with probable cause, and punishing the person doing the search (in a way that only makes sense if they are horribly clumsy) over a condition you can get wrong even with probable cause will only cause people to reach for the more extreme alternate hedged bet of just killing the detainee.

Which implants can be confused between each other?

Which implants can be confused between each other?

Uh, storage and uplink? Both could give syndie "esword out of thin air"

Even with the phala changes if the meta shield gets removed I would still envision implant checking to become significantly more common for storage implants.
Phala is, as you mentioned, trivial to use and obtain and giving sec a dedicated jug of phala is not difficult at all. Your proposed changes means the officer (likely ward) will have to set aside like 2 extra minutes of non active combat to heal up fully at most which for someone like the ward is basically ensured.
This is especially detrimental to thieves who would be impacted the most. After all it’s fairly reasonable to implant check a kleptomaniac for a storage implant provided the opportunity arises.
While I think the changes overall are beneficial, I would hope some rebalancing around the storage implant itself is done should this get merged. (Maybe reducing the TC cost a tad and/or increasing its storage space for the thief)

Which implants can be confused between each other?

Uh, storage and uplink? Both could give syndie "esword out of thin air"

If you are sure it's specifically an implant, then you must have fully searched that person, then they almost immediately pull out a sword out of nowhere. This is too specific of a case.

I have to vote no. This would make storage implant pointless as sec would basically always check for it if the suspect is clean. Plus they can just ask chem for some phalanx which isn't that hard to make.
The metashield is necessary and if anything should probably be expanded, since players WILL use Meta knowledge if allowed

with these changes phala healing cellular needs to go, cellular was intended to be a significantly more 'permanent' form of damage and it being easily healable kind of makes this pointless

I just hope that chemists and the CMO in general will tell security to piss off for an entire jug of phalaxamine every shift. Especially if it's shift start.

with these changes phala healing cellular needs to go, cellular was intended to be a significantly more 'permanent' form of damage and it being easily healable kind of makes this pointless

Could make cellular require a cryochem only to heal. Encourages the use of cryogenics and achieves the desired effect. This way security can't just check every damm implant. Feral slimes dealing cellular damage might have to be offset more into caustic though.

My problem is even if you make the heals harder, this disproportionately affects the storage implant as it's probably the most common and will have a reasonable success rate of removing if you have a strong suspect. At 8tc it's already pretty expensive. This will make it worthless.

At 8tc it's already pretty expensive. This will make it worthless.

I wouldn't say worthless but you can def argue that the tc cost should decrease a small amount should this get merged. Not really the end of the world. For the thief I think they could receptive an extra column of space in theirs but that's just my opinion.

Of course the most used implant will be disproportionally affected if the security officer wants to play "guess the implant this guy has".
It's the person who's using the implants fault if they get caught using an implant. This will promote syndies using their implant smarter.

fault

The problem is you probably won't get caught using the storage implant. You'll be a suspect, get searched, they'll find nothing, and they'll do a storage implant check. Every time. It will be useless.

My problem is even if you make the heals harder, this disproportionately affects the storage implant as it's probably the most common and will have a reasonable success rate of removing if you have a strong suspect. At 8tc it's already pretty expensive. This will make it worthless.

If Sec has a strong suspicion of there being a storage implant, they should be able to remove it. That's the whole point. You are right that Sec shouldn't be encouraged to check willy-nilly, but that's the whole point of the Cellular damage and the Phalanx changes in #32209. If Sec feels they can still check every time, then rest assured further balance tweaks will be made.
Also consider hiding your stuff in other ways, rather than relying on an implant as a crutch. The storage implant will still be great for stuff like random searches or where Sec suspects several people and can't afford to implant check every single one.

You'll be a suspect, get searched, they'll find nothing, and they'll do a storage implant check. Every time. It will be useless.

You can easily argue that you stashed it somewhere. They can't perform a check if you had obvious time to hide it.
You can also just let them take the item so they don't have to check you and you lose the implant. You don't have to keep the item hidden inside of you right after you're caught and spend 20 minutes losing the implant.
This is my entire point about syndies learning to use their implant in smarter ways.

I think the needing to select what implant to remove and having a penalty for selecting the wrong one is fun, but imo either the metashield needs to stay or there needs to be clear space law on when checking for an implant is allowed.
I can guarantee there will be plenty of sec that just automatically storage implant check if someone comes up clean, with no other reason to suspect an implant. I think the metashield of requiring DNA on an implanter or seeing obvious blatant use of the implant is the right way to go here.

I can guarantee there will be plenty of sec that just automatically storage implant check if someone comes up clean, with no other reason to suspect an implant.

then they will get it wrong the majority of the time, take 50 cellular, and stop doing that

Or they'll just bring prisoners to medbay for the check, or get arith from chem...

why would it need ot be reduced when in the current iteration implant are automaticaly removed without "proof" check

How often are you buying a storage implant and getting caught by sec? It's really, really, not that difficult to be stealthy as you steal these items giving sec no reason to capture you. If you are using it for smuggling then, again, sec would have no reason to think you have an implant unless you ALSO stole something before this.

Or they'll just bring prisoners to medbay for the check, or get arith from chem...

The proposed cellular change to accompany this promotes cellular damage as harder to cure, because it should be. Also, I believe the damage is going to the person who is administering the removal.

why would it need ot be reduced when in the current iteration implant are automaticaly removed without "proof" check

How often are you buying a storage implant and getting caught by sec? It's really, really, not that difficult to be stealthy as you steal these items giving sec no reason to capture you. If you are using it for smuggling then, again, sec would have no reason to think you have an implant unless you ALSO stole something before this.

I have frequently used a storage implant to get away with crimes. I have not been implant checked because I make sure I don't make it obvious or leave proof. However I have a hunch it is only because of metashield I wasn't defacto implant checked.
My concern is really just that "potential or likely suspect" doesn't become enough justification to do an implant check. A damage gamble shouldn't be the only thing governing sec's limitations.

The entire point of the meta shield is to protect against implant checking. The meta shield will obviously stay.
This is just adding a mechanical enforcement to a rule that already exists, much like zombies getting their bite tuned to not deal insane amounts of damage to structures. Doesn't mean it's against the rules anymore.

The entire point of the meta shield is to protect against implant checking. The meta shield will obviously stay.
This is just adding a mechanical enforcement to a rule that already exists, much like zombies getting their bite tuned to not deal insane amounts of damage to structures. Doesn't mean it's against the rules anymore.

"The purpose of this PR is to remove the need for metashield rules around implants, and instead use mechanics to achieve the desired effects."

"The purpose of this PR is to remove the need for metashield rules around implants, and instead use mechanics to achieve the desired effects."
You are taking things too literal. This is NOT removing the metashield. This is just enforcing it mechanically, reducing admin workload.

"The purpose of this PR is to remove the need for metashield rules around implants, and instead use mechanics to achieve the desired effects."

You are taking things too literal. This is NOT removing the metashield. This is just enforcing it mechanically, reducing admin workload.

"After this PR is merged, implants and implant knowledge should be removed from the metashield."

Guh, I retract my statements. I think the rules will probably stay for sakes, though...

Like I said, this change is overall beneficial and, at most, warrants a small buff to the storage implant. I really don't think sec is going to waste time taking 50 damage for every prisoner. Now, if they have a reasonable suspicion? Sure, go for it. But I really don't think it's going to be the end of the world for implants....
I'm not too fond of the meta shield around implants anyway, it's so strict that it basically prevents implant checking for any reason other than watching someone implant themself or if a syndie was foolish enough not to clean their implanter and left direct dna evidence on it. It's quite annoying watching someone who quite obviously has a storage implant but left your view for a bit and can claim that whatever is missing is "stashed in maints"

Honestly I'm all for it blowing the officers hand off if they get it wrong. But I don't think that's enough on it's own to keep it fair, we all know ss14 players will gamble every dollar cargo makes, or all their TC on a surplus.
I think we still need some kind of implant metashield though, even if it's made a bit more lax.

why would it need ot be reduced when in the current iteration implant are automaticaly removed without "proof" check

How often are you buying a storage implant and getting caught by sec? It's really, really, not that difficult to be stealthy as you steal these items giving sec no reason to capture you. If you are using it for smuggling then, again, sec would have no reason to think you have an implant unless you ALSO stole something before this.

never, because i don't play traitors and stopped playing on wizden for a while now.

Honestly I'm all for it blowing the officers hand off if they get it wrong, I think that part is hilarious. But I don't think that's enough on it's own to keep it fair, we all know ss14 players will gamble every dollar cargo makes on Grand lotteries, or all their TC on a surplus. 50 healable health is a much better odds gamble. I think we still need some kind of implant metashield though, even if it's made a bit more lax.

50 genetic damage and loosing an arm slot, now were talking about pushing hard gambles!

The better idea is for the implant remover to be removed from the game as I believe it was a temp-solution for when we have proper surgery in-game to remove implants. Instead of this UI design and rework which won't be good for whenever a new implant is added.

It sure was. But we can't just remove it without surgery being in place.

The better idea is for the implant remover to be removed from the game as I believe it was a temp-solution for when we have proper surgery in-game to remove implants. Instead of this UI design and rework which won't be good for whenever a new implant is added.

It sure was. But we can't just remove it without surgery being in place.

We removed the shuttle from the game before we got a salvage rework.

Space law should get a spot about implanters and checking similar to the metashield but in character instead of out of character and just tell people that its an in character issue in the rules or something. Otherwise i think this is a great set of PRs and i agree with the decisions made by slam.


Not able to use Docker Hub Registry

I have deployed an application in Argocd which uses image present in Docker hub container registry, when we update the image with new version in Docker Container Registry, Argocd Image updater should poll the Docker hub Container registry and update the application with latest verison of the image. This feature is not working.
Connection has been established between Argocd and Argocd Image updater, I can see in pod logs of Argocd Image updater,
Starting image update cycle, considering 1 annotated application(s) for update"
time="2020-11-17T09:16:05Z" level=info msg="Processing results: applications=1 images_considered=0 images_skipped=1 images_updated=0 errors=0"
I can see in logs its considering the application for update, but image is getting skipped, can't see any error logs and image is not getting updated for the application.
Logs:
time="2020-11-18T08:01:35Z" level=info msg="Starting health probe server TCP port=8080"
time="2020-11-18T08:01:35Z" level=info msg="Warming up image cache"
time="2020-11-18T08:01:35Z" level=info msg="Finished cache warm-up, pre-loaded 0 meta data entries from 5 registries"
time="2020-11-18T08:01:35Z" level=info msg="Starting image update cycle, considering 2 annotated application(s) for update"
time="2020-11-18T08:01:35Z" level=info msg="Processing results: applications=2 images_considered=0 images_skipped=2 images_updated=0 errors=0"
time="2020-11-18T08:03:35Z" level=info msg="Starting image update cycle, considering 2 annotated application(s) for update"
time="2020-11-18T08:03:35Z" level=info msg="Processing results: applications=2 images_considered=0 images_skipped=2 images_updated=0 errors=0"
time="2020-11-18T08:05:35Z" level=info msg="Starting image update cycle, considering 2 annotated application(s) for update"
time="2020-11-18T08:05:35Z" level=info msg="Processing results: applications=2 images_considered=0 images_skipped=2 images_updated=0 errors=0"
time="2020-11-18T08:07:35Z" level=info msg="Starting image update cycle, considering 2 annotated application(s) for update"
time="2020-11-18T08:07:35Z" level=info msg="Processing results: applications=2 images_considered=0 images_skipped=2 images_updated=0 errors=0"
time="2020-11-18T08:09:35Z" level=info msg="Starting image update cycle, considering 2 annotated application(s) for update"
time="2020-11-18T08:09:35Z" level=info msg="Processing results: applications=2 images_considered=0 images_skipped=2 images_updated=0 errors=0"
Registry.config looks like,
accounts.image-updater: apiKey
argocd.grpc_web: "true"
argocd.insecure: "true"
argocd.server_addr: <IP_ADDRESS>
registries.conf: |
registries:
- name: Docker Hub
api_url: https://argocdhub.docker.io
ping: yes
credentials: secret:argocd-image-updater/secrets
defaultns: library
Any help/leads would be highly appreciated.
@jannfis , Could you please help with  some leads on this.
Many Thanks!

Images are usually skipped for either of the two reasons:

There is no newer version of the image in the registry or
The image is not part of the application

Can you try to raise log level to debug by setting log.level: debug in argocd-image-updater-config, and restart the pod? This should give us a little more hints.

Hi @jannfis , I have enabled the debug log level.
I can see in logs, time="2020-11-20T11:11:00Z" level=debug msg="Image 'hello-kubernetes' seems not to be live in this application, skipping.
Application is using the image and I am able to access the application as well.
Any Leads would be highly appreciated.

Can you please post the annotations for image updater you are using?

Hi @jannfis ,
Please find the annotations,
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
annotations:
argocd-image-updater.argoproj.io/image-list: hello-kubernetes
argocd-image-updater.argoproj.io/hello-kubernetes.update-strategy: latest-first
argocd-image-updater.argoproj.io/hello-kubernetes.pull-secret: cpaasgitdockerhub
name: cpaascanary-updater-git
spec:
destination:
namespace: default
server: https://kubernetes.default.svc
project: default
source:
path: app-private-canary-GithubPackages
repoURL: https://github.com/nivedita-atci/argocd-example-apps
targetRevision: HEAD

OK. argocd-image-updater.argoproj.io/image-list should be a list of fully qualified image names.
Looking at the source for your application, it probably should be something like: argocd-image-updater.argoproj.io/image-list: hello-kubernetes=docker.pkg.github.com/nivedita-atci/argocd-example-apps/hello-kubernetes
Also, looking at your application source, you might want to let the image updater know which of the Helm parameters to set for updating the image. I think you could have success with argocd-image-updater.argoproj.io/hello-kubernetes.helm.image-spec: image.repository, given you using the alias from the annotation above.
For more information, please refer to https://argocd-image-updater.readthedocs.io/en/latest/configuration/images/#assigning-aliases-to-images and https://argocd-image-updater.readthedocs.io/en/latest/configuration/images/#specifying-helm-parameter-names

Thanks much for the leads, I could get the images are being considered to be updated now, getting,
"Could not get tags from registry: Get "https://docker.pkg.github.com/v2/nivedita-atci/argocd-example-apps/hello-kubernetes/tags/list\": http: non-successful response (status=401 body="{\"errors\":[{\"code\":\"UNAUTHORIZED\",\"message\":\"GitHub Docker Registry needs login\"}]}\n")" alias=hello-kubernetes application=cpaascanary-updater-git image_name=nivedita-atci/argocd-example-apps/hello-kubernetes image_tag=1.8 registry=docker.pkg.github.com

The Git Hub Docker registry requires authentication. In your configuration, but you have only configured a pull secret for a different registry.

Here is ConfigMap file of Argocd-image-updater,
apiVersion: v1
items:

apiVersion: v1
data:
accounts.image-updater: apiKey
argocd.grpc_web: "true"
argocd.insecure: "true"
argocd.server_addr: <IP_ADDRESS>
log.level: debug
registries.conf: |
registries:
- name: GitHub Docker Packages
prefix: docker.pkg.github.com
api_url: https://docker.pkg.github.com
ping: no
credentials: dockerconfigjson-github-com

I am getting below error,
time="2020-11-23T08:37:10Z" level=debug msg="Using no version constraint when looking for a new tag"
alias=hello-kubernetes application=cpaascanary-updater-app image_name=nivedita-atci/argocd-example-apps/hello-kubernetes image_tag=1.8 registry=docker.pkg.github.com
time="2020-11-23T08:37:10Z" level=error msg="Could not set registry endpoint credentials: invalid credential spec: dockerconfigjson-github-com" .
Same credentials have been used while deploying the application and we are able to deploy the application using the image from GitHub packages. When configured the same creds in registries.conf, I am getting error saying couldnot set registry endpoint credentials.
Any Leads would be highly appeciated.
Many Thanks in Advance.

time="2020-11-23T08:37:10Z" level=error msg="Could not set registry endpoint credentials: invalid credential spec: dockerconfigjson-github-com" .

You need to specify the pull secret in a fully qualified manner (refer https://argocd-image-updater.readthedocs.io/en/latest/configuration/registries/#specifying-credentials-for-accessing-container-registries).
For K8s secrets, the basic syntax is: <secret_type>:<namespace>#<secret_name>, where <secret_type> is either secret for a normal secret, or pullsecret for a secret in a classical pull secret format (with JSON contents).

I'm closing this issue. Feel free to reopen if it hasn't been resolved from your PoV.

I'm closing this issue. Feel free to reopen if it hasn't been resolved from your PoV.

Hello @nivedita-atci ,
I am having the same issue. Could you please let me know if you were able to get past this issue ?


Fixes nil issue that causes Service Member UI to fail at times

Description
For context, start at this Slack message and look at the follow-on messages in the channel:
https://defensedigitalservice.slack.com/archives/G8P7UD05U/p1553706274109800
We were having cases where the Service Member UI would get stuck on "Loading, please wait..." at times.  The error that was being thrown led us to realize that the CertificationType field of the SignedCertificationType model was not able to accept nil values, even though the field was optional per the database schema.
This PR changes that field so it can accept nil values, as well as puts some validations/tests around it to prevent bad values in the model.
Reviewer Notes
Interestingly, unless we made the enum definition in the internal.yaml file be nullable, the generated swagger-go code would not use a pointer for that field, even if the referencing definition marked the property using it as nullable.
Setup
(let Matt fill in)
References

Pivotal story for this change

Reference https://github.com/transcom/mymove/pull/1909 for more info.


refactor: Refactor the ButtonMenu integration tests.

Pull Request Test Coverage Report for Build 1072

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 73.32%

Totals

Change from base Build 1061:
-0.1%

Covered Lines:
585

Relevant Lines:
761

💛  - Coveralls


fix(libsinsp): keep the copy of cgroups alive across the write

What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area libsinsp
Does this PR require a change in the driver versions?
What this PR does / why we need it:
In https://github.com/falcosecurity/libs/pull/473 it was introduced a cgroups local variable in sinsp_threadinfo::cgroups_to_iovec, to have it work with a copy and avoid sinsp_threadinfo::m_cgroups being invalidated meanwhile.
Unfortunately, it slipped that iovec pointers reference the data owned by that local variable, thus becoming dangling at scope exit.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: deepskyblue86
Once this PR has been reviewed and has the lgtm label, please assign andreagit97 for approval by writing /assign @andreagit97 in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@poiana /area libsinsp

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, deepskyblue86, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


remove DS_Store dotfiles from exp init

It's weird to me that DS_Store files are included on a linux/ubuntu system, because those only come from mac's finder app.
I've attached a screenshot showing how I created a fresh project with exp init (version 39.0.0) and it has DS_Store files.

Fixed!


OCM Controller deployment error

Hello, I am trying to deploy ocm-controller to the kind cluster. I am getting error below
" ERROR	controller-runtime.source	if kind is a CRD, it should be installed before calling Start	{"kind": "GitRepository.source.toolkit.fluxcd.io", "error": "no matches for kind "GitRepository" in version "source.toolkit.fluxcd.io/v1beta2""} "
attached screenshots:

Right, so flux install is required for a cluster and ocm-controller now.

@mohammad-ammar14 is that still a case, could you validate and update/close the issue if not longer relevant


Outline?

Would there be a performant way of adding an outline?
Checking all neighboring pixels with IsPixelInLine_float seem to be a lot of work.

You could paint the line five times, displacing it 1 pixel up, down, left and right, and then the center.


graphdriver: fail earlier on existing driver

Prior to this change it was possible to end up with a running dockerd
which, when restarted, would fail due to multiple graphdrivers.
The obvious example of how to get into this state is the following:

start dockerd with -s overlay2
This creates /var/lib/docker/overlay2
start dockerd with no -s flag
This detects overlay2 and thinks it's okay since there's only one,
but then since overlay2 is not in the priority list, it ends up going
with overlay. Now overlay2 and overlay exist.
restart dockerd with no changes
It now detects both overlay2 and overlay and falls over

This change is intended to make case 2 impossibe. If a restart of
dockerd with no flag changes will reliably fail next time, it should
fail now too.
Implementation wise, this just checks that the driver that will be used
matches the existing one.

Manual testing done:

started on 17.09 (overlay2), downgraded, watched it fail immediately.
The above, but ensured -s overlay2 made it work correctly again.
The above, but with -s overlay which also works
Verified restarting the daemon with no -s and no data directory a couple times worked


[FancyZones Editor - Edit layout (Templates)]: Name is not defined for the Edit fields present on the 'Edit layout' dialog window.

Microsoft PowerToys version
"0.35.0"
Running as admin

[ ] Yes

Area(s) with issue?
FancyZones Editor
Steps to reproduce
Test Environment:
OS: Windows 10 Build 21354.1
App version: 0.35.0
App name: PowerToys
Screen Reader: Narrator
Tool: Accessibility Insight for Windows
Repro Steps

Launch 'PowerToys' application.
Application will get open with default list item 'General' selected.
Navigate to 'FancyZones' at the left side of the pane and activate it.
Now navigate to 'Launch layout editor' button and activate it.
FancyZones editor window will get open.
Navigate to 'Edit layout' button of any layout (say Grid) under Templates and activate it.
Edit layout dialog window will get open.
Run 'Accessibility Insight' tool on the application.
Observe the issue.

User Impact: Priority-0
If the object role, state(s), properties, boundary, name, and description are not programmatically determinable, it would be difficult for the platforms that provide Accessibility APIs, and would in turn affect the screen reader dependent users to determine the object properties.
MAS Reference:
https://microsoft.sharepoint.com/:w:/r/sites/accessibility/_layouts/15/Doc.aspx?sourcedoc={B661D774-60D0-4277-A121-73F986EBEE76}&file=MAS 4.1.2 – Name%2C Role%2C Value.docx&wdLOR=cE56E09CE-4478-4D20-B785-78D1B90569C1&action=default&mobileredirect=true&cid=577e2918-ba37-4bc7-bdd5-df0122160d1f
Note: Same issue repro for all the edit fields and combo box present on the Edit layout dialog of Custom.

✔ Expected Behavior
The name property of a focusable element must not be null. Provide a UI Automation Name property that concisely identifies the element.
For e.g. Name such as "Show space around zones" should be defined for its edit field.
❌ Actual Behavior
Name is not defined for the Edit fields present on the 'Edit layout' dialog window.
Other Software
No response

@dedavis6797 This seems to be a bug in ModernWPF - I have looked at tweaking the style but no success :(.
@jaimecbernardo Maybe someone from your team can have a look at this? Fall-back would be going back to TextBox (with regex for number detection) instead of NumberBox but that would be a regression in keyboard navigation and overall UX.

This seems to be a bug in ModerWPF, indeed: https://github.com/microsoft/microsoft-ui-xaml/issues/2951

@niels9001 ,
Figured out a way to achieve this. Not elegant, but it seems to work.
Please take a look: https://github.com/microsoft/PowerToys/pull/12718


When i run offline_lidar_obstacle_perception, check failed：config_manager->GetModelConfig(class_name, &model_config)

When i run offline_lidar_obstacle_perception, check failed : config_manager->GetModelConfig(Name(), &model_config)

bash docker/scripts/dev_into.sh
bazel build -c opt //modules/perception/lidar/tools:offline_lidar_obstacle_perception
/apollo/bazel-bin/modules/perception/lidar/tools/offline_lidar_obstacle_perception
See error

Expected behavior
offline_lidar_obstacle_perception appear.

And i find the error line:

OS: Ubuntu 18.04

- Version : Apollo5.5
I really need some help , and i will apperciate everyone who helps me to solve it.
here is the files in /apollo/data/log,maybe can help :

#11157 i meet the same problem as this issue.But he is running the lidar_app_lidar_pipline_test.cc, and I am running the offline_lidar_obstacle_perception.cc , and i am trying to find the solution.

/apollo/bazel-bin/modules/perception/lidar/tools/offline_lidar_obstacle_perception --work_root=/apollo/moudles/perception/production
And the problem is solved.


Unbreak haskell package ats-pkg

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Idk why are there so many commits. Just cherry-pick mine.

@poscat0x04 Please rebase your change on top of the haskell-updates branch.

Done

I tested this locally and it compiled.  Thanks for fixing this!


CI against Ruby 2.5.0

There have been more Ruby versions included in the matrix since this change, so it needs an update.

Merged with a few additions as f71053bc26fcd6e378cd570ac5f62e6d24419995


NIFI-5479: Upgrade Jetty

Upgrading Jetty. Including a commit that @joewitt had provided in PR #2933. I have provided an additional commit that addresses a behavioral change in Jetty's SslContextFactory. I have verified various NiFi deployments including (un)secured standalone and clustered instances using both certificate based authentication and our JWT authentication using OpenID Connect.
Once this PR is closed, we can also close #2933.
@markap14 Can you help verify some of our processors that leverage the bundled Jetty server?
@ijokarumawak Can you help verify our web socket processors?
Would also appreciate anyone else willing to deploy this proposed change to ensure there aren't any other regressions.

@mcgilman I was able to verify that the HandleHttpRequest and HandleHttpResponse processors still work - and in fact work better! This appears to have addressed NIFI-5522.

Of note, I was also able to verify PostHTTP, ListenHTTP, and HandleHttpRequest/Response both using SSL Context and without SSLContext.

@ijokarumawak as far as I'm concerned, I'm a +1 on this. If you're also happy with it, please feel free to go ahead and merge to master & mark as resolved. Thanks! And thanks @mcgilman for the PR - this is very timely!

@mcgilman I've confirmed that NiFi Websocket component uses the updated Jetty version and works without issue. I'm a +1 on this, too. Thanks for this fix, merging!


list tails files on server by rev reg id substring; e.g., issuer DID,…

… cred def id, tag
Signed-off-by: sklump<EMAIL_ADDRESS>

FYI @esune


Configure CH water temperature

Hi!
Is it possible to set the temperature of the heating hot water?
On the ariston-net.remothermo website it appears in option <IP_ADDRESS> - Tset Z1
I am not able to find how to do it.
I am running on a CHAFFOTEAUX PIGMA GREEN boiler with the Ariston Sensys control unit, and works well your integration.
Thank you very much for this integration.

Supported items depend on a model and so far I have not seen such a parameter (I got to check only few boilers).
Analyzer can be used to check the request (I use fiddler and chrome browser) but I suspect that it is parameter with name "U6_3_0_0". Since unsupported 1 parameter crashes request some logic should be considered to filter parameter out to not crash other boilers.
If I'll have free time maybe I can prepare a prototype with new parameter for you to test.

Supported items depend on a model and so far I have not seen such a parameter (I got to check only few boilers).
Analyzer can be used to check the request (I use fiddler and chrome browser) but I suspect that it is parameter with name "U6_3_0_0". Since unsupported 1 parameter crashes request some logic should be considered to filter parameter out to not crash other boilers.
If I'll have free time maybe I can prepare a prototype with new parameter for you to test.

Thanks a lot!
If you need acces to my remotethermo, just tell me and i will create a password for you.

Thanks a lot!
If you need acces to my remotethermo, just tell me and i will create a password for you.

You may replace files from attached archive, restart HA and then add sensor "ch_water_temperature":
ariston.zip
Changing via service requires use of "ch_water_temperature" parameter.
Please let me know if it works. Sharing login credentials might be required if nothing works.

You may replace files from attached archive, restart HA and then add sensor "ch_water_temperature":
ariston.zip
Changing via service requires use of "ch_water_temperature" parameter.
Please let me know if it works. Sharing login credentials might be required if nothing works.

You may replace files from attached archive, restart HA and then add sensor "ch_water_temperature":
ariston.zip
Changing via service requires use of "ch_water_temperature" parameter.
Please let me know if it works. Sharing login credentials might be required if nothing works.

You may replace files from attached archive, restart HA and then add sensor "ch_water_temperature":
ariston.zip
Changing via service requires use of "ch_water_temperature" parameter.
Please let me know if it works. Sharing login credentials might be required if nothing works.

Now I can see the water temperature, but I cannot change the value.
If you need the credentials, please contact me at<EMAIL_ADDRESS>

Now I can see the water temperature, but I cannot change the value.
If you need the credentials, please contact me at<EMAIL_ADDRESS>

I can contact you after work.
Meanwhile you may try service "ariston.set_data" under Developer Tools - Services
With data:
'''
entity_id: climate.ariston # name of entity
ch_water_temperature: 80 # temperature
'''

I can contact you after work.
Meanwhile you may try service "ariston.set_data" under Developer Tools - Services
With data:
'''
entity_id: climate.ariston # name of entity
ch_water_temperature: 80 # temperature
'''

You may try the new version uploaded.

You may try the new version uploaded.

Fantastic!
Now everything works correctly.
Thank you so much for everything!

Fantastic!
Now everything works correctly.
Thank you so much for everything!


Support different commands

Allow the end user of this in actions to call differnet commands like ape compile --size and ape test (and maybe ape run my_script?)

One possible solution, user adds this to their .github/workflow/action.yaml file:
- uses: ApeWorX/github-action@main
  with:
    command: compile --size
- uses: ApeWorX/github-action@main  # Uses `ape test` by default

solved by #4


Git commit window is cropped after a few characters

After about 7 or 8 characters, no text is visible in the commit window.

Thanks for the bug report 👍
it works now:


Format version with sub-versions is not compatible with the migration

Description
Using a recipe with format version 2.0.0 returns an empty recipe
Expected Behavior
Recipes with format sub-versions 2.0.x should not be migrated (if migration is not necessary)

We made the decision that we weren't going to need 3 units of precision for format versions. but then didn't update the recipes. So I think the fix here is just changing the format_version in the recipes instead of changing the code. We could add a check incase someone types it incorrectly

Sounds good, I have updated the recipes I was using. Closing this now.


Formants' frequencies passed to the callback function

Hi! Quick question. When I choose the output level 4 (Segment Formants), I can see reasonable values for the formants' frequencies in the canvas. However, the frequencies passed to the callback function in the features array seem to be rather low. For my schwa, they are on the order of 17/40/60. I was wondering why this happens and how to get the actual values in Hz

You are probably getting Mel filter's indices. You can convert to Hz by using a Mel-to-Hz conversion formula. It might not be completely accurate as each filter bank has different Hz range from 10Hz to 250Hz. It's better to convert the mid-point of the whole range, for example if you want to convert 60 (the raw output you are getting), then convert as: mels2Hz(60.5)
Let me know if that doesn't give you the right frequency then I will have a deeper look into it.

Thank you for such a fast and detailed response!
Here's what I'm getting in my latest experiment:

Value from features == 16
mels2Hz(lowM + (16.5 * delMel))  ~ 248
Value in the chart ~179

Value from features == 49
mels2Hz(lowM + (49.5 * delMel)) ~ 816
Value in the chart ~508

Value from features == 72
mels2Hz(lowM + (72.5 * delMel)) ~ 1403
Value in the chart ~833

Sorry, I can't figure out what's wrong here. Can you check if you are using the default settings?
spec_type: 1,
output_level: 4,
f_min: 50,
f_max: 4000,
N_fft_bins: 256,
N_mel_bins: 128,

Thank you! You were right, I messed with the defaults. Now everything works as expected. The transformed values from features match the frequencies in the chart


Overlay mod bindings and access to mouse/keyboard

We disallowed access to keyboard and mouse functions from our fork of sol_ImGui.
I believe, considering ImGui is completely inaccessible from outside of onDraw now, we could reenable keyboard and mouse access to it.
There were few valid requests for such access, like having an ability to have some copy-paste functionality or custom shortcuts while overlay is active.
I would propose reenabling the disabled functions (believe they are just left commented out inside sol_ImGui) and potentially tweaking VKBindings to allow for modbinds separate from in-game ones which would get triggered while overlay to allow for overlay-specific shortcuts.
This could be split into two separate tasks/PRs.
I believe sol_ImGui alone should cover most use-cases, but would need to get properly tested and implemented.
Making the issue so someone can pick it up when they want to. This enhancment would be something that should now be safe and I believe not that hard to implement. Marking it as an enhamcement and good first issue, as I believe it should be quite a small change, at least for the sol_ImGui part.

If anyone is willing to pick this up, can provide help as this is something I majorily worked on for CET in the past, know the systems and expected behaviors.
Feel free to contact me.

Interesting commit for this task:
https://github.com/maximegmd/CyberEngineTweaks/commit/4f23722a5fc68a65c6aa5ef2ac12e0846d9c1164
Everything that was removed by this commit that was under SOL_IMGUI_ENABLE_INPUT_FUNCTIONS should get reverted and retested it is

only accessible from onDraw
works as expected

I suspect 0 to none issues from such partial revert and removal of the define, just dont revert whole commit...


Missing Unity meta file for Editor/Bindings folder

Hello,
on the most recent version there is no Bindings.meta file in the unity/Editor folder. The Bindings folder, and the importer within are ignored as a result by the editor. This is only an issue if the package is imported remotely (since the package folder is then immutable, and the editor won't create one there) as far as I can tell.

Hi @Balint-H, is this solved in the newest release?

Not yet, but I'll send a PR for this tomorrow.

I noticed hence removed the comment 😅 Thanks!


Incorrect furigana entry

研究 is rendered as "ken-kiwamu" instead of expected "kenkyû"
source https://japanese.stackexchange.com/questions/86279/
verified https://ja.wikipedia.org/wiki/研究員

This is not the responsibility of this tool. See library igo-javascript.

See #9 #10 , the PR maybe could solve some of such case.


Add voice status feature

Pull Request Etiquette

[x] I have checked the PRs for upcoming features/bug fixes.
[x] I have read the contributing guidelines.

Changes

[x] Internal code
[x] Library interface (affecting end-user code)
[ ] Documentation
[ ] Other: _____

Closes Issue: NaN
Description
Reference: https://github.com/discord/discord-api-docs/pull/6398
Allows setting a status for a voice channel.

Any update on when this will be available? Seems like a pretty nice feature!

Any update on when this will be available? Seems like a pretty nice feature!

"status: awaiting discord docs pr"

Any update on when this will be available? Seems like a pretty nice feature!

"status: awaiting discord docs pr"

Yea, but it has been for a while now..

Any update on when this will be available? Seems like a pretty nice feature!

"status: awaiting discord docs pr"

Yea, but it has been for a while now..

well ask discord to merge the docs pr.


Add backwards compatibility for older versions of Node

Description
workos-node v6 added support for other JS runtimes, but that meant that the minimum node version required jumped up to v19.
This adds in backwards compatibility to make the SDK usable with at least Node v16.
Documentation
Does this require changes to the WorkOS Docs? E.g. the API Reference or code snippets need updates.
[ ] Yes

If yes, link a related docs PR and add a docs maintainer as a reviewer. Their approval is required.

We should also remove Node 14 from the CI matrix.

Can probably need to tell the linter to ignore these vendored polyfills.

Thanks for the review @alisherry! While doing some testing I found some bugs in the Node implementation which should now be fixed. Can you have another look?


Buildings with negative space underneath (feasibility test)

Is a model of the four-car pass in the Islands possible? It has four arches. If possible, might test an overpass in downtown Vice City

Fully possible and will come eventually, the map right now is all greyboxing. Anything that can be modeled in standard GLTF format is possible.


⚠ WSINGRESOS - GENERICO has degraded performance

In 308fa01, WSINGRESOS - GENERICO (https://srvshyweb.yucatan.gob.mx/cgi-bin/wspd_cgi.sh/WService=wsingresos/internet/servicios/wsGenericoPagosWeb.r) experienced degraded performance:

HTTP code: 200
Response time: 2260 ms

Resolved: WSINGRESOS - GENERICO performance has improved in ec1f91d after 18 minutes.


Create an e2e SingleTilingExpert pass pipeline for CPU backend.

This is currently only used for linalg.generic ops and is a means to
vectorize these operations by default.

This depends on https://reviews.llvm.org/D115820
Performance on local Pixel 4.

Model
Before
After

DeepLabV3
964 ms
954 ms

MobileBertSquad
682 ms
682 ms

MobileNetV2
177 ms
176 ms

MobileNetV3Small
47.6 ms
47.5 ms

MobileSSD
365 ms
368 ms

PoseNet
884 ms
884 ms

There is a slightly improvement (10ms) in DeepLabV3.
After running many times, I think the regression in MobileSSD is true (~2 ms). I think it's fine for now.

If you dont mind can you create a PR to the single_tiling_expert branch and then we can "merge" that branch into main?

If you dont mind can you create a PR to the single_tiling_expert branch and then we can "merge" that branch into main?

This is the PR to the branch.  I basically rebase it to top of tree and apply some minor changes. (e.g., fix some comments, add a util function abourt isVMVXBackend(), etc.)

it says google:main <- hanhanW:iree_sandbox_tip .I would expect it to be google:single_tiling_expert <- hanhanW:iree_sandbox_top. This would then be followed by google:main <- google:single_tiling_exper merge PR?

it says google:main <- hanhanW:iree_sandbox_tip .I would expect it to be google:single_tiling_expert <- hanhanW:iree_sandbox_top. This would then be followed by google:main <- google:single_tiling_exper merge PR?

Okay I can separate the changes and do it in two steps. It will be easier to review I think.

it says google:main <- hanhanW:iree_sandbox_tip .I would expect it to be google:single_tiling_expert <- hanhanW:iree_sandbox_top. This would then be followed by google:main <- google:single_tiling_exper merge PR?

Okay I can separate the changes and do it in two steps. It will be easier to review I think.

And also preserve commit history.

Created https://github.com/google/iree/pull/7895


Display Correct Fee on Spend Dialogue

Actual behaviour
When you do a spend, a message is shown that says 0.05 XZC are given to miners. This isn't always true.
Desired behaviour
As the client knows the exact fee at this time, it should be shown.
Steps to reproduce
Do any spend, see the message.

It always shows correct fee, only the message is confusing.
Message is this.
"Change will be reminted and amounts smaller than 0.05 will be paid as fees to miners."
Second part of the message can happen only when Subtract fee from amount is unchecked.
We can print second part only for that case.


Http hybrid mode

Internally we had a debate about current HTTP capability design, around the topic of whether router should be defined dynamically in the user code vs. should be defined statically in a configuration file. There are some advantages and disadvantages on both sides.
advantages of defining router and handlers in one applicaiton:

For those who are familiar with NodeJs epxress or Rust routerify, this is a more familiar pattern to define http server and handlers in the same code.

disadvantages of defining router and handlers in one application:

Each handler can't be written in other programming language that compiles to webassembly
The wasm binary size is relatively bigger the single handler size because it has to bundle other handlers and router defintion.
It's difficult to statically verify routes

The above two design choices are not mutually exclusive. What we can do is to provide a router implementation that is statically defined in a configuration file, and allow users to plug it in the router dynamically in code. In addition, we could also allow users to specify a path to wasm module to handle http request. Introducing the hybrid mode.
Hybrid mode
To allow the http handler to be written in other programming languages, one thing we can change in the server is to allow handler name be written as path to handler wasm modules. For example, instead of
fn main() -> Result<()> {
    let router = Router::new()?;
    let router_with_route = router
        .get("/hello", "handle_hello")?
        .get("/foo", "handle_foo")?
        .put("/bar", "handle_bar")?
        .post("/upload", "upload")?
        .delete("/delete-file", "delete_file_handler")?;
    let _ = Server::serve("<IP_ADDRESS>:3000", &router_with_route)?;
    Ok(())
}

we can write
fn main() -> Result<()> {
    let router = Router::new()?;
    let router_with_route = router
        .get("/hello", "./foo/handle_hello.wasm")?
        .get("/foo", "./bar/handle_foo.wasm")?
        .put("/bar", "handle_bar.wasm")?
        .post("/upload", "upload")?
        .delete("/delete-file", "delete_file_handler")?;
        .extend("/", "slight_api.toml")?;
    let _ = Server::serve("<IP_ADDRESS>:3000", &router_with_route)?;
    Ok(())
}

There are two notable differences

The handler name can now be a path to a wasm module. The server will load the wasm module and invoke the handler function in the wasm module.
a new router function called extend is introduced. This function allows users to extend the router with a configuration file. The configuration file is a toml file that defines the routes and handlers. The configuration file can be used to define routes and handlers statically.

@Mossaka I think most of this makes sense.
One suggestion: for router lines in which you reference a WASM module, like .get("/hello", "./foo/handle_hello.wasm")?, this restricts developers to one handler per wasm module. Some syntax that allows a developer to build many handlers into one module would be better. Can you add the method name to the string, like maybe this? .get("/hello", "./foo/handle_hello.wasm?fn=my_foo_handler")?

@devigned suggested this would allow us to statically check the existance of handler
.get("/foo", nameOf!(handle_foo))?


Consider not using Show when making GeneralCategory etc.

GeneralCategory.hs is enormous, but this is the nature of having this sort of lookup table in the code. It can be made quite a lot smaller and hopefully ease the work the compiler has to do parsing it by using the numeric values for the chars in it. replacing the generation of \EOT with \4 saves 254,666 characters in the source file, but also has the benefit that a human can look at the table and tell which category fromEnum value a particular position corresponds to. A quick find and replace of some of the more common characters gives this saving in the line length of bitmap#:
    Original     -> 3485166
    EOT replaced -> 3230500
    NUL replaced -> 3226838
    NAK replaced -> 3220233
    SOH replaced -> 3215779
    ENQ replaced -> 3211879
    SUB replaced -> 3211716
    ETX replaced -> 3211048

I understand this isn't something people are expected to read very often, but for the times when someone does need to, it would be helpful. I'd even consider adding a generated comment which shows the mapping between the numeric and GeneralCategory values.

Sure. Would you care to send a PR in case you have already done this?

I had a play around and came up with the following diff, sorry it's not a PR:
diff --git a/exe/Parser/Text.hs b/exe/Parser/Text.hs
index 8b8e1e6..a805b5a 100644
--- a/exe/Parser/Text.hs
+++ b/exe/Parser/Text.hs
@@ -167,8 +167,8 @@ genEnumBitmap funcName as = unlines
                <> show (fromEnum Cn)
                <> " else lookupIntN bitmap# n"
     , "  where"
-    , "    bitmap# = "
-        <> show (enumMapToAddrLiteral as) <> "#"
+    , "    bitmap# = \""
+        <> enumMapToAddrLiteral as "\"#"
     ]

 {-| Encode a list of values as a byte map, using their 'Enum' instance.
@@ -178,13 +178,13 @@ __Note:__ 'Enum' instance must respect the following:
 * @fromEnum minBound >= 0x00@
 * @fromEnum maxBound <= 0xff@
 -}
-enumMapToAddrLiteral :: forall a. (Bounded a, Enum a, Show a) => [a] -> String
-enumMapToAddrLiteral = fmap go
+enumMapToAddrLiteral :: forall a. (Bounded a, Enum a, Show a) => [a] -> String -> String
+enumMapToAddrLiteral xs tl = foldr go tl xs

     where

-    go :: a -> Char
-    go = chr . fromIntegral . toWord8
+    go :: a -> String -> String
+    go a tl' = '\\' : shows (toWord8 a) tl'

     toWord8 :: a -> Word8
     toWord8 a = let w = fromEnum a in if 0 <= w && w <= 0xff

Which takes the same from 3485793 to 3207915 for saving of 277878 and makes the array a little easier to understand by keeping everything numeric.


Add InheritDataTypeFromItems for AutoCompleteBox.ValueMemberBinding

What does the pull request do?
This pull request tags the AutoCompleteBox.ValueMemberBinding property with the InheritDataTypeFromItemsAttribute attribute to simplify the compiled binding expressions on this property in most cases.
What is the current behavior?
The property type needs to be declared explicitly in the binding expression on this property.
What is the updated/expected behavior with this PR?
Compiled binding expressions on this property no longer require explicit specification of the generic type for the ItemsSource collection type.
Breaking changes
None.
Obsoletions / Deprecations
None.
Fixed issues
Fixes #14161

@gehongyan please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@dotnet-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@dotnet-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@dotnet-policy-service agree company="Microsoft"

Contributor License Agreement

@dotnet-policy-service agree


Missing important information about interaction of the Add-in with Shared Mailboxes

https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/enable-the-report-message-add-in?view=o365-worldwide#what-do-you-need-to-know-before-you-begin
The Report Phishing and Report Message add-in function is not available when accessing a Shared Mailbox within Outlook.

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

ID: 445892a6-5948-33e4-ce60-72670829d8ef
Version Independent ID: a7407a6f-6563-9a4b-4a95-7ed908ab322b
Content: Enable the Report Message add-in - Office 365
Content Source: microsoft-365/security/office-365-security/enable-the-report-message-add-in.md
Product: m365-security
Technology: mdo
GitHub Login: @siosulli
Microsoft Alias: siosulli

Frankly, it should be. Shared Mailboxes are generally the delivery point of publicly posted email addresses and tend to be subject
to increased malicious mail flow....but until such time as THAT issue is resolved, the documentation should be clear about this limitation.

@Breid125 Thank you for your feedback. If the shared mailbox is auto mapped, you may not be able to view the add-in on outlook.
A multitude of features are only available when the mailbox is added as an additional account, there's nothing specific to the report message add-in here.
Hope this helps!
Thanks
Sri

So not providing the warning that the Report buttons will not work for a mailbox added in that manner is an acceptable omission of information? Consider that “group mailboxes” like info@ purchasing@ etc are among the most frequently targeted for attack, and that an org looking to protect itself buy using these adding leave themselves a hole in defence. Consider the cost of having customer contact Support asking “why doesn’t this work” and the time And money  wasted by not noting this limitation in the documentation.
Ignite 2019 indicated better support for addins on Shared Mailboxes, if this isn’t the case then tell your customers about the inherent limitation. If this is a documented issue, reflect that in the information.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Sriraman M S<EMAIL_ADDRESS>Sent: Tuesday, March 2, 2021 5:23:30 AM
To: MicrosoftDocs/microsoft-365-docs<EMAIL_ADDRESS>Cc: Brendan Reid<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/microsoft-365-docs] Missing important information about interaction of the Add-in with Shared Mailboxes (#4235)
@Breid125https://github.com/Breid125 Thank you for your feedback. If the shared mailbox is auto mapped, you may not be able to view the add-in on outlook.
A multitude of features are only available when the mailbox is added as an additional account, there's nothing specific to the report message add-in here.
Hope this helps!
Thanks
Sri
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/microsoft-365-docs/issues/4235#issuecomment-788905308, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AROPI7ZRYKBSL2D53CPHS7TTBTRFFANCNFSM4YDKLJNQ.

@Breid125 Thank you for the feedback. It makes sense to add that information. So I Have added the limitation to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/4299
Thanks
Sri

Thanks @Breid125
I've made an update to the what-do-you-need-to-know-before-you-begin section to include some text around
the Report Message add-in not working on Shared Mailbox within Outlook.

Thank you.
Same text should be applied to:
https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/enable-the-report-phish-add-in?view=o365-worldwide
As they’re effectively the same add-in but with different UI process for submission.
If/when this get’s fixed, I’ll come back and let you know.  =)
-Brendan
From: siosulli<EMAIL_ADDRESS>Sent: March 2, 2021 3:06 PM
To: MicrosoftDocs/microsoft-365-docs<EMAIL_ADDRESS>Cc: Brendan Reid<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/microsoft-365-docs] Missing important information about interaction of the Add-in with Shared Mailboxes (#4235)
Thanks @Breid125https://github.com/Breid125
I've made an update to the what-do-you-need-to-know-before-you-begin section to include some text around
the Report Message add-in not working on Shared Mailbox within Outlook.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/microsoft-365-docs/issues/4235#issuecomment-789287640, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AROPI746OQQWX6FB5CIS42TTBVVNTANCNFSM4YDKLJNQ.

@msbemba Thank you very much for the contribution and updating the documentation with PR. @Breid125 Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Upgrader Not Working

Known issue,  the key generated when a release is created via github releases is just not working. I am unsure why, until it is resolved, upgrading will not work

oop wrong repo


Add license to npm packages

For #19

Thanks! Will get it published in the next release

Glad to contribute.


if we use calico-IPAM for ip address management of the pods do we have to use whereabouts ipam for assigning unique ip addresses for the additional network interfaces like macvlan or ipvlan attached to the pods?

if we use calico-IPAM for ip address management of the pods do we have to use whereabouts ipam for assigning unique ip addresses for the additional network interfaces like macvlan or ipvlan attached to the pods?
Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

Calico version
Orchestrator version (e.g. kubernetes, mesos, rkt):
Operating System and version:
Link to your project (optional):

some hints on incompatibility https://github.com/projectcalico/calico/issues/5672


Added computation of match score for multiple samples

Changes look ok!

Thanks! All done, merge and delete branch.


Closes #364 - Agent should expose the number of log events as additio…

…nal selfmonitoring metric

This change is

@mariusoe  I've updated the commit :)

Finally, all test are green @mariusoe  :)


ENH: Remove warning message when nullptr is used as vtkObject pointer event data

ctkVTKConnection logged a warning message each time an event was received that vtkObject* as event data and the pointer was nullptr.
Always treating nullptr value as an error is too limiting, because it is often useful that an additional pointer can be supplied but not mandatory.
This change removes the warning message from ctkVTKConnection and makes it the event receiver's responsibility to log warning/error if in that particular case nullptr is not expected.
Since ctkVTKConnection just logged a warning message but already left nullptr values through, it is guaranteed that change does not alter any existing software behavior
(other than not displaying the warning).
This change is useful in Slicer because DisplayModified events typically contain the display node pointer as eventdata but if multiple DisplayModified events are lumped together
(due to batch update with Start/EndModify) then there is no display node that could be attached to the event.

Thanks @pieper!


Create zh_cn.json 1.16.1

Updadte zh_cn.json 1.16.1
In addition
Can I repost your mods to mcbbs?
mcbbs:https://www.mcbbs.net/
mcbbs is the largest minecraft fan forum in China.
I will not provide download sources other than Curseforge
I'm sorry to ask questions here, because of GFW, I cannot register for a twitch account, so I cannot ask questions on Curseforge.

I will allow it.

Updadte zh_cn.json 1.16.1
In addition
Can I repost your mods to mcbbs?
I will not provide download sources other than Curseforge

I will allow it.

There's been quite a few new keys added in the last day or two and this PR is behind me by.. I think a day or two of work, mostly the Patchouli elements. I'll merge this for now, but feel free to hit me with another if you happen to do more. Always appreciate translation work!


Won't work with python3.12

Cookiecutter Plone Distribution
================================================================================

Sanity checks
--------------------------------------------------------------------------------
  [1/2] Python: Python version is not supported: Got 3.12.4 | packaged by Anaconda, Inc. | (main, Jun 18 2024, 10:07:17) [Clang 14.0.6 ]
  [2/2] git: ✓
Pre-Prompt Hook script failed

@avoinea what happens if you edit this to include 3.12? https://github.com/collective/cookiecutter-plone-distribution/blob/main/hooks/pre_prompt.py#L42 It might fail, but at least it will get over the initial hurdle.

Actually it worked with:
pipx run --python $(which python3.11) cookiecutter gh:collective/cookiecutter-plone-distribution

We should add that to the README.

Also with:
pipx run --python=python3.11 cookiecutter gh:collective/cookiecutter-plone-distribution

That uses Python 3.11, not 3.12, as described in the issue title. We should still verify whether it would work with 3.12.
Nonetheless, we should update the readme with actual supported Python versions and how to specify a supported Python version with --python=python3.X.


Add Webex Teams Cards&Buttons as native python objects

This PR introduces Adaptive Cards as native python objects.
Example
from webexteamssdk.cards.card import AdaptiveCard
from webexteamssdk.cards.components import TextBlock
from webexteamssdk.cards.options import Colors, HorizontalAlignment
from webexteamssdk.cards.inputs import Text, Number
from webexteamssdk.cards.actions import Submit

title = TextBlock("Please give me your data!", color=Colors.GOOD)

first_name = Text('first_name', placeholder='Your first name')
age = Number('age', placeholder='Your age')

send_button = Submit(title='Send data')

card = AdaptiveCard(lang="en", body=[title, first_name, age], actions=[send_button])
print(str(card.to_json(pretty=True)))

will print the json required for this card

@sQu4rks Thank you for the PR!  I apologize for the delay in getting this merged.  I am going to move the package to the webexteamssdk.models package and do some refactoring.

No worries @cmlccie. I have since split this into its own package (see CiscoSE/pyadaptivecards). What do you think about adding that package as a dependency and import them in the init.py so that there is only one „adaptive Cards in python“ code base instead of two.

Makes sense to me!  I'll modify the webexteamssdk code to add this as an optional dependency.  If you can incorporate the make_card_attachment(card) function into your package, I will modify the SDK to automatically serialize the cards when passed to WebexTeamsAPI.messages.create(attachements=).

@sQu4rks in case you are interested...  Here are the refactoring edits I made to the code:
https://github.com/CiscoDevNet/webexteamssdk/commit/aa0617a8404820306f5603d8c18315d0ac78084d
I agree it is better to have this functionality in a separate package that you can maintain without waiting on me.  🙂 Let me know when you have incorporated the make_card_attachment(card) function (or modeled attachments as python data model) and I will update the SDK to add your library as an optional dependency and integrate the automatic serialization into messages.create().
Also, have you seen/used the pydantic library?  I am increasing using this and FastAPI for projects.  It could very easily be used to model the Adaptive Cards.  I am considering using it to model the Webex Teams data models in a future release that will support Python v3 (only).  I am also thinking of migrating the library to support both synchronous and asynchronous execution in a v3 release.


Update update-guide.md

need to remove the specific comments made.

This will be updated shortly.


What's the intended use pattern of RelationalDiagnosticSource* messages?

I'm trying to hook MiniProfiler up to Entity Framework Core, but I'm not really understanding what the intended interface is. My understanding is that my best (supported) route is DiagnosticSource, called via RelationalDiagnostics. That's the only path I see to get my hands on the DbCommand, DbConnection, etc. needed for various scenarios.
But the .Write() call for DiagnosticSource is:
public abstract void Write(string name, object value);

The way RelationalDiagnostics uses this passes in a typed object (good), example here:
diagnosticSource.Write(
    BeforeExecuteCommand,
    new RelationalDiagnosticSourceBeforeMessage
    {
        ConnectionId = connectionId,
        Command = command,
        ExecuteMethod = executeMethod,
        InstanceId = instanceId,
        Timestamp = startTimestamp,
        IsAsync = async
    });

...but those types passed are internal, for example here's RelationalDiagnosticSourceBeforeMessage:
namespace Microsoft.EntityFrameworkCore.Internal
{
    // TODO revert to anonymous types when https://github.com/dotnet/corefx/issues/4672 is fixed
    internal class RelationalDiagnosticSourceBeforeMessage
    {
        public Guid ConnectionId { get; set; }
        public DbCommand Command { get; set; }
        public string ExecuteMethod { get; set; }
        public bool IsAsync { get; set; }
        public Guid InstanceId { get; set; }
        public long Timestamp { get; set; }
    }
}

...and some other calls are anonymous objects, for example: WriteConnectionOpening(). So the usage pattern is inconsistent.
How am I supposed to get at the members in an inexpensive way? I'm hoping it's hot intended that everyone use reflection here to get the members, and I can't cast because they're internal. The TODO scares me because that means we have to use the DLR in what should be a code path as cheap as possible. Note: the #4672 issue has since been closed.
Currently I see as far as creating a DiagnosticSource for MiniProfiler and hooking up to logging that way, but not how to use the object passed to the write methods, since I'm unable to access those types.

As an example of why dynamic/DLR access is something I really, really want to stay away from here, I added a quick benchmark of the performance impact (this is .NET 4.6.2, re-runnable benchmark code here):
private static SomeType _type = new SomeType
{
    Foo = nameof(SomeType.Foo),
    Foo2 = nameof(SomeType.Foo2),
    Conn = new DbConn
    {
        Name = "Test",
        ConnectionString = "MyServer"
    }
};
private static object _passed = _type;
public string Casting()
{
    var t = ((SomeType)_passed);
    return t.Conn.ConnectionString;
}
public string Dynamic()
{
    dynamic t = _passed;
    return t.Conn.ConnectionString;
}

Results:

BenchmarkDotNet=v<IP_ADDRESS>, OS=Microsoft Windows NT 6.2.9200.0
Processor=Intel(R) Core(TM) i7-6900K CPU 3.20GHz, ProcessorCount=16
Frequency=3123189 Hz, Resolution=320.1856 ns, Timer=TSC
  [Host]     : Clr 4.0.30319.42000, 64bit RyuJIT-v4.6.1590.0
  DefaultJob : Clr 4.0.30319.42000, 64bit RyuJIT-v4.6.1590.0

Method
Mean
StdDev
Allocated

Casting
0.6203 ns
0.0138 ns
0 B

Dynamic
23.6551 ns
0.7789 ns
0 B

You can use https://github.com/aspnet/eventnotification and SubscribeWithAdapter extension method that generates proxy for you (https://github.com/aspnet/EventNotification/blob/dev/src/Microsoft.Extensions.DiagnosticAdapter/DiagnosticListenerExtensions.cs#L16)

Sample usage in ApllicationInsights MVC diagnostic listener: https://github.com/Microsoft/ApplicationInsights-aspnetcore/blob/develop/src/Microsoft.ApplicationInsights.AspNetCore/DiagnosticListeners/Implementation/MvcDiagnosticsListener.cs

Thanks @pakrym!
@NickCraver please let us know if the suggested approach works for MiniProfiler. Otherwise we can keep looking into it (and also discuss #774 if if really necessary).

@pakrym @divega Thanks a lot for the info and example, there's a lot there but everything seems sane. While I'm not as concerned with the perf given the proxy IL generation in play, I am concerned about the overall interface.
Is there documentation for the parameters available to the listener methods? While I can see from reading source the parameter names on the interface or anonymous type must be matched (unless I'm reading the proxy generation wrong - please correct me if so). How are users supposed to find these parameters or know this? By digging through source code?...or is there a doc somewhere?
I'd feel a lot more at ease that this interface wouldn't break if it was documented/supported somewhere - without that I'm a little uncomfortable. Hopefully there's a doc that Google just isn't finding for me? The only reference I see outside the code that the parameter names need to match was one unofficial blog post...and to find that I was searching with information I gleaned from code.
A concrete example of this would be I searched for ConnectionOpening in the repo (results here), and there appear to be no unit tests. So there's a chance of unwittingly breaking these brittle connection points, IMO - are these fears unfounded?

Assigning to @divega since work involved here is currently to make sure we are doing the right thing.

Opened #8007 for another issue I hit actually trying to hook up here - happy to PR it if someone will take a peek there.

@NickCraver, sorry for the late answer (I am catching up with issues assigned to me). I got this response from @vancem a while ago:

The short answer, is that there is missing documentation.      However realistically DiagnosticSource/Listener will be used by a handful of hard-core ‘profiler/monitoring’ tools, so the number of people who will use this documentation is small.  Also frankly in an open-source world, it is not clear that the docs add much value, since the source is there, and typically there are questions of EXACTLY what the meaning of various events and properties are, which means that people probably will be looking at the source anyway.    Thus fixing this may not be the highest priority for a while.   We should log issues.   My expectation is that this can be solved with a Markdown file in the appropriate code base.
There should be tests for any DiagnosticSource events that have been created.   This is a more serious omission, as was pointed out, it is reasonably likely for them to be broken unless there is some testing.   We should log issues in the appropriate code base to get this fixed.
It is possible to build a tool that ‘discovers’ what DiagnosticSource events exist.    It would not be perfect, as you will have not visibility into an event unless you have a scenario that takes a code path that is instrumented.    Still given a scenario you can discover all the events that that scenario might generate (and their arguments), which would be pretty nice.   This tool does not yet exist however.    I was thinking of adding it to the PerfView tool, but right now it is just a thought…

His answer seems relevant to the discussion you started on https://github.com/dotnet/corefx/issues/18114.
Note for triage: Here what I believe the follow up action items should be on the EF Core side:

Decide what the appropriate level of documentation is for these messages is, e.g. do we want to include them in some sort of documentation or are we ok with profiler tool writers to inspect them or look at the code?
Make sure we our unit test coverage for the events is adequate.

@NickCraver BTW @ajcvickers is working on a bunch of changes in this area for 2.0 which will likely include breaking changes. It would be great if we can devise a way to help you track this work closely, e.g. we can mention you in any PRs.

@ajcvickers to look at what MVC is doing.

There are two basic solutions to reading values out of objects passed with DiagnosticSource.

Use reflection to fetch items.

Standard reflection of course works, as does using the 'dynamic' feature of C#.
You can do efficient reflection (where you end up caching the delegate that does the fetch).   See
https://github.com/dotnet/corefx/blob/master/src/System.Diagnostics.DiagnosticSource/src/System/Diagnostics/DiagnosticSourceEventSource.cs#L784
For a class that does this.    Bascially you could do
static fetchExecuteMethod = new PropertySpec("ExecuteMethod");

Then to fetch the ExecuteMethod field from 'obj' you can do
string s =fetchExecuteMethod.Fetch(obj) as string;

Which should be pretty fast.
However it won't beat casting to a particular type.  If you have need for that the recommendation is that the DiagnosticSource should expose the payload type explicitly (under the System.Diagnostic.DiagnosticSource.Payloads namespace)

We did some investigation and thinking on this today and we have decided to create nominal types for all our payloads. This will mean:

There is a place we can easily document what the types are
Our normal processes for detecting breaking changes will just work without anything special being needed
Consumers can use the payloads in a performant and type-safe manner without needing any proxies,

We talked to @rynowak about the anonymous types/proxies approach that MVC uses and he indicated that  based on what they have learned using nominal types is probably better. As of yet they haven't had anybody really pushing them to change to nominal types, but they would at least consider doing so if there was such a push.

I think having explicit types is very reasonable.
My recommendation is that they call get put into a namespace that ends with 'DiagnosticSource'  Thus
namespace System.Data.YYY.DiagnosticSource {
public class EventXXXData {
string PayloadItem1;
int PayloadItem2;
}
}


Issue in  element wrapped in  element in lesson: http://www.freecodecamp.com/challenges/waypoint-wrap-an-anchor-element-within-a-paragraph

Challenge http://www.freecodecamp.com/challenges/waypoint-wrap-an-anchor-element-within-a-paragraph has an issue.
I marked the code correctly in the text editor and received: "Your a element should be wrapped within your new p element." this.

Went back, and did it again, following instructions a little closer.

KBLST..mind sharing what the issue was ? I am facing the same issue but cant seem to pin point

never mind, i found it.

click here for cat photos


Lint warnings #15

Description

This PR focuses on lint changes in lib/users.
Type of change

Internal change (not necessarily a bug fix or a new feature)

TODOs

[x] Self-review the change
[ ] Perform manual testing
[ ] Address review feedback

Implementation

Performance/Scaling

Testing done

Additional information

Can any of the admins review this?

What is the reason for the u -> c reciever change? Typically they change to match the first letter of the receiver type, but in this case it changes away?

Not sure why I went with c but it was original a tie:
ST1016: methods on the same type should have the same receiver name (seen 86x "c", 89x "u")


Add lightning-network as a topic to this repository

Hello,
This repository is listed on the Awesome Lightning-Network list, which is a collection of useful lightning-network projects. However, it seems that the 'lightning-network' topic is missing from this repository's topics.
Adding the 'lightning-network' topic will help users discover your project more easily and recognize its relevance to the lightning-network ecosystem. To add the topic, please follow these steps:

Navigate to the main page of the repository.
Click on the gear icon next to "About" on the right side of the page.
In the "Topics" section, type 'lightning-network' and press Enter.
Click "Save changes."

Thank you for your attention and for contributing to the lightning-network community!

Updated, thanks!


Feature / healthcheck

Added healthcheck API endpoint.
Closes #81

Codecov Report

Merging #82 (ca2d8cf) into master (afc73d0) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master      #82   +/-   ##
=========================================
  Coverage     99.60%   99.60%
- Complexity      628      629    +1
=========================================
  Files           106      107    +1
  Lines          1790     1792    +2
=========================================
+ Hits           1783     1785    +2
  Misses            7        7

Impacted Files
Coverage Δ

app/src/Controller/HealthcheckController.php
100.00% <100.00%> (ø)

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


openjscad to explicit .stl file without -of says it's outputting stla but outputs stlb

The following invocation of the openjscad command falsely claims it's outputting ascii stl, when in fact it outputs binary stl:
$ openjscad example001.jscad -o example001.stl;  file example001.stl
converting example001.jscad -> example001.stl (STereoLithography, ASCII)
example001.stl: data
In contrast, the following commands all speak the truth about what they are outputting:
$ openjscad example001.jscad;  file example001.stl
converting example001.jscad -> example001.stl (STereoLithography, ASCII)
example001.stl: ASCII text
$ openjscad example001.jscad -o example001.stl -of stla;  file example001.stl
converting example001.jscad -> example001.stl (STereoLithography, ASCII)
example001.stl: ASCII text
$ openjscad example001.jscad -o example001.stl -of stlb;  file example001.stl
converting example001.jscad -> example001.stl (STereoLithography, Binary)
example001.stl: data

Thank you for the bug report @donhatch , I double checked, and that is indeed the case, I'll add a fix asap.


[UI Graphics] -> [RIVE.APP]

[RIVE.APP]
A collection of thousands of Animations and UIs for Mob. Dev.
Link: https://rive.app/explore/popular/trending/all
Checklist:

[ yes ] I have performed a self-review of submitted resource and its follows the guidelines of the project.

I wrote a yes instead of a 'x' in the task lists section by mistake. Sorry Brad! Hope to not repeat it again. Thanks in advance


auto-release respect 'no-release' label

what

auto-release respect 'no-release' label

why

to be able to avoid drafting release when needed (ex. when only readme/docs was updated)

Use the official way: https://github.com/release-drafter/release-drafter#exclude-pull-requests

@osterman My understanding is that only excludes the PR message from the release notes. It does not influence whether or not the release is published.


[fixup] filepath.Walk didn't follow symlink

Prior this patch govendor didn't have the same behavior that other go tools, like go build, GoDeps, ...
This patch fix this issue, by following only the root package transparently.
Test scenario :
ls github.com/kardianos
govendor -> govendor.real/
cd github.com/kardianos/govendor
govendor list

I don't quite understand the motivation for this. I also don't understand the purpose behind the added lines in the resolve.go file. I'm not against this change, I just don't understand. At a minimum, I'd like comments above the lines you added to help explain why this is happening.

Feel free to reopen if you'd like to explain the purpose of this patch, even in a PR comment.

Currently govendor didn't follow symlink, right ...
Now when you are deploying some script (from the CI for example) do the checkout somewhere on your home for example, for many other reason it's more simple to symlink the source (checkout by the CI) to point to $GOPATH/src/$repo
What's the normal behavior (in the symlink configuration)

go list ./...   give you the list of subpackages
godep  works as well

With govendor, govendor return nothing, not even an error, as he didn't follow symlink, even if your current directory is the repo.himself.
So it's clearly a limitation of govendor
This patch correct this behavior

BTW I can't re-open the issue as I'm not a collaborator of this repo.
Regards,

Please do the following:

Create a new issue detailing your issue.

Optionally link to where "go list" evaluates symlinks in the code.

Please give an example repo I can clone on github or similar to test

This will help me evaluate it. Again I'm not disagreeing with you or want to discourage you; I just need to better understand it.

Here is the issue : #199
Regards,


use go-topaz-ui:0.1.15

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

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 0.0%

Totals

Change from base Build<PHONE_NUMBER>7:
0.0%

Covered Lines:
0

Relevant Lines:
0

💛  - Coveralls