Class 'App\Providers\App\Nova\User' not found

Returned error: Class 'App\Providers\App\Nova\User' not found
After default Laravel Nova installation
Then installing package via composer:
"composer require sparclex/nova-import-card"
Then registering in "NovaServiceProvider.php" file
public function card()
{
return [
// ...
new \Sparclex\NovaImportCard\NovaImportCard(App\Nova\User::class),
];
}
Application returned error:
Class 'App\Providers\App\Nova\User' not found
In vendor\sparclex\nova-import-card\src\NovaImportCard.php
 */
public $width = '1/2';

public function __construct($resource)
{
    parent::__construct();
    $this->withMeta([
        'fields' => [
            new File('File'),
        ],
        'resourceLabel' => $resource::label(),// --- This line returned error

=================================

Hi @trueman52
If you replace new \Sparclex\NovaImportCard\NovaImportCard(App\Nova\User::class), with new \Sparclex\NovaImportCard\NovaImportCard(\App\Nova\User::class), you should be fine.
Please let me know if this fixes the issue.
Regards
Silvan

Thank you very much, Silvan!!!
Problem solved!
And big thanks for your time regarding this Nova package.
It can save a lot of time.


Data cardinality

Hi, I am training a neural network use two inputs with different numbers of images, like this:
input1 = Input((500,500,3), name='input1')
input2 = Input((700, 500, 3,), name='input2')
l1 = Dense(64, activation='relu')(input1)
l1 = Dense(1, activation='sigmoid', name='output1')(l1)
l2 = Dense(64, activation='relu')(input2)
l2 = Dense(1, activation='sigmoid', name='output2')(l2)
model = keras.Model(inputs=[input1, input2], outputs=[l1, l2])
keras.utils.plot_model(model, 'multi_input_and_output_model.png', show_shapes=True)
model.compile(optimizer='adam', loss={'output1':keras.losses.MeanSquaredError(),'output2':keras.losses.MeanSquaredError()})
model.summary()
and you can check it by som dummy x1 and x2 but with different first dimension, for example:
x1.shape = (50, 500, 500, 3)
y1.shape = (50,)
x2.shape = (100,700,500,3)
y2.shape = (100,)
model.fit({'input1':x1, 'input2':x2}, {'output1':y1, 'output2':y2}, epochs=10)
I got the ValueError: Data cardinality is ambiguous: x sizes: 50, 100 y sizes: 50, 100 Please provide data which shares the same first dimension.
Can anyone help me to solve the problem?
Any help will be appreciated!

@KaterinaBao
You can have the model train on same number of samples. Thus, as per your example, you will be able to train on 50 examples only. The reason being, that on each step, your model requires a batch of data for all the inputs, and not only one of them. Thus, it is not possible to train on different sized datasets that go into a single model.
Hope this helps.

@KaterinaBao,
Please take a look at @AdityaKane2001's comment and check if it helps.
Also, this question is better asked on StackOverflow since it is not a TensorFlow bug or feature request. There is a larger community that reads questions there. Thanks!

@KaterinaBao
You can have the model train on same number of samples. Thus, as per your example, you will be able to train on 50 examples only. The reason being, that on each step, your model requires a batch of data for all the inputs, and not only one of them. Thus, it is not possible to train on different sized datasets that go into a single model.
Hope this helps.

Thank, that information really useful

@KaterinaBao,
Please take a look at @AdityaKane2001's comment and check if it helps.
Also, this question is better asked on StackOverflow since it is not a TensorFlow bug or feature request. There is a larger community that reads questions there. Thanks!

Yes, that's helpful. Thanks

Requesting to close the issue if the query is resolved.


Sash is wrong on mobile

Currently we detect whether we're on a touch/mobile device and set the sash size based on this. However, this has no effect on the related css variables.

I think we will have to give up using css variables to customise the size of the sash and move to setting it using javascript. Basically, the way VS Code does it. We can still use css variables internally, but it will no longer be the documented method of customising the sash. This will be a breaking change.

Closed by #101


[Feature Request] Custom server for new account

Feature request: when adding a new account, let the user choose the ip/url of the endpoint of the telegram server, that way it will work also on custom servers

Already possible with "server_address" in Config

for ex: "<IP_ADDRESS>:443" to connect to Test DC 2
This config is used only on the first connection to a server (creation of a session)


Issue With Centos7 Build Image Container on PPC64LE

The builds for JDK8, 11, 17, 20,etc are failing due to an issue with the adoptopenjdk/centos7_build_image, relevant details from the ongoing investigation are in the comments below, but also this slack thread..
https://adoptium.slack.com/archives/C53GHCXL4/p1694004795268149

Currently the issues appears to be related to an (as yet) undetermined change in a docker image..
Image sha256:1718ad98c8a39dd7b6cdaac5fba56d4bc333d434ab3ad5eba148c3d5fbf4829c was created here and failed to build here.
Image sha256:6a1880687647ec32430cdb6d2006d46e65fe3e1296e22753c8a7b5ec24816047 was created here and successfully built openjdk here.

images from #362 onwards are broken: https://ci.adoptium.net/view/Infra/job/centos7_docker_image_updater/362/

Hmm I that could have activated a new kernel version and possible new container integration modules for the kernel ...
Do we know the relative running of "new image being built" Vs "Restart of host that created it" Vs "When it started
The reboot occurred (2nd Sept), then the image built(4th Sept), then the build failures ( although there was a successful
Currently attempting to rebuild the docker image on the non-skytap node... also manually building the docker image on the skytap node..
So a rebuild of the image on a machine that hasnt been updated/rebooted also doesnt work....

Future docker image testing issue raised: https://github.com/adoptium/infrastructure/issues/3184

Some analysis running a container on skytap docker host, running image sha256:40cdf0d6717ba7480cd6dd3f10e92f87feca1336356c8ce999910624fa501f22:
3b3e8060b88f0f6e2dc6f2cbae94a68894f8c458dce38603206362e9d1a01259
jenkins@dockerhost-skytap-ubuntu2004-ppc64le-1:~$
jenkins@dockerhost-skytap-ubuntu2004-ppc64le-1:~$ docker exec -it 3b3e8060b88f0f6e2dc6f2cbae94a68894f8c458dce38603206362e9d1a01259 bash
bash: /home/jenkins/.bashrc: Permission denied
bash-4.2$ ls -l
total 84
-rw-rw-r-- 1 jenkins 1001  8596 Sep  4 13:41 CONTRIBUTING.md
-rw-rw-r-- 1 jenkins 1001  6142 Sep  4 13:41 FAQ.md
-rw-rw-r-- 1 jenkins 1001 11360 Sep  4 13:41 LICENSE
-rw-rw-r-- 1 jenkins 1001    65 Sep  4 13:41 NOTICE
-rw-rw-r-- 1 jenkins 1001 36695 Sep  4 13:41 README.md
drwxrwxr-x 3 jenkins 1001  4096 Sep  4 13:41 docs
drwxrwxr-x 6 jenkins 1001  4096 Sep  4 13:41 pipelines
drwxrwxr-x 4 jenkins 1001  4096 Sep 12 14:07 tools

Running with the last good image is slightly different sha256:6a1880687647ec32430cdb6d2006d46e65fe3e1296e22753c8a7b5ec24816047:
jenkins@dockerhost-skytap-ubuntu2004-ppc64le-1:~$ docker exec -it 74d3892bf7778acc4dd4cab814b863b772c0cd55e677c62e5ab601b17aa74120 bash
/usr/bin/id: cannot find name for group ID 1001
[jenkins@74d3892bf777 jdk21-linux-ppc64le-temurin]$ ls -l
total 84
-rw-rw-r-- 1 jenkins 1001  8596 Sep  4 13:41 CONTRIBUTING.md
-rw-rw-r-- 1 jenkins 1001  6142 Sep  4 13:41 FAQ.md
-rw-rw-r-- 1 jenkins 1001 11360 Sep  4 13:41 LICENSE
-rw-rw-r-- 1 jenkins 1001    65 Sep  4 13:41 NOTICE
-rw-rw-r-- 1 jenkins 1001 36695 Sep  4 13:41 README.md
drwxrwxr-x 3 jenkins 1001  4096 Sep  4 13:41 docs
drwxrwxr-x 6 jenkins 1001  4096 Sep  4 13:41 pipelines
drwxrwxr-x 4 jenkins 1001  4096 Sep 12 14:07 tools

@steelhead31 I think I may have worked out the pLinux build image issue, and it’s a matter of getting all the “ducks” line up!!
Root problem: skytap machine jenkins user has wrong groupid for the build image, needs to be 1000 so the permissions line up. Building the image on this node I think will generate a bad image due to the gid’s
Secondary problems:
When the updater job runs it pushed image: adoptopenjdk/centos7_build_image:linux-ppc64le
Then the last step of the updater job is “Push Docker Manifest”, this updates the dockerhub manifest so when you pull adoptopenjdk/centos7_build_image on a ppc64le box it actually pulls: adoptopenjdk/centos7_build_image:linux-ppc64le, and so-on for each platform. BUT, if a single docker build fails, then the “Docker Manifest” stage does not run! hence the platform manifest link is still pointing at the old image…. The Docker Manifest is not running most of the time, as typically either the build of armv7l or Alpine fails!
I’ve just confirmed this by disconnecting the skytap node, and running the centos7_docker_image_updater job, forcing the pLinux docker build on the good osusl node. The “docker manifest” failed as usual! So I submitted a build with: “DOCKER_IMAGE”: “adoptopenjdk/centos7_build_image:linux-ppc64le”,
and that is running successfully: https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk17u/job/jdk17u-linux-ppc64le-temurin/278/console
Actions:

Swap the skytap and jenkins user "gid" on the skytap host, so that jenkins is 1000:1000
Run the centos7_docker_image_updater repeating until all the builds are green and the "Docker Manifest" is updated. This will update adoptopenjdk/centos7_build_image to point at the good new image adoptopenjdk/centos7_build_image-ppc64le
Consider raising a new issue to allow an option on the centos7_docker_image_updater job, to choose which builds to run, so you can say update just one!

I've manually updated the groupids on the skytap server , and run a chmod across the jenkins homedirectory to change the GIDs in use..

This is now working, additional issues have been created for changes to testing etc #3184

Good job Scott! :)


Fix flickering when passing in an unformatted value.

Disabled padding the value prop to the underlying TextInput and reformatted the value prop on componentWillReceiveProps.

@BasitAli LGTM, thank you so much!

@BasitAli https://github.com/react-native-community/react-native-text-input-mask/releases/tag/v0.5.2


Proton Scatter script on working

Terrain3D version
v0.9.0
System information
Godot v4.2.stable.mono - Windows 10.0.22621 - Vulkan (Forward+) - integrated AMD Radeon(TM) Vega 3 Graphics () - AMD Ryzen 3 3250U with Radeon Graphics (4 Threads)
Is the issue reproducable in the demo?
Yes
Issue description
The proton scatter script is not working. I just Installed Proton Scatter v4. I am not able to select a terrian3d node.

Logs
No response

What exact commit of proton scatter?
Post all of those error messages. Can't help without them. Post everything in your console.

Had this same issue and was able to find a fix.
It is an issue with proton scatter not being able to get the child nodes of the scene due to an error.
I was able to fix it by simply commenting out a line in the file "parameter_node_selector.gd" located here:
"res://addons/proton_scatter/src/stack/inspector_plugin/ui/modifier/components/parameter_node_selector.gd:67"
The line to be commented out was line 67 for me. node_item.set_icon(0, theme.get_icon(node.get_class(), "EditorIcons"))

The latest proton scatter release, commit:   ca62441
There not much error log.
The error is :
res://addons/proton_scatter/src/stack/inspector_plugin/ui/modifier/components/parameter_node_selector.gd:67 - Attempt to call function 'get_icon' in base 'null instance' on a null instance.
I think this is proton scatter internal error. Not related to project_on_terrrian3D modifier.

Thanks, this works!

Thanks, this works!

Had this same issue and was able to find a fix.
It is an issue with proton scatter not being able to get the child nodes of the scene due to an error.
I was able to fix it by simply commenting out a line in the file "parameter_node_selector.gd" located here: "res://addons/proton_scatter/src/stack/inspector_plugin/ui/modifier/components/parameter_node_selector.gd:67"
The line to be commented out was line 67 for me. node_item.set_icon(0, theme.get_icon(node.get_class(), "EditorIcons"))

This worked for me

Indeed this is a scatter bug, which we can't fix or support. Thanks for providing a solution @BranDenn. You guys could report it on @HungryProton 's repo. Specifically that recent changes breaks the ability for modifier scripts to create an exported node path variable. In that function, the parent parameter is null.

Hello 👋 this just bit me today too, so I went ahead and filed the bug report in the other repository.


feat: add namespaced identifiers

fixes #50
We add "::" to the allowed continuation tokens for an identifier. Thats too general since only functions are namespaced but for the scope of this project it doesnt matter too much. This has the benefit of not breaking downstream projects.

Forgot to stage the grammar.js change?

Thanks for picking this up so fast @MichaHoffmann!


HDDS-11066. Fix inaccurate *.http.auth.type config descriptions in ozone-default.xml

What changes were proposed in this pull request?
Just fixing the doc:

SPNEOGO -> SPNEGO
There is no such thing as "Kerberos SPNEGO". Kerberos is a one of the auth sub-mechanisms that can be used under SPNEGO (the other common one being NTLM).

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-11066
How was this patch tested?

n/a

Thanks @adoroszlai for reviewing and merging this!


Put default affinity spec under podTemplate spec

Type of change

Bugfix

Description
The current affinity settings does not get applied as they are placed
directly under deployment.spec and statefulset.spec
Fixes #3646
Checklist

[ ] Update/write design documentation in ./documentation/design
[ ] Write tests and make sure they pass
[ ] Update documentation
[ ] Check RBAC rights for Kubernetes / OpenShift roles
[ ] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
[ ] Reference relevant issue(s) and close them after merging
[ ] Update CHANGELOG.md

@enmasse-ci run tests profile=smoke

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: smoke
TEST_CASE:
TOTAL: 3
PASS: 3
FAIL: 0
SKIP: 0
BUILD_NUMBER: 244


error with layout parsing when processing the large size pdf file

2024-06-28 14:50:59 - INFO - /home/xeon/OCRIntegrator/app/deepdoc/parser/pdf_parser.py - line 985 - OCR: page 19 cost time: 0.17715859413146973
[06/28/2024-14:50:59] [TRT] [E] 3: [executionContext.cpp::setInputShape::2068] Error Code 3: API Usage Error (Parameter check failed at: runtime/api/executionContext.cpp::setInputShape::2068, condition: satisfyProfile Runtime dimension does not satisfy any optimization profile.)
INFO:     <IP_ADDRESS>:59210 - "POST /layout/file HTTP/1.1" 500 Internal Server Error
ERROR:    Exception in ASGI application
Traceback (most recent call last):
File "/home/xeon/.local/lib/python3.11/site-packages/uvicorn/protocols/http/httptools_impl.py", line 399, in run_asgi
result = await app(  # type: ignore[func-returns-value]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/xeon/.local/lib/python3.11/site-packages/uvicorn/middleware/proxy_headers.py", line 70, in call
return await self.app(scope, receive, send)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/xeon/.local/lib/python3.11/site-packages/fastapi/applications.py", line 1054, in call
await super().call(scope, receive, send)
File "/home/xeon/.local/lib/python3.11/site-packages/starlette/applications.py", line 123, in call
await self.middleware_stack(scope, receive, send)
File "/home/xeon/.local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 186, in call
raise exc
File "/home/xeon/.local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 164, in call
await self.app(scope, receive, _send)
File "/home/xeon/.local/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 65, in call
await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
File "/home/xeon/.local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
raise exc
File "/home/xeon/.local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
await app(scope, receive, sender)
File "/home/xeon/.local/lib/python3.11/site-packages/starlette/routing.py", line 756, in call
await self.middleware_stack(scope, receive, send)
File "/home/xeon/.local/lib/python3.11/site-packages/starlette/routing.py", line 776, in app
await route.handle(scope, receive, send)
File "/home/xeon/.local/lib/python3.11/site-packages/starlette/routing.py", line 297, in handle
await self.app(scope, receive, send)
File "/home/xeon/.local/lib/python3.11/site-packages/starlette/routing.py", line 77, in app
await wrap_app_handling_exceptions(app, request)(scope, receive, send)
File "/home/xeon/.local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
raise exc
File "/home/xeon/.local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
await app(scope, receive, sender)
File "/home/xeon/.local/lib/python3.11/site-packages/starlette/routing.py", line 72, in app
response = await func(request)
^^^^^^^^^^^^^^^^^^^
File "/home/xeon/.local/lib/python3.11/site-packages/fastapi/routing.py", line 278, in app
raw_response = await run_endpoint_function(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/xeon/.local/lib/python3.11/site-packages/fastapi/routing.py", line 191, in run_endpoint_function
return await dependant.call(**values)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/xeon/OCRIntegrator/app/routers/ocr.py", line 48, in detect_layout_by_file
result = ocr_service.detect_layout(file_type, file_io)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/xeon/OCRIntegrator/app/service/layer.py", line 16, in detect_layout
return self.ocr_adapter.detect_layout(file_type, file)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/xeon/OCRIntegrator/app/adapter/deepdoc_adapter.py", line 24, in detect_layout
return self.pdf_parser.call(file_path)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/xeon/OCRIntegrator/app/deepdoc/parser/pdf_parser.py", line 1001, in call
self.images(fnm, zoomin)
File "/home/xeon/OCRIntegrator/app/deepdoc/parser/pdf_parser.py", line 984, in images
self._ocr(i + 1, img, chars, zoomin)
File "/home/xeon/OCRIntegrator/app/deepdoc/parser/pdf_parser.py", line 244, in _ocr
bxs = self.ocr.detect(np.array(img))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/xeon/OCRIntegrator/app/deepdoc/vision/ocr.py", line 545, in detect
dt_boxes, elapse = self.text_detector(img)
^^^^^^^^^^^^^^^^^^^^^^^
File "/home/xeon/OCRIntegrator/app/deepdoc/vision/ocr.py", line 460, in call
raise e
File "/home/xeon/OCRIntegrator/app/deepdoc/vision/ocr.py", line 458, in call
outputs = TextDetector._predictor.run(None, input_dict)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/xeon/OCRIntegrator/app/deepdoc/tensorrt_engine.py", line 165, in run
trt_outputs = self.infer(inputs)
^^^^^^^^^^^^^^^^^^
File "/home/xeon/OCRIntegrator/app/deepdoc/tensorrt_engine.py", line 158, in infer
self.stream.synchronize()
pycuda._driver.LogicError: cuStreamSynchronize failed: an illegal memory access was encountered
PyCUDA WARNING: a clean-up operation failed (dead context maybe?)
cuMemFreeHost failed: an illegal memory access was encountered
PyCUDA WARNING: a clean-up operation failed (dead context maybe?)
cuMemFree failed: an illegal memory access was encountered
PyCUDA WARNING: a clean-up operation failed (dead context maybe?)
cuMemFreeHost failed: an illegal memory access was encountered
2024年1-5月合同上部分五金造转.pdf

2024-06-28 14:50:59 - INFO - /home/xeon/OCRIntegrator/app/deepdoc/parser/pdf_parser.py - line 985 - OCR: page 19 cost time: 0.17715859413146973 [06/28/2024-14:50:59] [TRT] [E] 3: [executionContext.cpp::setInputShape::2068] Error Code 3: API Usage Error (Parameter check failed at: runtime/api/executionContext.cpp::setInputShape::2068, condition: satisfyProfile Runtime dimension does not satisfy any optimization profile.) INFO: <IP_ADDRESS>:59210 - "POST /layout/file HTTP/1.1" 500 Internal Server Error ERROR: Exception in ASGI application Traceback (most recent call last): File "/home/xeon/.local/lib/python3.11/site-packages/uvicorn/protocols/http/httptools_impl.py", line 399, in run_asgi result = await app( # type: ignore[func-returns-value] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/.local/lib/python3.11/site-packages/uvicorn/middleware/proxy_headers.py", line 70, in call return await self.app(scope, receive, send) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/.local/lib/python3.11/site-packages/fastapi/applications.py", line 1054, in call await super().call(scope, receive, send) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/applications.py", line 123, in call await self.middleware_stack(scope, receive, send) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 186, in call raise exc File "/home/xeon/.local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 164, in call await self.app(scope, receive, _send) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 65, in call await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app raise exc File "/home/xeon/.local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app await app(scope, receive, sender) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/routing.py", line 756, in call await self.middleware_stack(scope, receive, send) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/routing.py", line 776, in app await route.handle(scope, receive, send) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/routing.py", line 297, in handle await self.app(scope, receive, send) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/routing.py", line 77, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app raise exc File "/home/xeon/.local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app await app(scope, receive, sender) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/routing.py", line 72, in app response = await func(request) ^^^^^^^^^^^^^^^^^^^ File "/home/xeon/.local/lib/python3.11/site-packages/fastapi/routing.py", line 278, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/.local/lib/python3.11/site-packages/fastapi/routing.py", line 191, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/OCRIntegrator/app/routers/ocr.py", line 48, in detect_layout_by_file result = ocr_service.detect_layout(file_type, file_io) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/OCRIntegrator/app/service/layer.py", line 16, in detect_layout return self.ocr_adapter.detect_layout(file_type, file) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/OCRIntegrator/app/adapter/deepdoc_adapter.py", line 24, in detect_layout return self.pdf_parser.call(file_path) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/OCRIntegrator/app/deepdoc/parser/pdf_parser.py", line 1001, in call self.images(fnm, zoomin) File "/home/xeon/OCRIntegrator/app/deepdoc/parser/pdf_parser.py", line 984, in images self._ocr(i + 1, img, chars, zoomin) File "/home/xeon/OCRIntegrator/app/deepdoc/parser/pdf_parser.py", line 244, in _ocr bxs = self.ocr.detect(np.array(img)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/OCRIntegrator/app/deepdoc/vision/ocr.py", line 545, in detect dt_boxes, elapse = self.text_detector(img) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/OCRIntegrator/app/deepdoc/vision/ocr.py", line 460, in call raise e File "/home/xeon/OCRIntegrator/app/deepdoc/vision/ocr.py", line 458, in call outputs = TextDetector._predictor.run(None, input_dict) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/OCRIntegrator/app/deepdoc/tensorrt_engine.py", line 165, in run trt_outputs = self.infer(inputs) ^^^^^^^^^^^^^^^^^^ File "/home/xeon/OCRIntegrator/app/deepdoc/tensorrt_engine.py", line 158, in infer self.stream.synchronize() pycuda._driver.LogicError: cuStreamSynchronize failed: an illegal memory access was encountered PyCUDA WARNING: a clean-up operation failed (dead context maybe?) cuMemFreeHost failed: an illegal memory access was encountered PyCUDA WARNING: a clean-up operation failed (dead context maybe?) cuMemFree failed: an illegal memory access was encountered PyCUDA WARNING: a clean-up operation failed (dead context maybe?) cuMemFreeHost failed: an illegal memory access was encountered 2024年1-5月合同上部分五金造转.pdf

I'm checking.

2024-06-28 14:50:59 - INFO - /home/xeon/OCRIntegrator/app/deepdoc/parser/pdf_parser.py - line 985 - OCR: page 19 cost time: 0.17715859413146973 [06/28/2024-14:50:59] [TRT] [E] 3: [executionContext.cpp::setInputShape::2068] Error Code 3: API Usage Error (Parameter check failed at: runtime/api/executionContext.cpp::setInputShape::2068, condition: satisfyProfile Runtime dimension does not satisfy any optimization profile.) INFO: <IP_ADDRESS>:59210 - "POST /layout/file HTTP/1.1" 500 Internal Server Error ERROR: Exception in ASGI application Traceback (most recent call last): File "/home/xeon/.local/lib/python3.11/site-packages/uvicorn/protocols/http/httptools_impl.py", line 399, in run_asgi result = await app( # type: ignore[func-returns-value] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/.local/lib/python3.11/site-packages/uvicorn/middleware/proxy_headers.py", line 70, in call return await self.app(scope, receive, send) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/.local/lib/python3.11/site-packages/fastapi/applications.py", line 1054, in call await super().call(scope, receive, send) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/applications.py", line 123, in call await self.middleware_stack(scope, receive, send) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 186, in call raise exc File "/home/xeon/.local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 164, in call await self.app(scope, receive, _send) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 65, in call await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app raise exc File "/home/xeon/.local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app await app(scope, receive, sender) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/routing.py", line 756, in call await self.middleware_stack(scope, receive, send) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/routing.py", line 776, in app await route.handle(scope, receive, send) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/routing.py", line 297, in handle await self.app(scope, receive, send) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/routing.py", line 77, in app await wrap_app_handling_exceptions(app, request)(scope, receive, send) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app raise exc File "/home/xeon/.local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app await app(scope, receive, sender) File "/home/xeon/.local/lib/python3.11/site-packages/starlette/routing.py", line 72, in app response = await func(request) ^^^^^^^^^^^^^^^^^^^ File "/home/xeon/.local/lib/python3.11/site-packages/fastapi/routing.py", line 278, in app raw_response = await run_endpoint_function( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/.local/lib/python3.11/site-packages/fastapi/routing.py", line 191, in run_endpoint_function return await dependant.call(**values) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/OCRIntegrator/app/routers/ocr.py", line 48, in detect_layout_by_file result = ocr_service.detect_layout(file_type, file_io) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/OCRIntegrator/app/service/layer.py", line 16, in detect_layout return self.ocr_adapter.detect_layout(file_type, file) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/OCRIntegrator/app/adapter/deepdoc_adapter.py", line 24, in detect_layout return self.pdf_parser.call(file_path) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/OCRIntegrator/app/deepdoc/parser/pdf_parser.py", line 1001, in call self.images(fnm, zoomin) File "/home/xeon/OCRIntegrator/app/deepdoc/parser/pdf_parser.py", line 984, in images self._ocr(i + 1, img, chars, zoomin) File "/home/xeon/OCRIntegrator/app/deepdoc/parser/pdf_parser.py", line 244, in _ocr bxs = self.ocr.detect(np.array(img)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/OCRIntegrator/app/deepdoc/vision/ocr.py", line 545, in detect dt_boxes, elapse = self.text_detector(img) ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/OCRIntegrator/app/deepdoc/vision/ocr.py", line 460, in call raise e File "/home/xeon/OCRIntegrator/app/deepdoc/vision/ocr.py", line 458, in call outputs = TextDetector._predictor.run(None, input_dict) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/xeon/OCRIntegrator/app/deepdoc/tensorrt_engine.py", line 165, in run trt_outputs = self.infer(inputs) ^^^^^^^^^^^^^^^^^^ File "/home/xeon/OCRIntegrator/app/deepdoc/tensorrt_engine.py", line 158, in infer self.stream.synchronize() pycuda._driver.LogicError: cuStreamSynchronize failed: an illegal memory access was encountered PyCUDA WARNING: a clean-up operation failed (dead context maybe?) cuMemFreeHost failed: an illegal memory access was encountered PyCUDA WARNING: a clean-up operation failed (dead context maybe?) cuMemFree failed: an illegal memory access was encountered PyCUDA WARNING: a clean-up operation failed (dead context maybe?) cuMemFreeHost failed: an illegal memory access was encountered 2024年1-5月合同上部分五金造转.pdf

How much VRAM do you have? It could be caused by insufficient VRAM.

Ubuntu 22 ,how to increase the VRAM?


GL2 defines not working correctly

As discussed in this topic:
https://forum.playcanvas.com/t/depth-buffer-in-material-shader/9120/15
When the project compiles each shader on runtime the GL2 flag isn’t respected. Even though it runs on a WebGL2 context the shaders always fallback on the else branch of the GL2 defines.
Direct link to the fragment shader in question:
https://playcanvas.com/editor/code/657274?tabs=26543414
Direct link to the project with a workaround implemented (separate shaders for GL1 and GL2):
https://playcanvas.com/project/657274/overview/toon-water
Forked from this water tutorial project:
https://playcanvas.com/project/533435/overview/toon-water--tuts-tutorial
Tested on Chrome Version 79.0.3945.88 and Firefox Version 71.0 (64-bit) running on Windows 10.

Engine inserts this line when it builds shader from chunks:
#define GL2
and so the chunk based shader (such as basic or standard shader) can depend on GL2 define.
If you write a shader yourself, such as the linked shader: https://playcanvas.com/editor/code/657274?tabs=26543414
the define is not inserted and so you cannot depend on it. We don't currently post-process user supplied shaders to insert defines.
There are two ways you can go around it:

insert define to your shader as needed (needs code, as this specific define needs to be only inserted on webgl device). Code similar to this perhaps:
            if (this.webgl2) {              var gl2define = "#define GL2\n";              shaderSrc = gl2define.concat(shaderSrc);          }
write separate shaders for GL1 and GL2 and use appropriate based on device.


fix message frequency rules

Description

the rules engine is not dispatching rules response events when an event matches a rule. this was causing the user profile based frequency rules to not be matched. to resolve it, a rules response event is dispatched by the campaign extension for the profile extension to process.

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Let's close this one, since we'll have a fix in core.


Add to TechEmpower benchmarks

See https://github.com/TechEmpower/FrameworkBenchmarks/pull/2633

Can you also include wheezy.web in your benchmark on the readme, please?

Yeah, tho I'd need to re-run from scratch to make the comparison fair.
Also I must include the wrk command this time.
This should do:
 wrk -t 10 -c 100 -d 10 http://localhost:5000/

We'll probably change the section in favor of whatever TechEmpower publish if and when that becomes possible.

Very positive...

"API Star was already merged in, so it'll be in the Round 14 final"

It wasn't merged in time for us to be in any of the preliminary testing that they run prior to running the final round, so we can't see if they're getting similar results to my testing, or be able to fix any issues that crop up, so just have to cross fingers that all is setup smoothly.
We'll plan to expand the test cases in adequate time for round 15.
Will update the docs once they publish the final round, and close this off. (Should also be able to include wheezy.web then as per @ddorian's suggestion, or simply point to the TechEmpower site)

@tomchristie I only asked for wheezy to be included cause it's been fastest in ~all benchmarks that I've seen it.

Might also be useful in the future: http://klen.github.io/py-frameworks-bench/
(The remote request case is particular interesting for comparison of async vs sync frameworks)

Round 14 preliminary results. 👍
I've filtered to only JS, Py, Go, and Rby results here...

Round 14 has now been released. Added to the docs
---> https://github.com/tomchristie/apistar#performance


[I-side] - Fix issues found in tracing example

Fixes #288
Add missing grant qualification to stop spurious address updates
Make RTL robust to spurious rvalid signalling

Yes good idea, I ran the tracer test example given by @raulbehl, but it would be could if @udinator could run the failing riscv_rand_instr_test

Hi @vogelpi and @tomroberts-lowrisc, I reran a riscv_rand_instr_test, and Ibex is now able to run the test to completion, and passes the correctness log comparison check in our flow, but I am seeing that the second assertion in ibex_if_stage.sv starts to fail slightly less than halfway through the test (around 58000 cycles in), and the resultant simulation log looks like the below, though Ibex completely passes the test:

After digging into this failure, the below waveform shows the first time that this assertion fails:

At the location where the yellow cursor is, we see the request signal being asserted by Ibex for 3 cycles, but the testbench does not send a grant for this specific request for another 7-8 cycles, until after the request has been dropped by the core, thus triggering the assertion in question. From my discussion with Pirmin as well as the memory interface spec, it seems that grants should only be sent to the core while the request signal is high, which would make this stand-alone grant invalid, but Ibex still responds to the corresponding rvalid and rdata, which are sent around the 15,460,000ps mark, and continues executing as normal.
I will modify the testbench driver protocol to only send grants to Ibex when requests are active, but would it be possible to clarify Ibex's expected behavior in the situation I described above?
Best,
Udi

Hi Udi,
thanks for your report. Looking at the waveform, I see different points that need to be investigated, discussed and documented:

Is it allowed for the core to deassert request without getting a grant? The two of us earlier discussed that it makes sense to allow this. For example, if the core changes its mind about an outstanding request because of a branch. This is similar to the core changing the address as long as it does not get a grant. This has been confusing for many people in the past but it was allowed on the instruction interface. In the case of a PMP error, the same is also possible now on the data interface (the core asserts data_req_o for one cycle and then deasserts it if it does not get a grant). For our core interface it is currently not described if this is allowed or not and how the downstream should handle it. We need to take a decision here and document it. Just FYI: there are both interconnects that allow this behavior (TileLink) and such that do not (AXI).
-> I will create a separte issue for this.

Between the yellow marker in your wave diagram and the second time the core asserts request at around 15,420,000ps, the core does not change the address but quite a few cycles pass by. What's is happening there? This does not look good to me. Could you extract the waves and send to us for inspection?

There are rvalids missing. After the yellow marker, I see 3 request/grant pairs + the grant without request, but just 1 associated rvalid (the first one after the marker belongs to the handshake before the marker). Probably the IF stage is getting out-of-sync because of the grant without request?

Best regards,
Pirmin

Hi Pirmin,

I agree with your point about the spec saying that instr_req_o must stay high until instr_gnt_i is high for one cycle (I did not remember this either in our discussion).

Unfortunately, the original waveform file got overwritten, but I have recreated a very similar situation as in my previous post. I have sent the associated waves.fsdb and disassembled assembly code for further inspection via an email; the situation arises at around 17,410,000ps into the simulation, where instr_gnt_i is asserted when instr_req_o is low, and then there is quite a large delay until instr_req_o is asserted again, and the address does not change either. In this situation, shown in the new waveform snippet below, a rem instruction is being executed, and takes many cycles to complete (from the time the first request goes high just before 17,400,400ps until the next request goes high around 17,466,000ps. I recall in the previous scenario I posted above, a related instruction that utilizes the multdiv block was executing, causing the delay.

Regarding the waves image in my previous post, the rvalid shown near the right hand side of the waveform around 15,460,000ps is the one returning data associated with the stand-alone grant, as this grant actually is in response to the requested response at 15,370,000ps. This is due to the testbench inserting a random delay between receiving response and driving grant. In addition, our testbench inserts a delay of up to 20 clock cycles between detecting response and grant high during the same cycle, and driving rvalid with the associated read data. However, since the grant was standalone, the next time that the condition was true was at 15,420,000ps, which marks a separate transaction, which is why the rvalid corresponding to the standalone grant is so far after in the simulation.

Thanks for looking into it Udi. I think the grant |-> req assertion should probably just be removed. That's not how a sensible interconnect should behave, and the core can handle it happening.
I think we need a separate issue on whether or not the request can be dropped (and the address changed) once asserted. It will need quite a few changes to fix, but I can see it being something that's required for the future (not just for AMBA but any system running N:1 clocking between core and interconnect).

For now I think I can stop the ungranted request from dropping with an extra flop, and that gets us back to where we were before protocol-wise. Then we can look into the address changing as a separate issue.

Updates made to stop requests being dropped. Hopefully @udinator can rerun the test again and confirm all is ok.
Thanks!

I just discussed with Tom, the LSU is not affected by this behavior (in the case of PMP errors, I have changed my comment above). I have created a separate issue lowrisc/ibex#296 to discuss the address stability on the instruction interface.

Hi @tomroberts-lowrisc, @vogelpi,
I reran the same test with the updates to the RTL, and I also added back in our testbench's randomized delay before asserting grant (which I'd removed in #295) to test the core's new behavior. For the most part, the waves look better now, and request is usually dropping after the grant is asserted after some random delay. However, I'm still seeing some interesting situations as shown in the waveform below:

Around 19,973,000ps, the core sends out two consecutive requests, followed by a third request a clock cycle after the first two have been sent. The first two are answered with grants from the testbench immediately, and rvalid is raised two cycles after the core has asserted request. However, the third request the core sends out at around 19,980,000ps drops as soon as the rvalid (which indicates rdata for only the first two requests) drops, and does not wait for its grant to be asserted, which occurs at around 20,000,000ps. Resultantly, the rvalid for this third request is sent by the testbench only after it detects both request and grant are high again, which occurs much later, around 20,070,000ps, thus the read data for this standalone grant is sent at the location of the yellow cursor.
What is interesting is that we can see that around 20,053,000ps, the core sends out a request for the fourth time, but this one does wait until seeing a grant to deassert it.

Thanks again @udinator - I think I see the issue, have pushed another update which should fix the dropped requests

LGTM, I'm not seeing this issue anywhere in the tests. Thanks for all of the fixes @tomroberts-lowrisc !

Cool, thanks for your feedback @udinator and fixing it @tomroberts-lowrisc , great work!

Thanks again @udinator for testing this so quickly, and thanks @vogelpi for the review!


Istio v1.1

Using SM Operator v2.0, install the older v1.1 service mesh control plane

Sorry!  need to close this.  This has additional changes meant for a different workshop.


[Question] Redis_exporter upgrade to latest version

Can we update  redis_exporter to the latest version? the reason is:
https://github.com/oliver006/redis_exporter/issues/257#issuecomment-490314007

@frodenas it's possible to update Redis_exporter  to https://github.com/oliver006/redis_exporter/releases/tag/v1.0.0

Updated at https://github.com/bosh-prometheus/prometheus-boshrelease/commit/b41055e8e685b66d3e9cd9c0a497a7a2d67de507.


User interface for configuring which features to measure

Hi @0x00b1 ,
as just discussed in the napari community meeting: I think a user-interface for selecting which features should be measured would be awesome, A good example for such a GUI is ilastik:

source

Thank you very much sir. Banging on this now.

@haesleinhuepf merged and released. Thanks again, @haesleinhuepf.


Add threshold to MagickImage

This PR adds the threshold method to MagickImage.
I based the implementation on the Magick.Net impl.
I also added a test but it doesn't feel very thorough. I'm not sure what to test to validate that the image threshold changes based on the inputs though.

Updated based on your feedback!

Thanks for this PR!


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Created read me

All the info about project is added
#22

please @Akshatchaube01  merge this pull request.

Add git commands in How to Contribute section

No that was already added in the installation part containing a video tutorial as well

We need git commands under the How to Contribute section.

Okay adding that as well and making the desktop one as alternative. Is that fine??

Check @Akshatchaube01  made all the changes added git commands as well please merge the pull request

Hello @Akshatchaube01  Sir it would be great if you could provide me some review it was my first time contributing in open source how was the work any feedback will help

hi @Akshatchaube01 my contribution was not counted in leaderboard it would be great if you could help as you add it in level 2 as well and merged it as different issue that's why may be it was not counted

As I see no labels are assigned as well. Please I put a lot of effort in creating complete read me file

sir my pr is not counted please add labels like "ggsoc" and "level2". please please


Kafka Connector Vulnerabilities

Confluent regularly performs security scans on Confluent Hub connectors, as per Confluent’s security policy. Unfortunately this connector has been flagged as having unacceptable vulnerabilities and our policy is to escalate the connector to removal stages, unless we receive confirmation that the issues are being addressed by the partner.
I have attached the vulnerability scan. Please note that we acknowledge two exceptions for vulnerabilities raised:
Partner confirms that vulnerability is a false positive
Partner confirms that the issue is valid but not exploitable
Please can you urgently acknowledge receipt of this email, and as soon as possible thereafter let us know the ScyllaDB position on these vulnerabilities.
If you require further information on any of the above, please do not hesitate to get in touch.
Best regards,
Confluent CCET Team
scylladb.csv

Closing this older issue, the reported problems were already solved (notified via email) and now we have a daily vulnerability scan in the repo (that's currently passing).


Feature: Paragraph.add_hyperlink()  (wip)

The PR answers to the feature https://github.com/python-openxml/python-docx/issues/74

[x] Protocol/schema analysis
[ ] Implementations and tests for paragraph.add_hyperlink
-> implementation wip
[ ] Implementations and tests for paragraph.iter_run_level_items()

Hi again @scanny Could you please me some feekback on this PR ? I wait for your GO to attack the implementation part. :)

Hello @scanny ,
Thank you very much for the explanation in detail, it really helps :). I understand more now.
I am totally agree with you that we should escape special chars in Hyperlink.address. ^^
For <w:history>, I think you are right. In this document of Microsoft, it says

The history attribute value of true specifies that the target of the current hyperlink must be added to a list of visited hyperlinks when invoked within the document. end example]
The possible values for this attribute are defined by the ST_OnOff simple type (§<IP_ADDRESS>).

So the value can be 0/1/True/False.
But I don't think this <w:history> is important as <w:history> has not been set by google docx nor by open office. I suggest we don't implement  <w:history> at the moment.
As you have mentioned, <w:anchor> is a bookmark name with '#' prepended, either for the document itself (no <r:id>) or for an external uri (with  <r:id>). If neither <r:id> and the bookmark is present, the <w:anchor> is just a harmless bookmark name, e.g., as a link '#anchor_value'.
PS. document of Microsoft suggests that if the hyperlink is an external uri, the anchor attribute should be ignored. But in practice, Word put the anchor to the end of the uri with '#' prepended. I find this behavior is more reasonable as it corresponds to the behavior of the html anchors.
Therefore,  we might want to keep the <w:anchor> of the hyperlink, even Hyperlink.address is None and the bookmark cannot find in the document itself. How do you think?

@scanny
My commits are actually work in progress.  I will leave your a message when the commit is ready for the  review. So you won't lose too much time on it. :)
Thank you again.

@tanyunshi Thanks for letting me know about the commits, no worries, just let me know when you're ready :)
On the w:anchor bit, the main question in my mind is whether Word complains about loading a document that contains a w:anchor element pointing to a bookmark that is not present in the document. Have you tried making and loading such a document and seeing how Word responds?
If Word doesn't mind I expect we wouldn't either :)  But if it fails to load such a document we'll need to do due diligence to avoid allowing the user to create such a document. Does it make sense?

@scanny @tanyunshi I was wondering if this is getting merged with the main branch and if so when would we be looking at seeing it?
Thanks for all the awesome work!

Hey @rushton3179 I am always on the feature. I am a bit busy untils mid-may. I will catch up the dev after mi-may. :")

Hey @tanyunshi, no worries if you would ever like a hand implementing it let me know. I wrote a function that inserts hyperlinks and put it in the original feature request thread if its of any help too :)

@tanyunshi Great work! Will you be able to finalize this PR? Where should we start if you want help?

@spohner - I think you can pick this up more or less from the beginning of implementation. The analysis document (in the first commit above) is fairly well developed, so should provide the background needed. @tanyunshi also provided a "spiked" implementation, so I'm sure that's useful background as well, but to proceed with a merge we'll need tests, and it will need to be in test-driven commits.
The first step would be developing the acceptance test(s) in (features/{something}.feature). Then next is the unit-test/code pair that addresses the first error in the acceptance test, and so on in rinse-repeat style until the acceptance test passes. You can look at a couple of the recent pull requests for some idea how it all goes:
These two are pretty good examples:
https://github.com/python-openxml/python-docx/pull/261
https://github.com/python-openxml/python-docx/pull/291
Merges maintain a strictly test-driven discipline; it's the only way to keep the library robust while keeping maintenance/committer effort within doable levels :)  The basic idea is:

No code gets merged without its corresponding unit test.
No unit test gets written without a failing acceptance test.
Each commit is one atomic piece of functionality, generally a single property or method.

Let me know with any questions once you've had a chance to look through :)

@scanny I am currently up to implementing a hyperlink style and adding bookmarks in for anchors. I am having a little trouble as when I zip and unzip word files on my mac word does not like them and says they are unreadable.
Into styles.xml I am attempting to add
<w:lsdException w:name="Hyperlink" w:semiHidden="1" w:unhideWhenUsed="1"/>
<w:lsdException w:name="FollowedHyperlink" w:semiHidden="1" w:unhideWhenUsed="1"/>

...
  # In latent styles add this
  <w:style w:type="character" w:styleId="Hyperlink">
    <w:name w:val="Hyperlink"/>
    <w:basedOn w:val="DefaultParagraphFont"/>
    <w:uiPriority w:val="99"/>
    <w:unhideWhenUsed/>
    <w:rsid w:val="00E77728"/>
    <w:rPr>
      <w:color w:val="0563C1" w:themeColor="hyperlink"/>
      <w:u w:val="single"/>
    </w:rPr>
  </w:style>
  <w:style w:type="character" w:styleId="FollowedHyperlink">
    <w:name w:val="FollowedHyperlink"/>
    <w:basedOn w:val="DefaultParagraphFont"/>
    <w:uiPriority w:val="99"/>
    <w:semiHidden/>
    <w:unhideWhenUsed/>
    <w:rsid w:val="00E77728"/>
    <w:rPr>
      <w:color w:val="954F72" w:themeColor="followedHyperlink"/>
      <w:u w:val="single"/>
    </w:rPr>
  </w:style>

Do you have any tips for ensuring the modified default document is correct?
Currently I'm unzipping it, modifying the styles.xml and using zip -r default.zip * and then changing the extension.
I believe this should work as when using the hack I initially wrote when I manually set the rStyle value to 'Hyperlink' it would work as intended when modifying a document that didn't come from the default template.
Also I cannot seem to find any current implementation of inserting bookmarks into runs or paragraphs. The method of generating functions automatically has been a little confusing though so I may be missing something and thought I'd ask.
Other than that the basic feature tests I have written are working and I am just trying to fine tune it. Once I have those done I plan to do some more extensive testing.

I think I'll need a little more to go on to fully understand what you're trying to do, but in general you shouldn't have to work with zip files at all. That's all abstracted out by the docx.opc sub-package.
A Word file as a whole is known as a package. It can be saved as a zip archive, which is what a .docx file is, but can also be stored in other ways, such as in a database and so on. Each individual "file" within the zip archive is known as a part. This is the language you'll see reflected in the opc subpackage.
The opc subpackage takes care of all the details of opening (unzipping) and saving (zipping) .docx files and getting the contents into and out of the various Part subtypes. There's already a StylesPart object: https://github.com/python-openxml/python-docx/blob/master/docx/parts/styles.py
The styles part is a subclass of XmlPart, which has the root XML object of that part on .element as a pre-parsed lxml object. Actually lxml is loosely wrapped with xmlchemy, which is the foundation for the docx.oxml layer, but the point is all lxml._Element calls work on every element. Best not to go below that interface for modifying XML.
Pretty much every kind of operation on the XML has been done somewhere in the library already, and can serve as an example. If you explain more specifically what you're trying to accomplish I can probably guide you to those examples.
If all you want to do is add a few styles to the document, there's already API for that. Check out this page in the documentation: http://python-docx.readthedocs.io/en/latest/api/style.html#styles-objects

@scanny Awesome, that should get me through what I need and I will hopefully have a PR ready in the next couple of days. When it comes to testing, so far I have come up with most scenarios I can think of in the acceptance testing and I have noticed you comment before that unit testing is in this when acceptance test cases fail. If this is the case is there anything I should write unit test for just to ensure everything is as needed? Cheers!

The general flow is you write an acceptance test before any code. It should fail, of course, because the code that implements it isn't there. You mark the acceptance test with the @wip decorator so the test suite can skip these and therefore still pass. This acceptance test gets committed as a separate commit with message starting with 'acpt:...'.
Where the acceptance test fails determines what the first unit test and code is written. Each commit is atomic, generally meaning one unit test and just the code it takes to make it pass. After a few commits, the acceptance test passes, the @wip decorator is removed from it, and that's one cycle.
This pattern is clearly visible in the commit history, which you should study a bit to get the flow. The one for python-pptx has exactly the same pattern and is perhaps more active; just look for a commit starting with 'acpt:' and read up from there.
https://github.com/scanny/python-pptx/commits/master
If you don't get this right you end up rewriting stuff or putting me to unnecessary effort (time) when it comes to merging.

Gotchya, while I have actually done this all in one commit on my branch (but using a similar workflow) I can set up a new branch and step through it like this so you get something that is easy to review and has all the necessary tests. It might be a week or so until I get it done but it shouldn't be too far off as it is all currently working.

Hi @tanyunshi, just wanted to let you know that your analysis doc made it into release v1.0.0 going out in the next few days.
Right now that's in this commit: https://github.com/python-openxml/python-docx/commit/4935c302c440eaf97a412a51e5d1311e8ce4687f
But the SHA may change across rebases and force-pushes as it wends its way to release probably later this week.
In any case, wanted to thank you for that work and let you know it had been incorporated :)
There's no Paragraph.add_hyperlink() included yet, my main interest at the moment is improving granular extraction of text from documents, but many of the supporting objects are there and if you still want to take a crack at it these several years later just let me know :)


Scrolling with an external mouse is very janky

When scrolling with the wheel of an external mouse, instead of smooth scrolling like when swiping on the touchpad, I get a couple of "ticks", then the view stops for a second, and then jumps to the final location.
It's a cheap wireless mouse and I use Scroll Reverser with it, but other applications don't have this problem so I doubt it's related to that.

The bounds.origin didn't change when using the wheel on mouse, not sure why 🤔
@EditViewController.swift Line 129

@jansol Do you know the DPI of this mouse and the sensitivities you had? I'll try to look into this.

@nangtrongvuon Sorry, your comment shomehow slipped by me. The mouse in question is this one (Japanese only, unfortunately) and I've been using it in its 1600 DPI mode.

Have you tried scrolling on some other mouse? Perhaps its this one that's janky. I use a bunch of gaming mice and scrolling on xi feels fine to me. (Zowie FK2, Steelseries Kana V2, Logitech G305/G603, CM MasterMouse S)

I have, Logitech G3 and G90, the same issue.

Thanks for the reports, I'll investigate this when I have time.

Yea I couldn't reproduce this either, but haven't dug in too deep.

Similar issue here:
I'm using a microsoft optical mouse with wheel, and scrolling is truncated when using the wheel to scroll the text.
when using scrollbar it is smooth.
Thank you!
Details
macOS 10.14.5
rustc 1.36.0 (a53f9df32 2019-07-03)
rustup

@dimitre which commit are you on in xi-mac?

@dimitre Hey, this should already be fixed with the latest xi-mac master.


[BUG] Logs unable to reach OpenSearch

Bug Report
Describe the bug
We have Fluentbit sidecars, the logs are unable to reach OpenSearch. We see no errors in Fluentbit logs. We do not understand what is happening because we see no errors in the Fluentbit container logs.
Fluentbit Sidecar Log Message:
Fluent Bit v1.9.9
* Copyright (C) 2015-2022 The Fluent Bit Authors
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
* https://fluentbit.io

[2022/11/16 00:34:42] [ info] Configuration:
[2022/11/16 00:34:42] [ info]  flush time     | 1.000000 seconds
[2022/11/16 00:34:42] [ info]  grace          | 5 seconds
[2022/11/16 00:34:42] [ info]  daemon         | 0
[2022/11/16 00:34:42] [ info] ___________
[2022/11/16 00:34:42] [ info]  inputs:
[2022/11/16 00:34:42] [ info]      tail
[2022/11/16 00:34:42] [ info]      tail
[2022/11/16 00:34:42] [ info] ___________
[2022/11/16 00:34:42] [ info]  filters:
[2022/11/16 00:34:42] [ info]      modify.0
[2022/11/16 00:34:42] [ info]      modify.1
[2022/11/16 00:34:42] [ info]      modify.2
[2022/11/16 00:34:42] [ info] ___________
[2022/11/16 00:34:42] [ info]  outputs:
[2022/11/16 00:34:42] [ info]      es.0
[2022/11/16 00:34:42] [ info]      splunk.1
[2022/11/16 00:34:42] [ info] ___________
[2022/11/16 00:34:42] [ info]  collectors:
[2022/11/16 00:34:42] [ info] [fluent bit] version=1.9.9, commit=, pid=89
[2022/11/16 00:34:42] [debug] [engine] coroutine stack size: 24576 bytes (24.0K)
[2022/11/16 00:34:42] [ info] [storage] version=1.3.0, type=memory-only, sync=normal, checksum=disabled, max_chunks_up=128
[2022/11/16 00:34:42] [ info] [cmetrics] version=0.3.7
[2022/11/16 00:34:42] [debug] [tail:tail.0] created event channels: read=21 write=22
[2022/11/16 00:34:42] [debug] [input:tail:tail.0] flb_tail_fs_inotify_init() initializing inotify tail input
[2022/11/16 00:34:42] [debug] [input:tail:tail.0] inotify watch fd=27
[2022/11/16 00:34:42] [debug] [input:tail:tail.0] scanning path /var/log/iserver/ServerAudit*.log
[2022/11/16 00:34:42] [debug] [input:tail:tail.0] cannot read info from: /var/log/iserver/ServerAudit*.log
[2022/11/16 00:34:42] [debug] [input:tail:tail.0] 0 new files found on path '/var/log/iserver/ServerAudit*.log'
[2022/11/16 00:34:42] [debug] [tail:tail.1] created event channels: read=28 write=29
[2022/11/16 00:34:42] [debug] [input:tail:tail.1] flb_tail_fs_inotify_init() initializing inotify tail input
[2022/11/16 00:34:42] [debug] [input:tail:tail.1] inotify watch fd=34
[2022/11/16 00:34:42] [debug] [input:tail:tail.1] scanning path /var/log/iserver/DSSErrors*.log
[2022/11/16 00:34:42] [debug] [input:tail:tail.1] cannot read info from: /var/log/iserver/DSSErrors*.log
[2022/11/16 00:34:42] [debug] [input:tail:tail.1] 0 new files found on path '/var/log/iserver/DSSErrors*.log'
[2022/11/16 00:34:42] [debug] [filter:modify:modify.0] Initialized modify filter with 0 conditions and 3 rules
[2022/11/16 00:34:42] [debug] [filter:modify:modify.1] Initialized modify filter with 0 conditions and 1 rules
[2022/11/16 00:34:42] [debug] [filter:modify:modify.2] Initialized modify filter with 0 conditions and 1 rules
[2022/11/16 00:34:42] [debug] [es:es.0] created event channels: read=35 write=36
[2022/11/16 00:34:42] [debug] [output:es:es.0] host=vpc-elasticsearchcl-redacted.es.amazonaws.com port=443 uri=/_bulk index=iserver-logs type=doc
[2022/11/16 00:34:42] [debug] [splunk:splunk.1] created event channels: read=47 write=48
[2022/11/16 00:34:42] [ info] [output:es:es.0] worker #0 started
[2022/11/16 00:34:42] [ info] [output:splunk:splunk.1] worker #1 started
[2022/11/16 00:34:42] [ info] [output:splunk:splunk.1] worker #0 started
[2022/11/16 00:34:42] [ info] [output:es:es.0] worker #1 started
[2022/11/16 00:34:42] [debug] [router] match rule tail.0:es.0
[2022/11/16 00:34:42] [debug] [router] match rule tail.0:splunk.1
[2022/11/16 00:34:42] [debug] [router] match rule tail.1:es.0
[2022/11/16 00:34:42] [ info] [sp] stream processor started
[2022/11/16 00:34:42] [debug] [input:tail:tail.0] [static files] processed 0b, done
[2022/11/16 00:34:42] [debug] [input:tail:tail.1] [static files] processed 0b, done
[2022/11/16 00:35:42] [debug] [input:tail:tail.0] scanning path /var/log/iserver/ServerAudit*.log
[2022/11/16 00:35:42] [debug] [input:tail:tail.0] inode=5342925928760031785 with offset=0 appended as /var/log/iserver/ServerAudit-2022-11-16.log
[2022/11/16 00:35:42] [debug] [input:tail:tail.0] scan_glob add(): /var/log/iserver/ServerAudit-2022-11-16.log, inode<PHONE_NUMBER>760031785
[2022/11/16 00:35:42] [debug] [input:tail:tail.0] 1 new files found on path '/var/log/iserver/ServerAudit*.log'
[2022/11/16 00:35:42] [debug] [input:tail:tail.1] scanning path /var/log/iserver/DSSErrors*.log
[2022/11/16 00:35:42] [debug] [input:tail:tail.1] inode=10747040000057398530 with offset=0 appended as /var/log/iserver/DSSErrors.log
[2022/11/16 00:35:42] [debug] [input:tail:tail.1] scan_glob add(): /var/log/iserver/DSSErrors.log, inode -7699704073652153086
[2022/11/16 00:35:42] [debug] [input:tail:tail.1] 1 new files found on path '/var/log/iserver/DSSErrors*.log'
[2022/11/16 00:35:42] [debug] [input chunk] update output instances with new chunk size diff=10262
[2022/11/16 00:35:42] [debug] [input:tail:tail.0] [static files] processed 6.8K
[2022/11/16 00:35:42] [debug] [input:tail:tail.0] inode=5342925928760031785 file=/var/log/iserver/ServerAudit-2022-11-16.log promote to TAIL_EVENT
[2022/11/16 00:35:42] [ info] [input:tail:tail.0] inotify_fs_add(): inode=5342925928760031785 watch_fd=1 name=/var/log/iserver/ServerAudit-2022-11-16.log
[2022/11/16 00:35:42] [debug] [input:tail:tail.0] [static files] processed 0b, done
[2022/11/16 00:35:42] [debug] [input chunk] update output instances with new chunk size diff=53586
[2022/11/16 00:35:42] [debug] [input:tail:tail.1] [static files] processed 31.8K
[2022/11/16 00:35:42] [debug] [input chunk] update output instances with new chunk size diff=53269
[2022/11/16 00:35:42] [debug] [input:tail:tail.1] [static files] processed 31.9K
[2022/11/16 00:35:42] [debug] [input chunk] update output instances with new chunk size diff=3941
[2022/11/16 00:35:42] [debug] [input:tail:tail.1] [static files] processed 2.5K
[2022/11/16 00:35:42] [debug] [input:tail:tail.1] inode=10747040000057398530 file=/var/log/iserver/DSSErrors.log promote to TAIL_EVENT
[2022/11/16 00:35:42] [ info] [input:tail:tail.1] inotify_fs_add(): inode=10747040000057398530 watch_fd=1 name=/var/log/iserver/DSSErrors.log
[2022/11/16 00:35:42] [debug] [input:tail:tail.1] [static files] processed 0b, done
[2022/11/16 00:35:43] [debug] [task] created task=0x7fddc8e42d20 id=0 OK
[2022/11/16 00:35:43] [debug] [output:es:es.0] task_id=0 assigned to thread #0
[2022/11/16 00:35:43] [debug] [output:splunk:splunk.1] task_id=0 assigned to thread #0
[2022/11/16 00:35:43] [debug] [task] created task=0x7fddc8e42d90 id=1 OK
[2022/11/16 00:35:43] [debug] [output:es:es.0] task_id=1 assigned to thread #1
[2022/11/16 00:35:43] [debug] [http_client] not using http_proxy for header
[2022/11/16 00:35:43] [debug] [http_client] not using http_proxy for header
[2022/11/16 00:35:43] [debug] [upstream] KA connection #86 to ip-10-0-0-0.redacted.compute.internal:8088 is now available
[2022/11/16 00:35:43] [debug] [out flush] cb_destroy coro_id=0
[2022/11/16 00:35:43] [debug] [http_client] not using http_proxy for header
[2022/11/16 00:35:43] [debug] [output:es:es.0] HTTP Status=200 URI=/_bulk
[2022/11/16 00:35:43] [debug] [upstream] KA connection #87 to vpc-elasticsearchcl-redacted.es.amazonaws.com:443 is now available
[2022/11/16 00:35:43] [debug] [out flush] cb_destroy coro_id=0
[2022/11/16 00:35:43] [debug] [retry] new retry created for task_id=0 attempts=1
[2022/11/16 00:35:43] [ warn] [engine] failed to flush chunk '89-1668558942.65916959.flb', retry in 11 seconds: task_id=0, input=tail.0 > output=es.0 (out_id=0)
[2022/11/16 00:35:43] [debug] [output:es:es.0] HTTP Status=200 URI=/_bulk
[2022/11/16 00:35:43] [debug] [upstream] KA connection #88 to vpc-elasticsearchcl-redacted.es.amazonaws.com:443 is now available
[2022/11/16 00:35:43] [debug] [out flush] cb_destroy coro_id=0
[2022/11/16 00:35:43] [debug] [retry] new retry created for task_id=1 attempts=1
[2022/11/16 00:35:43] [ warn] [engine] failed to flush chunk '89-1668558942.70974100.flb', retry in 7 seconds: task_id=1, input=tail.1 > output=es.0 (out_id=0)
[2022/11/16 00:35:50] [debug] [output:es:es.0] task_id=1 assigned to thread #0
[2022/11/16 00:35:50] [debug] [upstream] KA connection #87 to vpc-elasticsearchcl-redacted.es.amazonaws.com:443 has been assigned (recycled)
[2022/11/16 00:35:50] [debug] [http_client] not using http_proxy for header
[2022/11/16 00:35:50] [debug] [output:es:es.0] HTTP Status=200 URI=/_bulk
[2022/11/16 00:35:50] [debug] [upstream] KA connection #87 to vpc-elasticsearchcl-redacted.es.amazonaws.com:443 is now available
[2022/11/16 00:35:50] [debug] [out flush] cb_destroy coro_id=1
[2022/11/16 00:35:50] [debug] [task] task_id=1 reached retry-attempts limit 1/1
[2022/11/16 00:35:50] [ warn] [engine] chunk '89-1668558942.70974100.flb' cannot be retried: task_id=1, input=tail.1 > output=es.0
[2022/11/16 00:35:50] [debug] [task] destroy task=0x7fddc8e42d90 (task_id=1)
[2022/11/16 00:35:54] [debug] [output:es:es.0] task_id=0 assigned to thread #1
[2022/11/16 00:35:54] [debug] [upstream] KA connection #88 to vpc-elasticsearchcl-redacted.es.amazonaws.com:443 has been assigned (recycled)
[2022/11/16 00:35:54] [debug] [http_client] not using http_proxy for header
[2022/11/16 00:35:54] [debug] [output:es:es.0] HTTP Status=200 URI=/_bulk
[2022/11/16 00:35:54] [debug] [upstream] KA connection #88 to vpc-elasticsearchcl-redacted.es.amazonaws.com:443 is now available
[2022/11/16 00:35:54] [debug] [out flush] cb_destroy coro_id=1
[2022/11/16 00:35:54] [debug] [task] task_id=0 reached retry-attempts limit 1/1
[2022/11/16 00:35:54] [ warn] [engine] chunk '89-1668558942.65916959.flb' cannot be retried: task_id=0, input=tail.0 > output=es.0
[2022/11/16 00:35:54] [debug] [task] destroy task=0x7fddc8e42d20 (task_id=0)
[2022/11/16 00:36:13] [debug] [upstream] drop keepalive connection #-1 to ip-10-0-0-0.redacted.compute.internal:8088 (keepalive idle timeout)
[2022/11/16 00:36:13] [debug] [socket] could not validate socket status for #86 (don't worry)
[2022/11/16 00:36:20] [debug] [upstream] drop keepalive connection #-1 to vpc-elasticsearchcl-redacted.es.amazonaws.com:443 (keepalive idle timeout)
[2022/11/16 00:36:20] [debug] [socket] could not validate socket status for #87 (don't worry)
[2022/11/16 00:36:25] [debug] [upstream] drop keepalive connection #-1 to vpc-elasticsearchcl-redacted.es.amazonaws.com:443 (keepalive idle timeout)
[2022/11/16 00:36:25] [debug] [socket] could not validate socket status for #88 (don't worry)

Fluentbit Configmap:
apiVersion: v1
metadata:
  name: iserver-fluentbit
data:
  fluent-bit.conf: """

    [SERVICE]
        Flush         1
        Log_Level     debug
        Daemon        off
        Parsers_File  parsers.conf

    [INPUT]
        Name tail
        Tag  iserver.audit.log
        Multiline Off
        Path /var/log/iserver/ServerAudit*.log

    [INPUT]
        Name tail
        Tag  iserver.dsserrors.log
        Multiline Off
        Path /var/log/iserver/DSSErrors*.log

    [FILTER]
        Name      modify
        Match     *
        Add       POD_NAME      {{ POD NAME }}
        Add       ENV_NAME      {{ RELEASE NAME }}
        Add       CLUSTER_NAME  {{ CLUSTER NAME }}

    [FILTER]
        Name modify
        Match iserver.dsserrors.log
        Add    LOGNAME      dsserror

    [OUTPUT]
        Name    es
        Match   iserver.*.*
        Host    {{ OPENSEARCH HOST }}
        Port    {{ OPENSEARCH PORT }}
        Logstash_Format  True
        Logstash_Prefix  iserver-logs
        Index   iserver-logs
        Type    doc
        AWS_Auth Off
        AWS_Region {{ AWS REGION }}
        tls     On
        tls.verify Off

  """

  parsers.conf: |2

    [PARSER]
        Name   apache2
        Format regex
        Regex  ^(?<host>[^ ]*) [^ ]* (?<user>[^ ]*) \[(?<time>[^\]]*)\] "(?<method>\S+)(?: +(?<path>[^ ]*) +\S*)?" (?<code>[^ ]*) (?<size>[^ ]*)(?: "(?<referer>[^\"]*)" "(?<agent>.*)")?$
        Time_Key time
        Time_Format %d/%b/%Y:%H:%M:%S %z

    [PARSER]
        Name   apache_error
        Format regex
        Regex  ^\[[^ ]* (?<time>[^\]]*)\] \[(?<level>[^\]]*)\](?: \[pid (?<pid>[^\]]*)\])?( \[client (?<client>[^\]]*)\])? (?<message>.*)$

    [PARSER]
        Name   nginx
        Format regex
        Regex  ^(?<remote>[^ ]*) (?<host>[^ ]*) (?<user>[^ ]*) \[(?<time>[^\]]*)\] "(?<method>\S+)(?: +(?<path>[^\"]*?)(?: +\S*)?)?" (?<code>[^ ]*) (?<size>[^ ]*)(?: "(?<referer>[^\"]*)" "(?<agent>[^\"]*)")
        Time_Key time
        Time_Format %d/%b/%Y:%H:%M:%S %z

    [PARSER]
        Name   json
        Format json
        Time_Key time
        Time_Format %d/%b/%Y:%H:%M:%S %z

    [PARSER]
        Name        docker
        Format      json
        Time_Key    time
        Time_Format %Y-%m-%dT%H:%M:%S.%L
        Time_Keep   On

    [PARSER]
        Name        syslog
        Format      regex
        Regex       ^\<(?<pri>[0-9]+)\>(?<time>[^ ]* {1,2}[^ ]* [^ ]*) (?<host>[^ ]*) (?<ident>[a-zA-Z0-9_\/\.\-]*)(?:\[(?<pid>[0-9]+)\])?(?:[^\:]*\:)? *(?<message>.*)$
        Time_Key    time
        Time_Format %b %d %H:%M:%S

    [PARSER]
        Name    kube-custom
        Format  regex
        Regex   (?<tag>[^.]+)?\.?(?<pod_name>[a-z0-9](?:[-a-z0-9]*[a-z0-9])?(?:\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*)_(?<namespace_name>[^_]+)_(?<container_name>.+)-(?<docker_id>[a-z0-9]{64})\.log$

    [PARSER]
        Name dsserror
        Format  regex
        Time_key  time
        Regex  ^(?<time>[^\[]+)\s(\[HOST:(?<host>[^\]]+)\]\[SERVER:(?<server>[^\]]+)\]\[PID:(?<processid>[^\]]+)\]\[THR:(?<threadid>[^\]]+)\]\[([^\]]+)\]\[([^\]]+)\](\[([^\]]+)\])?\[UID:([^\]]+)\]\[SID:([^\]]+)\]\[OID:([^\]]+)\])\s*(?<message>.*)\s*(?<message>.*)\s*(?<message>.*)\s*(?<message>.*)\s*(?<message>.*)\s*(?<message>.*)\s*(?<message>.*)$
        Time_Format %Y-%m-%d %H:%M:%S.%L
        Time_Keep On

Expected behavior
Ability to send logs to OpenSearch, errors produced when unable to send logs to OpenSearch
Your Environment

Version used: fluent-bit:1.9.9
Configuration: config map provided
Environment name and version: Kubernetes 1.22

Hi @zander312 , seems like your fluentbit having some trouble when pushing the logs to your es output. you can try enable error tracing on your es output plugin like this for better debugging
    [OUTPUT]
        Name    es
        Match   iserver.*.*
        Host    {{ OPENSEARCH HOST }}
        Port    {{ OPENSEARCH PORT }}
        Logstash_Format  True
        Logstash_Prefix  iserver-logs
        Index   iserver-logs
        Type    doc
        AWS_Auth Off
        AWS_Region {{ AWS REGION }}
        tls     On
        tls.verify Off
        Trace_Error On

Enabling error tracing is probably the right way to tackle this problem. Please reopen if you have more details and think there might be a problem in OpenSearch.

@andrross @kmdrn7 we were able to solve the issue, there were issues with the health of the OpenSearch cluster and we had run out of space for indexes.
However, one thing that concerned me was that we were receiving 200 responses back from the OpenSearch cluster. As you can see from the logs I attached. HTTP Status=200 URI=/_bulk We were not receiving the usual errors in FluentBit that we get when this kind of thing happens.
We were receiving these 200 responses even though the actual operation was failing on the OpenSearch side. I would have expected a better response code that indicates a failure. The AWS ElasticSearch team pointed out that it is a bulk API and that is why were receiving 200 responses back. But I am still a bit puzzled about that functionality.

Check out the documentation for the bulk API. Since it is a batch-style request, you have to look at the per-item responses since partial failures are possible. More detailed status codes are available for each item.

Short of transactional support, I think there's a feature request here to supply a parameter to bulk to abort on first failure. We also have https://github.com/opensearch-project/OpenSearch/issues/4562 and https://github.com/opensearch-project/OpenSearch/issues/3625. @zander312 if you believe that would help, open an issue?


Bugs to fix before launch

[ ] Baltic ecoregion, spr.27.22-32, 2021 -->  Error in Recruitment plot Error in check_aesthetics: Aesthetics must be either length 1 or the same as the data (1): ymin, ymax, x and y
126:

@Neilmagi @sarahlmillar re ghl.27.1-2, 2021, I just noticed that the headline advice in 2021 gives 2 separate advice for 2022 and 2023. In addition, it's giving us an error cause the advice view entries are not in consecutive years (the previous is in 2019). Should we take it off the list?

Yeah we need to have a good think about what to do with these years and stocks where there is no assessment but where there is valid advice from a previous assessment. I don't think this is something we'll do prior to launch, so I'd agree to taking it off the list ( also tur.27.4)

@Neilmagi I will copy here the stocks we need to have a look from above:

[ ] tur.27.4, 2019, TAC change column catch scen table
[ ] ple.27.7d, 2019 Problem with the implicit transmute() step. in catch scen table
[ ] nop.27.3a4, 2019 problem with missed columns catch scen table
[ ] dgs.27.nea, 2022 (azores) Error in UseMethod: no applicable method for 'filter' applied to an object of class "list"

@lucalamoni  sorry for getting here a bit late. Agree - any stock where there are 2 advice for 2 different years in one advice sheet should not be included in this release. This is one of the main things we need the advice view team to fix up

@lucalamoni @Neilmagi years should only be plotted as whole integers, no decimals

@sarahlmillar @Neilmagi re tur.27.4 I would like to keep it in. The code can now handle the case in which a stock does not have an advice view entry in the previous year. But we still get the catch scenario table and the SSB-F_catches plot.


Add an easy way to bind konacha server to <IP_ADDRESS>

First, sorry if such a way exists, but I couldn't find it.
Running konacha from vagrant machine (or, any VM) requires running the web server with bind to <IP_ADDRESS> (or any specific route) instead of <IP_ADDRESS> so that using the VM port-forwarding, it will be available from the host computer.
This might not be the case for every dev machine, so there needs to be some easy way to configure it from the running command.
Something like: rake konacha:serve BIND=<IP_ADDRESS>

Try this in your config/initializers/konacha.rb:
Konacha.configure do |config|
  config.port     = "<IP_ADDRESS>"
end if defined?(Konacha)

Hi @jfirebaugh , thanks for the quick reply.
I knew about the configuration settings, what I meant by this issue, is that a CLI config might be needed here.
As I wrote, not all developers work with a VM, and so, for obvious reasons, we don't want <IP_ADDRESS> to be the default. This is why a way to configure it directly when running the command seems like a good solution.

You can do something like:
Konacha.configure do |config|
  config.port = ENV['PORT'] || '<IP_ADDRESS>'
end if defined?(Konacha)

and  PORT=<IP_ADDRESS> rake konacha:serve


Sync with offline, manually-curated music libraries

Feature request from Tim.
Need to learn more, as I don't fully understand the technical and practical requirements of this yet.

[..] a public database with the dances corresponding to the music on folk CD's.
I was thinking about something CDDB (freedb) like
-- @wlemkens

I presume this feature is about updating the tags in a local library with data from the online database.


Failed builds result in silent removal of packages to be upgraded

Describe the bug
Vcpkg can't handle failed upgrades.
To Reproduce

Start upgrade process of installed packages, e.g.:

C:\vcpkg>vcpkg upgrade --no-dry-run
The following packages will be rebuilt:
  * bzip2[core]:x64-windows-static
  * curl[core,non-http,schannel,ssl,sspi,winssl]:x64-windows
  * freetype[bzip2,core,png]:x64-windows-static
  * libpng[core]:x64-windows-static
  * sdl2[core,vulkan]:x64-windows
  * zlib[core]:x64-windows
  * zlib[core]:x64-windows-static
The following packages will be built and installed:
  * brotli[core]:x64-windows-static
Additional packages (*) will be modified to complete this operation.
Starting package 1/15: freetype:x64-windows-static
...

Have one of the packages fail build process due to some reason (e.g. some random host not being reachable):

-- Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-1-any.pkg.tar.xz... Failed. Status: 28;"Timeout was reached"
CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:181 (message):

      Failed to download file.
      If you use a proxy, please set the HTTPS_PROXY and HTTP_PROXY environment
      variables to "https://user:password@your-proxy-ip-address:port/".
      Otherwise, please submit an issue at https://github.com/Microsoft/vcpkg/issues

Call Stack (most recent call first):
  scripts/cmake/vcpkg_find_acquire_program.cmake:438 (vcpkg_download_distfile)
  scripts/cmake/vcpkg_fixup_pkgconfig.cmake:270 (vcpkg_find_acquire_program)
  ports/brotli/portfile.cmake:25 (vcpkg_fixup_pkgconfig)
  scripts/ports.cmake:79 (include)

Error: Building package brotli:x64-windows-static failed with: BUILD_FAILED

Expected behavior
System state is not changed if upgrade is not successful.
Actual behavior
Upgraded packages are removed and no longer available, rendering system inoperable, as user is unable to reinstall the no-longer-available packages due to reasons out of their control.
C:\vcpkg>vcpkg upgrade --no-dry-run
All installed packages are up-to-date with the local portfiles.

C:\vcpkg>vcpkg list
capstone:x64-windows-static                        4.0.2#1          Multi-architecture disassembly framework
capstone[arm64]:x64-windows-static                                  Capstone disassembly support for ARM64
capstone[arm]:x64-windows-static                                    Capstone disassembly support for ARM
capstone[x86]:x64-windows-static                                    Capstone disassembly support for x86
glfw3:x64-windows-static                           3.3.2            GLFW is a free, Open Source, multi-platform libr...
vulkan:x64-windows                                 <IP_ADDRESS>-1       A graphics and compute API that provides high-ef...

Should be fixed by #13889.

#13889 fixes the msys problem, but this issue is more general, about any build failure that might happen.

@wolfpld Therefore,  we set more mirrors to avoid this issue.


tagged: fix lifetime on BerObjectHeader

The lifetime for BerObjectHeader<'hdr> was elided so it was not bound to
'a. However, it is clear that the BerObjectHeader<'hdr> should be bound
to the input that it is parsing.
This was generating a strange compiler warning for me as shown below.
Lifetime elision rules can be found here:

https://doc.rust-lang.org/reference/lifetime-elision.html

Steps to reproduce (roughly):
fn parse_tag_0_implicit_octectstring(input: &[u8]) -> BerResult {
    parse_ber_tagged_implicit(0, |input, header, rec| {
        // unwrapping for simplicity
        let (input, content) = parse_ber_content(BerTag::OctetString)(input, &header, rec).unwrap();
        // deref will cause a clone
        let obj = BerObject::from_header_and_content(*header, content);
        Ok((input, obj))
    })(input)
}

Full error message:
error[E0495]: cannot infer an appropriate lifetime for lifetime parameter 'hdr in function call due to conflicting requirements
  --> foo/src/lib.rs:9:19
   |
9  |         let obj = BerObject::from_header_and_content(*header, content);
   |                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
note: first, the lifetime cannot outlive the anonymous lifetime #3 defined on the body at 7:34...
  --> foo/src/lib.rs:7:34
   |
7  |       parse_ber_tagged_implicit(0, |input, header, rec| {
   |  __________________________________^
8  | |         let (input, content) = parse_ber_content(BerTag::OctetString)(input, &header, rec).unwrap();
9  | |         let obj = BerObject::from_header_and_content(*header, content);
10 | |         Ok((input, obj))
11 | |     })(input)
   | |_____^
note: ...so that the expression is assignable
  --> foo/src/lib.rs:9:54
   |
9  |         let obj = BerObject::from_header_and_content(*header, content);
   |                                                      ^^^^^^^
   = note: expected `der_parser::ber::BerObjectHeader<'_>`
              found `der_parser::ber::BerObjectHeader<'_>`
note: but, the lifetime must be valid for the anonymous lifetime #1 defined on the function body at 6:1...
  --> foo/src/lib.rs:6:1
   |
6  | / fn parse_tag_0_implicit_octectstring(input: &[u8]) -> BerResult {
7  | |     parse_ber_tagged_implicit(0, |input, header, rec| {
8  | |         let (input, content) = parse_ber_content(BerTag::OctetString)(input, &header, rec).unwrap();
9  | |         let obj = BerObject::from_header_and_content(*header, content);
10 | |         Ok((input, obj))
11 | |     })(input)
12 | | }
   | |_^
note: ...so that the expression is assignable
  --> foo/src/lib.rs:7:5
   |
7  | /     parse_ber_tagged_implicit(0, |input, header, rec| {
8  | |         let (input, content) = parse_ber_content(BerTag::OctetString)(input, &header, rec).unwrap();
9  | |         let obj = BerObject::from_header_and_content(*header, content);
10 | |         Ok((input, obj))
11 | |     })(input)
   | |_____________^
   = note: expected `std::result::Result<(&[u8], der_parser::ber::BerObject<'_>), _>`
              found `std::result::Result<(&[u8], der_parser::ber::BerObject<'_>), _>`

error: aborting due to previous error; 1 warning emitted

For more information about this error, try `rustc --explain E0495`.
error: could not compile `foo`.

Thanks for the detailed issue, with example and fix.
Applied!
I will also backport the fix for 4.x


Revert "Correctly handle QUICHE_ERR_STREAM_RESET (#305)"

This reverts commit b5453c45c393612f84817841b41899331e58c6e3.

@normanmaurer can you explain the reason for reverting?

@NiteshKant i am just testing something related to a segfault on windows ... I will not merge this one


Teacher forcing

Removes autoregressive loop from model.call into model.call_n.
This reduces model memory requirements by a factor of roughly storm_duration / N_FLOOD_MAPS because we no longer predict the entire sequence of flood maps, which unlocks GPU training.

Let's put together a smaller PR.
This contains more code than we want to review at a time. It also includes some code we know we don't want to merge as is, such as metastore.py and featurelabelchunks.py (those two files I rewrote as https://github.com/UrbanSystemsLab/climateiq-cnn/pull/112)
Can you put together a PR with just the changes to the model itself to start? The dataset generation we'll want to work on before reviewing & merging.

Let's put together a smaller PR.
This contains more code than we want to review at a time. It also includes some code we know we don't want to merge as is, such as metastore.py and featurelabelchunks.py (those two files I rewrote as #112)
Can you put together a PR with just the changes to the model itself to start? The dataset generation we'll want to work on before reviewing & merging.

Sure, I've reverted the extra files. The branch with e2e training colab is now at https://github.com/Katsutoshii/climateiq-cnn/tree/teacher-forcing-e2e


DwC Checklist importer + specs

Example cases for occurrence and checklist files

Codecov Report

Merging #2470 (7b42276) into development (d239dd0) will decrease coverage by 22.66%.
The diff coverage is 2.36%.

:exclamation: Current head 7b42276 differs from pull request most recent head 74648bd. Consider uploading reports for the commit 74648bd to get more accurate results

@@               Coverage Diff                @@
##           development    #2470       +/-   ##
================================================
- Coverage        87.75%   65.08%   -22.67%
================================================
  Files             1849     1357      -492
  Lines            63652    37664    -25988
================================================
- Hits             55855    24515    -31340
- Misses            7797    13149     +5352

Impacted Files
Coverage Δ

app/models/import_dataset/darwin_core/checklist.rb
8.33% <0.00%> (-5.40%)
:arrow_down:

app/models/dataset_record/darwin_core/taxon.rb
9.00% <3.57%> (-1.60%)
:arrow_down:

spec/support/concerns/random_token_methods.rb
2.63% <0.00%> (-97.37%)
:arrow_down:

spec/support/concerns/request/api.rb
11.11% <0.00%> (-88.89%)
:arrow_down:

app/models/identifier/global/issn.rb
14.28% <0.00%> (-85.72%)
:arrow_down:

app/models/identifier/global/isbn.rb
8.33% <0.00%> (-85.42%)
:arrow_down:

app/models/protonym/becomes.rb
16.43% <0.00%> (-79.46%)
:arrow_down:

lib/catalog/description_from_observation_matrix.rb
13.22% <0.00%> (-78.10%)
:arrow_down:

app/models/identifier/global/orcid.rb
22.22% <0.00%> (-77.78%)
:arrow_down:

app/models/identifier/global/lccn.rb
11.53% <0.00%> (-76.93%)
:arrow_down:

... and 1001 more

Continue to review full report at Codecov.

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

@LordFlashmeow can you resolve this: https://github.com/SpeciesFileGroup/taxonworks/pull/2470/checks?check_run_id=3606130946#step:21:86
@LocoDelAssembly after that I think we can pull?

originalGenusNameID need to be relaxed and not make mandatory (breaks dataset listed in https://ipt.gbif.org/manual/en/ipt/2.4/checklist-data#exemplar-datasets, our original code was able to handle accepted names). Also breaks ITIS' DwC-As as well since them do not have originalGenusNameID either.
But I think it is best I merge this anyway and work on top of it to fix. Getting originalGenusNameID is much more involved for the general case I'm afraid, lots of lookups on other records to see which one seems to be the original (having originalGenusNameID as best source to make a decision when available).


[BUG] Progress bar with auto_refresh=False about 30x slower

Read the docs
I have read all of https://rich.readthedocs.io/en/latest/progress.html
Describe the bug
When I create a progress bar with auto_refresh=False the worker loop seems to be about 30 - 40 times slower
With auto_refresh=True the ETA is about 1.5 minutes
Working... ╸━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━   2% 0:01:37

And with auto_refresh=False the ETA is 38 minutes.
Working... ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━   1% 0:38:17

To Reproduce
#!/usr/bin/env python3

import time
from rich.progress import Progress

lines = range(1*10**6)

for auto_refresh in [True, False]:
    with Progress(auto_refresh=auto_refresh) as progress:
        task = progress.add_task("Working...", visible=True, total=len(lines))
        for line in lines:
            progress.update(task, advance=1)
            if not auto_refresh:
                progress.refresh()
            time.sleep(0.00001)

Platform
Mac BigSur (10.15.2)
Python 3.9.7
Diagnose
I may ask you to cut and paste the output of the following commands. It may save some time if you do it now.
python -m rich.diagnose
╭───────────────────────── <class 'rich.console.Console'> ─────────────────────────╮
│ A high level console interface.                                                  │
│                                                                                │
│ ╭──────────────────────────────────────────────────────────────────────────────╮ │
│ │ <console width=236 ColorSystem.EIGHT_BIT>                                    │ │
│ ╰──────────────────────────────────────────────────────────────────────────────╯ │
│                                                                                │
│     color_system = '256'                                                         │
│         encoding = 'utf-8'                                                       │
│             file = <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'> │
│           height = 51                                                            │
│    is_alt_screen = False                                                         │
│ is_dumb_terminal = False                                                         │
│   is_interactive = True                                                          │
│       is_jupyter = False                                                         │
│      is_terminal = True                                                          │
│   legacy_windows = False                                                         │
│         no_color = False                                                         │
│          options = ConsoleOptions(                                               │
│                        size=ConsoleDimensions(width=236, height=51),             │
│                        legacy_windows=False,                                     │
│                        min_width=1,                                              │
│                        max_width=236,                                            │
│                        is_terminal=True,                                         │
│                        encoding='utf-8',                                         │
│                        max_height=51,                                            │
│                        justify=None,                                             │
│                        overflow=None,                                            │
│                        no_wrap=False,                                            │
│                        highlight=None,                                           │
│                        markup=None,                                              │
│                        height=None                                               │
│                    )                                                             │
│            quiet = False                                                         │
│           record = False                                                         │
│         safe_box = True                                                          │
│             size = ConsoleDimensions(width=236, height=51)                       │
│        soft_wrap = False                                                         │
│           stderr = False                                                         │
│            style = None                                                          │
│         tab_size = 8                                                             │
│            width = 236                                                           │
╰──────────────────────────────────────────────────────────────────────────────────╯

python -m rich._windows
platform="Darwin"
WindowsConsoleFeatures(vt=False, truecolor=False)

pip freeze | grep rich
rich==10.11.0

**Did I help?**

I think the issue is it's trying to refresh too much and CPU is being used to update the progress bar. I removed the call to update() and the issue disappeared. Sorry for the noise

I think the issue is it's trying to refresh too much and CPU is being used to update the progress bar. I removed the call to update() and the issue disappeared.

Hi @goldstar611 (from out of nowhere). I have a similar issue, and I'd like to ask a follow-up question about your solution.
I don't really understand how it was possible to remove the call to update() in your case. I think update() needs to stay there in your script, and the solution to this issue should be something different. Otherwise the progress bar doesn't get updated without any calls to update(), does it?

I need to double check but I believe what I did was call update() every N iterations.

@goldstar611 So, you pruned some of the calls (not removed all of them completely), given that you don't need that high frequency of updates. Thanks for the info.


[AzureMonitorDistro/Exporter] Update connection string and fix VS build error

Fixes https://github.com/Azure/azure-sdk-for-net/pull/34700/files#r1125061244
Added existing project Azure.Core.TestFramework.csproj to solve Visual Studio build errors

New changes ensures that a generic string is thrown only when connection string is empty. If it is invalid, it gives appropriate messages. For example, if connection string is set to test it throws below message.
[ConnectionStringError - System.InvalidOperationException: Connection string doesn't have value for keyword 'test'.

API change check
API changes are not detected in this pull request.


APM refactoring / APMv2

Before this PR can be merged the current state of the master has to be merged in again but this is not a blocker for people to review the implementation of the parser as it is proposed in this PR.

The code in this feature branch is taken as the starting point for the creation of the pynxtools-apm plugin.
All future development, including the linting with ruff is implemented and discussed here:
www.github.com/FAIRmat-NFDI/pynxtools-apm

Information for end users:
With https://github.com/FAIRmat-NFDI/pynxtools-apm/commit/5645326895122586d24569683e5b9b26a8e47565
can be used again as a plugin to standardize atom probe via NeXus, we are currently working on documentation and integrating the plugin into NOMAD Oasis


Downwards inference doesn't push types into the ?? operator

In the following example, we should infer the type of the list literal by pushing the context type down into the branches of the ?? operator.
This causes some unnecessary strong mode warnings in the markdown package.
cc @devoncarew
void main () {
  List<String> y = null ?? [];
}

possibly related to https://github.com/dart-lang/sdk/issues/24564 ... it doesn't look like we can type check ??= at all

@leafpetersen -- I may go ahead and grab this unless you already started it :)

https://codereview.chromium.org/1575173005


Reland "Migrate package/flutter to JS static interop. (#111315)"

Relands https://github.com/flutter/flutter/commit/6906493a94337d4f96968e4ac7749a2b697bbebf
Which was reverted here: https://github.com/flutter/flutter/pull/112247#event-7444297716

@eyebrowsoffire @ditman ptal, just getting this out for review again. There won't be any code changes, I just had to fix some internal build rules.
I will ensure a green internal presubmit before landing.

test-exempt: code refactor with no semantic change


new account creation with horizon rest api

how can I create a new account in testnet with just http call to horizon rest api something like this <IP_ADDRESS>:8000/friendbot ? Doc says here to use some sdk but I wanna integrate from an enterprise app context where I can't really run js client lib sdk or other lang , it has to be a simple dynamic rest api call returning new account id and details on successful creation. Also, if mainnet requires an existing account with fund to issue another account , then how do the very first account with fund gets issued..
Some quick help greatly appreciated.

Duplicate of https://github.com/stellar/go/issues/318


FOUNDRYUI-56 remove table row height 100% -> master

fix(table): remove table row height 100%

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


training needs to shorten contig names for snap/augustus training

The train step should probably automatically shorten the contig names as it seems like even header length set to 20 that still causes a problem. Adding a test for this to arrest training or better just shrink the names as internally for training the sequence IDs are not relevant?
To reproduce the bug/problem: try to run training step on this genome with long accessions as sequence names: https://ftp.ncbi.nlm.nih.gov/genomes/all/GCA/030/734/395/GCA_030734395.1_ASM3073439v1/GCA_030734395.1_ASM3073439v1_genomic.fna.gz

This should be addressed -- it will change headers and then change them back at the end.