Format and Check disagree for class construction parameter indentations

Expected Behavior
Format and Check should always agree.
Using // ktlint-disable parameter-list-wrapping did not skip this problem.
Observed Behavior
Running ./mvnw ktlint:format produces formatted code which fails ./mvnw ktlint:check for:
abstract class ContinuedFractionBase<
    T : BigRationalBase<T>,
    C : ContinuedFractionBase<T, C>,
    > protected constructor(
    private val terms: List<T>,  // Complaint from ktlint:check
    open val companion: ContinuedFractionCompanionBase<T, C>,  // Complaint from ktlint:check
) : Number(),  // Complaint from ktlint:check
    List<T> by terms,
    Comparable<ContinuedFractionBase<T, C>> {
// ... code ...
}

with complaints about the construct arguments:
[INFO] --- ktlint-maven-plugin:1.7.0:check (default-cli) @ kotlin-rational ---
[ERROR] src/main/kotlin/hm/binkley/math/ContinuedFractionBase.kt:15:5: Unexpected indentation (expected 8, actual 4) (parameter-list-wrapping)
[ERROR] src/main/kotlin/hm/binkley/math/ContinuedFractionBase.kt:16:5: Unexpected indentation (expected 8, actual 4) (parameter-list-wrapping)
[ERROR] src/main/kotlin/hm/binkley/math/ContinuedFractionBase.kt:17:1: Unexpected indentation (expected 4, actual 0) (parameter-list-wrapping)

Your Environment

Version of ktlint used: 0.39.0
Name and version (or code for custom task) of integration used (Gradle plugin, Maven plugin, command line, custom Gradle task): com.github.gantsign.maven:ktlint-maven-plugin:1.7.0
Operating System and version: output of uname -a: Linux bree 5.8.0-7630-generic #32~1605108853~20.04~8bcf10e~dev-Ubuntu SMP Wed Nov 11 18:45:49  x86_64 x86_64 x86_64 GNU/Linux
Link to your project (if it's a public repository): https://github.com/binkley/kotlin-rational (note, the failing code is not in the public repo; I don't want to push until local build passes)

Wasn't able to reproduce, please try 0.40.0, seems to be fixed by #950


Validate Codes

Are we going to validate the codes such as HTML and CSS, and maybe JS too, using sites like this below?
HTML: https://validator.w3.org
CSS: https://jigsaw.w3.org/css-validator/
Related to issue #60

I would only worry about validating it if everything wasn't working together. Also JS validates in the console by erroring out, that is what the "use strict" at the top of each page does, makes sure we only use proper syntax in our JavaScript.


Update README.md

Related issue

What changes does this PR do?
Screenshots (If any)
Questions

Looks good to me! Thanks for contributing.


Add support for automation_dsc_configuration #54

I created this manually before I realized the go code generates it.  I had issues getting the go code to compile.  I don't know if this will break, so I am leaving it draft.  Comments welcome.

This has been stale since 2021 will close thank you.


Remove AirlockPlus-Localization suggestion of AirlockPlus

The suggestion has been forgotten in https://github.com/KSP-CKAN/NetKAN/commit/8456e9ae2dd7ac4c15bf09cfa48255da782c0726.
@cake-pie, can you give a go?

Approve restoring to original state.


Speed up builds for 0.68

Description
I am seeing +20 min build more than 0.67 builds with 0.68.
Is this because AppDelegate.mm is slow? Is there anyway to speed it up?
Version
0.68.0
Output of npx react-native info
no..........
Steps to reproduce
A normal build. Xcode.
Snack, code example, screenshot, or link to a repository
No response

I have the same problem on Android.
Build takes more than 20min and waits on gradle task:

Task :ReactAndroid:buildNdkBuildDebug

Deal lord I see this post so many times.. all having panic with this 0.68

If on new architecture, that's expected as you're now compiling also native code.
The first build will be expensive, but subsequent builds are supposed to be faster.
Anyway, we've published a guide on how to mitigate this:
https://reactnative.dev/docs/build-speed

As per the docs if we use --active-arch-only flag should reduce the build time by a ~75% factor.
The build is still slow on my MacBook Pro (13-inch, 2019), 1.4 GHz Quad-Core Intel Core i5

As per the docs if we use --active-arch-only flag should reduce the build time by a ~75% factor.
The build is still slow on my MacBook Pro (13-inch, 2019), 1.4 GHz Quad-Core Intel Core i5

The docs clearly says that the --active-arch-only flag is for Android only. How is this related to this issue @raajnadar which is about iOS?

I am running the android project on my Macbook, I just gave my laptop info to see if anyone with the same config has the same slow-building issue
I used yarn react-native run-android --active-arch-only cmd it took 20 min

Please open a separate issue + specify if you're on New/Old architecture. As I mentioned before, on New Architecture an increase on build time is expected as you're building native code. Please follow the setup on reactnative.dev/docs/build-speed, configure ccache and report any issue you're having if any.


Added CVSS_V2 and fixed whitespace

Signed-off-by: Kurt Seifried<EMAIL_ADDRESS>

Adding @chrisbloom7 for review too :) Since you added the CVSS_V3 support.


Feature experimental

This is a very important update. Here I fix the issue of the current user which I consider it is a serious issue. It was not a good idea to save it to the local storage. Instead I read it directly from the database and update the store. The other things are experimental, It is just the old greeting page to display the lectures and give the button to call the details page. I have not implemented the style. But gives the structure needed to do the tasks. At this stage is experimental but it is working. I send it to pull request that you may see if it runs on your computer.

This PR is being closed, since we already discuss this topic on a call, and decided to merged "feature-temp" PR instead.


Not full dps recording

I was playing today with CM to actually see my dmg. Class -> Ninja, issue spotted -> not full dps is recording. As i could saw in chat combat tab I did few M crits with Fire Avalanche skill but CM didnt record them. Highest crit with CM was 1.1M, when i actually did over 7M. It's like there was too many dmg done in too short time.

May be you have "ignore oneshots" option active and hit the mob with less then 700k HP?

It was daily bams run and i didnt oneshoot him

Closed unless you have some screenshots/video demonstrating the issue.

 Good luck

We can't reproduce it. The core of all currently working meters is the same, and it shows even higher crits of FA successfully.


template list is illegible in any size terminal

@weikanglim can we hide description from listing and the template show can have the desc details?

This definitely needs to be fixed. If we want to keep the descriptions their current length then the solution needs to be to fix the table cell wrap.
Here's a quick example to illustrate:

I'll mock something up for azd asap.

Do we have any snapshot tests that needed to be updated to catch stuff like this?

@savannahostrowski We have snapshots for all our usage text, not for command output. Personally, I think the bug here is that we have a "table format" that hasn't been put to the test. The text wrapping is definitely not how table formats should work.
As @rajeshkamal5050 suggests, can we remove Description for now? Here's how it looks like:

That seems reasonable for now - @Austinauth any concerns?

Works for me 👍


manual installation fails for normal user

Environment
Microsoft Windows [Version 10.0.17763.1282]
due to restrictions in our environment, after having tried to install WSL and a distribution, I tried now to follow the commandline instructions given here: Manual Installation
Steps to reproduce

Enabled the WSL feature in PowerShell and rebooted previously (as a user with administrative rights but not the full Administrator). I have now redone this step and it looks like this:

PS C:\windows\system32> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
Path          :
Online        : True
RestartNeeded : False

since it says: RestartNeeded : False I did not reboot again.

Downloaded DebianGNULinux_1-1-3-0_x64__76v4gfsz19hv4.Appx, unpacked it and run debian.exe from the
unpacked directory (still with the user with administrative rights), it worked and I was able to create a new user and now I am able to call debian.exe by specifying the full path of the debian.exe file or by calling wsl from anywhere as this user, but I cannot start it as normal user.
I had previously tried to install it via add-appxpackage and I have a menu entry "Debian", but when I try to start that I get a message box saying that some service is not started:

Expected behavior
I would like to be able to start the debian prompt as normal user from anywhere in the filesystem.
Actual behavior
I can start the debian prompt only as administrative user by calling wsl.exe
When I try to start wsl as normal user, I still get

H:>wsl
Für das Windows-Subsystem für Linux wurden keine Distributionen installiert.
Distributionen zur Installation finden Sie im Microsoft Store:
https://aka.ms/wslstore

since it says: RestartNeeded : False I did not reboot again.

You needed to restart at that point. Relatively safe to assume you've restarted since though, since you did manage to install the distro.

from the unpacked directory (still with the user with administrative rights)

Install your distro as a normal user. [Similar to but different than #5428, others.]

Microsoft Windows [Version 10.0.17763.1282]

Also advisable to sync up to 19041.

Install your distro as a normal user. [Similar to but different than #5428, others.]

I managed to install & initialize Debian as normal user, but I cannot see/access network drives in linux and I still get that awfull message box (see above) when trying to start Debian from the start menu. When starting Linux from the Shift-Right klick menu in Windows Eplorer on a network drive, I end up in my home directory.

I have no idea what information I should prevode for a repro, please advise.

There isn't an expectation you'll be able to provide additional information. It is more likely it will remain unknown the steps taken to get your system in the current state. Hence the tag. Your constructive path forward would be to sync up to 19041, which will reinstall enough moving parts that there is at least some chance enough of your machine will be reconstituted into operable condition.

sync up to 19041,

hmm, I don't have any chance to influence the sync up, this will be provided by our global administrators. The last update was yesterday, but it was only up to Microsoft Windows [Version 10.0.17763.1339].
Just to summarize my restrictions: I do not have access to MS-App store. I have to download manually and on the command line. Our environment forces a huge amount of group policies upon us and has an active applocker.

It is possible WSL is being thwarted by some admin policy. They way to test that hypothesis would be to try WSL on another machine in your organization with the same admin policies. Be careful to do the Enable-WindowsOptionalFeature as Administrator, rebooting, and the rest as a normal user. If it fails similarly on the other locked down machine, there isn't much you can do except ask your IT-Service Dpt. If it does work, it is an exercise in finding out what is special about your machine.
You can try, on a lark, as Administrator:
C:\> sc stop LxssManager
[it might not be started]
C:\> sc start LxssManager

Doing a "restart LxssManager" has cured some ills in the past. After the start, pause for half a minute before starting WSL in another console as a normal user. The chances of this working are "low" but it is worth the shot.

try WSL on another machine in your organization with the same admin policies

there is one other (physical) machine with which I could try it, but that has to wait until I am back from home-office at my "normal" workplace.
When I try to call sc stop LxssManager from a cmd running with local admin rights I see  shortly a  black windowpopping up, but I don't have any chance to read any message. Trying it from Power Shell (with admin rights) passes silently without any feedback. The same happens for sc start. But the error message persists.


while creating a deployment through Azure CLI I am facing one issue as mentioned below.

Resource Provider
What is the Azure resource provider your feature is part of?
https://portal.azure.com/?quickstart=true#blade/HubsExtension/BrowseResourceGroups
Description of Feature or Work Requested
Provide a brief description of the feature or work requested. A link to conceptual documentation may be helpful too.
I am deploying DELL-EMC CLoudboost, Please refer below guide for reference
https://www.dellemc.com/en-us/collaterals/unauth/technical-guides-support-information/products/data-protection/docu96466.pdf
Minimum API Version Required
What is the minimum API version of your service required to implement your feature?
Swagger Link
Provide a link to the location of your feature(s) in the REST API specs repo. If your feature(s) has corresponding commit or pull request in the REST API specs repo, provide them. This should be on the master branch of the REST API specs repo.
Target Date
If you have a target date for release of this feature/work, please provide it. While we can't guarantee these dates,
it will help us prioritize your request against other requests.
Error Message which I am getting in Azure CLI while creating this deployment
C:>az group deployment create -n cloudboost18.1 -f C:\Users\atif.shakil\Downloads\CloudBoost-<IP_ADDRESS>.Build.7-azure\management\mgt_console\resources\scripts\autobuild\azuredeploy.json -g cloudboostemc
az: error: unrecognized arguments: -f C:\Users\atif.shakil\Downloads\CloudBoost-<IP_ADDRESS>.Build.7-azure\management\mgt_console\resources\scripts\autobuild\azuredeploy.json
usage: az [-h] [--verbose] [--debug]
[--output {json,jsonc,table,tsv,yaml,yamlc,none}] [--query JMESPATH]
{group} ...

add to S168

Hi Yonzhan can you please update what is a"add to S168" all about? Do you need any further information from my end?

Planned in https://github.com/Azure/azure-cli/milestones

Hello zhoxing-ms and yonzhan.. Can you help me on the above mentioned please?

@Atif-byte Are you using the old version of azure-cli?
In the old version of azure-cli, the shorthand -f for --template-file is not supported. This shorthand can be used in the latest version of azure-cli (2.2.0), please try it.

Because there is no reply to this question for a long time, I will close it temporarily. If you have any questions, please feel free to let us know.


Create site homepage

Acceptance Criteria:

[x] Need one H1 element
[x] HTML structure should follow the design mockup
[x] Should link to the main CSS file
[x] Should link to the main JS file
[x] Create a pull request for the above requirements

Acceptance Criteria is met


Change route /services/operations to /operations

Coverage remained the same at 100.0% when pulling d51a2e6a96bbd914498361efcbef6624f76eb08c on operations into f7db3ca41a3fe638edc87b63f296c34f6104dd94 on master.


Write dependencies version with "semver:" prefix

Write dependencies version with "semver:" prefix
This makes both npm and yarn to work

Note that it is not recommended to mix package managers. We recommend the usage of yarn.

Thanks @linquize :+1:


NatLang2Latex Project

Project that addresses the GenAI project request issue.
Simple streamlit frontend that calls the Gemini API backend to translate the user's input natural text to latex.
Ex: definitive integral from 3 to 4 of x squared -> $\int_3^4{x^2dx}$ (\int_3^4{x^2dx)

Task tracking:

[ ] #3
[ ] #7
[ ] #8
[ ] #9
[ ] #10


[Enhancement] Pull data such as HRV, breathing, temp using Oura's v2 API

I was wondering if your plugin could be expanded to include things such as average HRV value or average breathing rate, temperature etc.
Maybe that's related to the fact that the plugin is using v1 of the API, not sure. But v2 is availalbe.
Also, it would be awesome if one could define a date range i.e. 2022-06-23 to 2022-07-08, and the plugin would pull in these values.

Feels like the first part equals #8 but the latter would be awesome. Although it feels a bit like #2 it's more the other way round: Not extract fields but inject URL params.
One could insert that configured query into a weekly/monthly/quaterly/yearly template for the Periodic Notes plugin.

hoping that the 0.2.0 has fixed this -- we need more folks to test however.


[REQUEST]Can we cache the results of pipeline stages distribution to the disk? It costs much time when I restart the training.

If I give the same model, topology and gpus, the stages' partition method should be the same. so we can reuse it if cache it to the disk at the first time.
On the other hand, can I pass a 'list' to deepspeed to tell it how to partition the stages in my mind.
the list is like:
[(0,1),(2,6)]
means layers 0,1 gived to stage:0, layers 2-6 gived to stage:1

well, I get it.


About the generation of BTS and WND files in the FAST INFLOWIND document.

Hello everyone,
I am considering generating a BTS wind speed file with the features of an overall increasing trend with fluctuations up and down, as shown in the figure following:

Additionally, I would like to know how to extract information from an Excel file with wind speed changing over time and convert it into a WND file.

I have tried to copy wind speed and time data from an Excel file into a WND file and input it into FAST, but I did not get a SUM file. How can I solve this problem?

Hi @shipors,
The easiest in your case would be to generate a regular BTS file using TurbSim, and then add a linear slope to it using the python toolbox. You can see examples of how to manipulate a BTS file here:
https://github.com/OpenFAST/python-toolbox/blob/main/pyFAST/input_output/examples/Example_TurbSimBox.py
You would have to adapt line 104, to add a linear slope instead of adding a constant.
If you want to generate a TurbSim box from a given time series, you need to use a constrained time series in TurbSim, with TurbModel = "TIMESR" and specifying a UserFile. You can refer to the TurbSim manual for more info on the method and its limitations. I'm enclosing a example of input file to this post. You can find a more advanced example here.
You could also write a .WND file and use it directly in InflowWind (not TurbSim), using WindType=2 to prescribe a uniform field that varies with time. But prescribing a turbulent time series in this manner is unphysical. I'm enclosing an example o WND file for a wind step.
I hope that helps.
TS_dt0.05_example.txt
WindStep_Example.txt

Dear @ebranlard,
Thank you for your recent help and support. Your advice and suggestions have been incredibly valuable. My question has been answered.
Best wishes!

Dear @ebranlard,
Thank you for your recent help and support. Your advice and suggestions have been incredibly valuable. My question has been answered.
Best wishes!

Dear @jjonkman,
I just made the modifications to the WND file as ebranlard suggested, and that was enough for me. Your advice has taught me a lot. Thank you for your support and assistance.
Sincerely,


Set min osx deployment target to 10.11

to get maximum coverage for pre-built binaries
closes #1853
in addition, MACOSX_DEPLOYMENT_TARGET can be overridden
BTW
I was able to reproduce the referenced issue by providing not existing version(MACOSX_DEPLOYMENT_TARGET=10.14.3 make app):

I wonder if this is the best place to set this. I'd imagine if someone would compile it on their own machine, we'd very much want to set the deployment target to be exactly what is installed on the system.
Maybe it would be a better idea to just set this when building on CI before deploying the binaries? That way the pre-built binaries would still work, but on a local machine you might still benefit from using system-specific versions.

@chrisduerr I think you are right.
though

I'd imagine if someone would compile it on their own machine, we'd very much want to set the deployment target to be exactly what is installed on the system.

should we set it at all? I mean if we do not set any target version then the host version should be used as default one anyway. so I little bit confused by the comment in https://github.com/jwilm/alacritty/commit/24533d2c5d86857dbb2f75f171430da7073ce65c

On macOS 10.12.6, running make app creates a bundle that refuses to
start (it complains application is only compatible with more recent
versions of macOS). The binary works great when running it directly.

as there are no any target specific restrictions in the build script.

should we set it at all? I mean if we do not set any target version then the host version should be used as default one anyway. so I'm a little bit confused by the comment in 24533d2

I can not tell you why it didn't work, but apparently this does help building on some systems. Now I don't know if this is because the user had an improperly configured system with the variable set already, or if it's actually necessary, but I think the safest thing would be to just keep it set.
This raises a problem though. If we want to run make with a different value of this variable during CI, we'd need to make it conditional. So we'd only set the variable if it's not already present in the system. If we make the assumption that the only reason why it didn't work was because the environment variable was already set, then this will not help.
Maybe @Carreau is still around and is able to provide some feedback?

Now I don't know if this is because the user had an improperly configured system with the variable set already

while investigating this I found that system caches the result of minimum required version of a binary and does not invalidate the result on replacing a content of application directory. so I have an additional possible scenario:

user with old(10.12) osx version downloads the binary which was build on CI for higher version of osx; this version does not work for him (this is expected)
he decides to follow instructions for manual build and run make app and cp -r target/release/osx/Alacritty.app /Applications/; this does not invalidate the cache mentioned above and he still has the same problem

this scenario is reproducible

removing directory before  copying certainly helps with cache invalidation(not sure about other triggers) and fixes the problem.
if this is @Carreau's case, I'll vote for setting explicit MACOSX_DEPLOYMENT_TARGET only on CI.
it would also help if someone with osx 10.12.6 will make a fresh install without this line
https://github.com/jwilm/alacritty/blob/f0180430dfea33d806ab530e789d2edb1488af6b/Makefile#L11
and provide the results here.
in the case of failure, please run this command to check minimum os version of the compiled binary
otool -l target/release/osx/Alacritty.app/Contents/MacOS/alacritty | grep -E "minos|sdk"
      sdk 10.14
    minos 10.14.2

@dm1try In that case it seems like just setting it to 10.11 for everyone might just be the easiest solution. If that works on every macOS platform, maybe that's just the best choice. I doubt there will be much performance difference, though that's something that can be tested.

@dm1try Do you think this PR is good to go the way it is right now? It works on both 10.11 and later versions of macOS, right?
Or do you think there would be any benefit in following a different approach?

I might not be able to fully test before a couple of days (travelling +
promised to be offline, but already breaking promise) but will in a couple
of days. I was aware of the caching of binary compatibility (which made
testing supper annoying), but I'm pretty sure that option was necessary for
it to work on my machine.
I think people on "old" osx version are a minority, so I believe it would
be ok to not default to using the option for local build. If the effect of
building for "old" version have minimal impact, I would be happy for CI
built versions to have maximal compatibility.
On Sun, Dec 30, 2018, 17:13 Christian Duerr<EMAIL_ADDRESS>wrote:

@dm1try https://github.com/dm1try Do you think this PR is good to go
the way it is right now? It works on both 10.11 and later versions of
macOS, right?
Or do you think there would be any benefit in following a different
approach?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jwilm/alacritty/pull/1922#issuecomment-450570615, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAUez85FaAJhouh3anqHcyXLGD1QAHBKks5u-OYggaJpZM4Zgr6W
.

@chrisduerr  I want to update the PR

for setting explicit MACOSX_DEPLOYMENT_TARGET only on CI.

but let's wait for some feedback from @Carreau or other users who use the old version of osx.
as I mentioned above it's strange that the default behavior on the old OS version is different: the minimum required version is not equal the version of host machine while compiling a binary(I posted results for my environment above, see otool check). it might be a compiler/environment related issue(new Xcode on old system/or specific SDK settings). But even so, this should affect not only alacritty build but any other program build also, so passing MACOSX_DEPLOYMENT_TARGET by the user explicitly might be the preferred way to do it(this can be mentioned in wiki).

Or do you think there would be any benefit in following a different approach?

simplicity: less code to support, relying on the default behavior :)

So as far as I can tell, rustc default to 10.7 if MACOSX_DEPLOYMENT_TARGET is not set (at least for the linker). This is (possibly) unrelated to xcode ? But I'm out of my depth here.
This is a strange as it is incoherent with my test (slightly modified from above).
otool -l target/release/osx/Alacritty.app/Contents/MacOS/alacritty | grep -E "version|minos|sdk" | head -n2

gives respectively,
MACOS_DEPLOYMENT_TARGET unset.
version 10.12.7 # (I have 10.12.6)
      sdk 10.12

.app does not works
MACOS_DEPLOYMENT_TARGET=10.7
  version 10.7
      sdk 10.12

.app works
MACOS_DEPLOYMENT_TARGET=10.11
  version 10.11
      sdk 10.12

.app works
Xcode is Version 9.2 (9C40b), I don't believe I can use more recent. I don't usually develop with XCode or have specific setting – I'm not even sure how to change the default deployment target if you don't have a xcode project.
I'm happy to try other things, but I'm unsure where to go from there.

Looks to me like the best way forward is to keep the makefile the way it is right now and just override it to 10.11 during the release deployment process using the environment variable.
Thanks for getting back to this and providing some feedback regarding the original issue @Carreau.

That seem reasonable. If there is any other things I can help test on 10.12 let me know.
Also 10.12.7 is not a version of MacOS that exists, so I'm not sure what might be setting this.
Thanks to you for all the work you are doing.

I've noticed that in the current build process MACOS_DEPLOYMENT_TARGET is ignored at all; the cached binary is reused on packing an application, for example see this build
MACOSX_DEPLOYMENT_TARGET=10.13.3
cargo build --release
    Finished release [optimized + debuginfo] target(s) in 0.47s
Created 'Alacritty.app' in 'target/release/osx'
Packing disk image...
created: /Users/travis/build/jwilm/alacritty/target/release/osx/Alacritty.dmg
Packed 'Alacritty.dmg' in 'target/release/osx'

and the result
Load command 9
      cmd LC_VERSION_MIN_MACOSX
  cmdsize 16
  version 10.13
      sdk 10.13

instead of
Load command 9
      cmd LC_VERSION_MIN_MACOSX
  cmdsize 16
  version 10.13.3
      sdk 10.13

MACOSX_DEPLOYMENT_TARGET should be set before the first cargo --release run to get the expected result

anyway, I disagree with the decision

Why? It seems like compiling for the platform the user is on is the best choice in most cases. Caching should be irrelevant outside of CI builds.
Caching on CI is also not a big deal. We'd just have to set this once and clear the cache and everything should be good to go.
I've never been able to test or reproduce this issue since I don't have a macOS machine. So I'm very curious why you've decided to close this issue @dm1try since it seems like there should be a way forward which satisfies everyone. You said that just removing the variable completely is the best way forward you can recommend, but it seems like that would break both on CI and on setups like Carreau's?

Why? It seems like compiling for the platform the user is on is the best choice in most cases.

As I already said, this is how it works by default without providing MACOSX_DEPLOYMENT_TARGET. Particularly, the minimum required version is set to the version of SDK which is used on a compilation. The good example of default behavior is the current release binary which has the minimum version is equal 10.13(see above, MACOSX_DEPLOYMENT_TARGET is ignored at all because it is set after the binary was compiled)

Caching on CI is also not a big deal. We'd just have to set this once and clear the cache and everything should be good to go.

just for clarity, the cache discussed above is about caching the compiled binary between compilations
cargo test --release
export MACOSX_DEPLOYMENT_TARGET=10.13.3
make dmg #  MACOSX_DEPLOYMENT_TARGET is ignored as the binary was already compiled in the first step, so the minimum version is equal the version of used SDK

I've never been able to test or reproduce this issue since I don't have a macOS machine. So I'm very curious why you've decided to close this issue

I commented above about why I closed this:

I've noticed that in the current build process MACOS_DEPLOYMENT_TARGET is ignored at all; the cached binary is reused on packing an application

so the provided PR change does not solve the original problem(#1853). MACOS_DEPLOYMENT_TARGET should be set in .travis.yml or ci/script.sh to make an impact on a compiled binary.

since it seems like there should be a way forward which satisfies everyone.

please clarify that you mean by the satisfaction. I'm interested in the proper solving of the problem.
lets look at this information provided by @Carreau

version 10.12.7 # (I have 10.12.6)
Xcode is Version 9.2 (9C40b)
sdk 10.12

the minimum version in the test binary looks wrong.
the default sdk for this version of Xcode is 10.13.2

so adding the line with export MACOSX_DEPLOYMENT_TARGET = $(shell defaults read loginwindow SystemVersionStampAsString) to Makefile looks like a dirty workaround for fixing a system setup for this particular case, but the consequences are:

changing a default behavior and don't use MACOSX_DEPLOYMENT_TARGET for its intended purpose
the discussion in this issue that partially unrelated to the original problem(set a minimum required version for the pre-built binaries)

but it seems like that would break both on CI and on setups like Carreau's?

see above, CI setup already ignores MACOSX_DEPLOYMENT_TARGET and has the default values:

    # the information for a downloaded release binary
      cmd LC_VERSION_MIN_MACOSX
  version 10.13
      sdk 10.13

so it should not break anything

if the problem in Carreau's setup is common for users on 10.12.6 then this information should be added to the wiki. And again, it looks like a system-wide problem so the user should solve it on the system setup level but not in the makefile of every compiled binary.

The MACOSX_DEPLOYMENT_TARGET variable is used to specify the minimum version of macOS which should be supported by the application. So as far as I can tell, always setting it to 10.11 should resolve the problem for most users.
You're talking about caching of the binary, however this is not an issue on CI and neither is it a problem with local builds. The assumption for local builds is always that they're made from a clean repo clone, we don't need to worry about previous build caches unless they're going to create issues in the future. On CI we have full controll over the cache, cleaning that once is not an issue.

The good example of default behavior is the current release binary which has the minimum version is equal 10.13 (see above, MACOSX_DEPLOYMENT_TARGET is ignored at all because it is set after the binary was compiled).

The current release binary has a version of 10.13 because our CI server (the default travis setup) runs macOS 10.13 by default. It's not an issue with caching, this is the expected behavior.

You're talking about caching of the binary, however this is not an issue on CI and neither is it a problem with local builds.

Re-read above.

The current release binary has a version of 10.13 because our CI server (the default travis setup) runs macOS 10.13 by default. It's not an issue with caching, this is the expected behavior.

That's it. This is the default behavior without any dirty workarounds placed in Makefile.

That's it! This is the default behavior without any dirty workarounds that needed to be placed in Makefile.

It doesn't work though, since we don't want to produce binaries for 10.13.
Which gives us the option to either always specify 10.11, or specify 10.11 just for CI. As far as I know we don't need any newer features, so it should be irrelevant which version is specified exactly. Setting it to 10.11 in the makefile, will solve both @Carreau issue and the problem with binaries not being available on CI. Setting it just on CI deployment will only fix one of those problems.
I'll create a separate PR to set this up, but it seems like that's the best way forward since it makes everyone happy and means we don't need to deal with potential system configuration issues.

it doesn't work though, since we don't want to produce binaries for 10.13.

this was discussed in the context of https://github.com/jwilm/alacritty/commit/24533d2c5d86857dbb2f75f171430da7073ce65c, as the example of how it should work by default and it was indirectly related to the original #1853.


glossy:0.1.0 and glossy:0.1.1

I am submitting

[x] a new package
[x] an update for a package

Description: Cleanup, refactoring, bug fix.
0.1.0: remove errant PDF
0.1.1: new version

removed errant PDF
cleaned up logic in term selection
improved the example (readme.typ)
unified around terms with no groups having an empty group string: ""

Thanks


Make it possible to link against java 6

Class java.nio.charset.StandardCharsets is not available in JDK 6. By making this change it's possible to run with JDK 6.

Thanks! How urgent is a release for you?

Hi @magro, thanks for merging!
I'd be nice to have a release soon, I'm currently using a custom build of the library.
Thanks!

Hi there,
Would you please release a new version of the library so I can use this fix?
Thanks!

@maurociancio sorry for the delay, I just released this with 2.2.0
Thanks again for the PR!


Does not notify or log errors for logging in to ADC website

I had a typo in my config.json file where "username" was incorrect, and I couldn't figure out why this plugin wasn't working.   Eventually I saw the typo and fixed it.  It would have been helpful if the debug output had some info with the error when logging in to the alarm.com website.

@silverhack77 Not a bad idea.

@silverhack77 I just published version 0.7.2, which now logs login errors on alarm.com. You'll also need to update the login call on WrapAPI.


Fix create script syntax

Signed-off-by: yatinmaan<EMAIL_ADDRESS>Pull request
Description
The ModularTarget was ignored for aliased scripts with overridden params.
Checklist

[ ] The RFC, if required, has been submitted and approved
[ ] Any user-facing impact of the changes is reflected in docs.tremor.rs
[X] The code is tested
[x] Use of unsafe code is reasoned about in a comment
[X] Update CHANGELOG.md appropriately, recording any changes, bug fixes, or other observable changes in behavior
[ ] The performance impact of the change is measured (see below)

Performance

Coverage increased (+0.01%) to 85.239% when pulling f52b7ca455c72acde5d8221fc8f3a32631f92b76 on yatinmaan:fix_create_script into fa9e30f69ab9a13276c24d90a580d04e843ac8b7 on tremor-rs:main.


Added extra arguments to method to allow for lifecycle support

Added optional extra arguments to serverActorForClient to allow for lifecycle support.
Made buildAndStoreComet public so that any app can add a programmatically created CometActor

Wait... need to change some params


No Chat Reports couldn't evaluate the safety of this server

Modloader
Quilt
Minecraft Version
1.19.2
Modloader Version
Quilt: 0.17.6
No Chat Reports Version
1.19.2-v1.13.11
Modpack Info
Fabulously Optimized - https://modrinth.com/modpack/fabulously-optimized
The latest.log File
https://mclo.gs/FcXj7B9 - Ignore the lines that are realated to chunks, it's an issue with a different mod.
Bug Description
I was told to report this issue if this happened, the server has No Chat Reports as well:

Steps to Reproduce
No response
Other Information
No response

Could you reproduce this with only Multiconnect (and any dependencies) on Quilt and Fabric? I think that mod is the issue.

I think this might be somehow related to #132. Does server in question run on Fabric?

Ah, it wasn't the mod itself, it was its API:

MultiConnect API


Fix: add install requires for pip installation

Include the requirements packages in the setup file in order to be installed in the notifier pip installation.
These requirements must be updated any time a new requirement package be added to the project.

@fortizc, you were right. Read the install_requires from a file outside the setup file is a much better way to solve this!

Now, we use the latest minor and patch release for the current major version of celery...., but are you totally sure that a different minor version couldn't break our code?

Now, we use the latest minor and patch release...
Is mayor.minor.patch
but are you totally sure that a different minor version couldn't break our code?
Yes, see this Python versioning system is compatible with semantic versioning

We're right then!


Rename 'Usabilla' to 'GetFeedback'

SurveyMonkey acquired 'Usabilla' and new offering is now called 'GetFeedback'. See these articles -
https://techcrunch.com/2019/03/05/surveymonkey-acquires-web-survey-company-usabilla-for-80m/
https://www.globenewswire.com/news-release/2021/04/06/2205102/0/en/SurveyMonkey-Debuts-Rebrand-of-GetFeedback-CX-Platform.html
Vendor Site - https://www.getfeedback.com/
Example Site - https://www.chasecenter.com/home
You will see that Wappalyzer detects 'Usabilla' on this site but feedback widget says powered 'GetFeedback'. You can click 'Feedback' floating tab to see this OR screenshot attached

Also, I think we should tag this in additional category of 'Surveys'. Currently it's tracked under 'Issue Trackers'

Updated, thanks!


Ampersand (&) results in incorrect rendering of HTML

If the demo apps cannot help and there is no issue for your problem, tell us about it
Demo via NS Preview: https://stackblitz.com/edit/nativescript-stackblitz-templates-ipbbwj?file=app%2Fcomponents%2FHome.vue
Which platform(s) does your issue occur on?

Tested on Android 12 to replicate the ampersand issue.
Could not test on iOS 16.5 as I was getting ReferenceError: UILabelLinkHandlerTapDelegate is not defined (not sure if it's an NS Preview issue). However when testing in the application I'm working on I saw the same behaviour.

Please, tell us how to recreate the issue in as much detail as possible.
The issue is that HTML is not rendered properly when including ampersands in the text. Example:
<HtmlLabel :html="'
T&Cs
'" />
<HtmlLabel :html="'
T and Cs
'" />

I've tried using HTML Entities instead of the & symbol on its own but it resulted in the same thing.
<HtmlLabel :html="'
T&Cs
'" />

I've included other examples in the NS Preview link above.

@dangrima90 i dont understand your issue. What you describe seems ok to me.
Please clarify what you see and what you expect

@farfromrefug maybe I did not explain myself properly. The issue is that when having an & in the text HTML is not rendered as expected.
Screenshot:

The text you see highlighted with the red box appear as raw HTML rather than rendered as HTML.

@dangrima90 i get it now thanks!

Did you try to replace & with & ? & is a protected keyword

@dangrima90 no sorry it is not on my priority list right now as it can for now be fixed with a text replace.
if you want to make a a PR to fix the right way that would be welcome

@farfromrefug I've tested this out with the repo's demo and I can verify the following:

The issue is only replicable on Android
From my tests it seems that &, < and   break the rendering
Changing the above to &, < and   (space) does result in correct rendering

To test I've extracted all the characters listed here (https://www.freeformatter.com/html-entities.html) and tested them out in the Base.vue file.
Code Snippet

My small worry is that even though I tested a lot of different symbols, I don't know if there is anything else that would break the rendering. From my end in the app I can replace the breaking symbols (&, < and  ) to make sure that the app doesn't break.
I have tried looking at the code to understand where the error might be coming from but I'm not sure. My guess is that it is linked to the logic in here: https://github.com/nativescript-community/text/blob/0cf16bfa047e15879e49ea1e3e22fb0ac57c924e/packages/text/platforms/android/java/com/nativescript/text/Font.java#L312.
The stringBuilderFromHtmlString is called to generate the string to render, which in turn calls fromHtml. I couldn't figure out which part of the code is triggering the error.

@dangrima90 thanks for investigating this. The issue clearly comes from the html parser https://github.com/nativescript-community/text/blob/0cf16bfa047e15879e49ea1e3e22fb0ac57c924e/packages/text/platforms/android/java/com/nativescript/text/HtmlToSpannedConverter.java. It is modified code based on what you can see on the web. Clearly & and < (mostly > too) breaks the parser. Not sure why though

@dangrima90 stumbled upon this today. https://github.com/smart-fun/XmlToJson/issues/24
Can you try escaping the special characters <>&?

@farfromrefug thanks for the above - I have been testing with HTML Entities names and got somewhere but not 100% a full proof solution. For some reason in ns preview using & (&) still results in an issue, however using the HTML Entity number instead & does work successfully. (https://stackblitz.com/edit/nativescript-stackblitz-templates-ipbbwj?file=app%2Fcomponents%2FHome.vue). Locally I didn't see any difference between HTML Entity names (&) or numbers (&) using the ui-label demo.
For my use case I've been trying to use a regex to handle the replacing of these characters. The idea was to simply find &, < and > and convert them to their HTML Entity equivalent. With simple strings this will work but when dealing with nested HTML elements things start to get weird 😄 because you end up replacing the < / > of the tags themselves which will obviously break things.
Similar to the stackoverflow post in the issue you linked above, I found a similar explanation re: XML invalid characters: https://stackoverflow.com/a/28152666. Long story short it mentions that &, <, >, ', " between tags should be escaped. Now from my tests only & and < resulted in an error, but I guess if there's a fix to be made it would make sense to cater for all characters that should be escaped in XML.
My question would be this: Not sure if it would be possible that whilst building the HTML string (https://github.com/nativescript-community/text/blob/0cf16bfa047e15879e49ea1e3e22fb0ac57c924e/packages/text/platforms/android/java/com/nativescript/text/HtmlToSpannedConverter.java) it would check for any characters that should be escaped and it would handle that accordingly.
Just an educated guess here, maybe something like the following will cater for this issue?
@Override
public void characters(char ch[], int start, int length) throws SAXException {
    StringBuilder sb = new StringBuilder();
    /*
        * Ignore whitespace that immediately follows other whitespace; newlines count
        * as spaces.
        */
    for (int i = 0; i < length; i++) {
        char c = ch[i + start];
        if (c == ' ' || c == '\n') {
            char pred;
            int len = sb.length();
            if (len == 0) {
                len = mSpannableStringBuilder.length();
                if (len == 0) {
                    pred = '\n';
                } else {
                    pred = mSpannableStringBuilder.charAt(len - 1);
                }
            } else {
                pred = sb.charAt(len - 1);
            }
            if (pred != ' ' && pred != '\n') {
                sb.append(' ');
            }
        } else {
            switch(c) {
                case '&':
                    sb.append('&')
                    break;
                case '<':
                    sb.append('<')
                    break;
                case '>':
                    sb.append('>')
                    break;
                case '\'':
                    sb.append('’')
                    break;
                case '"':
                    sb.append('"')
                    break;
                default:
                    sb.append(c);
                    break;
            }
        }
    }
    mSpannableStringBuilder.append(sb);
}


"bark" and "tortoise"

Is this two separate things, "bark" and "tortoise" or are you planning to somehow combine them so that "bark" can use the "tortoise" model?

They are separate models, if anything I suspect there might be a way to reuse tortoises generations for some bark usage, but that is ways off for now.
Bark has a fast response time, while tortoise can generate massive amount of variations quickly.

I still don't see this as being viable in the upcoming future.  The realistic usage right now is already possible - use tortoise to generate a wav and use it to clone voice in bark. And that's already possible as of now.


Fixed in 1e8170b4373c8e15a813ae1b1a74ea81d727bfd3


Faction Issue

NOT RUNNING CRACKED CW OR PIRATED I ASSURE YOU
So basically it only started recently, but the CWU faction that is using the same code as citizen wont save whitelists or characters.

This isn't an issue with the framework.
If you need help I'd suggest actually submitting your code and posting it in a relevant place.

im new to this system i DO NOT know how to use it.

As already mentioned by @netxdaguy, this isn't an issue with the Clockwork framework. This GitHub and the issues posted are meant to identify bugs/error with the Clockwork framework, not things that are for other schemas or custom code that's not working. You'd be better off posting your issue on CloudSixteen's Development forum section found here: http://forums.cloudsixteen.com/forums/development.18/
Be sure to include the code you're using and any errors from your server's console log.


add js_computed() and js_watch()

I propose to include add js_computed() and js_watch() in analogy to js_methods() and have submitted a draft PR #31
@essenciary Please comment what you think about that.

@hhaensel Thank you for the contribution, that makes a lot of sense!


Unedified name 'message'

import 'package:flutter/material.dart';
class progressDialog extends StatefulWidget {
String message;
progressDialog({this.message});
@override
_progressDialogState createState() => _progressDialogState();
}
class _progressDialogState extends State {
@override
Widget build(BuildContext context) {
return Dialog(
backgroundColor: Colors.yellow,
child: Container(
margin: EdgeInsets.all(15.0),
width: double.infinity,
decoration: BoxDecoration(
color: Colors.white,
borderRadius: BorderRadius.circular(6.0),
),
child: Padding(
padding: EdgeInsets.all(15.0),
child: Row(
children: [
SizedBox(width: 6.0),
CircularProgressIndicator(
valueColor: AlwaysStoppedAnimation(Colors.black),
),
SizedBox(width: 26.0),
Text(
message,
style: TextStyle(color: Colors.black, fontSize: 10.0),
)
],
),
),
),

);

}
}

I am trying to define "message" as a string and constructor below progressDialog but it can't be identified in the _progressDialogState extends State
Also the progressDialog({this.message}); can't be defined in the _progressDialogState extends State
Help please

To access a variable into state class (_progressDialogState class), you need define it as  widget.message instead of message. Also this place is not for assistance on personal code. Please see https://flutter.dev/community for resources and asking questions like this.

Hi @najamshidi
It seems you are asking for assistance on personal code. Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Update jawn-parser to 1.0.0-RC3

Updates org.typelevel:jawn-parser from 1.0.0-RC2 to 1.0.0-RC3.
Release Notes/Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

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

labels: library-update, semver-pre-release

Superseded by #1360.


chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
cde7189 -> 00d2055

github.com/google/uuid
require
minor
v1.5.0 -> v1.6.0

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
minor
v1.26.5 -> v1.27.0

Release Notes

google/uuid (github.com/google/uuid)
v1.6.0
Compare Source
Features

add Max UUID constant (#149) (c58770e)

Bug Fixes

fix typo in version 7 uuid documentation (#153) (016b199)
Monotonicity in UUIDv7 (#150) (a2b2b32)

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.27.0
Compare Source
Features

delete iam policy (#745) (82603f4)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline


android build fails

Bug Report

Version/Commit: version 1.0.0 sha d1f82cd057f404b12decb3b9ea788d995f717a68
Ionic Version: 4.12.0
Node.js / npm versionsNode: v10.15.3 npm: 6.4.1

Issue
android build fails
Steps to reproduce

checkout master
pull latest changes
npm i
run ionic cordova build android
Get the following failure

> Configure project :app
WARNING: Configuration 'compile' is obsolete and has been replaced with 'implementation' and 'api'.
It will be removed at the end of 2018. For more information see: http://d.android.com/r/tools/update-dependency-configurations.html
Could not find google-services.json while looking in [src/nullnull/debug, src/debug/nullnull, src/nullnull, src/debug, src/nullnullDebug]
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
Could not find google-services.json while looking in [src/nullnull/release, src/release/nullnull, src/nullnull, src/release, src/nullnullRelease]
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)

> Task :app:preBuild UP-TO-DATE
> Task :CordovaLib:preBuild UP-TO-DATE
> Task :CordovaLib:preDebugBuild UP-TO-DATE
> Task :CordovaLib:checkDebugManifest UP-TO-DATE
> Task :CordovaLib:processDebugManifest UP-TO-DATE
> Task :app:preDebugBuild FAILED
3 actionable tasks: 1 executed, 2 up-to-date

FAILURE: Build failed with an exception.

* What went wrong:
Could not resolve all files for configuration ':app:debugCompileClasspath'.
> Could not resolve com.android.support:support-v4:26.+.
  Required by:
      project :app
   > Failed to list versions for com.android.support:support-v4.
      > Unable to load Maven meta-data from https://jcenter.bintray.com/com/android/support/support-v4/maven-metadata.xml.
         > Could not get resource 'https://jcenter.bintray.com/com/android/support/support-v4/maven-metadata.xml'.
            > Could not GET 'https://jcenter.bintray.com/com/android/support/support-v4/maven-metadata.xml'. Received status code 502 from server: Bad Gateway

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 2s
/home/austincunningham/repos-cs/ionic-showcase/platforms/android/gradlew: Command failed with exit code 1 Error output:
FAILURE: Build failed with an exception.

* What went wrong:
Could not resolve all files for configuration ':app:debugCompileClasspath'.
> Could not resolve com.android.support:support-v4:26.+.
  Required by:
      project :app
   > Failed to list versions for com.android.support:support-v4.
      > Unable to load Maven meta-data from https://jcenter.bintray.com/com/android/support/support-v4/maven-metadata.xml.
         > Could not get resource 'https://jcenter.bintray.com/com/android/support/support-v4/maven-metadata.xml'.
            > Could not GET 'https://jcenter.bintray.com/com/android/support/support-v4/maven-metadata.xml'. Received status code 502 from server: Bad Gateway

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 2s
[ERROR] An error occurred while running subprocess cordova.

        cordova build android exited with exit code 1.

        Re-running this command with the --verbose flag may provide more information.

@austincunningham You are missing com.android.support:support-v4:26.+ in your system. However, I downgraded showcase as we should announce that change to a wider group of users so they will know how to resolve it in the future.
We will introduce this dependency on next release and provide an upgrade path.

23, 24 and 27 on the system so no 26


[Run]  Mouse hover color enhancement

 Environment
PowerToys v0.33.1 (DarkMode On)
Windows 10 - 20h2
 Steps to reproduce
Make any search with more than one result in PT Run, the keyboard selected option will have the same color as the item hovered by the mouse.
 Expected behavior
It would be nice to have a distinction between the colors of the selection and the mouse hover, or maybe additionally even hide the mouse hover when you start navigating using the keyboard.
 Actual behavior
The colors are the same.
 Screenshot

@dougwl What is your system's accent color?  On my system, my highlight is blue which corisponds to selected and mouse hover is grey,  I tested on light and dark mode and both worked as expected

I'm on 0.35, fyi

Hi, @crutkas, thank you for looking into my suggestion.
So, I've updated to 0.35 to be safe and changed my accent color, and yes that does change the selection color as can be seen in the screenshot below, but if I want to keep my current color or any other similar, I'm bound to keep having this problem.
Maybe, this can be solved making the mouse hover based on a gradient between the current accent and the default one from PT Run?
Luminance or analagous colors are other options, since this would avoid problems if the two colors are very similar.

See for reference:
https://www.w3.org/TR/2008/REC-WCAG20-20081211/#relativeluminancedef

In light mode, it is near impossible it seems like to get into trouble BUT this really shows up in dark mode but we're following base WinUI guidance for how colors work in dark mode.

Seeing where this feedback needs to be directed

This was fixed with the redesign of Run


[vm] use_code_comments_flag_test timing out on vm-aot-linux-release-simarm_x64

The tests
vm/dart/use_code_comments_flag_test Timeout (expected Pass)

are failing on configurations
vm-aot-linux-release-simarm_x64

Flaky -> Timeout
Log https://dart-ci.appspot.com/log/vm-aot-linux-release-simarm_x64/vm-aot-linux-release-simarm_x64/2770/vm/dart/use_code_comments_flag_test
Test history: https://dart-ci.web.app/#showLatestFailures=false&test=vm/dart/use_code_comments_flag_test&configurations=vm-aot-linux-release-simarm_x64
Test started being flaky on https://github.com/dart-lang/sdk/commit/f02007839d2268da89e83891b377c48f3ee8fcac. Maybe we should just give it double time on simarm.

I guess the status file change fixes this issue.


duplicate serial number in used certificates

Hi Matthias,
There is a duplicate serial number in the certificates used, it can lead to confusion.
openssl x509 -in interm.cert.pem -text |grep Serial
openssl x509 -in signer1.cert.pem -text |grep Serial

Hi Grzegorz,
IIRC there is no expectation of uniqueness for serial numbers, right? Only
the issuer<>serial combination is supposed to be unique AFAIK.
I’ll check X.509 and RFC 5280 when I’m at my desk. Anyway I’m pretty sure
that those certs have different issuers. :)
On Sun, 15 Jan 2023 at 05:34, Grzegorz Makarewicz @.***>
wrote:

Hi Matthias,
There is a duplicate serial number in the certificates used, it can lead
to confusion.
openssl x509 -in interm.cert.pem -text |grep Serial
openssl x509 -in signer1.cert.pem -text |grep Serial
—
Reply to this email directly, view it on GitHub
https://github.com/MatthiasValvekens/pyHanko/issues/206, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABREJH5KGHYZKCT7QKXBY2LWSN45LANCNFSM6AAAAAAT3UUZYU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

RFC 5280 has the following to say about uniqueness of serials (emphasis mine):

The serial number MUST be a positive integer assigned by the CA to
each certificate.  It MUST be unique for each certificate issued by a
given CA (i.e., the issuer name and serial number identify a unique
certificate).  CAs MUST force the serialNumber to be a non-negative
integer.

Indeed, checking both certs you mentioned shows that the serials coincide, but the issuer is different, so there should not be any confusion in practice. :)
$ openssl x509 -in root/interm.cert.pem -text -noout | grep -E '(Issuer|Serial)'
        Serial Number: 4097 (0x1001)
        Issuer: C=BE, O=Example Inc, OU=Testing Authority, CN=Root CA
$$ openssl x509 -in interm/signer1.cert.pem -text -noout | grep -E '(Issuer|Serial)'
        Serial Number: 4097 (0x1001)
        Issuer: C=BE, O=Example Inc, OU=Testing Authority, CN=Intermediate CA

In fact, you're right. However, this coincidence caused me a slight panic.

In fact, you're right. However, this coincidence caused me a slight panic.

For what it's worth (not much), the default behaviour of openssl ca is to assign serial numbers in increasing order starting from 4096. As such, there are tons of certs with coinciding serial numbers generated by openssl, but it's not an issue in practice since the issuers are different.
Since openssl ca is the tool I originally used to generate my test certs, I adopted a similar convention when I started Certomancer to take over that job.


Deleting annotations when writing a comment not possible

A click on the speech bubble opens an annotation and among other things, the wastebasket-icon appears. But clicking on the wastebasket has no affect. Only when I first close the commentary field I can delete this annotation.
Solution: Annotations should be deletable also when the commentary field is open..

Problem remains existing.

Problem still exists in the merged version.

Problem still exists in the branch "Stable".


feat: Add data availability oracle

Fixes #3890
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

Benchmark results
Metrics with a significant change:

l2_block_processing_time_in_ms (8): 1,564 (+16%)
note_successful_decrypting_time_in_ms (8): 383 (-20%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit a2b267bf and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
222,972
867,920
3,450,068

l1_rollup_execution_gas
936,305 (+8%)
3,970,583 (+6%)
24,793,793 (+6%)

l2_block_processing_time_in_ms
:warning: 1,564 (+16%)
5,093
21,082

note_successful_decrypting_time_in_ms
:warning: 383 (-20%)
1,113 (+1%)
4,146 (+1%)

note_trial_decrypting_time_in_ms
92.2 (+3%)
35.8 (-9%)
133 (-7%)

l2_block_building_time_in_ms
14,931
59,425
238,748

l2_block_rollup_simulation_time_in_ms
10,604
42,187
170,173

l2_block_public_tx_process_time_in_ms
4,297
17,094
68,307 (+1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
15,397 (+2%)
29,399 (+1%)

note_history_successful_decrypting_time_in_ms
2,756 (+3%)
5,565 (+1%)

note_history_trial_decrypting_time_in_ms
109 (-1%)
145 (-2%)

node_database_size_in_bytes
3,621,289
3,722,804

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
211
44,709
25,561

private-kernel-ordering
137
30,953
14,809

base-rollup
1,077
128,374
881

root-rollup
82.7 (-2%)
4,088
889

private-kernel-inner
287
71,236
25,561

public-kernel-private-input
203
31,891
25,561

public-kernel-non-first-iteration
201 (+1%)
31,933
25,561

merge-rollup
9.78 (+1%)
2,608
881

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
2 leaves
8 leaves
16 leaves
32 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
8192 leaves

batch_insert_into_append_only_tree_ms
11.1 (-1%)
92.2 (+4%)
13.7 (-2%)
17.8 (-1%)
23.7 (+1%)
50.1
90.1 (+2%)
240 (-2%)
472
906
3,561

batch_insert_into_indexed_tree_ms
N/A
N/A
N/A
64.5
N/A
59.7 (+1%)
111
358 (-2%)
742 (+1%)
1,397
5,553

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
15,487
31,877

Transaction processing duration by data writes.

Metric
0 new commitments
1 new commitments

tx_pxe_processing_time_ms
346 (+1%)
973

Metric
1 public data writes

tx_sequencer_processing_time_ms
531


Optimize AssetRegistry.find and findAll

Improves AssetRegistry.find and findAll performance, by building and managing internal index of assets by names. And avoids casting large asset lists to arrays during these methods to avoid GC stalls.
In a project with around 2.5k of assets, calling find was taking around 0.04ms per request. With this patch it takes around 0.00006ms. This is around ~666 times improvement.
findAll used to take 0.04ms per request also, now it takes 0.0006ms. ~66 times improvement.
In specific project, during custom scene loaders that reference assets by names, it used to take around 200ms just finding assets, now it takes 0.25ms.
Timings are just a relative measurement and based on hardware.
It only highlights the performance change between versions.
Tested on high-end computer, so on mid/low/mobile it is even more apparent improvement.
I confirm I have read the contributing guidelines and signed the Contributor License Agreement.

Nicely done - thanks!! 🙏


Fix error return values from BIO_ctrl_(w)pending()

The BIO_ctrl_(w)pending() functions did not check for negative returns of underlying BIO_ctrl() call and cast it to size_t.
Checklist

[x] documentation is added or updated

This pull request is ready to merge

Merged to master and 3.0. Thank you.


[Valora] Pre-request 5, reveal 4th/5th attestation only if original 3 are not all received

Optimization on re-request flow.
Requires onchain changes to allow for attestation cancelation.
Optimization -- make this contextual, only in countries/carriers known to cause errors.

related to https://app.zenhub.com/workspaces/celo-5d94ef61d9b1e40001114c02/issues/celo-org/celo-monorepo/5373
this is assuming that user failures during this request phase are significant and we want to avoid sending user through the phase again.
Updates in handling transactions and komenci have been pushed in the latest version showing that drop off during this phase due to error, cancelation, and app close is low (92% drop between verification_request_all_attestation_start and verification_request_all_attestation_complete from test users)
data visual here
We've hesitated on making this change as it would negatively impact Validators attestation completion rates. With low traffic, it would be hard to differentiate completion failure percentages being low due to validator issues or intentional client incompletion.
I'd suggest we revisit this item if we see an ongoing issue with REAL users dropping off during request phase or as a UI optimization if significant number of users are re-requesting more issuers.
(cc @nityas)


Gifts getting passed around not getting accepted

I was testing the gift flow with Anant.
I had 2 kinds of gifts: 1) Freshly created gifts. 2) Ones that I had created earlier, had sent out earlier, and got back as they were unclaimed.
The first kind went and was accepted easily. Regarding the second kind, the app said gift expired in receiver phone and rejected in sender phone.
Also, the phone in which it said rejected... when I tried to reclaim the gift, the app just didn't respond. It didn't crash. But no response to the reclaim call to action.

When user Clicks on accept gift the screen doesn't respond.

After Accepting a gift this loading screen appears on the screen


Enable improved depth testing for all billboards

Fixes #6762
Now that we can do the billboard depth texture lookups in the vertex shader, I think it's safe to enable this option for all billboards instead of only when they're clamped to ground.
I did some performance testing using some of our sandcastle examples like the KML, BillboardClampToGround and Billboards Instancing Sandcastle examples and saw no differences in performance.
@bagnell can you review?
TODO

[ ] Fix #6840
[ ] Fix #6838 (or do something different than use disableDepthTestDistance)
[ ] CHANGES

Thanks for the pull request @hpinkos!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

I also bumped up the default depth testing range from 2000 to 4000.  I found 2000 to be a little too close in practice.

Well, now that I increased the range I do see a bit of a performance hit for a lot of billboards in a small area.
Sandcastle
I think I'll put this behind a flag instead.  I'm thinking it should default to true and people can disable it if they're seeing a performance impact and they don't need the feature.

Actually, I'm not sure if it's a performance issue.  There's something weird with zooming in and out though when you're at this angle:

The FPS doesn't drop and panning around still works fine, but zooming in and out kind of stops working.
@bagnell do you have any idea why that would be?

Looks like the zooming problem is the camera picking the depth buffer for the collision detection and it's picking the billboards. The problem is that billboards are pushed to the near plane when within the disabled depth test distance. I'm not sure how we fix this. There is a fallback for picking the terrain using ray-triangle intersections but we rely on picking the depth buffer so the camera doesn't go through 3D Tiles.

@bagnell okay, so this is an existing issue with disableDepthTestDistance
@pjcozzi what do you recommend we do here?

The problem is that billboards are pushed to the near plane...

What are the other options:

Separate depth buffer for collision detection / environment - doesn't need to be a separate render pass could just GPU-to-GPU copy the depth buffer - this is also needed for polylines on 3D Tiles, CC @ggetz
Maybe a gl.clear at the right time with a separate render pass for billboards/labels/points.  I dunno.
Bump by a fudge factor instead of all the way to the near plane?  Could be hard in practice.

We should also ask if we ever want collisions with billboards/labels/points, I suspect not.
Perhaps also chat with @lilleyse if he has bandwidth and ping me if you run out of ideas.

Separate depth buffer for collision detection / environment - doesn't need to be a separate render pass could just GPU-to-GPU copy the depth buffer - this is also needed for polylines on 3D Tiles, CC @ggetz

There are no GPU-to-GPU copies for depth buffers.

Maybe a gl.clear at the right time with a separate render pass for billboards/labels/points.  I dunno.

We can't clear the depth since we determine whether to depth test in the vertex shader. Some billboards may need to be depth tested while others are moved to the near plane so they are not.

Bump by a fudge factor instead of all the way to the near plane?  Could be hard in practice.

This could work, but I also think it could be hard in practice.
Other options:

Have two depth buffers and use the previous depth to render the billboards and the current depth for collision detection.
Render billboards last and have them enable the depth test but disable depth writes.

With both of these options, pickPosition wouldn't work on billboards.

For testing, search for depthMask in BillboardCollection.js and set them to false.
Is there anything we can to for top-down views? The billboards blink in and out when zooming.

Is there anything we can to for top-down views? The billboards blink in and out when zooming.

@bagnell I added a value to the depth check.  It seems to fix the flickering without causing the billboards to show through the terrain when they shouldn't.

Top-down views look much better for the linked Sandcastle example.

I'm seeing 10 test failures for billboards and labels.

@bagnell fixed the test failures.  I changed billboard.disableDepthTestDistance to default to undefined instead of 0.  That way the end user can explicitly set it to 0.  Otherwise it defaults to 5000 for the depth test thing.
Let me know when you're free to chat about the camera collision thing

@pjcozzi Dan and I discussed offline, and we decided that due both #6840 #6838 needing a non-trivial amount of work, we will put this option behind a flag and disable it by default.  Does that sound okay to you?

After a discussion with @mramato, I don't want to merge this in until #6840 (and ideally #6838) are fixed.  I ran the KML example in sandcastle and you can run into the bad mouse behavior pretty easily.  I don't think it makes sense to put this behind a flag because then we're more-or-less pushing through a feature that is fundamentally broken for no good reason other than to get it in.  It's currently enabled for billboards that are clamped to ground which I think covers the most common use case for this anyway.  We'll just leave it at that for now.

I had a few minor fixes in this PR, I'll open up a new PR for them

Thanks again for your contribution @hpinkos!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

@cesium-concierge stop

Closing this since we probably won't be able to merge this in the near term


Fixes cross-repo blob mounting in the BlobUploadHandler

Accidentally checked for err != nil instead of err == nil :/
Also now ensures that only a non-nil option is appended to the create
options slice

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

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

Current coverage is 58.00%

Merging #1348 into master will increase coverage by +3.35% as of 3ef917c

@@            master   #1348   diff @@
======================================
  Files          108     123     +15
  Stmts         9727   11098   +1371
  Branches       635     776    +141
  Methods          0       0
======================================
+ Hit           5316    6437   +1121
- Partial        635     776    +141
- Missed        3776    3885    +109

Review entire Coverage Diff as of 3ef917c

Uncovered Suggestions

+0.28% via ...ge/driver/gcs/gcs.go#185...216
+0.28% via ...ge/driver/gcs/gcs.go#104...135
+0.21% via ...ge/driver/gcs/gcs.go#474...497
See 7 more...

Powered by Codecov. Updated on successful CI builds.

LGTM


docs: remove await outside of an async function in example

See #549.

Thanks @RichardLitt! You're right the issue is the three lines in the example should be called within an async function. But .log is async and will return a promise

Thanks, Shams. How does this look?

@RichardLitt one last comment! :D

Thank you @RichardLitt ! :+1:


improve UX in MultiSig page with owners/sig count

[x] ensure we don't get NaN float issues for sig count (resolved in 9f91ac69bf2ef78b70891298f09981c69daa61a5)
~enter needs to be linked to submit~ (moved to #122)
[ ] see if we can somehow make it possible to more easily select an address of us

see if we can somehow make it possible to more easily select an address of us

We should make these kind of text fields an AutoComplete component with as suggestions array:

wallet names
all our addresses (that make sense)

In future we can also add to such arrays:

contact names
contact addresses


New release for Android Pie?

I see that you updated the git repository for Android 9 "Pie" about 10 days ago. I would like to update the Debian/Ubuntu package but I was waiting for a release tag to be pushed first. Is there anything you still need done before pushing the release tag?

Have been on vacation, and was waiting for some external verification of the font.  Haven't heard anything negative so I will tag it.

Thanks!


[nemo-qml-plugin-calendar] Factorise code between classes sharing eve…

…nt characteristics.
@pvuorela , this is a proposition to factorise a bit of code in nemo-qml-plugin-calendar.
Create a base class Event, based on CalendarData::Event struct,
from which inherit:

a StoredEvent class for events owned by a Manager,
a EventModification class to create new events or
modify data from StoredEvent instances,
a ImportEvent class for events read from ICS data
and not stored on device.

These classes mainly reuse the existing code or
class layouts.
All code handling transformations from an to
KCalendarCore::Event have been gathered and moved
to the CalendarData::Event structure.
This last part is to avoid to have this transformation code scaterred in utils and worker, like it was before. Often, when adding a new member in CalendarData::Event structure to mirror one from KCalendarCore, I forgot to put it in utils, so it can be seen from CalendarImportEvent also for instance. And when moving away from CalendarData::Event in favour of KCalendarCore::Incidence, the affected code will be less scattered also.
What do you think ? As a bonus, it is reducing the code volume by 200 lines ;-)

I've rebased and corrected the compilation issue in the tests.


GTA V patch results in bad image

After patching GTA V, when launching I recieve this error message.
GTA5.exe - Bad Image
C:\Program Files\LGHUB\sdks\sdk_legacy_led_x64.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0xc000012f.
Devices-2024-03-24 10.31.07.log
2024-03-24 10.31.02.log
Edit: Forgot to mention I'm using the Logitech G915 TKL and G502 Lightspeed

GTA integration doesn't work right now.
You should delete the patch until it is fixed

You can just disable GTA5 profile in Aurora as you can just use Lightsync profile with it


Filter out source node from Nodes response

What was wrong?
While I was debugging the flakiness in #851, I noticed that quite often we see the error ~ Unable to insert node into routing table, invalid self update. Indicating that a node is trying to add itself to its own routing table, since it is present in the Nodes response from a peer.
This didn't completely resolve the source of the flakiness, but it did get rid of that warning. It seems like a prudent choice to filter out the source node from a Nodes response. This behavior is not specified in the spec, so this would be a client team's implementation decision. However, it might be a good idea to add this to the spec as well?
Another solution would be to filter the "self" enr from the Nodes response on the receiving end (eg. before trying to add it to the routing table) rather than filtering it when constructing the response on the sending end. I'm not sure there are any advantages to this over the solution in this pr. And the solution in this pr results in slightly smaller network messages.
How was it fixed?
Filter out source node from a Nodes response.
To-Do

[ ] Add entry to the release notes (may forgo for trivial changes)
[ ] Clean up commit history

I think if this is not specified in the specs, we need to first bring the issue to https://github.com/ethereum/portal-network-specs for discussion and then implement it.

This pr is now ready for review after https://github.com/ethereum/portal-network-specs/pull/230 was merged into the specs.


Plug memory leak for never closing img mats 😒

Codecov Report

Merging #60 (9dcfa2c) into main (b0a68fe) will decrease coverage by 0.23%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##             main      #60      +/-   ##
==========================================
- Coverage   38.77%   38.53%   -0.24%
==========================================
  Files          10       10
  Lines         815      820       +5
==========================================
  Hits          316      316
- Misses        468      473       +5
  Partials       31       31

Impacted Files
Coverage Δ

pkg/media/connection.go
54.65% <33.33%> (-1.09%)
:arrow_down:

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 b0a68fe...9dcfa2c. Read the comment docs.


fix: replaced JWT library with web-compatible one

Could you replace the hardcoded tokens in the examples and call this authToken instead please? :-)


[Graded Games List] Filters/Sort Orders

A few suggestions came up here https://ldjam.com/events/ludum-dare/40/babies-babies-babies/we-should-be-better-at-announcing-new-features-my-graded-games-list

Sort based on average grade given by me
Sort based on theme/sound/fun/mood/overall grade given by me
Sort based on weather i have commented on the game.

I started working on the sorting but not so much these since they require new endpoints in the API to get the data needed
From gitter.im

[...] add an API call that returns everything given an event's node_id as input.

I actually want the same type of API endpoint as for grades that would return the node id:s for all nodes in an event that I've commented on.

#1518 Has sorting implemented, it is just waiting for the relative endpoints to add the above suggested sort-options.

Only thing missing from #1518 now is if commented on or not


forking a compiled script from an electron production app

In my case, most of my business logic is run in a separate process, which I bundle into a single js file and then fork from the renderer.
In development I've got forking working, taking care that I compile the js against electron locally available. I also use the "trick" as per https://github.com/bytenode/bytenode/issues/103#issuecomment-780516725 which utilizes the executable in the .bin folder.
However, where it gets hairy is in production, i.e., after bundling the whole things using electron-builder. I am aware that the js file should be compiled against the electron version cached by electron-builder, which is not the one locally available under node_modules/electron but kept in a cache folder.
I also kept the bytenode module among those which are packaged into the asar archive.
However, none of this seems to work, it's not forking the process. I think it's because the bytenode executable cannot be executed to create the child process since it's spawned with node which is (I guess?) not locally available in production.
Is there some way to make this work?
Ps: Please forgive me for this one https://github.com/bytenode/bytenode/issues/182, this was a mistake

Have you tried without ASAR enabled? Things can get weird putting binaries in the asar file.

Hi @jjeff, thanks for your feedback. Yes, you're right, I can confirm that with asar turned off it works good.
However, electron-builder notifies me:
asar usage is disabled — this is strongly not recommended  solution=enable asar and use asarUnpack to unpack files that must be externally available
I'd myself too rather keep asar enabled. Is there perhaps a way that we could leverage asarUnpack to achieve the same result? I highly appreciate your thoughts.

Ok, I've got it working myself without disabling asar.
In electron-builder.json, instead of asar: false I put
"asarUnpack": [
    "node_modules/bytenode"
  ]

This will keep the bytenode module outside of the asar. Then to fork the compiled process I can use
cp.fork(
    path.resolve(appPath, 'something_hidden.jsc'), // this is contained within the asar
    [],
    {
        execArgv: ['-r', path.resolve(appPath, '..', 'app.asar.unpacked', 'node_modules', 'bytenode')],
        env: {...}
    }
)

Now just to automate and clean up the build process.

Yeah. I just meant to try it without asar to see if that was the source of the problem. I think you're on the right track with asarUnpack.
For anyone listening in, it is possible to keep your bytenode .jsc files in your asar file.
The source of this problem may have more to do with the subprocess trying to access the asar rather than something bytenode-specific.

Yes I agree, that's why I documented how I achieved it and emphasized that the jsc is still in the asar. Thanks for your input, it put me in the right direction.


doesnt work

Vineflower version
vineflower-1.10.1
Describe the bug
gives errors in terminal
Additional information
java -jar vineflower-1.10.1.jar navine-3.2.8.jar src
Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/jetbrains/java/decompiler/main/decompiler/ConsoleDecompiler has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:473)
at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:621)

Ensure that you are using the right version of Java. I believe the 1.10 releases use Java 11.
You seem to be using Java 8, which of course won't work.
if absolutely necessary, you could try out tools such as JavaDowngrader (https://github.com/RaphiMC/JavaDowngrader)

Yes, Vineflower 1.9+ requires Java 11 or higher, while you have Java 8 installed.

Ensure that you are using the right version of Java. I believe the 1.10 releases use Java 11. You seem to be using Java 8, which of course won't work.
if absolutely necessary, you could try out tools such as JavaDowngrader (https://github.com/RaphiMC/JavaDowngrader)

how do  i switch java i have installed 11, 17, 18, 21

This is an issue tracker, not a help forum.
Otherwise: On linux: using the alternatives command or similar. On other plattforms: I do not know


Midnight false alarms

HAL sends false alarms at around midnight every night as seen below:

This is most likely due to the fact the BLUEFORS logging software has not finished updating the newly created log files for the day. HAL logs show there are no timestamps in the parsed BLUEFORS logs so checking for the existence of timestamps should fix this problem.

Fixed in #7


DbContext.Database.ExecuteSqlCommand should return rows affected

In EF6 the method returns an int for rows affected... currently the method is void in EF7.

Fixed in #3738


Sync eng/common directory with azure-sdk-tools repository

Sync eng/common directory with azure-sdk-tools repository

CredScan failure is a false positive calling out the testproxy dev cert. Currently we don't have a suppression file so I'm going to override. However, once we move that check out of the alps then we should share the common credscan template under eng/common and add a suppression.


Including appmetrics breaks promisified setTimeout

node v12.10.0, appmetrics v5.1.1
Test case:
'use strict'

const { promisify } = require('util')
const delay = promisify(setTimeout)

async function main () {
  console.log('Hello...')
  await delay(1000)
  console.log('...world!')
}

main().then(() => process.exit(0), e => { console.error(e); process.exit(1) })

Result without appmetrcis:
david@CHE-X1:~/z/Temp/appmetrics-test $ node index.js
Hello...
...world!

Result with appmetrics:
david@CHE-X1:~/z/Temp/appmetrics-test $ node --require appmetrics/start index.js
[Sat Mar 14 16:15:16 2020] com.ibm.diagnostics.healthcenter.loader INFO: Node Application Metrics <IP_ADDRESS>003141613 (Agent Core 4.0.5)
[Sat Mar 14 16:15:16 2020] com.ibm.diagnostics.healthcenter.mqtt INFO: Connecting to broker localhost:1883
Hello...
TypeError [ERR_INVALID_CALLBACK]: Callback must be a function. Received 1000
    at setTimeout (timers.js:118:11)
    at fallback (/mnt/c/Users/david/Temp/appmetrics-test/node_modules/async-listener/index.js:621:15)
    at /mnt/c/Users/david/Temp/appmetrics-test/node_modules/async-listener/index.js:651:53
    at internal/util.js:277:30
    at new WrappedPromise (/mnt/c/Users/david/Temp/appmetrics-test/node_modules/async-listener/es6-wrapped-promise.js:13:18)
    at internal/util.js:276:12
    at main (/mnt/c/Users/david/Temp/appmetrics-test/index.js:8:9)
    at Object.<anonymous> (/mnt/c/Users/david/Temp/appmetrics-test/index.js:12:1)
    at Module._compile (internal/modules/cjs/loader.js:936:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:947:10)

It seems as if for some reason promisify would not respect setTimeout's custom util.promisify.custom handler in this case!
EDIT: After further testing, it seems that after including appmetrics/start, for some reason setTimeout and setImmediate are now missing the util.promisify.custom symbol property entirely! Also, confusingly, this does not happen when I do it from a node REPL.

Same here for Node v13.0.1. But it's the async-listener package that's causing this since it's overriding the core Promise class with a custom one WrappedPromise.
`--<EMAIL_ADDRESS>  `--<EMAIL_ADDRESS>    `--<EMAIL_ADDRESS>      `--<EMAIL_ADDRESS>        `--<EMAIL_ADDRESS>
this is the dependency package list for which package requires what ending at the async-listener package.


[Proposal] Implementing @subscribed('plan') directive

I was thinking about implementing custom blade directives like
@subscribed('main')
// only subscribers
@endsubscribed

Should that be fine ?

Yeah I can see this being useful. Feel free to retry your PR with the feedback from Taylor.


How to get byte array output from  serialize and deserialize methods?

HI.
First, i want to appreciate you for share your great library.
I want to get binary data(as byte array) from output of serialize method. but it only send data to physical file that mention in oStream parameter. i just need that binary data without operation on file. how to do that?
Iin other side, i want to deserialize binary data(in byte array) to origin datatype, not from binary file but from an array without open any file. how to do that?
thanks in advance

You can just to the steps to deserialize the fronttal_face_detector from the
https://github.com/davisking/dlib/blob/23b9abd07a56f9fef560aa9e263b37f82543a0cc/dlib/image_processing/frontal_face_detector.h#L2353-L2367
That is exactly what I did in one small project, which you can find here:
https://github.com/arrufat/wallyfinder/blob/789e71a3e442547d39945c6997e7bc42f4503082/src/detector.h#L8-L29
dlib::deserialize(model_path) >> net;
std::ostringstream sout;
std::istringstream sin;
dlib::base64 base64_coder;
dlib::compress_stream::kernel_2a compressor;
// put the data into ostream sout
dlib::serialize(net, sout);
// put the data into istream sin
sin.str(sout.str());
sout.str("");
// compress the data
compressor.compress(sin, sout);
sin.clear();
sin.str(sout.str());
sout.str("");
// encode the data into base64
base64_coder.encode(sin, sout);
// print the data on the terminal
std::cout << sout.str() << std::endl;

Thank you guy that cool.

Right, use the string streams and you can read and write whatever you want to them.

yah you are right. thanks again


wayland artefacts in silverblue (rpm-ostree) in new version 1.76.1

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:  1.76.1
OS Version:
rpm-ostree --version output
rpm-ostree:
Version: '2023.1'
Git: 81c496fe887235bcf4a586dcc9312703e94c2b62
Features:

rust
compose
container
fedora-integration

uname -a output
Linux fedora 6.1.14-200.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Feb 26 00:13:26 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Steps to Reproduce:

run vscode
open firefox or some other app in the background, and switch between that app and vscode
a black box with white writing (I am using a dark theme), is left over the top of vscode menu bar.
if I drag the vscode title bar away from under the box, it disappears, and then I can remaximize vscode without any artefact blocking my view.
this doesn't happen if I use the earlier version 1.76.0
I am using libvirt and virtmanager to create a fedora silverblue virtual machine, in which I am developing, so my podman containers and my vscode instance are inside that fedora silverblue image.   My host is also silverblue.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.76.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Wow, thanks bot.  It works!  Version 1.76.2 no longer displays artefacts


First draft of parameter syntax CIP

It would be nice if this PR also updated the grammar.
Quite probably we should remove Sc from IdentifierStart - i.e. not allow any currency signs as the first character of an identifier.

CLG discussion comments have been addressed. This CIP should now be mergeable.


Blame annotations don't caclulate new margin when scrolling to zoom in VS code

GitLens Version: 10.2.2
VSCode Version: 1.50.1
OS Version: Windows NTx64 10.0.19042

Steps to Reproduce:

Enable "Mouse Wheel Zoom" in VS Code Settings
Enable "Block scope" under "Git Code Lens" > "Add code lens to the following scopes" > "Block scope"
Scroll to zoom in or out

Expected Result: The proportion of margin between the code lens and the adjacent code element should remain constant
Actual Result: The code lens text begins to grow closer or further away from the code portion

@JasonDiBabbo This is actually a bug in VS Code. Can you open this against the vscode repo please?


Overlaps between jupyter UI and terminal&vscode UI

Environment data

VS Code version: 1.58.2 c3f126316369cd610563c75b1b1725e0679adfb3 x64
Jupyter Extension version (available under the Extensions sidebar): v2021.8.1046824664
Python Extension version (available under the Extensions sidebar): v2021.6.944021595
OS (Windows | Mac | Linux distro) and version: Windows 10 & Ubuntu 20.04
Python and/or Anaconda version: conda 4.10.3
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): None
Jupyter server running: Local

Expected behaviour
There should be no UI overlaps.
Actual behaviour
There actually are UI overlaps between jupyter and terminal, vscode both on Ubuntu and Windows OS.
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
Windows:
Just open a .ipynb file and call a terminal. Just like below:

After I click the button in the green box to maximize the terminal. The bottons in the red boxes will overlap, like this:

There are overlaps between jupyter buttons and vscode buttons(File, Edit, etc)
Ubuntu:
Way to reproduce on Ubuntu is quite similar. But the result is different:

You can see there are  overlaps between  jupyter buttons and terminal buttons.

Fixed in main. THanks for reporting.


Unhandled false return from riak_index:object_key_in_range

This case statement https://github.com/basho/riak_kv/blob/develop-2.9/src/riak_kv_leveled_backend.erl#L405 should handle a possible return of 'false' from riak_index:object_key_in_range, due to this line here:
https://github.com/basho/riak_kv/blob/develop-2.9/src/riak_index.erl#L469
I got the pattern match error while playing with RiakCS using leveled as backend. Listing directories via the s3 API would trigger the error under some situations I couldn't  reproduce reliably.

Any clues at all about the conditions?  It will help me generate a riak_test test.
I can match the riak_kv_eleveldb_backend code to resolve this I assume - https://github.com/basho/riak_kv/blob/develop-2.9/src/riak_kv_eleveldb_backend.erl#L854-L855

@martinsumner I still have to figure out how RiakCS  maps paths to keys to come up with a test case that does not depend on running RiakCS. This was the simpler case to reproduce via the S3 API:
When using leveldb backend
~ ❯❯❯ s3cmd mb s3://mybucket                                                                                ⏎
Bucket 's3://mybucket/' created
~ ❯❯❯ s3cmd put test.txt s3://mybucket/foo/bar/baz/test.txt                                                                                ⏎
upload: 'test.txt' -> 's3://mybucket/foo/bar/baz/test.txt'  [1 of 1]
 4 of 4   100% in    0s    85.65 B/s  done
~ ❯❯❯ s3cmd put test.txt s3://mybucket/
upload: 'test.txt' -> 's3://mybucket/test.txt'  [1 of 1]
 4 of 4   100% in    0s    91.32 B/s  done
~ ❯❯❯ s3cmd ls s3://mybucket/foo/
                       DIR   s3://mybucket/foo/bar/

When using leveled backend
~ ❯❯❯ s3cmd mb s3://mybucket                                                                                ⏎
Bucket 's3://mybucket/' created
~ ❯❯❯ s3cmd put test.txt s3://mybucket/foo/bar/baz/test.txt
upload: 'test.txt' -> 's3://mybucket/foo/bar/baz/test.txt'  [1 of 1]
 4 of 4   100% in    0s    78.07 B/s  done
~ ❯❯❯ s3cmd put test.txt s3://mybucket/
upload: 'test.txt' -> 's3://mybucket/test.txt'  [1 of 1]
 4 of 4   100% in    0s    97.81 B/s  done
~ ❯❯❯ s3cmd ls s3://mybucket/foo/
connection without response)
WARNING: Waiting 3 sec...
^CSee ya!

The 'ls' crashed Riak with the error:
root@riak-kv:/# cat /var/log/riak/error.log
2020-06-08 13:08:10.104 [error] <0.1474.0> gen_server <0.1474.0> terminated with reason: no case clause matching false in riak_kv_leveled_backend:'-fold_objects/4-fun-0-'/9 line 405
2020-06-08 13:08:10.104 [error] <0.1474.0> CRASH REPORT Process <0.1474.0> with 0 neighbours exited with reason: no case clause matching false in riak_kv_leveled_backend:'-fold_objects/4-fun-0-'/9 line 405 in gen_server:terminate/6 line 744
2020-06-08 13:08:10.105 [error] <0.1467.0> Supervisor {<0.1467.0>,poolboy_sup} had child riak_core_vnode_worker started with {riak_core_vnode_worker,start_link,undefined} at <0.1474.0> exit with reason no case clause matching false in riak_kv_leveled_backend:'-fold_objects/4-fun-0-'/9 line 405 in context child_terminated

When 'riak_index:object_key_in_range/3' returns false, the leveldb backend halts the folding and returns the last accumulator.
Next I'll look into the 'ls' implementation of RiakCS to come up with a reproducible test case directly on riak-kv.

There already is a riak_test for this as it happens:
https://github.com/basho/riak_test/blob/develop-2.9/tests/verify_cs_bucket.erl
And it passes on eleveldb, and fails on leveled with the failure you detect.
This test was never included in the kv release set, so I hadn't noticed it before.
I will confirm the fix today, and add the test in for the future.

The problem is also related to the fact that we don't handle the start_key correctly in query, and so  we're always scanning the whole bucket.  Should have a fix tested this weekend.

I've extended he test to make sure it covers all start/end inclusive/exclusive scenarios:
https://github.com/basho/riak_test/pull/1347
Test now included in standard test suite to be run for each release