go get not downloading to src folder

What version of Go are you using (go version)?

$ go version
go version go1.16beta1 darwin/arm64

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/Users/aditya/Library/Caches/go-build"
GOENV="/Users/aditya/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/aditya/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/aditya/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/opt/homebrew/Cellar/go/1.15.7/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/opt/homebrew/Cellar/go/1.15.7/libexec/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="go1.16beta1"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/dc/mpdmt39s2j94rz4w2b9h91_c0000gn/T/go-build1453910353=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
command on terminal "go get go.uber.org/atomic@v1"
or another "go get" command

What did you expect to see?
source files getting downloaded to "$GOPATH/src/"
What did you see instead?
source files were not downloaded to "$GOPATH/src"
but files were downloaded to "$GOPATH/pkg/mod"

I think this is working as intended. See https://tip.golang.org/doc/go1.16#go-command.

I think this is working as intended. See https://tip.golang.org/doc/go1.16#go-command.

Thanks, It helped.


beets: ImportError: "six"

Issue description
After updating to the latest version of the nixos-unstable channel, I found that beets crashes on startup with the following stacktrace:
Traceback (most recent call last):
  File "/nix/store/7jhnkwyidrgmarakhdp4mxx23mv7xp04-beets-1.4.1/bin/.beet-wrapped", line 8, in <module>
    from beets.ui import main
  File "/nix/store/7jhnkwyidrgmarakhdp4mxx23mv7xp04-beets-1.4.1/lib/python2.7/site-packages/beets/__init__.py", line 20, in <module>
    from beets.util import confit
  File "/nix/store/7jhnkwyidrgmarakhdp4mxx23mv7xp04-beets-1.4.1/lib/python2.7/site-packages/beets/util/__init__.py", line 31, in <module>
    import six
ImportError: No module named six

This issue also appears to be present on nixpkgs master branch.
Steps to reproduce
git clone https://github.com/NixOS/nixpkgs.git
cd nixpkgs
nix-build -A beets
result/bin/beet

Technical details

System: NixOS 17.03pre96717.69bee1b (Gorilla)
Nix version: 1.11.4
Nixpkgs version: 17.03pre96799.571cf4f2

cc the maintainers @aszlig @domenkozar @pjones @Profpatsch

Maybe related to the regression I caused (https://github.com/NixOS/nixpkgs/issues/20943). Testing now.

Nope, six was simply missing. I'll push a fix.

Thanks, that fixed it.


Bug fixes to MOF structure tests

@camiloborges @caadam Hey guys - code review when you get a minute. Figured out that some tests were showing false positives so fixed that up then patched up minor issues to do with it.


Add _make_streaming_request, formerly _make_streaming_config.

Since this actually returned StreamingRecognizeRequest, I renamed it to _make_streaming_request.

Also just squashed.


[WIP][ENH] pull the pipeline's container if it is not found

Closes #

Changes proposed in this pull request:

Checklist (for reviewers)
This section is for the PR reviewer

[ ] PR has an interpretable title with a prefix (e.g. [BUG], [DOC], [ENH], [MAINT])
Refer to NumPy Development Guide for a full list
[ ] PR links to GitHub issue with mention Closes #XXXX
[ ] Tests pass
[ ] Checks pass

For new features:

[ ] Tests have been added

For bug fixes:

[ ] There is at least one test that would fail under the original bug conditions

Not sure if this can help, but boutiques as a cli to pull the container from a descriptor: bosh execute prepare

Not sure if this can help, but boutiques as a cli to pull the container from a descriptor

not sure either: in case the user wants to use datalad then I'd want to do a datalad install of the image but in other cases why not.
need to check

boutiques as a cli to pull the container from a descriptor: bosh execute prepare

This wouldn't help with the current descriptors because they don't use Boutiques' built-in support for containers (Nipoppy injects the Singularity/Apptainer command directly into the descriptor's "command-line" field)


Add an object as input to FindClientByIdAsync method instead of just a string parameter.

I want to get client according to some extra field that I store in my clients table.
By changing signature of the method in IClientStore it be more flexible to implementation .
Task<Client> FindClientByIdAsync(string clientId);
to
Task<Client> FindClientByIdAsync(Client client)

Why and where would you need that?

Task FindClientByIdAsync(Client client)

Uhh, don't you see the problem with this design? I have to create a Client to get the right Client?

@leastprivilege  I needs to query the store with more parameter (e.g tenantId,..). I want to have primary key on clientId and tenantId in the client table.
@brockallen  the parameter is an object to carry out parameter to query the table according the value of it's properties.

What is tenant specific about your client?

How would we know about your custom fields then?
You need a custom data access API for that.


Add received to Event

As part of data ingestion one interesting element we want to keep track of is when a certain event has been received by the ingestion backend.
This timestamp is not user-controlled like @timestamp and can guarantee us a certain timestamp for event reception, the step before ingestion (which is registered as event.ingested).
This PR adds the event.received field to protobuf Event and modeljson.Event.
This field value will be empty in modeljson.Event if it's not set in protobuf Event.
Tests have been adjusted to account for the additional field.

@kruskall No worries and thanks for catching the wrong test!


treats InstanceLimitExceeded as terminal error

What this PR does / why we need it: this pull treats InstanceLimitExceeded as terminal error. We are limited to running up to 20 on demand. See for more details https://aws.amazon.com/ec2/faqs/#How_many_instances_can_I_run_in_Amazon_EC2
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #183
Special notes for your reviewer:

@alvaroaleman @mrIncompetent here is the list of the errors that might be returned by AWS
https://docs.aws.amazon.com/AWSEC2/latest/APIReference/errors-overview.html
I have just thought we could be proactive and classify some of the errors on the list as terminal but perhaps it will be easier to treat them as they will appear.

does it mean that we cannot run more than 20 instances of certain type ?


[TTNN] Localizing TTNN workarounds on the op

Currently, output workarounds can change the op output layout, which can cause problems if the operand of the changed layout is the input to the op that doesn't define workarounds. For example, imagine this scenario:
module attributes {tt.device = #device, tt.system_desc = #system_desc} {
  func.func @forward(%arg0: tensor<1x128x128x32xbf16, #ttnn_layout>) -> tensor<1x64x64x32xbf16, #ttnn_layout1> {
    %0 = "ttnn.get_device..."
    %1 = "ttnn.to_layout"(%arg0, %0) -> tile output
    %2 = "ttnn.reshape"(%1) -> tile input, tile output
    %3 = "ttnn.empty"(%0) -> tile output
    %4 = "ttnn.to_layout"(%2, %0) -> row major output (transforms %2)
    %5 = "ttnn.to_layout"(%3, %0) -> row major output (transforms %3)
    %6 = "ttnn.max_pool2d"(%4, %5, %0) -> accepts row major input, produces row major output
    %7 = "ttnn.reshape"(%6) -> !!! PROBLEM HERE !!! expects input in tile, but we workaround output to row_major
    %8 = "ttnn.to_layout"(%7) -> moves output to host
    return %8 : tensor<1x64x64x32xbf16, #ttnn_layout1>
  }
}

With this change, we introduce the insertion of the toLayout op after the op if the output workaround changes the output result layout. This contains the workaround effect locally only on the op on which we apply the workaround.
module attributes {tt.device = #device, tt.system_desc = #system_desc} {
  func.func @forward(%arg0: tensor<1x128x128x32xbf16, #ttnn_layout>) -> tensor<1x64x64x32xbf16, #ttnn_layout1> {
    %0 = "ttnn.get_device..."
    %1 = "ttnn.to_layout"(%arg0, %0) -> tile output
    %2 = "ttnn.reshape"(%1) -> tile input, tile output
    %3 = "ttnn.empty"(%0) -> tile output
    %4 = "ttnn.to_layout"(%2, %0) -> row major output (transforms %2)
    %5 = "ttnn.to_layout"(%3, %0) -> row major output (transforms %3)
    %6 = "ttnn.max_pool2d"(%4, %5, %0) -> accepts row major input, produces row major output
    %7 = "ttnn.to_layout"(%6, %0) -> !!! PROBLEM SOLVED HERE !!! transform the layout back to tile
    %8 = "ttnn.reshape"(%7) -> tile input, tile output
    %9 = "ttnn.to_layout"(%8) -> moves output to host
    return %9 : tensor<1x64x64x32xbf16, #ttnn_layout1>
  }
}

I will follow up with proper tests. At the moment I want to get review inputs on the change! :)
Closes #1614

Should %4 be %6 in the first snippet of the PR description?
    %7 = "ttnn.reshape"(%4) -> !!! PROBLEM HERE !!! expects input in tile, but we workaround output to row_major

Yeah, I corrected the IRs, it had errors on few places :)


Different results using same image and same version of tesseract

Creating a separate issue to track this. Earlier discussion begins from
https://github.com/tesseract-ocr/tesseract/issues/1339#issuecomment-377206627
@yurytch commented 28 days ago

'My' results are different from 'yours' (was that to be expected?), not always to the good.

@stweil commented 28 days ago

I would not say no as I can imagine reasons why the same Tesseract version with same traineddata could give different results for the same image. If we can confirm such differences, that is clearly something which needs to get fixed. Results must be reproducible.

Please elobarate the phrase "same image". Because tesseract functions and gives one results on one image with resolution 72dpi and gives some other or slightly different result on the same image with resolution 300dpi and there are many more image pree processing steps and config arguments which may cause variation in the result for same image.

Please read the discussion in the link provided above. It has a copy of the image file and OCR results using the same traineddata file, OEM and PSM, without any preprocessing of image.

Followed it now. I'll once run Tess on your image with best and fast and compare the results with default psm. Can you confirm your png image size? Just bugging me. Is it 1.58 mb?

Just one suggestion to track down this kind of problems (that I had too): compute the MD5 of the file before reading it and the MD5 of the loaded image matrix. I've found that reading the same PNG image multiple times,  intermixed with other image read/write operations, gives me different in memory images (a bug, I suppose).

Seen similar issue. Can provide sample outputs that differ, it sometimes detects different characters. I am guessing whitelisting characters would help, but ideally for the same image, it shouldn't give two different outputs.

@ramannanda9 did you try to compute the MD5 of the images before passing them to tesseract? What os and image format are you using? Which library to read the images?

@stweil Please see issue posted in forum reporting different results on Windows and Linux.
https://groups.google.com/d/msgid/tesseract-ocr/dc5e5804-23a8-4677-b03d-0226a9e21f84%40googlegroups.com

@stweil Please see issue posted in forum reporting different results on Windows and Linux.
https://groups.google.com/d/msgid/tesseract-ocr/dc5e5804-23a8-4677-b03d-0226a9e21f84%40googlegroups.com

@stweil any solution to this issue?

Also see a recent report at https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/tesseract-ocr/PKRDrGa755U/9nqriZLuBwAJ

https://groups.google.com/d/msgid/tesseract-ocr/e0946afd-dbbe-41ea-9741-1bfadeff97f3%40googlegroups.com

Tesseract version:
tesseract v5.0.0-alpha.20191030
leptonica-1.78.0
libgif 5.1.4 : libjpeg 8d (libjpeg-turbo 1.5.3) : libpng 1.6.34 : libtiff 4.0.9 : zlib 1.2.11 : libwebp 0.6.1 : libopenjp2 2.3.0
Found AVX2
Found AVX
Found FMA
Found SSE
Found libarchive 3.3.2 zlib/1.2.11 liblzma/5.2.3 bz2lib/1.0.6 liblz4/1.7.5
OS:
Windows 10

There is the same version of tesseract on the two systems as i mentioned before.

Both AVX and AVX2 are enabled on both the systems.

I am not using specific tessdata_fast or tessdata_best. I am using the default eng.traineddata that comes with windows installer.

The file size of eng.traineddata is same - 3.92MB.


Feature request: Mirror racks for rack elevation in rear view

Just installed the software and i'm loving it with one visual exception:  It would be nice to have an option to display the rack elevation view mirrored when we are looking at the back view.  I spend most of my time behind my racks and in the current view, I can only look at the the way they are positioned (L-R) in the front view and switching to back view shows me the back of each rack but they are out of order for how I am used to looking at them in real life.
Hope that makes sense.
Basically I would like an option for rack elevation views to look like this:
Front view:
[A-1]   [A-2]   [A-3]   [A-4]
Then back view:
[A-4]   [A-3]   [A-2]   [A-1]
I searched open and closed requests and did not see anything like this.  Also, this is my first github anything, so please go easy on my ignorance!

Issue type
[X ] Feature request
[ ] Bug report
[ ] Documentation

Environment

Python version:  3.5.2
NetBox version:  2.2.6

Description

I too would like a view to see multiple racks in a view. Generally a DC is organized in rows of racks. Perhaps a designation between Site and Rack needs to be created, called "Row"? Then you can have a "Row View", which would show fronts and backs as mentioned. Another way to do it is have a button to display the fronts, or the backs, which limits how busy the screen will get.

@jasonguy Are you talking about something different than elevation view?  That shows you the racks in a row.  I'm just looking for a small feature WITHIN that view.

@chrispcall My mistake. I had not created multiple racks yet. I agree that the "rear" view should be reversed, as if you "walked around the back", everything would be reversed left to right. Good idea...I deleted my useless comment. :)

Rather than simply flipping the ordering, we probably want to expose a way for the user to choose how the racks are sorted. (This is accomplished in most list views using django-tables' built-in RequestConfig(), which allows sorting by column header.)

Since this feature request was accepted we're wondering when it's going to be implemented.
Any news on this? This doesn't sound to difficult to do but I may be wrong.

We'd like for this feature to accomplish 2 things.

Allow you to specify the sort order per rack group.  For example, if we number racks based on their relative position to a defined wall then opposing rows would have 1-4 going left to right and opposite row would have 1-4 going right to left

back       front       back
[1]           [1]
[2]           [2]
[3]           [3]
[4]           [4]

Reverse specified sort order when selecting "rear" option.  This would allow you to retain the physical layout of the rack and you look at it from the back.


fix: 24261 user able to select 2 emoji at a time

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/24261
PROPOSAL: https://github.com/Expensify/App/issues/24261#issuecomment-1671191476
Tests

Tap on a report
Tap on emoji picker in compose box
From smileys&emotion section, select any 2 emoji
The user should be able to select only one emoji at a time

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

Offline tests

Same as above
QA Steps

Tap on a report
Tap on emoji picker in compose box
From smileys&emotion section, select any 2 emoji
The user should be able to select only one emoji at a time

[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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[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 grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is 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] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[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 the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[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/113963320/986b7179-f8fd-43ad-bc9d-875c0f73d777

Mobile Web - Chrome

https://github.com/Expensify/App/assets/113963320/84326b4d-bed3-47ab-a60d-ddb1a9cb1949

Mobile Web - Safari

https://github.com/Expensify/App/assets/113963320/a2f79d17-653b-4ac6-8e54-64cce6889a23

Desktop

https://github.com/Expensify/App/assets/113963320/907f64d6-db95-404e-82fc-e12e5d30a576

iOS

Uploading Screen Recording 2023-08-16 at 15.20.10.mov…

Android

https://github.com/Expensify/App/assets/113963320/acaccec2-c362-4717-85ff-f7eae13269fc

Today, I'll review your PR. I apologize for any inconvenience; a few tasks have piled up on my end.

BTW @tienifr don't we want to wait for merge of your previous issue with useSingleExecution https://github.com/Expensify/App/pull/24173? I believe the conflicts will come out for one of these two

🎀 👀 🎀 C+ reviewed

@tienifr I'm okay with that change 👌🏼 The suggestion looks more inline with the intent of this hook. I've tested it briefly and I didn't find any regression after this change

@marcochavezf bumping as the PR introducing the useSingleExecution hook is already merged

Thanks guys, LGTM

🚀 Deployed to staging by https://github.com/marcochavezf in version: 1.3.63-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.63-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/marcochavezf in version: 1.3.64-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.64-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

Just noting that this PR caused a regression in the emoji picker due to not spreading the params here
https://github.com/Expensify/App/blob/d494433a80ff82f588e3888a8da2c527848843e9/src/hooks/useSingleExecution.js#L25
This caused the selected emoji to unexpectedly come through as an array. More details here.


Improve Focus, Remember Menus, T-State Logger Toggle

improved emulator focus (canvas focus on window focus, and on refresh)
remember what menu items are open
improved menu open/close
enable/disable the t-state logger (ie; writing to 0x86)
remove unnecessary console.log for uart and smooth

Thanks a lot, it's merged!


Does Alibaba Cloud have a test tool like localstack?

I want a local test environment,  just like https://github.com/localstack/localstack

https://github.com/aliyun/oss-emulator
似乎已经被弃了


The error Control labeled "Metrics" cannot be empty should not appear on the first time goes to chart screen by pressing table name

The validation works unexpected with my below steps to reproduce
Expected results
The error "Control labeled "Metrics" cannot be empty" should not appear when delete Metrics
Actual results
The error "Control labeled "Metrics" cannot be empty" appears when delete Metrics, but it not happens after refresh page
Screenshots

#### How to reproduce the bug

Go to 'Sources/Tables'

Click on 'a table name'

It goes to chart screen, with Table type

Delete Metrics COUNT(*)
=> It's show the error similar to attachment.

Try to select Columns on NOT GROUP BY or anything
=> The error not disappear

Refresh page, and try to delete Metrics COUNT(*) again
=> The error does not appear

Environment

superset version: Master branch on 2019, July 23
python version: 3.7.3
node.js version: 8.16.0
npm version: 6.4.1

This looks like a duplicate of #7363 which has a hint of why this is happening, but was closed due to inactivity

+1 on this. I am able to skirt around the issue by first defining "Not Grouped By" columns, and then clearing the 'Metrics' field.

the workaround I found is the following:

In the Section "Group By":
fill in the fields
1.a)  "Group By" with any available value
1.b)  "Metrics" with any available value
In the Section "NOT GROUPED BY":
fill in the fields that you target to use ( as "Columns")
Click on the button "Run Query" --> error message indicating that you can´t combine both "Group by " and "NOT GROUPED BY" fields
Clear the fields of the section "Group by" --> keep only the target fields
Click on the button "Run Query" --> OK

I found out that changing Visualization Type forth and back to Table clear the error for me.

This bug makes Superset unusable for me.  I have simple SQL that that reads 3 columns; a timestamp and 2 values.  I can't create a simple line chart and I have no idea how to proceed.


Prevent usage of self ID in modifiers working on bare ID

This allows the construction of otherwise nonsensical trees which might lead to unexpected panics further down the road.
This could be a fix for #35 but this is admittedly speculation.

LGTM


refactor: rename confusing 'call' templates

There are x:call-scenarios, x:generate-calls and x:output-call templates in the XSpec code base. Their names are very confusing:

They have nothing to do with x:call.
They work closely together, but their names do not signify it explicitly.
What is the difference between generate and output?
x:call-scenarios calls not only scenarios but also x:expect.

What they actually do is generating XSLT/XQuery instructions which invoke the compiled instances of x:scenario and x:expect.
So, to disambiguate those templates, this pull request renames them as follows:

old
new

x:call-scenarios
x:invoke-compiled-child-scenarios-or-expects

x:generate-calls
x:invoke-compiled-scenarios-or-expects

x:output-call
x:invoke-compiled-current-scenario-or-expect

@galtm
Can you review this?
If you have another idea of the naming convention, please feel free to propose it.


Initial support for federated learning

Federated learning plugin for xgboost:

A gRPC server to aggregate MPI-style requests (allgather, allreduce, broadcast) from federated workers.
A Rabit engine for the federated environment.
Integration test to simulate federated learning.

Additional followups are need to address GPU support, better security and privacy, etc.
Part of #7778

@trivialfis @RAMitchell @hcho3

Here is the output from running the integration test:
(venv) rou@rou:~/src/xgboost/tests/distributed$ ./runtests-federated.sh
[15:30:05] Connecting to federated server localhost:9091, world size 3, rank 0
[15:30:05] Connecting to federated server localhost:9091, world size 3, rank 1
[15:30:05] XGBoost federated mode detected, not splitting data among workers
[15:30:05] XGBoost federated mode detected, not splitting data among workers
[15:30:05] Connecting to federated server localhost:9091, world size 3, rank 2
[15:30:05] XGBoost federated mode detected, not splitting data among workers
[15:30:05] XGBoost federated mode detected, not splitting data among workers
[15:30:05] XGBoost federated mode detected, not splitting data among workers
[15:30:05] XGBoost federated mode detected, not splitting data among workers
[15:30:06] [0]	eval-logloss:0.22669	train-logloss:0.23338

[15:30:07] [1]	eval-logloss:0.13787	train-logloss:0.13666

[15:30:07] [2]	eval-logloss:0.08046	train-logloss:0.08253

[15:30:08] [3]	eval-logloss:0.05833	train-logloss:0.05647

[15:30:08] [4]	eval-logloss:0.03829	train-logloss:0.04151

[15:30:09] [5]	eval-logloss:0.02663	train-logloss:0.02961

[15:30:09] [6]	eval-logloss:0.01388	train-logloss:0.01919

[15:30:10] [7]	eval-logloss:0.01020	train-logloss:0.01332

[15:30:10] [8]	eval-logloss:0.00848	train-logloss:0.01113

[15:30:11] [9]	eval-logloss:0.00692	train-logloss:0.00663

[15:30:11] [10]	eval-logloss:0.00544	train-logloss:0.00504

[15:30:12] [11]	eval-logloss:0.00445	train-logloss:0.00420

[15:30:12] [12]	eval-logloss:0.00336	train-logloss:0.00356

[15:30:13] [13]	eval-logloss:0.00277	train-logloss:0.00281

[15:30:13] [14]	eval-logloss:0.00252	train-logloss:0.00244

[15:30:14] [15]	eval-logloss:0.00177	train-logloss:0.00194

[15:30:15] [16]	eval-logloss:0.00157	train-logloss:0.00161

[15:30:15] [17]	eval-logloss:0.00135	train-logloss:0.00142

[15:30:16] [18]	eval-logloss:0.00123	train-logloss:0.00125

[15:30:16] [19]	eval-logloss:0.00107	train-logloss:0.00107

[15:30:16] Finished training

@trivialfis I did the CLI because it was easier. :) We can certainly add a C API/Python wrapper if needed. Perhaps as a followup?

@trivialfis I added some unit tests along with the integration test. But the federated learning plugin is disabled by default so they are not being run by the CI. Need to send a followup PR to tweak the CI pipelines to add them. Also I added the C API and the Python wrapper as you suggested.
@RAMitchell what do you mean by the quantile issue? For now the quantiles are still constructed globally using allreduce. We need to do some followup work to enhance the privacy.

@RAMitchell what do you mean by the quantile issue? For now the quantiles are still constructed globally using allreduce. We need to do some followup work to enhance the privacy.

I think we need a plan on how to solve distributed quantiles while preserving privacy. Its hard for me to see how this can be possible with any reasonable guarantees. For example in in small datasets or datasets with few unique values, the quantiles could capture all of the data, so even sharing the final quantiles among workers would represent a significant leakage.

As I mentioned in the RFC, this first iteration is really about putting the basic framework in place so that federated learning can be done in a somewhat high trust, "enterprise" environment. We can then incrementally add more security and privacy features to widen the use case.
For the quantile leakage issue, one possibility is to have each party compute a histogram of different bin sizes depending on the size of the local data, then fuse the histograms at the server, something like https://arxiv.org/abs/2012.06670. This doesn't rely on homomorphic encryption or differential privacy, but of course there are other approaches we can also consider.


iOS Safari is broken

The status page doesn’t render and just shows a white screen, we’re probably missing some guards somewhere for browser APIs that aren’t on mobile (like Notification)
Using iOS + macbook safari to debug should be pretty simple, maybe we could also mock out the lack of APIs in our tests so too

This is due to https://github.com/pytorch/ci-hud/blob/28ec6a2160315fb838202f590eb13d6cadc24c13/src/pr/FailureReport.js#L36
Safari (as well as many other browsers do not support lookbehind/lookahead regexes)


Fix plugin preventing panning

I think this doesn't break the plugin's behavior as far as I could test, so it's fine to not consume the mouse motion in any case.
Close #107

Thanks!


add custom label and  fixes "Not work on my phone"

add custom label and  fixes "Not work on my phone"

https://stackoverflow.com/a/66840274

Labels are included for multilingual processing. Is there any other better way?
https://developer.android.com/guide/topics/ui/accessibility/service
android:label="@string/appName"


Personalized internships command

Make a command that allows the user to select some filters in order to get internships that suits their needs.
For example: if a user wanted all internships that are Summer 2024, has a requirement of Undergraduate (Sophomore), and a certain salary, then the bot should filter by these preferences.

We could maybe experiment with discord.py's button functionality and simply have a forwards and backwards button to load multiple internships en masse.

Can the bot automatically post new internships to the chat when they are posted?

Not yet, that'll probably be towards the end as we'll have to deploy our bot onto a cloud service so that it runs continuously. Right now, it only ever runs whenever we hit "run" on our file.


Show git actions to include also builtin telescope git actions

It would be convenient, in my opinion, to be able to have a single picker for all git actions. Do you think adding builtin telescope git pickers to “show_custom_functions” is a good idea?

Hi, great suggestion.
Can you try out the linked PR?
I made the functionality optional as I personally won't use this. (I'm using lazygit in a floatterm)

Cool, it seems to be working. Thanks!


Feature/contours

Added function to support the detection and drawing of contours

Thanks for the effort.

Wow - so fast
:+1:

:+1: would love to have your contribution in the future!
Thanks.

I just realised that images/shapes.png not used. I'll remove in my next PR.
BTW - Just wanted to say well done on this project, I'm finding it very useful


Generic inference from return type

TypeScript Version:  4.0.0-dev.20200715
Search Terms: generic inference
Code
interface Test<C> {
    title: string;
    test(context: C): unknown;
}
declare function suite<C>(setup: () => C, ...items: Test<C>[]): Test<C>;
declare function describe<PC, C extends PC>(setup: (context: PC) => C, ...items: Test<C>[]): Test<PC>;
declare function it<C>(title: string, test: (context: C) => unknown): Test<C>;

suite(
    () => ({
        a: 'param',
        b: 5
    }),
    it(``, ({a, b}) => {a.charAt(b)}), // <- generic works for first level
    it(``, () => {}),
    describe(
        ({a, b}) => ({a, b, c: true}),
        // it(``, ({a, c}) => {}) // <- uncomment to override generic ({a: any, c: any})
    )
);

Expected behavior:
Inference should work in the same way for describe as it works for suite.
Actual behavior:
Placing the it under the 2nd level triggers the inference in a different way. The difference between them is that in the describe signature the PC generic from the first level is used in the setup function - removing the context: PC from the setup function or just not using it in the actual setup will make both levels work the same.
Playground Link: Playground Link
Related Issues:

Inconsistency in generic parameter inference

Looks like a job for #30134

@RyanCavanaugh , this still doesn't work in the latest/nightly version, is this something that will not get resolved, or just a duplicate?

@idoros it's unlikely this will be changed barring a full redesign of generic inference


Added the possibility to limit which namespaces isto-csr creates configmaps in

Very useful for multitenant environments.
Signed-off-by: Knut-Erik Johnsen<EMAIL_ADDRESS>

/cc @JoshVanL


Feature: Animations

Provide apis for animations. Something like:
AnimatedMix(Mix(
  bgColor(Colors.green),
))

Whenever the Mix is changed, it should be animated.

Or maybe something like
Mix(
  bgColor(Colors.green).animated(Duration(milliseconds: 300)), // ofc there is a default duration
),

I think I know how to do this. Every attribute will have the animationDuration and animationCurve, always with null as default.
Whenever the animated function is called, it sets the animation duration and curve, and the widget will need to handle that. The API will be same as presented above.

@bdlukaa quick question, when would the animation take place. Is that when it's doing a transition between Mix?
The API on AnimatedContainer allows you to pick properties that are animated. I wonder if a higher level class AnimatedMix, would allow to define the animations, and maybe further configuration like duration, curve and so on.

I don't think AnimatedMix would be a good thing. It'd cause much confusion and the simplicity of mix would go away.
On the other hand, I also don't think that bgColor(Colors.green).animated(Duration(milliseconds: 300)) would be good too. It'd cause so much boilerplate code when multiple properties needs to be animated (like an AnimatedContainer). What we could have is:

The following approach will animate separated attributes

Mix(
  bgColor(Colors.green).animated(Duration(milliseconds: 300)),
),

The following approach will animate all the attributes

Mix(
  animated(Duration(milliseconds: 300)),
  bgColor(Colors.green),
),

The following approach will animate only the selected attributes

Mix(
  animated(Duration(milliseconds: 300)),
  bgColor(Colors.green).animated(),
  textColor(Colors.white),
),

I will add also the ability to apply Mixes and account for that. We probably would have to decorate these attributes with an animated attribute that has those animated properties to keep composability.
final simpleMix = Mix(
  animated(Duration(milliseconds: 300)),
  bgColor(Colors.green).animated(),
  textColor(Colors.white),
),

Mix(
  apply(simpleMix),
),

Fixed on #7, #9 and #10


⚠ Fetchers has degraded performance

In 210a474, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 154 ms

Resolved: Fetchers performance has improved in 43ef04b.


Try to resume RocksDB operations after background error

Scope & Purpose
Experimental PR for calling RocksDB's Resume() function after a background error has occurred.
This may fix a few cases of RocksDB going into read-only mode and not automatically recovering from it.

[x] :hankey: Bugfix (requires CHANGELOG entry)
[ ] :pizza: New feature (requires CHANGELOG entry, feature documentation and release notes)
[ ] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification
[x] :book: CHANGELOG entry made

Backports:

[x] No backports required

Testing & Verification

[x] The behavior in this PR was manually tested
[ ] This change is already covered by existing tests, such as (please describe tests).
[ ] This PR adds tests that were used to verify all changes:

[ ] Added new C++ Unit tests
[ ] Added new integration tests (e.g. in shell_server / shell_server_aql)
[ ] Added new resilience tests (only if the feature is impacted by failovers)

[ ] There are tests in an external testing repository:
[ ] I ensured this code runs with ASan / TSan or other static verification tools

No feedback. Closing as obsolete.


Expose special environment variables

e.g. RUNNING_NG_INVOCATION so that benchmarks can write outputs with unique filenames

@tianleq also want benchmark names

Also considering expanding these in modifier val


565 k nn and mpv algorithms gives wrong results

Waiting smoke tests with LPF OK, waiting CIs OK, waiting open issue for simplifying mpv implementation.

Rebased. Code review OK. New issue for improving mpv created. Waiting smoke tests with LPF OK, waiting CIs OK.

RFC made (@anhansson) re automated tests against a trusted external baseline

Many thanks Anders for the update. Review OK. GitHub CI OK.
Waiting internal CI OK, perform full test suite run with LPF before merging

Full test suite run with LPF found a checksum error for com-orkut. Now reconfirmed using Octave -- indeed it was previously missed. Finishing full test suite to make sure this was the only error, and re-running internal CI. Will merge if both OK.

Internal CI failed and in so doing implicitly detected that this MR was no longer based on the latest develop. My bad. Restarting internal CI check.

Internal CI failed and in so doing implicitly detected that this MR was no longer based on the latest develop. My bad. Restarting internal CI check.

All is now OK. Found missing attribution to @anhansson in NOTICE file -- added it, and will now proceed to write merge comments before merging.


How could i set message properties for the 'Approve', 'Reject' allowed values?

How could the allowed values at
https://github.com/jpotts/alfresco-developer-series/blob/master/workflow/workflow-tutorial/workflow-tutorial-platform-jar/src/main/resources/alfresco/module/workflow-tutorial-platform-jar/model/scWorkflowModel.xml#L94
be multilingual?

it works. thank you.


Example

Maybe I could try putting an example for this repo? Whatdyasay @Ujang360 ?

That would be really cool :+1:

:grin:


Suggestion: Add quick sample for ExportToNewSyntax

As the April update blog post includes a sample how to use ExportToNewSyntax with finsql but the June update seems to have removed that functionality (I get an "unknown command" error), I think it would make sense to quickly show how Export-NAVApplicationObject -ExportToNewSyntax works. There is one line on the June update blog post but I am not sure how many are going to read that and I would guess even less will know what to do

The blog post doesn't link to it but here is the documentation page for txt2al:
https://msdn.microsoft.com/en-us/dynamics-nav/newdev-txt2al-tool
I can see it is missing the powershell commandlet description we will try to add that as well.


Test Upgrade: Use V2 ut-core, correct the error handlings in the video device

Updated the changes on comparing the handle with the common marcro DS_ASSERT_AUTO_TERM_NUMERICAL.
Moved the UT_ASSERT_EQUAL into UT_ASSERT_EQUAL_NOT_FATAL.
Moved the UT_FAIL into UT_FAIL_FATAL

 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.

this is already taken care so closing the PR


Cover more test/widgets tests with leak tracking #12.

Description
This PR changes testWidgets by testWidgetsWithLeakTracking in number of flutter/test/widgets tests according to the https://github.com/dart-lang/leak_tracker/issues/134.
Tests

Updates animated_size_test.dart to use testWidgetsWithLeakTracking;
Updates framework_test.dart to use testWidgetsWithLeakTracking;
Updates html_element_view_test.dart to use testWidgetsWithLeakTracking;
Updates list_wheel_scroll_view_test.dart to use testWidgetsWithLeakTracking;
Updates navigator_test.dart to use testWidgetsWithLeakTracking;
Updates overlay_test.dart to use testWidgetsWithLeakTracking;
Updates router_restoration_test.dart to use testWidgetsWithLeakTracking;
Updates scrollable_test.dart to use testWidgetsWithLeakTracking;
Updates transform_test.dart to use testWidgetsWithLeakTracking.

Pre-launch Checklist

[X] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[X] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[X] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[X] I signed the [CLA].
[X] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[X] I added new tests to check the change I am making, or this PR is [test-exempt].
[X] All existing and new tests are passing.

LGTM
Will formally approve and merge it after merging this change to leak_tracker, and upgrading Flutter: https://github.com/dart-lang/leak_tracker/pull/149

@ksokolovskyi , may I ask you to resolve conflicts?

@polina-c, thanks a lot for the review!


Upgrade to latest wazimap version for Python 2.7 end of life

This project is currently running on Wazimap 0.8.2, which uses Python 2.7. Python 2.7 is reaching end of life at the end of 2019. This project should be upgraded to the latest version of Wazimap, which includes an upgrade to Python 3.
There are breaking changes from 0.8.2 to 1.0.0 of Wazimap that will need to be dealt with. There are also breaking changes from 1.X Wazimap to 2.X Wazimap.
I would recommend a stepped approach by upgrading to 1.X and, from there, to 2.X.
Documentation
The Wazimap docs up to version 1.0.0, which documents the breaking changes in 1.0.0: https://wazimap.readthedocs.io/en/latest/version_history.html
The Wazimap repo's changelog that includes the update to 2.1.0: https://github.com/OpenUpSA/wazimap/blob/master/CHANGES.rst

I have updated the dependencies to the most recent version for Python 2.7. The version of wazimap that runs on Python 3 has not yet been published to PyPi. The maintainers are currently working on documentation.
https://github.com/OpenUpSA/wazimap/issues/154

With the latest update, most of the problems with Wazimap 2 seems to be fixed and everything is looking good locally. I'm looking into fixing issues with docker. For some reason, I couldn't connect with the postgresql container from nepal map container (port 5432 wasn't open to nepalmap)  but I got around it using a quick fix for now (which might not be necessary, I'll look into it in detail). I'll report if any major problem occurs.

@cliftonmcintosh I forgot about this. Is anyone working on this? I have upgraded Nepalmap to Python 3.7 and Wazimap 2.1.2 (along with a few dependency upgrades). I have tested the docker builds (dev/stage/prod) and everything seems to be working fine (except for the "use my location" feature, but it doesn't seem to work on the current nepalmap.org as well). Should I submit a PR? Are there more tests I can use to validate if everything is working correctly?

@divyamani1
Hello. I am no longer active on this project, and I am not sure what the appropriate steps are for proceeding. There may be someone in C4N who is working on the project and can provide advice. You might try the C4N Slack for getting advice.

@divyamani1 great, thanks for working on this.  yes, can you submit a PR for this issue? I can review it. Since the "use my location" feature is not working on the current nepalmap.org too, we can create a diff issue for that and track/work on it.  Not sure, if you've already joined C4N slack channel.. if not you can find the link here. We can further discuss regarding the use my location and the update wazimap issue there.


Add exported members of all project files in the global completion list

Port of #19069

no need for a port. i merge master into 2.6


[2012-06-02] Models with namespaces are not recognized with "use \DataObject;"

created by: fab
created at: 2012-06-02
original ticket: http://open.silverstripe.org/ticket/7422

This code works:
namespace Acme\Model;

class Foo extends \DataObject { }

This not (no table created):
namespace Acme\Model;

use \DataObject;

class Foo extends DataObject { }

Possibly fixed with https://github.com/silverstripe/silverstripe-framework/pull/3899

*definitely fixed with #3899

fixed

Yay good job.


Improve pay-to-open errors

Users have reported issues with pay-to-open and automatic retries.
Let's imagine for example that Alice sends an HTLC to a new Phoenix user:
Alice -> X -> ACINQ -> Phoenix

If Phoenix rejects the pay-to-open request, Alice will see an onion error from ACINQ. Since ACINQ is an intermediate node, Alice may retry the payment.
When Phoenix rejects the pay-to-open, this should appear as Alice as a recipient failure (and thus prevent retries). That means that Phoenix needs to obtain some onion information in the PayToOpenRequest and provide a correctly encrypted onion error in the PayToOpenResponse.

That has been implemented (a while ago already).


fix sysctl ip_forward example in README

As written previously, the line added to /etc/sysctl.conf is actually
net.ipv4.ip_forward=1=1

which is invalid

Thanks, good catch! I'll merge this in tomorrow.

Since this is a README change, not worrying about the tailscale CI and overriding for merge


Updating the quick-start docs

Fixes #2201

@mcollina, PTAL and lemme know if more changes are required.


Project status

Hello,
What is the current status of this project? it looks very promising but looking at the history there doesn't seem to be a lot of activity and its very cumbersome to use since its not published to nuget and the instructions are somewhat lacking.

Thanks for your interest here. We're working on improving the usability by adding Nuget packages and the instructions will be updated in sync.
We recently added the "simulated hardware" provider to allow for app development/debugging when using the actual hardware is inconvenient. Beyond the improved usability of what we have, were there other improvements/additions you were hoping for?
Thanks,
Jesse

I think the prime points of improvement would be nuget publishing and docs, its such a shame that you're doing all this work and its so hidden away. Being able to do closed loop and high perf timing (via interrupts) is super useful.
Its also a little confusing that this library has a dependency to arduino, you mentioned in another issue that you were thinking about factoring that out and i agree with that

We've completed another round of refactoring.
The code for the Lightning providers has moved to the Lightning repository, while the binaries (for all Lightning SDK components) are now included and published as part of the latest Lightning SDK Nuget package.
So, apps that need Lightning only need to reference that Nuget package (plus update their AppX manifest). We're working on updating our docs as well.


Make CPS compatible with ground units

Tested after a slight refinement to idle unit detection to allow this. The changes and updated Asset_Pools_Example.miz are included in the Latest version.


[Migration]: upgrade pydantic to v2 with sdk compatibility

Description
This PR improves compatibility with the latest version of Pydantic (v2), ensuring the SDK remains up-to-date.
Changes done:

Improved and ensured the SDK types are compatible with pydantic>=2.
Updated function_signature to handle type annotations to allow fastapi to translate SDK type.
Refactored override_schema to align with Pydantic v2 schema definitions.
Updated the behaviour of the getBodySchemaName function in openapi_parser.ts to return the appropriate schema $ref due to the upgrade to Pydantic version 2.

Minor Changes done:

Updated Docker templates in docker-assets/ to ensure agenta installation precedes application dependency installation.

Hi @mmabrouk,
If you'd like to test the oss served app with the changes in this PR, please see here.  I made some minor frontend changes, so serving to beta (or any environment) won't work without them.
I have also deployed to cloud.beta for internal QA.

Hi @bekossy,
Incase you missed this, could you please look into the Cypress failing test? The app created isn't starting. I believe it has something to do with me changing the SDK. Can you please confirm if my assumption is correct? Thank you.

@aybruhm I was able to reproduce the issue and it turns out that it is from the code and not the tests
I ran the docker-compose.test.yml file and created a new app from the UI but got stuck here

@aybruhm I was able to reproduce the issue and it turns out that it is from the code and not the tests I ran the docker-compose.test.yml file and created a new app from the UI but got stuck here

Thanks, @bekossy! I've reproduced the issue. Could you please pull and test again? I've fixed the problem. @mmabrouk, the issue was the body schema of the LLM application that was created from the UI. Here it is:

It turns out that the body schema for an LLM app created from the UI is different from the one created from the CLI.
Next steps for QA:

Create and run an app locally from the CLI and UI using the current agenta version (with pydantic v1).
Checkout this PR branch and repeat the above steps. Before creating an app from the UI, update the backend environment variable AGENTA_TEMPLATE_REPO to stage_templates and start the Docker Compose.

@aybruhm I was able to reproduce the issue and it turns out that it is from the code and not the tests I ran the docker-compose.test.yml file and created a new app from the UI but got stuck here

Thanks, @bekossy! I've reproduced the issue. Could you please pull and test again? I've fixed the problem. @mmabrouk, the issue was the body schema of the LLM application that was created from the UI. Here it is:

It turns out that the body schema for an LLM app created from the UI is different from the one created from the CLI.
Next steps for QA:

Create and run an app locally from the CLI and UI using the current agenta version (with pydantic v1).
Checkout this PR branch and repeat the above steps. Before creating an app from the UI, update the backend environment variable AGENTA_TEMPLATE_REPO to stage_templates and start the Docker Compose.

I would say instead of trying to use the templates. A much easier solution is to serve applications from the CLI using the poetry shell with agenta pointing to this branch, then again with the CLI using the production branch and make sure that everything is working.
Specifically:

[ ] All types of parameters are shown and work (for this we should serve both the chat application and the single prompt application as they have all types of parameters)
[ ] The application can be used from the playground (generate endpoint) and in production using the endpoint shown under deployments (after publishing the application). We need to make sure that the deployed endpoint has the correct version of the configuration. For this please change the prompt dramatically (e.g. add answer only in chinese) then deploy the application

Everything LGTM! 👍🏾


Fix duplicate find-implementations button

Fixes https://github.com/sourcegraph/sourcegraph/issues/28973
@tjkandala Is this what you had in mind when you said "Could they check that the current language also matches the extension's language?"?

Yeah I think this is the idea: If two different hover find-implementations actions are loaded but we hide those with the language not active, we shouldn't be seeing the issue. cc @tjkandala
I tried to repro the issue with your changes following the extension dev guide but it seems like Find implementation isn't showing up at all now:

Maybe this has to do with the extension having the name template instead of being language specific. Even if this would, we would likely not be able to repro the issue unless we install two language-specific extensions:

If you have some ideas on how I could verify that this fixes the issue, I’m happy to dig in!

@philipp-spiess I ran into the same problem just now (and your comment popped up while my comment was sitting here in the text box). Locally I changed the LANGID in the package.json to go to test this.
I get the button then but I can also reproduce the original issue. Not sure if that's due to the "template" language being active on all languages and the Rust extension also still being active?

If I disable the "Rust" extension on Sourcegraph.com ("Go" was already disabled) and sideload the extension from localhost with LANGID in the check replaced with go it seems to be fixed? But again: not sure whether that's due to funky local setup.

@philipp-spiess I ran into the same problem just now (and your comment popped up while my comment was sitting here in the text box)

Ahaha great minds 🙂

I get the button then but I can also reproduce the original issue. Not sure if that's due to the "template" language being active on all languages and the Rust extension also still being active?

So to repro, you jumped from Go -> Rust or from Rust -> Go?
I believe to test that this is fixed we need to switch from the sideloaded extension to a default one (or sideload both). So maybe you can try to set the LANGID to rust instead and only disable the sideloaded extension?

To repro I followed the exact steps here https://github.com/sourcegraph/sourcegraph/issues/28973#issuecomment-1014695100 after disabling with extensions ("Go" and "Rust") locally and side-loading template (which I think acts as if it's available for every language?)

To repro I followed the exact steps here sourcegraph/sourcegraph#28973 (comment) after disabling with extensions ("Go" and "Rust") locally and side-loading template (which I think acts as if it's available for every language?)

I think the problem is that with this approach, we only register one extension but for the issue to reproduce we need two different extensions with the same exported menu items. The console would need to show Activating Sourcegraph extension: template twice.

Ahh, I see. Maybe we can generate the actual extensions locally and serve them?

@tjkandala Is this what you had in mind when you said "Could they check that the current language also matches the extension's language?"?

Yes, fix looks good 👍

Ahh, I see. Maybe we can generate the actual extensions locally and serve them?

Probably the best (only?) way to confirm that it works!

Local repro steps are tricky. We can't use the usual yarn --cwd template run serve because it doesn't replace 'LANGID' in template/package.json, so resource.language == 'LANGID' is always false, which is why you don't see the "Find implementations" button. I'm going to change the local dev scripts so we don't hit this snag in the future.
Here's what I did

Generate and serve the rust extension:

yarn run generate --languages=rust
cd generated-rust
yarn run serve

Sideload it
Set { "extensions": { "sourcegraph/rust": false } } in settings https://sourcegraph.com/users/chris/settings
Visit a Rust file
Navigate through Sourcegraph to a Go file (you can't refresh the page, you have to stay in the SPA)
You should see 1 "Find implementations" button

Prior to this video I deleted resource.language == 'rust', then during the video I restore it and show that it prevents showing duplicate buttons:
https://user-images.githubusercontent.com/1387653/150415462-f95efc80-ab50-492e-b87c-b08406311fe1.mp4


Memory leaks after evaluation

Hi!
I am observing CPU RAM memory leaks when training RT-DETR with PyTorch on multiple GPUs after the first evaluation. After that, the RAM usage increased from ~30GB to ~100GB, and continously increases further (and slows down training due to using swapfile). Do you have any ideas what could be the reason for this?
Thanks!

I rerun rtdetr-r50 on coco dataset, there is a similar phenomenon to what you said, but my machine has 600G ram.  I don't know what problem caused it yet.
epoch RAM(G)
01     66
15     114
36     125


Increase min.insync.replicas to 2 For New Topics

With V2, all of our topics have "all" enabled for acks. Setting the min.insync.replicas to 2 will guarantee for each new topic that the data has been replicated to at least 2 locations before the ack is sent. With "all", it is still possible for all replicas to be out of sync and thereby only the leader receives the data. This setting will force all insync replicas to get it, and guarantee that there are at least 2. Possibility of increasing latency, but also increases safety.

I verified that the E2E tests fail without the env variable for min insync replicas (there is only 1 node when running the project locally so the default of 2 can never be satisfied). Once I added the ENV for local running to be 1, it succeeded, as expected. We will need to watch closely as we deploy to stage to make sure that the process is working there too.

Also, we need to make an announcement about our users needing to git pull on their dp-composer as well as docker-compose pull if they want their stuff to continue working properly.


Add employment status question to DOS buyer journey

HMRC has strongly encouraged Public Sector Bodies (PSB)  to advertise roles as inside or outside IR35 in order to set the expectations of suppliers from the outset. The  HMRC off-payroll rules come into force in April 2021. As such, the DOS team has determined that all published (outcomes and specialist) opportunities will need clear indication if they are inside or outside of IR35.
Add a new question into the buyer journey that asks our buyers the IR35 status of an opportunity.
The wording of the question has been approved by CCS and the Tax Centre of Excellence at HMRC - see https://trello.com/c/apbMZmVd/12-5-confirm-wording-for-the-new-ir35-question
https://trello.com/c/aIJAqcQ4/954-3-allow-briefs-to-store-the-answer-to-the-new-ir35-question and
https://trello.com/c/l9lnd1GD/955-2-add-new-ir35-question-to-the-create-an-opportunity-journey

Releasing this will be a bit tricky because it's going to a live framework. To do it without breaking things, we'll need to release the API changes first, then merge the new frameworks version into the briefs FE and the buyer FE and release those.


Correct the latency histogram factor.

Why the min value of histogram is set to 2000?

I don't the latency will less than 2000us.

Why the min value of histogram is set to 2000?

I don't think the latency will less than 2000us.

It definitely will.
suggestion: 100000(buckets), 0(ming), 10000000(max)

Why the min value of histogram is set to 2000?

I don't think the latency will less than 2000us.

It definitely will.
suggestion: 100000(buckets), 0(ming), 10000000(max)

If concerning the memory consumption, they could be set to 50000, 0, 5000000

Why the min value of histogram is set to 2000?

I don't think the latency will less than 2000us.

It definitely will.
suggestion: 100000(buckets), 0(ming), 10000000(max)

Set to these.

Why the min value of histogram is set to 2000?

I don't think the latency will less than 2000us.

It definitely will.
suggestion: 100000(buckets), 0(ming), 10000000(max)

If concerning the memory consumption, they could be set to 50000, 0, 5000000

It is better to enables it to let the user configure?

 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.


Fix pipeline status when restarting the server #130

Fixed Issue #130.
Signed-off-by: Avishrant Sharma<EMAIL_ADDRESS>

@tdruez @AvishrantsSh gentle ping... what's left to do to finish this?

@pombredanne This is an incomplete solution, see https://github.com/nexB/scancode.io/issues/130#issuecomment-860731952 for details.
I think we should close this PR.

Closing for now, see https://github.com/nexB/scancode.io/issues/130 for discussion.


Action inputs generation and retrieval implementation

This PR implements:

generic action inputs generation code path (could be used by other actions)
partial retrieval action execution (generates the parameters, actual retrieval still TODO)

Associated Dust app for inputs generation is here: https://dust.tt/w/78bda07b39/a/f4816b1e13
Notes: I follow the error handling convention we agreed upon here. Result whenever we act on the error condition. Throwing means unrecoverable (but there is no throw here).

@PopDaph post-merge review welcome


--cert-email doesn't work for keyless signatures

First, sign some blob keylessly:
$ export COSIGN_EXPERIMENTAL=1
$ cosign sign-blob /dev/null --output-certificate /tmp/null.crt  --output-signature /tmp/null.sig
[...]

Now verify:
$ cat /tmp/null.crt \
        | base64 -d \
        | step certificate inspect - \
        | grep -A1 "Subject Alternative Name"
X509v3 Subject Alternative Name: critical
<EMAIL_ADDRESS>$ cosign verify-blob /dev/null --cert /tmp/null.crt  --signature /tmp/null.sig --cert-email<EMAIL_ADDRESS>&& echo "yay!"
[...]
yay!

Looks like it confirmed the subject in my cert! Or did it...?
$ cosign verify-blob /dev/null --cert /tmp/null.crt  --signature /tmp/null.sig --cert-email<EMAIL_ADDRESS>&& echo "that wasn't supposed to happen"
[...]
that wasn't supposed to happen

The help for --cert-email is:

the email expected in a valid Fulcio certificate

So I'd expect it to require a matching email. If I'm misunderstanding, I think (1) the help should be updated, and (2) cosign should warn if it's going to silently ignore the flag.

taking a look

Oh that's a subtle bug, good find. When the certificate flag is provided for verify-blob, we're only calling the function to unpack and validate the certificate when a chain is also provided - https://github.com/sigstore/cosign/blob/main/cmd/cosign/cli/verify/verify_blob.go#L124
Compared to when no certificate is provided and the cert is fetched from Rekor, which always calls this - https://github.com/sigstore/cosign/blob/main/cmd/cosign/cli/verify/verify_blob.go#L152-L166 and https://github.com/sigstore/cosign/blob/b649926565859155d11de082830a781338d5f790/cmd/cosign/cli/verify/verify_blob.go#L210
cosign verify has the same issue. When a cert is provided, it'll only validate the values of the cert if a chain is provided. If using the experimental mode when a cert is fetched from the OCI annotation, it works as expected.


ztunnel build fails because of "Unable to update https://github.com/howardjohn/boring/?branch=hyper-boring/adopt-hyper-1.0.0#5185311a"

I want to build ztunnel 1.19.4 binary with cargo build --release but it failed with below errors.
cargo build --release
Updating git repository `https://github.com/howardjohn/boring/`

error: failed to get boring as a dependency of package ztunnel v0.0.0 (/root/ztunnel)
Caused by:
failed to load source for dependency boring
Caused by:
Unable to update https://github.com/howardjohn/boring/?branch=hyper-boring/adopt-hyper-1.0.0#5185311a
Caused by:
object not found - no match for id (5185311af8addc6851a48bd5747ec634dbb72811); class=Odb (9); code=NotFound (-3)

Cannot reproduce, do you need to clean cache?

@hzxuzhonghu
Did you try to reproduce in version 1.19.4. Because I tried in the 1.20.0, it works.
This commit id 5185311af8addc6851a48bd5747ec634dbb72811 really doesn't exist in the branch "hyper-boring/adopt-hyper-1.0.0"

Yes, on 1.19

Do I need to modify the Cargo.lock file?

I got the same error while trying to compile tag 1.19.4, the commit 5185311a is indeed not exist @howardjohn

Do I need to modify the Cargo.lock file?

I had tried to use the newest commit of the branch hyper-boring/adopt-hyper-1.0.0 which full SHA is 423c260d87b69a926594ded0dd693b5cf1220452(also change version to 5.0.0), then a dependency conflict error appears:
$ BUILD_WITH_CONTAINER=1 make build
cargo build
    Updating git repository `https://github.com/howardjohn/boring/`
    Updating git submodule `https://github.com/google/boringssl.git`
    Updating git submodule `https://github.com/google/boringssl.git`
    Updating git repository `https://github.com/howardjohn/hyper-util`
    Updating crates.io index
error: failed to select a version for `hyper`.
    ... required by package `hyper-boring v5.0.0 (https://github.com/howardjohn/boring/?branch=hyper-boring/adopt-hyper-1.0.0#423c260d)`
    ... which satisfies git dependency `hyper-boring` (locked to 5.0.0) of package `ztunnel v0.0.0 (/work)`
versions that meet the requirements `^1.0` are: 1.0.1, 1.0.0

all possible versions conflict with previously selected packages.

  previously selected package `hyper v1.0.0-rc.3`
    ... which satisfies dependency `hyper = "=1.0.0-rc.3"` (locked to 1.0.0-rc.3) of package `hyper-util v0.0.0 (https://github.com/howardjohn/hyper-util?branch=h2-timer-expose-exec#b9eaeca8)`
    ... which satisfies git dependency `hyper-util` (locked to 0.0.0) of package `ztunnel v0.0.0 (/work)`

failed to select a version for `hyper` which could resolve this conflict
make[1]: *** [Makefile.core.mk:11: build] Error 101
make: *** [build] Error 2

seems the hyper-boring  is also needed by another dependency but they referenced different version.

Cannot reproduce, do you need to clean cache?

maybe the 5185311af8addc6851a48bd5747ec634dbb72811 exist in your local cache?

should be fixed now, sorry about that. We will be off of my forks soon

related to https://github.com/istio/ztunnel/pull/726


[fuse3] [fusell] Add missing flags argument to rename callback

flags may be RENAME_EXCHANGE or RENAME_NOREPLACE. If
RENAME_NOREPLACE is specified, the filesystem must not
overwrite newname if it exists and return an error
instead. If RENAME_EXCHANGE is specified, the filesystem
must atomically exchange the two files, i.e. both must
exist and neither may be deleted.

I also added an intermediary fuse_rename function that drops the extra argument for backwards compatibility

Actually, this seems to be a backward-incompatible change on fuse 3 (And I assume we are sticking to fuse 2.9 on this project)

@paulo-raca just re-opening this so we don't loose sight of it. We probably discuss the possibility of fuse3 support. (Unless there's another binding that is already doing that)
I added a tag [fuse3] to make it more obvious what this is targeting.

Doesn't look like fusepy will support fuse3, closing


Original VBA FizzBuzz solution

This pull request adds an original VBA solution of the FizzBuzz problem in response to Issue https://github.com/NLDev/Hacktoberfest-2020-FizzBuzz/issues/3:

FizzBuzz.vba: an original solution.

neat! thanks :)


pandas format (as default one day)

Most of the time, right after pulling data as the result of a query, most people will create a pandas.DataFrame. Couldn't we provide an option (df=True) as openaq does? It saves a lot of time AND points people to the direction of pandas, which would encourage plotting, quick transition to DBs, excel, etc.

pd.DataFrame(query1) should be work fine.


Implement bar texts (issue 34)

This PR implements attributes textposition, textfont, insidetextfont and outsidetextfont for bar traces.
I've followed this comment as close possible:

all these attributes accept arrays
default textposition is none
if textposition was set to auto, the inside options is preferred over outside
if outside was requested, but the bar is stacked under another bar, then the text is drawn inside
if inside was requested, but the bar is too small, then no text is drawn

I've also added jasmine tests and mocks exercising the new functionality.

all these attributes accept arrays

very nice

default textposition is none

yes :+1:

if textposition was set to auto, the inside options is preferred over outside

I vote :+1: on that

if outside was requested, but the bar is stacked under another bar, then the text is drawn inside
if inside was requested, but the bar is too small, then no text is drawn

answered in https://github.com/n-riesco/plotly.js/pull/4#pullrequestreview-7683700
@n-riesco I'm pretty excited about this. Once again, you'll make a bunch of users happy!

@etpinard @alexcjohnson
The PR is ready for review again:

I've moved the code to coerce array elements from Bar.supplyDefaults to Bar.plot.

I've changed the attributes textfont, insidetextfont and outsidetextfont so that now they accept arrays in family, size and color.

I've revamped the algorithm to position bar labels:

inside labels:

are drawn near the corresponding bar end
with a 3px padding (if the bar is too small, no padding is used)
are rotated counter-clockwise if this results in a larger label

outside labels:

are rotated clockwise or counter-clockwise so that they are laid along the bar end
laying the label along the bar end can result in tiny labels
I think we should rotate outside labels, in those case where otherwise they would be shrunk beyond a certain limit

The following mocks show best how the new positioning algorithms work:

@n-riesco great. I'll give this a look in the next few hours. Thanks!

@alexcjohnson I've updated the rotation algorithm. See the images below:

now rotations are always 90 degrees clockwise
in the case of outside labels, I'm still preventing rotation if this results in a label being perpendicular to the bar
I've changed the labels in the first plot from "0.5" to "50%" to ensure that the text width is larger than the height (unfortunately, this wasn't case in the baseline images, and it was hard to reason why the inside labels had been rotated)
I've also swapped textposition in the first plot, so that trace1 shows rotated outside labels (the case I think is the least favourable for clockwise rotation)

Questions before I continue:

do you like the results of the new criteria?
do you still think that I should change the criteria for the 'auto' mode?

@n-riesco the rotation algorithm is better but I still think for both horizontal and vertical bars the first choice should be horizontal text, and you only rotate it if horizontal is squished and vertical is (less) squished. That means that really the only time you would end up rotating text on horizontal bars is when inside is explicitly specified and the bar size is small enough that it's thinner than a square.
And again, in bar_attrs_relative I don't see why "outside text" in trace 1 is outside the orange bar, it looks like it would be just as big inside the bar, wouldn't it?

@alexcjohnson Thx, that's helped clear my mind a lot.

These are the latest results using these criteria:

auto only draws outside if the result is larger than inside
inside labels are rotated if it prevents excesive shrinkage
outside labels are never rotated
rotation are always 90 degrees clockwise


MRTK Sharing Service Extensions

Describe the problem
MRTK needs a set of sharing services for networked apps.
Describe the solution you'd like
ISharingService
A bare-bones networking service. Initially built on Photon but the interface should support any back-end. Some requirements:

Connects to other devices in a lobby or room
Can send / receive bytes to / from connected devices
Allows devices to specify which types of data they want to receive
Implementation compiles and fails gracefully even if Photon is not installed

Additional Services
A more advanced set of extensions built on the ISharingService extension:
ITimeSyncService
Synchronizes time between connected devices.
IStateSyncService
Efficient, error-free state synchronization. Some requirements:

Makes iterating through shared states easy
Synchronizes complete app state when new devices connect
Can handle merging conflicting states
Uses JsonUtility out of the box but lets users implement custom binary / JSON / BSON serialization methods
Provides optional components to automate detection / application of state changes to objects in scene

IUserSyncService
A user management system built on IStateSyncService - some requirements:

Can assign multiple devices to single 'users' (eg, a single user wearing a HoloLens while using a phone for input)
Allows devs to define what devices 'compose' a user as well as what transforms should be represented / synchronized between devices
Simulates absent users for testing purposes
Reports user readiness for custom lobby systems

IStageSyncService
A stage synchronization system built on IStateSyncService and IUserSyncService that guides users through pre-defined stages of an app. Examples would be a game with connect / loadout / gameplay / scoring stages or a showcase app with lots of slides. Some requirements:

Synchronizes scene loading among multiple users
Smoothly transitions between stages / scenes
Starting / stopping / skipping stages etc.

Describe alternatives you've considered
Continue to use bespoke Photon solutions for each app.
Additional context
These proposals are based on implementations used for sharing apps developed internally. A while ago we opened a PR to incorporate a Photon-based version of a state sharing extension similar to IStateSyncService. That version relied on PhotonView components and didn't mesh well with MRTK service architecture, so it was closed without being merged. The services described would not rely on scene assets to function.

This is long overdue, thank you for purposing/making this!
Some other ideas off the top of my head (some of these might be more appropriate for the transport layer):

Works over LAN and "the internet"
Allows me to run multiple instances of the app locally (on a dev PC)
Position & rotation extrapolation utilities
"Gracefully" handles version mismatch communication
Utilities for data compression
Voice over IP (I've seen good results with the Opus audio codec)
State serialization and recovery from disk

Many of these aren't needed for the first release, but adding them for tracking purposes.

Linking https://github.com/microsoft/MixedRealityToolkit-Unity/issues/3313 for some previous MRTK conversation around this.

Related discussion: #3210

@Railboy What do you propose for addressing this issue in the MRTK? In the HoloLens 2 tutorial sharing chapters, photon is used and a rudimentary abstraction was implemented, with the intention that other sharing platforms could eventually used should the reader decide.

@mr0ng I'm not sure what you're asking, could you clarify your question?

Correct me if I'm wrong @mr0ng, but what I believe he's asking is if someone should:

Replace the Sharing Capabilities sample on docs.microsoft.com to use these new capabilities when they're complete.

or

Add an alternative example on docs.microsoft.com that leverages these new capabilities.

The comments on #7613 are relevant here; currently, our recommendation is to explore the Microsoft Mesh solutions for multi-party XR experiences.


Update sort filter texts on mobile

Description
At search page, on mobile devices, the sort button shows the content of the query (e.g., Sort: latest-desc). I though that by changing SORT to a plain object it would be easier to access the value of the key (the label), without requiring iterating or filtering the entries. Not sure if is the best approach, hope it can be of some help :)
Screenshots

Before
After

Beautiful! Thank you!

hey @lfades 👋! I just made the changes and added a simpler check for the button label as you requested. Hopefully now everything is correct ... thanks =)


Update Quotes.js

PULL REQUEST TEMPLATE
My PR closes #issue_number_here
👨💻 What did you do ?
 added few new quotes.
Note to reviewers

📷 Screenshots

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title and description of the PR is clear and explains the approach.
[x] I have read the contribution guideline properly and following the criteria.

read the contribution guideline carefully and follow the steps


KIC 2.0: customizable ingress class

Make it possible to specify the ingress class that Railgun will be watching - currently it's hardcoded as "kong"

@hbagdi's comment:

Constants.go: KongIngressClass-> confusing name. DefaultIngressClassName is probably a better name. Stylistic minor comment.

Blocked on #1251 as this will have a large bearing on how this functions.

Acceptance Criteria:

[x] the IngressClassName should be configurable via the manager CLI
[ ] the IngressClassName should be plugged into each controller via the controller manager.
[ ] all controllers which cover Ingress and "ingress like" objects supporting the kubernetes.io/ingress.class and/or spec.IngressClassName field should have logic added to properly handle this

Acceptance Criteria (Tests):

[ ] Ingress with no annotation and with no IngressClassName
[ ] Ingress with an annotation not-kongtests
[ ] Ingress with an annotation kongtests
[ ] Ingress with a spec.IngressClassName not-kongtests
[ ] Ingress with a spec.IngressClassName kongtests

This is resolved, however there is follow up that needed to be split off to ultimately remove support for classless ingress:
https://github.com/Kong/kubernetes-ingress-controller/issues/1293
This has been added to the same milestone.


Fix smoke test bug

https://trello.com/c/7J2xuOkC/1249-spike-investigate-smoke-test-failures
Description
Smoke tests were failing due to not being able to find "Enter security code". This seemed to be because in our code we were breaking a loop based on the contents of a page which may not have loaded yet, so I have changed it to break the loop based on the path and changed the location of the break clause which fixes the issue.

Checklist:

[ ] Have you documented your changes in the pull request description?
[ ] Does the change present any security considerations?
[ ] Is any gem functionality overloaded? Eg: Devise controller methods being overloaded.
[ ] Has acceptance criteria been tested by a peer?
[ ] Has the CHANGELOG been updated? (If change is worth telling users about.)

General testing (author)

[ ] Test without JavaScript
[ ] Test on small screen

Accessibility testing (author)

[ ] Works keyboard only
[ ] Tested with one screen reader
[ ] Zoom page to 400% - content still visible
[ ] Disable CSS - does content make sense and appear in a logical order?

Codecov Report

Merging #1707 (ba067df) into master (c392ce5) will decrease coverage by 86.10%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #1707       +/-   ##
==========================================
- Coverage   89.72%   3.62%   -86.11%
==========================================
  Files         399     399
  Lines        8578   13076     +4498
  Branches     1241     224     -1017
==========================================
- Hits         7697     474     -7223
- Misses        701   12601    +11900
+ Partials      180       1      -179

Impacted Files
Coverage Δ

app/models/role.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/team.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/alert.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/contact.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/country.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/product.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/accident.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/incident.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/location.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/forms/alert_form.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 356 more

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 c392ce5...ba067df. Read the comment docs.


 When a process starts up, the rest mapper is populated using the discovery api, making a request for each Group/Version defined in the cluster. In clusters with a lot of apis, this would trigger the client side rate limiter to prevent spamming the api server.
Proposed solution
There's a new lazy rest mapper introduced upstream by https://github.com/kubernetes-sigs/controller-runtime/issues/1603
This rest mapper should allow us to remove custom rate limit thresholds by making only the essential requests to the api server.
Describe alternatives you've considered
Our current solution was to increase the client side limit to a threshold the warning is no longer printed. This solved the UX problem of printing a warning to the console in the middle of a command, but it still blocks while the requests are made and results in load on the api server.
Additional context
Custom rate limiter is applied here:
https://github.com/vmware-tanzu/apps-cli-plugin/blob/61b716a39fa221f3685f393f30d3d4accd37cd2c/pkg/cli-runtime/client.go#L209

Thanks for bringing this to our attention Scott. I'll bump this into our backlog.
cc @atmandhol ...


App freeze after upgrading to version 7, the issue is related to BreakpointObserver

When I upgraded my app to version 7 of Angular, Angular Material and CLI. My app hangs on the loading screen. After a lot of digging around I found the source of the issues, it has to do with BreakpointObserver from Angular CDK.
Here's the link on StackBlitz
All you have to do is to add the following to an element in the AppComponent template:
[style.minHeight.px]="height | async"
Then the app will freeze.

angular/angular#26586

All you have to do is create your observable only once. Currently you create a new one with every call to height().

@manklu is correct. The way you have it set up at the moment will introduce a memory leak. Closing since it works as expected.


Is Cookiecutter 1.7.3 required for cookiecutter-django or is it not updated readme?

Hi, I see the readme recommands installing cookiecutter 1.7.0, while current cookiecutter is already 2.6.0.
Is cookiecutter-django tested against 1.7 or is it simply readme not being updated?
I wonder as the latest cookiecutter-django pip package is also 1.11.9 from 2018, but I see this project being activly developed. I assume pip package is no longer in use as we directly point to the git repo with cookiecutter https://github.com/cookiecutter/cookiecutter-django, but wanted to make sure.
Regards

The cookiecutter-django package in PyPI exists only to secure the name and prevent anyone from using the name for malicious purposes.
Regarding the documentation in the readme, we simply ensure that the user has the minimum version installed, that is, if version 2.5.0 is currently installed, pip will not attempt to update to the latest version, however if 1.5.0 is currently installed, pip will perform an update.
This behavior is achieved with the "package-name>=minimum-version-number" syntax of pip install

Thank you, wanted to make sure major from 1 to 2 is fine and tested. Sorry for bothering.


docs: Improve hello world velocity for beginners

What were you trying to do?
As a developer without ACH experience I need to integrate Moov's software into my business needs. The faster I'm able to iterate, develop code and ship the happier I am. Ideally the software is consistent and intuitive.

Looking at the following popular projects README's: hugo | caddy | etcd | terraform | mattermost (FOSS chat app).
Roughy, the order of each README follows:

Logo
Links to community, documentation, build status, etc
Short, concise, and compelling feature list
Install / Download / Build
Contributing

Issues, Code / PR, testing, feature requests

@wadearnold Do you have suggestions for further improvements? https://github.com/moov-io/ach/pull/379 improves the README quite a lot. We'll expand as people give us feedback, but I'm not sure how much more detail to include.

I'm not really sure. It'd be nice to have some newbies take a look and tell us what's confusing or missing.

Users have created and sent test cases prior to these updates.  Should we close?


Impossible to share audio with discord

Hi,
first thanks for your dockerFile is very good and i use it everyday, i install chrome and discord and i have a probleme with discord.
Screen sharing works fine, except for sound I have this message : Sound may not be available when sharing a screen on your device

Do you have any idea where it might come from ?
Thanks

This project work with pulseaudio. The source of discord needs to be compiled with pulseaudio.
Does discord work at all , or is it the combination ?
https://www.reddit.com/r/discordapp/comments/f22vz6/guide_how_to_stream_audio_to_discord_on_linux/

yes it's work thanks :)


Not really an issue

What package did you use to solve this network? I'm a doctoral student looking for a similar analysis for biobased diesel markets and I'm having a heck of a time looking for a versitile tool.

Hey, I did not use a package. I encoded the projection algorithm in Matlab to solve this problem.


Update README_it.md and accompanying lesson titles

Closing this pull request to lack of updates or replies.


pull request for e2e test at 12/14/2016 08:26:04

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Support Conch Clash in Splat Fest

From Summer Fest 2024, a new fest mode Conch Clash is introduced.
There expected at least three modes

ホラガイ争奪戦 1x
10x
33x

Should introduce new values in fest_dragon or a new field?

Support for Conch Clash has been implemented.
If the clients' implementation is completed by the next fest, it should work for Food Fest and Grand Fest.
The API now includes conch_clash, and its value will be either 1x, 10x, or 33x.
If it is not a Conch Clash, it expects either a null setting or the absence of the conch_clash key in the JSON/MsgPack object.


BundleDecode export & vexana dependency removed

@VB10
BundleDecoder class exported and vexana package dependecy removed.

thank uu


appium flutter library but can't use commands with webview

my app is developed using flutter but some pages are webview ...
ex. run robot framework use appium flutter library can't click or input page webview
How do you have a way to do it? appiumflutterlibrary can be used for webview page ?

Hi,
Did you try to switch context?
In Java we are using something like driver.context("NATIVE_APP") to use Appium elements location
driver.context("WEBVIEW") to interact with webview
driver.context("FLUTTER") to use FlutterFinder

appium flutter library  no keyword "switch to context"
How can I use switch to context based on main:appium flutter library?

Hi, Did you try to switch context? In Java we are using something like driver.context("NATIVE_APP") to use Appium elements location driver.context("WEBVIEW") to interact with webview driver.context("FLUTTER") to use FlutterFinder

What client did you use?
You could find some client library's example to switch context: https://github.com/search?q=repo%3Aappium-userland%2Fappium-flutter-driver+NATIVE_APP+path%3A%2F^example\%2F%2F&type=code

https://appium.io/docs/en/latest/guides/context/

@KazuCocoa why this issue is closed and this link below just provide general information about context set and get
 not really solves the problem mentioned as title because when you use appium flutter driver it only gives you two type of context FLUTTER and NATIVE_APP in an arry after sending GET http request. So, do we have any real solution If In case when we automate Flutter app which is using component from NATIVE and some WEVIEW and It that case how to fix this webview switch context issue

WEBVIEW contexts depend on UIA2/XCUITest driver. This driver returns WEBVIEW contexts from them.
https://github.com/appium/appium-flutter-driver?tab=readme-ov-file#appium-flutter-driver-or-appium-uiautomator2xcuitest-driver

WEBVIEW context manages the WebView contents over Appium UiAutomator2/XCUITest driver

I'm not sure how to configure in Flutter framework side (maybe Flutter team has their own documentation to make their WebView contents debuggable), but below links in each driver (links from https://github.com/appium/appium-flutter-driver?tab=readme-ov-file#commands-for-native_appwebview-context ) would show hints to test them out via Appium drivers.
https://github.com/appium/appium-uiautomator2-driver?tab=readme-ov-file#hybrid-mode
https://appium.github.io/appium-xcuitest-driver/latest/preparation/#webview-testing

@KazuCocoa I know already thats possible with [uiautomator2/ xcuitest-driver] and it allows you to switch to webview and its an option one can code in there framework by replacing the automationName as placeholder as an when they need to switch the driver from appium flutter driver to uiautomator2 or xcuitest-driver to inspect the webview.
One more possibility is to use UiSelector() to scroll in webview wiithout changing appium flutter driver however its not the best solution but it works for now given the situation we dont have any real solution as such when we use appium flutter driver

when they need to switch the driver from appium flutter driver to uiautomator2 or xcuitest-driver to inspect the webview.

I meant this flutter driver got WEBVIEW contexts via UIA2/XCUITest driver internally. So if your app could get WEBVIEW contexts via uia2/xcuitest driver, the appium-flutter-driver also might be able to get them as well via uia2/xcuitest driver internally. Then, automationName can keep flutter.
https://github.com/appium/appium-flutter-driver/blob/7d57cc8363c7c321d36e9cc12e53fb000f53d18e/driver/lib/commands/context.ts#L34
If you meant get context request didn't go though uia2/xcuitest driver in flutter automationName, could you create a new issue with the full server log to check the behavior?

@KazuCocoaI I understand that when using flutter as the automationName in tests, and if we switch the context to NATIVE_APP, the system starts using UIAutomator2 for Android (or the native automation framework) to recognize elements. My understanding is that when this happens, we should be able to interact with WebView elements as well, by default, using native methods like UiScrollable and scrollIntoView() to inspect and locate WebView elements which I figured some now and it is working.
However, I also want to confirm that in some cases, explicit switching to the WebView context may still be necessary for more detailed or advanced interactions with specific Web elements inside the WebView.
So this being handled as well using flutter-appium-driver?

So, interacting with web elements in MATIVE_APP context? Then, it depends on Android OS side. Appium cannot inject such OS level recognition. Appium gets elements via AccessibilityNodeInfo by Android API. If web view elements are available via it (NATIVE_APP context) depends on OS side behavior.
So officially we provide WEBVIEW context to interact with WebView elements but no guarantees in NATIVE_APP context because the behavior is not injectable by Appium's layer.

https://github.com/appium/appium-uiautomator2-driver?tab=readme-ov-file#elements-cannot-be-found potentially helps, btw.


Updated dockerfile to 1.13.11

Updated to latest release of golang 1.13

 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.


DatePicker: Add week parse

Please make sure these boxes are checked before submitting your PR, thank you!

[x] Make sure you follow Element's contributing guide (中文 | English | Español | Français).
[x] Make sure you are merging your commits to dev branch.
[x] Add some descriptions and refer relative issues for you PR.

#13746 #12637

Does it align with ISO8601 week date definition?
Will it work with first-day-of-week?


OpenReadAsync does not work as expected

Hi all,
we were using storage library v11 without any problem when we were calling CloudBlockBlob.OpenReadAsync() Here is our v11 code:
`           CloudBlobContainer cloudBlobContainer = await GetContainerReferenceAsync(containerName);
        if (cloudBlobContainer != null)
        {
            CloudBlockBlob blob = GetBlobReference(cloudBlobContainer, fileName);

            if (blob != null)
            {
                    Stream cloudStream = await blob.OpenReadAsync();
                    return cloudStream;
            }
        }`

we have updated to v12 and the new code seems like this
`            BlobContainerClient cloudBlobContainer = GetContainerReference(containerName);
        if (cloudBlobContainer != null)
        {
            BlobClient blob = GetBlobReference(cloudBlobContainer, fileName);

            if (blob != null)
            {
                    Stream cloudStream = await blob.OpenReadAsync();
                    return cloudStream;
            }
        }`

the problem is, in this case, we have a zip file whose size is 4 Gb in a blob container. with v11 we were able to search through the stream without downloading the whole file and download just a file in zip whose size approximately 1Mb which was working perfectly and just need milliseconds to complete.
with the new library after calling the OpenReadAsync method, we have seen that we do not have the stream information, and length of the stream is surprisingly -1. the whole content is being downloaded when we want to search through the stream and it takes too long because the file is being downloaded.

could you please tell me what is wrong here ?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 60e56e69-1c44-2056-ad5f-319535e4b525
Version Independent ID: 49fa6098-0b8e-ebf5-efe7-f50f3604e325
Content: Quickstart: Azure Blob storage library v12 - .NET
Content Source: articles/storage/blobs/storage-quickstart-blobs-dotnet.md
Service: storage
Sub-service: blobs
GitHub Login: @mhopkins-msft
Microsoft Alias: mhopkins

@coachburcu Thanks for the question! We are investigating and will update you shortly.

@coachburcu Firstly, apologies for the delay in responding here and any inconvenience this issue may have caused. I'd recommend posting your question in https://azure.microsoft.com/en-us/support/community/ since it's not directly related to the documentation. We'll follow up there. We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.