Fixes #1132 Enables add and delete transitions on state diagram

Fixes 1132, allows adding and deleting transitions on the UML state diagram. Changes are reflected in the umple code. By default, the new transition starts with event1.

@glorialaw   So test DeleteTransitionActionTest is failing.

I have fixed the test.

@glorialaw There are still some failures in cruise.umple.sync.DeleteTransitionActionTest

@glorialaw it seems to me you are not looking at the QA page generated when you do a full build, as you would see the failed tests before pushing. The page is found in dist/qa/

@TimLethbridge Thank you for letting me know about the QA page. When I manually test using the test cases using umpleonline they work but I am not sure why it is not working when the the test case. Is there a way to debug this?

@glorialaw Are you certain the test cases are all working on your platform. Just because it says the build successfully, it doesn't mean anything. You always have to check the QA page generated by your full build, and look for any listed errors or failures. The QA page tells you exactly how a given test failed. If you see nothing, then that is strange. I may need to run a build of your branch and check it out myself, or enable Appveyor to give you more details.

@glorialaw So I can easily reproduce the issues on my computer. I just do a quick build, and then run only the template tests using the following command.
ant -f build.umple.xml template.test

Then you look at the qa page. Here is the first failure
DeleteTransitionActionTest | Go_WrongDirectionTransition | Failure | Failed at:8 expected:< }[]> but was:< }[ ]>

This is simply saying that there is an extra space at this point.
The second failure is
DeleteTransitionActionTest | Go_LastTransition | Failure | Failed at:4 expected:< select[Drive -> driv]e;> but was:< select[Reverse -> revers]e;>

The wrong transition appears.
The third failure is similar
NewTransitionTest | Go_SameFromId | Failure | Failed at:4 expected:< []selectDrive -> drive...> but was:< [ ]selectDrive -> drive...>

I have fixed all the issues and verified with the QA now. Thanks for your help Tim!

Before I can merge this, we need a change so that
'Transition' only appears on the palette when in js mode, and otherwise is hidden. By the same token the other items should also be hidden in that mode. I may try to do this myself as really it should be consistent across all the modes.

This pull request is old and operates on state diagrams in Joint.js, but the code is OK, so I am merging it so it is not left behind. The feature is not activated, since considerable work on Joint,js is still needed


Feat: Add Cypress E2E Test for User Creation Workflow - 305

This PR implements a Cypress E2E test for the user creation workflow.
Closes #305

Let's test if we can remove the wait commands as @dhaselhan has suggested.

Sure, I removed the wait commands, and everything worked well. Thanks!


Create Posts “seo対策”

Automatically generated by Netlify CMS

👷 Deploy Preview for strong-beijinho-c4d917 processing.

Name
Link

🔨 Latest commit
51bd804f0c03ed1c67603c6b78ebf1860ef49c16

🔍 Latest deploy log
https://app.netlify.com/sites/strong-beijinho-c4d917/deploys/65ebea9d3a5ba70008ea13a1


Lock file is created when -dryrun is passed

Dryrun should mean the lockfile is not created even when a disk is above the threshold

Lock backend is an interface no, disk-usage should set the interface to something like /dev/null when -dryrun is passed. This way we do not need additional logic for func (c Config) getUsage() error in "disk-usage_unix.go" and "disk-usage_windows.go".


allocator: Correct batch logic

If an update to Raft did not succeed, the wrong object would potentially
be removed from the unallocated list. The logic that cleaned up the
unallocated list assumed that all updates to Raft succeeded, which is a
bad assumption to make.
This shouldn't have been a problem in practice, because there are only
two errors we would expect to see. One is ErrSequenceConflict, which is
handled in a way that shouldn't result in a second ErrSequenceConflict.
(Note that this way of overriding sequence conflicts is problematic, but
fixing it would be a somewhat large/risky change). The other possible
error is loss of leadership, in which case the allocator will be shut
down and retries become moot.
Even though the current code doesn't seem likely to lead to problems,
it's worth fixing the bogosity.
cc @ijc25 @aboch @yongtang

LGTM

Opened #2112 as an alternative proposal.

LGTM (with one minor comment which applies in a bunch of places), although I think #2112 is preferable since the number returned by Batch is, as you say there, pretty useless.

Closing in favor of #2112


Paraphraser demo error

I tried to run Paraphrasing with round-trip translation and mixture of experts demo and I have found that there is an error in user_dir path. If I leave it blank, the path to examples/translation_moe/src/ does not exist. And if I explicitly indicate the path to examples/translation_moe/translation_moe_src/ it throws an error
hydra.errors.ConfigCompositionException: Error merging override task.mean_pool_gating_network_dropout=null
How can I fix this? Thanks!

Hi @KyloRen1 this bug can be fixed with #3605

@cronopioelectronico thanks!


Connecting a component that uses new .contextType API breaks it in React Redux 4.x

The problem in https://github.com/reduxjs/react-redux/issues/1067 isn't fixed in react-redux@4 which is pinned to hoist-non-react-statics@2. Can we get a fix in there? Since some people can't migrate to 5 due to the perf regressions (for some use cases), and the error is very confusing. Thanks!

@timdorr , you got time to bump deps on v4?
@gaearon : do you have any info on how many people are still on v4, and why?  I remember the one issue filed by Twitter.  Anyone else?

Yeah, I can get to it soon.

Done: https://github.com/reduxjs/react-redux/releases/tag/v4.4.10

Thanks!

Anyone else?

FB in RN apps, at least. :P

Really.  Do you have any details on why they haven't upgraded to 5.x?

Probably just didn't have any incentives. Migrating from legacy context can be one.


Add Http.json: a helper method to encode arbitrary Json.Encode.Value as an Http.Body

Motivation
This snippet comes up often in our code base, which consists of various forms talking to an HTTP backend. It'd be nice if elm-http supported this out of the box.
Considerations

This function might fall out of scope for a bare minimum HTTP library. I couldn't find a suitable elm-http-extra package, so making a PR here to test waters : )

Naming: if we take after the simplicity of Http.string, Http.json is fine. However, Http.toJson might be better if we want it to contrast nicely with Http.fromJson.

Might be better to: (not sure if there is a well-established convention for aliasing Json.* imports)
import Json.Decode as JsonDecode
import Json.Encode as JsonEncode

Changes

Added json : Json.Encode.Value -> Body

:+1: @ento there's now a elm-http-extra. I don't think any of the methods there do this, but I might be wrong. cc @lukewestby

i'd love to have a withJsonBody in elm-http-extra. @ento if you'd like, can you submit a PR over there?

@lukewestby @eeue56 will do, thanks for the pointer. Closing in favor of the yet-to-be-made PR.


kubernetes + acme open traefik/acme/account: not a directory

Do you want to request a feature or report a bug?
bug
What did you do?
The following traefik.toml file is supposed to use the KV store (etcd here) to store the acme related stuff. But it doesn't do that. It instead tries to open this path in the file system, which obviously doesn't work.
time="2017-12-04T16:41:34Z" level=error msg="Error creating TLS config: open traefik/acme/account: not a directory"
time="2017-12-04T16:41:34Z" level=fatal msg="Error preparing server: open traefik/acme/account: not a directory"

What did you expect to see?
That traefik uses the KV store.
What did you see instead?
That it doesn't use it, breaking lets encrypt support.
Output of traefik version: (What version of Traefik are you using?)
1.4.2
What is your environment & configuration (arguments, toml, provider, platform, ...)?
apiVersion: v1
data:
  traefik.toml: |
    defaultEntryPoints = ["http", "https"]

    # get config from kubernetes ingress configs
    [kubernetes]

    # tell traefik where to get the TLS cert for api.rimoto.net
    [entryPoints]
      [entryPoints.https]
      address = ":443"
        [entryPoints.https.tls]
            [[entryPoints.https.tls.certificates]]
            CertFile = "certificate"
            KeyFile = "key"
      [entryPoints.http]
        address = ":80"
    [web]
    address = ":8080"
    ReadOnly = true

    [acme]
    email = "myemail"
    storage = "traefik/acme/account"
    entryPoint = "https"
    onHostRule = true
    acmeLogging = true

    [[acme.domains]]
   <internal stuff 1>
    [[acme.domains]]
   <internal stuff 2>

kind: ConfigMap
metadata:
  name: traefik-config

Logs:
time="2017-12-04T16:43:23Z" level=info msg="Using TOML configuration file /etc/traefik/traefik.toml"
legolog: 2017/12/04 16:44:44 [INFO] acme: Registering account for myemail
time="2017-12-04T16:44:45Z" level=error msg="Error creating TLS config: open traefik/acme/account: not a directory"
time="2017-12-04T16:44:45Z" level=fatal msg="Error preparing server: open traefik/acme/account: not a directory"

Hello @Thermi . Many thanks for you interest in the project.
How I understand your Træfik configuration, the ETCD configuration is missing into you traefik.toml file.
That's why Træfik generates this error message.
You can add this kind of configuration :
[etcd]
endpoint = "X.X.X.X:2379"
watch = true
prefix = "/traefik"

Note : if you migrate to the new release-candidate version (1.5-rc2), you will be able to use the ETCD V3 API by adding useAPIV3 = true to your ETCD configuration.
I close de issue but feel free to reopen it if it does not solve your problem.

That's sad. Accessing etcd is not supposed to be possible by pods, so if we were to use it, we would need to enable traefik to use authentication for connecting to etcd and also somehow configure etcd, which is not always possible (quite probably not with GKE). So we're stuck. Is there any other way to use the let's encrypt support with  Kubernetes? etcd is the only way for traefik to share the information. Maybe there is some native way on Kubernetes by using its API for sharing the certificates? Maybe by using specific secrets? I have not found any way to do this on Kubernetes yet. Am I missing something?

@Thermi WDYT about creating a pod which contains you ETCD (or other KV store) and allows Træfik to access to it?

@nmengin The etcd server of Kubernetes runs on the (or all) the master nodes. It is not a pod. The list of pods and the complete configuration of the cluster is stored in the etcd server. So one can't do what you propose. AFAIK by Kubernetes design, only the kubelet processes that each node runs are supposed to ever connect to the etcd server.

@Thermi how about rolling your own etcd cluster, possibly inside Kubernetes? AFAIK there's a Helm chart and the etcd operator available to ease the management.

@timoreimann I'd consider that the last resort. traefik already has the ability to do Kubernetes API calls, so why not use a configmap or secret for storing the secrets, too?

@Thermi I'm not too familiar with ACME. Is there a need to mutate any data that come with it? If no, then ConfigMaps or Secrets might be a viable option. Otherwise, we're probably better off with a real data storage solution.
Either way, Traefik currently does not support ACME from anything but a K/V store (like etcd) on Kubernetes. (@dtomcej, correct me if I I'm wrong here please.) This issue was about etcd in the first place, hence my suggestion to go with a dedicated cluster.
I totally don't mind considering a solution more tightly integrated with Kubernetes, but it should come as a separate feature request in my opinion.

The page about Let's Encrypt configuration states this
# File or key used for certificates storage.
#
# Required
#
storage = "acme.json"
# or `storage = "traefik/acme/account"` if using KV store.

The "storage" implies that it is actively written to, which kind of makes sense. In a clustered environment, the issued certificates need to be stored permanently and distributed somehow.
AFAIK kubernetes allows notifications to processes when a CM is changed. A secret likely, too. I guess it is a normal inotify mechanism caused by the simple replacement of the file. One could use that to get data from the other traefik processes. The only issue now is an atomic writing to the file via the Kubernetes API.
Well, I'll make a feature request as soon as we figure out what we can actually do to solve that.

@Thermi a ConfigMap/Secret is an object living on the Kubernetes API server, the file system is not involved. The notification mechanism is an event sent through to Traefik's Kubernetes client. The Kubernetes client library already comes with a leadership implementation which could serve as a way to do atomic writes.
There are likely a few other challenges to it, but it seems doable. Feel free to go ahead and file a feature request.

@timoreimann That is wrong.

@Thermi nice, I didn't know that. (Is that a newer feature by any chance?)
I wonder if we'd be able to benefit from this for free, or whether we need to make sure our version of client-go is up-to-date.

@timoreimann No, it's not new. It was like that since at least 1.4.
You can't write to configmaps, because they're read only, so at least some code for the writing is needed.
I suppose just updating the lib before the next build will be enough?

@Thermi yeah we can probably do that. Let's continue discussing in that to-be-created issue and make sure we keep track of the known/presumed requirements.

Closed in favor of #2542


Ngnix --set rbac.create=false is not working

Hello,
tried to set rbac.create false, getting error. Command:
helm install stable/nginx-ingress --namespace kube-system --set rbac.create=false
Error:
Error: release handy-pike failed: clusterroles.rbac.authorization.k8s.io "handy-pike-nginx-ingress" is forbidden: attempt to grant extra privileges
replacement with new values.yaml  is working fine.
Thanks,
Monika

I ran into the same issue. I did some digging and it looks like this is something that has been broken in the 0.19.0 release. I ran the following command multiple times, once for each version from 0.13.0 up to 0.19.0, and the last version where the flag was respected seems to be 0.18.0:
helm install stable/nginx-ingress --version 0.18.0 --name nginx-ingress --namespace ingress-nginx --set rbac.create=false,controller.publishService.enabled=true --dry-run --debug > nginx-ingress.0.18.0.log

I think I've maybe figured out what's going on here. In https://github.com/kubernetes/charts/pull/5169, a change was made that also defaults rbac.createRole and rbac.createClusterRole to true. So if I run the following command, I get the same behavior as before the change:
helm install stable/nginx-ingress --version 0.19.0 --namespace ingress-nginx --set rbac.create=false,rbac.createRole=false,rbac.createClusterRole=false,controller.publishService.enabled=true --dry-run --debug > nginx-ingress.0.19.0.log

Is this the intended behaviour? I also notice that these two options aren't listed in the configuration table on https://github.com/kubernetes/charts/tree/master/stable/nginx-ingress, and the default value for rbac.create is specified as false, even though it's now been changed to true.
I don't mind putting together a PR for the docs if that would help - I just am pretty new to Helm and Kubernetes, so I'm not completely sure I understand the options.

Confirmed, the key was:
--set rbac.create=false,rbac.createRole=false,rbac.createClusterRole=false

since one of the latest pull requests auto-set those to true without documenting.


flag to open a new simulator

add a -n flag or something similar to the react-native cli, so that i can run react-native run-ios --simulator "sim1" -n, which is the same as without the -n, and it opens a simulator sim1 that runs the app. afterwards, i can do react-native run-ios --simulator "sim2" -n and it opens a new simulator window, with my other simulator sim2, and runs some other app.
is there a way to do that now?

Duplicate: https://github.com/facebook/react-native/issues/10288


WATT crashes on sign out. Sad!

Seems to be some delay between auth.currentUser not existing and FirebaseUserDataProvider being unmounted or something.

This is a production crash. Should fix soon!

The weird thing is that it doesn't happen locally (at least with emulators running), so its hard to pin down. Will have to go based on the obfuscated react build output error message instead.

Errors on the null assertion of auth.currentUser.uid which is forced by the non nullable ref argument to useFirestoreDoc. I thought the first image would fix this? Is there something pausing unmounting which makes it still use FirestoreUserDataProvider even while auth.currentUser is null?

Thankfully closed in https://github.com/GunnWATT/watt/commit/6d2e5615f8308253330df905e5d50a710daf0e58.


Resize image

Hello,
I'm trying to resize an images but I don't find the right way to do it.
What I've tried in my markdown file:
![Google Logo](google_logo.png){ height=20% }

In any case, the image appears in Confluence (I've uploaded it manually), but it is not resized.
Many thanks for your help

md2conf uses Python-Markdown for converting Markdown to HTML (or, to be more precise, Confluence Storage Format, which is a variant of XHTML). Does Python-Markdown understand the seemingly non-standard syntax with the image height set in curly braces?
The ac:image macro to embed an attached or external image has attributes ac:height and ac:width. (We already use ac:align.) We could populate these attributes based on attributes the source image has.

Linking to images hosted externally via a full URL is now possible with either of the following syntaxes:
![External image](http://confluence.atlassian.com/images/logo/confluence_48_trans.png)

The latter syntax allows you to specify image size.

I wil try it, thank you very much :)


Bug: Join Query is not working in Library

Description
I think its a bug as well, using the query builder, the join query is not working! It gets only the table mention inside table()  i.e acl_roles_permissions, while in MySQL Manager I'm getting the result with join.
$db = \Config\Database::connect();
$res = $db->table('acl_roles_permissions')
     ->select('`acl_roles_permissions`.`role_id` as `permission_role_id`,`acl_roles_permissions`.`permission_id`, `permissions`.`key` as `permission_key`,`permissions.name` as `permission_name`')
     ->join('acl_permissions permissions', 'permissions.id = acl_roles_permissions.permission_id')
     ->where('acl_roles_permissions.role_id', $role_id);
if ($res->countAllResults() > 0) {
     print_r($res->get()->getResultArray());

Result of above code in the library

The same query runs inside MySQL manager.

CodeIgniter 4 version
4.0.4
Context

Windows 10
PHP version 7.2.19

You're using Builder class incorrectly and you're not creating the query you think of. Please read more about Builder class in the user guide: https://codeigniter4.github.io/userguide/database/query_builder.html#selecting-data
Hint - it should be:
...
$res = $db->table('acl_roles_permissions');
$res->select(...

You're using Builder class incorrectly and you're not creating the query you think of. Please read more about Builder class in the user guide: https://codeigniter4.github.io/userguide/database/query_builder.html#selecting-data
Hint - it should be:
...
$res = $db->table('acl_roles_permissions');
$res->select(...

Well I verified the query $res->getCompiledSelect();  the query I received is:
SELECT     acl_roles_permissions.role_id AS permission_role_id,     acl_roles_permissions.permission_id,     permissions.key AS permission_key,     permissions.name AS permission_name FROM     acl_roles_permissions JOIN acl_permissions permissions ON     permissions.id = acl_roles_permissions.permission_id WHERE     acl_roles_permissions.role_id = '1'
But I'm unable to get the result, of joined queries. Btw the Hint you gave is the same as my code,  Put the whole builder query in one statement.
For my problem I tried another way I used $db->query()
            $query = $res->getCompiledSelect();
            print_r($db->query($query)->getResultArray());

With this, I fixed my problem. But still, we can not get the result of the joined query using the code in my question. Please verify it once.

Yes, you're right, but still, it's not a bug. Please try:
if ($res->countAllResults(false) > 0) {
     print_r($res->get()->getResultArray());

Yes, you're right, but still, it's not a bug. Please try:
if ($res->countAllResults(false) > 0) {
     print_r($res->get()->getResultArray());

Again failed, its result is the same without join queries data.

Sorry that this is not working for you, but I actually build a similar join query locally and I was not able to recreate the issue you're describing. We also have tests in place and they work fine too.
Please post your problem in the Forum since it doesn't seem like a bug in the framework.


how to deal with the unlabel data with the dataiter?

hi, I want to load some labeled and unlabeled data into mxnet.
I follow the example https://github.com/dmlc/mxnet/blob/master/example/fcn-xs/data.py#L96 to create a dataiter.
how to implement the provide_label method for unlabel data?
Thanks for your attention.

Just return a dummy one

@winstywang  Thank you. could you please me some example  of that? :)

I don't see the need of example for this. Just return anything you want, and do not use it later.

I am also in trouble with this when I try to predict the text label.
In example, https://github.com/dmlc/mxnet/blob/master/example/cnn_text_classification/text_cnn.py#L124, the data was bind into the model in training.  But in prediction, the loaded model need to take DataIter type  data as input.

thank you

if my labels are 0 and 1,  so I could set the label = -1 for the unlabeled  data.
I want to put the label and unlabeled data to the model and only use the label of labeled data at the final layer.
I see #2403 said need to use the "ignore label". Is it an attr of sym?  How to use it?

@R1ncy you can set ignore_label in softmax loss, if the sample is with label=ignore_label, it will contribute to the gradient.

is it mx.sym.SoftmaxOutput(..use_ignore = True, ignore_label = -1)?
what if I want to use mx.sym.SVMOutput ?
seems svmoutput doesn't have ignore_label


Shortcut stfulConsumer is not working.

https://user-images.githubusercontent.com/51766366/144686627-28a531ba-e9e3-4b0f-b95c-b59eaac2cce2.mov

Thanks for finding the issue @kokikudo. I am currently building and publishing a new version, I will close when either you or I can verify it on the new 1.0.1 version

Verified and now works!

1

Verified and now works!

I don't think it works. I have tried a lot of times with different permutations, and I cannot get the snippet to work for me.

@pcelis19 at the beginning with the version of the extension it looks like you are using v1.0.0 but it should be v1.0.1. Update it and let me know if it works!

@RobertBrunhage So it started working on Windows. I started working on my Mac and the same issue occurred, and I looked at the available versions on VS code, and it only goes up to 1.0.0 not 1.0.1


Highlight row selection

Is there a way to highlight the whole row, when clicking on a cell?

we did that in cellProvider.getCell = (config) => {…}
and there we checked if the row should be coloured or not:
if (_.includes(this.selectedThings.map(o => o.thing), config.row.thing)) {
config.fgColor = '#ffffff';
config.bgColor = '#777777’;    //highlight the whole row.
}
we update the selection in the array “this.selectedThings” by hooking to the event “fin-selection-changed”
be aware that there can be multiple selections in the table with the “CTRL” Key.

On 13 Jan 2016, at 16:18, Kiril Minkov<EMAIL_ADDRESS>wrote:
Is there a way to highlight the whole row, when clicking on a cell?
—
Reply to this email directly or view it on GitHub https://github.com/openfin/fin-hypergrid/issues/88.

Thanks!


Recently changed varable in header or parameter values is reverted after sending a request

Expected Behavior
Whenever I make a request, I would expect for it to be sent with the visible info
Actual Behavior
If I replace a variable I am using for my query/header value, it will not be applied for the next request. Even clicking around sometimes do not make new variable to stick and it is reverted when sending
Reproduction Steps

Go to query parameters for a request
Replace one existing variable with another
Send request

Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
https://github.com/Kong/insomnia/assets/20520590/476cbf6c-57b1-4779-9b30-61822c7d0c7a
Additional issue I've seen is that opening variables now requires two clicks: first click fails and the box flickers and only the second click is working. Should I make additional issue for that?
Insomnia Version
9.3.2
What operating system are you using?
Other Linux
Operating System Version
Linux arch 6.9.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 05 Jul 2024 22:11:24 +0000 x86_64 GNU/Linux
Installation method
AUR
Last Known Working Insomnia version
No response

Can confirm I have the same issue on a Fedora 40 KDE installation. Running Insomnia 9.3.2 on Wayland

Thanks for the feedback @DusanLesan and @AdivonSlav. This is now fixed in the latest beta and will be released in the coming patch version!

@gatzjames Thanks!

@gatzjames Is this fixing additional issue mentioned?

Additional issue I've seen is that opening variables now requires two clicks: first click fails and the box flickers and only the second click is working. Should I make additional issue for that?


Any updates?

Hi any updates to this gem release? I see some changes committed but latest release is from 2012.
Thanks.

Hi.
0.2.0, I released in 2015.
https://rubygems.org/gems/thinreports-rails/versions/0.2.0

Thanks


HBASE-22902: At regionserver start there's a request to roll the WAL

We should call rollwriter after initialization of the config variables since Rollwriter eventually calls postSync which checks for if there is a need for rolling log based on rollOnSyncNs and slowSyncNs. So, everytime the FSLog is initialized it requests a log roll because the values of these two variables are zero. Moving this call after the initialization of variables.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
1m 14s
Docker mode activated.

_ Prechecks _

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

:green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

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

:yellow_heart:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-1 Compile Tests _

:green_heart:
mvninstall
8m 25s
branch-1 passed

:green_heart:
compile
2m  5s
branch-1 passed with JDK v1.8.0_222

:broken_heart:
compile
0m 21s
hbase-server in branch-1 failed with JDK v1.7.0_232.

:green_heart:
checkstyle
1m 44s
branch-1 passed

:green_heart:
shadedjars
3m  9s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
0m 36s
branch-1 passed with JDK v1.8.0_222

:green_heart:
javadoc
0m 41s
branch-1 passed with JDK v1.7.0_232

:blue_heart:
spotbugs
3m  2s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
2m 58s
branch-1 passed

_ Patch Compile Tests _

:green_heart:
mvninstall
2m  3s
the patch passed

:green_heart:
compile
1m 50s
the patch passed with JDK v1.8.0_222

:green_heart:
javac
1m 50s
the patch passed

:broken_heart:
compile
0m 22s
hbase-server in the patch failed with JDK v1.7.0_232.

:broken_heart:
javac
0m 22s
hbase-server in the patch failed with JDK v1.7.0_232.

:green_heart:
checkstyle
1m 40s
the patch passed

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

:green_heart:
shadedjars
3m  6s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
5m  9s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

:green_heart:
javadoc
0m 31s
the patch passed with JDK v1.8.0_222

:green_heart:
javadoc
0m 41s
the patch passed with JDK v1.7.0_232

:green_heart:
findbugs
3m  4s
the patch passed

_ Other Tests _

:broken_heart:
unit
150m 10s
hbase-server in the patch failed.

:green_heart:
asflicense
0m 30s
The patch does not generate ASF License warnings.

193m 50s

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestAdmin2

Subsystem
Report/Notes

Docker
Client=19.03.2 Server=19.03.2 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-668/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/668

JIRA Issue
HBASE-22902

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

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

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-668/out/precommit/personality/provided.sh

git revision
branch-1 / f77c14d

Default Java
1.7.0_232

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_222 /usr/lib/jvm/zulu-7-amd64:1.7.0_232

compile
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-668/1/artifact/out/branch-compile-hbase-server-jdk1.7.0_232.txt

compile
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-668/1/artifact/out/patch-compile-hbase-server-jdk1.7.0_232.txt

javac
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-668/1/artifact/out/patch-compile-hbase-server-jdk1.7.0_232.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-668/1/artifact/out/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-668/1/testReport/

Max. process+thread count
4266 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-668/1/console

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

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

This message was automatically generated.


Have support dynamic creating jcarousel?

if possible support dynamic create?
e.g.
var str = `

Test

test

                    ‹
                    ›

`;
$('#test').append(str);

Doesn't that work for you?
//...
$('#test').append(str).find('.jcarousel').jcarousel();

yes!
look like it's work, but I couldn't used prev/next button and picture doesn't cycle.

Yes, you need to use the control and autoscroll plugins.

Thank you, Is working!
BTW, if possible more interactive when I click image?
It can work before dynamically create jcarousel.
$('img').on('click', function(e){
     console.log('click!');
});

You can do that with delegated events:
$(document).on('click', '.jcarousel img', function(e){
     console.log('click!');
});

ok, thank you a lot.


Allow GDExtensions to add editor plugins

Fixes https://github.com/godotengine/godot-cpp/issues/640
This is an alternative to PR #65592 (but just the GDExtension part) based on some feedback that PR received from the GDExtension team back in December.
It adds two new functions to the GDExtensionInterface struct (editor_add_plugin and editor_remove_plugin) which both take a StringName representing a class registered in ClassDB (since all GDExtension classes need to be registered in ClassDB).
This is used in the companion godot-cpp PR: https://github.com/godotengine/godot-cpp/pull/1114
It allows you to use EditorPlugins::add_by_type<MyEditorPlugin>() in your GDExtension, in much the same way as you would in a module.
If this is called during Godot's initialization process, it's just adding the class name to a list, and the actual editor plugins will be created later in EditorNode::EditorNode(), in the same place the built-in editor plugins are created. If it's called after the editor is already initialized, then it'll call straight into EditorNode::get_singleton()->add_extension_editor_plugin().
This is currently a draft because:

I still need to do the godot-cpp changes and actually test it :-)
If PR #76406 is merged, then this'll need to get reworked to use the new way of registering GDExtension interface functions. That PR is more important, so I'm fine saving this one until that one is resolved.

For the moment, I'd mainly like to see what others think of this general approach!
UPDATE: This is now ready for review!

I've rebased this now that PR #76406 has been merged, made the companion godot-cpp PR (https://github.com/godotengine/godot-cpp/pull/1114) and actually tested that this works. :-)
This is now ready for review!

Discussed this with @dsnopek after last meeting. This seems like a sound solution within the constraints we currently have.
My only remaining remark is that this is worth a wider discussion around our limited access to singletons. The "proper" way for this is that we do have access to the EditorNode singleton during registration so we can register the plugin just like core modules do.
We can't because in the current approach we're piggy backing singleton access on singletons being registered with the scripting engine and this doesn't happen until all classes are registered.
Imho we should change this part of godot-cpp and make the actual get_singleton() functions of these classes callable from godot-cpp. That is potentially a breaking change on the API but worth it as now we will simply be able to call the correct functions.
cc @vnen

Thanks, @BastiaanOlij!
Just quick clarification on this point:

The "proper" way for this is that we do have access to the EditorNode singleton during registration so we can register the plugin just like core modules do.

Core modules actually don't access the EditorNode singleton during registration to add their editor plugins, because even for modules, the EditorNode singleton won't be created until later.
Modules register a creation function during registration (via EditorPlugins::add_by_type<>()), and then in EditorNode's constructor, it calls all the creation functions. This PR does basically the same thing, but instead of registering a creation function, it's registering the name of the class in ClassDB (and then EditorNode's construct creates them just like for modules).

Ah gotcha, so really in this case we should be use exposing static functions but thats not really possible in this case because it's using a template.
Sigh, some things just don't survive the bridge :)
Yeah I'm all ok with this going ahead. I just hope we get around to doing the other thing some day too :)

I am waiting for this, because until it isn't merged, it is impossible to create advanced plugins with GDExtension (
For now, I have compiled the engine with this PR by myself.

@dsnopek also i can't compile this PR with MSVC, I get this error:
.\core/extension/gdextension_interface_dump.gen.h(1589): fatal error C1091: compiler constraint: string length exceeds 65535 bytes
It compiles fine with MinGW. Should it be like this?

Also i get this error when i try to port my plugin
at: _editor_init (modules\gltf\register_types.cpp:71)
ERROR: Method 'EditorInterface.get_base_control' has changed and no compatibility fallback has been provided. Please open an issue.
at: gdextension_classdb_get_method_bind (core\extension\gdextension_interface.cpp:1043)

I tried to create simple 3d editor:
test_editor.h
`
#ifndef TEST_EDITOR_PLUGIN_H
#define TEST_EDITOR_PLUGIN_H
#include <godot_cpp/classes/editor_plugin.hpp>
#include <godot_cpp/classes/editor_interface.hpp>
#include <godot_cpp/classes/ref.hpp>
#include <godot_cpp/classes/input_event.hpp>
namespace godot {
class TestEditorPlugin : public EditorPlugin {
GDCLASSTestEditorPlugin EditorPlugin);
protected:
void _notification(int p_what);
public:
static void _bind_methods();

virtual int _forward_3d_gui_input(Camera3D* p_camera, const Ref<InputEvent>& p_event) override;
virtual String _get_plugin_name() const override { return "Terrain"; }
virtual bool _has_main_screen() const override { return false; }
virtual void _edit(Object* p_object) override;
virtual bool _handles(Object* p_object) const override;
virtual void _make_visible(bool p_visible) override;

TestEditorPlugin ();
~TestEditorPlugin ();

};
}
#endif
`
test_editor.cpp contains empty implementations.
When I start a project and create any node, the editor hangs without any errors in the console or anywhere.

also i can't compile this PR with MSVC, I get this error:

This was fixed in PR #77137 - I'll rebase this PR to include it in a moment.

When I start a project and create any node, the editor hangs without any errors in the console or anywhere.

Hm, I did an even simpler test when working on this, and that worked for me. Later, I'll try with your test class and see what happens.

@dsnopek Minimal reproduction project:
src.zip

Video:
https://github.com/godotengine/godot/assets/54563399/35b24c7d-539d-4519-b1ac-de6d5b4637e0
There are also some errors in the console, but they appear regardless of whether there is any extension or not. (And they don't seem to affect anything, because when no extension is added to the project, nothing is freezes.)

Thanks! I'm able to reproduce the issue with your MRP.
It seems to be related to the _handles(Object *) method: if I remove that method from the class, then the editor doesn't hang.
I'll see if I can debug further...

@anunknowperson The hanging appears to be a regression caused by this godot-cpp PR: https://github.com/godotengine/godot-cpp/pull/1044 - if I reverse the changes that were committed there, then it doesn't hang, and the editor starts up normally!
For the details: running the MRP in the debugger, it looks like we're hanging on _instance_binding_mutex.lock() in Object::get_instance_binding(). Stepping up through the stack trace and inspecting all the pointers, in the transition from Godot to godot-cpp we seem to end up in a state where we're treating a random chunk of memory as if it were an Object, but it definitely isn't. I think the mutex hangs forever because isn't actually a valid mutex.
A related PR for godot-cpp (https://github.com/godotengine/godot-cpp/pull/1045) caused a similar regression, where it fixed calling normal methods, but broke calling virtual methods. This looks to be the same thing! When calling virtual methods, Godot is passing an Object ** but godot-cpp (after the afformentioned PR) is treating it as Object *.
In any case, that bug is out-of-scope for this PR! As far as I can tell, this PR is correctly registering the editor plugin.

@dsnopek thanks!
In other words, to make it work for now, I need to revert #1044? Or will it add some new problems?

In other words, to make it work for now, I need to revert https://github.com/godotengine/godot/issues/1044?

Yes.

Or will it add some new problems?

Well, it did fix a legitimate bug, so you'll be getting that bug back, unfortunately. So, it really depends on if your project runs into that bug too.
The regressions from https://github.com/godotengine/godot/issues/1044 and https://github.com/godotengine/godot/issues/1045 are critical and need to get fixed before Godot 4.1. I'm personally planning to focus my attention on them after the feature freeze next week - until then, we gotta try and finish up any new features (like this editor plugin PR). After the feature freeze, we'll have another 4 weeks to work on bugs. :-)

Thanks!


galactica.phantom

[Request Id: 74f476be-e7f7-4f41-92c6-d66f21b44b00
Correlation Id: 97f7deb6-6de1-48c3-925f-51ee764c4b31
Timestamp: 2020-05-06T04:35:14Z
Message: AADSTS50020: User account<EMAIL_ADDRESS>from identity provider 'live.com' does not exist in tenant 'Microsoft Services' and cannot access the application 'ebf6b2b7-c635-4217-b6b7-21de4ac65764'(Dynamics 365) in that tenant. The account needs to be added as an external user in the tenant first. Sign out and sign in again with a different Azure Active Directory user account.](https://m.apkpure.com/es/laser-launcher-light-speedy/com.toprange.laser Laser Launcher - light&speedy for Android - APK - Download)@

Microsoft Store on Xbox
galactica.phantom


RTL language support in UserAccountsDrawerHeader

Including RTL language (e.g, Arabic) in the UserAccountsDrawerHeader , it does not appear the way it is supposed to, see the following code, Arabic in UserAccountsDrawerHeader is not properly displayed while it is correctly displayed in the ListTile
endDrawer: Drawer(
          child: ListView(
            children: <Widget>[
              UserAccountsDrawerHeader(
                accountEmail: Text("عربي",textDirection: TextDirection.rtl),
                accountName:  Text("عربي", textDirection: TextDirection.rtl,),
                currentAccountPicture: CircleAvatar(),
              ),
              new ListTile(title: Text("عربي",textDirection: TextDirection.rtl,),)
            ],
          ),
        ),

Dupe of https://github.com/flutter/flutter/issues/10719.

The two issue are not the same, actually the issue you mentioned is solved by now by including TextDirection.rtl , while my issue is specific to the UserAccountsDrawerHeader as you can see in my code even by including TextDirection.rtl, Flutter still display Arabic in the wrong way.

@shadyaziza I think it is the same problem internally :)

Yeah the underlying issue is the same. We don't quite measure Arabic text correctly. If it turns out that fixing #10719 doesn't fix this bug, we can reopen this one. :-)


Navbar is not responsive

Describe the bug
Navbar is not responsive for small-screen devices
To Reproduce
Steps to reproduce the behavior:

Go to 'website on small screen devices'
Click on the 'navbar icon'
See the error

Expected behavior
Navbar should be responsive on small-screen devices like mobile.
Screenshots

Can you work on this and make one PR for #36 and this?

@KendallDoesCoding
It will be great to differentiate different issues in different PRs as it is a good practice in open-source.
And sure, I'll work on this issue you may assign me.

@KendallDoesCoding
It will be great to differentiate different issues in different PRs as it is a good practice in open-source.
And sure, I'll work on this issue you may assign me.

Ok.


gpu scalar mul

Gpu scalar mul using a modified form of accel available on jon-chuang/accel

TODO: Get accel to wrap kernel_mod with a module of derived name. This is to separate namespaces and dependencies.
Alternatively, remove copy pasting of rest of content of kernel module... they should only be copy pasted in the target = nvptx crate.
Other TODO: Get accel to support compiling multiple functions at the same time...

TODO:

coprocess/load balance with CPU
batch table generation portion of gpu_scalar_mul

TODO:

More generic static partitioning to take into account multiple devices.

closed in favour of #17


Default minikube/knative memory/cpu configuration

I am having some trouble with the default values used to start minikube (3 GB memory/3 CPUs or 6GB memory/3CPUs - that's not clear which one). My troubles' source is that I have a very resources consuming use case, but while I was doing some search on the subject of minikube/knative I found this recommendation on minikube's documentation that recommends  6 CPUs and 8G memory.
I know that these values can be changed in the minikube config, but shouldn't the current default CPU/Mem values be changed to match the recommendation ?

Thanks for pointing out the discrepancies!
Our recommended at least 3 GB/cpus when running on minikube -- will work on getting all the docs to be in agreement. (the minikube docs rec looks to have been there for a while, probably back when Istio was a hard requirement, which ramped up the memory needs)
As for why 3 GB: we default to that in quickstart as that's the minimum that's needed to get an environment up and running with all the Knative components along with a couple of applications (for example, the ones from the tutorial). We err on the side of being low so that we won't break users with smaller machines. For example, if someone only has 8 GB of RAM, their cluster would never come up...
One last thing to note: quickstart really isn't meant for much more than a demo environment (i.e. not prod), so since you mentioned a resource-heavy use case just wanted to call that out in case you weren't aware.

Cool -- thanks again for pointing out the issue


Release v0.1.0a1

Component Interoperability Matrix

RSTUF API >= v0.1.1a1

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (833cafd) 94.86% compared to head (b6c0bce) 94.86%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #258   +/-   ##
=======================================
  Coverage   94.86%   94.86%
=======================================
  Files          13       13
  Lines         701      701
=======================================
  Hits          665      665
  Misses         36       36

Impacted Files
Coverage Δ

repository_service_tuf/__version__.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Fixed FutureWarning

TimedeltaIndex construction is deprecated and will be removed in a future version.

Rebase and change target to dev branch, easy #1084


Redux toolkit

You can cut down quite a bit of your state management boilerplate by using the now recommended redux toolkit

Hi @garrettjoecox, thanks for the suggestion.
I've chosen the "old" redux on purpose in order to learn the basic version since it's my first React/Redux project. It might help me in the future if I will work on projects built with the older version.
Another important reason about my choice is that when I will use the RTK version I will instantly see and understand the major differences with the older version.
Thanks anyway!
Davide


Bugfix: Empty Participant Metric Details

Expected Behavior
When no participant-metric is selected, the table at the bottom of Participant Details should tell the user to select a metric table.
Current Behavior
As of #210, we show an empty table when no details are selected.
Possible Solution
Need to update mod_DataTableCard_UI() and mod_DataTableCard_Server() to deal with the empty state. Note that it should swap out the UI entirely when there isn't data.
Steps to Reproduce

Context (Environment)

Possible Implementation

Additional Comments

I'm leaning toward the "right" answer for this being another module "in between" the mod_ParticipantDetails_*() (the tab) and mod_DataTableCard_*() (the table). THAT module is what owns the switch between out_Placeholder() and a full-on module, and it passes on the value that's returned from mod_DataTableCard_Server() when/if that makes sense.


[ZEPPELIN-1695] Use shared versions in test libraries (maven)

What is this PR for?
Use shared test library versions in maven config so that lib versions do mot be fragmented.
Previously we used multiple versions of

Junit (4.11, 4.12)
mockito (1.9.0, 1.10.8, ...)
powermock (...)

What type of PR is it?
[Improvement]
What is the Jira issue?
ZEPPELIN-1695
How should this be tested?
Use this command to see test libraries share versions or not
$ mvn org.apache.maven.plugins:maven-help-plugin:2.2:effective-pom | vim -

Questions:

Does the licenses files need update? - YES, I updated JUnit version to 4.12 from 4.11
Is there breaking changes for older versions? - NO
Does this needs documentation? - NO

LGTM

LGTM!

Looks great to me, thank you @1ambda for valuable build improvements!
Merging to master if there is no further discussion.


xorg-docs: build a bottle for Linuxbrew

While building libxslt:
/usr/bin/ld: cannot find -lz
collect2: error: ld returned 1 exit status

Ah man. I just merged the libxslt bottle :frowning:

I've traced the zlib link to libxml2. This is kind of weird though. From libxml2's website:
What other libraries are needed to compile/install libxml2 ?

Libxml2 does not require any other library, the normal C ANSI API should be sufficient (please report any violation to this rule you may find).

However if found at configuration time libxml2 will detect and use the following libs:

    libz : a highly portable and available widely compression library.
    iconv: a powerful character encoding conversion library. It is included by default in recent glibc libraries, so it doesn't need to be installed specifically on Linux. It now seems a part of the official UNIX specification. Here is one implementation of the library which source can be found here.

@sjackman, I'm going to add a depends_on "zlib" => :recommended if OS.linux? to libxml2. We can worry about libiconv later, since it doesn't build correctly at the moment.

Either way though, this isn't actually the major problem here. The major problem is that it can't find various external entities:
I/O error : Attempt to load network entity http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd
warning: failed to load external entity "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
validity error : Could not load the external subset "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"
Document /tmp/xorg-docs-20160514-22943-bh592y/xorg-docs-1.7/general/fonts/fonts.xml does not validate

It also complains in several places that it doesn't know what nbsp means.

We're running into #11 here. We can worry about this some other time; this isn't blocking the X11 requirement.

Error: JAVA_HOME is not defined correctly.
  We cannot execute java
/tmp/xmlto.eXNzwr
Error: JAVA_HOME is not defined correctly.

While this isn't a major problem, it reveals that fop depends on Java. I think I'll submit that upstream.

While this isn't a major problem, it reveals that fop depends on Java. I think I'll submit that upstream.

Done and merged in https://github.com/Homebrew/homebrew-core/pull/1330

ENV["XML_CATALOG_FILES"] = etc/"xml/catalog"

Does this variable need to set in the user's environment as well? If so, should it be documented in caveats of the relevant formula?

Installing the xorg-docs bottle pulls in jdk as a dependency, even though the dependency on fop is a :build dependency, and fop depends on :java. So xorg-docs should not have a run-time dependency on jdk. This I believe is a bug in the dependency resolver of brew. @xu-cheng
$ brew install linuxbrew/linuxbrew/xorg-docs
==> Installing xorg-docs from linuxbrew/xorg
==> Installing dependencies for linuxbrew/xorg/xorg-docs: jdk
==> Installing linuxbrew/xorg/xorg-docs dependency: jdk
==> Downloading http://download.oracle.com/otn-pub/java/jdk/8u60-b27/jdk-8u60-li
==> Downloading from http://download.oracle.com/otn-pub/java/jdk/8u60-b27/jdk-8u
######################################################################## 100.0%
==> Caveats
By installing and using JDK you agree to the
Oracle Binary Code License Agreement for the Java SE Platform Products and JavaFX
http://www.oracle.com/technetwork/java/javase/terms/license/index.html

==> Summary
🍺  /home/sjackman/.linuxbrew/Cellar/jdk/1.8.0-60: 1,622 files, 348.0M, built in 1 minute 17 seconds
==> Installing linuxbrew/xorg/xorg-docs
==> Downloading https://linuxbrew.bintray.com/bottles-xorg/xorg-docs-1.7.x86_64_
######################################################################## 100.0%
==> Pouring xorg-docs-1.7.x86_64_linux.bottle.tar.gz
🍺  /home/sjackman/.linuxbrew/Cellar/xorg-docs/1.7: 136 files, 7.6M

$ brew deps xorg-docs
fop
jdk
libxml2
libxslt
util-macros
zlib
$ brew deps --include-build xorg-docs
bzip2
docbook
docbook-xsl
fop
gettext
gnu-getopt
gpatch
homebrew/dupes/ncurses
homebrew/dupes/unzip
jdk
libxml2
libxslt
pkg-config
util-macros
xmlto
xorg-sgml-doctools
xz
zlib
$ brew info xorg-docs
...
==> Dependencies
Build: util-macros ✔, xmlto ✔, fop ✔, libxslt ✔, xorg-sgml-doctools ✔, docbook ✔, docbook-xsl ✔, gpatch ✔
Recommended: util-macros ✔, fop ✔, libxslt ✔
...

Worth noting that the dependency on fop is depends_on "fop" => [:build, :recommended] whereas the dependency on docbook is depends_on "docbook" => :build (and likewise for docbook-xsl and xorg-sgml-doctools). It looks like :recommended is overruling :build.
That might or might not be a bug. It might just mean that we're misinterpreting what :recommended means.

What we might need to do is:
option "without-fop", "Build without fop"
depends_on "fop" => :build

ENV["XML_CATALOG_FILES"] = etc/"xml/catalog"
Does this variable need to set in the user's environment as well? If so, should it be documented in caveats of the relevant formula?

Found this in asciidoc's caveats (not the same obviously, but a useful guide if nothing else):
      If you intend to process AsciiDoc files through an XML stage
      (such as a2x for manpage generation) you need to add something
      like:

        export XML_CATALOG_FILES=#{etc}/xml/catalog

      to your shell rc file so that xmllint can find AsciiDoc's
      catalog files.

      See `man 1 xmllint' for more.

xmllint's man page has this to say:
       XML_CATALOG_FILES
           XML catalog behavior can be changed by redirecting queries to the user's own set of catalogs. This can be
           done by setting the XML_CATALOG_FILES environment variable to a list of catalogs. An empty one should
           deactivate loading the default /etc/xml/catalog catalog.

However, people might have important XML DTD's listed in /etc/xml/catalog and appearing somewhere in /etc/xml. Catalog entries look like this: <delegateSystem systemIdStartString="http://docutils.sourceforge.net/" catalog="file:///etc/xml/docutils-common.xml"/>.
I'm not really sure what would happen if two catalog files pointed the same URL to two conflicting DTD's, but, assuming it works like PATH and the first catalog file with a hit is used, I think for most users the correct thing to do would be something like export XML_CATALOG_FILES=$HOMEBREW_PREFIX/etc/xml/catalog:/etc/xml/catalog, assuming that the second location is constant (or nearly so) across all Linux distros.
Thoughts?


ISSUE-172 Support Disabling Schemas

Add ability to disable schema's this will mean when disabled, a schema will no longer partake in compatibilty checks (e.g. allowing disabling an accidental registration).
Also address's ISSUE-173, by providing helper method ability to disable all versions of a given schema (for sakes of topic deletion)

@michaelandrepearce Thanks for the patch. This is the most asked feature/request often. But we've a different take on it, to support Schema Lifecycle Management.

When user first registers a schema it goes into TEST state.
if this schema is tested and peer approved it can promoted to PRODUCTION state.
Clients by default can only see the schema in PRODUCTION state and can be configured to see TEST state schema as well.
If there are no clients using the schemas (client heartbeat functionality will show who all are accessing a schema) than it can go into DISABLED state.

We should at least start recording "STATE" as another column and make this patch to record this into the said column. We can add the above on top of it.

these two things I think are independent. What you're talking about is environment promotion. Test to uat to prod, very much like an artefact repo.
What we are needing is the ability to delete a schema (or at least make it ignored by back compatibility checks).
In your case where client no longer used if I had a valid schema even after client in prod stopped using it I would want the schema validated historically as it would still be possible to retro activate a client. Or at least if we are to merge the two I would suggest having a different state for this

the other issue slightly with hard coded environments or merging the two ideas and enum the env state, will be each org will have separate setup of environment promotion. Eg it's likely in a big org you can have Dev, test, qa, uat, demo, live. And no doubt other orgs all have different. Typically in a commercial artefact repo this is completely configurable for the staging layers. But globally the ability to disable/delete an artefact is a seperate function

For this reason I would suggest life cycle management and ability to disable/delete are left as two seperate features.

@satishd @harshach I assume by creation of https://github.com/hortonworks/registry/issues/177, we're agreeing to separate the concerns.

@michaelandrepearce @harshach I did not mean that these two are separate, this issue may be one aspect of schema lifecycle management.  Lifecycle is not only about promotion but includes stages from creation to till it is archived/deleted. We need to think through in detail and give a way to plug any states in between by users. This does not need to cover all usecases but it should be pluggable enough with basic lifecycle management. I will put my thoughts in #177 and discuss in detail over there.

@satishd I'm closing this off.


dns: trim server name if they are too long and remove all unwraps so we never panic.

Trust dns have a limit on server_names so automatically trim server name.
Remove pending unwraps from server.

@baude PTAL

one nit, else LGTM

@baude PTAL again.

Please add a test with a long network name to prevent regressions.

/lgtm


[en] home page

This issue is about writing en/source/index.rst

[x] write essential descriptions about qulacs in the home page
[x] correctly link documents to the toctree

Changes directly push to dev. Close this issue


internal_users.yml expects opendistro specific security label

Description
The security admin script throws an error when processing an internal_users.yml file matching the current provided documentation.
ERR: Seems /usr/share/opensearch/plugins/opensearch-security/securityconfig/internal_users.yml is not in OpenSearch Security 7 format: com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "opensearch_security_roles" (class org.opensearch.security.securityconf.impl.v7.InternalUserV7), not marked as ignorable (8 known properties: "opendistro_security_roles", "backend_roles", "attributes", "reserved", "hidden", "description", "hash", "static"])
To Reproduce
Steps to reproduce the behavior:

Place a internal_users.yml file matching the current documentation into your securityconfig folder.
Run the security admin script
See error

Expected behavior
I would expect the documented format to be accepted by the security admin script.
Plugins
OpenSearch Security Version: <IP_ADDRESS>
Host/Environment (please complete the following information):

OS: Oracle Linux 7
OpenSearch Version: 1.0.0

Additionally, if one tries to use opendisto_security_roles instead of opensearch_security_roles, the following message occurs in opensearch.log:
[2021-07-26T13:52:55,231][ERROR][o.o.s.c.ConfigurationLoaderSecurity7] [gsx001.lab.core.ns.internal] Exception while retrieving configuration for [INTERNALUSERS, ACTIONGROUPS, CONFIG, ROLES, ROLESMAPPING, TENANTS, NODESDN, WHITELIST, AUDIT] (index=.opendistro_security) com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "opendistro_security_roles" (class org.opensearch.security.securityconf.impl.v6.InternalUserV6), not marked as ignorable (7 known properties: "readonly", "username", "attributes", "hidden", "password", "roles", "hash"])  at [Source: (String)"{"_meta":{"type":"internalusers","config_version":1},"bootstrap":{"hash":"$2y$12$QgdMncp9oVNYxWDqFjDEjuO2ROseQzGQnOr12P6xLIE8gadQXFCVC","reserved":false,"hidden":false,"opendistro_security_roles":["admin"],"backend_roles":["admin"],"static":false,"description":"Bootstrap user. Created and deleted during the bootstrap process."}}"; line: 1, column: 198] (through reference chain: org.opensearch.security.securityconf.impl.SecurityDynamicConfiguration["bootstrap"]->org.opensearch.security.securityconf.impl.v6.InternalUserV6["opendistro_security_roles"])
It appears that the application is using a different version of security implementations than the security admin script. Although the security admin script can be overridden to validate on v6, this wouldn't be ideal.

Second error OP mentioned did not occur for me when using opendistro_security_roles.

Same issue with first error. opendistro_security_roles is the accepted property as opposed to what documentation says opensearch_security_roles

It seems like this is still the case. @opensearch-project/security we should take a look.

This is wrong on the documentation website. I opened a PR to address this.

We are doing some "spring cleaning in the fall", and to make sure we focus our energies on the right issues and we get a better picture of the state of the repo, we are closing all issues that we are carrying over from the ODFE era (ODFE is no longer supported/maintained, see post here).
If you believe this issue should still be considered for current versions of OpenSearch, apologies! Please let us know by re-opening it.
Thanks!


Create PlayerInitailiserCommand

Description
Creation and initialisation of the player is all over the place. It needs to be centralised to reduce the overall complexity
Acceptance Criteria:

Player is initialised through a command
The player spawning is handled through the same object
The model data is passed into the command

Scope Change
Instead of a command initialiser, a seperate player spawner is instead created


failed in discover one single mutation

--Hi,
i don't know why this record is discarded:
chr21   43104346        .       G       T       273     Q10     SAMPLE=SAD190004_S5;TYPE=SNV;DP=636;END=43104346;VD=289;AF=0.4544;BIAS=2:2;REFBIAS=170:177;VARBIAS=143:146;PMEAN=39.1;PSTD=1;QUAL=33.5;QSTD=1;SBF=0.93657;ODDRATIO=1.01975260801729;MQ=0;SN=35.125;HIAF=0.4554;ADJAF=0.0079;SHIFT3=0;MSI=2;MSILEN=2;NM=1.1;HICNT=281;HICOV=617;LSEQ=TCGGTTTATTGTGCAACCGA;RSEQ=AGCACCTGTCTCCATGACGA;DUPRATE=0;SPLITREAD=0;SPANPAIR=0  GT:DP:VD:AD:AF:RD:ALD   0/1:636:289:347,289:0.4544:170,177:143,146
which parameter i need to adjust ?
thank you --

Hi @lmanchon , these is MQ=0, that means that mapping quality of this variant is zero - so the reads supporting the variant should have MAPQ=0 as well and seems are not mapped correctly to the reference. Better to check with genome browser, but I believe it was filtered out correctly (FILTER field is Q10 for this case).

seems to be well mapped with BWA-MEM, see IGV panel here:

Maybe those are secondary alignments? Do you have XA tags in these reads? Just show any read supporting the variant. We filter secondary alignments, but probably they were included in tags instead of flags (-F 0x504).

Those are secondary alignments: there is XA:Z tag that shows where was another location in genome where the read can be mapped. And this one will have MAPQ 0. Usually these should be also put to SAM flags (i.e. 163/83 for those reads) but for some reason it wasn't - probably BWA setup. But anyway - this variant is likely to be on another position in genome, so it was filtered out here.

okay thank you for your help.


Right side navigation shows users the wrong page

Navigate to https://reactjs.org/docs/hello-world.html
Click "Handling Events" in the right side navigation
Observer that the user is shown the "Portals" page, not the handling events page

Can't reproduce this behavior. Are you sure you clicked the correct nav entry?

Just double checked and I am indeed clicking on the "Handling Events" nav item. For reference, this is with Firefox 56.0 (64-bit) and Chrome version 61.0.3163.100 (Official Build) (64-bit).

Hm. I'm not able to reproduce this on any browser (or operating systems) I have to test on. I think we would probably have heard of this before if it was a widespread problem. I suspect there's something unique about your system, given the fact that you've also reported another issue (#248) that I've never seen before.

I'm going to close this issue for now because I suspect it's something specific to your setup and I'm not sure what action I can take given that I'm unable to reproduce it. If someone else reports this issue, or if you're able to provide additional info to help track it down, we'll re-open!

Sounds good, thanks for looking into it.


Update polygon subgraph endpoint

Description
A few months ago we started pruning the subgraph at balancer-labs/balancer-polygon-v2 in order to increase the performance for the frontend, but that had unforeseen side effects for 3rd party integrations.
We've switched to a dual deployment model where balancer-labs/balancer-polygon-v2 has the full history and balancer-labs/balancer-polygon-prune-v2 is pruned. This PR switches to using the pruned endpoint on the frontend.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Dependency changes
[ ] Code refactor / cleanup
[ ] Documentation or wording changes
[x] Other

How should this be tested?

[ ] The app works on polygon

Checklist:

[ ] I have performed a self-review of my own code
[ ] I have requested at least 1 review (If the PR is significant enough, use best judgement here)
[ ] I have commented my code where relevant, particularly in hard-to-understand areas
[ ] If package-lock.json has changes, it was intentional.
[ ] The base of this PR is master if hotfix, develop if not

Cloudflare preview: https://polygon-graph-endpoint.balancer-d6h.pages.dev/#/polygon


Issues with directives not being removed when using Federation transformation with v1

Issue workflow progress
Progress of the issue based on the
Contributor Workflow

[x] 1. The issue provides a reproduction available on
https://github.com/madorb/gql-mesh-naughty-rosalind-3hqzhs
https://codesandbox.io/p/github/madorb/gql-mesh-naughty-rosalind-3hqzhs

[ ] 2. A failing test has been provided

[ ] 3. A local solution has been provided

[ ] 4. A pull request is pending review

Describe the bug
There are a couple of corner cases where the Federation Transformation for v1 does not remove directives.
Single Value Enum
Given OAS:
incorrectSingleValue:
  description: "Expected @enum/@typescript directives to be removed by federation transformer for v1. Also note: Description is not added to gql schema"
  type: string
  enum:
    - "SINGLEVALUE"
  default: "SINGLEVALUE"

Generated V1 schema: (note - also missing comment generated from OAS description)
enum incorrectSingleValue @typescript(type: "\"SINGLEVALUE\"") @example(value: "\"SINGLEVALUE\"") {
  SINGLEVALUE @enum(value: "\"SINGLEVALUE\"")
}

Integer Enum
This is a strange one as modeling enums as integers is likely not a good idea, and we actually changed this on our app but:
Given OAS:
incorrectInteger:
  description: "Expected @enum directive to be removed by federation transformer for v1"
  type: string
  enum:
    - 0
    - 1

Generated v1 schema:
"Expected @enum directive to be removed by federation transformer for v1"
enum incorrectInteger {
  _0 @enum(value: "0")
  _1 @enum(value: "1")
}

To Reproduce Steps to reproduce the behavior:
Examine the generated schema available on the reproduction: https://codesandbox.io/p/github/madorb/gql-mesh-naughty-rosalind-3hqzhs
Expected behavior
The generated schema should contain no @typescript or @enum directives when using federation v1
Environment:

OS: N/A
@graphql-mesh/...: 0.87.14
NodeJS: v16.17.0

Additional context

Fixed in https://github.com/Urigo/graphql-mesh/pull/6081


Can not back out of menu item after selected, deleting

Try pressing A and C together to return to the launcher :)
https://learn.pimoroni.com/article/getting-started-with-badger-2040

Oh, just seen #85 - glad to hear you're sorted.
Closing this duplicate :)


Fix test_primary.py

Some of this seems to have been broken by ASN.1/DER code.
Adjust the tests to work with ASN.1/DER format. While we're at it, expand the tests.

Fixed now.


[nrf fromlist] soc: nordic: nrf54h20: disallow using LR in s2ram mark…

…ing function
This change ensures that LR will not be implicitly used when calling pm_s2ram_mark_check_and_clear.
Upstream PR #: 81853

Merged as part of https://github.com/nrfconnect/sdk-zephyr/pull/2385


extracted footer and the head

https://www.coingecko.com/en/api/documentation?

I'd take just the crypto and its prices.
They want Asynchronous calls to smart contracts must be mocked-up., so maybe we should take the contract as well?
https://github.com/newton-blockchain/TIPs/issues/42

I'd take just the crypto and its prices.
They want Asynchronous calls to smart contracts must be mocked-up., so maybe we should take the contract as well?
https://github.com/newton-blockchain/TIPs/issues/42


Fix mixpanel event name

This PR is to fix the hard coded 'Experiment Started' event name.
Using the event named as 'Experiment Started' doesn't work with Mixpanel experiment tracking.
Mixpanel has an experiment started event (called $experiment_started) to be used by default. (It translates to 'Experiment Started' in the Mixpanel console)
Reference: https://docs.mixpanel.com/docs/reports/apps/experiments#add-experiments-to-an-implementation

@vishakha-aggarwal
Please merge this so we can use this.

Can this be pushed to npm as well?

@prabushitha @olivierverwoerd It's published on NPM. Please use v1.2.0.


Before uploading, how to package, compress and encrypt files before uploading?

excuse me.I want to implement a package compression encryption after upload, how to do？

I have never used JavaScript to make a tar file and compress it. You can probably use something like https://github.com/ankitrohatgi/tarballjs and get the resulting file as a Blob. This blob can then be given to tus-js-client to upload it like any other normal file. Please do you own research on what is the best way to create TAR files with ZSTD compression. I have never done that before.

Oh, oh, thank you. Let me check again


Reference style image after inline style image doesn't work correctely

failed:
![sd-inline](https://raw.githubusercontent.com/showdownjs/logo/master/dist/logo.readme.png) ![sd-ref][sd-logo]

ok:
![sd-ref][sd-logo] ![sd-inline](https://raw.githubusercontent.com/showdownjs/logo/master/dist/logo.readme.png)

@ye-will should be fixed now in 73206b0, develop branch

@tivie nice work.


Update README.md

Coverage remained the same at 93.609% when pulling 698006309b7e679f980ba1f71210da38b0d6f035 on katopz:patch-1 into 2dd914c6ed2b7010a297add0750a3b40963e9c63 on tableflip:master.


generalize resource selectors

What this PR does / why we need it:
Offer a public resource selector feature on the internal component descriptor version.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release Notes:

I've added resource selection via Labels and additionally tests for the new features.

Please try and not extend this any further. :D Also, we kind of need this for our tests sooner rather than later. :)
thanks! :)

yes, it is done now. What I wanted to achieve are the same selection features for resources and references (and potentially sources).
Therefore, the selector interface had to be extended a little bit. But now it is in a shape to be extendable in a compatible manner. if some extension will be required in the future.


wip: Move to Go modules

Move from go dep to go modules.
Fixes #1331

@amshinde Is the plan to get runtime moved while we move rest of the repos? In that case, tests repository needs to be bostered to run go mod verify against dep check for just these repos.

@amshinde, @ganeshmaharaj - please can we document the plan on https://github.com/kata-containers/kata-containers/issues/42 to allow others to understand (and comment on) it.

/test

@jodh-intel Will update the issue.

ping @amshinde

Hi @amshinde, @jodh-intel! Coming from #1420, I'm sorry to be the one bringing bad news here...
Context:

Currently, this repository retrieves the tests repo with 'go get' and expects it to be available in GOPATH/src/github.com/kata-containers/tests. However, in any environment where go modules are enabled, go get will NOT download sources of packages in that path. This is why this PR will fail when go modules are enabled in Travis: https://travis-ci.com/umarcor/kata-runtime/jobs/231319730. See https://github.com/kata-containers/runtime/pull/1420#issuecomment-528176791.
With go modules, 'vendor' is expected not to be required and there is no idiomatic way to properly 'mix' sources available in the modules caches and those in 'vendor'. This is related to https://github.com/kata-containers/tests/pull/1880#issue-303163610.

Any build with go modules should be reproducible, as long as remotes are not gone. This is the only use case of 'vendor' in the new environment: a backup, just in case some of the remotes fails. As a result, 'vendor' should not be included in the VCS. In any case, vendor packages could be distributed as tarballs for users with very specific requirements to have them.
By the  same token, build commands need to be specifically forced to use the vendor folder.

Therefore, I think that this PR  should ensure that go modules are not used, except for running go mod vendor.

I think go mod vendor can be an option. How about we only use go mod to manage our "vendor" dir instead of remove whole "vendor" from the repo?

I think go mod vendor can be an option. How about we only use go mod to manage our "vendor" dir instead of remove whole "vendor" from the repo?

That's a temporal solution that will only work as long as go modules are optional. Nevertheless, as commented, this approach would require:

this PR should ensure that go modules are not used, except for running go mod vendor.
build commands need to be specifically forced to use the vendor folder.

@amshinde ping this needs rebase

@amshinde any updates on this PR? Thx!

@amshinde any updates on this PR? Thx!

I'll revisit this PR this week.

@amshinde any updates? Thx.
Your weekly Kata herder.

Currently, this repository retrieves the tests repo with 'go get' and expects it to be available in GOPATH/src/github.com/kata-containers/tests. However, in any environment where go modules are enabled, go get will NOT download sources of packages in that path. This is why this PR will fail when go modules are enabled in Travis: https://travis-ci.com/umarcor/kata-runtime/jobs/231319730. See #1420 (comment).

We should not use the new go get to download code or binary inside a go module directory, -- it would fetch the code and add it to your go.mod dependency. git clone is your friend ;)
And kindly ping @amshinde from your Kata Herder this week ;)

We should not use the new go get to download code or binary inside a go module directory, -- it would fetch the code and add it to your go.mod dependency. git clone is your friend ;)

@bergwolf, thanks for acknowledging this point. I've trying to make it clear for almost a year now.. #1420, #1413. I believe that's the critical issue that is preventing any practical movement towards go modules.

@amshinde @bergwolf @umarcor ping.

See https://github.com/kata-containers/runtime/pull/1420#issuecomment-700777378.


Create issues

Please make sure to create all issues for one block before starting to work on it. Also, remember to assign them to the corresponding milestone.

Also two general comments:

Even if you edit files on GitHub, please create a pull request for them.
Wait with merging pull requests until I've given a thumbs-up (or didn#t react to changes for some hours).

Does it mean we should start an Issue for every task like:
-create a README.md
-add a license
-etc.
... write something to each and close it, if there are no questions anymore?

In general, yes, you should have an issue for each of the tasks I created.  There are still a number of tasks in Block 1 that you haven't completed, though, and I'd like you to create issues for them.

ok

I'll leave this open until you've actually created the issues...


Definition highlight not right on cpp.

Describe the bug
Hello, look at this code, if cursor on ::reused, the global value reused should be highlight, but the local value reused highlight.

  #include <iostream>

  int reused = 42;

  int main(int argc, char *argv[]) {
    int unique = 0;
    std::cout << reused << " " << unique << std::endl;
    int reused = 0;
    std::cout << reused << " " << unique << std::endl;
    std::cout << ::reused << " " << unique << std::endl;

    return 0;
  }

Expected behavior
the global value reused should be highlight.
Output of :checkhealth nvim_treesitter

health#nvim_treesitter#check
Installation

OK: git executable found.
OK: cc executable found.

elm parser healthcheck

OK: elm parser found.
WARNING: No highlights.scm query found for elm

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No locals.scm query found for elm

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No folds.scm query found for elm

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for elm

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

c parser healthcheck

OK: c parser found.
OK: highlights.scm found.
OK: locals.scm found.
OK: folds.scm found.
WARNING: No indents.scm query found for c

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

teal parser healthcheck

OK: teal parser found.
OK: highlights.scm found.
OK: locals.scm found.
OK: folds.scm found.
WARNING: No indents.scm query found for teal

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

java parser healthcheck

OK: java parser found.
OK: highlights.scm found.
OK: locals.scm found.
WARNING: No folds.scm query found for java

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for java

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

python parser healthcheck

OK: python parser found.
OK: highlights.scm found.
OK: locals.scm found.
OK: folds.scm found.
WARNING: No indents.scm query found for python

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

dart parser healthcheck

OK: dart parser found.
OK: highlights.scm found.
OK: locals.scm found.
WARNING: No folds.scm query found for dart

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for dart

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

lua parser healthcheck

OK: lua parser found.
OK: highlights.scm found.
OK: locals.scm found.
OK: folds.scm found.
OK: indents.scm found.

ocaml parser healthcheck

OK: ocaml parser found.
OK: highlights.scm found.
OK: locals.scm found.
OK: folds.scm found.
WARNING: No indents.scm query found for ocaml

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

go parser healthcheck

OK: go parser found.
OK: highlights.scm found.
OK: locals.scm found.
WARNING: No folds.scm query found for go

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for go

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

nix parser healthcheck

OK: nix parser found.
WARNING: No highlights.scm query found for nix

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No locals.scm query found for nix

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No folds.scm query found for nix

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for nix

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

yaml parser healthcheck

OK: yaml parser found.
WARNING: No highlights.scm query found for yaml

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No locals.scm query found for yaml

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No folds.scm query found for yaml

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for yaml

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

json parser healthcheck

OK: json parser found.
OK: highlights.scm found.
WARNING: No locals.scm query found for json

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No folds.scm query found for json

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for json

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

jsdoc parser healthcheck

OK: jsdoc parser found.
WARNING: No highlights.scm query found for jsdoc

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No locals.scm query found for jsdoc

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No folds.scm query found for jsdoc

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for jsdoc

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

php parser healthcheck

OK: php parser found.
OK: highlights.scm found.
OK: locals.scm found.
OK: folds.scm found.
WARNING: No indents.scm query found for php

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

julia parser healthcheck

OK: julia parser found.
WARNING: No highlights.scm query found for julia

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No locals.scm query found for julia

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No folds.scm query found for julia

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for julia

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

html parser healthcheck

OK: html parser found.
OK: highlights.scm found.
OK: locals.scm found.
WARNING: No folds.scm query found for html

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for html

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

typescript parser healthcheck

OK: typescript parser found.
OK: highlights.scm found.
OK: locals.scm found.
OK: folds.scm found.
WARNING: No indents.scm query found for typescript

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

fennel parser healthcheck

OK: fennel parser found.
OK: highlights.scm found.
OK: locals.scm found.
WARNING: No folds.scm query found for fennel

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for fennel

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

swift parser healthcheck

OK: swift parser found.
WARNING: No highlights.scm query found for swift

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No locals.scm query found for swift

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No folds.scm query found for swift

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for swift

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

query parser healthcheck

OK: query parser found.
OK: highlights.scm found.
OK: locals.scm found.
WARNING: No folds.scm query found for query

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for query

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

cpp parser healthcheck

OK: cpp parser found.
OK: highlights.scm found.
OK: locals.scm found.
OK: folds.scm found.
WARNING: No indents.scm query found for cpp

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

regex parser healthcheck

OK: regex parser found.
OK: highlights.scm found.
WARNING: No locals.scm query found for regex

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No folds.scm query found for regex

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for regex

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

verilog parser healthcheck

OK: verilog parser found.
OK: highlights.scm found.
WARNING: No locals.scm query found for verilog

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No folds.scm query found for verilog

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for verilog

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

ruby parser healthcheck

OK: ruby parser found.
OK: highlights.scm found.
OK: locals.scm found.
WARNING: No folds.scm query found for ruby

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for ruby

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

vue parser healthcheck

OK: vue parser found.
WARNING: No highlights.scm query found for vue

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No locals.scm query found for vue

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No folds.scm query found for vue

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for vue

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

ocamllex parser healthcheck

OK: ocamllex parser found.
OK: highlights.scm found.
WARNING: No locals.scm query found for ocamllex

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No folds.scm query found for ocamllex

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for ocamllex

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

scala parser healthcheck

OK: scala parser found.
WARNING: No highlights.scm query found for scala

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No locals.scm query found for scala

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No folds.scm query found for scala

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for scala

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

ql parser healthcheck

OK: ql parser found.
OK: highlights.scm found.
OK: locals.scm found.
WARNING: No folds.scm query found for ql

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for ql

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

rust parser healthcheck

OK: rust parser found.
OK: highlights.scm found.
OK: locals.scm found.
WARNING: No folds.scm query found for rust

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for rust

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

toml parser healthcheck

OK: toml parser found.
OK: highlights.scm found.
OK: locals.scm found.
WARNING: No folds.scm query found for toml

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for toml

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

bash parser healthcheck

OK: bash parser found.
OK: highlights.scm found.
OK: locals.scm found.
WARNING: No folds.scm query found for bash

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for bash

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

rst parser healthcheck

OK: rst parser found.
OK: highlights.scm found.
OK: locals.scm found.
WARNING: No folds.scm query found for rst

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for rst

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

css parser healthcheck

OK: css parser found.
OK: highlights.scm found.
WARNING: No locals.scm query found for css

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No folds.scm query found for css

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for css

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

ocaml_interface parser healthcheck

OK: ocaml_interface parser found.
OK: highlights.scm found.
OK: locals.scm found.
OK: folds.scm found.
WARNING: No indents.scm query found for ocaml_interface

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

javascript parser healthcheck

OK: javascript parser found.
OK: highlights.scm found.
OK: locals.scm found.
OK: folds.scm found.
WARNING: No indents.scm query found for javascript

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

c_sharp parser healthcheck

OK: c_sharp parser found.
OK: highlights.scm found.
WARNING: No locals.scm query found for c_sharp

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No folds.scm query found for c_sharp

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for c_sharp

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

haskell parser healthcheck

OK: haskell parser found.
WARNING: No highlights.scm query found for haskell

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No locals.scm query found for haskell

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No folds.scm query found for haskell

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

WARNING: No indents.scm query found for haskell

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

tsx parser healthcheck

OK: tsx parser found.
OK: highlights.scm found.
OK: locals.scm found.
OK: folds.scm found.
WARNING: No indents.scm query found for tsx

ADVICE:

Open an issue at https://github.com/nvim-treesitter/nvim-treesitter

Output of nvim --version
NVIM v0.5.0-781-ga22fe09b9
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/gcc-5 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/home/travis/build/neovim/bot-ci/build/neovim/build/config -I/home/travis/build/neovim/bot-ci/build/neovim/src -I/home/travis/build/neovim/bot-ci/build/neovim/.deps/usr/include -I/usr/include -I/home/travis/build/neovim/bot-ci/build/neovim/build/src/nvim/auto -I/home/travis/build/neovim/bot-ci/build/neovim/build/include
Compiled by travis@travis-job-cf8f8ff3-8560-4d24-8cbb-fea1921bfd23

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/share/nvim"

Run :checkhealth for more info

Additional context
Add any other context about the problem here.

Currently this is expected by the implementation. Scopes are defined by their parent nodes and don't take into account where they are defined amongst their siblings. This will take some rework to fix.


⚠ Bofrost.de has degraded performance

In c130550, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1775 ms

Resolved: Bofrost.de performance has improved in fbcaa61 after 24 minutes.


Types for each coord

During coding markCubeCell I spot that:
markCubeCell :: Coord -> Coord -> Coord -> ...
markCubeCell z y x ...

Not clear enough. If I change x and z nothing will happen (only tests can react to this). I think we can solve this issue by creating X, Y, and Z types (think about X coord and X player types overlap). But if they will be unique types, we can no longer can use Three for Coords.

If each coord will have its own type, then I can't no longer use Three for Coord.


Custom log file permisson in .snakemake

Hi Snakemake team,
Is your feature request related to a problem? Please describe.
I created a NGS processing pipeline on a slurm hpc so my colleague can run it and then we share the results/output.
I wanted all the output created the be user::rwx and group::rwx, which i managed to do by adding
os.umask(0o02)
At the beginning of my Snakefile, thus changing the umask to user::rwx, group::rwx, other::r-x for the directory and subdirectories.
But still file in .snakemake/log/ are user::rw-, group::r--, other::r-- so when my colleagues report bugs I have some permissions denied.
Describe the solution you'd like
Is there a way to add in the cluster config or cluster profile a custom permission option so all the output files and directories are user::rwx, group::rwx, other::r-x, including .snakemake/log/ files ?
I'm still using the old way to config cluster with a cluster.yaml file, I am not already using snakemake profile.
Thank a lot,
David

Could you use an onstart, onsuccess, or onerror handler to do this in the shell:
onstart:  # or onsuccess, onerror
    shell("chmod g+w {log}")

Sure, but be sure to close this issue when you feel it is resolved.
Your options kind of depend on how the cluster is set up.  The issues are that you may not know how long the main snakemake thread will take to complete and you may not be able to submit jobs from the worker nodes (the nested job submission).
For the cluster I typically use, you can execute sbatch from worker nodes but there is a 1 week time limit, which for long workflows isn't enough time for the main snakemake process.  Other clusters may not allow sbatch but may have an unlimited time limit option for the main process; contact your sys admins to be sure.
Snakemake is single core and mostly will use little cpu, so you could run it on the head node, just be sure to execute it in screen or tmux so you can detach from the session and keep the process running without you being connected.  I prefer tmux, but for this application either would work.  If the sys admins don't like running anything on the login node, ask if there is another interactive node you could use and submit jobs from.
One final consideration if you go with the submitted job option, your compute nodes may not have network connections so you will need to prefetch any images/environments and ensure no rules rely on the internet (e.g. downloading files, fetching neural networks, etc).


Deterministic heap for namenode

The current calculation was setup in such a way that NameNode heap would either be 16GB or some fraction of system memory, whichever is the minimum.  This was designed so that we are able to support real systems and along side this VM cluster.  This is not deterministic so lets just set to Xmx to 1GB and NewSize to 128m which is what is recommended for 1,000,000 files per http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.3.6/bk_installing_manually_book/content/ref-80953924-1cbf-4655-9953-1e744290a6c3.1.html, and is probably too much for a toy VM cluster anyway.
BONUS: All the confusing logic is removed (at least for the NameNode)
BREAKING: This will restart a NameNode since we are making configuration chnages

I think this was all a misguided .min, instead of a .max. There's further the same issue with the Datanode above these lines which also ignores the override and uses .min instead of .max. Really these should use the dynamic tunings unless an override is provided was the original thought.

I have not done any research for the datanode so I was not prepared to make any changes, especially since it  currently works.  For the NameNodes, the goal was to have a basic value and one that we can override, being able to support 1,000,000 files on a VM node seemed reasonable.

I added a dynamic calculation option so instead of min/max games one just needs to either set a value default["bcpc"]["hadoop"]["namenode"]["xmx"]["max_size"] and default["bcpc"]["hadoop"]["namenode"]["xmn"]["max_size"] or set them to nil for dynamic calculation to happen.


build does not respect context

https://github.com/netlify/cli/blob/d9756720205413ae771223098eb78cee71853338/src/commands/build/index.js#L31

Thanks @lucasconstantino for reporting this.
Don't hesitate to add more information when filing bugs, it helps us understand the problem.
For reference, the problem here is that the --context CLI flag is not passed from the CLI to @netlify/build due to the line of code referenced in the initial post.

Actually, the --context CLI flag does work properly. It is set inside cachedConfig at the following line. We also have a unit test.
@lucasconstantino Could you please describe your problem and steps to reproduce it? Thanks a lot.

Sorry for the noise. I'm just walking through the code debugging something related to local plugins. I'll share a better description if I can simulate the bug I have properly.
Thanks