PicklingError: Could not pickle the task to send it to the workers.

Describe the bug
While running ProfileReport(df), it returns picklerror while calculating  phi correlation.

To Reproduce

Version information:
 345                 return method()
346             return None
347         else:

/opt/conda/lib/python3.7/site-packages/pandas_profiling/profile_report.py in repr_html(self)
395     def repr_html(self):
396         """The ipython notebook widgets user interface gets called by the jupyter notebook."""
--> 397         self.to_notebook_iframe()
398
399     def repr(self):
/opt/conda/lib/python3.7/site-packages/pandas_profiling/profile_report.py in to_notebook_iframe(self)
375         with warnings.catch_warnings():
376             warnings.simplefilter("ignore")
--> 377             display(get_notebook_iframe(self))
378
379     def to_widgets(self):
/opt/conda/lib/python3.7/site-packages/pandas_profiling/report/presentation/flavours/widget/notebook.py in get_notebook_iframe(profile)
63         output = get_notebook_iframe_src(profile)
64     elif attribute == "srcdoc":
---> 65         output = get_notebook_iframe_srcdoc(profile)
66     else:
67         raise ValueError(
/opt/conda/lib/python3.7/site-packages/pandas_profiling/report/presentation/flavours/widget/notebook.py in get_notebook_iframe_srcdoc(profile)
21     width = config["notebook"]["iframe"]["width"].get(str)
22     height = config["notebook"]["iframe"]["height"].get(str)
---> 23     src = html.escape(profile.to_html())
24
25     iframe = f''
/opt/conda/lib/python3.7/site-packages/pandas_profiling/profile_report.py in to_html(self)
346
347         """
--> 348         return self.html
349
350     def to_json(self) -> str:
/opt/conda/lib/python3.7/site-packages/pandas_profiling/profile_report.py in html(self)
166     def html(self):
167         if self._html is None:
--> 168             self._html = self._render_html()
169         return self._html
170
/opt/conda/lib/python3.7/site-packages/pandas_profiling/profile_report.py in _render_html(self)
273         from pandas_profiling.report.presentation.flavours import HTMLReport
274
--> 275         report = self.report
276
277         disable_progress_bar = not config["progress_bar"].get(bool)
/opt/conda/lib/python3.7/site-packages/pandas_profiling/profile_report.py in report(self)
160     def report(self):
161         if self._report is None:
--> 162             self._report = get_report_structure(self.description_set)
163         return self._report
164
/opt/conda/lib/python3.7/site-packages/pandas_profiling/profile_report.py in description_set(self)
141     def description_set(self):
142         if self._description_set is None:
--> 143             self._description_set = describe_df(self.title, self.df)
144         return self._description_set
145
/opt/conda/lib/python3.7/site-packages/pandas_profiling/model/describe.py in describe(title, df)
80             pbar.set_postfix_str(f"Calculate {correlation_name} correlation")
81             correlations[correlation_name] = calculate_correlation(
---> 82                 df, variables, correlation_name
83             )
84             pbar.update()
/opt/conda/lib/python3.7/site-packages/pandas_profiling/model/correlations.py in calculate_correlation(df, variables, correlation_name)
166             if len(selcols) > 1:
167                 try:
--> 168                     correlation = df[selcols].phik_matrix(interval_cols=intcols)
169
170                     # Only do this if the column_order is set
/opt/conda/lib/python3.7/site-packages/phik/phik.py in phik_matrix(df, interval_cols, bins, quantile, noise_correction, dropna, drop_underflow, drop_overflow)
215
216     return phik_from_rebinned_df(
--> 217         data_binned, noise_correction, dropna=dropna, drop_underflow=drop_underflow, drop_overflow=drop_overflow
218     )
219
/opt/conda/lib/python3.7/site-packages/phik/phik.py in phik_from_rebinned_df(data_binned, noise_correction, dropna, drop_underflow, drop_overflow)
143         phik_list = Parallel(n_jobs=NCORES)(
144             delayed(_calc_phik)(co, data_binned[list(co)], noise_correction)
--> 145             for co in itertools.combinations_with_replacement(data_binned.columns.values, 2)
146         )
147
/opt/conda/lib/python3.7/site-packages/joblib/parallel.py in call(self, iterable)
1052
1053             with self._backend.retrieval_context():
-> 1054                 self.retrieve()
1055             # Make sure that we get a last message telling us we are done
1056             elapsed_time = time.time() - self._start_time
/opt/conda/lib/python3.7/site-packages/joblib/parallel.py in retrieve(self)
931             try:
932                 if getattr(self._backend, 'supports_timeout', False):
--> 933                     self._output.extend(job.get(timeout=self.timeout))
934                 else:
935                     self._output.extend(job.get())
/opt/conda/lib/python3.7/site-packages/joblib/_parallel_backends.py in wrap_future_result(future, timeout)
540         AsyncResults.get from multiprocessing."""
541         try:
--> 542             return future.result(timeout=timeout)
543         except CfTimeoutError as e:
544             raise TimeoutError from e
/opt/conda/lib/python3.7/concurrent/futures/_base.py in result(self, timeout)
426                 raise CancelledError()
427             elif self._state == FINISHED:
--> 428                 return self.__get_result()
429
430             self._condition.wait(timeout)
/opt/conda/lib/python3.7/concurrent/futures/_base.py in __get_result(self)
382     def __get_result(self):
383         if self._exception:
--> 384             raise self._exception
385         else:
386             return self._result
PicklingError: Could not pickle the task to send it to the workers.
-->
Additional context

@paudelsubodh could you describe the data somewhat? As this doesn't seem to occur with other usage.
Additionally, can you list the versions of pandas profiling, joblib and pandas?

@Baukebrenninkmeijer I had this same error. I am adding the information here.
Data: Telecom Churn Prediction
Pandas Profiling Version: 3.0.0
Joblib version: 1.1.0
Pandas version: 1.3.4
Please let me know if you need something else.

Any Update on this? I'm facing the same issue.

This happened to me as well, but the cause of the pickling error can vary. The following error seems to be generic:

PicklingError: Could not pickle the task to send it to the workers.

Just in case anyone else finds this issue, first make sure it's not caused by running out of space. The original issue shown above doesn't show an out of space issue.
If I dig into the lower level exception, I find No space left on device in my case:
  File "/home/a211278l/.local/lib/python3.10/site-packages/joblib/numpy_pickle.py", line 104, in write_array
    pickler.file_handle.write(chunk.tobytes('C'))
OSError: [Errno 28] No space left on device

The cause in my case seems common:

https://github.com/ydataai/pandas-profiling/issues/518
https://github.com/ydataai/pandas-profiling/issues/776


Add documentation for the Network resource

What this PR does / why we need it:
Add documentation for the network resource.
Which issue(s) this PR fixes:
Fixes #1579
Special notes for your reviewer:
Release note:

Documentation for the `Network` resources has been added.

Also refer this document from here https://github.com/gardener/gardener/blame/master/docs/README.md#L72


Fix to latest proptypes

Do the Text proptypes no longer work? As far as I can tell, they're still there. Happy to merge this in if there's an issue.


Redesign desktop nav, use shadcn and radix

I ran into an issue with radix with positioning the dropdown
https://github.com/shadcn-ui/ui/issues/1588
https://github.com/shadcn-ui/ui/issues/94
The best I could do was left align it
Moving your cursor on the space between the nav and the dropdown causes the dropdown to close, so I removed the space in between

I'd prefer to use headless but they open the dropdown on click, not hover.

Looks good to me


Fix errors reported by IBM OpenAPI Validator

$ npm run lint:ibm

><EMAIL_ADDRESS>lint:ibm /mnt/c/Users/thoma/Documents/dev/rocc-schemas
> npm run build && lint-openapi dist.yaml

><EMAIL_ADDRESS>build /mnt/c/Users/thoma/Documents/dev/rocc-schemas
> openapi bundle -o dist openapi/openapi.yaml

bundling openapi/openapi.yaml...
📦 Created a bundle for openapi/openapi.yaml at dist.yaml 42ms.

[Warning] No .validaterc file found. The validator will run in default mode.
To configure the validator, create a .validaterc file.

errors

  Message :   `id` property type should be string
  Path    :   paths./challenges.post.requestBody.content.application/json.schema.example.organizers.0.id
  Line    :   48

  Message :   `id` property type should be string
  Path    :   paths./challenges.get.responses.200.content.application/json.schema.items.example.organizers.0.id
  Line    :   67

  Message :   `id` property type should be string
  Path    :   paths./challenges/{id}.get.responses.200.content.application/json.schema.example.organizers.0.id
  Line    :   90

  Message :   `id` property type should be string
  Path    :   paths./challenges/{id}.put.requestBody.content.application/json.schema.example.organizers.0.id
  Line    :   109

  Message :   `id` property type should be string
  Path    :   paths./users/{username}.get.responses.200.content.application/json.schema.example.id
  Line    :   188

  Message :   `id` property type should be string
  Path    :   paths./users/{username}.put.requestBody.content.application/json.schema.example.id
  Line    :   220

  Message :   `id` property type should be string
  Path    :   paths./users/{username}.put.requestBody.content.application/xml.schema.example.id
  Line    :   223

  Message :   `id` property type should be string
  Path    :   components.schemas.Challenge.example.organizers.0.id
  Line    :   352

  Message :   `id` property type should be string
  Path    :   components.schemas.User.example.id
  Line    :   398

  Message :   Arrays MUST NOT be returned as the top-level structure in a response body.
  Path    :   paths./challenges.get.responses.200.content.application/json.schema
  Line    :   65

  Message :   Schema of type integer should use one of the following formats: int32, int64.
  Path    :   components.schemas.Grant.properties.amount.type
  Line    :   256

  Message :   Schema of type string should use one of the following formats: byte, binary, date, date-time, password.
  Path    :   components.schemas.Email.type
  Line    :   265

  Message :   Property names must follow case convention: lower_snake_case
  Path    :   components.schemas.Person.properties.firstName
  Line    :   274

  Message :   Property names must follow case convention: lower_snake_case
  Path    :   components.schemas.Person.properties.lastName
  Line    :   278

  Message :   Property names must follow case convention: lower_snake_case
  Path    :   components.schemas.Challenge.properties.startDate
  Line    :   298

  Message :   Property names must follow case convention: lower_snake_case
  Path    :   components.schemas.Challenge.properties.endDate
  Line    :   302

  Message :   Schema of type string should use one of the following formats: byte, binary, date, date-time, password.
  Path    :   components.schemas.Challenge.properties.website.type
  Line    :   310

  Message :   Property names must follow case convention: lower_snake_case
  Path    :   components.schemas.User.properties.firstName
  Line    :   374

  Message :   Property names must follow case convention: lower_snake_case
  Path    :   components.schemas.User.properties.lastName
  Line    :   378

warnings

  Message :   Operation `description` must be present and non-empty string.
  Path    :   paths./challenges.get
  Line    :   55

  Message :   Operations with non-form request bodies should set a name with the x-codegen-request-body-name annotation.
  Path    :   paths./users/{username}.put
  Line    :   197

  Message :   A 201 response should include a response body. Use 204 for responses without content.
  Path    :   paths./challenges.post.responses.201
  Line    :   51

  Message :   Should use status code 400 instead of 422 for invalid request payloads.
  Path    :   paths./challenges/{id}.get.responses.422
  Line    :   94

  Message :   Should use status code 400 instead of 422 for invalid request payloads.
  Path    :   paths./challenges/{id}.put.responses.422
  Line    :   118

  Message :   A 200 response should include a response body. Use 204 for responses without content.
  Path    :   paths./challenges/{id}.put.responses.200
  Line    :   112

  Message :   Should use status code 400 instead of 422 for invalid request payloads.
  Path    :   paths./challenges/{id}.patch.responses.422
  Line    :   136

  Message :   A 200 response should include a response body. Use 204 for responses without content.
  Path    :   paths./challenges/{id}.patch.responses.200
  Line    :   130

  Message :   Should use status code 400 instead of 422 for invalid request payloads.
  Path    :   paths./challenges/{id}.delete.responses.422
  Line    :   154

  Message :   A 200 response should include a response body. Use 204 for responses without content.
  Path    :   paths./users/{username}.put.responses.200
  Line    :   211

  Message :   Response schemas should be defined with a named ref.
  Path    :   paths./challenges.get.responses.200.content.application/json.schema
  Line    :   65

  Message :   operationIds should follow naming convention: operationId verb should be list
  Path    :   paths./challenges.get.operationId
  Line    :   59

  Message :   operationIds should follow naming convention: operationId verb should be get
  Path    :   paths./challenges/{id}.get.operationId
  Line    :   84

  Message :   operationIds should follow naming convention: operationId verb should be replace
  Path    :   paths./challenges/{id}.put.operationId
  Line    :   104

  Message :   operationIds should follow naming convention: operationId verb should be update
  Path    :   paths./challenges/{id}.patch.operationId
  Line    :   128

  Message :   operationIds should follow naming convention: operationId verb should be delete
  Path    :   paths./challenges/{id}.delete.operationId
  Line    :   146

  Message :   operationIds should follow naming convention: operationId verb should be replace
  Path    :   paths./users/{username}.put.operationId
  Line    :   202

  Message :   operationIds must follow case convention: lower_snake_case
  Path    :   paths./challenges.get.operationId
  Line    :   59

  Message :   operationIds must follow case convention: lower_snake_case
  Path    :   paths./challenges.post.operationId
  Line    :   43

  Message :   operationIds must follow case convention: lower_snake_case
  Path    :   paths./challenges/{id}.get.operationId
  Line    :   84

  Message :   operationIds must follow case convention: lower_snake_case
  Path    :   paths./challenges/{id}.put.operationId
  Line    :   104

  Message :   operationIds must follow case convention: lower_snake_case
  Path    :   paths./challenges/{id}.patch.operationId
  Line    :   128

  Message :   operationIds must follow case convention: lower_snake_case
  Path    :   paths./challenges/{id}.delete.operationId
  Line    :   146

  Message :   operationIds must follow case convention: lower_snake_case
  Path    :   paths./users/{username}.get.operationId
  Line    :   170

  Message :   operationIds must follow case convention: lower_snake_case
  Path    :   paths./users/{username}.put.operationId
  Line    :   202

  Message :   Schema properties must have a description with content in it.
  Path    :   components.schemas.Organization.properties.id.description
  Line    :   233

  Message :   Schema properties must have a description with content in it.
  Path    :   components.schemas.Organization.properties.name.description
  Line    :   236

  Message :   Schema properties must have a description with content in it.
  Path    :   components.schemas.Organization.properties.url.description
  Line    :   238

  Message :   Schema properties must have a description with content in it.
  Path    :   components.schemas.Grant.properties.id.description
  Line    :   246

  Message :   Schema properties must have a description with content in it.
  Path    :   components.schemas.Grant.properties.name.description
  Line    :   249

  Message :   Schema properties must have a description with content in it.
  Path    :   components.schemas.Grant.properties.description.description
  Line    :   251

  Message :   Schema properties must have a description with content in it.
  Path    :   components.schemas.Grant.properties.amount.description
  Line    :   255

  Message :   Schema properties must have a description with content in it.
  Path    :   components.schemas.Grant.properties.url.description
  Line    :   258

  Message :   Schema must have a non-empty description.
  Path    :   components.schemas.Person
  Line    :   268

  Message :   Schema properties must have a description with content in it.
  Path    :   components.schemas.Person.properties.id.description
  Line    :   271

  Message :   Schema properties must have a description with content in it.
  Path    :   components.schemas.Person.properties.firstName.description
  Line    :   274

  Message :   Schema properties must have a description with content in it.
  Path    :   components.schemas.Person.properties.lastName.description
  Line    :   278

  Message :   Schema must have a non-empty description.
  Path    :   components.schemas.User
  Line    :   360

  Message :   Schema properties must have a description with content in it.
  Path    :   components.schemas.User.properties.id.description
  Line    :   363

  Message :   Schema properties must have a description with content in it.
  Path    :   components.schemas.User.properties.username.description
  Line    :   366

  Message :   Schema properties must have a description with content in it.
  Path    :   components.schemas.User.properties.password.description
  Line    :   369

  Message :   Schema properties must have a description with content in it.
  Path    :   components.schemas.User.properties.role.description
  Line    :   384

  Message :   Schema properties must have a description with content in it.
  Path    :   components.schemas.User.properties.organizations.description
  Line    :   390

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>lint:ibm: `npm run build && lint-openapi dist.yaml`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>lint:ibm script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/tschaffter/.npm/_logs/2020-12-06T21_45_58_527Z-debug.log

Output of the linter after fixing all the errors. I could turn off the reporting of these warnings as OpenAPI states that the value of format is open for strings. For now keeping them, only a small number of fields like url and email are expected to show up in these warnings.
$ npm run lint:ibm

><EMAIL_ADDRESS>lint:ibm /mnt/c/Users/thoma/Documents/dev/rocc-schemas
> npm run build && lint-openapi dist.yaml

><EMAIL_ADDRESS>build /mnt/c/Users/thoma/Documents/dev/rocc-schemas
> openapi bundle -o dist openapi/openapi.yaml

bundling openapi/openapi.yaml...
📦 Created a bundle for openapi/openapi.yaml at dist.yaml 52ms.

warnings

  Message :   Schema of type string should use one of the following formats: byte, binary, date, date-time, password.
  Path    :   components.schemas.ResponsePageMetadata.properties.links.properties.next.type
  Line    :   183

  Message :   Schema of type string should use one of the following formats: byte, binary, date, date-time, password.
  Path    :   components.schemas.Organization.properties.url.type
  Line    :   204

  Message :   Schema of type string should use one of the following formats: byte, binary, date, date-time, password.
  Path    :   components.schemas.Grant.properties.url.type
  Line    :   231

  Message :   Schema of type string should use one of the following formats: byte, binary, date, date-time, password.
  Path    :   components.schemas.Email.type
  Line    :   238

  Message :   Schema of type string should use one of the following formats: byte, binary, date, date-time, password.
  Path    :   components.schemas.Challenge.properties.website.type
  Line    :   289


[Feature Request] Per-user permissions to download chapters

Is your feature request related to a problem? Please describe.
Currently only admin can download. The current workaround as detailed in the wiki is to run multiple instances, which from what I understand means the downloaders are not synchronized and will not respect the time limits to prevent IP bans.
Describe the solution you'd like
A toggle to allow users on the same instance to add chapters to the download manager. This way the download manager can queue concurrent downloads in a way that it won't get the IP banned on MD if there are concurrent downloads happening.
Additional context
There already is a "is admin" toggle when creating new users, but maybe a proper permission system is required.

Do you have a use case for this? Is there any particular reason why you want a user to download chapters but don't want to grant him admin access?

The main thing in the current form is that I wouldn't want these users to have permissions to add more users.
In the future, I would assume admins will have more features available that you wouldn't want a normal user to necessarily have as well, just so they can download chapters. This could be logs, viewing everyone's libraries, who knows.


*: automate releases with goreleaser

Description of the change:

.goreleaser.yml: goreleaser config file
.ci/gpg: GPG public key, encrypted private subkey (used for signing), and script to decrypt private subkey in CI
website/scripts: scripts to update versions in release commits and branches at build time
website/content/en/docs: release and installation guide simplifications, related docs cleanup
*: script and Makefile updates to support automated releases

Motivation for the change: This PR adds goreleaser and tooling for automated releases in CI, agnostic of CI platform (albeit with some environment configuration). Any Github user with write capabilities to the SDK repo can start a release by doing git tag vX.Y.Z && git push --tags.
Checklist
If the pull request includes user-facing changes, extra documentation is required:

[ ] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
[x] Add or update relevant sections of the docs website in website/content/en/docs

I need to test a full release on my operator-sdk fork before merging this, and add a PR description.

Successful release: https://travis-ci.org/github/estroz/operator-sdk/builds/741229073
Published release from job (using my Github key): https://github.com/estroz/operator-sdk/releases/tag/v0.33.0

/cc @asmacdo @rashmigottipati @theishshah


DAPR State store - Javascript SDK issue saving values always as string when use gRPC

With javascript SDK, If we use gRPC when save method is called, always values are persisted as string.
Then query filter does not work and also has others side efect.

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

ID: be98c390-3a32-085b-1529-a74bffefc76e
Version Independent ID: 1f92eb1d-21da-4d0b-ad70-a28d168636a9
Content: The Dapr state management building block
Content Source: docs/architecture/dapr-for-net-developers/state-management.md
Product: dotnet-architecture
GitHub Login: @amolenk
Microsoft Alias: nanil

Hi @zacutti
Because this is an issue with the JavaScript SDK, please report the issue in the Dapr JS SDK repository: https://github.com/dapr/js-sdk/issues
Thanks!

Closing this issue.


Plot line is not visible at the axis limits

ScottPlot Version: 4.1.65
Operating System: Windows 10
Application Type: WinForms
Question: Hello,
I noticed a rendering problem after migrating our project to ScottPlot from ComponentOne...
The lines are not visible over the axis line. I'm sure there is a solution for this. But I couldn't find....
For example:
double[] dataX = new double[] { 0, 2, 3, 4, 5 };
double[] dataY = new double[] { 0, 4, 9, 16, 25 };
var plot = formsPlot1.Plot.AddScatterList(Color.Red);
plot.StepDisplay = true;
formsPlot1.Plot.SetAxisLimitsX(0, 5);
formsPlot1.Plot.SetAxisLimitsY(0, 25);

My expected behavior is:

I don't want to change axis min/max values to make the lines visible. Min/max values are important for me to align other components next to plot. (I draw X and Y axis using my own component)
It is OK for me to give some padding between data area and axis area. But I cannot achieve this:

Actually, I don't need axes:

Any solution is accepted other than changing axis min/max values.
Thank you,
Murat

Hi @mocakturk,
I actually think this is the intended behavior.
Consider where the grid line is for x=5 ... it's right where the tick mark is, under the vertical black line

I think your final ascending step is underneath the black line... and I think this is its correct location.
Sample Code
double[] dataX = new double[] { 0, 2, 3, 4, 5 };
double[] dataY = new double[] { 0, 4, 9, 16, 25 };

ScottPlot.Plot plot = new(400, 300);

var scatter = plot.AddScatterList();
scatter.AddRange(dataX, dataY);
scatter.StepDisplay = true;

plot.SetAxisLimits(0, 5, 0, 25);
plot.SaveFig("test.png");

Solutions
If you really want to see that final line, two ideas come to mind:
Solution 1: pan 1 pixel
Pan the plot by a single pixel left. The tick mark for the x=5 position will look weird (it will be 1 pixel away from the edge of the screen), but you will be able to see your step. This is pretty hacky, but it works:
double[] dataX = new double[] { 0, 2, 3, 4, 5 };
double[] dataY = new double[] { 0, 4, 9, 16, 25 };

ScottPlot.Plot plot = new(400, 300);

var scatter = plot.AddScatterList();
scatter.AddRange(dataX, dataY);
scatter.StepDisplay = true;

plot.SetAxisLimits(0, 5, 0, 25);

plot.Render();
plot.GetSettings(showWarning: false).MouseDown(100, 100);
plot.GetSettings(showWarning: false).MousePan(99, 100);

plot.SaveFig("test.png");

Solution 2: thick line
Set your scatter plot's LineWidth to a large number and it will bleed away from beneath the frame and into the data area
double[] dataX = new double[] { 0, 2, 3, 4, 5 };
double[] dataY = new double[] { 0, 4, 9, 16, 25 };

ScottPlot.Plot plot = new(400, 300);

var scatter = plot.AddScatterList();
scatter.AddRange(dataX, dataY);
scatter.StepDisplay = true;
scatter.LineWidth = 5;

plot.SetAxisLimits(0, 5, 0, 25);
plot.SaveFig("test.png");

Thanks for this great question! I'm happy we found some solutions 🚀


sort order

how to set sort order while "censys search 'query'" ?
by default it sorted by digits (<IP_ADDRESS>, <IP_ADDRESS>....) asceding
in the web version : sort oder by relevance, asc, desc and random)

Hi @xroot000,
We currently do not support the sort order from the CLI. We can add that in the coming release, thank you for bringing this to our attention.


Added Blooms.

Adding Blooms. This implementation is quite unconventional when it comes to the colours and the UX.
Traditionally, Player 1 uses blue and black, and Player 2 uses red and yellow. In order to be consistent with Abstract Play's colour interface, I made the colours correspond with the colours assigned for players 1 and 2, and the second colours are the same colours with an opacity of 0.35. There is also a ring around the pieces to further differentiate it from the normal piece.
In terms of the UX, having a stash makes it very annoying to place pieces, so I opted for the ability to swap the colours if you tapped on the placed piece.
Board sizes 6 (default), 8 and 10 are included here.
For the threshold score, I went with the simple X(n) = 5n, where n is the base of the hexhex, so X(6) = 30, X(8) = 40 and X(10) = 50. We may explore a short game variant with a formula to generate a lower threshold for each size.
An alternative threshold that I'm also considering would be some fraction of the total number of cells. Assuming that the fraction is 0.25, X(6) = 31, X(8) = 54, and X(10) = 82.

I won't have time to look closely at the code for a bit, but I'll merge so you can get testing. Thanks!


Integrating multiple Jenkins CI instances for unified access

Is your feature request related to a problem? Please describe
The current OpenSearch Jenkins CI is critical to the success of OpenSearch project. It acts as a gateway for PR’s, distribution builds, benchmark tests, releases, security scans and more.
There are requests to add new tasks (for example adding integration test jobs against on a new Github Repo) to the current public OpenSearch Jenkins CI, keeping in mind the possibility of transitioning to community management soon.
The current Jenkins CI has been facing resource constraints, mainly caused by the increased specific tasks. This has led to service disruptions, for example increasing the frequency of build jobs, which in turn, has strained our other tasks within the Jenkins to run.
In response to these challenges, instead of relying on a current single Jenkins CI to handle all tasks, we're moving towards a distributed approach. This new strategy proposes the deployment of multiple Jenkins CI instances, each dedicated to managing specific types of tasks.
Describe the solution you'd like
The proposal in high level is to have multiple Jenkins instances, and each instance is resposible for a specific work/job/load ; for example we will have Jenkins for Build, Jenkins for Gradle Check, Jenkins for Benchmark, etc.
Acceptance criteria :

[ ] Jenkins CI shall be able to be deployed on multiple AWS accounts
[ ] By default, every AWS account should be able to deploy one instance of Jenkins CI
[ ] The Jenkins CI instances system should be publicly accessible as it is today
[ ] Support for BYOJ (Bring Your Own Jenkins) shall be available, allowing integration any Jenkins CI with the current Build Jenkinss CI that offers a public access point, provided it is accessible via the existing/current build CI URL path
[ ] If any Jenkins CI account is compromised, it won't impact any other Jenkins CI
[ ] If one Jenkins CI has been loaded, it won't impact any other Jenkins CI
[ ] Different accounts, teams, or individuals can manage Jenkins CI instances without sharing sensitive information or secrets or minimizing the needs for sharing information crossing accounts

Describe alternatives you've considered
Keep using the current Jenkins CI
Additional context
N/A

We've opted to proceed with having the identification of Jenkins instances into the URL path.
The existing URL, https://build.ci.opensearch.org/, will serve as the primary access point for the main Jenkins CI. For accessing additional Jenkins instances, we will utilize specific paths within the URL, denoted as /path/.
For example:


Fix histograms data range change.

Related to https://github.com/CartoDB/cartodb/issues/12618
Related PRs:

cartodb.js https://github.com/CartoDB/cartodb.js/pull/1719
deep-insights.js https://github.com/CartoDB/deep-insights.js/pull/577

When there is a map with several widgets, after applying a filter in one of them, the data returned by the other widgets adapts to the filter. It changes its data range. This is the bug fixed in this PR.
Acceptance

Add several widgets to a map. Histograms and time-series.
Apply several combinations of filters to those widgets. Assert that the range data doesn't change in all widgets.

While in Builder, modify the widget properties: bins, aggregation, column... with show totalson. Check that totals (the grey bars behind) reflect those changes, showing the proper visualization.
Check everything in embed page: no filters, filters applied, changing timezone...
To sum up, play A LOT with histogram and time-series widgets and check that the data range of all of them doesn't change.

I feel I've found something weird, but not related to this PR. Time series widget is being rendered each time any filter is applied or map center has changed. Instead of that, only bars should change their height, as we do with the histograms. Any clue @ivanmalagon or @rubenmoya if we have introduced recently or it is happening from the beginning of the new changes?

Found another bug, but again, not related :( -> https://github.com/CartoDB/cartodb/issues/12645

Both bugs mentioned by @xavijam fixed.

We had a whole render when data changed in time-series that was unnecessary. Now the bars change their height without rendering the whole widget.

When the bins are changed the histogram widgets gets reset. We weren't doing that and that caused the chart to be bad painted.

retest this please

retest this please


Add Codium as an option for the app name dropdown menu

Not all VSCode builds come from Microsoft. VSCodium is basically VSCode but without the telemetry Microsoft adds to their binary.

Will be added soon™.


autofix might not work for 100%?

Hi,
thanks for the plugin! I was looking for something like this for a long time. Awesome that you created it! I tested it on the voxpupuli/puppet-zabbix modul, the autofix created the following diff:
-) inherits zabbix::params {
+)inherits zabbix::params {

I'm not 100% sure this is correct, but I guess there should be a whitespace between ) and inherits?

I agree there should. It's not 100% yet, and there is a lot of stuff I want to add... I'm happy I'm not the only one with this itch :-)

@bastelfreak Should be fixed now (I added specific tests for this)


PhantomJS 2.1.1 (Windows 7 0.0.0) ERROR   ReferenceError: Can't find variable: Map

I have used "MVC ASP.NET Core with Angular" template.
I am trying to include phantomJS and run the tests, but i get the following errors:
    ERROR in [at-loader] ..\\node_modules\zone.js\dist\zone.js.d.ts:122:11 TS2451: Cannot redeclare block-scoped variable 'Zone'.     ERROR in [at-loader] ..\\node_modules\zone.js\ dist\zone.js.d.ts:363:14 TS2300: Duplicate identifier 'HasTaskState'.     ERROR in [at-loader] ..\\node_modules\zone.js\ dist\zone.js.d.ts:372:14 TS2300: Duplicate identifier 'TaskType'.     ERROR in [at-loader] ..\\node_modules\zone.js\ dist\zone.js.d.ts:458:15 TS2451: Cannot redeclare block-scoped variable 'Zone'.
PhantomJS 2.1.1 (Windows 7 0.0.0) ERROR ReferenceError: Can't find variable: Map at ../wwwroot/dist/vendor.js:12460
Below are the node module version i have been using(package.json):
` "dependencies": {
    "@angular/animations": "4.1.2",
    "@angular/common": "4.1.2",
    "@angular/compiler": "4.1.2",
    "@angular/core": "4.1.2",
    "@angular/forms": "4.1.2",
    "@angular/http": "4.1.2",
    "@angular/platform-browser": "4.1.2",
    "@angular/platform-browser-dynamic": "4.1.2",
    "@angular/platform-server": "4.1.2",
    "@angular/router": "4.1.2",
    "@types/node": "7.0.18",
    "angular2-template-loader": "0.6.2",
    "aspnet-prerendering": "^2.0.5",
    "aspnet-webpack": "^1.0.29",
    "awesome-typescript-loader": "3.1.3",
    "bootstrap": "3.3.7",
    "css": "2.2.1",
    "css-loader": "0.28.1",
    "es6-shim": "0.35.3",
    "event-source-polyfill": "0.0.9",
    "expose-loader": "0.7.3",
    "extract-text-webpack-plugin": "2.1.0",
    "file-loader": "0.11.1",
    "html-loader": "0.4.5",
    "isomorphic-fetch": "2.2.1",
    "jquery": "3.2.1",
    "json-loader": "0.5.4",
    "preboot": "4.5.2",
    "raw-loader": "0.5.1",
    "reflect-metadata": "0.1.10",
    "rxjs": "5.4.0",
    "style-loader": "0.17.0",
    "to-string-loader": "1.1.5",
    "typescript": "2.3.2",
    "url-loader": "0.5.8",
    "webpack": "2.5.1",
    "webpack-hot-middleware": "2.18.0",
    "webpack-merge": "4.1.0",
    "zone.js": "0.8.10"
  },
  "devDependencies": {
    "@types/chai": "3.5.2",
    "@types/jasmine": "2.5.47",
    "chai": "3.5.0",
    "istanbul-instrumenter-loader": "^3.0.0",
    "jasmine-core": "2.6.1",
    "karma": "1.7.0",
    "karma-chai": "0.1.0",
    "karma-chrome-launcher": "2.1.1",
    "karma-cli": "1.0.1",
    "karma-coverage-istanbul-reporter": "^1.3.0",
    "karma-htmlfile-reporter": "^0.3.5",
    "karma-jasmine": "1.1.0",
    "karma-jasmine-html-reporter": "^0.2.2",
    "karma-phantomjs-launcher": "^1.0.4",
    "karma-webpack": "2.0.3",
    "phantomjs-prebuilt": "^2.1.15"
  }`

and the tsconfig.json is as follows:
`{
	"compilerOptions": {
		"moduleResolution": "node",
		"target": "es5",
		"sourceMap": true,
		"experimentalDecorators": true,
		"emitDecoratorMetadata": true,
		"skipDefaultLibCheck": true,
		"lib": [ "es6", "dom" ],
		"types": [ "node" ]
	},
	"exclude": [
		"bin",
		"node_modules"
	],
	"atom": { "rewriteTsconfig": false }
}`

and the webpack.config.js code is :
`const path = require('path');
const webpack = require('webpack');
const merge = require('webpack-merge');
const CheckerPlugin = require('awesome-typescript-loader').CheckerPlugin;

module.exports = (env) => {
    // Configuration in common to both client-side and server-side bundles
    const isDevBuild = !(env && env.prod);
    const sharedConfig = {
        stats: { modules: false },
        context: __dirname,
		resolve: {
			extensions: ['.js', '.ts'],
			modules: [path.join(__dirname, "node_modules")]
		},
        output: {
            filename: '[name].js',
            publicPath: '/dist/' // Webpack dev middleware, if enabled, handles requests for this URL prefix
        },
        module: {
			rules: [
                { test: /\.ts$/, include: /ClientApp/, use: ['awesome-typescript-loader?silent=true', 'angular2-template-loader'] },
                { test: /\.html$/, use: 'html-loader?minimize=false' },
                { test: /\.css$/, use: [ 'to-string-loader', isDevBuild ? 'css-loader' : 'css-loader?minimize' ] },
                { test: /\.(png|jpg|jpeg|gif|svg)$/, use: 'url-loader?limit=25000' }
            ]
        },
        plugins: [new CheckerPlugin()]
    };

    // Configuration for client-side bundle suitable for running in browsers
	const clientBundleOutputDir = '..//wwwroot/dist';
    const clientBundleConfig = merge(sharedConfig, {
		entry: { 'main-client': '..//ClientApp/boot-client.ts' },
        output: { path: path.join(__dirname, clientBundleOutputDir) },
        plugins: [
            new webpack.DllReferencePlugin({
                context: __dirname,
				manifest: require('..//wwwroot/dist/vendor-manifest.json')
            })
        ].concat(isDevBuild ? [
            // Plugins that apply in development builds only
            new webpack.SourceMapDevToolPlugin({
                filename: '[file].map', // Remove this line if you prefer inline source maps
                moduleFilenameTemplate: path.relative(clientBundleOutputDir, '[resourcePath]') // Point sourcemap entries to the original file locations on disk
            })
        ] : [
            // Plugins that apply in production builds only
            new webpack.optimize.UglifyJsPlugin()
        ])
    });
    return [clientBundleConfig];
};
`

How can i solve the errors mentioned above? I have tried solutions mentioned in https://github.com/monounity/karma-typescript/issues/83. Nothing worked.
Any help would be appreciated!
Looking forward for some answer.
Thanks.

Sorry to hear of the trouble. I'm afraid this is not something I can help with, as it's specifically about some incompatibility among Karma, Zone, and PhantomJS (and maybe at-loader). You might be able to get better progress with this if you can create a minimal repro case involving as few different technologies as possible. If you end up tracking this down and believe it's an issue with some code in this repo, please let us know. Sorry I don't have an easier suggestion!

@NVK15 The boot-tests.js is configured to use latest chrome browser, so it runs fine with all ES6 keywords, syntax etc.,
But, phantom JS requires polyfills so install core-js, and import it before importing zone.


feat(api): add zod validate middleware

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

Current dependencies on/for this PR:

main

PR #6

PR #7   👈

This stack of pull requests is managed by Graphite.

Merge activity

Dec 31, 12:03 PM: @ToastedDev started a stack merge that includes this pull request via Graphite.


wip: cleanup(config): new json_output_properties flags and output options consolidation

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

/kind release

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area tests

/area proposals

/area CI

What this PR does / why we need it:
Redesign JSON log output fields options and expose configuration for most fields to give adopters more options to tailor the space of the log while maintaining backward compatibility.
This feature was requested by the community, CC @misterjulien
@jasondellaluce could get the python tests to run locally, but most of them failed meaning I am a bit unclear re how to add new tests to this PR , marking it as wip in the interim. Hoping you could give some pointers, thank you!
Which issue(s) this PR fixes:
https://github.com/falcosecurity/falco/issues/2628

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

cleanup(config): new json_output_properties flags and output options consolidation

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: incertum
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [incertum]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/milestone 0.36.0

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


How to debug "failed_to_pick_backend"

I deployed hasura graphql engine following the guide. Everything works fine except the endpoint keeps returning 502 (I've waited long enough).
Logs of load balancer show the error is failed_to_pick_backend. How can I debug this problem?

The deployment works in a single cluster. The only difference between it and the zoneprinter sample I can see is that hasura uses 8080 containerPort. Does it matter?

failed_to_pick_backend means that no backend responds to health checks with an HTTP 200 status.
You should start by checking the health check configuration on the load balancer.

Thanks a lot. Changed the health check configuration and everything works ok!


Update redux example

This PR uses next-redux-wrapper to simplify the redux setup.

Oh wonderful, thanks!

Hi, I was lazy and merged this without deploying as it ran locally (in dev and with npm run build).
It is fine locally but weirdly the build fails when deployed to now.sh:

next build

Using "webpack" config function defined in next.config.js.
{ Error: ./pages/clock.js?entry
Module not found: Error: Can't resolve 'next-redux-wrapper' in '/home/nowuser/src/pages'
resolve 'next-redux-wrapper' in '/home/nowuser/src/pages'
Parsed request is a module
using description file: /home/nowuser/src/package.json (relative path: ./pages)
Field 'browser' doesn't contain a valid alias configuration
after using description file: /home/nowuser/src/package.json (relative path: ./pages)
resolve as module
/home/nowuser/node_modules doesn't exist or is not a directory
/home/node_modules doesn't exist or is not a directory
/node_modules doesn't exist or is not a directory
/home/nowuser/src/pages/node_modules doesn't exist or is not a directory
looking for modules in /home/nowuser/src/node_modules/next/node_modules
using description file: /home/nowuser/src/node_modules/next/package.json (relative path: ./node_modules)
Field 'browser' doesn't contain a valid alias configuration
after using description file: /home/nowuser/src/node_modules/next/package.json (relative path: ./node_modules)
using description file: /home/nowuser/src/node_modules/next/package.json (relative path: ./node_modules/next-redux-wrapper)
as directory
/home/nowuser/src/node_modules/next/node_modules/next-redux-wrapper doesn't exist
no extension
Field 'browser' doesn't contain a valid alias configuration
/home/nowuser/src/node_modules/next/node_modules/next-redux-wrapper doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/home/nowuser/src/node_modules/next/node_modules/next-redux-wrapper.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/home/nowuser/src/node_modules/next/node_modules/next-redux-wrapper.json doesn't exist
looking for modules in /home/nowuser/src/node_modules
using description file: /home/nowuser/src/package.json (relative path: ./node_modules)
Field 'browser' doesn't contain a valid alias configuration
after using description file: /home/nowuser/src/package.json (relative path: ./node_modules)
using description file: /home/nowuser/src/package.json (relative path: ./node_modules/next-redux-wrapper)
as directory
/home/nowuser/src/node_modules/next-redux-wrapper doesn't exist
no extension
Field 'browser' doesn't contain a valid alias configuration
/home/nowuser/src/node_modules/next-redux-wrapper doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/home/nowuser/src/node_modules/next-redux-wrapper.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/home/nowuser/src/node_modules/next-redux-wrapper.json doesn't exist
[/home/nowuser/node_modules]
[/home/node_modules]
[/node_modules]
[/home/nowuser/src/pages/node_modules]
[/home/nowuser/src/node_modules/next/node_modules/next-redux-wrapper]
[/home/nowuser/src/node_modules/next/node_modules/next-redux-wrapper]
[/home/nowuser/src/node_modules/next/node_modules/next-redux-wrapper.js]
[/home/nowuser/src/node_modules/next/node_modules/next-redux-wrapper.json]
[/home/nowuser/src/node_modules/next-redux-wrapper]
[/home/nowuser/src/node_modules/next-redux-wrapper]
[/home/nowuser/src/node_modules/next-redux-wrapper.js]
[/home/nowuser/src/node_modules/next-redux-wrapper.json]
@ ./pages/clock.js?entry 31:24-53
@ multi ./pages/clock.js?entry
at /home/nowuser/src/node_modules/next/dist/server/build/index.js:122:21
at /home/nowuser/src/node_modules/webpack/lib/Compiler.js:256:15
at Compiler.emitRecords (/home/nowuser/src/node_modules/webpack/lib/Compiler.js:351:37)
at /home/nowuser/src/node_modules/webpack/lib/Compiler.js:249:12
at /home/nowuser/src/node_modules/webpack/lib/Compiler.js:344:11
at next (/home/nowuser/src/node_modules/tapable/lib/Tapable.js:154:11)
at Compiler.compiler.plugin (/home/nowuser/src/node_modules/webpack/lib/performance/SizeLimitsPlugin.js:99:4)
at Compiler.applyPluginsAsyncSeries1 (/home/nowuser/src/node_modules/tapable/lib/Tapable.js:158:13)
at Compiler.afterEmit (/home/nowuser/src/node_modules/webpack/lib/Compiler.js:341:8)
at Compiler. (/home/nowuser/src/node_modules/webpack/lib/Compiler.js:336:14)
errors: [ './pages/clock.js?entry\nModule not found: Error: Can't resolve 'next-redux-wrapper' in '/home/nowuser/src/pages'\nresolve 'next-redux-wrapper' in '/home/nowuser/src/pages'\n  Parsed request is a module\n  using description file: /home/nowuser/src/package.json (relative path: ./pages)\n    Field 'browser' doesn't contain a valid alias configuration\n  after using description file: /home/nowuser/src/package.json (relative path: ./pages)\n    resolve as module\n      /home/nowuser/node_modules doesn't exist or is not a directory\n      /home/node_modules doesn't exist or is not a directory\n      /node_modules doesn't exist or is not a directory\n      /home/nowuser/src/pages/node_modules doesn't exist or is not a directory\n      looking for modules in /home/nowuser/src/node_modules/next/node_modules\n        using description file: /home/nowuser/src/node_modules/next/package.json (relative path: ./node_modules)\n          Field 'browser' doesn't contain a valid alias configuration\n        after using description file: /home/nowuser/src/node_modules/next/package.json (relative path: ./node_modules)\n          using description file: /home/nowuser/src/node_modules/next/package.json (relative path: ./node_modules/next-redux-wrapper)\n            as directory\n              /home/nowuser/src/node_modules/next/node_modules/next-redux-wrapper doesn't exist\n            no extension\n              Field 'browser' doesn't contain a valid alias configuration\n              /home/nowuser/src/node_modules/next/node_modules/next-redux-wrapper doesn't exist\n            .js\n              Field 'browser' doesn't contain a valid alias configuration\n              /home/nowuser/src/node_modules/next/node_modules/next-redux-wrapper.js doesn't exist\n            .json\n              Field 'browser' doesn't contain a valid alias configuration\n              /home/nowuser/src/node_modules/next/node_modules/next-redux-wrapper.json doesn't exist\n      looking for modules in /home/nowuser/src/node_modules\n        using description file: /home/nowuser/src/package.json (relative path: ./node_modules)\n          Field 'browser' doesn't contain a valid alias configuration\n        after using description file: /home/nowuser/src/package.json (relative path: ./node_modules)\n          using description file: /home/nowuser/src/package.json (relative path: ./node_modules/next-redux-wrapper)\n            as directory\n              /home/nowuser/src/node_modules/next-redux-wrapper doesn't exist\n            no extension\n              Field 'browser' doesn't contain a valid alias configuration\n              /home/nowuser/src/node_modules/next-redux-wrapper doesn't exist\n            .js\n              Field 'browser' doesn't contain a valid alias configuration\n              /home/nowuser/src/node_modules/next-redux-wrapper.js doesn't exist\n            .json\n              Field 'browser' doesn't contain a valid alias configuration\n              /home/nowuser/src/node_modules/next-redux-wrapper.json doesn't exist\n[/home/nowuser/node_modules]\n[/home/node_modules]\n[/node_modules]\n[/home/nowuser/src/pages/node_modules]\n[/home/nowuser/src/node_modules/next/node_modules/next-redux-wrapper]\n[/home/nowuser/src/node_modules/next/node_modules/next-redux-wrapper]\n[/home/nowuser/src/node_modules/next/node_modules/next-redux-wrapper.js]\n[/home/nowuser/src/node_modules/next/node_modules/next-redux-wrapper.json]\n[/home/nowuser/src/node_modules/next-redux-wrapper]\n[/home/nowuser/src/node_modules/next-redux-wrapper]\n[/home/nowuser/src/node_modules/next-redux-wrapper.js]\n[/home/nowuser/src/node_modules/next-redux-wrapper.json]\n @ ./pages/clock.js?entry 31:24-53\n @ multi ./pages/clock.js?entry' ],
warnings: [] }
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "build"
npm ERR! Linux 4.7.0-coreos
npm ERR! code ELIFECYCLE
npm ERR! Please include the following file with any support request:
npm ERR!     /home/nowuser/src/npm-debug.log
npm ERR! node v7.0.0
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script 'next build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the nextjs-starter package,
npm ERR! not with npm itself.
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls nextjs-starter
npm ERR! There is likely additional logging output above.
npm ERR! Tell the author that this fails on your system:
npm ERR!     next build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs nextjs-starter
npm ERR! npm  v3.10.9
npm ERR<EMAIL_ADDRESS>build: next build

I've commented out the clock demo and removed the next-redux-wrapper package from package.json for now. :(
I've left it in as it works fine locally, but for some reason the build step fails on now.sh on that package, with the above error. It's like it can't find the package for some reason. If anyone has any idea why please let me know. :)

Hey @iaincollins sorry for my late response. I didn't use now deployment so I did hit this bug.
After I reproduced the bug with other apps as well using now, I believe next-redux-wrapper setup (nested next setup) breaks the deployment.
To fix the problem for now we can pull in the package wich actually works pretty well without its dependencies.
https://github.com/HaNdTriX/nextjs-starter/commit/02a8bf6a4bfe776f9c71b51427089bcd48ac8947

I tried to install your project nextjs-starter and it failed as is, so I did it this way:
git clone https://github.com/iaincollins/nextjs-starter.git
rm npm-shrinkwrap.json
yarn install
now

It helped. Both npm-shrinkwrap.json and yarn.lock should be updated too when you add packages.
Deployment log:
> Deploying ~/Sites/nextjs-starter
> Using Node.js 7.0.0 (requested: `7.x.x`)
> Ready! https://nextjs-starter-ijbpqoulco.now.sh (copied to clipboard) [833ms]
> Initializing…
> Building
> ▲ npm install
>  ‣<EMAIL_ADDRESS>>  ‣<EMAIL_ADDRESS>>  ‣<EMAIL_ADDRESS>>  ‣<EMAIL_ADDRESS>>  ‣<EMAIL_ADDRESS>>  ‣<EMAIL_ADDRESS>>  ‣<EMAIL_ADDRESS>>  ‣<EMAIL_ADDRESS>> ✓ Using "yarn.lock"
> ✓ Installed 877 modules [14s]
> ▲ npm run build
> ><EMAIL_ADDRESS>build /home/nowuser/src
> > next build
> > Using "webpack" config function defined in next.config.js.
> ▲ npm install
>  ‣<EMAIL_ADDRESS>>  ‣<EMAIL_ADDRESS>>  ‣<EMAIL_ADDRESS>>  ‣<EMAIL_ADDRESS>>  ‣<EMAIL_ADDRESS>>  ‣<EMAIL_ADDRESS>>  ‣<EMAIL_ADDRESS>>  ‣<EMAIL_ADDRESS>>  ‣<EMAIL_ADDRESS>> ✓ Installed 877 modules [14s]
> ▲ npm run build
> ><EMAIL_ADDRESS>build /home/nowuser/src
> > next build
> > Using "webpack" config function defined in next.config.js.
> ▲ npm start
> ><EMAIL_ADDRESS>start /home/nowuser/src
> > node index.js
> Deployment complete!

Interesting @kirill-konshin - thanks for looking at it! Thanks also @HaNdTriX for investigating.
I am probably going to remove the yarn lockfile, which came in a previous pull request and I don't want to maintaining two sets of package metadata.
The shrinkwrap file should be correct, so that looks like an issue.
Will update and verify and roll out an update it if it works here too!

@iaincollins you're welcome :)

Thank you, looks like that was it! The demo is back at https://nextjs-starter.now.sh :)
I'm very happy to have this in as I wasn't quite sure how to do this myself, so thank you both for your work on it too.


TimeViewer matplotlib figure color

This PR updates the background and foreground colors of the internal matplotlib figure depending on the palette chosen for _Brain.

background="white"
background="black" (default)

It's an item of #7162

can we add this to the doc somewhere?

I was told some years ago "if there is no doc it does not exist" :)

_Brain is a private class but its signature and features are designed to follow PySurfer's.

yes but does it justify not documenting this option in the doc?

AFAIK it's the case already:
https://github.com/mne-tools/mne-python/blob/e2e114d00ccb8eebca790550cbb3bb30eba81ecb/mne/viz/_brain/_brain.py#L60-L65

I mean in the tutorials in the narrative doc. I would love to see the
screenshots you shared appear
on the mne website. Makes sense?

#7927

Thanks @GuillaumeFavelier !


Return vue instance in mount method(#26)

According to #26

Released in https://github.com/CanopyTax/single-spa-vue/releases/tag/v1.6.0


Printing on custom page size does not work, tray with custom page size not accepted as default

After adding custom page size support to the PostScript Printer Application I have set the page size of one tray to a custom size on the "Media" page and then selected this tray as default on "Printing Defaults". After that I have left the "Printing Defaults" page to get to another page of the web interface and clicked into "Printing Defaults" again, finding that the other tray (using one of the standard size) was selected as default.
The log showed:
Unsupported media-default=custom_custom_5.5x11in_5.5x11in

I checked the code and found the problem. Here is the patch to fix it:
diff --git a/pappl/printer-driver.c b/pappl/printer-driver.c
index d5b37ec..4bf3acf 100644
--- a/pappl/printer-driver.c
+++ b/pappl/printer-driver.c
@@ -1212,8 +1212,8 @@ validate_defaults(

       if (pwg->length > max_length)
         max_length = pwg->length;
-      if (pwg->length > max_length)
-        max_length = pwg->length;
+      if (pwg->length < min_length)
+        min_length = pwg->length;
     }
   }

With this change custom page sizes work as intended.

[master 64d4b4d] Fix an issue with validation of custom media sizes (Issue #120)

[master 64d4b4d] Fix an issue with validation of custom media sizes (Issue #120)


Please invite me to the GitHub Community Organization

Name
Atharv Bobade
Discord Username (if applicable)
atharv181
Additional Context
I found eddie on twitter and the work is very impressive to me. Journey of my opensource is started because of eddie and hence would like to join the community to contribute, collaborate and learn.

My journey in opensource is just started because of eddie and want to continue with you all :)

Thank you :)


[Bug]: cannot find module 'puppeteer'

Minimal, reproducible example
const puppeteer = require("puppeteer");

(async ()=>{
 const browser= await puppeteer.launch();
 const page = await browser.newPage();
 await page.goto("http://xxxxxx");
})();

Background
node version 12.6.0
npm version 6.9.0
dependencies:
bufferutil"^4.0.1"
puppeteer-core:"^23.10.2"
utf-8-validate:"6.0.5"
Expectation
I would like to know if puppeteer is supported under the current node version.
Reality
Error: Cannot find module pupeteer
Puppeteer configuration file (if used)
No response
Puppeteer version
23.10.2
Node version
12.6.0
Package manager
npm
Package manager version
6.9.0
Operating system
Windows

You seem to be installing puppeteer-core and not puppeteer. Either install puppeteer or require('puppeteer-core'). Let me know if that helped.

Actually, it did not work.
Error:Cannot find module 'pupeteer-core/internal/puppeteer-core.js'
I try to install both pupetter,puetter-core. The Error still popped out.

That indicates an unsupported node version. Puppeteer requires at least Node 18+.


Wait for TS freeze

Waiting on #55 to be merged before accepting any more PRs, since this is a pretty large change, it will cause a lot of merge conflicts.

With #55 closed, TS freeze "has thawed" :P


"Polymorphic Aggregates in Spring" documentation (and error-handling) lacking

Basic information

Axon Framework version: 4.4.3
JDK version:  openjdk version "11.0.3" 2019-04-16 LTS

Documentation says:

Polymorphic Aggregates in Spring
If you are using Spring, Axon will automatically detect polymorphic aggregates based on the @Aggregate annotations and class hierarchy. The @Aggregate annotation needs to be put on the shared parent class that contains the aggregate identifier, as well as every subclass that is a potential instance type of that shared parent class.

I've read that as

put @Aggregate on any class that has @AggregateIdentifier
put @Aggregate on any conrete subclass

This worked so far, but we didn't really do much with polymorphic aggregates. Now consider this:
@Aggregate
abstract class A {
    @AggregateIdentifier String id;
}

// no annotation here as per my understanding of the docs
abstract class B extends A {
}

@Aggregate
class C extends B {
}

Generally this works. Unless you attempt to call a command-handler in B. I don't have it in front of me right now, but IIRC in SpringPrototypeAggregateFactory.afterPropertiesSet/AbstractAggregateFactory.postProcessInstance()  the lookup subtypes.get(aggregate.getClass()) looks for B.class here which is not contained in the map and the result is a rather meaningless NPE. You are doing a fine job with error messages all over the place and I feel SpringPrototypeAggregateFactory can be improved a bit here. :-)
Second there is the documentation. Again as I've read it, the example above should work, but doesn't. It can be fixed by adding @Aggregate to B, but is it the right way?

First off, thanks for drafting this issue with us, @michaelbub.
To get this out of the door before moving to the subject at hand, I would recommend upgrading to the most recent version of Axon.
It does not only provide you with newer features but also with more bug and security fixes.
Furthermore, we do not introduce breaking changes in patch and minor releases.
This approach will further simplify moving to the most recent release of Axon at all times.
Now, to your subject at hand.
The Polymorphic Aggregate implementation intends to support the use case you describe.
So, to simplify that, you should be able to have:

An root/parent abstract class with optional command and event sourcing handlers.
An intermediate (optionally) abstract class, with optional command and event sourcing handlers.
A child class with a no-argument constructor, command, and event sourcing handlers.

However, your problem doesn't come out of thin air.
As such, we improved the AggregatePolymorphismTest in this commit with exactly such a scenario.
As the test case succeeds, we wondered if you could provide more insights into what you're doing precisely.
Could you, perhaps, provide a small sample project showing the problem you are facing?
If that's too much of a hassle, please describe the difference between your use case and the test case I've just shared in the commit.

I should have mentioned that this works in unit-tests. IIRC unit-tests do not even require any of the @Aggregate to be present for everything to work just fine. But when the app is running (and using SpringPrototypeAggregateFactory and whatever else) and class B does not have the annotation: failure as soon as B should handle a command.
So the difference between your test case and what I am doing is just how you run it, I suppose.
If still required I can provide a sample project soonish.

I just setup a sample project and I cannot reproduce the problem here. Code-wise I am as close as I can think to our actual app. Configuration-wise probably not so much. Will get back with more info.

For the sake of completeness the stacktrace I got when things went wrong:
java.lang.NullPointerException: null
	at java.base/java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936)
	at java.base/java.util.concurrent.ConcurrentHashMap.containsKey(ConcurrentHashMap.java:964)
	at java.base/java.util.Collections$SetFromMap.contains(Collections.java:5510)
	at org.springframework.beans.factory.support.AbstractBeanFactory.markBeanAsCreated(AbstractBeanFactory.java:1721)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.configureBean(AbstractAutowireCapableBeanFactory.java:323)
	at org.axonframework.spring.eventsourcing.SpringPrototypeAggregateFactory$1.postProcessInstance(SpringPrototypeAggregateFactory.java:143)
	at org.axonframework.eventsourcing.AbstractAggregateFactory.createAggregateRoot(AbstractAggregateFactory.java:73)
	at org.axonframework.spring.eventsourcing.SpringPrototypeAggregateFactory.createAggregateRoot(SpringPrototypeAggregateFactory.java:82)
	at org.axonframework.eventsourcing.EventSourcingRepository.doLoadWithLock(EventSourcingRepository.java:129)
	at org.axonframework.eventsourcing.EventSourcingRepository.doLoadWithLock(EventSourcingRepository.java:52)
	at org.axonframework.modelling.command.LockingRepository.doLoad(LockingRepository.java:118)
	at org.axonframework.modelling.command.LockingRepository.doLoad(LockingRepository.java:52)
	at org.axonframework.modelling.command.AbstractRepository.lambda$load$4(AbstractRepository.java:122)
	at java.base/java.util.HashMap.computeIfAbsent(HashMap.java:1133)
	at org.axonframework.modelling.command.AbstractRepository.load(AbstractRepository.java:121)
	at org.axonframework.modelling.command.AggregateAnnotationCommandHandler$AggregateCommandHandler.handle(AggregateAnnotationCommandHandler.java:465)
	at org.axonframework.modelling.command.AggregateAnnotationCommandHandler$AggregateCommandHandler.handle(AggregateAnnotationCommandHandler.java:454)
	at org.axonframework.modelling.command.AggregateAnnotationCommandHandler.handle(AggregateAnnotationCommandHandler.java:173)
	at org.axonframework.modelling.command.AggregateAnnotationCommandHandler.handle(AggregateAnnotationCommandHandler.java:61)
	at org.axonframework.messaging.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:57)
	at net.artelis.commonlibs.axon.MdcInterceptor.handle(MdcInterceptor.java:128)
	at org.axonframework.messaging.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:55)
	at org.axonframework.messaging.interceptors.CorrelationDataInterceptor.handle(CorrelationDataInterceptor.java:65)
	at org.axonframework.messaging.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:55)
	at org.axonframework.messaging.unitofwork.DefaultUnitOfWork.executeWithResult(DefaultUnitOfWork.java:74)
	at org.axonframework.commandhandling.SimpleCommandBus.handle(SimpleCommandBus.java:177)
	at org.axonframework.commandhandling.SimpleCommandBus.doDispatch(SimpleCommandBus.java:143)
	at org.axonframework.commandhandling.SimpleCommandBus.dispatch(SimpleCommandBus.java:111)
	at org.axonframework.commandhandling.gateway.RetryingCallback$RetryDispatch.run(RetryingCallback.java:120)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)

What we did wrong:
In the early days (already Axon 4.x, but not sure which) we setup AspectJ to provide logging for each type of handler (Command/Event/Query). During development it became clear that Axon does not like if someone else is messing with the Aggregate classes. I remember the error we got made it rather obvious that whatever AspectJ does to the class, the change of type to generated proxy class, did not work with Axon. So we excluded handlers in aggregates from AspectJ, i. e. we excluded all handlers in classes with the @Aggregate annotation. Then polymorphism came along and suddenly there are command handlers in (abstract) aggregates that don't have the annotation. Boom! Only this time the error is far less obvious.
So by adding the annotation to B I was merely disabling AspectJ again, making everything work as it should have in the first place.
Now as we know Axon a little bit better there are probably better ways to do logging in just the same way. MessageXInterceptor classes should do the trick.
I am closing this as it's most certainly not a bug in Axon.

Wow darn, that's a pretty massive gotcha there, @michaelbub.
Thanks for sharing that with us!
If at all applicable, I'll see if future versions of the Framework can coop better with stuff like AspectJ.
Or, at least, provide more precise guidance on the subject through the Reference Guide or exception messages.
Thanks again for sharing this with the community, @michaelbub.


revisit API to add React and React-Dom as peer dependencies instead of being passed to the reactToWebcompnent function

I don't like to put real code in index files, as it makes searching and tabs harder. I limit indexes to only have imports/exports. For all those modlets (core, render, and root), rename index.ts to be <modlet>.ts, then create a new index.ts that has export { default } from "./<modlet>.ts"


[SPARK-11449][Core] PortableDataStream should be a factory

PortableDataStream maintains some internal state. This makes it tricky to reuse a stream (one needs to call close on both the PortableDataStream and the InputStream it produces).
This PR removes all state from PortableDataStream and effectively turns it into an InputStream/Array[Byte] factory. This makes the user responsible for managing the InputStream it returns.
cc @srowen

Can one of the admins verify this patch?

@kmader what do you think of this one?

Test build #1967 has started for PR 9417 at commit 91b8c6c.

Test build #1967 has finished for PR 9417 at commit 91b8c6c.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #1968 has started for PR 9417 at commit 91b8c6c.

Test build #1968 has finished for PR 9417 at commit 91b8c6c.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * case class Corr(\n  * case class Corr(left: Expression, right: Expression)\n  * case class RepartitionByExpression(\n  *         logInfo(s\"Hive class not found $e\")\n  *         logDebug(\"Hive class not found\", e)\n

@srowen @hvanhovell this is a nice improvement and more elegant than the original approach.
As a side node, In our code base (which uses PortableDataStream quite a bit), these changes didn't break anything so since it passes tests as well, I'd say it's good to go.

LGTM. Let me leave it open a bit for comments.

Merged to master


Test Framework: added support for uploading and deleting test support…

Thanks, @dmitrykhabarov. I have made a few small comments here.


mikutter: fix build against current glib

When compiled against current versions of glib, the glib2 gem in ruby-gnome fails to build because of a duplicated declaration of the function g_bookmark_file_get_type.
This has already been fixed upstream 1 2, but the respective patch needs a small adjustment to the path of the affected source file in order to work with mikutter's gemset declaration.
Description of changes
Add a patch that fixes the build of glib2 from ruby-gnome against current versions of glib.
Failing Hydra build: https://hydra.nixos.org/build/241836610#tabs-summary
Hydra log: https://hydra.nixos.org/build/241836610/nixlog/2
Relevant log excerpt:
rbglib_bookmarkfile.c:39:1: error: static declaration of 'g_bookmark_file_get_type' follows non-static declaration
   39 | g_bookmark_file_get_type(void)
      | ^~~~~~~~~~~~~~~~~~~~~~~~
In file included from /nix/store/ybmdzvab1s6hfkfj4hm848pgdxzlc36g-glib-2.78.1-dev/include/glib-2.0/gobject/gboxed.h:29,
                 from /nix/store/ybmdzvab1s6hfkfj4hm848pgdxzlc36g-glib-2.78.1-dev/include/glib-2.0/gobject/gobject.h:31,
                 from /nix/store/ybmdzvab1s6hfkfj4hm848pgdxzlc36g-glib-2.78.1-dev/include/glib-2.0/gobject/gbinding.h:31,
                 from /nix/store/ybmdzvab1s6hfkfj4hm848pgdxzlc36g-glib-2.78.1-dev/include/glib-2.0/glib-object.h:24,
                 from rbgobject.h:25,
                 from rbgprivate.h:31,
                 from rbglib_bookmarkfile.c:22:

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

Oh so, there are newer versions! I made the mistake and thought https://github.com/mikutter/mikutter was official (the updates there stopped about 3 years ago).
If updating fixes this, that's obviously great too. Do you happen to know the procedure for that? (I see there's an update.sh, but its usage eludes me so far)

Oh so, there are newer versions! I made the mistake and thought https://github.com/mikutter/mikutter was official (the updates there stopped about 3 years ago).
If updating fixes this, that's obviously great too. Do you happen to know the procedure for that? (I see there's an update.sh, but its usage eludes me so far)

heh -- i tried and failed a few weeks ago but i am not very familiar with ruby.
i started with
> nix-shell maintainers/scripts/update.nix --argstr path mikutter

but the files in deps needed some more editing. The Gemfile.lock didn't seem correct for nokogiri as it was missing a dependency for mini_portile2 and it's hash was not correct. i added an entry for mini_portile2 similar to how racc is setup and added a corresponding entry to gemset.nix.

ran nix-build -A mikutter
updated hashes
ran nix-build again

and that failed while building gtk stuff -- but doing it again just now it built.
however, there are some things in the Gem* files which say x86-64 which seem not good.
also not sure what the stuff in the plugin directory is doing. i removed it and seemed to have no effect.

i just pushed the branch: https://github.com/a-n-n-a-l-e-e/nixpkgs/tree/mikutter
or https://github.com/NixOS/nixpkgs/commit/140513bc4723c9cc0d759671eab51c8bab15c4db might be easier same thing.

Hi @a-n-n-a-l-e-e
Sorry for the late reply. Looks good! :)
I was able to build and start the application with your branch, so I guess it's better to switch to a PR based on your changes instead. I'll close mine.
I don´t really know what the plugin directory does... I guessed that it was there for the "plugin" group specified in the Gem declaration, but if I delete it, nix-build doesn't trigger any changes to the build (and just reuses the cached result). ¯_(ツ)_/¯

i'm not planning on moving forward with my branch -- i only posted it as a reference.

Should I start a PR with these changes in your stead?
If so: Can I assume keeping your commits as-is and linking your work here works for you w.r.t. attribution?

Should I start a PR with these changes in your stead?
If so: Can I assume keeping your commits as-is and linking your work here works for you w.r.t. attribution?

you can take the changes, no attribution is necessary.


Add Xwayland support for drawing only

Add Xwayland support for drawing only.
X clients such as steam and steamvr cannot be rendered yet, so I will create an additional PR for those support.

@Aki-7
I fixed your comments and problems with x-clients such as steamvr.
I would like you to review at this point!
(I will create another PR for task of making x-client window more solid, such as steamvr.)

Looks good! If you can get it fixed a little!


Cody Gray: Watch torello.directory

Cody Gray requests the watch of the watch_keyword torello\.directory. See the MS search here and the Stack Exchange search here.

Approved by Makyen in Charcoal HQ


Fix codecov reports python test

Link the Issue(s) this Pull Request is related to.
Each PR should link at least one issue, in the form:
Fixes #123
Use one line for each Issue. This allows auto-closing the related issue when the fix is merged.
Summarize your change.
Describe the reason for the change.
Add a list of changes, and note any that might need special attention during review.
Reference associated tests.
If no new tests are introduced as part of this PR, note the tests that are providing coverage.

Codecov Report

Merging #1 (e83bf81) into master (aada787) will increase coverage by 2.94%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master       #1      +/-   ##
==========================================
+ Coverage   82.78%   85.73%   +2.94%
==========================================
  Files          75      194     +119
  Lines        3306    19168   +15862
  Branches        0     2118    +2118
==========================================
+ Hits         2737    16433   +13696
- Misses        569     2186    +1617
- Partials        0      549     +549

Flag
Coverage Δ

unittests
85.73% <ø> (+2.94%)
:arrow_up:

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

Impacted Files
Coverage Δ

.../opentimelineio/schema/image_sequence_reference.py
100.00% <0.00%> (ø)

...pentimelineio/opentimelineio/schemadef/__init__.py
100.00% <0.00%> (ø)

tests/test_console.py
93.66% <0.00%> (ø)

tests/test_svg_adapter.py
82.14% <0.00%> (ø)

...ontrib/opentimelineio_contrib/adapters/fcpx_xml.py
91.34% <0.00%> (ø)

tests/baselines/example.py
100.00% <0.00%> (ø)

...y-opentimelineio/opentimelineio/schema/__init__.py
100.00% <0.00%> (ø)

...ntimelineio/opentimelineio/console/otiopluginfo.py
73.04% <0.00%> (ø)

...elineio_contrib/adapters/tests/test_ale_adapter.py
97.70% <0.00%> (ø)

...y-opentimelineio/opentimelineio/console/otiocat.py
93.10% <0.00%> (ø)

... and 109 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 aada787...e83bf81. Read the comment docs.


Patch for #104

Converting JAXBElement objects to Plain Old Java Types
New JAXBElementConverter to support JAXB full processing

Hi Lauri,
What is the progress state of merging this pull-request?
It's becoming too old, don't you think?
It's absolutely tested in our production projects for more than 2 years, what's the problem with?
Thanks!

Hi @josebarragan. The only problem has been my lack of time to look into this, as I would like to understand what I merge and why.
You are absolutely right to point out that this has taken much too long. I will set aside some time next week to read through the issue, the code and do the merge.

Thanks in advance @lauriharpf

@josebarragan, I have went through the pull request. Correct me if I am mistaken, but it appears to fix several JAXB-related mapping problems:

From a JAXBElement field in POJO A to a Foo field in POJO B
From (e.g.) a String field in POJO A to a JAXBElement field in POJO B
Directly from an instance of Foo to an instance of JAXBElement
Plus some degree of Calendar-to-String mapping

Questions
All in all, this looks like a really nice pull request and OK to merge. However, you might be able to clarify some things that are a bit unclear to me. No need to fret about changing anything before the merge unless you want to - I would just like your opinions on the following:
JAXBElementConverter
Convert method
The convert method finds the correct create method from the ObjectFactory. Convert changes the destination class to match the parameter type in the create method. This seems necessary e.g. when mapping XMLGregorianCalendars. I don't understand this, though:
Class<?>[] paramTypes = {destClass};
method = ReflectionUtils.getMethod(factoryClass, methodName, paramTypes);

Why re-search for the method? Removing this part does not break any tests, but is there something I am missing?
Searching for the create method
Since it gets repeated in getBeanId and convert, how would you feel about extracting this to a small helper method? I dumped a draft to PasteBin to illustrate.
XMLGregorianCalendarConverter
You tend to fully qualify class names and use the cast() method instead of the operator. Just a matter of preference or are there underlying reasons for it?
I am tempted to change
 if (java.util.Date.class.isAssignableFrom(sourceClass)) {
     // Date --> XMLGregorianCalendar
     result.setTime(java.util.Date.class.cast(srcObj));
 }

to
if (Date.class.isAssignableFrom(sourceClass)) {
    // Date --> XMLGregorianCalendar
    result.setTime((Date)srcObj);
}

and do the same in other similar situations (in this class and in e.g. MappingProcessor). The latter form is more readable to me.
Thanks for the pull request and for your patience!

Hi @lauriharpf
After review your proposal of change on the JAXBElementConverter class, I think you have a good point.  The original motivation was, granted to get the real method implementation based on real parameters, but it doesn’t really happen at the end, ergo your proposal seems OK for me.
Regarding the use of Object.class.cast(d) instead of (Object)d, is a criteria that I use, in order to use the new java 6 API for this.
Hope I’ve clarified your doubts about it.
Thanks for your effort and patience.
We keep in touch.

Hi,
It doesn't seem that this PR is available on maven (version 5.5.1). Am I correct?
Is it possible to release a new version regarding this feature, please?

Just saw that #101 is going to be released in the next version (5.5.2): https://github.com/DozerMapper/dozer/milestone/6

Hi,
Above mentioned enhancement still not available on maven repo?

https://mvnrepository.com/artifact/net.sf.dozer/dozer/5.5.1


Add 1 0 domain helm charts

Merge the 1.0 style domain helm charts from feature/helm_operator_1_1 branch to develop

Regarding testing, I have done manual testing, as well as passing integration testing both locally and on jenkins, after modifying src/integration-tests/bash/run.sh to use helm charts instead of scripts. The changes to run.sh and cleanup.sh are not being checked into the develop branch, but they were just merged into the operator 1.1 branch.
The README.md was brought over from the old helm charts as well, with some modifications to get them up to date with the values.yaml in the develop branch. It most probably needs more work but it is probably ok as a start.


libcouchbase: tests can't run in parallel

Motivation for this change
70e2b0bef065b1b turned on parallel checking for cmake
by default. This doesn't work for libcouchebase.
cc @Izorkin
closes https://github.com/NixOS/nixpkgs/issues/51837
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Thansk, worked.


rename dca bot to twap https://github.com/VolumeFi/twap_bot_python_script

rename dca bot to twap https://github.com/VolumeFi/twap_bot_python_script
for some reason swap bot is installed as dca_bot needs to be renamed?

Closing as won't ship.


Migrate code and build library

Goals:

Basic tests of the import
Build locally and CI
Remove anything unneeded from build system

Before review/merge:

[ ] Sync C/C++ code with PyBaMM

Not covered in this workpackage:

Configure pre-commit
Using a build system other than nox/setuptools

I have a temporary fix for the linking to casadi, I will replace this as I wrap up the PR

C++ code is synced as of pybamm-team/PyBaMM@62a7ee8bdc2aee2e71a80fd05876b28dc541310d

@MarcBerliner Can you check this branch out and make sure it works locally for you?
Commands:
virtualenv .venv
source .venv/bin/activate
pip install nox
nox

This will trigger a single unit test that just checks if the idaklu module is importable.
Wheels for stand alone tests can be found here.
I also made a branch for removing idaklu from pybamm. I am not going to make a PR for it until pybammsolvers is on pypi so that the CI won't work until the release is done. The branch is here. Since the release is not available yet, you have to install the wheel first.
virtualenv .venv
source .venv/bin/activate
pip install pybammsolvers-0.0.1-<your_arch>.whl
pip install "[.all,dev]"


I followed the INSTALLATION ,after I installed ,I got NotFoundHttpException

Laravel Version: 5.3
Voyager Version: 0.10.5
PHP Version:5.6.15
Database Driver & Version: mysql 5.7.9

Description: after I installed,I opened http://host.com/admin/ , it shows Sorry, the page you are looking for could not be found.
Steps To Reproduce:

Did you installed laravel correctly?

@Jaquedeveloper I'm sure I have installed laravel correctly . I can see laravel welcome page . I also created a test controller , it worked well too.

Try to run php artisan vendor:publish

Please verify that your routes/web.php file contains an line for Voyager::routes();

@Jaquedeveloper @handiwijoyo @fletch3555 I found the problem , because I use homestead for my development environment ,and after I create a new sites , I forget to run vagrant privision . Thank you !


compare bool for inequality

seems odd that we can't do this. if $true != $true { $true }

i tried to change bool to bool but it didn't work - haha!
i guess i could say if $true == $false but that's no fun.

Can I take this one?

@onsah - yup!

@jntrnr Here is the PR. I made the fix but there are some questions because I am not familiar with the project :)


add bindings for keypair_from_seed for authenticated encryption

This PR adds the bindings for keypair_from_seed for libsodium's authenticated encryption (crypto_box_curve25519xsalsa20poly1305).

The rust_sodium crate is no longer maintained by MaidSafe, you should check whether it is actively maintained on Subspace as per the readme, or switch to a modern alternative.


Method to stop animation

I would like to be able to stop an animation. If simply removing the canvas from the DOM, the animation is still running in the background, calculating the frames. Is there a way to stop a specific image animation, or all animations completely?

Thank you, I added APNG.releaseCanvas method in release 2.1.0.


updated data with all of latest veekun updates

Ah interesting, how likely is it that something like this will have to be updated?

Do you mean how likely is it that we would want to update data with the most recent veekun changes? I don't think we would need to do it often. I was just planning on keeping an eye out for anything significant or when new games are released. I just did this because I figured it would be good to launch with everything totally up to date when we're ready.

Do we use the data from veekun without changes (for processing with the build-scripts)?
If yes, why should we have a copy of this data. We could write a script to download the most recent version and than run the build-script on these files.
There would be no probleme with being up to date with the veekun data. You only have to rerun these scripts when there are changes.
These downloads could be big, but why should the data be in this repo if it has no changes to the data from veekun.
As well images why should these in this repo if we have a good source for the images. These files (veekun's csv and the images) are only needed by the server not by the people editing the code. Why not downloading these when needed.
If there are changes in the csv files or no good source for the images why not make a repo for the data?

There are no changes to the csv files. I think this is a fine idea if you want to tackle it. Downloads wouldn't be big. They're just csv files. I actually have a repo set up locally that pulls only those files from veekun's db. As for the images, I personally don't have much opinion one way or the other. I imagine when @phalt started this project his original intention wasn't to invite the open source community in so when he put it up here, he just put it up here.

The csv files are in the repo veekun/pokedex @ pokedex/data/csv/. The buildscript could be writen that you can give it the directory of the csv files (If there is a local copy why redownload. You only have to remember updating the repo copy) and a script to download the files out of the repo into the normal directory.
There would be a little change in the db-build script for those who have/want a local copy of veekuns pokedex and a script to download these files for those who don't want a repo copy. I have to read a little about the structure of github. I think this could be easy to write, but I don't know.
Veekun has some images (http://veekun.com/dex/downloads) but I don't know were they are from and they are only up to gen 5.

It's easy enough to update the data we have here when ever there are significant changes (new release of games usually mean slight stat changes for some pokemon, and new pokemon). I can rebuild the data whenever that happens. :)

@phalt just want to call attention to this one and see if we're in agreement on merging it in. Any reason why we would want to hold off on it?

@zaneadix nope, just had a busy weekend :)


http://<IP_ADDRESS>:8080/api/v2/  HTTP ERROR 404

Environment

OS: win10
Erlang/OTP: V8.3
EMQ: 2.3.11

Description
http://<IP_ADDRESS>:8080/api/v2/  return HTTP ERROR 404
http://localhost:8080/status
Node<EMAIL_ADDRESS>is started
emqttd is running
A description of the issue

Please update your Erlang/OTP to version 20.

emqttd.cmd use emqttd-windows10-v2.3.11\emqttd\erts-8.3\bin\erl.exe the version is  Erlang/OTP 19 [erts-8.3]

I'm not familiar with windows package and I did not advise you to use emqttd on windows. In this situation, maybe you did not use http basic authentication to  do request .  The REST API are protected with HTTP Basic authentication.

Hi, @chao-cn  , Did you read emqttd documentation or api lists on dashboard?
There is no such api called http://<IP_ADDRESS>:8080/api/v2/


PSVR - Each data block contains 2 sets of acc/gyro data

You can decode 2 sets of acc/gyros from the PSVR data, each is time stamped.
See:
https://github.com/mungewell/pyPSVR/blob/master/example1_hidapi/read_hid.py

I have seen this during my original reverse engineering as well, though I found that the second set was identical to the first one, making it quite useless.
Our current tracking is rock solid, so I see no reason to use the second (identical) set.

Even sat stationary on the desk my PSVR gives different values for the 2 slots
=
Time-Slot1: 8484961 499
Gyros: (-10, -4, -1)
Accel: (17073, 175, 3617)
-
Time-Slot2: 8485462 501
Gyros: (-4, -11, 2)
Accel: (17009, 175, 3713)
=
Time-Slot1: 8485962 500
Gyros: (-16, 0, 4)
Accel: (17121, -1, 3745)
-
Time-Slot2: 8486462 500
Gyros: (-2, -2, 5)
Accel: (17057, 63, 3873)
=

Note: Time delta between samples varies slightly, so this should be input to your computation (rather than assumed to be 500us)

Maybe this changed with an early firmware update? My PSVR also sends samples with a rate of 2 kHz, two different samples per report.

It may be that PSVR firmware has changed it's functionality, although I don't believe that they would have dropped/lowered the sampling rate of the Acc/Gyro. Maybe it's related to how the code configures the PSVR for operation. Scripts from the linked project may help.
BTW My PSVR is an early production unit, and has never been connected to a PS4.
ep.write('\x81\x00\xaa\x08\x80\x00\x00\x00\x00\x00\x00\x00')
8000aa30
0a 00 32 01 00 00 00 02 00 00 53 10 4d 50 31 36
4d 50 30 30 36 38 33 30 31 31 36 38 b1 1f 00 00
b1 1f 00 00 24 08 00 00 00 00 00 00 00 00 00 00

@pH5 Is this still worth looking into? IMU is working fine for me at least.

That is still relevant. I'll look into it.

I have added support for the second IMU sample in #164.

#164 is merged into master now.


Global abatement

We use a lot of global variables to hold different assets of the application. We should minimize the number of global variables, either by defining a single global object for the app and then adding properties to that, or by using closure for information hiding, or some other approach.

Resolved with #114.


iOS example support

This is the rebased version of #1418

This is based on branch from #1411
OpenGL, Window and Pong examples now build and run on iOS. As a consequence, previous iOS example is removed. The examples still currently suffer from SFML's iOS implementation though (drawing artifacts, wrong display size, missing HDPI, etc). IMHO all of these points should be addressed in other PRs.
Code for current scope is probably a bit raw though so don't hesitate to comment.
Pong example logic was slightly modified to be able to rely on touch input.
It can be tested both in simulator and on real device (if you have a valid certificate). The generated SFMLConfig should be checked on a desktop platform with static lib (which covers more things). It must remains exactly the same.

This looks fine other than the openGL example, which doesn't render the cube correctly for some reason I can't quite work out. I think all other issues mentioned in OP are fixed now

In the absence of any fix for the openGL example, shall we just remove it on iOS?


Render Blazor components from JavaScript:Set childContent Parameter

I try to set the childContent from JavaScript but it give me error relating to RenderFragment. How we can set Render Fragment Parameter from JavaScript here?
var dialogElem=document.getElementById("dialog");
Blazor.rootComponents.add(dialogElem,"dialog",{title:"Title of Dialog",childContent:`Test sample`});

Thanks for your response

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

ID: 81a32115-33f8-7d06-aaf0-b8ce918b5527
Version Independent ID: 31ad18df-1904-bbdd-cfed-8d0d0267c10e
Content: ASP.NET Core Razor components
Content Source: aspnetcore/blazor/components/index.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @abdollahkahne ... Please ask the product unit on that one at ...
https://github.com/dotnet/aspnetcore/issues
Please add a ...
cc: @guardrex https://github.com/dotnet/AspNetCore.Docs/issues/24648

... to the bottom of your opening comment so that I follow along. I might re-open this for doc work depending on what they say.


Is Imogen dead?

There hasn't been any development in quite some time.
Is this project still active or expected to become active again?
I've been checking for new releases, but nothing seems to have happened for more than a full year now - no commits and no releases.
I'd really love to see Imogen develop, as there isn't really any solid FOSS PBR seamless map generation tool out there, and Imogen seemed to be a very promising project.
Sadly I wasn't ever able to use it due to problems with running it on Linux.

For the weeks coming, I don't think there will be an development on it.
It's a nice project that I love to work on but I'm losing motivation a bit ATM.
I worked a lot of 0.14 version and I'd be sad to get it lost.
So, for now, no news :(

I see. Thanks fro the info.
In the mean time I have found another project that could scratch my itch:
https://github.com/RodZill4/material-maker

you have this one too https://galloscript.itch.io/texgraph/devlog/113538/texgraph-040-performance-update
but i prefer Imogen


Check that<EMAIL_ADDRESS>is working after bumping

Message:
Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16<EMAIL_ADDRESS>

Relevant issues:
https://github.com/stefanzweifel/git-auto-commit-action/issues/246
https://github.com/stefanzweifel/git-auto-commit-action/issues/250


chore(README.md): Add Travis and Coveralls badges + config

Changes Unknown when pulling db3d1bfa9f1d1b65bff3e4fb25d952b7681f70bf on JaKXz:chore/travis-coveralls-badges into ** on rsnara:master**.


[go-rancher] How do I use go-rancher generate the rancher-catalog ?

Rancher versions:
rancher/server: v1.4
rancher/agent: v1.2.2
Hi ：
I would like to ask how to use go-rancher generate the rancher-catalog and add it to rancher?
I did not find any test sample or example in the project

if your have some guide-doc or example ,Can you tell me where I can see it?

Thanks for your help~

@LanceNero go-rancher is a Go library for accessing Rancher REST API. I don't understand what you are trying to achieve? Did you mean you want to add your own catalog using the library calls?

@leodotcloud
Yes , I want use go-rancher to add some catalog ,  but i didn't know how use the library
After that, I found some code for use this library in other project , and  I can refer to these code to use the library.

https://github.com/hashicorp/terraform/tree/v0.9.6/builtin/providers/rancher
https://github.com/rancher/cli/tree/master/cmd

Thanks for you reply. :)


Contribute CohortsWidget

Overview
Description of changes
We have a ModelOptionsWidget, and a ModelOptionsAndCohortsWidget. This PR is to contribute the difference of the two widgets.
Author Checklist

[ ] Linting passes; run early with pre-commit hook.
[ ] Tests added for new code and issue being fixed.
[ ] Added type annotations and full numpy-style docstrings for new methods.
[ ] Draft your news fragment in new changelog/ISSUE.TYPE.rst files; see changelog/README.md.

Is there a reason why you are looking to add this particular widget?
It looks like you don't have any exploration controls that use the widget, which is confusing.
It also looks like you add any unit tests for the new widget since you only changed one file.

Include din #82