[SPARK-4804] StringContext method to allow String references to column names in Catalyst DSL

Now that #3862 has been merged, can we close this issue?


Improved error messages

This includes improved error messages by stripping down the browser-given error message to only two things:

the stack trace (inside of the editor, not dispatch.js or any other gamelab files)
the type of error or message given by the browser.

This also adds the esprima library to check for errors ahead of time because the browser does not give you a stack trace for syntax errors. (Only runtime errors.)
This has been tested on the latest version of Chrome, and works fine. Fixes are needed for Firefox and Safari.
Firefox:

Safari:

It should now be fixed for Chrome, Firefox, and Safari. It might not work anywhere else, though, because error messages are different in every browser. Safari barely gives you any information.

Thanks so much for adding this! Looking great. In the future, please merge into the dev branch.
Can we close https://github.com/hackclub/game-lab/issues/29 now?


Missing matmul of ShapedAttention and Norm

Hi, first of excellent paper. Thank you for the research!
I am looking to make a standalone version of the SAS-P model, and when I went through your code, I could not find any place where you matmul the Norm with the output of Shaped Attention, as indicated in Fig 10. Red circle for convenience. I am not a math guru, but I also can't find this connection in the equations. It kinda makes sense since you experiment with fewer "skip" connections. Thus, maybe this is just a bug in the figures?

I probably missed something, but it would be amazing if you could clarify! :)

Hi, thanks for your interest in our work!
I think the confusion is that the output of shaped attention is the T-by-T attention matrix not a T-by-d representation matrix (for sequence length T and width d), which is then matmulled by the T-by-d value representations. In SAS-P (and also SAS), the value weights are simply the identity matrix (and hence the value representations are just the output of the normalisation layer).
Let me know if that helps :)


Add support for codeowners to repo

Signed-off-by: Ryan Bogan<EMAIL_ADDRESS>Description
Add support for codeowners to repo
Issues Resolved
Progress on:
Meta issue
Check List

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

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

@ryanbogan Amy updates on this? Looks like it is lying stale since a long time here.

I used the same formatting for every repo and did not encounter any problems so I do not believe that the spacing matters.

@bbarani please approve.
Thanks.


Email quickstart resulting in error 534-5.7.14

Turned on Google auth, deployed app: https://functionstest-c1518.firebaseapp.com/
When logging in, I get the following error in the Function log:
Error: Invalid login: 534-5.7.14 <https://accounts.google.com/signin/continue?sarp=1&scc=1&plt=AKgnsbs7
534-5.7.14 UF7mumzUwFIZrMDWiiimSdrlEvZIp8kRC3QRkzqwfOM94wkvVFys_Yjllj6KGuBubi6SwF
534-5.7.14 BDIHCpQgETRmmgkyJXfYN4Ne3uG3tnsVJk7oGR4Z5fvgeIkuOJOKkvRA8cLWFN67ya4r28
534-5.7.14 u-eBDds9bTTh1poYtxXWk1x80iaSn_2VlJHWJnB0Yql6r_-A2lDE8nt00lWP7eoUpkzVih
534-5.7.14 x1DeI0bGyNqNHRRUuucw0k95Ph-CY> Please log in via your web browser and
534-5.7.14 then try again.
534-5.7.14  Learn more at
534 5.7.14  https://support.google.com/mail/answer/78754 100sm8943270iot.39 - gsmtp
    at SMTPConnection._formatError (/user_code/node_modules/nodemailer/node_modules/smtp-connection/lib/smtp-connection.js:528:15)
    at SMTPConnection._actionAUTHComplete (/user_code/node_modules/nodemailer/node_modules/smtp-connection/lib/smtp-connection.js:1231:30)
    at SMTPConnection.<anonymous> (/user_code/node_modules/nodemailer/node_modules/smtp-connection/lib/smtp-connection.js:319:22)
    at SMTPConnection._processResponse (/user_code/node_modules/nodemailer/node_modules/smtp-connection/lib/smtp-connection.js:669:16)
    at SMTPConnection._onData (/user_code/node_modules/nodemailer/node_modules/smtp-connection/lib/smtp-connection.js:493:10)
    at emitOne (events.js:96:13)
    at TLSSocket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:176:18)
    at TLSSocket.Readable.push (_stream_readable.js:134:10)
    at TLSWrap.onread (net.js:548:20)

From the support article in the error code, I enabled access for less secure apps here: https://www.google.com/settings/security/lesssecureapps and also allowed access to DisplayUnlockCaptcha here: https://accounts.google.com/DisplayUnlockCaptcha
Welcome and Bye emails are both working now!

Perhaps the docs could be updated to reflect these two (probably) required steps.

Thanks @markgoho. You are probably right, I'll add these steps. Were you using a gmail account? Or a GSuite account?

@nicolasgarnier gmail account to send the emails.

I am 100% sure I am using the correct password (I tried a GSuite account and a regular gmail account) and I have enabled less secure apps and authorized the captcha. Still getting: There was an error while sending the email: { Error: Invalid login: 535-5.7.8 Username and Password not accepted.

@carlosdelamora
I have also enabled both 1. & 2.
After a few hours I start getting an error: "Error: Invalid login: 534-5.7.14"
After Enabling 2. again, gmail login is successful.
Did you resolve the issue with enabling https://accounts.google.com/DisplayUnlockCaptcha again?


Litarvan Theme Navigation Issue

Hi
So I installed this Theme via AUR (V 3.0.0) and I am using the nody-greeter for the same. While loading the theme, the user icon is not present and neither the icons for WM (Qtile) is present. Also while trying to navigate back from the user page, I get a JS Error regarding navigation.

Do I need to upgrade to version 3.2.0? If so Do I need to remove the earlier zip package present in these paths usr/share/lightdm-webkit/themes/litarvan to /usr/share/web-greeter/themes/litarvan?

It is recommended to always use the latest version, however web-greeter and nody-greeter support was introduced in November 2021, while v3.2.0 is from April 2021; therefore, you would still have issues with v3.2.0. So, I recommend to use the master branch instead.

So I cloned the repo and executed the build.sh script. I also deleted the litarvan theme installed via AUR and then extracted the new theme to /usr/share/web-greeter/themes/litarvan. In the debug menu, the themes work correctly and the icons etc everything is getting rendered correctly. But when I switched on the theme again, I get this

The settings that I have enabled is:

Disable Avatar Picture
Show 12 hr Time
Remove username when name is known.

I wanted to know why is the username not in the center and the issue with the missing icon.

The missing icon is, in fact, your non-existent user icon. So, this means that the Avatar Picture is not actually disabled; you could try to enable and disable it again.
In the following video, you can see my user account with an icon on the left, and another user account without an icon that, when selected, looks exactly like your image above. As you can tell, the Avatar Picture is not disabled, so I just disable it to center my username and remove the Avatar picture.
https://user-images.githubusercontent.com/59768785/181592749-940a3a2a-9083-4671-b061-e6235766ba81.mov


Dircon Rework

This is not anywhere near ready to merge yet, but it'd be good to get feedback on the DirconMode API, as Dircon programs will be entirely specified by one or more DirconMode objects. Comments should focus on dircon_mode.h and, to a lesser extent, dircon_mode.cc

Closing this PR, will reopen when ready for review.


feat: add background image

Did you make that image? pretty cool, way better than mine lol.
if we are going to use this image, maybe we should change it a little bit to be more aligned with green/blue with accents of purple, or do you think the contrast would be too weird?
although I do like this a lot, if we changed this one to be more color scheme looking then I will just change the logo for the entire org
let me know what you think

[ ] also can you update README to show what it looks like with the image set thanks!
[ ]  possibly change image colors, then we can make this the main logo?


RC Test: Gravity Force Lab: Basics 1.1.0-rc.2

@emily-phet, @terracoda, @KatieWoe gravity-force-lab/1.1.0-rc.2 is ready for RC testing. This is the FIRST RC, but this build is rc.2 because of an error in the build request of rc.1 We are hoping to publish this sim by the end of this quarter. Document issues in https://github.com/phetsims/gravity-force-lab-basics/issues and link to this issue.
This sim includes all accessibility features including Voicing, Screen Reader support, Interactive Highlights, Pan and Zoom, iOS Accessibility, and sound. It does not include PhET-iO.
Assigning to @kathy-phet and @KatieWoe for prioritization.

General RC Test

What to Test

Click every single button.
Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.

If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Test all query parameters on all platforms. (See QA Book for a list of query parameters.)
Download HTML on Chrome and iOS.
Make sure the iFrame version of the simulation is working as intended on all platforms.
Make sure the XHTML version of the simulation is working as intended on all platforms.
Complete the test matrix.
Don't forget to make sure the sim works with Legends of Learning.
Test the Game Up harness on at least one platform.
Check this LoL
spreadsheet and notify AR or AM if it not there.
If this is rc.1 please do a memory test.
When making an issue, check to see if it was in a previously published version.
Try to include version numbers for browsers.
If there is a console available, check for errors and include them in the Problem Description.
As an RC begins and ends, check the sim repo. If there is a maintenance issue, check it and notify developers if there is a problem.

Link(s)

Simulation
iFrame
XHTML
Test Matrix

Accessibility (a11y) RC Test

What to Test

Specific instructions can be found below.
Make sure the accessibility-related feature that is being tested doesn't negatively affect the sim in any way. Here is a list of features to supported in this test:

Alternative Input
Interactive Description
Sound and Sonification
Pan and Zoom
Mobile Description
Self Voicing

Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.
Test all keyboard navigation inputs (if applicable).
Test all forms of input with a screen reader (if applicable).

Focus and Special Instructions
[Provide further instructions here. If you have any further tests you want done or specific platforms you want tested,
list them here. Any behaviors you want QA to pay special attention to should be listed here.]

Link(s)

a11y View
Simulation
Test Matrix

Screen Readers
This sim supports screen readers. If you are unfamiliar with screen readers, please ask Katie to introduce you to
screen readers. If you simply need a refresher on screen readers, please consult the
QA Book, which should have
all of the information you need as well as a link to a screen reader tutorial made by Jesse. Otherwise, look over the
a11y view before opening the simulation. Once you've done that, open the simulation and make sure alerts and
descriptions work as intended.

Platforms and Screen Readers to Be Tested

[x] Windows 10 + Latest Chrome + Latest JAWS
[x] Windows 10 + Latest Firefox + Latest NVDA
[x] macOS + Safari + VoiceOver
[x] iOS + Safari + VoiceOver (only if specified in testing issue)

Critical Screen Reader Information
We are tracking known screen reader bugs in
this Google Document. If you find a
screen reader bug, please check it against this list.

Keyboard Navigation
This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a
screen reader.
Magnification
This sim supports magnification with pinch and drag gestures on touch screens, keyboard shortcuts, and mouse/wheel controls. Please test magnfication and make sure
it is working as intended and well with the use cases of the simulation. Due to the way screen readers handle user input, magnification is NOT expected to
work while using a screen reader so there is no need to test this case.
Final Requests

[x] If this sim is not in this list or up to date there, make an
issue in website to ask if PhET research page links need updating. Please assign
to @terracoda and @emily-phet.

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

Memory test results:

QA is done


Invalid image name when use image with tag is number

Describe the bug
I tried to deploy my image with tag is number. Causing Kubernetes pod status to be InvalidImageName
Version of Helm and Kubernetes:
Helm version:
Client: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}

What happened:
Image:
khainguyendinh/dotnet:45980468

Output:
NAME                   READY     STATUS             RESTARTS   AGE
dotnet-dddb74c6d-9n48w   0/1       InvalidImageName   0          5m

Describe pod:
Events:
  Type     Reason          Age                From                                             Message
  ----     ------          ----               ----                                             -------
  Normal   Scheduled       6m                 default-scheduler                                Successfully assigned test/dotnet-dddb74c6d-9n48w to gke-demo-ci-default-pool-62e9718a-z0
x4
  Normal   SandboxChanged  6m                 kubelet, gke-demo-ci-default-pool-62e9718a-z0x4  Pod sandbox changed, it will be killed and re-created.
  Warning  Failed          4m (x12 over 6m)   kubelet, gke-demo-ci-default-pool-62e9718a-z0x4  Error: InvalidImageName
  Warning  InspectFailed   56s (x27 over 6m)  kubelet, gke-demo-ci-default-pool-62e9718a-z0x4  Failed to apply default image tag "khainguyendinh/dotnet:4.5980468e+07": couldn't parse i
mage reference "khainguyendinh/dotnet:4.5980468e+07": invalid reference format

What you expected to happen:
Support image with tag is number.

I've confirmed this using "helm template". I've also verified this is a Helm issue (not kubectl etc)

Even I am able to reproduce the issue with this chart - issue-5768.tar.gz , by doing helm template
I am able to reproduce with v2 and v3 too -
$ helm version --client
Client: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}

$ helm3-alpha version
version.BuildInfo{Version:"v3.0.0-alpha.1", GitCommit:"b9a54967f838723fe241172a6b94d18caf8bcdca", GitTreeState:"clean"}

@khainguyen95 @jdolitsky I don't know if I can entirely say this is a helm issue. Like, when I use the number 459804, the tag number comes correctly, but when I put 45980468 the image name along with tag shows up as khainguyendinh/dotnet:4.5980468e+07.
I think there's been some mishandling of the values.yaml when numbers are big - variables not being able to store big numbers as is? so they are being stored in scientific notation?
I have a small solution to this actually, instead of trying to make changes in helm, if we put the tag in quotes, then it works! That is, like this:
image:
  repository: khainguyendinh/dotnet
  tag: "45980468"

This way, the tag is treated as a string and not a number, and hence it's not represented in scientific notation (using e+ and stuff)
@khainguyen95 @jdolitsky Let me know what you think about this!

At first glance, this appears to be a duplicate of #1707. Can you check and confirm if that's the case here?

@bacongobbler yes, that's the issue - number getting converted to scientific notation representation. But idk where the values is coming from in this issue, --set or --values

@karuppiah7890 Thanks for the confirmation. Closing this issue as a duplicate of #1707.


No fullscreen modal

Let's say you have an iPad app witch is splitting the screen in two (like multitasking). In the current state of Presentr, if I present a viewController on the left side, I will be able to customise my origin and size, but the PresentrController frame will still use the screen frame instead of filling only the presentingViewController frame.
The result expected would be the same as using presentedVC.modalPresentationStyle = .OverCurrentContext.
I will take a look in the day if I have time, otherwise, I'm really interested in this feature 😄

I just edited the app example to give a more visual example:

Default view when launching app
When clicking on "present", it will present an alert, here the issue: I'd like to present only on the yellow and keep the green one clickable

I look into this, it seems more complicated that I though. In order to have this result, we have to set the modalPresentationStyle to OverCurrentContext, but presentationControllerForPresentedViewController is working only and only if the modalPresentationStyle is Custom. So right now, I have only one solution in mind

Don't use anymore UIPresentationController and handle all that stuff in it manually using  UIViewControllerTransitioningDelegate. Definitely not worth it
Find a good idea to handle everything together 😆

I didn't find examples about how to implement that features, but if anyone has a suggestion, I'm interested!

I was about to suggest using a custom PresentationType to set a custom origin/size, but now that I read it I realized that's not the issue. The issue is not the presented view controller itself, but the chrome/background view.
So basically, this issue would appear on ipad when doing multitasking or when doing view controller containment, or like a split view controller.
So, there are two issues, correct?

The chrome/background view should only cover the current/presenting view controller.
and the uncovered view controller should be clickable.

The .overCurrentContext is what usually makes the background clickable, right?
Will def. look into this, we can keep discussing it, and implement something as soon as we come up with a solution.

You did understand right the issue, it's concerning any apps which split the window in different controllers, as you said, that bring to these two issues.
I just watch the WWDC session about PresentationController to have a better understand of how it is working. Following that, we just have to use the right context when presenting the viewController. Normally shouldPresentInFullscreen handles this:

If true, it will use the fullscreen and adapt the view automatically
If false, it will use the presentingVC context, so keeping the same frame (which will give the right frame to the chrome view, and also make clickable the uncovered view)

So the real question is why shouldPresentInFullscreen has no effect on the presentedView 😆
I pushed the example that I'm using to do my tests, you can find it in my fork.

For information, I think I misunderstand what's the real purpose of shouldPresentInFullscreen. Apparently, it won't change the context of the presentedVC but used to enable or not UIPresentationController's adaptive* methods which are used to change the presented content following traits...
Well, there must be a way to handle this, but it will be for later!

@tbaranes I sent a pull request with this feature. You can try checking my fork.

I took a quick look on it, I dont think that will introduce the feature expected from this issue. The expected behaviour is to present a view controller over the current context instead of being in fullscreen. Did I miss something?

@tbaranes You are right. I misread because of the title.

@tbaranes If I understood you correctly what is necessary to do is to create the viewport of the modal based on its context's viewport. So in your example, that yellow viewController will be the context and its viewport will be used to create and render the modal. This way will achieve what you are looking for.

Well, I tried that way too, but never find any working solution. If you find it, I'm really interested :D

@tbaranes I'm pretty sure this way will work.
I'm going to implement a simple way to achieve this result and hopefully add it for the next release!

Looking forward for this release 😬

@gabrielPeart Did you try to make this working?

@tbaranes not yet. Sorry about that. Have been extremely busy.

@tbaranes @gabrielPeart I think I finally cracked this!
Have been extremely busy lately, but I finally have a couple of days to work solely on open source stuff. This was one of the first things on my to-do list.
@tbaranes Yeah, the "shouldPresentInFullscreen" property of UIPresentationController is of no help, and since in order to get the functionality you need you would need to set the UIModalPresentationStyle to .currentContext or .overCurrentContext, that is not possible because we are using the .custom presentation style.
Therefore this feature needed to be implemented from the ground up. The result looks like so:
        presenter.viewControllerForContext = self
        presenter.shouldIgnoreTapOutsideContext = true
        customPresentViewController(presenter, viewController: alertController, animated: true, completion: nil)

You have to set viewControllerForContext property, in which I use the controllers frame (with some corrections) to set a "context frame", which is hidden from the user. This should ideally be done before a presentation and not in a viewDidLoad because it needs to give a chance to autolayout to have set all frames correctly.
The other optional property is shouldIgnoreTapOutsideContext , the default is false. That means that a tap outside the context frame will be listened to, and will dismiss the presented controller. If this is set to true, then taps on the outside context will be passed along to the other view controller.
This still needs some testing and bug fixing, specially since I had to refactor how animations work to get some of this stuff working hehe, BUT if you checkout the development branch you can checkout the example project to see it in action. Scroll down to the last section where it says "current context" and a split view / container controller situation will show up.
Thanks for your patience! 👍

If any bugs come up we can start a new issue.

@danlozano great work! Thank you!

Woh, happy to hear that! I will try it this morning, thanks!

Sorry for the delay, I just test it, it's working as expected, impressive! Thanks for looking into this 👏

Awesome!
Release v 1.2.1 is out.
Had to release a quick .1 bug fix on PresentrShadow.


String manipulation performance improvements

This PR contains three minor performance optimizations:

Precompile pattern for unescaping attributes in ResourceUtil
Improve implementation of Strings.join
Replace custom implementation of replace in Strings.replaceAll with JDK's String.replace

The implementation of String.replace in recent JDK versions is 2-3x faster than Wicket's current custom version:

Benchmark
Mode
Cnt
Score
Units

StringsBenchmarks.replaceAllNew
thrpt
3
26823346,762
ops/s

StringsBenchmarks.replaceAllOld
thrpt
3
10294555,601
ops/s

Strings.join is about 40% faster after my minor tweaks:

Benchmark
Mode
Cnt
Score
Units

StringsBenchmarks.joinNew
thrpt
3
10444112,760
ops/s

StringsBenchmarks.joinOld
thrpt
3
7695290,533
ops/s

Thanks @svenmeier and @solomax!


Add option to disable mod on servers

Many servers have a 'Hub' or 'Lobby' to which the player is taken to every time they join the server. Because of this, every time I leave a server, the place where the screenshot was taken is not where I will be when I rejoin the server.

This already can be done, though maybe better worded. If you go into the server settings, there should be an option called "Custom Screenshot". When this is turned on, it doesn't take a screenshot on closing. The original intention was for you to take a screenshot of the hub itself, but you can also turn on the option and just delete the screenshot already existing (if there's one), which in effect disabled it

Given that, I can also add a disable button to be straightforward.

Yeah, another possibility could be a button that cycles between 3 options:

On/Enabled
Frozen/Custom
Disabled

Will be in the next release (commit)


More footprint fixes, from gis size vs square foot ratio analysis

Mike finally finished the footprint review based on analysis in #102
I saved his XLSX here:
https://docs.google.com/spreadsheets/d/1-3XT03AWcwHQU5NLgVtOA9Zkfb8Krunc?rtpof=true&usp=drive_fs
Looks like about 140 building IDs somehow implicated in fixes, with the usual sketches of varying legibility describing what's needed.
No huge rush on this, though sometime while I'm away would be nice (before 10/23).
Just let @tomay know when updates or ready, or if you have questions that need to route back to Mike, he can facilitate that. Also fine if you wanted to join a client call to discuss anything.
Notable: Mike said about half the buildings we highlighted with the ratio analysis were real errors, so he was pretty pleased with this method of detection.
┆Issue is synchronized with this Asana task

Excellent, I will start this next week. Glad the footprint ratio analysis was useful.

@tomay I finished updating the footprint outlines for this round. I had a couple of questions that I highlighted in the "fixes" tab of the sheet in magenta (yellow indicates successful check/update). But overall I think I was able to interpret things pretty well. Let me know if there is anything else you need from me for this since Dan is out!
Here is the file path: P:\proj_p_s\Seattle Building Dashboard\2024_update\seattle_building_outlines_20241009

Got clarification from Mike, he confirmed my interpretation for 565 and 27554 and I went back and removed the extra buildings from 26098. This should be ready to go now.

These have been updated on CARTO


Feature/gifs

Description
What is the intent of this change and why is it being made?
How Has This Been Tested?
What testing have you done to verify this change?

@luke-hagar-sp Please resolve the merge conflicts.

@colin-mckibben-sp conflicts are resolved


Supervised Contrastive Learning

https://arxiv.org/pdf/2004.11362.pdf
It would be great to have this paper implemented in Jax.
Thanks for the great work.

Hi, thanks for the suggestion! It would indeed a natural step as a follow-up notebook to SSL.

dear sir, Thank you very much for your informative repo. Please guide me how to implement GNN for text classification on custom dataset


chore: nodejs-hello-world to 0.0.4

chore: Promote nodejs-hello-world to version 0.0.4

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
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

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


PHP comment block is not highlighted

This comment:
  /**
   * Create a new command instance.
   *
   * @return void
   */

Renders as:
/**
   * Create a new command instance.
   *
   * @return void
   */

So only first line is part of comment.

I do not reproduce this issue on the Test drive page...

Sorry i should have test that page first. It's a problem on my own :)


documentation link to Landsat example notebook broken

Under the "interactivity" heading in this documentation page:
http://datashader.org/user_guide/5_Rasters.html
There is a link to the following url:
http://datashader.org/topics/Landsat.html
which returns a 403 forbidden error

Links should be all lowercase it seems: http://datashader.org/topics/landsat.html

Thanks; should be fixed now!  I thought we had a link checker running, but it must only be making warnings during doc builds, not errors...


nginx(Mainline|Quic): 1.25.0

Description of changes
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

considering it's mainline now and h3 is no longer experimental, would it make sense to build the http3 module by default?

considering it's mainline now and h3 is no longer experimental, would it make sense to build the http3 module by default?

Then have to use quictls instead of openssl in nginxMainline. And then in nginxStable version as well.

It's still experimental: https://hg.nginx.org/nginx/rev/12dcf92b0c2c
How well is quictls maintained in nixpkgs? Apparently this should also work with openssl (see https://hg.nginx.org/nginx/rev/bddd3f76e3e5), but not sure which version we'd need for that. Maybe 3.2?

I periodically update quictls package. OpenSSL 3.1 does not support QUIC. Judging by roadmap they plan to fully implement the protocol by version 3.4.

Ok, so we should look into that again once openssl has h3.


Upgrade joda-time to 2.0

Any plans for this?
Sayeth the homepage:

Version 2.0 is almost completely source and binary compatible with version 1.x. Key changes include the use of JDK 1.5 or later, generics, and the removal of some (but not all) deprecated methods. See the upgrade notes for full details including information on the corner cases that are not compatible. Applications should be able to drop version 2.0 in place of an earlier version without any issues providing they are using JDK 1.5 or later and are not using one of the deprecated methods. Please let us know if a corner case hits you, especially if Joda-Time is a dependency of another open source project.

I only ask because I can't seem to find the javadocs for 1.6 online. :/

+1

+1


Firestore cloud function not available on  Location

I am setting a new Firebase Firestore cloud for my project. I am from India and requires South-Asia1 for location But this location is having problem like cloud functions not enabled.
What should I do now, Should I go with my SouthAsia1 or change to nearest CloudFunctions location.

What does it mean that  Deploying a function to this location is not yet available.
I am using firebase on android with flutter.

Hi @Abhishek-kumar09, it means that Cloud Functions is not yet available in "asia-south1" location. If you're going to use Cloud Functions, the nearest region that can be used for it is "asia-east2". You may check out this documentation for more info.
You may also file on Firebase Support page to better assist you with questions regarding this.

So I should go with SouthAsia1 or asia-east2.As it is saying once i pick a location that cannot be changed

Can I have my firestore location and cloud function location different
thanks @rizafran

Hi @Abhishek-kumar09, as I've mentioned earlier, if you're going to use Cloud Functions, you'll need to use "asia-east2" which is the nearest region available in "asia-south1" (Mumbai). Take note that you could potentially experience increased latency and billing costs if your function and resource are in different locations.
If you're going to use Firestore only, then you can go with "asia-south1".


Pictures eventually require re-authentication

Setting HA 0.73 Lovelace picture-glance "image" to a Blue Iris camera feed (ex. http://BI_IP:BI_PORT/mjpg/CAMERA_NAME/video.mjpg?username=USER_NAME&password=USER_PASSWORD) works initially but later causes the image to disappear until eventually the browser prompts for the USER_NAME and USER_PASSWORD to the BI_IP (after which the image reappears).
This shouldn't happen since I'm providing the credentials through the url.

We don't support camera streams there, use camera_image instead

camera_image shows images every x seconds while image shows a real time camera feed


bso bug on dueling

🐛 Bug Report
Write a description of the bug here, give all the information you can about what it is, how it happened.
Tried dueling a friend on our server, he is banned for autotyping I believe. But I could still duel him, eventhough he can't type commands etc. But he can accept the duel.
I tried dueling for 1m and won. It's basically a 50/50 dice. Better odds than using =dice.
Tried it just to make sure, if he was talking bs 🤣

Blurred his name, since the name could be seen as pretty offensive...


laravel-mix scripts() and styles()  not watched

Laravel Mix Version: 0.8.8 (npm list --depth=0)
Node Version (node -v): v6.9.5
NPM Version (npm -v): 3.10.10
OS: win10 NT

Description:
I have the scripts() used as follow:
mix.scripts([
    'resources/assets/plugins/emoji/js/emojiUtil.js',
    'resources/assets/plugins/map/map.js',
    'resources/assets/plugins/helper.js'
 ], 'public/js/plugins.js');

when I change any one of these js file, watch or watch-poll both are not working and I have unchecked the safe writing of phpstorm.
any one please help me!!!
Steps To Reproduce:
...

Can you try bumping to Laravel Mix 1.0 and trying again? You're on a pretty old version.

I think I have the same issue with mix 1.0.7...

Okay it's a bit weird, when changing my less files the notifier etc is triggered and I see the compiling on my console. But when changing my js files this does not happen, it seems to update though.
This is my webpack file
mix.options({
    processCssUrls: false,
    purifyCss: false,

    postCss: [
        require('postcss-discard-comments')({
            removeAll: true
        }),

        require('autoprefixer')({
            browsers: ['last 2 versions', '> 1%']
        })
    ],

    uglify: {
        comments: false
    }
});

mix.less('resources/assets/less/production.less', 'public/assets/css')
    .scripts([
        paths.jquery + '/jquery.js',
        paths.bootstrap + '/bootstrap.js',
        paths.bootstrap + '/ie10-viewport-bug-workaround.js',
        paths.scripts + '/scripts.js'
    ], 'public/assets/js/app.js')
    .scripts([
        paths.scripts + '/moment.js',
        paths.scripts + '/fullcalendar.js',
        paths.scripts + '/fullcalendar-nl.js',
        paths.scripts + '/daterangepicker.js',
        paths.scripts + '/jstree.js'
    ], 'public/assets/js/admin.js')
    .version();


I can't inject dll into the system informer process

Brief description of your issue
Cant inject dll in system informer process
I tried to inject any dll but it just doesn’t want to work and doesn’t show up in the modules
Does the system  informer have injection protection or what?
Steps to reproduce (optional)
No response
Expected behavior (optional)
No response
Actual behavior (optional)
No response
Environment (optional)
No response

btw my injector tries to load the dll immediately after the process starts, I set a delay of 1 second and then it doesn’t load, but if without a delay, that is, constantly scan the system for the presence of a process and inject right at the moment of startup, then the dll will still load. I came to the conclusion that the minimum interval is around 100 milliseconds

Cant inject dll in system informer process

Windows requires signed images


BitSum.ProcessLasso.Beta version <IP_ADDRESS>

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Here you type BitSum and in this pr #15120 you type BitsumLLC why create duplicate Publisher?

Apologies updated publisher on other submission

Also it would be better for PackageIdentifier to be BitSum.ProcessLassoBeta instead of BitSum.ProcessLasso.Beta, because if you give a . (dot) it will create a subdirectory


[rom-e2e] rom_e2e_asm_watchdog

Testpoint name: rom_e2e_asm_watchdog
Contact person: @alphan
Description: Verify that watchdog is initialized in rom_start.S.
CREATOR_SW_CFG_ROM_EXEC_EN should be set to 0 and the chip should in a life cycle
state where debugging is enabled, i.e. TEST, DEV, or RMA.

Connect a debugger.
Set breakpoints on right after watchdog is initialized in rom_start.S and the asm
handler.
Wait until execution breaks at the first breakpoint, wait ~1s before continuing.
Verify that watchdog expires and execution breaks at the asm handler.

@alphan I think the goal is to test that the watchdog's bark (not bite) generates an interrupt that throws us into _asm_exception_handler. If that's right, I see a couple issues:

Interrupts are disabled.
The bark threshold is set to the highest value. (See rom_start.S:159-167.)
Because of (1) and (2), the bite happens before the bark, causing the core to reset. I believe this resets the debug module as well, causing OpenOCD to lose its connection.

I can potentially write a test that writes different bite and bark thresholds, but it's becoming more of a hardware test and less of an E2E ROM test. WDYT?

Discussed offline.

I just did the crudest possible test and confirmed this is working. If I enable the NMIs from the watchdog and swap the bite and bark thresholds, a GDB test can force execution by setting PC (after the wfi) and then check that it hits a breakpoint on _rom_start_boot, which is the NMI handler.

Disregard that, my test was flawed. I'm still having trouble hitting the NMI handler with the debugger.


Improve default display when no NCCN guildeline is provided

Currently the display is () for what I believe is an AID without an NCCN guideline associated. I don't know off what is the preferred language for when an entity has not been provided yet but can be curated.

This is actually an odd case, where the assertion is associated with an actual nccn guideline object in the database, which has a name of "". I think we might just want to delete this nccn guideline, since I doubt we meant to create it in the first place. I wonder if you would be able to remove this nccn guideline through the edit assertion form.

I fixed the underlying data issue. The NCCN guideline now show as None Provided.


Improve code quality on GCM mode

Addresses #78, except for making the spec literate (moved to #87).
This PR aims to improve the code quality, documentation, and NIST spec adherence of GCM mode (and its instantiations for AES). It builds on the paradigms (using CipherInterface) added in #83.
I identified all the issues that I addressed here; if others would like to take a pass of the NIST spec and/or this implementation and identify other areas for improvement, I would welcome that feedback.

I have one open / blocking question: There's a duplicate version of AES256-GCM in the repo. It looks like AES_256_GCM.cry is used in the aws-lc-verification repo. Should keep what I assume is a SAW-optimized version of the spec in this repo? It's not written with respect to the NIST spec (I assume because the NIST spec is not efficient) and I would have to spend some time to audit it and determine whether it's the same as the other version we have.
I believe there are several other cases where this repo contains duplicate, SAW-optimized versions of algorithms. I'm looking for guidance on what to do in these cases. The options I see are:

Remove the SAW-optimized versions from the repo; perhaps move them to another location. Add documentation somewhere at the top level of cryptol-specs to note that this repo aims to add spec-conformant versions of algorithms and they may need to be optimized much more to be used in conjunction with SAW / to actually verify an implementation.
Keep the SAW-optimized versions in the repo. Add documentation on each version explaining the use case; add docs at the top level of cryptol-specs to explain the need for multiple versions of things.

Pinging @RyanGlScott and @mccleeary-galois specifically; others also welcome to weigh in.

Right, there are various technical reasons why aws-lc-verification needs a very bespoke Cryptol specification for AES-GCM. In fact, not all of aws-lc-verification's Cryptol code is contained in cryptol-specs, as there are even more Cryptol files in the aws-lc-verification repo that make use of things like SMT arrays. One could make the argument that all of these bespoke Cryptol files should live in aws-lc-verification, but that's not currently the case.
I could be convinced either way on whether we should keep the bespoke code or remove it. I like the idea of making cryptol-specs contain spec-conformant code, so if we do keep the bespoke code, we should prominently advertise why it does something different.

Right, there are various technical reasons why aws-lc-verification needs a very bespoke Cryptol specification for AES-GCM. In fact, not all of aws-lc-verification's Cryptol code is contained in cryptol-specs, as there are even more Cryptol files in the aws-lc-verification repo that make use of things like SMT arrays. One could make the argument that all of these bespoke Cryptol files should live in aws-lc-verification, but that's not currently the case.

Indeed, all bespoke Cryptol and SAW should live somewhere else.  If we are "convinced" that some of it remain, e.g., if we are given permission to share similar work on HIPERSPACE that demonstrates how to assured that such refinement chains are valid, then we can choose to put those either in cryptol-specs or some as-of-yet-not-in-existence cryptol-use project/repository.

I could be convinced either way on whether we should keep the bespoke code or remove it. I like the idea of making cryptol-specs contain spec-conformant code, so if we do keep the bespoke code, we should prominently advertise why it does something different.

Exactly.  I'd prefer that we do not keep anything that is relevant to a specific client or project in cryptol-specs.  Let's get it all moved elsewhere, and notify current and past clients that this is happening.

@marsella is going to do a quick audit to see if the best course of action for the SAW optimized specs. We will either move them into their respective repos or create a new repo cryptol-use or equivalent if it appears to be easier to just dump them into a new repo.

I made #88 to follow up on the optimized specs.


Cypress. Exclude some files from instrumentation.

Motivation and context
Increase code coverage by about 1%

File name
Comment

/cvat-ui/src/actions/models-actions.ts
The code is not called in the standard CVAT build

/cvat-ui/src/actions/boundaries-actions.ts
If the application is running correctly, the code is not called.

/cvat-ui/src/containers/models-page/models-page.tsx
The code is not called in the standard CVAT build

/cvat-ui/src/reducers/models-reducer.ts
The code is not called in the standard CVAT build

/cvat-ui/src/utils/platform-checker.ts
Measure coverage conducted on a supported platform

How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below)

# Copyright (C) 2021 Intel Corporation
#
# SPDX-License-Identifier: MIT

@dvkruchinin , could we include testing of the page with models?

@nmanovic

could we include testing of the page with models?

Yes. I think it will be enough to change the CVAT build command in CI.

@nmanovic

could we include testing of the page with models?

Yes. I think it will be enough to change the CVAT build command in CI.

Let's do that in the case instead of excluding files from the coverage report.

Let's do that in the case instead of excluding files from the coverage report.

Ok.
But I think it's worth keeping the files
/cvat-ui/src/actions/boundaries-actions.ts
/cvat-ui/src/utils/platform-checker.ts

Since they will not be covered

Let's do that in the case instead of excluding files from the coverage report.

Ok.
But I think it's worth keeping the files
/cvat-ui/src/actions/boundaries-actions.ts
/cvat-ui/src/utils/platform-checker.ts

Since they will not be covered

Agree


[Bug]: Borders shown when they should not in 2022.5

Current Behavior
In 2022.5 it seems that borders are shown in cards like custom:vertical-stack-in-card for mushroom cards:
Example code:
square: true
columns: 2
type: grid
cards:
  - type: custom:vertical-stack-in-card
    cards:
      - type: custom:mushroom-entity-card
        entity: light.groep_woonkamer
      - type: custom:mushroom-entity-card
        entity: light.groep_woonkamer
  - type: custom:vertical-stack-in-card
    cards:
      - type: entity
        entity: light.groep_woonkamer
      - type: entity
        entity: light.groep_woonkamer

Result

The card using normal entity cards is rendered correct without borders, while the one with the mushroom cards still shows borders between the individual cards.
Expected Behavior
No borders :)
Steps To Reproduce
See code above
Environment
- OS: HA OS 8.0 rc3
- Broswer: Chrome
- Hassio: 2022.5.0b2

Anything else?
No response

Hi,
vertical-stack-card search a ha-card in the shadow root node but with mushroom we have a mushroom-card before so it's doesn't work

Fixed by #417


New initialization model

After talking with Jason Turner regarding libembeddedhal, he recommended that we eliminate 2-phase initialization and that we initialize in our constructors to prevent the obvious issues that would occur if a user executes a call to a driver before it has been initialized.
The idea that we came up with in our call was to utilize the factory functions for drivers as a place to not only construct the objects but also initialize them. For example:
template<int channel>
embed::lpc40xx::i2c & embed::lpc40xx::get_i2c(
  std::optional<embed::i2c_settings> p_settings = nullopt)
{
  static embed::lpc40xx::i2c i2c_object;
  if (p_settings) {
    i2c_object.settings = p_settings.value();
  }
  i2c_object.initialize();
  return i2c_object;
}

auto & i2c = embed::lpc40xx::get_i2c<1>();

In this way, you access which driver you need by using the get_i2c<N>() function and it gives you an initialized driver. This has implications that changes how the whole initialization scheme is done. And makes me reconsider how initialization is performed throughout the code base. Maybe drivers that use I2C shouldn't initialize them and should assume that they are already initialized when they are passed in. This eliminates a bunch of code checks for drivers, reducing code size.
The concern comes in for ordering of constructors if you were to call this in a global context. It would be interesting to see if there is a way to detect this and do something about this at compile time.

Resolved by #96


Added Dockerfile

Added Dockerfile and command to regenerate the template to the readme install instructions.

think you could optimize the Dockerfile (less layers)
FROM ubuntu:16.04
LABEL maintainer="jgsqware"
ENV DEBIAN_FRONTEND="noninteractive"
GOPATH="/go"
PATH="$GOPATH/bin:/usr/local/go/bin:$GOPATH/src/github.com/jgsqware/clairctl:$PATH"
GLIDE_VERSION="0.12.3"
GLIDE_DOWNLOAD_URL="https://github.com/Masterminds/glide/releases/download/v${GLIDE_VERSION}/glide-v${GLIDE_VERSION}-linux-amd64.tar.gz"
peharps also not mix apt... and apt-get ?

Done by #47


⚠ ClamAV has degraded performance

In 8915b33, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 198 ms

Resolved: ClamAV performance has improved in 3e1d6e1.


Method to check for valid guess returns the incorrect output

Hi George,
This does not appear to be fixed.
Regards,
Toby


Description size of recipes is limited on the server but not on the client side (currently get a 404 error when string is too large)

realised this also needed to be implemented for editing a recipe

I think I can close it now


Inconsistent 6.0.3 Update distributed trough KB 5012417

Description
Automatic update of .NET 6.0.2 to 6.0.3 produces inconsistent environment
Environment:
Edition	Windows 10 Pro
Version	21H1
Installed on	2/11/2022
OS build	19043.1586
Experience	Windows Feature Experience Pack 120.2212.4170.0
.NET 6.0.2 Hosting bundle installed

Steps :

In Windows Update , Advanced options , enable "Receive updates for other Microsoft products when you update windows"
Check for updates

Update KB 5012417 is downloaded and installed

Result:
Microsoft.ApsNetCore.App updated to 6.0.3
Microsoft.NetCore.App still stuck at 6.0.2

Issue:
Applications that targets 6.0.x will fail to execute because they will not be able to find the correct NET Runtime.
Workaround:
Install NET 6.0.3 Hosting bundle.
Comment:
The automatic update causes application crashes and a manual intervention is needed. This behavior is unacceptable when related to applications that are deployed on premise

@NikolaMilosavljevic can you please take a look?

@hankskorpio can you run Get-WindowsUpdateLog from powershell and attach the log. It will create a file called WindowsUpdate.log on your desktop.
@csnellgrove1-zz as an FYI. I manually installed 6.0.2 and then 6.0.3 and it seems to correctly upgrade. From the user's description it seems like it MU might be detecting and offering the wrong bundle.. Once we have the logs we should be able to confirm. I was testing in a sandbox so could not get the update to run

Sorry, meant to comment, not close.

@hankskorpio can you confirm whether you have IIS enabled and whether ANCM was installed from the hosting bundle. You can look for SOFTWARE\Classes\Installer\Dependencies\IIS_AspNetCore_Module_V2,x64
Also, can you run the VS log collection tool. It will gather additional data from the installations on the machine. The link to the tool is here: https://www.microsoft.com/en-ca/download/details.aspx?id=12493

@joeloff : IIS is not installed on that machine and the registry entry is not present.
BUT the same behavior happens on machines with IIS Installed. I can restore a machine with IIS to show you exactly the same steps and results, but... would it be supposed to work even without IIS using Kestrel?
In attachment the "collectInfo.txt" retrieved by VSLogCollectiontool
CollectInfo.zip

Hi. I'd opened a duplicate of this ticket last week which has now been closed but figure I can contribute.
I have been able to reproduce this problem on both a Windows Server 2012 R2 machine with IIS installed, and a Windows Server 2019 machine without IIS installed... combing the Windows Update logs doesn't seem to show any errors so appears the package is installing correctly.. so doesn't appear to be configuration or even platform specific.

Hi, I don't want to be pushy but ... any news about this issue? I'm a little worried about the deployment of our applications .

We are having this issue as well at our organization.  In our case one of our apps broke because the hosting bundle was not installed form the update package and that is a dependency for the app.  We opened a case with MS to see if they can help identify what is happening.

We are having this issue as well at our organization.  We noticed it specifically with the 6.0.3 update.  In our case one of our apps broke because the hosting bundle was not installed form the update package and that is a dependency for that app.  We opened a case with MS to see if they can help identify what is happening.

Hi, any news? Is it ok for microsoft that a production environment can crash suddenly due to an update?

Let's just hope this problem doesn't persist on this months released 6.0.4 update... fingers crossed.

We received this feedback from the .Net SE.  So fingers crossed the 6.04 version works correctly.
"We have identified some issues with the updates for .Net core 6.0.3 supplied through WSUS and MUC, this is going to be fixed with the 6.0.4 update."


[KIALI-242] Add link to Traces Jaeger in ServiceDetails

KIALI-242
Should I get the jaeger url by the backend or set it in the config file of the UI?
Actually the URI is the external one, but we can set jaeger-query, but I don't know if will keep this name for this service.

The link will be like <Jaeger_Host>/search?service=<service_name> (Example : http://jaeger-query-istio-system.<IP_ADDRESS>.nip.io/search?service=jaeger-query)
cc @theute @abonas
The link now is shoring all the traces of service, by default the query of jaeger show 20 traces of the last hour.

http://jaeger-query-istio-system.<IP_ADDRESS>.nip.io/search?end=1521731585049000&limit=20&lookback=1h&maxDuration&minDuration&service=jaeger-query&start=1521727985049000

What kind of search we want by default when then operator go to traces?
Need https://github.com/kiali/swscore/pull/129

For me the experience is fine.
To get the URL, can you see what @jotak did for Grafana ? It should probably be similar

In the backend the main handler to resolve the grafana service is here.
https://github.com/kiali/swscore/blob/master/handlers/grafana.go
I guess it could be similar for jaeger.
Note, it's not a trivial "read a constant from a file", it resolves the service asking openshift if available, or kubernetes, just falling into config if those are not present.
But I think most of the work is done and it can be re-used.

We can merge this now https://github.com/kiali/swscore/pull/129 was merged. Thanks @jotak
@lucasponce @xeviknal Can you review this? It's a link for Jaeger Traces

@aljesusg Although not technically part of this issue, would it be possible to also add the top level menu item for "Traces" to navigate to Jaeger UI (without service specified)? As currently only access to traces would be via the service details - so not as obvious if someone wants to look generally at all traces.
@theute Should it be included in this PR, or another one? If quick change would be good to get into this sprint to make jaeger UI integration more complete.

@aljesusg great!

@aljesusg Would it be possible to create a jira for adding the menu item and see if it can be squeezed into the sprint? :smile:
This is a great additional though!

@aljesusg Although not technically part of this issue, would it be possible to also add the top level menu item for "Traces" to navigate to Jaeger UI (without service specified)? As currently only access to traces would be via the service details - so not as obvious if someone wants to look generally at all traces.

Are you talking about menu item that pressing it opens a new browser tab?
Or embedding (iframe) the jaeger ui in that tab?

@theute Should it be included in this PR, or another one? If quick change would be good to get into this sprint to make jaeger UI integration more complete.

It should use an approach consistent with how the service details page navigates to the Jaeger ui.


fix(app): application data not populated on reload

closes #188

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


Investigate support for DNS over TLS

See: https://en.wikipedia.org/wiki/DNS_over_TLS

Support has been added!


isolate dependencies for tests and examples

If the dependencies for tests and examples are leaked into the
core sdk module, it will make the consumers hard or impossible to
use when there is a k8s dependency skew.

Going to merge this
@yuwenma Please take a look when you are back and let me know if you have any concerns.


Added endpoint to re_open a finding via the API

re-open a finding via the API.
Stole most of the logic from the finding/views.py open endpoint logic.
pretty straight forward, but it will allow us to update a finding and remove the "Mitigated" status via the API which currently isn't possible.

Oops didn't see the conflicts


tortoise: restart verifying by force

Motivation
when tortoise sees that some ballots started to vote consistently with local opinion it tries to bootstrap a verifying mode. in order to bootstrap a verifying mode it needs to find a cut of ballots that vote consistently with local opinion

block/ballot
local opinion
0xaa
0xbb
0xcc
0xdd
0xee
0xff

base
-
-
-
0xaa
0xaa
0xcc
0xcc

layer
-
10
10
11
11
12
12

0x11
1
-1
-1
1
-1
1
1

0x22
1
-1
-1
1
-1
1
1

0x33
-1
-1
-1
-1
-1
-1
-1

0x44
-1
-1
-1
-1
-1
-1
-1

In this example ballots starting from layer 10 are voting for some old layer (for example 5). Ballots from layer 10 disagree with local opinion and will be marked bad. Ballot 0xcc from layer 10 and ballots 0xee and 0xff will be marked "can be good" because exceptions from those ballots are consistent with local opinion. 0xee -> 0xcc and 0xff -> 0xcc is sufficient to bootstrap verifying tortoise.
closes: https://github.com/spacemeshos/go-spacemesh/issues/2985
closes: https://github.com/spacemeshos/go-spacemesh/issues/2678
Changes

try to bootstrap tortoise into verifying mode even if there are no good in the memory

Test Plan
uts
TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[x] Update documentation as needed

DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

i think this is also allows to get rid from "genesis" block thing, but i will try to do it in a separate pr.

Ballot 0xcc from layer 10 and ballots 0xee and 0xff will be marked "can be good" because exceptions from those ballots are consistent with local opinion. 0xee -> 0xcc and 0xff -> 0xcc is sufficient to bootstrap verifying tortoise.

in your example, why would oxee and oxff have exceptions from oxcc? they agree on those blocks.
do you think you can give "can be good" a definition?

Please check the definition for can be good in verifyong.go. or you are looking for smth else?

Please check the definition for can be good in verifyong.go. or you are looking for smth else?

do you mean by reading the code? i am looking for a comment that gives definition of

good
can be good
bad

@countvonzero

do you mean by reading the code? i am looking for a comment that gives definition of

yes i meant the comment above constants. i also tried to improve it in last commit

in your example, why would oxee and oxff have exceptions from oxcc? they agree on those blocks.

i included them in the table so that they can be easily compared with local opinion. i updated the example with more blocks, so it should make more sense now

bors merge


Upgrade to 0.17 alpha

Added in updates for 0.18 and going to merge so we don't fall too far behind


Create and implement the 'delete series' modal

Reassigning to @Coenego for review.

Coverage remained the same at 100.0% when pulling 35c2b01501a89a10af9a5bf1ec917d24b55874d9 on bp323:deleteSeries into 2c5e57c4164d108e246c3509393b1ae7f9212842 on CUL-DigitalServices:master.

Currently getting an error when trying to delete a series:
Uncaught TypeError: Cannot read property 'length' of undefined in gh.delete-series.js:169

Reassigning to @bp323

Currently getting the following error when deleting a series:
Cannot read property 'length' of undefined in gh.delete-series on line 169

Coverage remained the same at 100.0% when pulling 6bb1e89d1b643055481d9fc14274da40b7fb21cd on bp323:deleteSeries into 1a87f802fe421f8d1bb5f29b5a5f0d16707df74e on CUL-DigitalServices:master.

Added a follow-up commit that deletes the series from the hash.

Coverage remained the same at 100.0% when pulling 061c99c2127602a55faac777340f22922828d295 on bp323:deleteSeries into 685cc54de8e23011fa454d3f5d98cbce05ecc703 on CUL-DigitalServices:master.


Support for IAM in RN Messaging package

Added Javascript API's in Messaging package to handle In app Messages.
Implementation in iOS native side of RN Messaging package to handle In app Message.
Updated sample app

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@shtomar-adb can you add a private flag to messaging's package.json file? like -> https://github.com/adobe/aepsdk-react-native/blob/acc79a97ac09ff4082ad77efb178b85b8158182f/apps/AEPSampleApp/package.json#L4
Then the (Lerna) publish script will ignore this private package. https://github.com/lerna/lerna/issues/536#issuecomment-275960514

Hi guys. Is there any plan on merging / including this in RN library?


x-Axis ticks callback receives wrong value argument

Expected Behavior
We can specify a callback for the ticks of an axis in the form
ticks: {
    callback: function(value, index, values) {
        return value;
    }
}

The callback function should receive the default tick label as first argument and a numeric index as second (https://www.chartjs.org/docs/3.0.0-alpha/axes/labelling.html).
Current Behavior
For the x-Axis the callback function receives the index twice instead of value and index. For the y-Axis it works fine.
Steps to Reproduce
https://jsfiddle.net/fshu1xa8/
Environment
Chart.js version 3.0.0-beta.3 (works fine in 2.9.3, although the syntax needs to be adapted).

This is due to https://github.com/chartjs/Chart.js/blob/a8a83d12cda2901b84aaf987bdc589cca215feb7/src/scales/scale.category.js#L31-L49. I believe it's intentional to have common code between the axes so we should document that this is how the category scale works.

Ok, thank you for the explanation, @etimberg . Makes sense for categorical labels, even though I find it a bit confusing to have a different behaviour than for linear scale, for instance.
On a related note, it also took me some time to understand that the default axis type for the x-axis is "catetegory" even if the labels are numeric. It could be helpful to have another example under the header "Scale options" for "Numeric X Axis" (there is already "Non Numeric Y Axis"): https://www.chartjs.org/samples/3.0.0-alpha/.


Manga Galaxy changed its URL

Source information
Manga Galaxy 1.4.39
Source language
English
Source new URL
https://mangagalaxy.org/
Other details
Manga Galaxy changed its URL from https://mangagalaxy.me/ to https://mangagalaxy.org/

Acknowledgements

[X] I have updated all installed extensions.
[X] I have opened WebView and checked that the source URL has not changed yet.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I will fill out all of the requested information in this form.

now uses the same theme as vortex scan; (iken?)


cassandra: cleans up code and tests

This cleans up deprecation and style issues found in IntelliJ analysis. It also migrates docker tests to junit-jupiter and fixes the logging configuration which broke when we updated to SLF4J 2.x.
This also updates all use of docker test images to the latest, in attempts to share base image layers.

will rebase after https://github.com/openzipkin/zipkin/pull/3710

that all the docker tests pass with new images gives me confidence I can click the announce release button of 3.0.5. Thanks for all the help @anuraaga and @reta

going to merge this as master breaks occasionally due to memory limits on the elasticsearch image, which 3.0.5 fixed.


add ability to have custom prompts and save them

currently, you set some prompts for us, but most of the time we need refact to with custom instructions
similar to https://cursor.sh/features
ability to save those custom prompts and edit them would be great to fix/re-run them, as needed
with this small feature, you will make Cursor IDE less attracting
currently, I have both IDEs open  one for prompts and ai assistance and one for the IDE that I love,
please let me know how this sounds 🚀 or 👎. thanks

Hi! we are working on new chat and toolbox and we have some plans with this feature

1.4.1


Generate RPC Services from Go interfaces

Generate RPC services from Go interfaces. Also make transform to generate service definition instead of a list of RPCs.

There will be some more changes to generate client code as well, so don't merge yet.

We've been talking about this PR IRL. The main problem with this is that interfaces are the translations of oneof in protobuf. If in a future we want to support them somehow, we would have closed that door by accepting this.
We like the idea, though we would need to find a workaround for this. We are considering options for the comment proteus:generate but haven't settled in anything yet (ideas more than welcomed here).
Also, there is the problem that imagine you have the following interface:
type Person interface {
  Name() string
}

This would generate a personRemote struct satisfying this interface that would swallow any error in the called.
My initial proposal would be to apply the following two changes:

For an interface to be generated as a service, it needs to be called with //proteus:generate:service. This would imply no changes in hasGenerateComment since it checks with strings.HasPrefix.
For an interface to be generated as a service, all the methods need to return, at least, an error in final position. That would allow us to work with a remote version being able to handle the errors.

As before, an example needs to be added in example/models.go and checked in example_test.go
What do you think, @dennwc, @erizocosmico, and @mcuadros?

@Serabe why forcing that all interface methods return error? Currently we don't enforce that with functions or methods. So, why do it for interfaces?

@Serabe I agree with @erizocosmico that logic should match current behavior for global functions. If user wants an interface function with no error, he should be aware that RPC can fail and zero result will be returned. This can be documented, but is a valid use case.
Regarding type unions (interfaces that are implemented by multiple message types), I think we can easily distinguish between them and service interfaces. In any case RPC generation from interfaces requires explicit //proteus:generate annotation. And type unions (generated for protobuf), are useless without a message that contains them as a field type. And if we find a message/struct with such interface we can generate oneof automatically, the same way as dependent structs are generated.
And sure, I will add examples, but I need to commit few more changes first to integrate context support.

Review status: 0 of 13 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

Comments from Reviewable

The matching behaviour for current functions is with an error as last returned value in the client. We allow functions without errors as last returned value because we only generate the server, and therefore, we don't force functions to return an error.
func A(b string) int {
    return 0
}

func AWithError(b string) (int, error) {
    return A(b), nil
}

Since we are going from not having an error (original function) to having an error (in order to satisfy the signature in the server's interface) we are no loosing any information.
This PR adds a sort of client, the remote struct. In this case we have the following:
//proteus:generate
type RemoteType interface {
    Name() string
}

And we are generating something like:
func (c *remoteTypeRemote) Name() string {
    s, _ := c.Client.Name(ctx) // here we discard the error
    return s
}

So we are going the opposite direction, from having an error to not having it. That causes some information loss I would rather not have.
Since this is new behaviour, I would like to be conservative so far.
Thank you!

I totally understand what you are saying, and I agree that dropping an error in RPC client is a bad idea, but it's not possible to add an error to client's interface definition.
The point I was trying to make is that if client asks to generate an RPC client-server pair for his interface and this interface has a method with no error, RPC client should match this, or it will not be able to implement user's interface. It will render generated code useless in context of user's interface.
I propose printing a warning message in proteus log for these situations and/or generating a FIXME comment in client definition, so user will be aware that omitting an error might cause unexpected behavior.

Review status: 0 of 13 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

Comments from Reviewable

Rebased, integrated with context and added examples. @Serabe please take a look.

Review status: 0 of 18 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

protobuf/transform.go, line 157 at r2 (raw file):
Previously, Serabe (Sergio Arbeo) wrote…
There is no test checking what happens if we generate an empty interface. Can we add one to make sure nothing explodes?

Done. Added as an example.

Comments from Reviewable

@Serabe Any updates on this?

Still would like to only accept interfaces with the error, unless another solution is proposed. Don't like the idea of losing errors.

@Serabe I already proposed two solutions. What about them?

Okay, I think I should provide an example to show that this might be a desired behavior for some use cases.
Let's assume we are building a plugin system with microservices. Each plugin can do some useful work, and has an additional method to expose meta-information about itself:
message Info {
  enum State {
     UNAVAILABLE = 0;
     READY = 1;
  }
  State state = 1;
  string name = 2;
}

service Module {
    rpc Info(Empty) return (Info);
    rpc Do(DoReq) returns (DoResp);
}

This corresponds to a following Go interface:
type Module interface{
   Info() Info
   Do(DoReq) (DoResp, error)
}

As you can see, Info method has no error. But since default value of Info struct already has a valid meaning (status = unavailable), user can still verify that an error happened on the RPC and module cannot be reached.

We cannot check if an struct has anything that could be considered an unavailable state like in the Info above and still we are losing information (the error returned by gRPC).
To resume: For this PR to be accepted it needs to:

Only generate services from interfaces with //proteus:generate:service or something that is not a plain //proteus:generate.
Only generate methods that return an error in last place.

Thank you!


Get-AzureADApplicationProxyApplication

Hello,
When running this PS "Get-AzureADApplicationProxyApplication -ObjectId $item.objectid":
https://github.com/Azure/azure-docs-powershell-azuread/blob/live/azureadps-2.0/AzureAD/Get-AzureADApplicationProxyApplication.md
Error received:
Get-AzureADApplicationProxyApplication : Error converting value "aadHeaderBased" to type 'System.Nullable`1[Microsoft.Open.MSGraph.Model.OnPremisesPublishingSingleSignOnObject+SingleSignOnModeEnum]'. Path 'singleSignOnSettings.SingleSignOnMode', line 1, position 948
Tested with Preview and Normal AzureAD version.
Any ideas?

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

ID: 750d5a2e-c665-4cb5-ff0a-e9c68d21c05c
Version Independent ID: ac936328-df23-b3fa-82ab-668b300633cc
Content: PowerShell sample - Replace certificate in Azure Active Directory Application Proxy apps
Content Source: articles/active-directory/app-proxy/scripts/powershell-get-custom-domain-replace-cert.md
Service: active-directory
Sub-service: app-proxy
GitHub Login: @kenwith
Microsoft Alias: kenwith

@lightupdifire
Thanks for your feedback! We will investigate and update as appropriate.

@lightupdifire
Since this issue isn't directly related to improving our docs, and to gain a better understanding of your issue, I'd recommend working closer with our support team via an Azure support request. Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.
Thank you for your time and patience throughout this issue.


Use mail.sendMail instead of email_nag.sendMail

Coverage increased (+2.7%) to 52.616% when pulling 963996e6e9f858e2a8a7d1876312d96b54e0af00 on calixteman:master into 39d61d968b50c301b2f6c0e195e312f5a5638ce1 on mozilla:master.


"Profile" configuration not accessible in "Flutter Build" task

Hello guys, would it be possible to change a bit build task and add optional configuration dropdown?
Let me explain the problem: currently there is no way to run Flutter Build task with "Profile" configuration. There is only a "Debug" checkbox - if it is checked then Debug configuration is used, otherwise it's Release config. In Flutter projects there is usually "Profile" configuration as well. I'm in a situation where I must use "Profile" one but I have no way to make my Build task doing that.
Proposition:
Replace "Debug" checkbox by "Configuration" dropdown (with three values: Release (IMO it might be default one), Profile, Debug)
Or input field where user can type a name of configuration, but it doesn't seem to be better idea.

I thnk "profile" can be added but the issue is I don't want to break other people's builds by changing it to to a dropdown.
I have given "ExtraArgs" input field which exactly for these kind of extensions. If you need a "Profile" flag, you can try to pass "profile" as "extraArgs" (do not select debug) and push Profile flag here, it should work.

@hey24sheep that's true - changing this means changing the parameters, therefore it would require version 1.* so that pipelines having version 0.* still works.
Anyway, unchecking Debug and adding --profile as an extra argument does the job :) 👍
Thanks!

Yes, versions will be maintained. But, it depends actually, like in our company it is set to latest. So anytime I make a new feature or edit in this extension and upload to Microsoft marketplace, our pipelines automatically gets updated.
That extraArgs was added with the same thought in regards to future upgrade without breaking anything.
I'm glad it's working for you now. I will write it as a feature in future update. For now, I will close this issue as solved with a workaround.


Automate updates to ECS Optimized AMIs

Currently this is a manual process, and normally kind members of the community will submit a pull request updating the AMI identifiers in the infrastructure/ecs-cluster.yaml file.
We should either:

Use AWS CodeBuild to check for the latest AMIs for each region, and automatically open a pull request for the changes. I've done similar in another project (awslabs/goformation) before and it's worked well.

Replace the hardcoded AMIs in the CloudFormation templates with a custom resource that looks up the latest AMI for the region.

I think option 1 would be preferable, as i'm not sure CloudFormation update-stack evaluates the result of custom resources, so would not update stacks properly when the AMIs change.

FWIW I got tired of updating the AMI list by hand, and am now using this little Python script to generate the mapping:
#! ./venv/bin/python3
#
# python -m venv .venv
# .venv/bin/pip install lxml requests cssselect
# .venv/bin/python ecs-dump

from lxml import html
import requests

url = 'https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html'

page = requests.get(url)
tree = html.fromstring(page.content)

regions = [e.text_content() for e in tree.cssselect('tr td:nth-child(1) code')]
amis = [e.text_content() for e in tree.cssselect('tr td:nth-child(3)')]

version = tree.cssselect('table tr:nth-child(2) td:nth-child(2)')[0].text_content()
print('  # Current AMI version: %s' % version)
print('  AWSRegionToAMI:')
for (region, ami) in sorted(zip(regions, amis)):
    print('    %s:' % region)
    print('      AMI: %s' % ami)

@PaulMaddox : what about using Lambda to check the actual AMI ?

This just got much easier:
Amazon ECS provides ECS-Optimized AMI metadata via SSM Parameters
Amazon Elastic Container Service (Amazon ECS) now allows you to dynamically get the latest ECS-optimized Amazon Machine Image (AMI) ID when creating a cluster made up of EC2 instances
https://aws.amazon.com/about-aws/whats-new/2018/04/amazon-ecs-provides-ecs-optimized-ami-metadata-via-ssm-parameter/

CloudFormation supports pulling parameters directly from SSM Parameter Store.

@PaulMaddox Neat! I am wondering if using that should be considered a best practice. My experience has been that the a-c releases of an image series tend to be quite unstable, so upgrading automatically can be dangerous.

Is there any API to get latest AMI per region? ECS AMI ID is a parameter from my customized CFN so if there is an API to get the latest AMI for ECS, it'd be great.

Howdy,
PR #76 should address this issue.
Thanks,
Jason Swindle

PR #92 is an update version of PR #76 that will merge without conflicts


Service crashes after receiving malformed HELLO packet

Any summary here would be redundant, since the title captures the problem.
Attached please find the following log files:

auth.log
messages.txt
sysrepo.txt

Also attached is a text file that can be executed as a python script to reproduce the failure.
I also have pcap, but I do not know how to encode it to a file type that can be decoded
auth.log
messages.txt
sysrepo.txt
netconfAttack.txt

Hi,
a "print injection", nice. Should be fixed now.
Regards,
Michal


计算机领域有哪些顶级会议？

元数据源 http://www.wikicfp.com/cfp/allcat

计算机体系结构领域:  ISCA（The International Symposium on Computer Architecture)
Jun 25, 2017 - Jun 28, 2017  Toronto, Canada

操作系统 http://www.wikicfp.com/cfp/call?conference=operating systems

虚拟化 http://www.wikicfp.com/cfp/call?conference=virtualization

虚拟化方向

[ ] ICVAT @ International Conference on Virtualization Application and Technology

[ ] VHPC @ Workshop on Virtualization in High-Performance Cloud Computing

[ ] XDOM0 @ Workshop on Security and Dependability of Multi-Domain Infrastructures

[ ] USENIX ATC @ International Conference on Virtualization Application and Technology

[ ] CLOUD COMPUTING @ International Conference on Cloud Computing, GRIDs, and Virtualization

[ ] IC2E @ IEEE International Conference on Cloud Engineering

[ ] PROGNETS @ EAI International Conference on Programmable and Virtualized Networks

[ ] FiCloud @ The IEEE International Conference on Future Internet of Things and Cloud

[ ] SYSTOR @ ACM International Systems and Storage Conference

[ ] Sec-VirtNet @ IEEE Workshop on Security in Virtualized Networks

[ ] VT @ International Workshop on Virtualization Technologies in conjunction with Middleware

[ ] CloudCom @ IEEE International Conference on Cloud Computing Technology and Science

[ ] WIVOSCA @ Workshop on the Interaction amongst Virtualization, Operating Systems and Computer Architecture

[ ] VTDC @ Virtualization Technologies in Distributed Computing

[ ] HCCIEA @ International Workshop on Hybrid Cloud computing Infrastructure for E-Science application

操作系统方向

[ ] ASPLOS @ International Conference on Architectural Support for Programming Languages and Operating Systems

[ ] EWILI @ Embedded Operating System Workshop

[ ] ECBS @ European Conference on the Engineering of Computer Based Systems

[ ] OSPERT @ Annual Workshop on Operating Systems Platforms for Embedded Real-Time Applications

[ ] ROSS @ International Workshop on Runtime and Operating Systems for Supercomputers

[ ] SYSTOR @ ACM International Systems and Storage Conference

[ ] SEIoT @ Workshop on Security in equipment to the IoT

[ ] HotOS @ Workshop on Hot Topics in Operating Systems

[ ] VEE @ ACM SIGPLAN/SIGOPS International Conference on Virtual Execution Environments

[ ] ARCS @ INTERNATIONAL CONFERENCE ON ARCHITECTURE OF COMPUTING SYSTEMS

[ ] ICAITA @ International Conference on Advanced Information Technologies and Applications

[ ] INFLOW @ Workshop on Interactions of NVM/Flash with Operating Systems and Workloads

[ ] EWiLi @ Embedded Operating System Workshop

[ ] SBESC @ VI Brazilian Symposium on Computing Systems Engineering

[ ] OSDI @ USENIX Symposium on Operating Systems Design and Implementation

[ ] RST @ Special Issue on Reliable Software Technologies for Dependable Distributed Systems (Journal of System Architecture)

[ ] NOSSDAV @ ACM SIGMM Workshop on Network and Operating Systems Support for Digital Audio and Video

[ ] USENIX ATC @ USENIX Annual Technical Conference

软件架构 Software Architecture

[ ] IJSPTM @ International Journal of Security, Privacy and Trust Management

[ ] Microservices @ Microservices - Special Issue at IEEE Software

[ ] ISEC @ Innovations in Software Engineering Conference

[ ] ISSA @ International workshop on Interplay of Security, Safety and System/Software Architecture

[ ] SOFSEM @ International Conference on Current Trends in Theory and Practice of Computer Science

[ ] SEFM @ International Conference on Software Engineering and Formal Methods

[ ] ICSOFT @ International Conference on Software Technologies

[ ] SOEN @ International Conference on Software Engineering

[ ] ITPF @ International conference on Information Technology, Present and Future

[ ] ACVI @ Architecture Centric Virtual Integration

软件工程 / 系统软件 / 程序设计语言
学术期刊

TOPLAS @ ACM Transactions on Programming Languages & Systems

TOSEM @ ACM Transactions on Software Engineering Methodology

TSE @ IEEE Transactions on Software Engineering

计算机体系结构 / 并行与分布计算 / 存储系统
学术期刊

TOCS ／ TOC／ TPDS ／ TCAD ／ TOS

学术会议

ASPLOS ／ FAST／HPCA ／ ISCA ／ MICRO ／SC ／USENIX ATC／PPoPP

The 26th ACM Symposium on Operating Systems Principles
October 28-31, 2017, Shanghai, China

学术会议

IPDPS 异构计算
NSDI  网络顶会
ASPLOS  计算机系统结构领域
ICPADS 分布式并行
ICDCS 分布式计算
OSDI ,USENIX 操作系统领域重要会议，侧重操作系统各方面的新型技术。
SOSP, 和 OSDI 交替举行，每两年一届，操作系统旗舰会议操作系统
SPAA, 算法和体系架构
SC 全球超级计算大会

厂商会议

Linaro
Microsoft
IBM
Gartner
VMWare
Cloud Computing

项目会议

XXX Con

Apache

XXX Summit

Arch
CNCF

XXX Forum

KVM

中国内核开发者大会（CLK 大会）
Cloud Open
MIT ILP 麻省理工学院全球产业联络计划
China CCF

安全峰会

FIRST
Troopers
XXX安全峰会
Black Hat
XPwn
OWASP
MOSEC
GeekPwn
KCon
HITB

网络和通信学术界 Top1 的会议 SIGCOMM
信号处理、通信和计算三大领域 ICSPCC
测试峰会  STAREAST
讨论代码生成及优化技术

CGO
PPOPP
LLVM

FSE 大会是软件工程领域三大顶级会议（ICSE、FSE、ASE）之一
芯片设计工具以及嵌入式系统领域

Design Automation Conference（DAC）
NOCS

Workshop

HOTCLOUD
ONS
OSCON


convert avatar_source and avatar_license to TextField with markdown.

this is now functional, except the min and max length settings are not working yet.

Any chance to bring it up to 7 successful tests like before?

Hm. Some PRs have 7 successful tests, others 6 successful. Hm.


Nuget Push to GitHub Packages fails with 401 Unauthorized

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name:

NuGetCommandV2
DotNetCoreCLIV2

Environment

Server - Azure Pipelines
Agent - Hosted

Issue Description
When using a Nuget Service Connection, the Azure Pipeline tasks add the "--api-key" switch to the nuget command line, with a hardcoded value of "RequiredApiKey". In the past, this worked when pushing packages to GitHub Packages - however, it looks like a recent change made in GitHub to support the ApiKey switch causes these tasks to fail with a 401 Unauthorized error.
Task logs
/usr/bin/dotnet nuget push /home/vsts/work/1/a/packages/release/<package-name>.nupkg --source https://nuget.pkg.github.com/<owner> --api-key RequiredApiKey
Pushing <package-name>.nupkg to 'https://nuget.pkg.github.com/<owner>'...
  PUT https://nuget.pkg.github.com/<owner>/
warn : Your request could not be authenticated by the GitHub Packages service. Please ensure your access token is valid and has the appropriate scopes configured.
warn : Your request could not be authenticated by the GitHub Packages service. Please ensure your access token is valid and has the appropriate scopes configured.
warn : Your request could not be authenticated by the GitHub Packages service. Please ensure your access token is valid and has the appropriate scopes configured.
warn : Your request could not be authenticated by the GitHub Packages service. Please ensure your access token is valid and has the appropriate scopes configured.
warn : Your request could not be authenticated by the GitHub Packages service. Please ensure your access token is valid and has the appropriate scopes configured.
  Unauthorized https://nuget.pkg.github.com/<owner>/ 810ms
error: Response status code does not indicate success: 401 (Unauthorized).

Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Error logs
[Insert error from the logs here for a quick overview]

I met the similar issue.
These days, I am testing to push nuget package to github using Azure pipeline nuget task.
I have the service connection using basic authentication with my PAT.
1) If I use the NuGet task as:

I got the following error:
The nuget command failed with exit code(1) and error(Response status code does not indicate success: 401 (Unauthorized). System.Net.Http.HttpRequestException: Response status code does not indicate success: 401 (Unauthorized). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at NuGet.Protocol.Core.Types.PackageUpdateResource.EnsureSuccessStatusCode(HttpResponseMessage response, Nullable1 codeNotToThrow, ILogger logger) at NuGet.Protocol.Core.Types.PackageUpdateResource.<>c__DisplayClass24_0.<PushPackageToServer>b__0(HttpResponseMessage response) at NuGet.Protocol.HttpSource.<ProcessResponseAsync>d__191.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.d__24.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.d__20.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at NuGet.Protocol.Core.Types.PackageUpdateResource.d__19.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.d__18.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.d__14.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Commands.PushRunner.d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.CommandLine.PushCommand.d__36.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.CommandLine.Command.Execute() at NuGet.CommandLine.Program.MainCore(String workingDirectory, String[] args))
2) I use the custom nuget as:

I got the error

Any news about this? I have the same problem using basic and apikey authentication.

@Daniel127 I had to resort to using the dotnet CLI via an explicit script task instead:
          - script: dotnet nuget push --source https://nuget.pkg.github.com/<org-name>/index.json --api-key $(ApiKey) '$(Build.ArtifactStagingDirectory)/packages/release/*.nupkg'
            displayName: Publish Nuget Packages

I can't find this issue on the developer community.  Did they close it without migrating it?


On-demand replication Integrated Test

Added ReplicateBlob Integration Test

Codecov Report
Base: 53.79% // Head: 14.97% // Decreases project coverage by -38.81% :warning:

Coverage data is based on head (6164482) compared to base (e74bc5e).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@              Coverage Diff              @@
##             master    #2277       +/-   ##
=============================================
- Coverage     53.79%   14.97%   -38.82%
+ Complexity     7036     2377     -4659
=============================================
  Files           753      753
  Lines         57654    57704       +50
  Branches       7086     7102       +16
=============================================
- Hits          31014     8642    -22372
- Misses        23957    48548    +24591
+ Partials       2683      514     -2169

Impacted Files
Coverage Δ

...com/github/ambry/messageformat/BlobProperties.java
0.00% <0.00%> (-81.16%)
:arrow_down:

.../src/main/java/com/github/ambry/store/Message.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...rc/main/java/com/github/ambry/named/PutResult.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...rc/main/java/com/github/ambry/quota/QuotaMode.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...rc/main/java/com/github/ambry/quota/QuotaName.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...rc/main/java/com/github/ambry/rest/RestMethod.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...c/main/java/com/github/ambry/config/KMSConfig.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...c/main/java/com/github/ambry/config/SSLConfig.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../main/java/com/github/ambry/named/NamedBlobDb.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../main/java/com/github/ambry/quota/QuotaAction.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 476 more

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

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


only Xorg available when running under qemu-kvm

Describe the bug
I noticed that when I run a silverblue 39 image in qemu-kvm (on my ublue 39 host) I lose ability to run Wayland after rebasing to bluefin.
What did you expect to happen?
I expected to use Wayland.
Output of rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:39 (index: 0)
                   Digest: sha256:12237f09943c091bb5a4965e7284aad9f8ae1f016e95254483c7ab545d0f227c
                  Version: 39.20240129.0 (2024-01-29T23:17:22Z)
                   Commit: 6fe8df244314c307e9859b7e9bc36b7a03d23deba555eb4630f8360b6105b5f1
                StateRoot: fedora

ostree-unverified-registry:ghcr.io/bsherman/silverblue-custom:pr-6-39 (index: 1)
                   Digest: sha256:89ee4bf7d22f77bf22e4a0f89b57aea72e7b2bf30dc7d6ceaa7a37953c221fc7
                  Version: 39.20240131.0 (2024-02-01T07:49:45Z)
                   Commit: a05c4b73bfd5f6d08dad86f15ca41d4b15812a27f9685ad19c6f3b77efb942f1
                   Staged: no
                StateRoot: fedora

Extra information or context
No response

I'm happy to dig into this further, but not time right now. If someone else sees the solution, by all means please jump in here. :-)

Inside of /usr/lib/udev/rules.d/61-gdm.rules
There appears to be checks for virtual GPU. It will write variables to /run/udev/gdm-machine-has-virtual-gpu. Unless nomodeset is still set from kernel cmdline, it should good. If there are multiple virtual gpus it disables wayland.

I'm afk now, but is this file in Silverblue upstream or in Bluefin?
My report is that the same VM uses Wayland with upstream, but stops using Wayland after rebase to Bluefin

We should be getting this file from upstream. While we make changes for gnome-vrr, I don't believe this affects this file.

Playing with F40 iso's with qemu.
By default something in /usr/lib/udev/rules.d/61-gdm.rules is triggering the no-wayland support. Per the arch wiki, you can override this file with a symlink to /dev/null. Qemu is now working with wayland for gdm which then enables wayland sessions for login.
Aurora out of the box supports wayland.

Found the issue:
On lines 82 to 87 of /usr/lib/udev/rules.d/61-gdm.rules there is a check to disable wayland for the following situation:
If you have both a virtual gpu and a hardware gpu then wayland is disabled.
We obviously have a virtual gpu. But where does the hardware gpu come from? Well, displaylink apparently creates 4 additional /dev/dri/cards. The check for a hardware gpu is if there is an additional card that is not associated with the cirrus, virtio, qxl, or vga virtual hardware devices. So displaylink triggers that we have a physical gpu and the udev rule then disables wayland.
I'll see if disabling displaylink service fixes this. Otherwise, we can comment out a single line in /usr/lib/udev/rules.d/61-gdm.rules

Well, displaylink apparently creates 4 additional /dev/dri/cards.

That is pretty wild!
I wonder if, other than disabling a service, there is a way to stop displaylink from loading.  Shouldn't the drive only load if required?

@m2Giles filed this for more info https://github.com/negativo17/displaylink/issues/2
as we see the problem is here: https://github.com/negativo17/displaylink/commit/1feee61a49104183a836271fe2ccdd4185b9fd26

Interesting take, I can revert that commit, no problem, but I did not find the automatic startings/stopping based on USB IDs very reliable, EVDI takes some time to settle up and with dynamic loading we had a few end users connecting and disconnecting stuff before the display had time to initialize.
What is the use case for running Displaylink inside a VM though?

New packages with the change reverted will be live in a few minutes.

What is the use case for running Displaylink inside a VM though?

We install displaylink by default on all of our images. When it was first added to the image it was still in the hot plug mode where evdi didn't load until the plug in event.
We didn't put it together on why on VMs it was failing until the GitHub issue.
Also, this is something we'll likely bring up to gdm since the udev rules seem extremely out of place now.

Also, this is something we'll likely bring up to gdm since the udev rules seem extremely out of place now.

@m2Giles did you get in touch with the GDM folks?

I have not.


fix(base): define errorHandler with private not use #

With this PR, defining errorHandler with private not using #  in hono-base.ts:
private errorHandler: ErrorHandler = errorHandler

This will fix #3671
Since the property defined with # will be a completely private member that can't be accessed from outside in the JavaScript runtime phase, problem #3671 occurs. But, if you define it with private keyword without # it can be accessed from outside in the JavaScript runtime phase.
The author should do the following, if applicable

[ ] Add tests
[ ] Run tests
[ ] bun run format:fix && bun run lint:fix to format the code
[ ] Add TSDoc/JSDoc to document the code

@usualoma
Can you review this?

Hi @yusukebe, thank you 👍
Okay, so #3671 indicates that the problem is with apps that use a mixture of esm and cjs.
I'm not sure if this (mixing ems and cjs is OK) is within the scope of what Hono supports, but I think this change will fix it.

@usualoma

I'm not sure if this (mixing ems and cjs is OK) is within the scope of what Hono supports

I'm also thinking about this thing! But currently, we have to accept this PR.