windows restic init(possibly more?) broken by executing from smb3 share.

Output of restic version
restic 0.11.0 compiled with go1.15.3 on windows/amd64
How did you run restic exactly?
OS: Windows 10
1: (powershell, does not work)
$env:RESTIC_REPOSITORY="rest:http://<IP_ADDRESS>:8000/"
$env:RESTIC_PASSWORD="testing"
.\restic_0.11.0_windows_amd64.exe init

2: (powershell, does not work)
.\restic_0.11.0_windows_amd64.exe init --repo "rest:http://<IP_ADDRESS>:8000/"
3: (cmd, does not work)
.\restic_0.11.0_windows_amd64.exe init -r "rest:http://<IP_ADDRESS>:8000/"
4: (cmd, does not work)
.\restic_0.11.0_windows_amd64.exe init --repo "rest:http://<IP_ADDRESS>:8000/"

What backend/server/service did you use to store the repository?
rest-server docker image hosted on a fresh default install of ubuntu linux 18.04* with authentication and tls disabled for testing in order to minimize possible trouble sources.
*no special settings, firewall is off with recommended basic docker install instructions
docker run -d -p 8000:8000 -v /data:/data -e OPTIONS="--no-auth" --name rest_server restic/rest-server
(data volume at /data, I know that it is accessible to the image at least because I was able to create http auth users after running this test)
docker logs:
Data directory: /data
Authentication disabled
Private repositories disabled
Starting server on :8000

Expected behavior
proper parsing/usage of repo flag on windows as well as reading environment variables in order to init the repo remotely.

Actual behavior
quick failure to stdout:
restic_0.11.0_windows_amd64.exe : Fatal: create repository at rest:http://<IP_ADDRESS>:8000/ failed: Post "http://<IP_ADDRESS>:8000/?create=true": dial tcp <IP_ADDRESS>:8000: socket: An invalid argument was
supplied.
At line:1 char:1
+ . .\restic_0.11.0_windows_amd64.exe init
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Fatal: create r...t was supplied.:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

Steps to reproduce the behavior
1:
set the restic repository and password environment variables
run restic init
2:
run restic init with the "--repo" flag followed by the repository url

Do you have any idea what may have caused this?
improper parameter parsing perhaps? maybe a bug in a library?
Do you have an idea how to solve the issue?
Unfortunately I do not, I have little experience in the Go language and the error is ambiguous.
Did restic help you today? Did it make you happy in any way?
Unfortunately I cannot use restic on windows at the moment, but I am excited to see the VSS feature added in! (In my opinion that's a very valuable piece of code for backups on windows)

Hey, thanks for the report! I don't have any idea what's going on, but it feels to me that argument parsing is not the core issue.
My ideas for the next steps would be:

Does it work with a different backend than rest? Can you try creating a local repository in a directory or use a different backend than rest?
Can you please confirm that restic is not restricted by the Windows firewall? I've found the error message you're seeing (An invalid argument was supplied) in that context

Hey, thanks for the report! I don't have any idea what's going on, but it feels to me that argument parsing is not the core issue.
My ideas for the next steps would be:

Does it work with a different backend than rest? Can you try creating a local repository in a directory or use a different backend than rest?
Can you please confirm that restic is not restricted by the Windows firewall? I've found the error message you're seeing (An invalid argument was supplied) in that context

Docker by default assigns IP from the <IP_ADDRESS>/12 IP address range to its containers. So <IP_ADDRESS> looks like a container-internal IP which is not accessible from outside the docker host server. Please check whether this is really the external IP of the server.
--repo "rest:http://<IP_ADDRESS>/" cannot work as it's missing a port and the default for HTTP is 80.

Docker by default assigns IP from the <IP_ADDRESS>/12 IP address range to its containers. So <IP_ADDRESS> looks like a container-internal IP which is not accessible from outside the docker host server. Please check whether this is really the external IP of the server.
--repo "rest:http://<IP_ADDRESS>/" cannot work as it's missing a port and the default for HTTP is 80.

Hey Michael, nice thought with the docker IP range, I examined it and the current range for docker0 on this fresh install for me was <IP_ADDRESS>/16 (ending at <IP_ADDRESS>) and I double checked to ensure there were no weird entries in the ip route table in its default state.
My test network for virtual machines does indeed use the <IP_ADDRESS>/24 range externally.  This does not seem to be a network problem w.r.t. my setup as far as I can tell.
I double checked your comment about the port, that was a typo, my bad.  The copy of the output to stdout properly reflects the URL I entered.  I have updated the first two commands appropriately above.

fd0,
I can confirm that creation of a local repository works on windows.
My firewall does appear to be off on this network's profile.  I have also tried by adding an application exception to allow it through the windows firewall anywhere, init still fails with the same error however.  I will spin up a temporary windows machine tonight to verify with a fully disabled firewall.
I also installed and executed the linux client on my laptop and was able to init the repo with:
./restic_0.11.0_linux_amd64 init --repo rest:http://<IP_ADDRESS>:8000
enter password for new repository:
enter password again:
created restic repository 3242876ca8 at rest:http://<IP_ADDRESS>:8000/

verified creation on the rest-server vm:
administrator@test-backup:~$ ls /data
config  data  index  keys  locks  snapshots

I'm wondering if this is somehow related to golang's net dial code? I've seen a couple of issues when searching the golang repo, but I'll wrap up my windows vm test later tonight before I'd recommend jumping down that rabbit hole.

Hey Michael, nice thought with the docker IP range, I examined it and the current range for docker0 on this fresh install for me was <IP_ADDRESS>/16 (ending at <IP_ADDRESS>) and I double checked to ensure there were no weird entries in the ip route table in its default state.
My test network for virtual machines does indeed use the <IP_ADDRESS>/24 range externally.  This does not seem to be a network problem w.r.t. my setup as far as I can tell.
I double checked your comment about the port, that was a typo, my bad.  The copy of the output to stdout properly reflects the URL I entered.  I have updated the first two commands appropriately above.

fd0,
I can confirm that creation of a local repository works on windows.
My firewall does appear to be off on this network's profile.  I have also tried by adding an application exception to allow it through the windows firewall anywhere, init still fails with the same error however.  I will spin up a temporary windows machine tonight to verify with a fully disabled firewall.
I also installed and executed the linux client on my laptop and was able to init the repo with:
./restic_0.11.0_linux_amd64 init --repo rest:http://<IP_ADDRESS>:8000
enter password for new repository:
enter password again:
created restic repository 3242876ca8 at rest:http://<IP_ADDRESS>:8000/

verified creation on the rest-server vm:
administrator@test-backup:~$ ls /data
config  data  index  keys  locks  snapshots

I'm wondering if this is somehow related to golang's net dial code? I've seen a couple of issues when searching the golang repo, but I'll wrap up my windows vm test later tonight before I'd recommend jumping down that rabbit hole.

I may have figured this out, I do not believe windows firewall is the problem (or if it is, then when it is off, that would imply it isn't truly "off")

The issue seems to occur no matter whether the firewall is on or off, rather I was calling the executable while it was present on a network share... and it was functioning in all cases except for when it tried to connect remotely it would seem.
Once the exe was on my desktop, it executed perfectly and could connect to the rest backend.
Unless you think this is an appropriate problem to handle in restic I think then that this problem is solved, feel free to close the issue if you think that is the case.

I may have figured this out, I do not believe windows firewall is the problem (or if it is, then when it is off, that would imply it isn't truly "off")

The issue seems to occur no matter whether the firewall is on or off, rather I was calling the executable while it was present on a network share... and it was functioning in all cases except for when it tried to connect remotely it would seem.
Once the exe was on my desktop, it executed perfectly and could connect to the rest backend.
Unless you think this is an appropriate problem to handle in restic I think then that this problem is solved, feel free to close the issue if you think that is the case.

@Nemerensis The only error I could find which matches your problems is from 2018: https://stackoverflow.com/questions/50155482/after-windows-10-update-1803-my-program-cant-open-a-socket-when-running-from-ne . And that was a bug in Windows itself. Out of curiosity, is the network mount from which you ran restic a SMB1 mount as in the linked stackoverflow question?
I don't think there's anything to do on the restic side as this rather looks like a problem of the underlying OS.

@Nemerensis The only error I could find which matches your problems is from 2018: https://stackoverflow.com/questions/50155482/after-windows-10-update-1803-my-program-cant-open-a-socket-when-running-from-ne . And that was a bug in Windows itself. Out of curiosity, is the network mount from which you ran restic a SMB1 mount as in the linked stackoverflow question?
I don't think there's anything to do on the restic side as this rather looks like a problem of the underlying OS.

The share that the restic executable resided on was a default windows 10 client to server 2016 file server share running SMB 3.1.1 according to the output of:
Get-SmbConnection

The share that the restic executable resided on was a default windows 10 client to server 2016 file server share running SMB 3.1.1 according to the output of:
Get-SmbConnection

Thanks for the feedback!

Thanks for the feedback!


Upgrade to latest embedded-graphics

I updated some non-critical development dependencies while I was at it.

Sorry for being slow to get back to this, I will try to pass the build as soon as possible.  Getting this merged is not super urgent for me, I'm happy to keep using my own branch for a while :)

Thanks for fixing the build! This is now released as 0.3.0-alpha.1.


[feature] support of $ref in contact fields

given we handle a lot of Open API specification
given the fact that contact are mostly always the same
it would be great that $ref being supported for the field contact
this feature is not a breaking change could be added either to moonwalk project or beeing a feature candidate for 3.2.X
following this pattern
contact:
$ref: ../_shared/contact.yaml
this would requires a change in the meta schema

if the contact fields will be updated as this ticket , https://github.com/OAI/OpenAPI-Specification/issues/1589
This feature could be included as part of the 2024 initiative  https://github.com/OAI/OpenAPI-Specification/issues/3516

Consolidating under #3853 and closing


"github.com/go-openapi/spec" has unlicense file

license-bill-of-materials github.com/go-openapi/spec outputs unlicense:
$ license-bill-of-materials github.com/go-openapi/spec
...
{
  "project": "github.com/go-openapi/spec",
  "licenses": [
    {
      "type": "Apache License 2.0",
      "confidence": 1
    },
    {
      "type": "The Unlicense",
      "confidence": 0.3422459893048128
    }
  ]
}
...

From my understanding, the license-bill-of-materials tool iterates through all files of a given project and determine the license information from any files that has similar name as license.*.
Because "github.com/go-openapi/spec" has a file license.go,
license-bill-of-materials evaluates the license.go and determine the project is also unlicense.
The following steps reproduce the above issue.
$ tree $GOPATH/src/unlicense/
├── LICENSE
├── license.go
└── main.go

$ cat unlicense/LICENSE
                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.
   ....

$ cat unlicense/license.go
// Copyright 2018 CoreOs Authors
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
//    http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.

package main

$ license-bill-of-materials unlicense
[
    {
        "project": "unlicense",
        "licenses": [
            {
                "type": "Apache License 2.0",
                "confidence": 1
            },
            {
                "type": "The Unlicense",
                "confidence": 0.3488372093023256
            }
        ]
    }
]

cc/ @philips


Cannot create issues.

Extension version: 0.23.1
VSCode Version: 1.53.2
OS: Ubuntu 20.10

Steps to Reproduce:

Open a repository
Try to create an issue.
Save the issue, it should create the issue, but instead the window with the issue text stays open, the modified dot goes away and no issue is created.

I should note, there is nothing in the logs, and nothing in the dev console.  I am not sure where else to look to see what the issue could be.  This has been a problem for at least the last 2 versions of the extension, and I have tried to work through it to no avail.

I can also see issues that are created, I can create PRs no problem, and I can do all the other actions within the extension except create issues.

I just noticed this pop up in the console as I was trying to troubleshoot it further, but it has scope so I don't know if it's applicable:
[Violation] Forced reflow while executing JavaScript took 31ms

I just tried this in vscode, same version of the extension and main app, running in WSL on a Windows 10 machine.  WSL is Ubuntu 20.04.  It seems to work there, but not on my main linux machine.  Very odd.
On a lark, I opened a remote session from the windows 10 machine to the Linux host via SSH, opened the same repository as I was trying to do this with on the linux machine, and created an issue with no problem.  This looks like it might be related to vscode on Linux itself.

Do you have auto save turned off? We only do ctrl+s to create the issue when you have autosave on (when the settings is NOT "files.autoSave": "off").

Sorry I didn't see your reply until today.  Autosave is set to "onFocusChange" at the moment.
There have been updates to vscode and the extension since I opened this, and indeed, it's still not working.
Current versions:
Github Pull Requests and Issues: 0.25.0
VScode: 1.55.0
Linux: Ubuntu 20.10
An added oddity that I just noticed is the autocomplete stuff for the Assignees and Lables fields also doesn't work.  I wonder if it's related....

 Can you run the command "Developer: Toggle Keyboard Shortcuts Troubleshooting"? It will open a log. Try to repro your issue then share the log here and we'll see what's up.

Here is a snippet of the log from a Ctrl-S in a new issue window (I closed and reopened a new one.)
[2021-04-07 09:46:04.513] [renderer5] [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl], code: KeyS, keyCode: 49 ('S')
[2021-04-07 09:46:04.514] [renderer5] [info] [KeybindingService]: | Resolving ctrl+[KeyS]
[2021-04-07 09:46:04.515] [renderer5] [info] [KeybindingService]: \ From 2 keybinding entries, matched issue.createIssueFromFile, when: resourceScheme == 'newIssue' && config.files.autoSave != 'off', source: user extension GitHub.vscode-pull-request-github.
[2021-04-07 09:46:04.839] [renderer5] [info] [KeybindingService]: + Storing single modifier for possible chord ctrl.```

The issue is also not created if I click the checkmark icon at the top of the editor window, so it may be more than just a key mapping issue.

Yep, seems like it isn't the keybinding. Are there any other errors in the developer console?
Can you share the contents of the new issue file you are trying to use to create an issue?

There are no other errors in the dev console, sadly.
Here are the contents of the editor window:
instance_type not being respected

Assignees: jhujasonw
Labels:
The name of the variable changed as well as it's type, it's now a list called instance_types

<!-- Edit the body of your new issue then click the ✓ "Create Issue" button in the top right of the editor. The first line will be the issue title. Assignees and Labels follow after a blank line. Leave an empty line before beginning the body of the issue. -->

As a point, this seems to work fine in Windows vscode... which is what is bugging me.  I am not well versed in debugging vscode extensions, so my attempts to try to debug what's going on have unfortunately failed.  If you have suggestions on how to give it a go to step-wise debug it, I would give it a shot.
I've tried logging out and back in to github via the extension as well, but that doesn't effect it.

I tested with on Ubuntu, but I'm still unable to repro.
Can you try leaving a blank line between the "Labels:" line and the issue body? I still saw the issue get created without leaving a blank line when I tested, but the format is such that the blank line mentioned in the comment is supposed to be there.

Hi @alexr00,
Sorry for the delay.  I just tried it again today and... well... now it's working.  I have no idea what has changed or what is causing it to work now.  I guess my only remaining question is, if I run into it again, and nothing shows up in the logs, what is the best way to debug this?  Short of the answer to that question, which may be a separate issue, this can probably close as it's clearly an issue on my machine, for some reason....

I JUST HAD AN EPIPHANY!  Here is some more information about this that may be helpful for you to recreate.  I have a git submodule in the project I am working on.  If I have another file open in the editor, the NewIssue.md window opens up without asking me what repo to add the issue to.  If I close all open editors, and click the add issue button, it asks me what repo to add it to and then it works.  I think this starts to pinpoint what is going on here.

Closing since I was never able to repro. @jhujasonw if you're still seeing it we can keep trying to diagnose the problem.


【question】peaks is not the best match

@thijstriemstra
@katspaugh
In the process of learning, I find that my Audition is inconsistent with Adobe Audition。

My expression ability is not very good, but I tried to describe the problem and hope to get your reply. I attached the relevant audio in the issue

The highest peak waveform of wavesurfer is actually not the real peak
The real peak is not shown in the waveform, and the reason is probably because of the step size of the selection algorithm
wavesurfer and adobe audition time stamp location do not match, difference is close to 1 second

start: 422205, end: 436073, lenght: 13868, maxAplitude: 13849.4228515625

wavesurfer 10+s
adobe audition 9+s

my env
Additional information：

container div width: 1280
ratio :2

wavsurfer params:
container: '#waveform',
scrollParent: true,
ignoreSilenceMode: false,
progressColor: '#3B8686',
backend: 'MediaElement',
height: 600,
normalize: true,

target wav file
02_01_P00027_01_wav_00964.wav.zip
problem1:
Looking at wavesurfer's source code, I wonder if we missed the best peak because we made some choices for performance.

buffer len: 1060737
length = 1280*2  // width 1280, ratio 2
so we have 1060737/2560=414 group, and step size 414/10 =41
And we can't customize the step size （at least not now）
https://github.com/katspaugh/wavesurfer.js/blob/9e8aed5b964ac6c743333a8980aa5bfdb5b7cdc2/src/webaudio.js#L456-L458

problem2:
Why does it have the same peak effect as the Audition? The key is the time difference?

I think we're gonna be okay because : samplereate -> 422205/41000 = 10.2976829268 second, we are correct.
start:422205,end:436073,lenght:13868,maxAplitude:13849.4228515625

problem3:
Can the problem of missing the best peak value selected by peaks be further optimized through callback function form where we can control the step size by ourselves?

full image:
WAVESURFER:

Adobe auditon:

max aplitude
wavesurfer:

time:

start: 10.297687712585034
end:   10.635932929421768

start:422205,end:436073,lenght:13868,maxAplitude:13849.4228515625
Probem1: It's clearly not the highest waveform region in the picture
Problem2: Adobe audition The timestamps in the same area are different from waveSurfer

wavesufer:
audition with sample:
audition with time line:

I think you're right about the sample size being the root cause of these discrepancies.
Please feel free to make a pull request if you manage to hack it to look like Adobe. Probably also look into the current normalization based on the max value. It looks more monotonous than Adobe. Cheers!

why close this?

Oh because you mentioned:

I will submit PR at some time.


syscall: introduce IoctlPtr for exec_unix tests

This is a followup for https://github.com/golang/go/issues/44834. Similar issue is present in exec_unix_test.go, which calls sysctl.Ioctl() and passes Go pointers as uintptr, violating unsafe.Pointer safety rules. As sysctl.Ioctl() is exported solely for tests (and called only by exec_unix_test.go), replace it with sysctl.IoctlPtr() that accepts arg argument as unsafe.Pointer.

Thanks.  If you are going to send a patch, it's not necessary to open an issue.


Add the module path to the definition name to avoid name collisions

This PR intends to fix #357, but uses an alternative approach to #358.
With this PR, the behaviour will be as follows:
mod foo {
    pub mod bar {
        use paperclip::actix::{web, api_v2_operation, Apiv2Schema};
        use serde::Serialize;

        #[derive(Serialize, Apiv2Schema)]
        pub struct Response {
            bar: i32
        }

        #[api_v2_operation]
        pub fn b() -> web::Json<Response> {
            web::Json(Response { bar: 10 })
        }
    }
}

results in the following spec:
  foo_bar_Response:
    type: object
    properties:
      bar:
        type: integer
        format: int32
    required:
      - bar
...
          schema:
            $ref: '#/definitions/foo_bar_Response'

The advantage of this PR over #358 is that the generated spec is always the same for the same input code.
The name is determined by taking the output of std::module_path!(), removing the first 'component' (i.e. the crate name), then joining with _ as a separator.
This will not break code backwards compatibility, but it will break spec backwards compatibility, i.e. the generated spec is different from how it would be without this PR

Looks good, can we add a test for this feature?

I'll give writing a test a shot!


PEAR-1819: Handle exceptions related to login window

Description
Adding a try-catch block.
Checklist

[ ] Added proper unit tests
[ ] Left proper TODO messages for any remaining tasks
[ ] Scanned for web accessibility with aXe, and mitigated or documented
flagged issues

Screenshots/Screen Recordings (if Appropriate)

this worked for me. I didn't see the errors in the console and I was able to log in, download some CA data, and log out without anything unusual happening. 👍

Looks OK, but I agree with Amy's request for more context in the comment.

@amlehman @craigrbarnes  I just updated it. Please let me know if it's clear now.


AmMaps

Love AmCharts, AmMaps, it is a huge part of our web data display. I understand the js version but I am really struggling with the wrapper classes. Currently working on an iPad app,  I have pie charts, barcharts all working fine. I can't seem to find an example of the wrapper classes for amMaps and its killing me. Could you point me to a simple snippet of how to set up the map? Thank you.

@smuller20 take a look at the updated ReadMe.  https://github.com/chimpstudios/amcharts#world-map
You were probably just missing the chart.html template file that needs to have the proper maps added in the header section.  You can use:
setTemplateFilepath:

to use your own cloned chart.html and resources.  That way, your changes don't conflict with the master branch.

Thanks for your quick response. You were spot on with what I had overlooked. Thank you!!


Remove unused code in GI shaders

Follow-up to https://github.com/godotengine/godot/pull/52092.

Thanks!


Post Radarr and Sonarr failing due to sma.log permissions

Hello, first of all great job with the automator! Really helpful!
I know this Issue has been closed but I'm having the same situation with Radarr and Sonarr not having permissions to use sma.log, and I've used chmod and chown to change the permissions of the full directory of the script, and it works. Temporarily. I haven't figured out why or when, but after a while the sma.log files go back to their owner being root instead of pi which is my main user, and losing permissions.
This is after deleting the sma.log files and running manual.py:
drwxrwxrwx 3 pi   pi   4096 Nov 13 12:43 .
drwxrwxrwx 8 pi   pi   4096 Nov 13 12:43 ..
-rwxrwxrwx 1 pi   pi   4224 Nov  8 21:32 autoProcess.ini
-rwxrwxrwx 1 pi   pi      0 Nov  6 18:11 __init__.py
-rwxrwxrwx 1 pi   pi   1209 Nov  8 14:45 logging.ini
drwxrwxrwx 2 pi   pi   4096 Nov  8 14:45 __pycache__
-rw-r--r-- 1 root root  245 Nov 13 12:43 sma.log

Is there any configuration on the script that changes what the user and permissions that file is created with that I'm missing? You mentioned changing something in the container but I'm not sure what you meant by that. If it's related to docker then I'm not using one, I just have the script on a directory on /home/pi and run it directly from there.

The problem here is that you're running manual.py as your root user, and so when no log file exists it has no choice but to create the sma.log file as the user that's running the script
the log files also recycle with time (sma.log becomes sma.log.1) as the file size gets bigger, so if you're running lots of jobs as root then when that recycle event occurs you may end up with an sma.log file owned by root instead of pi. I would suggest just being consistent as to which user is running the script

That solved it! I was using sudo nohup to run manual.py in the background, but didn't know that by using that command I was basically running at as root. Quick search, changed the command to sudo -u user and now the logs are being created with the proper user. Thanks for the quick reply!


feat: author

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

6 of 6 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.007%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
821

Relevant Lines:
867

💛  - Coveralls


Create assume role variable for Instance Scheduler

Released on https://github.com/gravicore/terraform-gravicore-modules/releases/tag/0.11.1


[kwokctl] Support enable admission plugins

What would you like to be added?
TODO
Why is this needed?
The admission plugins are currently disabled by default, and we need a way to enable it

https://kubernetes.slack.com/archives/C04RG2YSK16/p1679581435316099


Update brouter.md

Improved and expanded existing text for clarity.

PS. If someone can explain where to upload it to, I can add a new profile image (in English)!

@EugeneZmeuk I still don't see the update on the webpage. (I have deleted the cached files!)
Could you update the image or point me to how and where to do it. Thanks.

@EugeneZmeuk I still don't see the update on the webpage. (I have deleted the cached files!)
Could you update the image or point me to how and where to do it. Thanks.

I have updated the web

@EugeneZmeuk I still don't see the update on the webpage. (I have deleted the cached files!)
Could you update the image or point me to how and where to do it. Thanks.

I have updated the web

That's better. Thanks.
Can we sort the image too, please.

@EugeneZmeuk I still don't see the update on the webpage. (I have deleted the cached files!)
Could you update the image or point me to how and where to do it. Thanks.

I have updated the web

That's better. Thanks.
Can we sort the image too, please.

done


Reduce staging overhead on subset workflows

This PR does a couple of things ...

Fixes bin/diann_convert.py, it was failing when no ambiguous protein groups are present (Line 590). + some minor cleanup and auto formatting...
bin/mzml_statistics.py adds better error messages and prevents a general exception handle
workflows/dia.nf fixes the workflow ... even though the last version was only searching a subset of the files, all of them were still being staged, this change stages only the needed ones.
workflows/quantms.nf (untested ..) fixes an issue where no slack messages were sent when the pipeline failed.

For some reason the majority of URLs are failing
ERROR ~ ERROR: Please check input file -> File Uri does not exist!
https://ftp.pride.ebi.ac.uk/pride/data/archive/2019/09/PXD007058/SF_200217_pPeptideLibrary_pool1_HCDnlETcaD_OT_rep1.raw

But they actually exist :(

could it be that the sever is noticing the same server pulling too many images at once and denying the request?
we had to add this to our nextflow config due to a similar issue
aws {
    batch {
        maxTransferAttempts = 3  // defaults to 1 <-------- This one was critical
        maxParallelTransfers = 5  // defaults to 5 ... on some nextflow versions
        delayBetweenAttempts = 20  // defaults to 10
    }
}

Interesting, we didn't have this problem before. @jpfeuffer do you remember this issue?


Accepted values in backcall/pipeline operator.

Hello. While trying to move one of my projects over from Moonscript to MoonPlus, I tried to do the following:
readFile "example.txt"
  |> (_) -> extract _, language, {}
  |> (_) -> parse _, language
  |> emit
  |> render
  |> print

But I was met with the following error:
Fail to compile: fir/generic/emit/markdown.mp.
193: backcall operator must be followed by chain value
  |> (_) -> extract _, language, {}
    ^

In this case, some questions or proposals come to mind:

What counts as a "chain value"?
Could a function be supported in a future update, as in my snippet?
Could there be a simpler way to do what I'm trying to do? Something along the lines of |> extract $, language, {} or |> extract @, language, {}.
Although this isn't a serious complain, the Fail to compile error does not roll off the tongue very well, maybe something like Could not compile or Failed to compile?

A chain value for backcall syntax could be one of the followings:
Callable:

@, @field, (a + b), func, t.func, t\func, t.func?, $macro

Invoke:
f!, f(1,2,3), $macro!, $macro(1,2,3)

DotChainItem:
with t
  1 |> .func

ColonChainItem:
with t
  1 |> \func

The accepted form for your example could be

readFile("example.txt")
  |> ((_)-> extract _, language, {})
  |> ((_)-> parse _, language)
  |> emit
  |> render
  |> print

-- or

readFile("example.txt")
  |> extract(language, {})
  |> parse(language)
  |> emit
  |> render
  |> print

The back call operator has a higher operator precedence. Without brackets the codes would be compiled as:
-- the example without proper brackets
readFile "example.txt"
  |> extract language, {}
  |> parse language
  |> emit
  |> render
  |> print
-- is treated like
readFile ("example.txt" |> extract language, ({} |> parse (language |> emit |> render |> print)))

It is really a problem. Got it fixed. 6a48f108666126893dcf7ff54b12172795858d3a

A chain value for backcall syntax could be one of the followings:
Callable:

@, @field, (a + b), func, t.func, t\func, t.func?, $macro

Invoke:
f!, f(1,2,3), $macro!, $macro(1,2,3)

DotChainItem:
with t
  1 |> .func

ColonChainItem:
with t
  1 |> \func

The accepted form for your example could be

readFile("example.txt")
  |> ((_)-> extract _, language, {})
  |> ((_)-> parse _, language)
  |> emit
  |> render
  |> print

-- or

readFile("example.txt")
  |> extract(language, {})
  |> parse(language)
  |> emit
  |> render
  |> print

The back call operator has a higher operator precedence. Without brackets the codes would be compiled as:
-- the example without proper brackets
readFile "example.txt"
  |> extract language, {}
  |> parse language
  |> emit
  |> render
  |> print
-- is treated like
readFile ("example.txt" |> extract language, ({} |> parse (language |> emit |> render |> print)))

It is really a problem. Got it fixed. 6a48f108666126893dcf7ff54b12172795858d3a

Thank you for the help!

Thank you for the help!

Just found that I missed a question. There is a syntax for your need:
readFile("example.txt")
  |> extract(_, language, {}) -- _ is a placeholder here instead of a variable indicating where to insert the argument
  |> parse(_, language)
  |> emit
  |> render
  |> print

2 |> func(1, _, 3) -- will be compiled to func(1, 2, 3)

Just found that I missed a question. There is a syntax for your need:
readFile("example.txt")
  |> extract(_, language, {}) -- _ is a placeholder here instead of a variable indicating where to insert the argument
  |> parse(_, language)
  |> emit
  |> render
  |> print

2 |> func(1, _, 3) -- will be compiled to func(1, 2, 3)

Changed the backcall operator syntax.
readFile "example.txt"
  |> extract language, {}
  |> parse language
  |> emit
  |> render
  |> print

will be compiled to the expected output with latest commit, extra parentheses are no longer needed.
return print(render(emit(parse(extract(readFile("example.txt"), language, { }), language))))


Allow to change config file (sub)directory

This allows the xrdp part of the path /etc/xrdp where config files are placed to be customizable. This change is useful when trying the stable version and the devel version alternately.

That's a great idea, and better than the solution I've hacked together on my development workstation.
Also there's a couple of /etc/xrdp/ strings embedded in C files. You may want to sweep these up if it's not too difficult. Here's some links to your repo:-

https://github.com/metalefty/xrdp/blob/854d060917c207177205f5d9e086081889a8cd8d/keygen/keygen.c#L466
https://github.com/metalefty/xrdp/blob/854d060917c207177205f5d9e086081889a8cd8d/genkeymap/genkeymap.c#L96

I have no idea why cppcheck complains to the former but doesn't to the latter. Anyway, I can pet cppcheck.
fprintf(stderr, "Example: %s -r evdev -c \"en-US pc104 keyboard\" "
        XRDP_CFG_PATH "/km-00000409.toml\n", programname);

fprintf(stderr, "Example: %s -r evdev -c \"en-US pc104 keyboard\" ", programname);
fprintf(stderr, XRDP_CFG_PATH "/km-00000409.toml\n");

cppcheck has some code to try to guess values of macros it can't find a definition for. Normally it uses 1 (without quotes) which breaks some uses of string macros.
@firewave may have something useful to contribute on this example.
Personally, I'm happy with the change you've made for cppcheck. However, if you'd rather use your first fprintf line you could make use of a workaround that's present further up in the file for cppcheck and PACKAGE_VERSION. It will prevent cppcheck having to guess at all:-
-- a/genkeymap/genkeymap.c
+++ b/genkeymap/genkeymap.c
@@ -49,15 +49,21 @@
 #include "scancode.h"
 #include "xrdp_constants.h"

-// cppcheck doesn't always set this macro to something in double-quotes
+// cppcheck doesn't always set PACKAGE_VERSION and
+// XRDP_CFG__PATH to something in double-quotes
 #if defined(__cppcheck__)
 #undef PACKAGE_VERSION
+#undef XRDP_CFG_PATH
 #endif

 #if !defined(PACKAGE_VERSION)
 #define PACKAGE_VERSION "???"

Let's merge this as-s and make further changes if cppcheck complains again.


azure: populate ApplicationSecurityGroups field in the new IPConfigurations

Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[x] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[x] All commits are signed off. See the section Developer’s Certificate of Origin
[x] Provide a title or release-note blurb suitable for the release notes.
[x] Thanks for contributing!

Azure wants all IPConfigurations to have the same
ApplicationSecurityGroups. So if the primary IPConfiguration is already
assigned an ApplicationSecurityGroup, adding a new IPConfiguration
without any ApplicationSecurityGroup fails. So we should populate
ApplicationSecurityGroups field that is the same as ASG of other
IPConfiguration.
Fix a bug that was causing Azure IPAM to not work when ApplicationSecurityGroups were attached to IPConfigurations of a NIC.

Could you also share how you found out about this or how we can repro?

Unfortunately, I couldn't find any Azure documentation on this. Also, AKS by default doesn't assign any ASG/NSG to the IPConfiguration/NIC on creation and so it would be hard to reproduce this in an AKS cluster.
We have a self-managed kubernetes cluster on Azure where we assign ASG to the primary IPConfiguration of the NIC during VMSS Nodepool creation. So when we deployed Cilium, we see errors in cilium-operator-azure logs -
unable to update virtualmachinescaleset: All IPConfigurations on a Network Interface should reference the same set of Application Security Groups. IPConfiguration Cilium-1 references ASG(s) , wheras IPConfiguration /subscriptions/$SUB_ID/resourceGroups/$RG_ID/providers/Microsoft.Compute/virtualMachineScaleSets/aks-ng3-34239724-vmss/updateGroups/894ddb7a-15af-4726-816d-cd5592ce3df4/networkInterfaceConfigurations/aks-ng3-34239724-vmss/ipConfigurations/default references ASG(s) /subscriptions/$SUB_ID/resourceGroups/$RG_ID/providers/Microsoft.Network/applicationSecurityGroups/nodepool.

Also, I feel this needs a backport to 1.9 (and 1.8 too maybe?) as this is a bug.

Added @twpayne as a reviewer since this might be of interest on the IPAM side.
@aanm What do you think regarding backporting?

kind ping @twpayne


feat(notifications): Implement PATCH /subscription V2 API

PR Checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/master/.github/Contributing.md.
Issue Number: #3143
What is the new behavior?
Per https://app.swaggerhub.com/apis-docs/EdgeXFoundry1/support-notifications/2.x#/default/patch_subscription, implement PATCH /subscription V2 API.
Close #3143
Does this PR introduce a breaking change?

[ ] Yes
[x] No

New Imports

[ ] Yes
[x] No

LGTM, does this still need to be in Draft?
Thanks. Converted to Ready-for-Review.

Codecov Report

Merging #3148 (f56f5be) into master (261101c) will increase coverage by 0.23%.
The diff coverage is 58.54%.

@@            Coverage Diff             @@
##           master    #3148      +/-   ##
==========================================
+ Coverage   41.38%   41.61%   +0.23%
==========================================
  Files         174      176       +2
  Lines       14536    14727     +191
==========================================
+ Hits         6015     6128     +113
- Misses       8187     8259      +72
- Partials      334      340       +6

Impacted Files
Coverage Δ

internal/pkg/v2/infrastructure/redis/client.go
0.00% <0.00%> (ø)

...ternal/pkg/v2/infrastructure/redis/subscription.go
0.00% <0.00%> (ø)

internal/security/proxy/init.go
0.00% <0.00%> (ø)

...nternal/security/bootstrapper/helper/redis_conf.go
46.66% <46.66%> (ø)

internal/security/bootstrapper/helper/helper.go
81.25% <81.25%> (ø)

...t/notifications/v2/controller/http/subscription.go
88.07% <93.93%> (+4.88%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5c26320...1e9658d. Read the comment docs.


Is it possible to add support for replicas?

Is it possible to add support for deploy: replicas. So I can run the same container multipole times for traefik?

Can you explain how you expect that would work under the hood? Would it just be that the single service maps to N identical containers in the generated Nix config?
To be frank, until now, the Deploy spec has been out of scope since its not really part of the core Compose spec. But if the feature is not complicated and only relies on a single machine (i.e. not Swarm), I am open to considering it.


Lint Markdown files

Currently, we manually check the syntax and style of Markdown files. The review process is time-consuming and can be inconsistent. It's better to automate the check so that reviewers can focus on the contents and clarity.
Actions

[x] Set up pre-commit and CI
[ ] Fix all the remaining issues

Hi, @tetsuok
A lot of new errors appeared regarding markdown lint when making a new PR, for example https://github.com/neulab/ExplainaBoard/actions/runs/3211437027/jobs/5249605967

@pfliu-nlp The linter found that the change doesn't follow the rules. It's not a bug in the linter. Found errors need to be fixed in the same way as we fix errors found by flake8.  Would you fix them?

@pfliu-nlp Some trivial errors can be fixed automatically by running 'pre-commit run markdownlint-cli2-fix --all-files'.

@tetsuok : I think the issue was probably that the PR that @pfliu-nlp was working on had not yet merged in the main branch. I just did it now, so let's see if that fixes the problem.

@neubig Ok. Thanks for the update.


marker shadows

I see you have SVG shadows on your todo list.
What I am doing is using css to create the drop shadows, it's not as pretty as handmade png shadows (which kind of defeat the idea of svg markers ;-) ), but maybe one can tweak the values. This is what I'm doing:
Create the marker

              var myVectorMarkerIcon = L.VectorMarkers.icon({
                prefix: 'fa',
                icon: 'check',
                markerColor: 'lightgray',
            });

and then in with css (note that you need to set the style specifically for the full class with the marker color. Note also that this shadow settings is for the default marker):

.vector-marker-icon-blue:before {
     position: absolute;
     content: "";
     z-index: -1;
     right: 22px;
     bottom: -5px;
     width: 60%;
     height: 30%;
     box-shadow: 30px -10px 10px rgba(0,0,0,0.4);
 -webkit-transform: skew(150deg);
 -moz-transform: skew(150deg);
  -ms-transform: skew(150deg);
  -o-transform: skew(150deg);
    transform: skew(150deg);
    -webkit-transform-origin: 50% 50%;
     -moz-transform-origin: 50% 50%;
    -ms-transform-origin: 50% 50%;
    -o-transform-origin: 50% 50%;
    transform-origin: 50% 50%;
 }
}

Result:

edit: there might be a way to embellish the shadow by using the drop-shadow filter in css but I haven't trie it yet.

This seems to be implemented in https://github.com/hiasinho/Leaflet.vector-markers/commit/32eccc34bc0f612d73af7062d1d48e81bd9628eb


explain the impact on build caching more clearly(2)

Another pr #20745
Signed-off-by: mikelinjie<EMAIL_ADDRESS>

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "dry-run-test" git@github.com:mikelinjie/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

ping @mikelinjie can you fix the missing sign-off?

I have ？
make the cache miss clear …
Signed-off-by: mikelinjie<EMAIL_ADDRESS>√ 248b1be

Thanks, two nits, but LGTM after those are addressed

Oh, and can you squash your commits, so that there's only a single commit in this PR?

ping @thaJeztah finish it

LGTM, thanks!

ping @mikelinjie can you address @MHBauer's comment?

It looks reasonable to me, but i guess @moxiegirl meant to ping @mikelinjie ;-)

Yes, I think she got hit by GitHub autocomplete doing its work :D

carried in https://github.com/docker/docker/pull/21790


compose-ui: build generic plugin view and compact view

With related to https://github.com/atsushieno/aap-core/issues/158 , now we can let plugin provide their native View reflected on the host's SurfaceView. We could provide our default generic view based on androidaudioplugin-ui-compose.
So far, current PluginDetails is not really designed to be usable in standalone form. We need a reasonably shrinked form of the plugin view.
Also, when we want to achieve compact mode (like Logic Pro for iPad or even earlier Bitwig Studio internal plugins panel), we could also provide a compact view for each plugin. The number of parameters there will be limited (filtered by "show on compact" kind of property for each parameter).

Current status (generic non-compact view):

Generic plugin view is alive, and now parameters extension has "priority" property.
We should probably have to think about more than just a generic compact view though: current default UI is already compact-ish, and it is rather a matter of (1) what window size should be the default, and (2) whether we should have bigger UI, not smaller (once bigger ones are set in stone, we could treat current view as "compact").


Failed test's error points to Chai

See e.g. https://travis-ci.org/ckeditor/ckeditor5-engine/builds/173847164#L7972:
Error: Uncaught AssertionError: expected 1 to equal 2 (/home/travis/build/ckeditor/ckeditor5-engine/node_modules/chai/chai.js:206)

This is pretty useless if a test have more assertions. In the screenshot I can see that with some other assertion lib it works fine, so perhaps it's a problem with Chai. But what could help (and in fact, be pretty useful in general) was if a longer stack trace was logged in case of a failed assert.

There is no limitation in the length of the stack trace. The reporter just displays the value coming from karma. So I guess this must be a problem specific to chai. I have tested it locally with the test included in this repository and they work fine.

Hmm... We'll have to dig into this. I've got some theories and I'm curious now which one of them it is – Webpack, source maps, different assertion function used. I'll let you know if we find something :).
Thanks! :)

I've had similar frustrations with stack traces using the same tech stack (except browserify instead of webpack). I don't remember the particulars of it now, but I traced it back to karma (or maybe karma-mocha?) itself messing with the stack traces.

I debugged this. It turns out that we had a broken test which caused an async error to be thrown so it was caught by mocha's native onerror listener. So it has the stack of length 2 and this is quite understandable now (or at least more acceptable, taken the sourcemaps) that we got this a bit useless error. I'm only unsure why it's 1!=2 assertion, but I won't have time to debug it further now, so I must live with this :D.
Thanks for the help! :)


Debug_scan fails if www directory is not present

Describe the bug
If www sub-directory is not present in config directory, debug_scan fails
To Reproduce
Steps to reproduce the behavior:
Remove www directory and try to run debug_scan
Expected behavior
During debug_scan initialize, when opening/appending /config/www/bosch_scan.json, please add check for www directory existence. If not existing, then create it.
Screenshots
n/a
Version

HA Core 2022.6.6
HA Bosch component version 0.18.0.dev5
Python Bosch HTTP client version?

** Debug SCAN **
** IMPORTANT **
Go to Developer tools in Home Assistant, choose Service tab and choose bosch.debug_scan
Download file to your computer and upload it somewhere eg. https://jsonblob.com/
Additional context
Add any other context about the problem here.

https://github.com/bosch-thermostat/home-assistant-bosch-custom-component#bosch-system-scan-via-raw-scan

Integration is not allowed to create dir for you.

It see now. It's a pitty.
Thank you


Potential dangers of reverse lookup in "describe" view

Whilst viewing https://usepa.3roundstones.net/usepa/data/rcra?query=describe+<http://usepa.3roundstones.net/rcra/handlers/OHD000816801> I made the mistake of clicking the chevrons against the object http://usepa.3roundstones.net/rcra/land-type/P (the landType predicate appears after the list of hasActivity predicates). I got no response and the server needed a restart after this due to running out of memory. As soon as I clicked it I realised what would happen but it was too late.
I believe the problem is that the describe page, as well as describing the object specified, includes a reverse lookup of triples referencing the object. In this case there would have been millions so it highlights how easy it is to cause a problem when you don't have a good understanding of the data. I was clicking around the describe page to try and gain this understanding.
Does the describe page use a select query to perform that reverse lookup and is there a limit on it? Is there anything we can do to protect users from mistakes like this?

See also https://openrdf.atlassian.net/browse/SES-1904

Resolution by phone: Perform a count of the describe on each URI in the query results when building the page. The hyperlink on the chevrons will resolve to the SPARQL query page populated with the generated query in the event that the count is "too high", and will include an error message saying that the number of results is too large. Small counts will result in the existing behavior.


aws.eks.Cluster opting into EKS Auto Mode with built in node pools is currently requiring the cluster to be replaced

Describe what happened
Users should be able to opt into EKS Auto Mode with existing clusters without requiring the cluster to be recreated. This is possible without using the built in nodepools, but currently not possible if users utilize one of the built in nodepools (system, general-purpose)
The set behavior is:

Enabling computeConfig.enabled and setting a computeConfig.nodeRoleArn is a valid in-place change
Disabling computeConfig.enabled even with a computeConfig.nodeRoleArn specified is a valid in-place change. The role is essentially a noop at thi point
With computeConfig.enabled, changing computeConfig.nodeRoleArn from one ARN value to another is not a valid in-place change; this change can only be made by re-placing the cluster

Currently, opting into EKS Auto Mode with an existing cluster and specifying a computeConfig.nodeRoleArn is wanting to replace the cluster since the nodeRoleArn value is changing (from undefined to defined). This should be a valid transition that does not require replacements.
This is caused by the following upstream bug: https://github.com/hashicorp/terraform-provider-aws/issues/40411
Sample program
n/a
Log output
n/a
Affected Resource(s)
aws.eks.Cluster
Output of pulumi about
pulumi-aws v6.63.0
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

The upstream issue has been fixed, waiting for the next upstream release to pull the fix

Fixed by #4925


chore: derive serialize and deserialize for chain info

Pull Request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

This change is

#97  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ArniStarkware and the rest of your teammates on  Graphite

Merge activity

Jul 31, 4:24 AM EDT: @ArniStarkware started a stack merge that includes this pull request via Graphite.


EVERYWHERE in your challanges the mouse pointer does not respond well. You click on row X but then it writes on a lower line.

Challenge Add Font Awesome Icons to our Buttons has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

<link href="https://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">

CatPhotoApp

      <button class="btn btn-block btn-primary">Like</button>

      <button class="btn btn-block btn-info">Info</button>

      <button class="btn btn-block btn-danger">Delete</button>

Things cats love:

cat nip

laser pointers

lasagna

Top 3 things cats hate:

flea treatment

thunder

other cats

  <form action="/submit-cat-photo">
    <input type="radio" name="indoor-outdoor"> Indoor
    <input type="radio" name="indoor-outdoor"> Outdoor
    <input type="checkbox" name="personality"> Loving
    <input type="checkbox" name="personality"> Lazy
    <input type="checkbox" name="personality"> Crazy
    <input type="text" placeholder="cat photo URL" required>
    <button type="submit">Submit</button>
  </form>

@Drizzt-14 we apologize for this inconvenience. This is a known problem #8253 #7847 and it is more of an issue with our editor CodeMirror. Please read through those links I've provided. Some users have talked about how they've gotten around this issue. Happy coding otherwise!

Thank you for reporting. This is not a directly actionable issue here on Free Code Camp. This is a known issue with CodeMirror. Please comment here codemirror/CodeMirror#1862.
If what you are seeing is not the same as the issue, open a new issue with CodeMirror with steps to reproduce.


Use of string instead of byte[]

During an empirical study to understand the nature of cryptographic misuses in enterprise-driven projects on GitHub, we randomly inspected a few of the misuses. One of the misuses for which we could confirm as a true positive of the analysis, CogniCryptSAST, is in this project.

In the class ninja.AwsLegacyHashCalculator (L. 113)   a string is passed as a secret key and that is considered insecure. In Java, strings are immutable and stay in memory until collected by Java's garbage collector. Thus, they are longer visible in memory for attackers than necessary and outside of the direct control of the developer. The suggested data types by the JCA are bytes.

Hallo @akwick 👋 Wow. Krass. 🤩
First of all, many thanks for this. We really appreciate your efforts, both for our product here, and in a wider sense, as a company relying on secure products running in a secure environment.
Having said that, we are not going to fix this particular line. 🙃 (Yeah, I know, strange twist. 😅) You see, S3 Ninja is a development tool designed to serve as a mockup during development of AWS S3 connected software. It never (really, never) should be used to store any real data, for a wide range of reasons, including security, reliability, performance, scalability, etc. (Rather the lack thereof.) The password, in fact, is in a plain-text file in this very repository, and an attacker will have access to that file long before getting even close to the memory controlled by the JVM. The sole purpose of S3 Ninja is to save some bucks during development. It never should be exposed to anyone outside of a LAN/VPN. Ideally, it should only run as a Docker container on the developer's computer, and it only should contain funny pictures of cats & dogs downloaded from the internet and transmitted for testing purposes. 😉
However, in general, your point is very valid, of course. If anyone reading this wants to submit a PR demonstrating the proper use of byte arrays instead of strings, we will happily accept it. For now, if you want, you could also add a comment in the file, warning people against blindly copying this piece of code. If you want to document your finding yourself (also in the sense of getting the "contributor" tag on GH), please submit a PR. Else, I will add a respective comment myself. Would that be ok?
Herzlichen Dank nochmals. Wir sind alle hin und weg von der Aktion. Großartig. Wirklich krass. 😊

By the way, your point causes us to cross-check our production libraries and non-public code for similar issues. So, maybe, it still will turn out to have positive security effects behind the scenes. 😉

Thanks for your friendly response! 🙏  I hope for your software quality that you did not find any security issues within your production libraries or public code.
As you may see I created a pull request with the comment you suggested above. 😄

Many thanks again, @akwick. Keep up the great work!


Commandline lotus_demo help is broken

Describe the bug
Command line lotus_demo help is broken because of forgotten character ,, this turns the string has a tuple and make Django to fail on an error. However the command line itself is still working.
https://github.com/emencia/django-blog-lotus/blob/8c05253b085c3a85d43d688c9d4ee99b5a9062d0/lotus/management/commands/lotus_demo.py#L143
Environment
Describe your environment:

Plateform: Any
Python version: Any
Django version: Any
Lotus version: 0.8.1

Expected behavior
The command help should not raise any error, the fix is simple as removing the character from the previously pointed line.

Done in v0.9.0-pre.2


Huntsville AL Update

Email from the lead of Code for Huntsville
"Hi Adams...
Just a quick note of gratitude and a quick update... no, we did not fall off the edge of the world.
We are using the android tracker app. I put it on my phone and it worked right out of the box... Well done kudos!! We will probably create a branch here so we can change the default variables in the setting and a couple of other minor tweaks. If we run into any major issues we will coordinate with you. Adam H was right, it was all much easier than I was building it up in my mind. And all the Android dev work came right back to me once I got into the code.
As for the other parts, we are using a different stack... node.js (express.io) using sockets with the client so updates are very fast, and a mongolab instance for data repo. When we have that all down and a better web client we'll let you know so if you want to incorporate a sockets solution into your code you can. (https://github.com/codeforhuntsville/transitTracks - caution it is still rough around the edges).
Our schedule is ambitious, but that is because you did all of the hard work. We think we will have a public prototype running on a public facing website (we will not be doing client iOS or Android app at this time) in time for the Holiday Season in Downtown Huntsville which has a weekend entertainment trolley like Greensville. If that works out in the month of December we will roll out a system-wide application shortly after the new year. The app is running under development on http://transitTracks.herokuapp.com if the red trolley is far away from downtown that is because I'm still tracking my phone and not a trolley.
Anyway, this is getting way too long for a thank you note so I just say Thank you! Great work!"

Awesome! Do you know how they found it Adam?
On Nov 18, 2015 10:40 AM, "Adam Gautsch"<EMAIL_ADDRESS>wrote:

Email from the lead of Code for Huntsville
"Hi Adams...
Just a quick note of gratitude and a quick update... no, we did not fall
off the edge of the world.
We are using the android tracker app. I put it on my phone and it worked
right out of the box... Well done kudos!! We will probably create a branch
here so we can change the default variables in the setting and a couple of
other minor tweaks. If we run into any major issues we will coordinate with
you. Adam H was right, it was all much easier than I was building it up in
my mind. And all the Android dev work came right back to me once I got into
the code.
As for the other parts, we are using a different stack... node.js (
express.io) using sockets with the client so updates are very fast, and a
mongolab instance for data repo. When we have that all down and a better
web client we'll let you know so if you want to incorporate a sockets
solution into your code you can. (
https://github.com/codeforhuntsville/transitTracks - caution it is still
rough around the edges).
Our schedule is ambitious, but that is because you did all of the hard
work. We think we will have a public prototype running on a public facing
website (we will not be doing client iOS or Android app at this time) in
time for the Holiday Season in Downtown Huntsville which has a weekend
entertainment trolley like Greensville. If that works out in the month of
December we will roll out a system-wide application shortly after the new
year. The app is running under development on
http://transitTracks.herokuapp.com if the red trolley is far away from
downtown that is because I'm still tracking my phone and not a trolley.
Anyway, this is getting way too long for a thank you note so I just say
Thank you! Great work!"
—
Reply to this email directly or view it on GitHub
https://github.com/codeforgreenville/trolley-tracker/issues/108.

I was talking to them about ImagineThat.io

Nice
On Thu, Nov 19, 2015 at 7:22 AM, Adam Gautsch<EMAIL_ADDRESS>wrote:

I was talking to them about ImagineThat.io
—
Reply to this email directly or view it on GitHub
https://github.com/codeforgreenville/trolley-tracker/issues/108#issuecomment-158071551
.

Additional update:
From Larry:
We have had two successful weekends of trolley tracking so I think we are going to go with a live prototype starting this weekend...
I'm putting together the about page today and giving credits...
I'll list the Code for Greenville Brigade and would like to give special notice to Adam Hodges since the part of your code we are using is the tracker-agent.
Do you want me to list all of your team members? if so can you send me their names again. Ed Note: Hodges asked to just list Code for Greenville and not to have any one person spotlighted.
BTW we did go with an express.io and sockets solution on a node.js stack... using mongoDB for data.
Can see where we are today at http://transittracks.herokuapp.com sometime Friday morning I'll point out new domain HopAroundHuntsville.com at the Heroku server...


makes emojicategories readable by separating with newlines

While fixing something with emojis I stumbled with this one liner file, which makes it hard to edit/find stuff in atom
had to convert to this to look for what I wanted
In any doubt, don't merge this

haha, so i don't merge.


Karpenter erroring with "Could not wait for Cache to sync"

Version

Karpenter Version: v0.25.0

Kubernetes Version:  v1.23.16-eks-48e63af
Expected Behavior
We have a huge cluster having 20K+ Pods and around 2200 Nodes. Karpenter informers shouldn't timeout and there should be an option to tweak the timeout.
Actual Behavior
Logs point to the fact that Karpenter was not able to sync informer caches.
Steps to Reproduce the Problem
We turned off consolidation in our Provisioners to make Karpenter work, and gave it 6Gigs of memory.
Resource Specs and Logs
Few of the log entries:
	Could not wait for Cache to sync	{"commit": "beb0a64-dirty", "controller": "node", "controllerGroup": "", "controllerKind": "Node", "error": "failed to wait for node caches to sync: failed to get informer from cache: Timeout: failed waiting for *v1alpha5.Provisioner Informer to sync"}
{"commit": "beb0a64-dirty", "controller": "node", "controllerGroup": "", "controllerKind": "Node", "Node": {"name":"<REDACTED>.us-west-2.compute.internal"}, "namespace": "", "name": <REDACTED>.us-west-2.compute.internal", "reconcileID": "ab8d6386-e166-4541-8903-31f9c993b6cb", "error": "Timeout: failed waiting for *v1.Node Informer to sync"}
ERROR	controller.deprovisioning	determining candidate nodes, listing provisioners, Timeout: failed waiting for *v1alpha5.Provisioner Informer to sync	{"commit": "beb0a64-dirty"}
Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Can you share the output of kubectl get crds on your cluster?

I fear thats huge list, because we have Crossplane which generates 100s of CRDs.
For now, let me know if only the count works for you ?
k get crds | wc -l
     295

I'm mainly just interested in Karpenter crds so you could just do kubectl get crds | grep karpenter

Sure.
awsnodetemplates.karpenter.k8s.aws                                2022-09-13T07:53:05Z
karpenterreservednode.constraints.gatekeeper.sh                   2022-03-31T11:44:59Z
provisioners.karpenter.sh

Got it, so the issue does appear to be related directly to the cache timeout. I'm surprised that the Provisioner informer cache timed out. How many Provisioners are you running with Karpenter on your system?

Just 4 Provisioners. The logs above also contains Node timeouts:
"Timeout: failed waiting for *v1.Node Informer to sync"}

Would extending the current timeout to work such that it works at your scale be sufficient? I'm mainly just wondering if we need to expose this as a config option if we can just wait for a longer time than the default controller-runtime setup gives us.

The logs above also contains Node timeouts

I'll try and repro this at the same scale. I'm surprised it's Node informer timeouts and not also Pod informer timeouts. Especially at the scale of pods that you are running at, I'd expect that to the main thing to be timing out here.

Would extending the current timeout to work such that it works at your scale be sufficient? I'm mainly just wondering if we need to expose this as a config option if we can just wait for a longer time than the default controller-runtime setup gives us.

I am going to turn on the consolidation back on again on Monday, and see if we again face these timeouts.
If we again see those issue, we may need that as a config option to see if that works.
How many controllers does consolidation alone run ?

I am going to turn on the consolidation back on again on Monday, and see if we again face these timeouts

Ah, so this issue went away when you turned off consolidation? What are your CPU requests that you are running the Karpenter pod on?

How many controllers does consolidation alone run

It's a single controller that runs in a loop but it is fairly cpu-intensive as it's doing a lot of computation to mock out the best cost-savings for your cluster

Resources for Karpenter.
          limits:
            cpu: "2"
            memory: 8Gi
          requests:
            cpu: "2"
            memory: 6Gi

Ah, so this issue went away when you turned off consolidation?

Yeah thats the theory, because we raised memory to 6Gigs and still Karpenter didn't launch instances. I can confirm this with team, if we want to enable consolidation next Week to confirm if current resources dont allow consolidation to work, because its production and might cause an outage.
Also apart from manually matching the pod startup timestamp and the first instance launch timestamp, is there any metric that gives us this information related to the time taken for controllers to be fully ready.
I believe its taking almost 15 mins after a Karpnter pod restart to finally be ready.

I believe its taking almost 15 mins after a Karpnter pod restart to finally be ready.

That's surprising. That certainly shouldn't be the case. If you're able to repro this, we definitely need to dig into what's bottlenecking here.

I ran into the same issue once I turned of the settings.featureGates.driftEnabled to true as well. I'm stuck on cluster sync for close to 16m now
2023-04-18T17:30:51.567Z	DEBUG	controller.inflightchecks	discovered EC2 instance types zonal offerings for subnets	{"commit": "d01ea11-dirty", "node": "ip-xxx.us-west-2.compute.internal", "subnet-selector": "{\"karpenter.sh/discovery\":\"xxxx\"}"}
2023-04-18T17:30:51.690Z	DEBUG	controller.deprovisioning	waiting on cluster sync	{"commit": "d01ea11-dirty"}

I was able to add more CPU to 2.0 and memory of 4 GB which solved the issue

I'm stuck on cluster sync for close to 16m now

I don't think it's actually waiting on cluster sync in this case. If it was waiting on cluster sync you would keep seeing the log over and over again. I suspect in this case, the controller is doing scheduling calculations and that's what's holding the log here. Do you see any logs in DEBUG that start with "abnormal time between runs of"?

I'm stuck on cluster sync for close to 16m now

I don't think it's actually waiting on cluster sync in this case. If it was waiting on cluster sync you would keep seeing the log over and over again. I suspect in this case, the controller is doing scheduling calculations and that's what's holding the log here. Do you see any logs in DEBUG that start with "abnormal time between runs of"?

No I don't see any issues of that sort but increasing CPU is the one solved it. These clusters are only about 10 nodes and 1000 pods.

Does these logs point out to the fact that it is taking time ?
2023-04-18T17:02:20.616Z	INFO	controller	Starting workers	{"commit": "beb0a64-dirty", "controller": "node", "controllerGroup": "", "controllerKind": "Node", "worker count": 10}
2023-04-18T17:02:20.656Z	INFO	controller	Starting workers	{"commit": "beb0a64-dirty", "controller": "provisionermetrics", "controllerGroup": "karpenter.sh", "controllerKind": "Provisioner", "worker count": 1}
2023-04-18T17:02:20.838Z	INFO	controller	Starting workers	{"commit": "beb0a64-dirty", "controller": "counter", "controllerGroup": "karpenter.sh", "controllerKind": "Provisioner", "worker count": 10}
2023-04-18T17:02:20.839Z	INFO	controller	Starting workers	{"commit": "beb0a64-dirty", "controller": "inflightchecks", "controllerGroup": "", "controllerKind": "Node", "worker count": 10}
2023-04-18T17:02:20.979Z	DEBUG	controller.awsnodetemplate	discovered subnets	{"commit": "beb0a64-dirty", "awsnodetemplate": "<REDACTED>", "subnets": ["<REDACTED>(us-west-2b)", "<REDACTED> (us-west-2c)", "<REDACTED> (us-west-2a)"]}
2023-04-18T17:02:21.766Z	DEBUG	controller.awsnodetemplate	discovered security groups	{"commit": "beb0a64-dirty", "awsnodetemplate": "<REDACTED>", "security-groups": ["<REDACTED>", "<REDACTED>"]}
2023/04/18 17:02:22 http: TLS handshake error from <IP_ADDRESS>:55942: EOF
2023-04-18T17:02:22.756Z	DEBUG	controller.deprovisioning	discovered EC2 instance types	{"commit": "beb0a64-dirty", "instance-type-count": 627}
2023-04-18T17:02:23.269Z	DEBUG	controller.inflightchecks	discovered EC2 instance types zonal offerings for subnets	{"commit": "beb0a64-dirty", "node": "<REDACTED>", "subnet-selector": "<REDACTED>"}
2023/04/18 17:12:22 http: TLS handshake error from <IP_ADDRESS>:44692: EOF
2023/04/18 17:27:23 http: TLS handshake error from <IP_ADDRESS>:33210: EOF
2023-04-18T17:27:51.023Z	INFO	controller.provisioner	pod <REDACTED> has a preferred Anti-Affinity which can prevent consolidation	{"commit": "beb0a64-dirty"}
2023-04-18T17:27:51.023Z	INFO	controller.provisioner	pod <REDACTED> has a preferred Anti-Affinity which can prevent consolidation	{"commit": "beb0a64-dirty"}
2023-04-18T17:27:51.737Z	DEBUG	controller.provisioner	relaxing soft constraints for pod since it previously failed to schedule, removing: spec.affinity.podAntiAffinity.preferredDuringSchedulingIgnoredDuringExecution[0]={"weight":100,"podAffinityTerm":{"labelSelector":{"matchLabels":{"name":"deployment-name"}},"topologyKey":"kubernetes.io/hostname"}}	{"commit": "beb0a64-dirty", "pod": "<REDACTED>"}
2023-04-18T17:27:51.801Z	DEBUG	controller.provisioner	relaxing soft constraints for pod since it previously failed to
2023-04-18T17:27:51.931Z

The start logs are from 17:02 but the first log from provisioner controller is at 17:27. This is with consolidation off.

The start logs are from 17:02 but the first log from provisioner controller is at 17:27

At the point where you start getting the "discovered" messages, the caches should be synced and the controller should be ready to receive pending pods. Are you seeing pending pods that Karpenter should consider not being considered until after that 25 minute timeframe?

Closing this one as communicated with @ra-grover over slack


Remove unused cahced omsagent windows image

Remove unused cahced omsagent windows image

@andyzhangx @ZeroMagic @nilo19 @feiskyer could you help to check the cached Windows images for azure csi/disk/file and azure-cloud-node-manager.
I think that we need to keep all versions support in AKS even for those old k8s versions. For example, we need to cache azuredisk-csi:v<IP_ADDRESS> for >=1.21.0 and azuredisk-csi:v<IP_ADDRESS> for < 1.21.0.


Game crash on startup, error 'No NoteSkins found'

I've seen this issue a lot on mac-os specific computers but have yet to see it on any windows os. I'm running windows 10 and have just downloaded the game.

Open the game from the directory it is installed and dont move the program out of the program folder.

I am. I didn't install it into the C:/Etterna directory, however, and instead installed in into a folder in my downloads. Should i reinstall?

You need to install it in a location you have permission and run the game from that location every time. Verify that the exe you are running is precisely the one that points to the Program folder within your Etterna install.

Hey, so I'm getting this on an ACTUAL mac? What do i do lol

Mind moving over to the Discord for support?
http://discord.gg/etternaonline
This is a very common problem with known solutions :)


MERN_React: 5.5 Introduction to JSON WebTokens

Description
Description
Introduction to JSON WebTokens
Domain
MERN
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

Please assign this project to me


Multi-chain

Instead of having a "default" network for all connected tabs, we want more flexibility

[ ] Optionally connect localhost tabs to anvil by default
[ ] Optionally remember per-domain chain connection

This has been fixed since the last release (#340)


Imxrt1020 enablement

Add board/device support for RT1020 based on SDK 2.5.0 release

Codecov Report

Merging #12285 into master will increase coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #12285      +/-   ##
==========================================
+ Coverage   48.28%   48.32%   +0.04%
==========================================
  Files         294      294
  Lines       44189    44189
  Branches    10600    10600
==========================================
+ Hits        21335    21354      +19
+ Misses      18589    18569      -20
- Partials     4265     4266       +1

Impacted Files
Coverage Δ

lib/cmsis_rtos_v2/kernel.c
79.16% <0%> (+39.58%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 41dfc4d...5b40e1e. Read the comment docs.


Update readme to use new Makefile targets

Signed-off-by: Adam Stokes<EMAIL_ADDRESS>

LGTM, thanks!


[formrecognizer] Rename DocumentElement to DocumentContentElement

Part of #20921

API changes have been detected in azure-ai-formrecognizer. You can review API changes here


Offsetting

Offset doesnt work on the new update (0.97.3)

Already reported and even fixed :+1:
https://github.com/Dogfalo/materialize/issues/2313
https://github.com/Dogfalo/materialize/issues/2312
https://github.com/Dogfalo/materialize/issues/2308
https://github.com/Dogfalo/materialize/commit/d5db2a3290ab2848f4482aae2933756b8e357346

Duplicate


[hold] Accessibility violations should make tests fail explicitly

Purpose
Make sure that unit tests fail and report errors if the page has accessibility violations - no more staring at the dev console and wondering.
Summary of changes
Upgrade to ember-a11y 0.2.0 to take advantage of a new feature.
Testing notes
I am presently having trouble visiting the login page with this new version; I get console errors about axe being undefined. Hold as a reminder until this is addressed. There may be weird interactions with the very newest release.

This should be fixed by the wonderfully helpful addon authors once 0.2.1 is released:
https://github.com/ember-a11y/ember-a11y-testing/pull/62
Will hold this PR until then.


events.ibd getting huge (17G)

Hello,
my database is getting out of proportion though userinterface shows just ~20.000 and I have been deleting quite a lot of them.
If I run Event.cleanup_expired! it just deletes 2 or 5 files but not more ...
EVENT_EXPIRATION_CHECK="6h" so this looks ok as well.
I am running huginn in a docker container - is there a way to directly access database and check?
Any ideas/help where i can look/clean db?
kind regards
Randy

DB Query says

Table events  is 16052MB

I found something - seems like a mysql setting issue:
Solved it by
OPTIMIZE TABLE events;
I guess the problem is a missing Parameter:
innodb_use_trim=1
freeing up space in ibd file...
Hope this helps someone else as well :-)


Mediamanager Item within a RichText field is not working in retrofit mode.

Mediamanager Item within a RichText field is not working while using retrofit mode. It is always getting failed to map the mediamanager item.
Error Details -
Sdl.Web.Common.DxaException: Unable to map field 'Content' to property of type 'Sdl.Web.Common.Models.RichText'. ---> Sdl.Web.Common.DxaException: No semantic mapping found between Schema 33274 (uuid:9389a8ce-0f19-44ee-9eb6-2d04d0c02c25:ExternalContentLibraryStubSchemamm) and model type 'Sdl.Web.Common.Models.MediaItem'
   at Sdl.Web.Common.Mapping.SemanticSchema.GetModelTypeFromSemanticMapping(Type baseModelType)

As a workaround we have created a subclass and extended the default MediaManagerDistribution model. But need proper fix for that.

Indeed, the MediaManagerDistribution View Model currentky doesn't work properly in conjunction with retrofit mode. The problem is that it only has a SemanticEntity annotation for the Core Vocabulary, but in retrofit mode, each CM Schema has its own Vocabulary (named after the Schema's namespace URI). So: an additional SemanticEntity annotation is needed for the MM Stub Schema.  Indeed, a work-around for this issue it to create abd register your own subclass which does have the appropriate SemanticEntity annotation.


Modal does not open on v5.0.0-beta1

Hello
I made 2 simple examples with identical code, for 5.0.0-alpha3 and 5.0.0-beta1
Here is link (which works) using 5.0.0-alpha3:
http://code.reloado.com/oeasyrik1/287/edit#html,live
same code, but using 5.0.0-beta1 does not work:
http://code.reloado.com/oeasyrik1/286/edit#html,live
what is the problem?
Thanks.

All data attributes are prefixed, i.e. data-bs-toggle.


Add GDS-SSO OAuth credentials for govuk-chat

trello card: https://trello.com/c/k8KTyMCx/1413-add-gds-sso-to-integration-environment

Asked in: https://gds.slack.com/archives/C013F737737/p1714645006120649

Yeah just follow the naming of the existing ones and you should be fine.

You'll need to add the app to the list here: https://github.com/alphagov/govuk-helm-charts/blob/main/charts/app-config/templates/signon-secrets-sync-configmap.yaml
There's probably nothing stopping us dropping that file now, though. I think we only introduced it because of the number of defunct applications in Signon that hadn't been cleaned up at the time. It's much tidier now so just importing everything is probably a good option.

As per the Slack chat I'm going to go and create the application in Signon in each environment before we proceed with merging

As per the Slack chat I'm going to go and create the application in Signon in each environment before we proceed with merging

Added one in integration already, just double check about the naming conventions etc.. so we could use same names in all the ENVs

Ok cool - I'll create the other ones and adjust integration if I have to for any consistency reasons

Looks like it's merged now 🎉
I've created the signon entry in prod, it'll sync to staging tonight. We won't wait for that before merging though (as far as I can tell, from Chris' changes signon won't error without Chat).
I imagine we will need to run a rake task in signon to get these secrets populated. I'm not sure on the automation schedule @sengi do you know?

These values won't have govuk- as a prefix because they're based on the signon name, which is just chat.
I think with that changed this will be good to be merged.

Done, thanks for the reviews 👍


The header is for on-premise and all drawings show cloud solution

This article is poor, as the header is for on-premise and all drawings show cloud solution. It doesn't show any graphics over the on-premise printing. Reading it make you doubt that this is for on-premise printing

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

ID: b720ef96-1322-53fd-6048-a329cf3d6405
Version Independent ID: c7f04b37-a94d-400a-da0c-b694d124b99e
Content: Document generation, publishing, and printing in on-premises deployments - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/fin-ops-core/dev-itpro/analytics/printing-capabilities-on-premises.md
Service: dynamics-ax-applications
Product: ****
Technology: ****
GitHub Login: @TJVass
Microsoft Alias: tjvass

@TJVass, please review this feedback from @amadse and consider updating this topic.

Bug 387403 has been logged to track this issue.


Confirm/update Blazor policy hashes

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

ID: 88177a7d-c9ff-c245-5629-a462c9258abf
Version Independent ID: 6e0b5c52-90a1-5ca6-bfad-df33a8beae6c
Content: Enforce a Content Security Policy for ASP.NET Core Blazor
Content Source: aspnetcore/blazor/security/content-security-policy.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

AFAIK, this has been resolved by the PU PR https://github.com/dotnet/AspNetCore.Docs/pull/23365. I'll keep an 👂 open for further feedback. I'd be happy to test in more detail myself, but I'm very 🏃😅 on high priority issues right through the end of the year into 22Q1. I suspect that if there's a problem with the latest guidance provided by the PU that our readers will sharpen their beaks and claws 🦅 for me! 😨 lol
There's also an open PU issue at https://github.com/dotnet/aspnetcore/issues/36805 that should be addressed sooner or later. We'll let the PU issue track it because it's an IF/WHEN update for the PU at this time.


Simulating sending a balance to and from different addresses

I found a video tutorial online walking through the basics of solidity. The contract that they build basically is one where you can send a balance to and from different accounts. I'm trying to figure out how browser-solidity allows you to interact with addresses. Here's my contract so far:
contract HelloWorld {
  address public owner;
  mapping (address => uint) balances;

  function HelloWorld() {
    owner = msg.sender;
    balances[owner] = 1000;
  }

  function getBalance(address _user) returns(uint _balance) {
    return balances[_user];
  }
}

When I press "Create", I get the getBalances() field that asks me for address _user. When I put in the address that the creation of the contract outputted, 0xca35b7d915458ef540ade6068dfe2f44e8fa733c, I get an error: Error encoding arguments: SyntaxError: JSON.parse: expected ',' or ']' after array element at line 1 column 3 of the JSON data.
Here's a screenshot of what I see:

I think you just need to put quotes around the address.
On 19 Aug 2016, 9:02 AM +0800, Joshua Terrill<EMAIL_ADDRESS>wrote:

I found a video tutorial online walking through the basics of solidity. The contract that they build basically is one where you can send a balance to and from different accounts. I'm trying to figure out how browser-solidity allows you to interact with addresses. Here's my contract so far:
contract HelloWorld { address public owner; mapping (address => uint) balances; function HelloWorld() { owner = msg.sender; balances[owner] = 1000; } function getBalance(address _user) returns(uint _balance) { return balances[_user]; } }
When I press "Create", I get the getBalances() field that asks me for address _user. When I put in the address that the creation of the contract outputted, 0xca35b7d915458ef540ade6068dfe2f44e8fa733c, I get an error: Error encoding arguments: SyntaxError: JSON.parse: expected ',' or ']' after array element at line 1 column 3 of the JSON data.
Here's a screenshot of what I see:
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub (https://github.com/ethereum/browser-solidity/issues/178), or mute the thread (https://github.com/notifications/unsubscribe-auth/AABkH4W4m1zvRd7bu-uYnHZD5o-xFEHCks5qhQCtgaJpZM4JoDpC).

Yup, I was just going to come back here and say that I figured that out. Is there a way to simulate multiple addresses?

You can select the sender address in the "arrow / paper plane" tab. We are working on adding UI elements to generate new addresses.

I only see two addresses in there anytime I start up an instance, though. If I switch it from the browser javascript VM to a local testrpc instance, then it shows me all the accounts I have.  But when I switch it from javascript VM to the local instance, the responses to my tests are encoded rather than decoded like they are in the javascript VM, so I've been working in the javasccript VM for right now. Glad to hear that soon there will be a button that allows you to generate multiple addresses. If no one has started working on it yet, let me know. I can probably write it and do a pull request some time in the next day or two.

@axic has started some work on that - I think there is even an open pull request about it.

Oh okay, cool. Is there a way that browser solidity can emulate sending eth to a contract? I know in the example above, I created a balance manually which is just an int. but can it simulate handling actual eth and moving it around?

Yes, that is what is happeninng in the "VM"  mode.


Add [[clang::annotate("idlgen::method")]] attr to distinguish between getter and method

Given header
class Foo : FooT<Foo>
{
  uint64_t Bar();
  uint64_t Baz();
}

idlgen would currently generate
runtimeclass Foo
{
  UInt64 Bar{get;};
  UInt64 Baz{get;};
}

There might be situation where Baz should be generated as a method instead. Since there is no way to distinguish between the two in C++, add idlgen::method attribute to so that idlgen would generate the following instead.

Given header
class Foo : FooT<Foo>
{
  uint64_t Bar();
  [[clang::annotate("idlgen::method")]]
  uint64_t Baz();
}

idlgen should generate
runtimeclass Foo
{
  UInt64 Bar{get;};
  UInt64 Baz();
}

After a heated and healthy discussion on discord, it's decided that idlgen would stick to winmd's convention of assuming everything is a method. Getter and setter would require attributes. This issue would be closed.


add visibility for group

make form group have a visible property
Revert "make form group have a visible property"
This reverts commit ab00934079e283382945dd549214c43f2f3c591a.

Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

Coverage remained the same at 89.979% when pulling 65650e9d34b3c7e4c5f113cd9e1f04248b6d6582 on pierreyvesm:master into 721a4eebbde77040a1318e60aa9ef21229bbcf99 on vue-generators:master.

Coverage remained the same at 89.979% when pulling 65650e9d34b3c7e4c5f113cd9e1f04248b6d6582 on pierreyvesm:master into 721a4eebbde77040a1318e60aa9ef21229bbcf99 on vue-generators:master.

Closing - This PR is doing way too many things.  Version bumps are not permitted in PR’s as well.
Why did you revert the one commit per the description?


installer: refactor

Motivation for this change
Borrow the harmless refactoring in https://github.com/NixOS/nixpkgs/pull/42610
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Hi! Thanks for the PR!
Could you write a small human-friendly overview of the borrowed refactor?
(At a glance, it looks like it de-duplicates files)

It adds kate to environment.systemPackages in installation-cd-graphical-kde.nix because that's an expected consistency to at least have a gui text editor.
We still default to using slim for a display manager, but it's disabled for installation-cd-graphical-gnome.nix because we default to gdm there. Prior to this it was enabling both gdm and slim which obviously didn't work.
There is a comment which I no longer know is true

GDM doesn't start in virtual machines with ISO

Verification is needed if this is still a problem (git blame says 3 years ago).
The rest is just de-duplication by adding installation-cd-graphical-base.nix for the shared configs between gnome and kde.

I had issues running gnome in qemu because it requires accelerated graphics. Maybe GDM is the same?

It could be so, though I've had both working regularly in qemu.
Though testing shouldn't be important because installation-cd-graphical-gnome.nix isn't used.

Am I missing something or 2430a13bcaf96a9516e9347a4b675bb712e863bf removed manual desktop icon from gnome installer? Why?

The previous discussion explains that it would be because Gnome doesn't have a desktop anymore. (I haven't verified.)

I see, still, the bottom of *-kde.nix looks pretty useful for all graphical installers, is it not?

I mean, konsole part isn't but the rest is. Like if we ever want to make an Xfce installer (which I would wholeheartedly vote for, as it is the most KISS of the big three DEs) or something, it would get those icons automagically.

@samueldr Yes GNOME removed this feature.
@oxij Maybe installation-cd-graphical-base.nix should have a mkDesktopItem (or something) in that case.


modify  preprocess

@didaladida It's obvious to me what this pull-request fixes, but it's better if you fill more info about that to make clear what the commit does.
The bug was fixed in my local repository a week ago, I forgot to push to github (sorry about that, I'll try to push bugfixes immediately in the future cases).


TUZ-145 Use ONNX node id in span in frontend

Using the node index as a stable identifier for ONNX layers is tricky because our flow may run ONNX checker on the model and that appears to modify the graph proto. Instead, most ONNX nodes are identified with a name that follows the format <op_name>_<id>, with <id> a seemingly unique integer. I don't actually know if this holds true across all models, unfortunately.
A more robust way to do this would be to create a string of ONNX node names called framework_op_src concatenated together with "\n" characters, stash that string as an attribute of the generated Relax module, and reference the Span line to the line in framework_op_src.
Just sharing this for ideas.
cc @jwfromm

@jwfromm @driazati can you have a look? I've changed this PR to use the NodeProto name field when it's not empty (it can be) and the index otherwise. In practice, the node name should be enough.


Critical security vulnerability in protobufjs 7.0.0

There is a security vulnerability disclosed in https://github.com/advisories/GHSA-h755-8qp9-cq85 which affects all versions above 7.0.0.
The issue was resolved in 7.2.4.
We are using the firebase admin package which depends on the firestore package.
Environment details

@google-cloud/firestore version: 6.7.0

Thanks for the PR. We will merge it. Is there any reason that updating your dependency tree didn't work, for example by using 'npm update' or 'yarn upgrade'? The previous version range ("protobufjs": "^7.0.0") should not have prevented you from getting the patched protobufjs v7.2.4.


Cannot load XLM from torch hub - cannot unpack non-iterable NoneType object

xlmr = torch.hub.load('pytorch/fairseq', 'xlmr.large')
I get the following error message -
TypeError                                 Traceback (most recent call last)
/tmp/ipykernel_11808/3675591151.py in <module>
----> 1 xlmr = torch.hub.load('pytorch/fairseq', 'xlmr.large', force_reload = True)

~/anaconda3/envs/btp/lib/python3.9/site-packages/torch/hub.py in load(repo_or_dir, model, source, force_reload, verbose, skip_validation, *args, **kwargs)
    397         repo_or_dir = _get_cache_or_reload(repo_or_dir, force_reload, verbose, skip_validation)
    398
--> 399     model = _load_local(repo_or_dir, model, *args, **kwargs)
    400     return model
    401

~/anaconda3/envs/btp/lib/python3.9/site-packages/torch/hub.py in _load_local(hubconf_dir, model, *args, **kwargs)
    423
    424     hubconf_path = os.path.join(hubconf_dir, MODULE_HUBCONF)
--> 425     hub_module = import_module(MODULE_HUBCONF, hubconf_path)
    426
    427     entry = _load_entry_from_hubconf(hub_module, model)

~/anaconda3/envs/btp/lib/python3.9/site-packages/torch/hub.py in import_module(name, path)
     74     module = importlib.util.module_from_spec(spec)
     75     assert isinstance(spec.loader, Loader)
---> 76     spec.loader.exec_module(module)
     77     return module
     78

~/anaconda3/envs/btp/lib/python3.9/importlib/_bootstrap_external.py in exec_module(self, module)

~/anaconda3/envs/btp/lib/python3.9/importlib/_bootstrap.py in _call_with_frames_removed(f, *args, **kwds)

~/.cache/torch/hub/pytorch_fairseq_main/hubconf.py in <module>
     37
     38 # only do fairseq imports after checking for dependencies
---> 39 from fairseq.hub_utils import (  # noqa; noqa
     40     BPEHubInterface as bpe,
     41     TokenizerHubInterface as tokenizer,

~/.cache/torch/hub/pytorch_fairseq_main/fairseq/__init__.py in <module>
     31 hydra_init()
     32
---> 33 import fairseq.criterions  # noqa
     34 import fairseq.distributed  # noqa
     35 import fairseq.models  # noqa

~/.cache/torch/hub/pytorch_fairseq_main/fairseq/criterions/__init__.py in <module>
     16
     17
---> 18 (
     19     build_criterion_,
     20     register_criterion,

TypeError: cannot unpack non-iterable NoneType object

I've seen this posted time and again, but none of the threads provide a solution.

You should install the suitable torch version for this command. I recommend installing torch==1.6.0 torchvision==0.7.0. It works for me. :)

I have the same problem. I tried to upgrade the torch and torchvision version to 1.6.0 and 0.7.0 respectively but it doesn't help

Did you try installing via pip install fairseq? I ran into the same issue when I tried to pip install the editable version. I had to uninstall it and reinstall with the aforementioned command.

pip installing fairseq changes the error to the following for me:
[/usr/lib/python3.8/distutils/dist.py](https://localhost:8080/#) in _parse_command_opts(self, parser, args)
    544         # to be sure that the basic "command" interface is implemented.
    545         if not issubclass(cmd_class, Command):
--> 546             raise DistutilsClassError(
    547                 "command class %s must subclass Command" % cmd_class)
    548

DistutilsClassError: command class <class 'torch.utils.cpp_extension.BuildExtension'> must subclass Command