Add doc for awslogs-endpoint log option

forward-port of https://github.com/docker/docker.github.io/pull/7003, which was merged in the vnext-engine branch, but the feature (https://github.com/moby/moby/pull/37374) was already included in the current 19.03 release

ping @usha-mandya ptal


Use JSON schema to validate specs

Would be nice to add some validation to catch typos such as "output" instead of "outputs" :-)

+1


bug: Oil seems to stuck in error state and not usable if we try to switch buffer not saving changes in oil

Did you check the docs and existing issues?

[X] I have read the docs
[X] I have searched the existing issues

Neovim version (nvim -v)
0.9.0
Operating system/version
Macos 12.6.6
Describe the bug
Oil becomes  unusable if after editing Oil window with lets say adding a new file and then without saving it, trying to switch to a different buffer. In this case, I tried opening Telescope old_files picker. My autosave could be the culprit here.

I think the problem here is that, I am using vim auto save plugin(Plug '907th/vim-auto-save') and it auto saves buffers on particular events
and here is my config for the same
vim.g.auto_save = 1 -- enable AutoSave on Vim startup
vim.g.auto_save_events = { "FocusLost", "TabLeave", "WinLeave", "BufLeave" }

Here are the autocommands created by that plugin

Steps To Reproduce
Keystrokes to reproduce:
:Oil
o abc.txt
ctrl [
:Telescope find_files
Expected Behavior
At present there seems to be a lock because user needs to answer the dialog, do you want to create file abc.txt and as that window disappears, the save function is locked as happening and it won't allow for next action. We can probably have some timeout and ignore it or on cancellation of the popup window, we can cancel the save operation
Directory structure
No response
Repro
Not filling this as it would entail, adding plugin manager, plugins etc. Hope the above plugin information and the plugin config suffices

Did you check the bug with a clean config?

[X] I have confirmed that the bug reproduces with nvim -u repro.lua using the repro.lua file above.

I'll add a pcall to guard against failures here, but it's still going to display an error. I would recommend disabling your auto-save plugin on oil buffers. Automatically committing file mutations doesn't sound like a good idea.


Can't to npm install

npm ERR! code ETARGET
npm ERR! notarget No matching version found for gatsby@next
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'gatsby-documentation-starter'
npm ERR! notarget

I had exactly same issue. I changed the "next" version to "latest" a problem was solved... I don't know what "next" mean.

I had exactly same issue. I changed the "next" version to "latest" a problem was solved... I don't know what "next" mean.

"next" is from YARN similar to "latest".

I had exactly same issue. I changed the "next" version to "latest" a problem was solved... I don't know what "next" mean.

"next" in YARN similar at "latest" in NPM

Aha...so the question ii: Why they use YARN syntax in package.json :)

I had exactly same issue. I changed the "next" version to "latest" a problem was solved... I don't know what "next" mean.

"next" in YARN similar at "latest" in NPM

Aha...so the question is: Why they use YARN syntax in package.json :)

iduno lol!! ahhahah.
BUT. See! There is 'package-lock.json' for NPM, but package.json for YARN.
BUT!! There is no 'yarn-lock.json' for yarn ))))
Mystic


Algorithm detecting exposure incorrectly when it was > 4 hours ago

Version

Type of phone: Android
OS Version: 10
Model: Pixel 3a

Steps to reproduce

Install the application build up location history
Analyse your location data (I wrote this script to help) and find a point that has the greatest distance from your actual location (point A, at time T)
Create a HA file that has point of concern just under 20m away from point A on both axes, let's call it point B
Double check the distance using this script - I get output like this:

Point of concern identified... 16.68193716061866m & 19.721204492528148m & 0:00:00

Add a test HA URL that reflects your current location showing point B at time T
Load the URL in the app

Expected Behavior
The app should detect exposure based on the algorithm described here.  I am assuming that the point needs to be within 20m on each axis.
Actual Behaviour
App shows no known exposure.
Please note I am happy to provide all the test files / location data to an individual developer, but not on github!

further testing has used pythagoras and confirmed the algorithm is accurate...


Manage mutation of permissions directly in the proxy

Rather than send ddlx commands through the replication stream and then apply them to the current permissions state when they come out of pg, this pr instead moves mutation of the permissions to the proxy process. so we load the current permissions state within the proxy transaction then mutate them on receipt of any ddlx commands.
if at the end of the tx the perms have changed, then we write them to pg before committing the txn.
the advantage of this is that the proxy is able to retrieve a consistent view of the permissions within migration transactions and so can determine the permissions state for any table when updating triggers. basically an essential building block if we're going to defer adding the consistency triggers at the point of granting write perms.
also includes a re-factor of the way we keep track of published tables to hopefully make that process less error prone, and a bit of a clean up of the internal migration code.

👋 we've been working the last month on a rebuild of the Electric server over at a temporary repo https://github.com/electric-sql/electric-next/
You can read more about why we made the decision at https://next.electric-sql.com/about
We're really excited about all the new possibilities the new server brings and we hope you'll check it out soon and give us your feedback.
We're now moving the temporary repo back here. As part of that migration we're closing all the old issues and PRs. We really appreciate you taking the time to investigate and create this improvement!


adding proxy support

why is proxy part of ssl options? proxy doesn't have to be ssl related
tests?
how can it be clear to the user what/which format should be put in the new proxy field?
readme updates?

@abonas do you think socket_options is a better location? or do you want me to add a new options to pass around?
I think 3 will be clarified when I fix 4, the readme. It is the same format that RestClient expects. (URI for the proxy).

why does it belong to socket_options?

@simon3z please also review. thanks

I moved it to its own place instead of piggybacking the existing options. Added a test as well.

perhaps the proxy should be treated in the input parameters similar to the url itself. iirc it could be passed as both uri or string and then the client takes care of it. but I don't have a strong opinion here.
cc @simon3z

@abonas updated this handling of the proxy uri.

@enoodle what about watches, is there any issue there? (are we depending on any proxy requirement?) Have you tried those? (Especially in regard to timeouts of the connection).

perhaps the proxy should be treated in the input parameters similar to the url itself. iirc it could be passed as both uri or string and then the client takes care of it. but I don't have a strong opinion here.

I prefer to be consistent, so probably yes we should support both.

@simon3z I am not sure what are watches but the proxy access itself is implemented in RestClient that itself is just passing it down to Net::HTTP (https://github.com/rest-client/rest-client/blob/68edb26431d2e7702a4b2cf6f3dca3f486dea08a/lib/restclient/request.rb#L327).
I used tshark to debug my setup (3 machines with TinyProxy in the middle between the client and the OpenShift host) does that count as a watch?

@enoodle watches are in: https://github.com/abonas/kubeclient/blob/master/lib/kubeclient/watch_stream.rb

@abonas  @simon3z Ok, Thank you. I updated to support watches as well.

@enoodle can you check if there's a way to test the proxy with stub_request. Current test is only checking that we're setting the proxy, not that it's actually used (maybe it's enough but if we can ensure that it's actually used for the request it would be better).

@simon3z , currently it doesn't work:
Run options: --seed 698

# Running:

..........................................E..............................

Finished in 0.517860s, 140.9648 runs/s, 519.4456 assertions/s.

  1) Error:
KubeClientTest#test_proxy_enabled:
WebMock::NetConnectNotAllowedError: Real HTTP connections are disabled. Unregistered request: GET http://kubehost:8080/api/v1/pods with headers {'Accept'=>'*/*; q=0.5, application/xml', 'Accept-Encoding'=>'gzip, deflate', 'User-Agent'=>'Ruby'}

You can stub this request with the following snippet:

stub_request(:get, "http://kubehost:8080/api/v1/pods").
  with(:headers => {'Accept'=>'*/*; q=0.5, application/xml', 'Accept-Encoding'=>'gzip, deflate', 'User-Agent'=>'Ruby'}).
  to_return(:status => 200, :body => "", :headers => {})

============================================================
    /home/efreiber/.rvm/gems/ruby-2.2.4@miq/gems/webmock-1.24.6/lib/webmock/http_lib_adapters/net_http.rb:114:in `request'
    /home/efreiber/.rvm/gems/ruby-2.2.4@miq/gems/rest-client-1.8.0/lib/restclient/request.rb:270:in `net_http_do_request'
    /home/efreiber/.rvm/gems/ruby-2.2.4@miq/gems/rest-client-1.8.0/lib/restclient/request.rb:418:in `block in transmit'
    /home/efreiber/.rvm/gems/ruby-2.2.4@miq/gems/webmock-1.24.6/lib/webmock/http_lib_adapters/net_http.rb:123:in `start_without_connect'
    /home/efreiber/.rvm/gems/ruby-2.2.4@miq/gems/webmock-1.24.6/lib/webmock/http_lib_adapters/net_http.rb:150:in `start'
    /home/efreiber/.rvm/gems/ruby-2.2.4@miq/gems/rest-client-1.8.0/lib/restclient/request.rb:413:in `transmit'
    /home/efreiber/.rvm/gems/ruby-2.2.4@miq/gems/rest-client-1.8.0/lib/restclient/request.rb:176:in `execute'
    /home/efreiber/.rvm/gems/ruby-2.2.4@miq/gems/rest-client-1.8.0/lib/restclient/request.rb:41:in `execute'
    /home/efreiber/.rvm/gems/ruby-2.2.4@miq/gems/rest-client-1.8.0/lib/restclient/resource.rb:51:in `get'
    /home/efreiber/kubeclient/lib/kubeclient/common.rb:181:in `block in get_entities'
    /home/efreiber/kubeclient/lib/kubeclient/common.rb:53:in `handle_exception'
    /home/efreiber/kubeclient/lib/kubeclient/common.rb:179:in `get_entities'
    /home/efreiber/kubeclient/lib/kubeclient/common.rb:85:in `block (2 levels) in define_entity_methods'
    /home/efreiber/kubeclient/test/test_kubeclient.rb:60:in `test_proxy_enabled'

73 runs, 269 assertions, 0 failures, 1 errors, 0 skips

I think that webmock doesn't support the proxy option.

@enoodle where is the test_proxy_enabled test in this PR?

@abonas I forgot to push it before because it doesn't work. Added it now.

@enoodle the travis failures are around VCR exception from what I briefly saw.
also, there are rubocop violations as well.

@simon3z @abonas I removed the test that I couldn't make work. I looked at RestClient and was that it was relaying on net::http to implement the proxy and it only tests that those parameters are passed on: https://github.com/rest-client/rest-client/blob/f0e2dc4327e91002187541de6baa0c35b125c549/spec/unit/request_spec.rb#L434

@enoodle what's missing to move this out of WIP? (Beside the fact that we can't test if the proxy is actually used with the stub).

@simon3z nothing. Its working as intended.

@jonmoter @grosser @msufa can you review this?

rebased.

@moolitayer can you review this one? Thanks.

LGTM :+1:

LGTM :+1: cc @abonas

I had cpl of comments inline in the code, but in addition, please clarify the following:
readme file documents that kubeclient needs to be initialized with this parameter:
:http_proxy => proxy_uri
However kubeclient.rb file is not modified in this patch, so I'm unclear on how this is supposed to pass the proxy details to common.rb.
Also, in the test, another parameter name is used that is different from the readme (:http_proxy_uri)

@abonas I fixed your comments on the test file and the type in the README. we dont need to change anything in kubeclient.rb becase the **options passes the http_proxy_uri to initialize_client in lib/kubeclient/common.rb


Android minimal version requirement

Type (choose one): Question
NLog version: 4.3.2 and above
Platform: Xamarin Android
I noted that NLog version 4.3.0 and 4.3.1, the target Android version is 5. NLog version 4.3.2 and above are targeting Android 6.
Is it possible to reduce the target to Android 4.4?
Thanks.

Why is this closed? Not needed anymore?

I found out that this is somehow a non-issue if we have the latest Android SDK. We just need to compile using the Android SDK version equal or higher than used to compile NLog. The compiled app/dll still work for target earlier than the SDK version.

Ok thanks for the update

FYI supported 4.4 in https://github.com/NLog/NLog/pull/1531

Thank you.


[stable] allocator_list unittests: Use core.memory.pageSize instead of minimumPageSize

Nothing else in druntime/Phobos uses the problematic minimumPageSize symbol. Problematic because the page size changes from 4 to 16 KB with macOS 11.0. See https://github.com/dlang/druntime/blob/c27346a7f471b1e31194c71e962c44a0d28a2c85/src/core/memory.d#L168-L179.

I can confirm on the DTK this change is making the allocator_list.d unittest pass in x86_64 and arm64 arch. Where it would crash o, both previously.


Share code between HSplit, VSplit

H and VSplit share a lot of code,create an intermediary class.
It seem that beyond the Swap width/height, the only difference is in extended_height, I suppose this is to allow things to overflow through the bottom of the screen. Would it make sens to introduce a (potentially useless)  extended_width and find a way to share more code ?

Failure seem random, cannot curl smth. Can you relaunch this travis test ?


Add specific events to allow handling backpressure in TCP sessions

Goals:

[x] TCP sockets trigger a TCP_BACKPRESSURE_DETECTED event when the libuv write buffer reaches a preconfigured threshold
[x] When the write buffer clears, they should trigger TCP_BACKPRESSURE_EASED instead

In NodeJS (and luvit), this is basically the drain event, which is implemented by all Streams (in NodeJS at least).
However, I'd rather have more descriptive and non-generic events for the different streams.

While working on this I noticed the code is extremely messy, mostly due to libuv callback soup and some inconsistencies between client and servers. I'm not sure if anything can be done about this, but it's probably worth keeping an eye on the TCP modules to avoid creeping tech debt as more features are needed in the future.


I cannot select style from commandline

Using Pygments version 2.9.0 I am unable to change style from commandline, via -O style=... flag:
Given this sample file:
package main

func main() {
  println("Hello World")
}

and running:
$ python3 -c "from pygments.styles import STYLE_MAP; print(\"\n\".join(STYLE_MAP.keys()))"| \
  while read x; do echo "// Using $x style..."; pygmentize -v -O style=$x hello.go; echo; done

I get all outputs colored in the exact same style:

Nevermind, looks like I needed to also select a formatter, namely terminal16m. For the record, here is the full command I used, and now it works: pygmentize -f terminal16m -O style=inkpot.
Cheers!


Update __repr__ of datapipes

Codecov Report
Patch coverage is 100.00% of modified lines.

Files Changed
Coverage

src/gravitorch/creators/datapipe/random.py
ø

src/gravitorch/datapipes/iter/batching.py
100.00%

src/gravitorch/datapipes/iter/dictionary.py
100.00%

src/gravitorch/datapipes/iter/length.py
100.00%

src/gravitorch/datapipes/iter/path.py
100.00%

src/gravitorch/datapipes/iter/saving.py
100.00%

src/gravitorch/datapipes/iter/shuffling.py
100.00%

src/gravitorch/datapipes/iter/source.py
100.00%

:loudspeaker: Thoughts on this report? Let us know!.


Reports

When I used Microsoft Edge to join the 1.18.2 server, the blocks of Y<0 don't display properly.
Make the Debug screen can display more information & add all debug-keys if you can.
DO YOUR BEST!
THANKS.

The first issue is a pviewer issue; could you please open an issue there?
Can you also please open a separate issue (it’s easier to track with separate issues for each feature) for the debug screen (if it doesn’t already exist)?
Thanks


survey form

Survey Form
This is a project that contains some semantic Html elements and CSS elements.
Built with:

select -This is used to pick an option in a code
placeholder - This is used to offer instruction for user input.
label submit input
background-color display , margin, padding,
font-type, font-size,

This link below contain the project image's link

####This link can be used to preview the project on browser
https://vercel.com/gbemisola19s-projects/04-fcc-survey-form

Survey Form
This is a project that contains some semantic Html elements and CSS elements.
Built with:
HTML5 form elements

select -This is used to pick an option in a code
placeholder - This is used to offer instruction for user input.
label submit input
background-color display , margin, padding,
font-type, font-size,


Is caching allowed in Lab 5?

Summary
Can I check if we are allowed to use caching in this lab? My first submission (after lab) got through and codecrunch did not complain about my cache attribute being non final. I did some debugging and tried to resubmit again but this time codecrunch raised this error that my cache attributes are not declared final.
Screenshots
First submission

Re-submission

the use of cache is allowed, but this whole cache idea should be encapsulated by Lazy

the use of cache is allowed, but this whole cache idea should be encapsulated by Lazy

@Wenbo-J Just came across this, how would you "memoize" the answer? I'm wondering if it's possible with a final customer; or it needs to be modified.

@SungMatt You may try to passing around the cached supplier (that has "memorized" the answer) when needed, the memorization is within the Lazy class


Add support for project roles

Motivation
We have added new endpoints to the Management API for project roles and we would like it to be covered in the SDK.
(!) Going to be released in the first half of January 22.
Proposed solution
The SDK should include the functionality of the new endpoints for roles:

get all roles
get role by identifier

Additional context
See Docs preview for more detailed info.
The endpoints that were added:

GET /{projectId}/roles

returns all roles in the project, no pagination
sample response:

{
  "roles":[
    {
      "id":"7dedb656-aef7-40ae-8158-98bbf3542f4a",
      "name":"Project manager",
      "codename":"project-manager"
    },
    {
      "id":"ee483b59-5a24-4010-b277-ae224c34bc71",
      "name":"Custom role"
    }
  ]
}

GET /{project_id}/roles/{role_identifier}

returns role by its identifier (id or codename)
sample response:

{
  "id":"7dedb656-aef7-40ae-8158-98bbf3542f4a",
  "name":"Project manager",
  "codename":"project-manager"
}

Released on 2022-01-12

We need to cover new endpoints as well as update code samples in docs.

[ ] Cover endpoint
[ ] Update code samples


Add base-ref and base-sha outputs.

Add outputs with the Found PR's base ref and base sha.
Base being what you're targetting your PR into, often main | master.  Eg. at the time of committing here, it would be:
base-ref: main
base-sha: aa49606811598ff8ea924cb03b306f14a1d4a7ca

This can no longer get from the action context and must use the findPullRequestFromSha function to get the full API response data.
See: https://docs.github.com/en/rest/reference/commits#list-pull-requests-associated-with-a-commit

This didn't work necessarily; I think that the Github Workflow is being ran with this PR's code, but rather master's code…
Will take the risky merge and see if it works!  Jest passes, so I expect so.


JBDS-4000 Introduce download-manager urls

Add dmUrl into requirements.json
Downloader uses dmUrl
Downloader calculates .sha256 urls for dmUrl
Tests fixes
Temporary use of public links from previous release

test this

test this


No Stack or Queue implementations yet

DESCRIPTION
Issue #111 has not been resolved yet and there aren't any queue implementations yet either.
STEPS TO REPRODUCE
Creating C++ files that will have Stack operations like push and pop based on arrays and pointers and Queue operations like insert and delete based on arrays and pointers.
EXPECTED OUTCOME
The repository would now contain algorithms of both Stacks and Queues
ACTUAL OUTCOME
--
Proposed Solution [optional]
Creating and adding the above algorithms into the Linked Lists Folder

@prateekiiest  Sir I would like you to assign this issue to me

I guess queue was already being done by some one

Issue #164  was raised by @dewangmodi
The issue is regarding the absence of Circular Queue

Oh I'm sorry Sir, PR #175  was submitted regarding the issue.
I sincerely apologize for not checking the PRs

Sir, @Arkadyuti30 has submitted the programs using the programming language JAVA.
I would like to add a .cpp file containing the same algorithms using the language C++


[Feature] Create a separate form site to integrate with main site instead of google forms

Problem
Following #9 the submission form is using and it's related to Google Forms being used. Moreover as I already suggested using Google Forms isn't a great idea because we don't have full control over the data.
Description/Alternative
My features suggestion is that we should create our own form component and host it on a subdomain like form.resources.creativecommmons.org and then embed that on the main jekyll site using iframes like we are doing now. The form component can be built using vanilla HTML5, CSS3 and a bit of JavaScript/TypeScript. But we would need some sort of backend for organizing and storing the data.
I have an idea for that as well. We could leverage GitHub to use it as a backend. The user would fill up a normal form but using GitHub API we would create an issue for the submission and if the issue gets approved, it gets automatically added to the site using a workflow. (The idea is somewhat inspired by #109 but we won't be forcing users to have a GitHub account so it will be a much better approach in my opinion.
Implementation

[x] I would be interested in implementing this feature.

@asrvd This idea as exactly as #109 . You need to have a GitHub account to create issues and pull requests.

@asrvd This idea as exactly as #109 . You need to have a GitHub account to create issues and pull requests.

No the user doesn't need to have a GitHub account, we aren't implementing authentication, the issue would be automatically created from an automated bot account.

@asrvd This idea as exactly as #109 . You need to have a GitHub account to create issues and pull requests.

No. The user doesn't need to have a GitHub account, we aren't implementing authentication, the issue would be automatically created from an automated bot account.

Please read the issue description again :)

we shouldn't expect all the users to have a GitHub account neither we should force them to have one, the site should be usable by everyone.

@asrvd This idea as exactly as #109 . You need to have a GitHub account to create issues and pull requests.

No. The user doesn't need to have a GitHub account, we aren't implementing authentication, the issue would be automatically created from an automated bot account.

Please read the issue description again :)

Oh! really sorry for that. Deleting comment to keep the comment section clean.

Hi @asrvd I liked your issue as it's very important to have data security for any Organisation. Since there was already has a option to submit a resource via google form  but since Creative Commons has already used Jeykll my approach is  to create a form but use google firebase as a backend data the user needs to sign  via google/ Microsoft  or Facebook account in before submitting the form.
Reasons to use

Firebase Database: It allows real-time database connection, which means multiple users can see the changes in the data when the data gets created or edited.

Data transmission is handled with web sockets so you don't have to send requests to get new data, you only need to subscribe once.

Data is secure and reliable in future implementation Creative Commons  may use Google Cloud and use other features

Who wants to  submit  resources to creative commons directly via firebase and be able to fetch and display them on the webpage we know all visitors may always have a google account/ Microsoft account so it is accessible and efficient

Hello Sir @possumbilities what about your opinions if yes please allow me to move forward I would be very happy to work on it

@Pursottam6003 (not a Sir)
I would say this would put too much of the functionality outside the project and be a bit much to maintain long term. I'm open to other's suggestion, on other issues around this, but I'm closing this as something that while inventive is probably a bit too ambitious for this project.
@asrvd thankyou for taking the time regardless! ❤


Improper type inferred in presence of overloads

TypeScript Version:  2.1.0-dev.20160916
Code
interface Editor {
  on(e: string, h: (x: Editor) => void): void;
  on(e: string, h: (x: string, e: any) => void): void;
  on(e: 'foo', h: (x: Editor, e: any) => void): void;
}

let cm: Editor = null as any;
cm.on('bar', (x, y) => {});

Expected behavior:
cm.on() infers some type for its second param that is accepted by the compiler, given that the param has no types specified.
Actual behavior:
err.ts(8,14): error TS2345: Argument of type '(x: Editor, y: any) => void' is not assignable to parameter of type '(x: string, e: any) => void'.
  Types of parameters 'x' and 'x' are incompatible.
    Type 'string' is not assignable to type 'Editor'.

It appears to infer that its param should have the third overload's expected type, but then typechecks it against the second overload.
It appears to also be sensitive to the order in which the overloads are declared.
(This is reduced from a larger example that involves the CodeMirror d.ts files.)

This example from @rkirov is a bit smaller and has maybe the same error.
interface Editor {
  on(h: (x: boolean) => void): void;
  on(h: (x: string, e: string) => void): void;
}

let cm: Editor = null as any;
cm.on((x, y) => {});

Argument of type '(x: boolean, y: any) => void' is not assignable to parameter of type '(x: string, e: string) => void'.
  Types of parameters 'x' and 'x' are incompatible.
    Type 'string' is not assignable to type 'boolean'.

I ran into this and I found out that if you replace the overload by an equivalent sum type it works!
This is maybe not so hard to fix so I hope the typescript team can give this some prio.
type FirstArgument<Fn extends (t: any) => any>
    = Fn extends (t: infer T) => any ? T : any;

Faulty behavior in the case of overloads:
interface MyFunction1 {
  (arg: string): any
  (arg: number): any
}

// should be string|number but acctually is number
type StringOrNumber1 = FirstArgument<MyFunction1>

Correct behaviour in the case of sum types:
type MyFunction2 =
    ((arg: string) => any)
    |
    ((arg: number) => any)

// is string|number
type StringOrNumber2 = FirstArgument<MyFunction2>

The definition in the OP has signatures in the wrong order - callbacks with more parameters should go first:
interface Editor {
  on(e: string, h: (x: string, e: any) => void): void;
  on(e: string, h: (x: Editor) => void): void;
  on(e: 'foo', h: (x: Editor, e: any) => void): void;
}


Update mgmt yml file

Update mgmt yml file to be closer to client yml file
still needs to be separate until we can get the mgmt tooling
to work with dotnet pack/test commands.
Added eng/mgmt.proj which builds all mangment libraries.
Updated root build.proj to include both mgmt and client libraries.
PTAL @shahabhijeet @mitchdenny @chidozieononiwu

/azp run net - mgmt - ci

/azp run net - mgmt - ci

@weshaggard I updated mgmt.yml last night as there were couple of PRs that wanted me to review/merge, so I excluded SDK directory, hence you see the conflict for that file.


Error message handling

We should have "nice" error output when possible. For example when:

Generator errors return JspmError for all errors that don't need an error stack (non-internal errors). We only need to show the message for these.
Similarly errors with nice messages thrown from within the CLI code itself don't need error stacks - throw new Error('import map not found') doesn't need to log a stack. So we distinguish between internal errors that do need a stack and nice errors which can be stackless. There's a few techniques for this, I quite like the separate error class for non-stack errors throw new JspmError(...) where class JspmError extends Error { constructor () { super() } } and that's it.

I'd handle this after #140 since it has some changes related. let me focus on other issues.


Null dereference in ippWriteIO for value collection

Found by fuzzing
Getting the crash with ./fuzzipp crash-e1a5e250cf0fa5a27edc86104712940cedd80eab
with crash-e1a5e250cf0fa5a27edc86104712940cedd80eab being a file whose base64 encoding is MQC6vhm6OgAINAAC7gcw
A simple fix may be
diff --git a/cups/ipp.c b/cups/ipp.c
index 3a341f217..a52d6621e 100644
--- a/cups/ipp.c
+++ b/cups/ipp.c
@@ -6024,7 +6024,11 @@ ippWriteIO(void       *dst,              /* I - Destination */
                  /*
                  * Then write the collection attribute...
                  */
-
+            if (value->collection == NULL) {
+                DEBUG_puts("1ippWriteIO: No collection to write value");
+                _cupsBufferRelease((char *)buffer);
+                return (IPP_STATE_ERROR);
+            }
                   value->collection->state = IPP_STATE_IDLE;

                  if (ippWriteIO(dst, cb, 1, ipp,

@catenacyber Thanks for reporting this. It should not be possible to get a NULL collection value from reading an IPP message, so the correct fix needs to be in the ippReadIO function. Investigating...

@catenacyber OK, so this isn't something that would affect (crash) cupsd or any other IPP server using libcups since we would never echo back a broken message like this. The simple solution is to delete the pending (new) attribute once we see that the value cannot be read:
[master 655ed2928] Delete an empty attribute if we aren't able to get the value length, otherwise the IPP message will contain a truncated attribute that cannot be written (Issue #195)


How does requery handle entity changes on version increment.

I've been searching in the issues and in general for the correct way to handle changes to my entity model. Up to now I've had the luxury of just deleting the old DB, but this is no longer the case..
I know of the version parameter when constructing DatabaseSource, but how does requery know which columns/fields/properties belong to which version. I've found a @Version annotation, but its unrelated to this. Will the versioning be messed up if I delete generated code?
I take it requery does not drop columns, if you have an old required column, but it's no longer used can the upgrade modify it to use a default value, or change to nullable?
I'm using the following:
Android
requery 1.3.
Kotlin 1.1.2-3
KotlinEntityDataStore.
TableCreationMode.DROP_CREATE
Thank you

requery supports additive changes to a database model. That is you can add tables/columns/indexes and it will generate the sql to create them when you update the model schema version. It does this by querying the existing columns and adding the missing ones.
Dropping columns/indexes or changing the fundamental type of a column are a more complex case because existing data will have to be lost, possibly in unpredictable ways. For your specific case about removing a non-null constraint, that's not really supported in SQLite you would have to move the data into a new table without the constraint.

Thanks,
Is there a way to hook into requery's upgrade function to run my own SQL?
On Fri, May 5, 2017 at 5:25 PM, Nikhil Purushe<EMAIL_ADDRESS>wrote:

requery supports additive changes to a database model. That is you can add
tables/columns/indexes and it will generate the sql to create them when you
update the model schema version. It does this by querying the existing
columns and adding the missing ones.
Dropping columns/indexes or changing the fundamental type of a column are
a more complex case because existing data will have to be lost, possibly in
unpredictable ways. For your specific case about removing a non-null
constraint, that's not really supported in SQLite you would have to move
the data into a new table without the constraint.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/requery/requery/issues/551#issuecomment-299495338,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AExyFeDBLUQt_dig5NAJA0oj-ZoMVcxKks5r2z9tgaJpZM4NRWm9
.

Hi yes you can extend DatabaseSource which extends Android's builtin SQLiteOpenHelper then you can override onUpgrade to execute any custom statements you need.

Thanks again. Much help
On Mon, May 8, 2017 at 8:07 AM, Nikhil Purushe<EMAIL_ADDRESS>wrote:

Hi yes you can extend DatabaseSource which extends Android's builtin
SQLiteOpenHelper then you can override onUpgrade to execute any custom
statements you need.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/requery/requery/issues/551#issuecomment-299780875,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AExyFUHqrh-BjWOXIbqGSqJqn7bur0CEks5r3rE3gaJpZM4NRWm9
.


For All Function in Power Apps

[Enter feedback here]

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

ID: e2ac30ff-c2c0-02b8-c502-4daaf0e15b00
Version Independent ID: e2ac30ff-c2c0-02b8-c502-4daaf0e15b00
Content: ForAll function in Power Apps - Power Platform
Content Source: power-platform/power-fx/reference/function-forall.md
Service: power-platform
Sub-service: power-fx
GitHub Login: @gregli-msft
Microsoft Alias: gregli

Thanks for your comment, @Deep-177. This issue has been assigned to the doc author for review.

There are no issues in this article. Please ignore the case.
Regards,
Deepak Saroop


chore(main): release 0.35.0

:robot: I have created a release beep boop
0.35.0 (2024-12-23)
Features

Add autocompletion for tool names and versions (e742e6f)
Add mise fmt (5e9be2e)
Open env variables defined in other files than toml files (9c2f2ac)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.35.0
:sunflower:


Uploader fixes

Is this for serial over USB? Because I thought the baudrate would not matter there.

No, for serial - @zehortigoza A quick description in a PR would be appreciated.

Jenkins test this please

Rebased and continued here: Rebased and continued here: https://github.com/PX4/Firmware/pull/5607

@julianoes the reason is in the commit message:
Uploader tool: Reboot board and keep it in bootloader

The Mavlink reboot messages was only requesting the board to reboot.
If the flashed bootloader has a small or no timeout user will
never be able to update firmware.


Use 200 as default status for deletes that reply with content

As per #1549, having deletes use 204 as the default status when a body is present causes some issues. Sending a 204 No Content with content will likely surprise some clients, and it causes the formatter to be skipped.
This PR adds a check for @body.present? so that we only default to 204 No Content when there's actually no content.

👍 On the MR!
I'm really thinking we should just use a helper that combines status + body false, like I suggested before in the discussion:
def return_no_content
  status 204
  body false
end

Why is this much better?

Explicit
No magic, maybe I want to return a 200 without any body, this will be converted to a 204 but I got a legacy client from 1989 that doesn't understand 204 (we all have our dragons :D)
We should have logical defaults and less magic, this really helps making Grape solid and consistent: This means we always return status 200/201(POST) unless set explicitly.

Also now we only set 204 on a delete when there is no body, this is just not consistent with other HTTP methods (why is delete so special?)

@jthornec Add a paragraph about this to UPGRADING please?
Consider the return_no_content improvement too, although we can take that as a subsequent PR from @JanStevens.
@LeFnord @namusyaka can you please chip in here to make sure I don't merge something we don't want?

I like this change because it looks like it corrects 1 specific bug: if there's a body on DELETE, don't return 204, but 200. I can live with that.
Now, I do believe there're a lot of sensible arguments in #1549 around what to do "in general", notably the following does make sense to me too:
if request.request_method == Grape::Http::Headers::POST
  201
elsif @body.empty?
  204
else
  200
end

@dblock Again why the magic behaviour for a specific method + no body returned? Helper would be more than sufficient. I keep bitching about this since I strongly feel this is magical and quite unexpected behaviour (what if i want to delete return nothing but want status 200, legacy clients for example?)
I vote for helper only :D

I've updated this PR to include the return_no_content helper and a section in UPGRADING.md explaining the changes.

@JanStevens I hear you. If we hadn't shipped this change in a previous version I would probably just say "you're right" and leave things as is. @LeFnord @namusyaka I need some help deciding.

yes, l'll confirm this within a few hours.

First of all, we have to apologize that that changes in the case were insufficient.
Actually, the behavior that the formatter skipped, for example, wasn't what we meant.
Well, regarding this pull request, never this change is wrong.
Let's check rfc.

A successful response SHOULD be 200 (OK) if the response includes an entity describing the status, 202 (Accepted) if the action has not yet been enacted, or 204 (No Content) if the action has been enacted but the response does not include an entity.
https://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.7

As written here, this changes is reasonable (but it's not complete..).

Also now we only set 204 on a delete when there is no body, this is just not consistent with other HTTP methods (why is delete so special?)

It's true that there is no consistency. However, we should commit considering changes at 0.19.0.
I can't say that this change certainly keeps consistent behavior in grape.
From developers who respected the last change, I think this change is the least damaging approach.
Also, The delete route can be said to be special because we made a mistake.
Therefore, I'd like to vote to both helper and this change.

Thanks @namusyaka, @LeFnord?

as I said here https://github.com/ruby-grape/grape/issues/1549#issuecomment-270461521, I see this as the best solution

Also now we only set 204 on a delete when there is no body, this is just not consistent with other HTTP methods (why is delete so special?)

good point, for that @dblock's suggestion for a general handling
when Grape::Http::Headers::POST
  201
when<EMAIL_ADDRESS>  204
else
  200
end

should be implemented
but this can also be done in a different PR IMHO

I am going to merge this. Lets let it sit for a bit on master. I'd like @JanStevens and @jthornec to at least confirm you're happy (enough) with this change.

I'm happy with this change.
My issues were that the formatter wasn't running, and the 204 with content might confuse my client. This fixes both of those things, and all my app's tests pass now, so I'm good to move forward with the upgrade once this gets released.

I am going to cut a release today.

@dblock … 👍 cool, so I can run tests and cut new ones for grape-entity and grape-swagger

And done.


Feature request: invoke handler

It is often the case that we want to do some further handling of a request after termination with caddy-l4. One example would be using the caddy http module to match on HTTP headers, rewrite URLs, or conditionally forward to different downstreams.
We do have some existing overlap of functionality in the l4.http module but it doesn't seem desirable to start lifting over further "missing functionality" from caddy into l4, or as a user to fork it for this purpose.
Currently, I see two ways to achieve this without modifying caddy-l4:

Putting caddy-l4 in listener_wrappers, wrapping downstream listeners

I have not tried this but seems working: https://github.com/mholt/caddy-l4/issues/102
This seems to be the idiomatic way?

Have a separate http app running on a local socket and have caddy-l4 dial it

This works fine and is relatively trivial to configure but is inefficient and ugly

If caddy-l4 adds support for an invoke handler matching the API of the http app and forwarding to named routes from other apps, it seems that we could get a nice middle-ground option which:

matches Caddy API
is relatively less complex than using listener_wrappers
shouldn't need accommodating for protocol particularities or larger changes in caddy-l4

Possibly at some point later I could take a stab at an early implementation if I could get a sanity-check on the above assumptions and suggested approach.

Related:

https://github.com/mholt/caddy-l4/issues/77
https://github.com/mholt/caddy-l4/issues/70
https://github.com/mholt/caddy-l4/issues/102
https://github.com/mholt/caddy-l4/issues/119
https://github.com/mholt/caddy-l4/issues/207
https://github.com/mholt/caddy-l4/issues/209
https://github.com/mholt/caddy-l4/issues/101

Have a separate http app running on a local socket and have caddy-l4 dial it

This works fine and is relatively trivial to configure but is inefficient and ugly

A while ago I experimented with making a listener that can "pipe" data directly within the process, without the inefficiencies of re-dialing: https://github.com/caddyserver/caddy/pull/5040
It seems like that would go a long way to fulfilling the feature request?


Crash on opening notification

Hey guys,
i tried to open a notification with gitpoint.
The app crashed immeditely.
I tried it with 2 different notifications.
Somebody can reproduce this crash?
Have iOS 11.0.2 on an iPhone 7 running latest GitPoint version

Update: I reinstalled gitpoint because everything crashed from this point on.
Everything is working smooth now and i can open one notification of the two i recieved.
Number 1, which broke gitpoint, is a notification about a comment in https://github.com/octokit/discussions/issues/7 when i try to open this notification gitpoint crashes and everything is "broken" from this point. I cant open issues, notifications and pr's anymore.
Probably something inside of this issue brings gitpoint to crash because it cant handle something.

Probably we could test this if somebody else subscribes to this issue and waits to recieve a notification.
If gitpoint crashes then we know where the issue comes from.

Seems to be caused by this exact comment: https://github.com/octokit/discussions/issues/7#issuecomment-327616339

Here's the error screenshot:

Seems to be related to this issue in RN: https://github.com/facebook/react-native/issues/10635

Do you want to take a look at this?

@machour probably I should change the issue title, because this is not related to notifications. It will happen also if I open the issue directly.


Full test coverage for /pkg/morserino_com/list_com.go

Based on the discussion with Julien, I was able to successfully implement a mock for the go.bug.st/serial/enumerator/GetDetailedPortsList() function.
This function scans available port on the system and tries to identify a port used by the Morserino USB serial device.
The same function is used in the lsiten_com.go (when auto identification of the port is requested). Note that this file will be substantially refactored in order to render it testable.

Thanks a lot for the very instructive comments @jlevesy . Much appreciated.


WIP, BUG: fix sparse random int handling

SciPy wheel builds have been failing for the last ten weeks, which has caused a number of issues to fly under the radar until my attempt to start the wheel build process for 1.2.0rc1 as described in https://github.com/MacPython/scipy-wheels/pull/37.
This PR targets perhaps the most worrisome of the failures, in scipy.sparse.tests.test_construct::TestConstructUtils::test_random_sampling.
I was able to reproduce one of the several failing wheel build matrix entries locally by using numpy==1.8.2, Cython==0.29.0, Python==2.7, and SciPy master branch.
The changes made in this PR were sufficient to patch that specific test failure locally, but that doesn't mean we actually want to fix it this way, and I'm not sure how imposing this fix is after the branch has happened--maybe not too cumbersome yet without a tag having been pushed.
The original compatibility layer addition was quite recent -- #9048 by @jor-.

E   ValueError: low >= high

Lock       = <built-in function allocate_lock>
RandomState = <class 'mtrand.RandomState'>
__builtins__ = <builtins>
__doc__    = None
__file__   = '/venv/lib/python3.4/site-packages/numpy/random/mtrand.cpython-34m.so'
__loader__ = <_frozen_importlib.ExtensionFileLoader object at 0x7f22052cbd30>
__name__   = 'numpy.random.mtrand'
__package__ = 'numpy.random'
__spec__   = ModuleSpec(name='numpy.random.mtrand', loader=<_frozen_importlib.ExtensionFileLoader object at 0x7f22052cbd30>, origin='/venv/lib/python3.4/site-packages/numpy/random/mtrand.cpython-34m.so')
__test__   = {'RandomState.binomial (line 3546)': '\n        binomial(n, p, size=None)\n\n        Draw samples from a binomial dist...0.3])\n        array(['pooh', 'pooh', 'pooh', 'Christopher', 'piglet'],\n              dtype='|S11')\n\n        ", ...}
_rand      = <mtrand.RandomState object at 0x7f22052d8c18>
_shape_from_size = <built-in function _shape_from_size>
beta       = <built-in method beta of mtrand.RandomState object at 0x7f22052d8c18>
binomial   = <built-in method binomial of mtrand.RandomState object at 0x7f22052d8c18>
... <etc>
zipf       = <built-in method zipf of mtrand.RandomState object at 0x7f22052d8c18>

mtrand.pyx:941: ValueError
=========================== short test summary info ============================
FAIL sparse/tests/test_construct.py::TestConstructUtils::test_random_sampling

I can't say I get the logic of either the original code or the fix, it's unclear to me what the options are for *args, **kwargs. Deserves some more comments.
Note that if this takes a while to resolve, you could also consider reverting that PR in 1.2.x. The problem seems to be for numpy <1.11.0 only, which we're dropping in master very soon.

randint didn't have the dtype argument for the older NumPy versions with a compat layer here.
--- a/scipy/_lib/_numpy_compat.py
+++ b/scipy/_lib/_numpy_compat.py
@@ -95,6 +95,11 @@ else:
     # method of RandomState does only work with int32 values.
     def get_randint(random_state):
         def randint_patched(*args, **kwargs):
+            # args should be: low, high, size
+            # kwargs should only really contain
+            # dtype argument not available in older
+            # NumPy versions, which couldn't handle
+            # int64
             try:
                 low = args[0]
                 size = args[2]

The patched function is probably a bit awkward though, and may be important to check which of its codepaths are actually tested locally.
The top of _numpy_compat.py  has a docstring with Functions copypasted from newer versions of numpy, but I think the random stuff is in Cython so we'd likely need to add in a compiled compatibility layer if we don't already have one (and only if it doesn't branch out too much to other parts of NumPy, which it might). I suspect @rkern would agree this is asking for trouble / maintenance issues.

Revised based on revisions requested from CJ, though I don't have immediate access to the local test environment originally used for reproduction since I'm at BIDS at the moment.

I reproduced the original test failure locally on the latest master branch (04c0e5f6f) using above-described dependencies & then confirmed that the test passes on the revised version of this PR branch (f9ad4bda4) in the same environment.
CI is all-green too. If there's still too much concern about the shim after the simplifications above then I should probably consider the PR reversion.

LGTM now, merged. Thanks @tylerjereddy and @perimosocordiae

Unfortunately we're still getting a related wheel build failure with OverflowError: Python int too large to convert to C long.
It looks like we really do have to ensure that all arguments to randint are within np.int32 bounds for the old NumPy version. Do we want to try attacking that with another PR, reverting the functionality, or xfail for old NumPy?

Out of all distributions available, it's only randint that fails right, all the other distributions do work? If so, I'd suggest to either skip testing for randint or xfail the test on 1.2.x.

#9550 might fix the problem with randint and old NumPy versions.


Implement floating panel

Floating Panel will contain a few elements on page as usual panel, but doesn't have a base locator. So it isn't locked to root element.

Implemented in pull request #16

Merged.


_get_dependency_versions throws value error if dependency not found

If a dependency is not found (for example it is not in the set of aliases), then a
value error is thrown ValueError: not enough values to unpack (expected 2, got 1), when
it attempts to split the string on ==. Could we get a better error message?

I believe this is resolved now, Testing it I don't see this behavior

Saw this error again when working:
cmd: realreq-d -s <dir>
Traceback (most recent call last):
  File "[path]/realreq", line 8, in <module>
    sys.exit(main())
  File "[path]/_realreq/realreq.py", line 34, in main
    app()
  File "[path]/_realreq/realreq.py", line 66, in __call__
    dep_ver = _get_dependency_versions(pkgs)
  File "[path]/_realreq/realreq.py", line 197, in _get_dependency_versions
    dep, ver = line.split("==")
ValueError: not enough values to unpack (expected 2, got 1)

Looking at this it could be caused by installs of packages from git repos e.g:
udl @git+https://gitlab.com/<project>/udl.git@commit

resolved


American option price under Cox-Ross-Rubinstein

Binomial options pricing models like Cox-Ross-Rubinstein have been widely used since they are able to handle a variety of conditions for which other models cannot easily be applied proving themselves to be more accurate, particularly for longer-dated options on securities with dividend payments.

Alexandre: Thanks for suggesting this issue and thanks Neil for volunteering to tackle it.
Binomial trees in general are relatively lower priority for us, partly because they don't generalize efficiently to the multi asset case. It is also not clear how efficiently they can be implemented in TF. However, CRR has the simplicity of recombining trees so the memory requirements should be reasonable for reasonable time steps and completeness of the toolbox would be nice.
If you are still happy to do it, Neil, I will assign the issue to you.

@neil-menghani
There has been no activity on this so I will be reassigning this to myself.

+brilhana
I have added a (admittedly not the most general) version of the CRR binomial tree for American (and European) options.
The main limitations I see (which we will remedy in the next few iterations) will be to support time dependent rates and volatility.
I will leave the bug open for a couple of days and then close it to give you a chance to comment if you give it a spin.

I am closing this issue now. Please create a new one if you spot any issues with the current implementation.


SVG stroke/fill is not removed in Storybook build

Bug Description
Storybook build does not replace fill/stroke with currentColor as the primary build does. This makes the Storybook build less reliable as a reference.
However, width/height is removed, so some SVGO plugins are running.
This SVG:
<svg width="32" height="32" viewBox="0 0 32 32" fill="none" xmlns="http://www.w3.org/2000/svg">
<path d="M21 8.5V23.5" stroke="green" stroke-linecap="round" stroke-linejoin="round"/>
<path fill-rule="evenodd" clip-rule="evenodd" d="M12 14C11.1716 14 10.5 14.6716 10.5 15.5V16.5C10.5 17.3284 11.1716 18 12 18H17C17.8284 18 18.5 17.3284 18.5 16.5V15.5C18.5 14.6716 17.8284 14 17 14H12Z" fill="hotpink"/>
</svg>

Results in this list of icons:

With this source in place of the SVG:
<svg viewBox="0 0 32 32" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M21 8.5v15" stroke="green" stroke-linecap="round" stroke-linejoin="round"></path><path fill-rule="evenodd" clip-rule="evenodd" d="M12 14a1.5 1.5 0 00-1.5 1.5v1A1.5 1.5 0 0012 18h5a1.5 1.5 0 001.5-1.5v-1A1.5 1.5 0 0017 14h-5z" fill="#ff69b4"></path></svg>

Also, notice how the fill color name is normalized to a hex value, but the stroke is not.

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

As per https://github.com/google/web-stories-wp/pull/6272#discussion_r574936829, it could be that the svgo config is not found in the root of the project for the storybook webpack config, which kinda makes sense.
Seems like we'd need to duplicate that config and pass it directly to the webpack config here:
https://github.com/google/web-stories-wp/blob/c9956a4aa83d970f43951e7d8f985bf6c470277e/.storybook/main.cjs#L50-L53
Something like this should work:
config.module.rules.unshift({
  test: /\.svg$/,
  use: [
    {
      loader: '@svgr/webpack',
      options: {
        titleProp: true,
        svgo: {
          plugins: [
            {
              removeViewBox: false,
              removeDimensions: true,
              convertColors: {
                currentColor: /\b(?!url|none)/i,
              },
            },
          ],
        },
      },
    },
    'url-loader',
    assetLoader,
  ],
});

However, width/height is removed, so some SVGO plugins are running.

That's not SVGO, but SVGR itself. See https://react-svgr.com/docs/options/#dimensions

So I just took your SVG:
<svg width="32" height="32" viewBox="0 0 32 32" fill="none" xmlns="http://www.w3.org/2000/svg">
<path d="M21 8.5V23.5" stroke="green" stroke-linecap="round" stroke-linejoin="round"/>
<path fill-rule="evenodd" clip-rule="evenodd" d="M12 14C11.1716 14 10.5 14.6716 10.5 15.5V16.5C10.5 17.3284 11.1716 18 12 18H17C17.8284 18 18.5 17.3284 18.5 16.5V15.5C18.5 14.6716 17.8284 14 17 14H12Z" fill="hotpink"/>
</svg>

And in the editor it is turned into this:
<svg viewBox="0 0 32 32" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M21 8.5v15" stroke="green" stroke-linecap="round" stroke-linejoin="round"></path><path fill-rule="evenodd" clip-rule="evenodd" d="M12 14a1.5 1.5 0 00-1.5 1.5v1A1.5 1.5 0 0012 18h5a1.5 1.5 0 001.5-1.5v-1A1.5 1.5 0 0017 14h-5z" fill="#ff69b4"></path></svg>

Which is identical to what you shared in you post:
<svg viewBox="0 0 32 32" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M21 8.5v15" stroke="green" stroke-linecap="round" stroke-linejoin="round"></path><path fill-rule="evenodd" clip-rule="evenodd" d="M12 14a1.5 1.5 0 00-1.5 1.5v1A1.5 1.5 0 0012 18h5a1.5 1.5 0 001.5-1.5v-1A1.5 1.5 0 0017 14h-5z" fill="#ff69b4"></path></svg>

Soo... it's not working at all?! 🤔 😩
Only when I manually added the SVGO config to webpack.config.cjs and removed the .svgo.yml did it work...
But apparently the currentColor regex doesn't work as expected either.

OK #6361 should fix this... 🤞


FactorIndexer returns new columns

Description and related tickets, documents
Added  def transform(ddf: DDF, newColumnNames: Map[String, String]): DDF into FactorIndexer, if newColumnNames is null then it overwrites the columns (previous behavior), otherwise it will create new columns based on the map.
Reviewers: @Huandao0812 @hai-adatao
Breaking changes & backward compatible issues
No
How to test
PR Progress
Make sure all checkboxes below are checked before merged

[x] Branch is in format prefix/description (see this)
[ ] Merge check has no conflicts. PR checks passed.
[ ] Code review is done.

lgtm


Move the TS4900 from experimental to production

fixed by https://github.com/resin-os/resin-ts/pull/97


Add servicePriority cluster property

What this PR does / why we need it
Adds the option to specify the service priority label, as defined in https://github.com/giantswarm/rfc/tree/main/classify-cluster-priority
Checklist

[ ] Update changelog in CHANGELOG.md.

Trigger e2e tests

/test create
/test upgrade

/retest


Move to Java 11 for building and running

Description
Move to using java 11 for building and running the containers.
Related issue and scope

[X] (Someone) opened an issue to propose and discuss this change (#4217)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[X] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[ ] Bug fix (generally a non-breaking change which closes an issue).
[X] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[X] I signed an Apache CLA.
[X] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

@dubee -

Are all of the JAVA_OPTS in the Ansible deployment roles still valid with the newer version of Java?

I looked there and nothing seemed to out of the ordinary. Also doesn't travis use ansible to get a cluster up to test it?

Also, the default garbage collector in Java 8 was Parallel GC, whereas the default in Java 11 is G1 GC. Has there been any investigation to determine if we should use G1 GC or Parallel GC?

No I haven't looked beyond the normal performance tests, do you have something in mind to run?

A performance test using each type of GC while comparing memory consumption of the controller and invoker should tell us.

@mcdan can you resolve the conflicts?

I sent a note to the dev list because I didn't see one https://lists.apache.org/thread.html/9acf4c4e213a4385c14f4bc9e4a1724ff79189ce4f35bf5ce1e239c6%40<dev.openwhisk.apache.org>
I will merge this PR next week assuming conflicts are resolved.

Should we replace this file also? https://github.com/apache/openwhisk/blob/master/tools/ubuntu-setup/java8.sh

Per the discussion on the tech interchange call, we are accepting this PR as is. A subsequent PR can apply this suggested change https://github.com/apache/openwhisk/pull/4706#discussion_r381441881 per the dev list note from @mhenke1.

My proposed change can be found as an unmerged pull request to the originating branch of this PR:
https://github.com/adobe-apiplatform/incubator-openwhisk/pull/12

Thanks Martin. Would you mind rebasing that branch? I can open the PR then.

Unfortunately my private OW Fork is utterly broken. I can not even delete it. I will open a PR as soon this is working again.

yikes - that maybe explains why it is not showing up in the pull down list for creating a new PR.


New TypeDef not persistent

If you create your own TypeDef, then after restarting the Egeria, all these TypeDefs disappear
I suppose this is due to the fact that TypeDefs are cached and not made constant
https://github.com/odpi/egeria-connector-xtdb/blob/5c4a10edf3c21262489c7d471904bc43324e93e0/connector/src/main/java/org/odpi/egeria/connectors/juxt/xtdb/repositoryconnector/XtdbOMRSMetadataCollection.java#L80
Will their permanent storage be realized?

There are descriptions and examples in the open-metadata-resources/open-metadata-archives module. https://github.com/odpi/egeria/tree/master/open-metadata-resources/open-metadata-archives

@cmgrote, @mandy-chessell , thank you, we tried this option. It turned out to be what we needed.


A question about Fig 3(charades-sta, "leave") in the paper

The denifition of axes in the paper is  "The left density plots in Fig. 3 show the overall distributions of the temporal moment locations in Charades-STA and ActivityNet Captions, where the horizontal and vertical axes are the starting time and duration of a moment, both of which are normalized to the range of 0 to 1 by dividing them by the length of the respective video".
So any point in the figure should satisfy: x + y <= 1, where x, y is normalized starting time and duration of a moment described by point, but points in the  right-bottom corner of Fig 3(charades-sta, "leave") are exceptions. Could you explain about that?

and the Charades-STA's<EMAIL_ADDRESS>value  is 39.81 in the 2d-tan, not 42.2 (fig4)


feat: split trail.ts (Unsummarized)

Splitting trail.ts into logically smaller files.

/reviewpad prompt is this PR good?

/reviewpad robin prompt Review this PR

/reviewpad robin prompt suggest code improvements


fix(project): Set new projects to private by default

Corollary to https://github.com/rungalileo/api/pull/1377.

Codecov Report

Merging #752 (1fec4d0) into main (99269e8) will decrease coverage by 0.08%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #752      +/-   ##
==========================================
- Coverage   88.50%   88.42%   -0.08%
==========================================
  Files         174      174
  Lines       14219    14208      -11
==========================================
- Hits        12585    12564      -21
- Misses       1634     1644      +10

Files
Coverage Δ

dataquality/clients/api.py
51.03% <100.00%> (-0.45%)
:arrow_down:

... and 7 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Weekly Calendar

Hi there! Currently I'm developing a weekly calendar and when I want to set a custom date after using startWithMonth option, my weekly calendar starts showing all dates of month, but it has to show only the full week with custom date. Is there any way to achieve this?

Can you please post your configuration and template? I'd need to see what your working with to recommend anything.

Part of my template:

                    <% _.each(daysOfTheWeek, function(day) { %>
                        <%= day %>
                    <% }); %>

                    <% _.each(days, function(day) { %>
                        <%= day.day %> <%= intervalStart.format('MMM') %>
                    <% }); %>

                   ...

And configurations:
var calendar = $('#calendar').clndr({
//startWithMonth:  moment(),
startWithMonth: "2016-01-01",
template: $('#full-clndr-template').html(),
weekOffset: 1,
daysOfTheWeek: ['SUN', 'MON', 'TUE', 'WED', 'THU', 'FRI', 'SAT'],
lengthOfTime: {
days: 7,
interval: 7
},
targets: {
nextButton: 'schedule-arrows-next',
previousButton: 'schedule-arrows-prev'
},
events: lotsOfEvents,
multiDayEvents: {
endDate: 'end',
singleDay: 'date',
startDate: 'start'
},
clickEvents: {
click: function(target) {
console.log(target);
},
},
});

Part of my template:

                    <% _.each(daysOfTheWeek, function(day) { %>
                        <th class="<%= day %>"><%= day %>
                    <% }); %>

                    <% _.each(days, function(day) { %>
                        <th class="<%= day.classes %>"><%= day.day %> <%= intervalStart.format('MMM') %>
                    <% }); %>

                   ...

And configurations:
var calendar = $('#calendar').clndr({
    //startWithMonth:  moment(),
    startWithMonth: "2016-01-01",
    template: $('#full-clndr-template').html(),
    weekOffset: 1,
    daysOfTheWeek: ['SUN', 'MON', 'TUE', 'WED', 'THU', 'FRI', 'SAT'],
    lengthOfTime: {
      days: 7,
      interval: 7
    },
    targets: {
        nextButton: 'schedule-arrows-next',
        previousButton: 'schedule-arrows-prev'
    },
    events: lotsOfEvents,
    multiDayEvents: {
        endDate: 'end',
        singleDay: 'date',
        startDate: 'start'
    },
    clickEvents: {
      click: function(target) {
        console.log(target);
      },
    },
});

@Ane-tta I think you found a bug. I haven't confirmed it yet, but my hunch is that the error is happening here: https://github.com/kylestetz/CLNDR/blob/master/src/clndr.js#L228
Line 228 of the library.:
if (this.options.startWithMonth) {
    this.month = moment(this.options.startWithMonth).startOf('month');
    this.intervalStart = moment(this.month);
    this.intervalEnd = moment(this.month).endOf('month'); // <- BAD LINE
}

This is setting the ending interval to be the end of the month, even if the lengthOfTime.days options is specified (like in your case).
The workaround is to use lengthOfTime.startTime instead of startWithMonth until I get this fixed.

@Ane-tta Sorry for the long delay in this, but I pushed up a fix in #269. If you are able to, could you please pull that branch and test your app against it? I'm almost certain it's 100% working, as I tested it in the test file after re-creating your bug, but if you're able to confirm it I'll compile this directly to 1.4.4. Thanks again for reporting the bug.

This is up in 1.4.4. It works :P


ModelFit plot - No artists with labels found to put in legend.

Hi, I am running Modelplot command as shown in the snippet. But everytime I am not getting the legends of the detectors in the plot. Is it a bug or do I need to make any change for that? Since there was no such issue in GBM tools before like this.

@nyctophile-aayu  In both the GDT and the GBM Data Tools, the legend is updated by the detector name in the response objects that are passed to the spectral fitter.  I would need to see how you are reading/extracting the response and how you are passing it to the spectral fitter to see what the problem is.

@AdamGoldstein-USRA It is somehow working, but I am generating it using Matplotlib instead of modelfit. But there is an issue while doing background subtraction. I have to provide the energy range that is greater than the energy limit defined for both NaI and BGO detectors. Is it okay to do so, or is it wrong? If you wish, I can mail you my notebook.

I am sharing the notebook. It might require access to open. Please check and lemme know what I am doing wrong in it. However, I can generate the results using this notebook as well.
https://drive.google.com/file/d/14yIteu1NH0UpxYOhowWmxZjcw8BYrfFN/view?usp=sharing

@nyctophile-aayu The link you posted does not appear to work.  You should be able to attach it here in the same way you attached a file in this post.

@AdamGoldstein-USRA I'll do that. Once you receive it please acknowledge.
SpecFit-II (T & E resolved)-I.zip

@nyctophile-aayu I ran the notebook, and I think I found the issue with the mission lables on the spectral fit plot.  The rebinning of the response does not preserve the detector information, and hence does not propagate to the plot legend.  This should be a simple fix in the code.
Regarding the energy selection, the energy selection for the BGO, while larger than the actual energy range of the BGO, will snap to the energy range of the data.  However, I suggest setting the BGO energy range to start at no lower than ~250 keV and to exclude the highest energy channel.  The highest energy channel is the overflow channel, and the channels below ~250 keV has poor calibration.  The low energy channel for the NaI looks good, just make sure again to remove the overflow channels before fitting.

@AdamGoldstein-USRA  Thank you for identifying the issue. At this stage, is there anything we can do to address the problem with the legend in the model plot, or do you think we should wait for the bug to be resolved? Additionally, can you suggest which attributes I should apply during the rebinning of the response to mitigate this?
Furthermore, I've encountered an issue setting the BGO energy range from 250 keV to 1 or 10 MeV. The background subtraction performs poorly in this range, with the background line significantly exceeding the source light curve, which I understand should not occur. I attempted this, and the light curve plots appear incorrectly as a result. You can try that as well. Could you please advise on the best approach to correct this?

@nyctophile-aayu
I have created a branch on gdt-core that fixes this issue.  You can pip install that branch and test to see if it solves your problem with displaying the detectors.
With regards to setting the energy range and background fitting, you are plotting the lightcurve integrated over energy_range, however you are integrating the lightcurve over the full energy range.  This is the line in your notebook that is the problem:
bkgd_lcs.append(bkgd_map[detector_name].integrate_energy())  # Call without energy_range
Integrate the background over the same energy range as your lightcurve, and that should solve your problem:
bkgd_lcs.append(bkgd_map[detector_name].integrate_energy(*energy_range))

@AdamGoldstein-USRA Yes, it goes through. Thank you so much for your patience and understanding.


Add S3 Infrequent Access calculator.

The calculator gives an idea about the cost savings by providing your bucket size, number of requests etc. You can checkout the calculator here at http://www.gulamshakir.com/apps/s3calc/index.html

LGTM. @max-zanko review?

Thank you for taking a look. I fixed the whitespace.


Address -Wunused-private-field Warnings

Codecov Report

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

@@            Coverage Diff             @@
##           master      #73      +/-   ##
==========================================
+ Coverage   60.12%   60.13%   +0.01%
==========================================
  Files         306      306
  Lines       49367    49367
==========================================
+ Hits        29681    29686       +5
+ Misses      19686    19681       -5

Impacted Files
Coverage Δ

...c/lib/profiles/data-management/Current/TraitData.h
58.18% <ø> (ø)
:arrow_up:

...files/data-management/Current/NotificationEngine.h
71.42% <ø> (ø)
:arrow_up:

src/test-apps/TestCASE.cpp
96.09% <0%> (+0.22%)
:arrow_up:

src/lib/profiles/security/WeaveCASEEngine.cpp
93.28% <0%> (+0.23%)
:arrow_up:

src/lib/profiles/security/WeaveToX509.cpp
88.8% <0%> (+0.26%)
:arrow_up:

src/lib/support/ASN1Writer.cpp
85.51% <0%> (+0.93%)
:arrow_up:

Continue to review full report at Codecov.

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


View characters of a selected anime or voice actor

One way to improve your Frontend folder structure is to have a folder with your file and then reference it using an index.js file.
For example:
pages > Anime.js could be
pages > Anime > Anime.js and index.js


Example of getting Notebook content in a type safe manner

I saw the example at https://github.com/gtk-rs/examples/blob/master/src/bin/notebook.rs and it is great. I am using it in my own project and it showed me how to customize "Types" of Widgets.
Now I would like to see an example for getting the content of a notebook page, changing it and adding it back to the notebook all in a type safe manner. The problem is that I get back a Option<Widget>, instead of whatever type I say I'll add to the Notebook. When I try to get back what I put in, obviously I know what it should be, but Rust seems not to know:
let the_tab: Option<Widget> = notebook.get_nth_page(4);  // just get the widget which was added in the fifth tab of the notebook

Then I could to the following:
let label = match the_tab {
    Some(widget) => widget.downcast::<Label>(),
    None => // what to do here?
};

I found downcast in the autogenerated docs from cargo doc in the Cast trait, after searching for an hour or more how to cast something, but still the problem is not solved, because I don't know how to handle the None case. The label must have some simple type like Label, so that I can call all the functions which are implemented for that type and work with what I got from the Notebook.
I am still a beginner in Rust, but I don't know how to proceed here. I think I would have to pass a type at creation time of the Notebook, in order to let Rust know what comes back, but that would not change the interface to suddenly give me not only Option<Widget>, but the actual more specific contained type.
An example of how to deal with such things in gtk-rs would be of great use.

As I understand you get None only if you try access to page that not exist,
so reaction only depend on what you wan't,
IMHO as  this normally don't happened,
you can use .unwrap() or better .expect("message") instead match.
Same with result of .downcast::<Label>():
or you know what type you inserted here and use .expect,
or you need decide that to do.
If you adding different types to pages,
then you can check type with http://gtk-rs.org/docs/gtk/trait.Cast.html#method.is beforehand.

@EPashkin Thanks for mentioning the Cast is thingy.

You can add generic type that contains Notebook (and deref) and add your variant append_page and get_nth_page for it,
but IMHO when all pages same type is rare and other cases can be statically checked.
IMHO better can add function like https://github.com/gtk-rs/gtk/blob/master/src/notebook.rs#L102
that generic over type T:IsA<Widget>, that do check and return Option<T>.

@EPashkin Thanks for the ideas. I have to think about this, as it is not obvious to me what the best way to go about it is.


fix: Synapse Workspace - Updated enforced location to latest supported

Description
Apparently, in March, the list of allowed locations was eastus, eastus2, southcentralus, westcentralus, westus, westus2, westus3.
As per the latest workflow run it's now apparently only uksouth
Pipeline Reference

Pipeline

Type of Change

[ ] Update to CI Environment or utilities (Non-module affecting changes)
[ ] Azure Verified Module updates:

[x] Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] Breaking changes and I have bumped the MAJOR version in version.json.
[ ] Update to documentation

@AlexanderSehr thanks for the PR. It looks good to me, the only remark would be to update the misleading title as the PR affects Purview and not Synapse.


How to perform assertions while using with mocha?

When I'm writing some tests and using nock I'm noticing that failed assertions will not be caught by mocha and instead mocha will just report that the test case timed out.  However, if I surround the assertions with a try catch block and send the error to mocha, it will work.  See the following examples:
Test case that times out:
describe('test', function() {
  it('example with nock', function(done) {

    var nockScope = nock(host)
      .get(url)
      .replyWithFile(200, file)

    asynchronousFunctionThatMakesHttpRequest(function(err, data) {

      nockScope.done()

      assert.equal(1, 0)  // error is not caught by mocha, so test case times out

    })
  })
})

Test case that does not time out:
describe('test', function() {
  it('example with nock', function(done) {

    var nockScope = nock(host)
      .get(url)
      .replyWithFile(200, file)

    asynchronousFunctionThatMakesHttpRequest(function(err, data) {

      nockScope.done()

      try {
        assert.equal(1, 0)
      } catch(e) {
        return done(e)  // error is caught and returned to test case callback
                        // and mocha reports desired error
      }

    })
  })
})

Is surrounding with a try catch the best way to do handle this situation?

I doubt the first case times out is due to the asynchronousFunctionThatMakesHttpRequest doesn't match the nock, can you double check the host of request?


Input Coordinates should be able to handle the same coordinates as Coordinate Conversion

Currently the Regular expressions that are a part of Coordinate Conversion are not in Military Symbol Editor.

We need to get the excel table from @elinz

-107° 25.4990' +28° 29.6578' and 107.424983W 28.494297N both worked for me on the Enter Coordinates tab, will need some specific examples of what is not working

closing. I cannot repro. It worked at our last released version as well


Event::Suspend should check surface.is_some and not is_none

https://github.com/AryanpurTech/BlueEngine/commit/790dcf8e76412136b6f7362fe6a9d00251d6416d#r144449242

fixed with #73


Add a Gitter chat badge to README.md

JuliaQuantum/QuDynamics.jl now has a Chat Room on Gitter
@amitjamadagni has just created a chat room. You can visit it here: https://gitter.im/JuliaQuantum/QuDynamics.jl.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Coverage remained the same at 89.916% when pulling e481edd123f26cebab4bc531b06950821ffdbff1 on gitter-badger:gitter-badge into ecb800e53d0acb3057158e592081467ce2774dec on JuliaQuantum:master.


[Snyk] Upgrade eslint from 8.14.0 to 8.15.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade eslint from 8.14.0 to 8.15.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 22 days ago, on 2022-05-06.

Release notes

Package name: eslint

8.15.0 - 2022-05-06Features

ab37d3b feat: add enforceInClassFields option to no-underscore-dangle (#15818) (Roberto Cestari)

Bug Fixes

8bf9440 fix: "use strict" should not trigger strict mode in ES3 (#15846) (Milos Djermanovic)

Documentation

28116cc docs: update AST node names link in no-restricted-syntax (#15843) (Milos Djermanovic)
272965f docs: fix h1 heading on formatters page (#15834) (Milos Djermanovic)
a798166 docs: update example for running individual rule tests (#15833) (Milos Djermanovic)
57e732b docs: mark SourceCode#getJSDocComment deprecated in working-with-rules (#15829) (Milos Djermanovic)
9a90abf docs: update docs directory in working-with-rules (#15830) (Milos Djermanovic)
810adda docs: add more examples for prefer-object-spread (#15831) (coderaiser)
06b1edb docs: clarify no-control-regex rule (#15808) (Milos Djermanovic)
9ecd42f docs: Fixed typo in code comment (#15812) (Addison G)
de992b7 docs: remove links to 2fa document (#15804) (Milos Djermanovic)
5222659 docs: fix 'Related Rules' heading in no-constant-binary-expression (#15799) (Milos Djermanovic)
e70ae81 docs: Update README team and sponsors (ESLint Jenkins)

Chores

1ba6a92 chore: upgrade<EMAIL_ADDRESS>(#15847) (Milos Djermanovic)
8167aa7 chore: bump version of minimatch due to security issue PRISMA-2022-0039 (#15774) (Jan Opravil)
b8995a4 chore: Implement docs site (#15815) (Nicholas C. Zakas)
6494e3e chore: update link in codeql-analysis.yml (#15817) (Milos Djermanovic)
36503ec chore: enable no-constant-binary-expression in eslint-config-eslint (#15807) (唯然)

8.14.0 - 2022-04-22Features

ab6363d feat: Add rule no-constant-binary-expression (#15296) (Jordan Eldredge)

Bug Fixes

35fa1dd fix: allow project paths to have URL-encoded characters (#15795) (Milos Djermanovic)
413f1d5 fix: update astUtils.isDirectiveComment with globals and exported (#15775) (Milos Djermanovic)

Build Related

c2407e8 build: add node v18 (#15791) (唯然)

Chores

735458c chore: add static frontmatter to no-constant-binary-expression docs (#15798) (Milos Djermanovic)
db28f2c chore: Add static frontmatter to docs (#15782) (Nicholas C. Zakas)
3bca59e chore: markdownlint autofix on commit (#15783) (Nicholas C. Zakas)

    from eslint GitHub release notes

Commit messages

Package name: eslint

9b17d6f 8.15.0
128b726 Build: changelog update for 8.15.0
1ba6a92 chore: upgrade<EMAIL_ADDRESS>(#15847)
8bf9440 fix: "use strict" should not trigger strict mode in ES3 (#15846)
28116cc docs: update AST node names link in no-restricted-syntax (#15843)
8167aa7 chore: bump version of minimatch due to security issue PRISMA-2022-0039 (#15774)
272965f docs: fix h1 heading on formatters page (#15834)
a798166 docs: update example for running individual rule tests (#15833)
b8995a4 chore: Implement docs site (#15815)
ab37d3b feat: add `enforceInClassFields` option to no-underscore-dangle (#15818)
2dc8d15 Sponsors: Sync README with website
57e732b docs: mark `SourceCode#getJSDocComment` deprecated in working-with-rules (#15829)
9a90abf docs: update docs directory in working-with-rules (#15830)
810adda docs: add more examples for prefer-object-spread (#15831)
c2d0a83 Sponsors: Sync README with website
bbbe755 Sponsors: Sync README with website
06b1edb docs: clarify no-control-regex rule (#15808)
6494e3e chore: update link in `codeql-analysis.yml` (#15817)
9ecd42f docs: Fixed typo in code comment (#15812)
36503ec chore: enable no-constant-binary-expression in eslint-config-eslint (#15807)
de992b7 docs: remove links to 2fa document (#15804)
5222659 docs: fix 'Related Rules' heading in no-constant-binary-expression (#15799)
e70ae81 docs: Update README team and sponsors

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

No longer needed, closing


Does not work with react

I get an error when including the rocket.chat/sdk in a react app.
Steps to reproduce:
yarn create react-app testchat
cd testchat
yarn add @rocket.chat/sdk
open App.js and add:
import { driver, methodCache, api } from<EMAIL_ADDRESS>Now when we run:
npm start
there is this error:
TypeError: Cannot read property 'map' of null
(anonymous function)
node_modules/websocket-driver/lib/websocket/http_parser.js:88
  85 |   31: 'LINK',
  86 |   32: 'UNLINK'
  87 | };
> 88 | var VERSION = (process.version || '').match(/[0-9]+/g).map(function (n) {
  89 |   return parseInt(n, 10);
  90 | });
  91 |

What can I do to make this work together?
Thanks

Same error when I try to import it to Vue/Nuxt.
To reproduce error:
yarn create nuxt-app nuxttestchat
open pages/index.vue and add:
import { driver, methodCache, api } from<EMAIL_ADDRESS>run:
yarn run dev
Same error as before with websocket http_parser.js

I had the same error too, and fixed it by updating your package.json entry for the sdk to this:
<EMAIL_ADDRESS>"1.0.0-alpha.30"
This version is the one used by RC's own react-native client, and also worked for me when trialing with plain react.


expand partial_eval to take boolean

LGTM - go ahead and merge when the checks pass

LGTM - go ahead and merge when the checks pass

Thanks!


Permission sets not updating when renaming API fieldname

Summary
When I rename API name of a field, I must navigate to relevant permission sets and update them manually.
Steps To Reproduce:

Create a field in a scratch org
Assign to relevant permission set(s)
SFDX Pull
Rename API-name of field
SFDX Pull

Expected result
I expect that after renaming the API-name of the field, the permission set is automatically updated when I pull metadata from my scratch org, giving me two files consisting of the field and the permission set.
Actual result
I only receive one file regarding the renaming, and must navigate in to the relevant permission set in the scratch org and update it, and execute another SFDX Pull to receive the file of the updated permission set.
System Information

Terminal in VS Code

Hi @ng-nina,
I tried reproducing this, but it was working as I was expecting it to.

create custom field on object
add CF to permissionSet
pull
see CF in permissionset in the project
rename the field from objects >  > fields > rename
pull
I now see the updated field name in the permission set in the project.

    <fieldPermissions>
        <editable>false</editable>
        <field>Broker__c.customField2__c</field>
        <readable>true</readable>

it was originally named customField and updated to customField2
let me know if I missed a step, or looked in the wrong place

Hello,
Thank you for your response.
Are you adding the CF to the permissionSet using Field-Level Security for Permission Sets during Field Creation (Beta)?

Hi @WillieRuemmele, we experience the same issue. However, it seems like might be related to https://github.com/forcedotcom/source-tracking and sfdx org login sfdx-url. We have a nightly job that prepares our scratch org (deploying all metadata on main branch). Then, each developer authenticates to a scratch org with all metadata preinstalled. To avoid having to push all files locally, we generate local source tracking files while we fetch the pre-generated scratch org using https://github.com/forcedotcom/source-tracking
The easiest way to replicate this would be to do the following:

Have a custom field and a permission set that references this custom field in a local project
Create an empty scratch org
sfdx project deploy the field and perm set
a.  This will generate source tracking files that we will reuse
Mimic fetching a scratch org previously created:
a. Move the source tracking (.sf/orgs/ folder) out of the project
b. Expose sfdx auth url using sfdx org display --json --verbose > auth.json
c. Delete the auth file for the newly created scratch org (.sfdx folder in your user directory)
d. Authenticate to the scratch org again using sfdx org login sfdx-url -f auth.json
e. Move the source tracking folder back to the project
Open the scratch org, rename the custom field and project retrieve down changes
a. Now, only the field should be listed as the change. The Perm Set is unchanged

Pulling v56.0 metadata from<EMAIL_ADDRESS>using the v57.0 SOAP API
Updating source tracking... done
=== Retrieved Source

 STATE   FULL NAME        TYPE        PROJECT PATH
 ─────── ──────────────── ─────────── ───────────────────────────────────────────────────────────────────
 Deleted Account.Test__c CustomField src-tmp/main/default/objects/Account/fields/Test__c.field-meta.xml
 Created Account.Test2__c CustomField src-tmp/main/default/objects/Account/fields/Test2__c.field-meta.xml

Hi @petter-eikeland 👋
Myself and a fellow CLI engineer followed your instructions a few times, with and without the setting that @ng-nina had enabled and weren't able to reproduce it 😦
do you have anything in your .forceignore that could be preventing this from working? Can you create a reproduction repository with a simple project, and script, that reproduces this issue, or a screen recording we can follow step for step?
below I've attatched the commands I ran, and their outputs. This starts from step 4c, I run a force source status command just to ensure that the auth information is removed
➜  dreamhouse-lwc git:(main) ✗  hub:(DevHub<EMAIL_ADDRESS> ➜  status (force source status)
Warning: We plan to deprecate this command in the future. Try using the "project retrieve/deploy preview" command instead.
Error (1): No default environment found. Use -o or --target-org to specify an environment.
➜  dreamhouse-lwc git:(main) ✗  hub:(DevHub<EMAIL_ADDRESS> ➜  sfdx org login sfdx-url -f auth.json
Successfully authorized<EMAIL_ADDRESS>with org ID 00DDE0000045aEk2AI
➜  dreamhouse-lwc git:(main) ✗  hub:(DevHub<EMAIL_ADDRESS> ➜  mv ../00DDE0000045aEk2AI .sf/orgs
➜  dreamhouse-lwc git:(main) ✗  hub:(DevHub<EMAIL_ADDRESS> ➜  oo (org open)
Opening org 00DDE0000045aEk2AI as user<EMAIL_ADDRESS>Waiting to resolve the Lightning Experience-enabled custom domain...... done

--
in the org, objects > Broker > fields > rename customField3
--
➜  dreamhouse-lwc git:(main) ✗  hub:(DevHub<EMAIL_ADDRESS> ➜  sfdx project retrieve start
Preparing retrieve request... Succeeded

Retrieved Source
================================================================================================================================
| State   Name                      Type          Path
| ─────── ───────────────────────── ───────────── ──────────────────────────────────────────────────────────────────────────────
| Deleted Broker__c.customField3__c CustomField   force-app/main/default/objects/Broker__c/fields/customField3__c.field-meta.xml
| Created Broker__c.customField4__c CustomField   force-app/main/default/objects/Broker__c/fields/customField4__c.field-meta.xml
| Changed Broker__c-Broker Layout   Layout        force-app/main/default/layouts/Broker__c-Broker Layout.layout-meta.xml
| Changed dreamhouse                PermissionSet force-app/main/default/permissionsets/dreamhouse.permissionset-meta.xml

I changed customfield3 to customfield4 on the Broker object in dreamhouse.

@WillieRuemmele Thanks for your swift investigation. I'm also struggling reproducing the issue again with the steps above. I must be missing a step or two. I will investigate further how I can confidently reproduce our issue without reimplementing our implementation of https://github.com/forcedotcom/source-tracking and come back to you


@include forces that include file must always exist.

First of all thanks for this great plugin. This is my first of two issues that I have faced using grunt-preprocess. Although not sure whether I should report these in preprocess repo or here, I am reporting here but advise me otherwise.
Consider if I have used something like in my source file:
// @ifdef WIDGETS
// @include ../temp/widgets.inc
// @endif

In my usecase, widgets.inc will only be generated conditionally but whenever WIDGETS is set in the task, widgets.inc does exist.
Problem arise when my task context does not set WIDGETS and hence no widgets.inc exists. The preprocess task will fail reporting that widgets.inc doesn't exist. My workaround for this has been to have an empty widgets.inc always and overwrite it when required.
As far as I have understood, this happens because @include is processed before @ifdef. (See preprocess() in preprocess.js). I don't know if it is there by design or for a reason but my opinion is since @ifdef is a block level directive, its body may contain other directives so it should be processed first.

Please open issue on https://github.com/nashdot/Preprocessor.js.
Grunt task is based on it.


Deploy & Upgrade adjustments

This PR includes documentation and script fixes which adjust the deployment and upgrade processes. The upgrade process is now set to re-use the deployment script, and the deployment script will no longer create the ELK stack containers if they are not going to be used. The documentation also now includes an extra step to do the same for non-AIO builds.

:+1:

LGTM, @mattt416 can you confirm the 2 commits that came in after your previous comment are OK and then we can merge this?

:+1:

backport?


Add Conformance Clause(s) to Spec

This was requested by the OCI TB Certification Program WG and I believe Stephen Walli (HPE) will be submitting a PR very soon.

We will try and get this into v0.5.0 if it comes in today. Otherwise we will punt to v0.6.0.

I chatted with Stephen and expect a draft this afternoon.

I suggested additional language in a pull request on the runtime-spec file. Apologies if I'm out of order on workflow. Haven't directly contributed until now.

On Wed, Apr 06, 2016 at 02:27:15PM -0700, Stephen Walli wrote:

I suggested additional language in a pull
request on
the runtime-spec file.

The PR should probably target the opencontainers repo, not your
personal fork.

@stephenrwalli has opened PR #373 with proposed language.

With thanks to @mrunalp, this is addressed in PR #374

#374 is merged.


fix: enable builds on Windows

PR summary
This PR modifies the project to allow developers to build and test the project on Windows.
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

Current vs new behavior

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

Updated this PR to completely remove the pylint.sh and .bat files. Instead, I updated the Makefile so that the "lint" and "lint-fix" targets invoke pylint directly instead of via the scripts.

:tada: This PR is included in version 0.40.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Support Angular 6: Do you have plan support Angular 6?

I'm submitting a ...
[ ] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Do you want to request a feature or report a bug?

What is the current behavior?

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar.

What is the expected behavior?

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Angular version: 2.0.0-rc.X
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Basically a duplicate of #99 since the issue is rxjs

I have ported this library here with angular6 and rxjs6 support. ngx-toasta.
And also with some extra enhancements.
npm install ngx-toasta


Column widths

This adds setting column widths in colgroups as a percentage.
Example With Alignment and Without Widths
| Head A | Spanned Header ||

Head B
Head C
Head D

1A
1B
1C

2A    ^
2B
2C

3A    ^
3B       3C

4A
4B       4C^

5A    ^
5B
5C

6A
6B ^
6C

Example With Alignment and Widths
| Head A | Spanned Header ||
| Head B | Head C | Head D |
|:--20%--|:-50%--:|--20%--:|
| 1A     |    1B  |    1C  |
| 2A    ^|    2B  |    2C  |
| 3A    ^|    3B       3C ||
| 4A     |    4B       4C^||
| 5A    ^|    5B  |    5C  |
| 6A     |    6B ^|    6C  |

Example Without Alignment and Widths
| Head A | Spanned Header ||
| Head B | Head C | Head D |
|---20%--|--50%---|--20%---|
| 1A     |    1B  |    1C  |
| 2A    ^|    2B  |    2C  |
| 3A    ^|    3B       3C ||
| 4A     |    4B       4C^||
| 5A    ^|    5B  |    5C  |
| 6A     |    6B ^|    6C  |

Thanks @dbolack-ab ! Added some tests and changed to use HTML width since Markdown should not generate CSS.


Fix byte order detection for np.uint8 and other types for which byte order is not defined.

Fixes: #154

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Hi @KOLANICH ,
Thanks for the fix.
Do you mind not changing the return type | seems like the correct return type for _byteorder so we would need to just do
if byteorder not in {'<', '|'|:  to fix it instead.
In addition, I think adding a test is worth it.
I can take care of everything if you want.

I was thinking about a better solution - just remove that function and replace it with def is_endian_ok(dtype) -> bool:. We currently don't support any endian except le and it is unlikely that anything except LE will be implemented in any new hardware. TBH IMHO only le endian makes sense because ints of different sizes are compatible to each other (wrt zero padding in MSBs) and because it is easier to deal with in software-implemented arythmetics. It was strange that BE got used in any hardware at all given its drawbacks, such a simple idea as LE seems to be uncopyrightable and unpatentable.

and, BTW, feel free to do everything yourself.

def is_endian_ok(dtype) -> bool:. We

Even better idea, I did just that !

I had to create #160 since I can't commit to your branch unfortunately.


Add concept doc on how exclusive placement works

What would you like to be added:
Add concept doc on how exclusive placement works
Why is this needed:
Users often have questions about how it works and it is helpful info for them to be able to debug issues on their own

/remove-lifecycle stale

/remove-lifecycle rotten

/assign
I will try this!

Is this issue meant to demonstrate how to use and operate, or is it to be explained through code?

__

Is this issue meant to demonstrate how to use and operate, or is it to be explained through code?

It's meant to explain how exclusive placement is implemented. I.e., a leader pod (index 0) from each Job is created, with pod affinity/anti-affinity rules ensuring only 1 leader pod lands in each topology domain (e.g., rack, node pool, etc). All follower pods (non-0 indexes) are blocked from creation until their corresponding leader pod has been scheduled. Once a leader pod from a job is scheduled, the follower pods in that Job will be created and have nodeSelectors injected which ensure they land in the same topology domain as the leader.

__

Is this issue meant to demonstrate how to use and operate, or is it to be explained through code?

It's meant to explain how exclusive placement is implemented. I.e., a leader pod (index 0) from each Job is created, with pod affinity/anti-affinity rules ensuring only 1 leader pod lands in each topology domain (e.g., rack, node pool, etc). All follower pods (non-0 indexes) are blocked from creation until their corresponding leader pod has been scheduled. Once a leader pod from a job is scheduled, the follower pods in that Job will be created and have nodeSelectors injected which ensure they land in the same topology domain as the leader.

OK, I understand, I will also demonstrate with examples

/remove-lifecycle stale


New developer

closes: #1468
Account number: f6f38190713621648c7a1d8e52cb300e9da5cad47aa190004dcc22a17c1963d2

@bojan-ilijevski created a separate PR for this, since there were some issues with this PR: https://github.com/thenewboston-developers/Website/pull/1504
You'll still get paid for it though