Is this project no longer maintained?

Is this project no longer maintained? No new release, no accepted PRs, no responses from @riophae.
vue-treeselect is a fantastic project - it would be a big loss if it was left to die... :(

you are correct - no longer maintained

It's very annoying to use a package and and see it is no longer mainained.
A simple message in readme file "this pacakge is not maintained" would be the minimum.
Unfortunately, this is often happening in ecosystem of Vue, too many package dead.

please someone give alternative of this package

I've found this one. https://www.npmjs.com/package/vue3-treeselect
the vue3-treeselect is alse not maintained

I've forked this package and updated a bit surrounding warnings and errors. It works for me (at the moment), but don't expect super things.

thanks @amanpatel I have it running here

@amanpatel did u test it, also how do we install this fork of yours?


[Feature]: What is Suspensive? Suspensive support all suspensive things. intersection observer, suspense, delay, error-boundary

Package Scope
etc
Description
We should rethink about suspensive
We not only support suspense, suspensive things delay, intersection observer, error-boundary, etc.
Possible Solution
No response
etc.
No response

Hi. I'm interested in this project. Thanks for your great works.
As I see, recently some packages such as @suspensive/jotai was added to this project or there are the plans yet like @suspensive/intersection, @suspensive/relay and so on.
So I have the questions.

This library will support ONLY the features related with React's suspense in the future? (I feel like the name, suspensive is to deal with Suspense as well. 😀)
I was wondering all of this new features that are released and planing recently, are needed from toss products?

This library will support ONLY the features related with React's suspense in the future? (I feel like the name, suspensive is to deal with Suspense as well. 😀)

In my personal opinion, No. At first time I made this Suspensive package, we only focus on suspense. But recently, I realized that in order to easily guarantee the situation we want, we often need to interrupt the progress of React's Children's render with promises, times, viewport and errors or etc. So, I think the name Suspensive should not be limited to supporting only Suspense. and https://dictionary.cambridge.org/dictionary/english/suspensive When I thought about the meaning of this word, I realized that it does not support only Suspense. So, I would like to call all the things that guarantee the undetermined as Suspensive interfaces

I was wondering all of this new features that are released and planing recently, are needed from toss products?

Since there are too many Toss team members besides me and too many Toss products, I cannot give an exact answer to this question on their behalf. However, we are developing the features we expect to be necessary in advance, and the hit rate is quite good. Toss products already rely on the Suspensive library in more than 10 projects, and we are working in consultation with the Toss front-end platform team to further expand it.(I'm not one of Toss fron-end platform team)  and Suspensive care not only toss's product suspensive cases, also all world products' suspensive cases.
I don't know if I gave you the answer you wanted. If you clarify the intent of this question, I may be able to answer more clearly.

Oh, thanks for your kind explaination. 👍
Recently this library was making other packages, so I was just wondering what's your thought on this library. 😄

I updated description of repository


Document existence of firing and resolved alerts lists

I wasn't able to find any docs that describe the .Firing and .Resolved collections.

LGTM

Thanks!


filesystem::path

build volk and use new version of boost 1.70.0 in debian 9 unstable
old version not have this error


Code cleanup

Fixes #590
Checklist

[ ] New tests are added to ensure new features are working (probably by modifying the frb_example/pure_dart example).
[ ] All existing and new tests are passing.
[ ] If this PR adds/changes features, documentations (in book folder) are modified as well.

LGTM, waiting for ci to pass

🎉


Push a CNAB Bundle to GCR fails

Pushing a CNAB bundle to gcr.io returns an error:
Error: error while pushing bundle config manifest: unexpected status: 400 Bad Request

After some investigation, we found multiple caveats:

The bundle manifest itself had only a config field and a null layer field. This was fixed in #64 , adding a dummy layer pointing to the config object itself (it adds duplication)
When using external (mostly multi architecture images) images for services, we are potentially mixing different format representations: one service can be a manifest list, another an OCI index, and the CNAB itself be an OCI index too. This mix is not supported by gcr (and maybe other registries too). I think we can't guarantee that every service image will share the same format, so the minimum we can do is to fail if we detect a mix between images. That said, we need to also improve cnab-to-oci to detect which format we should use, depending the one found in the service images, instead of the fallback mechanism (try with OCI Index then Docker Manifest List).

From https://github.com/docker/app/issues/562

I'm not sure https://github.com/docker/cnab-to-oci/pull/64 is a complete fix as I hit the problem when building at master (27701312d17158eea04c079e7ffcc75259741264). Here are steps to reproduce:

Grab this sample bundle.json
Issue: cnab-to-oci --log-level debug push bundle.json -t gcr.io/<your project>/cnab-to-oci-sample
Fails, where <your project> is cf-sandbox-gnormington with:

DEBU[0000] Fixing up bundle gcr.io/cf-sandbox-gnormington/cnab-to-oci-sample
DEBU[0000] Fixing image glyn/cnab-to-oci-sample-cnab:e923b473656ef515302cd8daf8d734e07ea0a1ac
Starting to copy image glyn/cnab-to-oci-sample-cnab:e923b473656ef515302cd8daf8d734e07ea0a1ac...
Completed image glyn/cnab-to-oci-sample-cnab:e923b473656ef515302cd8daf8d734e07ea0a1ac copy
DEBU[0003] Fixing image hello-world@sha256:92c7f9c92844bbbb5d0a101b22f7c2a7949e40f8ea90c8b3bc396879d95e899a
Starting to copy image hello-world@sha256:92c7f9c92844bbbb5d0a101b22f7c2a7949e40f8ea90c8b3bc396879d95e899a...
Completed image hello-world@sha256:92c7f9c92844bbbb5d0a101b22f7c2a7949e40f8ea90c8b3bc396879d95e899a copy
DEBU[0004] Bundle fixed
DEBU[0004] Pushing CNAB Bundle gcr.io/cf-sandbox-gnormington/cnab-to-oci-sample
DEBU[0004] Pushing CNAB Bundle Config
DEBU[0004] Trying to push CNAB Bundle Config
DEBU[0004] CNAB Bundle Config Descriptor
DEBU[0004] {
  "mediaType": "application/vnd.cnab.config.v1+json",
  "digest": "sha256:99bb324f7d14e36aa9871920df164d04956e51e5d5b5e44c4d1dc36324200e11",
  "size": 100
}
DEBU[0004] Trying to push CNAB Bundle Config Manifest
DEBU[0004] CNAB Bundle Config Manifest Descriptor
DEBU[0004] {
  "mediaType": "application/vnd.oci.image.manifest.v1+json",
  "digest": "sha256:88c71a3786a9fd8801f09985e4e5142a316f32864a70513f1cf88c186b424026",
  "size": 188
}
DEBU[0005] Failed to push CNAB Bundle Config Manifest, trying with a fallback method
DEBU[0005] Trying to push CNAB Bundle Config
DEBU[0005] CNAB Bundle Config Descriptor
DEBU[0005] {
  "mediaType": "application/vnd.oci.image.config.v1+json",
  "digest": "sha256:99bb324f7d14e36aa9871920df164d04956e51e5d5b5e44c4d1dc36324200e11",
  "size": 100
}
DEBU[0005] Trying to push CNAB Bundle Config Manifest
DEBU[0005] CNAB Bundle Config Manifest Descriptor
DEBU[0005] {
  "mediaType": "application/vnd.oci.image.manifest.v1+json",
  "digest": "sha256:fd7309a61ab1cb5ff783f78801b5edc667b836f95b56a5a4755051b1550fbbab",
  "size": 193
}
DEBU[0006] Failed to push CNAB Bundle Config Manifest, trying with a fallback method
DEBU[0006] Trying to push CNAB Bundle Config
DEBU[0006] CNAB Bundle Config Descriptor
DEBU[0006] {
  "mediaType": "application/vnd.docker.container.image.v1+json",
  "digest": "sha256:99bb324f7d14e36aa9871920df164d04956e51e5d5b5e44c4d1dc36324200e11",
  "size": 100
}
DEBU[0006] Trying to push CNAB Bundle Config Manifest
DEBU[0006] CNAB Bundle Config Manifest Descriptor
DEBU[0006] {
  "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
  "digest": "sha256:c12e12dd0993fcd5826668f14b4fec9215c8f12a20c956ea40f8e0c39d8b836c",
  "size": 520
}
DEBU[0006] CNAB Bundle Config pushed
DEBU[0006] Pushing CNAB Index
DEBU[0006] Trying to push OCI Index
DEBU[0006] {"schemaVersion":2,"manifests":[{"mediaType":"application/vnd.docker.distribution.manifest.v2+json","digest":"sha256:c12e12dd0993fcd5826668f14b4fec9215c8f12a20c956ea40f8e0c39d8b836c","size":520,"annotations":{"io.cnab.manifest.type":"config"}},{"mediaType":"application/vnd.docker.distribution.manifest.v2+json","digest":"sha256:65747a4dd330a0062b4288f8d500cd96dbcb140f7086548557504ad63c9fa6e2","size":1364,"annotations":{"io.cnab.manifest.type":"invocation"}},{"mediaType":"application/vnd.docker.distribution.manifest.v2+json","digest":"sha256:92c7f9c92844bbbb5d0a101b22f7c2a7949e40f8ea90c8b3bc396879d95e899a","size":524,"annotations":{"io.cnab.component.name":"simple-image","io.cnab.manifest.type":"component"}}],"annotations":{"io.cnab.runtime_version":"v1.0.0-WD","org.opencontainers.artifactType":"application/vnd.cnab.manifest.v1","org.opencontainers.image.authors":"[{\"name\":\"Glyn Normington\"}]","org.opencontainers.image.description":"","org.opencontainers.image.title":"cnab-to-oci-sample","org.opencontainers.image.version":"0.1.0"}}
DEBU[0006] OCI Index Descriptor
DEBU[0006] {
  "mediaType": "application/vnd.oci.image.index.v1+json",
  "digest": "sha256:0cbc68985d57a86c4a36a00fa2b766b3f47b0f93ba98924a14b1a467a001201d",
  "size": 1049
}
DEBU[0006] Unable to push OCI Index: unexpected status: 400 Bad Request
DEBU[0006] Trying to push Index with Manifest list as fallback
DEBU[0006] {"schemaVersion":2,"manifests":[{"mediaType":"application/vnd.docker.distribution.manifest.v2+json","digest":"sha256:c12e12dd0993fcd5826668f14b4fec9215c8f12a20c956ea40f8e0c39d8b836c","size":520,"annotations":{"io.cnab.manifest.type":"config"}},{"mediaType":"application/vnd.docker.distribution.manifest.v2+json","digest":"sha256:65747a4dd330a0062b4288f8d500cd96dbcb140f7086548557504ad63c9fa6e2","size":1364,"annotations":{"io.cnab.manifest.type":"invocation"}},{"mediaType":"application/vnd.docker.distribution.manifest.v2+json","digest":"sha256:92c7f9c92844bbbb5d0a101b22f7c2a7949e40f8ea90c8b3bc396879d95e899a","size":524,"annotations":{"io.cnab.component.name":"simple-image","io.cnab.manifest.type":"component"}}],"annotations":{"io.cnab.runtime_version":"v1.0.0-WD","org.opencontainers.artifactType":"application/vnd.cnab.manifest.v1","org.opencontainers.image.authors":"[{\"name\":\"Glyn Normington\"}]","org.opencontainers.image.description":"","org.opencontainers.image.title":"cnab-to-oci-sample","org.opencontainers.image.version":"0.1.0"},"mediaType":"application/vnd.docker.distribution.manifest.list.v2+json"}
DEBU[0006] Manifest list Descriptor
DEBU[0006] {
  "mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",
  "digest": "sha256:d84e8186a3cac7f71d0fc7c84e4a28dbf2a7bb4bc802fe881f6666bdb274c644",
  "size": 1121
}
DEBU[0007] Unable to push Index with Manifest list: unexpected status: 400 Bad Request
Error: unexpected status: 400 Bad Request

However, it works when pushing to docker hub. However, when I tried to copy the bundle from docker hub to GCR, I got the following error:
copy failed: failed to write image gcr.io/cf-sandbox-gnormington/cnab-to-oci-master-copied: failed to write image index gcr.io/cf-sandbox-gnormington/cnab-to-oci-master-copied: MANIFEST_INVALID: Failed to parse manifest for request "/v2/cf-sandbox-gnormington/cnab-to-oci-master-copied/manifests/sha256:fd7309a61ab1cb5ff783f78801b5edc667b836f95b56a5a4755051b1550fbbab": Manifest is missing required field "layers".


⚠ Bofrost.lu has degraded performance

In 5635103, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 838 ms

Resolved: Bofrost.lu performance has improved in ef7b578 after 6 minutes.


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 2435 ms

Resolved: Bofrost.de performance has improved in 919eba5 after 1 hour, 48 minutes.


position doesn't seem to work

I tried the following code:
vm.$notify('Profile saved successfully!', 'success', { position: 'bottom-right' });

It doesn't seem to display notifications on the bottom-right but rather top-left.

The positioning is a global setting and needs to be applied in the use statement:
import Vue from 'vue'
import Notify from 'vue2-notify'

Vue.use(Notify, {position: 'top-full', visibility: 3000})


Bump open aea to latest

Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.
Fixes
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an x in the box that applies

[ ] Non-breaking fix (non-breaking change which fixes an issue)
[ ] Breaking fix (breaking change which fixes an issue)
[ ] Non-breaking feature (non-breaking change which adds functionality)
[ ] Breaking feature (breaking change which adds functionality)
[ ] Refactor (non-breaking change which changes implementation)
[ ] Messy (mixture of the above - requires explanation!)

Checklist
Put an x in the boxes that apply.

[ ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the main branch (left side). Also you should start your branch off our main.
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have locally run services that could be impacted and they do not present failures derived from my changes

Minor and not an issue, but do we want to change the version in the example too?
https://github.com/valory-xyz/open-autonomy/blob/92f13bb2c3aeea38e68a7e0fcc51c770408b9aff/docs/price_oracle_intro.md?plain=1#L102


refactor: Simplify BacklinkField & add test for #1927

Description

Add a passing test for #1927
Add extensive tests for Task.getLinkText()
Make the types used for path and heading in BacklinkField tests match those used in Task
Simplify the implementation of BacklinkField.value() to re-use Task.getLinkText()

This previously looked like it wouldn't work as strings like filename >  were being generated, but that turned out to be due to the tests using undefined where Task was using null)

Simplify the implementation of BacklinkField.grouper() to remove substring() and do simple string joining

Motivation and Context
In investigating #1927 - and trying to figure out how it actually got fixed by f3c6a41e92b3e39a81f564b4287c3016318fb93b, I spent some time trying to understand how the refactoring in f3c6a41e92b3e39a81f564b4287c3016318fb93b could have changed the behaviour.
Even though the change in behaviour was an improvement, I hadn't spotted the change during reviewing the code, and so I wanted to understand the new code.
What I had misread in the new BacklinkField code was this, in the value() method:
https://github.com/obsidian-tasks-group/obsidian-tasks/blob/f3c6a41e92b3e39a81f564b4287c3016318fb93b/src/Query/Filter/BacklinkField.ts#L29-L33
It still had the filenameComponent === headingComponent code that pre-dated the bug-fix, and from the comment on line 29, I had thought that these lines still had the issue of comparing an escaped string with a non-escaped one.
But they weren't - both were non-escaped strings. And the code in value() wasn't relevant to the grouping code anyway!
However, by the time I had got that far, I could see some ways to simplify the BacklinkField code.
How has this been tested?

Adding new tests, and using code coverage to ensure they were thorough
Running existing tests

Screenshots (if appropriate)
Types of changes

Internal changes:

[x] Refactor (prefix: refactor - non-breaking change which only improves the design or structure of existing code, and making no changes to its external behaviour)
[x] Tests (prefix: test - additions and improvements to unit tests and the smoke tests)

Checklist

[x] My code follows the code style of this project and passes yarn run lint.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] My change has adequate Unit Test coverage.

Terms

[x] My contribution follow this project's contributing guide
[x] I agree to follow this project's Code of Conduct

@ilandikov This is where #1927 took me 🤣

oh I remember now I had the idea to remove the extra code in 'BacklinkField.value()` =)
I'm curious why you chose result += ' > ' + task.precedingHeader; over result += ' > ${task.precedingHeader}'. Not that is changes things =)

I'm curious why you chose result += ' > ' + task.precedingHeader; over result += ' > ${task.precedingHeader}'. Not that is changes things =)

Because for something so simple, I felt that simple addition was more immediately readable (and easier to type) than the alternative...
It's all subjective though - either would have been fine.


[Infra] Any plans to support Python version<3.6?

Is your feature request related to a problem? Please describe.
Default python 3 version on Ubuntu 16.04 LTS is still below 3.6, which makes me not so easy to use Recognizers-Text on that environment with OS default setting.
Describe the solution you'd like
I'm wondering if there could be any plans on supporting version<3.6. Latest 3.5.x would be appreciated.
Describe alternatives you've considered
At least mentioning about python version requirements on README.

Hi @combacsa, unfortunately currently we don't have plans for it.
Would you be able to help contribute support?

I'll close this issue for now, as it's not currently planned.
Thanks.


Remove blocking in IMessageProcessingStrategy

... and tidied up the background launch of the ListenLoop.
This PR addresses the concern in #422

Following this I'll rebase #426


dart2js strong: issue with deferred loading instantiations in constants

repro:
a.dart:
import 'b.dart' deferred as b;

main() async {
  await b.loadLibrary();
  print(b.m<int>(3));
}

b.dart:
T getFoo<T>(T v) => v;

typedef dynamic G<T>(T v);

m<T>(T x, {G<T> f: getFoo}) {
  print(f(x));
}

produces this error:
/tmp/out.js:5914: TypeError: O.b__getFoo$closure is not a function
  C.CONSTANT = O.b__getFoo$closure();

(__getFoo$closure is defined in a deferred unit, but it is being accessed incorrectly from the main chunk)

FYI @johnniwinther - this started failing as a result of adding InstantiateConstantValue.
I started to investigate, but feel free to take over if I haven't send a fix yet.

The example contains a compile-time error since getFoo is inferred to be instantiated with <m.T> which isn't a constant. The problem still exists if m is not generic:
T getFoo<T>(T v) => v;

typedef dynamic G<T>(T v);

m(int x, {G<int> f: getFoo}) { // `getFoo` is instantiated with `<int>`.
  print(f(x));
}


Additional UI improvements, mainly for RVs

Now obsolete, by: https://github.com/quantified-uncertainty/squiggle/pull/2026


Update Django to v2

This PR:

Removes version fixations for libs in setup.py
Adds on_delete=modules.CASCADE to several foreign keys in the Extra and Feedback classes
Adds some disable pylint comments
Fix error handlers

Fixes  #162

Do we need any further changes for this PR?

A point for discussion: Is on_delete=CASCADE the right thing to do for feedback?

I think yes. As soon as an object gets deleted, the respective feedback is probably not relevant anymore.

The CMS seems to start correctly now. Everybody is welcome to search for problems and errors.

After dropping the database, creating a new one with a fresh migration, I get the following errors:
Performing system checks...

System check identified no issues (0 silenced).
August 19, 2019 - 16:04:24
Django version 2.2.4, using settings 'backend.settings'
Starting development server at http://localhost:8000/
Quit the server with CONTROL-C.
Internal Server Error: /regions/
Traceback (most recent call last):
  File "/home/sven/Code/integreat-cms-django/.venv/lib64/python3.6/site-packages/Django-2.2.4-py3.6.egg/django/template/base.py", line 829, in _resolve_lookup
    current = current[bit]
  File "/home/sven/Code/integreat-cms-django/.venv/lib64/python3.6/site-packages/Django-2.2.4-py3.6.egg/django/utils/functional.py", line 257, in inner
    return func(self._wrapped, *args)
TypeError: 'User' object is not subscriptable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/sven/Code/integreat-cms-django/.venv/lib64/python3.6/site-packages/Django-2.2.4-py3.6.egg/django/db/models/fields/related_descriptors.py", line 393, in __get__
    rel_obj = self.related.get_cached_value(instance)
  File "/home/sven/Code/integreat-cms-django/.venv/lib64/python3.6/site-packages/Django-2.2.4-py3.6.egg/django/db/models/fields/mixins.py", line 13, in get_cached_value
    return instance._state.fields_cache[cache_name]
KeyError: 'profile'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/sven/Code/integreat-cms-django/.venv/lib64/python3.6/site-packages/Django-2.2.4-py3.6.egg/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
psycopg2.errors.UndefinedTable: relation "cms_userprofile" does not exist
LINE 1: ...ser_id", "cms_userprofile"."organization_id" FROM "cms_userp...

The previous error was due to a not clean database. After dropping everything and recreating as described in the README it works fine.


GPU benchmarks for PyTorch tests benchmark on CPU instead.

Currently, there is no support for benchmarking pytorch models on CUDA via pytest.
SHARK/setup_venv.sh should be updated with a GPU_BENCHMARKS flag to uninstall the CPU version of Pytorch Nightly and replace with CUDA version.
SHARK/shark/shark_benchmark_runner.py::SharkBenchmarkRunner has a torch_benchmark method that should be updated to run with GPU/CUDA for gpu pytest cases.

This issue is resolved by PR #218


FormatException: Unexpected character (at character 1) ... on Windows 10 Home Single Language Operating Systems

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
Environment Information:
Operating System: Windows 10 Home Single Language
Architecture: [x64 or x86]
Visual Studio: Build tried with both 2019 and 2022 version
Observed Behavior:
The application window opens but remains stuck on a white screen.
Expected Behavior
The application should launch successfully without getting stuck on a white screen, and no FormatException error should occur.

No similar issues have been observed on other operating systems.
Actual results
When attempting to launch the executable on Windows 10 Home Single Language, the application gets stuck on a white screen, and the following error is encountered:
27-11-2023 10:34: FormatException: Unexpected character (at character 1)

                                                                           ...

^

Logs

Logs
27-11-2023 10:34: FormatException: Unexpected character (at character 1)

                                                                           ...

^

Flutter Doctor output

Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.13.9, on Microsoft Windows [Version 10.0.19045.3324], locale tr-TR)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Community 2019 16.11.32)
[√] Android Studio (version 2022.3)
[√] IntelliJ IDEA Ultimate Edition (version 2022.3)
[√] VS Code (version 1.84.2)
[√] Connected device (3 available)
[√] Network resources

@huseyinhamad
The package list you shared contains lot of third party libraries. If you create a new Flutter project and try to run, does it throw the same error as reported ?

When attempting to launch the executable on Windows 10 Home Single Language,

Are you trying to double click the .exe or building using flutter build windows which gives you the said error ?

Is that the only error log you get or there's more ? If so, can you provide more details that will help to replicate locally ?


'NoneType' object has no attribute 'strip'

django 1.6.10,  embed_video, VERSION = (0, 10, 'stable')
#models.py
video = EmbedVideoField(_('video url'), blank=True,null=True)
When I save the page empty field from admin, below is returned, what could cause this? But if I put youtube url, then it is saved okay and all in good shape.
'NoneType' object has no attribute 'strip'

@sunjoomoon are you using any 3rd party apps? I'm also getting this error but with Django 1.8 and model translation.

@sunjoomoon please copy and paste full error stacktrace.

I think the issue here is to with initialising with null=True, I presume Django does a strip() and this is what causes the error.
As per the thread here remove null=True and that fixes the problem.

Long time, yes indeed. somehow at the database level that is not quite happy with null value. As you said removing null=True did the job.


Content model of type extensions to hast are incorrect

Initial checklist

[X] I read the support docs
[X] I read the contributing guide
[X] I agree to follow the code of conduct
[X] I searched issues and couldn’t find anything (or linked relevant results below)

Affected packages and versions
latest
Link to runnable example
No response
Steps to reproduce
https://github.com/syntax-tree/mdast-util-mdx-jsx/blob/b823b2000b11931ceda0c64f14c15e8b9ee5f8a5/lib/complex-types.d.ts#L46-L56
Expected behavior
should contain hast children
Actual behavior
contains mdast nodes
Affected runtime and version
latest
Affected package manager and version
No response
Affected OS and version
No response
Build and bundle tools
No response

weird caching, github!


Replaces SpanStoreValidator with SpanStoreSpec

SpanStoreValidator was in src/main and included a bespoke unit test
framework. This is harder to understand than normal unit tests, clutters
the main source tree, and makes debugging test failures custom.
This introduces a similar class, SpanStoreSpec, which uses normal
assertions and supports JUnit annotations. This means that you can use
IDE support such as rerunning a specific test, override or ignore test
methods, or even use test rules to start your backends. Finally, this
gets the test code out of the main source tree.

Don't merge, yet. I need to change this to skip the two failing cassie tests.

ok PTAL

Interesting that you uncovered the testing framework.  I restarted the travis job, but there was a problem with the redis span store spec.  Not sure if this is an intermittent failure or not.

yeah, well redis didn't actually run the tests prior (only did clear() actually!), so there may be some flakes to squash over time. beats zero coverage, though!

ok build's green. I will help with flakes or disabling things that flake on certain backends.


用homebrew安装了ttyd和gdb后，点击[debug this script]按钮后tippy要报错

运行环境是WSL 2，安装的版本是prebuild的0.3.0

As on M1 Mac, .Net doesn't seem to respect user path. When homebrew bin directory is not in standard location (e.g. /usr/local/bin it cannot fork gdb or ttyd.

Fixed in 6c41693.


Rename plugin entrypoint from "mkdocs/exporter" to "exporter"

Keep old names working but with a warning.
Slashes are reserved for theme-specific plugins, and this plugin is not specific to the "mkdocs" theme.

Hi @oprypin,
I really appreciate your contribution! The updated naming convention is fantastic, especially since it aligns more closely with the correct semantics.
Furthermore, I'm grateful that you've maintained compatibility with the previous nomenclature by including a deprecation warning. This is very thoughtful.
Thank you!


Remove forced seed from Delta Lake part_write_round_trip_unmanaged tests [databricks]

#9741 and #9748 crossed paths such that #9748 didn't remove the forced seed added in #9741.  This fixes that oversight.

build


Traceback from site: 'HTTP 403: Forbidden'

Hi,
I was looking at /report/ceph/ceph on repohealth.info and got the following traceback:
Traceback (most recent call last):
  File "/app/repohealth/generate.py", line 63, in no_raise
    yield
  File "/app/repohealth/generate.py", line 213, in repo_data
    stargazers = loop.run_sync(stargazers_fn)
  File "/app/.heroku/python/lib/python3.7/site-packages/tornado/ioloop.py", line 576, in run_sync
    return future_cell[0].result()
  File "/app/.heroku/python/lib/python3.7/site-packages/tornado/gen.py", line 1141, in run
    yielded = self.gen.throw(*exc_info)
  File "/app/repohealth/github/stargazers.py", line 41, in repo_stargazers
    response = yield client.fetch(url, headers=headers)
  File "/app/.heroku/python/lib/python3.7/site-packages/tornado/gen.py", line 1133, in run
    value = future.result()
tornado.httpclient.HTTPClientError: HTTP 403: Forbidden

Direct link: https://repohealth.info/report/ceph/ceph
Thanks,

Looks like this repo is in bad health 👎


Updating api for v6.0.0

PUBG API is updating their PC Rating for the new patch coming out which introduces a new ranking system. This will need to be addressed.
Important key notes:

For XBOX the original rating properties (as is) will still be available.
For PC killPoints, winPoints, and their deltas will be deprecated for RankPoint.

Hi,
thanks for the issue and the PR!
The only thing left to worry about is the removal of killPoints, killPointsDelta, winPoints and winPointsDelta from PC's participants attributes.
I think the easiest way to handle it would be to mark those fields as nullable in IParticipantAttributes (and by consequence, mark the same fields as nullable in the class Participant). This way we would keep the same code working for both PC and XBOX, otherwise we'd have to split Participant objects according to the platform requested, and I don't really like that.
Something like this: https://gist.github.com/martinsileno/e84b6daa11f1469fd7ddb5dd6e913ea9.
If you have better ideas let me know!
Anyway, since they are marked as deprecated, according to their release process they will still be available for two weeks after the release.

I like the idea of keeping one participant object instead of separating them out -- keeps the models more maintainable for now.
I took your gist and updated my PR with your changes 👍

@martinsileno PUBG made another announcement today so I updated this issue to be generically for v6.0.0 and updated notes.

PR merged and version v1.5.0 released! 🎉
Only thing left is to add typing for seasonState, as soon as we know its format.


[State management Bug - Node.js] privateConversationData always get cleaned when persisted

Bot Info

SDK Platform: Node.js
SDK Version: 3.15.0
Active Channels: Web
Deployment Environment:  Azure App Service, local development with Emulator

Issue Description
In relates to issue #3682, in session.endConversation(), privateConversationData is always reset to {} before it's persisted, making it useless in reality because all data were purged in the storage. Users are forced to hack the userData or implement their own state management.
Code Example
bot.dialog('/', [
      session => {
        session.privateConversationData = {
            sessionId: session.message.address.conversation.id,
            beginTime: (new Date()).toISOString()
          }
        builder.Prompts.text(session, 'feedback')
      },
     (session, arg) => {
        session.privateConversationData.feedback= arg.response
        session.endConversation('feedback-received')
      }
 ])

Expected Behavior
Conversation data stored in e.g. cosmos db
Actual Results
data property is empty or only contains "BotBuilder.Data.SessionState"

Hi beatgates,
I think you have missed on correctly setting/initializing the bot state data using cosmosDb. Link.
Additionally, try using session.save() explicitly before endConversation().
I hope this provides some input before a member responds here.
Cheers!

@ashi1702 This piece of code is only an extract for you to understand the problem. The initializing of bot state using cosmosDB is not essential for that purpose and thus not included. You can certainly use your own set up of cosmosDB and this problem will still reproduce with the provided example code above or actually any code trying to persist privateConversationData.
Secondly, using session.save() before endConversation() doesn't have any effect either. I hope you could read through issue #3682 as I quoted in the problem description to understand the problem better.
Like I described, the problem lies in the code in session.endConversation(). It always set privateConversationData and ConversationData to {} before sendBatch(), when those states get persisted. Yes, during the session, those states were persisted as expected, however once endConversation() is called, they are all gone. That's the problem. It's either a design or an implementation mistake I reckon.

@beatgates privateConversationData and conversationData are both intended to be temporary storage to help track where the bot is conversationally with a user. When you call session.endConversation() it makes sense for this temporary storage to be cleaned up given that you've said the conversation is over.
It's worth noting that while this behavior is by design in the v3 SDK it's no longer automatically cleaned up for you in the v4 SDK.  With that said, it's still a best practice to delete your conversation state when the conversation is over in v4.  If you don't you run the risk of getting users into a stuck state.

@Stevenic Thanks for the explanation. I believe the v4 design makes more sense. There could be risks but at least they are under users' control. Developers should be responsible for any risks associated if they are taking advantage of these features.
So instead of using the built-in state management scheme, the design seems to promote separation of conversation state management from conversation logging and prefer uses to implement their own state/conversation logging?

Thank you for opening an issue against the Bot Framework SDK v3. As part of the Bot Framework v4 release, we’ve moved all v3 work to a new repo located at https://github.com/microsoft/botbuilder-v3. We will continue to support and offer maintenance updates to v3 via this new repo.
From now on, https://github.com/microsoft/botbuilder repo will be used as hub, with pointers to all the different SDK languages, tools and samples repos.
As part of this restructuring, we are closing all tickets in this repo.
For defects or feature requests, please create a new issue in the new Bot Framework v3 repo found here:
https://github.com/microsoft/botbuilder-v3/issues
For Azure Bot Service Channel specific defects or feature requests (e.g. Facebook, Twilio, Teams, Slack, etc.), please create a new issue in the new Bot Framework Channel repo found here:
https://github.com/microsoft/botframework-services/issues
For product behavior, how-to, or general understanding questions, please use Stackoverflow.
https://stackoverflow.com/search?q=bot+framework
Thank you.
The Bot Framework Team


Property 'email' of object # is not a function

Property 'email' of object # is not a function

How are you reproducing this?

@beshoysemsem bump


Maybe document a localizable app for easier translations

https://github.com/mohakapt/Stringz

Apple has made this easier in Xcode 15 with a new localizable option. I have moved to that with the latest diffs in Xcode15 branch.


Clippy warns about ineffective identity_op

#[macro_use]
extern crate serde_derive;

#[derive(Serialize)]
struct S {
    a: u8,
}

fn main() {}

warning: the operation is ineffective. Consider reducing it to `Serialize`
 --> src/main.rs:4:10
  |
4 | #[derive(Serialize)]
  |          ^^^^^^^^^
  |
  = note: #[warn(identity_op)] on by default
  = help: for further information visit https://github.com/Manishearth/rust-clippy/wiki#identity_op

We have seen this before but it was fixed in Clippy I think. #395 has a workaround.

Also affects single_match_else: https://github.com/Manishearth/rust-clippy/issues/1877

Fixed as of clippy 0.0.144.


Add nix+ruff CI

Expensive for a single tool.  Nix CI could be revisited if we start doing more complicated tests/builds.


Latest AMI for testing does not allow for environments where users may be blocked from using  just any AMI

https://github.com/aws/aws-parallelcluster/blob/c3bec0846ce370a3691dc0e00cd83530e7eccdcf/cli/pcluster/config/pcluster_config.py#L429
In corporate environments such as mine, we are frequently blocked from using AMIs that are not on an approved list.  The barrier to adding new AMIs to the list is high.
The use of the latest AMI in this function surprised me, as it was not a documented AMI required for pcluster, as given here.  I had requested a specific AMI be whitelisted to get past the initial configuration test, then less than two weeks later the "latest" was advanced, and I had to repeat my request.  Actually, I modified the code in this line to return the specific AMI I had gotten approved previously.  I had to dig into the code to understand why these unlisted AMIs were required, and found that they are only used for a 'DRYRUN' configuration test.
Wouldn't it make sense to use the AMI that pcluster will launch itself, rather than this more generic AMI, which is not otherwise used by pcluster?  This could include potentially custom AMIs specified in the cluster section's custom_ami field.  By using the AMI for testing that is also used by pcluster itself (ie the AMIs in that amis.txt), I can request approval for a specific documented list corresponding to the version of the tool I'm using; I know that the configuration check that this AMI is used for will actually exercise my ability to launch that specific AMI, not some other AMI; and I have the option to stay at that version so as not to be blocked by unexpected changes in the required AMIs.
If that change cannot be made, maybe a global config option to have a 'test_ami'....

Sorry for the lack of communication at the time I tagged this issue.
I agree that this is definitely a worthwhile change. The motivation for using the latest Amazon Linux AMI instead of using the AMI that will actually be used is that the AMI mappings used to get the default AMIs for a given region-OS combination is contained in the CloudFormation template unless a custom_ami is used (as you mentioned).
As a workaround, you can prevent the error from blocking cluster creation by setting the sanity_check parameter to false.

This has been addressed as part of https://github.com/aws/aws-parallelcluster/pull/2584 . The code will be released as part of 3.0.0 release and is going to use official amis for the test.

This was addressed also as part of 2.10.2 release. From changelog:

Improve cluster config validation by using cluster target AMI when invoking RunInstances in dryrun mode.


Question: Better to use this or a client generated using OpenAPI?

It seems to me that a client generated using OpenAPI/swagger would be 'more complete' and also more up-to-date as the REST API evolves. Would you agree? Why or why not?

Hi Steve,
I think that generating a client via Swagger works well.  The Swagger definition is "mostly complete" but there are a few spots that will require manual fix-ups.  But you will get most of the endpoints "out of the box". I think you will also need to write your own OAuth connector if you would like to use OAuth.  Overall I think if your interested in using a swagger/openAPI generated client , it is worth giving it a try to see if it meets your needs.

Cool. Thanks for the response. We are currently using a version of this client, so we will need to do some work to use a swagger client. I'm trying to weigh costs vs benefits of doing that. We are currently using basic auth, and I don't currently see us changing that part of things.


Can't unlock secrets

Plugin version
v1.0.14
netbox-plugin-extensions version
v1.0.8
NetBox version
v3.1.7
Python version
3.7
Steps to Reproduce

Click unlock button under "Secret data" section

Expected Behavior
Unlocked secret
Observed Behavior
I am getting error page with message "Must define ciphertext before unlocking.":

There was a problem with your request. Please contact an administrator.

The complete exception is provided below:

<class 'Exception'>
Must define ciphertext before unlocking.
Python version: 3.7.3
NetBox version: 3.1.7

After deleting and recreating secret, everything is working.


fix(ui): fix S2 Unauthenticated dialog typo

fix(ui): remove spurious "t"

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 27.619%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3635

Relevant Lines:
13870

💛  - Coveralls

Sorry I'm a newb and don't know what to do to fix the check with an error, or how to ask the bot for help :(


Markdownit module doesn't work

I installed markdownit module.
First, it asked loader. There's not a single word in documentation that I need some kind of markdown loader. WHY?
Second, I found markdown-loader, tried to install it. You said seamless integration. Well, it is not working too. After loader installation I get this errors
TypeError: Cannot read property 'loaders' of undefined

  - index.js:15 Builder.extendBuild.config
    [markdownit]/[@nuxtjs]/markdownit/index.js:15:20

  - utils.js:79 Builder.<anonymous>
    [markdownit]/[nuxt]/lib/common/utils.js:79:8

  - client.config.js:223 Builder.webpackClientConfig
    [markdownit]/[nuxt]/lib/builder/webpack/client.config.js:223:31

  - builder.js:364 Builder._callee5$
    [markdownit]/[nuxt]/lib/builder/builder.js:364:46

  - builder.js:171 Builder._callee$
    [markdownit]/[nuxt]/lib/builder/builder.js:171:16

Ok. Next, I found a bunch of webpack config settings - https://github.com/nuxt-community/markdownit-loader
I have no idea hot to set it with Nuxt.
You call this seamless integration?
Also, Nuxtent template is absolutely unusable. I don't understand why you publish all this code.

It's been fixed #125, just waiting for it to be pushed to npm.
@pi0, any chance of getting that pushed to npm?  I couldn't find a contribution guide so I'm not certain if there is a process to follow for CI or CD?

@nuxtjs/markdownit: 1.1.2  released :)

Thanks for update. What about loader? Do I need it? Do I need to extend webpack config, or this module do this job?

@iamdubx It should do it automatically too.

Confirm, now it's working. Looks like I really started to use this modules in bad times, when Nuxt updating.
Thank you for support @pi0


added special open destination support, quieted some logging

You might want to try merging this with head first.

/easycla


ember-getowner-polyfill

I believe this should be added as a dependency, not dev-dependency?

/cc @mike-north

The way that supports node 0.12 (still supported by ember-cli) involves installing the dependent addon explicitly in a consuming app. Dependency works if you're on a much more modern version of node, but addons should aim to support everyone.
We just need a line here like this
return this.addBowerPackageToProject('selectize', 'miguelcobain/selectize.js#master').then(function() {
  return this.addAddonToProject('ember-getowner-polyfill', '^1.0.0');
});

I've always done this through dependencies entry in package.json. E.g https://github.com/cibernox/ember-power-select/blob/master/package.json#L69

@miguelcobain I believe you'll run into problems if there's an installation blueprint or something else ember-addon-ish, on whatever you're declaring a dependency on. I don't believe that addons are resolved hierarchically all the way down into nested nested nested node_modules (remember, this is the npm2 world I'm talking about :) ). With NPM 3 and a flat node_modules, the world is a little simpler, but we still have to support 0.10 and 0.12.
Hence, adding as an NPM dependency is sometimes safe, adding as a consuming app dependency (assuming the consumer performs the conflict resolution between versions according to what's most appropriate for them) is almost always safe.
For other related discussion around introducing this same addon as a nested addon to another project see: https://github.com/runspired/ember-gestures/pull/44 https://github.com/runspired/ember-gestures/pull/46


feat: generate .forest.car.zst files by default

Summary of changes

Changes introduced in this pull request:

forest-cli snapshot export generates .forest.car.zst output,
forest-cli archive export generates .forest.car.zst output.
bug fix: use tipset timestamp (rather than now()) when exporting.

It's more work to generate .forest.car.zst files but the new encoder is much faster than the old one. All in all, exporting is now a lot faster and the generated compressed files can be loaded directly into Forest.
Reference issue to close (if applicable)

Closes
Other information and links

Change checklist

[x] I have performed a self-review of my own code,
[x] I have made corresponding changes to the documentation,
[x] I have added tests that prove my fix is effective or that my feature works (if possible),
[x] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

It'd be nice to update tests to enforce this behaviour.
https://github.com/ChainSafe/forest/blob/main/scripts/tests/calibnet_export_check.sh#L18-L19


[Bug] App Crash: OutOfMemoryError

Device: NOH-NX9 (HUAWEI - HWNOH), SDK: 31 (12), App: 2.4.3-alpha01 (98)java.lang.OutOfMemoryErrorat android.graphics.Bitmap.nativeCreate(Native Method)at android.graphics.Bitmap.createBitmap(Bitmap.java:1257)at android.graphics.Bitmap.createBitmap(Bitmap.java:1192)at b3.a.b(SourceFile:1)at m0.d.r0(SourceFile:1)at k9.u.u(SourceFile:330)at k9.u.p(SourceFile:13)at l0.b.v(SourceFile:5)at j7.w.W1(SourceFile:74)at k9.e0.o(SourceFile:15)at k9.f.u(SourceFile:84)at k9.f.p(SourceFile:13)at l0.b.v(SourceFile:5)at j7.w.W1(SourceFile:74)at j8.w.G0(SourceFile:37)at k9.k.u(SourceFile:95)at o7.a.n(SourceFile:1)at j8.c0.run(SourceFile:1)at k.j.run(SourceFile:253)at p8.i.run(SourceFile:1)at p8.a.run(SourceFile:94)Suppressed: o8.e: [m1{Cancelling}@42f3c58, Dispatchers.Main.immediate]

Large image?

After selecting image
Using Resize 'Type' / 'Ratio' / manually setting Height to '800'
Repeated 3x & crashed 3x.
On Mon, 20 Nov 2023 at 22:14, Malik Mukhametzyanov @.***>
wrote:

Large image?
—
Reply to this email directly, view it on GitHub
https://github.com/T8RIN/ImageToolbox/issues/566#issuecomment-1819812661,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APSDK35YN23VYXLOCDDDXB3YFPB2TAVCNFSM6AAAAAA7TQY5O6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJZHAYTENRWGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ratio is quite buggy, i will remove it i think, it's just the copy of flexible but working bad


Error Suppression: Can't Save Record when Location is Selected

When trying to save a new error suppression record, the following error is generated if a location is selected from the dropdown.

This is due to how TypeORM interprets and executes conditional logic in its find options: it is a bug. In particular, the manifestation of this bug in ECMPS stems from applying an OR condition in the IsValidCodes validation pipe of the ErrorSuppressionPayloadDTO's locations attribute.
While it is possible to specify an OR condition when using TypeORM's find method, it appears that TypeORM first evaluates each side of the clause using an INNER JOIN when specifying nested relations.
There are at least two potential workarounds:

use TypeORM's SelectQueryBuilder instead of the repository's find method
execute two separate queries

Both workarounds require updating the IsValidCodes pipe. It is my opinion that option 2 is a better choice: the required changes are simpler and the queries can take advantage of parallelism to improve performance.

Error Suppression was able to be created following above parameters without running into above error.

Verified in test environment - error suppression was successfully added without error message.


Edit initialization on notebook

This problem will fix on #543
I explain how to do that on Discord and in the Issue, so may not need to be corrected.

We will lock the version of gradio to older version.


Get current object

Hey everybody.
I'm working in project which I need get the current object in pagination.
Let's to example:
In CoffeeScript

$scope.items = [
{id: 1, text: One},
{id: 2, text: Two},
{id: 3, text: Three},
]
$scope.pageChanged = (obj, id) ->
console.log obj // ok, this my function return
console.log id // this is the problem, return undefined

In Haml:

.item{"dir-paginate" => "item in items | itemsPerPage: 1", "pagination-id" => "details"}
%p
{{item.id}} - {{item.text}}
%dir-pagination-controls{"pagination-id" => "details", "on-page-change" => "pageChanged(items, item.id)", "template-url" => "dirPagination.html"}

The pageChanged function can't return the item.id parameter.
Hugs.

Hi,
Per the docs the on-page-change callback will be supplied with a single argument, newPageNumber, which is the number of the page being navigated to.
Since you are just displaying one item per page, you can use this number as an index to get the correct object from your items collection.
e.g. (plain Javacript cos I don't do coffeescript)
// your controller
$scope.pageChanged = function (pageNumber) {
    var obj = $scope.items[pageNumber - 1];
    console.log(olj);
}

<!-- your template -->
<dir-pagination-controls on-page-change="pageChanged(newPageNumber)"></dir-pagination-controls>

Ohh great Michael!
Worked 100%!
Really, thank you so much.


Clarify on quoting YAML keys

I did some testing to confirm, and this does seem to be the case.

I somehow missed the notification when you submitted this.  Thanks!


Question Service - Add new data types to support community authors

Currently, there is a field in the mongodb schema called author (type string).
The Question type also includes an author attribute with type string.
As discussed, we can assign leetcode questions with the special author name "leetcode". Also, we can store the user id as the author.
The creation of question has not been linked to the frontend. I think that is the more critical issue to work on now


fix(plugin-credentials): checks to disable refresh and getUserToken while loggingOut

Disable refresh and getUserToken while logging out

closing as it is handled through a different PR.


Non-ASCII filenames

Hi,
I ran into an issue when upgrading a project to Django 3.1 and bumping dependencies. But before sending a PR, I'd like to discuss the solution.
Serving files works fine, except in production when they contain non-ASCII characters. I printed the response generated to debug it::
Content-Type: text/plain
X-Sendfile: /example/Accentu\xe9.txt
Content-Disposition: inline; filename="Accentue.odt"; filename*=UTF-8''Accentu%C3%A9.txt
Content-length: 143543

The path is encoded in ISO-8859-1, which makes sense with HTTP, but the filesystem encoding is UTF-8.
So I tried to quote it using urllib.parse.quote::
X-Sendfile: /example/Accentu%C3%A9.txt

with no success. So let's just encode it ourselves adding os.fsencode(filename) in the xsendfile backend::
X-Sendfile: /example/Accentu\xc3\xa9.txt

and I could finally download the file.
I'm not sure why it used to work in Django 2.2 and/or older versions of sendfile2, I can't rollback to test and I don't really want to spend time on it.
But you may not consider that fsencode an elegant solution. I can see in other issues you want to support the case where the file is served by Apache from another server. It probably means a setting, with a fallback to the local filesystem encoding. Tell me and I'll tailor the PR.
If you reject that change altogether, I can just "fork" the xsendfile backend in my project and change the setting to point to it.
The nginx backend seems safe, as it quotes the path.

I'd suggest you first write a test for unicode filenames and open a draft PR that just contains that. We will then see if Django 3.1 did really break something or not and go from there.

There are tests already covering unicode filenames. My issue may be more in Apache/X-Sendfile, but that won't be covered in a unit test.
My findings so far:

mod_xsendfile is unmaintained for like 10 years, good thing it still compiles against 2.4.
HTTP response headers might not actually accept non-ASCII characters, so my solution is just a hack, and nginx is right in urlquoting the path.
I found a fork adding that quoting https://github.com/nmaier/mod_xsendfile but unmaintained as well, and I use a shared hosting anyway.

So all in all, there is no "good" answer, mod_xsendfile never made it to the Apache official modules. That's surprising for such a useful module with no alternative after all this time.

After a refactor I could actually serve the files directly from a memoryview, a new feature of Django 3, and I didn't need sendfile for this project anymore.
Feel free to close this issue as you see fit, but I hope that little summary of the mess X-Sendfile is was useful for your, other users, and to answer future issues.

What is the current state of this issue?
With a simple method-based view, I can still reproduce this issue (currently using version 0.5.1):
from django_sendfile import sendfile

def sendfile_test(request):
    return sendfile(request, '/absolute/path/to/äüö.pdf')

This will yield the following entry inside the Apache error log:
[Tue Jun 28 15:24:39.895816 2022] [:error] [pid 2988] (2)No such file or directory: [client 192.168.XXX.XX:57604] xsendfile: cannot open file: /absolute/path/to/\xe4\xfc\xf6.pdf

The runserver setup works fine, but this does not help in production environments.
Replacing/monkey-patching the backend will yield the correct result. The patch includes encoding the path before passing it to the header inside the xsendfile backend:
filename = filename.encode('utf-8')

Looking at response._headers, the current implementation yields /absolute/path/to/äüö.pdf for the X-Sendfile header, whereas /absolute/path/to/Ã¤Ã¼Ã¶.pdf is given by the encoded version (and appears to work correctly).

mod_xsendfile is unmaintained for like 10 years, good thing it still compiles against 2.4.

@stefan6419846 that's the current status. I will add a warning to the docs before closing this issue, but it's well beyond the scope of this project to start maintaining an Apache module.

Does this indicate that this should rather be reported against mod_xsendfile as this is an issue there?
While mod_xsendfile might not be actively maintained, it seems to still work without any real issues (at least given my requirements). For this reason, from my perspective it should not hurt to actually include the aforementioned patch - unless there are some other cases which will break and which I am not aware of. Unfortunately, for some user bases non-ASCII filenames are quite common, which includes Germany as in my case, rendering the default xsendfile backend useless.

Just stumbled over this thread while I was looking if there is any update for the xsendfile backend.

filename = filename.encode('utf-8')

We are using that workaround in production since 2020 and had no issues since then.


Some find-in-path improvements

So, tools.which checks for files that exist, are executable, and not directories.
On Unix, find-in-path just checks exists?.
On Windows, find-in-path just checks exists?, and also doesn't use PATHEXT (see reverted commit be9bff0e5bc77e3998bfc92257dcee9d8ee5728b).
Should we make find-in-path look for executables (which would mean using PATHEXT)?
Or should we make a new find-executable that works like tools.which?

The new find-in-standard-login-path which spawns a login shell and echos the $PATH is related.

Also, its kinda weird having find-in-applications only on Windows and find-native-bundle only on Mac.
Maybe we can unify some of this stuff.

Related to https://github.com/factor/factor/issues/2021 in that both deal with paths.


Enable soft delete Storage Account capability

Hi.
I'm working on the provisioning and configuration Storage Account
One of the required configurations I need to set up is enabling soft delete capability.
For hours I was looking for any sample that demonstrated it.
The only class if found that apparently should be used is DeleteRetentionPolicy
As I mention, I have difficulty finding a sample code.
I guess the current model doesn't allow to set this configuration during Storage account creation; that intuitively should be there.
here is the code I create for my Storage Account gen 2
 StorageAccount storageAccount = azureResourceManager.storageAccounts().define(storageAccountName)
                    .withRegion(Region.fromName(region))
                    .withNewResourceGroup(rgName)
                    .withHnsEnabled(true)
                    .withBlobStorageAccountKind().disableBlobPublicAccess()
                    .withBlobStorageAccountKind().withAccessTier(AccessTier.HOT)
                    .withOnlyHttpsTraffic()
                    .withSku(StorageAccountSkuType.STANDARD_RAGRS)
                    .withMinimumTlsVersion(MinimumTlsVersion.TLS1_2)
                    .withGeneralPurposeAccountKindV2()
                    .create();

Any doc references or code samples will be appreciated
Thanks

Hi @DenisVoloshin, thanks for reaching out to us via this GitHub issue.  Someone from the azure-resourcemanager team will follow up with you on this question shortly.

@DenisVoloshin
Yes, it is DeleteRetentionPolicy.
Doc https://docs.microsoft.com/azure/storage/blobs/soft-delete-blob-overview (please do check the doc, it seems it won't help if either storage account or container got deleted, only for blob within container)
Code https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/resourcemanager/azure-resourcemanager-storage/src/test/java/com/azure/resourcemanager/storage/StorageBlobServicesTests.java#L34-L48 (sorry, it is a test, not a sample, but it should demonstrate the same)


Mocking block number

Hey! Wondering if there's any way to mock the block number? I can't immediately figure it out, or if Waffle is the right place to do it. I'm using waffle with hardhat & hardhat-ethers

@jemgold did you ever find a solution for this?

Found one here:
   await provider.send('evm_mine', []);


[terra-button] VoiceOver in Safari is highlighting the Terra Button in a frame bigger than the button size, when the button is included to a modal dialog.

Summary
Fixed issue - "VoiceOver in Safari is highlighting the Terra Button in a frame bigger than the button size, when the button is included to a modal dialog."
What was changed:
Removed 'position: relative', 'left: 0' and 'top: 0' from the .css when on Mac.
Why it was changed:
The 'position: relative' was creating the issue. The position, along with the left and top attributes were set specifically for IE mode, so they were not necessary on Mac anyway.
Testing

This change was tested using:

[x] WDIO

[x] Jest

[x] Visual testing (please attach a screenshot or recording)
Button before changes:

Button after changes:

[ ] Other (please describe below)

[ ] No tests are needed

Reviews
In addition to engineering reviews, this PR needs:

[ ] UX review
[x] Accessibility review
[x] Functional review

Additional Details

This PR resolves:
UXPLATFORM-9645

Thank you for contributing to Terra.
@cerner/terra

We should add a unit test where we mock the isMac and test if the correct class is applied.

Added the jest tests.


Outdated PlaceholderAdminMixin docs

The documentation says "To provide admin support for a model with a PlaceholderField in your application’s admin, you need to use the mixin PlaceholderAdminMixin along with the ModelAdmin" and "Out of the box PlaceholderAdminMixin supports multiple languages and will display language tabs" but nothing happens when I add PlaceholderAdminMixin to admin class.
class News(models.Model):
    author = models.ForeignKey(User, verbose_name='Author', on_delete=models.PROTECT)
    title = models.CharField('Title', max_length=150)
    publication_date = models.DateTimeField('Publication date', auto_now_add=True)

    content = PlaceholderField('content')

@admin.register(News)
class NewsAdmin(PlaceholderAdminMixin, admin.ModelAdmin):
    ordering = ('-publication_date',)

    search_fields = ['title']
    list_display = ('title', 'publication_date')
    list_display_links = ('title',)

Where is the control for the 'content' field? Where are language tabs? How should this work? Am I doing something wrong?

Hello,
Thanks for reporting this.
The PlaceholderAdminMixin doesn't actually display language tabs, it hasn't done so in a long time.
Sadly the documentation is out of date.

Interested in taking this on! Would the only change here be to change the wording so it doesn't mention language tabs?

Hi @jramirez857 ! This would be great! I'd also love to welcome you the the contributors' slack channel #contributors.
For the start it looks like a wording issue. Of course it would be good to double check with the source code.


⚠ HDBits has degraded performance

In 51c8f03, HDBits ($HDB) experienced degraded performance:

HTTP code: 200
Response time: 2279 ms

Resolved: HDBits performance has improved in 62ee22d after 36 minutes.


Add Verse of Day

Please add verse of day endpoint.

This is a low-level API. Adding a verse-of-the-day endpoint would be beyond the scope of what we provide here. Plus, who would be responsible for selecting such a verse?
Sorry we won't be adding this.


Please add example of DistributedVirtualSwitch creation and configuration

Would love to use rbvmomi more extensively but topics such as distributed virtual switching are not clear to me. An example file covering this would be of great help.

Found documentation via main vSphere API docs.


Inspector is (too) lazy

The inspector does not start up until an endpoint is invoked, which makes it hard to discover by newbies. Let's make the inspector available via CLI option (perhaps enable by default) and make it visible by default. Printing and URL that automatically opens the browser inspector is a plus.

This has long since been fixed.


Usability Improvements

Hey -- I know you'll probably be updating this for the Client API soon, so I want to suggest two improvements:

The "confirm your password" field in /profile is not clearly labeled as such. As such, it causes confusion.

In server.js, there's this snippet of code:

  if (req.body.password) {
    var application = req.app.get('stormpathApplication');

    application.authenticateAccount({
      username: req.user.username,
      password: req.body.existingPassword
    }, function (err) {
      if (err) {
        return writeError('The existing password that you entered was incorrect.');
      }

      req.user.password = req.body.password;

      saveAccount();
    });
  } else {
    saveAccount();
  }

In pseudocode:
If a password is submitted
    Verify password

    If verified, save data
    else error
If password isn't submitted
    save data

The password check doesn't really accomplish any specific goal since it doesn't really gate anything in the API, and would confuse people learning from this example. Either enforce the password verification, or don't enforce it -- not both!

I am lost on this one.  I am trying to change the logic.
Either
Require that a pass, then save account
Or
Authenticate the user prior to form submit or on form submit, if bad error else saveAccount()


DB Connection page does not show Oracle

Describe the bug
DB Connection page does not show Oracle
Desktop (please complete the following information):

OS: [linux]
Browser [chrome]
Version [3.2.2]

Additional context

Hi @gflp123
Thanks for your interest.
Under the license policy, only five connection types are supported by default.
(Mysql, postgres, hive, presto and druid)
But we provide additional connection type by extension module.
You can check this guide and if you have further questions please let me know

Thanks for your imply,I try it.
It  is  correct for connect,But  execute dataset collect error. For detail
ORA-00933: SQL command not properly ended

oracle-connection.zip

limit is not support in oracle
if(queryStmt!=null && false==queryStmt.isEmpty()) {
String pattern0 = ".\s;\s*$";
if(true==queryStmt.matches(pattern0)) {
queryStmt = queryStmt.substring(0,queryStmt.lastIndexOf(";"));
}
            String pattern = ".*limit\\p{Space}+[0-9]+\\p{Space}*$";
            Pattern p = Pattern.compile(pattern);
            Matcher m = p.matcher(queryStmt.toLowerCase());
            if(true==m.matches()) {
                sql = queryStmt;
            } else {
                sql = queryStmt + " LIMIT " + size;
            }
        } else {
            sql = "SELECT * FROM " + tblName + " LIMIT " + size;
        }


Added "Compress a directory into tarball" example and reworded decompress example

Added "Compress a directory into tarball" example
Reworded the example to use Decompress consistently

removed tempdir
fixed api links

fixes: https://github.com/brson/rust-cookbook/issues/188
fixes: https://github.com/brson/rust-cookbook/issues/186
cc: https://github.com/brson/rust-cookbook/issues/185

Thanks @budziq !


Ability to execute Python code block in a PowerShell Notebook

Is your feature request related to a problem? Please describe.
I haven't been able to locate the SQL Kernel so I can use to create SQL Notebook. I've seen it Azure Data Studio but can't find it for .NET Interactive.
Describe the solution you'd like
I know that in a C# Notebook you can use the "#!" to execute PowerShell command. So, it would be nice to have it also for Python or any other Kernels.
The scenario I'm looking for, I want to create a connection using Python code to execute the SQL code. Of course, all required python modules are installed.
Is this possible?
It would be great!
:)
PS. I just realized using either #!python or #!python3 doesn't work in for PowerShell or C# notebook.

Yes it would be great to have multi language notebooks with Python. In particular F# and Python. I got surprised it didn't work. You also need Python with notebooks to make the usable.


"Iterate Through an Array with a For Loop" not able to complete due to infinite loop & automatic execution

Challenge Name

https://www.freecodecamp.com/challenges/iterate-through-an-array-with-a-for-loop
Issue Description

While writing the loop for this challenge, I used a new variable j but instead of doing j++, I mistyped i++. When I ran the code it gave me a warning saying it will go in infinite loop and browser will crash
so I double checked but couldn't find this mistyped letter. So I wrote the comment //noprotect and the browser crashed which is fine. I restarted to correct it but it crashes everytime whenever I go to this challenge due to automatic execution maybe. Not able to complete this one.
for(int j=0; j<myArr.length; i++)
Browser Information

Browser Name, Version: Chrome
Operating System: Windows 10
Mobile, Desktop, or Tablet: Desktop

Your Code
// If relevant, paste all of your challenge code in here

Screenshot

This doesn't seem to be an issue with the platform itself. This is a semantic error on part of the programmer.
Your loop control condition j<myArr.length is always true for value of j is left unchanged. Therefore the infinite loop.
j is 0. and j is always less than myArr.length (5) for this condition is independent of i, loop ends up being infinite. :)

@piyushon2411 What you can do is-

run the correct code in a new private window without logging in
the url will change to reflect the entered solution
copy the url of the correct solution and now run it in the normal window where you're already logged in.

Let me know if you encounter any problems!

@piyushon2411 thanks for the issue. This isn't a bug, per se. When you mistyped i++ in your for loop, there is no constraint or condition for it to check (yours currently checks the value of j, j < myArr.length, but not i) and i will increment to infinity. Thus, you will get an infinite loop.
If you need more help with a challenge, please ask questions to the Help Room. Happy coding!

@erictleung actually, I think his issue is that the code he wrote is autorun on page load every time he revisits the challenge, due to which the browser crashes and he is unable to write the correct code.
We can do something like preventing that via a url append like-
http://freecodecamp.com/...``&codeautorun=false

Thanks @xRahul @erictleung for responding promptly. Rahul, your instructions resolved the issue.


Do not wrap ImagePlugin into paragraph

Editor wraps text into paragraphs automatically, and it's great. But I don't want it to wrap ImagePlugin into <p/> because it has its own render template which add all I need. How to configure custom behaviour for auto-wrapping?

You can select the "div" element from the dropdown menu before or after inserting an image plugin.
This is actually a ckeditor setting anyway, not related to the django CMS plugin


Add support for KMS Keys

@JustinBeckwith sorry if this makes a nightmare for #53. This is needed for https://github.com/googleapis/nodejs-storage/pull/179!

No problem at all!  This won't be bad to merge.

Thanks! Is it safe to release from master after this merges?


Bug - Copy text from dialog causes exception

I have a dialog with text on it. When I select and copy the text using Ctrl+C, an exception arises and the program crashes. For some reason, the exception does not happen if the text is copied using mouse right-click and then copy.
Dialog built and shown like this:
private void ShowHelpDialog()
{
    Bitmap bitmap = new(AssetLoader.Open(new("avares://Pororoca.Desktop/Assets/Images/pororoca.png")));

    var msgbox = MessageBoxManager.GetMessageBoxStandard(
        new MessageBoxStandardParams()
        {
            ContentTitle = "title",
            ContentMessage = "content",
            WindowStartupLocation = WindowStartupLocation.CenterScreen,
            WindowIcon = new(bitmap),
            ButtonDefinitions = ButtonEnum.Ok
        });
    Dispatcher.UIThread.Post(async () => await msgbox.ShowAsync());
}

Exception in console:
Unhandled exception. System.NotImplementedException: The method or operation is not implemented.
   at MsBox.Avalonia.Controls.MsBoxStandardView.Copy()
   at CompiledAvaloniaXaml.XamlIlTrampolines.MsBox.Avalonia:MsBox.Avalonia.ViewModels.AbstractMsBoxViewModel+Copy_0!CommandExecuteTrampoline(Object, Object)
   at Avalonia.Markup.Xaml.MarkupExtensions.CompiledBindings.CommandAccessorPlugin.CommandAccessor.Command.Execute(Object parameter)
   at Avalonia.Input.KeyboardDevice.ProcessRawEvent(RawInputEventArgs e)
   at Avalonia.Input.InputManager.ProcessInput(RawInputEventArgs e)
   at Avalonia.Controls.TopLevel.HandleInput(RawInputEventArgs e)
   at Avalonia.X11.X11Window.DispatchInput(RawInputEventArgs args)
   at Avalonia.RawEventGrouper.Dispatch(RawInputEventArgs ev)
   at Avalonia.X11.X11PlatformThreading.RunLoop(CancellationToken cancellationToken)
   at Avalonia.Threading.DispatcherFrame.Run(IControlledDispatcherImpl impl)
   at Avalonia.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
   at Avalonia.Threading.Dispatcher.MainLoop(CancellationToken cancellationToken)
   at Avalonia.Controls.ApplicationLifetimes.ClassicDesktopStyleApplicationLifetime.Start(String[] args)
   at Pororoca.Desktop.Program.Main(String[] args) in /home/runner/work/Pororoca/Pororoca/src/Pororoca.Desktop/Program.cs:line 17

what version do u use?

what version do u use?

The latest

I am getting the same behavior as well.


[SUGGESTION]  - Support swift 3

Please support Swift 3 :)

Sorry, swift 3 was so long ago that I do not see the point) It's time to upgrade to swift 5 :)


ARROW-4532: [Java] fix bug causing very large varchar value buffers

The varchar/varbinary vectors have a setSafe variant that takes an arrow buf and a start/end offsets. The method needs to expand the buffer to make space for 'end - start' bytes. but, due to a bug, it was expanding it to accommodate 'end' bytes, thereby making the value buffer much larger than required.

may be edit the commit message slightly to describe the problem?

Yes. It helps for the changelog when other developers can see when a bug they run into was fixed

@pravindra  thanks!

Codecov Report

Merging #3613 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3613      +/-   ##
==========================================
- Coverage   87.78%   87.77%   -0.01%
==========================================
  Files         673      673
  Lines       82776    82839      +63
  Branches     1069     1069
==========================================
+ Hits        72661    72713      +52
- Misses      10004    10011       +7
- Partials      111      115       +4

Impacted Files
Coverage Δ

go/arrow/math/int64_avx2_amd64.go
0% <0%> (-100%)
:arrow_down:

go/arrow/memory/memory_avx2_amd64.go
0% <0%> (-100%)
:arrow_down:

go/arrow/math/float64_avx2_amd64.go
0% <0%> (-100%)
:arrow_down:

go/arrow/math/uint64_avx2_amd64.go
0% <0%> (-100%)
:arrow_down:

go/arrow/memory/memory_amd64.go
28.57% <0%> (-14.29%)
:arrow_down:

go/arrow/math/math_amd64.go
31.57% <0%> (-5.27%)
:arrow_down:

js/src/visitor/indexof.ts
97.26% <0%> (-1.37%)
:arrow_down:

cpp/src/arrow/python/decimal.cc
98.03% <0%> (-0.85%)
:arrow_down:

cpp/src/plasma/store.cc
91.85% <0%> (-0.34%)
:arrow_down:

go/arrow/math/float64_amd64.go
33.33% <0%> (ø)
:arrow_up:

... and 15 more

Continue to review full report at Codecov.

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


Add SeamRef and HoleRef to Occurrence

The possibility to include refernces to seams and Hole2D are missing in the schema.

Included in #108


[Script] Images folder convert script to data_info.json

This script transforms a folder with images and captions to the correct folder structure with the data_info.json file. It also copies the image files to an indexed file name with the same extension as the original in the InternImgs folder. It also supports recursivity i.e. you can put multiple dataset folders in the root folder.
There is also an optional argument --caption_extension which is by default .txt but the user can change it if he wishes.
I thought this would be a useful script as I am more used to the other folder structure.

Pretty good and useful scripts. Thx a lot. Let's add a how-to-use in the Readme file?

This script should be officially included and documented. Else maybe the functionality needed to be able to use SDXL structured training data could be in train.py?
The people that are most likely to train Pixart-Sigma tend to have SDXL structured (image + .txt caption) training data.

really nice work. Thank you so much for your PR.🥰 @frutiemax92


Update plan-hyper-v-security-in-windows-server.md

Added WS2019 to the list of products this document applies to; tweaked title to be more generic; fixed Installation Options link

Hi @larsiwer ,
Thanks for helping out with this. Taking 2016 out of the body is okay, but Microsoft has not released a product called Windows Server 2019, so we can't add that to "Applies to." Pull that reference out and you'll be good to go.
Thanks,
Corey

Thanks @coreyp-at-msft -- removed WS2019 for now. We'll have to re-add it once WS2019 releases.


Option to hide status bar item

Environment data
VS Code version: 1.19.0-insiders ddb27c63122c09a3c4800cc4d928cd9faf97cef1
Python Extension version: 0.8.0
Python Version: 2.7
OS and version: MacOS High Sierra
Actual behavior
I only do occasionally dabble with python, so I'd love to disable the item in the status bar, but I can't find a way to do so:

Expected  behavior
Option to hide the version in the status bar

To help manage our issues and to better communicate what the team plans to work on we are closing issues that we don't plan to work on but would accept a pull request from a volunteer for. To be clear, closing this issue does not mean we won't consider a pull request for this enhancement as outlined in our contributing guide, just that the development team has no plans to work on it themselves.


Split tracing packages

This PR:

Creates a new tracer package
Deprecates the old trace package
Moves the opentracing and otel implementations of the tracer to their own packages
Moves the dependencies into their corresponding submodules leaving the root library free of external dependencies if the user doesn't use any OpenTracing or OpenTelemetry.
The default tracer is tracer.Noop

Is this a new tracer API that can have some breaking changes? Asking because I tweaked a bit the old one with breaking changes that I used in our fork for easier tracing of what's happening inside the library.
Here the interface as part of my PR:
type TraceRequestFinishFunc func([]*errors.QueryError)
type TraceOperationFinishFunc func()
type TraceFieldFinishFunc func(*errors.QueryError)

type Tracer interface {
	TraceRequest(ctx context.Context, queryString string, opType string, operationName string, variables map[string]interface{}, varTypes map[string]*introspection.Type) (context.Context, TraceRequestFinishFunc)

	TraceQuery(ctx context.Context, root selected.Field) (context.Context, TraceOperationFinishFunc)
	TraceMutation(ctx context.Context, root selected.Field) (context.Context, TraceOperationFinishFunc)
	TraceSubscription(ctx context.Context, root selected.Field) (context.Context, TraceOperationFinishFunc)

	TraceField(ctx context.Context, label, typeName, fieldName string, trivial bool, args map[string]interface{}) (context.Context, TraceFieldFinishFunc)
}

Here the commit message I worth:
Added TraceSubscription to Tracer interface and re-worked the interface

This is a breaking change, but I think the previous interface had flawed like limited
support for root operation, name was not totally right since `TraceQuery` was picking
up `mutation` change also and no support to make some analysis on the selection of field.

The new interface makes a distinction between a Request and actual root "operation". In a
request, the new tracing format supports the following nesting:

    Request (query)
     Root query (type, alias)
       Field1
       Field2
     Root query (type, alias)
       Field1
       Field2
    End

The `TraceRequest` could be renamed `TraceOperation` with a specific kind, but `TraceRequest`
felt better.

This PR is dependent on having the actual selection of fields, so we can actually extract fields information from selection for effective tracing.

I would like to get your opinion on some changes here, it improved our tracing quite well and I would like to see that included somehow.

I'm talking specifically about the new Tracer package here, I never open a PR to update the old exactly because I knew it was a breaking change and would not be accepted.
Now that we have a new package, I would like to update it to provide a better interface.

Is there a way to add your improvements to the library and not to the tracer

Not sure I understand your comment.

Here what I see as improvements that were added in our forked version:
Ability to determine the type actual type of the operation: query, mutation, subscription
The current TypeQuery is equivalent to the new proposed TraceRequest here. This stays the same but new tracing element are then added TraceQuery, TraceMutation and TraceSubscription.
By having that, it's now possible to have find grained metrics per type like how many active subscriptions there is currently.
In addition, those new three elements received the root selected.Field value which enables them to extract the actual name of what is going to be performed, super useful to better understand what is happening within a request.
Multi root tracer
If a request is performing multiple top-level root operations like this:
    Request (query)
     Root resolveTimestamp (type, alias)
       Field1
       Field2
     Root resolveTimestamp (type, alias)
       Field1
       Field2
    End

Now it's possible to create a tracing span for each root which will usually map to some a particular resolver, this again enable better tracking of what happen as well as grouping field trace later can be achieved since their context is tied to the correct span.
A part from the interface breaking change to add new tracing method for the "root" operation I'm talking here, the rest is mostly if not identical to before, if people still just want to trace the top-level request, they can simply no-op on TraceQuery, TraceMutation and TraceSubscription and it becomes roughly the same as before.
For those that would like augmented metrics about what kind of operations is performed and finer grain tracing, they can implement the extra three methods and do something.
For sake of completeness, here is our tracer implementation with the new interface:
package dgraphql

import (
	"context"
	"fmt"
	"strings"
	"time"

	"github.com/streamingfast/dtracing"
	"github.com/graph-gophers/graphql-go/errors"
	"github.com/graph-gophers/graphql-go/introspection"
	"github.com/graph-gophers/graphql-go/selected"
	gqtrace "github.com/graph-gophers/graphql-go/trace"
	"github.com/streamingfast/dgraphql/metrics"
	"go.opencensus.io/trace"
)

type Tracer struct {
}

func (t *Tracer) TraceRequest(
	ctx context.Context,
	queryString string,
	opType string,
	operationName string,
	variables map[string]interface{},
	varTypes map[string]*introspection.Type,
) (context.Context, gqtrace.TraceRequestFinishFunc) {
	metrics.InflightRequestCount.Inc()
	metrics.TotalRequestCount.Inc()

	spanCtx, span := dtracing.StartSpan(ctx, "GraphQL Request",
		"graphql.operationType", opType,
		"graphql.variablesCount", len(variables),
	)

	return spanCtx, func(errs []*errors.QueryError) {
		if len(errs) > 0 {
			setSpanError(span, errs)
		}

		span.End()
		metrics.InflightRequestCount.Dec()
	}
}

func (*Tracer) TraceQuery(ctx context.Context, root selected.Field) (context.Context, gqtrace.TraceOperationFinishFunc) {
	fieldName := root.Identifier()
	if fieldName == "__schema" {
		// It's an introspection schema request, let's ignore them
		return ctx, func() {}
	}

	startTime := time.Now()
	metrics.InflightQueryCount.Inc(fieldName)
	metrics.TotalQueryCount.Inc(fieldName)

	spanCtx, span := dtracing.StartSpan(ctx, "GraphQL Query",
		"graphql.query.type", fieldName,
	)

	return spanCtx, func() {
		span.End()

		metrics.InflightQueryCount.Dec(fieldName)
		metrics.QueryResponseTimes.ObserveSince(startTime, fieldName)
	}
}

func (*Tracer) TraceMutation(ctx context.Context, root selected.Field) (context.Context, gqtrace.TraceOperationFinishFunc) {
	fieldName := root.Identifier()

	startTime := time.Now()
	metrics.InflightMutationCount.Inc(fieldName)
	metrics.TotalMutationCount.Inc(fieldName)

	spanCtx, span := dtracing.StartSpan(ctx, "GraphQL Mutation",
		"graphql.mutation.type", fieldName,
	)

	return spanCtx, func() {
		span.End()

		metrics.InflightMutationCount.Dec(fieldName)
		metrics.MutationResponseTimes.ObserveSince(startTime, fieldName)
	}
}

func (*Tracer) TraceSubscription(ctx context.Context, root selected.Field) (context.Context, gqtrace.TraceOperationFinishFunc) {
	fieldName := root.Identifier()

	metrics.InflightSubscriptionCount.Inc(fieldName)
	metrics.TotalSubscriptionCount.Inc(fieldName)

	spanCtx, span := dtracing.StartSpan(ctx, "GraphQL Subscription",
		"graphql.subscription.type", fieldName,
	)

	return spanCtx, func() {
		span.End()
		metrics.InflightSubscriptionCount.Dec(fieldName)
	}
}

func (t *Tracer) TraceField(
	ctx context.Context,
	label, typeName, fieldName string,
	trivial bool,
	args map[string]interface{},
) (context.Context, gqtrace.TraceFieldFinishFunc) {
	if trivial {
		return ctx, noop
	}

	var i = 0
	keyedAttributes := make([]interface{}, len(args)*2)
	for name, value := range args {
		keyedAttributes[i] = "graphql.args." + name
		i++
		keyedAttributes[i] = sanitizeTraceAttributeValue(value)
		i++
	}

	keyedAttributes = append(keyedAttributes,
		"graphql.type", typeName,
		"graphql.field", fieldName,
	)

	spanCtx, span := dtracing.StartSpan(ctx, "GraphQL Field", keyedAttributes...)

	return spanCtx, func(err *errors.QueryError) {
		if err != nil {
			setSpanError(span, []*errors.QueryError{err})
		}

		span.End()
	}
}

func sanitizeTraceAttributeValue(value interface{}) interface{} {
	switch v := value.(type) {
	case bool, int, int8, int16, int32, int64, uintptr, uint, uint8, uint16, uint32, uint64:
		return v
	case string, fmt.Stringer:
		return v
	case map[string]interface{}:
		pairs := make([]string, len(v))

		i := 0
		for k, v := range v {
			pairs[i] = fmt.Sprintf("%s: %s", k, v)
			i++
		}

		return strings.Join(pairs, ", ")
	default:
		return fmt.Sprintf("%T", v)
	}
}

func setSpanError(span *trace.Span, errs []*errors.QueryError) {
	if len(errs) > 0 {
		msg := errs[0].Error()
		if len(errs) > 1 {
			msg += fmt.Sprintf(" (and %d more errors)", len(errs)-1)
		}

		// What's the correct way to track error in the span?
		span.SetStatus(trace.Status{
			Code:    trace.StatusCodeUnknown,
			Message: msg,
		})

		span.AddAttributes(trace.StringAttribute("graphql.error", msg))
	}
}

func noop(*errors.QueryError) {}

By having that, it's now possible to have find grained metrics per type like how many active subscriptions there is currently.

You can see the number of active subscriptions in your WebSocket implementation.

In addition, those new three elements received the root selected.Field value which enables them to extract the actual name of what is going to be performed, super useful to better understand what is happening within a request.

I find this redundant and I'm still not convinced that this is necessary. When you trace the rest of the request you can see which fields are selected. The trivial fields are usually not interesting and only the ones that require fetching data from some backend storage system are the ones of interest.

Now it's possible to create a tracing span for each root which will usually map to some a particular resolver, this again enable better tracking of what happen as well as grouping field trace later can be achieved since their context is tied to the correct span.

I can't imagine yet the benefit. Can you possibly show me a trace graph from your tracer vs the ones from the library if it is not too much work to clear sensitive info. I'd be curious to see the comparison.
As for the:
	metrics.InflightRequestCount.Inc()

I tend to handle these in the HTTP middleware, not in the tracer of the GraphQL library because the request is "in flight" until we have written the response. In your case you decrease the in-flight requests but they are not written yet to the consumer of the API.

I would consider adding more methods which are by default "no-op" for most people and you could do something with them with some graphql.SchemaOpt that allows you to add custom tracer methods.
I see that you sanitise attribute values - aren't you afraid that you might end up with PII in your traces? It is nice to have everything in the traces but some customers might want to filter out sensitive information from their traces.
Back to your original question - adding tracing methods for metrics of the queries, mutations and subscriptions in flight might be a reasonable thing to do. It is a non-breaking change and if it is a no-op for most users then I'd consider it, however, it is outside of the scope of this PR. The intention here is to make sure we deprecate the OpenTracing tracer since the project has been deprecated by the CNCF and make sure we add a default OTEL tracer implementation. Again voiding breaking changes as much as possible in the 1.x versions.

You can see the number of active subscriptions in your WebSocket implementation.

You cannot see which actual subscription it is. Seeing 1000 active subscriptions is something, but it's much more interesting to see which actual subscription it is. This is possible only if you have the right parsed selection so it's possible to extract the "root" identifier.

I find this redundant and I'm still not convinced that this is necessary. When you trace the rest of the request you can see which fields are selected. The trivial fields are usually not interesting and only the ones that require fetching data from some backend storage system are the ones of interest.

I know you get the fully query at the request level, but is it really a good idea to actually try to extract some semantic information from there, not really, much easier to actually use the already parsed selection.

I can't imagine yet the benefit. Can you possibly show me a trace graph from your tracer vs the ones from the library if it is not too much work to clear sensitive info. I'd be curious to see the comparison.

I agree it's more subjective, I found it interesting to have grouping by "top-level" graphql element, mostly because the "top-level" element, at least in our case, is always the start of some external resource loading and it's the way I find to easily get the kind of the actual "graphql" element.

I can't imagine yet the benefit. Can you possibly show me a trace graph from your tracer vs the ones from the library if it is not too much work to clear sensitive info. I'd be curious to see the comparison.

I don't have them handy because we stop collecting them for now. Roughly, using StarWars graph and query:
query {
  heroNewHope:hero(episode: NEWHOPE) { name }
  human(id: "1000") { name }
}

old way was looking like:
request starting {"operation_name": ""}
 field starting
 field terminated
 field starting
 field terminated
request terminated

And with the added "top-level" element:
request starting {"operation_name": ""}
 query starting {"name": "human"}
  field starting
  field terminated
 query terminated
 query starting {"name": "hero"}
  field starting
  field terminated
 query terminated
request terminated

For field tracing with the same name but from two different "root", it was hard to see where they were coming from.

As for metrics.InflightRequestCount.Inc()

Indeed, we could argue that for "request", HTTP middleware would be better, it's was all grouped in the tracer for those actually using field name like metrics.InflightMutationCount.Dec(fieldName) which use the actual knowledge of the GraphQL selection.

I see that you sanitise attribute values - aren't you afraid that you might end up with PII in your traces? It is nice to have everything in the traces but some customers might want to filter out sensitive information from their traces.

This is to query blockchain data, so everything is already public there, so it was not a concern in this case.

Back to your original question - adding tracing methods for metrics of the queries, mutations and subscriptions in flight might be a reasonable thing to do.

Ultimately my goal is to be able to to get if it's a top-level "node" and it's kind in this case Query, Mutation, Subscription. It could be added differently, like modifying the TraceField with extra information. I could simply then make some logic based on the field.
But if I recall right, it was much easier to create new tracing method for each "root" element and pass the type. The selection of field was something I added because I had access to it in my fork, but it's not strictly required and only the kind and the field type would be enough.

It is a non-breaking change and if it is a no-op for most users then I'd consider it, however, it is outside of the scope of this PR.

It's technically a breaking change IMO because all consumers of graphql-go which implement the tracer interface would have needed to be updated.

The intention here is to make sure we deprecate the OpenTracing tracer since the project has been deprecated by the CNCF and make sure we add a default OTEL tracer implementation. Again voiding breaking changes as much as possible in the 1.x versions.

I don't want to be a blocker on this PR, but I find it interesting that a new tracer package exists, this is for me means it's the right time to change the new tracer API if you accept (of course, ensuring the old trace one can continue working).


@GrosSacASac As I fond the v3.2.4 ver on npm, When can we make the v3.2.4 tag on github ? We need the github tag

@GrosSacASac As I fond the v3.2.4 ver on npm, When can we make the v3.2.4 tag on github ? We need the github tag
Originally posted by @wxhthx in https://github.com/node-formidable/formidable/issues/856#issuecomment-1136648592

Currently seeing the same thing, this might help with other packages trying to upgrade.

https://github.com/node-formidable/formidable/releases/tag/v3.2.4


Mint Linux not supported

I am on linux mint 21.1 and it says the version of ubuntu is too old
EDIT: the command ran was the same in the README
--2023-05-14 18:11:25--  https://git.io/vpn
Resolving git.io (git.io)... <IP_ADDRESS>
Connecting to git.io (git.io)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://raw.github.com/Nyr/openvpn-install/master/openvpn-install.sh [following]
--2023-05-14 18:11:27--  https://raw.github.com/Nyr/openvpn-install/master/openvpn-install.sh
Resolving raw.github.com (raw.github.com)... 2606:50c0:8003::154, 2606:50c0:8000::154, 2606:50c0:8001::154, ...
Connecting to raw.github.com (raw.github.com)|2606:50c0:8003::154|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://raw.githubusercontent.com/Nyr/openvpn-install/master/openvpn-install.sh [following]
--2023-05-14 18:11:28--  https://raw.githubusercontent.com/Nyr/openvpn-install/master/openvpn-install.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 2606:50c0:8001::154, 2606:50c0:8000::154, 2606:50c0:8003::154, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|2606:50c0:8001::154|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 23598 (23K) [text/plain]
Saving to: ‘openvpn-install.sh’

openvpn-install.sh  100%[===================>]  23.04K  --.-KB/s    in 0.007s

2023-05-14 18:11:29 (3.01 MB/s) - ‘openvpn-install.sh’ saved [23598/23598]

Ubuntu 18.04 or higher is required to use this installer.
This version of Ubuntu is too old and unsupported.

Duplicate.


How can I use it if I have no Uber app?

How can I use it if I have no Uber app?

If you don't have the app installed, the button will redirect to the Apple app store where you can download the Uber app.
Ultimately, to request a ride, you will need an Uber account and the Uber application installed on your device.

@christinekim Is there anyway to override this? I don't like this or the fallback. I would rather provide my own OAuth flow.

Hi @aasatt, can you please open a new issue for your request? It is possible to supply custom logic to the buttons and I'll be happy to point you in the right direction


'Mesh' object has no attribute 'generate_mesh'

Hi，guys
When I run example line2mesh_tri.py， I got a error 'Mesh' object has no attribute 'generate_mesh'.
Do I need to install some libary?

Hi - yes - sorry the github examples work with the dev version only, to update do:
pip install -U git+https://github.com/marcomusy/vedo.git

Thanks.


Cannot  lunch statsgen.py

Hi !
When i try to start  py statsgen.py  i get this error :
  File "C:\Users\xxxx\hashcat\pack\statsgen.py", line 178
    print "[+] Analyzing %d%% (%d/%d) of passwords" % (self.filter_counter*100/self.total_counter, self.filter_counter, self.total_counter)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?

I'm beeginer, i'm wrong somewhere or it's bug ?
I have Python 3.10 x64  and hashcat v6.2.4-136
Thanks for your help !

youre not wrong going through the same pain, looks like a lot of debugging needs to be done , currently working of getting a running update to this

This version still depends on Python 2.x. This fork might match your setup better:
https://github.com/Hydraze/pack

FOUND THE SOLUTION TO MAKE IT WORK
download python 2 and run it as you would python 3
downloaded py 2 and stored it in a folder called py2  ran the python executable as if it were the command
D:\TRAINING-GROUNDS\py2>python.exe "D:\TRAINING-GROUNDS\policygen.py"
_
PolicyGen 0.0.2  | |
_ __   __ _  | | _
| ' \ / ` |/ __| |/ /
| |) | (| | (|   <
| ./ _,|__||_
| |
||<EMAIL_ADDRESS>Boom i can now use maskgen


Minidata API Spec cleanup

name: Pull Request
about: Propose changes to the codebase
title: '[PR] Case and spelling corrections'
labels: 'documentation'
assignees: ''

Related Issue
#474
Proposed Changes

Capitalising and grammar corrections
State that setting .xtra is a one-way operation

Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist
Go over all the following points, and put an x in all the boxes that apply:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] I am aware that this is an nbdev project, and I have edited, cleaned, and synced the source notebooks instead of editing .py or .md files directly.

from fastsql import *
db = database('postgres:...')

I don't think fastsql has a lowercase database().

Oops! Updated!


[Bug]  flags "is already declared in the upper scope" for enum declaration

💻 系统环境 | Operating System
macOS
🐛 问题描述 | Bug Description
Linting a TypeScript file that contains only the following line
export enum PanelFormat {
  short = 'short',
  percent = 'percent',
}

flags the error 'PanelFormat' is already declared in the upper scope.
🚦 期望结果 | Expected Behavior
No error on a unique enum.
📷 复现步骤 | Recurrence Steps
No response
📝 补充信息 | Additional Information
No response

fixed in https://github.com/yuntijs/yunti-lint/commit/cd4a077f3986fcf275b2f3f6d0234fe79b6f428a , please use v1.5.0


Disallow undefined values for ol.layer.Base

What about minResolution and maxResolution?

minResolution and maxResolution are now handled

Looks good to me.