Feature Request: Icons scaling with font

It would be great if the icons scaled in size next to headings and such.

thanks for making this. I've been looking for a replacement since the other icons plugin seems to have been abandoned.

I agree with this. Just installed this plugin after I had issues with another popular icon plugin not rendering icons in IOS. This enhancement would make this plugin perfect


Fix nits in feature gates page

Issues fixed by this PR:

Link in PodDeletionCost is wrong.
Default value for APIResponseCompression since 1.16 should be true
Default value for KubeletPodResources in 1.13, 1.14 should be false
CSIVolumeHealth is an Alpha feature introduced in 1.21, not graduated or deprecated
EndpointSlice is still Beta in 1.20
EndpointSliceNodeName is only GA’ed in 1.21
IndexedJob is an Alpha starting 1.21, not graduated or deprecated
KubeletPodResources has been GA’ed in 1.20, thus should be removed from the first table
RequestManagement was deprecated in 1.17 and replaced by APIPriorityAndFaireness
Several field names are incorrect (e.g. appProtocol, internalTrafficPolicy, loadBalancerClass)
SCTPSupport should be removed from the first table because it was GA’ed in 1.20.
ServcieAppProtocol is Beta until 1.20
StreamingProxyRedirects  is GA’ed in 1.19, not deprecated
No description for ValidateProxyRedirects is provided
VolumeCapacityPriority is an Alpha feature introduced in 1.21, not graduated
The order of VolumePVCDataSource is wrong in the table
No description is provided for Initializers
The deprecated status should not be repeated in the description since it is already indicated by the table in which a feature is listed.
No description is provided for RequestManagement

/kind cleanup

Page preview:
https://deploy-preview-27575--kubernetes-io-master-staging.netlify.app/docs/reference/command-line-tools-reference/feature-gates/

Thanks @tengqm .
/approve

/lgtm


Initialization problem: No new migrations found. Your system is up-to-date.

Hi, in my development environment, I had previously initialized the comments extension and had a comments table. Then, I dropped the database, re-created the database and re-ran the migrations to rebuild it.
Now, when I run:
./yii migrate --migrationPath=@vendor/yii2mod/yii2-comments/migration
It says:
Yii Migration Tool (based on Yii v2.0.37)
No new migrations found. Your system is up-to-date.
How do I get the migration to run again?
Thank you for your extension!

anyone?


Can't integrate together using material table and geolocation

Bug, feature request, or proposal:
Proposal
What is the expected behavior?
I am developing the app that takes user's current location, and passed to backend. In the backend it return the list of restaurant that near user and using material table to display it. For more details, please see https://stackoverflow.com/questions/45618354/using-angular-material-2-table-to-display-the-result-from-backend-based-on-user
What is the current behavior?
Since material table database takes Observable, but in order to getlocation it must be async method, and it returns promise... I don't know how to make it works
What are the steps to reproduce?
N/A
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U
I only have github repo for this project: https://github.com/zhengye1/Eatr/tree/dev
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
@angular/cli": "^1.2.4",
@angular/material": "^2.0.0-beta.8",
Is there anything else we should know?
I asked this question to stackoverflow, but no one answer.... hopefully I can ask this question here

Hi,
If I understand well, the problem is that the geolocation returns a promise and the material table only support Observable?
I think you can convert a promise to an Observable thanks to the operator fromPromise. I don't really know how it works, see : https://github.com/Reactive-Extensions/RxJS/blob/master/doc/api/core/operators/frompromise.md


Add 'vault' provider.

Would you be able to add the 'vault' provider? See https://www.terraform.io/docs/providers/vault/index.html.

@lvets I am going to look into it but I am very busy at the moment so it won't be soon. Feel free to fork the repo, add the vault provider and submit a pull request if you feel confident to do so.

The following works with release 0.5.0.
ts = Terrascript()
ts += provider('vault', address='https://address.to.vault.provider:1234', token='TOKEN')
ts.validate()

Obviously this is a dummy example. Can you adapt this to your needs and provide feedback whether it works for you?
Thanks, Markus

I'll give it a try. I did a quick test and saw this:
$ python test1.py
{
  "provider": {
    "vault": {
      "__DEFAULT__": {
        "address": "https://address.to.vault.provider:1234",
        "token": "TOKEN"
      }
    }
  }
}
$

Any idea why that DEFAULT is there?

This __DEFAULT__ key in the vault dictionary is there to satisfy JSON syntax. It's a dummy key when a provider does not have an alias which is possible in HCL. If you look a the Multiple Provider section in the Terrafrom documentation you will see that only the second AWS provider has an alias.


Needed to merge the output of crabs insilico_pcr and crabs pga?

Hi,
If I understand correctly, it is advisable to both run crabs insilico_pcr, followed by crabs pga, but do we need to merge the output, and use that as input for crabs assign_tax?
Best,
Sam

Hello @slambrechts,
It is not essential to run the crabs pga function to build your reference database. The crabs insilico_pcr function will try to locate the primer-binding regions in all sequences you provide to CRABS. If your input file are all full-length sequences that cover the full region of the amplicon and the primer-binding region, all amplicons will be retrieved during the insilico_pcr step. For example, if the input file only contains full mitogenome sequences and you're trying to retrieve the COI amplicon from those sequences.
In some cases, the input file will contain a subset of sequences where the primer-binding region(s) might be missing. This can happen when the barcoding was done with one or both of the primers you are using in the insilico_pcr step or if sequences are incomplete (containing lots of N in a particular region). In this situation, crabs will not be able to retrieve the amplicon during the insilico_pcr step. Hence, running the crabs pga function is needed if your intent is to retrieve the amplicons from those sequences as well and want to incorporate those amplicons in your reference database.
The crabs pga function uses the output file from the insilico_pcr function as input file and the input file from the insilico_pcr function as a database (initially downloaded sequence file). CRABS will automatically subset the data from the raw sequence file (database) to remove the sequences for which the amplicon was already retrieved (input). CRABS will then run a pairwise global alignment against all sequences with the input file as seed sequences in the aim to retrieve amplicons for which the primer-binding regions are missing. The output file from the crabs pga function will contain the sequences retrieved during the insilico_pcr step, as well as the newly retrieved amplicons during the pga step. There is no need to merge the output of crabs insilico_pcr and crabs pga.
Best regards,
Gert-Jan

Hi @gjeunen,
Ok sounds perfect, thank you
Best,
Sam


Set up release, update, and versioning for bundled app

We need a way to couple the release of a new version of the app with a way to publish the new version and allow users to automatically update their apps (the way most apps let you check for updates which allows the app to get updated).
One thing to watch out for is that when we update the app we should also remember that prisma migrations may need to get run. How do we handle this?

This is currently blocked as CXL is exploring code signing certificates for Windows and MacOS


Fourth commit

Fixes or introduces:
Proposed Changes

I don't know how to do it exactly.
But I tried. Can you check it once please

It's a great attempt! Thanks! But it's not quite right.
Try once more but follow this article (but to this repository): https://auth0.com/blog/a-first-timers-guide-to-an-open-source-project/
If you still find it hard, I can finish for you :)

I tried again.
If it's still incorrect, can you please do it for me.
Sorry for the inconvenience
On Sat, Oct 6, 2018, 22:15 Luke Oliff<EMAIL_ADDRESS>wrote:

It's a great attempt! Thanks! But it's not quite right.
Try once more but follow this article (but to this repository):
https://auth0.com/blog/a-first-timers-guide-to-an-open-source-project/
If you still find it hard, I can finish for you :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/my-first-pr/hacktoberfest-2018/pull/152#issuecomment-427588493,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ap1si0QfkUhEDhyKYJZs5Yy0hruoYx36ks5uiN4ggaJpZM4XLIe2
.

That was very fast for you to have followed the guide :D I would strongly suggest following it (I wrote it, it's super simple!)
In the meantime, I've changed it for you :)

Thank you.
I will definitely follow it.
On Sat, Oct 6, 2018, 22:30 Luke Oliff<EMAIL_ADDRESS>wrote:

That was very fast for you to have followed the guide :D I would strongly
suggest following it (I wrote it, it's super simple!)
In the meantime, I've changed it for you :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/my-first-pr/hacktoberfest-2018/pull/152#issuecomment-427589745,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ap1si89qENPNqqzk0oO_ejPEpi5uM2sRks5uiOHFgaJpZM4XLIe2
.


Redis Client always connecting to local

Version: 2.8.0
Platform: Node.js v10.16.0 on macOS High Sierra
Description: I'm attempting to use options to connect to a redis instance at a specific host and port. When I provide the options while creating the client it still attempts to look for redis on my localhost (the default conifg).

const client = redis.createClient({ 	host: 'core_redis_1', 	port: 6379 });
I am getting the following error:
events.js:183, throw er; // Unhandled 'error' event
Redis connection to <IP_ADDRESS>:6379 failed - connect ECONNREFUSED

This is probably related to a hostfile, DNS or firewall issue. Try to connect using the same exact info with redis-cli: $ redis-cli -h core_redis_1 -p 6379 and troubleshoot from there.
I'm going to close this issue as it's probably not an issue with the library but rather your configuration. If you continue to have problems, reopen or start a new issue with more details.

@stockholmux im seeing the same issue but I am able to ping with redis-cli. What did you do to fix this?

I don't think host is supported anymore. I can pass anything and it will still connect to localhost.
    legacyMode: true,
    host: 'asdfasdfasdf',
    port: 6379,
    password: env.get('REDIS_PASSWORD')
  })```

legacyMode does not support v3 config, try this instead:
createClient({
  legacyMode: true,
  socket: {
    host: 'asdfasdfasdf',
    port: 6379,
    password: env.get('REDIS_PASSWORD')
  }
});

This ended up working for me
    legacyMode: true,
    url: `redis://:passwordHere@$hostHere:portHere`
  });

I struggled with this for some weeks, and this was how i solved that problem:

install redis v3.1.2,
then... create the client like so:
✅  const client = redis.createClient({         password: redis_password         host: redis_host,         port: redis_port,     });
please, do not add the credentials in the socket objec i.e:
❌!   const client = createClient({       socket: {         host: redis_host,         port: redis_port,       }         password: redis_port,       });


[SPARK-27558] Check if array is null at UnsafeInMemorySorter.getMemoryUsage

What changes were proposed in this pull request?
NPE is got when the array is null in UnsafeInMemorySorter.class.
Why are the changes needed?
These changes will check if array is null and it should help to avoid NPE.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
It was tested manually.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

cc @JoshRosen

Test build #113056 has started for PR 26349 at commit 5aa5b20.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/17977/
Test PASSed.

Test build #113056 has finished for PR 26349 at commit 5aa5b20.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/113056/
Test PASSed.

retest this please

Test build #114041 has started for PR 26349 at commit 5aa5b20.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/18902/
Test PASSed.

Seems fine as a defensive check, though I wasn't clear how this gets called at cleanup time.

It registers TaskCompletionListener and then calls cleanupResources() https://github.com/apache/spark/blob/eef5e6d348e7025f48e8f69026254e07efe80894/core/src/main/java/org/apache/spark/util/collection/unsafe/sort/UnsafeExternalSorter.java#L178
Then the stack trace is freeMemory() -> updatePeakMemoryUsed() -> getMemoryUsage() -> inMemSorter.getMemoryUsage().

Test build #114041 has finished for PR 26349 at commit 5aa5b20.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/114041/
Test PASSed.

Thanks, merged to master!

@ayudovin Could you help submit a PR to Spark 2.4?

@gatorsmile, ok, no problem, I'll do it

@gatorsmile, I have created PR.


Color changes but site says it didn't

Challenge use-css-selectors-to-style-elements has an issue.
User Agent is: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0.
Please describe how to reproduce this issue, and include links to screenshots if possible.

CatPhotoApp

Click here to view more cat photos.

Things cats love:

cat nip

laser pointers

lasagna

Top 3 things cats hate:

flea treatment

thunder

other cats

  <form action="/submit-cat-photo">
    <input type="radio" name="indoor-outdoor" checked> Indoor
    <input type="radio" name="indoor-outdoor"> Outdoor

    <input type="checkbox" name="personality" checked> Loving
    <input type="checkbox" name="personality"> Lazy
    <input type="checkbox" name="personality"> Energetic

    <input type="text" placeholder="cat photo URL" required>
    <button type="submit">Submit</button>
  </form>

See the issue #13608 with temporary solution.
The main issue is #10749

As @fonsecapontes pointed out ;)
Closing it as a kind of duplicate for now


Only LDH admins can assign 'NFDI4Health PIs'

Describe the bug
We noticed, that only LDH admins can assign the role 'NFDI4Health PIs'.
For normal user, even trial project administrators, this option is not visible.
From my point of view, that is a major flaw und must be corrected. Otherwise users cannot add studies to the LDH and upload them to the CSH themselves.
To Reproduce
Steps to reproduce the behavior:

Create a study with a non-admin account
Check if you can assign the role of PI
Switch to an admin account
Check again

Expected behavior
Users assigned to the projects, at least Trial project administrators, must have the right to assign PIs to a trial project
Screenshots
Admin view:

User (Trial project administrator) view:

We see the problem. The Project Administrator should be able to set the PI (=PAL) - currently only the Seek Admin can. We request this.


adds newsletter form and css

Adds a simple newsletter form to the website
Resolves #237

Good work for the newsletter 📰 👏🏾


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


CUDA out of memory when training "google/pegasus-cnn_dailymail" on "samsum"

Information
The problem arises in chapter:

[ ] Introduction
[ ] Text Classification
[ ] Transformer Anatomy
[ ] Multilingual Named Entity Recognition
[ ] Text Generation
[x ] Summarization
[ ] Question Answering
[ ] Making Transformers Efficient in Production
[ ] Dealing with Few to No Labels
[ ] Training Transformers from Scratch
[ ] Future Directions

Describe the bug
Training with the "google/pegasus-cnn_dailymail" model and "samsum" dataset on a local system with 8G GPU results in CUDA out of memory errors that can not be resolved with simplistic memory management steps like os.environ["PYTORCH_CUDA_ALLOC_CONF"] = "max_split_size_mb:24" or deleting unused objects that are on the GPU
OutOfMemoryError: CUDA out of memory. Tried to allocate 16.00 MiB (GPU 0; 7.79 GiB total capacity; 6.75 GiB already allocated; 7.94 MiB free; 6.91 GiB reserved in total by PyTorch)
With batch_size set to 1 we can't reduce any further, and with the memory error triggered by a 16M object vs. a minimum max_split_size of 20, there's nothing further that can be done with those two simple adjustments.   Furthermore, there doesn't seem to be a lighter version of "google/pegasus-cnn_dailymail" on Hugging Face
To Reproduce
Steps to reproduce the behavior:

load the "google/pegasus-cnn_dailymail" model
load and process the "samsum" dataset
set training arguments:num_train_epochs=1,
warmup_steps=500,
per_device_train_batch_size=1,
per_device_eval_batch_size=1,
weight_decay=0.01,
logging_steps=10,
push_to_hub=False,
evaluation_strategy='steps',
eval_steps=500,
save_steps=1e6)
train()
OOM!

Expected behavior
Expectation here is that there would be something, anything I could do to (re)train this model, even if it meant slowing down the process.

In Chapter 6 - Summarization Training - Fine Tuning, I tried everything I could think of to make the PEGASUS retrain work.   We start with google/pegasus-cnn_dailymail, then add the Samsung Summaries dataset, then train on it.
Many many configurations and techniques failed to avert the "CUDA error: out of memory" error.   What isn't apparent, however, is that there are some highly effective memory saving steps that you can take just by adding some training arguments.
Also what isn't obvious, is that when a model trains, it is highly likely that it will expand to a huge size very quickly and then continue to grab more GPU memory, so all the steps you might take to setup the memory in preparation for train() are of no use, unless you've setup training arguments to not blow up.
Another thing that's not obvious is that many models 'almost fit', or 'just barely fit', and minor adjustments can actually make them fit and train.   With other models, the complexity of the model and its training demands more invasive changes.
NOTE: the reason models blow up in size is typically because size is being balanced with speed.    I believe that every single step below makes training models slower.   In some cases you'd want to compare with training on the CPU, especially if you have a lot of cores and huge RAM.
The other more pernicious potential issue is models that perform poorly or "not as well as they ought to".
This is all just to say that, models that train are better than models that don't train at all, but maybe not by much.
PYTORCH_CUDA_ALLOC_CONF
The change that's actually suggested right in the error message is modifying PYTORCH_CUDA_ALLOC_CONF.   What's not necessarily obvious though is that this value should be set as low as possible, because it's impossible to predict the size of the thing that Torch is going to try to allocate, and if it's smaller than PYTORCH_CUDA_ALLOC_CONF, it will fail.   I've even seen things like 16M objects crash a training, which, so sad, you can't do anything about because PYTORCH_CUDA_ALLOC_CONF minimum is 20M.
Anyway - os.environ["PYTORCH_CUDA_ALLOC_CONF"] = "max_split_size_mb:24"
Training Args
batch_size
Next most commonly recommended, and most commonly effective, is batch size.   What isn't obvious is how big each batch is, all things included.   Where the initial batch size is greater than 2, you can often just iteratively dial it down until your train() runs.
batch_size=4 (or whatever is less than what you started with - if desperate then 2, then 1)   (default is 8)
When you hit 1 you are totally out of luck.   Unless of course you're reading this guide, in which case - follow me...
gradient_accumulation_steps
Even in the lifesaving HF guide to "How to Fit a Bigger Model", they describe this as follows:

The idea behind gradient accumulation is to instead of calculating the gradients for the whole batch at once to do it in smaller steps, by calculating the gradients iteratively in smaller batches by doing a forward and backward pass through the model and accumulating the gradients in the process. When enough gradients are accumulated we run the model’s optimization step. This way we can easily increase the overall batch size to numbers that would never fit into the GPU’s memory.

Okay, yes, correct, but: this also works when no batch size, including 1, will train().   In other words, this can actually be a lifesaver when you have no more batch_size reductions available.
Of course it's also a good idea for tuning your batch sizes if that's something you have the luxury of focusing on.
It may not be obvious, but it's a larger value we want here.
gradient_accumulation_steps=64  (default is 1)
gradient_checkpointing

In order to compute the gradients during the backward pass all activations from the forward pass are normally saved. This can create a big memory overhead. Alternatively, one could forget all activations during the forward pass and recompute them on demand during the backward pass. This would however add a significant computational overhead and slow down training.

Gradient checkpointing strikes a compromise between the two approaches and saves strategically selected activations throughout the computational graph so only a fraction of the activations need to be re-computed for the gradients. See this great article explaining the ideas behind gradient checkpointing.

Fine, whatever - gradient_checkpointing=True  (default is False)
optimizer

The most common optimizer used to train transformer model is Adam or AdamW (Adam with weight decay). Adam achieves good convergence by storing the rolling average of the previous gradients which, however, adds an additional memory footprint of the order of the number of model parameters. One remedy to this is to use an alternative optimizer such as Adafactor.

Instead of keeping the rolling average for each element in the weight matrices Adafactor only stores aggregated information (row- and column-wise sums of the rolling averages) which reduces the footprint considerably. One downside of Adafactor is that in some instances convergence can be slower than Adam’s so some experimentation is advised here. We can use Adafactor simply by setting optim="adafactor":

This one seems to have been recently modified - I had to upgrade my transformers and accelerate in order for tha argument to be accepted
optim="adafactor" (default is adamw_hf)
Finally, the model trained!   (slowly)
Resources:

https://huggingface.co/docs/transformers/v4.19.2/en/performance


Improve camera frame rate

Camera frame rate is influences by

image size; smaller images, especially 640x480 and below, produce better frame rates
number of frame buffers allocated.  There should be at least 2 buffers allocated.  This is only possible for lower resolution modes and with PRAM available.
The clock rate.  It turns out a lower clock rate can enhance framerate on low resolutions, perhaps because all the work the sensor does can be done within a single frame.  See https://github.com/espressif/esp32-camera/issues/15

NOTE: the way memory is partitioned is important to make sure there is enough available for multiple frame buffers.  The ESP32-Cam example sketches us the 'Huge APP' partition scheme.  So we should make sure we've made enough memory available for our system to have multiple frame buffers.  See https://iotespresso.com/how-to-set-partitions-in-esp32/  See this for how to set partition table in platformio https://community.platformio.org/t/partion-scheme-no-ota-with-platformio/13102/8  See relevant PlatformIO docs https://docs.platformio.org/en/latest/platforms/espressif32.html#partition-tables
Tasks;

experiment with combinations of image size, frame buffers and clock rate to optimize frame rate

do this with and without factoring in the transfer of the images, so that we see the raw rate and the overhead imparted by transferring to the web UI.

Review partition table settings to make sure they support the configuration.  If possible leave memory for OTA, as that would be a much nicer way of programming the board.
Add a compile flag to fix the frame size, number of buffers allocated and the clock rate to the chose parameters
Hide the camera properties UI when the image properties are fixed.
Hard code the camera properties endpoint to return the fixed properties.

Donkeycar uses 160x120, so that might be what we want here.  However 640x480 is much better quality for FPV, so maybe we want a way to switch between these two mode.

Hi, @Ezward , did you manage to find something about increasing the framerate? Im using arduino ide, and struggle with the driver. Greetings.


Improve docs of Multi

The statement "Accepts the same arguments and options" was confusing because the other functions don't have a name argument

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


feat: provide android image uri

fix #1083
tested on android 29（requestLegacyExternalStorage="true"） and android 34

Thanks for the contribution. Closing in favor of #1094.


Only show XX hours in Snapshots Gallery

Hopefully there is a way and I missed it, otherwise this might be a very useful feature.
I monitor events mostly based on triggers, but it would be helpful to see only the day of events (or events in the last XX hours) when looking at the dashboard.

I monitor events mostly based on triggers, but it would be helpful to see only the day of events (or events in the last XX hours) when looking at the dashboard.

In the gallery there is a "When" filter in the drawer on the right hand side, that should let you narrow it down to the past day. Is that what you mean? If not, can you describe a little more the feature / usecase? Perhaps you mean in the thumbnail carousel on a non-gallery view?

Please re-open with additional details if you'd like to pitch for a new feature!


Add constructor keyword & default function

It would be useful to save the creator of the contract for administrative purposes. Solidity has this useful pattern:
contract SomeContract
{

address public owner;

constructor() public {
    owner = msg.sender;
}

}

Great :) The keyword init is quite nice too.

I've created #174 to track work on a fallback function mechanism.


Download Command fails when creating jfrog.cli.temp*

My team is having an issue in 1.39.3 where we attempt to sync with a folder on artifactory, the downloads all succeed but the command still fails on creating the temp file. For example:
jfrog rt dl --flat=true --threads=8 --sync-deletes="dl_dir" --quiet repo_path dl_dir

 Log path: C:\Users\maiteko\.jfrog\logs\jfrog-cli.2020-09-08.09-29-25.18940.log [---------------]
 Log path: C:\Users\maiteko\.jfrog\logs\jfrog-cli.2020-09-08.09-29-25.18940.log
{
  "status": "failure",
  "totals": {
    "success": 48,
    "failure": 0
  }
}
[Error] mkdir C:\Users\MAITEKO~1\AppData\Local\Temp\jfrog.cli.temp.-1599578966-235641541\C:: The filename, directory name, or volume label syntax is incorrect.

it looks like that \C:: is probably the problem.
Because of the failure getting returned, it stops our automated scripts, and prevents other assets from being downloaded.

if it's not obvious, this is specific to windows, I should have said that in the first place.

Hi @maiteko thanks for reporting this issue.
The fix is included in the 1.39.5 release.
We would appreciate any feedback from you.

Hey, thanks, that looks like it solved the problem :)


Create a HttpContext Based Managed Tracer

This PR Creates an IManagedTracer that is a wrapper around another IManagedTracer which it accesses via the current HttpContext.  This allows for a singleton IManagedTracer.
The IManagedTracer is now created in the middleware right before it is used and then set on the HttpContext. The current HttpContext can always be accessed by a singleton IHttpContextAccessor this allows for a singleton IManagedTracer so users do not have to deal with scoping issues of the IManagedTracer.
This change does mean users who try to trace anything before the trace middleware is registered will just be using a null managed tracer and not tracing anything.  I think this is acceptable for now as this seems like it will be a small use case and we would need to be careful about how we handle the spans.
Fixes #835
This is a similar access model to the AspNet library.

There are test failures. Should I hold off on reviewing until they are fixed or is it safe to review?

It's safe to review.  I just submitted a fix. Thanks Mike!

Ah - so public async Task Invoke(HttpContext httpContext, IManagedTracer tracer) in CloudTraceMiddleware gets the scoped tracer injected automatically? That makes sense. Presumably we could use the context-based one there too, but we don't need to.
Okay, LGTM (IIRC - it's hard to keep track of where I was on this).


Executing a cancelled action

Bug Report
Current Behavior
This code is throwing "Executing a cancelled action " after a while:
import { Observable } from "rxjs"

export default function visibilityState(): Observable<VisibilityState> {
  return new Observable(o => {
    o.next(window.document.visibilityState) // throws here!

    const handle = () => o.next(window.document.visibilityState)

    window.addEventListener('visibilitychange', handle)
    return () => window.removeEventListener('visibilitychange', handle)
  })
}

At this callsite:

which is in turn called from:

Stacktrace; and "Angular" is nowhere near my code, I assure you.
Uncaught Error: executing a cancelled action
    RxJS 2
        execute
        flush
    Angular 8
        invokeTask
        runTask
        invokeTask
        invoke
        timer
        setInterval handler*scheduleTask
        scheduleTask
        scheduleTask
AsyncAction.js:49
    RxJS 2
        execute
        flush
    <anonymous> self-hosted:982
    Angular 12
        invokeTask
        runTask
        invokeTask
        invoke
        timer
        (Async: setInterval handler)
    scheduleTask
        scheduleTask
        scheduleTask
        scheduleMacroTask
        scheduleMacroTaskWithCurrentZone
        setNative
        name
    RxJS 44
        requestAsyncId
        schedule
        schedule
        schedule
        interval
        _trySubscribe
        subscribe
        innerSubscribe
        _innerSub
        _tryNext
        _next
        next
        subscribeToArray
        _trySubscribe
        subscribe
        call
        subscribe
        subscribeToResult
        _complete
        complete
        subscribeToArray
        _trySubscribe
        subscribe
        call
        subscribe
        call
        subscribe
        innerSubscribe
        openBuffer
        notifyNext
        _next
        next
        _next
        next
        notifyNext
        _next
        next
        notifyNext
        _next
        next
        _next
        next
        _next
        next
    visibilityState visibilityState.js:6
    RxJS 43
    visibilityState visibilityState.js:6
    RxJS 25

Reproduction:
This repeats when I switch tabs, after a while. I'm not sure why: the calling code looks like this:
const triggerOnChangeTab = () => {
  if (typeof window === 'undefined') return from([])
  return visibilityState().pipe(
    filter(x => x === 'hidden'),
    tap(() => console.debug('visibilityState => "hidden"'))
  )
}

export default function periodicRequest<TRes>(
  connectivityStream: () => Observable<boolean>,
  makeRequests: Observable<TRes>,
  period: number = 500,
  extraTriggers: () => Observable<string> = triggerOnChangeTab
) {
  const trigger = () =>
    combineLatest([
      connectivityStream(),
      // this second parameter acts as the trigger, either every broadcast interval, or when the page is hidden
      merge(interval(period), extraTriggers())
    ]).pipe(filter(([online, _]) => online))

  return makeRequests.pipe(bufferWhen(trigger))
}

According to the code, in visibilityState; the crash comes immediately, so perhaps the observable is created and immediately cancelled, causing this issue.
Expected behavior
A clear and concise description of what you expected to happen (or code).
Environment

Runtime: [e.g. Node v${x}, Chrome v${x}] Firefox 79
RxJS version:

<EMAIL_ADDRESS>  version "6.6.2"
  resolved "https://registry.yarnpkg.com/rxjs/-/rxjs-6.6.2.tgz#8096a7ac03f2cc4fe5860ef6e572810d9e01c0d2"
  integrity sha512-BHdBMVoWC2sL26w//BCu3YzKT4s2jip/WhwsGEDmeKYBhKDZeYezVUnHatYB7L85v5xs0BAQmg6BEYJEKxBabg==
  dependencies:
    tslib "^1.9.0

(If bug is related) Loader, build configuration: [e.g webpack, angular-cli version, config]: nextjs:

<EMAIL_ADDRESS>  version "9.5.2"
  resolved "https://registry.yarnpkg.com/next/-/next-9.5.2.tgz#ef9b77455b32dca0e917c763529de25c11b5c442"
  integrity sha512-wasNxEE4tXXalPoUc7B5Ph3tpByIo7IqodE9iHhp61B/3/vG2zi2BGnCJjZQwFeuotUEQl93krz/0Tp4vd0DsQ==
  dependencies:
    "@ampproject/toolbox-optimizer" "2.6.0"
    "@babel/code-frame" "7.8.3"
    "@babel/core" "7.7.7"
    "@babel/plugin-proposal-class-properties" "7.8.3"
    "@babel/plugin-proposal-export-namespace-from" "7.10.4"
    "@babel/plugin-proposal-nullish-coalescing-operator" "7.8.3"
    "@babel/plugin-proposal-numeric-separator" "7.8.3"
    "@babel/plugin-proposal-object-rest-spread" "7.9.6"
    "@babel/plugin-proposal-optional-chaining" "7.9.0"
    "@babel/plugin-syntax-bigint" "7.8.3"
    "@babel/plugin-syntax-dynamic-import" "7.8.3"
    "@babel/plugin-transform-modules-commonjs" "7.9.6"
    "@babel/plugin-transform-runtime" "7.9.6"
    "@babel/preset-env" "7.9.6"
    "@babel/preset-modules" "0.1.3"
    "@babel/preset-react" "7.9.4"
    "@babel/preset-typescript" "7.9.0"
    "@babel/runtime" "7.9.6"
    "@babel/types" "7.9.6"
    "@next/react-dev-overlay" "9.5.2"
    "@next/react-refresh-utils" "9.5.2"
    ast-types "0.13.2"
    babel-plugin-syntax-jsx "6.18.0"
    babel-plugin-transform-define "2.0.0"
    babel-plugin-transform-react-remove-prop-types "0.4.24"
    browserslist "4.13.0"
    buffer "5.6.0"
    cacache "13.0.1"
    chokidar "2.1.8"
    crypto-browserify "3.12.0"
    css-loader "3.5.3"
    cssnano-simple "1.0.7"
    find-cache-dir "3.3.1"
    jest-worker "24.9.0"
    loader-utils "2.0.0"
    mini-css-extract-plugin "0.8.0"
    mkdirp "0.5.3"
    native-url "0.3.4"
    neo-async "2.6.1"
    node-html-parser "^1.2.19"
    path-browserify "1.0.1"
    pnp-webpack-plugin "1.6.4"
    postcss "7.0.32"
    process "0.11.10"
    prop-types "15.7.2"
    prop-types-exact "1.2.0"
    react-is "16.13.1"
    react-refresh "0.8.3"
    resolve-url-loader "3.1.1"
    sass-loader "8.0.2"
    schema-utils "2.6.6"
    stream-browserify "3.0.0"
    style-loader "1.2.1"
    styled-jsx "3.3.0"
    use-subscription "1.4.1"
    vm-browserify "1.1.2"
    watchpack "2.0.0-beta.13"
    web-vitals "0.2.1"
    webpack "4.44.1"
    webpack-sources "1.4.3"

Possible Solution
Don't crash the "constructor"; it doesn't matter as a user what scheduler you're using, if the constructor (aka. callback that instantiates the observable) can't run to completion.
Noteworthy:
I also have this package installed and initialised in the browser, which might affect your usage of Zone.js (if you're using it):
"<EMAIL_ADDRESS>  version "0.10.2"
  resolved<EMAIL_ADDRESS>  integrity sha512-ZJQ8Pbm3pTkoyZSkIOq1cZrmRL+HuTC4KTOnzE5qUg3+5h608zyRT1PMIIhR8+mvFZLHcDyGrs7sSJfpW7a6iw==
  dependencies:
    "@opentelemetry/api" "^0.10.2"
    "@opentelemetry/context-base" "^0.10.2"
    "@opentelemetry/core" "^0.10.2"
    "@opentelemetry/semantic-conventions" "^0.10.2"
    "@opentelemetry/tracing" "^0.10.2"

Ping

I'm facing the same issue randomly when running karma unit tests and angular. Some runs are fine, some are failing.
I've checked the setInterval/clearInterval calls and it seems they are called correctly even when the error pops up(number of calls to setInterval equals number of calls to clearInterval). The subscriptions are also correctly unsubscribed.
In my case the issue originates from the usage of the throttleTime(), which uses asyncSubscriber under the hood. Also, zone.js is used, which patches the setInterval, which may somehow conflict with rxjs in this instance.
@cartant Any advice on how I can investigate this further? Here are the stacktraces:

@pshurygin Instead of commenting on a closed issue, it's always preferable to open a new issue, fill out the template and refer the related issue. IDK what version you are using, etc.
Regarding what you can do next:

Does it always fail in the same test?
Does it fail if only that test runs?
Does if fail if that test and a subset of the other tests run?
What does the code in the test look like? Can it be simplified? Make it as simple as possible and then post the code. (In the separately-opened issue that includes your version information, etc.)

Fundamentally, the aim is to reduce the scenario that effects the problem to be as simple as possible. Hopefully, simple enough to share so that someone else can reproduce it.
@kwonoj I thought we had a bot that locked inactive, closed issues. Is that no longer a thing?

I think it's still thing? Haven't checked it recently though.

This issue came up at Google, I'm reopening it, although no one has been able to come up with a simple reproduction. :\

I believe it started with this PR: https://github.com/ReactiveX/rxjs/pull/5619
cc @cartant

Actually... this isn't quite the same thing as what I was talking about... :\  Closing again. We'll need to file another issue.

(I know it's closed. And there is no open issue for this problem currently.)
I see this in our logs occasionally, in our Angular app<EMAIL_ADDRESS>No idea how to reproduce. Mostly happens on Windows. Very rare anyway.
If I ever get more details, I'll file a new issue. But most probably I'm just gonna ignore it.

Actually... this isn't quite the same thing as what I was talking about... :\ Closing again. We'll need to file another issue.

@benlesh Was another issue filed? This issue seems to be occurring in rxjs v7. (Can't reproduce just yet. Will update if I can)

We are also facing the same issue and we have seen that it happens immediately after an "npm i" and then running our unit tests. Then after 1-2 times of executing our unit tests its stops comming

@nanditsaini  @pshurygin  @rahcusa what did you guys do for the flaky nature of the unit test. I am facing the same issue "Executing a cancelled action" in my jasmine tests for angular 16 application. Sometimes they fail and sometimes they pass.


only send readonly to replicas once on new connections

replicas have more CPU load because of extra commands(2x) than masters.

@duke-cliff Most tests fail with this current solution.Seems like the core solution/idea do not work as you expect in your commit there.

@duke-cliff Also how is this implementation different from the following code lines that exists in the on_connect method? https://github.com/Grokzen/redis-py-cluster/blob/6f1fb57c9522ce65ccea7d1a75b1118a32634d02/rediscluster/connection.py#L62

@Grokzen I don't think that code works.

It's only working for readonly=True. However, we need to check read_from_replicas=True
It's getting the value from kwargs: https://github.com/Grokzen/redis-py-cluster/blob/6f1fb57c9522ce65ccea7d1a75b1118a32634d02/rediscluster/connection.py#L51
But it won't even pass the named params(including read_only/read_from_replcias) from here: https://github.com/Grokzen/redis-py-cluster/blob/2.1.0/rediscluster/client.py#L375
In the ClusterConnection class, I think it might be too late because the connection object itself does not know the node information which contains whether the spawned connection is from a master node or a slave node. Unless you have some different thoughts, e.g to pass the node info to every connection object.

@duke-cliff Actually it will be passed down if i traced the code correct but the path is a bit strange :)
Setting readonly_mode=True into the RedisCluster class will change the connectionpool class to ClusterReadOnlyConnectionPool and it hardcodes readonly=True when it calls the super() function to ClusterConnectionPool which in turn is bound into connection_kwargs in the ClusterConnectionPool and those kwargs should be set/sent into each ClusterConnection class and it should be tracked for each connection created.
But... the downside with this is that if you set readonly mode, then you will send readonly to all nodes in the cluster when ever any connection is created. Even master nodes which technically is redundant but should not hurt in reality.
I do like this implementation as well, as it properly only sends it to slave nodes and it might work with all subclassed cluster connection pools as well as it moves the logic away from the connection side of things into the generic connection pool which is good, and the hack/workaround in the main client execute logic is removed which i like as well :)

I'm reviewing this thread and the associated branch now – based on what you said above @Grokzen, does this mean we can simply remove these lines and instead rely on the READONLY command that gets sent during connection init here, as you describe?


feat: Update thread to write to mda zarr

followup of #258.
In this PR I've updated the code with the suggestions in #258 + I've added a method (_process_remaining_frames) that is used to add to the zarr layer(s) any frames remaining in  _deck after the acquisition is finished. Note that at the moment, since we don't have a proper writer in napari-micromanager this method is called by _on_mda_finished but once we have a writer, we can simply link this method to _io_thread _connect ("finished": self._process_remaining_frames).
To speed up the process it was also necessary to specify the chunk size when creating the zarr.
I did few test on our microscope and this way of handling the acquired images works great!
In addition I've added some fixes for the use of the current pymmcore-widgets (main git branch).
Test failing until new release of pymmcore-widgets.
closes #258.

The private _sequence module definitely shouldn't be imported here.  Let's talk about what you need to accomplish and make it public if there's no other way

The private _sequence module definitely shouldn't be imported here. Let's talk about what you need to accomplish and make it public if there's no other way

Sure :) I'm doing some tests with your sequencable PR and it's awesome!!! I pushed this commit to not loose the testing progress :)

In addition I've added some fixes for the use of the current pymmcore-widgets (main git branch).

@fdrgsp can you please make this a separate self contained PR. Wrapping it up in a big PR like this makes it difficult for me to work on other things (and led to me thinking this was an unfixed bug: https://github.com/pymmcore-plus/napari-micromanager/issues/268)

closing. Open a simpler version #272.


IPv4s just got 3 digits per octet

Just a beauty mistake.

I don't mean to rain on your parade, but that's actually intentional: If we print three Xs, the user might assume that we have specifically censored a three-digit octet (not a two- or one-digit octet). With four Xs, it's very obvious that this is a generic replacement string. (Same with v6 where four Xs don't make sense without a :: shortening mark.)
Sorry… :/

It might be interesting to actually show the subnet mask used on the system (and correctly omit the host bits of the address), but that might leak too much information again (and be hard to implement for edge cases, e.g. internal IP ≠ public IP)…

You could curl ipinfo.io to gather the public IP address or one of the many other services.


Update dashboard design

Update dashboard to reflect latest comps -> https://hp.invisionapp.com/d/main#/projects/prototypes/9984910
This can probably be split up into different tasks as it's a big endeavour.

We are looking good with this.


How to pass values between resolvers

I've been using a lot this library (and i really enjoy it), and i'm moving my client side to relay.
I had a problem with the viewer pattern in relay, when trying to do the viewer pattern i can't pass values from my viewer resolver to my descendant resolvers.
type Viewer {
   info: UserInfo,
   todos: [Todo]!
}

In this case i would like to pass to todos which user has made the request so i can respond with their todos only.
I was thinking about using context to pass additional values between resolvers, but i'm not really sure how given that i can only return a resolver and an optional error.
If you could guide me a bit with a solution it would be really helpful,
Thanks a lot and thanks for all the work in this package!

When you return a resolver you can have that resolver contain those values, couldn't you?

To be honest i feel dumb for not thinking about that. I've been trying this, it works great so far, thanks @neelance, i'm going to close this then.


Fhir server doesn't support _include:recurse search parameter

Description
Fhir server does not support _include:recurse search parameter.
I have tested with the latest version 2.0.121
GET [base]/Observation?_include:recurse=Observation:related-target
FHIR Version
Stu3
Data provider
CosmosDB
Expected behavior
Should be able retrieve the resources with _include:recurse param
Actual behavior
Returns the following response.
{     "resourceType": "OperationOutcome",     "id": "347458f3-1859-4a11-8a1f-cabdf93d215b",     "issue": [         {             "severity": "error",             "code": "invalid",             "diagnostics": "_include:iterate and _revinclude:iterate are not supported."         }     ] }

This is a known limitation of using _include & _revinclude on Cosmos DB. We don't have the work prioritized but will keep it open for tracking.
https://docs.microsoft.com/en-us/azure/healthcare-apis/fhir/overview-of-search

AB#84437

If this can be prioritized, we'd use it right away.

We're waiting for this too.  🙏 Please priortize it.

It has been almost a year since this was reported. Please fix.

Please fix this as soon as possible.

Is there any update on this functionality please? I am trying to achieve a similar query
https:///Location?_include:recurse=Location:partof&_id=006b7615-7f41-47af-af1d-c4299924f224

@liamwilson-kainos - Are you provisioned on Azure API for FHIR/ using Cosmos DB as a persistence layer? :iterate modifier is supported on Azure Health Data Services/ SQL as a persistence layer. Thanks !

@liamwilson-kainos, the issue will be closed in a week, if no response is received.

This is a known limitation of using _include & _revinclude on Cosmos DB. We don't have the work prioritized but will keep it open for tracking.
https://docs.microsoft.com/en-us/azure/healthcare-apis/fhir/overview-of-search

Has this been resolved?  If so, can you tell use the version, so we know what to update to?

@Xal3ph
:iterate modifier is supported in Azure Health Data Services / SQL persistence layer. We do not support in Azure API for FHIR/ Cosmos persistence layer and do not plan to add.
For SQL persistence layer, this capability has been added while back. You can use latest FHIR application code version.

Closing as :iterate modifier is supported in Azure Health Data Services / SQL persistence layer. We do not support in Azure API for FHIR/ Cosmos persistence layer and do not plan to add.


Moloch v2.0.1 sessions tab loading error (stuck at 'hootin')

ES: 7.4.1:
Moloch version:v2.0.1
Ubuntu 18.04.3 LTS":
DB version: 63 (rpm, deb, easybutton, ...)
Provide logs, stack traces and steps to reproduce:
Moloch is unable to load data in the session tab after deployment (looped around "hootin" with an owl image). Re-produce steps:-
a) changes made in config.ini (see attach)
b) started service viewer and capture (logs attached)
3) interface enabled over the virtual machine which was disabled (ifconfig ens160 up)
4) span traffic configured over virtual switch
capture.log
viewer.log
config.txt
 (Screenshot taken from Firefox Inspector)
 (Screenshot taken from Chrome Inspector)

@Umor-inbox Let me know if this fixes your issue. The problem was that the info field was missing children fields (the info column is a list of a few fields). It looks like something else might be wrong, because the info column should always have children fields. Please reopen this issue or open another issue with more details if something is still broken.


Doc: Update DoEKS website for Ray content

We need to replace Ray on EKS Website doc with JARK and remove the Ray on EKS blueprint.

@alanty Take a look at the issue while updating the blueprint.


Copy-DbaSqlServerAgent fails when copying across a job that's dependent on a new proxy account or operator.

Bug Report
General Troubleshooting steps

[X] Verified running latest release of dbatools?
[X] Verified errors are not related to permissions? (I am running the command from an account which has sysadmin on both the source and destination instances.)
[X] Can duplicate in new/fresh PowerShell.exe session?

Version Information

Operating System (Name|Version): Windows 7
PowerShell Version: 5
SQL Server (Edition|Version): 2016 Standard

Steps to Reproduce
Steps:

Create an operator (Jo) on instance A.
Create a proxy (SSIS Proxy) account on instance A.
Create a job (Job 1) on instance A with a step that uses the new operator.
Create another job (Job 2) which sends a notification to the new proxy account.
Run Copy-DbaSqlServerAgent with server A as the source, and server B as the destination.

Results:

Operator copy successful.
Proxy account copy successful.
Job 1 copy fails due to operator not existing. (WARNING: [Copy-DbaAgentJob][hh:mm:ss] Operator(s) Jo doesn't exist on destination. Skipping job [Job 1])
Job 2 copy fails due to proxy account not existing. (WARNING: [Copy-DbaAgentJob][hh:mm:ss] Proxy Account(s) S doesn't exist on destination. Skipping job [Job 2].)
Checking instance B will confirm that the operator and proxy exist, but the jobs do not.

Running Copy-DbaSqlServerAgent again (without -Force) will result in everything working:

Operator skipped as it already exists.
Proxy account skipped as it already exists.
Job 1 copy successful.
Job 2 copy successsful.

However, running Copy-DbaSqlServerAgent with -Force will get a different result:

Dropping/recreating the operator will be successful.
2)The dropping of the proxy account will fail (WARNING: [Copy-DbaAgentProxyAccount][hh:mm:ss] Issue dropping proxy account | Exception calling "Drop" with "0" argument(s): "D
rop failed for ProxyAccount 'SSIS Proxy'. ")
The copy of the job dependent on the operator will fail again (WARNING: [Copy-DbaAgentJob][hh:mm:ss] Operator(s) Jo doesn't exist on destination. Skipping job [Job 1).
The copy of the job dependent on the proxy account will be successful.

I get the same results from subsequent runs regardless of whether I run it in the same session as the first run, or a separate one.
I'm going to try recreating this again from home and will edit to include logs once I have ones without work instance names included.

[ ] Attach any screenshots (if possible/allowed)
[ ] Attach logs generated by dbatools (Get-DbatoolsLog)
[ ] Attach output from PowerShell console (if possible/allowed)

Additional information
As discussed in the Slack #dbatools channel with @wsmelton and @alevyinroc on 2017-08-29. At the time I thought that Copy-DbaAgentJob was always failing if I passed an SMO rather than a server name, but this may have been my error; I'll try recreating again from home and add further details.

Thanks so much for the detailed report! We'll take a look asap.


Option to fallback to previous API version

Will it be convenient to support fallbacking incoming request to previous API version if new version isn't available ?
For example, there is V1 and V2 versions of API. V2 has some of the V1's routes. Now while making a request, developer has to remember which version has which API. One option to overcome this is to inherit all previous API's in new version, but it involves some duplicate code in routes and controller.
But if we can support optional fallbacking, request will be automatically served from previous API if new one isn't available. I'll be happy to look into it if its feasible.

This feels wrong to me, and I don't want to add this to versionist. If the client is requesting a resource/version that doesn't exist, the client has made an error, and should be notified as such, instead of blindly getting served some other version that may break their response handling.
If it makes sense for your specific use case, I suggest you handle this yourself. Map a catch all not found route at the end of your api_version block for a specific version, and put logic in the controller method you map this to to figure out what to serve back. See: http://stackoverflow.com/questions/21654826/how-to-rescue-page-not-found-404-in-rails
Good luck.


[MRG] DOC: update link to parallel.rst in contributors guide

The current link in the contributors guide for the parallel backend installation instructions points here. Since we don't currently compile the contributors guide via sphinx on the stable branches, the updated link here points toward whichever 'parallel.rst' file is on the master branch.

Not sure what the deal is with the linkcheck. Any ideas @jasmainak?

Codecov Report

Merging #483 (3d1ddf5) into master (bab8196) will decrease coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #483      +/-   ##
==========================================
- Coverage   90.51%   90.42%   -0.09%
==========================================
  Files          18       18
  Lines        3415     3415
==========================================
- Hits         3091     3088       -3
- Misses        324      327       +3

Impacted Files
Coverage Δ

hnn_core/parallel_backends.py
81.49% <0.00%> (-0.83%)
:arrow_down:

Continue to review full report at Codecov.

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

Not sure, it will require some digging. Did google search reveal anything?

It's possible that the newest release of sphinx or sphinx gallery broke something. You could check on Pypi what were released recently and compare that with the time when the error started popping up. Reverting to an older version temporarily might be a solution until the bug is fixed upstream

any update here?

Fixed in #495 and will rebase once that PR has been squashed and merged to avoid making the commit history here unnecessarily lengthy.

sounds good!

I think this is ready to go @ntolley @jasmainak!

Just thinking out loud, alternatively we could also include the contributing guide in our sphinx-build. Something like this:
https://github.com/jonescompneurolab/hnn-core/blob/master/doc/index.rst
but I'll go ahead and merge this for now.

Thanks @rythorpe !

Just thinking out loud, alternatively we could also include the contributing guide in our sphinx-build. Something like this:
https://github.com/jonescompneurolab/hnn-core/blob/master/doc/index.rst
but I'll go ahead and merge this for now.

I like this idea actually because it’d make things more consistent. IDK why I didn’t just do this here. I’ll open a new PR!


fix duplicate Service name in a manifest

Fixes #384

Thanks for your contribution. Could you please sign your commit e.g.
git commit -m "fix duplicate Service name in a manifest" -s

to fulfill the DCO check.

sorry I missed that, now corrected.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 91.999%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4542

Relevant Lines:
4937

💛  - Coveralls


Upgrade to CakePHP 4.5 for UBI8, UBI9 and PHP 7.4+

Resolves #136
Have cleaned up this template for a few different things:

Removed everything.
Put back a fresh CakePHP 4.5
Minimum support raised to PHP 7.4 for current OCP versions (and CakePHP 4.5)
Put back OpenShift template and S2I needed files

The major steps taken can be seen in the separate commits in this PR.
Changes:
I had to add some new stanzas to the DeploymentConfigs on the mysql variants. The new PSA enforcement things were holding it up.
I  got rid of the intrusive alterations to the application views and layouts of the standard new-app generation that CakePHP does. This should make it more familiar to users of vanilla CakePHP, not encourage the incorrect database access pattern in the view and only highlight the material differences for S2I. This is most noticeable in the new default homepage:

(This used to have a lot of OpenShift badging and a little database counter.)
Tested on OCP 4.14.1 with UBI8-7.4, UBI8-8.0 and UBI9-8.0

Holding at CakePHP 4.5 here because it supports 7.4+.
CakePHP 5.x requires PHP 8.1+ (https://book.cakephp.org/5/en/installation.html)

Another change that may be required in the future is a migration off of DeploymentConfig (no removal timeline presently):

/hold
I figured out the issue with UBI9. That PHP isn't honoring/receiving the environment variables from the container runtime. I'll play with that for a minute.
Also, the environment variables used in the same is a little bit complex. I think this is vestigial when we had postgres and mysql variants. Can be simplified for MySQL and I'll do that here.

/hold cancel
I was able to identify the difference (using FPM) and where the behavior change came in:
https://github.com/sclorg/s2i-php-container/blob/ca8d3eba0fd3a924fd2be88c3e7d60d8888fd3c7/8.0/s2i/bin/run#L59-L74
This now works for UBI9 images and is ready for review.

Verified this morning it works with UBI9 and PHP 8.1 also. We get an extra deprecation note (that I'd expect CakePHP 5 addresses, but doesn't cause us issues here):

Another change that may be required in the future is a migration off of DeploymentConfig (no removal timeline presently):

As imagestreams as templates will be migrated soon to Helm Charts so Deployment will be used instead of. Thanks

Everything LGTM. Thanks

I would prefer to merge it and fix later on issues separately.


handle helmrelease may uninstall chart that is pending-install or pending-upgrade

What happened:
Charts may be uninstalled probabilistically when installing or upgrading.
What you expected to happen:
Charts can not be uninstalled probabilistically when installing or upgrading.
How to reproduce it (as minimally and precisely as possible):
This event is sporadic, but when viewing the source code, the guess may be related to this part of the code https://github.com/clusternet/clusternet/blob/main/pkg/utils/deployer.go#L193. When one of helmreleases that rendered by description install or upgrade failed, both description-controller and helmrelrease-controller will re-execute the handle helmrelease logic. The code just mentioned will mistakenly delete the chart being executed.
When installing helmrelease by clusternet-hub, the above errors will cause helmrelease to generate the following events：
an error occurred while uninstalling the release. original install error: services "service-xxx" not found: uninstall: Release not loaded: chart-xxx: release: not found
Anything else we need to know?:
The above is my analysis, I hope you can see if it is correct.
Environment:

Clusternet version:

Clusternet-agent version (user clusternet-agent --version=json): image version v0.13.1
Clusternet-hub version (user clusternet-hub --version=json): iamge version v0.13.1

Kubernetes version (use kubectl version): client: v1.18.4-tke.1; server: v1.20.6-tke.20
Cloud provider or hardware configuration:
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Others:

@wl-chen Would you share some detailed information on the issue? Thanks.

@wl-chen Would you share some detailed information on the issue? Thanks.

Sorry, I slipped and didn't finish writing and sent it.

This event is sporadic, but when viewing the source code, the guess may be related to this part of the code https://github.com/clusternet/clusternet/blob/main/pkg/utils/deployer.go#L193. When one of helmreleases that rendered by description install or upgrade failed, both description-controller and helmrelrease-controller will re-execute the handle helmrelease logic. The code just mentioned will mistakenly delete the chart being executed.

Yeah, the helm releases will be re-enqueued and handled by handleHelmRelease in the next round.
https://github.com/clusternet/clusternet/blob/main/pkg/utils/deployer.go#L193 will only uninstall failed releases when atomic is explicitly set to true. I don't know whether setting atomic to false (which is false by default) will help mitigate this problem.

When installing helmrelease by clusternet-hub, the above errors will cause helmrelease to generate the following events：
an error occurred while uninstalling the release. original install error: services "service-xxx" not found: uninstall: Release not loaded: chart-xxx: release: not found

I wonder whether ignoring such not found helm release in function UninstallRelease will help solve the problem.
@wl-chen Please feel free to submit a PR if you've got a solution. Thanks.
cc @DanielXLee for this part of uninstalling logics.

This event is sporadic, but when viewing the source code, the guess may be related to this part of the code https://github.com/clusternet/clusternet/blob/main/pkg/utils/deployer.go#L193. When one of helmreleases that rendered by description install or upgrade failed, both description-controller and helmrelrease-controller will re-execute the handle helmrelease logic. The code just mentioned will mistakenly delete the chart being executed.

Yeah, the helm releases will be re-enqueued and handled by handleHelmRelease in the next round.
https://github.com/clusternet/clusternet/blob/main/pkg/utils/deployer.go#L193 will only uninstall failed releases when atomic is explicitly set to true. I don't know whether setting atomic to false (which is false by default) will help mitigate this problem.

When installing helmrelease by clusternet-hub, the above errors will cause helmrelease to generate the following events：
an error occurred while uninstalling the release. original install error: services "service-xxx" not found: uninstall: Release not loaded: chart-xxx: release: not found

I wonder whether ignoring such not found helm release in function UninstallRelease will help solve the problem.
@wl-chen Please feel free to submit a PR if you've got a solution. Thanks.
cc @DanielXLee for this part of uninstalling logics.

You mean handleHelmRelease will only be executed by helmrelease-controller in the next round ? Will the code https://github.com/clusternet/clusternet/blob/main/pkg/hub/deployer/helm/helm.go#L355 be optimized ?

You mean handleHelmRelease will only be executed by helmrelease-controller in the next round ?

handleHelmRelease will be executed by deployer in clusternet-agent / clusternet-hub. This depends on the cluster sync mode.

Will the code https://github.com/clusternet/clusternet/blob/main/pkg/hub/deployer/helm/helm.go#L355 be optimized ?

@wl-chen Feel free to make your changes if necessary. You'd better not introduce breaking changes.

@wl-chen you can try to fix it and then verify in our test env. If works well, push your fix to the community.

@wl-chen Would you please share some updates on this issue? Thanks.


doc: networking: qemu_setup: Update details and add DNS information

Majority of "accessing Internet" setup is the same for both QEMU and
real boards connected to host, mention that explicitly. Be more
precise that networking settings require net_app_settings API, not
entire net_app. Finally, add information about DNS setup for the
samples requiring it.
Signed-off-by: Paul Sokolovsky<EMAIL_ADDRESS>

Codecov Report

Merging #7599 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #7599      +/-   ##
==========================================
- Coverage   55.25%   55.25%   -0.01%
==========================================
  Files         468      468
  Lines       51673    51673
  Branches     9895     9895
==========================================
- Hits        28553    28552       -1
- Misses      19207    19208       +1
  Partials     3913     3913

Impacted Files
Coverage Δ

lib/posix/pthread.c
69.34% <0%> (-0.51%)
:arrow_down:

Continue to review full report at Codecov.

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

Addressed @dbkinder's comments.


SimpleLogin MX2 is down

When using the aliases, I received the following "Undelivered error" which reports mx2.simplelogin.co being down. As there is no logging of this in the status page, I am reporting it.
This is the mail system at host [w1.tutanota.de](http://w1.tutanota.de/).

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.a

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

The mail system

<[******@slmail.me](mailto:********@slmail.me)>: lost connection with
[mx2.simplelogin.co](http://mx2.simplelogin.co/)[<IP_ADDRESS>] while receiving the initial server
greeting

Hi we had an issue yesterday which is solved now. Do you still see this error?

Yes, it's solved now, sorry for not updating it. Thanks.


I'd like to join this project's community

Your public repo
https://github.com/michelezanini/gov4git-identity-public.git
Your public branch
main

Approved.

 Follow up
On Sunday, 10-Mar-24 22:21:42 UTC by Gov4Git dev
@michelezanini was added to the community.


ListView don't have a default source to use with the AllViewsTester.cs.

Adding a Text property may be resolve it.

I was planning on expanding AllviewsTester to have refelction-based code to check for a Source property just as it does for Text.
Actually, I thought I wrote that code at one point; not sure where it went. Weird.
Anyway, with PR #702 ListView will get a Text property for free. Not sure what it should do though.

It will appear Test Text only. You don't need to merge that as soon your PR is accepted. I only having some problems with the unit tests. It's only for you to see my idea.

This is the code:
View CreateClass (Type type)
{
	// Instantiate view
	var view = (View)Activator.CreateInstance (type);

	//_curView.X = Pos.Center ();
	//_curView.Y = Pos.Center ();
	//_curView.Width = Dim.Fill (5);
	//_curView.Height = Dim.Fill (5);

	// Set the colorscheme to make it stand out
	view.ColorScheme = Colors.Base;

	// If the view supports a Text property, set it so we have something to look at
	if (view.GetType ().GetProperty ("Text") != null) {
		try {
			view.GetType ().GetProperty ("Text")?.GetSetMethod ()?.Invoke (view, new [] { ustring.Make ("Test Text") });
		} catch (TargetInvocationException e) {
			MessageBox.ErrorQuery ("Exception", e.InnerException.Message, "Ok");
			view = null;
		}
	}

	// If the view supports a Title property, set it so we have something to look at
	if (view != null && view.GetType ().GetProperty ("Title") != null) {
		view?.GetType ().GetProperty ("Title")?.GetSetMethod ()?.Invoke (view, new [] { ustring.Make ("Test Title") });
	}

	// If the view supports a Source property, set it so we have something to look at
	if (view != null && view.GetType ().GetProperty ("Source") != null) {
		var source = new ListWrapper (new List<ustring> () { ustring.Make ("List Item #1"), ustring.Make ("List Item #2"), ustring.Make ("List Item #3")});
		view?.GetType ().GetProperty ("Source")?.GetSetMethod ()?.Invoke (view, new [] { source });
	}

	// Set Settings
	_computedCheckBox.Checked = view.LayoutStyle == LayoutStyle.Computed;

	// Add
	_hostPane.Add (view);
	//DimPosChanged ();
	_hostPane.LayoutSubviews ();
	_hostPane.Clear ();
	_hostPane.SetNeedsDisplay ();
	UpdateSettings (view);
	UpdateTitle (view);
	return view;
}


Failed to authenticate SSH session

Perhaps related to #13 ?, I have an error on try-merge:
Failed to authenticate SSH session: Unable to open public key file; class=Ssh (23)

git and ssh are working fine, peculiarities are:

non standard ssh port
ed25519 key

Sorry for the late reply! I got the notifications turned off for some reason. Unfortunately I think this will be hard to reproduce on my own, can you check one of these solutions?

It seems I did not put the code to handle passphrase. If you have a passphrase locking your ssh key, this might be the issue. In that case I think it's best that you use ssh-agent because it will unlock the key before adding it to the running agent (I believe).

The code that handles the credentials is here: https://github.com/cecton/git-tools/blob/72937393b65631cfe97e3b4cd13f6498f60b6dac/src/common.rs#L388-L426
Perhaps you can you check if this looks good to you?

I remember I had quite some issues getting this to work properly. Using git2_credentials was not enough.
I suspect this could be the offending code:
username_from_url.unwrap_or_else(|| user.to_str().unwrap()),

If you force it to user instead, does it work better?

Hi, thanks, no problem at all!

the gnome keyring should act as an agent, or at least git works without asking. I'll double check if I still have the same error in a shell I'm sure can see the agent.
I'll have a look there with some dbg!().
Can be, my local username is not the remote user, or at least, not on all the servers, maybe dbg!() will help here too.

I hope to remember to have a look at this in the next few days, if not, feel free to close the issue!


Hovering 3D points in 2D view should communicate correct depth to ray display in 3D corresponding view

Note that the displayed ray is marked bold/white all the way to the image plane when we're clearly hovering/selecting a point that is much closer to the camera!

Duplicate of #1818


Enquiry about status of this project

Not an issue but a question ― is this now practically speaking an abandoned project, or is it just perfect enough so that no further development has been necessary since 2016 within the implemented feature set? I wonder what folks here think...
Would you otherwise recommend any specific Java library for the time being, along the lines of Scala's Figaro? I think https://github.com/amidst/toolbox looks nice in terms of its accounting for concurrency, but it looks kind of newish too.

This project is actively being developed. However, the project repository is at bitbucket (https://bitbucket.org/probprog/anglican) and we synchronize this repository occasionally for visibility. I need it to set up a script to keep these repositories in sync but didn't get around to do this until now. Will do.

Oh, thanks!! and glad I asked as I'd not ever guess that!
On Mon, Sep 25, 2017 at 6:55 PM, David Tolpin<EMAIL_ADDRESS>wrote:

This project is actively being developed. However, the project repository
is at bitbucket (https://bitbucket.org/probprog/anglican) and we
synchronize this repository occasionally for visibility. I need it to set
up a script to keep these repositories in sync but didn't get around to do
this until now. Will do.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/probprog/anglican/issues/3#issuecomment-331926875,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEw74-HsN4LXtYFrzCsEsP0x-ctHCdcQks5sl80JgaJpZM4Pe_Ui
.

It would actually be nice if the git repo said something about this, since git is so standard these days. Does the github repository ever get pulled back into the bitbucket one?

why don't you ask the committers. i too would love to see a new release


Made it clear that fb is needed for the scheme

I didn't understand these two points when I tried setting up facebook login, so I figured that explaining it in the Readme might prevent other people from having the same problems.

Pull Request Test Coverage Report for Build 76

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 88.732%

Totals

Change from base Build 66:
0.0%

Covered Lines:
63

Relevant Lines:
71

💛  - Coveralls


ghm as an alias

gh-manager is bit long for a terminal command and I believe a command such as ghm or similar short alias would be nice to have. To have the backward capability, we still could have gh-manager as the main command. Open for discussions.
@charithsoori  @rajikaimal

Can I pick this up?

I agree with you @rehrumesh  . @BrainMaestro  Please go ahead .


feat/add ps rule baseline

add validation baseline for MI only, for hero services

@hund030 Would you be able to complete this to print the output in the issue?
It should only print the recommendation.


Undefined variable $template_engine

I followed the installation instructions for composer.
Your examples use $template_engine, like:
    $template_engine->render('comment', $row);
I get this error:

Warning: Undefined variable $template_engine in /home/xyz/easydb/test.php on line 25 Fatal error: Uncaught Error: Call to a member function render() on null in

I've search the whole source code and I'm not able to find a reference to $template_engine. What am I missing?

This appears to be an error in /home/xyz/easydb/test.php on line 25 rather than anything within EasyDB

It might be better to replace $template_engine with var_dump(), as you can't expect everyone to know what that means.


Update scipy/__config__.py to contain useful information

Describe your issue.
Just as the title suggests, on Windows when the username contains a single quote, importing the scipy package would cause an error.
Reproducing Code Example
python -c "import scipy"

Error message
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "C:\Users\Praxelogist's Lab\.conda\envs\losthub\lib\site-packages\scipy\__init__.py", line 134, in <module>
    from scipy.__config__ import show as show_config
  File "C:\Users\Praxelogist's Lab\.conda\envs\losthub\lib\site-packages\scipy\__config__.py", line 27
    lapack_info={'libraries': ['lapack', 'blas', 'lapack', 'blas'], 'library_dirs': ['C:/Users/Praxelogist's Lab/.conda/envs/losthub\\Library\\lib'], 'language': 'f77'}
                                                                                ^
SyntaxError: invalid syntax

SciPy/NumPy/Python version information
numpy==1.23.1  python==3.9.13  scipy==1.9.0

The reason behind the error is that in the __config__.py file, the file paths specified by the four dictionaries blas_info, blas_opt_info, lapack_info, and lapack_opt_info are hard-coded. Since the file path is represented as a string enclosed in single quotes, and the string itself contains a Windows username that also contains a single quote, it's unavoidable that the string would be broken, resulting in a syntax error, e.g.
lapack_info={'libraries': ['lapack', 'blas', 'lapack', 'blas'], 'library_dirs': ['C:/Users/Praxelogist's Lab/.conda/envs/losthub\\Library\\lib'], 'language': 'f77'}
blas_info={'libraries': ['cblas', 'blas', 'cblas', 'blas', 'cblas', 'blas'], 'library_dirs': ['C:/Users/Praxelogist's Lab/.conda/envs/losthub\\Library\\lib'], 'include_dirs': ['C:/Users/Praxelogist's Lab/.conda/envs/losthub\\Library\\include'], 'language': 'f77', 'define_macros': [('HAVE_CBLAS', None)]}
blas_opt_info={'define_macros': [('NO_ATLAS_INFO', 1), ('HAVE_CBLAS', None)], 'libraries': ['cblas', 'blas', 'cblas', 'blas', 'cblas', 'blas'], 'library_dirs': ['C:/Users/Praxelogist's Lab/.conda/envs/losthub\\Library\\lib'], 'include_dirs': ['C:/Users/Praxelogist's Lab/.conda/envs/losthub\\Library\\include'], 'language': 'f77'}
lapack_opt_info={'libraries': ['lapack', 'blas', 'lapack', 'blas', 'cblas', 'blas', 'cblas', 'blas', 'cblas', 'blas'], 'library_dirs': ['C:/Users/Praxelogist's Lab/.conda/envs/losthub\\Library\\lib'], 'language': 'f77', 'define_macros': [('NO_ATLAS_INFO', 1), ('HAVE_CBLAS', None)], 'include_dirs': ['C:/Users/Praxelogist's Lab/.conda/envs/losthub\\Library\\include']}

So, scipy/__config__.py is just a copy of the numpy/__config__.py from the numpy installation that was used during the building of scipy, so the core error is over there. AFAICT, the line responsible for generating this should use correctly-escaped strings:
https://github.com/numpy/numpy/blob/v1.23.1/numpy/distutils/misc_util.py#L2356
Given that the backslashes in that path are correctly escaped while the problematic part uses foreward slashes, I expect that the conda post-installation process is doing a regex search-and-replace to "rehome" the configuration to wherever the root of your conda installation is. So the error is in the conda packages' post-installation scripts, not numpy or scipy.

The full implementation in tools/config_utils.py right now is:
import sys
from pathlib import Path
import numpy as np
outfile = Path(sys.argv[1])

# This piece of code will just just copy the Numpy's `__config__.py` file,
# rather than write out SciPy's build-time config settings. This file should be
# generated by `config.make_config_py()` in `scipy/setup.py` which relies on an
# instance of `numpy.distutils.Configuration`. It cannot be accessed directly
# with a Meson build. This is a workaround for the same.
# For more details the implementation of this method is at https://github.com/numpy/numpy/blob/main/numpy/distutils/misc_util.py#L2113

outfile.write_text(Path(str(np.__config__.__file__)).read_text())

So let's repurpose this issue to a task to get rid of that and instead create a more useful __config__.py; what is there right now does not make much sense (and I think never has).

I'm think that we store the output of the configure stage of the build in __config__.py, minus the known Cython-related warnings (WARNING: custom_target '_cython_tree' has more than one output! ). That would look like:
Build started at 2022-10-17T18:06:33.672633
Main binary: /home/rgommers/mambaforge/envs/scipy-dev/bin/python3.10
Build Options: -Dprefix=/home/rgommers/code/scipy/build-install
Python system: Linux
The Meson build system
Version: 0.63.99
Source dir: /home/rgommers/code/scipy
Build dir: /home/rgommers/code/scipy/build
Build type: native build
Project name: SciPy
Project version: 1.10.0.dev0
C compiler for the host machine: /home/rgommers/mambaforge/envs/scipy-dev/bin/x86_64-conda-linux-gnu-cc (gcc 10.4.0 "x86_64-conda-linux-gnu-cc (conda-forge gcc 10.4.0-16) 10.4.0")
C linker for the host machine: /home/rgommers/mambaforge/envs/scipy-dev/bin/x86_64-conda-linux-gnu-cc ld.bfd 2.36.1
C++ compiler for the host machine: /home/rgommers/mambaforge/envs/scipy-dev/bin/x86_64-conda-linux-gnu-c++ (gcc 10.4.0 "x86_64-conda-linux-gnu-c++ (conda-forge gcc 10.4.0-16) 10.4.0")
C++ linker for the host machine: /home/rgommers/mambaforge/envs/scipy-dev/bin/x86_64-conda-linux-gnu-c++ ld.bfd 2.36.1
Host machine cpu family: x86_64
Host machine cpu: x86_64
Compiler for C supports arguments -Wno-unused-but-set-variable: YES
Compiler for C supports arguments -Wno-unused-function: YES
Compiler for C supports arguments -Wno-conversion: YES
Compiler for C supports arguments -Wno-misleading-indentation: YES
Compiler for C supports arguments -Wno-incompatible-pointer-types: YES
Library m found: YES
Fortran compiler for the host machine: /home/rgommers/mambaforge/envs/scipy-dev/bin/x86_64-conda-linux-gnu-gfortran (gcc 10.4.0 "GNU Fortran (conda-forge gcc 10.4.0-16) 10.4.0")
Fortran linker for the host machine: /home/rgommers/mambaforge/envs/scipy-dev/bin/x86_64-conda-linux-gnu-gfortran ld.bfd 2.36.1
Compiler for Fortran supports arguments -Wno-conversion: YES
Checking if "-Wl,--version-script" : links: YES
Program cython found: YES (/home/rgommers/mambaforge/envs/scipy-dev/bin/cython)
Program pythran found: YES (/home/rgommers/mambaforge/envs/scipy-dev/bin/pythran)
Program cp found: YES (/usr/bin/cp)
Program python3 found: YES (/home/rgommers/mambaforge/envs/scipy-dev/bin/python3.10)
Found pkg-config: /home/rgommers/mambaforge/envs/scipy-dev/bin/pkg-config (0.29.2)
Run-time dependency threads found: YES
Library npymath found: YES
Library npyrandom found: YES
Run-time dependency openblas found: YES 0.3.21
Dependency openblas found: YES 0.3.21 (cached)
Program _build_utils/cythoner.py found: YES (/home/rgommers/mambaforge/envs/scipy-dev/bin/python3.10 /home/rgommers/code/scipy/scipy/_build_utils/cythoner.py)
Compiler for C supports arguments -Wno-maybe-uninitialized: YES
Compiler for C supports arguments -Wno-discarded-qualifiers: YES
Compiler for C supports arguments -Wno-empty-body: YES
Compiler for C supports arguments -Wno-implicit-function-declaration: YES
Compiler for C supports arguments -Wno-parentheses: YES
Compiler for C supports arguments -Wno-switch: YES
Compiler for C supports arguments -Wno-unused-label: YES
Compiler for C supports arguments -Wno-unused-variable: YES
Compiler for C++ supports arguments -Wno-cpp: YES
Compiler for C++ supports arguments -Wno-deprecated-declarations: YES
Compiler for C++ supports arguments -Wno-class-memaccess: YES
Compiler for C++ supports arguments -Wno-format-truncation: YES
Compiler for C++ supports arguments -Wno-non-virtual-dtor: YES
Compiler for C++ supports arguments -Wno-sign-compare: YES
Compiler for C++ supports arguments -Wno-switch: YES
Compiler for C++ supports arguments -Wno-terminate: YES
Compiler for C++ supports arguments -Wno-unused-but-set-variable: YES
Compiler for C++ supports arguments -Wno-unused-function: YES
Compiler for C++ supports arguments -Wno-unused-local-typedefs: YES
Compiler for C++ supports arguments -Wno-unused-variable: YES
Compiler for C++ supports arguments -Wno-int-in-bool-context: YES
Compiler for Fortran supports arguments -Wno-argument-mismatch: YES
Compiler for Fortran supports arguments -Wno-conversion: YES (cached)
Compiler for Fortran supports arguments -Wno-intrinsic-shadow: YES
Compiler for Fortran supports arguments -Wno-maybe-uninitialized: YES
Compiler for Fortran supports arguments -Wno-surprising: YES
Compiler for Fortran supports arguments -Wno-uninitialized: YES
Compiler for Fortran supports arguments -Wno-unused-dummy-argument: YES
Compiler for Fortran supports arguments -Wno-unused-label: YES
Compiler for Fortran supports arguments -Wno-unused-variable: YES
Compiler for Fortran supports arguments -Wno-tabs: YES
Compiler for Fortran supports arguments -Wno-argument-mismatch: YES (cached)
Compiler for Fortran supports arguments -Wno-conversion: YES (cached)
Compiler for Fortran supports arguments -Wno-maybe-uninitialized: YES (cached)
Compiler for Fortran supports arguments -Wno-unused-dummy-argument: YES (cached)
Compiler for Fortran supports arguments -Wno-unused-label: YES (cached)
Compiler for Fortran supports arguments -Wno-unused-variable: YES (cached)
Compiler for Fortran supports arguments -Wno-tabs: YES (cached)
Checking for function "open_memstream" : NO
Configuring messagestream_config.h using configuration
Compiler for Fortran supports arguments -w: YES
Checking for size of "void*" : 8
Compiler for C supports arguments -Wno-unused-variable: YES (cached)
Compiler for C supports arguments -Wno-parentheses: YES (cached)
Compiler for C supports arguments -Wno-unused-label: YES (cached)
Compiler for C supports arguments -Wno-implicit-function-declaration: YES (cached)
Compiler for C supports arguments -Wno-switch: YES (cached)
Compiler for Fortran supports arguments -w: YES (cached)
Checking for size of "void*" : 8
Build targets in project: 206

SciPy 1.10.0.dev0

  User defined options
    prefix: /home/rgommers/code/scipy/build-install

Found ninja-1.11.0 at /home/rgommers/mambaforge/envs/scipy-dev/bin/ninja
Meson build setup OK

And that's a thing that scipy.show_config() can show. This will be helpful when interacting with folks who file build/install issues. It shows a number of things that we usually need to know and have a hard time getting info on:

Any user-specified options in the install command
Compilers used
Which build dependencies were found, and what versions of them
How Python was installed (typically obvious from the install location)
OS and CPU type

One little complication is that that info that is printed to the terminal is not readily available in a separate log file The build/meson-logs/meson-log.txt file has more content that we don't necessarily want to store (too large and verbose). So the file needs parsing before storing this. Or am I missing an easier way @eli-schwartz?
The way to get at this content during the build is probably to move the generate_config custom target to the bottom of scipy/meson.build and invoke an updated Python script that does the parsing.

You can get the compilers with:
comp.get_id()
comp.get_linker_id()
comp.version()
comp.cmd_array()

You can get the OS and CPU type with:
host_machine.cpu()
host_machine.cpu_family()

For build dependencies, you can push them to an array when looking them up, then iterate over them and check:
dep.name()
dep.found()
dep.version()

For the found version of Python, I think the primary useful information shown in the debug log is the path, anyway, right? So,
py_installation.path()

By the way, you can also use
py_installation.get_path('xxx')
py_installation.get_variable('xxx')

to get arbitrary sysconfig paths and config_vars, respectively, from that found python installation.
The one thing missing here is user-specified Build Options: xxx. By coincidence, someone else has proposed the same feature at https://github.com/mesonbuild/meson/issues/10898 and there's a linked PR to implement it as well.

The generally official approach would then be to collect all this information using the meson methods I listed, stuff them all into a dict, and use that via configure_file().

That does sound like a much nicer way of doing things than parsing a text log, thanks @eli-schwartz.
@h-vetinari WDYT?

@h-vetinari WDYT?

Sounds exactly what I had been hoping for 🤩

This is now in progress for NumPy: https://github.com/numpy/numpy/pull/22769. So probably best to finish it there, and then sync whatever comes out to SciPy.

The NumPy PR is now merged @h-vetinari

Shall I do the same for SciPy?

Shall I do the same for SciPy?

I was planning to do it, but don't let that stop you. ;)

This is addressed by gh-17862. Thanks all!


Identity vs IdentityServer

What makes the page, and many pages on this Authentication subject really difficult to understand (for a newcomer) is the terms 'Identity' ' Microsoft Identity' and 'IdentityServer'.  These three seemingly similar terms refer to three profoundly different things. It is taken me a week of heavy reading to grasp all this for the first time. A new paged just describing these terms, what they are, their relationship would be very helpful. They are just used everwhere without first establishing their complete meaning

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

ID: 21cb7455-3305-9316-5440-bdc22947a82d
Version Independent ID: 137d4b94-7b26-3911-b22d-42c754a95fc1
Content: Introduction to authentication for Single Page Apps on ASP.NET Core
Content Source: aspnetcore/security/authentication/identity-api-authorization.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @javiercn
Microsoft Alias: scaddie

See this SO answer to your question. That info should probably be in https://docs.microsoft.com/en-us/aspnet/core/security/authentication/identity

MOVED to #13697


fix con not get the correct status of the old subscription object

What type of PR is this?
What this PR does / why we need it:
fix con not get the correct status of the old subscription object
Which issue(s) this PR fixes:

Fixes #549
Special notes for your reviewer:

Codecov Report

Merging #550 (d8f7788) into main (4e6daef) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #550   +/-   ##
=======================================
  Coverage   13.52%   13.52%
=======================================
  Files          66       66
  Lines        7477     7477
=======================================
  Hits         1011     1011
  Misses       6386     6386
  Partials       80       80

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Add createMap option

This PR adds a new option, createMap, for cases where different backing storage for the cache is desired, such as https://github.com/mafintosh/turbo-hash-map when cache keys are buffers.

@mafintosh This is awaiting review.


Improve step 6

That's not a bad idea! Step 7 could be maybe turned into this, because I don't see a useful case for reranking in the current workshop. I'll submit an issue

@jmartisk reranking can still be demonstrated if we add more policies/documentation

@langchain4j my understanding is that reranking is generally useful for hybrid queries from different sources (which have mutually incomparable scoring strategies), but if you just use a single embedding store, then scores from a good embedding model should usually be enough for ranking the search results, no? Or at least I find it hard to explain why you should use a scoring model after you have already scored the results by computing the vector distance.

@jmartisk, reranking is still benefitial even if you have a single source/store.
The idea is to optimize retrieval by having 2-stages:

on the first stage a faster/cheaper (but worse) model is used to retrieve (let's say 1000) most relevant documents (from let's say 1.000.000)
on the second stage a slower/expensiver (but much better) model is used to filter retrieved documents even further (let's say down to 20)

Reranking/scoring models have a different (as compared to embedding models) network architecture/structure, so they can perform better (but much slower).


Fix SSL host name

Fixes #433 (CLIENTS-753) and #434 (CLIENTS-765)
Depends on basho/riak-client-tools#4

Now that I tweaked my environment, life it good

:+1: 550a2d1

@borshop merge


No "email" icon?

Am I blind or is there really no icon for emails?

How about the envelope-closed or envelope-open options?

Phew. Sorry I missed that. Thanks!


Use ArrayVec in SerializedSignature

See #2247

I think this won't be possible without an API change. ArrayVec doesn't implement Copy, so SerializedSignature wouldn't be able to implement it either. Is that worth it?

We recently added a simple version of ArrayVec that implements Copy in internals/src/array_vec.rs, perhaps that works?

Oh i missed that. Should I use the internal Copy version in #2310 instead of the external crate?

@conduition yes, please!


Fixed issue: C++ easy task

Wrote a program for converting temperature in Celsius to Fahrenheit that executes sucessfully

Wrote a program for converting temperature in Celsius to Fahrenheit that executes sucessfully

Looks good, well done!

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects. Just click here to find more. These projects contain real issues that you can help resolve. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


Text rotation no more working properly

Bevy version
acbed6040eeae99199657e44a9668772738ac344
What you did
I was looking at issue #15853, and found out that this is the rotation of the text that make it disappear.
I wrote the following example, that rotate a text, that showcase the bug:
use bevy::prelude::*;

fn main() {
    App::new()
        .add_plugins(DefaultPlugins)
        .add_systems(Startup, setup)
        .add_systems(Update, text_rotation_system)
        .run();
}

fn setup(mut commands: Commands, asset_server: Res<AssetServer>) {
    commands.spawn(Camera2d);
    commands.spawn((
        Text::new("abcdefghijklmnopqrstuvwxyz"),
        TextFont {
            font: asset_server.load("fonts/FiraSans-Bold.ttf"),
            font_size: 40.0,
            ..default()
        },
        TextLayout::new_with_justify(JustifyText::Center),
        Style {
            align_self: AlignSelf::Center,
            justify_self: JustifySelf::Center,
            ..default()
        },
    ));
}

fn text_rotation_system(time: Res<Time>, mut query: Query<&mut Transform, With<Text>>) {
    for mut transform in &mut query {
        let seconds = time.elapsed_seconds();
        transform.rotation = Quat::from_rotation_z(seconds / 2.0);
    }
}

What went wrong
At some small rotation some letters disappear then the whole text disappear. See video:
https://github.com/user-attachments/assets/c941e152-8cca-4dfc-ba84-a995f00f1ff2
Additional information
Fixing this issue should also fix #15863 directly.

Further testing shows that this issue IS NOT introduced by the move to required components.
The issue is already present the commit just before the Text Rework merge. Namely commit 0b2e0cfacab693e0ddbc1461fbf2190d373197af already has the issue ( need to adapt the provided code).

I have been able to bisect the problem and the first bad commit is 675f8ad40380966e3cc9176e95965538df621810
The updated example I used is
use bevy::prelude::*;

fn main() {
    App::new()
        .add_plugins(DefaultPlugins)
        .add_systems(Startup, setup)
        .add_systems(Update, text_rotation_system)
        .run();
}

fn setup(mut commands: Commands, asset_server: Res<AssetServer>) {
    commands.spawn(Camera2dBundle::default());
    commands.spawn((TextBundle::from_section(
        "abcdefghijklmnopqrstuvwxyz",
        TextStyle {
            font: asset_server.load("fonts/FiraSans-Bold.ttf"),
            font_size: 40.0,
            ..default()
        },
    )
    .with_style(Style {
        align_self: AlignSelf::Center,
        justify_self: JustifySelf::Center,
        ..default()
    }),));
}

fn text_rotation_system(time: Res<Time>, mut query: Query<&mut Transform, With<Text>>) {
    for mut transform in &mut query {
        let seconds = time.elapsed_seconds();
        transform.rotation = Quat::from_rotation_z(seconds / 2.0);
    }
}


variantToNotify possibility to inform only beta users

It would be great to have different notify settings for different built types.

It would definitely be a nice addition, I would love to see that in the next release!


Rename "operators" to "filters" in "Search operators" reference.

Changes all the uses of the word "operators" to "filters" in the in-app "Search operators" reference to align with the updated help center documentation.
Fixes #23767.
Screenshots and screen captures:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability

Communicate decisions, questions, and potential concerns.

[x] Automated tests.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Links.

@alya This PR is ready for your review.

The screenshots look good to me!
@timabbott I think you can review this one directly?

Looks good to me, marked to merge once CI passes.


Add training lab

Description
Add a containerlab-based lab for the inmanta training.

This training lab only works for a few kernel versions (not sure which), latest ubuntu 20.04 seems fine.  We probably need to find another solution that this then.


async/ thread environment issues

on the line [thread handle [receiver_lambda] the thread is given the environment present at the line. This is by design as we want to capture my_channel, however, this means it also has access to idx and anything following that can lead to some weird issues. See about modifying thread and async creation to explicitly take an optional channel and then have a brand new environment created.
[use "os"]

[chan my_channel]

[var receiver_lambda [lambda [] [block
    [var counter 0]
    [loop [< counter 30] [set counter [+ counter 1]] [block
        [if [my_channel.has_data] [block
            [var data [my_channel.get]]
            [putln "Got: " data]
        ]]
        [os.sleep_ms 1000]
    ]]
    [putln "broke"]
]]]

[thread handle [receiver_lambda]]
[var idx 0]
[loop [< idx 10] [set idx [+ idx 1]] [block
    [os.sleep_ms 5000]
    [my_channel.put idx]
    [if [== idx 5] [break]]
]]

[putln "Join"]
[handle.join]

The goof noticed was that in the chan put_fn we pushed the cell directly, and then processed it when get_fn was called. This allowed the variables to update out of sync. Instead, we now process on put_fn and just retrieve what was processed on get_fn. The accessing data in the outer environment is by design and will not change.
https://github.com/bosley/sauros/pull/82