Added instructions to run and test chaincode in dev mode

TODO: An API.md file containing the chaincode API for both versions.

Made a small correction to the formatting but otherwise looks good.  I'll merge as soon as travis is done.


support proxy setting for openai; add new commands

proxy settings, as stated in #110
add /history command to display dialogs

add an option in config ask_on_timeout to confirm before starting a new dialog on timeout

I also want to use proxy setting for openai.


fix(editors/cleanup) Cleanup of datatypes is buggy

Closes #1008
I have not been able to break this for some time now. Most of my recent tests have been around removing IEDs in large scd files and see that the templates still validate (everything is there that should be) and there are no "left behind" templates.
I have tried to work more with ids than elements to improve speed. Still, it hangs in Chrome frequently, and we have to click "Wait" to make it continue on large files. I think we need a way to deal with long-running tasks in the UI in future. Should it block with a modal/dialog? Should it be turned into a "this task will be completed in the background" with a task queue? Not today's problem... I guess :wink:
I will be grateful for a review and perhaps testing with some scd files or project files would be prudent.

Thank you for reviewing this. :+1:
I have made the changes requested, and will merge this, hoping that the test failure will disappear.

Regrettably now main is broken (I am sorry :cry:), and I can see why now.
When I do a git diff main from this branch, or I look at the changed files in Github I see:
\ No newline at end of file
diff --git a/test/unit/Logging.test.ts b/test/unit/Logging.test.ts
index 46fbd866..0627f57e 100644
--- a/test/unit/Logging.test.ts
+++ b/test/unit/Logging.test.ts
@@ -30,7 +30,7 @@ describe('LoggingElement', () => {

   it('cannot undo warning messages', () => {
     element.dispatchEvent(
-      newLogEvent({ kind: 'warning', title: 'test warning' })
+      ({ kind: 'warning', title: 'test warning' })
     );

I don't see this when I open test/unit/Logging.test.ts on either this branch or main.
This is a mysterious and new evil in my world.


Value tag

Hi Fatih,
I use the structs package for creating a flat map which contains the arguments I need for a named query. See the function https://godoc.org/github.com/jmoiron/sqlx#DB.NamedExec
However I run into issues with for example my NullTime type. My NullTime type is similar to the NullX types in the sql package of the standard library. See for example https://golang.org/pkg/database/sql/#NullBool
I have something like this:
type Record struct {
    LastStartAt NullTime
}

type NullTime struct {
    Time time.Time
    Valid bool
}

If I create a map from the Record, I would like to get an entry "LastStartAt" with the time.Time value and not a map[string]interface{}.
I saw no way to get this result with the current functionality of the package, so I have implemented support for a "value" tag similar to the already implemented "string" tag.
If the "value" tag is set and the child struct implements the Valuer interface, the return value of the Valuex() function is set in the final map.
So I end up with something like the following and get the map I need.
type Record struct {
    LastStartAt NullTime `structs:",value"`
}

type NullTime struct {
    Time time.Time
    Valid bool
}

func (nt NullTime) Valuex() interface{} {
    return nt.Time
}

What do you think about this? Is it something you like to add to the package? If so, I could implement a test and write some documentation.
And if you like it, have you a suggestion for the function name? I'm not very happy with Valuex(), but Value() could not be used because it would result in a conflict if the sql/driver.Valuer interface of the standard library is also implemented by a type.
Best regards,
Marco

Coverage decreased (-1.01%) to 98.469% when pulling 47353f78298f3a71cf598e7607d179d12b4557a7 on webguerilla:2016.06.23-valuer into bfcf7eedca5eca84631f95fe4b46d968e0a03500 on fatih:master.

Hi @webguerilla
Did you tried omitnested ? This doesn't follow structs recursively and just stop. So in your case you should be able to get the value.

Hi @fatih
Yes, that does not exactly what I need. If I use omitnested I get the NullTime value in the map, however I need the time.Time value from the NullTime with the key LastStartedAt. Thus flatten does also not work...

When you do a omitnested. You can get the type NullTime. After that, you can access it easily:
n := val.(NullTime)
n.Time
n.Valid

Does this not work? Can you post a play.golang.org snippet where it shows why omitnested doesn't work? I'm just curious.
You're idea is great btw, nothing against it. We already use the fmt.Stringer interface for map keys, so I'm totally ok adding something for map values as well. But before I want to be sure if omitnested solves your problem or not :)

A play.golang.org snippet would be difficult because a database is involved, but I can give you some more context.
I have the following types:
type Record struct {
    Form
    ID int64
    LastStartAt NullTime
}

type Form struct {
    ValueX int64
}

type NullTime struct {
    Time time.Time
    Valid bool
}

A Record type holds all values that are stored in the database. The values of the embedded Form type are also stored in the database, but they are updateable by the end users and thus separated from the Record. The separation is mainly for security reasons. I bind incoming requests to the Form type and make on this way sure that the end users could not manipulate values which are controlled by the system, like for example LastStartAt.
When I now insert or update a database record, I dynamically build a named query. For example with:
query := fmt.Sprintf("UPDATE table SET %s WHERE id = %d;", dbutils.ColumnPlaceholderPairsForUpdateSet(record), record.ID)

The resulting query looks somewhat like:
UPDATE table SET ValueX = :ValueX, LastStartAt = :LastStartAt WHERE id = 1;

Then I create a flat map with the structs package and execute the query:
mapx := structs.Map(record)
db.NamedExec(query, mapx)

The NamedExec function does not work well with nested types and therefore I convert the type to a flat map. The keys have to match the names of the named placeholders. In this map I need the key LastStartAt with the value of time.Time.
I could set this key manually, but I like to prevent manual post processing for each type...
Do you understand the issue better with this explanation? If not, maybe I could think about constructing a useful snippet.

The keys have to match the names of the named placeholders. In this map I need the key LastStartAt with the value of time.Time. I could set this key manually, but I like to prevent manual post processing for each type...

Alright, this is indeed a custom logic you want to include in this package. My suggestion would not help  you as it would add a different type. You don't want the NullTime to be stored, insted you want NullTime.Time
I'm ok for this PR now, but we need to fix and add a couple of things:

We need a test to cover this new feature
The Valuer interface needs a doc comment
I think Valuex is not a good method name. Maybe StructValue() or something else would be better. Also we need to document this in the Map doc comment as well

Hi @fatih
Sorry, it took some time, but now I have implemented the open tasks.
Please let me know if you have some questions about the changes or something needs to improved further.
Best regards
Marco

Coverage remained the same at 100.0% when pulling 1ae9b40b1513c497580e5dbdd742c13404de8ea6 on webguerilla:2016.06.23-valuer into be738c8546f55b34e60125afa50ed73a9a9c460e on fatih:master.

Hi,
Unfortunately, I'm archiving this project and will no longer maintaining it. For more information, please read my blog post: Taking an indefinite sabbatical from my projects.
Thanks for the feedback and contribution.


[question] How to extend identity model appropriately

In reference to current project architecture where should I create new entity model when I want to create sth like Department Entity? Each of department will have list of Users so creating department model class in Domain project will cause circular dependency for Infrastructure project.
Any suggestions how to deal with it?

Have the same question 🙋 but probably use the discussions tab to ask questions please, thanks!

This is a must in an enterprise application. We should find the best option to create this. Since many applications restricts the views based on the department you're in, and mybe you can have multiple departments....


No releases available on github.

https://nlmaps.nl/docs.html mentions:

Finally, you will need the nlmaps library itself, which you can download from the latest release on Github.

But there are no releases when I follow the link.

@jieter until this gets fixed the relevant files can be found in the dist directory.

Releases are available now.


wrap reqwest::Response to match Errors

Motivations

[taken from #57]
There is currently no wrapper for reqwest::Response. As a result, resp.body().await? [...]

... returns a reqwest::Error instead of reqwest_middleware::Error.
Solution
It would be possible to create wrapper types but this is not really feasible.
Instead there should be a wrapper to make the api more uniform.
Additional context
I'm implementing reqwest-middleware for https://github.com/peanutbother/api-client  to extend its features I'm trying to change to reqwest-middleware which introduces non uniform apis:
https://github.com/peanutbother/api-client/blob/main/src/lib.rs#L263
where
self.request(::reqwest::Method::$method, format!($url).as_str(), $crate::Body::Json(request)).await?.json().await

fails due to the response not being wrapped.

I might be missing something, if you change your return type to reqwest_middleware::Error, wouldn't it work with reqwest-middleware as-is? You'd need to change it anyways if we were to apply this suggestion here, no?

the call to response.json().await returns a reqwest::Result instead of a reqwest_middleware::Result
I solved it by mapping the error for now but it would be more convenient if the Result type would be consistent.


Inaccurate conversion of big integer values

Integer values close to INT64 maximum get unexpectedly changed to other values.
example-openapi-source.yaml:
openapi: 3.0.0
info:
  title: Simple API
  version: 1.0.0
paths:
  /example:
    get:
      summary: Example endpoint
      parameters:
        - name: number
          in: query
          required: true
          schema:
            type: integer
            format: int64
            minimum: 0
            maximum:<PHONE_NUMBER>854775807
      responses:
        '200':
          description: Successful response

To Reproduce
Steps to reproduce the behavior:

Run redocly bundle example-openapi-source.yaml -o example-openapi-redocly-output.yaml

Expected behavior
The value of maximum in example-openapi-redocly-output.yaml is the same as in example-openapi-source.yaml
Actual behavior
The value of maximum in example-openapi-redocly-output.yaml is equal to<PHONE_NUMBER>854776000
Redocly Version(s)
1.6.0
Node.js Version(s)
v20.10.0
Additional context
It's caused by this line https://github.com/nodeca/js-yaml/blob/master/lib/type/int.js#L129
parseInt('9223372036854775807', 10) returns<PHONE_NUMBER>854776000
JavaScript's maximum safe number is<PHONE_NUMBER>740991, but in the openai config a larger number was used<PHONE_NUMBER>854775807.

This should be reported to openai if they are using an invalid JS maximum number.


@conda-forge-admin, please add bot automerge

Issue:

Environment (conda list):

$ conda list

Details about  conda and system ( conda info ):

$ conda info

I don't think that will actually ping them unless it is in the body of a comment

I've used this countless times before, it's supposed to activate a bot. Seems to be broken at the moment.

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/pyvistaqt-feedstock#2.

@banesullivan :)


[locale] Extend cs locale with name of the months in genitive

In Czech, it is possible to use also declined form of the month name instead of the nominative case.
This commit adds those declined names of the months.
@radekdostal @marxsk @petrbela - please verify this patch as locales have to be verified by native speakers.
This PR is meant to replace solution suggested in https://github.com/moment/moment/pull/4765 (and agreed with @marxsk in https://github.com/moment/moment/pull/4765#issuecomment-419863315)
Discussion:
Pro of this solution is that is it easier to understand because plain regexes or their arrays are used instead of anonymous function.
Con is that "červenec" must precede "červen" in the monthsRegex and monthsStrictRegex to match properly.

Coverage increased (+0.1%) to 94.745% when pulling 3319adbddbf2e3d0de39e3f7421c6cc20768d2d6 on saxicek:patch-1 into 2e2a5b35439665d4b0200143d808a7c26d6cd30f on moment:develop.

Travis failed on locale/ka.js - which was untouched by this PR.

I haven't kept up with how monthsStrict works these days. Is the inflected version automatically used after an ord date (like "1. cervna")?
I feel like we should add a test case for the format function (is it the LL format?), or whichever publicly available interface this change affects.

Con is that "červenec" must precede "červen" in the monthsRegex and monthsStrictRegex to match properly.

I'm okay with this as long as we add a comment to the source file why this workaround is necessary.

@petrbela This change affects date parsing, not formatting. Therefore not sure about your suggestion to add test case for the format function.
Addressed the request to document why months are not in order in the regular expressions.
Unfortunately tests are still failing due to https://github.com/moment/moment/issues/4762.

Ah right makes sense. I'm just wondering whether the functionality should be symmetric; if we can parse a specific format, we should be able to print (format) it, too. As far as I can see, that's not available right now. What do you think?

Yes, it does make sense. But unfortunately I am unable to dedicate more time to design and implement this. Any volunteers?

imho the impact of having function symmetric is not that big. Additionally, it makes sense to make this available also for the other languages. And it is possible that in various languages this 'genitive-case' is oversimplifaction.

The thing is I don't know is how would you switch between the 2 forms - new setting? Where? On the other hand if someone needs that then (s)he can just simply overload locale definition using:
moment.updateLocale('cs', {
    months : 'ledna_února_března_dubna_května_června_července_srpna_září_října_listopadu_prosince'.split('_')
});

You could also introduce new locale variant but still - I don't think it is worth the effort.

@saxicek what's the status of this? looks like you have approval.

Yes. I think those involved in the discussion are ok with the solution. We were waiting for #4762 to pass CI tests.


Implement Volume Snapshotting

First off, thanks for this awesome project!
What
Are there any plans to support k8s Volume snapshotting with lvm snapshots, which would support various backup solutions in kubernetes relying on snapshots to be available ?
How
Describe how to address the issue.
Checklist

[ ] Finish implementation of the issue
[ ] Test all functions
[ ] Have enough logs to trace activities
[ ] Notify developers of necessary actions

@rslinckx
Thank you for your comment !!
I'm afraid we don't have any plan to support the volume snapshotting feature for now.
Your PR is always welcomed if you'd like to work on it, though.

working on #385 #446

the problem is  how to recover quickly  from snapshot?

I just want to write here for anyone looking at this today or in the future: TopoLVM supports expiremental snapshots for Thinly Provisioned volumes.

As mentioned above, we have a snapshot feature for thin volumes now.
For thick, it may be hard to implement as denoted, so we have no plan to forward it.


impossible to create a new module with the nativescript-schematics cli

Hi guys,
I try to create a new module
ng g m mymodule

but I have this error:
Schematic input does not validate against the Schema: {"routing":false,"routingScope":"Child","flat":false,"commonModule":true,"name":"mymodule","project":"sps-poc","path":"src\\app","spec":true}
Errors:

  Data path ".path" should match format "path".

For component, it's ok and If I remove the nativescript/schematics cli from angular.json, it works fine for module.
Am I doing something wrong?
(I confess, I already wasted around 1 hour because I didn't pay attention to the --bundle flag! ^^
Thanks!
fof
(amazing solution and work btw!!!)
env
Angular CLI: 6.1.4
Node: 8.11.4
OS: win32 x64
Angular: 6.1.4
nativescript/schematics: 0.2.5
 "devDependencies": {
    "@angular-devkit/build-angular": "~0.7.0",
    "@angular/animations": "^6.1.4",
    "@angular/cdk": "^6.4.6",
    "@angular/cli": "~6.1.0",
    "@angular/compiler-cli": "~6.0.3",
    "@angular/material": "^6.4.6",
    "@nativescript/schematics": "^0.2.5",
    "@types/jasmine": "~2.8.6",
    "@types/jasminewd2": "~2.0.3",
    "@types/node": "~8.9.4",
    "codelyzer": "~4.2.1",
    "jasmine-core": "~2.99.1",
    "jasmine-spec-reporter": "~4.2.1",
    "karma": "~1.7.1",
    "karma-chrome-launcher": "~2.2.0",
    "karma-coverage-istanbul-reporter": "~2.0.0",
    "karma-jasmine": "~1.1.1",
    "karma-jasmine-html-reporter": "^0.2.2",
    "nativescript-dev-sass": "~1.6.0",
    "nativescript-dev-typescript": "~0.7.0",
    "nativescript-dev-webpack": "^0.15.0",
    "protractor": "~5.3.0",
    "ts-node": "~5.0.1",
    "tslint": "~5.9.1",
    "typescript": "2.7.2"
  }

Hi @fofBdx! I try to reproduce the issue, but I'm failing so far. Could you please try to isolate the problem in a github repo?

Hi @sis0k0! ok, it must be my config so. Strange. I only do a "ng new" and it fails after.
ng new --collection=@nativescript/schematics shared-test --shared

nothing particular
ng g m mymod

same error: Data path ".path" should match format "path".
I'll verify that deeper and close,

@sis0k0 -> Yep, it works fine with a fresh ubuntu install.
With windows, I can't make it work even with node & cli reinstall. Problem with my config? Pb with win- paths?
Since I seem to be the only one, I guess it's my config
Cheers


Allow MSRIOGroup to be used on systems with restricted allow lists

If a control is not in the allow list, throw only when
the user tries to write the control, not when the save
happens.

fixes #1395

Duplicate

Duplicate


GIF support in PhotoBubbleView?

Hi, it would be nice to support Animated GIF when using the PhotoBubbleView in ChattoAdditions.

@allaire I would implement a completely new cell for this purpose. It would be hard to support both gif and static images inside one cell. Any contribution is appreciated. I'm not sure that we will do in in the near future (since we don't need GIF support in our main app).


University of Nottingham

@TrueMemer Is everything OK with the request? Did you close it mistakenly or on purpose?

@philipto I notice domain in blacklist only after creating pull request.


Investigated, not web view. I think its actually the text bitmap rendering b/c even tho the size is done off-main, the content is rendered as you scroll to the bottom of the issue.


Add space between sidebar links on fern docs

Very minor - I think there should be a little space between the links on the sidebar. Feels a little off that they are touching when you hover over the link below the selected page

@kgowru have a take here?


Request: could you make a Colab using Paraphrase-Generator

Hey,
Great stuff providing this paraphrase generator. I wonder though if you could quickly push a working Colab using this generator without streamlit.
In other words, could you show how to replicate the generation of paraphrase given a sentence with this repo on Google Colab?
I currently have a good number of issues, probably linked to the libraries. Would be great to simply replicate the great work done here on a Colab environment.
Thanks,

I think it's already there inside the Colab notebooks folder-> Paraphrase.ipynb. This was the notebook I used while training it. So you can find the inference part in this too.

I think it's already there inside the Colab notebooks folder-> Paraphrase.ipynb. This was the notebook I used while training it. So you can find the inference part in this too.

I took a look at it but I am not sure I can replicate it as you save the pretrained model after fine-tuning it.
I pulled the git repo and did the following in Colab but it is not working:
from transformers import AutoTokenizer, AutoModelForSeq2SeqLM

tokenizer = AutoTokenizer.from_pretrained("./T5_Paraphrase_Paws")
model = AutoModelForSeq2SeqLM.from_pretrained("./T5_Paraphrase_Paws")

sentence = "This is something which i cannot understand at all"
text =  "paraphrase: " + sentence + " </s>"
encoding = tokenizer.encode_plus(text,pad_to_max_length=True, return_tensors="pt")
input_ids, attention_masks = encoding["input_ids"].to("cuda"), encoding["attention_mask"].to("cuda")

outputs = model.generate(
    input_ids=input_ids, attention_mask=attention_masks,
    max_length=256,
    do_sample=True,
    top_k=200,
    top_p=0.95,
    early_stopping=True,
    num_return_sequences=5
)

for output in outputs:
    line = tokenizer.decode(output, skip_special_tokens=True,clean_up_tokenization_spaces=True)
    print(line)

Some guidance from this stage would be great.

I took a look at it but I am not sure I can replicate it as you save the pretrained model after fine-tuning it.
I pulled the git repo and did the following in Colab but it is not working:
from transformers import AutoTokenizer, AutoModelForSeq2SeqLM

tokenizer = AutoTokenizer.from_pretrained("./T5_Paraphrase_Paws")
model = AutoModelForSeq2SeqLM.from_pretrained("./T5_Paraphrase_Paws")

sentence = "This is something which i cannot understand at all"
text =  "paraphrase: " + sentence + " </s>"
encoding = tokenizer.encode_plus(text,pad_to_max_length=True, return_tensors="pt")
input_ids, attention_masks = encoding["input_ids"].to("cuda"), encoding["attention_mask"].to("cuda")

outputs = model.generate(
    input_ids=input_ids, attention_mask=attention_masks,
    max_length=256,
    do_sample=True,
    top_k=200,
    top_p=0.95,
    early_stopping=True,
    num_return_sequences=5
)

for output in outputs:
    line = tokenizer.decode(output, skip_special_tokens=True,clean_up_tokenization_spaces=True)
    print(line)

Some guidance from this stage would be great.

pip install transformers
pip install sentencepiece

from transformers import T5Tokenizer, T5ForConditionalGeneration

tokenizer = T5Tokenizer.from_pretrained("t5-base")
model = T5ForConditionalGeneration.from_pretrained("Vamsi/T5_Paraphrase_Paws")

sentence = "This is something which i cannot understand at all"
text =  "paraphrase: " + sentence
encoding = tokenizer(text,padding=True, return_tensors="pt")
input_ids, attention_masks = encoding["input_ids"], encoding["attention_mask"]

outputs = model.generate(
    input_ids=input_ids, attention_mask=attention_masks,
    max_length=256,
    do_sample=True,
    top_k=200,
    top_p=0.95,
    early_stopping=True,
    num_return_sequences=5
)

for output in outputs:
    line = tokenizer.decode(output, skip_special_tokens=True,clean_up_tokenization_spaces=True)
    print(line)

Hope this helps !!

pip install transformers
pip install sentencepiece

from transformers import T5Tokenizer, T5ForConditionalGeneration

tokenizer = T5Tokenizer.from_pretrained("t5-base")
model = T5ForConditionalGeneration.from_pretrained("Vamsi/T5_Paraphrase_Paws")

sentence = "This is something which i cannot understand at all"
text =  "paraphrase: " + sentence
encoding = tokenizer(text,padding=True, return_tensors="pt")
input_ids, attention_masks = encoding["input_ids"], encoding["attention_mask"]

outputs = model.generate(
    input_ids=input_ids, attention_mask=attention_masks,
    max_length=256,
    do_sample=True,
    top_k=200,
    top_p=0.95,
    early_stopping=True,
    num_return_sequences=5
)

for output in outputs:
    line = tokenizer.decode(output, skip_special_tokens=True,clean_up_tokenization_spaces=True)
    print(line)

Hope this helps !!


Azure AD Premium P1 license requirements for dynamic device groups?

Hello,

Note
This feature requires an Azure AD Premium P1 license for each unique user that is a member of one or more dynamic groups. You don't have to assign licenses to users for them to be members of dynamic groups, but you must have the minimum number of licenses in the tenant to cover all such users. For example, if you had a total of 1,000 unique users in all dynamic groups in your tenant, you would need at least 1,000 licenses for Azure AD Premium P1 to meet the license requirement.

Can you please clarify if this also applies to dynamic device groups?
It would make Windows Autopilot deployment profile assigning much more difficult as it's usually done with dynamic device groups.

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

ID: 5f7a4070-1be8-5f1f-0092-68fb6b9e2305
Version Independent ID: cd34312f-b507-affe-555e-1e0c63e7d494
Content: Rules for dynamic group membership - Azure AD
Content Source: articles/active-directory/users-groups-roles/groups-dynamic-membership.md
Service: active-directory
Sub-service: users-groups-roles
GitHub Login: @curtand
Microsoft Alias: curtand

@TechTrooper Thanks for your feedback! We will investigate and update as appropriate.

Hey @TechTrooper this should apply to dynamic device groups as well, i'm going to take a look into this a bit further to confirm.

hey @TechTrooper I'm following up on this, apologies for the late reply.
You shouldn't need an aad premium license for each device. Please let me know if you have anymore questions in regards to this, in addition to that, I'll go ahead and engage some more members to add a note into the document saying that devices don't require premium AAD licenses,
CC: @curtand

We've made an update to the docs accordingly, if there are any issues with this merge please let us know by opening a new issue with a reference to this issue. As we've made the change to the docs, I'll be closing out this github issue now @techtrooper


Secure domain with SSL

https://news.ycombinator.com/item?id=8880659

I'm currently hosting my static website on a VM. I'd like to avoid being personally responsible for keeping the system secure, so I'm looking for a service that will host my static website; ideally on a CDN. Here are my requirements:

Content must be transmitted via https end-to-end.

Content must be served from custom domain

Support for directory indexes (show contents of index.html when an URL with trailing slash is accessed)

I thought this would be easy, but all services I've found seem to have some kind of drawback.
Amazon S3 + Cloudfront: If I use Cloudfront with S3 buckets directly, there is no support for directory indexes. If I use Cloudfront with S3 website endpoints, the content is transferred only via http between S3 and cloudfront edge servers.
Rackspace cloudfiles: If I understand their docs correctly, they don't support custom domains with SSL
DreamObjects + DreamSpeed: Apparently doesn't support apex domains, and also doesn't support custom domains with SSL
Anybody know any other options?
Does this mean I need to continue to run my own VM just to serve a static website over SSL?

Answer:

GitHub pages + CloudFront (with SNI) does all three. It costs ~$2 a month and you can deploy via Git. It's lovely.

https://aws.amazon.com/blogs/aws/server-name-indication-sni-and-http-redirection-for-amazon-cloudfront/
https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_server-certs.html


Cannot create incident or metric

I am trying to create an incident, and it is failing with bad request
Post:
POST /api/v1/incidents HTTP/1.1
Content-Type: application/json
accept-encoding: gzip
X-Cachet-Token: 7lipnzcreXL2eXQTYS9a
Accept: */*
Host: <IP_ADDRESS>
Connection: close
User-Agent: Paw/2.2.2 (Macintosh; OS X/10.10.3) GCDHTTPRequest
Content-Length: 85

{"name":"Monkey Farts","message":"The title says it all","status":1,"component_id":1}

Reponse:
HTTP/1.0 400 Bad Request
Date: Wed, 24 Jun 2015 23:10:52 GMT
Server: Apache/2.4.6 (Red Hat Enterprise Linux) PHP/5.6.10
X-Powered-By: PHP/5.6.10
Cache-Control: no-cache, private
Content-Length: 111
Connection: close
Content-Type: application/json

{"errors":[{"status":400,"title":"Bad Request","detail":"The request cannot be fulfilled due to bad syntax."}]}

what am I doing wrong ?

Thanks for the bug report! This is now fixed :)

@jbrooksuk I did a fresh pull, and set it up again, but I am still getting the same error:
# curl -X POST -H 'Accept: */*' -H "accept-encoding: gzip" -H "Content-Type: application/json" -H "X-Cachet-Token: 9yMHsdioQosnyVK4iCVR" http://localhost/api/v1/incidents -d '{
name: "Monkey Farts",
message: "The title says it all",
status: 1,
component_id: 1,
}'

{"errors":[{"status":400,"title":"Bad Request","detail":"The request cannot be fulfilled due to bad syntax."}]}

Are you using Postgres, MySQL or SQLite?

@jbrooksuk MySQL (5.6)

I've just tried the demo and it works (also using Paw):
Request:
POST /api/v1/incidents HTTP/1.1
X-Cachet-Token: 9yMHsdioQosnyVK4iCVR
Content-Type: application/json
Cookie: __cfduid=d65c54b052f92169f515864c9a118770f1435218005
Host: demo.cachethq.io
Connection: close
User-Agent: Paw/2.2.1 (Macintosh; OS X/10.10.3) GCDHTTPRequest
Content-Length: 85

{"name":"Monkey Farts","message":"The title says it all","status":1,"component_id":1}

Response:
HTTP/1.1 200 OK
Server: cloudflare-nginx
Date: Thu, 25 Jun 2015 18:15:37 GMT
Content-Type: application/json
Transfer-Encoding: chunked
Connection: close
Cache-Control: no-cache
Set-Cookie: laravel_session=eyJpdiI6IkZwaEI0V1FFSUhuTnNYaDdmbGwxY1VyWFh3K2FIalVCUUtDRzlXMDBhRnM9IiwidmFsdWUiOiJ6OWlhNkIyNzMrTStXNlwva09FOWRUSkdJWExFQlNJMlYyT2tjR3dpaXFpeHBqK0tVSnp1dkJuNEdZeU54RzR3d0FzUURMXC8wNStweG8raFArNFNrQWVnPT0iLCJtYWMiOiIwN2RiN2Y4NzVjYjc4ZjMwZmZmYTI5NjFlZWYxNWY2ZTQ3YmFmMjIzYzQ2OWI3OTg5YmE2ODBlN2JmYjgxMDA2In0%3D; expires=Thu, 25-Jun-2015 20:15:37 GMT; Max-Age=7200; path=/; httponly
Strict-Transport-Security: max-age=0; includeSubDomains; preload
X-Content-Type-Options: nosniff
CF-RAY: 1fc2a8a8177e061c-LHR

{"data":{"name":"Monkey Farts","message":"The title says it all","status":"1","component_id":"1","visible":1,"updated_at":"2015-06-25 19:15:37","created_at":"2015-06-25 19:15:37","id":4,"human_status":"Investigating","scheduled_at":"2015-06-25 19:15:37"}}

Thanks. It looks like I had an issue with curl.

:)

Thanks @jbrooksuk.
whats weird is that, curl works now, but I am using the cachet-monitor tool, and that throws the same error.

You'll need to open an issue on cachet-monitor for that :)


[staging] sconsPackages.*: use python3

Motivation for this change
Attempt to use python3 for all scons builds.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

sorry for spam, wrong base branch

related: https://github.com/NixOS/nixpkgs/issues/148779

This build, but fail to execute any downstream packages

scons_latest uses python3, however, mongodb < 4.2 cannot use the newer python3 version. mongodb should start pointing to a newer version.


Decouple from Triton

Congratulations team! This is a seriously impressive model.
Thank you also for sharing the weights and supporting the open-source community!
FYI - I was able to successfully fine-tune the 2.8B model and completely demolish squad, showing strong reasoning abilities.
I'm wanting to see how far we can push the inference speed of this model, but the triton dependency is preventing loading it on CPU or doing an ONNX conversion.
Do you have any advice to decouple this dependency or alternative approaches?
Any help would be appreciated!

Great to hear about the Squad result!
I don't have much experience with CPU or ONNX deployment. I mostly work with GPUs.
The model architecture is quite different from what's commonly used (Transformers), so there's probably quite a bit to do to make it compatible with the ecosystem.
Some of the operations are implemented in CUDA (selective scan), idk if that would work with ONNX.
The causal_conv1d has a CUDA implementation but you can also just call pytorch.
Triton is used for RMS norm I think, and you can replace that with a reference Pytorch implementation.

I was also interested in a CPU implementation; I was curious if the functions suffixed with _ref are reference implementations (like this one https://github.com/state-spaces/mamba/blob/main/mamba_ssm/ops/selective_scan_interface.py#L311) that can be used to guide new implementations?
In the past I had quite some success porting CUDA/OpenCL kernels to CPU using ISPC (which has very similar programming model) but I saw that C10 & CUB are used here and I don't know them very well.

Modified version to work on CPU is available on this fork
I chopped a lot of code, but it works

Congratulations! But I have a question that why the 130M model doesn't preform well in training, only 15% accuracy. Am I doing something wrong?


ComplexOutput data as reference always generates a file named "input.csv", should be "output".

Description
When returning a ComplexOutput as Reference (output as_reference is True), the filename generated by the server (and used in the built URL) is always "input", eg "input.csv" for a "txt/csv" output, or "input.xml" for an "application/xml" output. This is misleading to users as this is actually the Output file.
After some digging through the sourcecode, I found where that name is set:
https://github.com/geopython/pywps/blob/d0bb9787207e670f4cf8ec5fc3d56abb284226e1/pywps/inout/basic.py#L271-L276
It appears there is no way to set this name on the ComlexOutput object, or on the FileStorage object or on the DataHandler object.
Environment

operating system: Ubuntu 22.04
Python version: 3.8
PyWPS version: 4.5.2
source/distribution
[ ] git clone
[ ] Debian
[x] PyPI
[ ] zip/tar.gz
[ ] other (please specify):

Hello,
You can change the output name by storing output data into a file.
https://github.com/geopython/pywps/blob/6293f3d5f69470b252863a838160f6959c83e5cf/pywps/inout/storage/file.py#L29C1-L35C31
Best regards


Update addAndScheduleOnFirst parameter name from func to f

It's just a little nitpick.
The parameters of the other functions (like runAndCaptureDeps, derive, ...etc)  use f as short for function, but only the addAndScheduleOnFirst function uses func as short for function, so I fixed it for coherence.

Thank you so much, Lee Byonghun!


Does not work on macos

On macos, running WPP_Whatsapp examples I get
  File "/Users/<USERNAME>/anaconda3/envs/join312/lib/python3.12/site-packages/PlaywrightSafeThread/browser/threadsafe_browser.py", line 413, in check_is_install
    k["creationflags"] = subprocess.CREATE_NO_WINDOW
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'subprocess' has no attribute 'CREATE_NO_WINDOW'

pip install PlaywrightSafeThread -U


Indexing: Improve vectors throughput

Purpose

AOAI supports batching for ada-002. This has increased through put and reduce rate limit errors. I have added a flag to disable it if it causes any issues. Tests looks good.
Does this introduce a breaking change?

[ ] Yes
[x ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[x ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

@srbalakr @chuwik
Another suggestion for reducing chance of rate limits and reducing overall deploy time: removing some of the sample documents. I actually do that myself always, to save deployment time. That would give developers a faster initial deploy and also reduce costs of their first experimental deploy. We would need to leave enough documents to answer the sample questions, of course.
That could be done in a follow-up PR if you think that's a good idea.
Another thought I had is to increase the ada TPM to 60. The main drawback is that developers are more likely to run into the capacity errors on later deployments, due to OAI counting existing TPMs against them (https://github.com/Azure/bicep-types-az/issues/1660).

I applied the 3 changes that Pamela proposed to my repo and was able to successfully deploy in 22 minutes with only 3 429's (Rate limited...). In addition, all the sample questions on the home page worked properly.
My previous attempted deployment failed while trying to create the embeddings for the Northwind_Health_Plus_Benefits_Details.pdf file, which took a long time, used a lot of my TPM, and was unnecessary for answering the sample questions. In addition, when it failed on that doc, it stopped processing the remainder of the docs.
Pamela's proposed changes:

Remove the 3 nice-to-have, but unnecessary PDFs:
Northwind_Health_Plus_Benefits_Details.pdf
Northwind_Standard_Benefits_Details.pdf
PerksPlus.pdf
Increase the TPM from 30 to 60
Increase the min wait time from 1 to 15

I'm pretty certain the biggest impact came from removing the PDFs, but the other changes provide some nice buffer to ensure a successful deployment.

I applied the 3 changes that Pamela proposed to my repo and was able to successfully deploy in 22 minutes with only 3 429's (Rate limited...). In addition, all the sample questions on the home page worked properly.
My previous attempted deployment failed while trying to create the embeddings for the Northwind_Health_Plus_Benefits_Details.pdf file, which took a long time, used a lot of my TPM, and was unnecessary for answering the sample questions. In addition, when it failed on that doc, it stopped processing the remainder of the docs.
Pamela's proposed changes:

Remove the 3 nice-to-have, but unnecessary PDFs:
Northwind_Health_Plus_Benefits_Details.pdf
Northwind_Standard_Benefits_Details.pdf
PerksPlus.pdf
Increase the TPM from 30 to 60
Increase the min wait time from 1 to 15

I'm pretty certain the biggest impact came from removing the PDFs, but the other changes provide some nice buffer to ensure a successful deployment.

Hi @charris-msft  you try the batch support changes in this branch. Our team tested with large dataset and batch support increased the throughout.

@srbalakr - regarding :

Hi @charris-msft did you try the batch support changes in this branch. Our team tested with large dataset and batch support increased the throughout.

I have not had a chance to try that yet. I'm hoping I'll find some time tomorrow.


Mycroft doesn't respond to wake word or button when playing radio.

Describe the bug
Mycroft II doesn't respond to wake word or listen to commands when radio is playing.
To Reproduce
Steps to reproduce the behavior:

Tell mycroft to play radio
Allow radio to play
Use the wake word
Mycroft will not respond and the LED will not light up.

This behavior also occurs when you press the button and the LED is lit up. Mycroft just doesn't appear to be listening.
Expected behavior
Expected behavior is that mycroft
Log files
Logs don't appear to register anything after I begin playing despite pressing the button and issuing commands.
-- Logs begin at Thu 2019-02-14 10:12:03 UTC. --
Dec 29 17:13:10 localhost.localdomain python[588]: DEBUG:mycroft.util.log:Utterance after cleaning: ''
Dec 29 17:13:10 localhost.localdomain python[588]: DEBUG:mycroft.util.log:ENDPOINT: stations/search?language=english&limit=1000&hidebroken=true&order=clickcount&reverse=true&tagList=classic+rock
Dec 29 17:13:10 localhost.localdomain python[588]: DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): at1.api.radio-browser.info:443
Dec 29 17:13:14 localhost.localdomain python[588]: DEBUG:urllib3.connectionpool:https://at1.api.radio-browser.info:443 "GET /json/stations/search?language=english&limit=1000&hidebroken=true&order=clickcount&reverse=true&tagList=classic+rock HTTP/1.1" 200 None
Dec 29 17:13:14 localhost.localdomain python[588]: DEBUG:mycroft.util.log:Successful response from RadioBrowser server: https://at1.api.radio-browser.info/json/
Dec 29 17:13:14 localhost.localdomain python[588]: DEBUG:play-radio.mark2:Getting mime type for http://softrock-ice.purestream.net/softrock.mp3
Dec 29 17:13:14 localhost.localdomain python[588]: DEBUG:play-radio.mark2:Getting mime type for Soft Rock Radio
Dec 29 17:13:14 localhost.localdomain python[588]: DEBUG:play-radio.mark2:Attempting to check mime type: try 1
Dec 29 17:13:14 localhost.localdomain python[588]: DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): softrock-ice.purestream.net:80
Dec 29 17:13:14 localhost.localdomain python[588]: DEBUG:urllib3.connectionpool:http://softrock-ice.purestream.net:80 "HEAD /softrock.mp3 HTTP/1.1" 200

Environment (please complete the following information):
Mark II
mycroft-dinkum

I see this issue intermittently when playing radio or playing music from a local usb drive.  Sometimes the only way to fix it is to pull the power plug to restart.

Sometimes I am able to get the radio to stop by pressing the stop button on screen. This does not work 100 percent of the time. Power cycling is the only reliable way so far.

This is related to this bug probably: #46


Identifier defined in a named block can not be resolved ('Failed to detect width for identifier ...')

A register, declared inside a named block can not be resolved (Yosys reports that it doesn't know the 'width' of the identifier, but that is probably due to it not resolving it properly).
Consider this test case:
module top();
  always @* begin : named_block
    reg[0:0] foo;
    foo = 1;
  end
endmodule

Running this through surelog -> UHDM then reading it in Yosys results in:
1. Executing UHDM frontend.
Generating RTLIL representation for module `\top'.
width_unknown.v:4: ERROR: Failed to detect width for identifier \named_block.foo!

So it looks like, Yosys attempts to look up this name foo with the named_block namespace prefix and doesn't find it.
This works if the block is not named (so, : named_block removed).
This is how the UHDM dump looks like
design: (work@top)
|vpiName:work@top
|uhdmallModules:
\_module: work@top (work@top) width_unknown.v:1:1: , endln:6:10, parent:work@top
  |vpiFullName:work@top
  |vpiDefName:work@top
  |vpiProcess:
  \_always: , line:2:3, endln:5:6, parent:work@top
    |vpiStmt:
    \_event_control: , line:2:10, endln:2:12
      |vpiStmt:
      \_named_begin: (work@top.named_block), line:2:13, endln:5:6
        |vpiName:named_block
<EMAIL_ADDRESS>        |vpiVariables:
        \_logic_var: (work@top.named_block.foo), line:3:14, endln:3:17<EMAIL_ADDRESS>          |vpiName:foo
<EMAIL_ADDRESS>          |vpiRange:
          \_range: , line:3:9, endln:3:12<EMAIL_ADDRESS>            |vpiLeftRange:
            \_constant: , line:3:9, endln:3:10
              |vpiDecompile:0
              |vpiSize:64
              |UINT:0
              |vpiConstType:9
            |vpiRightRange:
            \_constant: , line:3:11, endln:3:12
              |vpiDecompile:0
              |vpiSize:64
              |UINT:0
              |vpiConstType:9
        |vpiVariables:
        \_logic_var: (work@top.named_block.foo), line:3:14, endln:3:17<EMAIL_ADDRESS>        |vpiStmt:
        \_assignment: , line:4:5, endln:4:12<EMAIL_ADDRESS>          |vpiOpType:82
          |vpiBlocking:1
          |vpiRhs:
          \_constant: , line:4:11, endln:4:12
            |vpiDecompile:1
            |vpiSize:64
            |UINT:1
            |vpiConstType:9
          |vpiLhs:
          \_ref_obj: (work@top.named_block.foo), line:4:5, endln:4:8<EMAIL_ADDRESS>            |vpiName:foo
<EMAIL_ADDRESS>            |vpiActual:
            \_logic_var: (work@top.named_block.foo), line:3:14, endln:3:17<EMAIL_ADDRESS>    |vpiAlwaysType:1
|uhdmtopModules:
\_module: work@top (work@top) width_unknown.v:1:1: , endln:6:10
  |vpiName:work@top
  |vpiDefName:work@top
  |vpiTop:1
  |vpiTopModule:1

Unclear if this needed to be reflected with fully qualified name in UHDM (in which case CC: @alaindargelas ) or if this needs to be translated differently in the plugin. Put here to triage properly.

A recent change I did duplicated this var:  _logic_var<EMAIL_ADDRESS>as you can see there are 2 entries. I fixed that with #2926.
That could be the problem. The UHDM dump looks ok besides that.

This looks like to be working now, thanks!


Add sc-dial component and sc-dial-base component.

Overview
Provide an explanation of what the change is
Tests
[Include a link to the passing GitHub action running the test suite here.]
Legal
This project is available under the Apache 2.0 License.

E2E tests are failing, and theres no overview provided in the pull request.

theres still no overview description of what this PR is

@diehbria The tests look like they're failing because of the lock file change. Does it need to be overridden?

there's still no overview provided for this PR. I will not approve until there is an overview for the PR

@tracfren definitely not. The package lock must reflect the package.json changes and it's correct for it to fail otherwise

get the tests to pass

I guess the reason the test fails is that the dependencies added by package.json are not locked in Yarn. lock, so the automatically generated part of Yarn. lock is committed.


fix 3D image interpolation breaking remove-and-add layer

Description
Fixes #3667 by calling _on_display_changed on init to make sure layer and vispylayer are in sync. As far as I can tell, that reset() call is not needed. Also added a dtype parameter so calling _on_display_changed with empty data does not trigger the following warning:
UserWarning: GPUs can't support floating point data with more than 32-bits, precision will be lost due to downcasting to 32-bit float.

Type of change

[x] Bug-fix (non-breaking change which fixes an issue)

References
fixes #3667
How has this been tested?

[x] all tests pass with my change

Final checklist:

[x] My PR is the minimum possible work for the desired functionality

does it make more or less sense to include the call to _on_display_change() in the reset() method which is called in the init anyway? https://github.com/napari/napari/blob/0ec8643aa52609b8e6e5571d1daa550806aae071/napari/_vispy/layers/image.py#L185-L195
Test fails look related too, maybe removing reset() from on_display_change() was a bit heavy handed?
https://github.com/napari/napari/runs/4290114377?check_suite_focus=true
Should probably add a test for #3667 - does this only show up when removing and adding interactively?

does it make more or less sense to include the call to _on_display_change() in the reset() method which is called in the init anyway?

Added a comment to explain why this doesn't work.

maybe removing reset() from on_display_change() was a bit heavy handed?

Hehe, indeed it was, got carried away :)

Should probably add a test for #3667 - does this only show up when removing and adding interactively?

Yes, a test seems good. What do you mean with interactively?

Yes, a test seems good. What do you mean with interactively?
I assumed you wrote the example in ipython because running as a script didn't cause the bug in #3667

test looks good so my assumption must have been wrong! Assuming tests pass I think this is good to go


Matlab unit tests

Adds the first set of Matlab unit Tests,  fixes the getVector Failure in Matlab, and updates some documentation related to Matlab, Issue #189.
I think the rest of the tests and adding them to Ctest will come in a later revision.  But for now this tests the ValueFederate interface and makes a few fixes.
Also included are some fixes to the python tests that I came across while using them as a template.

Nice job catching these!

@kdheepak I am going to run a couple more checks at my office, when I get there, to make sure the vector fix in Matlab runs on multiple systems.  Then I will merge.


Concurrent data generation and training

I understand that t2t-trainer has a generate data option. But as far as I know, it generates data then proceeds to training. Is there a way to concurrently generate data in batches and train on them concurrently to save time for large datasets?

You can use t2t-datagen for generating the training data. I think recently it got support for multi-thread processing (but I am not sure, maybe you need to switch it on with some option - I'm busy now to check). You can even parallelize datagen manually (e.g. on different machines) and then just concat the TFRecords files (they have no header), or just rename the files. What is tricky is your idea of starting training before all the data is ready. You can resume training (i.e. stop and start again from the last checkpoint but with a new dataset), but does not seem user-friendly to me. I usually run t2t-datagen on CPU-only machines and t2t-trainer on GPU machines.


paros: init at 3.2.13

Description of changes

HTTP/HTTPS proxy for assessing web application vulnerabilities
https://sourceforge.net/projects/paros/
Related to #81418
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Fixed merge conflict with master

I just noticed that this created a paros directory in my home after I launched it, quite annoying.


Process Step

I think your process step in the metadata should give an overview of what is happening in your model code. You can describe this in multiple steps. I will need to figure out how to include multiple steps using our pipeline/template, but here's an idea of the type of content you want to include, taken from this model archive.

Download and process NWIS streamflow data. A set of scripts (https://code.usgs.gov/map/maprandomforest) were used to download daily streamflow data from the National Water Information System (NWIS), clean up the dataset, calculate baseflow separation by means of the PART algorithm, and aggregate the data by month and year.

Watershed characteristics associated with the stream flow points of interest were calculated. Processing starts with a shapefile that captures the upstream drainage area associated with each stream flow point of interest. For training the random forest model, this was a shapefile of the basins associated with each stream gage. A shapefile of ungaged basins was used to generate watershed characteristics for points of interest for which no stream flow gaging exists.
Zonal statistics were calculated for each basin, and included:

predominant surficial geology classification
elevation statistics (min, max, mean, std. deviation)
weather statistics: tmin, tmax, precipitation, and several lagged derivatives
estimated Hargreaves-Samani reference ET0, calculated from the weather data

Data assembly. Processed NWIS data (step 1) were joined to processed watershed characteristics (step 2) to produce a file that could be used to train the random forest model (testFlowDat.csv). The files 'testGagesDat.csv' and 'testUngagedDat.csv' were processed similarly, but contain no baseflow or total flow data items; these represent inputs that can be used by the random forest model to produce flow estimates at gaged sites that were missing records, or at ungaged sites.

Random forest training. The random forest model was trained on the inputs contained in 'testFlowDat.csv'. Model testing revealed that neither the elevation nor the surficial geological classifications data appreciably improved the model outputs; subsequently, although the inputs contain columns of data containing the Reed and Bush surficial geology and the elevation statistics, they were not used in the final random forest model.
The random forest training process produced two random forest 'objects': one was trained on total surface flow (original_trained_rf_model_object__total_flow.RData), the other on stream baseflows (original_trained_rf_model_object__baseflow.RData). These random forest objects may be fed new input data in order to calculate baseflow and total stream flow at other ungaged sites.

Apply random forest model. The files 'testGagedDat.csv' and 'testUngagedDat.csv' were used as input to the random forest model to fill in missing slices of data for gaged and ungaged (respectively) basins. The output of this step was captured in the file 'XXXXX'. A second set of estimates was generated for a second set of points (XXXX.csv).

Updated the process description to be more detailed akin to example.


Create contributors page

One thing we absolutely want to do is highlight the amazing people contributing their time to helping here. This issue will be to create a contributors page that allows that. When it comes to adding data to the table, just add a few entries of dummy-text and we'll update it once the PR is approved.
There will be a few steps needed to complete this task - there's a design comp at the bottom of this for reference:

[x] Remove first 'Find a Job' nav item completely, rename 'Quick Filter' to 'Find a Job'
[x] Add a 'Contributors' nav item between 'Get in Contact' and 'Post a Job'
[x] Add route for /contributors to App.js and routes.js
[x] Create Contributors.js file in /pages directory
[x] Add dummy-content/styling to Contributors.js

Bonus: - [ ] Add cypress test for new contributors page. (reference other page tests in ~/cypress/integration/pages - you're basically just testing to ensure that the page is rendering)

Don't hesitate to shoot me an email if you have any questions regarding the issue<EMAIL_ADDRESS>

Hi there! I would like to work on this. Is there a specific timeline you need to see this done?

No timeline!

Ok sounds good! I’ll be sending you an email tonight with some questions then 😀

Looking forward to it

Reviewing this now @ottogutierrez!

All the requirements are fulfilled. Thanks @ottogutierrez!


Getting exception on creating cart rules.

Framework Version: 0.1.6

Fixed.

Framework Version: 0.1.6

Fixed


Routr incorrectly setting transport to caller's, causing message delivery issue

Describe the bug
We are encountering an issue in Routr where it incorrectly sets the transport protocol to match that of the caller's when a Peer uses a different transport protocol. This action disrupts the proper arrival of messages.
To Reproduce
Create a deployment with a Peer (for example Asterisk) and set the Peer to TCP. Then create an Agent and attempt to send an invite while using a different transport.
Expected behavior
Routr should maintain the distinct transport protocols of the Peer and the caller separately, allowing for proper message delivery regardless of transport protocol disparity.
Screenshots

System information (please complete the following):
NA.
Additional context
None.

Additional context:

sip messages

Decided to create a new alterations function to calculate the Via header from the Route. https://github.com/fonoster/routr/releases/tag/2.1.5


Playbook-ARM-Template-Generator - setting unique file name

When using ARM template generator to export multiple playbooks they land in the folders with the correct playbook name but the JSON files name is the same for all exports i.e azuredeploy.json
This then causes issues when we try to upload our ARM templates to Gibhub for syncing back to Sentinel. Would it be possible to also set the json file name to match the playbook name?
Thanks

We wanted to check on the status of Issue https://github.com/Azure/Azure-Sentinel/issues/5603 . The issue is pending for more than expected days. Please let us know if you need any assistance to review this Issue. As per our standard operating procedures if no response is received in the next 7 business days, we will close this Issue. Thank you for your cooperation.

Since we have not received a response in the last 5 days, we are closing your issue https://github.com/Azure/Azure-Sentinel/issues/5603 as per our standard operating procedures. If you still need support for this issue, feel free to re-open at any time. Thank you for your co-operation.


Protocols.cs license question

Hi,
The file Submission/Protocols.cs still contains the LGPL license header.  Is this a mistake or oversight?
If not, how does it impact with the rest of the files being MIT Licensed?
Thanks

It's a leftover from the early releases which was under LGPL. Fixed it now. Thanks for the notice.
https://github.com/soygul/NBug/commit/b1aa9122404efa55f7304b867a601494c42d8a30


Feature/generate source modelname

implemented settings for file name of the generated file
implemented source path as destination path for the generated file

Resolves #388
Overview

Checklist

[x] I have run this code and it appears to resolve the stated issue
[x] README.md updated and added information about my change

Great work!

Hi @mdesmet,
When will this update be released?
KR,
Bas


findAndModify override the entire row

Im trying just to update a row, but when I "update" it get replaced by the new object and not just update the fields that i want
campaing.findAndModify({
          query: {
            id : req.params['id']
          },
          update: {
            subject:      req.param('subject'),
            from:         req.param('from'),
            reply_to:     req.param('from'),
            body:         req.param('body')
          },
          new: true
        }, function(err, data){
          //
        })

The document has more than this 4 cols, but when I update only those 4 remain, the other seems to be deleted!

I think you need to use $set notation to do a partial update. Check out the documentation here:
http://www.mongodb.org/display/DOCS/Updating
http://www.mongodb.org/display/DOCS/findAndModify+Command


[BUG] Reduced Area not unset correctly

Manufacturer: Thermo Fisher
When imaging with Image_settings.reduced_area = None, this does not set the imaging to full area imaging. This means that if reduced area has been selected in the UI, this setting will not be applied correctly.
Should explicitly set the condition as the system will use whatever is chosen in the UI if not explicitly set.

@LucileNaegele was this closed?

@patrickcleeve2  we haven't tested it yet but the code is there


Arbitrum Nova subgraph issues

Describe the bug
The Arbitrum Nova subgraph appears to be unreachable or missing. This (I believe) causes a "Not enough bridge liquidity to complete transfer. Use a smaller amount." error to appear when trying to transfer TO Arbitrum Nova.
To Reproduce
Steps to reproduce the behavior:

Go to https://bridge.connext.network/
Select destination chain Arbitrum Nova
Select origin chain BNB/Arbitrum/Optimism/Polygon (all of these are supported by the router with USDC liquidity)
Choose an amount like 100 USDC
See error (the estimated received will appear because a bid was received, but the site will still show not enough liquidity)

Expected behavior
The Arbitrum Nova subgraph should work correctly.
Additional context
It seems that after some time the subgraph loaded, and now the error doesn't show up and the subgraph data appears correctly in the status page of the explorer. This may be a temporary/intermittent issue.
Screenshots

This is temporary/intermittent, unfortunately won't fix this.


perf(vaults.snapshots): Optimize vault snapshots for harvests

Background
List methods for vaults harvests need snapshot at exact block on chain, to calculate estimated APR. Now we are using sdk method that fetches data from the graph, obviously it slows down the list method coz of IO in quadratic complexity.
Solution, index task which will save vault state at needed blocks.
Tasks

[x] Create, or extend existing ddb table for vault snapshots for harvests on all chains and their vaults
[x] Push it to indexing task in aws lamda

We've rethink a bit implemintation


Discussions?

Could you open discussions so we can ask questions without opening issues? Unless you would rather qestions be issues?

His shoes are totally fine! If there is a significant amount of discussion-related issues, then we can reevaluate, but for the most part it seems like issues are still the default for most people's workflows


Support of transformation parameters for the interaction box

Description
Until now, the interaction box did not adopt the layer transformation parameters like scaling, translation, ... ( see the attached videos).
https://user-images.githubusercontent.com/83079938/159717943-7a1c78cc-a3d8-4f10-9493-f625bb460c90.mp4
For use cases where these parameters are different from the standard values (e.g. defined in a layers metadata when read from file), the interaction box does not fit the actual layer.
Therefore we solved this, see the attached videos.
https://user-images.githubusercontent.com/83079938/159717956-eedc2604-fc31-4025-954a-2fb32315c9b9.mp4

Type of change

[x] Bug-fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

References

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

Good morning @alisterburt,
I have added a test function as you have suggested:) I tested this locally and this works. Hopefully, it works now.
Thank you very much for your help, input and review:) It is up-to-date, it should work:)

Okay thanks @alisterburt,
I do not understand why the PR Test for ubuntu, windows and macos fail?
This is strange. I observed this on some other pull request, too. Do you have any idea, where it comes from?

@MBPhys I asked @tlambert03 and he suggested maybe the way you were using settings could be the culprit - I've opened a PR at MBPhys/napari#1 so that we can test that.
A more general note (also brought up by @tlambert03) is that we want to avoid dynamically adding internal keybindings where possible, instead we would want to add them to the global viewer keybindings file and have them only active in a certain context - this is beyond the scope of this PR as we don't have a context object for the viewer yet, just noting here :)

Hi @alisterburt,
this could be the case. He is the expert. Thanks for asking:) And thanks for the answering @tlambert03
Let test that:)
Yes I understand this. I was also confused as I have seen this. For me the  global viewer keybinding files would be also better, but I did not want to change so much. The structure was already there.
I can make a new commit to put this out of the interaction box file into the global viewer file. Then it is more straightforward and not so confused. What do you think?

@MBPhys I would say let's keep this PR simple and confined to supporting transforms for the interaction box, that refactor can come later :)
Looking at other active PRs it does seem like the test errors are isolated to this PR. Let's try to simplify things a little bit and make this PR the absolute minimum required for the functionality by

removing any reference to settings
leave the keybinding as it was

If this solves the issues then we can at least move forward here and address those issues separately, how does that sound?

waiting on CI now!

@alisterburt
This sounds good. Yes, the goal of this PR was to support transform and not to merge keybindings.
This issue should be addressed separately, but it is a important point:)
So let try:) Keybindings can be confused...

I'm excited:)

https://github.com/napari/napari/runs/5692754514?check_suite_focus=true#step:9:211 my bad - this test is failing in 'headless' mode (where we run without a qt backend)
This came up recently in #4245 and the solution is that

tests of napari components should not depend on qt
we need the viewer for this test, so let's move move the test to napari._tests/test_interaction_box_with_qt.py 🙂

nearly there!

we need the viewer for this test,

if ViewerModel is sufficient: that is, if this doesn't require any of the logic in the _qt folder (and it appears not to) then use that instead of make_napari_viewer:
from napari.viewer import ViewerModel

def test_something():
    viewer = ViewerModel()

Okay:) Next try:)  @alisterburt
Thanks @tlambert03 for your help.
I learn more and more about your test architecture:) This is very fancy:)

@alisterburt
Sorry this was my fault. I was to fast... with the test function

@alisterburt
Hopefully, this should be the last commit on this small bug/ feature added:)

Thanks, @alisterburt :) I have followed this:) Yeah this can happen, unfortunately. meshzoo #4325 could also be the problem, or?
To figure this out, it is hard job. My respect for this great job and the testing procedure.
Hopefully, I can help more in the future concerning testing, Now that I'm more familiar with the napari test architecture:)
Is there any missing for this PR? Should I make a new push, because min_req still fails for the old one?

@MBPhys I think you've done everything that's needed here, thank you! The remaining issues are separate to this PR so should be resolved separately
Looking forward to seeing you around the repo more! 🙂

All checks passing! Great work here @MBPhys - this is your first on the main repo right? Congratulations on this first napari PR, excited to see what you'll do next 🚀 🎉

Thanks, @alisterburt :)
Yes, this is correct. There will be some other PR in the future concerning keybindings and adding a ruler #4200, but this needs more discussion to ensure that this will be not against some other PR and ideas. Maybe it will be useful to make stuff together so that people do not work past each other. I'm looking forward to see how napari evolves, how I can help :smile:, discuss stuff.
I'm very interested to see what your ideas are for labeling stuff. Perhaps I can help and we can discuss something if you want?
Thank you very much for your support and reviews @alisterburt, @brisvag,
in particular to solve the bug with min_req test:) Great job.


[docs] Use Stack in demos

[x] I have followed (at least) the PR section of the contributing guide.

Using new Stack component in demos 🎉
Docs: https://deploy-preview-25419--material-ui.netlify.app/components/stack/

@oliviertassinari What issue should this be linked to?

@oliviertassinari I understand, let's do it here.
I was watching the demo of the Paper and I think that it could not be used there because of the comment of the margin and left margin. Try to do it but in mobile you lose the bottom and top margin. Try to solve it by making mobile be direction='column' but I'm not sure if that's the way to go.

Yeah, it can't be used everywhere. I think that we should be conservative, best not to break exisiting demos when in doubt. Wrapping isn't supported 😁

@oliviertassinari I have finished switching the demos to the Stack component. It was only done in those who had the TODO comment. I have two doubts.

The BrandingPersona component I modified it but I couldn't see where it is used to check.
What do we do with the demo Paper component? Do we remove the comment TODO?

@oliviertassinari In the Stack component API alignItems and justifyContent are not declared. Is this for something special?

@vicasas What do you mean by not declared?

I mean no such props appear in the api spec. (alignItems and justifyContent)

@vicasas It's expected, it comes from the system. We don't use them in the docs.

@oliviertassinari understand! thanks for the clarification 😁


Forcing a pause at the end of HTTP headers

I've implemented a simple C++ wrapper for the http-parser library and ran into a problem when using the parser pause feature.
Basically, I have a Request object that wraps a http_parser instance.  This request object has a feed() method which invokes http_parser_execute().  The request object also has a headers_complete() which reports the end of HTTP headers.  To make this test reliable (mainly for proxying purposes), I force http_parser_execute() to return by pausing the parser calling http_parser_pause() from the on_headers_complete() callback.  All this seemingly works, except that it doesn't consume the last byte of a request without a body.  To finish processing the request, I have to call http_parser_execute() again with the last byte of data.
Now, calling feed()/http_parser_execute() one extra time is not that much of a problem, except that it makes it prevents clients from accurately finding the exact position of the end of HTTP headers.  In a proxying scenario (HTTP proxy, CGI/SCGI/FastCGI or even WebSockets), where you want to forward the body byte-for-byte, clients end up prefixing the HTTP request body with an extra byte.
This was reported to me on the httpxx issue tracker, but I believe it's an issue in http-parser.  Basically, the on_headers_complete() callback is called upon examining the last byte of the header data, and pausing in that callback prevents the library from marking the last byte (the one the triggered the callback) as consumed.
Visit the httpx issue #5 for a detailed discussion.  If it's unclear, I might be able to concoct an SSCCE that illustrates the problem.
Note: this issue seems related to pull request 89.

Confirmed.
It's annoying: while it's obviously a bug, fixing it breaks a number of assumptions that http-parser users may have made about the order of events or when it's safe to call the parser (evidenced by the number of tests the fix breaks).
Rock, meet hard place.

I've hacked a workaround in AndreLouisCaron/httpxx@608af01eee7cfdad579381f61edf70778eedaa58, but it's really ugly. I have to manually fix off-by-one errors because of this bug, and the count is unreliable until the on_message_complete() callback is called so that I can fix it.
If someone has a clear idea on how to fix this issue without breaking everything, I might be able to put in some time to fix it.

Yeah, this is tricky to fix because a single byte can trigger multiple callbacks, and if a callback other than the last results in the parser being paused, we need a way to track that these addition callbacks need to be executed. We're doing this now by not consuming the byte until we're done with all of the callbacks that it should trigger. For callbacks where we do not re-execute the same byte, this isn't an issue, of course.
We could fix this to return that all bytes were consumed (e.g. by stashing the last byte in http_parser and using it when continuing execution), but we'd be breaking the assumption of users of the http_parser_execute() API that if all bytes are consumed, there is no reason to call http_parser_execute() again until there is more data to parse (or an EOF has been received). We'd also need a way to poke the parser to consume this stashed byte -- calling http_parser_execute(NULL, 0) isn't going to cut it, as that would look eerily like an EOF to the un-trained eye. Some options here include adding a new http_parser_execute_buffered() API, or having http_parser_pause(0) kick off execution.
Mercifully, these changes in execution behavior might okay-ish because these assumptions about return value/byte consumption only break if you're using http_parser_pause(), and AFAIK there are a limited number of users of this function (possibly only us and AndreLouisCaron/httpxx).
Any other ideas @bnoordhuis, @ry or @clifffrey?

I'll go out on a limb here, but it seems to me that we're approaching the problem from the wrong angle.  Rather than trying to fix the thorny issue of marking the last byte, wouldn't it be easier to play on the pausing semantics?  I don't really care if more callbacks are invoked after I pause the parser (e.g. on_message_complete() for an empty message), so long as it pauses "soon".
Pausing is currently implemented by using a special error code, which happens to be temporary (the client can reset it by calling http_parser_pause(&parser, 0);).  The real issue here it that the parser does not distinguish between HPE_PAUSED and real error codes.  A more flexible approach to pausing would prevent the parser from continuing after a change of state (e.g. from "parsing headers" to "parsing body").
Any ideas on this?

Is node (or any other library) relying on http-parser not executing on_message_complete after pausing from inside on_headers_complete?
If not, I think the easiest 'fix' would be to implement pause as "don't consume any more bytes (but call whatever callbacks are necessary)" instead of "stop doing anything". That was what I thought it did when I read the prototype of http_parser_pause anyway.

I don't really care if more callbacks are invoked after I pause the parser (e.g. on_message_complete() for an empty message), so long as it pauses "soon".
I think having a immediate, non-advisory pause is pretty useful, particularly as evidenced by the Node community's continued struggles to deal with its absence: the fact that ##ServerRequest.pause()## doesn't actually pause bites people frequently, and is a work-around that looks likely to land in the latest release (by buffering in the application) is both highly desired and looked at with skepticism because of what it has to do to work around the fact that ##http_parser## couldn't natively pause (they don't know about ##http_parser_pause()## yet, it seems).
That said, there's certainly a trade-off between implementation complexity and value, but I don't think we've crossed that threshold.
The real issue here it that the parser does not distinguish between HPE_PAUSED and real error codes.
Is your expectation that calling ##http_parser_execute()## should implicitly un-pause the parser? If so, I'm not sure I follow how that's related to reporting the correct number of bytes consumed.

Is node (or any other library) relying on http-parser not executing on_message_complete after pausing from inside on_headers_complete?
Not that I know of. AFAIK there are very few users of http_parser_pause().
If not, I think the easiest 'fix' would be to implement pause as "don't consume any more bytes (but call whatever callbacks are necessary)" instead of "stop doing anything".
Yeah, that's certainly an option.
I do think it's worth spending some amount of effort to get the API to work with the more rigid semantics, though, as this provides a more powerful API. I'll spend some on that this weekend and see how far I get.

Couldn't we store the pause state somewhere explicitly?  It would be more
work to code up, but if we had different parser states for these things,
even though they were at the same byte offset, then the parser could know
which callbacks have been run already.
I think that pause needs to be absolute, it would be very surprising to a
new user of the API to see a callback called after the stream was paused.
On Mon, Feb 27, 2012 at 11:50 AM, Peter Griess <
<EMAIL_ADDRESS>
wrote:

Is node (or any other library) relying on http-parser not executing
on_message_complete after pausing from inside on_headers_complete?
Not that I know of. AFAIK there are very few users of
http_parser_pause().
If not, I think the easiest 'fix' would be to implement pause as "don't
consume any more bytes (but call whatever callbacks are necessary)" instead
of "stop doing anything".
Yeah, that's certainly an option.
I do think it's worth spending some amount of effort to get the API to
work with the more rigid semantics, though, as this provides a more
powerful API. I'll spend some on that this weekend and see how far I get.

Reply to this email directly or view it on GitHub:
https://github.com/joyent/http-parser/issues/97#issuecomment-4201469

If not, I think the easiest 'fix' would be to implement pause as "don't consume any more bytes (but call whatever callbacks are necessary)" instead of "stop doing anything".

Yeah, that's certainly an option.

Sorry if I wasn't clear when I said I wanted the parser to stop "soon".   This is what I had in mind.

I think the easiest 'fix' would be to implement pause as "don't consume any more bytes (but call whatever callbacks are necessary)" instead of "stop doing anything".

I've worked around the issue to implement exactly this in AndreLouisCaron/httpxx@fbd0422dfeaaa53d62956a3dee302d3f704714a4.  It only works for processing the last byte after the headers, but it fixes the only instance of this problem I've encountered so far.
I would still prefer this was fixed in http-parser for all (potential) cases, but if there is a serious design problem in implementing a real fix, I can live with this bug as long as the exact behavior of http_parser_pause() is documented so that no one gets "bitten" by this problem.

I would still prefer this was fixed in http-parser for all (potential) cases, but if there is a serious design problem in implementing a real fix, I can live with this bug

I think everyone agrees that it should be fixed on our side, the question is how?

I looked at bnoordhuis's new test case and it prevents pausing in on_headers_complete from invoking on_message_complete.  I don' t think this can ever be satisfied if we fix this issue since empty requests absolutely need to call both callbacks before marking the last byte as consumed.
I pushed a sample fix that just addresses the specific case of letting on_message_complete be called when the parser is paused from on_headers_complete.  It breaks current tests for pausing, which validate that absolutely no more callbacks should be called after a pause.  All other tests still pass, but don't use this since I think this is somewhat of a hack, and I'm not sure what the behavior is for pausing in other callbacks (e.g. on_url()).

I think everyone agrees that it should be fixed on our side, the question is how?

First, we need to define the semantics of pausing.  Should pausing be allowed all callbacks, or should it be limited to specific cases?  AFAICT, the only interesting places to call this are in on_headers_complete for proxying purposes and in on_message_complete for HTTP/1.1 pipelined requests.
Also, in what (other) cases is this a problem?  So far, the only problematic instance is for on_headers_complete(), which must potentially call on_message_complete when the request has no body.

I feel like I'm missing something.. why is it that "... empty requests
absolutely need to call both callbacks before marking the last byte as
consumed"?  Couldn't they consume the last byte, but leave the parser in a
state of s_paused_before_message_complete, and have that state just call
the callback and then do "goto reexecute_byte;"?  I'm probably missing
something though, so please forgive me if this idea can't work.
On Tue, Feb 28, 2012 at 9:21 PM, Andr Caron <
<EMAIL_ADDRESS>
wrote:

I looked at bnoordhuis's new test case and
it prevents pausing in on_headers_complete from invoking
on_message_complete.  I don' t think this can ever be satisfied if we fix
this issue since empty requests absolutely need to call both callbacks
before marking the last byte as consumed.
I pushed a sample fix that just addresses the specific case of letting
on_message_complete be called when the parser is paused from
on_headers_complete.  It breaks current tests for pausing, which validate
that absolutely no more callbacks should be called after a pause.  All
other tests still pass, but don't use this since I think this is somewhat
of a hack, and I'm not sure what the behavior is for pausing in other
callbacks (e.g. on_url()).

I think everyone agrees that it should be fixed on our side, the
question is how?

First, we need to define the semantics of pausing.  Should pausing be
allowed all callbacks, or should it be limited to specific cases?  AFAICT,
the only interesting places to call this are in on_headers_complete for
proxying purposes and in on_message_complete for HTTP/1.1 pipelined
requests.
Also, in what (other) cases is this a problem?  So far, the only
problematic instance is for on_headers_complete(), which must potentially
call on_message_complete when the request has no body.

Reply to this email directly or view it on GitHub:
https://github.com/joyent/http-parser/issues/97#issuecomment-4231984

After further reading of the code, it seems to me that the only risky bits are parser states that use goto reexecute_byte; and execute callbacks.  I only found only two states that do this:

s_body_identity; and
s_headers_almost_done.

FWIW, the latter is our problematic case and the former already has somewhat of a hack:
/* Mimic CALLBACK_DATA_NOADVANCE() but with one extra byte.
 *
 * The alternative to doing this is to wait for the next byte to
 * trigger the data callback, just as in every other case. The
 * problem with this is that this makes it difficult for the test
 * harness to distinguish between complete-on-EOF and
 * complete-on-length. It's not clear that this distinction is
 * important for applications, but let's keep it for now.
 */
 CALLBACK_DATA_(body, p - body_mark + 1, p - data);
 goto reexecute_byte;

Couldn't they consume the last byte, but leave the parser in a state of s_paused_before_message_complete, and have that state just call the callback and then do "goto reexecute_byte;"?

Hadn't thought of that!  I'll give this a try tomorrow.

Yeah, @AndreLouisCaron is right that the particular devil here is the extra byte that you need to stash: where to stash it, and how to kick off parsing with it. I don't think we need to add any more parser states to accomplish this, as there is already a state for every place where we might have paused (i.e. after every callback). We just need to tweak these states to look at the stashed byte.
I'm starting to think that renaming http_parser_pause() to http_parser_unpause_and_execute() (or something) is the right way to go. I can't think of a meaningful situation where one would un-pause the parser without wanting to then immediately process any data that remained. The major benefit of this API name change would be that it's obvious that the parser going to start executing without being given any additional data.

@indutny @bnoordhuis ... any reason to keep this open?

I'm about to open a new issue. I'd like my C++ wrapper to operate the parser in two stages, first to process the message header as a complete unit, and then to process the body. Returning 1 from on_headers_complete is not the answer because you can't resume parsing of the body. So I'm looking through the outstanding issues to see if anyone else seeks similar functionality and I came across this issue.
I'm going to try using the pause feature to implement two stage parsing. Was the bug described fixed? Am I going to encounter a problem with "that last byte?" Is there another way to implement the functionality I desire?


Upgraded dependencies

This PR upgrades dependencies and devDependencies

That's fine. :)
Thanks for rolling out the upgrade.
On Mon, 17 Sep 2018, 17:55 Stephen Flynn<EMAIL_ADDRESS>wrote:

Hi Darshan,
didn't accept the PR only because I was half way through the same process
and I needed to fix up the tests that got broken as a result.
Just published 0.2.2 as a release - should contain all the upgrades
included in your PR.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/JFTechnology/ember-keycloak-auth/pull/14#issuecomment-421993634,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARtjt-NhPq7Nn72LtO6gzJsQfpvs-AgOks5ub5SngaJpZM4Wioha
.


chore: add debugging for failing test case, see COUCHDB-3415

Overview
Add test case to see what trips up this test case in COUCHDB 3415.
This could be as simple as a newline character, but I want to make sure.

Testing recommendations

This needs to run in CI for a bit until it pops up again.
JIRA issue number

https://issues.apache.org/jira/browse/COUCHDB-3415
Checklist

[x] Code is written and works correctly;
[x] Changes are covered by tests;
[x] Documentation reflects the changes;
[x] I will not forget to update rebar.config.script
with the correct commit hash once this PR get merged.

+1
Though as mentioned in other PR ?debugFmt I think the preferred way to print during EUnit tests. Minor nit though. As this is temporary until we figure out all the flakiness issues, feel free to ignore.

@nickva good catch, I had tried that, but couldn’t get the caught error message to pass through debugFmt, so I went with the regular method.

Ah alright then. If user works then let go with that


[Bug] Vanilla hopper works incorrectly

OmniHopper makes vanilla hopper (and some mod hoppers) not work incorrectly.
All info: video_log_mixin_export.zip

I just found this problem myself.
https://www.youtube.com/watch?v=izb90f26sJc


Fix/circular progress ie

Please check if the PR fulfills these requirements

[x] The commit(s) message(s) follows our guidelines
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

What is the current behavior? (You can also link to an open issue here)
The circular progress animation does not work on IE11 since IE11 does not support animation with strokeDasharray and strokeDashoffset
see #91
What is the new behavior?
Workaround: I added default values for strokeDasharray and strokeDashoffset so that we have a kind of animation on IE11 and keep old behavior on others browser.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

false positive


Add timing information for acquiring an existing connection

Currently, client-side provides some timing information when a new connection is created.
https://armeria.dev/docs/advanced-structured-logging#client-connection-timing-properties
This information is exposed with the naming connectionAcquisitionDurationNanos.
However, these metrics are recorded only for cases where a new connection is created.
It has been pointed out that the naming is confusing since this metric isn't recorded when an existing connection is used.
We may do one of the following:

Add a new timing to ClientConnectionTimings

Add a connection timing info

e.g. existingConnectionAcquisitionDurationNanos

Measure the time to query from the connection pool (https://github.com/line/armeria/blob/b78d9515dc8b4b997dd65787f717443b38a21869/core/src/main/java/com/linecorp/armeria/client/HttpClientDelegate.java#L170-L174))
Note that whether the acquisition is successful or not, the duration will be recorded.

Reuse pendingAcquisitionDurationNanos

We don't have to worry about naming, but the logic to whether start/end the metric may be complex.

Don't define a separate timing and just end the timings

This may be achieved by simply passing the built timings

https://github.com/line/armeria/blob/b78d9515dc8b4b997dd65787f717443b38a21869/core/src/main/java/com/linecorp/armeria/client/HttpClientDelegate.java#L176

I propose we go with option 1 might be simpest/least prone to error.
I think we also want to expose this metric to RequestMetricSupport by default.
Note: As pointed out by @ikhoon, doing this would also fix a bug where dns timing information wasn't collected if there is a healthy connection already available.
ref: https://line-armeria.slack.com/archives/C1NGPBUH2/p1684469502484689

Thanks @jrhee17 for creating this issue!
I agree that option 1 is the most reasonable option. Here are some of my suggestions on option (and please FFTI):

existingConnectionAcquisitionDurationNanos is a good name. I'd also suggest renaming connectionAcquisitionDurationNanos to newConnectionAcquisitionDurationNanos. This way, the name is the most clear.
I understand that this^ renaming could be a breaking API change as ClientConnectionTimings is probably considered as a public API. So, maybe consider this renaming as part of the next major release. But before that happens, it'd be very nice to update all Javadocs/comments about connectionAcquisitionDurationNanos to clearly point out that this duration is only about acquiring/creating a NEW connection.

I'd also suggest renaming connectionAcquisitionDurationNanos to newConnectionAcquisitionDurationNanos. This way, the name is the most clear.

Rather, I was thinking that existingConnectionAcquisitionDurationNanos would be included in connectionAcquisitionDurationNanos.

If a readily existing connection exists, existingConnectionAcquisitionDurationNanos  > 0
If a connection is in the progress of creation, pendingAcquisitionDurationNanos > 0
If a connection is created, socketConnectDurationNanos > 0

Essentially, connectionAcquisitionDurationNanos = existingConnectionAcquisitionDurationNanos + pendingAcquisitionDurationNanos + socketConnectDurationNanos so semantically I was thinking the naming is fine as-is.

Note: @ikhoon also suggested that we change the naming of the metric collected in RequestMetricSupport:
https://github.com/line/armeria/blob/f2116739018c15f230dd8f0e5a4dd5db1fefc888/core/src/main/java/com/linecorp/armeria/internal/common/metric/RequestMetricSupport.java#L289-L296
He suggested that we use tags to differentiate connection acquisition
e.g.
connection.acquisition.duration

acquisition_type

new
piggyback (pending might be more appropriate)
reuse

To avoid breaking changes, we may just add another metric at the cost of extra metric exported. (and deprecate the old metric. Deprecation may be propagated via javadocs and documentation to be added)
We should also update documentation since the relationship between values in ConnectionTimings and the metric names may not be clear.

If the default metrics are more accurately expressed/exposed by RequestMetricsSupport, I think it will be possible to reduce the hassle of creating custom metrics by accessing ClientConnectionTimings.
The new metric will provide more accurate information about connection acquisition.