Only list gcs folder blobs in GCSToBQLoadRunnable

Functionality for specifying a GCS folder within the bucket to dump objects into was added here. This PR addresses an issue with this feature I have outlined in #271.
I have passed through the folder prefix as a list option to the GCSToBQLoadRunnable, and all tests seem to be passing for me with the update. However a new integration test should added to recreate the issue and confirm this change fixes it.
However, this new test is not a straight forward addition of data and schema, as detailed in the readme section for adding integration tests. I thought it was best discussed here for how it should be implemented, but I would imagine it working as follows:

Add some objects in same GCS bucket but in a folder next to the target folder of connector
Run connector
Assert rows in target folder appeared
Assert rows in other folder did not appear

 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.

@zachary-povey your proposed integration test flow sounds good

Codecov Report

Merging #270 into master will decrease coverage by 0.13%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #270      +/-   ##
============================================
- Coverage     70.87%   70.73%   -0.14%
  Complexity      301      301
============================================
  Files            32       32
  Lines          1538     1541       +3
  Branches        164      164
============================================
  Hits           1090     1090
- Misses          390      393       +3
  Partials         58       58

Impacted Files
Coverage Δ
Complexity Δ

...wepay/kafka/connect/bigquery/BigQuerySinkTask.java
58.33% <0.00%> (-0.62%)
27.00 <0.00> (ø)

...ay/kafka/connect/bigquery/GCSToBQLoadRunnable.java
15.38% <0.00%> (-0.11%)
5.00 <0.00> (ø)

Hi guys - i've added the integration test as described- it felt a bit hacky (I don't do much java) so feel free to make suggestions for refactoring.
On a different note are you aware of the integration test ever having race conditions? I was having intermittent issues where tables were the tables populated by streaming inserts wouldn't get created but on a re-run the problem would go away...


move /ds to /builder/data-sources

We're adding the assistant builder which will be under /builder/assistant. So /ds needs to become /builder/data-sources.
I prefer to merge with just this ASAP to limit the risk of conflict

I guess we don't have any return URL to here for OAuth. They all open popups or new tabs right?


Scrum Report 2: June 12, 2021

CSID: g6q1b

What did you work on this past iteration?

Creating the main components of the welcome page.

What were any major issues/challenges you ran into?

No major issues. However, I had some challenges working with material UI w/ styled components in regards to overriding styling in prebuilt material ui components (which I am still working on).

What do you plan to work on for this coming iteration?

Finishing up the styling of the login page, implementing the New Itinerary Page and connecting it to Itineraries page and making the pages responsive.

CSID: v0p1b

What did you work on this past iteration?

Creating main itinerary edit view and calendar + styling.

What were any major issues/challenges you ran into?

Challenges: having a responsive calendar that is mobile friendly; coming up with a UX- friendly way to show the map and itinerary view together.

What do you plan to work on for this coming iteration?

Finish creating what needs to be done. Formalizing data layout and API calls.

CSID: d9i2b

What did you work on this past iteration?

Created the navbar and implemented styling and routing.

What were any major issues/challenges you ran into?

Not many, there was an issue with trying to figure out what the best way to do the routing was, and how to setup the navbar initially but that was done with some trial and error.

What do you plan to work on for this coming iteration?

Continue working on the navbar to allow clicking outside to close, add a user settings button to navbar, implement a search bar, and start working on the backend.

CSID: k2r1b
What did you work on this past iteration?

Creared the map component and connected it to Redux. Also fixed several warnings and converted the frontend to TypeScript.

What were any major issues/challenges you ran into?

Using a third-party API for maps (Mapbox) that was not built for React while trying to keep the keep from using the document object was difficult. Redux Toolkit with TypeScript is also not as straightforward as plain React, although their documentation helped with most issues

What do you plan to work on for this coming iteration?

Finish connecting the map and other components to Redux, draft a schema for the database, setup the backend.


Exslt extension

Allows to enable exslt extension, namespace xmlns:exsl="http://exslt.org/common" and it's functions like exsl:node-set()

Codecov Report

Merging #1 (6a83899) into master (fc60dc2) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master        #1   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           32        34    +2
=========================================
+ Hits            32        34    +2

Impacted Files
Coverage Δ

xslt.go
100.00% <100.00%> (ø)

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 fc60dc2...6a83899. Read the comment docs.


Error handling and recovery mechanisms in Save System

Enhanced error handling with detailed logs and user feedback for save/load processes.
Implemented backup creation before saving to ensure data recovery.
Added data integrity checks using hashing to verify save file consistency.
Improved load recovery by attempting to load from backup if the primary save fails.
Provided user feedback and recovery options in case of errors.
SaveVersioning slightly enhanced and upgraded to 1.1.0

This commit addresses and resolves Issue #4 by ensuring the save system can handle and recover from errors gracefully.

Closes issue #4
Would need some enhancements to correct 2 Output errors, not project breaker for now :


Add back 3.9 support

This PR adds back support for 3.9, which we should keep until at least April!
Changes made in this Pull Request:

PR Checklist

[ ] Tests?
[ ] Docs?
[ ] CHANGELOG updated?
[ ] Issue raised/referenced?

Codecov Report

Merging #89 (e119b7c) into main (cf8c675) will decrease coverage by 16.33%.
The diff coverage is n/a.

Additional details and impacted files


Adding  dozent.ism.de for teachers at ISM Germany

Subdomain dozent.ism.de used for teachers
https://en.ism.de/full-degree-students/bachelor-programs/bachelor-information-systems/program-content#2nd-semester
screenshot_ism.pdf

@acsig Pull request merged. Thank you.


css('colorName') always return 'rgb(255, 0, 0)'

version: 9.0.0
  console.log(csx.color('red').toString())
  console.log(csx.color('green').toString())
  console.log(csx.color('blue').toString())

output:
rgb(255,0,0)
rgb(255,0,0)
rgb(255,0,0)

We removed named colors in 9.0.0 because they increased the bundle size of the library substantially and because it appeared that no one was using them. (there are well over 100 named colors) There was discussion about making them an optional import, but I was concerned about over-complicating a helper library.
The reason it shows up as red is because that is the default color we assign when the color cannot be parsed.

I apologize that the docs don't reflect this.  I am marking this as docs so we can go back and remedy that.

Thx for your reply.


[FEATURE] Child categories

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
Creating child categories. Example:
Category "minecraft" can have child categories with products: "bungeecord", "papermc" ect
Describe alternatives you've considered

Create normal categories...

Additional context
Add any other context or screenshots about the feature request here.

Hi, please for features refer to https://paymenter.hellonext.co


Creating new PR for Read receipt changes - nodeJs

Executed Build Pipeline:
https://github.com/OfficeDev/Microsoft-Teams-Samples/actions/runs/6994535900


404 at

404 found here
Set build-time variables (–build-arg)
You can use ENV instructions in a Dockerfile to define variable values. These values persist in the built image. However, often persistence is not what you want. Users want to specify variables differently depending on which host they build an image on.

A good example is http_proxy or source versions for pulling intermediate files. The ARG instruction lets Dockerfile authors define values that users can set at build-time using the --build-arg flag:

$ docker build --build-arg HTTP_PROXY=http://<IP_ADDRESS>:1234 .
This flag allows you to pass the build-time variables that are accessed like regular environment variables in the RUN instruction of the Dockerfile. Also, these values don’t persist in the intermediate or final images like ENV values do.

Using this flag will not alter the output you see when the ARG lines from the Dockerfile are echoed during the build process.

For detailed information on using ARG and ENV instructions, see the Dockerfile reference(https://docs.docker.com/v17.09/edge/engine/reference/builder/). // <=== HERE IT IS

This issue appears to be fixed. Please reopen the issue if the problem persists. Thank you.


Adding option for installation from release files into docs

Adding option for installation from release files into docs might be nice:
curl release_file
mv binary /usr/local/bin

We will be adding it soon


Upgrade to ReactJs 15

Ultimate Problem
We need to upgrade to ReactJs v15.
The upgrade to ReactJs 15 is much simpler than it was to upgrade to ReactJs 0.14.0.
Basically if you have no warnings in the console you should be good to go.
Solution

Pull in ReactJs files for v15.1.0.
Remove all previously deprecations.
Update usage of removed deprecations.
Fix imports.

Also Fixed

Un-parameterize ReactElement

This caused issues with strong-mode enabled libs/packages that use react-dart.

Breaking Changes

getDOMNode and setProps were removed entirely.
render, findDomNode, and unmountComponentAtNode were moved from react.dart to react_dom.dart.
renderToString and renderToStaticMarkup were moved from react.dart to react_dom_server.dart.
ReactElement was un-parameterized.

Testing

Verify that all tests pass.
Verify that all examples work as expected.

FYA: @hleumas @greglittlefield-wf @clairesarsam-wf @trentgrover-wf @maxwellpeterson-wf @evanweible-wf
FYI: @georgelesica-wf

Changes looks good, all tests pass.
+1

@trentgrover-wf this is ready for a final review / merge / tag.

+1
merging and releasing as 2.0


Forward Forward algorithm in more languages  like ardoino and cpp  because  no one   implemented in these languages

Something like  the ardoinoneuralnetwork

Can we have  it i really  need  a ardoino  one (not for the ardoino uno but for the esp32)because  it  learner's in real time  ?

And i don't know how to use tensor flow or torch

Hi, I have an F-F algorithm repository for vision (64x64 pngs). A single neuron learns to distinguish the datasets in my toy problem (Gaussian Splatting).


Prototype of method-forward paradigm

This is not a changeset that would be merged into our codebase.  It is just a prototype to evaluate whether we want to proceed with this approach.
The problem we're trying to solve is that many of our structs share common fields.  This can be problematic when PowerSystems consumers want to extend their own types.  They have to copy all of the fields.  More importantly, if we ever added a new field and used that field in an exported method, those consumers would get unclear runtime errors.
One part of this solution is to move away from defining field access (value.field) as part of our public API.  We would need to have accessor methods defined for every field.  Instead of typing "generator.name" you would type "name(generator)".
This changeset implements the paradigm for the subtypes of RenewableGen.  The common fields are in the new struct RenewableGenBase.  The forward macro from ReusePatterns.jl forwards all methods to that type.
The rest of the changes were to make the tests pass or illustrate how many lines of code we will have to change.
Thanks to Dheepak for finding and proposing the "forward" macro solution.

Sorry for the churn.  I based this off my UUID/serialization branch because I wanted to show how this interacts with that work.  This means that you should only look at the last commit.

Adding a core dependency on another package is less than optimal. I understand the need to have a better interface but reading the ReusePatterns developer justification for this in Discourse makes me even less certain that this is the way we should go. We had this discussion about the use of SimpleTraits.jl and arrived at the same conclusion.
Also, this discussion is pretty clear about why in Julia hacked inheritance is not advisable and why these perceived issued
https://discourse.julialang.org/t/workaround-for-traditional-inheritance-features-in-object-oriented-languages/1195/17
Also this http://www.stochasticlifestyle.com/type-dispatch-design-post-object-oriented-programming-julia/
It is worthwhile re-thinking some aspects of the way we define the fields in the structs and the type structure to make it more efficient, but I am not convinced this is the proper way.

We could actually just copy the function macro and dependent code into PowerSystems.  It isn't much code.  I linked it here for simplicity.  We should only focus on the use of it.
The discourse thread you linked shares the same types of discussions as the ones the ReusePatterns author linked to.  They talk specifically about our problem where multiple concrete types share the same fields.  Here are the main points:

You can define an abstract type (suppose RenewableGen) and require that all subtypes implement the fields that are common.  This is not very Julian.  Many of the developers specifically recommend against this.  It also presents lots of problems.  Changing fields because of implementation changes will cause massive churn in the codebase and everyone extending it.
A Julian solution would be to define required interfaces for RenewableGen and require that all subtypes implement that interface.  That means that all subtypes would have to define methods for all common fields. That becomes tedious very quickly.
You can automate the method generation with a forward macro. There are several packages out there that do this; some of them are written by Julia devs.  From reading these threads I think that inevitably some forward macro will end up in Base.  I really have no idea why that haven't already formalized it.

I think this is likely the most pragmatic solution to solve the problem.  Dheepak and I spent a lot of time discussing it.  I'm still very open to other options.

@jd-lara to add more context, let's say someone wants to use PowerSystems and extending the type we've implemented. e.g. in PowerSystems currently we have
struct RenewableCurtailment <: RenewableGen
    name::String
    available::Bool
    bus::Bus
    tech::TechRenewable
    econ::Union{EconRenewable,Nothing}
    internal::PowerSystemInternal
end

Let's say someone wants to make a CustomRenewableCurtailment that can be used interchangeably with RenewableCurtailment. If they do the following:
struct CustomRenewableCurtailment <: RenewableGen
    name::String
    available::Bool
    bus::Bus
    tech::TechRenewable
    econ::Union{EconRenewable,Nothing}
    internal::PowerSystemInternal
    custom_field::CustomType
end

and if we change RenewableCurtailment in the future, they'll have to change CustomRenewableCurtailment as well, in order to upgrade. This adds maintenance burden on developers extending PowerSystems. Alternatively, they can use composition and do this:
struct CustomRenewableCurtailment <: RenewableGen
    rc::RenewableCurtailment
    custom_field::CustomType
end

This will allow us to make changes to the fields of RenewableCurtailment in the future and developers that extend PowerSystems would get our new features when they upgrade. Also, code is not repeated in this case.
However, this is provided developers that extend PowerSystems do not use dot operator to access data. This means that in order to access the data, we need to provide a function that acts as an interface. An example for the name interface is as follows:
name(rc::RenewableCurtailment) = rc.name

A user that extends RenewableCurtailment to CustomRenewableCurtailment can also define the name function interface for CustomRenewableCurtailment. They can do this using the following:
name(crc::CustomRenewableCurtailment) = name(crc.rc)

However, it can be tedious to define all the functions for every extension. This is where having the @forward macro can be helpful. If users define the following:
@forward (CustomRenewableCurtailment, :rc), RenewableCurtailment

any function defined on RenewableCurtailment will work on CustomRenewableCurtailment, forwarding to the correct field automatically.
This is probably all obvious to you @jd-lara, I'm mainly writing it out so that others using PowerSystems in the future will know what patterns to follow for extensions, should this PR get merged and this be implemented across the package.
The only downside of this is that users of PowerSystems will not be able to use tab complete in a REPL, which I think can be remedied using (extensive) documentation.
@jd-lara do you have suggestions for alternatives that increase code-reuse and allow extensions without be tedious and putting the onus on other developers? Perhaps we can discuss this over a conference call to iron out the details.

@daniel-thom option 2 is probably the most Julian way of tackling this.
I am still unconvinced that we should support this type forwarding feature natively and if someday this capability makes into the Julia code base we can add it. I haven't seen any discussion to try to do it in the short run. Even though defining interfaces can be tedious, making a type system that can be extended with interfaces more simply is an excellent design goal if we are not there yet.
Also, it is clear we should move to a method forward use mode and rely less on the dot notation. This is a good improvement. However, I think this is unrelated to the use of macros to extended the types.
@kdheepak We have had this conversation about code re-use multiple times, and this solution all are trying to do is force Julia to work like OOP, and the discussion in the forum is long about how this just means that there is an improper type system design. The case of DataFrames is pretty well discussed.
My proposal to this "problem" is to do something similar to what is done in DifferentialEquations.jl (I have to prototype this better). Overload some functions like get_property on a custom AbstractType like this:
struct MyCustomRenewable{T<:RenewableGen} <: RenewableGen
       base_type::T
       myfield::Float64
       my_other_fied::Float64
end

t = RenewableCurtailment()
foo = MyCustomRenewable(t, 10.0, 10.0)
MyCustomRenewable{RenewableCurtailment}:
   base_type: RenewableCurtailment(name="init")
   myfield: 10.0
   my_other_fied: 10.0

In this way, a lot of methods that exist already for Renewable Energy can be extended.
Additional to this we can have a generic type for prototyping devices that is like this
struct GenericInjection <: Injection
    name::String
    bus::Bus
    available::Bool
    data::Dict{Symbol, Any}
end

and enable a type that can have any data template encoded into the Dict for users who want to add a very unconventional device.
One of the core questions here is which capabilities we want to enable such that users can extend the type structure for their use and how we want the type structure to be extended when contributing to the code. I believe most use cases so far are the former.

@daniel-thom @jd-lara @kdheepak , where are we on this? If this is our path forward, I'd like to pursue it soon. If more work is required to identify the solution, I'll rearrange some priorities.

@claytonpbarrows I think we agree on principle about going on this path. The implementation is not clear yet. I have been reading about the use of the eval() function for code generation but no definitive procedure.
@daniel-thom mentioned that there are some severe performance penalties with some of the "official" approaches to solve this and we probably should document that and ask in discourse.

Dheepak proposed an implementation in a separate repo (https://github.nrel.gov/dkrishna/power-systems-extension-example/blob/master/solution_2/powersystems.jl).  I am 100% onboard with that.  I do not know of any performance penalties with it.


Adapt library for 80*40 panel

Can this library be adapted to work with a Qiangli 80*40 p4 panel with 1/20 scan rate? If so, what changes have to be made?
Drivers mentioned are DP5125D + RUL5158C

RUL5158C is a shift register multiplexor , the code to support it discussed in #164


Yoda conditions and ts-standard

          prefer `'' !== inputValue`

see https://en.wikipedia.org/wiki/Yoda_conditions
Originally posted by @rjrodger in https://github.com/voxgig/model-react/pull/29#discussion_r1365104856

Decision: we'll keep ts-standard for now even if it breaks certain conventions.


Add delegation support for RA calls

Linked to the following swagger specs pr
https://github.com/Azure/azure-rest-api-specs/pull/2031
https://github.com/Azure/azure-rest-api-specs/pull/2043

Description

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] Please add REST spec PR link to the SDK PR
[x] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[x] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[x] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

@shahabhijeet API specs PR has been merged

@shahabhijeet Made all the changes as per the comments and rerecorded the tests

@shahabhijeet Fixed merge conflict issue and updated the version


K32W0 SDK 2.6.13 changes

Changelog:

Add extended search feature.
Limit temporary RAM buffer to PDM page size.
Radio: fix VS IE content.
Adjust RSSI to be [-110, 0].
Update west manifest to point to 2.6.13.
Sync with the sign_images script changes.

Signed-off-by: George Stefan<EMAIL_ADDRESS>Signed-off-by: Marius Tache<EMAIL_ADDRESS>

@jwhui, could you please take a look and have this merged?


Gradle isn't language but build tool

Groovy actually

Agreed. My Flutter projects which are around 80% Dart code are shown as using Gradle

Hi @kenrube and @faraazahmad !
Thank you for your feedback! We will fix language detection problem.
Also, where do you think we should show gradle statistics and other build tools? What is more suitable additional group in the "tech" section or a new section called "build tools"?

@anatolystansler If you can detect other build tools like Maven, cmake, Bazel and so on, I think "build tools" section would be preferable :)

@faraazahmad Do I understand right that gradle lives in '.gradle' files, dart lives in '.dart' files or are there exceptions?

@asurkov yes

@yaronskaya, so @faraazahmad issue has to be something else than lack of Dart support. I believe that sourcerer-app will report Gradle language for anything located in '.gradle' files.

@asurkov sure. However, it revealed a missing language.

@yaronskaya check it out for missing languages :) https://github.com/sourcerer-io/sourcerer-app/blob/develop/src/test/kotlin/test/tests/extractors/IgnoredSamplesWildcards.kt

Closed due to inactivity


(BUGedx-app-android VERSION 2.19.1 ) Choose a photo option is not working properly

Project Information

Repository:  https://github.com/edx/edx-app-android
Project Name:  edX - Online Courses by Harvard, MIT, Microsoft
My Github Account: https://github.com/friendsmobile
Download the application:  https://play.google.com/store/apps/details?id=org.edx.mobile

Expected behavior
When I select a photo from the gallery using a Choose a photo option, this picture should be upload and set  on the profile
Actual behavior
The picture will not be uploaded when I try to upload the picture by using the Choose, a photo option you see properly in GIF video
How to reproduce

Download the application

open the application

click on setting button

select the profile option

click on Edit option

click the change option and select the chose a photo option

select the picture from gallery and try to upload it

Note the Error

Browser/App version:  2.19.1

Operating system: 6.0

Recording Of The Bug

The bug wasn't reproducible, so it is likely a device-specific issue.
Please upgrade to the latest version 3.1.0.


WIP: feature: adding cassandra support

Fixes #877
This is still work in progress.
TODOS:

[x] add cassandra module
[x] add testcontainers support
[x] add a database migration support
[ ] add a dummy-cassandra module, as for dummy mongodb.
[ ] add a datastax connection support ? as for oauth2 okta and auth0 providers. What do you think about that ?

Converting to draft as you have a long TODO list :)

@DamnClin, is there a way to have a more detailed output from CI, especially sonar runs ?
logs don’t tell which are the impacted files and full report points to a local address :/

You can run a local sonar analysis this is documented in the readme:
docker compose -f src/main/docker/sonar.yml up -d
./mvnw clean verify sonar:sonar

Thank you!
I didn’t pay enough attention, sorry

@Yourgene : thanks for your work here. But I think it will be easier to split like this: 1 module = 1 pull request
So if the 1st module for init Cassandra is ready and reviewed, it can be merged.
Then, you can add dummy etc in another PRs


How to update Accessible property of existing request?

I used convenient class method saveData to save items to key chain. However after I realized that I need that keychain item during background operation. How can I update existing item's accessibility to something like kSecAttrAccessibleAfterFirstUnlock property?

I don't think this is directly possible with Locksmith, sorry. Your best bet is probably to load the item back from the keychain, and then re-save it with the right accessibility using Locksmith's API for that.
Feel free to reopen if necessary :)

I have written following code which seems working. Do you see any problem with the following code? Thanks.
    class func changeAccess() {
        //first check if it exists
        guard let dictionary =  Locksmith.loadDataForUserAccount("accountName") else {
            print("Old data is not available")
            return
        }
        if dictionary["key"] as! String == "value" {
            print("Old data is present")
            do {
                print("Old data is deleted")
                try Locksmith.deleteDataForUserAccount("accountName")
            } catch {
                print("Error deleting old one", error)
            }
            let updateRequest = LocksmithRequest(userAccount: "accountName", requestType: .Create, data:["key":"value"], service:LocksmithDefaultService)
            updateRequest.accessible = Accessible.WhenUnlockedThisDeviceOnly
            do {
                let dictionary = try Locksmith.performRequest(updateRequest)
                print(dictionary)
            } catch {
                print("Error change access: ",error)
            }
        }
    }


Add trimLeft/Right

I couldn't figure out how to ... fix the 2 errors that are left? Is there some trick that I don't know or should I just blacklist those, as I don't think these aren't important :grinning:

I couldn't figure out how to ... fix the 2 errors that are left? Is there some trick that I don't know or should I just blacklist those, as I don't think these aren't important :grinning:


docs: correct subsection formatting

Apply a small fix to ensure consistent subsection formatting throughout the document.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (1ba25e7) 85.00% compared to head (5c9e5cf) 85.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##           development      #64   +/-   ##
============================================
  Coverage        85.00%   85.00%
============================================
  Files                6        6
  Lines              260      260
============================================
  Hits               221      221
  Misses              39       39

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Web Server Clustering/Multiple IP Backends

Is your feature request related to a problem? Please describe.
I know its possible via configuration to configure multiply backend systems. Can you make it possible in the GUI?
Describe the solution you'd like
As I said, can you make this possible in the GUI?

The same problem.


syntax error after installation (pull)

Hi,
when searching how to create xlsx with abap of course I got to here eventually.
Pulled the package but when activating I get syntax error in
ZCL_EXCEL_WRITER_2007->CREATE_XL_DRAWINGS_HDFT_RELS (actually I get a dump when running any of the demo programs:
Category               ABAP programming error
Runtime Errors         SYNTAX_ERROR
ABAP Program           ZCL_EXCEL_WRITER_2007
Application Component  Not assigned

Line 49: Error in
arithmetic expression: A field, a function, or
"(" was expected instead of "<FS_DRAWINGS>-
DRAWING->GET_INDEX(".
section of the code:
46    lt_drawings = io_worksheet->get_header_footer_drawings( ).
47    LOOP AT lt_drawings ASSIGNING <fs_drawings>. "Header or footer image exist
48      ADD 1 TO lv_relation_id.
49      lv_value = <fs_drawings>-drawing->get_index( ).            <<<=== line giving error
50      READ TABLE lt_temp WITH KEY str = lv_value TRANSPORTING NO FIELDS.
51      IF sy-subrc NE 0.
52        APPEND INITIAL LINE TO lt_temp ASSIGNING <fs_temp>.
53        <fs_temp>-row_index = sy-tabix.
54        <fs_temp>-str = lv_value.
55        CONDENSE lv_value.
Can't figure out what should be wrong with the code.
I'm running on SAP_BASIS & SAP_ABA	Release 750	SP-level: 0019
Any help is very much appreciated.
Thanks
Regards
LAT2

Maybe the mass activation of abapGit didn't activate the ABAP dictionary objects of abap2xlsx. What version of abapGit do you use?
For instance, is the table type ZEXCEL_T_DRAWINGS activated? (SE11)

Same issue already reported (#674 @AndreaBorgia-Abo fyi). It doesn't seem this was reported to abapGit, maybe you could report it to abapGit?

Thank you. I'm just wondering why i did't find #674 ? I searched, of course, with exactly those key words.
Thanks for your help. I check activation and open a ticket with gitHub
Regards & Thanks for your extrem fast reply.
LAT2

Probably because #674 was closed and GitHub search default options are is:issue is:open. You may find closed issues by clearing is:open.

@sandraros I'm having the same issue pulling tag 7.15 but in this case the activation error is spurious, objects are active. Will see if I can find a pattern, no further updates here.

I pulled the full abap2xlsx again and after that everything was fine.
so actually I don't know what went wrong the first time.

@LAT2 in this case, the objects were already in the system and active. Unless you want to restore the system from backups just to run that test, that's hardly surprising, imho.


Add support for I2C slave mode

This pull request is based on #252. I recommend reviewing/merging that one first.

Haven't looked at this in-depth, but looks good to me! -> approved

Okay, so here's the thing: When I submitted this, it worked. I verified this with the provided example, using RTT and a logic analyzer. It no longer works for me now, on none of my boards.
Some context: I've been having trouble getting slave mode to work for a while. After much investigation, I concluded that one of the boards I was using was likely damaged. I was using a test setup with two boards, one acting as master, one as slave. Since I didn't have a replacement at hand, I implemented this new design and tested successfully on the other one.
Yesterday, I was no longer able to get it to work, on none of my boards. Not the presumably damaged one, not the one it originally worked on, and not the replacement board I have gotten in the meantime. The master just produces three clock pulses on SCL, then nothing. Right now, I'm at a loss on why that is, but I can think of two reasons:

There were some special circumstances in my successful test that I fail to replicate now.
There is something about my setup the damages the I2C peripheral.

I'll keep investigating. If you, or anyone, is testing this, I'd be very interested in the results.

Okay, turns out it was a wiring issue in my setup (don't ask about details, unless you're willing to embarrass me in public).
Merging, since @david-sawatzke already approved, and the only thing I did since then was rebase without changes.


Unintentional destruction of build trace output via API call

While looking through the API code, I noticed that this line could be unintentional destructive:
https://github.com/gitlabhq/gitlab-ci/blob/master/lib/api/builds.rb#L36
If the user only sets the state and not the trace, the Build#update_attributes call will set the trace to nil when it saves it, thus losing any previous trace data.
Also, the documentation for this particular API call is in error and has been fixed in https://github.com/gitlabhq/gitlab-ci/pull/293

@alakra Thanks for the issue report. Ive prepared a fix.


Update reverted README.adoc for broken dependencies image link

this commit is reverted at 946f5a8e857acb43da77a7cbf4e4d31d45176bd4
relate #1676

@fpnuseis Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@fpnuseis Thank you for signing the Contributor License Agreement!


Lantern 629 humana webscraper

Pull requests into this repository require the following checks to be completed by the submitter and reviewers.
Submitter:

[x] Administrative tasks are complete.

This pull request describes why these changes were made.
The JIRA ticket links to this PR.
The JIRA ticket for this PR is:

[x] Tests are complete.

Tests are included and test edge cases.
Tests have been run locally and pass.

[x] Code review has been performed.

Code diff has been done and checked to ensure only expected code is being committed.
A linter for the language has been run.

Primary Reviewer:

[ ] Code works.

Code has been run locally and the basic functionality affected by the PR has been checked.
Edge cases have been checked to ensure behavior is as expected.

[ ] Code review has been performed.

Code is maintainable, reusable, efficient, and correct.
Code accomplishes the tasks purpose.
Code follows style guidance appropriate for the language, including passing linter checks.
Code is well commented (which does not mean verbosely commented).

[ ] Tests are complete.

Tests are included and test edge cases.
Tests have been run locally and pass.

Merger:
Prior to merging, ensure that all checks have been completed. Delete the branch after the merge
is complete.

Regarding failure of Go Lintr for this branch:
The fix for that Go Lintr error has been done in the new pull request: https://github.com/onc-healthit/lantern-back-end/pull/403
The reason we are seeing this Lintr error now is because the other pull request with the fix is not merged to main yet. Once we merge the fix to main, merging this pull request wont thow errors in Github Actions (Go Lintr).

@archita-ekkirala Reviewed and Approved, please assign within Mettles for Github PR Reviewer approval


Develop upstream sync 200601

Can one of the admins verify this patch?

jenkins: retest please

jenkins: retest this please.


[Request] Can you make a way to load other extensions with burp-rest-api more easier

This is just a request
I know you guy have the option --burp.ext=<filename.{jar,rb,py} to load other extensions.
But I've installed many extension for Burp(many of them required Jython), loading burp-rest-api with bunch of options for that extension is really painful.
Maybe I'm did something wrong(correct me if I'm wrong) cause after I start burp-rest-api and install some extension then restart burp-rest-api those extension I installed completely disappear.
So can you make option for loading many extension easier like --burp.ext.folder= for example or do it like Burp original is loading it without specific anything.
Desktop:

OS: Mac OS 10.14
Burp Suite Professional version v2.0.09beta
Extension burp-rest-api version 2.0.1

Hi @j3ssie , the --burp.ext= option is only a way to include new extensions from the command line easily.
It is still possible to include them with a custom --user-config-file= like in normal burp.

Yeah I got it.
But another issue is after I used Burp with burp-rest-api and exit it then run original Burp I got no extension.

What you are experiencing it is the expected burp-rest-api behaviour. When it starts up it generates a new temporary user-config-file derived from the auto saved, user-config-file. Before exiting, burp-rest-api removes the temporary user-config-file

What you are experiencing it is the expected burp-rest-api behaviour. When it starts up it generates a new temporary user-config-file. Before exiting, burp-rest-api removes the temporary user-config-file.What you are experiencing is Burp Suite trying to access an unexistent user-config-file.

Closing this issue as for @thypon response. Please reopen an issue with step by step instructions, if you think there is a bug.


swap in grpclib for async grpc requests

This PR replaces grpc.aio.Channel with grpclib.client.Channel to allow for the use of async grpc requests in a multi-threaded environment, as we do in the batching algorithm
https://github.com/grpc/grpc/issues/25364

Codecov Report
Attention: 259 lines in your changes are missing coverage. Please review.

Comparison is base (a26557b) 89.38% compared to head (8bc470a) 89.18%.
Report is 228 commits behind head on beta/v4.0.

Files
Patch %
Lines

integration/test_collection_openai.py
33.33%
38 Missing :warning:

weaviate/collections/batch/base.py
82.43%
26 Missing :warning:

weaviate/collections/filters.py
73.01%
17 Missing :warning:

weaviate/collections/data.py
78.57%
15 Missing :warning:

integration/test_collection_rerank.py
26.31%
14 Missing :warning:

weaviate/collections/batch/batch_wrapper.py
82.27%
14 Missing :warning:

weaviate/collections/batch/grpc_batch_objects.py
84.41%
12 Missing :warning:

weaviate/collections/config.py
66.66%
10 Missing :warning:

weaviate/client.py
84.48%
9 Missing :warning:

integration/test_collection_batch_delete.py
94.96%
8 Missing :warning:

... and 32 more

Additional details and impacted files
@@              Coverage Diff              @@
##           beta/v4.0     #747      +/-   ##
=============================================
- Coverage      89.38%   89.18%   -0.20%
=============================================
  Files            154      177      +23
  Lines          16747    18029    +1282
=============================================
+ Hits           14970    16080    +1110
- Misses          1777     1949     +172

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[Bug]: cannot search folders (neither starred and recent items)

Bug Description
Typing 'o foo folder' does not yield results even if folder foo exists. 'o foo' does not yield results either.
Same behaviour with 'o bar starred' and 'o bar recent'
Else quick switcher search works fine.
Please help.
Relevant Screenshot
No response
To Reproduce
see above.
Debugging Log
16:37:30.602] Shimmering Obsidian[Script Filter] Queuing argument '(null)'
[16:37:34.480] Shimmering Obsidian[Script Filter] Script with argv '(null)' finished
[16:37:34.487] STDERR: Shimmering Obsidian[Script Filter] excluded files: undefined
[16:37:34.489] Shimmering Obsidian[Script Filter] {"items":[{"title":"_Task List","match":" Task List _Task List filename name title","subtitle":"▸ public_notes","arg":"public_notes/_Task List.md","quicklookurl":"/Users/stefan/Obsidian_Local/public_notes/_Task List.md","type":"file:skipcheck","uid":"public_notes/_Task List.md","icon":{"path":"icons/note.png"},"mods":

Workflow Configuration 1

h_lvl_ignore
h1 h2 h3 h4 h5 h6
ocr_languages
eng+deu

Workflow Configuration 2

Version & System Information
-------------------------------
Metadata JSONs: 3/3
Metadata String Length: 5834893
-------------------------------
WORKSPACE DATA
'workspace' exists
'workspace.json' exists
-------------------------------
INSTALLED VERSION
macOS: 13.0
Alfred: 5.0.3
---
Obsidian: 1.0.3
This Workflow: 3.1.3
Advanced URI Plugin: 1.17.0
Metadata Extractor: 1.0.2
-------------------------------
LATEST VERSION
Obsidian: 1.0.3 (Insider: 1.0.3)
This Workflow: 3.1.3
Advanced URI Plugin: 1.28.2
Metadata Extractor: 1.0.2
-------------------------------
INTERNAL WORKFLOW CONFIGURATION
Vault Path: /Users/stefan/Obsidian_Local
Vault Name (encoded): Obsidian_Local
-------------------------------

Make sure you have done the following

[X] I have updated to the latest version of this workflow.
[X] I have read the Troubleshooting Documentation.
[X] If the o… main search does not work, I have tried rerunning osetup and it still does not work.
[X] If I updated to version 3+ for the first time, I have disabled migrating workflow cutomizations. (If you haven't, you can simply re-download and install the latest release from GitHub and uncheck Migrate my workflow customizations.)

should most likely be fixed with the latest release 3.3.1. If not please leave a comment and I'll re-open.


Add resources to init container

When you have quota on a namespace then try to add a timescaleDB in it, it will fail because of missing resources in init container.
Idk if you prefer to use same resources configuration than containers, if yes, there is the PR

 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.


usage for rviz_common::VisualizationManager function

Hi,
There has been a change in the input arguments for the rviz_common::VisualizationManager function (rviz::VisualizationManager in ROS1) and now the following three have to be passed over to the function when called.
ros_integration::RosNodeAbstractionIface::WeakPtr
rclcpp::Clock::SharedPtr
WindowManagerInterface*

so  I did as follows.
(... for rviz_render_panel_ )
auto rviz_ros_node = std::make_shared<rviz_common::ros_integration::RosNodeAbstraction>("rviz");
rviz_common::WindowManagerInterface * wm;
auto clock = rviz_ros_node->get_raw_node()->get_clock();
rviz_manager_ = new rviz_common::VisualizationManager(rviz_render_panel_, rviz_ros_node, wm, clock);

but it fails when
rviz_render_panel_->initialize(rviz_manager_);
rviz_manager_->initialize();

The relevant tutorial for that function hasn't been written for ROS2 yet.  Any advice about what to pass over to the function when using it?
Thanks in advance,
Jaehyun

@JaehyunShim I took a look for similar code in rviz and found this: https://github.com/ros2/rviz/blob/ros2/rviz_common/src/rviz_common/visualization_frame.cpp#L325-L350
I suggest that you review that code for differences. Otherwise, you can submit a test case that can be used to reproduce the issue.

@mjeronimo  Thank you for your comment.
I copypasted the code in this guy's comment and tested it but it didn't work. The program dies when running the function (setEnable) I mentioned in this comment.
If visualization_manager is going to be added to Rviz2 for the next distro anyway (as you can see it here) and there are already use cases of the feature (to be migrated to ROS2) out there,  I think verifying that it works without issues this time is not a bad idea.
Thank you for your help in advance!
Jaehyun

@mjeronimo  ping

@JaehyunShim I've used the code as a starting point and have reproduced the failure (I'm getting a double free error). I need some time to debug to see if I can get to the root cause. Output should be a running example.

@mjeronimo  Thanks! I will wait for your next comment then

@mjeronimo Kind reminder~.
Also, I would like to ask if your team can reconsider blooming the latest version of this repository which is with the visualization_frame.hpp and visualization_manager.hpp files in foxy. It takes quite a lot of time to compile the entire rviz every build. I believe the Moveit working group will also need it for their setup assistant. If you release it in the next distro, we have to wait for not only rviz, but also other dependencies, and considering G distro is not an LTS version, I am worried many distributors might even skip the non-LTS version.

@JaehyunShim  Here's the code I've been working on: https://github.com/mjeronimo/rviz_embed_test. I haven't been able to get it working yet and could use some help debugging what's going on.
Regarding releasing the latest code for Foxy: we should be able to do that. @jacobperron any issues with this?

Hey @JaehyunShim @mjeronimo ,
I managed to get a working implementation of a custom Qt5 Application with a RenderPanel. I had to create a function in the source code of rviz2 and maybe it's not the best option but it works. I have the solution in this repo. Any feedback is apreciated.

@MartiBolet  Awsome! I will test it and let you know if it works now. It will be even more helpful if you send a pull request to https://github.com/ros-visualization/visualization_tutorials from your repo, then other users in the community will also see and use your code.

@MartiBolet
OK, so I read your code and it seems what you did is

instantiate a frame (which is a QMainWindow actually)
get the render panel from that frame
add that render panel to your QMainWindow

but my question here is about how to make a frame using a manager and a renderpanel.

Hey @JaehyunShim ,
Yes that's what it does. Since the error is the instantiation of the VisualizationManager, when there is a window event and tries to resize it, from this comment, I tried to instantiate the VisualizationManager in the same way the rviz2 app does it. However, I couldn't get it work, so the way I found was retrieving the RenderPanel from the VisualizationFrame as a last resort, so yes, I didn't solve that problem i just found a workaround to make a functional version.

@MartiBolet Yeah, I will wait for help from @mjeronimo a bit more. Thanks very much though!

@MartiBolet Thanks for letting us know about your work! I'll have a look at the repo you've provided.

Regarding releasing the latest code for Foxy: we should be able to do that. @jacobperron any issues with this?

I'm assuming we're talking about code on the ros2 branch. We should make sure we maintain API (and preferably ABI) compatibility for any changes being backported to the foxy branch.

@jacobperron We are not talking about backporting but git pulling from the ros2 branch to the foxy branch and releasing it so users can use the newly added features in the foxy distro as well.

@MartiBolet @JaehyunShim I did some more digging and found that the code was crashing in Ogre here:
     void X11EGLWindow::windowMovedOrResized()
    {
        if (mClosed || !mWindow)
        {
            return;
        }

        NativeDisplayType mNativeDisplay = mGLSupport->getNativeDisplay();
        XWindowAttributes windowAttrib;

        if (mIsTopLevel && !mIsFullScreen)
        {
            Window parent, root, *children;
            uint nChildren;

            XQueryTree((Display*)mNativeDisplay, (Window)mWindow, &root, &parent, &children, &nChildren);

            if (children)
            {
                XFree(children);
            }

It was crashing because the XQueryTree call failed with a BadWindow return value. The code doesn't check for an error code from XQueryTree and then attempts to free 'children', which is an uninitialized local variable that holds a random value.
However, this was just a clue and didn't provide the root cause for the mWindow value resulting in a BadWindow error. I had another look at the VisualizationFrame code in rviz that the myviz code is emulating. In the initialize() method there are several calls to app->processEvents: https://github.com/ros2/rviz/blob/ros2/rviz_common/src/rviz_common/visualization_frame.cpp#L246-#L375
I included some of those calls and the code now works. I believe the reason is that processing the message allows the window(s) to be properly initialized. Once initialized in this way, there is no BadWindow error.
I've updated the code here: https://github.com/mjeronimo/rviz_embed_test. I've borrowed some from @MartiBolet's code (thanks again for the help). Hopefully this is a good enough starting point for what you need to do.

@mjeronimo  Thanks a lot. One more thing, the code is actually from https://github.com/ros-visualization/visualization_tutorials/tree/ros2/librviz_tutorial. If you send a pull request to this repository, it will be reviewed & maintained & updated by the community.

Good news @mjeronimo,
I tested your repo and the RenderPanel is created and you can visualize in the MainWindow but I can't change the view, I can't drag the mouse or scroll and zoom in or zoom out. Did this happens to you or it's just me?

@MartiBolet
That's because he didn't add ViewController. Actually, I was thinking, using a pre-made frame is not a bad idea for such reasons. Users can take that easy option if he only adds the function with a RenderPanel type return to the VisualizationFrame class as you did.

Hi @mjeronimo
I would like to ask how it is going with the conversation you had with @jacobperron about the release of the latest rviz_common source code for Foxy? :smiley:
Thank you for your help in advance!
Jaehyun

@JaehyunShim We can backport relevant PRs to Foxy, but at the moment, we have a lot going on with the upcoming ROS 2 Galactic release. It'll take a bit of time to get to this. Thanks for your patience.

@JaehyunShim Thanks for the reminder. I've submitted a backport PR here: https://github.com/ros2/rviz/pull/709. I've successfully tested this change on Foxy with my rviz_embed_test.

@JaehyunShim Change integrated into Foxy branch and bloom released: https://github.com/ros/rosdistro/pull/29963.

@mjeronimo Thank you very much. I will test it when it is available and let you know if it works without issues.

@JaehyunShim  You're welcome. Closing this item.

@mjeronimo
Hi, I test rviz_common and you seem to have not added the "rviz_common/visualization_frame.hpp" file which is mentioned in our comments above. I also checked the foxy branch and it is not on the list. Could I get help with it?
Thanks,
Jaehyun

@mjeronimo
FYI, resource_retriever in the foxy branch will also be updated as retriever.hpp is used in the code in rviz_common. Please let me know if there is anything I can help.
Regards,
Jaehyun

@JaehyunShim I'm currently on vacation through July 21st. Feel free to submit PRs for any missing files and I'll review when I get a chance.

@mjeronimo  Hi thank you very much for your reply. PR is just the code in the ros2 branch. Could you merge it to the foxy branch as it has not hit EOL yet?

@JaehyunShim Feel free to open a PR backporting the changes to the foxy and/or galactic branches and we can review it.

@jacobperron
Thank you very much for your support.

I can see the galactic branch is up to date.
Foxy currently needs the same support (syncing with the ros2 branch).
I do not understand what you mean by sending a PR. It only has the dependency problem (https://github.com/ros/resource_retriever) as it already works in galatic. It only needs bloom release for the dependency (resource_retriever) and merging the main branch of rviz_common to foxy branch.

It can wait if there is other work in priority but I am asking if the Foxy version can also get continuous support as the support for Foxy is until May 2023 (https://docs.ros.org/en/foxy/Releases.html) and it is currently the only existing LTS version.
Thanks,
Jaehyun

Foxy currently needs the same support (syncing with the ros2 branch).

The thing is, we do not really "sync" between the ros2 branch and the older branches.  We carefully backport each change to older versions, being careful of API and ABI concerns.  So it needs someone to actively push it forward.

It can wait if there is other work in priority but I am asking if the Foxy version can also get continuous support as the support for Foxy is until May 2023 (https://docs.ros.org/en/foxy/Releases.html) and it is currently the only existing LTS version.

We do support Foxy, but we rely on the community to put the work into the parts that they are interested in.  In this case, you are specifically interested in the Foxy backport of this, so we are asking for your support in creating a PR that backports the functionality from the ros2 branch to Foxy.

@clalancette
Thank you very much for your explanation! That explanation is very helpful and clear. If that is the case, I would like to ask the following questions.

No backporting for the dependencies too? While more features from ROS1 rviz were added to ROS2 rviz_common, there were changes made also in its dependencies (ex, link). CI will crash if you merge rviz branches without updating the dependencies.

If 1) is possible, the below combination should work since it was working when I downloaded the source code on 23 April and tested.
rviz for e19a0750c4495646183ed819de62c7fea7a2624d commit
resource_retriever for 791becb15061bfb064512a17ddbd341eeb14cef7 commit
Let me go to my office and double-check it works.

Hi @clalancette
OK! I tested 2) and it worked with any issues. You mentioned

being careful of API and ABI concerns

but could I ask about it in more detail? Other than potential CI crashes, is there anything that has to be considered?
Thanks,

(ex, do you have sort of a policy that only certain features can be provided in old distros you can encourage users to use newer distros?)

No, we can backport features to older distributions if it makes sense, but...

but could I ask about it in more detail? Other than potential CI crashes, is there anything else that has to be considered?

We guarantee API and ABI stability within a ROS distribution.  That is, once we do the release, we make sure not break either the programming API, and we make sure not to break the binary ABI (which is the layout of the code and data in memory).  So sometimes when we do backports, we have to make certain changes to the code to make sure it keeps the API and the ABI.  That's why we have to evaluate each code change that gets backported individually.


AutoRest.CSharp static-serializer breaks client interface JsonSerializerSettings implementation

versions:
Type       Extension Name                           Version
core       @microsoft.azure/autorest-core           2.0.4387
extension  @microsoft.azure/autorest.csharp         2.3.82
extension  @microsoft.azure/autorest.modeler        2.3.55
config.yaml:
input-file: N/A - api swagger.json
namespace: N/A - namespace
output-folder: V1
use-datetimeoffset: true
add-credentials: true
sync-methods: none
static-serializer: true
this produces my api client implementation with a static property (among others):
public static JsonSerializerSettings SerializationSettings { get; private set; }

Due to it being a static property, this does not implement the generated property in the service client interface:
JsonSerializerSettings SerializationSettings { get; }

would it be possible to generate the implementation properties as something like this?
private static JsonSerializerSettings _serializationSettings;
public JsonSerializerSettings SerializationSettings => _serializationSettings;

and then, in Initialize(), assign the new JsonSerializerSettings{...} to _serializationSettings instead?

Is static-serializer still an option for AutoRest 3.1.1 (latest)?
I ran into this code-generation issue with version 2.x - the code generated with the static-serializer is incorrect.
It's important to use static serialization and deserialization settings.
If serialization settings are created for each client there's a significant performance impact for each call, since some reflection work, which is cached by the settings, would be done every time a request is made by a client. We noticed that has added about 20ms on average to each request issued by the client. The alternative is to use a singleton client, but since autorest is meant for generating SDKs one cannot always control how the callers will instantiate those generated clients. Also, a singleton client loses the ability to react to DNS changes enabled by using the IHttpClientFactory pattern in Asp.Net Core.
I upgraded to 3.1.1 and the static-serializer option doesn't seem to do anything anymore. It does not appear in this document:
http://azure.github.io/autorest/user/command-line-interface.html
Thanks,
F.

Follow-up to close. Clarified with @pakrym
In AutoRest v3 serialization is done differently; it does not require JsonSerializerSettings and it does not rely on reflection, so the problem goes away. We will migrate our code to use v3; until then we will mitigate the impact of serialization by extending the lifetime of the clients.

Hi autorest  owners - is there any word on fixing this 2-year-old issue for autorest 2.x? I just tried using --static-serializer again on 2.0.4413 and it generates the same incorrect code as reported by @engenb.
I'd like to move on to using 3.x but that's not yet possible for a variety of reasons so I am stuck with the older version. Static serializer settings would eliminate the performance hit associated to the periodic recycling of all rest clients which the service I am working on must perform.


[Dropdown] Performance issue with calling dropdown() on many  elements

I've noticed that there's a big performance difference between using normal <select> elements, and select elements with the 'ui dropdown' class.
In a particular project that I work on, I'm dynamically populating a table when the page loads, with up to 200 rows, where each row contains 2 drop down boxes. This means 400 select boxes on one page.
This page loads significantly slower when I format the select elements as 'ui dropdown' and especially when I call:  $('select.dropdown').dropdown();.
I've prepared a JSFiddle to show the difference in dynamically populating a table with or without the ui dropdown selects: http://jsfiddle.net/costyn/dskvg042/.
Whether showing 400 select boxes on the same page is useful to a user, is another question and I will look into improving the UI to make it more user friendly, but nevertheless it seems there is some performance issue deeper down in semantic-ui which makes it slow to render select boxes.

Initializing a dropdown with pre-existing html allows for greater performance than initializing a dropdown directly on a select element (~190ms vs ~1050ms on my end). Here's your JSFiddle that I changed a bit.
Other than that, you could implement pagination for your table to improve performance, or show a user [a loader] (http://semantic-ui.com/elements/loader.html) while you're preparing your table.

I will try the trick with the pre-existing HTML, instead of building the HTML elements per select. I've already added a loader for the user, so that the user can see that something is happening in the background.
Thanks for your feedback!

Creating the HTML up front works only partially. It does speed up the loading of the page, however to be able to react on the change in selection of the dropbox, I do need to set a unique id/name per select node (to be able to find back the selected values for each select node). Do, the HTML is not so static and needs to be build dynamically after all.
To avoid the long(er) load time, I did review the layout of the page and am now working with 1) a loader indicator and 2) with paging so the number of selects to load is limited and within reason for the user's experience.


Fix links in Katib blog

After this PR: https://github.com/kubeflow/katib/pull/1464 some links have been changed.
/assign @theadactyl @Bobgy @kramachandran @james-jwu
/cc @gaocegege @johnugeorge

/approve

Thanks for the approve @theadactyl.
I think this PR requires your /lgtm also.

/lgtm

/lgtm


Don't snap to commits while scrolling

When scrolling the extension snaps to the nearest commit, this can make scrolling look very jittery when scrolling slowly:

Personally, I'd much rather see half a commit than have the view jitter when I scroll.

yes I can see how that is annoying. I was also not super happy with how it worked. As the link says, it's done like this so the dotted connection lines at the top always reach their target. I now changed the logic so it doesn't snap after scrolling, instead it now prevents natural scrolling and injects custom scrolling speed / steps for any wheel or up/down events. I normally hate it when websites/apps do that but in this case, it still seems like the best solution. I'd be curious what you think! It's now released as version 0.1.3.
However, configurability is always nice so I added an option, git-log--graph.disable-scroll-snapping, which you can set to prevent that and indeed see half commits.

The new scrolling is awesome! Thanks for the change.


Display environment variables when showing the command being run

Even with #5666, when commands are shown in verbose output, there are still some cases where they can’t be run in the terminal. This is because the code is expecting certain environment variables that are provided by cargo. This PR updates the Display impl for ProcessBuilder to show the environment variables in front of the command (on unix), so that the command can be run. Example output:

Note that for workspaces, you will still have to run the command from the workspace root.
I deliberately didn’t update any of the tests yet, because I want to see if this is desired. I also want to see if this can be done on windows, so hopefully someone with experience with that platform can comment.

Thanks for the PR!
It's true yeah that sometimes it's nice to have these baked in so they can be copy-pasted, but I think I'd prefer to solve a few issues first before merging if we merge:

This should have both a Unix and a Windows implementation
I think we may want to gate this on -vv instead of just -v

And I think that should be good enough?

Hey @alexcrichton that all sounds good, I'm just not familiar with windows, so not really sure what to do there. I was reading the answer to this question, and it looks like the cleanest way to pass environment variables to a subprocess is with a command (env) that you have to install.
One thing we could do is just output the environment variables on a separate line, so people can add them manually.
Any thoughts?

Hm so that answer does have at least a solution:
cmd /V /C "set EDITOR=vim&& echo !EDITOR!"

albeit not the greatest script :(
Another possible idea is to split this output onto multiple lines, but that has the unfortunate side effect of maybe getting mixed up with compiler diagnostic output (which Cargo doesn't synchronize with currently). I'm unfortunately also not sure what the best solution here would be...

@alexchrichton I take it stdin.lock() wouldn't help, because they are different processes.
@Marwes, you use windows — what would you do here?

Yeah unfortunately stdin.lock() wouldn't help the cross-process issue here

@mikeyhew I use git bash for this reason and many others instead of cmd, so I am not any wiser of what's the best idea here (That SO link is the one I have used in the rare cases that I have needed it)

@mikeyhew hm do you have thoughts for how we might land this? Do you think it's important enough to land a unix-only implementation?

@alexcrichton ya, I think we should definitely support it at least on unix. For windows, I'm leaning toward the cmd option, because it can be pasted into the terminal and run:
cmd /c "set FOO=foo && BAR=bar && rustc --flag1 --flag2 file"

Ok makes sense to me, @rust-lang/cargo do y'all have thoughts on the feature here? It's pretty wonky (albeit not impossible) to implement this on Windows but wanted to check to see if anyone feels we should do something different here!

I absolutely want to see this land, to ensure that people can always re-run commands.
Regarding an implementation for Windows using cmd, I'd be deeply concerned about getting quoting correct to allow for copy-pasting.

Seems very useful! Does it make sense to show env only with -v -v, double verbose?
I also don’t think that we should go out of our way to make this copy-pastable on Windows. So, using VAR=foo binary syntax on windows seems fine by me: the user can adjust the command line themselthes depending on the shell being used.

I like gating it on -vv. I also think that if we think that the copy-pasting facility is useful on Linux and OSX, we should try to figure out how to make it work on Windows. I don't love that these micro-decisions often result in a noticeably worse user-experience on Windows in aggregate, and I don't think it would be too hard to figure out how to make this work properly.

Ok thanks for the input! @mikeyhew sounds like a "yes" to let's do the windows weird cmd syntax :)
(and then test it a bit for quoting and whatnot)

@mikeyhew ping on this, will you be able to implement the sytnax for windows?

@alexcrichton I've been busy lately, so that's why I haven't gotten to this yet. I don't have a windows machine, so I'd need to rely on CI to run tests for me, but I'll try that this coming week unless someone else wants to do the windows version.

I ran into another request for this from someone trying to debug builds, and I'd like to reopen it in the hopes that someone may wish to address it.
To avoid the perfect becoming the enemy of the good: I do think a UNIX implementation would be great to have.

:umbrella: The latest upstream changes (presumably #6416) made this pull request unmergeable. Please resolve the merge conflicts.

Along with a rebase, this is currently failing CI.

@dwijnand this never passed CI, since I didn't update the existing tests


Regression in v0.38.0 when checking object properties in conditionals

This appears related to #1879, but another bug was added in v0.38.0:
type ExactObj = {|
    a: string
|};

const someObj: ExactObj = {a: 'string'};
const test1 = someObj.COMPLAIN_PLZ; // expected error
if (someObj.COMPLAIN_PLZ) { // bug: should complain

}

// Errors in 0.37.4, not in 0.38.0 or master.
if (someObj.COMPLAIN_PLZ === true) { // bug: should complain.

}

if (Boolean(someObj.COMPLAIN_PLZ)) { // expected error

}

Try it.
This special-casing of conditionals appears also related to https://github.com/facebook/flow/issues/3309.
I don't see why conditionals should have special rules; someObj.missingProperty should be an error regardless of where it's written, and we should be encouraging hasOwnProperty or in checks.

This is clearly not a bug or regresseion, it's even mentioned in the changelog:

We've relaxed sentinel checks to allow you to check unknown properties. This is consistent with other conditionals

My apologies, missed that; came up as it appears some refinement being done relates to #3309.

To be honest, I don't understand this change too

We've relaxed sentinel checks to allow you to check unknown properties. This is consistent with other conditionals

I cannot find a reason why would that be relaxed for Exact types.
It makes something like this fragile:
type BagOfFlags = {|
  a: boolean,
  b: boolean,
  // REMOVED c: boolean
|}

declare var bag: BagOfFlags;

if (bag.c) { // would be nice not to typecheck after c is REMOVED
  // ...
}

IMO, it should not be relaxed even for non exact types, since it leads to dangerous implicit any like in #3309 .
Can this be made configurable in flowconfig?

With exact objects you might want to do this:
type T = {| foo: string |} | {| bar: string |};
declare var a: T;
const x: ?string = a.foo;

Is that possible to make this configurable? @vkurchatkin


fix(cli): missing failure counts when there is failedHooks

Motivation/Description of the PR

Failure count is wrong calculated when there is failed hook.

Applicable helpers:

[ ] Playwright
[ ] Puppeteer
[ ] WebDriver
[ ] REST
[ ] FileHelper
[ ] Appium
[ ] TestCafe

Applicable plugins:

[ ] allure
[ ] autoDelay
[ ] autoLogin
[ ] customLocator
[ ] pauseOnFail
[ ] coverage
[ ] retryFailedStep
[ ] screenshotOnFail
[ ] selenoid
[ ] stepByStepReport
[ ] stepTimeout
[ ] wdio
[ ] subtitles

Type of change

[ ] :fire: Breaking changes
[ ] :rocket: New functionality
[x] :bug: Bug fix
[ ] 🧹 Chore
[ ] :clipboard: Documentation changes/updates
[ ] :hotsprings: Hot fix
[ ] :hammer: Markdown files fix - not related to source code
[ ] :nail_care: Polish code

Checklist:

[x] Tests have been added
[ ] Documentation has been added (Run npm run docs)
[ ] Lint checking (Run npm run lint)
[x] Local tests are passed (Run npm test)

@kobenguyent I'm sorry for a delay. Just tried it with the 3.6.10 stable and it works well.
Tested with:

failed hooks + failed steps
failed steps only
failed hooks only
passed everything

Thank you very much.


resume training falid

Bug description
resume traning failed, when every_n_train_steps is equal to val_check_interval
How to reproduce the bug
checkpoint_callback = ModelCheckpoint(
        ***
        every_n_train_steps=config['val_check_interval'],
    )
    trainer = pl.Trainer(
        ***
        val_check_interval=config['val_check_interval'],

    )

### Error messages and logs

def validation_epoch_end(self, outputs):
    # pdb.set_trace()
    imgs = np.vstack(outputs)

File "/data_local/trainer.py", line 1342, in _call_lightning_module_hook
output = fn(*args, **kwargs)
File "/data_local//train.py", line 90, in validation_epoch_end
imgs = np.vstack(outputs)
outputs is empty

### Environment

<details>
  <summary>Current environment</summary>

#- Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow):
#- PyTorch Lightning Version (e.g., 1.5.0):
#- Lightning App Version (e.g., 0.5.2):
#- PyTorch Version (e.g., 1.10):
#- Python version (e.g., 3.9):
#- OS (e.g., Linux):
#- CUDA/cuDNN version:
#- GPU models and configuration:
#- How you installed Lightning(conda, pip, source):
#- Running environment of LightningApp (e.g. local, cloud):

</details>

### More info

_No response_

Closing due to lack of provided information.
If validation_epoch_end doesn't receive outputs, it is probably because none were returned in the validation_step.


Master

fix spelling errs
add [unowned self] to prevent strong pointer

added <#doSth#> to enhance productivity

Thank you for your Pull Request, but there are some issues preventing me from merging it.
Spelling issues are fixed by #10.
Using self in dispatch_async call is not an error, please check http://stackoverflow.com/questions/21987067/using-weak-self-in-dispatch-async-function/21988407#21988407
Considering above points I don't believe it should be merged.

Thanks for your guiding!


Fetch Data Source Info from EDI not working on empty method step.

Fetch Data Source Info from EDI not working on empty method step.

Closed in release 2024.01.03.


feat: [IDP]: Improved the what's supported section for custom actions

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6703629958a34927dccb7723--harness-developer.netlify.app

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: Debanitrkl:x: OrkoHunterYou have signed the CLA already but the status is still pending? Let us recheck it.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://67036865f9b53330a318d761--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://67036887655e9430446005ab--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://670368a7f42be53376e02eb0--harness-developer.netlify.app


Release Google.Maps.Routing.V2 version 1.0.0-beta01

Changes in this release:
Initial release.

Created release for Google.Maps.Routing.V2-1.0.0-beta01


update data submodule

new versions of data tables have been pushed to Sarah's GitHub

Rmd runs without issues


React Native: Unable to resolve module child_process

Hi
I'm trying to install lorem-ipsum in my react-native project, but I'm getting the following error from my bundler:

error: bundling failed: Error: Unable to resolve module child_process from /Users/jenskuhrjorgensen/Documents/Workspace/journl-incontinence/mobile/node_modules/lorem-ipsum/dist/index.js: Module child_process does not exist in the Haste module map

I've tried to restart the metro bundler with npm run start -- --reset-cache and remove and re-install node_modules, but to no avail.
Any help would be appreciated! :)
Environment:
"react": "16.6.3"
"react-native": "0.58.5"
"lorem-ipsum": "2.0.0-alpha.7"

Until this issue is resolved, is it possible to downgrade to 1.0.6. It's functionally the same.

Just wanted to follow-up to say that I looked into this issue and it seems to be a problem with React Native. See here for some discussion https://github.com/ethers-io/ethers.js/issues/268
That said, there was an issue with the builds where code meant to be executed in a server context (as part of the included CLI) was being included in the client libraries. That's sorted out now. I don't have a React Native project to test this with, but it should work now after the updates in https://github.com/knicklabs/lorem-ipsum.js/pull/34.

@knicklabs I get the same error in a project that's rendered server-side -- so not strictly React Native. Not sure if it matters much, but the rendering is handled by razzle

Hi @karolis-adapt, are you using the alpha version (v2.0.0-alpha.x) or version the latest stable release (v2.0.0)

@knicklabs was running latest stable. Figured task being closed meant it's released. If the fix is only in alpha, then pay no attention to my earlier comment ;)

This fix should be in version 2.0.0. Will investigate further, thanks. The child process module should only be imported in the executable script for the command line program. I'll investigate further.

I'm getting the same error in a webpack build with 2.0.0.
The error was happening with 1.0.6 as well but adding browser: { child_process: false } to package.json fixed it. The same fix doesn't have any effect in 2.0.0

@nocarroll Thanks for letting me know what you were seeing. That helped track down the issue.


review organization of craniofacial bone development

many terms under craniofacial development involve bone development but these terms are not under skeletal development
we need to review these and make sure the terms that belong under skeletal development are there

placement agrees with how UBERON is structured


Texthero

I am still trying to create more stories for hero text

Hi @HThanki , @robota-x and @DeagoBrowne , this pull request is ready to be be merged. Please review it for me and let me know if it needs any changes. Otherwise merge it to the main, please.


Mouse scrolling...

What is your question?
How could I detect mouse scrolling?
(Not a middle click but the scrolling...)

But nobody came...


Adjust privileges for /_admin/cluster/numberOfServers API

Scope & Purpose
Requested by popular vote:
Re-enable access to GET /_admin/cluster/numberOfServers for all users by default. Requests to PUT /_admin/cluster/numberOfServers require admin user privileges. This restores the pre-3.7 behavior.
In contrast to pre-3.7 behavior, the --server.harden option now can be used to restrict access to GET /_admin/cluster/numberOfServers to admin users, too. This can be used to lock down this API for non-admin users entirely.
Documentation PR: https://github.com/arangodb/docs/pull/488

[x] Bug-Fix for devel-branch (i.e. no need for backports?)
[x] The behavior in this PR can be (and was) manually tested (support / qa / customers can test it)
[x] The behavior change can be verified via automatic tests

Testing & Verification
This PR adds tests that were used to verify all changes:

[x] Added new integration tests (i.e. in shell_server / shell_server_aql)

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/10859/

Tests blue except unrelated leftover arangosearch view


Ogen generated code instruments OTEL Http Metrics following semantic conventions

Description
Would like to have the ogen generated code instrument metrics that are currently marked as stable in Semantic Conventions for HTTP Metrics

http.server.request.duration
http.client.request.duration

References

https://opentelemetry.io/docs/specs/semconv/http/http-metrics/

Please use go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp for metrics that follow semantic conventions, they will work perferctly with ogen.
I will update ogen/example repo with more details like using LabelerFromContext and WithSpanNameFormatter with ogen.
Thank you for bringing this issue.

For now please refer to
https://github.com/ogen-go/example/blob/4391e6af6a14aed4442ede1cfc355b19188ad763/cmd/api-server/main.go#L41-L52
https://github.com/ogen-go/example/blob/4391e6af6a14aed4442ede1cfc355b19188ad763/internal/httpmiddleware/httpmiddleware.go#L84-L102


Kth distance - POTD | 2-Nov-2024

Kth distance
Link
Difficulty: Easy
Given an unsorted array arr and a number k which is smaller than size of the array. Find if the array contains duplicates within k distance.
Examples:
Input: arr[] = [1, 2, 3, 4, 1, 2, 3, 4] and k = 3
Output: false
Explanation: All duplicates are more than k distance away.
Input: arr[] = [1, 2, 3, 1, 4, 5] and k = 3
Output: true
Explanation: 1 is repeated at distance 3.

Constraints:

1 ≤ arr.size() ≤ 106
1 ≤ k < arr.size()
1 ≤ arr[i] ≤ 105

Solved
def checkDuplicatesWithinK(self, arr, k):
        # your code
        hs={}
        for i in range(len(arr)):
            if arr[i] not in hs:
                hs[arr[i]]=[]
            hs[arr[i]].append(i)
        for v in hs.values():
            if len(v)>1:
                for i in range(len(v)-1):
                    if v[i+1]-v[i]<=k:
                        return 1
        return 0


Flickering nameplate issues

Hello! The nameplates seem to flicker rapidly and also sometimes just don't work. Are these known issues?

thanks for letting me know. shall investigate and attempt to fix when i have time. might not be 'til the end of april tho ;-;


[#5001] Reflect the switching agent event on the chart

Codecov Report

Merging #5016 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5016      +/-   ##
==========================================
- Coverage   40.78%   40.78%   -0.01%
==========================================
  Files        2649     2649
  Lines       79284    79284
  Branches    10717    10717
==========================================
- Hits        32336    32334       -2
- Misses      44017    44019       +2
  Partials     2931     2931

Impacted Files
Coverage Δ

...vercorp/pinpoint/rpc/packet/ClientClosePacket.java
55.55% <0%> (-11.12%)
:arrow_down:

...corp/pinpoint/rpc/stream/StreamChannelManager.java
70.68% <0%> (-1.73%)
:arrow_down:

...orp/pinpoint/rpc/server/DefaultPinpointServer.java
78.47% <0%> (-1.39%)
:arrow_down:

...m/navercorp/pinpoint/profiler/AgentInfoSender.java
75.67% <0%> (-0.91%)
:arrow_down:

...point/rpc/client/DefaultPinpointClientHandler.java
72.61% <0%> (+0.31%)
:arrow_up:

...om/navercorp/pinpoint/rpc/codec/PacketDecoder.java
63.82% <0%> (+2.12%)
:arrow_up:

...tor/metric/datasource/DefaultDataSourceMetric.java
78.12% <0%> (+3.12%)
:arrow_up:

...rc/main/java/com/navercorp/pinpoint/test/Item.java
68.96% <0%> (+6.89%)
:arrow_up:

Continue to review full report at Codecov.

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


Missing Documentation - 2FA Lockout

This should be in the GitHub documentation, when users lock themselves out of their Umbrel.

Download and install putty - https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
Open putty and type in umbrel.local for the hostname.
Click Open or hit Enter.
Then type umbrel for the username.
Then type your password, it's same password you use to log in to the Umbrel dashboard.
***If you haven't yet run through the setup process, the password will be set to moneyprintergobrrr.
Then type nano umbrel/db/user.json - This will open the json file for editing.
Using the down arrow, scroll down until you see " "otpUri": "otpauth://totp/umbrel?secret=blblablabla&period=30&digits=6&algorithm=SHA1&..." - or similar.
Delete the line so it looks like “otpUri”: “”.
Then hit Ctrl-O then Enter to save the file and lastly Ctrl-X to close the file.
Type logout and hit enter to close Putty.
Login to your umbrel normally, be sure to re-enable 2FA after regaining access.

References:

https://community.getumbrel.com/t/2fa-recovery-lost-phone-no-code/5135/36?u=wesmsl
https://github.com/getumbrel/umbrel-os

I think this is more of a workaround/hack and including it in the official docs would mean the security of 2FA is compromised and they know it.
Anyways this is just a backdoor nothing else they might be removing this in the future realise.

It's also on the Official Troubleshooting guide https://community.umbrel.com/t/official-umbrel-troubleshooting-guide-and-faq/9873


Include the required files (ex Makefile) to be able to cross-compile on x86

There is nothing needed to cc on x86. Managed to do it using this test kernel module: https://github.com/agherzan/rtl8192cu


add logoutUrl

send logout to server for those who want that. easy to do and no harm done

done https://github.com/SpoonX/aurelia-authentication/pull/139


Review Picture/Canvas system

The current picture/canvas graphics system is not really optimized, with over(mis)use of Bitmap objects. This causes the system to be slow and not really flexible.

Moved forward


Failed to lower scalar [*/] tensor

          Out of the 8 cases ({+, -, *, /} × { LHS, RHS }), the following 2 cases does not work:

scalar * tensor fails to compile
scalar / tensor gives incorrect results by computing tensor / scalar instead

I'm still investigating which lines of code drive such conversions.  In to_tt_pass.py, I only see conversions for aten.*.Tensor but not aten.*.Scalar.  There is also a hook for relational ops (relational_scalar_ops) but not for arithmetic ops.
Originally posted by @jdh8 in https://github.com/tenstorrent/pytorch2.0_ttnn/issues/100#issuecomment-2315009036

@kevinwuTT, do you know where the conversion of tensor-scalar ops (such as mul.Scalar) take place?  I tried git grep -F '.Scalar' **/*.py but was out of luck.
tests/lowering/misc/test_if.py:    assert target_0.count(torch.ops.aten.gt.Scalar) == 1
torch_ttnn/passes/lowering/to_tt_pass.py:    torch.ops.aten.eq.Scalar: ttnn.eq,
torch_ttnn/passes/lowering/to_tt_pass.py:    torch.ops.aten.lt.Scalar: ttnn.lt,
torch_ttnn/passes/lowering/to_tt_pass.py:            if node.target == torch.ops.aten.rsub.Scalar:

If they're not found, then I don't think they're implemented yet. Also, sometimes the following happens before we get our passes:
out = tensor * 3

Intuitively, you would think this gets lowered to:
out = aten.mul.Scalar(tensor, 3)

But instead, torch lowers this into something like:
fill = aten.fill([], 3)
out = aten.mul.Tensor(tensor, fill)

I'm not sure if there's a way to change this behavior, but this might be a reason why some scalar ops are being lowered even though there are no direct scalar conversions in our passes. Is this what you're seeing?

Yeah, I see tensor-scalar ops lowered anyhow despite of lacking an explicit conversion.  PyTorch probably converts the scalars to tensors in advance.


feat: init for capturing system resources

Overview

Test Plan

Changelog

Review requests

Risk assessment

Would it make sense to implement this as a systemd service running on the robot?

Yes, I think it makes sense to run this periodically as a systemd service. What frequency were you thinking?

I was going to try every second and see what the performance impact was. But with your suggestion of capturing the CPU seconds, it likely doesn't need to be that frequent.

If that happened on its own, something's definitely going wrong and we need to look into it.
If that happened when you hit Ctrl+C to stop the program, it's harmless but we should probably fix it to make it less confusing. I guess the normal way to handle that is to catch KeyboardInterrupt at the top level.

When I manually tested, I got: 2024-07-03 18:57:16,258 - __main__ - INFO - Starting system resource tracker... ^C2024-07-03 18:57:33,090 - __main__ - INFO - System resource tracker is stopping. Traceback (most recent call last): File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main return _run_code(code, main_globals, None, File "/usr/lib/python3.10/runpy.py", line 86, in _run_code exec(code, run_globals) File "/opt/opentrons-robot-server/performance_metrics/system_resource_tracker/__main__.py", line 25, in <module> time.sleep(tracker.refresh_interval) KeyboardInterrupt
is the traceback expected?

@skowalski08, fixed with https://github.com/Opentrons/opentrons/pull/15542/commits/89c687eaa957c1758686d6e45930569893000d1f


[Bug] Echarts can't accurately(maybe naturally) handle MAC touchpad gestures.

Version
5.3.3
Link to Minimal Reproduction
No response
Steps to Reproduce
1、Set dataZoom like this:
  {
    type: 'slider',
    show: true,
    xAxisIndex: [0],
    start: 1,
    end: 35
  },
  {
    type: 'slider',
    show: true,
    yAxisIndex: [0],
    left: '93%',
    start: 29,
    end: 36
  },
  {
    type: 'inside',
    xAxisIndex: [0],
    start: 1,
    end: 35
  },
  {
    type: 'inside',
    yAxisIndex: [0],
    start: 29,
    end: 36
  }

Current Behavior
When I use MAC touchpad to scale and move it, I just can't move it all direction. It just treat the gesture as scaling instead moving.
Expected Behavior
I want to move the chart through the gesture all direction(up、down、left and right). And when I separate my fingers, I want to scale it. Just like Chrome DevTools's timeline in performance panel.

Environment
- OS:
- Browser:
- Framework:

Any additional comments?
No response

And I tried the optionzoomOnMouseWheel: 'ctrl', when I use touchpad. It works when scale but doesn't work when move.

And I find relative code in file src/component/helper/RoamController.ts.
private _mousewheelHandler(e: ZRElementEvent) {
        const shouldZoom = isAvailableBehavior('zoomOnMouseWheel', e, this._opt);
        const shouldMove = isAvailableBehavior('moveOnMouseWheel', e, this._opt);
        const wheelDelta = e.wheelDelta;
        const absWheelDeltaDelta = Math.abs(wheelDelta);
        const originX = e.offsetX;
        const originY = e.offsetY;

        // wheelDelta maybe -0 in chrome mac.
        if (wheelDelta === 0 || (!shouldZoom && !shouldMove)) {
            return;
        }

        if (shouldZoom) {
            // Convenience:
            // Mac and VM Windows on Mac: scroll up: zoom out.
            // Windows: scroll up: zoom in.

            // FIXME: Should do more test in different environment.
            // wheelDelta is too complicated in difference nvironment
            // (https://developer.mozilla.org/en-US/docs/Web/Events/mousewheel),
            // although it has been normallized by zrender.
            // wheelDelta of mouse wheel is bigger than touch pad.
            const factor = absWheelDeltaDelta > 3 ? 1.4 : absWheelDeltaDelta > 1 ? 1.2 : 1.1;
            const scale = wheelDelta > 0 ? factor : 1 / factor;
            checkPointerAndTrigger(this, 'zoom', 'zoomOnMouseWheel', e, {
                scale: scale, originX: originX, originY: originY, isAvailableBehavior: null
            });
        }

        if (shouldMove) {
            // FIXME: Should do more test in different environment.
            const absDelta = Math.abs(wheelDelta);
            // wheelDelta of mouse wheel is bigger than touch pad.
            const scrollDelta = (wheelDelta > 0 ? 1 : -1) * (absDelta > 3 ? 0.4 : absDelta > 1 ? 0.15 : 0.05);
            checkPointerAndTrigger(this, 'scrollMove', 'moveOnMouseWheel', e, {
                scrollDelta: scrollDelta, originX: originX, originY: originY, isAvailableBehavior: null
            });
        }
    }

Can we set a callback when mouse wheel ? So then I can use a custom function to handle the moving and scaling.


ForeignField.toBits() discards high limbs of unreduced elements for input bit lengths <  176

https://github.com/o1-labs/o1js/blob/ea199efea8f393fa72a5d672762812a88989efec/src/lib/provable/foreign-field.ts#L356-L360
This behaviour is incorrect since we don't prove the higher limbs are zero! The simple fix is to add assertions that they are.

closed by #1617


Is the save button cosmetic?

Describe the bug
I saved and refreshed my browser and my entire project was erased.
Link to the blitz that caused the error
https://stackblitz.com/edit/angular-fvegeq
Steps to reproduce
spend two hours on a tutorial
press the save button on the top left
refresh the page
lose all progress
Expected behavior
the project would be saved
Parity with Local

[ ] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
No response
Platform
Browser name  = Chrome
Full version  = 97.0.4692.99
Major version = 97
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.99 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 129803168,
  "usedJSHeapSize": 98769316,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Hash = 5df97b5e61f923919ea927c406a4806b792de8c6

Additional context
No response

@thomassten I'm so sorry this happened to you. Any idea how large your project was? Any chance it was larger than 10mb?


Frontend Changes for Relaunch

Here's what we just discussed for ousd.com:

[x] Change the top banner to say something like "OUSD has relaunched with independent audits and a renewed focus on security."
[x] Change the top banner color from blue to black (with white text).
[x] Show the top banner on all screens (including /stake).
[x] Add https://zpl.io/bzKrQLA to all dapp screens (/mint and /stake).
[x] Hide the APY banner on all mobile screens.
[x] Remove the big red alert from /mint.

Pull request for this: https://github.com/OriginProtocol/origin-dollar/pull/476

Pull request for this: https://github.com/OriginProtocol/origin-dollar/pull/476

done via: https://github.com/OriginProtocol/origin-dollar/pull/476

done via: https://github.com/OriginProtocol/origin-dollar/pull/476


[WIP] exit_store_metadata: use repos from pulp_pull in exit plugins if available

Not sure if tests were updated correctly, but actual code was tested with next branch and works

Let me look at the docs for how this was supposed to work.

The way this is meant to work is that tag_from_config updates the tag_conf and group_manifests updates the push_conf. Then, pulp_sync should update push_conf with information about Pulp. When merged together we should get pull specifications for each tag the manifest list is accessible through, although it will also include the v2 docker registry.
Because delete_from_registry needs to know details of the image manifests in the docker registry, we'll need to have exit_store_metadata_in_osv3 act differently depending on whether it is running in the orchestrator or the worker build.
Orchestrator build: use pulp registries if there are any, otherwise use all registries
Worker build: use all registries

we'll need to have exit_store_metadata_in_osv3 act differently depending on whether it is running in the orchestrator or the worker build

Should it be an additional param to exit_store_metadata_in_osv3 plugin, or just checking for pulp_pull results in exit plugins is sufficient? In the latter case it should be enough to add a comment

I don't think checking for pulp_pull is the best way. I'd suggest either checking for orchestrate_build (make it's plugin key a constant), or being told by parameter. @lcarva?

I don't think checking for pulp_pull is the best way. I'd suggest either checking for orchestrate_build (make it's plugin key a constant), or being told by parameter.

I think checking for orchestrate_build seems reasonable. Maybe a helper utility function in utils.py is worth adding.

Updated _get_repositories() to check if its in orchestrator build flow or not and added a test for that

Now Travis fails on test_orchestrate_build, but I can't reproduce it locally :/

I have absolutely no idea why tests are failing in travis...

Tests fixed, don't import OrchestrateBuildPlugin - this seems to break the tests :(

Needs re-basing.

Rebased on master

Fix for unreleased bug, no need for release notes update.


@poperty() does not work with private class property

Describe the bug
you cannot apply @Property() decorator to a pivate class property when using # syntax to mark the private class property.
Stack trace
...

To Reproduce
Steps to reproduce the behavior:

create an entity using @Entity() decorator
create a private property of the class using #privateProperty
add the @Property () decorator above #privateProperty

Expected behavior
decorator is allowed here.
Additional context
This would be useful in order to then be able to have getters with the same naming.
Versions

Dependency
Version

node
?

typescript
?

mikro-orm
?

your-driver
?

https://mikro-orm.io/docs/entity-constructors#using-native-private-properties


README: link to yaegi repo itself

thanks for mentioning yaegi btw!

Sure thing! It’s a very cool project