Livefyre comments still broken

@tdykstra Livefyre made some changes such that profiles load correctly now :+1:; however, I'm still not getting messages from the forum on the Publish to IIS doc.
You can see in the screenshot that I'm "following" the comments. My E-mail address in their system is correct, which is an outlook.com address. I didn't get the last one that was posted eight days ago.

Feature request: Comments should be editable. I had to completely delete one just to make a change to it.

@GuardRex Is this still a problem, and if so do you have a recent example?

Yes ... I just checked and there are new messages that I didn't receive while configured to "Follow" the chat ...

I confirmed my E-mail address was correct when I filed this issue, but I just attempted to access my profile, and I received the spinning-forever-no-loading-profile (as we went through before) ...

So ... I sign out and try to sign in again with my MS account and it fails. I request a password reset and no message has arrived (ten minutes later anyway) to reset the password.
You guys sure this whole Deadfyre :trollface: thing was a good idea? :grin:

I can't get signed back into the system now. The reset feature is not sending a reset or temporary password to my Outlook mail account.

Livefyre Support is handling the issue.

This isn't going to get resolved easily or quickly, so I'll reopen and post updates as it goes forward.

Livefyre uses Zendesk for mail services.
Livefyre Support claims that Zendesk's portal shows the messages are going out.
At least some Zendesk servers are blacklisted by SORBS.
MS and Proofpoint, the owners of SORBS, are doing security business.

Therefore, a possible cause for Livefyre messages not reaching Outlook is blocking on the Outlook side due to blacklisted servers. It's just a guess, but it would explain the behavior here.

Today's update ...

They have no idea why their password reset system doesn't work. They had me forward the password reset link E-mail and the followup "Your password has been changed" E-mail.
They didn't check if my outlook.com address is linked to the comments for Publishing to IIS, as I asked them to confirm.
They have no answer on the Zendesk mail servers being blacklisted by SORBS. They remarked that I can whitelist the mail servers myself by adding their Zendesk address to my outlook.com Safe Senders list. [I'll let you guess what I think about the efficacy of that suggestion. :grin:]
They didn't delete an account I setup inadvertently under "GuardRex_Corporation1" when trying to get their system to work, as I asked them to do.


Jobs not showing up at https://cloud.qibo.science

The jobs I send never show up on the dashboard https://cloud.qibo.science. Neither the queued jobs, nor the finished one are shown.
I presume the Your jobs status section should display them

So sorry, I was apparently using an old API key (not sure where it did come from actually...), using the one reported on the dashboard worked fine. We can close.

Thanks for checking!


istg.txt

https://istg.edu.ec/
est.txt

gh pr checkout 15532

https://github.com/JetBrains/swot.git

@ANDYPILAY First stage of verification passed, official domain is istg.edu.ec as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@ANDYPILAY Pull request merged. Thank you.


Async PGVector to make LangChain with Postgres more performant

Feature request
Currently we use PGVector as our Vector Database and do in combination with FastAPI. One issue is that in the indexing process, which happens over an API Endpoint, we found out that the current implementation of PgVector is blocking due to its synchronous implementation. FastAPI offers async/await and SQLAlchemy also allows using async sessions. I would like to add an Async Alternative for PGVector.
Motivation
Non-Blocking code execution prevents blocking the main thread of our execution and provides far superior performance compared to synchronous execution
Your contribution
I already coded a prototype, which works so far and does not block the main thread of the API. I would fully implement this async solution. Currently I only have to discuss this with my boss, since I did this during worktime.

@Coding-Crashkurse any updates on this?

@danny-avila : I froze implementing this, due to the addition of "run_in_executor" of the LangChain team. This solved the issue with the blocked main thread, but to be honest I will would like to make it async natively. But currently no time for that.

I see, thanks! Do you have any examples of using the Indexing API with PGVector asynchronously?

With a FastAPI, I need to expose a 'load()' method, to import data in the pgvector, with index() (and RecordManager, SQLDocStore, etc). I have a lot of documents, and it can take several tens of seconds.

I propose a PR for that

@Coding-Crashkurse Can you give an example on how you used run_in_executor? If i use the driver asyncpg i always get this error: There is no current event loop in thread 'asyncio_0'.

As you can see now, an asynchronous implementation has been added to langchain-postgres pgvector

Can you please point to this feature? I don't see it and all my attempts to use pgvector with either asyncpg or psycoppg2 in async mode fail.

Try with "psycopg" (with no number)

Thank you will do
———————
David Eisner
240.994.5900

From: RoQuasar @.>
Sent: Friday, September 20, 2024 6:00:57 AM
To: langchain-ai/langchain @.>
Cc: davidtheITguy @.>; Comment @.>
Subject: Re: [langchain-ai/langchain] Async PGVector to make LangChain with Postgres more performant (Issue #14836)
Try with "psycopg" (with no number)
—
Reply to this email directly, view it on GitHubhttps://github.com/langchain-ai/langchain/issues/14836#issuecomment-2363341518, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARYO7J5JRIEHZOSL5MURHLLZXPW5TAVCNFSM6AAAAABAZCQYEGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRTGM2DCNJRHA.
You are receiving this because you commented.Message ID: @.***>


Fix test folder names and comment ComponentGraph tests

Types of changes

[ ] Bugfix (change which fixes an issue)
[ ] New feature (change which adds functionality)
[X] Refactor (change which changes the codebase without affecting its external behavior)
[X] Non-breaking change (fix or feature that would causes existing functionality to work as expected)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Purpose

Standardize the "tests" name for test folders
Add comments for in-progress tests and remove some tests as well

Good job! looks fantastic


amending the UI layout on backup screen for missing button

Can this PR be merged into master? Not sure why it's been deleted


[ENH] python 3.7 and 3.8 testing

Codecov Report

Merging #107 into master will increase coverage by 0.2%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master     #107     +/-   ##
=========================================
+ Coverage    76.8%   77.01%   +0.2%
=========================================
  Files          11       11
  Lines         677      683      +6
  Branches       96       96
=========================================
+ Hits          520      526      +6
  Misses        126      126
  Partials       31       31

Impacted Files
Coverage Δ

celer/tests/test_lasso.py
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Spike: Heterogenous random distribution of arbitrary values within the same property

To generate arbitrary values based on a size hint and a random number generator the javaslang.test framework provides us with a function int -> Random -> T.
// return a generator given a size hint
Arbitrary<T> : int -> Gen<T>

// return a value given a random number generator
Gen<T> : Random -> T

To me, this seems to be too complicated. How often is a random generator changed in practice? Better would be to just give a size hint to generate values: int -> () -> T.
TODO: Check, if it is a viable alternative to change the random number generator at the level of generators (Gen) and not at the level of properties (Property).
Update: It should be sufficient to change Gen to () -> T and provide additional factory methods which take a Random, e.g. Gen.choose(Random, int, int) in addition to Gen.choose(int, int).
Then Arbitrary<T> would be (Random, int) -> Gen<T> which equals (Random, int) -> () -> T and we can decide whether to use the provided random number generator or a different one. This simplifies the creation of custom object generators!

Idea to test a custom random:
Use generator of {1, 2} with a custom random which always returns 1 and a property which succeeds for 1 and fails for 2.

Implemented the idea described above and reverted it. No good DX, too much additional methods.


[BUG] Scala UDF compiler can decompile UDFs with RAPIDS implementation

Now that Scala UDFs have support for a RAPIDS implementation since #1636, there's the possibility that the Scala UDF compiler could end up compiling a user's Scala UDF into Catalyst expressions despite the fact that it already provides a RAPIDS columnar implementation.  The UDF compiler should detect and avoid trying to translate UDFs that implement the RapidsUDF interface.

Remove from v21.06. Let's target in 21.08.

Fixed by #1712


[Question][v2] How to ignore validate from object ?

Dear @jagi , i has Class have some validation defined, but sometime i want disable on save like this:
User.save({
  validation: false // i want ignore validate in this time.
});

this can be ? have any ideas for this ?

You can do so but I would not recommend it
import { ValidationError } from 'meteor/jagi:astronomy';

try {
  user.save();
} catch(err) {
  // You can also check here if it was validation error and ignore it.
  if (!ValidationError.is(err)) {
    throw err;
  }
}

Sorry my bad it will catch validation error but still prevent saving. There is no way of performing save without validation using Astronomy. It's by purpose. You can only disable client validation:
user.save({
  simulation: false
});

If you want to save some data without validation, you have to use pure Meteor for that:
const modifier = user.getModifier();
Users.update(user._id, modifier);

However I would not recommend doing it if you're not 100% sure about security.

thanks @jagi so much, i got it !


Error reading char at handle 26, status=5

Hi, I'm having a weird problem, preventing me to use this at all. As far as I know, @sud33p has the same issue.
I wanted to set up an ESP32 with for my Idasen desk with this config:
esphome:
  name: idasen
  platform: ESP32
  board: esp32dev

# === DESK ===

external_components:
  - source<EMAIL_ADDRESS>

esp32_ble_tracker:
ble_client:
  - mac_address: "CA:B3:52:CE:1E:70" # Replace with the desk bluetooth mac address
    id: idasen_desk

idasen_desk_controller:
    # Reference to the ble client component id
    # -----------
    # Required
  ble_client_id: idasen_desk
    # Fallback to use only up and down commands (less precise)
    # -----------
    # Optional
  only_up_down_command: false

cover:
  - platform: idasen_desk_controller
    name: "Desk"

However, I keep getting the same error:
[16:36:03][D][esp32_ble_tracker:214]: Starting scan...
[16:36:03][D][esp32_ble_tracker:720]: Found device DE:9E:9A:10:97:6B RSSI=-86
[16:36:03][D][esp32_ble_tracker:741]:   Address Type: RANDOM
[16:36:03][D][ble_client:047]: Found device at MAC address [CA:B3:52:CE:1E:70]
[16:36:03][I][ble_client:085]: Attempting BLE connection to ca:b3:52:ce:1e:70
[16:36:04][W][idasen_desk_controller:049]: [Desk] Disconnected!
[16:36:04][W][ble_client:117]: connect to ca:b3:52:ce:1e:70 failed, status=133

This error is repeating over and over again, until I press the pairing button on my desk. Then this happens:
[16:36:04][D][esp32_ble_tracker:214]: Starting scan...
[16:36:04][D][ble_client:047]: Found device at MAC address [CA:B3:52:CE:1E:70]
[16:36:04][I][ble_client:085]: Attempting BLE connection to ca:b3:52:ce:1e:70
[16:36:04][I][idasen_desk_controller:042]: [Desk] Connected successfully!
[16:36:05][I][ble_client:161]: Service UUID: 0x1800
[16:36:05][I][ble_client:162]:   start_handle: 0x1  end_handle: 0x9
[16:36:05][I][ble_client:341]:  characteristic 0x2A00, handle 0x3, properties 0xa
[16:36:05][I][ble_client:341]:  characteristic 0x2A01, handle 0x5, properties 0x2
[16:36:05][I][ble_client:341]:  characteristic 0x2A04, handle 0x7, properties 0x2
[16:36:05][I][ble_client:341]:  characteristic 0x2AA6, handle 0x9, properties 0x2
[16:36:05][I][ble_client:161]: Service UUID: 0x1801
[16:36:06][I][ble_client:162]:   start_handle: 0xa  end_handle: 0xd
[16:36:06][I][ble_client:341]:  characteristic 0x2A05, handle 0xc, properties 0x20
[16:36:06][I][ble_client:161]: Service UUID: 99FA0001-338A-1024-8A49-009C0215F78A
[16:36:06][I][ble_client:162]:   start_handle: 0xe  end_handle: 0x13
[16:36:06][I][ble_client:341]:  characteristic 99FA0002-338A-1024-8A49-009C0215F78A, handle 0x10, properties 0xc
[16:36:06][I][ble_client:341]:  characteristic 99FA0003-338A-1024-8A49-009C0215F78A, handle 0x12, properties 0x12
[16:36:06][I][ble_client:161]: Service UUID: 99FA0010-338A-1024-8A49-009C0215F78A
[16:36:06][I][ble_client:162]:   start_handle: 0x14  end_handle: 0x17
[16:36:06][I][ble_client:161]: Service UUID: 99FA0020-338A-1024-8A49-009C0215F78A
[16:36:06][I][ble_client:162]:   start_handle: 0x18  end_handle: 0x1f
[16:36:06][I][ble_client:341]:  characteristic 99FA0021-338A-1024-8A49-009C0215F78A, handle 0x1a, properties 0x12
[16:36:06][I][ble_client:341]:  characteristic 99FA0029-338A-1024-8A49-009C0215F78A, handle 0x1d, properties 0x2
[16:36:06][I][ble_client:341]:  characteristic 99FA002A-338A-1024-8A49-009C0215F78A, handle 0x1f, properties 0x2
[16:36:06][I][ble_client:161]: Service UUID: 99FA0030-338A-1024-8A49-009C0215F78A
[16:36:06][I][ble_client:162]:   start_handle: 0x20  end_handle: 0xffff
[16:36:06][I][ble_client:341]:  characteristic 99FA0031-338A-1024-8A49-009C0215F78A, handle 0x22, properties 0xc
[16:36:06][D][esp32_ble_tracker:214]: Starting scan...
[16:36:06][D][esp32_ble_tracker:720]: Found device CA:B3:52:CE:1E:70 RSSI=-56
[16:36:06][D][esp32_ble_tracker:741]:   Address Type: RANDOM
[16:36:06][D][esp32_ble_tracker:745]:   TX Power: 2
[16:36:06][D][esp32_ble_tracker:720]: Found device FE:96:45:99:85:E0 RSSI=-92
[16:36:06][D][esp32_ble_tracker:741]:   Address Type: RANDOM
[16:36:06][D][esp32_ble_tracker:743]:   Name: 'Charge 4'
[16:36:07][D][esp32_ble_tracker:720]: Found device 37:F7:7F:51:C3:81 RSSI=-50
[16:36:07][D][esp32_ble_tracker:741]:   Address Type: RANDOM
[16:36:10][D][esp32_ble_tracker:720]: Found device B4:E8:42:2D:D0:89 RSSI=-66
[16:36:10][D][esp32_ble_tracker:741]:   Address Type: PUBLIC
[16:36:10][D][esp32_ble_tracker:743]:   Name: 'LEDnetWF0100332DD088'
[16:36:11][W][idasen_desk_controller:104]: Error reading char at handle 26, status=5
[16:36:13][D][esp32_ble_tracker:720]: Found device DE:9E:9A:10:97:6B RSSI=-84
[16:36:13][D][esp32_ble_tracker:741]:   Address Type: RANDOM
[16:36:22][D][esp32_ble_tracker:720]: Found device 7E:C8:A9:90:13:FC RSSI=-82
[16:36:22][D][esp32_ble_tracker:741]:   Address Type: RANDOM
[16:36:25][D][esp32_ble_tracker:720]: Found device C4:80:7F:64:1D:5F RSSI=-90
[16:36:25][D][esp32_ble_tracker:741]:   Address Type: RANDOM
[16:36:36][W][idasen_desk_controller:049]: [Desk] Disconnected!

Looks promising at first, but then the error pops up, it disconnects again and the loop with the first log I showed continues.
Any idea what could be causing this?
If you need any more information, please let me know!
Thank you.

Looking at the documentation for BLE error codes:

Status
Status Hex
Description

5
0x05
BLE_HCI_AUTHENTICATION_FAILURE

Seems to be some sort of authentication failure. Any idea why? I pressed the pairing button, maybe I could also try completely resetting the desk

hey did you get a fix for this?

I didn't! If you have any additional information though, please let me know!

I was thinking maybe the desk is asking for a code but esphome does not support codes yet

mmmh, that could be a reason but I wouldn't think so, this is working for so many other people
what kind of board are you using?

esp 32 and my table is a new idasen

Okay, I bought mine in september 2020 🤔

Got the same errors in the log unfortunately. Was working with 1.2.3 until a few days ago but now neither 3.0.0. nur 1.2.3 is working.

hmm so its nothing new then, where did u get your esp 32 i got mine off amazon it may be the ble chip (which i doubt)

@j5lien can you please look into this?

I have the same issue :(

I was thinking maybe the desk is asking for a code but esphome does not support codes yet If there was a code I’d would be 0000 or 1111

I don't think this is the case, since when pairing the desk to my phone it didn't ask for any pairing code

Workaround:

add v1.2.3 with the accompanying config and install
overwrite with the 3.0.0 config

Sensors are not updating, though...

In my case workaround doesn't help. Actually, it helps for a moment, and then I get the same error.

Happens to me, too.
Workaround:
1. add v1.2.3 with the accompanying config and install

2. overwrite with the 3.0.0 config

Sensors are not updating, though...

In the end, I tried this yesterday, and it worked! I've used v1.2.2, because v1.2.3 did not work for me. Saw this workaround originally here and followed its steps.
It is working since yesterday, both moving the desk and reading the sensors
To do the initial pairing with the desk used the following config:
esphome:
  name: *********    <- put the desired name here
  platform: ESP32
  board: esp32dev
  libraries:
    - "ESP32 BLE Arduino"
# Enable logging
logger:

# Enable Home Assistant API
api:

ota:
  password: ***************************************

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "*********"
    password: "**************"

captive_portal:

external_components:
  - source<EMAIL_ADDRESS>

idasen_desk_controller:
  mac_address: "**:**:**:**:**:**"

cover:
  - platform: idasen_desk_controller
    name: "Desk"

Once paired successfully, used the following config:
esphome:
  name: *********    <- put the desired name here

esp32:
  board: esp32dev
  framework:
    type: arduino

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:
  password: ***************************************

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: *********************
    password:  *********************

captive_portal:

external_components:
  - source<EMAIL_ADDRESS>
esp32_ble_tracker:

globals:
  # To store the Desk Connection Status
  - id: ble_client_connected
    type: bool
    initial_value: 'false'

ble_client:
  - mac_address: "**:**:**:**:**:**"
    id: idasen_desk
    on_connect:
      then:
        # Update the Desk Connection Status
        - lambda: |-
            id(ble_client_connected) = true;
        - delay: 5s
        # Update desk height and speed sensors after bluetooth is connected
        - lambda: |-
            id(desk_height).update();
            id(desk_speed).update();
    on_disconnect:
      then:
        # Update the Desk Connection Status
        - lambda: |-
            id(ble_client_connected) = false;

idasen_desk_controller:
  ble_client_id: idasen_desk
  only_up_down_command: false

cover:
  - platform: idasen_desk_controller
    name: "Desk"

sensor:
  # Desk Height Sensor
  - platform: ble_client
    ble_client_id: idasen_desk
    id: desk_height
    name: 'Desk Height'
    service_uuid: '99fa0020-338a-1024-8a49-009c0215f78a'
    characteristic_uuid: '99fa0021-338a-1024-8a49-009c0215f78a'
    icon: 'mdi:arrow-up-down'
    unit_of_measurement: 'cm'
    accuracy_decimals: 1
    update_interval: never
    notify: true
    lambda: |-
      uint16_t raw_height = ((uint16_t)x[1] << 8) | x[0];
      unsigned short height_mm = raw_height / 10;

      return (float) height_mm / 10;

  # Desk Speed Sensor
  - platform: ble_client
    ble_client_id: idasen_desk
    id: desk_speed
    name: 'Desk Speed'
    service_uuid: '99fa0020-338a-1024-8a49-009c0215f78a'
    characteristic_uuid: '99fa0021-338a-1024-8a49-009c0215f78a'
    icon: 'mdi:speedometer'
    unit_of_measurement: 'cm/min' # I'm not sure this unit is correct
    accuracy_decimals: 0
    update_interval: never
    notify: true
    lambda: |-
      uint16_t raw_speed = ((uint16_t)x[3] << 8) | x[2];
      return raw_speed / 100;

binary_sensor:
  # Desk Bluetooth Connection Status
  - platform: template
    name: 'Desk Connection'
    id: desk_connection
    lambda: 'return id(ble_client_connected);'

  # Desk Moving Status
  - platform: template
    name: 'Desk Moving'
    id: desk_moving
    lambda: 'return id(desk_speed).state > 0;'

Thanks for sharing. I'll try this approach.

Reading sensors works, for now, however moving is not :(
I'll see if it keep working over longer period of time

And it got disconnected after 2 days and doesn't connect anymore...

@leukanos at least you progressed 3 handles! 😁
does anybody know if it is possible to use esphome at the pull requests head?

I did pretty much what andrethrill said in the comment below me. Things work, but the sensors don't :/ I'm using Adafruit ESP32 feather board if that's any help. The controls don't work for down (up and stop do), but the automation does (because it's behaving like a curtain).

I’m also seeing this issue. I just got a new desk, partly because I wanted to automate it with this project 😄
Is there anything I can do to test/debug? It isn’t clear from reading the thread if there are any leads to follow up on.
Otherwise I’ll do my own investigation

Unfortunately we have not found a fix yet. But please send your progress here so others don’t have the same issue

small update from me:

I've updated my esphome in home assistant to this version (look at these release notes, they changed the install method: https://esphome.io/changelog/2022.2.0.html)

it worked for a bit, but the card showed wrong values so i tinkered a bit with the configuration. The reported height is correct now, but the connection status is false and sometimes it randomly stops working - I haven't found out why yet.

I'll post my configuration here later, probably tomorrow. I'll also continue to look into why the bugs are still occuring

See below for what I'm running currently. This is running on ESPHome 2022.3.2. I have 2 external_components setup:

My fork of this repository, which I've enhanced (or fixed?) the ability to auto drive on the desks that don't have auto drive. For example, when the component received a request to go to a certain position, it was sending that to the desk and the desk would start moving, but it would only move a couple of inches at most and then stop. But the component didn't attempt to continue sending the command even though it could see that it wasn't at the right position. I'm not sure if this was intentional or not...but regardless, I can auto drive my desk now. I still need to figure out the calibration though because I'm pretty sure the numbers are off, but I haven't measured. Also there are some edge cases where I've found that it gets stuck in the loop continuously sending the command to move, but the desk doesn't move. However because the ESP keeps sending the command, the paddle on the desk becomes non-responsive until I restart the ESP (and maybe the desk). Also, I think when the desk is moving, there are a lot of updates that come through, but I don't think all of them make it to home assistant. The buffer of queued messages gets too full. So for example, on my home assistant card I have a stand position at 117cm and if I press it, the desk does it's thing and it does in fact make it to the position, but home assistant may get the last update at like 115cm. A quick tap of the paddle that effectively doesn't move the desk much causes one more update to run through and home assistant shows it at 117cm.
The PR I had submitted to ESPHome, which I believe is in the 2022.4.0b1 release

esphome:
  name: office-desk-controller-frontier

esp32:
  board: esp32dev
  framework:
    type: arduino

# Enable logging
logger:
  level: INFO

# Enable Home Assistant API
api:

ota:
  password: !secret ota_password

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Office-Desk-Controller-Frontier"
    password: !secret ap_password

captive_portal:

external_components:
  - source: github://ammmze/esphome-idasen-desk-controller@make-it-work
  - source: github://pr#3320
    components:
      # list all components modified by this Pull Request here
      - ble_client
      - esp32_ble_tracker

globals:
  # To store the Desk Connection Status
  - id: ble_client_connected
    type: bool
    initial_value: 'false'

esp32_ble_tracker:

ble_client:
  - mac_address: "00:00:00:00:00:00" # Replace with the desk bluetooth mac address
    id: idasen_desk
    on_connect:
      then:
        # Update the Desk Connection Status
        - lambda: |-
            id(ble_client_connected) = true;
        - delay: 5s
        # Update desk height and speed sensors after bluetooth is connected
        - lambda: |-
            id(desk_height).update();
            id(desk_speed).update();
    on_disconnect:
      then:
        # Update the Desk Connection Status
        - lambda: |-
            id(ble_client_connected) = false;

idasen_desk_controller:
    # Reference to the ble client component id
    # -----------
    # Required
    ble_client_id: idasen_desk
    # Fallback to use only up and down commands (less precise)
    # -----------
    # Optional
    only_up_down_command: false

cover:
  - platform: idasen_desk_controller
    name: "Office Desk"

sensor:
  # Desk Height Sensor
  - platform: ble_client
    ble_client_id: idasen_desk
    id: desk_height
    name: 'Office Desk Height'
    service_uuid: '99fa0020-338a-1024-8a49-009c0215f78a'
    characteristic_uuid: '99fa0021-338a-1024-8a49-009c0215f78a'
    icon: 'mdi:arrow-up-down'
    unit_of_measurement: 'cm'
    accuracy_decimals: 1
    update_interval: never
    notify: true
    # filters:
    #   - debounce: 0.5s
    lambda: |-
      uint16_t raw_height = ((uint16_t)x[1] << 8) | x[0];
      unsigned short height_mm = raw_height / 10;

      return (float) height_mm / 10;

  # Desk Speed Sensor
  - platform: ble_client
    ble_client_id: idasen_desk
    id: desk_speed
    name: 'Office Desk Speed'
    service_uuid: '99fa0020-338a-1024-8a49-009c0215f78a'
    characteristic_uuid: '99fa0021-338a-1024-8a49-009c0215f78a'
    icon: 'mdi:speedometer'
    unit_of_measurement: 'cm/min' # I'm not sure this unit is correct
    accuracy_decimals: 0
    update_interval: never
    notify: true
    # filters:
    #   - debounce: 0.5s
    lambda: |-
      uint16_t raw_speed = ((uint16_t)x[3] << 8) | x[2];
      return raw_speed / 100;

binary_sensor:
  # Desk Bluetooth Connection Status
  - platform: template
    name: 'Office Desk Connection'
    id: desk_connection
    lambda: 'return id(ble_client_connected);'

  # Desk Moving Status
  - platform: template
    name: 'Office Desk Moving'
    id: desk_moving
    lambda: 'return id(desk_speed).state > 0;'

well thanks to you this is the first time HA moved my desk

@ammmze Neat! I also tried this config out and it seems to partially work. I can now move the desk up and down with Home Assistant. However, the sensors don't seem to be updating. I don't need them for now, it isn't quite as nice but I can work with a cover percentage in Home Assistant so I just removed them for now. My more minimal config therefore look like...
external_components:
  - source: github://ammmze/esphome-idasen-desk-controller@make-it-work
  - source: github://pr#3320
    components:
      - ble_client
      - esp32_ble_tracker

substitutions:
   nicename: Study
   devicename: study

esphome:
  name: ${devicename}
  platform: ESP32
  board: esp32dev

# Enable logging
logger:
  level: INFO

# Enable Home Assistant API
api:

ota:
  password: "***************************************"

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  fast_connect: true

esp32_ble_tracker:
ble_client:
  - mac_address: "00:00:00:00:00:00" # Replace with the desk bluetooth mac address
    id: idasen_desk

idasen_desk_controller:
    ble_client_id: idasen_desk
    only_up_down_command: false

cover:
  - platform: idasen_desk_controller
    name: "Study Desk"

@d0ugal the first time I loaded it in the sensors did not update but then I unplugged it and plugged it back in (the esp) and it’s working

Good point, the height did seem to update once after restart. It didn't seem to update after that but I'll do some experimentation.

@d0ugal Did you ever get a chance to do some experimenting? I'm getting the same thing where the sensors are updated when the ESP first boots up but never again.

@callumgare I had some problems until 4.0.0 was released. Since then it has worked fine and I don't get the issue anymore. My full config is now the following;
external_components:
  - source<EMAIL_ADDRESS>
substitutions:
   name: study-desk

esphome:
  name: ${name}
  platform: ESP32
  board: esp32dev

esp32_ble_tracker:

ble_client:
  - mac_address: "00:00:00:00:00:00" # Replace with the desk bluetooth mac address
    id: idasen_desk

idasen_desk_controller:
    ble_client_id: idasen_desk
    only_up_down_command: false

cover:
  - platform: idasen_desk_controller
    name: "Study Desk"

# These just include some common things like wifi details that I share between devices. Nothing speicifc to the desk.
<<: !include .common.yaml
<<: !include .atom-identify.yaml

Thanks for that @d0ugal!


Close button and modal transition mismatch

When closing the modal it disappears immediately but the close button has a 200ms transition. I would either add a transition to the card as well or restrict the transition to only affect the filter property (i guess that is the reason it was added).
P.S. I hope you saw the eclipse and can check that card 🙂

Good catch! Fixed up the animations a little, and there was a bit of a graphical glitch with the different fading times, so that's been cleaned up as well, so it feels a bit cleaner now. Thanks!


Move PWM's set_duty_cycle_raw from public to protected

This PR fixes #149.

For records-keeping:

This project is licensed under Apache License v2.0 for any software, and Solderpad Hardware License v2.1 for any hardware - do you agree that your contributions to this project will be under these licenses, too? Yes
Were any of these contributions also part of work you did for an employer or a client? No
Does this work include, or is it based on, any third-party work which you did not create? No

@rohanpurohit If you have access to a ventilator unit where the Nucleo and prototype electronics board have been integrated together with the flow sensors and the solenoid valves, would you be able to test this PR to confirm that the valves are closed upon program startup (even if the valves were previously opened before the Nucleo was forcibly restarted, e.g. by pressing its reset button)? The only place where we used set_duty_cycle_raw was at startup.

@rohanpurohit If you have access to a ventilator unit where the Nucleo and prototype electronics board have been integrated together with the flow sensors and the solenoid valves, would you be able to test this PR to confirm that the valves are closed upon program startup (even if the valves were previously opened before the Nucleo was forcibly restarted, e.g. by pressing its reset button)? The only place where we used set_duty_cycle_raw was at startup.

We were supposed to bring a working ventilator unit from one of the hospitals, the other unit we have has the full feature power board and the new PCB I presume and there are no connections made on that one, so I think we can test it on a ventilator unit once Renji collects the one from the hospital, so I guess its kinda blocked from my end, maybe you could go ahead with it if you have tested it on your end?

Currently I don't actually have a way of testing this with the hardware integrated. Since this change is basically static (i.e. any issues which occur should probably be caught by the compiler), let's merge in this fix for now and then we can file a new issue if a regression is found later.


Issue on docs for Build a Go App with CockroachDB

The documentation does not currently layout any mechanism for using either of the provided Go drivers with the client TLS authentication mechanisms explained in the "secure cluster" sections of the video.
Taking as an assumption that running an insecure cluster in production would be irresponsible I feel that it would be beneficial to adapt the driver explanations to cover how to use the TLS client certificates within a postgres client driver.
Or simply referring to the use of Passwords as a fallback in the case that the driver does not natively support such a mechanism.

Thanks for opening this issue, @AJCStriker. It's on our near-term plan to provide secure versions of the build an app tutorials. Here's the main issue, in case you want track progress: https://github.com/cockroachdb/docs/issues/631

Duplicate of https://github.com/cockroachdb/docs/issues/631


How to use my own data?

Thank you for the excellent work. I'm currently trying to adapt it for my own data. I have a AgileX Robot. How can I replace it with data from the AgileX Robot and my own environment?

Hi, that sounds really exciting. You can use our perception stack and agent API as long as you implement your low-level stack to use the action and observations interfaces: https://github.com/facebookresearch/home-robot/blob/main/src/home_robot/home_robot/core/interfaces.py. You will have to build your own "AgileX" environment for this. You can look up our Stretch's environment as a reference: https://github.com/facebookresearch/home-robot/blob/main/src/home_robot_hw/home_robot_hw/env/stretch_pick_and_place_env.py

Thank you, I'm trying this out, and once again, thanks for your work!


fix: osmo lp fiat / base unit calculations

Description
This PR:

Fixes calculations to properly use base unit amounts, not precision ones, and not "floated base units"
Brings vernacular sanity to the domain this was spotted on
Adds loading render cycles sanity, so we don't try and do math on loading market data, lp asset data etc
Fixes input validation where we were doing "balance base unit > input precision" as a check

Notice

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[x] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
N/A
Risk

Testing

Fiat input is working for Osmo LP and produces valid Txs
Fiat/crypto input validation is working
Displayed amounts are correct vs. the ones on the Tx

Engineering

☝🏽

Operations

☝🏽

Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #3827   👈

This comment was auto-generated by Graphite.

@gomesalexandre @pastaghost the lp token precision in https://github.com/shapeshift/lib/pull/1198 is published in @shapeshiftoss/asset-service-v8.8.1 if you want to bump it in this PR too
@pastaghost i'm happy if you approve this particular PR as you have the most context in this domain currently

LGTM


Provide option for parsing function bodies

Hi there, I'm trying to use CppAst.NET to parse metal-cpp header files, which are a wrapper of the Objective-C API. The underlying Objective-C functions being called are contained within a macro within the function body.

To generate valid C# code, I need to be able to access the string used to generate the selector inside the function bodies, however currently, function body parsing is disabled.
Could an option be added to enable function body parsing? I'm happy to PR it myself, however, I don't know what other modifications would be required.

Could an option be added to enable function body parsing? I'm happy to PR it myself, however, I don't know what other modifications would be required.

Adding such an option would require also to parse the full content, handle all the syntax elements, create all the associated AST classes. Unfortunately, I don't want to support this as it would require a significant amount of work - and maintenance.
This library is meant for parsing interfaces, signatures of methods and so mostly header files.

Adding such an option would require also to parse the full content, handle all the syntax elements, create all the associated AST classes. Unfortunately, I don't want to support this as it would require a significant amount of work - and maintenance. This library is meant for parsing interfaces, signatures of methods and so mostly header files.

If I'm not mistaken, if function body parsing was enabled, could I get this information from the generic CppToken? I don't need full function parsing; I just need to be able to get the _MTL_PRIVATE_SEL contained within.

If I'm not mistaken, if function body parsing was enabled, could I get this information from the generic CppToken? I don't need full function parsing; I just need to be able to get the _MTL_PRIVATE_SEL contained within.

I would believe that the visitor would still go through lots of nodes - and generate several warnings or errors along the way, but maybe be that could be fine, you will have to try.

I conducted an inital test with the following code:
[Test]
        public void TestComplex()
        {
            ParseAssert(@"
#include <objc/runtime.h>

#define _NS_PRIVATE_SEL(accessor) (Private::Selector::s_k##accessor)
#define _NS_PRIVATE_DEF_SEL(accessor, symbol) extern SEL s_k##accessor

namespace Private
{
    namespace Selector
    {
        _NS_PRIVATE_DEF_SEL(test,
            ""test"");
    }
}

SEL method()
{
    return _NS_PRIVATE_SEL(test);
}
",
                compilation =>
                {
                    Assert.False(compilation.HasErrors);
                },
                new CppParserOptions
                {
                    SystemIncludeFolders =
                    {
                        "/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/v1",
                        "/Library/Developer/CommandLineTools/usr/lib/clang/15.0.0/include"
                    },
                    AdditionalArguments =
                    {
                        "-isysroot",
                        "/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk",
                    },
                    TargetCpu = CppTargetCpu.ARM64,
                    TargetSystem = "darwin",
                    TargetVendor = "apple",
                    ParseSystemIncludes = true,
                    ParseMacros = true
                });
        }

It seemed to run without errors, with the only problem being that the method's contents are not available in the AST yet. But I think it might be possible.


Consistent labeling of kyma module: API-Gateway

Description
Changes proposed in this pull request:

Use common labels for Kyma module, based on decision being made

Related issue(s)

https://github.com/kyma-project/api-gateway/issues/795
https://github.com/kyma-project/community/issues/864

We must not forget to update the release jobs that build the image to include the version build-arg

there is a problem with it, we will discuss it


[CHORE]  Clean up mobile CSS

@artillect @minnieoo  CSS crew
Image submitted by a user:

On the last kbin theme (purple), install updates button has low contrast and is painful/hard to read. Are we using kbin's color theming correctly for this button?
More spacing between header icons to make tapping easier
Reset button is huge and occludes footer
Bug icon is getting thrown out of alignment

taking a look

Are we using kbin's color theming correctly for this button?

it is indeed the correct link color for this theme, but it's obviously not gonna work on that green so yea, ill try and fix it

Take a look at some of the bg vars, var(--kbin-alert-danger-bg) seems pretty consistent on all themes, but maybe not the most handsome? The success-bg currently being used seems like it is not designed for this use case, should be used sparingly.

Another thing I noticed is that the "updates available" notifier is all but invisible on the purple theme:

var(--kbin-alert-danger-bg) aint gonna work unfortunately, on some it does, some it doesn't. have a feeling color blind people especially will struggle here with this one. ill see about other options. also, noted about the update notifier

The original user who reported it is colorblind
Guess we need higher separation between fg and bg text?

yea definitely, i'm looking for css vars that have the most contrast between each other in all themes

i would want to say the upvote vars, as that should be well contrasted on all themes, but some themes actually have the same contrast issue :smiling_face_with_tear: :smiling_face_with_tear:

using: var(--kbin-vote-bg) for bg and var(--kbin-vote-text-color) for color, and we could experiment with a hover color from there if its necessary (though i think it's pretty clear what it does with or without hover color)

though maybe to combat this we can just add a border with the  var(--kbin-vote-text-color)? (first is 2px, 2nd is 1px)

Right, I think some of the themes themselves are half-baked right now and their colors are not set up exactly right.
We don't need a hover color per se, we can just use opacity like we are now.
The border idea seems decent provided it works on all themes. I am pretty meh about box shadows in general, and the design of the interface right now is pretty flat, so seems out of place.

agreed on box shadows, not really a fan lol, but thought i'd present the option anyway. ill test on the rest of the themes now and update you

whyyyyy light theme's contrast sucks 🥲 🥲 so close

I was actually thinking you'd do idea 1 but add a border to all of them, does that help at all?

with var(--kbin-alert-danger-bg)?

No, in the post after that you had three ideas (I thought), but they looked pretty similar to one another so now I guess it was actually two ideas with similar looking screenshots. But in the first pic you had a green button on the gray theme, so maybe that was unintentional?
The fact of the matter is that the light theme is terrible lol.

I am mocking it in Stylus now to see your edits

oh, that was actually due to the colors for solarized dark on the panel not loading in 🥲 , sometimes the panel stays grey despite the theme, but it corrects itself upon opening and closing

Try this,
.kes-version .new {
	background-color: var(--kbin-vote-bg) !important;
	border: 2px solid var(--kbin-vote-text-color);
}
.kes-version .new:hover {
	opacity: 0.4
}

Don't set the fg text color and let it set its own. Light theme defaults to a bluish color. I think this is readable on all themes, albeit spartan.

Second edit (reverse opacity):
.kes-version .new {
	background-color: var(--kbin-vote-bg) !important;
	border: 2px solid var(--kbin-vote-text-color);
	opacity: 0.4
}
.kes-version .new:hover {
	opacity: 0.8
}

o yea that's a good solution, light theme is legible finally :0

Item 1 resolved by 12650d8d812f7dadf79cc72943e8683c500f55f3
How about the updates icon? Should be a lot easier, I think

yea it should be, ill see about it rn

this is with var(--kbin-upvoted-color), once again light theme (dark blue bg) is the odd man out. pretty much everything is diluted with that one.

and this is var(--kbin-danger-color). i can understand why red may not be preferable, but it certainly does bring attention to it, except in light theme bc its still fuckin diluted lol

Best guess is the white theme is supposed to be a high visibility/accessibility theme, so colors look like photonegatives at times. Nix on the red. There aren't a lot of choices here, the green is probably good enough. The default purple bg theme is just blah.

Could also just inherit the same color as the icon, not sure if that is good or not.

i don't think people would necessarily miss it if it was the same color as the icon, but it wouldn't call attention to itself. i agree that the green is good enough, anyone using light theme anyway, considering how bad the contrast is, ought to be able to spot it, they must have good vision and aren't needing enhanced visual accessibility. i think it stands out well enough.

Seems like a best-effort approach here is good enough, can we drop the hover color on the notifier then?
People using light theme: https://www.youtube.com/watch?v=PWFF7ecArBk

People using light theme: https://www.youtube.com/watch?v=PWFF7ecArBk

lmfao that's so real, i don't know how they do it 💀, cant believe its still the default on a lot of sites

can we drop the hover color on the notifier then?

if you'd like, what do you think?

Feels like managing one color is less problematic than two, and seems like they really only give you dull orange, green, red, and white, so feels like if green is the base notifier color, none of those really works? Keep it simple

As far as I can tell, kbin-success-color is identical to kbin-upvoted-color, and seems more semantically correct, so going with that one

sorry for my late response, i fell asleep. yea they are pretty much the same, i just chose whichever green i had spotted first at the time

No problem. I'm not sure about issues 3 and 4, maybe arti will have an idea about it

For now, I think I've managed to force these elements into alignment when the device is smaller than 576px, but it's a bit of a hack atm since I hardcoded the pixel offsets to look reasonably correct. The main problem is that the version number/update button in the header doesn't fit well on mobile, so it'd probably be better if we checked the innerWidth when setting up the menu itself, and insert that element into its own div if on mobile, then use grid order to put it after the header but before the sidebar.


Moved Start/Stop buttons to the top of the preview.

Click on the preview starts / pauses the engine.
Added EVT_IKALOG_PAUSE event.

Cool, thanks!


Add CLI storage conf example to run manpage

Signed-off-by: TomSweeneyRedHat<EMAIL_ADDRESS>Add an example to the run man page to illustrate how
you can configure storage from the CLI.  This addresses
a request from issue #2662.
Signed-off-by: TomSweeneyRedHat<EMAIL_ADDRESS>

@tobwen PTAL

@TomSweeneyRedHat LGFM, but maybe just use overlay.mount_program=/opt/fuse-overlayfs to keep the lines short? :-)

@tobwen, I went with @mheon's shortened version instead.

@TomSweeneyRedHat SIAB, LGFM, thx

LGTM

/lgtm


Audio not working with BabylonJS Demo on iOS devices

With the latest version of this repository, text-to-speech audio does not work on iOS devices. A mute button appears at the top left, and even when clicked on, the audio still does not play. This issue started happening in the recent months. Just a theory, but perhaps the issue is related to version 4 of BabylonJS, and it was fixed in more recent updates (e.g. version 5 or 6). Please see the screenshot attached.

On iOS, the click event has to happen before any Web Audio is played. If this does not happen, Babylon audio is permanently broken the rest of the session until a user restarts the tab (ouch!).
https://forum.babylonjs.com/t/remove-unmute-button/27577


Validation Provider access to invalid rules

Versions

vee-validate: 2.1.7
vue: 2.6.8

Describe the bug
I want to know which rule is invalid but i have only the error messages
To reproduce
Steps to reproduce the behavior:

Go to input
Fill with a basic string
See email error message and errors array

Expected behavior
The errors object is a basic array with errors messages but i can't access to the rule error to display custom message for example.
Demo link
Codesandbox.
Desktop (please complete the following information):

OS: any
Browser any
Version any

Smartphone (please complete the following information):

Device: any
OS: any
Browser any
Version any

Additional context
There is a way to access to first or all rule and check if it's valid or invalid or maybe transform the errors array to a ErrorBag?

The validation provider currently lacks this feature, but I agree its useful to have.

@logaretm thank you for this enhancement! This works also in the Observer?

The observer has no access to the failed rules of each provider since the information is specific to each provider rather than the entire form. if you have a use-case in mind feel free to suggest.

Sure, in my use-case I have two field and one them have to be required with a custom message:
//template
<validation-observer>
  <form>
   <custom-input name="field1" rule="required" />
   <custom-input name="field2" rule="required" />

Field 1 or Field 2 is required

....

Now I use a workaround to have this behavior using the data value, but using complex rules this can be helpful

@logaretm Perhaps I did not explain this fully... tell me if you need an example with codesandbox


update minor versions

and check what fails to fix them incrementally for 0.7.1 release

merging to dev and later fix the test failures one by one

I'm -1 for this merge. We should fix the tests before the merge. The tests are broken because the code are broken too.

this is on development branch and the fails are on dev branch. Intended to fix the failures in dev branch so no problem in merging as it wont effect the released ones.

@auvipy we should not merge failing PR's in the development branch.


RDS Core: separate general methods from the sriov verification suite

helper.go file created

verifySRIOVConnectivity was renamed to the verifyConnectivity and moved to the helper.go

createServiceAccount, deleteServiceAccount, deleteClusterRBAC, createClusterRBAC, deleteConfigMap, createConfigMap, deleteDeployments, findPodWithSelector, defineContainer, verifyMsgInPodLogs were moved to the helper.go

'if pState == "NonCompliant"' state was changed to the 'if pState == "NonCompliant"'. Depends on deployment type it can be some extra policies with no state at all be found and it can fail test with no reason

@yprokule Hi! as was discussed, PTAL

@yprokule I'm sorry, but I do not understand why general methods like delete/create API objects cannot be outside the sriov validation test. What if we need it for the other operator's tests? For example, configmap, rbac, and sa config can be required for the keda config.
I also do not understand what is terrible in double-checking if ns exists.
Anyway, with all the requested changes, we are returning to the original version; I do not see any value in this MR.
Thank you!

@yprokule I'm sorry, but I do not understand why general methods like delete/create API objects cannot be outside the sriov validation test. What if we need it for the other operator's tests? For example, configmap, rbac, and sa config can be required for the keda config.

@elenagerman what are U talking about? I didn't object about having some of the common methods in a dedicated file. What I said is that during your move of existing methods to a new file U broke the existing logic and were asked to fix it

I also do not understand what is terrible in double-checking if ns exists.

U don't double check but create if it's missing which again affects existing logic. And what the problem to run this at the beginning of the test or in the setup block?

Anyway, with all the requested changes, we are returning to the original version; I do not see any value in this MR.

Again, not sure where U got the idea that we are returning to the original version - all U had to do was to address broken logic in the PR.
Feel free to reopen PR and address comments or I might piggyback on this work and adjust it myself.
Thank you!


Feat/kitchen sink projects

Please describe the changes this PR makes and why it should be merged:
Status

[ ] Code changes have been tested against prettier, or there are no code changes
[ ] I know how to update typings and have done so, or typings don't need updating

Semantic versioning classification:

[ ] This PR changes the codebase

[ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
[ ] This PR changes the internal workings with no modifications to the external API (bug fixes, performance improvements)

[ ] This PR only includes non-code changes, like changes to documentation, README, etc.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 25.682%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1256

Relevant Lines:
5083

💛  - Coveralls


Fix python path in code build

Code build uses pyenv python  path which is used in the build phase.
This PR changes the python path to use the system's path instead.

cc https://github.com/OnionIoT/openwrt-buildsystem-wrapper/issues/12


Mistyping errors on Chapter 2 and 5

In Chapter 2 on Error Control, writing about 2.2 Positive predictive value, the fourth line states "They key to understanding this difference is that two different probabilities are calculated.". "They key" maybe should be "The key".
In Chapter 5 on Asking Statistical Questions, writing about 5.2 Prediction, the example "For example, during the COVID-9 pandemic a large number of models (...)". "COVID-9" maybe should be "COVID-19.

thanks, fixed


Add Dockerfiles for Ubuntu 22.04 LTS (Jammy Jellyfish) Beta

As Ubuntu 22.04 LTS (Jammy Jellyfish) Beta release is available, I suggest to add related Dockerfiles.
https://releases.ubuntu.com/22.04/
The final release is expected on the 21st April.
See Jammy Jellyfish Release Schedule

Thanks a lot @sestegra!


[core & hive] Introduce renameDatabase method for catalog

fix https://github.com/apache/incubator-paimon/issues/716
Purpose
Introduce renameDatabase method for catalog
Tests
FileSystemCatalogTest
API and Format
no
Documentation
no

I have updated this PR. PTAL. @SteNicholas thx.

@s7monk could you take a look at above method IMetaStoreClient#alterDatabase (from @SteNicholas )?

@s7monk could you take a look at above method IMetaStoreClient#alterDatabase (from @SteNicholas )?

ok.


install error on Windows

(C:\Anaconda3) C:\Anaconda3\cudamat-master>python setup.py install
running install
running bdist_egg
running egg_info
writing top-level names to cudamat.egg-info\top_level.txt
writing cudamat.egg-info\PKG-INFO
writing dependency_links to cudamat.egg-info\dependency_links.txt
reading manifest file 'cudamat.egg-info\SOURCES.txt'
writing manifest file 'cudamat.egg-info\SOURCES.txt'
installing library code to build\bdist.win-amd64\egg
running install_lib
running build_py
running build_ext
building 'cudamat.libcudamat' extension
error: Microsoft Visual C++ 14.0 is required. Get it with "Microsoft Visual C++ Build Tools": http://landinghub.visualstudio.com/visual-cpp-build-tools
But I have installed VC,how to solve it?

Can you please try: pip install http://github.com/f0k/cudamat/archive/simplify-compile.zip?
This uses a different compilation setup. It should work as long as nvcc works. Let me know if and what error you get with this command.

I use that command and get this error!
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\bin\nvcc.exe -O -Ic:\anaconda3\include -Ic:\anaconda3\include -c cudamat/cudamat.cu -o build\temp.win-amd64-3.5\Release\cudamat/cudamat.obj -Ic:\anaconda3\include -Ic:\anaconda3\include
nvcc warning : The 'compute_20', 'sm_20', and 'sm_21' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning).
nvcc fatal   : Cannot find compiler 'cl.exe' in PATH
error: command 'C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\bin\nvcc.exe' failed with exit status 1
----------------------------------------
Command "c:\anaconda3\python.exe -u -c "import setuptools, tokenize;file='C:\Users\fan18\AppData\Local\Temp\pip-olpcrxur-build\setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record C:\Users\fan18\AppData\Local\Temp\pip-3wg_5sjx-record\install-record.txt --single-version-externally-managed --compile" failed with error code 1 in C:\Users\fan18\AppData\Local\Temp\pip-olpcrxur-build\

nvcc fatal : Cannot find compiler 'cl.exe' in PATH
So even if you have installed MSVC, it's not on the PATH for the command line prompt you used. An easy way out could be:
set NVCCFLAGS="--compiler-bindir=C:\..." --cl-version=2014
pip install http://github.com/f0k/cudamat/archive/simplify-compile.zip

where C:\... is the path to your MSVC compiler, something like C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64 (assuming that you have a 64-bit Python). I'm not sure if blanks in that path are a problem. Experiment with the placement of the quotation marks if it doesn't work (around everything after =, just around the path, around everything after set, ...).
If you cannot easily figure out the correct bits to put into set NVCCFLAGS=..., then try compiling a simple test program as described on https://github.com/Lasagne/Lasagne/wiki/From-Zero-to-Lasagne-on-Windows-7-(64-bit)#debugging. (Ignore everything else on that wiki page, it does not apply to cudamat.)

I have tryed that command,but get this error!
nvcc -o cuda_check.exe cuda_check.c --compiler-bindir="C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\amd64" --cl-version=2015 -lcuda -lcudart -lcublas
nvcc warning : The 'compute_20', 'sm_20', and 'sm_21' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning).
nvcc fatal   : Microsoft Visual Studio configuration file 'vcvars64.bat' could not be found for installation at 'C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/../../..'

If I want to use cudamat ,I have to install Microsoft Visual Studio 2010?

nvcc fatal : Microsoft Visual Studio configuration file 'vcvars64.bat' could not be found for installation at 'C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/../../..'

This pretty much nails it: You will need a vcvars64.bat for nvcc. Sometimes this is installed with MSVC, sometimes you need to create it manually. For Lasagne, I figured out how to do this for a particular version of a MSCV compiler: https://github.com/Lasagne/Lasagne/wiki/From-Zero-to-Lasagne-on-Windows-7-(64-bit)#configuration
For other compiler versions, it might work the same way. Feel free to search for "nvcc vcvars64.bat" online, it's a common problem.

I have figured the vcvars64.bat problem:https://stackoverflow.com/questions/18727964/nvcc-exe-linking-error-microsoft-visual-studio-configuration-file-vcvars64-bat.But I still cann't install cudamat.
Here is the problem!
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\bin\nvcc.exe -O -Ic:\anaconda3\include -Ic:\anaconda3\include -c cudamat/cudamat.cu -o build\temp.win-amd64-3.5\Release\cudamat/cudamat.obj "--compiler-bindir=C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\amd64" --cl-version=2015 -Ic:\anaconda3\include -Ic:\anaconda3\include
nvcc warning : The 'compute_20', 'sm_20', and 'sm_21' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning).
error: command 'C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\bin\nvcc.exe' failed with exit status 1
----------------------------------------

Command "c:\anaconda3\python.exe -u -c "import setuptools, tokenize;file='C:\Users\fan18\AppData\Local\Temp\pip-r500h4tg-build\setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record C:\Users\fan18\AppData\Local\Temp\pip-z38wjntn-record\install-record.txt --single-version-externally-managed --compile" failed with error code 1 in C:\Users\fan18\AppData\Local\Temp\pip-r500h4tg-build\

error: command 'C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\bin\nvcc.exe' failed with exit status 1

This doesn't say anything about the error, unfortunately. Again, can you please try compiling a simple test program as described on https://github.com/Lasagne/Lasagne/wiki/From-Zero-to-Lasagne-on-Windows-7-(64-bit)#debugging? (Ignore everything else on that wiki page, it does not apply to cudamat.)

I try this command,and get this always exist warning!
nvcc -o cuda_check.exe cuda_check.c --compiler-bindir="C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\amd64" --cl-version=2015 -lcuda -lcudart -lcublas
nvcc warning : The 'compute_20', 'sm_20', and 'sm_21' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning)

I try this command,and get this always exist warning!But I thought it was not a problem.Am I wrong?

The warning about 'compute_20', 'sm_20', and 'sm_21' is not a problem. As explained in the installation instructions, you can compile cudamat with a higher architecture if you want. The problem in your case is that it says the command failed with exit status 1. This is a serious problem, but the warning doesn't have anything to do with it. You'll need to find out why the command failed, that's why I suggested you to compile a simple test program directly with nvcc.

I cann't download the cuda_check.c!The link of it cann't open!Can you email it to me(fan18742422083@163.com)?Thank you!

I cann't download the cuda_check.c!The link of it cann't open!

The link is correct. You can copy/paste the file from https://gist.github.com/f0k/0d6431e3faa60bffc788f8b4daa029b1 if your browser doesn't display the .c file.

Can you email it to me

I removed your email address from your comment, posting it publicly will give you a lot of spam.

Thank you for removing the email address!
I downloaded the cuda_check.c and save it to C:\Anaconda3,then I run these commands:
cd Anaconda3
nvcc -o cuda_check.exe cuda_check.c --compiler-bindir="C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\amd64" --cl-version=2015 -lcuda -lcudart -lcublas
But I only got the same warning:
nvcc warning : The 'compute_20', 'sm_20', and 'sm_21' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning).
Then I removed the last three command line switches in the cuda_check.c:
//case 0x13: return 8;
//case 0x20: return 32;
//case 0x21: return 48;
Try that command,get the same warning!

Try that command,get the same warning!

As I said before, please ignore the warning. Did it produce a cuda_check.exe that you can run?

It didn't produce cuda_check.exe!

It didn't produce cuda_check.exe!

But then it must have given some other error message besides the warning.
As explained in https://github.com/cudamat/cudamat/blob/master/INSTALL.md, you can add -arch=sm_35 to the nvcc call if the warning bothers you too much.

It didn't give any other error message!

But what does it say when you run with --verbose?

I run this command:C:\Anaconda3>nvcc -o cuda_check.exe cuda_check.c --compiler-bindir="C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\amd64" --cl-version=2015 -lcuda -lcudart -lcublas -arch=sm_35 -v
Get this:
#$ VSINSTALLDIR=C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/../../../
#$ VCINSTALLDIR=C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/../../../VC/
#$ C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/../../../VC/bin/amd64/vcvars64.bat
(C:\Anaconda3) C:\Anaconda3>call C:\Users\fan18\AppData\Local\Temp/tmpxft_000003e8_00000000-2.bat
(C:\Anaconda3) C:\Anaconda3>CALL setenv /x64
'setenv'  not an internal or external command, nor a program or batch file that can run.
"CALL setenv /x64" is the content of vcvars64.bat file.Something is wrong with the vcvars64.bat?

Something is wrong with the vcvars64.bat?

Yes. As you can see from the last message, it does not find setenv. You will need to specify the full path, as I did here: https://github.com/Lasagne/Lasagne/wiki/From-Zero-to-Lasagne-on-Windows-7-(64-bit)#configuration
I guess in your case it will be:
CALL "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\SetEnv" /x64

But don't take my word for it, check if there is a "SetEnv.exe" in that directory.

I searched the C drive,but cann't find the "SetEnv.exe"!

What's in your Visual Studio bin directory then? Is there a cl.exe and everything, but no SetEnv.exe?
Maybe it's easier to install a different MSVC version, but I'd be surprised if there wasn't a relatively simple solution to get this to work.


The hOCR specification is at version 1.2

Trivial text edit to update the version mentioned for hOCR.

Thanks


Failed to store PAT using keyring; falling back to file storage.

Describe the bug
Hi Team,
I am facing the below issue while logging to az devops.. pls check and help me out....
a-> Added the PAT with full access.
Generate a Personal Access Token with Packaging read & write scopes.
b-> copy the token key to my_pat_token.txt file
c-> export the path
#export azure_devops=$(cat my_pat_token.txt)
d-> run the loggin cmd
#echo $azure_devops | az devops login --organization https://dev.azure.com/WWgroup/
Failed to store PAT using keyring; falling back to file storage.
You can clear the stored credential by running az devops logout.
Refer https://aka.ms/azure-devops-cli-auth to know more on sign in with PAT.
Azure tools and utilities version pls see below
#az --version
azure-cli                         2.49.0
core                              2.49.0
telemetry                          1.0.8
Extensions:
azure-devops                      0.26.0
Dependencies:
msal                              1.20.0
azure-mgmt-resource               22.0.0
Python location '/opt/az/bin/python3'
Extensions directory '/home/wwserviceadmin/.azure/cliextensions'
Python (Linux) 3.10.10 (main, May 19 2023, 08:20:31) [GCC 11.3.0]
Legal docs and information: aka.ms/AzureCliLegal
Your CLI is up-to-date.
Please check and let me know if there any further information need to be added,thanks.
Regards,
Shilesh
Related command
az devops login --organization https://dev.azure.com/WWgroup/
Errors
Failed to store PAT using keyring; falling back to file storage.
You can clear the stored credential by running az devops logout.
Refer https://aka.ms/azure-devops-cli-auth to know more on sign in with PAT.
Issue script & Debug output
.com"}},"resourceVersion":2,"metaTypeId":1},"instanceId":"70abfbfb-51f6-485c-8d7f-ed8031f90290","deploymentId":"917a458e-1d30-b5
3d-ff6e-6b3ef9f8a0de","deploymentType":"hosted","locationServiceData":{"serviceOwner":"00025394-6065-48ca-87d9-7f5672854ef7","defaultAcc
essMappingMoniker":"PublicAccessMapping","lastChangeId":245633076,"lastChangeId64":245633076}}'
keyring.backend: Loading KWallet
keyring.backend: Loading SecretService
keyring.backend: Loading Windows
keyring.backend: Loading chainer
keyring.backend: Loading macOS
cli.azext_devops.dev.common.credential_store: Keyring backend : keyring.backends.fail.Keyring (priority: 0)
cli.azext_devops.dev.common.credential_store: Failed to store PAT using keyring; falling back to file storage.
cli.azext_devops.dev.common.credential_store: You can clear the stored credential by running az devops logout.
cli.azext_devops.dev.common.credential_store: Refer https://aka.ms/azure-devops-cli-auth to know more on sign in with PAT.
cli.azext_devops.dev.common.credential_store: Keyring failed. ERROR :No recommended backend was available. Install the keyrings.alt pack
age if you want to use the non-recommended backends. See README.rst for details.
cli.azext_devops.dev.common.credential_store: Storing credentials in the file: /home/czsmartserviceadmin/.azure/azuredevops/personalAcce
ssTokens
cli.azext_devops.dev.team.credentials: Another organization is already set as default.
cli.knack.cli: Event: CommandInvoker.OnTransformResult [<function _resource_group_transform at 0x7fa6885b6c20>, <function _x509_from_bas
e64_to_hex_transform at 0x7fa6885b6cb0>]
cli.knack.cli: Event: CommandInvoker.OnFilterResult []
cli.knack.cli: Event: Cli.SuccessfulExecute []
cli.knack.cli: Event: Cli.PostExecute [<function AzCliLogging.deinit_cmd_metadata_logging at 0x7fa68856ee60>]
az_command_data_logger: exit code: 0
cli.main: Command ran in 0.618 seconds (init: 0.180, invoke: 0.438)
telemetry.main: Begin splitting cli events and extra events, total events: 1
telemetry.client: Accumulated 0 events. Flush the clients.
telemetry.main: Finish splitting cli events and extra events, cli events: 1
telemetry.save: Save telemetry record of length 3314 in cache
Expected behavior
az devops loggin should happen
Environment Summary
#az --version
azure-cli                         2.49.0
core                              2.49.0
telemetry                          1.0.8
Extensions:
azure-devops                      0.26.0
Dependencies:
msal                              1.20.0
azure-mgmt-resource               22.0.0
Python location '/opt/az/bin/python3'
Extensions directory '/home/wwserviceadmin/.azure/cliextensions'
Python (Linux) 3.10.10 (main, May 19 2023, 08:20:31) [GCC 11.3.0]
Legal docs and information: aka.ms/AzureCliLegal
Your CLI is up-to-date.
Additional context
No response

Thank you for opening this issue, we will look into it.

@yonzhan   we are facing the same issue, any update please?

Hi @shileshbabu  , have you found a solution for this issue ?

Hi @maldamiri, we tried to repro the issue, but we are unsuccessful.
we are successfully login with PAT using below two methods.
1.cat my_pat_token.txt | az devops login --organization https://dev.azure.com/contoso/

2.#export azure_devops=$(cat my_pat_token.txt)
#echo $azure_devops | az devops login --organization https://dev.azure.com/ChatOpstestOrg/

Please let us know if you still faced the issue after trying above methods.

Hi @Arvindgade I was unable to reproduce successfully.

either in the pipeline or in the Linux terminal, same error

@brunooliveiramelo  Did you try az devops logout as suggested in the screenshot share shared by you

I also encountered the same error, is there any latest solution?

Hi @Alancere  I can see some warnings in your windows. Could you please try to run the devops commands after the warnings messages.
Thanks,
Anjali

Hi @Alancere I can see some warnings in your window. Could you please try to run the devops commands after the warnings messages.
Thanks, Anjali

Any update on this error?

I have exactly the same problem - any news?

I've had this same warning message for over a year - any update?

I ran into same issue:
lizhuhua@CHIEVMlizhuhu01:~$ az --version
azure-cli                         2.53.1 *
core                              2.53.1 *
telemetry                          1.1.0
Extensions:
azure-devops                      0.26.0
Dependencies:
msal                            1.24.0b2
azure-mgmt-resource             23.1.0b2
Python location '/opt/az/bin/python3'
az devops login --organization https://dev.azure.com/AzureCSI
Token:
Failed to store PAT using keyring; falling back to file storage.
You can clear the stored credential by running az devops logout.
Refer https://aka.ms/azure-devops-cli-auth to know more on sign in with PAT.
Any workaround?

Hi @lizhuhuams Are you facing only warnings?

No,
I was not able to run az devops commands. Thus I was unable to download image to my VM.
Linda
From: v-anvashist @.>
Sent: Tuesday, December 19, 2023 8:36 PM
To: Azure/azure-cli @.>
Cc: Linda Hua @.>; Mention @.>
Subject: Re: [Azure/azure-cli] Failed to store PAT using keyring; falling back to file storage. (Issue #26731)
Hi @lizhuhuamshttps://github.com/lizhuhuams Are you facing only warnings?

Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-cli/issues/26731#issuecomment-1863831785, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYV7AKWNRJB3PDMRLUEZV4DYKJTLNAVCNFSM6AAAAAAZP2X2HWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRTHAZTCNZYGU.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Hi @lizhuhuams You are trying to run commands in which machine is it windows or linux?
Please send some screenshots also.

you can work with this task on Azure Pipeline:

bash: |
az pipelines build list
git pr list
displayName: 'Show build list and PRs'
env:
AZURE_DEVOPS_EXT_PAT: $(System.AccessToken) # or your PAT
https://learn.microsoft.com/en-us/azure/devops/cli/azure-devops-cli-in-yaml?view=azure-devops

Hi @vunguyen22271, do we need to consider your shared task to work on @lizhuhuams issue? We are not able to repro it fully in Linux environment I can see only warnings but still we are able to run the command as below screenshot for reference

Hi @vunguyen22271, do we need to consider your shared task to work on @lizhuhuams issue? We are not able to repro it fully in Linux environment I can see only warnings but still we are able to run the command as below screenshot for reference

Hi, the task I shared working on Azure Pipeline.
About @lizhuhuams issue, I create AZURE_DEVOPS_EXT_PAT environment variable, after that I ran "az pipelines build list" and I can see the Build Information.
I think just ignore the warning and make sure PAT have enough permissions!

Hi @vunguyen22271, Thanks for the update!
@lizhuhuams We have created the user story for the same and will update in the below work item.
https://dev.azure.com/mseng/AzureDevOps/_workitems/edit/2103441

the same issue
I can see "project list" but can't create PR
# az -v azure-cli                         2.63.0 core                              2.63.0 telemetry                          1.1.0 Extensions: azure-devops                       1.0.1 Dependencies: msal                              1.30.0 azure-mgmt-resource               23.1.1 Python location '/opt/az/bin/python3' Extensions directory '/root/.azure/cliextensions' Python (Linux) 3.11.8 (main, Jul 31 2024, 03:41:17) [GCC 12.2.0]


Crash when setting view on TurbolinksSession

My app recently began crashing on some devices when I set the view on a TurbolinksSession.
session.activity(this)
                .adapter(this)
                .view(turbolinksView) // Crashes on this line
                .visit(url);

It has been working fine for over a year and this recently popped up without us making any changes to our code base (I'm assuming related to a change in Chromium). Looks like Basecamp has acknowledged a similar issue on their Twitter account and was wondering if there were plans to fix the issue for this library as well. Thanks!

at android.app.LoadedApk.forgetReceiverDispatcher (LoadedApk.java:1047)
at android.app.ContextImpl.unregisterReceiver (ContextImpl.java:1359)
at android.content.ContextWrapper.unregisterReceiver (ContextWrapper.java:651)
at android.content.ContextWrapper.unregisterReceiver (ContextWrapper.java:651)
at android.content.ContextWrapper.unregisterReceiver (ContextWrapper.java:651)
at org.chromium.content.browser.accessibility.LollipopWebContentsAccessibility.onDetachedFromWindow (LollipopWebContentsAccessibility.java:42)
at org.chromium.content.browser.ContentViewCoreImpl.onDetachedFromWindow (ContentViewCoreImpl.java:339)
at org.chromium.android_webview.AwContents$AwViewMethodsImpl.onDetachedFromWindow (AwContents.java:351)
at org.chromium.android_webview.AwContents.onDetachedFromWindow (AwContents.java:598)
at com.android.webview.chromium.WebViewChromium.onDetachedFromWindow (WebViewChromium.java:802)
at android.webkit.WebView.onDetachedFromWindowInternal (WebView.java:2365)
at android.view.View.dispatchDetachedFromWindow (View.java:16685)
at android.view.ViewGroup.dispatchDetachedFromWindow (ViewGroup.java:3426)
at android.view.ViewGroup.removeViewInternal (ViewGroup.java:4956)
at android.view.ViewGroup.removeViewInternal (ViewGroup.java:4930)
at android.view.ViewGroup.removeView (ViewGroup.java:4861)
at com.basecamp.turbolinks.TurbolinksView.attachWebView (TurbolinksView.java:161)
at com.basecamp.turbolinks.TurbolinksSession.view (TurbolinksSession.java:264)

Hey @jchunch, thanks for calling our attention to this. We did run into this last week and patched it up with a not-so-pretty workaround. We were making sure the patch worked in the wild (it has) as well and try to find the low level root cause (we have, we think).
I'll work up a patch today and try to get it out by tomorrow. Thanks!

Pushed a workaround/fix for now. It's been released as version 1.0.8 of the library, so please try pointing to that version and test with Chrome 64 on Android. That should temporarily alleviate the crash.
Thanks!

@lateplate thanks for the quick fix!

Sure thing! Note that this is a temp workaround as we try to find a more permanent solution.


#73 improves printOn: message

This class is not referenced anywhere and does not seem to have any real functionality, should be removed?

Handled in https://github.com/pharo-rdbms/glorp/issues/100


issue/6096-log-which-pip-index (#7064)

Pull request opened by the merge tool on behalf of #7064

Merged in d6b62096246ab85f26b08be7a64aa08572178959


How to import to Swift project?

I`m trying to import this library to a swift project, but I can`t. This don`t compile. :(

Make sure you add use_frameworks in your Podfile
Add bridging header which include code #import <PLCameraStreamingKit/PLCameraStreamingKit.h>
Good luck.

Not working yet, the library has not shown at "Linked Frameworks and Libraries". :(

Just import Pods in your swift file. You should be able to use PLCameraStreamingKit class.


Rox 11149 collector ci migration test scripts

Description
Copies the .circleci directory to .openshift-ci. Many changes will need to be made to this new directory, but this should be a helpful starting point.
Checklist

[x] Investigated and inspected CI test results

Testing Performed
See above

Not needed as get-builder-flavor will not be migrated.


WIP: revert Mesos to pre-monolith build.

This is an attempt to revert the Mesos build system back to its state before the Mesos modules were built statically into the Mesos binaries.
High-level description
What features does this change enable? What bugs does this change fix?
Corresponding DC/OS tickets (required)

D2IQ-ID JIRA title / short description.

Related tickets (optional)

D2IQ-ID JIRA title / short description.

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

Not relevant anymore.


WIP: Allow for ControlBuilders to construct par blocks with *=

Edit: I changed this back to a draft because I'm not sure this is actually useful. Turns out this doesn't really solve the problem I had in the first place. May end up scrapping this. Happy to hear any thoughts on the usefulness of this.

Closes #1889, although slightly changes what is actually implemented when compared to the issue.
ControlBuilders can now use *= to create par blocks. Using *= multiple times should flatten par blocks in the same way += does. So we don't get things like par{A; par{B; C;}}.
Please let me know if this behaves as expected? I went back and forth a bit about how this should work to feel "natural"
Draft because I'd like to

[x] Add some runt tests that make sure that par blocks and seq blocks combine properly.
[x] Add documentation regarding *= and its interactions with +=.

Some examples of *= and += interactions:
my_comp.control *= par(group1, group2)

will output
par{
  group1;
  group2;
}

If we take the above python and add another line that uses *= the initial par block will remain flat:
my_comp.control *= par(group1, group2)
my_comp.control *= group3

produces
par{
  group1;
  group2;
  group3;
}

similar to the existing += behavior.
If we use *= and then a += we will have the par block wrapped in a seq
my_comp.control *= par(group1, group2)
my_comp.control += group3

produces
seq{
  par{
    group1;
    group2;
  }
  group3;
}

hopefully as expected!

Cool stuff!! Two questions.
One

my_comp.control *= [group1, group2]

will output
par{
  group1;
  group2;
}

Are you sure? Since box brackets have semantics in the eDSL, I would have thought that you'd get:
par{
  seq {
    group1;
    group2;
  }
}

Are you doing something clever to avoid this? It seems to me that my little theory has evidence in your runt test, specifically when you do:
https://github.com/calyxir/calyx/blob/f6fd2736c77dd625cfa1ac1541344c69c5e21b93/calyx-py/test/par.py#L27
and expect:
https://github.com/calyxir/calyx/blob/f6fd2736c77dd625cfa1ac1541344c69c5e21b93/calyx-py/test/par.expect#L32-L35
to be added to the par that's under construction.
Two

If we use *= and then a += we will have the par block wrapped in a seq
my_comp.control *= [group1, group2]
my_comp.control += group3

produces
seq{
  par{
    group1;
    group2;
  }
  group3;
}

Very cute indeed, though, if I'm getting this correctly, you only get to tack on things "on the go" to the outermost par/seq that is under construction. So there is no way for me to go add group4 like so:
seq{
  par{
    group1;
    group2;
    group4; // new!!
  }
  group3;
}

Is that right? It's totally okay if so. I was mostly just genuinely curious, and I'd suggest that you impress this fact/limitation upon the reader in the little motivating example that I am requesting in the docs!

Cool! Sorry I got here a little late, but I do think something along these lines could be useful. In particular, it seems cool to be able to build up parallelism in place… even with no flattening at all, it would at least be marginally useful to do something like ctrl *= foo to construct par { ctrl; foo; }. So I don't think it's a lost cause!
@anshumanmohan makes a good point, though, about lists meaning sequencing in general… so hopefully ctrl *= [foo, bar] constructs par { ctrl; seq { foo; bar; }; }.

Spoke with @sampsyo synchronously and I think it's been decided for now that the way to accomplish this is to keep a list of threads we want to see in a par block my_list = [A,B,C] and create said par block with my_par = par(*my_list).
This will create par {A;B;C;}
Closing this.

Sounds good, but thanks for the cool idea and implementation!


SciMLBase = "1, 2"

SciMLBase is now at 2 and PEtab have similar issues to this: https://github.com/bifurcationkit/BifurcationKit.jl/issues/121
currently set
SciMLBase = "1, 2"

but maybe something else is prefered.

A week ago SciMLBase v2 failed for me (thus I did not update), but now it works. Is there then any reason to keep compat for version below 2.0?

Thanks, will then merge this


WIP: TLSv1.3: Support KeyUpdate

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

Description of change

This adds support for the TLSv1.3 KeyUpdate message.
It adds a new API call SSL_key_update() which provides the ability for an application to update its sending keys, and send a KeyUpdate message. Additionally the application can request that the peer also updates its own sending keys at the same time (SSL_KEY_UPDATE_REQUESTED) or not (SSL_KEY_UPDATE_NOT_REQUESTED).
At one point it was suggested that we could make a call to SSL_renegotiate() do a KeyUpdate instead for TLSv1.3. On reflection I'm not convinced that's a great idea - so I haven't done that. Renegotiation and KeyUpdate are different things. For example, you can't do client auth through KeyUpdate. It would confuse the semantics of the function to try and fit the two concepts into a single API call. It also wouldn't remove the need for a separate SSL_key_update() API anyway because of the need to flag whether a peer update is requested or not.
It occurs to me that an application is going to need to know whether a TLSv1.3 (or greater) connection has been established or not (e.g. to know whether to bother calling SSL_renegotiate() or not). So I have also provided a SSL_is_tls13_plus() function. Not sure that is the best name. Open to suggestions.
I have managed to (manually) test sending KeyUpdates against Boring but not receiving them, since Boring never sends them at the moment. Picotls also can't handle them. It does work OpenSSL talking to OpenSSL though.
This is marked as WIP as I still need to provide some documentation for the new API call. I also need to write some tests.

I totally agree with your intro comment about keyupdate/renegotiation.

Instead of SSL_is_tls13_plus(), I'd suggest checking for capabilities.  SSL_can_key_update() or something more elegant.

Instead of SSL_is_tls13_plus(), I'd suggest checking for capabilities. SSL_can_key_update() or something more elegant.

That's an interesting idea which is quite attractive. The main problem I see with that is that there are a whole load of reasons why you're going to need to know you're dealing with a TLSv1.3 connection and most of them are nothing to do with KeyUpdate. For example the way sessions work is quite different, client auth, early data, etc. Should we have a whole suite of SSL_can_xxx() functions which all do the same thing - and tell you whether you have TLSv1.3 or not.

Instead of SSL_is_tls13_plus(), I'd suggest checking for capabilities. SSL_can_key_update() or something more elegant.

That's an interesting idea which is quite attractive. The main problem I see with that is that there are a whole load of reasons why you're going to need to know you're dealing with a TLSv1.3 connection and most of them are nothing to do with KeyUpdate. For example the way sessions work is quite different, client auth, early data, etc. Should we have a whole suite of SSL_can_xxx() functions which all do the same thing - and tell you whether you have TLSv1.3 or not.

I would prefer that.  I'm thinking future.  What if a TLSv1.4 also gets numerous incomatible changes?  TLSv2.0?    It's a problem waiting to happen.  However, asking "can I do this?" and get a precise response for exactly that thing someone wants to do should be rather safe.

Please don't add these functions until (unless) we need them.

Well, @mattcaswell has identified a need for one now, so...

No he hasn't.  He thinks it's useful for future-proofing.  My counter to that is "why isn't getting the TLS version enough?"  We should not add API's we think might be useful, as we have to live with them for a very very long time.

"why isn't getting the TLS version enough?"

Well I did think about that. The "obvious" way to do it is:
if (SSL_get_version(s) == TLS1_3_VERSION)
    do_something();

Of course that fails as soon as TLSv1.4 comes along. So perhaps better is:
if (SSL_get_version() >= TLS1_3_VERSION)
    do_something();

But actually that's worse because the above evaluates to "true" if you happen to be using DTLS (any version). So actually this is quite tricky to get right and probably the kind of thing that should be the responsibility of the library.

Oh come on :)  The only test that matters right now is "is this 1.3"
NOBODY needs to ask "TLS 1.3 or later"  No bo dy.

Why should the application need to check whether it can do something before trying to do it?  Let the application just SSL_keyupdate() and deal with the error if the connection is TLS 1.2 or below.

@richsalz wrote:

Oh come on :) The only test that matters right now is "is this 1.3"
NOBODY needs to ask "TLS 1.3 or later" No bo dy.

Well, that's true right now. But that's the point isn't it? Code written in applications right now is potentially going to live for a long time....past the point when TLSv1.4 comes out. And actually we are talking about an API with the lifespan of 1.1.1, so whatever we decide now has to still make sense for applications written in 2+ years time.
Even if you don't buy the argument above and we don't think people need to worry about TLSv1.4 yet, you can guarantee that people are going to write:
if (SSL_get_version() >= TLS1_3_VERSION)
Which is wrong.
Actually though Richard is right. Right now applications do need to know whether they should call SSL_key_update() or SSL_renegotiate()...and perhaps asking if the version is TLSv1.3 or greater is the wrong test anyway (what about when the extension comes along that disables KeyUpdate requests; or when TLSv1.4 removes the KeyUpdate capability). So I'm quite drawn to the capability test idea - although I don't like the potential explosion of different functions that would entail (perhaps a single function that takes as a parameter a feature id?)
@kaduk wrote:

Why should the application need to check whether it can do something before trying to do it? Let the application just SSL_keyupdate() and deal with the error if the connection is TLS 1.2 or below.

Yes that is possible too, and also something I thought about. Its quite messy though...typically this is going to end up putting error messages on the queue which you probably want to remove before continuing. Also you can't tell whether it failed because the connection doesn't support it or because "something bad happened".

By adding this API, you are encouraging developers to predict the future, which is a very bad idea.

By adding this API, you are encouraging developers to predict the future, which is a very bad idea.

Which one? Do you mean SSL_is_tls13_plus() or Richard's capability test idea? If the latter then I disagree...deciding whether to call SSL_key_update() or SSL_renegotiate() is a "right now" problem that has nothing to do with what might happen in the future (although it could be impacted by those things).

The only test that is needed right now is "is this TLS 1.3"
We don't know what TLS-next will even be called.
We don't know what TLS-next will decide; it could do PFS and new keys for every record.
What do app developers need right now?

What do app developers need right now?

They need to know whether to call SSL_key_update() or SSL_renegotiate() (and probably various other similar things).

Skipping the "and probably" since that's a guess, not a fact :)
A single API that says "SSL_refresh_keys" which calls the right thing underneath seems like a reasonable approach, then.

Skipping the "and probably" since that's a guess, not a fact :)

Well one other thing that immediately springs to mind is session handling. With <= TLSv1.2 you can call SSL_get0_session() at any time after the connection is established. With TLSv1.3 if you do that before the NewSessionTicket message has been sent then you are going to get a bad session (this is an outstanding TODO item). Another one will be around whether you can do early data or not.

A single API that says "SSL_refresh_keys" which calls the right thing underneath seems like a reasonable approach, then.

Hmmm....that's a possibility - although it kind of takes us back to the "single function that does two different things" argument that made me want to separate SSL_key_update() from SSL_renegotiate() in the first place.

It's not quite the same, it moves up a level and only does the same thing on both versions.  I deliberately called it "refresh keys"
Early data is a tls1.3-or-not thing.  not sure if session keys matter, have to see what happens when you finish that code.

@mattcaswell said:

So I'm quite drawn to the capability test idea - although I don't like the potential explosion of different functions that would entail (perhaps a single function that takes as a parameter a feature id?)

Yes, I was thinking that would be a possibility.  It's a bit like the cpuID bits (although we'd keep that internal).
I don't quite understand how specifying current capabilities is trying to predict the future.  Do you mean it's an attempt to predict a future where there will be other capabilities?  Considering the history of SSL/TLS so far, is that even a difficult prediction?
However, if eveyone is fine with something like SSH_refresh_keys(), I have no issues

However, if eveyone is fine with something like SSH_refresh_keys(), I have no issues

SSH_refresh_keys()? Did we change projects :-)
Actually the more I think about it the less convinced I am that SSL_refresh_keys() is the right answer.

Updated to address the comments received so far. Also rebased to deal with some conflicts that were showing. I have also added documentation to this PR. Still needs tests, so still WIP.

Tests now added. I also rebased. I've taken this out of WIP - this is now ready for review.

New commits pushed addressing all comments.

+1

Pushed. Thanks.


Add pyproject

The setup requires numpy, so we need to tell python that. This is to adhere with https://peps.python.org/pep-0517/
After this update, you will be able to use other build tools such as poetry to install the package.

Thank you very much for the merge!


Clarity about when the bot can merge pull requests

I've been using pull for merging changes from an original repository to my forked version of the repository.  Pull sometimes merges these pull requests automatically, but other times it just creates the pull request and I have to manually carry out the merge.
What determines whether pull will or will not automatically merge the pull request after creating it?

GitHub decides which pull requests can and cannot be merged by a GitHub app. I know pull requests with workflow files changes have to be merged manually.
I'd gladly take a look if you have other examples.


Supermicro X10DRG-OT+-CPU Broadwell Re-Bar on linux working and not.

I have the latest bios on this board. It has 3 GPU. 2x3090 and a P40.
Ubuntu 22.04 Installed kernel 6.1.
Above 4g is enabled and supported. No bios setting for re-bar.
The P40 is using a 32gb bar. One 3090 supports resizing, the second I need to flash a vrom update on.
Unfortunately both 3090s only use 256MB bar. I have fairly recent nvidia 5.xx driver. Is there some reason one 3090 doesn't use 32g bar right now and how can I force it?

@Ph0rk0z You need to use option in NVIDIA driver NVreg_EnableResizableBar=1 to do resizing by Linux kernel
or use ReBarUEFI to do it by UEFI.

Thank you, I will try to enable it. Am trying to avoid patching this bios and fiddling with backing up with HW programmer.

Unfortunately enabling it did not help. I set nvidia.NVreg_EnableREsizeableBar=1 in kernel and it shows enabled but my 3090 still says 256 selected but 32gb supported. I am trying flashed bios now. None of the patches applied except for the broadwell USB3 fix. I will build the linux executable and see if it enables after I run that.

Ok.. I have ran the PE and set size of 32. 2 of my cards show correct big BAR right now.. I have to flash the 3rd to support it. You can call this mobo working.

It's likely 3.3v chip, its a server. No need to unlock FD or do any crazy stuff here. The BMC can recover bad flashes if you got one. On mine, bios is signed but no bootguard was enabled. Try to read the whole chip with intel FPT.

Serials and macs should be in the nvram part of the bios. I guess for this version, you're right, there's no linux FPT, only for newer gens.
BMC seemed to read the whole thing when I used it. All update files are the full image but I didn't edit the FD.
Didn't try to turn off ME because of the same worry.

On mine it did the USB patch only I think.


[zh] Sync Updates to the Auto-refreshing Official CVE Feed blog into Chinese

Translate Updates to the Auto-refreshing Official CVE Feed blog into Chinese:
content/zh-cn/blog/_posts/2023-04-25-Updates-to-the-Auto-refreshing-Official-CVE-Feed/index.md

Hi @wilsonwu, pls refer to zh localization style guide or the recent PR of a zh-cn blog.

PR of a zh-cn blog

Got it, thanks for these information, I will fix all ASAP.

Please squash your commits into a single one, thanks.

Done

/lgtm


Hierarchical LVS support

Update Netgen
steps.Netgen.LVS:

Add NETGEN_INCLUDE_MARCOS_NETLIST. If enabled macros' netlist are loaded when running LVS. Either pnl or nl or vh views are selected.
Update Netgen setup file to equate cells inside macros where the GDS is generated with blackbox macro option

Sorry, misclicked. Changes are requested


demo.r | document error

Project Robyn
Describe issue
demo/demo.r, line 120: Also, to convert weekly to daily we can transform the parameter to the power of (1/7), so to convert 30% daily to weekly is 0.3^(1/7) = 0.84.
shouldn't this be "convert 30% weekly to daily is 84%"?

Calling the theta "decay rate" could be bit misleading, because 30% means 30% carrying over to the next period, not 30% less. The doc is correct. Daily theta should be higher than weekly.


AMP Review 2

Purpose
The purpose of this PR is to update the repo to meet the requirements laid out in AMP Review Checklist
Changes Made

[x] Add LICENSE.txt
[x] Update and add Cloudera Copyright source headers
[x] Pinned dependency versions
[x] Minor updates to .project-metadata.yaml

@victordibia When you get the chance, can you review and merge these changes? Thanks!

Thanks Andrew!


Remove Awares and Templates

I am not completely sure about this one. It's nice to have these convenient interfaces and traits. However, in many cases you might want to have a custom getter which checks the existence of the factory first and use for example a discovery to get a default implementation.

Decided to remove these anyway, we can readd them later if there is need.

+1
constructor injection is much cleaner anyways.


Add validation to new settings editor

Closes #55801

Looks like there's some tests that need updating

Never mind, looks like that's unrelated, despite being a tree issue.

createValidator probably deserves unit tests. (But don't let that block merging this)

@roblourens I think this should be ready to go.


Print slides/export as PDF

See https://revealjs.com/pdf-export/
Slides can be print-formatted by adding /?print-pdf to the end of the URL. Maybe we put this in sidebar menu?
An actual "print" button (if needed) can use the following code
<button onclick="window.print();return false;" value="print">Print</button>

For PDFs users would then need to select "Save as PDF"
Alternatively we just add an alternate "view" for the content that doesn't use the reveal layout.

During testing, I encountered a bug linked to the Prettier Code Formatting plugin in Visual Studio. Normally, this plugin auto-formats the code when I save a file, which helps maintain clean code. However, when I edit and save the reveal.html file, it seems that the plugin corrupts the code, causing the slides to stop loading. I'll make sure to include this in the documentation.

@YSL4L We'll try to finish this up for the WiSe version