Adding option to disable rename feature , Fixes #159

Option to disable setting the alternative advertising name. This is required by some customers that had released a device that crashes when this feature is being used. It's better to update a device without this feature then not update it at all.

🥇 Looks perfect ! will merge and publish a release for that now !


Suggestions for co-log binding

Hello, here are some suggestions regarding the co-log binding.
First: The binding is great and I liked the use of forkEnv for the LogActions in particular. Nice work! :+1:
As for the changes to the test suite: Most of them are simple code reorderings and styling issues which helped me throughout the review. Those mirror my personal taste; Feel free to incorporate those in your PR or not.
I noticed that some functions do not have a binding. For example: Colog.Rotation.withLogRotation, Colog.Concurrent.withBackgroundLogger, Colog.Core.IO.logStringStdout, Colog.Core.IO.logPrint.
Is this intentional?
In addition to the changes here I have the following ideas:

Maybe it is good to split the bindings in effectful-co-log-core and effectful-co-log to mirror the package structure of the authors of the original package.
This way we could provide bindings for those who are concerned about the dependency footprint of their application.
It may be good to mirror the module hierarchy present in the original packages, e.g. Effectful.Colog.Monad, Effectful.Colog.Core, ...
This makes it a bit easier to track for which functions/types we provide bindings to.
Both ideas could be implemented in a separate PR so we can merge yours quickly.
@ambroslins What do you think?

One more thing: You may note that I accidentally pushed on your branch (Didn't know that this is even possible). This was not my intention and I reverted the changes.

Hello, thanks for the feedback and suggestions.
Using unsafeUnliftIO is a great idea, using IO for these functions did bother me, but I could not figure out how to get rid of it.
The styling changes to the test suit also look reasonable.
The missing functions are not intentional, I just missed them. I will add them.

I am fine with splitting the package.

For the module hierarchy, I choose to use a single module as in a mirrored module hierarchy some modules would end up very small. E.g. the Effectful.Colog.Pure module would basically only contain the  logMessagePure function (maybe adding the runPureLogEff and execPureLogEff from the test suite would be a good idea).
While working on this I also found the generated haddock documentation for the Colog module difficult to use. As i would constantly jump back and forth between small modules. However this is just my personal preference and I am open to implement the mirrored module hierarchy.


IndexError: list index out of range

Hi,
I run CAT and have the following error:
"Warning:  Sequence is long (max 32000000 for training).
Training on the first 32000000 bases.
diamond file is /path_to/target.fa_contigs_prodigal.m8
gff file is /path_to/target.fa_contigs_prodigal.gff
faa file is /path_to/target.fa_contigs_prodigal.faa
bitscore 1 is 0.9
bitscore 2 is 0.5
Traceback (most recent call last):
File "/tools/analysis/metagenomics/CAT-master/CAT/bin/contig_id.py", line 109, in
protein=line[1].split("|")[1]
IndexError: list index out of range
running prodigal
running diamond search"

the first message is showing that sequence is long. But in my fasta file, "sum = 332021388, n = 37221, ave = 8920.27, largest = 27143". Is this warning due to that the total file size is larger than 32000000 bases?

For the "IndexError: list index out of range" error, I have checked the diamond file and here are several lines:
"1_5     ACA64215.1      45.3    75      40      1       10      83      283     357     8.4e-05 55.5
1_5     WP_059303418.1  37.8    74      46      0       13      86      319     392     1.1e-04 55.1
1_5     SCF81904.1      40.5    84      48      1       4       85      543     626     1.1e-04 55.1"
For the corresponding codes:
"all_pro=open(diamond,'r')
for line in all_pro:
line=line.strip()
line=line.split("\t")
protein=line[1].split("|")[1]
d_allpro[protein]=True "
The cause of this error should be that there is no "|“ in protein ids. How can I solve this?

Best,
Quan

As far as I can understand, the cause of this problem is that, CAT expects the sequences ids in nr.faa to contain gi separated by "|", while actually these ids are accession.version now. "gi_taxid_prot.dmp" seems to be a mapping file mapping each gi to a taxid. The solution may be using an updated mapping file which maps accessions to taxid, am I correct?

Update:
I solved it by changing "line[1].split("|")[1]" to "line[1]" in contig_id.py and used a new mapping file:
wget ftp://ftp.ncbi.nih.gov/pub/taxonomy/accession2taxid/prot.accession2taxid.gz
gunzip ftp://ftp.ncbi.nih.gov/pub/taxonomy/accession2taxid/prot.accession2taxid.gz
cut -f2-3 prot.accession2taxid > gi_taxid_prot.dmp

Yes. CAT uses the gi, so gi2taxid file and not the the
prot.accession2taxid. A new version where the access
is considered is coming. Thanks for the contribution.
2016-11-07 6:13 GMT+01:00 danshu<EMAIL_ADDRESS>
Update:
I solved it by changing "line[1].split("|")[1]" to "line[1]" in
contig_id.py and used a new mapping file:
wget ftp://ftp.ncbi.nih.gov/pub/taxonomy/accession2taxid/prot.
accession2taxid.gz
gunzip ftp://ftp.ncbi.nih.gov/pub/taxonomy/accession2taxid/prot.
accession2taxid.gz
cut -f2-3 prot.accession2taxid > gi_taxid_prot.dmp
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/diegocambuy/CAT/issues/3#issuecomment-258748924, or mute
the thread
https://github.com/notifications/unsubscribe-auth/APWt3x9Q0Yy3GRXMdjUMQ6Y1qucEoi-nks5q7rOKgaJpZM4KqL-7
.


Ensure the order of images in the response

Solution you'd like
I encountered this problem when I tried to match the image descriptions in the reponse and image urls.
Since this library is converting the image urls to set, not list, the order of the urls are lost.
I changed the code and the description slightly to address this issue.

Thank you for contribution!
Solved at f5d8fcccc10f030310e3b4065a4fed70bdd7ae0f by kota113


merging of subprocess into master

Creating an issue so that we can track what will likely be incremental progress in getting this stuff moved over.
Necessary conditions:

[ ] (@streichler ) a successful rebase onto a recent master

Is there a reason we can't track this on #627?

Nope.  I just forgot that one existed.


Detail the time asymptotic complexity of lint rules

As a developer I would like to know the asymptotic complexity of lint rules. Ideally I would like to have the best, average and worst time complexities (where appropriate) detailed in the individual lint rule documentation page.
Additional context
The dart analyser can be slowed when analysing big codebases. Some rules might be resource intensive in nature since more tree traversing/visiting needs to be performed. Having the asymptotic complexities for each rule would help developers decide if a rule is worth to be included or not.

I'd love something like this.  FWIW we do some pretty primitive rank-ordering on our benchmarking bot and despite how basic it is, it's been really handy in providing early warnings around performance degradation (though checking it is entirely manual).  Anyway, I've often thought even these crude numbers could be useful in sorting lints into some coarse-grained performance buckets.
Here's a recent run for example (https://github.com/dart-lang/linter/actions/runs/4187360395/jobs/7257088851):
--------------------------------------------------------------------------
Timings                                                                 ms
--------------------------------------------------------------------------
close_sinks                                                             91
use_late_for_private_fields_and_variables                               61
always_specify_types                                                    58
prefer_double_quotes                                                    49
avoid_redundant_argument_values                                         48
unreachable_from_main                                                   33
prefer_final_parameters                                                 32
unnecessary_overrides [core]                                            30
discarded_futures                                                       30
avoid_positional_boolean_parameters                                     30
depend_on_referenced_packages [core]                                    29
use_named_constants                                                     27
prefer_const_constructors [flutter]                                     27
unnecessary_string_escapes [recommended]                                27
directives_ordering                                                     27
cancel_subscriptions                                                    26
prefer_final_fields [recommended]                                       25
lines_longer_than_80_chars                                              25
require_trailing_commas                                                 24
non_constant_identifier_names [core]                                    24
use_build_context_synchronously [flutter]                               22
avoid_dynamic_calls                                                     21
void_checks [core]                                                      20
no_runtimeType_toString                                                 20
avoid_web_libraries_in_flutter [flutter]                                19
cascade_invocations                                                     19
null_closures [recommended]                                             18
avoid_type_to_string                                                    18
public_member_api_docs                                                  18
prefer_contains [recommended]                                           18
avoid_escaping_inner_quotes                                             17
collection_methods_unrelated_type                                       16
flutter_style_todos                                                     15
avoid_returning_this                                                    15
library_private_types_in_public_api [recommended]                       14
annotate_overrides [recommended]                                        14
prefer_final_locals                                                     14
control_flow_in_finally [recommended]                                   12
always_put_control_body_on_new_line                                     12
always_use_package_imports                                              12
prefer_const_constructors_in_immutables [flutter]                       11
use_to_and_as_if_applicable                                             11
prefer_const_declarations [flutter]                                     11
no_leading_underscores_for_local_identifiers [recommended]              10
implementation_imports [recommended]                                    10
unnecessary_parenthesis                                                 10
always_declare_return_types                                              9
overridden_fields [recommended]                                          9
prefer_initializing_formals [recommended]                                9
avoid_print [flutter]                                                    9
parameter_assignments                                                    9
file_names [core]                                                        9
type_annotate_public_apis                                                9
avoid_unused_constructor_parameters                                      9
use_key_in_widget_constructors [flutter]                                 9
unnecessary_lambdas                                                      8
unrelated_type_equality_checks [core]                                    8
slash_for_doc_comments [recommended]                                     8
avoid_types_as_parameter_names [core]                                    8
noop_primitive_operations                                                8
unnecessary_nullable_for_final_variable_declarations [recommended]       7
leading_newlines_in_multiline_strings                                    7
deprecated_consistency                                                   7
use_setters_to_change_properties                                         7
unawaited_futures                                                        7
prefer_relative_imports                                                  7
use_raw_strings                                                          7
always_put_required_named_parameters_first                               7
prefer_is_empty [core]                                                   7
unnecessary_statements                                                   7
unsafe_html                                                              7
avoid_renaming_method_parameters [recommended]                           7
avoid_slow_async_io                                                      7
unnecessary_null_aware_operator_on_extension_on_nullable                 7
prefer_collection_literals [recommended]                                 7
diagnostic_describe_all_properties                                       6
use_super_parameters                                                     6
avoid_init_to_null [recommended]                                         6
recursive_getters [recommended]                                          6
use_enums                                                                6
prefer_void_to_null [recommended]                                        6
avoid_final_parameters                                                   6
constant_identifier_names [recommended]                                  6
avoid_unnecessary_containers [flutter]                                   5
avoid_returning_null_for_void [recommended]                              5
join_return_with_assignment                                              5
sized_box_shrink_expand                                                  3
eol_at_end_of_file                                                       3
exhaustive_cases [recommended]                                           3
missing_whitespace_between_adjacent_strings                              3
prefer_iterable_whereType [core]                                         3
sized_box_for_whitespace [flutter]                                       3
prefer_foreach                                                           3
prefer_if_null_operators [recommended]                                   3
unnecessary_this [recommended]                                           3
use_decorated_box                                                        2
prefer_is_not_empty [core]                                               2
prefer_asserts_with_message                                              2
await_only_futures [core]                                                2
test_types_in_equals                                                     2
unnecessary_constructor_name [recommended]                               2
provide_deprecation_message [core]                                       2
sort_unnamed_constructors_first                                          2
prefer_mixin                                                             2
unnecessary_to_list_in_spreads                                           2
do_not_use_environment                                                   2
use_is_even_rather_than_modulo                                           2
unnecessary_brace_in_string_interps [recommended]                        2
avoid_single_cascade_in_expression_statements [recommended]              2
always_require_non_null_named_parameters [recommended]                   2
prefer_int_literals                                                      2
tighten_type_of_initializing_formals                                     2
prefer_null_aware_method_calls                                           2
prefer_for_elements_to_map_fromIterable [recommended]                    2
no_logic_in_create_state [flutter]                                       2
no_duplicate_case_values [core]                                          2
library_prefixes [recommended]                                           2
avoid_return_types_on_setters [recommended]                              2
unnecessary_null_in_if_null_operators [recommended]                      2
avoid_js_rounded_ints                                                    2
combinators_ordering                                                     2
avoid_implementing_value_types                                           2
invalid_case_patterns                                                    2
throw_in_finally                                                         2
one_member_abstracts                                                     2
avoid_double_and_int_checks                                              2
only_throw_errors                                                        2
prefer_adjacent_string_concatenation [recommended]                       2
camel_case_extensions [core]                                             1
conditional_uri_does_not_exist                                           1
avoid_bool_literals_in_conditional_expressions                           1
avoid_empty_else [core]                                                  1
prefer_generic_function_type_aliases [core]                              1
use_function_type_syntax_for_parameters [recommended]                    1
no_leading_underscores_for_library_prefixes [recommended]                1
unnecessary_new [recommended]                                            1
prefer_if_elements_to_conditional_expressions                            1
empty_statements [recommended]                                           1
avoid_returning_null                                                     1
empty_constructor_bodies [recommended]                                   1
no_default_cases                                                         1
avoid_catches_without_on_clauses                                         1
implicit_call_tearoffs                                                   1
empty_catches [core]                                                     1
avoid_returning_null_for_future                                          1
unnecessary_library_directive                                            1
unnecessary_late [recommended]                                           1
unnecessary_string_interpolations [recommended]                          1
type_init_formals [recommended]                                          1
use_rethrow_when_possible [recommended]                                  1
avoid_catching_errors                                                    1
prefer_null_aware_operators [recommended]                                1
cast_nullable_to_non_nullable                                            1
prefer_is_not_operator [recommended]                                     1
unnecessary_null_aware_assignments [recommended]                         1
use_string_in_part_of_directives                                         1
unnecessary_null_checks                                                  1
use_test_throws_matchers                                                 1
library_names [recommended]                                              1
sort_pub_dependencies                                                    0
enable_null_safety                                                       0
prefer_equal_for_default_values [recommended]                            0
avoid_as                                                                 0
unnecessary_breaks                                                       0
secure_pubspec_urls                                                      0
package_names [recommended]                                              0
invariant_booleans                                                       0
super_goes_last                                                          0
prefer_bool_in_asserts                                                   0
package_prefixed_library_names [core]                                    0
--------------------------------------------------------------------------
Total                                                                 1730
--------------------------------------------------------------------------

Thanks @pq for the comment!
I'm happy that you agree that classifying the lint rules depending on their performance is great. Thanks for supplying those crude numbers.
How do you think we should move forward with this?

We're pretty heads-down with work supporting upcoming language features so I'm not sure how many cycles I'll have right away but I'd be open to hearing design considerations and ideas.
Can you describe what you'd like to see in an ideal world?
/fyi @InMatrix who might may have ideas or pointers to prior art


Export stats to a time-series database

Since we're on the network data path we can measure the traffic as it passes through. We could  measure

packets per second
bytes per second
DNS requests latency
DNS request failure rate
Number of active UDP NAT rules
etc

This data could be sent to an external time-series database such as influxdb and then visualised.
This involves

writing a client for a time-series database (this may be as easy as connect()ing to it and writing .json messages)
adding some basic counters to the network stack
(stretch goal): allow the user to define their own filters via datakit and record these too

From Prometheus you'd only need to expose and HTTP /metrics endpoint, see docs about format.

@djs55 have you seen https://github.com/mirage/prometheus ?

Note: It's already being used in DatakitCI courtesy of https://github.com/mirage/prometheus


Revert faster setup code

This is because we encountered a bizarre camera alignment
bug when trying to pull off something cool with positioning
and zooming.
There is no obvious reason why this is the code that breaks,
unless it's related to the camera operations not being blocking.
Room changes are still quite fast with queue_resource, which
is the proper way to do it. Fixing the thread deadlock bug in
it would probably be the smarter way than trying to figure this
out.
Restored the relevant parts of b246a5761bfa6c80180e58ffbbf4910b014dddfc,
as it was reverted only to make the sequence free from conflicts.
Revert "Fix not LEAVE_BLACK behavior for new code"
This reverts commit 4137c1b61e65320274f75632ec87e63c702f4a1c.
Revert "Fake a :setup for scenes without one to keep up the flow of events"
This reverts commit 2625a144c837661b8f3e67feb217c59cb20522b1.
Revert "Yielding on any event causes lag, don't do it"
This reverts commit 05d93233f2644c9ddc08c88548ca1303b83884eb.
Revert "Make it possible to have a scene without events_path"
This reverts commit b246a5761bfa6c80180e58ffbbf4910b014dddfc.
Revert "Kick off :setup before previous scene is cleared"
This reverts commit 9ffda4fd7b4a87e66c44beace4533f3946915449.

Relevant to #238


langchain[minor]: feat(embedding integration): Gradient AI

Adds support for Gradient AI's embeddings.
Resolves #3007

Thank you!

@jacoblee93 I can also whip up a quick contribution doc for the text embeddings, since we are presently missing a specific one for text embeddings

@jacoblee93 I can also whip up a quick contribution doc for the text embeddings, since we are presently missing a specific one for text embeddings.
Something like this

Saw you opened a PR, thank you!


Issue when using ResponseDetective with Carthage

Hello! We are having this issue since yesterday when trying to use the project through Carthage:
A shell task (/usr/bin/env git clone --bare --quiet https://github.com/netguru/xcconfigs.git /Users/adrian/Library/Caches/org.carthage.CarthageKit/dependencies/xcconfigs) failed with exit code 128:
fatal: could not read Username for 'https://github.com': terminal prompts disabled

Any chance that the access rights for the repo https://github.com/netguru/xcconfigs.git changed?

Yes, it seems that xcconfigs repo has been made private. I don't work at Netguru anymore, and I haven't been given prior notice of this change. Fortunately, I have a local clone and the repository was MIT-licensed. I'll just include the config files directly in ResponseDetective instead of pulling them from that repository. Hold on.

Side note: I'm not sure how much longer will I be able to maintain ResponseDetective. I don't get paid for this anymore and I'm effectively maintaining a project for free under my ex-employer's brand (this is strange). I'm not sure what will happen once I resign from being a maintainer, there's a high chance this will become abandonware or just disappear randomly as xcconfigs did. I suggest migrating off ResponseDetective to other tools, such as FLEX, or keeping a fork just in case.

Released in version 1.5.0. Your project should now build. Thank you for bringing this up.

Thank you for solving this quickly!


Create ASPSP software statement in Open Banking Directory for SAPI-G

SAPI-G does not currently have an Open Banking Directory ASPSP Software Statement, it also does not have an OB signed OBWac or OBSeal.

Create a new ASPSP software statement in Open Banking Directory
Create new OBWac and OBSeal and associate them with the new software statement

Store the keys in the ob-ci-secrets repo

Configure our deployment to use the new OBSeal to sign OB API response messages (as per docs: https://github.com/SecureApiGateway/SecureApiGateway/wiki/Configuring-Open-Banking-ASPSP-secrets#signing-certificates)

Hey team! Please add your planning poker estimate with Zenhub @dbadham-fr @jorgesanchezperez @shaunharrisonFR

Software Statement:
Secure API Gateway Test Bank v1
https://manager.openbankingtest.org.uk/participants/PSD2/0015800001041REAAY/software-statements/YfxeCuxENNVSwUiJbS0LIH
Domain: v1.ob-sandbox.forgerock.financial


Make "Your organization's description" text-box responsive.

Currently Your organization's description text-box in Organization Settings/Organization profile is not reponsive.

@zulipbot label "area: settings UI"

Hmm, yeah, this would be good to fix.

@zulipbot claim

@zulipbot claim.

@zulipbot abandon

@zulipbot claim

@zulipbot claim

@synicalsyntax Hey Zulipbot commands not working here. Can you check it?

@abhigyank @zulipbot was down during the time you and @Shobitha-M tried to claim the issue. Feel free to try again.

@zulipbot claim


New company

Here are the info
Orga
https://orga.nl/
Schiedam, NL

Same here. https://orga.nl/careers/
Now, you're good to go.
You can open a PR per each issue


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

AWS CodeBuild CI Report

CodeBuild project: DDKIntegrationTestsD8472609-5SCHWjldmWcf
Commit ID: f686d5a6a3ec0a8e8500e8067d367ea0a1d0db64
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Should spinnaker be configured once the cluster has been created?

It works to access the spinnaker and jenkins ui. There is a job in Jenkins. When it is run it fails immediately. The spinnaker UI is empty. What is the expected flow? Should there be a job in jenkins in spinnaker as well? Perhaps the context could be extended in the readme?

https://github.com/spinnaker/spinnaker/issues/1939


API documentation does not match Readme

Bug Report
Current Behavior
The public API documentation found on https://ssense.github.io/vue-carousel/api/ states that the paginationEnabled setting is defaulted to false, while the Readme states otherwise.
Possible Solution
change false to true

Hey @caseyrlentz, thanks for report. I'll fix right now!

Fixed it a while ago but forgot to rebuild lol should be visible now! Thanks for reporting the issue :octocat:


No font name rollovers on "Home" panel?

The main headline, "Beautiful Web Type" is set in Abril Fatface, but on http://hellohappy.org/beautiful-web-type/ I had to view the page's source code to find that out. (Fringe benefit: I also learned the hard way that you kerned W-eb, which for more easily is discoverable if you highlight the text by selecting it.) But, my point is, that first panel at the top of the page--shouldn't the fonts in it be conveniently identified too? (Pretty please?)

I've just launched a completely new version of the site and all the samples are clearly labeled, with links to both the Google Fonts version (when available) and the GitHub repos for each typeface.


Abstraction package for blazor

When developing a library for ASP.NET Core that needs to use IApplicationBuilder I can reference Microsoft.AspNetCore.Http.Abstractions.
When I want to use IComponentsApplicationBuilder I need to add an reference to Microsoft.AspNetCore.Blazor which not just contains the abstractions.
Having an abstraction package for Blazor like Microsoft.AspNetCore.Blazor.Abstractions would allow to just reference the abstractions instead of needing to add a reference to blazor itself.

@chris579 Thanks for contacting us.
Can you give us more details on why is it problematic to reference Microsoft.AspNetCore.Blazor and what you are trying to accomplish?
This is an area that is likely to change in the future. What functionality of IComponentsApplicationBuilder are you trying to get access to?

I find it inconvenient to reference Blazor as a whole (especially because it will heavily change in the future). When there are new Blazor versions introducing breaking changes (that are not affecting my library) I would need to update my package even though it does not make use of Blazor at all. Plus, if creating a library that does target both Blazor and Blazor Serverside I would need to reference Blazor as a whole too. That means that if somebody uses Blazor Serverside and installs my library he will also install blazor, no matter if he even uses it.

Plus, if creating a library that does target both Blazor and Blazor Serverside I would need to reference Blazor as a whole too.

Our recommendation would be to reference Microsoft.AspNetCore.Components and Microsoft.AspNetCore.Components.Web if you're building a library. Can you be specific about what else you need?

IComponentsApplicationBuilder is neither part of Microsoft.AspNetCore.Components nor Microsoft.AspNetCore.Components.Web.

I think we need to know a little bit more about what you're doing then. Using IComponentApplicationBuilder isn't something I anticipated from a library. Is there a publicly accessible link I can look at?

I removed the relevant code from my library some days ago because I restructured it a bit. However, this kind of describes what I did:
public class MyInitService
{
    public void DoInit() {}
}

public class Startup
{
    public void ConfigureServices(IServiceCollection services)
    {
        services.AddTransient<MyInitService>();
    }

    public void Configure(IComponentsApplicationBuilder app)
    {
        app.UseInit();
        app.AddComponent<App>("app");
    }
}

public static class ComponentApplicationBuilderExtensions
{
    public static IComponentsApplicationBuilder UseInit(this IComponentsApplicationBuilder componentsApplicationBuilder)
    {
        componentsApplicationBuilder.Services.GetRequiredService<MyInitService>().DoInit();

        return componentsApplicationBuilder;
    }
}

For me, the purpose of the Configure method is similar to the one from AspNetCore server.

Thanks @chris579 - we'll look for a solution to this kind of thing as part of the client release.

We will tackle this as part of https://github.com/aspnet/AspNetCore/issues/16874


ja: Make docs/concepts/overview/working-with-objects/namespaces.md follow v1.18 of the original text

This is a Feature Request

What would you like to be added
Update docs/concepts/overview/working-with-objects/namespaces.md to follow v1.18 of the original (English) text.
Why is this needed
content/ja/docs/concepts/overview/working-with-objects/namespaces.md is outdated.
Comments
/language ja
/good-first-issue
File to update
https://github.com/kubernetes/website/blob/dev-1.18-ja.1/content/ja/docs/concepts/overview/working-with-objects/namespaces.md
Original
https://github.com/kubernetes/website/blob/fb6364d/content/en/docs/concepts/overview/working-with-objects/namespaces.md
diff between translated and v1.18
https://gist.github.com/a3b863d5d54336fd28cf054763722573
Note
Currently, we use dev-1.18-ja.1 branch. Please open a PR targeting the branch.
ref
https://kubernetes.io/ja/docs/contribute/localization/
If you have a question, feel free to ask us at slack.k8s.io #kubernetes-docs-ja channel.

/close


Declaring normative content

In the past, TDWG had "normative" and "non-normative" documents.  That all went away when the Standards Documentation Specification (SDS) came into force.  Section 3.2.1 says:

The normative and non-normative parts of standards MUST be clearly labeled as such. If all of the content of a document is normative, this MUST be stated in the introduction to the document. If a single document contains both normative and non-normative content, material in a single section SHOULD be of a single type. The introduction SHOULD state that content is normative unless otherwise noted and headings SHOULD indicate if material in that section is non-normative.
It is also permissible to indicate in the introduction that content of a particular type (e.g. examples or diagrams) is non-normative.

For an example, see Section 1.1 of the Audubon Core Term List document.
In Darwin Core, we don't have a similar human-readable document defining the terms and saying what parts of that document are normative.  Rather, we have the quick reference guide, a document that is outside of the standard itself and therefore not subject to the requirements for standards documents, and the so called "normative document", a CSV file that contains the metadata fields that are (mostly) considered normative and excluding stuff like notes and examples that aren't normative.
I don't have a problem with that approach.  However, if I were a newbie with Darwin Core, I'm not sure it would be obvious to me how this all works.  I would like to see some text at least in the Quick Reference Guide and maybe also on the DwC landing page and  repo landing page that flesh this out a bit.  Perhaps some statement on the Quick Reference Guide like "Term definitions are normative.  Comments and examples are informative. " and on the landing pages changing the description of the normative document to "A CSV file with the full version history of Darwin Core terms. This file contains all of the term metadata that are considered normative."

Speaking as a newbie to Darwin Core, I have just been confused by this. For example, for organismQuantityType, the quick reference guide gives some examples, but omits some that one would intuitively expect (e.g. '%biomass' is listed, but not '%cover', widely used in plant and marine ecology). The normative CSV file mentioned above seems to list the same three examples as the quick reference guide, but from what @baskaufs says above this file is normative (although presumably not exhaustive with respect to vocab). Anyway, the result is that I am confused about the process for creating and using new vocab items within terms, such as my '%cover' example above.

This is something we need to work on. People have noted the lack of an easy-to-read Darwin Core specification document that clearly lays out what is normative and what is not. I will try to bring this up with the DwC Maintenance Group to see if we can fix it.
One comment for now: I think the general consensus has been reached that examples are not normative. So the presence of some examples and the absence of others shouldn't be construed to have too much significance. Optimally, there would be some kind of "best-practices" guide outside of the standard that would provide guidance to people in using the terms. There is a much higher demand for such documents than the supply of people who are willing to take the time to write them. That isn't an excuse, just a statement of fact. We need to keep working on that.

There is a much higher demand for such documents than the supply of people who are willing to take the time to write them. That isn't an excuse, just a statement of fact.
Entirely understood. Thanks for all the efforts of the community to date. I hope my comment will be taken as a useful example of where the understanding of a newcomer might falter based on the current resources, rather than a complaint. Many thanks for response.

Thank you for taking the time to write it! This kind of feedback is really useful.

I think this is fixed with the completion of https://github.com/tdwg/dwc/milestone/10?closed=1


nextcload cant find the windows version

Expected behavior
nextcloud shows to have window version.
Actual behavior
when selecting it in the IU it can find the correct version
Information about the Issue
Steps to reproduce the behavior

...
...

No information provided or steps to replicate - Closing 😞


Replacing ptvsd with debugpy in remote attach config prompt and contributing guide

For https://github.com/microsoft/vscode-python/issues/10916

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.

Codecov Report

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

@@            Coverage Diff             @@
##           master   #10917      +/-   ##
==========================================
- Coverage   60.64%   60.62%   -0.02%
==========================================
  Files         580      580
  Lines       31557    31557
  Branches     4490     4490
==========================================
- Hits        19138    19132       -6
- Misses      11444    11448       +4
- Partials      975      977       +2

Impacted Files
Coverage Δ

src/datascience-ui/react-common/arePathsSame.ts
75.00% <0.00%> (-12.50%)
:arrow_down:

src/client/common/utils/platform.ts
64.70% <0.00%> (-11.77%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0.00%> (-1.57%)
:arrow_down:

src/client/common/process/proc.ts
14.49% <0.00%> (-0.73%)
: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 dd1bb4c...cca8f33. Read the comment docs.


added parameter set to search for all groups in an OU

Added just a small change to allow monitoring of all group types/scope in an OU. ADModule only - I don't have access to the Quest cmdlets.

Sorry for the delay and thanks for the PR @lc9er !
However looks like there are some conflicts but there are not visible here.
It looks like you changed the file encoding (this happen often when using PSISE for example).
Could you resubmit without editing the encoding ?


kepler metrics persistence between reboot

[ ] #305
[ ] deployment and doc update

We had some discussion about this in the issue.
We are not sure if we really need this since what should persist the data is the data base (Prometheus in this case) and prometheus already has a good logic to deal with counters that were reset....
For example, other exporters, e.g. node_exporter does not persist the data.....
So, maybe persist the data is an overhead that might not be necessary....


Azure CXP Updating Formating

Fixed formatting on line 115 to the following

[!NOTE]
Group Overage Claim :- To ensure that the token size doesn’t exceed HTTP header size limits, Azure AD limits the number of object Ids that it includes in the groups claim. If a user is member of more groups than the overage limit (150 for SAML tokens, 200 for JWT tokens), then Azure AD does not emit the groups claim in the token. Instead, it includes an overage claim in the token that indicates to the application to query the Graph API to retrieve the user’s group membership.
{
...
"_claim_names": {
"groups": "src1"
},
{
"_claim_sources": {
"src1": {
"endpoint":"[Graph Url to get this user's group membership from]"
}
}
...
}
You can use the BulkCreateGroups.ps1 provided in the App Creation Scripts folder to help test overage scenarios.

As per MicrosoftDocs/azure-docs#39289

@shashishailaj : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@shashishailaj: I'm sorry - only the author of this article, @rwike77, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@jborsecnik : Thanks for your contribution! The author(s) have been notified to review your proposed change.


(HAL-32) REENTRANCY IN MCR STAKING CONTRACT

(HAL-32) REENTRANCY IN MCR STAKING CONTRACT
Auditor: Halborn
Severity: Low
Description
The staking contract staking function makes an external call to an arbitrary IERC20 interface. That allows an attacker to artificially inflate their stake through a malicious whitelisted contract without providing the corresponding tokens. That can cause unfair voting or reward privileges, and possibility to drain the staking contract.
The custodian provided in the parameters is arbitrary and the function calls custodian.transferFrom, exposing itself to reentrancy in the case where the custodian is malicious:

Running the test shows:

BVSS
AO:S/AC:L/AX:L/R:N/S:C/C:N/A:N/I:N/D:C/Y:C (3.1)

Recommendation
It is recommended to add a reentrancy guard on the stake function.

Possibly a duplicate of #419


Only apply new layout params if they have actually changed.

Otherwise will trigger an infinite loop of layout re-drawing if a badge is present which a) is bad for performance and b) breaks interactions with other custom behaviors
You can see this by overriding requestLayout in BottomBar.java:
@Override
public void requestLayout() {
   super.requestLayout();
}

You will observe this breakpoint is hit continually in the event that a badge is drawn on one of the tabs.
This took me about 3 hrs to debug and I would suggest is a Very Serious regression. Thanks!

FYI I believe this issue may also be mitigated by commit f41aac0b092d89aa123164a4ccb65798745306e1


12

This PR solves #12 . Tests for all Vector functions have been written, now coverage on them is supposed to be around 100%.

@rultor merge this PR please

@rultor merge this PR please

@maxgoryunov Can't merge it. Some CI checks were failed. Apparently, the pull request is not ready to be merged since it has some problems. Please, fix them first.


Uncaught Error: Position (36.2, Infinity) is less than the current token's start ((37, 0))

Opened a file and this error was thrown.

Have been using beta all day and this is the first time it did it upon opening a file.  Nothing different about this one file compared to other files I have been in and out of across the day.
Atom Version: 1.13.0-beta0
Electron Version: 1.3.6
System: Mac OS X 10.12.1
Thrown From: Atom Core
Stack Trace
Uncaught Error: Position (36.2, Infinity) is less than the current token's start ((37, 0))
At /Applications/Atom Beta.app/Contents/Resources/app.asar/node_modules/display-index/dist/token-iterator.js:251

Error: Position (36.2, Infinity) is less than the current token's start ((37, 0))
    at TokenIterator.translateScreenPosition (/Applications/Atom Beta.app/Contents/Resources/app.asar/node_modules/display-index/dist/token-iterator.js:251:15)
    at DisplayLayer.module.exports.DisplayLayer.translateScreenPosition (/Applications/Atom Beta.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/display-layer.js:1491:52)
    at DisplayMarkerLayer.module.exports.DisplayMarkerLayer.translateToBufferMarkerLayerFindParams (/Applications/Atom Beta.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/display-marker-layer.js:220:46)
    at DisplayMarkerLayer.module.exports.DisplayMarkerLayer.findMarkers (/Applications/Atom Beta.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/display-marker-layer.js:133:21)
    at DecorationManager.module.exports.DecorationManager.decorationsStateForScreenRowRange (/Applications/Atom Beta.app/Contents/Resources/app.asar/src/decoration-manager.js:151:21)
    at TextEditor.module.exports.TextEditor.decorationsStateForScreenRowRange (/Applications/Atom Beta.app/Contents/Resources/app.asar/src/text-editor.js:1711:37)
    at TextEditorPresenter.module.exports.TextEditorPresenter.fetchDecorations (/Applications/Atom Beta.app/Contents/Resources/app.asar/src/text-editor-presenter.js:1380:44)
    at TextEditorPresenter.module.exports.TextEditorPresenter.getPreMeasurementState (/Applications/Atom Beta.app/Contents/Resources/app.asar/src/text-editor-presenter.js:125:14)
    at TextEditorComponent.module.exports.TextEditorComponent.updateSyncPreMeasurement (/Applications/Atom Beta.app/Contents/Resources/app.asar/src/text-editor-component.js:259:60)
    at TextEditorComponent.module.exports.TextEditorComponent.updateSync (/Applications/Atom Beta.app/Contents/Resources/app.asar/src/text-editor-component.js:191:12)
    at /Applications/Atom Beta.app/Contents/Resources/app.asar/src/text-editor-component.js:318:28
    at ViewRegistry.module.exports.ViewRegistry.performDocumentUpdate (/Applications/Atom Beta.app/Contents/Resources/app.asar/src/view-registry.js:219:9)
    at /Applications/Atom Beta.app/Contents/Resources/app.asar/src/view-registry.js:3:59

Commands
     -3:50.6.0 find-and-replace:show (input.hidden-input)
     -3:49.7.0 core:confirm (input.hidden-input)
     -3:41.6.0 core:save (input.hidden-input)
  2x -3:41.5.0 core:backspace (input.hidden-input)
     -3:40.6.0 core:save (input.hidden-input)
     -3:39.9.0 core:move-right (input.hidden-input)
     -3:39.8.0 core:backspace (input.hidden-input)
  2x -3:39.6.0 core:save (input.hidden-input)
     -0:38.1.0 core:paste (input.hidden-input)
  2x -0:36.6.0 core:backspace (input.hidden-input)
     -0:34.4.0 core:save (input.hidden-input)
     -0:14.6.0 core:undo (input.hidden-input)
     -0:13.9.0 core:redo (input.hidden-input)
     -0:11.9.0 core:cut (input.hidden-input)
     -0:10.6.0 core:backspace (input.hidden-input)
     -0:10.2.0 core:save (input.hidden-input)

Config
{
  "core": {
    "allowPendingPaneItems": false,
    "customFileTypes": {
      "source.ini": [
        ".buckconfig",
        ".flowconfig"
      ],
      "source.json": [
        ".arcconfig"
      ],
      "source.python": [
        "BUCK"
      ],
      "text.html.liquid": [
        "inc",
        "tpl",
        "htm",
        "html"
      ]
    },
    "disabledPackages": [
      "wrap-guide",
      "htmlhint",
      "Remote-FTP"
    ],
    "excludeVcsIgnoredPaths": false,
    "followSymlinks": false,
    "openEmptyEditorOnStart": false,
    "packagesWithKeymapsDisabled": [
      "sass-autocompile",
      "highlight-selected",
      "highlight-line"
    ],
    "telemetryConsent": "limited",
    "themes": [
      "genesis-ui",
      "one-dark-vivid-syntax"
    ],
    "useCustomTitleBar": true
  },
  "editor": {
    "invisibles": {},
    "scrollPastEnd": true,
    "showIndentGuide": true,
    "showInvisibles": true,
    "softTabs": false,
    "softWrap": true,
    "tabLength": 4,
    "tabType": "hard"
  }
}

Installed Packages
# User
atom-beautify, v0.29.13 (active)
atom-compile-less, v0.12.0 (active)
base16-ocean-dark-spacegray, v0.12.0 (inactive)
base64, v0.3.0 (inactive)
duotone-blue-dark-syntax, v1.4.0 (inactive)
duotone-dark-space-muted-syntax, v1.0.0 (inactive)
duotone-dark-space-syntax, v2.0.0 (inactive)
duotone-dark-syntax, v2.0.0 (inactive)
duotone-darksky, v1.1.5 (inactive)
duotone-snow, v2.0.2 (inactive)
ficus-dark-syntax, v1.1.0 (inactive)
file-icons, v1.7.24 (active)
genesis-syntax, v1.0.7 (inactive)
genesis-ui, v0.5.0 (active)
github-atom-dark-syntax, v0.2.0 (inactive)
github-atom-light-syntax, v0.2.0 (inactive)
grunt-runner, v0.14.0 (active)
hide-tree, v0.0.20 (active)
highlight-line, v0.11.1 (active)
highlight-selected, v0.11.2 (active)
jshint, v1.8.6 (active)
language-liquid, v0.5.1 (active)
less-than-slash, v0.16.0 (active)
merge-conflicts, v1.4.4 (active)
one-dark-vivid-syntax, v1.6.0 (active)
pigments, v0.38.0 (active)
project-manager, v3.3.3 (active)
Remote-FTP, v0.9.4 (inactive)
sass-autocompile, v0.13.1 (active)
sort-lines, v0.14.0 (inactive)
spacegray-atom-dark-syntax, v1.2.0 (inactive)
spacegray-dark-ui, v0.12.0 (inactive)
tab-title, v0.3.3 (active)
atom-dark-syntax, v0.28.0 (inactive)
atom-dark-ui, v0.53.0 (inactive)
atom-light-syntax, v0.29.0 (inactive)
atom-light-ui, v0.46.0 (inactive)
base16-tomorrow-dark-theme, v1.4.0 (inactive)
base16-tomorrow-light-theme, v1.4.0 (inactive)
one-dark-ui, v1.8.2 (inactive)
one-light-ui, v1.8.2 (inactive)
one-dark-syntax, v1.6.0 (inactive)
one-light-syntax, v1.6.0 (inactive)
solarized-dark-syntax, v1.1.1 (inactive)
solarized-light-syntax, v1.1.1 (inactive)
about, v1.7.2 (active)
archive-view, v0.62.0 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.14.1 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.33.1 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.2 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.43.2 (active)
bracket-matcher, v0.82.2 (active)
command-palette, v0.39.1 (active)
deprecation-cop, v0.55.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.40.0 (active)
find-and-replace, v0.204.1 (active)
fuzzy-finder, v1.4.0 (active)
git-diff, v1.2.0 (active)
go-to-line, v0.31.2 (inactive)
grammar-selector, v0.48.2 (active)
image-view, v0.60.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.2 (inactive)
markdown-preview, v0.159.1 (active)
metrics, v1.0.0 (active)
notifications, v0.65.1 (active)
open-on-github, v1.2.1 (inactive)
package-generator, v1.0.2 (inactive)
settings-view, v0.244.0 (active)
snippets, v1.0.3 (active)
spell-check, v0.68.5 (active)
status-bar, v1.6.0 (active)
styleguide, v0.48.0 (active)
symbols-view, v0.113.1 (inactive)
tabs, v0.103.1 (active)
timecop, v0.33.2 (active)
tree-view, v0.211.1 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.35.1 (active)
whitespace, v0.35.0 (active)
wrap-guide, v0.39.0 (inactive)
language-c, v0.54.0 (active)
language-clojure, v0.22.1 (active)
language-coffee-script, v0.48.1 (active)
language-csharp, v0.12.1 (active)
language-css, v0.40.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.43.0 (active)
language-html, v0.46.1 (active)
language-hyperlink, v0.16.1 (active)
language-java, v0.24.0 (active)
language-javascript, v0.122.0 (active)
language-json, v0.18.3 (active)
language-less, v0.29.6 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.37.0 (active)
language-php, v0.37.3 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.1 (active)
language-ruby, v0.70.2 (active)
language-ruby-on-rails, v0.25.1 (active)
language-sass, v0.57.0 (active)
language-shellscript, v0.23.0 (active)
language-source, v0.9.0 (active)
language-sql, v0.25.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.29.1 (active)
language-toml, v0.18.1 (active)
language-xml, v0.34.12 (active)
language-yaml, v0.27.1 (active)

# Dev
No dev packages

Same instance here.
Added a line, saved file, closed file, used fuzzy finder to open another file when the exception occurred. I am able to repeat the error whenever I open the specific file. File does not highlight syntax and is a few edits behind when the error occurs. When I click back into the editor contents, the syntax highlights (GFMD) and the edits I made a few minutes ago come back.
Version: Atom 1.13.0-beta1 ia32
Operating System: MS Windows 10 Home 10.0.14393
Device: Dell Inspiron 7559
Error Report
Atom Version: 1.13.0-beta1 ia32
Electron Version: 1.3.6
System: Microsoft Windows 10 Home 10.0.14393
Device: Dell Inspiron 7559
Thrown From: Atom Core
Stack Trace
Uncaught Error: Position (25.833333333333332, Infinity) is less than the current token's start ((26, 0))
At C:\Users\tjger\AppData\Local\atom\app-1.13.0-beta1\resources\app.asar\node_modules\display-index\dist\token-iterator.js:251

Error: Position (25.833333333333332, Infinity) is less than the current token's start ((26, 0))
    at TokenIterator.translateScreenPosition (C:\Users\tjger\AppData\Local\atom\app-1.13.0-beta1\resources\app.asar\node_modules\display-index\dist\token-iterator.js:251:15)
    at DisplayLayer.module.exports.DisplayLayer.translateScreenPosition (C:\Users\tjger\AppData\Local\atom\app-1.13.0-beta1\resources\app.asar\node_modules\text-buffer\lib\display-layer.js:1491:52)
    at DisplayMarkerLayer.module.exports.DisplayMarkerLayer.translateToBufferMarkerLayerFindParams (C:\Users\tjger\AppData\Local\atom\app-1.13.0-beta1\resources\app.asar\node_modules\text-buffer\lib\display-marker-layer.js:220:46)
    at DisplayMarkerLayer.module.exports.DisplayMarkerLayer.findMarkers (C:\Users\tjger\AppData\Local\atom\app-1.13.0-beta1\resources\app.asar\node_modules\text-buffer\lib\display-marker-layer.js:133:21)
    at DecorationManager.module.exports.DecorationManager.decorationsStateForScreenRowRange (C:\Users\tjger\AppData\Local\atom\app-1.13.0-beta1\resources\app.asar\src\decoration-manager.js:151:21)
    at TextEditor.module.exports.TextEditor.decorationsStateForScreenRowRange (C:\Users\tjger\AppData\Local\atom\app-1.13.0-beta1\resources\app.asar\src\text-editor.js:1711:37)
    at TextEditorPresenter.module.exports.TextEditorPresenter.fetchDecorations (C:\Users\tjger\AppData\Local\atom\app-1.13.0-beta1\resources\app.asar\src\text-editor-presenter.js:1380:44)
    at TextEditorPresenter.module.exports.TextEditorPresenter.getPreMeasurementState (C:\Users\tjger\AppData\Local\atom\app-1.13.0-beta1\resources\app.asar\src\text-editor-presenter.js:125:14)
    at TextEditorComponent.module.exports.TextEditorComponent.updateSyncPreMeasurement (C:\Users\tjger\AppData\Local\atom\app-1.13.0-beta1\resources\app.asar\src\text-editor-component.js:259:60)
    at TextEditorComponent.module.exports.TextEditorComponent.updateSync (C:\Users\tjger\AppData\Local\atom\app-1.13.0-beta1\resources\app.asar\src\text-editor-component.js:191:12)
    at C:\Users\tjger\AppData\Local\atom\app-1.13.0-beta1\resources\app.asar\src\text-editor-component.js:318:28
    at ViewRegistry.module.exports.ViewRegistry.performDocumentUpdate (C:\Users\tjger\AppData\Local\atom\app-1.13.0-beta1\resources\app.asar\src\view-registry.js:219:9)
    at C:\Users\tjger\AppData\Local\atom\app-1.13.0-beta1\resources\app.asar\src\view-registry.js:3:59

Commands
     -0:27.9.0 core:cancel (atom-workspace.workspace.scrollbars-visible-always.seti-ui-no-icons.theme-one-dark-syntax.theme-one-dark-ui)
     -0:27.2.0 fuzzy-finder:toggle-file-finder (atom-workspace.workspace.scrollbars-visible-always.seti-ui-no-icons.theme-one-dark-syntax.theme-one-dark-ui)
     -0:25.1.0 core:move-down (input.hidden-input)
     -0:24.9.0 core:confirm (input.hidden-input)
     -0:15.9.0 fuzzy-finder:toggle-file-finder (input.hidden-input)
     -0:11.1.0 core:backspace (input.hidden-input)
     -0:09.5.0 core:move-down (input.hidden-input)
     -0:09.2.0 core:confirm (input.hidden-input)
     -0:08.4.0 fuzzy-finder:toggle-file-finder (input.hidden-input)
     -0:07.5.0 editor:consolidate-selections (input.hidden-input)
     -0:07.5.0 core:cancel (input.hidden-input)
     -0:07.0 pane:show-next-recently-used-item (input.hidden-input)
     -0:06.8.0 core:close (input.hidden-input)
     -0:06.1.0 fuzzy-finder:toggle-file-finder (input.hidden-input)
     -0:04.1.0 core:move-down (input.hidden-input)
     -0:03.9.0 core:confirm (input.hidden-input)

Config
{
  "core": {
    "autoHideMenuBar": true,
    "disabledPackages": [
      "linter-pep8"
    ],
    "telemetryConsent": "limited"
  },
  "editor": {
    "fontSize": 13
  }
}

Installed Packages
# User
atom-beautify, v0.29.13 (active)
atom-python-test, v0.5.4 (active)
autoclose-html, v0.23.0 (active)
autocomplete-java, v1.2.5 (inactive)
autocomplete-python, v1.8.11 (active)
builder-go, v1.0.1 (active)
file-icons, v1.7.24 (active)
firepad, v0.8.0 (inactive)
gerot-word-count, v0.0.0 (inactive)
git-time-machine, v1.5.3 (inactive)
go-config, v1.2.4 (active)
highlight-selected, v0.11.2 (active)
linter, v1.11.18 (active)
linter-csslint, v1.3.3 (active)
linter-javac, v1.9.4 (active)
linter-pep8, v1.3.2 (inactive)
merge-conflicts, v1.4.4 (active)
minimap, v4.25.6 (active)
pretty-json, v1.6.1 (active)
wordcount, v2.8.0 (active)
atom-dark-syntax, v0.28.0 (inactive)
atom-dark-ui, v0.53.0 (inactive)
atom-light-syntax, v0.29.0 (inactive)
atom-light-ui, v0.46.0 (inactive)
base16-tomorrow-dark-theme, v1.4.0 (inactive)
base16-tomorrow-light-theme, v1.4.0 (inactive)
one-dark-ui, v1.8.2 (active)
one-light-ui, v1.8.2 (inactive)
one-dark-syntax, v1.6.0 (active)
one-light-syntax, v1.6.0 (inactive)
solarized-dark-syntax, v1.1.1 (inactive)
solarized-light-syntax, v1.1.1 (inactive)
about, v1.7.2 (active)
archive-view, v0.62.0 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.14.1 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.33.1 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.2 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.43.2 (active)
bracket-matcher, v0.82.2 (active)
command-palette, v0.39.1 (active)
deprecation-cop, v0.55.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.40.0 (active)
find-and-replace, v0.204.2 (inactive)
fuzzy-finder, v1.4.0 (active)
git-diff, v1.2.0 (active)
go-to-line, v0.31.2 (inactive)
grammar-selector, v0.48.2 (active)
image-view, v0.60.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.2 (inactive)
markdown-preview, v0.159.1 (active)
metrics, v1.0.0 (active)
notifications, v0.65.1 (active)
open-on-github, v1.2.1 (inactive)
package-generator, v1.0.2 (inactive)
settings-view, v0.244.0 (active)
snippets, v1.0.4 (active)
spell-check, v0.68.5 (active)
status-bar, v1.6.0 (active)
styleguide, v0.48.0 (active)
symbols-view, v0.113.1 (inactive)
tabs, v0.103.1 (active)
timecop, v0.33.2 (active)
tree-view, v0.211.1 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.35.1 (active)
whitespace, v0.35.0 (active)
wrap-guide, v0.39.0 (active)
language-c, v0.54.0 (active)
language-clojure, v0.22.1 (active)
language-coffee-script, v0.48.1 (active)
language-csharp, v0.12.1 (active)
language-css, v0.40.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.43.0 (active)
language-html, v0.46.1 (active)
language-hyperlink, v0.16.1 (active)
language-java, v0.24.0 (active)
language-javascript, v0.122.0 (active)
language-json, v0.18.3 (active)
language-less, v0.29.6 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.37.0 (active)
language-php, v0.37.3 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.1 (active)
language-ruby, v0.70.2 (active)
language-ruby-on-rails, v0.25.1 (active)
language-sass, v0.57.0 (active)
language-shellscript, v0.23.0 (active)
language-source, v0.9.0 (active)
language-sql, v0.25.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.29.1 (active)
language-toml, v0.18.1 (active)
language-xml, v0.34.12 (active)
language-yaml, v0.27.1 (active)

# Dev
No dev packages

I can reproduce this with the steps @tjgerot posted.

Can not reproduce it when trying on my home computer Windows 10 anniversary 64bit. So here is a retelling of what I did to reproduce this with the referenced file on my work computer.
Windows 7 64-bit, classic mode.

Atom 1.13.0-beta1 running in developer mode. I have one-dark-ui linked.
Opened a new window and pasted the contents of this file
Saved the file on the desktop in a folder named issues. The filename was README.md
Everything worked fine, no issues at all
Closed the README.md file tab and reopened it with Ctrl-Shift-T
Issue appeared in console
Since this was out safe mode and in dev mode I closed all instances of Atom and launched in safe mode
Issue appeared. NOTE: The file was restored from previous session.

I can make further attempts to try and narrow this down on Monday. Right now I am unable to reproduce this.
/cc: @ungb

@Ben3eeE I can also reproduce with the file that @tjgerot provided and have made it so that I can reproduce it every time on open.
Using the system mentioned in the first post on this issue I can replicate it by:

Opening Atom 1.13.0-beta1 in safe mode.
Copy the contents of this file into the empty window and saving it somewhere.

This is then where it seems to become very specific!

Move place the cursor at position 8:244 (see screenshot attached).
Quit Atom
Re-open Atom in safe mode and error is thrown.

It seems that if you have the cursor anywhere else in the file then it places the cursor back at position 1:1 on opening the file again, but leaving it at position 8:244 (and maybe others), throws the error upon re-opening.
Hope that helps!

Sorry about this everyone. We'll release another beta hotfix shortly.


Fpet 1046

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)
[ ] the enable_keep_helm label has been added, if the helm release should be persisted after a successful build

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Closing the PR as it will change bring in unnecessary changes after resolving the conflict


Get Chats API taking 7-12 seconds time

Hi,
We are using the below API to get chats of a user
https://graph.microsoft.com/v1.0/me/chats?$expand=members
It is taking anywhere between 7-12 seconds to give a response. Upon hitting multiple times, it starts to give a response in 4-5 seconds.
We tested from Graph API explorer as well and it took around 5 seconds for fetching 20 chats.

We would like to know the reasons and possible solutions to improve the time taken by the APIs.
FYI we are based in Hyderabad, India, if location makes any impact on the response time.
Thanks,
Simran Sidhu,
Software Engineer,
ServiceNow, India

@kaursimransidhu1 - We tried to run this API. However, we noticed that it gives us response in 2-3 seconds.

Hi Prasad, Yes sometimes it takes around 3 seconds and sometimes it takes 4-5 seconds. And sometimes while hitting the very first time it may take up to 7 seconds. But just for fetching 20 chats it shall take less than a second right, it shall be done in milliseconds. If the API call itself takes 3-5 seconds, then if we build functionality on top of it, imagine the load time.

Ran again, and got time taken 4.5 seconds. I have more than 100 chats in my team's account, in real use cases users may have even more chats. I see you have only 19 chats in your account.

Okay @kaursimransidhu1 - We will check with engineering team if there are any possible solutions to improve the time taken by the APIs.

Hi @kaursimransidhu1 -Could you please provide the client-request-Id and timestamp when you are fetching the request?

Hi @Prasad-MSFT, I am attaching the response headers below -
{     "client-request-id": "7d351716-3218-1349-7701-8d0d5c6ac558",     "content-type": "application/json;odata.metadata=minimal;odata.streaming=true;IEEE754Compatible=false;charset=utf-8",     "request-id": "56083e70-fbc7-4fe8-8eed-6838838075c8" }
I am unable to get the exact timestamp, but I ran this request around 4:54 PM IST on 10th July.
Thanks,
Simran Sidhu

We have shared the above details and got below info from engineering team "It doesn't look like the user calls the service enough because we had to fetch their license status on live request (we hold on to this info for a long time while background refreshing it to avoid hitting the impact on incoming request)."


Error (403) User does not have sufficient permissions for this profile.

Hi,
I keep getting this error message on my dashboard:
Error calling GET https://www.googleapis.com/analytics/v3/data/ga?ids=ga%3A15210611&start-date=30daysAgo&end-date=today&metrics=ga%3Avisits&dimensions=ga%3Adate: (403) User does not have sufficient permissions for this profile.
I did all the steps as described, searched other solutions and anything seems to solve the problem.
What am i missing?
Cheers

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/26215776-error-403-user-does-not-have-sufficient-permissions-for-this-profile?utm_campaign=plugin&utm_content=tracker%2F1282891&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1282891&utm_medium=issues&utm_source=github).

Have you been able to resolve the issue? I'm having it too.

I have heard there may be some replication time involved in the permissions, it should resolve itself within 10-15mins or so I'm guessing?

I'm having it for 4 days now, so...

Turns out, the Account Id (under Admin -> Account -> Account Settings) is not the correct number to use as your Profile Id. You have to use the specific View Id that you want to analyse. These may be the same, but they may also be different, as it is my case.


test cancel job

reguler : https://issues.redhat.com/browse/AAP-24973
smart and constructed: doesn't have inventory -> host -> jobs tab


Differentiate between mouse down and mouse up events to enable drag select of text with the mouse

Is your feature request related to a problem? Please describe.
When you drag select text in a textbox using the mouse and release the mouse button outside of the text box you lose focus of the text box:
https://github.com/pdfme/pdfme/assets/7068515/e2d218fb-efc8-48b3-aaa4-b86ba683ad16
Describe the solution you'd like
Differentiate between mouse down and mouse up events when taking action on select/deselect within the Designer main area, so that a mouse up will not deselect the text box.
Describe alternatives you've considered
Leave unchanged
Additional context
No response

I think this issue is fixed.
can we close this?

The issue is that the schema is deselected if you mouseup outside of the schema (if you accidentally drag-select from inside to outside of the schema).
It's a minor issue, but it still exists.


Fails silently on 'edit as project' with MicroFlo

To reproduce:

Install and run Microflo microflo runtime
Open the printed Flowhub live URL
Click 'edit as project'

Expected: Can edit program
Actual:

URL changes, but nothing else seems to happen
console shows Object {id: "MergeContext", error: TypeError: Cannot read property 'type' of undefined at i (http://app.flowhub.io/browser/noflo-ui.m…

I was unable to debug the issue, as the exception is not thrown and catchable in debugger, and the stack logged only refers to the minified source.
On live Flowhub, v0.19.5. MicroFlo 0.3.54

Building locally and replacing the minified include with the proper, I got a usable stacktrace:
TypeError: Cannot read property 'type' of undefined
  at getGraphType (http://localhost:9999/browser/noflo-ui.js:47189:36)
  at Component.<anonymous> (http://localhost:9999/browser/noflo-ui.js:47262:17)
  at task (http://localhost:9999/browser/noflo-ui.js:91228:22)
  at resumeTaskQ (http://localhost:9999/browser/noflo-ui.js:90858:25)
  at InPort.inPort.process (http://localhost:9999/browser/noflo-ui.js:91233:13)
  at InPort.handleSocketEvent (http://localhost:9999/browser/noflo-ui.js:29932:16)
  at InternalSocket.<anonymous> (http://localhost:9999/browser/noflo-ui.js:29860:24)
  at InternalSocket.EventEmitter.emit (http://localhost:9999/browser/noflo-ui.js:2457:20)
  at InternalSocket.debugEmitEvent (http://localhost:9999/browser/noflo-ui.js:14050:21)
  at InternalSocket.handleSocketEvent (http://localhost:9999/browser/noflo-ui.js:14232:19)
  at InternalSocket.send (http://localhost:9999/browser/noflo-ui.js:14095:19)
  at http://localhost:9999/browser/noflo-ui.js:30122:23
  at Array.forEach (native)
  at OutPort.send (http://localhost:9999/browser/noflo-ui.js:30118:22)
  at InPort.<anonymous> (http://localhost:9999/browser/noflo-ui.js:51795:35)
  at InPort.EventEmitter.emit (http://localhost:9999/browser/noflo-ui.js:2442:17)
  at InPort.handleSocketEvent (http://localhost:9999/browser/noflo-ui.js:29938:19)
  at InternalSocket.<anonymous> (http://localhost:9999/browser/noflo-ui.js:29860:24)
  at InternalSocket.EventEmitter.emit (http://localhost:9999/browser/noflo-ui.js:2457:20)
  at InternalSocket.debugEmitEvent (http://localhost:9999/browser/noflo-ui.js:14050:21)
  at InternalSocket.handleSocketEvent (http://localhost:9999/browser/noflo-ui.js:14232:19)
  at InternalSocket.send (http://localhost:9999/browser/noflo-ui.js:14095:19)
  at http://localhost:9999/browser/noflo-ui.js:30122:23
  at Array.forEach (native)
  at OutPort.send (http://localhost:9999/browser/noflo-ui.js:30118:22)
  at Component.<anonymous> (http://localhost:9999/browser/noflo-ui.js:48491:20)
  at task (http://localhost:9999/browser/noflo-ui.js:91228:22)
  at resumeTaskQ (http://localhost:9999/browser/noflo-ui.js:90858:25)
  at InPort.inPort.process (http://localhost:9999/browser/noflo-ui.js:90899:16)
  at InPort.handleSocketEvent (http://localhost:9999/browser/noflo-ui.js:29932:16)
  at InternalSocket.<anonymous> (http://localhost:9999/browser/noflo-ui.js:29860:24)
  at InternalSocket.EventEmitter.emit (http://localhost:9999/browser/noflo-ui.js:2457:20)
  at InternalSocket.debugEmitEvent (http://localhost:9999/browser/noflo-ui.js:14050:21)
  at InternalSocket.handleSocketEvent (http://localhost:9999/browser/noflo-ui.js:14232:19)
  at InternalSocket.send (http://localhost:9999/browser/noflo-ui.js:14095:19)
  at http://localhost:9999/browser/noflo-ui.js:30122:23
  at Array.forEach (native)
  at OutPort.send (http://localhost:9999/browser/noflo-ui.js:30118:22)
  at InPort.process (http://localhost:9999/browser/noflo-ui.js:47405:27)
  at InPort.handleSocketEvent (http://localhost:9999/browser/noflo-ui.js:29932:16)
  at InternalSocket.<anonymous> (http://localhost:9999/browser/noflo-ui.js:29860:24)
  at InternalSocket.EventEmitter.emit (http://localhost:9999/browser/noflo-ui.js:2457:20)
  at InternalSocket.debugEmitEvent (http://localhost:9999/browser/noflo-ui.js:14050:21)
  at InternalSocket.handleSocketEvent (http://localhost:9999/browser/noflo-ui.js:14232:19)
  at InternalSocket.send (http://localhost:9999/browser/noflo-ui.js:14095:19)
  at InternalSocket.<anonymous> (http://localhost:9999/browser/noflo-ui.js:18768:25)
  at InternalSocket.g (http://localhost:9999/browser/noflo-ui.js:2526:16)
  at InternalSocket.EventEmitter.emit (http://localhost:9999/browser/noflo-ui.js:2457:20)
  at InternalSocket.debugEmitEvent (http://localhost:9999/browser/noflo-ui.js:14050:21)
  at InternalSocket.handleSocketEvent (http://localhost:9999/browser/noflo-ui.js:14232:19)
  at InternalSocket.connect (http://localhost:9999/browser/noflo-ui.js:14080:19)
  at http://localhost:9999/browser/noflo-ui.js:18770:23
  at Array.forEach (native)
  at Port.send (http://localhost:9999/browser/noflo-ui.js:18763:27)
  at IDBTransaction.<anonymous> (http://localhost:9999/browser/noflo-ui.js:52848:35)

Graph does not have .properties.environment

Seemingly this only happens if the runtime connection does not have a main graph (returned by getruntime). Since this is optional in the protocol, should also handle this case.


When will the 5.1  release approximately？

I can‘t wait for it   :P

Hi,
Now I'm working to release the most important components:

Sparse font support
Faster anti aliasing

Your question came in  the right time: hopefully I will push these new updates on this weekend or next Monday.
I will open an issue to inform you and ask to test it.
What feature are the most important to you?

@kisvegabor  Hi！Thanks for your working!  the anti aliasing for the Sparse font is important to me.

It was faster then I thought :)
Check:  #125

As v5.1 is released I close this issue.


CRD error in diff and failed webhook calling

Operating system
Linux Mint 21
Kluctl Version
2.21.0
Kubernetes Version
v1.24.0
kubectl Version
v1.25.3
Bug description

CRD references are failing in diff even though should be fixed by https://github.com/kluctl/kluctl/pull/438 ?
Failing to call webhook as (sometimes) the webhook is not ready I assume

Its unclear how I could create a reliable barrier.
Steps to reproduce
*** metallb folder ***
==> helm-chart.yaml <==
helmChart:
  repo: https://metallb.github.io/metallb
  chartName: metallb
  chartVersion: 0.13.9
  releaseName: metallb
  namespace: "metallb-system"
  skipPrePull: true

==> kustomization.yaml <==
resources:
  - namespace.yaml
  - helm-rendered.yaml

==> namespace.yaml <==
apiVersion: v1
kind: Namespace
metadata:
  name: metallb-system

*** metallb-config folder ***
==> metallb_config.yaml <==
apiVersion: metallb.io/v1beta1
kind: IPAddressPool
metadata:
  name: kind-pool
  namespace: metallb-system
spec:
  addresses:
  - <IP_ADDRESS>-<IP_ADDRESS>
---
apiVersion: metallb.io/v1beta1
kind: L2Advertisement
metadata:
  name: advertisement
  namespace: metallb-system

*** top level folder ***
==> deployment.yaml <==
deployments:
  - path: metallb
    waitReadiness: true
  - barrier: true
    message: "Waiting for metallb install to be finished"
  - path: metallb-config

Relevant log output
kluctl deploy -t local
✓ Loading kluctl project
✓ Initializing k8s client
✓ Rendering templates
✓ Pulling Helm Chart metallb with version 0.13.9
✓ Rendering Helm Charts
✓ Building kustomize objects
✓ Postprocessing objects
✓ Writing rendered objects
✓ Getting remote objects by discriminator
✓ Getting 25 additional remote objects
✓ Getting namespaces
✓ metallb: Applied 23 objects.
✓ Finished waiting
✗ metallb-config: Encountered 2 errors.
✓ Running server-side apply for all objects

New objects:
  Namespace/metallb-system
  metallb-system/Secret/webhook-server-cert
  metallb-system/Service/metallb-webhook-service
  metallb-system/ServiceAccount/metallb-controller
  metallb-system/ServiceAccount/metallb-speaker
  ValidatingWebhookConfiguration/metallb-webhook-configuration
  CustomResourceDefinition/bfdprofiles.metallb.io
  CustomResourceDefinition/bgppeers.metallb.io
  CustomResourceDefinition/addresspools.metallb.io
  CustomResourceDefinition/communities.metallb.io
  CustomResourceDefinition/l2advertisements.metallb.io
  CustomResourceDefinition/ipaddresspools.metallb.io
  CustomResourceDefinition/bgpadvertisements.metallb.io
  metallb-system/DaemonSet/metallb-speaker
  metallb-system/Deployment/metallb-controller
  ClusterRole/metallb:speaker
  ClusterRole/metallb:controller
  ClusterRoleBinding/metallb:controller
  ClusterRoleBinding/metallb:speaker
  metallb-system/Role/metallb-pod-lister
  metallb-system/Role/metallb-controller
  metallb-system/RoleBinding/metallb-pod-lister
  metallb-system/RoleBinding/metallb-controller

Errors:
  default/IPAddressPool/kind-pool-9klvpssd: failed to patch default/IPAddressPool/kind-pool-9klvpssd: the server could not find the requested resource (patch ipaddresspools.metallb.io kind-pool-9klvpssd)
  default/L2Advertisement/advertisement-cqxrlhzg: failed to patch default/L2Advertisement/advertisement-cqxrlhzg: the server could not find the requested resource (patch l2advertisements.metallb.io advertisement-cqxrlhzg)
✓ The diff resulted in errors, do you still want to proceed? (y/N) y
✓ metallb: Applied 23 objects.
✓ Finished waiting
✗ metallb-config: Applied 1 objects. Encountered 1 errors.
✓ Running server-side apply for all objects
ⓘ Deleted old command result cc5740b4-0381-49c7-b48c-f5c69e16ebde
⠹ Writing command result

New objects:
  Namespace/metallb-system
  metallb-system/Secret/webhook-server-cert
  metallb-system/Service/metallb-webhook-service
  metallb-system/ServiceAccount/metallb-speaker
  metallb-system/ServiceAccount/metallb-controller
  ValidatingWebhookConfiguration/metallb-webhook-configuration
  CustomResourceDefinition/l2advertisements.metallb.io
  CustomResourceDefinition/bgpadvertisements.metallb.io
  CustomResourceDefinition/ipaddresspools.metallb.io
  CustomResourceDefinition/bfdprofiles.metallb.io
  CustomResourceDefinition/communities.metallb.io
  CustomResourceDefinition/bgppeers.metallb.io
  CustomResourceDefinition/addresspools.metallb.io
  metallb-system/DaemonSet/metallb-speaker
  metallb-system/Deployment/metallb-controller
  metallb-system/L2Advertisement/advertisement
  ClusterRole/metallb:controller
  ClusterRole/metallb:speaker
  ClusterRoleBinding/metallb:controller
  ClusterRoleBinding/metallb:speaker
  metallb-system/Role/metallb-pod-lister
  metallb-system/Role/metallb-controller
  metallb-system/RoleBinding/metallb-pod-lister
  metallb-system/RoleBinding/metallb-controller

Errors:
  metallb-system/IPAddressPool/kind-pool: failed to patch metallb-system/IPAddressPool/kind-pool: Internal error occurred: failed calling webhook "ipaddresspoolvalidationwebhook.metallb.io": failed to call webhook: Post "https://metallb-webhook-service.metallb-s✓ Writing command result
✗ command failed
✗ command failed

Can you reproduce this 100%? For some reason, I'm completely unable to reproduce it. What k8s version and what type of cluster are you using?

@cliveseldon fyi, I believe that I know how to fix this. The issue seems to be that the K8s API is reporting different errors in different situations. I'd however really like to understand the internals first as I'm afraid that I might have missed something that could cause other issues as well.
It might be helpful for me if you run the deploy with --debug and post the result here.

I can try.I have "solved" the webhook issue by moving the metallb config to much later so there is more of a chance the webhook is running ok. This is not ideal but I suppose a lot of the issue I am seeing is to needing to wait for dependent resources to be fully ready.

Regarding the webhook: The waitReadiness that you're using should actually fix this already. I will later check if there is a bug, but I actually assume that metallb is reporting readiness too early, which some controllers/operators unfortunately do...
A more reliable fix would be to a hook that waits until the webhook endpoint is actually responding properly, but this is very specific to the controller/operator that you need wait for.
Long-term, I plan to add more flexible means of "waiting for readiness", meaning that I'll add ways to use Jinja2 expressions that would perform various checks.

That makes sense on the webhook issue.

@cliveseldon Do you still see the 1. bug from time to time?
I'm still unable to reproduce this. I will however now start to work on a reliable solution for the 2. issue, meaning that you'll be able to wait for proper readiness, including webhook readiness.

I haven't seen one but this maybe due to my changes to get around it. A solution to 2 would be great.

I finally found the issue behind the error in 1.
It was caused by outdated on-disk discovery caches. The k8s client used by Kluctl assumed that the API resource behind the CRD still existed, even though it was deleted after it was initially discovered (I assume you did kluctl delete or some other way to get rid of CRDs).
#941 has a fix for this. That same PR also implements waitReadinessObjects which can be used to wait for specific objects to become ready (e.g. the metallb controller so that webhooks are ready as well).


Testrtc linechart

This is quite experimental.. but I think it would beneficial to submit and improve over it instead of being rotting in my pull requests.
For now this plot is only used in WiFi periodic test which is an explicit test so it should not ruin any other user experience.

Consider renaming the test to something like "Network latency analyzer"

Also consider adding a timeout with an error for the test if the network connection is disconnected suddenly.

Renaming and timeout on test for users who get disconnected is left for another CL.

LGTM


[DEFECT] Cannot Sample Multiple RELAP5 Variables on the Same Line

Defect Description
I created a RAVEN sample that would perform the same sampling for multiple variables on a single RELAP5 line and it did not perform the correct sampling and caused the calculation to abort.
RAVEN xml input line of interest:

RELAP5 input line of interest:
7290102 0.0  0.0          1000
What did you expect to see happen?
I expected RAVEN to sample the first and second RELAP5 variables consistently on the line of interest.
What did you see instead?
The code aborted with a non-descriptive error message.
Do you have a suggested fix for the development team?
Traceback (most recent call last):
File "/home/cgosdin/RAVEN_FPS/RAVEN_FPS/framework/Driver.py", line 285, in
raven()
File "/home/cgosdin/RAVEN_FPS/RAVEN_FPS/framework/Driver.py", line 238, in raven
simulation.run()
File "/home/cgosdin/RAVEN_FPS/RAVEN_FPS/framework/Simulation.py", line 780, in run
stepInstance.takeAstep(stepInputDict)
File "/home/cgosdin/RAVEN_FPS/RAVEN_FPS/framework/Steps.py", line 315, in takeAstep
self._localTakeAstepRun(inDictionary)
File "/home/cgosdin/RAVEN_FPS/RAVEN_FPS/framework/Steps.py", line 640, in _localTakeAstepRun
myLambda([finishedJob,outputs[outIndex]])
File "/home/cgosdin/RAVEN_FPS/RAVEN_FPS/framework/Steps.py", line 588, in
self._outputCollectionLambda.append( (lambda x: inDictionary['Model'].collectOutput(x[0],x[1]), outIndex) )
File "/home/cgosdin/RAVEN_FPS/RAVEN_FPS/framework/Models/Code.py", line 738, in collectOutput
self.raiseAnError(AttributeError,"No available Output to collect")
File "/home/cgosdin/RAVEN_FPS/RAVEN_FPS/framework/MessageHandler.py", line 99, in raiseAnError
self.messageHandler.error(self,etype,msg,str(tag),verbosity,color)
File "/home/cgosdin/RAVEN_FPS/RAVEN_FPS/framework/MessageHandler.py", line 313, in error
raise etype(message)
AttributeError: No available Output to collect
Describe how to Reproduce
Steps to reproduce the behavior:

Unzip file
Rerun Raven

Screenshots and Input Files
Attached a zip file of the directory where the calculation was executed.
Multiple_Variables_Same_Line.zip
Platform (please complete the following information):
LSB Version:    n/a
Distributor ID: SUSE
Description:    SUSE Linux Enterprise Server 12 SP4
Release:        12.4
Codename:       n/a

Dependencies Installation: CONDA

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?

Impact to users is only a crash, so no notification required.
Approved to close via #1118


fix(llms/marshaling): toolCall can not unmarshal

The function parameter becomes map[string]any when unmarshal is applied.
PR Checklist

[x] Read the Contributing documentation.
[x] Read the Code of conduct documentation.
[x] Name your Pull Request title clearly, concisely, and prefixed with the name of the primarily affected package you changed according to Good commit messages (such as memory: add interfaces for X, Y or util: add whizzbang helpers).
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. Fixes #123).
[x] Describes the source of new concepts.
[x] References existing implementations as appropriate.
[x] Contains test coverage for new functions.
[x] Passes all golangci-lint checks.

@tmc @eliben please review this MR!


autocomplete when cursor not at end of word causes incorrect completetion

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

Version: 1.71.0 (Universal)
Commit: 784b0177c56c607789f9638da7b6bf3230d47a8c
Date: 2022-09-01T07:25:38.437Z (2 wks ago)
Electron: 19.0.12
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 20.6.0
Sandboxed: No
Steps to Reproduce:

Start typing something you know can be autocompleted
If autocomplete popup opens automatically close it by hitting esc
Open autocomplete (for me that's ctrl + space)
Left arrow a couple of characters so the cursor is not at the end of the word
Choose one of the autocomplete suggestions

Expected: Entire word is replaced with selected suggestion
Actual: Characters left of the cursor are replaced and the right side is kept - the result is incorrect
e.g. fo|o -> fooBaro instead of fooBar
(The pipe above indicates the cursor position when using autocomplete)

This may not be a bug (perhaps some people desire this behaviour?) but because it results in some incorrect code (and it's a bit annoying) I decided to raise a bug. I can reproduce it consistently but in real world use it happens infrequently.
Thanks for your help!

Suggest usually supports insert and replace mode. The default be configured with editor.suggest.insertMode and the "alternative" variant is available via Shift+Tab, so Tab does insert and Shift+Tab does replace

@jrieken thanks - that works great, didn't know that existed!


Why is the siwe 1.1.6 the latest on npm but siwe v2 has been released months ago?

Links:
https://www.npmjs.com/package/siwe
https://github.com/spruceid/siwe/releases

Links: https://www.npmjs.com/package/siwe https://github.com/spruceid/siwe/releases

This is because we've tagged the v2 versions as beta. We plan on merging some changes coming down the pipeline for a v3 version in the future with a sufficient sunset period for previous versions.


Dowload data

In my role as...
a student.
I need to be able to...
Download the data from the climate indexes in various formats, such as an excel format.
in order to...
Do a basic analysis.

Supporting various output formats


Description of MODS elements in sip-spec incomplete

Fixed in https://github.com/KBNLresearch/omSipCreator/commit/01912eca4942a3255dce81601fe09ecd81d99a42


chore: Reporting Code Coverage to Codecov

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Add Item Modifiers support

This pull request adds Item Modifiers support

Oh, just a question: why did you remove Score as a valid NumberProvider? It works perfectly fine

It messed up the auto-completion since Score's properties are also suggested

Great news: the bug I reported got noticed, & someone wrote a PR: https://github.com/microsoft/TypeScript/pull/45044


Added functionality to report message flow statistics to AppDynamics

- Added functionality to process message flow statistics
- Adjusted README and unit tests accordingly
- Changed package structure to differentiate between resource and flow statistics
- Removed IBM libs from repository
- Adjusted POM to reflect the specific libraries for MQ8 / MQ7.5

Thanks for the contribution. I made changes to the code based on your contributions. Let me know if you see any bugs.


Searching for other value types than strings

First of all: I really like this package, it helps a lot to implement search functionality.
Today, I tried to set-up a search that uses an array of strings instead of a plain string as an input parameter. This did not work. Instead, I got the following error message:
I20151106-13:55:32.616(1)? Exception while invoking method 'search.source' Error: Match error: Failed Match.OneOf or Match.Optional validation
I20151106-13:55:32.616(1)?     at checkSubtree (packages/check/match.js:244:1)
I20151106-13:55:32.616(1)?     at check (packages/check/match.js:32:1)
I20151106-13:55:32.617(1)?     at [object Object].Meteor.methods.search.source (packages/meteorhacks:search-source/lib/server.js:12:1)
I20151106-13:55:32.617(1)?     at [object Object].methodMap.(anonymous function) (packages/meteorhacks:kadira/lib/hijack/wrap_session.js:164:1)
I20151106-13:55:32.617(1)?     at packages/check/match.js:109:1
I20151106-13:55:32.617(1)?     at [object Object]._.extend.withValue (packages/meteor/dynamics_nodejs.js:56:1)
I20151106-13:55:32.617(1)?     at Object.Match._failIfArgumentsAreNotAllChecked (packages/check/match.js:108:1)
I20151106-13:55:32.617(1)?     at maybeAuditArgumentChecks (packages/ddp/livedata_server.js:1614:1)
I20151106-13:55:32.617(1)?     at packages/ddp/livedata_server.js:648:1
I20151106-13:55:32.617(1)?     at [object Object]._.extend.withValue (packages/meteor/dynamics_nodejs.js:56:1)
I20151106-13:55:32.617(1)? Sanitized and reported to the client as: Match failed [400]
I20151106-13:55:32.617(1)?

Is there any particular reason why the input parameter is limited to a string? I will now concat the array using a delimiter character as a work-around, but it would be nicer if I could send arrays or plain objects directly.

I've just made a custom version for myself that accepts an object.  Besides adding "Object" to the check function arguments in the search.source Meteor call, I had to make several surgical changes to the client code to get it all to work.  For instance:

to continue to accept simple strings added some argument checking which falls back to the existing code
allowed optionally specifying a key to use to highlight the search results (as it currently does for the simple string)
added a callback to build the mongo selector on the client (my case included a date range plus a string)
modified the search history key based on the search object contents
other

Separate but related those modifications was an issue of duplicate Mongo-selector-building code on the server and client.  Let me see if I can explain.
The existing SearchSource code requires the user to define her own server-side Mongo selector but, oddly, I thought, it builds the client-side selector (an $or) in its own code (see getData in client.js).  Having added an optional callback for the client selector (see item 3, above), I tried get SearchSource itself to share a Mongo-selector-building function between the client and server.
After some struggle and breakpointing I was enlightened to the fact that there's no simple way to pass a function between client and server via, say, the existing SearchSource ‘option’ argument.  So, I decided to share a mongo-selector-building function externally from SearchSource: a shared function available to the client and server callbacks.  Less modular but fine for now.
It works well.  At present, I have as search criteria only a date range and a string, but there’s no limit on the complexity of search allowed by this architecture.  That’s satisfying.
I hope this little note encourages you.

Thanks a lot for these insights!


Update 1.92 pointerlist

1.94
https://community.bistudio.com/wiki/getResolution

count getResolution = 6 on Version: 1.94.145903

will have to add a condition on that then

setBehaviour was broken if you passed a object :D oops, fixed now


VR view is brighter than desktop

It's a bit subtle but there's a distinct difference in lighting between desktop / vr views, with vr being a lot brighter..

Best guess is something funny with the colour normalisation - srgb vs linear.
Would try submitting linear rgb to openxr, but at least on steamvr only srgb is supported for 8-bit swapchain images, despite the spec saying both srgb and linear should be supported by runtimes..


On node v0.12 util.puts gives warnings

Everytime I run protractor I get these warnings:
util.puts: Use console.log instead
util.puts is deprecated according to node.js docs https://nodejs.org/api/util.html#util_util_puts

@juliemr I've been wondering about this too

Yes - but we should have already done that, so I'm confused. The only instance of util.puts that I see is in our test application.

I've been wondering about that part too tbh

That is, I've been wondering why I see the warning given that we don't seem to use util.puts

@sjelin @bobbijvoet What specific version of node are you running? I haven't been able to replicate with 0.12.0 or 0.12.4 and protractor 2.1.0. This is very curious :)

Closing this issue, as I don't see these warnings and we do not use util.puts. Please open a new issue with how to reproduce if there is still a problem.


localisation issue in units.py

In locations where decimal separator is a ',' kicad crashes with the message.
"in wxWidges with the comment setlocale called directly not using wxlocale.
now there is a mismatch between C/C== and Windows locale"
this can be fixed by commenting line 17 in units.py
#locale.setlocale(locale.LC_NUMERIC, '')
Benno

Can you post a screenshot of the message? Also add kicad version information and windows version.

Error message and kicad version below.

Updated to 5.1.4 it is working now


XML comments removed / not rendered on NuGet.org

See https://www.nuget.org/packages/IceRpc.Slice.Tools#readme-body-tab
There are a few XML code blocks with blank lines. In the actual README.md, these are XML comments.

Should we just remove the comments?

The comments are helpful and it would be better to render them.

I think we have to XML escape them

XML escaping doesn't work here, tried a few things but I cannot get XML comments to render with NuGet READMEs.
I think the only option is to move this text out of the xml code block.


[DS-3749] Selective enabling of identifier generation per-container

A version for DSpace 5.6 has been lightly tested and was recently placed in service locally.
This still needs a user interface for convenient configuration, hence Work-In-Progress.  (For local reasons we had to build a separate GUI for our use.)

The default metadata for collections is only partially related to this feature or am I missing something?
I would prefer a single metadata field with multiple values containing the disabled identifiers, instead of a single metadata field for each identifier with a value of "true" (but this might be my personal taste). It may even be more logically if the field would be a white-list containing the enabled identifiers.

Please rebase this PR against the latest master branch.  The master branch now requires adherence to our new Java Code Style documented at: https://wiki.duraspace.org/display/DSPACE/Code+Style+Guide
If you have any questions, feel free to ask in this PR or on our Slack: https://wiki.duraspace.org/display/DSPACE/Slack


Stop jdk19u builds and archive jobs

Now jdk-19.0.2 is complete, no more builds are required, as jdk-20 supercedes.
We should disable jdk-19 nightlies and archive the jobs.

The nightly-publishing checker and corresponding slack notification job needs updates as well to move it to check JDK 20 over 19.

https://github.com/adoptium/ci-jenkins-pipelines/pull/628

The CI pipeline repo has been updated here and here to remove jdk19u and to substitute jdk20 in its place.
Scott Fryer has agreed that this should be included in the release checklist, and has volunteered to make the relevant changes.
Next task: Figure out how to archive the jobs in a way that prevents them from being recreated the next time the jobs are refreshed.

Andrew has laid out the process, and has kindly volunteered to handle the final stage of this issue as I seem to lack the admin permissions needed to delete jobs.

The relevant jobs have been archived. I should also notify @steelhead31 that the changes to the source code required to fully retire a build in ci-jenkins-pipeline also seems to disable the thing that updates that pipeline automatically. Including the part of the update that disables the nightly build schedule for that JDK version.
So, to fully retire a pipeline, you also need to manually disable the pipeline job. Plus any other JDK-related Job disabling/deleting that may be needed.


New release

Hi,
@subchen When will you release the Parameter Store feature?
regards

sure

1.3.11 released


A/B Landing Page

Landing page template: https://8-aaeffee09b-7w6v22.manager.zesty.io/content/6-beb393cb89-4dl2n5/7-facfcbf68b-zpl8tj
Variations: https://8-aaeffee09b-7w6v22.manager.zesty.io/content/6-aa81a983e2-k9mzjm
Doc outline: https://docs.google.com/document/d/1AG7LA345wWDG-yOeqX6UAyAuGpZuGcU2dEQaOSl9rDI/edit?usp=sharing
Please create a landing page with the following components:
Header
From: https://www.zesty.io/ppc/content-management-system/

Make secondary button like the homepage secondary button

Logo bar from homepage with H2

H2 from homepage

Benefits section from homepage

Middle CTA from homepage

Features
From: https://www.zesty.io/ppc/content-management-system/

Testimonial
From: ./src/blocks/team/WithCompanyLogo/WithCompanyLogo.js|ts

Don't need logo

Final CTA

deployed on stage  -> https://kfg6bckb-dev.webengine.zesty.io/discover


Update latest source on npm

ping @esbullington
I think we should do this now since many get confused =(

done in #256