NV21 to JPG

how do i convert NV21 to jpg?
Before, in the older version that gave me the image in YUV, I did the conversion to JPG using dart's own "image" package. now with this version that generates the image in NV21 and I can no longer use the same conversion method, can anyone help me?
previously used method:
`static Future<List> convertCameraImageToImage(
CameraImage cameraImage) async {
if (Platform.isAndroid) {
final DynamicLibrary convertImageLib = Platform.isAndroid
? DynamicLibrary.open("libconvertImage.so")
: DynamicLibrary.process();
  _conv = convertImageLib
      .lookup<NativeFunction<convert_func>>('convertImage')
      .asFunction<Convert>();
}

//ranulfo - 20230615 - início

imglib.Image? img;
if (Platform.isAndroid) {
  Pointer<Uint8> p = calloc(cameraImage.planes[0].bytes.length);
  Pointer<Uint8> p1 = calloc(cameraImage.planes[1].bytes.length);
  Pointer<Uint8> p2 = calloc(cameraImage.planes[2].bytes.length);

  // Assign the planes data to the pointers of the image
  Uint8List pointerList = p.asTypedList(cameraImage.planes[0].bytes.length);
  Uint8List pointerList1 =
      p1.asTypedList(cameraImage.planes[1].bytes.length);
  Uint8List pointerList2 =
      p2.asTypedList(cameraImage.planes[2].bytes.length);
  pointerList.setRange(
      0, cameraImage.planes[0].bytes.length, cameraImage.planes[0].bytes);
  pointerList1.setRange(
      0, cameraImage.planes[1].bytes.length, cameraImage.planes[1].bytes);
  pointerList2.setRange(
      0, cameraImage.planes[2].bytes.length, cameraImage.planes[2].bytes);

  // Call the convertImage function and convert the YUV to RGB
  Pointer<Uint32> imgP = _conv(
      p,
      p1,
      p2,
      cameraImage.planes[1].bytesPerRow,
      cameraImage.planes[1].bytesPerPixel!,
      cameraImage.width,
      cameraImage.height);
  // Get the pointer of the data returned from the function to a List
  List<int> imgData =
      imgP.asTypedList((cameraImage.width * cameraImage.height));

  //ranulfo 20230615 - inicio
  Uint8List uint8List = Uint8List.fromList(imgData);
  ByteBuffer byteBuffer = uint8List.buffer;
  //ranulfo 20230615 - fim

  img = imglib.Image.fromBytes(
      height: cameraImage.height,
      width: cameraImage.width,
      bytes: byteBuffer /*imgData*/);

  calloc.free(p);
  calloc.free(p1);
  calloc.free(p2);
  calloc.free(imgP);
  img = imglib.flip(img, direction: imglib.FlipDirection.vertical);
} else if (Platform.isIOS) {
  img = imglib.Image.fromBytes(
    //cameraImage.planes[0].bytesPerRow,
    width: cameraImage.width,
    height: cameraImage.height,
    bytes: cameraImage.planes[0].bytes.buffer,
    format: imglib.Format.bgra, //ranulfo 20230615
  );
}
var imgJpg = imglib.encodeJpg(img!, quality: 70);

return imgJpg;

}`

This plugin does not provide conversion from CameraImage or InputImage to JPG.
However, I hope this helps: NV21 has only 1 plane, and YUV 3, try to use the same plane for the others or convert it with a single plane like in iOS. Basically NV21 and BGRA8888 are the same in terms of having a single plane, you can use _convertBGRA8888 like in this post: https://gist.github.com/Alby-o/fe87e35bc21d534c8220aed7df028e03

I already tried to use this method for nv21 images and it doesn't work. but it is worth remembering that in the new version of image.dart image: ^4.0.17, the fromBytes method was changed and the bytes parameter now expects a ByteBuffer type and the format parameter is now an enum of type:
enum Format {
  uint1,
  uint2,
  uint4,
  uint8,
  uint16,
  uint32,
  int8,
  int16,
  int32,
  float16,
  float32,
  float64
}

causing the call to result in an error
var img = imglib.Image.fromBytes(
      width: cameraImage.width,
      height: cameraImage.height,
      bytes: cameraImage.planes[0].bytes.buffer,
      format: imglib.Format.uint8,
    );

RangeError (RangeError (end): Invalid value: Not in inclusive range 518400..518586: 520560)

Please, reopen this issue

@ranulfo: you issue is outside of our scope, you are trying to convert CameraImage to Image, and those classes belong to other plugins, I recommend you go to the repos for those plugins and post your issue there: How to convert CameraImage to Image when using nv21.

You can use this convert_native_img_stream to convert. It work so well.


brew cu doesn't update properly latest version of app

For an unknown reason, one of my macs isn't updating properly the latest version of the apps.
As an example, as of today, latest version of firefox is 91.0.1 and is shown as such on my Mac #1 and is getting properly updated
On the other hand, if I run brew cu on Mac #2, the latest version is showing 90.0.2
This is valid for also other apps.
To me it looks like the 'list of latest available versions' is not updated properly
Has anyone some suggestions (files, folders, configs) I should look at?

Fix:
git -C $(brew --repo homebrew/cask) checkout master
My mistake, Brew was not on the default branch anymore - Nothing to do with homebrew-cask-upgrade.


Dashboard Menu Icon is not centered

Describe the bug

To Reproduce
I run 2 monitors one 3440x1440 and one 1080x1920
Doesn't matter which of the two monitors I use the dashboard Icon is off center
happens for both the Autodetected Icon and the Manual one,
when increaing the margins or padding of the icon the it is still off center
different fonts do not change anything, no matter which font I take, monospace of not it is always off center
Expected behavior
Icon should be centered in the button
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: NixOS 25.05.20241128.970e93b (Warbler) x86_64-linux
DE: Hyprland (Wayland)
Additional context
I feel like it worked at some point and then stopped working, it was never a big issue, but I thought I should report it anyways

i get the same with the nixos logo too

same issue

@jukefr @FarokhRaad @Daholli Even after following this: https://hyprpanel.com/help/faq.html#why-are-my-icons-misaligned ?

I mean all other icons work perfectly just the dashboard doesn't, but also I am in Australia right now and cannot test much more until the new year


Fix typo in dr diff error message

Fixes a small typo in a deploy-request does not exist error.

Thank you @jgreet.


[DESIGN] as_nested_tensor doesnt behave same as as_tensor

as_nested_tensor constructor doesn't behave exact the same way as as_tensor constructor. While at_tensor won't copy the data if input already is a tensor with the same metadata (device/dtype/etc) and will copy otherwise, as_nested_tensor will never copy and will throw an error in a case when it's impossible to construct a nested tensor from the given input without a copy.
Options:

1. keep everything as it is. we are agreeing that semantics are different
2. keep the behavior the same but rename as_nested_tensor to something else to avoid confusion.
pros and cons should be discussed.

I don't think the framing is quite right.
as_tensor turns something into a tensor if it isn't already.  It's used at user-interface boundaries when you aren't sure if something is a tensor or not.  The copy stuff just falls out from that.

I think we need to change as_nested_tensor to what Greg suggested. If the input is already a Nestedtensor, return it. If it's not, try to create one. But having this "view" concept is troubling, because it also raises questions around things like autograd + unbind. If I unbind a NestedTensor constructed with as_nested_tensor that's tracking autograd I'm expecting to get a view that won't be a leaf, but currently I might get a leaf, since the autograd operations are simply forwarded to its constituents. This isn't an issue when the NestedTensor is contiguous as constructed by nested_tensor, since the unbound Tensors already are slices of the underlying buffer, but it is an issue when constructed with as_nested_tensor, since the unbound Tensor won't be a view (we could try to force them to be a view, but it seems smarter to make that an extension later on in context of maybe a view_as_nested_tensor operation).


fix(redirects): update redirects for sl guide update

Quick fix for missing redirects! Thank you @T-Dunlap and @mirnawong1 for finding and getting the missing pages right on the first try respectively ❤ !

redirects work in previews!


Elasticsearch request failure. task isn't running and hasn't stored its results

When importing on both dev and prod I get ES errors:
EsRequestException: Elasticsearch request failure. 404 Not Found. task [xTwUbd7mSvuFGdFtYPbj8A:7183081] isn't running and hasn't stored its results
logs
life.catalogue.es.EsRequestException: Elasticsearch request failure. 404 Not Found. task [xTwUbd7mSvuFGdFtYPbj8A:7183081] isn't running and hasn't stored its results
	at life.catalogue.es.EsUtil.executeRequest(EsUtil.java:384)
	at life.catalogue.es.EsUtil.deleteByQuery(EsUtil.java:265)
	at life.catalogue.es.EsUtil.deleteDataset(EsUtil.java:169)
	at life.catalogue.es.nu.NameUsageIndexServiceEs.createOrEmptyIndex(NameUsageIndexServiceEs.java:248)
	at life.catalogue.es.nu.NameUsageIndexServiceEs.indexDatasetInternal(NameUsageIndexServiceEs.java:83)
	at life.catalogue.es.nu.NameUsageIndexServiceEs.indexDataset(NameUsageIndexServiceEs.java:73)
	at life.catalogue.importer.ImportJob.importDataset(ImportJob.java:246)
	at life.catalogue.importer.ImportJob.run(ImportJob.java:116)

In the background are full ES reindexing processes running, but the ES server is fine and responds to searches.

@ayco-at-naturalis did you ever see this?

This msut be because deleteByQuery now uses the task API rather than waiting for the result .... but I assume this is solved now

@mdoering I am also seeing similar errors, the task is created, and can be checked using the task API. Then suddenly the API call to check task returns similar exceptions.
The only resource I found to be useful is this post: https://stackoverflow.com/q/60878827/6064933

Thanks @jdhao. Gladly this problem hasn't shown up again since 3 years, but I doubt we actually changed any code.


Improvement optimise histogram keyword

Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 33.46 seconds
load time: 486 seconds
storage size:<PHONE_NUMBER>1 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230202131525_clickbench_pr_89593.html


Fix typing error in AutofillGroup docs

Fixes a small typing error in the AutofillGroup docs
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[ ] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is [test-exempt].
[ ] I followed the [breaking change policy] and added [Data Driven Fixes] where supported.
[x] All existing and new tests are passing.

Thank you for the contribution. Could you fix the issue with the CLA (see previous comment from the bot)? Otherwise we cannot review or merge this, unfortunately.


chore: accept approval from collaborators

Accept approvals from zalando org and collaborators.

👍

@ruiaraujo Does this pass the compliance check?

👍

👍

👍

:+1:


Working azure download flow

Changes necessary to integrate with Azures services and demo pipeline on 2023-12-09

Great job @zsusswein! Some notes from the demo. Some of these may be separate issues that we deal with later:

[ ] Roll back .env and config workarounds in demo instructions (after these are fixed)
[ ] Would be nice to add a mermaid diagram of all the relevant repos, environments, and microservices and how they connect
[ ] Would be nice to document in each step - from where is this step reading inputs and writing outputs (this would help with troubleshooting)

FYI @amondal2 I tagged you in case you want to take a look, but the azure stuff is kind of a mess. I'm planning on circling back to it and tagging you and Nate to look once it's cleaner.

Some notes from the demo. Some of these may be separate issues that we deal with later:

Tracking in #116

Merging off of Nate's review per conversation with Katie earlier today.


add achievement storage

Checklist

[ ] I tested all changes and all related features with different users (student, tutor, instructor, admin) on the test server https://artemistest.ase.in.tum.de.
[ ] Server: I added multiple integration tests (Spring) related to the features
[ ] Server: I added @PreAuthorize and check the course groups for all new REST Calls (security)
[ ] Server: I implemented the changes with a good performance and prevented too many database calls
[ ] Server: I documented the Java code using JavaDoc style.
[ ] Client: I added multiple integration tests (Jest) related to the features
[ ] Client: I added authorities to all new routes and check the course groups for displaying navigation elements (links, buttons)
[ ] Client: I documented the TypeScript code using JSDoc style.
[ ] Client: I added multiple screenshots/screencasts of my UI changes
[ ] Client: I translated all the newly inserted strings into German and English

Motivation and Context

Description

Please create an issue first in which you explain the data model
changes in detail including the rationale and alternatives.

Glad you mentioned that since I forgot to link the issue.

Looks good to me! Was a long ride, but really good work Balazs! 🚀

Thanks a lot. Feels great to hear that 😊

we decided to merge this PR into a separate branch develop-leaderboard that collects all changes to leaderboards until the feature is finally implemented


Immutable variables

A middle term between a normal var, and a const, that once set, would remain forever with the given value. A good syntax could be using a word short as "var", like "let":
let var_name # Starts 'null', can still have something assigned to it.
let var_name = value # A value has been given, now its value cannot be changed anymore.

One of the main uses of immutable variables would be pairing it together with onready, when creating variables to keep stuff like nodes and certain references:
onready let var_name = $Node/SubNode

I am in favor of a let/val keyword. This is a pretty standard language feature. I know gdscript is similar to python, but protecting data is important, especially in use-cases like creating plugins where a developer might want to restrict a user from accessing something that could break functionality.

I'm in favor of val as well.
@YeldhamDev var/val is used in Kotlin, no real issue.

C# has a keyword called readonly to do something similar. Despite the name, it can be written once, but only either inline (like const) or during constructors, so it's not write once from anywhere. Java's final keyword does the same thing.
val seems too close to var, and I don't like let personally. Some ideas:

What if const thing with no value was allowed to be written once? I don't know if GDScript constants are evaluated compile-time like C# constants are (it doesn't say), but this could be an easy way to solve the problem with no additional keywords.

Re-use a keyword from another language, such as final.

Make it a modifier to var, such as writeonce var.

Why don't you like let? By "personally", do you mean that it's a personal dislike and it shouldn't affect whether it's chosen as the keyword?

I'm in favor of let, as it's harder to confuse compared to val (which looks close to var at a quick glance) and a few languages like Nim already use this keyword for immutable variables. However, there's the downside that JavaScript users may be confused by this, since let variables are mutable there.

I also support let it's hard to confuse it with anything else. It would also solve my issue of initiating some variables in parent class and allowing children to edit them This would allow for autocomplete of functions in parent class that use those variables and assign value to them in children only so the actual objects in the game that use them will have them working fine.

Coming to GDScript after doing a coding session in Dart, which has a similar concept of final variables, I really miss them. lets or vals are really useful writing data classes that are often desired immutable. Would like to have immutable vars featured in GDScript as well!

I programmed in Scala for quite some time and there are zero practical issues with var + val. If you try reassigning val compiler (IDE) will quickly tell you so. I find using let for constants unfortunate, because many people coming from JS/TS will find it confusing. Sure, there are languages like Haskell where it's used as an immutable binding, but let's be honest, how many people are coming from these significantly less popular languages?
Honestly, I find const in GDS confusing, because despite being it a dynamically typed language, it behaves like a macro or similar from "lower" statically typed languages. I would be for upgrading const to work same as const in JS - it can be filled at runtime (e.g. onready const a:= $A or const a:= A.new()), but cannot be re-assigned. Please note that its value is not necessarily immutable, only (I don't know how it's called in GDS) the reference/binding/pointer is.

What's the difference between let and const? They seem like they're supposed to accomplish the same thing (preventing modification of a variable's value once it's created), so I don't really understand why there'd be two keywords for them.

@WARIO-MDMA const needs a value immediately when created. The idea is for let to allow giving it a value later, and then lock changes.

@YeldhamDev I see. Thank you for clearing that up.

@YeldhamDev This may not necessarily be the case. We could still require let variables to be initialized on assignment, which should make the GDScript parsing logic significantly simpler.

An immutable variable declared via let would have to be initialized immediately and then would never change. The difference to const is that it can be created anywhere and conditionally with a value at runtime. It's not constant, just immutable.

initialized on assignment

How would that work with the usage example I gave on the first post, about using it with onready?

It wouldn't work. Maybe modifying let with onready should be a special case that allows it to start as null and change, since it's clearly visible from the syntax to the user that it will be modified on ready (also easily enforceable because there's no separate assignment statement to check the correctness of).
I don't think it's too much of a problem UX-wise to allow later definition for other let declarations, since you can look at the declaration and tell that it may change from null because it is declared without a definition. It is however impossible at compile / semantic checking time to determine whether a variable will ever be assigned to multiple times. I think the feature will be much more useful for avoiding bugs if single assignment can be checked statically.
Maybe you could use static checks for lets with definition or with onready, and dynamic checks for let statements in function bodies with no definition, but this would create an inconsistency that might trip up users. It is possible also to try to conservatively detect safe situations with multiple assignment statements (for example, in separate branches of a conditional statement), but depending on how complex this criteria is, it might not be clear to users when it is allowed.
When GDScript becomes more performant it may also be a performance concern that you have to dynamically perform a null check, but at the moment it is not an issue because of the high overhead interpreting bytecode. Just make sure the dynamic check and the assignment are part of the same bytecode instruction so that you don't double that overhead.

Closing in favor of https://github.com/godotengine/godot/issues/23695, as feature proposals are now tracked in the Godot proposals repository.

Closing in favor of #23695, as feature proposals are now tracked in the Godot proposals repository.

But ... #23695 is this issue? 🤨

@mnn Sorry, I fixed it.


remove taglanguage table and city and website column from profile

https://github.com/rubymonsters/speakerinnen_liste/issues/610

[x] pushed to staging

[ ] test the staging system

[ ] pushed to production

[ ] test production

thank you :)


Speed limit by CPU

What is the issue?

I have a server with 4 RTX 4090 GPUs. When I run a model, all GPUs are utilized between 10-25%, while the CPU is at 100%, but only using one thread. All layers are loaded into the GPUs.
I already tried, the num_thread parameter that does not change anything.
I believe the single thread process in the CPU is limiting the response speed. Is there a way to improve the speed? By changing the configuration?
OS
Linux
GPU
Nvidia
CPU
AMD
Ollama version
0.3.11

https://github.com/ggerganov/llama.cpp/issues/8684


Typo in Sign Up

Instead of "Write down your Recover Phrase" it should be "Write down your Recovery Phrase"

Very good working

very smooth transaction no bug. I joined its testnet beta 2, it is a very secure wallet. And its transection is completed very fast, I'm really lucky to be able to use the fuel wallet fuel199hg3h79xlg8txdcupz4j5qn5gjnrxu0at8p8uup39eakzzk88xs4x2445


Mageck failing on big data sets

Description of the bug
When running the pipeline with 96 input files, the Mageck tool runs into the maximum allowed time (8.h in this case). Possibly, this might be less the case if there is less to calculate for Mageck, e.g. by taking out the "time" column out of the design matrix which is automatically generated for Mageck, or even also the "common", although this probably gives valuable information.
Alternatively, I would suggest to add a parameter to turn off Mageck calculations during pipeline execution, since this tool is not too crucial anyways?
Command used and terminal output
Error executing process > 'NFCORE_CRISPRISCREEN:CRISPRISCREEN:MAGECK_MLE (all_counts)'

Caused by:

  Process exceeded running time limit (8h)

Command executed:

  mageck \

      mle \

       \

      --threads 6 \

      -k all_counts.tsv \

      -d design.tsv \

      -n all_counts

  cat <<-END_VERSIONS > versions.yml

  "NFCORE_CRISPRISCREEN:CRISPRISCREEN:MAGECK_MLE":

      mageck: $(mageck -v)

  END_VERSIONS

Relevant files
No response
System information
No response

Quite interesting! I never tested Mageck with that many input files. But I noticed too that fitness calculation takes much longer than with DESeq. I wonder if others noticed too that it takes that long. And with a lot of resources too; I usually run it with as many cores as possible, still takes much longer than DESeq with 1 core.
Might be something for the original developers of the Mageck module @LaurenceKuhl over at nf-core modules.

Hi @ute-hoffmann ,
i had a similar issue, I think i had 70 comparisons to do and it also ran out, I did a bit of nextflow magic (aka played with the channels) to get all of these comparisons to run parallelised, let me know if you're interested we could have a look, since everything is still under construction.
Thanks for tagging me Michael :)
Best,
Laurence

Hi Laurence,
Thanks for picking this conversation up :-) I wasn't sure if this works, but one can always try.
I would be very interested to learn how you achieved a better performance within an NF pipeline. From what I can see the Mageck module uses all assigned CPUs but maybe not efficiently..?

Hi @LaurenceKuhl ,
for now we are fine with running the whole pipeline with DESeq2 instead of the Mageck analysis, but I think in future it could be nice to adjust this accordingly - so as @m-jahn I would actually be curious to learn about more efficient ways of including Mageck into the pipeline :)
Cheers,
Ute


A WebWorker declared in a dependency is not correctly bundled

Command
build
Description
If a library that uses a Web Worker is used, the angular bundle generation is not including the worker file.
I made a mimimal reproduction case here: https://github.com/andsouto/angular-webworker-example
That project just imports in main.component.ts the next function from a dependency:
export function launchWorker() {
    console.warn('Example of creating a webworker in a dependency');
    const worker = new Worker(new URL('./x.worker', import.meta.url), {type: 'module'});
    worker.postMessage('foo');
}

If that code is included in the app itself it works as expected but when it is declared in a dependency it fails.
Afaik, in the dev server is not working because vite does not support this yet. More info including workarounds in this issue: https://github.com/vitejs/vite/issues/11672
But my main concern here is the production build because I suspect that is a problem in the angular build system itself and I wasn't able to find any workaround for this.
Describe the solution you'd like
Correctly bundle Web Workers declared in a dependency.
Describe alternatives you've considered
No response

Thanks for reporting this issue. Luckily, it has already been fixed in one of the recent releases. Please update to the most recent version to resolve the problem.
If the problem persists in your application after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior. You can use ng new repro-app to create a new project where you reproduce the problem.


ci(docker): speedup build by proxying yarn registry

Codecov Report

Merging #9 (9b3a4ec) into master (58bfc74) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master      #9   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files          18      18
  Lines         257     257
  Branches       15      15
======================================
  Misses        255     255
  Partials        2       2

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 40d93b3...9b3a4ec. Read the comment docs.

Result is so far approx show ~25% (approx 3m) speed up (decrese from 12m to 9m ) on whole build. ✅

The Verdaccio caching seems to be broken due to some permission issues so further small improvement could gained.


Crash in SortConstructorFirst

Thread 0 main thread
CastError: Null check operator used on a null value
at SortConstructorFirst.compute.<fn>(sort_constructor_first.dart:35)
at ChangeBuilderImpl.addDartFileEdit(change_builder_core.dart:144)
at SortConstructorFirst.compute(sort_constructor_first.dart:33)
at FixInFileProcessor._fixError(fix_internal.dart:308)
at FixInFileProcessor.compute(fix_internal.dart:274)
at <asynchronous gap>(async)
at DartFixContributor.computeFixes(fix_internal.dart:221)
at <asynchronous gap>(async)
at EditGetFixesHandler._computeDartFixes(edit_get_fixes.dart:170)
at <asynchronous gap>(async)
at EditGetFixesHandler.handle(edit_get_fixes.dart:78)

Failing tests https://dart-review.googlesource.com/c/sdk/+/243841

@scheglov did you find this from a user report or just yourself somehow? Without a user bug I think this can be P3.

I saw it in google3 crash logs, and constructed a short example to reproduce it.

I see. Let's call it P2. :)


Update content based on CATS feedback.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

azure-go-sdk-conceptual/azure-sdk-go-auth-aad-samples.md
:white_check_mark:Succeeded
View

azure-go-sdk-conceptual/azure-sdk-go-authorization.md
:white_check_mark:Succeeded
View

azure-go-sdk-conceptual/azure-sdk-go-compute-networking-samples.md
:white_check_mark:Succeeded
View

azure-go-sdk-conceptual/azure-sdk-go-containers-samples.md
:white_check_mark:Succeeded
View

azure-go-sdk-conceptual/azure-sdk-go-install.md
:white_check_mark:Succeeded
View

azure-go-sdk-conceptual/azure-sdk-go-qs-vm.md
:white_check_mark:Succeeded
View

azure-go-sdk-conceptual/azure-sdk-go-sql-database-samples.md
:white_check_mark:Succeeded
View

azure-go-sdk-conceptual/azure-sdk-go-tools.md
:white_check_mark:Succeeded
View

azure-go-sdk-conceptual/includes/azure-sdk-go-get.md
:white_check_mark:Succeeded
View

azure-go-sdk-conceptual/includes/cloud-shell-try-it.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard

azure-go-sdk-conceptual/includes/azure-sdk-go-get.md
96
1
link

azure-go-sdk-conceptual/includes/cloud-shell-try-it.md
100
0
link

More info about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard

azure-go-sdk-conceptual/includes/azure-sdk-go-get.md
96
1
link

azure-go-sdk-conceptual/includes/cloud-shell-try-it.md
100
0
link

More info about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

azure-go-sdk-conceptual/azure-sdk-go-auth-aad-samples.md
:white_check_mark:Succeeded
View

azure-go-sdk-conceptual/azure-sdk-go-authorization.md
:white_check_mark:Succeeded
View

azure-go-sdk-conceptual/azure-sdk-go-compute-networking-samples.md
:white_check_mark:Succeeded
View

azure-go-sdk-conceptual/azure-sdk-go-containers-samples.md
:white_check_mark:Succeeded
View

azure-go-sdk-conceptual/azure-sdk-go-install.md
:white_check_mark:Succeeded
View

azure-go-sdk-conceptual/azure-sdk-go-qs-vm.md
:white_check_mark:Succeeded
View

azure-go-sdk-conceptual/azure-sdk-go-sql-database-samples.md
:white_check_mark:Succeeded
View

azure-go-sdk-conceptual/azure-sdk-go-tools.md
:white_check_mark:Succeeded
View

azure-go-sdk-conceptual/includes/azure-sdk-go-get.md
:white_check_mark:Succeeded
View

azure-go-sdk-conceptual/includes/cloud-shell-try-it.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Layers not cloned when added to multiple map views

When using a custom view that creates multiple map views, there is some odd behaviour with layers added to map views.
Workflow

Get the locale
Set layers to locale.layers
Create a map view
Add layers to it
Create second map view
Add same layers to this
Change a theme on the second map view on a layer, the behaviour does not work, it may change the theme or perhaps the theme is reversed multiple times incorrectly too as the layer is decorated over and over.

Will provide a replicable example next week

I am looking into this!


Offset fetch only provided one partition due to current partition id

As title, Should return all partition meanwhile

Bring with tag <IP_ADDRESS>


Only run linters on the changed code, except for main build

Linters take a lot of time to run.

Locally only run linters on the code that has changed in the current branch from the master branch point.
For pull requests only run on the new Code.
For main build, run linter on everything.

This change is

Current coverage is 74.02% (diff: 100%)

Merging #207 into master will not change coverage

@@             master       #207   diff @@
==========================================
  Files            39         39
  Lines          1532       1532
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1134       1134
  Misses          369        369
  Partials         29         29

Powered by Codecov. Last update f5fd329...3e002fd


Add field .spec.virtualCluster.etcd.main.backup.managed for Garden resource

How to categorize this PR?

/area control-plane
/kind enhancement
What this PR does / why we need it:
The newly introduced generation of the BackupBucket resource for the virtual garden by the gardener-operator is now controlled by the new boolean field .spec.virtualCluster.etcd.main.backup.managed for the Garden resource kind.
This is needed at least temporarily until the provider extensions are ready to be deployed on the runtime cluster.
The section .spec.virtualCluster.etcd.main.backup is typically already specified for configuring ETCD druid.
With the current logic, the garden reconciliation waits endless for the reconciliation of the BackupBucket in this case.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

Add field `.spec.virtualCluster.etcd.main.backup.managed` for Garden resource to enable gardener managed `BackupBucket` by provider extension on runtime cluster optionally.

/cc @oliver-goetz @shafeeqes

/test pull-gardener-e2e-kind-operator-seed

As the PR description explains the introduced field is more of temporary nature, it's preferable to not add an API change at all. Instead, the operator could check if there is a Extension available that registeres a BackupBucket resource and if it doesn't we just skip the flow step. WDYT?

OK, will make a new PR following that way.

/close in favour of #10837


try and add max surge for upgrade

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

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

/azp run automation - sdk

Can one of the admins verify this patch?

@paulgmiller Please fix the spellcheck failure

Moved to 04-01 branch

https://github.com/Azure/azure-rest-api-specs/pull/9331


execStart should use the 'noTimeoutClient'.

Like attachContainer, the execution created by execStart could take an
arbitrary amount of time, and if the inactivity execeeds the socket read
timeout (default 30s), data could be overlooked, or the stream could be
closed.
For example, if one has a running container, and creates a separate execution instance (running /bin/sh) using execCreate/execStart, after 30s of inactivity on the returned stream, it will time out and be unusable.
The test in this commit reproduces this by setting the timeout to 5s and creating a separate execution that sleeps for 10s and then prints "Finished". When execStart uses the regular resource() call, this fails due to a timeout after 5s, but with noTimeoutResource() this succeeds.

Codecov Report

Merging #916 into master will not change coverage.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master     #916   +/-   ##
=========================================
  Coverage     66.04%   66.04%
  Complexity      769      769
=========================================
  Files           171      171
  Lines          3240     3240
  Branches        369      369
=========================================
  Hits           2140     2140
  Misses          940      940
  Partials        160      160

We've seen problems potentially related to this when using exec based commands: if the command tries to examine its environment with isatty(3), the request may block indefinitely.
@rgrunber Is it possible that the timeout and subsequent request closure used by the previous client allowed the exec command's output and exit code to be captured? I'll have to do some pseudo-tty spelunking.


Use six-part cron syntax for gen1 scheduled tasks

I suspect this is why our gen1 cron jobs aren't starting, although I haven't verified it.
Release Playbook

[ ] Rebase against master
[ ] Code review
[ ] Merge into master
[ ] Verify changes at http://site-staging.convox.com
[ ] Promote release on site-production in the convox/production Rack

I don't think this is why your cron jobs are not starting. The manifest already adds a * as a 6th element.
https://github.com/convox/rack/blob/master/provider/aws/helpers.go#L1240

Got it! Yes, you're right, that was not why our cron jobs were not starting.
I was confused because the example for gen1 apps uses a six-part cron syntax:
web:
  labels:
    - convox.cron.myjob=0 * * * ? * bin/myjob


[SPARK-40569] Expose SPARK_MASTER_PORT 7077 for spark standalone cluster

What changes were proposed in this pull request?

This PR aims to expose SPARK_MASTER_PORT in Dockerfile, default value of which is 7077.

The EXPOSE instruction informs Docker that the container listens on the specified network ports at runtime.
https://docs.docker.com/engine/reference/builder/#expose

Why are the changes needed?

In standalone mode, spark workers need to connect to spark master through SPARK_MASTER_PORT.  It's better to expose default port in DOI.
Does this PR introduce any user-facing change?

Yes, expose a new port in Dockerfile.
How was this patch tested?

Add smoke test in GA.

Thanks!
Try change on template and apply changes. :)

Change the Dockerfile.template.
Run ./add-dockerfiles.sh 3.3.0.

Could you fullfill the PR description with test results about EXPOSE port?

Thanks for your comment @Yikun
It's still draft and let me update it. BTW, we need CONTRIBUTING.md to help contributor to improve the project by updating the Dockerfile.template. If you agree that, I will submit a new PR to make it.

cc @HyukjinKwon @Yikun
It would be good if you have time to review this

@dcoliversun Thanks, CI is green. I will take a look soon.
A quick question, how many ports should be exposed in future? For common ports, we could write them directly in the dockerfile, and for the less commonly used ones, we can expose them to users through docker -p port:port and doc them, WDYT?

@Yikun Agreed.

A quick question, how many ports should be exposed in future?

I believe we should only expose 7077 because it is used to connection between master and work and other ports which should be published are used to access the application from the host.

For common ports, we could write them directly in the dockerfile, and for the less commonly used ones, we can expose them to users through docker -p port:port and doc them, WDYT?

Yes, I have SPARK-40570 to do it. 8080(master ui port)/8081(worker ui port)/4040(live app ui port)/6066(external service) should be published and I will write in doc with command docker run --publish <host_port>:<container_port>.

cc @HyukjinKwon @zhengruifeng Mind taking a look, thanks!

I guess it's ready?
Probably the only potential problem is that the 7077 feels a bit hardcode. If other people think there is a problem, we can temporarily not add 7077. Only add standalone tests wit specified -p 7077.
For standalone tests, I think it is very useful. BTW seems it references some from link and reimplemetened for Spark, according my test also works well.
So, if you think EXPOSE port it's a problem, we can specified -p first, otherwise all is looks good for me.

also cc @holdenk @dongjoon-hyun

I have discussed with @Yikun offline, because the ports required by master and worker are different, we will not unify exposure in Dockerfile. Now publish the port in the docker run command instead. I will submit a new PR to do the job, the new PR does not modify the Dockerfile, only adds smoke tests in standalone cluster for local and GA.


Add key terms checks

ACAI Dataset: https://drive.google.com/file/d/1GDf_aRONcBGeJrj5h80FhOnXY9ON2oMt/view?usp=sharing
unfoldingWord TranslationWords: https://preview.door43.org/u/unfoldingWord/en_tw/master#other--other ; https://git.door43.org/unfoldingWord/en_tw

[ ] Collect names with verse references (should include anaphoric refs, distinguish between entities (e.g. Mary Magdalene vs Jesus' mother), synonymous names (sea of Galilee vs Kinnereth, etc.), entity type (person, place, etc.))
[ ] Look at Strongs dataset
[ ] Collect key terms with Biblical references


docs(masthead): add missing sandbox dependency

Related Ticket(s)
#7847
Description
This PR adds a missing dependency to the masthead sandbox example so that it displays without any build errors
The working sandbox should be viewable at https://codesandbox.io/s/github/emyarod/carbon-for-ibm-dotcom/tree/7847-docs/masthead-sandbox-example/packages/web-components/examples/codesandbox/components/masthead

@emyarod we should actually look into this because ideally our adopters shouldn't need to do this.


Update supported-platforms.md

Fixes #26140
Internal review URL

The linked doc - https://github.com/Azure/app-service-linux-docs/blob/master/HowTo/gRPC/use_gRPC_with_dotnet.md - looks like it's intended to be published. It has [!WARNING] syntax in it.
Do you know where the published doc lives? It would be nicer to link to it.

The linked doc - https://github.com/Azure/app-service-linux-docs/blob/master/HowTo/gRPC/use_gRPC_with_dotnet.md - looks like it's intended to be published. It has [!WARNING] syntax in it.
Do you know where the published doc lives? It would be nicer to link to it.

My guess is this is not built and published to https://docs.microsoft.com/azure/app-service/ but is just a ReadMe file in MD format. https://github.com/Azure/app-service-linux-docs has no information either way.
cc @btardif @AngelosP who can answer this question.

@btardif @AngelosP can you verify if  https://docs.microsoft.com/azure/app-service/ but is just a ReadMe file and not published as a doc?

@jeffwmartinez we should make sure we update this doc once GRPC is fully rolled out on App Service.

@Rick-Anderson you guys have the right link --> https://github.com/Azure/app-service-linux-docs/blob/master/HowTo/gRPC/use_gRPC_with_dotnet.md there is no official gRPC doc but we are working on it.


adding emojis broke wasm build

with f3adda15f31f18c1442c24657634440a8e9225f3 and adding twemoji-rs unconditionally as a dependency wordcloud-rs does not longer run in wasm environments anymore. unfortunately it will only break at runtime with:
panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Unsupported, message: "operation not supported on this platform" }', /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/twemoji-rs-0.1.2/src/lib.rs:10:37

could you make emoji support conditional so it could be disabled via features?

I'm quite busy with work and other projects so idk when i'll fix this but thanks for pointing it out !


Search filters

An idea to be able to further filter your games list, useful for those with hundreds of entries:

The current Search button could reveal a Unique|Duplicates drop-down box (DDB) to filter only games marked as having duplicates or not. The DDB would then have a checkbox beside it to toggle the DDB's active state (disable its UI and its filtering).
Similarly, a Complete|Partial DDB for games with only some their items checked (i.e. when you see "5 of 26" next to a game title), or those that have all of their items checked.
Similarly, a Selected|Unselected DDB for games which are currently unselected and won't be backed up, or those that will be.

My thinking is that these options would be additional filters on top of any supplied search term and able to be combined for specific types of results, for example: "Call of Duty" + [x] Duplicates + [x] Partial + [x] Selected. This example is an extreme case which actually would be more likely to be used without the search term, i.e.: find any games which have duplicates, which have only some of their items selected, and which the games themselves are selected to be backed up.
With such a design, an All button would be nice to have to bypass all the DDB filters (to avoid the need to uncheck the checkboxes of each filter) to only see what the search term by itself returns, i.e. turn the feature off altogether.
How regularly would one need these filters, I'm not sure, but I could see them being useful to help find those two games out of your 200 that are unchecked for example. Over-engineered or practical? Thanks!

Here's a preview from the upcoming release:

https://user-images.githubusercontent.com/4934192/229463214-9a93086d-112b-4eb2-bae0-0a7c5869a4e8.mp4

Looks great! Thanks @mtkennerly.


Support installing natively via Bazel

This was partially resolved by #190. We still need to add support for installing with SnapshotTesting as the snapshot engine.


v2.0.0 How to extend role declared in JSON?

I can't seem to extend a role when declared in json.  The following works but when I take the tostring and then use as access control.setGrants(thejson) it complains about $extend being a reserved word.  I see that is a new addition in the changelog.  How do I achieve the same result using setGrants()?
const accessControl = new AccessControl();
accessControl.grant('viewer').readAny('users');
accessControl.grant('admin').extend('viewer').createAny('users').deleteAny('users').updateAny('users');
let assert = require('assert');
assert('admin can read any user=' + accessControl.can('admin').readAny('users').granted);
console.log(`accessControl.getGrants()=${JSON.stringify(accessControl.getGrants())}`);

$> accessControl.getGrants()={"viewer":{"users":{"read:any":["*"]}},"admin":{"$extend":["viewer"],"users":{"create:any":["*"],"delete:any":["*"],"update:any":["*"]}}}

This looks like a bug. Will confirm and fix shortly.

Fixed in v2.2.0.


Display config file path when something goes wrong while parsing it

Currently:
Fatal error has occurred
Error occured at: src/parser.c - parse_log - 1650
No time format was found on your conf file.

This has been implemented. It should help for debugging purposes.
GoAccess - version 0.9.1 - Jun 10 2015 21:04:32
Config file: config/goaccess.conf

Fatal error has occurred
Error occured at: src/parser.c - verify_formats - 1657
No date format was found on your conf file.


Update dependencies to use Grafana 8.5.4

In order to fix #28 the dependencies - especially those belonging to @grafana - needed to be updated.
I also updated further core dependencies such as react or jest.
After updating I had some problems with running tests, which were fixed by the changes in jest.config.js.

The CI shows that the dependency react-dev-utils needs Node v14, but it seems like plugins need Node v12.
How do we handle those cases?
Reasoning for upgrading react-dev-utils were some vulnerabilities inside that dependency [Source PR].

Hmm maybe we can leave updating react-dev-utils for another PR - to keep this one more focused.
I also see that both "react-dev-utils": "^12.0.0" & "@types/react-dev-utils": "9.0.10" are dependencies in grafana

May need to revert updating some other libraries too as build_frontend is failing.

This is fantastic, great job on getting the build fixed. Will take another look at this after lunch :)

Hi @joey-grafana
I now also updated @grafana/toolkit to version 8.5.4. This will come with a few benefits:

all @grafana dependencies are running on the same version
plugin is working with those updates (important benefit, right? 😅)

However, since this plugin should also work with Node 12 I needed to pin the following dependencies to a version which is fine for Node 12:

"react-dev-utils": "10.2.1",
"@typescript-eslint/eslint-plugin": "4.0.1",
"@typescript-eslint/parser": "4.0.1"

What do you think about this?

Hi @joey-grafana
I now also updated @grafana/toolkit to version 8.5.4. This will come with a few benefits:

all @grafana dependencies are running on the same version
plugin is working with those updates (important benefit, right? 😅)

However, since this plugin should also work with Node 12 I needed to pin the following dependencies to a version which is fine for Node 12:

"react-dev-utils": "10.2.1",
"@typescript-eslint/eslint-plugin": "4.0.1",
"@typescript-eslint/parser": "4.0.1"

What do you think about this?

That's good! Please double check that there are no console errors after running yarn install, then yarn watch :) You can also check out elasticsearch to see how it deals with the newer versions where the package api has changed and requires updates in opensearch.

Hi @joey-grafana
I now also updated @grafana/toolkit to version 8.5.4. This will come with a few benefits:

all @grafana dependencies are running on the same version
plugin is working with those updates (important benefit, right? 😅)

However, since this plugin should also work with Node 12 I needed to pin the following dependencies to a version which is fine for Node 12:

"react-dev-utils": "10.2.1",
"@typescript-eslint/eslint-plugin": "4.0.1",
"@typescript-eslint/parser": "4.0.1"

What do you think about this?

That's good! Please double check that there are no console errors after running yarn install, then yarn watch :) You can also check out elasticsearch to see how it deals with the newer versions where the package api has changed and requires updates in opensearch.

I like the idea of just updating @grafana/data much better. Did that now, which seems to work after arranging some types.


History.action is always 'POP' even when loading the page the first time.

We've noticed in the following code that history.action is ALWAYS === to 'POP' even when page is first loaded.
import { useHistory, useParams } from "react-router-dom";
import React, { useState, useEffect, useRef } from "react";
import { Link } from "react-router-dom";

export default function Test(props) {
	const [refresh, setRefresh] = useState(false);
	const history = useHistory();

	useEffect(() => {
		if (history.action === "POP")
			console.log("Back button used: "+history.action);
		else console.log("useEffect called in home");
	}, []);

	return (
		<>
			Hello from Test
			<Link to="/test2">Test me</Link>
		</>
	);
}

See the following Sandbox demonstrating the same problem:
[https://codesandbox.io/s/sad-framework-e8h7z]

https://github.com/ReactTraining/history/issues/96#issuecomment-147446262

https://github.com/ReactTraining/history/issues/96#issuecomment-147446262


Small addition to kernel file and addition of unsupervised introduction

Added a little information about SVMs in the kernel discussion. Also added a first draft of the introduction to unsupervised learning as discussed with @attp and @frankharkins. The images in the unsupervised learning section don't yet exist, will discuss with design team to see what they should be.

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

I'm merging so I can start working, @attp can you still review please and Owen & I will incorporate any feedback after


Apply gravity alignment to odometry data passed to SPG

Fixes #515.
I am not sure if this also belongs in 3D (I just mirrored the change that I did in 2D).

Thanks for the PR, this definitely goes into the right direction. As far as the concrete implementation goes, I think there is a different approach more in line with the rest of the codebase. I'll prepare a PR together with @cschuet soon.

3D does not have any issue and should not be changed. In the 3D pose graph all poses are in tracking frame.
The approach you take to change the odometry data is brittle. Since we do not want to make guarantees about the yaw, interpolating (which we later do in the pose graph optimization) this changed odometry data might introduce errors.
A better approach would be to take the gravity alignment of the poses in the 2D pose graph optimization into account when computing the predicted relative change from one pose to the next. We'll look into implementing this now.


Capture EPA standard Latitude/Longitude metadata

Should the EPA lat/lon standard be followed https://www.epa.gov/sites/production/files/2014-08/documents/latitude_longitude_standard_08_11_2006_final_0.pdf?

Duplicated by https://github.com/ACWI-SSWD/nldi-services/issues/63


missing dependency for running gdb on Arch linux

Hi ,
I try to run gdb on my arch linux and gdb need some dependency that are not found on arch linux. I followed the readme to install the linux setup + eclipse front end. Up to now I can compile and flash my bord from linux.
I try to get ARM-USB-OCD working on my ESP32 thing board (from sparkfun). I have wired it already and openOCD seem to be happy with it.
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : esp32.cpu0: Core was reset (pwrstat=0x1F, after clear 0x0F).
Info : esp32.cpu0: Target halted, pc=0x40080AC8
esp32.cpu0: target state: halted
When I try to start gdb, I got those error messages.
could not found shared library libncurses.so.5 and libtinfo.so.5
ldd xtensa-esp32-elf/bin/xtensa-e
linux-gate.so.1 (0xb77cf000)
libdl.so.2 => /usr/lib/libdl.so.2 (0xb77a2000)
libncurses.so.5 => not found
libtinfo.so.5 => not found
libm.so.6 => /usr/lib/libm.so.6 (0xb774c000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0xb772f000)
libpython2.7.so.1.0 => /usr/lib/libpython2.7.so.1.0 (0xb754d000)
libc.so.6 => /usr/lib/libc.so.6 (0xb7394000)
/lib/ld-linux.so.2 (0xb77d1000)
libutil.so.1 => /usr/lib/libutil.so.1 (0xb7390000)
On Arch I have
/usr/lib/libncurses++.so
/usr/lib/libncurses++w.so
/usr/lib/libncurses++w.so.6
/usr/lib/libncurses++w.so.6.0
/usr/lib/libncurses.so
/usr/lib/libncursesw.so
/usr/lib/libncursesw.so.6
/usr/lib/libncursesw.so.6.0
But I don't have any libtinfo.so
What should I do now ?
any idea ?

For ncurses5 (including libtinfo) on Arch, there is a package from AUR that is needed:
https://aur.archlinux.org/packages/ncurses5-compat-libs/
Or possibly, as you are using the 32-bit toolchain:
https://aur.archlinux.org/packages/lib32-ncurses5-compat-libs/
I will update the prerequisites guide to mention this.

Hi,
I will have a look at it.
Regards
Jonathan

lib32-ncurses5-compat-libs 6.0-4  (2016-07-07 23:34)
( Unsupported package: Potentially dangerous ! )
==> lib32-ncurses5-compat-libs dependencies:

lib32-glibc (building from AUR)
lib32-ncurses (building from AUR)
gcc-multilib (building from AUR) [makedepend]

==> Continue building lib32-ncurses5-compat-libs ? [Y/n]
==> ----------------------------------------------------
==>
==> Building and installing package
==> Install or build missing dependencies for lib32-ncurses5-compat-libs:
error: target not found: gcc-multilib
error: target not found: lib32-ncurses
error: target not found: lib32-glibc
==> Restart building lib32-ncurses5-compat-libs ? [y/N]
==> ---------------------------------------------------
==>
regards
Jonathan

Hi,
Building it from your crossNG fork seem to work. No problem starting gdb.
Regards
Jonathan


Add Outline and SelectiveBloom

These are currently in but not working. I already started the work, posting this as a reminder

Outline kind of works but props don't seem to do anything. Tried changing strength, color, etc and they have no effect.

Closed by #24 #35


Create codeql-analysis.yml

Closes #1799
Summary

Setup CodeQL workflow to automatically detect common vulnerability and coding errors.

Acceptance Test (how to verify the PR)

CodeQL scan should pass

:tada: This PR is included in version 2.141.0-next.33 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.141.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


"root" path duplicated for new modules when changing "root" path of .angular-cli.json ng generate  to more then one subdirectory level

Versions
Windows 10, Node 8.9.2, npm 5.5.1, ng-cli 1.6.0:
[duricz@msgn07241 ~/temp/my-new-app]$ uname -a
MINGW64_NT-10.0 msgn07241 2.9.0(0.318/5/3) 2017-10-05 15:05 x86_64 Msys
[duricz@msgn07241 ~/temp/my-new-app]$ node -v
v8.9.2
[duricz@msgn07241 ~/temp/my-new-app]$ npm -v
5.5.1
[duricz@msgn07241 ~/temp/my-new-app]$ ng -v
_                      _                 ____ _     ___
/ \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
/ △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
/ ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
/_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
|___/

Angular CLI: 1.6.0
Node: 8.9.2
OS: win32 x64
Angular: 5.1.1
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 1.6.0
@angular-devkit/build-optimizer: 0.0.36
@angular-devkit/core: 0.0.22
@angular-devkit/schematics: 0.0.42
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.0
@schematics/angular: 0.1.11
@schematics/schematics: 0.0.11
typescript: 2.4.2
webpack: 3.10.0

Repro steps
If I change the app.root property to more than one level bellow "src" in .angular-cli.json, ng generate duplicates the source path when generating new components.
I mean, if "root" is "src", all is well. If root is "src/subdirectory", still all cool. If root is "src/sub/secondsubdirectory", the path of generated modules is duplicated.
Steps to reproduce:

create a new app (ng new my-new-app)
generate a new module to make sure module is done properly
change the "root" property of .angular-cli.json to "src/main/frontend"
generate a new module.

The path that is generated is duplicating the "root" part of the path.
Observed behavior
duricz@msgn07241 ~/temp/my-new-app]$ grep root .angular-cli.json
      "root": "src",
[duricz@msgn07241 ~/temp/my-new-app]$ ng g m module
  create src/app/module/module.module.ts (190 bytes)
[duricz@msgn07241 ~/temp/my-new-app]$ vi .angular-cli.json
[duricz@msgn07241 ~/temp/my-new-app]$ grep root .angular-cli.json
      "root": "src/main/frontend",
[duricz@msgn07241 ~/temp/my-new-app]$ ng g m another
  create src/main/frontend/src/main/frontend/app/another/another.module.ts (191 bytes)
[duricz@msgn07241 ~/temp/my-new-app]$ ng g m another --flat
  create src/main/frontend/src/main/frontend/app/another.module.ts (191 bytes)
[duricz@msgn07241 ~/temp/my-new-app]$
[duricz@msgn07241 ~/temp/my-new-app]$ ng g m nested/module
  create src/main/frontend/src/main/frontend/app/nested/module/module.module.ts (190 bytes)
[duricz@msgn07241 ~/temp/my-new-app]$

Desired behavior
I expect that my new module would be generated directly under src/main/frontend/app. Instead, my new module is made in src/main/frontend/src/main/frontend/app.
Mention any other details that might be useful (optional)
This was mentioned in https://github.com/angular/angular-cli/issues/58, but closed.
The same happens if I try to generate service, component etc. The problem only appears for more than two levels of directory:
[duricz@msgn07241 ~/temp/my-new-app]$ vi .angular-cli.json
[duricz@msgn07241 ~/temp/my-new-app]$ ng g module mymo
  create srcss/app/mymo/mymo.module.ts (188 bytes)
[duricz@msgn07241 ~/temp/my-new-app]$ vi .angular-cli.json
[duricz@msgn07241 ~/temp/my-new-app]$ ng g module mymo
  create src/single/app/mymo/mymo.module.ts (188 bytes)
[duricz@msgn07241 ~/temp/my-new-app]$ vi .angular-cli.json
[duricz@msgn07241 ~/temp/my-new-app]$ ng g module mymo
  create src/single/twolevels/src/single/twolevels/app/mymo/mymo.module.ts (188 bytes)
[duricz@msgn07241 ~/temp/my-new-app]$ vi .angular-cli.json
[duricz@msgn07241 ~/temp/my-new-app]$ ng g module mymo
  create src/single/twolevels/three/src/single/twolevels/three/app/mymo/mymo.module.ts (188 bytes)
[duricz@msgn07241 ~/temp/my-new-app]$

Any news on this, it's kind of annoying to move all the generated code manually every time..

Oh, I forgot to update this ticket. This started working for me, sometimes between 1.6.0 and 1.6.4, not sure which version fixed it. I will leave it open if you guys wanna make sure it works. @ntrp, did you try with the latest versions of ng-cli?

I used 1.6.7 and it was happening.. for now I moved my sources close to the root to avoid the problem and to refactor the project.

Closing this as it should be addressed by the better workspace file in 6.0.


Test adjacency matrix against different values of 'out_size'

Codecov Report

Merging #175 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #175      +/-   ##
==========================================
+ Coverage   79.09%   79.15%   +0.05%
==========================================
  Files          81       81
  Lines        3521     3530       +9
==========================================
+ Hits         2785     2794       +9
  Misses        736      736


Test new Netlify image

Summary

Context

It looks like the Netlify preview is working. I don't see any reason to merge this PR, as it doesn't contain any changes. Is that correct @dpulitano? Should we just close it?


Reverted blosc version change for VFX2021

The change was commited by mistake in the last PR...

No worries Nick, are you able to approve it so I can merge?

Looks like the approval can only come from a select few... @jfpanisset to the rescue?


Dark mode is not working - Debian 10 - KDE

install
scan the qr code
settings --> enable dark mode

expected: dark mode

obtained only the scroll line is darkened

WhatsDesktop 1.8.0
linux x64 4.19.0-6-amd64 <-- Debian 10

At the chats:


Deprecate the log directory setting

@FeliciaAnnKelleyTaylorGV Thanks for the PR can you follow the instructions in this message: https://github.com/microsoft/vscode-python/pull/23297#issuecomment-2186952207
Would it be also possible to open a issue and provide description on this change.

Closing this since we have not heard back in a while. I can reopen this or you can create a new PR, and we will be happy to reaview.


fire certain tooltip with other element

Hi, I have about 30 tooltips. Each of them is fired by one element.
Example:

Click to fire tooltip!

This is the content of my tooltip!
Is it possible to fire this tooltip with a different element? But on position related to first div.

You can also click here to fire tooltip!

This should be a question on StackOverflow since it is not an issue, is just a way to work with the plugin.
Anyway, you can get the tooltipstered element and use .tooltipster('show') or .tooltipster('open') (last version has both).
Here's an example:
https://jsfiddle.net/macmessa/guqb0x4v/

You're right. Thanks a lot!


About the model structure

Incredible work! However, the code of the model structure is quite hard to read for me. Is there any chance to post a model structure figure or anything that helps us understand the model structure? Really appreciate it!

Thanks for your interest in our work. I will definately try make a rough diagram for a better understanding of the codebase. Stay tuned.


[DUBBO-3137]: step4 - remove  ConfigConstants

What is the purpose of the change
issue #3137: step4 - remove ConfigConstants
Brief changelog
XXXXX
Verifying this change
XXXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

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

@@             Coverage Diff              @@
##             master    #4079      +/-   ##
============================================
+ Coverage     62.91%   62.98%   +0.06%
- Complexity      542      544       +2
============================================
  Files           756      756
  Lines         32541    32581      +40
  Branches       5137     5164      +27
============================================
+ Hits          20474    20520      +46
+ Misses         9703     9701       -2
+ Partials       2364     2360       -4

Impacted Files
Coverage Δ
Complexity Δ

...apache/dubbo/rpc/protocol/dubbo/DubboProtocol.java
66.91% <ø> (+0.12%)
0 <0> (ø)
:arrow_down:

...va/org/apache/dubbo/config/ConfigCenterConfig.java
77.61% <ø> (ø)
0 <0> (ø)
:arrow_down:

.../java/org/apache/dubbo/config/ReferenceConfig.java
59.85% <ø> (ø)
0 <0> (ø)
:arrow_down:

...ava/org/apache/dubbo/config/ApplicationConfig.java
97.59% <ø> (ø)
0 <0> (ø)
:arrow_down:

...ain/java/org/apache/dubbo/config/ModuleConfig.java
89.47% <ø> (ø)
0 <0> (ø)
:arrow_down:

...n/java/org/apache/dubbo/config/RegistryConfig.java
91.5% <ø> (ø)
0 <0> (ø)
:arrow_down:

...in/java/org/apache/dubbo/config/ServiceConfig.java
58.2% <ø> (ø)
0 <0> (ø)
:arrow_down:

...ain/java/org/apache/dubbo/config/MethodConfig.java
95.12% <ø> (ø)
0 <0> (ø)
:arrow_down:

...n/java/org/apache/dubbo/config/ProtocolConfig.java
92.85% <ø> (ø)
0 <0> (ø)
:arrow_down:

...g/apache/dubbo/config/AbstractInterfaceConfig.java
72% <ø> (ø)
0 <0> (ø)
:arrow_down:

... and 32 more

Continue to review full report at Codecov.

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


[irods/irods#6597] Add Ubuntu 22.04 support

I don't remember if this works all the way, but putting up for interested eyeballs :)

Companion PRs:
https://github.com/irods/irods/pull/6620
https://github.com/irods/irods_client_icommands/pull/323
https://github.com/irods/irods_development_environment/pull/72

Unit tests and core tests passed. Also confirmed that catalog consumer instances are working


[Question]: Inquiry on the Availability of ver GPT-4o API

What is your question?
I am writing to enquire about the roadmap for the GPT API, specifically regarding the release of a GPT-4o version.  the capabilities of the GPT models are critical to the progress and efficiency of my projects.
Please give as many details as possible:
I have been utilizing the current version available, and I'm eager to understand what improvements and new features GPT-4 will bring.
More Details
If there is a timeline or any planned release date for GPT-4o, as well as details on how we can prepare to integrate the new API version, it would be immensely helpful.
The main subject of my question is the release schedule and feature set of the upcoming GPT-4o API.
What is the main subject of your question?
Other
Screenshots
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@danny-avila
https://huggingface.co/spaces/LibreChat/LibreChat use this service, but so far I don't see anything updated in the models here.

@danny-avila https://huggingface.co/spaces/LibreChat/LibreChat use this service, but so far I don't see anything updated in the models here.

you will have to wait until the HF space is updated, then.

@danny-avila https://huggingface.co/spaces/LibreChat/LibreChat use this service, but so far I don't see anything updated in the models here.

I need to manually update the model list on our demo. I'm outside now but will take care of this when I'm back

@rdbox It should be live now!
Also, small tip, use one of these URLs to access it and you will not be logged out every time you refresh the page:
https://demo.librechat.cfd/
https://librechat-librechat.hf.space/


[pred_mod] Update process datasets nf-tower script

Describe your changes
param_list not working due to duplicate ID's found.
Issue ticket number and link
Closes #xxxx (Replace xxxx with the GitHub issue number)
Checklist before requesting a review

[x] I have performed a self-review of my code

Check the correct box. Does this PR contain:

[ ] Breaking changes
[ ] New functionality
[ ] Major changes
[ ] Minor changes
[x] Bug fixes

[ ] Proposed changes are described in the CHANGELOG.md

[ ] CI Tests succeed and look good!

Requirements after merging

[ ] Need to regenerate common/ resources

[ ] Need to regenerate task-specific resources. Specify: <all or ...>

Please make sure to squash and merge


Mixture of two polarized triplets

It's currently not possible to simulate a mixture of two spin-polarized triplets with different polarizations with a single call to pepper, since the polarization is taken from Exp.Temperature, which is used for all spin systems in a mixture. (Workaround: simulate the two spectra separately, and add them)
Maybe introduce a Sys field that holds the polarization?

This works now with Sys.Pop. Example:
clear, clc

Sys1.S = 1;
Sys1.D = 1400;
Sys1.Pop = [1 0 1];
Sys1.weight = 1;

Sys2.S = 1;
Sys2.D = 300;
Sys2.Pop = [0 1 1];
Sys2.weight = 0.1;

Exp.mwFreq = 9.5;
Exp.Harmonic = 0;
Exp.Range = [250 450];

pepper({Sys1,Sys2},Exp);


Implements nss_cache binary for OSLogin.

Introduces a simple nss_cache binary. This binary simply queries the OS Login
database for all uses and writes the passwd entries to a file.
It is intended to be used with the libnss-cache nss module, which depends on a local
file for stored passwd entries.

When trying to build the latest version of this, I got:
nss_cache/nss_cache.cc: In function ‘int main(int, char**)’:
nss_cache/nss_cache.cc:61:42: error: ‘buflen’ was not declared in this scope
BufferManager buffer_manager(buffer, buflen);
^~~~~~
It looks like the 'int buflen = 2048' line was removed.

Thanks for catching that, should be fixed now!

LGTM

I am making some minor changes to this. Don't merge yet.

Ok PTAL. The binary will create a backup in case caching fails, and attempt to restore the cache on failure. There are also some changes to the utils file, since I found a discrepancy between what the library expected for page_token behavior, and what actually happens in production.
The library thought that the last page would contain an empty page token, along with the final array of passwd entries. What actually happens is the last page of actual passwd entries still has a page token, and the next page will contain no passwd entries, but a page token of 0.

LGTM
Seems to work as expected.


Preparation for PyPi integration

Added various metadata to setup.py
Added setup.cfg file required by PyPi
Fixed flaky tests
Fixed linter errors

From now on, any new commit to master needs to increment the value of 'version' in setup.py. That does not necessarily need to correspond to a new publicly released version.
Once we're integrated into PyPi, we'll just need to add a tag to the particular commit to master that we want to release, making sure that the tag exactly matches the value of 'version' in setup.py in that commit.


Proprietary/confidential license in CustomTelemetryChannel.cs

https://github.com/dotnet/dotnet/blob/826dcac6ef3a34e4e41042fb1112995fe1f21609/src/source-build-externals/src/application-insights/LOGGING/test/Shared/CustomTelemetryChannel.cs#L1-L6
has this license
//-----------------------------------------------------------------------------------
// <copyright file='CustomTelemetryChannel.cs' company='Microsoft Corporation'>
//     Copyright (c) Microsoft Corporation. All Rights Reserved.
//     Information Contained Herein is Proprietary and Confidential.
// </copyright>
//-----------------------------------------------------------------------------------

[Triage] This is something the we should open an issue for/fix in App Insights.  We may need to carry a fix depending on what the release schedule is for app insights and if we can upgrade before GA.  If not possible we will have to cloak this file.

The license seems to have been corrected in the original repo thanks to Omair's report -> https://github.com/microsoft/ApplicationInsights-dotnet/issues/2670
In main the file also does not have the indicated line - https://github.com/microsoft/ApplicationInsights-dotnet/blob/main/LOGGING/test/Shared/CustomTelemetryChannel.cs#L2-L4
So it seems we are just carrying a version that does not have the fix. I'll check the minimum version that would have the fixed header

So source-build-externals is on 2.21.0 and the fix is available with 2.22.0-beta1.
Currently in NuGet the latest available version is 2.22.0-beta3. Not sure how happy would the repos be if we were to ask them to pick-up a beta version.

I don't think we want to take a dependency on a beta version.  Can you find out/ask what when this would be released?  If it is soon, we can just wait.

The milestone that is referenced in issues for 2.22 is running late for almost a month - https://github.com/microsoft/ApplicationInsights-dotnet/milestone/50
I'll create an issue asking for some estimation we could use

https://github.com/microsoft/ApplicationInsights-dotnet/issues/2792


Update deleteTag to be case-insensitive

Fixes #156, fixes #229

Codecov Report

Merging #230 (d84ed1b) into master (2f5063f) will increase coverage by 0.39%.
The diff coverage is 94.11%.

@@             Coverage Diff              @@
##             master     #230      +/-   ##
============================================
+ Coverage     69.05%   69.44%   +0.39%
- Complexity      645      652       +7
============================================
  Files            96       96
  Lines          2133     2144      +11
  Branches        270      271       +1
============================================
+ Hits           1473     1489      +16
+ Misses          561      557       -4
+ Partials         99       98       -1

Impacted Files
Coverage Δ
Complexity Δ

...java/seedu/module/logic/commands/RecurCommand.java
0.00% <ø> (ø)
0.00 <0.00> (ø)

.../seedu/module/logic/parser/RecurCommandParser.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

.../seedu/module/logic/commands/DeleteTagCommand.java
100.00% <100.00%> (ø)
11.00 <1.00> (+1.00)

...du/module/logic/parser/DeleteTagCommandParser.java
86.66% <100.00%> (ø)
3.00 <0.00> (ø)

...ain/java/seedu/module/logic/parser/ParserUtil.java
90.19% <100.00%> (+0.83%)
18.00 <0.00> (+1.00)

...va/seedu/module/logic/parser/TagCommandParser.java
70.58% <100.00%> (ø)
5.00 <0.00> (ø)

src/main/java/seedu/module/model/tag/Tag.java
100.00% <100.00%> (ø)
8.00 <1.00> (ø)

...rc/main/java/seedu/module/model/task/Workload.java
90.47% <0.00%> (+4.76%)
15.00% <0.00%> (+1.00%)

src/main/java/seedu/module/model/task/Name.java
100.00% <0.00%> (+9.09%)
9.00% <0.00%> (+1.00%)

...main/java/seedu/module/model/task/Description.java
100.00% <0.00%> (+9.09%)
9.00% <0.00%> (+1.00%)

... and 1 more

Continue to review full report at Codecov.

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


Mesop can be very slow if there are a lot of child components being rendered with click event handlers

I had a use case a few weeks ago where I was splitting up about 200 lines in box/text components and making them clickable. I noticed Mesop got very sluggish in this scenario so I removed it.
Didn't look into the root cause for this yet. My hunch is tree diffing with a lot of child components. But not sure.

Was it still slow when you removed the click handler?

I haven't had a chance to dig into the root cause yet. It's likely not the click handlers. I think they were all pointing to the same click handler reference with different keys. So I think my title is slightly misleading.


remove Getter and Setter annotation

Description
Remove @Getter and @Setter lombok annotation.

Codecov Report

Merging #412 into azure-config will increase coverage by 0.36%.
The diff coverage is 68%.

@@                Coverage Diff                 @@
##             azure-config     #412      +/-   ##
==================================================
+ Coverage           53.67%   54.03%   +0.36%
- Complexity            527      542      +15
==================================================
  Files                 143      143
  Lines                2340     2389      +49
  Branches              138      138
==================================================
+ Hits                 1256     1291      +35
- Misses               1002     1016      +14
  Partials               82       82

Impacted Files
Coverage Δ
Complexity Δ

...ure/spring/cloud/config/ConfigServiceTemplate.java
84.78% <ø> (ø)
13 <0> (ø)
:arrow_down:

...zure/spring/cloud/config/msi/ConfigAccessKeys.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...loud/config/msi/AzureCloudConfigMSIProperties.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...azure/spring/cloud/config/domain/KeyValueItem.java
92.59% <100%> (+9.25%)
17 <16> (+7)
:arrow_up:

...e/spring/cloud/config/domain/KeyValueResponse.java
80% <100%> (+5%)
3 <2> (ø)
:arrow_down:

...pring/cloud/config/AzureCloudConfigProperties.java
86.88% <88.88%> (-0.3%)
18 <16> (+8)

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 1856c27...6b48c4b. Read the comment docs.


"Host" header is always taken from URI and overwrite the set one.

GuzzleHttp\Client

    public function sendAsync(RequestInterface $request, array $options = [])
    {
        // Merge the base URI into the request URI if needed.
        $options = $this->prepareDefaults($options);

        return $this->transfer(
            $request->withUri($this->buildUri($request->getUri(), $options)),
            $options
        );
    }

There is no option to set the second parameter in $request-> withUri(..., ).
Host header is always overwritten by previously set value!
Is there any workaround? Thank you.

Yeah, sorry this is something that needs to be worked on. We're tracking this in https://github.com/guzzle/guzzle/issues/1297


Improve Error Cases when adding ports to server

The core API specifies that 0 is returned when the library fails to add a port.
/** Add a HTTP2 over plaintext over tcp listener.
    Returns bound port number on success, 0 on failure.
    REQUIRES: server not started */
GRPCAPI int grpc_server_add_insecure_http2_port(grpc_server* server,
                                                const char* addr)

Python has this behavior as well. But it is not documented. As a result, the most likely outcome for an application that fails to bind a port (e.g. in the case of multiple listeners without SO_REUSEPORT), is for the application to continue under the assumption that it is listening properly while it is actually incapable of handling requests.
I think we should do one of the following:

Handle the case that the result returned from core is 0 and throw a Python-level exception for it.
Improve the documentation to clarify the return value in case of error.

However, depending on how you view things, the first option could be seen as a backwards-incompatible change.

CC @lidizheng

I personally prefer the later option. My first reason is the same, it might break user. The second reason is that currently we only have one exception class grpc.RpcError, it isn't really fit into this scenario semantically.

As noted in the issue description, agree on the compatibility side. However, most of the errors that this would generate would fall firmly under OSError, which is built in.
I'll go ahead and put together a PR to clarify the documentation.

Fixed by https://github.com/grpc/grpc/pull/23632. After all, we picked the first solution.


TDI-37479 Added percent type schema infering

Please check if the PR fulfills these requirements

[x] The commit message follows Talend standard
[x] Tests for the changes have been added (for bug fixes / features)

What is the current behavior? (You can also link to an open issue here)
SalesforceAvroRegistry returns String schema for Percent Salesforce specific data type
What is the new behavior?
SalesforceAvroRegistry returns Double schema for Percent Salesforce specific data type
Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:
Related to https://jira.talendforge.org/browse/TDI-37479

Pull request test result: success :star:

Why is percent expressed as a double? Wouldn't it be better as a decimal value? In general floating point is not used for commerce things like this (but maybe this is the way it's implemented in salesforce).

@sgandon,
I've added test-case
see SalesforceAvroRegistryTest.java
@francisu,
2 reasons for it:

It is a way it's implemented in Salesforce
https://developer.salesforce.com/docs/atlas.en-us.200.0.object_reference.meta/object_reference/field_types.htm
see percent type

Backward compatibility. Old (javajet) Salesforce treated percent as double type.

Pull request test result: success :star:


Resolve the readOnly dilemna

Background
In order to adhere to the DRY (Don't repeat yourself) principle, we have defined a single schema, for example Challenge.yaml, that we used for the body of a POST request and the response body. However, in the cases where the ID of the newly created entity is generated by the DB, the user is not expected to provide a value for this field as part of the body of the POST request.
OpenAPI provides the options readOnly: <boolean> and writeOnly: <boolean> that are meant to be used with object properties that should be provided only as input or output. These two options are well supported by the Node package @redocly/openapi-cli that we use to generate an HTML visualization of the schemas. However, the options readOnly and writeOnly not perfectly supported by the openapi-generator, depending the programming language select for the generated server/client codebase. In the case of python-flask server, the issue is that the schema examples (automatically?) created seem to ignore the options readOnly and writeOnly. Therefore we heading to the web page /api/v1/ui to try a request, the body of a POST request may include an ID. The request is then rejected because the current implementation of the python-flask throws an an error when receiving values for parameters that are marked as readOnly: true (the same error probably affect writeOnly). I don't have the link handy, but previous searches online revealed that the server should ignore values for properties marked as readOnly instead of throwing errors. A workaround may be for us to provide full schema example instead of example for individual properties that are then used by the generator to created a full example, see the section External Example.
Another issue is that we have started to define properties in their own file, like TagId.yaml. However, it is not possible to associated readOnly and writeOnly to a property that relies on the use of $ref. For example, the following code is not valid.
properties:
   tagId:
      $ref: ../parameters/TagId.yaml
      readOnly: true

Candidate solutions

Solution 1: Keep the current approach where we have one schema (e.g. Challenge.yaml) that includes the property challengeId referenced with $ref: ChallengeId.yaml. The backend just ignores this property if provided as input to a POST request. The example provided in the page /api/v1/ui could be a bit confusing because they include challengeId as a possible parameter for the input, while the backend actually ignore this value.

A possible partial workaround is to find a way to have more control over the example provided, for example by specify different examples when a schema is used as input or output.

Solution 2: Create different schema, for example ChallengeCreateRequest following the approach adopted by Nextflow Tower (see their OpenAPI spec, search for "TraceCreateRequest").

I may be convinced to adopt Solution 2 because it provides more flexibility and would make our documentation more user-friendly. Because the solution adopted would be used to improve our other APIs that follow the same development model, I'm looking forward to hearing your thoughts @vpchung @thomasyu888 .

Thanks @tschaffter for the details.  It's a bit unfortunate that we run into those issues when using readOnly and writeOnly as I think that is probably the most pretty solution.  That being said,  I am inclined to support "solution 2":

Even though it may not adhere to DRY completely, I agree that this would provide us with more flexibility.  We could try to use allOf where we can to reduce the number of duplicated information: example)
This solution will most likely cause us the least trouble openapi-generator not supporting readOnly/writeOnly.  Although it may be worth it to open tickets to openapi-generator for them to to fully support those fields.

Thanks @tschaffter for the details.  It's a bit unfortunate that we run into those issues when using readOnly and writeOnly as I think that is probably the most pretty solution.  That being said,  I am inclined to support "solution 2":

Even though it may not adhere to DRY completely, I agree that this would provide us with more flexibility.  We could try to use allOf where we can to reduce the number of duplicated information: example)
This solution will most likely cause us the least trouble openapi-generator not supporting readOnly/writeOnly.  Although it may be worth it to open tickets to openapi-generator for them to to fully support those fields.

Sounds good! Pending @vpchung input.

We could try to use allOf where we can to reduce the number of duplicated information: example)

I've seen this solution in the past. I've given it a try but I observed that the code generated by the generator was more obscure. I try to limit the use of allOf and oneOf whenever possible when using the openapi-generator until the generator handles these cases more elegantly.

Sounds good! Pending @vpchung input.

We could try to use allOf where we can to reduce the number of duplicated information: example)

I've seen this solution in the past. I've given it a try but I observed that the code generated by the generator was more obscure. I try to limit the use of allOf and oneOf whenever possible when using the openapi-generator until the generator handles these cases more elegantly.

I'm working on implementing Solution 2 (different schema for POST body request and return response) for the NLP Sandbox Data Node (see above ticket). I'm using the implementation of Tower NF as the main source of inspiration (link to their openapi.yaml posted above). I'll come back to this ticket once I have completed the task to share my findings.

I'm working on implementing Solution 2 (different schema for POST body request and return response) for the NLP Sandbox Data Node (see above ticket). I'm using the implementation of Tower NF as the main source of inspiration (link to their openapi.yaml posted above). I'll come back to this ticket once I have completed the task to share my findings.

It seems that OpenAPI 3.1 will enable the use of readOnly with $ref sibling (source).
This is an improvement in itself. This however does not solve the issue of openapi-generator generating faulty examples of body requests that include readOnly properties, making example requests in /api/v1/ui fail, which can confuse the user/developer.

It seems that OpenAPI 3.1 will enable the use of readOnly with $ref sibling (source).
This is an improvement in itself. This however does not solve the issue of openapi-generator generating faulty examples of body requests that include readOnly properties, making example requests in /api/v1/ui fail, which can confuse the user/developer.


How to intercept normal execution of program in case of eslint error

I need to display the eslint error message on the page when eslint reports an error

Hello,
As explained here this is not in the scope of this plugin.
You can try (vite-plugin-checker)[https://github.com/fi3ework/vite-plugin-checker] or less popular but more scoped (vite-plugin-eslint-logger)[https://github.com/Joker/vite-plugin-eslint-logger]


Timing question

start
	save c = C4, E4, G4
	save dm = D4, F4, A4
	save em = E4, G4, B4
	save f = F4, A4, C5
	save g = G4, B4, D5
	save am = A4, C5, E5
	save bdim = B4, D5, F5

	chunk intro
		play g for 4b
		play c for 4b
		rest for 4b
	endchunk

	chunk chorus
		play g for 2b
		play c for 2b
		play dm for 2b
		play f for 2b
		rest for 3b
		play c for 1b
	endchunk

	run intro with sound piano, loop for 2
	run chorus with sound piano
finish

Hello, me again 😄  I tried the following thing, I defined some basic chords, then make the composition using chunks, but they play at the same time. I think this is intended to allow to play multiple things at the same time.
I also tried to wrap the run intro in a block (see below), because that would make things run after each other but that doesn't seem to work either.  How to approach this?
	block
		run intro with sound piano
	endblock loop for 2

	block
		run chorus with sound piano
	endblock loop for 1

Hi @markknol! This is the expected behavior, as of the current version of Handel. Currently, running a chunk is the equivalent (conceptually) of creating a new song track. This is the case from wherever on the call stack the chunk is ran. So your first block loop would create 2 song tracks, and the second would create one song track. And they would all play at the same time.
To achieve what you're looking for in the above program, a rest  could be used. So:
start
	save c = C4, E4, G4
	save dm = D4, F4, A4
	save em = E4, G4, B4
	save f = F4, A4, C5
	save g = G4, B4, D5
	save am = A4, C5, E5
	save bdim = B4, D5, F5

	chunk intro
		play g for 4b
		play c for 4b
		rest for 4b
	endchunk

	chunk chorus
                rest for 24b
		play g for 2b
		play c for 2b
		play dm for 2b
		play f for 2b
		rest for 3b
		play c for 1b
	endchunk

	run intro with sound piano, loop for 2
	run chorus with sound piano
finish

The above would schedule the chorus to start after the second loop of the intro. Basically thinking of chunks as running at the same time gives the intuition of scheduling.
And if you don't want the rest  duration to be hard coded you can do something along the lines of:
start
	save c = C4, E4, G4
	save dm = D4, F4, A4
	save em = E4, G4, B4
	save f = F4, A4, C5
	save g = G4, B4, D5
	save am = A4, C5, E5
	save bdim = B4, D5, F5

	save wait = for 1b
    save times = 2
    update wait rshift 12 * times - 1

	chunk intro
		play g for 4b
		play c for 4b
		rest for 4b
	endchunk

	chunk chorus using abit
                rest abit
		play g for 2b
		play c for 2b
		play dm for 2b
		play f for 2b
		rest for 3b
		play c for 1b
	endchunk

	run intro with sound piano, loop for times
	run chorus using wait with sound piano
finish

The above sets the amount of times to loop the intro. Knowing the intro is 12 beats, its shifts the wait time by 12 * times (the amount of times to loop). And minus 1 because the original duration is 1b. So it is the equivalent of val += 12 * times  - 1  in other languages.
Of course you can take this further.

Hi @markknol. I considered this some more, and I'm now planning to introduce a way to call chunks synchronously using the call keyword. Will update you when that is live.
So chunks would now be able to be called with run and call. run creates a new conceptual song track, and takes parameters (using keyword) and  customizations  to track with the with keyword. call calls the chunk in the existing track and takes parameters but does not allow track customizations.

call functionality for running chunks in place (in the current track they are called in) is now live in Handel v0.8.10


Add force formula in Classical mechanics

Describe the solution you'd like
Add force calculator in classical mechanics along with some content about force.

Hi Amit, I'd like to work on this.

@Prashantvik heyy u can add but do u know exactly what u need to do??

hello @Amit366 sir, can you please assign this to me?

Can you please further elaborate on what is to be done.
I would like to work on this.

@mayank-wadhwa-git in the classical mechanics section add a heading as force. Now on clicking the heading force, a calculator will open up. In the calculator page there should be some content about force and also force calculator.

@mayank-wadhwa-git do u want to work on this issue??

Yes sir, I would like to try it.

ok

I would to like to work on this issue under DCP'21. Please assign this to me

@Hiteshsukhwani29 go ahead

@Hiteshsukhwani29 send the PR by 6 Aug.

sure

okay


Document Cipher Suite and TLS version used

OpenSearch has a list of default cipher suites:
https://github.com/opensearch-project/OpenSearch/blob/main/libs/ssl-config/src/main/java/org/opensearch/common/ssl/SslConfigurationLoader.java#L361
and it is also possible to configure the list:
https://opensearch.org/docs/latest/security/configuration/tls/#advanced-enabled-ciphers-and-protocols
However, as the different setting also impacts performance, I would like to document with which cipher suite is used while performing tests.
Can anyone document what is being used or tell me how to retrieve the information when doing the tests?

@IanHoang @gkamat ,,could you please take a look and share some comments here ,, thanks !!

The cipher suite is determined based on the initial TLS negotiation when the connection is established.  This is the first entry in the default list above, possibly limited by the restrictions noted and what is supported on the client end.
There is likely no straightforward way to Identify the cipher that gets selected apart from peeking at the network packets during the handshake.  Will check with some folks in Security to get more details.


Fix cloudstack e2e tests

Description of changes:
Return the proper required env var array.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/lgtm
/approve


Dc to ec

Summary
Bringing in the latest updates to docs into staging.
Link to Shortcut story.
Motivation
Update docs to latest UI, features, and nomenclature.
Checks

[ ] Run npm run test locally.
[ ] Create a Pull Request (follow the GitHub flow) and Conventional Commits Specification)
[ ] Verify any structural/CSS changes on all screen sizes (if relevant)

Cant resolve the only error as it relates to broken links, which we know cant be fixed until full DNS stuff is done.

Closed, because I incorporated changes via a different PR #258


Multiple performance optimizations

Codecov Report

Merging #75 into master will decrease coverage by 0.24%.
The diff coverage is 61.9%.

@@             Coverage Diff              @@
##             master      #75      +/-   ##
============================================
- Coverage     74.69%   74.44%   -0.25%
+ Complexity      664      655       -9
============================================
  Files            86       85       -1
  Lines          1972     1953      -19
  Branches        196      196
============================================
- Hits           1473     1454      -19
- Misses          357      358       +1
+ Partials        142      141       -1

Impacted Files
Coverage Δ
Complexity Δ

...rg/smof/bson/codecs/bytes/ByteCollectionCodec.java
47.05% <0%> (-14.48%)
4 <0> (ø)

...of/bson/codecs/number/SmofNumberCodecProvider.java
80% <100%> (-7.5%)
2 <0> (-1)

...mof/bson/codecs/bool/SmofBooleanCodecProvider.java
90% <100%> (ø)
3 <0> (ø)
:arrow_down:

...n/java/org/smof/collection/SmofCollectionImpl.java
86.17% <100%> (-0.79%)
26 <4> (ø)

...g/smof/bson/codecs/date/SmofDateCodecProvider.java
91.66% <100%> (ø)
3 <0> (ø)
:arrow_down:

...n/java/org/smof/collection/SmofDispatcherImpl.java
84.31% <100%> (+1.5%)
19 <2> (-2)
:arrow_down:

...ava/org/smof/collection/CollectionOptionsImpl.java
90.9% <100%> (ø)
11 <0> (ø)
:arrow_down:

...smof/bson/codecs/bytes/SmofBytesCodecProvider.java
90.9% <100%> (ø)
4 <0> (ø)
:arrow_down:

.../java/org/smof/collection/CollectionsPoolImpl.java
64.28% <52.38%> (-15.72%)
12 <6> (-1)

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 070ed1b...8eeeb28. Read the comment docs.