Logging breaks transaction when something with db connection is logged

Logging breaks transaction when something with db connection is logged. BaseVarDumper::exportInternal is using serialize which is closing db connection (calling close inside __sleep)
What steps will reproduce the problem?
Start transaction, do some changes in db and then log something including db connection.
$transaction = \Yii::$app->db->beginTransaction();
// do some changes in db
(new LocationZip([
            'zip' => 12345,
            'federation' => 'Sachsen'
]))->save();

// see changes exists in db
$newRecord = LocationZip::find()->where(['zip' => 12345,])->one();

// log something that has db connection inside (it could be stacktrace of exception)
\Yii::info(\Yii::$app->db);

// connection to db was closed while trying to serialize log message so transaction is lost
$newRecord = LocationZip::find()->where(['zip' => 12345,])->one();

// will throw exception because transaction doesn't exists anymore
$transaction->commit();

What is the expected result?
Logging should't do side effects like closing db connections
Additional info

Q
A

Yii version
2.0.12

PHP version
7.1

Operating system
Ubuntu

May be resolve it with
\Yii::info(clone \Yii::$app->db);

?

@bscheshirwork  It was only simple example, your solution won't work if db connection is somewhere in logged stacktrace.

i.e. title can read as "Serialize breaks transaction anything"

related to #13890

Why __sleep() closes connection?

to not serialize the PDO instance. This is mainly to know we are not connected after unserializing the connection. See https://github.com/yiisoft/yii2/pull/10149

This does not seem right to me. Serializing object should not affects it's state. unserialize(serialize($db)) should be equivalent to clone $db;

This does not seem right to me. Serializing object should not affects it's state. unserialize(serialize($db)) should be equivalent to clone $db;

This is impossible, since any PHP resource including DB connection can not be shared between different PHP processes.

This is mainly to know we are not connected after unserializing the connection.

No actual connection closing is perfromed at Connection::close() - it simply unsets the related PDO object - nullifies it. In case there is another reference to this PDO object - the connection will still stand.
Only nullifing of the last reference to the PDO object will cause its actual destruction an thus DB connection close.
Thus in general the issue described here should not ever appear.

Then cloned $db should open it's own connection to DB. If I have two separate Connection instances, they should have separate connections to DB.  I don't see any reason to magically close connections from source instance.

@rob006, see https://stackoverflow.com/questions/15620012/serialize-file-resource for instance.

@klimov-paul Sorry, don't get your point. If I do $db1 = clone $db; I will have two Connection instances with with two separate connections to DB. Connection of $db will not be magically closed, $db1 will just open new one. It should work the same in case of unserialize(serialize($db)).

Statement unserialize(serialize($db)) has absolutely no purpose. It is unlikely you need to unserialize the serialized object withing the same process. Object serialization is performed to save object for the another process processing, thus serialization process should be aware of such possibility and prevent passing stream resources between different processes.

This is just a example. I'm not talking about serializing resources, but about not closing resource that is used by existing object. Serializing object should not affect its instance.

Unit test to reproduce
abstract class ConnectionTest extends DatabaseTestCase
{
    // ...

    public function testSerialize()
    {
        $connection = $this->getConnection(false, false);
        $connection->open();
        $serialized = serialize($connection);

        $this->assertNotNull($connection->pdo);

        $unserialized = unserialize($serialized);
        $this->assertInstanceOf('yii\db\Connection', $unserialized);
        $this->assertNull($unserialized->pdo);

        $this->assertEquals(123, $unserialized->createCommand('SELECT 123')->queryScalar());
    }
}

For me this is an unexpected PHP behavior as __sleep() applied to the instance itself, but it is as it is.
The only possible solution I can see is unsetting PDO at __wakeup() instead of __sleep().

No go - ends up with Exception:

PDOException: You cannot serialize or unserialize PDO instances

There is a example in documentation how to handle serialization and PDO: http://php.net/manual/en/language.oop5.magic.php#object.sleep
$pdo attribute should not be serialized.

Resolved by commit 9e6f9e3b6d41c918718b953968cf631c6a03ad73


Fix/workaround for #204

Fix/workaround for #204 - https://github.com/jm-73/Indego/issues/204

Maybe not necessary as the integration started working again 2023-11-24?


Tang et. al. Dataset Groundtruth Visualization

Hello, first of all congratulations on this great work.
I would like to know how you generated to 3d mesh from tang. et. al. groundtruth depth file as in the following figure

:

Hi. Thanks a lot for your message. This figure was made in MATLAB using surfl. You can take a look at the MATLAB visualization code for more information. Note that we do not generate the mesh for this visualization.
However, Tang et al. also provide a code to generate mesh from the depth that might be useful for your case, which we also adopt in our inference code here.


Incorrect metadata parsing when run outside of English-speaking countries

Since there doesn't appear to be any public facing API call to get just metadata, it is all being parsed from the HTML. The only way I have found so far to differentiate between newspaper, magazine, and book is by parsing the English text "Preview this (content type)", but this is failing when run in other countries since the content is being served in different languages regardless of URL.
At present, this may result in newspapers not being downloaded at full resolution (to a point that they are illegible) and all periodicals being saved directly into the target directory rather than into sub-directories as intended depending on where you run the program from geographically.
A new method of determining content type will need to be discovered. I think the types of metadata available can be used to distinguish between periodical and book, but not between magazine and newspaper as far as I can tell. I could potentially just remove the content type flag altogether and always greedily process all data available, but this may result in extra API calls when not processing newspapers (API calls to get an image link for a given page may contain links for adjacent pages as well, and these are used when the content type is not newspaper).

Issue partially resolved in v0.3.2 by adding "&hl=eng" to end of book URLs to force English language, and (hopefully) fully resolved in v0.3.3 by doing the same to URLs used for batch operations.


Installation note

Installation note

Thanks @spookiecookie! Let's move the note to the installation section of the README though.
Under the gem install byebug line:
+
+ Or if you use `bundler`,
+
+ ```shell
+ bundle add byebug
+ ```

Great thank you:)!
2017-12-24 03:28 "David Rodríguez"<EMAIL_ADDRESS>rašė:

Thanks @spookiecookie https://github.com/spookiecookie! Let's move the
note to the installation section of the README though.
Under the gem install byebug line:
++ Or if you use bundler,+ + shell+ bundle add byebug+
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/deivid-rodriguez/byebug/pull/389#issuecomment-353759492,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE9FzwRd7GgigjLQ5IfPLJpbYptpxpyLks5tDai0gaJpZM4RG_eF
.


Update Resource Models Details Cards

Heritage Site Resource Model Details Card:
TBD (after Xmas break)
Legislative Act Details Card:

[x] Authority
[x] Legal Instrument
[x] Act Section
[x] Recognition Type
[x] Validity Period

Government Details Card:

[x] Gov name
[x] Gov type
[ ] Gov location

Government Person Details Card:

[ ] Name
[ ] username
[ ] Contact
[ ] Gov Association

Site Submission Details Card:

[ ] Submitting Government Name
[ ] Submission Date
[ ] Completion Date
[ ] Submitted Sites Number
[ ] Requested Operation
[ ] Information Provided
[ ] Historic Site(s)

@emjohnst - Are you looking for the government location map or address? If it's the map that will need to wait until after MVP.

@bferguso that's fine, I'll update ticket to remove that.


Error: This integration doesn't support provided entity!

Describe the bug
I have been using the MeteoalarmCard in conjunction with the core meteoalarm integration for a few weeks without any issues. However, it has stopped working a few days ago because it supposedly doesn't support the same provided binary_sensor.meteoalarm entity anymore which worked fine until recently.
To Reproduce

Add MeteoalarmCard to a Lovelace dashboard
Click on edit
Select entity binary_sensor.meteoalarm

Screenshots

System (please complete the following information):

Card version: v1.9.0
Integration type: Core
Installation type: HACS

Hey, please attach logs from your console

I'm not entirely sure what you mean with logs as I cannot find any entries in my home assistant log or any log entry in dev tools. Sorry, I'm a noob in this regard :(. Could you please provide more detailed instructions?

@DarkWarden85  You can access your browser console by pressing F12, it may be different depending on your browser, if that doesn't work just google <your browser> developer console.
Then i will need a screenshot of attributes of binary_sensor.meteoalarm sensor from your HA dev tools:

Thanks @MrBartusek for clarification.
Logs:
`app.62541dd1.js:13499 The main 'lit-element' module entrypoint is deprecated. Please update your imports to use the 'lit' package: 'lit' and 'lit/decorators.ts' or import from 'lit-element/lit-element.ts'.
55704 @ app.62541dd1.js:13499
:8123/local/scheduler-card/dist/scheduler-card.js?v=0:1 Failed to load resource: the server responded with a status of 404 (Not Found)
simple-thermostat.js:285 simple-thermostat: 2.4.2
vertical-stack-in-card.js:1 vertical-stack-in-cardVersion: 0.4.1
layout-card.js?hacstag=156434866230:223 LAYOUT-CARD 2.3.0 IS INSTALLED
slider-entity-row.js:59 SLIDER-ENTITY-ROW 17.1.0 IS INSTALLED
banner-card.js:162 banner-card: 0.12.0
paper-buttons-row.js?hacstag=244872232060:1  PAPER-BUTTONS-ROW  0.6.0
fold-entity-row.js:42 FOLD-ENTITY-ROW 20.0.4 IS INSTALLED
decluttering-card.js:831  DECLUTTERING-CARD    Version 0.6.3
chunk.59536e6ae6caec2cfd80.js:1 Uncaught (in promise) http://homeassistant.local:8123/local/scheduler-card/dist/scheduler-card.js?v=0
multiple-entity-row.js:1  MULTIPLE-ENTITY-ROW  4.2.0
card-tools.js:90 CARD-TOOLS 2.1.2 IS INSTALLED  DeviceID: 2902d886-22cbeb65
auto-entities.js:210 AUTO-ENTITIES 1.9.1 IS INSTALLED
button-card.js:425   BUTTON-CARD   Version 3.4.2
mini-graph-card-bundle.js:1  MINI-GRAPH-CARD  0.10.0
meteoalarm-card.js?hacstag=361205663190:339 === METEOALARM CARD ERROR ===
Report issue: https://bit.ly/3hK1hL4
Error: This integration doesn't support provided entity!
at HTMLElement.getAttributes (meteoalarm-card.js?hacstag=361205663190:289)
at HTMLElement.render (meteoalarm-card.js?hacstag=361205663190:325)
at HTMLElement.update (meteoalarm-card.js?hacstag=361205663190:159)
at HTMLElement.performUpdate (meteoalarm-card.js?hacstag=361205663190:134)
at HTMLElement._enqueueUpdate (meteoalarm-card.js?hacstag=361205663190:134)
render @ meteoalarm-card.js?hacstag=361205663190:339
secondaryinfo-entity-row.js:38 Uncaught (in promise) TypeError: Cannot read property 'querySelector' of null
at HTMLElement._updateElement (secondaryinfo-entity-row.js:38)
secondaryinfo-entity-row.js:38 Uncaught (in promise) TypeError: Cannot read property 'querySelector' of null
at HTMLElement._updateElement (secondaryinfo-entity-row.js:38)
secondaryinfo-entity-row.js:38 Uncaught (in promise) TypeError: Cannot read property 'querySelector' of null
at HTMLElement._updateElement (secondaryinfo-entity-row.js:38)
secondaryinfo-entity-row.js:38 Uncaught (in promise) TypeError: Cannot read property 'querySelector' of null
at HTMLElement._updateElement (secondaryinfo-entity-row.js:38)
secondaryinfo-entity-row.js:38 Uncaught (in promise) TypeError: Cannot read property 'querySelector' of null
at HTMLElement._updateElement (secondaryinfo-entity-row.js:38)
secondaryinfo-entity-row.js:38 Uncaught (in promise) TypeError: Cannot read property 'querySelector' of null
at HTMLElement._updateElement (secondaryinfo-entity-row.js:38)
secondaryinfo-entity-row.js:38 Uncaught (in promise) TypeError: Cannot read property 'querySelector' of null
at HTMLElement._updateElement (secondaryinfo-entity-row.js:38)
meteoalarm-card.js?hacstag=361205663190:339 === METEOALARM CARD ERROR ===
Report issue: https://bit.ly/3hK1hL4
Error: This integration doesn't support provided entity!
at HTMLElement.getAttributes (meteoalarm-card.js?hacstag=361205663190:289)
at HTMLElement.render (meteoalarm-card.js?hacstag=361205663190:325)
at HTMLElement.update (meteoalarm-card.js?hacstag=361205663190:159)
at HTMLElement.performUpdate (meteoalarm-card.js?hacstag=361205663190:134)
at HTMLElement._enqueueUpdate (meteoalarm-card.js?hacstag=361205663190:134)
render @ meteoalarm-card.js?hacstag=361205663190:339
secondaryinfo-entity-row.js:38 Uncaught (in promise) TypeError: Cannot read property 'querySelector' of null
at HTMLElement._updateElement (secondaryinfo-entity-row.js:38)
secondaryinfo-entity-row.js:38 Uncaught (in promise) TypeError: Cannot read property 'querySelector' of null
at HTMLElement._updateElement (secondaryinfo-entity-row.js:38)
secondaryinfo-entity-row.js:38 Uncaught (in promise) TypeError: Cannot read property 'querySelector' of null
at HTMLElement._updateElement (secondaryinfo-entity-row.js:38)
secondaryinfo-entity-row.js:38 Uncaught (in promise) TypeError: Cannot read property 'querySelector' of null
at HTMLElement._updateElement (secondaryinfo-entity-row.js:38)
secondaryinfo-entity-row.js:38 Uncaught (in promise) TypeError: Cannot read property 'querySelector' of null
at HTMLElement._updateElement (secondaryinfo-entity-row.js:38)
secondaryinfo-entity-row.js:38 Uncaught (in promise) TypeError: Cannot read property 'querySelector' of null
at HTMLElement._updateElement (secondaryinfo-entity-row.js:38)
secondaryinfo-entity-row.js:38 Uncaught (in promise) TypeError: Cannot read property 'querySelector' of null
at HTMLElement._updateElement (secondaryinfo-entity-row.js:38)
meteoalarm-card.js?hacstag=361205663190:339 === METEOALARM CARD ERROR ===
Report issue: https://bit.ly/3hK1hL4
Error: This integration doesn't support provided entity!
at HTMLElement.getAttributes (meteoalarm-card.js?hacstag=361205663190:289)
at HTMLElement.render (meteoalarm-card.js?hacstag=361205663190:325)
at HTMLElement.update (meteoalarm-card.js?hacstag=361205663190:159)
at HTMLElement.performUpdate (meteoalarm-card.js?hacstag=361205663190:134)
at HTMLElement._enqueueUpdate (meteoalarm-card.js?hacstag=361205663190:134)
render @ meteoalarm-card.js?hacstag=361205663190:339
fold-entity-row.js:1 Uncaught (in promise) TypeError: Cannot read property 'style' of null
at HTMLElement.applyStyle (fold-entity-row.js:1)
fold-entity-row.js:1 Uncaught (in promise) TypeError: Cannot read property 'style' of null
at HTMLElement.applyStyle (fold-entity-row.js:1)
fold-entity-row.js:1 Uncaught (in promise) TypeError: Cannot read property 'style' of null
at HTMLElement.applyStyle (fold-entity-row.js:1)
fold-entity-row.js:1 Uncaught (in promise) TypeError: Cannot read property 'style' of null
at HTMLElement.applyStyle (fold-entity-row.js:1)
fold-entity-row.js:1 Uncaught (in promise) TypeError: Cannot read property 'style' of null
at HTMLElement.applyStyle (fold-entity-row.js:1)
fold-entity-row.js:1 Uncaught (in promise) TypeError: Cannot read property 'style' of null
at HTMLElement.applyStyle (fold-entity-row.js:1)
fold-entity-row.js:1 Uncaught (in promise) TypeError: Cannot read property 'style' of null
at HTMLElement.applyStyle (fold-entity-row.js:1)
fold-entity-row.js:1 Uncaught (in promise) TypeError: Cannot read property 'style' of null
at HTMLElement.applyStyle (fold-entity-row.js:1)
fold-entity-row.js:1 Uncaught (in promise) TypeError: Cannot read property 'style' of null
at HTMLElement.applyStyle (fold-entity-row.js:1)
fold-entity-row.js:1 Uncaught (in promise) TypeError: Cannot read property 'style' of null
at HTMLElement.applyStyle (fold-entity-row.js:1)
fold-entity-row.js:1 Uncaught (in promise) TypeError: Cannot read property 'style' of null
at HTMLElement.applyStyle (fold-entity-row.js:1)
fold-entity-row.js:1 Uncaught (in promise) TypeError: Cannot read property 'style' of null
at HTMLElement.applyStyle (fold-entity-row.js:1)
fold-entity-row.js:1 Uncaught (in promise) TypeError: Cannot read property 'style' of null
at HTMLElement.applyStyle (fold-entity-row.js:1)
fold-entity-row.js:1 Uncaught (in promise) TypeError: Cannot read property 'style' of null
at HTMLElement.applyStyle (fold-entity-row.js:1)
fold-entity-row.js:1 Uncaught (in promise) TypeError: Cannot read property 'style' of null
at HTMLElement.applyStyle (fold-entity-row.js:1)
`
Attributes of binary_sensor.meteoalarm:

Seams odd, could you provide your sensor configuration from configuration yaml ?

Yes, sure:

Just wanted to change my language but it was not working, deleted the language part in my sensor configuration and now have the same problem. Was working fine before i changed the language and restarted HA...

I noticed another detail of this bug. A few days ago, the meteoalarm started working normally again all by itself. I couldn't really figure out why at that time. Later I got the answer when a new weather alarm was issued: The error immediately turned up again. It seems that the card works fine when the binary_sensor.meteoalarm is in the off state. As soon as it enters on state, the card displays the error message discussed in this thread.

Hi, I have the same error here, started only a few days ago :
meteoalarm-card.js?hacstag=361205663190:339 === METEOALARM CARD ERROR ===
Report issue: https://bit.ly/3hK1hL4

 Error: This integration doesn't support provided entity!
    at HTMLElement.getAttributes (:8123/hacsfiles/MeteoalarmCard/meteoalarm-card.js?hacstag=361205663190:289)
    at HTMLElement.render (:8123/hacsfiles/MeteoalarmCard/meteoalarm-card.js?hacstag=361205663190:325)
    at HTMLElement.update (:8123/hacsfiles/MeteoalarmCard/meteoalarm-card.js?hacstag=361205663190:159)
    at HTMLElement.performUpdate (:8123/hacsfiles/MeteoalarmCard/meteoalarm-card.js?hacstag=361205663190:134)
    at HTMLElement._enqueueUpdate (:8123/hacsfiles/MeteoalarmCard/meteoalarm-card.js?hacstag=361205663190:134)
render @ meteoalarm-card.js?hacstag=361205663190:339

binary_sensor data :
language: fr-BE
category: Met
event: Avertissement verte orage
responseType: None
urgency: Expected
severity: Moderate
certainty: Likely
effective: '2021-05-11T18:00:00+02:00'
onset: '2021-05-11T18:00:00+02:00'
expires: '2021-08-01T21:00:00+02:00'
senderName: Institut Royal Météorologique de Belgique
headline: Avertissement verte orage en Belgique - Brabant
description: Aucune attention particulière nécessaire
web: https://www.meteo.be/fr/meteo/avertissements/carte-de-belgique
awareness_level: 1; Green; Minor
awareness_type: 3; Thunderstorm
attribution: Information provided by MeteoAlarm
friendly_name: meteoalarm
device_class: safety

Note that for the same HA dashboard I have this error on Edge and Chrome, but not in the Android mobile app.
Hope this helps and thanks for the great integration !

Same error for me too for the last few days.
Thanks for the UI!!

@DarkWarden85 sorry for the delayed response! It seems like in very rare scenarios Awareness level and Awareness type are not present, i will investigate it a bit more and include fix for these scenarios in next relese

Just wanted to change my language but it was not working, deleted the language part in my sensor configuration and now have the same problem. Was working fine before i changed the language and restarted HA...
Btw, my binary_sensor.meteoalarm is working fine so that's not the issue.

If you think that this issue is different that this one, please create an issue

I noticed another detail of this bug. A few days ago, the meteoalarm card started working normally again all by itself. I couldn't really figure out why at that time. Later I got the answer when a new weather alarm was issued: The error immediately turned up again. It seems that the card works fine when the binary_sensor.meteoalarm is in state 'off'. As soon as it enters 'on' state, the card displays the error message discussed in this thread.

This is expected since this error is alert parsing issue so your card will function normally when there are no warnings
@kalhimeo I just set up my integration for France and it works without any problem, please try to update your HA and reinstall card, if the issue persist create an issue

Hi MrBartusek,
Thanks for the update. I did not update to HA 2021.08 yet so I will do that in the following days and try again, but for info I am not using the integration for France but for Belgium in french language.
Best regards, Laurent

@kalhimeo Okay then, I didn't notice that! I will wait for any Belgium alerts to come up and I will check that.

thank you !

@MrBartusek, parts of the UK have a warning today.
binary_sensor:
  - platform: meteoalarm
    country: 'united-kingdom'
    province: 'South West England'

Entity binary_sensor.meteoalarm:
language: en-GB
category: Met
event: Yellow thunderstorm warning
responseType: Prepare
urgency: Future
severity: Moderate
certainty: Possible
effective: '2021-08-09T09:36:11+00:00'
onset: '2021-08-09T11:00:00+00:00'
expires: '2021-08-09T20:00:00+00:00'
senderName: UK Met Office
headline: >-
  While many places will stay dry, heavy showers and thunderstorms may cause
  flooding and travel disruption in a few places.
description: >-
  Heavy, slow-moving, thundery downpours will develop today. Some places will
  miss these, but where they do occur, 10-20 mm rain may fall in a short space
  of time, perhaps with 20-40mm over 2 or 3 hours in a few places. The showers
  will die out during the evening. For further details see
  https://www.metoffice.gov.uk/weather/warnings-and-advice/uk-warnings
instruction: >-
  What to expect: There is a small chance that homes and businesses could be
  flooded quickly, with damage to some buildings from floodwater, lightning
  strikes, hail or strong winds; Spray and sudden flooding could lead to
  difficult driving conditions and some road closures; There is a small chance
  that some communities become cut off by flooded roads; Where flooding or
  lightning strikes occur, there is a chance of delays and some cancellations to
  train and bus services; There is a slight chance that power cuts could occur
  and other services to some homes and businesses could be lost.
web: https://www.metoffice.gov.uk/weather/warnings-and-advice/uk-warnings
attribution: Information provided by MeteoAlarm
friendly_name: meteoalarm
device_class: safety

@DeviantUK yes, it seems that UK don't send Awareness level and Awareness type  too, it will be fixed in next release


feature: parse 'schedule' job log for dependency cycles

could look for the most recent 'schedule' job, parse its log, and build a UI to build the optional_deps string.

I could also write it out in the status.json: https://github.com/msys2/msys2-autobuild/releases/tag/status

The basic list of cycles is now included in https://github.com/msys2/msys2-autobuild/releases/tag/status

https://github.com/msys2-arm/msys2-autobuild-controller/blob/main/job_log_parse.py could probably be removed in that case (I don't think it is called anywhere yet), and instead add code to load the status json.  That would also be useful for #9


Write an installer for macos

The macOS installer currently fails using the GitHub Action with
Could not solve for environment specs
Encountered problems while solving:
  - nothing provides requested pycuda 2022.2**

The environment can't be solved, aborting the operation

@pantaray, does that also happen locally?

Hi! Nope, but I only tested it on my Intel MBP from 2015. I'll test-drive the entire thing on one of our M1 Mac Minis today. I also noticed, that the installer crashes, if one attempts to launch it within an activated conda installation. This can be circumvented, of course but should we include some sort of interactive road block, that asks if the user really wants to install neuo-conda alongside an existing conda installation? What do you think?

Yup, okay, perfect! In the spirit of our planned env variables (ncEditor etc.) I could includencNoninteractive. If set, no user input is queried and the installer just does its thing. Would that work for you?

Yup, okay, perfect! In the spirit of our planned env variables (ncEditor etc.) I could includencNoninteractive. If set, no user input is queried and the installer just does its thing. Would that work for you?

Good idea! Thanks for testing the macs.

Took a bit of trial-and-erroring but I think this works now. I think we might want to merge now and include more tests (e.g., uninstalling) later. Is that okay with you?


windows install error

OS: win10
Rust: 1.38 stable amd64
cargo install flamegraph, I get error like this:
Compiling inferno v0.4.1
Compiling cargo_metadata v0.7.4
Compiling flamegraph v0.1.13
error[E0425]: cannot find value exit_status in this scope
--> d:\Program\cargo\registry\src\mirrors.ustc.edu.cn-61ef6e0cd06fb9b8\flamegraph-0.1.13\src\lib.rs:134:6
|
134 |     !exit_status.success()
|      ^^^^^^^^^^^ not found in this scope
error: aborting due to previous error
For more information about this error, try rustc --explain E0425.
error: Could not compile flamegraph.
warning: build failed, waiting for other jobs to finish...
error: failed to compile flamegraph v0.1.13, intermediate artifacts can be found at C:\Temp\cargo-installwtC1Id
Caused by:
build failed

I am also facing this issue on Windows 10.
Toolchain: stable-x86_64-pc-windows-msvc
Rustc: rustc 1.39.0 (4560ea788 2019-11-04)
error[E0425]: cannot find value `exit_status` in this scope
--> C:\.cargo\registry\src\github.com-1ecc6299db9ec823\flamegraph-0.1.13\src\lib.rs:134:6
    |
134 |    !exit_status.success()
    |     ^^^^^^^^^^^ not found in this scope

error: aborting due to previous error

For more information about this error, try `rustc --explain E0425`.
error: failed to compile `flamegraph v0.1.13`

I guess something went wrong when refactoring here

base v0.1.13, Just make the following changes and it will compile:
position: flamegraph-0.1.13\src\lib.rs:134:6
!exit_status.success() -> !status.success()

@zydxhs I additionally had trouble building because of signal_hook, do you not run into this when building?

@ConnorSkees Don not use the master version, there are many compilation errors.

This is now fixed on master.


Fix FreeJoint velocity and position integration for articulated bodies

#10 attempted to fix an integration issue when the COM offset from the link origin. However, this seems to work only for single body systems. With an articulated body, the fix in #10 actually caused errors that lead to fictitious forced being applied. This in essence reverts #10 while keeping the necessary changes for updateConstrainedTerms and adding more tests.
However, reverting #10 means small errors will be introduced when the COM is offset from the link origin. In a similar vain, if two bodies are connected by a fixed joint and a torque is applied, the whole system will rotate about the lumped COM. However, due to the way the velocities and positions are integrated in FreeJoint, this will also incur errors. I had to reduce the force and torque values in order to make tests pass. I think we should revisit this and see if it would be possible to eliminate these errors by applying the integration at the lumped COM.
/cc @Yadunund

Just to clarify, do we believe that JS's comment here is correct, that the root problem is some kind of numerical error accumulation due to calculating the forward dynamics in the local body frame? If so, I imagine we should focus future efforts on revising that convention in the forward dynamics. It would be tedious work that would touch on all the different joint types in DART, but it should be very doable, and shouldn't require any special case handling. As far as I'm aware, the choice to use the local body frame for the forward dynamics is recommended by Featherstone because it reduces the number of matrix transform operations that need to be performed, making it more efficient than using the global frame. But it seems like the benefit of that efficiency is dwarfed by the errors that accumulate, assuming that is the root cause of this problem.
The measures in this PR seem like a reasonable way to deal with this problem for now, and the additional tests are definitely great to have, so I'm happy to give this an approval.
Regarding the failing tests, do we want to increase the tolerance to allow the tests to pass, or just leave the tests failing as a reminder to revisit this problem?

Thanks for the review @mxgrey! I do think the root problem comes from using body frames in the forward dynamics algorithm and how we integrate such quantities. Section 8.3 of Jakub Stępień's dissertation talks about the problem we're seeing here and attributes the issue to the use of body frames. But changing the system to use global frames is a daunting task. Using global frames may also have numerical issues when a body is far from the fixed frame's origin resulting in large values in the "linear" portion of the spatial velocity.


[docs] Demo site broken on IE 11

Problem description
Array.find isn't polyfilled in the demo site, so it doesn't load in IE 11.
Steps to reproduce
Open v1 demo site in IE 11.
Images & references

Notes
Not 100% sure on this, but I'm fairly confident it used to load on IE 11 in the past.

Yes, it used to work. Oops, I must have broken it with the latest documentation update.

I have been fixing some issues. The last one might be next.js related.

I have been noticing issues with the following line:
const ansiRegex = __webpack_require__(420);

module.exports = input => typeof input === 'string' ? input.replace(ansiRegex(), '') : input;

This is related to https://github.com/zeit/next.js/issues/2747. They have merged a fix. it I should soon be fixed for the dev env. For the production env, it's working fine now. We can close :).


remove fastertransformer build and release in DJLServing

Description
Removing FasterTransformer

[x] Container build removal
[x] Integration test removal
[x] ECR sync test removal
[x] DJLServing code logic removal
[ ] AOT Partition removal
[ ] LMIC test removal
[ ] SageMaker integration test removal
[ ] Documentation removal

@sindhuvahinis @tosterberg please guide how to remove LMIC and partition, anything need to aware to remove?


Return value for net_listening is wrong.

net_listening returns true instead of the hexadecimal representation of the value.
The expected return value according to Ethereum Wiki would be:
curl -X POST --data '{"jsonrpc":"2.0","method":"net_listening","params":[],"id":67}' localhost:8545
{"id":67,"jsonrpc":"2.0","result":true}

Expected Behavior
0x0000000000000000000000000000000000000000000000000000000000000001
Current Behavior
true
Context
Can't implement consistent return value across clients in my PHP implementation.

The expected behavior is now true from the JSON RPC. Closing due to now being compliant!


Sure Electronics 24x16 Support

Modified the Library to Support the 24x16 mode of the Driver Chip

Thank you!


Getting rate limited when trying to collect PR data for issue-metrics

I'm trying to implement the github/issue-metrics@v2 action, my main desire is to collect data on time-to-first-comment/review on Pull Requests in my repository, which this tool seems to support.
However I am getting an API rate exceeded error, when trying to use it across a window of only a couple of days content:
github3.exceptions.ForbiddenError: 403 API rate limit exceeded for installation ID 8026696. If you reach out to GitHub Support for help, please include the request ID FC00:1733:4E64548:A17BDA6:65A1A825.
The full yml is very simple for now, and looks like this:
name: PR Metrics Test
on: push

permissions:
  pull-requests: read

jobs:
  build:
    name: pr metrics
    runs-on: ubuntu-latest
    steps:
    - name: Run issue-metrics tool
      uses: github/issue-metrics@v2
      env:
        GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        SEARCH_QUERY: 'repo:<OrgHere>/<RepoHere> is:pr created:2023-05-01..2023-05-02'

... you can see I just selected a single day, but still get rate limited (it appears, at least).
I don't know what queries the tool is running under the hood though. Is this expected? The repository is not typically hugely busy, I would expect only a handful of PRs per day max.
Thanks for any guidance!

Once you've been rate limited once, it lasts for a while so that's what I expect is happening here. Have you tried running this since? Still an issue?

Moving to a feature request issue #217


Brainstorm Around Q4 Security Engineering Champion Milestones

Let's get some ideas around the work to support the Q4 milestones, what we want to accomplish and most importantly, what done looks like.
Q4 Milestones / Milestone 3

Security Implementation: Report on OpenSSF Best Practices Badge program for JavaScript published
Security Ongoing / Self-sustaining post contract:

Content documented: customized best practices recommended by OpenSSF
Best practices JavaScript checklist completed
Templates documented
Compliance tools created
SBOM Generation / Tooling Best Practices updated and documented

For Reference.. All Milestones
Milestone 1

Infra Discovery: Project, stakeholders, and requirements gathering completed
Infra Planning: Project and program scoping completed
Security Planning: Security engineer, Audit Vendor, and Training Vendor hired
Security Planning: Inventory and analysis audit completed to establish project
Tiers. Top 10 Tier 1 projects to start identified.
Security Implementation: Provided direct support to maintainers on the menu of
OpenSSF Best Practices Badge program
Security Implementation: Provided direct support for secure releases and CVE
management

Milestone 2

Infra Planning: SOW and communication strategy created
Security Implementation: Broad JavaScript ecosystem education and outreach
on OpenSSF Best Practices Badge program completed
Security Ongoing:
o Content development update: customized best practices recommended
by OpenSSF
o SBOM Generation / Tooling Best Practices created.
o Compliance Report / Audits / Dashboard created and populated by Tier 2
projects

Milestone 3

Infra Design: CI/CD and productivity tools standardization exercise completed
Infra Design: Proof of concept where needed implemented
Security Implementation: Report on OpenSSF Best Practices Badge program for
JavaScript published
Security Ongoing / Self-sustaining post contract:
o Content documented: customized best practices recommended by
OpenSSF
o Best practices JavaScript checklist completed
o Templates documented
o Compliance tools created
o SBOM Generation / Tooling Best Practices updated and documented

Milestone 4

Infra Design: Proof of concept user acceptance validation completed
Infra Implementation: Onboarded projects into tooling where needed
Security Implementation: Secondary Tier projects started. Educate and onboard
through consensus with projects’ technical steering committees or individual
maintainers
Security Implementation: OpenJS and audit vendor publish an Impact Report,
summarizing all results of security audits. Example:
https://openssf.org/blog/2023/02/01/independent-security-audit-impact-report/
Security Implementation: JavaScript training launched
Security Implementation: Compliance Report / Audits / Dashboard created and
populated by Tier 2 projects
Security Ongoing:
o Direct support to maintainers on the menu of OpenSSF Best Practices
Badge program
o Direct support for secure releases and CVE management
o Content development: customized best practices recommended by
OpenSSF
o SBOM Generation / Tooling Best Practices created

Milestone 5

Infra Implementation: Targeted project transition of productivity and CI/CD
complete (Target projects to be identified via SOW) (Phase 1)
Security Implementation: Badges implemented on Tier 2 Projects
Security Ongoing:
o Direct support for secure releases and CVE management.
o Content development: customized best practices recommended by
OpenSSF
o SBOM Generation / Tooling Best Practices created.
o Compliance Report / Audits / Dashboard created and populated by Tier 2
projects.

Milestone 6

Infra Implementation: Targeted project transition of productivity and CI/CD
complete (Target projects to be identified via SOW) (Phase 2)
Security Implementation: Broad JavaScript ecosystem education and outreach
on OpenSSF Best Practices Badge program
Security Ongoing:
o Content development update: customized best practices recommended
by OpenSSF
o SBOM Generation / Tooling Best Practices created.
o Compliance Report / Audits / Dashboard created and populated by Tier 2
projects

Milestone 7

Infra Implementation: Targeted project transition of productivity and CI/CD
complete (Target projects to be identified via SOW) (Phase 3)
Infra Finalization of transition work
Project sunsetting completed
Infra: Internal and external support documentation created
Infra Formalization of budget forecasting
Security Implementation: Public report on OpenSSF Best Practices Badge
program for JavaScript
Security Ongoing / Self-sustaining post contract:
o Content documented: customized best practices recommended by
OpenSSF
o Best practices JavaScript checklist created
o Templates documented
o Compliance tools created
o SBOM Generation / Tooling Best Practices updated and documented

Notes From Discussion with Robin, Jordan, and Ben on Oct 9, 2023
Security Implementation: Report on OpenSSF Best Practices Badge program for JavaScript published

Implement badges on Tier-1 projects, have all 7 projects be passing

Gaps in silver are explained

Report:

Status of the projects, for those that have gaps, explanation of them and next steps
Breakdown of what work was done by the project and what work was done by Jordan
Recommendations and analysis of gaps (e.g. single contributor project)
Analysis of the project state (are things better than we thought they were)

Audience For Report

Internal - OpenJS projects, STF
External - Developers using OpenJS projects

Security Ongoing / Self-sustaining post contract:
Content documented: customized best practices recommended by OpenSSF

Analysis: are there other best practices beyond Badges, Secure Releases, SBOMS and what should we adapt and adopt (list of what we looked at, and decisions on each)

Engage with OpenSSF best practices working group

Best practices JavaScript checklist completed

Dashboard will be where the checklist lives
Done for this one means, it's populated with all our agreed-upon best practices and approved by the Collab Space
Checklist will be a living document

Templates documented

Nothing obvious for this item at this time. Likely will create future concise guides based on the checklist.

Compliance tools created

Gov compliance - too early to do this officially
OpenJS compliance - what do we want to bake into the project lifecycle
Tools vs Shaping policy

Prob can not move forward with tools since compliance standards have not been published yet
Working directly with Fiona and Tara
1 pager inventory on things in motion and areas that we should be involved in/prioritized

SBOM Generation / Tooling Best Practices updated and documented

Publishing of our SBOM primer/recommendation
Additional tasks will be dependent on what the final recommendation is.

Brainstorm complete. Next steps are @ljharb integrating this into his planning for Q4.


Inventory not being stored when switching back to world the first time

I have 2 worlds, a creative and survival one. A player spends hours grinding for diamonds in survival but never accesses the creative mode. One day, they choose to enter. When they return to the survival mode, they are surprised to see that everything they've had in their inventory is completely gone. They start grinding again. Now they go back to creative their creative inventory is there, and when they return to survival their new inventory is still there, explain why? It works after the first time, but I need it to work at once!

the inventory switches to default on WORLD CHANGE, not WORLD SPAWN. And since you spawn in the survival world but not in the creative, the default inventory will be the "DEFAULT"


UnboundLocalError: local variable 'data_onehot' referenced before assignment

Hello!
I followed the installation tutorial on the README.md.
I tried both

installing using 'pip install annopro'
install from source code.

The commands I used are:

python -m annopro -i data.fasta -o output --used_gpu 0,1,2,3
python -m annopro -i data.fasta -o output
python run.py

After these attempts, I got the same error as indicated in the Logs.
Do you know how to fix this?
Thanks in advance!
Input
The data.fasta is like:
>sp|O14793|GDF8_HUMAN Growth/differentiation factor 8 OS=Homo sapiens OX=9606 GN=MSTN PE=1 SV=1
MQKLQLCVYIYLFMLIVAGPVDLNENSEQKENVEKEGLCNACTWRQNTKSSRIEAIKIQI
LSKLRLETAPNISKDVIRQLLPKAPPLRELIDQYDVQRDDSSDGSLEDDDYHATTETIIT
MPTESDFLMQVDGKPKCCFFKFSSKIQYNKVVKAQLWIYLRPVETPTTVFVQILRLIKPM
KDGTRYTGIRSLKLDMNPGTGIWQSIDVKTVLQNWLKQPESNLGIEIKALDENGHDLAVT
FPGPGEDGLNPFLEVKVTDTPKRSRRDFGLDCDEHSTESRCCRYPLTVDFEAFGWDWIIA
PKRYKANYCSGECEFVFLQKYPHTHLVHQANPRGSAGPCCTPTKMSPINMLYFNGKEQII
YGKIPAMVVDRCGCS

The run.py is:
from annopro import main
main("data.fasta", "output", "0,1,2,3")

or
from annopro import main
main("data.fasta", "output")

Runtime Environment

Operation System: RedHat 8.6
Python: Python 3.8
Tensorflow: 2.6.5
Cuda: 11.6.1
CuDNN: <IP_ADDRESS>

Logs
Running "module reset". Resetting modules to system default. The following $MODULEPATH directories have been removed: None
A conda environment has been detected CONDA_PREFIX=
CONDA_PATH/envs/annopro
anaconda3_gpu is loaded. Consider running conda deactivate and reloading it.
diamond v<IP_ADDRESS> (C) Max Planck Society for the Advancement of Science
Documentation, support and updates available at http://www.diamondsearch.org/
Please cite: http://dx.doi.org/10.1038/s41592-021-01101-x Nature Methods (2021)
#CPU threads: 4
Scoring parameters: (Matrix=BLOSUM62 Lambda=0.267 K=0.041 Penalties=11/1)
Temporary directory: output
#Target sequences to report alignments for: 25
Opening the database...  [0.044s]
Database: USER_DIR/.annopro/data/cafa4.dmnd (type: Diamond database, sequences: 87514, letters: 44798577)
Block size =<PHONE_NUMBER>
Opening the input file...  [0.001s]
Opening the output file...  [0s]
Loading query sequences...  [0s]
Masking queries...  [0s]
Algorithm: Double-indexed
Building query histograms...  [0s]
Loading reference sequences...  [0.042s]
Masking reference...  [0.583s]
Initializing temporary storage...  [0.007s]
Building reference histograms...  [0.402s]
Allocating buffers...  [0s]
Processing query block 1, reference block 1/1, shape 1/2, index chunk 1/4.
Building reference seed array...  [0.159s]
Building query seed array...  [0s]
Computing hash join...  [0.003s]
Masking low complexity seeds...  [0s]
Searching alignments...  [0.001s]
Deallocating memory...  [0s]
Processing query block 1, reference block 1/1, shape 1/2, index chunk 2/4.
Building reference seed array...  [0.186s]
Building query seed array...  [0s]
Computing hash join...  [0.003s]
Masking low complexity seeds...  [0s]
Searching alignments...  [0s]
Deallocating memory...  [0s]
Processing query block 1, reference block 1/1, shape 1/2, index chunk 3/4.
Building reference seed array...  [0.202s]
Building query seed array...  [0s]
Computing hash join...  [0.003s]
Masking low complexity seeds...  [0s]
Searching alignments...  [0s]
Deallocating memory...  [0s]
Processing query block 1, reference block 1/1, shape 1/2, index chunk 4/4.
Building reference seed array...  [0.16s]
Building query seed array...  [0s]
Computing hash join...  [0.003s]
Masking low complexity seeds...  [0s]
Searching alignments...  [0s]
Deallocating memory...  [0s]
Processing query block 1, reference block 1/1, shape 2/2, index chunk 1/4.
Building reference seed array...  [0.151s]
Building query seed array...  [0s]
Computing hash join...  [0.003s]
Masking low complexity seeds...  [0s]
Searching alignments...  [0s]
Deallocating memory...  [0s]
Processing query block 1, reference block 1/1, shape 2/2, index chunk 2/4.
Building reference seed array...  [0.186s]
Building query seed array...  [0s]
Computing hash join...  [0.003s]
Masking low complexity seeds...  [0s]
Searching alignments...  [0s]
Deallocating memory...  [0s]
Processing query block 1, reference block 1/1, shape 2/2, index chunk 3/4.
Building reference seed array...  [0.201s]
Building query seed array...  [0s]
Computing hash join...  [0.003s]
Masking low complexity seeds...  [0s]
Searching alignments...  [0s]
Deallocating memory...  [0s]
Processing query block 1, reference block 1/1, shape 2/2, index chunk 4/4.
Building reference seed array...  [0.155s]
Building query seed array...  [0s]
Computing hash join...  [0.004s]
Masking low complexity seeds...  [0s]
Searching alignments...  [0s]
Deallocating memory...  [0s]
Deallocating buffers...  [0s]
Clearing query masking...  [0s]
Computing alignments... Loading trace points...  [0.014s]
Sorting trace points...  [0s]
Computing alignments...  [0.004s]
Deallocating buffers...  [0s]
Loading trace points...  [0s]
[0.022s]
Deallocating reference...  [0s]
Loading reference sequences...  [0s]
Deallocating buffers...  [0s]
Deallocating queries...  [0s]
Loading query sequences...  [0s]
Closing the input file...  [0s]
Closing the output file...  [0.001s]
Closing the database...  [0s]
Cleaning up...  [0s]
Total time = 2.668s
Reported 5 pairwise alignments, 5 HSPs.
1 queries aligned.
2023-06-16 13:27:18.651280: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-06-16 13:27:27.991777: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1510] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 43511 MB memory:  -> device: 0, name: NVIDIA A40, pci bus id: 0000:07:00.0, compute capability: 8.6
2023-06-16 13:27:28.072954: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1510] Created device /job:localhost/replica:0/task:0/device:GPU:1 with 43511 MB memory:  -> device: 1, name: NVIDIA A40, pci bus id: 0000:46:00.0, compute capability: 8.6
2023-06-16 13:27:28.074780: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1510] Created device /job:localhost/replica:0/task:0/device:GPU:2 with 43511 MB memory:  -> device: 2, name: NVIDIA A40, pci bus id: 0000:85:00.0, compute capability: 8.6
2023-06-16 13:27:28.076816: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1510] Created device /job:localhost/replica:0/task:0/device:GPU:3 with 43511 MB memory:  -> device: 3, name: NVIDIA A40, pci bus id: 0000:c7:00.0, compute capability: 8.6
Traceback (most recent call last):
File "CONDA_PATH/envs/annopro/lib/python3.8/run.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "CONDA_PATH/envs/annopro/lib/python3.8/run.py", line 87, in _run_code
exec(code, run_globals)
File "PROJECT_PATH/AnnoPRO/annopro/main.py", line 4, in
console_main()
File "PROJECT_PATH/AnnoPRO/annopro/init.py", line 27, in console_main
main(
File "PROJECT_PATH/AnnoPRO/annopro/init.py", line 75, in main
predict(output_dir=output_dir,
File "PROJECT_PATH/AnnoPRO/annopro/prediction.py", line 19, in predict
init_evaluate(term_type=term_type,
File "PROJECT_PATH/AnnoPRO/annopro/prediction.py", line 160, in init_evaluate
preds = model.predict(data_generator, steps=data_steps)
File "CONDA_PATH/envs/annopro/lib/python3.8/site-packages/keras/engine/training.py", line 1720, in predict
data_handler = data_adapter.get_data_handler(
File "CONDA_PATH/envs/annopro/lib/python3.8/site-packages/keras/engine/data_adapter.py", line 1383, in get_data_handler
return DataHandler(*args, **kwargs)
File "CONDA_PATH/envs/annopro/lib/python3.8/site-packages/keras/engine/data_adapter.py", line 1138, in init
self._adapter = adapter_cls(
File "CONDA_PATH/envs/annopro/lib/python3.8/site-packages/keras/engine/data_adapter.py", line 917, in init
super(KerasSequenceAdapter, self).init(
File "CONDA_PATH/envs/annopro/lib/python3.8/site-packages/keras/engine/data_adapter.py", line 794, in init
peek, x = self._peek_and_restore(x)
File "CONDA_PATH/envs/annopro/lib/python3.8/site-packages/keras/engine/data_adapter.py", line 928, in _peek_and_restore
return x[0], x
File "PROJECT_PATH/AnnoPRO/annopro/prediction.py", line 50, in getitem
return ([data_onehot, data_si])
UnboundLocalError: local variable 'data_onehot' referenced before assignment

We use profeatpy to calculate it protein sequence features and it was developed with Fortran. But its input is not a standard FASTA format so it require sequence info rows only contain id without any space, for example
>sp|O14793|GDF8_HUMAN
MQKLQLCVYIYLFMLIVAGPVDLNENSEQKENVEKEGLCNACTWRQNTKSSRIEAIKIQI
LSKLRLETAPNISKDVIRQLLPKAPPLRELIDQYDVQRDDSSDGSLEDDDYHATTETIIT
MPTESDFLMQVDGKPKCCFFKFSSKIQYNKVVKAQLWIYLRPVETPTTVFVQILRLIKPM
KDGTRYTGIRSLKLDMNPGTGIWQSIDVKTVLQNWLKQPESNLGIEIKALDENGHDLAVT
FPGPGEDGLNPFLEVKVTDTPKRSRRDFGLDCDEHSTESRCCRYPLTVDFEAFGWDWIIA
PKRYKANYCSGECEFVFLQKYPHTHLVHQANPRGSAGPCCTPTKMSPINMLYFNGKEQII
YGKIPAMVVDRCGCS

Problem solved! Thanks!


feat(storage): Series File Compaction

This pull request adds an offline command to compact series files:
$ influxd inspect compact-series-file \
    [--sfile-path SERIES_FILE_PATH] \
    [--tsi-path INDEX_PATH] \
    [--concurrency N]

This is a forward port of https://github.com/influxdata/influxdb/pull/16542 except that the command has been separated out (instead of being embedded in buildtsi).
Closes https://github.com/influxdata/influxdb/issues/16890

Looks good so far!

go vet issue
# github.com/influxdata/influxdb/tsdb_test
vet: tsdb/series_file_test.go:365:50: cannot use ([][]byte literal) (value of type [][]byte) as *tsdb.SeriesCollection value in argument to sfile.CreateSeriesListIfNotExists
github.com/influxdata/influxdb/write
github.com/influxdata/influxdb/tsdb/tsm1_test
make: *** [Makefile:159: vet] Error 2

alchemy please merge


Armv7: sha1h.32 instruction fails to disassemble

objdump:
72f10:       f3b962c0        sha1h.32        q3, q0
Capstone also fails to disassemble it:
cstool -d arm C062B9F3
ERROR: invalid assembly code
cstool -d arm F3B962C0
ERROR: invalid assembly code

After digging a bit further, I think none of the sha* instructions are implemented atm.


Option to configure editor scrollbar to be opaque

Currently, if editor.renderLineHighlight is set to "line" or "all", the highlight extends into the scrollbar. It would be helpful if it stopped just left of the scrollbar. Here is my rationale:

The line position isn't the same as the scrollbar position, except by coincidence. They are independent, however the highlighting suggests a linkage of some kind.
With certain color schemes it can be confusing at a quick glance to determine where on the scrollbar I actually am.

Example of intrusion of line highlight into the scrollbar:

Notice how similar the two highlighted areas look on the scrollbar? On closer inspection I can tell that I am actually at the lower point on the scrollbar, because of the brown horizontal line.
As a workaround, I could easily change the color of the highlight to prevent confusion. But, I'm having trouble understanding why the highlight extends into the scrollbar in the first place.
Thanks for your consideration!
VS Code 1.22.1

The reason is that the scrollbar is transparent. Even characters are visible through the scrollbar.

Having a transparent scrollbar is nuts.  Who thinks editor text that is visible in the scrollbar is a good thing?
There is no option that I can find to get the editor to work like, well, ALL other editors...

I'm not a frequent VSCode user-- Today I thought there was no horizontal scrollbar as it looks exactly like highlighted search text.  I'd vote for a system native scrollbar.

Today I was wondering where my horizontal scrollbar was, turns out it's there, but almost invisible

This is now partially implemented by using a new colour contribution, editorOverviewRuler.background. Using this, you can set the background colour of the scrollbar, but the colour is only used when the minimap is visible and placed on the right side of the editor. For all other situations, the scrollbar is still transparent.

Le scrollbar trasparenti sono una minchiata. Perche' non vi dedicate a qualcosa di piu' utile?

I would like to have a scrollbar like this too!

The reason is that the scrollbar is transparent. Even characters are visible through the scrollbar.

Why the characters are needed to be placed under the scrollbar? this is the problem.

I don't see how one could advocate a transparent scroller as good UX design. It makes the editor significantly less efficient. At minimum please add a setting for scroller transparency.

A work around (care of @jakequinter), add this to your settings.json and set it to the color you want, and the scrollbars will be that color and no longer transparent.
    "workbench.colorCustomizations": {
       "scrollbarSlider.background": "#333333",
       "scrollbarSlider.hoverBackground": "#333333",
       "scrollbarSlider.activeBackground": "#333333",
    }

@bploetz's workaround only makes the scrollbar slider opaque.
A workaround to make the scrollbar itself opaque while not having a visible minimap:
"editor.minimap.maxColumn": 1,
"editor.minimap.enabled": true,

Make sure to enable the minimap for this to work.
Hopefully the underlying bug will be fixed eventually and this workaround won't be necessary.

"workbench.colorCustomizations": {
"scrollbarSlider.background": "#333333",
"scrollbarSlider.hoverBackground": "#333333",
"scrollbarSlider.activeBackground": "#333333",
}

This seems to work, but only when the frame has focus. For example, my code area's scrollbars disappear if my cursor is in any sidebar or the terminal.

@ps2goat try these settings:

"editor.minimap.maxColumn": 0,
"editor.minimap.enabled": true,

I already have the minimap open, but I tried this anyway and it didn't work. The scrollbars still disappear if the focus changes to a different area.

scrollbar slider disappearing when losing focus is a different issue. This issue is about the scrollbar itself being transparent. I would suggest opening a new issue for that.


Make hivemind accessible to non-gui users

I've installed Hivemind (alongside Node-red) on my KDE testing rig.
The skill shows up on the WebUI with all configuration options accessible (as Version1).
My non-gui Mycroft version (where hivemind was installed yesterday) sadly throws an exception on loadup.
I think that the environment is also beneficial to non-gui users, where mycroft is served from a central server or users just don't want the gui overhead.
The UPnP Client / soap protocol now is looking for a libxslt handled object file which isn't found in a non-gui setup. (i guess) Maybe there are more things down the drain, but this is what throws mycroft (non-gui) off.
Traceback (most recent call last):
  File "/home/pi/mycroft-core/mycroft/skills/skill_loader.py", line 252, in _load_skill_source
    skill_module = load_skill_module(main_file_path, self.skill_id)
  File "/home/pi/mycroft-core/mycroft/skills/skill_loader.py", line 72, in load_skill_module
    spec.loader.exec_module(mod)
  File "<frozen importlib._bootstrap_external>", line 728, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/opt/mycroft/skills/skill-node-red.jarbasskills/__init__.py", line 4, in <module>
    from jarbas_hive_mind_red import get_listener
  File "/home/pi/mycroft-core/.venv/lib/python3.7/site-packages/jarbas_hive_mind_red/__init__.py", line 1, in <module>
    from jarbas_hive_mind.master import HiveMind, HiveMindProtocol
  File "/home/pi/mycroft-core/.venv/lib/python3.7/site-packages/jarbas_hive_mind/__init__.py", line 4, in <module>
    from jarbas_hive_mind.master import HiveMind, HiveMindProtocol
  File "/home/pi/mycroft-core/.venv/lib/python3.7/site-packages/jarbas_hive_mind/master/__init__.py", line 12, in <module>
    from jarbas_hive_mind.discovery.ssdp import SSDPServer
  File "/home/pi/mycroft-core/.venv/lib/python3.7/site-packages/jarbas_hive_mind/discovery/__init__.py", line 1, in <module>
    import upnpclient
  File "/home/pi/mycroft-core/.venv/lib/python3.7/site-packages/upnpclient/__init__.py", line 143, in <module>
    from upnpclient import const, errors, marshal, soap, ssdp, upnp, util  # noqa: F401
  File "/home/pi/mycroft-core/.venv/lib/python3.7/site-packages/upnpclient/soap.py", line 4, in <module>
    from lxml import etree
ImportError: libxslt.so.1: cannot open shared object file: No such file or directory

hivemind does not require (or use at all) the gui, that sounds like a missin OS level dependency

OK, that seems to be resolved after a system wide libxslt1.1 install.
Now it throws an error on mycroft_skill.py but this should be because of a push from mycroft-core earlier today

will add that to Readme


Write module documentation and minimal example

The module neural_trajectory.py needs a module documentation describing what the functions are doing and including a minimal example to help the user to understand how to use the method.

Module documentation and minimal examples are now provided in a new format.


Microsoft App not working

Description
RefreshMailboxCommand is failing.
How to reproduce
Wait 1 day after setting up a Microsoft App.
Possible Solution
Fixing the refresh access token method.
Additional context
Webkul\UVDesk\CoreFrameworkBundle\Services\MicrosoftIntegration::refreshAccessToken(): Argument #1 ($app) must be of type Webkul\UVDesk\CoreFrameworkBundle\Entity\MicrosoftApp, null given,

pmdevelopment/mailbox-component#1


Versioned dependency and dependency circles

AUR packages which depend on one specific version of another package won't update in case the pkgver of both packages is increased.
This is somewhat hard to describe but let's take letsencrypt [1] as an example: It requeries python2-acme [2] to be installed on the system in the version as the package itself. When updating pacaur tries to update each of them individually, which obviosly results in an error (error: failed to prepare transaction (could not satisfy dependencies)), since they both need to be updated at the same time.
Pacman handles this properly and recognizes those special cases, hence I suggest to install all pacakges which pacaur has prepared at the same time and not as soon as just one is ready.
[1] https://aur.archlinux.org/packages/letsencrypt/
[2] https://aur.archlinux.org/packages/python2-acme/

I'll see what I can do. The installation process of built packages needs to be reworked anyway (see #364).

Indeed, this might get tricky, though it should be fixable since the information about which dependency is cyclic (needs to be installed in parrallel or prior by ignoring the conflict) and which not (can be installed as usual).

Care to expand? I'm not sure how I could retrieve that information without adding a lot of complexity to the code, but I might be missing something here.

I just came up with two rather crappy solutions:

just do it how it is done now and evaluate the error message and accordingly wait for those mentioned packages to finish building
use the dependcy information from the pacman database to see which packages depend on one specific version of another and evaluate which package can and which can't be installed the usual way
However I admit that both solutions would add some degree of complexity to the code.

The first solution is clearly a no go. If the dependency solver fails, then the whole operation should stop.
The second one looks better on theory, but is actually hard to implement correctly in practice. Dependencies are solved on a "per-dependency level" basis with the deepest dependencies on the tree installed first. This issue would actually need to completely change the installation process in a awkward, prone to error way that would result in a mess imho, especially when the solver has to take multiple packages installation or upgrade at the same time.
The real question is actually why do you need to depend on this specific dependency version in the first place. I understand  letsencrypt requires the latest python2-acme to work, but Arch is a continuously updated distribution, with only the latest version of packages available and with unsupported partial update. If both packages are updated at the same time in the AUR by their maintainers (which seems to be you in both cases), then the solver will do the rest.
In other words, it seems to me that you're the one that creates this issue with a versioned dependency which doesn't make sense on Arch. If this reasoning is flawed in some way, please add your input. I might have completely missed something here.

No response, closing as 'INVALID'.

Sorry for the long delay.
Your conclusion is correct: I am the maintainer and yes I am causing this bug. I have fixed the versioned dependencies for now, though I think this should not be a longterm solution. I also admit that Arch does not support partial upgrade.
However I don't think that this means one should not follow upstream dependencies. Taking the nvidia package [1] as an example, it depends on nvidia-utils [2] but it must be present in the same version. Pacman handles this accordingly, so pacaur should do it for AUR packages a well.
A proper approach would be to check whether the dep is already installed in the requiered version (using pacman's -T option) or whether it will be installed soon after, if so either delay the installation or install it with pacman's --nodeps option.
[1] https://www.archlinux.org/packages/extra/x86_64/nvidia/
[2] https://www.archlinux.org/packages/extra/x86_64/nvidia-utils/

True, pacman handles this situation correctly and ideally pacaur would handle it too. I however won't work on a theoretical issue. Do you have any existing AUR packages in mind where this user case really happens?
Using --nodeps might be a possibility, but again solving this issue is tricky as deps are solved by "level" in the dependency chain, and not by packages. In this regards, this issue is kind of similar to #173.

I though letsencrypt was a good enaught example. I just guess many AUR package maintainers are getting used to not using versioned deps. Admittetly this is not a serious problem and is fixable by only a small incorrectness in the PKGBUILD.

Again, letsencrypt was an issue that should not exist in the context of a rolling distribution such as Arch. Versioned dependencies make rarely sense in AUR (although sometimes they do make sense), and pacaur is built around the idea that everything that should be fixed in the PKGBUILDs should be, well, fixed in the PKGBUILDs.
I am aware of only one AUR packages that needs a versioned dependency which causes a cyclic dependency situation (although I can't remember that package name right now..), but it is a slighly different beast. It needs a package to be built to bootstrap its dependency, before the main package can be built and the first package being removed - a user case so specific that only manual intervention can fix.

I would argue that versioned deps make as much sense in the AUR as they do in the official repo.
However you are probably right that for this narrow use case the added complexity would not be worth it.

If there is an existing real user case where this issue does happen, then I'm interested in trying to fix it.
But as far as I can see, we don't have a real user case scenario here which isn't something that should be fixed in the PKGBUILD - and thus this issue does not exist as far as I'm concerned. If you ever came across such an user case, please comment on this ticket - I'll have a look.


Use custom authorisation scheme

We experienced some bug using LinkedIn OAuth and the "Authorization" header. Turns out this bug disappear if we use the parameter "oauth2_access_token" instead. This brings us to think about this correction.
I want to be able to use my own authorisation method using custom params. See LinkedIn Demo for example.

I can accept to merge a PR with 6 commits with only one (see contributing guide)
Use git to make only one commit, use rebase instead of pull when possible, etc...
On way is to create a branch from previous commit named feature-xxxx, rebase our master branch into this new branch, then apply a patch to this branch and commit....
Then I am not sure this is the solution for your problem
Adding "oauth2_access_token" for each request is weird
Maybe .CustomParameters(["oauth2_access_token": token]) will be better
(I think of other solution, allow to customise the string used internally if possible)

Just saw the commit mess, willl create an other PR, thanks.
In our case we use the function only once so that make sens to me but I see the struggle, will think about something else. Thank you!


feature: We should add a test for Job cleaning,

Feature Description
We should add a test for Job cleaning, similar to service cleaning.
Proposed Solution
Add a new e2e test.
Want to contribute?

[ ] I would like to work on this issue.

Additional Context
No response

The "properly starts a job with metadata.generateName" test has been added to test/e2e/ginkgo/multiple_cluster_deployment_test.go.


Verify 1ES hoted pool provisioning profile works with 1ES PT

We currently use a provisioning script for our windows pools to enable Microbuild signing. Verify that a pool and image that works with the 1ES PTs works for the signing scenario with our existing provisioning script, or write down which changes would need to be made to enable the scenario.
Part of https://github.com/dotnet/dnceng/issues/1956

Release Note Category

[ ] Feature changes/additions
[ ] Bug fixes
[ ] Internal Infrastructure Improvements

Release Note Description

Validated this works when investigating moving an official build to the pipeline templates. The provisioning profile we use for Signing works.


If "initialStale" is setted or return true, 'isFetching' will be true and 'data'  will be undefined when the key is changed

Describe the bug
The initialStale behavior is strange. When initialStale is false and query key is changed, isFetching will always be true, and data will always be undefined
To Reproduce
Steps to reproduce the behavior:

codesandbox: https://codesandbox.io/s/rq-initialstale-xg9u2?file=/src/index.js:444-456
Click 'add' button

Expected behavior
Not sure what it should be.
I think initialStale should not be called multiple times, and data should be an object.
Screenshots

Desktop (please complete the following information):

OS: Mac
Browser: Chrome
Version: 84.0.4147.125

Additional context
Add any other context about the problem here.

Hmm, this indeed looks like a bug. Could be happening around here: https://github.com/tannerlinsley/react-query/blob/caa6522a72b3338b610b5e8c207b3b0d332c0784/src/core/queryObserver.ts#L204

@boschni any ideas here? I'm still a bit disconnected from this code lol


Update of RTD documents in preparation for the upcoming 0.5.2 release

@andrewwhitehead -- please review and (hopefully) merge before the 0.5.2 release.

Codecov Report

Merging #565 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #565   +/-   ##
=======================================
  Coverage   96.74%   96.74%
=======================================
  Files         240      240
  Lines       12737    12737
=======================================
  Hits        12323    12323
  Misses        414      414


website: Golang.org blocks DigitalOcean Frankfurt IPv6 ranges

What version of Go are you using (go version)?
1.5

What operating system and processor architecture are you using?
Ubuntu 14.04 server on DigitalOcean's Frankfurt instance.

What did you do?
Try to download Go binary

What did you expect to see?
A successful http request.

What did you see instead?
403 Forbidden

<?xml version='1.0' encoding='UTF-8'?>
<Error>
AccessDenied
<Message>Access denied.</Message>
We're sorry, but this service is not available in your location
</Error>

If I disable IPv6 or set IPv4 preferred, I am able to download the binary succesfully.
More info,
https://gist.github.com/jrasanen/a3276494d58bc93a88de
https://gist.github.com/jrasanen/abfdf1c864897baa8717

What does ip.appspot.com say from there over ipv6? Email me privately if you prefer.

It says the following,
root@frankfurt-test1:~# curl -i ip.appspot.com
HTTP/1.1 403 Forbidden
Date: Thu, 17 Sep 2015 14:55:48 GMT
Content-Type: text/html
Server: Google Frontend
Content-Length: 2053

<!DOCTYPE html>

<meta charset=utf-8><meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width">
<title>Error 403 (Forbidden)!!1</title>

403.

That’s an error.
Your client does not have permission to get URL / from this server.  (Client IP address: 2a03:b0c0:3:d0::84:5001)

We're sorry, but this service is not available in your country.

  That’s all we know.

Okay, so it's 2a03:b0c0:3:d0::84:5001

Yes, also:
2a03:b0c0:3:d0::76:2001
2a03:b0c0:3:d0::81:4001

I'm able to reproduce this as well, also from an IP in the 2a03:b0c0::/32 range.

I've contacted two internal Google teams about this.

This should now be fixed.


In firefox iceconnection disconnects automatically while streaming video

Please read first!
Please use discuss-webrtc for general technical discussions and questions.

[ ] I have provided steps to reproduce (e.g. a link to a jsfiddle)
[x] I have provided browser name, version and adapter.js version
[ ] This issue only happens when adapter.js is used

Note: If the checkboxes above are not checked, the issue will be closed.
Versions affected
Firefox 52.0.2
**https://webrtc.github.io/adapter/adapter-latest.js **
Description
I am using RTCPeerConnection, navigator.mediaDevices.getUserMedia, RTCIceCandidate, xmpp, DTMF, iceservers
Steps to reproduce
While streaming video in the Firefox Browser, iceconnection gets disconnected automatically and the video freezes and it gets connected again and soon disconnects and freezes, but this does not happen in Chrome Browser.
Expected results
Video Streaming should happen continuously without freezing in firefox
Actual results
Video gets freezed in Firefox

So the issue does not happen when NOT using adapter.js? Not sure what adapter has to do with this, sounds more like a network issue.
Also, make sure to fulfill all the conditions in the checkboxes, they are there for a reason, an issue without enough information is not actionable and a waste of time.


Harvester dups seeds from Mystical Agraddations

Mystical Agradditions is an addon for Mystical Aggriculture. Among other things, it adds seeds for nether stars and awakened draconium. These are special in that they require a specific block under the soil in order to grow.
When the Harvester attempts to harvest one of these plants, when the plant doesn't have the support block in place, the harvester breaks the plant, retrieves the seed, but the plant is left in place. This allows the seed to be duplicated. This happens repeatedly and as fast as the harvester harvests.
https://github.com/BlakeBr0/MysticalAgradditions/issues/7

So weird that it gets blocked from breaking it.

Testing this out now. so weird.  So when i use any non-tier 6 seed, so from the base mod such as Fire seed, everything works as normal.
When using a Tier 6 seed, in this screenshot its Nether star seed, the harvester seems to think that the plant is fully grown, even when in reality its not.  Then it breaks and replants which makes seeds, one seed every time.  It should be trying to remove one seed from the drop of the items.    Saw it on dirt, so the block below doesnt seem to matter

Code where i get the seed
https://github.com/PrinceOfAmber/Cyclic/blob/04b525a5ba3a52c86a2f4750f717730e178ecae5/src/main/java/com/lothrazar/cyclicmagic/util/UtilHarvestCrops.java#L108
remove one seed
https://github.com/PrinceOfAmber/Cyclic/blob/04b525a5ba3a52c86a2f4750f717730e178ecae5/src/main/java/com/lothrazar/cyclicmagic/util/UtilHarvestCrops.java#L263
Check if fully grown: if it cannot grow any more, its done growing, at least thats the assumption the code makes
https://github.com/PrinceOfAmber/Cyclic/blob/04b525a5ba3a52c86a2f4750f717730e178ecae5/src/main/java/com/lothrazar/cyclicmagic/util/UtilHarvestCrops.java#L222
There are some rough spots in that giant function for sure.   but i dont know why the raw mod and the addons behave so differently.

Ill see if i can check their source code on the addon to see what weirdness is being used

It seems like it has something to do with not meeting the special block requirement. That addon mod has another seed (Inferium Seeds, Tier 6) that doesn't require a special block and works as expected with the harvester. The base mod doesn't have any seeds with that kind of dependency.

I'm thinking it would be best for Mystical Agradditions to change their code such that their special block detection is done in updateTick rather than canGrow. I'm not sure what the server impact of doing that way is.

Mystical Agradditions recently applied patches for this. So it should be fixed once that mod makes the rounds.
[1.10] Fix tier 6 crops checking for the crux badly (Also contains fixes for 1.12)
[1.11] Fix the tier 6 crop thingies and organize imports


Add support for multi disk LUNS : Production & Cost concious setup

Is your feature request related to a problem? Please describe.
Certified Azure production HANA currently requires 4x disks based LVM for Data and 3x disks based Log volumes ( with Write accelerator enabled ).
In addition, A cost conscious setup ( Non certified ) setup is typically provisioned in non-production (dev,qa,sbx) environment.
Current jinja template (https://github.com/Azure/sap-automation/blob/main/deploy/ansible/roles-os/1.5-disk-setup/templates/volume_groups.j2:16) can only process by creating LVMs comprising of single disks.
This has a technical limitation as the stripe size set during LVM creation based on number of participating disks and cannot be changed later without a complete rebuild. It also limits performance to 1x the disk irrespective of how many disks you add into the LVM in future.
Describe the solution you'd like
Modify the template https://github.com/Azure/sap-automation/blob/main/deploy/ansible/roles-os/1.5-disk-setup/templates/volume_groups.j2:16 code block to below code
{%     for disk in disks if (disk.host == inventory_hostname) and (disk.type == disktype) %}
{%        for lun in disk.LUN%}
{%         set _ = pvlist.append('/dev/disk/azure/scsi1/lun' ~ lun) %}
{%        endfor %}
{%     endfor %}
This will require TF code be  to modified in  how it outputs the sap-automation.yaml file from the templates.
A sample disks block will be as below
disks:
- { host: 'hana-01', luns: [0], type: 'usrsap'}
- { host: 'hana-01', luns: [1], type: 'hanashared'}
- { host: 'hana-01', luns: [11,12,13,14], type: 'hanadata'}
- { host: 'hana-01', luns: [21,22,23], type: 'hanalog'}
- { host: 'hana-01', luns: [31], type: 'hanabackup'}
Note the comma separated array / list of iSCSI LUN numbers.
For Cost Conscious HANA setup, we could go for 4x disks combined in a single Volume group, which carves out 3 LVM , one each for Shared, Data and Log. An identifier for this in  vars/disk_config.yaml file can be added to allow
Additional context
Recommendations/requests here are based on official documentation
https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/hana-vm-operations-storage

@shekharsorot  - I have checked with the team and they haven't seen this as an issue, we create a PV containing all the disks of a specific type. Additionally, the code for creating disks relies on various files including the var/disk_config.yaml.
On the cost conscious configuration - the custom disk sizes yaml can be specified with the configuration required

This issue is very old and i see that code has been updated to accommodate custom disk layout.


draggable content within a node.

Hi! Thanks for this amazing library.
I'm building a list with draggable items inside a node. The dragging works, but I get this strange behavior (shown below) where the internal item being dragged and the pointer aren't aligned. Seems that there is some issue where the board is interfering with the cursor position when dragging something inside a node.
The problem persists with className = {'nodrag'} and gets worse the further the node is from the top left of the viewport.

Hey @nicojochnick
It's good that you are already using the nodrag class but I need to see your code to understand the issue here. Maybe it's on your side maybe react-flow is doing strange things.. can you share a sandbox or a repo with me?

Closed due to inactivity. Feel free to re-open if the issue still occurs.


Track custom events being $dispatch-ed

This is again inspired by Vue.js Devtool's "events" tab, obviously Alpine.js doesn't use synthetic events or emit events to communicate between components.
Instead we should register a top-level listener for events being dispatched with $dispatch (which we can detect) eg. we can read @click="$dispatch('my-custom-event') which means we should listen to 'my-custom-event' at the top-level (using document.addEventListener) and then report their contents in a tab.
Any thoughts/ideas limitations you can think of @ryangjchandler @Te7a-Houdini ?
We probably want a new panel for this.
Update 1
With Alpine latest we can overwrite $dispatch and instrument it (see https://github.com/amaelftah/alpinejs-devtools/issues/48#issuecomment-732133163):

It turns out that it's possible to overwrite a magic property 👀 , so we can inject some code that will replace $dispatch and send debug info on call 👍
https://codepen.io/hugodf/pen/xxOvqpg

Note on this: we should check that the suggested $dispatch function override works the same as regular Alpine one, one thing that might be different is which element dispatchEvent is being called on
Update 2
Overwriting $dispatch doesn't behave the same as Alpine implementation see https://codepen.io/hugodf/pen/GRjKgNO?editors=1111 the overriden $event.target is not correct (it's the root of the component, not the element from which $dispatch is called).
A way to get this to work is to monkey-patch dispatchEvent with something like this:
const _dispatchEvent = EventTarget.prototype.dispatchEvent;
EventTarget.prototype.dispatchEvent = function(...args) {
  // send a message to devtools
  // `this` is the element from which `$dispatch` is called
  // `args[0]` is the event name, `args[1]` is the options (including `options.detail`)
  console.log(this, args);

  return _dispatchEvent.apply(this, args);
}

This has the advantage of not being Alpine.js specific (eg. if custom events are sent from vanilla JS) + not locking us into a minimum Alpine version.

Here's the relevant code in Alpine, if we can hook into CustomEvent or el.dispatchEvent that could work
https://github.com/alpinejs/alpine/blob/3c3e8b801a7b00a982dd54290cf656f051e915d9/src/component.js#L369

When you say hook in, do you mean monkey-patching the prototype?

When you say hook in, do you mean monkey-patching the prototype?

Pretty much hahaha

When you say hook in, do you mean monkey-patching the prototype?

Pretty much hahaha

Yeah, I think that could work.

I think we should do the page -> devtools communication refactor first.

It turns out that it's possible to overwrite a magic property 👀 , so we can do inject some code that will replace $dispatch and send debug info on call 👍
https://codepen.io/hugodf/pen/xxOvqpg
Other interesting note is that $dispatch basically doesn't need to be in core any more 😂

@HugoDF Legendary, hadn't even thought about that.

It turns out that it's possible to overwrite a magic property 👀

Oh nice! We can implement both $refs and $dispatch both now :D

It turns out that it's possible to overwrite a magic property 👀

Oh nice! We can implement both $refs and $dispatch both now :D

well see this update

Overwriting $dispatch doesn't behave the same as Alpine implementation see https://codepen.io/hugodf/pen/GRjKgNO?editors=1111 the overriden $event.target is not correct (it's the root of the component, not the element from which $dispatch is called).


Global ts base

global timestamp will show deviation due to global timestamp base adjustment every 500ms. Issues found:

milli-second precision too low.  Skip update if half usb delay > 250us
Base change may happen between two mono images receiving.  Adjust 2nd mono image timestamp to match 1st mono image timestamp.

Request to development branch


Text on multi connection link is reversed when layout is set to Left

Hi @bumbeishvili, Thanks for the wonderful library. I feel we have a bug on the below mentioned scenario, can you please let me know if it's bug or am I doing something wrong.
Describe the bug
Text on multi connection link is reversed when layout is set to left and when compact is set to false.
I've forked an example to reproduce the scenario, Please check - link
To Reproduce
Steps to reproduce the behaviour:

Click on Fit to screen
Click on Multi Node Connections
Click on Left Layout
See text on links, text is not proper.

Expected behavior
Text should be proper on links.
Screenshots

Thanks!

Hi, it relies on an svg marker functionality to draw arrows and  texts
If there is a bug, it can be fixed by overriding current defs generation function
chart.defs(function (state, visibleConnections) {
                return `<defs>
                    ${visibleConnections.map(conn => {
                    const labelWidth = this.getTextWidth(conn.label, { ctx: state.ctx, fontSize: 2, defaultFont: state.defaultFont });
                    return `
                       <marker id="${conn.from + "_" + conn.to}" refX="${conn._source.x < conn._target.x ? -7 : 7}" refY="5" markerWidth="500"  markerHeight="500"  orient="${conn._source.x < conn._target.x ? "auto" : "auto-start-reverse"}" >
                       <rect rx=0.5 width=${conn.label ? labelWidth + 3 : 0} height=3 y=1  fill="#E27396"></rect>
                       <text font-size="2px" x=1 fill="white" y=3>${conn.label || ''}</text>
                       </marker>

                       <marker id="arrow-${conn.from + "_" + conn.to}"  markerWidth="500"  markerHeight="500"  refY="2"  refX="1" orient="${conn._source.x < conn._target.x ? "auto" : "auto-start-reverse"}" >
                       <path transform="translate(0)" d='M0,0 V4 L2,2 Z' fill='#E27396' />
                       </marker>
                    `}).join("")}
                    </defs>
                    `})

Thanks for the input @bumbeishvili , i'll try this solution and update here.

I'll have to modify the orientation for the text in the defs, thanks @bumbeishvili it's working now.


node-sass not found

Steps to reproduce the behavior
when I first run yo keystone followed by node keystone this is what I see:
Please install the node-sass-middleware from npm to use the sass option.
You can do this by running "npm install node-sass-middleware --save".

I believe this issue can be closed.    From latest, node-sass-middleware is in the package.json file and gets installed with npm install

@TaylorAckley is right, this is included in the latest version of the generator.


Shouldn't let me create a project with all garbage characters

Weights and Biases version: 0.4.45
Python version: 3.6.1
Operating System: mac

Description
If I make a project with name say '//////' I automatically and quietly get back a project with name fragrant-variance or something like that.

@shawnlewis says this is working as intended.  When someone get's real mad about this take it up with him.


@deprecated createModelViewDialog - ambiguous hint

Azure Data Studio Version:

Version: 1.29.0 (system setup)
Commit: 0f5cfdc2c8c2433028842e16dc5ac1a65da24292
Date: 2021-05-15T01:12:11.112Z
VS Code: 1.53.0
Electron: 11.2.2
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19043
Steps to Reproduce:

Create a new dialog extension
Open the main.ts

The deprecated message is ambiguous: createModelViewDialog is deprecated use createModelViewDialog
        /**
         * @deprecated please use the method createModelViewDialog(title: string, dialogName?: string, width?: DialogWidth) instead.
         * Create a dialog with the given title
         * @param title The title of the dialog, displayed at the top
         * @param isWide Indicates whether the dialog is wide or normal
         */
        export function createModelViewDialog(title: string, dialogName?: string, isWide?: boolean): Dialog;

Question
createModelViewDialog is deprecated or not?

That version of the function is (with the isWide parameter) - you should use the version that takes a width?: DialogWidth parameter. It provides all the same functionality and more.

No createModelViewDialog(title: string, dialogName?: string, width?: DialogWidth) with the width parameter inside the d.ts

A solid point - forgot that one is still in proposed : https://github.com/microsoft/azuredatastudio/blob/main/src/sql/azdata.proposed.d.ts#L648
We're not going to remove the old function anytime soon so feel free to continue using it until we get the new one into the stable API.
@alanrenmsft - Note to us that we probably shouldn't be deprecating stuff in the main API until we have a replacement there - it's pretty confusing if people aren't familiar with the proposed API and given our usual time frame for actually removing stuff waiting a bit longer for it to make it into stable isn't a huge deal.


container config: add OSArguments

Store the full command plus arguments of the process the container has
been created with.  Expose this data as a Config.OSArguments field in
the container-inspect data as well.
This information can be useful for debugging, as we can find out which
command has created the container, and, if being created via the Podman
CLI, we know exactly with which flags the container has been created
with.
The immediate motivation for this change is to use this information for
podman-generate-systemd to generate systemd-service files that allow
for creating new containers (in contrast to only starting existing
ones).
Signed-off-by: Valentin Rothberg<EMAIL_ADDRESS>

@rhatdan PTAL. I didn't yet integrate it into podman-generate-systemd, which I want to reflect on a bit longer. I figured to break this change out as it can generally be useful, especially when debugging we can ask users to provide this data.

LGTM, would like a @mheon head nod

I feel like we already expose this. I remember I had to generate it for the
new version of Inspect.
On Thu, Dec 12, 2019, 08:19 Tom Sweeney<EMAIL_ADDRESS>wrote:

LGTM, would like a @mheon https://github.com/mheon head nod
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/containers/libpod/pull/4684?email_source=notifications&email_token=AB3AOCASP5JCWD3NI2XOL7LQYI26ZA5CNFSM4JZ45QO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGWUK4I#issuecomment-565003633,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3AOCBNTL72KEH36Y5U5ATQYI26ZANCNFSM4JZ45QOQ
.

Hm. This is definitely different than what I was initially thinking, so we don't include it. Hm.

Updated, @mheon PTAL

@mheon Do you like this PR?

Yeah, LGTM
On Thu, Dec 19, 2019, 08:50 Daniel J Walsh<EMAIL_ADDRESS>wrote:

@mheon https://github.com/mheon Do you like this PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/containers/libpod/pull/4684?email_source=notifications&email_token=AB3AOCHWRDDWMFBDQ5UMQVLQZN33DA5CNFSM4JZ45QO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHJVGRA#issuecomment-567497540,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3AOCCCE2NSOTXXNR76FW3QZN33DANCNFSM4JZ45QOQ
.

/lgtm


Feature/borismod 1 unit tests

NuGet package restore was added
Downgrade NUnit package to 2.6.4
Build destination of all the projects was changed to shared location Binaries
Ignore 3 failing tests

connect #1

It seems that this pull request is no longer valid. The changes have already been made to develop and the issues I identified have already been resolved. It should probably be removed.
I did do a review on reviewable.io just to practice using that tool. Not sure if you got my review comments or not. It seemed to have some kind of issue publishing, but it still shows the comments I made in the code.

Ok, you are right, this is an outdated PR. I will close it.


unable to download the dll file Interop.ADOMD.dll required for the extention.

Need help to download Interop.ADOMD.dll
tried installing MS feature pack ADOMD.NET ,But could not find the dll.
Please help.
Thanks,
Abin

Hi @abinjacob
Legally, we cannot provide DLL files since they don't come with support. They are a "find-and-use-at-your-own-risk" component which we cannot help with.
Thanks!


fix model_tokens not being used for ollama

I am passing in the explicit model_tokens from user config as the default_token so it will correctly fallback to the users setting if the model is not found

related to #377


[BUG] Auto confirm appointments do not work when appointment page is not visited

Describe the bug
If all appointments are auto confirmed and added and required the appointment page is skipped. In scenario the appointment is correctly added without the registrant knowing, but auto confirm is not working by setting the appointment to confirm. This is because the appointment is actually added on the registration page rather than the appointment page. The logic is missing in the first registration page to set confirmed on auto confirmed appointments.

Included in beta release <IP_ADDRESS>

Included in production release <IP_ADDRESS>


Create validation for deleting stories

Use validation that exists in StoryController and also add validations against banned users deleting stories.

38995d13d39001cac8c3d3972ae3b1851e4fd702


Property User.email incorrect

diff --git a/edstem/user.py b/edstem/user.py
index 3d7f3d6..ebb492f 100644
--- a/edstem/user.py
+++ b/edstem/user.py
@@ -62,7 +62,7 @@ class User(base.EdObject[base.UserID]):
 @property
 def email(self) -> str:

   return self._data["name"]

   return self._data["email"]

Thanks for catching this! This repo is still under development (and I've had a break from it for a while), but I'll fix this right now.
I'll mention that we have a more stable version of a Python wrapper for the API here and are working on this one to provide some better abstractions on the API.

Thanks!  I'll take a look at the 'toolshed', but this has already been very
helpful.
On Fri, Jan 12, 2024, 16:39 Hunter Schafer @.***> wrote:

Closed #11 https://github.com/hschafer/edstem/issues/11 as completed
via d306e82
https://github.com/hschafer/edstem/commit/d306e829019e38d6f15241fd410dbeb050e29946
.
—
Reply to this email directly, view it on GitHub
https://github.com/hschafer/edstem/issues/11#event-11475399477, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAET2DAND5JPQPKEACRWKITYOHJVHAVCNFSM6AAAAABBTYQITSVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGQ3TKMZZHE2DONY
.
You are receiving this because you authored the thread.Message ID:
@.***>


Refine the logical and physical plan serialization and deserialization

Which issue does this PR close?

Closes #4597.
Rationale for this change

What changes are included in this PR?

After https://github.com/apache/arrow-datafusion/pull/4390, there're still parts which needs to follow up for the physical plan.
Remove Ballista related things in the datafusion.proto
Add missing fields for FileScanExecConf, like output_ordering and config_options. Otherwise, it will block some Ballista UT.
Make the code well organized for serialization and deserialization like physical plan does
Are these changes tested?

Are there any user-facing changes?

Hi @alamb and @andygrove, could you help review this PR? After this PR merged, we can go further to upgrade the Datafusion dependency in Ballista, like https://github.com/yahoNanJing/arrow-ballista/commit/279d9afc3644a91218eb4ec2a1a42934decad7f2 does.

Since it's a big refactor for the proto mod, I propose to merge this PR as soon as possible. Otherwise, there will be many conflicts when new commits merged to the master branch.

Thanks again @yahoNanJing


Add a min_gas_price verification step in the health check process

Summary

Add a min_gas_price verification step in the health check process.
Problem Definition

We often ask users to provide us with the min_gas_price value as part of their app.toml when debugging issues. Now that the SDK exposes this value over gRPC in v0.45.10, we can automatically check for this value as part of Hermes' health check process so that there wouldn't be a need to ask the user for this value directly.
Proposal

Add a min_gas_price verification step in the health check process that checks that the gas_price parameter in the Hermes config.toml file is set to be greater than or equal to the min_gas_price advertised by the chain.
Acceptance Criteria

[ ] Added a min_gas_price verification step to the health check

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

We probably need to update the protos for that to be able to issue the query and then just gracefully deal with the failure in case the chain does not support it

@romac Could you expand a bit on what you meant by this?


feat: export markdown-it instance without code highlight

Please check if the PR fulfills these requirements

[x] It's the right issue type on the title
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added/updated (for bug fixes/features)
[x] It does not introduce a breaking change or has a description of the breaking change

Description
The editor exports ToastUIEditor.markdownitHighlight so others can extend the markdown rendering behaviour. However the secondary markdown-it instance which is used in convertor.js: _markdownToHtml(markdown)  is not exported. It was therefore impossible to extend the markdownToHtml behaviour.
This PR uses the same approach as used for ToastUIEditor.markdownitHighlight to export ToastUIEditor.markdownit as well.

I think it's a good feature. I will merge after checking.


Building against CUDA SDK

Hi,
Was this code tested against the CUDA SDK, and if so, which version?
I note that the C++ Includes setup includes the Intel OpenCL SDK, the CUDA SDK and the AMD APP SDK. The applications builds and runs fine against the Intel SDK but doesn't appear to build against the CUDA SDK. The first error you will run into is that cl2.hpp does not exist in the CUDA SDK.
Can you explain how/if this code was built to run on an NVIDIA GPU?
Thanks,
Adam

Bear with me since the code was mostly made in 2017. So, I cannot remember all the details.
CLUtils library uses bindings from cl2.hpp, but not any OpenCL 2.0 features. So, it should work on nvidia GPUs. Could you try adding the cl2.hpp to your CL include folder and see if it then builds?
I have run some version of the code on 4 different nvidia machines (For example CUDA SDK version 9.2.148) and cannot remember having any major hassle. However, a lot of OpenCL development have been done on all of those machines. So, it is plausible that cl2.hpp does not ship with the driver and it has been copied to include folder by hand.

@AdamJMiles please if you get it working on CUDA, tell me how. I tried to build in VS 2017 and bump against Error MSB4019 The imported project "C:\BuildCustomizations\IntelOpenCL.props" was not found.

@trsh  I meet the same problem. Did you solve it?

@yiifanLu no. :/


HTML2Canvas Output image rotated or distorted.

Hello,
I've got an issue where the outputted image is sometimes rotated or is distorted. I'm using it as part of a Canvas tool for users to create their Canvas in the browser.
The issue seems to happen when the image is a selfie image from a phone. I can't get it to cause the issue on any other photo.
Is this a known issue?
Below is an example of what the issue produces.

It appears to be Apple that is causing the problem, the images are rotated.

Please share an example on jsfiddle

same issue...
HTML2Canvas displays iOS photos taken in portrait as landscape.
Try this fiddle on your phone:
https://jsfiddle.net/0f0evru0/

same issue...


Solana Workbench gets replaced by ERB default app after running it once

Auto-update is still pointed to ERB by default in package.json...
but we can't point it to our repo yet, we get the following error in this case:
Error: Error: Cannot find latest-linux.yml in the latest release artifacts (https://github.com/workbenchapp/solana-workbench/releases/download/v0.3.0/latest-linux.yml): HttpError: 404

closed by #294


Check whether gather_metrics_memory can be simplified

By using else instead of if for all the newer distro's.

Used another method, but also fixed in https://github.com/nozel-org/serverbot/commit/e2e9869e49e496f9fab4d318067d947cbab31df8