Using a pre-existing namespace?

Qt.py is awesome! I'm slowly transitioning a good chunk of Qt4 stuff and this has been a huge help! Thank you!
I only have one question:
I typically like to mirror my python and c++ code so typing QtCore.Qt.(something) isn't my favorite for each time I want to access the QtCore::Qt module.
from MyBinding import QtWidgets/QtGui
from MyBinding import QtCore
from MyBinding.QtCore import Qt, SIGNAL

is typically how I have my imports go however the last line becomes tricky due to the name of Qt.py
I was just wondering if there was anything you would recommend to avoid the clash (other than say, call each instance of Qt in my scripts referring to the QtCore::Qt version something like _Qt, which isn't out of the question. Just inquiring).
Thanks again!
Cheers.

As I typed the question out I put together that I could just use an intermediary module to fake it. Which isn't too bad. I'm still up for any other suggestions. That said, anyone is welcome to close this.
# -- /repo/QtBinding.py
import Qt
_Qt = Qt
Qt = _Qt.QtCore.Qt
# ...
# Place any modules into this namespace as 1:1...
# ...

# -- /repo/somefile.py
from QtBinding import Qt # In the clear. Represents the QtCore::Qt and is still only 1 level deep.

Hi @mccartnm, thanks for your kind words and feedback!
What are your thoughts on using the as mechanism of Python?
# For example..
from Qt.QtCore import Qt as _Qt
# Or..
from Qt.QtCore import Qt as QtCoreQt

Right on I don't mind that solution either. You're method is probably smoother sailing for when trying to import modules I'm not really aware of that other developers might need (i.e. .ui loading tools).
Thanks again :)

No problem, thanks for the feedback! Any other questions, just let me know!


Fix invalid encoding

https://github.com/V-Sekai/godot-whisper/issues/44#issuecomment-1902254629

Reasoning from the comment follow to conclusion.
Because English is not my native language, do you mean to ask me to explain why I need to modify it this way? Or is it the process of discovering problems?

I mean it looks good. 👍


Fine-tuning

Hello:
Very outstanding work!
Can you provide a tutorial on fine-tuning based on the Open-Sora-Plan v1.0.0 model?
Thank you so much!

In fact each stage is a fine-tuning of the previous stage, and you can observe the difference between stage 2 scripts and stage 1 to customize your fine-tuning scripts.

Sorry, we fixed the training script.
See https://github.com/PKU-YuanGroup/Open-Sora-Plan/blob/main/scripts/text_condition/train_videoae_65x512x512.sh#L31


Migrate loggie to booker

related to kaelzhang/node-booker#4

comfort will no longer depend on logger


Default configuration for the export

What should the default configuration look like?

should indexes be part of the table script or not?
should indexes be both ... part of the table script AND exported separately?
should triggers be part of the table script or not?
should triggers be both ... part of the table script AND exported separately?

remove trigger from dependent objects for tables
add trigger to views
add index in type-excludes
--exclude-types LOB "TABLE_PARTITION" "INDEX PARTITION" "JAVA CLASS" JAVA "JAVA RESOURCE" INDEX ^

Need a solution for REF_CONSTRAINTS in different folders or in tables folder with <table name>_ref.sql filename.

per default we will create directory ref_constraints using the constraint name.


Support type parameters in def macros

The transform should take type parameters into consideration and handle PolyType.

It seems inlining makes this feature difficult to implement without sacrificing type safety.
Given the macro definition:
class eden {
  inline def as[T](a: Any): Any = meta {
    val tp = T.asInstanceOf[scala.meta.Type]
    val term = a.asInstanceOf[scala.meta.Term]
    q"$term.asInstanceOf[$tp]"
  }
}

We transform it into the follows:
class eden {
  inline def as[T](a: Any): Any = meta { eden$inline.as(this)(a) }    //   <= how to pass T?
}

object eden$inline {
  def as(prefix: Any)(T: Any)(a: Any): Any = {
    val tp = T.asInstanceOf[scala.meta.Type]
    val term = a.asInstanceOf[scala.meta.Term]
    q"$term.asInstanceOf[$tp]"
  }
}

But in the meta block above, how do we pass T to the implementation, so that inlining & type safety are not compromised?
Note that without inlining, we don't face this problem, as we don't have the call eden$inline.as(this)(a) as part of the code.

Type parameters are supported in e9e392bac516612ccca6b44057f2937ed61f8373. I ended up doing away with the complication of inlining. I resort to a special flag macro to tell whether to expand a macro or not. https://github.com/liufengyun/dotty/commit/ef16d23360e075b3e23db99158d62859a55526dd
It seems we can implement macros much simpler without inlining. Inlining is itself another category of useful macros with better foundation. Mix them together seems to make both harder.

Nice progress! Am I right in thinking that you only support meta blocks that are the sole right-hand sides of inline methods (by translating such methods into <macro> something)?

Yes, the translation is the same before, except we remove the inline flag and add macro flag, to avoid inlining.
I don't know how to translate meta blocks that are in the middle of an expression and reflectively expand such meta blocks.

Improvement of typing to avoid asInstanceOf boilerplate is now implemented in https://github.com/liufengyun/dotty/commit/26ee23a1624e728da761506775caf7b2559ef187 and https://github.com/liufengyun/eden/commit/acc43d3f9b6f451ca3edb34ec05812d483248e99 .

Close this for now.


Custom index configuration

There is no information in docs how I can configure and create custom index with sleimanx2/plastic.
So, as sleimanx2/plastic is a wrapper over elastic/elasticsearch-php I can create console artisan command for index configuration and creation using elastic/elasticsearch-php package.
But it looks weird. Can I setup custom index with sleimanx2/plastic?

currently plastic does not handle index creation, the way to do it is using the default client as you mentioned.


75 int96 read as raw type

Fixes
Issue #75
Description
Used parquetoptions properties to toggle between dates and bigintegers
Todos

[x] unit/integration tests
[x] documentation

Looks good )


Upgrade RKE to use the latest ingress-nginx 1.16.x

We should upgrade RKE ingress-nginx image to the latest release: https://github.com/kubernetes/ingress-nginx/releases/tag/nginx-0.14.0

https://github.com/rancher/ingress-nginx has new tag nginx-0.14.0-rancher1

New Ingress tag for us is nginx-0.16.2-rancher1. @deniseschannon Could you help to create and push the new docker image for this tag in https://github.com/rancher/ingress-nginx? And I can have someone to review my types PR https://github.com/rancher/types/pull/418.

We had to revert the fix for this issue due to https://github.com/rancher/rancher/issues/14660. The revert pr: https://github.com/rancher/types/pull/513.

The build for the previous image wasn't built correctly. Please re-run validation to confirm that ingress is not having any issues.

rancher/rancher:master 7/25
Automation tests for ingress all passed.


Proposal: make Gitea use its own customized global config

Background
In history, Gitea uses default (system/global) git config file. It would cause a problem: conflicting with user's git config if the Gitea instance is running without isolation.
Proposal
According to:  https://git-scm.com/docs/git-config#_environment , set GIT_CONFIG_GLOBAL to use a git config inside Gitea's data directory, and set GIT_CONFIG_NOSYSTEM to skip the system git config.
Benefits
Then Gitea can set any git option it needs in its own customized git config. And it avoids unexpected git problems caused by user's incorrect git config.
Breaking or not
To upgrade from an existing Gitea instance (there is no customized git config for Gitea yet):

Breaking way: if there is no customized git config for Gitea, then ignore the existing git config and create a new customized git config for Gitea from scratch. If some users ever set some options for Gitea in their global/system git config, this way would lose these options. Users can set these options in the customized git config manually later.

Non-breaking way: copy the existing global/system git config options into the customized git config. This way would bring in some unrelated (maybe incorrect) config options.

In my mind the Breaking way is the preferred method, because it's clear, and normally users shouldn't have set any Gitea-related options in their git config. So it's not that breaking indeed.
Reference

https://git-scm.com/docs/git-config

The PR is ready for review. More complex than I thought because various reasons .....

#19732


Sceneform particle system?

Hello, first of all, thanks for a great update with FBX animations in Sceneform 1.7.0. I have a feature request, do you guys plan to implement some particle system into Sceneform?  Both ViroCoreAR and ARKit have one...

Can your animation work properly? I was able to work in the virocore FBX file before. Now the model will disappear when the animation starts on sceneform

Some FBX transformation SFB files also fail to create sfa files

Yes, the work, the FBX file needs to be valid, if you have animation files in a separate file you need to add them when importing. Also if you import assets with textures remember that you need to have relative paths to textures. Also, the roughness map needs to only use the red channel if you use one. I haven't figured out how to create valid roughness map yet since Sceneform docs aren't super precise on this part...

My animation is included in the FBX file, similar to the dae file. Could you please help me check my file? Thank you
apple.zip

This FBX file works in both virocore and web, but cannot be converted to an SFB file


Horizontal scroll bar issue

I noticed that the help button contains a horizontal scroll bars, suspected that is was messed by some global styling but after checking your website I noticed you have this issue as well ( see the attached images)
On windows:

On Mac:

Thanks for taking a look at this.

temporary fox for now.
setTimeout(() => {
    const userFlowFrame = document.querySelector(
      'iframe.userflowjs-resource-center-frame'
    ) as HTMLIFrameElement;
    if (!userFlowFrame) return;
    const resourceDiv = userFlowFrame.contentWindow.document.querySelector(
      '.userflowjs-resource-center-frame-root--closed'
    ) as HTMLDivElement;
    if (resourceDiv) {
      resourceDiv.style.width = 'unset';
    }
  }, 1000);

I had to rely on setTimeout since there is no event that I can use to know that userflow is mounted, it would be a great addition if you can add that to the list of supported event listeners

Hi @agnostic-coder,
Thanks for reporting this! It was a display issue introduced today only visible with the "Show scroll bars: Always" setting.
It has been fixed now. Sorry for the trouble :)


Feature/86 linq2db support

Added Linq2Db Support
Substantially refactored repository interfaces and underlying implementations.
Added a base unit testing data project to simplify unit testing across multiple repositories.
Enhanced unit testing across repository implementations.

Good to go!


Make istioctl install output more user friendly

Changes progress output to be more user facing, from this:
$ ic install --charts manifests --set profile=demo
- Processing resources for components Base.
✔ Component Base installed
✔ Component Pilot installed
✔ Component EgressGateways installed
✔ Component IngressGateways installed
✔ Component AddonComponents installed
- Pruning removed resources                                                                                Pruned object PodDisruptionBudget:istio-system:istio-egressgateway.
Pruned object Deployment:istio-system:istio-egressgateway.
✔ Installation complete

to this:
$ ic install --charts manifests --set profile=default
- Processing resources for Istio core.
✔ Istio core installed
✔ Istiod installed
✔ Addons installed
✔ Ingress gateways installed
- Pruning removed resources                                                                                Removed PodDisruptionBudget:istio-system:istio-egressgateway.
Removed Deployment:istio-system:istio-egressgateway.
✔ Installation complete

@ostromart: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
d383abbf13a3d6a51f0a80c5b1ee5a6c639ce2f6
link
/test lint_istio

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

@ostromart: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
d383abbf13a3d6a51f0a80c5b1ee5a6c639ce2f6
link
/test lint_istio

gencheck_istio
d383abbf13a3d6a51f0a80c5b1ee5a6c639ce2f6
link
/test gencheck_istio

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

@ostromart: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
d383abbf13a3d6a51f0a80c5b1ee5a6c639ce2f6
link
/test lint_istio

gencheck_istio
d383abbf13a3d6a51f0a80c5b1ee5a6c639ce2f6
link
/test gencheck_istio

unit-tests_istio
d383abbf13a3d6a51f0a80c5b1ee5a6c639ce2f6
link
/test unit-tests_istio

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

- Pruning removed resources
Removed Deployment:istio-system:istio-egressgateway.

should be
- Pruning removed resources
- Removed Deployment:istio-system:istio-egressgateway.

or something probably or something else?

Changed to:
- Pruning removed resources
  Removed Deployment:istio-system:istio-egressgateway.

@ostromart: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
d383abbf13a3d6a51f0a80c5b1ee5a6c639ce2f6
link
/test unit-tests_istio

gencheck_istio
a7326ab1943bc995606ad16a599247b8fc9c60b5
link
/test gencheck_istio

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

@ostromart: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
a7326ab1943bc995606ad16a599247b8fc9c60b5
link
/test gencheck_istio

unit-tests_istio
a7326ab1943bc995606ad16a599247b8fc9c60b5
link
/test unit-tests_istio

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

@ostromart: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
99e392c854b97eadbb31bf0bfb28290272b73f28
link
/test unit-tests_istio

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

@ostromart: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
99e392c854b97eadbb31bf0bfb28290272b73f28
link
/test unit-tests_istio

integ-local-tests_istio
99e392c854b97eadbb31bf0bfb28290272b73f28
link
/test integ-local-tests_istio

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

/retest

In response to a cherrypick label: #23424 failed to apply on top of branch "release-1.6":
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	operator/cmd/mesh/manifest-apply.go
M	operator/pkg/helmreconciler/prune.go
M	operator/pkg/helmreconciler/reconciler.go
M	operator/pkg/util/progress.go
M	operator/pkg/util/progress_test.go
Falling back to patching base and 3-way merge...
Auto-merging operator/pkg/util/progress/progress_test.go
Auto-merging operator/pkg/util/progress/progress.go
CONFLICT (content): Merge conflict in operator/pkg/util/progress/progress.go
Auto-merging operator/pkg/helmreconciler/reconciler.go
CONFLICT (content): Merge conflict in operator/pkg/helmreconciler/reconciler.go
Auto-merging operator/pkg/helmreconciler/prune.go
CONFLICT (content): Merge conflict in operator/pkg/helmreconciler/prune.go
Auto-merging operator/cmd/mesh/manifest-apply.go
CONFLICT (content): Merge conflict in operator/cmd/mesh/manifest-apply.go
Patch failed at 0001 Make istioctl install output more user friendly

cc @ostromart @brian-avery @irisdingbj
The cherry-pick failed and does not have a manual cherry picked PR for 1.6. I see that @ostromart has a commit that references this, but there is no PR yet. This is being used for documentation purposes.

/cherry-pick release-1.6

@jacob-delgado: #23424 failed to apply on top of branch "release-1.6":
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	operator/cmd/mesh/manifest-apply.go
M	operator/pkg/helmreconciler/prune.go
M	operator/pkg/helmreconciler/reconciler.go
M	operator/pkg/util/progress.go
M	operator/pkg/util/progress_test.go
Falling back to patching base and 3-way merge...
Auto-merging operator/pkg/util/progress/progress_test.go
Auto-merging operator/pkg/util/progress/progress.go
CONFLICT (content): Merge conflict in operator/pkg/util/progress/progress.go
Auto-merging operator/pkg/helmreconciler/reconciler.go
CONFLICT (content): Merge conflict in operator/pkg/helmreconciler/reconciler.go
Auto-merging operator/pkg/helmreconciler/prune.go
CONFLICT (content): Merge conflict in operator/pkg/helmreconciler/prune.go
Auto-merging operator/cmd/mesh/manifest-apply.go
CONFLICT (content): Merge conflict in operator/cmd/mesh/manifest-apply.go
Patch failed at 0001 Make istioctl install output more user friendly

In response to this:

/cherry-pick release-1.6

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

@jacob-delgado: new issue created for failed cherrypick: #23630

In response to this:

/cherry-pick release-1.6

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


geoserver issue on JS2

weird issue, highres works, however, coloring is not working
possible issue
https://stackoverflow.com/questions/66526411/geoserver-advice-please-http-status-400-bad-request

https://dev.to/iamtekson/using-nginx-to-put-geoserver-https-4204
in geoserver-2.22/webapps/geoserver/WEB-INF/web.xml
un_comment three parts, modify the urls
    <context-param>
      <param-name>PROXY_BASE_URL</param-name>
      <param-value>https://example.com/geoserver</paramvalue>
    </context-param>

two parts for CORS
then add one more entry:
<context-param>
  <param-name>GEOSERVER_CSRF_WHITELIST</param-name>
  <param-value>example.org</param-value>
</context-param>

restart geoserver

also under global setting in geoserver:
put in proxy base url and check "Use headers for proxy url"


fix!: Fix tests related to output struct rename

Issue #
#1169
Description of changes
The companion to this PR https://github.com/smithy-lang/smithy-swift/pull/599 changes the name suffix of operation output structures from OutputResponse to just Output.
This PR just fixes codegen tests affected by this name change.
New/existing dependencies impact assessment, if applicable
No new dependencies were added to this change.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/test


Update travis.yml: Add node 7

Coverage decreased (-5.9%) to 69.649% when pulling f43548593804e01d2b9057b9bc831c97ac4c8d92 on travis-node-6-and-7 into 611e3e7dee4455cd4f6c45d325e6e8da2fb71787 on master.


[stdlib] Make unavailable protocol implementation @_alwaysEmitIntoClient

…and add a comment about use of Lemire's nearly divisionless method.
In follow-up to #38161, make the clever recursion-breaking protocol implementation @_alwaysEmitIntoClient in addition to being unavailable.
Additionally, in follow-up to #25286, add a brief comment in the code about the use of Lemire's nearly divisionless method; the code is very neat but without any comment a reader who is unfamiliar with the algorithm has no easy way of understanding what's going on.
If accepted, this change should be nominated for inclusion in Swift 5.5 as per discussion in #38161.

@swift-ci smoke test

Hah, saw this after I already opened https://github.com/apple/swift/pull/38273

Heh, I threw the @_aEIC change in only because I was already editing the file. The principal purpose of this PR is to add the comment to help readers understand what’s going on. Happy to rebase if your merge goes through.

@stephentyrone OK to merge?


Rename all example datasets to default dataset

Also makes it a public method.
Fixes #67

Yeah, makes sense to make it a public method as well.


Insert R code chunk snippet does not work for selected text.

Reprex

Make test.Rmd.

Write two lines and select.
x <- 1
(y <- x + 2)

Do Insert Snippet -> r code chunk, Insert R code chunk

See if the two lines are surrounded with R code chunk fence:  the two lines are completely replaced with R code snippet.
```{r}

```

@renkun-ken, sorry, I'm not very familiar with git operation for collaborative work, I'm still studying it. , It may be better to use "${TM_SELECTED_TEXT}$0" in this .


Typo in testnet name

The Görli testnet is spelled goerli not georli.
I can send a PR to fix it, just nott sure how you want to handle it since this might be a breaking change.

https://github.com/seanjameshan/starknet.js/pull/97


Add question template

Which issue does this PR close?

Closes #.
Rationale for this change

For some issues (like #640), they are neither bug reports nor feature requests. It's just a question about something.
This template is for such "question" issues. Makes it easier to file and manager issues.
What changes are included in this PR?
Add issue template.

Are there any user-facing changes?
No.

Codecov Report

Merging #649 (ce93139) into master (b38a4b6) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head ce93139 differs from pull request most recent head 8a5e036. Consider uploading reports for the commit 8a5e036 to get more accurate results

@@           Coverage Diff           @@
##           master     #649   +/-   ##
=======================================
  Coverage   82.50%   82.50%
=======================================
  Files         168      168
  Lines       47237    47237
=======================================
  Hits        38971    38971
  Misses       8266     8266

Continue to review full report at Codecov.

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

Thanks @waynexia !


Allow generating workflow tasks if workflow is non-current

What changed?

Add UpdateWorkflowExecutionTasks in wf context for only generating workflow tasks.
Add a new workflow update mode IgnoreCurrent to bypass checks and updates to current execution record
Update cross-cluster operations and admin wf refresh to use UpdateWorkflowExecutionTasks
Allow running admin wf refresh on standby cluster

Why?

We need a way to only generate some workflow tasks and don't update the workflow itself at all. This is useful for the refresh admin command and also cross-cluster operations (since we need to convert between transfer and x-cluster tasks after workflow close)
Existing update workflow code path only supports two modes: 1. the workflow being updated must be current workflow 2. the workflow being updated must NOT be current workflow. But in our case, the workflow may or may not be the current workflow so we need a new code path for it.
Workflow refresh command should also be available on the standby side.

How did you test it?

Added new unit tests
Tested locally for admin wf refresh on both active and standby cluster.

Potential risks

Workflow refresh may stop working
X-cluster operations may have issues and we can't convert between transfer and x-cluster tasks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 06804b7d-d822-4ec4-b730-f6e0280e6ce3

35 of 192 (18.23%)  changed or added relevant lines in 10 files are covered.
121 unchanged lines in 9 files lost coverage.
Overall coverage increased (+0.001%) to 56.9%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

common/persistence/sql/sqlExecutionStore.go
0
1
0.0%

service/history/historyEngine.go
0
2
0.0%

common/persistence/nosql/nosqlExecutionStore.go
0
4
0.0%

service/history/task/transfer_active_task_executor.go
22
31
70.97%

common/persistence/persistence-tests/persistenceTestBase.go
0
16
0.0%

service/history/execution/context.go
0
45
0.0%

common/persistence/persistence-tests/executionManagerTest.go
0
80
0.0%

Files with Coverage Reduction
New Missed Lines
%

service/history/task/transfer_active_task_executor.go
1
71.93%

common/task/fifoTaskScheduler.go
2
87.63%

common/task/weightedRoundRobinTaskScheduler.go
2
89.64%

service/matching/matcher.go
2
91.46%

service/matching/taskListManager.go
2
74.19%

service/history/task/fetcher.go
4
86.15%

common/persistence/nosql/nosqlplugin/cassandra/tasks.go
14
72.8%

common/persistence/nosql/nosqlTaskStore.go
16
58.37%

service/history/shard/context.go
78
66.22%

Totals

Change from base Build e45f7120-9897-426b-9ada-96fd4f373374:
0.001%

Covered Lines:
82859

Relevant Lines:
145621

💛  - Coveralls


MODEL_TYPE and TASK_NAME : more details

Hi,
could you please explain the MODEL_TYPE and TASK_NAME options ?
I have a large number of DHS sequences and I want to use the sequence embeddings for downstream processing
Thanks

Currently, there are only two possible choices for MODEL_TYPE, dna and dnalongcat. The dna is used for sequences shorter than 512 and the second one is used for longer sequences. When using dnalongcat, please make sure the sequence length equals to N*512 (e.g., 1024, 2048).
The TASK_NAME is used for the code the understand what task you want to perform and how the data should be load. For 2-class classification with your own data, you can process the data to the format as the sample data and set TASK_NAME as dnaprom. For other cases, you need to define your own task, which is more complicated.
First, go to src/transformers/data/processors.py to define a new processor class for your own data (including the number of labels and how to load data). Second, go to the bottom of this file to update these three dictionaries, which is straightforward. Third, go to the src/transformers/data/metrics/__init__.py line 98 to define the metric (e.g., f1/accuracy) you want to calculate for your task.

Thanks for explaining.
Are the available pretrained models of MODEL_TYPE dna or dnalongcat ?
If they are of MODEL_TYPE dna, do you have a pretrained model of
MODEL_TYPE dnalongcat ?
Thanks
On Wed, Dec 16, 2020 at 8:31 PM Zhihan Zhou<EMAIL_ADDRESS>wrote:

Currently, there are only two possible choices for MODEL_TYPE, dna and
dnalongcat. The dna is used for sequences shorter than 512 and the second
one is used for longer sequences. When using dnalongcat, please make sure
the sequence length equals to N*512 (e.g., 1024, 2048).
The TASK_NAME is used for the code the understand what task you want to
perform and how the data should be load. For 2-class classification with
your own data, you can process the data to the format as the sample data
and set TASK_NAME as dnaprom. For other cases, you need to define your own
task, which is more complicated.
First, go to src/transformers/data/processors.py to define a new
processor class for your own data (including the number of labels and how
to load data). Second, go to the bottom of this file to update these three
dictionaries, which is straightforward. Third, go to the
src/transformers/data/metrics/init.py line 98 to define the metric
(e.g., f1/accuracy) you want to calculate for your task.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jerryji1993/DNABERT/issues/5#issuecomment-747145587,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACPSFVFSSWWWXDT6MYN7GX3SVFNPHANCNFSM4UV5BGBA
.

Sure. The pre-trained models work for both dna and dnalongcat. Please directly use them.

ok. Thanks
On Wed, Dec 16, 2020 at 9:31 PM Zhihan Zhou<EMAIL_ADDRESS>wrote:

Sure. The pre-trained models work for both dna and dnalongcat. Please
directly use them.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jerryji1993/DNABERT/issues/5#issuecomment-747164297,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACPSFVFM35TEEH4DXHK3F63SVFURHANCNFSM4UV5BGBA
.

Hi,
about your suggestions to modify the code, I have a few questions:

the src/transformers/data/processors.py does not exist or I cannot see it. Do I have to create it ?
what three directories ? at the bottom of which file ? processors.py ?

Thanks

Hi, How can I fintune the model for regression cases?


Update B2C RedirectURI

Purpose

Updated RedirectURI in Readme file of B2C sample.
Does this introduce a breaking change?

[ ] Yes
[x ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ x] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code
Follow instructions in readme

Seems like a minor readme change - just confirming that the app logic has also been changed to reflect the redirect URI that is outlined in the readme?

Only Readme update is done, code change was not required.
Thanks Sam.


Werkzeug server is shutting down in Django application

related to: #2387 and #1715
i know that the workaround is to delete the line 326 and replace it with environ.pop('werkzeug.server.shutdown',None)
or to use this command --keep-meta-shutdown
but this is not a solution , I should not interfere with the package code to make it working
is there any near update that targets this fix?
after updating the Werkzeug version from 2.0.3 to 2.1.0, I keep getting errors every time I run the server, and here is the error log:
Exception happened during processing of request from ('<IP_ADDRESS>', 44612)
Traceback (most recent call last):
  File "/usr/lib/python3.8/socketserver.py", line 683, in process_request_thread
    self.finish_request(request, client_address)
  File "/usr/lib/python3.8/socketserver.py", line 360, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/usr/lib/python3.8/socketserver.py", line 747, in __init__
    self.handle()
  File "/home/oladhari/.virtualenvs/reachat/lib/python3.8/site-packages/werkzeug/serving.py", line 363, in handle
    super().handle()
  File "/usr/lib/python3.8/http/server.py", line 427, in handle
    self.handle_one_request()
  File "/usr/lib/python3.8/http/server.py", line 415, in handle_one_request
    method()
  File "/home/oladhari/.virtualenvs/reachat/lib/python3.8/site-packages/werkzeug/serving.py", line 243, in run_wsgi
    self.environ = environ = self.make_environ()
  File "/home/oladhari/.virtualenvs/reachat/lib/python3.8/site-packages/django_extensions/management/commands/runserver_plus.py", line 326, in make_environ
    del environ['werkzeug.server.shutdown']
KeyError: 'werkzeug.server.shutdown'

this exception keep appearing while incrementing by 2 ( ('<IP_ADDRESS>', 44612) ->  ('<IP_ADDRESS>', 44628)  and the server crash
checking the changes log, I have found this detail:
Remove previously deprecated code. #2276

Remove the non-standard shutdown function from the WSGI environ when running the development server. See the docs for alternatives.

here is the link to the changes log
it asks to check the documentation for alternatives but can not find any
please let me know how I would resolve this error, thank you
Environment:

Python version: 3.8
Werkzeug version: 2.1.0

have same.
try to patch to keep it's work
        class WSGIRequestHandler(_WSGIRequestHandler):             def make_environ(self):                 environ = super().make_environ()                 if not options['keep_meta_shutdown_func']:                     **if 'werkzeug.server.shutdown' in environ.keys():**                         del environ['werkzeug.server.shutdown']                 return environ


Secretless has a MSSQL connector

From @beaudryj:
Secretless has a MSSQL connector
TBD
Aha Cards

Link to Aha Card

Team

Product Manager: Naama Schwartzblat
Engineering Manager: Geri Jennings (@izgeri)
Feature Lead: TBD
Engineers:

TBD

SDLC Timeline

Stage
Status
Date (or ETA)
Artifact
GH Issue

High Level Feature Doc
started
yyyy-mm-dd
Feature Doc
Link to Feature Doc GH issue

Functional Sign-off
Not Scheduled
yyyy-mm-dd
See above

Detailed Feature Doc
Not Done
-
Feature Spec
Link to Feature spec GH issue

Design doc
Done\ Not Done
[Design doc]
link to design doc

Solution Sign-off
Not Scheduled
-

Execution
Not Started
-

Epicor wants this.


Hooray! Just a few days after clang 4.0 is released :) Thanks!

Now we just have to wait once more for 4.0 (https://github.com/travis-ci/apt-source-whitelist/issues/360).

@mattgodbolt should we add a clang4.0 ci build? We could drop one of the older clang's (3.6?) to keep the number of builds low.

Yes, let's add 4.0 if it's easy. I don't necessarily think we should drop
clang 3.6 just yet. I'm always amazed how far behind some people can be...!
On Wed, Mar 15, 2017 at 7:33 AM offa<EMAIL_ADDRESS>wrote:

@mattgodbolt https://github.com/mattgodbolt should we add a clang4.0 ci
build? We could drop one of the older clang's (3.6?) to keep the number of
builds low.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mattgodbolt/seasocks/pull/64#issuecomment-286728030,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAmsdT-QrA1_B3EH94K_vuclaoahn9OIks5rl9qkgaJpZM4Md2xI
.

Ok, I can add it (as I'm currently doing this for another project too).


sap.tnt.NavigationList shows only two levels of sap.tnt.NavigationListItem

OpenUI5 version:
1.36.8
Browser/version (+device/version):
IE 11, Chrome 50, Firefox 42
Any other tested browsers/devices(OK/FAIL):
URL (minimal example if possible):
User/password (if required and possible - do not post any confidential information here):
Steps to reproduce the problem:

Create an sap.tnt.NavigationList and try adding three levels of sap.tnt.NavigationListItem
Once control is rendered, try to expand the list

What is the expected result? Should be  able to navigate till 3rd level
What happens instead? Restricted to 2nd level only. There is no expand/collapse icon for 3rd level
Any other information? (attach screenshot if possible)
There is a thread in scn.sap.com saying  that by mere extending the control without any changes works perfectly. Here is the direct URL to access the same:
http://scn.sap.com/thread/3882580

Hi,
the sap.tnt.NavigationList supports only 2 level navigation.
Best,
Teo

Well, then at least update the API documentation to reflect the same. I am sure there would be a lot of people showing interest in this control and after implementation come to know that it allows two levels only. Please ignore if documentation already reflects the same.
~Prospecta


Panic: docker socket permission denied

Me and i guess a lot of others will have no permissions to access the docker socket by default, (see error)
When i type lazydocker it panics because docker can't access the docker socket.
The error:
mark@that-laptop-with-solus-os ~> lazydocker
2019/06/30 11:56:06 An error occurred! Please create an issue at https://github.com/jesseduffield/lazydocker/issues

*errors.withStack Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.25/images/json: dial unix /var/run/docker.sock: connect: permission denied
/home/mark/go/src/github.com/jesseduffield/lazydocker/main.go:63 (0x81fed1)
	main: newErr := errors.Wrap(err, 0)
/usr/lib64/golang/src/runtime/proc.go:200 (0x42f1dc)
	main: fn()
/usr/lib64/golang/src/runtime/asm_amd64.s:1337 (0x45a131)
	goexit: BYTE	$0x90	// NOP

It would be nice if lazydocker just exits normally with a nice error like:
ERROR: Can't access docker socket at: unix:///var/run/docker.sock
Run lazydocker as root or read https://docs.docker.com/install/linux/linux-postinstall/

Hey @mjarkk long time no see :)
That sounds reasonable. I'm thinking that in main.go we could catch the error, check if it contains something like Got permission denied while trying to connect to the Docker daemon socket and then print the error you came up with?

I've put up a PR here https://github.com/jesseduffield/lazydocker/pull/14 let me know what you think :)

closin :)


Hotfix/take parameters from body in post and put routes

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

8.1.2
GitHub release

Your semantic-release bot :package::rocket:


minor nit and GH action version updates

Update helm to 3.10.2
Rename variables in test from kubectl to helm
Update Github Actions to use latest version of checkout and other actions

Hi @ajayk. Thanks for the PR. Can you sign the commits when you get the chance?

@OliverMKing / @jaiveerk : Can we please this get merged


Update recover-from-golden-gmsa-attack.md

update to describe side-effect of auth-restore
Pull request guidance
Thank you for submitting your contribution to our support content! Our team works closely with subject matter experts in CSS and PMs in the product group to review all content requests to ensure technical accuracy and the best customer experience. This process can sometimes take one or more days, so we greatly appreciate your patience.
We also need your help in order to process your request as soon as possible:

We won't act on your pull request (PR) until you type "#sign-off" in a new comment in your pull request (PR) to indicate that your changes are complete.

After you sign off in your PR, the article will be tech reviewed by the PM or SME if it has more than minor changes. Once the article is approved, it will undergo a final editing pass before being merged.

@HerbertMauerer The change will go live. This PR will be closed.


Not working for new Django releases

safety version: 1.8.5
Python version: 3.7.2
Operating System: Ubuntu 16.04

Description
I'm trying to verify that safety knowns about Django security releases.
What I Did
$ cat req.txt
Django==2.2.1
Flask==0.12.2
$ safety check -r req.txt
# It reports `flask` but not `Django`.

I understand that the free database is not always up to date but the Flask security report was published 2019-07-17 and it worked for that. But Django==2.2.2 was released 2019-06-03.

Same problem here. I'm on a paid plan, but safety ignores new Django patches. Tried to contact support, but they do not respond.

Still does not work. Does not detect e.g. CVE-2019-14235 (Django <2.2.4) or CVE-2019-14234.

I have looked at all issues raised in this thread and concluded that they are all now solved.
The PyUp team acknowledges that we were behind for quite a while. However, we're back on track now.
Yesterday, we sent out an apology email to all our users.


bump dependencies

Jade v1.11.0 has been released. https://github.com/jadejs/jade/blob/master/History.md
I've looked the changelog through and there seems to be no breaking changes related to this plugin.

:white_check_mark:  This PR passed all the tests. https://travis-ci.org/phated/gulp-jade/builds/69581408

Yes, this is useful commit! I had an issue with old jade version in gulp-jade when try to use multiline block code. So I've updated my local deps manually.

Would be rad to see this merged :) multiline block code is super useful!

This release looks stable (I typically let things simmer a few weeks).  I'll merge and bump


More consistent formatting of articles and other types

Originally reported in https://github.com/oscar-system/Oscar.jl/issues/3760.
We would like to streamline how our bibliography (ref https://docs.oscar-system.org/dev/references/) looks like, in particular, we would like to have the href for all bib entry types on the title. This works for everything so far, apart from the article type.
We mostly contain DOIs and no URLs (there is no entry that has both), so it would be great to have the first available link on the title, as is already done in https://github.com/JuliaDocs/DocumenterCitations.jl/blob/de9fd1fb2b9b453d7fc26009a0253b113dd42c08/src/formatting.jl#L207 for all other bib entry types.
This would make the aesthetics of the references page a lot more coherent.

The current formatting is definitely by design. I'm generally guided by RevTeX with the formatting, which links the article DOI via the "published in" information. The ability to link both a URL and a DOI is also a design goal. This leaves only the title as a second link location for articles. Conversely, non-articles don't necessarily have sufficient "published in" information to serve as link text, so there, the title becomes the primary link location.
Of, course, all of this is partly a matter of taste, but I'm not very inclined to change this. I'm absolutely open to adding options, or changing the code in some way, to make it easier to modify the behavior with a custom style. In general, I suspect such a custom style might have problems with linking both a URL and a DOI. If a particular project like Oscar.jl is careful only to have on or the other, consistently linking only from the title seems sensible.


Detecting missing letters?

Does misspell detect typos with missing letters?
E.g. confg instead of config.
Is it in misspell scope? It would be very useful IMHO.
It's probably possible to generate all such typos statically, given a word list.

Interesting idea.  Try it out!
http://app.aspell.net/create?max_size=60&spelling=US&max_variant=1&diacritic=both&download=wordlist&encoding=utf-8&format=inline
I suspect you'll find a few problems:

The word lists don't contain very many technical words, include many common ones.
Some words will be need to be rejected since it's ambiguous  (bad example: is fll full, fill, or fall?)
Some other words will need to be rejected since removing a letter turns it into a valid word
The size! there are at least 100,000 words,   All combinations of missing letters, might be 500,000 entries.   To make that work, I think misspell would need to be implemented very differently.

The strategy misspell is using is "common misspellings" or "probable misspellings", not "all possible misspellings".
that said, I'm happy to take a look at any patch or pull request for this.
thanks!
n

Hi @gavv  recently I added ~30,000 additional corrections.
let us know if it helps you.
n


Cherry Picked new KS-Sim (Bhatt) into ks_sim_fix

See Title, merging done together in zoom.

Perfekt, thanks!


operator 0.4.2 via operatorHub does not work

When trying to install 0.4.2 the operator does not roll out any oneagent & activegate pods.
There are no error messages in the logs of the dyntrace-operator or dynatrace-webhook pods.
Installing 0.4.2 via oc apply does seem to work but is not preferred.
Main difference that I found was that using oc apply the operator pods are scheduled in the dynatrace namespace as before.
While using operatorHub these pods are scheduled in the openshift-operator namespace.
OpenShift version information (if applicable):
openshift 4.8.27

Hi, we released 0.5.0 on operatorHub yesterday and the issues should be resolved :) Therefore I will close this issue. Thanks for your patience.

@luhi-DT  I've installed 0.5.0 today and the problem seems to persist.
I install the operator, it's installed in openshift-operators with AllNamespaces (no other option)
I create a namespace openshift-monitoring-dynatrace (tried dynatrace as well)
I create a dynakube secret containing necessary tokens in this namespace
And finally I create the dynakube in the namespace.
Unfortunately no oneagent/activegate pods are created

I have the exactly same problem with 0.5.0. I also tried openshift-monitoring and dynatrace namespace. No pods are started.


Added Checkstyle xml and classes to each submodule

@joshuad2 I believe we have this functionality covered now.  Is there anything we're missing from your contribution here?  If not, would you mind closing this PR?  Thanks for your contribution and looking forward to many more.


Set the max size in multiple curators choicefield.

@johngian / @comzeradd r?

r+
Tested it locally. max-inline-size matches the one in the above text area.


mixer report handler/instance not found when adding a custom adapter

Describe the bug
{{ Succinctly describe the bug }}
To add a custom adaptor, i add the the adaptor code in mixer/adapter/ and fix the inventory.yaml, and test it through integrationtest.
however when run the mixer image (through command "make docker compile") in kubernetes, it logs errors blew:
at this time the instance, handler and the rule of the custom adaptor haven't been created.
gc 1 @0.011s 7%: 0.048+0.62+0.97 ms clock, 2.3+0.10/2.2/0.64+46 ms cpu, 4->4->2 MB, 5 MB goal, 48 P
Mixer started with
MaxMessageSize: 1048576
MaxConcurrentStreams: 1024
APIWorkerPoolSize: 1024
AdapterWorkerPoolSize: 1024
APIPort: 9091
APIAddress: unix:///sock/mixer.socket
MonitoringPort: 9093
EnableProfiling: true
SingleThreaded: false
NumCheckCacheEntries: 1500000
ConfigStoreURL: k8s://
ConfigDefaultNamespace: istio-system
LoggingOptions: log.Options{OutputPaths:[]string{"stdout"}, ErrorOutputPaths:[]string{"stderr"}, RotateOutputPath:"", RotationMaxSize:104857600, RotationMaxAge:30, RotationMaxBackups:1000, JSONEncoding:false, LogGrpc:true, outputLevels:"default:info", logCallers:"", stackTraceLevels:"default:none"}
TracingOptions: tracing.Options{ZipkinURL:"http://zipkin:9411/api/v1/spans", JaegerURL:"", LogTraceSpans:false}
IntrospectionOptions: ctrlz.Options{Port:0x2694, Address:"<IP_ADDRESS>"}
LoadSheddingOptions: loadshedding.Options{Mode:0, AverageLatencyThreshold:0, SamplesPerSecond:1.7976931348623157e+308, SampleHalfLife:1000000000, MaxRequestsPerSecond:0, BurstSize:0}

gc 2 @0.021s 11%: 0.055+3.0+1.6 ms clock, 2.6+0.080/7.2/2.4+80 ms cpu, 4->5->3 MB, 5 MB goal, 48 P
2018-12-10T07:23:39.290871Z	warn	Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
2018-12-10T07:23:39.291258Z	info	Built new config.Snapshot: id='0'
2018-12-10T07:23:39.291313Z	info	Cleaning up handler table, with config ID:-1
gc 3 @0.036s 12%: 0.19+1.5+1.7 ms clock, 9.3+2.0/11/0.81+84 ms cpu, 6->8->4 MB, 7 MB goal, 48 P
2018-12-10T07:23:39.304506Z	warn	Failed to discover kinds: [dogstatsd cloudwatch], start retry in background
2018-12-10T07:23:39.304626Z	info	Built new config.Snapshot: id='1'
2018-12-10T07:23:39.304667Z	info	Cleaning up handler table, with config ID:0
2018-12-10T07:23:39.304675Z	info	Awaiting for config store sync...
gc 4 @0.040s 16%: 0.23+1.3+1.6 ms clock, 11+1.7/11/0+77 ms cpu, 7->8->5 MB, 8 MB goal, 48 P
2018-12-10T07:23:40.305556Z	info	Publishing 9 events
2018-12-10T07:23:40.306465Z	error	Handler not found: handler='handler.prometheus'
2018-12-10T07:23:40.306478Z	error	No valid actions found in rule
2018-12-10T07:23:40.306493Z	error	Instance not found: instance='attributes.kubernetes'
2018-12-10T07:23:40.306508Z	error	No valid instances found
2018-12-10T07:23:40.306512Z	error	No valid actions found in rule
2018-12-10T07:23:40.306524Z	error	Handler not found: handler='handler.prometheus'
2018-12-10T07:23:40.306529Z	error	No valid actions found in rule
2018-12-10T07:23:40.306539Z	error	Instance not found: instance='attributes.kubernetes'
2018-12-10T07:23:40.306553Z	error	No valid instances found
2018-12-10T07:23:40.306557Z	error	No valid actions found in rule
2018-12-10T07:23:40.306562Z	info	Built new config.Snapshot: id='2'
2018-12-10T07:23:40.306615Z	info	Cleaning up handler table, with config ID:1
gc 5 @1.437s 0%: 0.035+1.4+1.6 ms clock, 1.7+0.13/9.5/3.5+77 ms cpu, 8->8->5 MB, 10 MB goal, 48 P
2018-12-10T07:23:41.504514Z	info	Publishing 8 events
2018-12-10T07:23:41.506106Z	info	Built new config.Snapshot: id='3'
2018-12-10T07:23:41.506190Z	info	adapters	getting kubeconfig from: ""	{"adapter": "handler.kubernetesenv.istio-system"}
2018-12-10T07:23:41.506204Z	warn	Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
2018-12-10T07:23:41.507014Z	info	adapters	Waiting for kubernetes cache sync...	{"adapter": "handler.kubernetesenv.istio-system"}
gc 6 @2.260s 0%: 0.025+1.5+1.6 ms clock, 1.2+0.46/12/5.1+78 ms cpu, 10->10->6 MB, 11 MB goal, 48 P
gc 7 @2.267s 0%: 0.11+1.4+1.5 ms clock, 5.7+0.69/13/3.6+74 ms cpu, 11->12->9 MB, 12 MB goal, 48 P
gc 8 @2.283s 0%: 0.023+1.7+2.1 ms clock, 1.1+1.3/16/6.9+101 ms cpu, 17->18->11 MB, 18 MB goal, 48 P
gc 9 @2.296s 0%: 0.017+2.3+2.3 ms clock, 0.82+0.88/20/1.5+110 ms cpu, 22->23->13 MB, 23 MB goal, 48 P
2018-12-10T07:23:41.607115Z	info	adapters	Cache sync successful.	{"adapter": "handler.kubernetesenv.istio-system"}
2018-12-10T07:23:41.607615Z	info	adapters	serving prometheus metrics on 42422	{"adapter": "handler.prometheus.istio-system"}
2018-12-10T07:23:41.609145Z	info	Cleaning up handler table, with config ID:2
2018-12-10T07:23:43.703019Z	info	Publishing 1 events
2018-12-10T07:23:43.704386Z	info	Built new config.Snapshot: id='4'
2018-12-10T07:23:43.704536Z	info	adapters	getting kubeconfig from: ""	{"adapter": "handler.kubernetesenv.istio-system"}
2018-12-10T07:23:43.704547Z	warn	Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
2018-12-10T07:23:43.705235Z	info	adapters	Waiting for kubernetes cache sync...	{"adapter": "handler.kubernetesenv.istio-system"}
gc 10 @4.464s 0%: 0.042+2.5+2.4 ms clock, 2.0+0.65/26/5.7+118 ms cpu, 25->26->17 MB, 26 MB goal, 48 P
gc 11 @4.487s 0%: 0.016+3.3+3.1 ms clock, 0.77+1.8/30/11+152 ms cpu, 32->33->23 MB, 33 MB goal, 48 P
2018-12-10T07:23:43.805350Z	info	adapters	Cache sync successful.	{"adapter": "handler.kubernetesenv.istio-system"}
2018-12-10T07:23:43.807119Z	info	Cleaning up handler table, with config ID:3
2018-12-10T07:23:43.807139Z	error	adapters	adapter did not close all the scheduled daemons	{"adapter": "handler.kubernetesenv.istio-system"}
2018-12-10T07:23:43.807150Z	error	adapters	adapter did not close all the scheduled daemons	{"adapter": "handler.prometheus.istio-system"}
gc 12 @5.448s 0%: 0.021+4.1+4.6 ms clock, 1.0+3.9/44/38+222 ms cpu, 94->94->89 MB, 95 MB goal, 48 P
gc 13 @5.463s 0%: 0.010+20+6.4 ms clock, 0.48+0.17/60/38+307 ms cpu, 136->136->136 MB, 179 MB goal, 48 P
2018-12-10T07:23:44.754177Z	info	Starting monitor server...
Istio Mixer<EMAIL_ADDRESS>Starting gRPC server on port 9091
2018-12-10T07:23:44.757165Z	info	ControlZ available at <IP_ADDRESS>:9876
gc 14 @101.074s 0%: 0.043+20+6.9 ms clock, 2.0+0.34/59/26+332 ms cpu, 175->175->137 MB, 273 MB goal, 48 P
scvg0: inuse: 161, idle: 18, sys: 179, released: 0, consumed: 179 (MB)
GC forced
gc 15 @221.141s 0%: 0.037+15+6.8 ms clock, 1.7+0/48/33+329 ms cpu, 184->184->137 MB, 274 MB goal, 48 P
scvg1: inuse: 171, idle: 17, sys: 188, released: 0, consumed: 188 (MB)

the mixer config is blew:
kubectl get rules --all-namespaces
NAMESPACE      NAME                     AGE
istio-system   kubeattrgenrulerule      3d
istio-system   promhttp                 3d
istio-system   promtcp                  3d
istio-system   tcpkubeattrgenrulerule   3d

kubectl get crd -listio=mixer-adapter
NAME                              AGE
adapters.config.istio.io          3d
bypasses.config.istio.io          3d
circonuses.config.istio.io        3d
deniers.config.istio.io           3d
fluentds.config.istio.io          3d
myadaptor.config.istio.io       3d
kubernetesenvs.config.istio.io    3d
listcheckers.config.istio.io      3d
memquotas.config.istio.io         3d
noops.config.istio.io             3d
opas.config.istio.io              3d
prometheuses.config.istio.io      3d
rbacs.config.istio.io             3d
redisquotas.config.istio.io       3d
servicecontrols.config.istio.io   3d
signalfxs.config.istio.io         3d
solarwindses.config.istio.io      3d
stackdrivers.config.istio.io      3d
statsds.config.istio.io           3d
stdios.config.istio.io            3d

kubectl get crd -listio=mixer-instance
NAME                                    AGE
apikeys.config.istio.io                 3d
authorizations.config.istio.io          3d
checknothings.config.istio.io           3d
edges.config.istio.io                   3d
instances.config.istio.io               3d
kuberneteses.config.istio.io            3d
listentries.config.istio.io             3d
logentries.config.istio.io              3d
metrics.config.istio.io                 3d
quotas.config.istio.io                  3d
reportnothings.config.istio.io          3d
servicecontrolreports.config.istio.io   3d
tracespans.config.istio.io              3d

Expected behavior
{{ What did you expect to happen? }}
Steps to reproduce the bug
{{ Minimal steps to reproduce the behavior }}
Version
{{ What version of Istio and Kubernetes are you using? Use istioctl version and kubectl version }}
istio:1.0.4
Installation
{{ Please describe how Istio was installed }}
Environment
{{ Which environment, cloud vendor, OS, etc are you using? }}
Cluster state
{{ If you're running on Kubernetes, consider following the
instructions
to generate "istio-dump.tar.gz", then attach it here by dragging and dropping
the file onto this issue. }}

I'm not clear on the issue. Would you mind providing more detail?  Did you provide config for a new instance and a new handler?
The errors in the logs look related to start-up configuration of the Mixer instance, as it awaits a full configuration snapshot, which it eventually receives and starts processing.
I do not see any errors related to a new handler or a new instance (only prometheus and kubernetesenv).
Your kubectl get rules --all-namespaces does not show any new rules. Did you create them and apply them?

Closing, due to lack of updates.


LU LSP bugs

Describe the bug
In playing with the auto-suggest, auto-complete capabilities for LU,  I ran into the following issues -

Picking from the entity type (list) adds the entity type without a space and the parser complains of no space. We should not auto-complete content that will result in known parser errors.

repro:
1. Type '@' and wait for the entity type auto-suggest UI
2. Pick list entity type

Adding sub-lists in list entity definition is missing space after ‘-‘

repro:
1. Type '@ list city = ' and hit enter. Notice '- ' auto-complete for normalized value.
2. Type 'seattle : ' and hit enter
3. Notice we no longer offer auto-complete '- ' with appropriate indentation for sub-lists

Hyphen stops working on new utterances on new intent added after entity definition

repro:
1. Add an intent section - e.g.
# greeting
- hello
2. Then add an entity definition - e.g.
@ ml testEntity
3. Then add another intent section - e.g. '# testIntent' and hit enter
4. Notice the auto-complete for '- ' no longer works.

No hyphen auto-inserted after @ phraselist todoItem =

repro:
1. Type '@ phraselist test = ' and hit enter. We should auto-complete each line with '- ', this is just a list of values similar to intent definition.

No auto-suggest for (interchangeable) for phrase list

repro:
1. Type ' @ phraselist test('
We should offer auto-complete for '@ phraselist test(interchangeable)'

Version

Browser

[ ] Chrome
[ ] Safari
[ ] Firefox
[x] Edge

OS

[x] macOS
[ ] Windows
[ ] Ubuntu

addressed via https://github.com/microsoft/BotFramework-Composer/issues/2046


[SPARK-17585][PySpark][Core] PySpark SparkContext.addFile supports adding files recursively

What changes were proposed in this pull request?
PySpark SparkContext.addFile should support adding files recursively under a directory similar with Scala.
How was this patch tested?
Unit test.

Test build #65579 has started for PR 15140 at commit c277a2c.

Test build #65579 has finished for PR 15140 at commit c277a2c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65579/
Test PASSed.

cc @rxin @davies @srowen

Just one minor suggestion, otherwise LGTM

@BryanCutler Updated, thanks your comments.

Test build #65652 has started for PR 15140 at commit 6174f0d.

Test build #65652 has finished for PR 15140 at commit 6174f0d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65652/
Test PASSed.

@srowen Would you mind to have a look at this when you available? Thanks.

Merged into master. Thanks for all your review. @BryanCutler @srowen


feature-<#5631>-

Description
Creating a spread execution model to execute when spread is desirably small in C#.

Related Issue
#5631

Motivation and Context
To provide easy implementation of execution through tight spread to reduce slippage

Requires Documentation Change
Add desciption on this class in "Execution" page

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Refactor (non-breaking change which improves implementation)
[ ] Performance (non-breaking change which improves performance. Please add associated performance test and results)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Non-functional change (xml comments/documentation/etc)

Checklist:

[X] My code follows the code style of this project.
[X] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[X] My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

The tests failed by LiveOptionChainProviderReturnsNoDataForOldFuture. It is unrelated to the execution model here itself, I'm confused on passing the tests.


lightwalletd: Implement mechanism to allow log rotation (a la zcashd)

If the log file is never trimmed, it can exhaust all available disk space. Zcashd has a mechanism to allow a tool like logrotate to do this. (Zcashd inherited this from Bitcoin Core.) It will be very easy to add this mechanism to lightwalletd, just a few lines of code.
The basic idea is the logrotate tool renames the existing log file and sends the process (lightwalletd) a SIGHUP signal, causing it to reopen the log file (and create it since it no longer exists with that name). The logrotate tool can then archive, compress, delete or whatever (according to how it's configured) the non-current log file.

This is a good idea, and probably a very small ticket, I'm going to move it way down the backlog but we will implement it if log storage becomes a problem.


BlackRock data format 3.0

Describe the bug
Read *.ns6 data from BlackRock causes a "Too many open files" error in __read_nsx_data_variant_b  function nearly immediately.
To Reproduce
Something  like this:
import neo

data_dir = "data/test_data/HubTests/"
path_gemini = data_dir + "233117-001.ns6"  # new data

reader = neo.io.BlackrockIO(filename=path_gemini)

(Data cannot be shared publicly.)
Expected behaviour
Data is read into memory
Environment:

OS: Windows 10
Python version: 3.7.8
Neo version: momentarily not available, most recent downloadable
NumPy version: 1.21.6

Additional context
New Blackrock device uses nsx-format version 3.0.
The neo code seems to have execute branches for version 3.0,
but states in comments that it handles nsx-formats up to version 2.3.
Prior devices (using nsx version 2.3) produced data that were read without problem,
so it seems that either blackrock is implementing the 3.0 format incorrectly, or neo
is handling it incorrectly.
There could be a marker, or signal, in the v3.0-data that is interpreted as
a "recording pause" triggering a segment split by neo code?
The arrival of nsx v3.0 is recent for us, with new equipment, but the version
may have been available for a long while.
Is this a known problem?

Further input, in case it helps: a stacktrace from execution as above:
---------------------------------------------------------------------------
OSError                                   Traceback (most recent call last)
Cell In[5], line 1
----> 1 reader = neo.io.BlackrockIO( filename="data/20230710-031124-001.ns6")

File ~/VirtualEnvs/neotest/lib/python3.11/site-packages/neo/io/blackrockio.py:17, in BlackrockIO.__init__(self, filename, **kargs)
     15 def __init__(self, filename, **kargs):
     16     BlackrockRawIO.__init__(self, filename=filename, **kargs)
---> 17     BaseFromRaw.__init__(self, filename)

File ~/VirtualEnvs/neotest/lib/python3.11/site-packages/neo/io/basefromrawio.py:74, in BaseFromRaw.__init__(self, *args, **kargs)
     72 def __init__(self, *args, **kargs):
     73     BaseIO.__init__(self, *args, **kargs)
---> 74     self.parse_header()

File ~/VirtualEnvs/neotest/lib/python3.11/site-packages/neo/rawio/baserawio.py:179, in BaseRawIO.parse_header(self)
    166 def parse_header(self):
    167     """
    168     This must parse the file header to get all stuff for fast use later on.
    169
   (...)
    177
    178     """
--> 179     self._parse_header()
    180     self._check_stream_signal_channel_characteristics()

File ~/VirtualEnvs/neotest/lib/python3.11/site-packages/neo/rawio/blackrockrawio.py:366, in BlackrockRawIO._parse_header(self)
    364 for nsx_nb in self.nsx_to_load:
    365     spec = self.__nsx_spec[nsx_nb]
--> 366     self.nsx_datas[nsx_nb] = self.__nsx_data_reader[spec](nsx_nb)
    368     sr = float(main_sampling_rate / self.__nsx_basic_header[nsx_nb]['period'])
    369     self.sig_sampling_rates[nsx_nb] = sr

File ~/VirtualEnvs/neotest/lib/python3.11/site-packages/neo/rawio/blackrockrawio.py:975, in BlackrockRawIO.__read_nsx_data_variant_b(self, nsx_nb)
    971     offset = \
    972         self.__nsx_data_header[nsx_nb][data_bl]['offset_to_data_block']
    974     # read data
--> 975     data[data_bl] = np.memmap(
    976         filename, dtype='int16', shape=shape, offset=offset, mode='r')
    978 return data

File ~/VirtualEnvs/neotest/lib/python3.11/site-packages/numpy/core/memmap.py:267, in memmap.__new__(subtype, filename, dtype, mode, offset, shape, order)
    265 bytes -= start
    266 array_offset = offset - start
--> 267 mm = mmap.mmap(fid.fileno(), bytes, access=acc, offset=start)
    269 self = ndarray.__new__(subtype, shape, dtype=descr, buffer=mm,
    270                        offset=array_offset, order=order)
    271 self._mmap = mm

OSError: [Errno 24] Too many open files

I have been in communication with @gedwald and I have been able to reproduce. I am investigating.

The problem is because the file comes from one of Blackrock's newer PTP-enabled systems. Previously, the presence of a header would indicate a new section due to a dropped sample, and all samples within a section would be assumed to be exactly 1/30_000 s apart. Now, on PTP-enabled systems only, each sample has a header containing its timestamp (nanoseconds). If the data reader thinks that the header indicates a new section, then it will create a new section for each sample.
This has been fixed in Blackrock's Python-Utilities (see change here: https://github.com/BlackrockNeurotech/Python-Utilities/pull/22). I am working on a fix for neo. While I do so, @gedwald and other readers may wish to use Blackrock's file importer. https://github.com/BlackrockNeurotech/Python-Utilities/blob/main/examples/extract_continuous_data.ipynb


fltk-fluid installation error

error: failed to run custom build command for fltk-fluid v0.1.9
Caused by:
process didn't exit successfully: C:\Users\admin\AppData\Local\Temp\cargo-install7rpRVi\release\build\fltk-fluid-ba221c03046df901\build-script-build (exit co
de: 101)
--- stdout
cargo:rerun-if-changed=build.rs
--- stderr
thread 'main' panicked at 'Git is needed to retrieve the fltk source files!: Error { kind: NotFound, message: "program not found" }', C:\Users\admin.cargo\reg
istry\src\index.crates.io-6f17d22bba15001f\fltk-fluid-0.1.9\build.rs:15:10
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
error: failed to compile fltk-fluid v0.1.9, intermediate artifacts can be found at C:\Users\admin\AppData\Local\Temp\cargo-install7rpRVi.
To reuse those artifacts with a future compilation, set the environment variable CARGO_TARGET_DIR to that path.

Rust version
rustc 1.72.1 (d5c2e9c34 2023-09-13)
binary: rustc
commit-hash: d5c2e9c342b358556da91d61ed4133f6f50fc0c3
commit-date: 2023-09-13
host: x86_64-pc-windows-msvc
release: 1.72.1
LLVM version: 16.0.5


163 jobs in db

Fixes #163
Changes
See closed PR #178 but without the local client
Checklist before merge
Developer's responsibilities

[ ] Assign one or two developers
[ ] Change code if reviewer(s) has/have requested it
[ ] Pull request build has passed
[ ] tested locally (in at least chrome & firefox if frontend)
[ ] updated the documentation
[ ] added tests where necessary

Todo: make sure that new session for client deletes the old one

closed because fixed in #185


Pin contrib again to very latest master to include servicebus fixes

Signed-off-by: Bernd Verst<EMAIL_ADDRESS>Description
Pins components contrib again to latest master to include servicebus fixes.

This commit is included in https://github.com/dapr/dapr/pull/4626 which also performs other fixes for tests

Don't merge just yet until you see another commit from me. Need one more thing in contrib :)


Documentation:  ADVFQ vignette

Please select a category the issue is focused on?
No response
Let us know where something needs a refresh or put your idea here!
needs updating when we have vfq QS data

Needs update to use VFQ test data


some errors with version 2.0 (and files are valid)

I have several PDFs that are generating some errors with this gem but are correctly handled by other programs.

First, a PDF giving an error that is neither MalformedPDFError or UnsupportedFeatureError:
20170212-1018-2831-314589-1.pdf

p = PDF::Reader.new(path)
p.pages.first.text
# TypeError: no implicit conversion of nil into String
# /Users/mathieu/.rvm/gems/ruby-2.2.5/gems/pdf-reader-2.0.0/lib/pdf/reader/buffer.rb:237:in `prepare_inline_token'
# /Users/mathieu/.rvm/gems/ruby-2.2.5/gems/pdf-reader-2.0.0/lib/pdf/reader/buffer.rb:177:in `block in prepare_tokens'
# /Users/mathieu/.rvm/gems/ruby-2.2.5/gems/pdf-reader-2.0.0/lib/pdf/reader/buffer.rb:172:in `times'
# /Users/mathieu/.rvm/gems/ruby-2.2.5/gems/pdf-reader-2.0.0/lib/pdf/reader/buffer.rb:172:in `prepare_tokens'
# /Users/mathieu/.rvm/gems/ruby-2.2.5/gems/pdf-reader-2.0.0/lib/pdf/reader/buffer.rb:118:in `token'
# /Users/mathieu/.rvm/gems/ruby-2.2.5/gems/pdf-reader-2.0.0/lib/pdf/reader/parser.rb:134:in `pdf_name'
# /Users/mathieu/.rvm/gems/ruby-2.2.5/gems/pdf-reader-2.0.0/lib/pdf/reader/parser.rb:37:in `block in <class:Parser>'
# /Users/mathieu/.rvm/gems/ruby-2.2.5/gems/pdf-reader-2.0.0/lib/pdf/reader/parser.rb:76:in `call'
# /Users/mathieu/.rvm/gems/ruby-2.2.5/gems/pdf-reader-2.0.0/lib/pdf/reader/parser.rb:76:in `parse_token'
# /Users/mathieu/.rvm/gems/ruby-2.2.5/gems/pdf-reader-2.0.0/lib/pdf/reader/page.rb:144:in `content_stream'
# /Users/mathieu/.rvm/gems/ruby-2.2.5/gems/pdf-reader-2.0.0/lib/pdf/reader/page.rb:111:in `walk'
# /Users/mathieu/.rvm/gems/ruby-2.2.5/gems/pdf-reader-2.0.0/lib/pdf/reader/page.rb:81:in `text'
# (pry):17:in `__pry__'

PDF::Reader::MalformedPDFError: xref stream not found when expected
20170323-1505-6657-314380-1.pdf

PDF::Reader::MalformedPDFError: PDF malformed, expected 5 but found 4 instead
20170322-1634-2447-323309-1.pdf

PDF::Reader::MalformedPDFError: PDF malformed, expected 5 but found 0 instead
reformed.pdf

Hope you can improve this gem with that

How did you generate these files?
I checked 20170322-1634-2447-323309-1.pdf - it has a broken xref table. Most PDF viewers silently fix that, though.

they are created by a scanner

Thanks for providing these. I've confirmed the first 3 files parse correctly in v2.9.0, however the final file (reformed.pdf) still errors.

however the final file (reformed.pdf) still errors

interesting. The xref table in this file has a slightly wrong byte offset for object 5, which is definitely "Malformed". Other readers must be able to compensate for this error - for example, I notice this message in the console when I open it in Firefox and yet it opens correctly:
Warning: XRef.parse - Invalid "Root" reference: "XRefEntryException: Bad (uncompressed) XRef entry: 5R".


Combine specs and test-generators

See Issue #836 for motivation and reasoning on basic structure.
specs
The specs directory, unchanged. Where the markdown specs live.
test_generators
Full documentation on generators can be found in /test_generators/README.md.
If there is anything magic to remember, it's that you run make gen_yaml_tests to run the generators, the makefile will handle virtual environments/dependencies etc.
py-tests
Py-tests are meant to validate basic consistency and sanity expectations of the spec itself.
Documentation can be found here: /pytests/README.md. Generally not used by client teams, it just helps to make sure a PR is valid.
scripts
This contains the (basic, no dependencies) code to generate the pyspec from the markdown version.
test_libs
This contains all the python packages that one may use during any kind of testing (pyspec, test-generator utilities, and more in the future)
pyspec
Most of the pyspec is rather static, it is just the eth2/phase0/spec.py file being dynamically generated from the markdown for now. This file is git-ignored. The other files are just kept in place, to keep the build system simple. You run make pyspec to build the pyspec from the markdown.
More documentation in /test_libs/pyspec/README.md
gen_helpers
This is just a module to require in your yaml generator to make use of the base generator etc. Documentation can be found in /test_generators/README.md.
.circleci
The Circle CI configuration. Similar to before, but updated to handle yaml test generation, and make use of the new makefile commands.

Waiting for a review from @djrtwo on the CI script. I updated it to make use of the new makefile commands, but I have no access to the settings panel to make any changes, or verify if it runs.
Since the code is heavy on python configuration, I would appreciate a review from @hwwhww and @ChihChengLiang, and anyone else from Trinity, to make sure it meets their standards.
Anyone that loves writing make files, please comment as well. I tried to improve on the old one by creating the necessary aliases, auto detection of generators, and make good use of dependencies. But there may be room for improvement still.
The base-test-generator was discussed and reviewed before in https://github.com/ethereum/eth2.0-test-generators/pull/31, but I'm still open for improvements on it.
Every review request aside, I can't wait to see the from eth2.phase0 import spec, and see tests directly being derived from the spec :tada:

Also; the old YAML generators still work, and should output the same format as earlier. The new base generator aims at standardizing the header format, as described in https://github.com/ethereum/eth2.0-test-generators/issues/29#issue-421837454 (See section: test-suites > format). Other parts of that proposal are not included, but I would want to see more standardization, and see PRs for pyspec+base-gen based test generators.
Note: The test-format proposal is a bit out-of-date, as we (suggestion by Danny) are looking to make "operations" (previously "transactions") tested individually, rather than testing the sub-transition of the block that processes multiple at a time.

Closing and reopening to trigger circleci

My strong wish about module naming conflicts sweat_smile: Py-EVM (Trinity) is using eth2 namespace and we may upload it to pypi; any chance that you can rename eth2 directory to pyspec?

@hwwhww Yes, was thinking about that. Just wanted to not duplicate folder names. pyspec/pyspec does seem worth it, given the collision here. Will change it in a bit.

Renamed eth2->pyspec, and fixed some minor things in the make file (build order for make all, clean pytest cache)

+1 on eth2spec

@djrtwo The BLS related stuff is not me, but from the code bridged over from the generators repo. I will look into fixing it.

Renamed to eth2spec. Also considered eth2pyspec, but then it's just too long. It being in python already makes it a "py"-spec. Eth2spec should work, and doesn't collide with the eth2 namespace.

Work in progress. Working on support for new test-format in the base generator now.

Just to be clear about the large change-set. Believe me, I dislike it as much as any of you do, but it is for the better. The tests and pyspec are good tools to build towards spec-conformance for clients, and the work was not picked up in smaller bits earlier on.
This PR is very close to being finished, the last todo points are:

new tracking issues for future plans:

CI triggers and output to new tests repository (Git LFS configured to facilitate a very large test collection, ideally as extensive as Eth 1.0)
operations generator extension (currently just pyspec based deposits, more to be introduced)
ssz generator update (old tests are far from complete SSZ)
block, slot/cache, epoch, multi-block tests
BLS test extension: verify, multi-verify

review, adjust, merge.

To be completely clear on not breaking anything with such a large change-set:
git diff dev --summary | grep specs only reports the documentation for the new test_formats, no actual specs have been touched, and all current tests & generators are fully functional (but upgraded, documented, and extended). :tada:

Looks like this PR is finally ready to be merged. :tada:
If anyone wants more time to review, this is the time. However, I've been extensively discussing testing with Danny IRL here in Sydney, and I'm sure we could fix any remaining typos or style improvements later.
Also, I'm happy to announce that ZRNT has a working test-suite consumption system, with compile-time configurations, and a passing deposit tests suite.
With this PR we have the strong tooling, standardization, documentation and POC to get more state-transition test generators set up. Can't wait to make ZRNT fully conformant, and get full-client implementers up to speed with testing their spec-conformance.
Next up:

#928 CI triggering, output to new LFS repo (handle larger test vectors size :rocket: )
#927 More test-suites, very similar to the POC deposits test generation. Now that the tooling is in-place, it should be straight-forward to get test vectors for the other block-operations.
Configurations need to be hosted somewhere for clients to use easily (or they would need to submodule the specs itself to access). Yet, we can't just git-submodule the configs directory, as it needs to be updated here. I propose we set up a CI job to just put them in an automatically maintained git repository, similar as with the yaml-test-generation.

Possibly next up, depending on status (need confirmation on target SSZ version, and PR status):

Get the new SSZ testing from the generators repo in here. https://github.com/ethereum/eth2.0-test-generators/pull/32 and possibly later https://github.com/ethereum/eth2.0-test-generators/pull/35
Get the new hash-tree-root testing from the generators repo in here https://github.com/ethereum/eth2.0-test-generators/pull/34/files

Future steps:

Other types of tests, like:

fork-choice
non-operation (transaction) block-processing sub-transitions
epoch-transition

handlers for each sub-transition, similar to block-processing

full state-transition with multiple blocks

Future ideas:

clients report test-coverage from CI to some shared service, and we gamify things a little bit (dashboard? charts? :thinking: )

Release plan:

This PR for v0.6
Some more operations being tested in v0.6
A stable v0.6; keep adding more tests for clients to test their work on this stable version. (non-spec-breaking)
See #928 for thoughts about deprecation tests and generators repo, and the new outputs becoming available from a Git LFS repo.


[SMALLFIX] Use the @Nullable annotation for all methods which may ret…

…urn null in RPCMessage.java

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16901/
Test PASSed.


Create a delete and reroll command for OT names

We decided in a staff meeting today that there will be a new command that, for a given off-topic channel, picks a different name from the available pool and deletes the current name from the pool (rather than marking it used). This would be a moderator+ command that lives in the off-topic cog.
Other details of the spec have not been decided on, including:

The name of the command. reroll is a contender, though one might not infer that the command both rerolls and deletes.
The argument that is passed to it. Should it be an integer in {0, 1, 2}, or should it be a channel ID? Should it be optional and in that case act upon the channel in which it in invoked?

I may be able to implement this myself, as I'm pretty much done with school.

cc @RohanJnr

@RohanJnr would like to implement this. I chatted with him earlier, and for now the specification is that !otn reroll n for n in {0, 1, 2}, though keep in mind that it will both reroll the name for that channel and delete the then-current name. The n argument will be optional when evoked in an off-topic channel.
Whoever is knowledgeable about rate limits as they apply to channel renames, I'd be interested to know if this command needs a cooldown.

We will need a cool down, we can edit the channel 2 times before we hit a 10min rate limit cooldown.
The command can have a cooldown of 5min to avoid the rate limit.

Do we want the cooldown for the entire command or do we want the cooldown per channel?

@RohanJnr whichever count cooldown pertains to.

Plan 1  to handle rate limits.
Store the number of times an off-topic channel has been edited as times_edited and also the datetime instance for the last edit
data structure:
{
 channel_id: {
    "times_edited": int,
    "last_edit": datetime
 }
}

or the above can be done using a Class ( I have not decided which one I want to use yet).
Conditions before editing a channel via the reroll command or the daily channel name updater task,

if times_edited is 2 and 10minutes have not passed since the last_edit, then:

Reschedule the channel edit if it's the daily channel name updater task.
Tell the user to try the command later if it's the reroll command or schedule the reroll command.

if times_edited is 2 and 10minutes have passed since the last_edit, then:

Go ahead and edit the channel.
Reset times_edited to 1 and store last_edit.

if times_edited is 1, then we just edit the channel, update times_edited to 2, and last_edit to the current time.

Plan 2
Just to set a 10minute cooldown on the reroll command.
The former allows you to edit multiple channels 2 times within 10min(mostly) and then not allowing you to edit the channels for the next 10min (to reset the rate limit cooldown) whereas the latter allows you to edit only 1 channel every 10min though easier to implement.

If you go with plan one, can you store that information in an async redis cache? How will you handle the daily non-deleting rerolls (since those also count towards the rate limit)?
If you're worried that plan one would slow down development too much, you can go with plan 2 for now and we can plan to migrate to plan 1 later. The underlying logic for the actual deletion-reroll should be unaffected.

How will you handle the daily non-deleting rerolls

I did mention it as daily channel name updater task.

hello @swfarnsworth , can you update the issue description to match the updated implementation?
Updated implementation
Instead of deleting the off topic name after re-rolling, we are gonna mark that name as inactive in the backend (database).
These inactive names will not be considered for future channel names. We are storing these to avoid similar names to be added via the add command as the command checks existence of similar names.

If we reroll a channel's name, do we want to reschedule the daily OT update tasks to update the channel name 24h from the reroll, or does the channel name update at the standard time 00:00 UTC?

@RohanJnr I've added this to the specification:

...and (updated 20 August) marks the removed name as "inactive" in the database. When attempting to add a name to the pool that exists in the pool as inactive, the command should fail with the bot explaining as much. One should be able to circumvent this with forceadd.

@RohanJnr what's the status on this?

The site pr is almost ready, current being reviewed


Library not loaded: @rpath/libcublas.8.0.dylib when running TF GPU on MacOS

System information

System: Mac OS 10.13.4:

Xcode:9.2 .  Apple LLVM version 9.0.0 (clang-9<IP_ADDRESS>):

Cuda::

nvcc: NVIDIA (R) Cuda compiler driver:

Copyright (c) 2005-2018 NVIDIA Corporation:

Built on Sun_Mar_18_21:08:25_CDT_2018:

Cuda compilation tools, release 9.2, V9.2.64:

cudnn:7.1.4:

gcc g++ : 4.2.1:

Question::
When i use anaconda install tensorflow-gpu,the terminal say i was successful! Such as:
Installing collected packages: numpy, six, werkzeug, protobuf, tensorflow-gpu
Successfully installed numpy-1.14.3 protobuf-3.5.2.post1 six-1.11.0 tensorflow-gpu-1.1.0 werkzeug-0.14.1

But when is write "import tensorflow as tf",some erroes is show.

(tensorflowGPU) jhmdeMacBook-Air:Sources jhm$ python
Python 3.6.5 |Anaconda, Inc.| (default, Apr 26 2018, 08:42:37)
[GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

import tensorflow as tf
Traceback (most recent call last):
File "/Users/jhm/anaconda3/envs/tensorflowGPU/lib/python3.6/site-packages/tensorflow/python/pywrap_tensorflow.py", line 41, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "/Users/jhm/anaconda3/envs/tensorflowGPU/lib/python3.6/site-packages/tensorflow/python/pywrap_tensorflow_internal.py", line 28, in
_pywrap_tensorflow_internal = swig_import_helper()
File "/Users/jhm/anaconda3/envs/tensorflowGPU/lib/python3.6/site-packages/tensorflow/python/pywrap_tensorflow_internal.py", line 24, in swig_import_helper
_mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
File "/Users/jhm/anaconda3/envs/tensorflowGPU/lib/python3.6/imp.py", line 243, in load_module
return load_dynamic(name, filename, file)
File "/Users/jhm/anaconda3/envs/tensorflowGPU/lib/python3.6/imp.py", line 343, in load_dynamic
return _load(spec)
ImportError: dlopen(/Users/jhm/anaconda3/envs/tensorflowGPU/lib/python3.6/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so, 10): Library not loaded: @rpath/libcublas.8.0.dylib
Referenced from: /Users/jhm/anaconda3/envs/tensorflowGPU/lib/python3.6/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
Reason: image not found

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "", line 1, in
File "/Users/jhm/anaconda3/envs/tensorflowGPU/lib/python3.6/site-packages/tensorflow/init.py", line 24, in
from tensorflow.python import *
File "/Users/jhm/anaconda3/envs/tensorflowGPU/lib/python3.6/site-packages/tensorflow/python/init.py", line 51, in
from tensorflow.python import pywrap_tensorflow
File "/Users/jhm/anaconda3/envs/tensorflowGPU/lib/python3.6/site-packages/tensorflow/python/pywrap_tensorflow.py", line 52, in
raise ImportError(msg)
ImportError: Traceback (most recent call last):
File "/Users/jhm/anaconda3/envs/tensorflowGPU/lib/python3.6/site-packages/tensorflow/python/pywrap_tensorflow.py", line 41, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "/Users/jhm/anaconda3/envs/tensorflowGPU/lib/python3.6/site-packages/tensorflow/python/pywrap_tensorflow_internal.py", line 28, in
_pywrap_tensorflow_internal = swig_import_helper()
File "/Users/jhm/anaconda3/envs/tensorflowGPU/lib/python3.6/site-packages/tensorflow/python/pywrap_tensorflow_internal.py", line 24, in swig_import_helper
_mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
File "/Users/jhm/anaconda3/envs/tensorflowGPU/lib/python3.6/imp.py", line 243, in load_module
return load_dynamic(name, filename, file)
File "/Users/jhm/anaconda3/envs/tensorflowGPU/lib/python3.6/imp.py", line 343, in load_dynamic
return _load(spec)
ImportError: dlopen(/Users/jhm/anaconda3/envs/tensorflowGPU/lib/python3.6/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so, 10): Library not loaded: @rpath/libcublas.8.0.dylib
Referenced from: /Users/jhm/anaconda3/envs/tensorflowGPU/lib/python3.6/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
Reason: image not found

Failed to load the native TensorFlow runtime.
See https://www.tensorflow.org/install/install_sources#common_installation_problems
for some common reasons and solutions.  Include the entire stack trace
above this error message when asking for help.
BugLog/tensorflowGPU-01.log
I don't konw what to do!

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

It has been 15 days with no activity and the awaiting response label was assigned. Is this still an issue?

We are not supporting GPUs on macos anymore, because apple and nvidia do not provide official support for each other. I will mark this community support.
You may have better luck trying to get support for this from stackoverflow.

So the cause of this issue is the SIP in Mac OS, basically when python launches, due to SIP, the subprocess of Tensorflow doesn't get passed the environment variable for the library locations, so _pywrap_tensorflow_internal.so as referenced in the error message can't find the library locations.
The solution is to link _pywrap_tensorflow_internal.so so rather than relying on environment variables, it checks the file path directly (in this case looking for /usr/local/cuda/lib/).
The workaround, so you don't have to rebuild everything is to use the command line tool "install_name_tool" to update the object file linking. To do this you just run this command, using the appropriate path for where your tensorflow wheel installed, you'll need to do this for 2 object files actually:
install_name_tool -change @rpath/libcusolver.9.2.dylib /usr/local/cuda/lib/libcusolver.9.2.dylib -change @rpath/libcudart.9.2.dylib /usr/local/cuda/lib/libcudart.9.2.dylib   -change @rpath/libcublas.9.2.dylib /usr/local/cuda/lib/libcublas.9.2.dylib CHANGETHISPATH/python3.5/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
install_name_tool -change @rpath/libcudart.9.2.dylib /usr/local/cuda/lib/libcudart.9.2.dylib -change @rpath/libcublas.9.2.dylib /usr/local/cuda/lib/libcublas.9.2.dylib -change @rpath/libcudnn.7.dylib /usr/local/cuda/lib/libcudnn.7.dylib -change @rpath/libcufft.9.2.dylib /usr/local/cuda/lib/libcufft.9.2.dylib -change @rpath/libcurand.9.2.dylib /usr/local/cuda/lib/libcurand.9.2.dylib -change @rpath/libcudart.9.2.dylib /usr/local/cuda/lib/libcudart.9.2.dylib  CHANGETHISPATH/python3.5/site-packages/tensorflow/libtensorflow_framework.so
The permanent solution seems to be to add a flag to the compile per https://stackoverflow.com/questions/39927235/alternative-for-the-dyld-library-path-trick-since-mac-os-10-11-el-capitan-with-s but I don't know enough about the tensorflow build to say where this needs to go

I have encounter similar problem in my hackintosh, I am not sure if it is related to SIP,  while I am use 0x67 in clover config.
the simplest way is :
export DYLD_LIBRARY_PATH="/usr/local/cuda/lib":$DYLD_LIBRARY_PATH
then everything is fine.

@JiangHoumin ,
Could you take a look at this comment with the similar error and let us know if the issue still persists. Thank you!


Suggest a friendly name replacement macro

In order to have a "friendly" name for a board or product when @boardname@ is used for strict branding, I suggest something like<EMAIL_ADDRESS>This is declared in appTheme as boardCommonName.

We already have AppTarget.nickname, just FYI


Guidance for using an argument value in bash script substitution

I'm having a little trouble escaping curly braces properly - it's a bit of an esoteric example (and I should probably just make it a script that I call from just directly), but for the sake of demonstration purposes, I would like to figure this out.
I have a recipe that takes a single argument, type, and I want to check to see if the argument passed in is in a bash array of strings and do something different depending on what is given. I think it would help to first show what the bash script would look like (that works fine):
#!/usr/bin/env bash
echo 'Checking to make sure release request is valid...'
valid_types=("patch" "minor" "major")
[[ ${valid_types[*]} =~ ${1:?} ]] &&
    echo "Release type accepted!" || echo "no!"

Running the script works as expected:
$ ./script.sh patch
Checking to make sure release request is valid...
Release type accepted!

$ ./script.sh lol
Checking to make sure release request is valid...
no!

I want to put this into a just recipe. So I'm trying the following, and I can't quite seem to get it to work:
# Cut a release! Valid arguments: 'patch'/'minor'/'major'
release type:
    #!/usr/bin/env bash
    echo 'Checking to make sure release request is valid...'
    valid_types=("patch" "minor" "major")
    [[ ${valid_types[*]} =~ ${{{{{type}}:?} ]] &&
        echo "Release type accepted!" || echo "no!"

Running the recipe gives me an error:
$ just release blah
Checking to make sure release request is valid...
/var/folders/6w/3nlpd0_d6wv82xwsbg0jxpww0000gp/T/just0ftGRC/release: line 13: ${{{type}}:?}: bad substitution
error: Recipe `release` failed with exit code 1

I think I'm escaping the initial { properly (by putting two {{ before it), but it doesn't seem like that's working quite right. The README gives guidance on how to escape two curly braces, but it doesn't give guidance for doing it for just one. Any guidance someone could provide me here?

Oh, trying to stuff just references within Bash variables with a post-colon modifier?! You may not want to do that. Or at least my brain doesn't wan't to figure that out right now. There are a few options to consider before trying to escape the Bash variable name from the just variable recipe argument. Yes, it could work but "there lies madness" and I still need breakfast.  👼
Position Arguments Setting
# Allows positional arguments to be accessed "normally" and supports $@ access as well
set positional-arguments := true

# Cut a release! Valid arguments: 'patch'/'minor'/'major'
release type:
    #!/usr/bin/env bash
    echo 'Checking to make sure release request is valid...'
    valid_types=("patch" "minor" "major")
    [[ ${valid_types[*]} =~ ${1:?} ]] &&
        echo "Release type accepted!" || echo "no!"

-or-
Pass to Shell Variable
# Cut a release! Valid arguments: 'patch'/'minor'/'major'
release type:
    #!/usr/bin/env bash
    echo 'Checking to make sure release request is valid...'
    input_type={{type}}
    valid_types=("patch" "minor" "major")
    [[ ${valid_types[*]} =~ ${input_type:?} ]] &&
        echo "Release type accepted!" || echo "no!"

There may be a few more options I'm not thinking of currently. But these are how I generally handle such situations. It's easy to read and grok even after the code has been entirely forgotten a week or two later.

Jeez, didn't even thing about just using it like a normal positional argument to a script. That makes tons of sense. Thanks - I'll close this out in that case, I think it's a perfectly valid alternative to what craziness I was trying to do!


Space vs hyphen in name in FVTT package directory

I noticed the name of the module in the FVTT package directory uses a hyphen (i.e., Active-Auras), and all other references use a space (Active Auras). When searching from the Foundry VTT module installation UI, typing "Active Auras" doesn't find the module. It might be better to change the title in the FVTT package directory listing to use a space instead of a hyphen to make finding it easier.

I guess the same would apply to the title in the manifest file.


Speed up docker build

This speeds the docker build up from ~1:30 hours to slightly over 10 minutes and also enables it to run with every CI run (that could also be left out if 10 minutes is still to slow)
This PR contains three commits:

Enables the workflow to run whenever the normal CI workflow runs. It also makes sure the built image is only uploaded on release.
Uses xx (a collection of tools for cross-compiling in docker) to enable cross-compiling in the Dockerfile. This alone brings the compile time down to around 16 minutes.
Reworks the workflow file to use a build matrix to build for different architectures and merge the images into a single manifest, bringing the compile time down to slightly over 10 minute

It's in my opinion still too slow for inclusion in the merge group (merge group CI used to run in 2-3mins which was fantastic and GitHub's slow Windows runners bringing it up to 4-6mins is already very noticeable in my day-to-day work).
The speed-up is still great though!
Since I don't know much about Docker, I'll leave review to @reknih.

There's a project called cargo-chef. Have you tried that?

Thanks!