Set seconds of dates per default to '00' (so time should be 'XX:XX:00')

Is your feature request related to a problem?

When creating exercises or exams you need to specify a lot of dates (e.g. visibility/start/end/assessment/due-date). Therefore you only have the date + the time in hours and minutes as input. Seconds then get set automatically with the seconds from the current time. This is a bit annoying, as in most cases seconds should just equal '00' (e.g. exam starting/ending times should be precise to prevent any complaints by students) and therefore need to be changed manually afterwards.
Describe the solution you'd like

When dates are determined for exercises/exams, the resp. seconds should just be set to '00' per default, as this would be the required value for appr. 99% of the cases.
Describe alternatives you've considered

An alternative would be to change the input field so that you could also define the seconds directly when determining the date.
From my perspective the other solution (seconds = '00' per default) would be better and way less effort.
Additional context

dates in exercise creation (the seconds would need to be changed manually 3x):

dates in exercise creation (the seconds would need to be changed manually 6x):

input field for dates (seconds cannot be defined):

Duplicate of #1649


Config Generator - Getting ValueError: If using all scalar values, you must pass an index

Describe the bug
When testing a PR and compare with the latest deploy version, found this error when setting up a market on kucoin and binance

# dashboard logs
2024-06-26 12:36:04.033 Uncaught app exception
Traceback (most recent call last):
  File "/opt/conda/envs/dashboard/lib/python3.10/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 584, in _run_script
    exec(code, module.__dict__)
  File "/home/dashboard/frontend/pages/config/pmm_dynamic/app.py", line 40, in <module>
    candles = get_candles(connector_name=inputs["candles_connector"], trading_pair=inputs["candles_trading_pair"], interval=inputs["interval"], days=days_to_visualize)
  File "/opt/conda/envs/dashboard/lib/python3.10/site-packages/streamlit/runtime/caching/cache_utils.py", line 168, in wrapper
    return cached_func(*args, **kwargs)
  File "/opt/conda/envs/dashboard/lib/python3.10/site-packages/streamlit/runtime/caching/cache_utils.py", line 197, in __call__
    return self._get_or_create_cached_value(args, kwargs)
  File "/opt/conda/envs/dashboard/lib/python3.10/site-packages/streamlit/runtime/caching/cache_utils.py", line 224, in _get_or_create_cached_value
    return self._handle_cache_miss(cache, value_key, func_args, func_kwargs)
  File "/opt/conda/envs/dashboard/lib/python3.10/site-packages/streamlit/runtime/caching/cache_utils.py", line 280, in _handle_cache_miss
    computed_value = self._info.func(*func_args, **func_kwargs)
  File "/home/dashboard/frontend/pages/config/utils.py", line 23, in get_candles
    df = pd.DataFrame(backend_client.get_historical_candles(connector_name, trading_pair, interval,
  File "/opt/conda/envs/dashboard/lib/python3.10/site-packages/pandas/core/frame.py", line 778, in __init__
    mgr = dict_to_mgr(data, index, columns, dtype=dtype, copy=copy, typ=manager)
  File "/opt/conda/envs/dashboard/lib/python3.10/site-packages/pandas/core/internals/construction.py", line 503, in dict_to_mgr
    return arrays_to_mgr(arrays, columns, index, dtype=dtype, typ=typ, consolidate=copy)
  File "/opt/conda/envs/dashboard/lib/python3.10/site-packages/pandas/core/internals/construction.py", line 114, in arrays_to_mgr
    index = _extract_index(arrays)
  File "/opt/conda/envs/dashboard/lib/python3.10/site-packages/pandas/core/internals/construction.py", line 667, in _extract_index
    raise ValueError("If using all scalar values, you must pass an index")
ValueError: If using all scalar values, you must pass an index

# backend logs
INFO:     <IP_ADDRESS>:33054 - "GET /is-docker-running HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:33056 - "GET /all-controller-configs HTTP/1.1" 200 OK
2024-06-26 12:36:04,025 - asyncio - ERROR - Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0xffff7c352590>
2024-06-26 12:36:04,026 - asyncio - ERROR - Unclosed connector
connections: ['[(<aiohttp.client_proto.ResponseHandler object at 0xffff7c358760>, 6730.242969143)]']
connector: <aiohttp.connector.TCPConnector object at 0xffff7c353d90>
INFO:     <IP_ADDRESS>:33062 - "POST /historical-candles HTTP/1.1" 200 OK

Check traceback seems to be pointing to historical candles. Tried to check if we can reproduce using data and MACD_BB V1

Steps to reproduce bug

Clone latest deploy version then setup bash setup.sh
Go to Dashboard page
Go to Config Generator then PMM Dynamic (on this test we used kucoin XCAD-USDT, binance FIRO-USDT) then observe error on setup
Go to data then download candles for the same market and it would return same error

Yes I am getting this error as well anytime I try to load candlestick charts both on hummingbot deploy and dashboard/backend-api/hummingbot repos.  Following.

When testing PR today, found this issue reproduced on grid_strike controller config's default value

Dashboard logs:
2024-11-11 13:41:47.477 Uncaught app exception
Traceback (most recent call last):
  File "/home/rapcmia/miniconda3/envs/dashboard/lib/python3.10/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 584, in _run_script
    exec(code, module.__dict__)
  File "/home/rapcmia/github/hummingbot/dashboard/190/frontend/pages/config/grid_strike/app.py", line 63, in <module>
    candles = get_candles(
  File "/home/rapcmia/miniconda3/envs/dashboard/lib/python3.10/site-packages/streamlit/runtime/caching/cache_utils.py", line 168, in wrapper
    return cached_func(*args, **kwargs)
  File "/home/rapcmia/miniconda3/envs/dashboard/lib/python3.10/site-packages/streamlit/runtime/caching/cache_utils.py", line 197, in __call__
    return self._get_or_create_cached_value(args, kwargs)
  File "/home/rapcmia/miniconda3/envs/dashboard/lib/python3.10/site-packages/streamlit/runtime/caching/cache_utils.py", line 224, in _get_or_create_cached_value
    return self._handle_cache_miss(cache, value_key, func_args, func_kwargs)
  File "/home/rapcmia/miniconda3/envs/dashboard/lib/python3.10/site-packages/streamlit/runtime/caching/cache_utils.py", line 280, in _handle_cache_miss
    computed_value = self._info.func(*func_args, **func_kwargs)
  File "/home/rapcmia/github/hummingbot/dashboard/190/frontend/pages/config/utils.py", line 22, in get_candles
    df = pd.DataFrame(backend_client.get_historical_candles(connector_name, trading_pair, interval,
  File "/home/rapcmia/miniconda3/envs/dashboard/lib/python3.10/site-packages/pandas/core/frame.py", line 778, in __init__
    mgr = dict_to_mgr(data, index, columns, dtype=dtype, copy=copy, typ=manager)
  File "/home/rapcmia/miniconda3/envs/dashboard/lib/python3.10/site-packages/pandas/core/internals/construction.py", line 503, in dict_to_mgr
    return arrays_to_mgr(arrays, columns, index, dtype=dtype, typ=typ, consolidate=copy)
  File "/home/rapcmia/miniconda3/envs/dashboard/lib/python3.10/site-packages/pandas/core/internals/construction.py", line 114, in arrays_to_mgr
    index = _extract_index(arrays)
  File "/home/rapcmia/miniconda3/envs/dashboard/lib/python3.10/site-packages/pandas/core/internals/construction.py", line 667, in _extract_index
    raise ValueError("If using all scalar values, you must pass an index")
ValueError: If using all scalar values, you must pass an index

Note: When changed connector like OKX or Kucoin, seems to fix itself. Only happens on binance for grid-strike co
Steps to reproduce:

Setup dashboard/backendapi source or docker build
Also you can run setup deploy and load dashboard
Go to Config Generator -> Grid Strike

As per discussed with dev team, this error commonly happens when it takes time to load or fetch historical candles from the selected exchange. Observed this happened Hyperliquid's HYPEUSDC using GS controller, we let dashboard (config generator) to load the candles of the selected market by waiting for couple of minutes and able to create controller successfully.
Ticket will remain open until we found a fix for this error


Datepicker calendar flickers behind element before dismissed

Describe the bug
Datepicker calendar flickers behind element before dismissed
To Reproduce
on https://auro-prod-site-w2.azurewebsites.net/components/auro/datepicker

scroll down to where calendar overlays tabs
close calendar,

Steps to reproduce the behavior:
on Auro site

go to https://auro-prod-site-w2.azurewebsites.net/components/auro/datepicker
scroll down to where calendar overlay would be on top of nav tabs (Datepicker, Install, API, etc)
click on datepicker input to open calendar
click outside to close datepicker
on https://www.alaskaair.com/search-qa/
go to https://www.alaskaair.com/search-qa/
click on either Departing or Returning datepicker
click somewhere on the page to dismiss the datepicker

Expected behavior
datepicker calendar should dismiss without having some weird flickering/z-index
Screenshots
auro site:
https://user-images.githubusercontent.com/13775747/189238821-99221e98-6f1a-4b38-9f59-99802097872f.mov
as.com - qa
https://user-images.githubusercontent.com/13775747/189238853-346811cb-5049-4a73-afea-488a6d1d25a0.mov
Desktop (please complete the following information):

OS: Mac iOS
Browser: chrome(Version 105.0.5195.102), firefox(104.0.2), safari(v15.6)

This is an interesting bug. I see what you are talking about in the attached videos, but I am unable to repro. Are there others on your team that can confirm?

I am unable to reproduce this bug.

Confirmed, unable to repro this issue. @vhdinh can you validate your repro criteria?

Completed further validation testing and I am also unable to repro this bug. This ticket is being closed.


Use new cointype on new wallets

see decrediton support for both 20 and 42 https://github.com/decred/decrediton/blob/master/app/wallet/constants.js#L30-L33
current dcrandroid derivation path is set as a constant, doesnt change. https://github.com/decred/dcrandroid/blob/master/app/src/main/java/com/dcrandroid/data/Constants.java#L87-L88

Add some UI bits necessary to explain everything the user needs to know about cointype and 20 vs 42. Prevent situation like when dcrwallet warns about old cointype and you have no idea what to do about it.

related to https://github.com/decred/dcrwallet/issues/1422

there is a resolution for this upstream now. unblocked.
https://github.com/decred/dcrwallet/pull/1499


New way to install flow

Add a Dockerfile that can run with a desktop on your browser with every flow packages installed and ready to use

+1, we should clarify local installation vs. non-local installation and ensure that developers install the local install

Actually, @lucfisc can u replace the table of contents with this?
.. contents:: Table of contents

@AboudyKreidieh  Done

A few more minor comments, almost there!

Added the dockerfile, publish the docker to the docker hub. RLLIB is installed, RLLAB is installed , FLOW is installed. Documentation is up to date

Thanks! Just to check, @lucfisc , ready to merge?


Server-unit-test cannot bring up any file is written by es6(babel)

Example:
Test = {a: 1};

in file /lib/test.jsx, which is complied by grigio:babel .
I get error Test is not defined when I try to run server-unit-test by:
describe('test', function() {
  it('should work', function() {
    expect(Test.a).toBe(1);
  });
});

This code works well in server-integration-test, client-unit-test and client-integration-test.
Or is this a problem I should report to grigio:babel ?

It's a limitation of the server unit mode. Please just use the server integration mode for your unit tests. In the next release the unit mode will be removed anyway. If you need any functionality from the server unit mode that is not available in the server integration mode, let me know.

Cool, thank you Sanjo. Just to confirm, in the next release, both unit mode on client and server will be removed right?

both unit mode on client and server will be removed right?

Yes.


Impl manage retweet

Codecov Report

Merging #110 (7516504) into main (dc82e49) will increase coverage by 0.02%.
The diff coverage is 57.69%.

@@            Coverage Diff             @@
##             main     #110      +/-   ##
==========================================
+ Coverage   56.99%   57.02%   +0.02%
==========================================
  Files          30       30
  Lines        1493     1545      +52
==========================================
+ Hits          851      881      +30
- Misses        406      417      +11
- Partials      236      247      +11

Impacted Files
Coverage Δ

retweet.go
56.41% <56.00%> (-0.74%)
:arrow_down:

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

Continue to review full report at Codecov.

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


S2 Time-Series GEE Python API

Hey @bethdelaney , I've made a new PR because I got confused when checking out an old commit on the s2_timeseries_gee branch, so I made a new branch.
For posteriority and anyone else reading this in the future (hello future!) below is a description of what this PR does:
I am developing services to work with GeoData360, I have to work with Python programmatically i.e. everything has to be run in a single go from start to finish, for use on a cloud based platform. Additionally, assets cannot be created programmatically (to my knowledge...), so assuming the user for a service uploads a vector file, I convert the vector file into a GEE geometry.
The script get_sentinel2_timeseries.py essentially:

takes a vector file for an AOI
initialises the GEE project
for each polygon in the vector file:

converts vector to GEE geometry
queries S2 archive with the geometry
QC checks the ImageCollection
computes NDVI, NBR, NDWI and SAVI
optionally, saves the first image of the ImageCollection as pngs of the indices for visualisation
return the ImageCollection as CSV with indices

Whilst the script apply_smoothing.py:

Applies Savitzky-Golay filter smoothing to each observation of a timeseries

@bethdelaney merge if you are happy with the changes. There are other improvements to make, but that's future stuff...


Name argument of Test.prototype.test is not optional when providing options object

Calling tap.test(options, testFunction) will create a subtest with the name "[object Object]", instead of "(unnamed test)". The subtest ignores the supplied options object.
This behaviour surprises me because the documentation of Test.prototype.test suggests that all three arguments are optional:

t.test([name], [options], [function])

Huh.  Yeah, that seems like a bug for sure.
Patch welcome!


fix(leaving-ibm): fixed text styles

Related Ticket(s)
#5003
Description
Fixed the React Wrapper text styles appearing larger than expected

@kennylam Getting rid the span tag and adding the slotted  selector works for web-components.  There seems to be a span styling on the react-wrapper version that's overwriting some of the slotted styles

There seems to be a span styling on the react-wrapper version that's overwriting some of the slotted styles

@andysherman2121 You need to make the change here
https://github.com/carbon-design-system/carbon-for-ibm-dotcom/blob/50daa3234a48a8e6e83eee46ea8fbaa45e4bd9a6/packages/web-components/src/components-react/leaving-ibm/leaving-ibm-composite.tsx#L101

@kennylam When I got it working in react-wrapper, the web component version styling wasn't working.  So I have two slotted stylings in the scss


All Argo Workflows logs are marked as error in stackdriver (GCP)

Summary
Similar problem to closed unsolved issue #4471
On Google Cloud all logs generated by argo-server and workflow-controller can not be properly parsed. Meaning all logs show as ERROR logs in Google Stackdriver.
One of the reasons might be that all the logs are dumped to stderr so it's handled as error.
Also Stackdriver is using severity keyword instead of info to parse logging level.
Is there a way to define custom way of logging for argo-server and workflow-controller? Or change the default logging output to stdout?
Another problem is frequency of logging Enforcing history limit and leases it too high and it's polluting our logs.
Can I somehow define that I want to log only warning or higher in argo-server and workflow-controller?
Diagnostics
What Kubernetes provider are you using?:
Google Cloud platform kubernetes 1.17.15
What version of Argo Workflows are you running?
Tested with Argo Workflows installed by release v2.12.9 and also with v3.0.0-rc2
It can be reproduced by installing Argo on GCP with:
kubectl apply -n argo -f https://raw.githubusercontent.com/argoproj/argo/anyversion/manifests/install.yaml
Following logs keep poluting stackdriver every 5s or so.
time="2021-02-18T13:05:00.629Z" level=info msg="Enforcing history limit for 'workflow'" namespace=default workflow=workflow
time="2021-02-18T13:05:00.630Z" level=info msg="Enforcing history limit for 'workflow'" namespace=default workflow=workflow
time="2021-02-18T13:05:00.630Z" level=info msg="Enforcing history limit for 'workflow'" namespace=default workflow=workflow
time="2021-02-18T13:05:00.632Z" level=info msg="Enforcing history limit for 'workflow'" namespace=default workflow=workflow
time="2021-02-18T13:05:04.345Z" level=info msg="Get leases 200"
time="2021-02-18T13:05:04.361Z" level=info msg="Update leases 200"
time="2021-02-18T13:05:09.373Z" level=info msg="Get leases 200"
time="2021-02-18T13:05:09.379Z" level=info msg="Update leases 200"
time="2021-02-18T13:05:10.641Z" level=info msg="Enforcing history limit for 'workflow'" namespace=default workflow=workflow
time="2021-02-18T13:05:10.642Z" level=info msg="Enforcing history limit for 'workflow'" namespace=default workflow=workflow
time="2021-02-18T13:05:10.643Z" level=info msg="Enforcing history limit for 'workflow'" namespace=default workflow=workflow
time="2021-02-18T13:05:10.643Z" level=info msg="Enforcing history limit for 'workflow'" namespace=default workflow=workflow
time="2021-02-18T13:05:14.384Z" level=info msg="Get leases 200"
time="2021-02-18T13:05:14.392Z" level=info msg="Update leases 200"

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Please consider reopening this; these types of logs should be in debug-only logging.
And also having them result in errors is definitely a surprise; please allow for stdout redirect with some sort of config.

I would also like if this was re-opened, as the logs are all sent to the cloud logging tool of choice and these logs are thus an extra cost on the deployment. I think the cost grows linear to usage too.

@klaucos did u solve 'frequency of logging Enforcing history limit' ?


Cannot read property 'kind' of undefined after upgrade to  "@angular-devkit/build-angular": "^0.1001.0",

🐞 Bug report
Command (mark with an x)

[X] build
[X] serve

Is this a regression?
Yes, the previous version in which this bug was not present was:
Prev version:  0.1000.7
Current Version: ^0.1001.0
Description
I'm using angular CLI project with multiple projects.
After I upgrade the package json with the latest >>  "@angular-devkit/build-angular": "^0.1001.0",
I start to get this error:
ERROR in Cannot read property 'kind' of undefined
For this command:
ng build project-name --prod --aot --source-map --build-optimizer

When I downgrade to  0.1000.7 it back to work
🔬 Minimal Reproduction

🔥 Exception or Error

ERROR in Cannot read property 'kind' of undefined

🌍 Your Environment

Angular CLI: 10.1.0
Node: 12.3.1
OS: darwin x64

Angular: 10.1.0
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... platform-server, router, service-worker
Ivy Workspace: Yes

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.901.12
@angular-devkit/build-angular     0.1001.0
@angular-devkit/build-optimizer   0.901.12
@angular-devkit/build-webpack     0.901.12
@angular-devkit/core              10.1.0
@angular-devkit/schematics        10.1.0
@angular-devkit/schematics-cli    0.901.12
@angular/cdk                      10.2.0
@angular/material                 10.2.0
@ngtools/webpack                  9.1.12
@nguniversal/common               10.0.2
@nguniversal/express-engine       10.0.2
@schematics/angular               10.1.0
@schematics/schematics            0.901.12
@schematics/update                0.1001.0
rxjs                              6.6.2
typescript                        3.9.7
webpack                           4.42.0

Hi, from the ng version I am seeing a number of auto-dated packages example which might not be compatible with Angular CLI version 10.1:
Example:
@angular-devkit/architect         0.901.12
@angular-devkit/build-optimizer   0.901.12
@angular-devkit/build-webpack     0.901.12
@schematics/schematics            0.901.12

If you are depending on these directly you don't need them unless you are developing schematics and builders.
Are you using a custom CLI builder? If so, please try to update to the latest version.

@alan-agius4
I update the above packages and I still have the same issue
Angular CLI: 10.1.0
Node: 12.3.1
OS: darwin x64
Angular: 10.1.0
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... platform-server, router, service-worker
Ivy Workspace: Yes
Package                           Version
@angular-devkit/architect         0.1001.0
@angular-devkit/build-angular     0.1001.0
@angular-devkit/build-optimizer   0.1001.0
@angular-devkit/build-webpack     0.1001.0
@angular-devkit/core              10.1.0
@angular-devkit/schematics        10.1.0
@angular-devkit/schematics-cli    0.901.12
@angular/cdk                      10.2.0
@angular/material                 10.2.0
@ngtools/webpack                  9.1.12
@nguniversal/common               10.0.2
@nguniversal/express-engine       10.0.2
@schematics/angular               10.1.0
@schematics/schematics            0.1001.0
@schematics/update                0.1001.0
rxjs                              6.6.3
typescript                        3.9.7
webpack                           4.42.0

Are you using a custom CLI builder? I am still seeing outdated packages example: @ngtools/webpack 9.1.12, which likely is due to a custom builder.
Most likely the root cause is similar to https://github.com/angular/angular-cli/issues/18615
Can you run npm ls typescript?

@alan-agius4
I don't use a custom CLI builder. I don't know what is it.
The result  for npm ls typescript
<EMAIL_ADDRESS>/../console
├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └─┬<EMAIL_ADDRESS>│     └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>deduped
│ └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
└──<EMAIL_ADDRESS>

@ofirrifo, can you provide a reproduction? Unfortunately, without a reproduction it's hard to tell what is causing the issue.

@alan-agius4
The project is private but I will try to create an public repo

@alan-agius4
I created a new repo with reproduction of my issue
Steps to rep-reduce:

Clone project git clone git@github.com:ofirrifo/ng-issue.git
Install packages npm i
Execute npm scriptnpm run serve:app
Now you will get this error > ERROR in Cannot read property 'kind' of undefined

Same cause as https://github.com/angular/angular-cli/issues/18615 where the presence of an outdate version @angular-builders/custom-webpack is causing issues during module hosting.
Kindly update @angular-builders/custom-webpack to the latest stable version.
npm i @angular-builders/custom-webpack@10 -D
rm -rf node_modules package-lock.json
npm i

/workspace/ng-issue $ npm run serve:app

><EMAIL_ADDRESS>serve:app /workspace/ng-issue
> ng serve app-a --open --port=4400

Compiling @angular/core : es2015 as esm2015
Compiling @angular/common : es2015 as esm2015
Compiling @angular/platform-browser : es2015 as esm2015
Compiling @angular/router : es2015 as esm2015
Compiling @angular/platform-browser-dynamic : es2015 as esm2015

chunk {main} main.js, main.js.map (main) 59.6 kB [initial] [rendered]
chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 141 kB [initial] [rendered]
chunk {runtime} runtime.js, runtime.js.map (runtime) 6.15 kB [entry] [rendered]
chunk {styles} styles.js, styles.js.map (styles) 13.2 kB [initial] [rendered]
chunk {vendor} vendor.js, vendor.js.map (vendor) 2.63 MB [initial] [rendered]
Date: 2020-09-08T12:56:21.900Z - Hash: ea4902c05542db6a1b0a - Time: 13875ms
** Angular Live Development Server is listening on localhost:4400, open your browser on http://localhost:4400/ **
: Compiled successfully.
50% building 0/1 modules 1 active /workspace/ng-issue/projects/app-a/$$_lazy_route_resource lazy groupOpti
Date: 2020-09-08T12:56:23.203Z - Hash: ea4902c05542db6a1b0a
5 unchanged chunks

@alan-agius4 Thanks for your help :)
It did help and now it back to work.
is there a way the next time I will be able to understand alone what is the issue ?

@ofirrifo, without debugging it’s hard to understand and find the root cause of the problem, though typically removing the lock file and node_modules does solve a number of issues.


Move x509 cert logic to sub-directory

The x509 certificate logic has been moved to a dedicated sub-directory
to better group the coming CRL and certificate chain logic.

Motivation

Current dependencies on/for this PR:

main

PR #68   👈

This comment was auto-generated by Graphite.


pkg/maps/metricsmap/: Add a doc.go in the metricsmap pkg

This change adds a doc.go which describes the metricsmap package, so that this package shows up on:
https://godoc.org/github.com/cilium/cilium
Fixes: #4224
Signed-off by: Manali Bhutiyani<EMAIL_ADDRESS>Add a doc.go in the metricsmap pkg

test-me-please

test-docs-please

test-me-please

test-me-please


docs(bigquery): add change log and unit tests

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Created another PR without conflicts


docs(readme): add HTTP/3 Check, hstspreload.org, Bulma

Pull Request Test Coverage Report for Build 1700

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 63.793%

Totals

Change from base Build 1699:
0.0%

Covered Lines:
101

Relevant Lines:
152

💛  - Coveralls


ps shows shows etcdctl's credentials

Hi All,
I am using etcdctl into SystemD start scripts to execute changes into server. For example: change password of some user or update ntp servers.
But the passwords are shown with ps:
# ps -Af|grep etcdctl
root      1389     1  0 08:18 ?        00:00:00 etcdctl -u root:2ecfca1612c7b2d8638a417fe5377f2f exec-watch /client/user/password -- bash -c  if [ "x$ETCD_WATCH_VALUE" != "x" ];then  . /opt/cui/config.cfg || true . /opt/cui/functions  || true not_setup_password="THE-PASSWORD-NOT-SETUP-$$"  previous_value=$(read_config_key "$URL" 2>/dev/null||echo "$not_setup_password" ) # if [ "$previous_value" != "$ETCD_WATCH_VALUE" ];then       echo -e "${ETCD_WATCH_VALUE}\n${ETCD_WATCH_VALUE}\n"|passwd radware &> $OPT_RDWR_LOG/chpassword.${LOG_TIMESTAMP}.log       exit_status=$?       if (($exit_status == 0));then           save_config "${URL}_status" "Success"       else           save_config "${URL}_status" "Failure"       fi  # else #    save_config "${URL}_status" "Already applied" # fi fi

Example /etc/systemd/system/host_ntp.service:
[Unit]
Description=host password backend script
After=syslog.target
After=network.target
Before=lxc.service
BindsTo=etcd.service

[Service]
Type=simple
ExecStart=/usr/local/bin/host_ntp_service.sh
Restart=always
RestartSec=10s
LimitNOFILE=40000
Nice=10

[Install]
WantedBy=multi-user.target

Example /usr/local/bin/host_ntp_service.sh:
. /cui/config.cfg || true
. /opt/cui/functions  || true
export URL="/client/user/password"
exec etcdctl $ROOT_AUTH exec-watch $URL -- bash -c '
if [ "x$ETCD_WATCH_VALUE" != "x" ];then

. /opt/rdwr/dfcc/lib/cui/config.cfg || true
. /opt/rdwr/dfcc/lib/cui/functions  || true

 not_setup_password="THE-PASSWORD-NOT-SETUP-$$"
 previous_value=$(read_config_key "$URL" 2>/dev/null||echo "$not_setup_password" )
# if [ "$previous_value" != "$ETCD_WATCH_VALUE" ];then
      echo -e "${ETCD_WATCH_VALUE}\n${ETCD_WATCH_VALUE}\n"|passwd radware &> $OPT_RDWR_LOG/chpassword.${LOG_TIMESTAMP}.log
      exit_status=$?
      if (($exit_status == 0));then
          save_config "${URL}_status" "Success"
      else
          save_config "${URL}_status" "Failure"
      fi

# else
#    save_config "${URL}_status" "Already applied"
# fi
fi
'

@weldpua2008 Is this an etcd issue? ps should show the args your provided. If someone can see the process you started, he/she already got the access to the machine anyway. But I am not a security expert. You probably should ask some linux security experts instead.

@xiang90 I think it can be problematic because any unprivileged users can see the password in the output of ps command. Hiding a password in argv by modifying the variable would be a common practice, e.g., a case of MySQL: http://www.lenzg.net/archives/256-basic-mysql-security-providing-passwords-on-the-command-line.html
But I don't know the best practice for doing it in go programs (or go programs which use cobra) so I'll seek a suitable method.

@weldpua2008 maybe the easiest workaround is creating a file with 600 permission that has below line:
ETCDCTL_USERNAME=root:2ecfca1612c7b2d8638a417fe5377f2f

and source it from your scripts. Is this work for your case?

Hi,
I have the following etcd version:
# etcdctl -v
etcdctl version 2.2.5

I try to run as in this example:
# ETCDCTL_USERNAME="root:2ecfca1612c7b2d8638a417fe5377f2f" etcdctl set my-key to-a-value
Error:  110: The request requires user authentication (Insufficient credentials) [0]

# export ETCDCTL_USERNAME="root:2ecfca1612c7b2d8638a417fe5377f2f";ETCDCTL_USERNAME="root:2ecfca1612c7b2d8638a417fe5377f2f" etcdctl set my-key to-a-value
Error:  110: The request requires user authentication (Insufficient credentials) [0]
#
# etcdctl -u $ETCDCTL_USERNAME set my-key to-a-value
to-a-value

it's working:
# etcdctl -u root:2ecfca1612c7b2d8638a417fe5377f2f set my-key to-a-value
to-a-value

My ETCD startup script /etc/systemd/system/etcd.service:
[Unit]
Description=etcd key-value store
Documentation=https://github.com/coreos/etcd
After=syslog.target
After=network.target
Before=lxc.service

[Service]
User=etcd
Type=notify
# Run ExecStartPre with root-permissions
PermissionsStartOnly=true
ExecStartPre=-/bin/mkdir -p /var/lib/lxc/etcd/data
ExecStartPre=-/bin/chown -R etcd:etcd /var/lib/lxc/etcd/data
ExecStartPre=-/usr/local/bin/etcd_pre_start.sh
# enable authentification
ExecStartPost=-/usr/local/bin/etcd_post_start.sh

Environment=ETCD_DATA_DIR=/var/lib/lxc/etcd/data
Environment=ETCD_INITIAL_ADVERTISE_PEER_URLS=http://<IP_ADDRESS>:2380
Environment=ETCD_LISTEN_PEER_URLS=http://<IP_ADDRESS>:2380
Environment=ETCD_LISTEN_CLIENT_URLS=http://<IP_ADDRESS>:2378,http://<IP_ADDRESS>:2379
Environment=ETCD_ADVERTISE_CLIENT_URLS=http://<IP_ADDRESS>:2378,http://<IP_ADDRESS>:2379
Environment=ETCD_NAME=host0
#Environment=ETCD_NAME=%m
#Environment="GOMAXPROCS=nproc || (grep -c ^processor /proc/cpuinfo || echo '1')"
Environment="ETCD_INITIAL_CLUSTER=host0=http://<IP_ADDRESS>:2380"
Environment="ETCD_INITIAL_CLUSTER_STATE=new"
Environment="ETCD_INITIAL_CLUSTER_TOKEN=ETCDEinitianTokenF!rDFCC"

ExecStart=/usr/local/bin/etcd
Restart=always
RestartSec=10s
LimitNOFILE=40000
Nice=5

[Install]
WantedBy=multi-user.target

Try with etcd 2.3.7. I do not think we should fix the ps issue. It will also show in history.
I researched around, the suggested ways to make it secure are:

use prompt
use ENV

which are supported by etcdctl today.


Authentication exception (401) when connecting to elasticsearch: 'unable to authenticate user [elastic] for REST request [/]'

PGSync version: 3.1.0
Postgres version:
Elasticsearch/OpenSearch version: elastic search 8.11.1
Redis version: 7.2.3
Python version: 3.11.7
Problem Description:
I'm having trouble with elastic search authentication though I'm setting the same password and SSL certificates, the three of them: client, CA and key certificates.  If I turn off ssl and https as schema everything works fine, but I need to use secure connection. Here below is a reproduceable example. I can login to elasticsearch through kibana and curl just fine (I haven't tested yet with curl supplying the ca and client certificates).
Any feedback on this would be appreciated.
Docker YAML File:
version: '3.9'

services:
  setup:
    networks:
      - elastic
    image: elasticsearch:${STACK_VERSION}
    volumes:
      - certs:/usr/share/elasticsearch/config/certs
    user: '0'
    command: >
      bash -c '
        if [ x${ELASTIC_PASSWORD} == x ]; then
          echo "Set the ELASTIC_PASSWORD environment variable in the .env file";
          exit 1;
        elif [ x${KIBANA_PASSWORD} == x ]; then
          echo "Set the KIBANA_PASSWORD environment variable in the .env file";
          exit 1;
        fi;
        if [ ! -f config/certs/ca.zip ]; then
          echo "Creating CA";
          bin/elasticsearch-certutil ca --silent --pem -out config/certs/ca.zip;
          unzip config/certs/ca.zip -d config/certs;
        fi;
        if [ ! -f config/certs/certs.zip ]; then
          echo "Creating certs";
          echo -ne \
          "instances:\n"\
          "  - name: es01\n"\
          "    dns:\n"\
          "      - es01\n"\
          "      - localhost\n"\
          "    ip:\n"\
          "      - <IP_ADDRESS>\n"\
          > config/certs/instances.yml;
          bin/elasticsearch-certutil cert --silent --pem -out config/certs/certs.zip --in config/certs/instances.yml --ca-cert config/certs/ca/ca.crt --ca-key config/certs/ca/ca.key;
          unzip config/certs/certs.zip -d config/certs;
        fi;
        echo "Setting file permissions"
        chown -R root:root config/certs;
        find . -type d -exec chmod 750 \{\} \;;
        find . -type f -exec chmod 640 \{\} \;;
        echo "Waiting for Elasticsearch availability";
        until curl -s --cacert config/certs/ca/ca.crt https://es01:9200 | grep -q "missing authentication credentials"; do sleep 30; done;
        echo "Setting kibana_system password";
        until curl -s -X POST --cacert config/certs/ca/ca.crt -u "elastic:${ELASTIC_PASSWORD}" -H "Content-Type: application/json" https://es01:9200/_security/user/kibana_system/_password -d "{\"password\":\"${KIBANA_PASSWORD}\"}" | grep -q "^{}"; do sleep 10; done;
        echo "All done!";
      '
    healthcheck:
      test: ['CMD-SHELL', '[ -f config/certs/es01/es01.crt ]']
      interval: 1s
      timeout: 5s
      retries: 120

  es01:
    depends_on:
      setup:
        condition: service_healthy

    networks:
      - elastic
      - frontend
      - data-center

    image: elasticsearch:${STACK_VERSION}
    volumes:
      - certs:/usr/share/elasticsearch/config/certs
      - esdata01:/usr/share/elasticsearch/data
    ports:
      - ${ES_PORT}:9200
    environment:
      - node.name=es01
      - cluster.name=${CLUSTER_NAME}
      - cluster.initial_master_nodes=es01
      - ELASTIC_PASSWORD=${ELASTIC_PASSWORD}
      - bootstrap.memory_lock=true
      - xpack.security.enabled=true
      - xpack.security.http.ssl.enabled=true
      - xpack.security.http.ssl.key=certs/es01/es01.key
      - xpack.security.http.ssl.certificate=certs/es01/es01.crt
      - xpack.security.http.ssl.certificate_authorities=certs/ca/ca.crt
      - xpack.security.transport.ssl.enabled=true
      - xpack.security.transport.ssl.key=certs/es01/es01.key
      - xpack.security.transport.ssl.certificate=certs/es01/es01.crt
      - xpack.security.transport.ssl.certificate_authorities=certs/ca/ca.crt
      - xpack.security.transport.ssl.verification_mode=certificate
      - xpack.license.self_generated.type=${LICENSE}
    mem_limit: ${MEM_LIMIT}
    ulimits:
      memlock:
        soft: -1
        hard: -1
    healthcheck:
      test:
        [
          'CMD-SHELL',
          "curl -s --cacert config/certs/ca/ca.crt https://localhost:9200 | grep -q 'missing authentication credentials'",
        ]
      interval: 10s
      timeout: 10s
      retries: 120

  kibana:
    depends_on:
      es01:
        condition: service_healthy

    networks:
      - elastic

    image: kibana:${STACK_VERSION}

    volumes:
      - certs:/usr/share/kibana/config/certs
      - kibanadata:/usr/share/kibana/data

    ports:
      - ${KIBANA_PORT}:5601

    environment:
      - SERVERNAME=kibana
      - ELASTICSEARCH_HOSTS=https://es01:9200
      - ELASTICSEARCH_USERNAME=kibana_system
      - ELASTICSEARCH_PASSWORD=${KIBANA_PASSWORD}
      - ELASTICSEARCH_SSL_CERTIFICATEAUTHORITIES=config/certs/ca/ca.crt

    mem_limit: ${MEM_LIMIT}
    healthcheck:
      test:
        [
          'CMD-SHELL',
          "curl -s -I http://localhost:5601 | grep -q 'HTTP/1.1 302 Found'",
        ]
      interval: 10s
      timeout: 10s
      retries: 120

  postgres:
    ports:
      - 5432:5432
    image: postgres:16.1
    volumes:
      - "./init_db:/docker-entrypoint-initdb.d"
      # - "../postgres/data:/var/lib/postgresql/data"
    environment:
      - "POSTGRES_USER=revista"
      - "POSTGRES_PASSWORD=${ELASTIC_PASSWORD}"
    restart: always

    networks:
      - data-center

    command:
      - "postgres"
      - "-c"
      - "wal_level=logical"
      - "-c"
      - "max_replication_slots=3"

  redis:
    image: redis:7.2.3
    ports:
      - 6379:6379
    command: redis-server --requirepass ${ELASTIC_PASSWORD}
    networks:
      - data-center

  pgsync:
    build:
      context: ../pgsync
      dockerfile: ./Dockerfile-pgsync

    restart: on-failure

    labels:
      org.label-schema.name: "pgsync"
      org.label-schema.description: "Postgres to Elasticsearch sync"
      com.label-schema.service-type: "daemon"

    sysctls:
      - net.ipv4.tcp_keepalive_time=200
      - net.ipv4.tcp_keepalive_intvl=200
      - net.ipv4.tcp_keepalive_probes=5

    depends_on:
      - postgres
      - redis

    environment:
      - CHECKPOINT_PATH=/pgsync
      - PG_USER=revista
      - PG_HOST=postgres
      - PG_PORT=5432
      - PG_PASSWORD=${ELASTIC_PASSWORD}
      - ELASTICSEARCH_SCHEME=https
      - ELASTICSEARCH_HOST=es01
      - ELASTICSEARCH_PORT=9200
      - ELASTICSEARCH_USER=elastic
      - ELASTICSEARCH_PASSWORD=${ELASTIC_PASSWORD}
      - ELASTICSEARCH_VERIFY_CERTS=True
      - ELASTICSEARCH_USE_SSL=True
      - REDIS_HOST=redis
      - REDIS_PORT=6379
      - REDIS_AUTH=${ELASTIC_PASSWORD}
      - ELASTICSEARCH=True
      - OPENSEARCH=False
      - SCHEMA=/pgsync/schema.json
      - LOG_LEVEL=INFO
      - ELASTICSEARCH_CA_CERTS=/usr/share/elasticsearch/config/certs/ca/ca.crt
      - ELASTICSEARCH_CLIENT_CERT=/usr/share/elasticsearch/config/certs/es01/es01.crt
      - ELASTICSEARCH_CLIENT_KEY=/usr/share/elasticsearch/config/certs/es01/es01.key

    command: ./runserver.sh && sleep inf

    volumes:
      # - ../pgsync/example-schema.json:/pgsync/schema.json
      - ../pgsync/schema.json:/pgsync/schema.json
      - certs:/usr/share/elasticsearch/config/certs

    networks:
      - data-center

volumes:
  certs:
    driver: local
  esdata01:
    driver: local
  kibanadata:
    driver: local

networks:
  networks:
  data-center:
  frontend:
  elastic:

Error Message (if any):
pgsync-1  | Traceback (most recent call last):
pgsync-1  |   File "/usr/local/bin/pgsync", line 7, in <module>
pgsync-1  |  0:00:00.202205 (0.20 sec)
pgsync-1  |     sync.main()
pgsync-1  |   File "/usr/local/lib/python3.11/site-packages/click/core.py", line 1157, in __call__
pgsync-1  |     return self.main(*args, **kwargs)
pgsync-1  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^
pgsync-1  |   File "/usr/local/lib/python3.11/site-packages/click/core.py", line 1078, in main
pgsync-1  |     rv = self.invoke(ctx)
pgsync-1  |          ^^^^^^^^^^^^^^^^
pgsync-1  |   File "/usr/local/lib/python3.11/site-packages/click/core.py", line 1434, in invoke
pgsync-1  |     return ctx.invoke(self.callback, **ctx.params)
pgsync-1  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
pgsync-1  |   File "/usr/local/lib/python3.11/site-packages/click/core.py", line 783, in invoke
pgsync-1  |     return __callback(*args, **kwargs)
pgsync-1  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^
pgsync-1  |   File "/usr/local/lib/python3.11/site-packages/pgsync/sync.py", line 1480, in main
pgsync-1  |     sync: Sync = Sync(
pgsync-1  |                  ^^^^^
pgsync-1  |   File "/usr/local/lib/python3.11/site-packages/pgsync/singleton.py", line 36, in __call__
pgsync-1  |     cls._instances[key] = super(Singleton, cls).__call__(
pgsync-1  |                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
pgsync-1  |   File "/usr/local/lib/python3.11/site-packages/pgsync/sync.py", line 88, in __init__
pgsync-1  |     self.search_client: SearchClient = SearchClient()
pgsync-1  |                                        ^^^^^^^^^^^^^^
pgsync-1  |   File "/usr/local/lib/python3.11/site-packages/pgsync/search_client.py", line 48, in __init__
pgsync-1  |     self.__client.info()["version"]["number"].split(".")[0]
pgsync-1  |     ^^^^^^^^^^^^^^^^^^^^
pgsync-1  |   File "/usr/local/lib/python3.11/site-packages/elasticsearch/_sync/client/utils.py", line 402, in wrapped
pgsync-1  |     return api(*args, **kwargs)
pgsync-1  |            ^^^^^^^^^^^^^^^^^^^^
pgsync-1  |   File "/usr/local/lib/python3.11/site-packages/elasticsearch/_sync/client/__init__.py", line 2278, in info
pgsync-1  |     return self.perform_request(  # type: ignore[return-value]
pgsync-1  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
pgsync-1  |   File "/usr/local/lib/python3.11/site-packages/elasticsearch/_sync/client/_base.py", line 320, in perform_request
pgsync-1  |     raise HTTP_EXCEPTIONS.get(meta.status, ApiError)(
pgsync-1  | elasticsearch.AuthenticationException: AuthenticationException(401, 'security_exception', 'unable to authenticate user [elastic] for REST request [/]')

Try setting the ElasticSearch password to not include special characters.


Reading own MAC address

Hi There!
Is there a way to read the ESP32 BT MAC address?
Thanks!

Only with plain esp-idf command:
https://esp-idf.readthedocs.io/en/latest/api-reference/system/base_mac_address.html

would be a nice feature to add :-)


Link from hex to github page incorrect

Not a source issue of course, but I found that the easiest thing to point it out:
Hex is pointing to https://github.com/robconery/stripe-elixir rather than to https://github.com/robconery/stripity-stripe

Yeah I know - I can't get them to update the package settings. Not sure why.

It seems to be working correctly now

Confirmed - it is working now.


Upgrade Elasticsearch to 7.17

This was my plan. But this tag does not exist:
https://hub.docker.com/_/elasticsearch?tab=tags&page=1&name=7.17


feat: bump jQuery to v3.6.0

Description
Building on top of https://github.com/lsegal/yard/pull/1358
Testing
The generate API reference can be viewed at https://lsegal-yard-1397.netlify.app/

The jQuery version is "3.6.0", verified by running $.fn.jquery in Console.
All toggle functionalities are working:

Table of Contents on landing page
https://user-images.githubusercontent.com/16024985/131574652-39808355-b4e5-43ba-918d-37459158e1de.mov

Inheritance tree on Array page.
https://user-images.githubusercontent.com/16024985/131574907-bf3d318e-fa61-4201-95ea-020db86875a3.mov

Source above footer on Array page.
https://user-images.githubusercontent.com/16024985/131574943-d3a06add-7ab9-4c24-be15-091e5b51aa59.mov

Defines on Module: YARD::Handlers::Ruby page.
https://user-images.githubusercontent.com/16024985/131583803-f222164c-f1f5-452e-94b9-00f6114f798d.mov

Completed Tasks

[x] I have read the Contributing Guide.
[x] The pull request is complete (implemented / written).
[x] Git commits have been cleaned up (squash WIP / revert commits).
[x] I wrote tests and ran bundle exec rake locally (if code is attached to PR).

@lsegal This PR is ready for review.

:shipit:

Update: Added jQuery Migrate to not break downstream consumers with custom templates who may use jQuery deprecated APIs.
It's depending on prior feedback in:

Tweet: https://twitter.com/lsegal/status/1310315871051501568
PR comment: https://github.com/lsegal/yard/pull/1358#issuecomment-716072243

I'll close this PR after rebase once https://github.com/lsegal/yard/pull/1399 is merged.
This way, we'll have PR to refer to if jQuery upgrade is prioritized in future.

I'll close this PR after rebase once #1399 is merged.
This way, we'll have PR to refer to if jQuery upgrade is prioritized in future.

I'm not sure I understand this.
The intention is to backport toggle(), not remove it. #1399 is also not mergeable as is since it too is a breaking change.
The only way any of this can be merged is if the underlying jquery library is API compatible with the previous version distributed by YARD.
Custom templates (packaged as separate gems) depend on specific functions provided by YARD's templating system in the browser environment. Any changes to those functions would be equivalent to changes in Ruby methods. Replacing YARD's own internal API calls is secondary to this requirement.
TL;DR: toggle() must continue to be available to YARD's JavaScript templating system. Whether that's a custom implementation or a vendored jQuery backport doesn't matter, but the function has to exist.


Implements most _char procs and findlastextEx()

Closes #353
Closes #347
Closes #345
Closes #344
Closes #288
Closes #273
Closes #268
Adds _char() procs for every already-implemented text proc, and implements findlasttextEx()
The unimplemented text procs are splicetext(), spantext(), and nonspantext(). Issues exist for all 3.

When this PR is merged I'll update the Breaking Changes wiki page to point out that all procs work in chars instead of bytes.


Asset Library URL is malformed

The download URL submitted to the Godot Asset Library is broken:
Error parsing URL: https://github.comhttps://github.com/LuisEscorza/GodotLabelFontAutoSizer/releases/download/v1.0.2_godot_4.2/GodotLabelFontAutoSizer-1.0.2_godot_4.2.zip.

i.e. the URL got pasted twice, in the middle of itself. Quick guess, are you using Linux and using middle-click paste for everything? I do, and that's a thing that happens pretty regularly to me :)

Damn, hadn't even noticed that after so long 🤦♂... no Linux though, just general clumsiness; thank you for noticing and letting me know! I already submitted an edit with the correct URL 👍


Adding page to airport

Now it is possible to get any page you need

Thank you for contributing to the project!


link cargo to its CONTRIBUTING.md

note this is just from a quick look at the code and the README - I'm not sure if this is right, so feedback very welcome.

Heh, I have literally no idea whether this will work! This is a feature from Servo highfive that we don't use. However, it looks like it should work, so let's give it a go!

assuming this change is what is running, it looks like it didn't work :(
https://github.com/rust-lang/cargo/pull/5367#issuecomment-381754627

I suspect your change has not been deployed. This is what happens on master:
>>> from highfive import newpr
>>> config = """{
...     "groups": {
...         "all": ["@alexcrichton", "@matklad"]
...     },
...     "dirs": {
...         "doc": ["doc"]
...     },
...     "contributing": "https://github.com/rust-lang/cargo/blob/master/CONTRIBUTING.md"
... }"""
>>> import json
>>> newpr.welcome_msg('foouser', json.loads(config))
u"Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @foouser (or someone else) soon.\n\nIf any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.\n\nPlease see [the contribution instructions](https://github.com/rust-lang/cargo/blob/master/CONTRIBUTING.md) for more information.\n"

I deployed just now (I tend to batch changes and deploy once per week or so), so the next PR to Cargo should see this change

confirmed! 🎉 https://github.com/rust-lang/cargo/pull/5402#issuecomment-383361959


Reanimated crashing when using animations

When using the code:
<Square
  bc="$pink10"
  animation="bouncy"
  elevation="$4"
  size={110}
  br="$9"
  hoverStyle={{
    scale: 1.2,
  }}
  pressStyle={{
    scale: 0.9,
  }}
>
  <MyComponent width="$4" height="$4" />
</Square>;

I'm getting the following error: Tried to synchronously call anonymous function from a different thread.

What platform, OS, browser, node?

Facing the same issue in Android, browser works fine.

Sorry for the late reply @natew

What platform, OS, browser, node?

OS - Mac Intel w/ iOS simulator
Browser - n/a
Node - v16

I had some issues recently with simulator as well, a bit different, but if I attach the Chrome devtool debugger it fixes it. Seems like something in Reanimated itself.
Could anyone verify if that fixes for them?

i also bumped into this issue.
when attempting to remote debug, it crashed with a different issue of "document not defined"
used a fresh install of create-tamagui-app on 1.0.1-beta.70

it's crashing again.
in createAnimations.js the inner function that is return by callback(...) must be anonymous.
typescript generates additional code which cannot be denoted as a worklet when the inner function is given a name.

also, the fix i made had onExitComplete called. it doesn't seem to be working it anymore with beta.72

@kyunghoon thanks, I did merge your PR mostly as-is and just made small adjustments to fix the exit thing in other areas, I think there's still some bug with exit but if you set exitStyle it doesn't happen. If I get a chance I'll take a look soon.
I have keepNames true now in tamagui-build, going to turn that off for next release.

Lmk if it's still going on.


Elasticsearch::Transport::Transport::Errors::BadRequest in example

After running the last template 03-expert.rb application throw an error:
Elasticsearch::Transport::Transport::Errors::BadRequest at / [400] {"error":{"root_cause":[{"type":"search_parse_exception","reason":"failed to parse search source. unknown search element [facets]","line":1,"col":239}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query_fetch","grouped":true,"failed_shards":[{"shard":0,"index":"searchapp_application_development","node":"Ba5Nr4l6TGi5DXDlDrVJeg","reason":{"type":"search_parse_exception","reason":"failed to parse search source. unknown search element [facets]","line":1,"col":239}}]},"status":400}

This is because facets have been deprecated in Elasticsearch 2.0 -- I'll fix the template shortly.

Any progress?

@mohsinali Not yet -- too much stuff going on. In general, replace facets with aggregations and fix errors along the way, the structures are almost the same.


Inference API wrapper: adding parameters documentation

I'd like to use some parameters when calling the inference API with huggingface_hub.inference_api.
e.g.: "wait_for_model": True
Can we add documentation to explain how to use it?

What specific parameters did you have in mind?
For wait_for_model in particular, it's always set to True. There was some discussion about this in #65, https://github.com/huggingface/huggingface_hub/pull/65#discussion_r644628072 in particular.
Feel free to check the code here since it's relatively simple. The only parameter that we should likely document is use_gpu but that should likely go in the Inference API documentation.

I was thinking wait_for_model and use_gpuand you answered to everything. Thanks very much !


Test items defined inside a function

(currently does not compile)
The trait impls should presumably be moved outside of the derive __scope module, now that we're re-exporting core I think it should be okay to remove that module entirely from the codegen?

LGTM, merging.
I've seen some weird incremental compilation issues get reported in rustc's issue tracker. I hope it'll get fixed one day.


Constantly disconnecting and reconnecting

I was about to put the sensor on my meter when I did a final test with it in the case (Different from the official one). Now it constantly reboots and restarts creating a loop. It ended up just looping this
ERROR Error while reading incoming messages: Error while receiving data: [Errno 104] Connection reset by peer
WARNING Disconnected from API: Error while receiving data: [Errno 104] Connection reset by peer
INFO Connecting to home-meter.local:6053 (<IP_ADDRESS>)
WARNING Couldn't connect to API (Timeout while waiting for message response!). Trying to reconnect in 1 seconds
INFO Connecting to home-meter.local:6053 (<IP_ADDRESS>)
WARNING Couldn't connect to API (Error connecting to <IP_ADDRESS>: timed out). Trying to reconnect in 1 seconds
INFO Connecting to home-meter.local:6053 (<IP_ADDRESS>)
INFO Successfully connected to home-meter.local

Re-flashing the firmware a few times fixed it.


Transport rewrite & Editor Upgrade

:tada: This PR is included in version 8.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


IGNITE-5839: Unclear exception from BinaryObjectBuilder::build call when builder is reused.

Fix BinaryObjectBuilder reusage issue.

Already in master


Add translate folder

well, I'm korean. so, I thought that I needed a translation and proceeded.
Thank you.

Wow! This is awesome, thank you for your work!


Suggestion: Improve Alcaeus Web DX by documenting eliminating/reducing Node.js dependencies?

While trying to use Alcaeus with Angular (which uses webpack for tooling under the hood) following the Alcaeus getting started instructions, I ran into a couple of issues when trying to run the application through the webpack based tooling.
Repro steps
Here is what I tried:

Download, unzip, and open our example Angular App: alcaeus-app.zip (based on the default Angular CLI template)

Install Alcaeus

npm install --save alcaeus

Import and use Alcaeus from inside a component

import { Component, OnInit } from '@angular/core';
import { Hydra } from 'alcaeus/web';

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.scss']
})
export class AppComponent implements OnInit{
  async ngOnInit(): Promise<void> {
    var hydraRsrc = await Hydra.loadResource('https://sources.wikibus.org/');
    var root = hydraRsrc.representation!.root!;
    console.log(root.toJSON());
  }
}

Try to run the application

npm start

Notice and troubleshoot problems (see below)

Problems found
Problem 1 - resolving 'stream'

Problem

./node_modules/jsonld-streaming-parser/lib/JsonLdParser.js:14:17-34 - Error: Module not found: Error: Can't resolve 'stream' in 'C:\Users\Kris.garcia\code\open\sema\alcaeus-examples\getting-started-example\node_modules\jsonld-streaming-parser\lib'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
        - install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "stream": false }

Solution

* Same solution as Problem 2 & 3

Install the node-polyfill-webpack-plugin package

npm install --save-dev node-polyfill-webpack-plugin

Configure the node-polyfill-webpack-plugin in the custom-webpack.config.ts file

import { Configuration } from 'webpack';
import NodePolyfillPlugin from 'node-polyfill-webpack-plugin';

export default {
  plugins: [
    new NodePolyfillPlugin()
   ]
} as Configuration;

Problem 2 - resolving 'url'

Problem

./node_modules/parse-link-header/index.js:4:10-24 - Error: Module not found: Error: Can't resolve 'url' in 'C:\Users\Kris.garcia\code\open\sema\alcaeus-examples\getting-started-example\node_modules\parse-link-header'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
        - install 'url'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "url": false }

Solution

* Same solution as for Problem 1 & 3

Install the node-polyfill-webpack-plugin package

npm install --save-dev node-polyfill-webpack-plugin

Configure the node-polyfill-webpack-plugin in the custom-webpack.config.ts file

import { Configuration } from 'webpack';
import NodePolyfillPlugin from 'node-polyfill-webpack-plugin';

export default {
  plugins: [
    new NodePolyfillPlugin()
   ]
} as Configuration;

Problem 3 - resolving 'util'

Problem

./node_modules/rdf-dataset-ext/fromStream.js:5:4-19 - Error: Module not found: Error: Can't resolve 'util' in 'C:\Users\Kris.garcia\code\open\sema\alcaeus-examples\getting-started-example\node_modules\rdf-dataset-ext'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "util": require.resolve("util/") }'
        - install 'util'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "util": false }

Solution

* Same solution as for Problem 1 & 2

Install the node-polyfill-webpack-plugin package

npm install --save-dev node-polyfill-webpack-plugin

Configure the node-polyfill-webpack-plugin in the custom-webpack.config.ts file

import { Configuration } from 'webpack';
import NodePolyfillPlugin from 'node-polyfill-webpack-plugin';

export default {
  plugins: [
    new NodePolyfillPlugin()
   ]
} as Configuration;

Problem 4 - finding declaration file for 'clownface'

Problem

...
Error: ../../../../../Code/open/sema/alcaeus-examples/getting-started-example/node_modules/@tpluscode/rdfine/RdfResource.d.ts:4:56 - error TS7016: Could not find a declaration file for module 'clownface'. 'C:/Users/Kris.garcia/Code/open/sema/alcaeus-examples/getting-started-example/node_modules/clownface/index.js' implicitly has an 'any' type.
  Try `npm i --save-dev @types/clownface` if it exists or add a new declaration (.d.ts) file containing `declare module 'clownface';`

4 import { MultiPointer, GraphPointer, AnyPointer } from 'clownface';
                                                         ~~~~~~~~~~~

Error: ../../../../../Code/open/sema/alcaeus-examples/getting-started-example/node_modules/@tpluscode/rdfine/factory.d.ts:2:40 - error TS7016: Could not find a declaration file for module 'clownface'. 'C:/Users/Kris.garcia/Code/open/sema/alcaeus-examples/getting-started-example/node_modules/clownface/index.js' implicitly has an 'any' type.
  Try `npm i --save-dev @types/clownface` if it exists or add a new declaration (.d.ts) file containing `declare module 'clownface';`

2 import { AnyContext, AnyPointer } from 'clownface';
...

Solution

Install the @types/clownface package

npm install --save-dev @types/clownface

Summary
While we understand that this is not in any way a bug with Alcaeus per se, we would like to see if there is anything that can be done to improve the getting started DX when working with typescript and webpack based tooling like that which Angular uses. We would like to understand whether this means adding details to the documentation or making changes to how Alcaeus itself is packaged or potentially to how certain dependencies of Alcaeus are packaged, etc.. Please let us know if we can provide anymore information or collaboration on this and thanks!

Hello @lambdakris. Thank you for sharing your issues and workarounds.
Starting with easy, I could totally add @types/clownface as a dependency to @tpluscode/rdfine.
As for the others, admittedly, I've been kind of stuck with webpack 4. It's really nice of you to share your experience. As you point out, all those issues are caused by native packages being used by alcaeus' dependencies. Some may be possible to fix at the source, but if and when is uncertain at best. For example, parse-link-header does have a PR in progress apparently https://github.com/thlorenz/parse-link-header/pull/24
Hence, I think I would propose to create a page in the documentation which would describe steps needed to work with webpack 5 as you outlined above.

Thanks @tpluscode , I was kinda thinking along the same lines. I appreciate you adding @types/clownface to the @tpluscode/rdfine and I would be happy to add our findings to the docs. I read through the PR for parse-link-header and hopefully that will get merged soon-ish.
With regards to adding to the docs, could you provide or point me to some brief directions of how to work with the docs? Can we just make additions/revisions to the docs/latest folder or is there a different workflow that you follow?

Yes, I would simply add the necessary new pages to docs/latest and an entry in _sidebar.md to have it in the main menu somewhere. That should be it. And in case you haven't noticed, yarn docs will start it locally for you.
The other dir next to latest are snapshots of some past versions but unless there are significant breaking changes I don't suppose I would add more.

Just to add to this for anyone else coming here to get this building under Webpack 5.
The patch on rdefine fixes the need for @types/clownface, but there was some fun and games with rdfjs due to versioning … ESM cutovers … or something … oh my, is it my bed time yet? :laughing: :zzz:
Anyway, the remaining bit of the puzzle for me was modifying the project's webpack.config.js file to add the following:
module.exports = {
     // ...
    resolve: {
        // modules = [path.resolve(__dirname, 'node_modules'), 'node_modules'],
        alias: {
            '@rdf-esm/to-ntriples': path.resolve(__dirname, 'node_modules/@rdfjs/to-ntriples/index.js'),
        },
    },
    fallback: {
        'rdf-dataset-ext/addAll': path.resolve(__dirname, 'node_modules/rdf-dataset-ext/addAll.js'),
        'rdf-dataset-ext/deleteMatch': path.resolve(__dirname, 'node_modules/rdf-dataset-ext/deleteMatch.js'),
        'rdf-dataset-ext/fromStream': path.resolve(__dirname, 'node_modules/rdf-dataset-ext/fromStream.js'),
    },
};

YMMV.

Hi @GwendolenLynch. I'm surprised with the hoops you had to jump. We have been using alcaeus in a vue3 app that builds with webpack 5. Other the node native stream and buffer, the config is pretty much the defaults.
I'm especially surprised you had to alias and @rdf-esm package. I forked and published the @rdf-esm package specifically as dual ESM/CommonJS package for them to work better in web environment. They are the last I would expect should be giving you trouble. 🤔
And I do not know the fallback setting. What does it do and why was that necessary?

OK, under the context of "this is how I understood it" …

The commented-out resolve.modules for some reason is required in my set-up, but it shouldn't be so it is left commented for someone that understands this better than I do to understand (part of) my thinking
The resolve.alias and resolve.fallback settings were to workaround — at least in my project — deprecated/archived v0.x / v1.x copies of rdf-esm/(.+) and their merged updated v2.x versions; rdfsj/$1

tl;dr Webpack's module resolution referenced the rdfjs v2 libs, while the files fromalcaeus use import that are referencing rdf-esm/* < v2.x
… at least that is how I understood things :woman_shrugging:


Adding theme name to the health data log

@prafulVaishnav @abose Could you guys take a quick look at this PR and see if this looks fine?

LGTM.. Merging..

Thanks @prafulVaishnav :)

@nethip @prafulVaishnav It seems like we should only send the theme name if it's in the Extension Registry, similar to what we do for extensions...  Is there time to do that for 1.4?

@peterflynn Unfortunately we are pretty tight on the schedule. We are targeting for a release today itself! (hopefully there are no blockers)
I am wondering what are the use cases in which we would want to figure out if the theme is present in the registry or not and only then log it? I am guessing percentage of people installing themes from outside extension registry is minimal. The idea was to know what are the most used themes inside Brackets irrespective of where the theme is coming from.
We could hard code to log only if the theme is light or dark, but that way we would never know about other themes used inside Brackets.
Am I missing something here?

@nethip This is a privacy protection we put in place for logging extension names.  It seems like the exact same rationale applies to themes too.  Theme names seem a little less sensitive than extension names, but I don't think we should surprise people by logging the names of themes they didn't intend to share publicly (especially if we post them on a wiki summary for the world to see).  If there's no time to apply this check for theme names, maybe we should disable logging them for now?

@nethip Also btw, before we ship 1.4 I think we need to update https://github.com/adobe/brackets/wiki/Health-Data with the new list of what's being logged.  We link to this from the UI, and we promised to update it whenever we add things to the Health Report...

@peterflynn That is a very good catch! This was what I was missing :smile: . I just spoke to @prafulVaishnav, he says it is relatively simple. Let us target this for 1.4 itself. If it is turning out to be too much of work, we will then disable logging of this for 1.4. Also thanks for pointing out the Health Data URL that need to be updated. I will add to the deployment tasks.

Sounds good!


UART write not working

Has anyone successfully gotten UART write to work?  I had no issue getting read to work but I cant seem to get the Raspberry pi to write to the serial bus.

Nevermind figures out the issue it was on the hardware side oops.... sorry


Update doc for 21.12 release (#58)

Update doc for 21.12 release

Signed-off-by: Allen Xu<EMAIL_ADDRESS>
update for 21.12 release

Signed-off-by: Allen Xu<EMAIL_ADDRESS>
update

Signed-off-by: Allen Xu<EMAIL_ADDRESS>
Update

Signed-off-by: Allen Xu<EMAIL_ADDRESS>Co-authored-by: Allen Xu<EMAIL_ADDRESS>

close

closse


Open the snackbar for a given duration

It would be great to be able to open the snackbar with a given duration as it is possible for the Snackbar component.
openSnackbar("Hello", "success", 5000)

That is a good idea! Thanks 👍
it has been done on duration branch


Add Global Delays for Each Action Type, and Add Default Setting for "Human Frames"

Related to the frames/particles issue, I did some frame counts, and my sense is that while we could fine tune a few of these frame counts, the overall problem is not really about particle timing or the ending animation cancels, but rather that people unconsciously do all these micro-waits in game, and then expect the sim to mostly just work out of the box, and bounce off somewhat hard from the sim when it doesn't.
I think that aside from the per-each action delay stuff, we should probably also add in a setting for global delays across each type of action, that kind of simulate something closer to human play, and then make that our "human default" settings because there's no way we can do an individualized setting for each character. So something like the below:
defaults swap_delay=8 burst_delay=20 skill_delay=10 charge_delay=8;

rosaria skill[delay=20];

Would set swap delay to 8, and would add the number of frames to all usages for each action in the sim. So for example each skill usage would have 10 frames of ending animation by default, and then Rosaria E would have another 20 frames (total of 30 frames of delay).
We can then just create some reasonable global delays based on a few videos and add them as a global option like so:
defaults frame_counts="human";

which could be treated as equivalent to the above defaults statement or something. That will probably catch like 90% of all use cases, and then the remaining people who need really fine grained control (mostly Hu Tao I'm guessing since her frame timing is really tight) can add in manual waits.
Related to #171 and #209.

#352 merged into main


update wallets in dashboard

📝 Changed routes:

/dashboard/wallet

(view full size)

Commit a4fc53daedce4258aeceb0cbf1440c0c80284c82 (https://thirdweb-gab180i01.thirdweb-preview.com).

@nachoiacovino thx, this is much better than what we have now so will ship it
we can improve it further


Free floating

Right now i have to define how many items to show per slide , isn't there any way to set it to auto , means show as much as you can based upon their current width.
Use case
I am trying to use it to setup a tabbed navigation like Google play store where you have floating tabs regardless of number of items inside a viewport

Found , there is an auto option


Releasing new tag uploads only to pyviz/label/dev conda channel

When tagging a new release Travis only seems to upload the package to label/dev. This build is an example: https://travis-ci.org/pyviz/pyviz/jobs/401209417
For now I've manually uploaded 1.5.2 packages to label/main and label/earthsim. @ceball

Oops, sorry, there was another typo in my recent PR to simplify the travis config:

Should be LABELS_REL and CHANS_REL, not _DEV

For now I've manually uploaded 1.5.2 packages to label/main and label/earthsim

When you say manually uploaded to x, do you mean added the label x? (There's no need to upload multiple times.)
Separately, the earthsim label won't be automated (at least, that's not the idea in my mind). During earthsim dev, we'll use the pyviz dev channel (maybe via a 'dev' developments.txt file). But users will get a deliberately pinned/known environment, and the earthsim label is part of that.

(I'm not sure how to understand the travis link you added...it's to pyviz?)

(I'm not sure how to understand the travis link you added...it's to pyviz?)

Wrong link sorry but sounds like you've figured it out anyway.


Performance is bad on Collection queries

On my dev computer, when I attempt to retrieve a fairly complex entity (20 fields and 5 relations) collection, it takes 130ms to load ~60 entities. Each entity takes 2-3 ms to instantiate and prepare.
When I comment the relations, it takes 100ms.
One of the biggest hits seems to be with $this->data($data, false); in the Entity class constructor. When I change it for $this->_data = $data; and keep relations, it takes 60ms. Without relations nor data(), I get ~30ms.
Is this the performance to expect or am I doing something wrong?
$result = $mapper->all();
foreach ($result as $entity) {
    //...
}

I honestly have not done any performance benchmarking, but now that this project is getting a good amount of users, it might be a good time to start. Thanks for opening this issue and investigating this a bit. Performance improvements help all users immediately.

 So if you perform a JOIN or get more data than the target entity normally has, it will just be loaded on the target entity, and no attempt will be made to map the data to other entities or to filter it based on only the defined fields.

I think it's by design. In spot everything should be treated as an entity. If you filter the result set you could broke the whole record/entity if you are not careful. Ofc this has upsides and downsides as well. Maybe in the future spot will support this.

This is supported in the Query object:
https://github.com/spotorm/spot2/blob/master/lib/Query.php#L201
So from the mapper, you would have to do something like this:
$result = $mapper->all()->select('field1, field2');

Remember that Spot lazy-executes query objects, so you can add more criteria even after calling all() before the query actually gets executed.

Wow, I did not know that.


feat: action skill notebook

creating skill analysis notebook for action skills

Rebased with current master, build passes. Should be ready for review again.


The type of parameter is inconsistent between the help message and the template file

OS: Win10/Mac
Build Version: 20200806.9
Repro Steps:

Open any template file in VS Code.
Hover the mouse over parameter name.
Check the help massage.

Expect:
The type of parameter is consistent between the help message and the template file.
Actual:
The type of parameter is inconsistent between the help message and the template file, it keeps showing "Type: object".

More Info:
This issue also reproduces for the parameters which created from "Insert Item..." command.

This hover info is coming from the language server, hence is talking about JSON.  And indeed the parameter definition is a JSON object.
I could add hover info to this to provide info that this is a parameter of type string, and additional info if we wanted to.  With a little work, I could probably get rid of the "Type: object" part coming from the language server.
@neilpeterson, @jodavis Is any of this worth doing?  Personally I'd put it at a pri 3.

I had never noticed this before. Looking at it now, it doesn't seem like a huge issue. If there is some related work, perhaps bundle it in. If not, my vote would be to hold off until customer +1.

Waiting for customer feedback before taking the time to fix.


Excuse me, how can I get the code for this paper?

Excuse me, how can I get the code for this paper? The link in README seems to be inaccessible.
Looking forward to getting your reply.

Hi, some version of that code and the ideas are available in upstream llvm https://github.com/llvm/llvm-project/blob/main/clang/lib/Analysis/CloneDetection.cpp

@vgvassilev  Thanks


Support Unicode

As a user, I wish NLP Primitives had the ability to handle unicode text.
Currently, Unicode text is not correctly handled by regexes in nlp_primitives.
For example, Àbc is not recognized as a title word by TitleWordCount (Abc is).

@sbadithe Is it possible to make a pytest fixture and have it be used by all the NL primitives? That way if we add more NL primitives in the future, we can make sure they support unicode.


Failing tests under win32 & py2.7.8

See, e.g. this log.
I'll be skipping all tests on this platform for now.

Issue fixed in 195f4cd493564d18c7725acb40d9f341dda5bb0a


Adding: type declaration

Changed

adding type declaration for react-swift-slider - @zulucoda.
adding typescript example - @zulucoda.

Coverage remained the same at 96.203% when pulling 93376779d58e84de133db27781406a43b150b218 on adding/type-declaration into 1f69ce29b83e9426e677b6680ab7bb97a1c438aa on master.


bug: mention of pcluster in output of our Kubestellar-prep-for-cluster

Describe the bug
output of prep-for-cluster includes pcluster reference
`
Current workspace is "root:example-imw1".
--- current directory is /Users/andan02/projects/MCC/cicd/workloads/odh-operator-edgeplacement
current ws is root:example-imw1
imw is .
current cwsi is root:example-imw1
edge.kubestellar.io apibinding exists in workspace root:example-imw1
synctarget.edge.kubestellar.io/wec6 created
location.edge.kubestellar.io/wec6 created
synctarget.edge.kubestellar.io/wec6 labeled
location.edge.kubestellar.io/wec6 labeled
Current workspace is "root:example-imw1".
Current workspace is "root:espw".
Creating service account "kubestellar-syncer-wec6-2agyzzih"
Creating cluster role "kubestellar-syncer-wec6-2agyzzih" to give service account "kubestellar-syncer-wec6-2agyzzih"

write and sync access to the synctarget "kubestellar-syncer-wec6-2agyzzih"
write access to apiresourceimports.

Creating or updating cluster role binding "kubestellar-syncer-wec6-2agyzzih" to bind service account "kubestellar-syncer-wec6-2agyzzih" to cluster role "kubestellar-syncer-wec6-2agyzzih".
Wrote physical cluster manifest to wec6-syncer.yaml for namespace "kubestellar-syncer-wec6-2agyzzih". Use
KUBECONFIG= kubectl apply -f "wec6-syncer.yaml"
to apply it. Use
KUBECONFIG= kubectl get deployment -n "kubestellar-syncer-wec6-2agyzzih" kubestellar-syncer-wec6-2agyzzih
to verify the syncer pod is running.
Current workspace is "root:example-imw1".
Current workspace is "root".`
Steps To Reproduce

run 'KUBECONFIG=~/ks.config kubectl kubestellar prep-for-cluster --imw root:example-imw1 wec6 env=wec6'
observe output

Expected Behavior
replace 'pcluster' with 'workload execution cluster'
Additional Context
No response

The offending text is "physical cluster", right?

The output of the prep-for-cluster includes the syncer instructions. In the syncer instructions the term "pcluster" is being used. More than once I think.

I don't see it here. I guess I pasted in the wrong output. But yes, physical cluster is in this output.
Probably should do a search through the code base and replace all instances of "pcluster" and "physical cluster" at this time.

here it is
`--- current directory is /Users/andan02/projects/kubestellar/core-helm-chart
current ws is root:imw1
imw is .
current cwsi is root:imw1
edge.kubestellar.io apibinding exists in workspace root:imw1
synctarget.edge.kubestellar.io/wec5-wmw labeled
location.edge.kubestellar.io/wec5-wmw labeled
Current workspace is "root:imw1".
Current workspace is "root:espw".
Creating service account "kubestellar-syncer-wec5-wmw-1tln0c28"
Creating cluster role "kubestellar-syncer-wec5-wmw-1tln0c28" to give service account "kubestellar-syncer-wec5-wmw-1tln0c28"

write and sync access to the synctarget "kubestellar-syncer-wec5-wmw-1tln0c28"
write access to apiresourceimports.

Creating or updating cluster role binding "kubestellar-syncer-wec5-wmw-1tln0c28" to bind service account "kubestellar-syncer-wec5-wmw-1tln0c28" to cluster role "kubestellar-syncer-wec5-wmw-1tln0c28".
Wrote physical cluster manifest to wec5-wmw-syncer.yaml for namespace "kubestellar-syncer-wec5-wmw-1tln0c28". Use
KUBECONFIG= kubectl apply -f "wec5-wmw-syncer.yaml"
to apply it. Use
KUBECONFIG= kubectl get deployment -n "kubestellar-syncer-wec5-wmw-1tln0c28" kubestellar-syncer-wec5-wmw-1tln0c28
to verify the syncer pod is running.
Current workspace is "root:imw1".
Current workspace is "root:imw1".`

because it was in brackets, gh hid it.  I removed the brackets - you can see the text in the 4 line from the bottom.

@namasl would you look at this?

I take it that "physical cluster" is old terminology for what is now "workload execution cluster"?

correct @namasl


Cannot scan HELM charts with all controls/frameowrks

Running helm template <mychart> | kubescape scan - fails while helm template <mychart> | kubescape scan framework nsa - works as expected

We do not support input from stdin/yaml files when scanning all frameworks.
This is because the command scan is expecting to receive a command framework/control and not args

executing kubescape scan file.yaml will fail, instead execute kubescape scan framework nsa,mitre,armobest file.yaml

@slashben Thank you.
Run helm template <mychart> | kubescape scan framework all -, this will work.


Remove observability components

Purpose

Move observability components for separate components

module-ballerina-observe ( as a standard library )
module-ballerinai-observe

Related Issues

https://github.com/ballerina-platform/ballerina-lang/issues/33195

Approach

Moving observe lib components, observability test-utils and integration tests for separate repositories. Integration tests and observability-test-utils are moven to module-ballerinai-observe

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

The changes in this PR are sent in https://github.com/ballerina-platform/ballerina-lang/pull/34507


Wisp gets despawned on weapon switch.

Issue happens during switching of weapons or sheathing and unsheathing. Temporary workaround is to use flash (T) to release the wisp every weapons switch.

Sadly I had no luck reproducing it. For me wisp stays no matter I do. Maybe there is some incompatibility with mods like "use equipment in water", "use weapons in water".  Maybe some mod affecting status effects.
Of mods like this I use only https://thunderstore.io/c/valheim/p/Azumatt/Queue_Me_Maybe/ and it works fine.

This might be a mod conflict. Anyway thanks for checking it out


Fix invalid usage by waiting on CommandBuffer fence before resetting CommandBuffer

Add fences to per-image copy resource
Save device in swapchain state
Give fence to QueueSubmit to signal
Wait on fence before resetting commandbuffer

See also https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/8655

CI gfxreconstruct build queued with queue ID 274089.

CI gfxreconstruct build queued with queue ID 274095.

CI gfxreconstruct build # 4983 running.

CI gfxreconstruct build # 4983 passed.

CI gfxreconstruct build queued with queue ID 275201.

CI gfxreconstruct build # 5013 running.

CI gfxreconstruct build # 5013 passed.

CI gfxreconstruct build queued with queue ID 284779.

CI gfxreconstruct build # 5151 running.

CI gfxreconstruct build # 5151 passed.

CI gfxreconstruct build queued with queue ID 284802.

CI gfxreconstruct build # 5152 running.

CI gfxreconstruct build queued with queue ID 284819.

CI gfxreconstruct build queued with queue ID 284834.

CI gfxreconstruct build queued with queue ID 284835.

CI gfxreconstruct build queued with queue ID 284850.

CI gfxreconstruct build # 5156 running.

CI gfxreconstruct build # 5156 passed.


hCapthca: add custom error handling and fix documentation

This pull request introduces custom error handling functionality to the hCaptcha middleware. It allows users to define a custom validation response function, providing greater flexibility for handling hCaptcha validation errors. If the custom function is set, it will be invoked with the validation result, allowing for tailored error responses.
Additionally, this PR corrects the documentation, specifying the correct order of middleware usage. The hCaptcha middleware should be placed before the handler in the route definition, ensuring proper validation of the hCaptcha token before processing requests.
Changes Made:
•	Extended the Config structure to include a ValidateFunc field for custom error handling.
•	Updated the Validate method to call the custom function if provided.
•	Fixed the documentation to clarify the order of middleware and handler in usage examples.

Summary by CodeRabbit

New Features

Introduced a custom validation function, ValidateFunc, allowing users to define their own validation logic for HCaptcha results.
Updated example usage in documentation to reflect the new validation capabilities and changed the endpoint to /api/submit.

Bug Fixes

Enhanced error handling for validation failures, providing custom error responses.

@levatax thanks for the work
can you add any more tests ?
do the other fiber middlewares or other hcaptcha golang functions already have such functions ? just want to make sure that the existing fiber/golang users are satisfied with the function names and functionality and do not expect other schemes
can you do some more research?


CredsStore fails with private repositories

Output of docker version:
Client:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   5604cbe
 Built:        Wed Apr 27 00:34:20 2016
 OS/Arch:      darwin/amd64

Server:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   8b63c77
 Built:        Tue May 10 10:39:20 2016
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.11.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 1
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 4.4.9-moby
Operating System: Alpine Linux v3.3
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 1.954 GiB
Name: moby
ID: QBXC:V2FI:A2VA:V7ZG:R5V4:Q5PW:PNNP:EDH6:2QV3:WBT7:NCTH:MUDD
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): true
 File Descriptors: 18
 Goroutines: 38
 System Time: 2016-05-23T15:31:47.048310555Z
 EventsListeners: 1
Registry: https://index.docker.io/v1/

Additional environment details (AWS, VirtualBox, physical, etc.):
Using Docker for Mac beta.
Steps to reproduce the issue:

Enable a credsStore via config.json
Log into a private registry using a full url, e.g. https://my-registry.blah
Try to push an image to the registry

Describe the results you received:
The repository credentials are not retrieved. The following error is returned:
<layer hash>: Image push failed
no basic auth credentials

Describe the results you expected:
Successful image push
Additional information you deem important (e.g. issue happens only occasionally):
When logging in, the credsStore is given the full registry URL as a ServerURL. When performing image operations (push, pull), the scheme is omitted and the credsStore can't find the matching credentials.

Does it work if you omit the protocol when logging in? i.e. docker login my-registry.blah?

Yes, actually, it does.
Another example I just tested was to add a port to the registry (my-registry.blah:443). Login succeeds, push fails.

Hm, yes, so it stores the exact URL it used when logging in
ping @dmcgowan @calavera wdyt?

I'll take a look at it (I've fixed some bugs with cred store in the past)

thanks @runcom

@slank why are you using a full URL with https in front of the registry?

This issue surfaced while using the Amazon ECR CLI. It provides a get-login command that returns expiring credentials in the form of a docker login command. The registry URL is passed in full (including the scheme). It works fine with the default store.

I tried with the official docker hub and if you prepend https you can login but of course pull fails. Let me try with a private registry

I chased it down - I believe this is expected behavior with the new external credentials store. The default store (the .docker/config.json so to speak) could be in a legacy format where registries where saved with the scheme. This is, however, legacy, and only the default store is converting registries string to strip the scheme part and do the math to give back the correct credentials. The external stores (everyone) instead don't do this conversion. This is documented at https://github.com/docker/docker/blob/master/cliconfig/credentials/file_store.go#L33
I can fix this by doing the same logic (but trickier) for the external stores though. I'm removing the bug label for now.
ping @thaJeztah @icecrime

I believe also we need to fix this since we're letting users to login using http|https prefix :(

I'll need to rework my patch which fixes this also after https://github.com/docker/docker/pull/22988

@runcom I wanted to check in to see if you have had a chance to look at this?
Users are still encountering the problem: https://forums.docker.com/t/docker-pull-from-aws-registry-fails/17808/2

@friism, I've already sent a PR #23100, I'll try to rebase and fix it this week but it needs discussion also.

#23100 merged. Closing this.


adds sideload path for sideloading on apple silicon

Pretty harmless change so you can sideload on apple silicon M1 chips - thought it'd be useful for you guys 😄

Thank you, this is not something I would have even known about if this PR didn't happen!

lol no worries! I just happened to be noodling on it from my personal mac and figured it'd be a matter of time before someone else has the same wtf moment 😄


Update roadmap.md

@bgrant0607 et al:
Linking to the "v1 issues" is effective for tracking completion status. Here is a proposal to link to the "v1 issues" (for those who want play-by-play) with a more written/prose form for the rest of capturing "v1".

Thanks much. Good enough for now.


How to redirect after info is logged in form

Its working very well for me but after the form is submitted it just shows {"result":"success","row":1}
How would i get the page to redirect to another url after the form is submitted
Sorry if the answer is very obvious, im very new to coding
Thank you for your work

#11

If you're new to coding, I also recommend creating a free Sheet Monkey account: https://sheetmonkey.io/ which allows you do a redirect without any coding at all.


Aserto.Topaz.v0.30.32

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Actual hash:   B6A73C0DDDE2BC11358FF59DD90483F6763B5EFF49A23C2109A5AA4F4042F4EE
Expected hash: 5fe5640440fca729e9f734a594dde4d2196f121071094e9ff9ad9efe6f17ce75

(Automated response - build 729.)

Close with reason: Duplicate of #140152;


Title field panel customisations introduce invisible tab stops

In https://github.com/wagtail/wagtail/blob/9aeb2e3e49bb98201029d99fa613b0da9c6f1865/client/scss/components/forms/_title.scss#L18, we hide the title field panel’s header with sr-only so the field’s label is still present for screen reader users.
Unfortunately this isn’t correct – only the heading/label should be present. Right now, this approach also leads to invisible tab stops for the anchor links and section toggle/expand button.
We need to add extra styles to this title panel customisation so all anchor links and the button are display: none, so you can tab straight from the "Content" tab to the Title field.

Fixed in #9047


AOSP Calculator

Sir please build an AOSP Calculator app with some extra features like
Tiles button, pop-up or floating Calculator.
Please sir think about it your desk clock is too good.

I can also bring the aosp calculator, but it has a bug. The bug is the following clicking on the operation history nothing happens.
I don't know how to fix this bug. If you want I can build aosp calculator but know it has this bug

I know your looking for an AOSP calculator but I use Simple Calculator on google play store. It's free no ads.
https://play.google.com/store/apps/details?id=com.sawicki.piotr.calculator.simple.simplecalculator&hl=en_US&gl=US

The best beautiful calculator, no ads, no permission is the oneplus calculator.
This https://www.apkmirror.com/apk/oneplus-ltd/oneplus-calculator/oneplus-calculator-2-0-0-210322213558-10f33ee-release/
try to see if it installs, on my phone with aosp rom it works

I throughout that every app has some bugs.
And "history" is not big issue.
You published your app and fix bugs
in near future.Totally bugs free app is not possible.work on it.👍

@Pranab009 here's the calculator https://github.com/qw123wh/Aosp-Calulator/tree/0.1
Start trying it then calmly I'll put it on android and fix something if I can.
I have released a trial apk


Devfile registry telemetry integration

Signed-off-by: Jingfu Wang<EMAIL_ADDRESS>What type of PR is this?
/kind feature
What does this PR do / why we need it:
The change is to let odo consume the latest registry library for enabling the devfile registry telemetry on client side.
Which issue(s) this PR fixes:
Related issue: https://github.com/devfile/api/issues/281
PR acceptance criteria:

[x] Unit test

[x] Integration test

[x] Documentation

[x] I have read the test guidelines

How to test changes / Special notes to the reviewer:
Run odo catalog and odo create commands then monitor the community registry telemetry to see if the data can be collected.

@GeekArthur WDYT about putting telemetryClient as a const in one place in the code and reuse it at places where you have currently defined it? IMO, it could go into pkg/odo/cli/registry/util/util.go along with what we presently have there:
const (
	RegistryUser = "default"
)

Thoughts @feloy @valaparthvi ?

Make sense, thanks for suggesting the shared file

@GeekArthur WDYT about putting telemetryClient as a const in one place in the code and reuse it at places where you have currently defined it? IMO, it could go into pkg/odo/cli/registry/util/util.go along with what we presently have there:
const (
	RegistryUser = "default"
)

Thoughts @feloy @valaparthvi ?

I agree to put the constant in a common place, but the util package is not a place I would first go to find such a constant. Can we instead have a consts.go file in the registry package (`pkg/odo/cli/registry/consts.go)?

Can we instead have a consts.go file in the registry package (pkg/odo/cli/registry/consts.go)?

+1

Can we instead have a consts.go file in the registry package (pkg/odo/cli/registry/consts.go)?

+1

pkg/odo/cli/registry/consts.go has circular dependency issue, so I create a separate consts package under ``pkg/odo/cli/registry`, please review again

ci/prow/psi-k8s-ibmc-integration-e2e fails due to the following errors:
[ssh:Fedora 32] ++ make bin
[ssh:Fedora 32] go: GOPATH entry cannot start with shell metacharacter '~': "~/go"
[ssh:Fedora 32] go: GOPATH entry cannot start with shell metacharacter '~': "~/go"
[ssh:Fedora 32] make: *** [Makefile:62: bin] Error 2
[ssh:Fedora 32] ++ cp -avrf ./odo '~/go/bin/'
[ssh:Fedora 32] cp: cannot stat './odo': No such file or directory

It seems like an test automation infrastructure issue, probably need to use absolute path instead of relative path for go

/retest

/retest

@GeekArthur Things lgtm from code perspective, but I was unable to see any data in Devfile Registry on Segment, or was I looking in the wrong place? I tested with odo create and odo catalog list components. Can you help?

@GeekArthur Things lgtm from code perspective, but I was unable to see any data in Devfile Registry on Segment, or was I looking in the wrong place? I tested with odo create and odo catalog list components. Can you help?

I thinik the telemetry data for this will show up on devfile registry side, and not on odo side. Correct me if I'm wrong @GeekArthur.

@GeekArthur Things lgtm from code perspective, but I was unable to see any data in Devfile Registry on Segment, or was I looking in the wrong place? I tested with odo create and odo catalog list components. Can you help?

I thinik the telemetry data for this will show up on devfile registry side, and not on odo side. Correct me if I'm wrong @GeekArthur.

Yes, the telemetry data is on devfile registry side as odo is the client that consumes registry library to interact with.
@valaparthvi You can check the telemetry data of devfile registry here: https://app.segment.com/redhat-devtools/sources/devfile-registry/overview

/retest

@valaparthvi You can check the telemetry data of devfile registry here: https://app.segment.com/redhat-devtools/sources/devfile-registry/overview

That is what I did before, but I did not see any data on odo create or odo catalog list components. Do you see this data on telemetry when you run these commands?

/retest

@dharmit can you confirm if you can see the data in Devfile Registry and maybe approve it ?

/approve


[Feature]: Inactivity log out

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
After a certain time frame of inactivity a user will be prompted that they will be logged out in said amount of time. If the user is still inactive, they will be logged out.
Why should this be worked on?
This should be worked on for apps that may need that extra layer of security. This is unable to be handled via JavaScript in Appsmith since there is an inability to access the window or the document in order to add event listeners for user activties such as scroll.

@arielVelir you can now configure the user session timeout on the Appsmith instance which should achieve this for you
https://docs.appsmith.com/getting-started/setup/instance-configuration#configure-instance-1

Reopening this feature request, since the Session timeout setting does not entirely solve the user's problem.
Use case:
If the end-user was inactive for a certain amount of time, a modal pops up, warning them that they will be logged out. At this juncture, it is not possible to detect this within an app and trigger an action (e.g., open modal).
EE Ticket for reference