Specify format for fullyQualifiedName

Summary
With this PR I propose to use the common convention for fullyQualifiedName to be a dot-separated path, aligning this field value with the Open Metadata specifications.
Context
The field fullyQualifiedName occurs in many entities in the Data Product specifications and it is currently a free-form string "description". This somewhat overlaps with fields name (that is the human-readable display name) and description (that should be a long-form description). The current purpose of the field is unclear IMHO.
Proposal
In SWE, a "fully qualified name" represents a string representation that includes a path like identifier package.module.class_name, as opposed to the simple name that would be class_name.
In the Open Metadata Specifications, the field fullyQualifiedName is specified following the above convention across many entities. Here a few examples:

table: serviceName.databaseName.tableName
database: ServiceName.DatabaseName
pipeline: ServiceName.PipelineName

The Open Metadata specifications don't have the concept of Data Products, Output Ports and other entities related to the Data Mesh paradigm, but nonetheless the purpose of the field is similar.
I propose to align the field fullyQualifiedName in the Data Product specifications to follow the common convention followed by Open Metadata.
Here I report an example of the fields with the proposed convention:

dataproduct fullyQualifiedName: domain_name.dataproduct_name
outputport fullyQualifiedName: domain_name.dataproduct_name.outputport_name
workload fullyQualifiedName: domain_name.dataproduct_name.workload_name
storage_area fullyQualifiedName: domain_name.dataproduct_name.storage_area_name
observability fullyQualifiedName: domain_name.dataproduct_name.observability_name

I think this proposal is actually excellent.
I agree when it is said that "the current purpose of the field is unclear", since we are inheriting it from the OpenMetadata specification, but we are not actually using this field at all. Making it more structured and adding real value to it would make it more interesting.
We can improve this proposal by making the proposed structure something verified by the CUE file. IMHO we should keep this field optional, but we can enforce that when it is present it should be compliant with the proposed structure.

IMHO we should keep this field optional, but we can enforce that when it is present it should be compliant with the proposed structure.

I agree on this 👍

Can we move forward on this ?


fix: kernel completion serialize issue

Kernel completion serialize issue (symbol can't serialize)

maybe allow source to distinguish kernel and lsp，seems useful for cmp

done


if both teams say CAAARRR then the game will pause

Created by brendan (Brendan Prin)

Closed by eric (Eric Fields)


can not convert Resnet101-Faster-Rcnn from tensorflow to IR then to MXNET

I am not sure whether it is possible to convert Resnet101-Faster-Rcnn from tensorflow to IR then to MXNET. I can not even pass convert from Resnet101 to IR. Thank you so much
Platform (like ubuntu 16.04/win10):
ubuntu
Source framework with version (like Tensorflow 1.4.1 with GPU):
Tensorflow with GPU
Pre-trained model path (webpath or webdisk path): Path is:
https://drive.google.com/drive/folders/0B1_fAEgxdnvJeGg0LWJZZ1N2aDA
name: coco_900-1190k.tgz
Running scripts:
For second step:
python -m mmdnn.conversion.examples.tensorflow.extract_model -n resnet50 -ckpt examples/tf/res50_faster_rcnn_iter_1190000.ckpt.data-00000-of-00001
bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
2018-02-07 23:26:33.110263: W tensorflow/core/util/tensor_slice_reader.cc:95] Could not open examples/tf/res50_faster_rcnn_iter_1190000.ckpt.data-00000-of-00001: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
2018-02-07 23:26:33.111700: W tensorflow/core/util/tensor_slice_reader.cc:95] Could not open examples/tf/res50_faster_rcnn_iter_1190000.ckpt.data-00000-of-00001: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
2018-02-07 23:26:33.111733: W tensorflow/core/framework/op_kernel.cc:1192] Data loss: Unable to open table file examples/tf/res50_faster_rcnn_iter_1190000.ckpt.data-00000-of-00001: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
2018-02-07 23:26:33.111703: W tensorflow/core/util/tensor_slice_reader.cc:95] Could not open examples/tf/res50_faster_rcnn_iter_1190000.ckpt.data-00000-of-00001: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
2018-02-07 23:26:33.116709: W tensorflow/core/util/tensor_slice_reader.cc:95] Could not open examples/tf/res50_faster_rcnn_iter_1190000.ckpt.data-00000-of-00001: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
2018-02-07 23:26:33.116975: W tensorflow/core/framework/op_kernel.cc:1192] Data loss: Unable to open table file examples/tf/res50_faster_rcnn_iter_1190000.ckpt.data-00000-of-00001: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
2018-02-07 23:26:33.117285: W tensorflow/core/util/tensor_slice_reader.cc:95] Could not open examples/tf/res50_faster_rcnn_iter_1190000.ckpt.data-00000-of-00001: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
2018-02-07 23:26:33.118989: W tensorflow/core/util/tensor_slice_reader.cc:95] Could not open examples/tf/res50_faster_rcnn_iter_1190000.ckpt.data-00000-of-00001: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
2018-02-07 23:26:33.118992: W tensorflow/core/util/tensor_slice_reader.cc:95] Could not open examples/tf/res50_faster_rcnn_iter_1190000.ckpt.data-00000-of-00001: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
2018-02-07 23:26:33.119025: W tensorflow/core/framework/op_kernel.cc:1192] Data loss: Unable to open table file examples/tf/res50_faster_rcnn_iter_1190000.ckpt.data-00000-of-00001: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
2018-02-07 23:26:33.126774: W tensorflow/core/util/tensor_slice_reader.cc:95] Could not open examples/tf/res50_faster_rcnn_iter_1190000.ckpt.data-00000-of-00001: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
2018-02-07 23:26:33.126781: W tensorflow/core/util/tensor_slice_reader.cc:95] Could not open examples/tf/res50_faster_rcnn_iter_1190000.ckpt.data-00000-of-00001: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
2018-02-07 23:26:33.127091: W tensorflow/core/framework/op_kernel.cc:1192] Data loss: Unable to open table file examples/tf/res50_faster_rcnn_iter_1190000.ckpt.data-00000-of-00001: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
2018-02-07 23:26:33.128075: W tensorflow/core/util/tensor_slice_reader.cc:95] Could not open examples/tf/res50_faster_rcnn_iter_1190000.ckpt.data-00000-of-00001: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
2018-02-07 23:26:33.128339: W tensorflow/core/framework/op_kernel.cc:1192] Data loss: Unable to open table file examples/tf/res50_faster_rcnn_iter_1190000.ckpt.data-00000-of-00001: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
Traceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
"main", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/home/xuw080/tensorflow/lib/python2.7/site-packages/mmdnn/conversion/examples/tensorflow/extract_model.py", line 103, in
_main()
File "/home/xuw080/tensorflow/lib/python2.7/site-packages/mmdnn/conversion/examples/tensorflow/extract_model.py", line 86, in _main
saver.restore(sess, args.checkpoint)
File "/home/xuw080/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/training/saver.py", line 1666, in restore
{self.saver_def.filename_tensor_name: save_path})
File "/home/xuw080/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 889, in run
run_metadata_ptr)
File "/home/xuw080/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 1120, in _run
feed_dict_tensor, options, run_metadata)
File "/home/xuw080/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 1317, in _do_run
options, run_metadata)
File "/home/xuw080/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 1336, in _do_call
raise type(e)(node_def, op, message)
Caused by op u'save/RestoreV2_126', defined at:
File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
"main", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/home/xuw080/tensorflow/lib/python2.7/site-packages/mmdnn/conversion/examples/tensorflow/extract_model.py", line 103, in
_main()
File "/home/xuw080/tensorflow/lib/python2.7/site-packages/mmdnn/conversion/examples/tensorflow/extract_model.py", line 85, in _main
saver = tf.train.Saver()
File "/home/xuw080/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/training/saver.py", line 1218, in init
self.build()
File "/home/xuw080/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/training/saver.py", line 1227, in build
self._build(self._filename, build_save=True, build_restore=True)
File "/home/xuw080/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/training/saver.py", line 1263, in _build
build_save=build_save, build_restore=build_restore)
File "/home/xuw080/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/training/saver.py", line 751, in _build_internal
restore_sequentially, reshape)
File "/home/xuw080/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/training/saver.py", line 427, in _AddRestoreOps
tensors = self.restore_op(filename_tensor, saveable, preferred_shard)
File "/home/xuw080/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/training/saver.py", line 267, in restore_op
[spec.tensor.dtype])[0])
File "/home/xuw080/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/ops/gen_io_ops.py", line 1021, in restore_v2
shape_and_slices=shape_and_slices, dtypes=dtypes, name=name)
File "/home/xuw080/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/framework/op_def_library.py", line 787, in _apply_op_helper
op_def=op_def)
File "/home/xuw080/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 2956, in create_op
op_def=op_def)
File "/home/xuw080/tensorflow/local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 1470, in init
self._traceback = self._graph._extract_stack()  # pylint: disable=protected-access
DataLossError (see above for traceback): Unable to open table file examples/tf/res50_faster_rcnn_iter_1190000.ckpt.data-00000-of-00001: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
[[Node: save/RestoreV2_126 = RestoreV2[dtypes=[DT_FLOAT], _device="/job:localhost/replica:0/task:0/device:CPU:0"](_arg_save/Const_0_0, save/RestoreV2_126/tensor_names, save/RestoreV2_126/shape_and_slices)]]
[[Node: save/RestoreV2_263/_37 = _Recvclient_terminated=false, recv_device="/job:localhost/replica:0/task:0/device:GPU:0", send_device="/job:localhost/replica:0/task:0/device:CPU:0", send_device_incarnation=1, tensor_name="edge_584_save/RestoreV2_263", tensor_type=DT_FLOAT, _device="/job:localhost/replica:0/task:0/device:GPU:0"]]

Hi @xuw080 ,

the resnet-50 extractor is only for slim-resnet50 model.

object detection models are not supported yet. We are working on SSD models and will release it in few weeks.

Thanks.

Any example to convert if we have some custom layers? It seems that it's better to provide a tutorial to modify MMdnn if the layer is not supported by default.

Hi @twmht ,here is Contribution-Guideline , a tutorial to modify MMdnn. We will provide a tutorial for models with some custom layers(class) later.


Can you place the Extension Installation instructions inline?

Here you tell us to register: https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-cosmosdb-v2#packages---functions-2x
Which links off to the following page with the instructions. Why not just place them inline?
https://docs.microsoft.com/en-us/azure/azure-functions/functions-triggers-bindings#local-development-azure-functions-core-tools

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

ID: fa5bcb79-2af8-3b0e-c78c-0c89a2535e15
Version Independent ID: 31b87687-7841-f46f-8c97-38898e7b97db
Content: Azure Cosmos DB bindings for Functions 2.x (Preview)
Content Source: articles/azure-functions/functions-bindings-cosmosdb-v2.md
Service: functions; cosmos-db
GitHub Login: @ggailey777
Microsoft Alias: glenga

@timmyreilly Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

In the same vain, I'm trying to use the DocumentClient, how do I install the proper package/extensions?
I get this error:
The type or namespace name 'DocumentClient' could not be found (are you missing a using directive or an assembly reference?)

@Mike-Ubezzi-MSFT please assign to @craigshoemaker whonow owns this article. Thanks!

@timmyreilly to answer your original question, we can really put the extension installation instructions inline because they differ depending on the development environment (portal/Visual Studio/Core Tools, etc..).
The DocumentClient is installed with the Cosmos DB binding extension (I think it's part of the Microsoft.Azure.DocumentDb.Core package), but you have to add the following using statement in C#:
using Microsoft.Azure.Documents.Client;

Thanks for the feedback, @timmyreilly. I have created an internal work item to address this issue. Please let me know if you see anything else that needs attention.
#please-close


Undo History Messed Up When Obsidian App Open

🐛 Describe the bug
Open a file with, eg, :ObsidianNew. Open that file in obsidian with, eg, :ObsidianOpen. Type some text (like with GoHello). Save the file with :up. Change the text (like with GciwBye). Save again: :up. Undo with U and notice that the cursor is positioned at the top of the document but that the document is the same and did not undo the last change. If you do u once more, then it actually undoes the change.
It seems like if you have obsidian open, then every time you :write (or :update) the file, obsidian replaces the entire file with the same text. Even if I do :set noautoread, somehow the undo history is messed up. I don't even see it in :undolist, so I'm not sure exactly what is happening.
Please help. I keep trying to do incremental changes with the obsidian graphviz community plugin (yes, I disabled and removed it completely to verify that this is not the cause), and every time I write the file, I can't undo easily because it keeps making my cursor jump to the top of the file and I have to undo a lot on top of it truncating my undo history (can't redo with CtrlR. It's really annoying and completely unusable as is for what I am trying to do.
I'm on linux btw.
Versions
NVIM v0.10.0-dev-1722+g884a83049b
Build type: RelWithDebInfo
LuaJIT 2.1.1702233742
obsidian.nvim (v2.6.0)] Commit SHA: 86caccdac82e78a268e25fab901f47bc36ccd33c
[plenary.nvim] Commit SHA: 55d9fe89e33efd26f532ef20223e5f9430c8b0c0
ripgrep 14.1.0

I think :undojoin might be able to solve this problem

On Mac it seems to work as expected. Is this still an issue? Either way, I don't think this a bug with obsidian.nvim.


[$250]  Search - Report does not show error when payment failure happens in Search

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.76-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause Internal Team
Device used: Mac 15.0 / Chrome
App Component: Search
Action Performed:

Go to staging.new.expensify.com
[User A] Open chat with User B.
[User A] Submit two expenses to User B.
[User B] Open report with User A.
As User A, delete one of the expenses and User B quickly pays the group expenses (quickly before the deleted expense is removed for User B).
Note that User B receives an error because User B pays an expense that is no longer available.
[User A] Submit one more expense to User B so there are two expenses.
[User B] Go to Search > Expenses > Outstanding.
Repeat Step 5 but this time User B quickly pays in Search.
[User B] Click on the Review button with RBR.

Expected Result:
When User B clicks on the Review button in Search, expense RHP will show error for payment failure (so that it is consistent when the payment failure happens in Inbox - Step 6).
Actual Result:
When User B clicks on the Review button in Search, expense RHP does not show error for payment failure, which is not consistent with the same steps performed in Inbox (Step 6).
Workaround:
Unknown
Platforms:

[x] Android: Standalone
[x] Android: HybridApp
[x] Android: mWeb Chrome
[x] iOS: Standalone
[x] iOS: HybridApp
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/4c1b501d-1d1a-4342-ad2d-50be58622c6e
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021868705876872827221
Upwork Job ID:<PHONE_NUMBER>872827221
Last Price Increase: 2024-12-30

Issue OwnerCurrent Issue Owner: @ntdiary

Proposal
Please re-state the problem that we are trying to solve in this issue.
Search - Report does not show error when payment failure happens in Search
What is the root cause of that problem?
In the payMoneyRequestOnSearch and approveMoneyRequestOnSearch functions, the finallyData erases the error message in response from the backend.
https://github.com/Expensify/App/blob/01c0ad96d604e8ee914c5de06c9ef518d233588b/src/libs/actions/Search.ts#L321-L329

What changes do you think we should make in order to solve the problem?

In payMoneyRequestOnSearch and approveMoneyRequestOnSearch replace finallyData with successData so the error message from the response gets merge into the onyx.
https://github.com/Expensify/App/blob/01c0ad96d604e8ee914c5de06c9ef518d233588b/src/libs/actions/Search.ts#L321-L323
const optimisticData: OnyxUpdate[] = createOnyxData({isActionLoading: true});
const failureData: OnyxUpdate[] = createOnyxData({isActionLoading: false, hasError: true});
const successData: OnyxUpdate[] = createOnyxData({isActionLoading: false});

Finally, we can handle dismissing the error message for ReportListItem as well if needed.

Hey @ntdiary, I believe this issue would be best solved in BE and needs an FE fix to dismiss the error.
After re-investigating the snapshots, it seems that immediately after /api/PayMoneyRequestOnSearch is requested, /api/Search is requested and then the response sets a different snapshot without the report errors.
Since the separate snapshots don't have report errors, the item.errors will be empty because they are loaded from another report's search data in the latest snapshot.

However, we could also set the error in the FE but I believe the BE should return the errors in the next snapshot when the report's transactions change.
So, let's fix the BE first, and then we can check if an FE fix is needed to dismiss the errors.
WDYT?

@Tony-MK, I guess your Search request was triggered by a network reconnect, and having the backend returning that error might not be ideal since it’s not persistent, It seems normal to disappear the error when the user search again

@ntdiary, It seems you are right about this.

However, there’s something else that’s quite strange: my screenshot still shows Pay instead of Review, and I haven’t been able to figure out why:

I think found the cause of the issue.
There is confusion between this line which expects hasError and the response returns hasErrors.

https://github.com/Expensify/App/blob/483d28729c6f81b6c59fd87a7fc2ed5bff04f81e/src/libs/SearchUIUtils.ts#L267
I believe the fix should look like this.

WDYT?


Issue

https://github.com/TheThingsNetwork/arduino-node-lib/blob/f28ef321af1bae0715c374099a47335a25f4d19d/examples/Basic/Basic.ino#L56

What is the issue?


Bugfix/delint MIM parser

Description
Fixes bugs observed (so far) in MIMParser during the xref sprint, add additional checks, and delint the code to facilitate further refactoring. See ENSCORESW-2880.
Use case
Part of the efforts to improve the xref pipeline.
Benefits
Multi-line descriptions no longer end up with words adjacent to line breaks erronenously concatenated. Improved performance thanks to reduced amount of redundant text processing. Partly generalised xref-insertion code. Some future-proofing. Code (hopefully) easier to maintain. PerlCritic at level 3 complains only about still rather high complexity of run() and the only additional complaints introduced by level 2 are missing certain POD sections and $VERSION.
Possible Drawbacks
None I can think of.
Testing
Have you added/modified unit tests to test the changes?
No.
If so, do the tests pass/fail?
N/A
Have you run the entire test suite and no regression was detected?
N/A. However, I have run the parser itself on current MIM data set and it appears to work correctly.

Coverage remained the same at 81.127% when pulling 189f7abb37d86ec54c322acd4f333c58cd894607 on bugfix/delint_MIMParser into fb849f5a081df4e1d1eb5d5fbbba8de0eeb416e8 on feature/xref_sprint.

@nerdstrike are you happy with the updates?


Add loop.create_future() and start using it

This PR adds a new API -- loop.create_future() (see discussion in #282 for details).

We don't want this committed before 3.5.1, right?

No, let's hold off on this one for a little bit.

@1st1: Python 3.5.1 has been out for a while now. You can safely merge this!

Hi Guido!
Sorry for the delayed reply, I was away from the office.
Before merging this PR, I'd like to reiterate on a few things:

I'm working on an implementation of Future class in C.  I'll create an issue on CPython bug tracker soon, and it would be great if we can ship 3.5.2 with it (would you be OK with that?).

If we have a fast Future, then adding just loop.create_future won't directly help projects like uvloop (since there are a lot of places with code like if isinstance(fut, asyncio.Future): ...).

So this PR is mainly for streamlining creation of Futures for asyncio users.  Since the loop parameter in Future constructor is optional, it is often omitted.  loop.create_future is a less ambiguous API, and it mirrors loop.create_task.

With all that in mind, are you still OK with merging this PR?

I forgot -- do you want this PR in 3.5.2 or the C-accelerated Future class?
Why wouldn't uvloop's Future class be able to inherit from the default Future class (accelerated or not)?
For most people leaving out the loop= parameter doesn't matter because there's only one loop they care about (or at least they're doing the Future instantiation when the right loop is current -- either way it doesn't matter).
I've noticed that create_task() has caused some confusion (see the recent issue #306 demanding that certain functions that currently return a Future be changed to be actual coroutines so they could be passed to create_task()). I worry that create_future() will cause more confusion (as yet unknown -- I hadn't anticipated the create_task() confusion either).
Anyway, do you really need this?

I forgot -- do you want this PR in 3.5.2 or the C-accelerated Future class?

The latter.  If we have a fast Future implementation, we don't need loop.create_future just to further improve the performance.  Sorry for the confusion.
We might need create_future to make Futures creation a little less error prone.  You're right -- most users use only one event loop per process, but when users develop reusable libraries, they should pass the loop explicitly in their code.  create_future would plug this specific hole.  [1]
Another interesting benefit of create_future is that it'd allow one to instrument their code, say collect stats on how many Futures were created/cancelled/errored, how many callbacks were added/deleted.  [2]

Anyway, do you really need this?

If you don't see enough benefits in having [1] and [2], then I propose to close this PR and focus on adding a C implementation of Future in CPython.

I've noticed that create_task() has caused some confusion (see the recent issue #306 demanding that certain functions that currently return a Future be changed to be actual coroutines so they could be passed to create_task()).

Oh, that's no good :(  TBH, I always worried that we treat Futures and coroutines as they are interchangeable (in docs).  Futures have add_done_callback(), cancel() etc, and some users will write code like loop.run_in_executable(...).add_done_callback(...).  Maybe we should wrap asyncio functions that are documented as coroutines in actual coroutines?

On Fri, Jan 8, 2016 at 1:06 PM, Yury Selivanov<EMAIL_ADDRESS>wrote:

I forgot -- do you want this PR in 3.5.2 or the C-accelerated Future class?
The latter. If we have a fast Future implementation, we don't need
loop.create_future just to further improve the performance. Sorry for
the confusion.

Honestly I'm skeptical about adding an accelerated Future class. That feels
like a risky thing to do in a bugfix release (even granting that asyncio is
still  provisional).

We might need create_future to make Futures creation a little less error
prone. You're right -- most users use only one event loop per process, but
when users develop reusable libraries, they should pass the loop explicitly
in their code. create_future would plug this specific hole. [1]

Yeah, but they'll still have to change their code. It's not any easier to
rewrite every call to Future() to read loop.create_future() instead, and if
you're just going to call get_current_event_loop() it doesn't help at all
(since that's the default anyway).
So I don't believe this helps.

Another interesting benefit of create_future is that it'd allow one to
instrument their code, say collect stats on how many Futures were
created/cancelled/errored, how many callbacks were added/deleted. [2]

And why couldn't you instrument Future.init directly? (Maybe using
mock.)

Anyway, do you really need this?
If you don't see enough benefits in having [1] and [2], then I propose to
close this PR and focus on adding a C implementation of Future in CPython.

Let's close this PR. But I'm not so sure about the latter.

I've noticed that create_task() has caused some confusion (see the recent
issue #306 https://github.com/python/asyncio/pull/306 demanding that
certain functions that currently return a Future be changed to be actual
coroutines so they could be passed to create_task()).
Oh, that's no good :( TBH, I always worried that we treat Futures and
coroutines as they are interchangeable (in docs). Futures have
add_done_callback(), cancel() etc, and some users will write code like
loop.run_in_executable(...).add_done_callback(...). Maybe we should wrap
asyncio functions that are documented as coroutines in actual
coroutines?

No we should fix the docs.
--
--Guido van Rossum (python.org/~guido)

Hi Guido,
I continue to experiment with uvloop and create_future. I have an experimental branch of uvloop with create_future and a Future implemented in Cython.
The streams echo server benchmark becomes 25% faster, if I replace 'StreamReader._waiterwith a fast uvloop Future implementation.  My implementation is a subclass ofasyncio.Future`, so everything in asyncio supports it without any problem.
Future is the only core primitive in asyncio that I can't improve in uvloop. Even for tasks we have a create_task method.
Could you please re-consider merging this PR?

Did a quick futures benchmark here, the result is that uvloop's Futures are 1.8-2x faster.
Benchmarks for sock_recv/sock_sendall are >70% faster.
Benchmarks for asyncio streams are 25-30% faster.
I also think that loop.create_future() is a better API than asyncio.Future(loop=loop).

I am completely overwhelmed with stuff, can it wait a few days?

Absolutely. I only want this to make it to 3.5.2 if possible.

I don't think new APIs or new features are in scope of 3.5.2, my guess is this will have to wait for 3.6...

Actually they are, asyncio is still provisional in 3.5.

Actually they are, asyncio is still provisional in 3.5.

Yes, pretty please... There are some significant performance improvements here.

This PR is out of date, and I'm a little confused. But I think we should go ahead with something. Here are some questions and observations.
This PR seems to do a few things:

Add metaclass=ABCMeta to Future (why?)
Add create_future() (and a test for it)
Use create_future() everywhere

So the last two bullets feel uncontroversial, but I'm curious about the addition of ABCMeta. (In mypy, we found that this significantly slows down some things.)
Also, in some previous comment you seemed to be claiming that you didn't (or at least might not) need create_future() after all, and in some other comment you seemed to be indicating that you really want an accelerated Future implementation in CPython. So which is it? Can you lay everything clearly on the table please? (We could open a new issue or use the python-tulip list, but we might as well continue the discussion here, unless you think you'd like to start a fresh PR.)

Thanks for reviewing!

Add metaclass=ABCMeta to Future (why?)

Having an ABC for Futures was something I wanted to do in the beginning, but now we don't need that. I'll update the PR. And yes, adding an ABCMeta will make isinstance calls significantly slower, this is something we cannot even consider.

Also, in some previous comment you seemed to be claiming that you didn't (or at least might not) need create_future() after all, and in some other comment you seemed to be indicating that you really want an accelerated Future implementation in CPython. So which is it?

Yes, I created an issue (http://bugs.python.org/issue26081) to re-implement the asyncio.Future in C.  At that time I believed that it's something we can do relatively fast.  However, we can only merge that in 3.6, it still requires a lot of work, and because of a few limitations of CPython C API and a very complex code dependancy graph the code looks very ugly. I'm honestly not sure if I will have time to finish that work, and there are somewhat more important things I wanted to do in 3.6.
OTOH, I tried to re-implement Future in Cython, and saw the same speedups as with my C Future from issue 26081.  The performance benefits are very significant, and this is something I'd like people to start using asap.
I think that create_future is a nice solution, as it allows uvloop to speed-up things that are out of its control, for instance asyncio.streams. I was very surprised when I discovered that using an accelerated future for waiters in streams improves the performance by 25%.

What if some library or app mixes calling create_future() and instantiating
Future directly?
Also what about code that calls isinstance(x, Future)?
On Sunday, May 15, 2016, Yury Selivanov<EMAIL_ADDRESS>wrote:

Thanks for reviewing!
Add metaclass=ABCMeta to Future (why?)
Having an ABC for Futures was something I wanted to do in the beginning,
but now we don't need that. I'll update the PR. And yes, adding an ABCMeta
will make isinstance calls significantly slower, this is something we
cannot even consider.
Also, in some previous comment you seemed to be claiming that you didn't
(or at least might not) need create_future() after all, and in some other
comment you seemed to be indicating that you really want an accelerated
Future implementation in CPython. So which is it?
Yes, I created an issue (http://bugs.python.org/issue26081) to
re-implement the asyncio.Future in C. At that time I believed that it's
something we can do relatively fast. However, we can only merge that in
3.6, it still requires a lot of work, and because of a few limitations of
CPython C API and a very complex code dependancy graph the code looks very
ugly. I'm honestly not sure if I will have time to finish that work, and
there are somewhat more important things I wanted to do in 3.6.
OTOH, I tried to re-implement Future in Cython, and saw the same speedups
as with my C Future from issue 26081. The performance benefits are very
significant, and this is something I'd like people to start using asap.
I think that create_future is a nice solution, as it allows uvloop to
speed-up things that are out of its control, for instance asyncio.streams.
I was very surprised when I discovered that using an accelerated future for
waiters in streams improves the performance by 25%.
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/python/asyncio/pull/290#issuecomment-219345934

--
--Guido (mobile)

What if some library or app mixes calling create_future() and instantiating
Future directly?

That's totally fine. uvloop will recognize any Future that extends asyncio.Future. And uvloop.Future will work just fine with vanilla asyncio.

Also what about code that calls isinstance(x, Future)?

Here's some pseudocode illustrating how it's implemented in uvloop:
cdef class BaseFuture:
    """Optimized & statically typed Future implementation"""

class Future(BaseFuture, asyncio.Future):
    pass

Because uvloop.Future is inherited from asyncio.Future it works fine with isinstance checks, and since BaseFuture is the first parent it's faster.

Awesome. Let me know when the updated PR is ready!
(Also, super thanks for all the PR merging and other stuff you've done
recently to asyncio. As you might have guessed I'm totally consumed by
typing stuff and I rarely have time to dive deep enough into asyncio. So
you and Victor are basically it! Rest assured I am still watching the
stream of notifications and will jump in when I see anything fishy
happening. 3.5.2 will be a great release!)

Awesome. Let me know when the updated PR is ready!

It should be ready now.  I can merge it myself if you don't have time.

Also, super thanks for all the PR merging and other stuff you've done
recently to asyncio. As you might have guessed I'm totally consumed by
typing stuff and I rarely have time to dive deep enough into asyncio.

NP!  I can't wait to hear your typing talk on PyCon!  And I have a few
ideas to discuss too ;)

(I'm not sure why github shows that the branch is out of date -- I've just rebased it on top of the master branch.  Anyways, we can merge manually)

LGTM. Can you manually merge this? The GitHub warning feels scary, maybe it's because the branch is so old? Also you should probably make sure no new Future() calls have appeared since you wrote this.

Also you should probably make sure no new Future() calls have appeared since you wrote this.

Yep, I did that ;) -- Indeed we had a new one, where we parse ip addresses.
Thanks a lot, Guido, I'll merge it now.

Merged. Thanks again!

Good luck! Remember to update the docs.


mqtt/mqtts is not recognized as valid AppRise URL

Describe the bug
When entereing an mqtt/mqtts URLs as a Notification URL it is not saved wit the error that it would not be an valid AppRise URL, even if  it is.
Version
v0.45.16
To Reproduce

Go to 'Settings'
Click on 'Notifications'
Enter an URL starting with 'mqtt://' or 'mqtts://'
See error 'mqtts://...' is not a valid AppRise URL.

Expected behavior
The JSON set as the Notification Body should be sent to the mqtt broker.

Looks like a bug in apprise?
$ ls|apprise  mqtt://home-server/nice-topic
Exception ignored in: <function Client.__del__ at 0x7f8dc2cc0310>
Traceback (most recent call last):
  File "/home/dgtlmoon/.local/lib/python3.10/site-packages/paho/mqtt/client.py", line 874, in __del__
    self._reset_sockets()
  File "/home/dgtlmoon/.local/lib/python3.10/site-packages/paho/mqtt/client.py", line 1133, in _reset_sockets
    self._sock_close()
  File "/home/dgtlmoon/.local/lib/python3.10/site-packages/paho/mqtt/client.py", line 1119, in _sock_close
    if not self._sock:
AttributeError: 'Client' object has no attribute '_sock'
2024-03-09 12:38:53,340 - ERROR - Could not load MQTT Notification URL: mqtt://home-server/nice-topic
2024-03-09 12:38:53,340 - ERROR - There are no service(s) to notify

@Red96Baron please try to send a mqtt:// from the command line (pip install apprise)
if it persists, please open in caronc/apprise repo
thanks for the report

@dgtlmoon thanks for the fast reply!
Please refere to caronc's answer from the apprise issue:

This is related to the version of mqtt being installed under the hood. The new version was released (v2.0) and not backwards compatible with its previous. See here.

Your Change detection instance just needs to include the previous version of paho-mqtt and it will work fine.

Just released .17 :)


adjust entrypoint script in a way, what it will not fail while starting existing, but stopped container

Hi @tony2001 and @anton-povarov.
While adding pinba to development environment made by docker-compose, I noticed that pinba start successfully only for the first time, and when container was stopped and then started again - it fails.
I realised, that installation commands are written to be executed only once.
Here is my proposal how to fix this.

LGTM, @Sannis could you take a look please


The size of Select does not affect the size of SelectItem

🐛 Bug Report
To Reproduce
select doc

Expected behavior
The size of Select should directly affect the size of its sub-components, that is, SelectItem, so that it will appear more coordinated
Link to runnable example or repository (highly encouraged)
select doc, see the part of "size"
UI Kitten and Eva version

Package
Version

@eva-design/eva
latest

@ui-kitten/components
latest

Should it be changed to enhancement? I don’t know, but it’s not very coordinated, especially on small cellphones.

Agree. Even I set the size of the <Select size='small' />, the <SelectItem /> dropdown listing is still on default size.


⚠ Samsung has degraded performance

In bf407ad, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2647 ms

Resolved: Samsung performance has improved in 9353be4.


Release version 0.3.0

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (822bf5e) to head (5e33a03).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #245   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            7         7
  Lines          219       219
  Branches        14        14
=========================================
  Hits           219       219

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Customize default --help message

Original issue 32 created by schuhschuh on 2010-01-07T16:01:10.000Z:
Hi all,
is there any way of improving/customizing the regular --help message? The
default --help shows the help message for all flags, including the gflags
flags, and plus, it separates the flags for modules, as in the example below:
Flags from /home/user/Main.cpp:
-a (some description) type:...
-f ....
So, if i'm using only one module is look strange..
Is there any way of making help printing only my flags independent from
which modules the flags are? And plus, the usage message comes before the
help message.. is there any way of making it to come after?
I couldn't find anything  to help on those issues looking at gflags.h and
in the gflags help...
thanks...
Pablo

Related to #72. Will implement new help output formatting features as part of next major release.

Workaround for anyone stumbling across this issue:
// Before main()
DEFINE_bool(h, false, "Show help");
// In main()
gflags::ParseCommandLineNonHelpFlags(&argc, &argv, true);
if (FLAGS_help || FLAGS_h) {
FLAGS_help = false;
FLAGS_helpshort = true;
}
gflags::HandleCommandLineHelpFlags();
The code is such that it does the right thing.
You can also customize the output by setting --helpmatch.

Workaround for anyone stumbling across this issue:
// Before main()
DEFINE_bool(h, false, "Show help");
// In main()
gflags::ParseCommandLineNonHelpFlags(&argc, &argv, true);
if (FLAGS_help || FLAGS_h) {
FLAGS_help = false;
FLAGS_helpshort = true;
}
gflags::HandleCommandLineHelpFlags();
The code is such that it does the right thing.
You can also customize the output by setting --helpmatch.

thanks a lot.
the 'ParseCommandLineNonHelpFlags' and 'HandleCommandLineHelpFlags' is the way to control help message, from here

@gritzko
Perhaps you mean:
DECLARE_bool(help);
DECLARE_bool(helpshort);

Yes. On --help current output is total mess.
By default on --help should show what --helpshort shows now. And --helpshort should be deprecated.


Cannot fullscreen video in external iframe on iOS

My Vimeo embeds work with BigScreen on my desktop, but not on iOS.
It looks like it fails during BigScreen.videoEnabled($('iframe)[0]). Is there a way to bypass this?
FYI: Vimeo support states that their API does not integrate with native JS fullscreen.

BigScreen needs to be able to have access to the <video> on iOS, which is not possible to do with an <iframe> from a different origin.


Swiping on info panel doesn't work correctly on iOS

On iOS 12, swiping up or down on the info panel scrolls the whole page, making it difficult to drag. See the attached example:
qwant_maps_bug.MP4.zip

Hi!
Thanks for the detailed report and sorry for the late reply. I wasn't able to reproduce the issue with Safari, the bug may be fixed on more recent versions of erdapfel.
Don't hesitate to reopen the issue if the problem persists on your side.


Type of change

[x] Other (please describe): Linting

Browser conformance:

[x] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

/retest


Improve migration docs

The existing v11 -> v12 migration documentation is missing some necessary information.
The net effect is that, if one follows the documented migration process as-is, it doesn't work.

step 2 needs to pack before it can publish
the migration tool doesn't adjust the orb-publish build instructions within config.yml and test-deploy.yml so this needs to be documented instead
step2 parameters were wrong (see also #216 which also contains a fix for this)

This PR fixes that.
... and also makes this orb's test-deploy (step2) build "practise what it preaches" by avoiding the dev-publish step for forked-PR builds (as they should fail to get a context).

A little late here but if you are willing to rebase, we have got the examples update so we can safely remove them from this PR. Thanks for the help!

I've rebased the PR as requested.
Note: You can safely enable the CircleCI -> Project settings -> Advanced "Build forked PRs" flag for this PR ... and once this is merged, you can safely leave it enabled because this PR turns off the dev-publish job (which requires a context) for forked PRs.
i.e. once this is "in" you can let CircleCI do the builds that GitHub has been told to insist upon.
(and if you update other orbs' test-deploy.yml files to follow this pattern, you can then enable forked-PR builds for those too, which will really help non-CircleCI folks contribute usefully to the orb code and generally make your job a little easier 😉)
PS. ensure that the "Pass secrets to builds from forked pull requests" flag is OFF (it defaults to "on"). That setting should never be "on" for a publicly-visible repo.

Highly appreciate the help. Unfortunately it was not (only) the publish job that forces us to disable forked builds. We may still experiment with turning it back on, but the original reason was due to crypto miners. We used to get a LOT of spam PRs that totally changed the config to mine crypto. We actually have a config policy feature that I haven't yet to dove too deeply into which can probably help too.

Crypto miners? Wow - that's "unsociable" ... but I guess it's not entirely unexpected; any loophole will be exploited if it can be.
I've been told that OPA config policies are "the CircleCI answer" to all of those security concerns ... although I've personally found that OPA syntax rather difficult; if you do find an answer then please do share because we want to have some of our own CircleCI builds be public and forkable too...

OK, understood.
I'll split things up ... although y'all have to merge "both together" or "neither" in order to avoid inconsistencies. As is, this PR keeps everything nice and consistent, ensuring that the orb itself builds using code that's really similar to the example code.
(Sorry for the delay in responding; had an end-of-year work-rush, followed by xmas break. I'll get on with this as soon as I've cleared the holiday backlog)

I've split this PR up. See #229 and #230.

This one (#220) just updates the migration documentation ... although the new documentation does point people at the example & build code from this orb which are updated in #229 and #230.
#229 updates the example.
#230 updates this orb's build code so that it builds the way it's telling everyone else to do it.


(eval) incorporate SimpleBench

What problem or use case are you trying to solve?
Add SimpleBench to eval suite.

Ah, my bad, this isn't for agentic benches, nvm.


Test related to authentication with x.509 certificates.

Description
[Describe what this change achieves]

Category (Integration tests)
Why these changes are required?
What is the old behavior before changes and new behavior after changes?

Issues Resolved
[List any issues this PR will resolve]
Integration tests related to user authentication with X.509 certificates.
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #2227 (de3f33f) into main (a57fd0a) will decrease coverage by 0.07%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #2227      +/-   ##
============================================
- Coverage     61.05%   60.97%   -0.08%
+ Complexity     3270     3263       -7
============================================
  Files           259      259
  Lines         18335    18335
  Branches       3248     3248
============================================
- Hits          11194    11180      -14
- Misses         5555     5565      +10
- Partials       1586     1590       +4

Impacted Files
Coverage Δ

...urity/ssl/transport/SecuritySSLNettyTransport.java
62.36% <0.00%> (-4.31%)
:arrow_down:

...earch/security/ssl/util/SSLConnectionTestUtil.java
93.18% <0.00%> (-2.28%)
:arrow_down:

...ecurity/configuration/ConfigurationRepository.java
72.13% <0.00%> (-2.19%)
:arrow_down:

.../dlic/auth/ldap2/LDAPConnectionFactoryFactory.java
57.46% <0.00%> (-1.50%)
:arrow_down:

...iance/ComplianceIndexingOperationListenerImpl.java
61.76% <0.00%> (-1.48%)
:arrow_down:

...search/security/transport/SecurityInterceptor.java
75.38% <0.00%> (-0.77%)
:arrow_down:

.../org/opensearch/security/support/ConfigHelper.java
86.00% <0.00%> (ø)

...ensearch/security/ssl/DefaultSecurityKeyStore.java
67.83% <0.00%> (ø)

...dlic/auth/http/saml/AuthTokenProcessorHandler.java
47.28% <0.00%> (ø)

...ty/configuration/ConfigurationLoaderSecurity7.java
70.43% <0.00%> (ø)

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

Bwc tests are broken on main. Tracking issue here: https://github.com/opensearch-project/security/issues/2221


Password prompt re-appears on language selector

Recently I am facing a strange issue with the new build. When the system boots I get the language selection screen every time and after selecting the preferred language I am asked to enter the password and after entering the password correctly also I get the same prompt again and again.

Is this on the Live system or on the installed system?

Installed system
On Mon, 31 Jul 2023, 12:36 probonopd, @.***> wrote:

Is this on the Live system or on the installed system?
—
Reply to this email directly, view it on GitHub
https://github.com/helloSystem/ISO/issues/502#issuecomment-1657788625,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGAHHHWRV5CGFGIQJ3YJNELXS5KOBANCNFSM6AAAAAA25WB7YE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yes I set a password while installing the system. And the password is
working after the system is loaded.
My system supports UEFI boot and the system boots in UEFI mode.
On Mon, 31 Jul 2023, 18:13 probonopd, @.***> wrote:

Please answer all questions:

When installing the system, did you set a password?
Does your system support UEFI and is running in UEFI (not CSM) mode?

Thanks.
—
Reply to this email directly, view it on GitHub
https://github.com/helloSystem/ISO/issues/502#issuecomment-1658302442,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGAHHHWEDKI27NKVNYG5QRTXS6R53ANCNFSM6AAAAAA25WB7YE
.
You are receiving this because you authored the thread.Message ID:
@.***>

I have reinstalled the system now works perfectly. But I didn't understand
why the system didn't recognise the UEFI boot and was always asking for
language selection at login when I installed it last time.
On Mon, 31 Jul 2023, 19:58 probonopd, @.***> wrote:

Thanks. Do you think you can look into the Python code and try to identify
what causes the issue?
—
Reply to this email directly, view it on GitHub
https://github.com/helloSystem/ISO/issues/502#issuecomment-1658481022,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGAHHHTQZIQQJA6CHADIGPLXS66HVANCNFSM6AAAAAA25WB7YE
.
You are receiving this because you authored the thread.Message ID:
@.***>


Add checkbox column

Introduces a checkbox column to unsbuscribe/subscribe from projects directly

[x] Introduce checkbox factory (#161)
[x] Add the column to the grid (#163)
[x] Remove the old checkbox (#165)

Hi @KochTobi I am a little confused by your feedback. You already reviewed the factory in #161 and now you request changes for it which you already approved. In general I am not against improving it but it also doesnt make sense to me since a factory should not keep information, it only creates content. I am happy to quickly meet and resolve this, if required.

Hi @KochTobi I am a little confused by your feedback. You already reviewed the factory in #161 and now you request changes for it which you already approved.

Yes because at that time there was no map anywhere. This only makes sense after the different parts are being fused together which this PR does.

In general I am not against improving it but it also doesnt make sense to me since a factory should not keep information, it only creates content. I am happy to quickly meet and resolve this, if required.

The factory pattern is not that strict. After all it is only a pattern. However, it is good practice to hide as much detail as possible. Where the objects come from is a detail from my point of view.

LGTM


Deepstream-app with YOLOv4 ONNX model + BatchedNMSPlugin

Hi,
I successfully created engine file from yolov4 + BatchedNMSPlugin according these instructions in this repository. The engine file works fine (I can successfully run ../bin/yolov4 --demo command ).
Now I want to deploy this engine file to deepstream-app. To do that, I need a parse function for config_infer_primary.txt file. The default parse function for yolov4 is here in this repository including the NMS. But I do not need NMS in the post processing time because the BatchedNMSPlugin is part of the engine file so the NMS is already done and the output should contain only the final bboxes.
I tried to rewrite the parse function for yolov4 for my case, but with no success.
Is there any example of parse function for yolov4 + BatchedNMSPlugin? If not, where should I start? Is there any information how to write own parse function for engine files?

Ok, I found example in:
/opt/nvidia/deepstream/deepstream-5.1/sources/libs/nvdsinfer_customparser


Python: Run Selection/Line in Python REPL (or Terminal)

Neither of the above keybinds do anything. At all. Please fix this non-functionality.
-- TO REPRODUCE --

Look at the above listed keyboard shortcuts
Open up a Python REPL in the terminal
Observe the keyboard shortcuts above do nothing.

@peekxc Thank you for filing the issue.
What is the version of Python extension that you are running?
Does opening a command palette (control/cmd + shift + p) and pressing on 'Python Clear Cache and Reload' do anything?

Can confirm that reloading did not help.
Here's a short video showing the non-functionality of the above shortcuts:

@peekxc Thanks for the video demonstration of this. I'm trying to think of why this is happening - It may be because you have the interactive window tab opened on the bottom there? Can you try closing that interactive tab and shift+enter from the Python file?(Make it so that the Python file is the only thing you have open and then try shift+enter to trigger sending to Terminal REPL or native REPL depending on your setting). Let me know how this work out - Thanks

@anthonykim1 Can confirm this did not help.
Though, even if I keep the interactive window open, I would still classify this as a bug---the shortcut should just work regardless.
Now that you mention it, I was able to get this working by just removing all the extraneous 'When' conditions other than config.python.REPL.sendToNativeREPL

What you have open ('interactive-1') is called Interactive Window coming from the Jupyter Extension.
Only Native REPL(You won't have to install Jupyter or ipykernel for this), Terminal REPL belongs to the Python Extension.
You will know when you are in Native REPL when the kernel in the right hand corner says "Python REPL"

the shortcut should just work regardless.
Python Native REPL is not meant to send command from your Python file to Interactive Window

I cannot repro this:
https://github.com/user-attachments/assets/fb4ba398-ca4b-4920-bd1c-239c807605ac
Please note the first tab in the right hand editor section is interactive window(not sure why its named Python REPL instead of interactive-1, but if you see the kernel section you can see it is ..(venv)..etc and NOT Python REPL)
@peekxc Do you have the setting below checked or no?
Is there a chance setting
  could be related? /cc @amunger

I have two windows open, actually, an interactive window (via jupyter) and a regular terminal.
The command should send inputs to the bottom one.

Neither of the above keybinds do anything.

Can you run the command "Toggle keyboard shortcuts troubleshooting" and post the logs from that after trying to use the key binding.
The output panel for either 'python', 'jupyter' or 'window' would likely have an error if the expected command is being run.


TypeError: Object of type Client is not JSON serializable. Using Cohere LLM

When trying to save the route configuration to a file using the to_file method in the Layer class, a TypeError is raised with the message "Object of type Client is not JSON serializable".
Steps to reproduce the behavior:
functions = [get_time]

routes = []

llm = CohereLLM(name="command-nightly")

for function in functions:
    route = Route.from_dynamic_route(entity=function, llm=llm)
    routes.append(route)

layer_config = LayerConfig(routes=routes, encoder_type="cohere", encoder_name="embed-english-v3.0")
layer_config.to_file("output/layer_config.json")

Expected behavior
The to_file method should successfully serialize the Layer object and its routes (including any Client objects) to a file in JSON or YAML format.
Error

Hi @yusufola, I'm investigating this issue. Thank you for bringing it to our attention.

@yusufola, I'm making some updates in a branch to bug fix this. It's in the early testing and review phase. Will let you know when we have something more concrete.

Many Thanks @Siraj-Aizlewood

@yusufola this has been fixed and merged into main now. Please let us know if you run into any additional issues.

I forgot to mention: If this resolves things, please close the Issue :-)


Plugin enabled but no "options" page

I've installed the plugin but the "options" view isn't available so I can't configure it.

You should see the obsidian icon folder settings when you go to settings. This is the same thing.

You should see the obsidian icon folder settings when you go to settings. This is the same thing.

Exactly but it isn't there. I posted a screenshot of the plugin page because usually the "Options" button appear right next to "Disable" when the plugin has options but apparently it's a bug.
Anyway, it doesn't show up in the settings list too, so I can't get it to work:

I closed the issue because I thought it was solved. I restarted Obsidian and the plugin was working, I set up a few icons, closed Obsidian again and when I reopened it the plugin wasn't working anymore.
It is enabled but it doesn't show the custom icons anymore and there is NOT a settings page.


Unsure how to use setLogger

Hi,
I'm not sure how to use $api->setLogger function so it will write into Laravel log files.
I'm trying to get the errors->exception from the rest response and I see that the api class already logs it so I tried to use setLogger however I don't see it created the file.
Most likely, I set it up incorrectly.
This is my code:
use Monolog\Logger;
use Monolog\Handler\StreamHandler;

$logger = new Logger('shopify');
        $logger->pushHandler(new StreamHandler(storage_path('logs/flagged-order.log'), Logger::WARNING));
        $this->shop->api()->setLogger($logger);

Here's the api response:
{#6643 ▼
  +"response": Response {#6640 ▼
    -reasonPhrase: "Bad Request"
    -statusCode: 400
    -headers: array:29 [▶]
    -headerNames: array:29 [▶]
    -protocol: "1.1"
    -stream: Stream {#6638 ▶}
  }
  +"errors": {#6634 ▼
    +"status": 400
    +"body": {#261 ▼
      +"errors": {#6637 ▼
        +"page_info": "Invalid value."
      }
    }
    +"exception": ClientException {#6641 ▶}
  }
  +"body": ""
  +"timestamps": array:2 [▶]

Please help. Thanks :)

Sorry, will look into this.
The logger only logs some debug items, it does not capture full responses.
I'll see whats up.. but should accept any PSR compatible logger and "work" in my previous testing.

Yes... so the logger is only for debug purposes, it does not catch "errors" param and shoot it to the logs... I will adjust it so it does!

Thanks!


Update visualize.py: Flexible Image Size

Added flexible input image size for attention map visualization.
I was using this excellent repo. However, when I wanted to visualize the attention map, I noticed that visualize.py accepts just square input (but mine was rectangle). That is why I adjusted the attention map function: as it will get the dimensions of the height and width of the model input shape, then it will resize a given image to that input shape (not to a square).

This is now available in vit-keras v0.1.1.


Migrating psql DB fails when using Decimal type on models

Expected Behavior
Database should be created including column for Decimal property
Actual Behavior
Thread 1: Fatal error points to line 179 of the file Decodable+CodingPath.swift (path: Core 3.0.0-rc.1.0.1/CodableKit/Key)
With logging enabled:
databaseConfig.enableLogging(on: .psql)

the output is:
Migrating psql DB
[psql] [2018-03-20 20:39:24 +0000] SELECT count(*) as "fluentAggregate" FROM "fluent" []
[psql] [2018-03-20 20:39:24 +0000] SELECT "fluent".* FROM "fluent" ORDER BY "fluent"."batch" DESC LIMIT 1 OFFSET 0 []
[psql] [2018-03-20 20:39:24 +0000] SELECT "fluent".* FROM "fluent" WHERE ("fluent"."name" = $1) LIMIT 1 OFFSET 0 ["7 bytes"]
[psql] [2018-03-20 20:39:24 +0000] SELECT "fluent".* FROM "fluent" WHERE ("fluent"."name" = $1) LIMIT 1 OFFSET 0 ["6 bytes"]
[psql] [2018-03-20 20:39:24 +0000] SELECT "fluent".* FROM "fluent" WHERE ("fluent"."name" = $1) LIMIT 1 OFFSET 0 ["18 bytes"]
[psql] [2018-03-20 20:39:24 +0000] SELECT "fluent".* FROM "fluent" WHERE ("fluent"."name" = $1) LIMIT 1 OFFSET 0 ["13 bytes"]

Steps to Reproduce the Problem

Create new project (e.g. vapor new api-template --template=api --branch=beta )
Add Postgres config
Add decimal property to model

import FluentPostgreSQL
import Foundation
import Vapor

struct Todo: Content, Migration, Parameter, PostgreSQLModel {
  var id: Int?
  var decimal: Decimal
}

Hit Run

Specifications

Versions:

Vapor Toolbox 3.1.4
Swift 4.1
Xcode 9.3 beta 4

Decimal encodes to JSON, like:
{"exponent":-3,"length":1,"isCompact":true,"isNegative":true,"mantissa":[1234,0,0,0,0,0,0,0]} (JSONB)

This is desired since it allows the type to store values with higher precision than Float and Double. I've added a test to make sure this is working in the latest build, just make sure to use a JSONB column type 👍 .


Can not use go get github.com/webview/webview

What OS are you using (uname -a, or Windows version)?
macOS 10.14.6 Mojave
What programming language are you using (C/C++/Go/Rust)?
go version go1.17.2 darwin/amd64
What did you expect to see and what you saw instead?
I expected go get github.com/webview/webview to add the webview package to my Go environment
Instead I get the error go build github.com/webview/webview: build constraints exclude all Go files in<EMAIL_ADDRESS>I realized this was a CGO issue and so tried
$ CGO_ENABLED=1 go get github.com/webview/webview
# github.com/webview/webview
In file included from webview.cc:3:
In file included from ../../lib/pkg/mod/github.com/webview/webview@v0.0.0-20210330151455-f540d88dde4e/webview.h:129:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/functional:494:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/memory:660:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/iterator:416:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/iosfwd:96:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/wchar.h:119:
In file included from /usr/local/include/wchar.h:90:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/stdio.h:108:
/usr/local/include/stdio.h:205:10: fatal error: '_ctermid.h' file not found

Like most Go developers <sarcasm>I love CGO with all my heart</sarcasm> and remembered from prior experience to add CPATH:
$ CPATH=/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include CGO_ENABLED=1 go get github.com/webview/webview
# github.com/webview/webview
In file included from _cgo_export.c:3:
/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/stdlib.h:134:25: warning: pointer is missing a nullability type specifier (_Nonnull, _Nullable, or _Null_unspecified) [-Wnullability-completeness]
##### REMOVED OVER 1,000 LINES FROM EXAMPLE FOR SANITY #####
/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/stdlib.h:356:13: note: insert '_Nonnull' if the pointer should never be null
# github.com/webview/webview
In file included from webview.cc:3:
../../lib/pkg/mod/github.com/webview/webview@v0.0.0-20210330151455-f540d88dde4e/webview.h:577:10: fatal error: 'CoreGraphics/CoreGraphics.h' file not found
../../lib/pkg/mod/github.com/webview/webview@v0.0.0-20210330151455-f540d88dde4e/webview.h:577:10: note: did not find header 'CoreGraphics.h' in framework 'CoreGraphics' (loaded from '/System/Library/Frameworks')

So obviously CoreGraphics framework needs to be included. I've seen online where I can do go build -ldflags="-framework CoreGraphics" but
$ CPATH=/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include CGO_ENABLED=1 go get -ldflags="-framework CoreGraphics" github.com/webview/webview

and
$ CPATH=/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include CGO_ENABLED=1 LDFLAGS="-framework CoreGraphics" go get github.com/webview/webview

does not change in errors generated.
So how can I go get the WebView package at this point? I've done it before without issue. Or at least not much issue beyond the CGO_ENABLED and CPATH variables being needed possibly.

OK, after days of digging and testing this is what finally worked to let me go get github.com/webview/webview on my system without erroring even when there was no update to be had.
export CPATH=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include
export CGO_CPPFLAGS="-F/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks -Wno-expansion-to-defined -Wno-nullability-completeness"
CGO_ENABLED=1 CGO_LDFLAGS="-framework CoreGraphics -g -O2" go get github.com/webview/webview

Absolutely everything was required except for -g -O2 in CGO_LDFLAGS. But as it was the default for CGO_LDFLAGS on my system I didn't want to specifically remove it.


Add transformationController to Interactive Viewer

This simply adds a way to use a TransformationController with the InteractiveViewer inside the player.

LGTM.


Allow autocompletion of fields

Change Summary
Modifies the __dir__ method to show fields as well as canonical functions and attributes. As the __dir__ method is explicitly for interactive use (see the docs) this should not effect other areas of pydantic and as such is implemented in a very straightforward manner. It is also possible to hide metafields and the Config object as well if desired.
Use case: Our users will often handle pydantic objects in Jupyter notebooks and interactive interpreters where this feature is quite useful when exploring objects that they are not familiar with.
Checklist

[x] Unit tests for the changes exist
[x] Tests pass on CI and coverage remains at 100%
[x] Documentation reflects the changes where applicable
[x] HISTORY.rst has been updated

if this is the first change since a release, please add a new section
include the issue number or this pull request number #<number>
include your github username @<whomever>

awesome, thank you.


Feature request : Custom shorthands with multiple parameters {}

Hello,
In custom shorthands, if the expression ends by {}, cursor automatically goes inside the brackets. If there are multiple {}, it would be really useful that :

Cursor moves into the first {}, and not the last.
Using tab, we could jump to the next {}.
Using shift + tab, we could jump to the previous {}.

This feature exists in TexMaker (customize completion), and it is so useful.
I often define macros with multiple parameters (e.g. : \macroName{param1}{param2}{param3}) : it would be really useful to have the previously described feature.
Also, as mentioned here, it would be wonderful if custom shorthands were not limited to only 2 characters.
Thanks !

To anyone it may help, here is a solid workaround using Espanso :
https://forum.remnote.io/t/using-espanso-a-text-expander-to-automate-writing-latex/4089

@Elaws  Hi! Thank you so much for the suggestion!
though, as people use this custom shorthand for various different purposes, I am afraid that the tab jumping feature may not generalize to other use cases...
But you are more than welcome to fork this repository and customize to your own usage~
However, I incorporated your other suggestion about allowing more characters to be the custom shorthands. Hope that helps~

Thanks for implementing #30 !
If this tab jumping function was proposed as an option disabled by default, wouldn't it be safe for, other use cases ?
If not applicable, I will think of forking the repo indeed ;)

Resolved in v2.3.0, please update and take a look! (try uninstall and reinstall the plugin to see the new default list of shorthands with multiple parameters)
The function now allows using "#cursor"  to set the cursor location after replacement,
and also use "#tab" to set the next place to fill after pressing tab
e.g. bi:\binom{#cursor}{#tab},  after keying bi and spacebar, the shorthand will expand into \binom{|}{#tab} with cursor in the first brackets. After keying the values in first brackets, press tab to jump to the #tab location to continue typing.


feat!(remix-react,remix-server-runtime): remove deprecated properties from HtmlLinkDescriptor, LinkDescriptor & PrefetchPageDescriptor types

Hey @MichaelDeBoey, I think we should actually keep these in place for now. We have no plans to drop support for React 17, and I don't want the console yelling at folks who are following older type defs. Gonna go ahead and close this for now!

@chaance This is not dropping React 17 support, it is only dropping the possible use of these props.
I still made sure that React 17 is supported, so I think we should re-open this PR
https://github.com/MichaelDeBoey/remix/blob/f4bb5427f8fc41f494bedc5fc6ffcf451dcf9e44/packages/remix-react/components.tsx#L379-L384
https://github.com/MichaelDeBoey/remix/blob/f4bb5427f8fc41f494bedc5fc6ffcf451dcf9e44/packages/remix-react/components.tsx#L400-L401

I added some filters for console.log assertions in https://github.com/remix-run/remix/pull/5706 prior to merging to avoid false negatives.  Once dev is merged out to v2 again we should rebase this and remove those filters in this PR

@brophdawg11 The extra changes you mentioned are now removed as well in this PR


Remove all references to absent nixos-prepare-root

Fixes the broken 0f5d5970b28c9d85e7166f85ecfa3f86064d3f25 commit.
Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Also, the referenced commit states that this is no longer necessary due to nix 2.0's magic.
What is this magic? @edolstra

The "magic" is that Nix 2.0 has chroot support, so it's no longer needed to bootstrap the target environment by copying Nix to it.


Screenshots for app store

would someone be interested in creating screenshots for the app store?
You must upload a screenshot for 12.9-inch iPad Pro (2nd generation) displays.
You must upload a screenshot for 12.9-inch iPad Pro (6th generation) displays.
You must upload a screenshot for 5.5-inch iPhone displays.
You must upload a screenshot for 6.5-inch iPhone displays.

I am intreasted, Should i run the app in different emulator of these sizes and take the ss ?

Yes from the simulator is good.  They must match the height and width requirements exactly so please check those. 3 screenshots for each model is sufficient. Thank you!

Ok got it Thanks @letsintegreat @DonnieBLT

https://drive.google.com/drive/folders/1ta8Fc5t2orGxC_qyf_CMBeRcZASR6rnP?usp=sharing
Screenshots are uploaded here


[docs] Deploy on iisnode

Documentation entry for https://github.com/mui/mui-toolpad/issues/3153#issuecomment-1921749059
Very basic, mostly delegating to existing documentation.
https://deploy-preview-3155--mui-toolpad-docs.netlify.app/toolpad/how-to-guides/iis-deploy/

Didn't seem to work for the user


Missing conditional compilation symbol WINDOWS

This is a fix for issue #2

I just noticed this is also a problem for the mvvmcross implementation, so the "fix" also needs to be implemented in that project file.


wallet-ext: create & import flow

path aliases
fixes webpack eslint plugin to check all the files
force extension to open in main window when wallet is not initialized
create and import mnemonic
after creating a wallet show the mnemonic to the user to save for backup
NOTE: mnemonic is not encrypted for now

Views:

Welcome

Choose wallet init option

Import

Create

Backup

Main view (after importing/creating a wallet)

part of #1849

See video: "passphrase is not valid" does not prevent me from going into the next screen.
https://user-images.githubusercontent.com/76067158/168735619-90a4534e-d398-41a0-a199-58fb3e880677.mp4

See video: "passphrase is not valid" does not prevent me from going into the next screen.
CleanShot.2022-05-16.at.22.27.00.mp4

Thanks for the review @666lcz! This was done in order to just follow this

Please remember to allow recovery from mnemonic phrases that have invalid checksums (or that you don't have the wordlist)

But I didn't care much about providing < 12 works, since in the end it creates a key. I will improve it and push a fix soon. Thanks

@666lcz I fixed it, just disabled the button whenever the mnemonic is invalid. (Updated some of the dependencies as well)


flask_util refers to GOOGLE_OAUTH2_CLIENT_SECRETS_JSON instead of GOOGLE_OAUTH2_CLIENT_SECRETS_FILE

In https://github.com/google/oauth2client/blob/master/oauth2client/contrib/flask_util.py#L38
This refers to GOOGLE_OAUTH2_CLIENT_SECRETS_JSON in the comments.
This should actually be GOOGLE_OAUTH2_CLIENT_SECRETS_FILE.  Otherwise, you get an error later on...
ValueError: OAuth2 configuration could not be found. Either specify the client_secrets_file or client_id and client_secret or set theapp configuration variables GOOGLE_OAUTH2_CLIENT_SECRETS_FILE or GOOGLE_OAUTH2_CLIENT_ID and GOOGLE_OAUTH2_CLIENT_SECRET.

There's also 4 other hits in the same file for GOOGLE_OAUTH2_CLIENT_SECRETS_JSON


Add feature to permit users to save the generated visualization data

This should apply to, at minimum, the pipeline visualizations

Added feature in b9e4e27

Passed all devel tests


[FEATURE] cog.toml schema validation

Is your feature request related to a problem? Please describe.
Not a problem per say, but think the experience would be nicer if there was validation and documentation connected to the cog.toml file.
Describe the solution you'd like
It'd help to reduce errors if there was a related JSON schema describing the TOML config, and also easier to find documentation if there was the related description on each field.
It could be referenced as such:
#:schema ./cog.json

ignore_merge_commits = true

And get functionality like the following:

Describe alternatives you've considered
Creating a local cog.json schema file and referencing that
Additional context
I don't think it's a complete set of all the fields but here's an example json schema that I manually put together. But I think this could be generated somehow from the actual documentation.
https://gist.github.com/mewhhaha/a326542c4dd3bbd1f39214f919766ab0

Hello @mewhhaha, this would be super cool !
Here are the required steps to get there:

[ ] generate the schema from rustdoc, we could use trustfall or directly parse the rustdoc ouput.
[ ] expose the schema on cocogitto.io
[ ] add #:schema https://cocogitto.io/cog-schema.json to the cog.toml template
[ ] documentation (this would work out of the box for lsp based text editors such as lapce, zed vscode etc; but would require some manual configuration for jetbrains IDEs, neovim)

Thanks a lot for suggesting this, let me know if you are interested in implementing it yourself.

I you need help for the trustfall part don't hesitate to ask on discord.

Another way of doing it is using the JSONSchema derive from schemars. Maybe that's not preferable, but I put up an example PR to show how it would look like.
https://github.com/cocogitto/cocogitto/pull/393
I got a bit stuck with trustfall and looking through the rustdocs.json (killed my computer) 🫠


Onnxruntime 1.7.0 breaks tests

https://github.com/microsoft/hummingbird/runs/2035682979
We need to investigate why onnxruntime==1.7.0 breaks the tests. (Last known good at 1.6.0)

Closed with #523 🎊


"Move all" shortcut improvement

Make the "move all" shortcut include the hotbar items when a chest is open?

(Duplicate of previously done issue)


net/frr: added as-override to gui

This is to bring in the ability add the as-override command to the neighbor peers so that the AS number of learned local peers can be overridden to the local AS number. This only works with EBGP peers but is necessary to use when wanting to filter out VRF based peering traffic and advertising learned local routes into your ebgp network space.

@mimugmail ping

Merged, thanks!


Make core API work with Python 2.x

tsalib is tested with Python 3.6 but the core API implementation should work with Python 2.x with minor changes.

Not a priority now.


Open World makes first thing in an OrderedCollection indeterminate

Given the open world assumption, it is not possible to tell which is the first thing in an OrderedCollection just by looking for the absence of a predecessor.   We may want an explicit hasFirstMember type property to remove this ambiguity and make it easy to find the first member of an OrderedCollection.

Excellent point from @stewardont. I'm in favor of this.

DECISION: Add hasFirstMember predicate - subproperty of hasMember, domain is OrderedCollection, range is OrderedMember. Not a functional  property since ordered collections are not necessarily strictly ordered.

Fixed in PR #667.


Still getting error after 9anime extension update

Source information and language
Version: 13.36  Language: English eu.kanade.tachiyomi.animeextension.en.nineanime
Steps to reproduce
Try to use the 9anime extension.
Expected behavior
Open 9anime anime series for streaming and download
Actual behavior
Fails to even bring up anime episode list.
Aniyomi version
App version: <IP_ADDRESS>
Android version
Android 11
Other details
App version: <IP_ADDRESS> (standard, 7722361, 72, 2023-02-09T10:47Z)
Android version: 11 (SDK 30)
Device brand: Motorola
Device manufacturer: Motorola
Device model: moto g power (2020)
Device product name: sofia_retail

9Anime extension version Version: 13.36
Language: English eu.kanade.tachiyomi.animeextension.en.nineanime
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version <IP_ADDRESS>
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

I'm also having the same problem with gogoanime as weel as 9anime maybe all anime sources are not working I can't watch even any anime from the extensions

This was fixed by clearing data, system cash, and using a beta version of the app


Feedback on improving unique array API

In the Data API meeting, we started discussing some pain points around the current NumPy unique implementation and how we might improve this ( https://github.com/data-apis/array-api/issues/212 ). Part of the issue is this function tries to do a bunch of stuff, which results in some unpleasantness around implementation, usage, etc. Some ideas around how we might improve it our included in that issue. Would be curious to know how others think we might improve the API of unique generally as well as how this plays into use cases in practice.

Combing through the issues here have identified the following:

Doing tree reductions with unique is complicated due to all the return values provided ( https://github.com/dask/dask/issues/2851 )
Returning multiple arguments complicates things for Dask (making it hard to use CuPy or other things) ( https://github.com/dask/dask/issues/7482 )
Memory usage can be a problem for some additional arguments ( https://github.com/dask/dask/issues/6828 ) ( https://github.com/dask/dask/issues/5377 )

Admittedly with all of these there is some gray area in terms of whether these are issues with Dask itself, the API, or its usage.

@pentschev, would be good to get your thoughts here since we have discussed the oddities of np.unique before and the changes proposed in the Data API may help with that here

@jakirkham yeah, I've seen this before, and I wrote https://github.com/dask/dask/issues/7997 covering two issues that involve structured arrays in Dask, one of them being da.unique. Unfortunately I haven't found any better ideas than using a dict, and in the case of np.unique I went ahead with https://github.com/dask/dask/pull/8021 to allow computing it with CuPy chunks, but for values only.
I'm happy to engage in further discussion, but I also got stuck with that problem without a good solution.

Since this is mostly an upstream issue in Data API, I'm going to close this here and let discussion continue there.


Feature/gh 303

Added typesafety for AuthenticationModule and GlobalMessageModule, unable to find any where I can do so for RoutingModule

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


feat: allow differential objects with shifts in an AddMonoidWithOne

What I was really hoping to do was show that ℕ-graded DGOs were the same as ℕ-graded chain complexes (we have the ℤ version), but this still seems awkward. If anyone would like to help with that, please let me know. I think this might be helpful in constructor tensor products of chain complexes with less suffering.

bors d+

bors merge


Add Collector status to the collector page

A part of #1574

For prior and relevant discussion see, https://github.com/open-telemetry/opentelemetry.io/issues/1570#issuecomment-1199491412, and https://github.com/open-telemetry/opentelemetry.io/issues/1570#issuecomment-1199506433 in which @TylerHelmuth wrote:

Makes sense. The collector SIG has established Stability Levels for components and is https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/10116 with that status (and more). There has also been updates to allow components to print out their stability level on collector startup if the component is unmaintained or deprecated. Hopefully that work is helpful in some way.

@TylerHelmuth and @open-telemetry/collector-maintainers: where can I find the collector's status (as a whole)? /cc @cartermp


unset akash gas price env. var. on init targets

In the latest RC & on master I can't do make init on the _run/kube example because it tries to connect to an RPC node & fails.
This change disables the Akash gas prices config. on the init target, where it is no longer needed. At that point I can get make init to work again.

it looks like a bug in cosmos sdk. it should not go for node talk


Alpha - regular controller closes #1

Signed-off-by: Judy-Zhu<EMAIL_ADDRESS>

Alpha link is not working properly.


[Question] What is crashlytics_build_id.xml and crashlytics_unity_version.xml and can they be gitignore'd?

Hi!
In Assets/Plugins/Android/FirebaseCrashlytics.androidlib/res/values I notice there are 2 files:
crashlytics_build_id.xml
crashlytics_unity_version.xml
(and with 2 related .meta files generated by Unity)
Questions:

What are they for exactly?
Is it needed to track them in git or we can add them to .gitignore? (Especially it seems crashlytics_build_id.xml is changed every time I build the Unity project which I think it's like a "temp" generated file)

Thanks.

Those files are regenerated whenever you build your scene, so they're safe to .gitignore. I'm not sure what they're for off the top of my head but I'll ask and get back to you.

They are required for Crashlytics Android SDK. Basically information like bundle-id and Unity version number. (You can click into it and read them. :) )
I would say you can gitignore the entire FirebaseCrashlytics.androidlib and FirebaseApp.androidlib folder.  They will just regenerate whenever Unity is launched.
I'll close this issue for now.


getDerivedStateFromProps

Hi! Cool HOC collection!
Could you please provide a usage example of a getDerivedStateFromProps method?
Is it just work inside onReceiveProps but with new logic?

Hi. Cool HOC collection!

Hi. Thanks :)

Is it just work inside onReceiveProps but with new logic?

Exactly.
Because getDerivedStateFromProps with its returned state doesn't match well the HOCs idea, onReceiveProps lifecycle method is basically a getDerivedStateFromProps under the hood but only as a callback, without the returned state feature.
I hope that onReceiveProps name is not very confusing, I had to improvise.

withLifecycle({
  onReceiveProps(props, nextProps) {
    // called every time `getDerivedStateFromProps` is called,
    // i.e. "on constructor" as well
  }
})

Noice! My life's getting easier.
It would be nice to see some basic examples in the docs for each of the methods though - better help newcomers. Maybe i'll fetch a PR.

Maybe i'll fetch a PR

Please do 🙏


Update README.md for AWS usage.

The following PR updates the README.md for how to use vault-unsealer with existing vaults / new vaults.
It also describes the set of permissions needed on IAM for using this tool.

Thanks @innovia, this AWS documentation was very helpful.  I was also able to get it working with a bit less permissive policy which I've attached.
https://gist.github.com/FraaJad/414821a42c2a7675ab14c1a95d8738b7

@simonswine round done. Can we proceed with the PR?

@apenney
Thanks for taking a look, I have moved the AWS instructions under docs to a separated file in order to  keep the readme more concise and leave room for future google instructions.
Ami

@apenney can we continue with the PR?

Can someone continue please with this PR?

@simonswine @apenney  ping

@innovia yeah sorry but there way much work than time in a day. Just continue nudging. I guess it would have made it easier with smaller pieces.
Maybe take a look if my build from source instructions work for you

/lgtm
/approve

/test verify

/test verify

/approve


lxml vulnerable to quadratic blowup

Parsing XML from sources you don't control opens the door for multiple XML parser vulnerabilities. lxml prevents some, but not all, with quadratic blowup being one of them. Switching to defusedxml would fix this.
Expected Behavior
nexpose-client-python should avoid entity expansion when parsing incoming XML.

Current Behavior
nexpose-client-python may open up the user to XML parser vulnerabilities if pointed at a fake nexpose instance.

Possible Solution
Use defusedxml, which is a drop-in replacement for lxml.

From the documentation on defusedxml it seems like it's not necessarily a complete drop-in replacement. I may need to look into it some more, though.
For now I feel that this is a fairly low priority issues since risk of attack is very low. That said if someone comes in with a pull request I won't turn them away.


No Instruction -100

how to run this

how to run this

hey sorry i didn't document much because this was our project and it's done. To run this, you need to install love2d and have also lua because love2d uses it. if your'e using linux, you can download both love2d and lua using your package manager, for windows, you need to download the installer and the same for lua. May I ask what OS are you using?

im using Windows11 :>

im using Windows11 :>

you can now download the game from the releases page


Add support for creator package

Hello, Creator is a state management package I recently released. It is inspired by rivperpod.
Currently, I'm copying all the source code to make DartPad work (example), and I would like to request native DartPad support.
Not sure what is the criteria here. I guess my package is still too early? Anyway, creating this issue to track.

+1

+1

Closed in #995

Actually, this isn't shipped to production, so I'm re-opening this issue. This package has been shipped to our hidden testing instance https://dartpad.dev/?channel=dev
Please exercise your suggested package on this instance and confirm here that it works as intended. If you do confirm this as working I'll ship it to stable, beta, master, and old channels on dartpad.dev. If you don't confirm, I won't ship it.

Hi @domesticmouse I confirm it works on the testing instance. Thank you!

Thank you @terryl1900!


Proposal: change to contributing guidelines

Hey! It's me, again, I know, I'm annoying.
So, I'd like to propose here another contributing model that addresses both the issues raised in this issue, and some others, it consists of:

A protected main branch where only you, the maintainer, can push to.
A protected dev branch where only you, the maintainer, and trusted contributors (listed as 'developers' in Github) can push to, but, people can issue a merge request to this branch with their hot new changes, before being merged into main when it's seen as stable.
A (optionally protected) testing branch where you and other people can test crazy (fun) stuff that you would never in a hundred moons put in your main code, but, if it works out, you can merge into your dev branch for additional testing, or you can just burn it all to the ground when you see it's a clearly bad idea, it's part of the fun of it I suppose.

Feel free to take what I say, take it apart or tweak it as it fits you, no need to be shy!
Edit:
But, yeah, I noticed something odd with your current model, why the email part? Why? I don't really mind it all that much, but it's a hell of a lot of bureaucracy for something that could be easily discussed in the merge request itself.
If you intend to keep the email requirement, I'd really appreciate it if you would specify why in the readme.

Thanks for the feedback again and no you aren't annoying me, I think that I'm the only one who is capable of performing merge, commits and etc, into the project, probably I will create a test branch, so we can make things go boom without hurting anyone, which is great, thanks for all the advices man, I'm lovin' it.


[ZEPPELIN-4068] Implement MongoNotebookRepo

What is this PR for?
the format of note storage file name is changed  in 0.9, this is the implementation of MongoNotebookRepo.please refer to ZEPPELIN-2619.
this patch use a folder collection to store path hierarchy.
What type of PR is it?
[Bug Fix | Improvement | Feature | Documentation | Hot Fix | Refactoring]
Feature
Todos

[ ] - this implementation need mongoDB 3.4.

What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-4068
How should this be tested?
manual
Screenshots (if appropriate)
Questions:

Does the licenses files need update?
no
Is there breaking changes for older versions?
no
Does this needs documentation?
no

Thanks @yx91490 , Could you add unit test for it ?

Thanks @yx91490 , Could you add unit test for it ?

It is difficut to add unit test, because I don't know which mongoDB server to connect.

Just curious to know is there any embedded mongodb server for unit test ? What other projects do unit test if they use mongdo ?

Just curious to know is there any embedded mongodb server for unit test ? What other projects do unit test if they use mongdo ?

ping @yx91490

ping @yx91490

I'll solve it on this weekend.

ping @yx91490 Do you have time to continue this work ?

ping @yx91490 Do you have time to continue this work ?

wait for your reply...

because this pr's repo have been deleted before, I pushed a new pr for this issue.


Overhaul the version to codename mapping

We currently resolve cloud component versions to OpenStack codenames using a modified version of zaza's get_os_code_info function. This issue tracks at least these improvements:

since the mapping is applied to both core OpenStack components and auxiliary components (e.g. ceph, ovn), it should more appropriately named; we're basically returning the latest or the set of OpenStack versions a given component is compatible with
all related code should live in the same place. The Application class should import the lookup function and call it without having to know its inner workings, i.e. Application._get_representative_workload_pkg and Application._get_current_os_version should disappear
stop using regexps and use an external package for parsing versions
don't just look at the major version. Horizon in particular can only be mapped checking if its version falls in a specific range: 17.0.0 to 18.3.5 is Ussuri, while Victoria starts at 18.4
keep in mind all of this should eventually become an external package. Everything should be self-contained

Closed by #16


Add an intro/welcome message on first run

This is a bit abrupt and unclear why I need an access token:
$ vip
 This will open https://ui.go-vip.co/me/cli/2 in your web browser. Follow the instructions there to acquire an access token. Continue? (Y/n)

Welcome to
 _    __________     ______
| |  / /  _/ __ \   / ____/___
| | / // // /_/ /  / / __/ __ \
| |/ // // ____/  / /_/ / /_/ /
|___/___/_/       \____/\____/

You need an access token to continue. Next, we'll open https://ui.go-vip.co/me/cli/2 in your web browser. Follow the instructions there to acquire an access token. Continue? (Y/n)


Enhancement: Show IP Address on System or settings screen

I was hoping there would be a way to show the IP address of the device on the system or settings screens, that way when you connect the musicbox to a new wired netwrok, you can use one device to find the IP (By going to musibox.local) and then you can use that address if you have an android device.

There is an issue for this already somewhere.
On 9 Apr 2015 03:34, "Daniel Selmes"<EMAIL_ADDRESS>wrote:

I was hoping there would be a way to show the IP address of the device on
the system or settings screens, that way when you connect the musicbox to a
new wired netwrok, you can use one device to find the IP (By going to
musibox.local) and then you can use that address if you have an android
device.
—
Reply to this email directly or view it on GitHub
https://github.com/woutervanwijk/Pi-MusicBox/issues/269.

Duplicate of https://github.com/woutervanwijk/Mopidy-MusicBox-Webclient/issues/67


Fix PR template

Moves the PR template to a different folder, see https://github.com/ros-controls/ros2_control_demos/pull/270 where this worked out.

Codecov Report

Merging #587 (136191f) into master (e7f9962) will decrease coverage by 3.31%.
The diff coverage is 26.60%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##           master     #587      +/-   ##
==========================================
- Coverage   35.78%   32.48%   -3.31%
==========================================
  Files         189        7     -182
  Lines       17570      665   -16905
  Branches    11592      357   -11235
==========================================
- Hits         6287      216    -6071
+ Misses        994      157     -837
+ Partials    10289      292    -9997

Flag
Coverage Δ

unittests
32.48% <26.60%> (-3.31%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ontroller/test/test_load_diff_drive_controller.cpp
12.50% <0.00%> (ø)

diff_drive_controller/src/odometry.cpp
42.16% <11.11%> (ø)

diff_drive_controller/src/speed_limiter.cpp
46.55% <11.11%> (ø)

...ive_controller/test/test_diff_drive_controller.cpp
17.62% <12.08%> (ø)

...troller/include/diff_drive_controller/odometry.hpp
20.00% <20.00%> (ø)

...iff_drive_controller/src/diff_drive_controller.cpp
39.22% <35.50%> (ø)

...de/diff_drive_controller/diff_drive_controller.hpp
100.00% <100.00%> (ø)

... and 189 files with indirect coverage changes


Propagate trace context to workers

Hello @jenniferplusplus 👋
I was starting to wonder how I could pass the trace coming from an API to the consumers, and I noticed this package to instrument with Otel our BullMQ.
Would it make sense to instrument this package in a way it detects the trace ID on the add() method, and set the trace context in the worker doing the process? (is it even possible?)
What I had in mind was to use propagation to detect the current trace (https://opentelemetry.io/docs/languages/js/propagation/) and pass it in the data object with a custom property (_otel: { traceparent: <traceparent>}). Then when the worker picks up a job, we could remove the field _otel and instruct the new context to use the traceparent. What do you think?
I would be curious to give it a try!

@Lp-Francois I don't actually work on projects that depend on BullMQ anymore, so tbh it's been a couple of years since I really gave this project much thought.
IIRC, trace context does propagate from Add down to the worker. I certainly meant for it to, and I'm pretty sure it used to. If that's not working, I would consider it a bug and want to fix it.

Also, I had built the propagation field into the job headers, rather than the data. It seemed less likely to disrupt workers

Hello! So I double checked, and I did something wrong with my example, I started fresh with a simple setup on NestJS and I can get the same traceID through the job :)
Sorry for the issue, will close :)

No worries, glad it's working for you


added build script, environment yaml, action to build and publish main branch to pypi.org test as version 1 on push

Thanks!! Will merge and then update readme.


Need nzalchemy build compatible with sqlalchemy 1.4.22

Team,
Is there any timeline for getting compatible version of nzalchemy with latest sqlalchemy 1.4.22 version ? This is needed for addressing few security issues found on sqlalchemy 1.3.x builds and upgrading to SQLAlchemy 1.4.22 is blocked by nzalchemy due to its dependency  on SQLAlchemy<=1.3.24
Env:
Python 3.8
SQLAlchemy 1.4.22
nzpy==1.15
nzalchemy==11.0.2
ERROR: nzalchemy 11.0.2 has requirement SQLAlchemy<=1.3.24, but you'll have sqlalchemy 1.4.22 which is incompatible.

bump

bump

bump