Focused Aim causes type error

A monk with this feature missed the target, and the Focused Aim dialog popped up allowing the choice of how many ki points to spend. After selecting the correct amount of ki to correct the miss, I got the following error in the console log. Using CPR 0.2.8, midi 10.0.35, ddb-importer 3.4.12
focusedAim.js:36 Uncaught (in promise) TypeError: undefined. originItem.use is not a function
[Detected 2 packages: chris-premades, midi-qol]
at Workflow.focusedAim (focusedAim.js:36:22)
at async eval (eval at callMacro (workflow.js:1669:15), :4:3)
at async Promise.all (index 0)
at async Workflow.callMacros (workflow.js:1559:13)
at async Workflow._next (workflow.js:440:6)
at async Workflow.next (workflow.js:262:10)
at async Item5e.doAttackRoll (itemhandling.js:517:2)
at async Workflow._next (workflow.js:416:6)
at async Workflow.next (workflow.js:262:10)
at async Workflow.next (workflow.js:262:10)
at async Workflow.next (workflow.js:262:10)
at async Workflow.next (workflow.js:262:10)
at async Workflow.next (workflow.js:262:10)

I'll take a look at this when I get home later tonight.

Could you screenshot the focused aim effect that is on the actor.  Specifically interested in seeing what it says the source is.

I've verified that the item referenced is Focused Aim using developer mode.
{
"name": "Focused Aim",
"type": "feat",
"system": {
"description": {
"value": "When you miss with an attack roll, you can spend 1-3 ki points to increase your attack roll by 2 for each of these ki points you spend, potentially turning the miss into a hit.\n\n  \n    More Details\n  \n  \n    5th-level monk featureWhen you miss with an attack roll, you can spend 1 to 3 ki points to increase your attack roll by 2 for each of these ki points you spend, potentially turning the miss into a hit.\n  \n",
"chat": "",
"unidentified": ""
},
"source": "",
"activation": {
"type": "special",
"cost": 1,
"condition": ""
},
"duration": {
"value": "",
"units": ""
},
"target": {
"value": null,
"width": null,
"units": "",
"type": ""
},
"range": {
"value": null,
"long": null,
"units": ""
},
"uses": {
"value": null,
"max": "",
"per": "",
"recovery": ""
},
"consume": {
"type": "charges",
"target": "hobuo2x8EpPJuBzY",
"amount": 1
},
"ability": "",
"actionType": "other",
"attackBonus": "",
"chatFlavor": "",
"critical": {
"threshold": null,
"damage": ""
},
"damage": {
"parts": [],
"versatile": ""
},
"formula": "",
"save": {
"ability": "",
"dc": null,
"scaling": "spell"
},
"type": {
"value": "class",
"subtype": ""
},
"requirements": "",
"recharge": {
"value": null,
"charged": false
}
},
"flags": {
"ddbimporter": {
"id": "2438003",
"entityTypeId": "222216831",
"componentId": 3035408,
"componentTypeId": 12168134,
"type": "class",
"class": "Monk",
"subclass": "Way of Shadow",
"dndbeyond": {},
"effectsApplied": true,
"chrisEffectsApplied": true,
"chrisPreEffectName": "Focused Aim",
"importId": "NDBFjgrEfx2WUPAF"
},
"infusions": {
"infused": false
},
"obsidian": {
"source": {
"type": "class",
"text": "Monk"
}
},
"midi-qol": {
"onUseMacroName": "",
"effectActivation": false
},
"custom-character-sheet-sections": {
"sectionName": ""
},
"rest-recovery": {
"data": {
"recovery": {
"enabled": false
}
}
},
"midiProperties": {
"nodam": false,
"fulldam": false,
"halfdam": false,
"rollOther": false,
"critOther": false,
"magicdam": false,
"magiceffect": false,
"concentration": false,
"toggleEffect": false,
"ignoreTotalCover": false,
"autoFailFriendly": false,
"autoSaveFriendly": false,
"offHandWeapon": false
},
"magicitems": {
"enabled": false,
"equipped": false,
"attuned": false,
"charges": "0",
"chargeType": "c1",
"destroy": false,
"destroyFlavorText": "reaches 0 charges: it crumbles into ashes and is destroyed.",
"rechargeable": false,
"recharge": "0",
"rechargeType": "t1",
"rechargeUnit": "r1",
"sorting": "l"
},
"exportSource": {
"world": "homebrew",
"system": "dnd5e",
"coreVersion": "10.291",
"systemVersion": "2.1.4"
}
},
"effects": [
{
"label": "Focused Aim",
"icon": "icons/skills/targeting/target-strike-triple-blue.webp",
"changes": [
{
"key": "flags.midi-qol.onUseMacroName",
"mode": 0,
"value": "function.await chrisPremades.macros.focusedAim,preCheckHits",
"priority": 20
}
],
"transfer": true,
"_id": "rzksUWAkBsCf1Eie",
"disabled": false,
"duration": {
"startTime": null,
"seconds": null,
"combat": null,
"rounds": null,
"turns": null,
"startRound": null,
"startTurn": null
},
"origin": null,
"tint": null,
"flags": {
"dae": {
"selfTarget": false,
"selfTargetAlways": false,
"stackable": "none",
"durationExpression": "",
"macroRepeat": "none",
"specialDuration": []
},
"core": {
"statusId": ""
},
"ActiveAuras": {
"isAura": false,
"aura": "None",
"radius": "null",
"alignment": "",
"type": "",
"ignoreSelf": false,
"height": false,
"hidden": false,
"displayTemp": false,
"hostile": false,
"onlyOnce": false
},
"dfreds-convenient-effects": {
"description": ""
}
}
}
],
"_id": "NKmtLsToLZvA6fTZ",
"img": "icons/skills/targeting/target-strike-triple-blue.webp",
"folder": null,
"sort": 700000,
"ownership": {
"default": 0,
"imLxB9KPmJBqVcY5": 3
},
"_stats": {
"systemId": "dnd5e",
"systemVersion": "2.1.5",
"coreVersion": "10.291",
"createdTime":<PHONE_NUMBER>764,
"modifiedTime":<PHONE_NUMBER>001,
"lastModifiedBy": "imLxB9KPmJBqVcY5"
}
}

perhaps an await missing on line 35 at the fromUuid?

Try the latest update.  I did the fix from mobile so I haven't tested it.  The missing await seems right.

All good now.


YoloV3 conversion

Hi all. I am interested in using the YOLOv3 Keras model to ONNX format. It is the one that is from https://github.com/qqwweee/keras-yolo3, which the attempt to convert has been successful. For personal interest, I would like to convert it once more with my own pretrained model. I've attempted to use the yolov3.py API but to no success. My first question is if you have the list of packages and their versions, I believe there might be a few dependencies problems for me. I am also wondering what is the difference between the yolov3.py & test_yolov3.py since yolov3.py suffices my needs. Thanks

This is the command I've used

python yolov3.py /home/lizhong/keras-yolo3/pictures/bus.jpg

And the following are the packages I have installed.

Package                Version

absl-py                0.8.1
astor                  0.8.0
atomicwrites           1.3.0
attrs                  19.3.0
bleach                 1.5.0
cachetools             3.1.1
certifi                2018.8.24
chardet                3.0.4
coverage               4.5.4
cycler                 0.10.0
fire                   0.2.1
gast                   0.2.2
google-auth            1.7.0
google-auth-oauthlib   0.4.1
google-pasta           0.1.8
grpcio                 1.24.3
h5py                   2.10.0
html5lib               0.9999999
idna                   2.8
importlib-metadata     0.23
Keras                  2.1.5
Keras-Applications     1.0.8
Keras-Preprocessing    1.1.0
keras2onnx             1.6.0
kiwisolver             1.1.0
Markdown               3.1.1
matplotlib             3.0.3
more-itertools         7.2.0
numpy                  1.17.3
oauthlib               3.1.0
onnx                   1.6.0
onnxconverter-common   1.6.0
onnxruntime            1.0.0
opencv-python          <IP_ADDRESS>
opt-einsum             3.1.0
packaging              19.2
pathlib2               2.3.5
Pillow                 6.2.1
pip                    19.3.1
pluggy                 0.13.0
protobuf               3.10.0
py                     1.8.0
pyasn1                 0.4.7
pyasn1-modules         0.2.7
pyparsing              2.4.3
pytest                 5.2.2
python-dateutil        2.8.1
PyYAML                 5.1.2
requests               2.22.0
requests-oauthlib      1.2.0
rsa                    4.0
scipy                  1.3.1
setuptools             41.6.0
six                    1.12.0
tensorboard            1.6.0
tensorflow             1.5.0
tensorflow-estimator   1.15.1
tensorflow-tensorboard 1.5.1
termcolor              1.1.0
typing-extensions      <IP_ADDRESS>
urllib3                1.25.6
wcwidth                0.1.7
Werkzeug               0.16.0
wheel                  0.31.1
wrapt                  1.11.2
zipp                   0.6.0

Duplicate of #121 I've also received the similar error, but opset is 10

Can you use keras 2.2.4+ and tensorflow 1.11.0+ ? test_yolov3.py is an end-to-end nightly build test (we run it every day to ensure correctness), but the core part is the same as yolov3.py. You just replace the .h5 file with your own file in test_yolov3.py , then it should work.

Hello, I have tested with test_yolov3.py with yolov3 h5 file from https://github.com/qqwweee/keras-yolo3 but I keep getting the following error. Any advice on this matter?
2019-12-30 13:40:38.481690: I tensorflow/core/grappler/optimizers/auto_mixed_precision.cc:2005] Running auto_mixed_precision graph optimizer
2019-12-30 13:40:38.482199: I tensorflow/core/grappler/optimizers/auto_mixed_precision.cc:1248] No whitelist ops found, nothing to do
2019-12-30 13:40:38.989981: I tensorflow/core/grappler/optimizers/auto_mixed_precision.cc:2005] Running auto_mixed_precision graph optimizer
2019-12-30 13:40:38.990532: I tensorflow/core/grappler/optimizers/auto_mixed_precision.cc:1248] No whitelist ops found, nothing to do
/usr/local/lib/python3.5/dist-packages/keras/engine/saving.py:251: DeprecationWarning: The truth value of an empty array is ambiguous. Returning False, but in future this will result in an error. Use array.size > 0 to check that an array is not empty.
if weight_names:
2019-12-30 13:40:40.373318: I tensorflow/core/grappler/optimizers/auto_mixed_precision.cc:2005] Running auto_mixed_precision graph optimizer
2019-12-30 13:40:40.374380: I tensorflow/core/grappler/optimizers/auto_mixed_precision.cc:1248] No whitelist ops found, nothing to do
2019-12-30 13:40:40.492524: I tensorflow/core/grappler/optimizers/auto_mixed_precision.cc:2005] Running auto_mixed_precision graph optimizer
2019-12-30 13:40:40.494453: I tensorflow/core/grappler/optimizers/auto_mixed_precision.cc:1248] No whitelist ops found, nothing to do
2019-12-30 13:40:40.607255: I tensorflow/core/grappler/optimizers/auto_mixed_precision.cc:2005] Running auto_mixed_precision graph optimizer
2019-12-30 13:40:40.608198: I tensorflow/core/grappler/optimizers/auto_mixed_precision.cc:1248] No whitelist ops found, nothing to do
/usr/local/lib/python3.5/dist-packages/keras/engine/saving.py:292: UserWarning: No training configuration found in save file: the model was not compiled. Compile it manually.
warnings.warn('No training configuration found in save file: '
2019-12-30 13:40:47.909061: I tensorflow/core/grappler/optimizers/auto_mixed_precision.cc:2005] Running auto_mixed_precision graph optimizer
2019-12-30 13:40:47.909947: I tensorflow/core/grappler/optimizers/auto_mixed_precision.cc:1248] No whitelist ops found, nothing to do
2019-12-30 13:40:48.295570: I tensorflow/core/grappler/optimizers/auto_mixed_precision.cc:2005] Running auto_mixed_precision graph optimizer
2019-12-30 13:40:48.296692: I tensorflow/core/grappler/optimizers/auto_mixed_precision.cc:1248] No whitelist ops found, nothing to do
2019-12-30 13:40:48.427660: I tensorflow/core/grappler/optimizers/auto_mixed_precision.cc:2005] Running auto_mixed_precision graph optimizer
2019-12-30 13:40:48.428124: I tensorflow/core/grappler/optimizers/auto_mixed_precision.cc:1248] No whitelist ops found, nothing to do
../../../keras-yolo3/yolo3/../yolov3-tiny.h5 model, anchors, and classes loaded.
E
ERROR: test_yolov3 (main.TestYoloV3)
Traceback (most recent call last):
File "test_yolov3.py", line 81, in test_yolov3
onnx_model = keras2onnx.convert_keras(my_yolo.final_model, channel_first_inputs=['input_1'])
File "/workspace/keras-onnx/keras2onnx/main.py", line 63, in convert_keras
return convert_topology(topology, name, doc_string, target_opset, channel_first_inputs)
File "/workspace/keras-onnx/keras2onnx/topology.py", line 268, in convert_topology
get_converter(operator.type)(scope, operator, container)
File "/workspace/keras-onnx/keras2onnx/_builtin.py", line 591, in convert_tf_reshape
desired_shape=shape_value)
File "/workspace/keras-onnx/keras2onnx/common/onnx_ops.py", line 91, in apply_op_with_output
apply_func(self._scope, ox_inputs, outputs, self._container, operator_name=name, **attrs)
File "/usr/local/lib/python3.5/dist-packages/onnxconverter_common/onnx_ops.py", line 565, in apply_reshape
container.add_node('Reshape', [input_name, desired_shape_name], output_name, op_version=5, name=name)
File "/workspace/keras-onnx/keras2onnx/common/interim.py", line 117, in add_node
raise ValueError('Inputs must be a list of string but get [%s]' % type_list)
ValueError: Inputs must be a list of string but get [<class 'list'>,<class 'str'>]

Ran 1 test in 14.102s
FAILED (errors=1)

Hello, I have tested with test_yolov3.py with yolov3 h5 file from https://github.com/qqwweee/keras-yolo3 but I keep getting the following error. Any advice on this matter?

@mckhang can you pull latest keras2onnx master and onnxconverter-common master and try?


Contribution/Building instructions

Hi,
I and perhaps others would like to contribute to this library. However there are no instructions with regards to building a new version of this package.
Could you please provide/document how to generate/build this package?
In the comments I saw that the classes have been generated using swagger-codegen. I have tried to generate the same classes as in this library using swagger-codegen-cli however the classes I get are quite different from the ones in this library (They depend on Guzzle instead of cURL and I suppose we need cURL instead of Guzzle for BC?).
Maybe it is related to the version of swagger-codegen?
Anyway something like https://help.github.com/en/articles/setting-guidelines-for-repository-contributors would be highly appreciated along with some information on how to build this package.
Also it would be interesting to know more about the timeline with regards to supporting older PHP versions. Currently the docs state that PHP 5.4 and higher is supported. Officially even PHP 7.1 is not even actively supported anymore: https://www.php.net/supported-versions.php
So maybe at some point in the near future this package can drop support for PHP 5.x?
Thanks in advance for your time and effort.

@larrykluger @LarryKlugerDS @MattKingDS @TonyMannDS @jwimberley-ds Would any of you happen to have an answer?
I did notice that when using an old version of swagger-codegen the classes that are generated look more like the ones in this repository. However there are some methods that are not generated, like for example the generateAccessToken() method.
Were the classes generated and edited afterwards (although the comment  block in pretty much every class states that the file should not be edited manually, bc they're generated)? Or am I missing something with regards to generating the client classes?

Hi @4c0n,
Thank you for your questions.
Contributing to the DocuSign eSignature PHP SDK.
Yes, we'd like to enable you and other developers to contribute to the SDK's development.
We're currently using a private fork of the CodeGen tool to generate the SDK from the Swagger file. So today, contributions to most of the SDK can't be provided as pull requests. -- But we do value your comments about the SDK, please submit issues.
We have a plan to update to a public code generation system, please ask your DocuSign support or account representative to add your organization's name and information to ticket DCM-2367.
Unfortunately we don't yet have a schedule for this update.
OAuth Methods
The OAuth methods in the SDK are written by hand, they're not generated via the Swagger file. You're welcome to file issues and/or PRs for them.
PHP version support
I'm not an expert on PHP. Can you provide the top reasons why we should no longer support 7.1 or below? Are there new PHP patterns that we should use that are only supported on versions after 7.1?
Thank you for using DocuSign!

Hi @LarryKlugerDS,
Thanks for your response!
It's very useful. What I was missing mostly in the ApiClient is that yes there is a method generateAccessToken(), but unfortunately no refreshAccessToken() (In my fork I added it, so I'll send a PR for that later).
I noticed that with OpenAPI version 3 it is possible to generate the authentication related code as well and it requires very little changes to the swagger file. I might send a PR for that one soon. It might help, because the the new version has support for defining all of the OAuth2 flows that are available (as far as I could tell).
As far as the PHP support goes:
There were a lot of major changes in version 7, some of them are for example improved strict typing. So with version 7 we're finally capable of using return type declarations. Using type hints for parameters that are primitive types is another important one.
For example in PHP5:
public function returnSomething($parameter)
{
    return $parameter;
}

In PHP7+:
public function returnSomething(string $parameter): string
{
    return $parameter;
}

The latter being a lot less error prone.
The PHP5 version of that method will work fine in PHP7, the other way around not so much.
However since most of the lib is generated it might not make that much of a difference right now.
The new version of swagger-codegen generates a client based on the Guzzle 6 HTTP client which requires PHP 5.5 as a minimum version.
Also since there are no patches at all being made for PHP version 5 it cannot be considered secure anymore, so motivating people to move on to PHP 7 could be a reason on by itself.


Caledar display issue

Using monospace font for calendar tooltip, yet its not spaced properly
module config :
        "tooltip-format": "<big>{:%d %B}</big>\n<tt>{calendar}</tt>",

Any news about this?
I have exactly the same problem.
I've tried several fonts, change the Waybar configuration, change the GTK theme, change the CSS...
Nothing to do, I still have this shifted display on Sway and on Hyprland too.

Hi @Iss-in  and @jlaunay
Kindly share the full clock config block. The reason I'm asking for is, I've installed IBM Plex Mono font and for me it looks good so far
    "clock": {
        "format": "{:%H:%M}  ",
        "format-alt": "{:%A, %B %d, %Y (%R)}  ",
        "tooltip-format": "<big>{:%d %B}</big>\n<tt>{calendar}</tt>",
        "today-format": "{}",
        "format-calendar": "{}",
        "on-scroll": {
                    "calendar": 1
                     }
    },

I installed this font and I have the same problem.

my bad, i totally forgot about this,   I did check again and not sure what the issue was, but it look fine from my side as well
using same tooltip config as mentioned in OG comment

You might faced with the same issue https://github.com/Alexays/Waybar/issues/1874#issuecomment-1349150106
@jlaunay had the same problem


ENH: Add weight support to FamaMacBeth

Add weight support to FamaMacBeth regression

This pull request introduces 2 alerts - view on lgtm.com
new alerts:

1 for Non-callable called
1 for Potentially uninitialized local variable

Comment posted by lgtm.com


Fix nightly clippy lints

Objective

Clippy added new nightly Lints

Solution

Fix those Lints.

Ignored cases
Any Lint that triggered inside the Rendering crates were ignored, as they are about to be replaced by the rendering rework.

I'm going to close as a duplicate of #2934; we can consolidate the work over there.


Challenges schedule

Are there any plans to add the new Sizzle Season Challenges schedule?

yup, they have been added yesterday evening!

@jackssrt The data is available now in schedules.json, and @Inkception is hard at work adding UI to the site. Stay tuned!

Challenges page looks really nice, GJ!


On IBM credential

This is common for chapter 3 (algorithm) and 4 (application). Currently, real quantum computers are accessed in this way.
IBMQ.load_accounts()
backend = IBMQ.get_backend('ibmq_16_melbourne')

I believe this is a somehow older way (?) and do not work anymore, probably should change to the following?
IBMQ.load_account()
provider = IBMQ.get_provider(hub='ibm-q')
backend = provider.get_backend('ibmq_16_melbourne')

This is correct @tbcdebug. Would you like to open a pull request with these changes?

Yes

I've already created a pull request.

Great job @tbcdebug -- I've left you some comments there. Just a couple of things and it's ready to merge.

Closed by #31


Assistant 2.0 not working and Chrome overly saturated

Hi, I'm using Poco F1 with Awaken OS 1.3 and I can't seem to enable Assistant 2.0. I tried all steps outlined in the main page and also from the previous user who reported the issue a while ago (now closed) and still doesn't work.
Also Chrome for some reason is oversaturated. Please help. Thanks

I don't know why on acrrenshots it doesn't show chrome being saturated, but everytime I access it or use it the colors are oversaturated. And i tried changing colors in flags and even my system, still the same

Got it fixed. Seems that a GSuite account was preventing assistant 2.0 from pushing through.


The "v" parameter with version number becomes obligatory for all API …

The "uid" parameter obsolete. Use "id" instead.
The "v" parameter with version number becomes obligatory for all API requests. An error will be returned if the parameter is not sent.
https://vk.com/dev/version_update

Does anybody know when it'll be merged and released?

@mrbrut This PR was only cut 3 days ago. I'll be looking at this ASAP, but probably by the end of the week.

@imaleksandr how is this and #227 different? I havn't yet read the docs, but I'm assuming this PR is the actual fix we want?

oh I see, basically its not different...

@imaleksandr please see #230

this will go with 2.21.0


Add platform keyword to build on M1 Macs

By default, docker builds images based on the underlying OS of the host machine that calls build. New M1 Macs have an arm-based CPU compared to the x86-based CPU of previous Intel Macs.
While most packages have an arm compatible package, zokrates 0.7.7 does not. (Note that zokrates 0.7.10 has a arm-package, although it is not currently available as an image).
Both worker and optimist are built from this image and thus fail to properly run as critical linking libraries are not available. To get around this we explicitly set the platform that these should be built to.
An alternative solution would be to set DEFAULT_DOCKER_PLATFORM, however this Multi-platform build feature requires the semi-experimental docker buildx workflow.

Closing in favour of #404


Use multipart upload API in S3 Move method

This change to the S3 Move method uses S3's multipart upload API to copy
objects whose size exceeds a threshold.  Parts are copied concurrently.
The level of concurrency, part size, and threshold are all configurable
with reasonable defaults.
Using the multipart upload API has two benefits.

The S3 Move method can now handle objects over 5 GB, fixing #886.

Moving most objects, and espectially large ones, is faster.  For
example, moving a 1 GB object averaged 30 seconds but now averages 10.

Signed-off-by: Noah Treuhaft<EMAIL_ADDRESS>

Ignore the documentation build failure.

Moving most objects, and espectially large ones, is faster. For example, moving a 1 GB object averaged 30 seconds but now averages 10.

I thought sub-5GB moves in S3 were atomic and not bound to the object size?

They're atomic in the sense that intermediate state is never visible, but running time is definitely a function of object size.

Current coverage is 52.36% (diff: 0.00%)

Merging #1906 into master will decrease coverage by 10.50%

@@             master      #1906   diff @@
==========================================
  Files           120        120
  Lines         10586      10666     +80
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           6655       5585   -1070
- Misses         3061       4344   +1283
+ Partials        870        737    -133

Powered by Codecov. Last update c810308...6615fff

Looks good, apart from a couple of nits.  I'll need to push this branch to upstream to run the unit tests against S3 before we merge.

@RichardScothern: 63468ef4a85fabb756e799c2534f0df2f3c8167c should address your comments on 6615fff1ca168549e5d561356691bb705c93b15d.

Build is green.  LGTM 🚼


Figura mod incompatability with Elytra

The Figura mod allows for custom avatars via Blockbench program, that program can create models that are grouped and some groups are Keywords that Figura uses to mimic vanilla behavior. What is broken are RightElytra and LeftElytra keywords that as the names suggest mimic parts of the Elytras when Apugli is loaded.
Figura version that is broken is Figura 0.1.0 Pre-4 to Figura 0.1.0 Pre-6
A Figura report on this that has more specific info and an example avatar can be found here: https://discord.com/channels/805969743466332191/975571425295474708/999759885900206191

I'm genuinely unsure as to what may cause this.

It wasn't the code that you all talked about btw.
It's something else that I may need to dive deep into Apugli to fix.

I'll see when I get the time to see what's causing this.

Should be fixed in v1.9.1


Cannot read properties of undefined

Hi
I'm having an issue using the package, I get the error
TypeError: Cannot read properties of undefined (reading 'data')
    at /home/gwendal/Documents/SvelteKit/easyinvoice/node_modules/easyinvoice/dist/easyinvoice.min.js:1:17753
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

My code is this :
var easyinvoice = require('easyinvoice');
var fs = require('fs');

var data = {};

easyinvoice.createInvoice(data, function (result) {
    fs.writeFileSync("invoice.pdf", pdf, 'base64');
});

Hi,
Please try this:
`var easyinvoice = require('easyinvoice');
var fs = require('fs');
var data = {};
easyinvoice.createInvoice(data, function (result) {
fs.writeFileSync("invoice.pdf", result.pdf, 'base64');
});`
The result object contains the pdf. So in your example replace 'pdf' with 'result.pdf'. That should fix it.


Incorrect response time in output and chart?

The calculated response time seems wrong if the intention is to present in milliseconds.
Several tests against urls that I know takes longer than LoadTestToolbox presented makes me think that the calculation of elapsed time is the problem.

Resolved by #16

For the record, the times you are seeing are server response times for the initial request, which can be drastically different from browser rendering times
The other thing to make sure is that you're specifying the protocol (http://example.com vs just example.com)


Migration

Hello,
Its possible to migrate from jQuery Menu Editor 1.1.1? If yes then How?

Hi. Yes, it is posible. In order to migrate, you must take into account the following points. This way, you will be able to make the necessary adaptations and replacements.
The data
The data are very similar. You need to change the attribute "title" for "tooltip"
{
"href":"http://home.com", // href
"icon":"fas fa-home", // icon
"text":"Home",  // text
"target": "_top",  // target (now this is optional)
"title": "My Home", // tooltip,  <=== Attribute name in Javascript Menu Editor
"children": [] // children
}

Equivalents methods

jQuery Menu Editor
Javascript Menu Editor

setData(data)
setArray(data)

getString()
getString()

Javascript Menu Editor is not linked to a form or input element, instead is more flexible and have these events and methods:

onClickDelete(event) and onClickEdit(event)
add(item)
update(item)

External plugin
The jQuery plugin "Bootstrap Icon Picker" is no longer necessary. You can choose your own icon picker; however, my new library, Vanilla Javascript Iconpicker, is currently in development stage and I will release it in the upcoming days.
I hope this has helped you. Feel free to reach out to me via Twitter

Is there any additional or required plugin OR plugin in version? like jQuery version requirement in both.


PathTree Bug(s)

When I try to generate a path tree from a TPS simulation with the code:
tree = ops_vis.PathTree(
    steps[:],
    ops_vis.ReplicaEvolution(replica=0, accepted=True
    )
)
tree.options.css['scale_x']=0.5/len(steps)
tree.options.css['width'] = '200%'
SVG(tree.svg())

where steps is a list of mc steps from multiple save files(the tps simulation is broken across multiple save files). It only shows the step numbers of the last file and an asterisk for all others, as seen in:

While running
step = steps[20]
print step.mccycle

gives:
20

Also, could it be possible to scale the vertical connectors independently?
Because as you can see, above the highlighted try: the width of my trajectories are actually smaller than the connectors. This scaling issue is probably because my original trajectory was taken with a 10x higher save frequency (resulting in 74000 frames in comparison to around 100 for the short tries). It is actually cut off in the above image, this is the full image (without the width scaling):

Lastly, the automatic scaling (without both the width and scale_x option), results in an unreadable image (I first thought I got no output at all):

Last things first: About the scaling: Yes, the problem with trees and very different lengths of trajectories is annoying and I thought about a nice solution, but might come later. Quick about the different for scale_x and width.
scale_x represents the effective pixels between two frames and thus affects the overall size of the figure.
width only affects the output width in the browser. So it does not change the effective number of pixels of the embedded SVG. If you use 'width': 'inherit' it will use the calculated number of pixels of the SVG also in the browser. 100% will rescale the figure to fit, etc...
If you use scale_x the way you do. Then you rescale the real pixels to be more narrow, while the width of the connecting bars is fixed and actually a css property that you can change using Javascript.
I agree that there should be an easy way to change the css of a figure to you liking and I will add that.
Now the first problem of the step: When you use ReplicaEvolution then what happens is, that it starts with the last step you give and get the replica and from there it traces back using the parent property of each sample. It does not use the steps! And I think that is indeed the wrong behaviour, although in most cases it will give you the right behaviour.
In your particular case this may lead to the result you have: Imagine me using only steps[50:60] in the ReplicaEvolution then it will pick the replica from step[59] and trace back beyond step 50 and earlier until there is no .parent for a Sample. When this list is generated we try to figure out which sample was actually generated in which step and since you only have steps 50 to 60 to inspect all samples created at earlier steps will not be known and hence the * is shown.
Now. You said that you split the simulation but step[20] has step number 20. And this is indeed strange so I need to look into what can happen there. I will get back to you.
A short summary if things to do for me:

Easy access to CSS properties
Check ReplicaEvolution or create a StepEvolution generator to really inspect the change after each step. (I think that maybe SampleAncestors and ReplicaEvolution got somehow mixed)
Look into potential bug of step numbers

@sroet Quick question: How do you join all the steps from multiple files. Do you do something like this?
steps = []
for file in files:
   st = Storage(file)
   steps.extend(st.steps)

Can you do
print type(steps)

and try
tree.steps._create_step_sample_list()
SVG(tree.svg())

and see if that changes anything? It seems the list of sample -> step is not updated correctly.
And I forgot this:

Lastly, the automatic scaling (without both the width and scale_x option), results in an unreadable image (I first thought I got no output at all):

This is strange. Maybe you figure is way to big and the browser fails?

@jhprinz
I run
steps = sum([s.steps[:] for s in storages],[])

where storages is generated by:
storages = []
for filename in filenames:
    storages.append(paths.Storage(filename, 'r')

When I run:
print type(steps)

it gives:
<type 'list'>

if I run
tree.steps._create_step_sample_list()
SVG(tree.svg())

After I generated the tree with the code of my first post. It doesn't change anything and gives the same image
If I however make a tree for step[:50] (my storage is split every 25 steps after the first decorrelation of 2 steps), it now know the step numbers of again the last save file(from 27 to 50)
Also, if I run with accepted = False it now knows all the step numbers as can be seen in:


Keymaps that requires holding down "Shift" to trigger such as "!", "?" or "#" are not working

A keymap that requires holding down "Shift" to generate e.g. "!" or "?" characters will not trigger correctly.
For example, this will fail.
{
    "keybindings": {
        "StockWatch": {
            ...
            "<?>": "ToggleShowHelp", // Shift-/
            "<@>": "DummyAction1", // Shift-1
            "<#>": "DummyAction2",  // Shift-3
            ...
        },
    }
}

But this works:
{
    "keybindings": {
        "StockWatch": {
            ...
            "<Shift-?>": "ToggleShowHelp",
            "<Shift-@>": "DummyAction1",
            "<Shift-#>": "DummyAction2",
            ...
        },
    }
}

This modification works fine enough for me to take care of various characters from Shift-1 for "!", Shift-2 for<EMAIL_ADDRESS>Shift-0 for ")" on my keyboard.
if c.len() == 1 => {
            let mut c = c.chars().next().unwrap();
            if modifiers.contains(KeyModifiers::SHIFT) {c = c.to_ascii_uppercase();}
            else if "!@#$%^&*()_+{}|:\"<>?".contains(c) { modifiers.insert(KeyModifiers::SHIFT);}
            KeyCode::Char(c)
        }

I'm not able to reproduce this issue.
I changed the ratatui-counter example to use ? to "ToggleHelp" and it uses / to EnterInsert mode, and it seems to be working fine for me:
https://github.com/ratatui-org/templates/blob/04e586790bf0f00bd8af41184633423aa68946f2/async/ratatui-counter/.config/config.json5#L7-L8

Closing for now, let us know if this is still an issue!


Undefined behavior when dropping Music after mix_quit has been called

If you call mix::quit before dropping a Music, dropping it will trigger undefined behavior and causes a segmentation fault on my system.
This is unacceptable, as this can be caused by safe Rust code.
One solution is to just let the music leak if the library is not initialized anymore.
Another solution is to change the architecture of the library, as was done with rust-sdl2, to be able to tie the lifetime of a music to the lifetime of the sdl2_mixer context.
I haven't checked, but this issue most likely also applies to Chunk and maybe some other types that implement Drop.
Here is a minimal test case:
extern crate sdl2 as sdl;
extern crate sdl2_mixer as mix;

fn main() {
    let _sdl_ctx = sdl::init().everything().unwrap();
    mix::init(mix::INIT_MODPLUG);
    mix::open_audio(mix::DEFAULT_FREQUENCY, mix::DEFAULT_FORMAT, 2, 4096).unwrap();
    // http://modarchive.org/index.php?request=view_by_moduleid&query=96492
    let mus = mix::Music::from_file("sdv_3.mod".as_ref()).unwrap();
    mus.play(0).unwrap();
    ::std::thread::sleep_ms(3000);
    mix::quit();
}

Thanks.
I prefer to change ths architecture of the library.
Can you post the minimal fail code here?

@andelf I edited the original post and added a test case.

:( The code runs ok under my macbook.
sdl_* libs installed by homebrew.

Whether it runs fine for you specifically or not, the fact still remains that it triggers undefined behavior.
It might run fine on some systems, it might crash on others. It might silently corrupt the program state on yet others. Undefined behavior must be eliminated, and it is forbidden in Rust to let safe code trigger it.

I'll try to tie the lifetime of a music to the lifetime of the sdl2_mixer context.

With that last pull request, this issue should be solved and can be closed

With that last pull request, this issue should be solved and can be closed

Alright, I can't reproduce this issue anymore (in fact, it even works without sdl::init() or mix::init() being called), so I'm going to close it.


twitter - bad gateway

Summary:
Logged in with twitter, logged out, just tried login with twitter againgot this
502 - Bad Gateway nginx error
if I hit refresh it takes me to the app

502 Bad Gateway happened because I shut down the server to pull the latest code from GitHub to update and then started up the server again. Does this happen again?


Does Fantasia Append "Front"/"Side" to prompts?

I was wondering whether Fantasia also appends "front" and "side" to their text prompts as a function of view angle? I don't think this was specified in the paper. I assume that it follows Magic3D and Dreamfusion, but just wanted to check.

Yes, see #1 for more details.

Cheers, thanks!
Might be worth making a FAQ so you don't have to answer repeat questions


System panic at execution

I was able to compile on my installation of KISS Linux with cargo build --release and moving the executable to /usr/bin/ but upon execution I get the following error:
2024-11-14T07:05:51.894428Z  INFO bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "Linux  KISS Linux Community", kernel: "6.6.59_1", cpu: "Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz", core_count: "4", memory: "7.5 GiB" }
2024-11-14T07:05:51.959037Z  INFO bevy_render::renderer: AdapterInfo { name: "Mesa Intel(R) UHD Graphics 620 (KBL GT2)", vendor: 32902, device: 0, device_type: IntegratedGpu, driver: "OpenGL", driver_info: "4.6 (Compatibility Profile) Mesa 24.2.5", backend: Gl }
2024-11-14T07:05:52.163000Z  WARN bevy_pbr::ssao: ScreenSpaceAmbientOcclusionPlugin not loaded. GPU lacks support: TextureFormat::R16Float does not support TextureUsages::STORAGE_BINDING.
2024-11-14T07:05:52.163269Z  INFO bevy_winit::system: Creating new window "Sokoban" (Entity { index: 0, generation: 1 })
2024-11-14T07:05:52.170154Z  INFO soukoban_rs::systems::level: Loading levels from files
thread 'Compute Task Pool (3)' panicked at src/systems/level.rs:20:48:
called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }
Encountered a panic in system `soukoban_rs::systems::level::setup_database`!
Encountered a panic in system `bevy_app::main_schedule::Main::run_main`!

Does the program expect to be executed from the source directory or is another issue the source of this error?

Yes, this will happen if you just move the executable.
This is because levels are stored in files in the assert/level folder.
https://github.com/ShenMian/sokoban-rs/blob/17f7f3f344dd61f520f21db8c8569ac7d6fb1e88/src/systems/level.rs#L15
The current design does make it difficult to install directly on Linux.

Ah, makes sense. For reference BrogueCE is another project that provides a nice solution to a similar challenge (although that game is written in C not Rust). If it's aligned for the project at some point I think this could be implemented through either an ENV var or a CLI arg.
The current approach doesn't fit my use case right now and if this changes in the future I'd love to come back to the game.


404 implement new assets

Add new assets for the game !

Codecov Report

Merging #410 (7d4457e) into master (2405f10) will decrease coverage by 0.22%.
The diff coverage is 0.00%.

:exclamation: Current head 7d4457e differs from pull request most recent head 48f50ec.  Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Update diagnostic-settings.md

Proposing moving a warning that was added to the docs page below because of a known issue.
https://learn.microsoft.com/en-us/previous-versions/azure/azure-monitor/app/export-telemetry#diagnostic-settings-based-export
That page is inside the older versions of our App Insights docs and I think this doc is a better location for it to be easily found by customers.

@rboucher
Can you review the proposed changes? Note that the validation warnings are unrelated. A close/reopen of the PR should clear them once they've been resolved in main.
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#reassign: @AbbyMSFT

#sign-off


(Re)activation of prev button

I have a simple carousel with 2 visible items: $carousel.tinycarousel({ infinite: false, animationTime: 400 });
Initially the .prev button is disabled so I can only go from slide 1 to 2 etc...

When I proceed to slide 2, the .prev is enabled correctly (.disable is removed)
However, I can not click on it to go back to slide 1…

So slide 2 is the first slide. I can't go back to 1.
Going to slide 3 I can go back to 2, so from there it works normally..
It works correctly on the last slide: when I reach the end .next is disabled. Going 1 slide back .next is re-enabled again correctly and I can go to the last slide.
My gut-feeling is that the infinite funcitonality is a bit buggy. Maybe there's some index bug (difference between 0-based or 1-based index?)

Should be fixed in 2.1.8 :)

Awesome, thanks Maarten!

thanks


Appstudio update test-annotations-clyb

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-jgvv-on-pull-request-
creating pipelinerun test-annotations-jgvv-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-mxdd-on-pull-request-
creating pipelinerun test-annotations-mxdd-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-xaot-on-pull-request-
creating pipelinerun test-annotations-xaot-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-jihl-on-pull-request-
creating pipelinerun test-simple-build-jihl-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-jpia-on-pull-request-
creating pipelinerun test-simple-build-jpia-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-gjnx-on-pull-request-
creating pipelinerun test-annotations-gjnx-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-gsnx-on-pull-request-
creating pipelinerun test-simple-build-gsnx-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-izee-on-pull-request-
creating pipelinerun test-simple-build-izee-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-igaw-on-pull-request-
creating pipelinerun test-simple-build-igaw-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-gvay-on-pull-request-
creating pipelinerun test-simple-build-gvay-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-gqbk-on-pull-request-
creating pipelinerun test-annotations-gqbk-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-lbhf-on-pull-request-
creating pipelinerun test-annotations-lbhf-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-qvet-on-pull-request-
creating pipelinerun test-annotations-qvet-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-umup-on-pull-request-
creating pipelinerun test-annotations-umup-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-pzcq-on-pull-request-
creating pipelinerun test-annotations-pzcq-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-mbrb-on-pull-request-
creating pipelinerun test-simple-build-mbrb-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-xtgf-on-pull-request-
creating pipelinerun test-annotations-xtgf-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-yoht-on-pull-request-
creating pipelinerun test-annotations-yoht-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-pjiw-on-pull-request-
creating pipelinerun test-annotations-pjiw-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-ygyv-on-pull-request-
creating pipelinerun test-simple-build-ygyv-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-kpke-on-pull-request-
creating pipelinerun test-annotations-kpke-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-ckox-on-pull-request-
creating pipelinerun test-simple-build-ckox-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-xtci-on-pull-request-
creating pipelinerun test-annotations-xtci-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-xosv-on-pull-request-
creating pipelinerun test-simple-build-xosv-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-izai-on-pull-request-
creating pipelinerun test-annotations-izai-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-pmki-on-pull-request-
creating pipelinerun test-simple-build-pmki-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-fohw-on-pull-request-
creating pipelinerun test-annotations-fohw-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-pyqq-on-pull-request-
creating pipelinerun test-annotations-pyqq-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nzyu-on-pull-request-
creating pipelinerun test-simple-build-nzyu-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-bxtt-on-pull-request-
creating pipelinerun test-simple-build-bxtt-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-phhr-on-pull-request-
creating pipelinerun test-simple-build-phhr-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-smhg-on-pull-request-
creating pipelinerun test-simple-build-smhg-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nycf-on-pull-request-
creating pipelinerun test-simple-build-nycf-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-bkgt-on-pull-request-
creating pipelinerun test-annotations-bkgt-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-opmr-on-pull-request-
creating pipelinerun test-annotations-opmr-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-wgvq-on-pull-request-
creating pipelinerun test-simple-build-wgvq-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-qfje-on-pull-request-
creating pipelinerun test-simple-build-qfje-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-qzgm-on-pull-request-
creating pipelinerun test-simple-build-qzgm-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-kvjs-on-pull-request-
creating pipelinerun test-simple-build-kvjs-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-qlwi-on-pull-request-
creating pipelinerun test-annotations-qlwi-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-qezd-on-pull-request-
creating pipelinerun test-simple-build-qezd-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-wfdk-on-pull-request-
creating pipelinerun test-simple-build-wfdk-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-uwwa-on-pull-request-
creating pipelinerun test-annotations-uwwa-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-owhs-on-pull-request-
creating pipelinerun test-simple-build-owhs-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-pcyu-on-pull-request-
creating pipelinerun test-annotations-pcyu-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-yjrl-on-pull-request-
creating pipelinerun test-annotations-yjrl-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-taux-on-pull-request-
creating pipelinerun test-simple-build-taux-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-fuha-on-pull-request-
creating pipelinerun test-simple-build-fuha-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-onzg-on-pull-request-
creating pipelinerun test-simple-build-onzg-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-wznz-on-pull-request-
creating pipelinerun test-simple-build-wznz-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-kzfl-on-pull-request-
creating pipelinerun test-simple-build-kzfl-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-knyw-on-pull-request-
creating pipelinerun test-simple-build-knyw-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-wipu-on-pull-request-
creating pipelinerun test-simple-build-wipu-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-plnr-on-pull-request-
creating pipelinerun test-annotations-plnr-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-eukh-on-pull-request-
creating pipelinerun test-annotations-eukh-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-efea-on-pull-request-
creating pipelinerun test-simple-build-efea-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-fglt-on-pull-request-
creating pipelinerun test-simple-build-fglt-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-andp-on-pull-request-
creating pipelinerun test-annotations-andp-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-cvzf-on-pull-request-
creating pipelinerun test-simple-build-cvzf-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-acga-on-pull-request-
creating pipelinerun test-annotations-acga-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-ylok-on-pull-request-
creating pipelinerun test-simple-build-ylok-on-pull-request- in namespace build-e2e-lvzu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI/test-annotations-clyb-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
5 seconds
init

✅ Succeeded
13 seconds
clone-repository

✅ Succeeded
7 seconds
sast-snyk-check

✅ Succeeded
42 seconds
build-container

✅ Succeeded
49 seconds
deprecated-base-image-check

✅ Succeeded
23 seconds
inspect-image

✅ Succeeded
46 seconds
clamav-scan

✅ Succeeded
11 seconds
clair-scan

✅ Succeeded
7 seconds
sbom-json-check

✅ Succeeded
5 seconds
show-sbom

✅ Succeeded
6 seconds
show-summary


TextInputMask and keyboardType does not work with the floatLabel property.

KeyboardType of React Native and TextInputMask from the react-native-masked-text library does not work with the Item component and the Label float property. Any solution or option to mask with the floatLabel property?

Hi @luka-rmar , you can try this solution. Follow here. Let us know if the issue still persists.
import React, {useState} from 'react';
import {Input, Item, Label, Text, View} from 'native-base';
import {MaskService, TextInputMaskOptionProp} from 'react-native-masked-text';

// generates an object containing the input required properties (value and onChange) and handles state
const useInputState = (initialValue?: string) => {
  const [value, onChange] = useState(initialValue);
  return {value, onChange};
};

// converts the value using the mask parameters
const mask = ({value = '', onChange}, type: string, options?: TextInputMaskOptionProp) => ({
  // the value is converted to a mask so it is displayed properly with the <Input /> component
  value: MaskService.toMask(type, value, options),
  // when the value is modified, it is converted back to its raw value
  onChangeText: newValue => onChange(MaskService.toRawValue(type, newValue, options).join('')),
});

const component = () => {
  const input = useInputState();
  const masked = mask(input, 'credit-card');

  return (
    <View>
      <Item floatingLabel>
        <Label>card number</Label>
        <Input maxLength={19} {...masked} keyboardType='number-pad' />
      </Item>
      <Text>Actual value: {input.value}</Text>
    </View>
  );
};

export default component;

Hi @luka-rmar , closing for now due to inactivity. Let us know if the issue still persists.


No type error when setting an unknown property of a JSX element

Bug Report
I've augmented solid-js's JSX.IntrinsicElements with new intrinsic elements made within my solid-js-consuming application.
When I write an unknown prop manually (not with spread as detailed in https://github.com/microsoft/TypeScript/issues/18801), I do not get a type error.
https://user-images.githubusercontent.com/297678/104986944-4a9c7c00-59c9-11eb-9a24-24edb1dd8617.mp4
🔎 Search Terms
typescript no error on unknown prop
🕗 Version & Regression Information
Not sure when this happened, but I've been trying unsuccessfully to import {JSX} into particular files to as not to clash with React's global JSX definitions, but because import {JSX} does not work (https://github.com/microsoft/TypeScript/issues/41813), I've since started trying to use the new @jsxImportSource feature as comments inside my files.
So far, I have gotten types to appear using per-file @jsxImportSource comments, and there are no other global JSX types in those files (I have segregated React JSX code from Solid.js JSX code using Project References and placing the two forms of files in separate projects with their own tsconfig to ensure only certain types are available to each group of files).
So, I'm not sure, but it could be that I'm one of the few people testing unknown waters in TypeScript, and hitting this issue.
I have not tried with an older version of TypeScript, because @jsxImportSource doesn't work there, and import {JSX} has never worked for JSX markup (#41813).
⏯ Playground Link
I tried to recreate the issue in playground, but due to https://github.com/microsoft/TypeScript-Website/issues/1427, @jsxImportSource comments to not work in the playground, so I can't reproduce a small version of my environment.
The following is my attempt to try @jsxImportSource just to get started, but no luck (same example from https://github.com/microsoft/TypeScript-Website/issues/1427):
playground
I'll see if I can make a reproduction in a repo...
💻 Code
As you see in the video, I can hover on an unknown prop, and TypeScript will infer the type of the prop as whatever value I have set it to.
For example, in the next video I changed the value to a number, and now the type shows up as a number instead of a function:
https://user-images.githubusercontent.com/297678/104987468-a9aec080-59ca-11eb-83ed-11f802b4d8ba.mp4
I have double checked that the type supplied to JSX.IntrinsicElements does not contain an index signature. There are only specific properties defined in the type of the video's timeline-scrubber.
🙁 Actual behavior
It infers unknown props.
🙂 Expected behavior
It should give a type error.

You forgot to provide example code that allows to reproduce this issue.

You forgot to provide example code that allows to reproduce this issue.

I believe that attributes with - in them are exempt from type-checking. @RyanCavanaugh knows more, but this was probably put in place to accommodate data- attributes.

I believe that attributes with - in them are exempt from type-checking. @RyanCavanaugh knows more, but this was probably put in place to accommodate data- attributes.

The rule here is that properties are allowed to be excess if their names wouldn't be legal variable names. This was the most-agnostic thing we could think of that didn't just allow anything, yet still allowed the entire family of data- and aria- properties to be provided in a certain framework whose name I dare not speak in current company.
Once we have some way of representing those keys in the type system, we'll remove that rule, so duping to #26797

The rule here is that properties are allowed to be excess if their names wouldn't be legal variable names. This was the most-agnostic thing we could think of that didn't just allow anything, yet still allowed the entire family of data- and aria- properties to be provided in a certain framework whose name I dare not speak in current company.
Once we have some way of representing those keys in the type system, we'll remove that rule, so duping to #26797

@RyanCavanaugh How exactly does this issue have to do with https://github.com/microsoft/TypeScript/pull/26797 (which is closed in favor of the merged #44512)?
I still see the same (bad) behavior here.
We should be adding all attribute types we need (to JSX), and erroring on unknown ones as a default. Someone can easily add an index signature for data-* or aria-* attributes to catch all of them.
Can you please re-open this?

That will be great. At the same time, if that breaks people, looks like the fix is easy with template literal types:
type O = Record<`data-${string}`, number>

const o: O = {
  'data-foo': 123, // ok
  foo: 123, // error (good)
}

playground


cleanup useless check in mirror test helper funcion 'CreateEmptyMirrors'

Quick cleanup of mirror testhelper function as requested here https://github.com/k8snetworkplumbingwg/ovs-cni/pull/227#discussion_r979462642
If createEmptyMirror executed without an error, it's safe to assume that mirror is really in ovsdb Mirror table.

/retest
/lgtm
/approve

@Ks89 one of the mirror tests seems flakey, would you please look into it?
{ Failure /tmp/src/github.com/k8snetworkplumbingwg/ovs-cni/tests/mirror_test.go:86
Expected
    <string>: 09:02:10.934759 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 8, seq 1, length 64

to contain substring
    <string>: IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo reply
/tmp/src/github.com/k8snetworkplumbingwg/ovs-cni/tests/mirror_test.go:102}

We cannot reproduce this error in our environment, but it's probably related to a slower VM for kubevirtci.
We tried to increase the timeout from 10s to 30s.

/retest

/lgtm
Thanks!

/release-note-none


Move Runtime Transactions to Separate Package

There's too much namespace overlap.

Let's move the service interface to a new home instead.


ID for the user on Google's side

Is there a way to identify the Google user that a request comes from? We need to be able to persist some state, which will be specific to the Google user.
To give some context:
2 Google users could complete account linking using the same user in our cloud.
How can we easily identify which user this was?
Google User 1 <----
                  |
                  |----> Our user
                  |
Google User 2 <----

Note: We're unable to do modifications to the schema of our access token.

You can't identify the Google user. You get an access token that relates to the account on your side. You'd need to have two user accounts, one for each user, to identify the request as you'd want.

@Fleker Just to give some more context - this is for handling disconnect. For example, if 2x Google users have linked with the same account, we don't want to stop sending state updates when user 1 unlinks, if user 2 is still linked.
However, 2 users/accessTokens is not currently possible on our side for this scenario. It's possible now for 2x Google users to complete account linking with the same account on our side - there's nothing to prevent this. For example, you could have 2 people in the same household, who want to control their devices, but use their own Google account. I think that's a realistic scenario.
Also, a related question, we have a scenario like this, and send state updates. The same agentUserId would apply to both Google users.

This is a similar question to #246, which would ideally consist of an OAuth system that would surface different refresh and access tokens to different Google accounts connected to a single user account.


Fix IPv6 adding prefix route

Adds flag noprefixroute to IPv6 address, as adding /64 route steers any cross-node pod traffic.
Fixes #28327
Add flag `noprefixroute` to IPv6 address

cc @cilium/loader

@CallMeFoxie Sorry, but I'll have to close this PR as it's made directly against the 1.14 release branch. We require patches to go through main first, where they'll be picked up by our backport process that puts them in the release branch. As such, please reopen this PR against main.
Also, please elaborate as much as possible in your commit message on what exactly this one-liner fix accomplishes. GH issue references are difficult to follow for someone reading commit logs in a terminal.


Should associate sdf::Element with XPath

Combination of #226 and #533
\cc @aaronchongth @seancurtis-tri

Closed by #548 (given that XPath is assigned to content-parsed sdf::Elements, not just upon errors)


Using and/or wrapped in parenthesis is not working

Hi!
Trying to build a very simple expression in the Demo section of https://ericsmekens.github.io/jsep/, but it throws an error, as if I'm missing a closing ):

Is this expected? I was planning to use jsep to build expressions like the following:
(x > 4 and w == "hey") or (x <= 4 and w == "hello")

@mateusmoury - you just have to add and (and or) as custom binary operators. The source code shows the default operators (in your example, &&)


Can maps support custom cursor style?

What problem does this feature solve?
most of series support to set cursor style but map,Can map support custom cursor style?
like this:
series:[{
  type: 'map',
  data: [
    {item:'aa', itemStyle:{cursor:'move'}},
    {item:'bb', itemStyle:{cursor:'pointer'}},
    {item:'bb', itemStyle:{cursor:'none'}},
  ]
}]

What does the proposed API look like?
series

Similar to: #10584 graph series


Make parent configurable

Make parent configurable, so it will work in apps that use a model other than Team for the endpoints and webhook issuing models

@dansingerman Sorry, I took too long to merge some stuff from @petekeen-cf and now this PR is conflicting. Do you mind resolving the conflicts?

@dansingerman Sorry, I took too long to merge some stuff from @petekeen-cf and now this PR is conflicting. Do you mind resolving the conflicts?

I think I have resolved them locally, but I have a failing test, that I don't think the merge introduced: in Webhooks::Outgoing::IssuingModel , endpoints_listening_for_event_type? is called as an instance method:
if team.endpoints_listening_for_event_type?(event_type)

but it's defined in Webhooks::Outgoing::TeamSupport as a class method, so I get this failing test:
Error:
WebhooksSystemTest#test_team_member_registers_for_webhooks_and_then_receives_them_on_macbook_pro_15_inch:
NoMethodError: undefined method `endpoints_listening_for_event_type?' for #<Team id: 9889, name: "Your Team", slug: nil, created_at: "2022-07-26 07:36:46.715991000 +0000", updated_at: "2022-07-26 07:36:46.715991000 +0000", being_destroyed: nil, time_zone: nil, locale: nil>
    test/factories/users.rb:17:in `block (4 levels) in <main>'
    test/system/webhooks_system_test.rb:6:in `setup'

I guess I can fix that here, but want to check I'm not missing something? Not sure why the CI is passing with this failing test, so that's also a concern.

@dansingerman I had to revert the other PRs, so chances are this will merge cleanly now.


Seeking Solutions for Abnormal VAT Vertex Animation Behavior in Gamma Space

I found that the VAT vertex animation behaves abnormally under Gamma space. I tried adding GammaToLinear before inputting the vertex offset, but it didn't solve the problem. Does anyone who has encountered a similar situation have any suggestions or ideas to offer?

I should also mention that I used the Unity Editor tool to convert the VAT texture to the EXR format to prevent texture compression.

A bit late, but in case this is still relevant or someone else encounters it: Unity's texture importer clamps negative values when working in Gamma space. This has been a know issue for years, see for example this thread on their forums.
This doesn't affect render targets created in code, such as used by this tool, but it will once you convert the texture and import it as a regular texture like you did.


Show union of supported types when completing overload

TypeScript Version:  2.7.0-dev.20171025
Code
interface Abc {
    abc: number
}

interface Xyz {
    xyz: number
}

declare function foo(x: Abc);
declare function foo(x: Xyz);

foo({
    |
})

Trigger completions at |
Expected behavior:
Suggestions for both abc and xyz are returned since either version of overload could apply
Actual behavior:
Only a completion for abc is returned.
// cc @octref

Perhaps the more interesting case is:
interface Abc {
    abc: number
}

interface Xyz {
    xyz: number
}

declare function foo(x: Abc);
declare function foo(x: Xyz);

foo({
    x|
})

In this case, no suggestions are show because we map the argument type to Abc


UFormGroup error state doesn't load css classes

Version
@nuxthq/ui: 2.50
nuxt: v3.6.1
Reproduction Link
https://stackblitz.com/edit/nuxtlabs-ui-3bkhpx?file=app.vue,package.json
Steps to reproduce
Look at  UInput
What is Expected?
UInput should load ring-red-500 dark:ring-red-400 focus:ring-2 focus:ring-red-500 dark:focus:ring-red-400 classes but they does not exist. Framework properly adding those classes, but those classes does not load.

What is actually happening?

The problem is that tailwind doesn't load this classes, when I add some span anywere in the project, everything works fine:
      <span
        class="ring-red-500 dark:ring-red-400 focus:ring-2 focus:ring-red-500 dark:focus:ring-red-400"
      ></span>

The issue here is that the red color for the Input hasn't been safelisted as there is no such code as <UInput color="red" />. We should safelist it by default I guess.

For now, you can safelist the red color manually in your nuxt.config.ts:
ui: {
    safelistColors: ['red']
}


Are coroutines cancellable?

Hi @lewissbaker,
this is more of a question, since you seem to be well aware about how C++ coroutines work.
We recently talked about cancellation of coroutines for Rust at https://trio.discourse.group/t/structured-concurrency-in-rust/73. Thereby we came to the conclusion that the requirements for a synchronous destructor (which allows for immediate cancellation) makes it hard to implement some abstractions, e.g. over IOCP operation in windows. Most other coroutine frameworks (e.g. async functions in Javascript, C# or Kotlin) are not cancellable, and could wrap those operations. Now I was wondering how C++ behaves here.
As far as I e.g. saw in the source code for https://github.com/lewissbaker/cppcoro/blob/master/lib/async_manual_reset_event.cpp the coroutines here are not cancellable. Otherwise if a waiter would be cancelled, the setter would deal with a dangling pointer. Is that generally the case, that the coroutines - either in C++ in general or this repository - have run-to-completion semantics?
I have seen that the C++ specification specifies a destroy() method on the coroutine frame, which can be called when the coroutine is suspended as far as I understand. This would also imply some kind of synchronous destruction for me. Is the intention here that there are different classes of coroutines? Ones like task, which are not cancellable, and ones like generator which are cancellable?

Within cppcoro there are two flavours of cancellation that are used with C++ coroutines.
The first is the generator model. This is where a producer suspends after producing a value and resumes the consumer which then has the decision of whether to ask for the next value, resuming the producer, or to cancel the generator. When the generator is cancelled it calls the .destroy() method on the handle which synchronously calls the destructors of all in-scope variables, cleaning up any resources. In this model the consumer is active and the producer is suspended.
The second model occurs when the consumer is currently suspended waiting for the producer to produce a value. In this model the consumer cannot actively perform an action to interrupt/cancel the producer. Instead, the producer passes a cancellation_token into the operation which can be used to communicate a request to cancel/stop the operation. The producer can register a callback with the cancellation_token to allow it to actively interrupt the operation if cancellation is requested.
With this model, as the consumer is suspended waiting for the producer, there needs to be some other concurrent operation that is able to actively request cancellation. Once cancellation is requested, the producer is interrupted but will still run to completion, hopefully in a timely manner. Once the producer completes the consumer is resumed, possibly with kind of result that indicates it was cancelled.
While the second model allows the producer to perform some asynchronous cleanup, the use of .destroy() to implement the first model means that it cannot perform asynchronous cleanup operations.
I have been exploring some alternatives that would allow an async_generator to perform async cleanup but it involves introducing another asynchronous operation that can be used to wait until cleanup completes after the destructor of the generator signals a request to cancel. See https://github.com/lewissbaker/cppcoro/blob/async_streams/test/async_stream_tests.cpp for an example.
I've also been exploring some ideas for extending the C++ coroutines language feature to incorporate async cleanup / async RAII patterns. There is some early ideas here https://github.com/lewissbaker/papers/issues/4 but I've also been exploring some other ideas as well.


Start markdown

This is my first header using markdown
It's a very exciting experience working with this language
Very easy to get and user friendly

Adding this project to the github......
$ git add index.md && git commit -m 'My first markdown project' && git push

[x] The process and github tests are successful
[x] The assignment has been checked and it exists
[ ] An error occurred

Working with markdown


WIP: Fallback to CPU for Parquet reads with _databricks_internal columns [databricks]

When performing a Delta Lake MERGE operation on Databricks, a query runs that relies on receiving valid data from computed columns such as _databricks_internal_edge_computed_column_row_index and _databricks_internal_edge_computed_column_skip_row in the Parquet read.
For example:
+- FileScan parquet [country#755,_databricks_internal_edge_computed_column_row_index#963L] Batched: true, DataFilters: [], Format: Parquet, Location: TahoeBatchFileIndex(1 paths)[file:/tmp/myth/delta/corpus], PartitionFilters: [], PushedFilters: [], ReadSchema: struct<country:string,_databricks_internal_edge_computed_column_row_index:bigint>

These columns obviously do not exist if we are reading the files on GPU so we need to fall back to CPU in this case.
This PR is still WIP because there are no tests yet.

build

build

I still plan on making the shim change, but tests are now passing, and this could be merged as is for 22.08 with a follow-up issue to use shims in 22,10.

I filed https://github.com/NVIDIA/spark-rapids/issues/6279 for the follow-up issue


Document Metric and Tagging Conventions

Overview
While reviewing the current code and reading up and metrics, events, tagging and such, it become clear that we'll need to have some structure and conventions and around how we name and tag metrics (and possible events, etc...). Without any structure or conventions our naming could become difficult to understand which metrics are which and what their meaning is.
Examples of some metrics are unique_users, or even well-named and scoped metrics like vmstats.atom_count. Here is the metric summary of it: https://app.datadoghq.com/metric/summary?filter=vmstats.at&metric=vmstats.atom_count.
Questions that I can't answer are, is this the atom count in the cc, the watcher or the watcher-info? Tags can help answer this question, but not yet. Unfortunately the relevant tags are: application:watcher, application:watcher_info and application:child_chain and this metric has been tagged with all 3.

a minor topic and no document is needed. closing this ticket.reference https://github.com/omisego/elixir-omg/pull/1327 for more info.


OModal: Props passed to OModal are not reflected when dynamically changed.

Overview of the problem
Oruga version: [0.8.5]
Vuejs version: [3.4.20]
OS/Browser:
Windows 10 / Chrome 122.0.6261.95 (64bit)
Description
Props passed to OModal are not reflected when dynamically changed.
Steps to reproduce
See this StackBlitz:
https://stackblitz.com/edit/vitejs-vite-spyfnj
(Click "To OModal problem")
Expected behavior
Props passed to OModal are reflected when dynamically changed.
Actual behavior
Props passed to OModal are not reflected when dynamically changed.
(definitely for width and rootClass.)

@mk-startialab Thank you for pointing this out!
Firstly: Surely the width property can be changed to be reactive.
Second: I think that the class properties not being reactive is a bigger issue. It looks like no class property for any component is reflected when dynamically changed.
Was this reactive before 0.8?

@mlmoravek
Hmm... you are right, I think there are no class properties reflected reactively, even prior to version 0.8.
And I understand that it is a very big issue, but still I would like at least the rootClass to be the only one that changes reactively.
There are workarounds, such as using wrapped div tags, but in order for the style of the component to change reactively, it would be simpler as a component if the rootClass could change reactively if possible.
(However, if rootClass can change reactively, we can expect requests to do the same for other classes, and as I mentioned above, there are workarounds, so my opinion is merely "It would be more organized if that were the case.")

@mlmoravek Thanks a lot, and I understand.

For now, as a workaround, you can add a :key property with the same value as your :rootClass property to force a rerender of the component every time your rootClass changes.
Oh, it's a good information! I'll give it a try.

Close.

@mlmoravek

For now, as a workaround, you can add a :key property with the same value as your :rootClass property to force a rerender of the component every time your rootClass changes.

The workaround worked great.
Thank you so much!


Support external cache location

If a user is running pack locally, or perhaps wants to do a very dangerous thing and share a cache across multiple platforms, this should be possible.  If <platform>/maven exists, it should be used for the cache.

Cannot accomplish with specification.