Fix typo

occured→occurred

Docs Build status updates of commit 6c44a86:
:clock10: Full build: the average full build time is 70 min(s) 14 sec(s), this is based on the last 15 build(s) for this repository.
:warning: This is a FULL build due to a recent Docs Build service upgrade, normally no action is required on your part. In the result you find subsequent builds still performing full builds, please contact your repository admin to manually perform a full build on the 'master' branch. For more detailed info, please click here.

Docs Build status updates of commit 6c44a86:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

en/api/AppKit.NSApplicationEnumerateWindowsHandler.yml
:x:Error

Details

en/api/AppKit.NSApplicationFile.yml
:x:Error

Details

en/api/AddressBook.ABPersonCompositeNameFormat.yml
:x:Error

Details

en/api/AppKit.NSApplicationError.yml
:x:Error

Details

en/api/AppKit.NSApplicationFileCommand.yml
:x:Error

Details

en/api/AppKit.NSApplicationMenu.yml
:x:Error

Details

en/api/AppKit.NSAnimationCurve.yml
:x:Error

Details

en/api/AppKit.NSApplicationPredicate.yml
:x:Error

Details

en/api/AppKit.NSApplicationPrint.yml
:x:Error

Details

en/api/AddressBook.ABPersonProperty.yml
:x:Error

Details

en/api/AppKit.NSApplicationActivationOptions.yml
:x:Error

Details

en/api/AppKit.NSBrowserDropOperation.yml
:x:Error

Details

en/api/AppKit.NSApplicationActivationPolicy.yml
:x:Error

Details

en/api/AppKit.NSApplicationReopen.yml
:x:Error

Details

en/api/AppKit.NSLayoutConstraintOrientation.yml
:x:Error

Details

en/api/AppKit.NSApplicationSelection.yml
:x:Error

Details

en/api/AppKit.NSApplicationHandlesKey.yml
:x:Error

Details

en/api/AppKit.NSLayoutFormatOptions.yml
:x:Error

Details

en/api/AppKit.NSControlTextError.yml
:x:Error

Details

en/api/AppKit.NSControlTextFilter.yml
:x:Error

Details

en/api/AppKit.NSFunctionKey.yml
:x:Error

Details

en/api/AppKit.NSRuleEditorNumberOfChildren.yml
:x:Error

Details

en/api/AppKit.NSOpenGLContextParameter.yml
:x:Error

Details

en/api/AppKit.NSControlTextValidation.yml
:x:Error

Details

en/api/AppKit.NSRulerEditorChildCriterion.yml
:x:Error

Details

en/api/AppKit.NSRulerEditorPredicateParts.yml
:x:Error

Details

en/api/AppKit.NSOpenGLGlobalOption.yml
:x:Error

Details

en/api/AppKit.NSOpenGLProfile.yml
:x:Error

Details

en/api/AppKit.NSDraggingEnumerator.yml
:x:Error

Details

en/api/AppKit.NSRulerEditorDisplayValue.yml
:x:Error

Details

en/api/AppKit.NSTableViewToolTip.yml
:x:Error

Details

en/api/AppKit.NSPasteboardWritingOptions.yml
:x:Error

Details

en/api/AppKit.NSTableViewViewGetter.yml
:x:Error

Details

en/api/CloudKit.CKDatabaseDeleteSubscriptionHandler.yml
:x:Error

Details

en/api/CoreLocation.CLGeocodeCompletionHandler.yml
:x:Error

Details

en/api/AppKit.NSPrinterTableStatus.yml
:x:Error

Details

en/api/CoreGraphics.CGEvent.CGEventTapCallback.yml
:x:Error

Details

en/api/AudioToolbox.AudioQueue.AudioQueuePropertyChanged.yml
:x:Error

Details

en/api/CoreSpotlight.CSSearchableIndexFetchHandler.yml
:x:Error

Details

en/api/CoreVideo.CVDisplayLink.DisplayLinkOutputCallback.yml
:x:Error

Details

en/api/Foundation.RegisterDataRepresentationLoadHandler.yml
:x:Error

Details

en/api/AppKit.NSPrintingOrientation.yml
:x:Error

Details

en/api/Foundation.RegisterFileRepresentationCompletionHandler.yml
:x:Error

Details

en/api/Foundation.RegisterFileRepresentationLoadHandler.yml
:x:Error

Details

en/api/AppKit.NSOpenGLPixelFormatAttribute.yml
:x:Error

Details

en/api/AppKit.NSPrintingPageOrder.yml
:x:Error

Details

en/api/GameController.GCControllerAxisValueChangedHandler.yml
:x:Error

Details

en/api/Foundation.RegisterObjectRepresentationCompletionHandler.yml
:x:Error

Details

en/api/CoreVideo.CVFillExtendedPixelsCallBack.yml
:x:Error

Details

en/api/AppKit.NSPrintingPaginationMode.yml
:x:Error

Details

This comment lists only the first 50 files in the pull request.

en/api/AppKit.NSApplicationEnumerateWindowsHandler.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSApplicationFile.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AddressBook.ABPersonCompositeNameFormat.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetEnum' (https://static.docs.com/ui/latest/schemas/NetEnum.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSApplicationError.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSApplicationFileCommand.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSApplicationMenu.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSAnimationCurve.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetEnum' (https://static.docs.com/ui/latest/schemas/NetEnum.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSApplicationPredicate.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSApplicationPrint.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AddressBook.ABPersonProperty.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetEnum' (https://static.docs.com/ui/latest/schemas/NetEnum.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSApplicationActivationOptions.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetEnum' (https://static.docs.com/ui/latest/schemas/NetEnum.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSBrowserDropOperation.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetEnum' (https://static.docs.com/ui/latest/schemas/NetEnum.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSApplicationActivationPolicy.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetEnum' (https://static.docs.com/ui/latest/schemas/NetEnum.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSApplicationReopen.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSLayoutConstraintOrientation.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetEnum' (https://static.docs.com/ui/latest/schemas/NetEnum.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSApplicationSelection.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSApplicationHandlesKey.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSLayoutFormatOptions.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetEnum' (https://static.docs.com/ui/latest/schemas/NetEnum.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSControlTextError.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSControlTextFilter.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSFunctionKey.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetEnum' (https://static.docs.com/ui/latest/schemas/NetEnum.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSRuleEditorNumberOfChildren.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSOpenGLContextParameter.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetEnum' (https://static.docs.com/ui/latest/schemas/NetEnum.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSControlTextValidation.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSRulerEditorChildCriterion.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSRulerEditorPredicateParts.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSOpenGLGlobalOption.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetEnum' (https://static.docs.com/ui/latest/schemas/NetEnum.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSOpenGLProfile.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetEnum' (https://static.docs.com/ui/latest/schemas/NetEnum.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSDraggingEnumerator.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSRulerEditorDisplayValue.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSTableViewToolTip.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSPasteboardWritingOptions.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetEnum' (https://static.docs.com/ui/latest/schemas/NetEnum.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSTableViewViewGetter.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/CloudKit.CKDatabaseDeleteSubscriptionHandler.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/CoreLocation.CLGeocodeCompletionHandler.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSPrinterTableStatus.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetEnum' (https://static.docs.com/ui/latest/schemas/NetEnum.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/CoreGraphics.CGEvent.CGEventTapCallback.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AudioToolbox.AudioQueue.AudioQueuePropertyChanged.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/CoreSpotlight.CSSearchableIndexFetchHandler.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/CoreVideo.CVDisplayLink.DisplayLinkOutputCallback.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/Foundation.RegisterDataRepresentationLoadHandler.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSPrintingOrientation.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetEnum' (https://static.docs.com/ui/latest/schemas/NetEnum.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/Foundation.RegisterFileRepresentationCompletionHandler.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/Foundation.RegisterFileRepresentationLoadHandler.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSOpenGLPixelFormatAttribute.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetEnum' (https://static.docs.com/ui/latest/schemas/NetEnum.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSPrintingPageOrder.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetEnum' (https://static.docs.com/ui/latest/schemas/NetEnum.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/GameController.GCControllerAxisValueChangedHandler.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/Foundation.RegisterObjectRepresentationCompletionHandler.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/CoreVideo.CVFillExtendedPixelsCallBack.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetDelegate' (https://static.docs.com/ui/latest/schemas/NetDelegate.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

en/api/AppKit.NSPrintingPaginationMode.yml

[Error-ViolateSchema]

Schema validation failed. Please validate the file and make sure it conforms to schema 'NetEnum' (https://static.docs.com/ui/latest/schemas/NetEnum.schema.json):
Property 'assembliesWithMoniker' has not been defined and the schema does not allow additional properties. Path 'assembliesWithMoniker'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Compile error from client

Hi, all
Thanks for your great project. I found there are some error message during the build. I use rustc 1.66.0-nightly (9565dfeb4 2022-10-28) and build the project with cargo +nightly build --release. Here is the log:
   Compiling client v0.1.0 (/home/eecheng/monoio-benchmark/client)
   Compiling monoio-server v0.1.0 (/home/eecheng/monoio-benchmark/monoio-server)
error[E0596]: cannot borrow `stream` as mutable, as it is not declared as mutable
  --> monoio-server/src/main.rs:40:34
   |
36 |     while let Ok((stream, _)) = listener.accept().await {
   |                   ------ help: consider changing this to be mutable: `mut stream`
...
40 |                 let (r, buf_r) = stream.read_exact(buf).await;
   |                                  ^^^^^^^^^^^^^^^^^^^^^^ cannot borrow as mutable

error[E0596]: cannot borrow `stream` as mutable, as it is not declared as mutable
  --> monoio-server/src/main.rs:45:34
   |
36 |     while let Ok((stream, _)) = listener.accept().await {
   |                   ------ help: consider changing this to be mutable: `mut stream`
...
45 |                 let (w, buf_w) = stream.write_all(buf_r).await;
   |                                  ^^^^^^^^^^^^^^^^^^^^^^^ cannot borrow as mutable

error[E0034]: multiple applicable items in scope
  --> monoio-server/src/main.rs:23:18
   |
23 |                 .build()
   |                  ^^^^^ multiple `build` found
   |
   = note: candidate #1 is defined in an impl for the type `RuntimeBuilder<FusionDriver>`
   = note: candidate #2 is defined in an impl for the type `RuntimeBuilder<TimeDriver<FusionDriver>>`
   = note: candidate #3 is defined in an impl for the type `RuntimeBuilder<IoUringDriver>`
   = note: candidate #4 is defined in an impl for the type `RuntimeBuilder<TimeDriver<IoUringDriver>>`
   = note: and 2 others

Some errors have detailed explanations: E0034, E0596.
For more information about an error, try `rustc --explain E0034`.
error: could not compile `monoio-server` due to 3 previous errors
warning: build failed, waiting for other jobs to finish...
error[E0596]: cannot borrow `stream` as mutable, as it is not declared as mutable
   --> client/src/main.rs:123:26
    |
115 |     let stream = TcpStream::connect(target).await.unwrap();
    |         ------ help: consider changing this to be mutable: `mut stream`
...
123 |         let (w, buf_w) = stream.write_all(buf).await;
    |                          ^^^^^^^^^^^^^^^^^^^^^ cannot borrow as mutable

error[E0596]: cannot borrow `stream` as mutable, as it is not declared as mutable
   --> client/src/main.rs:129:26
    |
115 |     let stream = TcpStream::connect(target).await.unwrap();
    |         ------ help: consider changing this to be mutable: `mut stream`
...
129 |         let (r, buf_r) = stream.read_exact(buf_w).await;
    |                          ^^^^^^^^^^^^^^^^^^^^^^^^ cannot borrow as mutable

error[E0034]: multiple applicable items in scope
  --> client/src/main.rs:49:82
   |
49 |             let mut rt = RuntimeBuilder::new().with_entries(2560).enable_timer().build().unwrap();
   |                                                                                ^^^^^ multiple `build` found
   |
   = note: candidate #1 is defined in an impl for the type `RuntimeBuilder<FusionDriver>`
   = note: candidate #2 is defined in an impl for the type `RuntimeBuilder<TimeDriver<FusionDriver>>`
   = note: candidate #3 is defined in an impl for the type `RuntimeBuilder<IoUringDriver>`
   = note: candidate #4 is defined in an impl for the type `RuntimeBuilder<TimeDriver<IoUringDriver>>`
   = note: and 2 others

error: could not compile `client` due to 3 previous errors

It can be fixed as the help hints. To run it quickly, you can fix it by your own. And if you are will to submit a PR, feel free to submit one.


[Bug]: Gemini Ultra Supported?

Bug Description
When I try to create:
gemini_pro = GeminiMultiModal(model_name="models/gemini-ultra-vision")

I get the following error:
google.api_core.exceptions.NotFound: 404 Model is not found: models/gemini-ultra-vision for api version v1beta

Do you support Gemini Ultra?
Version
0.10.30
Steps to Reproduce
import os
from llama_index.multi_modal_llms.gemini import GeminiMultiModal
from llama_index.core.multi_modal_llms.generic_utils import load_image_urls
from llama_index.core import SimpleDirectoryReader
from llama_index.core import StorageContext, load_index_from_storage
from llama_index.embeddings.openai import OpenAIEmbedding

gemini_pro = GeminiMultiModal(model_name="models/gemini-ultra-vision")

Relevant Logs/Tracbacks
No response

We support it, but depends on your access and installed client version (this response is coming directly from Google 🤷🏻 )

There's an example here (if you want to leverage the multimodal capabilities, you need the multi moda llm class for now)
https://docs.llamaindex.ai/en/stable/examples/multi_modal/gemini/?h=gemini
You can also use googles api to list the models available to you
https://ai.google.dev/api/python/google/generativeai/list_models

Ah ok thanks, I guess this means I need to be paying for Gemini Advanced to access Ultra?

Maybe? Haha I'm not fully aware of how googles api and access works (just pointing to examples I was aware of 😅)

Would it be possible to get support for Gemini model gemini-1.5-pro-latest? I believe this is different

I think once again, it's supported assuming you can access the model over the Google client

The reason I'm a bit confused is because on Gemini's website, there is a list  of their current models. I see that models/gemini-pro-vision is one of their current models, and this is one that is supported by Llamaindex. However, the other model supported by Llamaindex models/gemini-ultra-vision is not on Gemini's current list of models. Is there a way I can access gemini-1.5-pro-latest through llamaindex? I don't think this is the same as ultra?

1.5-pro-latest and ultra support landed if you have access, so I think we can close this?


Add initial html comments support

Fixes #1

Thanks for the merge request. I've tested it and it looks fine.


About performance improvement

Hello, thank you for your excellent work!
I am a green hand in diffusion model.
If I want to further improve the performance of model, what parameters and network structure do I need to modify? Do you have any suggestions? Thank you!

I'd suggest looking into sota U-net architectures (this one didn't have attention or anything like that). Could also take a look at more recent training / sampling schemes, e.g. Karras https://arxiv.org/abs/2206.00364.


Bug fix navigation

fixed about, contact us, newsletter and gallery header / navigation links. Replaced # with /

Href should also replace by routerLink, because we use  Angular


HTTP Error 503: Service Unavailable: Back-end server is at capacity

I keep getting this error while trying to test my bot, full error
youtube_dl.utils.DownloadError: ERROR: Unable to download JSON metadata: HTTP Error 503: Service Unavailable: Back-end server is at capacity (caused by <HTTPError 503: 'Service Unavailable: Back-end server is at capacity'>); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Post the full output of youtube-dl when run with -v, i.e. add -v flag to your command line, copy the whole output and post it in the issue body wrapped in ``` for better formatting. It should look similar to this:
$ youtube-dl -v <your command line>
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.youtube.com/watch?v=BaW_jenozKcj']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2015.12.06
[debug] Git HEAD: 135392e
[debug] Python version 2.6.6 - Windows-2003Server-5.2.3790-SP2
[debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
[debug] Proxy map: {}
...

Do not post screenshots of verbose log only plain text is acceptable.
The output (including the first lines) contains important debugging information. Issues without the full output are often not reproducible and therefore do not get solved in short order, if ever.

The problem is that I am not directly using it, I am going through a library (discord.py) that uses it, the library developer wasn't much help.

No help is possible without context, i.e. verbose log.


Plugin reporting invalid nvim version

I've installed this plugin with the below config on lazyvim
return {
  -- https://github.com/sourcegraph/sg.nvim
  {
    "sourcegraph/sg.nvim",
    dependencies = {
      "nvim-lua/plenary.nvim",
      "nvim-telescope/telescope.nvim"
    },
  },
}

I then login per the directions, and run the health check :checkhealth sg, and get the following output.
sg: require("sg.health").check()

sg.nvim report ~
- Machine: x86_64, sysname: Linux
- ERROR Invalid nvim version. Upgrade to at least 0.10.0. Current version: table: 0x7ff9ca663ad0
- ERROR Invalid nvim version. Upgrade to at least 0.9.4 or nightly

I'm currently on v0.9.5, I'm not sure where the Current version: table: 0x7ff9ca663ad0 is coming from.
$ nvim --version
NVIM v0.9.5

I have a few colleagues who have also installed the plugin and reported similar errors. Let me know any other details you would like, happy to work with you to diagnose the issue
Environment
NixOS 24.05, nvim 0.9.5, lazyvim as my plugin manager.

I had the exact same error. Upgraded Neovim to 10.0. :checkhealth now runs fine.


Add processes to project approval.

Hello directors!
I've added the process as we have discussed over the years. Unfortunately, most of the time the champion of a project has written up less than formal process. Thus I'm proposing here that we move all of these reviews to our formal github proposal process and use the attached rubrik.

With the information I have at this stage, this looks great! As noted in the docs, we're trying to hit a balance between providing specificity/direction and flexibility to the board. To better ensure we've hit that balance, perhaps we should vote on this after test driving the process detailed at our next meeting -- i.e. after hearing from the champions about how easy the given questions were to answer and after seeing how straightforward the resulting discussion is.
That being said, if everyone else is happy with this, I'm happy to vote positively and we can always amend if needed later. :)

@xorJane that sounds good. I'll ask Lorena to add it to the agenda.

I'll go ahead and merge the PR and add it to the board agenda for further discussion


Performance issue

Hi,
I use sensu and plugins on AWS.
When I have few check particulary when plugins require fog/aws-sdk gem the load average on my instance is very high.
On my fork I try each time as possible to rewrite some part of plugin to handle many cloudwatch / rds / elasticache / etc ... Because the bottleneck is the load of external gem.
How is the best way to handle many check ? The good response is not "increase your instance type". I know I can dispatch checks to more instances but I think a better way can be found.
Regards,

@yanntech Is this still an issue that you would like help with?  If not I would like to close this in a at the end of the month.
Thanks

Hi,
OK I close this issue


_body key instead of body in response

Describe the bug
Node.js version: >= 14
OS version: Docker devcontainer with vscode image
Description:
There is a _body key instead of body in response.
I don't know if it's an expected behavior due to recent changes but it's a breaking change for all my tests
Actual behavior
// ./app.js

const express = require('express')
const app = express()
const port = 3000

app.get('/', (req, res) => {
  res.json({
    ok: true,
  })
})

app.listen(port, () => {
  console.log(`Example app listening on port ${port}`)
});

module.exports = app;

// ./tests/app.test.js

const supertest = require('supertest');
const { expect } = require('chai');
const app = require('../app.js');

const server = supertest.agent(app);

describe("Tests", () => {
  it('should return a JSON object', async () => {
    const response = await server.get('/').expect(200);

    console.log({ response });

    expect(response).to.haveOwnProperty('body');
  });
});

Result
  1) Tests
       should return a JSON object:
     AssertionError: expected { Object (_events, _eventsCount, ...) } to have own property 'body'
      at Context.<anonymous> (tests/app.test.js:14:25)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

In the response object there is no "body", only a "_body"

Expected behavior
"body" should be present and test should pass.
Code to reproduce
Here is a replit example<EMAIL_ADDRESS>You just have to run npm test in the shell
Checklist

[x] I have searched through GitHub issues for similar issues.
[x] I have completely read through the README and documentation.
[x] I have tested my code with the latest version of Node.js and this package and confirmed it is still not working.

It works up to version 6.1.6, but from version 2.0.0, it doesn't work anymore.

I am also experiencing this


False Positive on simpleclient_dropwizard-0.6.0.jar

False positive on library simpleclient_dropwizard-0.6.0.jar - reported as cpe:2.3:a:dropwizard:dropwizard:0.6.0:*:*:*:*:*:*:*.
I checked the dependency tree and it shows the following:
compile - Dependencies for source set 'main' (deprecated, use 'implementation' instead).
\--- io.prometheus:simpleclient_dropwizard:0.6.0
     +--- io.prometheus:simpleclient:0.6.0
     \--- io.dropwizard.metrics:metrics-core:3.1.2
          \--- org.slf4j:slf4j-api:1.7.7

The CVE-2020-5245 is only affecting dropwizard-validation.
See also RELEASE 2.0.2 and RELEASE 1.3.19.
If you want to replicate the issue, just use this as a dependency:
dependencies {
    // https://mvnrepository.com/artifact/io.prometheus/simpleclient_dropwizard
    compile group: 'io.prometheus', name: 'simpleclient_dropwizard', version: '0.6.0'

}

<!-- https://mvnrepository.com/artifact/io.prometheus/simpleclient_dropwizard -->
<dependency>
    <groupId>io.prometheus</groupId>
    <artifactId>simpleclient_dropwizard</artifactId>
    <version>0.6.0</version>
</dependency>

I just tested this with 6.0.3-snapshot and it appears to be resolved.


add vertx plugin.

#1417

Current coverage is 39.33% (diff: 6.23%)

Merging #2420 into master will decrease coverage by 1.15%

@@             master      #2420   diff @@
==========================================
  Files          1631       1654     +23
  Lines         57250      58252   +1002
  Methods       11133      11293    +160
  Messages          0          0
  Branches       7887       8099    +212
==========================================
- Hits          23180      22913    -267
- Misses        34070      35339   +1269
  Partials          0          0

Powered by Codecov. Last update 9361474...52cf931


Download folder patch lost

Supermium constantly permanently changes downloads folder
if you open something in online apps
folder with this open file often becomes downloads folder
even? after restart browser

This issue cannot be reproduced, but if the downloads folder is set to the desktop by default, then it will be changed as the desktop is considered "unsafe".


Minor dependency bumps

Bump jacoco-maven-plugin from 0.7.8 to 0.8.3
Bump maven-javadoc-plugin from 2.7 to 3.1.0
Bump maven-resources-plugin from 2.4.3 to 3.1.0
Bump httpcore from 4.4.10 to 4.4.11

Thanks! Will give it a try soon and post here.

Addressed in rewrite or no longer relevant.


Communication on 0.13

0.13 is mostly ready, and it will be quite a milestone. This release rolls out the new dependency injection system (aka providers) and Server-Sent Event support.
It's exciting! — so let's let the world know. Ideas:

Besides the traditional release announcement tweet, write a thread on Twitter with usage tips for providers, SSE, testing utils, the new ASGI middleware, etc.
Publish a blog post on DEV to introduce providers — Bocadillo is now an ASGI framework with dependency injection for endpoints.

Might come in handy: https://bocadilloproject.github.io/blog/ :+1:

Planning to adapt the upcoming chatbot tutorial (see #208) as an article to demonstrate WebSocket, providers, etc.

OK:

Twitter announcement
Personal blog post
DEV post


As a website owner, I want to research and update legal requirements for my website, so that I can ensure compliance with laws and regulations

Acceptance criteria

The website owner can access the legal requirements for their website through a dedicated section on the website and can easily understand the information provided.
The legal requirements listed are up-to-date and accurate, and the website owner can verify their compliance through documentation or other means.
The website owner can update their website to comply with any legal requirements that are not already met and can receive notifications when new legal requirements or changes to existing requirements are identified.
The website owner enters incorrect information, leading to inaccurate legal requirements being listed on the website.
The website owner does not understand the legal requirements listed and does not update their website to comply with them.
The website owner does not receive notifications when new legal requirements or changes to existing requirements are identified, leading to non-compliance with updated laws and regulations.
The resources or support for understanding and complying with legal requirements are not easily accessible or not helpful.

Importance: High
Urgency: Low
Estimation: 1-2 weeks
Resources: legal expertise, research materials, access to relevant laws and regulations
Story Points: 5


Badge suggestion feature fix

Fix for https://github.com/badges/shields/issues/3033
The last working commit with suggestion is 7955f460f37f7cfaa1e9588cb84aa050f2f14275

Screenshots of the last working version

If you want to test this change locally please add a private.gh_token to config/local.yml.
Changes in this PR:

BadgeExamples requires examples instead of definitions (service definitions)
BadgeExamples is able to prepare a real badge as a preview
customization form fills inputs with details of suggested badges
end to end tests

Screenshots after fix

Compare the form above with a form of a regular, non-suggested badge:

I've addressed all issues.

@paulmelnikow thank you for the review

Well done both for working on this - it looks like it was a bit of a monster.
One question:
Since this was merged, we seem to have changed from showing URLs as placeholder in the badge index e.g: :user/:repo to showing example URLs again e.g: badges/shields regardless of whether we're using the suggest feature or not.
Was that an intended change in this PR, or an accident? I can't see a comment on in reading through the review notes here.
Before:

After:

I noticed that too though TBH did not attribute it to this PR. So at least I didn't intend it.
Assuming we're good with returning to patterns, I'd suggest we drop both the hostname and the multiple-choice bits from patterns while we're at it. So :vcsName(github|gh|bitbucket|bb|gl|gitlab) becomes :vcsName, and http://localhost:8080/ goes away.

@chris48s well spotted. I wasn't intended. I will fix this and I will apply Paul's suggestions as well.


[test/plugin] immigrate sofarpc scenario

Please answer these questions before submitting pull request

Why submit this pull request?

[ ] Bug fix

[x] New feature provided

[ ] Improve performance

Related issues
#3583

Bug fix

Bug description.

How to fix?

New feature or improvement

Describe the details and related test reports.

Group 1 seems having slots still.


build(deps): update Arrow/Parquet to 52.0, object-store to 0.10

Which issue does this PR close?

Closes #.
Rationale for this change

Previous one: https://github.com/apache/datafusion/pull/9613
Arrow release ticket: https://github.com/apache/arrow-rs/issues/5688

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

Okay, the one last thing is to update Cargo.toml after arrow 52.0 is published. This PR itself is ready for review.

Epic!

@waynexia It looks like you need to run cargo update in datafusion-cli to fix CI

I merged up from main and updated the lock file

Thanks for reviewing!

@waynexia I was inspecting the dependency tree for delta-rs and it seems the dependency didn't get bumped for object-store in proto-common fyi, so 0.9.1 gets pulled.
object_store v0.9.1
└── datafusion-proto-common v39.0.0 (https://github.com/apache/datafusion?tag=39.0.0-rc1#6a4a280e)
    └── datafusion-proto v39.0.0 (https://github.com/apache/datafusion?tag=39.0.0-rc1#6a4a280e)
        └── deltalake-core v0.18.0 (/Users/abhiagarwal/Developer/delta-rs/crates/core)
            ├── deltalake v0.18.0 (/Users/abhiagarwal/Developer/delta-rs/crates/deltalake)
            │   └── deltalake-python v0.18.0 (/Users/abhiagarwal/Developer/delta-rs/python)
            ├── deltalake-aws v0.1.2 (/Users/abhiagarwal/Developer/delta-rs/crates/aws)
            │   └── deltalake v0.18.0 (/Users/abhiagarwal/Developer/delta-rs/crates/deltalake) (*)
            ├── deltalake-azure v0.1.2 (/Users/abhiagarwal/Developer/delta-rs/crates/azure)
            │   └── deltalake v0.18.0 (/Users/abhiagarwal/Developer/delta-rs/crates/deltalake) (*)
            ├── deltalake-catalog-glue v0.1.0 (/Users/abhiagarwal/Developer/delta-rs/crates/catalog-glue)
            │   └── deltalake v0.18.0 (/Users/abhiagarwal/Developer/delta-rs/crates/deltalake) (*)
            ├── deltalake-gcp v0.2.1 (/Users/abhiagarwal/Developer/delta-rs/crates/gcp)
            │   └── deltalake v0.18.0 (/Users/abhiagarwal/Developer/delta-rs/crates/deltalake) (*)
            └── deltalake-mount v0.1.0 (/Users/abhiagarwal/Developer/delta-rs/crates/mount)
                └── deltalake-python v0.18.0 (/Users/abhiagarwal/Developer/delta-rs/python)

Sorry for causing this! Opened https://github.com/apache/datafusion/pull/10848 to fix it.

All good, just wanted to bring it to your attention before 39 formally drops :)

All good, just wanted to bring it to your attention before 39 formally drops :)

FYI @andygrove  -- maybe this means we should make another RC for 39.0.0 🤔
We could also potentially make a 39.1.0 release too with this dependency upgrade fix https://github.com/apache/datafusion/pull/10848


HOTA seems to have non-intuitive association score properties

Consider as a thought experiment a ground truth object and two prediction cases.
Case 1: Detections are predicted that perfectly match the ground truth object positions. The first 90% have ID a, and the last 10% have random IDs. HOTA dictates that 90% are TPAs and 10% are FPAs so association component of HOTA is 0.9
Case 2: Detections are predicted that perfectly match the ground truth object positions. The first 50% have ID a, and the last 50% have ID b. HOTA dictates that 50% are TPAs and 50% are FPAs so association component of HOTA is 0.5.
To me, it is not intuitive that one of these cases is vastly superior to another, or if anything Case 2 indicates intuitively "better" performance. It would seem intuitive that for a very long ground truth track, one might expect the predictions that are associated with that track to be fragmented (multiple IDs assigned). It seems a bit strange to only score the longest such fragment as TPAs and to score all other associated fragments as FPAs. In most hard tracking problems fragmentation is almost guaranteed. Thus, I find the association component of HOTA not that useful as defined.
Can you provide a justification for this choice, or, if I am misunderstanding something, a clarification for the actual calculation? The definitions in the original paper are at times a bit hard to follow because c and k are never explicitly defined.

You are misunderstanding one thing:
The 'not best' ID, DOES contribute.
Let's take 4 cases (all with perfect detection), all having a length of 1000:
a) 500 with ID A, the rest of the 500 with each a unique ID per detection.
b) 500 with ID A, the rest of the 500 with ID B
c) 900 with ID A, the rest of the 100 with each a unique ID per detection.
d) 900 with ID A, the rest of the 100 with ID B
The AssA scores for these are:
a) 0.50.5 + 0.50.001 = 0.2505
b) 0.50.5 + 0.50.5 = 0.5
c) 0.90.9 + 0.10.001 = 0.8101
d) 0.90.9 + 0.10.1 = 0.82
Each of the above are calculated as such:
sum_IDs (percent_of_dets * correctness_of_dets_ass)
So the difference is not 0.5 vs 0.9 as you say, but 0.5 vs 0.81
The reason for the problem you are highlighting, is that the score is 'normalized' over the number of detections. E.g. here HOTA is about 'how much is each detection correct'. There is an easy adaptation to normalize over 'tracks'/'IDs', which would have the property you desire, but isn't really applicable in every situation.

Is there a HOTA version where we have much more similar scores for b and c cases? My task is more sensitive to the number of ID switches than to the relation between tracks' lengths

As you said in an earlier comment (that I can no longer see), the Fragmentation-Aware HOTA might be what you are looking for here.

As you said in an earlier comment (that I can no longer see), the Fragmentation-Aware HOTA might be what you are looking for here.

Is it implemented in your code? I cannot find it anywhere


[Bug]: Error when opening Chinese name function when ob version is 425

ODC version
odc433
OB version

What happened?

What did you expect to happen?
Interface does not return error message
How can we reproduce it (as minimally and precisely as possible)?
Open the function with Chinese name
Anything else we need to know?
No response

Looks like a sql parser bug. Cannot be repeated, provide the  specific sql


How do I send notifications to a at a set time every day without the user being on my website?

When I initially set this up I had to first set this up the notification appears when ever the site is loaded, but I was to send push notifications to the user every day at a set time also while they are not on the website?

I believe you could do this with the service worker and a setTimeout call.

Push.js facilitates in creation of notification. In essence, it provides cross-browser wrappers over the Notification API.
How and when you create the notification is part of your application's logic. There are many ways you can achieve that. I can propose two:

Using the ServiceWorker to create a notification at an specific time.
Sending a push from you server


(PUP-10059) fix package not installed check

dpkg provider package_not_installed? method was not correctly handling the case in which dpkg-query returns unknown ok not-installed.
it was rewritten to use query method as interface to dpkg-query

jenkins please test this on
debian8-64a,debian8-32a,debian9-64a,debian9-32a,ubuntu1604-64a,ubuntu1604-32a,ubuntu1804-64a

CLA signed by all contributors.

Can you update the git commit message with the text from the PR summary?


EKF2 external vision, yaw divergence issue

I use EKF2 estimator with external vision input(MOCAP or msf vision pose).
But sometimes yaw angle of pixhawk(only yaw) is diverged.(0 -> 360 or 360 -> 0)
This is flight log when yaw angle divergence.
https://review.px4.io/plot_app?log=6e7040c7-7a5c-44d8-89b5-80084aa61f33
My system is as follows.

Pixhawk firmware 1.8.0
Pixhawk platform is 2.1(cube)
EKF2 parameter set

EKF2_AID_MASK 24
EKF2_HGT_MODE 3
EKF2_MAG_TYPE 4
EKF2_EV_DELAY 0

use internal magnetometer(but when I use external magnetometer, divergence is also same)
I use MSF with external distance range sensor, 2D lidar, mono camera and IMU of Pixhawk.

Even I have tried replacement pixhawk platform, pixhawk3, pixhawk4, pixhawk2.
But every pixhawk is same result.
The ratio between normal and divergent is almost the same, and in the case of divergence,
it may be okay to turn off the system and turn on and off again.
In the past, I was using the INAV estimator on the pixhawk 1 platform(firmware ver. 1.4.4),
but since pixhawk1 was discontinued, I can not use it anymore. So I have to change it to EKF2
I've been suffering from this problem for almost a month. I ask for your help.

I have a similar problem. I am also using EKF2 estimator with external vision input.
What I see is that sometimes when I startup, the yaw (read from mavros/local_position/pose) is 180 degree rotated compared to what I send (mavros/vision_pose/pose). In that case it is impossible to fly the drone, because it is correcting to the wrong direction.
The strange thing is that the error does not always occur, it is random.
@Heojongbeom can this be the same problem as you described?
Does anyone else see this problem? Any suggestion?

Hi,
I have disabled the magnetometers. It works without magnetometers. EFK2 does output local pose.
I use this settings (don't know if they are all necessary, but it works)
CAL_MAG0_EN disabled
EFK2_MAG_TYPE None
SYS_HAS_MAG disabled
The vision position and yaw is send correctly to the px4. It takes the position correctly, but the yaw is sometimes 180 degree inverted.
I am using Pixhawk 3Pro with px4 firmware Version 1.8.0dev.

The combination of EKF2_MAG_TYPE 4 and EKF2_AID_MASK 24 is untested. I will look at the code for this in more detail this week.

Hi
I have tested disabled the magnetometers that you told me, but it still
does not work...
The motion capture data(position and yaw) is send to PX4, but PX4 local
pose does not out...
However
CAL_MAG0_EN enabled
EFK2_MAG_TYPE None
SYS_HAS_MAG disabled
This combination works well, I can't disable all magnetometers
2018년 11월 7일 (수) 오후 6:04, Gerlach<EMAIL_ADDRESS>작성:

Hi,
I have disabled the magnetometers. It works without magnetometers. EFK2
does output local pose.
I use this settings (don't know if they are all necessary, but it works)
CAL_MAG0_EN disabled
EFK2_MAG_TYPE None
SYS_HAS_MAG disabled
The vision position and yaw is send correctly to the px4. It takes the
position correctly, but the yaw is sometimes 180 degree inverted.
I am using Pixhawk 3Pro with px4 firmware Version 1.8.0dev.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PX4/Firmware/issues/10581#issuecomment-436553171, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AkO8KSWIYJHSjlttgMRVJzOADVEdlLKgks5usqIfgaJpZM4W7tw3
.


iOS - To extend NSProtocol  and override methods in Native-script Plugin which is created in iOS Native Framework

What we are expecting?
In one of our Native script application, We made one framework using Native iOS Code and wants to send some data from Native iOS Framework to Native script Plugin.
Now in Native script plugin, we wants to extend Native iOS NSProtocol so we can override methods of our custom iOS NSProtocol.
We search for the use of Protocol delegate in Native script but there is only syntax available which can create NSProtocol and implements it in Native script only and our requirement is to create NSProtocol in iOS Framework and implements it’s methods in Native script.
Please suggest us a proper way or syntax to implement it.
Thanks in advance!

Hello,
You can take a look at these two sections for examples on how to implement protocols from JS and TS: https://docs.nativescript.org/core-concepts/ios-runtime/how-to/ObjC-Subclassing#calling-base-methods-Protocol and https://docs.nativescript.org/core-concepts/ios-runtime/how-to/ObjC-Subclassing#typescript-support
I hope this helps! :)

Hello @mbektchiev,
Thanks for the quick reply but i already go through with this links and it wasn't work in our case.
We wants to extend custom protocol which is made in Native iOS .framework.
can you please help me by providing an example with custom protocol?

The syntax is the same. It doesn't matter whether the protocol is custom or system. You can see the iOS runtime's test cases here: Protocol implementation and Protocol definition

Hello @mbektchiev ,
I am facing an issue like Delegate name can not be found in when extending protocol.
public MyObject = (NSObject as any).extend({
    GetBytes: function(arr: any) {
        let self = this.super.GetBytes();
        if (self) {
            // The base class initialized successfully
            console.log("Initialized");
        }
        return self;
    }
  },
    {
      name: "NativeBluetoothCode",
      protocols: [BLECommunicationDelegate]
    }
);
![Screenshot 2020-04-02 at 9 45 01 PM](https://user-images.githubusercontent.com/59596311/78272535-4337df00-752b-11ea-91d4-b33aeefbb981.png)

is it correct way to do it or not?

You seem to have not generated typings (.d.ts files) for your plugin. Follow these instructions to do it: https://docs.nativescript.org/plugins/Use-Native-iOS-Libraries#generating-typescript-typings
In the meantime you can nevertheless access the protocol from TS, you just have to make the compiler happy by replacing BLECommunicationDelegate with global["BLECommunicationDelegate"] or (<any>global).BLECommunicationDelegate

Hello @mbektchiev ,
I tried as per your suggestions, but still i am getting below error:

JS ERROR Error: The protocols property must be an array

can you please guide me how i can solve this?
for your knowledge only, currently method does not contains any params still i am getting this error.
My code is
public MyObject = (NSObject as any).extend({
    GetBytes: function() {
        let self = this.super.GetBytes();
        if (self) {
            // The base class initialized successfully
            console.log("Initialized");
        }
        return self;
    }
  },
    {
      name: "NativeBluetoothCode1",
      protocols: global["BLECommunicationDelegate"]
    }
);

As the error states you'll have to make the protocols property an array:  protocols: [global["BLECommunicationDelegate"]]

I tried the following code but it's now throwing an exception that is the "unrecognized selector sent to instance".
declare var iOSBluetoothProtocol: any
public NativeBluetoothCode1 = (NSObject as any).extend({
     TestNotifDelegate: function () {
          console.log("TestNotifDelegate called in Plugin");
        }
    }, {
name: "NativeBluetoothCode1",
        protocols: [iOSBluetoothProtocol]
    });

even I am not able to use NSObject and this is an error we received, Cannot find the name 'NSObject'. Did you mean 'Object'?
Here, can you help me to fix an issue?

I assume that this error is coming from the TypeScript compiler. One possible reason could be that you haven't included the NativeScript's typings declarations. Can you install as an NPM dev dependency this module: https://www.npmjs.com/package/tns-platform-declarations and follow the instructions in the README, namely:

Create reference.d.ts and add the following content:
/// <reference path="./node_modules/tns-platform-declarations/ios.d.ts" />
/// <reference path="./node_modules/tns-platform-declarations/android.d.ts" />


Fixed wrong variable name on assertNotNullOrEmpty_

While testing the workflow, the gulp upload-latest --env=test step displayed a warning:
src\tests\lib.testing.js
  line 68  col 24  'message' used out of scope.

  ‼  1 warning

I signed it!
On Fri, Jul 8, 2016 at 12:51 PM, googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project. Before we can look at your
pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll
verify. Thanks.

If you've already signed a CLA, it's possible we don't have your
GitHub username or you're using a different email address. Check your
existing CLA data https://cla.developers.google.com/clas and verify
that your email is set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
If you signed the CLA as a corporation, please let us know the
company's name.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/google-apps-script-samples/pull/19#issuecomment-231331539,
or mute the thread
https://github.com/notifications/unsubscribe/AAc4UTTemhsFTOJXHf2hiR_HlbLxT-Rnks5qTiudgaJpZM4JH7Jz
.


Support not specifying integration alias

Notice that this code will fail to understand an integration declared with an
alias and which needs to be configured with only one argument whose value is a
dictionary:
notify:
    my-alias:
        the-integration-name:
            the-only-argument:
                a-dict-key: 'a dict value'
                another-dict-key: 'another dict value'
                yet-another-dict-key: 'yet another dict value'

I believe this is so far an unlikely scenario, because if the value needs to be
a dictionary, you might as well allow it to be inlined at the argument level,
like so:
notify:
    my-alias:
        the-integration-name:
            a-dict-key: 'a dict value'
            another-dict-key: 'another dict value'
            yet-another-dict-key: 'yet another dict value'

and supporting it would make the problem far harder to solve without changing
the integration declaration schema.

Nice! — I was just thinking about working on this. I'll need some time to take a better look at it though

Well, I finally found some time to review this — I upgraded to python 3.5 (forgot about this) so I had to rebuild some things to get the project working again.
This change seems to fail when integrations don't take any parameters, like the terminal integration:
Traceback (most recent call last):
  File "/.../pysellus/pysellus/core.py", line 34, in <module>
    main()
  File "/.../pysellus/pysellus/core.py", line 24, in main
    integration_config.load_integrations(user_input)
  File "/.../pysellus/pysellus/integration_config.py", line 23, in load_integrations
    _load_integrations_from_configuration(integrations_configuration)
  File "/.../pysellus/pysellus/integration_config.py", line 53, in _load_integrations_from_configuration
    kwargs_for_integration_constructor
  File "/.../pysellus/pysellus/integration_config.py", line 92, in _get_integration_instance
    return integration_class(**kwargs_for_integration_constructor)
TypeError: object() takes no parameters

This seems to be the problem:
def _get_integration_instance(name, kwargs_for_integration_constructor):
    try:
        integration_class = integration_classes[name]
    except KeyError:
        print("The '{}' integration does not exist\nAborting...".format(name))
        exit(1)

    return integration_class(**kwargs_for_integration_constructor)  # <- object() takes no parameters

Printing kwargs_for_integration_constructor at that points (for terminal) gives us: {'terminal': None} for a configuration like:
...
'terminal':
    terminal:
...

If we omit the 'terminal' alias, this pops up instead:
Traceback (most recent call last):
  File "/.../pysellus/pysellus/core.py", line 34, in <module>
    main()
  File "/.../pysellus/pysellus/core.py", line 24, in main
    integration_config.load_integrations(user_input)
  File "/.../pysellus/pysellus/integration_config.py", line 23, in load_integrations
    _load_integrations_from_configuration(integrations_configuration)
  File "/.../pysellus/pysellus/integration_config.py", line 50, in _load_integrations_from_configuration
    in unpack_integration_configuration_data(integrations_configuration):
  File "/.../pysellus/pysellus/integration_config.py", line 59, in unpack_integration_configuration_data
    if _has_only_one_key_and_a_dict_as_value(child):
  File "/.../pysellus/pysellus/integration_config.py", line 70, in _has_only_one_key_and_a_dict_as_value
    return len(a_dict.keys()) == 1 and type(a_dict[_get_the_only_key_in(a_dict)]) is dict
AttributeError: 'NoneType' object has no attribute 'keys'

All right, with your PR merged I believe this is ready.

Everything looks good now.
I've also tested the issue you mentioned about failing for single dictionary parameters and everything works as expected, so that's great!


fix #1237

While fixing I realized that also analysis.biom_tables will return None vs. [] so fixed.

Thanks @antgonza
Do any of these changes impact the interface? i.e. there isn't any check in the interface for the result of these calls being None. If so, that code should be removed. Otherwise :+1:

AFAIK there are no checks in the interfase, which cause the problem.

Thanks! :+1:

Coverage increased (+0.01%) to 78.69% when pulling 73f7627362f0f1990d45c0d71e6a8f668e863fea on antgonza:issue-1237 into 906a55653ae8f8abd4f13e96ac52f177ba9a5470 on biocore:master.

:+1: ready for merge once tests pass.

Coverage increased (+0.01%) to 78.69% when pulling 92f66d0945adaca64f94b57fc674734b5b1e43b7 on antgonza:issue-1237 into 906a55653ae8f8abd4f13e96ac52f177ba9a5470 on biocore:master.

Coverage increased (+0.01%) to 78.69% when pulling 92f66d0945adaca64f94b57fc674734b5b1e43b7 on antgonza:issue-1237 into 906a55653ae8f8abd4f13e96ac52f177ba9a5470 on biocore:master.


Missing data due to differences in reporting dv

We set up this pipeline to pull down daily value data for all active gages. Unfortunately, we learned that our assumption that the "mean" stat code (00003) would be used if there was any dv data was wrong. The stat code used to report daily groundwater varies widely by state (see map below). Thus, in the current setup where we use stat_cd = "00003", we are missing huge swaths of GW sites and entire states.
We will likely need to switch over to generating a daily value from instantaneous data. Could save some processing time by only doing this for sites without the dv data already. That is similar to how national-flow-observations is setup. This change will also need to happen for how the historic data was generated.

Code used to generate this map (need to run in pipeline):
# Why does it seem like we are missing so many sites across the country?
# E.g. there are none in OH but OH has real-time sites on GWW
# https://groundwaterwatch.usgs.gov/StateMap.asp?sa=OH&sc=39

# This OH site has real time daily data for 72019 but only stat code 00001 (max)
# It also has `uv` for 72019. I suppose we could do all of our data pulls for
#   `uv` and then make our own summary ...
x <- whatNWISdata(siteNumber = "383638082103300")

# What other sites are we missing that have `00001` instead?

source("1_fetch/src/fetch_nwis.R")

fetch_gw_sites("sites_max.rds", "2020-10-01", "2020-12-31",
               c(-124.409591, 24.523096, -66.949895, 49.384358),
               param_cd = '72019', stat_cd = '00001')
fetch_gw_site_info("sites_max_info.csv", "sites_max.rds")

# Do the same but for `00002`

fetch_gw_sites("sites_min.rds", "2020-10-01", "2020-12-31",
               c(-124.409591, 24.523096, -66.949895, 49.384358),
               param_cd = '72019', stat_cd = '00002')
fetch_gw_site_info("sites_min_info.csv", "sites_min.rds")

# Also, which have `uv`??
fetch_gw_sites("sites_uv.rds", "2020-10-01", "2020-12-31",
               c(-124.409591, 24.523096, -66.949895, 49.384358),
               param_cd = '72019', service = 'uv')
fetch_gw_site_info("sites_uv_info.csv", "sites_uv.rds")

proj_str <- scmake("proj_str")
convert_to_sf <- function(data, proj) {
  data %>%
    st_as_sf(coords = c("dec_long_va", "dec_lat_va"), crs = "+proj=longlat +datum=WGS84") %>%
    st_transform(proj_str)
}

# Now map & compare
fy20q1_mean_sites <- read_csv("1_fetch/out/gw_site_info.csv", col_types = "cccnn") %>% convert_to_sf(proj_str)
fy20q1_min_sites <- read_csv("sites_min_info.csv", col_types = "cccnn") %>% convert_to_sf(proj_str)
fy20q1_max_sites <- read_csv("sites_max_info.csv", col_types = "cccnn") %>% convert_to_sf(proj_str)
fy20q1_uv_sites <- read_csv("sites_uv_info.csv", col_types = "cccnn") %>% convert_to_sf(proj_str)

usa_sf <- st_as_sf(maps::map('state', fill=TRUE, plot=FALSE)) %>% st_transform(proj_str)

cols_to_use <- viridis::viridis(4)

par(mar = c(0,0,0,0))
plot(st_geometry(usa_sf), col = "#fcf8e8", border = "lightgrey", bg = "grey")
plot(st_geometry(fy20q1_uv_sites), col = cols_to_use[4], cex = 0.8, pch = 20, add=TRUE)
plot(st_geometry(fy20q1_min_sites), col = cols_to_use[2], cex = 0.8, pch = 20, add=TRUE)
plot(st_geometry(fy20q1_max_sites), col = cols_to_use[3], cex = 0.8, pch = 20, add=TRUE)
plot(st_geometry(fy20q1_mean_sites), col = cols_to_use[1], cex = 0.8, pch = 20, add=TRUE)
legend("bottomleft", pch = 20, cex = 0.8, col = cols_to_use[c(4, 3, 2, 1)], bty = "n",
       legend = c("UV only", "DV 00002 (min)", "DV 00001 (max)", "DV 00003 (mean)"),
       title = "Service queried (listed in\norder added to map)")
title(main = "Available FY20 Q1 GWL Data\nby Service & Stat Code Type",
      line = -3.5, cex.main = 1.5)

There is also an issue with the parameter code used being different per state!

# 62610 (Groundwater level above NGVD 1929, feet)
# 62611 (Groundwater level above NAVD 1988, feet)
# 72019 (Depth to water level, feet below land surface)
# 72020 (Elevation above NGVD 1929, feet)
# 72150 (Groundwater level relative to Mean Sea Level (MSL), feet)
# 72226 (Groundwater level above American Samoa Datum of 1962 (retired in 2001), feet)
# 72227 (Groundwater level above American Samoa Vertical Datum of 2002, feet)
# 72228 (Groundwater level above Guam Vertical Datum of 1963 (retired in 2003), feet)
# 72229 (Groundwater level above Guam Vertical Datum of 2004, feet)
# 72230 (Groundwater level above Local Hawaiian Datum, feet)
# 72231 (Groundwater level above Northern Marianas Vertical Datum of 2003, feet)

library(dataRetrieval)
library(tidyverse)
library(sf)

inventory_sites <- function(pcodes) {
  hucs <- zeroPad(1:21, 2) # all hucs

  sites <- tibble()
  for(huc in hucs){
    message(sprintf("Trying HUC %s ...", huc))
    sites <- tryCatch(
      whatNWISdata(huc = huc,
                   startDate = "2020-10-01",
                   endDate = "2020-12-31",
                   siteType = "GW",
                   parameterCd = pcodes) %>%
        select(site_no, dec_lat_va, dec_long_va, data_type_cd,
               parm_cd, stat_cd, begin_date, end_date, count_nu),
      error = function(e) return()
    ) %>% bind_rows(sites)
  }

  return(sites)
}

proj_str <- "+proj=laea +lat_0=45 +lon_0=-100 +x_0=0 +y_0=0 +a=6370997 +b=6370997 +units=m +no_defs"
convert_to_sf <- function(data, proj) {
  data %>%
    st_as_sf(coords = c("dec_long_va", "dec_lat_va"), crs = "+proj=longlat +datum=WGS84") %>%
    st_transform(proj_str)
}
usa_sf <- st_make_valid(st_as_sf(maps::map('state', fill=TRUE, plot=FALSE))) %>% st_transform(proj_str)

####################

all_gw_params <- c("62610", "62611", "72019", "72020", "72150", "72226",
                   "72227", "72228", "72229", "72230", "72231")
all_data <- inventory_sites(all_gw_params)
all_data_sf <- all_data %>%
  # Only keep real-time data, so only "uv" or "dv"
  filter(data_type_cd != "gw") %>%
  # Keep the largest data series parameter
  group_by(site_no) %>%
  filter(count_nu == max(count_nu)) %>%
  ungroup() %>%
  filter(!is.na(dec_lat_va), !is.na(dec_long_va)) %>%
  convert_to_sf(proj_str) %>%
  st_make_valid()

all_data_conus_sf <- st_intersection(all_data_sf, usa_sf)
cols_to_use <- viridis::viridis(length(unique(all_data_conus_sf$parm_cd)))
ggplot(all_data_conus_sf, aes(color = parm_cd)) +
  geom_sf(data = usa_sf, fill = "#fcf8e8", color = "lightgrey") +
  geom_sf(size = 3, stroke = 0, shape = 16, alpha = 0.5) +
  scale_color_manual(values = cols_to_use) +
  guides(color=guide_legend(title="pcode with\nmost obs",
                            override.aes = list(size = 5,alpha = 1))) +
  ggtitle("Sites with real-time gw data") +
  theme_void() +
  theme(plot.background = element_rect(fill = "grey", color = NA),
        panel.background = element_rect(fill = "grey", color = NA),
        plot.title = element_text(size = 40, face = "bold", hjust = 0.5, vjust = 0),
        legend.title=element_text(size=20, face = "bold"),
        legend.text=element_text(size=15))

Even though these sites are using different parameter codes, I think we can still compare their quantiles to each other because we would be saying the groundwater level is above/below X percent of other days in its historic record regardless of whether that is level above NAVD 1988 or Depth to water level, right?
If that is the case, then I think we need a step that constructs a table of site number + query parameters (dv/uv, parameter code, stat code if applicable) and use that to group and query chunks at a time. Then, they can all use their respective "value" columns to calculate percentiles, perhaps leaning on the HASP::site_data_summary function.

Yes - I agree with that general sentiment. The percentile is standardized so the interpretation stays the same. This becomes more important if we want to show actual gwl vs within-site variation.
But I also wonder if level above vs depth to water reflects a different direction of the measurement, so that the trends would be inverted if compared between parameter codes. Like, if it's level above and it's increasing that would reflect higher gwl than usual. Then if its depth to water level and increasing, the gwl are getting lower overall (but the magnitude is increasing).
Did you look any deeper at sites with multiple parameter codes? I wonder why that would be, especially if given those two codes mentioned above. One way to answer my question would be to look at a site with both codes and see if they are showing the same trend direction. That would only be possible if there are multiple parameter codes across the same time period, which idk if there are. That might be a good question to ask though because if they are, it makes sense to filter to the most common one. But if they are temporally segregated, then it might be valuable to include both.

I think level above vs depth to water are inverted, but hard to know for sure. Will dig in a bit more. If they are, then we could solve this way:
# Issue with these param codes used in FL is that they are the inverse of 72019 (which is everywhere else)
# Where they are "level above" some elevation compared to "level below surface"

gw_levels <- c(5, 8, 3, 15, 12, 14, 9, 11, 7)

# If depth ABOVE, then bigger numbers = more GW
quantile(gw_levels, probs = c(0.25, 0.75))

# If depth BELOW, then bigger numbers = less GW
quantile(-gw_levels, probs = c(0.25, 0.75))

# By negating the "depth below" values, we will end up with 25the %ile values that
# mean the well is experiencing lower than normal water and 75th %ile values that
# mean the well is experiencing higher than normal water. I think hat would make it
# possible to compare across the gages that have different parameters.

This makes sense to me. We may want to revisit down the line if we want to show magnitude using actual values in some way, but at the moment I don't see a need for it

Digging to get KS & FL data (because none comes back for 72019). Both have some sites that 62610, so I started exploring those. Naturally, all but 5 of the FL sites report daily 62610 using only max. So, we will need to use UV instead and calculate our own daily means. KS is similar, but the values reported in the "daily" service are actually instantaneous values taken at noon (stat_cd == '31200'). So again, we will need to download UV and calculate a daily mean.
Path forward: Create special targets in 0_historic & 1_fetch that download UV 62610 data for FL/KS, summarize to a daily mean, and then include in the quantile calculation. Be sure to implement the negation (as noted in https://github.com/USGS-VIZLAB/gw-conditions/issues/9#issuecomment-854115170) for the "depth below" (72019) values.
Florida and pcode = 62610
library(dataRetrieval)
library(dplyr)
library(sf)

# What daily data does FL have for 62610?
fl_dv_sites <- whatNWISdata(stateCd = "FL", parameterCd = "62610", service="dv")
length(unique(fl_dv_sites$site_no))
# [1] 411
sum(fl_dv_sites$stat_cd == "00003") # Most report daily values using max (00001)
# [1] 5

# What about UV?
fl_uv_sites <- whatNWISdata(stateCd = "FL", parameterCd = "62610", service="uv")
length(unique(fl_uv_sites$site_no))
# [1] 362

sum(!unique(fl_dv_sites$site_no) %in% unique(fl_uv_sites$site_no)) # 50 sites with DV but not UV
# [1] 50
sum(!unique(fl_uv_sites$site_no) %in% unique(fl_dv_sites$site_no)) # 1 site with UV but not DV
# [1] 1

# Choosing UV and then averaging to daily mean, we will lose 50 sites (in green on the map) and gain one
fl_sf <- st_as_sf(maps::map('state', region = "florida", fill=TRUE, plot=FALSE))
fl_dv_sites_sf <- st_as_sf(fl_dv_sites, coords = c("dec_long_va", "dec_lat_va"), crs = "+proj=longlat +datum=WGS84")
fl_uv_sites_sf <- st_as_sf(fl_uv_sites, coords = c("dec_long_va", "dec_lat_va"), crs = "+proj=longlat +datum=WGS84")

par(mar = c(0,0,0,0))
plot(st_geometry(fl_sf), col = "#fcf8e8", border = "lightgrey", bg = "grey")
plot(st_geometry(fl_dv_sites_sf), col = "#35B779FF", cex = 0.8, pch = 20, add=TRUE)
plot(st_geometry(fl_uv_sites_sf), col = "#440154FF", cex = 0.8, pch = 20, add=TRUE)
title(main = "Available FL GW Data for\npcode=62019 & service=uv",
      sub = "Green = sites with DV, but not UV",
      line = -3.5, cex.main = 1.5)

Kansas and pcode = 62610
ks_dv_sites <- whatNWISdata(stateCd = "KS", parameterCd = "62610", service="dv")
length(unique(ks_dv_sites$site_no))
# [1] 20
unique(ks_dv_sites$stat_cd)  # KS is reporting a "daily value" using an instaneous observation at noon
# [1] "31200"

# What about UV?
ks_uv_sites <- whatNWISdata(stateCd = "KS", parameterCd = "62610", service="uv")
length(unique(ks_uv_sites$site_no))
[1] 14

sum(!unique(ks_dv_sites$site_no) %in% unique(ks_uv_sites$site_no)) # 6 sites with DV but not UV
# [1] 6
sum(!unique(ks_uv_sites$site_no) %in% unique(ks_dv_sites$site_no)) # 0 site with UV but not DV
# [1] 0

# Choosing UV and then averaging to daily mean, we will lose 6 sites (in green on the map)
ks_sf <- st_as_sf(maps::map('state', region = "kansas", fill=TRUE, plot=FALSE))
ks_dv_sites_sf <- st_as_sf(ks_dv_sites, coords = c("dec_long_va", "dec_lat_va"), crs = "+proj=longlat +datum=WGS84")
ks_uv_sites_sf <- st_as_sf(ks_uv_sites, coords = c("dec_long_va", "dec_lat_va"), crs = "+proj=longlat +datum=WGS84")

par(mar = c(0,0,0,0))
plot(st_geometry(ks_sf), col = "#fcf8e8", border = "lightgrey", bg = "grey")
plot(st_geometry(ks_dv_sites_sf), col = "#35B779FF", cex = 0.8, pch = 20, add=TRUE)
plot(st_geometry(ks_uv_sites_sf), col = "#440154FF", cex = 0.8, pch = 20, add=TRUE)
title(main = "Available KS GW Data for\npcode=62610 & service=uv",
      sub = "Green = sites with DV, but not UV",
      line = -3.5, cex.main = 1.5)

Back at this but now for Hawaii.
gw_pcodes <- c("62610","62611","72019","72020","72150","72226",
              "72227","72228","72229","72230","72231")

hi_data <- whatNWISdata(stateCd = "HI",
             startDate = "2020-10-01",
             endDate = "2020-12-31",
             siteType = "GW",
             parameterCd = gw_pcodes) %>%
  select(site_no, dec_lat_va, dec_long_va, data_type_cd,
         parm_cd, stat_cd, begin_date, end_date, count_nu)

hi_data %>%
  group_by(parm_cd, data_type_cd) %>%
  summarize(ncounts = sum(count_nu),
            nsites = n(), .groups="keep")

# A tibble: 6 x 4
# Groups:   parm_cd, data_type_cd [6]
  parm_cd data_type_cd ncounts nsites
  <chr>   <chr>          <dbl>  <int>
1 72019   gw              9664     60
2 72019   qw                 5      1
3 72020   qw              2708      6
4 72150   dv            117922     27
5 72150   gw              9691     60
6 72150   uv            106566     40

In the pulls, we are pulling from dv & uv services, which means that for HI we need to add a special pull since it doesn't use the most common pcode, 72019, and instead uses 72150 (Groundwater level relative to Mean Sea Level (MSL), feet) for the uv and dv services.

To be able to relate the values from 72150 to our "depth to water level", I can convert to depth to water level by subtracting out the land surface elevation. This value is stored in the site metadata as alt_va. I tested one site to confirm:
library(dataRetrieval)
library(dplyr)

site <- "190423155371501"
site_info <- readNWISsite(site)
site_gw_data <- readNWISdv(siteNumber = site, parameterCd = "72150",
                           startDate = "2021-09-01", endDate = "2021-09-10")

site_gw_data %>%
  select(Date, gw_relative = X_72150_00003) %>%
  mutate(depth_to_wl = site_info$alt_va - gw_relative)

         Date gw_relative depth_to_wl
1  2021-09-01     1015.05      284.21
2  2021-09-02     1015.04      284.22
3  2021-09-03     1015.04      284.22
4  2021-09-04     1015.03      284.23
5  2021-09-05     1015.03      284.23
6  2021-09-06     1015.02      284.24
7  2021-09-07     1015.02      284.24
8  2021-09-08     1015.01      284.25
9  2021-09-09     1015.01      284.25
10 2021-09-10     1015.00      284.26

As a check, I can see that the resulting depth_to_wl values calculated above line up with the second y-axis in this graph on NWISWeb. 👍  nice!


snakemake version 7.18.2 crashes with group rules

I am currently working on some fixes for the MultiQC reporting. While doing so, I wanted to update MultiQC version to its most recent, since the issue I submitted: https://github.com/ewels/MultiQC/issues/1645 seems to have been fixed.
I created a fresh environment for this with MultiQC 1.13, but now when I run with the test data I get:
UnknownRuleException:
There is no rule named compute_scaling_factors_group_group2.

When comparing I notice that snakemake-minimal also got updated to 7.18.2. With the older environment the workflow succeeds, so I guess there is some change in how snakemake handles rule groups or rule names that makes this crash now, but I am uncertain about whether it is a workflow issue, or a snakemake issue. For the time being I will probably pin snakemake version on environment.yaml to one that works until I find out what the origin of the issue is.
Additional note on this is that there is some intermediate version of snakemake-minimal that trashes output from failed rules under the run: directive: https://github.com/snakemake/snakemake/issues/1698 that gives me headaches if something crashes there, so I will probably pin the version on some intermediate that makes both things work (if such configuration exists).

I am currently working on some fixes for the MultiQC reporting. While doing so, I wanted to update MultiQC version to its most recent, since the issue I submitted: ewels/MultiQC#1645 seems to have been fixed.
I created a fresh environment for this with MultiQC 1.13, but now when I run with the test data I get:
UnknownRuleException:
There is no rule named compute_scaling_factors_group_group2.

When comparing I notice that snakemake-minimal also got updated to 7.18.2. With the older environment the workflow succeeds, so I guess there is some change in how snakemake handles rule groups or rule names that makes this crash now, but I am uncertain about whether it is a workflow issue, or a snakemake issue. For the time being I will probably pin snakemake version on environment.yaml to one that works until I find out what the origin of the issue is.
Additional note on this is that there is some intermediate version of snakemake-minimal that trashes output from failed rules under the run: directive: snakemake/snakemake#1698 that gives me headaches if something crashes there, so I will probably pin the version on some intermediate that makes both things work (if such configuration exists).

Hello！I got the same issue when running on my own data. I wonder have you fix this problem? Which version of snakemake can work ?

Hi! The workaround I found is to downgrade snakemake in the conda environment to an older version that works. I have found that snakemake-minimal =7.16.0 does not raise this issue. So you can either manually do this on your environment (something like conda install snakemake-minimal=7.16.0. You might need to uninstall the previous version before) or update the environment.yaml file with this line and create another envirnoment with this.
There is an ongoing PR  #160 that among other things pins snakemake version to that one until I find out a more permanent fix for this, so eventually this will be updated in the main branch.

I have been looking at this issue for a while and it is very difficult to debug. Oddly enough, it only crashes with the renaming of the scaling rules but not the demultiplexing ones.
I feel like the inherent recursivity of running snakemake makes it complicated to follow up the workflow object, and maybe it should not be modified directly accessing its variables. The reason we do this is mostly cosmetic (the DAG table of rules gets a few numbered rules on the initial summary), and I would prefer the workflow not to crash due to that, so I am inclined to remove both those rule name setting functions and just letting the workflow work with the anonymous rule numbers while we find a better solution to this, so we can keep up with an up-to-date version of snakemake, which I think is preferable.


Odd behavior when combinging webpack with vagrant

Hey there,
I'm facing a quite odd issue with vagrant and webpack:
Technologies being used:

Webpack 1.13 (locally and globally)
NodeJS: (5.0.0 locally, 6.0.0 in the VM)
NPM: (3.3.6 locally, 3.8.6 in the VM)
OS (Windows 8.1 locally, Ubuntu 14.04 in the VM)
Vagrant 1.7.4
VirtualBox 5.0

Repo and branch containing code to reproduce
https://github.com/Sententiaregum/Sententiaregum
https://github.com/Sententiaregum/Sententiaregum/tree/%23238-refactor-webpack
Steps to reproduce
just run vagrant up
Description
the vagrant up command executes all the build processes (NPM install/Webpack build: https://github.com/Sententiaregum/Sententiaregum/blob/%23238-refactor-webpack/src/AppBundle/Composer/ScriptHandler.php)
When trying to access the page or running the webpack command in the VM (which can be accessed with vagrant ssh (it'll jump into the appropriate directory automatically)), WebPack is unable to resolve certain modules:
ERROR in ./~/react-router/lib/Router.js
Module not found: Error: Cannot resolve module 'history/lib/createHashHistory' in /var/www/sententiaregum/node_modules/react-router/lib
resolve module history/lib/createHashHistory in /var/www/sententiaregum/node_modules/react-router/lib
  looking for modules in /var/www/sententiaregum/node_modules
    resolve 'file' or 'directory' lib/createHashHistory in /var/www/sententiaregum/node_modules/history
      resolve file
        /var/www/sententiaregum/node_modules/history/lib/createHashHistory.js doesn't exist
        /var/www/sententiaregum/node_modules/history/lib/createHashHistory doesn't exist
        /var/www/sententiaregum/node_modules/history/lib/createHashHistory.scss doesn't exist
      resolve directory
        /var/www/sententiaregum/node_modules/history/lib/createHashHistory doesn't exist (directory default file)
        /var/www/sententiaregum/node_modules/history/lib/createHashHistory/package.json doesn't exist (directory description file)
[/var/www/sententiaregum/node_modules/history/lib/createHashHistory.js]
[/var/www/sententiaregum/node_modules/history/lib/createHashHistory]
[/var/www/sententiaregum/node_modules/history/lib/createHashHistory.scss]
 @ ./~/react-router/lib/Router.js 7:25-65

ERROR in ./~/react-router/lib/hashHistory.js
Module not found: Error: Cannot resolve module 'history/lib/createHashHistory' in /var/www/sententiaregum/node_modules/react-router/lib
resolve module history/lib/createHashHistory in /var/www/sententiaregum/node_modules/react-router/lib
  looking for modules in /var/www/sententiaregum/node_modules
    resolve 'file' or 'directory' lib/createHashHistory in /var/www/sententiaregum/node_modules/history
      resolve file
        /var/www/sententiaregum/node_modules/history/lib/createHashHistory.js doesn't exist
        /var/www/sententiaregum/node_modules/history/lib/createHashHistory doesn't exist
        /var/www/sententiaregum/node_modules/history/lib/createHashHistory.scss doesn't exist
      resolve directory
        /var/www/sententiaregum/node_modules/history/lib/createHashHistory doesn't exist (directory default file)
        /var/www/sententiaregum/node_modules/history/lib/createHashHistory/package.json doesn't exist (directory description file)
[/var/www/sententiaregum/node_modules/history/lib/createHashHistory.js]
[/var/www/sententiaregum/node_modules/history/lib/createHashHistory]
[/var/www/sententiaregum/node_modules/history/lib/createHashHistory.scss]
 @ ./~/react-router/lib/hashHistory.js 5:25-65

This is just a part of the errors that araised.
For debugging reason I've tried to do the following:
vagrant@sententiaregum:/var/www/sententiaregum$ node
> require('/var/www/sententiaregum/node_modules/history/lib/createHashHistory.js')
[Function: createHashHistory]
>
(To exit, press ^C again or type .exit)
>

As you can see, Node is able to load the module (I've checked this for all of the modules which can't be resolved by webpack).
After that I've called webpack again.
Although webpack complains about modules that can't be resolved, all modules that have been called in the CLI manually using the require function can be resolved now.
As the modules can be resolved after being called via require from the CLI, I think that it's quite unlikley that a mounting problem caused this odd issue.
Does anyone know, how the resolve issue can be solved?

OK, it seems as I managed to solve that issue.
Removing the --no-bin-links option solved it although I'm using vagrant which contains odd issues with symlinks.
Therefore closing...


Code | Numeric Pattern 174

@aryashah2k can i work on this?

@aryashah2k hey bro i think i messed up here!! i meant alphabeticpattern 174
can you please unassign me here and assign me that issue?

Please assign this issue to me!


Configure Floating Numbers Settings Will Not Open - Validation Error

Describe the bug
Within settings, the 'Configure Floating Numbers Settings' nested under 'Starfinder' does nothing. Console shows a validation error.
To Reproduce
Navigate to 'Game Settings', 'Configure Settings', then 'Starfinder', and click on the button 'Configure Floating Number Settings'.
Expected behavior
A menu should pop-up allowing configuration of floating number settings.
Screenshots

Technical details (please complete the following information):

OS: Windows 10
Browser: electron app (Tested in Chrome as well, same issue)
Foundry Version: 10.291
SFRPG Version: 0.22.0

Additional context
This was first discovered on primary world with 50+ active modules then repeated on a test world with no active modules to confirm the issue is not module dependent.

Found this one recently and it's already fixed 🙂


I added sun and moon icon as replacement of dark mode button

I added sun and moon icon as replacement of dark mode button .
Light Mode

Dark Mode

Issue no : #45

please resolve the conflict first.


Add release date column

+1 (with update date)

Yes, that would be useful. Feel free to make a PR!

@eugeneyan @moghadas76 I created a PR on this https://github.com/eugeneyan/open-llms/pull/23. Can you check it out?

Thanks @adekunleoajayi for adding the dates. Very much appreciated!
Do you also want to add the release dates for the LLMs for Code models down below?

Due to lack of activity on this one, I will take over and will add the release dates for the code models now.

Resolved with 3f31dba691a7d0d7697f58060eb250b3e0fc1670.

Due to lack of activity on this one, I will take over and will add the release dates for the code models now.

@LudwigStumpp sorry for the late reply on this. Please go for it. Thanks


PollOpt is deprecated for event trigger types in MIO

Looks like with mio 0.7.* PollOpt is not there anymore.
So we need to refactor the code to don't pass PollOpt along with interests.

I’d like to take a swing at this!

So, I've looked into the issue and I'm just going to summarize the findings here to save time for others.
Mio removed PollOpts from the public API here: https://github.com/tokio-rs/mio/pull/975
The purpose of this was to reduce the scope of the API and no longer support oneshot events as described here:  https://github.com/tokio-rs/mio/issues/928
Mio simply drops the parameter since there is only the one supported mode now (Edge triggered). Fortunately, async-std only uses this in one spot:  https://github.com/async-rs/async-std/blob/57974ae0b7be220d9e96e0262fd8bd7d8d1e851d/src/net/driver/mod.rs#L98-L99
The solution here is to simply remove opts. But, this would only compile with Mio at version 0.7 of course. Is there a branch to convert async-std to mio 0.7?

@guiri14 Not in my knowledge. @stjepang Are you willing to?


3d_viewport_to_world example never returns a ray

Bevy version
main: f4dab8a4e86f965919dc7525d72dff51be70b857
Works on v0.12.1.
What you did
Cargo run the 3d_viewport_to_world example
What went wrong
This branch is always taken

Since I found it works on v0.12.1 just now I will bisect and report back.

During bisect all steps worked.. when I got to the end it still worked, so I don't know why it was failing initially.


nixos-container: Fix destroy terminating before it's done. Fixes #32545

nixos-container: Fix destroy terminating before it's done. Fixes #32545
This also fixes the race condition found in #32551.
And it fixes nixops's repeated destroy/deploy being broken
(https://github.com/NixOS/nixops/issues/809).
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

CC @domenkozar

CC @johbo @kevincox via https://github.com/NixOS/nixops/pull/759

@GrahamcOfBorg eval
(sorry for the noise, master was broken by a merge)

@GrahamcOfBorg test containers-imperative

No attempt on x86_64-linux
The following builds were skipped because they don't evaluate on x86_64-linux: tests.containers-imperative
No log is available.

Failure on aarch64-linux (full log)
Attempted: tests.containers-imperative
Partial log (click to expand)
machine: exit status 1
machine: output:
error: command `nixos-container create foo --ensure-unique-name' did not succeed (exit code 1)
command `nixos-container create foo --ensure-unique-name' did not succeed (exit code 1)
cleaning up
killing machine (pid 627)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
builder for '/nix/store/ww1ca1y5xhmlqx6j3x8k3h3bacyg1pc5-vm-test-run-containers-imperative.drv' failed with exit code 255
error: build of '/nix/store/ww1ca1y5xhmlqx6j3x8k3h3bacyg1pc5-vm-test-run-containers-imperative.drv' failed


AMQP-599: Log Appenders - Add addresses Property

JIRA: https://jira.spring.io/browse/AMQP-599
Also add docs for the appenders.
cherry-pick to 1.5.x - except Log4j2 and docs

LGTM.
I can fix that minor concern on merge.

Merged as https://github.com/spring-projects/spring-amqp/commit/d29a3a0a39b5861594c26e2d72028613694c1a7c
And cherry-picked as https://github.com/spring-projects/spring-amqp/commit/9db4aba23ab6e9a162975f1d59ad867b03c6b73c after resolving conflicts.


Limit the explorer breadcrumb to the pages the user has explore permission over

Refactor of #3133, based on #3192

Merged in f2fcfe54a2d3a55fccf3fe16c85c4a9fc19cb1ba