dateFormat doesnt work as expected

If I set the "value" of the input field in the format "d/m/Y" and dateFormat is "d/m/Y" the input field will convert the value to format "m/d/Y" (it should be "d/m/Y").
Try with the following date: 3/8/2016 <-> 8/3/2016

@dalpras is this using the latest flatpickr (2.0-rc5)?

The date string supplied in input's value or the defaultDate option must have days come after months come after years, regardless of your chosen dateFormat


Footer Improved

@SSHSRN I have improved the footer, please merge this into main

Mention the issue this pr closes, so that it will be easier to award you points!

Issue no. 70

closes #70

Thanks for the contribution!


cmd/go: -cover stdout format is not consistent between failed & pass

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

$ go version
go version go1.14.2 windows/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\\AppData\Local\go-build
set GOENV=C:\Users\\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\Chris\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=c:\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=c:\go\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\\AppData\Local\Temp\go-build342408862=/tmp/go-build -gno-record-gcc-switches

What did you do?
Run go test -cover on any set of packages including a failed tests.
What did you expect to see?
$ go test -count=1 -cover -tags="sample" github.com/digitalocean/gocop/sample/...
# cover github.com/digitalocean/gocop/sample/failbuild
2020/05/14 09:18:17 cover: C:\Users\Chris\dev\code\do\gocop\sample\failbuild\broken.go: C:\Users\Chris\dev\code\do\gocop\sample\failbuild\broken.go:5:1: expected declaration, found fun
--- FAIL: TestWillFail (0.00s)
    failing_test.go:14: number does equal eleven
--- FAIL: TestWillFailComplex (0.00s)
    --- FAIL: TestWillFailComplex/my_simple_test (0.00s)
        failing_test.go:37: 423 (int) to equal 10 (int)
            failing_test.go:37
    --- FAIL: TestWillFailComplex/my_simple_test2 (0.00s)
        failing_test.go:37: 517 (int) to equal 12 (int)
            failing_test.go:37
FAIL
FAIL    github.com/digitalocean/gocop/sample/fail       0.028s  coverage: 100.0% of statements
FAIL    github.com/digitalocean/gocop/sample/failbuild [build failed]
ok      github.com/digitalocean/gocop/sample/flaky      0.024s  coverage: [no statements]
?       github.com/digitalocean/gocop/sample/numbers    [no test files]
ok      github.com/digitalocean/gocop/sample/pass       0.018s  coverage: 100.0% of statements
ok      github.com/digitalocean/gocop/sample/pass/nostatements  0.025s  coverage: [no statements]
FAIL

What did you see instead?
$ go test -count=1 -cover -tags="sample" github.com/digitalocean/gocop/sample/...
# cover github.com/digitalocean/gocop/sample/failbuild
2020/05/14 09:18:17 cover: C:\Users\Chris\dev\code\do\gocop\sample\failbuild\broken.go: C:\Users\Chris\dev\code\do\gocop\sample\failbuild\broken.go:5:1: expected declaration, found fun
--- FAIL: TestWillFail (0.00s)
    failing_test.go:14: number does equal eleven
--- FAIL: TestWillFailComplex (0.00s)
    --- FAIL: TestWillFailComplex/my_simple_test (0.00s)
        failing_test.go:37: 423 (int) to equal 10 (int)
            failing_test.go:37
    --- FAIL: TestWillFailComplex/my_simple_test2 (0.00s)
        failing_test.go:37: 517 (int) to equal 12 (int)
            failing_test.go:37
FAIL
coverage: 100.0% of statements
FAIL    github.com/digitalocean/gocop/sample/fail       0.028s
FAIL    github.com/digitalocean/gocop/sample/failbuild [build failed]
ok      github.com/digitalocean/gocop/sample/flaky      0.024s  coverage: [no statements]
?       github.com/digitalocean/gocop/sample/numbers    [no test files]
ok      github.com/digitalocean/gocop/sample/pass       0.018s  coverage: 100.0% of statements
ok      github.com/digitalocean/gocop/sample/pass/nostatements  0.025s  coverage: [no statements]
FAIL

The same behavior is observed via json formatting.

We wrote a tool, [https://github.com/digitalocean/gocop|GoCop], to enable us to identify and track flaky tests. It is designed to parse stdout of go test so then we can redirect the output to file during CI runs, use the tool to identify packages which failed and attempt to rerun them N times to determine if they are flaky. We also use this tool to persist the test outcome per package to a Postgres database.
When tests fail, the coverage % output being inconsistently placed leads to data that is missed by the tool. When considering flakiness of a package, the coverage info is something we want to track regardless of the package result.

I submitted a change to address this issue, I will update the change with integration tests as requested.
https://go-review.googlesource.com/c/go/+/233617/1

/cc @bcmills @jayconrod @matloob

As I asked on the CL review: why do we believe that the coverage numbers are meaningful for failed tests?
I suspect that in practice the coverage for failed tests will be systematically lower than for passing tests, because many tests use t.Fatalf or similar on failure — skipping the remainder of the test (and any associated coverage for that test).
So it generally will not be meaningful to compare coverage between two test runs with different failing tests or different failure modes — and if you have a flaky test with a consistent failure mode over time, why not fix the test instead of worrying about its coverage?

@bcmills Thanks for the question. The way I see it, the coverage data reported for a test run is unique to each test run and should be recorded regardless of the outcome of a test. The coverage being potentially less for a failed test run is no different than coverage being less for a passing run if -short is used. Or the coverage being less based on the build constraints that were used to execute the tests. Test coverage can also differ for different platforms. Each run of a suite of tests has the possibility of having a different coverage % due to many factors.
If the expectation is that the coverage % is always reflective of the parameters/factors of the test execution, then there is no logical reason to have inconsistencies between reporting this value based on the outcome of the execution.

FWIW, I agree that reporting coverage % on failure is more likely to be misleading than helpful. If the tests are failing, the coverage doesn't mater. And if they are failing early, the coverage will be somewhat meaningless. Doesn't seem worth the churn.

@rsc the same then could be said for execution duration, could it not?

Maybe, but "how long did it run before it failed?" is a more meaningful question than "what level of code coverage did it achieve before it failed?"
This discussion kind of trailed off, but I think the rough consensus here is that the output should be left as is.


Import data that is in JSON into Teslamate

Hi,
Before I have been using the API call
https://owner-api.teslamotors.com/api/1/vehicles/:id/vehicle_data
To log data BEFORE I found teslamate. I've got data that looks like this going back several months since I got my car.
Am I able to read this into the database somehow to fill up the gaps from before I was using teslamate to now?
  "response": {
    "id":<PHONE_NUMBER>7987462,
    "user_id": 134950,
    "vehicle_id": 163057375,
    "vin": ":vin",
    "display_name": ":name",
    "option_codes": "AD15,AF02,AH00,APF0,APH2,APPA,AU00,BCMB,BP00,BR00,BS00,BTX4,CC02,CDM0,CH05,COUS,CW02,DRLH,DSH7,DV4W,FG02,FR01,GLFR,HC00,HP00,IDBO,INBPB,IX01,LP01,LT3B,MDLX,ME02,MI02,PF00,PI01,PK00,PMBL,QLPB,RCX0,RENA,RFPX,S02B,SP00,SR04,ST02,SU01,TIC4,TM00,TP03,TR01,TRA1,TW01,UM01,USSB,UTAB,WT20,X001,X003,X007,X011,X014,X021,X025,X026,X028,X031,X037,X040,X042,YFFC,SC05",
    "color": null,
    "tokens": [
      ":token1",
      ":token2"
    ],
    "state": "online",
    "in_service": false,
    "id_s": ":ids",
    "calendar_enabled": true,
    "api_version": 6,
    "backseat_token": null,
    "backseat_token_updated_at": null,
    "charge_state": {
      "battery_heater_on": false,
      "battery_level": 74,
      "battery_range": 186.57,
      "charge_current_request": 48,
      "charge_current_request_max": 48,
      "charge_enable_request": true,
      "charge_energy_added": 29.64,
      "charge_limit_soc": 90,
      "charge_limit_soc_max": 100,
      "charge_limit_soc_min": 50,
      "charge_limit_soc_std": 90,
      "charge_miles_added_ideal": 117.0,
      "charge_miles_added_rated": 91.5,
      "charge_port_cold_weather_mode": null,
      "charge_port_door_open": false,
      "charge_port_latch": "Engaged",
      "charge_rate": 0.0,
      "charge_to_max_range": false,
      "charger_actual_current": 0,
      "charger_phases": null,
      "charger_pilot_current": 48,
      "charger_power": 0,
      "charger_voltage": 0,
      "charging_state": "Disconnected",
      "conn_charge_cable": "<invalid>",
      "est_battery_range": 146.18,
      "fast_charger_brand": "<invalid>",
      "fast_charger_present": false,
      "fast_charger_type": "<invalid>",
      "ideal_battery_range": 238.93,
      "managed_charging_active": false,
      "managed_charging_start_time": null,
      "managed_charging_user_canceled": false,
      "max_range_charge_counter": 0,
      "not_enough_power_to_heat": false,
      "scheduled_charging_pending": false,
      "scheduled_charging_start_time": null,
      "time_to_full_charge": 0.0,
      "timestamp":<PHONE_NUMBER>159,
      "trip_charging": false,
      "usable_battery_level": 74,
      "user_charge_enable_request": null
    },
    "climate_state": {
      "battery_heater": false,
      "battery_heater_no_power": false,
      "climate_keeper_mode": "off",
      "driver_temp_setting": 20.0,
      "fan_status": 0,
      "inside_temp": 29.0,
      "is_auto_conditioning_on": false,
      "is_climate_on": false,
      "is_front_defroster_on": false,
      "is_preconditioning": false,
      "is_rear_defroster_on": false,
      "left_temp_direction": -240,
      "max_avail_temp": 28.0,
      "min_avail_temp": 15.0,
      "outside_temp": 24.0,
      "passenger_temp_setting": 20.0,
      "remote_heater_control_enabled": false,
      "right_temp_direction": -240,
      "seat_heater_left": 0,
      "seat_heater_rear_left": 0,
      "seat_heater_rear_right": 0,
      "seat_heater_right": 0,
      "seat_heater_third_row_left": 0,
      "seat_heater_third_row_right": 0,
      "side_mirror_heaters": false,
      "smart_preconditioning": false,
      "steering_wheel_heater": false,
      "timestamp":<PHONE_NUMBER>159,
      "wiper_blade_heater": false
    },
    "drive_state": {
      "gps_as_of":<PHONE_NUMBER>,
      "heading": 163,
      "latitude": 40.459698,
      "longitude": -79.92347,
      "native_latitude": 40.459698,
      "native_location_supported": 1,
      "native_longitude": -79.92347,
      "native_type": "wgs",
      "power": null,
      "shift_state": null,
      "speed": null,
      "timestamp":<PHONE_NUMBER>160
    },
    "gui_settings": {
      "gui_24_hour_time": false,
      "gui_charge_rate_units": "mi/hr",
      "gui_distance_units": "mi/hr",
      "gui_range_display": "Rated",
      "gui_temperature_units": "F",
      "timestamp":<PHONE_NUMBER>160
    },
    "vehicle_config": {
      "can_accept_navigation_requests": true,
      "can_actuate_trunks": true,
      "car_special_type": "base",
      "car_type": "modelx",
      "charge_port_type": "US",
      "eu_vehicle": false,
      "exterior_color": "MetallicBlack",
      "has_air_suspension": true,
      "has_ludicrous_mode": false,
      "motorized_charge_port": true,
      "perf_config": "P1",
      "plg": true,
      "rear_seat_heaters": 3,
      "rear_seat_type": 3,
      "rhd": false,
      "roof_color": "None",
      "seat_type": 0,
      "spoiler_type": "Passive",
      "sun_roof_installed": 0,
      "third_row_seats": "FuturisFoldFlat",
      "timestamp":<PHONE_NUMBER>160,
      "trim_badging": "90d",
      "wheel_type": "AeroTurbine20"
    },
    "vehicle_state": {
      "api_version": 6,
      "autopark_state_v2": "ready",
      "autopark_style": "dead_man",
      "calendar_supported": true,
      "car_version": "2<IP_ADDRESS> 4b1dd29",
      "center_display_state": 0,
      "df": 0,
      "dr": 0,
      "ft": 0,
      "homelink_nearby": false,
      "is_user_present": false,
      "last_autopark_error": "no_error",
      "locked": true,
      "media_state": {
        "remote_control_enabled": true
      },
      "notifications_supported": true,
      "odometer": 20101.093888,
      "parsed_calendar_supported": true,
      "pf": 0,
      "pr": 0,
      "remote_start": false,
      "remote_start_enabled": true,
      "remote_start_supported": true,
      "rt": 0,
      "sentry_mode": false,
      "software_update": {
        "expected_duration_sec": 2700,
        "status": ""
      },
      "speed_limit_mode": {
        "active": false,
        "current_limit_mph": 85.0,
        "max_limit_mph": 90,
        "min_limit_mph": 50,
        "pin_code_set": false
      },
      "sun_roof_percent_open": null,
      "sun_roof_state": "unknown",
      "timestamp":<PHONE_NUMBER>158,
      "valet_mode": false,
      "vehicle_name": ":name"
    }
  }
}```

I too have a considerable amount of data in JSON format and plan to import it by translating it to a TeslaFi export format..
If I understand correctly an examples of a valid TeslaFi export can be found here: https://github.com/adriankumpf/teslamate/tree/master/test/fixtures/import/01_complete
If I get mine working will report back here.

@LelandSindt - thanks, that is tremendously helpful. If you figure it out please do post back.

got started on this...
git@gist.github.com:5b6caac5a8fe5b320233149be953109e.git
My data coming from a RESTish server... so it may be a little different than your source... but this might get you started..
I will push my changes to the linked gist as I make them... let me know if you have any questions.

The latest version of the above linked script resulted in csv files that were successfully imported into Teslamate. Teslamate is currently repairing drives.. ~1400 of them... which feels like a lot for 1 years worth of data...
Note: I am importing this data into an empty/test instance of Teslamate.

... more feedback... my data is missing enough data points that it may not be worth importing into TeslaMate.

yeah, my collector was not good about quickly starting collection when the car woke/started driving.
I will not be importing my old data into TeslaMate. :(
Let me know if you chose to continue or if you have any questions.


Fixing aiohttp dependency version

Thank you for your great contribution, however when installing vuer via pip install vuer[all] the installed version of aiohttp is 3.10.10 however this version seems to give a blank output (no resulting mesh) in the renderer with the only error appearing in terminal as:
Traceback (most recent call last):
File "python3.8/site-packages/aiohttp/web_protocol.py", line 653, in finish_response
    prepare_meth = resp.prepare
AttributeError: 'NoneType' object has no attribute 'prepare'

This error does not show up if using pip install aiohttp==3.10.5 or previous versions. It would be great if the version was fixed to 3.10.5 on installation.

Thank you for raising the issue! I have reproduced this and have updated the dependencies to use aiohttp==3.10.5 for now.


renovate.json: disable renovate

for this particular repo, it isn't that important to keep dependencies up to date.

i got tired to resolve conflicts between renovate's changes and my changes.

This means disabling all package updates. Is it hard to keep up with updates?

as mentioned in the commit message, i don't think it's important to keep us updated.
also, we already disabled renovate for important packages.

Unless you have a strong request, I would like to keep this Repo up to date. Last time we pause wasmtime and wit-bindgen not to break the on going implementation. But basically I want to allow to update if CI/CD pass

then, please stop merging these PRs when it creates conflicts.

well noted


[student_notes] update lms endpoint for searching notes

it was: [...]/search/?text=[search_text]
is now: [...]/notes/?text=[search_text]

@MichaelRoytman let me know if your testing was fully functional using this branch

@pwnage101 It looked good when I tested out the loadtest!


"show_logo" config does not seem to be implemented

Hi,
First thank you for this great and useful action.
By reading the doc, I can see that there is an option "show_logo" that should  "Display the action's logo in the README".
But I can't find anywhere how to use it, and don't find any usage of this option in the code.
Can you explain how it should work?
Thank you

@neilime this is true, and since you pointed it out I have created a pull request to remove show_logo, and add a branding section to the readme, so that the action.yml branding can be added to the readme automatically.
https://github.com/bitflight-devops/github-action-readme-generator/pull/231

If you would like a custom logo section, that too can be added.


Runtime configuration

conda-store-ui is configurable at compile time thanks to the .env file
This PR adds a runtime configuration that can be defined right before loading the bundled app, for instance like  :
<script>
    var condaStoreConfig = {
        REACT_APP_AUTH_METHOD: "cookie",
        REACT_APP_AUTH_TOKEN: "",
        REACT_APP_STYLE_TYPE: "grayscale",
        REACT_APP_SHOW_LOGIN_ICON: "true",
        REACT_APP_API_URL: "http://localhost:5000/conda-store",
        REACT_APP_LOGIN_PAGE_URL: "http://localhost:5000/conda-store/login?next=",
    };
</script>
<!-- then load the bundled app here -->

@jujogi we could use a review from you here :) just to make sure this PR is checked by a react expert.
I think the goal of the PR is quite clear (allowing configuration at runtime), let me know if you'd want me to give more details.

It looks good to me, @pierrotsmnrd! Just one thing: replace var for const.

@jujogi  you mean turning this :
const { condaStoreConfig = {} } =
  typeof window !== "undefined" && (window as any);

into this :
var { condaStoreConfig = {} } =
  typeof window !== "undefined" && (window as any);

correct ?

ping @jujogi

@pierrotsmnrd @costrouc is there anything needed to move this PR? it has been reviewed but it is not clear if more work is needed or planned

I've gone ahead and made the appropriate changes in the docs, thanks everyone! I will be closing and merging this.


issue #434 I have added contributors page

Description

I have added a Contribution page .I have implemented a Frontend code. furthermore, we can implement backend.
Related Issues

Closes #

Type of PR

[ ] ()

Screenshots / videos (if applicable)

Checklist

[x] I have gone through the contributing guide
[x ] I have updated my branch and synced it with project main branch before making this PR
[x] I have performed a self-review of my code
[x ] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

@priyachau12 add my profile to the missing images , from my linkedin profile u can find in my github profile for directing to linkedin.

@priyachau12 add my profile to the missing images, from my linkedin profile u can find in my github profile for directing to LinkedIn.

Yeah, I'm working on it!


Define contributor role vocabulary

In the metadata model update we want to have a more flexible take on various contributors to a dataset, not just the authors & editors. For this we need a role vocabulary or decide to even use just free text.
Contributor roles will have to be mapped from and to DataCite DOI metadata and EML RoleType, so a controlled vocabulary would be very useful. EML allows free text and only recommends a few roles in comments, but DataCite and GBIF are strict and require controlled values.
See https://docs.google.com/spreadsheets/d/1-zO5zHqul6VBwcCcYh8egMI2N6q6LUB7uCU247o727c/edit#gid=491248187 for a quick and dirty mapping of these roles.

First draft proposal for roles:

contact: Person with knowledge of how to access, troubleshoot, or otherwise file issues related to the dataset
author: The main researchers involved in producing the data, or the authors of the publication, in priority order. This property will be used to formulate the citation, so consider the prominence of the role.
editor: A person who oversees the details related to the publication format of the dataset. This property will be used to formulate the citation, so consider the prominence of the role.
publisher: The name of the entity that holds, archives, publishes prints, distributes, releases, issues, or produces the dataset. This property will be used to formulate the citation, so consider the prominence of the role.
manager: Person (or organisation with a staff of data managers, such as a data centre) responsible for maintaining the finished dataset.
curator: Person tasked with reviewing, enhancing, cleaning, or standardizing data
contentProvider ? : Person/institution responsible for finding, gathering/collecting data under the guidelines of the author(s) or Principal Investigator (PI)
metadataAuthor ?
programmer
distributor: Institution tasked with responsibility to generate/disseminate copies of the dataset
rightsHolder: Person or institution owning or managing property rights, including intellectual property rights over the dataset
other

The bold roles are metadata fields on their own and can be supplied directly without a role under contributor.

Thanks @mdoering. I'm already struggling with thinking about how to apply so many role terms consistently in different cases. Some thoughts.

Wouldn't the contact always be someone who occupies one of the other roles? If so, should it be a separate property that can be attached to any person record in the metadata (indicating that they can be contacted about the dataset)?
Do we expect just to have a single block of contributors in the metadata, each with an associate role (or roles)? Or will there (also) be contributor records elsewhere in the metadata in contexts where some of the semantics are constrained by the context? For example, would we expect to have a section on the authorship of the metadata itself, with an embedded contributor record that is for the metadata author? If we are separately relying on or expecting some semantics to be based on structure, we may not need the role vocabulary to be so rich. Rights holder is a role that I would expect only to see in the context of the IPR and licensing section.
I know we have the name author because of our history, but it still feels odd to me to use this word to refer to list compilation and curation tasks.
I can't understand why "curator" would be separate from "author".
"Manager" seems cryptic - I would not split it further, but I'd think about what we mean. There is likely to be someone who leads the project (not necessarily a PM) and who can be seen as the lead author and primary contact. I would expect us to indicate this person through a combination of the author role and the contact role/flag. Then there may be a person who heads up the technical infrastructure that is hosting the dataset - if this is what we are highlighting, I'd call them something like "host" rather than manager. I'm not sure we need to think of "project managers" in the sense we would use the term for an IT project. See my next bullet.
To be honest, I'm not sure I'd split the informatics roles so much. I would think that the boundary between data managers and programmers would be blurry in many relevant organisations. Other than because it seems so passive, I would be inclined just to have an "IT support" role and include them all that way.
If "contributor" was not our umbrella term for all roles, I would tend to use "contributor" for "contentProvider". This captures the kind of relationship I think is intended.

Wouldn't the contact always be someone who occupies one of the other roles? If so, should it be a separate property that can be attached to any person record in the metadata (indicating that they can be contacted about the dataset)?

Roles are not exclusive, the same person can be the contact, author and more.

Do we expect just to have a single block of contributors in the metadata, each with an associate role (or roles)? Or will there (also) be contributor records elsewhere in the metadata in contexts where some of the semantics are constrained by the context? For example, would we expect to have a section on the authorship of the metadata itself, with an embedded contributor record that is for the metadata author? If we are separately relying on or expecting some semantics to be based on structure, we may not need the role vocabulary to be so rich. Rights holder is a role that I would expect only to see in the context of the IPR and licensing section.

Yes, thats the current expectation. We have an agent type merging person and organisation information that is used for  contact, author, editor, publisher & contributor lists. The first ones implicitly define their roles, for contributors we were thinking to provide finer roles. But reading your last comment about contentProvider being best described as contributor I tend to agree and wonder if we should rather just have contributor without any further roles. And instead add a few more properties for e.g. reviewer, manager, programmer (IT support is not a nice YAML key) or distributor.
Dublin Core has the following properties with range http://purl.org/dc/terms/AgentClass:

audience: A class of agents for whom the resource is intended or useful. Recommended practice is to use this property with non-literal values from a vocabulary of audience types.
contributor: An entity responsible for making contributions to the resource. The guidelines for using names of persons or organizations as creators apply to contributors.
creator: An entity responsible for making the resource. Recommended practice is to identify the creator with a URI. If this is not possible or feasible, a literal value that identifies the creator may be provided.
mediator:  An entity that mediates access to the resource. In an educational context, a mediator might be a parent, teacher, teaching assistant, or care-giver.
publisher: An entity responsible for making the resource available.
rightsHolder : A person or organization owning or managing rights over the resource. Recommended practice is to refer to the rights holder with a URI. If this is not possible or feasible, a literal value that identifies the rights holder may be provided.

I know we have the name author because of our history, but it still feels odd to me to use this word to refer to list compilation and curation tasks.

DataCite & DublinCore both use creator - happy to adopt that term instead which indeed fits better to datasets.

I can't understand why "curator" would be separate from "author".

Apart from the reviewer role I agree.

"Manager" seems cryptic - I would not split it further, but I'd think about what we mean. There is likely to be someone who leads the project (not necessarily a PM) and who can be seen as the lead author and primary contact. I would expect us to indicate this person through a combination of the author role and the contact role/flag. Then there may be a person who heads up the technical infrastructure that is hosting the dataset - if this is what we are highlighting, I'd call them something like "host" rather than manager. I'm not sure we need to think of "project managers" in the sense we would use the term for an IT project. See my next bullet.

I guess the use case was the WoRMS Data Management Team. That is probably best handled by the "IT support" below

To be honest, I'm not sure I'd split the informatics roles so much. I would think that the boundary between data managers and programmers would be blurry in many relevant organisations. Other than because it seems so passive, I would be inclined just to have an "IT support" role and include them all that way.

Agree. Can we think of a name for IT support that can easily be used as a key and starts with a lower case?
informatics, support (would also include helpdesks), systemSupport or use programmer and be very inclusive in its definition?

If "contributor" was not our umbrella term for all roles, I would tend to use "contributor" for "contentProvider". This captures the kind of relationship I think is intended.

Yes I like that. See above.
That would leave the following "roles", each existing as their own property and not nested under contributor:

contact
creator
editor
publisher
reviewer
contributor
programmer (aka IT support, name to be discussed)
distributor

Distributor might not be needed even. But might make sense for Plazi?
in GBIF there are 2 related organisations for a datasets, the hosting and the publishing organization. The later is the publisher, the first maps best to distributor. We could also consider to use "host", but with EML and DataCite both having a distributor role I would prefer distributor.

Thanks @mdoering - that seems better. I forgot to mention that I don't understand the difference between creator and editor in real-world GSD cases, but I'm comfortable for it to be there.

I wonder if we should not just collapse reviewer and programmer into contributor. Whats the benefit of having those roles separated out explicitly? We could habe a note field for contributors that allows people to specify their exact contribution if that is wanted. FishBase does this for example Ali, Atheer Provided references on fishes of Iraq:
https://www.fishbase.de/collaborators/CollaboratorSummary.php?id=2574

This makes sense to me @mdoering
Donald Hobern / @.*** / +61 420511471
Araba Bioscan Project https://stangeia.hobern.net/araba-bioscan-project/
/ Pterophoroidea https://pterophoroidea.hobern.net/ / Alucitoidea
https://alucitoidea.hobern.net/ / BOLD Australia
https://bold-au.hobern.net/
ORCID: 0000-0001-6492-4016 https://orcid.org/0000-0001-6492-4016 / Blog
https://stangeia.hobern.net/ / iNaturalist
https://inaturalist.ala.org.au/people/dhobern / Flickr
https://www.flickr.com/photos/dhobern// GitHub
https://github.com/dhobern / Twitter https://twitter.com/dhobern
On Wed, 21 Apr 2021 at 20:09, Markus Döring @.***>
wrote:

I wonder if we should not just collapse reviewer and programmer into
contributor. Whats the benefit of having those roles separated out
explicitly? We could habe a note field for contributors that allows people
to specify their exact contribution if that is wanted. FishBase
https://www.fishbase.de/Collaborators/CollaboratorsTopicList.php does
this for example Ali, Atheer Provided references on fishes of Iraq:
https://www.fishbase.de/collaborators/CollaboratorSummary.php?id=2574
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CatalogueOfLife/backend/issues/1001#issuecomment-823945036,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGHP4ZTD6KTAHPXG4M5Y3HLTJ2P4DANCNFSM427KXAYA
.

"Role" tends to be an overloaded term, often conflating job title or responsibilities with the action executed in the context of producing a work. Likewise, there's a frequent requirement to capture multiple roles. This is why RDA/TDWG Interest Group has downplayed this term in favour of a vocabulary to express the actions as the edge between two nodes: edited, curated, reviewed, programmed, etc.

Closing this as we converged on having no contributor role at all but instead a flexible note field and fixed "roles" as part of metadata fields based on Dublin Core or EML:

contact
creator
editor
publisher
distributor
contributor

Related discussion will continue on the metadata model update.


Can we set default value for o-select?

Good day, I see that the pure HTML Select tag has an option for selected, that sets that option value as the default. Does o-select have this prop? How would I make the empty value default one if none are selected?
<script>
</script>

<template>
  <section>
    <o-field label="Pick one">
      <o-select placeholder="Select a player">
        <option value="empty"></option>
        <option value="p01">Player 01</option>
        <option value="p02">Player 02</option>
        <option value="p02">Player 03</option>
      </o-select>
    </o-field>
  </section>
</template>

Thanks again and keep up the amazing work on the library!

 Thanks so much for the tip.


Update sdk + sample app to use single error

What

Why

Test Plan

✅ | ❌ I've added unit tests for this change.
✅ | ❌ The reviewer should manually test the changes in this PR.

Demo

How

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#295  👈
#289
#288
#290
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @devinmorgan and the rest of your teammates on  Graphite

Merge activity

Jul 24, 4:47 PM EDT: @devinmorgan merged this pull request with Graphite.


Do not ever store build artefacts on main

This pollutes our azure accounts (and storage allowance) for 2 years with useless stuff. It's fine for debugging a PR, but https://github.com/conda-forge/pysr-feedstock/commit/925d13211796c3a23db694585c3fa91599677b59 should have never been merged to main.
CC @ngam

Also, I was under the impression the artifacts are only stored for ~60 (or less) days just like the logs

That's just for PRs. Logs on main get persisted for 2 years. Checking the logs here, it seems that the artefacts already get deleted before that (not sure based on what mechanism and whether that changed recently - I've never seen what actually happens with artefact persistence on main; I'm just reflecting the clear instructions I've gotten about this, but details aside, it seems like a no-brainer to not store these things pointlessly)

Closed from #85


video-analytics-service build failed due to too long log

Preparing to unpack .../0-python3-minimal_3.6.7-1~18.04_amd64.deb ...
Unpacking python3-minimal (3.6.7-1~18.04) ...
Selecting previously unselected package mime-support.
Preparing to unpack .../1-mime-support_3.60ubuntu1_all.deb ...
Unpacking mime-support (3.60ubuntu1) ...
Selecting previously unselected package libmpdec2:amd64.
Preparing to unpack .../2-libmpdec2_2.4.2-1ubuntu1_amd64.deb ...
Unpacking libmpdec2:amd64 (2.4.2-1ubuntu1) ...
Selecting previously unselected package readline-common.
Preparing to unpack .../3-readline-common_7.0-3_all.deb ...
The job exceeded the maximum log length, and has been terminated.

The issue is fixed.


.wixproj and .wapproj info

I see the email for support. Saving that for more pressing questions. :-)
I was able to open the main branch in visual studio pro 2010 on an old PC that already been used for XNA development and build a debug.
However I can't sort out how the .wixproj and .wapproj projects open. I did install the included WiX installer. It seemed to do stuff on a VS2015 I had installed.

I opened BokuSetup in a higher VS but when I tried to build it, it complained about a missing SourceDir. I tried creating the folder and built it again and the folder was removed in the build process. Seems like maybe some instructions are needed.

The WiX setup should have added those project types for VS2010.  I have a machine I can try it on here.  Which version of Windows are you running?

I was on Win 8.1 but have Windows 10 too. I had the old VS2010 for Windows Phone installed by it didn't support project files. So I went ahead and setup VS2010 Pro. I wasn't sure what problems I would run into trying to get XNA installed on Win 10 so went with where I had it first. Thanks for checking it out. Esp. interested in the UWP build option if that exists. I assume that wouldn't be available in VS2010.

XNA should have no trouble on Win10.  I'm not sure if the UWP build ever actually worked.  When I originally uploaded Kodu to GitHub I just grabbed everything instead of trying to trim it down to the minimum needed.  At the time of the UWP build we were trying to figure out the best way to get a build into the Microsoft Store.  Microsoft has since made this much easier with the MSIX Packaging Tool which allows you to take pretty much any desktop app and bundle it up so that it works with the store.
Did switching to VS2010Pro solve the WiX project issues?
Right now, I'm resetting Windows on a spare PC I have so I'll have a clean slate to try the install on.  I'll try and take good notes so I can update the instructions.

Great! VS2010Pro was what allowed a successful build and debug run without WiX. [I've never used Wix before.] The two pictures on the first note are what happened when I opened the solution with VS2010Pro. I was still able to build without WiX. It may be that WiX only saw my VS2015 (also on the same machine.) I'll be interested to know if it works on your clean slate.


Support caching of local offloaded pods in the controller-manager

Description
This PR adds local offloaded pods to the liqo-controller-manager cache.
The problem: controllers in liqo-controller-manager have in cache only the pods managed by a shadowpod (i.e. remote offloaded pods) for performance reasons. For future controllers, it may be useful to cache local offloaded pods as well.
Implementation: the PR creates a new auxiliary manager that caches local offloaded pods so that future controllers can retrieve the new (cached) client from it.
How Has This Been Tested?

[x] Locally on KinD
[x] Unit tests
[x] e2e tests

/test

/merge


Aborted due to warnings.
test.html like this:

Tuijs Unit Test

<script src="qunit/qunit-1.14.0.js"></script>
<script src="../dist/sea-2.1.1.js"></script>
<script src="../dist/tui.config.js"></script>
<script>

    (function(){
        seajs.use(['tuiInit'], function(){
            $.extend(seajs.data.alias, {testInit: '../tests/test.Init.js'});
        });
        seajs.use(['testInit'], function(){});
    })();

</script>

I'm having a similar issue running using jQuery.  When I view my test page in the browser, I get no errors, jQuery loads fine and is used in tested code and tests.
When running through Grunt/PhantomJS, i get an error saying jQuery can't be found.

Can't reproduce using latest releases.
Closing for now, will reopen if the issue persist.


RUBY-1033 App Tests

:fire: remove integration testing
This will remove the Contrast specific application testing from this project, instead having it in our own repository.
To test this, checkout the Ruby App Test project and follow the instructions in its README to assert the tests can be run.
Note: The docker images here still have Contrast Agents in them and use the CI testing flag. There'll be a follow up to change that

testing?

I'm testing this with the instructions here, and I've gotten to these steps:

Move up to the directory above this project, which should have both this and vulneruby_engine in it.
Run docker-compose up --abort-on-container-exit --exit-code-from test_harness.
There docker-compose.yml file is in ruby-app-test, but the instructions say to run the docker-compose command from the directory above it, so I get a Can't find a suitable configuration file error. I tried ignoring the instructions and cd-ing into ruby-app-test, but that eventually fails when we can't find files in vulneruby_engine.

My comfort level with docker-compose is probably 1.5/10, so maybe this is obvious for people that know what they're doing, but I can't figure it out 😬

I'm testing this with the instructions here, and I've gotten to these steps:

Move up to the directory above this project, which should have both this and vulneruby_engine in it.
Run docker-compose up --abort-on-container-exit --exit-code-from test_harness.

The docker-compose.yml file is in ruby-app-test, but the instructions say to run the docker-compose command from the directory above it, so I get a Can't find a suitable configuration file error. I tried ignoring the instructions and cd-ing into ruby-app-test, but that eventually fails when we can't find files in vulneruby_engine.
My comfort level with docker-compose is probably 1.5/10, so maybe this is obvious for people that know what they're doing, but I can't figure it out 😬

Should be addressed. Updated instructions. I missed the -f flag in the initial commit

docker-compose -f ./ruby-app-test/docker-compose.yml up --abort-on-container-exit --build


globed keeps crashing

whenever i get onto globed its fine but when i try to click on the 2nd level it crashes (not the 1st)

please upload crashlog

2024-07-28_13-15-31.txt
here

looks like an issue with the Level Info mod, not globed


DRILL-5355: Misc. code cleanup

Recent work in Drill has identified a number of cases where code can be
cleaned up: adding missing annotations, etc. These changes don't fit as part of a separate ticket and so are rolled up into a this "general
hygiene" PR.

+1


[BUG]OpenAI client is not initialized. Skipping generation.

Describe the bug
A clear and concise description of what the bug is.
I rename the .env.sample to .env and set my openai-api
To Reproduce
Steps to reproduce the behavior
Expected behavior
A clear and concise description of what you expected to happen.
Logs and Error Reports
If applicable, include any relevant console logs or error reports to help diagnose the issue.
INFO:app.services.llm.factory:Creating LLM service for provider: openai
2024-10-25 16:06:55 INFO:app.services.llm.factory:Creating LLM service for provider: openai
2024-10-25 16:06:55 WARNING:app.services.llm.openai_service:OpenAI API key is not set. LLM features will be disabled.
2024-10-25 16:06:55 WARNING:app.services.llm.openai_service:OpenAI API key is not set. LLM features will be disabled.
2024-10-25 16:06:55 INFO:app.services.vector_db.factory:Creating vector database service with provider: milvus
2024-10-25 16:06:55 INFO:app.services.vector_db.factory:Creating vector database service with provider: milvus
2024-10-25 16:06:55 INFO:pymilvus.orm.connections:Pass in the local path ./milvus_demo.db, and run it using milvus-lite
2024-10-25 16:06:55 INFO:pymilvus.orm.connections:Pass in the local path ./milvus_demo.db, and run it using milvus-lite
2024-10-25 16:06:56 DEBUG:pymilvus.milvus_client.milvus_client:Created new connection using: abbc7ecf7f3245a798c0cfe37e20a8a6
2024-10-25 16:06:56 DEBUG:pymilvus.milvus_client.milvus_client:Created new connection using: c14a319a45494883aec96ededf2e3ac2
2024-10-25 16:06:56 INFO:app.api.v1.endpoints.query:Received query request: {'document_id': 'a7d92cfa52664a6c80c16d0da22b029e', 'prompt': {'id': 'cm2k5w1y900013p6iec91t6z4', 'entity_type': 'year', 'query': 'when did the file public?', 'type': 'str', 'rules': [{'type': 'must_return', 'options': [], 'length': None}]}}
2024-10-25 16:06:56 INFO:app.services.vector_db.milvus_service:Performing hybrid search.
2024-10-25 16:06:56 WARNING:app.services.llm.openai_service:OpenAI client is not initialized. Skipping generation.
2024-10-25 16:06:56 ERROR:app.services.llm_service:Error extracting keywords: 'NoneType' object has no attribute 'keywords'
2024-10-25 16:06:56 WARNING:app.services.llm.openai_service:OpenAI client is not initialized. Skipping embeddings.
2024-10-25 16:06:56 ERROR:pymilvus.decorators:RPC error: [describe_collection], <DescribeCollectionException: (code=100, message=: collection not found)>, <Time:{'RPC start': '2024-10-25 08:06:56.673653', 'RPC error': '2024-10-25 08:06:56.676264'}>
2024-10-25 16:06:56 ERROR:pymilvus.milvus_client.milvus_client:Failed to describe collection: milvus
2024-10-25 16:06:56 ERROR:app.services.vector_db.milvus_service:Error during Milvus search: <DescribeCollectionException: (code=100, message=: collection not found)>
2024-10-25 16:06:56 ERROR:app.services.vector_db.milvus_service:Milvus search parameters: collection_name=milvus, data shape=1x0
2024-10-25 16:06:56 ERROR:app.api.v1.endpoints.query:Error processing query: <DescribeCollectionException: (code=100, message=: collection not found)>
2024-10-25 16:06:56 INFO:     <IP_ADDRESS>:29157 - "POST /api/v1/query HTTP/1.1" 500 Internal Server Error
2024-10-25 16:06:56 INFO:app.api.v1.endpoints.query:Received query request: {'document_id': '9f0a1d711ccb46788b3c4c937cd072b8', 'prompt': {'id': 'cm2k5w1y900013p6iec91t6z4', 'entity_type': 'year', 'query': 'when did the file public?', 'type': 'str', 'rules': [{'type': 'must_return', 'options': [], 'length': None}]}}
2024-10-25 16:06:56 INFO:app.services.vector_db.milvus_service:Performing hybrid search.
2024-10-25 16:06:56 WARNING:app.services.llm.openai_service:OpenAI client is not initialized. Skipping generation.
2024-10-25 16:06:56 ERROR:app.services.llm_service:Error extracting keywords: 'NoneType' object has no attribute 'keywords'
2024-10-25 16:06:56 WARNING:app.services.llm.openai_service:OpenAI client is not initialized. Skipping embeddings.
2024-10-25 16:06:56 ERROR:pymilvus.decorators:RPC error: [describe_collection], <DescribeCollectionException: (code=100, message=: collection not found)>, <Time:{'RPC start': '2024-10-25 08:06:56.678623', 'RPC error': '2024-10-25 08:06:56.680722'}>
2024-10-25 16:06:56 ERROR:pymilvus.milvus_client.milvus_client:Failed to describe collection: milvus
2024-10-25 16:06:56 ERROR:app.services.vector_db.milvus_service:Error during Milvus search: <DescribeCollectionException: (code=100, message=: collection not found)>
2024-10-25 16:06:56 ERROR:app.services.vector_db.milvus_service:Milvus search parameters: collection_name=milvus, data shape=1x0
2024-10-25 16:06:56 ERROR:app.api.v1.endpoints.query:Error processing query: <DescribeCollectionException: (code=100, message=: collection not found)>
2024-10-25 16:06:56 INFO:     <IP_ADDRESS>:42285 - "POST /api/v1/query HTTP/1.1" 500 Internal Server Error
Screenshots
If applicable, add screenshots to help explain your problem.

Hey @happywinder, someone has mentioned here: https://github.com/whyhow-ai/knowledge-table/issues/41. Dealing with it ASAP.

Hi @happywinder, this has now been resolved and merged into main. See context here:
https://github.com/whyhow-ai/knowledge-table/pull/38


AZ ACR TASK CREATION ERROR: Traceback (most recent call last):

Traceback (most recent call last):
  File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 215, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 654, in execute
    raise ex
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 718, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 711, in _run_job
    six.reraise(*sys.exc_info())
  File "/opt/az/lib/python3.6/site-packages/six.py", line 703, in reraise
    raise value
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 688, in _run_job
    result = cmd_copy(params)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 325, in __call__
    return self.handler(*args, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/__init__.py", line 545, in default_command_handler
    return op(**command_args)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/acr/task.py", line 200, in acr_task_create
    task_create_parameters=task_create_parameters)
  File "/opt/az/lib/python3.6/site-packages/azure/mgmt/containerregistry/v2019_06_01_preview/operations/_tasks_operations.py", line 265, in create
    **operation_config
  File "/opt/az/lib/python3.6/site-packages/azure/mgmt/containerregistry/v2019_06_01_preview/operations/_tasks_operations.py", line 215, in _create_initial
    raise models.ErrorResponseException(self._deserialize, response)
azure.mgmt.containerregistry.v2019_06_01_preview.models._models_py3.ErrorResponseException: Operation returned an invalid status code 'Not Found'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/az/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/opt/az/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/__main__.py", line 44, in <module>
    exit_code = cli_main(az_cli, sys.argv[1:])
  File "/opt/az/lib/python3.6/site-packages/azure/cli/__main__.py", line 31, in cli_main
    return cli.invoke(args)
  File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 226, in invoke
    exit_code = self.exception_handler(ex)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/__init__.py", line 106, in exception_handler
    return handle_exception(ex)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/util.py", line 94, in handle_exception
    error = response_dict['error']
TypeError: string indices must be integers

WHILE CREATING ACR TASKER
az acr task create     --registry stagingregistry     --name staging     --image rstagingregistry.azurecr.io/rstage:{{.Run.ID}}     --image stagingregistry.azurecr.io/stage:latest     --context https://github.com/SANDEEP/STAGING-app.git#Devops      --file Dockerfile     --git-access-token xyz

ACR

Please investigate

@sandeepmindwave , thanks for the report. To make it work, you need enable either the commit-trigger or base-image trigger when using the git-access-token. It works if adding "--commit-trigger-enabled false --base-image-trigger-enabled true" in the end of your command. But there's a bug in our side, it should give you the clear error message.

@yugangw-msft I filed another issue by my investigation.  When the status is not expected, it is supposed to throw the error detail. But the cli util failed to parse the error from the ex response.

@sandeepmindwave , thanks for the report. To make it work, you need enable either the commit-trigger or base-image trigger when using the git-access-token. It works if adding "--commit-trigger-enabled false --base-image-trigger-enabled true" in the end of your command. But there's a bug in our side, it should give you the clear error message.

It works for me.

Hi is there any progress on this?
While --commit-trigger-enabled false --base-image-trigger-enabled true
--commit-trigger-enabled true doesn't work, so it seems I can't create a task with a commit trigger enabled?

@timja The commit trigger works. The above issue is caused by an invalid git-access-token I think. We have problem to parse the error as the issue filed in https://github.com/Azure/azure-cli/issues/14343. It works if everything is right.

#14830

The actual issue in my case was that the PAT I was using didn’t have admin access to the repo

@sandeepmindwave , thanks for the report. To make it work, you need enable either the commit-trigger or base-image trigger when using the git-access-token. It works if adding "--commit-trigger-enabled false --base-image-trigger-enabled true" in the end of your command. But there's a bug in our side, it should give you the clear error message.

@ thanks for replay , i am facing new issue, this command working **--commit-trigger-enabled false --base-image-trigger-enabled true** but auto trigger is not working while i get new commit tasker is not running

@sandeepmindwave Apologies for the late reply. Could you please let us know if you still need assistance on this issue ? Awaiting your reply.


resolves STREAMS-276

updates to make this module use DocumentClassifier and ActivityConverter interfaces and reflection-based DateTime handling and Activity conversion.
tweaks and renames to the tests to match the new model.
This change impacts testing in streams-runtime-pig, so https://github.com/apache/incubator-streams/pull/179 must merge first.
Note that this will be a breaking change to streams components and pipelines which rely on 'Serializer'-style conversion.  The good news is resolving should be as simple as:
ActivityConverterProcessor converter = new ActivityConverterProcessor();
builder.addStreamsProcessor("converter", converter, 4, "provider");
where upstream provider passes in String or ObjectNode representations of POJOs in com.twitter
TwitterEventClassifier and TwitterEventProcessor are no longer necessary.

i'm deleting this branch so i can resolve the merge conflicts with a rebase


reduce "same but neq" cases

towards #7237
PYTHONPATH=. CNT=1000 SEED=42 CHECK_NEQ=1 DEBUG=0 python3 test/external/fuzz_shapetracker_math.py
same but neq
master - good (60/1000 = 6.00%)
branch - good (55/1000 = 5.50%)
PYTHONPATH=. CNT=5000 SEED=42 CHECK_NEQ=1 DEBUG=0 python3 test/external/fuzz_shapetracker_math.py
same but neq
master - good (305/5000 = 6.10%)
branch - good (298/5000 = 5.96%)
PYTHONPATH=. CNT=10000 SEED=42 CHECK_NEQ=1 DEBUG=0 python3 test/external/fuzz_shapetracker_math.py
same but neq
master - good (578/10000 = 5.78%)
branch - good (559/10000 = 5.59%)

PYTHONPATH=. CNT=1000 SEED=1 CHECK_NEQ=1 DEBUG=0 python3 test/external/fuzz_shapetracker_math.py
same but neq
master - good (55/1000 = 5.50%)
branch - good (52/1000 = 5.20%)
PYTHONPATH=. CNT=5000 SEED=1 CHECK_NEQ=1 DEBUG=0 python3 test/external/fuzz_shapetracker_math.py
same but neq
master - good (279/5000 = 5.58%)
branch - good (264/5000 = 5.28%)
PYTHONPATH=. CNT=10000 SEED=1 CHECK_NEQ=1 DEBUG=0 python3 test/external/fuzz_shapetracker_math.py
same but neq
master - good (571/10000 = 5.71%)
branch - good (539/10000 = 5.39%)

Why does this indexing test fail?

@chenyuxyz this is ready for review.

Maybe there some good ideas here, but the pull request is hard to review. It looks like adding bunch if else conditions to reduce the diff. Is this complete, and if not, does this completely fix a sub category of cases?
For pr itself, minimize the diff and document properly with unit tests before asking for review.

earlier, when projecting vm2's mask onto vm1, we were completely ignoring strides where len(term) > 1. This PR changes that and slightly more views are able to get merged.

Example (same but unequal) shapetracker with more than 1 canonical form. Is there a way to identify these?
ShapeTracker(views=(View(shape=(7, 8), strides=(7, 1), offset=-7, mask=((1, 5), (0, 7)), contiguous=False), View(shape=(58,), strides=(1,), offset=0, mask=((0, 56),), contiguous=False)))
ShapeTracker(views=(View(shape=(8, 8), strides=(7, 1), offset=-7, mask=((1, 5), (0, 7)), contiguous=False), View(shape=(58,), strides=(1,), offset=0, mask=((0, 56),), contiguous=False)))

i added some tests in https://github.com/tinygrad/tinygrad/blob/801e199196c19f1f1adee43cff616adce45d0580/test/unit/test_view.py#L77
if you want i can merge the tests in this pr with unittest.expectedFailure for TODOs

i added some tests in https://github.com/tinygrad/tinygrad/blob/801e199196c19f1f1adee43cff616adce45d0580/test/unit/test_view.py#L77
if you want i can merge the tests in this pr with unittest.expectedFailure for TODOs

sure, I will create the PR with the failing tests.

thanks for adding the tests. for the actual implementation i think https://github.com/tinygrad/tinygrad/issues/8305 is the way, so closing this one


CodeQL-Runner CLI: Unexpected end of JSON input

I seem to be running into an issue with uploading sarif results generated from trivy where the GitHub Action for upload works as expected but reproducing the same command over the CLI doesn't seem to work. The same report.sarif file works in GH Actions. Could I be missing something with the command?
./codeql-runner-linux upload --sarif-file "report.sarif" --repository "user/repo" --commit "commit-hash" --ref "refs/heads/main" --github-url "https://github.com" --github-auth "personal-access-token"

SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at validateSarifFileSchema (/snapshot/dist/codeql-runner.js)
    at uploadFiles (/snapshot/dist/codeql-runner.js)
    at Object.uploadFromRunner (/snapshot/dist/codeql-runner.js)
    at Command.<anonymous> (/snapshot/dist/codeql-runner.js)
    at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:62:5)
    at Function.Module.runMain (pkg/prelude/bootstrap.js:1376:13)
    at internal/main/run_main_module.js:17:47

My PAT has full control for private repos (even though the repo is public) but it's not clear if any more permissions are needed? GitHub shows that the PAT has never been used. Does it need a different scope?

Update, looks like the SARIF file generated was empty :)

Looks like SARIF file was empty, resolved!


[doc][question][feature?] - in libs.versions.toml?

I've been using -, not _ in my libs.versions.toml. It seems to be the default recommendation is it not supported? please improve the documentation as part of answer. If it's not, maybe also add feature.

Yes this works as Gradle automatically replaces both _ and - with .. I added a test to confirm this and added a note about the notations in TOML to the Readme.


BUG : EXTRA IMAGE IN SERVICE SECTION AND HOVER OF SERVICES HEADING

One extra image is present in one of the cards of service section .

The hover of services heading in services section is improper, even if the cursor is far away from heading the hover activates .
https://github.com/khushi-joshi-05/Food-ordering-website/assets/159682348/e464dc5a-067d-4746-9823-bc8624c7c928

@khushi-joshi-05 @sunny0625
I have fixed this issue and created a pull request for the same . Please assign this issue to me and merge my pull request under gssoc label .

@khushi-joshi-05 please merge this ansd close this issue .


Why is the Rails assets pipeline not being used?

I'm just curious on why you guys decided moving to Grunt, any specific reasons?

because:

it was slow as hell in the way we wanted to use it
cartodb frontend is big enough to have its own build/deploy/management
I don't like rails

@javisantana Thanks

said that it worked pretty well while we used it


Refactor - Split all interfaces and base implementations

This depends on patch-an-address so update it after all of those commits are merged into v1.1


[GOBBLIN-1342] Add API to resume a flow

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-1342

Description

[x] Here are some details about my PR, including screenshots (if applicable):

This PR adds flow resume functionality, which means after a flow fails, resume can be called on it, and the flow will be reattempted from the point before it failed (i.e. not rerunning the successful jobs).
How it works:

Whenever a flow fails, on cleanup, it is now added to a failedDagStateStore, similar to the normal dag state store. (It is also kept in an in-memory failedDags map to avoid querying the store for every resume request).
User triggers a resume request by calling partial update on the FlowExecutions endpoint, updating the status from FAILED to RUNNING. This is a little confusing, but as per this discussion it seems to be the most correct way to represent a triggered action like this in rest.
The request is forwarded to the DagManager as a ResumeFlowEvent through the eventbus, similar to how killing a flow works.
DagManager adds it to a resumeQueue to be picked up by a thread
The thread calls beginResumingDag on the dag, which sets the status of both the flow and each FAILED/CANCELLED job to PENDING_RESUME (and also sends events so this will be updated in the status store). The dag is then added to another map resumingDags
In finishResumingDags, the dags in resumingDags are checked by querying the status store. If the dag has reached the correct state, then it is passed back to initialize to be launched. This is separated from beginResumingDag because it takes some time for the status to be updated in the status store.

Other related changes:

Fixed a bug where addDag sets all jobs to PENDING, even if the dag is already running. This would cause their initial jobs to get relaunched on service restart.
Added a flowStartTime variable in JobExecutionPlan which is set on flow resume so that flow SLA will not be calculated based on the original flow.
Added PENDING_RESUME to execution status enum, it is a special status required because resuming flows are allowed to move "backwards" in status from FAILED to PENDING.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
Add unit test

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #3179 (bcbdf77) into master (92fe239) will decrease coverage by 37.09%.
The diff coverage is 0.00%.

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

Codecov Report

Merging #3179 (bcbdf77) into master (92fe239) will decrease coverage by 37.09%.
The diff coverage is 0.00%.

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


Fix macOS name for libqrencode

Use the proper macOS name for libqrencode 3.

OK I signed it!

Thanks!
Not sure why googlebot didn't update the labels, but I double-checked that it looks good.


psr log compatibility

"psr/log": "^1.1|^2|^3"

Hello, will this pull request be merged anytime soon?

Hello, will this pull request be merged anytime soon?

I don't know, what you mean by "soon" :-)


tree: Publish APis for creating new custom events as alpha

Description
Publish API for creating events as alpha.
Reviewer Guidance
The review process is outlined on this wiki page.

A usability issue with this APi has been reported:
Lack of strong typing of the keys least to string names for keys in code easily getting out of date (or having typos) with no compile errors.
There are two ways this could be improved:

strong types on the keys in the set (ex: derive them from the object node or nodes provided)
a way to refer to property key strings that is strongly typed to the object they are on and refactors properly. For example Foo.fields.bar.key possible leveraging a "FieldSchemaContextual" subclass which has the key as s strongly typed property.


Formatting and deprecations

This PR

Uses Scalafmt instead of Scalariform for formatting and applies the formatting globally. The reason for this is that every time I touch a file it gets reformatted because automatic formatting apparently wasn't applied on all files.
The config is optimized for Git usage (e.g. it doesn't align arrows because with alignment you get changed lines unrelated to the actual change just so that they align again). If you hugely prefer the old formatting style with alignment I can adapt the config accordingly.
Replaces the Unicode arrow ⇒ with => because it leads to warnings in Scala 2.13. A nicer look of symbols can be achieved
using font ligatures.

I'm fine with any format as long as it's usage is consistent.


fix: Intermittent failure from Kafka to get consumer offsets

fixes #784

@yhl25 LGTM. Thanks for fixing this issue.


permission_denied at /items: Client doesn't have permission to access the desired data

ERROR Error: permission_denied at /items: Client doesn't have permission to access the desired data.
at G (database.js:209)
at Object.G (database.js:213)
at database.js:173
at Ag.webpackJsonp.../../../../firebase/database.js.g.wd (database.js:178)
at og.webpackJsonp.../../../../firebase/database.js.og.wd (database.js:168)
at Yf.Xf (database.js:166)
at ag (database.js:150)
at WebSocket.Ia.onmessage (database.js:149)
at WebSocket.wrapFn [as __zone_symbol___onmessage] (zone.js:1056)
at ZoneDelegate.webpackJsonp.../../../../zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:424)

Looks like your firebase database rules are set to .read/write = false. Go to your firebase console > realtime database > rules. You can manually change them here. For additional information also see: https://firebase.google.com/docs/database/security/

Hey @amitsinghv! What @lehrenberg is the cast. You likely have your default rules set to authenticated only. For development you can change it to read true and write true.

Better, you should keep steps for that as well. Its will be great for new
people.
On Fri, Jul 7, 2017 at 9:52 PM, David East<EMAIL_ADDRESS>wrote:

Hey @amitsinghv https://github.com/amitsinghv! What @lehrenberg
https://github.com/lehrenberg is the cast. You likely have your default
rules set to authenticated only. For development you can change it to read
true and write true.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/angular/angularfire2/issues/1059#issuecomment-313728145,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATMdxmU1Ioqxd1t5Vw4rn35O2JIdOd-cks5sLls5gaJpZM4OPN3U
.

--
Regards,
Amit Kumar Singh
Software Engineer, Voonik
+91<PHONE_NUMBER>

Issue fixed. I've reinstall firebase and everything work perfectly 👌
Le sam. 8 juil. 2017 à 05:50, Amit Kumar Singh<EMAIL_ADDRESS>a
écrit :

Better, you should keep steps for that as well. Its will be great for new
people.
On Fri, Jul 7, 2017 at 9:52 PM, David East<EMAIL_ADDRESS>wrote:

Hey @amitsinghv https://github.com/amitsinghv! What @lehrenberg
https://github.com/lehrenberg is the cast. You likely have your
default
rules set to authenticated only. For development you can change it to
read
true and write true.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/angular/angularfire2/issues/1059#issuecomment-313728145
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/ATMdxmU1Ioqxd1t5Vw4rn35O2JIdOd-cks5sLls5gaJpZM4OPN3U
.

--
Regards,
Amit Kumar Singh
Software Engineer, Voonik
+91<PHONE_NUMBER>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/angularfire2/issues/1059#issuecomment-313833629,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXXkDP_hPVF8RUtXTScz2gVB2KsZVBcPks5sLwp6gaJpZM4OPN3U
.

--
Cordialement,
David K. Hiheaglo

Also, this has happened to me. I was logged in with the incorrect Google account at the time, the moment I swapped to the correct one and reloaded, it all started working again. Hope it helps.
Context: Ionic / Firebase project

I have the same issue except I am logged in to my only google account and read/write are enabled.
I have tried logging in and out several times.
Any other suggestions?


Key metadata is stored unencrypted

Output of restic version
restic 0.9.2 compiled with go1.11 on linux/amd64
How did you run restic exactly?
restic -r /repo init
What backend/server/service did you use to store the repository?
local
Expected behavior

Keys should contain no plaintext information (apart from salt, iteration, ...).
Actual behavior
Keys contain host name, username, and time of creation in plaintext.
Do you have any idea what may have caused this?
Restic stores key metadata unencrypted.
Do you have an idea how to solve the issue?
Store key metadata encrypted. We could update the key format by adding e.g. a hostname_enc field and blanking the hostname field for new repos. Then old clients would show empty metadata until they are updated. We should also migrate existing keys to remove potentially old plaintext metadata from existing repos.

We'll probably just remove the fields from the key metadata, that should be sufficient.

How are keys identified then, if all their metadata gets removed? Or do you just want to remove the plaintext fields and introduce encrypted ones?

If this metadata is to be removed, could we at least have an optional 'tag' attribute for each key that can contain anything we wish? Make the tag empty by default for those concerned with leaking metadata, but allow custom text that could be useful for key management, for those that are not.

When stripping the metadata manually I get the following:
Load(<key/5d081d8a51>, 0, 0) returned error, retrying after 552.330144ms: loadAll(<key/5d081d8a51>): invalid data returned
Load(<key/5d081d8a51>, 0, 0) operation successful after 1 retries

The error is expected, as the id no longer matches the content, but the successful retry is a (nice) surprise to me. I can't find in the code where it loosens the check and accept the content anyway. Can someone point me to where that happens?

@ducalex The filename of a file stored in the repository must always match the SHA256 hash of its content. Thus after tampering with a key, you have to update its filename. Removing integrity checks isn't a good idea.

Load(<key/5d081d8a51>, 0, 0) operation successful after 1 retries

Hmm, that error message isn't particularly helpful...

@ducalex The filename of a file stored in the repository must always match the SHA256 hash of its content. Thus after tampering with a key, you have to update its filename. Removing integrity checks isn't a good idea.

That is what I would expect, but why does it eventually succeed anyway?
Example:
$ mkdir temp
$ restic -rtemp init
enter password for new repository:
enter password again:
created restic repository 5a13f78dee at .
$ vi temp/keys/6de9da466bb841d144529a04690a7d0ca3aa1caa3fa0c8aa8416f67cae34f521 # strip metadata
$ touch test
$ restic -rtemp backup test
enter password for repository:
Load(<key/6de9da466b>, 0, 0) returned error, retrying after 552.330144ms: loadAll(<key/6de9da466b>): invalid data returned
Load(<key/6de9da466b>, 0, 0) operation successful after 1 retries
Load(<key/6de9da466b>, 0, 0) operation successful after 1 retries
Load(<key/6de9da466b>, 0, 0) returned error, retrying after 582.280027ms: loadAll(<key/6de9da466b>): invalid data returned
Load(<key/6de9da466b>, 0, 0) operation successful after 1 retries
repository 5a13f78d opened (version 2, compression level auto)
no parent snapshot found, will read all files

Files:           1 new,     0 changed,     0 unmodified
Dirs:            0 new,     0 changed,     0 unmodified
Added to the repository: 448 B (488 B stored)
processed 1 files, 155 B in 0:00
snapshot bcb08633 saved

That is what I would expect, but why does it eventually succeed anyway?

restic retries downloading a damaged file at most once. Afterwards the data is passed on to whatever component requested it, independent of whether that data is correct or not. Depending on what that component does, this will either be successful (key is usable as the JSON can still be decoded) or fail (e.g. what trying to decrypt damaged data).
The reason why invalid data might be passed on to the next component is that this can be useful e.g. when trying to repair or analyze a damaged repository.

Any news?
This leak hostname and username
I came here after searching in the repository.
grep -rE 'myuser|myhost|otherinfos|user|host' /repos*
I hope this was encrypted  binary file.


Investigate parallel DD activation

Function group SDMP have some interesting function modules, looks like they can be used for parallel activation of DD objects, eg function module DD_MASS_ACT_C3
We should sometime investigate if this can be used, in order to speed up the activation step
log can be shown via SUBMIT rsputprt

#1466

For https://github.com/abapkochbuch/Sources abapGit tries to activate the DDIC objects, with the old logic no errors are shown.
With new parallel logic abapGit shows an error list:

above errors are probably just due to the fact that errors did not show up properly with the old logic

think we should try activating this by default sometime soon

activated in https://github.com/larshp/abapGit/pull/2437, closing


Events: Siblings, Overlapping (width and z-index)

I'm reporting my comment on #379 as a unique issue so people can find it.
I have an other behavior that is unexpected with event overlaping.
Here the save events.
GoogleCalendar/Fullcalendar

React Big Calendar

As I say in the image, Blue event should be bellow the red one, and stop at the same position that the yellow one.
My questions were:
Is that plan to have the exact same behavior as GoogleCalendar/Fullcalendar ?
If yes, Is that related to this PR ?
If not, should I open a new issue ?

Here @bkniffler response into the #379 comments

It seems like big calendar tries to follow google calendar in terms of look&feel, which is good since the google devs surely put lots of research into their calendar. I bet the maintainers here would be willing to accept a PR on this matter.
There is 2 things that could to be addressed somewhere around here to imitate gcal:

z-index of sibling events needs to be raised (through inline styles or via an additional class rdc-sibling-event) or rendering of these events needs to happen after non-sibling ones.
only the left offset should vary with siblingIdx rising, while still trying to fill the whole width. Currently the algorithm will make the yellow 70% width/0 offset. It could be better to follow google calendar and make the yellow 100% width/0 offset, the red 70% width/30% offset.

Give it a shot, shouldn't be too hard!

Happy to take a PR for this :)

Did anyone manage to find a solution for this?

I think the z-index problems should be solved by now..

I have this issue, and I can't figure out if it's the same thing, hoping someone can help me:

Hm yeah that doesn't look right. I don't have time to look at it now, but will probably get to it eventually if no one else does it. If you'd like to give it a try, the file you should look at is: https://github.com/intljusticemission/react-big-calendar/blob/585cc392f1acdeff6cf8f1121155a059cba5fa19/src/utils/DayEventLayout.js.


Design Docker orchestration for models (e.g., using Traefik)

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

[ ] Design adapters that should act as a connector of models and the main repository source code.
[ ] Design model orchestration in Docker (and Traefik).

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Closing. See https://github.com/gipplab/cs-insights-prediction-endpoint/issues/19#issuecomment-1214888946


Issues applying a lut3d

Trying to apply a simple LUT sequence to a file

stream = ffmpeg.input('original.mp4')
stream = ffmpeg.filter('lut3d', 'Rec709.cube')
stream = ffmpeg.filter('lut3d', 'Fancy.cube')
stream = ffmpeg.output(stream, 'result.mp4')

I'm sure it's something dumb because I am dumb, but you know... let's see what haappens.

File "E:\file.py", line 37, in apply_luts
stream = ffmpeg.filter('lut3d', 'Rec709.cube')
File "C:\Users\13057\AppData\Local\Programs\Python\Python39\lib\site-packages\ffmpeg_filters.py", line 49, in filter
return filter_multi_output(stream_spec, filter_name, *args, **kwargs).stream()
File "C:\Users\13057\AppData\Local\Programs\Python\Python39\lib\site-packages\ffmpeg_filters.py", line 24, in filter_multi_output
return FilterNode(
File "C:\Users\13057\AppData\Local\Programs\Python\Python39\lib\site-packages\ffmpeg\nodes.py", line 266, in init
super(FilterNode, self).init(
File "C:\Users\13057\AppData\Local\Programs\Python\Python39\lib\site-packages\ffmpeg\nodes.py", line 200, in init
stream_map = get_stream_map(stream_spec)
File "C:\Users\13057\AppData\Local\Programs\Python\Python39\lib\site-packages\ffmpeg\nodes.py", line 133, in get_stream_map
return stream_map
UnboundLocalError: local variable 'stream_map' referenced before assignment

stream = ffmpeg.input('original.mp4')
video = stream.video.filter('lut3d', 'Rec709.cube')
video = video.filter('lut3d', 'Fancy.cube')
stream = ffmpeg.output(stream.audio, video, 'result.mp4')
ffmpeg.run(stream)

Figured it out by splitting the filters into video and audio independently... will close for anyone who comes after me.


CircularProgressIndicator should provide a simple color setting

Steps to Reproduce
new CircularProgressIndicator(
        valueColor: new AlwaysStoppedAnimation<Color>(Colors.green)

I had search quite a bit to find the information in gitter how to change the progress bar color and wondered why there is no direct setting for the color to make this easier.
Flutter Doctor

C:\Projects\emoji>flutter doctor
[√] Flutter (on Microsoft Windows [Version 10.0.16299.125], locale en-US, channel alpha)
    • Flutter at c:\sdks\flutter
    • Framework revision 8f65fec5f5 (3 days ago), 2017-12-12 09:50:14 -0800
    • Engine revision edaecdc8b8
    • Tools Dart version 1.25.0-dev.11.0
    • Engine Dart version 2.0.0-edge.d8ae797298c3a6cf8dc9f4558707bd2672224d3e

[√] Android toolchain - develop for Android devices (Android SDK 27.0.1)
    • Android SDK at C:\Users\ride4\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-27, build-tools 27.0.1
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b01)

[√] Android Studio (version 3.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b01)

[√] IntelliJ IDEA Community Edition (version 2017.2)
    • Flutter plugin version 19.1
    • Dart plugin version 172.4343.25

[√] Connected devices
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 7.1.1 (API 25) (emulator)

You can use Theme here
new Theme(
      data: Theme.of(context).copyWith(accentColor: Colors.yellow),
      child: new CircularProgressIndicator(),
    );

I agree that the fact that one can use AlwaysStoppedAnimation<Color>(color) as valueColor is a little obscure.  It's currently mentioned in the documentation for the valueColor properties but not in the progress indicator class docs.
Providing a parameter that's just shorthand for AlwaysStoppedAnimation seemed like overachieving a little.
Updated the progress indicator docs here: https://github.com/flutter/flutter/pull/29564. Hopefully that should bring AlwaysStoppedAnimation out of the shadows :-).

I disagree - from the user perspective, it takes several minutes if not longer to find the docs for this obscure setting. As a developer, I start with the IDE (Intelly Sense) dropdown help. Then I have startup the docs... etc. Adding a shorthand would probably take less than a minute to add but would save many people valuable time down the road and adds consistency throughout the framework. Just my 2 Cents.

You can add this code.
CircularProgressIndicator(
valueColor: new AlwaysStoppedAnimation(Colors.white),
),
Found At Here

You can add this code.
CircularProgressIndicator(
valueColor: new AlwaysStoppedAnimation(Colors.white),
),
Found At Here


fix: bug in updating input & output amount

Summary
solved two issues:

Incorrect updating of the input amount occurs when the source token is eliminated.
The dollar value at the destination is not updated accurately when tokens are removed.

Fixes # (issue)
The issue was that the values weren't updated appropriately when the tokens were removed.
In order to improve display, I added a condition to the inputs component that states that values will be presented correctly in the event that the token is removed or the USD value is null.
How did you test this change?
It is preferable to take the test on the playground:

First, indicate the token and input's default values.
Navigate to the token selection page. Choose all options without choosing a token.
Return to the home screen.
In this instance, the USD values ought to be shown appropriately.

Checklist:

[x] I have performed a self-review of my code

I think the value of realUsdValue should also be updated
Because now when we show zero dollar amount, the tooltip is still showing the previous amount.

I think the value of realUsdValue should also be updated Because now when we show zero dollar amount, the tooltip is still showing the previous amount.
Please check if it needs to be updated elsewhere

I fixed, now updated real Usd Value when delete selected token

I think the value of realUsdValue should also be updated Because now when we show zero dollar amount, the tooltip is still showing the previous amount.
Please check if it needs to be updated elsewhere

fixed


Audio Setup

Hello!
Awesome to see this project happening!
Was wondering - audio setup should be the same as https://github.com/not-matt/Systematic-LEDs ? any additional setting required?

Nope, just download and install LedFX! Works with SysLED Arduino firmware.
On Fri, Mar 8, 2019, 21:18 Yariv<EMAIL_ADDRESS>wrote:

Hello!
Awesome to see this project happening!
Was wondering - audio setup should be the same as
https://github.com/not-matt/Systematic-LEDs ? any additional setting
required?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ahodges9/LedFx/issues/35, or mute the thread
https://github.com/notifications/unsubscribe-auth/Ae5azFB9SuZBqK8DPAlnq7d96N2ftAN7ks5vUtO2gaJpZM4bmJTR
.


src: using ubi8/nodejs-12 instead of nodeshift/centos7-s2i-nodejs

@lholmquist ubi8/nodes-12 is available :+1:
/me already tested locally in crc and it is working fine.

Pull Request Test Coverage Report for Build 568

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

Totals

Change from base Build 566:
0.0%

Covered Lines:
12

Relevant Lines:
12

💛  - Coveralls

missed the applicaiton.yaml,  https://github.com/nodeshift-starters/nodejs-rest-http/blob/master/.openshiftio/application.yaml#L54

Impressive...
11:08 $ rg centos7
✘-1 ~/Desktop/examples/nodejs-rest-http [ubi8 L|✚ 2]

rg means ripgrep command , kind of grep alternative...
after that I noticed that rg don't search on hidden files by default ...
It should be
rg centos7 --hidden

Thanks for the review, I'm going to update that :+1:

i noticed the node version in the ubi version is 12.4.0,  LTS node is 12.13.0, do we know when that will be updated.
I think think the current centos7-s2i-nodejs 12.x is 12.12.0

yeah, I noticed that also.
I have no idea when they plan to release a new version, we can take a look on that.


test: TestCreateTraceExporter flaky

Failed once but passed other times, perhaps it is related to using Darwin instead of Linux
--- FAIL: TestCreateTraceExporter (0.37s)
    --- FAIL: TestCreateTraceExporter/Headers (0.00s)
        factory_test.go:145:
                Error Trace:    factory_test.go:145
                Error:          Expected nil, but got: &status.statusError{Code:1, Message:"grpc: the client connection is closing", Details:[]*any.Any(nil), XXX_NoUnkeyedLiteral:struct {}{}, XXX_unrecognized:[]uint8(nil), XXX_sizecache:0}
                Test:           TestCreateTraceExporter/Headers
FAIL
FAIL    github.com/open-telemetry/opentelemetry-service/exporter/opencensusexporter     0.485s

I noticed this happening with TestCreateTraceExporter in the past and this failure is inherited from exporter tests which I copied from old implementation. Definitely needs fixing.

Re-opening, hit again https://travis-ci.org/open-telemetry/opentelemetry-service/builds/563102924?utm_source=github_status&utm_medium=notification on PR #195
--- FAIL: TestCreateTraceExporter (1.99s)
    --- FAIL: TestCreateTraceExporter/UseSecure (0.81s)
        factory_test.go:167:
            	Error Trace:	factory_test.go:167
            	Error:      	Expected nil, but got: &status.statusError{Code:1, Message:"grpc: the client connection is closing", Details:[]*any.Any(nil), XXX_NoUnkeyedLiteral:struct {}{}, XXX_unrecognized:[]uint8(nil), XXX_sizecache:0}
            	Test:       	TestCreateTraceExporter/UseSecure
FAIL


Changes on storage module

Several enhancements can be added to storage module:

Add the ability to provision storage general purpose v2
Make several properties configurable:

accountType. This is the name of the sku. Allowed values: [Standard_LRS, Standard_GRS, Standard_RAGRS, Standard_ZRS, Premium_LRS, Premium_ZRS]
accessTier. Allowed values: [Hot, Cool]. Hot storage is optimized for storing data that is accessed frequently ,and cool storage is optimized for storing data that is infrequently accessed and stored for at least 30 days.
supportsHttpsTrafficOnly. Allows https traffic only to storage service if sets to true.

Make service instance updatable.

I'll separate these features into several PRs as in Redis module.

I think maybe as part of this work, it might be good to investigate if more info is needed in the credential?
 I think you can infer these things from the name of the storage account, but it might be good to provide these to make life easier for the OSBA user? I believe that is the info the user was looking for in #578 .

Oh, thanks for the tips! Agree that it should be added to the credential.


Import singer-tools to SDK, resolving any version conflicts

Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/103
Originally created by @aaronsteers on 2021-04-15 15:58:36

Background

singer-tools has helpful tools, like singer-infer-schema
That package doesn't get a lot of updates, has several known bugs, and has conflicting version with more recently built versions
Developers of the SDK are likely to want these tools (or similar) and may have difficulty getting them to work with the SDK due to version conflicts.

Re slack conversation here: https://meltano.slack.com/archives/CFG3C3C66/p1618501051356400?thread_ts=1618494607.353700&cid=CFG3C3C66
Suggested
We can possibly import (some of) the tools into our repo, since they are also under Apache 2.0, and iterate from there.

View 2 previous comments from the original issue on GitLab


foundation-apps build fails

When I run foundation-apps watch all is well, when I run foundation-apps build I fail.  Below is the failure.  Wanting to just build the app into the build folder then deploy that to my web server as part of a Continuous Integration build process.  Assuming this is what I want, foundation-apps build
Thoughts?
Ken.Crismon@62PYL12 /c/tfs/VTNG/Branches/Features/VTNG (Dillard)
$ foundation-apps build
npm ERR! Error: ENOENT, open 'c:\tfs\VTNG\Branches\Features\VTNG\node_modules\bu
ild\package.json'
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR!     http://github.com/npm/npm/issues
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "c:\Program Files\nodejs\\node.exe" "c:\Program Files\nod
ejs\node_modules\npm\bin\npm-cli.js" "start" "build"
npm ERR! cwd c:\tfs\VTNG\Branches\Features\VTNG
npm ERR! node -v v0.10.32
npm ERR! npm -v 1.4.28
npm ERR! path c:\tfs\VTNG\Branches\Features\VTNG\node_modules\build\package.json
npm ERR! code ENOENT
npm ERR! errno 34
npm

Try running npm start build manually in your command line and see if that works. Occasionally we've had issues where, for some reason, the user's machine freaks out if you add more arguments after npm start.

@gakimball I believe this is because of a change in the "npm start" command in a somewhat recent version. @kencrismontp is likely running an older version of NPM and should update to the latest using sudo npm update npm -g.
See this commit for more details: https://github.com/npm/npm/commit/df4b0e7fc1abd9a54f98db75ec9e4d03d37d125b

Yep, it looks like version 2.0.0 of npm introduced that change. I added a remark to the Install & Update page advising users to update their system's npm if they aren't installing a new copy of Node.

Thanks for looking into this!
All is better.

Awesome, glad to hear it!

But for God's sake: never, never, never run "npm update npm -g" :
https://github.com/npm/npm/issues/4099
https://github.com/npm/npm/issues/6247

@k-j-kleist Aren't those issues referring to running npm update -g not npm update npm -g?
I said to run sudo npm update npm -g, which for me recently was the only way I could update NPM without it breaking.

Quoting from https://docs.npmjs.com/misc/faq:
How do I update npm?
npm install npm -g

Yeah, I did that and it spat an error and broke npm! Hence eventually settling on the other command.


Using normal onActivityResult in fragment

 Options options = new Options();
    options.setToolbarColor(ContextCompat.getColor(getActivity(), R.color.colorAccent));
    options.setAspectRatio(500, 500);

RxPaparazzo.register(this);
Firstly, thanks for perfect library. But, i have a problem with using onActivityResult. I know you dont like this but, my project gives some error with your solution. So how can i get path of image when photo cropped? Thank you
`public void onActivityResult(int requestCode, int resultCode, Intent data) {
if (requestCode == REQUEST_GALLERY && resultCode == Activity.RESULT_OK&& null != data) {

    return;
}

}`
i want to both of camera and gallery code for my project. Thanks
By the way i'm using for choose photo and crop, with this code:
size = Size.Original; RxPaparazzo.takeImage(this) .size(size) .crop(options) .usingCamera() .subscribe();
is this true?

HI @canberkcakmak
Sorry, but I can't understand the problem. I'm only can advice you to check the example using a fragment.

I said, you were used this method for get image path : `.subscribe(response -> {
if (response.resultCode() != Activity.RESULT_OK) {
response.targetUI().showUserCanceled();
return;
}
                response.targetUI().loadImage(response.data());
            });`

But i want this method:
`if (requestCode == REQUEST_GALLERY && resultCode == Activity.RESULT_OK&& null != data) {
return;

}
}``
how can i convert it?

You need to specify previously what component to use. Pick camera or gallery, but you can't use both of them in the same intent call. But again, I'm not sure about the question.

But it never @Override in onActivityResult. In debug mode, it never returns or enter in this part :
`@Override
public void onActivityResult(int requestCode, int resultCode, Intent data) {
if (resultCode == RESULT_OK && requestCode == UCrop.REQUEST_CROP) {
final Uri resultUri = UCrop.getOutput(data);
    } else if (resultCode == UCrop.RESULT_ERROR) {
        final Throwable cropError = UCrop.getError(data);
    }
}`


Add codeball workflow

Stack:

#8
#7 ⬅
#5
#4
#3

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.


Details about the MKGC mission

First of all, thank you to the author for such valuable work. I have a question about the MKGC task, and I hope the author can help to answer it.  In the MKGC task, the five KGS were used to learn the features of nodes by GCN respectively for prediction, or were the five KGS aligned to see a complete graph and directly learn the features of nodes?

Thank you for your question.
For each run, only one KG (e.g. ja) missing triples are predicted and the model is allowed to fully observe all the other KGs (es, el, fr, en).
Five KGs were not aligned explicitly before performing the completion task but the model implicitly optimizes alignment loss among all pairs of KGs. The model is also trained to maximize scores of observed triples of all KGs.


IP firewall docs do not explain configuration required to use Data Explorer with IP firewall

This paragraph does not fully describe behavior in Data Explorer: "When using IP firewall, it is recommended to allow Azure portal to access your account. Access is required to allow use of data explorer as well as to retrieve metrics for your account that show up on the Azure portal."
We have recently found that in addition to allowing portal access, the IP of the user viewing Data Explorer also needs to be added to the IP firewall whitelist. This is according to a banner currently being displayed for us in Azure Portal, though I haven't seen this documented anywhere else:
"The way Data Explorer accesses your databases and containers has changed and you need to update your Firewall settings to add your current IP address to the firewall rules. For your convenience we prepared the change already, just click 'Save' to save the changes. Note that firewall changes may take up to 15min to propagate. If you need access urgently or for some reason you are unable to update firewall settings, you can use https://cosmos.azure.com which is not updated at this time, and offers access to your data as long as the "Allow portal access" knob is checked."

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

ID: 5d6fa068-69da-7a32-6479-1145f14f2ed2
Version Independent ID: 952c3241-3f4c-b319-6457-02701b24d46d
Content: IP firewall for Azure Cosmos accounts
Content Source: articles/cosmos-db/firewall-support.md
Service: cosmos-db
GitHub Login: @kanshiG
Microsoft Alias: govindk

@c-d Thank you for for bringing this to our notice.
We are assigning this issue to the content author to update as appropriate.

@c-d Thanks for pointing out, looks like this informational message was recently added. I submitted an update to the doc to mention the IP address condition.
We will now close the issue if there aren't any further questions.
#please-close

Thanks @SnehaGunda, sounds good to me.


About the setting in ablataion studies.

Hello,
Thanks for your inspiring work~
In the Sec. 6.4 of the main paper, you mentioned that the ablation analyses are conducted with shrunk LiDAR images (64*512). Could you share more details with us? change the image_prop[hight][width] directly?
Besides, it would be grateful if you could share us with the hyperparameters of training under this setting. (Batch size, learning rate, epochs, etc).
Thanks again for your insightful work.

Thank you. Yes, you can directly change the image_prop[hight][width]. As for the hyperparameters of training under this setting, I am not quite sure since it has been a long time. We didn't carefully tune these hyperparameters before, so I think you maybe just need to keep the same training recipe, it will reflect the similar conclusions.

Thanks for your quick response~


Pipenv version doesn't support categories

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
pip
Package manager version
pipenv 2022.10.25
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
No response
Updated dependency
No response
What you expected to see, versus what you actually saw
We've started using Pipfile categories to group some optional dependencies in our project, however it seems the dependabot is using pipenv version 2022.4.8.
Dependabot is writing the old lock file format, without our optional category. Fortunately this is caught in our build process, which uses the a newer versions of pipenv and detects that the lock file hashes to not match.
Categories were introduced in version 2022.10.10.
Please could you upgrade to a more recent version of pipenv?
Alternatively, are we able to specific a newer pipenv version ourselves in our dependaboy.yml ?
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response

We are currently pinned to 2022.4.8 to maintain Python 3.6 support. I believe we made an attempt to allow newer pipenv versions for newer Python versions but were unable to get it to work correctly. I will make another attempt and document the findings here.

@deivid-rodriguez was already working on this: #6104. We have a number of tests that fail due to changes in pipenv args and error output. It looks like we're going to need to match pipenv version with each project since the output (lockfile format and errors) change between versions.
Unfortunately, I don't think this is trivial as each project might use a different method to bootstrap pipenv. Out of curiosity how do you bootstrap pipenv in your project? The most common method I think I've seen is to use a dedicated requirements-pipenv.txt.

Out of curiosity how do you bootstrap pipenv in your project?

We're deploying through docker, so for us we just pip install --upgrade pipenv in our Dockerfile and in our CI environment.

Howdy -- pipenv maintainer here for the past year.  I just came to look for if dependabot supported named package categories and if it makes use of --keep-outdated which we plan to drop support for (it doesn't appear that dependabot uses this flag).
I know we had to change underlying library for the Pipfile/lockfile, but I did not think there were these compatibility issues.  I would be happy to shed more light on any issues if you could provide more details on what you have encountered so far.

Thanks so much for chiming in @matteius, and sorry for not saying anything before 🙏.
Upgrading Pipenv and getting it to a good state should be much easier with your support ❤. I think I'll ask some questions at #6104 when I get back to working on it if you're still willing to help.

We have now updated pipenv, so closing this! :tada:


KAFKA-6238: Fix 1.0.0 upgrade instructions relating to the message format version

The upgrade instructions concerning the message format versions did not account for upgrades from versions prior to 0.11.0.x.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@ijuma when are we going to push the changes to kafka-site?

@omkreddy I'll push to site today.

@hachikuji Thanks for pushing the changes to the website!