Update scalafmt-core to 2.7.4

Updates org.scalameta:scalafmt-core from 2.7.2 to 2.7.4.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, semver-patch

Codecov Report

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

@@            Coverage Diff            @@
##             master     #100   +/-   ##
=========================================
  Coverage          ?   28.78%
=========================================
  Files             ?       40
  Lines             ?     1716
  Branches          ?       37
=========================================
  Hits              ?      494
  Misses            ?     1222
  Partials          ?        0

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 35532c3...af363a2. Read the comment docs.


build failed

run is ok
build failed
Building com.mxqh.wsapp for device (ios-release)...
Automatically signing iOS for device deployment using specified developm                                                                                ├─Building Dart code...                                    99.8s                                                                                ├─Generating dSYM file...                                   0.5s
 ├─Stripping debug symbols...                                0.4s
 ├─Assembling Flutter resources...                           7.6s
 └─Compiling, linking and signing...                        51.5s
Xcode build done.                                           177.6s
Failed to build iOS app
Error output from Xcode build:
↳
    2019-02-22 14:22:36.891 xcodebuild[61424:5145419] [MT] PluginLoading: Required plug-in compatibility UUID D7881182-AD00-4C36-A94D-F45FC9B0CF85 for plug-in
    at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/KSImageNamed.xcplugin' not present in DVTPlugInCompatibilityUUIDs
    2019-02-22 14:22:36.892 xcodebuild[61424:5145419] [MT] PluginLoading: Required plug-in compatibility UUID D7881182-AD00-4C36-A94D-F45FC9B0CF85 for plug-in
    at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/FuzzyAutocomplete.xcplugin' not present in DVTPlugInCompatibilityUUIDs
    2019-02-22 14:22:36.892 xcodebuild[61424:5145419] [MT] PluginLoading: Required plug-in compatibility UUID D7881182-AD00-4C36-A94D-F45FC9B0CF85 for plug-in
    at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Alcatraz.xcplugin' not present in DVTPlugInCompatibilityUUIDs
    2019-02-22 14:22:38.166 xcodebuild[61424:5145467]  DTDeviceKit: deviceType from 6070e3de45c7ad35ba42a806f80bde6f532ec9a4 was NULL
    ** BUILD FAILED **

Xcode's output:
↳
    === BUILD TARGET Runner OF PROJECT Runner WITH CONFIGURATION Release ===
    The use of Swift 3 @objc inference in Swift 4 mode is deprecated. Please address deprecated @objc inference warnings, test your code with “Use of
    deprecated Swift 3 @objc inference” logging enabled, and then disable inference by changing the "Swift 3 @objc Inference" build setting to "Default" for
    the "Runner" target.
    The use of Swift 3 @objc inference in Swift 4 mode is deprecated. Please address deprecated @objc inference warnings, test your code with “Use of
    deprecated Swift 3 @objc inference” logging enabled, and then disable inference by changing the "Swift 3 @objc Inference" build setting to "Default" for
    the "Runner" target.
    === BUILD TARGET Runner OF PROJECT Runner WITH CONFIGURATION Release ===
    Non-fat binary /Users//MEGA/Flutter/wsapp/wsapp/build/ios/Release-iphoneos/Runner.app/Frameworks/flustars.framework/flustars is not armv7. Running
    lipo -info:
    Non-fat file: /Users//MEGA/Flutter/wsapp/wsapp/build/ios/Release-iphoneos/Runner.app/Frameworks/flustars.framework/flustars is architecture: arm64
    Command /bin/sh failed with exit code 1

你用^0.1.9先试下

好像还是一样的,你试下 flutter build ios --release

我没有appp Id，你去flutter github上去搜下吧，有32位打包异常，ios我不太懂


feat: add custom logger support to HECEventWriter (v3+)

This is just to enable a specific use case in a consuming app.

I don't think the failing check is related to my code? Am I safe to merge it without making it pass or not?
For context:
Cache entry deserialization failed, entry ignored
Collecting pip
  Downloading https://files.pythonhosted.org/packages/b1/44/6e26d5296b83c6aac166e48470d57a00d3ed1f642e89adc4a4e412a01643/pip-21.1.2.tar.gz (1.6MB)
    100% |████████████████████████████████| 1.6MB 593kB/s eta 0:00:01
Installing collected packages: pip
  Found existing installation: pip 8.1.1
    Uninstalling pip-8.1.1:
      Successfully uninstalled pip-8.1.1
  Running setup.py install for pip ... - \ | / - \ | done
Successfully installed pip-21.1.2
Traceback (most recent call last):
  File "/opt/circleci/.pyenv/versions/2.7.12/bin/pip", line 9, in <module>
    load_entry_point('pip==21.1.2', 'console_scripts', 'pip')()
  File "/opt/circleci/.pyenv/versions/2.7.12/lib/python2.7/site-packages/pkg_resources/__init__.py", line 542, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/opt/circleci/.pyenv/versions/2.7.12/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2569, in load_entry_point
    return ep.load()
  File "/opt/circleci/.pyenv/versions/2.7.12/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2229, in load
    return self.resolve()
  File "/opt/circleci/.pyenv/versions/2.7.12/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2235, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/opt/circleci/.pyenv/versions/2.7.12/lib/python2.7/site-packages/pip/__init__.py", line 1, in <module>
    from typing import List, Optional
ImportError: No module named typing


Fix spinner racing condition

This should fix spinner issue for github reported in #13 and #17 .
As far as I found out the in #13 described racing condition, was caused by fetching the user icons (.AvatarStack), which happens after triggering the pjax:end, but replaces the icons again.
It also looks like Github isn't triggering a mutation event each time they change items , but rather just overwrites the innerHtml property of a parent element.
I.e. when observing QUERY_FILE_TABLE_ITEMS, the observer callback never got triggered.
The changes in the implementation of the observer were inspired by @wyze 's PR #18 .
But the observer only observes #js-repo-pjax-container, instead of body and only triggers showRepoTreeIcons instead of update, which should lead to bit increased performance.
Github also changed the markup for the breadcrumbs.
While it still work if a file is displayed, it doesn't work if a folder is displayed.
Thus, I changed QUERY_PATH_SEGMENTS from js-path-segment to .repository-content .breadcrumb a.
To simplify debugging while developing I changed the build:dev to use webpack in development mode and create source-map files.
If there are some brave testers in #13 and/or #17 here are the built extensions as zip.
I hope having testers helps you with the review ^^
chrome-github-vsci-1.20.zip
edge-github-vsci-1.20.zip
firefox-github-vsci-1.20.zip
closes #13 #17 #18

Hi,
thank you very much for this PR, I like every change you made :+1: !
I did a lot of testing and it seems that everything works fine.
I'm going to merge this, do some refactor and release new version of extension this weekend
📦 :rocket:
Thanks


Add settings/vscode integration for diagnostic "global-element"

This PR adds the settings necessary for the diagnostic global-element and group strict-conventions we add in "Add optional diagnostic warning about any global element" #2040.
The diagnostic is disabled by default and put in a separate group, so it won't affect any existing configurations.
Affected settings:

diagnostics.disable (will disable global-element as well)
diagnostics.neededFileStatus (global-element is now an option)
diagnostics.severity (global-element is now an option)
diagnostics.groupfilestatus (strict-conventions is now an option)
diagnostics.groupseverity (strict-conventions is now an option)

Messages are added in english language files
Note: This PR does not take care about updating the submodule.

These contents will be generated automatically, you don't need to submit PR for them


Generating Static Gestures

Hi,
I tried to create push hand out gesture from NvGestures dataset by importing the StaticGesture Actor and modifying the FingerSpacingVariation, ArmNoise and related parameters. However, the best I could get to is this:

Is there a tutorial/documentation on how these hand and finger-related parameters can be modified to generate more static gestures (e.g., show index finger, show three fingers)?

Hi, thanks for trying to expand the gestures, the FingerSpacingVariation, ArmNoise and related parameters, are intended to adjust the shape of the hand and the arm jitters a person do when performing a gesture. However, you create different gestures by defining a new spline path for the model and adding selecting this new gesture from the Actor Settings. You could create those spline with a blueprint, or simply duplicate/edit one of the existing the gestures and manipulate its spline with the GUI. You can check the below screenshot for different options.

Yes, that makes sense. I was looking at a simpler approach towards creating a new static gestures; which is, since the only difference between Gesture4 in your framework and the push hand out gesture is orientation of Ring, Pinky, and Thumb fingers. Hence I created a copy of Gesture4 Actor and tried to modify the following parameters:

But I could figure what finger-related parameter changes I need to make to transform Gesture4 into a push hand out. I apologize for not precisely describing the issue in my previous comment.

No worries at all. All of the variations are options to make the gesture differ. This is like having different participants. I have enabled some of them already by default and that is why you don't get exactly the same gesture performed every time you play. You can find below a brief description of what each of the variations do, I have also added to the github readme:
• SpeedVariation
Changes the speed at which the gesture will be performed. Depending on the setting in the gesture, this might also influence the speed of the pre- and post gesture (these are the path followed until the position of the spline and back). If a relative value is selected, it will be relative to the default speed in the gesture settings.
• PositionVariation
Changes the position of the spline. It is recommended to use relative values since absolute values refer to the world coordinates.
• FingerVariation
Changes how angled each finger is. A value of 0 for all fingers represents a flat hand, while a value of -90 for all fingers represents a fist.
• HandNoise
Changes the rotation of the hand. The hand can move from a random starting rotation to a random end rotation during the gesture. This is only recommended for arm gestures.
• ArmNoise
Determines how much the arm should move for gestures performed by the hand or a finger.
• HandNoise
Determines how much the hand should move for gestures performed by a finger.
• FingerSpacingVariation
Change the spacing between fingers. For example to create a piece sign with the fingers.
• StaticPause
Changes how long the hand should hold the pose for static gestures.
• RadiusVariation (not in all gestures)
Changes the radius of gestures that are based on a circle. Can also be used to distort the circle.
• PositionVariation
Changes the position of the effector for animation-based gestures.

Thanks for the detailed explanation! Now I am able to generate the full palm gesture :)

One last question before closing the ticket: What is the functionality of variable Arm Part: {Arm, Hand, Finger}. What impact it has the generated gesture?

The Arm part is also a way of variation for how the gesture is performed. You could try it out with Gesture 1 and see how it affects the gesture performance every time you play the scene. It is also again a way to simulate different human behavior. For example, '''Arm''' option makes the gesture movement from left to right (for Gesture 1) coming from the Arm, while '''Hand''' make the movement originating from the hand itself, while '''Finger''' does not make sense here and will cause a weird behavior as you can see when playing it.


Fix #1086: exit with 0 code on help

What is the purpose of this change? What does it change?
Make CommandLine not exit on error and intercept flag.ErrHelp to return
0 instead of default behavior of flag.Parse which is to exit with code 2
on error (flag.ErrHelp is raised when help is asked).
Was the change discussed in an issue?
fixes #1086
How to test changes?
odo -h returns 2 prior to this change
odo -h returns 0 after
Nothing else should change.

:white_check_mark: odo build 702 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/823f93ae2b by @metacosm)

But doesn't exit code 2 make sense? https://shapeshed.com/unix-exit-codes/
"2 - Misuse of shell builtins (according to Bash documentation)"

But doesn't exit code 2 make sense? https://shapeshed.com/unix-exit-codes/
"2 - Misuse of shell builtins (according to Bash documentation)"
@metacosm @geoand

I was wondering that myself since returning 2 is pretty standard for go tools on -h invocation (that behavior is the behavior you get from the default flag package)…

even oc -h and kubectl -h returns 0

Yeah, I would avoid going the exit-with-0 route and stick with the normal conventions (error 2). It makes sense.

Yeah, I would avoid going the exit-with-0 route and stick with the normal conventions (error 2). It makes sense.

That is not the standard convention :-)
see https://github.com/redhat-developer/odo/issues/1086#issuecomment-445244309
I'm happy to proven wrong. Show me one tool that returns an error code when you call it with the correct flag or command to display help.

@kadel Yeah, you're right. Even after checking kubectl and oc and a few other's it's all completely different.
Kompose provides error 255
Cobra provides error 1
oc provides 0
kubectl provides 0

Available Commands:
  add         Add a command to a Cobra Application
  help        Help about any command
  init        Initialize a Cobra Application

Flags:
  -a, --author string    author name for copyright attribution (default "YOUR NAME")
      --config string    config file (default is $HOME/.cobra.yaml)
  -h, --help             help for cobra
  -l, --license string   name of license for the project
      --viper            use Viper for configuration (default true)

Use "cobra [command] --help" for more information about a command.

~
▶ echo $?
0

~
▶ godef --kalsdjfklasjdf
flag provided but not defined: -kalsdjfklasjdf
usage: godef [flags] [expr]
  -A	print all type and members information
  -a	print public type and member information
  -acme
    	use current acme window
  -debug
    	debug mode
  -f string
    	Go source filename
  -i	read file from stdin
  -json
    	output location in JSON format (-t flag is ignored)
  -o int
    	file offset of identifier in stdin (default -1)
  -t	print type information

~                                                                                ⍉
▶ echo $?
2

~
▶ kompose --askldfjsdf
eError: unknown flag: --askldfjsdf
Usage:
  kompose [command]

Available Commands:
  completion  Output shell completion code
  convert     Convert a Docker Compose file
  down        Delete instantiated services/deployments from kubernetes
  help        Help about any command
  up          Deploy your Dockerized application to a container orchestrator.
  version     Print the version of Kompose

Flags:
      --error-on-warning    Treat any warning as an error
  -f, --file stringArray    Specify an alternative compose file
  -h, --help                help for kompose
      --provider string     Specify a provider. Kubernetes or OpenShift. (default "kubernetes")
      --suppress-warnings   Suppress all warnings
  -v, --verbose             verbose output

Use "kompose [command] --help" for more information about a command.

unknown flag: --askldfjsdf

~                                                                                ⍉
▶ echo $?
255


[help wanted] CANopenNode 1.3 cannot use the CO_OC.c&h files genratoed by CANopenEditor

Using CANopenNode v1.3/examples/IO.eds to genrate CO_OC.c&h files.
I have tried using CANopenEditor and libedssharp, but they don't work.
For CANopenEditor v0.8，the generated CO_OD.h file is missing the definiton of COB_ID_TIME.
For CANopenEditor build, the generated CO_OD.h file is missing the definiton of timeOfDay_t.

CANopenNode v1.3 b92b4bb(https://github.com/CANopenNode/CANopenNode/releases/tag/v1.3)
CANopenEditor build branch(https://github.com/aerospacesoftware/CANopenEditor/tree/build)
libedssharp 0.8 Release(https://github.com/robincornelius/libedssharp/releases/tag/v0.8)

What I also want to know is whether the CO_OD.c&h file under CANopenNode v1.3/examples/ is generated by the old generator? Where can I find this tool?

We are using v1.3. The last editor update we did is to 2e53b. I don't know at which version v1.3 Support was dropped, but this one works for me. You need to compile this from the source.
With this version, you can use insert profile -> DS301 profile.xml. This contains register 0x1012, which when enabled triggers the export for COB_ID_TIME and the missing struct. Be aware that the "enabled" feature (and some more) works only if you save with "file -> export device file -> "CANopenNode XML" in this old version.

We are using v1.3. The last editor update we did is to 2e53b. I don't know at which version v1.3 Support was dropped, but this one works for me. You need to compile this from the source.
With this version, you can use insert profile -> DS301 profile.xml. This contains register 0x1012, which when enabled triggers the export for COB_ID_TIME and the missing struct. Be aware that the "enabled" feature (and some more) works only if you save with "file -> export device file -> "CANopenNode XML" in this old version.

Thank you sooo much, it works in using _project.xml file.

Why don't  consider supporting v1.3 in CANopenEditor as well? After all, v1.3 is the latest version in Release.
@trojanobelix @CANopenNode

I myself only use V1.3. I am not aware of any problems with the CANopenEditor when using V1.3.
Sure that you using the actual editor from https://github.com/CANopenNode/CANopenEditor?

I'm sorry, I use CANopenEditor is from https://github.com/aerospacesoftware/CANopenEditor/tree/build.
When I try to use https://github.com/CANopenNode/CANopenEditor/tree/4.0-104-g6f50f73 to open the _project. XML and insert DS301_profile_old to generatethe CO_OD.c/h file, but the compiler still fails to compile successfully, showing a missing definition of timeOfDay_t.
By the way, the CO_TIME.h file in v1.3 release version (b92b4bb) does not define timeOfDay_t.
Perhaps you are using v1.3 c49f119?

I myself only use V1.3. I am not aware of any problems with the CANopenEditor when using V1.3.
Sure that you using the actual editor from https://github.com/CANopenNode/CANopenEditor?
I do not use the CO_NO_TIME feature, but as far as I see comes the timeOfDay_t from CANopenNode:
CO_TIME.h #ifndef timeOfDay_t typedef union { unsigned long long ullValue; struct { unsigned long ms:28; unsigned reserved:4; unsigned days:16; unsigned reserved2:16; }; }timeOfDay_t; #endif`
The COB-ID TIME comes with Object 0x1012, when using DS_301_old profile. (in the newer Profile it is named "COB-ID time stamp object")

I'm sorry, I use CANopenEditor is from https://github.com/aerospacesoftware/CANopenEditor/tree/build.
When I try to use https://github.com/CANopenNode/CANopenEditor/tree/4.0-104-g6f50f73 to open the _project.xml and insert DS301_profile_old.xml to generatethe CO_OD.c/h files, but the compiler still fails to compile successfully, showing a missing definition of timeOfDay_t.
By the way, the CO_TIME.h file in v1.3 release version (b92b4bb) does not define timeOfDay_t.
Perhaps you are using v1.3 c49f119?


When the GA would be available ?

When the GA would be available ?

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

ID: 31806d3b-6d26-ba48-3860-559dc0938b9d
Version Independent ID: 3eccfc69-2ea4-d8ab-3299-df054a0f6a47
Content: What is Azure App Configuration?
Content Source: articles/azure-app-configuration/overview.md
Service: azure-app-configuration
GitHub Login: @yegu-ms
Microsoft Alias: yegu

@vikramdadwal Thank you for the question. Routing this to @yegu-ms to provide GA dates for the product.

Any updates ?

@vikramdadwal We're targeting mid-Oct.
#please-close

Is it postponed?

@vikramdadwal we just posted our GA and pricing plan. Please check it out.
https://github.com/Azure/AppConfiguration-Announcements/issues/2


Store asset size timeseries in Postgres rather than Redis

Storing them in Redis was using too much memory when reading the values
because the timestamps and values were stored as strings. By storing
them in a Postgres JSON array, we can leave them as integers and floats,
saving memory when reading the values. I think inserts will be a bit
slower and use more memory, but that's okay.

Changing branch name. Closing.

See https://github.com/davidrunger/david_runger/pull/1320.


Incorrect Statuses

Thank you for the plugin! I've been pondering my own NetBox plugin for a while, but I'm glad that one is officially released now.
I was wondering if the statuses are being set as intended (but maybe it's us using things differently).
In Netbox we use:

Status
Description

Active
In use

Reserved
Not in use, but reserved for future use

In Morpheus, it appears that NetBox Active is showing as Reserved in Morpheus and NetBox Reserved is showing as Static. Should this be reversed?

These were both getting set to reserved by accident.  Resolving next release.


Cleanup lib.rs

close #396

Why change the code style in the process? :huh:

I know what change code style is bad. But this file did not have single style. Also code like pub use foo::bar as bar was strange for me.


Public apps return 500 on first visit

Overview
When visiting hydrox.shopifycloud.com for the first time you will see a internal server error page due to the missing session cookie on the initial load.
More information given when loading the app locally incognito:
React server-side rendering error:
Error: Network error: Error writing result to store for query:
 {"kind":"Document","definitions":[{"kind":"OperationDefinition","operation":"query","name":{"kind":"Name","value":"ProjectListQuery"},"variableDefinitions":[],"directives":[],"selectionSet":{"kind":"SelectionSet","selections":[{"kind":"Field","name":{"kind":"Name","value":"projects"},"arguments":[],"directives":[],"selectionSet":{"kind":"SelectionSet","selections":[{"kind":"Field","name":{"kind":"Name","value":"title"},"arguments":[],"directives":[]},{"kind":"Field","name":{"kind":"Name","value":"id"},"arguments":[],"directives":[]},{"kind":"Field","name":{"kind":"Name","value":"__typename"},"arguments":[],"directives":[]}]}}]}}],"loc":{"start":0,"end":53,"source":{"body":"query ProjectListQuery{projects{title id __typename}}","name":"GraphQL request","locationOffset":{"line":1,"column":1}}},"id":"84ca953fd60792db1dfaa69ace54fde92586ed98150b0f2d86f1bd7c67077b11"}
Cannot read property 'projects' of undefined
    at new ApolloError (/Users/mattseccafien/src/github.com/Shopify/hydrox/node_modules/apollo-client/bundle.umd.js:92:26)
    at /Users/mattseccafien/src/github.com/Shopify/hydrox/node_modules/apollo-client/bundle.umd.js:1587:34
    at /Users/mattseccafien/src/github.com/Shopify/hydrox/node_modules/apollo-client/bundle.umd.js:2007:15
    at Set.forEach (<anonymous>)
    at /Users/mattseccafien/src/github.com/Shopify/hydrox/node_modules/apollo-client/bundle.umd.js:2005:26
    at Map.forEach (<anonymous>)
    at QueryManager.broadcastQueries (/Users/mattseccafien/src/github.com/Shopify/hydrox/node_modules/apollo-client/bundle.umd.js:2003:20)
    at /Users/mattseccafien/src/github.com/Shopify/hydrox/node_modules/apollo-client/bundle.umd.js:1482:29
    at process._tickCallback (internal/process/next_tick.js:68:7)

Fixed by following quilt_rail's CSRF guide.


  See #14 for what changes should be made.

Awesome @jwokaty !!!


Move from OkHttp to JDK HTTP client

The Kubernetes Config Provider currently still uses the OkHttp 3 as the HTTP client which has CVEs. This PR changes it to use the JDK HTTP client to remove the OkHttp dependency.

Not clear from the PR but I guess that with the new Kube client , the Java SDK HTTP client is now the default one.

It uses what it has in the Maven dependencies. I'm not entirely sure why we had the client factory there TBH.


V13

Codecov Report

Merging #154 (59cf14f) into main (85c860b) will increase coverage by 0.06%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             main     #154      +/-   ##
==========================================
+ Coverage   63.86%   63.93%   +0.06%
==========================================
  Files          60       60
  Lines        1832     1830       -2
  Branches      245      244       -1
==========================================
  Hits         1170     1170
+ Misses        575      574       -1
+ Partials       87       86       -1

Impacted Files
Coverage Δ

src/discordBot/services/logger.js
29.41% <50.00%> (+3.09%)
: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 85c860b...59cf14f. Read the comment docs.


[NFR]: Add FilterTrait

Add Filter trait to allow array filtering based on passed parameters

Resolved in 54aacd4e578a28f368256d52185de95ea8e50966


from future import division

Really nice package, thanks for all the great work.
When I try to use
from __future__ import division
it breaks. Any chance of fixing this? I think it would basically require implementing __truediv__ for a few classes.

Thanks for raising this issue.  This also brings us closer to supporting Python 3.


Does the minifier work for DOTLESS ?

Its a question not an issue. Does the minifier work for less styling files compiled with DOTLESS?
If yes how can you use it for this case?
For example if you use a Bootstrap theme you will get through DOTLESS/../...Bootsrap.css which is not minified.
Can that file minified with this plugin?

Any CSS file can be minified. We try to minify as little as possible so most CSS files will not result into issues.


[Github app]: [Timebox 4h] AANewUser I can add my repo to the app.

Description

We know how to install the app and get reviews. What we don't know how to do is add the repo to a user of the app in the db. This is important so we can use the users API key and track requests etc...
I am guessing that we will receive a webhook event.
We will be using a fanout pattern to consume all the webhook events see ticket #242
We need to work oout how to filter the events and fanout to the correct lambda.
This will probably mean some manipulation of the event body in the apigateway mapping template to get the event into a pattern which can be filtered by an eventbridge filter. This ticket should work out that code.
This will allow us to create a new lambda which consumes the event which adds a new repo... whatever that event looks like (this ticket should work that out)
Expected Outcome
I know what the add new repo event looks like
I have code which can accomplish the fanout and filter pattern of apigateway to eventbridge.

Can you link to the outcomes here @lizacullis. I dont have anything to FR

Outcomes:
#242  Updated ticket to reflect what we needed to do.
#265  Created this tickect to get the filtering working
Rough thoughts that I put down in notion while I was doing this ticket:
https://www.notion.so/m33/184-AANewUser-I-can-add-my-repo-to-the-app-73de211e17824e4ab5329d31ad3b5413


Water Sensors- BRW

This site has been down since 07/03/2022. Was recording pretty consistently with a few gaps in life. Low signal strength all around with nodes and gateway. Reset?

Sent this to Charles:
This field site has not connected to the tech dashboard in quite some time
Print off the logs for this field from the nodes and gateway and email them to Ethan
Try resetting the nodes and gateway to see if that resolves the issue


Tool for prototyping TypeScript types faster

Currently, it's very difficult to develop / debug complex types and there seems to be no official tool for prototyping, or not one the community is aware of.

Copy pasted from StackOverflow
https://stackoverflow.com/questions/58500139/tool-for-prototyping-typescript-types-faster
Is there an online tool, IDE or VSCode settings option/extension that allows to prototype type definitions (easier/faster)?
The only option I am aware of is to hover over a typed statement which displays the associated type in a tooltip. It's very impractical to use as the types are trimmed and non-interactive, i.e. I cannot hover over a type sub-component to see the trimmed part. Also it's impossible to say which sub-type failed as it's not highlighted.

If I need to step through a complex type to discover the error, I have to deconstruct it like below and then keep hovering over each statement, which is very inconvenient. Maybe if only the IDE could generate those "result comments" automatically, that would make life easier.

For example: https://marketplace.visualstudio.com/items?itemName=sokra.ts-inline-types

Unfortunatelly this extension is very resource demanding up to the point of killing the extension host and it doesn't work with type definitions and declarations as in the screenshot. It does seem interesting though, as it names the function parameters.
It think the VSCode's inherent feature should at least be little more friendly than it is now. Can we at least somehow get the full message from the tooltip and get what's hidden under all those <...>? Creating extension just to expand the trimmed parts seems like an overkill to me.
If I hover over an interface in the tooltip, I would also like to see the properties or be able to click on a name and go to definition.


Packaged app not running on raspberry. No output.

[ x] I have read the contribution documentation for this project.
[ x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

The application packaged with packager does not start on Raspberry Pi 3.
No output while starting the app.
Packaged with
electron-packager . --platform=linux --arch=armv7l
Victor

Console output when you run electron-packager with the environment variable DEBUG=electron-packager. Please include the stack trace if one exists.
Put the console output here

What command line arguments are you passing? Alternatively, if you are using the API, what
parameters are you passing to the packager() function?
Put the arguments or parameters here

Please provide either a failing minimal testcase (with a link to the code) or detailed steps to
reproduce your problem. Using electron-quick-start
is a good starting point.

Thanks for filing an issue! In order to help you with your problem, we're going to need more information about it. In particular:

Please provide either a failing minimal testcase (with code) or detailed steps to reproduce your
problem. Using electron-quick-start is a good starting point.

It would help to know what distro, distro version, and desktop environment you're running on your Raspberry Pi 3, along with the output of uname -m to make sure that the arch is correct.
Also, is there any console output if you try to run the Electron app via a terminal window?

Its armv7l. No console output at all :( so I could not identify an issue. I have neither electron nor nodejs, chromium installed on the machine as I think, they all are packed to the release, don't they?
I packed all these on MAC OS and just copied to raspberry. I'm not sure, what am I doing wrong and googling did not give too much. The goal is to pack the app on MAC OS and deploy the release to raspberry with other dependency to be deployed.
Here is console output:
username@RB05:~/electron/assistant-linux-armv7l $ ls -l
total 95444
-rw-r--r-- 1 username raspberry     1060 Nov 20 22:26 LICENSE
-rw-r--r-- 1 username raspberry  1775951 Nov 20 22:27 LICENSES.chromium.html
-rwxr-xr-x 1 username raspberry 55462456 Nov 20 22:26 assistant
-rw-r--r-- 1 username raspberry    24844 Nov 20 22:27 blink_image_resources_200_percent.pak
-rw-r--r-- 1 username raspberry       15 Nov 20 22:26 content_resources_200_percent.pak
-rw-r--r-- 1 username raspberry 12032534 Nov 20 22:26 content_shell.pak
-rw-r--r-- 1 username raspberry 10130560 Nov 20 22:27 icudtl.dat
-rw-r--r-- 1 username raspberry  2002296 Nov 20 22:27 libffmpeg.so
-rwxr-xr-x 1 username raspberry 14323560 Nov 20 22:26 libnode.so
drwxr-xr-x 2 username raspberry     4096 Nov 20 22:27 locales
-rw-r--r-- 1 username raspberry   262947 Nov 20 22:27 natives_blob.bin
-rw-r--r-- 1 username raspberry   140979 Nov 20 22:27 pdf_viewer_resources.pak
drwxr-xr-x 3 username raspberry     4096 Nov 20 22:27 resources
-rw-r--r-- 1 username raspberry  1315500 Nov 20 22:27 snapshot_blob.bin
-rw-r--r-- 1 username raspberry   151829 Nov 20 22:26 ui_resources_200_percent.pak
-rw-r--r-- 1 username raspberry        6 Nov 20 22:27 version
-rw-r--r-- 1 username raspberry    57761 Nov 20 22:26 views_resources_200_percent.pak
username@RB05:~/electron/assistant-linux-armv7l $
username@RB05:~/electron/assistant-linux-armv7l $
username@RB05:~/electron/assistant-linux-armv7l $ uname -m
armv7l
username@RB05:~/electron/assistant-linux-armv7l $ sudo ./assistant
username@RB05:~/electron/assistant-linux-armv7l $

Why are you trying to run it via sudo?
It would help to know what distro, distro version, and desktop environment you're running on your Raspberry Pi 3.

Its actually no matter, "sudo" or not. it does not run either.
I have no desktop environment, just CLI. No GUI.
Here is all other info:
username@RB05:~/electron/assistant-linux-armv7l $ ./assistant
username@RB05:~/electron/assistant-linux-armv7l $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
username@RB05:~/electron/assistant-linux-armv7l $ lsb_release -a
No LSB modules are available.
Distributor ID:	Raspbian
Description:	Raspbian GNU/Linux 8.0 (jessie)
Release:	8.0
Codename:	jessie
username@RB05:~/electron/assistant-linux-armv7l $ uname -a
Linux RB05 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
username@RB05:~/electron/assistant-linux-armv7l $ uname -r
4.9.35-v7+
username@RB05:~/electron/assistant-linux-armv7l $ uname -a
Linux RB05 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
Victor

Your problem is that Electron requires an X session running on Linux.


Inconsistent definitions error

Building on Mac (but could also simply be a highs version issue?)
brew install pkg-config
brew install highs

$ pkg-config highs --cflags --libs
-I/opt/homebrew/Cellar/highs/1.7.2/include/highs -L/opt/homebrew/Cellar/highs/1.7.2/lib -lhighs

Installing highs go package:
$ go install github.com/lanl/highs
# github.com/lanl/highs
cgo: inconsistent definitions for C.kHighsObjSenseMinimize
cgo: inconsistent definitions for C.kHighsHessianFormatTriangular
cgo: inconsistent definitions for C.kHighsObjSenseMaximize

I looked into this, and it appears that it's not a HiGHS version issue but rather a GCC vs. Clang issue.  Clang, which is the default compiler on Mac, seems to be more pedantic than GCC.  I compared GCC 13.2.0 and Clang 18.1.3, both on Ubuntu 24.04.  go build (GCC) works, but env CC=clang go build (Clang) gives the same "inconsistent definitions" errors you report above.
I believe I can fix the problem by redeclaring all of the HiGHS variables and functions instead of using the HiGHS header files directly.  Stay tuned…

Now it works, thanks @spakin !


ngrok ERR_NGROK_702 Too Many Connections

Cant open jupyterlab because of this

I am about import kora.install.py38

Hi @kinivi , I also had the same error, try this:

Create an account at grok.com
Then you copy your autotoken
Create a new colab notebook and run:

!pip install colabcode
authtoken='here your ngrok authtoken'
import colabcode as cc
cc.ColabCode(port = 10000,  lab = True , authtoken=authtoken, mount_drive=False)

Credit: https://github.com/abhishekkrthakur/colabcode


[BUG] WPF SKElement does not call PaintSurface when inside a Panel

WPF under Windows 10.
I have this layout
Window -> WrapPanel -> UserControl -> SKElement.
With this hiearchy, the PaintSurface event attached to the SKElement never gets called.
If I pull the SKElement "one level up" (i.e. get rid of the WrapPanel)
Window -> UserControl -> SKElement
The PaintSurface event is called again.
I expected it to work, instead it is never called. Calling InvalidateVisual on the SKElement does not help either: when outside the panel it triggers a call to PaintSurface, when inside a panel it does nothing.

My bad, I was not setting dimensions! Sorry for the noise.

No prob. You will never guess how often that happens to me. And then I also forget to add the view to the window as well...


Fixed link for Virto Commerce.

E-Commerce and Payments/Virto Commerce
Fixes 301.

@dlemstra Thanks.


Response and Response Body should be clonable

Is your feature request related to a problem? Please describe.
I want to clone a Response and Response Body so that I can pregenerate them, store them in memory and then just clone and serve them when the request comes.
Describe the solution you'd like
The ability to clone Responses and Reponse Bodies

The multi-purpose hyper::Body cannot be Clone, because it may contain state that isn't cloneable. An easy solution is to have the full body in a Bytes, which is cheaply cloned and can be converted into a new body via Body::from(bytes).
A Response also cannot be Clone. See https://github.com/hyperium/http/pull/280 for history.

Uhm, this is too bad because this has some notable performance downsides.
Without setting any Headers on the Builder, Hyper is capable of delivering an incredible 300k requests per second on my machine (nginx does ~30k), but when adding multiple headers from Scratch for every request this goes down to 180k, even when reusing and cloning the HeaderMap it does not get above 233k (Don't get me wrong, this is still incredible but also quite a noticeable drop, especially as the bodies contents are quite cheaply clonable).
Body
Just sending a string:
res.body(Body::from("test")).unwrap();

287k/s
compared to cloning in the real body contents from memory
res.body(Body::from(fsmap.get(&access_path).unwrap().clone())).unwrap();

281k/s
This is quite cheap.
Headers
But sending headers:
With DOCUMENT_MAP containing ~10 headers
res.headers_mut().unwrap().extend(DOCUMENT_MAP.clone());

233k/s
compared to not sending headers
281k/s
Thank you! Hyper is awesome!

You could skip the clone, and just .extend(&DOCUMENT_MAP), I think. That should save a bit of allocations.

Thank you for the suggestion but this doesn't work.
&DOCUMENT_MAP` is not an iterator the trait `std::iter::Iterator` is not implemented for `&DOCUMENT_MAP

Perhaps calling the .iter() method.


fix: Fix indexmap compatibility for yew 0.21.0 (#3659)

Description
Fix conversion from IndexMap to IMap in IntoPropValue implementation
This PR addresses an error in the IntoPropValue implementation for IndexMap to IMap conversion. The original code used IMap::from(self), which failed because there's no direct From implementation for IMap from indexmap::IndexMap.
Changes made:

Replace IMap::from(self) with IMap::from_iter(self)

Rationale:

from_iter utilizes the FromIterator trait to construct an IMap from an iterator.
IndexMap implements IntoIterator, allowing it to be used with from_iter.
This approach avoids the need for a direct From implementation between IMap and IndexMap.

The change resolves the compilation error and provides a more flexible conversion method using existing trait implementations.

This change may not directly resolve the Issue, but at least it resolved a similar error that was occurring in my environment
I added yew to the dependencies package,
yew = { version = "0.21", features = ["csr"] }

I added yew to the dependencies package, and ran into the error in this Issue when I did a simple HTML build to see how it worked.
Here is the code of main.rs at that time.
use yew::prelude::*;

#[function_component(App)]
fn app() -> Html {
    html! {
        <h1>{ "Hello World" }</h1>
    }
}

fn main() {
    yew::Renderer::<App>::new().render(); }
}

Fixes #3659
Checklist

[x] I have reviewed my own code
[ ] I have added tests

Incidentally, CI is making errors in areas unrelated to my changes, but I have not done anything special about this since it is not causally related to this issue.

This error is a result of implicit-clone, a daughter crate of Yew, trying to support both indexmap v1 & v2
See #3659 for more discussions on this, and implicit-clone/#51 that will prevent this from happening in future Yew versions

@its-the-shrimp
thanks, I understood and close this.


Prepare for release 1.0 "Naked Chicken"

This will ultimately be the first release of nf-core/openmspeptidequant, "Naked Chicken".
PR checklist

[x] This comment contains a description of changes (with reason)
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If necessary, also make a PR on the nf-core/openmspeptidequant branch on the nf-core/test-datasets repo
[x] Ensure the test suite passes (nextflow run . -profile test,docker).
[x] Make sure your code lints (nf-core lint .).
[x] Documentation in docs is updated
[x] CHANGELOG.md is updated
[x] README.md is updated

Learn more about contributing: https://github.com/nf-core/openmspeptidequant/tree/master/.github/CONTRIBUTING.md

Naked Chicken - really?? 😆

Few minor things:

main.nf is missing ASCII art for the help text
nextflow.config has the standard profile twice
Most of the configs in base.config could be grouped into a couple of withLabel statements
Would be nice to harmonise the profiles a bit with the base template (add uppmax, add zurich to the template)
Nextflow throws a warning:

WARN: The operator `first` is useless when applied to a value channel which returns a single value by definition -- check channel `id_files_merged_psm_perc_filtered`

Strange minor markdown rendering bug in docs:

num_threads is documented (and here) and in nextflow.config but not used in main.nf
Docs don't describe several profiles

Generally looking really good though!
Phil

Naked Chicken - really?? 😆

Yes, @Leon-Bichmann had the idea, not my choice :-D

All points mentioned by @ewels addressed now:

ASCII Art added
got rid of the first() statement which was unnecessary
Added documentation fixes for markdown rendering issues
Added Docs for Profiles present atm (others will come via Sync)
Submitted separate PR to tools for having more profiles there (e.g. UZH, also introduced sorting there in the PR)
Removed redundant resource statements in the base.config, these are now defaults

Only resource requests bigger or smaller get their own labels now

Got rid of num_threadswhich isn't used at all in the pipeline anymore

Complete rename solved :-)

The openms version in the environment spec must be openms=2.4.0

Had to adapt the test-datasets first, now this works.

anything missing still for the chicken to leave the nest?

A review by @ewels for example ;-)

I think this is fine, will merge to dev atm


Specify Swift version in podspec

This helps when using AlamofireImage on a Swift 4 project in Xcode 10.
Goals :soccer:
When using AlamofireImage from CocoaPods in Xcode 10, the Swift version will be set properly and building succeeds.
Implementation Details :construction:
This just adds the swift_version attribute to the root-level pod spec. There’s also a .swift_version file, but CocoaPods doesn’t look at that when creating its Xcode project (perhaps this could be an enhancement to CocoaPods).
Testing Details :mag:
To test this, create a new project in Xcode 10 and add AlamofireImage using CocoaPods. The release version will fail, but this version will succeed.

Unfortunately we can't accept this, as AFI supports multiple versions of Swift and locking into a single version for CocoaPods users could create incompatibilities where AFI works fine.


Collection Name not supported by VirtualizedList

Description
Collection Name not supported by VirtualizedList. No components can be set as any collection role. With support for "List" or "Grid" roles would these would likely work as expected.
This issue is covered in-depth by parent issue #30972, please check there for more details.
React Native version:
v0.63

Hey! @amarlette can i have a look at this issue?

This was fixed in #31630 and verified here https://github.com/facebook/react-native/issues/30972#issuecomment-1192399980


allow use for proxy

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've been mindful about doing atomic commits, adding documentation to my changes, not refactoring too much.
[x] I've a descriptive title and added any useful information for the reviewer. Where appropriate, I've attached a screenshot and/or screencast (gif preferably).
[x] I've written tests to cover the new code and functionality included in this PR.
[x] I've read, agree to, and signed the Contributor License Agreement (CLA).

PR Summary
Allow use for proxies when creating websockets and calling slack apis.
This PR didn't change the user end docs, just the API docs, which I don't think is being shown anywhere on the docs, but the FAQ says I have to re-compile the docs if I added any docs. I'll revert the docs change or put them in a separate commit if in need.
Related Issues
None
Test strategy
I'm not sure how to test this feature.
Motive
I'm using python-slackclient in China so I'm very interested in proxy functionalities in slack client, there's a old PR solving the same problem but I don't think @pfrederiks have time to continue the work, so I copied a few lines of code and create a separate PR.

 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.

Sorry to bother, but travis fails under TOX_ENV=flake8, and I'm not sure how to reproduce on my local environment, to fix this issue.
Could you take a look and determine whether it's my mistake? Because travis builds pass without error on other TOX_ENVs.
@Roach

@timfeirg sorry for the delay. I'm looking into this now, we'll see if we can get this merged today or tomorrow.

@timfeirg we might also want to consider Web API proxy support for this, as this change is limited to RTM (websocket) proxy 🤔

Request for comment  @Roach

bugs and other issues suggested by @nooperpudd had been fixed

@timfeirg can you add a simple test for proxy parsing? That should bump up the Codecov score enough to allow merging 🎉

I've add tests to ensure the proxies gets passed correctly between SlackClient, SlackServer and SlackRequest, and that the proxies actually gets used. @Roach

any updates? @Roach


Incorrect information regarding View-only capabilities for Webinars

Please remove the line that says
-Participants over 1,000 up to 20,000 have View-only capabilities
As currently this is not yet possible.
Thanks
Jorge
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 92fcb1f6-5cc2-f6bd-cfa9-11d811f1dbf1
Version Independent ID: 9a571e6d-8cb3-9ff8-a5c2-62deab146264
Content: Quick start - Meetings, webinars, and live events - Microsoft Teams
Content Source: Teams/quick-start-meetings-live-events.md
Service: msteams
GitHub Login: @CarolynRowe
Microsoft Alias: crowe

@JorgeALeitao Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@dariomws @scanum  Please do not make any changes to this article.  The limits were approved and signed off by several PMs.  I will follow up with those PMs regarding this issue.

@dariomws @scanum Please do not make any changes to this article. The limits were approved and signed off by several PMs. I will follow up with those PMs regarding this issue.

@CarolynRowe , given that Siunie agreed to my suggestion will you give green light to update the doc article? Thanks!

The article update is already live:  https://docs.microsoft.com/en-us/microsoftteams/quick-start-meetings-live-events

Closing this issue.  Thank you, Jorge, for the feedback.


Cannot install Kubevirt on minikube cluster

What happened:
While trying to deploy KubeVirt on minikube (WSL), Error 404 was being reported on the terminal window! Suspect a Broken Link!

What you expected to happen:
KubeVirt getting deployed on minikube and we are able to see deployments, services, daemonset etc deployed by KubeVirt

@itsaviral2609  first you need to set the VERSION with this command
export VERSION="v0.59.0"
,then enter the create command

kubectl create -f https://github.com/kubevirt/kubevirt/releases/latest/download/kubevirt-operator.yaml
kubectl create -f https://github.com/kubevirt/kubevirt/releases/latest/download/kubevirt-cr.yaml
you can use this it solved my problem i was facing the same issue

@shivangnayar-crypto @Vikash993468 Thanks for helping me out!
Going to close this one!


Create mock object for layer information

Create a mock object with the information that should appear on the sidebar right information panel.

This is not needed, because the layers are already loaded.  Map rendering will break though, when geoserver is unreachable


how to use 'populate where' in route

I have two model User and address ,  it is One to Many
Use route /use  ,The result is the list of User contain address like below.
{
"address": [
{
"city": "zh",
"detail": null,
"owner": 7,
"id": 4,
}
],
"name": "刘兴",
"password": null,
"email"<EMAIL_ADDRESS>"id": 7,
"createdAt": "2014-11-12T09:43:15.000Z",
"updatedAt": "2014-11-12T09:43:53.000Z"
}

But ,I need to disable config blueprints.js
populate: false,

So, req route become http://localhost:1337/user/?populate=address
The result is exact
But, I want get the users what's address attr  {city:'changsha'}
User.find({name: 'mx'}).populate('address',{city:'changsha'})

How can I release it the by edit route url ?
More than,  get the User's address list ,  address name equal changsha

/user/?populate=['address']


feature_timeline

James will be adding dates. See how the timeline could be resurrected or a different ways of visualising dates could be implemented.

Timeline will not be part of the public engagement demo, and doesn't really provide useful information at the moment. Feature is being discarded.


plan to replace golang_org package

I suggest to use forks of

https://github.com/golang/net
https://github.com/golang/crypto
https://github.com/golang/text

with patches from vendor/golang_org and the possibility of go module to replace dependencies as here
https://github.com/kamilsk/lift/blob/3d70617c288acc83b6bf5e330dd3a3fcb25a2170/go.mod#L10
The final go.mod may looks like
require (
	golang.org/x/crypto ...
	golang.org/x/net ...
	golang.org/x/text ...
)

replace golang.org/x/crypto => github.com/Lookyan/crypto v0.0.1-patch
replace golang.org/x/net => github.com/Lookyan/net v0.0.1-patch
replace golang.org/x/text => github.com/Lookyan/text v0.0.1-patch

It will make possible to close #35, show difference between patched versions and upstream, fix go get -u to update deps (when vendor/golang_org disappears)

I can take care of routine: create forks and branches with patches, etc

I hope fasthttp will eventually replace the current fork of stdlib. But yes, for now, we can handle it in a better way.
Not sure we need to do it right now, but if you think it is handy you can do it.

fixed by bc4947a


[mach] Make section_by_name support loading sections starting with dot

For example .rustc used to be replaced with __rustc before searching, which meant .rustc was not findable
cc https://github.com/bjorn3/rustc_codegen_cranelift/pull/435

I think this is good (and I'd actually prefer if we got rid of this hack completely, but that's liable to break things). But maybe you should be naming the section __rustc in the first place for Mach-O? Not sure what the llvm backend does.

Coverage remained the same at 0.0% when pulling f2012af98bd25630709cef11ba6395ab1d2faf8c on bjorn3:patch-1 into 10be0ee1b41338f36c49a47799d7674fefbe5452 on gimli-rs:master.

The llvm backend uses .rustc for all platforms.


arm64 support

Describe the enhancement
Many of the addons don't provide arm64 images. Please consider providing arm64 images.

cc @zhujian7 @xuezhaojun

/assign @zhujian7 for managed-serviceaccount
will create another one for cluster-proxy @xuezhaojun

Hi, @tamalsaha I checked the repos of cluster-proxy and MSA and saw there are already arm64 images exist, is there any extra support you need in this case?
https://quay.io/repository/open-cluster-management/cluster-proxy?tab=tags
https://quay.io/repository/open-cluster-management/managed-serviceaccount?tab=tags&tag=latest

/close
seems this has been done.


OS X Port

Given that Arnold, Maya and Python are available for OS X, the current windows+linux restriction should only apply to Softimage. i.e. for Arnold, Maya and Python, it should just be windows+non-windows.

Could anyone with a successful build process for OS X share their method with me? I am trying to modify the Unix method for our OS X environment.

Could anyone with a successful build process for OS X share their method with me? I am trying to modify the Unix method for our OS X environment.


Add more operations

This is a nice, mutable Interval Tree implementation. I was hoping for more operations (especially mutating ones), as in this Python library: https://github.com/chaimleib/intervaltree
In particular, I was interested in chop (trim/remove nodes intersecting with an interval), which I think requires a bunch of other functionality.

Hi @BrettWitty!
I have no immediate plans to implement mutable operations other than insertion, but I'll consider it for the future. The application in which I wrote this library strictly uses it for lookups after build.


Update system-dependencies.R

Checks on r-pkg-template https://github.com/insightsengineering/r.pkg.template/pull/146
checks on teal https://github.com/insightsengineering/teal/pull/809
Checks on my account  https://github.com/arkadiuszbeer/r.pkg.template/actions/runs/4344934153/jobs/7588942876


Pan chart programmatically

Is there a way to move the enlarged graph by clicking the buttons I created (back, forward), as if I were using a pan tool?

I found a similar issue


school library set

~Implementation of classes and objects in Ruby.
~Implementation of  encapsulation and inheritance with Ruby.
~correct gitflow

all requested changes have been made


Fix per gram calculation

Reference values are always per 100g, not per 1st serving value.
You can check it yourself, compare the values with what google finds about their nutrition.

This would defeat the purpose of setting the serving size on foods. Please explain the bug this fixes, the steps to re-produce and what you expect to happen.

Whether it defeats or not, the calculation is not correct now. I updated the starter of the conversation with an example.

Sorry, here is the third screenshot to understand the issue

As you see, when we input 100 grams, the data doesn't match the reference values I showed before

Your above example doesn't look like a bug to me. You set your food to be 61 calories per 244 grams, then you entered 100 grams.
61 / 244 = 0.25
0.25 * 100 = 25

I don't set my food. That's the database that you provide with the App. And this database contains nutrition facts per 100 g, not per first serving size.

So the way you calculate nutrition facts per gram now, it's always returning incorrect values for the whole database except for items where 1st serving size is 100g

Oh I see what happened now it's because I've conflated these new fields with the old ones

I need to add a new field for the user specified serving size, and move this MyFoodData field serving weight back below with the other fields, then it defaults to 100 if the user hasn't specified a serving size.

I will be happy with any solution that fixes the App!

Sadly this will make some peoples entries incorrect if they took a version of the app with this bug and started editing the servingWeight1G field, this will however fix all the built-in foods which there are so many it's worth doing.


Migrate serialization extensions to new project

Migrate the Id3.Serialization package code to the new netstandard2.0 project.

[x] Fix any errors
[x] Update language features to C# 7.2
[x] Code clean-up and optimization

Closed with 34426c2b15addb57a55b39a5944d17e63b84aeb6


Add Q (kdb+).

Have I found the right Wiki entry for this language?
https://en.wikipedia.org/wiki/Q_(programming_language_from_Kx_Systems)#Examples
'Cause if I have it looks like the -1  in your HW isn't needed.
NB: Following links to the "tutorial" makes me think of this.

It's APL based language, it's far from brainf__k :)  More docs available at http://code.kx.com/q/.
-1 prior to "Hello World" meant to send output to stdout, which I personally prefer. In this case, you're looking for simplest example.

APL Based

Now you mention it I do see the similarity; and of course that explains why it reminded me of BF. :smile:
APL is a quite limited language in that you are constrained to work within it's usual patterns. Unlike BF it works well within those limitations but once you hit the limit is very difficult to get any further (like BF). If you don't like the BF comparison the DC language works too; it's a full Turing complete language and can do "anything" but pushing to past it's normal limits is nasty.


📖 Removed "Third," (typo?)

What type of PR is this?
/kind documentation     Adds documentation.
What this PR does / why we need it:
fix typo.

Thank you very much! Please add :book: at the beginning of the PR title

Thank you very much! Please add :book: at the beginning of the PR title

does the title fit your needs now?


Contains

I kinda was expecting this to not pass
  const wrapper2 = shallow(<Button>Hello
Goodbye
</Button>);
  const expectedChildren = [
    wrong,

Goodbye

  ];

  t.ok(wrapper2.contains(expectedChildren), 'should render children');

Any thoughts?

whoa.  I'd call that a bug.

workarounds:
  const expectedChildren = [
    bye,

Goodbye

  ];

  t.deepEqual(wrapper2.props.children, expectedChildren, 'should render children');

  t.ok(wrapper2.contains(Hello), 'should render children');
  t.ok(wrapper2.contains(
Goodbye
), 'should render children');

Maybe it's fine that contains only accepts single nodes?

@SeeThruHead Yeah. I'm not sure what contains would actually do when passed an array... I don't think the case is ever handled specifically so I'm not sure what it actually does in that case.

Looks like it will try to compare the array to every node using nodeEqual from './Utils'
I'll take a look at it later to see if I can figure out why nodeEqual(Array, Node) is passing.

@SeeThruHead I believe I've fixed this ^^. Thanks for reporting the bug!

Awesome thanks a lot @lelandrichardson


move singleton to classes's annotations

This patch refactors the Guice uses, and mainly move all singleton binding to respective classes with singleton annotations. The corresponding tests are added as well. a bit more context is at #1285 .

Thanks for making this change!

@suvodeep-pyne ExecutorManager code needs to do a save-action refactor before changing guice. Others in azkaban-common module were all added. Web and Exec refactor will be in a separate PR.

I just realized Jamie should be working on ExecutorManager code, so I'm just adding the annotation on top of this class, but would not refactor.

@suvodeep-pyne @HappyRay updated the PR again. Any more comments?


Trie + leveldb integration for on-chain logging/storage

Txn pool / blocks exchanged are all in memory at the moment. This should follow the paradigm of file storage drivers such as leveldb

Can refer to ethereum code tx_joural.go https://github.com/ethereum/go-ethereum/blob/master/core/tx_journal.go, it provide a file strorage driver to txs.


GetInstrumentsAsync missing variables

{"alias":"","baseCcy":"","category":"1","ctMult":"1","ctType":"inverse","ctVal":"100","ctValCcy":"USD","expTime":"","instFamily":"BTC-USD","instId":"BTC-USD-SWAP","instType":"SWAP","lever":"125","listTime":"1611916828000","lotSz":"1","maxIcebergSz":"100000000.0000000000000000","maxLmtSz":"100000000","maxMktSz":"10000","maxStopSz":"10000","maxTriggerSz":"100000000.0000000000000000","maxTwapSz":"100000000.0000000000000000","minSz":"1","optType":"","quoteCcy":"","settleCcy":"BTC","state":"live","stk":"","tickSz":"0.1","uly":"BTC-USD"}
Some variable are missing when using GetInstrumentsAsync.
maxIcebergSz, maxLmtSz, maxMktSz, maxStopSz, maxTriggerSz, maxTwapSz
Could you add those variables?

Fixed in https://github.com/burakoner/OKX.Api/commit/7ce8234eeda11ba61241da68d2dce5efdf1e7796 and https://www.nuget.org/packages/OKX.Api/1.0.6


Make uploading recursive in ssh native

This tries to fix #889
scp -r does not work here, because upload() receives only files (not directories), so I've fixed it using mkdir -p before the scp.
In order to improve performance, I've used a simple caching system with the private property mkdirs. Maybe it's not the ideal solution but I couldn't find anything better.

I think it's possible to implement with some new interface, like Server\RecursiveUploadEnabledInterface. And then checking to $server instanseof RecursiveUploadEnabledInterface and do $server->uploadDirectory(...).
@oscarotero can you improve this part here? New PR?

Yes, PR created: #908 🎉


Starter kit DRS does not use https or port 443

The starter kit use of port 5000 for DRS servers does not conform to the following in the DRS 1.2 spec:

The protocol is always https and the port is always the standard 443 SSL port. It is invalid to include a different port in a DRS hostname-based URI.

See DRS URIs.
Acknowledging that there is a practical problem here, that for starter/demo/tutorial purposes the implementation https may distract from learning about DRS itself. Perhaps the DRS spec should allow for this usage of a port other than 443.

yes, that makes sense. We will update the documentation with this note. Should we also bring this up in the DRS specification repository?


[WIP] fix(ChatMessage): chat message focus is overlaying message actions in Teams theme

Fixes https://github.com/stardust-ui/react/issues/1609

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS


HappyPack not working when loaders is a Array of one item

This code not working when IS_PROD === true.
    {
        test: /\.jsx$/,
        loaders: IS_PROD ? ['babel'] : ['react-hot', 'babel'],
        happy: {id: `jsx-${name}`},
        exclude: /node_modules/
    }

But this code working fine
    let jsxLoader = {
        test: /\.jsx$/,
        happy: {id: `jsx-${name}`},
        exclude: /node_modules/
    };
    if (IS_PROD) {
        jsxLoader.loader = 'babel';
    } else {
        jsxLoader.loaders = ['react-hot', 'babel'];
    }

Are you sure it's not a cache issue? Are you providing IS_PROD in your cacheContext? If you can explain how it's not working I can provide more help.

@amireh I'm sorry, I can not reproduce


Factories stub the figgy_uuid; rename from source_metadata_identifier

It looks like we were initially using the source_metadata_identifier as the filename for these fixtures, but at some point moved to using the uuid and now the label is misleading.

Coverage remained the same at 100.0% when pulling 72b963755c799b754c22981f35385bb974e9fc7f on iiif-resource-stubs into 2877262a60045b85546677e6c90e508bd992c825 on master.


langchain[patch]: Add possibility to rerank retrieved docs in ParentDocumentRetriever

With many documents from the vector store that are passed to LLM, final answers sometimes consist of information from
irrelevant documents, making it less precise and sometimes incorrect. Also, passing multiple irrelevant documents makes it
more expensive.
So there are two reasons to use rerank - precision and costs.
Side note: there is currently Cohere SDK error on some environments with new Node/Next - https://github.com/cohere-ai/cohere-typescript/issues/136. It should be solved in the upcoming release of Cohere SDK.

Really sorry for the delay - I don't think I'll have time to implement this for Cohere soon.
If you'd like, we can remove the docs/example and get this merged sooner?

@jacoblee93 Sounds perfect. I've removed examples. Regards!

Hi really sorry for the delay - @bracesproul or I will address this on Monday now that DocumentCompressor is in core

Hi really sorry for the delay - @bracesproul or I will address this on Monday now that DocumentCompressor is in core

Fantastic!

@jacoblee93 I've refactored the above code, and now it's document compressor agnostic so you can use Cohere reranking (as shown in the example) or any other solution that fit's you.
Tested on the real app using NPM library Patch Package.

Sorry about the delay!

Thank you for your patience!

Thank you for the good work. You are awesome maintainer!


As a user with many friends, I want to be able to see all my friends' birthday in a list

so that I know who's birthday is upcoming

#94 #59


New Event on Button hover or click

One cool effect would be that the whole site rotates but only the target element keeps as it is, when the user hovers over it.

nice idea :+1:
but I think that a particle emitting plugin should not do such crazy effects :-D you can add that easily to your click event for example like this
@keyframes rotate {
from {
transform: rotate(0deg);
}
to {
transform: rotate(360deg);
}
}
body {
animation: rotate 2s linear infinite;
}


Fix a soundness hole

Just like Mutex<T> is only Sync if T is Send, SyncWrapper<T> should contain the same constraints.
See https://github.com/rust-lang/rust/pull/106792 for an example of how this can play out in practice.

Please see #2 and https://github.com/rust-lang/rust/pull/106792#issuecomment-1381378750 for arguments why this PR is incorrect. Can you present a counterexample? (i.e. code that typechecks but does indeed contain UB)

Closed since I can't seem to find a std counterexample.


bot goes to sleep unwanted

Hey, I wrote a bot hosted on Heroku and my problem is that the bot goes offline . I guess after 12 or 20 hours or something like that. I keep the heroku app alive with a webserive call ervery five minutes. When I check the heroku app I can confirm that the heroku app is not sleeping. Is this a comon problem? How to wake up the bot ?

this isn't a discordie problem, you would be more suited to ask on the heroku forums about ways to keep your container running.

Agreeing with Gus, this isn't an issue on discordie side and doesn't have anything to do with it(unless you're dumb and didn't turn on auto reconnecting)

Thank you for fast reply. I missed the autoReconnect feature.

Auto reconnect is still their.


Handle window.ai.[assistant|languageModel]

Hey @tomayac, this PR fixies Chrome Canary 131.0.6776.0's use of window.ai.languageModel instead of window.ai.assistant.
I verified that this WAI on my fork. Please take a look, thanks!

Please also consider updating https://docs.google.com/document/d/1VG8HIyz361zGduWgNG7R_R8Xkv0OOJ8b5C9QKeCjU0c
I can also send that request, and an offer to help, via email; +CC @kenjibaheux and @alexandrawhite

Thanks, @michaelwasserman! Appreciate the PR, and what you do in your PR is what you'd do if this were a rolled out API. The demo, though, needs to show the API always used as per the latest version, as we expect everyone to use the latest Canary while they are part of the early preview program. I'll close the PR as per this background information. It's served as a nudge, though, to fix all our other demos. I'll have a larger PR open on our "mono-repo" and will link it here if you want to follow along. Thanks again!

As promised, here's the larger overarching PR: https://github.com/GoogleChromeLabs/web-ai-demos/pull/69.


when_all/split: operation state might get prematurely destroyed when child completes synchronously inside its stop callback

I may have stumbled across a nasty lifetime issue in the handling of stop callbacks in the when_all/split algorithms. But this would apply to any algorithm using a inplace_stop_source inside its operation state.
when_all has a inplace_stop_source inside its operation state, and then a stop callback, like this:
struct when_all_opstate {
    // ...
    inplace_stop_source stop_src{};
    // ...
    optional<stop_callback> on_stop{nullopt};
    // ...
};

In on_stop, a stop callback is registered, which calls stop_src.request_stop() when there is a stop request on the receiver's stop token. All child senders of the when_all are registered on the stop_src. This propagates the stop request from the receiver to all children of the when_all sender.
Now, what I observed is the following chain of events:

receiver's stop token triggers
on_stop callback calls stop_src.stop_requested()
the stop_src now iterates over its list of registered stop callbacks (those are the ones from the children) (*)
the last child calls set_stopped synchronously from inside its stop callback. In my case it's from deregistering a sleep timer from an self-written epoll-based "io context", something like this:            struct stop_cb {
                opstate* op;
                void operator()() noexcept
                {
                    if (op->loop_->deregister_deadline(op)) {
                        op->set_stopped();
                    } else {
                        // lost the race, main loop will call `set_value()`
                    }
                }
            };

now, arrive() of the when_all opstate gets called
complete() of the when_all opstate gets called
ex::set_stopped is called, satisfying the receiver contract of the when_all sender
the when_all opstate is synchronously (!) destroyed from inside the set_stopped callback by some follow up work.
-> UB, since we are still iterating over the list of registered stop callbacks of stop_src! (the line marked with "*" above)

I've managed to "hack around" it by doing some checking of thread id's and deferring the completion to the stop callback if I detect that the completion is called synchronously from inside a stop callback. So something like this:
template <typename Opstate>
struct on_stop_request_with_thread_id {
public:
    void operator()() const noexcept
    {
        id_->store(std::this_thread::get_id(), std::memory_order::relaxed);
        op_->request_stop();
        if (id_->load(std::memory_order::relaxed) == std::thread::id{}) {
            op_->deferred_complete();
            return;
        }
        id_->store(std::thread::id{}, std::memory_order::relaxed);
    }

public: // NOLINT enable aggregate initialization
    Opstate* op_;
    std::atomic<std::thread::id>* id_;
};

export template <typename Opstate, typename Token>
struct stop_callback_with_thread_id {
public:
    bool should_defer_completion()
    {
        if (id_.load(std::memory_order::relaxed) != std::this_thread::get_id()) {
            return false;
        }

        id_.store(std::thread::id{}, std::memory_order::relaxed);
        return true;
    }

    void reset() { on_stop_.reset(); }

    void emplace(Token token, Opstate* op)
    {
        on_stop_.emplace(std::move(token), on_stop_request_with_thread_id<Opstate>{op, &id_});
    }

private:
    using stop_callback_t = ex::stop_callback_for_t<Token, on_stop_request_with_thread_id<Opstate>>;

    std::atomic<std::thread::id> id_{};
    std::optional<stop_callback_t> on_stop_ = {};
};

...and then using stop_callback_with_thread_id instead of optional<stop_callback> inside when_all's opstate, and having a complete() like this:
            void complete(Rcvr& rcvr) noexcept
            {
                // If we are completing synchronously from inside a stop
                // callback, defer completion.
                if (on_stop.should_defer_completion()) {
                    this->deferred_rcvr = &rcvr;
                    return;
                }

                complete_impl(rcvr);
            }

This all feels very hacky to me, though.
I haven't deeply investigated split yet, but I think the solution could be a bit simpler there, by using a stop callback like this instead of on-stop-request:
template <typename SharedState>
struct split_on_stop_request {
    void operator()() const noexcept
    {
        shared_state_->inc_ref();
        shared_state_->stop_src.request_stop();
        shared_state_->dec_ref();
    }

    SharedState* shared_state_;
};

...i.e. just wrapping the request_stop() between inc_ref/dec_ref to ensure the opstate object stays alive long enough.
I do wonder if there is a more elegant way to solve this issue. I don't think synchronous completions from stop callbacks should be outlawed -- it seems "natural" to me to do the set_stopped right inside the stop callback if possible. Or maybe synchronous destruction from inside the set_stopped completion of when_all is the problem? I've thought that you have to assume the lifetime of the opstate may end when calling the completion, though.

The scenario seems plausible. I think a nice way to work around the early destruction could be to increment the number of expected completions before iterating: the iteration over the children is conceptually an outstanding task. Once that is done the count is decremented and the appropriate completion is triggered if all outstanding work is completed.

This seems eerily similar to an issue reported in libunifex some time back:
https://github.com/facebookexperimental/libunifex/issues/445

The standard doesn't have that problem [yet?]: it sets up a callback using on-stop-request (see [exec.when.all p12]) which isn't defined/described. However, only when_all's stop source is passed in, ie., there is no option to play tricks with the count.

The scenario seems plausible. I think a nice way to work around the early destruction could be to increment the number of expected completions before iterating: the iteration over the children is conceptually an outstanding task. Once that is done the count is decremented and the appropriate completion is triggered if all outstanding work is completed.

This is an excellent suggestion, thanks! Now, looking at libunifex's implementation, this is how they fixed it as well.

This seems eerily similar to an issue reported in libunifex some time back: facebookexperimental/libunifex#445

Yep, seems to be the exact same issue. Thanks for the pointer! In the comments they mention stop_when as well, which is interesting, because this is where I originally stumbled across this (trying to implement the exposition-only stop_when sender algorithm from P3149R6). I was implementing it in a naive way, without stashing the original sender's result in a result_variant in the opstate. But I guess there's no way around it because of this lifetime issue.
Reading P3409R0 earlier, I had hopes that maybe single_inplace_stop_source could fix it, because it wouldn't need to loop around the list of stop callbacks as there is just a single one. But it needs to do some book-keeping after calling the stop callback, so this is sadly not a correctness fix:
  inline bool single_inplace_stop_source::request_stop() noexcept {
...
      callback->execute(callback);

      state_.store(stop_requested_callback_done_state(), memory_order_release); // <<< this might access the opstate after its lifetime ended
      state_.notify_one();
    }

    return true;
  }

The standard doesn't have that problem [yet?]: it sets up a callback using on-stop-request (see [exec.when.all p12]) which isn't defined/described. However, only when_all's stop source is passed in, ie., there is no option to play tricks with the count.

It is mentioned in [exec.snd.expos]: https://eel.is/c++draft/exec#snd.expos-16

It is mentioned in [exec.snd.expos]: https://eel.is/c++draft/exec#snd.expos-16

I didn't look there! Thanks for pointing that out. The implication is, of course, that the standard does have the problem. It may be reasonable to factor out the counting behavior and the stop callback handling into a separate entity used in relevant places: on-stop-request is also used for split (and other similar algorithms would use the same approach).

Here is one possible outline of a fix for the standard. It is a bit fiddly because of the "basic sender" infrastructure, but not too bad I feel.

Make on-stop-request generic over "operation state like" types:

template <class State>
struct on-stop-request {
    State& state;
    void operator()() noexcept { state.request_stop(); }
};

The idea is that every operation state can customize how it wants stop requests to be handled.

Add a request_stop() member function to basic-state:

  template<class Sndr, class Rcvr>
  struct basic-state {                                          // exposition only
    basic-state(Sndr&& sndr, Rcvr&& rcvr) noexcept(see below)
      : rcvr(std::move(rcvr))
      , state(impls-for<tag_of_t<Sndr>>::get-state(std::forward<Sndr>(sndr), rcvr)) { }

    Rcvr rcvr;                                                  // exposition only
    state-type<Sndr, Rcvr> state;                               // exposition only

    void request_stop() noexcept
        requires requires { state.request_stop(rcvr); }
    {
        state.request_stop(rcvr);
    }
  };

...so basic-state handles stop requests by delegating to a possible request_stop() function of the "local" state that takes the receiver as an argument (needed by when_all).

In basic-operation, give the basic-state object to start instead of the local state and the receiver separately:

    void start() & noexcept
    {
        inner_ops.apply(
            [this](auto&... ops) { impls_for<tag_t>::start(*static_cast<basic_state<Sndr, Rcvr>*>(this), ops...); });
    }

Change all start functions to take the basic-state instead of local state and receiver separately. Now, the sender can register a stop callback by using ex::on_stop_request{basic_state}. To get the previous rcvr and state arguments back it can destructure the basic_state argument.

    static constexpr auto start = []<class... Ops>(auto& basic_state, Ops&... ops) noexcept -> void {
        auto& [rcvr, state] = basic_state;

        state.on_stop.emplace(ex::get_stop_token(ex::get_env(rcvr)), ex::on_stop_request{basic_state});

For when_all, add a request_stop to its state-type:

            void request_stop(Rcvr& rcvr) noexcept
            {
                if (this->count++ == 0) {
                    return;
                }
                this->stop_src.request_stop();
                this->arrive(rcvr);
            }

For split add a request_stop() to its local-state:

    void request_stop(Rcvr&) noexcept { sh_state->request_stop(); }

...and add a request_stop() to its shared-state:
    void request_stop() noexcept
    {
        this->inc_ref();
        this->stop_src.request_stop();
        this->dec_ref();
    }

There is a simpler way that only involves the "local" state class, but then when_all would need to save a pointer/reference to the receiver in its local state, which is not needed in the approach above.
Here is a standalone example/test demonstrating the problem for when_all (also works for split if you replace when_all by it):

namespace tst {

template <class State>
class on_stop_request {
public:
    void operator()() const noexcept { state_->request_stop(); }

public: // NOLINT enable aggregate initialization
    State* state_;
};

class wait_forever_sender {
public:
    using sender_concept = ex::sender_t;

    using completion_signatures = ex::completion_signatures<ex::set_stopped_t()>;

    template <typename Rcvr>
    ex::operation_state auto connect(Rcvr&& rcvr) noexcept(
        std::is_nothrow_constructible_v<std::remove_cvref_t<Rcvr>, Rcvr>)
    {
        return opstate{std::forward<Rcvr>(rcvr)};
    }

private:
    template <typename Rcvr>
    class opstate {
    public:
        using operation_state_concept = ex::operation_state_t;

        void start() & noexcept
        {
            on_stop_.emplace(ex::get_stop_token(ex::get_env(rcvr_)), tst::on_stop_request{this});
        }

        void request_stop()
        {
            on_stop_.reset();
            ex::set_stopped(std::move(rcvr_));
        }

    private:
        using stop_callback =
            ex::stop_callback_for_t<ex::stop_token_of_t<ex::env_of_t<Rcvr>>, tst::on_stop_request<opstate>>;

    public: // NOLINT enable aggregate initialization
        Rcvr rcvr_;
        std::optional<stop_callback> on_stop_ = {};
    };
};

ex::sender auto wait_forever()
{
    return wait_forever_sender{};
}

struct call_function_on_stop_receiver {
public:
    using receiver_concept = ex::receiver_t;

    explicit call_function_on_stop_receiver(std::function<void()>* f, ex::inplace_stop_token stoken)
        : f_{f}, stoken_{stoken} { };

    call_function_on_stop_receiver(call_function_on_stop_receiver&& other) noexcept
        : f_{std::move(other.f_)}, stoken_{std::move(other.stoken_)}, called_{other.called_.exchange(true)} { };
    call_function_on_stop_receiver& operator=(call_function_on_stop_receiver&& other) = delete;
    ~call_function_on_stop_receiver() { assert(called_); }

    void set_value() && noexcept { std::terminate(); }
    void set_error(std::exception_ptr) && noexcept { std::terminate(); }
    void set_stopped() && noexcept
    {
        called_ = true;
        (*f_)();
    }

    auto get_env() const noexcept { return ex::prop{ex::get_stop_token, stoken_}; }

private:
    std::function<void()>* f_;
    ex::inplace_stop_token stoken_;
    std::atomic<bool> called_ = false;
};

} // namespace tst

int main()
{
    ex::inplace_stop_source ssource{};

    std::function<void()> f;

    auto* op = new auto(
        ex::connect(ex::when_all(tst::wait_forever()), tst::call_function_on_stop_receiver{&f, ssource.get_token()}));

    f = [&] { delete op; }; // NOLINT(cppcoreguidelines-owning-memory)
    ex::start(*op);

    ssource.request_stop();
}

I have implemented something akin to the proposed fix here. I plan to write that up as LWG issue together with a corresponding proposed fix. I'll post the issue here once I have created it.

So far I haven't reported it. I wanted to have a reproduction for both when_all and split and verify the fix but I didn't have split. I should do that this week.


Fix closing connection before content is read

This PR is related to user story ESS-XXXX
Description
Fixes an issue in _blob_to_df, where connection was set to stream=True and  closed, before content was read. This meant that the connection was available in the pool while the data was still being read.
If the connection is then reused by someone else, this would look like the connection broke from server side, potentially leading to all the ChunkedEncodingError and IncompleteReadError.
Fixed by reading the content all at once while connection was still open. No need for streaming, since we dont use the partial data.
Checklist

[x] PR title is descriptive and fit for injection into release notes (see tips below)
[x] Correct label(s) are used

PR title tips:

Use imperative mood
Describe the motivation for change, issue that has been solved or what has been improved - not how
Examples:

Add functionality for Allan variance to sensor_4s.simulate
Upgrade to support Python 9.10
Remove MacOS from CI

Well spotted @ace-e4s . I think even better would be to put everything inside the with statement and pass the stream directly on without any intermediate copying, that should cause less memory allocation. These files can be quite large.

Well spotted @ace-e4s . I think even better would be to put everything inside the with statement and pass the stream directly on without any intermediate copying, that should cause less memory allocation. These files can be quite large. I will try to come up with a suggestion.

That is a good point. I principle, we could just send response.raw directly into read_csv. However, there is one show stopper.
DRIO may send "malformed" CSV, which requires us to define the seperator as a regex and use a pure Python csv engine. This has a huge(!) performance impact. To mitigate this, we have choosen to inspect the entire content (counting new lines and commas) and determine if the csv can be parsed using regular C engine, and only use the Python engine as a last resort.
The price we pay is double memory usage for a few seconds while parsing.
Malformed csv: DRIO assumes everything is 2 column csv. Therefore, it may send a csv file where there is more than 1 comma, and no quatation is used to encapsulate the second column.
Example of a malformed line:  `1234, {"key1": "value1", "key2": "value2"}

So, if DRIO operated with RFC4180 definition of CSV (https://datatracker.ietf.org/doc/html/rfc4180.html), we could have done it more memory efficient and always used the fastest parser.

Thanks, this is nice to know. So when the value is JSON we can have commas in there, therefore parsing it requires special care. JSON and CSV sounds like a strange mix, we would have to send some encoded JSON or something to make that work, I would assume. This is indeed a strange mix...
I guess we will have to continue doing it for now, but we should discuss this with the DRIO team. It shows how some of these assumptions about values being a string has consequences.

We should have something in the code that explains the intent behind the code that handles the parsing, a comment is probably good enough.


Full E2E test of AI proxy in Playwright and NEAR sandbox

Test the AI proxy in Playwright connecting to the Fungible Token contract in a NEAR sandbox.
https://github.com/user-attachments/assets/031b1df7-f614-40d1-a7d6-7e3ec8f72cba

@race-of-sloths include

@petersalomonsen Thank you for your contribution! Your pull request is now a part of the Race of Sloths!
Weekly streak is on the road, smart strategy! Secure your streak with another PR!

Current status: waiting for scoring
We're waiting for maintainer to score this pull request with @race-of-sloths score [0,1,2,3,5,8,13] command. Alternatively, autoscoring [1,2] will be applied for this pull request
What is the Race of Sloths

Race of Sloths is a friendly competition where you can participate in challenges and compete with other open-source contributors within your normal workflow
For contributors:

Tag @race-of-sloths inside your pull requests
Wait for the maintainer to review and score your pull request
Check out your position in the Leaderboard
Keep weekly and monthly streaks to reach higher positions
Boast your contributions with a dynamic picture of your Profile

For maintainers:

Score pull requests that participate in the Race of Sloths and receive a reward
Engage contributors with fair scoring and fast responses so they keep their streaks
Promote the Race to the point where the Race starts promoting you
Grow the community of your contributors

Feel free to check our website for additional details!

Bot commands

For contributors

Include a PR: @race-of-sloths include to enter the Race with your PR

For maintainers:

Invite contributor @race-of-sloths invite to invite the contributor to participate in a race or include it, if it's already a runner.
Assign points: @race-of-sloths score [1/2/3/5/8/13] to award points based on your assessment.
Reject this PR: @race-of-sloths exclude to send this PR back to the drawing board.
Exclude repo: @race-of-sloths pause to stop bot activity in this repo until @race-of-sloths unpause command is called

@race-of-sloths score 8


feat(website-frontend): add new repositories page

Minimal UX improvements, but it will fit better with the current styling.

It seems that I cannot run the e2e tests anymore, can you run them @hugo-vrijswijk? (I believe it might be because we are using npm workspaces now).

It seems that I cannot run the e2e tests anymore, can you run them @hugo-vrijswijk? (I believe it might be because we are using npm workspaces now).

Locally? I can still run them (though I'm getting a lot of errors, maybe there should be something in the contributing.md on how to run them 😄). In CI they're running fine too. What is not working for you?

I get the following (tested with 2 different machines, and with a fresh clone):
node:internal/modules/cjs/loader:1152
  throw err;
  ^

Error: Cannot find module '/../Stryker/stryker-dashboard/packages/e2e/node_modules/playwright-core/cli.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1149:15)
    at Module._load (node:internal/modules/cjs/loader:990:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:142:12)
    at node:internal/main/run_main_module:28:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}```

Got the tests running and made a new issue for improving this cumbersome workflow: #550, still need to fix the actual tests + add the badge config thingy back on this page.

Small TODO list:

Make repositories clickable so that it navigates the user to the report.
For now, since we do not have an api for getting (only) the mutation score, place the badge inside the sme-report component


Inset legend

Gadfly supports putting legend components inside the plot box. That would be nice in Makie because it takes less space.

http://gadflyjl.org/stable/gallery/guides/#[Guide.colorkey](@ref)

This is supported:
https://makie.juliaplots.org/dev/makielayout/legend.html#Legend-Inside-An-Axis
I guess you can also make the background transparent and hide the spines ;)


fix: setTranslucent and setBackgroundColor are Android only

Question
Response

Version?
master

Devices tested?
iPhone 7

Bug fix?
yes

New feature?
no

Includes tests?
no

All Tests pass?
yes

Description
This PR silences the following warning on iOS by testing the platform OS:
2017-12-04 14:05:11.418 [warn][tid:com.facebook.react.JavaScript] `setTranslucent` is only available on Android
2017-12-04 14:05:11.418 [warn][tid:com.facebook.react.JavaScript] `setBackgroundColor` is only available on Android

Coverage remained the same at 39.937% when pulling 8c0c63d855a8a4302b0e3fc92ccda92b4b023292 on machour:silence-status-bar into 2bc73fe13ac7e7a15bc15dd8f14bd955c43f3f2e on gitpoint:master.

@machour sorry for that 🙈  good catch I didn't saw that.


Unify IR vNet injection experience

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x] Add new API for the existing service

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
It is expected to be deploy at the end of this month (June of 2021).
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
It is planned to publish swagger at the end of july of 2021.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

These changes should go into a new API version.  If you feel like this warrants an exception please go through the Breaking Change Process outlined in the PR description

Please also update the latest preview Swagger spec for Synapse: https://github.com/Azure/azure-rest-api-specs/blob/master/specification/synapse/resource-manager/Microsoft.Synapse/preview/2021-06-01-preview/integrationRuntime.json

/azp run


fix extend problem

on every call to the function the options passed get merged into the global default options object

Thanks for the PR.


#347 | SEO for the website done

Related Issue

SEO of the application | #347

Proposed Changes

Added keywords
Added meta description to the webpages
Optimized title of the pages
Added alt-name to all the image tags
Organized the code

Additional Info

Any additional information or context

Checklist

[ x] ✅ My code follows the code style of this project.
[ ] 📝 My change requires a change to the documentation.
[ ] 🎀 I have updated the documentation accordingly.
[ ] 🌟 ed the repo

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

Output Screenshots

Screenshot #1
Screenshot #2

Title goes here
Title goes here

Image goes here
Image goes here

NA

Hey! can you please make the tags in lowercase. like 'gssoc23' and 'level1'


Checkbox is insanely huge

/clients/new
.form-control is the cause :hankey:

Fixed with latest release of branch bugfixes.


Can You Update Password Complexity Verbiage for Share Password and Device Password

Can you please update the requirements for Share Password and Device Password to the below is outline on the Azure Government Portal
For share password:  The password must be alphanumeric, contain at least one uppercase letter, one lowercase letter, one special character, and one number. Only @ # - $ % ^ ! + = ; : _ ( ) special characters are allowed, I i L o O 0 characters are not allowed. The password must be 12-64 characters.
For device password: The password must be alphanumeric, contain at least one uppercase letter, one lowercase letter, one special character, and one number. Only @ # - $ % ^ ! + = ; : _ ( ) special characters are allowed, I i L o O 0 characters are not allowed. The password must be 12-15 characters.

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

ID: 67c2c09a-7b85-ea4b-a084-a8938709b9ca
Version Independent ID: 0b3177e7-180c-fbe3-5edf-f1e1df67a547
Content: Tutorial to order Azure Data Box
Content Source: articles/databox/data-box-deploy-ordered.md
Service: databox
Sub-service: pod
GitHub Login: @alkohli
Microsoft Alias: alkohli

@RDukes425  thanks for your patience. Work on this has begun. #in-progress


/live/clip/notes/get, remove and similar...

It would be nice to have methods for listing and removing notes in a clip, so it is possible to get a complete reconstruction of the liveset state.

Totally agree, this will be included in the API for sure.

Now supported:
/live/clip/get/notes
/live/clip/add/notes
/live/clip/remove/notes

Docs: Clip API


Add the FINISH goal state and rename the FINISHED goal state to ONCE

The goal state formerly known as FINISHED had the behavior that, even on a configuration update, a task with that goal state would not be relaunched. A helpful compromise between this and the  RUNNING goal state is one called FINISH that restarts a task with state TASK_FINISHED only if its configuration has been changed. To avoid ambiguity, the former FINISHED state has been renamed as ONCE.

@mrbrowning , do you have any ETA for this PR ? We'd like to use the code of this PR for the Kubernetes upgrades.

Sure, it just seemed as though there might be some semantics attached to UNKNOWN more specific than "I don't recognize this value at all." Will change.

Nice 🎉 . Thanks guys!