Update .NET SDK to fix metric description

The .NET SDK had a bug with a schema defined metric description being incorrect. When this PR is released, we need to update the cartservice SDK dependencies and revert #738 which added a transform processor to the collector to temporarily prevent an  error condition.

duplicated: https://github.com/open-telemetry/opentelemetry-demo/issues/737


Text widget annotations: implement maximum length and text alignment

Moreover, we refactor the code a bit to extract code that is shared between the two branches and we only apply text alignment (and create the array) when it is actually defined, since it's optional and left is already the default.
@Snuffleupagus Could you review this PR? This patch is a part of #7613 and improves the support for text widget annotations. You can test this by opening the f1040.pdf file and noticing that you can now only enter two characters into the top right input box (with 20 before it) and that most fields in the "Income" section and now right-aligned.

This seems fine, thank you!
It would be great to have tests for this feature, but I realize that it might not be too easy to add tests at this stage and I'm not sure if a unit-test would bring much (in any) value here!?
(Once we've got more complete support for forms, it might make sense to add a modified f1040 file with the various form elements already filled in (e.g. via fieldValue) in the PDF file itself, since I'm assuming that this would give us the opportunity to check that e.g. things like justification/text colour/text style/etc. works as intended.)
r=me, with passing tests and with the CONSTANTcomment addressed.

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

src/display/annotation_layer.js, line 461 at r1 (raw file):

        var font = null;
        if (this.data.fontRefName) {

Just something I noticed in passing:
Since this is existing code you don't need to worry about it in this PR, but it doesn't appear that there's currently any code in core/annotation.js that actually sets this fontRefName property.
This could perhaps be something worth to look into in a future PR, since there's also a TODO comment in the _setTextStyle method, and it doesn't seem that we currently even try to load/use the correct font information here in display/annotation_layer.js.

src/display/annotation_layer.js, line 468 at r1 (raw file):

      if (this.data.textAlignment) {
        var alignments = ['left', 'center', 'right'];

Would it make sense to make this a constant instead, e.g. TEXT_ALIGNMENT or similar, and define it outside of the render method?

Comments from Reviewable

The comment has been addressed and I followed the specification better by making sure that the values we use for maximum length and text alignment are integers (as other values would not work). This is trivial and there probably are not such broken PDFs, but let's be safe nevertheless.
In the meta issue, I'll add a note once this lands about the (probably dead) font code and about sanitizing the values for maximum length/text alignment in the core layer (so that this display layer code is only getting either null, which doesn't pass isInt, or a valid integer), and adding unit tests for that.

/botio-linux preview

/botio test


perf(todo): Merge hot updates of uno.css to reduce the number of updates

Clear and concise description of the problem
Every time the file magicString is updated, it will trigger a hot update of uno.css. Is it possible to find a way to merge this update, or add a delay or cancellation strategy, and only update it once for the last time?
Suggested solution
To be explored
Alternative
No response
Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the README.md of using the package.
[X] Already used the Interactive Docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

We already doing a bit of throttling for sending the events. If too long it would make it feel slower to response to user changes. Do you have some case specifically to improve?

#3741


Fix Bug in GC Reallocation Calculation

Updates the way we calculate thenext GC to make sure that we're not
already past the threshold. This was causing endless garbage collections
on 32 bit builds in test/language/deeply_nested_gc.wren.
This bug is partly responsible for 32 bit build failures on #391

Awesome!


effects don't seem to take place until an event triggers

To clarify what I mean,
When I cat $X11FS/event to watch events stream in, if I try to interrupt the stream by passing SIGINT through ^C, the stream does not stop until another event happens.
Similarly, when I increase the border-width of a window (this is under dwm), the width effect does not take place until the window actually goes out of sight (e.g., by switching views or removing the window from the current tags) and is brought back.
Ideally, all effects should be immediate.

I am aware of the issue with catting $X11FS/event, and am not sure I can fix it. When cat calls read it blocks in get_events() (which in calls xcb_wait_for_event() which blocks.) While cat is blocked on this read call it will not respond to SIGINIT, and I don't see much of a way round this. The window border problem sounds like dwm may be in some way conflicting with x11fs setting the border width. (If I understand the problem correctly, when you echo a number into $X11FS/<winid>/border/width the width doesn't change). Whilst I am planning to make x11fs work alongside window managers, it currently only works with 100% functionality when running standalone. Unfortunately making it work with every window manager will be nigh on impossible, due to the mess of standards that X window managers follow/don't follow. My current plan is to make a version of x11fs (or add a command line flag), to allow it to communicate with window managers following the ewmh standard. However there will still be incompatibilities with window managers such as DWM which don't implement ewmh.

Ahh, so then these are two separate issues. Good to know.
Disregard the border issue; I do not expect x11fs to ever function completely correctly under reparenting WMs. As for the first, you could register your own signal handler for SIGINT to fail out, but I am not convinced that is a good idea, so this may not be fixable.


[FLINK-12513][e2e] Improve end-to-end (bash based) tests

What is the purpose of the change
Make bash based end-to-end tests more "isolated" from each other (by more thorough clean up).
Brief change log

whole Flink lib and conf sub directories are backuped and restored on each test run by test-runner-common.sh. Tests themselves don't need to revert their changes for this dirs anymore.
introduced an on_exit hook as alternative to built-in trap hook. The letter is discouraged to be used directly in tests.
refactored Flink config key delete and setter methods.

Verifying this change

Would be nice to run this changes in CI environment and see if there are any test failures.
Some new methods and their behavior was tested manually by running a sample test:

#!/usr/bin/env bash

source "$(dirname "$0")"/common.sh

# Check on_exit hook
function foo {
    echo "Debug 1"
    ls -la "$FLINK_DIR/lib/"
}

function foo_2 {
    echo "Debug 2"
    ls -la "$FLINK_DIR/lib/"
}

on_exit foo
on_exit foo_2

# Check add_optional_lib

add_optional_lib "table"
add_optional_lib "s3-fs-presto"

ls -lh "$FLINK_DIR/lib"

# Check config_key methods

set_config_key "jobmanager.archive.fs.dir" "hdfs:///sdsds-jobs/"
set_config_key parallelism.default 42
delete_config_key high-availability
delete_config_key jobmanager.rpc.address
cp ${FLINK_DIR}/conf/flink-conf.yaml ${FLINK_DIR}/conf/flink-conf.test.yaml

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Would be nice to run this changes in CI environment and see if there are any test failures.

That message is a little bit outdated. Since then, I have already experimented a little bit with CI runs.

Or do you think that risk of something failing is small enough (basing on passing pre-commit tests) that it's better to commit it as it is and just observe next nightly build?

I lean towards this 😎🤞.

Ok :) Merging


[bug] HTMLAudioInstance.ts

Bug Description:
There is a potential writing error in sound/src/htmlaudio/HTMLAudioInstance.ts on line 341.
The code snippet this.emit('progress', start, this._duration); should have 'start' modified to 'start/this._duration'.
Steps to Reproduce:
Navigate to the sound/src/htmlaudio/HTMLAudioInstance.ts file.
Go to line 341.
Note the mentioned code snippet.
Expected Behavior:
Modify the code to change this.emit('progress', start, this._duration); with start/this._duration to ensure correct behavior.
Thank you for bringing this to attention, looking forward to the resolution of the issue!

Same here.

Released in v6.0.1


Visual shader editor node preview shader compilation fails with instance uniforms

Godot version
4.0b17
System information
macOS 13.2
Issue description
If you make a visual spatial shader and that uses an instance uniform and you have some nodes with previews (the little graphic view) for example like this:

You will get a strange error in the output whenever you load the shader like this:
--Main Shader--
    1 | shader_type canvas_item;
    2 |
E   3-> instance uniform float InstanceParameter : hint_range(0, 1) = 1;
    4 |
    5 |
    6 |
    7 | void fragment() {
    8 |
    9 |  float n_out21p0 = InstanceParameter;
   10 |
   11 |
   12 |
   13 |  float n_out14p0 = 1.0 - n_out21p0;
   14 |
   15 |
   16 |  COLOR.rgb = vec3(n_out14p0);
   17 | }
   18 |
  :3 - Uniform instances are not yet implemented for 'canvas_item' shaders.
  Shader compilation failed.
  ./servers/rendering/renderer_rd/shader_rd.h:140 - Condition "!version" is true. Returning: RID()

After a lot of experimenting the reason for this seems to be that the visual shader editor is actually also generating canvas_item shaders to render the little node previews (an elegant solution!). And for this shader code it's using the uniforms the nodes are connected to. However, this doesn't seem to account for the fact that we now have instance uniforms that are supported in spatial visual shaders, but not in canvas_item shaders. So it's failing to compile the shaders for the previews and outputs this error in the process. The failures have probably been happening since instance uniforms were added, but the error reporting has been added more recently so I started seeing these in one of the later beta versions.
This doesn't seem to affect the generated shader performance, but it's outputting some confusing errors (took me a good while to figure out) and the previews for the nodes just show all white so you could say it affects the usability of the shader editor.
Steps to reproduce

Create a spatial visual shader
Add an input parameter and set the qualifier to be "Instance"
Link the parameter value to some node with a preview
Link that node to the output
Observe output for errors
Open/close the file in the editor or open/close the preview on the node to see errors again.

Minimal reproduction project
The shader from the example: VisualShaderInstanceUniform.zip

There is a function that decides whether previews are allowed to be shown. It should be able to detect if an instant uniform is used and then just not allow the preview to be shown.

It should be able to detect if an instant uniform is used and then just not allow the preview to be shown.

Or, in the spirit of my renderer feature support flags proposal it could disable them if instance uniforms are not supported for canvas_item shaders in the current renderer, and define that in the renderer. So that if instance uniforms are supported for canvas_item shaders in the future this functionality will adapt automatically.

It should be able to detect if an instant uniform is used and then just not allow the preview to be shown.

Or, in the spirit of my renderer feature support flags proposal it could disable them if instance uniforms are not supported for canvas_item shaders in the current renderer, and define that in the renderer. So that if instance uniforms are supported for canvas_item shaders in the future this functionality will adapt automatically.

I don't think we should use macros for something like this. At most we should convert the instance uniform into a regular uniform

Looking into this a little, its going to require a decent amount of work. Right now we have a function to check if a given node will show the preview icon; has_output_port_preview() For most nodes it defaults to true, and then a few nodes override it and set it to return false.
The trouble is, this check isn't recursive. So If I have something like an instance uniform, or a depth texture node, the next node will still show the preview port, even though it shouldn't.
@Chaosus Should we make has_output_port_preview() cascade to further nodes? For example, if one of a node's inputs has has_output_port_preview() evaluate to false, it would also evaluate to false. Or is there a situation where an input can't be used for previews, but the current node can?

Should we make has_output_port_preview() cascade to further nodes?

I guess we should focus our forces to implement the canvas item instances instead.

Should we make has_output_port_preview() cascade to further nodes?

I guess we should focus our forces to implement the canvas item instances instead.

Well, the problem still presents itself for other things like varyings and depth_texture.

Ah, then yes, recursive check should be added like I already did for recursive connections (https://github.com/godotengine/godot/pull/35362).

I think I could fix it.

At most we should convert the instance uniform into a regular uniform

After thinking some more about this, isn't it the case that within the context of the shader editor previews all uniforms can actually be considered basic shader uniforms (or even constants?) with the uniform default value (or 0 I guess if it doesn't have one)? I'm not sure about varyings but I guess depth_textures could also be just be given a default value in the previews. This would require some substitutions in the shader code generated for the previews, but would have the benefit of being able to show previews, work on all renderers and allows the user to see changes to the previews by changing these default values.
While hiding the previews might be correct if these can't be generated now, it's also quite confusing and bad from a usability point of view. And if that's also a lot of work to achieve cascading correctly I wonder if it's worth the effort?


[CP]: Lowest Common Ancestor in Binary Tree

Description 📜
This is the documentation about lowest common ancestor problem.
Fixes ##7966

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[x] Documentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[x] Competitive Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] JavaScript_#Domain
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@ravireddy07 I have made the changes, please recheck.

Please update the status in PR Tracksheet @areenoverclouds


Just use a slice when rendering file

Highlight currently uses a map which is memory inefficient. Switch to use a slice instead.
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

Codecov Report

Merging #16774 (60c1280) into main (db1e3d0) will decrease coverage by 0.01%.
The diff coverage is 55.55%.

@@            Coverage Diff             @@
##             main   #16774      +/-   ##
==========================================
- Coverage   45.52%   45.50%   -0.02%
==========================================
  Files         762      762
  Lines       85939    85937       -2
==========================================
- Hits        39124    39108      -16
- Misses      40508    40519      +11
- Partials     6307     6310       +3

Impacted Files
Coverage Δ

modules/highlight/highlight.go
60.39% <55.55%> (+0.20%)
:arrow_up:

modules/util/timer.go
42.85% <0.00%> (-42.86%)
:arrow_down:

modules/queue/workerpool.go
53.05% <0.00%> (-4.20%)
:arrow_down:

modules/queue/manager.go
65.34% <0.00%> (-2.85%)
:arrow_down:

models/unit.go
41.09% <0.00%> (-2.74%)
:arrow_down:

routers/api/v1/repo/pull.go
29.11% <0.00%> (-0.52%)
:arrow_down:

services/pull/pull.go
42.19% <0.00%> (+0.40%)
:arrow_up:

modules/log/event.go
62.50% <0.00%> (+1.85%)
:arrow_up:

models/gpg_key_common.go
64.51% <0.00%> (+4.83%)
:arrow_up:

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 db1e3d0...60c1280. Read the comment docs.


list teams by command line

list teams by command line

Sorry, I don't know why we need this feature. Please add more description for this scenes.

Plan to create teams and add team members by command line. But, still don't know how to get it done, so, 'list team' at first.

It is not necessary, I can use swapper API in bash to do the batch add team things.


@BeanParam annotations should work on methods

the update to jersey2 support does work with @BeanParam objects, however it will only find fields.  It should also treat methods correctly.  Here is the offending code:
https://github.com/wordnik/swagger-core/blob/master/modules/swagger-jaxrs/src/main/scala/com/wordnik/swagger/jaxrs/JaxrsApiReader.scala#L268

This seems to have been completed already but the code is in master only and not the develop_2.0 branch.  The important commit was a part of pull request #547.  Can you (@fehguy) confirm this?  If so, fixing this is as simple as merging 0adb22e from master to develop_2.0.

The logic is in master but it's not complete.  In addition, in master it's scala and not java so it'll need a complete redo

Okay, I'll get started.  Thanks for clarifying.

Pull request #843 should address this when accepted.


BUG: addFlashMessage can not handle Message object

When purging content cache for a certain content type (ex. text/css) you will get the following exception after the purging is done
Exception #1243258395 in line 175 of /var/www/website/Data/Temporary/Production/Cache/Code/Flow_Object_Classes/MOC_Varnish_Controller_VarnishCacheController.php: The message body must be of type string, "object" given. - See also:<PHONE_NUMBER>2504a2ac87.txt
This is due to a Object being passed to the flashMessage.
This change cast it to a string (using the __toString) method of the Message object

@sorenmalling your patch is included in https://github.com/mocdk/MOC.Varnish/releases/tag/4.0.1


Duplicate nodes in domain-level webgraph

Hi,
I noticed duplicate rows in the Common Crawl Oct/Nov/Jan 2021-2022 domain-level webgraph. You can find it by unzipping the file and running the command:
grep -e $'\tno\.hordaland\t' cc-main-2021-22-oct-nov-jan-domain-ranks.txt

This leads to the following output:
grep -e $'\tno\.hordaland\t' cc-main-2021-22-oct-nov-jan-domain-ranks.txt
720700  1.4451489E7     273019  1.4683511019933418E-7   no.hordaland    1
46550260        1.0575547E7     79735653        4.063660522732166E-9    no.hordaland    1

This is the only duplicate I found in the entire file.
You probably want to do a sanity check for this in whatever is your preferred language. This is how I found the issue in the first place! I used python with pandas:
import pandas as pd

df = pd.read_csv(
    "./dataset/cc-main-2021-22-oct-nov-jan-domain-ranks.txt.gz",
    compression="gzip",
    sep="\t")

# should work but crashes
# print(df["#host_rev"].is_unique())

# using unique instead works
print(len(df) == len(df["#host_rev"].unique()))

# to see non-unique values
print(df["#host_rev"].value_counts())

Pandas takes several minutes for some of these operations due to loading the full file in memory. You may want to try vaex or something similar if using python. I'm sure there are similar tools in Java and other languages. You could of course do the check in other ways, but I thought I'd provide the code in case it's useful.
Note I haven't checked yet if these duplicate nodes are present in the other web graph files but I suspect they probably are. So you probably want to do similar sanity checks for those. This should improve the quality of what is an excellent dataset. Thanks very much for making this available!

Thanks, @covuworie! I can confirm the issue. It's caused by two factors:

no and os.hordaland.no are ICANN suffixes in the public suffix list but hordaland.no is not

in the input there is also os.hordaland.no (in reverse domain name notation):
334975755	no.hordaland
...
334975765	no.hordaland.os
334975766	no.hordaland.os.bibliotek
334975767	no.hordaland.oygarden

The assumption is that a sorted list of host names in reversed domain name notation can be "folded" to the level of registered domains with constant memory requirements only remembering the latest domain name (no need to keep all 90 million domain names in memory). Unfortunately, the switching from hordaland.no to bibliotek.os.hordaland.no and back is a edge case to be considered.
I'll fix this in the code which folds the host-level graph into the domain-level one (but likely not for existing graphs).
And yes, eventually add also a verification step whether there are duplicated vertices. Thanks again!

Thanks @sebastian-nagel for your quick response on this issue! I look forward to seeing the updates.

Fixed in 6b4be52 and f663b5c: it's now made sure that domain names are strictly sorted lexicographically - strict sorting does not allow for duplicates. This can be verified by running:
zcat cc-main-2022-may-jun-aug-domain-vertices.txt.gz | cut -f2 | LC_ALL=C sort -uc


added php7 to travis

@rdlowrey hmm why does travis not run the PRs... did you miss to enable the webhook for travis for this project?

@staabm I must have failed to enable it. I've updated that setting. Should work going forward.


Wifi 1355 Repair MIMO mode auto

Signed-off-by: Rick Sommerville<EMAIL_ADDRESS>

Merged, thanks


service tests for Arch Linux [aur]

Messages

:book:

:sparkles: Thanks for your contribution to Shields, @chris48s!

  Generated by :no_entry_sign: dangerJS

good points - updated


When guest user accesses a protected page with CredentialsProvider settings, an error occurs

Environment

Operating System: Darwin
Node Version:     v20.2.0
Nuxt Version:     3.13.2
CLI Version:      3.14.0
Nitro Version:    2.9.7
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
Steps to Reproduce:
Configure CredentialsProvider in the Nuxt config.
Set up a protected route that requires authentication.
Open a session as a guest user and try to access the protected page.
Expected Behavior: The guest user should be redirected to the login page without seeing any error.
Actual Behavior: An error occurs, disrupting the expected flow.
Context: Include the Nuxt version, the @sidebase/nuxt-auth version, and any relevant configuration or code snippets that might help in identifying the issue.
Describe the bug
When a guest (unauthenticated) user attempts to access a protected page configured with CredentialsProvider settings, an error is triggered. Expected behavior would be a redirect to the login page, but instead, an error page appears.
receive 500 status code
Additional context
No response
Logs
ERROR  [nuxt] [request error] [unhandled] [500] The first argument must be of type string or an instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received an instance of URLSearchParams
at __node_internal_captureLargerStackTrace (node:internal/errors:490:5)
at new NodeError (node:internal/errors:399:5)
at Function.from (node:buffer:324:9)
at ./node_modules/h3/dist/index.mjs:410:21
at async readBody (./node_modules/h3/dist/index.mjs:438:16)
at createRequestForAuthjs (./node_modules/@sidebase/nuxt-auth/dist/runtime/server/services/authjs/nuxtAuthHandler.js:123:70)
at Object.handler (./node_modules/@sidebase/nuxt-auth/dist/runtime/server/services/authjs/nuxtAuthHandler.js:42:25)
at async ./node_modules/h3/dist/index.mjs:1975:19
at async Object.callAsync (./node_modules/unctx/dist/index.mjs:72:16)
at async toNodeHandle (./node_modules/h3/dist/index.mjs:2266:7)
at async ufetch (./node_modules/unenv/runtime/fetch/index.mjs:9:17)
at async $fetchRaw2 (./node_modules/ofetch/dist/shared/ofetch.4747642d.mjs:249:26)
at async $fetch2 (./node_modules/ofetch/dist/shared/ofetch.4747642d.mjs:304:15)
at async Object.callAsync (./node_modules/unctx/dist/index.mjs:72:16)
at async signIn (./node_modules/@sidebase/nuxt-auth/dist/runtime/composables/authjs/useAuth.js:92:16)
at async Object.callAsync (./node_modules/unctx/dist/index.mjs:72:16)
at async ./node_modules/nuxt/dist/pages/runtime/plugins/router.js:189:26
No response

Please look into https://github.com/sidebase/nuxt-auth/issues/883
You may need upgrading to a fresh h3


Body parameter with x-examples causes JsonParseException

@fehguy requested that I report swagger-api/swagger-codegen#4442 here.  Reproducing issue text below for context:
Description
Running swagger-codegen on a Swagger definition which includes the x-examples property in a Parameter with in: body causes code generation to fail with com.fasterxml.jackson.core.JsonParseException.
Swagger-codegen version
master (ba285759)
The issue is also present in 2.2.1 and 2.1.6.
Swagger declaration file content
swagger: "2.0"
info:
  version: "1.0.0"
  title: API which causes JsonParseException
paths:
  /pets:
    post:
      parameters:
      - name: "pet"
        in: "body"
        schema:
          type: object
        x-examples:
          application/json:
            foo: bar
      responses:
        "200":
          description: Success
          schema:
            type: object

Steps to reproduce
With the above Swagger declaration file saved as bad_example.yaml run:
git clone https://github.com/swagger-api/swagger-codegen.git
cd swagger-codegen
mvn clean package
java -jar modules/swagger-codegen-cli/target/swagger-codegen-cli.jar generate -i bad_example.yaml -l java -o /tmp/result

Which produces the following output:
[main] INFO io.swagger.parser.Swagger20Parser - reading from bad_example.yaml
[main] INFO io.swagger.parser.Swagger20Parser - reading from bad_example.yaml
com.fasterxml.jackson.core.JsonParseException: Unrecognized token 'swagger': was expecting ('true', 'false' or 'null')
 at [Source: bad_example.yaml; line: 1, column: 9]
        at com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1419)
        at com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:508)
        at com.fasterxml.jackson.core.json.UTF8StreamJsonParser._reportInvalidToken(UTF8StreamJsonParser.java:3201)
        at com.fasterxml.jackson.core.json.UTF8StreamJsonParser._handleUnexpectedValue(UTF8StreamJsonParser.java:2360)
        at com.fasterxml.jackson.core.json.UTF8StreamJsonParser._nextTokenNotInObject(UTF8StreamJsonParser.java:794)
        at com.fasterxml.jackson.core.json.UTF8StreamJsonParser.nextToken(UTF8StreamJsonParser.java:690)
        at com.fasterxml.jackson.databind.ObjectMapper._initForReading(ObjectMapper.java:3105)
        at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3051)
        at com.fasterxml.jackson.databind.ObjectMapper.readTree(ObjectMapper.java:1861)
        at io.swagger.parser.SwaggerCompatConverter.readResourceListing(SwaggerCompatConverter.java:147)
        at io.swagger.parser.SwaggerCompatConverter.read(SwaggerCompatConverter.java:74)
        at io.swagger.parser.SwaggerParser.read(SwaggerParser.java:72)
        at io.swagger.codegen.config.CodegenConfigurator.toClientOptInput(CodegenConfigurator.java:391)
        at io.swagger.codegen.cmd.Generate.run(Generate.java:221)
        at io.swagger.codegen.SwaggerCodegen.main(SwaggerCodegen.java:41)
Exception in thread "main" java.lang.RuntimeException: missing swagger input or config!
        at io.swagger.codegen.DefaultGenerator.generate(DefaultGenerator.java:635)
        at io.swagger.codegen.cmd.Generate.run(Generate.java:223)
        at io.swagger.codegen.SwaggerCodegen.main(SwaggerCodegen.java:41)

(Note that the issue appears regardless of the chosen language.)
Related issues
The JsonParseException: Unrecognized token 'swagger' exception has occurred before due to bad encoding file encoding (swagger-api/swagger-codegen#1575) or use of YAML anchors (#146).  The cause in both of those cases appears to be a Jackson issue.  Since the issue here only occurs when x-examples appears on specific Parameter types, that suggests to me that the issue is not solely with Jackson.
There is an open issue for x-examples support in Swagger UI (swagger-api/swagger-ui#1980), which is unrelated to this issue.  Whether or not that is implemented, x-examples should not prevent code generation.

Does this still happen on the latest master?

@fehguy Yep.  I can confirm it's still happening with swagger-api/swagger-codegen@3f66e27a and swagger-api/swagger-parser@f4845213 on my machine.

Could you please send a PR with a failing test?

@fehguy Sure.  Test case in #376.

Looks like the issue is in the deserialization of the body parameters.  It is currently using Jackson to do so, while the other operations are manually extracting objects, and therefore being more lenient to type conversions and helpful with error messages.

@kevinoid I need to provide more tests, but https://github.com/swagger-api/swagger-parser/pull/381 should fix this.

@fehguy I can confirm it is fixed for the test file I have been using.  Thanks!


Support Yarn v4

Is there an existing issue for this?

[X] I have searched the existing issues

Feature description
Yarn v4 was released a little under two months ago. It brings quite a few performance improvements which convinced my team to finally upgrade from v1. However, we had to pause our migration when we discovered Dependabot did not support v4.  Since Dependabot does support v1-3, supporting v4 seems to be a reasonable thing to do.

We recently updated to yarn v4 our monorepo, and I confirm dependabot does not work. It updates dependencies but does not commit updated yarn.lock file.

Wondering if this works if you set packageManager to yarn v4 in your package.json file. We use corepack internally to select the yarn version to be used so there's a chance that helps?

A PR already exists: https://github.com/dependabot/dependabot-core/pull/8265. Only one workflow seems to be failing.

Any update on yarn v4 support? To expound on the original reasoning for why this would be nice, it provides a way to change how yarn creates symlinks on Windows which–selfishly speaking–would make my job easier.

I have a PR that fixes the issue causing the test to fail here: https://github.com/dependabot/dependabot-core/pull/9405

@brocef , this was already merged, please reactivate if it still doesn't work for you.

We've been using Dependabot since the last few weeks with Yarn v4 and so can confirm it does "work" and update the yarn.lock.
However, just asking a question here and I'll open a separate issue with more context if I see it's related to Yarn v4, but we're having a bit of trouble with Yarn v4 and the Dependabot groups. Our dependabot.yml file contains quite a few groups configurations but for some reasons, some dependencies like next or jose seem to just be ignoring those group configurations completely, as they get added to groups defined at the complete end of our groups configuration.
Since this issue was still opened, I thought it was something to do with Yarn v4 support, but now that @abdulapopoola says it has been available since a few weeks already, I feel like it might just be an issue with Dependabot itself...


v0.2.0

Changelog
v0.2.0

Added option for custom read user output from get
and search user endpoints
Fixed typo

@wsz Closing that pull request for now. I've been convinced that using callback is not a best solution here.


feature request : support asm from string

reg somevar
reg someaddr
or reg some module base addr
-------------- so we can
mov eax,0x1,
lea eax, somevar
jmp someaddr

There is RawAssembyCode pattern. I think your code could be:
X86Assembly.ExecuteScript(new object[]
{
    new RawAssemblyCode("reg somevar"),
    new RawAssemblyCode("reg someaddr"),
    mov, EAX, 0x1,
    lea, EAX, "somevar",
    jmp, "someaddr"
}, typeof(SomeDelegate));


OptionParser: make flag addition code simpler and faster

I'd guess I'm missing something, but this code is imo easier to read and a simple/naive benchmark shows it's 50x faster to do " " * x ...  (5s vs 0.1s)
require "benchmark"
y = 0
z = Benchmark.realtime do
  1000000.times do
    x = " " * 100
    y += x.size
  end
end
puts y
puts z

vs

x = String.build do |str|
  100.times do
  str << " "
  end
str
end

Can you use Benchmark.ips to test that whole method please?

unable to run ips :(
with bin/crystal I get:
./bin/crystal test.cr --release
Error in ./src/fiber.cr:26: this 'initialize' doesn't explicitly initialize instance variable '@stack_top' of Fiber, rendering it nilable

with latest crystal I get:
Empty enumerable (Enumerable::EmptyError)
[4312558] ???
[4312118] ???
[4308862] main +11918
[140672253235013] __libc_start_main +245
[4249449] ???
[0] ???

...
script is:
require "benchmark"

class Testeroo1
  def initialize
    @flags = [] of String
  end

  def append_flag(flag, description)
    @flags << "    #{flag}#{" " * (33 - flag.size)}#{description}"
  end
end

class Testeroo2
  def initialize
    @flags = [] of String
  end

  def append_flag(flag, description)
    @flags << String.build do |str|
      str << "    "
      str << flag
      (33 - flag.size).times do
        str << " "
      end
      str << description
     end
  end
end

x = Benchmark.ips do
  test = Testeroo1.new
  5.times do
    test.append_flag "-f", "a test flag to figure out how fast things are"
  end
end

puts x

@grosser please read the Benchmark.ips docs again, you are missing the syntax to define the tests.

updated script above ...
New 421.11k (± 8.33%)       fastest
Old  288.8k (± 5.66%)  1.46× slower

.. ideally ips should not fail with a cryptic error though :D

@grosser Thanks!
Regardless of the time it takes to perform it, I agree that it reduces the code a lot. And in this case the performance gain or loss in any case shouldn't be noticeable.

❤ first language I could contribute too, thx for making it easy :D

congratulations @grosser


settings: Improve buttons and error handling status elements.

This improves the styling of the inline error messages in the settings window. (This PR includes @shubhamdhama's changes in https://github.com/zulip/zulip/pull/9274)

Have you tested line-wrapping etc.?

There's a little red-spot glitch when you move one of the dropdowns to create the N field:

Yes, line-wrapping and a variety of window sizes/dimensions have been tested—all works fine.
Regarding that visual glitch, it's because the "inline-block subsection-failed-status" div shows even when the save hasn't failed. I can get around it by removing the background of the error, but I think the better fix would be to not show that div unless the save has actually failed.

Cool, if it's a JS logic issue, @shubhamdhama maybe you can pull this styling work into your PR and fix that glitch?

Merged via #9274.


Started grammar and puncuation editing

Started going through files and editing the contents for grammar, punctuation, and spelling. More fixes to come later; it's bed time for me now.

Is this done with American English rules and spelling? I'm happy to help out if you need some extra eyes!

Removed contribution links from minor edits. Figured it'd get obnoxious crediting myself just for a few missing periods and commas everywhere. Also, I fixed the issues the system mentioned, but it's still saying my tofu stir fry recipe is failing checks, just won't say why now.

Does anyone know why my recipe keeps getting rejected? I've compared it to several others and can't find the difference that's making the compliance check fail.

Does anyone know why my recipe keeps getting rejected? I've compared it to several others and can't find the difference that's making the compliance check fail.

Yeah It looks like to much spacing, I'll fix em up.

Finally got it! Heck, this thing sure is strict about spacing. Also sucks I couldn't have "Simple Cooking Procedures" instead of "Directions". Oh well. XD


"No color" disappear or not present

Describe the bug
If you using Google chrome to write page,
the "No color" disappear after set color to a text.
If you use Microsoft Edge, the no color is not present.
Steps To Reproduce
For Google Chrome
Steps to reproduce the behavior:

click to background color
click in document to close colors list
click to background color
the "no color" is no longer there

Expected behavior
Always "no color" present in list of colors.
Screenshots
Google Chrome
first click:

reopen list of colors:

Microsoft Edge

Your Configuration (please complete the following information):

Exact BookStack Version (Found in settings): v0.23.2
PHP Version: 7.2
Hosting Method (Nginx/Apache/Docker): Apache 2.4

Additional context
No additional information.

Thanks for reporting @Xarkam and thanks for the really clear description and screenshots.
This will be fixed as of the next upcoming release, v0.24.


Can't install example app on Mac OS

Hello, I am stuck in the very beginning :) I'm trying to run the next command:
serverless create -u https://github.com/adieuadieu/serverless-chrome/tree/master/serverless-chrome/examples/serverless-framework/aws

But output is always the same:
Serverless: Generating boilerplate...
Serverless: Downloading and installing "aws"...

  Serverless Error ---------------------------------------

  Error: EEXIST: file already exists, symlink '../dist/' -> '/var/folders/xz/fmlcpsh92zn23tv701vvynfh0000gn/T/serverless-chrome/packages/lambda/integration-test/dist'

  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues
     Forums:        forum.serverless.com
     Chat:          gitter.im/serverless/serverless

  Your Environment Information -----------------------------
     OS:                     darwin
     Node Version:           8.9.1
     Serverless Version:     1.24.1

I tried 3 different macs, and the problem is the same on all of them.

That's no good. Sorry about that. 😞
Alternatively, you can try:
git clone https://github.com/adieuadieu/serverless-chrome.git
cd serverless-chrome/examples/serverless-framework/aws
[ -n "$(which yarn)" ] && yarn install || npm install

Now you should be as far as you'd be doing serverless create -u ...

Great, thanks @adieuadieu, that really helped!

@anzebra glad to hear that helped!
I'm going to re-open this Issue thread as the original reported problem has not been corrected, and I'd like to make sure it gets fixed.

Hi, @adieuadieu
I have a same error in Ubuntu 16.04 LTS.
To fix the problem I use provided you solution:
git clone https://github.com/adieuadieu/serverless-chrome.git
cd serverless-chrome/examples/serverless-framework/aws
[ -n "$(which yarn)" ] && yarn install || npm install

But I don't understand which command I should perform after this.
Could you please provide a more detailed instructions?

I'm still getting the same error as originally reported when running 'serverless create.' Was this ever fixed? Thanks!


Constant name "this_screen" doesn't conform to UPPER_CASE naming style

https://github.com/lbonanomi/gRist/blob/0bb7eceee04bd597966217117892ae3e98250892/grist.py#L148

Issues for naming style are now ignored.


Disallow multiple constants assignment

This is my first time deep diving into the compiler 😄  Fixes #3466
I added a spec to spec/compiler/semantic/const_spec.cr with assert_error, it's working but failing.
Failures:

  1) Semantic: const errors on multiple constant assignment (#3466)

       Syntax error in :2: Multiple assignment is not allowed for constants
       [4386931682] *CallStack::unwind:Array(Pointer(Void)) +82
       [4386931585] *CallStack#initialize:Array(Pointer(Void)) +17
       [4386931544] *CallStack::new:CallStack +40
       [4386881281] *raise<Crystal::SyntaxException>:NoReturn +17
       [4395110195] *Crystal::Parser@Crystal::Lexer#raise<String, Int32, Int32, (Crystal::VirtualFile | String | Nil)>:NoReturn +35
       [4395110158] *Crystal::Parser@Crystal::Lexer#raise<String>:NoReturn +62
       [4395126494] *Crystal::Parser#parse_multi_assign:Crystal::ASTNode+ +206
       [4395125219] *Crystal::Parser#parse_expressions_internal:Crystal::ASTNode+ +163
       [4395125012] *Crystal::Parser#parse_expressions:Crystal::ASTNode+ +52
       [4395075326] *Crystal::Parser#parse:Crystal::ASTNode+ +30
       [4386881258] *parse<String, Bool>:Crystal::ASTNode+ +58
       [4386881183] *parse<String>:Crystal::ASTNode+ +31
       [4386904867] *assert_error<String, String, Bool>:Nil +83
       [4386904775] *assert_error<String, String>:Nil +39
       [4386909101] ~procProc(Nil)@./spec/compiler/semantic/const_spec.cr:241 +29
       [4386879831] *it<String, String, Int32, &Proc(Nil)>:(Array(Spec::Result) | Nil) +375
       [4386879432] ~procProc(Nil)@./spec/compiler/semantic/const_spec.cr:3 +2088
       [4387385321] *Spec::RootContext::describe<String, String, Int32, &Proc(Nil)>:Spec::Context+ +361
       [4386877289] *describe<String, String, Int32, &Proc(Nil)>:Spec::Context+ +9
       [4386784117] __crystal_main +4661
       [4386855336] main +40

Finished in 1.41 seconds
28 examples, 0 failures, 1 errors, 0 pending

Any help wecome 👍

@sdogruyol I had a bit of time to review this (it was low prio) and your changes look really good! I made a comment, after you fix that I'll merge it :-)

Closing this for #3728


Hermes integration failed

Version
Tell us which versions you are using:

react v16.11.0
react-native v0.62.2

Product flavours 2 - uat and prod
Expected behaviour
assembleRelease command should be successful
Actual behaviour
FAILURE: Build failed with an exception.
Process 'command '../../node_modules/hermes-engine/osx-bin/hermes'' finished with non-zero exit value 6

⚠	Missing Environment Information
ℹ	Your issue may be missing information about your development environment. You can obtain the missing information by running react-native info in a console.

System:
OS: macOS 10.15.6
CPU: (4) x64 Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
Memory: 2.41 GB / 16.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 12.18.2 - /usr/local/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 6.14.5 - /usr/local/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.9.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 13.5, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
Android SDK:
API Levels: 23, 28, 29
Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.2
Android NDK: Not Found
IDEs:
Android Studio: 4.0 AI-193.69<IP_ADDRESS>26763
Xcode: 11.5/11E608c - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_261 - /usr/bin/javac
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 16.11.0 => 16.11.0
react-native: 0.62.2 => 0.62.2
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found


Search docs

I really hate markdown sometimes. FYI the distutils.version link didn't work so I left the url.

Current coverage is 97.29%

Merging #22 into develop will not affect coverage as of e2eeff6

@@            develop     #22   diff @@
=======================================
  Files            42      42
  Stmts          1182    1182
  Branches          0       0
  Methods           0       0
=======================================
  Hit            1150    1150
  Partial           0       0
  Missed           32      32

Review entire Coverage Diff as of e2eeff6

Powered by Codecov. Updated on successful CI builds.

All comments have been addressed 5df9d276c7d02757dcc8d737aa15ab07807ff76a


Refactor RRTMGP interface to be GPU compatible

@sriharshakandala should we close this?

Yes, we can close


Fireworks for limited amount of time

Feature Proposal
option 1: a variable in the options object to set the amount of seconds that the library will generate projectiles.
option 2: A function that when called will stop generating new projectiles.
the pause & stop function doesn't satisfy this because:

the pause function freezes the canvas instantly
the stop function clears the canvas instantly

the goal is to make the transition from fireworks all around to no fireworks seem natural.
Motivation
I want fireworks to blast for a limited amount of time. I have fireworks in the background of a cta/feature div.
By keeping the fireworks on indefinitely the screen looks very busy and is hard to read. But i like the attention it grabs in the beginning.
Example
const fireworks = new Fireworks(container,
                {
                    traceSpeed: 1,
                    acceleration: 1.01,
                    rocketsPoint: 25,
                    explosion: 3,
                    trace: 2,
                    delay: { min: 20, max: 30 },
                    generationMs: 5000 //5 seconds
                });

fireworks.start();

//option2
let stopped = false;
window.addEventListener('scroll', function() { //lets say fireworks is at the top of my page and i want to disable it on scrolling.
        if (!stopped){
                stopped = true;
                fireworks.stopGenerating();
        }
}

i wrote a piece of code that did exactly what i want. The fireworks start once the h2 element in the container is visibile. It starts of with lots of fireworks but decreases quickly to very low intensity so that the CTA is readable.
    const fireworks = new Fireworks(container, {intensity: 60, trace: 1});
    let intensity = 58.5;
    let intensityDecay = [0,20,15,10,6,3,2,1];
    let intensityInterval = null;

    let fireworksObserver = new IntersectionObserver(function (entries) {
        entries.forEach(entry => {
            if (entry.isIntersecting) {
                fireworksObserver.disconnect();
                fireworks.start();
                intensityInterval = setInterval(function (){
                    if (intensityDecay.length>0){
                        intensity-=intensityDecay.shift();
                        console.log(intensity);
                        fireworks.setOptions({intensity: intensity});
                    } else {
                        clearInterval(intensityInterval);
                    }
                }, 400);
            }
        });
    }, {
        rootMargin: '0px',
        threshold: 0.5
    });

    fireworksObserver.observe(document.getElementById('2ndHeading'));```

This resolved my issue, but it might be a cool idea to include similar functionality in the library natively.


Update devenv-richtext-content-controls.md

Fixed wrong variable name used in example code from Output to Outstream

Thanks so much for this. We just fixed it based on a GH issue on the private side of this repo, so to avoid conflicts, I will close this one. But much appreciated!


Add Zapier logo

Can you add Zapier's logo to the sponsors?
https://zapier.com/about/brand/

Closed by #126.


Vert.x on Kubernetes with Hazelcast clustering not working

Hi
I am trying to deploy Vert.x on Kubernetes with hazelcast clustering. I followed the same steps mentioned here:
https://vertx.io/docs/vertx-hazelcast/java/#_configuring_for_kubernetes
I have 2 verticles and they both are able to discover themselves on Kubernetes as shown below:

But when one verticle tries to send message to another over eventBus it uses localhost, and connection cannot be established:

I have done the setup by following steps:

Following are the dependencies that I added in the verticles:

<dependencies>
<dependency>
                        <groupId>io.vertx</groupId>
                        <artifactId>vertx-hazelcast</artifactId>
                        <version>3.6.3</version>
                </dependency>
                <dependency>
                        <groupId>com.hazelcast</groupId>
                        <artifactId>hazelcast-kubernetes</artifactId>
                        <version>1.0.0</version>
                </dependency>

  </dependencies>

And my cluster.xml for both the vert.x verticles looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<!-- ~ Copyright 2017 Red Hat, Inc. ~ ~ Red Hat licenses this file to you
        under the Apache License, version 2.0 ~ (the "License"); you may not use
        this file except in compliance with the ~ License. You may obtain a copy
        of the License at: ~ ~ http://www.apache.org/licenses/LICENSE-2.0 ~ ~ Unless
        required by applicable law or agreed to in writing, software ~ distributed
        under the License is distributed on an "AS IS" BASIS, WITHOUT ~ WARRANTIES
        OR CONDITIONS OF ANY KIND, either express or implied. See the ~ License for
        the specific language governing permissions and limitations ~ under the License. -->

<hazelcast
        xsi:schemaLocation="http://www.hazelcast.com/schema/config hazelcast-config-3.10.xsd"
        xmlns="http://www.hazelcast.com/schema/config"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <properties>
   <property name="hazelcast.discovery.enabled">true</property>
 </properties>
<group>
                <name>k8s</name>
                <password/>
        </group>
 <network>
   <join>
     <multicast enabled="false"/>
     <tcp-ip enabled="false" />

     <discovery-strategies>
       <discovery-strategy enabled="true"
           class="com.hazelcast.kubernetes.HazelcastKubernetesDiscoveryStrategy">
         <properties>
           <property name="service-dns">service-hazelcast-server.default.svc.cluster.local</property>
         </properties>
       </discovery-strategy>
     </discovery-strategies>
   </join>
 </network>
</hazelcast>

And After that I deployed one headless Kubernetes service with following Kubernetes configuration:

apiVersion: v1
kind: Service
metadata:
 namespace: default
 name: service-hazelcast-server
spec:
 selector:
   component: service-hazelcast-server
 clusterIP: None
 ports:
 - name: hz-port-name
   port: 5701
   protocol: TCP

Once service is deployed, I am  passing component label as service name in Verticles k8 deployments as follows:

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  namespace: default
  name: pod-hazelcast-client1
spec:
  # 1 or 2 client pods
  # replicas: 1
  replicas: 1
  selector:
    matchLabels:
      app: pod-hazelcast-client1
  template:
    metadata:
      labels:
        app: pod-hazelcast-client1
        component: service-hazelcast-server
    spec:
      containers:
        - env:
          # Are we in Kubernetes
          - name: K8S
            value: "true"
          image: "<my-docker-registry-address>/hazelcast-client1"
          ports:
          - name: verticle-port
            containerPort: 8281
            hostPort: 8281
          ports:
          - name: hazelcast-port
            containerPort: 5701
            hostPort: 5701
          # Always from local, never from Dockerhub
          imagePullPolicy: Always
          # Url to check every 10 seconds if the container is ok
          name: container-hazelcast-client1
          # Url to check the container is up
      imagePullSecrets:
      - name: pvt-reg-cred
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  namespace: default
  name: pod-hazelcast-client2
spec:
  # 1 or 2 client pods
  # replicas: 1
  replicas: 1
  selector:
    matchLabels:
      app: pod-hazelcast-client2
  template:
    metadata:
      labels:
        app: pod-hazelcast-client2
        component: service-hazelcast-server
    spec:
      containers:
        - env:
          # Are we in Kubernetes
          - name: K8S
            value: "true"
          image: "<my-docker-registry-address>/hazelcast-client2"
          ports:
          - name: verticle-port
            containerPort: 8281
            hostPort: 8281
          ports:
          - name: hazelcast-port
            containerPort: 5701
            hostPort: 5701
          # Always from local, never from Dockerhub
          imagePullPolicy: Always
          # Url to check every 10 seconds if the container is ok
          name: container-hazelcast-client2
          # Url to check the container is up
      imagePullSecrets:
      - name: pvt-reg-cred

But still I am not able to configure Verticles to publish message over EventBus.

I am also facing the same issue. I also tried setting up the cluster host (using  new VertxOptions().setClusterHost()) in Java but still got no luck. I tried setting up this value to Host address of my hazel cast server but it is keep on saying Not able to bind, address already in use.

@Swatikp how is the Vert.x app started? It sounds like you created your own main instead of reusing the Launcher class . When you create your own main, you must set the cluster host option yourself (the launcher autodetects the node IP).

@Swatikp Did you resolve the issue? I'm using Launcher class and still ran into this issue. However in my case, i can't seem to get the hazelcast clustering working either, and ofcourse the eventbus clustering is the next stop. Followed like you, verbatum the vert.x docs and see the following log from ping verticle and pong verticle. I'm using hazelcast port 5701 and explicit event-bus port 5711
INFO: [<IP_ADDRESS>]:5701 [dev] [3.9.4] Kubernetes Discovery properties: { service-dns: hazelcast-headless-service.ngi-dev.svc.cluster.local, service-dns-timeout: 5, service-name: hazelcast-headless-service, service-port: 5701, service-label: component, service-label-value: hazelcast, namespace: ngi-dev, resolve-not-ready-addresses: false, kubernetes-master: https://kubernetes.default.svc} Apr 03, 2019 12:25:07 AM com.hazelcast.spi.discovery.integration.DiscoveryService INFO: [<IP_ADDRESS>]:5701 [dev] [3.9.4] Kubernetes Discovery activated resolver: DnsEndpointResolver Apr 03, 2019 12:25:07 AM com.hazelcast.instance.Node INFO: [<IP_ADDRESS>]:5701 [dev] [3.9.4] Activating Discovery SPI Joiner Apr 03, 2019 12:25:07 AM com.hazelcast.spi.impl.operationexecutor.impl.OperationExecutorImpl INFO: [<IP_ADDRESS>]:5701 [dev] [3.9.4] Starting 2 partition threads and 3 generic threads (1 dedicated for priority tasks) Apr 03, 2019 12:25:07 AM com.hazelcast.internal.diagnostics.Diagnostics INFO: [<IP_ADDRESS>]:5701 [dev] [3.9.4] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments. Apr 03, 2019 12:25:07 AM com.hazelcast.core.LifecycleService INFO: [<IP_ADDRESS>]:5701 [dev] [3.9.4] [<IP_ADDRESS>]:5701 is STARTING Apr 03, 2019 12:25:07 AM com.hazelcast.system INFO: [<IP_ADDRESS>]:5701 [dev] [3.9.4] Cluster version set to 3.9 Apr 03, 2019 12:25:07 AM com.hazelcast.internal.cluster.ClusterService INFO: [<IP_ADDRESS>]:5701 [dev] [3.9.4]  Members {size:1, ver:1} [ 	Member [<IP_ADDRESS>]:5701 - 1def86ee-13c4-4dc9-958a-10d7ac76abed this ] Apr 03, 2019 12:25:07 AM com.hazelcast.core.LifecycleService INFO: [<IP_ADDRESS>]:5701 [dev] [3.9.4] [<IP_ADDRESS>]:5701 is STARTED Apr 03, 2019 12:25:08 AM com.hazelcast.internal.partition.impl.PartitionStateManager INFO: [<IP_ADDRESS>]:5701 [dev] [3.9.4] Initializing cluster partition table arrangement... 2019-04-03 00:25:08,324 1862 [main] DEBUG c.b.banking.ngi.common.Launcher - @afterStartingVertx, isClustered:true, isMetricsEnabled:false, eventBus: io.vertx.core.eventbus.impl.clustered.ClusteredEventBus@14a2f921 Apr 03, 2019 12:25:08 AM io.vertx.core.impl.launcher.commands.VertxIsolatedDeployer INFO: Succeeded in deploying verticle 2019-04-03 00:25:45,890 39428 [vert.x-eventloop-thread-0] DEBUG c.b.b.ngi.request.PingVerticle - Error: No reply(NO_HANDLERS,-1) No handlers for address pong

Never mind! My issue was with the network policy on kubernetes preventing pod discovery. It's all good!

@mpreddy77 thanks for letting us know!

Hi @tsegismont
The problem for me was that the verticle  was trying to discover other verticle on localhost and since all of them were on different port, localhost does not make sense in that case. So the below approach worked for me.
Finding address where the verticle is running:
String address = InetAddress.getLocalHost().getHostAddress();

Configuring eventbus to set host as the  Address that we found in previous step:
VertxOptions options = new VertxOptions().setClustered(true).setClusterManager(clusterManager).setEventBusOptions(new EventBusOptions().setPort(5711).setHost(address));

I hope this can help anyone else facing the same issue.

Thank you @mpreddy77


Pre-fills the Exposure Notes section when Enrolling Close Contact

Description
Jira Ticket: SARAALERT-747
Per user request, it would be nice if, when enrolling a Close Contact, the Close Contact's notes were pre-populated into the Exposure Notes in the final card in the enrollment carousel.
Important Changes
app/javascript/components/close_contact/CloseContact.js

Added placeholder text depending on the Monitoree's Workflow. The logic is quite simple.

 this.closeContactNotePlaceholder = this.props.patient.isolation
        ? 'enter additional information about case'
        : 'enter additional information about monitoree’s potential exposure';

app/controllers/patients_controller.rb

Now pre-fills the exposure notes when enrolling a Close Contact that has Notes

app/javascript/components/enrollment/steps/Contact.js

Now checks for the existence of an email address to decide whether to prefill the confirm_email field. Before, it was only when editing an existing monitoree, but enrolling a Close Contact should prefill their email to the confirm_email as welll.

Can you change the target branch from master to 1.14 since this ticket is slotted for 1.14?

Tested, and code changes look good. After the target branch is updated I'm good to approve.


MdDialog passing in data and or variables to modal

Bug, feature request, or proposal:
Passing things into the second component seems obscure.  I can't readily pass in values to the second component to display on modal popup.
What is the expected behavior?
When the modal popup is displayed... information such as variables will display accordingly {{data.here}}
What is the current behavior?
Not working
What are the steps to reproduce?
pass in variables to the new value
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: http://plnkr.co/edit/o077B6uEiiIgkC0S06dd
https://plnkr.co/edit/dhZ4UldIlQKDPvrjJP2f?p=preview  <<< this is example from Material
    export class DialogResultExampleDialog {
        title: string = 'book';
      constructor(public dialogRef: MdDialogRef<DialogResultExampleDialog>) {}

      public testFunction(errorMsg: string) {
        console.log('this is a test999999 ' + errorMsg);
      }

   }

What is the use-case or motivation for changing an existing behavior?
To be able to pass in data / variables to the modal dialog popup upon request.
Which versions of Angular, Material, OS, browsers are affected?
Angular 2.4.1
Is there anything else we should know?

There is a pull request to make it easier
feat(dialog): add a config option for passing in data
In the mean time https://github.com/angular/material2/issues/1377#issuecomment-250632661

@antonyRoberts is right. I'll close this issue as a duplicate of #2181.

Hi @crisbeto and @antonyRoberts ... I have been working through it and I notice that the way the example API shows how to do the diaglog there is a 2 component system.  The issue with that is accessing the class to fire the modal popup is probably the same class that has the data you need to access too... not to say there aren't ways to get around this but the point is still a concern.  So what I did is pointed it to the same class.
This works per se but now I can't set the data.
For example...
title: string = 'book';  i

this is fine but what if I want to access data... i.e.
title: any = this.someFunction(dataPassedIn);

^^^^^ I can't do this.  perhaps I am doing something wrong but any help would be appreciated.
Should I post this in the other issue forum?  #2181

Not sure I get the issue @xtianus79. Can you post what your classes look like?

@crisbeto it is pretty straight forward...
export class ApiHelper {

selectedOption: any = this.openMessage();
messagetype: string;
name: string = 'paul';

constructor(
    private http: Http,
    public dialog: MdDialog,
    //public dialogRef: MdDialogRef<DialogResultExampleDialog>
) { }

openDialog(errorMsg: string) {
let dialogRef = this.dialog.open(ApiHelper);
this.selectedOption = 'test here';
let blue = this.openMessage(errorMsg);
console.log('three he is ' + errorMsg + ' >>>> ' + blue);
console.error('this is errorMsg22222 = ' + errorMsg);
dialogRef.afterClosed().subscribe(result => {
  this.messagetype = errorMsg;
  this.selectedOption = blue;
});

}
openMessage(errorMsg: string) {
  console.log('this is the open message9999 = ' + errorMsg)
  this.selectedOption = errorMsg;

  return this.selectedOption;

}
I would like for this >>>> selectedOption: any = this.openMessage(); to work but i get a typescript error that I am not matching in the function... i.e. errorMsg: string isn't being passed in...

Not sure where the openMessage comes from, but you're basically calling it in the constructor. In regards to getting a hold of the dialog instance, you can do that in the openDialog method with dialogRef.componentInstance.

@crisbeto you mean like dialogRef.ApiHelper ???

No, literally dialogRef.componentInstance.

MMMMMMMMM.... @crisbeto You SIR...
I appreciate your help that did the trick...
let blue = dialogRef.componentInstance.openMessage(errorMsg);

I have to clean this up a lot but i will repost on plunkr to show what I did...
Again thanks!!


deprecate expireInMinutes and expireInSeconds - in favor of expires

This change adds a deprecation warning on the confusing expiresInMinutes and expiresInSeconds options of the sign method.
The new option expires accept seconds or an string that represents an amount of time. Examples:
jwt.sign({foo: 'bar'}, 'my-secret', { expires: 24 * 60 * 60 });
jwt.sign({foo: 'bar'}, 'my-secret', { expires: '2d' });
jwt.sign({foo: 'bar'}, 'my-secret', { expires: '2 days' });
jwt.sign({foo: 'bar'}, 'my-secret', { expires: '10 hours' });
jwt.sign({foo: 'bar'}, 'my-secret', { expires: '10h' });

This should also solve the concern expressed in #87.

I like it. Can we add tests for good errors in case the string is not valid?

@dschenkelman que tal esto?

:laughing:

Just a minor phrasing change: I'd use expiresIn since expires is similar to exp, which is an absolute datetime instead of a time interval. Maybe have both expiresIn and expiresOn?

I like expiresIn

@dschenkelman  Heads up, I just renamed to expiresIn and I think is ready to merge.

Is there a reason we are dividing by 1000 in several places as apposed to multiplying by 1000 when setting the expiration?  It would seem we are losing a bit of precision here (even if it is a small amount)

This change has been merged and released as<EMAIL_ADDRESS>

It's good to put this breaking change in CHANGELOG.md


decoding pipeline + documentation

I am going through the individual files leaving in-line comments, but here a few general ones:

We need to flake the code (format according to PEP conventions), I'll let that be for now I think it's easier to do in the end
This file should probably be removed and these types of files should be added to the .gitignore data_checks/.DS_Store

The solution with making a copy of the settings file is good for now. It does seem though, that there are very few settings that actually need to be changed by the user, namely the output directory and the target (maybe the estimator, which should then be more at the top of the settings file maybe).
So I wonder if those two or three could not instead be parsed as a simple input when running the pipeline or main function. Nothing that needs to change for now but if you'd want to distribute this beyond this paper (Charles might want to?) I think that would be the way to go

@themattinthehatt remove process_motors

@themattinthehatt remove process_motors

Merged "manually"


Bitbucket parses Jira keys in different way

I would like to use this library to parse Jira keys, but I have found some edge cases regarding to banch name parsing. As I see, this library parse it as a different way.
Could you support these formats also?

Parsing of pull requests' commits uses similar logic:
JRA-345-JRA-456
JRA-567--JRA-678
JRA-789-b-JRA-890


[CWS] split host workloads and container workloads in cgroup resolver

What does this PR do?
GetWorkload is called a lot, and every call iterate on the whole map and allocates a new "values" slice. This PR splits the workload into host workloads (that have a cgroupID but no containerID) and container workloads (that have both).
This PR also switches the RWMutex to a regular Mutex since an LRU needs to write even in the Get path (to update the LRU info)
Fixes: https://github.com/DataDog/datadog-agent/pull/31702
Example profile showing the issue
Motivation
Describe how you validated your changes

Possible Drawbacks / Trade-offs
Additional Notes

/merge


Write values to file

There are applications which reads values only from file, not from environment variables.
Should support these applications?

Is this enough?
$ cat echo_env.sh
#!/bin/bash

set -e

eval "echo \${$1}"

$ ssmwrap -paths ... -- echo_env.sh FOO_BAR > foo_bar.txt
$ ssmwrap -paths ... command_read_from_foo_bar_txt

should -file option receive file permission, owner and group?
It seems to use structured argument like:
-file name=foo,path=/path/to/foo,owner=bar,group=baz,mode=0600


Update Checkout to version 3

Inspired from #14625

Checkout was upgraded so it can use node.js 16 by default

Thank you for updating this!

^^ it wasn't hard


feat: update hardware type for an ironic node

Going to close this out because we've finally now implemented this.


Add general feedback from notifications

-[ ] Send notification to HRD about new feedback
NOTE: Feedback form for both Residents + PMs

Since the form is just a Google form right now, I'm closing this task to notify HRD about the feedback.


AWS provider tries to terminate empty list of instance IDs, and always logs instances as "pending"

After completing tasks, Parsl passes on empty list of instances to terminate to boto3, which raises an API error and terminates the program before it is complete. Further, even when the EC2 console and the AWS CLI show instance status as "running," and even when Parsl logs that tasks have been completed on instances, Parsl logs instance status as "pending".

@fritzreece Hi Fritz, thanks a bunch for reporting this. I'm able to reproduce this bug, and have a fix in testing now. I'll have these changes in dev branches for now since these are being tested for our next major release (v0.6.0). I'll post more information once I have fixes out.

This is fixed.


Extendable api: easier storage

@Laucans Alternatively, if we don't want the user to concern themself with a extension = () in the storage, we can do as in commit bef232bd44898f9ae3b9d993e98fd10d1928e14c (only implemented for NFT.mligo, look at the examples/marketplace.jsligo file). With additional lifting and unlifting operations, we can have a slightly better API, but the code produced is much worse.
See the two attached files, normal.tz.txt and with-lift.tz.txt. Those are the same contract NFT.mligo from both branch (just-extendable and the current one). If you diff both files, you can see that there's around 75 lines of code that are added. I think the compiler could do much better, but with the current version I'm not sure that's warranted.
By the way, is there a reason for keeping both JSLigo and Mligo implementations? Especially if we expose a single main.mligo.

is there a reason for keeping both JSLigo and Mligo
Good question

@Laucans Updated the README here too.

Removing of submodule has not been done on the commit with the name  "Easier interface + compilation (no submodule anymore) " :
https://github.com/ligolang/contract-catalogue/pull/37/commits/5329761a9c155725b140dfe2059edd723f4c07a0
Not a big deal now the review is done. Make sure to squash before commit :D

Removing of submodule has not been done on the commit with the name "Easier interface + compilation (no submodule anymore) " : 5329761
Not a big deal now the review is done. Make sure to squash before commit :D

I think it's done in the parent commit, no?

Rebased on https://github.com/ligolang/contract-catalogue/pull/36 and fixed the issues you raised. Still not formated properly I think.


Links to .NET standard specs are broken

The table that lists .NET standard versions and their compatibility with different runtimes makes the .NET Standard version number a link, for example pointing to https://github.com/dotnet/standard/blob/master/docs/versions/netstandard2.0.md.
However, none of these links work, and the dotnet/standard repo was migrated and the master branch no longer contain a docs directory.

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

ID: 9eb8b774-c6f0-8235-6964-15219baf2ea7
Version Independent ID: 6819a4a7-7527-d8c7-e132-767f7344e00e
Content: .NET Standard
Content Source: docs/standard/net-standard.md
Product: dotnet
Technology: dotnet-standard
GitHub Login: @gewarren
Microsoft Alias: gewarren

Thank you @zivkan.


check the accuracy of the memory track in test mode

What problem does this PR solve?
Issue Number: close #5776
Problem Summary:
What is changed and how it works?
Check the accuracy of the memory track in test mode through the following method.

Add memory_tracker_accuracy_diff_for_test to the configuration.
It defaults to 0 (off state), and when it is greater than 0, it is regarded as on.
When allocating memory, if the test mode is on and real_rss > accuracy_diff_for_test + current_amount, throw an exception.

Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

If the pr is ready，you can remove  mark “[WIP] ” remove the title

/cc @bestwoody

/assign @bestwoody

/merge


Fix connection port

@dmcyk I'm not sure about this one, but swift build complained about "rangeOfPort is only available on OS X 10.11 or newer". That's why I'm trying to achieve the same results by using port property.

Right, by default it's using 10.10 deployment target, even on newer versions, thus the error.
Thanks for the pr!


Sort not working on createdAt timestamp with @key directive

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
14.16.1
Amplify CLI Version
5.0.2
What operating system are you using?
Windows 10
Amplify Categories
api
Amplify Commands
Not applicable
Describe the bug
I cannot sort by createdAt using the @key directive. The query works however the result produced is not ordered at all. When I switch between ASC and DESC, the result flips as expected but the order is not related to the createdAt field which is expected.
I have tried manually setting the createdAt field to:

new Date().valueOf().toString() =<PHONE_NUMBER>163
new Date().toString() = Mon Jun 28 2021 12:41:31 GMT+0100 (British Summer Time)

To no avail... I have also tried leaving it blank in which case amplify populates the field with something looking like "2021-06-28T11:42:16.880Z" with no luck.
This issue was found when mocking the environment (using Local DynamoDb)
Expected behavior
The result produced is an ordered list by the createdAt timestamp.
Reproduction steps

Create the message entry n amount of times

mutation CreateMessage {
  createMessage(
    input: {status: SENT, value: "Message 1", receiver: "user's_sub_attribute"}
  ) {
    id
  }
}

List the messages

query MyQuery {
  messagesByDate(
    receiver: "user's_sub_attribute"
    sortDirection: ASC
  ) {
    items {
      value
      id
      createdAt
      receiver
    }
  }
}

GraphQL schema(s)

# Put schemas below this line
type Message
  @model
  @auth(
    rules: [
      # Owner has full access
      { allow: owner }
      # The reciever can read and update
      { allow: owner, ownerField: "receiver", operations: [read, update] }
    ]
  )
  @key(
    name: "messagesByDate"
    fields: ["receiver", "createdAt"]
    queryField: "messagesByDate"
  ) {
  id: ID!
  receiver: ID!
  deleted: Boolean
  status: MessageStatus!
  value: String!
  createdAt: String!
}

Log output

# Put your logs below this line

Additional information
No response

Hey @bacon1097 :wave: if you change createdAt's type to AWSDateTime will it sort as expected? I noticed in one of our examples on the docs site it originally shows String and then switches to AWSDateTime in a later example.
https://docs.amplify.aws/cli/graphql-transformer/key#example-get-orders-by-customer-email-by-createdat

Hi @josefaidt, I have indeed tried that also with no luck. Forgot to mention that in the initial issue.

query MyQuery {
  messagesByDate(
    receiver: "06c690af-3bf1-4007-a951-22c34eb7a3f8"
    sortDirection: ASC
  ) {
    items {
      createdAt
      value
      receiver
    }
  }
}

Produces:
{
  "data": {
    "messagesByDate": {
      "items": [
        {
          "createdAt": "2021-06-29T15:47:24.753Z",
          "value": "Message 5",
          "receiver": "06c690af-3bf1-4007-a951-22c34eb7a3f8"
        },
        {
          "createdAt": "2021-06-29T15:46:18.374Z",
          "value": "Message 3",
          "receiver": "06c690af-3bf1-4007-a951-22c34eb7a3f8"
        },
        {
          "createdAt": "2021-06-29T15:47:22.216Z",
          "value": "Message 4",
          "receiver": "06c690af-3bf1-4007-a951-22c34eb7a3f8"
        },
        {
          "createdAt": "2021-06-29T15:47:47.919Z",
          "value": "Message 6",
          "receiver": "06c690af-3bf1-4007-a951-22c34eb7a3f8"
        },
        {
          "createdAt": "2021-06-29T15:46:14.325Z",
          "value": "Message 2",
          "receiver": "06c690af-3bf1-4007-a951-22c34eb7a3f8"
        },
        {
          "createdAt": "2021-06-28T11:42:16.880Z",
          "value": "Message 1",
          "receiver": "06c690af-3bf1-4007-a951-22c34eb7a3f8"
        }
      ]
    }
  }
}

query MyQuery {
  messagesByDate(
    receiver: "06c690af-3bf1-4007-a951-22c34eb7a3f8"
    sortDirection: DESC
  ) {
    items {
      createdAt
      value
      receiver
    }
  }
}

Produces:
{
  "data": {
    "messagesByDate": {
      "items": [
        {
          "createdAt": "2021-06-28T11:42:16.880Z",
          "value": "Message 1",
          "receiver": "06c690af-3bf1-4007-a951-22c34eb7a3f8"
        },
        {
          "createdAt": "2021-06-29T15:46:14.325Z",
          "value": "Message 2",
          "receiver": "06c690af-3bf1-4007-a951-22c34eb7a3f8"
        },
        {
          "createdAt": "2021-06-29T15:47:47.919Z",
          "value": "Message 6",
          "receiver": "06c690af-3bf1-4007-a951-22c34eb7a3f8"
        },
        {
          "createdAt": "2021-06-29T15:47:22.216Z",
          "value": "Message 4",
          "receiver": "06c690af-3bf1-4007-a951-22c34eb7a3f8"
        },
        {
          "createdAt": "2021-06-29T15:46:18.374Z",
          "value": "Message 3",
          "receiver": "06c690af-3bf1-4007-a951-22c34eb7a3f8"
        },
        {
          "createdAt": "2021-06-29T15:47:24.753Z",
          "value": "Message 5",
          "receiver": "06c690af-3bf1-4007-a951-22c34eb7a3f8"
        }
      ]
    }
  }
}

Hey @bacon1097 are you also seeing this issue if you run the query in the AppSync Console or is it only when mocking locally?

Hi @josefaidt, I am only seeing it when locally mocking so far. Just tested the AppSync Console and it seems fine there.
createdAt timestamp in the AppSync console is the same format as local versions e.g. 2021-06-30T20:20:07.920Z

Hey @bacon1097 I re-tested this in Windows 10 with changing createdAt types in between creating records to no avail. Are you still seeing this issue after removing the amplify/mock-data directory and recreating the records? Is this sorting issue affecting other models as well?

Hi @josefaidt, looks like deleting the mock directory and recreating the records worked. Sorting works as expected now.

Potentially a warning or defect still available here? To alert people that recreating the mock records is required when adding a sort key to a model.

Hey @bacon1097 glad this is working for you! I will keep an eye out for future reports of sort-related issues in mock.


Emotes?

Emotes not working for me? On latest build of better discord and using PTB.

You're not alone. Discord changed something and now BetterDiscord code is broken. Because span.markup.message-content no longer exists in new versions.
But I can get all displayed currently messages with this method:
$('div.message').each(
  (index, message) => {
     message = $(message);

     var sender = message.find('.user-name');
     sender = sender[0] ? sender[0] : null;
     sender = sender ? $(sender).text() : "previous";

     console.log(`Sender: ${sender}`);

     var messageText = message.find('.markup');
     messageText = messageText[0] ? messageText[0] : null;
     messageText = messageText ? $(messageText).text() : "No text";
     messageText = messageText.trim();
     messageText = messageText === "" ? "No text (it's can be image)" : messageText;

     console.log(`Text: ${messageText}\n----------------------------`);
 }
);

So there exists a way to fix it, but it's not my work :d

PTB is not really supported.