We need a way to disable the bell

Environment
Windows build number: [run `[Version 10.0.19041.630]`
Windows Terminal version (if applicable): 1.5.3242.0

Any other software?
Multiple variants of Linux and BSD

Steps to reproduce
In a WSL terminal and at a command prompt, press tab or any direction key.
Expected behavior
Bell will sound
Actual behavior
Bell will sound
Request
Give us a mechanism in Terminal settings to disable the bell without having to silence the bell every where.  Perhaps a profile setting to disable sound in general for the specific profile or possible an option to disable CTRL-G

bellStyle is already a per-profile setting. So you can set it to "none" for your WSL distros and leave it "audible" for the rest

Awesome, thank you so much.  Not sure how I missed that.

For anyone else finding this issue: the option is now documented in https://docs.microsoft.com/en-us/windows/terminal/customize-settings/profile-advanced.

Out of interest does anybody actually enjoy the beep and is glad this feature was added?

I mean, there were at least 8 people who 👍'd #4046

so I'm guessing there are plenty of people who like it.

Well I don't; it's not a pleasant experience to hear this sound when wearing a headset :-S
Anyways, setting "bellStyle" to "none" doesn't work for me. Atleast not in PowerShell...

Could you share your whole settings.json?

I mean, there were at least 8 people who 👍'd #4046

so I'm guessing there are plenty of people who like it.

Thanks for pointing that out, I guess it takes all types to make the world go around, cheers!

Boy I can't get PowerShell to beep at all. I'm worried that they're doing something weird like calling [console]::beep() rather than emitting a BEL, which we wouldn't be able to stop, but since I can't even get powershell to beep outside of the Terminal I can't be more help 😕

is there a (possible) setting for visual bell (e.g. flickering the background) ?

for windterm portable:

We don't own "Windterm". This is not the appropriate place to file issues on "Windterm". :)

open powershell in wt，cilck Ctrl+R for history search, then click backspace, I heard a beep noise, which not emitting a BEL.

open powershell in wt，cilck Ctrl+R for history search, then click backspace, I heard a beep noise, which not emitting a BEL. It‘s caused by powershell.exe, nothing about wt.

Thank you!
I hate that bell

For anyone else finding this issue: the option is now documented in https://docs.microsoft.com/en-us/windows/terminal/customize-settings/profile-advanced, and can also be set the the GUI settings, but only per profile and not as a global setting.
It's at the bottom of this screenshot:

Version 1.16.10261.0 has a Defaults profile, which is gloabal seeting.


Require.js conflict [Bug]

Our software uses require.js, and it appears yours does as well.  Since the update, we have seen an unexpected error in the console which is due to multiple instances of require.js trying to run our code.
Sadly, I can't help you repro the problem or give too many proprietary details about our code.  Basically, we use a data-main attribute for our require.js script tag that runs a file to modify the require-base stuff.   See here for more about that: https://requirejs.org/docs/api.html#data-main
Now that's happening twice and the second time incorrectly since it's running it as a relative path, tacking that main js file to the end of the url.
So perhaps the solution is for us to change our software to have more specificity about which require.js to use.  But if you could contain the scope of your require.js a bit, as it was before (or is the addition of requirejs new?) that'd be ideal.  I don't think we'll change soon, so I might just have to find another CSS extension if you can't change it.
To repro, create a little local site using the data-main attribute and see if it conflicts.

@iamsolarplexus thanks for reporting. I was redundantly injecting the requirejs script without the stylebot editor being activated. I am hoping this will resolve the issue. I will let you know when the release is published on the chrome webstore so you can help me test this out.

I'm so glad it's an evident issue with a potential fix on the way.  Thanks for your responsiveness.  The recent changes to the UI look really good, btw.
I'll look forward to testing out the next release when you advise.

@iamsolarplexus this should now be resolved in the latest update.


Parallel collections no longer work since 0.8.1

For versions 0.8.1 and 0.8.2 parallel collections no longer work. Previously (0.8.0) we got
Loading...
Compiling LoadedPredef.sc
Welcome to the Ammonite Repl 0.8.0
(Scala 2.11.8 Java 1.8.0_66)
@ List(1,2,3).par.foreach(println)
2
1
3

@ Bye!

Now (0.8.1 and 0.8.2) the call
Loading...
Compiling LoadedPredef.sc
Welcome to the Ammonite Repl 0.8.1
(Scala 2.12.1 Java 1.8.0_66)
@ List(1,2,3).par.foreach(println)

never terminates. Attached you will find a stack trace of the hanging program version 0.8.1.
trace.txt

It's a regression in scala 2.12, see my comment at #556. here you can find the latest version for scala 2.11. it's should work fine.

Oh, thanks. I did not find that issue in my casual search. :)


Using XamarinMediaManager to Play local video

💬 Questions and Help

Is it possible to play video from a local folder of my project with XamarinMediaManager?
All the examples I've seen so far are with URL Web addresses as the source of the video.
Is there way that I can use a local path as my source to play a video save in my project as a Resource or Assembly?
What are the recommended instructions to achieve this with  on XamarinMedisManager for iOS and Android?

Thank You
For questions or help we recommend checking:

The Xamarin tag in Stack Overflow
The General slack channel in the Xamarin Slack
Ask your question in the Xamarin Forums

Use
File:///storage/...

And you must give:
Permisions of storage to app.

Thanks for your response Marcelo.
So all i have to do is add the video in my project and concatenate "File:///storage/" to the name of the file? like this?----> File:///storage/LowHeelSquat.mp4
I tried that and it did not work
Is there a special folder in which i have to put the video file?

Create a folder for the videos in the memory of the devices.
Copy a vídeo.
File:///storage/emulated/0/videos/video1.mp4

For the resources tomorrow i searching in my computer. I dont remember...

The readme already say it is available:
Task<IMediaItem> Play(FileInfo file);
Task<IMediaItem> Play(DirectoryInfo directoryInfo);
Task<IMediaItem> PlayFromAssembly(string resourceName, Assembly assembly = null);
Task<IMediaItem> PlayFromResource(string resourceName);

If you play from assembly you need to mark the media file as embedded resource in the editor.
When playing from assembly or resource, you only need to put in the name of the media, not the path.


Do we need a PairwiseAlignment object?

Currently we only have Alignment which represents a multiple sequence alignment. We also need to be able to represent multiple alignments to a single reference (#1014 ). This makes it unclear what alignment functions should return, as they could justifiably return a reference based alignment. What if we had these objects:

MultipleAlignment
ReferenceAlignment
PairwiseAlignment

where the PairwiseAlignment will be a default case for two sequences and can be converted to a MultipleAlignment or a ReferenceAlignment.

I think that sounds reasonable, but why not have the pairwise aligners just return a MutlipleAlignment containing two sequences (i.e., what does PairwiseAlignment do that MultipleAlignment wouldn't)?

I guess there wouldn't be a difference, and we could have a method which could create a ReferenceAlignment from two sequences in a MultipleAlignment. Though I think we would only ever be able to support a conversion for a single read and reference from a MultipleAlignment as any more would produce a ReferenceAlignment that wasn't independent (unless I am thinking about this wrong). I think that is where the PairwiseAlignment starts to make sense as the user never gets to ask the question of "why only 2?", but maybe that doesn't matter.

Closing in favor of #1288.


can't fetch RPI_5.15 Branch

I'm trying to make image for raspberry pi from branch "Langdale "
but i have this issue .
i want to switch to version 5.10 but i don't know which to files shall i change in .
can any one help please ?

update :
i tried fetching 5.10 and i got the same issue
i changed the content of 5.15.bb file to be like that
LINUX_VERSION ?= "5.10.110"
LINUX_RPI_BRANCH ?= "rpi-5.10.y"
LINUX_RPI_KMETA_BRANCH ?= "yocto-5.10"
SRCREV_machine = "427c6bd8835e197693e9b4aedbe45c2c3c84cdce"
SRCREV_meta = "3b1dc2f1fcd869f97901402759b859035984aa7f"
but still same issue

I tried many branches like dunfell // micklorde but got the same issue .
cloning the issue outside yocto got me this
git clone https://github.com/raspberrypi/linux.git
Cloning into 'linux'...
remote: Enumerating objects: 10939748, done.
remote: Counting objects: 100% (19413/19413), done.
remote: Compressing objects: 100% (5378/5378), done.
error: 2874 bytes of body are still expected1.70 GiB | 182.00 KiB/s
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output

this tells that the issue might be on how your build host is set to access internet. Maybe some firewalls are kicking in.

i managed to fetch the repo outside yocto using some git workaround .
now i copied the folder into the downloads folder of yocto but not sure about what exactly the name should be
can any one guide on what is the naming convention for he folder or where to find it ?
i tried
linux-raspberrypi-1_6.1.20.tar.gz
linux-raspberrypi-1_6.1.tar.gz
linux-raspberrypi-1_6.1.20
but still want to fetch

What was the git workaround?
Check the downloads directory for examples of fetched packages.

i will leave the solution here for everyone
1-increasing buffer
git config --global http.postBuffer 52428800
2-Turn off the compression
git config --global core.compression 0


Title Page is not to spec as per dissertation office review

As per an email that i received  from the dissertation office during draft review:

TITLE PAGE
-Please add a line space above A DISSERTATION
-Please add a line space above BY

Attaching a pull request that will fix this issue shortly.

I am surprised that people are using this template for years and no one noticed this issue. Thanks for pointing out and sending the PR.

Happened to me, I thought it was a one-off, but my roommate mentioned today he had the same issue with the office, so I decided to open the PR. Cheers.


Newest to oldest sorting inside History tab

Hey, thanks for the app!
I find current history tab isn't very practical - right now you have to scroll down the whole history in order to back to your latest search, and I think that's the purpose of the tab in most cases. It would be better from my angle to show the recent searches on the top and the oldest at the bottom.
Regards, Martin

Thank you very much for your input, I'm going to fix that now!

Hi Martin, please confirm that the current update also fixes this issue. Thanks!

Unfortunately order of the history is still the same - latest look ups aren't on the top of list
Also the auto dark mode from screenshots doesn't apply on my device

Thanks, I just tested the latest release and the problem seems to be solved!


[BUG] LLM Chat models do not work outside Flowise after 2nd prompt, unless it's OpenAI Chat Model

Describe the bug
LLM Chat models do not work outside Flowise after 2nd prompt, unless it's OpenAI Chat Model
Tried to use Other Chat Models like Anthropic, & Cohere.
They all worked inside Flowise though.
To Reproduce
Create a simple RAG app with a Conversation Retrieval QA Chain, Pinecone, OpeAI Embedding, Upstash Redis-backed Chat memory, and Chat Model [Anthropic, OpenAI, Cohere].
Run it inside Flowise. It works fine.
Embed it outside, you can chat with it one time only. But It won't respond the 2nd time you prompt it.
Expected behaviour
It won't respond the 2nd time you prompt it outside Flowise.

Not able to replicate this. Are you using the latest embed version? And what version of Flowise you are using currently. This might helps - https://docs.flowiseai.com/using-flowise/embed#using-specific-version


added new active icons to left nav plus nec. Csss

🚀 Deployed on https://670579c11b65e424a6ae66b2--cozy-fox-0defec.netlify.app

Can you not use css filters to change the color of the svg? https://stackoverflow.com/questions/22252472/how-can-i-change-the-color-of-an-svg-element
Shouldnt need another image


stopAllTasks() not working

In the example project, I press the top Stop button, but the downloads keep running.
I also commented
NotificationCenter.default.post(name:NSNotification.Name(rawValue: suspendNotificationName), object: ExampleCell.self)
but they still keep running. So it might be something in Digger, not in the example project.
I'm running iOS 11 Simulator.

Thank you for your issue,you are right.I judged that the download task was wrong.
            if diggerSeed.downloadTask.state == .running{
                diggerSeed.downloadTask.suspend()
                diggerDelegate?.notifySpeedZeroCallback(diggerSeed)
            }

I'll fix it in the next version
@alexandrutomescu


Add threshold variables for RDS alarms

Add additional configuration variables for AWS RDS alarms.
Related to: https://github.com/civiform/civiform/issues/5109

thought (non-blocking): I wonder if there are helpful consistency validations we could add for numeric config values such as min, max, or step (if the value needs to be a multiple of 8 or something like that). We currently have regex or enum based validations for strings: https://github.com/civiform/cloud-deploy-infra/blob/main/cloud/shared/validate_variable_definitions.py#L101-L130

Yes, I like that idea! Added to doc


Add appveyor button for README

Please assign to me

Assigned to @Twon - thanks Ant!

Appveyor CI button now added to the README.


x/mobile/cmd/gomobile: setup installation failed. when i run gomobile init it gives error in command line that gomobile: command not found

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
1.10
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/usrname/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/usrname/go"
GORACE=""
GOROOT="/usr/lib/go-1.10"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go-1.10/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build802535089=/tmp/go-build -gno-record-gcc-switch

Can you outline the steps you took to install gomobile? is $GOPATH/bin present in your $PATH?

HI all! I can't install gomobile in feodra 29
go get golang.org/x/mobile/cmd/gomobile
running this nothing to du
i have added path for go in bashrc file.
How i can fix that ?


Timeline scroll reset when going back from translation

Steps to Reproduce
On the timeline translate a post, get back from the Google translate view, the timeline will be scrolled to the top thus "loosing" the original translated post
Attachments
No response
What platform(s) does this occur on?
Android
Device Info
No response
What version of the app are you using?
Build version: <IP_ADDRESS>3; Bundle info: ee184d2cd (prod); Bundle date: 24111518; Platform: android
Additional Information
Need to use the back button to come back to the app from Google translate opened inside the app (perhaps loss of a state)

Related issue #6287 and Fix PR #6289


RuntimeError:map not found

Hi,
Thanks for your interest in our work. Have you downloaded CARLA using the link that we provided and followed the instructions to install both CARLA and SafeBench? We have included an extra map and corresponding Python client library in our CARLA simulator that you may find useful.

Hi,
Thanks for your interest in our work. Have you downloaded CARLA using the link that we provided and followed the instructions to install both CARLA and SafeBench? We have included an extra map and corresponding Python client library in our CARLA simulator that you may find useful.

Hello, I am excited to receive your reply.
I have installed CARLA according to the instructions_ 0.9.13 and SafeBench, when executing to "Desktop Users" in "Usage" according to instructions,

Carla successfully ran and obtained the following results

But when running SafeBench on another terminal, this error occurs:

I am a bit confused about how to use the additional map and Python client library in the CARLA simulator you mentioned. Can I have your guidance?

Did you download CARLA using the link we provided in the README? You can download our CARLA simulator using this link.

WARNING:cannot parse georeference: ''. Using default values.
Thank you very much for your guidance. The above issue 'RuntimeError: map not found' has been resolved. My mistake did indeed lie in not following the link on GitHub when downloading CARLA, which resulted in the error.
But now I have encountered a new problem:
“WARNING:cannot parse georeference: ''. Using default values.”
Warning while running Carla and unable to load screen：

Running safebench also has the same warnings and errors：

Can you give me some guidance?

It seems that Carla cannot successfully run on your side. Is your hardware compatible with running Carla?

I got the same error. My GPU is RTX 4070 and my Nvidia Driver Version is 535.104.05, is the problem of my Nvidia Driver Version?

Hi, I solved this issue by reinstalling the NVIDIA driver, and the driver version I used came from NVIDIA drivers that support Vulkan

WARNING:cannot parse georeference: ''. Using default values. Thank you very much for your guidance. The above issue 'RuntimeError: map not found' has been resolved. My mistake did indeed lie in not following the link on GitHub when downloading CARLA, which resulted in the error. But now I have encountered a new problem: “WARNING:cannot parse georeference: ''. Using default values.”
Warning while running Carla and unable to load screen：  Running safebench also has the same warnings and errors：   Can you give me some guidance?

I have meet the same issue, RuntimeError: map not found, how did you fix it?


Fully upgrade to 1.0

This branch should fix #204 for now, I gonna check other parts later on. Another concern is the enum integration(#162),  currently, it seems that it's on nobody's radar.

Thanks. I took a quick glance, 😐on the style changes (but that's fine). LGTM, so feel free to merge when it passes CI.

(haven't had a lot of time for this recently, so I really appreciate all the fixes -- you should have an invite for push access now)

hi @ihnorton I can only Squash and merge this PR instead of a common merge commit, but I guess those commits should be reserved since there are so many changes in this PR. Could you help to merge this?

Thanks! (Rebase and merge should have been available too, I think)


[cognitive-language] Update @azure/ai-language-text to ESM/vitest

Packages impacted by this PR

@azure/ai-language-text

Issues associated with this PR

https://github.com/Azure/azure-sdk-for-js/issues/31338

Describe the problem that is addressed by this PR
Migrates @azure/ai-language-text to ESM/vitest via automation.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.


Do you need 'doSelectionField'/'doSelectionChannel' to go with 'doSelection'?

In hvega I wanted to make a "context and detail" style plot where you could zoom in both the X and Y directions. Since the selection is projected across both channels, I couldn't just use doSelection on both axes (of the detail plot) as this just used the same range from the context plot for both axes. I ended up adding versions of doSelection which took either a field name or an encoding channel - e.g. something like doSelectionField : String -> String -> ScaleDomain and doSelectionChannel : String -> Channel -> ScaleDomain which create JSON objects {"selection": selName, "field": fieldName} or {"selection": selName, "encoding": channel}
Here is a not-very-informative example I used to check it worked (in this case I used my equivalents of both doSelectionField and doSelectionChannel just to check they worked; the VL documentation suggests only one is needed and the other could remain doSelection):
https://vega.github.io/editor/#/url/vega-lite/N4KABGBEAuBOCGA7AzgMwPawLaQFxgG1hJ5k8oBPSAGigGN4AbOgV0fmgFNzI71kAFABMOLLADpoAC07R4ASkgBfALrVwUEXPLFknAI4tOiOt3zFSPabPg0oyObGjkADLUgPOAB1fiAjO4O6D74AGziAEwAHEpK6hCQAG58JhzkBBoQoBA5UFjwsADWPIwAlojc8bn2nIycdNCl6Ig6mdWQAEawLMhSrdXt5aXO5pAAHukukbShapTpALRTUbTLKnFtA5DGfELlAOZk+ATjdpBUapvt0BReZlDlXLCJTJBXEEpXG1s76HuI+36AygE1GqFKtSEVhk2ncNzuPEMSEackaiUqUHgY1KRzAiDYjG+wPOOkg4MhPCocNu90gSMQKI4pXRZyxOPI+MYhK+bSJWSukHyRR4dFKsDodRoAt+-0B5neIKBwKg5MYUPwMBhtiqyo8DEloyE6Hy5VJqvVUGssJqdQaTRaGq6PT6sR1xPhtPpjLR3AVfPaVHlyoS5spUuD9n192IRpNDrAulq9UazR4Tt6ZxlBzDroVCQ9iJYyOGTJZfp5uU+EEuCQAJMg6DJ8jwpNBoF5kLgAPRd9H7eDifbDKQsDriJpdhtN+C9zj9hZlLi9gAs4gAVshUyAlEA

Thanks very much for this. I've added two functions doSelectionChannel and doSelectionField as you suggest.


Objection query promises do not handle errors

Describe the bug
We are seeing issues with client time outs. This is the same situation as closed issue #134. During high query activity searching for files, we see client time outs. The client's default time out is 100 seconds. Calls to the COMS service never returns in various cases. and because it never returns, nothing is logged in the COMS console of the pods. Tracking it down, the most likely situation would be unresolved promises. This lead me to look at where promises are being resolved. I am not very proficient JavaScript, so I may not correct.
The problem definitely occurs when the system is under load. For example, when we are getting about 20-30 requests/second to COMS, we start to get time outs,

In the various services that query the database, the then handler does not provide a errorHandler parameter. By not handling the errors, the service could return SQL and other information about the application. See Error handling in the Objection documenation.
Additionally it seems, the searchObjects controller function does not map the error using errorToProblem like other methods.
Version Number

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Screenshots

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context

We see the COMS pod reports unhealthy during this time...

Hey Phil.
I'm looking into these timeouts this week.
I suspect it may be a combination of sql queries and the way we handle unresolved javascript promises.
Are you able to let me know the resource allocation to your Patroni cluster (eg: cpu and memory, number of pods), or if you use a single postgres pod?
Is it mainly the searchObjects api call that gives timeouts under high load?
Thanks

Closing this issue as the error conditions described are not repeatable. That being said, we did do an internal performance review pass and added a few indexes to the permission tables to improve lookup speed in #162 . Should a similar issue appear again in the upcoming COMS v0.4.1 release, please feel free to request this issue to be reopened or to file a new issue.


Better consumer offset handling

Add Client.GetOffsetRange to get the available range of offsets for a partition in one request. I had to make some changes to OffsetRequest and OffsetResponse to make it possible to ask for more than one offset per partition, but no changes to the public API were necessary.

When calling ConsumePartition, always check whether the offset is within the offset range. This means we now have to do an OffsetRequest for every ConsumePartition call, even if the offset is provided. The good news is that the method will immediately return an error and never start a goroutine, instead of starting the goroutine and returning an error in the Errors() channel which you can easily ignore.

@Shopify/kafka

make it possible to ask for more than one offset per partition

Is that even possible? It's never explicitly stated, but I'd always assumed based on the layout of the protocol that it wasn't really supported to include multiple blocks for a single partition.

Apparently it works in Kafka 0.8.1 and 0.8.2. The OffsetRequest documentation is especially unclear, but this led me to believe that is was supported:

The response contains the starting offset of each segment for the requested partition as well as the "log end offset" i.e. the offset of the next message that would be appended to the given partition.

You can even do more than two, as long as you request the timestamps in descending order.

WTF :/ Github marked this as merged after I rebased.

Closing in favor of #418


SFC compiler produces bloated sourcemaps

Version
3.0.0
Reproduction link
https://github.com/vitejs/vite/tree/master/playground
Steps to reproduce

Build any Vue application with an SFC
Inspect the sourcemap output

What is expected?
Sourcemap should contain minimal number of mappings
What is actually happening?
Sourcemap contains separate mapping for every single non-whitespace character

This behavior was introduced with commit 698c8d3. I'm unsure if there was some kind of rationale behind this change (I am not super familiar with sourcemaps, so please explain if I'm missing something), but I have been trying to debug some issues I was having with sourcemaps in a plugin I am writing for Vite, and I noticed that the mappings for Vue 3 SFC files are massive. For the Vite playground application (here), the "mappings" field in the sourcemap for the main App.vue is over 10kB. When I load up the sourcemap in this visualizer, you can see how each character has its own separate mapping entry.
https://i.imgur.com/ulKE756.png
When I apply this change to only apply 1 mapping per line, the "mappings" field goes down to ~300 bytes, and the visualization looks like this:
https://i.imgur.com/CfZZtgF.png
I'm opening this as an issue because it seems as though this change was introduced intentionally, but I don't understand what the purpose of it would be - so I was hoping to get an explanation. I can open a pull request if my change is the desired behavior.

I've found some references here and here to "high resolution" source maps that map each individual character to ensure completely accurate column numbers for errors, so it seems like that is what this change was meant to implement. Closing this since it sounds like this is somewhat standard practice.


tests: Fix race condition

@brauner if you happen to be around, this is ready to merge :)

Of course :)


OLM doesn't create roles corresponding to the permissions defined in the CSV file

Bug Report

What did you do?
We are trying to install IBM IAM Operator(https://github.com/IBM/ibm-iam-operator) from this catalogSource defintion:
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: opencloud-operators
  namespace: openshift-marketplace
spec:
  displayName: IBMCS Operators
  publisher: IBM
  sourceType: grpc
  image: quay.io/opencloudio/ibm-common-service-catalog:dev-latest
  updateStrategy:
    registryPoll:
      interval: 45m

The following permissions are defined in our CSV https://github.com/IBM/ibm-iam-operator/blob/master/deploy/olm-catalog/ibm-iam-operator/3.6.4/ibm-iam-operator.v3.6.4.clusterserviceversion.yaml#L1592-L1953 .
What did you expect to see?
We expect to see three different roles to be created and associated with three different serviceAccounts as it is evident from the lines highlighted in the CSV file.
What did you see instead? Under which circumstances?
All the three roles and rolebindings to associate them to the serviceAccounts were created successfully prior to Openshift Container Platform 4.4.6 and everything worked as expected. However, we have found that on Openshift Container Platform 4.4.11 and 4.5.0-rc6, all the three roles and rolebindings to the serviceaccounts have NOT been created(only one role and rolebinding is created) and the following errors are seen:
oc describe csv ibm-iam-operator | grep NotSatisfied -B 5
      Status:   Satisfied
      Version:  v1
      Group:    rbac.authorization.k8s.io
      Kind:     PolicyRule
      Message:  namespaced rule:{"verbs":["get","create"],"apiGroups":["monitoring.coreos.com"],"resources":["servicemonitors"]}
      Status:   NotSatisfied
--
      Version:  v1
      Group:    rbac.authorization.k8s.io
      Kind:     PolicyRule
      Message:  namespaced rule:{"verbs":["update"],"apiGroups":["apps"],"resources":["deployments/finalizers"],"resourceNames":["ibm-iam-operator"]}
      Status:   NotSatisfied
--
      Status:   Satisfied
      Version:  v1
      Group:    rbac.authorization.k8s.io
      Kind:     PolicyRule
      Message:  namespaced rule:{"verbs":["create","delete","get","list","patch","update","watch"],"apiGroups":["operator.ibm.com"],"resources":["*","policydecisions","oidcclientwatchers","authentications","policycontrollers","paps","securityonboardings"]}
      Status:   NotSatisfied
--
      Version:  v1
      Group:    rbac.authorization.k8s.io
      Kind:     PolicyRule
      Message:  namespaced rule:{"verbs":["create","delete","get","list","patch","update","watch"],"apiGroups":["certmanager.k8s.io"],"resources":["*","certificates"]}
      Status:   NotSatisfied
--
      Version:  v1
      Group:    rbac.authorization.k8s.io
      Kind:     PolicyRule
      Message:  namespaced rule:{"verbs":["create","delete","get","list","patch","update","watch"],"apiGroups":["networking.k8s.io"],"resources":["*","ingresses"]}
      Status:   NotSatisfied
--
      Version:  v1
      Group:    rbac.authorization.k8s.io
      Kind:     PolicyRule
      Message:  namespaced rule:{"verbs":["create","delete","get","list","patch","update","watch"],"apiGroups":["batch"],"resources":["jobs"]}
      Status:   NotSatisfied
--
      Version:  v1
    Group:
    Kind:       ServiceAccount
    Message:    Policy rule not satisfied for service account
    Name:       ibm-iam-operand-restricted
    Status:     PresentNotSatisfied

Environment

operator-lifecycle-manager version:
OLM version: 0.15.1
git commit: 922f6adf41c7ae7bb9c9a63fdd021cf2cd4dcf2c

Kubernetes version information:

Kubernetes Version: v1.18.3+6025c28

Kubernetes cluster kind:

Possible Solution

Additional context
Add any other context about the problem here.

btw: there is a BugZilla for this issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1855088

@posriniv Hi!
I sent a PR which addresses problem of missing (Cluster)RoleBindings.
Is it important for your use case to have 3 distinct Roles created?

@matskiv Yes, it is important for us.


Do not convert method to a string if logging is disabled

We need a proper logging infrastructure as a long term fix, but this shaves off 8% of the compilation time for Hello World, so worth it on it's own...

LGTM otherwise


chore: fix cache paths for backcompat tests

Fixes #2510

/easycla

This is blocking release please review @open-telemetry/javascript-approvers


Curl command example

It would be helpful to have a curl command example here for the image url endpoint

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

ID: 021ecbd2-8976-64a4-ca95-0009a1c02692
Version Independent ID: 47011e64-0198-6fac-cd07-0334f350f59c
Content
Content Source
Service: cognitive-services

@stephlocke - Thank you for the suggestion/feedback. The folks listed in the article as the content owners don't work here now, so I am going to have to track down the current product owner.

Here is one I wrote yesterday
curl -H 'Prediction-Key: 634e5ccc37c04515a5' -H "C
ontent-type: application/json" -d '{"Url": "https://github.com/stephlocke/lazyCDN/blob/ma
ster/leia-inquisitive.jpg?raw=true"}' https://southcentralus.api.cognitive.microsoft.com/
customvision/v1.1/Prediction/7f571dd8-a1d7-4be9-8fd8-e1d03/url?iterationId=79e1fe1
5-6c7e-4132-a7f1-3c97506

* keys and guids truncated

@stephlocke Thank you for that!! @Blackmist Larry is there someone who can take a look at this one?

@JennieHubbard @stephlocke Tracking down the current owner of this document now.

Apologies for the delay on this @stephlocke .
@MicrosoftDocs/azure-cxp-triage can you please assign to @anrothMSFT ? The author fields in the document have already been updated.

Thank you. So we have example curl commands and other snippets on the API reference page. But I see that this is not clearly linked to from this documentation. I am going to update this page to clear link to the reference page in the intro.

#please-close

@stephlocke We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


fixing hardcoded loop

Proposed changes
Replaces hardcoded loop [0:2] with loop that is not affected by size of polygon file in multipolygon notebook [:] - This notebook is coming up on reviewNB as if the whole notebook has changed; I think this is because we've changed datacube versions in between

Looks good @BexDunn.  You can simplify the loop further by changing:
for index, row in gdf.iloc[:].iterrows():
to
for index, row in gdf.iterrows():

sorry @CBUR . meant thanks @cbur24

Hi there – you’ve got the wrong Chris Burgess  From: cbur24Sent: Wednesday, 13 May 2020 11:12 AMTo: GeoscienceAustralia/dea-notebooksCc: Chris Burgess; MentionSubject: Re: [GeoscienceAustralia/dea-notebooks] fixing hardcoded loop (#571) @cbur24 approved this pull request.—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.


Pdf documentation link is broken

The pdf documentation link does not open the pdf.

@jagatsingh Please provide a link to the page which isn't generating PDF documentation. This request isn't specific enough.

The download pdf link at bottom left of Azure Cli documentation.
https://docs.microsoft.com/en-us/cli/azure/opbuildpdf/azure-cli-latest/TOC.pdf?view=azure-cli-latest&branch=live
On Tue, 18 Sep 2018, 3:29 am Stephen Tramer<EMAIL_ADDRESS>wrote:

@jagatsingh https://github.com/jagatsingh Please provide a link to the
page which isn't generating PDF documentation. This request isn't specific
enough.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-docs-cli-python/issues/1030#issuecomment-422102192,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABNjXDwp0mrN9yCBpnCpedALTqyipb6Mks5ub9vhgaJpZM4WqqQf
.


Add review immunity details table

This will allow us to keep an audit log of what goes on with immunity details, i.e. multiple back and forths between assessor and reviewer

Superseded by https://github.com/unboxed/bops/pull/1042


Fixed import path for WritableNestedSerializer

This PR restores compatibility with NetBox 3.3.0
fixes #220

Thanks.


Go v1.4.1

It looks like you started with an old branch where the Go version was 1.3.2—can you please pull the latest changes with git and then redo this PR? The current version of Go that we have is 1.4.


Simpifying docker contrib

Removing docker-build.sh step and building superset container with docker-compose (build command)
Removing exposed ports for psql and redis.
Adding new SUPERSET_ENV development that also runs npm watcher
Removing npm and superset runserver/worker from docker-init. Dockerfile already builds assets and  starts superset.

Codecov Report

Merging #5802 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #5802   +/-   ##
=======================================
  Coverage   63.82%   63.82%
=======================================
  Files         364      364
  Lines       23099    23099
  Branches     2587     2587
=======================================
  Hits        14744    14744
  Misses       8340     8340
  Partials       15       15

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 d43813f...2b742ee. Read the comment docs.

Would it be worth adding some explicit instructions in the doc of how to run this locally using docker? Since it's not just docker-compose up

@ivansabik I thought that it already exists?
https://github.com/apache/incubator-superset/blob/master/docs/installation.rst#user-content-start-with-docker
Oh course if this PR gets merged that documentation has to changed a little.

@kakoni mind adjusting the docs as you mentionned as part of this PR?

@mistercrunch I thought I already did?;) https://github.com/apache/incubator-superset/pull/5802/commits/2f67a04679de80fe2aead114ac06f78169f71485

@kakoni this is potentially superseded by this PR: #5966.
Could you take a look and see if it does indeed? I am sorry I didn't see your PR before. Anyway mine goes farther but seems to tackle what you did.

@victornoel Hi! We seem to have same goals, so we should combine our work.
Anyway question; Build processes/docker images for develoment / production would look bit different (for instance running editable pip install, npm/webpack dev server running for assets). So perhaps, would it make sense to create two compose files(one for dev and one for prod like builds) ?

@kakoni from what I understood, nobody uses this image for production, most people are using https://hub.docker.com/r/amancevice/superset/, so for now, I wouldn't bother tackling this question.
In #5966, the objective is clearly to simplify the experience of the developer, both for the backend and the frontend.
Some things that differs in your PR:

your build the frontend in the entrypoint.sh. My take was to build it once in the image, and if the desire was to do development, the dev would run dev-server on its host, not in docker (that's not needed to do it in docker since running dev-server is happening all in memory). That being said, it means that if the frontend code change but the dev does not want to run dev-server, then he has to rebuild the image… that's maybe not the best, we could include building the front as part of starting the image.
yours build the image directly from docker-compose while mine lets the dev build it himself. I think you solution is more elegant.

WDYT? Would you agree that I incorporate those changes in my PR and that we continue with it? Since it covers more things too.

Also, is there an official docker image published on DockerHub? That would be helpful, so I can ask our DevOps architect how to set up a Superset instance in our AWS infrastructure.

@brylie you should open another issue for this, I don't think this is the best place to discuss it, @kakoni and I have no official position in the superset org :)
You can check out https://hub.docker.com/r/amancevice/superset/ also.

@victornoel

Would you agree that I incorporate those changes in my PR and that we continue with it? Since it covers more things too.

Makes sense. Lets continue there.


Design: button updates + guidance

Decisions have been made regarding buttons:

Adding supertask button
removing small buttons
changing disabled state from grey to 50% opacity

To do:

[x] Update buttons in EN library
[x] Update buttons in FR library
[ ] Update EN poster
[ ] Update FR poster
[x] Update EN guidance
[ ] Update FR guidance
[x] Update component archive Figma file

Presented in sprint review Nov 14th, Poster cant be updated until review is finalized . Will be next step

@RavinaSamaroo , can you add the links of the work you presented yesterday ? Thank you

Do we need another card to capture the content/translation and then another for the publishing?

@SmartMouthWords yes, and we need a card for the development changes as well (I'll check and see if one already exists)


Move upcast and local size check into apply_opt

also not allowing upcast == 256 which fixed a linearizer test case

local size < 256 is definitely too small

so we don't have all handcode opt result in search space yet due to the upcast and local size check. this is deeper than i initially thought


Remove request promise for request-light (#10346)

remove request promise for request-light

make sure data is a string not a json

add configure call

remove unused reference

more fixes

Move configure calls

clean up

fix name

move test deps as dev

Co-authored-by: chgagnon<EMAIL_ADDRESS>
This PR fixes #

Coverage decreased (-0.06%) to 33.674% when pulling 99de7f51ad2fd6cdfae4f3d9a575e7bc00884a85 on port/10346 into f6e7b569465f23a9fd680c411b05d80ff0acf303 on release/1.18.

@anthonydresser could you please ask @kenvanhyning to approve porting this to the release branch?

fixes #10367

@kburtram made a linked issue.

Merging due to issue being approved


[WIP] Add optional enable init param to Motor, close #366

An updated version of #367 - need to add tests and docs

Codecov Report

Merging #677 into master will increase coverage by 0.16%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #677      +/-   ##
==========================================
+ Coverage   85.41%   85.57%   +0.16%
==========================================
  Files          36       36
  Lines        7307     7385      +78
==========================================
+ Hits         6241     6320      +79
+ Misses       1066     1065       -1

Impacted Files
Coverage Δ

gpiozero/output_devices.py
98.36% <100%> (+0.01%)
:arrow_up:

tests/test_boards.py
99.57% <100%> (ø)
:arrow_up:

tests/test_outputs.py
100% <100%> (ø)
:arrow_up:

gpiozero/devices.py
86.72% <0%> (+0.44%)
: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 2916a0f...0dc72da. Read the comment docs.


feat(miranum-stack-showcase): add showcase

Description
Add a showcase that demonstrates how to use the Miranum-Tools all together.
Checklist

[x] Code is easy to understand
[x] No obvious errors or bugs
[x] CI/CD Pipelines did run successfully
[x] Tests were implemented
[x] Documentation was created

Wow, that looks super cool! 💯 🚀
A couple of conceptual thoughts:

We should port the readme's to our documentation. (happy to take care of this)
Since it is a showcase in our Consulting Repository I would also point out an "easy" way to start the platform in less time than described in the eight steps. Ideally I imagine something like a stack folder containing a docker compose and build file which pulls / builds and provisions all necessary services to jump right into the Miranum-Stack. In such a scenario everything would be containerised.

I am curious to hear your opinion on this thought!

Thank you!

I can do that. The place for this would be under miranum.io > Guides > Showcases, right?
Yes, you're right, I hadn't thought of that.

I can do that. The place for this would be under miranum.io > Guides > Showcases, right?

Yes! That's correct! 👍

Hey @peterhnm, can you check if starting the docker-compose after having build the project works for you now?
It does the trick for me! 🤩


Please check if 'Famsv6VM' should be 'Famsv6' instead

Hello,
please check if 'Famsv6VM' should be 'Famsv6' instead in this sentence: The new Falsv6, Fasv6, and Famsv6VM series virtual machines public preview now available.
The article speaks about Fasv6, Falsv6 and Famsv6 series.
Kind regards,
Anne H., QC

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

ID: 782aa167-dd84-4469-3f7d-7072591588fa
Version Independent ID: 07832b4a-465f-ad3d-610f-e7ef2973aa46
Content: Fasv6, Falsv6 and Famsv6-series - Azure Virtual Machines
Content Source: articles/virtual-machines/fasv6-falsv6-series.md
Service: virtual-machines
Sub-service: sizes
GitHub Login: @iamwilliew
Microsoft Alias: wwilliams

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


Presenting multiple children from a feature

Description
There is a bug in the modal presentation behavior when replacing child views. Specifically:

When a modal is presented.
The modal displays a first child.
An attempt is made to replace the first child with a second child.

The replacement operation is not working as expected. The behavior is inconsistent and incorrect, resulting in improper display or failure to update the modal's content.
Note: this is a UIKit project.
Checklist

[ ] I have determined whether this bug is also reproducible in a vanilla SwiftUI project.
[X] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior
The first child should be dismissed, and the second child should be presented.
https://github.com/user-attachments/assets/628b4602-b905-448d-a0ae-65c0ccfd0f5a
Actual behavior
Sometimes (randomly), the parent modal is dismissed when trying to present the second child.
https://github.com/user-attachments/assets/07c0547f-dd8b-40ec-a06e-0121121af3f0
Steps to reproduce

Present Parent as a modal.
Present the First Child as a modal from the Parent.
Tap a button on the First Child; the Parent should be able to receive this action from the delegate and replace the destination with a Second Child.

Sample project: https://github.com/ysmaliak/tca-navigation-test
The Composable Architecture version information
1.14.0
Destination operating system
iOS 17.5
Xcode version information
15.4
Swift Compiler version information
swift-driver version: <IP_ADDRESS> Apple Swift version 5.10 (swiftlang-<IP_ADDRESS> clang-15<IP_ADDRESS>)
Target: arm64-apple-macosx14.0

Hi @ysmaliak, this is not a bug with the library, but rather just how UIKit (and even SwiftUI) work. You cannot simultaneously dismiss and present controllers, and you can't even simultaneously present two sheets at once. There is even some logs in the console of your app letting you know this wrong:

Attempt to present <tca_navigation_test.SecondChildViewController: 0x13af15120> on <tca_navigation_test.ParentViewController: 0x13ad0a270> (from <tca_navigation_test.ParentViewController: 0x13ad0a270>) whose view is not in the window hierarchy.

The fix is to space out the destination mutations. You can first nil out the destination, wait a small amount of time, and then mutate the destination to the next screen.
However, I also tested this code in iOS 18.1 and things seem to work as intended. So perhaps UIKit has fixed some bugs. I'm not sure it will always work, but at least this simple use case seems to work as expected.
Since this isn't an issue with the library I am going to convert it to a discussion. Please feel free to continue the conversation over there!


change name

#75  👈
main

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

Join @AmineAfia and the rest of your teammates on  Graphite


update max length for environment name to 32 (40 - 8)

Elastic beanstalk lengthened the name a while back to 40 from 23 a while back.

@throttleup @reydi apologies for the major delay in reviewing this. This looks fine. Merging.


Scala deprecation updates

Addressing deprecation warnings for akka-http and http4s:

akka-http: Route.asyncHandler -> Route.toFunction
akka-http: StatusCode.RequestEntityTooLarge -> PayloadTooLarge
akka-http: Remove ActorMaterializer.apply()
http4s: decodeString -> decodeText

Contributing to Twilio

All third-party contributors acknowledge that any contributions they provide will be made under the same open-source license that the open-source project is provided under.

[x] I acknowledge that all my contributions will be made under the project's license.

Codecov Report

Merging #778 into master will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master     #778   +/-   ##
=======================================
  Coverage   82.72%   82.72%
=======================================
  Files          73       73
  Lines        5378     5378
  Branches      140      140
=======================================
  Hits         4449     4449
  Misses        929      929

Impacted Files
Coverage Δ

...guardrail/generators/Scala/AkkaHttpGenerator.scala
28.39% <0.00%> (ø)

...ail/generators/Scala/AkkaHttpServerGenerator.scala
93.07% <ø> (ø)

...ilio/guardrail/generators/Scala/Http4sHelper.scala
100.00% <ø> (ø)

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 ad84229...0151ba0. Read the comment docs.

Will this narrow the version range of akka-http that we support?

Yeah:

akka-http 10.0.11 is the first release that uses PayloadTooLarge
akka-http 10.2.0 is the first release that exposes Route.toFunction
akka 2.6.0 is the first release that uses the global ActorMaterializer
http4s 0.21.5 is the first release with decodeText

I guess this PR really should just be a draft, but the http4s upgrade is actually nontrivial as it resolves "[the decoder] may loop infinitely for charsets other than UTF-8."

Circling back on this, I'm a bit worried about the akka 2.6 requirement, as I know there are things that are still using akka 2.5.
The PayloadTooLarge bit should be ok because only specs that use that status code should hit this, and those specs would already not work, right?
Maybe can split the http4s change into a separate PR that can get merged on its own?

These changes apparently have gradually made it in anyway, so closing this.


Change draggable-points.js to ONLY support inverted columnranges

I have change the script to ONLY support inverted columnrange charts, and add snapping of data points.
Unfortunately I am not a JS developer so have been unable to generalise this script to automatically detect the graph type and adjust logic accordingly, so it would be good if my changes could be merged with the existing logic to work for all graphs.

This PR is now out of date


Replace interface generation and upgrade monaco

This is definitely not yet ready, but I wanted to share the current state.

@ctron Thanks so much for this effort to update monaco. Have you been able to make more progress on this? 🙂

@ctron Thanks so much for this effort to update monaco. Have you been able to make more progress on this? 🙂

Sorry, no.


DE-1399 | Export chart data option

:tada: This PR is included in version 1.2.0-develop.19 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[Feature Request] "Year and Month" date picker

Right now you can pick a year (2018), pick just a month (Jan), or pick a full date (2018-01-01). I'd like to be able to pick a date at the month-level (2018-01). So you'd pick the year, pick the month, and then the datepicker would close and the date would return.
Would love your thoughts on how to best make this change (for example, should i modify MonthPicker or DatePicker?). Happy to submit a PR.

What if we just add some prop to  DateInput that will force it to return value after selecting just year and month? look at this method https://github.com/arfedulov/semantic-ui-calendar-react/blob/37bffcd574d428d3de7f901bf9a1d97c1a26ba42/src/inputs/DateInput.tsx#L332

Sounds great. Will submit PR.

We ended up working around the issue, so no longer need this feature. Closing the issue for now.

Hey @MarkAZhang how did you solve the issue?

Hey @MarkAZhang how did you solve the issue?


Update source-build with the razor-compiler/razor refactoring

In .NET 8.0 the razor-compiler repo was merged with razor-tooling into the razor repo.  Source-build needs to respond to this.  Mainly the razor-compiler needs to be removed and the razor repo needs to be built instead.  The razor repo is already included in the vmr.

@chsienki - I made an attempt to start building razor in source-build but I noticed it has an npm dependency.  Can you help the source-build team on this?  What is the NPM dependency for?  Is this new in .net 8 and needed for source-build scenarios or is this a side effect of the repo consolidation where we are possibly building more that what is necessary for source-build?
  [SourceBuiltSdkResolver] Looking for SDK Yarn.MSBuild. Detected config(s) in env: 'ARCADE' for 'Microsoft.DotNet.Arcade.Sdk/8.0.0-beta.22605.1' at '/repos/dotnet/Tools/source-built/Microsoft.DotNet.Arcade.Sdk/'
    /tmp/MSBuildTemproot/tmpc86986f068294c2f99c8c6575d0218bc.exec.cmd: line 2: node: command not found
  /repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets(36,5): error MSB3073: The command "node -v" exited with code 127. [/repos/dotnet/src/razor/artifacts/source-build/self/src/src/Razor/src/Microsoft.AspNetCore.Razor.VSCode.BlazorWasmDebuggingExtension/Microsoft.AspNetCore.Razor.VSCode.BlazorWasmDebuggingExtension.npmproj]
  ##vso[task.logissue type=error;sourcepath=/repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets;linenumber=36;columnnumber=5;code=MSB3073;](NETCORE_ENGINEERING_TELEMETRY=Restore) The command "node -v" exited with code 127.
  /repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets(40,5): error : Building *.npmproj but NodeJS was not detected on path. Ensure NodeJS is on path or disable building NodeJS projects with /p:BuildNodeJs=false. Skipping NodeJS projects will also skip managed projects depending on them, including Components, Mvc and Analysers. [/repos/dotnet/src/razor/artifacts/source-build/self/src/src/Razor/src/Microsoft.AspNetCore.Razor.VSCode.BlazorWasmDebuggingExtension/Microsoft.AspNetCore.Razor.VSCode.BlazorWasmDebuggingExtension.npmproj]
  ##vso[task.logissue type=error;sourcepath=/repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets;linenumber=40;columnnumber=5;code=;](NETCORE_ENGINEERING_TELEMETRY=Restore) Building *.npmproj but NodeJS was not detected on path. Ensure NodeJS is on path or disable building NodeJS projects with /p:BuildNodeJs=false. Skipping NodeJS projects will also skip managed projects depending on them, including Components, Mvc and Analysers.
    /tmp/MSBuildTemproot/tmp5285dd6a4dd84680b47dd110e6b4ed4b.exec.cmd: line 2: node: command not found
    /tmp/MSBuildTemproot/tmpf3d5269359ea45eea10b40b0024f82a0.exec.cmd: line 2: node: command not found
  /repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets(36,5): error MSB3073: The command "node -v" exited with code 127. [/repos/dotnet/src/razor/artifacts/source-build/self/src/src/Razor/test/Microsoft.AspNetCore.Razor.VSCode.Grammar.Test/Microsoft.AspNetCore.Razor.VSCode.Grammar.Test.npmproj]
  ##vso[task.logissue type=error;sourcepath=/repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets;linenumber=36;columnnumber=5;code=MSB3073;](NETCORE_ENGINEERING_TELEMETRY=Restore) The command "node -v" exited with code 127.
  /repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets(36,5): error MSB3073: The command "node -v" exited with code 127. [/repos/dotnet/src/razor/artifacts/source-build/self/src/src/Razor/test/Microsoft.AspNetCore.Razor.VSCode.Grammar.Test/Microsoft.AspNetCore.Razor.VSCode.Grammar.Test.npmproj]
  ##vso[task.logissue type=error;sourcepath=/repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets;linenumber=36;columnnumber=5;code=MSB3073;](NETCORE_ENGINEERING_TELEMETRY=Restore) The command "node -v" exited with code 127.
    /tmp/MSBuildTemproot/tmp1139ed979a7e46858d067bb85b0664f0.exec.cmd: line 2: node: command not found
  /repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets(36,5): error MSB3073: The command "node -v" exited with code 127. [/repos/dotnet/src/razor/artifacts/source-build/self/src/src/Razor/test/Microsoft.AspNetCore.Razor.VSCode.Test/Microsoft.AspNetCore.Razor.VSCode.Test.npmproj]
  ##vso[task.logissue type=error;sourcepath=/repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets;linenumber=36;columnnumber=5;code=MSB3073;](NETCORE_ENGINEERING_TELEMETRY=Restore) The command "node -v" exited with code 127.
  /repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets(36,5): error MSB3073: The command "node -v" exited with code 127. [/repos/dotnet/src/razor/artifacts/source-build/self/src/src/Razor/test/Microsoft.AspNetCore.Razor.VSCode.Test/Microsoft.AspNetCore.Razor.VSCode.Test.npmproj]
  ##vso[task.logissue type=error;sourcepath=/repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets;linenumber=36;columnnumber=5;code=MSB3073;](NETCORE_ENGINEERING_TELEMETRY=Restore) The command "node -v" exited with code 127.
  /repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets(40,5): error : Building *.npmproj but NodeJS was not detected on path. Ensure NodeJS is on path or disable building NodeJS projects with /p:BuildNodeJs=false. Skipping NodeJS projects will also skip managed projects depending on them, including Components, Mvc and Analysers. [/repos/dotnet/src/razor/artifacts/source-build/self/src/src/Razor/test/Microsoft.AspNetCore.Razor.VSCode.Grammar.Test/Microsoft.AspNetCore.Razor.VSCode.Grammar.Test.npmproj]
  ##vso[task.logissue type=error;sourcepath=/repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets;linenumber=40;columnnumber=5;code=;](NETCORE_ENGINEERING_TELEMETRY=Restore) Building *.npmproj but NodeJS was not detected on path. Ensure NodeJS is on path or disable building NodeJS projects with /p:BuildNodeJs=false. Skipping NodeJS projects will also skip managed projects depending on them, including Components, Mvc and Analysers.
  /repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets(40,5): error : Building *.npmproj but NodeJS was not detected on path. Ensure NodeJS is on path or disable building NodeJS projects with /p:BuildNodeJs=false. Skipping NodeJS projects will also skip managed projects depending on them, including Components, Mvc and Analysers. [/repos/dotnet/src/razor/artifacts/source-build/self/src/src/Razor/test/Microsoft.AspNetCore.Razor.VSCode.Test/Microsoft.AspNetCore.Razor.VSCode.Test.npmproj]
  ##vso[task.logissue type=error;sourcepath=/repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets;linenumber=40;columnnumber=5;code=;](NETCORE_ENGINEERING_TELEMETRY=Restore) Building *.npmproj but NodeJS was not detected on path. Ensure NodeJS is on path or disable building NodeJS projects with /p:BuildNodeJs=false. Skipping NodeJS projects will also skip managed projects depending on them, including Components, Mvc and Analysers.
  /repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets(36,5): error MSB3073: The command "node -v" exited with code 127. [/repos/dotnet/src/razor/artifacts/source-build/self/src/src/Razor/test/VSCode.FunctionalTest/Microsoft.AspNetCore.Razor.VSCode.FunctionalTest.npmproj]
  ##vso[task.logissue type=error;sourcepath=/repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets;linenumber=36;columnnumber=5;code=MSB3073;](NETCORE_ENGINEERING_TELEMETRY=Restore) The command "node -v" exited with code 127.
  /repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets(36,5): error MSB3073: The command "node -v" exited with code 127. [/repos/dotnet/src/razor/artifacts/source-build/self/src/src/Razor/test/VSCode.FunctionalTest/Microsoft.AspNetCore.Razor.VSCode.FunctionalTest.npmproj]
  ##vso[task.logissue type=error;sourcepath=/repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets;linenumber=36;columnnumber=5;code=MSB3073;](NETCORE_ENGINEERING_TELEMETRY=Restore) The command "node -v" exited with code 127.
  /repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets(40,5): error : Building *.npmproj but NodeJS was not detected on path. Ensure NodeJS is on path or disable building NodeJS projects with /p:BuildNodeJs=false. Skipping NodeJS projects will also skip managed projects depending on them, including Components, Mvc and Analysers. [/repos/dotnet/src/razor/artifacts/source-build/self/src/src/Razor/test/VSCode.FunctionalTest/Microsoft.AspNetCore.Razor.VSCode.FunctionalTest.npmproj]
  ##vso[task.logissue type=error;sourcepath=/repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets;linenumber=40;columnnumber=5;code=;](NETCORE_ENGINEERING_TELEMETRY=Restore) Building *.npmproj but NodeJS was not detected on path. Ensure NodeJS is on path or disable building NodeJS projects with /p:BuildNodeJs=false. Skipping NodeJS projects will also skip managed projects depending on them, including Components, Mvc and Analysers.
    /tmp/MSBuildTemproot/tmp5e3ad59538504ee7b48b625239b3d246.exec.cmd: line 2: node: command not found
  /repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets(36,5): error MSB3073: The command "node -v" exited with code 127. [/repos/dotnet/src/razor/artifacts/source-build/self/src/src/Razor/src/Microsoft.AspNetCore.Razor.VSCode.Extension/Microsoft.AspNetCore.Razor.VSCode.Extension.npmproj]
  ##vso[task.logissue type=error;sourcepath=/repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets;linenumber=36;columnnumber=5;code=MSB3073;](NETCORE_ENGINEERING_TELEMETRY=Restore) The command "node -v" exited with code 127.
  /repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets(36,5): error MSB3073: The command "node -v" exited with code 127. [/repos/dotnet/src/razor/artifacts/source-build/self/src/src/Razor/src/Microsoft.AspNetCore.Razor.VSCode.Extension/Microsoft.AspNetCore.Razor.VSCode.Extension.npmproj]
  ##vso[task.logissue type=error;sourcepath=/repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets;linenumber=36;columnnumber=5;code=MSB3073;](NETCORE_ENGINEERING_TELEMETRY=Restore) The command "node -v" exited with code 127.
    /tmp/MSBuildTemproot/tmp863411ff14b34cd5b97a31474a40c704.exec.cmd: line 2: node: command not found
  /repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets(40,5): error : Building *.npmproj but NodeJS was not detected on path. Ensure NodeJS is on path or disable building NodeJS projects with /p:BuildNodeJs=false. Skipping NodeJS projects will also skip managed projects depending on them, including Components, Mvc and Analysers. [/repos/dotnet/src/razor/artifacts/source-build/self/src/src/Razor/src/Microsoft.AspNetCore.Razor.VSCode.Extension/Microsoft.AspNetCore.Razor.VSCode.Extension.npmproj]
  ##vso[task.logissue type=error;sourcepath=/repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets;linenumber=40;columnnumber=5;code=;](NETCORE_ENGINEERING_TELEMETRY=Restore) Building *.npmproj but NodeJS was not detected on path. Ensure NodeJS is on path or disable building NodeJS projects with /p:BuildNodeJs=false. Skipping NodeJS projects will also skip managed projects depending on them, including Components, Mvc and Analysers.
  /repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets(36,5): error MSB3073: The command "node -v" exited with code 127. [/repos/dotnet/src/razor/artifacts/source-build/self/src/src/Razor/src/Microsoft.AspNetCore.Razor.VSCode/Microsoft.AspNetCore.Razor.VSCode.npmproj]
  ##vso[task.logissue type=error;sourcepath=/repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets;linenumber=36;columnnumber=5;code=MSB3073;](NETCORE_ENGINEERING_TELEMETRY=Restore) The command "node -v" exited with code 127.
  /repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets(36,5): error MSB3073: The command "node -v" exited with code 127. [/repos/dotnet/src/razor/artifacts/source-build/self/src/src/Razor/src/Microsoft.AspNetCore.Razor.VSCode/Microsoft.AspNetCore.Razor.VSCode.npmproj]
  ##vso[task.logissue type=error;sourcepath=/repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets;linenumber=36;columnnumber=5;code=MSB3073;](NETCORE_ENGINEERING_TELEMETRY=Restore) The command "node -v" exited with code 127.
  /repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets(40,5): error : Building *.npmproj but NodeJS was not detected on path. Ensure NodeJS is on path or disable building NodeJS projects with /p:BuildNodeJs=false. Skipping NodeJS projects will also skip managed projects depending on them, including Components, Mvc and Analysers. [/repos/dotnet/src/razor/artifacts/source-build/self/src/src/Razor/src/Microsoft.AspNetCore.Razor.VSCode/Microsoft.AspNetCore.Razor.VSCode.npmproj]
  ##vso[task.logissue type=error;sourcepath=/repos/dotnet/src/razor/artifacts/source-build/self/src/eng/targets/Npm.Common.targets;linenumber=40;columnnumber=5;code=;](NETCORE_ENGINEERING_TELEMETRY=Restore) Building *.npmproj but NodeJS was not detected on path. Ensure NodeJS is on path or disable building NodeJS projects with /p:BuildNodeJs=false. Skipping NodeJS projects will also skip managed projects depending on them, including Components, Mvc and Analysers.

@MichaelSimons Yeah, the NPM stuff is for the VSCode blazor wasm debugging extension, so not something we need to source build. Does source build support slnf files as a build target? We could create a filter that only includes the parts that ship in the SDK and thus need source building.

@chsienki, Yes, source-build will work with slnf files.  You just need to  modify the SourceBuild.props to reference it instead of a sln.

Great, I'll get working on that and ping here when it's done.

@MichaelSimons https://github.com/dotnet/razor/pull/8019 was merged, which should fix the issue.

Thanks @chsienki - I pulled in the changes as a patch in https://github.com/dotnet/installer/pull/15105 to validate the e2e.


docs: base-Update comments in .env for cublas, openblas, clblas

This commit provides a little extra guidance for users when deciding whether to select cublas, openblas, or clblas.
This PR fixes #
Notes for Reviewers
Signed commits

[X] Yes, I signed my commits.

Thanks @scott4290 !


add backend and frontend of dashboard

resolve conflicts in pkg/storage/backend after create apiserver storage

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

files output by npm run build command can be ignored.

files output by npm run build command can be ignored.

Done

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@c9694c4). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #112   +/-   ##
=========================================
  Coverage          ?   21.70%
=========================================
  Files             ?       73
  Lines             ?     4341
  Branches          ?        0
=========================================
  Hits              ?      942
  Misses            ?     3269
  Partials          ?      130

Flag
Coverage Δ

unittests
21.70% <0.00%> (?)

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

Continue to review full report at Codecov.

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

/approve


Run SSM Agent on AWS by default

Current situation
The agent system service for the AWS Session Manager is not installed by default. It can be started as a Docker service with a customized image.
Impact
Users don't have this functionality available unless they know the system very well and are ready to run the agent themselves.
Ideal future situation
The agent runs by default if there is no drawback.
Implementation options
Run it via Docker with a customized image as written here. There is an OEM package for EC2 but I recommend to include the service file not in the OEM package but in the regular /usr partition and only start it under the systemd unit condition that the kernel command line includes the OEM ID, i.e., KernelCommandLine=flatcar.oem.id=ec2 (and maybe add KernelCommandLine=coreos.oem.id=ec2).
Build the Docker image in our quay repo and tag it with a version.
Additional information
All relevant links are in the blog post linked above.

I am interested and happy to contribute here. I dont like option to run it via docker, as it is tool like ssh, to access host itself, not container internals. And also because agent itself are just few golang binaries, w/o any external dependencies. I been able to run agent on a host by copying files from my docker container. Below is my dockerfile to build it:
FROM golang:1.12 as builder
ARG VERSION=2.3.1205.0
RUN set -ex && apt-get install make git gcc libc-dev curl bash && \
    curl -sLO https://github.com/aws/amazon-ssm-agent/archive/${VERSION}.tar.gz && \
    mkdir -p /go/src/github.com && \
    tar xzf ${VERSION}.tar.gz && \
    mv amazon-ssm-agent-${VERSION} /go/src/github.com/amazon-ssm-agent && \
    cd /go/src/github.com/amazon-ssm-agent && \
    gofmt -w agent && make checkstyle || ./Tools/bin/goimports -w agent && \
    make build-linux

## Copy files from this dir to /opt/ssm

#COPY --from=builder /go/src/github.com/amazon-ssm-agent/bin/linux_amd64/ /usr/bin
## From this locations to etc/amazon/ssm/
#COPY --from=builder /go/src/github.com/amazon-ssm-agent/bin/amazon-ssm-agent.json.template /etc/amazon/ssm/amazon-ssm-agent.json
#COPY --from=builder /go/src/github.com/amazon-ssm-agent/bin/seelog_unix.xml /etc/amazon/ssm/seelog.xml

@dongsupark do you think its a good thing to have? I can start working on it if you feel that it could be included to the official build.

@dongsupark only q i have (probably dummy one) is how to add package in the way that it is added only to AWS AMI

Hi,
thanks for stepping in. The idea of using it via Docker is that it can be easily updated which is not the case otherwise for OEM packages because they are extracted on installation and not part of the A/B update mechanism for the /usr partition.
Currently the oem-ec2 ebuild package in coreos-overlay is responsible for the OEM partition contents of the AMI but my idea was to move this single servicefile which is just a few bytes to invoke Docker to the /usr partition so that the service file itself gets updates. In the mean time it would also be ok to have it be part of the oem-ec2 ebuild.

@pothos ami update for me sounds like a better idea. With running over docker i see number of issues:

Isolation which we dont really need and all related issues
If docker fails to start agent will fail to start as well -> no way to fix vm
Not possible to start on early boot

But yes, like an idea to make it in /usr/bin in the base

The isolation can be minimized to share as much with the host as possible.
If needed we can also make the commands available in /usr/bin as small wrappers that either enter the Docker container (to resolve the correct libs), or expose the Docker filesystem and use an LD_PRELOAD trick in the wrapper.

I created initial version of the ebuild for the SSM.

@pothos i still think that running it in docker is a bad idea, for the reasons above. Also it will be different from any other system which bundles it.
About your concern about updating - i think it should be solved independently, without using A/B scheme. Either by AMI upgrade (something i am using now) or by making it via native updater tool (see amazon-ssm-agent/agent/update). Seems that this tool is not documented well, but it should be trivial to understand how it works and document it.

Found how native updater works. It is fetching manifest from the special url (e.g. https://s3.us-east-1.amazonaws.com/amazon-ssm-us-east-1/ssm-agent-manifest.json). Then it selects binary for the right system and performing update. To support Flatcar - either vendor needs to provide binaries for it or we should use different manifest source. Probably when ssm-agent would land into flatcar we can try to speak with AWS about building and supporting package for it.

I think I agree with @samm-git here.  We've been running the SSM agent on all our containers for a while, and not via docker.  The whole point of SSM is to give you a great deal of control of the host from the AWS console/api's and to do that means you'd need to essentially mount every host directory to the docker container, which completely defeats the purpose of sandboxing it in docker in the first place.
I noticed that the PR was merged a couple of days ago.  Any idea when this will be available in stable?
Thanks for your hard work here @samm-git I was thinking we might do the same thing. You've saved me a bit of work.

According to commit details, 2605.9.0 contains those changes, but systemd unit file is not in filesystem. Do I need to build AMI by myself to enable it?

We wanted to enable it, but could not because of partition size issues.
See https://github.com/kinvolk/coreos-overlay/pull/510 for details.
I think such issues are going to happen again if we keep the current mechanism of OEM partitions.

@samm-git
Hi Alex, Can you please simplify and tell us if we can use your AWS AMI with SSM agent installed and enabled?
I need this badly and I need this fast. In fact, one of the future requirements would be to allow the SSM agent to upgrade itself in prod. I guess it would be a red flag for anyone running a big fleet of flatcar not being able to get the operational insights.
I can sure give a hand in code/build efforts.

@pothos
Do you see any new way of enabling ssm agent in flatcar linux?
It's a red flag from the security reviewers.

@pothos
Do you see any new way of enabling ssm agent in flatcar linux?
It's a red flag from the security reviewers.

You can run it in Docker container https://thepracticalsysadmin.com/deploy-aws-ssm-agent-to-coreos/ but I would probably add some more Docker parameters to be able to access the host environment from within the container.

You can run it in Docker container https://thepracticalsysadmin.com/deploy-aws-ssm-agent-to-coreos/ but I would probably add some more Docker parameters to be able to access the host environment from within the container.

I am doing it from userdata, without docker. I was proposing different options to solve it in flatcar but so far no luck. I personally see this as a serious issue for the flatcar/aws.

I am doing it from userdata, without docker. I was proposing different options to solve it in flatcar but so far no luck. I personally see this as a serious issue for the flatcar/aws.

@bjethwan i can share my recipe later if you interested.

@bjethwan i can share my recipe later if you interested.

@dongsupark may be we should just extend oem part. size as a workaround before oem mechanism is recreated?

@dongsupark may be we should just extend oem part. size as a workaround before oem mechanism is recreated?

Or we could host some resources that are too large elsewhere and fetch them through Ignition…

Or we could host some resources that are too large elsewhere and fetch them through Ignition…

@pothos this also could be an option, however, will require connectivity to such location, what is not always a good option. This is what i am doing now, from s3 bucket. However, still think it must be part of the base in aws. Like it is with other cloud-native distros.

@pothos this also could be an option, however, will require connectivity to such location, what is not always a good option. This is what i am doing now, from s3 bucket. However, still think it must be part of the base in aws. Like it is with other cloud-native distros.

What I'm doing now is downloading SSM agent rpm file from S3 bucket stated in official AWS docs, then extract binary from the rpm.
I used busybox image for extracting agent binary because Flatcar doesn't seem to contain tools required for extracting rpm files.

What I'm doing now is downloading SSM agent rpm file from S3 bucket stated in official AWS docs, then extract binary from the rpm.
I used busybox image for extracting agent binary because Flatcar doesn't seem to contain tools required for extracting rpm files.

@pothos i still feel that as short-term solution changing partition size is a way to go.

@pothos i still feel that as short-term solution changing partition size is a way to go.

With btrfs compression (just zlib for the start until GRUB gets updated) we are finally able to fit the 122 MB binaries into the OEM partition, resulting in a 37 MB used filesystem.
A quick estimate: Depending on what we put in we have space for ~300 MB more Go binaries until the 128 MB filesystem is full.

The SSM Agent is now included on the AWS image (released in next Alpha): https://github.com/kinvolk/coreos-overlay/pull/1162
I think we can close this issue now, please try it out after the Alpha release and give your feedback, in case we need to reopen this :)


Disabled prop no longer passed to WrappedComponent

Our implementation of a sortable list ca. 0.0.9 depended on the disabled prop being passed through to the wrapped child component, but it appears as of 0.6.2 this is no longer the case. Our workaround currently looks like this:
const Item = SortableElement(({ child, itemClassName, disableSorting }) => {
  const classes = classnames('sortable-item', { 'sortable-item--disabled': disableSorting }, itemClassName)
  return <RecordListItem className={classes}>{child}</RecordListItem>
})

const List = SortableContainer(({ items, loaded, copy, itemClassName, disableSorting }) => {
  const renderChild = (child, index) => {
    const props = {
      key: `item-${index}`,
      itemClassName,
      index,
      child,
      disabled: disableSorting,
      disableSorting,
    }
    return <Item {...props} />
  }

  return (
    <RecordList loaded={loaded} copy={copy}>
      {items.map(renderChild)}
    </RecordList>
  )
})

Would be great to just use the disabled prop and not have a duplicate prop for this. Is there any reason why disabled is explicitly omitted from the passed-through props?

Yeah, this is an unfortunate side-effect of https://github.com/clauderic/react-sortable-hoc/issues/98
See #128 and #180 for more context


Streamer should count as a mod

It doesn't seem like the streamer counts as a 'mod' for purpose of 'mod-only commands', meaning streamer can't easily create/delete their own commands.
Example debug output, showing the user-type being empty:

2017/07/24 16:52:36 [IN]  @badges=moderator/1,subscriber/0,turbo/1;color=#5F5775;display-name=r4v5;emotes=433:65-66;id=156a2dbc-ff2f-404e-99fb-4abc589a2204;mod=1;room-id=113481237;subscriber=1;tmi-sent-ts=1500933155182;turbo=1;user-id=39399416;user-type=mod<EMAIL_ADDRESS>PRIVMSG #bengineering :Yep, still need to fix that so that the streamer counts as a mod
2017/07/24 16:52:51 [IN]  @badges=broadcaster/1,subscriber/0;color=#DAA520;display-name=Bengineering;emotes=;id=c25b5f41-5884-48ff-b638-b9a58baba0ee;mod=0;room-id=113481237;sent-ts=1500933126760;subscriber=1;tmi-sent-ts=1500933170337;turbo=0;user-id=113481237;user-type=<EMAIL_ADDRESS>PRIVMSG #bengineering :ohhhh alright cool I thought I was crazy

Workaround: Streamer can mod themselves in Twitch chat with the /mod command :D


Submit release 4 (final)

[ ] Source code

[ ] Have the code of the application

[x] Have script to import lira data

[ ] Have a commit tagged "v4"
[ ] Have a Readme to deploy the application ("it should be possible to install and deploy the group's software based on the READMEs")

[x] Configuration
[x] Dependencies
[x] Building steps
[x] Start built website
[ ] Test readme from scratch

[ ] Server up-to-date and running on v4
[x] Teachers have access to repos
[ ] Check for author tags
[ ] Check for unused packages/files/remove all unnecessary console.log

[ ] Reports

[ ] Submit System specification
[ ] Submit Handbook
[ ] Submit Frontend documentation (from the generated one)
[x] A conversion table Name/Student id/author tag/GitHub name (in Appendix B.)
[x] Provide upload password (in Appendix A.)
[ ] A list identifying which students have worked on which parts of the project (see 8. for more info) (in Appendix C.)

SE2-Project-e23-Final-Submission.pdf

@a-thansen & @marcosantiagomuro this issue represents the last thing to do for SE2 (submit everything on DTU learn). The todo list can help to catch oversight. The pdf (comment on Nov 10) is authoritative
because i'll most likely not be available in the coming days, i assign you two so that at least one of you submit when everything is done

okay thank youuu


Move spring-security to Compile Only since its not a requirement.

Pull Request type

[ ] Bugfix
[ ] Feature
[ ] Refactoring (no functional changes, no api changes)
[x] Build related changes
[ ] Other (please describe):

Changes in this PR
Move spring-security as an optional module. Fixes #631

We should move this, ref below, to happen as part of a static init block/object or refactor the class to support a chain of handlers and then make the spring-security handler available conditionally on the org.springframework.security.access.AccessDeniedException class.
        val springSecurityAvailable = try {
            Class.forName("org.springframework.security.access.AccessDeniedException")
            true
        } catch (ex: ClassNotFoundException) {
            false
        }


Script errors, System.Runtime or dependency

inflating: System.ServiceModel.Primitives.dll
The entry point method could not be loaded due to Could not load file or assembly 'System.Runtime, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies.
This is the error I get when running the script. I just installed Mono v6, any ideas?
mono --version:
Mono JIT compiler version <IP_ADDRESS> (Debian <IP_ADDRESS>+dfsg-2 Wed Feb 26 23:23:50 UTC 2020)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS:           __thread
SIGSEGV:       altstack
Notifications: epoll
Architecture:  amd64
Disabled:      none
Misc:          softdebug
Interpreter:   yes
LLVM:          supported, not enabled.
Suspend:       hybrid
GC:            sgen (concurrent by default)

Hey :) I'm sorry you are having trouble with the script. That error is coming from depotdownloader. I'm not sure what's causing it. I'm on mono 6.4.0 as that is the latest available version in the stable Manjaro repository.
I would suggest you try to first confirm the issue is with depotdownloader by attempting to run it directly:

Change to the depotdownloader directory cd ~/doomgrader/depotdownloader
Download the first chunk with ./depotdownloader -app 782330 -depot 782332 -manifest<PHONE_NUMBER>586464647 -username "YOUR_STEAM_USERNAME" -password "YOUR_STEAM_PASSWORD" -remember-password -dir "~/doomgrader/files" (you will have to manually enter your Steam credentials)

If you are still running into problems, you can try running depotdownloader with dotnet instead of mono. We are swapping out the dotnet dependency to mono for improved compatibility but it's technically not supported by depotdownloader. It could be causing issues with your system. If you have access to dotnet in your distro, you could try using that:

Install dotnet. More info here (don't forget to add it to your path if required on your distro)
Remove the depotdownloader directory rm -rf ~/doomgrader/depotdownloader
Comment out this line by putting a # at the start
Run doomgrader again ./doomgrader

Seems like the latter worked for me! Have to run steam in offline mode and turn off auto updates but we're all good!

Great! I'm glad you got it working :)
You shouldn't have to run steam in offline mode or disable updates. It won't verify the game files until a new update is released and the next update is going to remove the anti cheat anyway!
If the game gets updated and still doesn't work on Linux for any reason, you can just re-copy the downgraded files with ./doomgrader -c. You won't have to re download the files as doomgrader keeps a copy of them


Update request: nexusmods-app 0.4.1 → 0.5.1

Package name: nexusmods-app

Latest released version: 0.5.1

Current version on the unstable channel: N/A

Current version on the stable/release channel: N/A

[x] Checked the nixpkgs pull requests

Make sure to follow upstream package maintainers documentation.
Notify maintainers

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

I think it should be on packaging request, not out-of-date package update.

@MisileLab it was packaged in https://github.com/NixOS/nixpkgs/pull/270372 at v0.4.1, it just hasn't made nixos-unstable yet.

Blocked:
❯ nix-shell maintainers/scripts/update.nix --argstr package nexusmods-app

this derivation will be built:
  /nix/store/jq9mmjkarxdylc3w1rskhmfgm1adl9z3-packages.json.drv
building '/nix/store/jq9mmjkarxdylc3w1rskhmfgm1adl9z3-packages.json.drv'...

Going to be running update for following packages:
 - nexusmods-app-0.4.1

Press Enter key to continue...
Running update for:
 - nexusmods-app-0.4.1: UPDATING ...
 - nexusmods-app-0.4.1: ERROR

--- SHOWING ERROR LOG FOR nexusmods-app-0.4.1 ----------------------

cp: cannot stat '/tmp/deps-nexusmods-app-e6jxVa/home/.nuget/packages/*': No such file or directory

--- SHOWING ERROR LOG FOR nexusmods-app-0.4.1 ----------------------
The update script for nexusmods-app-0.4.1 failed with exit code 1

well, now 0.6.0 is out https://github.com/Nexus-Mods/NexusMods.App/releases/tag/v0.6.0 xD

Closing in favour of #331150.


Increase targetSdkVersion to 33

Also, add POST_NOTIFICATIONS permission to the Android manifest.

The usage of AlarmManager should be migrated
https://github.com/thunderbird/thunderbird-android/blob/8f06c24bd3b6cc04abcda86de0b63ad420764781/app/core/src/main/java/com/fsck/k9/helper/AlarmManagerCompat.kt#L10
See https://developer.android.com/about/versions/14/changes/schedule-exact-alarms

the permission introduced in Android 12 for apps to schedule exact alarms, is no longer being pre-granted to most newly installed apps targeting Android 13 and higher (will be set to denied by default)

After bumping to targetSdk 33, this permission will not be granted automatically on Android 14 devices for clean installations.

I currently don't see a way around using exact alarms. Staying below targetSdkVersion 33  isn't an option either. So I'll merge this change and we'll deal with Android 14 separately.
I created issue #7363 to keep track of the problem.


Got the login and signup forms to show and hide properly. Renamed js …

…files to json

Yay!!! You did it.


Convert a few GLSL shaders to Rust

We talked about today that we should convert a few of our existing rendering shaders to Rust to see how well we could express it, even if we can't compile it to SPIRV or run them yet. Having a few GLSL or HLSL shaders here in the repo that we also have a manually converted Rust versions of, initially maybe just rough Rust psuedo code but can also try and build them in a Rust CPU crate project to actually compile it.
Can take for example the Ark mesh and sky shaders, they are quite basic and fine to duplicate to this repo for testing.
This would be a helpful guide to see what functions we would want in a shader core crate, that doesn't exist in Rust std, also for easy porting of existing shaders. And will be a guide to see what areas of Rust are the least ergonomic for shaders where we may want to have Rust language shaders to simplify it.

I think this can be closed now on the rust-gpu side? We have converted quite a few shaders to Rust.

I think this can be closed now on the rust-gpu side? We have converted quite a few shaders to Rust.


fix: rewrite monitor test

https://github.com/omisego/elixir-omg/issues/988
Overview
Harden the test that was sometimes failing.
Changes

I've merged two tests into one to avoid side affects

Testing
/

Coverage remained the same at ?% when pulling d521b5a4e01aaa6b57258bccbcb1ac5c58611816 on 988-tuple_spcs into 56b047f779b4e41d8b0f6ff8200a1effe66d3b04 on master.


Temporarily disable failing tests

Ticket
#458
Problem description
Temporarily disable failing tests test_adaptive_avg_pool_2d and test_masked_fill
What's changed

Skip tests of test_adaptive_avg_pool_2d and test_masked_fill

Good run
https://github.com/tenstorrent/pytorch2.0_ttnn/actions/runs/11930823963


Problem with TFRecords Preparation

Error occurs in for shard_id, (image, label) in enumerate(dataset):  I checked dataset length and output which is not empty.  please help me
Thank you
--train2
     --n000002
        --0001_0.jpg
        --0001_02.jpg
        --0001_03.jpg
     --n000003
     --n000004

dataset_path = 'C:/Users/Kmu/PycharmProjects/train2'
tfrecs_path = 'C:/Users/Kmu/PycharmProjects/dosyalar/tfrecords'
shard_size = 12000
tensorflow version 1.14.0 and 1.15.0 tested same result
ERROR
2020-01-08 09:29:18.958101: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at strided_slice_op.cc:107 : Invalid argument: slice index -1 of dimension 0 out of bounds.
2020-01-08 09:29:18.958102: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at strided_slice_op.cc:107 : Invalid argument: slice index -1 of dimension 0 out of bounds.
2020-01-08 09:29:18.958102: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at strided_slice_op.cc:107 : Invalid argument: slice index -1 of dimension 0 out of bounds.
2020-01-08 09:29:18.958109: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at strided_slice_op.cc:107 : Invalid argument: slice index -1 of dimension 0 out of bounds.
2020-01-08 09:29:18.958112: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at strided_slice_op.cc:107 : Invalid argument: slice index -1 of dimension 0 out of bounds.
2020-01-08 09:29:18.958114: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at strided_slice_op.cc:107 : Invalid argument: slice index -1 of dimension 0 out of bounds.
2020-01-08 09:29:18.958146: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at strided_slice_op.cc:107 : Invalid argument: slice index -1 of dimension 0 out of bounds.
2020-01-08 09:29:18.959258: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at strided_slice_op.cc:107 : Invalid argument: slice index -1 of dimension 0 out of bounds.
2020-01-08 09:29:18.985959: W tensorflow/core/framework/op_kernel.cc:1502] OP_REQUIRES failed at iterator_ops.cc:1037 : Invalid argument: slice index -1 of dimension 0 out of bounds.
	 [[{{node strided_slice}}]]
multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
  File "C:\Users\Kmu\AppData\Local\Programs\Python\Python36\lib\multiprocessing\pool.py", line 119, in worker
    result = (True, func(*args, **kwds))
  File "C:\Users\Kmu\AppData\Local\Programs\Python\Python36\lib\multiprocessing\pool.py", line 44, in mapstar
    return list(map(*args))
  File "C:\Users\Kmu\PycharmProjects\deneme1\tfrecords-faster\tfrecsfaster\prepare_tfrecords2.py", line 73, in task
    for shard_id, (image, label) in enumerate(dataset):
  File "C:\Users\Kmu\PycharmProjects\deneme1\venv\lib\site-packages\tensorflow\python\data\ops\iterator_ops.py", line 586, in __next__
    return self.next()
  File "C:\Users\Kmu\PycharmProjects\deneme1\venv\lib\site-packages\tensorflow\python\data\ops\iterator_ops.py", line 623, in next
    return self._next_internal()
  File "C:\Users\Kmu\PycharmProjects\deneme1\venv\lib\site-packages\tensorflow\python\data\ops\iterator_ops.py", line 615, in _next_internal
    output_shapes=self._flat_output_shapes)
  File "C:\Users\Kmu\PycharmProjects\deneme1\venv\lib\site-packages\tensorflow\python\ops\gen_dataset_ops.py", line 2150, in iterator_get_next_sync
    _six.raise_from(_core._status_to_exception(e.code, message), None)
  File "<string>", line 3, in raise_from
tensorflow.python.framework.errors_impl.InvalidArgumentError: slice index -1 of dimension 0 out of bounds.
	 [[{{node strided_slice}}]] [Op:IteratorGetNextSync]
"""

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "C:/Users/Kmu/PycharmProjects/deneme1/tfrecords-faster/tfrecsfaster/prepare_tfrecords2.py", line 92, in <module>
    pool.map(task, inputs)
  File "C:\Users\Kmu\AppData\Local\Programs\Python\Python36\lib\multiprocessing\pool.py", line 266, in map
    return self._map_async(func, iterable, mapstar, chunksize).get()
  File "C:\Users\Kmu\AppData\Local\Programs\Python\Python36\lib\multiprocessing\pool.py", line 644, in get
    raise self._value
tensorflow.python.framework.errors_impl.InvalidArgumentError: slice index -1 of dimension 0 out of bounds.
	 [[{{node strided_slice}}]] [Op:IteratorGetNextSync]

Process finished with exit code 1

/////////////////////////////////////////////////////////////////////////
All code
#!/usr/bin/env python3

import os

WORKERS = os.cpu_count()
print("Using %d workers." % WORKERS)

dataset_path = 'C:/Users/Kmu/PycharmProjects/train2'
tfrecs_path = 'C:/Users/Kmu/PycharmProjects/dosyalar/tfrecords'
shard_size = 12000

n_samples = None

def tensorflow():
    import tensorflow as tf
    tf.enable_eager_execution()
    return tf

def init_task():
    print('[init_task] Started...')
    tf = tensorflow()
    image_paths = tf.io.gfile.glob(dataset_path + '/*/*.jpg')
    batch_size = len(image_paths) // WORKERS
    if len(image_paths) % WORKERS != 0:
        batch_size += 1
    image_paths_batched = [
        image_paths[index * batch_size: (index + 1) * batch_size]
        for index in range(WORKERS)
    ]
    global n_samples
    n_samples = len(image_paths)
    print('[init_task] Exiting...')
    return image_paths_batched

def task(inputs):
    worker_id, filenames = inputs

    def print_info(text):
        print('[Worker %d] %s' % (worker_id, text))

    print_info('Started...')

    tf = tensorflow()

    def wrap_bytes(list_of_bytestrings):
        return tf.train.Feature(bytes_list=tf.train.BytesList(value=list_of_bytestrings))

    def get_image_and_class(image_path):
        class_label = tf.strings.split(tf.expand_dims(image_path, axis=-1), sep='/').values[-2]
        img = tf.io.read_file(image_path)
        return img, class_label

    def to_tfrecord(image, class_name):
        feature = {
            'image': wrap_bytes([image]),
            'class': wrap_bytes([class_name])
        }
        return tf.train.Example(features=tf.train.Features(feature=feature))

    filenames = tf.convert_to_tensor(filenames)
    dataset = tf.data.Dataset.from_tensor_slices(filenames)
    dataset = dataset.shuffle(n_samples // WORKERS)
    dataset = dataset.map(get_image_and_class, tf.data.experimental.AUTOTUNE)
    dataset = dataset.batch(shard_size)

    for shard_id, (image, label) in enumerate(dataset):
        print_info('Working on shard %d' % shard_id)
        image, label = image.numpy(), label.numpy()
        current_shard_limit = image.shape[0]
        filename = tfrecs_path + '/worker{}-{:06d}-l{}.tfrec'.format(worker_id, shard_id, current_shard_limit)
        with tf.io.TFRecordWriter(filename) as out_file:
            for i in range(current_shard_limit):
                record = to_tfrecord(image[i], label[i])
                out_file.write(record.SerializeToString())
        print_info('Wrote file {} containing {} records'.format(filename, current_shard_limit))

image_paths_batched = init_task()
inputs = [(index, batch) for index, batch in enumerate(image_paths_batched)]

import multiprocessing

if __name__ == '__main__':
    with multiprocessing.Pool(WORKERS) as pool:
        pool.map(task, inputs)

    print('All workers exited')

Not sure what is causing the error to occur.
Are you using this script to prepare TFRecords using your dataset?

Any updates, @reducedwow? (I had tried but couldn't reproduce the error)


[RIP-9]Submit yaml file of deployment type

Submit yaml test files of deployment type

Why not make changes to the original file?

How should I operate here

I have finished the modification. Do you have anything else to modify
@Poorunga


improved skeletal muscle regeneration plus review of decreased/increased X regeneration terms

new child of improved muscle regeneration MP:0013161 and abnormal skeletal muscle regeneration MP:0013237
need to add synonyms for enhanced/increased to this and the existing term
see J:304135 and J:238474, also existing annotations to MP:0013237

Review/standardize textual definition for impaired/improved X regeneration terms (related to issues #3401 and #3474

Rename all decreased X regeneration terms using “impaired” in primary term label (add decreased/reduced as synonyms)

Rename all increased X regeneration terms using ‘enhanced” (add increased/improved as synonyms)

Tweak textual definition to include both injury and disease

Abnormal X: anomaly in the renewal, repair, and/or regrowth of [ ] following injury or disease

Impaired: decrease in the renewal, repair, and/or regrowth of [ ] following injury or disease

Enhanced: increase in the renewal, repair, and/or regrowth of [ ] following injury or disease

Changed primary term labels for tissue specific regeneration terms (now using impaired and enhanced) and tweaked textual definitions to include both injury and disease in all instances.
Added new term:
enhanced skeletal muscle regeneration MP:0031318 (new synonyms: increased skeletal muscle regeneration, improved skeletal muscle regeneration)
Also, added new terms impaired intestine regeneration MP:0031319 and enhanced intestine regeneration MP:0031320