[#5010] Add LICENSE and NOTICE files for Iceberg REST binary

What changes were proposed in this pull request?
Add LICENSE and NOTICE files for Iceberg REST binary
Why are the changes needed?
To comply with ASF policy.
Fix: #5010
Does this PR introduce any user-facing change?
N/A
How was this patch tested?
compiled locally

@justinmclean  thanks for your work,  do you mind copy the LICENCE and NOTICE files to the Iceberg REST package in
https://github.com/apache/gravitino/blob/main/build.gradle.kts#L624-L628   and https://github.com/apache/gravitino/blob/main/build.gradle.kts#L578-L582


Fix for missing plugin situation

Fixes #187
The intended behaviour is that the entries should load OK, but that
the plugin attribute contains None, so that an attempt to access
the entry as a data source fails, but other entries are unaffected.
The message you get is like
~/code/intake/intake/catalog/local.py in get(self, **user_parameters)
    235         if len(self._plugin) == 0:
    236             raise ValueError('No plugins loaded for this entry: %s'
--> 237                              % self._driver)
    238         elif isinstance(self._plugin, list):
    239             plugin = self._plugin[0]

ValueError: No plugins loaded for this entry: parquet

(although Intake has no way of knowing which conda package might contain the named driver)

Thanks for the report, @timothydmorton


CLI issue with Dotnet 8 using Mac

I'm unable to run cli commands. I have installed dotnet sdk version 8. I'm using mac m3 pro. Someone please help me.
Please check screenshot.

@iammukeshm @justSteve @pashaie @geekz-reno

FSH CLI tool is not yet functional for the new version of this project. To test this application, please fork the repository instead, for now.


job not triggered at sh.keptn.event.deployment.triggered

I have job description:
apiVersion: v2
actions:
  - name: "Run something"
    events:
      - name: "sh.keptn.event.deployment.triggered"
    tasks:
      - name: "Deploy Something"
        files:
          - deploy.sh
          - networks.yaml
        image: "bitnami/kubectl:latest"
        cmd:
          - ls -la

However, this job is not triggered at all when the service is deployed.
A log of the distributor container in the job-executor-service shows other triggers, but none for any deployment.
keptn 0.13.4 and jes 0.1.8-next.3

Hi, it seems that your job configuration isn't valid. The command given in cmd must only be the executable and all arguments must go into the args property. Your task should look like this:
    tasks:
      - name: "Greet the world"
        image: "bitnami/kubectl:latest"
        cmd:
          - ls
        args:
          - "-la"

But that should already emit a failing job, which you can check via kubectl (kubectl -n <namespace> get jobs) and should also produce some error messages similar to the one shown below:
[job-executor-service] 2022/03/29 11:26:04 Error while creating job: job job-executor-service-job-a83c4fef-9ff2-454f-9b61-83e4-1 failed. Reason: BackoffLimitExceeded, Message: Job has reached the specified backoff limit
[distributor] time="2022-03-29T11:26:04Z" level=info msg="Received CloudEvent with ID 30070846-0103-44e1-9e9f-5c55b326f8ad - Forwarding to Keptn"
[distributor] time="2022-03-29T11:26:04Z" level=info msg="Received '.finished' event with status 'errored'. Forwarding log message to log ingestion API"
[distributor] time="2022-03-29T11:26:04Z" level=info msg="Event forwarded successfully"

If that is not the case, please verify that the job-executor-service shows up correctly in the bridge (with all subscriptions you have configured) and that the job configuration was successfully added via keptn add-resource to the repository.

@RoadRunnr did you manage to resolve the problem?

Closing this for now. Please re-open it if the problem appears again.


Status Tab - Out of Date

The staleness warning should be tied to the most recent status date.
draft status is not used in calculation

As a (type of user)
I want (goal)
so that (reason/ why/ value)
Acceptance Criteria
Scenario 1:
GIVEN ... (you or your condition)
WHEN ... (what you do)
THEN ... (what you see)
Scenario 2:
xxxxxx
Validation Rules?
(If yes, list here)
Screenshot
(Link above will always be the most up-to-date version.)

when I have an approved status, there's no staleness indicator


Return only sparse dataset in cdv export

Right now the mixed data is hard to handle, because the interval changes in middle of the file

Decided in the meeting that when zooming level is more than 1 day, request only sparse data. It will fix this issue too.

QA passed


Update huawei-sun2000-dongle.yaml

Increase timeout from 10s to 15s to help with service panic caused restarts.

@rtttc I don't think the timeouts are related to the panics. Timeouts will just error. Panics are due to invalid response. The panics should already be fixed in nightly- could we test if that's ok to work with first before we start creating always higher timeouts?

I am not using nightly, jus release 0.96 and after I increased timeout from 10s to 15s = no more panics.
I do not notice any negative side effects from increased timeouts neither?

Are they still needed with 0.97?

For some reason it reduces panic evens drastically, although with 0.97 panic does not cause restart. So what to do?


feat: CRUD REST API for CSS Templates

SUMMARY
New CRUD REST API for css templates ( api/v1/css_template )

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[X] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #11114 into master will decrease coverage by 5.16%.
The diff coverage is 91.30%.

@@            Coverage Diff             @@
##           master   #11114      +/-   ##
==========================================
- Coverage   65.75%   60.58%   -5.17%
==========================================
  Files         818      391     -427
  Lines       38783    24447   -14336
  Branches     3655        0    -3655
==========================================
- Hits        25501    14811   -10690
+ Misses      13173     9636    -3537
+ Partials      109        0     -109

Flag
Coverage Δ

#cypress
?

#javascript
?

#python
60.58% <91.30%> (-0.60%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

superset/css_templates/dao.py
80.95% <80.95%> (ø)

superset/css_templates/commands/bulk_delete.py
88.46% <88.46%> (ø)

superset/css_templates/filters.py
92.85% <92.85%> (ø)

superset/css_templates/api.py
95.45% <95.45%> (ø)

superset/app.py
80.45% <100.00%> (+0.15%)
:arrow_up:

superset/css_templates/commands/exceptions.py
100.00% <100.00%> (ø)

superset/css_templates/schemas.py
100.00% <100.00%> (ø)

superset/db_engines/hive.py
0.00% <0.00%> (-85.72%)
:arrow_down:

superset/db_engine_specs/hive.py
53.90% <0.00%> (-30.08%)
:arrow_down:

superset/db_engine_specs/presto.py
69.76% <0.00%> (-12.32%)
:arrow_down:

... and 447 more

Continue to review full report at Codecov.

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


Showing/Hiding panel causes HorizontalScrollView in main content to move

I have a slide up panel and a main view which contains a HorizontalScrollView. I have the intermittent problem that seems to be caused by scrolling the horizontal view too fast (although I am not 100% sure this is the cause). When I pull the panel in collapsed mode it changes the position of the scroll view in the main content. The same happens when I hide the panel afterwards.
I initially thought I was accidentally scrolling the view while tapping the screen but after debugging the app I could see that the horizontal scroll view's onScrollChanged() event is called after the panel is shown/hidden.
I also ruled out wide content in the slide up panel to be the cause as I tried loading it with no content and the result was the same.

Can you provide a sample project where that happens? It would help with debugging.


[Tangram R&D] Reduce the size of the library

The size of Tangram is pretty large, we have Ramda with 285kb and carto with 209kb, this is unacceptable.
To improve this, I've used ES6 decomposition for not loading the complete ramda library, now his size is 61kb, but for carto it is more complex, it is not ready to make loading decomposition so we are loading a lot of unused code, to avoid a huge part I've actively removed torque-reference from the bundle, so we have 81kb less leaving carto about 129kb.

I also updated some of the dependencies

@alonsogarciapablo can you take a look please?

@donflopez what should be the acceptance procedure/criteria? thanks!

I've put them on the PR @rafatower :)

My understanding is that this issue is not deployed yet, right? just double-checking, thanks!

It is deployed! I forgot to move this card @rafatower, sorry :)


Ask about the Results

Hi! I am wondering whether you have done the experiment using CodeBERT on these data?
I am wondering whether you have a plan to release the results and also the model's checkpoint?
It would be great if you plan to do so :)
Thanks!

Hi imamnurby,
Thank you for your interest in this project.  Yes, we have done the experiment in CodeBERT.  The paper pre-print with results is at:  https://arxiv.org/abs/2205.01254
The models and datasets are available at:  https://zenodo.org/record/6388030
The models for deepAPI won't work with the deepAPI project at guxd/deepAPI because the format of the .h5 files is a bit different.  This weekend, I will make a fork of guxd/deepAPI with the necessary modifications.

This weekend, I will make a fork of guxd/deepAPI with the necessary modifications.

Thank you! I am looking forward for this! :)

The forks of deepAPI and CodeBERT are now available:
https://github.com/hapsby/deepAPIPython
https://github.com/hapsby/CodeBERT-deepAPI


External partner organizations and consultants need access to enter and view data

 Issue by glind
Saturday Sep 12, 2015 at 19:27 GMT
Originally opened as https://github.com/mercycorps/tola-activity/issues/57

We likely need to remove the SSO component of Activity and replace it with google auth and local accounts.  There are a number of sub-grants in each country that will need to allow data entry and views into specific programs.

This is partially available through the report server access as well as the new export to TA function in TT


500 Server Error

Server error I gets after passing credentials into login system of pydash.
Footprint in apache2 logs:
[wsgi:warn] [pid 28372:tid<PHONE_NUMBER>58912] mod_wsgi: Compiled for Python/2.7.8.
[wsgi:warn] [pid 28372:tid<PHONE_NUMBER>58912] mod_wsgi: Runtime using Python/2.7.9.
Error Log configured in vhosts stays empty.
Using Debian 8 wheezy.

Looks like a possible issue with your apache/mod_wsgi install, i would recommend going thru the install steps again and making sure everything was done right or reinstall mod_wsgi.

Damn, you were right, just forgot about chowning:
chown -R www-data.www-data pydash
Now everything works fine.
Damn me!
Thanks.


Option to split entity list & components

As titled, I think it might be worth to experiment with layout of the UI, in this case the entities and their relations stay in top half of the window and second half would be dedicated to the components.

I implemented that (with two panels though) with a custom version of egui

I created https://github.com/jakobhellermann/bevy_editor_pls to build a more familiar editor-like UI on top of the inspector, so I think bevy-inspector-egui itself can stay the way it is and bevy_editor_pls can be used for the split layout.


merge package template from arlac77/npm-package-template

package.json

chore(devDependencies): update<EMAIL_ADDRESS>from template

Coverage remained the same at 48.936% when pulling 2e99dcc18b63379bc140644b4f553026baf2dc2f on template-sync-1 into 233e15e504d974092da1cbf084a3794c55bb2b14 on master.

Codecov Report

Merging #144 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #144   +/-   ##
=======================================
  Coverage   48.83%   48.83%
=======================================
  Files           2        2
  Lines          43       43
=======================================
  Hits           21       21
  Misses         22       22

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 233e15e...2e99dcc. Read the comment docs.


Update some AbstractSparkApplicationDataLoader methods to be async

Related to some work in sync_backend, there is increasing usage of async when loading various parts of data to construct a Spark Application object. This PR converts a few methods to be async in order to support that.

Not that I'm aware of! The create_spark_application helper function still exists as a non-async function, and anyone else using the Data Loader classes directly would already have to be using async


feat: auto close Snackbar

This long overdue PR is related to this issue. 😅
I tackle this issue by make it optional to auto-close the snack bar when tapped the main button. Setting in the snackbarConfig is required to make it happen.
Please review and comment if there's any improvement needed. Thank you!

@akifarhan thanks !


fix(gitmoji): change raycast reserved modifier keys

Description
Changed shortcuts to avoid conflict with raycast reserved modifier keys
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Could you give this a whirl @ricoberger 🚀

Could you give this a whirl @ricoberger 🚀

lgtm


Update finagle-http to 21.11.0

Updates com.twitter:finagle-http from 21.9.0 to 21.11.0.
Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.twitter", artifactId = "finagle-http" } ]

labels: library-update, early-semver-minor, semver-spec-minor

Superseded by #685.


KCM (deployment controller) on TP cluster failed to sync up deployment with its token

What happened:
KCM (deployment controller) on TP cluster failed to sync up deployment with its token.
I0321 00:18:52.347999       1 deployment_controller.go:563] Started syncing deployment "arktos/v8uy5l-testns/saturation-deployment-0" (2021-03-21 00:18:52.347985815 +0000 UTC m=+665.382452865)
I0321 00:18:52.348391       1 deployment_util.go:260] Updating replica set "saturation-deployment-0-c47675f5" revision to 1
I0321 00:18:52.352163       1 deployment_controller.go:565] Finished syncing deployment "arktos/v8uy5l-testns/saturation-deployment-0" (4.172689ms)
I0321 00:18:52.352185       1 deployment_controller.go:485] Error syncing deployment arktos/v8uy5l-testns/saturation-deployment-0: replicasets.apps is forbidden: User "system:kube-controller-manager" cannot create resource "replicasets" in API group "apps" in the
namespace "v8uy5l-testns"

append_or_replace_prefixed_line "${known_tokens_csv}" "${KUBE_CONTROLLER_MANAGER_TOKEN}," "system:kube-controller-manager,uid:system:kube-controller-manager"
What you expected to happen:
the controller should be permitted to perform the replication sets and create pods on the deployment
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Arktos version (use kubectl version):
Cloud provider or hardware configuration:
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Network plugin and version (if this is a network-related bug):
Others:

Needs to check with tenant RBAC model

fixed in PR 1040


Refactor test_interop/test_crypto.py to use BoaConstructor

Refactored test_interop/test_crypto.py files to use BoaTestCase in place of BoaTest for unit testing.

Task linked: CU-86drpnc8j Refactor test_interop/test_crypto.py to use BoaConstructor


Global max images

POC for how we can approach the solution asynchronously.

This looks good to merge into the other branch so we can consider it in-toto.


can tippecanoe generate vector tiles for a given area?

There's no built-in global clipping currently, but I could add the feature if it would be useful. Is clipping to a bounding box good enough for what you need?

I'm thinking about updating tiles,i don't want to regenerate all the tiles,so if i can only regenerate tiles according to the bounding box of the updated features,that will help.

Oh, OK, so you want to generate all the tiles that the bounding box intersects, not just the features that are actually within the bounding box?

That's it,don't know if this is possible.

This sounds like a good application for the plugin scripts that I've been working on in https://github.com/mapbox/tippecanoe/pull/332.
I just added a sample script to filter tiles by bounding box in 263a1b9.

This is great functionality. It works well, unless you set other pre-filters that produce output in the terminal. There seems to be some collision with the use of the standard out between tippecanoe and the perl script it calls into. I get a broken pipe and segfault error.
I like that the way it's setup now as it's really extendable, but do you think this is a common enough need that it could be built in as an additional pre-filter like the others (ex drop-smallest-as-needed)? Something like --filter-by-bbox=[x_min, x_max, y_min, y_max] Curious as to how many people find this useful

Can you provide an example of a script that causes the problem? If Tippecanoe is crashing with a segmentation fault I would really like to fix that.
It would be straightforward enough to clip to a bounding box that I should probably just go ahead and add that as another command line option.

Thanks! I'll try some filters in combination with --maximum-tile-bytes=15000 and see if I can reproduce the problem.

Thanks! This is very reproducible with
tippecanoe -F --no-feature-limit --maximum-zoom=15 --no-tile-compression --maximum-tile-bytes=15000 --drop-smallest-as-needed --output-to-directory /tiles/ -C './/filters/limit-tiles-to-bbox -115.001970 43.534703 -114.147301 44.019667 $*' ne_10m_admin_0_countries.json

and is because of a typo I made in parsing the filter output (it is checking the wrong JSON field to make sure it is not NULL).

This will be fixed in https://github.com/mapbox/tippecanoe/pull/650.

Awesome, thanks for the quick turn around!

#650 will also add a --clip-bounding-box option to clip the input geometry.

Merged and tagged: https://github.com/mapbox/tippecanoe/releases/tag/1.32.1


Option to not evade ban for mutes

Currently evaders will also get hit even for just mutes, which can be a bit heavy handed.

Resolved in #552


connected brick skins dont work

I've tried to add all sorts of skins under connected skins, they dont rlly work-

any example of one of the skins you tried to use?

any example of one of the skins you tried to use?

any skin, i realised that the extension defaults to using a skin that i didn't even choose. it overrides any file i put in

does it look like this

does it look like this

yes

just refresh the extension then


garm webhook && metrics/o11y

Hello folks,
One the challenges about runners and github actions after years it's still observability.
I'd like to know if we have plans to work on o11y for garm's webhook. https://github.com/cloudbase/garm/blob/8f0d44742e3fcae1746b75899c132881b7b4ada1/apiserver/controllers/controllers.go#L98
Use case(s)

If there's a stuck workflow because of a failed runner/provider. I know we have a timeout for bootstrap
What's the P99/P90 for jobs&runners,  startup time
Get better insights about jobs. It should be possible to log/report about webhook events.
Github actions doesn't provide a retry-mechanism. How do we cope with it?

Hi @pathcl
The scope of GARM is limited to successfully spinning up runners and making them available to the workflow jobs that are triggered on GitHub. Everything we add to GARM is geared towards that scope. But I'll explain on each point:

If there's a stuck workflow because of a failed runner/provider. I know we have a timeout for bootstrap

Indeed, this is something that can be addressed simultaneously with adding metrics to providers (see bellow). If the stuck workflow is a symptom of a stuck runner/provider, then that should be addressed by metrics added to providers. Otherwise, it's outside the scope of GARM to watch workflows themselves. We only care about the workflow jobs that we record. The distinction is important. We may not record all jobs for various reasons:

There is no pool to handle it, so we don't care
GARM was down when that event was generated.
GitHub was down and webhooks were never sent out (happens more often than one might think)

Sadly, there is no efficient way to fix any of the last 2 scenarios. We have orgs which may have many repos, and we have enterprises which may have many orgs which may have many repos. Workflows only exist at the repo level, so if we attempt to ingest any workflows we missed, it means hammering the GH API for workflows on potentially thousands of repos.
The only potential workaround is if the operator of GARM knows that GARM/GitHub was down for a while and missed some jobs, they can increase min-idle-runners to match max-runners until they consume the queue on their github repos and then set min-idle-runners back to its original value.

What's the P99/P90 for jobs&runners, startup time.

This is one area where we need to improve. We have metrics for the GH API calls, but no metrics for provider calls. We don't currently see if a runner just failed to reach idle state and is just recreated over and over due to the bootstrap timeout. So yes, this needs to be addressed. Would you be willing to open an issue about this?

Get better insights about jobs. It should be possible to log/report about webhook events.

We have that. If you look at the function you highlighted above, you should see them in the body of the function.:
https://github.com/cloudbase/garm/blob/8f0d44742e3fcae1746b75899c132881b7b4ada1/apiserver/controllers/controllers.go#L112-L115
https://github.com/cloudbase/garm/blob/8f0d44742e3fcae1746b75899c132881b7b4ada1/apiserver/controllers/controllers.go#L120-L123
https://github.com/cloudbase/garm/blob/8f0d44742e3fcae1746b75899c132881b7b4ada1/apiserver/controllers/controllers.go#L125-L128
https://github.com/cloudbase/garm/blob/8f0d44742e3fcae1746b75899c132881b7b4ada1/apiserver/controllers/controllers.go#L134-L137
We can improve on this. If you have any suggestions in regards to what extra info you believe would make sense, we can find a way to add it.

Github actions doesn't provide a retry-mechanism. How do we cope with it?

That is something that we can't fix. The scope of GARM is to make a runner available to a workflow job. As long as we receive a webhook for a queued job that we can handle, we go ahead and try to create a runner. But retrying jobs is something that should be done by the repo maintainer. Any retry attempt will generate new jobs, which will get to GARM and GARM will do the right thing (hopefully).

[...]  We have metrics for the GH API calls, but no metrics for provider calls [... ]

we are able to "calculate" some kind of an error rate when it came to provider-interaction (this metric is part of the runner_ scope) - please see my comment here

slightly off topic, but somehow related to this discussion here.
I can't share the exact code here (will discuss if possible - but it's not that complicated if you read my next few words :sweat_smile: ):
We are operating garm on an enterprise level. To make this work, we are receiving every action event from github (according to the garm documentation).
With that, we get a lot of events, even those we are not responsible for. To get more insights about our users/customers and the information we already have in the event payload, we are using this information by storing it into a database.
To do custom operation with the event requests, we installed traefik in front of garm.
With that we are able to use the mirroring feature of traefik (xref) and sending the traffic to garm and also to our custom piece of code to parse the event payload and store information like org/repo, job started, job ended, job queued, job status, ...
with that we are e..g able to see how delayed github send events to our system.


Fix broken CI of pages

This PR fixes the broken CI of pages by adding the correct name of the branch and adding permission to the deploy job.

👍


fix vso break

ifdef out ChakraCore only function
use LPCWSTR

@MSLaguana Thanks for the quick review

@Penguinwizzard Thanks for the confirm!

This is merged to master in https://github.com/Microsoft/ChakraCore/commit/1f91974aaa97a5847b15787256c396ada7d255fa


[ELE-126] Display execution time in Test Runs

Is your feature request related to a problem? Please describe.
Tracking down optimisation candidates within a dbt project, quickly identifying slow tests or those that are trending upwards in execution time
Describe the solution you'd like
Display execution time stats in the Test Runs tab in the UI
Describe alternatives you've considered
Querying artifacts from the tables directly, i.e. dbt_run_results, etc, is fine for those of us who do it frequently, but it's easier to democratise the responsibility with the Elementary UI
Additional context
Alerting on long running tests/ models will be useful one day to notify those accountable for the models
Would you be willing to contribute this feature?
I'm not really a UI dev, so wouldn't be much help here, happen to contribute to other tasks though!
ELE-126

Thanks for opening this issue @gary-beautypie !
We added this task to our backlog and it will go through our product prioritization process. Usually one of our considerations when prioritizing is the demand from the community.
We'll keep you updated once we have news about this issue.

https://elementary-community.slack.com/archives/C02CTC89LAX/p1674582169679429 (Jon Simpson)

I would also like to see this feature, As a data engineer a big part of my job is optimizing runs and having model and test timing metrics easily available is a huge plus for me as I can review the reports at least once a week to see if there are any models / tests running longer than they should or being able to identify models/tests that may need optimization

https://elementary-community.slack.com/archives/C03LPJ5EYU9/p1682079171532709

Closing, since we now support last and median execution time in the Test Execution History (previously Test Runs) screen!


Collection project owner can't access location of observation

User efmer cannot access the true location of this observation, even though it is in their BorregoWildflowers.org database project and the observer trusts them with all observations in the project.

When you look into this the export file has the same problem, it doesn't show any of the obscured coordinates.

I second this problem. When I try to obtain unobscured location data for project https://www.inaturalist.org/projects/serpentine-plants-of-the-western-united-states with Pingicula macroceras in California as a test case I get a file with header only and no data. There are 172 obscured observations (Research Grade) none of which are recovered.

James
(iNat jhorthos)

Hmm my problem might be because (maybe) I am not allowed access yet. Apparently whenever I add a new taxon to the project list I get new wait period for access. (which is kind of pain in the neck - maybe that can be changed? it is already quite difficult to get folks signed on etc., doesn't seem to be much point in the wait period except perhaps when the project is first created).

It seems like the problem here is that we are only allowing project owners to access these locations when the project attribute observation_requirements_updated_at exists and the value is at least 7 days ago. In this case the value of observation_requirements_updated_at is nil. That attribute was added in this commit on 2021/01/28, and when I look at projects with user trust enabled where observation_requirements_updated_at is nil, they are all created before that commit was deployed.
My best guess for the root of this problem is when we deployed that change, we didn't retroactively set observation_requirements_updated_at to anything for projects that had already enabled user trust. It would have been set if their rules were ever changed, but if the rules were never changed the value would remain nil and owners wouldn't have been able to access private coords since a corresponding API deploy that checked that value.
If that seems right, then I'd recommend we now retroactively set observation_requirements_updated_at to at least 7 days ago for 255 affected projects, which should allow owners of those projects to access private coords of users in those projects that have opted-in.

@kueda does that seem like a plausible cause for this bug? Can you see any problem with retroactively setting observation_requirements_updated_at to ProjectUser::CURATOR_COORDINATE_ACCESS_WAIT_PERIOD.ago for these 255 projects that have trust enabled, but where observation_requirements_updated_at is null (since they haven't updated requirements since the column was added)?

...maybe. I addressed something similar in a2000abc8c67cceebcbd21638d285c91e0beee77, and according to my notes I also ran the following that should have fixed all the projects where trust was on but observation_requirements_updated_at was null:
updated = []
Project.
    where( project_type: %w(collection umbrella) ).
    joins( :stored_preferences ).
    where( "preferences.name = 'user_trust' AND value = 't'" ).
    where( "observation_requirements_updated_at IS NULL" ).
    find_each do |proj|
  next if proj.collection_search_parameters.blank?
  proj.update_column( :observation_requirements_updated_at, proj.created_at )
  proj.elastic_index!
  puts "Updated #{proj}"
  updated << proj.id
end

It's entirely possible that I wrote that down with the intent to run it and never actually ran it, but if I did run it, then there's probably still some lingering way that a project can have trust enabled but observation_requirements_updated_at be null.

It seems to me like that code never ran. There are still 230 collection and umbrella projects that query will find, and all of them created on or before 2021-01-29, when that column was added. I'm also not seeing any place the code would ever set observation_requirements_updated_at to null. If something were resetting observation_requirements_updated_at from some value to nil, I'd expect it to affect at least some newer projects as well.
Since you were planning on running this earlier, would you mind if I ran it now? I'll then confirm they all have values for that field and we can monitor if it ever gets turned back to nil

Go ahead and run it, @pleary.

I can see the observation mentioned in the first line and I can see another one.
So looks OK.
Should this resolve the export as well?

Thanks for confirming. Yes this will hopefully fix the export as well. If you have the time, it would be worth testing that now too before I close the issue.

I'll go ahead and close this access to the observation mentioned is resetored. @efmer if you try the export and find you can't access coordinates there, please feel comment here and feel free to reopen the issue. I can confirm that as of today, there are no projects that would be updated by @kueda's code above since all of them have values for observation_requirements_updated_at


Error creating Docker images: "error while creating mount source path '/host_mnt/private/etc/scancodeio'"

I tried the Docker installation following the docs on a MacBook Pro (Apple Silicon) with macOS Monterrey 12.5.1:
git clone https://github.com/nexB/scancode.io.git && cd scancode.io
make envfile
docker-compose build
docker-compose up

I encountered this error, and I'm wondering what the reason is. Did I miss a step?
Status: Downloaded newer image for nginx:latest
Creating scancodeio_db_1    ... done
Creating scancodeio_redis_1 ... done
Creating scancodeio_web_1   ... error

ERROR: for scancodeio_web_1  Cannot start service web: error while creating mount source path '/host_mnt/private/etc/scancodeio': mkdir /host_mnt/private/etc/scancodeio: operation not permitted

ERROR: for web  Cannot start service web: error while creating mount source path '/host_mnt/private/etc/scancodeio': mkdir /host_mnt/private/etc/scancodeio: operation not permitted
ERROR: Encountered errors while bringing up the project.

When I try to create the folder manually, I also get an error:
🤷 ❯ mkdir /host_mnt
mkdir: /host_mnt: Read-only file system

I could do that sudo, but I'm not sure that's the right way...

@ospaarmann could you try to restart your Docker daemon, or alternatively your whole system, and try again?

@tdruez I restarted both the system and Docker but the problem persists.

@tdruez deleting the images, restarting docker and then building again did the trick. Thanks.


【MiniLLM】About the number of training data of dolly

Hi, I'm wondering the real data num of dolly in your experiments. You mentioned that you randomly used 14k samples as training data and 500 for validation and testing. However, the data download from here only contains 12.4K samples in raw.jsonl and 500 samples in valid.jsonl. Furthermore, the scripts for data processing process_data_dolly.sh and process_data_dolly.py seem to split another 1000 samples from raw.jsonl as validation data.
Same thing also happened in SelfInst, where the real data num in valid.jsonl v.s. the reported data num is 242 v.s. 252.
So why are these numbers inconsistent with the ones in the paper and how to reproduce the reported results?

The code and data in this repo can reproduce the reported results. We filtered out the samples that are too long to fit in the context length of our model. Therefore, the number of samples in the repo are smaller than that in the paper (12.4k v.s. 15k, 242 v.s. 252). For validation samples in dolly, we indeed use 1K samples for validation in our experiments. We will fix and explain these information in our paper. Thanks for pointing it out!

Thanks very much for your quick reply! So for dolly, you use 11.4k data for training, 1k data for validation (selecting the best ckpt) and 500 data for testing (reproducing the results in paper)?

yes

yes

Thanks!


Add selenium-driven testcases that test user-facing functionality

The recent practice mode issue with the welcome dojo got me thinking that the welcome dojo actually makes for a really nice smoke test of pwn.college's user-facing functionality. This PR adds initial capabilities to test this using selenium.

Dedicating this one to @adamdoupe


[ ] Notifications API

[ ] Async events

[ ] How elements should fire async evens (e.g. new detections, new saved samples available, etc.)
[ ] How clients should consume events.
[ ] Auto broker from Python to MQTT
[ ] Auto broker from Python to WebSockets
[ ] Auto broker to Kafka

related to #50


bug: Scan QrCode doesn't work on Samsung A23

Plugin(s)

[X] Barcode Scanning
[ ] Face Detection
[ ] Face Mesh Detection
[ ] Selfie Segmentation
[ ] Translation

Version
5.4.0
Platform(s)

[X] Android
[ ] iOS
[ ] Web

Current behavior
With a Samsung A23 the scan doesn't work (Nothing append)
Expected behavior
qrcode scan work with the Samsung A23
Reproduction
https://github.com/capawesome-team/.capacitor-app
Steps to reproduce

Try to scan a QRcode with a Samsung A23

Other information
My code :
  async scanCode() {
    await BarcodeScanner.requestPermissions();

    const data = await BarcodeScanner.isGoogleBarcodeScannerModuleAvailable();

    if (data.available) {
      const code = await this.startScanner();
      this.importerService.generateDossierFromQRCode(code);
    } else {
      try {
        await BarcodeScanner.installGoogleBarcodeScannerModule();
        const code = await this.startScanner();
        this.importerService.generateDossierFromQRCode(code);
      } catch (e) {
        await this.ui.alertSimple(
          "ERROR"
        );
      }

    }
  }

    async startScanner() {
    const { barcodes } = await BarcodeScanner.scan({
      formats: [BarcodeFormat.QrCode, BarcodeFormat.Ean13]
    });
    return barcodes;
  }

  async requestPermissions(): Promise<boolean> {
    const { camera } = await BarcodeScanner.requestPermissions();
    return camera === 'granted' || camera === 'limited';
  }

Capacitor doctor
💊   Capacitor Doctor  💊
Latest Dependencies:
@capacitor/cli: 5.7.4
@capacitor/core: 5.7.4
@capacitor/android: 5.7.4
@capacitor/ios: 5.7.4
Installed Dependencies:
@capacitor/ios: not installed
@capacitor/cli: 5.6.0
@capacitor/core: 5.6.0
@capacitor/android: 5.6.0
[success] Android looking great! 👌
Before submitting

[X] I have read and followed the bug report guidelines.
[X] I have attached links to possibly related issues and discussions.
[X] I understand that incomplete issues (e.g. without reproduction) are closed.

Someone have a same problem with the same phone with another plugin : https://github.com/juliansteenbakker/mobile_scanner/issues/698

After few test the scan work if the qrcode is not center Ex :

the getMaxZoomRatio doesn't work for my devices

Thank you for creating the bug report. Unfortunately, I don't have access to this device. Feel free to submit a PR.

Thank you for creating the bug report. Unfortunately, I don't have access to this device. Feel free to submit a PR.

There another probleme i have this error for all my phone : There is no active scan session.
Impossible to change the ratio

For example GetMaxZoomRatioResult work after the qrcode has been scanned...

We are running into this issue as well, looking at other threads it might have to do with a couple of things:
1, That phone uses android new image format NV21,
2, People report setting a custom resolution to the underlying controller solves the issue
3, ml-kit repo reports having done a pr which solves this issue.
I am willing to put some work into this, but it looks like this library is just a java wrapper on top of the ml-kit (I am not familliar with it), and the methods show do not have access to setting the resolution.
Steps would be to detect what kind of platform is being used, based on that use BGR888 (ios) or Yuv420/Nv21 (android). I have no background into imageprocessing except for my courses in uni, and I dont know how they are handled on android. If someone can get me some pointers, I am okay with walking the mile.
Ionic seems to have a new plugin as well (or Outsystems). It doesn't seem to be open (but I do see all collaborators are Ionic based). I don't know if they have the same issue yet.

After few test the scan work if the qrcode is not center Ex :

Do you get the impression that this is caused by the phone using the wrong camera? In the other issue you mentioned, there is talk about 4 cameras. I am not familiar with the code of this plugin, but I can imagine that the zoom level determines which camera is used, hence it seems like the QR code is not centered. What happens if you lower or increase the zoom ratio?

is there any news about this issue?

Probably won't be fixed because the author doesn't have that device, so he cannot reproduce the error.
I just switched to the official plugin, works great, superfast, and you don't have to provide additional CSS and HTML to make it work.

I also received a report that this is happening with Samsung A23 device. I don't have access to the device. Has anyone found out anything more about this? Is "not centering" the QR code actually working that it reads it every time?


ISPN-13449 server config doc updates

https://issues.redhat.com/browse/ISPN-13449
Needs backport to 13.0.x

minor changes. Is the JSON & YAML IP filter example working for you?

I thought that they were but I did the initial testing while I was in the airport using the overlay config method. Those examples don't actually seem to be working now so I've removed them.
I agree that we need to add more JSON and YAML examples of the server configuration but I've been crafting those by hand in some places, which is unreliable. I didn't include JSON and YAML for multiple endpoints because I couldn't get them to work.
How about I create a separate Jira to update the Server Guide with JSON/YAML alongside XML? That way we won't block this PR while wrangling with the different config formats. The XML does work at least.

@oraNod sound goods.
I'm not sure if the YAML/JSON are supposed to work to change the server config or if they are only for caches.

@pruivo https://issues.redhat.com/browse/ISPN-13465 - There are JSON and YAML examples for security realms and some other server configuration. Tristan added those so I don't think it's cache configuration only. Plus for the likes of the Helm chart the configuration is in YAML. I'll sort it out but maybe it's too much for the scope of this PR.


lock provider_configure() to admin only access

prevents a rococo whale messing with us. Locks the contract so only admins can mutate/register providers. This is a stop gap solution until we're on a live chain / have proper staking setup

closing due to dropping contract


Export data drill down

Added additional information about expected behavior when exporting data--includes data hierarchies that the visual is grouped by.

@tessahurr : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@mgblythe : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@mihart : Thanks for your contribution! The author(s) have been notified to review your proposed change.

I'm new to the functionality whereby I can see another person's review inline.  I rewrote the next content that Tessa created but I may have missed what Justin added.

@mihart : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@mihart : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@mihart - is this PR ready to merge? thanks.

@mihart : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi Jak-MS,
I'd like Tessa or Justin to review my edit. Want to be sure I didn't misunderstand.  I've sent them both a separate email. Thanks.

@Jak-MS : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@mgblythe : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@mgblythe : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@mgblythe : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@mihart - I accepted Justin's changes and will merge. If you have additional edits, please open a new PR for those.


[WIP] examples: Add double proxy sandbox

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>Commit Message: examples: Add double proxy sandbox
Additional Description:
this provides a sandbox with the following setup:
envoy (front) -> flask-app -> envoy (postgres-front) -> envoy(postgres-back) -> postgres
essentially it demonstrates using Envoy in a situation where a frontend app is not on the same subnet as its db, and uses a proxy in each of the subnets to transport traffic between.
ideally, the traffic between envoy (postgres-front) -> envoy (postgres-back) should be encrypted (and perhaps authenticated) to show a situation of the traffic travelling over insecure/public networks
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]

@mattklein123 not sure how useful this is or if this is what is meant in docs etc by "double proxy"
its the pattern i was most interested in when i first looked at envoy - kinda like subnet (rather than pod/container) sidecars, that can be used as a bridge/router to upstream services
not sure if encrypting traffic in the middle proxies is possible, but it would make for a much better sandbox if it is, and would remove the need to use vpns etc in this kind of set up, esp if we could do client authentication

what is meant in docs etc by "double proxy"

Yeah this is an example of a double proxy scenario. The most common example is in POPs, something like envoy <pop> <-> envoy <origin> <-> backend
We can definitely encrypt across the hops. This is typically done using mTLS but it depends on the scenario. I think we could do this with a self-signed cert and make for a pretty interesting sandbox.
Let me know how you want to proceed on this one.
/wait

ive added mtls and all appears to work - just ironing out wrinkles with the example
i still need to add some docs
one question im now wondering is whether we could/should add compression to the mtls filling

afaict compression wont work as its http/hcm based and in this example the middle proxies arent using http

docs are rendered here https://storage.googleapis.com/envoy-pr/13748/docs/start/sandboxes/double-proxy.html

@mattklein123 if we can land the securing quick-start page first, ill update this and tie them together

Yeah I think dropping SNI from this one makes sense.
/wait

great, updating...

latest render is here
https://storage.googleapis.com/envoy-pr/075c570/docs/start/sandboxes/double-proxy.html


HADOOP-16005: Add XAttr support to WASB and ABFS

As discussed in HADOOP-16005, this pull request implements getXAttr and setXAttr on hadoop-azure's WASB and ABFS file-systems.
The changes were tested against the following Azure storage account configurations:

WASB: StorageV2, RA-GRS replication in East US (primary) West US (secondary). WASB test session screenshot. All tests pass and the ABFS tests are skipped as expected.

ABFS: StorageV2 with Data Lake Storage Gen2 preview enabled, RA-GRS replication in East US (primary) West US (secondary). ABFS test session screenshot. All ABFS tests pass but the WASB tests fail since the storage account hasn't implemented the blob endpoints yet.

The test-patch script passed: test-patch output.

Apologies for the delay on this pull request. I resolved the merge conflicts and pushed an update.
All the unit testes pass, but when running the integration tests with my azure-auth-keys.xml file against StorageV2 accounts, I'm getting some failures. However, I'm also getting these failures when running against trunk so I doubt that the errors are related to this pull request.
I ran the tests by executing sudo mvn clean install -Pdist -Dtar -Ptest-patch -pl ./hadoop-tools/hadoop-azure | tee test.log.txt in the development environment Docker container running on WSL: see test.log.txt and a sample detailed test failure.
As a new contributor to this project, I'd appreciate any guidance on how to resolve the errors and properly integration test my change. Any ideas @DadanielZ? Thanks in advance for your help!

@c-w the configuration for ABFS is not correct, the account name and related suffix should be "dfs.core.windows.net", not "blob.core.windows.net".

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
3m 25s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
23m 59s
trunk passed

+1 :green_heart:
compile
0m 30s
trunk passed

+1 :green_heart:
checkstyle
0m 23s
trunk passed

+1 :green_heart:
mvnsite
0m 33s
trunk passed

+1 :green_heart:
shadedclient
15m 47s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 36s
trunk passed

+0 :ok:
spotbugs
0m 57s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
0m 55s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 30s
the patch passed

+1 :green_heart:
compile
0m 22s
the patch passed

+1 :green_heart:
javac
0m 22s
the patch passed

+1 :green_heart:
checkstyle
0m 21s
the patch passed

+1 :green_heart:
mvnsite
0m 27s
the patch passed

+1 :green_heart:
whitespace
0m  1s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
15m  7s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 23s
the patch passed

+1 :green_heart:
findbugs
0m 53s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 18s
hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 29s
The patch does not generate ASF License warnings.

67m 37s

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-452/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/452

JIRA Issue
HADOOP-16005

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 9e270c2aaaf6 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / ef950b0

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-452/2/testReport/

Max. process+thread count
305 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-452/2/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

Thanks for the help, @DadanielZ. I was able to run the tests by changing the ABFS endpoint to dfs as opposed to blob as you suggested.
All test now pass for the branch except for one test which also fails on trunk: comparison, branch log, trunk log. Let me know if this is sufficient for the purposes of this pull request or if there's further testing/verification you'd like me to perform.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 15s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
23m 14s
trunk passed

+1 :green_heart:
compile
0m 27s
trunk passed

+1 :green_heart:
checkstyle
0m 24s
trunk passed

+1 :green_heart:
mvnsite
0m 31s
trunk passed

+1 :green_heart:
shadedclient
14m 31s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 22s
trunk passed

+0 :ok:
spotbugs
0m 54s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
0m 52s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 26s
the patch passed

+1 :green_heart:
compile
0m 22s
the patch passed

+1 :green_heart:
javac
0m 22s
the patch passed

+1 :green_heart:
checkstyle
0m 18s
the patch passed

+1 :green_heart:
mvnsite
0m 26s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
14m 51s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 20s
the patch passed

+1 :green_heart:
findbugs
0m 54s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 17s
hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 28s
The patch does not generate ASF License warnings.

62m 15s

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-452/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/452

JIRA Issue
HADOOP-16005

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 299679ebd1f0 4.15.0-70-generic #79-Ubuntu SMP Tue Nov 12 10:36:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 6b2d6d4

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-452/3/testReport/

Max. process+thread count
295 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-452/3/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 47s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
21m 47s
trunk passed

+1 :green_heart:
compile
0m 26s
trunk passed

+1 :green_heart:
checkstyle
0m 22s
trunk passed

+1 :green_heart:
mvnsite
0m 30s
trunk passed

+1 :green_heart:
shadedclient
14m 49s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 21s
trunk passed

+0 :ok:
spotbugs
0m 53s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
0m 50s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 28s
the patch passed

+1 :green_heart:
compile
0m 24s
the patch passed

+1 :green_heart:
javac
0m 24s
the patch passed

+1 :green_heart:
checkstyle
0m 16s
the patch passed

+1 :green_heart:
mvnsite
0m 25s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
15m  0s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 20s
the patch passed

+1 :green_heart:
findbugs
0m 53s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 17s
hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 29s
The patch does not generate ASF License warnings.

61m 53s

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-452/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/452

JIRA Issue
HADOOP-16005

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux e1f92a9e389d 4.15.0-70-generic #79-Ubuntu SMP Tue Nov 12 10:36:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 6b2d6d4

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-452/4/testReport/

Max. process+thread count
306 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-452/4/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
18m  0s
trunk passed

+1 :green_heart:
compile
0m 31s
trunk passed

+1 :green_heart:
checkstyle
0m 26s
trunk passed

+1 :green_heart:
mvnsite
0m 34s
trunk passed

+1 :green_heart:
shadedclient
13m 45s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 26s
trunk passed

+0 :ok:
spotbugs
0m 51s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
0m 48s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 27s
the patch passed

+1 :green_heart:
compile
0m 23s
the patch passed

+1 :green_heart:
javac
0m 23s
the patch passed

+1 :green_heart:
checkstyle
0m 19s
the patch passed

+1 :green_heart:
mvnsite
0m 26s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
13m 33s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 23s
the patch passed

+1 :green_heart:
findbugs
0m 54s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 21s
hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 31s
The patch does not generate ASF License warnings.

54m 44s

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-452/7/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/452

JIRA Issue
HADOOP-16005

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 79ceaaf65ff9 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 6b2d6d4

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-452/7/testReport/

Max. process+thread count
412 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-452/7/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
23m 43s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  1s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
23m 12s
trunk passed

+1 :green_heart:
compile
0m 27s
trunk passed

+1 :green_heart:
checkstyle
0m 23s
trunk passed

+1 :green_heart:
mvnsite
0m 30s
trunk passed

+1 :green_heart:
shadedclient
14m 32s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 22s
trunk passed

+0 :ok:
spotbugs
0m 53s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
0m 51s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 31s
the patch passed

+1 :green_heart:
compile
0m 28s
the patch passed

+1 :green_heart:
javac
0m 28s
the patch passed

+1 :green_heart:
checkstyle
0m 18s
the patch passed

+1 :green_heart:
mvnsite
0m 27s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
14m 37s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 20s
the patch passed

+1 :green_heart:
findbugs
0m 54s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 21s
hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 31s
The patch does not generate ASF License warnings.

84m 50s

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-452/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/452

JIRA Issue
HADOOP-16005

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 24241755d1fe 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 6b2d6d4

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-452/5/testReport/

Max. process+thread count
295 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-452/5/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
24m 12s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
22m  8s
trunk passed

+1 :green_heart:
compile
0m 31s
trunk passed

+1 :green_heart:
checkstyle
0m 22s
trunk passed

+1 :green_heart:
mvnsite
0m 31s
trunk passed

+1 :green_heart:
shadedclient
14m 28s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 26s
trunk passed

+0 :ok:
spotbugs
0m 56s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
0m 55s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 29s
the patch passed

+1 :green_heart:
compile
0m 25s
the patch passed

+1 :green_heart:
javac
0m 25s
the patch passed

+1 :green_heart:
checkstyle
0m 17s
the patch passed

+1 :green_heart:
mvnsite
0m 26s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
15m 10s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 20s
the patch passed

+1 :green_heart:
findbugs
0m 58s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 17s
hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 27s
The patch does not generate ASF License warnings.

84m 44s

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-452/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/452

JIRA Issue
HADOOP-16005

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux e4cb54c0831e 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 6b2d6d4

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-452/6/testReport/

Max. process+thread count
309 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-452/6/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
29m 55s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
20m 31s
trunk passed

+1 :green_heart:
compile
0m 28s
trunk passed

+1 :green_heart:
checkstyle
0m 21s
trunk passed

+1 :green_heart:
mvnsite
0m 31s
trunk passed

+1 :green_heart:
shadedclient
14m 26s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 22s
trunk passed

+0 :ok:
spotbugs
0m 48s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
0m 47s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 26s
the patch passed

+1 :green_heart:
compile
0m 22s
the patch passed

+1 :green_heart:
javac
0m 22s
the patch passed

+1 :green_heart:
checkstyle
0m 17s
the patch passed

+1 :green_heart:
mvnsite
0m 25s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
14m 59s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 20s
the patch passed

+1 :green_heart:
findbugs
0m 53s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 17s
hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 27s
The patch does not generate ASF License warnings.

88m  9s

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-452/8/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/452

JIRA Issue
HADOOP-16005

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux cc953942734b 4.15.0-70-generic #79-Ubuntu SMP Tue Nov 12 10:36:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 6b2d6d4

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-452/8/testReport/

Max. process+thread count
305 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-452/8/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
docker
0m 10s
Docker failed to build yetus/hadoop:104ccca9169.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hadoop/pull/452

JIRA Issue
HADOOP-16005

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-452/9/console

versions
git=2.17.1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
docker
0m  9s
Docker failed to build yetus/hadoop:104ccca9169.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hadoop/pull/452

JIRA Issue
HADOOP-16005

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-452/10/console

versions
git=2.17.1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

@DadanielZ Any chance you could take another look at this and provide some guidance on @virajith's question regarding encodings https://github.com/apache/hadoop/pull/452#discussion_r352263050? Would love to get this wrapped up and merged soon.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 13s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
20m 59s
trunk passed

+1 :green_heart:
compile
0m 29s
trunk passed

+1 :green_heart:
checkstyle
0m 25s
trunk passed

+1 :green_heart:
mvnsite
0m 31s
trunk passed

+1 :green_heart:
shadedclient
14m 28s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 24s
trunk passed

+0 :ok:
spotbugs
0m 50s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
0m 48s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 26s
the patch passed

+1 :green_heart:
compile
0m 23s
the patch passed

+1 :green_heart:
javac
0m 23s
the patch passed

+1 :green_heart:
checkstyle
0m 17s
the patch passed

+1 :green_heart:
mvnsite
0m 27s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
14m 59s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 20s
the patch passed

+1 :green_heart:
findbugs
0m 52s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 17s
hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 28s
The patch does not generate ASF License warnings.

60m 14s

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-452/11/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/452

JIRA Issue
HADOOP-16005

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 72a3738d9792 4.15.0-70-generic #79-Ubuntu SMP Tue Nov 12 10:36:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / a40dc9e

Default Java
1.8.0_232

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-452/11/testReport/

Max. process+thread count
305 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-452/11/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


Upgrade to java-build-tools 2.5?

It's been out 6 months. I could create a PR if the maintainers would like
https://github.com/cloudbees/java-build-tools-dockerfile/blob/2.5.0/Dockerfile

exists cloudbees/jnlp-slave-with-java-build-tools:2.5.1


ApiManagement API deployment: non required query parameters are wrongly added to the URL path

Bicep version
Bicep CLI version 0.26.54 (5e20b29b58)
Describe the bug
I am using this code to deploy an API to APIM. I am using loadJsonContent to load in an OpenAPI spec (v3.0.1).
param openApiSpecContents = loadJsonContent('./open-api.json')

resource api 'Microsoft.ApiManagement/service/apis@2022-04-01-preview' = {
  name: name
  parent: service
  properties: {
    // other properties
    format: 'openapi+json'
    value: string(openApiSpecContents)
    translateRequiredQueryParameters: 'query'
  }
}

The API has an endpoint with 2 non-required parameters (iterationId and gln).
"parameters": [
    {
        "name": "iterationId",
        "in": "query",
        "schema": {
            "type": "string"
        }
    },
    {
        "name": "gln",
        "in": "query",
        "schema": {
            "type": "string"
        }
    }
]

I then deploy the API to APIM.
Expected
The query parameters are set as being not required and as a result, they do not show up in the URL since they are not required.
Actual
The query parameters show up as being not required which is correct

But, they do show up in the URL path, and when I call the API without the query parameters, I get a 404, so the issue is that the parameters should not be added to the URL path since they are not required, but they are falsely added.

To Reproduce
See steps above.

This is a Microsoft.APIManagement issue, please open a support ticket with that team and I will try to route it correctly on our end

What is the correct place to report this then? I can't really find it.


Refactor join session

Description
The main purpose of this pull request is to enhance the process of joining a live session.
Test Plan
N/A
Motivation and Context
The general functionality of the app needs to be improved to be leaner and more performant overall. By refactoring not only the JoinSession async thunk, but as well as the containers where the thunk is used, the process of joining a live session can be improved upon.
How Has This Been Tested?
I've manually tested the performance of the app by going through the containers in question and seeing how the new implementation is performing.
Types of Changes

Documentation
Bug fix
[x] New feature
Breaking change

Checklist

[x] My code follows the code style of this project

 Join session thunk


adding progress bar / ETA for load_dataset

Please consider:
Downloading and preparing dataset oscar/unshuffled_deduplicated_en (download: 462.40 GiB, generated: 1.18 TiB, post-processed: Unknown size, total: 1.63 TiB) to cache/oscar/unshuffled_deduplicated_en/1.0.0/84838bd49d2295f62008383b05620571535451d84545037bb94d6f3501651df2...
HF google storage unreachable. Downloading and preparing it from source

and no indication whatsoever of whether things work well or when it'll be done. It's important to have an estimated completion time for when doing slurm jobs since some instances have a cap on run-time.
I think for this particular job it sat for 30min in total silence and then after 30min it started generating:
897850 examples [07:24, 10286.71 examples/s]

which is already great!
Request:

ETA - knowing how many hours to allocate for a slurm job
progress bar - helps to know things are working and aren't stuck and where we are at.

Thank you!
@lhoestq

Is this done now? I see progress bars when using load_dataset.

There are progress bars when downloading data and when preparing them as Arrow files.
The "total silence" part mentioned in OP refer to checksums verifications which have some changes for the next release:

they're disabled by default (other less costly verifications are still done like checking the generated dataset size)
they're using a tqdm bar as well


Can't change pseudo for member

Describe the bug
Following the wiki, everything works except account linking.
Server is running Forge 1.19.4 on Ubuntu 22.04 via Pterodactyl (Java 17). Bot was invited normally using the /mc2discord invite command.
Console log:
[12:11:19] [boundedElastic-9/WARN] [mc2discord/]: Can't change pseudo for member Hasumin (IG : hsmn)
[ERROR] (boundedElastic-9) Operator called default onErrorDropped - ml.denisd3d.mc2discord.repack.reactor.core.Exceptions$ErrorCallbackNotImplemented: ml.denisd3d.mc2discord.repack.discord4j.rest.http.client.ClientException: PUT /guilds/1087323928256577628/members/489578008030740500/roles/1103901713091539036 returned 403 Forbidden with response {code=50001, message=Missing Access}
ml.denisd3d.mc2discord.repack.reactor.core.Exceptions$ErrorCallbackNotImplemented: ml.denisd3d.mc2discord.repack.discord4j.rest.http.client.ClientException: PUT /guilds/1087323928256577628/members/489578008030740500/roles/1103901713091539036 returned 403 Forbidden with response {code=50001, message=Missing Access}
Caused by: ml.denisd3d.mc2discord.repack.discord4j.rest.http.client.ClientException: PUT /guilds/1087323928256577628/members/489578008030740500/roles/1103901713091539036 returned 403 Forbidden with response {code=50001, message=Missing Access}
        at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.discord4j.rest.http.client.ClientResponse.clientException(ClientResponse.java:171)
        Suppressed: The stacktrace has been enhanced by Reactor, refer to additional information below:
Error has been observed at the following site(s):
        *__checkpoint ⇢ Request to PUT /guilds/1087323928256577628/members/489578008030740500/roles/1103901713091539036 [RequestStream]
        *__checkpoint ⇢ Request to PUT /guilds/1087323928256577628/members/489578008030740500/roles/1103901713091539036 [DefaultRouter]
Original Stack Trace:
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.discord4j.rest.http.client.ClientResponse.clientException(ClientResponse.java:171)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.discord4j.rest.http.client.ClientResponse.lambda$createException$13(ClientResponse.java:149)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:125)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1839)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.core.publisher.MonoFlatMap$FlatMapInner.onNext(MonoFlatMap.java:249)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:122)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.core.publisher.FluxHandle$HandleSubscriber.onNext(FluxHandle.java:126)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.core.publisher.FluxPeekFuseable$PeekConditionalSubscriber.onNext(FluxPeekFuseable.java:854)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.core.publisher.FluxPeekFuseable$PeekConditionalSubscriber.onNext(FluxPeekFuseable.java:854)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.core.publisher.FluxPeekFuseable$PeekConditionalSubscriber.onNext(FluxPeekFuseable.java:854)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.core.publisher.FluxMap$MapConditionalSubscriber.onNext(FluxMap.java:224)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.core.publisher.FluxDoFinally$DoFinallySubscriber.onNext(FluxDoFinally.java:113)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.onNext(FluxHandleFuseable.java:191)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.core.publisher.FluxContextWrite$ContextWriteSubscriber.onNext(FluxContextWrite.java:107)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1839)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.core.publisher.MonoCollectList$MonoCollectListSubscriber.onComplete(MonoCollectList.java:129)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.core.publisher.FluxPeek$PeekSubscriber.onComplete(FluxPeek.java:260)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.core.publisher.FluxMap$MapSubscriber.onComplete(FluxMap.java:144)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.netty.channel.FluxReceive.onInboundComplete(FluxReceive.java:415)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.netty.channel.ChannelOperations.onInboundComplete(ChannelOperations.java:424)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.netty.channel.ChannelOperations.terminate(ChannelOperations.java:478)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.netty.http.client.HttpClientOperations.onInboundNext(HttpClientOperations.java:712)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.reactor.netty.channel.ChannelOperationsHandler.channelRead(ChannelOperationsHandler.java:113)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:436)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:324)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:296)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:251)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1372)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.handler.ssl.SslHandler.decodeJdkCompatible(SslHandler.java:1235)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.handler.ssl.SslHandler.decode(SslHandler.java:1284)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:507)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:446)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:276)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:719)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:655)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:581)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
                at TRANSFORMER/mc2discord@3.3.1-pre/ml.denisd3d.mc2discord.repack.io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
                at java.base/java.lang.Thread.run(Thread.java:833)

Your upload command isn't working (as https://m2d.denisd3d.ml is down and upon checking it doesn't seem like I'm the only one that can't access it, it's actually down), so I'm pasting the config here without sensitive data:
# Change the language of the mod. Delete the rest of this file to translate the config. Big thanks to the translators : Morty#0273 (ru_ru), PixelVoxel#4327 (ko_kr)
# Supported language : en_us, fr_fr, ru_ru, ko_kr
lang = "en_us"

# Minecraft2Discord configuration
#  - Curseforge: https://www.curseforge.com/minecraft/mc-mods/minecraft2discord
#  - Modrinth: https://modrinth.com/mod/minecraft2discord
#  - Discord: https://discord.gg/rzzd76c
#  - Github: https://github.com/DenisD3D/Minecraft2Discord
#  - Wiki: https://github.com/DenisD3D/Minecraft2Discord/wiki
#
# Read the wiki for a quick start guide or for more advanced customization
# You can also join the discord to get some help
#
# You can use discord markdown
# Many variables are available to customize the behavior. Check them on the wiki: https://github.com/DenisD3D/Minecraft2Discord/wiki/Variables
[General]
	# Token for the bot. This is a secret string that can be generated on discord website. More info here: https://github.com/DenisD3D/Minecraft2Discord/wiki/Discord-token
	token = --redacted--

# Channels configuration. You may duplicate this block. Each one correspond to one channel
# id is the discord id of the channel. See: https://github.com/DenisD3D/Minecraft2Discord/wiki/Discord-ids
# subscriptions is an array of what type of message you want in this channel. Currently supported are:
#   - chat (player chat message in both direction)
#   - info (join, leave, start, stop, death, advancement)
#   - command (listen to command, see Commands section)
#   - log (all the log of the server)
#   - discord_announcement (for relaying announcement channel to Discord)
# mode define how to send messages (WEBHOOK, PLAIN_TEXT or EMBED)
[Channels]

	[[Channels.Channel]]
		id = --redacted--
		subscriptions = ["info", "chat", "command"]
		mode = "WEBHOOK"

# Customize here the message that are sent on discord. To disable one, set an empty value ("")
# For the list of available variables see: https://github.com/DenisD3D/Minecraft2Discord/wiki/Variables
[Messages]
	# Global variables only
	start = "The server has started"
	# Global variables only
	stop = "The server has stopped"
	# Global variables and Player variables
	join = "${player_display_name} joined the game"
	# Global variables and Player variables
	leave = "${player_display_name} left the game"
	# Global variables, Player variables and Death variables
	death = "${death_message}"
	# Global variables, Player variables and Advancement variables
	advancement = "${player_display_name} has made the advancement ${advancement_title}. ${advancement_description}."

[Commands]
	# Prefix used before each command. Minecraft default one is '/' (eg : /help)
	prefix = "/"
	# If true, text returned by commands will be in a Discord code block
	use_codeblocks = true
	# Response when the user isn't allowed to use the command
	error = "Sorry, you're not allowed to use that command!"

	# Commands permissions configuration. You may duplicate the block. Each block correspond to one rule
	# id is an user id or a role id. The rule (current block) will apply for this user or users with this role
	# commands is a list of the commands that are allowed in addition of the permission level
	# permission_level allow all the commands with this permission or under level. -1 mean only the commands in the list commands above and 0 mean all non op commands
	# comment not used by the mod. You can use it to remember what the rule is for
	# see https://minecraft.gamepedia.com/Server.properties#op-permission-level
	[[Commands.Command]]
		id = 0
		commands = ["help"]
		permission_level = -1
		comment = ""

[Status]

	[Status.Presence]
		# Message to display under the bot in the member list on Discord
		message = " Minecraft (${online_players} online)"
		#The type of presence (PLAYING, STREAMING, LISTENING, WATCHING, COMPETING)
		type = "PLAYING"
		# Update frequency of the presence message (in seconds). A too low number might result in limitation from Discord
		update = 60
		# Only if type is STREAMING, ignored for others. Must be a valid youtube or twitch link.
		link = ""

	# Status channels configuration. You may duplicate the block. Each block correspond to one channel
	# id is the discord id of the channel. See : https://github.com/DenisD3D/Minecraft2Discord/wiki/Discord-ids
	# update_period is the update frequency of the channel (in seconds). A too low number might result in limitation form Discord (max 2 update per 10 minutes as of writing)
	# name_message is the message to set as a name of the channel. You can use Global variables. If the channel is a text channel, whitespace will be replaced by '-'
	# topic_message is the message to set as the description of the channel. You can use Global variables
	[Status.Channels]

		[[Status.Channels.Channel]]
			id = 0
			update_period = 610
			name_message = "${online_players} / ${max_players}"
			topic_message = "${online_players} / ${max_players}"

[Features]
	# Enable account linking features (use /mc2discord restart to generate the associated config). Require SERVER MEMBERS INTENT to be enabled for all features to work
	account_linking = true

[Account]
	# The id of the guild your players are on
	guild_id = --redacted--
	# If true, the member on discord will be renamed to the format in discord_pseudo_format
	rename_discord_member = true
	# The format to rename the discord member. Available variables : Player & Member
	discord_pseudo_format = "${member_name} (IG: ${player_name})"
	# The link command (you need to leave & rejoin for the command to appear in suggestion, old command will disappear after a server restart)
	link_command = "discord link"
	# The unlink command (you need to leave & rejoin for the command to appear in suggestion, old command will disappear after a server restart)
	unlink_command = "discord unlink"
	# If true, non linked players will be kick of the server at login with a link code else players will be able to link using the command
	force_link = false

	# Customize here the message that are sent
	[Account.Messages]
		# Message to give the code to the player. ${code} will be replaced by the code
		link_get_code = "To link your account please send $c!code ${code}$r to ${bot_name}#${bot_discriminator} in a private message on Discord"
		# The message sent when link is complete
		link_successful = "You have successfully linked your account"
		# The message sent when the code is wrong
		link_invalid_code = "This code is invalid"
		# The message sent when the account is already linked
		link_error_already = "Your account is already linked"
		# The message sent when the account unlinking is successful
		unlink_successful = "Your account is now unlinked"
		# The message sent when the account unlink is unsuccessful
		unlink_error = "Can't unlink your account"
		# The message sent when the account is missing some roles
		missing_roles = "You are missing some permissions or roles on Discord needed for Account Linking"

	# Set here some requirements to link accounts: required_roles_id is an array of role id required to make the link & roles_id_to_give is an array of role id that will be given on the link. You may create multiple block
	[[Account.Policy]]
		required_roles_id = [--redacted--]
		roles_id_to_give = [--redacted--]

# Style configuration
[Style]
	# Override the bot name in webhook mode. You may use global variable here
	bot_name = ""
	# Override the bot avatar in webhook mode. Must be a valid an url. You may use global variable here
	bot_avatar = ""
	# Url to fetch player avatar from. Must be a valid url and not empty. You may use Global variables and Player variables here
	avatar_api = "https://mc-heads.net/head/${player_uuid}/right"
	# Format for the messages sent in the minecraft chat. You may use Global variables, Member variables and Message variable here. You may change the color with '${color_start_COLOR} CONTENT ${color_end}' where COLOR is a hex color or 'top_role' for discord highest role color. ${reply} will be replaced with reply_format if the message has a referenced message.
	minecraft_chat_format = "${color_start_#ffff00}<Discord - ${color_end}${color_start_top_role}${member_nickname}${color_end}${color_start_#ffff00}>${color_end} ${message}"
	# Format for chat messages sent in discord when webhook mode is turned to false. You may use Global variables, Player variables and Message variable here
	discord_chat_format = "**${player_display_name}**: ${message}"
	# Replace ${reply} in minecraft_chat_format if the message has a referenced message. You may use Global variables and Member (author of the referenced message) variables here.
	reply_format = "Replying to ${member_nickname}: "
	# If true, the server avatar will be shown in the embed for info messages
	embed_show_server_avatar = false

	[Style.embed_color]
		# Color for the embeds. A int color or one of https://github.com/DenisD3D/Mc2Discord/blob/main/mc2discord-core/src/main/java/ml/denisd3d/mc2discord/core/M2DUtils.java#L102-L134
		info = "SUMMER_SKY"
		chat = "MEDIUM_SEA_GREEN"
		command = "MEDIUM_SEA_GREEN"
		log = "SUMMER_SKY"

# The rest of the settings
[Misc]
	# Define if other bots messages must be sent in the minecraft chat
	relay_bot_messages = false
	# Define if /say & /me command must be relayed on Discord
	relay_say_me_tellraw_command = true
	# List of allowed mention type. Supported value : "EVERYONE_AND_HERE", "ROLE", "USER"
	# Eg : ["ROLE", "USER"] to allow all mention except @everyone & @here
	allowed_mention = []
	# Message for the /discord command
	discord_text = "Invitation link not set"
	# Link for the /discord command
	discord_link = "https://discord.gg/"
	# Format for forwarding the log on Discord
	logs_format = "[${log_time!HH:mm:ss}] [${log_thread_name}/${log_level}] [${log_logger_name}]: ${log_message}"
	# Level for the log on Discord (FATAL, ERROR, WARN, INFO, DEBUG, TRACE, ALL)
	logs_level = "INFO"
	# List of class to prevent from being sent to discord. You may use a package or a fully qualified class name. Eg: ["net.minecraft", "com.asupermod.somepackage.AClassToBan"]
	banned_mods_messages = []

Your config file
N/A

You need to add the permission to manage role to your bot


Let events bubble up through DOM

Instead of returning false which will both stopPropagation() and preventDefault() this will let events bubble up and href-to-links will behave the same way link-to does per default.
Checkout ember.js link-to-source: https://github.com/emberjs/ember.js/blob/master/packages/ember-htmlbars/lib/components/link-to.js#L627

Some context: I'm using ember-modal-dialog in a project and it listens for events outside the modal in order to dismiss and close it. This PR enables the click event to bubble up and for ember-modal-dialog to do its thing :)

@oscarni thanks for this, perhaps you could add a test?

Sure, I'll update the PR

Thanks! 🍻


eslint setup with some code fixes

Eslint Configuration
#16

Are all commits Es-Lint configuration related
?

@SauveJeanLuc yes, all of the commits are eslint related, some are minor changes due to errors by Eslint

@SauveJeanLuc yes, all of the commits are eslint related, some are minor changes are to fix errors pointed by Eslint

I can see some UI changes from the preview.
Did you notice ?

@SauveJeanLuc fixed that unexpected padding change in PopUp.jsx. Can you check again?

You can consider resolving all conflicts before I merge

@SauveJeanLuc resolved all merge conflicts


storagecluster: add CephCluster reconcile strategy

Signed-off-by: Jose A. Rivera<EMAIL_ADDRESS>(cherry picked from commit ed7b76419ae58b74328037d2c181afd776f06fa9)

/retest