UUID support in URLs

Thanks for the good extension that helps a lot!
I have problems using it with Flask-UUID extension and URLs that have UUIDs inside. Is it possible to fix this? Providing stack trace below:
File "..prog_path/e_venv/lib/python2.7/site-packages/flask/app.py", line 1997, in __call__
return self.wsgi_app(environ, start_response)
File "..prog_path/e_venv/lib/python2.7/site-packages/flask/app.py", line 1985, in wsgi_app
response = self.handle_exception(e)
File "..prog_path/e_venv/lib/python2.7/site-packages/flask/app.py", line 1540, in handle_exception
reraise(exc_type, exc_value, tb)
File "..prog_path/e_venv/lib/python2.7/site-packages/flask/app.py", line 1982, in wsgi_app
response = self.full_dispatch_request()
File "..prog_path/e_venv/lib/python2.7/site-packages/flask/app.py", line 1615, in full_dispatch_request
return self.finalize_request(rv)
File "..prog_path/e_venv/lib/python2.7/site-packages/flask/app.py", line 1632, in finalize_request
response = self.process_response(response)
File "..prog_path/e_venv/lib/python2.7/site-packages/flask/app.py", line 1856, in process_response
response = handler(response)
File "..prog_path/e_venv/lib/python2.7/site-packages/flask_debugtoolbar/__init__.py", line 223, in process_response
toolbar_html = toolbar.render_toolbar()
File "..prog_path/e_venv/lib/python2.7/site-packages/flask_debugtoolbar/toolbar.py", line 46, in render_toolbar
return template.render(**context)
File "..prog_path/e_venv/lib/python2.7/site-packages/jinja2/environment.py", line 1008, in render
return self.environment.handle_exception(exc_info, True)
File "..prog_path/e_venv/lib/python2.7/site-packages/jinja2/environment.py", line 780, in handle_exception
reraise(exc_type, exc_value, tb)
File "..prog_path/e_venv/lib/python2.7/site-packages/flask_debugtoolbar/templates/base.html", line 50, in top-level template code
{{ panel.content()|safe }}
File "..prog_path/e_venv/lib/python2.7/site-packages/flask_debugtoolbar/panels/sqlalchemy.py", line 122, in content
'signed_query': dump_query(query.statement, query.parameters),
File "..prog_path/e_venv/lib/python2.7/site-packages/flask_debugtoolbar/panels/sqlalchemy.py", line 34, in dump_query
return query_signer().dumps([statement, params])
File "..prog_path/e_venv/lib/python2.7/site-packages/itsdangerous.py", line 565, in dumps
payload = want_bytes(self.dump_payload(obj))
File "..prog_path/e_venv/lib/python2.7/site-packages/itsdangerous.py", line 847, in dump_payload
json = super(URLSafeSerializerMixin, self).dump_payload(obj)
File "..prog_path/e_venv/lib/python2.7/site-packages/itsdangerous.py", line 550, in dump_payload
return want_bytes(self.serializer.dumps(obj))
File "..prog_path/e_venv/lib/python2.7/site-packages/itsdangerous.py", line 51, in dumps
return json.dumps(obj, separators=(',', ':'))
File "/usr/lib64/python2.7/json/__init__.py", line 251, in dumps
sort_keys=sort_keys, **kw).encode(obj)
File "/usr/lib64/python2.7/json/encoder.py", line 207, in encode
chunks = self.iterencode(o, _one_shot=True)
File "/usr/lib64/python2.7/json/encoder.py", line 270, in iterencode
return _iterencode(o, 0)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xe8 in position 0: invalid continuation byte

The stack trace is from the SQLAlchemy panel, so I think the issue is with serializing one of your SQL query parameters, not necessarily with the URL.
What parameters are you passing to the SQL query? Also, what version of the extensions are you using?

I have some models with UUID as their primary key. I use UUID type from SQLAlchemy-Utils package. Endpoints that uses UUID in URL have queries by UUID from the tables.
Versions of packages that may be interesting (actually there is more stuff like redis, marshmallow, etc.):
Flask==0.12.1
Flask-DebugToolbar==0.10.1
Flask-SQLAlchemy==2.2
Flask-UUID==0.2
SQLAlchemy==1.1.9
SQLAlchemy-Utils==0.32.14

You are right, the real problem is random UUIDs that are serialized to strings and inserted to queries. As a result such strings contain invalid utf-8 characters. Below is the example:
[
   u'SELECT client.id AS client_id, client.name AS client_name \nFROM local_client_on_pc \nWHERE local_client_on_pc.id = %s',
   ('s\xa7Gf\x0f\xadEL\x87\xef{$ya2t')
]

Now I'm using toolbar with sqlalchemy panel disabled. Why debug toolbar tries to dump list with query and parameters to json?


Upload api success but not return some metadata.

I follow the topic here: https://dev.onedrive.com/items/upload_put.htm, and execute a simple item upload like:
Request:
Request<EMAIL_ADDRESS>Request Method:PUT
Request Headers
Authorization:bearer my_token
Content-Type:image/png
Response:
HTTP/1.1 201 Created
Content-Type: application/json
{
"id": "1C6546CD87472073!348",
"name": "generics2.png",
"size": 10191,
"file": { }
...
}
Everything works fine but the response metadata was missing something, just like "image":{"height":287,"width":765}  and "photo":{"takenDateTime":"2017-05-23T07:19:16.957Z"}.
So, I execute a get item request and try to get the correct metadata:
Request
Request URL:https://api.onedrive.com/v1.0/drive/items/1C6546CD87472073!348
Request Method:GET
Request Headers
Authorization:bearer my_token
But it also didn't return image and photo tag, similar situation in mp3 file and didn't return audio tag.
After a long try, I found that if we delay a period(about few seconds) before execute the get item request, it works and return the correct image and photo tag. So, my question is: How can I fix this issue? Is there OneDrive server need some time to processing image data？
Looking forward to your reply! Thanks!

This is actually by design - in order to ensure uploads complete as fast as possible the process that extracts image metadata is run asynchronously. As a result, it can take a few seconds for the associated metadata to appear.


write-flexpr-xml/content doesn't allow specifying the root element

write-flexpr-xml/content is a useful shortcut, but it doesn't allow specifying the root element like flexpr->xexpr does. I'd like to be able to do this:
(write-flexpr-xml/content (hasheq 'foo 1 'bar 2) #:root 'BRAAAAAAINS)

(Note: I have a patch for this, but won't be able to submit it as a PR for a day or two)

That was a silly mistake. I'd originally defined this as a simple compose, which did handle this for flexpr->xml. Then I remembered the optional out arg for write-xml/content, stopped using compose ... and in the process forgot about flexpr->xexpr. Sigh.
Does your patch fix the same issue with display-flexpr-xml/content?
If still convenient for you to make the PR in a day or two, I'm happy to take that. Otherwise let me know and I'll fix myself. Either way -- thanks!

My new job is quite stringent about software licensing, so in order for me to submit the patch I'd have to add "Google Inc." to the list of copyright holders in the project license. If that's alright with you I'll open a PR, but otherwise I'll leave it up to you.

Although I'm not necessarily opposed to that, I think in this case it's simpler for me to make the change, which I just pushed. Thanks again for reporting this!


Description When creating a user, the built-in text in the nickname text box is not fully displayed

新建用户，昵称文本框内置文字显示不全

it is fixed in pr  #817

I will take a check the inpu style with design


Do not return an error in odo analyze if current directory contains an invalid Devfile

What type of PR is this:
/kind bug
What does this PR do / why we need it:
Which issue(s) this PR fixes:
Fixes #6683
PR acceptance criteria:

[x] Unit test

[ ] Integration test

[ ] Documentation

How to test changes / Special notes to the reviewer:
See repro steps in #6683

  [FAILED] Timed out after 420.001s.
  Expected
      <string>:   __
       /  \__     Developing using the "rrnylj" Devfile
       \__/  \    Namespace: cmd-dev-test600thr
       /  \__/    odo version: v3.11.0
       \__/

      â†ª Running on the cluster in Dev mode
       â€¢  Waiting for Kubernetes resources  ...
       âš   Pod is Pending
       âš   0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.
       âš   0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.
       âš   AttachVolume.Attach failed for volume "pvc-87a9ce7b-78c7-4e7d-8f3e-8c126760999b" : timed out waiting for external-attacher of vpc.block.csi.ibm.io CSI driver to attach volume r010-88fdbb0d-b379-4830-a20d-e203d8cb55cb
       âš   Unable to attach or mount volumes: unmounted volumes=[odo-projects], unattached volumes=[odo-shared-data kube-api-access-dnh85 odo-projects]: timed out waiting for the condition
       âš   AttachVolume.Attach failed for volume "pvc-87a9ce7b-78c7-4e7d-8f3e-8c126760999b" : timed out waiting for external-attacher of vpc.block.csi.ibm.io CSI driver to attach volume r010-88fdbb0d-b379-4830-a20d-e203d8cb55cb
       âš   Unable to attach or mount volumes: unmounted volumes=[odo-projects], unattached volumes=[odo-projects odo-shared-data kube-api-access-dnh85]: timed out waiting for the condition
       âš   AttachVolume.Attach failed for volume "pvc-87a9ce7b-78c7-4e7d-8f3e-8c126760999b" : timed out waiting for external-attacher of vpc.block.csi.ibm.io CSI driver to attach volume r010-88fdbb0d-b379-4830-a20d-e203d8cb55cb

  to contain substring
      <string>: [Ctrl+c] - Exit
  In [BeforeEach] at: /go/odo_1/tests/helper/helper_run.go:54 @ 06/21/23 20:51:16.584
...
Summarizing 1 Failure:
  [FAIL] odo dev command tests when a component is bootstrapped when odo dev is executed and Ephemeral is set to false [BeforeEach] when stopping odo dev normally should have deleted all resources before returning
  /go/odo_1/tests/helper/helper_run.go:54

Ran 475 of 918 Specs in 1633.089 seconds
FAIL! -- 474 Passed | 1 Failed | 0 Pending | 443 Skipped

Storage issues on OpenShift - reported in https://github.com/redhat-developer/odo/issues/6894
/override OpenShift-Integration-tests/OpenShift-Integration-tests

  [FAILED] Timed out after 420.012s.
  Expected
      <string>:   __
       /  \__     Developing using the "mmwtez" Devfile
       \__/  \    Namespace: cmd-dev-test804mwc
       /  \__/    odo version: v3.11.0
       \__/

      - Running on the cluster in Dev mode
       -  Waiting for Kubernetes resources  ...
       !  0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.
       !  Pod is Pending
       !  0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.
       !  AttachVolume.Attach failed for volume "pvc-8df539bb-0904-43c1-930c-b99a766616af" : timed out waiting for external-attacher of vpc.block.csi.ibm.io CSI driver to attach volume r010-cd42c6c9-6e7b-4d3a-88a6-29444ea32fd3
       !  AttachVolume.Attach failed for volume "pvc-c6e0c891-5251-4abf-84dc-298f7ada8405" : timed out waiting for external-attacher of vpc.block.csi.ibm.io CSI driver to attach volume r010-302bd738-ecfa-492e-89ee-05882a815272
       !  AttachVolume.Attach failed for volume "pvc-7f697659-8dde-4386-a2f8-f4f1f686ca79" : timed out waiting for external-attacher of vpc.block.csi.ibm.io CSI driver to attach volume r010-eb0a1eab-cd3a-4527-a37a-3c607e251ec7
       !  Unable to attach or mount volumes: unmounted volumes=[auto-pvc-automount-readonly-pvc auto-pvc-automount-default-pvc auto-pvc-automount-mount-path-pvc], unattached volumes=[auto-cm-automount-mount-path-configmap auto-secret-automount-access-mode-secret auto-cm-automount-default-configmap auto-secret-automount-mount-path-secret auto-pvc-automount-readonly-pvc auto-pvc-automount-default-pvc auto-secret-automount-access-mode-subpath-secret auto-cm-automount-access-mode-configmap-decimal auto-cm-automount-subpath-configmap auto-cm-automount-access-mode-configmap auto-secret-automount-default-secret odo-projects auto-cm-automount-access-mode-subpath-configmap kube-api-access-qkh7p odo-shared-data auto-secret-automount-subpath-secret auto-pvc-automount-mount-path-pvc]: timed out waiting for the condition
       !  AttachVolume.Attach failed for volume "pvc-8df539bb-0904-43c1-930c-b99a766616af" : timed out waiting for external-attacher of vpc.block.csi.ibm.io CSI driver to attach volume r010-cd42c6c9-6e7b-4d3a-88a6-29444ea32fd3
       !  AttachVolume.Attach failed for volume "pvc-c6e0c891-5251-4abf-84dc-298f7ada8405" : timed out waiting for external-attacher of vpc.block.csi.ibm.io CSI driver to attach volume r010-302bd738-ecfa-492e-89ee-05882a815272
       !  AttachVolume.Attach failed for volume "pvc-7f697659-8dde-4386-a2f8-f4f1f686ca79" : timed out waiting for external-attacher of vpc.block.csi.ibm.io CSI driver to attach volume r010-eb0a1eab-cd3a-4527-a37a-3c607e251ec7
       !  Unable to attach or mount volumes: unmounted volumes=[auto-pvc-automount-mount-path-pvc auto-pvc-automount-readonly-pvc auto-pvc-automount-default-pvc], unattached volumes=[auto-cm-automount-default-configmap auto-cm-automount-access-mode-configmap-decimal auto-secret-automount-default-secret auto-cm-automount-subpath-configmap odo-shared-data auto-pvc-automount-mount-path-pvc auto-secret-automount-subpath-secret auto-pvc-automount-readonly-pvc auto-secret-automount-mount-path-secret auto-cm-automount-access-mode-configmap auto-pvc-automount-default-pvc auto-cm-automount-mount-path-configmap kube-api-access-qkh7p auto-secret-automount-access-mode-secret odo-projects auto-secret-automount-access-mode-subpath-secret auto-cm-automount-access-mode-subpath-configmap]: timed out waiting for the condition
       !  AttachVolume.Attach failed for volume "pvc-8df539bb-0904-43c1-930c-b99a766616af" : timed out waiting for external-attacher of vpc.block.csi.ibm.io CSI driver to attach volume r010-cd42c6c9-6e7b-4d3a-88a6-29444ea32fd3
       !  AttachVolume.Attach failed for volume "pvc-7f697659-8dde-4386-a2f8-f4f1f686ca79" : timed out waiting for external-attacher of vpc.block.csi.ibm.io CSI driver to attach volume r010-eb...

  Gomega truncated this representation as it exceeds 'format.MaxLength'.
  Consider having the object provide a custom 'GomegaStringer' representation
  or adjust the parameters in Gomega's 'format' package.

  Learn more here: https://onsi.github.io/gomega/#adjusting-output

  to contain substring
      <string>: [Ctrl+c] - Exit
  In [BeforeEach] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4213/tests/helper/helper_run.go:54 @ 06/21/23 13:50:13.872
...

Summarizing 3 Failures:
  [FAIL] odo dev command tests multiple dev sessions with different project are running on same platform (podman=false), same port when odo dev session is run for nodejs component when odo dev session is run for go project on the same port but different address when go and nodejs files are modified [It] should be possible to access both the projects on same address and port
  C:/Users/Administrator.ANSIBLE-TEST-VS/4213/tests/helper/helper_http.go:52
  [FAIL] odo dev command tests when a component is bootstrapped when Automount volumes are present in the namespace when odo dev is executed [BeforeEach] should mount the volumes
  C:/Users/Administrator.ANSIBLE-TEST-VS/4213/tests/helper/helper_run.go:54
  [FAIL] odo devfile deploy command tests deploying devfile with long-running exec when Automount volumes are present in the namespace [It] should mount the volumes
  C:/Users/Administrator.ANSIBLE-TEST-VS/4213/tests/helper/helper_cmd_wrapper.go:120

Ran 459 of 918 Specs in 2037.576 seconds
FAIL! -- 456 Passed | 3 Failed | 0 Pending | 459 Skipped

Storage issues on OpenShift - reported in https://github.com/redhat-developer/odo/issues/6894
/override windows-integration-test/Windows-test


ci: automatically run robot regression and negative tests daily and weekly

Which issue(s) this PR fixes:

Issue https://github.com/longhorn/longhorn/issues/9679
What this PR does / why we need it:
ci: automatically run robot regression and negative tests daily and weekly
Special notes for your reviewer:
Additional documentation or context

Summary by CodeRabbit

New Features

Updated testing framework from pytest to robot framework, affecting command-line argument handling.

Bug Fixes

Enhanced error handling and resource cleanup during the build process.

Chores

Maintained existing structure for backup store configurations and test execution flow.

@Mergify backport v1.7.x v1.6.x


Page refresh resets status from 'Latest/Ready' to 'Live'

When a user refreshes the page while the status is set to "Latest/Ready," the status resets back to "Live."
Steps to reproduce the behavior:

Go to 'https://functional-adminportal-test.azurewebsites.net/dynamic/TestModule/mondayTest-tables'
Click on the form status and set it to 'latest'/Ready
Afterwards, refresh the page
Actual Results: The status resets back to 'live' after the page is refreshed

Expected behavior
The status should remain on the selected stats after the page is refreshed
See attached video: https://jam.dev/c/bce2cf66-24d0-4060-af21-5e0e9aa74bf5
Old changes: https://jam.dev/c/e5d53fc6-78b3-4323-b88d-28218ad5202c

Hi @hlayisanimazuze. It's fixed, please check


Focus first child from no focus.

What does the pull request do?
If there is no currently focused element when tab navigation occurs, move focus from the root.
Fixed issues
Fixes #11290

You can test this PR using the following package version. 11.0.999-cibuild0035167-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]


No an issue exactly ;-)

This is what I came up with this modified project:
https://youtu.be/CQTEDK5EOqk
Ultracompact size: 95x30x10mm enclosure.
Hope you like it.

Nice!
More pictures?

OK, more pictures!
One thing I want to ask you. Would you help me to make the MP3 player function work in this revision?
I have microSD card on my PCB, so it would be nice if it can be used.
I can ship one assembled unit to you so you can work on it.
RDS
Simeon

You got a deal!

Great, please let me know your shipping address on my email<EMAIL_ADDRESS>


Address new custom build logic issues

Resolves several issues introduced during the addition of AAB support to the Android export workflow:

Commit e06301c resolves issue https://github.com/godotengine/godot/issues/42793
Commit e79192e resolves issue https://github.com/godotengine/godot/issues/42795
Commit 82490f7 resolves issue https://github.com/godotengine/godot/issues/42792

Thanks!


Is MetroWindow Per-Monitor DPI-Aware?

Does MetroWindow use Per-Monitor DPI-Aware features provided by Windows 8.1+?
https://msdn.microsoft.com/en-us/library/windows/desktop/ee308410(v=vs.85).aspx
If no: feature request :)
Thanks!

Unfortunately it is not Per-Monitor DPI-Aware. But it would be fine to have built in support. I found a project which adds this functionality to MahApps.Metro: https://github.com/circuitdiagram/CircuitDiagram.DPIWindow

Why was this closed? The DPI helpers were added in .NET 4.6.2. .NET 4.5 apps still need to do this manually.

because you can add DPI awarenes via an app.manifest file. @punker76 linked a repo containing a sample for that.


is mellanox ConnectX-6  supported?

What issue would you like to bring attention to?
na
What is the impact of this issue?
na
Do you have a proposed response or remediation for the issue?
na

It should work.


Question: NER with Spacy

Are there any plans of adding NER capabilities to Spacy soon? Any recommendations on the most modern techniques to do so, if not? (Eg, perhaps using the word vector representation?)

I'm not really happy with any of the existing algorithms, so I've been working on a novel shift-reduce approach. Briefly, where previous work usually encodes the structure into sequence tags, so that a finite-state machine can be used, I think it makes more sense to use a push-down automaton, now that work in parsing with shift-reduce grammars is so well understood.
I'm just starting to get results for this. Currently accuracy is only 77% on OntoNotes, where the Stanford NER system reportedly gets around 84%. I still need to do a lot of bug-fixing and tuning, and I'm not using gazetteers or any semi-supervised learning at the moment.
So, in short: yes, NER is planned, and the bulk of the work is done. It remains to be seen whether my approach will hit comparable accuracy to previous work, but imo it should. Once the accuracy is good, I then need to design and implement the Python API, and write the testing and deployment code. Probably about 1 month all up, given other things I'm working on.

Thanks, that's an interesting approach. Are there any specific papers you recommend for PDA based NER?
Also, are you inviting code/collaboration on this yet?

As far as I know PDA for NER is a new idea, since most of the previous work uses HMMs and CRFs. If it works, I'll write it up.
I need to set up the contributors agreement, but then I could accept contributions. But, I think it's easiest if I do the research parts myself. Collaborating on that gets complicated.
If you want to weigh in on what sort of API you'd like to see though, that would be very welcome.

Ah, I didn't realize it hasn't been tried before - I remember coming across a chinese NER system that used PDAs, but I can't find that paper. Would you be interested in sharing some high level thoughts on the PDA/NER approach that you're taking?
Re: collaborating on the research parts - just an idea - it might be interesting to have a shared ipynb or some such, on one of the github style research collaboration platforms.
Definitely, let me think about the APIs. I've always thought that the GATE or UIMA style, and even the Stanford NER APIs have been super heavy weight.
It would be good to have a visual representation of the parse tree, like NLTKs as this progresses,
(S
  Over/IN
  (NP a/DT cup/NN)
  of/IN
  (NP coffee/NN)
  ,/,
  (NP Mr./NNP Stone/NNP)
  told/VBD
  (NP his/PRP$ story/NN)
  ./.)

Quick update:
This is progressing well: I'm now getting 81% on the OntoNotes WSJ corpus. I expect gazzetteers from Wikidata will bring this in line with current state-of-the-art.
It's hard to say, but this might be ready by the end of April.

NER now included, although the model still needs accuracy improvements. Currently it's getting 82% F on OntoNotes, and 86% on CoNLL '03. State-of-the-art is around 85% and 90% on these benchmarks. Improvements are in the works.

Sweet - is there a pointer on usage?


Refactor the SHOW/SET documentation.

Both SHOW and SET are really single statements which act on the
session (and they are also handled using a single code path in
CockroachDB!), with the exception of SET TRANSACTION which acts on the
current transaction. This patch acknowledges the commonality and
merges the various documentation pages into two more general pages.
Supports the changes in https://github.com/cockroachdb/cockroach/pull/13678.

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/739869692b22f79810e82e5bc37b718301752f75/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/b4f465488d1bffed92880d795895d46a0eca1c0d/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/bd2d8ee8846feebdcfbd0fe2842c043d9f6adc78/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/ca0bea23b043f0ee113634786cf9ec0958d6ac2c/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/98382aaf0900d25851d3c3348d94edf9c55017d9/

Note: I actually think we should merge the SET and SHOW documentation pages into a single page that explains "Session variables", and presents SET and SHOW as the two ways to access them. That would make the navigation even simpler. Let me know if there is interest.

@mjibson @sploiselle can you explain to me how to generate the missing railroad diagrams. I have no clue.

I'm sorry this errors out with:
2017/02/25 22:33:06 rename_table: exit status 1: Error: Unable to access jarfile Railroad.jar

@mjibson ? Is it possible to add a link to this jar file in the wiki page too?

You can find railroad.jar on the cockroach labs google drive. I've created #1124 to track changing the docs build to not require it by default, because this problem comes up a lot.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/afc0499b5a6b2dc96c60afdd274f3f20414925cb/

Review status: 0 of 27 files reviewed at latest revision, 15 unresolved discussions.

learn-cockroachdb-sql.md, line 51 at r1 (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
set-vars.md should have a header in its Examples section that this can link to.

Done.

set-vars.md, line 20 at r1 (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
Is it possible to instead convert this into a railroad diagram like the other SQL statements?

Done.

set-vars.md, line 37 at r1 (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
Notes have specific templates that use HTML formatting, e.g. in this case:
{{site.data.alerts.callout_info}}The SET statement for session settings in unrelated to the other SET TRANSACTION statement.{{site.data.alerts.end}}

Done.

set-vars.md, line 42 at r1 (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
If this is the first mention of SHOW in this doc, it needs some explanation as to why you would use it.
Also, I think it would be a little more clear to move | Can be viewed with [SHOW](show-vars.html)? | to the last column.

Done.

set-vars.md, line 56 at r1 (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
e.g. ### Set the Session Database followed by a brief description of what that does ("defaults to using the database as the qualified name" or something to that effect).

Done.

set-vars.md, line 85 at r1 (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
e.g. ### Set the Search Path...with an explanation of why you would do that or what it accomplishes.

Done. Note that these are examples of the syntax, not sections where individual variables are explained/motivated. The table above serves that purpose.

set-vars.md, line 99 at r1 (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
Seems like this should just be its own document, or could maybe be consolidated into this document by generating railroad diagrams.

Yes railroad diagrams probably would do the trick.

show-vars.md, line 18 at r1 (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
Would ideally be a railroad diagram.

Done.

show-vars.md, line 37 at r1 (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
Wrap in note formatting {{site.data.alerts.callout_info}}{{site.data.alerts.end}} and maybe shorten to provide only one example of the type of statement you're referring to.

Done.

show-vars.md, line 49 at r1 (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
Same comment as with SHOW in set-vars.md, where we need an explanation of SET and this column might be better suited for the final column.

Done.

show-vars.md, line 66 at r1 (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
Examples need H3 headers and explanations as to what they accomplish.

Done.

transactions.md, line 181 at r1 (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
What about them is controlled by those two parameters? Is this a functional grouping in some way?

I do not understand this question.

transactions.md, line 196 at r1 (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
What is the benefit of adding this version of the statement?

That was a mistake; removed.

_data/sidebar_doc.yml, line 194 at r1 (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
I'd rather have this as SET <session variable>

Done.

_data/sidebar_doc.yml, line 200 at r1 (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
Same as above but SHOW <session variable>

Done.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/b5467bf5a4dc4e1354834e0802442cd750596910/

Needed for https://github.com/cockroachdb/cockroach/pull/13540
I probably need to rebase this

Rebasaed

@benesch @sploiselle can you give this another look? I'm pretty confident I had rebased successfully yesterday already. This commit ecab285e48c1950f611e6d67a59630f4843bae10's parent is f490682c90a287fab0161d44eb46a0ee022b08d3, from last Tuesday. How come is TC still failing?

Oh—you've been rebasing onto the gh-pages branch, haven't you? Sorry!  I've opened #1588 to prove that rebasing on master works; feel free to commandeer that PR or nuke it once it serves its purpose.

Woah thanks Nikhil for pointing me to the master branch! Lemme do that.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/62efd5f20b835b09de61de54b4aa0044cb5f394a/

Ok I fixed the broken link, PTAL

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/8bcf0e39f43578fa24222e730e92c93f61b79156/

Review status: 0 of 30 files reviewed at latest revision, 19 unresolved discussions.

set-vars.md, line 23 at r2 (raw file):
Previously, jseldess wrote…
@knz, these diagrams aren't rendered correctly. I've pulled down your branch to figure it out. Here's what you need to do:

Insert an empty line between the 2 includes.
Regenerate the set_var.html image. cd generate and then go run main.go --filter set_var.

Then view locally to make sure the diagrams look like this:

Done.

show-vars.md, line 19 at r2 (raw file):
Previously, jseldess wrote…
Just as with the diagrams on set_var.md, an empty line needs to be inserted between these two includes.
Also, I think you need to regenerate the diagrams themselves one more time:
cd generate
go run main.go --filter show_var
go run main.go --filter show_all

Done.

show-vars.md, line 28 at r2 (raw file):
Previously, jseldess wrote…
Need a closing backtick (`) after each item in the second column.

Done.

show-vars.md, line 33 at r2 (raw file):
Previously, jseldess wrote…
Unfortunately, this alert needs to be formatted as HTML. As is, it's breaking the table above it. To save time, here's the HTM version for you to use:
{{site.data.alerts.callout_info}}The SHOW statement for session settings is unrelated to the other SHOW statements: SHOW CREATE TABLE, SHOW CREATE VIEW, SHOW USERS, SHOW DATABASES, SHOW COLUMNS, SHOW GRANTS, and SHOW CONSTRAINTS.

Done.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/247413cfaf48cde158fe29f82ba336e5bfe4d109/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/009251f6c0b7917c90f95a402775c283e637a2e9/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/3a0df8bd5a53c3506daf25b5cd55e73c452a0555/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/8faa22d5715ca4580803722b2ed9ecf81ac3324c/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/df46f60441e86c590f9d99be46df2ba3fbe0a0c1/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/4777dd13c11c75f6ce6c7e8269fe687343673dd3/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/1c8f0e41e857a189522ada11fdb23bd07249bad9/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/1af66a1f4bc91d0019d598518d90948c3db7f228/

PTAL - while I was at it I even added two new pages for SET/SHOW CLUSTER SETTING.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/5a9e4ad808bfae24d9ff29f3c3912c8912906a7c/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/dd0a14821ed5be1d2045179b7ad2500b28c7c2f2/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/97443583f8cf25d7822a68a03b00bcfe6bc1e9a3/

Will get to this tonight.

Man––what great work, @knz. I appreciate all the time and attention you pored into this. I have a few quick structural suggestions to align these pages with the rest of our docs.

Review status: 0 of 37 files reviewed at latest revision, 36 unresolved discussions, some commit checks failed.

set-vars.md, line 24 at r3 (raw file):

{% include sql/diagrams/set_var.html %}

The variable name is case insensitive.

I have essentially the same feedback for this page as for SHOW. I would prefer the Parameters section be added directly after the diagram, but in this case with a table expressing something that includes var_value.

show-vars.md, line 21 at r3 (raw file):

The variable name is case insensitive.
It may be enclosed in double quotes; this is useful if the variable name itself contains spaces.

Both of these notes reference the var_name parameter, so I would move them into the Parameters section I suggest a bit lower on the page.

show-vars.md, line 23 at r3 (raw file):

It may be enclosed in double quotes; this is useful if the variable name itself contains spaces.

Special syntax cases supported for compatibility:

These equivalences would be less obtrusive in the Supported variables section.

show-vars.md, line 34 at r3 (raw file):

{{site.data.alerts.callout_info}}The SHOW statement for session settings is unrelated to the other SHOW statements: SHOW CLUSTER SETTING, SHOW CREATE TABLE, SHOW CREATE VIEW, SHOW USERS, SHOW DATABASES, SHOW COLUMNS, SHOW GRANTS, and SHOW CONSTRAINTS.{{site.data.alerts.end}}

## Supported variables

To make this more consistent with the other SQL documentation, this should immediately follow the diagram itself.  I'd prefer it use the same format as the rest of the documentation, too, though you'll need to add some text for it to make sense. I suggest something like:
## Parameters

The `SHOW <session variable>` statement's only parameters is `var_name`.

### Support `var_name` Values

Comments from Reviewable

Review status: 0 of 37 files reviewed at latest revision, 36 unresolved discussions, some commit checks failed.

set-cluster-setting.md, line 17 at r3 (raw file):
Previously, jseldess wrote…
set-var.html should be set-vars.html

Done.

set-cluster-setting.md, line 27 at r3 (raw file):
Previously, jseldess wrote…
Might want to add the detail that the variable name is case insensitive.

Done.

set-cluster-setting.md, line 31 at r3 (raw file):
Previously, jseldess wrote…
capitalization nit: Change the Default Distributed Execution Paremeter

I wasn't sure. Thanks for clarifying.

set-vars.md, line 24 at r3 (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
I have essentially the same feedback for this page as for SHOW. I would prefer the Parameters section be added directly after the diagram, but in this case with a table expressing something that includes var_value.

Done.

set-vars.md, line 33 at r3 (raw file):
Previously, jseldess wrote…
The last  tag needs to be . As is, it's messing up the styling of the table below.

Done.

set-vars.md, line 39 at r3 (raw file):
Previously, jseldess wrote…
Found the styling issue (see note above about the  tag), so the change suggested here probably isn't required, but still good to do for the sake of consistency.

Done.

set-vars.md, line 41 at r3 (raw file):
Previously, jseldess wrote…
I think it's unnecessary to quote the values in the Initial Values column.

Done.

set-vars.md, line 91 at r3 (raw file):
Previously, jseldess wrote…
Is using a list applicable to anything but search_path? I supposed additional such variable may be added in the future...
In any case, I might just cut everything after the comma.

Done.
(Yes we have an incoming feature set trace which is likely to take a list too.)

show-cluster-setting.md, line 9 at r3 (raw file):
Previously, jseldess wrote…

These can also be configured...

Done.

show-cluster-setting.md, line 22 at r3 (raw file):
Previously, jseldess wrote…
I'd move this into the description of the any_name parameter.

Done.

show-cluster-setting.md, line 24 at r3 (raw file):
Previously, jseldess wrote…
show-var.html should be show-vars.html

Done.

show-cluster-setting.md, line 34 at r3 (raw file):
Previously, jseldess wrote…
capitalization nit: Showing the Value of a Single Cluster Setting

Done.

show-cluster-setting.md, line 62 at r3 (raw file):
Previously, jseldess wrote…
capitalization nit: Showing the Value of All Cluster Settings

Done.

show-cluster-setting.md, line 82 at r3 (raw file):
Previously, jseldess wrote…
show-var.html should be show-vars.html

Done.

show-vars.md, line 21 at r3 (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
Both of these notes reference the var_name parameter, so I would move them into the Parameters section I suggest a bit lower on the page.

Done.

show-vars.md, line 23 at r3 (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
These equivalences would be less obtrusive in the Supported variables section.

Done.

show-vars.md, line 34 at r3 (raw file):
Previously, sploiselle (Sean Loiselle) wrote…
To make this more consistent with the other SQL documentation, this should immediately follow the diagram itself.  I'd prefer it use the same format as the rest of the documentation, too, though you'll need to add some text for it to make sense. I suggest something like:
## Parameters

The `SHOW <session variable>` statement's only parameters is `var_name`.

### Support `var_name` Values

Done.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/9fef2c1cfbb478525cbaf0fc5604d60d1fbda68b/

Review status: 0 of 37 files reviewed at latest revision, 36 unresolved discussions, some commit checks pending.

set-vars.md, line 99 at r1 (raw file):
Previously, knz (kena) wrote…
Yes railroad diagrams probably would do the trick.

To react further on this comment specifically: the next PR on this page will address the change in 1.1 which makes "SET TIME ZONE" truly equivalent to SET "time zone", and this section can be removed entirely (and replaced by a mere example).

Comments from Reviewable

Review status: 0 of 37 files reviewed at latest revision, 36 unresolved discussions, all commit checks successful.

Comments from Reviewable

Off we go then :smile_cat:
Thank you so much for the sweet learning experience!


Text can not be read

I went to http://demo.convos.by/ registered and could not continue.
I only see several text slapped one over each other.

This happens on Ubuntu 16.04 Firefox 49.

Oh! That's just awful. I will download and test in Firefox some time later this week.

Sorry, but I'm unable to reproduce this bug. Looks fine to me.


datatypes: project-profile: refine function source list

This is kinda related to https://github.com/ossf/fuzz-introspector/issues/794 -- in this case we will exclude more functions in the stats table, but in particular the number of functions with code coverage. This will help a lot for Python projects, where currently builtin's are included in the list as well as functions from third-party dependencies that not really part of a given package's source.


[BUG]: Mandate Request Validation Missing

Bug Description
Currently payment_method_data and off_session can be passed in the same request, which should not be the case as both these are mutually exclusive, same goes for the combination of setup_future_usage and off_session.
Expected Behavior
A Bad Request error should be thrown if any of the unwanted combination is sent in request.
Actual Behavior
There is no check and the request went to get processed in general.
Steps To Reproduce
Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.

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

Context For The Bug
No response
Environment
Are you using hyperswitch hosted version? Yes/No
If yes, please provide the value of the x-request-id response header to help us debug your issue.
If not (or if building/running locally), please provide the following details:

Operating System or Linux distribution:
Rust version (output of rustc --version): ``
App version (output of cargo r --features vergen -- --version): ``

Have you spent some time checking if this bug has been raised before?

[X] I checked and didn't find a similar issue

Have you read the Contributing Guidelines?

[X] I have read the Contributing Guidelines

Are you willing to submit a PR?
None

Can i take up this issue?

Hey @shivam-jainn , Surely will be happy to assign it to you.
Let us know if any clarity is required regarding the reported issue


Stable savers do not appear

Add USDC to savers.
Go to savers screen, it does not appear.
Upon the load of the saver's screen, the following endpoint is used to have a look at savings positions for native coins.
https://thornode.ninerealms.com/thorchain/pool/{asset{/saver/{address} which returns a subset of https://thornode.ninerealms.com/thorchain/pool/{asset}savers
While native coins are queried, stablecoins are not.

Only native assets are queried

USDC appears now, not able to see USDT


Cell magic not converting properly when exporting as Python script

With the following cell in notebook,
%%timeit
print('hi')

when we export to Python script, we get:
# To add a new cell, type '# %%'
# To add a new markdown cell, type '# %% [markdown]'
# %%
from IPython import get_ipython

# %%
get_ipython().run_cell_magic('timeit', '', "print('hi')")

Is it possible to convert directly to cell magic (%%timeit) in the interactive Python page instead of this get_ipython() output? It becomes difficult to edit if you use cell magic with larger chunks of code.

Assigning to Ian as he was working on exporting ipynb to python files recently
Also adding this to the milesone (if this gets resolved with the recent changes).
@IanMatthewHuff  please feel free to remove this from the milestone if this will not get addressed.

/verified


Support for MWE Schemes

Hello Team,
We have been trying to add the  support for ngrams and skipgrams into nlcodec. The PR above does the following:

Adds the following schemes : NgramScheme , SkipgramScheme , MWEScheme ( combines both NgramScheme and SkipgramScheme )
Added a list of PMI variants to allow merging of tokens on the basis of the metrics other than freq.

The implementation for the above cannot directly be merged in the code base as the code is not properly factored. However, we would like you to review the code and see how does it align with the purpose of the codec.

Hi @pegasus-lynx  thanks for the pull request.
I will gladly review it, and look forward to merging it.
This week is a little busy one as the ACL is going on ... I will get back to this after a few days.
Thanks again for submitting the PR! Its looking good.

Hey @pegasus-lynx
Sorry for the long delay.
I tried to test these new features. But I am clueless regarding how to use this API.
I need a simple example of how to use ngram, skipgram and MWE.
A simple test case for creating vocab would do; here is an example:
https://github.com/isi-nlp/nlcodec/blob/b99d0239902474c106e354a4ced4b5f763eee83c/tests/test_codec.py#L20-L39
AND/OR  a sample usage e.g. https://github.com/isi-nlp/nlcodec/blob/master/docs/intro.adoc#python-api so we
Thanks.
Once again, I apologize for the delay.

@pegasus-lynx let me know if this is ready for a review!

Hey @thammegowda, sorry for the delay. We have moved in a different direction with this branch. I will close this PR and create a new PR for this. As of now, the SkipScheme has some issues in decoding, so it is still not ready for review.


jupyter not oppening at all

after i started my pod i tried to run jupyter but it is not running. i'm using ubuntu 18.04.

Could you please provide the command line you executed and the output?

nevermind i understood how to use it. i was trying to open jupyter after starting the pod.
thank you

Cool! You could also use snark attach pod_id -L 8888:localhost:8888 after you execute the pod and run jupyter from inside.


Obsolete res (res has newer versions) should be immutable to prevent unexpected change through api

Obsolete res (res has newer versions) should be set immutable on backend to prevent unexpected change through api

@horsburgh @dtarb Currently we allow users to share obsoleted resources. Want to make sure this is indeed what we want while I set immutable to True for obsoleted resources so that obsoleted resources cannot be modified via REST API. Otherwise, if we want to disable sharing of obsoleted resources, I can address it as part of this issue by setting sharable attribute on the resource to False and update Sharing status and disable manage access from landing page for obsoleted resources.

I am going to defer to @horsburgh on this.  I do not want to micromanage or take the time to work through the edge cases involved in the versioning model that was already worked out to respond substantively.

@horsburgh After giving this a bit of more thought, I think current implementation makes sense that allows users to manage access control for obsoleted resources. Since we set immutable flag to True for obsoleted resources, all users with edit and owner privileges are downgraded to VIEW privilege by access control policy, so they cannot really modify obsoleted/immutable resources any way, but they can still add other people access privileges if they want to allow them to view obsoleted resources. This appears to be consistent with our current access control policy. So I will just create a PR for this specific issue to set immutable flag to True for obsoleted resources without touching sharable and manage access control part. We can always create another issue as needed if we decide to change current behavior for managing access control for obsoleted resources.

Ok. I think this may be one of those things where we have to see what users want - or see if we have conflicts and issues. I'm OK with your current plan.

immutable has been set for obsoleted resources, so I am closing this issue.


Inconsistency when value fails type and enum check

Consider this program:
$ cat ~/json-schema-test.py
import jsonschema

schema = {
    'enum': ['3', '5'],
    'type': 'string',
}

failed_validators = {}
for _ in range(100):
    checker = jsonschema.FormatChecker()
    try:
        jsonschema.validate(None, schema, format_checker=checker)
    except jsonschema.exceptions.ValidationError as exc:
        if exc.validator not in failed_validators:
            failed_validators[exc.validator] = 0
        failed_validators[exc.validator] += 1

print(failed_validators)

I would expect it to always fail validating the type of the value rather than iterate over the enum before doing the type check. But if you run it, it sometimes rejects None for having an invalid type and sometimes for not being in the enum list. What's even stranger, it varies across times you execute this script, not within a single execution:
$ for i in {1..10} ; do python3 ~/json-schema-test.py ; done
{'type': 100}
{'type': 100}
{'enum': 100}
{'enum': 100}
{'enum': 100}
{'enum': 100}
{'type': 100}
{'enum': 100}
{'enum': 100}
{'enum': 100}

Version details:
[mfw]$ python3
Python 3.5.3 (default, Apr 28 2018, 10:34:28)
[GCC 4.8.5] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import jsonschema
>>> jsonschema.__version__
'3.0.1'

What makes you expect it to always fail with one or the other?
On Tue, Jun 18, 2019, 14:15 blakehilliard<EMAIL_ADDRESS>wrote:

Consider this program:
$ cat ~/json-schema-test.py
import jsonschema
schema = {
'enum': ['3', '5'],
'type': 'string',
}
failed_validators = {}
for _ in range(100):
checker = jsonschema.FormatChecker()
try:
jsonschema.validate(None, schema, format_checker=checker)
except jsonschema.exceptions.ValidationError as exc:
if exc.validator not in failed_validators:
failed_validators[exc.validator] = 0
failed_validators[exc.validator] += 1
print(failed_validators)
I would expect it to always fail validating the type of the value
rather than iterate over the enum before doing the type check. But if you
run it, it sometimes rejects None for having an invalid type and sometimes
for not being in the enum list. What's even stranger, it varies across
times you execute this script, not within a single execution:
$ for i in {1..10} ; do python3 ~/json-schema-test.py ; done
{'type': 100}
{'type': 100}
{'enum': 100}
{'enum': 100}
{'enum': 100}
{'enum': 100}
{'type': 100}
{'enum': 100}
{'enum': 100}
{'enum': 100}
Version details:
[mfw]$ python3
Python 3.5.3 (default, Apr 28 2018, 10:34:28)
[GCC 4.8.5] on linux
Type "help", "copyright", "credits" or "license" for more information.

import jsonschema
jsonschema.version
'3.0.1'

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Julian/jsonschema/issues/571?email_source=notifications&email_token=AACQQXWX7NF656YNKQQ4VN3P3EQ3NA5CNFSM4HZCTR4KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G2GZ6MA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACQQXSYGRESS77FET4GMH3P3EQ3NANCNFSM4HZCTR4A
.

Getting the type wrong is a more basic type of problem than not being in the enum, therefore it's more helpful for the client to know that's where they messed up.
Performance. It's quicker to check the type than iterate through an enum list.

It sounds like you want to have a look at the documentation on validation
errors.
https://python-jsonschema.readthedocs.io/en/stable/errors/#best-match-and-relevance
On Tue, Jun 18, 2019, 14:35 blakehilliard<EMAIL_ADDRESS>wrote:

Getting the type wrong is a more basic type of problem than not
being in the enum, therefore it's more helpful for the client to know
that's where they messed up.
Performance. It's quicker to check the type than iterate through an
enum list.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Julian/jsonschema/issues/571?email_source=notifications&email_token=AACQQXWYN3HAJAP5NKSFI7DP3ETFJA5CNFSM4HZCTR4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX7R5RA#issuecomment-503258820,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACQQXTUTVNNDSKN6ZTNMVLP3ETFJANCNFSM4HZCTR4A
.

Closing, but happy to see a PR improving the docs if you find anything missing.


  Fidgeting.  I don't see this tekinged, but not sure if I am misspelling it.

I believe it’s derived from mozizi Japanese word for fidget.
 Fidgeting. I don't see this tekinged, but not sure
if I am misspelling it.
—
Reply to this email directly, view it on GitHub
https://github.com/tekinged/missing/issues/517, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF2DJJDZUX6HTLBFH4VQODLZQP3QDAVCNFSM6AAAAABMHM3FHSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ2TMOBRHAYTMOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@Gnalu , can you find a webpage anywhere that shows MOZIZI as a Japanese word? I couldn't find anything like that so I'm not sure that MOZIZI is a Japanese word. I did find mojimoji which can mean fidgeting but that seems too far away from this word.

@ John It also refers to moving to the music. One might say, Ng di kosebakl
ongak e ngii a mla mo ousingesing.
On Fri, Aug 9, 2024 at 8:44 AM John Bent @.***> wrote:

@Gnalu https://github.com/Gnalu , can you find a webpage anywhere that
shows MOZIZI as a Japanese word? I couldn't find anything like that so I'm
not sure that MOZIZI is a Japanese word. I did find mojimoji which can mean
fidgeting but that seems too far away from this word.
—
Reply to this email directly, view it on GitHub
https://github.com/tekinged/missing/issues/517#issuecomment-2276888910,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXYSPXSH4I2TPHQR3JIYWXDZQP7EBAVCNFSM6AAAAABMHM3FHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZWHA4DQOJRGA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Desperately needed - Custom Content Type Grouping

{
"verb": "createContentType",
"group":"Something other than 'Custom Content Types', please. 🙏🏻",
--rest--
}

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

ID: 68267476-ee8d-7b95-446b-711ddb683da2
Version Independent ID: aa099b9d-48db-5513-11c7-32c49a27e5be
Content: Site design JSON schema
Content Source: docs/declarative-customization/site-design-json-schema.md
Product: sharepoint
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

I agree. +1

I suggest heading over to UserVoice and voting on this.
https://sharepoint.uservoice.com/forums/329220-sharepoint-dev-platform/suggestions/36320569-enhance-createcontenttype-with-group-property-to-d


Failure in successive tests when a @ViewScoped bean depends on another @ViewScoped bean

Hello,
When a @ViewScoped bean depends on another @ViewScoped bean, every test after the first one fails.
The failure message for the 3.x line used to be:
WELD-001303: No active contexts for scope type javax.faces.view.ViewScoped

With 4.x the error is more descriptive and pointing to the proposed solution:
IllegalStateException: WELD-000229: Contextual reference of Managed Bean [class ...]
    with qualifiers [@Default @Any @Named] is not valid after
    container 6d8d88ef-461c-47d5-a577-bfefd6d20df1 shutdown

I have traced the reason to the static Map<String, Object> viewMap field of org.jglue.cdiunit.internal.jsf.ViewContext and to the fact that Weld is created and started anew for each test (see org.jglue.cdiunit.CdiRunner methods createTest() and methodBlock()). The problem is that, after the first time a test is run, some view-scoped beans are found in the static map, referring to the old, disposed Weld instance.
The proposed solution is to make the viewMap field non-static because there is no point in sharing a bean instance between runs since container is created anew.

Thanks for the fix @nikospara!

Thank you for a most useful tool :)


Error No X11 DISPLAY variable not set

Hello,
i get this error in github. Can i please help? Thanks you!
@GBIEK ➜ /workspaces/code-examples-java (master ✗) $  /usr/bin/env /opt/java/11.0.14/bin/java -agentlib:jdwp=transport=dt_socket,server=n,suspend=y,address=localhost:46125 @/tmp/cp_5qngrjy5gj0th2nhtjgsk18jn.argfile com.docusign.App
14:19:17.952 [main] INFO com.docusign.App - Retrieving the default initialize context
Exception in thread "main" java.awt.HeadlessException:
No X11 DISPLAY variable was set, but this program performed an operation which requires it.
at java.desktop/java.awt.Desktop.getDesktop(Desktop.java:301)
at com.docusign.App.main(App.java:48)
@GBIEK ➜ /workspaces/code-examples-java (master ✗) $

Thank you for reaching out.
One of our engineers will come back to you shortly.

Is this still an issue?


Day 16: Proboscidea Volcanium

Codecov Report

Merging #25 (f66b4a8) into main (a3bf246) will increase coverage by 0.00%.
The diff coverage is 98.42%.

@@           Coverage Diff            @@
##             main      #25    +/-   ##
========================================
  Coverage   98.34%   98.35%
========================================
  Files          45       47     +2
  Lines        3389     3577   +188
========================================
+ Hits         3333     3518   +185
- Misses         56       59     +3

Impacted Files
Coverage Δ

lib/solution/src/lib.rs
100.00% <ø> (ø)

lib/solution/src/day16/cave.rs
97.69% <97.69%> (ø)

bin/aoc2022/src/main.rs
94.02% <100.00%> (ø)

lib/solution/src/day16/mod.rs
100.00% <100.00%> (ø)

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

Codecov Report

Merging #25 (f66b4a8) into main (a3bf246) will increase coverage by 0.00%.
The diff coverage is 98.42%.

@@           Coverage Diff            @@
##             main      #25    +/-   ##
========================================
  Coverage   98.34%   98.35%
========================================
  Files          45       47     +2
  Lines        3389     3577   +188
========================================
+ Hits         3333     3518   +185
- Misses         56       59     +3

Impacted Files
Coverage Δ

lib/solution/src/lib.rs
100.00% <ø> (ø)

lib/solution/src/day16/cave.rs
97.69% <97.69%> (ø)

bin/aoc2022/src/main.rs
94.02% <100.00%> (ø)

lib/solution/src/day16/mod.rs
100.00% <100.00%> (ø)

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


pixi-display or pixi-layers

Hey Ivan,
I've stumbled upon this library when trying to do some work to create a image/content editor with Pixi as the rendering engine. Basically Fabric.js/Illustrator but with Pixi for the WebGL.
I was going to write a lot of my own stuff but I saw the pixi-layers branch and all the great work/demos that went into that. Great job and docs too!
I then also saw that pixi-display had a few commits as well. Are you forking the projects? The way the pixi-layers readme reads pixi-layers has a more advanced version of pixi-display in it.
I'm going to start with pixi-layers as a starting point but I'd like to know/understand your plans moving forward and if in my using this library I can be of any help.

There is only one commit, I deleted something. Yes, its better to start with pixi-layers.


Cleantool

Adds a tool to help manually clean up orphaned test resources.
Fixes #232

friendly ping @bowei @kl52752 @AwesomePatrol

/lgtm
/approve

/lgtm


switch off smoothing for incidence plot

Smoothing changes the very last value of incidence rate, but people want to know exactly that latest value.
One may offer to smooth only a part of the data, but then there will be a breakpoint. Therefore I suggest full removing the smoothing of the curve. It looks good enough after we made it thicker.
Closes #231

It looks fine, so I merge straight away.


Calling method on non-struct

I have a type like
type Bob string
func (b Bob) FuncName() string {
return string(b)
}
and when I try to eval  it "someBob.FuncName()=='bob'"I get the error
"Unable to access '" + pair[i] + "', '" + pair[i-1] + "' is not a struct"
So I modified evaluationStage.go:makeAccessorStage to check for a method before doing the
struct-check and I get
Too many arguments to parameter call: got 1 arguments, expected 0
I do not understand why or how to fix.
Help? Suggestions?

You'd better use a custom struct?
My test case works.
package testgovaluate

import "github.com/Knetic/govaluate"

const ZacharyWins = "Zachary wins"

type AccessorFuncRet struct {
}

func (afr AccessorFuncRet) Tide(arguments ...interface{}) (interface{}, error) {
	return ZacharyWins, nil
}

func TestAccessorFunc(t *testing.T) {
	exp, err := govaluate.NewEvaluableExpression("A.Tide('hello world')")
	if err != nil {
		panic(err)
	}
	res, err := exp.Evaluate(map[string]interface{}{"A": AccessorFuncRet{}})
	if err != nil {
		panic(err)
	}
	resFloat, ok := res.(string)
	if !ok {
		t.Fatalf("return is %v, the type is %v, not string ", res, reflect.TypeOf(res))
	}
	if resFloat != ZacharyWins {
		t.Errorf("Error -> Real result is %v", res)
	} else {
		t.Logf("result of TestAccessorFunc is %q", res.(string))
	}
}

Well, the struct is not necessarily one of mine.  It may be from a framework or something.
gp does all kinds of things with giving functions to primitive types like strings, ints etc.


DOC: adding recon-all issue to faq

Changes proposed in this pull request

adding question to faqs: recon-all already running. Addresses https://github.com/poldracklab/fmriprep/issues/1570

Documentation that should be reviewed

docs/faq_tips_tricks.rst

Hi @franklin-feingold, can you start all your commits with the string docs(recon-all): <your message>? That will trigger the docs build only (no need for you to cancel manually).

@oesteban I tried to use your docs(recon-all): <message> as my commit but it did not automatically cancel the get* jobs, not sure if there was another step needed to not run the get* jobs


!tm:adc:TM_ADC_InitADC:RCC - avoid all ADC clocks enable

current implementation TM_ADC_init enables all ADC clocks, this patch enables only initianed ADC clock

What do you mean?
#if defined(ADC1) 	if (ADCx == ADC1) 	__HAL_RCC_ADC1_CLK_ENABLE();  //<--- should i insert more tabs here? #endif

if (check) {
    statement;
}

Use brackets always with 4 spaces indent.

this is very ugly rule, imho, but as you govern...


chore: Vendor kubernetes.core doc_fragments

What this PR does / why we need it:
Vendor the kubernetes.core doc_fragments used by this collection because it is not possible to refer to doc_fragments of dependency collections.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

None

/approve


Bind Query to new syntax. Add useQuery hook.

Hello, everyone, excited make my first PR here! :)
useQuery rationale
First of all, I want to highlight some considerations I had to take in making the useQuery binding not as good as the Query component.
Currying Drawbacks
To start it all, the main driving force for how I decided to go with that API was the Drawback No. 3 here: https://bucklescript.github.io/docs/en/function#drawback
Because of BuckleScript currying, I couldn't get too sophisticated with the API before it messed up with the context React Hooks needs to properly function.
It was not possible to use a type signature such as:
let useQuery = (~query: string, ~variable=?, ~requestPolicy=?, ~pause=?, ()) => {};

// Doesn't even compile, as you can't force uncurrying with labeled args
// let useQuery = (. ~query: string, ~variable=?, ~requestPolicy=?, ~pause=?, ()) => {};

// Even with only one argument in the function, it would curry
let useQuery = args: richUseQueryResponse('a) => {};

// Cant force uncurrying here because of https://bucklescript.github.io/docs/en/function#pitfall
let useQuery = (.args): richUseQueryResponse('a) => {};

So in the end, the best option was to expose the binding directly, and use<EMAIL_ADDRESS>abstract] for the args record to maintain type safety in ReasonML land and not deal with Js object directly.
By the end of it, we have the bindings in this PR, and use it like this:
let args = useQueryArgs(~query, ~variables, ());
let (result, _executeQuery) = useQuery(args);

Query component new syntax
This one was tricky not because of the complexity, or drawbacks from the language, it was because of a known issue with npm-link (https://github.com/facebook/react/issues/13991) that made testing it really hard. To solve it, you have to add to webpack.config.js resolve the following alias:
  resolve: {
   alias: {
    react: path.resolve('./node_modules/react'),
     urql: path.resolve('./node_modules/urql'),
    "react-dom": path.resolve('./node_modules/react-dom'),
   }
  }

Maybe it would be interesting to add it to all examples already, so future users don't face the same issue?
I saw that in 3-mutation, there's a resolve config too, like this:
  resolve: {
    modules: [path.resolve(__dirname, "../../node_modules"), "node_modules"]
  },

This one seems more catch-all, and could help mitigate any issue that may arise with future libraries!

Just an idea re: the useQuery currying -- what were your thoughts about redefining the useQuery function in reason so that it uses the useQuery external but provides a nicer interface? like this:
<EMAIL_ADDRESS>"urql"]
external useQuery: (useQueryArgs('a)) => useQueryResponse('b) = "useQuery";

let useQuery = (~query: string, ~variables=?, requestPolicy=?, pause=?, ()) =>
  useQuery(useQueryArgs(~query, ~variables?, ~requestPolicy?, pause?, ()));

Then people could call useQuery without needing to know about useQueryArgs

I tried that approach, the currying will mess up the React Hook context that way too. It seems that uncurrying is a pre requisite for any React Hook in Reason.

I just noticed that what I thought was the error (currying drawback) in the useQuery case, is not really the culprit. It was the webpack issue I mentioned that was giving me error and I thought it was the currying drawback.
Actually what you suggested, @Schmavery, is quite possible. I gave it a test again and it worked just fine. I'll commit later today the changes to make useQuery more consistent with useMutation implementation

Thanks for the review @parkerziegler!
I changed everything you suggested, except for the webpack config as I don't know much about it, and it gave me some errors when I tried to copy-paste from 3-mutation

@all-contributors add @gugahoa for code and example.

@all-contributors add @Schmavery for ideas.

@all-contributors add @kiraarghy for example.


Object.get_signal_connection_list() only returns signals connected with the Signals GUI.

Tested versions
4.3 RC
System information
Godot v4.3.rc1 - macOS 14.5.0 - GLES3 (Compatibility) - Apple M1 Pro - Apple M1 Pro (8 Threads)
Issue description
expected behaviour of Object.get_signal_connection_list() is to return a list of nodes a signal is connected to, regardless of if it was connected with the Signals GUI or with code (it doesn't say otherwise in the class reference).
Steps to reproduce
running the attached project should print the button to the console. If you disconnect the button's 'pressed' signal using the GUI and uncomment the code in the button's script, it should print an empty array ([]).
the single main scene is a button with the following script:
extends Button

func _ready() -> void:
	#pressed.connect(_button_pressed)
	#self.pressed.connect(self._button_pressed)
	pass

func _button_pressed() -> void:
	print("hello!")

and a child Node with this script:
extends Node

func _ready() -> void:
	print(get_parent().get_signal_connection_list("pressed"))

Minimal reproduction project (MRP)
signals.zip

The _ready of the child node is called before that of the parent, see the documentation, so this is expected
Can you confirm it works when you call it after having connected the signal?

@AThousandShips it works if I move the above code from respective _ready() functions to _enter_tree(). Was the issue that I wasn't using best practice for referencing nodes when they're initialised?

Read the link I sent, _ready in a child is called before that of a parent
Closing as there's no bug here, but an issue of order of execution

Hi I did read the link you sent I was just asking for clarification so I could investigate it myself and better understand the order of execution. Not very helpful :[

The order is described there, I didn't intend any dismissal, but this isn't a bug, please turn to the other community channels for more support! But in this particular case the issue is that _ready is called in all children, and then in the parent, and _enter_tree is called in the opposite order

Okay thanks I understand. Appreciate it!