The navbar and footer of FAQ page aren't consistent with that of Homepage

What happened?
The navbar and footer CSS is distorted on FAQ page, also the hover functionality, font-weight, size are not consistent with that of the Homepage.
Homepage Navbar Footer : -

FAQ Navbar :-

How can we reproduce this bug?
No reproduction needed..... It's component consistency issue
Desktop Information (Optional)
No response
Urgency (Optional)
Medium priority

Kindly assign me this issue under Gssoc 2022 contribution

Assigned u @GaganpreetKaurKalsi


mavlink: 2020.10.11-1 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository mavlink to 2020.10.11-1:

upstream repository: https://github.com/mavlink/mavlink.git
release repository: https://github.com/mavlink/mavlink-gbp-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.9.8
previous version for package: 2020.9.10-1

Holding for the pending Kinetic sync


disable serving-cert-secret-name annotation when cert-manager enabled

When using Helm to deploy the operator with enableCertManager=true, the service.alpha.openshift.io/serving-cert-secret-name: patch-operator-certs annotation on the controller-manager-metrics-service svc causes the cert-manager operator to contend with built-in platform certificate issuing operations.
I'm reasonably certain that only one of the two techniques for issuing certificates should be enabled at any given time. If that assumption is correct, then the change in this PR only adds the serving-cert-secret-name annotation if cert-manager is not enabled. In my testing, this resolves the contention.

@davgordo Is there a reason why you closed this PR? I'm currently stuck at the same problem and came to the same conclusion: service-ca should be disabled when using cert-manager.


Fix float overflow on utf8 parsing

I couldn't see a way to print the raw value of the Float80 to string—which raised a feature enhancement idea: supporting scientific notation.

Hi @ryanbooker, sorry for not following up sooner and thanks for PRing!
Would you mind walking me through this change a bit more? I checked out your branch and commented out the n <= .greatestFiniteMagnitude checks and the tests you added still seem to pass, so I'm just a bit puzzled as to what this PR changes 😅

Hi @stephencelis. Thanks for the reply. No worries at all. I neglected to mention this is related to issue: https://github.com/pointfreeco/swift-parsing/issues/26
It's only a problem in the Xcode 12.5 beta. Hopefully it will be fixed by release… it seems like an Apple regression.

Hi @stephencelis, I just received an update from Apple. This is new intended behaviour.
When parsing strings containing number values too large for the type, Float etc, now return inf rather than nil, so some version of this change will definitely be needed when Xcode 12.5 is released.

@ryanbooker After thinking about this some more, we decided that it's probably best to embrace Apple's defaults here, even as they change, so we're going to keep things as they are.
We think that if you want to fail on infinity there are a couple options:

Inspect the parser's output and fail if it's infinity
Copy and paste the float parsers you use and modify the behavior in the project (if you want things to more immediately fail)

Thanks for bringing this to our attention, though!

No worries. My fear was a general one really. Relying on the old behaviour means everyone's code is now going to compile, but probably crash at run time. Apple did say they will update the release notes to actual mention this. :)


calendarCurrentPageDidChange not showing correct Date

Hi all,
I've been messing with the calendar and have come across an issue in calendarCurrentPageDidChange not showing the correct Date. Here is an example. Today is 30th March 2016. so it shows March 2016 on launch. I am printing the calendar.currentPage variable here:
calendarCurrentPageDidChange: 2016-02-01 00:00:00 +0000 <-scroll to Feb from March
calendarCurrentPageDidChange: 2016-03-01 00:00:00 +0000 <- scroll back to March from Feb
calendarCurrentPageDidChange: 2016-03-31 23:00:00 +0000 <- now scroll to April!?! (is currently displaying April on screen)
Also at this point, if i select a date, it is wrong by one day. in didSelectDate, I selected 20th April. this is what shows:
(Date Selected: 2016-04-19 23:00:00 +0000)
Am i overlooking something here or is this actually unusual behaviour? Thanks!
I am using Swift 2.2, Xcode 7.3. iphone 6 with ios 9.3. I have tested in objective C using your example project, it doesn't seem to be an issue there at all

I think this is something to do with the timezone hour change difference in March/October. It shows -1 hour from April to September, then corrects itself at November again

@lynchjbrendan   The example doesn't print NSDate object directly, it prints [calendar stringFromDate:date];

@WenchaoD , Thanks for the prompt reply. Thanks! :)
I was getting confused that it wasn't printing in UTC. If anyone else comes across this and is confused, you can see the date in UTC by using this the following:
func getDateAsStringInUTC(date: NSDate) -> String{
let dateFormatter = NSDateFormatter()
dateFormatter.dateFormat = "yyyy-MM-dd HH:mm:ss ZZZ"
let UTCTimeAsString = dateFormatter.stringFromDate(date)
return UTCTimeAsString
}
func calendar(calendar: FSCalendar, didSelectDate date: NSDate) {
print(getDateAsStringInUTC(date))
}
func calendarCurrentPageDidChange(calendar: FSCalendar) {
print(getDateAsStringInUTC(calendar.currentPage))
}

Actually, you can just use
[calendar stringFromDate:date format:@"yyyy-MM-dd HH:mm:ss ZZZ"];

But still thanks.


added TypeScript Definitions for blackbox

In the case you don't know typescript: http://www.typescriptlang.org/
It uses definition files (.d.ts) to know which type a variable will be. This is used for Intellisense editor support and error checking.

Thanks!


Plugin doesn't handle or indicate an unsafe repository (where the directory owner is not me!)

Thanks in advance for your bug report!

[X] Have you reproduced issue in safe mode?
[X] Have you used the debugging guide to try to resolve the issue?
[X] Have you checked our FAQs to make sure your question isn't answered there?
[X] Have you checked to make sure your issue does not already exist?
[X] Have you checked you are on the latest release of Pulsar?

What happened?
If opening a folder one deep from parent, it only offers the Create initial repository.
If opening the parent folder, it shows that it is git-tracked but does not display any commit history.
Once the git command "git config --global --add safe.directory {pathname}" has been done, everything works as expected.
Pulsar version
1.104.2023051203
Which OS does this happen on?
🪟 Windows
OS details
Windows 7
Which CPU architecture are you running this on?
64-bit(x86_64)
What steps are needed to reproduce this?
see "what happened"...
Additional Information:
see https://github.blog/2022-04-12-git-security-vulnerability-announced/ for more info...

Thanks for reporting this!
I do want to mention that often times Pulsar uses the version of Git that's already on your System. So please ensure that you're up to date there.
Otherwise for the few tasks that do still use some other version of Git, we will have to see about upgrading those.

It's a windows 7 vm that doesn't have have git already installed.  In fact, it was after I installed another editor (that also used its own copy of git) that this one told me it was unsafe and prompted me to trust it the repo, after which I could open it in Pulsar...


Latest version of PhpStorm #PS-242.20224.361 is not supported

Describe the bug
The latest version of PhpStorm #PS-242.20224.361 is not supported by this plugin and the IDE has disabled the plugin for now.
I'm properly too soon by submitting this. I hope a new version is coming, so I can use the plugin again in the latest version of PhpStorm. Thank you for this great plugin.
Screenshots

Desktop (please complete the following information):

macOS 14.5

Thanks for the heads up and kind words :) New version coming soon!

Fixed in 08308bff2056fd1af764d88649de7fe90b8516b1

Now approved in the plugin store here: https://plugins.jetbrains.com/plugin/23928-contextive/versions/stable/598421
@frankvanhest let me know if any problems

@chrissimon-au, thank you for the new release!


Utterance cloner unable to generate speech using text different from the reference-transcription

Hello!
I read the paper "Prosody Cloning in Zero-Shot Multispeaker Text-to-Speech" and I ran the code using "run_utterance_cloner.py"
Looking at the aligner between text and reference, the model is not able to generate speech using text that doesn't correspond to the reference.
However, in your demo on HuggingFace .. this feature was supported.
Could you, please, describe how to generate a speech of different text using this approach?

Hi!
Thanks for your interest! As you said, there always needs to be a corresponding reference utterance. In the huggingface demo, there are just multiple references, one for each prompt. At the time when I made the demo, Gradio didn't yet offer the feature to display the audios prior to executing the demo, so the references are always displayed alongside the generated audio.
The use of this is mostly meant for privacy. So the input utterance and the output utterance are always the same and retain the original prosody, but the voice can be exchanged, so that the original speaker can remain anonymous.

Interesting! thank you for the explanation. Interesting paper.


CORS issue with 1.0.0-alpha2

I have a Startup.cs similar to the following:-
        public void ConfigureServices(IServiceCollection services)
        {
            // Add framework services.
            services.AddCors(options =>
            {
                options.AddPolicy("CorsPolicy",
                    builder => builder
                    .AllowAnyOrigin()
                    .AllowAnyMethod()
                    .AllowAnyHeader()
                    //.AllowCredentials()
                    );
            });
            services.AddMvc();
            services.AddSignalR();

            services.AddSwaggerGen(c =>
            {
                c.SwaggerDoc("v1", new Info { Title = "Contacts API", Version = "v1" });
            });
        }

        // This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
        public void Configure(IApplicationBuilder app, IHostingEnvironment env)
        {
            if (env.IsDevelopment())
            {
                app.UseDeveloperExceptionPage();
            }

            app.UseDefaultFiles();
            app.UseStaticFiles();
            app.UseWebSockets();

            app.UseMvc(routes =>
            {
                routes.MapRoute(
                    name: "default",
                    template: "{controller=Home}/{action=Index}/{id?}");
            });

            app.UseSignalR(routes =>
            {
                routes.MapHub<DefaultHub>("hubs/default");
            });

            app.UseCors("CorsPolicy");

            app.UseSwagger();

            app.UseSwaggerUI(c =>
            {
                c.SwaggerEndpoint("/swagger/v1/swagger.json", "Contacts API V1");
            });
        }
    }

In the front end, the code is doing the following:-
    ...
    this._httpConnection = new HttpConnection(this._hubUrl, { transport: TransportType.WebSockets });
    this._hubConnection = new HubConnection(this._httpConnection);

    try {
      this._hubConnection.on(this._methodName, data => {
        this.dataRecieved.emit(data);
      });

      await this._hubConnection.start();
      ...

When the start() method is called on the client, I see the following in the console (Google Chrome):
Failed to load http://localhost:50960/hubs/default: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:53364' is therefore not allowed access.

I did note that #4000 had been logged in August however there are no comments on it, so I assume this was due to the alpha releases coming out.
Obviously in my case the MVC and Swagger stuff isn't necessary for SignalR to work, however I left that in to give a clue whether that could be breaking CORS. I configured CORS in exactly the same way I managed to do for MVC itself, so I am guessing that SignalR for .net core isn't quite there.

 I app.UseCors after my app.UseSignalR, when the SignalR connection was getting setup I have the same CORS error. Switch those to call UseCors before UseSignalR, appears to be working!
Thanks!


add extra visual level for local view, view more only lose some detail.

add extra visual level to local image, we can zoom in even data source can not provide that level.

Thanks, this looks pretty cool.
At the very lists it needs tests to be merged and an entry in CHANGELOG.
I wonder whether extraVisualLevel is the best name for this. It's about tileLevel, so I think  maxVisualTileLevel would be more consistent as it's also a max?

I made a bunch of comments. It has been a while since I touched this code, so forgive me if some questions are naive. Hang with me here and lets get this merged, it's a nice and useful function!

Actually set maximumZoomScale of NATiledImageMapView can do the same thing, may be I should widthdraw the pull request?

So maximumZoomScale just works and accomplishes the same result? Then yes.


uib-popover-html not working

uib-popover-html is not working starting at 1.2.0
This Plunker works as is, but if you change the UIBS version to 1.2.0+ it breaks.  I didn't see any breaking changes that would cause this in the changelog.
http://plnkr.co/edit/Cafvvc2K9lZMoKB3v8y4?p=preview
Version of Angular, UIBS, and Bootstrap
Angular: 1.5.0
UIBS: 1.2.0
Bootstrap: 3.3.6

@sdesmond, please be respectful of our time by searching existing open and closed issues before opening a new one.  This is a duplicate of #5602 and has already been fixed in master.

@icfantv, I would also ask that you be respectful and not assume I haven't searched the issues.  The default search for issues includes the tag is:open, so I searched and found no results.  We're all on the same team here.  Sorry I missed it, and that's for pointing out the fix.

@sdesmond, the apology is appreciated, the attitude is not.  we deal with dozens of issues per week the large majority of which are varying degrees of issues like yours.  some people are just lazy, some are in such a rush to have their issue addressed they don't read, and some are so entitled they actually get demanding and abusive.  please remember that the next time you don't appreciate what you might view as a sharp remark.  most are not actually bugs.
the above creates an enormous amount of work for us because this library is so popular.  you need to remember that we are all unpaid volunteers and the processes we have in place not only make our lives easier, but allow us to address YOUR needs faster.
when developers get lazy, the entire community suffers.  and quite frankly, that's not fair to anyone.

@icfantv, I've been following this project for a while now and know how far it's come, especially in the last little while.  I absolutely appreciate what you all do to keep this going.  Not trying to be disrespectful at all, just hoping for the benefit of the doubt as I tried to submit the issue in the most helpful way possible.  Obviously my fault for only searching open issues, so we can leave it at that.  Thanks again for the hard work.


post processor clean up

Issue Description
What did you expect to see happen?
PostProcessor should use Assembler Object in a consistent way.
What did you see instead?
There are currently two different ways to add Assembler Object for PostProcessor.
Do you have a suggested fix for the development team?
Please attach the input file(s) that generate this error.  The simpler the input, the faster we can find the issue.

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[x] 1. Is it tagged with a type: defect or task?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[x] 1. If the issue is a defect, is the defect fixed?
[x] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[x] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[x] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

Approved for Closure bia #971


Enable Sourcegraph

I want to use Sourcegraph for jquery-countTo code search, browsing, and usage examples. Can an admin enable Sourcegraph for this repository? Just go to https://sourcegraph.com/github.com/mhuggins/jquery-countTo. (It should only take 30 seconds.)
Thank you!

Sure, just did. :)


add default version for Fedora 35

Signed-off-by: John Florian<EMAIL_ADDRESS>

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

Would it be possible to merge this PR soon as Fedora 35 was released some months ago now.

I completely forgot about this. After approving I started CI and forgot to check back.

@ekohl thank you for your fast reaction to my comment. Would it be possible to build a new release soon, so that we can reference an official version instead of a specific commit.

I started https://github.com/puppetlabs/puppetlabs-postgresql/runs/4951722999?check_suite_focus=true but it's been running for over an hour. That's not normal.

It finally opened https://github.com/puppetlabs/puppetlabs-postgresql/pull/1320.


Default configuration running with V100-32G causes OOM

When using the official default configuration with a single V100-32G, I found this will cause OOM with the whole pipline. And according to other issues mentioned above, I changed the batch_size from 16 to 8, and it works. So I just wonder if  this is normal 'cause I did not see any instruction.

@binderwang, can you please share the command line and stack trace of the OOM? Thanks!

Assuming you are using the default settings for the single-gpu deployment type, I think this is expected with only 32GB of memory. Lowering the batch size will decrease memory requirements.

In the bash file, I just modify the command line as this:
deepspeed --num_gpus 1 main.py \    --model_name_or_path facebook/opt-1.3b \    --per_device_train_batch_size 8 --per_device_eval_batch_size 8 \    --gradient_accumulation_steps 2 --lora_dim 128 --zero_stage $ZERO_STAGE \    --only_optimize_lora --deepspeed --output_dir $OUTPUT &> $OUTPUT/training.log
And I set zero_stage to 2. With this above command I can run Step1 successfully with a single V100-32G. But If I change nothing with the default command line, it will cause OOM error.

And the error is as
Beginning of Epoch 1/1, Total Micro Batches 2860 Traceback (most recent call last):   File "main.py", line 341, in <module>     main()   File "main.py", line 310, in main     outputs = model(**batch, use_cache=False)   File "/home/ma-user/anaconda3/envs/PyTorch-1.11.0/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl     return forward_call(*input, **kwargs)   File "/home/ma-user/anaconda3/envs/PyTorch-1.11.0/lib/python3.7/site-packages/deepspeed/utils/nvtx.py", line 15, in wrapped_fn     ret_val = func(*args, **kwargs)   File "/home/ma-user/anaconda3/envs/PyTorch-1.11.0/lib/python3.7/site-packages/deepspeed/runtime/engine.py", line 1695, in forward     loss = self.module(*inputs, **kwargs)   File "/home/ma-user/anaconda3/envs/PyTorch-1.11.0/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl     return forward_call(*input, **kwargs)   File "/home/ma-user/anaconda3/envs/PyTorch-1.11.0/lib/python3.7/site-packages/transformers/models/opt/modeling_opt.py", line 947, in forward     return_dict=return_dict,   File "/home/ma-user/anaconda3/envs/PyTorch-1.11.0/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl     return forward_call(*input, **kwargs)   File "/home/ma-user/anaconda3/envs/PyTorch-1.11.0/lib/python3.7/site-packages/transformers/models/opt/modeling_opt.py", line 710, in forward     use_cache=use_cache,   File "/home/ma-user/anaconda3/envs/PyTorch-1.11.0/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl     return forward_call(*input, **kwargs)   File "/home/ma-user/anaconda3/envs/PyTorch-1.11.0/lib/python3.7/site-packages/transformers/models/opt/modeling_opt.py", line 334, in forward     output_attentions=output_attentions,   File "/home/ma-user/anaconda3/envs/PyTorch-1.11.0/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl     return forward_call(*input, **kwargs)   File "/home/ma-user/anaconda3/envs/PyTorch-1.11.0/lib/python3.7/site-packages/transformers/models/opt/modeling_opt.py", line 211, in forward     attn_weights = torch.bmm(query_states, key_states.transpose(1, 2)) RuntimeError: CUDA out of memory. Tried to allocate 256.00 MiB (GPU 0; 31.75 GiB total capacity; 30.33 GiB already allocated; 231.50 MiB free; 30.53 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF

@binderwang this is expected behavior. The scripts we released are intended for A6000/A100 GPUs. If you are running on a GPU with less memory, you will be required to modify the scripts (e.g., lower the batch size) so that the model can train with less available memory.

It is wierd that when I only add the --gradient_checkpointing with the default script, I can successfully run these steps with a V100-32G, and only using half of the GPU memory.

@binderwang the options that will have the greatest impact on memory requirements right now are --gradient_checkpointing, --only_optimize_lora, --zero_stage {0|1|2|3}, and --per_device_*_batch_size.
The examples we provide were tuned for specific systems (primarily A6000 / A100 GPUs) and we encourage users to modify the examples to fit their systems. We are also working on an autotuning feature which will automatically detect optimal settings for the parameters listed above. Stay tuned for those updates!


[research] CLN reckless plugin to install plugins

An alias to start with:
alias reckless='sudo -u bitcoin reckless -c /home/bitcoin/.lightning/config -d /home/bitcoin/reckless'

More info: https://github.com/darosior/reckless

Tested on v1.11.2. : Not working
reckless clones the CLN plugin repo via ssh, which results in a Host key verification failed on the Blitz.
Opened: https://github.com/ElementsProject/lightning/issues/7635


fix: hoist constraints on inputs to top of program

Description
Problem*
Followup to #4065
Summary*
This PR fixes a small mistake in #4065. I mixed up the front and back of the vector for the case where we don't find an instruction for which the constraint's inputs are a result. This results in constraints on the program inputs not being pushed up to the beginning of the program.
This PR fixes the index to insert these instructions so that we constrain the inputs first.
Additional Context
Documentation*
Check one:

[x] No documentation needed.
[ ] Documentation included in this PR.
[ ] [Exceptional Case] Documentation to be submitted in a separate PR.

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Looking at the bit_and test we probably want to split out the actual bit operations as right now the only constraint actually getting down to ACIR is this snippet from the test:
    let flag = (x == 0) & (y == 16);
    assert(flag);

We would be testing a bit AND still, but it would only be on u1. We should probably do it for u8 as well (u11 isn't really needed as we will be moving to power of two bit sizes) to make sure we are still testing the more complex bit AND.

I'd agree that we should ensure that we keep a mix of "compile down to trivial constraints" and "carry full behaviour through to ACIR" in our tests so that we're testing both behaviours. I've modified the test so that the latter half works on fresh inputs.


Add star count badges to github repos (partial)

#327
Added star count badges to all the tools in the Python section to see how it looks. To be honest it does end up looking a little busy. Also, I'm not really sure about the API limits of shields.io - even though loading one section works, it may have trouble if the entire readme has these badges (~330 github links currently) on a page load.
Link to see the readme on my fork: https://github.com/amar1729/static-analysis/#python

Thanks for your work @Amar1729. I have to say this information is quite helpful when comparing different tools.
The data format has changed a bit. The README.md is actually rendered from the list of tools  in data.yml.
We could extend this structure per entry so that we have a separate "source" URL that points to Gitlab/Github next to the homepage URL like so:
- name: My awesome tool
  homepage: "https://example.com/"
  source: "https://github.com/example/awesome"
  description: "Awesome description"
  tags:
    - foo
    - bar

Of course, many tools don't have a dedicated homepage, so the homepage URL would be the same as the source URL. Others are proprietary, so the source URL would be empty. That's fine in my book, as the two URLs would serve a different purpose.
We can then auto-generate the README from the template here.
The shields could be linked there. To make it look less busy, you can style the shields a bit. Here is an example:

As a final step, we could add the star counter to the new website by calling the Github API with the information from the source URL.
Sounds like a plan?

@mre ah I didn't even notice the README was being rendered from somewhere else. I think that having that source separate from the homepage makes sense (I know Homebrew and pypi.org keep that info separate, for example).
Do you think it makes sense to have a separate linter.badge entry in data.yml, so the README templating can just use that? Then any non-github sources will just have an empty badge attribute as well.
And yeah, displaying these badges on the website sounds like a good idea.

Do you think it makes sense to have a distinct linter.badge entry in data.yml, so the README templating can just use that? Then any non-github sources will just have an empty badge attribute as well.

Yeah sure we could add that. If we find batches for Gitlab in the future, too then that would be the perfect place. As you said, if we find no good fit it'll simple be missing from the entry. 👍

@Amar1729 as a heads-up we refactored the tools list lately, so you'd have to reintegrate master if you're planning to work on adding the fields we talked about. Wonder if we should create a new branch for that and create a fresh pull request. What do you think?

Closed in favor of new pr


Support for Request/Response Cashing

It would be great to have support and possibility to turn on the Request/Response Caching from Algolia.
Official doc: https://www.algolia.com/doc/api-client/getting-started/customize/javascript/?client=javascript#caching-requests-and-responses
Reference to: https://github.com/nuxt-modules/algolia/discussions/111

I will implement it as a part of next release.
Stay tuned!

Thank you!


Bump minimum Python version to 3.5

Describe the new feature you'd like
We are now using Python 3.5 specific features (type annotations). We should bump the Python version in setup.py and document it in the logical places.
See here for more info

✅ in changelog


"asynchronous function" -> "async function"

When you use await in a function that isn't marked async, you get the error "The await expression can only be used in an asynchronous function". Here's an example from DartPad2:

Could you change "asynchronous function" to "async function"?
In the docs we've been distinguishing between asynchronous functions (any function that returns a future) and async functions (the subset of asynchronous functions that have async before the body). I'm not sure readers will necessarily get the difference (and I'm open to other options), but we should try to be consistent.

https://dart-review.googlesource.com/c/sdk/+/111603


Lexy Documentation

It would be nice to have some documentation on how Lexy works as i would like to use it in the views for the project i am working on.

Content blocks @block('example')
Assets

At the moment i am trying to make sense of the code that already does this but it's not all that clear.

What does Lexy offer than Blade doesn't?

@jbrooksuk It seems to be more stripped back.

Thanks :)

+1 for some docs.


Introduce PropertyFormat to avoid validation errors that can lead to internal exceptions

Fixes #247 , more info there.
Can you please review my code for now so that I can make some appropriate changes?
Cheers

Hey, just pushed the changes, can you please take a look if it's alright?

Hey! Thank you so much! I'm happy that there were some things I could've improved :)
Just pushed the changes

Btw,
Do you think we should add a default case handling here with a simple console.warn() that the property format is not recognized?
You didn't do that in other places, so I didn't do it as well - I'd just like to hear your opinion.
https://github.com/Arciiix/notifo/blob/b1d331f386f0f62999666c4b9983d15384517dfd/frontend/src/app/pages/integrations/IntegrationDialog.tsx#L127-L136

No, I dont think so.

Okay.
So do you think everything's ready to merge? Or do you want me to do something more (I will unify the phone numbers in another PR)?

The build fails ;) ... so it is not ready yet.

I think I forgot to update the C#'s SDK (I only updated the TypeScript one)... stupid me ;)
Thank you for noting!

Actually never mind - I updated it as well.
I'll investigate a bit because this error seems to be weird - everything was working in my local env.

Okay, I think I spotted my mistake - the host field in the SMTP integration expects http(s):// since I set its FieldFormat to URL.
Will fix it soon.
Have a nice day!

It's especially weird that the same tests that fail in the GitHub Action actually pass on my local machine

Do you think I should create a dummy (e.g. adding a comment) commit to re-run it again?

It also failed with previous commits. Just try it

Oh, so it apparently worked 🤣
I think I can quote the popular "My code doesn't work, I have no idea why" and "My code works, I have no idea why".
Also, it actually worked on the 2nd previous commit (8a9dbcf), but didn't work on the previous one which actually didn't change anything on the back-end side (b1d331f). That's weird.
Have a nice evening!

Just renamed the "Url" PropertyFormat to "HttpUrl". Can you take a look if everything is looking good?

Only the one thing with allocations. See


changed currency format

human readable currency for amount implemented yet

"12,345.68" instead of "1234568"

updated this function using<EMAIL_ADDRESS>
"$12,345.68" instead of "1234568"

Dump file example:
Describing ACH file 'examples/testdata/ack-read.ach'

  Origin      OriginName               Destination  DestinationName          FileCreationDate  FileCreationTime
   231380104  My Bank Name              031300012   Federal Reserve Bank     190816            1055

  BatchNumber  SECCode  ServiceClassCode    CompanyName       DiscretionaryData     Identification  EntryDescription  EffectiveEntryDate  DescriptiveDate
  0000001      ACK      220 (Credits Only)  Name on Account                         231380104       Vndr Pay          190816

    TransactionCode                              RDFIIdentification  AccountNumber      Amount  Name                    TraceNumber      Category
    24 (Checking Zero Dollar Remittance Credit)  03130001            744-5678-99        $0.00   Best. #1<PHONE_NUMBER>00001  Forward

    TransactionCode                              RDFIIdentification  AccountNumber      Amount  Name                    TraceNumber      Category
    24 (Checking Zero Dollar Remittance Credit)  03130001            744-5678-99        $0.00   Best. #1<PHONE_NUMBER>00002  Forward

  ServiceClassCode    EntryAddendaCount  EntryHash   TotalDebits  TotalCredits  MACCode              ODFIIdentification  BatchNumber
  220 (Credits Only)  000002<PHONE_NUMBER>  $0.00        $0.00                              23138010            0000001

  BatchCount  BlockCount  EntryAddendaCount  TotalDebitAmount  TotalCreditAmount
  000001      000001      00000002           $0.00             $0.00

Codecov Report

Merging #1161 (cf610d9) into master (17dd4e4) will not change coverage.
The diff coverage is 100.00%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1161   +/-   ##
=======================================
  Coverage   90.09%   90.09%
=======================================
  Files          71       71
  Lines        6742     6742
=======================================
  Hits         6074     6074
  Misses        401      401
  Partials      267      267

I don't think adding $ helps us here. While ACH in North America is USD based I've seen some applications in Africa/South America that wouldn't use $. The separator , vs . is already wrong for their local currencies, so I'm hesitant to add more formatting. My bad that the issue was still open.


Add performance advices to PARCELS page or tutorial

There are several caveats on how to setup MPI, job submissions, Dask and Parcels in order to be performant and efficient. Especially after changes in https://github.com/OceanParcels/parcels/pull/719, the wiki or PARCELS page or the tuturial should be updated with that.

[ ]  Check if guidelines on the submission system are sufficient (e.g. explain the submission script and its parameters)

[ ]  Check that the MPI explanations are sufficient (e.g. mention that next to just installing mpi4py, one needs to actually run the script with mpiexec)

[ ]  Explain (on the surface) the relation between Numpy/SciPy, xarray and dask, and how data allocation is affected

[ ]  Explain how the chunking is done, how to use the field_chunksize parameter, and how to setup the (locally-operating) dask.yaml file

[ ] Update / link to the documentation in the warning messages on the field_chunksize in NetcdfFileBuffer.__enter__()

After having a look on the website and the documentation_MPI.ipynb, I think that this notebook doesn't really reflect what it promises from the heading of the website. I suggest splitting it up in two notebooks - one called Splitting and Managing Field data, which holds the main parts of the current documentation_MPI.ipynb (e.g. called field_chunking_tutorial.ipynb), and a new, separate example for documentation_MPI.ipynb called Parallel Kernel Optimization via MPI that really introduces and shows how to integrate MPI with some communication. Right now, if I wanted to use MPI for some simulation, the current notebook wouldn't really demonstrate to me how to use the feature.


HomeAssistant slave instance does not get configuration attributes from configuration.yaml

I have set up Home Assistant to work in multiple instances.

Master - faster machine
Slave - Raspberry Pi Zero - multiple sensors in remote location

My slave script looks like that:
#! /usr/bin/env python
#
import homeassistant.remote as remote
import homeassistant.bootstrap as bootstrap
import homeassistant.config as config
remote_api = remote.API("<IP_ADDRESS>", port= 8123)
hass = remote.HomeAssistant(remote_api)
myconfig = config.load_yaml_config_file("/home/pi/.homeassistant/configuration.yaml")
bootstrap.setup_component(hass, 'frontend', myconfig)
bootstrap.setup_component(hass, 'sensor', myconfig)
bootstrap.setup_component(hass, 'switch', myconfig)
hass.start()
hass.block_till_stopped()

Original issue was that DHT sensor connected to a slave showed it's state in master but did not get temperature unit configuration. Unit was set to None and because of that in frontend it didn't plot those historical temperature charts but state charts like sun or switches.
I've investigated the code a bit and I think I've found something that might be causing the issue.
Although I'm not very experienced in python so I'm might be wrong.
Slave Home assistant is being run through  homeassistant.remote and in remote.py in init method there is part of code:
self.config = ha.Config()
where ha is homeassistant.core
In homeassistant.core init takes config from Config class. It looks like that:
    def __init__(self):
        """Initialize new Home Assistant object."""
        self.pool = pool = create_worker_pool()
        self.bus = EventBus(pool)
        self.services = ServiceRegistry(self.bus, pool)
        self.states = StateMachine(self.bus)
        self.config = Config()

And this Config class in init contains setting default values to all attributes:
def __init__(self):
        """Initialize a new config object."""
        self.latitude = None
        self.longitude = None
        self.temperature_unit = None
        self.location_name = None
        self.time_zone = None

I did not find in the calling sequence anything that would load the units from configuration.yaml in case of homeassistant being started from remote.py.
I did a test and changed temperature config to:
self.temperature_unit = "C"
And it solved the issue for me. Although I'm not completly sure if it proves my findings are correct.
As I mentioned before I do not know python good enough to be comfortable with changing home assistant core.
Can anyone verify if my findings are correct and apply some code changes so that it is solved?

You are correct. Config is currently not shared between slave and master. It wouldn't make much sense either as slaves can have a different location gps, name or timezone. Really the only value you do want to share is the temperature unit.

After some more test my quick 'workaround' broke temperature unit for Onewire sensor, so not the best way to correct it.
I agree with you that sharing things like location coordinates, name and timezone is not necessary but this data is also in slave configuration.yaml can it be read from there for sensors connected to the slave?
If it's not possible or too much work to correct it in more general way, do you think it would be good to add possibility to define temperature unit in configuration.yaml per sensor independently from global setting?
So far in my situation I've corrected it by hardcoding temperature unit in dht.py . Works fine but not a very elegant correction.

I did run into the same issue. I am currently trying to implement slave as kind of command line switch.

Has this been resolved?

Closing this as we won't fix this. Config will not be shared.


[Output] Jira_v2 add secondary jira output to support new API based authentication.

to:
cc: @airbnb/streamalert-maintainers @ryandeivert
related to: https://github.com/airbnb/streamalert/issues/932
resolves: https://github.com/airbnb/streamalert/issues/932
Background
The following addresses https://github.com/airbnb/streamalert/issues/932 , the following is not intended to be merged at this point as it will break existing usage of the Jira output.
The existing jira output remains unchanged and this is now jira_v2
Changes

Copy of jira output and relevant tests.
Rebrand as jira_v2
TODO (Add relevant docs)

Testing
Deployed to production as an output

hi @gavinelder do you want to change this from a draft or is it still a work in progress?

@ryandeivert been testing it in production for a few weeks will change.

Coverage increased (+0.09%) to 96.923% when pulling ca18e57c244d33c9a23dbb2aa9efb374f4301e56 on gavinelder:jira_api into 2085a69bce434e26edad6e96a05dc647eaf20b62 on airbnb:master.


Github Actions: make sure config.php exists

This makes the tests pass on Github Actions again.

Oh right, I forgot about the tests! Thank you!


Wrong minting dates at hover card

I strongly sense there are wrong times on hover cards
@jbienesdev 👀
This author has something which was made way weeks ago https://beta.kodadot.xyz/rmrk/u/J9cppW5x7akmWG6yTiEMHy5Cx8VVZ9YTQKV3AGfABvFXrFN
Also please recheck other numbers as well:)

Sure! Will take a look on this


Emit supplemental outputs for the target variant

This patch teaches the driver how to emit the supplementary outputs for a module build for the target-variant.
These supplementary outputs are:

Swift module
Swift module documentation
Swift module source information
Swift interface
Swift private interface
Swift package interface
JSON API description
JSON ABI description

This means that the driver can emit all of the relevant outputs for a build in a single invocation without needing to be called twice with the same arguments, with one to emit the zippered object and target supplemental outputs, and again for the target-variant outputs.
Patch to add new flags: https://github.com/swiftlang/swift/pull/78336
rdar://141582282

@swift-ci please test


Space between confirmed and active case

To change little formatting between the confirmed and active case.

+1 same for me in smaller devices

Yes , I think so some spaces should be there in between the confirmed and the active cases

Let me /claim this issue

Issue solved!


Slider-Question

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
import * as React from 'react';
import Box from '@mui/material/Box';
import Stack from '@mui/material/Stack';
import Slider from '@mui/material/Slider';
import VolumeDown from '@mui/icons-material/VolumeDown';
import VolumeUp from '@mui/icons-material/VolumeUp';
export default function ContinuousSlider() {
const [value, setValue] = React.useState(30);
const handleChange = (event, newValue) => {
setValue(newValue);
};
return (
<Box sx={{ width: 200 }}>
<Stack spacing={2} direction="row" sx={{ mb: 1 }} alignItems="center">

);
}
Current behavior 😯
Causes redundant renders.
Expected behavior 🤔
Should be using onChangeCommitted instead of onChange.
Context 🔦
Caused redundant renders and slowed down my app.
Your environment 🌎
No response

It doesn't look like this bug report has enough info for one of us to reproduce it.
Please provide a CodeSandbox (https://mui.com/r/issue-template), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve


minor fix

Thank you for the fix! When you are ready for review, feel free to move out of draft.

Initially left it as draft in case I had more commits as I'm experimenting.


kernel: timeout: fix issue with z_timeout_expires

issue found with Ztest case of test_thread_timeout_remaining_expires on Intel ISH platform when adjust CONFIG_SYS_CLOCK_TICKS_PER_SEC to 10k.
timeout_rem() return exact remaining ticks which is calibrated by decrease elapsed(), as behavior in z_add_timeout, z_timeout_expires should get expire ticks to be timeout using current tick as base, so need get exact current ticks by plus elasped().

It looks like it doesn't break anything, but I would like to have @andyross or @npitre review.
There are some compliance issues to fix before its mergable @qipengzha

try to make it more clear for this issue,   the timeout_rem() is calibrated, then the current_tick should also be calibrated, if not, then z_timeout_expires is not correct ticks.  eg, if add a timeout of 100 ticks when curr_tick is 500(expect timeout @ 600 ticks),  if call z_timeout_expires after 10 ticks is elapse() but curr_tick is not update in tickless kernel,  then timeout_rem() return 90 ticks while curr_tick is still 500,  current api will get 590 ticks which is not expect.
for this ztest case, it can pass test if TICKS_PER_SECOND < 1K,  since the elapse() will get small ticks for same period of time
thanks


Update InstrumentParallel.cpp

Added suppression in "__tsan_default_suppressions" function inserted by the instrumentation pass.

@simoatze: is there an issue ticket for this problem? If so, it would be good to list it here gor better tracking. If not, could yoi create a short one, thulis will help review this PR.

@dongahn Joachim added the suppression in the suppression file, I was just adding the same in the function that is inserted at instrumentation time, so we don't need to specify the explicitly the suppression file with the env var TSAN_OPTION. I didn't open an issue because it was just an integration. Do you want me to open it?

@simoatze: thanks. Yes, please copy and paste your comment into a new new issue and refer it in this PR. This way, if someone other than us can trace back the topic of this PR when they look at the commit message. Also, if you have "Resolve #N" in your PR message body (where N is the issue ticket number), merging your PR will automatically close that issue. Thanks.

LGTM. Since this is @jprotze 's branch, i will let him review this and merge if ok.


allow configuration of docker metadata context

See https://nav-it.slack.com/archives/C5KUST8N6/p1683561444028229
It's kind of wonky though with regards to detached heads and metadata-action's implementation for resolving the ref (git symbolic-ref HEAD), so maybe we should solve this some other way. Thoughts?

If the goal is to allow Git tags, how about using type=ref,event=tag in docker/metadata-action ? I expect it to be omitted if it's not set, falling back to our tag?
Unsure if it works as expected with the workflow from Slack, but it could be a workflow that pushes a tag, with another workflow which deploys when a tag is pushed.

My understanding is that some teams want to build specific commits and deploy manually using a workflow with workflow_dispatch.
metadata-action uses the workflow context by default, which for workflow_dispatch resolves:

GITHUB_SHA to "Last commit on the GITHUB_REF branch or tag"
GITHUB_REF to "Branch or tag that received dispatch".

Current behavior: If the user provides a specific commit as input to workflow_dispatch, performs checkout on this commit, the SHA (and thus our generated tag) points to the last commit on the given branch that was provided during input - instead of the commit that is checked out.
The git context should account for this, though as evidenced in the Slack thread, doesn't seem to work too well with detached HEADs.

After some more thinking, this is likely best solved by using https://github.com/nais/login directly so that the team can customize the tag/build/push jobs to their liking