Rounding in Python

Code:
print (round(3.555, 2))
print (round(2.555, 2))
print (round(1.555, 2))

Output:
3.56
2.56
1.55

Why doesn't round(1.555, 2) give 1.56 as the output?

Duplicate of https://github.com/satwikkansal/wtfpython/issues/196


Some error while start using swagger-autogen

Hello,
I'm just getting start, and when I build documentation without starting the project.
I got an error by following:
><EMAIL_ADDRESS>swagger-autogen
> node ./swagger.js

/home/iottalk/scratchtalk/ScratchTalk/node_modules/swagger-autogen/src/swagger-tags.js:546
    const quotMark = swaggerDescription[0];
                                       ^

TypeError: Cannot read property '0' of undefined
    at Object.getDescription (/home/iottalk/scratchtalk/ScratchTalk/node_modules/swagger-autogen/src/swagger-tags.js:546:40)
    at /home/iottalk/scratchtalk/ScratchTalk/node_modules/swagger-autogen/src/handle-files.js:1037:88
npm ERR! code 1
npm ERR! path /home/iottalk/scratchtalk/ScratchTalk
npm ERR! command failed
npm ERR! command sh -c node ./swagger.js

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iottalk/.npm/_logs/2021-12-02T19_26_28_801Z-debug.log

Besides, I have created a swagger.js file at the level of my root file.
this is the file:
const swaggerAutogen = require('swagger-autogen')(); //this is for swagger2.0

const doc = {
  info: {
    title: 'Scratch API',
  },
  host: 'localhost:3000',
  schemes: ['http'],
  // by default: empty object (Swagger 2.0)
  //components: { ... }, // by default: empty object (OpenAPI 3.x)
  //definitions: { ... }, //your definitions
};

const outputFile = './apidoc/scratchtalk_api.json';
const endpointsFiles = ['./index.js', './routes/auth.js', './routes/project.js', './routes/rc.js'];
/* NOTE: if you use the express Router, you must pass in the
   'endpointsFiles' only the root file where the route starts,
   such as index.js, app.js, routes.js, ... */

swaggerAutogen(outputFile, endpointsFiles, doc);

I'm not sure where is the error.

Hi @rreexxllii0310! Thank you for opening the issue.
Could you post here all the "#swagger.description" used in your code, please? Or, if you prefer, you can post a sample project that reproduces this problem as well. That way it is easier to find and handle the error.

Hi @rreexxllii0310! Thank you for opening the issue.
Could you post here all the "#swagger.description" used in your code, please? Or, if you prefer, you can post a sample project that reproduces this problem as well. That way it is easier to find and handle the error.
Thanks for answering!

I have just written the docstring in Auth.js, the project.js and the rc.js have not yet.
the following is my #swagger annotation in Auth.js:
router.get('/', authRedirect = (req, res) => {
    /* #swagger.tags = ['Auth']
       #swagger.descriptions = ['Redirect user-agent to the authorization endpoint or login if have loggined before']
       #swagger.responses[302] = {
                    description: 'Redirect to IoTtalk Account Subsystem login page.'
       }
       #swagger.responses[404] = {
                    description: 'Failed to redirect to OAuth page.'
       }
    */
}

router.get('/callback', authCallback = async (req, res) => {
    /* #swagger.tags = ['Auth']
       #swagger.descriptions = ['Authentication callback url.']
       #swagger.parameters['code'] = {
                in: 'query',
                description: 'grant type: code',
                required: true,
                type: 'string'
       }
       #swagger.responses[302] = {
            description: 'Redirect to index.'
       }
       #swagger.responses[401] = {
            description: 'OAuth provider failed to authorize user.'
       }
    */
}

router.get('/logout', logout = async (req, res) => {
    /* #swagger.tags = ['Auth']
       #swagger.descriptions = ['Logout and clean session.']
       #swagger.responses[302] = {
            description: 'Redirect to index'
       }
       #swagger.responses[404] = {
                    description: 'User has not logged in'
       }
       #swagger.security = [{
            "oAuth2": [
                "openid",
            ]
       }]
    */
}

router.post('/status', async (req, res) => {
    // check if session exist to determine whether the user has logged in or not
    /* #swagger.tags = ['Auth']
       #swagger.descriptions = ['Check if session exist to determine whether the user has logged in or not.']
       #swagger.responses[200] = {
            description: 'response session status.'
       }
       #swagger.security = [{
            "oAuth2": [
                "openid",
            ]
       }]
    */
}

router.post('/userprofile', async (req, res) => {
    /* #swagger.tags = ['Auth']
       #swagger.descriptions = ['Get user information']
       #swagger.responses[200] = {
                    description: 'response session status.'
       }
       #swagger.responses[401] = {
                    description: 'Not Logged In.'
       }
       #swagger.security = [{
            "oAuth2": [
                "openid",
            ]
       }]
    */
}

@rreexxllii0310,  there are two things to see in your code. #swagger.description have no 's' at the end and they receive a string parameter. So, instead of:
#swagger.descriptions = ['Get user information']
change to:
#swagger.description = 'Get user information'
To see more about description, you can click here
The latest version (2.13.3) released now, did many improvements about the error's messages.
Any other problem, let me know.

@davibaltar
The problem is solved.
Thank you for replying!


Fix Header UI and Accessibility

Navbar doesn't have a mobile dropdown menu
The logo needs to be updated
The logo should redirect to the homepage
The alignment needs to be fixed

Okay, let me fix this.

I have fixed and pushed fix-ui_HOMEPAGE  branch. It has the most recent updates of the landing page.

Alright, I will fix this once it get to this page. @misspee007


macOS: swap command for control keys in integrated terminal

vscode already has a macOptionIsMeta config for treating option key as meta in the integrated terminal. It'd be good if you could add a macCommandIsControl option as well.
Context: Many Linux users who have to use Macs map their control key to command to make most things behave similarly between linux and macOS. One expecption where control is absolutely necessary is the terminal. I can use something like Karabiner Elements to map Command to Control in my dedicated terminal app (based on the app bundle ID) but don't want to do that across the entire VS Code.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

Same issue here.

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Migrate to travis-ci.com

travis-ci.org will be closed down on december 31, public repos are required to migrate to travis-ci.com before that date (see newsletter).
As an alternative, we could switch to GitHub Actions.

I tested GitHub Actions (see here), here's my thoughts:

it's faster than Travis, the pipeline took 14 minutes to build and test all image tags
if a single job fails you can't re-run only that like any sane CI solution, you have to re-run the whole pipeline

Agree that Travis isn't the solution to go anymore.
As an alternative, I propose also evaluating Azure DevOps Pipelines, which are of course free for open source. If I'm not wrong, GitHub Actions are basically a wrapper around that platform, and syntax is pretty much similar. I'll take a look at that and open a test branch in the afternoon.


Runtime of List.length

Can the runtime of List.length be added to the Remarks section of its documentation?
The standard implementation for a linked list would have linear runtime, but maybe F#'s list caches the length in the "head node" so that a constant runtime is possible.  Since F#'s list is immutable, this is a textbook example of a time-space tradeoff: either choice has advantages over the other.
I briefly looked at the F# code to see if I could determine for myself what the implementation (and thus runtime) is.  If someone wants to "teach me how to fish" in addition to "giving me a fish", that too would be greatly appreciated.

Based on these runtime tests, it appears to be a linear-time computation.
Case 1 compuated in 00:00:00.0004770 has length 10
Case 2 compuated in 00:00:00.0000022 has length 100
Case 3 compuated in 00:00:00.0000286 has length 1000
Case 4 compuated in 00:00:00.0003881 has length 10000
Case 5 compuated in 00:00:00.0008908 has length 100000
Case 6 compuated in 00:00:00.0070297 has length 1000000
Case 7 compuated in 00:00:00.0586394 has length 10000000
Case 8 compuated in 00:00:00.4871563 has length 100000000

That is correct, lists are implemented as singly linked lists and determining the length requires iteration over it until the last item, performance is O(n). Conversely, arrays have a fixed length and getting this length is O(1). While at it, sequences need to be evaluated in full, which can have side effects, but apart from that, getting their length is O(n).
I agree that the docs should have info on performance characteristics, I think there's a more general item open somewhere.


[INTERNAL] use eslint-plugin-ava and cleanup test-suite

Coverage remained the same at 94.042% when pulling e6e98d450380d92c89b7273e5aa1f9c0ace495f5 on eslint-ava into 3fe72a633748d6d88b8ac35527ef980cfd4d8b2e on next.


[f1] build: use vite to build bundle

Prior to this commit, rollup was being use to bundle the application directly. This was 1) slow and 2) difficult to use when trying to also support UMD modules.
The CJS and ES dependencies that are used in this project don't play nicely with the commonjs() rollup plugin, making it difficult to create a UMD bundle. Using vite side-steps this issue.
The one major drawback here is that the CSS cannot be inlined into the JS. So we have to both 1) provde an index.css file that includes the videojs styles and 2) check if it's being used and fallback to using a <link> tag that references the CSS if it's not.

Stacked PR Chain: f1

PR
Title
Status
Merges Into

#46
(Draft)fix: detect if vjs css present

-

#47
👉 (Draft)build: use vite to build bundle

#46

Closing this as this was handled in #48


turn off when serving ?

archive generation takes quite some time for our site; without it ~1-2seconds with it 7-10seconds.
any way to have archive generation turned off when rendering in serve mode ?

You can use a second config file to disable the plugin when you are serving. For example, in
_config_dev.yml:
jekyll-archives:
  enabled: false

Then run:
bundle exec jekyll serve --config _config.yml,_config_dev.yml

that’s a nice trick - thanks!


Release first version

@rultor release pls, tag=0.1.0

@rultor release pls, tag=0.1.0

@aliceice OK, I will release it now. Please check the progress here

@rultor release pls, tag=0.1.0

@aliceice Done! FYI, the full log is here (took me 3min)


Add unit tests for LoadWorkflowExecution method

What changed?
Add unit tests for LoadWorkflowExecution method

Why?
improve coverage

How did you test it?
unit tests

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 018eb012-70f6-4a29-93e3-b58da8b38ea9
Details

22 of 24 (91.67%)  changed or added relevant lines in 1 file are covered.
19 unchanged lines in 7 files lost coverage.
Overall coverage increased (+0.02%) to 66.592%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

service/history/execution/context.go
22
24
91.67%

Files with Coverage Reduction
New Missed Lines
%

common/task/weighted_round_robin_task_scheduler.go
2
88.56%

service/history/task/transfer_active_task_executor.go
2
72.7%

service/matching/taskListManager.go
2
80.46%

common/persistence/historyManager.go
2
66.67%

service/history/task/fetcher.go
3
85.57%

service/history/task/transfer_standby_task_executor.go
4
86.19%

service/history/queue/timer_queue_processor_base.go
4
77.62%

Totals

Change from base Build 018eafb9-de7b-4258-9306-2e578a222f87:
0.02%

Covered Lines:
97431

Relevant Lines:
146310

💛  - Coveralls


[Thesis] Multi Technology Participant Deployment

This PR includes work on new features including:

Implemented extension of the EDMM model with multiple participants
Enabling the deployment of specific components and deployment technologies through new REST-Endpoint
Automated generation of BPMN workflows based on the EDMM model
Integration of Camunda Engine for the orchestration and data exchange with other participants
Initial GUI for the orchestration and management of the overall application deployment

One last thing before I merge... I understood that it is still possible to execute the stuff without the Camunda engine. Is this somewhere documented how to enable the Camunda-less implementation?

The provided implementation by Felix has not been altered and can still be executed through the CLI. If only technology_regions are detected, the multi participant implementation is skipped.

Ah that's great. Could you also please document these two routes somewhere?! So, Camunda-less -> use CLI, Choreo -> use web and new "app".

So let's leave this PR open till the doc part is ready.

I've added the documentation. If I've missed some aspects in the documentation, I can add them before we can start merging to master.


feature request: add callbacks

add callback provisioning or api feature so that you can send/forward new data to a url instead of polling with current api.

Hi, I don't get your need. :grimacing:
Could you describe a bit more your use case ?
Which part of Leshan are you talking about ? server, client , libraries, demos ?

Sorry, server side that is.
Our current use case is we have device sending data to a leshan server and we'd like to forward all updated data to our ingestion pipeline's http server. For example if the server get's updated data from the client, an event triggers and sends the data to a url.

I'm not sure to get what you are calling "updated data from the client" ?
Could you be more specific (and ideally exhaustive) ? :pray:

We have a device with a lwm2m client sending sensor values to a leshan server. Client is connected and the leshan server has the current sensor values. Our end goal is to get these current values out of the leshan server to the rest of our cloud environment.
Using leshan's api we can poll the leshan server to get current values but for our use case we can not pull from our ingestion pipeline. The data has to be pushed from the leshan server side. Specifically, the device goes into a power save mode state so it is only active briefly to send data to the leshan server and then it goes back into a sleep state.
We would like to trigger an event any time the leshan server receives data. Ideally an API or something that will allow each trigger to act on the new data (in our case, pass it to our ingestion pipeline)

I'm sorry but still not clear to me.
Which version of LWM2M / Leshan are you using ?

We have a device with a lwm2m client sending sensor values to a leshan server.

How does client sends data ?
Does the server send READ Request ?
Does the server send OBSERVE Request ?
Does the client send SEND Request  (lwm2m v1.1 only) ?

Using leshan's api we can poll the leshan server to get current values

Which API are you talking about ?
Are you talking about the REST API of leshan-server-demo ?  if yes which  API are you calling exactly ?
If you are talking about the Java API of leshan library I don't get what you mean.  Which java API (class/method) are you calling exactly ?

Specifically, the device goes into a power save mode state so it is only active briefly to send data to the leshan server and then it goes back into a sleep state.

So you are using Queue Mode ?

We're using lwm2m v1.1, Leshan version 2.0 for the server (updated about a week ago).
The client is also lwm2m v1.1 and uses SEND requests. We are using queued mode for power savings.
The API I mentioned we tested earlier is the leshan-server-demo REST API polling every minute.
api GET call: https://<leshan_server>/api/clients/
For our use case though, we'd like the data received by the server from the client's SEND request pushed to our ingestion pipeline instead of polled GET requests. Ideally if the server receives a send request it triggers an event which causes the server to pass the received data to a url where we have a http server set up.

OK now I get it.
leshan-server-demo is not intended to be reused. See https://github.com/eclipse/leshan/wiki/F.A.Q.#could-i-reuse-leshan--demo-
Anyway, at library level there is already a java API which allows to listen data received via SEND Operation.
leshanServer.getSendService().addListener( new SendListener {
   public  void dataReceived(Registration registration, Map<String, LwM2mNode> data, SendRequest request){
     // Implement your behavior.
   }
}

At leshan-server-demo level, there is a ServerSent event called SEND available at api/event.
You can eventually use option ?ep=YOUR_DEVICE_ENDPOINT_NAME to get only event for a given endpoint.
(See usage in our demo : https://github.com/eclipse/leshan/blob/411e34ec3572b86cc4450703f4775647c44dd11a/leshan-server-demo/webapp2/src/views/Client.vue#L129-L160

Should we close this issue ?

I close this one hoping last comment helps.
Feel free to reopen if needed


Feed URL
https://www.taniarascia.com/rss.xml
More Info
No response

closed by 0d586f7fe5283b74efbd388e9b77f90019b63b06


grpc: escape binary headers

Signed-off-by: Kuat Yessenov<EMAIL_ADDRESS>@PiotrSikora @htuch
Description: escape base64-encoded binary metadata from gRPC library
Risk Level:
Testing:
Docs Changes:
Release Notes:
[Optional Fixes #Issue]
[Optional Deprecated:]

@lizan I find it hard to break through envoy interfaces to create a binary header. gRPC lib is all hidden behind envoy interfaces, and envoy insists on non-binary metadata.

/azp run envoy-linux


Add Scalability, Availability, and Stability Design Patterns in Back-end Development.

Add awesome curated list for Scalability, Availability, and Stability Design Patterns in Back-end Development.

https://github.com/binhnguyennus/awesome-scalability
Awesome curated list for Scalability, Availability, and Stability Design Patterns in Back-end Development.
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title.For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:

Include a short description about the project/theme of the list. It should not describe the list itself.Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
Be added at the bottom of the appropriate category.

The list I'm submitting complies with these requirements:

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
It's the result of hard work and the best I could possibly produce.
Non-generated Markdown file in a GitHub repo.
Includes a succinct description of the project/theme at the top of the readme. (Example)
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.

Either fullwidth or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.
Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of sub-lists, preferably none.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
WTFPL and Unlicense are not acceptable licenses.
If you use a license badge, it should be SVG, not PNG.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Drop all the A / An prefixes in the descriptions.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.

Go to the top and read it again.

I talked to @binhnguyennus and he'll add it when it's ready.


fix(search): update to only link title in search results

Hey, I just made a Pull Request!
This change updates the way that the search page displays links.  When a user opens the search modal window, the entire block of text is a link.  This change makes it so that only the primary text (header) is a link. This aligns with how many web sites work and makes it more readable for users when hovering over the text.
Previous:

Updated:

:heavy_check_mark: Checklist

[X] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[X] Screenshots attached (for UI changes)
[X] All your commits have a Signed-off-by line in the message. (more info)

Thanks for pointing those out @kuangp . Will look into updating those as well so its consistent across the board.

@nuritizra this is ready to re-review. Let me know if there is any additional items.


Campaign details home

What this PR does
Fixes #346
Describe the purpose of this pull request and note the issue it addresses

This PR makes use of the updated campaign details home API to fetch the data for the home tab

Screenshots
Before:

After:

@gconnect can you check why codacy check is failing.

https://app.codacy.com/manual/ragesoss/apps-android-wikiedudashboard/pullRequest?prid=5081238

It's not due to this PR. In development branch, some methods don't have documentation.


[REEF-80] avoid multip-thread writing to evaluators change log on hdfs

This PR adds sync blocks for writing to evaluators change log on HDFS as an attempt to fix REEF-80. As part to the changes, we also rethrow the exception if the problem is not resolved.

@yingdachen
I have one minor comment regarding the code.
Could you please rebase this PR onto the current master branch? It would help me greatly in testing the code on our YARN cluster and merging.

All reef-tests pass on our YARN cluster. Will merge it.


Grid: Support adding horizontal split below a vertical split

Issue Type: Bug
If I have two vertically splitted editors like this:
___________
|    |    |
|    |    |
|____|____|

I want to be able to move an editor below these to to create a horizontal split like this:
___________
|    |    |
-----------
|_________|

But I cannot do that:

The editor supports this kind of layout, because if I create a horizontal split first, and split the upper horizontal, I can create the desired layout:

This is why I wonder why it is not possible to create this layout using the first method.
VS Code version: Code - Insiders 1.24.0-insider (0f4cde307559a2140cbe11989dc0052f13679921, 2018-06-01T12:17:19.366Z)
OS version: Windows_NT x64 10.0.16299
Extensions (10)

Extension
Author (truncated)
Version

xml
Dot
2.2.0

tslint
eg2
1.0.30

vscode-great-icons
emm
2.1.33

vscode-todo-plus
fab
2.1.2

vscode-insiders-language-pack-hu
MS-
1.23.1

mssql
ms-
1.3.1

debugger-for-chrome
msj
4.5.0

polacode
pnp
0.2.2

vscode-icons
rob
7.23.0

markdown-pdf
yza
1.2.0

(3 theme extensions excluded)

duplicate of #50666


Please add a feature to fix broken characters when exporting data

Please add a feature to fix broken characters when exporting data automatically so that they get exported properly.
Or at least the let the user know which files were not exported.
Thanks

Hi @CoolDouble,
What exactly do you mean by broken characters?
In output file paths, characters which are not allowed in some file systems should already be replaced automatically.
Do you get an error or do you have problems with the content of exported files?

"Invalid character in filename, failed to replace
Continue?"
If I click yes, does it still export the file? If so, under which name?

Could you post a screenshot here where I can see the filename/path? Which operating system do you use? Do you know the file system of the drive you wanted to export it to?
If you click on continue there, it will continue without that file because it could not be exported. I can fix it after I know which characters are not replaced correctly yet.

The error does not show the file names.
Windows 10 Pro 64-Bit
NTFS

Which domain or folder were you trying to export? Can you please run the program from the command line using java -jar itunes-backup-explorer-1.5.jar and post the output here after you got the error again?


Suspect typo in the paper on arxiv

I think the subscript here should be k=0.

Thank you, you are correct. The paper will be updated soon on arXiv with other minor changes as well, since it got accepted at ICPR'20.

Got it : )

Thank you for your input @mo-vic , but that is correct. The "iff" here means "if and only if".  What that sentence is trying to convey is: for any two lanes with indexes j1 and j2, if and only if j1 < j2, then the point closest to the bottom of j1 will have a smaller x value than the one in j2, which means that the lane j1 is closer to the left border of the image.

The paper has been updated on arXiv.


Update list-active-sandboxes.md

Corrected the example to have the right endpoint (with / at the end)

Fix in PR 844: https://git.corp.adobe.com/AdobeDocs/experience-platform.en/pull/844


endpointmanager: Skip warning logs for endpoints being removed

Skip warning log for failed policy update for endpoints that are being removed.
This avoids unnecessary warnings (and CI flakes) like:
Found 1 k8s-app=cilium logs matching list of errors that must be investigated:
2024-05-19T16:15:52.160976650Z time="2024-05-19T16:15:52Z" level=warning msg="Failed to apply policy map changes. These will be re-applied in future updates." ciliumEndpointName=kube-system/coredns-7db6d8ff4d-t6sjv containerID=7120688df8 containerInterface= datapathPolicyRevision=1 desiredPolicyRevision=1 endpointID=370 error="lock failed: endpoint is in the process of being removed" identity=42104 ipv4=<IP_ADDRESS> ipv6="fd02::a8" k8sPodName=kube-system/coredns-7db6d8ff4d-t6sjv subsys=endpointmanager

/test


Landing Page

create a landing page in which user can see nextjs components by category and components as well

please share screen shot before creating PR

looks good @arhamabeer


README.md: Remove duplicated line and add missing punctuation.

Description
Removed a duplicated sentence and added a missing punctuation in the readme.
Motivation and Context
Improved the readme file.
How Has This Been Tested?
README.md change only.

/azp run


Redesign of Resource create / edit screen

The current UI for the Resources is horrifically utilitarian. Since this will be one of, if not the most import touch point of the software it should be much cleaner and direct. Redesign!

Proposed design

Note the arrow next to title expands an additional area that is normally hidden for description, active status and required status

Overall I am happy with this design for iteration 1.  When tags, sharing and other features are brought in it will need modification. But for now it is good!

As part of the effort to complete #75 this one is good for now.


Auth priority value needs to match language used to describe it

Currently we have a bit of a mismatch between the fact that priority is an integer where higher values mean lower priority and vice versa. This seems like an unnecessary complication especially since we allow negative values there (so to get something to really high priority you can set the value to -1000). I think that the values and language used to describe priorities needs to match, so that low value means low priority, increasing priority means increment the priority value, etc.
Related to #1021

@elprans do you think we need to do anything about this one?

Yes, we should revisit this and #1021 for a4.


Feature request: Modifier key to open the result as "i'm feeling lucky"

Would be very useful if you want to jump straight to the top listing of a suggested term.

That’s a nice idea, but unfortunately it doesn’t really work because Google somewhat broke that solution years ago.
Now if you try to do it directly (not from their homepage) it sends you to a redirect page where you have to click a link anyway, which kind of defeats the purpose.


Google Trace degrades performance of our application

This is a cry for help / help us understand what we're doing wrong kind of issue :)
We have added Google Trace to a series of APIs for a client to help investigate some performance problems, however, on one of the projects, adding Google Trace just made the performance problems worse.
I have managed to narrow it down to a very simple repro (I can share the repository if you need it) which shows that when we add the following TraceFallbackPredicate things go south. It causes about a 10x slowdown in request handling capabilities on my local test-bed hardware, and we're seeing similar degradation in our production deploy:
options.TraceFallbackPredicate = TraceDecisionPredicate.Create(request =>
{
    // Do not trace OPTIONS
    var isOptionsCall = request.Method.ToLowerInvariant().Equals("options");

    // Do not trace our monitoring routes
    var isMonitoringRoute =
        request.Path.Equals(PathString.FromUriComponent("/"));

    return !(isOptionsCall || isMonitoringRoute);
});

Basically filter out OPTIONS calls and health checks on /.
I have performed some profiling with Rider, the first screenshot shows the flamegraph WITH our custom predicate - a lot of time is spent in EndSpan:

The following screenshot is with the predicate removed, which looks more sane:

The code profiled does some network IO and returns a response.
So what are we doing wrong? Can that trace predicate really cause this, or is something else at play?

reproduction repository is available here: https://github.com/nover/google-trace-performance-degradation-repro

I'll take a look at this in the afternoon and come back as soon as I know more.

By adding the trace predicate you are effectively tracing almost every request (except for the ones you are filtering out) as oposed to tracing 1 request per second. That's not a problem in itself, but when you combine that with the fact that you are using no buffer, then you get the latency increase you are seing (see #5632 for instance and also #5275 which is tangentially related), because now you have one "extra" service call per request. My suggestion is simply to use buffers. If you are using auto-scalable services, like Google's Cloud Run, you cannot use the timed buffer because these environments usually don't guarantee CPU cycles during downtime, in those cases you should use the sized buffer. Else you can use either buffering strategy.
I've looked at making ISpan to be IAsyncDisposable before, which would help mitigate some of this but it would involve some major and even breaking changes, and we've felt that the amount of work involved does not makes up for just a mitigation, you can still have enough requests so that the change doesn't help much. And, using buffers is mitigation enough, and a natural strategy to use for monitoring, and that you can even tweak over time depending on your load.
Let me know if this works for you.

Thanks for you always detailed answers @amanda-tarafa - I'll try to look into a combination of buffers and QPS limiting.
Side note : the thing about not using buffers is basically because we just went with what it's the getting started docs. Might it be worth it to note someting in the docs about implications of not using buffers? (Step 4)
https://cloud.google.com/trace/docs/setup/aspnetcore#configuring_the_client_library

I'll take a look at the docs tomorrow to see how best we can clarify.

@amanda-tarafa I can confirm that enabling the BufferOptions.TimedBuffer and setting a qpsSampleRate of 1 in the repro brings the speed back to how it is without Google Trace added.
Feel free to close the issue.

Thanks for confirming! You can probably set QPS higher than 1 now if you need to see more traces.
I'll close this one, but I've created GoogleCloudPlatform/dotnet-docs-samples#1266 to look into clarifying docs.
Thanks!

Thanks for confirming! You can probably set QPS higher than 1 now if you need to see more traces.

Yes I can indeed, reran my test with QPS:10 and QPS:100 without any noticeable performance degradation (test suite is generating ~800 req/s)


Add table with ClinGen/ GenCC entity scores

For manual curation add a table with detailed ClinGen/ GenCC entity scores and curations.
TODO:

[ ] find a source for this data
[ ] compute a summary table
[ ] consider adding this to the per gene subpages (e.g. issue #18)

Use this URL for ClinGen:
https://search.clinicalgenome.org/kb/gene-validity/download
Then perhaps parse the curation URLs in that file.
However, there are various SOPs that may be difficult to unify.


Switch to GoogleTest, GoogleMock, etc, try Travis CI

Closing this issue because all topics have been addressed.  Individual details below.
Switch to GoogleTest
Have not fully switched to GoogleTest, but it is included after https://github.com/allegroflare/allegro_flare/pull/160 was merged, and all tests now build and compile in CI and can be run locally.  Not all tests are passing.  It's expected to support botth GoogleTest and Boost Test, and not fully switch over to GoogleTest.
GoogleMock
GoogleMock was absorbed into GoogleTest.
Travis CI
TravisCI was added in https://github.com/allegroflare/allegro_flare/pull/151, and is working great.  Since the introduction in its first PR, it has been refined several times to support testing and building example programs.  Some examples:
https://github.com/allegroflare/allegro_flare/commit/b710a5dff9c9cf5e29f85b221f188a2474447eef#diff-354f30a63fb0907d4ad57269548329e3
https://github.com/allegroflare/allegro_flare/commit/9559cdbc2e5f6385e489cee71494ca5041f119fe#diff-354f30a63fb0907d4ad57269548329e3
https://github.com/allegroflare/allegro_flare/commit/682a0fae2ca7435446714a1a81deb8d4d73414d0#diff-354f30a63fb0907d4ad57269548329e3
https://github.com/allegroflare/allegro_flare/commit/bdc023df17d42669cc5312a7ba305525d56ad093#diff-354f30a63fb0907d4ad57269548329e3
https://github.com/allegroflare/allegro_flare/commit/7a5e2250e3ec62ba4c84d2a3a8aae11096258ab3#diff-354f30a63fb0907d4ad57269548329e3


Flapping values like Rated Power

When reconnecting, there are some values, like Rated Powerand Max Designed Power`, flapping.

Fixed with #130


In remote firefox some elements not painted when using ff - hardware acceleration

When I use on a remote Windows7 system Firefox 59.0 and in the Firefox settings the hardware acceleration is activated (default : yes), I don't see some elements like menus.
For example, clicking on the menu button in the upper right corner does not show the menu.
When I disable hardware acceleration in Firefox, everything works.
I'm using this version on openSUSE Tumbleweed + Leap 15.0:
This is FreeRDP version 2.0.0-dev3 (c5572b087)
Build configuration: BUILD_TESTING=OFF BUILTIN_CHANNELS=OFF HAVE_AIO_H=1 HAVE_EXECINFO_H=1 HAVE_FCNTL_H=1 HAVE_INTTYPES_H=1 HAVE_JOURNALD_H=TRUE HAVE_MATH_C99_LONG_DOUBLE=1 HAVE_POLL_H=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK=ON HAVE_PTHREAD_MUTEX_TIMEDLOCK_LIB=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK_SYMBOL= HAVE_SYSLOG_H=1 HAVE_SYS_EVENTFD_H=1 HAVE_SYS_FILIO_H= HAVE_SYS_MODEM_H= HAVE_SYS_SELECT_H=1 HAVE_SYS_SOCKIO_H= HAVE_SYS_STRTIO_H= HAVE_SYS_TIMERFD_H=1 HAVE_TM_GMTOFF=1 HAVE_UNISTD_H=1 HAVE_XI_TOUCH_CLASS=1 WITH_ALSA=ON WITH_CCACHE=ON WITH_CHANNELS=ON WITH_CLIENT=ON WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_CHANNELS=ON WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_COMMON=ON WITH_CLIENT_INTERFACE=OFF WITH_CUPS=ON WITH_DEBUG_ALL=OFF WITH_DEBUG_CAPABILITIES=OFF WITH_DEBUG_CERTIFICATE=OFF WITH_DEBUG_CHANNELS=OFF WITH_DEBUG_CLIPRDR=OFF WITH_DEBUG_DVC=OFF WITH_DEBUG_KBD=OFF WITH_DEBUG_LICENSE=OFF WITH_DEBUG_MUTEX=OFF WITH_DEBUG_NEGO=OFF WITH_DEBUG_NLA=OFF WITH_DEBUG_NTLM=OFF WITH_DEBUG_RAIL=OFF WITH_DEBUG_RDP=OFF WITH_DEBUG_RDPDR=OFF WITH_DEBUG_RDPEI=OFF WITH_DEBUG_REDIR=OFF WITH_DEBUG_RFX=OFF WITH_DEBUG_RINGBUFFER=OFF WITH_DEBUG_SCARD=OFF WITH_DEBUG_SND=OFF WITH_DEBUG_SVC=OFF WITH_DEBUG_SYMBOLS=OFF WITH_DEBUG_THREADS=OFF WITH_DEBUG_TIMEZONE=OFF WITH_DEBUG_TRANSPORT=OFF WITH_DEBUG_TSG=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_WND=OFF WITH_DEBUG_X11=OFF WITH_DEBUG_X11_CLIPRDR=OFF WITH_DEBUG_X11_LOCAL_MOVESIZE=OFF WITH_DEBUG_XV=OFF WITH_DIRECTFB=OFF WITH_EVENTFD_READ_WRITE=1 WITH_FFMPEG=ON WITH_GFX_H264=ON WITH_GPROF=OFF WITH_GSM=ON WITH_GSSAPI=OFF WITH_GSTREAMER_0_10=OFF WITH_GSTREAMER_1_0=ON WITH_ICU=OFF WITH_IPP=OFF WITH_JPEG=ON WITH_KRB5=ON WITH_LIBRARY_VERSIONING=ON WITH_LIBSYSTEMD=ON WITH_MACAUDIO=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO_AVAILABLE=0 WITH_MANPAGES=ON WITH_MBEDTLS=OFF WITH_OPENH264=OFF WITH_OPENSLES=OFF WITH_OPENSSL=ON WITH_OSS=OFF WITH_PAM=ON WITH_PCSC=ON WITH_PROFILER=OFF WITH_PULSE=ON WITH_SAMPLE=OFF WITH_SANITIZE_ADDRESS=OFF WITH_SANITIZE_ADDRESS_AVAILABLE=1 WITH_SANITIZE_MEMORY=OFF WITH_SANITIZE_MEMORY_AVAILABLE=1 WITH_SANITIZE_THREAD=OFF WITH_SANITIZE_THREAD_AVAILABLE=1 WITH_SERVER=ON WITH_SERVER_CHANNELS=ON WITH_SERVER_INTERFACE=ON WITH_SMARTCARD_INSPECT=ON WITH_SSE2=ON WITH_THIRD_PARTY=OFF WITH_VALGRIND_MEMCHECK=OFF WITH_VALGRIND_MEMCHECK_AVAILABLE=1 WITH_WAYLAND=OFF WITH_X11=ON WITH_X264=OFF WITH_XCURSOR=ON WITH_XDAMAGE=ON WITH_XEXT=ON WITH_XFIXES=ON WITH_XI=ON WITH_XINERAMA=ON WITH_XKBFILE=ON WITH_XRANDR=ON WITH_XRENDER=ON WITH_XSHM=ON WITH_XTEST=ON WITH_XV=ON WITH_ZLIB=ON
Build type:          Release
CFLAGS:               -fPIC -Wall -Wno-unused-result -Wno-unused-but-set-variable -Wno-deprecated-declarations -fvisibility=hidden -Wimplicit-function-declaration -Wredundant-decls
Compiler:            GNU, 7.3.1
Target architecture: x64
The remote system is a Windows7 Prof. 64 Bit with a NVIDIA Quadro NVS 290 graphics card.

@hendwolt your command line would be appreciated.
This can have 2 causes:

FreeRDP does not implement some ROP/codec/...
There is a server side issue (did you test with mstsc or other non freerdp based clients?)

I tested this with mstsc on Windows10 and there it works, no matter if hardware acceleration is used.
My command line:
xfreerdp /u:hendwolt /d:ZW /f +clipboard -wallpaper /v:<IP_ADDRESS> /gfx:rfx
I tested also without "/gfx:rfx", and with "/gdi:sw"; no changes.

@hendwolt does it work with /network:auto added to the command line? some win10 features require bandwidth measuerment enabled.

The target is Windows/ Prof., no Windows10. But the weird thing is, that I can't reproduce the issue today. And I did not change anything on the target site or the freerdp software.
So I can only guess, that it was a temporary server side issue.
Sorry for the noise.

@hendwolt then better add /rfx to your command line, /gfx is only supported by windows 8 and up. The /network:auto switch will help anyway.


GDScript atan2() and Vector.atan2() bug

I believe the Vector.atan2() function does not work as intended. Here is an example script that displays atan2 values for various unit vectors (anti-clockwise / trigonometric order) and expected values :
printt(Vector2(1,0), Vector2(1,0).atan2(), 0)
printt(Vector2(1,1), Vector2(1,1).atan2(), PI/4)
printt(Vector2(0,1), Vector2(0,1).atan2(), PI/2)
printt(Vector2(-1,1), Vector2(-1,1).atan2(), 3PI/4)
printt(Vector2(-1,0), Vector2(-1,0).atan2(), PI)
printt(Vector2(-1,-1), Vector2(-1,-1).atan2(), -3PI/4)
printt(Vector2(1,-1), Vector2(1,-1).atan2(), -PI/4)
Output :
1,0	1.570796	0
1,1	0.785398	0.785398
0,1	0	1.570796
-1,1	-0.785398	2.356194
-1,0	-1.570796	3.141593
-1,-1	-2.356194	-2.356194
1,-1	2.356194	-0.785398
Obviously, atan2() method calculates value for the inverse vector (0,1) instead of (1,0), (-1,1) instead of (1,-1), and so one.

I can confirm that in core/math/math_2d.cpp, Math::atan2 is called.
real_t Vector2::atan2() const {
return Math::atan2(x,y);
}
However, in core/math/math_funcs.cpp we have :
double Math::atan2(double p_y, double p_x) {
return ::atan2(p_y,p_x);
}
We have an inconsistency in the order of atan2() parameters. The GDScript documentation also suffer of this inconsistency where atan2(x,y) is defined instead of atan2(y,x).

I created a branch on my forked repo fixing this bug (https://github.com/StraToN/godot/tree/atan2fix), but it appears that atan2() function is used in multiple locations, showing either atan2(x, y) or atan2(y, x) usages. Maybe it would be nice to define the right syntax once and for all, and correct any impacted use elsewhere in the code and Godot demos. Thanks for your advices guys.

I'd be very interested in what's going on with atan2(). I had code using atan2() that I was very sure was correct but didn't work properly.

This is solved now, the problem was in Vector2.atan2() which is gone and replaced by Vector2.angle() atan2() is not affected


Does Peek Reference only search opened tabs?

Maybe I missed something obvious, but when I use Shift-F12 to peek reference, files in the workspace that are not currently open won't be searched. In other words, the result of shift-F12 is different every time based on what tabs I have opened. If I only have one tab open, I won't get any result, unless my function definition and function calls are in the same file.
Is this the intended behavior? I think it kind of defeats the purpose. Supposedly, Peek Reference should answer the question "I wonder which files imported this function?"
By the way, if I press Shift-F12 on a reference, it'll always be able to find its definition even if the definition is not open, but it doesn't work the other way around - if I presss Shift-F12 on a definition, it'll only find references that are inside open tabs.

I'm happy to provide sample code files if needed.

What language?

@roblourens JavaScript

@ZYinMD If you want references to look at all js files in your project, not just opened ones, you need to create a jsconfig


GAVO TAP address needs updating

Eventually will learn github enough to solve this, but for now, the GAVO admins told me this url has been removed server-side:
service = vo.dal.TAPService("https://dc.zah.uni-heidelberg.de/system/tap/run/tap"
and has to be updated in query_gaia to this:
service = vo.dal.TAPService("https://dc.zah.uni-heidelberg.de/tap"

Thanks for letting me know! :)


Can't link after unlink-ing once

Hi,
I created cla link for a repo once. Then deleted the git repo and recreated it under the same organization. Now, I can't create cla links anymore. How do I fix this issue?
Thanks.

@TamalSaha could you give me the name of the repository?

https://github.com/appscode/data is the repository. I see the name of the repository in the dropdown list. After I click the "Let's go" green button, I see the following animation and nothing happens. I have waited more 5 mins and then closed the tab

.

Could you try it again, please?

Thanks @KharitonOff. It worked this time. Did you fix any bug or was this some one-off manual thing?

@TamalSaha This was a special, exclusive fix only for you 😏
We will fix this bug too, but it will take some time... so it would be great if you unlink your repo in CLA assistant first before you delete and recreate it in GitHub 😄

:) Thanks for the info. I have another repo in similar situation. I was just testing to make sure it was really a bug. I am going to file another issue if the bug is not fixed by the time we are ready to make it public, again.


Broken in quick entry forms

SuperTable is broken in the quick entry form overlays.
I'm running:

Craft CMS 2.6.2780
Super Table 0.4.6

This should be fixed in the latest master - let me know if you have any further issues!


Change your organization connection to a different Azure AD

You have 100 or fewer users in your organization. If your organization has more than 100 users, contact Support for help with changing your Azure AD.

Does this apply to the source org, the target org, or both?

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

ID: 98f0caaf-2697-c506-339b-2dea64233e48
Version Independent ID: 7cd2ea02-2079-85d0-09e0-a90af59937d9
Content: Switch to another Azure Active Directory - Azure DevOps Services
Content Source: docs/organizations/accounts/change-azure-ad-connection.md
Product: devops
Technology: devops-accounts
GitHub Login: @chcomley
Microsoft Alias: chcomley

Hi @YodaDaCoda, thanks for your question. It applies to both - contact Support. Thank you!


Add support for custom messages on request completion/receive/failure

hapi-pino 9.2.0 and 9.3.0 added a few changes to the default output of "request completed" and "request error", that while useful for certain transports it can be redundant for others (the same information is already included). This pull request adds a way to customize these messages without changing the defaults:

customRequestStartMessage - to customize messages when enabled by logRequestStart
customRequestCompleteMessage - to customize messages when enabled by logRequestComplete
customRequestErrorMessage - to customize request error messages

These properties are based on equivalent properties existing in other implementations, specifically in pino-http, but the terminology is changed to fit better with existing terminology in this project.
This also addresses #162 without unnecessarily changing the existing defaults.

Coverage increased (+0.03%) to 99.073% when pulling e55d71745cf51e1fc36d3fc952d610a4484cc47b on jonathansamines:feature/custom-access-log-messages into 0f187f3c3c65dc8614b4beb521236a462d6aeaf8 on pinojs:master.


The Deploy templates fail as the JSON references /master/ and yet the path is changed to /main/

The Deploy templates fail as the JSON references /master/ and yet the path is changed to /main/

Thanks!!! I changed the references to master!


set ImageBackground style with height: '50%' backgroundImage got 25% height

Description
When I set the height of ImageBackground to 50%, it seems that both the Image and its container got 50% height, turn out the image got 25% but not 50% height to the ImageBackground container.
react-native 0.62.2 is 50%
react-native 0.67.2 is 25%
all the '%' style got the same problem
Version
0.67.2
Output of npx react-native info
nothing
Steps to reproduce
<View style={{ width: 400, height: 400, backgroundColor: '#333' }}>
  <ImageBackground
    style={[{ width: '100%', height: '50%', backgroundColor: '#aaa' }]}
    source={require("./images/bg.png")}>
    <Text style={{ color: '#fff' }}>contexts</Text>
  </ImageBackground>
</View>

Snack, code example, screenshot, or link to a repository
No response

The problem seems to be related to the fact that the Image component on ImageBackground implementation is using a flattenedStyle that depends on style, the same one that is used in the container View, so the container has a width of 50% and the nested image also has 50% so => 25 %

You should use imageStyle instead of style


feat(): add support for re-registering metrics

@odedino: Thank you for your contribution. I will look into it the next days.


Signal handled: Terminated when restarting docker

My environment is: ubuntu 16.04 + docker 17.06.2-ce
After starting a memchache container and then restarting docker (service docker restart), I noticed that the docker logs command return:
Signal handled: Terminated.
I suggest also to add close to the end of the Dockerfile, the following command:
RUN chmod +x /usr/local/bin/docker-entrypoint.sh

I'm not sure I see the correlation between A) docker logs -f exiting when the docker itself is restarted and B) "this file needs a chmod +x".
A) that is normal since it is the docker daemon process streaming the logs to your terminal
B) the file is already executable in git, so no chown necessary


Remove data transformation in cairo1 cheatcodes

Closes #1824
Checklist

[x] Relevant issue is linked
[ ] Docs updated/issue for docs created
[ ] Added relevant tests

Not sure if any tests/docs updates for this is necessary. Our docs indicated that only felt252 is supported as calldata anyways, changes introduced here are mostly internal.


CVE scanning: investigate scanning by digests (in context of multiarch images)

As a result of the investigation https://github.com/aquasecurity/trivy/issues/3571 was posted.
At the moment we don't have a way to scan multiarch images.


add save/load assembled binary functions

add save/load assembled binary functions, in order to use powerful machine to assemble large program.

Thanks!


The S3 location provided to save your query results is invalid

Describe the bug
I'm trying to use this project as a scaffold to a project that I'm building with c# and athena. I configured every step in the readme and was able to start. However, when I clicked in any covid19 query, I got the error bellow:
athenanetcore.webapp_1  | fail: Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware[1] athenanetcore.webapp_1  |       An unhandled exception has occurred while executing the request. athenanetcore.webapp_1  | Amazon.Athena.Model.InvalidRequestException: The S3 location provided to save your query results is invalid. Please check your S3 location is correct and is in the same region and try again. If you continue to see the issue, contact customer support for further assistance.
This error does not make sense, because I tested the bucket generated by CF stack in step 2 inside DBeaver and the results was returned without problems (picture1/picture2).
Bellow is my env configurations:
AWS_DEFAULT_REGION=us-east-1
AWS_ACCESS_KEY_ID=xxxxxxx
AWS_SECRET_ACCESS_KEY=yyyyyyyyyyyyyyy
S3_RESULT_BUCKET_NAME=s3://athena-results-netcore-s3bucket-cycw2c22srf5/athena/results/

Is there aditional steps I'm missing to make this project work?
Thanks!
Screenshots

The problem was in BaseRepository, line 34. The region was hardcoded and I have to change.


TC Meeting 2024-06-18

The OpenRail Technical Committee is holding a weekly meeting. The agenda is prepared in issues and the protocols are stored in the meetings folder.
Please add additional topics or any other comments by commenting on this issue.
Agenda

Project Proposal: NGE (#68)

License questions on dependencies
Input regarding OSRD collaboration
What else do we need to take a decision?

Onboarding RCM OSS
Criteria for stage 2 of the incubation process (#78)

Protocol is at #80


EmailFields do not have a regex attribute

Signed-off-by: Justin Lecher<EMAIL_ADDRESS>

Fixes https://github.com/krisfields/django-baker/issues/8


Fix scheduler peer state

Description

Fix scheduler peer state.

Related Issue

Motivation and Context

Screenshots (if appropriate)
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.

Codecov Report

Merging #1267 (4e66b0f) into main (85a3237) will decrease coverage by 0.19%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1267      +/-   ##
==========================================
- Coverage   46.08%   45.88%   -0.20%
==========================================
  Files         135      135
  Lines       11278    11279       +1
==========================================
- Hits         5197     5175      -22
- Misses       5516     5542      +26
+ Partials      565      562       -3

Flag
Coverage Δ

unittests
45.88% <100.00%> (-0.20%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

scheduler/resource/peer.go
76.66% <100.00%> (ø)

scheduler/scheduler/evaluator/evaluator_base.go
90.76% <100.00%> (+0.14%)
:arrow_up:

client/daemon/peer/peertask_piecetask_poller.go
30.43% <0.00%> (-16.67%)
:arrow_down:

client/daemon/peer/peertask_conductor.go
58.19% <0.00%> (ø)


Calculate a min/max/average value based on log data

Hello,
I'm trying to use grok_exporter to parse an application log that looks something like this:
2021-06-15 09:24:19,243 - INFO - SomethingSomething device AAAAA; Processing time is:4511us
2021-06-15 09:24:19,260 - INFO - SomethingSomething device BBBBB; Processing time is:3928us

I can count the lines and use "device" as a label and get the number of occurrences per device.
What I'd like to do now is parse the processing time (per device) and do a calculation of min/max/average processing time based on the data in the log file. I know I can export the raw data, but that would be more difficult (and a lot of data). Something like exporting a "Min processing time" metric, a "Max processing time" and an "Average processing time". The min/max/averages period could be controlled by the retention parameter.
I'd like to ask if such processing is possible in some way (using jinja perhaps?) with the stock grok exporter?
Thank you!

I've solved this issue by using the histogram data type.
Now I can get distribution in "time buckets" for my requests.
Sample config for the metric:
  -   buckets:
        - 0.5
        - 1
        - 2.5
        - 5
        - 10
        - 20
        - 50
        - 100
        - 200
        - 400
        help: Widget processing time distribution
        labels:
            host: myhost
            logfile: '{{.logfile}}'
            device: '{{.device}}'
        match: device (?<device>[^\s]+); Processing time is:(?<processing_time>[0-9\.]+)us
        name: widget_processing_time
        type: histogram
        value: '{{.processing_time}}'

And then I followed this tutorial to display the values on a heat map in grafana: https://grafana.com/blog/2020/06/23/how-to-visualize-prometheus-histograms-in-grafana/


Update/rules

Hey Edem,
Please have a look at the branch. I have done format changes and would like to incorporate for any new rules added in the repository.

Hey Karan it looks okay. You have the green light


[6.0][ClangImporter] Make sure the -resource-dir is checked before the -sdk, as done everywhere else in the compiler

Explanation: The frontend currently looks in -sdk for a C/C++ sysroot and -resource-dir for Swift modules, with the former implicitly set to / and the latter always explicitly passed in by swift-driver. However, a "full SDK" contains both C/C++ headers and Swift modules, so in that case and if -sdk is explicitly passed in, this ClangImporter was looking in the full SDK first and wrongly using those Swift module maps, rather than the ones in -resource-dir.
Scope: When does that actually happen? Suppose you have Swift 5.10 installed in the system and are trying to build Swift 6.0 from source. In that scenario, the CMake config explicitly passes -sdk / and the Swift 6 compiler wrongly uses the old Swift 5.10 C and C++ module maps and fails. This could also affect some SDK bundles, say if one linux distro triple's Swift modules are placed in the common SDK itself, while others are put in separate -resource-dir paths, since compiling SDK bundles passes in an explicit -sdk.
It does not affect simply building Swift packages with a local SwiftPM 6.0 while the implicit system SDK path of / has a system Swift 5.10 installed, as no explicit -sdk is passed to build those packages.
Issue: #74696
Original PRs: #74814 and #76119
Risk: Low, since this only affects the few listed scenarios where the -sdk flag is explicitly passed to the compiler
Testing: Passed all CI on trunk and my and others' testing locally. @compnerd did report an issue with his new Android SDK with an earlier version of this patch, so I'll wait on his further testing and approval before asking to merge this.
Reviewer: @egorzhdan

This might be a breaking change for certain setups

Such as?

I don't think we can land this kind of change in a bugfix release.

Ideally, we'd get it into Swift 6.0.0 also, once it's accepted into this branch.

This might be a breaking change for certain setups

Such as?

I think the answer is that we don't know, but past experience has shown that changing search paths can break configurations that we hadn't heard about.
This does look like the right set of changes to make, but I'm somewhat concerned that the issue @compnerd hit with https://github.com/swiftlang/swift/pull/74814 isn't known to be resolved.

I think the answer is that we don't know, but past experience has shown that changing search paths can break configurations that we hadn't heard about.

OK, I looked into it and Saleem added this first SDK lookup five years ago in 370aa9d9c, precisely to look for these module maps in full SDKs that are causing the problems now. I think this was to paper over the frontend not looking for Swift modules in full SDKs altogether, as I reported earlier this year in swiftlang/swift-driver#1562, and @artemcm's Frontend pull for that is how it should've been fixed instead.
I don't think most compilation scenarios set the -sdk flag, as I noted in the writeup about Risk, so the only question is whether this is worth fixing for the niche scenarios I listed where the current lookup order is broken for the potential unknown niche scenarios that depend on the current lookup order.

I'm somewhat concerned that the issue @compnerd hit with https://github.com/swiftlang/swift/pull/74814 isn't known to be resolved.

That was with an earlier version of this patch, but since this merged version was made available a couple weeks ago, their CI has been broken or they have been traveling, so we have not received any notice on this patch.
I suspect this patch works fine, but as I said above, I'm still waiting on them to verify.

@shahmishal, we're going on three weeks with no response here, can we get this in? I suspect the reason Saleem had an issue with an earlier version of this patch is that I made a mistake initially, which Egor then found and we corrected.
This has been in trunk for a month now without any reported issues and distros like Fedora have to pull it in for their 6.0 build.

@swift-ci please test

Ping @shahmishal or @DougGregor, this passed the 6.0 CI, just need a decision now.

Ping, this has been in trunk for four months now and in the downstream 6.0 release of Fedora for the last month: I think we have a pretty good body of evidence that it is unlikely to break anything.

Ping @DougGregor, with the next patch release coming up, can you make a decision on this? I consider this a small fix for more advanced build scenarios, but I leave it up to you release managers if it's worth backporting.


Add a comparison with autoflake, faq

Apparently it is impossible to write an md file by hand to satisfy prettier


[Feature]: ignoreProjects counterpart to selectProjects

🚀 Feature Proposal
Currently, selectProjects allows you to include projects by displayName. However, there is no to way exclude projects by displayName. So, adding ignoreProjects would allow you to exclude projects by displayName.
Motivation
In a large monorepo it is quite verbose to use selectProjects when you only need to exclude a small number of projects.
Example
--selectProjects A,B,D,E,F,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W,X,Z

versus
--ignoreProjects C,G,Y

Pitch
If there is an include there should also be an exclude.
Although I could probably get this to work with --projects and a glob, it would be nice to exclude them by displayName instead of path.
Also, as a bonus, they use the same number of characters. 😄

@eliw00d I'd like to implement this feature. do you think using selectProjects and ignoreProjects  together make sense?

I don't see why not!

https://github.com/facebook/jest/releases/tag/v28.0.0-alpha.8

Insane turnaround! Thanks @F3n67u and @SimenB !


page isn't loading up

ERROR in ./src/components/SellerRoute.js 26:36-44
export 'Redirect' (imported as 'Redirect') was not found in 'react-router-dom' (possible exports: AbortedDeferredError, Await, BrowserRouter,
Form, HashRouter, Link, MemoryRouter, NavLink, Navigate, NavigationType, Outlet, Route, Router, RouterProvider, Routes, ScrollRestoration, UNSAFE_DataRouterContext, UNSAFE_DataRouterStateContext, UNSAFE_FetchersContext, UNSAFE_LocationContext, UNSAFE_NavigationContext, UNSAFE_RouteContext, UNSAFE_ViewTransitionContext, UNSAFE_useRouteId, UNSAFE_useScrollRestoration, createBrowserRouter, createHashRouter, createMemoryRouter, createPath, createRoutesFromChildren, createRoutesFromElements, createSearchParams, defer, generatePath, isRouteErrorResponse, json, matchPath, matchRoutes, parsePath, redirect, redirectDocument, renderMatches,
resolvePath, unstable_HistoryRouter, unstable_usePrompt, unstable_useViewTransitionState, useActionData, useAsyncError, useAsyncValue, useBeforeUnload, useBlocker, useFetcher, useFetchers, useFormAction, useHref,
useInRouterContext, useLinkClickHandler, useLoaderData, useLocation, useMatch, useMatches, useNavigate, useNavigation, useNavigationType, useOutlet, useOutletContext, useParams, useResolvedPath, useRevalidator, useRouteError, useRouteLoaderData, useRoutes, useSearchParams, useSubmit)
webpack compiled with 4 errors
m getting this error please assign me this issue so i can fix this and make your repo better

Thank you for assigning me this task I'll finish it by the week


security_tenant and embed parameteres are mutually exclusive

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Hi
In my application, I embed Kibana dashboards and other pages in iframes.
In order to select tenant, we add security_tenant parameter to the url (before the # anchor)
To embed the Kibana page (remove the upper and leftside menus), we use embed=true (after the # anchor)
Each of those parameters works separately, but when we put them together the embed parameter is not working
Here is a sample of url in iframe
https://kibana_host:443/app/opendistro_kibana_reports?security_tenant=my-tenant#/?embed=true
This issue is submitted by @WassimDhib
https://github.com/opendistro-for-elasticsearch/kibana-reports/issues/279

we dont support iframe for reporting, could you please describe your usecase and reopen this issue. thanks


Pokemons keep vanishing?

Expected Behavior
Capture of a Pokemon
Actual Behavior
[#] A Wild Zubat appeared! [CP 10]
[x] Using Pokeball...
[x] Oh no! Zubat vanished! :(
all pokemons seem to vanish :(
Steps to Reproduce
Run the program.
Other Information
OS: OSX 10.11.5
Git Commit: acc2d4f

There is a chance you are soft banned dont know for sure

/softbanned.

@mauriez Please do not use the Pokemon GO App while the bot is running with the same account. This gets you (soft)banned very very fast. Stop the bot, wait 10-20 minutes. Open the Mobile App and try to spin a PokeStop, if it is working (returin Items) then your softban most probably was lifted.
Then you can proceed by, this is what I do

Logout of the Mobile App
(This is optional: If your farming spot is not the same as your physical location, then you should probably wait some time, to prevent the discrepency between locations to be some what alerting)
Start the Bot

@mauriez you can use the bot with -m farm. It will try to spin a PokeStop and it will detect if you are soft banned or not.

Yeah.. softbanning seems to be it. Didnt know about it. Hope it clears me soon :) Thanks!


Citation manager stops working when copying cells in a new notebook

Description
I am drafting my final dissertation using Jupyter Notebooks and Jupyter Book to "compile" it into LaTeX. jupyterlab-citation-manager is a godsend, but unfortunately today I encountered some minor issues that gave me some pretty decent sized headaches.
When I moved some paragraphs (containing citations) that I had written in one notebook to another one, the extension stops working in that notebook. When I alt + c to insert a citation, the search bar appears, but nothing is inserted. It took me the cell metadata inspector to find out what happened: while the cells metadata are copied over, the notebook metadata is not.
Reproduce
EDIT: the error does not occur when copying the content of the cell (like with ctrl+c ctrl+v), but only when copying over multiple cells with Jupyter default shortcuts C V or X

In notebook A, insert some citations (either with alt + c or the GUI) in a markdown cell. Save the file.
Create notebook B and copy over the cell containing the citations from notebook A.
Attempt to insert citations in notebook B

Context

Operating System and version: macOS 11.6
Browser and version: Brave Browser <IP_ADDRESS> (Chromium)
JupyterLab version: 3.2.1

Possible Suggestions?

When reloading with alt + u check whether metadata across cell and notebook match

I was not able to reproduce the bug as described (by copying between notebooks, or cutting and pasting to another notebook). I was able to break it by copying a cell and pasting it again in the same notebook, which is a simpler case; I wonder if it could be that you tried to paste a cell copied from notebook A twice into the notebook B?
In my case I get the following error in the console in developer tools:

This is relatively simple to fix as we just need to re-assign the citation ID if it is already taken. I didn't find a paste-specific event for cells, but it probably should be triggered when catching the exception shown above, so that the manual edits give the same result.
If it happens again (or if you have time to try to reproduce it), would you be able to check if there is any error in the console, please? A GIF demonstration on two clean notebooks could also help, maybe I am just missing some less obvious step that leads to the occurrence of this bug.

Hi Mike, sorry if I could not reply to the conversation here and on #36 - I will be more active after the 15th, I need to finish my dissertation


File list failing to display after Atom 1.17 update.

I just updated to Atom 1.17.0 x64 and now git tree view is failing to open.
Error
tree-view-git-modified-view.coffee:63
Uncaught (in promise) TypeError: Cannot read property 'style' of null
at .atom/packages/tree-view-git-modified/lib/tree-view-git-modified-view.coffee:63:64
Here is the code

Atom Packages
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Maybe this has something to do with Docks?

patched

Excellent. I've updated and everything is working with Atom 1.19-beta2

happy for it
;-)


Let nativeDotProduct iterate over all query fields if no field is given as argument

https://github.com/vespa-engine/vespa/pull/6195

available in vespa 6.248.31

That's a really good feature you have added. I have a question on how internally nativeDotProduct(field) works, basically in one of the experiments, we found this.
We wanted to boost (add score) on some query term matching in some field.
Basically, we had 40 fields which could be used for ranking and based on some model, dynamically per query some tuples of (<field>,<term>,<weight>) used to generate (based on raw query) saying, if for a document, <term> is found in <field>, then add <weight> in relevance score for that document.
So, we wrote
matches(title,1)*query(title_1)+
matches(title,2)*query(title_2)+
….
matches(title,20)*query(title_20)+
matches(text,1)*query(text_1)+
matches(text,2)*query(text_2)+
matches(text,3)*query(text_3)+
....
matches(text,20)*query(text_20)+
……
……

where  `` is passed as query features.
so we had 800 matches feature in ranking expression (assuming we won't have more than 20 terms in the query), so by following
https://github.com/vespa-engine/vespa/blob/b8e9cbb6cdad643d937de3ffbe700fa8114a8a30/searchlib/src/vespa/searchlib/features/matchesfeature.cpp
It can be concluded that for a document, all 800 features are evaluated, (let's call it experiment 1)
Now, I came to know that nativeDotProduct(field) does the same thing, and now tried out with ranking expression.
nativeDotProduct(title)+nativeDotProduct(text)+... <same way for all 40 fields>
now, referring to https://github.com/vespa-engine/vespa/blob/f562d35d3636cfbb6fd6d9caeb94d97dcdfc0f8e/searchlib/src/vespa/searchlib/features/native_dot_product_feature.cpp
[for nativeDotProduct(field)], though in this ranking expression only 40 features are evaluated, each feature takes all 20 query terms in consideration, so in getTermFieldHandle() is apparently called 800 times here also.   (let's call it experiment 2)
To my surprise, I find experiment 2 way faster performant than experiment 1.
Basically, it looks like somehow same thing happening internally, it's just that nativeDotProduct(field) kind of masks matches(field,1)*query(field_1)+matches(field,2)*query(field_2)+ ... + matches(field,20)*query(field_20). Then why I find very huge difference? What optimizations are done for nativeDotProduct(field).
It's to note that I was using double type numbers in experiment 1, while I am restricted to use integer type numbers in experiment 2. But I don't think it could be this much difference maker. (getting 10 times better performance)

Think of the ranking expression as a function that combines features. The function itself is compiled to machine code and is very fast. Each feature used in the function is calculated by separate components called feature executors. The speed increase is due to fewer features being used, resulting in fewer feature executors being run. Also, getTermFieldHandle is called during setup and not per hit, so this should not impact performance when you have a reasonable amount of documents.

Yes, I do understand that getTermFieldHandle() is called only at setup time. So, we can say that each termData has context saved which fields are searched by term for that query, which is found by <term_data>->lookupField(uint32_t fieldId).
Thanks for the clarification.

Yes, each term can search multiple fields. Match information used for ranking is available separately for each term-field combination. The lookupField(fieldId) is a convenience to avoid having to inspect all fields for a term when you already know which field you are interested in.

@havardpe  how to call this new rolled out feature nativeDotProduct.
expression :  nativeDotProduct is failing

6.248 isn't released yet. Unless you built yourself you don't have it. It will be released on Monday.

@bratseth , has the new version released with this feature?

Yes
https://github.com/vespa-engine/vespa/releases


Developer/contributing documentation?

Seems there is a lot of steps to build, minify and otherwise be able to reproduce the same files that exists here in this repository.
In order to contribute, it'd be great to be able to run these steps locally too. Currently I'm trying to figure out why the <select> element is not firing change events and was gonna use this websites examples as a base, but because I don't know/understand how this project is built, I cannot use it...

https://github.com/thomas-lowry/figma-plugin-ds/pull/9/commits/ad7750e253b5e6c2cca09eb0656a17d64c32c91a
Check this pull request, it fixes the  issue.
Still not sure how to build it though.

Thanks a lot @jackiecorn, will give that a try! Found another issue that is now blocked by this one https://github.com/thomas-lowry/figma-plugin-ds/issues/10

Fixed in the latest release which is now available as an npm package with a Gulp 4 build.
Also please check out Figma Plugin Boilerplate which comes pre-installed with this library. As a build process as well and is steup with CSS Purge to remove most unused styles to keep it light.


xorm/router logs will be not rotated

Description
This
[log]
MODE             = file,file-servicesmirror
MAX_DAYS         = 15
LEVEL            = Error
ROOT_PATH        = /var/lib/gitea/log
ROUTER           = file
STACKTRACE_LEVEL = Error
XORM             = file

[log.file.xorm]
FILE_NAME        = xorm.log
STACKTRACE_LEVEL = Error

[log.file-servicesmirror]
MODE       = file
FILE_NAME  = servicesmirror-trace.log
LEVEL      = Error
EXPRESSION = services/mirror

is my log configuration. The xorm/router logs were created on 27.02.2022 and are not rotated. But this works for the other logs.
Gitea Version
1.16.4
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots

Git Version
2.25.1
Operating System
Ubuntu 20.04.4
How are you running Gitea?
Self hosted
Database
PostgreSQL

Did you try adding the MAX_DAYS to the log.file.xorm ini section?
...

[log.file.xorm]
FILE_NAME        = xorm.log
STACKTRACE_LEVEL = Error
MAX_DAYS         = 15

Did you try adding the MAX_DAYS to the log.file.xorm ini section?
...

[log.file.xorm]
FILE_NAME        = xorm.log
STACKTRACE_LEVEL = Error
MAX_DAYS         = 15

No, cause this is defined in
[log]
MAX_DAYS         = 15

like here https://docs.gitea.io/en-us/logging-configuration/#file-mode and this will be used by [log.file-servicesmirror]. Can you see in the screenshot.
But now I added it and I will see what would happen.
And what should I add for router.log? This is defined in [log] and should be rotated every 15 days too.

With the "new" config parameter it works.


chore: add client extensions examples to existing Prisma Client sections

Describe this PR
Add Prisma Client extension examples to existing workarounds:

[ ] Excluding fields
[x] Computed fields
[x] Custom validation
[x] Custom models methods
[x] exists function
[x] JSON field type validation
[x] Middleware migration to Client extensions:

[ ] soft delete (Update when support for nesting is added)
[x] query logging
[ ] session data (RLS?)

[ ] RLS
[x] Move PCE a level above Middleware?
[x] Set up redirects for old pages

Examples marked with ~~ are currently out of scope for v1.
Alternative idea:
Convert the Prisma Client extensions GH repo to resemble the Prisma Examples repo — in terms of structure and purpose.
The repository can serve as a reference + dump for PCE ideas + contributions from other users.
Create a page to aggregate the list of all extensions in the repository — name and descriptions

What is the difference between an "example" and a "sample"?

Difference between "sample" and "example"

I'm still conflicted on what terminology to stick to. The docs on Middleware uses "sample", however, it doesn't feel as natural. I'm open to suggestions and don't have any particular preferences.
The "Extensions Examples" page lists examples listed in the prisma-client-extensions repo, and "EXT sample" shows how to implement one. I'm also unsure whether we should provide the implementation of samples or list examples in the repo. The former might not be a great approach if we intend to add more examples as it might get too big.

We do not consider "Custom validation" and "Computed fields" solved, so their feature request issues are still open. They ask for a top level feature, not the building blocks and then a "sample/example" that is marked as "do not use in production". https://www.prisma.io/docs/concepts/components/prisma-client/custom-validation and https://www.prisma.io/docs/concepts/components/prisma-client/computed-fields were clear about that, https://docs-git-client-extensions-prisma.vercel.app/concepts/components/prisma-client/client-extensions/custom-validation and https://docs-git-client-extensions-prisma.vercel.app/concepts/components/prisma-client/client-extensions/computed-fields are not.

It's not super clear to me why we include the sub-pages with the examples. Aren't they just the same examples from the blog post?

When initially working on the content, the docs were a good place to cross-post the examples created in the blog post. We can aggregate the content in a table instead of creating a separate page for each example and duplicating what's in the blog post + PCE examples repo.
I'll also revert the changes made to the pages on middleware and have them in a separate PR.

I've made a few updates to the PR:

Restored the custom validation and computed fields file. I've linked to Prisma Client extensions in the "Going further" section
Restored the redirects file (no redirects needed as I've restored the file)
Deleted all files with extension examples. We're only listing and linking to the Prisma Client extensions repo examples
Restored the model used in the logging middleware example (will be taken care of in a separate PR)

/vercel/path0/content/800-data-platform/400-members/100-add.mdx: Expected corresponding JSX closing tag for <Admonition>. (34:0)
  32 |
{`From the `}{`Role`}{` drop-down menu, select a `}{`role`}{` for the new team member.`}

  33 | <Admonition>
> 34 |

     | ^
  35 |

  36 |
{`Note`}

  37 |
{`On the `}{`Free plan`}{`, you can only assign the `}{`Admin`}{` role.`}

{`

@ruheni


Inspec gem is constantly reinstalled if version is specified

Cookbook version
3.0.0
Chef-client version
12.9.29
Platform Details
RHEL 7.3
Scenario:
Install particular version of inspec gem
Steps to Reproduce:
Add attribute inspec_version to the configuration, for instance:
"inspec_version": "1.17.0"
Expected Result:
Gem is re-installed if not installed or has another version
Actual Result:
Gem is reinstalledd each chef-client run, even if it is already the configured version. The resource has no check for the installed version and always remove installed and install ne gem if version is specified.
Here is the output:
Recipe: audit::inspec

inspec_gem[inspec] action install[2017-05-02T12:45:04+02:00] INFO: Processing inspec_gem[inspec] action install (audit::inspec line 20)

chef_gem[remove all inspec versions] action remove[2017-05-02T12:45:04+02:00] INFO: Processing chef_gem[remove all inspec versions] action remove (/var/chef/cache/cookbooks/audit/resources/inspec_gem.rb line 41)
[2017-05-02T12:45:05+02:00] INFO: chef_gem[remove all inspec versions] removed

remove package inspec

chef_gem[remove all train versions] action remove[2017-05-02T12:45:05+02:00] INFO: Processing chef_gem[remove all train versions] action remove (/var/chef/cache/cookbooks/audit/resources/inspec_gem.rb line 46)
[2017-05-02T12:45:05+02:00] INFO: chef_gem[remove all train versions] removed

remove package train

uninstall all inspec and train gem versions

chef_gem[inspec] action install[2017-05-02T12:45:05+02:00] INFO: Processing chef_gem[inspec] action install (/var/chef/cache/cookbooks/audit/resources/inspec_gem.rb line 32)
ERROR:  SSL verification error at depth 0: self signed certificate (18)
ERROR:  Certificate /C=US/O=YouCorp/OU=Operations/CN=clrv0000000070.ic.ing.net is not trusted
[2017-05-02T12:45:07+02:00] INFO: chef_gem[inspec] installed inspec at 1.17.0

install version 1.17.0 of package inspec

install requested inspec version 1.17.0

chef_gem[remove all inspec versions] action remove[2017-05-02T12:45:07+02:00] INFO: Processing chef_gem[remove all inspec versions] action remove (/var/chef/cache/cookbooks/audit/resources/inspec_gem.rb line 41)
[2017-05-02T12:45:08+02:00] INFO: chef_gem[remove all inspec versions] removed

remove package inspec

chef_gem[remove all train versions] action remove[2017-05-02T12:45:08+02:00] INFO: Processing chef_gem[remove all train versions] action remove (/var/chef/cache/cookbooks/audit/resources/inspec_gem.rb line 46)
[2017-05-02T12:45:09+02:00] INFO: chef_gem[remove all train versions] removed

remove package train

chef_gem[inspec] action install[2017-05-02T12:45:09+02:00] INFO: Processing chef_gem[inspec] action install (/var/chef/cache/cookbooks/audit/resources/inspec_gem.rb line 32)
[2017-05-02T12:45:10+02:00] INFO: chef_gem[inspec] installed inspec at 1.17.0

install version 1.17.0 of package inspec

[2017-05-02T12:45:10+02:00] INFO: loading handler from /var/chef/cache/cookbooks/audit/files/default/handler/audit_report

@voroniys The expected behavior is that InSpec is not installed if it is the same version, right?

Yes, if the configured version already installed it should do nothing. Now it removing it and re-installing each chef-client run.


Fix broken cluster API link

NONE

/assign @simonswine @MattiasGees

@JoshVanL thanks for finding and fixing!
Can we make sure that we only assign issue to exactly one person?
/unassign @MattiasGees
/lgtm
/approve


Upgrade faraday to 0.14.0

[x] Upgrade faraday to version 0.14.0
[x] Fix warning unexpected middleware set after the adapter

Coverage remained the same at 100.0% when pulling c2165e5ea8519275b893be34b89abf5c48944202 on jdaviderb:update-faraday into ceb63460b8b45b7e00766ae3a4c3e361d76c6ffc on emorikawa:master.


Cloud Push, recommend approach / examples

What's the recommended cloud messaging approach for Tabris.
CloudPush (http://developer.eclipsesource.com/tabris/docs/2.0/working/client-services/cloud-push/)
Seems fairly involved, requiring Xcode to set up an "application delegate"
And firebase cloud messaging support was not clear (platforms, Tabris version)
In the current day, what is the recommended approach? And is there a clear example or tutorial?

For Android we have developed the plugin https://github.com/eclipsesource/tabris-plugin-firebase. It allows you to use firebase cloud messaging with Tabris.js (2.x). For iOS there are several cordova plugins available that support the Push Message mechanics.

Ok, great to know. so the firebase plugin wouldn't work for iOS? can you suggest the list of compatible cordova plugins please?

This plugin works with iOS https://github.com/eclipsesource/phonegap-plugin-push. However it has been modified and only supports APNS. The GCM part has been removed. JS API remained unchanged.

if you use Pushwoosh, I updated their cordova plugin to work with tabris. It seems to work well on iOS and Android although I have not tested some of their advanced features (location tracking etc)
https://github.com/spatialdatalogic/pushwoosh-phonegap-plugin

@bFlood Would you happen to have an example config.xml that shows the plugin being loaded, and how to call it in Javascript? The docs on pushwoosh show onDeviceReady, but as I understand it, we don't need that in Tabris-js. Thanks in advance

@camstuart That is correct. You don't have to wait for the device ready callback. The plugin is available instantly.

plugin.xml
<plugin name="pushwoosh-cordova-plugin" spec="https://github.com/spatialdatalogic/pushwoosh-phonegap-plugin" />

and like @mpost mentioned above, plugins are available immediately, so you can call this from anywhere

Server.prototype.initPushwoosh = function() {
    try {

        var pushNotification = cordova.require( 'pushwoosh-cordova-plugin.PushNotification' );

        var self = this;

        if (util.isAndroid()) {

            //============
            //Android

            //set push notifications handler
            document.addEventListener('push-notification', function (event) {
                var title = event.notification.title;
                var userData = event.notification.userdata;

                if (typeof(userData) != "undefined") {
                    var module = util.safeGet(userData, "module", "");
                    var type = util.safeGet(userData, "type", "");
                    var iid = util.safeGet(userData, "iid", "");
                    self.processPushNotification(module, type, iid);
                }
            });

            //initialize Pushwoosh with projectid: "GOOGLE_PROJECT_NUMBER", pw_appid : "PUSHWOOSH_APP_ID". This will trigger all pending push notifications on start.
            pushNotification.onDeviceReady(
                {projectid: "1234567890", pw_appid: "12345-67890"}
            );

            //register for pushes
            //fast Google Pixel device caused issue here, can functions get executed out of order?
            //delay the registerDevice call to fix the issue
            window.setTimeout(function() {
                pushNotification.registerDevice(
                    function (status) {
                        util.log(status);
                        var pushToken = status.pushToken;

                        util.setItem("_pndt", pushToken);
                    },
                    function (status) {
                        util.log(['failed to register ', status]);
                    }
                );
            }, 200);

        } else {

            //============
            //iOS

            //set push notification callback before we initialize the plugin
            document.addEventListener('push-notification', function (event) {
                //get the notification payload
                var notification = event.notification;

                //TODO - figure out what comes through iOS
                util.log(notification);

            });

            //initialize the plugin
            pushNotification.onDeviceReady({pw_appid: "12345-67890"});

            //register for pushes
            pushNotification.registerDevice(
                function (status) {
                    var deviceToken = status['pushToken'];
                    util.log('registerDevice: ' + deviceToken);
                    util.setItem("_pndt", deviceToken);
                },
                function (status) {
                    util.log(['failed to register ', status]);
                }
            );
        }

    } catch (e) {
        util.log("PUSH NOTIFICATIONS failed to initialize");
    }
};

Fantastic @bFlood thanks for your great example, really appreciated. I have it working now.
In my case I removed the outer callback
Server.prototype.initPushwoosh = function() {

because Server was not defined
And the event notification response data on iOS looks like this:
{
   foreground:true,
   onStart:false,
   ios:{
      aps:{
         alert:"This is the push message text",
         sound:"default",
         badge:0
      },
      p:"7"
   },
   message:"This is the push message text"
}

Mostly options selected in the push woosh UI

great, glad it helped. Pushwoosh is extra money but it does make working with all push on all platforms a little easier IMO. cheers

Closing this as resolved. Please reopen if you have any more issues.


Add an option to use UTC time in replying quotes

There is already an option that allows using UTC time in headers to avoid metadata leaking, but the time shown in replying quotes are still in local timezone. We should also add an option to change this behavior.

I'd rather the same option just controlled both unless there's a particular use case for wanting one and not the other.


[WIP]Feature: Deep scope analysis support

This is an internal support of Deep Scope Analysis (improve tree shaking).
This PR is working in progress. Even after it's merged, the improved tree shaking feature will not be enabled by default, here's an example for how to enable and test it:
example
You should enable the plugin in webpack.config.js and set optimization.usedExports to true.
Also, you can compare the results of the plugin:

Plugin enabled
Plugin disabled

You will find that more variable will be commented /* unused harmony export xxx */ in the bundle file, which will help improve tree-shaking.
There still some problems of the plugin in production mode, that's why it's still WIP.

#7585 solved


Remove "new NotImplementedExceptions" from IO code.

Sites found by tooling:
[System.Private.CoreLib] System.IO.Stream.SyncStream::BeginRead(byte[], int, int, AsyncCallback, object)
[System.Private.CoreLib] System.IO.Stream.SyncStream::BeginWrite(byte[], int, int, AsyncCallback, object)

How to remove:

Include the following in your .csproj file:

    <Compile Include="..\..\Common\src\System\NotImplemented.cs">
      <Link>System\NotImplemented.cs</Link>
    </Compile>

Options for removing “throw new NotImplementedException()”:
If you can implement the missing functionality now:
Do so.
If this is functionality that’s not supported on a particular framework or OS, replace with
throw new PlatformNotSupportedException(SR.xxx);
If this is an api that needs to throw NotImplemented for backward compat reasons, replace with:
throw NotImplemented.ByDesign;
or
throw NotImplemented.ByDesignWithMessage(SR.xxx);
If this is a virtual api method that’s only intended to work when overridden by another class, replace with:
throw new NotSupportedException(SR.xxx);
(Unless required for backward compat, refrain from throwing NotImplemented out of these.)
If this is a virtual non-api method that’s only intended to work when overridden by another class, replace with:
An abstract method.
If this is a compiler or toolchain intrinsic that only needs a body to make C# happy:
throw new NotSupportedException();
If this is true undone work and you just can’t fix it now, replace with:
throw NotImplemented.ActiveIssue(“https://github.com/dotnet/corert/issues/xxx”);
The string will not leak out via Exception.Message. The string is for tooling and human readers only. In the past, we’ve usually added an inline comment but the trouble with those is that IL-based tooling can’t read comments.

Now tracked as TFS 451317


Make quantity optional in CheckoutLinesUpdate mutation

Make quantity optional in CheckoutLinesUpdate mutation.
Copy of PR: https://github.com/saleor/saleor/pull/9418

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-6365 Allow updating only custom price

Task linked: SALEOR-6089 Custom prices when adding items to checkout


Chromatic; Change diffThreshold to 0.2

Who is this for?
Chromatic debugging
What is it doing for them?
Default threshold is 0.063, we were recommended trying something between 0.1 and 0.3 so here I go!

Alright, it stills detects a few pixels changing positions, so I'd be willing to merge that in and see if it helps our "1px in image" issue.


Test: Allow tests to run in parallel.

It's worth noting that this doesn't actually work. The tests fail. This
has highlighted a number of weird quirks in our controller when one
test cleans up at just the wrong time. Containers go missing, 404s go
flying, calamity ensues.
I think these problems will be addressed by making harvesting a
background job, so we can leave it here and maybe switch to this mode as
the default when it's stable.
Here's an example of the errors we might get running tests in parallel:
[2018-04-18 18:53:14,358] ERROR in app: Exception on /executions/bd30ac06-4339-11e8-8805-6bbc9a67228c/logs [GET]
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/docker/api/client.py", line 225, in _raise_for_status
    response.raise_for_status()
  File "/usr/local/lib/python3.6/site-packages/requests/models.py", line 935, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http+docker://localhost/v1.35/containers/f3819193e947894fa0e54a202ba9ac6ec45c6ee0cffc55a3fab25e4b15052c0b/json

No reason not to approve, but let's discuss changes to harvesting when you're back.

OK, cool, I’ll hold off doing anything until after we discuss.


chore: release master

:robot: I have created a release beep boop
@allaround/all-components: 1.9.1
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/input bumped from ^2.9.0 to ^2.9.1
@allaround/icons bumped from ^1.1.0 to ^1.2.0
@allaround/hooks bumped from ^1.1.0 to ^1.1.1
@allaround/textarea bumped from ^1.0.8 to ^1.0.9
@allaround/tags bumped from ^1.0.9 to ^1.0.10
@allaround/dropdown bumped from ^1.0.9 to ^1.0.10
@allaround/select bumped from ^1.0.9 to ^1.0.10
@allaround/upload bumped from ^1.0.9 to ^1.0.10
@allaround/scheduler bumped from ^1.0.9 to ^1.0.10
@allaround/video bumped from ^1.0.10 to ^1.0.11
@allaround/image bumped from ^1.0.9 to ^1.0.10
@allaround/checkbox bumped from ^1.0.9 to ^1.0.10
@allaround/tooltip bumped from ^1.1.0 to ^1.1.1
@allaround/notification bumped from ^1.0.8 to ^1.0.9

@allaround/checkbox: 1.0.10
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/tooltip bumped from ^1.1.0 to ^1.1.1
@allaround/input bumped from ^2.9.0 to ^2.9.1

@allaround/dropdown: 1.0.10
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/icons bumped from ^1.1.0 to ^1.2.0
@allaround/tooltip bumped from ^1.1.0 to ^1.1.1

@allaround/hooks: 1.1.1
Dependencies

The following workspace dependencies were updated

devDependencies

@allaround/notification bumped from ^1.0.8 to ^1.0.9

icons: 1.2.0
1.2.0 (2023-09-03)
Features

add newtab icon (#98) (efc7dc9)

@allaround/image: 1.0.10
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/upload bumped from ^1.0.9 to ^1.0.10
@allaround/tooltip bumped from ^1.1.0 to ^1.1.1
@allaround/icons bumped from ^1.1.0 to ^1.2.0

@allaround/input: 2.9.1
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/hooks bumped from ^1.1.0 to ^1.1.1
@allaround/tooltip bumped from ^1.1.0 to ^1.1.1

@allaround/notification: 1.0.9
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/icons bumped from ^1.1.0 to ^1.2.0

@allaround/scheduler: 1.0.10
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/hooks bumped from ^1.1.0 to ^1.1.1
@allaround/select bumped from ^1.0.9 to ^1.0.10
@allaround/icons bumped from ^1.1.0 to ^1.2.0

@allaround/select: 1.0.10
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/icons bumped from ^1.1.0 to ^1.2.0
@allaround/hooks bumped from ^1.1.0 to ^1.1.1

@allaround/tags: 1.0.10
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/hooks bumped from ^1.1.0 to ^1.1.1
@allaround/input bumped from ^2.9.0 to ^2.9.1
@allaround/icons bumped from ^1.1.0 to ^1.2.0
@allaround/textarea bumped from ^1.0.8 to ^1.0.9

@allaround/textarea: 1.0.9
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/icons bumped from ^1.1.0 to ^1.2.0

@allaround/tooltip: 1.1.1
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/hooks bumped from ^1.1.0 to ^1.1.1

@allaround/upload: 1.0.10
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/hooks bumped from ^1.1.0 to ^1.1.1
@allaround/input bumped from ^2.9.0 to ^2.9.1
@allaround/icons bumped from ^1.1.0 to ^1.2.0

@allaround/video: 1.0.11
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/icons bumped from ^1.1.0 to ^1.2.0
@allaround/hooks bumped from ^1.1.0 to ^1.1.1
@allaround/tooltip bumped from ^1.1.0 to ^1.1.1
@allaround/upload bumped from ^1.0.9 to ^1.0.10

allaround-components: 2.12.0
2.12.0 (2023-09-03)
Features

add newtab icon (#98) (efc7dc9)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/allaround-components-v2.12.0 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/all-components-v1.9.1 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/input-v2.9.1 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/icons-v1.2.0 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/hooks-v1.1.1 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/textarea-v1.0.9 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/tags-v1.0.10 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/dropdown-v1.0.10 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/select-v1.0.10 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/upload-v1.0.10 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/scheduler-v1.0.10 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/video-v1.0.11 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/image-v1.0.10 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/checkbox-v1.0.10 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/tooltip-v1.1.1 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/notification-v1.0.9 :sunflower: