Cannot load a SVG from XAML

According to your doc (https://github.com/luberda-molinet/FFImageLoading/wiki/SVG-support), one should write
Source="{Binding image.svg, Converter={StaticResource SvgImageSourceConverter}}"

But this just does not work. Specifying image.svg within the binding will look for an object image and bind to its property svg. This just cannot work.
Even if that's obvious, SvgImageSourceConverter needs to be loaded. Tried following:
    ...
    xmlns:ffimageloading="clr-namespace:FFImageLoading.Forms;assembly=FFImageLoading.Forms"
    xmlns:svg="clr-namespace:FFImageLoading.Svg.Forms;assembly=FFImageLoading.Svg.Forms"
    ...>

    <ContentPage.Resources>
        <ResourceDictionary>
            <svg:SvgImageSourceConverter x:Key="svgImageSourceConverter" />
        </ResourceDictionary>
    </ContentPage.Resources>

    ...
    <ffimageloading:CachedImage Source="{Binding image.svg, Converter={StaticResource svgImageSourceConverter}}" />

Tried with {Binding 'image.svg', ... but does not help either.
Only way to get it working is to give the CachedImage a name and specify the source from code behind (then facing #522 of course).
As you see, I'm using CachedImage. From the doc it's not clear whether the converter could be use with a standard Image instead but it does not.

Same issue, only works with Binding

Same problem here.
With Binding Source, declared on code, works fine, but it doesn't work if I put directly like "Binding test.svg"

Updated: I just updated the nuget and now SVG doesn't work neither if I declare the binding property nor the file name.

There was a typo on wiki page, fixed it. I added SvgCachedImage for simpler usage (you don't need to use converters with it):
<?xml version="1.0" encoding="UTF-8"?>
<ContentPage xmlns="http://xamarin.com/schemas/2014/forms" xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" x:Class="FFImageLoading.Forms.Sample.SvgSamplePage"
		xmlns:xamvvm="clr-namespace:Xamvvm;assembly=Xamvvm.Forms"
		xmlns:ffimageloading="clr-namespace:FFImageLoading.Forms;assembly=FFImageLoading.Forms"
		xmlns:fftransformations="clr-namespace:FFImageLoading.Transformations;assembly=FFImageLoading.Transformations"
		xmlns:ffimageloadingsvg="clr-namespace:FFImageLoading.Svg.Forms;assembly=FFImageLoading.Svg.Forms"
		Title="SVG">

	<ContentPage.Resources>
		<ResourceDictionary>
	  		<ffimageloadingsvg:SvgImageSourceConverter x:Key="SvgImageSourceConverter"></ffimageloadingsvg:SvgImageSourceConverter>
		</ResourceDictionary>
	</ContentPage.Resources>

	<ContentPage.Content>
		<StackLayout>

			<!-- FIRST APPROACH: -->
			<ffimageloadingsvg:SvgCachedImage WidthRequest="200" HeightRequest="200" Source="sample.svg"/>

			<!-- SECOND APPROACH: -->
			<ffimageloading:CachedImage WidthRequest="200" HeightRequest="200"
				Source="{Binding Source, Converter={StaticResource SvgImageSourceConverter}}">
			</ffimageloading:CachedImage>

		</StackLayout>
	</ContentPage.Content>
</ContentPage>

https://github.com/luberda-molinet/FFImageLoading/commit/635faa58ddff365f87ba8656c7dd4f2d0d8328e7 should fix this.


Update Docs: correct form_invalid descriptions

Change form_invalid description under both UpdateView and CreateView:
From:
"...when a valid form submission occurs..."
To:
"...when an invalid form submission occurs..."

Thanks!


Reachable nodes vs routable nodes

It would be nice to have a mode that could require things like poe skip, HSS skip, D7 key without magnet glove, but only if there's also a mode that doesn't require tricks you have to spend a bunch of time practicing. IIRC the logic allows for those things right now but doesn't require any of them.
Some prenodes in the randomizer should be marked as "hard", meaning that the logic knows you can do them, but will never require you to do them. The former will be used for forbid nodes and softlock checks, and the latter will be used for item placement. Examples of "hard" nodes include poe skip, HSS skip, magnetless D7, and clearing Moosh pits with cape only.

The difficulty here is that if something is technically doable, then it has to be in the logic, or else doing it is a sequence break that can lead to softlocky problems. So the randomizer needs to keep track of two graphs—what can be done, and what the player is expected to be able to do. Which makes me wonder if what I said about the currently "allows but doesn't require" behavior is true.

Other things that aren't actually "hard" but are "dangerous" would also fall into this category, like using consumable items like bombs as your only way to remove bushes.

Implemented in dev branch; will be released in 1.4.


optimize: Saga SpringBeanServiceInvoker support switch json parser

Ⅰ. Describe what this PR did
Saga SpringBeanService invoker support switch json parser.
It was hard code with Fastjson.
Ⅱ. Does this pull request fix one issue?
#3512
Ⅳ. Describe how to verify it
client {
  rm {
    ...
    sagaJsonParser = jackson
    ...
  }
}

or
<bean id="dbStateMachineConfig" class="io.seata.saga.engine.config.DbStateMachineConfig">
    ....
    <property name="sagaJsonParser" value="jackson"></property>
    ....
</bean>

Ⅴ. Special notes for reviews

Codecov Report

Merging #3513 (21dd1f2) into develop (e4c0683) will increase coverage by 0.04%.
The diff coverage is 33.33%.

@@              Coverage Diff              @@
##             develop    #3513      +/-   ##
=============================================
+ Coverage      51.68%   51.72%   +0.04%
- Complexity      3394     3397       +3
=============================================
  Files            621      621
  Lines          20589    20579      -10
  Branches        2564     2567       +3
=============================================
+ Hits           10641    10645       +4
+ Misses          8886     8871      -15
- Partials        1062     1063       +1

Impacted Files
Coverage Δ
Complexity Δ

.../saga/statelang/parser/impl/JacksonJsonParser.java
46.87% <28.57%> (-4.98%)
5.00 <1.00> (+1.00)
:arrow_down:

...ata/saga/statelang/parser/impl/FastjsonParser.java
43.75% <37.50%> (-6.25%)
5.00 <1.00> (+1.00)
:arrow_down:

...r/src/main/java/io/seata/server/UUIDGenerator.java
33.33% <0.00%> (-44.45%)
2.00% <0.00%> (-1.00%)

...java/io/seata/rm/datasource/DataSourceManager.java
14.63% <0.00%> (-9.76%)
3.00% <0.00%> (-1.00%)

...n/src/main/java/io/seata/common/util/IdWorker.java
77.08% <0.00%> (-6.25%)
11.00% <0.00%> (-1.00%)

...n/java/io/seata/rm/datasource/DataSourceProxy.java
42.18% <0.00%> (-4.69%)
11.00% <0.00%> (-2.00%)

...io/seata/core/rpc/netty/AbstractNettyRemoting.java
13.42% <0.00%> (-1.35%)
5.00% <0.00%> (ø%)

...tasource/sql/struct/cache/MysqlTableMetaCache.java
82.35% <0.00%> (-1.18%)
10.00% <0.00%> (-1.00%)

...ery/registry/consul/ConsulRegistryServiceImpl.java
1.85% <0.00%> (+0.08%)
1.00% <0.00%> (ø%)

...rage/redis/store/RedisTransactionStoreManager.java
64.38% <0.00%> (+0.45%)
38.00% <0.00%> (+1.00%)

... and 9 more

Please modify the 1.5.0.md


If leader is disabled before a unit is disabled, and the leader is restarted, leader shows incorrect $state

time=0

leader is online
unit is online, state=ready

time=1

leader is turned off

time=2

unit is turned off

time=3

leader is turned back on. Still shows unit is in state ready.

Solutions

Periodically send a job's state to leader (every few minutes or so?)


Can't update message

By using the REST API PUT /v3/conversations/{conversationId}/activities/{activityId} , I always encounter this error when trying to update an existing message:
{
    "error": {
        "code": "BotNotInConversationRoster",
        "message": "The bot is not part of the conversation roster."
    }
}

The request body:
{
	"type": "message",
	"text": "New message "
}

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

ID: 293d28d8-bd82-299a-05b3-4f798e485542
Version Independent ID: 2f747d61-5ff7-be26-d55d-fdc715f4293d
Content: Update and delete messages sent from your bot - Teams
Content Source: msteams-platform/bots/how-to/update-and-delete-bot-messages.md
Product: msteams
GitHub Login: @WashingtonKayaker
Microsoft Alias: anclear

@clearab please help

@jerry-le Could you please share some piece of code you are trying? Also, here is a similar issue reported few days back. Could you please check if your issue is similar to this?

Thanks, Gousia.
By following the issue you mentioned above, it's turned out I got the same mistake. I should get the activity id from the response instead of the id receiving when the user makes an action (a button on an adaptive card in my case)
But it's leading to another issue. When I send an activity with text only, the response has id field, but when the activity includes an attachment (which is the adaptive card in my case) the response has id but with empty string value.

Hi,
I just want fo add here that I have the same issue
even if no text is set and only attachments (adaptive card or hero card).
If my reply contains only 1 attachment, I get back an activity id otherwise if more than 1 attachments (cards) are present in the reply, then the I get back an empty object.
example message:
{
  "text": "",
  "summary": "I found a relevant article.",
  "attachments": [
    {
      "contentType": "application/vnd.microsoft.card.adaptive",
      "content": {
        "type": "AdaptiveCard",
        "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
        "version": "1.0",
        "body": [
          {
            "type": "Container",
            "items": [
              {
                "type": "TextBlock",
                "text": "I found a relevant article.",
                "wrap": true,
                "isSubtle": false
              },
              {
                "type": "TextBlock",
                "text": "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.",
                "wrap": true,
                "isSubtle": false
              }
            ]
          }
        ],
        "actions": []
      }
    },
    {
      "contentType": "application/vnd.microsoft.card.hero",
      "content": {
        "title": "",
        "subtitle": "",
        "text": "",
        "images": [],
        "buttons": [
          {
            "title": "Yes",
            "value": "Yes",
            "type": "messageBack",
            "displayText": "You clicked \"Yes\""
          },
          {
            "title": "No",
            "value": "No",
            "type": "messageBack",
            "displayText": "You clicked \"No\""
          },
          {
            "title": "Test",
            "value": "Test",
            "type": "messageBack",
            "displayText": "You clicked \"Test\""
          }
        ]
      }
    }
  ]
}

@aosolis please correct me if I'm wrong - If you send more than one attachment the Teams backend will split your message into more than one activity, which is why you end up with no Id. The best way to handle this is to send a separate message for each attachment.
The same thing is happening when you send both text and an attachment - it is getting split into two messages. You unfortunately need to send them separately.

@clearab is correct, the service “splits” the list into individual messages.
If your scenario is to update the card in response to a click on a button on the card, then another option is to use the replyToId in the message. That will contain the ID of the activity with the card, so you can use it to update.
If you need to update the message proactively, or if you’re updating a different message, then the only option is to send the list in separate messages :(

@aosolis @clearab thanks for the reply.
I can understand that the message is split into multiple activities and why I don't get back a single activityId.
IMO though this is not the expected behavior.
Since I am only sending 1 message, I should get 1 activityId (even if multiple attachments are present, which is valid btw.). MS Teams could group them into 1 activity and let the rendering do the splitting.
Use case:
I need to send out 1 message (Msg_1) and replace part of the content when a button is pressed.
The message (Msg_1) consists of 2 attachments:

Attachm_1 (Text content)
Attachm_2 (Buttons-actions)

On a button click on Attachm_2 I need to update both --> Text content in Attachm_1 and buttons in Attachm_2
Now, even if I send the attachments one by one and store them locally:

if a button is clicked on Attachm_2 I will get the replyToId of just Attachm_2
I don't get any info about the activityId of Attachm_1, which I also need to update
This means, I need to store and manage locally mappings/groups and order of appearance for each activityId sent.
As you understand this makes it much more complex than it could be.

I would propose 2 enhancements:

MS Teams returns a single activityId for a single message(even with multiple attachments)
MS Teams sends on a button-click (action) the payload, replyToId together with the original message-JSON. This way we don't need to store locally messages that have been sent to users. Our code adjusts the message-JSON and uses updateActivity with the replyToId to update the message. (Note: this is also what Slack does for interactive messages and it is much easier to handle them)

Thanks

@nikosalexakis Thanks for sharing your suggestions here.


feat: sync featureFlagGroup from clerk to posthog

#329 adds the ability to set feature flags based on a user's featureFlagGroup
This PR syncs changes in Clerk metadata to Posthog, so that posthog has an up-to-date version of featureFlagGroup
It's probably inevitable that we need to receive webhooks from Clerk, so I think this could prove useful in the long run as well
I basically just followed this guide: https://clerk.com/docs/integrations/webhooks/sync-data

:tada: This PR is included in version 1.14.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update Pages “about”

Automatically generated by Netlify CMS

👷 Deploy Preview for genuine-toffee-7d5122 processing.

Name
Link

🔨 Latest commit
1b2b9b883398ea604274c5420a0c08f17ed23199

🔍 Latest deploy log
https://app.netlify.com/sites/genuine-toffee-7d5122/deploys/65a942e6dcff690008824acb


Add default to column filter form, fix external operator

#305  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @thisisgoldman and the rest of your teammates on  Graphite

Merge activity

Sep 24, 3:24 PM EDT: @thisisgoldman started a stack merge that includes this pull request via Graphite.


RTL homepage "Search" button covered by featured images at certain specific viewport widths

Description

Reported here https://github.com/WordPress/openverse-frontend/pull/788#pullrequestreview-877725191
Reproduction

Visit the RTL homepage /ar for example.
Change the screen width until you can reproduce the search button being covered by a featured image as in the screenshot in the PR comment link above.

Expectation

The featured images should be further off the side of the page to prevent this and match the LTR version.
Resolution

[ ] 🙋 I would be interested in resolving this bug.

This is no longer reproducible.

I believe this can be safely closed; if anyone observes it again, please re-open!


Small charge current in constant charge(CC)! Please help me!

20:48:50.186 -> AXP2101 Started Successful.
20:48:50.186 -> DCDC1  :ENABLE   Voltage:3100 mV
20:48:50.218 -> DCDC3  :DISABLE   Voltage:3300 mV
20:48:50.218 -> ALDO1  :DISABLE   Voltage:3300 mV
20:48:50.218 -> ALDO2  :DISABLE   Voltage:3100 mV
20:48:50.218 -> ALDO3  :DISABLE   Voltage:3100 mV
20:48:50.218 -> ALDO4  :DISABLE   Voltage:3100 mV
20:48:50.218 -> BLDO1  :DISABLE   Voltage:3300 mV
20:48:50.218 -> ->  getSysPowerDownVoltage:2600
20:48:50.218 -> DISABLE - HEX:0xffffffff
20:48:50.218 -> ENABLE - HEX:0x18fcc0
20:48:50.259 -> Setting Charge Target Current : 1000
20:48:50.259 -> Setting Charge Target Voltage : 4200
20:48:50.259 ->
20:48:55.248 -> ---------------------------------------------------------------------------------------------------------
20:48:55.248 -> Satus1  Satus2  CHARG   DISC   STBY    VBUSIN    VGOOD    VBAT   VBUS   VSYS   Percentage    CHG_STATUS
20:48:55.248 -> (Bin)   (Bin)   (bool)  (bool) (bool)  (bool)    (bool)   (mV)   (mV)   (mV)      (%)           (str)
20:48:55.248 -> ---------------------------------------------------------------------------------------------------------
20:48:55.294 -> 0b11000	0b10010	YES	NO 	NO 	YES	YES	3774	4771	4765	49	constant charge(CC)
20:49:06.297 -> =====================================================================
20:49:06.297 -> BatVoltage: 3772(49%)
20:49:06.297 -> >>>>>>register 0x0: 0b111000
20:49:06.297 -> >>>>>>register 0x1: 0b110010
20:49:06.297 -> >>>>>>register 0x67: 0b11100110
20:49:06.340 -> charge_status: 0b10
The charging current is only about 3-5mA, so the charging time exceeds 12H (set by reg67H[5:4]), and thus also interrupts the charging process. I can't fix this problem, please help me!

Please help me!

You want to set the charge current, but it doesn't change after setting it to 1000mA?

Yes, I set charge current to 1000mA:
// Set constant current charge current limit
if (!PMU.setChargerConstantCurr(XPOWERS_AXP2101_CHG_CUR_1000MA)) {
Serial.println("Setting Charger Constant Current Failed!");
}
And Charger Status is Constant Current (CC)
But the charging current is only from 3mA to 5 mA, so the charging time exceeds 12 hours so an error is reported through the charger status LED (1Hz blink) and stops charging.
Can you help me solve this problem, thank you very much!

Which board do you use? Looks like a hardware issue

Schematic_BBKB_LORA_AXP2101_v1.0_28.10.2023_2024-04-12.pdf
It is my board, use stm32l432 and AXP2101

This problem has nothing to do with this library. It can be determined to be a hardware problem. Please ask your supplier about the charging method of the AXP2101 you are using. AXP2101 has two charging methods, and the hardware wiring methods are different.


New version Pending (Version 1.2)

The new version will add these mods.
Initial smoketest is going to happen and then if all goes right,  the new ZIP file will be uploaded then the world will be wiped for this new version.
SpiceOfLife-mc1.12-1.3.12.jar
jei_1.12.2-<IP_ADDRESS>1.jar
Botania r1.10-363.jar
StorageDrawers-1.12.2-5.4.2.jar
Chameleon-1.12-4.1.3.jar
pamscookables-1.1.jar
AgriCraft-2.12.0-1.12.0-a6.jar
CTM-MC1.12.2-<IP_ADDRESS>.jar
Animus-1.12-2.1.7.jar
tinkersjei-1.2.jar
infinitylib-1.12.0.jar
Pam's BrewCraft 1.12.2-1.0.2.jar
Pam's Get all the Seeds! 1.12a.jar
Pam's Simple Recipes 1.12.2c.jar
CookingForBlockheads_1.12.2-6.5.0.jar
bloodagricraft-1.0.0.jar
Pam's HarvestCraft 1.12.2zg.jar

pyrotech and MysticalCreations have to come out.  Still smoke-testing.

pyrotech and MysticalCreations have to come out.  Still smoke-testing.

these mods were added, the smoke test passed.  The new mod pack is posted.  See http://foo.farm for detail.


Issues 377, 259, 253

Coverage increased (+0.0%) to 70.43% when pulling 01111ea14747e1d89ed7d8867935cb0c1d7c9fd6 on nenewell:master into 1be971e166f3ca3843a01714efd9f8b543cc574e on broadinstitute:master.

Hi Nenewell.  Thanks for your interest in Hellbender!

Hi Nick, looks good. A few comments: many if not all of the warnings could be fixed rather than simply suppressed. Fixing warnings is always preferred to suppressing them. Can you try fixing them?

Nick, this needs to be split into separate pull requests, one for issue. I'm going to close this - please reopen when you have split it.


Give access to Image ID

Docker v1.10 introduced a content/digest-based image ID to uniquely identify docker images. It would be great if this image ID would be available from the gradle (and maybe maven) plugin after the image has been built or is deemed being already up-to-date.
Having the image ID would, for example, let the subsequent deployment processes skip containers that do not change (without having to resolve tags to image ids or workaround with manual mechanisms). This is of particular importance for larger multi-project gradle setups / single repository approaches where a single build manages multiple images.

Hi @remmeier , after some discussions over how to provide the user with the digest output, we are planning to have the Jib tasks/goals output a jib-image.digest into the build output directory (build/jib-image.digest for Gradle/target/jib-image.digest for Maven). This file will contain the container image digest. Will this be adequate for your use case?

yes thx, that would be a great help.

Just so I'm clear @coollog, you are proposing we write out the manifest digest (type application/vnd.docker.distribution.manifest.v2+json, not the container configuration digest (type application/vnd.docker.container.image.v1+json)?
(docker images --digests reports the container configuration digests as the Image ID, and the manifest digest as Digest. The manifest references the container configuration as config.digest.)

Yes, the manifest digest, which is the digest portion of the image reference if it's qualified with a digest (ie. gcr.io/distroless/java@sha256:bb1c9179c2263733f235291998cb849d52fb730743125420cf4f97a362d6a6dd where sha256:bb1c9179c2263733f235291998cb849d52fb730743125420cf4f97a362d6a6dd is the image digest.

Hmm, maybe we should write out jib-image.id as well. @remmeier Do you happen to need the Docker Image ID (config digest) or is the image digest enough?

thx a lot! I'm ok with either. i could imagine that some people may expect the docker image id as it is well establusged

Filed #1204 for that!

Hi @remmeier , @sdavids, @novotnyr, @keykey7, @Tanmayshetty, version 0.10.0 has been released with the image digest written out to a jib-image.digest file in the build output directory.


Changed node version to run as a service

Description
In order to migrate to Node 16, we need to update the version used to run an agent as a service too.
Changelog

Node version used to run as a service updated to 16

Tested on Mac M1, node and agent processes runs as arm64 without x86 emulation, commands like svc.sh start/stop/install/uninstall working fine


[Snyk] Upgrade junit:junit from 4.13.1 to 4.13.2

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade junit:junit from 4.13.1 to 4.13.2.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 3 years ago, on 2021-02-13.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@snyk-bot


G

Bug描述
A clear and concise description of what the bug is.
复现步骤
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

截图
If applicable, add screenshots to help explain your problem.
复现环境:

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 2.0.4]

详细描述
Add any other context about the problem here.

Please describe your problem correctly.
请正确描述你的问题。


Comma in from-name will mess up reply

When a user set its name to "foo, bar" (which will result in From: "Foo, Bar"<EMAIL_ADDRESS>and then click on reply, the first part before the comma will be cropped, I think because it will be interpreted as a delimiter of mail receipents. Also this do funny things, when the receipent will be inserted in the adressbook.
How to fix? Use a library :laughing: or check if a , is inside of two double qoutations and do not treat it as a delimiter.

Seems to be the same as #1447 where all the action was?

Oh boy, this is almost 3 years old. I don't use rainloop anymore, so I can't confirm if it's fixed, sorry. But I guess so.


Sync some methods from flutter

Description
I synced some android method from flutter, for IOS this library provides more device detail then flutter.
Fixed #622

Checklist

[x] I have tested this on a device/simulator for each compatible OS
[x] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md
[x] I updated the typings files (deviceinfo.d.ts, deviceinfo.js.flow)
[ ] I updated the dummy web/test polyfill (default/index.js)
[x] I added a sample use of the API (example/App.js)

This looks good on a read, I’ll pull it locally and if it tests out I’ll merger and release a minor for the feature additions. Thanks for taking the time to bring the module up to parity, I really appreciate it

You are welcome :)


Debugger stopped working with the projection event service

I was using the debugger while using the event sourcing library on Visual Studio 17.8.4 and the debugger was working when I persisted the events. The debugger would immediately jump to my projectionread class and all was good.  I upgraded my Visual Studio to 17.8.5 and the debugger stopped working in the projectionread class. I am still able to debug up to the point I persist to the event store and complete the process. Debugger does not jump to the projection read class.
any thoughts?

Issue was on my end.


Fixing a integral conversion warning

Fixes a warning as reported here: https://irclog.cct.lsu.edu/ste~b~~b~ar/2022-02-06#374594;

The HIP problems will be solved by https://github.com/STEllAR-GROUP/hpx/pull/5770. Merging...


[60mBTC bounty] Gate.io implementation

Hello,
I offer a 60mBTC bounty to whom finishes the full implementation of Gate.io API before December 7th (2017, yes). If it is done before December 12th, the bounty would be 40 mBTC. If it is not done by then, I may be available to do it by myself.
And I always pay my bounties: hitbtc, liqui, livecoin, yobit, cryptopia

I did it today by converting bter to gate.io.
https://github.com/timmolter/XChange/commit/85e6925373e917cf86edacb4077ecd3913193ca8
Haven't tested it through though, nor do I plan to.

You just saved me 60mBTC if so. I am going to test it asap.?

Works so far (balance, ticker, place order), thank you.


Consul should use prometheus/common HTTPClient

With https://github.com/prometheus/common/pull/308, consul should be able to use the full common's http client.
It means that it can get the ability to read its token and basic auth password from a file.
Currently we only use the TLS part.
Notes:

We must stay compatible with the current config (when unmarshalling, turn provided username and password into http client basicauth).
We should check that authorization is not set at the same time as consul token. If it is the case, error.
if a consul token is passed, it should still be passed to the consul client, because I think it uses X-Consul-Token, which is needed to connect to old consul, that does not support Authorization header. So consul_token should still be documented.
if username and basic_auth.username are set, we should error. Same for password.

if username and basic_auth.username are set, we should error.

cc @LeviHarrison

For the record, Levi is working on this.


Support for Observable in call

Can the effect call support observables as well.  right now i'm having to do:
let dataFunction = () => { return businessesService.getAllWells().take(1).toPromise(); }
const wells = yield call(dataFunction);

I'm not sure if this needs to be added to the core. you can create a little helper saga for this

Could you point me to an explanation on how to do that?  It looks like I would need to create my own effect?  Is this correct or is there an easier way.  I figured it would be nice to have the call abstraction understand whether I am using a promise or an observable whether its an Rx version or an ES7 version.  It seems weird that call wouldn't support an ES7 proposed interface.

function* callObs(obs) {
   return ( yield obs.take(1).toPromise() )
}

function* saga() {
   ...
   const wells = yield call(businessesService.getAllWells());
}

@babeal I don't understand what you would expect redux-saga to do. What does it mean to call an observable? How can we know the behavior you want? You may want the first item of the stream, or you may want all the items of the stream once the stream ends

@slorber - of course the behavior of an observable can be different than a promise.  In this case for this operator I would expect that the semantics would remain the same and only the first value of the observable would be used.  This may or may not be acceptable.


Fix pybind11 issues with macOS

This fixes a test failure and compiler error when running the pybind11 tests on macOS. This pull request has a matching branch name with https://github.com/osrf/homebrew-simulation/pull/1793, so the CI is using pybind11 and is now clean.

This pull request has been mentioned on Gazebo Community. There might be relevant details there:
https://community.gazebosim.org/t/new-ignition-releases-2022-03-01-citadel-edifice-fortress/1313/1


Training log of RepLLaMA

Hi Xueguang,
Great work! I am training my own RepLLaMA now and find that the training loss starts from 90+ and quickly drops below 0.1 in around 30 steps (as shown below). Is it normal or could please provide your training log of RepLLaMA?

Thanks!

this looks a bit weird. what is your batch size/ training group size setting?

this looks a bit weird. what is your batch size/ training group size setting?

The param settings are:

per_gpu_train_batch_size=8,
hard_negatives_per_sample=15,
learning_rate=1e-4,
gradient_accumulation_steps=4.

I use 6 A100 40G GPUs for training.

Solved. It is because of my own bug about processing the EOS token. Thanks!

Hello, I met the same problem. Can you please tell me how do you solve it? Thank you a lot!


Add page for test results

This adds a new view for "test results", and links to this view from the relevant entries in the activity timeline.
In future it will also be linked to from a "Supporting information" tab.
Checklist:

[x] Have you documented your changes in the pull request description?
[x] Does the change present any security considerations?
[ ] Has acceptance criteria been tested by a peer?
[ ] Has the CHANGELOG been updated? (If change is worth telling users about.)

Screenshots
Before
Activity timeline links directly to the test result file:

After
Activity timeline links to new page for the test result:

New test result page:

Had a look - looking good so far.
A few things to clean up:

Need to make sure all details collected are displayed.
** Further details not displayed
** Product tested not displayed
** Attachment description not displayed (this is a bit awkward as attachment is on the right, but I think for now we can include in table.
Can we change Date to Date of test
Link for view test result on the activity timeline would ideally be unique - I wonder if we can include some of the title in it?

A demo for Kam, this is different


Potential unsound casting from volatile_register::RW to the wrapped type

Hi, I am wondering whether the casting here is unsound:
https://github.com/rust-embedded/cortex-m/blob/1746a63ca16b68514ea23dcca1543aed00165452/src/peripheral/scb.rs#L172-L174
Based on the definition, the wrapper struct volatile_register::RW (let me abbreviate it as vr here) didn't have stable layout, and rustc would preserve the right to insert padding or reorder the structure. vr<u32> should be declared as transparent; otherwise, casting it to u32 could lead to UB such as uninitialized memory exposure to ptr::read_volatile.

Yep, you're right. In practice this is very unlikely to lead to any issues but in principle volatile_register should add a repr to the structs. There's an open PR to do so here: https://github.com/japaric/volatile-register/pull/9 but it's not merged yet.

volatile-register v0.2.2 is now out, it adds #[repr(transparent)] so the pointer cast is now sound.


Add option to enable hardware sync on deploy

That is required to add this fubctionality in terraform-provider-maas

https://github.com/maas/terraform-provider-maas/issues/57


New-BCContainerWizard not working in <IP_ADDRESS> - <IP_ADDRESS> ?

(credit to Nitin Verma, who emailed me about this issue)
In recent versions of NavContainerHelper, it seems that New-BCContainerWizard no longer works.
When the New-BCContainerWizard command is issued in versions <IP_ADDRESS> - 22, a blank PowerShell window appears to briefly open, then closes immediately.  It looks like an error might sometimes flash in the new window, but it's so brief that I can't read it. No other error is displayed, and the wizard does not start in the PowerShell session.
Start-Transcript does not capture any activity or errors in the calling session.
Here is an animated gif of the issue:

If I roll back to version <IP_ADDRESS>, the wizard works.
I am able to reproduce the issue on 3 different servers.
Please let me know if you have any questions or need any additional information.

Problem is the space in the path where navcontainerhelper gets installed.
during my tests, it is located elsewhere:-(

No worries, thanks!

Shipped in <IP_ADDRESS>

This issue is back for me.
using BcContainerHelper version 6.0.11
Running on Windows, PowerShell 5.1.22621.2506

you need 6.0.12 (which right now is in preview) - will ship tomorrow


fix: incorrectly thrown exception in Directory.CreateSymbolicLink

Remove incorrectly thrown exception when the target does not exist in Directory.CreateSymbolicLink. The real file system does not throw an exception in this case.

See here for a succeeding test against the real file system.

@fgreinacher
I consider this a bug, as our goal is to mimic the behaviour of the real file system. As we did not change any interface, I would not consider this a breaking change.

Technically it's still a breaking change as folks might have relied on the exception. But I agree that in this case it's pretty unlikely.


Input validation allows invalid UTF-8 code points

My Environment

ArangoDB Version: 3.9.10
Deployment Mode: Single Server
Deployment Strategy: Manual Start
Configuration: nothing special, just installed on debian via apt
Infrastructure: VPS
Operating System: Debian 12
Total RAM in your machine: 64Gb
Disks in use: HDD
Used Package: Debian or Ubuntu .deb

Component, Query & Data
Affected feature:
data store
Dataset:
A single collection with a single document with the following content:
{"field": "\uDC89"}

It was possible to create such a document through the web interface. Probably any string with invalid UTF-8 code points will reproduce the issue. One can use Perl for example to confirm that the string contains an invalid code point:
$ perl -Mutf8 -wle 'binmode STDOUT, ":utf8"; print "\x{DC89}"'
Unicode surrogate U+DC89 is illegal in UTF-8 at -e line 1.

Executing
db._executeTransaction({ collections: {}, action: function() {return require("internal").options(); } })['server.validate-utf8-strings']

confirms the default value of the config to be true.
Size of your Dataset on disk: minimal
Steps to reproduce

insert above document into a collection

Problem:
Invalid data like this will lead to failure of downstream libraries that are relatively hard to debug since the data returned by the API is not even valid JSON (at least for some definition of "valid JSON").
Expected result:
I expected — and maybe that's not correct — that server.validate-utf8-strings will validate input data. Hence  I'd expect that the API denies entry of such documents.

With the change, it will validate any new incoming data.
Data that is already in the database will not be revalidated automatically, unless it is passed through some APIs that trigger the validation. This could happen, for example, when data is shipped around inside an ArangoDB cluster from node to node.
Note that the change is still pending and we are currently discussing target versions. No decision yet.

For info, the bugfix will be part of 3.11.0. In 3.11.0 the checks for invalid surrogate data will be enabled by default.
The fix cannot easily be backported to stable branches because it would change the behavior for existing deployments when doing patch release upgrades. Such behavior change would be unexpected when doing an upgrade from, say 3.9.x to 3.9.y, or from 3.10.x to 3.10.y.
Larger changes can be expected when upgrading from one minor version to another, say from 3.10.x to 3.11.y.
There is also the option to opt out of the extended checks in 3.11 by setting --server.validate-utf8-strings=false on startup. This is not recommended, but can be used for compatibility or during an upgrade until all data has been validated/cleared.


500 Error Thrown when attempting to upload attribute csv

Successfully able to create graph from node and edge tables uploaded as separate csv files. When attempting to upload attribute csv file after graph constructed, I get this 500 error.

Sample of the server log:
<IP_ADDRESS> - - [18/Jun/2019:15:25:46] "POST /api/v1/multinet/graphql HTTP/1.1" 200 356 "http://localhost:8080/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.90 Safari/537.36"
Bulk Loading
<IP_ADDRESS> - - [18/Jun/2019:15:26:01] "POST /api/v1/multinet/csv/doesItWork/attributes HTTP/1.1" 500 125 "http://localhost:8080/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.90 Safari/537.36"
Bulk Loading
<IP_ADDRESS> - - [18/Jun/2019:15:28:54] "POST /api/v1/multinet/csv/doesItWork/attribute HTTP/1.1" 500 125 "http://localhost:8080/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.90 Safari/537.36"
Executing GraphQL Request
request: query {
        workspaces (name: "doesItWork") {
          tables {
            name
            fields
          }
          graphs { name }
        }
      }
Errors in request: 0
<IP_ADDRESS> - - [18/Jun/2019:15:30:27] "POST /api/v1/multinet/graphql HTTP/1.1" 200 356 "http://localhost:8080/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.90 Safari/537.36"
Bulk Loading
<IP_ADDRESS> - - [18/Jun/2019:15:32:52] "POST /api/v1/multinet/csv/doesItWork/leaf-attributes HTTP/1.1" 500 125 "http://localhost:8080/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.90 Safari/537.36"

Update-
Created new workspace and attempted to upload attribute file as the first file and got same error.
Gist for file:
attribute csv

@jenrogers1207, did we ever resolve this?

@waxlamp I honestly don't remember! I think so? Might also be obsolete now if we are transitioning to the nested json

Good point--I'll close the issue now, and if this flares up again we'll just re-open. Thanks!

sounds good thanks for doing that!
On Tue, Aug 13, 2019 at 1:43 PM Roni Choudhury<EMAIL_ADDRESS>wrote:

Closed #64 https://github.com/multinet-app/multinet/issues/64.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/multinet-app/multinet/issues/64?email_source=notifications&email_token=AFM5ERFQPUS7NMZEC5BHDP3QEMFE5A5CNFSM4HZENGBKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOTBBL4SQ#event-2554510922,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFM5EREIMC3NPQBY2RG2LTDQEMFE5ANCNFSM4HZENGBA
.


[Event Request] codeunit 5940 ServContractManagement procedure CheckMultipleCurrenciesForCustomers()

Please can you add the following event/code at the start of the above procedure...
OnBeforeCheckMultipleCurrenciesForCustomers(ServiceContractHeader, IsHandled);
if IsHandled then
    exit;

with a local variable...
var
    IsHandled: Boolean;

The event publisher would be...
[IntegrationEvent(false, false)]
local procedure OnBeforeCheckMultipleCurrenciesForCustomers(var ServiceContractHeader: Record "Service Contract Header"; var IsHandled: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 11061.


Error: The system cannot find the path specified (solution found)

Hey guys, such a great work you're doing and love it!!
I get this error when i'm using Ctrl+Alt+p (on Win8) + Sublime3
Error: The system cannot find the path specified (screenshot here http://screencast.com/t/mfTPeLEnPd )
Do you have any idea why this happenes? I have NodeJS installed, and checked version:
C:\Users\Marius>node -v
v0.10.31
Thank you so much!!
Marius

Since the bump of autoprefixer-core to 4.0.0, this issue is resolved.
The "ie > 8" syntax now works as expected.

Hi @alexilyaev . Can you say how you fixed problem with ">"? I have this problem in sublime3, but I am not indestand what you do for fix this (this "Since the bump of autoprefixer-core to 4.0.0, this issue is resolved." - or this you may that autoprefixer updated and all working ok?)
Thanks!
p.s.: autoprefixer I am install a few days ago. I.e. it new version.

I have the same problem with sublime 3. Cant get the > to work with any browser. Shouldnt this work in the autoprefxer configuration?
"browsers": ["last 2 versions","ie => 8"]

its a lot of work to start listing all browsers that i need support for...

@chyvak1831 @tinktonk The latest version of sublime-autoprefixer works ok for me.
Try re-installing the package in Sublime.
I also have<EMAIL_ADDRESS>installed using npm, not sure it's related.
But try running autoprefixer directly on your file.


Resource -> URI Mapper

For the Auth System V2 project. Technically this is for the hs_auth_client repo but I included it here to add it to the project taskboard to make it easier to track progress.
We need to add functionality to the hs_auth client to map resources to their corresponding URIs. The mapper would need to:

the path to the resource (e.g: hs:hs_auth:api:v1:getme)
include resource and metadata parameters in the URI (e.g: hs:hs_auth:api:v1:getme?user=kzalys#until=20)

Definition of done:

Implemented the described mapper with unit tests and merged it into the hs_auth_client, integrating it into the service calls to hs_auth will be handled as a separate issue.

I'll work on implementing the resource -> URI mapping for hs_auth. We will also need to implement something similar on hs_auth_client

hs_auth resource -> URI done in #76.
We still need to implement this for the hs_auth client library: https://github.com/unicsmcr/hs_auth_client

Closing in favor of https://github.com/unicsmcr/hs_auth_client/issues/15


New Game: Hit Counter

PR Description 📜
Hit Counter is an interactive web-based game designed to test and measure your speed and accuracy in either hitting the spacebar or clicking the mouse button. Choose your preferred mode and duration, then compete to see how many hits you can achieve within the given time.
Fixes #3734

Mark the task you have completed ✅

[ x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[ x] I have performed a self-review of my own code or work.
[ x] I have commented my code, particularly in hard-to-understand areas.
[ x] My changes generates no new warnings.
[ x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[ x] I have added screenshot for website preview in assets/images
[x ] I have added entries for my game in main README.md
[x ] I have added README.md in my folder
[x ] I have added working video of the game in README.md (optional)
[x ] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @anisharma07 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Thank you  @anisharma07 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


DDPB-4094: Upgrade client to PHP 8

Purpose
Upgrades the frontend and admin apps to PHP 8.0.12.
Fixes DDPB-4094
Approach
Most of this was working out the dependency trees and which packages to update. The vast majority of changes here are updating files for PHP 8 syntax. The main code changes I had to make as a result of PHP 8 was checking array indexes exist before accessing them as these are now thrown as warnings rather than notices.
Learning
It looked like some of our client unit tests weren't being run as there were a number of tests that were broken (e.g. variables not defined, prophecy expectations not set up properly). Everything seems to be running now but with a bunch of deprecation warnings so we should tackle them in a future ticket.
I also attempted to run rector on the project which had some amazing refactoring results but it seems to be conflicting with our pre-commit hooks so I reverted the changes for now. We should definitely run it in the future as some of the code changes were great and converted old-style PHP to shiny new style PHP 8 (particularly replacing switch statements to match statements which are so much easier to read).
Checklist

[x] I have performed a self-review of my own code
[ ] I have updated documentation (Confluence/ADR/tech debt doc) where relevant
[x] I have added tests to prove my work
[ ] The product team have approved these changes

Looked at rector briefly - looks like a really good way to do upgrades!

We've been using it in Sirius a bit and it does help a lot.


Adding istioctl and upgrade release qualification (#9947)

Adding istioctl and upgrade release qualification
These were moved from https://github.com/istio-releases/daily-release so
they can be run and tested more easily.
Also refactored the e2e test logic in lib.sh for re-usability.
Cherry-pick from #9947. No impact to production code.

@hklai: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hklai
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [hklai]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@hklai: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-local-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-k8s-tests

prow/e2e-simpleTests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test e2e-simpleTests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-k8s-tests

prow/e2e-simpleTests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test e2e-simpleTests

prow/e2e-dashboard.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-k8s-tests

prow/e2e-simpleTests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test e2e-simpleTests

prow/e2e-dashboard.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-k8s-tests

prow/e2e-simpleTests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test e2e-simpleTests

prow/e2e-dashboard.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-k8s-tests

prow/e2e-simpleTests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test e2e-simpleTests

prow/e2e-dashboard.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test e2e-mixer-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hklai
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

prow/OWNERS [hklai]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-k8s-tests

prow/e2e-simpleTests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test e2e-simpleTests

prow/e2e-bookInfoTests-v1alpha3.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
ab1e7faeae42540f4a611ba8e1007964e49aaf7f
link
/test e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-k8s-tests

prow/e2e-bookInfoTests-v1alpha3.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
ab1e7faeae42540f4a611ba8e1007964e49aaf7f
link
/test e2e-dashboard

prow/e2e-simpleTests.sh
ab1e7faeae42540f4a611ba8e1007964e49aaf7f
link
/test e2e-simpleTests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
ab1e7faeae42540f4a611ba8e1007964e49aaf7f
link
/test e2e-dashboard

prow/e2e-simpleTests.sh
ab1e7faeae42540f4a611ba8e1007964e49aaf7f
link
/test e2e-simpleTests

prow/e2e-bookInfoTests-v1alpha3.sh
ab1e7faeae42540f4a611ba8e1007964e49aaf7f
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
9e9d503833a31a0f9380487914eb3a55d809e384
link
/test istio-integ-k8s-tests

prow/e2e-dashboard.sh
ab1e7faeae42540f4a611ba8e1007964e49aaf7f
link
/test e2e-dashboard

prow/e2e-simpleTests.sh
ab1e7faeae42540f4a611ba8e1007964e49aaf7f
link
/test e2e-simpleTests

prow/e2e-bookInfoTests-v1alpha3.sh
ab1e7faeae42540f4a611ba8e1007964e49aaf7f
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ab1e7faeae42540f4a611ba8e1007964e49aaf7f
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
ab1e7faeae42540f4a611ba8e1007964e49aaf7f
link
/test e2e-mixer-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Add in testing option to generate output

          is there option to override expected output with new output?

Originally posted by @adisos in https://github.com/np-guard/vmware-analyzer/pull/94#discussion_r1896595416

fixed by #107


Fixes broken display of CfP-Dates

Currently in the list of upcomming CfPs there is no information given to when the CfP starts and/or ends. This is due to wrongly named methods for CfP-Date-retrieval. I've fixed these function names and now the CfP-Info is displayed again.

Much better, thanks :)


Catch uncaught exception to pass it to callback

Some error of underlying store, like memcached-plus, throw exception that is not capture and could propagate to main loop.
CF assertKey for exemple: https://github.com/victorquinn/memcache-plus/blob/master/lib/client.js#L16-L22.
Surround by try catch to capture and restore the error to the chain promise / callback.

Thanks, I'll release this soon.

This is available in version 3.4.2


Initial working e2e report expires, no dependency

We need to test via e2e testing, the following situations:

[X] Does a report with no dependencies with an expiration set, properly expire?
[ ] Does a report that is depended on by another report not get deleted despite reaching its expiration date?
[ ] Does a report that is depended on by a ReportQuery not get deleted despite reaching its expiration date?

/test all

/retest

/retest

/retest

/lgtm

/retest

/retest

/retest

/override ci/prow/metering-e2e-aws

Not entirely sure why tide is retesting all these jobs.
/override ci/prow/metering-upgrade-aws


TypeError: Cannot read properties of undefined (reading 'inTable') in v4.0.0

Affected packages and versions
4.0.0
Link to runnable example
https://github.com/arechsteiner/gfm-bug/blob/main/src/App.tsx#L12
Steps to reproduce
Attempt to render
const test = `hello world \`call' hello world \`call'`

With
<ReactMarkdown remarkPlugins={[remarkGfm]}>
  {test}
</ReactMarkdown>

Expected behavior
Previously this was no issue.
Actual behavior
TypeError: Cannot read properties of undefined (reading 'inTable')

Runtime
No response
Package manager
yarn 1
OS
macOS
Build and bundle tools
Vite

The updates are making their way through several hundred packages, for now pin the previous major until the new react-markdown major is released

@ChristianMurphy I'm a bit confused, how is this a duplicate of a typescript related issue? This is not a typescript error, this is a runtime error.

A major version release is rolling out across all: unified, remark, rehype, and micromark packages.
This includes both type changes and changes to the parser.

Is this issue fixed yet?

@arechsteiner there is nothing to "fix" it isn't a bug.
The major releases are still rolling out across the remark and mdx projects.
Check if the project you use has a new major update.
If there, is try out the new version.
If not, be patient it takes time to update 500+ packages.

Hey @ChristianMurphy, thank you and everyone for the fantastic work here!
What's a reasonable expectation to have for this to be resolved?
I noticed that it's approaching 2 months since the initial major releases were made, so I wondered how much longer it will take for them to be in sync.
Thanks again!

@ky1ejs this issue, remark-gfm with react-markdown is resolved, and has been for a while.
There are 500+ unified packages being updated so:

Be patient
Be specific on which you are using

You (@ky1ejs) appear to be asking about remark-gfm with mdx, that is in progress currently, you can track the progress towards the next mdx release in the mdx repo itself.

Thanks @ChristianMurphy, great breakdown, much appreciated! 🙏🏼 🙏🏼

Funny thing, that I still got that error, but it was working like 10 minutes ago. After reviewing all the changes, I've noticed that the problem was causes the error was additional white space.
Working code:
<ReactMarkdown
    // ...
    remarkPlugins={[remarkGfm]}
>{content}</ReactMarkdown>

Code that throws an error:
<ReactMarkdown
    // ...
    remarkPlugins={[remarkGfm]}
>
    {content}
</ReactMarkdown>

Parsing error: Cannot set properties of undefined (setting 'inTable') eslint

Still getting this error after updating to:
"@mdx-js/mdx": "^3.0.0",

        "remark": "^15.0.1",
        "remark-directive": "^3.0.0",
        "remark-frontmatter": "^5.0.0",
        "remark-gfm": "^4.0.0",
        "remark-lint": "^9.1.2",
        "remark-mdx-frontmatter": "^4.0.0",
        "remark-mermaidjs": "^6.0.0",
        "remark-preset-lint-recommended": "^6.1.3",
        "remark-preset-prettier": "^2.0.1",
        "remark-smartypants": "^2.0.0",

---
Foo: Bar
---

| First Header  | Second Header |
| ------------- | ------------- |
| Content Cell  | Content Cell  |
| Content Cell  | Content Cell  |

You can make a PR to remark-preset-prettier, most likely.
Run npm why remark-gfm and look for who uses the the outdated version.

remark-preset-prettier doesn't have any dependencies.

Thanks for much for reviewing. Here's what I got after running npm why remark-gfm. Seems like we aren’t running anything else that depends on remark-gfm and I confirmed v4.0.0 is what we are running from the top-level of node_modules. So far I haven't seen anything nested deeper that is using another version of it.
$ npm why remark-gfm
<EMAIL_ADDRESS>node_modules/remark-gfm
<EMAIL_ADDRESS>from the root project

This looks like a screenshot from the VSCode remark extension. I’ve been holding back updating this until remark-lint is updated to the latest unified.

Thanks all. This seems to resolve the issue by forcibly overriding in package.json, though it's not something I'm ok with for now, so I may need to roll back to prior version of MDX. The underlying cause seems to be eslint. Specifically, the dependencies declared by these two packages are outdated now. See: https://github.com/mdx-js/eslint-mdx/tree/master/packages
    "overrides": {
        "remark-mdx": "3.0.0",
        "remark-parse": "11.0.0",
        "remark-stringify": "11.0.0",
        "unified": "11.0.4"
    }

It is still not fixed, right? And the best approach is
https://github.com/syntax-tree/mdast-util-from-markdown/issues/34#issuecomment-1727310901
Hold on version 3 of remark-gfm, until the next major of react markdown is released

Is it correct?

It is fixed by now. See https://github.com/remarkjs/react-markdown/releases/tag/9.0.0. The comment you linked precedes that release.

@remcohaszing Thank you for quick response.
I got this error with  "remark-gfm": "4.0.0", and recommendation here https://github.com/contentlayerdev/contentlayer/issues/611#issuecomment-1841747046 to check this issue.
Or do we mean different issues?
• "docs/codeblock.mdx": UnexpectedMDXError: Error: Build failed with 1 error:
     _mdx_bundler_entry_point-d295f73f-3987-4c43-b652-df139b3af638.mdx:0:0: ERROR: [plugin: @mdx-js/esbuild] TypeError: Cannot read properties of undefined (reading 'inTable')
         at Object.exitCodeText (file:// /node_modules/.pnpm/mdast-util-gfm-table@2.0.0/node_modules/mdast-util-gfm-table/lib/index.js:123:17)
         at compile (file:// /node_modules/.pnpm/mdast-util-from-markdown@1.3.1/node_modules/mdast-util-from-markdown/lib/index.js:352:40)
         at fromMarkdown (file:// /node_modules/.pnpm/mdast-util-from-markdown@1.3.1/node_modules/mdast-util-from-markdown/lib/index.js:187:29)
         at parser (file:// /node_modules/.pnpm/remark-parse@10.0.2/node_modules/remark-parse/lib/index.js:18:12)
         at Function.parse (file:// /node_modules/.pnpm/unified@10.1.2/node_modules/unified/lib/index.js:273:12)
         at executor (file:// /node_modules/.pnpm/unified@10.1.2/node_modules/unified/lib/index.js:393:31)
         at new Promise (<anonymous>)
         at Function.process (file:// /node_modules/.pnpm/unified@10.1.2/node_modules/unified/lib/index.js:380:14)
         at process (file:// /node_modules/.pnpm/@mdx-js+mdx@2.3.0/node_modules/@mdx-js/mdx/lib/util/create-format-aware-processors.js:50:22)
         at onload (file:// /node_modules/.pnpm/@mdx-js+esbuild@2.3.0_esbuild@0.18.20/node_modules/@mdx-js/esbuild/lib/index.js:151:22)
         at requestCallbacks.on-load ( /node_modules/.pnpm/esbuild@0.18.20/node_modules/esbuild/lib/main.js:1434:28)
         at processTicksAndRejections (node:internal/process/task_queues:95:5)
         at handleRequest ( /node_modules/.pnpm/esbuild@0.18.20/node_modules/esbuild/lib/main.js:729:13)

package.json
     "dependencies": {
    "@radix-ui/react-accordion": "1.1.2",
    "@radix-ui/react-aspect-ratio": "1.0.3",
    "@radix-ui/react-collapsible": "1.0.3",
    "@radix-ui/react-dialog": "1.0.5",
    "@radix-ui/react-dropdown-menu": "2.0.6",
    "@radix-ui/react-icons": "1.3.0",
    "@radix-ui/react-scroll-area": "1.0.5",
    "@radix-ui/react-slot": "1.0.2",
    "@radix-ui/react-tabs": "1.0.4",
    "@radix-ui/react-tooltip": "1.0.7",
    "axios": "1.6.8",
    "class-variance-authority": "0.7.0",
    "clsx": "2.1.0",
    "cmdk": "1.0.0",
    "contentlayer": "0.3.4",
    "jotai": "2.8.0",
    "next": "14.2.2",
    "next-contentlayer": "0.3.4",
    "next-themes": "0.3.0",
    "react": "18.2.0",
    "react-children-utilities": "2.10.0",
    "react-dom": "18.2.0",
    "react-wrap-balancer": "1.1.0",
    "rehype-slug": "6.0.0",
    "sharp": "0.33.3",
    "tailwind-merge": "2.2.2",
    "tailwindcss-animate": "1.0.7",
    "zod": "3.22.4"
  },
  "devDependencies": {
    "@types/node": "20.12.7",
    "@types/react": "18.2.79",
    "@types/react-dom": "18.2.25",
    "autoprefixer": "10.4.19",
    "eslint": "9.0.0",
    "eslint-config-next": "14.2.2",
    "mdast-util-toc": "7.0.0",
    "postcss": "8.4.38",
    "rehype-autolink-headings": "^7.1.0",
    "rehype-pretty-code": "^0.13.1",
    "remark": "15.0.1",
    "remark-code-import": "1.2.0",
    "remark-gfm": "3.0.1",
    "tailwindcss": "3.4.3",
    "typescript": "5.4.5",
    "unist-builder": "4.0.0",
    "unist-util-visit": "5.0.0"
  }
}

I suggest you run npm ls unified. You should see only one version of unified, ideally 11.
You can try to fix it by removing node_modules and your lockfile, and running npm install.

I suggest you run npm ls unified. You should see only one version of unified, ideally 11.
You can try to fix it by removing node_modules and your lockfile, and running npm install.

Thank you for your patience and help. I added overrides  as was suggested here https://github.com/remarkjs/remark-gfm/issues/57#issuecomment-1826794187
It didn't help. But I add '"mdast-util-frontmatter": "2.0.1"' in addition:
  "pnpm": {
    "overrides": {
      "remark-mdx": "3.0.0",
      "unified": "11.0.4",
      "remark-parse": "11.0.0",
      "mdast-util-frontmatter": "2.0.1"
    }
  }

Now it works.
Just for google, if other devs will have the same compatibility issue
Error: Found 1 problems in 10 documents.

 └── Encountered unexpected errors while processing of 1 documents. This is possibly a bug in Contentlayer. Please open an issue.

     • "docs/supabase/env.mdx": UnexpectedMDXError: Error: Build failed with 1 error:
     _mdx_bundler_entry_point-3f5a0ab5-57a4-43a2-a41d-8ff1cd0b0b3d.mdx:0:0: ERROR: [plugin: @mdx-js/esbuild] TypeError: Cannot set properties of undefined (setting 'value')
         at Object.close (file:// /apps/docs/node_modules/.pnpm/mdast-util-frontmatter@1.0.1/node_modules/mdast-util-frontmatter/lib/index.js:69:14)
         at compile (file:// /apps/docs/node_modules/.pnpm/mdast-util-from-markdown@2.0.0/node_modules/mdast-util-from-markdown/lib/index.js:337:40)
         at fromMarkdown (file:// /apps/docs/node_modules/.pnpm/mdast-util-from-markdown@2.0.0/node_modules/mdast-util-from-markdown/lib/index.js:173:27)
         at parser (file:// /apps/docs/node_modules/.pnpm/remark-parse@11.0.0/node_modules/remark-parse/lib/index.js:33:12)
         at Function.parse (file:// /apps/docs/node_modules/.pnpm/unified@11.0.4/node_modules/unified/lib/index.js:668:12)
         at executor (file:// /apps/docs/node_modules/.pnpm/unified@11.0.4/node_modules/unified/lib/index.js:734:40)
         at new Promise (<anonymous>)
         at Function.process (file:// /apps/docs/node_modules/.pnpm/unified@11.0.4/node_modules/unified/lib/index.js:720:47)
         at process (file:// /apps/docs/node_modules/.pnpm/@mdx-js+mdx@2.3.0/node_modules/@mdx-js/mdx/lib/util/create-format-aware-processors.js:50:22)
         at onload (file:// /apps/docs/node_modules/.pnpm/@mdx-js+esbuild@2.3.0_esbuild@0.18.20/node_modules/@mdx-js/esbuild/lib/index.js:151:22)
         at requestCallbacks.on-load ( /apps/docs/node_modules/.pnpm/esbuild@0.18.20/node_modules/esbuild/lib/main.js:1434:28)
         at processTicksAndRejections (node:internal/process/task_queues:95:5)
         at handleRequest ( /apps/docs/node_modules/.pnpm/esbuild@0.18.20/node_modules/esbuild/lib/main.js:729:13)

SourceFetchDataError: {
  "_tag": "HandledFetchDataError"
}

Should this be reopened?
Downgrading to 3.0.1 fixes the problem for now.

This is not a bug. If you’re seeing this, it means some of your dependencies are outdated, but not all.


XMPP component not working after upgrading to 0.87

Home Assistant release with the issue:
 0.87
Last working Home Assistant release (if known):
0.86.4
Operating environment (Hass.io/Docker/Windows/etc.):
 venv install
Component/platform:
 https://www.home-assistant.io/components/notify.xmpp/
Description of problem:
notify XMPP not longer working after upgrading from 0.86.4 to 0.87--> See Traceback attached
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
notify:
  - name: thorsten
    platform: xmpp
    host: <IP_ADDRESS>
    port: 5222
    sender<EMAIL_ADDRESS>    password: xxxxxxxxxxxxxxxxxxxxxx
    recipient<EMAIL_ADDRESS>    tls: true

Traceback (if applicable):
2019-02-08 10:41:01 ERROR (MainThread) [homeassistant.core] Error doing job: Exception in callback _SelectorSocketTransport._read_ready()
Traceback (most recent call last):
  File "/usr/lib/python3.6/asyncio/events.py", line 145, in _run
    self._callback(*self._args)
  File "/usr/lib/python3.6/asyncio/selector_events.py", line 732, in _read_ready
    self._protocol.data_received(data)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/xmlstream.py", line 406, in data_received
    self._spawn_event(xml)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/xmlstream.py", line 970, in _spawn_event
    stanza = self._build_stanza(xml)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/xmlstream.py", line 951, in _build_stanza
    stanza = stanza_type(self, xml)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 1389, in __init__
    ElementBase.__init__(self, xml, parent)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 415, in __init__
    if self.setup(xml):
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/stanza/stream_features.py", line 27, in setup
    self.values = self.values
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 614, in _set_stanza_values
    self[full_interface] = value
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 752, in __setitem__
    lang=lang)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 958, in _set_sub_text
    return self._del_sub(name, lang=lang)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 1039, in _del_sub
    parent = self.xml.find(parent_path)
  File "/usr/lib/python3.6/xml/etree/ElementTree.py", line 298, in find
    return ElementPath.find(self, path, namespaces)
  File "/usr/lib/python3.6/xml/etree/ElementPath.py", line 298, in find
    return next(iterfind(elem, path, namespaces), None)
TypeError: 'NoneType' object is not an iterator

Additional information:

same here with raspbian strech

My component (also based on slixmpp) fails with the same error since 0.87.
It only happens in my "fully configured" HA instance. In the stripped down dev instance it still works fine.
The error is not always there. After a couple of restarts it starts to work again.

@marconfus  May I ask which component you use? Do you have a custom component?

Yes, it's a custom climate device for Bosch thermostats which isn't in the official codebase yet.
https://github.com/marconfus/ha-nefit-ng
It uses the same XMPP library and shows the same error. To validate this I also installed the XMPP notify component. Unfortunately I am not able to reproduce it in my dev environment and haven't found a good way to debug my prod env which is in a Hass.io installation.
Are you able to reproduce the error in a more or less empty/base venv installation of HA?

I dunno what they changed but it seems group chats don't work but direct messages do.. For example  I got my xiaomi map sent but not all my notifications about lights etc... the only backtrace I have is the part I posted

Hm, the functions in the stacktrace get the exact same parameters in case it works and when it fails. Also when it works, it works all the time and when it fails it fails all the time until you restart the python process...
As the error only triggers when certain(?) other components are loaded, I guess it's some kind of internal error/racecondition in async Python or elsewhere. But I have absolutely no idea how to debug this...

I figured out that one to one works bit group chat fails

So, I modified slixmpp to use lxml instead of xml.
In stanzabase.py and xmlstream.py replace
from xml.etree import cElementTree as ET
with
from lxml import etree as ET
and added a try/catch block to stanzabase.py around the line from the stacktrace.
            try:
                parent = self.xml.find(parent_path)
            except:
                parent = None

This seems to works all the time....

I've opened a bug report at slixmpp:
https://dev.louiz.org/issues/3434

I've opened a bug report at slixmpp:
https://lab.louiz.org/poezio/slixmpp/issues/3429

I guess xmpp will be fixed in version 0.89 ?

do we have some news here ? I only get pictures sent to my xmpp client.

I don't think there is anybod working on this. I guess it's because the bug only affects a couple of users. You could try to find the combination of active components that are necessary to trigger the bug. I.e. do you see the bug in an HA installation with only the xmpp component installed? And then add your other components until the bug triggers...
I have a workaround for my component and not enough time to dig deeper. Sorry.

Could you share your workaround lease and i will add it :) would be nice ..
thanks mate

I have forked slixmpp and used that instead:
https://github.com/poezio/slixmpp/compare/master...marconfus:master
https://github.com/marconfus/ha-nefit-ng/commit/89310658ff192f242fd3c508f423286ca36000d2

@marconfus works like a charm. I also forked your repo now :)

I get a similar error. Maybe it is related (see below)
I just started with HA, so my installation is not that complex to mind. Maybe it helps, when I list it here:

HA 0.88.2 (started with 0.87)
Hassio/Docker install on a raspberry pi running raspbian
Addons: Zigbee2Mqtt, Mosquitto MQTT broker, Check Home Assistant configuration

My configuration contains:
notify:
  - name: jabber
    platform: xmpp
    sender<EMAIL_ADDRESS>    password: SECRET
    recipient<EMAIL_ADDRESS>
The error I get is:
2019-02-23 21:42:36 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport
Traceback (most recent call last):
  File "uvloop/handles/stream.pyx", line 827, in uvloop.loop.__uv_stream_on_read_impl
  File "/usr/local/lib/python3.7/site-packages/slixmpp/xmlstream/xmlstream.py", line 406, in data_received
self._spawn_event(xml)
  File "/usr/local/lib/python3.7/site-packages/slixmpp/xmlstream/xmlstream.py", line 970, in _spawn_event
stanza = self._build_stanza(xml)
  File "/usr/local/lib/python3.7/site-packages/slixmpp/xmlstream/xmlstream.py", line 951, in _build_stanza
stanza = stanza_type(self, xml)
  File "/usr/local/lib/python3.7/site-packages/slixmpp/xmlstream/stanzabase.py", line 1390, in __init__
ElementBase.__init__(self, xml, parent)
  File "/usr/local/lib/python3.7/site-packages/slixmpp/xmlstream/stanzabase.py", line 416, in __init__
if self.setup(xml):
  File "/usr/local/lib/python3.7/site-packages/slixmpp/stanza/stream_features.py", line 27, in setup
self.values = self.values
  File "/usr/local/lib/python3.7/site-packages/slixmpp/xmlstream/stanzabase.py", line 615, in _set_stanza_values
self[full_interface] = value
  File "/usr/local/lib/python3.7/site-packages/slixmpp/xmlstream/stanzabase.py", line 753, in __setitem__
lang=lang)
  File "/usr/local/lib/python3.7/site-packages/slixmpp/xmlstream/stanzabase.py", line 959, in _set_sub_text
return self._del_sub(name, lang=lang)
  File "/usr/local/lib/python3.7/site-packages/slixmpp/xmlstream/stanzabase.py", line 1040, in _del_sub
parent = self.xml.find(parent_path)
  File "/usr/local/lib/python3.7/xml/etree/ElementTree.py", line 299, in find
return ElementPath.find(self, path, namespaces)
  File "/usr/local/lib/python3.7/xml/etree/ElementPath.py", line 307, in find
return next(iterfind(elem, path, namespaces), None)
TypeError: 'NoneType' object is not an iterator

Just tried the workaround and HA is finally sending messages. Thanks a lot 👍

To test the workaround, I modified the source files in the homeassistant docker instance of my hassio install. Which works like a charm.
But: That changes are lost, if I restart HA.
When using normal docker images, I would use a custom dockerfile and make my modifications there. But the image is managed by the hassio supervisor which I don't know a lot about.
Do you have any ideas how to make changes like applying this workaround persistent on a hassio install?

You could copy the original component and install it as a custom_component. The documentation says, that that is supported:
https://developers.home-assistant.io/docs/en/creating_component_loading.html
Of course that is a terrible hack and it would be better to find the real cause of the problem...

Thanks for the fast answer. I will try this.
I hope the real cause can be found soon :-)

Adding my name to this issue. Testing use of slixmpp for Harmony component and getting same error.

I get new issue when trying to send a local file:
Traceback (most recent call last):
  File "/usr/lib/python3.6/asyncio/events.py", line 145, in _run
    self._callback(*self._args)
  File "/usr/lib/python3.6/asyncio/selector_events.py", line 976, in _read_ready
    self._protocol.data_received(data)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/xmlstream.py", line 407, in data_received
    self._spawn_event(xml)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/xmlstream.py", line 971, in _spawn_event
    stanza = self._build_stanza(xml)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/xmlstream.py", line 952, in _build_stanza
    stanza = stanza_type(self, xml)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/stanza/iq.py", line 70, in __init__
    StanzaBase.__init__(self, *args, **kwargs)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 1394, in __init__
    ElementBase.__init__(self, xml, parent)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 427, in __init__
    reuse=False)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 508, in init_plugin
    plugin = plugin_class(parent=self, xml=existing_xml)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 427, in __init__
    reuse=False)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 508, in init_plugin
    plugin = plugin_class(parent=self, xml=existing_xml)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/plugins/xep_0004/stanza/form.py", line 35, in __init__
    ElementBase.__init__(self, *args, **kwargs)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 427, in __init__
    reuse=False)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 520, in init_plugin
    self.init_plugin(plugin_class.plugin_multi_attrib)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 508, in init_plugin
    plugin = plugin_class(parent=self, xml=existing_xml)
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 417, in __init__
    if self.setup(xml):
  File "/home/hass/homeassistant/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 112, in setup
    self.xml = ET.Element('')
  File "src/lxml/etree.pyx", line 2998, in lxml.etree.Element
  File "src/lxml/apihelpers.pxi", line 95, in lxml.etree._makeElement
  File "src/lxml/apihelpers.pxi", line 1549, in lxml.etree._getNsTag
  File "src/lxml/apihelpers.pxi", line 1584, in lxml.etree.__getNsTag
ValueError: Empty tag name

my script:
  3_send_jabber_message_with_local_image_path:
    alias: "Send Image via Jabber from local file"
    sequence:
      - service: notify.thorsten
        data:
          title: ""
          message: ""
          data:
            path: "/home/hass/.homeassistant/cam_snap_shots/front-door/record.mp4"

Any chance of reverting the slixmpp version used by hass to the one used in 0.86.4?

@Human Would be the best I think. But you can temporairly use the "dirty" workaround described above. It works but like mentioned: httpupload won't work

I asked in slixmpp channel for this issue and apparently we use wrong XML library

Yes, in my "dirty fix" I changed the XML parser to lxml. Apparently this leeds to other errors in your scenario.

I just updated to Python 3.7.3 and issue is still present. :-( Was hoping maybe a fix through there. .
If I use my library (aioharmony) outside of Home Assistant I have no issues. If I use it within HA then I get the error.

Here it's even worse .. notify component not showing up at all.nithing related in logs I'll activate debit and provide details asap

LOGS:
2019-04-15 16:09:29 INFO (MainThread) [homeassistant.loader] Loaded xmpp from homeassistant.components.xmpp
File "/home/hass/homeassistant/lib/python3.6/site-packages/homeassistant/components/xmpp/notify.py", line 2
but:
2019-04-15 19:08:06 ERROR (MainThread) [homeassistant.components.automation] Error while executing automation automation.notify_state_change. Service not found for call_service at pos 1: (ServiceNotFound(...), 'Service notify.thorsten not found')

File "", line 665, in _load_unlocked
File "", line 674, in exec_module
File "", line 781, in get_code
File "", line 741, in source_to_code
File "", line 219, in _call_with_frames_removed
File "/home/hass/homeassistant/lib/python3.6/site-packages/homeassistant/components/xmpp/notify.py", line 2
Jabber (XMPP) notification service.
^
SyntaxError: invalid syntax

OK! I found my issue setting up the component. A # has benn added on line 2 :P. But httpupload still not working

Any chance of reverting the slixmpp version used by hass to the one used in 0.86.4?

slixmpp in 0.86.4 was 1.4.1. For my component (aioharmony) that I'm trying to get to work with XMPP I have tried both 1.4.1 and 1.4.2 in HA; both fail.
No issues outside of HA.

I am sure it is not just slixmpp version related but something global in hass. I'd like seeing a dev for this component giving a feedback here.. unfortunately the xmpp platform is underestimated and not used that often like other platforms. But I think it should be maintained like every platform

Been adding a bunch of debug info to my local copy of slixmpp but so far haven't found anything. From what I can tell it is all going and working the same.
But, I'm far from an expert when it comes to XMPP and the XML objects.
I've also been going through the release notes from 0.87 (as 0.86.4 was working and 0.87 not based on 1st posts here) but haven't been able to find anything or anything standing out that could be the explanation for it breaking.

@ehendrix23 Are you able to do a git bisect to narrow down the commit that introduced the bug?

I could .... if I knew how. :-)

@ehendrix23 Does this help? https://git-scm.com/docs/git-bisect
If I'm reading the tags right, you'd want to start the bisect at the commit for tag for 0.87 ( c366fa00d8f63c4ebe8398280ed342bd4903f7c0 ) and mark it as bad then mark the commit for tag 0.86.4 ( aa29eeba04a68234a46c298fabef88d3635922f5 ) as good. Then the bisect process will cut the commits between the two in half, letting you test each one and mark the result as good or bad. After a few iterations, it'll tell you which commit specifically introduced the bug.

Just to confirm that i have the same issue (object is not an iterator), that i do prefer XMPP over other notification services, and I'm waiting for it to be resolved :).  I am no programmer unfortunately so may not be of any help other than providing my logs if required.

Same issue here, not sure how the workaround works, but xmpp is the only way to send proper notifications. Please fix.

Strangely after upgrading today to --pre homeassistant 0.94.0 XMPP works like a charm... maybe a try it's worth @Glotzon

Can't confirm that homeassistant 0.94 works. The problem remains for me. I still have to use a custom component with the slixmpp package of @marconfus

Can't confirm either:
Traceback (most recent call last):
  File "/usr/lib/python3.5/asyncio/events.py", line 126, in _run
    self._callback(*self._args)
  File "/usr/lib/python3.5/asyncio/selector_events.py", line 730, in _read_ready
    self._protocol.data_received(data)
  File "/srv/homeassistant/lib/python3.5/site-packages/slixmpp/xmlstream/xmlstream.py", line 406, in data_received
    self._spawn_event(xml)
  File "/srv/homeassistant/lib/python3.5/site-packages/slixmpp/xmlstream/xmlstream.py", line 970, in _spawn_event
    stanza = self._build_stanza(xml)
  File "/srv/homeassistant/lib/python3.5/site-packages/slixmpp/xmlstream/xmlstream.py", line 951, in _build_stanza
    stanza = stanza_type(self, xml)
  File "/srv/homeassistant/lib/python3.5/site-packages/slixmpp/xmlstream/stanzabase.py", line 1390, in __init__
    ElementBase.__init__(self, xml, parent)
  File "/srv/homeassistant/lib/python3.5/site-packages/slixmpp/xmlstream/stanzabase.py", line 416, in __init__
    if self.setup(xml):
  File "/srv/homeassistant/lib/python3.5/site-packages/slixmpp/stanza/stream_features.py", line 27, in setup
    self.values = self.values
  File "/srv/homeassistant/lib/python3.5/site-packages/slixmpp/xmlstream/stanzabase.py", line 615, in _set_stanza_values
    self[full_interface] = value
  File "/srv/homeassistant/lib/python3.5/site-packages/slixmpp/xmlstream/stanzabase.py", line 753, in __setitem__
    lang=lang)
  File "/srv/homeassistant/lib/python3.5/site-packages/slixmpp/xmlstream/stanzabase.py", line 959, in _set_sub_text
    return self._del_sub(name, lang=lang)
  File "/srv/homeassistant/lib/python3.5/site-packages/slixmpp/xmlstream/stanzabase.py", line 1040, in _del_sub
    parent = self.xml.find(parent_path)
  File "/usr/lib/python3.5/xml/etree/ElementTree.py", line 297, in find
    return ElementPath.find(self, path, namespaces)
  File "/usr/lib/python3.5/xml/etree/ElementPath.py", line 298, in find
    return next(iterfind(elem, path, namespaces), None)
TypeError: 'NoneType' object is not an iterator

Thats' weird and strange.. I had similar problem with this XMPP and after just upgrading to 0.94 it was fixed. I know nothing was changed in XMPP component.. I am confused :P

Problem continues on 0.94.0
TypeError: 'NoneType' object is not an iterator

Also confirm that not resolved in 0.94. NoneType' object is not an iterator

I also get the same error after updating to 0.94.

Same here on 0.94.3.

Same stack-trace for me in 0.94.3

Still the same bug in 0.94.4

In 0.95.4, the line numbers have changed, but it's still the same error:
Traceback (most recent call last):
  File "/usr/lib/python3.6/asyncio/events.py", line 145, in _run
    self._callback(*self._args)
  File "/usr/lib/python3.6/asyncio/selector_events.py", line 721, in _read_ready
    self._protocol.data_received(data)
  File "/home/igo/.homeassistant/deps/lib/python3.6/site-packages/slixmpp/xmlstream/xmlstream.py", line 406, in data_received
    self._spawn_event(xml)
  File "/home/igo/.homeassistant/deps/lib/python3.6/site-packages/slixmpp/xmlstream/xmlstream.py", line 970, in _spawn_event
    stanza = self._build_stanza(xml)
  File "/home/igo/.homeassistant/deps/lib/python3.6/site-packages/slixmpp/xmlstream/xmlstream.py", line 951, in _build_stanza
    stanza = stanza_type(self, xml)
  File "/home/igo/.homeassistant/deps/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 1390, in __init__
    ElementBase.__init__(self, xml, parent)
  File "/home/igo/.homeassistant/deps/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 416, in __init__
    if self.setup(xml):
  File "/home/igo/.homeassistant/deps/lib/python3.6/site-packages/slixmpp/stanza/stream_features.py", line 27, in setup
    self.values = self.values
  File "/home/igo/.homeassistant/deps/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 615, in _set_stanza_values
    self[full_interface] = value
  File "/home/igo/.homeassistant/deps/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 753, in __setitem__
    lang=lang)
  File "/home/igo/.homeassistant/deps/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 959, in _set_sub_text
    return self._del_sub(name, lang=lang)
  File "/home/igo/.homeassistant/deps/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 1040, in _del_sub
    parent = self.xml.find(parent_path)
  File "/usr/lib/python3.6/xml/etree/ElementTree.py", line 298, in find
    return ElementPath.find(self, path, namespaces)
  File "/usr/lib/python3.6/xml/etree/ElementPath.py", line 298, in find
    return next(iterfind(elem, path, namespaces), None)
TypeError: 'NoneType' object is not an iterator

@fabaff Hi! I and others have implemented these small changes described here to get XMPP working again in HASS. As the XMPP maintainer, if this were turned into a PR, would you accept the change?

I'm using Hassos. Where can I find the stanzabase.py and xmlstream.py files?

@fabaff Hi! I and others have implemented these small changes described here to get XMPP working again in HASS. As the XMPP maintainer, if this were turned into a PR, would you accept the change?

The dirty hack of mine you referenced is not in the homeassistant code, so it cannot be fixed here. It's the most obscure python problem I have ever seen and unfortunately nobody has an idea how to fix it. As long as I know, nobody is even able to reproduce it 100% (i.e. create a demo ha config that triggers the bug).
If, at all, a workaround could be added to the slixmpp library -> https://github.com/poezio/slixmpp/pull/17
But this seems to lead to other errors.

@marconfus Well, it could be fixed by forking slixmpp and making HASS use the fork instead of the mainline version.
Before I applied your workaround, I had 100% XMPP failure. If I get some time, I could derive a minimal example HASS configuration that causes the bug.

@Human Have you already tried to derive a minimal configuration that causes the bug?

Back to this issue... Thats ODDDD!!!  :P
ok.. jokes bisides .. Would be nice if someone would seriously take car of it if not Home assistant will loose this component.And the fact that maybe not that much users use this component doesn't mean it is not that important for them.
So please: could someone seriously throw an eye on this issue please?

@meisterlampe Unfortunately, no. I have seen no side effects of implementing the workaround, though.

For me, in 101.3 sending XMPP messages still works with fix. But I do believe that messages get lost every now and then.

Hello... All of sudden xmpp started working again. Dunno the reason but i am happy about it anyway :) i am on latest dev version and can confirm it works again.

Good news. Will try the upcoming 102 release without the fix/workaround in the next days

I updated to 102 but still got no success with xmpp messages. I tried plain text as well as messages with picture upload.
Traceback (most recent call last):
  File "/usr/lib/python3.7/asyncio/selector_events.py", line 813, in _read_ready__data_received
    self._protocol.data_received(data)
  File "/srv/homeassistant/lib/python3.7/site-packages/slixmpp/xmlstream/xmlstream.py", line 406, in data_received
    self._spawn_event(xml)
  File "/srv/homeassistant/lib/python3.7/site-packages/slixmpp/xmlstream/xmlstream.py", line 970, in _spawn_event
    stanza = self._build_stanza(xml)
  File "/srv/homeassistant/lib/python3.7/site-packages/slixmpp/xmlstream/xmlstream.py", line 951, in _build_stanza
    stanza = stanza_type(self, xml)
  File "/srv/homeassistant/lib/python3.7/site-packages/slixmpp/xmlstream/stanzabase.py", line 1390, in __init__
    ElementBase.__init__(self, xml, parent)
  File "/srv/homeassistant/lib/python3.7/site-packages/slixmpp/xmlstream/stanzabase.py", line 416, in __init__
    if self.setup(xml):
  File "/srv/homeassistant/lib/python3.7/site-packages/slixmpp/stanza/stream_features.py", line 27, in setup
    self.values = self.values
  File "/srv/homeassistant/lib/python3.7/site-packages/slixmpp/xmlstream/stanzabase.py", line 615, in _set_stanza_values
    self[full_interface] = value
  File "/srv/homeassistant/lib/python3.7/site-packages/slixmpp/xmlstream/stanzabase.py", line 753, in __setitem__
    lang=lang)
  File "/srv/homeassistant/lib/python3.7/site-packages/slixmpp/xmlstream/stanzabase.py", line 959, in _set_sub_text
    return self._del_sub(name, lang=lang)
  File "/srv/homeassistant/lib/python3.7/site-packages/slixmpp/xmlstream/stanzabase.py", line 1040, in _del_sub
    parent = self.xml.find(parent_path)
  File "/usr/lib/python3.7/xml/etree/ElementTree.py", line 299, in find
    return ElementPath.find(self, path, namespaces)
  File "/usr/lib/python3.7/xml/etree/ElementPath.py", line 307, in find
    return next(iterfind(elem, path, namespaces), None)
TypeError: 'NoneType' object is not an iterator

I dunno why this always appears.... for me almost each upgrade of homeassistant will break the component. Then.. all of sudden and after multiple restarts and longer times of running home assistant it works again. But i fear that some messages won't be sent from time to time. I am missing some messages.. Unfortunately nothing moves here in this threat and also on xmpp dev site nothing moves really forward. IT's a bit a pity as i thought home assistant i privacy orientated and i refuse using whatsapp telegram and co for my sensitive data sent by a notifier.
Would be really awesome not only to library issue threats but also get in contact with them and try solving this issue together.

Now I saw your post about the custom component in the other issue ( https://github.com/home-assistant/home-assistant/issues/28611 ).
Thanks for the info.
I guess I will also test the approach by @mariohock this week. I find the bi-directional communication feature interesting.

@mariohock  Setting up appdaemon in a docker container on my pi was really a pain.
Anyway chatty itself was up and running within no time and I really like the simplicity of the code as well as that it is easy to extend. Again: Thanks for sharing!

I just upgraded to 0.103 from 0.98 and started getting this error.  The work around above worked for me.
https://github.com/home-assistant/home-assistant/issues/20860#issuecomment-462454805

@thundergreen Just tested your custom_component approach and it is working without any problems. The same code starts working, when beeing used in a custom component ...really weird and I guess @mariohock's race condition assumption could be correct.

I confirm I just enabled custom component again and it's working perfectly. We should make this. Public

@meisterlampe  unfortunately it did not work for me ... do u use custom slixmpp out of the issue here or the original sixmpp?

@thundergreen Just tested your custom_component approach and it is working without any problems. The same code starts working, when beeing used in a custom component ...really weird and I guess @mariohock's race condition assumption could be correct.

Do u use the https://github.com/marconfus/slixmpp/archive/master.zip#slixmpp==<IP_ADDRESS> or the slixmpp 1.4.2 standard?

I'm using the original slixmpp from home assistant. I just copied the files to custom_components/xmpp and it seems to work. But I haven't tested it a lot.
So for you it stopped working after while?

es  directly after restarting hass it stopped working again.ill upgrade to latest beta to see if it then works again ..for 5he moment I 8se the custom slixmpp library in this post

slixmpp has been updated recently (now at 1.5.1), and now includes a fix that should take care of this problem.


Adding MultiTypedList data structure

The new MultiTypedList structure behaves in a similar way to the List structure, but provides facilities for limited polymorphic serialization, unlike the normal List structure.  To use it, you need to specify exactly which types you plan to store in the structure, in a similar way to how UnityEvent is done.
//List that supports adding types SubClassA, SubClassB, and SubClassC
public class MyListType : MultiTypedList<BaseClass, SubClassA, SubClassB, SubClassC> { }
To test:

[ ] Verify that code looks good
[ ] Verify that tests pass
[ ] Verify that you can create multi typed lists and that they serialize properly

Closing this until I add some additional features