K8SSAND-1453 ⁃ Upgrade to cass-operator 1.10.3 (or later)

What happened?
DNS lookups for Cassandra pods does not work. See https://github.com/k8ssandra/cass-operator/issues/304.
Did you expect to see something different?
DNS resolution for Cassandra pods should work.
How to reproduce it (as minimally and precisely as possible):
See https://github.com/k8ssandra/cass-operator/issues/304 for steps.
Environment

K8ssandra Operator version:
v1.0.1

┆Issue is synchronized with this Jira Task by Unito
┆friendlyId: K8SSAND-1453
┆priority: Medium

Upgrading cass-operator in main fails as follows:
$ go get<EMAIL_ADDRESS>go: downloading github.com/k8ssandra/cass-operator v1.10.3
go get: installing executables with 'go get' in module mode is deprecated.
	To adjust and download dependencies of the current module, use 'go get -d'.
	To install using requirements of the current module, use 'go install'.
	To install ignoring the current module, use 'go install' with a version,
	like 'go install example.com/cmd@latest'.
	For more information, see https://golang.org/doc/go-get-install-deprecation
	or run 'go help get' or 'go help install'.
# github.com/k8ssandra/cass-operator/pkg/httphelper
../../gocode/pkg/mod/github.com/k8ssandra/cass-operator@v1.10.3/pkg/httphelper/security.go:302:4: unknown field 'Handler' in struct literal of type "k8s.io/api/core/v1".Probe
../../gocode/pkg/mod/github.com/k8ssandra/cass-operator@v1.10.3/pkg/httphelper/security.go:305:25: container.LivenessProbe.Handler undefined (type *"k8s.io/api/core/v1".Probe has no field or method Handler)
../../gocode/pkg/mod/github.com/k8ssandra/cass-operator@v1.10.3/pkg/httphelper/security.go:306:25: container.LivenessProbe.Handler undefined (type *"k8s.io/api/core/v1".Probe has no field or method Handler)
../../gocode/pkg/mod/github.com/k8ssandra/cass-operator@v1.10.3/pkg/httphelper/security.go:307:25: container.LivenessProbe.Handler undefined (type *"k8s.io/api/core/v1".Probe has no field or method Handler)
../../gocode/pkg/mod/github.com/k8ssandra/cass-operator@v1.10.3/pkg/httphelper/security.go:313:4: unknown field 'Handler' in struct literal of type "k8s.io/api/core/v1".Probe
../../gocode/pkg/mod/github.com/k8ssandra/cass-operator@v1.10.3/pkg/httphelper/security.go:316:26: container.ReadinessProbe.Handler undefined (type *"k8s.io/api/core/v1".Probe has no field or method Handler)
../../gocode/pkg/mod/github.com/k8ssandra/cass-operator@v1.10.3/pkg/httphelper/security.go:317:26: container.ReadinessProbe.Handler undefined (type *"k8s.io/api/core/v1".Probe has no field or method Handler)
../../gocode/pkg/mod/github.com/k8ssandra/cass-operator@v1.10.3/pkg/httphelper/security.go:318:26: container.ReadinessProbe.Handler undefined (type *"k8s.io/api/core/v1".Probe has no field or method Handler)

This is because k8ssandra-operator depends on k8s.io/kubernetes v1.23.4 in main whereas cass-operator v1.10.3 depends on k8s.io/kubernetes v1.22.2. cass-operator master branch is on k8s.io/kubernetes v1.23.4.
We can upgrade to cass-operator v1.10.3 on the release/1.0 branch fine so that the upgrade can be included in k8ssandra-operator v1.0.2.
In the main branch we will need to upgrade to a more recent commit of cass-operator.


If defaultTransitions are not given, VictoryTransition should use defaultTransition.discrete

This issue was moved to FormidableLabs/victory#333


Publications from bib file

Instead of manually adding the publications, there should be an option to input the bib file and fetch the relevant data and use that to build the publications section. This will come handy when a user a long list of publications

Instead of DOI, there should be URL or another generic keyword, in order to add not yet published articles which are under peer review (arXiv). I know arXiv also gives DOI, but it is more intuitive for people just to use the arXiv identifier instead of the DOI.
or a different approach would be:
In the publications sections, one can give the path to bib file. And then for markdown it needs to be handled by the markdown parser and for latex it can be directly handeled by the Texlive (I dont know if it is possible at all since LaTeX is generated from the Markdown file)

Thank you! In the next release, url field will be available as an alternative to doi for PublicationEntry.

RenderCV v1.11 has url field for the PublicationEntry and has been released,

@sinaatalay I have added the conversion for bib to yml as per your format. Maybe take a look and see if you want to merge? I haven't included this in your code yet, I couldn't understand how to do it. Here's the repo: https://github.com/sahiljhawar/bib2yaml-for-rendercv

Thank you! I think it's best to have this in another script. We could have added a new CLI command (rendercv convert-from-bib example.bib), but it would have added new dependencies and a new thing to maintain, which is not really in the scope of the project.
If you would like:

You could add this to the User Guide's FAQ and link your script. You can send a pull request with updated docs (check out the developer guide for docs).
Also, you could open a discussion about this so that people can see it.

This does not add extra heavy dependencies. Just two more. I would suggest this script for the CLI command.


Erroneous Bounding boxes in Road Object Detection dataset

While going through the dataset, I found few erroneous bboxes. Eg. in  100k/train/635dacee-af1dd825.json at line 60 -
"box2d": {
"x1": 0,
"y1": 122.849907,
"x2": 0,
"y2": 148.499896                                                                                }
Are there any other known errors?

This is a known problem. Those boxes will be filtered out in label2det: https://github.com/ucbdrive/bdd-data/blob/master/bdd_data/label2det.py#L25

there are also some wrong class labels too.


feat: add verifyWithIndividualChecks

Returns an array of promises, each promise corresponds to a verification check.
The last promise resolves to the overall validity based on all the checks.
This allows us to work on the promises independently from the other verification checks.

:tada: This PR is included in version 2.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Verilog improvements

Improve number support
Verilog is case sensitive

@raphnet can you please add short markup test for Verilog?

@Sannis Done. I created two tests. First a verilog number test, since fixing number highlighting was specifically what my original commit was about, and a second test based on a copy of the language detection code which will be I think a good sanity test.

Thanks for keeping an eye on the language!


C schiff

perche non farlo in php?

PHP isn't, for me, the right language to use for an application.


infinite crash loop when cookiebot script is blocked

If Cookiebot was blocked by the client, it would cause an infinite client error loop which crashed the site. This was because every time the path updated, it would attempt to run the Cookiebot script on the window object, which did not exist.
I have added some additional checks/error handling to prevent the crash loop from happening: https://github.com/equinor/energyvision/commit/de55554271b1ebe17a9db04970c16d973f5eefd5

This can be tested by blocking Cookiebot. I did that using the Ghostery extension and pressing the magical "Restrict website" button. Tested it in Vivaldi since we got a bug report form someone using that browser specifically, but it probably behaves the same in other browsers and other extensions that can/do block Cookiebot.

LGTM :thumbsup:


chore: update spin sdk to 0.6.0

Signed-off-by: karthik Ganeshram<EMAIL_ADDRESS>

closed in favor of #55


pipenv is not installing or running cmds

-bash: pipenv: command not found is the error that I get when I install pipenv. I've tried everything from installing it to uninstalling it
I am writing this code  pipenv install --system --skip-lock

sounds like you have a problem with your system python installation, or your user paths. I'd recommend adding the directory that pipenv is installed to to your path.


Fix #3201: Provide more detail on "Unknown opcode: 5".

Jenkins, test this please

Er ... Jenkins refuses to see that PR :( It's like it doesn't even receive any kind of notification about it.

Seems it has picked it up now. Note that I have added a big comment that this is not so nice, but as good as it gets :)


Time point not loosing precision in json conversion

Explicit millisecond clock made with the iso8601 conversion.
Add uuid to item

Okay, I can agree to this. We should add a static assert for nanoseconds and microseconds if we don't want them encoded.

the requires clause takes care of nano and microseconds, requires(!std::is_same_v<duration_t, std::chrono::microseconds> && !std::is_same_v<duration_t, std::chrono::nanoseconds>) so when/if we need that precision we can review this decision.


[L] Create knotx-extensions repository

Please move to knotx-extensions:

Authorization Knot,
Http Action Adapter

Repository structure - module by feature:
/authorization/authorization-knot
/generic/http-action-adapter

HttpActionAdapter will be fixed in #204.


v2.0 Beta - Multiple maps sometimes does not render

If you aren't taking issues on the beta branch, please disregard.
In my application, I have two tabs each with a separate map.  Sometimes when navigating between tabs, one map will not render.  If I switch to a different tab and back to the non-rendering tab though the map will render itself.
For example, I have tabs A, B, and C in an application.  Tabs A and B have maps.  If I start on tab A, the map on that tab (A) will render.  However, if I switch to tab B, the map on that tab (B) will not render.  If I then switch to tab C (no map) and then back to tab B, the map on tab B will render.
I am using the setVisible(true/false) workaround that is documented here in section "change 2: Multiple pages".  My code for setting the map visible state is shown below.
In Tab A controller
$scope.$on("$stateChangeSuccess", function (e, toState, toParams, fromState, fromParams) {
  if (fromState.name === 'tab.A') {
    return mapA.setVisible(false);
  }

  if (toState.name === 'tab.A') {
    return mapA.setVisible(true);
  }
});

In Tab B controller
$scope.$on("$stateChangeSuccess", function (e, toState, toParams, fromState, fromParams) {
  if (fromState.name === 'tab.B') {
    return mapB.setVisible(false);
  }

  if (toState.name === 'tab.B') {
    return mapB.setVisible(true);
  }
});

Before I added the code above, two maps would not render simultaneously at all.  With the above code, both maps render maybe 95% of the time, however, occasionally one will not render.
Am I missing something?  If I am doing things correctly, I'd be happy to provide more information and try to provide steps for consistently repeating the issue.

Since the ionic framework is slow, the plugin finishes the initialization before ionic finishing when you change the page tabs.
If you need to redraw the map mandatory, you need to execute cordova.fireDocumentEvent('plugin_touch', {}); by yourself.
https://github.com/mapsplugin/cordova-plugin-googlemaps-doc/blob/master/v2.0.0/whats-new-v2/README.md#change-4-save-battery-life

I think I understand.  Is there an ionic event that can be used to ensure the plugin inits after the page does?  Right now, I'm initializing the maps inside of $ionicPlatform.ready() but upon further research that fires after the device is ready so it's probably not the best option for this.
Maybe $ionicView.afterEnter()?

I'm sorry but I'm not familiar with ionic at all.
I think cordova.fireDocumentEvent('plugin_touch', {}); inside of $ionicPlatform.ready() or map.on(plugin.google.maps.event.MAP_READY solves your issue.
Basic idea
$ionicPlatform.ready(function() {
  cordova.fireDocumentEvent('plugin_touch', {}); // <-- maybe here

  var map = plugin.google.maps.Map.getMap(div, { ... });
  map.on(plugin.google.maps.event.MAP_READY, function() {

     cordova.fireDocumentEvent('plugin_touch', {}); // <-- or maybe here

  });
});

If the above idea does not work, please share your project on github or bitbucket.
By the way, please also check out this document.
How to install the cordova-googlemaps-plugin v2-beta on Ionic 2
https://github.com/mapsplugin/cordova-plugin-googlemaps-doc/blob/master/v2.0.0/For-ionic2-users/README.md#how-to-install-the-cordova-googlemaps-plugin-v2-beta-on-ionic-2

No problem.
Firing the event in the MAP_READY by itself unfortunately doesn't fix the issue.  However, wrapping the redraw event in a $timeout and seems to reduce the occurrence of the issue.  This is a pretty brittle "solution" though.
$ionicPlatform.ready(function() {
  var map = plugin.google.maps.Map.getMap(div, { ... });
  map.on(plugin.google.maps.event.MAP_READY, function() {

     $timeout(function() {
       cordova.fireDocumentEvent('plugin_touch', {});
     }, 200);
  });
});

Ok, thank you for sharing your solution ;)


setting server.timeout

Hi,
the sockpress server has no oppertunity to set server.timeout.
A new property serverTimeout in the options solve this problem.
In index.js:
if (options.serverTimeout && options.serverTimeout>=0)
  _server.setTimeout(options.serverTimeout);

Hi!
Thank you for pointing out this issue. I'll check this as soon as possible.
Tests are broken under the last version of NPM and I have to do some refactor before adding anything to this module.

Ok, I've probably a better idea regarding this issue.
What if Sockpress populates the express application with the raw http or https server? You could then customize this server with any option you want with something like app.rawServer.setTimeout(...). Express provides maybe a way to access the server, but I've not found anything yet...

You are right. That is more general and prevents other configuration issues.

Added and available in<EMAIL_ADDRESS>:+1:


Support for Reason Phrase in ResponseObject

Proposal
An additional ResponseObject attribute called reasonPhrose to support specifying the status line's reason phrase.
Explanation
An HTTP response's status line provides a status code (e.g. 201) and a reason phrase (e.g. "Created").  While the meanings are semantically normalized and the status phrases tend to be stable, they can vary.  OpenAPI provides a description field, but no way to specify it.  This creates a small problem when using documentation generators: they often resort to presenting the status code and the description together.  Worse, a long or multi-line description may be presented as if it were the status string.
While this is arguably a tool problem, the author of a doc generator would likely prefer not to assume the value when the spec author could rightly intend to provide a different reason phrase.
The x-summary ResponseObject extension provides a way to set the reason phrase.  More importantly, it unambiguously makes the ResponseObject description field appropriate for long form prose.  However, x-summary or summary aren't specific about what is being specified, it's just a short description.  While a summary attribute may be justifiable on its own merits, reasonPhrase is semantically unambiguous.
Examples
responses:
  '201':
    x-summary: Created
    description: |
      A new pet has been created.
      Once created, the pet will require care and feeding.
      This can be performed using the `/pets/{id}/care`
      and `/pets/{id}/feed` endpoints.
    content:
      application/json:
        schema:
          type: object
          properties:
            name:
              type: string

  '202':
    description: |
      A new pet will be created at some point in the future.
      If you don't want to wait, trying searching for a pet
      that already exists using `GET /pets?exists=true`.

Redoc demonstrates the ambiguity and the opportunity for better handling by having an additional attribute.  As can be seen in the image, the 201 example has associated a reason phrase taken from x-summary, and the description is rendered appropriately where the viewer would expect a description.  202 shows long-form description placed inline.  By having two separate fields, Redoc is able to articulate both the reason phrase and the description.

Can you expand a little on the benefit of having this additional property? ReDoc (for example) renders a commonly-accepted reason phrase for the various status codes, regardless of whether an x-summary or description field is present. So does swagger-ui.
Would the presence of a reasonPhrase mean that the response was only valid if that reason-phrase was sent? How would this work, given that duplicate status-code keys are not allowed in the responses object? Or is your use-case more for cases such as i18n?
It's also worth noting this text from RFC 7230:

The reason-phrase element exists for the sole purpose of providing a
textual description associated with the numeric status code, mostly
out of deference to earlier Internet application protocols that were
more frequently used with interactive text clients.  A client SHOULD
ignore the reason-phrase content.

and I believe HTTP/2 and QUIC/HTTP3 both drop the reason-phrase entirely. COAP similarly has no such field.

It's less a matter of functionality.  More about tying up a loose end in OpenAPI's ability to express flexibility that HTTP provides, and also about removing the ambiguity.  There are indeed two text fields to produce values for, but just one attribute (description) from which to draw.
There would be no ambiguity if generators assumed the standard reason string, as they probably will when working with HTTP 2, 3, and CoAP, but the example image, which matches example openapi objects, demonstrates the ambiguity in practice.  It came from Redoc 2.0.0-rc.50, the latest, and one can make several observations.

The generator does not assume the value of the reason phrase.
When provided the x-summary extension, it uses the value for the reason phrase.
The description field is rendered in a different place.  Instead of rendering inside the green box, it renders underneath, consistent with other description field rendering using the tool

Swagger Editor (and I assume Hub) does not render a reason phrase at all.  And it ignores x-summary, as you say.
In terms of having purely informational attributes, summary may be a good precedent.  Adding a summary field doesn't change the interpretation of an object, but it facilitates generation of documents, the short descriptions for operations in test tools, etc.  Likewise, reasonPhrase would be purely for presentation.

Would the presence of a reasonPhrase mean that the response was only valid if that reason-phrase was sent?

I would expect the client to obey RFC7230 and use only the status code to interpret the semantics of the response.

How would this work, given that duplicate status-code keys are not allowed in the responses object?

I would imagine no change.  The status code would be the key.

Or is your use-case more for cases such as i18n?

Drivers for me are a) to remove the ambiguity for doc generators and b) to support HTTP 1.1's flexibility for this value.  I can't cite drivers for HTTP's flexibility beyond what you've already provided, but support for non-English users may have been one.  Since the reason phrase is pretty much just ASCII, there is limited opportunity for non-English support.
If not reasonPhrase, a summary field would also reduce the ambiguity without tying directly to the HTTP feature.

I quote @MikeRalphson for this issue. Moreover an API MUST NOT be tied to a specific HTTP messaging version (1.1, 2.0, 3.0) because you do not have any guarantee that a proxy does not translate a message to HTTP/2.
I'd avoid to re-state HTTP stuff in your APIs: this would need to be done on every single response...


Minor css issue for bottom CosmicDS icon

This issue appeared in #175, but I went ahead and merged it, so we still have to fix it.
If you hide and reopen the top content (with the map), a gray overlay appears on top of the CosmicDS logo.

This issue is that when double-clicking to select on a page, the browser selects something according to some rule. In https://github.com/cosmicds/minids/pull/178/commits/e7b62b6ea9a8d8566be92e42c6f4448a0233d1c5 on #178 I disable user-select to prevent clicking near the buttons.


refactor(blockifier_reexecution): refactor retry config params

This change is

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

#1920  👈
#1905 : 1 other dependent PR (#1906 )
#1902
main

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

Join @AvivYossef-starkware and the rest of your teammates on  Graphite


[WIP] Attempt to use single submit file template with dag

Want to see if it's possible to use a single Job submit file when using a Dagman

@jrbourbeau How is the progress of this PR?  We are interested using pycondor to build a dag with over hundreds of thousands nodes.  Many nodes will have the same executable with different arguments.  So it makes sense to generate one submit file and specify different arguments in the dagman submit file.
We are happy to help implement this feature.  I wonder if you can shed some lights where we should make changes in.

@ChromeHearts Thanks for asking about this, I really appreciate your interest!
Unfortunately I've been distracted with other things and haven't worked seriously on this PR in a couple months. However, as you've pointed out, I think having a single job submit file could be really useful when a dagman has many nodes.

We are happy to help implement this feature. I wonder if you can shed some lights where we should make changes in.

That's great! For now I'd like to have a separate dagman object, perhaps a TemplatedDagman (suggestions for a better name are welcome : ) ) to avoid breaking changes for users who might rely on having a submit file for each Job. The TemplatedDagman.build() method needs to create a single Job submit file with variables for each Job attribute. For example, something like
# Job submit file
executable = $(executable)
arguments = $(arguments)
request_memory = $(request_memory)
request_disk = $(request_disk)
...

and then create a dagman submit file that fills in those variable values for each Job it is managing.
# Dagman submit file
JOB job1_name /path/to/job_template.submit
VARS job1_name executable="my_script.py"
VARS job1_name request_memory="3GB"
JOB job2_name /path/to/job_template.submit
VARS job2_name executable="my_other_script.py"
VARS job2_name arguments="--some-option"

The construction of the Dagman submit file lines happens here
https://github.com/jrbourbeau/pycondor/blob/80f8a6cf5f60397c0d3766283c34464bae2f8c5f/pycondor/dagman.py#L306-L322
Specifically the _get_job_arg_lines method would need to be changed for the TemplatedDagman.

@jrbourbeau Thanks for your prompt reply and help!
I started from your branch and found it's needed one change to fully work.  When a job had no arguments, no VAR_ATTR would be generated.  I made the code changes.  Then I was able to generate a DAG with 20k+ individual jobs in a single submit file and run successfully in condor.
Of course, it needs to be backward compatible.  Another way to do this is to take another argument in build, eg. dagman.build(single_file=True) or dagman.build(file_mode=SINGLE).   This argument will eventually transverse to _get_job_arg_lines().  I prefer this way because there will be less client APIs (less documentation)

Thanks for your work on this @ChromeHearts! Would you like to open up a new PR with these changes, or are you okay with me adding them to this existing PR?

Another way to do this is to take another argument in build, eg. dagman.build(single_file=True) or dagman.build(file_mode=SINGLE)... I prefer this way because there will be less client APIs (less documentation)

Good point. I like that way too : )


fix: correctly handle http status codes other than 2xx

fixes #4

This looks great! You tested that it works? @d-Rickyy-b

@d4v3y0rk yes, works on my machine :D. On a more serious note: I have only been able to test the status() method (1. with wrong credentials forcing a 401 and 2. with correct credentials). But since it worked without issues I'd assume there won't be any issues for the other methods.
Although I can still test the other methods tonight or in the coming days.


Divide by zero warning?

Hi Peter,
Thank you for developing the powerful tool. Unfortunately I have some issue while applying it to my data, and could you please take a look on it? My python version is 3.6.2 and all my site packages are up to date.
gmm_logL(simu,20)
The function gmm_logL is:
def gmm_logL(simu, K = 10):     #calculate log likelihood of GMM fitting for different K
    logL = []
    if type(K) is list:
        K_list = K
    else:
        K_list= list(np.arange(1,K+1))
    for i in K_list:
        start = time.time()
        try:
            gmm = pygmmis.GMM(K=i, D=len(simu[0]))
            logl, U = pygmmis.fit(gmm, simu, w = 1e-6)
            logL.append(logl)
        except Exception and RuntimeWarning:
            print('There is an error with K = %d' %(i))
            K_list.remove(i)

        print("Time used for K = %d is %gs, min amplitude is %g" % (i,(time.time() - start),np.min(gmm.amp)))
    plt.plot(K_list, logL, linewidth = 5)
    plt.title('Log likelihood of GMM fitting')
    plt.xlabel('$K$')
    plt.ylabel('$log-likelihood \lnU$')
    plt.show()

and the file for simu is as below:
simulation100000.txt
you can simply use simu = np.loadtext('simulation100000.txt') to load it.
I ran the code as above in ipython console and the trace back log is as below:
D:\Anaconda\lib\site-packages\pygmmis.py:910: RuntimeWarning: divide by zero encountered in log
  log_S[H] = np.log(log_S[H])

D:\Anaconda\lib\site-packages\pygmmis.py:153: RuntimeWarning: invalid value encountered in add
  return np.log(np.exp(logX + c[c_shape]).sum(axis=axis)) - c

D:\Anaconda\lib\site-packages\pygmmis.py:766: RuntimeWarning: invalid value encountered in greater
  moved = np.flatnonzero(shift2 > shift_cutoff)

D:\Anaconda\lib\site-packages\numpy\linalg\linalg.py:1741: RuntimeWarning: invalid value encountered in slogdet
  sign, logdet = _umath_linalg.slogdet(a, signature=signature)
D:\Anaconda\lib\site-packages\numpy\linalg\linalg.py:1741: RuntimeWarning: invalid value encountered in slogdet
  sign, logdet = _umath_linalg.slogdet(a, signature=signature)
D:\Anaconda\lib\site-packages\numpy\linalg\linalg.py:1741: RuntimeWarning: invalid value encountered in slogdet
  sign, logdet = _umath_linalg.slogdet(a, signature=signature)
D:\Anaconda\lib\site-packages\numpy\linalg\linalg.py:1741: RuntimeWarning: invalid value encountered in slogdet
  sign, logdet = _umath_linalg.slogdet(a, signature=signature)

above are the runtime warnings I've got while running gmm_logL(simu,20), and it stopped at here seems to fall into a infinite loop for more than 2 hour. So I pressed ctrl+c to stop it:
and it didn't stop directly but stop after generating these information:
^C
Process SpawnPoolWorker-7:
Process SpawnPoolWorker-6:
Process SpawnPoolWorker-5:
Process SpawnPoolWorker-3:
Process SpawnPoolWorker-2:
Process SpawnPoolWorker-1:
Process SpawnPoolWorker-4:
Process SpawnPoolWorker-8:
Traceback (most recent call last):
  File "D:\Anaconda\lib\multiprocessing\process.py", line 249, in _bootstrap
    self.run()
  File "D:\Anaconda\lib\multiprocessing\process.py", line 93, in run
    self._target(*self._args, **self._kwargs)
  File "D:\Anaconda\lib\multiprocessing\pool.py", line 119, in worker
    result = (True, func(*args, **kwds))
  File "D:\Anaconda\lib\multiprocessing\pool.py", line 44, in mapstar
    return list(map(*args))
  File "D:\Anaconda\lib\site-packages\parmap\parmap.py", line 116, in _func_star_many
    **func_items_args[3])
  File "D:\Anaconda\lib\site-packages\pygmmis.py", line 932, in _Esum
    dx = d_ - gmm.mean[k]
KeyboardInterrupt
Traceback (most recent call last):
Traceback (most recent call last):
Traceback (most recent call last):
Traceback (most recent call last):
Traceback (most recent call last):
  File "D:\Anaconda\lib\multiprocessing\process.py", line 249, in _bootstrap
    self.run()
  File "D:\Anaconda\lib\multiprocessing\process.py", line 249, in _bootstrap
    self.run()
Traceback (most recent call last):
  File "D:\Anaconda\lib\multiprocessing\process.py", line 93, in run
    self._target(*self._args, **self._kwargs)
  File "D:\Anaconda\lib\multiprocessing\process.py", line 249, in _bootstrap
    self.run()
  File "D:\Anaconda\lib\multiprocessing\process.py", line 249, in _bootstrap
    self.run()
  File "D:\Anaconda\lib\multiprocessing\process.py", line 249, in _bootstrap
    self.run()
  File "D:\Anaconda\lib\multiprocessing\pool.py", line 108, in worker
    task = get()
  File "D:\Anaconda\lib\multiprocessing\process.py", line 93, in run
    self._target(*self._args, **self._kwargs)
  File "D:\Anaconda\lib\multiprocessing\queues.py", line 341, in get
    with self._rlock:
  File "D:\Anaconda\lib\multiprocessing\process.py", line 93, in run
    self._target(*self._args, **self._kwargs)
  File "D:\Anaconda\lib\multiprocessing\process.py", line 93, in run
    self._target(*self._args, **self._kwargs)
  File "D:\Anaconda\lib\multiprocessing\pool.py", line 108, in worker
    task = get()
  File "D:\Anaconda\lib\multiprocessing\process.py", line 249, in _bootstrap
    self.run()
  File "D:\Anaconda\lib\multiprocessing\synchronize.py", line 96, in __enter__
    return self._semlock.__enter__()
  File "D:\Anaconda\lib\multiprocessing\pool.py", line 108, in worker
    task = get()
  File "D:\Anaconda\lib\multiprocessing\pool.py", line 108, in worker
    task = get()
  File "D:\Anaconda\lib\multiprocessing\queues.py", line 341, in get
    with self._rlock:
  File "D:\Anaconda\lib\multiprocessing\process.py", line 93, in run
    self._target(*self._args, **self._kwargs)
  File "D:\Anaconda\lib\multiprocessing\pool.py", line 108, in worker
    task = get()
  File "D:\Anaconda\lib\multiprocessing\queues.py", line 341, in get
    with self._rlock:
  File "D:\Anaconda\lib\multiprocessing\process.py", line 93, in run
    self._target(*self._args, **self._kwargs)
  File "D:\Anaconda\lib\multiprocessing\queues.py", line 341, in get
    with self._rlock:
  File "D:\Anaconda\lib\multiprocessing\queues.py", line 341, in get
    with self._rlock:
  File "D:\Anaconda\lib\multiprocessing\synchronize.py", line 96, in __enter__
    return self._semlock.__enter__()
KeyboardInterrupt
  File "D:\Anaconda\lib\multiprocessing\synchronize.py", line 96, in __enter__
    return self._semlock.__enter__()
  File "D:\Anaconda\lib\multiprocessing\pool.py", line 108, in worker
    task = get()
  File "D:\Anaconda\lib\multiprocessing\synchronize.py", line 96, in __enter__
    return self._semlock.__enter__()
KeyboardInterrupt
  File "D:\Anaconda\lib\multiprocessing\synchronize.py", line 96, in __enter__
    return self._semlock.__enter__()
KeyboardInterrupt
KeyboardInterrupt
KeyboardInterrupt
  File "D:\Anaconda\lib\multiprocessing\queues.py", line 341, in get
    with self._rlock:
  File "D:\Anaconda\lib\multiprocessing\synchronize.py", line 96, in __enter__
    return self._semlock.__enter__()
KeyboardInterrupt
Traceback (most recent call last):
  File "D:\Anaconda\lib\multiprocessing\process.py", line 249, in _bootstrap
    self.run()
  File "D:\Anaconda\lib\multiprocessing\process.py", line 93, in run
    self._target(*self._args, **self._kwargs)
  File "D:\Anaconda\lib\multiprocessing\pool.py", line 108, in worker
    task = get()
  File "D:\Anaconda\lib\multiprocessing\queues.py", line 342, in get
    res = self._reader.recv_bytes()
  File "D:\Anaconda\lib\multiprocessing\connection.py", line 216, in recv_bytes
    buf = self._recv_bytes(maxlength)
  File "D:\Anaconda\lib\multiprocessing\connection.py", line 306, in _recv_bytes
    [ov.event], False, INFINITE)
KeyboardInterrupt

Thank you for your time and patience!

Hi Jieyu,
I reproduced your problem. The root cause is in the first line of the traceback: it tells us that there's zero probability for some sample. This should be prevented by only evaluating the probability of each sample over the neighborhood H. In your case (the default configuration), this neighborhood comprises all samples, including some that may have very low probability under any of the GMM components. So, you've got a numerical underflow. I suspect that this happens because some components shrink very strongly.
Use the argument cutoff=5 in fit, which limits the evaluation to 5-sigma neighborhoods of each component (where each sigma refers to the covariance of the component). That prevents the underflow by ignoring samples that are too far away for any component and speeds up the process considerably. I just ran the full simu with K=10 in 5 seconds.
Another option is increasing the minimum component covariance w to something larger. 1e-6 doesn't help for the range your data cover.

Thanks for helping me out and for a quick reply!! Now it works fine for my model.


Minor update to the 'redactor' CLI command examples.

In the 'redactor' CLI command examples, this PR removes the equal signs from the --format options, to match options table in docs, where the option is specified as --format value.
It's better to keep examples and options tables consistent, to avoid customer/reader confusion.
Nevertheless, using an equal sign in this context, or not, should make no functional difference to the way this option is used.

Thanks @DrJosh9000 !
Just want to add a couple more tweaks to at least one of the related option descriptions, now that I've read them in a tad more detail ;-)


Added Option to provide selector for MouseAction

Added option to provide Selector with mouseAction.
Related #893

@jayandran-Sampath the tests are now failing for valid reasons:
https://github.com/getgauge/taiko/pull/951/checks?check_run_id=346234131
ReferenceError: element is not defined
            at mouseAction (/home/runner/work/taiko/taiko/lib/taiko.js:1614:18)
            at module.exports.<computed> (/home/runner/work/taiko/taiko/lib/taiko.js:3511:36)
            at Object.<anonymous> (tests/click.js:76:11)

I believe this is coming from https://github.com/getgauge/taiko/pull/951/files#diff-c626d926eeff4a14b1c1f5114bcc21c5R1614


How to get the selected country data after it is selected from the list?

I am trying to get the country name and its country two character code after a selection from the country flag list.
For now, I am using this code below because the selected data isn't available until after a country selection is made.  Is there a better way to get the country data after a selection is done?
$('.country').click(function(e) {{

    setTimeout(function() {{
        alert(  $("#country_selector").countrySelect("getSelectedCountryData")['name'] + ' ' +
        $("#country_selector").countrySelect("getSelectedCountryData")['iso2']  );
    }}, 2000);

}});

If you have a field for the plugin to set the country code, you could just use an on-change event for that field. The field will contain the 2-character code, and will be updated any time the user makes a new selection. That way there's no need for a wait on a timeout function, and you can grab the code directly, you'd only need to look to the other field for the country name.

For a little more clarity, here's a code example:
$('#country_selector_code').change(function(e) {{      alert( $("#country_selector").countrySelect("getSelectedCountryData")['name'] + ' ' + $("#country_selector_code").value ); }});

That was it, the jquery change function works great to select the country.  Thanks.

Great, glad to hear you've got it working. I'm going to close out this issue, then.


fix error: conflicting types for ‘dgesvd_’#177

Please take a look of #177.
And I'm aware of that if someone uses ubuntu 18.04 with LAPACKE 3.7.1-4ubuntu1.
It could happen the same error after we change it.
I recommend you to update the README.md such as how to fix it.
Or you could consider a better way to deal with this issue.

Use ariapoy/libact/ LAPACKE-dev branch is better and more clear.


Unclear how to allow 'style' attribute

To Reproduce
Use the following config for allowedAttributes:
allowedAttributes: {
      '*': ['style']
    }

and I just extended the allowed tags a bit...
allowedTags: sanitizeHtml.defaults.allowedTags.concat(['iframe', 'img', 'del', 'ins']),

Have a unit test with this input:
'
test
'

which after running through the sanitizer removes the style
"
test
"

Expected behavior
Style tag is removed from html. Shouldn't it be left in since I have wildcard and allow style attribute?
Describe the bug
Not sure if this is expected behavior or if my configuration is incorrect
Details
Version of Node.js:
12
Server Operating System:
linux

I ran into the same problem in react.  Version: "sanitize-html": "^2.4.0"
Test case:
    expect(
      sanitizeHtml("", {
        allowedTags: false,
        allowedAttributes: {
          span: ['style'],
        },
        allowedStyles: {
          span: {
            color: [/blue/],
            'text-align': [/left/],
          },
        },
      }),
    ).toEqual('');

Result:
    Expected: "\"
    Received: "\\"

      123 |         },
      124 |       }),
    > 125 |     ).toEqual('');
          |       ^
      126 |
      127 |     const setting = {
      128 |       allowedTags: false,

@maxcrane Have you found a clue to solve the problem？


Federate Community

Describe the feature
Function to explicitly federate a community. Can currently be done by:
data =<EMAIL_ADDRESS>
dataCommunity =<EMAIL_ADDRESS>
Resolve object needs an explicit ! before the community but get needs to exclude it.
Additional context
Why the feature would be useful or should be implemented
Can reduce code needed and make sure that communities can be found. Perhaps could be rolled into a try except in the get function and automatically federate it if it isnt found.

data will have the community information so an explicit get may not be necessary afterwards.


Initial Nix Support

This PR uses Crane to build the project with Nix. Currently, the tests (nix flake check) are failing because it found 2 vulnerable crates being used as dependencies. Additionally, the flake template I added has a bunch of convenient tests, which we can put into GitHub Actions and get effortless, declarative CI.
I'll add the NixOS module in a later PR.

Here is the failing check log:
cargoVendorDir not set, will not automatically configure vendored sources
cargoArtifacts not set, will not reuse any cargo artifacts
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking sources
unpacking source archive /nix/store/la4891v6kwq9kx6hix44xy95qanbn1ad-source
source root is source
@nix { "action": "setPhase", "phase": "patchPhase" }
patching sources
Executing configureCargoCommonVars
@nix { "action": "setPhase", "phase": "configurePhase" }
configuring
default configurePhase, nothing to do
@nix { "action": "setPhase", "phase": "buildPhase" }
building
++ command cargo --version
cargo 1.64.0
++ command cargo audit -n -d /nix/store/ndpc8wa7p6imzhd8zwayn12h8vd8hx8k-source
      Loaded 469 security advisories (from /nix/store/ndpc8wa7p6imzhd8zwayn12h8vd8hx8k-source)
warning: couldn't open crates.io index: registry: failed to resolve address for github.com: Temporary failure in name resolution; class=Net (12)
    Scanning Cargo.lock for vulnerabilities (403 crate dependencies)
Crate:     chrono
Version:   0.4.19
Title:     Potential segfault in `localtime_r` invocations
Date:      2020-11-10
ID:        RUSTSEC-2020-0159
URL:       https://rustsec.org/advisories/RUSTSEC-2020-0159
Solution:  Upgrade to >=0.4.20
Dependency tree:
chrono 0.4.19
├── shadow-rs 0.11.0
│   └── nu-command 0.64.0
│       └── nu-discord-bot 0.2.0
├── serenity 0.11.2
│   └── nu-discord-bot 0.2.0
├── reedline 0.7.0
│   ├── nu-command 0.64.0
│   └── nu-cli 0.64.0
│       └── nu-discord-bot 0.2.0
├── procfs 0.12.0
│   └── nu-system 0.64.0
│       └── nu-command 0.64.0
├── nu-system 0.64.0
├── nu-protocol 0.64.0
│   ├── nu-table 0.64.0
│   │   ├── nu-command 0.64.0
│   │   └── nu-color-config 0.64.0
│   │       ├── nu-command 0.64.0
│   │       └── nu-cli 0.64.0
│   ├── nu-parser 0.64.0
│   │   ├── nu-discord-bot 0.2.0
│   │   ├── nu-command 0.64.0
│   │   └── nu-cli 0.64.0
│   ├── nu-engine 0.64.0
│   │   ├── nu-discord-bot 0.2.0
│   │   ├── nu-command 0.64.0
│   │   └── nu-cli 0.64.0
│   ├── nu-discord-bot 0.2.0
│   ├── nu-command 0.64.0
│   ├── nu-color-config 0.64.0
│   └── nu-cli 0.64.0
├── nu-parser 0.64.0
├── nu-engine 0.64.0
├── nu-command 0.64.0
├── nu-cli 0.64.0
├── dtparse 1.3.0
│   └── nu-command 0.64.0
├── chrono-tz 0.6.1
│   └── nu-command 0.64.0
└── chrono-humanize 0.2.1
    ├── nu-protocol 0.64.0
    └── nu-command 0.64.0

Crate:     time
Version:   0.1.44
Title:     Potential segfault in the time crate
Date:      2020-11-18
ID:        RUSTSEC-2020-0071
URL:       https://rustsec.org/advisories/RUSTSEC-2020-0071
Solution:  Upgrade to >=0.2.23
Dependency tree:
time 0.1.44
└── chrono 0.4.19
    ├── shadow-rs 0.11.0
    │   └── nu-command 0.64.0
    │       └── nu-discord-bot 0.2.0
    ├── serenity 0.11.2
    │   └── nu-discord-bot 0.2.0
    ├── reedline 0.7.0
    │   ├── nu-command 0.64.0
    │   └── nu-cli 0.64.0
    │       └── nu-discord-bot 0.2.0
    ├── procfs 0.12.0
    │   └── nu-system 0.64.0
    │       └── nu-command 0.64.0
    ├── nu-system 0.64.0
    ├── nu-protocol 0.64.0
    │   ├── nu-table 0.64.0
    │   │   ├── nu-command 0.64.0
    │   │   └── nu-color-config 0.64.0
    │   │       ├── nu-command 0.64.0
    │   │       └── nu-cli 0.64.0
    │   ├── nu-parser 0.64.0
    │   │   ├── nu-discord-bot 0.2.0
    │   │   ├── nu-command 0.64.0
    │   │   └── nu-cli 0.64.0
    │   ├── nu-engine 0.64.0
    │   │   ├── nu-discord-bot 0.2.0
    │   │   ├── nu-command 0.64.0
    │   │   └── nu-cli 0.64.0
    │   ├── nu-discord-bot 0.2.0
    │   ├── nu-command 0.64.0
    │   ├── nu-color-config 0.64.0
    │   └── nu-cli 0.64.0
    ├── nu-parser 0.64.0
    ├── nu-engine 0.64.0
    ├── nu-command 0.64.0
    ├── nu-cli 0.64.0
    ├── dtparse 1.3.0
    │   └── nu-command 0.64.0
    ├── chrono-tz 0.6.1
    │   └── nu-command 0.64.0
    └── chrono-humanize 0.2.1
        ├── nu-protocol 0.64.0
        └── nu-command 0.64.0

Crate:     ansi_term
Version:   0.12.1
Warning:   unmaintained
Title:     ansi_term is Unmaintained
Date:      2021-08-18
ID:        RUSTSEC-2021-0139
URL:       https://rustsec.org/advisories/RUSTSEC-2021-0139
Dependency tree:
ansi_term 0.12.1
└── lscolors 0.9.0
    └── nu-command 0.64.0
        └── nu-discord-bot 0.2.0

Crate:     dotenv
Version:   0.15.0
Warning:   unmaintained
Title:     dotenv is Unmaintained
Date:      2021-12-24
ID:        RUSTSEC-2021-0141
URL:       https://rustsec.org/advisories/RUSTSEC-2021-0141
Dependency tree:
dotenv 0.15.0
└── nu-discord-bot 0.2.0

Crate:     failure
Version:   0.1.8
Warning:   unmaintained
Title:     failure is officially deprecated/unmaintained
Date:      2020-05-02
ID:        RUSTSEC-2020-0036
URL:       https://rustsec.org/advisories/RUSTSEC-2020-0036
Dependency tree:
failure 0.1.8
└── pwd 1.3.1
    └── nu-path 0.64.0
        ├── nu-test-support 0.64.0
        │   └── nu-command 0.64.0
        │       └── nu-discord-bot 0.2.0
        ├── nu-parser 0.64.0
        │   ├── nu-discord-bot 0.2.0
        │   ├── nu-command 0.64.0
        │   └── nu-cli 0.64.0
        │       └── nu-discord-bot 0.2.0
        ├── nu-engine 0.64.0
        │   ├── nu-discord-bot 0.2.0
        │   ├── nu-command 0.64.0
        │   └── nu-cli 0.64.0
        ├── nu-command 0.64.0
        └── nu-cli 0.64.0

Crate:     net2
Version:   0.2.37
Warning:   unmaintained
Title:     `net2` crate has been deprecated; use `socket2` instead
Date:      2020-05-01
ID:        RUSTSEC-2020-0016
URL:       https://rustsec.org/advisories/RUSTSEC-2020-0016
Dependency tree:
net2 0.2.37
├── miow 0.2.2
│   └── mio 0.6.23
│       ├── notify 4.0.17
│       │   └── nu-command 0.64.0
│       │       └── nu-discord-bot 0.2.0
│       └── mio-extras 2.0.6
│           └── notify 4.0.17
└── mio 0.6.23

error: 2 vulnerabilities found!
warning: 4 allowed warnings found

It says
error: 2 vulnerabilities found!
warning: 4 allowed warnings found

Do you know which ones are the allowed warnings and which dependencies are causing the vulnerabilities?

chrono and time are the vulnerable ones, the rest are just deprecated.

failure's SEC report says it's a "critical" issue even though its just been deprecated; is that fine?

failure's SEC report says it's a "critical" issue even though its just been deprecated; is that fine?

It should still be fixed, but the more important ones are chrono and time, since they have actual vulnerabilities

I think updating all our dependencies will be enough; I don't see a dependency on chrono 0.4.19 from any of the nushell crates.
However, updating to the latest nushell crates gives me the following error, which I can't find anything on the internet about:
error: failed to run custom build command for `libproc v0.12.0`

Caused by:
  process didn't exit successfully: `/Users/tanishqkancharla/Documents/Projects/nubot/target/debug/build/libproc-3bd9e6f2288d83b0/build-script-build` (exit status: 101)
  --- stderr
  /Users/tanishqkancharla/.cargo/registry/src/github.com-1ecc6299db9ec823/libproc-0.12.0/libproc_rs.h:1:10: fatal error: 'libproc.h' file not found
  /Users/tanishqkancharla/.cargo/registry/src/github.com-1ecc6299db9ec823/libproc-0.12.0/libproc_rs.h:1:10: fatal error: 'libproc.h' file not found, err: true
  thread 'main' panicked at 'Failed to build libproc bindings: ()', /Users/tanishqkancharla/.cargo/registry/src/github.com-1ecc6299db9ec823/libproc-0.12.0/build.rs:9:10
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...

Got it working and updated the deps as much as I can; let me know if there's something else to be done.

Got it working and updated the deps as much as I can; let me know if there's something else to be done.

The tests still fail, but the package itsself builds. The PR is ready to merge, we can deal with the failing tests later.

Are you referring to the unit tests in this package? Or something else?

Are you referring to the unit tests in this package? Or something else?

I'm referring to the Nix tests, the one that audits the package along with everything else


METRON-1333 Ensure that ansible-docker can be used to build metron ( including rpms )

The ansible-docker container could be used to build metron ( even the rpms ) and run the ansible scripts. This is no longer true, as the new node ui projects have native compilation that requires c++ 11 support in gcc, and rpm build requires node to be installed ( not local installed as in the mvn packaging ).
Many users are having problems building metron on centos platforms, having this container available and functioning would be a great help.
This PR addresses this by:

installing devtoolset-2 into the container to get cpp 11
creating a .bash_profile for root that enables the devtoolset environment
installing node into the container since building rpms now requires node ( and not just the local node used during building in maven )
documenting building in container, as well as mapping local .m2 repo into the container

You can now build and test metron, including building the rpms.
Testing
Follow the steps in the read me and build metron:
mvn clean package
mvn clean package -DskipTests
mvn clean install && cd metron-deployment && mvn package -P build-rpms
Also, after building with the rpms, exit docker
and do full_dev with
vagrant --ansible-skip-tags="build" up  and verify that you can use vagrant with the doc built packaging and rpms.
Pull Request Checklist
For all changes:

[x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?
[x] Have you included steps or a guide to how the change may be verified and tested manually?
[x ] Have you run a build, test, build rpm set of builds in the container?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book?

Added above, adding as a comment to make sure it is seen

Also, after building with the rpms, exit docker
and do full_dev with
vagrant --ansible-skip-tags="build" up  and verify that you can use vagrant with the doc built packaging and rpms.

Tested via
cd /Users/jzeolla/metron-pr848
docker run -it -v /Users/jzeolla/metron-pr848:/root/metron ansible-docker:<IP_ADDRESS> bash
cd /root/metron
mvn clean package -DskipTests # Failure

Ran into
[ERROR] npm ERR! Linux 4.9.49-moby
[ERROR] npm ERR! argv "/root/metron/metron-interface/metron-config/node/node" "/root/metron/metron-interface/metron-config/node/node_modules/npm/bin/npm-cli.js" "run" "build"
[ERROR] npm ERR! node v6.2.0
[ERROR] npm ERR! npm  v3.8.9
[ERROR] npm ERR! code ELIFECYCLE
[ERROR] npm ERR<EMAIL_ADDRESS>build: `./node_modules/angular-cli/bin/ng build -prod`
[ERROR] npm ERR! Exit status 1
[ERROR] npm ERR!
[ERROR] npm ERR! Failed at the<EMAIL_ADDRESS>build script './node_modules/angular-cli/bin/ng build -prod'.
[ERROR] npm ERR! Make sure you have the latest version of node.js and npm installed.
[ERROR] npm ERR! If you do, this is most likely a problem with the metron-management-ui package,
[ERROR] npm ERR! not with npm itself.
[ERROR] npm ERR! Tell the author that this fails on your system:
[ERROR] npm ERR!     ./node_modules/angular-cli/bin/ng build -prod
[ERROR] npm ERR! You can get information on how to open an issue for this project with:
[ERROR] npm ERR!     npm bugs metron-management-ui
[ERROR] npm ERR! Or if that isn't available, you can get their info via:
[ERROR] npm ERR!     npm owner ls metron-management-ui
[ERROR] npm ERR! There is likely additional logging output above.
[ERROR]
[ERROR] npm ERR! Please include the following file with any support request:
[ERROR] npm ERR!     /root/metron/metron-interface/metron-config/npm-debug.log
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Metron ............................................. SUCCESS [ 18.059 s]
[INFO] metron-stellar ..................................... SUCCESS [  7.965 s]
[INFO] stellar-common ..................................... SUCCESS [01:27 min]
[INFO] metron-analytics ................................... SUCCESS [  0.012 s]
[INFO] metron-maas-common ................................. SUCCESS [ 10.648 s]
[INFO] metron-platform .................................... SUCCESS [  0.031 s]
[INFO] metron-zookeeper ................................... SUCCESS [  1.542 s]
[INFO] metron-test-utilities .............................. SUCCESS [ 42.995 s]
[INFO] metron-integration-test ............................ SUCCESS [ 40.759 s]
[INFO] metron-maas-service ................................ SUCCESS [ 10.431 s]
[INFO] metron-common ...................................... SUCCESS [ 46.535 s]
[INFO] metron-statistics .................................. SUCCESS [ 22.078 s]
[INFO] metron-writer ...................................... SUCCESS [ 33.132 s]
[INFO] metron-storm-kafka-override ........................ SUCCESS [  4.151 s]
[INFO] metron-storm-kafka ................................. SUCCESS [  2.083 s]
[INFO] metron-hbase ....................................... SUCCESS [ 16.480 s]
[INFO] metron-profiler-common ............................. SUCCESS [  5.086 s]
[INFO] metron-profiler-client ............................. SUCCESS [ 26.173 s]
[INFO] metron-profiler .................................... SUCCESS [ 56.438 s]
[INFO] metron-hbase-client ................................ SUCCESS [ 16.283 s]
[INFO] metron-enrichment .................................. SUCCESS [01:01 min]
[INFO] metron-indexing .................................... SUCCESS [ 22.402 s]
[INFO] metron-solr ........................................ SUCCESS [ 56.301 s]
[INFO] metron-pcap ........................................ SUCCESS [  5.602 s]
[INFO] metron-parsers ..................................... SUCCESS [01:09 min]
[INFO] metron-pcap-backend ................................ SUCCESS [ 35.876 s]
[INFO] metron-data-management ............................. SUCCESS [01:46 min]
[INFO] metron-api ......................................... SUCCESS [ 57.116 s]
[INFO] metron-management .................................. SUCCESS [ 14.077 s]
[INFO] elasticsearch-shaded ............................... SUCCESS [ 11.380 s]
[INFO] metron-elasticsearch ............................... SUCCESS [01:02 min]
[INFO] metron-deployment .................................. SUCCESS [  0.006 s]
[INFO] Metron Ambari Management Pack ...................... SUCCESS [  4.145 s]
[INFO] metron-contrib ..................................... SUCCESS [  0.015 s]
[INFO] metron-docker ...................................... SUCCESS [  5.673 s]
[INFO] metron-interface ................................... SUCCESS [  0.005 s]
[INFO] metron-config ...................................... FAILURE [04:55 min]
[INFO] metron-alerts ...................................... SKIPPED
[INFO] metron-rest-client ................................. SKIPPED
[INFO] metron-rest ........................................ SKIPPED
[INFO] site-book .......................................... SKIPPED
[INFO] 3rd party Functions (just for tests) ............... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 21:01 min
[INFO] Finished at: 2017-11-28T01:34:36+00:00
[INFO] Final Memory: 154M/394M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.3:npm (ng build) on project metron-config: Failed to run task: 'npm run build' failed. (error code 1) -> [Help 1]

More detail
0 info it worked if it ends with ok
1 verbose cli [ '/root/metron/metron-interface/metron-config/node/node',
1 verbose cli   '/root/metron/metron-interface/metron-config/node/node_modules/npm/bin/npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'build' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for prebuild, continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
9 verbose lifecycle<EMAIL_ADDRESS>PATH: /root/metron/metron-interface/metron-config/node/node_modules/npm/bin/node-gyp-bin:/root/metron/metron-interface/metron-config/node_modules/.bin:/root/metron/metron-interface/metron-config/node:/root/metron/metron-interface/metron-config/node:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:
10 verbose lifecycle<EMAIL_ADDRESS>CWD: /root/metron/metron-interface/metron-config
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', './node_modules/angular-cli/bin/ng build -prod' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec build script
14 verbose stack Error<EMAIL_ADDRESS>build: `./node_modules/angular-cli/bin/ng build -prod`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/root/metron/metron-interface/metron-config/node/node_modules/npm/lib/utils/lifecycle.js:245:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (/root/metron/metron-interface/metron-config/node/node_modules/npm/lib/utils/spawn.js:24:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:850:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /root/metron/metron-interface/metron-config
17 error Linux 4.9.49-moby
18 error argv "/root/metron/metron-interface/metron-config/node/node" "/root/metron/metron-interface/metron-config/node/node_modules/npm/bin/npm-cli.js" "run" "build"
19 error node v6.2.0
20 error npm  v3.8.9
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>build: `./node_modules/angular-cli/bin/ng build -prod`
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>build script './node_modules/angular-cli/bin/ng build -prod'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the metron-management-ui package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     ./node_modules/angular-cli/bin/ng build -prod
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs metron-management-ui
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls metron-management-ui
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

+1, this is awesome work thanks Otto.  Tested via
cd metron-deployment/packaging/docker/ansible-docker/
docker build -t ansible-docker:<IP_ADDRESS> .
docker run -it -v /Users/jzeolla/metron-pr848:/root/metron ansible-docker:<IP_ADDRESS> bash
cd /root/metron
mvn clean package -DskipTests # Success
mvn clean install && cd metron-deployment && mvn package -P build-rpms # Success
exit
cd ../../../vagrant/full-dev-platform/
vagrant --ansible-skip-tags="build,quick_dev" up # Success

@JonZeolla I would like to change the readme example to include the quick_dev skip.

Ahh sorry, missed that was in the docs as well.  Ok, looks good


Fix doublet filtering out non-doublets cells

The use of the mask was inverted. The adata[mask, :] was keeping the cells that are being predicted as doublets and filtering out the non-doublets cells
PR checklist

[x] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[x] Make sure your code lints (nf-core lint).
[x] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).

Only a single character and probably (hopefully) the largest but in the pipeline right now... Thanks for the PR!

Apparently, the tests take a lot longer now, as more cells make it through doublet filtering - will have to do further downsampling of the test data to make the tests fast again

Yes, apparently the SCVITOOLS_SCVI process is the bottleneck now. I think that the training can be accelerated using a GPU. I can try to implement it as an optional parameter

If you have strong motivation, you can - but be aware that in this case, we will also need a different environment definition that comes with CUDA drivers and everything. Also we have to tell workload balancers like slurm to utilize GPUs. I don't know yet how to do these things in an nf-core compliant way (maybe we will implement the first prototype here). However I have already done it for scvi outside of nf-core here.

Fixed test execution time via implementation of HVG selection (#70)


css

Hello,
Where can we find some css ? Is there a way to generate one with the library ?

I've just figured out that the library actually calls pygmentize, and I found some css.


Handle xero sdk exception in a right way

linting checks failed because, sdk isn't released, will re-run once they're released


"'disable_attachment': True" should hide the Attachments model in admin

Adding
SUMMERNOTE_CONFIG = {
...
    'disable_attachment': True,
}

still leaves the Attachments model visible in admin.
Arguably, the Attachments model should never have been created in the database in the first place!
See also #329

Sounds reasonable. :+1:

Fixed https://github.com/summernote/django-summernote/commits/main


BoilR: Add version 1.9.4

Added BoilR.
This manifest does not handle the persistence: (BoilR writes its settings to %APPDATA%/BoilR. I didn't know how to remap.)
It also used just uses the skewed version scheme of BoilR (having v.x.x.x Tags instead of vx.x.x). Since scoop will just work fine with it, I didn't bother writing a complex regex. This is also why the version number currently starts with a dot.

Closes #12171

[x] I have read the Contributing Guide.

/verify

@ZzzZeta Thanks for the excellent suggestions!


 HACS not working after reboot as HACS is also gone.

Expected behavior
Only remove the Alexa component.
System details

Home-assistant (0.111.4):
Hassio (No):

Logs
No logs

This is not something I can fix. You need to report this to HACS.


Culling render request

Is your feature request related to a problem? Please describe.
When we view a closed mesh, which is quite common for indoor scenes, the culling rendering is very useful.
Describe the solution you'd like
Just like the meshlab, we can add an option to cull the backface of the mesn
Describe alternatives you've considered
Additional context
Contribution

I think that would be pretty trivial to add, wdyt @Meakk ?

Yes, it's just a flag on the actors

Here's a file I create for testing: backface.zip
And the visualization in ParaView:

Front/Back display:

With backface culling:

In f3d:

From a related discussion on Discord we've also got an .obj file with cubes from @theuser021: backface-cubes.zip
MeshLab rendering options for reference:

single (back facing dark)
double (back facing same color as front facing)
cull (back facing not displayed)
fancy (two different colors)

Improved the issue.

Is anyone working on this? I would love to be able to help out + its a feature I really want to have!

Well go for it! Are you on discord already?
https://discord.f3d.app

Just joined! Thanks!

any news on this one @Raghav-B ?

@mwestphal
I'm really sorry, I completely missed your messages on Discord. I know this a really simple feature that can be added in a couple of hours but I really haven't had the bandwidth these past 2 months due to some personal issues. I would have really liked to help out with this but it would be better if you could assign this to someone else if you need this done timely.

No worries:)

Im working on it :)


grails: 4.1.0.M1 -> 5.1.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/grails/grails-core/releases.
meta.description for grails is: "Full stack, web application framework for the JVM"
meta.homepage for grails is: "https://grails.org/"
meta.changelog for grails is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/154vgxr9kaghxahmqdp9i3j45s8zng2y-grails-5.1.2/bin/grails had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 5.1.2 with grep in /nix/store/154vgxr9kaghxahmqdp9i3j45s8zng2y-grails-5.1.2
found 5.1.2 in filename of file in /nix/store/154vgxr9kaghxahmqdp9i3j45s8zng2y-grails-5.1.2

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
grails

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/154vgxr9kaghxahmqdp9i3j45s8zng2y-grails-5.1.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A grails https://github.com/r-ryantm/nixpkgs/archive/dd10ac6d9744b072e338dbe20be21ed31c066157.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/154vgxr9kaghxahmqdp9i3j45s8zng2y-grails-5.1.2
ls -la /nix/store/154vgxr9kaghxahmqdp9i3j45s8zng2y-grails-5.1.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

grails

Maintainer pings
cc @bjornfor for testing.

Result of nixpkgs-review pr 161800 run on x86_64-linux 1

1 package built:

grails


Better support for logged mailables

See this discussion: https://github.com/spatie/ray/discussions/77#discussioncomment-270875

Thanks!

Thanks!

Is there a way to disable sending mail to ray when using log mail driver?


Object store error handling

Is your feature request related to a problem? Please describe.
I observed S3 returned SlowDown error (caused by excessive delete requests to S3) in my recent benchmark. This caused both CN and compactor to panic and reveals two problems:

We don't have fine-grain control on the GC background task and thus it can affect foreground read/write. #4728 can help to reduce the delete qps to be 1000 times smaller but I think we still have potential risk here because the amount of GC SSTs can be large with min_sst_retention_time_sec to be 7days.
We don't have proper error handling for object store error. Specifically, for retriable and recoverable errors, we should trigger backoff + retry instead of panic to avoid crashing the cluster.

Describe the solution you'd like

Limit object store QPS for GC task.
Proper retry + error handling for object store error.

Describe alternatives you've considered
No response
Additional context

I think aws-sdk may already implement backoff + retry internally. We can check whether there is a misconfiguration from our side.

Could you upload more logs? It seems that the logs in the screenshot don't contain functions related to storage.

This is what happens when we reach the S3 prefix QPS limitation (link).  The problem should be mitigated after #4965 merged.

I think aws-sdk may already implement backoff + retry internally. We can check whether there is a misconfiguration from our side.

The aws-sdk has built-in retry logic for throttling errors and server-side errors. And the default retry times are 2. So we can increase the retry times a bit to mitigate the Slowdown errors.  cc @hzxa21

Does S3 has any doc to talk about how long the throttling will last with sufficient number of prefixes?  I think we can adjust the retry time and backoff delay accordingly. Also, in our case, should upper layer (user of object store) see the throttling error?

As far as I know, I didn't find docs about how long S3 will take to finish the scaling for high QPS. And I think we should not rely on this. So we may need to choose the backoff delay by ourselves. The default value in aws-sdk is 1 second and the comment for it is "Most services should work fine with the default duration of 1 second, but if you find that your requests are taking too long due to excessive retry backoff, try lowering this value".

should upper layer (user of object store) see the throttling error?

Since we cannot rely on the time needed by S3 to finish scaling, throttling errors still need to be thrown to upper layer.
And currently we have wrapped the SDK errors in the ObjectError.
impl<E> From<aws_sdk_s3::types::SdkError<E>> for ObjectError
where
    E: std::error::Error + Sync + Send + 'static,
{
    fn from(e: aws_sdk_s3::types::SdkError<E>) -> Self {
        ObjectErrorInner::S3(e.into()).into()
    }
}


HTTP listener returns empty response

Hi I am using a control plane-based dynamic configuration setup. I am trying to create an HTTP listener(not HTTPS), when I apply the configurations through the control plane, the config is correctly added to the envoy config. But when I send the HTTP request I get this
curl "http://test.something.com:9080/test-api-with-multiple-port-listener/v1.0.0/user/user123/playlist/watch-later"
I get this: curl: (52) Empty reply from server
This is the config dump [1] of this setup. Could someone help me why this behavior is occurring I could not find any problem in this dump that prevents a http request.
Thanks.
[1]: http-config.json

@Tharsanan1 better to have envoy log, you can run Envoy with parameter "-l debug"

@soulxu I've attempted it with debug-enabled deployment, but I don't see any logs related to this HTTP request in the logs. Usually, when we receive curl: (52) Empty reply from server, it means the server is listening for HTTPS, but we provided an HTTP request, correct? In this case, I intend to listen for HTTP requests, so I haven't added any transport_socket related configurations to the specific HTTP listener. I assume that will prompt Envoy to listen for HTTP requests. I hope we don't have to set any other special properties to specify that this listener should listen for HTTP, not HTTPS. Could you please take a look at the config dump and let me know if there are any issues with the configuration? Thanks.

@soulxu I found the problem. In the configuration I had "filter_chain_match" field. After removing that http started to work. Thanks. I ll close the issue


Japanese not handling repeat char correctly

Sample current result:

For text:
聞こえる行く先々

新品 あたいのBody
Singing mi nah tell nuh lie
金銀 あたいの価値

Also spaces being removed for some reason.

Fixed in develop for the "repeat" character.
Mecab is stripping space characters ... I didn't want to fix this one just yet as I think it's rare, and have enough to do.
Singing mi nah tell nuh lie parsed yields
Singing	5	45
mi	5	38
nah	5	38
tell	5	38
nuh	5	38
lie	5	38
	0	4
EOP	3	7

In release 3.5.5.


Ian Effendi intro

Hi all, I'm Ian Effendi. I'm starting my master's in Data Science and am excited to see where the program will go. I'll be joining this course from my home in the Bronx. I graduated last May from RIT with a degree in Game Design & Development and spent the last nine months making educational math games for kids with a small start-up in NYC.
My family has been impacted by the pandemic but we're making it work one day at a time. I hope to apply the skills I learn during this program to a career in data analysis for video game studios. Outside of RIT, I'm also a professional tax preparer, working at a firm that serves low-income clients in NYC to help file federal and state taxes.
If you utilize RIT's Writing Commons services (which are remote this year), you'll also see me on staff as a part-time Graduate Writing Consultant. It's my pleasure to meet you all (virtually)!

Nice to meet you @rimij405! I am a big fan of video games so please make good ones :)

Nice to meet you @rimij405! I am a big fan of video games so please make good ones :)


Long scan times with cut and paste

When we scan a barcode in from a barcode scanner, everything works normally and it pulls up a call number almost instantly.
If we cut and paste a barcode from a file into the scan field, the search takes much, much longer and sometimes even hangs. The search time is very variable but always longer than just scanning it in.
The barcodes are in a plaintext file generated by our handheld barcode scanner but other manually generated files and ones that have come from a CSV file seem to do it as well.
I don't remember ever noticing this before, but I went back to 8.1.0 and it does it.

Hmmm...that's interesting.  Even more odd is if, after pasting the barcode, you move your mouse pointer off the app before hitting , it works fast again.  @jessestn , do you see that behavior, too?

Yes, I just tried it. If the mouse pointer isn't over the app when enter, it seems to go about the normal speed.
Also, I didn't mention it before, but if you use the drop-down to "re-scan" a previously scanned barcode it also always took much longer, but moving the mouse pointer seems to fix that as well.
Weird.

I've replicated the problem back to 7.0. Will look into it for the next version.


MM-10369: configure api/ws subpath

Summary
Wire up api and ws to use any configured /subpath.
Ticket Link
https://mattermost.atlassian.net/browse/MM-10369
Checklist

[x] Ran make check-style to check for style errors (required for all pull requests)
[x] Ran make test to ensure unit and component tests passed
[x] Added or updated unit tests (required for all new features)

The changes for MM-10369 relied on MM-10368 anyway, and amounted to a single commit, so I just pushed that commit into https://github.com/mattermost/mattermost-webapp/pull/1348.


Typescript private/public constructor shorthand is not possible

Question about Next.js - with-typescript example
The problem is about using the shorthand notation to assign private/public object properties through private/public/protected constructor argument modifiers, which is perfectly valid typescript since a long time.
I've provided an example page using private/public constructor argument modifiers that do not seem to work in whatever typescript setup is included in @zeit/next-typescript.
You can find the example in my fork here:
https://github.com/Bennit/next.js/blob/canary/examples/with-typescript/pages/test.tsx
Is there a way to get this specific feature of typescript working? I'm thinking babel config or tsconfig extension.
It makes me wonder if there are other hidden things I shouldn't do in typescript to work in next.js's framework
Kind regards
Ben

next-typescript just implements @babel/typescript, so you can file an issue on the babel repository. If you want to use the older ts-loader downgrade next-typescript to a version below 1.0.0.


Inner abstract class not reported as mapped

Commit: https://github.com/JetBrains/intellij-community/commit/7655200f58293e5a30bf8b3cbb29ebadae374564
File: BreakpointManager.java

Also, MergeVariable Refactoring is not handled properly

@tsantalis
This is similar to https://github.com/pouryafard75/RM-ASTDiff/issues/4. The abstract class is declared inside the method body.

@pouryafard75
I fixed the issue, but do you have any idea why it is shown as moved?


PKG-5647

pyuca 1.2
Destination channel: defaults
Links

PKG-5647
Upstream repository
Upstream changelog/diff

Explanation of changes:

Added wheel to host
Added pip check test
Added metadata

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_69d_1e7f4u/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:21: patch_must_be_in_build: patch must be in build when source/patches is set.
===== Final Report: =====
1 Error and 0 Warnings were found


Promise in IE not defined

How can this bug be reproduced?

Install Axios
import axios from 'axios';
Fetch some data
    axios    .get(urlRequest)    .then((response) => {      let temp = parseInt(response.data.main.temp);      let weather = response.data.weather[0].id;      showWeather(temp, weather, el);    })    .catch((error) => {      console.log(error);    });

What did you expect to happen?
Should return correct data from API
What happened instead?
Promise is not defined in IE11
Please List the Following:

OS & version:  macOS 10.13.3 - tested on BrowserStack and Windows 10
Node version  : 8.9.4
FoundationPress version : 2.10.4
Foundation version  : 6.4.3

You need to add the polyfill according to the Axios repo.

axios depends on a native ES6 Promise implementation to be supported. If your environment doesn't support ES6 Promises, you can polyfill.

Source: https://github.com/axios/axios#promises


Feature ui

Feature-ui represents the most feature packed version of the program. I suggest a merge into develop for the purpose of updating the dev-branch.

I agree, feature-ui has essentially become develop which is not a good thing.

Go for it

Yes, this is great. In my modules of the software, 'game' and 'host' screens, there are no bugs. There is lacking UI but they are just cosmetic and will not hinder development on any other modules. Go for it.

Sounds like we are in agreement ! Updating develop with the UI feature will be a good step in improving the program and showcase the work that has been put in the project .


Touchpad gestures

[x] show windows
[x] switch terminals
[x] back / forward

Using libinput-gestures and gestures.


Can't save anything to storage

Current behavior
I get an error when trying to save anything but a string.
Expected behavior
To be able to save objects.
Repro steps
I tried saving the object from the docs:
const legacyStorage = new LegacyStorage()

type StorageModel = {
  user: {
    name: string
    age: number
  }
}

const storage = AsyncStorageFactory.create<StorageModel>(legacyStorage)

async function saveItem() {
  const myUser = {
    name: 'John',
    age: 22
  };

  await storage.set('user', myUser);
}

// Somewhere else...

saveItem()

Environment

Async Storage version: ^2.0.0-rc.2
React-Native version: 0.61.5
Platform tested: iOS
Logs/Error that are relevant:

WARN  [AsyncStorageLegacy] The value for key "user" is not a string. This can lead to unexpected behavior/errors. Consider stringifying it.
Passed value: [object Object]
Passed key: user

If I change StorageModel to
type StorageModel = {
  user: string
}

and stringify the object before saving, it works (and I can also read it back, as a string, of course). But that's not really what I'd expect 😞

@Krizzu correct me if I'm wrong but we currently do not have any plans to support this scenario. The only way we would be able to support this is if we stringified the object behind the scenes. This will however open up different issues like losing data. In my opinion, this behaviour is more explicit, and it puts the responsibility of correctly serializing objects on the consumer. If you have ideas on how we can solve this, we're open to suggestions.
Perhaps we can set expectations with better documentation?

Thanks for the quick reply!
Sadly, I don’t have too much JS experience to acknowledge all the implications of serialization and/or have any suggestions; I’d probably stringify it.
What about using an SQLite database, like on Android? If it’s possible there, should be possible here as well, since iOS supports it as well?

Perhaps we can set expectations with better documentation?

If it’s truly no way to do it, I suppose so, because that piece of code definitely looks like it should save 🙃

On Android, we do in fact use SQLite underneat. On iOS, we have a different solution. The issue is really the fact that everything has to be serialized at some point in JS before it is passed to the native side. This is currently how React Native works in general, not just AsyncStorage. This may change with the Fabric rewrite but I haven't really looked into it yet.
I find the MDN entry on JSON.stringify() is really useful. It has a section with examples on what gets returned (or doesn't) given different input.

Hmm, but for Android, doesn't a "serialization" happen to be able to save it in SQLite? Can't that same serialization logic be used for iOS too and use SQLite instead of documents?

@rolandleth Like @tido64 said - we don't serialize data implicitly, because of the data loss, so we rather expect to be given serialized data that we can store as string.
There's a work for v2 in progress, which allows for different storage implementation to be used. SQL for iOS would be something I'd look for in this version.

Oh, my bad, I misunderstood; I implicitly assumed (wrong) that because it's using SQLite, it's also serializing the data somehow.
What would serialization require/imply? Following the example in the issue/docs, what would need to happen to StorageModel to be saved and how would it have to be passed in?

In React Native, all communication between JS and native occur over a bridge. When AsyncStorage wants to send data to the native side, where the actual storing of data occurs, the data is handed to the bridge. The bridge will serialize the data, pass it to native, deserialize the data, then forward it to the appropriate native module. While the bridge does its best to preserve as much data as possible, there are certain types of data it cannot distinguish between, leading to loss of meta data and sometimes data itself. This is a limitation in React Native. AsyncStorage tries to work around this by requiring strings to be passed.
Since StorageModel is fairly simple, you can rely on JSON.stringify() to do the right thing.

OK, understood 👍🏻
Thanks for all the explanations!


support for django (htmldjango)?

Still have this problem (nvim v0.7).
Have filetypes = { "htmldjango", ... in config files.
It seems to be trying to do something, considering mode indicator blinking.

I really love this plugin, but this issue makes me disappointed.

Still have this problem (nvim v0.7).
Have filetypes = { "htmldjango", ... in config files.
It seems to be trying to do something, considering mode indicator blinking.

I really love this plugin, but this issue makes me disappointed.

I also have the same experience with @shket-228

Confirming that the issue still persists, it'd be good to reopen the issue. Or should I create a new one?

are you sure guys? try as following config
-- enable html parser in htmldjango file
local import_parsers, parsers = pcall(require, 'nvim-treesitter.parsers')
if import_parsers then
	local parsername = parsers.filetype_to_parsername
	parsername.htmldjango = 'html'
end

local import_tag, autotag = pcall(require, "nvim-ts-autotag")
if not import_tag then return end
autotag.setup({
	autotag = {
		enable = true,
	},
	filetypes = {
		'html', 'htmldjango',
	},
})

@shaeinst Thanks a lot, enabling html parser for htmldjango filetype did the trick.
I think nvim-treesitter should do this by default. Will try opening an issue there, thanks again.

I'm still having problems.
I already have filetypes = { 'htmldjango', 'html', ... } in nvim-treesitter config.
I tried both lua require"nvim-treesitter.parsers".filetype_to_parsername.htmldjango = 'html' and lua vim.treesitter.language.register("html", "htmldjango") but none of these worked.
Only way I could get autotag to work is to set ft=html but this would cause LSPs to fail.

for neovim >= 0.9
-- safely import tree-sitter
local treesitter_imported_ok, treesitter =  pcall(require, 'nvim-treesitter.configs')
if not treesitter_imported_ok then return end

local register = vim.treesitter.language.register
register('html', 'htmldjango') -- enable html parser in htmldjango file

local import_tag, autotag = pcall(require, "nvim-ts-autotag")
if not import_tag then return end
autotag.setup({
	autotag = {
		enable = true,
	},
	filetypes = {
		'html', 'htmldjango',
	},
})

reference

@shaeinst , don't you lose syntax highlighting for the templating aspects of the htmldjango file?

Does this have a fix yet?
I am still facing the same issue. I tried all the solutions mentioned above in this thread. None of them worked.

Not sure what exactly this entails since I don't have much experience in Lua, but:
After hacking around for a little while I've found that removing "htmldjango" from the HBS_TAG.filetypes seems to do the trick. Perhaps it's overwriting the definition in HTML_TAG?
https://github.com/windwp/nvim-ts-autotag/blob/531f48334c422222aebc888fd36e7d109cb354cd/lua/nvim-ts-autotag/internal.lua#L69
It was last changed in this commit: https://github.com/windwp/nvim-ts-autotag/commit/25698e4033cd6cd3745454bfc837dd670eba0480 and I can't find the reason why.
Dunno if we should file this as a bug or if this has a reason to exist, but for the time being, to enable django support you can just remove it on line 69 of lua/nvim-ts-autotag/internal.lua.
@an4s911 @comiluv @shk3t @shaeinst you might find this helpful.

i still cannot get this working, i have tried all of the above and nothing. If anybody has fixed please post


alt-click to recursively expand component tree

Version
6.0.9
Browser and OS info
chrome LTS, windows 10
Steps to reproduce
open vue dev tools, go to Components tab, alt-click on arrow next to component, see that tree does NOT recursively open
What is expected?
tree to recursively open (was standard on devtools before Vue3 became default)
What is actually happening?
just opens 1 layer

please bring this feature back

feat: double click or enter key to expand current node


Example/config.sample is "Using deprecated database connection string!"

See also #907

@kuvaldini you mean the pg_opt?.. cause you said that the "database" one is up to date?

yes.

Iroha v1 is to be deprecated soon.


Fix web views not reloading when the extension host restarts (hot reloading)

Describe the bug
When you edit and save an extension or other source file, web views that are not opened immediately on startup (aka all the important ones) are not reloaded from their source. This failure hinders the functionality of hot reloading.
To Reproduce
Steps to reproduce the behavior:

Open Resource Viewer to some project
Change the source code for the resource viewer web view so some visual change occurs
Notice the resource viewer doesn't update.
Reload the page (Ctrl+R)
Notice the resource viewer is updated

Expected behavior
When changing source code, the web view should update appropriately.

is #928 happening because of this or is it something else?

I verified the fix with the latest code.

Open 'Open PAPI Menu Testscreen', webview is opened with the title PAPI Menu Test
Added a div with Webview Reload test
Verified that the webview is updated with hot reload.


feature/v1-070/responsive my courses

Responsive design for My courses page.
Responsive design for common Course component.
Different display of common component on Courses list and My courses pages for mobile devices.

We had lost menu arrow click area again)Its work only on current arrow

I didn't touch menu arrow in this branch. Problems with arrow are already fixed in develop and this branch was just created earlier


Remove hardcoding of trad_as_or_ru_name

What is the context of this PR?
Banished trad_as_or_ru_name!
The same behaviour is achieved through the use of a jinja filter display_first_valid_item, feel free to suggest a better name.
This filter can also be reused to return one of any number of arguments. The filter returns the first valid value. I didn't want to make this trad_as specifc, so for the purposes of trad_as_or_ru_name, trad_as must be passed before ru_name.
Trello
Author:
Spoke to @samiwel and he is happy for this to go in as is since it doesn't break author. A card also on thier backlog to allow this new style.
For the time being, authors will use ru_name instead. This ofcouse will mean, for the time being, a manual change is required.
How to review
Ensure:

New filter allows same behaviours as before without the hardcoded logic.
All references to the old style has been replaced with the new style. (Affects live surveys)
All trad_as_or_ru_name logic is removed from runner.

Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

@insacuri Can you re-review?


Remove element

IMPORTANT: Please do not create a Pull Request without an issue.
All Submissions:

[ ] I have read the CONTRIBUTING document.
[ ] My code is written in Python3 and is ending with .py
[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[ ] I have checked that my submission does pass the test on LeetCode.com
[ ] Does your filename follow the naming Conventions?
[ ] Have you linked your PR to an Issue?

Closing issues
Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if such).

Closed as SPAM - Problem/Issue already solved - Please read Contribution Guidelines before creating an PR!


Revert unproject_layout's action; use shape_touched in column optimization.

Should fix #314 and #313.
This reverts the action that unproject_layout and plugs the hole left behind by using the shape_touched attribute of the typetracer report. The only negative side-effect we have is converting to dask.array.Array is failing in tests because of a mismatch between a regular numpy array and a masked numpy array.

@lgray would you be able to torture test with this PR on top of the latest awkward and uproot releases?

Busy with other things today - but I can give it a shot later.

Busy with other things today - but I can give it a shot later.

of course always no rush :)

Codecov Report

Merging #317 (b7f3b69) into main (67e84fc) will decrease coverage by 1.49%.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main     #317      +/-   ##
==========================================
- Coverage   92.31%   90.82%   -1.49%
==========================================
  Files          21       21
  Lines        2564     2562       -2
==========================================
- Hits         2367     2327      -40
- Misses        197      235      +38

Impacted Files
Coverage Δ

src/dask_awkward/lib/optimize.py
93.99% <100.00%> (ø)

src/dask_awkward/lib/unproject_layout.py
12.50% <100.00%> (-32.59%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@douglasdavis so this gets coffea tests to pass again but overtouching is has run rampant again in my usual torture tests.

Closing in favor of #319


Which PyTorch Lightning version to use?

Hello, thanks for the great work!
I am trying to run your code, but there are issues with PyTorch Lightning (specifically the API changes very quickly).
If run with the latest version (1.6.5 at the moment), an error is thrown because val_dataloaders is not a valid argument for Trainer.validate:
https://github.com/Cuberick-Orion/CIRPLANT/blob/4592c979eb8638ccd0d8590a68507df26c27cb89/trainval_oscar.py#L271
However, if I revert to 1.3.1 (specified here), then an error is thrown as it cannot import lightning from pytorch_lightning.core (see full traceback below).
After some trial and error, I found 1.5.1 works. Perhaps this could be specified in the README?
P.S:
  File "/private/home/sgvaze/CIRPLANT/trainval_oscar.py", line 242, in <module>
    from _trainval_base import init_main
  File "/private/home/sgvaze/CIRPLANT/_trainval_base.py", line 34, in <module>
    from pytorch_lightning.core import lightning
  File "/private/home/sgvaze/miniconda3/envs/cirr/lib/python3.9/site-packages/pytorch_lightning/__init__.py", line 20, in <module>
    from pytorch_lightning import metrics  # noqa: E402
  File "/private/home/sgvaze/miniconda3/envs/cirr/lib/python3.9/site-packages/pytorch_lightning/metrics/__init__.py", line 15, in <module>
    from pytorch_lightning.metrics.classification import (  # noqa: F401
  File "/private/home/sgvaze/miniconda3/envs/cirr/lib/python3.9/site-packages/pytorch_lightning/metrics/classification/__init__.py", line 14, in <module>
    from pytorch_lightning.metrics.classification.accuracy import Accuracy  # noqa: F401
  File "/private/home/sgvaze/miniconda3/envs/cirr/lib/python3.9/site-packages/pytorch_lightning/metrics/classification/accuracy.py", line 18, in <module>
    from pytorch_lightning.metrics.utils import deprecated_metrics, void
  File "/private/home/sgvaze/miniconda3/envs/cirr/lib/python3.9/site-packages/pytorch_lightning/metrics/utils.py", line 22, in <module>
    from torchmetrics.utilities.data import get_num_classes as _get_num_classes
ImportError: cannot import name 'get_num_classes' from 'torchmetrics.utilities.data' (/private/home/sgvaze/miniconda3/envs/cirr/lib/python3.9/site-packages/torchmetrics/utilities/data.py)```

Hi sgaze,
Thanks for pointing it out -- indeed, the PytorchLightning API changes quite frequently. I will add the recommended version as 1.5.1 in README.
As a side note, for the most part, I found that the errors associated with API changes can usually be resolved with minor changes though. In the case of val_dataloaders, I believe the newer versions use the argument dataloaders instead.

Installation instruction updated at https://github.com/Cuberick-Orion/CIRPLANT/commit/a294f1900cfbf61307c501903963baf42e9d9ad3.


[Bug][Module Name] DruidDataSource exception:  physical connection to pool failed

**For better global communication, Please describe it in English. If you feel the description in English is not clear, then you can append description in Chinese(just for Mandarin(CN)), thx! **
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior, for example:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
DruidDataSourceput exception:  physical connection to pool failed
Which version of Dolphin Scheduler:
-[1.1.0-preview]
Dolphin Scheduler 1.3.2
Additional context
Add any other context about the problem here.
master-worker error  log:
[INFO] 2021-06-10 18:15:07.818 com.alibaba.druid.pool.DruidDataSource:[2615] - put physical connection to pool failed.
[INFO] 2021-06-10 18:15:07.826 com.alibaba.druid.pool.DruidDataSource:[2615] - put physical connection to pool failed.
[INFO] 2021-06-10 18:15:07.834 com.alibaba.druid.pool.DruidDataSource:[2615] - put physical connection to pool failed.
[INFO] 2021-06-10 18:15:07.841 com.alibaba.druid.pool.DruidDataSource:[2615] - put physical connection to pool failed.
[INFO] 2021-06-10 18:15:07.850 com.alibaba.druid.pool.DruidDataSource:[2615] - put physical connection to pool failed.
[INFO] 2021-06-10 18:15:07.858 com.alibaba.druid.pool.DruidDataSource:[2615] - put physical connection to pool failed.
[INFO] 2021-06-10 18:15:07.865 com.alibaba.druid.pool.DruidDataSource:[2615] - put physical connection to pool failed.
[INFO] 2021-06-10 18:15:07.875 com.alibaba.druid.pool.DruidDataSource:[1823] - connection recyle failed.
[INFO] 2021-06-10 18:15:07.881 com.alibaba.druid.pool.DruidDataSource:[2615] - put physical connection to pool failed.
[INFO] 2021-06-10 18:15:07.890 com.alibaba.druid.pool.DruidDataSource:[2615] - put physical connection to pool failed.
Requirement or improvement

Please describe about your requirements or improvement suggestions.

Can you provide more information about the stack?

The issue will be closed because no update for a long time. You can reopen it if need.

这是来自QQ邮箱的假期自动回复邮件。你好，我最近正在休假中，无法亲自回复你的邮件。我将在假期结束后，尽快给你回复。


ChemicalSystem difference method

User story
It would be good to have a method built into ChemicalSystem that checks how it differs from another ChemicalSystem and have it return a dict of list of components that are different.

May require some feedback from the protocol devs group. @ijpulidos do you have thoughts on the output data structure you'd like to see from this?

Note: not saying this is the right data structure, just how we're using this downstream.
In openfe, our chemical system difference method returns a dict[str, list[Component]] which is keyed as stateA and stateB and contains all the "unique" components for each state.
Maybe doing a tuple of bools would be better?


Docs: Fix packages URL on npmjs.org

Links to formatter packages on npmjs.org are currently leading to 404. :/
Doest this PR need a build or something?
Pull request checklist
Make sure you:

[x] Signed the Contributor License Agreement
[x] Followed the commit message guidelines

Thanks, @ffoodd!

Doest this PR need a build or something?

Once merge, it will trigger a rebuild of the website, so the site should be updated in a few minutes.

your*

Very efficient, thanks :)


Add hydration-free-energies/phenol

Add implicit and explicit solvent example as explicit-solvent.yaml and implicit-solvent.yaml

Fixed by #20