Appropriate projection methods for post-processing and higher-order elements

Currently, data that is saved off to be post-processed is saved off as L2-type elements that have an order of 0 (essentially elemental data). I've recently been experimenting with saving the data off as (p-1) order where p is the order of your field / H1 type elements. I've noticed that this can lead to some interesting oscillations with whatever variable your plotting outside of the solutions variables. An example of this is the below figure that has the von Mises stress plotted for a single crystal at 1% strain. The subfigure on the left makes use of linear hex elements and the right makes use of quadratic hex elements, so the von Mises fields would be constant and linear respectively in each subfigure. It appears to me that the elements need to take in information either about their local neighbors or they need to have their field interpolated across a given grain with L2 projection type method. Depending on the type of data analyst you plan on doing the answer to this question might change. I haven't really thought it through too much other than it will introduce some order of error into the data analyst, since it's all interpolated from the data that lies at the quadrature points.
It's not critical to fix now, but it is something that we'll want to address in the future. I'll need to sit down with some of the MFEM folks and see if we can't come up with a nice solution to this problem.
One last point I think should also be thought about is that orientation type data might be a bit trickier to deal with depending on what orientation space we're in.

So while working on the QuadratureFunction VectorCoefficient and Coefficient PR for MFEM, it appears to me that we'll have to come up with an appropriate NodalFiniteElement::Project for QuadratureFunctions, or if we're doing higher order elements than the order of our L2 space should be the same order as our H1 elements.

Once the MFEM PR is pulled in, we'll have access to proper L2 project methods for all of our QuadratureFunction needs.  In the mean time setting the L2 space to the same order as our H1 space should fix some of the weird graphical problems we were seeing above. The new MFEM methods also offers a chance in the future to offload all these projection techniques onto the GPU which means we only have to worry about bringing back the post-processing data back onto the host.

We'll have more flexibility with this through a future MFEM PR. So, I'm closing this for now.


Problem with default values

When using case class as parameter of another case class, default parameter does not work. This probably would not be base of problem. When case class have only one parameter and it has default value, it works. But (presented example), when case class has two parameters, booth with default value, it does not work.
Sample:
import upickle.default._
case class NestedDefault(asdf: Double = null.asInstanceOf[Double], qwer: Int = null.asInstanceOf[Int])
read[NestedDefault]("""{}""")
/*
upickle.Invalid$Data
	at upickle.GeneratedUtil$class.mapToArray(ScalaSandbox.sc0.tmp:40)
	at upickle.default$.mapToArray(ScalaSandbox.sc0.tmp:21)
	at upickle.Implicits$$anonfun$CaseR$1.applyOrElse(ScalaSandbox.sc0.tmp:78)
	at upickle.Implicits$$anonfun$CaseR$1.applyOrElse(ScalaSandbox.sc0.tmp:77)
	at scala.runtime.AbstractPartialFunction.apply(ScalaSandbox.sc0.tmp:32)
	at upickle.Types$Reader$$anonfun$read$1.applyOrElse(ScalaSandbox.sc0.tmp:89)
	at upickle.Types$Reader$$anonfun$read$1.applyOrElse(ScalaSandbox.sc0.tmp:89)
	at scala.PartialFunction$OrElse.apply(ScalaSandbox.sc0.tmp:163)
	at upickle.Types$class.readJs(ScalaSandbox.sc0.tmp:133)
	at upickle.default$.readJs(ScalaSandbox.sc0.tmp:21)
	at upickle.Types$class.read(ScalaSandbox.sc0.tmp:129)
	at upickle.default$.read(ScalaSandbox.sc0.tmp:21)
	at #worksheet#.#worksheet#(ScalaSandbox.sc0.tmp:44)
*/

Workaround is to not use default values (obviously). You can than partly make it nice by using alternative apply methods for default things (like copy method).

There is no such a bug in uPickle. The defaut values do work.
The reported problem is bound the the "IntelliJ Scala Worksheet" only (the usage is visible in the provided error stack).
The problem is, that the case class in defined in the worksheet directly and in such a case the Scala macros are not applied to it.
The default values does work in a normal case (in tests, in application code). It will work in IntelliJ Scala Worksheet only, when the case class is defined outside of it.

Well I got a similar bug in regular code here's a test to, hopefully reproduce (scala 2.11, pickle 0.3.6):
testdata.scala:
package upickle.testdata

case class Content(
  foo: Int = 999,
  bar: Option[String] = None
)

object Protocol {
  case class Container(content: Content)
  def read(str: String) = upickle.default.read[Container](str)
}

UpickleSpec.scala:
package upickle.test

import org.scalatest._
import upickle.testdata.Protocol
import upickle.testdata.Content

class UpickleSpec extends Matchers with FlatSpecLike {
  behavior of "upickle"

  // fails
  it should "read/write our case class with Protocol.read" in {
    val in: Protocol.Container = Protocol.Container(Content())
    val ser = upickle.default.write(in)
    val out = Protocol.read(ser)
    out should be (in)
  }

  // works
  it should "read/write our case class with inline read" in {
    val in: Protocol.Container = Protocol.Container(Content())
    val ser = upickle.default.write(in)
    val out = upickle.default.read[Protocol.Container](ser)
    out should be (in)
  }
}

What's stunning is that in a previous version of upickle I had the exact opposite behaviour, impossible to read something from another module with pickle.default.read but worked perfectly with the def defined in the file containing the data to serialise/deserialize.


macOS-latest workflows will use macOS-11

Breaking changes
macOS-11 is ready to be the default version for the "macos-latest" label in GitHub Actions and Azure DevOps.
Target date
This change will be rolled out over a period of several weeks beginning on September, 15. We plan to complete the migration by November, 3 December, 13 January 14.
The motivation for the changes
GitHub Actions and Azure DevOps have supported macOS-11 in preview mode since October 2020, and starting from August 2021 macOS-11 is generally available for all customers. For almost a year we have monitored customer feedback to improve the macOS-11 image stability and now we are ready to set it as the latest.
Possible impact
The macOS-11 image has a different set of software than macOS-10.15. The most significant changes are listed in the table below:

Tool name
macOS-10.15
macOS-11
Notes

R lang
4.*
-
R was not available for Big Sur when we prepared the image for the first time. Please use standard tool request process if the tool needs to be added

Virtualbox and Vagrant
6.* and 2.*
-
Virtualbox on macOS 11 requires security preferences changes, which can't be easily done. The PR with virtualbox is not yet merged https://github.com/actions/virtual-environments/pull/4010

Java
8(default)111213
8(default)11
Due to our software guidelines we left only LTS versions on the image. If you need to use other versions of Java, consider using setup-java and Java tool installer tasks

Python toolcache
<IP_ADDRESS>.73.83.9
<IP_ADDRESS>
EOL python versions were deprecated

PyPy toolcache
<IP_ADDRESS>
2.73.7
Version 3.6 was deprecated as it won't receive any updates

Go toolcache
<IP_ADDRESS>.161.17
<IP_ADDRESS>
EOL go versions were deprecated

Xamarin.Mono
6.4 - 6.12
6.12
Old versions and versions incompatible with the pre-installed Xcodes were removed

Xamarin.iOS
13.2 - 14.10
13.20 - 14.20
Old versions and versions incompatible with the pre-installed Xcodes were removed

Xamarin.Mac
6.2 - 7.8
6.20 - 7.14
Old versions and versions incompatible with the pre-installed Xcodes were removed

Xamarin.Android
10.0 - 11.2
11.0 - 11.3
Old versions and versions incompatible with the pre-installed Xcodes were removed

Xcode
12.4 (default)12.3<IP_ADDRESS>.<IP_ADDRESS>1.611.5<IP_ADDRESS>.<IP_ADDRESS>
13.0 (beta)12.5.1 (default)12.512.411.7
Only OS-compatible versions left + the latest 11 version

Android SDK build-tools and platforms
24 - 31
27 - 31
Android Platforms and build tools < 27.0 were removed from image. Consider installation in runtime using sdkmanager

Virtual environments affected

[ ] Ubuntu 16.04
[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[X] macOS 10.15
[X] macOS 11
[ ] Windows Server 2016
[ ] Windows Server 2019
[ ] Windows Server 2022

Mitigation ways
If you see any issues with your workflows during this transition period:

File an issue in this repository
Switch back to macOS 10.15 by specifying the “macOS-10.15" label. We will continue to support macOS 10.15.

This should probably be given higher priority or a sooner release date, with iOS 15 becoming widely available to end users on September 20.
In our experience the iOS 15 betas are already requiring the new digital signatures that only seem to be available in Xcode 12.5.x, so any Apple Enterprise program users signing applications with the macos-10.15 image are going to see their apps not launching on iOS 15 if they are installing them via AppCenter.ms or anywhere but TestFlight/App Store.
It appears that Xcode 12.5.x is only available on the macos-11 image and Apple doesn't support it on Catalina aka 10.15 so either you will have a LOT of customers using the default macos-latest image reaching out for support or spending hours (or days) trying to figure out the issue, or you could save them a lot of hassle and update the tag for everybody.

When I compiled the ios version of the flutter project on actions, the script script of the ios project got stuck. Stuck at the last script running. I was stuck for six hours and was eventually cancelled because time ran out.
Project type: flutter
Compilation platform: iOS
Compilation tool: fastlane

@zi6xuan feel free to create a new issue and we will try to help you

Meanwhile, this forum post highlights the iOS re-signing details on macOS 10.15 / Xcode 12 to solve the new signature issues on iOS 15 devices:
https://developer.apple.com/forums/thread/682775

FWIW the first R-4.1.1.pkg link for Intel based Macs at https://cloud.r-project.org/bin/macosx/ does support Big Sur (I have been using it on Big Sur myself for months now), however the explanatory text does not seem to have been updated to reflect this.

@jimhester feel free to open Add request in this repo and we will add R to the Big Sur image.

Just out of curiosity - why does this update take so long after new iOS and MacOS has been already officially released by Apple? I mean, If it's gonna be done by November 3rd it's gonna be +/- 3 months without proper GitHub support for this kind of environments.

EOL python versions were deprecated

Technically 2.7 is also deprecated, why is it included in the image?

Getting the following error when running tns test android on macOS-latest (11.6)
Execution failed for task ':app:stripDebugDebugSymbols'.
No toolchains found in the NDK toolchains folder for ABI with prefix: arm-linux-androideabi

I even get this error when running it against 10.15. Did something change?

@palumbo67 could be related to this https://github.com/actions/virtual-environments/issues/3894

@miketimofeev so I can technically run my unit tests in ubuntu-latest instead of macOS-latest

Hi All,
Any update on when the macOS host agent will support XCode 13?
Kind regards

Hi All, Any update on when the macOS host agent will support XCode 13? Kind regards

It is already available.
https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md

Xcode

Version
Build
Path

13.0 (beta)
13A5212g
/Applications/Xcode_13.0_beta.app

13.0
13A233
/Applications/Xcode_13.0.app

Any update when Xamarin IOS builds will support XCode 13? There doesn't seem to be way to make Visual Studio to use 13 instead of Xcode_12.5.1.

xamarin/xamarin-macios#12778

Yes, the updates were published today. Wondering when they will be available on the Azure pipeline. Currently the builds use 12.5.1 as Xamarin.iOS 14.20 is the latest available. Will we be getting <IP_ADDRESS> anytime soon on the image?

Hi, I get the following error (https://github.com/hbeni/fgcom-mumble/actions/runs/1293281303):
The log tells me, that on macos-latest openssl is not found.
Yesterday it run just fine. Today even switching back to macOS-10.15 does drop the same error.
2021-10-01T01:03:56.8559230Z make CC=g++-11 outname=fgcom-mumble-macOS.bundle CFLAGS="-I/usr/local/opt/openssl/include/ -L/usr/local/opt/openssl/lib/" plugin
2021-10-01T01:03:56.9026430Z g++-11 -shared -fPIC -o fgcom-mumble-macOS.bundle lib/radio_model.o lib/audio.o lib/io_plugin.o lib/io_UDPServer.o lib/io_UDPClient.o lib/garbage_collector.o fgcom-mumble.cpp -lssl -lcrypto -DSSLFLAGS -I/usr/local/opt/openssl/include/ -L/usr/local/opt/openssl/lib/ -Wall -O3 -I. -I./lib  -pthread
2021-10-01T01:03:57.2057260Z In file included from ./lib/updater.cpp:55,
2021-10-01T01:03:57.2060090Z                  from fgcom-mumble.cpp:1148:
2021-10-01T01:03:57.2061970Z ./lib/http/httplib.h:210:10: fatal error: openssl/err.h: No such file or directory

Hi @hbeni, you faced the same issue probably https://github.com/actions/virtual-environments/issues/4195

Hey, @hbeni
Could you please use /usr/local/opt/openssl -><EMAIL_ADDRESS>path?

@al-cheb @miketimofeev
Thank you, works!

Too bad we cant specify that we want the latest MacOS 12 Beta if we are writing code that depends on explicitly using that to build + run tests.

@mportune-bw you don't need this rollout to build for iOS15. macos-11 runners are already available so the change only affects the macos-latest tag

Since macOS 11 it's impossible to symlink iOS 12.4 runtime anymore since Xcode 10.3 is not shipped with the image anymore. Without it it's impossible to run tests for apps that support iOS 12 - 15 range. The one would need Xcode 13 for that.
Using Xcode-install I can easily add iOS 12 sim but it takes 10 minutes to install. It takes ages then to run tests.
xcversion simulators --install='iOS 12.4 Simulator'

Please provide some sort of solution to avoid doing that because it takes very long time to get anything tested.

@miketimofeev Today is November, 2. We're still see warnings "##[warning]macOS-latest pipelines will use macOS-11 soon" in our builds. Can you tell please when migration will be completed? It's blocking us to use iOS 15.

@Rus1an31 sorry for the inconvenience, the migration is delayed till December. You can explicitly point your builds to the macos-11 image label until that.

When doing a nuget restore on a xamarin solutions with windows, ios, and android I am getting ##[error]The nuget command failed with exit code(1) and error(/Users/runner/work/1/s/YYY/YYY.UWP/YYYY.UWP.csproj : error MSB4057: The target "_IsProjectRestoreSupported" does not exist in the project.  It works if the vmImage version is 11.6, but not 11.6.1

Hello @joshepkt!
We have updated Mono version from <IP_ADDRESS> to <IP_ADDRESS>. The default behavior of the nuget restore command has been changed. Previously, this command skipped restoring for project if the project file is invalid. For now, it throws the error.
Could you please confirm if restoring for the YYYY.UWP.csproj project was skipped in your successful builds?
Also, could you please try using  dotnet restore or msbuild -t:restore command as a possible workaround?

is there any way to sign development team to building a swift app in GitHub workflows????

@MaksimZhukov, Yes in the ones that worked, it looks like it errored out and skipped the UWP project.
From a working one:
/Users/runner/work/1/s/YYYY/YYYY.UWP/YYYY.UWP.csproj : error MSB4057: The target "_IsProjectRestoreSupported" does not exist in the project.
/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/NuGetScratch/rque8wsk.68l.nugetrestore.targets(315,5): warning : Skipping restore for project '/Users/runner/work/1/s/YYYY/YYYY.UWP/YYYY.UWP.csproj'. The project file may be invalid or missing targets required for restore. [/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/NuGetScratch/9ax69yfn.nz4.nugetinputs.targets]
I was able to work around by explicitly running the restore command for the csproj file and its referenced project(s).  I will work on switching it to msbuild -t:restore and see if that works.

When doing a nuget restore on a xamarin solutions with windows, ios, and android I am getting ##[error]The nuget command failed with exit code(1) and error(/Users/runner/work/1/s/YYY/YYY.UWP/YYYY.UWP.csproj : error MSB4057: The target "_IsProjectRestoreSupported" does not exist in the project. It works if the vmImage version is 11.6, but not 11.6.1

We're also seeing this same issue today. So far I've not had much luck getting it sorted; using msbuild -t:restore allowed the NuGet restore to complete but caused the iOS build to fail (Android was fine) thinking that the packages/references weren't there.

using the macos-latest just got a job executed by

and my binary is no longer executable neither on macos-11 nor macos-10.5

FYI: I had CI runs this morning using macos-latest. They did run on MacOS 11. They produced binaries running in the runner but not valid on an Intel Mac running 11.6 (Big Sur).
Specifying macos-10.15 instead of macos-latest as suggested in the issue indeed solves the issue for now.

When doing a nuget restore on a xamarin solutions with windows, ios, and android I am getting ##[error]The nuget command failed with exit code(1) and error(/Users/runner/work/1/s/YYY/YYY.UWP/YYYY.UWP.csproj : error MSB4057: The target "_IsProjectRestoreSupported" does not exist in the project. It works if the vmImage version is 11.6, but not 11.6.1

It seems like a temporary workaround is to add a dummy target in the UWP project file, i.e.
  <Target Name="_IsProjectRestoreSupported" />

I guess this workaround should be handled with caution, since I think including this target in the UWP project file will override correctly implemented instances of the _IsProjectRestoreSupported target. But until the original problem is fixed, this might be a better way forward e.g. than downgrading the Xamarin SDK.

When doing a nuget restore on a xamarin solutions with windows, ios, and android I am getting ##[error]The nuget command failed with exit code(1) and error(/Users/runner/work/1/s/YYY/YYY.UWP/YYYY.UWP.csproj : error MSB4057: The target "_IsProjectRestoreSupported" does not exist in the project. It works if the vmImage version is 11.6, but not 11.6.1

It seems like a temporary workaround is to add a dummy target in the UWP project file, i.e.
  <Target Name="_IsProjectRestoreSupported" />

I guess this workaround should be handled with caution, since I think including this target in the UWP project file will override correctly implemented instances of the _IsProjectRestoreSupported target. But until the original problem is fixed, this might be a better way forward e.g. than downgrading the Xamarin SDK.

This does not work for me as it breaks my UWP build
Error WMC9999: Type universe cannot resolve assembly: System.Runtime, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a.

So running  this  would  do what?

Breaking changes
macOS-11 is ready to be the default version for the "macos-latest" label in GitHub Actions and Azure DevOps.
Target date
This change will be rolled out over a period of several weeks beginning on September, 15. We plan to complete the migration by ~November, 3~ December, 13.
The motivation for the changes
GitHub Actions and Azure DevOps have supported macOS-11 in preview mode since October 2020, and starting from August 2021 macOS-11 is generally available for all customers. For almost a year we have monitored customer feedback to improve the macOS-11 image stability and now we are ready to set it as the latest.
Possible impact
The macOS-11 image has a different set of software than macOS-10.15. The most significant changes are listed in the table below:
Tool name	macOS-10.15	macOS-11	Notes
R lang	4.*	-	R was not available for Big Sur when we prepared the image for the first time. Please use standard tool request process if the tool needs to be added
Virtualbox and Vagrant	6.* and 2.*	-	Virtualbox on macOS 11 requires security preferences changes, which can't be easily done. The PR with virtualbox is not yet merged #4010
Java	8(default)
11
12
13	8(default)
11	Due to our software guidelines we left only LTS versions on the image. If you need to use other versions of Java, consider using setup-java and Java tool installer tasks
Python toolcache	2.7
3.5
3.6
3.7
3.8
3.9	3.7
3.8
3.9	EOL python versions were deprecated
PyPy toolcache	2.7
3.6
3.7	2.7
3.7	Version 3.6 was deprecated as it won't receive any updates
Go toolcache	1.13
1.14
1.15
1.16
1.17	1.15
1.16
1.17	EOL go versions were deprecated
Xamarin.Mono	6.4 - 6.12	6.12	Old versions and versions incompatible with the pre-installed Xcodes were removed
Xamarin.iOS	13.2 - 14.10	13.20 - 14.20	Old versions and versions incompatible with the pre-installed Xcodes were removed
Xamarin.Mac	6.2 - 7.8	6.20 - 7.14	Old versions and versions incompatible with the pre-installed Xcodes were removed
Xamarin.Android	10.0 - 11.2	11.0 - 11.3	Old versions and versions incompatible with the pre-installed Xcodes were removed
Xcode	12.4 (default)
12.3
12.2
12.1.1
12.1
12.0.1
11.7
11.6
11.5
11.4.1
11.3.1
11.2.1
10.3	13.0 (beta)
12.5.1 (default)
12.5
12.4
11.7	Only OS-compatible versions left + the latest 11 version
Android SDK build-tools and platforms	24 - 31	27 - 31	Android Platforms and build tools < 27.0 were removed from image. Consider installation in runtime using sdkmanager
Virtual environments affected

[ ]  Ubuntu 16.04
[ ]  Ubuntu 18.04
[ ]  Ubuntu 20.04
[x]  macOS 10.15
[x]  macOS 11
[ ]  Windows Server 2016
[ ]  Windows Server 2019
[ ]  Windows Server 2022

Mitigation ways
If you see any issues with your workflows during this transition period:

File an issue in this repository
Switch back to macOS 10.15 by specifying the “macOS-10.15" label. We will continue to support macOS 10.15.

，

Adding <Target Name="_IsProjectRestoreSupported" /> broke the UWP build when running in AppCenter.

@ramondeklein @MuddyChrisA

Adding <Target Name="_IsProjectRestoreSupported" /> broke the UWP build when running in AppCenter.

I found a more sufficient workaround here. Instead of adding a dummy `´, when building the iOS or Android apps, the UWP project(s) is removed from the solution in the post-clone build script.

@anders9ustafsson Love the hacks that people make to workaround this issue. :joy: My hack was a bit different. I patch out the <Target Name="_IsProjectRestoreSupported" /> using the appcenter-post-clone.sh script... Also works.

Azure DevOps users have been fully migrated.
Migration for GitHub actions users will be finished in the next 5-10 days.

🎊
On Tue, Dec 7, 2021, 2:53 PM Mikhail Timofeev @.***>
wrote:

Azure DevOps users have been fully migrated.
Migration for GitHub actions users will be finished in the next 5-10 days.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/actions/virtual-environments/issues/4060#issuecomment-988256157,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWMCLEFX5MXSTFHVBCVZ7ODUPZX6DANCNFSM5DZFV56A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Seeing an issue with our Azure Devops Build Pipeline. We have two pipelines, a CI pipeline and a release pipeline. The release pipeline signs the app for Store distribution, but otherwise is the same. the CI pipeline passes and the build pipeline fails. Pretty sure its related to the macOS 11 switch (both pipelines use macos-latest)
MTOUCH : error MT2101: Can't resolve the reference 'System.String CoreFoundation.CFString::FromHandle(System.IntPtr)', referenced from the method 'System.String Bind_TOCropViewController.TOCropToolbar::get_CancelTextButtonTitle()' in 'Xamarin.iOS, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=84e04ff9cfb79065'.
The builds on Friday ran, the same commit that built friday fails with the above message. TOCropViewController is pulled from a nuget package we include.

Some of my repos have been updated but others still on 11. I guess is slowly being rolled out to different repos?

@filipworksdev correct, we migrate gradually. Sorry for the inconvenience!

The migration is completed — all the jobs on macos-latest now run on macos-11.

My job doesn't run yet on macos-11 https://github.com/goblinengine/goblin/actions/runs/1730824706

@filipworksdev the build took place 6 days ago, we finished the migration yesterday

@iMonZ @miketimofeev  Guys you were right. Everything is done. The build was old. I did a fresh build and is all been ported. Is all good . Thank you everyone! Now I can finally use C++17 for iOS 👍


MandatoryPerformanceOptimizations: force inlining of transparent functions and de-virtualization

Do this even if the function then contains references to other functions with wrong linkage. Instead fix the linkage later.
Fixes a false error in embedded swift.
rdar://134352676

@swift-ci test


Update the architecture docs: talk about OCI registries

The charts on the page have been updated to show also the involvement of OCI registry. The text should be updated to reflect that.

Nothing special to be done, the docs already cover it.


Update prompt-chat-completion.md | Temperature range

Actually temperature should be between 0 and 1

@mrbullwinkle
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@Ali-Huseynov thanks for the contribution. Unfortunately, this is incorrect. While it is true that we artificially cap temperature between 0-1 in the Azure OpenAI Studio as setting the temperature over tends not yield the best results. Via the API it is still completely supported to set temperature between 0-2.


JBDS-4504 Installer randomly downloading components that bundled

Codecov Report

Merging #828 into master will decrease coverage by 0.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #828      +/-   ##
==========================================
- Coverage   96.48%   96.35%   -0.14%
==========================================
  Files          35       35
  Lines        3187     3374     +187
  Branches      267      480     +213
==========================================
+ Hits         3075     3251     +176
- Misses        112      114       +2
- Partials        0        9       +9

Impacted Files
Coverage Δ

browser/model/helpers/downloader.js
96.94% <0%> (-1.52%)
:arrow_down:

browser/model/jbosseap.js
98.8% <0%> (-1.2%)
:arrow_down:

browser/pages/about/controller.js
21.05% <0%> (-1.17%)
:arrow_down:

browser/directives/componentPanel.js
14.28% <0%> (-1.1%)
:arrow_down:

browser/pages/confirm/controller.js
89.71% <0%> (-0.93%)
:arrow_down:

browser/services/data.js
97.03% <0%> (-0.92%)
:arrow_down:

browser/model/jbossfuse.js
99.21% <0%> (-0.79%)
:arrow_down:

browser/model/cdk.js
99.22% <0%> (-0.78%)
:arrow_down:

browser/model/jdk-install.js
97.29% <0%> (-0.45%)
:arrow_down:

browser/model/devstudio.js
89.13% <0%> (-0.41%)
:arrow_down:

... and 21 more

Continue to review full report at Codecov.

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


Update github workflows.

Updated github workflows and added scopeci tokens for pushing to docker hub.

@michalbiesek - addressed your comments.

@ricksalsa Looks good to me feel free to merge it


lnd: 0.9.2 -> 0.10.0

Motivation for this change
Changelog
Things done

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

[ ] NixOS
[ ] macOS
[x] other Linux distributions (ArchLinux)

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

ping @cypherpunk2140

Result of nixpkgs-review pr 86656 1

1 package built:
- lnd


pcp_combine rewrite - check file paths instead of looping directories

pcp_combine currently has code to loop through an input directory, get the time information out of the file, and check if it is a valid file that is needed. This is inefficient and has caused strange requirements, like needing a dated subdirectory. It also makes it very difficult to unzip files (see issue #89 ). Instead, we can build the filename that we expect, then check if that file exists. We can then also utilize the functionality to decompress the files

A few of the instances where the pcp_combine wrapper looped through a directory to find files has been replaced by code to check that the expected path exists. This work was done to satisfy requirements for another issue. The wrapper currently still loops through a directory to find daily files.

pcp_combine no longer loops through directories and no longer requires directories to have a certain number of directories (i.e. no required dated subdirectory). To accomplish this, I added a conf item for pcp_combine called [OBS/FCST]_TIMES_PER_FILE that is used for daily file mode.
In the hrefmean-vs-s4gempak use case, there are 4 accumulations (6 hours each) within a daily file. Printing the NetCDF file will show that the 'times' dimension is 4. This is used to determine how far back to look for a file relative to the valid time. 4 * 6 = 24 so if METplus can't locate a file that is 24 hours before the valid time, it will give up because any files that come before that time will not correspond to the valid time.
Eventually it would be nice to remove the *_TIMES_PER_FILE parameter and have METplus look at the NetCDF file to determine this value.


(Apparently) new errors with OpenBLAS devel, win32, matrix inverse.

I am sorry to email without a replication in C for you, but over at Numpy we have found that the latest development branch is giving us errors for a matrix inverse on 32-bit Windows:
https://github.com/scipy/scipy/issues/8759#issuecomment-383147766
The basic issue is that a new 32-bit OpenBLAS library, built from the latest devel branch, with mingw-w64 (mingw-builds), gives a newly incorrect result for a matrix inverse.
I can describe how to replicate this in Python if its helpful (the details are on the thread above), but the basic result is the following:
import numpy as np  # This uses a previous OpenBLAS library
import scipy.linalg  # This uses the latest OpenBLAS devel

n = 100
alpha = 1 - 1e-6
A = -scipy.linalg.inv(np.identity(n) + alpha*np.eye(n, k=1))
A_np = -np.linalg.inv(np.identity(n) + alpha*np.eye(n, k=1))
print(np.abs(A - A_np).max())

This should give some very small number or 0, but it actually prints a value of 0.999999.  We have confirmed that the A_np result is correct on a couple of platforms.  So it looks like the current OpenBLAS is giving incorrect results, on Windows 32 bit only (not 64 bit).
Does this ring any bells?  What should we do next to debug?

What is the underlying hardware (or TARGET used for OpenBLAS compilation) ? Haswell (and later Intel generations) will use Nehalem kernels or worse in 32bit builds (and I seem to remember fixing(?) a bug in that code "recently" but will have to look up what it was - pretty sure it was something that led to regular tests failing but my usual platform is Linux) .
As you mention "newly incorrect", can you give an approximate time frame for when "it" (ideally the develop branch) was last known to return the expected result ?

Actually the bugfix I remembered was just the DSDOT fix for your #1492 (Mac 32bit), which should be harmless. (But looking at that issue again I notice that there was an unexplained and not locally reproducible test failure on travis, with IEEE floating point exception signals for division by zero, apparently in at least one of the blas3 tests. I cannot figure out from the travis log what TARGET was in use there, except that it was 32bit. Does your scipy code call into any blas3 function ?)

Hmm. Another fix (from october 2017) affected TRMM on 32bit Haswell (in response to a compilation failure, issue #1331 and PR #1333, so any earlier version should not even have built on that platform)

The commit that worked (and gives no test errors) was 5f998ef . It's a dynamic arch build, but going through the core types by setting OPENBLAS_CORETYPE I get:
Wrong (0.9999) on Nehalem (default), Prescott
Correct (0) on Dunnington, Penryn, Core2
Sandybridge and Haswell reset to the default of Nehalem.
I'm afraid I don't know what functions scipy.linalg.inv calls into - @pv - do you know?

Does reordering import and/or inv statements yield zero at least in one combo?

Confirmation that Scipy built against the old 5f998ef 32-bit libraries does pass the tests on the same systems: https://ci.appveyor.com/project/matthew-brett/scipy-wheels/build/job/x10hhlok3ex6nxaa

Hmm. 5f998ef is very shortly after 0.2.20, so it is one of only 390 commits that happened since then. I am not aware of anything directly affecting Nehalem besides the two I mentioned. Can you try reverting the simple change from #1333 in your tree ? If that does not help, someone needs to do a git bisect to track it down.

32bit Haswell builds fail the DTRMM test both with and without the change from #1333. Not sure yet if that is a recent regression (or even related to this issue).

No, no reordering of the imports / invs generates a zero.

@matthew-brett in principle both implementations should act identically. Especially if scipy.linalg is present& loaded numpy.lonalg will use that instead of own implementation.
What I suspect is that either uninitialized memory is added to result, or something gets overwritten outside intended arrays.
Please try following:

calling numpy routine twice, comparing results
caling scipy same way
original script with OPENBLAS_NUM_THREADS=1 set in environment
(if it really writes outside scope) setting input dimension to 64 (or any multiple thereof) is more likely to set some memory protection barrier right after in/out arrays and trigger the crash.

Calling the numpy / scipy routines more than once always gives the same results (0.999 max error for scipy, 0 max error for numpy).
OPENBLAS_NUM_THREADS=1 removes the error, making the difference 0, as it should be.
Neither 64 nor 128 for matrix dimension generate the error, but 100 does...

All numpy tests pass with a commit to OpenBLAS reverting #1333 : https://ci.appveyor.com/project/matthew-brett/scipy-wheels/build/job/76h70mvd4lnc3f9w

Reverted now, sorry.

No problem - thanks for the help diagnosing.

Sorry to ask - but will reverting the #1333 cause any problems for 32-bit Haswell builds?

I have not found any new ones, that's why I was so quick to revert this. (Actually I have not even been able to reproduce the original problem from #1331 yet)
You will however see DTRMM failures in the output of the cblat3 test (both with and without that change).


Group schema components by content-type

I'm working on an API that has many content-type, and they use references to schema
The references to the user entity, for example, aren't the same on each content-type.
I'm currently handling that by adding a content-type prefix on each schema:
schemas:
  application/json_user:
    type: object
  application/custom+json_user:
    type: object

I'd like to use something like
schemas:
  application/json:
    user:
      ...
  application/custom+json:
    user:
      ...

Is your desire to group the schemas for ease of editing, production of documentation or another use-case?

Because they are distinct and I don't want to pollute the name of the schema
For example, in my application/custom+json content-type, we wrap enums with objects like {_t: enum, _v: "admin"}
So we have 2 distinct user schemas, one for application/json, other for application/custom+json
schemas:
  application/json_user:
    type: object
    properties:
      id:
        type: string
      role:
        type: string
        enum: [ admin, regular ]
  application/custom+json_user:
    type: object
    properties:
      id:
        type: string
      role:
        type: object
        properties:
          _t:
            type: string
            enum: [ enum ]
          _v:
            type: string
            enum: [ admin, regular ]

You could use subschemas inside /components/schemas, via $defs:
components:
  schemas:
    user:
      $defs:
        application/json:
          ..
        application/custom:
          ..

And then reference them as "$ref": "#/components/schemas/user/$defs/application/json"

@karenetheridge
This indeed partially works, but swagger-ui does not support this kind of references

Open https://petstore.swagger.io/#/default/get_
paste this on swagger url

data:application/json;base64,eyJjb21wb25lbnRzIjp7InNjaGVtYXMiOnsidXNlciI6eyIkZGVmcyI6eyJhIjp7InR5cGUiOiJudW1iZXIifX19fX0sIm9wZW5hcGkiOiIzLjAuMyIsInBhdGhzIjp7Ii8iOnsiZ2V0Ijp7InJlc3BvbnNlcyI6eyJkZWZhdWx0Ijp7ImNvbnRlbnQiOnsiYXBwbGljYXRpb24vanNvbiI6eyJzY2hlbWEiOnsiJHJlZiI6IiMvY29tcG9uZW50cy9zY2hlbWFzL3VzZXIvJGRlZnMvYSJ9fX19fX19fX0=

As we can see in the image

The resolution of the schema works (we can find the number type in GET / route
The bottom Schemas component does not support this kind of reference, showing an empty group

I would like to have an explicit example of this in OAI spec, then swagger-ui and other tools will be able to implement proper support.

I would like to have an explicit example of this in OAI spec, then swagger-ui and other tools will be able to implement proper support.

@karenetheridge it would be great if you could PR a new example to the examples/v3.1 directory 😁

@MikeRalphson I can do this PR?

Note that $defs is only allowed in OAS 3.1 and later, which Swagger UI does not support.

Something like this

components:
  schemas:
    $defs:
      application/json:
        Error:
          type: object
          required:
            - code
            - message
          properties:
            code:
              type: integer
              format: int32
            message:
              type: string
      text/plain:
        Error:
          type: string

Can be added to petstore example

@souenzzo anyone can submit a PR!  For a PR on the examples, you need a slight change as the first thing under /components/schemas still needs to be a schema name:
components:
  schemas:
    Error:
      $defs:
        application/json:
          type: object
          required:
            - code
            - message
          properties:
            code:
              type: integer
              format: int32
            message:
              type: string
        text/plain:
          type: string

So you would use "$ref": "#/components/schemas/Error/$defs/application~1json" to reference the JSON version, and "$ref": "#/components/schemas/Error/$defs/text~1plain" to references the plain text version.  (The ~1 is how JSON Pointer escapes the presence of a /).
It's probably worth making a separate example rather than changing Petstore as my impression is that Petstore is the basic starting point.  But that's just my impression, not any sort of official guidance.
Beyond that, you'll need swagger-ui to support OAS 3.1 which looks like it might happen in version 5.0.  Theres nothing that the OAS spec can do about that.


[Request] Forge port

There's apparently zero mods at the moment which offer as much features as your plugin. It would be great to see nice round worlds on modded servers too so is there any chances for Forge port of this plugin?

Someone did a Forge port of WorldBorder which they released quite some time ago, though I'm not sure what the current state of it is.
Anyway, doesn't Spigot generally work with other mods?

@Brettflan I noticed that you mentioned the Forge port on your BukkitDev page but unfortunately the link redirected to 404 Not Found, so I assume that there's none at the moment.

Anyway, doesn't Spigot generally work with other mods?

I was hoping this when I started to exchange my server from Bukkit/Spigot to Forge, but as far as I know it's impossible to run mods and plugins at the same time. If you got more information about this I'll be grateful.

@Brettflan Can you consider making a Sponge port? I tried it but I've never modded Minecraft before so it's hard but it looks a lot like a Bukkit.

I don't have the time or desire to do so, sorry.

@Brettflan I have but I have none of experience about programming Minecraft so I can't do it alone. Certainly I have common experience at programming just to make you know.

If you want to try making a port of it for Sponge, you're welcome to do so. I've never used Sponge, so I can't really help with that end of things, but I don't mind answering questions about my code here or how it works through Bukkit.


Scrape less/faster, not just save, with --since?

It appears that when using the --since parameter that Twint is only using this parameter to save data up until that date. But is it possible to simply scrape only up until that date? Twint appears to still over scrape as much as it can until it hits the [!] Twitter does not return more data, scrape stops here. point. Then it limits what it saves. Is there a way to simply scrape less, so the command will complete faster? Or does it have to scrape everything, then discern the results?

In my experience Twint is working good with --since. That parameter is passed to Twitter in the search query, it could be possible that Twitter returns more data but it's rare

If that's not working right in your case, may you post a screenshot and your query so that I can dig a bit?

Here's an exampe:
twint -u joerogan --database tweets.db --since 2019-08-11 --retweets
You can see it's scraping way before 2019-08-11. Is the date format off maybe?

Scrolled to the bottom...

OK, spotted the issue.
The fact is that --retweets scrapes the user's timeline, while --since is a parameter that's given to the search query. --retweets calls .Profile while --since is used for .Search. Those two work differently.

Oh, I see. So is there a way to include retweets in a profile search? Also, I noticed the date created value of a retweet is that of the original tweet. I would really like to get the value of when it was retweeted, not created by the original user.

Getting retweets is quite hard, getting all the retweets from an user can be considered impossible. I'm not sure if you can get them via API, but, if possible, I highly suggest you to use it
Added retweet_date field

Ok, thanks!


Feature machine deployment annotations

What this PR does / why we need it: It allows to define .meteadata.annotations for MachineDeployment resources in a KubeOne configuration file (.dynamicWorkers.providerSpec.annotations).
Among other possible use cases, it allows to define the cluster-autoscaler clusterapi annotations alongside other attributes for worker node groups in a KubeOne config file.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #1133
Special notes for your reviewer:
The PR is based on the current kubeone master branch. The zz_generated.* files were created with the provided script hack/update-codegen.sh and verified with hack/verify-codegen.sh.
Does this PR introduce a user-facing change?:

No breaking changes are introduced with this PR.
User can optionally define annotations for `dynamicWorkers` elements in a KubeOne config file, which are used for the corresponding `MachineDeployment` resource.

/test all

/retest

/test all

/retest

/retest

Thanks for merging and the amazing fast replies.


Unable to Discover Device on Numato 8 Channel USB GPIO Possibly due to Version Number

8 Channel USB GPIO Module
Ubuntu 20.04
Python 3.8.10
numato-gpio 0.11.0.dev0
User is in the dialout group
Works fine with separate 8 channel board with ver '8' firmware
Device is discovered and interactable via putty

Same problem here.

Hi @MitchMagnuson and @will-riley , sorry for not responding for such a long time. The issue with versions strings is resolved in v0.12.0. Notifications are not supported on the 8 port devices unfortunately. In 'v0.13.0` I'll be raising errors with a clear message to not leave that unnoticed when you try to use the notification related API. Hope that helps!
@will-riley , are you also trying on an 8 port device? If not, may I suggest you open another issue. Maybe my improvements soon released in v0.13.0 will improve your situation. Otherwise I'd be interested in more details.
Thanks for reporting, everyone, and sorry again for the lack of responsiveness!

Mitch is no longer with Ainstein. Can you provide some background regarding
this?
Michael Paulson
VP of Engineering
785.554.5768
Home: http://ainstein.ai
Shop: https://sensing.ai/
On Sun, Mar 10, 2024 at 3:52 PM Henning Claßen @.***>
wrote:

Closed #25 https://github.com/clssn/numato-gpio/issues/25 as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/clssn/numato-gpio/issues/25#event-12066351514, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AYEHET5WACZB4B4FDCM7BJDYXTBY5AVCNFSM6AAAAAASSFAFM2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSGA3DMMZVGE2TCNA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
The information in this message is Proprietary and Confidential, intended
only for those to whom it is addressed. Any use of this information by
persons other than intended is prohibited. If you have received this email
in error, please contact the sender and delete the material from any
computer.


Support Redis Sentinel on Svix Server

Feature Request
Motivation
Redis Sentinel is a common HA practice for a small production deployment of Redis, since it requires much less physical resources to ensure high availability compare to Redis Cluster. It'd be nice if Svix supports Sentinel as well.
Proposal

Alternatives

@svix-james, what do you think?

I know next to nothing about sentinel so am not positive offhand, but I'm sure it's doable. The library supports sentinel.

Hi guys, I'm wondering if there is any more information on this? If the library supports Sentinel, perhaps it is simply a matter of the correct configuration. This is how other Redis libraries work.

How about support for AWS ElasticCache ?

@andrewmatthews We now have support for Redis Sentinel in main. It should be available in our next release. In order to try it, you'll need to at a minimum add these configuration parameters.
redis_dsn -- should point to a sentinel server
sentinel_service_name -- the name of the sentinel service
I don't recommend this for production workloads at this point without a good amount of testing. It has been lightly tested on our end, and there are some upstream optimizations that need to be made in the redis library. I will try to work on that at some point.
Fixed by https://github.com/svix/svix-webhooks/pull/1472


Unable to deploy Docker images through Kubernetes using .yaml files

Type of issue

[X] Bug
[ ] New feature
[ ] Enhancement

Description
Issue with deploying Docker images through Kubernetes using .yaml files in remotemonitoring/scripts
Error: invalid type for io.k8s.kubernetes.pkg.api.v1.ServiceSpec.loadBalancerIP
Steps to reproduce

Follow instructions at https://github.com/Azure/azure-iot-pcs-remote-monitoring-dotnet/wiki/Developer-Reference-Guide#deploy-docker-images-through-kubernetes
kubectl create -f ./remotemonitoring/scripts/nginx-ingress-controller.yaml
Similar issue with running kubectl create -f ./remotemonitoring/scripts/all-in-one.yaml

Current behavior
azureuser@vm-h4c37:~/pcs-cli/solutions/remotemonitoring/scripts$ kubectl create -f nginx-ingress-controller.yaml
service "default-http-backend" created
replicationcontroller "default-http-backend" created
error: error validating "nginx-ingress-controller.yaml": error validating data: ValidationError(Service.spec.loadBalancerIP): invalid type for io.k8s.kubernetes.pkg.api.v1.ServiceSpec.loadBalancerIP: got "map", expected "string"; if you choose to ignore these errors, turn validation off with --validate=false
azureuser@vm-h4c37:~/pcs-cli/solutions/remotemonitoring/scripts$ kubectl create -f nginx-ingress-controller.yaml --validate=false
deployment.extensions "nginx-ingress-controller" created
Error from server (AlreadyExists): error when creating "nginx-ingress-controller.yaml": services "default-http-backend" already exists
Error from server (AlreadyExists): error when creating "nginx-ingress-controller.yaml": replicationcontrollers "default-http-backend" already exists
Error from server (BadRequest): error when creating "nginx-ingress-controller.yaml": Service in version "v1" cannot be handled as a Service: [pos 120]: json: expect char '"' but got char '{'
azureuser@vm-h4c37:~/azure-iot-pcs-remote-monitoring-dotnet/cli/solutions$ kubectl create -f ./remotemonitoring/scripts/all-in-one.yaml
ingress.extensions "remotemonitoring" created
error: error validating "./remotemonitoring/scripts/all-in-one.yaml": error validating data: ValidationError(Service.spec.loadBalancerIP): invalid type for io.k8s.kubernetes.pkg.api.v1.ServiceSpec.loadBalancerIP: got "map", expected "string"; if you choose to ignore these errors, turn validation off with --validate=false
Context and Environment

Operating System: Linux and Windows
GitHub branch: Current
Node.js Runtime: v8.11.3

@faister: Have you replaced "{xxx}" in the yaml file with the  actual values of the ConfigMap section?


CentralManager instance after the DFU completed can't be used to start scanning and receive events

CentralManager instance after the DFU completed can't be used to start scanning and receive events.
I have to create a new one to be able to start scanning and connecting and getting delegate results reliably. Do you do anything particular to the centralManager passed to you after dfu completion?
Let me know if you need more details about the later behaviour I'm describing.
Thanks for your help.

Hi, you have to restore the CBCentralManager.delegate, as it was modified and nullified by the lib. We are soon releasing version 4.2 where the lib no longer needs the CBCentralManager instance. Should be published today.

that's because the library unfortunately at the time of writing takes over the centralManager and it's delegate causing this, the new upcoming version resolves this issue.
if you do not want to update the the new version straight away when it's out, just hold a reference to the central manager and it's delegate before you start the DFU initialiser, after it's complete, simply restore the centralManager's delegate as soon as you're completed, and everything should work with no issues

Yes, I do that but it doesn't seem to work.
CBCentralManager *manager = [BluetoothControllersManager sharedInstancewithDelegate:nil].centralManager;
manager.delegate = [BluetoothControllersManager sharedInstancewithDelegate:nil];
[[BluetoothControllersManager sharedInstancewithDelegate:nil] startScanningForDevices];

Couple of questions,
1-Are you sure the delegate is properly set on the second line?
2-Can you show how you initialise the DFU process ?
I have a feeling the issue might be in the underlying code in BluetoothControllersManager and not in our library

oh.. Yes indeed...

@property (atomic, strong) CBCentralManager *centralManager;

static BluetoothControllersManager *sharedInstance;

+ (BluetoothControllersManager *)sharedInstancewithDelegate:(id)delegate {
    static dispatch_once_t onceToken;
    dispatch_once(&onceToken, ^{
        if (!centralQueue) {
            centralQueue = dispatch_queue_create("{{queue_name}}", DISPATCH_QUEUE_SERIAL);
        }
        sharedInstance = [[BluetoothControllersManager alloc] init];
        sharedInstance.centralManager = [[CBCentralManager alloc] initWithDelegate:sharedInstance queue:centralQueue];
        sharedInstance.delegate = delegate;
        sharedInstance.availablePeripherals = [[NSMutableArray alloc] init];
        [sharedInstance registerForApplicationStatusNotifications];
        sharedInstance.moduleCache = [[NSMutableArray alloc] init];
        sharedInstance.modulesToIgnore = [[NSMutableArray alloc] init];
        sharedInstance.nearbyModules = [[NSMutableArray alloc] init];
    });
    if (delegate) {
        sharedInstance.delegate = delegate;
    }
    return sharedInstance;
}

CBCentralManager *manager = [BluetoothControllersManager sharedInstancewithDelegate:nil].centralManager;
manager.delegate = [BluetoothControllersManager sharedInstancewithDelegate:nil];
[[BluetoothControllersManager sharedInstancewithDelegate:nil] startScanningForDevices];

So, the code fetches the centralManager stored in the singleton sharedInstance and sets the sharedInstance as the delegate for the centralManager.
That is what you expect us to do right?

Anyway, if a new version of the app hands back control of the centralManager automatically I will gladly update to remove this logic. Still, in its current state something doesn't seems right.

- (void)initiateDFUControllerForController:(Controller *)controller {
    _isPerformingDFUUpdate = YES;
    [self startProgress];

    [self stopScanning];
    [[BluetoothControllersManager sharedInstancewithDelegate:nil] stopScanning];
    CBCentralManager *manager = [SLMBluetoothUpdateManager sharedInstance].centralManager;
    if (self.moduleToUpdate.typeUsesNewDFU) {
        manager = [BluetoothControllersManager sharedInstancewithDelegate:nil].centralManager;
        [[BluetoothControllersManager sharedInstancewithDelegate:nil] stopScanning];
    }
    NSArray *peripherals = [manager retrievePeripheralsWithIdentifiers:@[[[NSUUID alloc] initWithUUIDString:self.moduleToUpdate.hardwareAddress]]];
    self.shouldRetry = YES;

    DFUFirmware *selectedFirmware = [[DFUFirmware alloc] initWithUrlToZipFile:[self getUpdateFileForDevice:self.moduleToUpdate]];

    self.dfuServiceInitiator = [[DFUServiceInitiator alloc] initWithCentralManager:manager target:[peripherals lastObject]];
    self.dfuServiceInitiator = [self.dfuServiceInitiator withFirmware:selectedFirmware];
    // Optional:
    self.dfuServiceInitiator.forceDfu = NO; // default NO
    // initiator.packetReceiptNotificationParameter = N; // default is 12
    self.dfuServiceInitiator.logger = self; // - to get log info
    self.dfuServiceInitiator.delegate = self; // - to be informed about current state and errors
    self.dfuServiceInitiator.progressDelegate = self; // - to show progress bar

    self.dfuServiceInitiator.peripheralSelector = self; // the default selector is used
    self.dfuServiceInitiator.alternativeAdvertisingNameEnabled = NO;

    self.dfuServiceController = [self.dfuServiceInitiator start];
}

hmm this implementation is a bit confusing, but let's go with it anyways.
After the first time you init, you're manually setting the delegate to the shared instance which is ok, however, at that moment, you don't have any reference to the delegate still, so when our library takes over and completes the process, you don't have that stored anywhere.
What I would say, after the dfu service is completed and returns success or failure, you have to execute following code you showed first.
manager.delegate = [BluetoothControllersManager sharedInstancewithDelegate:nil];
[[BluetoothControllersManager sharedInstancewithDelegate:nil] startScanningForDevices];

is that what you're currently doing ?

also, is [SLMBluetoothUpdateManager sharedInstance] and [BluetoothControllersManager sharedInstancewithDelegate:nil] the same class ?

also, what's going on here, this is very unclear:
    [self stopScanning];
    [[BluetoothControllersManager sharedInstancewithDelegate:nil] stopScanning];
    CBCentralManager *manager = [SLMBluetoothUpdateManager sharedInstance].centralManager;
    if (self.moduleToUpdate.typeUsesNewDFU) {
        manager = [BluetoothControllersManager sharedInstancewithDelegate:nil].centralManager;
        [[BluetoothControllersManager sharedInstancewithDelegate:nil] stopScanning];
    }

You're doing the following:
1- Stop scanning
2- Tell the singleton to stop scanning
3- override the manager to even another centralManager from another instance
4- Stop that central too from scanning
5- Check if it's using the new dfu (what is this? is it secure vs legacy DFU ? if that's the case, we handle that in the library already.)
6- if it's using the new DFU, override it with the first central again.
7- then you ask the actual singleton to stop scanning again.
I see this is a very confusing piece of code that I'm not sure what's going on, I'd say if you are having lots of logic that's overriding our libraries functionality, we might not be able to support that as we will have to see lots more code than that before we can debug.
can you clarify a bit more ?

Yes, it is what I'm currently doing.
No, SLMBluetoothUpdateManager and BluetoothControllersManager are different singletons.

If they're different singletons, this will not work, the central manager that discovered and connected to a peripheral will be the only one that can reconnect and discover it. so as I said, you have some extra logic that's causing this and it's not a bug in the library unfortunately.
I'm not sure if our new version will help you out either as the issue is in your logic that handles the centrals

The manager that discovers .typeUsesNewDFU devices is not the BluetoothUpdateManager. Thus the code:
CBCentralManager *manager = [SLMBluetoothUpdateManager sharedInstance].centralManager;
    if (self.moduleToUpdate.typeUsesNewDFU) {
        manager = [BluetoothControllersManager sharedInstancewithDelegate:nil].centralManager;
        [[BluetoothControllersManager sharedInstancewithDelegate:nil] stopScanning];
    }

Before I hand the manager to the DFULibrary

I'm sorry we can't help, but this still is your own code that's causing this and it's not an issue in the library itself, I would suggest opening a ticket on DevZone and we can try to support you further there, but a solution might not be easy to catch without some refactoring on your side to also remove those singletons.

If you're sure there is no issue with the library I'm fine with that. I already found a solution before I opened this ticket, just wanted to make sure you didn't miss something is the library. Will be updating to the latest version when it becomes available.

100% sure it's not in the library :), the new version 4.2.1 is out so you should give it a try whenever you have time, thanks a lot for the feedback :)

Thanks


Evolving based on IV and CP

Short Description:
Instead of evolving pokemons by their CP, evolving is now done by IV first. To prevent situations where ridiculously low CP pokemons with high IVs are evolved, there is a new optional config value cp_min (default: 300). This is used as a threshold - first, all larger (than the threshold) CP pokemons are evolved based on their IV. Then, if possible, lower CP pokemons are evolved based on their CP alone, since presumably IV doesn't matter that much then.

In the previous PR I was asked to modify config.json.example, but I see this has been removed from the dev branch?
Other than that this has been tested locally and is working.

This looks great, but I know we're trying to refactor the code into an event-driven worker-plugin system. Evolution will eventually be migrated into a worker, perhaps this PR should do that?

Evolution is already its separate worker, so not sure how this applies? There is definitely refactoring to do to have the workers share some utility functionalities - but this is beyond just this worker. I'll do it myself if I get around to it soon, but that might not be the case.
Also, this change is fairly small but very useful. I've been using it for the past two days and it does a much better job compared to just CP.

Please help to check the README, if feature list updated.


cmd/pk/put: staticcheck

Closing this, see my comment here:

https://github.com/perkeep/perkeep/pull/1405#issuecomment-894727096


mac-6 is dead.

Type of Request
bug
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
mac-6 is dead.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

mac-6 is up and running fine, I can login remotely from my end. Machine out of sync with Salt master, run command "salt-call state.apply" to re-sync with Salt master.
flutter-devicelab-mac-6:~ swarming$ uptime
12:23  up 58 mins, 3 users, load averages: 1.42 1.46 1.50


downloaded folders are emtpty

I  also tried to download BIOS and drivers for Dell laptops locally but all folder were empty.
it keeps failing on download the files from dell.

+1 on this one.
Having problems with everything from DELL. Lenovo works fine
Have version 7.0.4
Start-BitsTransfer : HTTP status 504: The request was timed out waiting for a gateway.
At line:19250 char:14

...             Start-BitsTransfer $BIOSDownload -Destination "$($BIOSUpd ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidOperation: (:) [Start-BitsTransfer], Exception
FullyQualifiedErrorId : StartBitsTransferCOMException,Microsoft.BackgroundIntelligentTransfer.Management.NewBitsTransferCommand

Get-Item : Cannot find path '\loc-121SCCM\osd$\Driver Packages\MDM\Dell\Latitude 7290\BIOS\1-24-1\Latitude_7x90_1.24.1.exe' because it does not exist.
At line:19253 char:48

... bByteSize -eq $((Get-Item -Path ($BIOSUpdateRoot + $BIOSFile))).Lengt ...

                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : ObjectNotFound: (\loc-121SCCM\o...7x90_1.24.1.exe:String) [Get-Item], ItemNotFoundException
FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetItemCommand

'Get-CMDriverPackage' supports -Fast for retrieving objects without loading lazy properties. Loading lazy properties can cause significant performance penalties. If it is not necessary to utilize the lazy properties in the returned object(s), -Fast should be used. This warning can be disabled by setting $CMPSSuppressFastNotUsedCheck = $true.


Partial Equilibrium parameters not working in TB

Under the same reform (available here), I implemented the partial equilibrium functionality in TB (available here), and it seem that this PE function is not working at all:

Note that, from the two tables above, TB yields almost identical result with or without PE assumption, which is not the case for TC, nor dropQ local.
So my guess is that PE options are not being properly implemented in TB.
cc @MattHJensen

Confirmed. Thanks @GoFroggyRun

It seem that, in the latest TB (test) release, taxable income and capital gains parameters under partial equilibrium sector are working just fine, while two parameters in Charitable Contributions section are not.
The issue is that, when you input any valid parameter to any of the charitable contribution variable, the calculator will keep running. At least I wasn't able to finish any calculation involving charitable assumptions so far.
cc @MattHJensen  @brittainhard

could you take a screenshot of the parameters that aren't working?
On Apr 3, 2017, at 3:08 PM, Sean.Wang <notifications<EMAIL_ADDRESS>wrote:
It seem that, in the latest TB (test) release, taxable income and capital gains parameters under partial equilibrium sector are working just fine, while two parameters in Charitable Contributions section are not.
The issue is that, when you input any valid parameter to any of the charitable contribution variable, the calculator will keep running. At least I wasn't able to finish any calculation involving charitable assumptions so far.
cc @MattHJensenhttps://github.com/MattHJensen @brittainhardhttps://github.com/brittainhard
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/OpenSourcePolicyCenter/webapp-public/issues/512#issuecomment-291242992, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AH6qJBh8JPsfYhC4VLLnP4EIr5YPCBSeks5rsUO_gaJpZM4Mfyki.

@MattHJensen :

We don't need to include those parameters for now. @brittainhard, is it trivial to drop them?
On Apr 3, 2017, at 3:27 PM, Sean.Wang <notifications<EMAIL_ADDRESS>wrote:
@MattHJensenhttps://github.com/MattHJensen :
[screen shot 2017-04-03 at 3 27 03 pm]https://cloud.githubusercontent.com/assets/13324931/24627226/0b2071e4-1882-11e7-8d6d-731a83b85b4b.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/OpenSourcePolicyCenter/webapp-public/issues/512#issuecomment-291247937, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AH6qJDPVRb9KirIPHrVsXthUJAEukY9jks5rsUgsgaJpZM4Mfyki.

Just to be clear, the to dos here is:

[ ] Remove the Charitable Contributions elasticities from the partial equilibrium page.

@MattHJensen I can remove them from the form. I'll push a fix.

Resolved. Thanks @brittainhard and @GoFroggyRun


WRs of Campaign Maps

Put all 25 WRs in a Paginator including a download link for their ghost files. Should include Name of Player, Nationality/Locality of Player, Time of the Run, Difference to Second Place, Difference to Tenth Place, Difference to 500th Place,

moving back to v1.6 because I have nothing to do

not needed, WR players are very famous there isn't any point of this command


ArcGIS Pro crashes when changing the coordinate type after importing a list

Ways to reproduce:

Import a table to CC
Flash some of the coordinates
Hit the change coordinate button

Hitting this button will crash ArcGIS Pro

Also, clicking around while the tool is trying to load the data will also make it fail.

I'll have a look at this one

This was crashing while trying to get a UI property from the closed AmbiguousCoordsView. Switching this to a non-UI property seems to fix.
Fixed in #387

followed these exact repro steps in arcmap and arcgis pro, and did not get a crash anymore. closing


Add support for arm64_32 architecture in watchOS binaries

This mini pull request adds the arm64_32 architecture to the fat binaries for watchOS.
Build has been tested: completes successfully, and binaries do contain i386, armv7k and arm64_32 code segments. New binaries fix compilation issues such as "missing arm64_32 architecture" when building watchOS extensions on Xcode 10.x.
See also issue #1013.

The CLA is signed (but with my corporate e-mail address).

Thanks for your report and pull request! I'll give it a try and merge it once the automated CLA check passes.

BTW, this is not my first contribution, see PR #738. Don't know why the CLA check failed.

It's weird, I do not know how the CLA check works. It could be that it expires after certain time or when the clauses in the agreement are updated. When you have a chance, could you please check the links in this comment? https://github.com/google/j2objc/pull/1014#issuecomment-440062513
Thanks!

I signed it again as an individual. CLA checks should pass now.

Thank you for this great project!


value_shape

Some elements may need a value shape as well as a value size

Regge already falls into this category.
In ffcx it is not too problematic, as we get the size/shape from ufl. But it is probably a good idea to add this...
I suggest we change int value_size to vector<int> value_shape and add a convenience function value_size() that returns product(value_shape).

Completed with PR #27


ChEMBL33 updates

Description
Final changes for the ChEMBL33 update
Changes

add data/human_kinases_and_chembl_targets.chembl_33.csv
run the EGFR notebook with the updated data (new release link anticipated)

That's right. Maybe we can come up with a better procedure for the next releases :)


[Proposal] Using larger time-limit for slow execution environment

I generated model outputs using WizardLM/WizardCoder-15B-V1.0 and evaluated them using HumanEval+. When running on my laptop, I get a pass@1 of ~0.4 on HumanEval+. If I run the exact same thing on the same samples.jsonl file, but on runpod, I get a score of ~0.23 with very high variance, i.e. the score changes every time I run evalplus.evaluate.
I believe that this is due to runpod using a slower CPU which triggers the time limits in HumanEval+ that were also already in HumanEval. In L#173 of evalplus/eval/__init__.py, a time limit for evaluating some code is defined. This minimum time limit is 50ms but may be higher depending on the problem. This time limit seems to be sufficient for HumanEval, but it is not for HumanEval+. The HumanEval score isn't impacted by this. It's really just the HumanEval+ score, probably because of the increased number of tests.
When I modify this time limit from 50ms to 5 seconds and don't change anything else, I also get a pass@1 of ~0.4 on runpod. I also confirmed in other ways that the problem is really due to the the limit, e.g. on my laptop I also get slightly lower pass@1 if I create a high CPU load while running evalplus.evaluate. Not as much as when running it on runpod, but still noticable.
I haven't tried out other time limits. I just increased the 0.05 in L#173 of evalplus/eval/__init__.py to 5 seconds to confirm my hypothesis. It haven't really looked at whether even more time might be required for some problems and there is also a bunch of other logic in the code that increases this minimum time, but it wasn't enough for HumanEval+ and I'm not sure whether it's worth to modify that instead of simply increasing the minimum time limit.

Hi @tju01 thanks for the issue. The timeout policy of evalplus is set here:
https://github.com/evalplus/evalplus/blob/4a46eb1e10934f1d164f622bfe26b8956f144567/evalplus/eval/__init__.py#L174
That is, $\max(50ms, 2\times T_{gt})$ where $T_{gt}$ is the testing time used by the reference/ground-truth solution (consistent with the Appendix A of our arXiv paper).  In other words, I doubt if it is purely due to how small the lower bound is -- if "runpod" is slow then $T_{gt}$ could be much larger than 50ms too.  And if the LLM solution is of a 2x slower than the standard one -- it is judged as wrong.
That being said, I agree that a high variance is not acceptable and we will definitely improve our implementation if it helps. Nonetheless, I hope to more precisely understand the actual reason. One way you can help me is to log the runtime around here:
https://github.com/evalplus/evalplus/blob/4a46eb1e10934f1d164f622bfe26b8956f144567/evalplus/eval/__init__.py#L129
And try to minimize the log by only debugging one specific LLM solution samples.

@tju01 Would like to kindly try out this quick & temporary solution to see if it works for you? https://github.com/evalplus/evalplus/pull/6
Or I can try that later when I can touch my test-bed.

@ganler Yes, that works, even without the flag. Just increasing it to 100ms already gives me a pass@1 of ~40 again.
As for your other comment above, I agree that if the CPU would be (consistently) slower then it would measure that in the beginning and increase the timeout to twice that amount. That being said, the minimum of 50ms means that even if a solution is more than 2 times as slow as the reference solution, it can still pass if the time is less than 50ms. So on a faster CPU, more solutions will pass because they will be below the 50ms.
At least I think that's basically the reason. I'm not completely sure. But I'm quite sure that the problem is the time limit and I don't just get increased variance (i.e. the mean would still be ~40), but I get consistently lower pass@1 scores (still with high variance, but also way lower mean than 40).
I can do the tests that you wrote about above tomorrow.

I see. I think you brought a fairly good point anyways -- we should be more conservative regarding the timeout -- it does no harm except the evaluation speed (but we shall just allow users to tweak it more). That being said, I have shipped #6 and hope it can at least work for your pipeline for now -- I think it is also unnecessary for you to double-check the timing details since either way using a more conservative timeout can alleviate that (but it is appreciated if you can!).
In the immediate next step, I am thinking about following steps to improve EvalPlus:

A larger $T_\min$ to 200 milliseconds.
Allow LLM samples to be at most K-times slower than the GT where K can be set to "4" wrt the previous "2". -- we make this configurable anyways so users could tune that according to their PC setup
Document this in our README as "tips" to use EvalPlus.

cc: @brutalsavage @Kristoff-starling for alignments.

looks good to me


Ginkgo CI: Validate that tests/01-ct.sh is migrated over to Ginkgo framework

Validate that the functionality in this test is migrated over to the Ginkgo framework - provide references to which test in the Ginkgo framework covers this as a comment on this ticket. If there needs to be changes to achieve parity, make necessary additions to the Ginkgo framework to achieve parity.

Seems like test/runtime/connectivity.go checks everything that is checked in tests/01-ct.sh
Main differences:

bidirectional connectivity is always checked (this seems reasonable)
only two containers are created in ginkgo test, each test case has it's own policy instead of creating more containers at the beginning of the test and having big policy covering all test cases. This seems like it isolates test cases better.


Need to justify priority value for Vallee and provide recommendations

very small outlet drop and low flows in historic photos
Recommend sampling to get an idea of fish community composition and fish densities upstream and downstream

very small outlet drop
low flows in historic photos
Perhaps a moderate priority but recommend fish sampling to inform follow up as fish community composition and fish densities upstream and downstream may provide insight into biological value of remediating the site.


Fix: Wrap Azure calls with try/catch

Fix to handle when Azure requests throw errors instead of returning them in the callback.
Depends on https://github.com/scality/Arsenal/pull/350

PR has been updated. Reviewers, please be cautious.

Test added :)


Improve naming and documentation of iati.validator functions

After working with @allthatilk to use validation functionality, we have the following comments regarding the naming and documentation of validation functions:

In is_iati_xml - Suggest add information about other exceptions that could be raised (such as occurred an malformed XML file)
Tests for bad schemas should be added

In full_validation
In is_iati_xml
In is_valid

In is_valid, the docstring should make it clearer that this function checks against codelists.
Other than the difference in return types, what is the difference between full_validation and is_valid ??

Indeed, what does ‘full validation’ even mean?

Suggest add information about other exceptions that could be raised (such as occurred an malformed XML file)

If other exceptions are raised here, that sounds like an implementation bug - a minimal failing test case should be created and a fix made. Any lxml exception that appears is a bug and should not be part of the module's interface.

the docstring should make it clearer that this function checks against codelists.

And Rulesets. Adding something like given its population state to the summary line provides the high-level information. More detail could then be added to the rest of the description.

Other than the difference in return types, what is the difference between full_validation and is_valid ??

They should be undertaking the same steps such that the is_valid() implementation could be not full_validation(dataset, schema).contains_errors().
I'd suggest that this might have been missed in the conversion to _check_x()-style functions.

Indeed, what does ‘full validation’ even mean?

The intention is along the lines of "check ALL THE THINGS and give me details about errors".

The private / public split of functions returning alternative levels of detail about specific things should be looked at - eg. there's nothing in the module's public interface to only perform Codelist validation at the moment.

#107 acts as a small precursor to tidy up something that the caller of is_iati_xml shouldn't have to think about.

#250 indicates that error names also need more thorough investigation / their help and description text reviewed.


UrbanSim using outdated version of Patsy

I discovered this error while trying to fit a SegmentedMNLDiscreteChoiceModel. Patsy throws an error when creating the dmatrix. Looking into it I found that the author of Patsy fixed this when upgrading Patsy from v.0.4.0 to v0.4.1
I upgraded Patsy and this corrected the error. I don't know if the latest UrbanSim release bundles Patsy 0.4.1, but it will need the newer version of the package to fit models.

@apdjustino I know it's been a while, but do you remember if the segmented MNL model was indeed breaking on v0.4.0, or were you maybe on an earlier version? I'm able to reproduce this error on Patsy v0.2.1 which urbansim currently requires so it's clear we need to bump the required version, but for me the issue is resolved upon upgrading to v0.3.0.

We're going to update the Patsy required version to 0.3.0 in this release. Give us a heads up if you still think we need to require a higher version.

Addressed with #195.

Reopening this as @sablanchard found a similar bug.
We should likely bump required version of Patsy all the way up to 0.4.1 to ensure the bugfix is included, as @apdjustino suggested.


docs(TableExamplePagination): order icon names per docs

According to https://react.semantic-ui.com/elements/icon, chevron left and chevron right should be used.

Icon names are not order dependent.  However, the typescript is not as forgiving as the prop type checker and the CSS.
Since we've had this PR twice in the last week or two, I'll go ahead and merge this one 👍

Codecov Report

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

@@           Coverage Diff           @@
##           master    #2534   +/-   ##
=======================================
  Coverage   99.74%   99.74%
=======================================
  Files         154      154
  Lines        2712     2712
=======================================
  Hits         2705     2705
  Misses          7        7

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 da7d96f...215d56b. Read the comment docs.

Released in<EMAIL_ADDRESS>


[FormRecognizer] Changing test location to West Central US + Live tests fix

As instructed by the service team. A test scenario is being ignored due to a known service regression (tracked by #12319).
In parallel, using the Operation-Location header for copy operations instead of the Location header.

/azp run net - formrecognizer - tests


New Tab in VS Code Status Bar for Quick Uploading and Status of Auto Uploading

Issue:
Integrate a new tab in the VS Code status bar with an "upload" or "reload" style similar to Copilot's functionality. This feature would enhance the user experience and improve the speed and convenience of uploading files.
Description:
The proposed feature aims to add a new tab in the VS Code status bar that allows users to quickly upload files or reload changes made to the code. The idea is to emulate the style and functionality of Copilot, which provides users with an easy way to access different features or be notified about the extension actions without being annoyed
The new tab would be designed with an "upload" or "reload" style, similar to the GIF example provided, making it instantly recognizable and easy to use

Added in version 1.3.1


External Blu-ray drive

i have a external blu-ray connected to my unraid server, if the drive is not powered up the container fails to start, with the following error:
MakeMKV start failed: no such container

This is expected.  If the drive is not connected, you need to remove the --device parameter from 'Extra Parameters'.
Docker can't assign a non-existing device to a container.

is there a way to toggle it in the menu? maybe webUI with Drive and without?

Which menu are you talking about?  The only way to assign a device is through container's settings.

i understand what your saying….nevermind
do you have any interest in creating a plugin for unraid? i have a idea
On Aug 3, 2017, at 4:32 PM, Jocelyn Le Sage <notifications<EMAIL_ADDRESS>wrote:
Which menu are you talking about? The only way to assign a device is through container's settings.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/jlesage/docker-makemkv/issues/2#issuecomment-320107705, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADtCATR3cfl7IdDt4XsCgp1pyeRHoMEyks5sUkpggaJpZM4OtDAj.

What is your idea?

a plugin that allows you to share the optical drive attached to unraid via iSCSI

Ok I think I have not enough experience yet with the plugin system for this kind of integration with unRAID... Maybe later!


(ruby.portable) Migrate package

Accepted as it is a Core package used by Chocolatey CLI itself, and we are already maintaining the installer edition of the package.
Discussed in https://github.com/chocolatey-community/chocolatey-packages/discussions/1756

Originally posted by TheCakeIsNaOH November 25, 2021

The ruby.portable package is out of date and is currently broken due to the shutdown of bintray.
https://community.chocolatey.org/packages/ruby.portable
The current maintainer, @ferventcoder, is not actively maintaining packages on CCR at the moment. This package is used by the ruby alternate source for the Chocolatey CLI install command, so it is important that it is working, thus the suggestion by @AdmiringWorm to bring it into this repository.
It should be able to be updatable by AU with a similar script to the one for the ruby package.
As a part of this migration, the ruby package should probably be converted to a virtual package, and a ruby.install package should be created.
I'm not sure who should be responsible for this package, perhaps someone would be able to volunteer?
Done checklist

[ ] Rename existing ruby package to ruby.install
[ ] Create meta package ruby that have a dependency on ruby.install
[ ] Migrate ruby.portable from https://github.com/ferventcoder/chocolatey-packages/tree/master/manual/ruby.portable to this repository
[ ] Update and modernize ruby.porptable to latest Contributing Guidelines
[ ] Create AU update script to keep ruby.portable automatically up to date
[ ] Open PR to remove ruby.protable from https://github.com/ferventcoder/chocolatey-packages
[ ] Update CODE_OWNERS file with GitHub user responsible of keeping the package up to date, and fix any issues

I have opened PRs to take care of all but the last item on the todo list.

This issue has now been completed thanks to @TheCakeIsNaOH.
A new version of the ruby.portable package should also be submitted soon to CCR.


LanceDB Integration

LanceDB is a open-source, serverless, setup-free, multi-modal vector database.
@NivekT , regarding your comments about query_builder - it is essentially a function to query the database which accepts some optional arguments that can be passed with query_args. But feel free to edit of something doesn't make sense

That makes sense about query_builder.

If I understand correctly, it is doing an approximate nearest neighbor search, what happens if they want to compare that vs a Python full text search (the experimental feature)? Is that something that we want to support here.
Within nearest neighbor search, is that the setup always like it is shown? Or should we allow them to override that default query_builder? What if they want to pass in nprobes, refine_factor, etc? The Weaviate example has some query_builder like that.

That makes sense about query_builder.

If I understand correctly, it is doing an approximate nearest neighbor search, what happens if they want to compare that vs a Python full text search (the experimental feature)? Is that something that we want to support here.
Within nearest neighbor search, is that the setup always like it is shown? Or should we allow them to override that default query_builder? What if they want to pass in nprobes, refine_factor, etc? The Weaviate example has some query_builder like that.

I think we can allow FTS but then it would add some setup setps, like installing tantivy and rust. So maybe let's wait till it becomes mature (we're working on it)
Yeah we can allow users to scpecify, n_probes and refine_factor but I think that should still be included in the query_args dict, as providing different functions as input and also different args as input might not be needed as we can simply customize the operation by passing different argument parameters?

Thanks for the contribution and answers. We can merge this as it is and expand it based on user requests.


[🐞] Context values are just partially updated

Which component is affected?
Qwik Runtime
Describe the bug
Updating a context value does not re-render all places where it is used.
Use Case
Have a use-case where i want to update a context based on an API response. Therefore i'd expected that values are updated/re-rendered on all places. But as shown in the repro the value gets updated on the context but just re-rendered on the child component. By setting a new random value, it gets correctly re-rendered on all places.
Reproduction
https://stackblitz.com/edit/qwik-starter-uerlkp?file=src/routes/index.tsx
Steps to reproduce

open repro
see values context values 1 and context values 2
they should be in sync but are not
hitting the force button with a random value will update both context outputs as expected

System Info
System:
    OS: macOS 12.6
    CPU: (10) arm64 Apple M1 Max
    Memory: 304.00 MB / 64.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.13.0 - /var/folders/34/mgxs4kqs24s8kl0jfxg9jng00000gn/T/fnm_multishells/1593_1670193819142/bin/node
    Yarn: 1.22.18 - /var/folders/34/mgxs4kqs24s8kl0jfxg9jng00000gn/T/fnm_multishells/1593_1670193819142/bin/yarn
    npm: 8.1.0 - /var/folders/34/mgxs4kqs24s8kl0jfxg9jng00000gn/T/fnm_multishells/1593_1670193819142/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 108.0.5359.94
    Chrome Canary: 110.0.5462.2
    Firefox: 107.0.1
    Safari: 16.0
    Safari Technology Preview: 16.4

Additional Information
No response

updated the reproduction to use currently lasted versions:

<EMAIL_ADDRESS><EMAIL_ADDRESS>

still a problem?

Seems to be fixed!


fix(fe_hx): Support valid and invalid syslog headers

:tada: This PR is included in version 1.48.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.48.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Multiple evm cross-chain requirements

🌟 Feature Request
support for toher evm chain request
📝 Description

🤔 Rationale
easier for users to move from other chians
📋 Additional Context
none

now only eth mainnet


How To Config for Angular Conventional Commits

Thanks for making this tool available! How do I configure commit lint for Angular Conventional Commits?
https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines
On the GitHub marketplace commit lint displays the following: "Commit Lint allows you to add a layer of control over the title of your pull request and commit, forcing to respect the formatting convention that you choose (Angular, Atom, Ember ...)"
However, in the documentation it states we need to define two regex statements: PR_TITLE_REGEX and COMMIT_MESSAGE_REGEX.
I can't find any information on the regex used for Angular Conventional Commits. I'm not even sure if it can be expressed as a regex statement.
We currently use https://github.com/conventional-changelog/commitlint in our CI and are looking for something similar for a GitHub pull request.

Hi @matthew-valenti
Thanks for your interest in the app. But I am not sure where did you read the description. This description does not correspond to this app. Following is the app link for your reference:
Commit Message Lint
This app only allows you to define a regex for commit messages and PR title and then validate based on those. Following wiki link provides an example:
https://github.com/SystangoTechnologies/commit-message-validator/wiki/Commit-Message-Validator
Do let us know if you have further queries.


link to main page in header

Clicking on the Icon or OpenMapKit Server should bring you back to the main page.

Done.


What are 'bananas, with regard to the errors during pull request?

Hi, @hectorsector
Yesterday, during the pull requests we had a message that stated lack of bananas. What's it all about?
Thanks,
S.

@bhediathewolf it wasn't intended to be there -- it came over from the source code I used to implement teacherbot. It was a simple project showing you how to create a bot to check for the word "banana" in a commit message, and mark a PR accordingly, and I extended the functionality to add collaborators. But I forgot to remove the 🍌's part!

Oh, that clears it up pretty well, thank you! Can you please share the bot repository? It would be fun to learn how that works. :smiley:

Here's the bot I'm using: https://github.com/probot/probot
Teachbot, in particular, is still a little buggy (as you saw yesterday) so it's private right now. But I don't see a reason to keep it public when we go live with it (maybe in a couple of weeks?).

Thanks, that great. :+1:


What is TIMEEPS?

It seems that the sole purpose of TIMEEPS used in proc_segmentation.m L#108 is to increment a frame. I am unable to understand why.

Hi underscoredam,
for some reason, I didn't receive notifications about issues for several months, and so I also missed your question. I am sorry about that.
Unfortunately, I don't remember the reason exactly. In the straight forward implementation, numerical errors could lead to an unexpected shift in the extracted segments, when the sampling interval (1000/cnt.fs) was fractional. Introducing the TIMEEPS code, this shift is avoided. For integer sampling intervals it should not make a difference.
Best regards,
Benjamin


Add vulnerabilities/security scanning

Some options:

bandit is a Python specific tool to find common security issues in Python code.
CodeQL is a more general GitHub specific solution that supports many languages.

Discussion:

https://github.com/frequenz-floss/frequenz-repo-config-python/discussions/28

New auto-fix feature for CodeQL:

https://github.blog/changelog/2024-03-01-codeql-2-16-3-ai-powered-autofixes-for-python-updated-queries-and-security-fixes/


fix: #37 Fbe.octo is not aware of GitHub API quota

Fix: #37
Changes

Added Faraday middleware. It checks the number of requests and the remaining quota. If the number of requests equals 100 and the quota is less than 5, it pauses
Added testing of Faraday middleware
Added a test to test/fbe/test_octo.rb that tests the use of pausing

@yegor256, on my local machine, bundle exec rake is green. Do I need to fix something in my branch so that the checks will pass?

@yegor256 thanks for the comments. Fixed

@yegor256 fixed

@yegor256 fixed

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 8min)

@Suban05 Thanks for the contribution! You've earned +16 points for this: +30 as a basis; -7 for too many hits-of-code (200 >= 100); -6 for too many (25) comments that were made during review. Please, keep them coming. Your running balance is +50.

@Suban05 Thanks for the review! You've earned +5 points for this: +25 as a basis; -40 for reviewing your own contribution (which is a bad idea); +20 to give you at least something.  Your running balance is +86.

@yegor256 Great job on the review! 🎉 You've earned 45 points: 25 base points, plus 20 for your 26 insightful comments. We appreciate your thorough feedback, which hit the maximum comment bonus. Your running balance is now -581. Keep up the excellent work!


Removes Broken Two-factor Auth Link

 Purpose
Remove unnecessary link for Two-factor Auth message. Close #3901.
 Changes
Deletes link tag
 Side Effect
None that I know of.

This doesn't seem to address the root of the issue, which is that the alert shouldn't display outside of the user  settings page (see https://github.com/CenterForOpenScience/osf.io/issues/3901#issuecomment-127384824).
@Johnetordoff Can you look into this further?

@sloria Still seeing this (the issue mentioned in the comment), has this been merged?

No, this wasn't merged because it did not address the root of the issue. Ping @Johnetordoff for follow-up on this.

@sloria I got to say I'm totally stumped by this, does the page have to refresh for this to work, because that would be an easy fix.


Added Hulebäcksgymnasiet

Both students and teachers have their email adresses at this domain.
The home page for the school is at http://hule.harryda.se/

@CMDJojo Pull request merged.
Please notice that free educational subscription for JetBrains tools is for students and teachers only, and is valid for using the tools for educational purpose only. If employees of this school (or others who possesses an email address in this domain) who are not students, nor teachers, also need a license for JetBrains tools, they are eligible for an academic discount for the tools. They can get the discount by email to<EMAIL_ADDRESS>Thank you!


Update swiftLanguageVersions to swift-tools-version:4.2

This PR fixes incompatibilities with Swift 5 compiler due to an API change in the Package.swift manifest API.
swiftLanguageVersions changed from taking [Int] to [SwiftVersion] in PackageDescription API Version 4.2. For more information, see https://github.com/apple/swift-package-manager/blob/master/Documentation/PackageDescriptionV4_2.md#swift-language-version.
I've tested this with Swift 4.2.1 (swiftlang-1000.11.42) and Swift 5 (swiftlang-1<IP_ADDRESS>), and it appears to work for both. It was difficult to verify because of build errors related to #2698, but I was able to work around that by passing an explicit macOS 10.12 target with the -Xswiftc flag:
$ swift build -Xswiftc -target -Xswiftc x86_64-apple-macosx10.12
Compile Swift Module 'Alamofire' (30 sources)

Thanks Mattt!
Once Xcode 10.2 ships we'll update to the v5 syntax and fix #2698.

@jshier Thanks for the quick merge!
Please see #2737 if you're interested in a solution that isn't blocked by Xcode 10.2 GM.


feat(ci): add trufflehog secrets detector

What does this PR do?
Adding a GH action to scan for leaked secrets on each commit.

Yes! Full list of "detectors" here: https://github.com/trufflesecurity/trufflehog/tree/main/pkg/detectors


Module specifier "k6-junit" was tried to be loaded as remote module by prepending "https://" to it, which didn't work

I get this error:
WARN[0000] The moduleSpecifier "k6-junit" has no scheme but we will try to resolve it as remote module. This will be deprecated in the future and all remote modules will need to explicitly use "https" as scheme.
ERRO[0000] Module specifier "k6-junit" was tried to be loaded as remote module by prepending "https://" to it, which didn't work. If you are trying to import a nodejs module, this is not supported as k6 is _not_ nodejs based. Please read https://k6.io/docs/using-k6/modules for more information. Remote resolution error: "Get "https://k6-junit": dial tcp: lookup k6-junit: no such host"
        at go.k6.io/k6/js.(*InitContext).Require-fm (native)
        at file:///Users/poponuts/Repositories/k6/k6.config.ts:5:0(22)
        at go.k6.io/k6/js.(*InitContext).Require-fm (native)
        at file:///Users/poponuts/Repositories/k6/support/authenticate.ts:3:0(37)
        at go.k6.io/k6/js.(*InitContext).Require-fm (native)
        at file:///Users/poponuts/Repositories/k6/test/user.api.ts:4:0(46)  hint="script exception"

My webpack.config.js has:
    externals: [
        function ({context, request}, c) {
            if (request.startsWith('k6') || request.startsWith('https://')) {
                return request === 'k6-junit' ? c() : c(null, 'commonjs ' + request);
            }
            return c();
        },
    ],

I created a kg.config.ts with the following:
import {jUnit} from "k6-junit";

export function handleSummary(data) {
    console.log('Preparing the end-of-test summary...');
    return {
        "./junit.xml": jUnit(data)
    };
}

Understandably, package.json has:
{
  "devDependencies": {
    "k6-junit": "X.X.X"
  }
}

Hello. Please share the following:

k6 version
Full source code or reproduction steps

k6 version 0.39.0
https://github.com/poponuts/k6-junit-boilerplate
run as per README: k6 run -e ENVIRONMENT=test -e test/booking.api.ts

@poponuts Thanks for the additional info. So, the root cause is that you're running k6 against TypeScript test. To make it work you need:

Run webpack to build plain js test files (like this: webpack --stats-error-details)
Run k6 against js test files (like this: k6 run test.js)

If u want I can publish an example.

Sorry, if I understand you correctly, does this mean that your package can only work on js files and not ts files?
I tried to use this official k6 repo as a reference for typescript tests: https://github.com/grafana/k6-template-typescript and they work fine without the k6-junit package.

@poponuts It can work both, but it would be more correctly to transpile with webpack (see also this). If it is mandatory to keep using ts without transpiling then u need to update ur exports:
From:
import {jUnit} from "k6-junit";

To:
import {jUnit} from "./node_modules/k6-junit/index.js";