fix: use tooltip on money request header avatar

Details

This PR adds tooltips to the payee and the payer in the MoneyRequestHeader component.
Fixed Issues

$ https://github.com/Expensify/App/issues/19341
PROPOSAL: https://github.com/Expensify/App/issues/19341#issuecomment-1555922209
Tests

Open the App and by clicking on the + icon in the LHN, send money to any user.
In the chat that opens with the user after sending money, click on the IOU preview message.
This opens the IOU transaction report page.

Verify that the tooltip shows in the header by moving the cursor over the sender and receiver avatars + names.

[x] Verify that no errors appear in the JS console

Offline tests

N/A
QA Steps

Open the App and by clicking on the + icon in the LHN, send money to any user.
In the chat that opens with the user after sending money, click on the IOU preview message.
This opens the IOU transaction report page.

Verify that the tooltip shows in the header by moving the cursor over the sender and receiver avatars + names.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

https://github.com/Expensify/App/assets/30054992/3667df8a-795e-47c4-a269-d2fa3ff29d15

Mobile Web - Chrome

Mobile Web - Safari

Desktop

https://github.com/Expensify/App/assets/30054992/d5daaf0e-1f95-49f6-a42e-d855381d649f

iOS

Android

@allroundexperts Looks like we don't show any tooltip when hovered over Workspace name in chat header. So, should we do the same for workspace in Money Request Header as well?
I think one way will be to show email for individual and nothing for Workspace. What is your opinion on this @youssef-lr?

Yeah I don't think we need to show a tooltip for the workspace, as it'll basically be the same as the display name.

@allroundexperts There are still multiple issues.

First we decided not to show anything if its workspace (Please mimic chat header of workspace)

https://github.com/Expensify/App/assets/25876548/b9d823b1-4eb3-42c1-a093-47ec696a48c0

Second please do consider subscript avatar. For avatar with subscript avatar (Workspace) we are showing two different tooltips. I don't think we would want to show any tooltip in subscript avatar.

https://github.com/Expensify/App/assets/25876548/13dfc9ef-f95c-4e13-a06e-50eabe03a33f

Third requestor avatar should also show email

Yeah I don't think we need to show a tooltip for the workspace, as it'll basically be the same as the display name.

@allroundexperts I think we decided not to show tooltip for workspace name as it just shows the display name itself.

@allroundexperts Looks like we will no longer need these changes. We are going to update money request header in this issue.


Logs implementation draft

Codecov Report

Merging #103 into master will decrease coverage by 3.95%.
The diff coverage is 25.58%.

@@            Coverage Diff             @@
##           master     #103      +/-   ##
==========================================
- Coverage   80.36%   76.41%   -3.96%
==========================================
  Files           5        5
  Lines         433      458      +25
==========================================
+ Hits          348      350       +2
- Misses         71       94      +23
  Partials       14       14

Flag
Coverage Δ

#unittests
76.41% <25.58%> (-3.96%)
:arrow_down:

Impacted Files
Coverage Δ

session/session.go
100% <ø> (ø)
:arrow_up:

config/config.go
91.3% <100%> (ø)
:arrow_up:

main.go
68.62% <100%> (+0.31%)
:arrow_up:

selenoid.go
71.17% <21.95%> (-7.85%)
:arrow_down:

Continue to review full report at Codecov.

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


Dev_HackerRank Problems

Added new Hacker rank Problems in cpp and Python.

Please consider this pull request for hacktoberfest2022


Improve migrations folder structure

Currently all the migrations are created inside the migrations folder at the same level.
As the number of created migrations for a project rises it gets more cumbersome to navigate this folder (opening a migration file to edit after creation for example), because the list is huge and a lot of scrolling is necessary. This could also have a performance impact if the number of files is really big (git uses sub-folders in its internal object organisation to avoid this problem)
My suggestion is to group the migrations by year and maybe month too and this way make the migrations folder more user friendly.
Regarding the existing migrations, all of them have a timestamp and we could write a script to migrate them to the new structure if necessary.
I don't think this is a priority but it could be an improvement.
I could find some time to work on this if the maintainers and users consider this useful/necessary.

It's definitely something to consider, but the argument about finding files doesn't really make sense, since the files will always be oldest-to-newest or vice versa.
I would consider this very low priority, but definitely something to consider as we move towards v1.0.

I never meant to make an argument about finding files. The migrations are ordered by ascending date, so the latest migration created is always at the bottom but getting to that means scrolling past all the others. Sorry about the confusion.

definitely a low pro for me as well and also a tough one. Some people use Phinx with very few migrations, whilst others have very substantial use cases.

One possibility to consider is to squash all migrations older than x into a single (the first) one, and remove all other migrations (incl the DB footprint of them). this way you basically refreshed all.
This would go well together with
https://github.com/cakephp/phinx/issues/206
IMO
The whole team just has to be certain all migrations have been applied everywhere below that threshold of months/years :)
This way you can keep everything as it is, one just needs to clean up those every x years or months.

Closing due to lack of activity or out of scope. If there is new interest, please open a PR.


Server address form docker compose

Which Issue was this PR made for?

Closes #92

What is within the scope with this PR
Be able to flexibly change server url that socketio connects to from docker-compose.yaml
What is NOT in the scope with this PR
Related Issue
Other sidenotes that reviewer should be aware of

https://github.com/Amijakan/mochatto/blob/a8584236bb2fd6386f0d85dc4f923de5587d2871/client/src/contexts/SocketIOContext.tsx#L14
Fixed this path since the room id wasn't included.


textLayer slightly off

The text layer for marking, as demonstrated in the simpleviewer is slightly off (towards the bottom). The example from there shows

I've studied this problem and the way to fix it is to use font_metrics.js found in #4629. I've been improving on that code recently, to resolve problems with large or small zoom.
The reason why it happens is because the calculated fontAscent in text_layer_builder.js is slightly off, and always appears to be so. If anyone has better ideas of resolving this without using font_metrics.js I'd like to know, since the aforementioned solution can be (slightly) less performant.

Thinking about this more. What font_metrics.js is really doing is just letting the browser render the fonts correctly and then we measure it from the canvas. It basically means that the font rendering pipeline on the PDF.js end isn't as good as the browser, therefore we fallback to the browser for that information. So probably the best solution would be to improve the font pipeline in pdf.js

Pull request #5545 largly fixes this problem.

Closing since this got fixed by #12896 and other work.


Zygote producing wrong result for ndim >1 & batch > 0

Only 1st element in the gradient is wrong and it is scaled exactly by the batchsize. NOTE: that the batchsize is determined by the internal algorithm and batch=10 is just a hint. In this following example the batchsize is 17. 136/17=8, where 8 is the correct answer
using Quadrature, Cuba, Cubature, Zygote, FiniteDiff, ForwardDiff, Test

f(x,p) = x[1,:]*p[1].+p[2]*p[3]

lb =[1.0,1.0]
ub = [3.0,3.0]
p = [2.0, 3.0, 4.0]
prob = QuadratureProblem(f,lb,ub,p)

function testf3(lb,ub,p; f=f)
    prob = QuadratureProblem(f,lb,ub,p, batch = 10, nout=1)
    solve(prob, CubatureJLh(); reltol=1e-3,abstol=1e-3)[1]
end

dp1 = ForwardDiff.gradient(p->testf3(lb,ub,p),p)
dp2 = Zygote.gradient(p->testf3(lb,ub,p),p)[1]
dp3 = FiniteDiff.finite_difference_gradient(p->testf3(lb,ub,p),p)

@test dp1 ≈ dp3 # passes
@test_broken dp2 ≈ dp3 # Fail  [136,16,12] ≈ [9,16,12]

Most likely due to y not being the correct size for batch. Here it is size nout instead of nout x batch
https://github.com/SciML/Quadrature.jl/blob/11feb791e9423c4dafe615c224526409986f9dcf/src/Quadrature.jl#L491


chore: migrate from k8s.gcr.io to registry.k8s.io

Kubernetes is migrating its image registry from k8s.gcr.io to registry.k8s.io.
Part of kubernetes/k8s.io#4780.

Looks like build is failing for mutation since this was originated from a fork. Could you update your branch?
Run echo "::error::Files were changed during build (see build log). If this was triggered from a fork, you will need to update your branch."
  echo "::error::Files were changed during build (see build log). If this was triggered from a fork, you will need to update your branch."
  cat .repo.patch
  exit 1
  shell: /usr/bin/bash -e {0}
  env:
    CI: true
Error: Files were changed during build (see build log). If this was triggered from a fork, you will need to update your branch.
diff --git a/test/__snapshots__/yaml.test.ts.snap b/test/__snapshots__/yaml.test.ts.snap
index dd2e186..f6c89c0 100644
--- a/test/__snapshots__/yaml.test.ts.snap
+++ b/test/__snapshots__/yaml.test.ts.snap
@@ -87,7 +87,7 @@ Array [
         "spec": Object {
           "containers": Array [
             Object {
-              "image": "registry.k8s.io/redis:e2e",
+              "image": "k8s.gcr.io/redis:e2e",
               "name": "master",
               "ports": Array [
                 Object {
Error: Process completed with exit code 1.

Hey, @ahmedwaleedmalik, our build step cannot run on a fork. Could you run yarn build on your fork and update here.

Not sure what you want from me here? Do you want me to build it and check if it's working? Then yes, i was able to build it.

Hey @ahmedwaleedmalik, we have taken care of this issue and would be closing this PR now.
We thank you for your contribution and bringing visibility into this. Really appreciate it. :)

Hey @ahmedwaleedmalik, we have taken care of this issue and would be closing this PR now.
We thank you for your contribution and bringing visibility into this. Really appreciate it. :)

So the maintainers didn't bother to reply for a month and then just closed the PR. Seems like you folks are very "open source" friendly.


change version number to use when creating scalr gem. Fix bash export…

Superficial changes to version number and PATH export in setup instructions. Let me know if you have any questions!

@saraolives done

@TheJefe 🥇


[core-lro] Initial implementation

Fixes #4900
This PR is ready for an initial review. Feedback appreciated!
Comments about this PR:

As requested by Brian, I'm not exactly following other Poller implementations. Perhaps only Brian's concept design.
It adds isomorphic tests that will run in both NodeJS and the browser.
It adds simple utility unit tests as well as a test simulating a custom Client.
Regarding how core-arm is going to use core-lro, here's a work in progress PR: https://github.com/sadasant/azure-sdk-for-js/pull/6

TODOs:

[ ] Get approval for the current API.
[x] Make sure the new API follows the guidelines: https://azure.github.io/azure-sdk/typescript_design.html#ts-lro
[x] core-arm should not be a dependency, therefore we should not use AzureServiceClient. See the related note below.
[x] Once the API has no references to individual implementations, submit this for review.
Once the feedback is done, follow up the remaining tasks in this issue: https://github.com/Azure/azure-sdk-for-js/issues/4832

Resources

Long Running Operations for the Azure SDK.
TypeScript guidelines for LROs.
Brian's Poller concept design for TypeScript.
Poller implementation in Java.
Java's overall LRO's API design.

Notes about the current implementation in core-arm
Some notes regarding the current code:
AzureServiceClient
The current LRO code depends on the structure of core-arm's AzureServiceClient, of which only two properties are used:

sendRequest.
longRunningOperationRetryTimeout as the delay in seconds.

Another object with a similar shape is the policy that exists the ChallengeBasedAuthenticationPolicy class that exists in each KeyVault package's auto-generated core.
I believe that we will need to make a new class and see how that would fit with the available classes of core-arm and keyvault-certificates.
Non-generic code in core-arm's LRO strategy
The code for the LRO strategy in core-arm determines the state of the request with some non-generic code that is tied to how core-arm interacts with its own service calls and the possible expected responses. This code needs to be factored out so that core-arm is still able to define this behavior by using core-lro's API without storing this inside of core-lro.

Current TODOs:

Rename forget to stop.
Rename retry to poll.
Accept a RequestOptionsBase parameter for any API method that sends an http request underneath, then either use the class' requestOptions or the provided one on the parameters.
Write tests for all the possible ways to cancel the poller.
Add to the TypeScript guidelines that the LRO implementation needs to throw if the cancel method is called when cancellation is not supported.
Move the defaultAzurePoller to a separate PR based on this branch, and targeting this branch, in which core-arm depends on core-lro, so we can prove that the core-arm tests are passing as expected.
Make a separate PR with keyvault-certificate's LRO strategy.

Resolved all the previous conversations since I did a major API change based on the latest meeting Jeff and I had.

@sadasant Is this still on track for the October preview?


Update() doesn't refresh background images.

Using version 10.19.
It appears the update() doesn't refresh background images?
Also the 'loaded' class is not being appended to lazy loaded background images.
My patch around this (using jquery)
$('.lazy:not(.loaded)[data-bg]').each(function(i, el){
var $el = $(el);
var background = $el.data('bg');
$el.css("backgroundImage", background).addClass("loaded");
});

It appears the update() doesn't refresh background images?

No, it doesn't, and it isn't supposed to. If you read the API docs, it says the update method only checks if new images arrived in the scrolling container.

Also the 'loaded' class is not being appended to lazy loaded background images.

No, it doesn't, and it isn't supposed to. There's no way to check if a background image is loaded in javascript. The real question is: if it really is a background image, why do you need to be notified for its loading? If it is a content image, you should use real images with the img tag.
There are tons of closes issues about this topic. Please check the closed issues containing the "background" word.

Fair..
2a) I wouldn't expect it to check if it actually loaded. In my mind if the swap from data-src to src happened the loaded class would apply. It's 50/50 here.
2b) If there is a background image loading in an infinite scrolling loading scenario. The background image was used on a svg, where background-position: contain. Applying the loaded class here (as in the code above) prevents reloading.


ios: Update examples to display errors with a red background

Update the Swift and Objective-C demos to follow the UI logic implemented by https://github.com/lyft/envoy-mobile/pull/166.
// @buildbreaker

https://github.com/lyft/envoy-mobile/pull/192


Support localizations for program name and description

Description
Programs should have names and descriptions that are localized to all supported languages. To do this, the first step is adding localizedName and localizedDescription fields to ProgramDefinition

name for programs is now an immutable field - the admin sets this once, and it is later used to (for example) get all versions of a program with name x
Adds a localizedName field to ProgramDefinition that contains an ImmutableMap<Locale, String> with the localized, applicant-viewable names of programs
Adds a localizedDescription field to ProgramDefinition similar to the above, though the description is both for admin and applicant views

Checklist

[x] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Issue(s)
Fixes #766
#777

In general looks good. Do we want to include input field for admin to set localized name/description? It's a bit confusing to me as we seem to set admin name/description on create but then on update we change the localized name/description.

Agree it's confusing! The next step is to allow the admin to add localized names and descriptions for the applicant display cards: #777


end brace with next comment line make bad indent

Input
The code looked like this before beautification:
var o = {
    k: 0
}
// ...
foo(o)

Expected Output
var o = {
    k: 0
}
// ...
foo(o)

Actual Output
var o = {
        k: 0
    }
    // ...
foo(o)

Settings
Example:
{
    "brace_style": "collapse"
}

The proposed fix for #1069 would also handle this.  The comment would stick to the element below and match the indent there.  It would also not be part of the preceding statement, fixing the over-indent there.


Add 2 streaming_error_response tests cases with large payloads

This would help with testing certain paths in cronet_transport.c.

Test seems to fail with current code:
https://grpc-testing.appspot.com/job/gRPC_pull_requests_asan_c/2712/testReport/junit/(root)/c_linux_asan_native/bins_asan_h2_ssl_proxy_test_streaming_error_response_GRPC_POLL_STRATEGY_poll_cv/

[trickle] No significant performance differences


Feed not working in netvibes

I tried several other profiles and they work fine, but they're seems to be a problem with the following: http://googleplusrss.nodester.com/103530621949492999968
It does, however, work in google reader.

Are you still having issues? I see nothing wrong with it? What is the issue?

It seems to have resolved itself. I was just given a generic feed error from netvibes and it refused to populate the content from that feed. I'm guessing whatever was causing the problem disappeared from historical scope of the feed (before feb 18th).

Ok well if you see it again let me know. I don't mind fixing any issues.


ObjectStore Has No .Keys Attribute

Expected Behavior

We can gather all of the keys in the ObjectStore with .Keys.
Actual Behavior

To gather the keys in the ObjectStore, we currently need to use
keys = [str(j).split(',')[0][1:] for _, j in enumerate(qb.ObjectStore.GetEnumerator())]
See this related thread.
Potential Solution

Upgrade IObjectStore from IEnumerable<KeyValuePair<string, byte[]>> to IDictionary<string, byte[]>.
Reproducing the Problem

Refer to the notebook in the related thread.
System Information

QC Cloud
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

[x] I have provided detailed steps to reproduce the issue

The ObjectStore instance can be iterated directly providing kvp pairs. In the algorithm can use for kvp in self.ObjectStore: or for kvp in qb.ObjectStore: for research. We might of fixed this in some recent update to pythonNet. Closing issue for now.


Problem: Sample ConfStore files contain secrets

JIRA ticket: EOS-18815
Solution: replace "secret" values with STUB strings.

@johnbent Would you mind to review this patch?


Response references are not resolved

Hello
Looks like NSwag right now do not support references for responses (see example bellow)
swagger: '2.0'
info:
  version: 0.1.0
  title: Test example
  description: Test example
consumes:
  - application/json
produces:
  - application/json
basePath: /
schemes:
  - http
paths:
  /resources:
    get:
      summary: Retrieves a list of resources
      description: Retrieves a list of resources
      operationId: GetResources
      responses:
        '200':
          description: Successful response
          schema:
            type: array
            items:
              $ref: '#/definitions/Resource'
        '500':
          $ref: '#/responses/GeneralError'
definitions:
  Resource:
    description: Some resource.
    type: object
    properties:
      name:
        type: string
  Error:
    type: object
    required:
      - message
    properties:
      message:
        type: string
        description: Error message
responses:
  GeneralError:
    description: General error
    schema:
      $ref: '#/definitions/Error'

I'm going to provide pull request with fix for this...


onWidthChangeCallback to respond on Resize Events from outer Component

Added a onWidthChange callback, to respond to resize Events.
Example Usage:
<ResponsiveReactGridLayout
				className="layout row"
				layouts={gridLayout}
				cols={{lg: 6, md: 6, sm: 6, xs: 2, xxs: 2}}
				rowHeight={this.state.rowHeight}
				useCSSTransforms={true}
				isDraggable={false}
				isResizable={false}
				autoSize={true}
				verticalCompact={true}
			    margin={[10, 10]}
			    onWidthChange={this._onWidthChange}
				>
			</ResponsiveReactGridLayout>

Callback:
_onWidthChange: function(width, margin, cols) {
		var height = width * 1/cols;
		this.setState({
			rowHeight: height
		});
	}

Fixed in 32703a1, thanks for the contribution.


Bug Installation with http

Today I observe new installations can be done with not https
<EMAIL_ADDRESS>There also now in the queue many servers with http

Duplicate of #172


Feature: Ability to reorder columns in the details layout by drag/drop

*Currently limited by the lack of a WinUI DataGrid control.

Can't we use another ListView or TabView with styled for the headers?

@0x5bfa that should work, but we'll need to implement the column generator before we can enable reordering columns.

Is this still not possible ?

It's not supported yet but it's on the todo list

FYI. When I tried last time, it turned out that the list of columns was not stored in user pref database bin file (I used List instead of ColumnsViewModel). That will be a blocker again when I try again.

We can take steps to save the column order, but having the ability to rearrange them would be a good step in the right direction.

[ ] Convert layout manager into service
[ ] Use a list instead of each column model
[ ] Create a control that allows user to slide column like controls such as Taskbar, Slider

Looking forward to this one!!!

Configuring the order of the columns cannot be done in the settings, so can you recreate the grid with the columns in the defined order whenever you open the application and/or confirm the settings with a change of order?

The way we plan to do this, is to allow users to drag & drop columns.


Fix memory leak

Hi!
First, thank you for your work on clammit.
There is a small memory leak which starts to show when handling lots of requests. I found a corresponding issue in the go-clamd library used: https://github.com/dutchcoders/go-clamd/issues/9
Here is a small patch to fix it. I tried it and it did stabilize memory usage.

LGTM, thank you.
@jblackman cleared for merge?
May the 4th be with you!  It would be better to address this in go-clamd itself, IMO, but if you are pressed for time, then all good.

 It would be better to address this in go-clamd itself, IMO, but if you are pressed for time, then all good.

Agreed, it is a quickfix (I'm worried go-clamd is not maintained anymore, though I can still try a PR)

When is this memory leak fix going to be rolled into the main/release?

When is this memory leak fix going to be rolled into the main/release?

Hello,
I prefer to fix this in go-clamd, please hold until the end of this week, I'll update this issue by then.

Dear @hectorj thanks for contributing this. As I wasn't able to focus on this, I've merged your fix and released v0.7.3. I anyway leave #27 open to proper fix this in go-clamd.
Cheers


Jobs enter Error state when session ends

Addresses https://github.ibm.com/IBM-Q-Software/sw-iqx-documentation/issues/1227
✅ I have added the tests to cover my changes.
✅ I have updated the documentation accordingly.
✅ I have read the CONTRIBUTING document.
-->
Summary
Details and comments
Fixes #

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 66.639%

Totals

Change from base Build<PHONE_NUMBER>:
0%

Covered Lines:
3256

Relevant Lines:
4886

💛  - Coveralls


Update SurveyMonkey Info

Easier way, here: http://help.surveymonkey.com/articles/en_US/kb/Canceling-an-Account?deflect=Deleting%20my%20account.

Update found here: #561


Explore running the UATs behind proxy

Context
This task to explore and estimate the effort to be able to run the UATs behind the proxy. We need to look at issues #27 and #54 for initial pointers.
What needs to get done

Explore the effort to run the UATs behind proxy
Document the exploration and the tasks we need to create

Definition of Done
the effort for running UATs behind proxy is well understood and broken down

In #78 I did the exploration for Pipelines, it is the odd one out in our UATs because we cannot modify the container specs of pipelines runners directly, it has to be done through the kfp sdk API. This is not the case for the rest of the UATs, where we can edit the container spec. Therefore my porposal for the Pipelines UATs is different from the rest.
Pipelines UATs behind proxy
Use the kfp sdk to inject the proxy environment variables into the pipelines runner pods.
Here is how we can do this by modifying the existing notebook:

add a cell at the beginning to define the proxy and no proxy values

PROXY_URL=<insert your proxy values>
NO_PROXY_URLS=<insert your no proxy values>

add a cell with a helper function that adds the proxy env variables to the PipelineTask. For more details see the kfp sdk docs. The helper function is as follows:

def add_proxy(obj, proxy=PROXY_URL, no_proxy=NO_PROXY_URLS):
    """Adds the proxy env vars to the PipelineTask object."""
    return (
        obj.set_env_variable(name='http_proxy', value=proxy)
        .set_env_variable(name='https_proxy', value=proxy)
        .set_env_variable(name='HTTP_PROXY', value=proxy)
        .set_env_variable(name='HTTPS_PROXY', value=proxy)
        .set_env_variable(name='no_proxy', value=no_proxy)
        .set_env_variable(name='NO_PROXY', value=no_proxy)
    )

Modify the cell where the pipeline is defined to use the add_proxy helper so that it adds the proxy env vars to all components:

@dsl.pipeline(name='condition-v2')
def condition_pipeline(text: str = 'condition test', force_flip_result: str = ''):
    flip1 = add_proxy(flip_coin(force_flip_result=force_flip_result))
    add_proxy(print_msg(msg=flip1.output))

    with dsl.Condition(flip1.output == 'heads'):
        flip2 = add_proxy(flip_coin())
        add_proxy(print_msg(msg=flip2.output))
        add_proxy(print_msg(msg=text))

UATs behind proxy (excluding Pipelines)
I checked issue #27 and did some ad-hoc test runs in a proxy environment
What we need to achieve is to make all the workloads' containers have the following proxy environment variables set:

HTTP_PROXY
HTTPS_PROXY
NO_PROXY
http_proxy
https_proxy
no_proxy

Adding proxy option to tox
As mentioned in #54, we need to have an option to run the proxy tests with tox. This can be tricky because based on my above proposals, the notebooks will need to be slightly modified to be able to run behind proxy.

We can have a different set of Notebooks with a _proxy suffix for every UAT.

Limitation: It is adding to our maintenance work, double the amount of notebooks every time we change in those tests.

We can have .patch files containing the diff needed to be done to the notebooks and if the proxy option is chosen with tox then the .patch files are used to edit the notebooks before they are run.

This is still some maintenance work because the patch file will rely on the lines of code, so we still need to update them if the lines changed, but it is less maintenance than another set of notebooks.

??

Really great work @NohaIhab! I have some questions, although they 're not a blocker, probably more things we 'll need to consider during implementation.
Adding proxy option to tox
Another option would be to always keep the label there and apply the podDefault only when tox has the proper configuration. But for pipelines, we 'd still need to edit the notebook with the proxy code
Running from UI

Will the user have to apply manually the PodDefault?
If we follow the .patch approach (which I prefer), will the user need to apply manually those changes? On that note, also for pipelines, will they need to uncomment the code this configuration will add?

If yes, we 'll need instructions for those.

thanks @orfeas-k for the review
Adding proxy option to tox
Your suggestion is a great idea actually, we can always have the label, and conditionally create the PodDefault if we are running the tests behind proxy.
If the PodDefault is not created, the label will still be there but no proxy envs will be added to the worrkloads.
Running from the UI

Yes, I think to run from the UI you have to apply this before creating a notebook, so it can be done manually with instructions in the README
In case we apply the label anyway, the .patch will be needed for pipelines only, the .patch removes the need to have the commented code. In that case, the user will apply the .patch and then the notebook is ready to run. -> instructions for running from the UI will be added for that

closing the issue as now we have enough information to start the implementation
thanks @orfeas-k for the review

After discussing with the team, one suggestion was to have in the Notebooks an if condition to check whether the proxy envs are set. and based on that use the PodDefault for the workload or not. This can then eliminate the need for .patch files and make it easier to automate the tests using the driver.


Which type of the flow files does the model employ?

The flownet2 products two types of the optical flow, '.flo' and '.png', which should I choose？Thnaks

.png format, we use a standard visualization code to transform a '.flo' file into a '.png' file.


Image.create_from_data has no sensible way of passing multi-byte samples

Godot version
3.3
System information
N/A
Issue description
When using Image.create_from_data with a multibyte format such as FORMAT_RGBF, there is no sensible way to pass the required 32-bit floating point samples as the expected PoolByteArray argument.
The byte-order of the Float32 samples is not specified anywhere, which means we cannot safely reinterpret the original Float32 samples as a raw buffer of UInt8 values (from the GDNative side), and pass the reinterpreted UInt8 buffer to  Image.create_from_data.
Steps to reproduce
N/A
Minimal reproduction project
No response

It's native byte order according to the source code:
https://github.com/godotengine/godot/blob/7610409b8a14b8499763efa76578795c755a846d/core/image.cpp#L2613-L2618

But it forces us to choose between big-endian and little-endian.

Wasn't big-endian serialization removed from master?

@Calinou It's still there on the current master.
https://github.com/godotengine/godot/blob/8ffb631cdb740540ae74edaa5cef8a04d263ccee/core/io/stream_peer.cpp#L181-L191
Yeah, in practice, one can use little endian where native endian is needed because Godot only runs on platforms that is little endian native. But it's wrong semantically.

Yeah, some image formats can be written and read as little/big endian, so likely both should be supported even today.
See also https://people.cs.umass.edu/~verts/cs32/endian.html.

It's native byte order according to the source code:
https://github.com/godotengine/godot/blob/7610409b8a14b8499763efa76578795c755a846d/core/image.cpp#L2613-L2618

does this mean a reinterpret_cast can be used from the GDNative side, and we can assume the GDNative library uses the same endianness as the engine binary? I am using Swift nativescripts, and Swift has utilities for dealing with endianness.

does this mean a reinterpret_cast can be used from the GDNative side, and we can assume the GDNative library uses the same endianness as the engine binary?

I think so. Not sure how Swift works, but in C++ you can reinterpret_cast a pointer to floats into a pointer to bytes, and use it to fill your PoolByteArray.


remove Option "deployUrl" is deprecated warning

I use the following command to build my angular app and publish it with a back-end made using .NET:
ng build --base-href /%folder% --deploy-url /%folder%/ --configuration=production

And it's a bit annoying to see this warning:

Option "deployUrl" is deprecated: Use "baseHref" option, "APP_BASE_HREF" DI token or a combination of both instead. For more information, see https://angular.io/guide/deployment#the-deploy-url.

There's no way deployUrl is deprecated. Please remove this warning.
OS: Windows 11

deployUrl is indeed deprecated. Closing as working as intended.

and how are we supposed to work without it? https://stackoverflow.com/q/71548735/2896495


Textdraw colors aren't right

Hi, I used this plugin on my open.mp server, everything works fine except for the tdxtdraw colours, the texdraw are supposed to be a semi transparent box, instead I got a Gray box

Can I see your code?

it's just a regular createplayertextdraw
\

Have you tried it in an idle game mode?

yes

Add via Discord: benburakya

i have the same problem

i have the same problem

Can you demonstrate the problem by taking a video?

fixed

fixed

how do u fixed it??

If you're using OpenMP and mixed spellings in your project, here's a quick fix. Simply rename PlayerTextdrawcolor to PlayerTextdrawcolour to maintain consistency and avoid confusion.

@Mydeenissak1 If you're using OpenMP and mixed spellings in your gamemode, here's a quick fix. Simply rename PlayerTextdrawcolor to PlayerTextdrawcolour .

PlayerTextdrawColour kullandığınızda sorun çözülüyor mu?

yes rename all textdrawcolor to colour it worked for me

Using #undef MIXED_SPELLING should solve all the problems then.

yes

but you still need to rename some functions

but still need to rename some functions

I will change all the naming of the plugin and release a new version. Probably all the problems will be fixed. I will also make a converter that will change all your codes.

there is a textdraw order issue also

there is a textdraw order issue also

Yes, I will address this issue as well.


When the Google Chrome font is smaller than 12px, the cursor is selected misplaced

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version:  Chrome  87.0.4280.88
Operating system and its version: macos 10.14.5
PDF.js version: 2.5.207
Is a browser extension: no

Steps to reproduce the problem:

Use official example：https://mozilla.github.io/pdf.js/web/viewer.html
Zoom out to 50% and select text

What is the expected behavior? (add screenshot)

What went wrong? (add screenshot)

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension): none
When the pdf is zoomed, the font size is adjusted in response, but the minimum font size of Google Chrome is 12px, so there is an offset.

Duplicate of #12243

I managed to fix with pdfPage.getTextContent({ normalizeWhitespace: true })


feat: add BPMN timer events notifications

This PR adds support for BPMN timer events and add subscription by arguments using the following schema:
type Subscription {
    engineEvents(
    	serviceName : [String!],
    	appName : [String!],
        eventType: [EngineEventType!],
    	processDefinitionKey : [String!],
	processInstanceId : [String!],
	businessKey : [String!]
    ) : [EngineEvent]
}

with enum for event types:
enum EngineEventType {
	PROCESS_STARTED
	PROCESS_COMPLETED
	PROCESS_CREATED
	PROCESS_CANCELLED
	PROCESS_RESUMED
	PROCESS_SUSPENDED
	PROCESS_DEPLOYED
	ACTIVITY_STARTED
	ACTIVITY_CANCELLED
	ACTIVITY_COMPLETED
	VARIABLE_CREATED
	VARIABLE_UPDATED
	VARIABLE_DELETED
	SEQUENCE_FLOW_TAKEN
	TASK_CREATED
	TASK_COMPLETED
	TASK_ASSIGNED
	TASK_ACTIVATED
	TASK_SUSPENDED
	TASK_CANCELLED
	INTEGRATION_REQUESTED
	INTEGRATION_RESULT_RECEIVED
	TASK_CANDIDATE_USER_ADDED
	TASK_CANDIDATE_USER_REMOVED
	TASK_CANDIDATE_GROUP_ADDED
	TASK_CANDIDATE_GROUP_REMOVED
	SIGNAL_RECEIVED,
        TIMER_SCHEDULED,
        TIMER_FIRED,
        TIMER_CANCELLED,
        TIMER_EXECUTED,
        TIMER_FAILED,
        TIMER_RETRIES_DECREMENTED
}

and EngineEvent type:
type EngineEvent {
    id : String
    timestamp : Long
    serviceName : String
    serviceFullName : String
    serviceVersion : String
    serviceType : String
    appName : String
    appVersion : String

    processInstanceId : String
    parentProcessInstanceId : String
    processDefinitionId : String
    processDefinitionKey : String
    processDefinitionVersion : Long
    businessKey : String

    entityId : String
    entity : ObjectScalar
    eventType : EngineEventType
}

Part of https://github.com/Activiti/Activiti/issues/2636

@erdemedeiros I have fixed all the comments


Vendor chunk naming ignores webpackChunkName comments

Bug report

What is the current behavior?
For a dynamic import like this
import(/* webpackChunkName: "account" */ /* webpackPrefetch: true */ './Components/Account/Account'),

Webpack 5 will generate the following source code chunk for me:
account.e5d772cdaf3c5f18ee93.js
and a vendor chunk that looks something like:
323.fee73acb2259d6f54633.js
If the current behavior is a bug, please provide the steps to reproduce.

Try a dynamic import with webpackChunkName magic comment
Do not specify optimization config or use SplitChunksPlugin
Run the build
Check the resulting chunk files and try to find the vendor chunk for your source chunk

What is the expected behavior?
Previously, with webpack 4, I'd get files that look like:
account.e5d772cdaf3c5f18ee93.js
account~vendor.fee73acb2259d6f54633.js

Other relevant information:
webpack version: 5.50.0
Node.js version: 12.16.2
Operating System: Linux
Additional tools:

We intentionally no longer name vender split chunks by the name of the origin chunk. vendor chunks might be shared by multiple chunks, adding a new chunk which shares an existing vendor chunk should not affect the filename/content of the vendor chunk, since this causes unnecessary invalidations.
You could restore the old behavior with a custom splitChunks.cacheGroups.xxx.name option, but I won't recommend doing that.


config: update the list of auto-assigned reviewers for four docs repos

Signed-off-by: qiancai<EMAIL_ADDRESS>In ti-community-blunderbuss, remove the exclude reviewers and add the include reviewers for the following four docs repos:

pingcap/docs-cn
pingcap/docs
pingcap/docs-dm
pingcap/docs-tidb-operator

/merge


Wrong word in the expression "installing values"

A wrong word was used in the about section of the landing page.
Which task do you want to work on?
change "Installing values" to "Instilling values"
Expected behaviour
"Instilling values"
Actual behaviour
"Installing values"
What needs to be done?
Research for the right word: https://www.google.com/search?q=Installing+values&oq=Installing+values&aqs=chrome..69i57j0i271l3j69i60j69i65j69i61j69i60.4906j0j7&sourceid=chrome&ie=UTF-8
Who want to work on this issue?
Jolade (Outreachy Applicant)

Currently working on it.

working on this......Thank you

Issue #139 fixed, awaiting your review @BatoolMM


feat: add rail viewed event

The type of this PR is: feat

This PR resolves CX-3385
Description
Add rail_viewed event to cohesion

PR Checklist (tick all before merging)

[x] If I've added a new file to the tree I've exported it from the common index.ts
[x] I've added comments with examples for any new interfaces and ensured that they're in the docs
[x] No platform-specific terminology has been used outside of click and tap (platform is inferred by the DB storing events)

:rocket: PR was released in v4.104.0 :rocket:


[4.0.0-rc-1] Missing URLs on "Content"

URLs are missing on the page "Content".
They are needed for internal links.

I removed it in purpose to simplify the view and not confuse the beginners, do you think is good to add it?


Best way to get self/calendar into a google calendar

Hi,
I'm trying to get all of the events I have been invited to across all of the interests I have and groups I have joined into one google calendar. The link on the homepage only adds events I have RSVP'd to but I'd like all that I have been invited to. I can get this from the self/calendar API call, but not sure how to link this into a google calendar.
Any help appreciated,
Thanks

Hi @sophieheb the /self/calendar API is a relatively recent addition. It currently only supports json responses but may be extended in the future to support formats like ICAL. If you visit http://www.meetup.com/find/events/?allMeetups=true&eventFilter=all in your browser and look in the right nav bar you should see a calendar display with an export link at the bottom. Click that and you should get the google calendar you're looking for.


Reuse row header template

I've implemented a column that is checkable and also have a header template for that column that toggles all checkable checkboxes in that column

    <input type="checkbox" class="chkRow" ng-disabled="(!tran.allowEdit)" ng-checked="vm.isRowChecked(tran)" id="cb-{{tran.Id}}" value="{{tran.Id}}"
            name="cb" tabindex="0" title="Select Row" ng-click="vm.selectTran(tran)">

and the header template looks like this:

The individual row checkboxes need to be part of the definition of the table and therefore must be defined for each table that supports checkboxes. I would like the have the header checkbox template be defined once for all consumers of that template, but it's difficult because all consumers' controller must be "ControllerAs" "vm".
How can I refactor the header checkbox template to be more generic and consumed by all tables that need this template - without having to have all Controllers be "vm" or rewriting the template for each Controller using their specific ControllerAs alias?

@esinek as you will add 'gridHeaderCheckbox_template' to some html file, say 'gridHeaderCheckbox_template.html' and then you will need to include that html file where ever you have ng-table which uses this header template. like:
<ng-include src="'gridHeaderCheckbox_template.html'" ng-init="vm = HomeCtrl" > </ng-include>

and ng-init to pass current scope to template so that you can use vm in template, irrespective of whatever name of your "ControllerAs" is, here  ControllerAs is HomeCtrl .
Hope this helps.


💲[Native Checkout] Pledge Amount Cell

📲 What
Implements pledge amount cell UI.
🤔 Why
New design = new cell 😄
🛠 How
We've added custom cell PledgeAmountCell as well a custom input view for the amount AmountInputView which properly aligns the amount value and the currency.
Please note that user interaction has not been enabled (this is simply a visual layout work).
This is me fighting UIKit this week...thanks Apple
(I'm the hamster)

📍 Note
In order to being able to see the screen you can navigate to ProjectPamphletContentViewController and change the behaviour of goToRewardsPledge function to the following
let vc = PledgeViewController.instantiate()
vc.configureWith(project: project, reward: reward)

let nc = UINavigationController(rootViewController: vc)
self.present(nc, animated: true)

👀 See

iPhone SE
iPhone X
iPad Pro

♿ Accessibility
For the Dynamic Type support we're switching the axis of the container that holds the stepper & the input field. If the font gets too big the axis are vertical...for anything normal-ish the axis are horizontal.

iPhone SE
iPhone X
iPad Pro

Dynamic Type

[ ] Stepper & input field are aligned horizontally for smaller/normal-ish font sizes
[ ] Stepper & input field are aligned vertically for accessibility (larger) font sizes

VoiceOver

[ ] The title is read as Your pledge amount (and is localized)
[ ] The minus button is read as Decrement, button (alternatively dimmed if it's in default state)
[ ] The plus button is read as Increment, button
[ ] The currency is read as US dollars (or any other currency)
[ ] The amount is read as X, textfield (plus instructions on editing the textfield)

✅ Acceptance criteria

[ ] The cell matches designs
[ ] Stepper's default state for the - button is disabled
[ ] Stepper's - & + buttons have highlighted state (light shade of gray)
[ ] Currency's ascender is aligned to amount's ascender

Please note that there are some deprecated snapshot tests included, I'm not entirely sure but they must have been missed on the feature branch.


More aggressive temporary demoting

Description
Increase the scope of temporary demoting to those fields that are accessed in multiple stages, but only at [0, 0, 0].
To do:

[ ] Increase the scope of testing demotion pass
[ ] Verify that the demotion is done correctly

Requirements
Before submitting this PR, please make sure:

[ ] The code builds cleanly without new errors or warnings
[ ] The code passes all the existing tests
[ ] If this PR adds a new feature, new tests have been added to test these
new features
[ ] All relevant documentation has been updated or added

Additionally, if this PR contains code authored by new contributors:

[x] All the authors are covered by a valid contributor assignment agreement,
signed by the employer if needed, provided to ETH Zurich
[x] The names of all the new contributors have been added to an updated
version of the AUTHORS.rst file included in the PR

I need to re-think this approach. We need the addition of cross-stage VarDecls in order for this to work.


Update README.md - include Yarn at Install section

Coverage increased (+8.4%) to 95.152% when pulling 322615b011091ffc6d2b7522a64e41f4184c6215 on jbruni:patch-1 into 245cc3b9c1266bf0a653913d1771f672d213f2d6 on davidjbradshaw:master.

Thanks


Cannot install jruby <IP_ADDRESS> or 1.7preview1 - Ubuntu

Is there a workaround to ruby-build to install jruby on ubuntu 12.04? I receive this error when trying to install.
sayth@sayth-TravelMate-5740G:~$ rbenv install jruby-<IP_ADDRESS>
Downloading http://jruby.org.s3.amazonaws.com/downloads/<IP_ADDRESS>/jruby-bin-<IP_ADDRESS>.tar.gz...
Installing jruby-<IP_ADDRESS>...
BUILD FAILED
Inspect or clean up the working tree at /tmp/ruby-build.20120720224807.9240
Results logged to /tmp/ruby-build.20120720224807.9240.log
Last 10 log lines:
make[2]: g++: Command not found
make[2]: *** [build/unix/Linux/argparser.o] Error 127
make[2]: Leaving directory /home/sayth/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/1.8/gems/jruby-launcher-1.0.14-java' make[1]: *** [.build-conf] Error 2 make[1]: Leaving directory /home/sayth/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/1.8/gems/jruby-launcher-1.0.14-java'
make: *** [.build-impl] Error 2
Gem files will remain installed in /home/sayth/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/1.8/gems/jruby-launcher-1.0.14-java for inspection.
Results logged to /home/sayth/.rbenv/versions/jruby-<IP_ADDRESS>/lib/ruby/gems/1.8/gems/jruby-launcher-1.0.14-java/./gem_make.out

im having this kind of problem, how did you solved this? Thanks :) :+1:

i solved it after installing g++.
sudo apt-get install g++
Thanks :)


Code coverage in CI

Add unit test modules

60% coverage for gh-lib crate.
0% for gh-auth.
0% for gh-cli.


Update README.md

GitSecure Bill of Material

Control ID
Section
Description

CM-8
Configuration Management
Information System Component Inventory

 Download Bill of Material Report: [JSON Format]

❌ GitSecure Open Source License Assessment: Needs Review
FedRAMP Controls covered:

Control ID
Section
Description

CM-7(5)
Configuration Management
Least Functionality - Authorized Software / Whitelisting

CM-10
Configuration Management
Software Usage Restrictions

CM-11
Configuration Management
User-Installed Software

CA-6
Security Assessment and Authorization
Security Authorization

CM-4
Configuration Management
Security Impact Analysis

CA-2
Security Assessment and Authorization
Security Assessments

❌ Python PackagesSelf-Certifiable Packages
MarkupSafe version 1.1.1zipp version 0.6.0Flask_Cors version 3.0.8itsdangerous version 1.1.0pytz version 2019.3visitor version 0.1.3Mako version 1.0.7six version 1.13.0Flask_API version 1.1WTForms version 2.2.1wheel version 0.33.6Flask_Bootstrap version <IP_ADDRESS>Flask_WTF version 0.14.2more_itertools version 8.0.2importlib_metadata version 1.2.0Werkzeug version 0.16.0pyrsistent version 0.15.6aniso8601 version 8.0.0Flask version 1.1.1Flask_HTTPAuth version 3.3.0flask_nav version 0.6attrs version 19.3.0Click version 7.0Packages that Need Review
pip version 19.3.1setuptools version 41.6.0pathvalidate version 0.29.0Django version 1.2flask_restplus version 0.13.0Jinja2 version 2.10.3MarkupSafe version 1.0dominate version 2.4.0jsonschema version 3.2.0django version 1.2
Download Open Source Steering Committee (OSSC) Report: [JSON Format]  [HTML Format]

Docker CIS Community Edition 1.13

Control ID
Section
Description

CM-6
Configuration Management
Configuration Settings

CA-2
Security Assessment and Authorization
Security Assessments

Dockerfile: redis.yaml

ID
Rule
Compliant?

5.11
Ensure CPU priority is set appropriately on the container
:heavy_check_mark:

5.13
Ensure incoming container traffic is binded to a specific host interface
?

5.14
Ensure 'on-failure' container restart policy is set to '5'
?

5.19
Ensure mount propagation mode is not set to shared
?

5.20
Ensure the host's UTS namespace is not shared
?

5.31
Ensure the Docker socket is not mounted inside any containers
:heavy_check_mark:

5.1
Ensure AppArmor Profile is Enabled
?

5.10
Ensure memory usage for container is limited
:x:

5.16
Ensure the host's IPC namespace is not shared
:heavy_check_mark:

5.28
Ensure PIDs cgroup limit is used
?

5.6
Ensure ssh is not run within containers
?

5.27
Ensure docker commands always get the latest version of the image
?

5.21
Ensure the default seccomp profile is not Disabled
?

5.18
Ensure the default ulimit is overwritten at runtime, only if needed
?

5.15
Ensure the host's process namespace is not shared
:heavy_check_mark:

5.29
Ensure Docker's default bridge docker0 is not used
?

5.12
Ensure the container's root filesystem is mounted as read only
?

5.4
Ensure privileged containers are not used
:heavy_check_mark:

5.5
Ensure sensitive host system directories are not mounted on containers
:heavy_check_mark:

5.3
Ensure Linux Kernel Capabilities are restricted within containers
:heavy_check_mark:

5.7
Ensure privileged ports are not mapped within containers
:heavy_check_mark:

5.8
Ensure only needed ports are open on the container
?

5.9
Ensure the host's network namespace is not shared
:heavy_check_mark:

5.23
Ensure docker exec commands are not used with user option
?

5.24
Ensure cgroup usage is confirmed
?

5.26
Ensure container health is checked at runtime
?

5.2
Ensure SELinux security options are set, if applicable
?

5.22
Ensure docker exec commands are not used with privileged option
?

5.25
Ensure the container is restricted from acquiring additional privileges
?

5.30
Ensure the host's user namespaces is not shared
?

5.17
Ensure host devices are not directly exposed to containers
?

GitSecure Dockerfile Linter
Checks powered by Hadolint
Haolint is a smarter Dockerfile linter that helps you build best practice Docker images.

Control ID
Section
Description

SA-11 (1)
System and Services Acquisition
Developer Security Testing and Evaluation - Static Code Analysis

Dockefile : //Dockerfile

Line #
ID
Description

2
DL3008
Pin versions in apt get install. Instead of apt-get install <package> use apt-get install <package>=<version>

2
DL3009
Delete the apt-get lists after installing something

2
DL3015
Avoid additional packages by specifying --no-install-recommends

GitSecure Vulnerablility Report

Control ID
Section
Description

RA-5
Risk Assessment
Vulnerability Scanning

CA-7
Security Assessment and Authorization
Continuous Monitoring

SA-12
System and Services Acquisition
Supply Chain Protection

SI-2
System and Information Integrity
Flaw Remediation

CM-4
Configuration Management
Security Impact Analysis

CA-2
Security Assessment and Authorization
Security Assessments

   For Dockerfile: /Dockerfile  Stage: shri4u/myapp-base:0.1

:x: OS Packages Safe
:x: Pip Packages Safe
Vulnerability Analysis
Vulnerable OS Packages
Total of 1 vulnerable os packages found
Package  django   needs to be updated to version ****
Vulnerable Python Packages
Total of 1 vulnerable pip packages found
Package  Django   needs to  satisfy this version requirement  >= 1.8.15
Detailed Package Analysis
Contains vulnerability, license and pedigree information for each package

  OS Packages [Expand for more information]

 Package Name: django | Current Version: 1.2   (VULNERABLE)

CVE Vulnerabilities:
Recommended update :

25701
Severity:
Fixed in:

33063
Severity:
Fixed in:

33064
Severity:
Fixed in:

33065
Severity:
Fixed in:

33066
Severity:
Fixed in:

33067
Severity:
Fixed in:

33068
Severity:
Fixed in:

33069
Severity:
Fixed in:

25709
Severity:
Fixed in:

33071
Severity:
Fixed in:

33072
Severity:
Fixed in:

33070
Severity:
Fixed in:

25713
Severity:
Fixed in:

25714
Severity:
Fixed in:

25715
Severity:
Fixed in:

33074
Severity:
Fixed in:

33073
Severity:
Fixed in:

25718
Severity:
Fixed in:

33058
Severity:
Fixed in:

33059
Severity:
Fixed in:

33060
Severity:
Fixed in:

33062
Severity:
Fixed in:

Compliance:
OSSC Compliant:
Last Reviewed License Version: Not Available
Pedigree Reviewed:
Last Reviewed Pedigree Version: Not Available

  Python Packages [Expand for more information]

 Package Name: django | Current Version: 1.2

Python Vulnerabilities:
No Vulnerabilities Present in this Pip Package
Compliance:
OSSC Compliant:
Last Reviewed License Version: Not Available
Pedigree Reviewed:
Last Reviewed Pedigree Version: Not Available

 Package Name: Django | Current Version: 1.2  (VULNERABLE)

Python Vulnerabilities:
Recommended update : >= 1.8.15

1. Affected Versions  : <1.2.2
 Description
Cross-site scripting (XSS) vulnerability in Django 1.2.x before 1.2.2 allows remote attackers to inject arbitrary web script or HTML via a csrfmiddlewaretoken (aka csrf_token) cookie.

2. Affected Versions  : <1.2.7
 Description
django.contrib.sessions in Django before 1.2.7 and 1.3.x before 1.3.1, when session data is stored in the cache, uses the root namespace for both session identifiers and application-data keys, which allows remote attackers to modify a session by triggering use of a key that is equal to that session's identifier.

3. Affected Versions  : <1.2.7
 Description
The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 relies on Python libraries that attempt access to an arbitrary URL with no timeout, which allows remote attackers to cause a denial of service (resource consumption) via a URL associated with (1) a slow response, (2) a completed TCP connection with no application data sent, or (3) a large amount of application data, a related issue to CVE-2011-1521.

4. Affected Versions  : <1.2.7
 Description
The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 originally tests a URL's validity through a HEAD request, but then uses a GET request for the new target URL in the case of a redirect, which might allow remote attackers to trigger arbitrary GET requests with an unintended source IP address via a crafted Location header.

5. Affected Versions  : <1.2.7
 Description
The CSRF protection mechanism in Django through 1.2.7 and 1.3.x through 1.3.1 does not properly handle web-server configurations supporting arbitrary HTTP Host headers, which allows remote attackers to trigger unauthenticated forged requests via vectors involving a DNS CNAME record and a web page containing JavaScript code.

6. Affected Versions  : <1.3.2
 Description
The (1) django.http.HttpResponseRedirect and (2) django.http.HttpResponsePermanentRedirect classes in Django before 1.3.2 and 1.4.x before 1.4.1 do not validate the scheme of a redirect target, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via a data: URL.

7. Affected Versions  : <1.3.2
 Description
The django.forms.ImageField class in the form system in Django before 1.3.2 and 1.4.x before 1.4.1 completely decompresses image data during image validation, which allows remote attackers to cause a denial of service (memory consumption) by uploading an image file.

8. Affected Versions  : <1.3.2
 Description
The get_image_dimensions function in the image-handling functionality in Django before 1.3.2 and 1.4.x before 1.4.1 uses a constant chunk size in all attempts to determine dimensions, which allows remote attackers to cause a denial of service (process or thread consumption) via a large TIFF image.

9. Affected Versions  : <1.3.4
 Description
The django.http.HttpRequest.get_host function in Django 1.3.x before 1.3.4 and 1.4.x before 1.4.2 allows remote attackers to generate and display arbitrary URLs via crafted username and password Host header values.

10. Affected Versions  : <1.4.18
 Description
The django.util.http.is_safe_url function in Django before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3 does not properly handle leading whitespaces, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted URL, related to redirect URLs, as demonstrated by a "\njavascript:" URL.

11. Affected Versions  : <1.4.18
 Description
The django.views.static.serve view in Django before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3 reads files an entire line at a time, which allows remote attackers to cause a denial of service (memory consumption) via a long line in a file.

12. Affected Versions  : <1.4.18
 Description
Django before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3 allows remote attackers to spoof WSGI headers by using an _ (underscore) character instead of a - (dash) character in an HTTP header, as demonstrated by an X-Auth_User header.

13. Affected Versions  : <1.4.20
 Description
The utils.http.is_safe_url function in Django before 1.4.20, 1.5.x, 1.6.x before 1.6.11, 1.7.x before 1.7.7, and 1.8.x before 1.8c1 does not properly validate URLs, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a control character in a URL, as demonstrated by a \x08javascript: URL.

14. Affected Versions  : <1.7.11
 Description
The get_format function in utils/formats.py in Django before 1.7.x before 1.7.11, 1.8.x before 1.8.7, and 1.9.x before 1.9rc2 might allow remote attackers to obtain sensitive application secrets via a settings key in place of a date/time format setting, as demonstrated by SECRET_KEY.

15. Affected Versions  : <1.7.6
 Description
Cross-site scripting (XSS) vulnerability in the contents function in admin/helpers.py in Django before 1.7.6 and 1.8 before 1.8b2 allows remote attackers to inject arbitrary web script or HTML via a model attribute in ModelAdmin.readonly_fields, as demonstrated by a @property.

16. Affected Versions  : <1.8.10
 Description
The password hasher in contrib/auth/hashers.py in Django before 1.8.10 and 1.9.x before 1.9.3 allows remote attackers to enumerate users via a timing attack involving login requests.

17. Affected Versions  : <1.8.10
 Description
The utils.http.is_safe_url function in Django before 1.8.10 and 1.9.x before 1.9.3 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks or possibly conduct cross-site scripting (XSS) attacks via a URL containing basic authentication, as demonstrated by<EMAIL_ADDRESS>

18. Affected Versions  : <1.8.15
 Description
The cookie parsing code in Django before 1.8.15 and 1.9.x before 1.9.10, when used on a site with Google Analytics, allows remote attackers to bypass an intended CSRF protection mechanism by setting arbitrary cookies.

19. Affected Versions  : >=1.2,<1.2.4
 Description
The administrative interface in django.contrib.admin in Django before 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1 does not properly restrict use of the query string to perform certain object filtering, which allows remote authenticated users to obtain sensitive information via a series of requests containing regular expressions, as demonstrated by a created_by__password__regex parameter.

20. Affected Versions  : >=1.2,<1.2.4
 Description
The password reset functionality in django.contrib.auth in Django before 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1 does not validate the length of a string representing a base36 timestamp, which allows remote attackers to cause a denial of service (resource consumption) via a URL that specifies a large base36 integer.

21. Affected Versions  : >=1.2,<1.2.5
 Description
Django 1.1.x before 1.1.4 and 1.2.x before 1.2.5 does not properly validate HTTP requests that contain an X-Requested-With header, which makes it easier for remote attackers to conduct cross-site request forgery (CSRF) attacks via forged AJAX requests that leverage a "combination of browser plugins and redirects," a related issue to CVE-2011-0447.

22. Affected Versions  : >=1.2,<1.2.5
 Description
Directory traversal vulnerability in Django 1.1.x before 1.1.4 and 1.2.x before 1.2.5 on Windows might allow remote attackers to read or execute files via a / (slash) character in a key in a session cookie, related to session replays.

Compliance:
OSSC Compliant:
Last Reviewed License Version: Not Available
Pedigree Reviewed:
Last Reviewed Pedigree Version: Not Available

GitSecure Auto-remediation
  PR Created at:  https://github.com/cmadam/myapp/pull/16

GitSecure Deployment Vulnerablility Report

Control ID
Section
Description

RA-5
Risk Assessment
Vulnerability Scanning

See package details below.
Report for: redis.yaml
Docker image: redis:3.0
This vulnerable image is exposed by the following services:

service default:redissvc:30080 declared in redis-service.yaml and also exposed in ingress default:redis-ingress declared in redis-ingress.yaml

Base OS image: debian 8.8

Package
Version
CVE
Severity
Fix

libgcrypt20
1.6.3-2+deb8u3
[CVE-2018-0495]
Unknown
1.6.3-2+deb8u5

libgcrypt20
1.6.3-2+deb8u3
[CVE-2019-13627]
Unknown
1.6.3-2+deb8u6

libgcrypt20
1.6.3-2+deb8u3
[CVE-2017-7526]
Negligible
1.6.3-2+deb8u4

bash
4.3-11+deb8u1
[CVE-2019-9924]
Low
4.3-11+deb8u2

bash
4.3-11+deb8u1
[CVE-2016-9401]
Unknown
4.3-11+deb8u2

gnupg
1.4.18-7+deb8u3
[CVE-2018-12020]
Negligible
1.4.18-7+deb8u5

gnupg
1.4.18-7+deb8u3
[CVE-2017-7526]
Negligible
1.4.18-7+deb8u4

e2fsprogs
1.42.12-2+b1
[CVE-2019-5094]
Unknown
1.42.12-2+deb8u1

tar
1.27.1-2+deb8u1
[CVE-2018-20482]
Unknown
1.27.1-2+deb8u2

procps
2:3.3.9-9
[CVE-2018-1122]
Unknown
2:3.3.9-9+deb8u1

procps
2:3.3.9-9
[CVE-2018-1126]
Unknown
2:3.3.9-9+deb8u1

procps
2:3.3.9-9
[CVE-2018-1124]
Unknown
2:3.3.9-9+deb8u1

procps
2:3.3.9-9
[CVE-2018-1123]
Unknown
2:3.3.9-9+deb8u1

procps
2:3.3.9-9
[CVE-2018-1125]
Unknown
2:3.3.9-9+deb8u1

sensible-utils
0.0.9
[CVE-2017-17512]
Unknown
0.0.9+deb8u1

systemd
215-17+deb8u7
[CVE-2018-16864]
Unknown
215-17+deb8u9

systemd
215-17+deb8u7
[CVE-2018-15686]
Unknown
215-17+deb8u8

systemd
215-17+deb8u7
[CVE-2018-16865]
Unknown
215-17+deb8u9

systemd
215-17+deb8u7
[CVE-2018-1049]
Unknown
215-17+deb8u8

systemd
215-17+deb8u7
[CVE-2017-18078]
Negligible
215-17+deb8u12

systemd
215-17+deb8u7
[CVE-2018-15688]
Negligible
215-17+deb8u8

systemd
215-17+deb8u7
[CVE-2019-3815]
Negligible
215-17+deb8u11

systemd
215-17+deb8u7
[CVE-2019-3842]
Unknown
215-17+deb8u12

systemd
215-17+deb8u7
[CVE-2019-6454]
Unknown
215-17+deb8u10

apt
<IP_ADDRESS>.4
[CVE-2019-3462]
Unknown
<IP_ADDRESS>.5

❌ GitSecure Open Source License Assessment: Needs Review
FedRAMP Controls covered:

Control ID
Section
Description

CM-7(5)
Configuration Management
Least Functionality - Authorized Software / Whitelisting

CM-10
Configuration Management
Software Usage Restrictions

CM-11
Configuration Management
User-Installed Software

CA-6
Security Assessment and Authorization
Security Authorization

CM-4
Configuration Management
Security Impact Analysis

CA-2
Security Assessment and Authorization
Security Assessments

❌ Python PackagesSelf-Certifiable Packages
MarkupSafe version 1.1.1zipp version 0.6.0Flask_Cors version 3.0.8itsdangerous version 1.1.0pytz version 2019.3visitor version 0.1.3Mako version 1.0.7six version 1.13.0Flask_API version 1.1WTForms version 2.2.1wheel version 0.33.6Flask_Bootstrap version <IP_ADDRESS>Flask_WTF version 0.14.2more_itertools version 8.0.2importlib_metadata version 1.2.0Werkzeug version 0.16.0pyrsistent version 0.15.6aniso8601 version 8.0.0Flask version 1.1.1Flask_HTTPAuth version 3.3.0flask_nav version 0.6attrs version 19.3.0Click version 7.0Packages that Need Review
pip version 19.3.1setuptools version 41.6.0pathvalidate version 0.29.0Django version 1.2flask_restplus version 0.13.0Jinja2 version 2.10.3MarkupSafe version 1.0dominate version 2.4.0jsonschema version 3.2.0django version 1.2
Download Open Source Steering Committee (OSSC) Report: [JSON Format]  [HTML Format]


Allow customize cattle-cluster-agent

Is your feature request related to a problem? Please describe.
My cluster agent is being evicted and I would like to ensure it's the last pod being evicted due to it's severity.
Describe the solution you'd like
config.yaml allows to customize the agent itself.
Describe alternatives you've considered
Run a manual patch as a workaround as an after hook of bootstrapping a new cluster.
Additional context
Hello,
Recently I have been suffering from cattle-cluster-agent eviction due to some diskPressure (not related with the topic). I wanted to set the priorityClass field to cattle-cluster-agent deployment in a way that is persisted. I have been reviewing the documentation and issues and haven't come up with a way to customize the agent itself during the bootstraping on config.yaml file.
I think additional manifest sections won't work here as I don't want to create new objects, but patch the existing ones.
I have seen that you can customize/add tolerations, priorityClass, etc. to  the CNI itself. Would be great to be able to customize the cluster-agent itself as that would also enable users to set more requirements.

[SURE-4264]

Hi @brandond
Makes sense... Then I guess the question would be how this could be configured in Rancher.
Best,
Alex

This is much needed. We just started enforcing custom taints on ALL our Nodes. This breaks our cattle-cluster-agent initialization because there's no way for us to configure it with tolerations at cluster-init.
We use the rancher terraform provider so running a patch after the cattle-cluster-agent is deployed isn't really viable since we want the terraform apply to succeed to abide by our current Iac workflow.

Just a heads up, this should be resolved with new functionality added in Rancher v2.7.5

https://github.com/rancher/rancher/issues/41035


Input Validation Text

Fixes #332
Creator

[ ] Build relevant tests if any apply
[ ] Ensure there are no new warnings
[ ] Upload an animated GIF showcasing the solution (if it applies)
[ ] Set a relevant reviewer

Reviewer

[x] Run test and make sure all tests pass
[x] Review function and form on iOS
[x] Review function and form on Android
[x] Review function and form on Web
[ ] Review new test logic

@burkeshartsis Everything looks good on my end. Wanted to make sure your eyes viewed it before we merge.

@richarddubay This is good to merge.


Fix GyroReset, TimerReset and EncoderReset AST classes are erroneous

Description
This PR implements the following changes:

fix {Encoder, Gyro, Timer}Reset AST classes and tests - 1452

Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Tested by running the integration tests locally.
Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] My changes generate no new warnings
[X] New and existing unit tests pass locally with my changes

merged with https://github.com/OpenRoberta/openroberta-lab/commit/02d557e7baa7df5e726d8422ab50157eecf73e7a


[1.10.2] No Wither skeletons spawning

After searching in the nether for half an hour I decided to test it in a creative world with a minimal set of mods installed (version <IP_ADDRESS>, but also tested with <IP_ADDRESS>). It is not possible to spawn in a wither skeleton through a spawn egg in the nether. Going back to version <IP_ADDRESS> works as expected.
Minecraft 1.10.2
Forge <IP_ADDRESS>6
Mods:
craftingharmonics-1.9.4_1.10_1.10.2-<IP_ADDRESS>
jei_1.10.2-<IP_ADDRESS>
NashornLib-1.9.4-1.8.77-<IP_ADDRESS>
http://paste.ee/p/SMoId

This is due to the same issue as the Ender Dragon from the last bug.  Dangit Mojang.


Allow increase of filesystem size

Related to #585, if we allow increasing of volume size for block devices, we must also enable support for filesystem growth methods (xfs_growfs for xfs and resize2fs for ext4)

This answers my confusion I outlined in #585. Thank you. This is a good idea. Thanks for capturing it. Please include a general / parent issue that notes we should allow for mutability / update operations to volumes / other objects in general. Thanks.

There have been several comments in meetings I've been in. I definitely see the need in applications like Cassandra and MongoDB where knowing the required future size of a volume upon creation is difficult. It is also very wasteful to over-deploy, even if thinly provisioned.

leaving this one here for any CLI changes that might be needed.


Fixed inappropriate path for documentation

@thinkingserious - Could you decline the other pull request, which has issues with the "username" - valerian-pereira and review / approve this one?
The invalid username, because the inappropriate SSH keys were imported to GitHub.
Fixed the same.
@mbernier  for approval, please

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Feature request: configure the size of the iTerm window

Hi !
First of all, thank you ! I've been looking for this kind of automation tool for iTerm2 for looong time!
I was wondering, it might be possible to define the size of the window at launch.
2 parameters here:

original / latest screen resolution OR full screen  at launch
"native full screen windows" activated or not (Preferences> General> Window)

I don't know if this is something that can be simply configured.

Thank you for opening the issue. I looked at the iTerm API docs and I couldn't find anything for resizing so I don't think it's possible with the API.
They allow setting profiles though. I am not sure if we can save window sizing as a part of the profile and maybe support switching profiles.


Handle database name

This fix will support setting database name for tbl_cache, in other words, non-default databases.
e.g.
tbl_cache(sc, "db_name1.table")

This PR also add use_db() for changing database.
fix: https://github.com/rstudio/sparklyr/issues/447

I found it doesn't solve the problem.

I confirmed this patch fixes only tbl_cache(), so I changed the title.

@chezou Please rename to db_use to be consistent with tbl_, sdf_, ml_, spark_, ft_, etc. functions.

@javierluraschi Changed to tbl_change_db https://github.com/rstudio/sparklyr/pull/474/commits/e8840cc44e5bafd05ff30e5952babe5eb4dc2368

@chezou thank you, the new name puts this function with the right family.

Is this merged in CRAN version?

@bedantaguru No, not yet. I think It'll be released on v0.6.0.


create-environment and replace-environment goals always deploy to default region

I'm trying to use the beanstalk-maven-plugin v1.4.0 to deploy an application to us-west-2. Here's an excerpt from my pom.xml:
<plugin>
    <groupId>br.com.ingenieux</groupId>
    <artifactId>beanstalk-maven-plugin</artifactId>
    <version>1.4.0</version>
    <configuration>
        <!-- the ELB Application/Environment to update -->
        <applicationName>My Application</applicationName>
        <environmentName>application-environment-name</environmentName>
        <region>us-west-2</region>
        <s3Region>us-west-2</s3Region>
        <cnamePrefix>application-environment-name2</cnamePrefix>

        <!-- the artifact to upload -->
        <artifactFile>${project.build.directory}/${project.build.finalName}.zip</artifactFile>

        <!-- the S3 location to upload the artifact to -->
        <s3Bucket>my-s3-bucket</s3Bucket>
        <s3Key>${project.build.finalName}.zip</s3Key>

        <!-- the name to give to this version of the application -->
        <versionLabel>${project.build.finalName}</versionLabel>
    </configuration>
    <executions>
        <!-- hook on the mvn deploy task -->
        <execution>
            <phase>deploy</phase>
            <goals>
                <goal>upload-source-bundle</goal>
                <goal>create-application-version</goal>
                <goal>create-environment</goal>
            </goals>
        </execution>
    </executions>
</plugin>

When I run mvn clean deploy, everything succeeds as expected, except that the application is created in the us-east-1 region, instead of the us-west-2 region as specified in the config. The same problem occurs when I switch the create-environment goal out for replace-environment.
How do I override the default us-east-1 region with a region of my choice?

See https://github.com/ingenieux/beanstalker/issues/69 and run mvn -X with your output please

After a lot more experimentation, I think the solution is to put the environment and region configuration values into my pom file's properties block:
<properties>
    <!-- these config values describe where our application lives in ELB so that the beanstalk-maven-plugin can find it -->
    <beanstalk.applicationName>My Application</beanstalk.applicationName>
    <beanstalk.environmentRef>${artifactId}-dev.elasticbeanstalk.com</beanstalk.environmentRef>
    <beanstalk.environmentName>${artifactId}-dev</beanstalk.environmentName>
    <beanstalker.region>us-west-2</beanstalker.region>
</properties>

I'm not clear on why, but doing so seems to fix the problem. Is this as designed? I would expect to be able to put these properties in the plugin's configuration block without their beanstalk and beanstalker prefixes.

It actually is as designed :)
--
-- Aldrin Leal<EMAIL_ADDRESS>/ http://about.me/aldrinleal
On Tue, Dec 22, 2015 at 4:21 PM, Jonathan<EMAIL_ADDRESS>wrote:

After a lot more experimentation, I think the solution is to put the
environment and region configuration values into my pom file's properties
block:

My Application
${artifactId}-dev.elasticbeanstalk.com
${artifactId}-dev
us-west-2

I'm not clear on why, but doing so seems to fix the problem. Is this as
designed? I would expect to be able to put these properties in the plugin's
configuration block without their beanstalk and beanstalker prefixes.
—
Reply to this email directly or view it on GitHub
https://github.com/ingenieux/beanstalker/issues/79#issuecomment-166732689
.

If that's the case, can I suggest that this be more clearly documented? It seems like a pretty big gotcha that a lot of users of the plugin might run into.
Since I'm only using the plugin for one phase of my build process, I'd prefer to keep its configuration in one spot, rather than splitting it between the global properties block and the plugin's own configuration block, but if I must do so, then that's ok, as long as the requirement is clearly documented.

Somehow, the Mojo Docs for the plugin weren't shown, but it should be regionName instead:
https://github.com/ingenieux/beanstalker/blob/master/beanstalker-common/src/main/java/br/com/ingenieux/mojo/aws/AbstractAWSMojo.java#L119


Deceive D: Adaptive Pseudo Augmentation for GAN Training with Limited Data

Could you please share the paper of Deceive D: Adaptive Pseudo Augmentation for GAN Training with Limited Data, THX.

Thanks very much for your attention. :) The paper is now available: https://arxiv.org/abs/2111.06849


I'd want to specify a path with autopilot.

I want to specify a path with autopilot.
how can I do it?
and I want to know specify a path without autopilot too

Not sure you can with autopilot / trafficmanager, but the undocumented(?) agent API might handle this.

Hey @hi6724, what @qhaas is exactly right. Adding to the comment, the autopilot doesn't currently allow to specify a path for vehicles, choosign randomly one diretion when faced with multiple paths. We have plans to do that but as of right now, you can't.
Regarding the agent API, it does indeed allow you to do so. It is currently undocummented, so here is a bit more detail on how it works. By using the basic agent you can set a destination of an actor.  This is done using the global route planner, which creates a graph and gets the shortest route, as well as the local planner, which uses PIDs to control the vehicle.

Hi,
I'm using carla 0.9.11 in Windows 10. I tried to use the agent API like u recommend before. But i getting the error
name 'BasicAgent' is not defined
What make no sense, sice the other function from PythonAPI work fine. Have you any idea, what the problem is?
Thanks!

As of 0.9.13, the TrafficManager now allows setting paths for its vehicles. I don't think we have the propert documetnation ready yet, so you can check this PR, which has all the new features explained


Tags added in Description

Attempts to fix #44
setup.py  was modified and few tags were added in the Description. Tags are related to neural networks.

setup.py doesn't like having lists in it... let me look into the long_description field and i'll fix it


Threads and isolate in flutter

Article checklist
Attention
Our Peer Reviewer and Content Moderator teams do NOT provide any revisions services. All revisions and edits should be completed on your own forked repo (as to not take up room in the queue) in order for our team to review them all in a timely manner.
ANY ARTICLE SUBMITTED WITH GLARING ERRORS WILL BE IMMEDIATELY CLOSED.

As a rule of thumb - please be sure to only submit articles (pull requests) that are fully polished and ready to be published. Be sure to go through our resources documents for extra and 3rd party (vetted) resources to help improve overall technical writing.

Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels, under 300KB in size, and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes

Remove the backticks and add the issue number below to link and close your Topic Suggestion (issue) when your article has been published (PR has been merged). See this video for more details.

This closes #4136

Finally, delete the article checklist notes in blockquotes and submit your PR. We look forward to reviewing your article.

Good afternoon and thank you for submitting your article for publishing.
Your article has been entered into our queue and should be reviewed (and published pending any changes) as soon as a peer reviewer is finished with the ones in the queue before it. 🚀
Thank you.

@BrianaNzivu kindly reviews changes

Plagiarism check done ✅

Tech review done 👍

Amazing job, @waigwakanoi and @BrianaNzivu. Thanks for the wonderful article. Keep up the fantastic work :)

@waigwakanoi Please DM me via Slack asap.
This article will not received a payout this period - we have no PayPal on file - and the cut off time for this period is up.

Also you may want to consider changing your avatar image (to a more professional looking one) as these articles are intended to help student jump start their developer careers and may be seen by potential employers.

okay sir
On Fri, 21 Jan 2022 at 22:26, hectorkambow @.***> wrote:

@waigwakanoi https://github.com/waigwakanoi Please DM me via Slack asap.
This article will not received a payout this period - we have no PayPal on
file - and the cut off time for this period is up.
—
Reply to this email directly, view it on GitHub
https://github.com/section-engineering-education/engineering-education/pull/5819#issuecomment-1018795610,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVWXVTRKDHKAQ4MK4JKDQSDUXGXMZANCNFSM5K54JVLQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
<section-engineering-education/engineering-education/pull/5819/c1018795610
@github.com>


newsfeed now remembers user configuration settings for descriptions after fullscreen view. Fixes #1282.

Added a runtime var isShowingDescription that gets reset to user config.
this.config.showDescription no longer mutates during runtime.
Changelog has been updated to include this fix.
Sorry about the notification spam in #1282; the actual PR only has one commit.

Please send your pull requests the develop branch.
Don't forget to add the change to CHANGELOG.md.

Note: Sometimes the development moves very fast. It is highly
recommended that you update your branch of develop before creating a
pull request to send us your changes. This makes everyone's lives
easier (including yours) and helps us out on the development team.
Thanks!

Does the pull request solve a related issue?
If so, can you reference the issue?
What does the pull request accomplish? Use a list if needed.
If it includes major visual changes please add screenshots.

This feature is currently present on the develop branch. It's recommended that you wait for the scheduled release on 7/1.
If you really want to switch to the develop branch (which may be unstable), you'll need to git checkout develop and git pull. Then do npm install.

Ah ok. Now I see. Thank you.


Generated an empty chunk: "popup", overwrites a previously emitted file of the same name

Hello. This package has been a huge help! However, I am running into an issue right near what I presume is the finish line in getting my extension migrated to vite. Unfortunately, I am having a very difficult time figuring out where the root problem is at.
TL;DR; popup.popup.html is getting built twice. Once at popup.html with expected contents, and once at popup/popup.html with "empty" / placeholder contents. If I flatten the folder structure, the latter / useless one wins.
Directory structure:
- popup/popup.html
- manifest.json

manifest.json
{
  "manifest_version": 3,
  "action": {
    "default_popup": "popup/popup.html"
  }
}

(essentially the same as this e2e test... which works for me... but I still cannot get my plugin to):
https://github.com/aklinker1/vite-plugin-web-extension/blob/2517ce065d3264c93b0c9e5a5796f3c905796c4a/packages/e2e/e2e.test.ts#L69-L77
build log
[vite-plugin-web-extension] Building HTML Pages in Multi-Page Mode
✓ 1 modules transformed.
Generated an empty chunk: "popup/popup"
../dist/other/icon.xcf       43.14 KiB
../dist/other/icon_128.png   9.81 KiB
../dist/other/icon_48.png    2.52 KiB
../dist/popup.html           0.23 KiB
../dist/popup/popup.html     0.03 KiB

Note that there are two output popup.html files... one with my actual contents (dist/popup.html) and another (dist/popup/popup.html) with contents: export default "/popup.html".
Unfortunately, the path pointed to by the extension is popup/popup.html, so my extension is not usable. No foray through several iterations of additionalInputs, different file structures, verbose logging, rollup options, etc. have been helpful. Further, if I change or flatten the folder structure, it seems that the blank popup.html is generated last / wins with a message "popup.html" overwrites a previously emitted file of the same name.
I have tried different versions of vite in the 3.0 line, and it seems to affect both 3.1 and 3.2. I have seen some related-ish looking activity on vite lately though - maybe I will try the e2e tests with newer versions of deps.
https://github.com/vitejs/vite/pull/9928
Any ideas how to keep debugging / resolve this "double build" issue?

NOTE: in case it is helpful - I am also using some other deps, so it is possible something else is involved here too:
  "dependencies": {
    "@vitejs/plugin-vue": "^3.1.0",
    "events": "^3.3.0",
    "path": "^0.12.7",
    "pouchdb": "^7.3.0",
    "pouchdb-browser": "^7.3.1",
    "pouchdb-core": "^7.3.1",
    "pouchdb-node": "^7.3.1",
    "process": "^0.11.10",
    "vite": "~3.1",
    "vite-plugin-chrome-extension": "^0.0.7",
    "vite-plugin-vuetify": "^1.0.0-alpha.17",
    "vite-plugin-web-extension": "^1.4.4",
    "vue": "^3.2.39",
    "vuetify": "^3.0.0-beta.11"
  }

And vite.config.ts
import { resolve } from "path";
import { defineConfig } from "vite";

// @ts-ignore
import webExtension from "vite-plugin-web-extension";

import vue from '@vitejs/plugin-vue'
import vuetify from 'vite-plugin-vuetify'
import * as path from "path";

export default defineConfig({
    root: "src",
    logLevel: 'info',
    resolve: {
	    alias: {
		    "@": resolve(__dirname, "src"),
	    },
    },
    build: {
        minify: false,
        outDir: path.resolve(__dirname, "dist"),
        emptyOutDir: true,
    },
    plugins: [
        webExtension({
            manifest: "src/manifest.json",
            assets: "other",
        }),
    	vue(),
        vuetify({autoImport: true}),
    ],
})

More bad-ish news (for me). I migrated to using the budding/beta v2 version (vite-plugin-web-extension@next) and am still seeing the same behavior.

Ugh. After all the digging I did, starting a repository from scratch is not illustrating this behavior... 😭
Through a bunch of diffing / tweaking / comparing, the issue came down to this benign-looking line in my vite.config.ts, which I excluded above in trying to make the config more palatable... little would I ever have imagined that this line creates this behavior...
assetsInclude: [],

BEWARE the assetsInclude 😱
Here is a trimmed down example - latest commit breaks in this way: https://github.com/colearendt/extensions-example

Sorry this was so hard to debug! I have no idea why assetsInclude: undefined is different than assetsInclude: []. The docs don't hint at anything.
I can forcefully ignore that option inside the plugin, but that might cause issues for someone else down the line who knows how to use that field properly. Instead, if this happens to anyone else, hopefully they can find this issue and the solution works for them.
// vite.config.ts
export default defineConfig({
    ...
-   assetsInclude: someValue,
});

Let me know if you have any other problems!

Thanks, I think that sounds like the right call too! My extension is now happy and healthy - thanks again for the great package!
Part of it feels like this may be a bug in vite too, so I will probably go toss an issue their direction in case it crops up elsewhere 😄

Just a note that this issue was fixed upstream in vite! 🎉
https://github.com/vitejs/vite/pull/10941/files

Nice!


MongoDB transport base

Closes specklesystems/Core#12

Hi @clairekuang! Thanks for this PR. One thing that I'm worried about is that I see no dependencies to the mongodb driver added to the csproj file, maybe that was missed in the git add step?

@didimitrie  forgot to commit .csproj updates! The mongo package reference should be included now

Just passing by to say that we're not merging this yet as we've uncovered a little structural problem of having all the transports inside Core proper: we'll end up having a wee bit too many dependencies!
We're thinking of a way to do organise this to be future proof, and hopefully we'll be able to proceed! (PS: i've started tracking this issue in #36).

Thanks a lot for this PR Claire ✨
As Dimitrie mentioned, we've decided to move transports out of Core to prevent bloating of Core itself as more transports are added over time. We've just merged this change (along with your MongoDB transport) in #38
Closing this PR as the changes have already been merged into master 🚀


Upgrade fixes

Upgrade command wasnt working because IoC was missing
After testing, the upgrade didnt set the web.config, so I added code to handle that too.

Thanks @stuartcrouch
Not sure why the build failed, I'll need to look into that. 😦
Anyway a build is rolling through, should deploy to NuGet as 1.4.1 shortly for you to use.