SearchAbout issue / support

Hi !
When I try to evaluate SearchAbout nat, the plugin stop responding (it display a couple entries and that's it). Is there a way to use SearchAbout with this plugin ?
Note: coq-au-vim has the same issue :p

Hi, could you tell me what version of Coq you're using? SearchAbout works fine for me on all the versions I've tried.

I'm using Coq from opam:
coqtop -v
The Coq Proof Assistant, version 8.8.1 (October 2018)
compiled on Oct 9 2018 17:40:59 with OCaml 4.02.3

Using SearchAbout nat in a clean file works, but using it after some Require seems to fail, here is an example screen:

Ok, it looks like this is a problem for Coq >=8.6 and Python 2. I'll look into it.

It might also have been my fault: I had still traces of coq-au-vim around. It seems to be better with these traces deleted. If you have some benchmark you would like me to test, feel free to reach out.
Thanks for your work !

I pushed a possible fix to branch slow-search-fix. When you have a chance could you try pulling it and see if it helps?

It seems ok, and even a bit faster than yesterday ! Thanks a lot. I only tested my problematic use case, but I'll try to test it more by the end of the week.

Fixed by 762fdaccc3f569f72a53624682d0f197468f98fc.


[SourceControl] Address SR-5704

This pull request adds a new function, isUpToDate(), addressing SR-5704.
If dependencies are up-to-date, handleWillUpdate(_:), fetch() and handleDidUpdate(_:) are skipped entirely.

So basically, the bug is about informing user that there was no update that can be applied to his dependencies. We will always need to do a git fetch anyway to fetch the versions. What we need to do is, emit a message that nothing change if none of packages were changed. This can be easily detected using the package state change enum in Workspace. You can add a delegate which is fired when each element of packageStateChanges is .unchanged (see updateCheckouts method in Workspace.swift). Does this make sense?

Changes have been implemented. Please review.


settings: Use default database_user value when looking up.

Failure to pull the default "zulip" value here can lead to
accidentally applying a postgres_password value which is unnecessary
and may never work.
For consistency, always skip password auth attempts for the "zulip"
user on localhost, even if the password is set.  This mirrors the
behavior of process_fts_updates.
Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Merged, thanks @alexmv!

Backported to 5.x as fa68acd669972f4516a5bc8819efe41ba77fd914


Question: How to implement browser depedencies.

According to https://playwright.dev/docs/test-global-setup-teardown (Option 1) you can create 'depedencies' for each browser.
For this to work you should set the testDir of playwright.config.ts, but testDir is defined by defineBddConfig in this situation and cannot define another one.
Any other way to make this work ? Global setup does not fit in my situation, I want to use Playwright depedencies ideally.
Thank you.

This should be possible. Could you share the playwright.config.ts that does not work?


Code climate setup

Closes #58

@jamessimone if you have some time, I added you as a reviewer to this. It's primarily to get the new .codeclimate.yml file (and a few other config files) added to the project, but I also made some code changes in this PR that Code Climate has suggested.
I think this will be the last PR for v1.0! I'll leave the rest of the Code Climate suggestions for future releases (I may need to tweak the rules later anyway, so I don't want to try to implement all of the suggested changes right now).

@jamessimone thanks for reviewing! Yeah, I think those classes both look cleaner now, so Code Climate (PMD) seems to be helpful so far 👍


BOSH update (260->261) failed with new stemcell (3312->3363)

Hi.
Old bosh.yml:
releases:
- name: bosh
  url: https://bosh.io/d/github.com/cloudfoundry/bosh?v=260
  sha1: f8f086974d9769263078fb6cb7927655744dacbc
- name: bosh-openstack-cpi
  url: https://bosh.io/d/github.com/cloudfoundry-incubator/bosh-openstack-cpi-release?v=27
  sha1: 85e6244978f775c888bbd303b874a2c158eb43c4

resource_pools:
- name: vms
  network: private
  stemcell:
    url: https://bosh.io/d/stemcells/bosh-openstack-kvm-ubuntu-trusty-go_agent?v=3312
    sha1: 36dd5035c3868aa9f2da32291e6338636b63c345

New bosh.yml:
releases:
- name: bosh
  url: https://bosh.io/d/github.com/cloudfoundry/bosh?v=261
  sha1: b7855edc33ece92e9e8e1b5d03c5e2c897d426d8
- name: bosh-openstack-cpi
  url: https://bosh.io/d/github.com/cloudfoundry-incubator/bosh-openstack-cpi-release?v=30
  sha1: 2fff8e1c241a91267ddd099a553c1339d2709821

resource_pools:
- name: vms
  network: private
  stemcell:
    url: https://bosh.io/d/stemcells/bosh-openstack-kvm-ubuntu-trusty-go_agent?v=3363
    sha1: 9db642b70eb93bb4092f967d8c1716be67af1a77

Error:
Started deploying
  Waiting for the agent on VM 'fd0e4139-f54f-467e-b91c-bd560d6ce057'... Finished (00:00:00)
  Stopping jobs on instance 'unknown/0'... Finished (00:00:01)
  Unmounting disk 'c21c7672-84b4-4fc5-8b4b-318cf2cb1557'... Finished (00:00:03)
  Deleting VM 'fd0e4139-f54f-467e-b91c-bd560d6ce057'... Finished (00:00:14)
  Creating VM for instance 'bosh/0' from stemcell '652416c5-b1f2-4449-835e-193e3d63831a'... Finished (00:01:09)
  Waiting for the agent on VM 'd9289248-2a87-425c-bd50-9d71c11fc965' to be ready... Finished (00:00:16)
  Attaching disk 'c21c7672-84b4-4fc5-8b4b-318cf2cb1557' to VM 'd9289248-2a87-425c-bd50-9d71c11fc965'... Failed (00:00:34)
Failed deploying (00:02:27)

Stopping registry... Finished (00:00:00)
Cleaning up rendered CPI jobs... Finished (00:00:00)

Command 'deploy' failed:
  Deploying:
    Creating instance 'bosh/0':
      Updating instance disks:
        Updating disks:
          Deploying disk:
            Mounting disk:
              Sending 'get_task' to the agent:
                Agent responded with error: Action Failed get_task: Task 46cb2187-932b-487d-4b42-aeeb4f47dabf result: Persistent disk with volume id 'c21c7672-84b4-4f
c5-8b4b-318cf2cb1557' could not be found

Actually, in openstack console and inside of VM I see that disk was attached, but was not mounted.
Unfortunately, the root password is not working in this half-upgraded VM, so I can't tell you more.
After the rollback to the previous version of the stemcell - update has been successfully completed.

This feels related to https://github.com/cloudfoundry/bosh-cli/issues/110.
Can you give bosh-init 0.0.100+ or bosh-cli v2 2.0.1+ with new stemcell a
try?
cc @voelzmo
On Thu, Feb 16, 2017 at 12:53 AM, Anton Soroko<EMAIL_ADDRESS>wrote:

Hi.
Old bosh.yml:
releases:

name: bosh
url: https://bosh.io/d/github.com/cloudfoundry/bosh?v=260
sha1: f8f086974d9769263078fb6cb7927655744dacbc
name: bosh-openstack-cpi
url: https://bosh.io/d/github.com/cloudfoundry-incubator/bosh-openstack-cpi-release?v=27
sha1: 85e6244978f775c888bbd303b874a2c158eb43c4

resource_pools:

name: vms
network: private
stemcell:
url: https://bosh.io/d/stemcells/bosh-openstack-kvm-ubuntu-trusty-go_agent?v=3312
sha1: 36dd5035c3868aa9f2da32291e6338636b63c345

New bosh.yml:
releases:

name: bosh
url: https://bosh.io/d/github.com/cloudfoundry/bosh?v=261
sha1: b7855edc33ece92e9e8e1b5d03c5e2c897d426d8
name: bosh-openstack-cpi
url: https://bosh.io/d/github.com/cloudfoundry-incubator/bosh-openstack-cpi-release?v=30
sha1: 2fff8e1c241a91267ddd099a553c1339d2709821

resource_pools:

name: vms
network: private
stemcell:
url: https://bosh.io/d/stemcells/bosh-openstack-kvm-ubuntu-trusty-go_agent?v=3363
sha1: 9db642b70eb93bb4092f967d8c1716be67af1a77

Error:
Started deploying
Waiting for the agent on VM 'fd0e4139-f54f-467e-b91c-bd560d6ce057'... Finished (00:00:00)
Stopping jobs on instance 'unknown/0'... Finished (00:00:01)
Unmounting disk 'c21c7672-84b4-4fc5-8b4b-318cf2cb1557'... Finished (00:00:03)
Deleting VM 'fd0e4139-f54f-467e-b91c-bd560d6ce057'... Finished (00:00:14)
Creating VM for instance 'bosh/0' from stemcell '652416c5-b1f2-4449-835e-193e3d63831a'... Finished (00:01:09)
Waiting for the agent on VM 'd9289248-2a87-425c-bd50-9d71c11fc965' to be ready... Finished (00:00:16)
Attaching disk 'c21c7672-84b4-4fc5-8b4b-318cf2cb1557' to VM 'd9289248-2a87-425c-bd50-9d71c11fc965'... Failed (00:00:34)
Failed deploying (00:02:27)
Stopping registry... Finished (00:00:00)
Cleaning up rendered CPI jobs... Finished (00:00:00)
Command 'deploy' failed:
Deploying:
Creating instance 'bosh/0':
Updating instance disks:
Updating disks:
Deploying disk:
Mounting disk:
Sending 'get_task' to the agent:
Agent responded with error: Action Failed get_task: Task 46cb2187-932b-487d-4b42-aeeb4f47dabf result: Persistent disk with volume id 'c21c7672-84b4-4f
c5-8b4b-318cf2cb1557' could not be found
Actually, in openstack console and inside of VM I see that disk was
attached, but was not mounted.
Unfortunately, the root password is not working in this half-upgraded VM,
so I can't tell you more.
After the rollback to the previous version of the stemcell - update has
been successfully completed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cloudfoundry/bosh/issues/1589, or mute the thread
https://github.com/notifications/unsubscribe-auth/AALV91OvHDDMenS3voy5ZyFKWFbmbUlVks5rdA6HgaJpZM4MCvKK
.

@cppforlife
Hi.
I forgot to mention that I used bosh-init version 0.0.99-1c660f1-2016-11-11T23:51:52Z
With bosh-init version 0.0.100-a5c1605-2017-02-14T23:33:52Z update has been successfully completed.
Thanks for the tip.

@antonsoroko I dont think we can do much in the stemcell as it seems to be a problem that was resolved in bosh-init 100+. Thanks for confirmation that bosh-init 100 resolved the problem.

I tried to deploy my proto bosh on bosh-openstack-kvm-ubuntu-trusty-go_agent/3363 stemcell and facing same issue. I switch back to bosh-openstack-kvm-ubuntu-trusty-go_agent/3312.15 and it is running fine for me.It seems bosh-openstack-kvm-ubuntu-trusty-go_agent/3363 having some bugs.

@cfmagnum
Hi. Have you tried to update your bosh-init/bosh-cli?

@antonsoroko
My Bosh CLI version is BOSH 1.3262.4.0
And bosh-init version is 0.0.81-775439c-2015-12-09T00:36:03Z

@cfmagnum
Hi. Try to upgrate to any of these versions:
https://github.com/cloudfoundry/bosh/issues/1589#issuecomment-280273526
I solved problem by upgrading my bosh-init version to 0.0.100+:
https://github.com/cloudfoundry/bosh/issues/1589#issuecomment-280348697

Hey thanks @antonsoroko
I have updated my bosh cli to 1.3262.26.0 and bosh-init to 0.0.101 .
And it's working fine. I  am using bosh-openstack-kvm-ubuntu-trusty-go_agent/3363.12 stemcell.

I had the same issue trying to update stemcell with an old version of bosh-cli.
@cppforlife do you think it is possible to create a way to have correspondence between bosh-cli version and the version of stemcell? It worked well with ruby bosh cli.

@allomov, bosh-cli and stemcell shouldn't be correlated - they're developed independently and CLI should general not care about which stemcell or director version they're using. In the director's case, the CLI may try hitting unsupported endpoints for newer features, but it should still function.
For this particular issue, I think there were two, independent undesired behaviors/bugs. First the stemcell started dealing with connections slightly differently (that was fixed in newer stemcells). But then that behavior change demonstrated another, otherwise hidden bug in the init/CLI (which then had to be fixed and backported).
In this case, I think the correct solution is to still upgrade the bosh-init/CLI, regardless of which stemcell version you might be using.

@dpb587-pivotal thank you for your comment. Using the latest version of CLI might be a good solution here.
From my understanding there is a weak dependence between bosh-agent and bosh-cli, because bosh-cli performs requests to bosh-agent through http mbus. Changing interface of http mbus communication is going to break possibility to deploy/update bosh using bosh-cli.

That's true. But, no need to worry about that API breaking... it won't be changing [relatively] ever. If we do, we'd probably do it in a backwards/fallback compatible way within our golang libraries.


Expose queryThreadIoLatency counter in connector

Expose query thread IO Latency counter in connector, which would help analyze latencies observed by Velox in Gluten.

@akashsha1 There are CI failures. Would you take a look?

It would be nice to document all these runtime stats and make sure their names are consistent and intuitive.

Where would you suggest adding such a documentation?
There is documentation about them present in:
https://github.com/facebookincubator/velox/blob/main/velox/dwio/common/IoStatistics.h

Where would you suggest adding such a documentation?

Maybe somewhere here: https://facebookincubator.github.io/velox/develop/debugging.html

@akashsha1
you may need to update the tests with the new metric here:
https://github.com/facebookincubator/velox/blob/main/velox/exec/tests/PrintPlanWithStatsTest.cpp#L174
-yuan

@akashsha1 you may need to update the tests with the new metric here: https://github.com/facebookincubator/velox/blob/main/velox/exec/tests/PrintPlanWithStatsTest.cpp#L174
-yuan

thanks for pointing this out. Fixing the test worked.


[FEATURE] Project manifest schema

Make "Even Better TOML" a dependecy of the VSCode extension and provide a schema for witcherscript.toml.

[x] Change the tomlValidation key in package.json to point to a specific version or master branch before next version is shipped

[ ] Change the tomlValidation key in package.json to point to a specific version or master branch before next version is shipped

[ ] Change the tomlValidation key in package.json to point to a specific version or master branch before next version is shipped

Even Better TOML's status bar at the bottom left displays schema's URL instead of a short title.

For now I have no idea how to fix this while not uploading the schema to https://www.schemastore.org catalog.

Released with v0.3.0


insurgent-lab

Hi Pierre,
I just wanted to send you a note as I believe there's a mistake in your semantic-release-hex-demo project on Github that's notifying me (insurgent) instead of the user "Insurgent-lab".
Take care,
John

Hi :wave:
This is because we use the package @insurgent/conventional-changelog-preset, where @insurgent is the name of the NPM org.
Due to a bug in that package, the org name inside the backtick quoted package's name from this commit got unquoted in the generated CHANGELOG, effectively tagging you because of a name collision.
Sorry for the unsolicited notification :sweat_smile:
All the best,
Pierre


Add security

Right now the API is unauthenticated. An example of how to do API security for a RESTful API would be sweet!

Also to security stuff - you shoudn't send everything to the user... only that what is needed. I mean - good idea would be to make 2 models for Input (Requests) and Output (Responses) to prevent data leakage. :D I'm trying to master it right now. :)

@TheAifam5 I agree, having separate classes to model what's stored in the DB, what's returned to the user, and what's accepted in a POST reduces the chances that you'll accidentally leak something. This project already uses that pattern. 🙂


InitManager: TargetImpl::ready() behavior change

Signed-off-by: Yuchen Dai<EMAIL_ADDRESS>Description:
TargetImpl::ready() called before Init::Manager switch the target state to ready.
This behavior change allows asynchronous TargetImpl::ready() invocation.
This PR remains the behavior that destroyed TargetImpl is considered as ready.
Risk Level: Mid
Testing: Existing tests and added unit test for InitManager
Docs Changes: Inline comment
Release Notes:
This is a developer behavior change but not a user behavior change. Not sure if release notes is needed.
This behavior is discussed in #6904

@mergeconflict would you be up for doing first pass, and tagging Harvey/Matt when you've LGTMd?

@silentdai can we step back for a sec?
I'm a little concerned that we are not solving the right problem here. Can you summarize what problem you are trying to solve? My understanding is that you want a resource to be ready() before initialize() is called. Is that right? For my understanding, why can you not just keep track that it is ready and then just immediately call ready() in the context of initialize()?

@mattklein123 Thank you for the comment!

My understanding is that you want a resource to be ready() before initialize() is called. Is that right?

Yes!

For my understanding, why can you not just keep track that it is ready and then just immediately call ready() in the context of initialize()?

Yes. I can. I did it in #7440
EagerTarget beats my code in two ways

coherency: EagerTarget  vs a ready_flag + a TargetImpl. It burns brain to understand the flag should be touched by Target. I don't want invent another GUARDED_BY :)

ownership:
There are 4 objs: Target, InitializeFn  as arg of TargetImpl ctor, ready_flag, another initialize function which could set the ready_flag. Which owns/refers which?
EagerTarget is simple: InitializeFn owns EagerTargetImpl. InitializeFn doesn't care the timing of target is added to Init::Manager. If target is gone when it should be added to Manager, it is also fine.

Yes. I can. I did it in #7440

My personal opinion is that init manager is already complicated enough as it is, and unless we really need to make changes to support a new use case, we probably should not. IMO it's not that complicated to just call ready() in the context of initialize(). I'm pretty sure we already did that in other places, e.g., for static clusters.
However I will defer to @mergeconflict as he has been thinking about this area a lot more closely.

Yes. I can. I did it in #7440

My personal opinion is that init manager is already complicated enough as it is, and unless we really need to make changes to support a new use case, we probably should not. IMO it's not that complicated to just call ready() in the context of initialize(). I'm pretty sure we already did that in other places, e.g., for static clusters.
However I will defer to @mergeconflict as he has been thinking about this area a lot more closely.

Yeah, I honestly agree with @mattklein123. If it's possible to support your use case without changes/additions to the init code, I'd prefer that, since the init manager is already tricky enough without having to reason about multiple varieties of target with different polymorphic behaviors.

OK. I will adopt the idea that check ready flag in initialize function.
Sorry my initial intention is to extract the logic from xDS to Init namespace since this is not a configuration business logic.
By polymorphic behaviors I also find a RAII Target which invoke ready() is also useful but I guess you don't like either.
I appreciate your comments and feedback!


Deprecated farady dependencies

This library depends on pre-1.0 faraday and faraday middleware libraries that are deprecated. This is causing dependency conflicts with other libraries that are depending on newer versions of faraday.

Thanks for posting this.
Update is in progress on master branch.

Updated in v.2.3.0:

https://rubygems.org/gems/ringcentral_sdk/versions/2.3.0
https://github.com/grokify/ringcentral-sdk-ruby/releases/tag/v2.2.3


New term template

I would suggest not using "Asplenia", it is a phenotype rather than a disease, I think. We could use something that is clearly a disease, such as Noonan syndrome

Yep, we'll completely overhaul these see https://github.com/INCATools/ontology-development-kit/issues/162 @nicolevasilevsky maybe you can work with Nomi on this?

sure, I can work on this.


doom-themes-treemacs-config breaks treemacs resizing

When I run doom-themes-treemacs-config in my init.el, resizing of the Treemacs buffer (via M-x treemacs-toggle-fixed-width) does not work any more, no matter where I click.
The culprit appears to be this:
(defun doom-themes-hide-modeline ()
  (setq mode-line-format nil))

in doom-themes-ext-treemacs.el. If I remove the line adding that function as a hook, it works.

It doesn't make much sense that unsetting the mode-line would tamper with treemacs' ability to resize itself. Please restore doom-themes-hide-modeline and check *Messages* for errors or warnings after trying to resize treemacs. C-h e will open this buffer.

Hello,
I've investigated some more. The actual resizing (via C-x { and C-x }) does work after switching to the treemacs buffer via C-x o. The part that actually doesn't work is resizing via the mouse pointer. It simply doesn't show the typical resizing pointer style you get when moving the pointer to the separator between two adjacent buffers.
Could hiding the modeline be made optional?

Sorry for the tremendously later response: after looking into this again I realize that my earlier suspicions were correct: your behavior has nothing to do with the visibility of the mode-line, but Treemacs fixes the width of its window by default. You can toggle this fixed-width off by pressing t w (or M-x treemacs-toggle-fixed-width), the C-x { / C-x } will work.
You can make this the default behavior with:
(add-hook 'treemacs-mode-hook #'treemacs-toggle-fixed-width)

If for some reason this still doesn't fix your issue, you can prevent the mode-line by being hidden with
;; after you call `doom-themes-treemacs-config'
(with-eval-after-load 'treemacs
  (remove-hook 'treemacs-mode-hook #'doom-themes-hide-modeline))

But as this would simply be masking an underlying issue, it's not appropriate to upstream.
In any case, thanks for bringing it to my attention!


found "comment" but expected [.proto element {comment|option|import|syntax|enum|service|package|message}]

I need to generate my logic.go  by my tpl.
How to assign the comment in .proto?
I need my logic.go to show my tpl's {{.comment}}.
My assign in the below picture(I don't know how, just try)

Then I use  goctl rpc protoc ... get error: found "comment" but expected [.proto element   {comment|option|import|syntax|enum|service|package|message}]

this is the getComment link
https://github.com/zeromicro/go-zero/blob/358d86b8ae5d8a43480c5ce124e4c4a4e3e48255/tools/goctl/rpc/parser/comment.go

hope https://go-zero.dev/cn/docs/goctl/zrpc show the comment usage

It's an proto syntax error, if you want to generate head comments for a func, you can try to define your proto like this:
syntax =  "proto3"
package foo;

message Req{}

message Resp{}

service Foo{
  // Place your comment here.
  rpc Bar(Req) returns (Resp)
}

It's an proto syntax error, if you want to generate head comments for a func, you can try to define your proto like this:
syntax =  "proto3"
package foo;

message Req{}

message Resp{}

service Foo{
  // Place your comment here.
  rpc Bar(Req) returns (Resp)
}

This works, thank you!
hope https://go-zero.dev/cn/docs/goctl/zrpc show the comment usage


Confirm and warn dialog icons are not showing up

http://ciena-frost.github.io/ember-frost-modal/#/confirm
http://ciena-frost.github.io/ember-frost-modal/#/warn?isWarnVisible=true

Fixed in #75


a few JS optimizations

Seems reasonable.

Did you test these changes thoroughly? This will certainly break any inline code which tries to access jQuery.

You can definitely see the menu flashing with a fresh cache, please fix/revert.

You can definitely see the menu flashing with a fresh cache, please fix/revert.

The body onload code runs jquery ready, so the menu is already hidden. Will recheck.

This will certainly break any inline code which tries to access jQuery.

Wasn't aware of that usage.

The body onload code runs jquery ready, so the menu is already hidden. Will recheck.

The problem is the moment during which jQuery.js is downloaded/parsed/executed, the HTML and CSS is already available to the browser, which goes ahead and renders them. Since the CSS says that the menus are visible, the browser renders them as visible. Only after jQuery runs are the menus hidden.

Wasn't aware of that usage.

I don't know if we use this right now (that's why I said testing is needed). Even if we don't, moving scripts to the bottom means we won't be able to add inline scripts that use jQuery in the future.

Only after jQuery runs are the menus hidden.

Now fixed by using <noscript><style>. That in turn required to switch to HTML5 which seems a sane choice anyhow.
I still left the scripts at the bottom, couldn't find any jQuery usage in druntime/phobos/dlang.org.
And actually it's good that using more heavy-weight JS in docs would require and explicit change here.

Please don't use <noscript> since it may not always indicate the absence of JavaScript. Opera/Presto ignores <noscript> tags when JS is disabled.

OK, so now you got rid of $(SCRIPT document.body.className += ' have-javascript';) but instead added a hard-coded CSS rule in the HTML document. I might seem extremely nitpicky but I don't see how this is a good change :)

OK, removed the no-js stuff. What about HTML5?

LGTM, ready to merge if you are.


Update chart version to keep main branch latest (ScalarDB GraphQL v3.7.2)

A new patch version of ScalarDB GraphQL Helm Charts has been released.
This PR updates version of ScalarDB GraphQL chart to keep main branch latest.
(This release flow will be fixed in the future.)
This PR applies the same update as the following commit.
https://github.com/scalar-labs/helm-charts/commit/a2fbac90fb24330eeffb7e011f3b8bc726afce33
Please take a look!

Today, I will release the next patch versions. So, I change this PR to draft.
After I release the next patch versions. I will ask review of this PR.

A new patch version of ScalarDB GraphQL Helm Charts has been released.
This PR updates the version of the ScalarDB GraphQL chart to keep the main branch the latest.
(This release flow will be fixed in the future.)
This PR applies the same update as the following commit.
https://github.com/scalar-labs/helm-charts/commit/c2317f7b77625440f11dfc71b743a7d8b6a7bb05
Please take a look!


Workbench-NPE Errors when deleting objects (slots, templates, content types)

Connect workbench application with CM server.

Right Click on any Content Type and select Delete.

Click on Ok button of confirmation prompt.

Observe the error appeared on the screen.

No error logged on jetty server.

closed by fix for #88


[Dataverse] Additional filters - Cross filter

Feature: [Dataverse] Additional filters - Cross filter

As an end-user of the portal on the .../dataverse page,
I want to cross filter the dataverse
So that only items having the metadata I previously selected in a filter are to be selected in the next filter

Acceptance criteria
Scenario  : Cross filter
Given that I am an end-user navigating the portal using a desktop
And I want to cross filter
When I select an item on a filter,
Then the selectable items in the rest of the filters must meet the criteria of the first selected item and so on
And the items that doesn't meet the criteria are hidden
When I select an item in resources
Then only the applicable filter to the resources are to be shown.
Environment

staging URL: https://app.staging.okp4.network/

Additional informations
None.

Estimation to be done the 17th, please prepare the technical specification

Hey team! Please add your planning poker estimate with Zenhub @0xLodz @AnjaMis @ErikssonJoakim @lolottetheclash

Please add your planning poker estimate with Zenhub @amimart

Note that this ticket is of high complexity, and could take over a week of dev even with peer programming


Run workers: Mocha report contains only data from the first worker; all other workers data is lost

Hi,
I'm running tests in parallel using workers:
codeceptjs run-workers --suites 4 --config codecept/config.js --reporter mocha-multi
the generated mocha report only shows the result for the first worker. How to generate the report that will include results for all workers, and not only for the first worker? I'm missing now a lot of information.
What I want to achieve: I want to run tests with four workers and generate mocha report with all the information from all workers, which will be used in the CodeBuild in AWS.
What do you get instead?
From AWS console,
2021-02-04 16:51:12,084 - INFO :: [2]   FAIL  | 10 passed, 2 failed
BUT when I check the generated report, only results from first worker shown.

Also, I checked the generated mocha xml file locally, it also contain the data from the first worker only.
Details

CodeceptJS version: ^3.0.4
NodeJS Version: 12.19
Operating System: MacOS

works when adding hash to my mocha-junit-reporter
more details here: https://www.npmjs.com/package/mocha-junit-reporter#results-report


Increase error messaging

I'm getting
Error during update: Failed to load file

On
https://github.com/nordnet/cordova-hot-code-push/blob/34fc9f3fe36871035790b63692b0354e10deafb9/src/ios/Network/HCPFileDownloader.m#L81
Can you please tell me what URL it is trying to download? It is hard to debug without it.

Yes, that must be added.
Right now you can look in the url variable:
https://github.com/nordnet/cordova-hot-code-push/blob/34fc9f3fe36871035790b63692b0354e10deafb9/src/ios/Network/HCPFileDownloader.m#L79
But I think you know that already.


Why default behavior of generating asset path is not started with root path?

I just had an issue with pathnames with multiple slashes(/.../).
With default behavior, it generates following scripts:
<script type="text/javascript" src="bundle.js"></script>
In SPA, If we navigate to URL like http://somehost/path1/path2, it try to load assets from http://somehost/path1/bundle.js, not http://somehost/bundle.js so it failed to initialize the application.
I found that we can override the path via setting publicPath to '/' so that every assets can be loaded from root path, but the default publicPath value was ''.
Is there any reason that default behavior is not generated with '/'?

Default publicPath goes from your webpack config output.publicPath, which maybe set or maybe not. If you ask why webpack doesn't have output.publicPath set to / by default then it would be better to ask that question in webpack's repo.
If you ask why html-webpack-plugin doesn't have it set to / by default when publicPath is missing, then it's simple (I assume why it's so here): because having it as output.publicPath is a good default. After all, you don't want to have troubles with someone intentionally net setting output.publicPath but suddenly having publicPath as / in html-webpack-plugin.

Correct :)
It would not allow to have relative paths


@searchable returning an error but unable to work out how to fix

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
7.6.5
What operating system are you using?
windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
Nope.
Amplify Categories
api
Amplify Commands
Not applicable
Describe the bug
I believe my search index has got some duff data in it but I'm unsure how to correct it or fix it from the error message give.
I either need a clear way to brute force a reindex of all the data or better error message on how to fix the data issue. As is I'm stuck.
Error:
{"data":null,"errors":[{"path":null,"locations":[{"line":387,"column":11,"sourceName":null}],"message":"Validation error of type FieldUndefined: Field 'user' in type 'StaffMember' is undefined @ 'searchAddresss/items/area/accountManager/user'"},{"path":null,"locations":[{"line":416,"column":11,"sourceName":null}],"message":"Validation error of type FieldUndefined: Field 'user' in type 'StaffMember' is undefined @ 'searchAddresss/items/area/technician/user'"}]}

Now I can guess what its complaining about, some Model doesn't have a connection set that is a requirement, probably due to us changing our schema around during development. Trouble is how do I find that missing conection? We've tried using GraphQL an exisits:false but nothing comes back. We can't find the missing bit of data.
We've tried to trigger a reindex (why is that not a button somewhere btw?) but that seems to result in the same error which makes me think that its still within the source data in DynamoDB?
Expected behavior
Hmmm this is tricky to answer, what is the expected behaviour?
I guess for me it shouldn't be possible to get in this state in the first place. And now I'm in it there should be a clear path to get out of it.
For the ES index, how about not indexing the data if it doesnt' match some validation?
How about we make to easier to reindex.
How about we make it easier to find orphaned connections (if indeed that is what it is).
A lot of fixes for stuff like this seem to always be buried in issues like this rather than out there front of house helping us do our thing quicker without having to be tapping you lovely lovely folks on the shoulder every few hours. I feel like a kid at school constantly queuing up at teachers desk to check a spelling rather than actually doing any writing.
Reproduction steps
I think this might have happened but isn't in itself a full on recreation.
Created a model, Article.
Added some data for that model.
Created a new model, Authors.
Added some data to Authors.
Later wanted to link Authors to their Articles. Create a @connection on Article and Author id is required.
New content will now have to have an Author assigned.
Existing content might not have an Author assigned (ideally this would need back filling but for some reason hasn't been)
Not all of the Articles are updated to include an Author, ES indexes it anyway and GraphQL then blows up when you query it.
Alternatively an Author that was assigned to an Article has then been removed and although referenced still in Article can't be found so returns null?
GraphQL schema(s)

# Put schemas below this line
Recently emails this over to @josefaidt for https://github.com/aws-amplify/amplify-cli/issues/9398#issuecomment-1011493131

Log output

# Put your logs below this line

Additional information
No response

Forgot to add some of the bits we've tried.
We've gone through and added a "unknown" user to all Staff that didn't have one set (test data) and then ensured each Area has StaffMembers set. That from the error is what the problem seems to be. Yet still no fix.
We've tried removing the @searchable from the model in question and pushing, then re-adding it and pushing again. This was in a hope of it rebuilding the index completely incase there was any left over duff setup in ES or similar, scorched earth! Same error.

ok we are now trying to remove the manditory flag on the connectoins to see if that lets it slip throuhg the validation. Believe we had that on there to keep DataStore happy but now we've stripped that out we can have non-manditory fields in connections we think.

Removing the mandatory flag on the staffMember connections didn't work
Re-reading the error, it's not the staffMember that's null, it's the user connection on staff that's returning as null
For reference in the error {"data":null,"errors":[{"path":null,"locations":[{"line":387,"column":11,"sourceName":null}],"message":"Validation error of type FieldUndefined: Field 'user' in type 'StaffMember' is undefined @ 'searchAddresss/items/area/accountManager/user'"},{"path":null,"locations":[{"line":416,"column":11,"sourceName":null}],"message":"Validation error of type FieldUndefined: Field 'user' in type 'StaffMember' is undefined @ 'searchAddresss/items/area/technician/user'"}]}
The technician and accountManager fields are of type StaffMember
StaffMember does not have a user field, there used to be a connection for it but it was removed
(This was to work around a DataStore issue so we could expose the userId on the StaffMember model)
So why is the ES index trying to reference a non existent field? How do we refresh this?
Removing and re-adding @searchable didn't work
Running the ddb_to_es.py script on the table didn't work
There's nothing in the UI to let us rebuild

Here's the relevant bits of our Schema for reference
I can attempt to re-add the user connection now we've removed DataStore from the project but it looks like it's just holding onto stale data and I can't find a way to refresh it
Afraid of trying to delete it in the UI as last time we tried something in the UI instead of the CLI it caused no end of issues
type StaffMember
  @model
  @key(name: "byEmail", fields: ["email"], queryField: "staffByEmail")
  @auth(
    rules: [
      { allow: groups, groups: ["admin"] }
      { allow: public, provider: apiKey }
    ]
  ) {
  id: ID!
  firstName: String!
  lastName: String!
  email: String
  phoneNumber: String
  roles: [String]
  roundDirectionPreference: String
  profilePictureUrl: String
  userID: ID
  # user: User @connection(fields: ["userID"]) THIS IS COMMENTED OUT AND HAS NOT BEEN ACTIVE FOR SOME TIME
  defaultSectorID: ID
  addressLine1: String
  addressLine2: String
  addressLine3: String
  town: String
  county: String
  postcode: String
  geoCords: Location
  hasGeocodingIssues: Boolean
}

type Area
  @model
  @searchable
  @auth(
    rules: [
      { allow: groups, groups: ["admin"] }
      { allow: public, provider: apiKey }
    ]
  )
  @key(name: "bySectorID", fields: ["sectorID"], queryField: "areaBySectorID") {
  id: ID!
  name: String!
  displayName: String!
  active: Boolean
  officePhone: String
  officeAddressName: String
  officeAddress1: String
  officeAddress2: String
  officeTown: String
  officePostcode: String
  officeEmail: String
  geoCords: Location
  hasGeocodingIssues: Boolean
  sectorID: ID!
  sector: Sector @connection(fields: ["sectorID"])
  accountManagerID: ID
  accountManager: StaffMember @connection(fields: ["accountManagerID"])
  technicianID: ID
  technician: StaffMember @connection(fields: ["technicianID"])
  mature: Boolean
  servicePricings: [ServicePricing]
    @connection(keyName: "byAreaID", fields: ["id"])
  postcodesCovered: [String]
  bankName: String
  bankSortCode: String
  bankAccountNumber: String
}

type Address
  @model
  @searchable
  @auth(
    rules: [
      { allow: groups, groups: ["admin"] }
      { allow: public, provider: apiKey }
    ]
  )
  @key(
    name: "byCustomerID"
    fields: ["customerID"]
    queryField: "addressesByCustomerID"
  )
  @key(
    name: "byAreaAndStatus"
    fields: ["areaID", "addressStatus"]
    queryField: "addressesByAreaAndStatus"
  )
  @key(name: "byAreaID", fields: ["areaID"], queryField: "addressesByAreaID") {
  id: ID!
  companyName: String
  addressLine1: String!
  addressLine2: String
  addressLine3: String
  town: String
  county: String
  postcode: String!
  phoneNumber: String
  bedrooms: Int!
  houseTypeID: ID!
  houseType: HouseType @connection(fields: ["houseTypeID"])
  hasConservatory: Boolean
  customerID: ID!
  customer: Customer! @connection(fields: ["customerID"])
  addressStatus: String!
  importantVisitSummary: String
  importantCAMSummary: String
  comments: [Comment] @connection(keyName: "bySourceID", fields: ["id"])
  subscribedServices: [ServiceSubscription]
    @connection(keyName: "byAddressID", fields: ["id"])
  sectorID: ID
  areaID: ID!
  area: Area! @connection(fields: ["areaID"])
  geoCords: Location
  hasGeocodingIssues: Boolean
}

Re-adding the user connection to StaffMember fixed that error but what if we don't want to re-add an old connection?
How would we work around that?
In Addition to the error reported, we're also getting these from the same search
Can't serialize value (/searchAddresss/items[1]/_lastChangedAt) : Unable to serialize 1.6190332464E12 as a valid timestamp. Ensure that the value provided is an Integer that lies within the limits specified in this scalar's description.
Not sure what to do about this one, _lastChangedAt is an internal field we can't touch
Cannot return null for non-nullable type: 'Customer' within parent 'Address' (/searchAddresss/items[0]/customer)
I've queried all addresses and checked that each customerID matches an existing customer and they all do, none of them return as null/undefined
My first suspicion is stale data in the ES index but I'll see what I can find

We're now also getting this error
Can't serialize value (/searchCustomers/items[16]/signUpDate) : Unable to serialize 2021-03-31T17:06:20.707Z as a valid date.
Are signUpDates were originally AWSDateTime but with the release of AWSDate we've been using that
All of the data we have is in the date format without a timestamp eg. "2021-03-31"
Again it looks like the ES index has stale data it tries to validate against the most recent schema

Hey @PeteDuncanson and @JackPenney - I know we discussed some strategies around this last week - what is the current status?
The biggest dangling thread that I still see is from your comment "it shouldn't be possible to get in this state in the first place" - but I also want to make sure you've been able to get yourself unblocked.

Hey @johnpc
So I tried clearing the index and reindexing via the python script in the docs (https://github.com/aws-amplify/amplify-cli/blob/master/packages/graphql-elasticsearch-transformer/scripts/ddb_to_es.py). The reindex said it worked but no updated data appears. Then then I tried deleting the index, then creating a new mapping and reindexing again. Script reports it works but no data appears. Then I gave up.
Since then I had the idea to spin up a new environment (which I hope will spin up a clean ES instance with the correct mappings) and then "steal" those mappings to apply to my other ES instance (or just use that instance for my other environment) but that again seems "wrong" so I'm loathed to spend time on it, feels like I shouldn't have to spin up a whole new environment each time I do a schema change.
Open to ideas, options and suggestion. I still don't understand how it go into this state...again :(
Cheers
Pete

I guess this issue tracks the latest better, its all related I feel https://github.com/aws-amplify/amplify-cli/issues/9536#issuecomment-1016715768

Closing this as a duplicate


Vote on whether to move to Medium as the editing/deployment platform for the newsletter.

The question we're asking is: do we move to Medium as the platform for editing/posting the newsletter?
Please vote by using the 👍 /👎  emojis below for tallying.  Obviously feel free to post a comment with further info if you'd like.
My personal vote is yes, based on the fact that the team doing most of the work on this found it to be a good solution that solved a number of problems they were having workflow-wise, it provides good email integration and stable, archival URLs for the posts.  It's not perfect (multi-editor revisioning is pretty primitive/nonexistent, archival of source material in a cleaner format like markdown doesn't seem easy), but it works for what we need now.
Others may have different opinions, of course.
See #26 for background.

I think one of my primary concerns is the ability to get the material out of a proprietary system in the future if the need arises. When you say archiving is not easy...is it doable to get the material out, especially in an automated way (i.e., download all articles)?

Export from Medium is via Settings in their UI. @ruv7 and I did a test this morning and the ZIP file of all html contents of all articles was delivered in a matter of seconds.
FYI. Observing the CP newsletter folks at work, it does seem to me that Medium is an easier process than Ghost was.

Cool, thanks for checking. I defer to all ya'lls judgement on the matter.

Brian/Katie had previously voiced their yes votes on the transition. @JamiesHQ @Carreau - any feedback or thoughts? If not please indicate this so we can move forward.

Well, I was not able to access, or received any invite to edit or view the edit interface so hard to judge, so I'll let involved person make a judgement.

In the flurry of emails on the topic I can't seem to pinpoint how/when the draft of the first two posts which are currently live was sent out. Perhaps this came from @katiewhite360 and that's why I can't seem to find. Regardless of whether I sent them or Katie sent I thought you had received... This flags a problem I see with managing this process/task with such a large group of contributors. I think that to keep things moving it would be ideal to have one technical person co-lead the effort with me and have others who are interested in the topic serve as backups for when the other person is traveling or otherwise unavailable to help. @fperez @ellisonbg - please close the loop on proposed idea with me - if that doesn't work let's define who needs to say yes to this idea so we can make progress.

@willingc, could you post/send that test zip file? I'd like to run a quick test on it out of curiosity...
@Ruv7, could you make @Carreau an editor so he could have a look at the edit interface?
Thanks!

@fperez I shared the google folder with you.

Only publication owners can delete a publication and add editors. @ellisonbg would need to do this. As an editor I can only add writers.

Thanks @willingc! I tested the conversion to markdown from the folder you gave me, using pandoc, and it mostly works pretty well. The following three lines of ipython do the trick:
files =! ls
for f in files:
    !pandoc -f docx -t markdown --atx-headers $f > {f.replace('html.docx', 'md')}

I've pasted the result here.
The original, for comparison, is here
A few notes on the result:

The Medium export isn't really HTML, it's this awful "Word HTML" format. Pandoc mostly understands and exports it, except...

Images aren't correctly exported: we'd need to save those to files manually.

Furthermore, embedded media like the video at the end aren't exported at all.

In summary, I think it's doable, but it will require a little bit of elbow grease.
My suggestion:

We open a repo for the static, markdown version of this material.
At publication time, for each newsletter, we run the above code (python-ified into a standalone script so it can be done mindlessly from the cmd line without ipython) to get markdown.
The result is fixed up by hand to include the images (by downloading them - we can script that too if we really want, but it's just minutes of manual labor).
We fix by hand any links to embedded videos and other similar media that don't get exported.
We commit and push the resulting static markdown back up to this archival site.

@Ruv7, how does that sound? I'm happy to help you out walking you through this process so that you and your team can do this, my estimate is that once you're familiar with the process, it will just add at most a few minutes per newsletter, which is peanuts compared to the actual work of writing it up.
That would give us a pretty solid archival story for the long run, I think
Is this acceptable to folks? BTW @jasongrout, thanks for pressing on this!!

The publication owner is @ProjectJupyter and the authentication is the
regular Twitter account. Matthias can add himself as an editor by logging
onto Medium using this account.
On Thu, May 5, 2016 at 9:33 PM, Ana Ruvalcaba<EMAIL_ADDRESS>wrote:

Only publication owners can delete a publication and add editors.
@ellisonbg https://github.com/ellisonbg would need to do this. As an
editor I can only add writers.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/jupyter/newsletter/issues/27#issuecomment-217346513

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

What is the goal of having a separate archive of the posts that is updated upon each newsletter being published?
I agree that it is good to be able to get all of our data if/when we need it, but I don't see why we have to do that whole process every two weeks, even though we are not going to use the data in any useful way in the short term.
The danger of Medium disappearing without notice is extremely minimal - far lower than us loosing all the data from our Ghost blog because our deployment fails. That actually almost happened a while back. The backup of the Ghost blog even failed, but thankfully we had a second backup that did work.
I am fine if someone technical wants to volunteer to do this work regularly, but that should be entirely decoupled from the newsletter team's regular work.

I don't like the idea of "do your backups in an emergency". It's kind of saying "buy a fire extinguisher when your house is on fire".
I think if we want the data to be backed up, it should be done when created. The process I outlined is literally minutes of work (for a machine with python and pandoc).  I don't think it's too high a burden to keep our data available in a clean format for future record.
Furthermore, it's a lot easier to spot little problems and fix them once a month for a couple of newsletters, than to go back and fix a ton of them retroactively.  That would indeed be a lot of work.
I simply think that good data hygiene implies keeping the backed-up info in a good state as we go along.  In the grand scheme of things, I think it's a very minimal burden for the upside of having all our newsletters cleanly archived for the long haul.

We have way more important stuff going not backed up, but as long as
someone technical wants to do this regularly, I don't mind.
On Thu, May 5, 2016 at 10:56 PM, Fernando Perez<EMAIL_ADDRESS>wrote:

I don't like the idea of "do your backups in an emergency". It's kind of
saying "buy a fire extinguisher when your house is on fire".
I think if we want the data to be backed up, it should be done when
created. The process I outlined is literally minutes of work (for a
machine with python and pandoc). I don't think it's too high a burden to
keep our data available in a clean format for future record.
Furthermore, it's a lot easier to spot little problems and fix them
once a month for a couple of newsletters, than to go back and fix a ton of
them retroactively. That would indeed be a lot of work.
I simply think that good data hygiene implies keeping the backed-up info
in a good state as we go along. In the grand scheme of things, I think it's
a very minimal burden for the upside of having all our newsletters cleanly
archived for the long haul.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/jupyter/newsletter/issues/27#issuecomment-217353780

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Also, if no one technical steps up to the plate, Ana or Katie could just
download the .zip file and throw it into a dropbox folder with a name that
reflects the date. Not pretty, but would at least cover the data loss risk.
On Thu, May 5, 2016 at 11:05 PM, Brian Granger<EMAIL_ADDRESS>wrote:

We have way more important stuff going not backed up, but as long as
someone technical wants to do this regularly, I don't mind.
On Thu, May 5, 2016 at 10:56 PM, Fernando Perez<EMAIL_ADDRESS>wrote:

I don't like the idea of "do your backups in an emergency". It's kind of
saying "buy a fire extinguisher when your house is on fire".
I think if we want the data to be backed up, it should be done when
created. The process I outlined is literally minutes of work (for a
machine with python and pandoc). I don't think it's too high a burden to
keep our data available in a clean format for future record.
Furthermore, it's a lot easier to spot little problems and fix them
once a month for a couple of newsletters, than to go back and fix a ton of
them retroactively. That would indeed be a lot of work.
I simply think that good data hygiene implies keeping the backed-up info
in a good state as we go along. In the grand scheme of things, I think it's
a very minimal burden for the upside of having all our newsletters cleanly
archived for the long haul.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/jupyter/newsletter/issues/27#issuecomment-217353780

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>
--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Is there a way for anyone else to download that data? I can't seem to...  It would be good to ensure that folks other than Ana and Katie can actually grab the raw data.

ps - what else is critical that we aren't backing up? If that's the case, we should make a list and a plan to address it...

Actually, scratch that: the docx format seemed to be an artifact of Google Drive. @willingc, could you email me the zip file directly as generated by Medium itself? Would be best to test how much extra cleanup is really necessary straight from their archive, Google Drive seems to be doing an automatic export to Word as best I can tell.

@Ruv7 Would you mind emailing @fperez the zipped zip file that we downloaded from medium yesterday? I only have the unzipped in Google Docs. I'll be in the office in a bit if we need to download again 💃

Not backed up:

All of our hackpads.
All of the many google docs spread across numerous people's Google Drives.
All of the Dropbox files spread across different accounts.

On Fri, May 6, 2016 at 8:20 AM, Carol Willing<EMAIL_ADDRESS>wrote:

@Ruv7 https://github.com/Ruv7 Would you mind emailing @fperez
https://github.com/fperez the zipped zip file that we downloaded from
medium yesterday? I only have the unzipped in Google Docs. I'll be in the
office in a bit if we need to download again 💃
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/jupyter/newsletter/issues/27#issuecomment-217472066

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Yes I can send the unzipped file. Is this detail going to stop us from using Medium? If not does it make sense that we concurrently create the custom sub domain so that when we work through this we are ready to go? I'm wrapping up the design with Cameron today.

Lately I've been viewing hackpad, slack, and Dropbox as ephemeral just-in-time thinking and design work. If it's meant to carry on longer, it must end up in a repository somewhere whether in code, doc, or issue.
As for assets, while not completely bulletproof, git+lfs has been pretty good so long as you set up the repo right.
I'm definitely not going to volunteer for setting up a job to slurp down our medium posts. I am quite happy with using Medium though, it sounds like a great and simple direction for the project.

Pretty much all non-technical parts of the project are on Dropbox/Google/Hackpad. This includes staffing, budgets, financial, organizational, fund-raising, design, communications. Many/most of the people who work with these documents don't use GitHub at all.

The danger of Medium disappearing without notice is extremely minimal - far lower than us loosing all the data from our Ghost blog because our deployment fails. That actually almost happened a while back. The backup of the Ghost blog even failed, but thankfully we had a second backup that did work.

FYI, the purpose of my original query had more to do with how we get our content out if we decide in the future to migrate off of medium, not necessarily how to back up our content for when medium catastrophically fails. It's useful to think about backups of important content too, but that's also part of a much larger conversation about all of our "critical" content, and I don't think that larger conversation should necessarily impede progress here.

Thanks for the clarification - from that perspective the HTML export that
Medium has should be sufficient and we can do that if/when we decide to
migrate elsewhere.
On Mon, May 9, 2016 at 6:23 AM, Jason Grout<EMAIL_ADDRESS>wrote:

The danger of Medium disappearing without notice is extremely minimal -
far lower than us loosing all the data from our Ghost blog because our
deployment fails. That actually almost happened a while back. The backup of
the Ghost blog even failed, but thankfully we had a second backup that did
work.
FYI, the purpose of my original query had more to do with how we get our
content out if we decide in the future to migrate off of medium, not
necessarily how to back up our content for when medium catastrophically
fails. It's useful to think about backups of important content too, but
that's also part of a much larger conversation about all of our "critical"
content, and I don't think that larger conversation should necessarily
impede progress here.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/jupyter/newsletter/issues/27#issuecomment-217862471

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Next steps to closing out this issue:
@cameronoelsen - can you point me to towards the images you created, I'll upload and make sure they're working well
@katiewhite360  - please let me know when you have final drafted for the post. Link to today's DevMeeting: ttps://youtu.be/5FilnwzSicU
@minrk - thanks for volunteering to create the custom sub domain, what info do you need to create this?

@Ruv7 To help with the time difference, @minrk probably would need what you want as the custom subdomain name, i.e. newsletter.jupyter.org or puppiesandkittens.jupyter.org and possibly an email associated with the newsletter.

Here is the header:

I can make one of these when we know the day we will be publishing:

puppiesandkittens.jupyter.org

I vote for this one.

and possibly an email associated with the newsletter.

That already exist and is<EMAIL_ADDRESS>which redirect to<EMAIL_ADDRESS>and hence is autotagged by the projectJupyter gmail account.

@minrk - thanks for volunteering to create the custom sub domain, what info do you need to create this?

newsletter.jupyter.org also already exists and point to the newsletter on medium already:

You beat me to this, I was going to check what the address was and I see that it is already done. @ellisonbg please confirm if anything else needs to happen. Our medium account can now be found at https://newsletter.jupyter.org/

Great I think we are ready to go with the next one on medium - thanks everyone!
Sent from my iPhone

On May 10, 2016, at 3:56 PM, Ana Ruvalcaba<EMAIL_ADDRESS>wrote:
You beat me to this, I was going to check what the address was and I see that it is already done. @ellisonbg please confirm if anything else needs to happen. Our medium account can now be found at https://newsletter.jupyter.org/
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

newsletter.jupyter should be all set up. I can point something else to it as well, if that was wrong.

Sorry, I replied to Ana via email separately. Yes, I don't think we need to hold this decision contingent on the archiving: what we get from medium in HTML isn't ideal, but it's workable.
I do think that our publicly facing "persistent" content, like blog and newsletter raw sources, should be stored in a repo somewhere always, along the lines @rgbkrk states above, as a matter of principle. It's viable to do at least the 80% version of that with minimal effort.


Fix aggregation for units with missing values

@saelsa It would be great to adapt the docstring of this method for param method: and list the currently supported aggregation-methods, see here

@saelsa Please merge the current develop in your branch. I fixed the CI there.


Add more keyboard shortcuts to sprite editor

I really like the keyboard shortcuts provided by Aseprite and Piskel and I constantly find myself trying to use them in the sprite editor.
Here are the tool keybindings from Aseprite and Piskel:

Tool
Aseprite
Piskel

Paint Bucket
G
B

Pencil
B
P

Draw Rectangle
U
R

Draw Line
L
L

Eraser
E
E

Draw Circle
shift-U
C

Personally, I think the Piskel ones are a little more obvious
Other nice to haves:

Holding shift while in the pencil tool draws a line from the last pen-up location to the cursor
Undo and Redo shortcuts (right now this closes the sprite editor)
Holding alt while clicking selects the color under the cursor in the palette

I love the Aseprite ones personally because many of them mimic Photoshop shortcuts which have been reinforced in my brain since 1993 : ]

Ah, in https://github.com/microsoft/pxt/pull/5549 I leaned towards the piskel ones as they seemed a bit more intuitive when richard and I discussed it offline (though we were both used to aseprite / photoshop shortcuts personally as well)


Add new integration test

Test starknets hello world contract https://www.cairo-lang.org/docs/hello_starknet/intro.html#your-first-contract

I'm not sure if your_first_contract is the best possible name for the test. What about increase_balance? I think it may be more descriptive.

I'm not sure if your_first_contract is the best possible name for the test. What about increase_balance? I think it may be more descriptive.

How about hello_starknet_inrease_balance? I wanted the test name to reflect that we have one of the starknet examples running

Codecov Report

Merging #157 (de88cda) into main (c0ca33f) will increase coverage by 0.65%.
The diff coverage is 77.77%.

@@            Coverage Diff             @@
##             main     #157      +/-   ##
==========================================
+ Coverage   74.59%   75.25%   +0.65%
==========================================
  Files          34       34
  Lines        1858     1883      +25
==========================================
+ Hits         1386     1417      +31
+ Misses        472      466       -6

Impacted Files
Coverage Δ

src/business_logic/state/cached_state.rs
71.95% <ø> (ø)

src/core/syscalls/os_syscall_handler.rs
84.31% <0.00%> (-0.84%)
:arrow_down:

...rc/core/syscalls/business_logic_syscall_handler.rs
69.76% <44.44%> (+2.94%)
:arrow_up:

src/core/syscalls/syscall_handler.rs
80.58% <100.00%> (+0.46%)
:arrow_up:

src/core/syscalls/syscall_info.rs
100.00% <100.00%> (ø)

src/core/syscalls/syscall_request.rs
86.88% <100.00%> (+1.43%)
:arrow_up:

...usiness_logic/fact_state/in_memory_state_reader.rs
95.83% <0.00%> (+12.50%)
:arrow_up:

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

How about hello_starknet_inrease_balance? I wanted the test name to reflect that we have one of the starknet examples running

Although more descriptive, that's even longer. Since you can't see the entire name from the file tree on vscode unless you make the column large (wasting space), what about leaving the shorter name while changing the test name to hello_starknet_increase_balance? That name is what will be displayed when running the test, after all.

How about hello_starknet_inrease_balance? I wanted the test name to reflect that we have one of the starknet examples running

Although more descriptive, that's even longer. Since you can't see the entire name from the file tree on vscode unless you make the column large (wasting space), what about leaving the shorter name while changing the test name to hello_starknet_increase_balance? That name is what will be displayed when running the test, after all.

Good Idea, I made the changes https://github.com/lambdaclass/starknet_in_rust/pull/157/commits/4c62931831bb3355f68a5efb6f91a2eafe46eb50


feat: position & content consistent comment removal

closes #43 to create a position and content-consistent comment removal evaluation. We do this by performing post-processing on the originally constructed context in make_code_cotext. Follows the steps:

Grab original constructed prefix, needle_code and suffix contexts
Remove comments from the components
Calculate the amount of tokens removed
Fill back the missing tokens using some dummy token

This approach guarantees that the comment-free context is content-consistent (i.e. the same code content just with the comments removed). The position may very slightly fluctuate (less than 1 percent difference in my testing) simply due to the dummy token used and the tokenizer
This code performs post-processing on the constructed context so no prior works should be impacted by this.

One question: will the "dummy"s be included in the input context? Other changes look good.

Yes it would atm, open to feedback on more non-intrusive tokens that don't change the semantics of the code context.

Modified to use language comment prefix which is a more non-intrusive dummy token in terms of code understanding for the models.

A known issue is that if we have repeated "#\n", OAI will complain about the repeated patterns:

Not sure if we can hack by adding things like # Comment {LINE_NO}.


Idk if this has been reported

Bazzites logo while updating steam client show up with a white background instead of bazzite background
[]

Happening on Steam Deck LCD and HTPC for me too

Fixed in testing and will hit stable soon.


Shouldn't Biometric Authentication (D3-BAN) map to User Account artifact (similar to MFA)?

Backup Documentation for D3-BAN Issue.docx

Yes, will get this added, thank you!


⚠ Bofrost.at has degraded performance

In 61e9676, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1459 ms

Resolved: Bofrost.at performance has improved in e2500d7 after 6 minutes.


[Fix][web] Fields' value should be clear after closing edit dialog on Registration Center's Flink instance management page

… Registration Center's Flink instance management page
Purpose of the pull request
fixed #1344

Brief change log

reset form when render cluster form

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Hi. This fix has serious problems.

Hi. This fix has serious problems.

Got that. How to reproduce.

Try to create a new cluster or cluster configuration.

Try to create a new cluster or cluster configuration.

Okay, I reproduce that in cluster configuration. onValuesChange will invoke rednerContent() I guess. But cluster is ok right?
I will fix that ASAP.

@aiwenmo see #1449


PowerToys Run crashed after the search result came

Microsoft PowerToys version
<IP_ADDRESS>
Running as admin

[X] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce
2022-04-13.txt
✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

[2022-04-13 11:40:19.9278] [FATAL]
Exception
System.InvalidOperationException: Dispatcher processing has been suspended, but messages are still being processed.
   Source: WindowsBase
   TargetAssembly: WindowsBase, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35
   TargetModule: WindowsBase.dll
   TargetSite: IntPtr WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Environment

Command Line: "C:\Program Files\PowerToys\modules\launcher\PowerToys.PowerLauncher.dll" -powerToysPid 26776 --started-from-runner
Timestamp: 04/13/2022 11:40:19
Wox version: <IP_ADDRESS>
OS Version: Microsoft Windows NT 10.0.19043.0
IntPtr Length: 8
x64: True
CLR Version: 6.0.3
Installed .NET Framework:

v2.0.50727 2.0.50727.4927 SP2
v3.0 3.0.30729.4926 SP2
v3.5 3.5.30729.4926 SP1
v4 Client 4.8.04084
v4 Full 4.8.04084
v4.0 Client <IP_ADDRESS>

/dup #17371
Could you please try these instructions in 0.57.2 and post results in that issue?
https://github.com/microsoft/PowerToys/issues/17371#issuecomment-1087604609


Fix typos

Found via codespell -S target,*.txt -L crate

@rillian Separate PR for cargo fmt created, https://github.com/abonander/multipart/pull/147.


Add changes to the MIGRATION.md

We need to write down the changes made in 0.14 -> 0.15 in MIGRATION.md.

WasmMsg::Execute and WasmMsg::Instantiate - rename send to funds.


Value wrapping has problem finding serializer

See notebooks/00_basic_padl

https://github.com/lf1-io/padl/tree/401-serializer-notebook


Drop python 3.8 support

Please describe your wishes and possible alternatives to achieve the desired result.
We're well past the window for python 3.8 support (https://scientific-python.org/specs/spec-0000/#support-window), so we should drop it for the next version.

@flying-sheep, seems like a PR you might wanna make?

next version will be 0.10? no patch release?
then we could just bump the version, add Ruff’s "UP" rules and have Ruff handle most things for us.


Add dark mode

Thou shall not blast my eyes with #FFFFFF as the background color and #000000 as the text/foreground color.

Made it.
Currently, you can't change back to Light mode (which you shouldn't be able), and I haven't fully done it.

I have a made a fork with dark mode.
If you're wondering why the commit changes a lot, it's because I didn't clone the repo, I downloaded the source as a ZIP file...
Which means that I didn't have git source control.


exposes backgroundColour to python

What does this implement/fix? Explain your changes.
Exposes the drawing option backgroundColour to python.
Any other comments?
@DavidACosgrove @greglandrum Hopefully this is a simple one.

The idea is that this should remove the need for the get/setBackgroundColour() methods?

That and it exposes the RDKit Colour directly.
It's really a POC so we can ignore it for now.
On Thu, Sep 7, 2017 at 8:51 AM, Greg Landrum<EMAIL_ADDRESS>wrote:

The idea is that this should remove the need for the
get/setBackgroundColour() methods?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rdkit/rdkit/pull/1548#issuecomment-327789601, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJbioPmhGq61Lka0KZ1xr_euMZGNpYw2ks5sf-bWgaJpZM4PPwVy
.

It looks like the tuple stuff doesn't work outside of clang

We can revisit on the modern-c++ branch in the not-too-distant future


Compatibility with Isotope

An optional enhancement:
I am struggling to make this plugin compatible with http://isotope.metafizzy.co/. After sorting the lightbox still shows all the images in the gallery.
I am sure I am not the only one who would like to use your Lightbox plugin with a sorting plugin.
Could you advise how to make the lightbox see only the elements that are on the screen, but not the ones that are hidden?
Maybe add it to the docs?
Would really appreciate that.
Example of the problem is here.
Cheers!

I would listen for the isotope event  arrangeComplete and add the data-gallery attribute for items that are displayed and remove it for others.
You might need to look into jquerys removeData function as this info is cached.
You'll be better off asking on stackoverflow as I've never used isotope.


Don't load events when there's a gap between known events

Fixes https://github.com/matrix-org/sliding-sync/issues/283
Part of #294.
Is going to conflict with #296.
Recommend commitwise review. I was going to write an E2E test, but it's fiddley to get a gappy sync deterministically, so opted for an integration test.

Upgrade test is failing. After the upgrade:
Sync v3 [0.99.10] (262f8cb)
Debug=true LogLevel= MaxConns=0
panic: pq: column "missing_previous" of relation "syncv3_events" does not exist

goroutine 1 [running]:
github.com/jmoiron/sqlx.MustExec(...)
	/home/runner/go/pkg/mod/github.com/jmoiron/sqlx@v1.3.3/sqlx.go:722
github.com/jmoiron/sqlx.(*DB).MustExec(0x30?, {0xdbf993?, 0xc0003c4c60?}, {0x0?, 0xc0002ef900?, 0x40fd47?})
	/home/runner/go/pkg/mod/github.com/jmoiron/sqlx@v1.3.3/sqlx.go:366 +0x46
github.com/matrix-org/sliding-sync/state.NewEventTable(...)
	/home/runner/work/sliding-sync/sliding-sync/state/event_table.go:116
github.com/matrix-org/sliding-sync/state.NewStorageWithDB(0xc0003c4c90, 0x0)
	/home/runner/work/sliding-sync/sliding-sync/state/storage.go:85 +0x70
github.com/matrix-org/sliding-sync.Setup({0xc00004248e?, 0xd7fc8b?}, {0xc00004806a, 0x4c}, {0xc00003c00e, 0xa}, {0x0, 0x0, 0x0, 0x3b9aca00, ...})
	/home/runner/work/sliding-sync/sliding-sync/v3.go:106 +0x189
main.main()
	/home/runner/work/sliding-sync/sliding-sync/cmd/syncv3/main.go:213 +0x175b

That's a surprise to me because I thought CREATE TABLE IF NOT EXISTS would be a no-op if the table already exists!

Oh this will be the COMMENT ON..., won't it?

Only EW failed, but it suceeded on the prior commit. The only change I made was in unit tests, so I assume this is some Cypressy flake.


Revert "fix: workaround for exit code 134 (#106)"

This reverts commit 4e255cd85c7df9dea31500eeee012464c5645267 (#106).
This workaround is not needed in neovim 0.10 anymore, and is actually making the session completely freeze for 10m upon exit.

Thanks. Could we put a check in for users below version 0.10 though?


GitHub actions

Sorry for the delay in getting this over the line!
I'm going to continue working on the Windows issues and aim to get both a Windows and a Cygwin on Windows build working soon.
Could you take a look at the tests skipped in chore: skip leaky tests and see if you're able to make sense of what's happening? I can then rebase out that commit before you merge this.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This looks good. I'm going to go ahead and merge then diagnose the skipped tests post merge
This isn't a blocker but just a question: did the ci/cd test fail when jest was running in parallel? noticed that we changed it to run serially

This looks good. I'm going to go ahead and merge then diagnose the skipped tests post merge
This isn't a blocker but just a question: did the ci/cd test fail when jest was running in parallel? noticed that we changed it to run serially

@kevins8 sweet, thanks for reviewing this. I switched to running serially to make the Jest output easier to read when troubleshooting failures. Happy to switch to running them in parallel if you prefer? I could try to split out the test output per-module and make that available as an artifact.

@kevins8 sweet, thanks for reviewing this. I switched to running serially to make the Jest output easier to read when troubleshooting failures. Happy to switch to running them in parallel if you prefer? I could try to split out the test output per-module and make that available as an artifact.

@kevins8 sweet, thanks for reviewing this. I switched to running serially to make the Jest output easier to read when troubleshooting failures. Happy to switch to running them in parallel if you prefer? I could try to split out the test output per-module and make that available as an artifact.

Got it. no worries since ci-cd minutes are (for now) free on github for open source. I might add a separate local parallel option since I usually run it manually before committing.
One last thing, could you also update the developer getting started docs with the new scripts?

@kevins8 sweet, thanks for reviewing this. I switched to running serially to make the Jest output easier to read when troubleshooting failures. Happy to switch to running them in parallel if you prefer? I could try to split out the test output per-module and make that available as an artifact.

Got it. no worries since ci-cd minutes are (for now) free on github for open source. I might add a separate local parallel option since I usually run it manually before committing.
One last thing, could you also update the developer getting started docs with the new scripts?


the size did not usefull    最新版本的在设置的size后在不起作用，如果height太小，就会遮挡底部

child: HighCharts(
loader: const SizedBox(
child: LinearProgressIndicator(),
width: 200,
),
size: const Size(400, 380),
data: logic.chartPption,
scripts: const [
"https://code.highcharts.com/highcharts.js",
'https://code.highcharts.com/modules/networkgraph.js',
'https://code.highcharts.com/modules/exporting.js',
],
),

Hello yuxingmin,
Can you Share a Screenshot so it would be great to fix it out.


Use stream_socket_set_options on PHP 8.3

https://github.com/search?q=org%3Aamphp "stream_context_set_option"&type=code

Calling stream_context_set_option() with 2 arguments is deprecated, use stream_context_set_options() instead

See https://github.com/symfony/symfony/pull/54102/files for inspiration :)

Somehow I managed to leave the prior call in place when I "fixed" this before. 😅
Fixed now for real and tagged as 2.2.4.


Specified gremlinpython library version 3.4.13

Specified that we recommend the use of gremlinpython==3.4.13 with the Gremlin (Graph) API for the time being.
The previous instructions would result in pip defaulting to version 3.5.2, which was not working correctly when I attempted to run the sample.

@john-pao : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

Whoops. Yeah, I'm not authorized to merge this.

@manishmsfte Do you want the pull request to be closed?
Thanks.

Merged, please.

Hi @john-pao - I need the author to sign off. I see contradictory directions, so could @manishmsfte clarify?

Thank you!

Kindly merge the PR.

Thanks, all.


Doesn't work with cloudflare R2 and Google cloud run ?

I tried the example on R2 and gcp  with more than 100MB file. Due to limitation of 32MB on cloudrun and 100MB on R2, this is not working.
Also, what's the benefit of using this lib over simply using await req.formData() on edge server (vercel or cloudflare workers).

Depending on which implementation you're using, req.formData() will typically need to buffer the entire request in memory instead of streaming it.
HTTP 413 indicates the server rejected the request because the payload was too large. That doesn't have anything to do with this parser. Rather, it's probably a setting you can adjust on your GCP config.


Support examples for numeric array fields

This PR adds support for examples for numeric array fields. It depends on #232.

@nkly could you help resolve conflicts?

@easonlin404 Sure thing!


Delete unused files of thirdparty libs (zlib, mbedtls)

They weren't listed inside appropriate source lists (inside SCsub files) so this change shouldn't affect compiled binaries at all but obviously check it

Please update the readme with the deletion indtructions

Thanks!


Persons without declarations

We have 58 MPIs without declarations which were inserted during 2 hours 5-7 pm 02.04.2018
select *
from persons p left join declarations dec on p.id=dec.person_id
where dec.id is null and p.inserted_at::date=date'2018-04-02'

We need to clarify why it happened.

A long-shot guess for now: there's a declaration creation process, of which mpi creation is a part of, that didn't finish successfully. Hence MPI was created, but declaration didn't.
@danakonovalenko what do you think?

@gmile

we should be sure
we should find proofs of this theory at least for few records
we should investigate what exactly went wrong with the declaration sign process.

The main point that it has happened just BEFORE release

sign declaration request is a multi-step process with the orchestration of different services: ael, mpi, declarations, etc. There is no transaction within the orchestration. That's why the steps order that has been chosen suppose that we might have mpi without declaration, but there shouldn't be any declaration without mpi. And this is the case.


Prepare.sh structure of the zip directory

Hi,
Thanks again for your work. I followed the instruction on prepare.sh and tried to reproduce vild*. However, the estimated training time is > 5 days instead of ~ 2 days as you mentioned in other posts. I suspect the issue is with the lvis_clip_image_embedding.zip and want to confirm whether what I have is correct.

I followed the first command in prepare.sh but turn it into 8 GPU execution:
CUDA_VISIBLE_DEVICES=0,1,2,3,4,5,6,7 ./tools/dist_train.sh  configs/lvis/detpro_ens_20e.py 8 --work-dir workdirs/collect_data --cfg-options model.roi_head.load_feature=False total_epochs=1, which gives me 99342 *.pth files under data/lvis_clip_image_embedding/train2017.
After step 1, I run: zip -r data/lvis_clip_image_embedding.zip data/lvis_clip_image_embedding/*  from the root directory and get data/lvis_clip_image_embedding.zip
I run ./tools/dist_train.sh configs/lvis/detpro_ens_20e.py 8 --work-dir workdirs/vild --cfg-options model.roi_head.prompt_path=lvis_clip_text_embedding.pt model.roi_head.load_feature=True as instructed in another post with 8 GPUs. I checked the GPU usage and they are all fully loaded so I didn't think the problem is with GPU utilization. However, the estimated finishing time is > 5 days.

I checked the hierarchy inside lvis_clip_image_embedding.zip and it looks like the internal hierarchy looks like:
data/lvis_clip_image_embedding/train2017/000000203466.pth while the zip file is already under ./data. In other words, it seems that a redundant level of data is created inside the zip file. I'm not sure if this expected or not. If not, what is the expected hierarchy inside the zip file?
Thanks for your help!

I think I solved the problem now. It turns out that we need to modify the path of loading embeddings in standard_roi_head.py to make it consistent with the path in zip file.
A reference for future users: if your program loads the clip embeddings correctly, there should be no directory called lvis_clip_image_embedding created under data/.
After fixing this, the training estimation time becomes 3 days and half with 8 V100 GPUs...still a bit slower than the estimation provided by the author but seems to be ok


Can I use elastic.v7 for both elasticsearch 5.x and 7.x

Which version of Elastic are you using?
elastic.v7 (for Elasticsearch 7.x)
We have two ES clusters, one is ES 5.X while the other is 7.X. The mapping is almost the same. Can we use elastic.v7 to support both cluster?

You can certainly try, but some responses are simply different in ES 5.x and ES 7.x, e.g. the number of total hits is (by default) returned differently in ES 5/6 and ES 7. See here for e.g. a list of breaking changes in 7.x.
Also, ES sometimes changed the way to retrieve the list of nodes in the cluster. It doesn't make any guarantees on that the ES 7 client will find the nodes in an ES 5 cluster.
In general, I would provide an interface to perform operations against an ES cluster. Here's an example of that. That also makes testing so much easier, as you can mock the ES cluster.


Sides of Tiles appear as if they are shadowed regardless of lighting settings

I have a Hex Tiles map set up in my project running an out of the box URP shader for its rendering settings. Regardless of what material I place on the tiles themselves, the sides appear as if they are always shadowed. I have tried baking lighting with the global lighting settings and if I set a high enough intensity it's clear that the textures themselves are mapped correctly, they're just... very dark. At a global intensity of 1 they are too dark to see.

If I turn off "Scene Lighting" the problem "fixes" itself, but inside the game that uses a "sun" (aka a directional light that rotates around the map and not baked skybox/environment lighting) the sides go back to being almost entirely matte black regardless.

Even if I turn off the directional light and used baked in lighting, it's still very very dark.

Hi! I notice the capsule primitive in the first screenshot also looks quite dark so I suspect now this may be to do with your lighting setup, but if you can attach or link a sample project with a scene that has the issue I'd be happy to check it out.
If there is an issue with the mesh that's being generated I think it's likely that the normals are not correct, so check with a tool that visualises normals to see if they are correct. Currently the vertex normals are calculated in HexChunk.GenerateMesh() by calling Mesh.RecalculateNormals(), but if that isn't calculating them correctly, that would be the place to look in the code to set up something different.

Regarding the lighting, "Scene Lighting" is just a setting for how you view the scene in the editor so won't affect play mode. If all you want is to do is increase the ambient light level, the easiest way is to change Environment Lighting to a solid colour instead of Skybox and the set the colour of that. Check out the Unity docs on Ambient light and the lighting window for more info.

Luckily, this has been resolved - the problem was that my directional light was too far away. After moving things in my scene and re-checking my lighting, everything looks perfect. Looks like this was entirely user error. Thank you!


Add a command line to list the things that are want'd

The default set of want's can be hard to figure out short of letting everything build. Is there scope for having a flag to say what they are?

There is scope for listing the things that are wantd, but I can't see any way of finding the things that are action . needd, since they can put arbitrary actions in between. I suspect simple builds grep want will be enough, and for complex builds they are going to be using plenty of action. I could run and stop at the first action, but that's necessarily approximate as people can do action $ need xs >> need ys. Since anything I do will be necessarily approximate, better to do nothing.


The templates should have at least one simple route and controller, like 'Hello World'.

Feature Summary
Mongoose should have at least one simple route and controller, like 'Hello World'.
Detailed Solution
Mongoose should have at least one simple route and controller, like 'Hello World'.
Motivation and Goals
No response
Alternatives and Considerations
No response
Additional Context
No response
Compliance Checklist

[X] I have checked for similar feature requests and found none.
[X] I have explained the feature with enough detail for it to be understood.
[X] I have provided a clear rationale for why this feature should be implemented.

JS-MongoDB-Prisma-NoAuth-Template already taken

Js-PostgreSql-Prisma-noAuth For @abdinasir-Tman and he completed

JS-MySQL-Prisma-NoAuth-Template already taken @Omar-Tood

JS-PostgreSQL-Sequelize-NoAuth-Template already teken by @Omar-Tood

JS-MongoDB-TypeORM-NoAuth-Template already taken by @Omar-Tood

JS-MySQL-TypeORM-NoAuth-Template already taken by @Omar-Tood

JS-MySQL-Prisma-NoAuth-Template already taken by @miirshe

JS-MySQL-Sequelize-NoAuth-Template already taken by @miirshe

JS-PostgreSQL-TypeORM-Auth-Template already taken by @miirshe

JS-PostgreSQL-TypeORM-NoAuth-Template already taken by @miirshe

completed this issues with @abdinasir-Tman , @Omar-Tood & @miirshe . thanks engineers for your effort.

completed this issues with @abdinasir-Tman , @Omar-Tood & @miirshe . thanks engineers for your effort.

Thanks engr Sharafdin


Maven builds bad jar on 64-bit PC; fine on 64-bit MacBook

Lost of testing against the same codebase on both a PC and a Mac prove that a jar built on the pc with mvn clean install fails to honor a run-time unit test with a NoClassDefFoundError. Same condition if that jar is moved from the pc to a project that uses it on the mac (BacksideServletKS). Same failure.
On the Mac, mvn clean install runs all unit tests. That jar, in BacksideServlet, runs fine.
Something about building on the PC.

Seems related to https://issues.apache.org/jira/browse/SUREFIRE-1198


This code works but the Bot does not.

I followed all the steps above and created the Web Bot. When I test the bot online in Web Chat it gives me the following error:"Sorry, my bot code is having issue". I have been reading on Stack Overflow, GitHub, and some other websites. No luck yet.
Can anyone help me with this?

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

ID: 3041fcf6-3b37-8d88-4d16-73ad0f841b78
Version Independent ID: 76c146ee-7c51-9486-9a76-cac90ca9b674
Content: LUIS and QnAMaker - Bot Integration - Azure Cognitive Services
Content Source: articles/cognitive-services/QnAMaker/Tutorials/integrate-qnamaker-luis.md
Service: cognitive-services
GitHub Login: @diberry
Microsoft Alias: diberry

@Charlie-Chat-Bot Thank you for submitting an issue.
Debugging the bot depends on how comfortable you are with Visual Studio compared to Kudu. If you are comfortable debugging in Visual Studio, download the bot code from the ABS build page and the bot emulator. Make sure to download the emulator that works with your version of the SDK of the bot.
If you are more comfortable working with the app service editor (online code editor), use the top toolbar to find and open the Kudu console. Open the LogFiles directory, then look through the various log files.
#in-progress

Thanks @diberry. Much Appreciated.
I've never worked with the emulator. Does it show what part of the code caused the error? I am looking at the LogFiles right now. They don't seem to be very straightforward in terms of debugging and narrowing down the issue.

#please-close

@Charlie-Chat-Bot We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Use a real database for storing instance data

Currently all data for the registry is stored in an in-memory database. Because the latest changes to the data model introduced a need for persistent storage, we have to integrate a real database.
This includes:

[x] Decide which DB technology to use
[ ] Find a suiting docker image and modify the build.sbt to use this as a base image
[x] Implement a suiting data-access-object for the application (must implement this trait)

Closed with #54 , thanks @sami-cseseu :+1:


Update Pages “home”

Automatically generated by Netlify CMS

👷 Deploy Preview for enchanting-chaja-c384e5 processing.

Name
Link

🔨 Latest commit
c2d3ee32a0c28794da879bff6ba1055d708672b6

🔍 Latest deploy log
https://app.netlify.com/sites/enchanting-chaja-c384e5/deploys/66d3851628568500088b7211


Add condition based MetodFilter

This MR is the first fragment of #395 to port to the trunk. Here I extend MethodFilter with possibility to use condition under the hood to ignore situations, where method is not ready and condition is false. This has the caveats that resulting filter is single_caller so both versions should coexistence.

A remark to remember is that the usage of validate_arguments is not possible in MethodFilter, because this feature cause blocking of method, if the condition is not fulfilled, what cause the blocking of the calling transaction.


Feat/aws provider

Add AWS terraform support

Reviewed and approved. Thanks for the effort of integration in the project coding patterns. :+1:


Forms content not working properly

This is a placeholder to discover forms that appear across the site and create additional stories as needed to address those forms.  Acceptance criteria are only the identification of those forms and creating stories for them.
Examples:

Find us form on homepage

Several forms in the contact section of the site such as:

https://www.stewart.com/en.html
https://www.stewart.com/en/about-stewart/supplier-diversity-at-stewart.html
https://www.stewart.com/en/agent-verification.html
https://www.stewart.com/en/contact-us/contact-customer-relations.html
https://www.stewart.com/en/contact-us/contact-information-technology-security.html
https://www.stewart.com/en/contact-us/customer-service-inquiries-and-complaints.html
https://www.stewart.com/en/contact-us/submit-a-claim.html
https://www.stewart.com/en/contact-us/submit-a-claim1.html
https://www.stewart.com/en/cpl-form.html
https://www.stewart.com/en/deed-documentary-stamps.html

There are also quite a few under quick links as well.

Stewart - Forms List.xlsx

superseded by other forms issues.


Get a better cert for material.angular.io

Bug, feature request, or proposal:
The cert used by material.angular.io is being flagged as suspicious by BlueCoat because it also validates a bunch of junk domains.  Can you get a let's encrypt or whatever?  I can't access the site from work.

This should be fixed once some changes propagate through Firebase Hosting's system (within a few hours).

Closing this as resolved. Thanks @mbleigh!


[Object object] in auto-updater section of settings

Of course, of all things, the auto-updater is showing bugs. Need to see why [Object object] is showing in there.

Can't repro this anymore. Closing for now.

I'm seeing it this evening:

error | browser |   | Unhandled Rejection at: Promise [object Promise] reason: Error: net::ERR_FAILED | 2020-05-19T04:11:50.260Z
-- | -- | -- | -- | --
error | browser |   | [AUTO-UPDATE] error: Error: net::ERR_FAILED | 2020-05-19T04:11:50.260Z
info | browser |   | [AUTO-UPDATE] Checking for a new version. | 2020-05-19T04:11:50.259Z

That actually looks like correct behavior. Connection failed, maybe bad network or github downtime


Feature Request Bring back gimbal stabilisation feature for servo gimbals

If I understand things correctly, before #5389 the vmount module (called gimbal at the time) was used to stabilize a gimbal, and now it is used for passthrough control of gimbals (now including Mavlink gimbals). The stabilization code is still in there, but the only way I can see to activate it is to through MAV_CMD_DO_MOUNT_CONFIGURE.
I'm interested in this module for use with a servo gimbal. Another issue for that application is that the default output range is 360 degrees; it would be nice if that was adjustable without having to edit the mixers so that stabilization roughly works without too much effort. The Ardupilot implementation of this feature has the PWM limits and the angle limits adjustable from the GCS, but that's probably going a bit far here.
I propose adding a parameter MNT_STABILIZE to control whether stabilization is on or off by default, and MNT_RANGE_PITCH, MNT_RANGE_ROLL, and MNT_RANGE_YAW to set the output range. Does that seem reasonable and would you accept a PR?

Sounds reasonable to me if you're able to implement and test the PR. Once the configuration is exposed as params the last step of making a gui to edit them in QGC is pretty easy.

Implemented in #8149


CI is broken

See https://github.com/openzim/phet/actions/workflows/ci.yml
Should be green

Fixed by #150


Apply common codestyle to client

This is a step to move client/ to src/, furthermore joining what was three different repos before.
I tried to minimize the amount of changes here, so there is still client/.eslintrc.cjs, and still a separate package.json.

finally!


Disappearing recipes

Since the update into .7.2v several previously working recipes, such as those used with a furnace (including all forms of stones so far encountered) are not registered, and are not recognized by the NEI nor the furnace itself.

would need an list of these "Disappearing" recipes. This is due to changing code constantly and sometimes i accidentally delete things without meaning too.

This issue / recipes will be fixed within the next release of the modpack.
I Have fixed Cobble - > Stone Smelting, If there is anything else, feel free to open another issue to let me know of more broken recipes