Plugins

Hi Tyler,
First I'd like to thank you for your contribution as this is the best editor I've seen. I just purchased Redactor v10.0.6 and installed your latest version with angular 1.3.5. After working with this the past 2 days, I think the following might help others getting started with some of the advanced features.

I've got all my libs loaded (download plugins)
'bower_components/redactor/redactor.js',
'bower_components/redactor/table.js',
'bower_components/redactor/fullscreen.js',
'bower_components/redactor/video.js',
'bower_components/redactor/clips.js',
'bower_components/redactor/imagemanager.js',
'bower_components/angular-redactor/angular-redactor.js',

added to app.js angular.module('sailng', [...  ,'angular-redactor']...

added to to app.js
.config(function(redactorOptions) {
redactorOptions.imageUpload = '/upload';
redactorOptions.focus = true;
redactorOptions.enterKey = true;
redactorOptions.linebreaks = true;
redactorOptions.pastePlainText = false;
redactorOptions.buttonSource = true;
redactorOptions.imageResizable = true;
redactorOptions.imageEditable = true;
redactorOptions.imageLink = true;
redactorOptions.visual = true;// flase for html mode
 redactorOptions.plugins = ['table','fullscreen','video','imagemanager'];
 redactorOptions.buttons =   ['html', 'formatting', 'bold', 'italic', 'deleted',
     'unorderedlist', 'orderedlist', 'outdent', 'indent',
      'image',     'video', 'file','table', 'link', 'alignment', 'horizontalrule','fullscreen','clips']

})
While the upload feature is a bit ticky and requires a good read of documnetation, everything works as expected except
The enterKey does not execute crlf when in a table.
Thanks,
John

Hi +john Where solve the Snippets pass or set the Snippets list to clip plugin

@johntom I think what @carlosCeron  is trying to say is have you included the .js files for the plugins to your html page?

Sorry, a bit confused, that's why I referrenced them as 'bower_components/redactor/redactor.js'...
I place all libs in a grunt/pipeline.js file (see co-authored repo https://github.com/SharePointOscar/MEANS).


Improve Usage Docs

Added all the available methods for usage. Previously, user had to inspect the code to get an idea. Now, the READMe makes it very clear.

Amazing!
Thank you for taking the time to do this!
Cheers, Fede.


Feature request: Support Middy 5.x

Use case
This feature request is about an upcoming official support of Middy 5.x.
The current Powertools version 1.18.0 officially supports Middy up until version 3, as described in the documentation.
Support for Middy v4 is expected to be launched soon as part of the upcoming major release 2.x.
If and when Middy v5 will be officially supported, it would be good to guide developers on what changes they need to implement in their codebase to successfully leverage the Logger utility together with Middy v5.
Solution/User Experience
Upgrading to Middy v5 may have a significant impact on the codebase and developer experience.
See Middy's documentation for more info.
Alternative solutions
No response
Acknowledgment

[X] This feature request meets Powertools for AWS Lambda (TypeScript) Tenets
[ ] Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers
Please react with 👍 and your use case to help us understand customer demand.

Hi @saragerion thank you for opening this issue.
At the moment we don't have concrete plans for officially supporting Middy.js v5, however when the time comes I expect there will be challenges due to Powertools supporting both CJS and ESM and Middy.js having dropped support for the former in their v5 major version.
According to our versioning policy we are committed to supporting all current AWS Lambda managed runtimes, which at the time of writing are the ones corresponding to Node.js 16 through Node.js 20.
On Middy.js side, their release cadence aligns more closely with the Node.js LTS policy. This means that v5 dropped support for Node.js 16.
For the time being, I'd suggest customers to stick with v4 if they're using mainly the @middy/core module (the only one required by Powertools' middlewares), as suggested by Middy.js own maintainer.
With this in mind, and according to the latest info publicly available on the AWS Lambda Runtime versioning policy, the earliest we can consider support for Middy.js 5x is going to be late Q2/early Q3, which is when we're expected to also drop support for Node.js 16.
I'm going to mark this as an item to revisit in the next quarter, but it would be useful for us to have customers interested in the feature react with a 👍 to this issue as this will help us understand demand.

In the next release we are going to drop support for Node.js 16, which means we can now look into extending support to Middy.js v5.x.
Based on the reactions to my last message above, there seems to be significant interest in us adding support to Middy.js 5.x despite it dropping support for CJS.
I have already started testing some of our utilities with the newer version in some samples & demos, but before officially adding support we'll need to look into adding the version to our test matrix.

As mentioned in the issue you've opened on middyjs/middy/#1208, this is most likely happening because you're transpiling your TypeScript code to CommonJS while Middy.js 5.x only supports ESM.
As the stack trace suggests, the root cause of the issue is Middy.js and not Powertools for AWS, nor AWS Lambda itself.
Without knowing how you are transpiling or bundling your code, I can't make any specific suggestions, but if you are using CDK like shared in the other issue, then you need to instruct esbuild to actually output ESM - we have an example of this in the repo.
If this is still an issue and either 1/ you are sure that are using ESM but it still doesn't work, or 2/ would like Middy.js to support CJS, I would suggest to follow up with them on their repo.


Structured Field Values for HTTP

One to watch - https://www.rfc-editor.org/info/rfc8941?s=03
No urgent demand here, but can help us be opinionated on sending correct requests.

Hi, I am willing to contribute on this. Do you mind elaborating on this issue?

We are not looking for external contributions here, thanks for the offer.

https://github.com/undef1nd/sfv rust impl


add python coderz doc

Hey there, thanks for your contribution, I've looked into the resource you're trying to add, and it's basically a book!
so it is better to put that under the Book section rather than creating a new one for documents.
Regards.

Hi, I agree with @IHosseini083, It's a book, and please add it inside the book section and commit again, so we can merge.
Thanks for your contribution.


chore(main): release 1.5.0

:robot: I have created a release beep boop
1.5.0 (2024-09-30)
Features

add goji (6c39c1d)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/sanriodev/blvckleg.dev/releases/tag/v1.5.0 :sunflower:


how can I use Chinese language sentiment analysis

am trying to do sentiment analysis for Chinese language. it's not working properly. I added training data also it's not working

Hello Rajesh, i have a problem like you, i want to sentiment analysis for portuguese language. I solved the problem tranlating the tweet in portugues (i´m was checking the analysis of some hashtag), to english and use the translation on sentiment analysis.

TextBlob's default sentiment analyzer only supports English at the moment. I recommend using @NewtonGaliza 's workaround: translate to English before analyzing.


rustup for import changes

@bors r+

:pushpin: Commit 9f3383d55d99635a38c5406f60d16c478534d9f6 has been approved by RalfJung

:hourglass: Testing commit 9f3383d55d99635a38c5406f60d16c478534d9f6 with merge 147ea8f400de3ca529abcb5eb7b65f84a4896ae9...

Third rustup on one day, that could be a new record.^^

:sunny: Test successful - checks-travis, status-appveyor
Approved by: RalfJung
Pushing 147ea8f400de3ca529abcb5eb7b65f84a4896ae9 to master...


Labeling Candidates in the Viewer

Hello,
I labeled candidates in the viewer but cannot access it. In third tutorial, it says use annotator's name as the AnnotationKey.

Even though I labeled the candidates in the viewer, the resultant matrix of labeled instances is empty.
Am I accessing labels wrong?
Appreciate any info.
Best regards,
Nurzat

Hi @NurzatRakhman, sorry for the delayed response!  It seems like you're putting in "AnnotationKey" as your annotator name; instead you should use the username for yourself when you made annotations.
By default this will use your username (as returned by getpass.getuser(), see https://github.com/HazyResearch/snorkel/blob/master/snorkel/viewer.py#L57), however you can also explicitly pass in an annotator user name when you call sentence viewer, e.g.
sv = SentenceNgramViewer(dev_cands, session, annotator_name='Bob')

Thanks Alex,
sorry for delayed response, it is working  :)
Best regards,
Nurzat

Great!
On Mon, Apr 10, 2017 at 12:27 AM Nurzat<EMAIL_ADDRESS>wrote:

Thanks Alex,
sorry for delayed response, it is working :)
Best regards,
Nurzat
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/HazyResearch/snorkel/issues/584#issuecomment-292870407,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABgw_dYu_3RvPRw6JuntMCERPDSU44iKks5rudnlgaJpZM4MqeeA
.


What is the project accuracy?

Hello schollz, would you mind to tell me how accurate your indoor location can be? My indoor project uses knn and naive bayes algorithm too, the acuracy is about 2 meters. I forked your project and checked your csv test data file, it seems your position unit is for large space, such as an office, or a room. But I collect  training data by blocks (1 to 2 meters), so I would like to know what your accuracy is, that will be helpful to me.Thanks.

https://www.internalpositioning.com/doc/faq.md#minimum


The results are worse than original 3DGS on static street scene.

Hello, thanks for the efforts to implement this paper. However, I find the results are even worse than the original 3D-GS. I don't know if there some errors in my settings.
Original 3DGS:

VastGaussian:

I follow the TJ Manhattan Alignment, and here is the intermediate regions splits:

I follow the original partition settings(m = 3, n = 3)
python train_vast.py -s {path/to/data} —exp_name test --manhattan --platform tj --pos "0 0 0" --rot "0 0 0"
I use TJ to do Manhattan alignment, and the original pcd's ground is already perpendicular to y-axis.


Reactive support

Hello,
Does make cense some reactive support here or not?
I'm just thinking about using spring-data-mapdb in reactive spring-webflux apps and avoid Mono/Flux wrapper services...
Thanks

Regards

Hello Maksim, sorry for late response.
I think it's totally worth the try. Reactive Spring repositories is what I was looking at but have no chance to addopt yet. If you want to give it a try please feel free to fork.
Regards Pavel.

Understand. Thanks for feedback.


v4/v5: Row columns for responsive card decks and more

Overview
Trying to find a new way to do responsive card decks while not locking ourselves into more card classes. My thinking here is we can easily control the column (.col) width by the parent with responsive .row-cols-* classes, but I don't know how many we need (have 0-5 now).

Column

Column

Column

Column

Column

/cc @twbs/css-review
How it works
We can add a default number of columns to support (thinking a max of 6). You can override this if you like, but otherwise we'll loop over it and generate the responsive classes.
Here's a simplified example with out the responsive infixes. See it in action via Sassmeister.
$row-columns: 6 !default;

@for $i from 1 through $row-columns {
  .row-cols-#{$i} > [class^="col"] {
    flex: 0 0 calc(100% / #{$i});
  }
}

Screenshots
Some screenshots to show how it's shaping up for grid columns and cards.

And here's how it could work with some Sass mixins: https://www.sassmeister.com/gist/1a567b85b0c7c5a837e9b65be6220688.

This is ready for review @twbs/css-review.

I don't see the benefit of this. We can just use the grid for this scenario.

I don't see the benefit of this. We can just use the grid for this.

This would be really helpful when you're pulling a dynamic list and unable to change the grid markup each time. Having it on the parent class would make it "set it and forget it".

Could we have these classes responsive with breakpoints that way we can have 1 column stacked on mobile and multiple columns on desktop?
row-cols-1 row-cols-md-3

Could we have these classes responsive with breakpoints that way we can have 1 column stacked on mobile and multiple columns on desktop?

Yup, that's the intent of the changes here: https://github.com/twbs/bootstrap/pull/29073/files#diff-f6ca44772c5cdca97cf5be7357416fb8.

Rebased

Ok, I think this can come in handy in some situations, but the current implementation needs some fine tuning:

The [class^="col"] doesn't really make sense. You can use whatever col class you want, but the implementation is always overridden by the .row-cols-* class?
We don't use the calc() notation in our grid cols, so it might also be better to use percentage() here (or use calc() in both places)

The [class^="col"] doesn't really make sense. You can use whatever col class you want, but the implementation is always overridden by the .row-cols-* class?
We don't use the calc() notation in our grid cols, so it might also be better to use percentage() here (or use calc() in both places)

Made an alternative implementation draft of this in https://github.com/twbs/bootstrap/pull/29274 which solves these issues

Should we close this @mdo in favor of #29274?

@XhmikosR I want to comment, so please leave this. (but sorry, I don't have time today...)

The difference between this PR and #29274 is the need for .col class and whether the .col- class can override the default width.
I support the @mdo proposal which requires .col class. Because, Bootstrap's grid system has the rule:

In a grid layout, content must be placed within columns and only columns may be immediate children of rows.
https://deploy-preview-29073--twbs-bootstrap.netlify.com/docs/4.3/layout/grid/#how-it-works

If this traditional rule changes, it will confuse the many user.
This PR can not overriding the default width because of the CSS priority, but this can be fixed by changing the definition order.
I created #29317 for clarify the diff.

Is this ready from all of you @twbs/css-review?

Since we (@mdo, @ysds and me) all agreed on https://github.com/twbs/bootstrap/pull/29317, I assume it is

It is better to add a responsive examples on the grid page :)

@ysds can you do it please?

done!

@mdo please have a final look and hit rebase and merge if it LGTY, thanks!

This needs to be backported manually in my v4-dev-xmr branch.
I'll have another try again later, but it conflicts a lot. Also note that we need to make sure we don't use Hugo-related stuff in v4, like placeholder, docsref and example.


Gem::ConflictError net-ssh-4.1.0

Since upgrading to the latest chefDK, I've started receiving this error on latest MacOS. Does anyone knows what could be the problem?
$ knife solo -v
/opt/chefdk/embedded/lib/ruby/site_ruby/2.3.0/rubygems/specification.rb:2288:in `raise_if_conflicts': Unable to activate knife-solo-0.6.0, because net-ssh-4.1.0 conflicts with net-ssh (< 4.0, >= 2.7) (Gem::ConflictError)
	from /opt/chefdk/embedded/lib/ruby/site_ruby/2.3.0/rubygems/specification.rb:1408:in `activate'
	from /opt/chefdk/embedded/lib/ruby/site_ruby/2.3.0/rubygems.rb:220:in `rescue in try_activate'
	from /opt/chefdk/embedded/lib/ruby/site_ruby/2.3.0/rubygems.rb:213:in `try_activate'
	from /opt/chefdk/embedded/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:126:in `rescue in require'
	from /opt/chefdk/embedded/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:40:in `require'
	from /Users/user/.chefdk/gem/ruby/2.3.0/gems/knife-solo-0.6.0/lib/chef/knife/cook.rb:1:in `<top (required)>'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-12.21.2/lib/chef/knife/core/subcommand_loader.rb:100:in `load'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-12.21.2/lib/chef/knife/core/subcommand_loader.rb:100:in `block in load_commands'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-12.21.2/lib/chef/knife/core/subcommand_loader.rb:100:in `each'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-12.21.2/lib/chef/knife/core/subcommand_loader.rb:100:in `load_commands'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-12.21.2/lib/chef/knife/core/subcommand_loader.rb:110:in `load_command'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-12.21.2/lib/chef/knife/core/subcommand_loader.rb:124:in `command_class_from'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-12.21.2/lib/chef/knife.rb:153:in `subcommand_class_from'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-12.21.2/lib/chef/knife.rb:214:in `run'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-12.21.2/lib/chef/application/knife.rb:156:in `run'
	from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-12.21.2/bin/knife:25:in `<top (required)>'
	from /opt/chefdk/bin/knife:57:in `load'
	from /opt/chefdk/bin/knife:57:in `<main>'

chef -v
Chef Development Kit Version: 1.5.0
chef-client version: 12.21.2
delivery version: master (17c1b0fed9be4c70f69091a6d21a4cbf0df60a23)
berks version: 5.6.4
kitchen version: 1.16.0
inspec version: 1.25.1

I'd install the 0.7.0 pre-release. That should have compatible gem requirements.

@matschaffer you are right chef gem install knife-solo -v 0.7.0.pre did the trick.


Use async_get instead of async_get_registry for entity registry

Which Model do you use from loxone? Miniserver? Gen1 or Gen2?
Gen2
Which software version does your loxone use?
0.3.10
How did you install HomeAssistant? Over Hassio oder manual install?
Home Assistant OS on Proxmox
Which Version do you use of HomeAssistant?
2022.6
Describe the bug
A clear and concise description of what the bug is.
See error log below
Paste the error log with the following settings:
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:103
First occurred: 07:39:18 (3 occurrences)
Last logged: 07:39:46

Detected integration that uses deprecated `async_get_registry` to access device registry, use async_get instead.
Please report issue to the custom component author for loxone using this method at
custom_components/loxone/miniserver.py, line 181: device_registry = await self.hass.helpers.device_registry.async_get_registry()

@elRadix thanks for your hint. I fixed it in the newest version.


option to disable internal thread pool

Is your feature request related to a problem? Please describe.
in high load multi-user applications using internal thread pool for each rdp instance is suboptimal
Describe the solution you'd like
thread pool created inside libfreerdp/codec/rfx.c in RFX_CONTEXT* rfx_context_new(BOOL encoder) function and already have option to disable it.
this optioin need to be accessible via rdpSettings or any other api exported to end user.
Additional context
here is quicj and dirty patch to hard disable thread pool
diff --git a/libfreerdp/codec/rfx.c b/libfreerdp/codec/rfx.c
index b7b08738d..64ae36bf5 100644
--- a/libfreerdp/codec/rfx.c
+++ b/libfreerdp/codec/rfx.c
@@ -262,7 +262,7 @@ RFX_CONTEXT* rfx_context_new(BOOL encoder)
        if (!priv->BufferPool)
                goto error_BufferPool;

-#ifdef _WIN32
+/*#ifdef _WIN32
        {
                BOOL isVistaOrLater;
                OSVERSIONINFOA verinfo;
@@ -275,7 +275,8 @@ RFX_CONTEXT* rfx_context_new(BOOL encoder)
        }
 #else
        priv->UseThreads = TRUE;
-#endif
+#endif */
+       priv->UseThreads = FALSE;
        GetNativeSystemInfo(&sysinfo);
        priv->MinThreadCount = sysinfo.dwNumberOfProcessors;
        priv->MaxThreadCount = 0;

Pull requests welcome

Ok, just had a look at the code, thread pool can already be configured. Just set your desired number of threads and you're done.


jupyter notebook latex math equations render error

environment
vscode 1.44.2
vscode-python-ext: 2020.4.76186
recurrent

make a blank ipynb file
paste the following code as markdown into the first cell

$$ \text{For } x \in \mathbb{R}^n \text{,     } sigmoid(x) = sigmoid\begin{pmatrix}
x_1  \
x_2  \
...  \
x_n  \
\end{pmatrix} = \begin{pmatrix}
\frac{1}{1+e^{-x_1}}  \
\frac{1}{1+e^{-x_2}}  \
...  \
\frac{1}{1+e^{-x_n}}  \
\end{pmatrix}\tag{1} $$

the result cannot be displayed properly. but the result is displayed correctly in the other markdown
I tried to delete all the carriage returns and it displayed correctly.

$$ \text{For } x \in \mathbb{R}^n \text{,     } sigmoid(x) = sigmoid\begin{pmatrix}    x_1  \    x_2  \    ...  \    x_n  \\end{pmatrix} = \begin{pmatrix}    \frac{1}{1+e^{-x_1}}  \    \frac{1}{1+e^{-x_2}}  \    ...  \    \frac{1}{1+e^{-x_n}}  \\end{pmatrix}\tag{1} $$

This now appears to render properly using native notebooks with VS Code 1.60


Not able to to generate "additionalProperties" property in swagger using cadl.

We have a swagger spec where we specify "additionalProperties": true in the model so user can add not defined properties as part of the model.
Example:
    "ModelProperties": {
      "description": "Model properties",
      "type": "object",
      "additionalProperties": true,   // additional properties flag
      "properties": {
        "provisioningState": {
          "readOnly": true,
          "$ref": "global.json#/definitions/ProvisioningState",
          "description": "Provisioning state  at the time the operation was called"
        }
      },
    },

And the generated client model code in go using autorest looks like below:
type ModelProperties struct {
	// OPTIONAL; Contains additional key/value pairs not defined in the schema.
	AdditionalProperties map[string]interface{}

	ProvisioningState *ProvisioningState `json:"provisioningState,omitempty" azure:"ro"`
}

with the default case in UnmarshalJSON funtion to add the not defined properties in AdditionalProperties map. i.e
func (e *ModelProperties) UnmarshalJSON(data []byte) error {
	var rawMsg map[string]json.RawMessage
	if err := json.Unmarshal(data, &rawMsg); err != nil {
		return fmt.Errorf("unmarshalling type %T: %v", e, err)
	}
	for key, val := range rawMsg {
		var err error
		switch key {
		case "provisioningState":
				err = unpopulate(val, "ProvisioningState", &e.ProvisioningState)
				delete(rawMsg, key)
		default:
			if e.AdditionalProperties == nil {
				e.AdditionalProperties = map[string]interface{}{}
			}
			if val != nil {
				var aux interface{}
				err = json.Unmarshal(val, &aux)
				e.AdditionalProperties[key] = aux
			}
			delete(rawMsg, key)
		}
		if err != nil {
			return fmt.Errorf("unmarshalling type %T: %v", e, err)
		}
	}
	return nil
}

But i couldn't find a way to have a similar functionality using cadl. I have tried using Record, when client code is generated I can see it create a map but not the default case in the UnmarshalJson.
I was hoping to have something like @AdditionalProperties annotation on the mode which would generate "additionalProperties" flag on the object in swagger, or is there any other way to achieve the same functionality?
Playground Link

Related to #763
You would actually want to require a constrained map, like string -> string for additional properties, I think, rather than just allowing additional properties of any type.

Fix tracked in #1590


[DO NOT MERGE] Change how GA4 index parameter works

What
Changes how the index parameter is handled, from being a string of the form 1.2.3 or 2.1 to an object with sub-parameters.
This is handled by a function in ga4-core.js. Trackers that could receive an index parameter are also modified in this PR to call the function. This means that we can automatically update our index data without having to change all the places in applications where index is declared. The function is written so that if we decided to switch an application to pass the correct index parameter, it shouldn't cause a problem - so if we wanted to later update all our applications to pass the correct data in the first place, we could do that.
The ecommerce tracker has not been modified as the index parameter works differently there.
Why
The data structure is being changed to help analysts understand the data more easily. This will involve future work to fix existing instances of the index not being quite right, and to add a third sub-parameter to this object.
This is being handled centrally in the gem code to avoid having to change all the existing instances of how index is handled across applications.
Visual Changes
None.
Trello card: https://trello.com/c/8tNN5gGX/426-change-the-index-parameter

@JamesCGDS @AshGDS thanks for your feedback and help on this, have now amended the ga4-core.js code to fix the identified problem 👍

Will you be fixing the breadcrumbs index in this PR, or will this be done in a separate PR?
Will the index functionality be documented anywhere?

Of course, I'd forgotten that the breadcrumbs stuff is here! Yes, will definitely do that.
And yes, documentation is also a good idea. Will check.

Thanks @andysellick - for reference, here's the breadcrumb code: https://github.com/alphagov/govuk_publishing_components/blob/ca68f50ea4641f2f09f23d3e83b51ec19d970efc/lib/govuk_publishing_components/presenters/breadcrumbs.rb#L61

@AshGDS have updated the breadcrumb tracking as suggested, thanks for that. I had a look at the documentation but aside from updating what's already there I'm not sure I want to add anything specific for the new index parameters - that feels like something more suitable for the implementation guide/record. Also I'm hoping that eventually we can phase out the need for this code, by updating GA4 tracking data in applications when there's time and opportunity to do so. Does all that sound okay or do you have a specific thing you think we should be documenting here?


Design and implementation of phase 02

Subtask of https://github.com/ballerina-platform/ballerina-standard-library/issues/1057
Add leap seconds and time zone supports.

In the second phase, we can implement the following APIs according to the initial design. @daneshk FYI.
// Time zones

type Zone readonly & object {
  // if always at a fixed offset from Utc, then this
  // function returns it; otherwise nil
  function fixedOffset() returns ZoneOffset?;
  // this does not pay attention to timeZoneOffset nor dayOfWeek
  // it does pay attention to utc
  function utcFromCivil(Civil civilTime) returns Utc|Error;
  function utcToCivil(Utc utc) returns Civil;
};

final Zone systemZone = check loadSystemZone();

// Get a time zone from Ballerina's internal database
// of time zones.
// id is  of form "Continent/City"
function getZone(string id) returns Zone?;

The design phase 02 in this doc mentioned that,
  // this does not pay attention to timeZoneOffset nor dayOfWeek
  // it does pay attention to utc
  function utcFromCivil(Civil civilTime) returns Utc|Error;

Should this be rephrased as it does pay attention to time zone?.
And why we don't need to return an error from the getZone like we did in loadSystemZone. @jclark @daneshk

The design phase 02 in this doc mentioned that,
  // this does not pay attention to timeZoneOffset nor dayOfWeek
  // it does pay attention to utc
  function utcFromCivil(Civil civilTime) returns Utc|Error;

Should this be rephrased as it does pay attention to time zone?.

Yes, It does pay attention to the time zone, not for the timeZoneOffset in the Civil record passed as input.

And why we don't need to return an error from the getZone like we did in loadSystemZone.

IMO, the getZone method is similar to maps where we have zone ids as keys and Zone as values. nonexistent entries should return nil rather than errors similar to maps. On the other hand, the loadSystemZone method should always return value unless there is a system error which is okay to return an error.


Don't send null name and type fields for UpdateChannel route

Finally figured out what was causing #149. Wew.
The docs state that the name and type fields can't be null, so this PR prevents the fields from serializing as such if they are not set.

##[warning]GitHub Actions are not allowed to create Check annotations, when executed for a forked repos. See https://github.com/actions-rs/clippy-check/issues/2 for details.
Posting clippy checks here instead.
error: this seems like a manual implementation of the non-exhaustive pattern
  --> command-parser/src/parser.rs:5:1
   |
5  |   pub struct Command<'a> {
   |   ^---------------------
   |   |
   |  _help: add the attribute: `#[non_exhaustive] pub struct Command<'a>`
   | |
6  | |     /// A lazy iterator of command arguments. Refer to its documentation on
7  | |     /// how to use it.
8  | |     pub arguments: Arguments<'a>,
...  |
13 | |     __nonexhaustive: (),
14 | | }
   | |_^
   |
note: the lint level is defined here
  --> command-parser/src/lib.rs:65:5
   |
65 |     clippy::all,
   |     ^^^^^^^^^^^
 note: the lint level is defined here
  --> command-parser/src/lib.rs:65:5
   |
65 |     clippy::all,
   |     ^^^^^^^^^^^
   = note: `#[deny(clippy::manual_non_exhaustive)]` implied by `#[deny(clippy::all)]`
help: remove this field
  --> command-parser/src/parser.rs:13:5
   |
13 |     __nonexhaustive: (),
   |     ^^^^^^^^^^^^^^^^^^^
   = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_non_exhaustive

##[error]Exiting due to clippy errors

Uh... CI failure looks unrelated to this change?

The clippy issue is unrelated to your code so I will just merge it anyways.
@Arzte maybe we should keep clippy as optional, at least if we use the nightly version.

Thanks for the investigating and fix 😄


Changelog generation

Update/generate CHANGELOG for each crate.
We could use a library that given the list of commits (and the current changelog?), generates the new changelog.
Available libraries:

git-cliff

We could use git-cliff-core like this to build the changelog entries of the commits we found.
If there is not changelog yet, we also generate the header, otherwise we can insert the generated text under the [Unreleased] section.


Add dedicated Arguments type

This will make type-checking easier later.
This PR builds on #85.

@jwodder might need to rebase this one, unless rebase and merge is smart enough to only include the last commit

well nevermind, rebase and merge is smart!


[SwiftDemangle] NFC: Increase portability via C standard APIs

Not every Linux distribution has the libbsd package installed.

@swift-ci please test and merge


Customize Event Popper

Hi and thanks for the great work.
I wonder if it would be possible to fully customize the Event Popper (the view that appears if you click on an event).
At the moment, the only option is to add content via ViewerExtraComponent.
Concretely, I would like to have an additional button next to edit and delete.
Thanks in advance and BR
Chris

Hi
Unfortunately this is not possible with the current setup.
Hopefully will do make it possible in future releases.


Media > GIF link broken

Seems like it was deleted. @ibaaj do you have a recent copy which someone else can put back online?

Ok, if you wouldn't like to continue the project I've created a replacement repository with the content you provided: https://github.com/davisonio/awesome-gif.

@davisonio perfect!

Fixed in https://github.com/sindresorhus/awesome/commit/8617b899d8254963cdbe537a6f4c60cb6b7f57de ❤


Final Number of Locations (Complete) = 0 in PreTest

Bug description
When I run the pre-test code I end up with a correct number of Raw locations and time periods but the final number of locations (complete) = 0.
##################################
Summary
##################################

Raw Number of Locations: 11
Time Periods: 795
Final Number of Locations (Complete): 0

I am then unable to progress further with the head() or GeoPlot() functions.
Session information
Please paste the output after running sessionInfo() in your R session.
R version 4.2.1 (2022-06-23 ucrt)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows 10 x64 (build 22000)
Matrix products: default
locale:
[1] LC_COLLATE=English_United Kingdom.utf8  LC_CTYPE=English_United Kingdom.utf8
[3] LC_MONETARY=English_United Kingdom.utf8 LC_NUMERIC=C
[5] LC_TIME=English_United Kingdom.utf8
attached base packages:
[1] tools     stats     graphics  grDevices utils     datasets  methods   base
other attached packages:
[1] GeoLift_2.4.32 augsynth_0.2.0 remotes_2.4.2
loaded via a namespace (and not attached):
[1] ggrepel_0.9.1          Rcpp_1.0.9             mvtnorm_1.1-3          lattice_0.20-45
[5] tidyr_1.2.0            listenv_0.8.0          zoo_1.8-10             assertthat_0.2.1
[9] digest_0.6.29          foreach_1.5.2          utf8_1.2.2             parallelly_1.32.1
[13] lfe_2.8-8              R6_2.5.1               plyr_1.8.7             Boom_0.9.10
[17] ggplot2_3.3.6          pillar_1.8.0           panelView_1.1.9        rlang_1.0.2
[21] rstudioapi_0.13        Matrix_1.4-1           labeling_0.4.2         stringr_1.4.0
[25] BoomSpikeSlab_1.2.5    directlabels_2021.1.13 munsell_0.5.0          proxy_0.4-27
[29] compiler_4.2.1         pkgconfig_2.0.3        globals_0.15.1         htmltools_0.5.2
[33] CausalImpact_1.2.7     tidyselect_1.1.2       gridExtra_2.3          tibble_3.1.7
[37] quadprog_1.5-8         dtw_1.22-3             codetools_0.2-18       fansi_1.0.3
[41] future_1.27.0          crayon_1.5.1           dplyr_1.0.9            MASS_7.3-57
[45] grid_4.2.1             gsynth_1.2.1           xtable_1.8-4           gtable_0.3.0
[49] lifecycle_1.0.1        magrittr_2.0.3         scales_1.2.0           cli_3.3.0
[53] stringi_1.7.6          farver_2.1.1           reshape2_1.4.4         doRNG_1.8.2
[57] ggthemes_4.2.4         doParallel_1.0.17      ellipsis_0.3.2         xts_0.12.1
[61] generics_0.1.3         vctrs_0.4.1            sandwich_3.0-2         Formula_1.2-4
[65] iterators_1.0.14       glue_1.6.2             purrr_0.3.4            rngtools_1.5.2
[69] MarketMatching_1.2.0   abind_1.4-5            parallel_4.2.1         fastmap_1.1.0
[73] colorspace_2.0-3       LowRankQP_1.0.5        bsts_0.9.8
Reproduction steps
Enter steps to reproduce the behavior.
Expected behavior
I expected the locations complete to be greater than 0.
Output goes here

Additional context
Add any other context about the problem here. (like proxy settings, network setup, overall goals, etc.)

Hi @zig-and-zag, thanks for reaching out to us!
This is almost definitely caused by missing in the data-set. These missing values could be explicit (a time-location combination having a value of NA) or simply a missing date. We'd like to make sure that if a time-location combination doesn't have a value, we specify that explicitly with a 0.

Hi Arturo,
All solved, thanks very much for your quick response.
Thanks
Andy
On Wed, Aug 3, 2022 at 4:04 PM Arturo Esquerra @.***>
wrote:

Hi @zig-and-zag https://github.com/zig-and-zag, thanks for reaching out
to us!
This is almost definitely caused by missing data in the data-set. These
missing values could be explicit (a time-location combination having a
value of NA) or simply a missing date. We'd like to make sure that if a
time-location combination doesn't have a value, we specify that explicitly
with a 0.
—
Reply to this email directly, view it on GitHub
https://github.com/facebookincubator/GeoLift/issues/108#issuecomment-1204069918,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2LGTF2LLC5B2674H3KZFH3VXKC63ANCNFSM55NSWNRA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
ANDREW FOOTE
Partner - Zebra Associates
07732 822622
@.***

Hi Arturo,
I am getting an error when running geolift:
Error in dplyr::mutate():
! Problem while computing significant = ifelse(pvalue < alpha, 1, 0).
Caused by error in ifelse():
! object 'pvalue' not found
For the below code, do you happen to have any ideas?
Many thanks
Andy
MarketSelections <- GeoLiftMarketSelection(data = GeoTestData_PreTest,
treatment_periods = c(90),
N = c(12),
Y_id = "Y",
location_id = "location",
time_id = "time",
effect_size = seq(0, 0.15, 0.01),
lookback_window = 1,
include_markets = c("Bradford",
"Darlington", "Doncaster", "Halifax", "Harrogate", "Huddersfield", "Hull",
"Lancaster", "Leeds", "Sheffield", "Wakefield", "York"),
exclude_markets =
c("Birmingham", "Bristol", "Chelmsford", "Coventry", "Guildford", "Kingston
upon Thames", "Manchester", "Rochester", "Milton Keynes", "Newcastle upon
Tyne", "Nottingham", "Portsmouth", "Reading", "Redhill", "South East
London", "Stockport", "Stoke-on-Trent", "South West London", "Tonbridge",
"Wigan"),
holdout = c(),
cpic = 1,
alpha = 0.1,
Correlations = TRUE,
fixed_effects = FALSE)
On Thu, Aug 4, 2022 at 11:39 AM Andy Foote @.***>
wrote:

Hi Arturo,
All solved, thanks very much for your quick response.
Thanks
Andy
On Wed, Aug 3, 2022 at 4:04 PM Arturo Esquerra @.***>
wrote:

Hi @zig-and-zag https://github.com/zig-and-zag, thanks for reaching
out to us!
This is almost definitely caused by missing data in the data-set. These
missing values could be explicit (a time-location combination having a
value of NA) or simply a missing date. We'd like to make sure that if a
time-location combination doesn't have a value, we specify that explicitly
with a 0.
—
Reply to this email directly, view it on GitHub
https://github.com/facebookincubator/GeoLift/issues/108#issuecomment-1204069918,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2LGTF2LLC5B2674H3KZFH3VXKC63ANCNFSM55NSWNRA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
ANDREW FOOTE
Partner - Zebra Associates
07732 822622
@.***

--
ANDREW FOOTE
Partner - Zebra Associates
07732 822622
@.***

Hi Arturo, I am getting an error when running geolift: Error in dplyr::mutate(): ! Problem while computing significant = ifelse(pvalue < alpha, 1, 0). Caused by error in ifelse(): ! object 'pvalue' not found For the below code, do you happen to have any ideas? Many thanks Andy MarketSelections <- GeoLiftMarketSelection(data = GeoTestData_PreTest, treatment_periods = c(90), N = c(12), Y_id = "Y", location_id = "location", time_id = "time", effect_size = seq(0, 0.15, 0.01), lookback_window = 1, include_markets = c("Bradford", "Darlington", "Doncaster", "Halifax", "Harrogate", "Huddersfield", "Hull", "Lancaster", "Leeds", "Sheffield", "Wakefield", "York"), exclude_markets = c("Birmingham", "Bristol", "Chelmsford", "Coventry", "Guildford", "Kingston upon Thames", "Manchester", "Rochester", "Milton Keynes", "Newcastle upon Tyne", "Nottingham", "Portsmouth", "Reading", "Redhill", "South East London", "Stockport", "Stoke-on-Trent", "South West London", "Tonbridge", "Wigan"), holdout = c(), cpic = 1, alpha = 0.1, Correlations = TRUE, fixed_effects = FALSE) On Thu, Aug 4, 2022 at 11:39 AM Andy Foote @.> wrote:
…
Hi Arturo, All solved, thanks very much for your quick response. Thanks Andy On Wed, Aug 3, 2022 at 4:04 PM Arturo Esquerra @.> wrote: > Hi @zig-and-zag https://github.com/zig-and-zag, thanks for reaching > out to us! > > This is almost definitely caused by missing data in the data-set. These > missing values could be explicit (a time-location combination having a > value of NA) or simply a missing date. We'd like to make sure that if a > time-location combination doesn't have a value, we specify that explicitly > with a 0. > > — > Reply to this email directly, view it on GitHub > <#108 (comment)>, > or unsubscribe > https://github.com/notifications/unsubscribe-auth/A2LGTF2LLC5B2674H3KZFH3VXKC63ANCNFSM55NSWNRA > . > You are receiving this because you were mentioned.Message ID: > @.> > -- ANDREW FOOTE Partner - Zebra Associates 07732 822622 @.
-- ANDREW FOOTE Partner - Zebra Associates 07732 822622 @.***

Hi Arturo. Were you able to find the solution? I am running into the same error. The data has no gaps which I thought might be the issue, but still getting the same thing.

Also have the same issue. No NAs.


Cloud-init seed from a file or network url

NoCloud Cloud-init datasource can be configured to seed from a file or network url (like metadata API).
https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html
Do you have plan to implement this or you prefer to keep the cloud init partition ?

This could be open as a future task. We kept it this way because we had a dead line to make it works at the time we were developing it.


Functional Hedera network configured in HardhatUserConfig.networks

Problem
A hedera network configured in HardhatUserConfig.networks isn't functional presumably due to the lack of parity in the hedera-json-rpc-relay with the standard ethereum json rpc.
import { HardhatUserConfig } from "hardhat/config";
import "@nomicfoundation/hardhat-toolbox";

const config: HardhatUserConfig = {
  ...,
  defaultNetwork: "hedera",
  networks: {
    hedera: {
      url: "http://<IP_ADDRESS>:7546",
      chainId: 298,
      accounts: [
        // Alias ECDSA keys private keys
        "0x105d050185ccb907fba04dd92d8de9e32c18305e097ab41dadda21489a211524",
        "0x2e1d968b041d84dd120a5860cee60cd83f9374ef527ca86996317ada3d0d03e7",
        "0x45a5a7108a18dd5013cf2d5857a28144beadc9c70b3bdbd914e38df4e804b8d8",
        "0x6e9d61a325be3f6675cf8b7676c70e4a004d2308e3e182370a41f5653d52c6bd",
        "0x0b58b1bd44469ac9f813b5aeaf6213ddaea26720f0b2f133d08b6f234130a64f",
        "0x95eac372e0f0df3b43740fa780e62458b2d2cc32d6a440877f1cc2a9ad0c35cc",
        "0x6c6e6727b40c8d4b616ab0d26af357af09337299f09c66704146e14236972106",
        "0x5072e7aa1b03f531b4731a32a021f6a5d20d5ddc4e55acbb71ae202fc6f3a26d",
        "0x60fe891f13824a2c1da20fb6a14e28fa353421191069ba6b6d09dd6c29b90eff",
        "0xeae4e00ece872dd14fb6dc7a04f390563c7d69d16326f2a703ec8e0934060cc7",
      ],
    },
  }
  ...,
};

export default config;

Attempting to run a simple test fails on the first call to the json rpc relay i.e. deploy:
import { expect } from "chai";
import { ethers } from 'hardhat';

describe("Greeter", function () {
  it("Should return the new greeting once it's changed", async function () {

    const signers = await ethers.getSigners();

    const signer = signers[0];

    const Greeter = await ethers.getContractFactory("Greeter", signer);

    // fails here
    const greeter = await Greeter.deploy("Hello, world!");

    await greeter.deployed();

    expect(await greeter.greet()).to.equal("Hello, world!");

    const setGreetingTx = await greeter.setGreeting("Hola, mundo!");

    // wait until the transaction is mined
    await setGreetingTx.wait();

    expect(await greeter.greet()).to.equal("Hola, mundo!");
  });
});

Hardhat error stack trace:
ProviderError: Internal error
  at HttpProvider.request (node_modules/hardhat/src/internal/core/providers/http.ts:78:19)
  at LocalAccountsProvider.request (node_modules/hardhat/src/internal/core/providers/accounts.ts:188:34)
  at async EthersProviderWrapper.send (node_modules/@nomiclabs/hardhat-ethers/src/internal/ethers-provider-wrapper.ts:13:20)

Greeter.sol:
//SPDX-License-Identifier: Unlicense
pragma solidity ^0.8.9;

contract Greeter {
    string private greeting;

    constructor(string memory _greeting) {
        greeting = _greeting;
    }

    function greet() public view returns (string memory) {
        return greeting;
    }

    function setGreeting(string memory _greeting) public {
        greeting = _greeting;
    }
}

json-rpc-relay docker container logs:
[2022-08-29 08:42:13.714 +0000] INFO (rpc-server/50 on baafe97141e2): [GET]: /health/liveness 1 ms
[2022-08-29 08:42:13.958 +0000] DEBUG (rpc-server/50 on baafe97141e2): eth_chainId
[2022-08-29 08:42:13.958 +0000] TRACE (relay-eth/50 on baafe97141e2): chainId()
[2022-08-29 08:42:13.960 +0000] INFO (rpc-server/50 on baafe97141e2): [POST] eth_chainId: 200 1 ms
[2022-08-29 08:42:13.964 +0000] DEBUG (rpc-server/50 on baafe97141e2): eth_chainId
[2022-08-29 08:42:13.964 +0000] TRACE (relay-eth/50 on baafe97141e2): chainId()
[2022-08-29 08:42:13.964 +0000] INFO (rpc-server/50 on baafe97141e2): [POST] eth_chainId: 200 0 ms
[2022-08-29 08:42:13.971 +0000] DEBUG (rpc-server/50 on baafe97141e2): eth_chainId
[2022-08-29 08:42:13.971 +0000] TRACE (relay-eth/50 on baafe97141e2): chainId()
[2022-08-29 08:42:13.971 +0000] INFO (rpc-server/50 on baafe97141e2): [POST] eth_chainId: 200 0 ms
[2022-08-29 08:42:13.997 +0000] DEBUG (rpc-server/50 on baafe97141e2): eth_blockNumber
[2022-08-29 08:42:13.998 +0000] TRACE (relay-eth/50 on baafe97141e2): blockNumber()
[2022-08-29 08:42:14.024 +0000] DEBUG (rpc-server/50 on baafe97141e2): eth_chainId
[2022-08-29 08:42:14.024 +0000] TRACE (relay-eth/50 on baafe97141e2): chainId()
[2022-08-29 08:42:14.024 +0000] INFO (rpc-server/50 on baafe97141e2): [POST] eth_chainId: 200 0 ms
[2022-08-29 08:42:14.037 +0000] ERROR (mirror-node/50 on baafe97141e2): [GET] blocks?limit=1&order=desc 567 status
    err: {
      "type": "Error",
      "message": "connect ECONNREFUSED <IP_ADDRESS>:5551",
      "stack":
          Error: connect ECONNREFUSED <IP_ADDRESS>:5551
              at MirrorNodeClient.handleError (/home/node/app/packages/relay/dist/lib/clients/mirrorNodeClient.js:107:27)
              at MirrorNodeClient.<anonymous> (/home/node/app/packages/relay/dist/lib/clients/mirrorNodeClient.js:95:22)
              at Generator.throw (<anonymous>)
              at rejected (/home/node/app/packages/relay/dist/lib/clients/mirrorNodeClient.js:25:65)
              at processTicksAndRejections (node:internal/process/task_queues:96:5)
    }
[2022-08-29 08:42:14.042 +0000] ERROR (Internal error/50 on baafe97141e2): [POST] eth_blockNumber: -32603 45 ms
    code: -32603
    message: "Unknown error invoking RPC"

Solution

Requires further investigation.

Alternatives
No response

I think you have to setup the hedera network in the hedera network config
const config: HardhatUserConfig = {
  ...,
  defaultNetwork: "hedera",
  hedera: {
     networks: {
        hedera: { ... }
    }
}

and not in the hardhat network config as stated in the config https://github.com/hashgraph/hedera-hardhat-hethers#configuration

I'm aware of that, however that requires using the @hashgraph/hardhat-hethers plugin. However, I would like to connect to the local hedera json rpc directly as one would for any other local ethereum node e.g. ganache, etc.
The reason is that using the @hashgraph/hardhat-hethers plugin seems to break other hardhat plugins as I've pointed out in some of the other issues I created: #28 #25
In addition hethers doesn't have all the functionality that hardhat.ethers has, as pointed out in these issues: #30 #29 #27

@dimitrovmaksim is there a reason y'all went this route over enabling standard network configuration within Hardhat? It makes for a terrible dev experience given that an entire ecosystem of hardhat plugins is inaccessible to Hedera devs.

As shown in the example projects the hedera relay can be configured normally in hardhat networks


https://export.amar.io/  expired certificate

Hello,
Export destination url https://export.amar.io/ cannot access because of the expired certificate

Thanks for letting me know, I've renewed it now.

Can we make a note to move this to a databox sever eventually?
thanks

(sooner rather than later- by thursday?)

Should be very quick to deploy on any server. Pure Node, no native deps: https://github.com/me-box-archive/databox-export-destination. Should it be restored from me-box-archive? It's more of a debug tool.
To dockerise, the app store's Dockerfile without line 8 and 10 should suffice.

I'd prefer that all the infrastructure necessary for a databox install, or
for the demo apps etc, was installed and running under collective control
rather than a single individual.
What is it actually used for currently?
If it's containerised, can run it here alongside the forum pretty easily I
think.
On 20 October 2017 at 19:53, Yousef Amar<EMAIL_ADDRESS>wrote:

Should be very quick to deploy on any server. Pure Node, no native deps:
https://github.com/me-box-archive/databox-export-destination. Should it
be restored from me-box-archive? It's more of a debug tool.
To dockerise, the app store's
https://github.com/me-box/platform-app-server Dockerfile without line 8
and 10 should suffice.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/me-box/databox/issues/161#issuecomment-338293248, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAKP4LQuh9-N0rZqCalTtA0kVvrp_p9Gks5suOw6gaJpZM4P-mL5
.

--
Richard Mortier
<EMAIL_ADDRESS>

AFAIK currently os-monitor and the twitter demo app export to that URL. Perhaps if it was an optional dev mode component that could act as a local placeholder for apps that want to export, it will have served its use? Sort of how the local app server is done? (@Toshbrown what do you think?)
If we use it for demos, as we are now, then I think it would be better if it were just a one-off thing. It logs all requests no matter where they come from, so it's no good if many people export to it at the same time for general debugging. I can't quite remember, but perhaps that was the reasoning behind archiving it (after all, for debug you can just tail -f apache/nginx/whatever logs).

Otherwise, if we wanted to turn it into a debugging tool (e.g. export to export.databoxproject.uk to test before you launch your own server), then I think it would need to be extended to have some kind of namespacing or authentication, such that the requests can be divvied up by source databox / dev.

I would prefer export.databoxproject.uk over another remote service running locally. But am happy to be convinced otherwise.
The export service could be altered to embed an identifier into the exported data to use as a filter. As a quick and easy fix.

@mor1  Also might be worth moving the app server too (after Mozfest). Currently, it's running on toms server at store.iotdatabox.com.

Agree. I've created a tracking issue at #165. We'll revisit after Thursday.e

Ok-- finally revisiting now :)
If we have this service running, I can host it locally without a problem.
But first: is there a good reason why we need this running as a shared service, vs something that developers run themselves, locally, for testing purposes?
/cc @Toshbrown @yousefamar


[BUG] Theme selection box text overflow

Longer named themes overflow the selection box. Noticed when updated to latest version of docker image, which is a bit behind 1.4.5.

Thanks for raising this, I will get this fixed this evening

Thanks for raising this, fixed in d8ae1dc1a6d174e365deb047fe351d34ad01e40a which was merged as part of #121 in Dashy V 1.5.3. Do let me know if you come across any other issues :)


Change DMDynamicWaterfallDatasource to DMDynamicWaterfallDelegate, I ...

...think the name is more kind such as the UICollectionViewDelegateFlowLayout

Implement the method collectionView:layout:minimumInteritemSpacingForSectionAtIndex: & ollectionView:layout:minimumLineSpacingForSectionAtIndex: then you can use the DMDyamicWaterfall like UICollectionViewFlowLayout

fixed the bugs


fix: correct oracle and postgres schema versions when bootstrapped

Fixes Issue
Noted by users at https://github.com/jeremylong/DependencyCheck/issues/6746#issuecomment-2200034691 and https://github.com/jeremylong/DependencyCheck/issues/6746#issuecomment-2200305208 for Postgres, but likely missed due to the many other unrelated comments. Similar oversight exists for Oracle, but not sure if there are other issues there as imagine oracle is less frequently used.
Description of Change
No idea if the rest of the changes actually work, but these version numbers seem definitely wrong, and would need to an attempt to re-run delta scripts later?
Have test cases been added to cover the new functionality?
no

again - thank you for the PR. I really need to setup automated testing for the database integrations....


Readme cleanup

Please see #290 :)

I love this cleanup. Finding things are much easier.

@M4lik Thank you for the rework! I wanted to move the news for a long time. Maybe we'll leave the latest news on the front to keep the users informed about changes.
Will merge the pullrequest now.


copy and paste typo ?

The exact same 4 lines are repeated twice: https://github.com/myriadrf/LimeSuite/blob/master/SoapyLMS7/Settings.cpp#L424
https://github.com/myriadrf/LimeSuite/blob/master/SoapyLMS7/Settings.cpp#L429
And also:
https://github.com/myriadrf/LimeSuite/blob/master/SoapyLMS7/Settings.cpp#L449
https://github.com/myriadrf/LimeSuite/blob/master/SoapyLMS7/Settings.cpp#L454

thanks! https://github.com/myriadrf/LimeSuite/commit/6cdf7f32deebd57d6544d7ec3a3f54f43360d15f


registry: Auto deprecate staking program

We should consider building into the staking program an "auto deprecate" feature.
On initialization, we can give the registrar a unix timestamp specifying when staking halts. If anyone tries to stake or switch nodes past that date, the program can return an error, requiring users to upgrade to the new version.

Not doing. Closing.

Not doing. Closing.


Cannot read property 'toString' of undefined

This query fails:
query {
  findCalls(filter: {
    id: {
      eq: 150
    }
  }) {
    items {
      id
      company {
        id
        name
        users {
          user {
            email
            is_active
          }
        }
      }
    }
  }
}

Here is the result:
{
  "errors": [
    {
      "message": "Cannot read property 'toString' of undefined",
      "locations": [
        {
          "line": 9,
          "column": 11
        }
      ],
      "path": [
        "findCalls",
        "items",
        0,
        "company",
        "users",
        0,
        "user"
      ],
      "extensions": {
        "code": "INTERNAL_SERVER_ERROR",
        "exception": {
          "stacktrace": [
            "TypeError: Cannot read property 'toString' of undefined",
            "    at /var/task/node_modules/@graphback/codegen-schema/dist/SchemaCRUDPlugin.js:599:88",
            "    at Array.find (<anonymous>)",
            "    at /var/task/node_modules/@graphback/codegen-schema/dist/SchemaCRUDPlugin.js:599:46",
            "    at Array.map (<anonymous>)",
            "    at SchemaCRUDPlugin.<anonymous> (/var/task/node_modules/@graphback/codegen-schema/dist/SchemaCRUDPlugin.js:598:33)",
            "    at Generator.next (<anonymous>)",
            "    at fulfilled (/var/task/node_modules/tslib/tslib.js:112:62)",
            "    at processTicksAndRejections (internal/process/task_queues.js:97:5)"
          ]
        }
      }
    }
  ],
  "data": {
    "findCalls": {
      "items": [
        {
          "id": "150",
          "company": null
        }
      ]
    }
  }
}

When I add id to the selection set of users.user, the query succeeds:
query {
  findCalls(filter: {
    id: {
      eq: 150
    }
  }) {
    items {
      id
      company {
        id
        name
        users {
          user {
            id
            email
            is_active
          }
        }
      }
    }
  }
}

Companies and users have a many-to-many relationship, so there is a join table called Companies_users that looks like this:
type Companies_users {
    id: ID! # Note that this id exists in the schema because it is necessary, but my database actually does not have this field. Not usre if that matters in this case
    company: Companies!
    user: Users!
}

Automatically generated comment to notify maintainers
/cc @craicoverflow, @machi1990, @wtrocki

This looks like it is related to https://github.com/aerogear/graphback/issues/1752 and the more global one about  better support for many to many relationships.

This looks like it is related to #1752?

This only happens in 0.16.0-alpha3 after https://github.com/aerogear/graphback/pull/1834.  #1861 should fix this issue!

@lastmjs we dropped 0.16.0-alpha4 to take care of this issue. Mind checking and see it fixes the issue for your. Feel free to re-open if it's not the case.

It works! Thanks a ton

Thanks for reporting back!


Ctrl not working as toMods

Hey Elliot. First of all, a HUGE Thank you. Left cmd and arrow shortcuts are genius!
I wanted to extend them to use ctrl as well:
  {'leftCmd+leftCtrl', 'j', 'ctrl', 'left'},
  {'leftCmd+leftCtrl', 'l', 'ctrl', 'right'},

But it does not work.
the problem is with the 'ctrl' . It is not recognized for some reason.
As I had encountered this problem I tried implementing these shortcuts in Karabiner-Elements. First I was very happy as I did not need to define each of them one by one.
Then I encountered a very weird problem, which I have described here:
https://github.com/pqrs-org/Karabiner-Elements/issues/2666

If you could take a look at these, I'd really appreciate it.
It is like I hit a wall from both sides.
( Edit: OMG, you are behind the new youtube rating extension as well??  )

I just tried the solution of issue #1
It also did not work
keyDownWatcher = hs.eventtap.new({hs.eventtap.event.types.keyDown}, function(event)
  -- Maps rightCmd+rightShift+a -> ctrl+a. The key code for rightCmd is 54.
  if modStates[55] and modStates[59] and event:getKeyCode() == hs.keycodes.map['j'] then
    return true, hs.eventtap.keyStroke('ctrl', 'left', 0)
  end
end):start()

keyDownWatcher = hs.eventtap.new({hs.eventtap.event.types.keyDown}, function(event)
  -- Maps rightCmd+rightShift+a -> ctrl+a. The key code for rightCmd is 54.
  if modStates[55] and modStates[59] and event:getKeyCode() == hs.keycodes.map['l'] then
    return true, hs.eventtap.keyStroke('ctrl', 'right', 0)
  end
end):start()

Strange, both versions seem to work for me. Both this version:
{'leftCmd+leftCtrl', 'j', 'ctrl', 'left'},

And this one:
keyDownWatcher = hs.eventtap.new({hs.eventtap.event.types.keyDown}, function(event)
  if modStates[55] and modStates[59] and event:getKeyCode() == hs.keycodes.map['j'] then
    return true, hs.eventtap.keyStroke('ctrl', 'left', 0)
  end
end):start()

However, there is an error in your second example that may be causing an issue. You are assigning both event tap objects to the save variable, keyDownWatcher. You should instead assign each to its own variable, for example keyDownWatcher1 and keyDownWatcher2, or cmdCtrlLeftKeyDownWatcher and cmdCtrlRightKeyDownWatcher. The variable names are arbitrary, but they need to be unique. The reason that they each need to be assigned to a unique global variable is that once the event tap object returned by the call to hs.eventtap.new() goes out of scope, the object will eventually get garbage collected and will no longer capture events. And how long it takes to get garbage collected is variable, so it might start out working for some amount of time, but then later stop working when it eventually gets garbage collected. So in your example code, when you make your second assignment to keyDownWatcher = ..., it will make the first event tap object no longer be referenced from the global scope so it will eventually get garbage collected.
Let me know if changing the code to something like this helps at all:
cmdCtrlLeftKeyDownWatcher = hs.eventtap.new({hs.eventtap.event.types.keyDown}, function(event)
  if modStates[55] and modStates[59] and event:getKeyCode() == hs.keycodes.map['j'] then
    return true, hs.eventtap.keyStroke('ctrl', 'left', 0)
  end
end):start()

cmdCtrlRightKeyDownWatcher = hs.eventtap.new({hs.eventtap.event.types.keyDown}, function(event)
  if modStates[55] and modStates[59] and event:getKeyCode() == hs.keycodes.map['l'] then
    return true, hs.eventtap.keyStroke('ctrl', 'right', 0)
  end
end):start()

P.S. - Sorry for taking so long to reply to this. I just found out I haven't been receiving GitHub notifications. This should be fixed now.

I'm going to close this issue since I haven't heard a reply in a while. But feel free to let me know if I should reopen this issue if it is still unresolved.


ci: add PyPi publishing workflow

This workflow automizes the publishing of APyTypes:

Publish to test.pypi.org on pushes to main
Publish to pypi.org on new tags
GitHub release on new tags

TODO:

[X] Register project name apytypes on test.pypi.org and pypi.org
[X] First publication on test.pypi.org/project/apytypes 🎉
[ ] Get the apytypes organization accepted on pypi.org and test.pypi.org
[ ] Transfer project name apytypes to the public PyPi apytypes organization
[ ] Update README install instruction to pip install apytypes
[x] Fix the build wheel step for windows-latest
[x] Fix the build wheel step for macos-12

One can add a badge that shows the PyPi version: https://shields.io/badges/py-pi-python-version


wayland support

getting the Error: "Couldn't find any pixel format that matches the criteria" on wayland.

Can you give me more info about it? Is this a panic? Can you run it with RUST_BACKTRACE=1?

running the bunnymark example with RUST_BACKTRACE=1
Error: "Couldn't find any pixel format that matches the criteria."

this is with the input mouse example

I have done some research and this seems to be an issue with the drivers wayland+mesa. Are you using mesa? My machi has xorg+nvidia so I cannot test this easily. I did a little update on the gl context builder, can you try again draw_bunnymark  to see if it works? Thanks

on fedora 36 it works 🎉

Great, thanks!


Bitmap with Image url 404 breaks easeljs rendering

stage.addChild( new createjs.Bitmap('myimage.jpg' ) ); //url to 404 image
Results in Chrome:
Failed to load resource: the server responded with a status of 404 (Not Found)
easeljs-0.8.0.min.js:13 Uncaught InvalidStateError: Failed to execute 'drawImage' on 'CanvasRenderingContext2D': The HTMLImageElement provided is in the 'broken' state.
Feels like a case that easel should handle more gracefully.

Odd. This shouldn't happen according to the info I can find. We test .complete before a draw, which according to the spec should only be true if the image was downloaded and decoded successfully:
https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement
Maybe we'll have to add a test for image.width instead.

It might be due to mixed network.. Localhost img vs cdn domain. I will test
all on domain or all local. Thinking there is a security context to this.
On Friday, February 27, 2015, Grant Skinner<EMAIL_ADDRESS>wrote:

Odd. This shouldn't happen according to the info I can find. We test
.complete before a draw, which according to the spec should only be true
if the image was downloaded and decoded successfully:
https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement
Maybe we'll have to add a test for image.width instead.
—
Reply to this email directly or view it on GitHub
https://github.com/CreateJS/EaselJS/issues/573#issuecomment-76472214.

testing cross domain images hitting a 404 shows that all browsers except IE incorrectly return .complete=true.
I have a fix locally that uses .naturalWidth instead. I'll push it up later, and would appreciate testing. I'll then roll it out to SpriteSheet as well.

I just pushed this change. Please test and report back. I've tested locally, and it seems to work well.
https://github.com/CreateJS/EaselJS/commit/13691cdc6b872cf63397e0f25b945e6130b9061c
I'll likely propagate this change to SpriteSheet and elsewhere tomorrow.

This was implemented in EaselJS 0.8.1.


Bundle the locally-built CanvasKit in Flutter tool

We are now building CanvasKit in the Flutter engine and on LUCI. We should get the CanvasKit engine artifacts and bundle it with flutter_web_sdk when we download the Web SDK in the Flutter tool.

This is mostly addressed by https://github.com/flutter/flutter/pull/113072 which will use the prebuilt CanvasKit once it has been made available

Fixed by https://github.com/flutter/flutter/pull/118654


[ Feature Request ] We need a node and lua function for SetCollidable(bool) for moveables and statics

Is your feature request related to a problem? Please describe.
At this time we can only build workarounds when we want set the Collision for Statics and Moveables: We can move it to another position and move it back when needed or we can use a static and use enable disable command to get collision or not, but it should be nice if TEN can natively support a function which can SetCollidable(bool) for moveables and statics
Describe the solution you'd like
A new node and lua function like SetCollidable(bool) for moveables and for statics
Describe alternatives you've considered
No response
Additional context
No response

Implemented for moveables


Fix default certs paths

Motivation and Context
The default certs paths were hardcoded for the toolbox image, update them to work for the monitoring image.
What has changed

Update hardcoded certs paths

How to test?
Check the certs paths are valid for this repos image
Links
https://trello.com/c/XHfzQUze/1257-split-cloudshell-utilities-and-monitoring-tools-out-of-census-rm-toolbox

 Split cloudshell utilities and monitoring tools out of census-rm-toolbox


File Locksmith - option to show in extended context menu only

Description of the new feature / enhancement
Like the options for PowerRename, we should have an option that shows the File Locksmith menu item in the regular context menu or in the extended context menu only.
Scenario when this would be used?
It is rare that I need to look up a lock, but this is a wonderful item to have nearby when I need it. So I would like this powertool to behave like PowerRename does: it isn't present for every right-click, but when needed, user can hit the shift key, and there it is, conveniently located in the extended context menu.
Supporting information
Many windows tools tend to throw items onto the context menu, and too many items gum it up. I currently have 5 different tools that have added things to the standard windows context menu items. It's a welcome courtesy when a program gives you the option to control/stop the placement, and I often turn them off if possible. I appreciate that PowerRename has this option - it isn't always there, but a quick shift+right click and there it is.

Could I add that there should ideally be an option for this to also be promoted to the Windows 11 new context menu as well, but maybe as a submenu under a general PowerToys menu (I have submitted a specific feature request about the submenu idea here)

Good point. Having that said:
Thanks for your message. This is a Duplicate of an other issue. Additional comments may be added there. /dup #21719


ClangImporter: use nameless arguments for anonymous struct/unions in constructors

This patch follows that discussion: https://github.com/apple/swift/pull/6816#pullrequestreview-17037169
Following a13c1345215ee85, constructors of structures/unions containing
anonymous structures/unions fields include those field in their parameter
list, using the generated field name as parameter name:
 typedef struct foo_t {
     union {
         int a;
         int b;
     };
 } foo_t;

Generates:
 struct foo_t {
     init(__Anonymous_field0: foo_t.__Unnamed_union__Anonymous_field0)
 }

 let foo = foo_t(__Anonymous_field0: .init(a: 1))

One important downside here is that the generated field name get exposed
in the API.
An idealistic approach would be to generate the constructors that expose
the fields indirectly inherited from those structures:
 struct foo_t {
     init(a: Int32)
     init(b: Int32)
 }

However, this approach requires the generation of a constructor per valid
combination of indirect fields, which might start having a huge
cardinality when we have nested anonymous structures in nested anonymous
unions...
 typedef struct bar_t {
     union {
         struct {
             int a;
             int b;
         };
         struct {
             int c;
             int d;
         };
     };
     union {
         int e;
         int f;
     };
 } bar_t;

In this examples, we have 4 constructors to generates, for (a, b, e), (a, b, f), (c, d, e) and (c, d, f).
The proposed approach is to use a nameless parameter for anonymous
structures/unions, still forcing the user to build that sub-object by
hand, but without exposing the generated field name. This is very similar
to what can be done in C:
 foo_t foo = { { .a = 1 } };

 let foo = foo_t(.init(a: 1))

Or
 bar_t bar = { { { .a = 1, .b = 2 } }, { .e = 1 } };

 let bar = bar_t(.init(.init(a: 1, b: 2)), .init(e: 1))

Looks good. @jrose-apple Do we want this for 3.1 as well, to maintain source compatibility between 3.1 and 4.0?

Yeah, I agree, @slavapestov. No reason to have this diverge right when it's introduced.

This does need to go into master before it can go to the 3.1 branch. (There's no automerge back to master.) The cherry-pick to the 3.1 branch should then follow the template described in the Swift 3.1 Release Process and must be approved by @tkremenek.

@Fruneau , can you create a PR against master ?

@swift-ci Please test

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 6024b15263a3c6120a68083f85b85582333f0caa
Test requested by - @slavapestov

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 6024b15263a3c6120a68083f85b85582333f0caa
Test requested by - @slavapestov

@swift-ci Please test

This needs to be approved by @tkremenek as release manager before it can be merged, and it still needs to follow the PR format for the release branch.

@jrose-apple I've updated the PR to match the requested format. Let me know if you think there are missing pieces of information in the description.


support customized pull secret

https://github.com/open-cluster-management/backlog/issues/12396
Signed-off-by: Marco<EMAIL_ADDRESS>

/retest

/lgtm


build fails with Allocation failed - JavaScript heap out of memory

Getting an out of memory exception when running polymer build with 3 builds (es2015+modules, es2015 and es5 - standard configurations). All 3 builds work individually - when run 1 at a time.
<--- Last few GCs --->

[2500:00000251EB102490]   134164 ms: Mark-sweep 1337.1 (1459.1) -> 1336.6 (1461.1) MB, 2435.8 / 0.0 ms  allocation failure GC in old space requested
[2500:00000251EB102490]   137374 ms: Mark-sweep 1336.6 (1461.1) -> 1336.6 (1422.6) MB, 3208.7 / 0.0 ms  last resort GC in old space requested
[2500:00000251EB102490]   140427 ms: Mark-sweep 1336.6 (1422.6) -> 1336.6 (1422.6) MB, 3053.3 / 0.0 ms  last resort GC in old space requested

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context:<PHONE_NUMBER>025879
    1: DoJoin(aka DoJoin) [native array.js:~94] [pc=0000035D008EF3B4](this=0000011DD08022D1 ,o=00000151517294A1 ,p=496,D=0000011DD0802371 ,z=0000011DD0802431 ,y=0000011DD08023E1 )
    2: Join(aka Join) [native array.js:~119] [pc=0000035D008DE07E](this=0000011DD08022D1 ,o=00000151517294A1 ,p=496,z=0000011DD0802431
I'm on Windows 10, node v.8.12. The node.js process approaches ~1.5GB but doesn't grow any further even as there's still a few GB of free memory available.
Thanks

I'm on macOS high sierra, node v11 and it happens to me too

Here's another more detailed error:
<--- Last few GCs --->

[15404:000001DFC67353C0]   187819 ms: Mark-sweep 1348.5 (1468.9) -> 1347.7 (1474.9) MB, 2882.8 / 0.0 ms  allocation failure GC in old space requested
[15404:000001DFC67353C0]   190801 ms: Mark-sweep 1347.7 (1474.9) -> 1347.7 (1440.4) MB, 2980.5 / 0.0 ms  last resort GC in old space requested
[15404:000001DFC67353C0]   193735 ms: Mark-sweep 1347.7 (1440.4) -> 1347.7 (1436.9) MB, 2932.6 / 0.0 ms  last resort GC in old space requested

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 00000051B5725879 <JSObject>
    1: constructor(aka NodeBase) [C:\Users\...\AppData\Roaming\npm\node_modules\polymer-cli\node_modules\rollup\dist\rollup.js:~9085] [pc=0000007A96C59E1C](this=00000155292F40C9 ,esTreeNode=0000037A5E9FE701 ,parent=00000155292F4009 ,parentScope=00000155292E2331 <BlockScope map = 0000023A...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node_module_register
 2: v8::internal::FatalProcessOutOfMemory
 3: v8::internal::FatalProcessOutOfMemory
 4: v8::internal::Factory::NewUninitializedFixedArray
 5: v8::internal::WasmDebugInfo::SetupForTesting
 6: v8::internal::WasmDebugInfo::SetupForTesting
 7: v8::internal::WasmDebugInfo::SetupForTesting
 8: v8::internal::WasmDebugInfo::SetupForTesting
 9: v8::internal::SharedFunctionInfo::SetScript
10: v8::internal::JSReceiver::class_name
11: v8::internal::SourcePositionTableIterator::Advance
12: v8::internal::SourcePositionTableIterator::Advance
13: 0000007A965043C1

Here's another more detailed error (running latest node 11.2 on Windows 10):
<--- Last few GCs --->

[15068:00000191C5A4AF50]   134907 ms: Mark-sweep 1356.1 (1425.7) -> 1355.3 (1426.2) MB, 1445.0 / 0.0 ms  (average mu = 0.097, current mu = 0.017) allocation failure scavenge might not succeed
[15068:00000191C5A4AF50]   137036 ms: Mark-sweep 1356.4 (1426.2) -> 1355.7 (1426.7) MB, 2096.1 / 0.0 ms  (average mu = 0.048, current mu = 0.015) allocation failure scavenge might not succeed

<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 00000225CE950361]
Security context: 0x0343e559d9f1 <JSObject>
    1: updateInDeepMap(aka updateInDeepMap) [000003E2E208FA81] [C:\Users\...\AppData\Roaming\npm\node_modules\polymer-cli\node_modules\rollup\dist\rollup.js:~5923] [pc=00000225CFD2E24B](this=0x008d224025b1 ,0x03e2e208e8f9 <Object map = 000000F316B82521>,0x00b21301d3b9 ,0x03e2e208e8f9 <Object map = 000000F...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 00007FF7052FABAA v8::internal::GCIdleTimeHandler::GCIdleTimeHandler+4810
 2: 00007FF7052A0C96 uv_loop_fork+80486
 3: 00007FF7052A1BC0 uv_loop_fork+84368
 4: 00007FF70571DC6E v8::internal::FatalProcessOutOfMemory+798
 5: 00007FF70571DBA7 v8::internal::FatalProcessOutOfMemory+599
 6: 00007FF7059F6E24 v8::internal::Heap::RootIsImmortalImmovable+14788
 7: 00007FF7059ECA64 v8::internal::Heap::CollectGarbage+7556
 8: 00007FF7059EB138 v8::internal::Heap::CollectGarbage+1112
 9: 00007FF7059F4AA7 v8::internal::Heap::RootIsImmortalImmovable+5703
10: 00007FF7059F4B26 v8::internal::Heap::RootIsImmortalImmovable+5830
11: 00007FF7055B5611 v8::internal::Factory::NewFillerObject+49
12: 00007FF705D103DA v8::internal::StoreBuffer::StoreBufferOverflow+26826
13: 00000225CE950361
Adding "--max_old_space_size=8192" to node command line arguments arguments in polymer.cmd file as follows lets the process to grow to about 2.5GB and the build succeeds
@IF EXIST "%~dp0\node.exe" (
  "%~dp0\node.exe" "--max_old_space_size=8192" "%~dp0\node_modules\polymer-cli\bin\polymer.js" %*
) ELSE (
  @SETLOCAL
  @SET PATHEXT=%PATHEXT:;.JS;=;%
  node "--max_old_space_size=8192" "%~dp0\node_modules\polymer-cli\bin\polymer.js" %*
)

We are having the same issue...
What can we do about it?
Building locally won't work even on a 16GB machine without anything else to do.
Building on our CI server works sometimes.

Same here.
Here's an example stack trace
<--- Last few GCs --->

[24066:0x32a78b0]   201862 ms: Scavenge 1342.5 (1421.4) -> 1342.2 (1422.4) MB, 3.3 / 0.0 ms  (average mu = 0.162, current mu = 0.033) allocation failure
[24066:0x32a78b0]   202509 ms: Mark-sweep 1342.8 (1422.4) -> 1342.6 (1422.4) MB, 645.9 / 0.0 ms  (average mu = 0.088, current mu = 0.010) allocation failure scavenge might not succeed

<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 0xe6662f4fb5d]
Security context: 0x096974d1d969 <JSObject>
    1: /* anonymous */ [0x8a9dfb7d219] [/home/jbg/webapp/app/node_modules/@babel/traverse/lib/index.js:~87] [pc=0xe6663c1f5c8](this=0x33568c3fd661 <JSFunction traverse (sfi = 0x8a9dfb32969)>,0x11235ed78199 <Node map = 0x1a51faaa4171>,0x08a9dfb7fbe1 <Object map = 0x19933309c471>,0x34fd001deb19 <Scope map = 0x19933309c241>,0x37f75f6db091 <Object map = 0x1993330...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x90af00 node::Abort() [polymer]
 2: 0x90af4c  [polymer]
 3: 0xb05f9e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [polymer]
 4: 0xb061d4 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [polymer]
 5: 0xf0c6f2  [polymer]
 6: 0xf0c7f8 v8::internal::Heap::CheckIneffectiveMarkCompact(unsigned long, double) [polymer]
 7: 0xf18f88 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [polymer]
 8: 0xf19b1b v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [polymer]
 9: 0xf1c851 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [polymer]
10: 0xee6834 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [polymer]
11: 0x11a0672 v8::internal::Runtime_AllocateInNewSpace(int, v8::internal::Object**, v8::internal::Isolate*) [polymer]
12: 0xe6662f4fb5d
Aborted (core dumped)
error Command failed with exit code 134.

Any updates on this? I got the same issue :|

Same here

If it's out of memory it means it does too much. One solution would be to build half of the app by specifying half of the fragments and then the other half of the app by specifying the rest of the fragments and then merge the result

I was facing the same issue. In our polymer.json we have 2 build configurations (I don't even know, why):
"builds": [
    {
      "name"  : "default",
      "preset": "es5-bundled",
      "bundle": {
        "excludes": ["configuration-mixin.js", "src/daq-search-query-worker.js"]
      }
    },
    {
      "name"  : "default1",
      "bundle": {
        "excludes": ["configuration-mixin.js", "src/daq-search-query-worker.js"]
      },
      "addServiceWorker": false
    }
  ]

For me, as well, when I run specific builds, one at a time, it works fine, but running polymer build without --name ... will create this error.
I don't know, if this matters, but the project was a Polymer 2 project, which we are porting to Polymer 3, i.e. the code is based on PolymerElement not LitElement.

@djlauk try this:
export NODE_OPTIONS=--max_old_space_size=4096
polymer build

My team had this issue after upgrading from Polymer 2 to Polymer 3 and this solution worked for us.

Thanks, @adi130987. This workaround worked as well, but it still takes very long:
$ time polymer build
info:	Clearing build/ directory...

... some warnings ...

info:	(default1) Building...
[BABEL] Note: The code generator has deoptimised the styling of undefined as it exceeds the max of 500KB.
info:	(default) Building...
info:	(default) Build complete!
info:	(default1) Build complete!

real	18m59.162s
user	20m44.079s
sys	0m9.745s

While each of the individual named builds runs a lot faster:
$ time polymer build --name default
info:	Clearing build/ directory...
info:	(default) Building...
[BABEL] Note: The code generator has deoptimised the styling of undefined as it exceeds the max of 500KB.

... some warnings ...

info:	(default) Build complete!

real	0m25.081s
user	0m34.406s
sys	0m1.926s

and
$ time polymer build --name default1
info:	Clearing build/ directory...
info:	(default1) Building...
[BABEL] Note: The code generator has deoptimised the styling of undefined as it exceeds the max of 500KB.

... some warnings ...

info:	(default1) Build complete!

real	0m25.371s
user	0m34.696s
sys	0m2.043s

I hope this information can help someone to circle in on the cause of this issue a bit quicker. Here are some more notes / thoughts:

I am aware that the names "default" and "default1" are not great. (Like I said, I don't even know, why we have the two. It's just what was already there when I was put on the project.)
The warnings that I skipped in the output are the same for all the builds, combined or individual. So I consider them irrelevant to this issue. (They are about not being able to resolve a class reference which is the parameter to the mixin functions in our code.)

Also maybe worth noting are the following things I noticed about the combined polymer build (top output):

For the combined build, the warnings come before the output info: (default1) Building...; for the individual builds the order is reversed.
The output of build "default" is nested inside the output of build "default1". I.e. judging from the output:

Build "default1" starts.
Build "default" starts.
Build "default" ends.
Build "default1" ends.

For the longest time there is no visible activity at all, then everything seems to have been finished at once:

Output starts at "normal progress speed" but there is a long pause right after the warnings for most of the remaining time.
The build of "default" seemed to have taken the same amount of time (noticed from the corner of my eye)

There was only a short amount of time between info: (default) Building... and info: (default) Build complete!

Right afterwards there was the notice info: (default1) Build complete!

I've repeated to run polymer build multiple times, each run giving similar results (a few seconds faster / slower)

polymer build --name whatever doesn't run the build config called "whatever", it just builds with the defaults & names the output "whatever".
Someone opened https://github.com/Polymer/tools/issues/606 for that

@djlauk - does your polymer.json include:
"moduleResolution": "node", "npm": true
If not and you add it does it make any difference?

@hyperpress Yes, the polymer.json has both options set this way:
{
  //...
  "moduleResolution": "node",
  "npm": true,
  // ...
}

Running into the same issue here, anyone any tips or tricks on this? we're being killed on build/deploy times/resources. :(

Delete your node_modules folder and package-lock.json. Then, do 'polymer
install' and 'polymer serve'. If all works run 'polymer build'.
Make sure that the old modules folder and lock file are deleted, not just
in trash.
If that doesn't solve it. Please post a full trace, along with environment
(Windows, Mac, Linux, OS version, Node and NPM version, hardware RAM, CPU,
Disk space available.
I'm thinking we should just start from the basics and try a figure out
what's causing the fault from there.

Tried it all :) @adi130987 @acory have been leading on this one...
for context here's one of the repo polymer.json and package.json:
https://github.com/unicef/etools-partnership-management/blob/prepare-for-deploy/polymer.json
https://github.com/unicef/etools-partnership-management/blob/prepare-for-deploy/package.json
whether running in circleCi, locally docker , or locally (2016 Macbook Pro | High Sierra | 16gb Ram | 2.9GHz I7) running into the same issue, either memory allocation or if we export NODE_OPTIONS=--max_old_space_size=4096 it takes 20 min.
the repo is open source if anyone is inclined to help you might be able to reproduce this if you clone it, go to prepare-for-deployment branch and run npm run build after installing node packages.
We recently moved from poly2 to poly3.
Thanks a million, in advance :)

There are 3 builds in that polymer.json, have you tried running polymer
build with one build at a time in the builds array? Do all of the builds
behave this way when they are the only one in the polymer.json or is there
a single culprit? What about 2 builds at a time? etc
On Fri, Mar 29, 2019, 9:30 AM Robert Avram<EMAIL_ADDRESS>wrote:

Tried it all :) @adi130987 https://github.com/adi130987 @acory
https://github.com/acory have been leading on this one...
for context here's one of the repo polymer.json and package.json:
https://github.com/unicef/etools-partnership-management/blob/prepare-for-deploy/polymer.json
https://github.com/unicef/etools-partnership-management/blob/prepare-for-deploy/package.json
whether running in circleCi, locally docker , or locally (2016 Macbook Pro
| High Sierra | 16gb Ram | 2.9GHz I7) running into the same issue, either
memory allocation or if we export NODE_OPTIONS=--max_old_space_size=4096
it takes 20 min.
the repo is open source if anyone is inclined to help you might be able to
reproduce this if you clone it, go to prepare-for-deployment branch and
run npm run build after installing node packages.
We recently moved from poly2 to poly3.
Thanks a million, in advance :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Polymer/tools/issues/757#issuecomment-478063598, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AVLM4bB8LI2wiZfSKHVdPE1eiewMKVNRks5vbj-lgaJpZM4X6dFl
.

I cloned a copy and what I'm seeing on install is that your repo is referencing Polymer 2 components which rely on bower for HTML Imports.
You're referencing pmp/app-shell.html in polymer.json, and that file references Polymer 2 files in bower_components so obviously the app is setup to run on Polymer 2. package.json doesn't reference any Polymer 3 packages or deps.
Is this the correct repo? Perhaps you can explain this in more detail because this is not a standard polymer 3 project upgraded from polymer 2.

@hyperpress The Polymer 3 version is on upgrade--polymer3 branch

So, I downloaded the correct branch and tried several build versions and tests. There is definitely something in the tsc build process to polymer build that it's unhappy about. There's the dynamic imports that get non-literal warnings , but then, really no matter what I've tried from one preset build with minimal options to a bunch of other trial and errors, everything hangs up badly after it clears the build directory.
I'm running this on a 24 core with a half a gig of RAM workstation with Ubuntu Linux 18.10. There's not a lack of horsepower involved here. Here's the last one I tried (just the esm build) and it did complete the build in about 50 seconds:
polymer.json.txt
If I add all the builds back in for esm, es6, and es5 the process results in a core dump with the following stack trace:
==== JS stack trace =========================================

    0: ExitFrame [pc: 0x9193974fc5d]
    1: StubFrame [pc: 0x9193970a111]
    2: ConstructFrame [pc: 0x91939709cc4]
Security context: 0x0a397d81d9b1 <JSObject>
    3: getScope [0x103c5bc063e1] [/home/john/.nvm/versions/node/v11.11.0/lib/node_modules/polymer-cli/node_modules/@babel/traverse/lib/path/index.js:~142] [pc=0x9193a3b087a](this=0x0e6a156cb731 <NodePath map = 0x3b860f267f61>,0x0e6a156ca829 <Scope map = 0x3b860f267bf1>)
    4: visi...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

Writing Node.js report to file: report.20190329.202431.22581.001.json
Node.js report completed
 1: 0x959570 node::Abort() [polymer]
 2: 0x95a25e node::OnFatalError(char const*, char const*) [polymer]
 3: 0xb3735e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [polymer]
 4: 0xb37594 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [polymer]
 5: 0xf36bd2  [polymer]
 6: 0xf36cd8 v8::internal::Heap::CheckIneffectiveMarkCompact(unsigned long, double) [polymer]
 7: 0xf433f8 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [polymer]
 8: 0xf43f0b v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [polymer]
 9: 0xf46c41 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [polymer]
10: 0xf10e74 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [polymer]
11: 0x11c72be v8::internal::Runtime_AllocateInNewSpace(int, v8::internal::Object**, v8::internal::Isolate*) [polymer]
12: 0x9193974fc5d
Aborted (core dumped)

If it were me, I think I'd move all this into webpack, maybe using @anoblet my-project setup as an example. His is quite fast and he's using a similar TS schema to yours. But there might be someone a lot smarter than I am with this who will see something I don't. Wish I could be of more help, but I'm stumped at this point.

Same problem here since this morning
[8952:0000020F1954BA10] 95246 ms: Scavenge 1317.9 (1436.2) -> 1307.5 (1439.7) MB, 12.6 / 0.0 ms (average mu = 0.105, current mu = 0.054) allocation failure
[8952:0000020F1954BA10] 95330 ms: Scavenge 1320.5 (1439.7) -> 1309.8 (1442.7) MB, 12.4 / 0.0 ms (average mu = 0.105, current mu = 0.054) allocation failure
<--- JS stacktrace --->
==== JS stack trace =========================================
0: ExitFrame [pc: 000002909E95C5C1]
Security context: 0x0229fb79e6e1
1: word [0000014F23E32009] [C:\Users\Bastien\AppData\Roaming\npm\node_modules\polymer-cli\node_modules\babel-generator\lib\printer.js:~127] [pc=000002909F55D173](this=0x00c5556022c1 ,str=0x0122b0fff9c1 <String[5]: value>)
2: Identifier [0000014D5577EC61] [C:\Users\Bastien\AppData\Roaming\npm\node_modules\polymer-cl...
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 00007FF7DC6FECE5
2: 00007FF7DC6D8196
3: 00007FF7DC6D8BA0
4: 00007FF7DC968D5E
5: 00007FF7DC968C8F
6: 00007FF7DCEA69D4
7: 00007FF7DCE9D137
8: 00007FF7DCE9B6AC
9: 00007FF7DCEA4627
10: 00007FF7DCEA46A6
11: 00007FF7DCA47767
12: 00007FF7DCADF44A
13: 000002909E95C5C1
I don't know why, but when changing the head on my git repo and doing a git reset -fd will make the build works sometimes...

Just ran into this problem today. Running it on Cloud Build. It was running fine this morning, which is the weirdest part.
Here's the relevant part of the logs:
Finished Step #1 - "Polymer build"
Step #1 - "Polymer build": 8: 0x18e979842fd
Step #1 - "Polymer build": 7: v8::internal::Runtime_GrowArrayElements(int, v8::internal::Object**, v8::internal::Isolate*) [polymer]
Step #1 - "Polymer build": 6: 0xd7fc13 [polymer]
Step #1 - "Polymer build": 5: v8::internal::Factory::NewUninitializedFixedArray(int) [polymer]
Step #1 - "Polymer build": 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [polymer]
Step #1 - "Polymer build": 3: v8::Utils::ReportOOMFailure(char const*, bool) [polymer]
Step #1 - "Polymer build": 2: 0x8cbf4c [polymer]
Step #1 - "Polymer build": 1: node::Abort() [polymer]
Step #1 - "Polymer build": FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
Step #1 - "Polymer build":
Step #1 - "Polymer build": 2: word [/usr/local/lib/node_modules/polymer-cli/node_modules...
Step #1 - "Polymer build": 1: _append [/usr/local/lib/node_modules/polymer-cli/node_modules/babel-generator/lib/buffer.js:~94] [pc=0x18e981edd60](this=0xd186942e5d1 <Buffer map = 0x1c3aa4e7a759>,str=0x19cbab67c0c9 <String[1]: >,line=8265,column=63,identifierName=0xe5607f02201 <null>,filename=0x1fc578f82501 <String[31]: file:///workspace/src/my-app.js>)
Step #1 - "Polymer build": Security context: 0x19cbab625879 <JSObject>
Step #1 - "Polymer build":
Step #1 - "Polymer build": ==== JS stack trace =========================================
Step #1 - "Polymer build":
Step #1 - "Polymer build": <--- JS stacktrace --->
Step #1 - "Polymer build":
Step #1 - "Polymer build":
Step #1 - "Polymer build": [1:0x2da34a0] 376761 ms: Mark-sweep 1342.6 (1477.2) -> 1342.6 (1473.2) MB, 3490.1 / 0.0 ms last resort GC in old space requested
Step #1 - "Polymer build": [1:0x2da34a0] 373270 ms: Mark-sweep 1342.7 (1525.2) -> 1342.6 (1477.2) MB, 3452.2 / 0.0 ms last resort GC in old space requested
Step #1 - "Polymer build": [1:0x2da34a0] 369817 ms: Mark-sweep 1342.9 (1525.2) -> 1342.7 (1525.2) MB, 3535.3 / 0.0 ms allocation failure GC in old space requested
Step #1 - "Polymer build":
Step #1 - "Polymer build": <--- Last few GCs --->
Step #1 - "Polymer build":
Step #1 - "Polymer build": info:	Clearing build/ directory...

I was able to "fix" the problem by removing the bundle=true property from my polymer.json file. I don't consider it truly fixed because I still haven't discovered the root cause, but it's a decent workaround to get my project deployed. I compared the last successful commit with the first failed build, and I can't see anything that would cause the bundler to fail.

I encountered this problem too. Seems to be because there's no tree-shaking from what I can tell. Importing modules (my problem is with date-fns) like this:
const { startOfDay, endOfDay } from 'date-fns'

causes the whole date-fns library to be loaded and run out of memory for some reason. Sometimes it doesn't even compile it correctly and I get missplaced imports error of the like my-app.js doesn't export isProtectedWeekYearToken and such, which I am not even directly.
Importing functions one by one solved the problem for me. Like this:
const startOfDay from 'date-fns/startOfday';
const endOfDay from 'date-fns/endOfday';

Only files needed by those 2 functions get imported and everything builds smoothly.

@Pupix great...
lodash has this issue too.
In our project we used to do imports like this:
import { isNil, isObject} from 'lodash'
or even worse
import _ from 'lodash', not paying attention to build performance.
After all lodash imports were updated like this:
import isNil from 'lodash/isNil';
import isObject from 'lodash/isObject';

build time improved with 50%;

Well my fix stopped working, unfortunately. I also tried rewriting some of my imports, but it didn't help at all. Anyone have an alternative to using polymer-cli for building a polymer/lit-element project?

Well my fix stopped working, unfortunately. I also tried rewriting some of my imports, but it didn't help at all. Anyone have an alternative to using polymer-cli for building a polymer/lit-element project? It's very frustrating how this problem seems to arise for no apparent reason.

Since the beginning i use bundle=false in my polymer.json file.
By adding "--max_old_space_size=8192", the process don't take more than 1go in my computer ...
I found which file and where the builder fails (in fact, i'm not sur, but i think)
I have a big file with a very big switch...case (around 20 switch), in every switch a document.createElement.
If i comment the document.createElement, it's better, but i don't know why ...
it's like polymer try to run all the code before parsing it ....

But that removes a big benefit to using polymer-cli. I'm currently
attempting to build an alternative build process using rollup. I haven't
been too successful, but I'll definitely update once I make some progress.
On Tue, Jul 2, 2019, 10:58 PM bastienarm<EMAIL_ADDRESS>wrote:

Well my fix stopped working, unfortunately. I also tried rewriting some of
my imports, but it didn't help at all. Anyone have an alternative to using
polymer-cli for building a polymer/lit-element project? It's very
frustrating how this problem seems to arise for no apparent reason.
Since the beginning i use bundle=false in my polymer.json file.
By adding "--max_old_space_size=8192", the process don't take more than
1go in my computer ...
I found which file and where the builder fails (in fact, i'm not sur, but
i think)
I have a big file with a very big switch...case (around 20 switch), in
every switch a document.createElement.
If i comment the document.createElement, it's better, but i don't know
why ...
it's like polymer try to run all the code before parsing it ....
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Polymer/tools/issues/757?email_source=notifications&email_token=AC2JDEGEM6EC3ZEGX4IWLMDP5Q5XPA5CNFSM4F7J2FS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZDLJKQ#issuecomment-507950250,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC2JDEHVWK6FVI53V46HXUDP5Q5XPANCNFSM4F7J2FSQ
.

But that removes a big benefit to using polymer-cli. I'm currently attempting to build an alternative build process using rollup. I haven't been too successful, but I'll definitely update once I make some progress.
…
On Tue, Jul 2, 2019, 10:58 PM bastienarm @.***> wrote: Well my fix stopped working, unfortunately. I also tried rewriting some of my imports, but it didn't help at all. Anyone have an alternative to using polymer-cli for building a polymer/lit-element project? It's very frustrating how this problem seems to arise for no apparent reason. Since the beginning i use bundle=false in my polymer.json file. By adding "--max_old_space_size=8192", the process don't take more than 1go in my computer ... I found which file and where the builder fails (in fact, i'm not sur, but i think) I have a big file with a very big switch...case (around 20 switch), in every switch a document.createElement. If i comment the document.createElement, it's better, but i don't know why ... it's like polymer try to run all the code before parsing it .... — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#757?email_source=notifications&email_token=AC2JDEGEM6EC3ZEGX4IWLMDP5Q5XPA5CNFSM4F7J2FS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZDLJKQ#issuecomment-507950250>, or mute the thread https://github.com/notifications/unsubscribe-auth/AC2JDEHVWK6FVI53V46HXUDP5Q5XPANCNFSM4F7J2FSQ .

Yes ... but at least i can work.
I'm the only one front dev here, and we need to move :)

Just to let you know; for me this issue came from (module) import 'sinon/pkg/sinon-esm.js'
After removing the import all worked well for me.

By my experience the most important factor in build time is number of dependencies in package.json ("devDependencies" doesn't matter). Any other dependency than polymer, webcomponents, lit-element, pwa-helpers and redux dramatically increases build time for me.

Ever since I migrated to rollup, I haven't experienced any issues whatsoever. This comes from someone that had using polymer-cli for over 2 years.

Ever since I migrated to rollup, I haven't experienced any issues whatsoever. This comes from someone that had using polymer-cli for over 2 years.

@kr05 Would you be willing to paste a sample of your implementation?

My setup is due for an update, but I'll link a previous answer where I posted my implementation.

Steps to resolve memory leaks: StackOverFlow


Cant read data points.

Tested On :
Influxdb Shell Version : InfluxDB shell 0.9.1
Influxdb Shell Version : InfluxDB shell 0.9.2
Go Version : go version go1.4.2
I connect to my Influxdb database that is hosted on influxdb.com.
Execute the following command :
Show databases;
And get :

{ Results []client.Result "json:\"results,omitempty\""; Err string "json:\"error,omitempty\"" }

@mbejda how did you execute the show databases command? You mentioned client version that you're using is 0.9.x, but which version of Influxdb are you using? Can you recreate the issue locally?

Ok Im closing this issue. There is a influxdb 0.8.x to influxdb 0.9.x shell incompatibility. The hosted service still uses influxdb 0.8.x database and locally Im using 0.9.2. So you cant use influxdb 0.9.x shell to communicate in influxdb 0.8.x database.  You need to use influxdb 0.8.x shell to communciat with influxdb 0.8.x database. I wish this was written somewhere in the docs. XD. :tangerine:

@mbejda I'll open an issue in the influxdb.com repo for this.